Accedian EtherNID GE Service manual

1
EtherNID™
Administrator’s Guide
for the
EtherNID™ EE
EtherNID™ GE
MetroNID™ TE
MetroNID™ TE-R

2
Release 4.1.1 (September 2008)
Accedian Networks, EtherNID, EtherSHELF, MetroNID and Performance Assurance Agent (PAA) are trademarks of Accedian Networks
Inc.
All other brand and product names are trademarks or registered trademarks of their respective corporations.
The mention of any product does not constitute an endorsement by Accedian Networks Inc.
The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Accedian Networks Inc. Accedian Networks Inc. assumes no responsibility or liability for any errors or inaccuracies that
may appear in this document.
Except as permitted by such lease agreement, no part of this publication may be reproduced, stored in any retrieval system, or
transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without prior written consent of Accedian
Networks Inc.
Changes are periodically made to the information herein; these changes will be incorporated into new editions of this publication.
Accedian Networks Inc. may make improvements and/or changes in the products and/or software programs described in this publication
at any time.
If you have comments on this manual or the products it describes, address them to:
Accedian Networks Inc.
Attention: Publications
4878, Levy street, Suite 202
Saint-Laurent, Québec
Canada
H4R 2P1
Tel: [phone]
Fax: [phone]
Toll free: 1-866-685-8181
Accedian Networks Inc. may use or distribute whatever information you supply in any way it believes appropriate without incurring any
obligations to you.
Copyright © 2005-2008 Accedian Networks Inc. All rights reserved, including those to reproduce this publication or parts thereof in any
form without permission in writing from Accedian Networks Inc.

3
Contents
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
Introducing the EtherNID . . . . . . . . . . . . . . . . . . . 6
Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . 7
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Application scenario . . . . . . . . . . . . . . . . . . . . . . . 8
2
Hardware installation . . . . . . . . . . . . . . . . 9
Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . 9
Front panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Status lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mounting options . . . . . . . . . . . . . . . . . . . . . . . . 14
Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . 14
Rack mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Powering the EtherNID . . . . . . . . . . . . . . . . . . . . 18
Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Resetting to factory defaults . . . . . . . . . . . . . . . . 20
3
Management and configuration . . . . . . . 21
About the management web interface . . . . . . . . 21
Starting the management web interface . . . . . . . . . 21
Managing web interface accounts . . . . . . . . . . . . . . 21
DNS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring interfaces . . . . . . . . . . . . . . . . . . . . . 25
Creating or editing an interface . . . . . . . . . . . . . . . . 25
Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 26
Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Adding a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Route parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Syslog options . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Syslog parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Setting the system date and time . . . . . . . . . . . . 30
Timezone and Daylight saving . . . . . . . . . . . . . . 31
SNMP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
SNMP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 33
History buckets . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 34
Remote retrieval of history buckets . . . . . . . . . . . 35
Scheduling and file transfer configuration . . . . . . . . 36
Session management . . . . . . . . . . . . . . . . . . . . . 37
Management parameters . . . . . . . . . . . . . . . . . . . . 37
Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . 38
Session configuration . . . . . . . . . . . . . . . . . . . . . 39
Session parameters. . . . . . . . . . . . . . . . . . . . . . . . . 39
Session management . . . . . . . . . . . . . . . . . . . . . 40
Management parameters . . . . . . . . . . . . . . . . . . . . 40
Session RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 41
RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . 41
Management bridge . . . . . . . . . . . . . . . . . . . . . . 43
Configuration procedure . . . . . . . . . . . . . . . . . . . . . 43
4
Port configuration . . . . . . . . . . . . . . . . . .45
Port list and port status . . . . . . . . . . . . . . . . . . . . 45
Port configuration and status. . . . . . . . . . . . . . . . . . 47
Port options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring port settings . . . . . . . . . . . . . . . . . . . 49
Port parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
PHY auto-negotiation configuration . . . . . . . . . . . 55
PHY parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . 57
SFP information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
SFP thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
SFP memory and monitor memory . . . . . . . . . . . . . 61
Cable verification . . . . . . . . . . . . . . . . . . . . . . . . . 62
Testing a cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4
5
Monitoring and filtering . . . . . . . . . . . . . 64
Service mapping . . . . . . . . . . . . . . . . . . . . . . . . . 64
Viewing CoS profiles . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring a CoS Profile . . . . . . . . . . . . . . . . . . . . 65
CoS Profile parameters . . . . . . . . . . . . . . . . . . . . . . 66
Assigning a CoS profile to a policy . . . . . . . . . . . . . 67
Viewing Bandwidth regulator sets . . . . . . . . . . . . . . 67
Configuring a Bandwidth regulator set. . . . . . . . . . . 68
Bandwidth regulator set parameters . . . . . . . . . . . . 68
Assigning a Bandwidth regulator set to a policy . . . 69
Layer-2 Protocol Tunneling . . . . . . . . . . . . . . . . . 70
Adding a new L2PT Rule . . . . . . . . . . . . . . . . . . . . . 72
L2PT rule settings . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Traffic policies and monitoring . . . . . . . . . . . . . . 74
Configuring a traffic policy . . . . . . . . . . . . . . . . . . . . 75
Policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Traffic filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Viewing L2 filters . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configuring an L2 filter. . . . . . . . . . . . . . . . . . . . . . . 80
L2 filter parameters . . . . . . . . . . . . . . . . . . . . . . . . . 80
Viewing IPv4 filters. . . . . . . . . . . . . . . . . . . . . . . . . . 82
Configuring an IPv4 filter . . . . . . . . . . . . . . . . . . . . . 83
IPv4 filter parameters. . . . . . . . . . . . . . . . . . . . . . . . 84
Bandwidth policing . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring a regulator . . . . . . . . . . . . . . . . . . . . . . 87
Regulator settings . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Assigning a regulator to a policy . . . . . . . . . . . . . . . 88
6
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alarm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alarm configuration . . . . . . . . . . . . . . . . . . . . . . . 90
Customizing an alarm . . . . . . . . . . . . . . . . . . . . . . . 91
Alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7
Operations, Administration and
Maintenance. . . . . . . . . . . . . . . . . . . . . . . 95
OAM configuration . . . . . . . . . . . . . . . . . . . . . . . 95
Configuring an OAM instance . . . . . . . . . . . . . . . . . 96
OAM instance parameters . . . . . . . . . . . . . . . . . . . . 96
Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Loopback parameters . . . . . . . . . . . . . . . . . . . . . . . 99
OAM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Transmitted and Received event notifications. . . . 102
OAM status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Detailed status information . . . . . . . . . . . . . . . . . . 105
OAM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 107
OAM detailed statistics information . . . . . . . . . . . . 108
8
RFC-2544. . . . . . . . . . . . . . . . . . . . . . . . .113
RFC-2544 Generator . . . . . . . . . . . . . . . . . . . . . 113
Viewing RFC-2544 Generator . . . . . . . . . . . . . . . . 113
Configuring RFC-2544 Generator . . . . . . . . . . . . . 114
RFC-2544 monitor . . . . . . . . . . . . . . . . . . . . . . . 118
Viewing RFC-2544 Monitor . . . . . . . . . . . . . . . . . . 118
Detailed view of RFC-2544 Monitor. . . . . . . . . . . . 119
RFC-2544 testsuite . . . . . . . . . . . . . . . . . . . . . . 121
Viewing RFC-2544 Testsuites . . . . . . . . . . . . . . . . 121
Detailed view of RFC-2544 Testsuites . . . . . . . . . 122
RFC-2544 reports . . . . . . . . . . . . . . . . . . . . . . . 126
Starting an RFC-2544 Testsuite . . . . . . . . . . . . . . 126
Viewing RFC-2544 Reports . . . . . . . . . . . . . . . . . . 127
9
Performance Assurance Agent. . . . . . .129
PAA configuration . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring a probe . . . . . . . . . . . . . . . . . . . . . . . . 131
PAA parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 132
PAA status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Detailed PAA status. . . . . . . . . . . . . . . . . . . . . . . . 136
PAA results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Detailed PAA results . . . . . . . . . . . . . . . . . . . . . . . 138

5
10
Traffic shaper. . . . . . . . . . . . . . . . . . . . . 140
Traffic shaper configuration . . . . . . . . . . . . . . . 140
Traffic shaper statistics . . . . . . . . . . . . . . . . . . . 144
11
CFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
CFM continuity fault management . . . . . . . . . . 146
CFM configuration . . . . . . . . . . . . . . . . . . . . . . 147
CFM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 154
12
Command Line Interface. . . . . . . . . . . . 156
Command summary . . . . . . . . . . . . . . . . . . . . . 156
Command syntax . . . . . . . . . . . . . . . . . . . . . . . 158
13
Appendix A - Alarms . . . . . . . . . . . . . . . 159
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
14
Appendix B - MIB support . . . . . . . . . . 163
Public MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Private MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

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

1: Introduction Introducing the EtherNID
7
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
8
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.
Demarcation
point
Remote
Management
Station
Hub Node Transport Media Access Node EtherNIDTM Customer Device
Network
port
Client
port
Test traffic
Test traffic looped back
Management port
Local
Management
Station
Customer SiteCarrier Site
Test
Equipment
Remote Site
Remote Site
Customer
traffic
Legend
Test traffic
Customer traffic
Ethernet connection

2: Hardware installation Hardware overview
9
Chapter 2: Hardware installation
Hardware overview
Front panel - EtherNID EE
Front panel - EtherNID GE, and MetroNID TE / TE-R
Rear panel - All units
2Hardware installation

2: Hardware installation Hardware overview
10
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:
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.
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.
Light Solid Flashing
Link/RX Port is connected at the link layer. Port is receiving data.
TX N/A Port is transmitting data
Model SFP RJ-45
EE N/A 10Base-THD/TFD
100Base-TX/TXHD/TXFD
(Auto-negotiation/Auto MDIX)
GE / TE
/ TE-R
Fiber SFP
100Base-BX10D/BX10U/FX/F
XFD/LX10
1000Base-BX10D/BX10U/LX/L
XFD/LX10/SX/SXFD/T/TFD
(Auto-negotiation)
Copper SFP
10Base-TFD
100Base-TX/TXFD
1000Base-T/TFD
(Auto-negotiation/Auto MDIX)
10Base-THD/TFD
100Base-TX/TXFD
1000Base-T/TFD
(Auto-negotiation/Auto MDIX)

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

2: Hardware installation Hardware overview
12
Status lights •PWR (green): On when power is applied.
•LPBK (yellow): On when the loopback function is enabled. Flashes when traffic is being
looped-back.
•MIN (yellow): On when a minor alarm condition is present.
•MAJ (red): On when a major alarm condition is present.
•CRIT (red): On when a critical alarm condition is present.
• SFP (green):
•TX: Flashes when the port transmits data.
•Link/RX: Solid when the link level is present. Flashes when the port receives data.
Rear panel The rear panels on all units are identical.
Port/Connectors
•+/-40-57V---0.25A connector: For use with the EtherSHELF connectors or a discrete
power cord (connector sold separately) providing +/-40 to +/-57 V DC.
•5V---2A connector: For use with the DC power adapter.
•Console: RJ-45 serial connection for access to the console interface. Pin-outs for both
ends of the console cable are as follows:
Console
RJ-45
Cable
81
TERMINAL
5
1
9
6
DB-9 Female

2: Hardware installation Hardware overview
13
To establish a connection with the CLI interface on the EtherNID from your computer, use
a terminal emulation program with the following settings:
•Protocol: Serial
•Port: COM1 to 8
•Baud rate: 115200
•Data bits: 8
•Parity: None
•Stop bits: 1
•Flow Control: None
Status light
•5V: On when power is applied via the power adapter.
Buttons
The Bypass and Loopback buttons are used to reset the EtherNID. See "Resetting to factory
defaults" on page 20 for instructions.
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

2: Hardware installation Mounting options
14
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.
Mounting
bracket
Screw
Screw

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

2: Hardware installation Mounting options
16
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.
Warning: Before proceeding to the next step, ensure that power is removed from the DC
circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that
services the DC circuit, switch the circuit breaker to the OFF position, and then tape the
switch handle of the circuit breaker in the OFF position.
2. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).
3. Crimp the two-hole grounding lug around the exposed wire.
Attach brackets before mounting in the drawer.

2: Hardware installation Mounting options
17
4. Use a small wrench to tighten the bolts around the two grounding screws to secure the
two-hole grounding lug to the back of the EtherSHELF
5. Connect the other end of the wire to a grounding point on the rack.
Dimensions
The EtherSHELF is a 4U chassis for 19 inch racks with available side extenders for 23 inch
racks. It holds 12 EtherNIDs all individually fused that are powered by 2 x 48V power feeds.
• Height = 7 inches
• Width = 19 inches
• Depth = 7 inches

2: Hardware installation Powering the EtherNID
18
Powering the EtherNID
The EtherNID can be powered using one of the following options:
DC power adapter
Connect the supplied power adapter to the 5V/2A DC connector on the rear of the unit.
48V DC from the 12 unit EtherSHELF
You can power EtherNIDs mounted in the EtherSHELF using the shelf’s built-in 48 V DC
power connector. Slide the EtherNID into the shelf to engage the power connector on the rear
of the unit.
The EtherSHELF’s power feed must be limited with a 5A/48V fuse. Voltage must be in the
range +/-40 to +/-57 V DC using AWG 14 gauge or larger cable.
48V DC from the Terminal Block Adapter
In a 1U rack mount bracket installation, it is sometimes preferable to use 48V DC power
through directly secured wires as opposed to the DC power adapter.The Terminal Block
Adapter fastens to the back of the EtherNID to provide such an installation.
To ground the Terminal Block Adapter, use a small wrench to tighten the bolt around the
grounding screw, located at the bottom right on the back of the Terminal Block Adapter, to
secure the grounding lug.

2: Hardware installation Powering the EtherNID
19
48V DC via discrete power cord
It is possible to power units with a custom built 48V DC power cable. When powered in this
manner, the unit must be installed horizontally to meet all applicable safety
regulations. Therefore, supported mounting options are desktop mounting or 1 or 2 unit rack
mounting. Wall mounting is not allowed.
On older models of the EtherNID™, the +/- 48V Return is common to both Feed A and Feed
B, whereas other models will have an isolated Return A and Return B.
To locate your serial number, please refer to the sticker on the Rear Panel of the unit. If the
serial number starts with:
• I006-… or less then the unit has a common +/- 48V Return
• P004-… or less then the unit has a common +/- 48V Return
• I007-… or more then the unit has an isolated +/- 48V Return A and Return B
• P005-… or more then the unit has an isolated +/- 48V Return A and Return B
The following diagram depicts the pin-out of the white +/- 48V connector on the
rear panel of the EtherNID™:
Common +/- 48V Return Isolated +/- 48V Return A and B
If an EtherNID™ with a Common +/- 48V Return is being used with the Terminal Block Adapter, then the
two +/- 48V Return screws corresponding to the “RTN FEED A” and “RTN FEED B” on the Terminal
Block Adapter must be tied together:
Terminal Block Adapter with Return Feeds tied
The power source (+/-40 to +/-57 V DC) must be limited by a 0.5A/48V fast acting fuse or
equivalent (Littelfuse 0217.500 0.50A). There should be one fuse per power feed.
Warning: Disconnect all power sources (feed A and feed B) when servicing. Removing fuses
can be used as a disconnect method.
Warning: Fuses must be installed on the live wire(s) and not on the grounded wire(s).

2: Hardware installation Restarting
20
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.