Basic Ethernet Demarcation Device: The Access Company

OPERATION MANUAL
INSTALLATION AND
ETX-102
Basic Ethernet Demarcation Device
Version 3.8
The Access Company

ETX-102
Basic Ethernet Demarcation Device
Version 3.8
Installation and Operation Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD").
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the ETX-102 and
any software components contained therein are proprietary products of RAD protected under
international copyright law and shall be and remain solely with RAD.
The ETX-102 product name is owned by RAD. No right, license, or interest to such trademark is
granted hereunder, and you agree that no such right, license, or interest shall be asserted by
you with respect to such trademark. The RAD name, logo, logotype, and the terms EtherAccess,
TDMoIP and TDMoIP Driven, and the product names Optimux and IPmux, are registered
trademarks of RAD Data Communications Ltd. All other trademarks are the property of their
respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
ETX-102. You are prohibited from, and shall not, directly or indirectly, develop, market,
distribute, license, or sell any product that supports substantially similar functionality as the
ETX-102, based on or derived in any way from the ETX-102. Your undertaking in this paragraph
shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the ETX-102 package and shall continue until
terminated. RAD may terminate this Agreement upon the breach by you of any term hereof.
Upon such termination by RAD, you agree to return to RAD the ETX-102 and all copies and
portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters North America Headquarters

RAD Data Communications Ltd. RAD Data Communications Inc.
24 Raoul Wallenberg Street 900 Corporate Drive

Tel Aviv 69719, Israel Mahwah, NJ 07430, USA
Tel: 972-3-6458181 Tel: (201) 5291100, Toll free: 1-800-4447234
Fax: 972-3-6498250, 6474436 Fax: (201) 5295777
E-mail: market@rad.com E-mail: market@rad.com
20042011 RAD Data Communications Ltd. Publication No. 377-200-0(/1#

Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the ETX-102 to be delivered hereunder shall
be free of defects in material and workmanship under normal use and service for a period of
twelve (12) months following the date of shipment to DISTRIBUTOR.
If, during the warranty period, any component part of the equipment becomes defective by
reason of material or workmanship, and DISTRIBUTOR immediately notifies RAD of such defect,
RAD shall have the option to choose the appropriate corrective action: a) supply a replacement
part, or b) request return of equipment to its plant for repair, or c) perform necessary repair at
the equipment's location. In the event that RAD requests the return of equipment, each party
shall pay one-way shipping costs.
RAD shall be released from all obligations under its warranty in the event that the equipment has
been subjected to misuse, neglect, accident or improper installation, or if repairs or
modifications were made by persons other than RAD's own authorized service personnel, unless
such repairs by others were made with the written consent of RAD.
The above warranty is in lieu of all other warranties, expressed or implied. There are no
warranties which extend beyond the face hereof, including, but not limited to, warranties of
merchantability and fitness for a particular purpose, and in no event shall RAD be liable for
consequential damages.
RAD shall not be liable to any person for any special or indirect damages, including, but not
limited to, lost profits from any cause whatsoever arising from or in any way connected with the
manufacture, sale, handling, repair, maintenance or use of the ETX-102, and in no event shall
RAD's liability exceed the purchase price of the ETX-102.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to ETX-102 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the ETX-102 are provided "as is" and without warranty of any kind.
RAD disclaims all warranties including the implied warranties of merchantability and fitness for a
particular purpose. RAD shall not be liable for any loss of use, interruption of business or
indirect, special, incidental or consequential damages of any kind. In spite of the above RAD
shall do its best to provide error-free software products and shall offer free Software updates
during the warranty period under this Agreement.
RAD's cumulative liability to you or any other party for any loss or damages resulting from any
claims, demands, or actions arising out of or relating to this Agreement and the ETX-102 shall
not exceed the sum paid to RAD for the purchase of the ETX-102. In no event shall RAD be liable
for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if
RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal
waste at the end of its life cycle. Upon termination of the units use,
customers should provide for its collection for reuse, recycling or other form
of environmentally conscientious disposal.
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or service
personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the
product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building
protective ground bus.
Some products may be equipped with a laser diode. In such cases, a label with the
laser class and other warnings as applicable will be attached near the optical
transmitter. The laser warning symbol may be also attached.
Warning Please observe the following precautions:
Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the transmitter.
Do not attempt to adjust the laser drive current.
Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
The use of optical devices with the equipment will increase eye hazard.
Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
Handling Energized Products
General Safety Practices

Do not touch or tamper with the power supply when the power cord is connected. Line voltages
may be present inside certain products even when the power switch (if installed) is in the OFF
position or a fuse is blown. For DC-powered products, although the voltages levels are usually
not hazardous, energy hazards may still exist.
Before working on equipment connected to power lines or telecommunication lines, remove
jewelry or any other metallic object that may come into contact with energized parts.
Unless otherwise specified, all products are intended to be grounded during normal use.
Grounding is provided by connecting the mains plug to a wall socket with a protective ground
terminal. If a ground lug is provided on the product, it should be connected to the protective
ground at all times, by a wire with a diameter of 18 AWG or wider. Rack-mounted equipment
should be mounted only in grounded racks and cabinets.
Always make the ground connection first and disconnect it last. Do not connect
telecommunication cables to ungrounded equipment. Make sure that all other cables are
disconnected before disconnecting the ground.
Some products may have panels secured by thumbscrews with a slotted head. These panels may
cover hazardous circuits or parts, such as power supplies. These thumbscrews should therefore
always be tightened securely with a screwdriver after both initial installation and subsequent
access to the panels.
Connecting AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be
readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF
position. When connecting the DC supply wires, first connect the ground wire to the
corresponding terminal, then the positive pole and last the negative pole. Switch the circuit
breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Connecting Data and Telecommunications Cables

Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port
differs from the standard one, a notice will be given in the manual.
Ports Safety Status
V.11, V.28, V.35, V.36, RS-530, X.21, SELV Safety Extra Low Voltage:
10 BaseT, 100 BaseT, Unbalanced E1, Ports which do not present a safety hazard. Usually
E2, E3, STM, DS-2, DS-3, S-Interface up to 30 VAC or 60 VDC.
ISDN, Analog voice E&M
xDSL (without feeding voltage), TNV-1 Telecommunication Network Voltage-1:
Balanced E1, T1, Sub E1/T1 Ports whose normal operating voltage is within the
limits of SELV, on which overvoltages from
telecommunications networks are possible.
FXS (Foreign Exchange Subscriber) TNV-2 Telecommunication Network Voltage-2:
Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are not possible. These
ports are not permitted to be directly connected to
external telephone and data lines.
FXO (Foreign Exchange Office), xDSL TNV-3 Telecommunication Network Voltage-3:
(with feeding voltage), U-Interface Ports whose normal operating voltage exceeds the
ISDN limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are possible.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution To reduce the risk of fire, use only No. 26 AWG or larger telecommunication line
cords.
Attention Pour rduire les risques sincendie, utiliser seulement des conducteurs de
tlcommunications 26 AWG ou de section suprieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In
such cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Electromagnetic Compatibility (EMC)

The equipment is designed and approved to comply with the electromagnetic regulations of
major regulatory bodies. The following instructions may enhance the performance of the
equipment and will provide better protection against excessive emission and better immunity
against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially
for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be
installed on certain cables. In such cases, special instructions are provided in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines
is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal
conversion loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with
plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines.
Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive
wrist strap.
FCC-15 User Information
This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Canadian Emission Requirements

This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulation.
Cet appareil numrique de la classe A respecte toutes les exigences du Rglement sur le matriel
brouilleur du Canada.
Warning per EN 55022 (CISPR-22)

Warning This is a class A product. In a domestic environment, this product may cause radio
interference, in which case the user will be required to take adequate measures.
Avertissement Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel, cet
appareil peut provoquer des brouillages radiolectriques. Dans ces cas, il peut tre
demand lutilisateur de prendre les mesures appropries.
Achtung Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In Wohngebieten

knnen beim Betrieb dieses Gertes Rundfunkstrrungen auftreten, fr deren
Behebung der Benutzer verantwortlich ist.
Mise au rebut du produit
Franais
Afin de faciliter la rutilisation, le recyclage ainsi que d'autres formes de

rcupration d'quipement mis au rebut dans le cadre de la protection de
l'environnement, il est demand au propritaire de ce produit RAD de ne pas
mettre ce dernier au rebut en tant que dchet municipal non tri, une fois
que le produit est arriv en fin de cycle de vie. Le client devrait proposer des
solutions de rutilisation, de recyclage ou toute autre forme de mise au rebut
de cette unit dans un esprit de protection de l'environnement, lorsqu'il aura
fini de l'utiliser.
Instructions gnrales de scurit

Les instructions suivantes servent de guide gnral d'installation et d'opration scurises des
produits de tlcommunications. Des instructions supplmentaires sont ventuellement
indiques dans le manuel.
Symboles de scurit
Ce symbole peut apparaitre sur l'quipement ou dans le texte. Il indique des risques
potentiels de scurit pour l'oprateur ou le personnel de service, quant
l'opration du produit ou sa maintenance.
Avertissement
Danger de choc lectrique ! Evitez tout contact avec la surface marque tant que le
produit est sous tension ou connect des lignes externes de tlcommunications.
Mise la terre de protection : la cosse ou la borne marque devrait tre connecte

la prise de terre de protection du btiment.
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas, une
Franais
tiquette indiquant la classe laser ainsi que d'autres avertissements, le cas chant,
sera jointe prs du transmetteur optique. Le symbole d'avertissement laser peut
aussi tre joint.
Avertissement
Veuillez observer les prcautions suivantes :
Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre
optique est intact et qu'il est connect au transmetteur.
Ne tentez pas d'ajuster le courant de la commande laser.
N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans
terminaison et n'observez pas directement un rayon laser.
L'usage de priphriques optiques avec l'quipement augmentera le risque pour
les yeux.
L'usage de contrles, ajustages ou procdures autres que celles spcifies ici
pourrait rsulter en une dangereuse exposition aux radiations.
ATTENTION : Le rayon laser peut tre invisible !
Les utilisateurs pourront, dans certains cas, insrer leurs propres metteurs-rcepteurs Laser SFP
dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas tre tenue responsable de
tout dommage pouvant rsulter de l'utilisation d'metteurs-rcepteurs non conformes. Plus
particulirement, les utilisateurs sont avertis de n'utiliser que des produits approuvs par
l'agence et conformes la rglementation locale de scurit laser pour les produits laser de
classe 1.
Respectez toujours les prcautions standards de scurit durant l'installation, l'opration et la
maintenance de ce produit. Seul le personnel de service qualifi et autoris devrait effectuer
l'ajustage, la maintenance ou les rparations de ce produit. Aucune opration d'installation,
d'ajustage, de maintenance ou de rparation ne devrait tre effectue par l'oprateur ou
l'utilisateur.
Manipuler des produits sous tension
Rgles gnrales de scurit

Ne pas toucher ou altrer l'alimentation en courant lorsque le cble d'alimentation est branch.
Des tensions de lignes peuvent tre prsentes dans certains produits, mme lorsque le
commutateur (s'il est install) est en position OFF ou si le fusible est rompu. Pour les produits
aliments par CC, les niveaux de tension ne sont gnralement pas dangereux mais des risques
de courant peuvent toujours exister.
Avant de travailler sur un quipement connect aux lignes de tension ou de tlcommunications,
retirez vos bijoux ou tout autre objet mtallique pouvant venir en contact avec les pices sous
tension.
Sauf s'il en est autrement indiqu, tous les produits sont destins tre mis la terre durant
l'usage normal. La mise la terre est fournie par la connexion de la fiche principale une prise
murale quipe d'une borne protectrice de mise la terre. Si une cosse de mise la terre est
fournie avec le produit, elle devrait tre connecte tout moment une mise la terre de
protection par un conducteur de diamtre 18 AWG ou plus. L'quipement mont en chssis ne
devrait tre mont que sur des chssis et dans des armoires mises la terre.
Branchez toujours la mise la terre en premier et dbranchez-la en dernier. Ne branchez pas des
cbles de tlcommunications un quipement qui n'est pas mis la terre. Assurez-vous que
tous les autres cbles sont dbranchs avant de dconnecter la mise la terre.
Connexion au courant du secteur
Franais
Assurez-vous que l'installation lectrique est conforme la rglementation locale.

Branchez toujours la fiche de secteur une prise murale quipe d'une borne protectrice de mise
la terre.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de
court-circuit dpassant 35A (40A aux Etats-Unis et Canada).
Branchez toujours le cble d'alimentation en premier l'quipement puis la prise murale. Si un
commutateur est fourni avec l'quipement, fixez-le en position OFF. Si le cble d'alimentation ne
peut pas tre facilement dbranch en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est install dans l'installation du btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si le systme de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par
rapport la mise la terre. Tout ple doit tre mis la terre en externe.
A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient
tre prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques
d'incendie.
Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que
l'installation est conforme la rglementation locale.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de
court-circuit dpassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le
en position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le
conducteur de mise la terre la borne correspondante, puis le ple positif et en dernier, le
ple ngatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du
btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC
est flottante.
Declaration of Conformity
Manufacturer's Name: RAD Data Communications Ltd.
Manufacturer's Address: 24 Raoul Wallenberg St.

Tel Aviv 69719
Israel
Declares that the product:
Product Name: ETX-102
Conforms to the following standard(s) or other normative document(s):
EMC EN 55022:2006 + Information technology equipment Radio disturbance

A1:2007 characteristics Limits and methods of measurement.
EN 55024:1998 + Information technology equipment Immunity characteristics

A1:2001, A2:2003 Limits and methods of measurement.
EN 61000-3-2:2006 Electromagnetic compatibility (EMC) - Part 3-2: Limits

Limits for harmonic current emissions (equipment input current
16A per phase)
EN 61000-3-3:1995 Electromagnetic compatibility (EMC) Part 3-3: Limits

+ A1:2001, A2:2005 Limitation of voltage changes, voltage fluctuations and flicker in
public low-voltage supply systems, for equipment with rated
current 16A per phase and not subject to conditional
connection.
Safety EN 60950-1:2005 Information technology equipment Safety Part 1:

General requirements.
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 2004/108/EC, the Low
Voltage Directive 2006/95/EC and the R&TTE Directive 99/5/EC for wired equipment. The product
was tested in a typical configuration.
Tel Aviv, 15 July 2010
Nathaniel Shomroni
Approvals Coordinator
European RAD Data Communications GmbH

Contact: Otto-Hahn-Str. 28-30, 85521 Ottobrunn-Riemerling, Germany
Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
Analog A continuous wave or signal (such as human voice).
ANSI American National Standards Institute.
AWG The American Wire Gauge System, which specifies wire width.
Balanced A transmission line in which voltages on the two conductors are

equal in magnitude, but opposite in polarity, with respect to
ground.
Bandwidth The range of frequencies passing through a given circuit. The

greater the bandwidth, the more information can be sent through
the circuit in a given amount of time.
Baud Unit of signaling speed equivalent to the number of discrete

conditions or events per second. If each signal event represents
only one bit condition, baud rate equals bps (bits per second).
Best Effort A QoS class in which no specific traffic parameters and no

absolute guarantees are provided.
Bit The smallest unit of information in a binary system. Represents

either a one or zero (1 or 0).
Bit A process used in time division multiplexing where individual bits

Interleaving/Multiplexing from different lower speed channel sources are combined (one bit
from one channel at a time) into one continuous higher speed bit
stream.
bps (Bits Per Second) A measure of data transmission rate in serial transmission.
Bridge A device interconnecting local area networks at the OSI data link
layer, filtering and forwarding frames according to media access
control (MAC) addresses.
Buffer A storage device. Commonly used to compensate for differences

in data rates or event timing when transmitting from one device to
another. Also used to remove jitter.
Bus A transmission path or channel. A bus is typically an electrical

connection with one or more conductors, where all attached
devices receive all transmissions at the same time.
Byte A group of bits (normally 8 bits in length).

Carrier A continuous signal at a fixed frequency that is capable of being
modulated with a second (information carrying) signal.
Cell The 53-byte basic information unit within an ATM network. The
user traffic is segmented into cells at the source and reassembled
at the destination. An ATM cell consists of a 5-byte ATM header
and a 48-byte ATM payload, which contains the user data.
Channel A path for electrical transmission between two or more points.

Also called a link, line, circuit or facility.
Clock A term for the source(s) of timing signals used in synchronous

transmission.
Data Information represented in digital form, including voice, text,

facsimile and video.
Data Link Layer Layer 2 of the OSI model. The entity, which establishes, maintains,
and releases data-link connections between elements in a
network. Layer 2 is concerned with the transmission of units of
information, or frames, and associated error checking.
dB (Decibel) A unit used to measure relative increase or decrease in power,

voltage or current, using a logarithmic scale.
dBm A measure of power in communications: the decibel in reference

to one milliwatt (0 dBm = 1 milliwatt and -30 dBm = .001
milliwatt).
Decibel See dB.
Diagnostics The detection and isolation of a malfunction or mistake in a

communications device, network or system.
Digital The binary (1 or 0) output of a computer or terminal. In data

communications, an alternating, non-continuous (pulsating) signal.
E3 The European standard for high speed digital transmission,

operating at 34 Mbps.
Encapsulation Encapsulating data is a technique used by layered protocols in

which a low level protocol accepts a message from a higher level
protocol, then places it in the data portion of the lower-level
frame. The logistics of encapsulation require that packets traveling
over a physical network contain a sequence of headers.
Ethernet A local area network (LAN) technology which has extended into
the wide area networks. Ethernet operates at many speeds,
including data rates of 10 Mbps (Ethernet), 100 Mbps (Fast
Ethernet), 1,000 Mbps (Gigabit Ethernet), 10 Gbps, 40 Gbps, and
100 Gbps.
Ethernet OAM Ethernet operation, administration and maintenance (OAM) are a
set of standardized protocols for measuring and controlling
network performance. There are two layers of Ethernet OAM:
Service OAM (provides end-to-end connectivity fault management
per customer service instance, even in multi-operator networks)
and Link or Segment OAM (detailed monitoring and
troubleshooting of an individual physical or emulated link).
Flow Control A congestion control mechanism that results in an ATM system

implementing flow control.
Frame A logical grouping of information sent as a link-layer unit over a

transmission medium. The terms packet, datagram, segment, and
message are also used to describe logical information groupings.
Framing At the physical and data link layers of the OSI model, bits are fit
into units called frames. Frames contain source and destination
information, flags to designate the start and end of the frame,
plus information about the integrity of the frame. All other
information, such as network protocols and the actual payload of
data, is encapsulated in a packet, which is encapsulated in the
frame.
Full Duplex A circuit or device permitting transmission in two directions

(sending and receiving) at the same time.
FXO (Foreign Exchange A voice interface, emulating a PBX extension, as it appears to the
Office) CO (Central Office) for connecting a PBX extension to a
multiplexer.
FXS (Foreign Exchange A voice interface, emulating the extension interface of a PBX (or
Subscriber) subscriber interface of a CO) for connecting a regular telephone
set to a multiplexer.
Gateway Gateways are points of entrance and exit from a communications

network. Viewed as a physical entity, a gateway is that node that
translates between two otherwise incompatible networks or
network segments. Gateways perform code and protocol
conversion to facilitate traffic between data highways of differing
architecture.
Half Duplex A circuit or device capable of transmitting in two directions, but

not at the same time.
Impedance The combined effect of resistance, inductance and capacitance on

a transmitted signal. Impedance varies at different frequencies.
Interface A shared boundary, defined by common physical interconnection

characteristics, signal characteristics, and meanings of exchanged
signals.
IP Address Also known as an Internet address. A unique string of numbers

that identifies a computer or device on a TCP/IP network. The
format of an IP address is a 32-bit numeric address written as four
numbers from 0 to 255, separated by periods (for example,
1.0.255.123).
Jitter The deviation of a transmission signal in time or phase. It can
introduce errors and loss of synchronization in high speed
synchronous communications.
Laser A device that transmits an extremely narrow and coherent beam

of electromagnetic energy in the visible light spectrum. Used as a
light source for fiber optic transmission (generally more expensive,
shorter lived, single mode only, for greater distances than LED).
Loopback A type of diagnostic test in which the transmitted signal is

returned to the sending device after passing through all or part of
a communications link or network.
Manager An application that receives Simple Network Management Protocol

(SNMP) information from an agent. An agent and manager share a
database of information, called the Management Information Base
(MIB). An agent can use a message called a traps-PDU to send
unsolicited information to the manager. A manager that uses the
RADview MIB can query the RAD device, set parameters, sound
alarms when certain conditions appear, and perform other
administrative tasks.
Multiplexer At one end of a communications link, a device that combines

several lower speed transmission channels into a single high speed
channel. A multiplexer at the other end reverses the process.
Sometimes called a mux. See Bit Interleaving/Multiplexing.
Network (1) An interconnected group of nodes. (2) A series of points,

nodes, or stations connected by communications channels; the
collection of equipment through which connections are made
between data stations.
Node A point of interconnection to a network.
Packet An ordered group of data and control signals transmitted through

a network, as a subset of a larger message.
parameters Parameters are often called arguments, and the two words are
used interchangeably. However, some computer languages such as
C define argument to mean actual parameter (i.e., the value), and
parameter to mean formal parameter. In RAD CLI, parameter
means formal parameter, not value.
Payload The 48-byte segment of the ATM cell containing user data. Any
adaptation of user data via the AAL will take place within the
payload.
Physical Layer Layer 1 of the OSI model. The layer concerned with electrical,
mechanical, and handshaking procedures over the interface
connecting a device to the transmission medium.
Port The physical interface to a computer or multiplexer, for connection

of terminals and modems.
Prioritization Also called CoS (class of service), classifies traffic into categories
such as high, medium, and low. The lower the priority, the more
drop eligible is a packet. When the network gets busy,
prioritization ensures critical or high-rated traffic is passed first,
and packets from the lowest categories may be dropped.
Protocol A formal set of conventions governing the formatting and relative

timing of message exchange between two communicating
systems.
RADIUS (Remote An authentication, authorization and accounting protocol for

Authentication Dial-In applications such as network access or IP mobility. Many network
User Service) services require the presentation of security credentials (such as a
username and password or security certificate) in order to connect
to the network. Before access to the network is granted, this
information is passed to a network access server (NAS) device
over the link-layer protocol, then to a RADIUS server over the
RADIUS protocol. The RADIUS server checks that the information is
correct using authentication schemes like PAP, CHAP or EAP.
Router An interconnection device that connects individual LANs. Unlike

bridges, which logically connect at OSI Layer 2, routers provide
logical paths at OSI Layer 3. Like bridges, remote sites can be
connected using routers over dedicated or switched lines to create
WANs.
Routing The process of selecting the most efficient circuit path for a
message.
Serial Transmission A common mode of transmission, where the character bits are
sent sequentially one at a time instead of in parallel.
SFP (Small Form-factor A compact optical transceiver used in optical communications. It

Pluggable) interfaces a network device (a switch, router or similar device) to a
fiber optic or unshielded twisted pair networking cable. It is a
popular industry format.
Single Mode Describing an optical wave-guide or fiber that is designed to

propagate light of only a single wavelength (typically 5-10 microns
in diameter).
Synchronous Transmission in which data bits are sent at a fixed rate, with the
Transmission transmitter and receiver synchronized.
T1 A digital transmission link with a capacity of 1.544 Mbps used in

North America. Typically channelized into 24 DS0s, each capable of
carrying a single voice conversation or data stream. Uses two pairs
of twisted pair wires.
Telnet The virtual terminal protocol in the Internet suite of protocols. It

lets users on one host access another host and work as terminal
users of that remote host. Instead of dialing into the computer,
the user connects to it over the Internet using Telnet. When
issuing a Telnet session, it connects to the Telnet host and logs in.
The connection enables the user to work with the remote machine
as though a terminal was connected to it.
VLAN-Aware A device that is doing the Layer 2 bridging according to the VLAN
tag in addition to the standard bridging parameters. A VLAN-aware
device will not strip or add any VLAN header.
VLAN Stacking A technique that lets carriers offer multiple virtual LANs over a
single circuit. In essence, the carrier creates an Ethernet virtual
private network to tunnel customer VLANs across its WAN; this
helps avoid name conflicts among customers of service providers
who connect to the carrier. Stacking works by assigning two VLAN
IDs to each frame header. One is a "backbone" VLAN ID used by
the service provider; the other one has up to 4,096 unique 802.1Q
VLAN tags.
Quick Start Guide
Installation of ETX-102 should be carried out only by an experienced technician. If
you are familiar with ETX-102, use this guide to prepare the units for operation.
1. Installing the Unit
Connecting the Interfaces

1. Insert the rear end of the SFP into the socket, and push slowly backwards to
mate the connectors until the SFP clicks into place. If you feel resistance
before the connectors are fully mated, retract the SFP using the latch wire as
a pulling handle, and then repeat the procedure.
2. Connect the LANs to the appropriate network or user RJ-45 connectors.
3. Connect the control terminal to the rear panel CONTROL connector.
or
Connect a Telnet host, or a PC running a Web browsing application to one of
the Ethernet ports.
Note A valid IP address must be assigned to ETX-102 to allow Telnet or Web

management.
Connecting the Power

Connect the power cable to the power connector on the ETX-102 rear panel.
The unit has no power switch. Operation starts when the power is applied
to the rear panel power connector.
2. Configuring the Unit

Configure ETX-102 to the desired operation mode via an ASCII terminal connected
to the rear panel CONTROL port. Alternatively, you can manage
ETX-102 over Telnet or a PC running a Web browsing application via one of the
Ethernet ports.
Starting a Terminal Session

To start a terminal session:
1. Turn on the control terminal PC and set its default port parameters to
115,200 baud; 8 bits/character; 1 stop bit; no parity.
ETX-102 Ver. 3.8 Configuring the Unit 1

Quick Start Guide Installation and Operation Manual
2. Set the terminal emulator to ANSI VT100 emulation (for optimal view of
system menus).
3. Enter your user name and password and proceed with the management
session.
Note The ETX-102 default user name is user (case-sensitive), default password is
1234.
Configuring the Unit Parameters

The management software provides a Quick Setup menu, which includes the most
basic parameters necessary for configuration.
To configure ETX-102:
From the Quick Setup menu (Main > Configuration > Quick Setup), configure
the following parameters:
Host IP address
Host IP mask
Default gateway
Host tagging
Host VLAN ID
VLAN mode
Forwarding mode
DHCP client.
2 Configuring the Unit ETX-102 Ver. 3.8

Contents
Chapter 1. Introduction
1.1 Overview.................................................................................................................... 1-1
Device Options ....................................................................................................... 1-1
Applications ............................................................................................................ 1-1
Features ................................................................................................................. 1-2
1.2 Physical Description ................................................................................................... 1-5
1.3 Functional Description................................................................................................ 1-6
Network Port Redundancy ...................................................................................... 1-6
Bridge..................................................................................................................... 1-8
Fault Propagation ................................................................................................. 1-11
Diagnostic Loopbacks ........................................................................................... 1-12
1.4 Technical Specifications............................................................................................ 1-13
Chapter 2. Installation and Setup

2.1 Site Requirements and Prerequisites .......................................................................... 2-1
2.2 Package Contents ...................................................................................................... 2-2
2.3 Mounting the Unit ...................................................................................................... 2-2
2.4 Installing SFP Modules ................................................................................................ 2-2
2.5 Connecting to the Ethernet Equipment ....................................................................... 2-3
2.6 Connecting to the ASCII Terminal ................................................................................ 2-4
2.7 Connecting to Power .................................................................................................. 2-5
Connecting AC Power .............................................................................................. 2-5
Connecting DC Power.............................................................................................. 2-5
Chapter 3. Operation
3.1 Turning On the Unit ................................................................................................... 3-1
3.2 Front Panel Indicators ................................................................................................ 3-2
3.3 Default Settings ......................................................................................................... 3-2
3.4 Configuration and Management Alternatives .............................................................. 3-7
Working with Terminal ............................................................................................ 3-7
Working with Web Terminal................................................................................... 3-10
Menu Maps ........................................................................................................... 3-12
3.5 Turning Off the Unit ................................................................................................. 3-14
Chapter 4. Configuration
4.1 Configuring for Management ...................................................................................... 4-1
Configuring IP Host Parameters ............................................................................... 4-1
Entering Device Information .................................................................................... 4-3
Configuring Communities ........................................................................................ 4-4
Configuring the Host Encapsulation ......................................................................... 4-5
Configuring the Network Managers ......................................................................... 4-6
Configuring SNMPv3 ................................................................................................ 4-7
Controlling Management Access ............................................................................ 4-13
Configuring Control Port Parameters ..................................................................... 4-16
4.2 Configuring for Operation ........................................................................................ 4-17
Configuring the Link Protection ............................................................................. 4-17
Configuring Ethernet Ports at the Physical Layer.................................................... 4-19
ETX-102 Ver. 3.8 i

Table of Contents Installation and Operation Manual
Configuring the Bridge .......................................................................................... 4-22

Configuring OAM ................................................................................................... 4-30
Configuring Quality of Service (QoS) ..................................................................... 4-36
4.3 Additional Tasks ....................................................................................................... 4-40
Displaying Inventory.............................................................................................. 4-41
Displaying Status .................................................................................................. 4-41
Setting the Date, Time and NTP Server Parameters................................................ 4-49
Configuring User Access ........................................................................................ 4-50
Configuring Syslog Parameters .............................................................................. 4-51
Transferring Software and Configuration Files ....................................................... 4-52
Swapping Software Files ....................................................................................... 4-54
Resetting ETX-102 ................................................................................................ 4-54
Chapter 5. Diagnostics and Troubleshooting

5.1 Monitoring Performance ............................................................................................. 5-1
Displaying End-to-End Statistics .............................................................................. 5-1
Displaying Ethernet Statistics .................................................................................. 5-3
5.2 Handling Events and Traps ......................................................................................... 5-6
Displaying Events .................................................................................................... 5-6
Configuring Event Reporting (RMON Counters) ........................................................ 5-7
Clearing Events ....................................................................................................... 5-9
Masking Alarm Traps ............................................................................................. 5-12
Configuring the Trap Delay .................................................................................... 5-12
5.3 Testing ETX-102 ....................................................................................................... 5-13
Running a Ping Test .............................................................................................. 5-13
Tracing the Route ................................................................................................. 5-14
Running Loopbacks ............................................................................................... 5-14
Testing the Cables ................................................................................................ 5-17
Running the VLAN Test ......................................................................................... 5-18
5.4 Frequently Asked Questions ..................................................................................... 5-19
5.5 Technical Support .................................................................................................... 5-20
Chapter 6. Software Upgrade

6.1 Compatibility Requirements ........................................................................................ 6-1
6.2 Impact ....................................................................................................................... 6-1
6.3 Software Upgrade Options ......................................................................................... 6-1
6.4 Prerequisites .............................................................................................................. 6-2
Software Files ......................................................................................................... 6-2
System Requirements ............................................................................................. 6-2
6.5 Upgrading ETX-102 Software via the File Utilities Menu .............................................. 6-2
Verifying the Host Parameters ................................................................................ 6-3
Pinging the PC ........................................................................................................ 6-4
Activating the TFTP Server ....................................................................................... 6-4
Downloading the New Software Release File to ETX-102 ......................................... 6-6
6.6 Upgrading ETX-102 Software via the Boot Menu ......................................................... 6-7
Using the XMODEM Protocol ................................................................................... 6-8
Using TFTP ............................................................................................................ 6-10
6.7 Verifying Upgrade Results ........................................................................................ 6-11
Chapter 7. Application Tutorial

7.1 Configuring the VLAN Stacking Application .................................................................. 7-1
ii ETX-102 Ver. 3.8

Installation and Operation Manual Table of Contents
Configuration Sequence .......................................................................................... 7-2

Configuring System Parameters............................................................................... 7-2
Configuring Ethernet Interfaces at the Physical Layer .............................................. 7-4
Configuring the Bridge ............................................................................................ 7-4
Configuring QoS...................................................................................................... 7-6
7.2 Configuring a VLAN-Aware Application ........................................................................ 7-7
Configuration Sequence .......................................................................................... 7-8
Configuring System Parameters............................................................................... 7-9
Configuring Ethernet Interfaces at the Physical Layer .............................................. 7-9
Configuring the Bridge ............................................................................................ 7-9
Appendix A. Connector Wiring

Appendix B. Operation, Administration, and Maintenance (OAM)
ETX-102 Ver. 3.8 iii

Table of Contents Installation and Operation Manual
iv ETX-102 Ver. 3.8

Chapter 1
Introduction
1.1 Overview
ETX-102 is a carrier-class demarcation device owned and operated by the service
provider and installed at the customer premises, providing a demarcation point
between the private LAN and the operators network. ETX-102 offers flexible
network and user port combinations. The network ports support link aggregation
according to IEEE 802.3ad requirements. The user ports accept traffic, providing
different port-based services. At the physical level, ETX-102 supports
autonegotiation, flow control, and fault propagation. The unit can be managed
via a local terminal port, or via one of its Ethernet ports (inband management).
ETX-102 includes a DHCP client utility that obtains the IP address, IP mask, and
default gateway values.
Device Options
Several versions of the unit are available, offering different combinations of
Ethernet ports and enclosure types.
Ethernet ports:
Ports 1 and 2 Any standard Fast Ethernet SFP or built-in 10/100BaseT
Ports 36 Built-in 10/100BaseT.
Enclosure type Plastic (regular unit) or metal (temperature-hardened
version).
Applications
In a typical application ETX-102 provides Ethernet access to a packet-switched
network (Figure 1-1) or next generation SDH/SONET network Figure 1-2) over a
fiber optic local loop.
ETX-102 Ver. 3.8 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
Figure 1-1. Three Methods of Providing Managed Ethernet Services over a PSN
Figure 1-2. Providing Managed Ethernet Services over a Next-Generation SDH/SONET

Network
Features
Network Interface
ETX-102 includes two network ports. The network ports use industry-standard
SFP (Small Form-Factor Pluggable) hot-swappable optical transceivers. Refer to
the SFP data sheet for the complete list of the SFPs supported by ETX-102.
Alternatively, ETX-102 can be ordered with built-in RJ-45 ports supporting
autonegotiation and flow control
User Interface
ETX-102 user interfaces terminate in up to four built-in RJ-45 ports that support
autonegotiation and flow control.
Link Redundancy
The unit supports link aggregation (1+1) based on 802.3ad requirements.
Dual homing technology (1:1) allows ETX-102 to be connected to two different
upstream devices.
1-2 Overview ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 1 Introduction
Bridge
The bridge operates in VLAN-aware or VLAN-unaware mode, in accordance with
802.1Q. Learning and filtering can be enabled or disabled.
The unit can append a VLAN tag (provider VLAN) at user port ingress and remove
it at network port ingress. The provider VLAN includes provider VID and priority
(VLAN stacking).
QoS
ETX-102 supports traffic prioritization and rate limitation.
Traffic Classification and Prioritization

ETX-102 provides four priority queues for each user port. The traffic can be
classified and mapped into the priority queues according to the VLAN priority,
DSCP, IP TOS, or per port basis.
Rate Limitation
ETX-102 supports an egress rate limitation per port (network and user) and
ingress rate limitation per user port.
Fault Propagation
The unit provides the network-to-user fault propagation mechanism. When the
fault propagation is enabled, the user port shuts itself down when a link failure is
detected at the network port.
Management
Setup, monitoring and diagnostics tests can be performed using one of the
following methods:
Out-of-band via ASCII terminal connected to the V.24/RS-232 DCE control port
Inband management via one of the Ethernet ports, for network management
using Telnet or terminal Web-based application:
ETX-102 can be managed via a third-party SNMP-based NMS, using SNMPv3.
The ETX-102 device provides a user-friendly Web-based terminal management
system for remote device configuration and maintenance that is embedded into
ETX-102 and provided at no extra cost. It can be run from any standard Web
browser.
Inband Management
For the inband management, the host of ETX-102 can be configured to the
tagged or untagged operation:
When the host tagging is enabled, the host packets receive a VLAN tag,
creating a dedicated management VLAN.
When tagging is disabled, no traffic separation is performed and management
packets can be forwarded to the user port.
ETX-102 Ver. 3.8 Overview 1-3

Security
The following security protocols are provided by ETX-102 to ensure client-server
communication privacy and correct user authentication:
RADIUS (client authentication only)
SSL for Web-based management application
SSH for Secure Shell communication session
SNMPv3 for secure SNMP sessions.
Ethernet OAM
ETX-102 provides tools to monitor and troubleshoot an Ethernet network and
quickly detect failures. Two OAM types are provided:
End-to-end (path) based on IEEE 802.1ag and Y.1731 for continuity check,
non-intrusive loopback and performance management, including Frame Delay,
Frame Delay Variation, Frame Loss, Availability etc
Single segment (link) according to IEEE 802.3ah for remote management and
fault indication, including remote loopback, dying gasp, and MIB parameters
retrieval.
Appendix B provides a more detailed description of the OAM functions.
Remote Monitoring
The Syslog protocol is used by ETX-102 to generate and transport event
notification messages over IP networks to the central Syslog server. The Syslog
operation is compliant with the RFC 3164 requirements.
ETX-102 supports DDM (Digital Data Management) SFPs according to Sff-8472
Version 9.3.
DHCP Client
When enabled, the DHCP client of ETX-102 automatically requests an IP address,
IP mask and default gateway from the DHCP server. In addition, ETX-102
automatically defines a network manager with a valid IP address and subnet
mask.
Statistics Collection
ETX-102 collects Ethernet performance statistics for the physical layers of the
network/user ports, OAM flows and VLANs.
In addition to the regular statistics collection, ETX-102 allows you to receive
reports when one of the available counters (physical layer or end-to-end OAM)
rise above or drop below the set thresholds within the specified sampling period
of time. These reports can be sent as SNMP traps to the defined network
management stations and/or be written to the event log.
Dying Gasp
Some of the ETX-102 units feature a dying gasp mechanism. If a power failure
occurs, ETX-102 sends traps to the defined network management stations,
informing the failure.
1-4 Overview ETX-102 Ver. 3.8

Network Time Protocol

The Network Time Protocol (NTP) provides the means of synchronizing all
managed elements across the network to a reliable clock source. ETX-102
supports the client side of the NTP v.3, based on RFC 1305.
Diagnostic Tools
A built-in ping utility allows checking IP connectivity by pinging remote IP hosts.
The Trace Route application can quickly trace a route from ETX-102 to any other
network device.
Loopbacks can be closed on any of the ETX-102 ports. Only one loopback can be
active at a time. Layer-2 loopback with MAC address swapping enables
end-to-end connectivity verification.
The quality of the copper cables, connectors and terminations can be checked by
running a Virtual Cable Test (VCT). During the test, ETX-102 transmits a signal of
known amplitude (+1V) down each of the two pairs of an attached cable, testing
the Rx and Tx pairs sequentially. The signal travels down the cable until it reflects
off of a cable imperfection. By measuring the magnitude of the reflection and the
time it takes for the reflection to come back, ETX-102 estimates the approximate
distance to the location of a cable break or short.
1.2 Physical Description

Figure 1-3 shows a 3D view of a typical ETX-102 unit.
Figure 1-3. ETX-102, 3D View

The front panel includes several LEDs that display the status of power, Ethernet
links, and alarms. For a detailed description of the front panel, see Chapter 3.
The rear panel includes AC/DC power connector, network and user Ethernet ports,
and V.24 terminal connector. The ETX-102 rear panel is described in greater detail
in Chapter 2.
ETX-102/H is a temperature-hardened version intended for industrial installations.
It requires temperature-hardened SFP transceivers.
ETX-102 Ver. 3.8 Physical Description 1-5

1.3 Functional Description
Network Port Redundancy

The two network interfaces can be configured to operate either independently,
as two separate Ethernet interfaces, or used as a single Ethernet interface with
line redundancy.
Link aggregation mode in accordance with IEEE 802.3ad (without LACP). This
mode inherently provides redundancy: if one of the Gigabit Ethernet ports
fails, the traffic is transmitted on the other.
1:1 bidirectional protection (redundancy) mode. In this mode, at any time
only one of the ports is actively carrying traffic. With 1:1 bidirectional
redundancy, the recovery mode (revertive or non-revertive), and the
restoration time in the revertive mode, can be selected in accordance with
the application requirements.
Using Link Aggregation

The two network Ethernet ports can be operated as a single logical interface,
using link aggregation in accordance with IEEE 802.3ad without LACP (Link
Aggregation Control Protocol). In the virtual link group only one link transmits at a
time. If a failure occurs on the transmitting link, ETX-102 switches to the standby
link in the group. The flip is performed by reassigning destination ports.
With link aggregation, the two network ports serve as a single logical interface.
The two ports must be connected to the same switch/router, as shown in
Figure 1-4.
Figure 1-4. Link Aggregation Redundancy Mode

Using link aggregation inherently provides redundancy, because if one of the
network ports fails, the other can continue transferring traffic. Therefore, link
aggregation per IEEE 802.3ad has inherent APS (Automatic Protection Switching)
characteristics.
Failure of one of the links is detected by sensing the loss of valid signals at a
port, in which case the whole traffic is sent through the remaining port. The
switching time is less than a second.
Link aggregation always provides revertive recovery, because that as soon as the
down port returns to normal, the full bandwidth is again available.
The equipment connected to the network ports must use compatible switching
criteria for redundancy to be available:
For networks using Layer 2 switching: the criterion is signal loss
1-6 Functional Description ETX-102 Ver. 3.8

For networks using Layer 3 routing: the router must support IEEE 802.3ad or
other link aggregation protocol that views the aggregated link as a single
logical interface.
As the two network ports serve as a single logical interface, the learning tables
do not change as a result of the interface flip.
Using 1:1 Bidirectional Redundancy

As an alternative to link aggregation, the two ETX-102 network ports can be
configured for 1:1 bidirectional mode (dual homing). With this mode, two
topologies can be used:
Connection of both network ports to the same switch/router, as shown in
Figure 1-4.
Connection of the network ports to different switch/routers, as shown in
Figure 1-5. The main advantage of this topology is its higher availability,
because each port can be routed along a different path through the network.
Figure 1-5. 1:1 Bidirectional Redundancy Mode (Dual Homing)

With 1:1 bidirectional redundancy mode, at any time only one of the ports is
actively carrying traffic, and the other port serves as the backup port. A RAD
proprietary redundancy algorithm, based on loss of signal, is used to detect line
failure. The protection switching (flipping) time is less than 1 second. It also
depends on the network relearning time or aging.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
Non-revertive mode ETX-102 will not automatically flip back after the failed
port returns to normal operation, but only when the currently used port fails,
or after a manual flip command.
Revertive mode ETX-102 will flip back to the original port when it returns to
normal operation. Flipping back can be delayed by specifying a restoration
time, during which alarms are ignored. As a result, ETX-102 starts evaluating
the criteria for protection switching (flipping) only after the restoration time
expires, thereby ensuring that another flip cannot occur before the specified
time expires.
When flip occurs, ETX-102 clears the MAC tables, enabling more efficient address
relearning.
Bridge
ETX-102 has a multi-port bridging capability handling up to six bridge ports. The
bridge supports VLAN-aware and VLAN-unaware modes of operation.
ETX-102 Ver. 3.8 Functional Description 1-7

Each mode comprises the following processes:

Ingress: Checks each frame entering the bridge to decide if and how this
frame should be passed on to the forwarding process
Learning: Learns new MAC table entries (MAC only or MAC VID pairs)
Aging: Checks the forwarding MAC table periodically
Forwarding: Decides to which bridge port(s) to forward the frame
Transmission (VLAN-aware mode only): Selects the format of the transmitted
frame at the output port: with VLAN ID (tagged) or without VLAN ID
(untagged).
These processes are described below for each mode.
VLAN-Aware Mode
This mode enables the creation of subgroups of bridge ports within the bridge.
Each subgroup is associated with a unique VLAN ID (VID). Frames containing a VID
can be forwarded only between bridge ports that are members of this specific
VLAN, enabling a total separation between different VLAN users within the same
bridge.
Ingress Process
The ingress process is composed of three steps:
Frame Admission: Two modes of operation (configured per bridge port):
Admit All Frames: All frames arriving from the port are admitted and
proceed to the ingress filtering process. PVID is assigned to untagged or
priority-only tagged frames.
Admit Only Tagged Frames: Only VLAN tagged frames are admitted and
allowed to proceed to the ingress filtering process. Untagged or priority-
only tagged frames are discarded.
Ingress Filtering: Works in one of the following modes (configured per bridge
port):
Enable Performs ingress filtering according to VIDs. Only frames that
share a VID assigned to this bridge port are admitted
Disable All frames are forwarded.
Only admitted frames that pass filtering are submitted to learning and
forwarding processes.
PVID Assignment: Is per bridge port configuration:
In case the received frame does not contain a VLAN ID (untagged or
priority-only tagged frames), the bridge port PVID is assigned to these
frames before they pass to the forwarding process.
Accordingly, the untagged/priority-tagged frames that have passed the
admission/ingress filtering, are tagged with PVID and proceed to the
forwarding process.

For untagged frames that were tagged during this process to VID=PVID,
the priority tag is assigned at the VLAN priority field, according to the
default priority configuration.
Frames that pass this stage are submitted to the forwarding and learning
processes.
Learning Process
The learning process observes the source MAC address (SA) and the VID of the
received frame, and updates the forwarding database (MAC table) with the MAC
VID pair and with the bridge port from which the frame was received.
Entries in the MAC table can be dynamic (inserted by the learning process) or
static (inserted by configuration). A dynamic entry has an aging time associated
with it.
The ETX-102 VLAN-aware bridge is an Independent VLAN Learning (IVL) bridge.
The learning process inserts a new dynamic entry into the MAC table. This entry
consists of a MAC-VID pair and bridge port.
If the MAC-VID pair already exists for the same port, the aging time is
updated
If the MAC-VID pair already exists but for a different bridge port (dynamic
entry), the new entry overrides the existing one
If the MAC-VID pair already exists for a different bridge port (static entry), the
static entry prevails.
Aging Process
The aging process checks the forwarding MAC table periodically. Each dynamic
entry-aging period that has exceeded the configured aging time limit is deleted.
The aging period represents the time passed since the last frame for this entry
entered the bridge. The periodic check of the MAC table (aging time intervals)
results an actual aging time that can reach up to twice the value that was
configured for the bridge.
Forwarding Process
The forwarding process is performed based on the frame destination MAC VID
pair. The frame is forwarded to the bridge port that was specified in the MAC
table for this MAC VID pair entry.
Untagged frames are forwarded according to the PVID that was attached to the
frame during the ingress process.
Frames are forwarded, dropped, or flooded according to the following guidelines:
Forwarded: If the bridge port of the pair entry (DA, VID) in the MAC table is
both an active bridge port and a member of the VLAN, the frame is forwarded
to that bridge port only.
Dropped:
If the bridge port for the pair entry (DA, VID) in the MAC table is the port
on which the frame was received, the frame is dropped.

If there are no active ports associated with the frames VID, or if the VID
is not defined at all, the frame is dropped.
Flooded:
If the pair (DA, VID) is not learned and does not exist in the MAC table,
the frame is transmitted to all bridge ports that are associated with the
frames VLAN ID.
Multicasts and broadcasts are flooded only through the bridge ports
whose VLAN ID is identical to the frames VLAN ID.
Transmission Process
After the forwarding process identifies the destination bridge port(s) to which
the frames must be transmitted, the frames are transmitted in the appropriate
format.
The frame format can be configured for each VLAN port membership:
Egress tagged: In this mode:
VLAN-tagged frames are transmitted unchanged.
Untagged frames are transmitted tagged with priority according to the
default priority of the ingress bridge port, and VID=PVID of the port from
which they entered.
Priority-tagged frames are transmitted tagged with original priority and
VID = PVID.
Egress untagged: In this mode, all frames are transmitted as untagged.
VLAN-Unaware Mode
In this mode the bridge forwarding ignores the VLAN ID of VLAN-tagged frames.
Each Ethernet packet received from each bridge port is forwarded according to its
destination MAC address.
Ingress Process
All frames are accepted in this mode: untagged, priority-tagged, or VLAN-tagged.
Learning and forwarding is based on the MAC addresses, with no regard to the
VLAN. This mode is also known as transparent mode.
Learning Process
The learning process observes the source MAC address (SA) of the received frame
and updates the forwarding database (FDB) with the MAC address and the bridge
port that the frame was received from. (FDB is also referred to as MAC table).
The learning process inserts a new entry into the MAC table. This entry consists
of the MAC and bridge port.
If the MAC already exists for the same bridge port, the aging time is updated.
If the MAC already exists, but for a different bridge port, (dynamic entry) the
new entry overrides the existing one.

Aging Process
The aging process checks the forwarding MAC table periodically. Each dynamic
entry aging time period that has exceeded the configured Aging Time Limit is
deleted. The aging time period is the period of time since the last frame for this
entry entered the bridge. The periodic check of the MAC table (aging time
intervals), results in an actual aging time that can reach up to twice the value that
was configured by the user.
Forwarding Process
The forwarding process is performed based on the frame MAC Destination
Address (MDA). The frame is forwarded to the bridge/port specified in the MAC
table for this MAC.
Frames are forwarded, dropped, or flooded at this stage:
Forwarded: A frame is forwarded according to its DA, to the bridge port
where its DA was learned.
Dropped: If the port for that DA entry in the MAC table is the port on which
the frame was received, the frame is dropped.
Flooded:
If there is no information regarding the DA in the MAC table, the frame is
flooded to all ports
Frames with multicast or broadcast addresses are flooded to all ports.
Transmission Process
The frames are transmitted according to the tag handling configured for the
bridge port:
None: The frames are transmitted unchanged, that is no tags are added or
removed.
Stack: In the user-to-network direction, the bridge port PVID is added to
frames (stacking) before transmitting them. In the network-to-user direction,
VLAN tag is removed from frames (stripping) before transmitting them.
Fault Propagation
If a network link fails, ETX-102 propagates this condition to user ports (all or only
some of them), see Figure 1-6. The user-configurable time-to-restore parameter
specifies the time period ETX-102 waits before enabling user interfaces once the
network interface is restored.
Figure 1-6. Fault Propagation

Diagnostic Loopbacks
ETX-102 supports the following diagnostics loopbacks:
Layer-1 loopback performed at the PHY of the bridge ports. When the
loopback is active the data forwarded to a bridge port is looped from the Tx
path to the Rx path, disrupting the traffic. This loopback cannot pass through
Ethernet bridges.
Layer-2 loopback with MAC address swapping, when ETX-102 exchanges
source and destination MAC addresses of the incoming packets. This loopback
can be performed per VLAN (or EVC), it passes through Ethernet bridges and
does not disrupt traffic flows, which are not being tested.

1.4 Technical Specifications
Network Number of Ports Up to 2 RJ-45 or fiber optic SFPs

Interface
Note: Port 2 can be configured to operate as a network
or as a user port.
Type SFP (100BaseFx, 100BaseLX10, 100BaseBx10)

Built-in 10/100BaseT
Electrical Operation 10/100 Mbps (copper), full or half duplex,

Mode autonegotiation
User Interface Number of Ports Up to 4 RJ-45 ports
Type Built-in 10/100BaseT
Electrical Operation 10/100 Mbps (copper), full or half duplex,

Mode autonegotiation
Internal Bridge Forwarding Mode Transparent/filtered, VLAN-aware/VLAN-unaware
Number of VLANs 64
Maximum Frame 1,632 bytes

Size
Standard IEEE 802.3, 802.3u, 802.1D, 802.1Q, 802.1p, 802.1ag,

Compliance 802.3ad, 802.3ah
MEF MEF 9, MEF 14
Management Out-of-Band Via dedicated terminal port; V.24/RS-232 DCE;

9.6, 19.2, 38.4, 57.6, 115.2 kbps; DB-9 female
connector
Inband Via one of the Ethernet ports
Indicators TST/ALM/PWR Loopback, alarm, and power status

(green/orange/red)
NET 1, NET 2, Link/activity status of the network/user port

USER 36 (green)
Power AC/DC Source 100240 VAC or 48/60 VDC nominal (4072 VDC)
DC Source WRDC: 24/48/60 VDC nominal (1872 VDC)
Power Consumption 6.1W max
ETX-102 Ver. 3.8 Technical Specifications 1-13

Physical ETX-102 Height: 43 mm (1.7 in)

(Plastic Enclosure) Width: 220 mm (8.6 in)
Depth: 170 mm (6.7 in)
Weight: 0.5 kg (1.1 lb)
ETX-102/H Height: 47 mm (1.8 in)

(Metal Enclosure) Width: 215 mm (8.4 in)
Depth: 147 mm (5.8 in)
Weight: 0.7 kg (1.5 lb)
Environment Temperature ETX-102: 0C50C (32C122F)

ETX-102/H: -40 to 65C (-40 to 149F)
Humidity Up to 90%, non-condensing
1-14 Technical Specifications ETX-102 Ver. 3.8

Chapter 2
Installation and Setup
This chapter describes installation and setup procedures for the ETX-102 unit.
After installing the unit, refer to Chapter 3 for the operating instructions.
If a problem is encountered, refer to Chapter 5 for test and diagnostic
instructions.
Internal settings, adjustment, maintenance, and repairs may be performed only

by a skilled technician who is aware of the hazards involved.
Always observe standard safety precautions during installation, operation, and
Warning maintenance of this product.
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the cables connected to the equipment, ETX-102 must be properly grounded
at any time. Any interruption of the protective (grounding) connection inside or
Grounding outside the equipment, or the disconnection of the protective ground terminal
can make this equipment dangerous. Intentional interruption is prohibited.
2.1 Site Requirements and Prerequisites

AC-powered ETX-102 units should be installed within 1.5m (5 ft) of an
easily-accessible grounded AC outlet capable of furnishing the voltage in
accordance with ETX-102 nominal supply voltage.
DC-powered ETX-102 units require a -48 VDC power source, which must be
adequately isolated from the main supply.
Note Refer also to the sections describing connections of AC and DC mains at the
beginning of the manual.
Allow at least 90 cm (36 in) of frontal clearance for operating and maintenance
accessibility. Allow at least 10 cm (4 in) clearance at the rear of the unit for signal
lines and interface cables.
The ambient operating temperature of ETX-102 is 0 to 50C (32 to 122F), at a
relative humidity of up to 90%, non-condensing.
ETX-102 Ver. 3.8 Site Requirements and Prerequisites 2-1

Chapter 2 Installation and Setup Installation and Operation Manual
2.2 Package Contents

The ETX-102 package includes the following items:
One ETX-102 unit
Matching SFP modules (if ordered)
AC power cord or DC connection kit
Optional accessories included if ordered:
RM-33-2 rack mount kit for ETX-102 with plastic enclosure
RM-35/P1 rack mount kit for mounting one ETX-102/H unit with metal
enclosure
RM-35/P2 rack mount kit for mounting two ETX-102/H units with metal
enclosures
WM-35 wall mount kit for ETX-102/H unit with metal enclosure
CBL-DB9F-DB9M-STR, control port cable.
2.3 Mounting the Unit

ETX-102 is designed for installation as a desktop unit. It can also be mounted in a
19" rack.
For rack mounting instructions, refer to:
RM-33-2 installation kit manual (ETX-102 in a plastic enclosure)
RM-35 installation kit manual (ETX-102/H in a metal enclosure)
For wall mounting instructions, refer to:
Drilling template at the end of the manual (ETX-102 in a plastic enclosure)
WM-35 installation kit manual (ETX-102/H in a metal enclosure)
If ETX-102 is to be used as a desktop unit, place and secure the unit on a
stable, non-movable surface.
Refer to the clearance and temperature requirements in Site Requirements and
Prerequisites.
2.4 Installing SFP Modules

ETX-102 uses SFP modules with LC fiber optic connectors.
Third-party SFP optical transceivers must be agency-approved, complying with the

local laser safety regulations for Class 1 laser equipment.
Warning
2-2 Installing SFP Modules ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 2 Installation and Setup
To install the SFP modules:

1. Lock the wire latch of each SFP module by lifting it up until it clicks into place,
as illustrated in Figure 2-1.
Note Some SFP models have a plastic door instead of a wire latch.
Figure 2-1. Locking the SFP Wire Latch

2. Carefully remove the dust covers from the SFP slot.
3. Insert the rear end of SFP into the socket, and push slowly backwards to
mate the connectors until the SFP clicks into place. If you feel resistance
before the connectors are fully mated, retract the SFP using the wire latch as
a pulling handle, and then repeat the procedure.
4. Remove the protective rubber caps from the SFP modules.
To remove the SFP module:
1. Disconnect the fiber optic cables from the SFP module.
2. Unlock the wire latch by lowering it downwards (as opposed to locking).
3. Hold the wire latch and pull the SFP module out of the Ethernet port.
2.5 Connecting to the Ethernet Equipment

ETX-102 can be connected to the Ethernet equipment via the fiber optic LC
designated 100Fx or 8-pin RJ-45 electrical port designated 10/100BT. Refer to
Appendix A for the RJ-45 connector pinout.
To connect to the Ethernet equipment with fiber optic interface:
Connect ETX-102 to the Ethernet network equipment using a standard fiber
optic cable terminated with an LC connector.
ETX-102 Ver. 3.8 Connecting to the Ethernet Equipment 2-3

NET NET/USER USER

1 2 3 4 5
CONTROL
DCE
100Fx 10/100BT 10/100BT 10/100BT 10/100BT
Figure 2-2. 100Fx Optic Connector

To connect to the Ethernet equipment with a copper interface:
Connect ETX-102 to the Ethernet network equipment using a standard
straight UTP cable terminated with an RJ-45 connector.
Note In order to comply with electromagnetic compatibility requirements (Class B), it is

recommended to use shielded cables when connecting to the RJ-45 port of the
ETX-102 electrical network or user interface.
NET NET/USER USER

1 2 3 4 5
CONTROL
DCE
100Fx 10/100BT 10/100BT 10/100BT 10/100BT
Figure 2-3. 10/100BT Electrical Connectors
2.6 Connecting to the ASCII Terminal

ETX-102 can be connected to an ASCII terminal via a 9-pin D-type female
connector designated CONTROL. Refer to Appendix A for the connector pinout.
NET NET/USER USER

1 2 3 4 5
CONTROL
DCE
100Fx 10/100BT 10/100BT 10/100BT 10/100BT
Figure 2-4. CONTROL Connector

To connect to an ASCII terminal:
1. Connect the male 9-pin D-type connector of CBL-DB9F-DB9M-STR straight
cable available from RAD to the CONTROL connector.
2. Connect the other connector of the CBL-DB9F-DB9M-STR cable to an ASCII
terminal.
2-4 Connecting to the ASCII Terminal ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 2 Installation and Setup
Caution Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to the supervisory
terminal port.
2.7 Connecting to Power

ETX-102 accepts either 100240 VAC or 48/60 VDC power through the same
power inlet.
Before connecting or disconnecting any communication cable, the unit must be

grounded by connecting its power cord to a power outlet with a ground terminal,
and by connecting the ground terminal on the panel (if provided) to a protective
Warning ground.
Any interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting of the protective ground terminal can make this
unit dangerous. Intentional interruption is prohibited.
Note
Refer also to the sections describing connections of AC and DC mains at the
beginning of the manual.
Connecting AC Power
AC power is supplied to ETX-102 through a standard 3-prong socket. AC power
should be supplied via a 1.5m (5 ft) standard power cable terminated by a
standard 3-prong socket. A cable is provided with the unit.
To connect AC power:
1. Connect the power cable to the power connector on the ETX-102 rear panel.
2. Connect the power cable to the mains outlet.
The unit turns on automatically upon connection to the mains.
Connecting DC Power
An unterminated power cord for the 48/60 VDC power connection is supplied
with the unit.
To connect DC power:
Refer to the DC power supply connection supplement for instructions how to
wire the DC adapters. The DC supplement is provided at the end of the
manual.
ETX-102 Ver. 3.8 Connecting to Power 2-5

2-6 Connecting to Power ETX-102 Ver. 3.8

Chapter 3
Operation
This chapter:
Explains power-on and power-off procedures
Provides a detailed description of the front panel controls and indicators and
their functions
Lists alternative methods of the product configuration, explaining ASCII
terminal and Web browser management applications and illustrating
management menus.
For a detailed explanation of parameters in the menus, see Chapter 4.
3.1 Turning On the Unit

To turn on ETX-102:
Connect the power cord to the mains.
The PWR indicator lights up and remains lit as long as ETX-102 receives
power.
ETX-102 requires no operator attention once installed, with the exception of
occasional monitoring of front panel indicators. Intervention is only required
when ETX-102 must be configured to its operational requirements, or diagnostic
tests are performed.
ETX-102 Ver. 3.8 Turning On the Unit 3-1

Chapter 3 Operation Installation and Operation Manual
3.2 Front Panel Indicators

The unit's LEDs are located on the front panel (see Figure 3-1). Table 3-1 lists the
functions of the ETX-102 LED indicators.
Figure 3-1. ETX-102 Front Panel
Table 3-1. ETX-102 LEDs and Controls
Name Type Function

TST/ALM/PWR Green/ ON (green) Device is starting up
orange/ ON (orange) Power is ON and device has completed startup
red LED Blinking (orange) Diagnostic loopback is active
ON (red) One of the Ethernet links is down
NET 1, NET 2, Green LEDs ON Corresponding Ethernet link is OK
USER 36 Blinking Data is being transmitted or received on the corresponding Ethernet
link
3.3 Default Settings

The following table lists the default settings of the ETX-102 configuration
parameters.
Table 3-2. Default Settings
Type Parameter Default Value
System
Host IP address 0.0.0.0
IP mask 0.0.0.0
Default gateway 0.0.0.0
Default IP 0.0.0.0
DHCP Enable
Device Info Name ETX-102
Location The Location of the Device
Contact Person Name of Contact Person
Management Access Telnet/SSH Access Enable
SNMP Access Disable
3-2 Default Settings ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 3 Operation
Web Access Enable
RADIUS Authentication Disable
User Access User Name su
Permission Read Only
Access All
RADIUS Parameters Server IP Address 0.0.0.0
Shared Secret
Number of Retries 3
Timeout (in seconds) 3
Authentication Port 1812
Accounting Port 1813
Host Read Community public
Write Community private
Trap Community public
Encapsulation Host Tagging Tagged
Host VLAN ID 300
Host VLAN Priority 7
Security Definition Network Only
Alarm Trap Mask Alarm ID 1
Trap Status Masked
Alarm Threshold Alarm Description Dropped Frames

Configuration
Port Label Port 1
Rising Alarm Threshold 0
Falling Alarm Threshold 0
Sampling Interval 1
Event Type None
SNMPv3 SNMPv3 Disable
SNMPv3 Settings Authentication Protocol usmNoAuthProtocol
Privacy Protocol usmNoPrivProtocol
Message Processing Model SNMPv3
Security Model Any
Security Level noAuthNoPriv
Control Port Baud rate 115200
ETX-102 Ver. 3.8 Default Settings 3-3

Set Scrolling Window Size 4
Security timeout 10
Syslog Logging Status Disable
Device UDP Port 514
Facility Local 1
Severity Level Major
Server Access Disable
Server IP Address 0.0.0.0
Server UDP Port 514
Traps Delay 0
Date/Time NTP Mode Disable
NTP Server IP Address 0.0.0.0
GMT 0
NTP Update Interval 1
Protection (LAG) Redundancy Method LAG
Wait to Restore 0
Protection (1:1) Recovery Mode Revertive
Wait to Restore 0
Shut Down Duration Upon Flip 0
Set Active Port None
Physical Layers Fault Propagation WTR 0
Ethernet Administrative Status Up
Autonegotiation Enable
Max Capability Advertised/Speed 100base - TX full duplex mode

& Duplex
Flow Control Disable
MDIX Auto Cross Over Enable
Fault Propagation Disable
Link OAM (802.3ah) Disable
OAM MNG Disable

OAM
EVC ID Put your string here
SP VLAN 1
MEP Local MEP ID 0
Remote MEP ID 0

OAM Mode Disable

Continuity Verification Mode Disable
OAM Destination Address Type Multicast
OAM Destination MAC Address 00-00-00-00-00-00
Default Priority 0
Services PM Disabled
Service Priority 0
Delay Objective 1
Delay Variation Objective 1
Event Reporting Event Reporting Type None
(Frame Loss Ratio,
Unavailability Ratio)
Rising Threshold 1E-10
Falling Threshold 1E-10
(Frame Above Delay,
Frame Above Delay Variation)
Rising Threshold 1
Falling Threshold 1
Sampling Interval 1
Bridge VLAN Mode Unaware
Forwarding Mode Filter
Aging Time 300
Network Port Ingress Filtering Enable
Accept Frame Type All
Port VID 1
Default Priority Tag 0
Cnode Level 1 State Disable
User Port Ingress Filtering Enable
Accept Frame Type All
Port VID \ Stacking VID 1
Default Priority Tag 0
Tag Handling None
OAM Standard OAM MAC Address 01-80-C2-00-00-30
Standard OAM EtherType 8902
MD Names MD Format String
MD Name None
EVC EVC Name Put your string here
ETX-102 Ver. 3.8 Default Settings 3-5

SP VLAN 1
Protocol Type Standard
MA ID MD ID 1
MA Format String
MA Name DEFAULT
MEP Local ID 0
OAM Destination Address Type Mulicast
OAM Destination MAC Address 00-00-00-00-00-00
Remote ID
MD Level 3
OAM Mode Disable
CC Interval 1 second
Services PM Disabled
Service Priority 0
Delay Objective 0
Delay Variation Objective 0
(Frame Loss Ratio,
Unavailability Ratio)
Rising Threshold 1E-10
Falling Threshold 1E-10
(Frame Above Delay,
Frame Above Delay Variation)
Rising Threshold 1
Falling Threshold 1
Sampling Interval 1
QoS
Priority Classification 802.1p
Rate Limitation
Ingress Rate Limitation No Limit
Burst Size 96
Limit Packet Type All
Egress Rate Limitation No Limit
Diagnostics
Ping Destination IP Address 0.0.0.0
Number of Frames to Send 1

Loopbacks MAC Swap Disable
Looped Data All
VLAN ID 1
Direction Local
Forced Source Mac 00-00-00-00-00-00
Forced Destination Mac 00-00-00-00-00-00
Loopback Timeout 0
Loopback State Disable
VLAN Test Port Network 1
VLAN ID 1
State Off
3.4 Configuration and Management Alternatives

After installation, there are no special operating procedures for ETX-102. Once it
is powered up, the unit operates automatically. The unit operational status can
be monitored constantly.
If required, ETX-102 can be reconfigured. ETX-102 can be managed using the
following ports and applications:
Local out-of-band management via an ASCII terminal connected to the
RS-232 port. Usually, preliminary configuration of the system parameters is
performed via ASCII terminal. Once the ETX-102 host IP parameters are set, it
is possible to access it via Telnet or Web browser for further configuration.
Remote inband management via user or network port. Remote management
is performed via Telnet or Web browser.
The following functions are supported by the ETX-102 management software:
Viewing system information
Modifying configuration and mode of operation, including setting system
default values and resetting the unit
Monitoring ETX-102 performance
Initiating connectivity tests
Uploading and downloading software and configuration files.
Working with Terminal

ETX-102 has a V.24/RS-232 asynchronous DCE port, designated CONTROL and
terminated in a 9-pin D-type female connector. The control port continuously
monitors the incoming data stream and immediately responds to any input string
received through this port.
ETX-102 Ver. 3.8 Configuration and Management Alternatives 3-7

The ETX-102 control port can be configured to communicate at the following

rates: 9.6, 19.2, 38.4, 57.6 or 115.2 kbps.
To start a terminal control session:

1. Make sure all ETX-102 cables and connectors are properly connected.
2. Connect ETX-102 to a PC equipped with an ASCII terminal emulation
application (for example, Windows Hyper Terminal or Procomm).
3. Turn on the control terminal PC and set its port parameters to 115,200 baud;
8 bits/character; 1 stop bit; no parity.
4. Set the terminal emulator to ANSI VT100 emulation (for optimal view of
system menus).
5. When the initialization and self-test are over, press any key to display the
user name and password entry fields.
Login
To prevent unauthorized modification of the operating parameters, ETX-102
supports two access levels: .
Superuser can perform all the activities supported by the ETX-102
management facility, including defining new users.
Users access rights (full control or read only) are defined by the superuser.
Users are not allowed to create new users.
Note It is recommended to change default passwords to prevent unauthorized access

to the unit.
To enter as a superuser:
1. Enter su for user name.
2. Enter 1234 for password.
This allows you to configure all the parameters of ETX-102, and to change the
su and user passwords.
To enter as a user:
1. Enter user for user name.
2. Enter 1234 for password.
Note
If the password is invalid in three consecutive attempts, the system becomes
inaccessible for 15 minutes.
Choosing Options
How to use the terminal to perform a desired activity:

To select a menu item, type the corresponding line number and then press
<Enter>. This will either
3-8 Configuration and Management Alternatives ETX-102 Ver. 3.8

display a submenu or a parameter selection screen

or
let you type the (free text) parameter value in the same row
or
toggle the current value of the corresponding parameter (relevant to
ENABLE/DISABLE or ON/OFF selections).
The type of response to be expected after selecting a menu item is indicated
as follows:
> Selecting that item will display a submenu or a parameter

selection screen.
... Selecting that item will let you type the desired value in the
same line.
Nothing When neither symbol is displayed, selecting that item will toggle
the current selection, now shown in brackets (for example, this
will change ENABLE to DISABLE or vice versa).
When a menu does not fit on one screen (because it includes many lines), it
is displayed on two consecutive pages. In this case, you will see (N) after
the last line on the first page and (P) after the last line on the second page:
While on the first page, press N to display the second page
While on the second page, press P to return to the first page.
When a configuration screen is organized as a table, a special set of keys is
used for navigation within the table (such screens always have a ? (help)
option that displays these keys). The following keys may be used for
navigation within tables:
L move to the left R move to the right

^D scroll down ^U scroll up
In addition, the following shortcuts are also available:

Tab select the next cell that may be changed
G followed by <row number>,<col number> select a specific cell. For
example, type G2,5 to select the fifth cell in the second row.
The current value of a parameter is listed within parentheses ( ). To change a
parameter value on a parameter selection screen:
Type the line number corresponding to the desired value, and then press
<Enter>
To enter a value which requires free text entry, type in the desired string
and then press <Enter>. Use backspace to erase the current string.
Note that whenever applicable, the allowed range of values of a
parameter is listed within square brackets [ ].

The entry is checked after pressing <Enter>, and it is accepted only if it is

valid:
If you make an error, for example, if you press a key not active on the
current screen or select an invalid parameter value, an ERROR indicator
appears in the right-hand corner. This indicator disappears as soon as
you make a correct operation.
If you select a parameter value incompatible with the current operating
state or other parameters, you will see a message that explains the error.
When done with the current screen, press <Esc> to return to the previous
screen, or type ! to return directly to the main menu.
Ending a Terminal Configuration Session
To end the current terminal session:

Type &.
After a session is ended, it is necessary to enter again a valid user name and
password to start a new session.
Working with Web Terminal
Web Browser Requirements

The following Web browsers can be used to access the ETX-102 supervision utility
from any location that enables access to the ETX-102 using Internet protocols.
Internet Explorer 6.0 and up, running on Windows
Netscape Communicator 7.0 and up, running on Windows, HPOV or Linux
Firefox 1.0.4 and up, running on Windows
Mozilla 1.4.3 and up, running on Linux.
However, before using Web access, it is necessary to perform a preliminary
configuration of ETX-102.
When using a Web browser, pay attention to the following points:
Enable scripts
Configure the firewall that is probably installed on your PC in order to allow
access to the destination IP address
Disable pop-up blocking software (such as Google Popup Blocker); you may
also have to configure your spyware/adware protection program to accept
traffic from/to the destination IP address
Browsers store the last viewed pages in a special cache. To prevent
configuration errors, it is absolutely necessary to flush the browsers cache
whenever you return to the same screen.

Login
To manage ETX-102 via Web terminal:

1. Open the Web browser.
2. Enter the IP address of ETX-102 in the address field of the browser in the
following format: http://IP address (IP address stands for the actual
ETX-102 IP address).
3. After entering the address, press <Enter> to command the browser to
connect.
4. After the opening window is displayed, click LOGIN.
5. In the Password Entry window, log in by entering your user name (user) and
password (1234).
The Main menu is displayed.
6. Use standard browser operating procedures to perform the desired activities.
Notes
It is recommended to change default passwords to prevent unauthorized
access to the unit.
ETX-102 allows up to three management sessions to be active at a time. This
includes up to two network sessions (Telnet, Web) and one ASCII terminal
session.
If no user input is detected for five minutes during the Web terminal session,
ETX-102 automatically disconnects from the management station.
Navigating the Web Terminal Menus

The Web-based remote access terminal management software provides a
user-friendly interface for configuring, collecting statistics, and performing
diagnostic tests on the ETX-102 units.
To choose an option:
1. Click a link in the Web screen to display the next menu.
2. Once the target screen is displayed, select a value from the drop-down box or
enter it in a text box.
At the left-hand bottom corner are some auxiliary management tools:
Status shows the number of users currently managing ETX-102
Trace opens an additional pane for system messages, progress indicators
(ping, software and configuration file downloads) and alarms. It is
recommended to keep the trace pane open all the time.
Refresh All refreshes all display elements.

Menu Maps
Use these menu trees as a reference aid while performing configuration and
control functions. Chapter 4 illustrates menus and explains parameters. Table 3-2
lists default values.
Main Menu Configuration Quick Setup
Inventory Quick Setup Host IP Address
Configuration System Host IP Mask
Monitoring Physical Layers Default Gateway
Diagnostics OAM Host Tagging
Utilities Bridge Host VLAN ID
QoS VLAN Mode
Forwarding Mode
DHCP Client
Figure 3-2. Main Menu > Configuration > Quick Setup
Device Info
Name
Location
Contact Person
Host Encapsulation
Read Community Host Tagging Target Params
Write Community Host VLAN ID Name
Trap Community Host VLAN Priority Message Processing Model
Configuration System Host Encapsulation Security Definition Security Model
Quick Setup Host IP Address Security Name
System Management IP Mask Users Security Level
Physical Layers Control Port Default Gateway Security Name
OAM Date/Time Default IP Authentication Protocol Target Address
Bridge Factory Default DHCP Authentication Password
Name
QoS Protection DHCP Status SNMPv3 Settings Privacy Protocol
IP Address
Users Privacy Password
Params Name
Management Targets & Notify Targets and Notify Address Mask
Device Info SNMPv1/v3 Mapping Tag List
Target Params
SNMPv3 SNMPv3 Factory Defaults
Target Address Notify
Host Summary Target Table
Notify
Manager List Summary User Table Name
Trap
SNMPv3 Settings Tag
Management Access
Alarm Trap Mask Trap
Alarm Threshold Configuration
Trap Name
Traps Delay
Notify Name
Control Port User Access
Baud Rate Management Access User Name
Set Scrolling Window Size User Access Access
Security Timeout Telnet/SSH Access 'su' Password
SNMP Access New Password
Web Access Confirm New Password
Date/Time
Access Policy
Time
RADIUS Parameters
Access Policy
Date 1st Level
NTP Mode Alarm Trap Mask 2nd Level
NTP Server IP Address
GMT (+/- XX) Alarm ID
NTP Update Interval Trap Status RADIUS Parameters
Serve Access
Protection Server IP Address
Redundancy Method Key String
Number of Retries
Recovery Mode (1:1 only)
Wait to Restore Timeout
Shut Down Duration Upon Flip (1:1 only) Authentication Port
Set Active Port (1:1 only)
Alarm Threshold Configuration
Alarm Description
Port Label
Rising Alarm Threshold
Falling Alarm Threshold
Sampling Interval
Event Type
Figure 3-3. Configuration > System

Configuration Ethernet (Network)

Quick Setup Physical Layers Administrative Status
System Ethernet User Name
Physical Layers Fault Propagation WTR Flow Control
OAM OAM (802.3ah)
Bridge OAM MNG
QoS
or
Ethernet (User)
Administrative Status
User Name
Autonegotiation
Max Capability Advertised
Flow Control
MDIX Auto Cross Over
MDIX Manual Switch
Fault Propagation
OAM (802.3ah)
OAM MNG
Figure 3-4. Configuration > Physical Layers
Configuration
Quick Setup
System Bridge Bridge Port Bridge Port
Physical Layers VLAN Mode (Network) (User)
OAM Forwarding Mode Ingress Filtering Ingress Filtering
Bridge Aging Time Accept Frame Type or Accept Frame Type
QoS Static MAC Table Port VID/Stacking VID Port VID/Stacking VID
Erase MAC Table Default Priority Tag Default Priority Tag
Bridge Port Tag Handling
VLAN Membership
Egress Tagged Ports
Egress Untagged Ports
Figure 3-5. Configuration > Bridge
Figure 3-6. Configuration > OAM

Configuration
Quick Setup
System
Physical Layers
OAM QoS Priority
Bridge
QoS Priority Classification
Rate Limitation Mapping
Rate Limitation Ingress
Ingress Rate Limitation
Egress Burst Size
Limit Packet Type
Egress
Rate Limitation
Figure 3-7. Configuration > QoS
Main Menu Monitoring System

Inventory System Connection Status
Configuration Physical Layers Connected Managers
Monitoring OAM Event Log
Diagnostics Bridge
Utilities Physical Layers Statistics
Diagnostics End-to-End 15 Min. Intervals
Ethernet Status
Ethernet Statistics Status 24 Hours Counters
Ping Statistics Service Counters
Trace Route OAM
Loopback End-to-End Link (802.3ah)
VCT Test Link (802ah)
VLAN Test Status
Bridge
Utilities
MAC Bridge
File Utilities VLAN Table
Reset
File Utilities
S/W & File Transfer using TFTP
Swap Main Application File with Backup
Figure 3-8. Monitoring, Diagnostics and Utilities
3.5 Turning Off the Unit

To power off the unit:
Remove the power cord from the power source.
3-14 Turning Off the Unit ETX-102 Ver. 3.8

Chapter 4
Configuration
This chapter illustrates the configuration ETX-102 screens and explains their
parameters.
The menu tree of the ETX-102 management software is shown in Chapter 3.
For your convenience, parameters that are mandatory for configuration, such as
IP settings of the ETX-102 host or forwarding mode, are given in the Quick Setup
menu (Main menu > Configuration > Quick Setup). This menu is explained in the
Quick Start Guide at the beginning of the manual, and the menu parameters are
explained in the relevant sections of the configuration chapter.
4.1 Configuring for Management

Usually, initial configuration of the management parameters is performed via an
ASCII terminal. Once the ETX-102 host IP parameters are set, it is possible to
access it via Telnet or Web for operation configuration. Perform the following
steps in order to configure ETX-102 for management:
Configuring IP Host Parameters
Entering Device Information
Configuring Communities
Configuring the Host Encapsulation
Configuring the Network Managers.
Configuring IP Host Parameters

ETX-102 can be managed by a network management station which is located on
the LAN connected to the one of the units Ethernet ports. In order to establish a
proper connection, it is necessary to configure the following: host IP address,
subnet mask, default gateway. Also it is possible to enable or disable the ETX-102
DHCP client.
ETX-102 Ver. 3.8 Configuring for Management 4-1

Chapter 4 Configuration Installation and Operation Manual
ETX-102
Configuration>System>Host
1. IP Address ... (0.0.0.0)

2. IP Mask ... (255.255.255.0)
3. Default gateway ... (0.0.0.0)
4. DHCP ... (Enable)
5. Default IP ... (0.0.0.0)
6. `DHCP Status >
>
ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
Figure 4-1. Host Menu
Configuring the DHCP Client

To facilitate integration of a new device into a DHCP IP network, if no IP address
has been manually configured, ETX-102 automatically requests one from the
DHCP server upon booting. ETX-102 is shipped with the DHCP client set to Enable.
To enable the DHCP client:

1. From the System menu, select Host.
The Host menu appears.
2. From the Host menu, select DHCP Client, and choose Enable.
ETX-102 starts broadcasting requests for an IP address. When the DHCP
server is found, ETX-102 receives from it all necessary host IP
parameters.
3. From the Host IP menu, select DHCP Status to view the current status of the
ETX-102 DHCP client:
Server ID IP address of the DHCP server
Lease expiration time Time when the IP address lease expires
Current status Current status of the DHCP client (Locating available
server, Waiting for confirmation of lease, etc)
Note When the IP address lease is about to expire, DHCP client automatically requests
lease extension.
To disable the DHCP client:

From the Host menu, select DHCP Client, and choose Disable.
ETX-102 sets the host IP address to 0.0.0.0, while preserving the IP mask
and default gateway values. Telnet or HTTP connection to ETX-102 is
disrupted and the unit can be accessed only using a previously defined
default IP address (see the next section for instructions on how to enter
a default IP address).
4-2 Configuring for Management ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 4 Configuration
Setting Host IP Parameters

ETX-102 allows entering IP parameters manually or using parameters acquired
from the DHCP server.
To define the IP parameters manually:

1. Disable the DHCP client.
ETX-102 releases the current IP address by sending the release message
to the DHCP server, sets all host IP parameters to 0.0.0.0 and reboots
itself automatically.
2. From the Host menu, perform the following:
Select IP Address to define the host IP address
Select IP Mask to define the host IP mask.
Select Default Gateway to set the default gateway IP address
Select Default IP to enter a default IP address. Configuring a default IP
address is necessary if you want to preserve a Telnet or HTTP connection
to ETX-102 after disabling its DHCP client.
Note The default gateway must be in the same subnet as the host.
To acquire a new IP address from the DHCP server:

1. From the Host IP menu, set all host IP parameters (host IP, IP mask and
default gateway) to 0.0.0.0.
2. Enable the DHCP client.
ETX-102 reboots itself automatically and acquires new IP parameters
from the DHCP server at startup.
Entering Device Information

The ETX-102 management software allows you to assign a name to the unit, add
its description, specify its location to distinguish it from the other devices
installed in your system, and assign a contact person.
To enter device information:

1. From the System menu, select Management.
2. From the Management menu, select Device Info.
The Device Info menu appears (see Figure 4-2).
3. From the Device Info menu, select Device Name and enter a desired name for
the ETX-102 unit.
4. Select Device Location and enter the desired name for the current ETX-102
location.
5. Select Contact Person and enter name of a contact person.

ETX-102
Configuration>System>Management>Device Info
Description ... (ETH NTU: Boot: 2.01, Hw: 3.01, Sw: 3.80)
1. Name ... (ETX-102)

2. Location ... (The Location of the Device)
3. Contact Person ... (Name of Contact Person)
>
Figure 4-2. Device Info Menu
Configuring Communities
For establishing a proper management link, you must specify the SNMP trap,
read, and write communities.
To configure ETX-102 communities:

1. From the Management menu, select Host.
The Host (Management) menu is displayed (see Figure 4-3).
2. From the Host menu, do the following:
Select Read Community to enter the name of a community with read-only
authorization.
Select Write Community to enter the name of a community with write
authorization.
Select Trap Community to enter the name of a community to which
ETX-102 sends traps.
ETX-102
Configuration>System>Management>Host
IP Address ... (0.0.0.0)
IP Mask ... (0.0.0.0)
Default Gateway ... (0.0.0.0)
1. Read Community ... (Public)
2. Write Community ... (Public)
3. Trap Community ... (Public)
4. Encapsulation >
>
Figure 4-3. Host (Management) Menu

Configuring the Host Encapsulation

ETX-102 management software allows you to create a dedicated management
VLAN in order to separate management traffic from the user data. In addition, it
is possible to restrict the management traffic to the network or user ports or
allow inband management via any of the ETX-102 ports.
To configure the host encapsulation:

1. From the Host menu (Figure 4-3), select Encapsulation.
The Encapsulation menu is displayed (see Figure 4-4).
2. From the Encapsulation menu, do the following:
Select Host tagging, and choose Tagged or Untagged to consider or
ignore the VLAN tagging of the management traffic coming from the
management station.
If host tagging is enabled, select Host VLAN ID to enter the ID of the host
VLAN (14094).
If the host tagging is enabled, select Host VLAN priority to specify priority
of the host VLAN (07).
Select Security Definition and define the ports from which the manager
can access ETX-102. Possible values depend on the VLAN mode (aware or
unaware) of the ETX-102 bridge, selected in the Bridge menu (see
Configuring the Bridge below).
All ETX-102 can be accessed via any of its ports (available in
VLAN-aware and VLAN-unaware mode). In VLAN-aware mode, an
ETX-102 port and the ETX-102 host must be members of the same
VLAN to allow access to the unit via this port.
Network Only ETX-102 can be accessed via the network port only
(available only in the VLAN-unaware mode)
User Only ETX-102 can be accessed via one of its user ports
(available only in the VLAN-unaware mode).
ETX-102
Configuration>System>Management>Host>Encapsulation
1. Host Tagging (Tagged)

2. Host VLAN ID [1 - 4094] ... (300)
3. Host VLAN Priority [0 - 7] ... (7)
4. Security Definition (All)
>
Figure 4-4. Encapsulation Menu

Configuring the Network Managers

You can define or modify the network management stations to which the SNMP
agent of ETX-102 sends traps. Up to ten managers can be defined. Entering the
IP address and corresponding subnet mask defines each management station. In
addition, you can temporarily prevent a manager station from receiving traps by
masking the network manager. Before editing the manager list, it is necessary to
add at least one network manager.
To add a network manager:

1. From the Management menu, select Manager List.
The Management List menu appears (see Figure 4-5).
2. From the Management List menu, type a to add a management station.
The Management List menu display changes, entering the Add mode
(see Figure 4-6).
3. When in Add mode, perform the following:
Select Manager IP, and enter the IP address of the management station.
Select Manager Trap Mask, and select Enable or Disable to mask or
unmask traps for the selected management station.
Select SNMP Traps UDP Port and define a UDP port to be used for sending
SNMP traps to the network manager.
Select Save All to save the network manager.
Press <Esc> to return to the Edit mode.
To edit the manager list:

1. From the Management List menu, move the cursor to the Trap Mask field by
pressing <Tab>.
2. Toggle between Enable and Disable to mask or unmask traps for the selected
management station.
ETX-102 supports SNMP traps for the following events:
Cold start
Link up
Link down
Authentication failure
TFTP status change
Agent status change
Power failure
Rising alarm
Falling alarm.
Refer to trap list in Chapter 5 for the detailed description of the ETX-102 traps.

To remove a network manager:

1. From the Manager List, select a network manager that you intend to remove.
2. Type r to remove the selected network manager from the list.
To clear the manager list:

From the Manager List, type x to delete all network managers.
ETX-102
Configuration>System>Management>Manager List
Manager ID IP Address Trap Mask SNMP Traps UDP Port
1. 1.1.1.1 Disable 162
2. 2.2.2.2 Disable 162
| 3. 3.3.3.3 Disable 162
v 4. 4.4.4.4 Disable 162
A add R remove X clear table

ESC-prev.menu; !-main menu; &-exit; ?-help
Figure 4-5. Manager List Menu
ETX-102
Configuration>System> Management > Manager List
Manager ID (1)
1. IP Address ... (1.1.1.1)
2. Trap Mask ... (Disable)
3. SNMP Traps UDP Port ... (162)
4. Save All
>
Figure 4-6. Manager List Menu, Add Mode
Configuring SNMPv3
ETX-102 supports SNMP version 3 entity, providing secure access to the device by
authenticating and encrypting packets transmitted over the network.
Follow these steps to configure the SNMPv3 entity:
1. Enable SNMPv3.
2. Add a new user.
3. Add a new notification entry.
4. Assign traps to notification entries.
5. Configure target (NMS) parameters.
6. Specify target address, define its parameter set and assign notification tags.
7. Map SNMPv3 setting to SNMPv1 settings (if necessary).

Enabling SNMPv3
To enable SNMPv3:
1. From the Management menu (Configuration > System > Management), select
SNMPv3 to enable the SNMPv3 entity.
The SNMPv3 Settings line is added to the Management menu.
2. From the Management menu, select SNMPv3 Settings.
The SNMPv3 Settings menu is displayed.
The SNMPv3 Settings menu includes the following information:
Engine Boots (The number of times that the SNMP engine has reinitialized
since its identification was last configured.)
Engine Time (The number of seconds since the last SNMP engine boot)
SNMP Message Size (The maximum length of an SNMP message (in
octets) that the SNMP engine can send or receive and process.)
ETX-102
Configuration>System>Management>SNMPv3 Settings
Engine Boots (2)
Engine Time (276)
SNMP Message Size ... (1500)
1. Users >
2. Targets & Notify >
3. SNMPv1/v3 Mapping >
4. SNMPv3 Factory Defaults
5. Summary User Table []
6. Summary Target Table []
>
Figure 4-7. SNMPv3 Settings Menu
Adding SNMPv3 Users

ETX-102 supports up to ten SNMPv3 managers with different authorization and
privacy attributes.
Note
Access control policy is defined via the vacmSecurityToGroupTable and
vacmAccessTable tables, which can be accessed via an SNMP browser only.
To add an SNMPv3 user:

1. From the Users menu (Configuration > System > Management > SNMPv3
Settings > Users), perform the following:
Select Security Name and enter security name for a new user (up to 32
alphanumeric characters).

Select Authentication Protocol and define the authentication protocol to

be used for authenticating the user:
usmNoAuthProtocol (No authentication is performed)
usmHMACMD5AuthProtocol (MD5 protocol)
usmHMACSHAAuthProtocol (SHA protocol)
Select Privacy Protocol and define the type of privacy protocol to be used
for encryption:
usmNoPrivProtocol (Privacy protocol is not used)
usmDESPrivProtocol (DES protocol)
Select Authentication Password and define the authentication password
of the user. This is not available if authentication has been disabled.
Select Privacy Password and define the private key used for encryption.
This is not available if privacy has been disabled.
2. To view the summary of the SNMPv3 user configuration, select Summary User
Table from the SNMPv3 Settings (Configuration > System > Management >
SNMPv3 Settings) menu.
To delete an SNMPv3 user:

1. From the Users menu (Configuration > System > Management > SNMPv3
Settings > Users), type f or b to select an SNMPv3 user.
2. Type r to delete the selected user.
Adding Notification Entries
To add a notification entry:

1. From the Targets & Notify menu (Configuration > System > Management >
SNMPv3 Settings > Targets & Notify), select Notify.
The Notify menu is displayed (see Figure 4-8).
2. From the Notify menu, perform the following:
Name (ASCII string identifying the notification entry)
Tag (A tag value to be associated with the current notification entry. This
tag is used to identify the current notification entry when configuring the
target address.)

ETX-102
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Notify
Type > ()
1. Name ...()
2. Tag ...()
>
Figure 4-8. Notify Menu
Assigning Traps
One or more traps must be assigned to each notification entry.
To assign traps to notification entries:

1. From the Target & Notify menu, select Trap.
The Trap menu is displayed.
2. From the Trap menu, configure the following:
Tag Name (A tag from the list of previously defined notification tags)
Trap (A trap to be assigned to the selected tag).
ETX-102
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Trap
1. Tag Name >()

2. Trap >()
>
Figure 4-9. Trap Menu
Configuring Target Parameters

A target is an SNMPv3 network management station to which ETX-102 is going to
send trap notifications. A set of parameters has to be configured and assigned to
each target.
To configure target parameters:

SNMPv3 Settings > Targets & Notify), select Target Params.
The Target Params menu is displayed (see Figure 4-10).
2. From the Target Params menu, configure the following:
Name (An ASCII string identifying current set of target parameters)

Message Processing Model (The Message Processing Model to be used

when generating SNMP messages using this entry):
SNMPv1
SNMPv2c
SNMPv2u
SNMPv3
Security Model (The Security Model to be used when generating SNMP
messages using this entry):
Any
SNMPv1
SNMPv2c
User-Based Security Model (USM)
Security Name (Identification of the principal on whose behalf SNMP
messages are to be generated using this entry. This can be either
SNMPv3 user or SNMPv1/SNMPv2 community string.)
Security Level (The level of security to be used when generating SNMP
messages using this entry):
noAuthNoPriv (Authorization and privacy are disabled)
authNoPriv (Authorization is enabled, privacy is disabled)
authPriv (Authorization and privacy are enabled)
ETX-102
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Params
1. Name ... ()
2. Message Processing Model > ()
3. Security Model > ()
4. Security Name ... ()
5. Security Level > ()
>
Figure 4-10. Target Params Menu
Configuring Target Address

Each target must have a valid IP address and IP mask. Also, previously-configured
parameter set and notification tags must be assigned to the target.
To configure the target address:

SNMPv3 Settings > Targets & Notify), select Target Address.
The Target Address menu is displayed (see Figure 4-11).

2. From the Target Address menu, configure the following:

Name (ASCII string identifying the target)
IP Address (Valid IP address of the NMS. The IP address must be in
xxx.xxx.xxx.xxx:162 format, where 162 is a standard SNMP port used for
sending traps.)
Params Name (Name of the previously defined target parameter set to be
assigned to this target)
Address Mask (An IP mask of the NMS)
Tag List (List of previously defined notification tags).
3. To view the summary of the SNMPv3 target configuration, select Summary
Target Table from the SNMPv3 Settings (Configuration > System >
Management > SNMPv3 Settings) menu.
ETX-102
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Address
1. Name ... ()
2. IP Address ... ()
3. Params Name ... ()
4. Address Mask ... ()
5. Tag List ... ()
>
Figure 4-11. Target Address Menu
Mapping SNMPv1 to SNMPv3

ETX-102 supports coexistence of different SNMP versions by mapping
SNMPv1/SNMPv2 community name to the SNMPv3 security name value. The
mapping is performed according to the RFC 3584 requirements.
To map SNMPv1 to SNMPv3:

1. From the SNMPv3 Settings menu (Configuration > System > Management >
SNMPv3 Settings), select SNMPv1/v3 Mapping.
The SNMPv1/v3 Mapping menu is displayed.
2. From the SNMPv1/v3 Mapping menu, select the following:
Community Index (SNMP community index)
Community String (SNMPv2/SNMPv2 community name)
Security Name (SNMPv3 security name to me mapped to the
SNMPv2/SNMPv2 community name)
Transport Tag (Specifies a set of transport endpoints which are used in
two ways:

To specify the transport endpoints from which an SNMP entity

accepts management requests
To specify the transport endpoints to which a notification may be
sent using the community string matching the corresponding instance
of community name.)
ETX-102
Configuration>System>Management> SNMPv3 Settings> SNMPv1/v3 Mapping
1. Community Index ... ()

2. Community Name ... ()
3. Security Name ... ()
4. Transport Tag ... ()
>
Figure 4-12. SNMPv1/v3 Mapping Menu
Controlling Management Access

You can enable or disable access to the ETX-102 management system via an SNMP,
Telnet or Web-based application. By disabling SNMP, Telnet or Web, you prevent
unauthorized access to the system when security of the ETX-102 IP address has
been compromised. When SNMP, Telnet and Web access is disabled, ETX-102 can
be managed via an ASCII terminal only. In addition, you can limit access to the
device to only the stations defined in the manager list. Table 4-1 details
management access implementation, depending whether the network managers
are defined or not.
To define the management access method:

1. From the Management menu, select Management Access.
The Management Access menu appears (see Figure 4-13).
2. From the Management Access menu, select Telnet/SSH Access to configure
Telnet access, select SNMP Access to configure SNMP access, or select Web
Access to configure Web access.
3. Define access mode for each management method:
Enable (Telnet, SNMP or Web access is enabled)
Disable (Telnet, SNMP or Web access is disabled)
Manager Only (Access is allowed only for the stations appearing in the
manager list)
Enable Secure (Secure access (SSH-enabled for Secure Shell or SSL-
enabled for Web) is enabled)
Manager Only Secure (Secure access (SSH-enabled for Secure Shell or
SSL-enabled for Web) is allowed only for the stations appearing in the
manager list).

Table 4-1. Management Access Implementation
Access Method Mode Who is Allowed to Access ETX-102
Network Network
Manager(s) Defined Manager(s) not
Defined
Enable Anybody Anybody
Disable Nobody Nobody

SNMP Access
Managers Only Only defined Nobody
network managers
Enable/Enable Secure Anybody Anybody

Telnet Access
Managers Only/ Only defined Nobody
Managers Only Secure network managers
Enable/Enable Secure Anybody Anybody

Web Access
Managers Only/ Only defined Nobody
Managers Only Secure network managers
ETX-102
Configuration>System>Management>Management Access
1. User Access >

2. TELNET/SSH access > (Enable)
3. SNMP access > (Disable)
4. WEB access > (Enable)
5. RADIUS Authentication > (Enable Remote)
6. RADIUS Parameters >
>
Figure 4-13. Management Access Menu
Defining Access Policy

Access policy allows configuration of multiple authentication protocols. User
authentication is performed in the order the methods are selected. If the first
authentication method is not available, the next selected method is used.
However if the authentication is rejected by the first method, the next method is
not used.

To define the access policy:

From the Access Policy menu (Configuration > System > Management >
Management Access > Access Policy), configure the following:
1st Level (First level of authentication):
RADIUS (ETX-102 uses authentication database stored at the RADIUS
server)
Local (ETX-102 uses locally stored authentication database)
2nd Level (Second level of authentication. Available only when the 1st level
authentication is set to RADIUS.):
None (Second authentication level is disabled, access to ETX-102 is
allowed only using the 1st level method.)
Local (ETX-102 uses locally stored authentication database)
Configuring RADIUS Client

The RADIUS (Remote Authentication Dial-In User Service) is a client/server
security protocol. Security information is stored in a central location, known as
the RADIUS server. RADIUS clients, such as ETX-102, communicate with the
RADIUS server to authenticate users. ETX-102 supports up to four RADIUS
servers.
To configure RADIUS client:

1. From the RADIUS Parameters menu (Configuration > System > Management >
Management Access > RADIUS Parameters), type f to select a RADIUS server
that you intend to configure.
The Server Status parameters indicate the current status of the selected
server. The status can be one of the following:
Connected Selected server is currently operating as an active RADIUS
server
Not Connected Selected server is a backup RADIUS server
Disconnected Connection to the selected server has timed out.
2. Configure the following parameters:
Server Access (Disables or enables the RADIUS server)
Server IP Address (IP address of the RADIUS server)
Key String (The shared secret is a password used by RADIUS to
authenticate the client. ETX-102 encrypts the user-password, if present;
using the secret it shares with the RADIUS server.): Any alphanumeric
string up to 16 characters
Number of retries (The number of retries to be made when sending
request to the RADIUS server): 05
Timeout (The maximum time ETX-102 waits for a single request response
from the RADIUS server (in seconds). After this time the request is
retransmitted.): 060

Authentication Port (The UDP port number to be used for the RADIUS
authentication application. Make sure to define the same value in the
RADIUS server.): any valid UDP port number.
Configuring Control Port Parameters

ETX-102 embedded software enables you to configure the serial port parameters,
which include specifying terminal baud rate, scrolling window size and security timeout.
To access the Control Port menu:

From the System Configuration menu, select Control Port.
The Control Port menu appears (see Figure 4-14).
ETX-102
Configuration>System>Control Port
Terminal Type (VT100)
Data Bits (8)
Parity (None)
Stop Bits (1)
Flow Control (None)
1. Baud Rate >(115200 bps)
2. Set Scrolling Window Size[0 - 11] (4)
3. Security Timeout (min)[0 - 60] (10)
>
Figure 4-14. Control Port Menu
To configure the control port data rate:

1. From the Control Port menu, select Baud Rate.
The Baud Rate menu appears (see Figure 4-15).
2. Select the terminal rate by typing the number corresponding to the desired
value, and pressing <Enter>.
Note
The Baud Rate parameter is masked during Telnet and Web sessions.
ETX-102
Configuration>System>Control Port>Baud Rate (115200 bps)
1. 9600 bps
2. 19200 bps
3. 38400 bps
4. 57600 bps
5. 115200 bps
Figure 4-15. Baud Rate Menu

Setting Scrolling Window Size

User-configurable size of the scrolling window specifies the height of the area
that is reserved for status information. This area is located at the bottom of the
screen.
To set scrolling window size:

From the Control Port menu (Figure 4-14), select Set Scrolling Window Size to
set the size of the status information section at the bottom of the screen in
the range of 0 to 11.
Configuring Security Timeout

The timeout specifies a time interval after which ETX-102 automatically
disconnects from the supervisory terminal or Telnet host if no input from the
user is detected. The timeout value can be in the range of 1 to 60 minutes.
To configure the security timeout:

From the Control Port menu (Figure 4-14), select Security Timeout to set to
in the range of 1 to 60 minutes.
The display is refreshed and a new value appears.
Note
Security timeout value is not valid for Web management, where it is permanently
set to 10 minutes.
4.2 Configuring for Operation

The recommended configuration procedure for ETX-102 includes the following
stages:
1. Configuring device-level parameters (link protection)
2. Configuring network and user Ethernet interfaces at the physical level
3. Configuring internal bridge
4. Configuring QoS parameters.
Configuring the Link Protection

The ETX-102 uses two network link protection modes:
LAG (Link Aggregation Group)
1:1.
Note
Before configuring the link protection make sure that both network ports have
identical bridge port parameters (ingress filtering mode, port VID etc) and are the
members of the same VLAN.
ETX-102 Ver. 3.8 Configuring for Operation 4-17

To select the link redundancy method:

1. From the System menu (Configuration > System), select Protection.
The Protection menu (LAG mode) is displayed (Figure 4-16).
2. From the Protection menu select Redundancy Method and choose the
required method:
LAG Both network links are combined into one virtual group, but only
one link transmits data at a time. If a failure occurs on the transmitting
link, ETX-102 switches to the standby link in the group.
Note
In the LAG mode the first link to have its Administrative Status to be set to Up
becomes an active link of the group and starts data transmission. Refer to the
Configuring Network and User Ethernet Interfaces section below for
instructions on how to change the administrative status of the link.
In the LAG mode both network links receive data, but only one of them
transmits.
1:1 Both network ports operate independently, one of them is active,

the other on standby. The traffic is automatically switched to the
standby port in case the active network port or its link fails.
ETX-102
Configuration>System>Protection
GROUP ID > (1)

Port Members > (1,2)
1. Redundancy Method > (LAG)
2. Wait to Restore (sec) [0-720] ... (0)
>
Figure 4-16. Protection Menu (LAG Mode)
To configure the LAG link protection

From the Protection menu (LAG mode), select Wait to Restore and define a
period of time between link restoration and using the link for the data
transfer.
To configure the 1:1 link protection:

From the Protection menu (1:1 mode), perform the following:
1. Define port recovery mode:
Non-revertive (Traffic keeps on being sent over the secondary port
(network port 2) after the primary port recovery)
Revertive (Traffic is switched back to the primary port (network port
1) after the primary port recovery)
2. Define Wait to Restore time (Period of time between link restoration and
using the link for the data transfer): 0720 sec
4-18 Configuring for Operation ETX-102 Ver. 3.8

3. Define Shut Down Duration upon Flip time (Period of time during which
the failed link suspends its transmission in order to inform the remote
device of the link failure): 030 sec.
4. Select a permanently active network port:
None (None of the network ports is configured as permanently
active)
Port 1 (Port 1 is configured as a permanently active link. Even if port
1 fails, the traffic is not switched to the standby port.)
Port 2 (Port 2 is configured as a permanently active link. Even if port
2 fails, the traffic is not switched to the standby port.)
ETX-102
Configuration>System>Protection
GROUP ID > (1)

Port Members > (1, 2)
1. Redundancy Method > (1:1)

2. Recovery Mode > (Non Revertive)
3. Wait to Restore (sec) [0-720] ... (0)
4. Shut Down Duration Upon Flip (sec)[0-30] ... (0)
5. Set Active Port > (None)
>
Figure 4-17. Protection Menu (1:1 Mode)
Configuring Ethernet Ports at the Physical Layer

ETX-102 includes two SFP-based FE or GbE network ports, one SFP-based user
port, and three 10/100BasetT user ports. The following parameters can be
configured for the Ethernet ports at the physical level:
Flow control as per IEEE 802.3 (network and user ports)
Fault propagation (10/100BaseT ports)
Autonegotiation (10/100BaseT ports)
Maximum advertised capability for autonegotiation procedure
Data rate and duplex mode, when autonegotiation is disabled
Automatic MDIX cross-over function (10/100BaseT ports)
Fault propagation Wait-to-Restore time
Link OAM (802.3ah) mode
Tunneling of management traffic between two devices implementing OAM.

Configuring Network and User Ethernet Interfaces
To configure Ethernet ports:

1. From the Physical Layers menu, select Ethernet.
The Ethernet menu appears (see Figure 4-18).
2. Type f or b to select the Ethernet port.
3. From the Ethernet menu, configure the following:
Administrative Status:
Up (The network port is enabled)
Down (The network port is disabled)
User Name (Description of the port)
Autonegotiation:
Enable (Autonegotiation is enabled)
Disable (Autonegotiation is disabled)
Max Capability Advertised (The highest traffic handling capability to be
advertised during the autonegotiation process. Relevant for the
10/100BaseT ports only.):
10BaseT Half Duplex
10BaseT Full Duplex
100BaseT Half Duplex
100BaseT Full Duplex.
Speed & Duplex (Data rate and duplex mode of the Ethernet port, when
the autonegotiation is disabled. Relevant for the 10/100BaseT ports
only.):
10BaseT Half Duplex
10BaseT Full Duplex
100BaseT Half Duplex
100BaseT Full Duplex.
Flow Control (Data flow control method based on Ethernet Pause frames.
Relevant for the 10/100BaseT ports only.):
Enable (Flow control is enabled)
Disable (Flow control is disabled).
MDIX Auto Cross Over (Correction of connection polarity errors for the
user ports. This allows using straight or crossed cables for connecting
user Ethernet ports.)
Enable (MDIX auto cross-over is enabled)
Disable (MDIX auto cross-over is disabled)

Note Disable the MDIX automatic cross-over function before running the physical
loopbacks on the ETX-102 user ports.
MDIX Manual Switch (User port connection type, when the MDIX
automatic cross-over function is disabled.
Cross (Cross-over connection)
Straight (Straight connection).
Fault Propagation, only for user ports (When enabled, fault propagation
mechanism disconnects the current user Ethernet interfaces, when the
network interface is down.)
Enable (Fault propagation is enabled)
Disable (Fault propagation is disabled).
OAM (802.3ah) (Controls OAM link operation for the current port as per
IEEE 802.3ah requirements):
Enable (OAM (802.3ah) operation is enabled)
Disable (OAM (802.3ah) operation is disabled).
OAM MNG (Controls tunneling of SNMP traffic using OAM 802.3ah
protocol. This parameter is available when the OAM 802.3ah operation is
enabled.)
Enable (SNMP tunneling is enabled)
Disable (SNMP tunneling is disabled).
ETX-102
Configuration>Physical Layers >Ethernet
Interface > (RJ45)

Port Label > (1)
Ethernet Port > (Network 1)
1. Administrative Status (Up)
2. User Name (ETH 1)
3. Auto Negotiation (Disable)
4. Speed & Duplex > (10baseT Half Duplex)
5. Flow Control (Enable)
6. MDIX Auto Cross Over (Disable)
7. MDIX Manual Switch (Cross)
8. OAM (802.3ah) (Enable)
9. OAM MNG (Disable)
Figure 4-18. Ethernet Menu (Network Port)

ETX-102
Configuration>Physical Layers >Ethernet
Interface > (RJ45)

Port Label > (4)
Ethernet Port > (User 2)
1. Administrative Status (Up)
2. User Name ... (ETH 4)
3. Auto-Negotiation (Disable)
4. Speed & Duplex > (10baseT Half Duplex)
5. Flow Control (Enable)
6. MDIX Auto Cross Over (Disable)
7. MDIX Manual Switch (Cross)
8. Fault Propagation (Disable)
9. OAM (802.3ah) (Enable)
10.OAM MNG (Disable)
Figure 4-19. Ethernet Menu (User Port)
Configuring the Fault Propagation Wait-to-Restore Time

If the fault propagation feature is enabled, you can also specify the wait-to-
restore (WTR) time for the user interfaces. WTR is the time period ETX-102 waits
before enabling user interfaces once the network interface is restored.
To configure the fault propagation WTR time:

From the Physical Layers menu (see Figure 4-20), select Fault Propagation
WTR and select the required fault propagation WTR in the range of 03600
seconds (0 disables the WTR).
ETX-102
Configuration>Physical Layers
1. Ethernet >
2. Fault Propagation WTR (sec) [0 3600] ...(0)
Figure 4-20. Physical Ports Menu
Configuring the Bridge

The ETX-102 bridge connects Ethernet ports of the unit. The bridge operates in
VLAN-aware and VLAN-unaware mode. Learning and filtering can be enabled or
disabled. Static MAC addresses are stored in the MAC table. Each bridge port can
be assigned to a VLAN.

To configure the bridge:

1. From the Configuration menu, select Bridge.
The Bridge menu is displayed (see Figure 4-21).
2. From the Bridge menu, configure the following:
VLAN Mode:
Aware (ETX-102 bridge handles VLANs)
Unaware (ETX-102 bridge does not handle VLANs)
Forwarding Mode (Operation mode of the bridge):
Transparent (No filtering is performed. ETX-102 forwards all received
frames.)
Filter (ETX-102 filters traffic according the received MAC addresses)
Aging Time (Amount of time a LAN node (station) is allowed to be
inactive before it is removed from the network): 300 to 4080 seconds.
ETX-102
Configuration>Bridge
1. VLAN Mode (Unaware)

2. Forwarding Mode (Filter)
3. Aging Time[300 - 4080] ...(300)
4. Static MAC Table []>
5. Erase MAC Table
6. Bridge Port >
Figure 4-21. Bridge Menu (VLAN-Unaware)
Configuring MAC Table

You can add static MAC addresses to the ETX-102 MAC table. When the bridge
operates in the VLAN-aware mode, it is possible to assign VLAN ID to a MAC address.
To add a static MAC addresses:

1. From the Bridge menu, select Static MAC Table.
The Static MAC Table appears (see Figure 4-22).
2. From the Static MAC Table, type A to add a static MAC address.
The Static MAC Table display changes, entering the Add mode
(see Figure 4-24).
Select MAC Address, and enter a new MAC address.
Select Received Bridge Port, and choose an ETX-102 interface that this
MAC address will be attached to.
Specify the status of this MAC table entry permanent or forbidden.

If the bridge operates in the VLAN-aware mode, specify VLAN ID with

which frames from the current MAC address are expected to arrive.
Save the changes.
Press <Esc> to return to the Static MAC Table.
To remove a static address from the table:

From the Static MAC Table (Figure 4-22), select a MAC address that you want
to remove and type R.
The static MAC address is deleted from the table.
To delete static addresses from the MAC table:

1. From the Static MAC Table (Figure 4-22), type C to delete all static MAC
addresses.
ETX-102 displays the following message: Are you sure??? (Y/N)
2. Type Y to confirm deletion of all static MAC addresses from the table.
To delete learned addresses from the MAC table:

1. From the Bridge menu, select Erase MAC Table to delete all learned addresses
from the MAC table.
ETX-102 displays the following message: MAC table will be
cleared. Continue??? (Y/N)
2. Type Y to confirm deletion of all learned MAC addresses from the table.
ETX-102
Configuration>Configuration>Bridge>Static MAC Table
MAC Address Received Bridge Port
1 10-00-00-00-00-00 Network
A - Add R Remove C - Clear Table
Figure 4-22. Static MAC Table (VLAN-Unaware)

ETX-102
VLAN ID MAC Address Received Bridge Port
1 1 10-00-00-00-00-00 Network
A - Add R Remove C - Clear Table
Figure 4-23. Static MAC Table (VLAN-Aware)

ETX-102
1. Vlan Id[1 - 4094] (0)
2. MAC Address ... (10-00-00-00-00-00)
3. Status (Permanent)
4. Received Bridge Port > (Network)
5. Save All
>
Figure 4-24. Static MAC Table, Add Mode (VLAN-Aware)
Defining Port 2 as Network or User

Port 2 can be defined as network port 2 or user port 1. When it is configured as a
network port, link aggregation/redundancy becomes available.
To define port 2 type:

1. From the Bridge Port menu (Configuration > Bridge > Bridge Port), type f to
navigate to port 2.
2. Select Bridge Port and define its type: Network 2 or User 1.
You are prompted to confirm the change.
3. Type Y to confirm.
ETX-102 resets automatically with its configuration reset to defaults
(except for management-related parameters).
Configuring Network Bridge Ports

ETX-102 network bridge ports support filtering of incoming user traffic, accepting
all frames or only those that have VLAN tags. The untagged frames can be
assigned PVID and priority by the network bridge ports.
To configure network bridge ports:

1. From the Bridge menu, select Bridge Port.
The Bridge Port menu is displayed (see Figure 4-25).
2. From the Bridge Port menu, type f to select a network bridge port, and
configure the following:
Ingress Filtering (Controls filtering of the incoming user traffic)
Enable (Network bridge port accepts only frames with tags of the
VLANs, which include the network port as a member.)
Disable (Network bridge port accepts all incoming frames)
Accept Frame Type (Specifies the frame types to be accepted by the
network port)
All (Network bridge port accepts all frames (tagged, untagged,
priority-tagged). Untagged and priority-tagged frames receive PVID of
the network bridge port.)

Tag only (Network bridge port accepts only tagged frames, discarding
untagged and priority-tagged).
Note
The Ingress Filtering and Accept Frame Type parameters are available only in
VLAN-aware mode.
Port VID (Port VID to be added by the network bridge port to untagged
and priority-tagged frames): 14094
Default Priority Tag (Default priority tag to be added by the network
bridge port to the incoming untagged frames, or to the frames coming
from the user ports with assigned port priority): 07..
ETX-102
Configuration>Configuration>Bridge>Bridge Port
Port Label
Bridge Port (Network)
1. Ingress Filtering > (Enable)
2. Accept Frame Type (All)
3. Port VID [1 - 4094] ... (1)
4. Default Priority Tag [0- 7] ... (0)
>
f - forward
Figure 4-25. Bridge Port Menu (Network)
Configuring User Bridge Ports

ETX-102 user bridge ports support filtering of incoming traffic, accepting all
frames or only those that have VLAN tags. The incoming frames can be assigned
PVID and priority by the user bridge ports.
To configure user bridge ports:

1. From the Bridge menu, select Bridge Port.
The Bridge Port menu is displayed (see Figure 4-26).
2. From the Bridge Port menu, type f to select the user bridge port that you
intend to configure, and set the following parameters:
Ingress Filtering (Controls filtering of the incoming traffic)
Enable (User bridge port accepts only frames with tags of the VLANs,
which include this user port as a member.)
Disable (User bridge port accepts all incoming frames)
Accept Frame Type (Specifies the frame types to be accepted by the user
bridge port)

All (User bridge port accepts all frames (tagged, untagged,

priority-tagged). Untagged and priority-tagged frames can receive
PVID of the user bridge port.)
Tag only (User bridge port accepts only tagged frames, discarding
untagged and priority-tagged)
Note
The Ingress Filtering and Accept Frame Type parameters are available only in
VLAN-aware mode.
Port VID (Port VID to be added by the user bridge port to the arriving
frames): 14094
Note
PVID operation depends on the tag handling mode:
None PVID is added to untagged and priority-tagged frames only.
Stack (allowed only in VLAN-unaware mode) PVID is added to all frames
(tagged, untagged, or priority tagged) arriving network-to-user. VLAN tag is
removed from user-to-network frames.
Default Priority Tag (Default priority tag to be added by the user bridge
port to untagged frames. No default priority tags are added to frames
arriving with assigned port priority): 05.
Tag Handling (Defines if user ports add port VID only to untagged or to all
arriving frames)
None (PVID is added to the untagged and priority-tagged frames
only)
Stack (PVID is added to all arriving frames).
ETX-102
Port Label (3)
Bridge Port > (User1)
3. Port VID\Stacking VID [1 - 4094] ... (1)
4. Default Priority Tag [0 - 5] ... (0)
5. Tag Handling (None)
>
F - Forward
Figure 4-26. Bridge Port Menu (User 1)
Configuring VLAN Membership

Each ETX-102 port can be defined as a VLAN member. The ports can also be
configured to add or to strip the VLAN tag at the egress.

To configure the VLAN membership:

1. From the Bridge menu, select VLAN Membership.
The VLAN Membership menu is displayed (see Figure 4-27).
2. From VLAN Membership menu, type a to add a new VLAN and enter the new
VLAN number, or type f to select an existing VLAN to which you intend to
assign the ETX-102 port.
3. When the number of the required VLAN is displayed at the top of the menu,
do the following:
Select Egress Tagged Ports to assign network and/or user ports to be the
tagged members of the current VLAN. These ports add the current VLAN
tag to all frames at egress.
Select Egress Untagged Ports to assign network and/or user ports to be
the untagged members of the current VLAN. These ports strip the current
VLAN tag from all frames at egress.
Note
Each port can be an untagged member in only one VLAN.
To assign an ETX-102 port to a VLAN:

1. From the Egress Tagged Ports or Egress Untagged Ports menu, type a to add
a port.
The display changes, entering the Add mode (see Figure 4-27).
a. Select the ETX-102 port range, displayed as [1 3], [1 4] or any other
combination, depending on the number of ports available in ETX-102 and
enter the desired port number.
b. Repeat step 1 for all ETX-102 ports that you intend to define as
egress-tagged or egress-untagged for the current VLAN.
c. Select Save All to save the changes.
d. Press <Esc> to return to the VLAN Membership menu.
e. Save the changes.
To delete ETX-102 ports assigned to VLAN:

1. From the Egress Tagged Ports or Egress Untagged Ports menu, select Delete
Range and specify network or user ports that you intend to disconnect from
the current VLAN and save the changes
The ports which will be disconnected are selected one after another or as a
group in the x-y format in the ascending order.
For example, if you want to disconnect ports 1, 2 and 3 from the VLAN, you
can do it in the following succession: Delete Range 1, Delete Range 2, Delete
Range 3, Save All.
Alternatively, you can specify the port range and do it in just two steps, as
follows: Delete Range 1-3, Save All.
2. Press <Esc> to return to the VLAN Membership menu.

3. Save the changes.

ETX-102
Configuration>Bridge>VLAN Membership>Egress Tagged Ports
1. [1 - 3]... (-)
2. Save All
>
Please select item <1 to 2>
ESC-prev.menu; !-main menu; &-exit; A-add 1 Mngr/s
Figure 4-27. Egress Tagged Ports Menu, Add Mode
Configuring OAM
ETX-102 has the following capabilities for providing operation, administration,
and maintenance (OAM) in packet-switched networks:
Continuity check
Non-intrusive loopback which used to detect loss of bidirectional continuity.
Performance measurements (per service when using the proprietary protocol)
OAM diagnostics (loopback and trace route utility).
To configure the OAM:

1. Define the standard OAM MAC address and EtherType.
2. Assign a name to a Maintenance Domain (MD):
Define an MD format
Specify an MD name
3. Create an EVC (Ethernet Virtual Connection), define its ID and VLAN. The EVC
must be a VLAN member of the network port.
4. Configure MA (Maintenance Association, if the OAM protocol is set to
Standard
5. Configure the MEPs (Maintenance Entity Endpoints)
Assign IDs to the local and remote MEPs
Set OAM destination address type
Define OAM and continuity verification modes
Provide destination addresses for OAM messages
Define an MD level
Set default priority, if you do not intend to define OAM services.
6. Enable OAM services, if the OAM protocol is set to Proprietary
7. Configure the enabled OAM services:
a. Define performance monitoring mechanism
b. Provide service priority

c. Set objectives (thresholds) for measurement parameters.
Defining Standard OAM MAC Address and Ether Type

The standard OAM MAC address and Ether type can be changed to match your
OAM service requirements.
To define standard OAM MAC address and Ether Type:

From the End-to-End menu (Configuration > OAM > End-To-End), configure
the following:
Standard multicast OAM MAC address
Standard OAM EtherType: 0ffff.
ETX-102
Configuration>OAM>End-to-End
1. MD Names >
2. Standard OAM MAC Address ... (01-80-C2-00-00-30)
3. Standard OAM EtherType[0 - ffff] ... (8902)
4. EVCs >
>
Figure 4-28. End-to-End Menu
Assigning a Name to Maintenance Domain (MD)

Maintenance Domain is a domain or part of a domain for which the faults in
connectivity are to be managed. Each MD is administered separately. Each
Maintenance Domain is assigned a Maintenance Domain Name. The name must
be unique amongst all those used or available to an operator, and to facilitate
easy identification of administrative responsibility for the Maintenance Domain.
To assign a name to a maintenance domain:

1. From the MD Names menu (Configuration > OAM > End-To-End >MD Names),
type f or b to select a maintenance domain.
Note MD ID 1 is read-only and its parameters cannot be changed.
2. Type a to add a new name.

3. Define the following:
MD Format (Format of the MD name):
None (No name is defined)
String (Alphanumeric value)
DNS-like (DNS format)
MAC + UINT (MAC and UINT format)

MD Name (Maintenance domain name, according to the selected format).

ETX-102
Configuration>OAM>End-to-End>MD Names
MD ID[1 - 64] ... (2)
1. MD Format > (String)

2. MD Name ... (None)
>
Figure 4-29. MD Names Menu, Add Mode
Configuring the EVC

EVC (Ethernet Virtual Connection) is an association of ETX-102 units used for
OAM message exchange. ETX-102 supports up to 16 EVCs. EVCs can be defined in
the VLAN-aware and VLAN stacking modes only. Changing VLAN mode to
Unaware, deletes all existing EVCs.
To add and configure an EVC:

1. From the EVCs menu (Configuration > OAM > End-to-End > EVCs), type a to
add an EVC.
2. Enter a new EVC number.
3. Type f or b to select an EVC you intend to configure and perform the
following:
4. Select EVC Name and enter an alphanumeric string of up to 100 characters.
This string is unique and it is used for EVC identification in the maintenance
domain (managed network). The EVC name must be the same for the local
and remote units. When used with the proprietary protocol type, EVC names
serve as Maintenance Association identifiers.
Note The network bridge port must be a member in the SP VLAN.
5. Define SP VLAN, VLAN tag attached to OAM messages sent over the current
EVC. The SP VLAN must be different from the host VLAN: 14094.
6. Define the Protocol Type, you can choose the standard protocol or the RAD
proprietary protocol:
Proprietary (RAD proprietary OAM protocol)
Standard (Standard OAM protocol).

ETX-102
Configuration>OAM>End-to-End>EVCs
EVC[1 - 64] ... (1)
1. EVC Name ... (Put your string here)

2. SP VLAN[1 - 4094] ... (0)
3. Protocol Type (Standard)
4. MAID >
5. MEP >
>
Figure 4-30. EVCs Menu
Defining the MA Names

When the OAM protocol is set to Standard, it is necessary to define Maintenance
Association (MA) names. The MAs are Maintenance Entities (MEs) that belong to
the same service in an OAM domain.
To define the MA names:

1. From the MA ID menu (Configuration > OAM > End-To-End > EVCs > MA ID),
type f or b to select a maintenance domain (MD ID). Possible values are 1, 2
or 3.
2. Define the MA format and the MA name:
MA Format (Format of the MA name):
String (Alphanumeric value)
Primary VLAN
Unsigned Int 16
ICC (According to ITU-T Y.1731 requirements).
MA Name (Maintenance association name, according to selected format).
ETX-102
Configuration>OAM>End-to-End>EVCs>MAID
EVC ID ... (test)

1. MD ID[1 64] ... (Put your string here)
MD Format
2. MA Format
3. MA Name
>
F-Forward MD ID; B-Backward MD ID; S-Save


Figure 4-31. MAID Menu
Configuring the MEP

Once the EVC was created, it is necessary to define its MEPs (Maintenance
Endpoints) and configure other OAM parameters.
To configure the MEP:

From the MEP menu (Configuration > OAM > End-to-End > EVCs > MEP),
define the following:
Local MEP ID (Identification number of the local maintenance endpoint. It
must be different from the remote MEP ID and unique for the
maintenance domain.): 18191
OAM Destination Address Type (Type of the MAC address to which the
OAM messages are sent. If the multicast OAM destination address is
selected, you can define up to five remote MEPs.):
Multicast (multicast address defined in the Standard OAM MAC
address)
Unicast (User-defined unicast address)
Remote MEP ID (Identification number of the remote maintenance
endpoint, terminating the maintenance entity. It must be different from
the local MEP ID and unique for the maintenance domain.): 18191
1. From the Remote ID menu (Configuration > OAM > End-To-End > EVCs
> MEP > Remote ID), type a to add a new remote MEP.
2. Type 1 to add the first remote MEP and enter its number in the
18191 range.
3. If the OAM destination address type is set to Multicast, type a, then
type 2 to add the second remote MEP and enter its number.
4. Repeat steps 1 and 2 to define up to five remote MEPs.
6. To delete remote MEPs, select Delete Range and enter the remote
MEP ID that you intend to delete. You can also enter ID ranges to
delete multiple remote MEPs. For example, entering 1100 in the
Delete Range line, deletes all MEPs within the 1100 range, inclusive.
MD Level (OAM Maintenance Domain level. Domains discard OAM frames
belonging to lower level domains; frames belonging to higher level
domains are passed transparently. MD level of the Proprietary OAM mode
it is permanently set to 3.): 07
OAM Mode (OAM behavior):
Disabled (No continuity check is performed)
Initiate (ETX-102 initiates and reacts to OAM CC messages)
React (ETX-102 only reacts to OAM CC messages, without initiating
them)

Continuity Verification Mode (Continuity check method. The Continuity

Verification Mode can be configured when the OAM Mode is set to Initiate
or React and the OAM Mode is Proprietary.):
Disabled (No continuity check is performed)
LB-based (Continuity check is performed via loopback messages)
CC-based (Continuity check is performed via received OAM packets)
Note
When the OAM mode is set to Initiate, the continuity verification mode can be
either LB- or CC-based only. In the React OAM mode only CC-based verification is
available.
OAM Destination MAC Address (User-defined MAC address to which the

OAM messages are sent. It is available only if the OAM destination
address type is set to Unicast.)
Default Priority (Priority of the OAM CC messages): 07
CC Interval (Interval between CC messages): 100 ms, 1 sec, 10 sec, 1 min,
10 min.
ETX-102
Configuration>OAM>End-to-End>EVCs>MEP
EVCs ID ... (1)
1. Local ID [1-8191] ... (0)

2. OAM Destination Address Type (Unicast)
3. Remote ID > (1)
4. MD Level {0-7] ... (3)
5. OAM Mode > (Initiate)
6. OAM Destination MAC Address ... (00-00-00-00-00-00)
7. Default CC Priority[0 - 7] ... (0)
8. CC Interval > (1 Second)
>
Figure 4-32. MEP Menu
Configuring OAM Services

Three OAM services are defined automatically for each created proprietary EVC.
Each service has its own identification number (13), priority level and set of
variation objectives (thresholds).
To configure the OAM services:

1. From the Service menu (Configuration > OAM > End-to-End > EVCs > MEP >
Services), select one of the three available services by typing f or b.
2. Define the following parameters of the selected service:

Performance Monitoring:
Enabled (Performance monitoring is enabled)
Disabled (Performance monitoring is disabled)
Service Priority (P (priority) bit value sent in OAM messages originating
from the selected service): 07
Delay Objective (Delay objective for the specified service. You can display
the total number of frames above or below defined delay objective for the
15-min or 24-hour intervals via Connection Statistics screen, see
Chapter 5).
Delay Variation Objective (Delay variation objective for the specified
service. You can display the total number of frames above or below
defined delay variation objective for the 15-min or 24-hour intervals via
Connection Statistics screen, see Chapter 5).
Event Report (OAM counter to be monitored and its rising/falling
thresholds, and sampling intervals. See Chapter 5 for the detailed
description.
ETX-102
Configuration> OAM>End-to-End>Services
Service[1 - 3] ... (1)
1. Performance Monitoring (Enabled)

2. Service Priority[0 - 7] ... (0)
3. Delay Objective(msec) ... (0)
4. Delay Variation Objective(msec) ... (0)
Event Report
5. Frame Loss Ratio >
6. Frames Above Delay >
7. Frames Above Delay Variation >
8. Unavailability Ratio >
>
FForward; S-Save
Figure 4-33. Services Menu
Configuring Quality of Service (QoS)

ETX-102 supports configuration of two QoS categories: priority and rate
limitation. QoS configuration is performed via the QoS menu (Main menu > QoS).
Configuring the Traffic Priority

ETX-102 provides four priority queues for each user port. User traffic can be
prioritized according to the VLAN priority, DSCP, IP TOS or per port basis.

To select the traffic priority type:

1. From the Configuration menu, select QoS.
The QoS menu is displayed.
2. From the QoS menu, select Priority.
The Priority menu is displayed (see Figure 4-34).
3. From the Priority menu, select Classification and choose one of the following
traffic prioritization methods:
802.1p (Traffic is prioritized according to VLAN priority)
DSCP frame DSCP field (Traffic is prioritized according to the
Differentiated Services Codepoint, as specified in RFC 2474).
TOS (Traffic is prioritized according to IP ToS field)
Per Port (Traffic is prioritized according to port default priority).
ETX-102
Configuration>QoS>Priority
1. Classification >(802.1p)
2. Mapping >
S - save
>
Figure 4-34. Priority Menu
To define the priority mapping:

1. Once the priority type is defined, select Mapping from the Priority menu.
The Mapping menu appears. The Mapping menu changes according to the
selected priority type (802.1p, DSCP, TOS, per port). Figure 4-35
illustrates the Mapping menu for the 802.1p priority.
2. From the Mapping menu, define the following:
802.1p priority assign each priority tag, supported by IEEE 802.1p (17)
to a specific priority queue (traffic class 0 (lowest), traffic class 13)
DSCP priority assign each DS codepoint (063) to a specific priority
queue (traffic class 0 (lowest), traffic class 13)
TOS priority assign each IP ToS field value (07) to a specific priority
queue (traffic class 0 (lowest), traffic class 13)
Per port priority assign priority to the user traffic according to the
default priority of a bridge port.

ETX-102
Configuration>Configuration>QoS>Priority>Mapping (802.1p)
1. User priority 0 >(Traffic class 0)

>
S - Save
Figure 4-35. Mapping (802.1p) Menu
Configuring Rate Limitation

ETX-102 supports data rate limitation at the egress and ingress of the network
and user ports. ETX-102 limits the data rate proper, without taking into account
Ethernet frame intergaps.
Configuring Ingress Rate Limitation

Via ingress rate limitation the user controls the rate of traffic received at the
network and user interfaces. The traffic that exceeds the selected rate limitation
value for an ETX-102 port is dropped. In addition to that ETX-102 defines
maximum packet burst for each rate limitation value. This enables service
providers to compensate their subscribers for underused bandwidth by allowing
temporary traffic bursts. Also, the rate limitation can be applied to all packets or
to certain types (broadcast, multicast, etc).
To configure the ingress rate limitation:

1. From the Rate Limitation menu (Configuration > QoS > Rate Limitation),
select Ingress.
The Ingress menu is displayed (Figure 4-36).
2. From the Ingress menu, type f to select the network or user port to which
you intend to apply rate and burst limitation.
3. Select Rate Limitation and define the maximum ingress data rate allowed on
the port (see Table 4-2).
4. If you defined a rate limitation, select Burst Size and define the maximum
allowed size of the packet buffer (in kilobytes) to be used by the port when
traffic bursts occur. See Table 4-2 for the allowed burst values depending on
configured port rate limitation. Traffic bursts are permitted only if the traffic
has been sent to the ETX-102 below the rate limit for a certain period of
time.

Note The following rate/burst limit combinations are not allowed:

12 kilobyte burst for 45 Mbps rate
12 kilobyte burst for 71 Mbps rate
12 and 24 kilobyte burst for 90 Mbps rate.
5. Select Limit Packet Type and choose a packet type to which the rate/burst
limitation is to be applied:
All The limitation is applied to all arriving packets
Broadcast The limitation is applied to broadcast packets
Multicast & Flooded The limitation is applied to broadcast, multicast
and flooded packets
Broadcast & Multicast The limitation is applied to broadcast and
multicast packets
Broadcast The limitation is applied to broadcast packets.
ETX-102
Configuration>QoS>Rate Limitation>Ingress
Port Label > (1)
Ethernet Port > (Network)
1. Rate Limitation > (2Mbps)

2. Burst Size (in kB) > (12K)
3. Limit Packet Type > (All)
>
F - Forward S Save
Figure 4-36. Ingress Rate Limitation Menu
Table 4-2. Rate and Burst Limitation
Burst Size Burst Size

Rate Limit Rate Limit
12 kB 24 kB 48 kB 96 kB 12 kB 24 kB 48 kB 96 kB
1 Mbps 20 Mbps
2 Mbps 25 Mbps
3 Mbps 30 Mbps
4 Mbps 35 Mbps
5 Mbps 40 Mbps
6 Mbps 45 Mbps X
7 Mbps 50 Mbps
8 Mbps 60 Mbps
9 Mbps 71 Mbps X

Burst Size Burst Size

Rate Limit Rate Limit
12 kB 24 kB 48 kB 96 kB 12 kB 24 kB 48 kB 96 kB
10 Mbps 83 Mbps
15 Mbps 90 Mbps X X
Configuring Egress Rate Limitation
To configure the egress rate limitation:

1. From the QoS menu, select Rate Limitation.
The Rate Limitation menu is displayed.
2. From the Rate Limitation menu, select Egress.
The Egress menu is displayed.
3. From the Egress menu, type f to select the network or user port to which you
intend to apply rate limitation.
4. Select Rate Limitation and define the maximum egress data rate allowed on
the port (see Table 4-2).
ETX-102
Configuration>QoS>Rate Limitation>Egress
Port Label > (1)
Port > (User 1)
1. Rate Limitation > (No Limit)

>
F - Forward S Save
Figure 4-37. Egress Rate Limitation Menu
4.3 Additional Tasks

This section describes additional operations supported by the ETX-102
management software, including the following:
Displaying inventory
Displaying ETX-102 status at the system, physical, and application levels
Setting data, time, and NTP
Changing user names and passwords
Configuring Syslog parameters
Transferring software and configuration files
Resetting the unit.
4-40 Additional Tasks ETX-102 Ver. 3.8

Displaying Inventory
The ETX-102 inventory displays description of the unit, its hardware revision and
power supply type.
To display the ETX-102 inventory:

1. From the Main menu, select Inventory.
The Inventory menu appears (see Figure 4-38).
2. In the Inventory screen, use the arrow keys to navigate between the pages.
ETX-102
Inventory
Id Description Vendor Type Class Entity Name

1 RAD.ETX-102.Chassis 00 3 ETX-102
2 RAD.ETX-102.Power Supply 00 6 Power Supply
| 3 RAD.ETX-102.Port 00 10 Network Port 1
v 4 RAD.ETX-102.Port 00 10 Network Port 2
5 RAD.ETX-102.Port 00 10 User Port 1
->>
>
Figure 4-38. Inventory Screen
Displaying Status
The ETX-102 software provides access to the following status information:
System level MAC address, presence of SSL/SSH security keys, connection
status, system uptime period, list of managers currently connected to
ETX-102, link protection status
Physical ports Ethernet and SFP status
OAM level EVC and link (802.3ah) status
Bridge level MAC table, VLAN table.
The status information is available via the Monitoring menu.
Displaying System Status Information

System menu specifies MAC address of the ETX-102 unit and provides access to
the information on the interface connection status, SSL/SSH security keys,
currently connected managers and link protection status for 1:1 redundancy
mode. For description of ETX-102 system messages, which are displayed via the
Event Log screen, refer to Chapter 5.
ETX-102 Ver. 3.8 Additional Tasks 4-41

Displaying Interface Connection Information
To display interface connection information:

1. From the Monitoring menu, select System.
The System menu is displayed (see Figure 4-39).
The System menu includes the following information:
MAC address of ETX-102
Presence of SSL/SSH security keys.
2. From the System menu, select Connection Status.
The Connection Status screen is displayed (see Figure 4-40).
The Connection Status screen includes the following information:
Description Ethernet Network Port or Ethernet User Port
Type Type of the interface according to the IF MIB
Status Administrative status of the link (Up or Down), as set via the
Ethernet network (Figure 4-18) and Ethernet user (Figure 4-19) menus.
Operation Actual operational status of the link (Up or Down).
3. From the Connection Status screen, type R to refresh the display.
ETX-102
Monitoring>System
MAC Address (00-22-F4-27-F4-68)

Security key ()
1. Connection Status []
2. Connected Managers >
3. Event Log >
4. Protection Status >
>
Figure 4-39. System Menu
ETX-102
Monitoring>System>Connection Status
Index Description Type Admin Status Operation
1 ETHERNET NETWORK PORT fastEtherFx Up Up
2 ETHERNET USER PORT 1 fastEther Up Down
3 ETHERNET USER PORT 2 fastEther Up Up
R - Refresh Table
Figure 4-40. Connection Status Screen

Displaying List of Connected Managers
To display list of managers currently connected to ETX-102:

From the System menu (Figure 4-39), select Connected Managers.
The Connected Managers screen is displayed (Figure 4-41).
The Connected Managers screen includes the following information:
IP Address IP address of the connected remote agent. For an ASCII
terminal connection (UART), this field remains empty.
Terminal Type Type of the terminal used by the manager (UART, Telnet,
SSL, SSH)
User Name The login user name.
ETX-102
Monitoring>System>Connected Managers
Index IP Address Terminal Type User Name
1 UART su
2 158.15.163.20 SSH su
3 158.15.163.30 SSL user
4 158.15.163.40 Telnet user
R - Refresh Table
Figure 4-41. Connected Managers Screen
Displaying the Link Protection Status

When the network port redundancy is configured to the 1:1 mode, it is possible
to display the current protection status.
To display the link protection status:

From the System menu (Figure 4-39), select Protection Status.
The Protection Status screen is displayed (see Figure 4-42).
The Protection Status screen includes the following information:
Active Port Currently active network port.
ETX-102
Monitoring>System>Protection Status
GROUP ID > (1)
Port Members > (1, 2)
Active Port (1)
Figure 4-42. Protection Status Screen

Displaying the Physical Layer Status

You can view the status of the Ethernet connections at the physical level. For
description of ETX-102 Ethernet statistic data, refer to Chapter 5. In addition, you
can access the SFP status information.
Displaying the Ethernet Physical Layer Information
To display the physical layer information:

1. From the Monitoring menu, select Physical Layers.
The Physical Ports menu is displayed.
2. From the Physical Ports menu, select Ethernet Status.
The Ethernet Status screen is displayed (see Figure 4-43).
3. From the Ethernet Status screen, type F to toggle between the network and
user Ethernet ports.
The Ethernet Status screen includes the following information:
Port Type Fiber optic interface characteristics of the current port
Administrative Status Administrative status of the link (Up or Down), as
set via the Ethernet network (Figure 4-18) and Ethernet user
(Figure 4-19) menus.
Operational Status Actual operational status of the link (Up or Down)
Actual Speed & Duplex Current data rate and duplex mode of the link
Actual Flow Control Current flow control status (Enable or Disable).
ETX-102
Monitoring>Physical Layers>Ethernet Status
Port Label > (1)

Port Type (100FX SFP Not Install)
Administrative Status (Down)
Operational Status > (Not Present)
Actual Speed & Duplex > (100Mbps - Full Duplex)
Actual Flow Control (Disable)
>
F - Forward
Figure 4-43. Ethernet Status Screen
Displaying SFP Information

ETX-102 identifies the SFPs inserted in its network and user ports and displays
the link status information, as well as the optical parameters of the transceivers.

Note When managing ETX-102 via SNMP, increase the NMS timeout period to ensure
correct retrieval of the SFP status information.
To display the SFP link status information:

From the Link Status screen (Monitoring > Physical Layer > SFP > Link Status),
type f or b to toggle between the available user or network ports.
The Link Status screen includes the following information:
SFP connector type
Manufacturers name
Manufacturers SFP designation
Typical maximum range in kilometers
Wavelength
Fiber type.
ETX-102
Port Label (1)

Ethernet Port (Network 1)
Connector Type (SC)

Manufacturer Name (RAD)
Manufacturer PN (1234)
Typical Max. Range ... (20km)
Wave Length > (1310nm)
Fiber Type > (MM)
>
F - Forward
Figure 4-44. SFP Link Status Screen
To display the current optical parameters of the SFPs:

1. From the Optical Parameters screen (Monitoring > Physical Layer > SFP >
Optical Parameters), type f or b to toggle between the available user or
network ports.
The Optical Parameters screen includes the following information:
SFP transmit optical power (-40 dBm to + 8.2 dBm at 0.1 dBm resolution)
Laser bias current (0 mA to 131 mA at 0.1 mA resolution)
Laser temperature (0 C to 100 C at 1 C resolution)
SFP receive optical power (-40 dBm to + 8.2 dBm at 0.1 dBm resolution)
Internally measured transceiver supply voltage (-40 dBm to + 8.2 dBm at
0.1 dBm resolution)
2. Select History to display the minimum and maximum values recorded for each
optical parameter.

ETX-102
Port Label (1)

TX Optical Power ... (-6.1 dBm)

LASER Bias ... (1.7 mA)
LASER Temp ... (33 C/ 93 F)
Rx Optical Power ... (-23.5 dBm)
Supply Voltage ... (3.31 V)
1. History []
>
F - Forward
Figure 4-45. SFP Link Status Screen
Displaying EVC Connection Status

At the connection level ETX-102 provides information on the EVC ID, EVC VLAN
and EVC status.
To display the EVC connection status information:

1. From the End-to-End menu (Monitoring > OAM > End-to-End), select Status.
The EVC Connection Status menu is displayed (see Figure 4-46).
2. From the End-to-End Status screen type F or B to toggle between the active
EVCs.
ETX-102
Monitoring>OAM>End-to-End>Status
EVC ID ... (EVC1)
EVC SP VLAN[1 - 4094] ... (1)
EVC Status > (Not Applicable)
1. EVC[1 - 64] ... (1)

F - Forward; B - Backward
Figure 4-46. End-to-End Status Screen
Displaying the Link Status

At the link level ETX-102 provides status information according to the IEEE
802.3ah requirements. The 802.3ah link status collection must be enabled at the
physical level for each ETX-102 network and user interface.

To display link OAM status:

1. From the Link (802.3ah) menu (Monitoring > OAM > Link (802.3ah)), select
Status.
The Link (802.3ah) Status screen is displayed.
2. From the Link (802.3ah) Status screen, type F to toggle between the network
and user Ethernet ports.
The Link (802.3ah) Status screen includes the following information:
Local Discovery State (Detection of an OAM sublayer presence in remote
unit)
Remote Revision (Current revision of information TLV)
Remote MAC Addr. (MAC address of remote unit)
Remote Capabilities (OAM capabilities of remote unit):
Vars Retrieval
Link Events
Loopback
Unidirectional
OAM Mode.
ETX-102
Monitoring> OAM> Link (802.3ah)>Status
Port Label > (1)

Local OAM mode > (Active)

Local Discovery State > (Passive Wait)
Remote revision > (0)
Remote Mac Addr. (00-00-00-00-00-00)
Remote Capabilities
Vars Retrieval > (Supported)
Link Events > (Supported)
Loopback > (Supported)
Unidirectional > (Supported)
Remote OAM mode > (Active)
F- Forward
Figure 4-47. Link (802.3ah) Status Screen

Displaying the Bridge Level Status

At the bridge level ETX-102 provides information on the MAC addresses (static
and learned), their bridge ports, and VLAN assignments (VLAN-aware mode). It is
also possible to display VLAN table, summarizing information on all existing
VLANs, member ports, and port egress tagging mode (tagged or untagged). In
addition, the link aggregation status information is available
To display the MAC table:

1. From the Monitoring menu, select Bridge.
The Bridge menu appears.
2. From the Bridge menu, select MAC Table.
The MAC Table screen appears (see Figure 4-48).
The MAC Table screen includes the following information:
MAC Address Existing MAC address
Status Static or Learned
Bridge Port User or Network
VLAN A VLAN the current MAC address belongs to (VLAN-aware mode only).
3. Type R to refresh the MAC table.
ETX-102
Monitoring>Bridge>MAC Table
MAC Address Status Bridge Port VLAN
10-00-00-00-00-00 Static Network 5
10-00-00-00-00-01 Learned User1 7
R - Refresh table
Figure 4-48. MAC Table
To display the VLAN table:

From the Bridge menu, select VLAN Table.
The VLAN Table screen appears (see Figure 4-49).
The VLAN Table screen includes the following information:
VLAN ID
Egress tagging mode of a port.

ETX-102
Monitoring>Bridge>VLAN Table
Network Port User Port 1 User Port 2 User Port 3 User Port 4
VLAN 1 tag tag
VLAN 1024 untag
Figure 4-49. VLAN Table
Setting the Date, Time and NTP Server Parameters

You can set the date and time for the ETX-102 internal real-time clock. In
addition, you can add an NTP server, to lock ETX-102 to a reliable clock source.
To set date, time and NTP server parameters:

1. From the System menu, select Date/time.
The Date/Time menu appears (see Figure 4-50).
2. From the Date/Time menu, select Time, and enter the current time in the
hh:mm:ss format.
3. Select Date, and enter the current date in the yyyy:mm:dd format.
4. Select NTP Mode and enable (Unicast Client) or disable it.
5. Select NTP Server IP Address and define the IP address of the NTP server.
6. Select GMT (+/- XX) and define time zone in reference to Greenwich Mean
Time (GMT) with an hour resolution: -12 to +12.
7. Select NTP Update Interval and define a period of time after which ETX-102
polls the NTP server: 11440 minutes.
ETX-102
Configuration>System>Date/Time
1. Time <HH:MM:SS> ... (09:12:06)

2. Date <YYYY-MM-DD> ... (2004-01-18)
3. NTP Mode > (Unicast Client)
4. NTP Server IP Address ... (0.0.0.0)
5. GMT (+/- XX) > (0)
6. NTP Update Interval (Min)[1 1440] ... (1)
>

Figure 4-50. Date/Time Menu

Configuring User Access

ETX-102 management software allows you to define new users, their
management and access rights. Only superusers (su) can create new users, the
regular users are limited to changing their current passwords, even if they were
given full management and access rights. Up to eight users can be created in
addition to the user and su users that exist by default.
To add a new user:

1. Make sure that you logged in as su.
2. From the Management Access menu, select User access.
The User Access menu is displayed (see Figure 4-51).
3. From the User Access menu, do the following:
Select User name, and enter a name for a new user.
Select Permission, and specify the users access rights (full control or
read-only).
Select Access, and specify the users access methods (ASCII terminal,
Telnet, Web browser, Telnet and Web browser, or all of them).
Select su password, and enter your current superuser password.
Select New password, and assign a password to a new user name.
Select Confirm and re-enter the new user password to confirm it.
Save new settings by typing S, when asked.
To delete an existing user:

From the User Access menu, do the following:
Type F to display a user that you intend to delete.
Select su password, and enter your current superuser password.
Type D to delete the current user.
ETX-102
Configuration>System>Management>Management access>User access
1. User name ... (su)

2. Permission > (Full Control)
3. Access > (All)
4. su password ... ()
5. New password ... ()
6. Confirm New Password ... ()
>

Figure 4-51. User Access Menu

Configuring Syslog Parameters

To allow logging/sharing of system events on an external server, you need to
configure the Syslog server parameters.
To configure the Syslog parameters:

From the Syslog menu (Configuration > System > Syslog), configure the
following:
Device Logging Status (Enables or disables event logging):
Enable (ETX-102 logs events onto Syslog server)
Disable (ETX-102 logs the events internally)
Server IP Address (IP address of the Syslog server to which the event logs
are sent): 0.0.0.0255.255.255.255
Server UDP Port (The UDP port of the Syslog server): 165535
Device UDP Port (The local UDP port from which the Syslog messages are
sent: 165535
Note The UDP port values cannot be changed when the logging status is enabled.
Facility (The software module, task or function from which the Syslog
messages are sent): Local 17
Severity Level (Only events with the severity which equals or exceeds the
selected severity level are sent):
Critical corresponds to the Emergency (0) severity level of Syslog
Major corresponds to the Alert (1) and Critical (2) severity levels of
Syslog
Minor corresponds to the Error (3) severity level of Syslog
Warning corresponds to the Warning (4) severity level of Syslog
Event corresponds to the Notice (5) severity level of Syslog
Info corresponds to the Informational (6) severity level of Syslog
Debug corresponds to the Debug (7) severity level of Syslog.
Configuration>System>Syslog
1. Device logging status > (Disable)

2. Device UDP port > (514)
3. Facility > (Local 1)
4. Severity level > (Major)
5. Server Parameters >
>
Figure 4-52. Syslog Menu

To configure a Syslog server:

From the Server Parameters menu (Configuration > System > Syslog > Server
Parameters), configure the following:
Server Sequence Number (Sequence number of the Syslog server)
Server Access (Controls the access to the Syslog server):
Enable (Access to the Syslog server is enabled)
Disable (Access to the Syslog server is disabled)
Server IP Address (IP address of the Syslog server)
Server UDP Port (UDP port of the Syslog server): 165535
Configuration>System>Syslog>Server Parameters
1. Server Sequence Number ... (1)

2. Server Access > (Disable)
3. Server IP Address ... (0.0.0.0)
4. Server UDP Port[1 65535] ... (514)
>
Figure 4-53. Syslog Server Parameters Menu
Transferring Software and Configuration Files

This section presents procedures for installing new software releases into the
ETX-102 units and transferring configuration files.
ETX-102 stores two software versions, each of them in one of the two 1.15 MB
partitions of its flash memory, which also contains a boot program. The software
is stored in compressed format. The main version is decompressed and loaded
into the ETX-102 RAM upon power-up. The backup software is kept for backup
purposes. If the main software becomes corrupted, you can swap it with the
backup. By default, ETX-102 is delivered with active software only.
New software releases are distributed as *.img files, which are downloaded to
ETX-102. When starting a download, ETX-102 erases the current backup and
places the new software in the backup partition. When downloading is complete,
the unit checks the integrity of the new software file. If it is correct, the backup
and active files are swapped. The new software release becomes active and the
former active software becomes the backup. If a failure occurs during
downloading, the new version is erased. In this case, only one version is left
stored in the flash memory. The backup software can be downloaded to the unit
and swapped with the main software later.
Configuration files can be uploaded for storage and backup.
Management software allows file transfer via TFTP only. The software files can
also be downloaded to ETX-102 via Boot Manager, using XMODEM or TFTP. For
details on upgrading the device software, refer to Chapter 6.

To transfer files via TFTP:

1. From the Main menu, select Utilities.
The Utilities menu appears.
2. From the Utilities menu, select File Utilities.
The File Utilities menu appears.
3. From the File Utilities menu, select S/W & File Transfer using TFTP.
The S/W & File Transfer using TFTP menu is displayed (see Figure 4-54).
4. From the S/W & File Transfer using TFTP menu, perform the following:
Select File Name, and enter a file name:
For downloading, you specify name of the file, which is to be
downloaded to ETX-102.
For uploading, you specify a name, under which the file is going to be
saved on the remote server.
Select Command to start the desired procedure:
No Operation (TFTP file transfer is disabled)
Software Download (Transferring a software file from the TFTP server
to ETX-102)
Software Upload (Transferring a software file from ETX-102 to the
TFTP server)
Configuration Download (Transferring a configuration file from the
TFTP server to ETX-102)
Configuration Upload (Transferring a configuration file from ETX-102
to the TFTP server)
Software Download and Reset (Transferring a software file from the
TFTP server to ETX-102 and resetting the unit)
Software Download to Backup (Transferring a software file from the
TFTP server to the backup partition of ETX-102).
Select Server IP, and enter IP address of TFTP server.
Define Retry Timeout (Interval between connection retries in seconds).
Define Total Timeout (TFTP connection timeout in seconds)
Select Save to save the changes.
ETX-102 starts file transfer.
View status of the current TFTP transfer:
TFTP Starting Upload
TFTP Starting Download
TFTP Upload Failed
TFTP Download Failed.

ETX-102
Utilities>File Utilities>S/W & File Transfer using TFTP
1. File name ... (FILE.IMG)

2. Command > (No Operation)
3. Server IP ... (0.0.0.0)
4. Retry Timeout(sec)[0 - 1000] ... (1)
5. Total Timeout(sec)[0 - 1000] ... (5)
6. View Transfer Status >
>
Figure 4-54. S/W & File Transfer using TFTP Menu
Swapping Software Files

When the software file is downloaded to the backup partition, it can be swapped
with the main software file.
To swap software files:

1. From the File Utilities menu, select Swap Main Application File With Backup.
ETX-102 displays the following message: Backup application file
will be active after reset. Continue ??? (Y/N).
2. Type Y to complete the swap.
Resetting ETX-102
ETX-102 supports two types of reset:
Reset to the default setting
Overall reset of the device.
Resetting to Factory Defaults

You can reset ETX-102 to its default settings. All configuration parameters can be
reset to their default values, or you can reset ETX-102 without affecting its
management settings (host IP address, mask, default gateway, and the network
managers).
To reset ETX-102 to the default settings:

1. From the System menu, select Factory Default.
The Factory Default menu is displayed (see Figure 4-55).
2. From the Factory Default menu, do the following:
Select Full to reset all configuration parameters to their defaults
Select Except Management to reset all configuration parameters, except
for the management settings.

ETX-102 displays the following message: Configuration will be

lost and system will be reset. Continue??? (Y/N).
3. Type Y to confirm the reset.
ETX-102 performs the specified type of reset.
ETX-102
Configuration>System>Factory default
1. Full
2. Except management
>
Figure 4-55. Factory Default
Resetting the Unit

You can perform an overall reset of ETX-102.
To reset ETX-102:
1. From the Utilities menu (Main menu>Utilities), select Reset.
The following confirmation message appears: System will be reset.
Continue??? (Y/N)
2. Type Y to confirm the reset.


Chapter 5
Diagnostics and
Troubleshooting
This chapter describes how to:
Display system messages
Monitor performance
Run diagnostic tests.
5.1 Monitoring Performance

Performance monitoring data is collected at the EVC and physical levels.
Displaying End-to-End Statistics

You can display end-to-end connectivity and performance monitoring data for the
existing EVCs and their services. The statistics are available for the 15-minute and
24-hour periods.
To display the OAM statistics:

1. From the End-To-End menu (Monitoring > OAM > End-to-End), select
Statistics.
The Statistics menu is displayed.
2. From the Statistics menu, select the following:
15 Min Intervals (OAM statistics for a selected 15-min interval)
24 Hours Counters (OAM statistics for the last 24 hours)
Service Counters (Total OAM statistics collected since the service was
enabled)
3. Selected OAM statistic screen is displayed (see Figure 5-1 and Figure 5-2).
Table 5-1 and Table 5-2 explain the OAM statistic parameters.
4. Type f or b to select an EVC.
5. Type Ctrl + f or Ctrl + b to select an interval (196).
Note
No interval selection is available for the 24-hour statistics.
ETX-102 Ver. 3.8 Monitoring Performance 5-1

Chapter 5 Diagnostics and Troubleshooting Installation and Operation Manual
ETX-102
Monitoring>OAM>End-To-End>Statistics>15 Min. Intervals
Frames Above Delay Obj.... (0) Elapsed Time ... (102767)
Frames Below Delay Obj.... (0)
Frames Above DV Obj. ... (0) Min. RT Delay (Msec) ... (0.0)
Frames Below DV Obj. ... (0) Avg. RT Delay (Msec) ... (0.0)
Frames Transmitted ... (101902) Max. RT Delay (Msec) ... (0.0)
Frames Loss ... (0)
Unavailable Seconds ... (101899) Avg. DV ... (0.0)
Max. DV ... (0.0)
1. Interval ... (0)
2. EVC ... (1)
3. Service ... (1)
>
F - Forward(EVC); B - Backward(EVC); ^F - Forward(Int.); ^B - Backward(Int.)
Figure 5-1. End-to-End Statistics (15-Minute Interval)
Table 5-1. OAM Statistic Parameters
Parameter Description
Frames Above Delay Obj. Number of frames that exceeded delay objective
Frames Below Delay Obj. Number of frames below or equal delay objective
Frames Above DV Obj. Number of frames that exceeded delay variation objective
Frames Below DV Obj. Number of frames below or equal delay variation objective
Frames Transmitted Total number of OAM frames transmitted in the current interval
Frames Lost Number of frames lost in the current interval
Unavailable Seconds Number of seconds during which the service was unavailable in the current
interval
Elapsed Time Time (in seconds) elapsed from beginning of the interval 0900
Min. RT Delay Minimum round trip delay (in mseconds) calculated in the interval (or up to
elapsed time in current interval)
Avg. RT Delay Average round trip delay (in mseconds) calculated in the interval (or up to
Max. RT Delay Maximum round trip delay (in mseconds) calculated in the interval (or up
to elapsed time in current interval)
Avg. DV Average delay variation (in mseconds) calculated in the interval (or up to
Max. DV Maximum delay variation (in mseconds) calculated in the interval (or up to
5-2 Monitoring Performance ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 5 Diagnostics and Troubleshooting
ETX-102
Monitoring>OAM>End-To-End>Statistics>Service Counters
EVC ... (1)
Service ... (1)
OAM transmitted frames counter... (2087328632)

OAM Frames lost counter ... (0
OAM Frame loss ratio(*E-10) ... (0)
Elapsed time ... (1487)
Unavailable seconds ... (0)
Unavailability ratio(*E-10) ... (0)
>
F - Forward(EVC); B - Backward(EVC)
Figure 5-2. End-to-End Service Counters
Table 5-2. Service OAM Statistic Parameters
OAM Transmitted Frames Counter Total number of OAM frames transmitted since the service was
enabled
OAM Frames Loss Counter Total number of OAM frames lost since the service was enabled
OAM Frame Loss Ratio Total number of lost OAM frames divided by total number of
transmitted OAM frames since the service was enabled
Elapsed Time Time (in seconds) elapsed since the service was enabled
Unavailable Seconds Total number of unavailable seconds since the service was enabled
Unavailability Ratio Total number of unavailable seconds divided by elapsed time
Displaying Ethernet Statistics

You can display statistic data for the network and user Ethernet ports at the
physical layer.
To display the Ethernet statistics:

1. From the Physical Layers menu, select Ethernet Statistics.
The Ethernet Statistics screen appears (see Figure 5-3).
2. From the Ethernet Statistics screen, type f or b to toggle between network
and user interface statistics. Table 5-3 describes the Ethernet statistic
registers.
3. Type Ctrl + D to display the next page of the counters or Ctrl + U to display
the previous page.
4. Type C to reset the counters.
5. Type R to refresh the screen.

ETX-102
Monitoring>Physical Layers>Ethernet Statistics
Port Label (1)
|
v Counter --- RX --- --- TX ---
Total Frames (0) (0)
Total Octets (0) (0)
Correct Frames (0) (0)
FCS Errors (0)
Jabber Errors (0)
Fragments Errors (0)
Undersized Frames (0)
Oversizes Frames (0)
Discard Frames (0) (0)
Collisions (0)
Errors (0)
F Forward; C Clear Statistics; R Refresh Statistics

Figure 5-3. Ethernet Statistics (Page 1)
ETX-102
Monitoring>Physical Layers>Ethernet Statistics
^
| Port Label (1)
Counter --- RX --- --- TX ---

Unicast Frames (0) (0)
Multicast Frames (0) (0)
Broadcast Frames (0) (0)
In 64 Octets (0) (0)

In 65- 127 Octets (0) (0)
In 128- 255 Octets (0) (0)
In 256- 511 Octets (0) (0)
In 512-1023 Octets (0) (0)
In 1024-long Octets (0) (0)
F Forward; C Clear Statistics; R Refresh Statistics

Figure 5-4. Ethernet Statistics (Page 2)
5-4 Monitoring Performance ETX-102 Ver. 3.8

Table 5-3. Ethernet Statistics Parameters
RX
Total Frames The total number of correct frames received
Total Octets The total number of octets received, including framing characters
Correct Frames The number of frames successfully received
FCS Errors Total number of frames received on a particular interface that is an integral
number of octets in length, but do not pass the FCS check. This count does not
include frames received with Frame-Too-Long or Frame-Too-Short error.
Jabber Errors Total number of long frames received with invalid CRC
Fragments Errors Total number of frames, which are less than 64 octets in length (excluding framing
bits, but including FCS octets) and had either a bad Frame Check Sequence (FCS)
with an integral number of octets (FCS Error) or a bad FCS with a non-integral
number of octets (alignment error)
Undersized Frames Total number of received short frames with size under 64 bytes and with valid CRC
Oversized Frames Total number of received long frames with size over 1518 bytes and with valid CRC
Discard Frames Total number of frames that were discarded even though no errors had been
detected
Unicast Frames Total number of unicast received frames
Multicast Frames Total number of multicast received frames
Broadcast Frames Total number of broadcast received frames
In 64 Octets Total number of received 64-byte packets
In 65-127 Octets Total number of received 65127-byte packets
In 1024-long Octets Total number of received 1024-byte packets
TX
Total Frames Total number of correct frames transmitted
Total Octets Total number of octets transmitted, including framing characters
Correct Frames Total number of frames successfully transmitted
Collisions Total number of occurred collisions
Discards Total number of discarded frames
Errors Total number of transmission errors
Unicast Frames Total number of unicast transmitted frames
Multicast Frames Total number of multicast transmitted frames
Broadcast Frames Total number of broadcast transmitted frames
In 64 Octets Total number of transmitted 64-byte packets
In 65-127 Octets Total number of transmitted 65127-byte packets


In 1024-long Octets Total number of transmitted 1024-byte packets
5.2 Handling Events and Traps

ETX-102 maintains a log file that can hold up to 100 events (system messages).
All events are time-stamped.
Displaying Events
To access the event log:
1. From the Monitoring menu, select System.
The System menu is displayed.
2. From the System menu, select Event Log.
The Event Log menu appears.
3. From the Event Log menu, select Read Log File.
The Event Log is displayed (see Figure 5-5).
4. In the Event Log screen, use the Ctrl + U and Ctrl + D keys to scroll the alarm
list up and down.
ETX-102
Monitoring>System>Event Log>Read Log File
Log Entry
1 2005-03-16 19:50:08 LOGIN VIA TERMINAL
2 2005-03-16 19:22:32 LOGIN VIA TERMINAL
| 3 2005-03-16 19:22:13 LINK DOWN PORT 5
v 4 2005-03-16 19:22:12 LINK DOWN PORT 4
5 2005-03-16 19:22:12 LINK DOWN PORT 3
6 2005-03-16 19:22:12 LINK DOWN PORT 2
7 2005-03-16 19:22:12 LINK DOWN PORT 1
8 2005-03-16 19:22:11 COLD START
>
^D - Scroll Down , ^U - Scroll Up
ESC-prev.menu; !-main menu; &-exit; ?-help 1 Mngr/s
Figure 5-5. Event Log
5-6 Handling Events and Traps ETX-102 Ver. 3.8

Configuring Event Reporting (RMON Counters)

In addition to the regular statistics collection, ETX-102 allows you to receive
reports when one of the available counters (physical layer or OAM) rises above or
drops below the set thresholds within the specified sampling period of time.
These reports can be sent as SNMP traps to the defined network management
stations or written to the event log.
To configure event reporting (physical layer counters):

1. From the Alarm Threshold Configuration menu (Configuration > System >
Management > Alarm Threshold Configuration), type a to add a new RMON
instance.
2. For each RMON instance configure the following:
Alarm Description (Name of the counter to be monitored):
Dropped Frames
Undersize Frames
Oversize Frames
Fragmented Frames
Jabbers
Port Label (Switch port on which the current RMON instance is active):
None, Port 16
Rising Alarm Threshold (The report is sent if the selected counter has
been above the rising threshold for ten consecutive seconds): 160
Falling Alarm Threshold (The report is sent if the selected counter has
been below the falling threshold for ten consecutive seconds): 160
Sampling Interval (Period of time in seconds during which the data is
sampled and compared with the rising and falling thresholds):
160 seconds
Event Type (Method of event reporting):
None (Reports are not sent)
Log (Reports are recorded as events in the event log)
Trap (Reports are sent as SNMP traps)
Log and Trap (Reports are recorded as events in the event log and
sent as SNMP traps).
Refer to Table 5-4 for the description of the events recorded in the event
log when a counter exceeds or drops below the set threshold.
ETX-102 Ver. 3.8 Handling Events and Traps 5-7

ETX-102
Configuration>System>Management>Alarm Threshold Configuration
1. Alarm Description > (Dropped Frames)
2. Port Label > (None)
3. Rising Alarm Threshold ... (0)
4. Falling Alarm Threshold ... (0)
5. Sampling Interval[1 - 60] ... (0)
6. Event Type > (None)
>

A - Add New RMON ; S - Save
Figure 5-6. Alarm Threshold Configuration
To configure event reporting (OAM counters):

1. From the Event Reporting menu (Configuration > Connection > EVCs > Service
> Event Reporting), select an OAM counter to be monitored:
Frame Loss Ratio
Frames Above Delay
Frames Above Delay Variation
Unavailability Ratio
2. For each OAM counter define:
Rising Threshold (The report is sent if the selected counter has been
above the rising threshold for ten consecutive seconds)
14294967296 for Frames Above Delay and Frames Above Delay
Variation
1E-3, 1E-4, 1E-5, 1E-6, 1E-7, 1E-8, 1E-9, 1E-10 for Frame Loss Ratio
and Unavailability Ratio
Falling Threshold (The report is sent if the selected counter has been
below the falling threshold for ten consecutive seconds):
14294967296 for Frames Above Delay and Frames Above Delay
Variation
1E-3, 1E-4, 1E-5, 1E-6, 1E-7, 1E-8, 1E-9, 1E-10 for Frame Loss Ratio
and Unavailability Ratio
Sampling Interval (Period of time in seconds during which the data is
sampled and compared with the rising and falling thresholds):
160 seconds
Note
Sampling interval configuration is not available for the Frame Loss Ratio and
Unavailability Ratio counters.

Event Reporting Type (Method of event reporting):

None (Reports are not sent)
Log (Reports are recorded as events in the event log)
Trap (Reports are sent as SNMP traps)
Log and Trap (Reports are recorded as events in the event log and
sent as SNMP traps).
Refer to Table 5-4 for the description of the events recorded in the event
log when a counter exceeds or drops below the set threshold.
Clearing Events
To clear the event log:
From the Event Log menu, select Clear Log File.
All events are deleted from the log.
Table 5-4 presents the event types that appear in the event log.
Table 5-4. Event List
Event Description
COLD START The unit has been restarted
FATAL ERROR XX Hardware failure has been detected
FATAL ERROR AT XX LINE XX Hardware failure has been detected
SYSTEM USER RESET Overall reset was performed by the user
LINK DOWN (PORT 1 \ PORT 2 Network or user Ethernet port has been disconnected
\ PORT 3)
LINK UP PORT (PORT 1 \ Network or user Ethernet port has been connected
PORT 2 \ PORT 3)
LINK ADMIN DOWN PORT Network or user Ethernet port has been disabled by the user
(PORT 1 \ PORT 2 \ PORT 3)
LOGIN VIA (TELNET, WEB, ETX-102 has been accessed via Telnet, Web or terminal
TERMINAL)
INVALID LOGIN VIA (TELNET, Invalid user name or password was detected during initialization of Telnet, Web
WEB, TERMINAL) or terminal control session
IP X.X.X.X ASSIGNED BY IP address X.X.X.X has been assigned by DHCP server X.X.X.X
SERVER X.X.X.X
IP X.X.X.X IS RELEASED IP address X.X.X.X has been released by ETX-102
LOG FILE RECOVERED Log file corruption has been detected and fixed at startup.
CONNECTIVITY MISMATCH EVC No EVC ID or MEP ID mismatch has been detected on EVC X
X OFF
CONNECTIVITY MISMATCH EVC EVC ID or MEP ID mismatch has been detected on EVC X
X ON

Event Description
CC FAILURE EVC X OFF Continuity check on EVC X has failed
CC FAILURE EVC X OFF Continuity check on EVC X has been restored
DROPPED FRAMES EXCEEDED Number of dropped frames exceeded configured threshold on port X
PORT X
DROPPED FRAMES DROPPED Number of dropped frames dropped below configured threshold on port X
BELOW PORT X
UNDERSIZED FRAMES Number of undersized frames exceeded configured threshold on port X

EXCEEDED PORT X
UNDERSIZED FRAMES Number of undersized frames dropped below configured threshold on port X
DROPPED BELOW PORT X
OVERSIZED FRAMES Number of oversized frames exceeded configured threshold on port X

EXCEEDED PORT X
OVERSIZED FRAMES DROPPED Number of oversized frames dropped below configured threshold on port X
BELOW PORT X
FRAGMENTED FRAMES Number of fragmented frames exceeded configured threshold on port X

EXCEEDED PORT X
FRAGMENTED FRAMES Number of fragmented frames dropped below configured threshold over port X
DROPPED BELOW PORT X
JABBERS EXCEEDED PORT X Number of jabbers exceeded configured threshold on port X
JABBERS DROPPED BELOW Number of jabbers dropped below configured threshold on port X
PORT X
FRAMES LOSS RATIO Frames loss ratio exceeded configured threshold for service Y on EVC X
EXCEEDED EVC X SVC Y
FRAMES LOSS RATIO Frames loss ratio dropped below configured threshold for service Y on EVC X
DROPPED BELOW EVC X SVC Y
FRAMES ABOVE DELAY Number of frames above delay exceeded configured threshold for service Y on
EXCEEDED EVC X SVC Y EVC X
FRAMES ABOVE DELAY Number of frames above delay dropped below configured threshold for service Y
DROPPED BELOW EVC X SVC Y on EVC X
FRMS ABOVE DEL VAR Frames above delay variation exceeded configured threshold for service Y on EVC
EXCEEDED EVC X SVC Y X
FRMS ABOVE DEL VAR Frames above delay variation dropped below configured threshold for service Y
DROPPED BELOW EVC X SVC Y on EVC X
UNAVAIL RATIO EXCEEDED Unavailability ratio exceeded configured threshold for service Y on EVC X
EVC X SVC Y
UNAVAIL RATIO DROPPED Unavailability ratio dropped below configured threshold for service Y on EVC X
BELOW EVC X SVC Y
OAM (802.3ah) REMOTE Dying gasp indication has been received from the remote partner on OAM link on
DYING GASP PORT X port X

Event Description
OAM (802.3ah) OAM connectivity has been lost on port X

CONNECTIVITY FAIL PORT X
ON
OAM (802.3ah) OAM connectivity has been restored on port X

CONNECTIVITY FAIL PORT X
OFF
OAM (802.3ah) REMOTE LINK Indication of the OAM connectivity failure has been received from the remote
FAIL PORT X ON partner on OAM link on port X
OAM (802.3ah) REMOTE LINK Indication of the OAM connectivity recovery has been received from the remote
FAIL PORT X OFF partner on OAM link on port X
OAM (802.3ah) REMOTE Indication of the critical errors has been received from the remote partner on
CRITICAL ERRORS PORT X ON OAM link on port X
OAM (802.3ah) REMOTE Indication of the critical error termination has been received from the remote
CRITICAL ERRORS PORT X OFF partner on OAM link on port X
OAM (802.3ah) REMOTE Indication of the remote loopback activation has been received from the remote
LOOPBACK PORT X ON partner on OAM link on port X
OAM (802.3ah) REMOTE Indication of the remote loopback deactivation has been received from the
LOOPBACK PORT X OFF remote partner on OAM link on port X
Table 5-5. Trap List
Trap Description OID Maskable
coldStart The unit has been restarted 1.3.6.1.6.3.1.1.5.1 No
authenticationFailure User authentication has failed 1.3.6.1.6.3.1.1.5.5 No
linkDown Network or user Ethernet port has 1.3.6.1.6.3.1.1.5.3 Yes

been disconnected
linkUp Network or user Ethernet port has 1.3.6.1.6.3.1.1.5.4 Yes

been connected
tftpStatusChangeTrap TFTP session status has changed 1.3.6.1.4.1.164.6.1.0.1 No
agnStatusChangeTrap SNMP agent status has changed 1.3.6.1.4.1.164.6.1.0.2 No
agnPowerFailureTrap ETX-102 power supply is about to 1.3.6.1.4.1.164.6.1.0.13 No

fail
successfulLogin Successful login to ETX-102 has 1.3.6.1.4.1.164.6.1.0.24 Yes

been detected
failedLogin Failed login to ETX-102 has been 1.3.6.1.4.1.164.6.1.0.25 Yes

detected
prtStatusChangeTrap An SFP has been removed from one 1.3.6.1.4.1.164.6.1.0.3 No

of the ports

Masking Alarm Traps

You can mask some ETX-102 alarm traps to prevent them from being sent to the
management stations.
To mask alarm traps:

1. From the Management menu (Configuration > System > Management), select
Alarm trap mask.
The Alarm Trap Mask menu appears (see Figure 5-7).
2. From the Alarm Traps Mask menu, select Alarm ID to choose a maskable trap
that you intend to mask (see Table 5-5).
Note List of the alarm traps can be displayed by typing ? for Help.
3. Select Trap Status to enable or disable masking of the selected alarm trap.
ETX-102
Configuration>System>Management>Alarm trap mask
Active alarm traps: > (1, 2, 3)
1. Alarm ID <use 'help'> [1-3] ... (1)

2. Trap status (Active)
>
? - Help
Figure 5-7. Alarm Trap Mask Menu
Configuring the Trap Delay

You can define a delay between the unit power up and sending the first trap to
the NMS. This prevents the ETX-102 traps from being dropped by a peer device
that may not be ready to forward the traps to the NMS.
To configure the trap delay:

From the Management menu (Configuration > System > Management), select
Traps Delay and define a period of time between completing the power-up
procedure and sending the first trap to the NMS: 0100 seconds.

ETX-102
Configuration>System>Management
1. Device Info >

2. SNMPv3 > (Disable)
3. Host >
4. Manager List []>
5. Management Access >
6. Alarm Trap Mask >
7. Alarm Threshold Configuration >
8. Traps Delay[0 - 100] ... (0)
>
? - Help
Figure 5-8. Management Menu
5.3 Testing the Unit

ETX-102 checks network integrity by running ping or trace route tests. In
addition, the user can close loopbacks on the switch ports, run a cable integrity
and VLAN test.
Running a Ping Test

You can ping a remote host to check the ETX-102 IP connectivity.
To ping an IP host:
1. From the Main menu, select Diagnostics.
The Diagnostics menu appears.
2. From the Diagnostics menu, select Ping.
The Ping menu appears (see Figure 5-9).
3. From the Ping menu, configure the following:
Destination IP Address (IP address of the host that you intend to ping):
0.0.0.0 to 255.255.255.255.
Number of frames to send: 050. When set to 0, ETX-102 starts endless
pinging.
4. Select Send Ping to start sending pings.
5. Select Stop Ping to stop the ping test.
ETX-102 Ver. 3.8 Testing the Unit 5-13

ETX-102
Diagnostics>Ping
1. Destination IP Address ... (0.0.0.0)

2. Number of Frames to Send[0 - 50] ... (1)
3. Send Ping
4. Stop Ping
>
Figure 5-9. Ping Menu
Tracing the Route

This diagnostic utility traces the route through the network from ETX-102 to the
destination host. The trace route utility supports up to 30 hops.
To trace a route:
1. From the Diagnostics menu, select Trace Route.
The Trace Route menu is displayed (see Figure 5-10).
2. From the Trace Route menu, select Destination IP Address and enter an IP
address of the host to which you intend to trace route.
3. Select Display Trace Route to start tracing.
ETX-102 starts tracing the route, displaying the IP addresses of all hop
nodes.
4. Select Stop Trace Route to stop the tracing.
ETX-102
Diagnostics>Trace Route

2. Display Trace Route
3. Stop Trace Route
>
Figure 5-10. Trace Route Menu
Running Loopbacks
ETX-102 supports two loopback types:
Regular loopback run at the PHY of the bridge ports. When the loopback is
active the data forwarded to a bridge port is looped from the Tx path to the
Rx path.
5-14 Testing the Unit ETX-102 Ver. 3.8

MAC Swap loopback which supports exchanging source and destination MAC
addresses of the incoming packets. The user can define loopback direction
(ingress or egress) and type of data to be looped back (all data except for
packets with management VLAN tag or only packets with a specific VLAN tag).
To run a regular loopback:

1. From the Diagnostics menu, select Loopbacks.
The Loopbacks menu is displayed (Figure 5-13).
2. From the Loopbacks menu, type f to select the port that you intend to run
loopback on.
3. From the Loopbacks menu, configure the following:
Loopback Timeout (Specifies a period of time, after which the loopback is
automatically disabled. Setting timeout to 0 disables the timeout.):
03600 seconds.
Loopback State (Controls loopback activation)
Enable Loopback is activated
Disable Loopback is deactivated.
Note
Only one loopback can be run at a time.
To run a MAC Swap loopback:

1. From the Diagnostics menu, select Loopbacks.
The Loopbacks menu is displayed (Figure 5-13).
2. From the Loopbacks menu, type f to select the port that you intend to run
loopback on.
3. From the Loopbacks menu, configure the following:
MAC Swap (Enables or disables exchanging source and destination MAC
addresses:
Enable MAC address swap is enabled
Disable MAC address swap is disabled
Looped Data (Defines which data will be looped back):
All Except MNG All packets, excluding the ones with management
VLAN tag, are looped back. The management traffic remains intact.
Specific VLAN Only packets with specific VLAN tag are looped back.
Notes
MAC Swap loopback cannot be run on network port 2.
Specific VLAN mode is not available for a bridge port with tag handling set to
Stack.
All Except MNG mode is not available for the user ports.
VLAN ID (Specifies VLAN value for the Specific VLAN mode): 14094
Note
Specific VLAN ID must be different from the host VLAN ID.

Direction (Defines direction in which the loopback is to be closed):

Local The loopback is closed towards the user interface
(see Figure 5-11)
Remote The loopback is closed towards the network interface
(see Figure 5-12).
Network User
Interface Interface
ETX-102
Figure 5-11. Local Loopback
Network User
Interface Interface
ETX-102
Figure 5-12. Remote Loopback
The following MAC Swap loopbacks cannot be activated:
When the Tag Handling is set to Stack: Specific VLAN local and
specific VLAN remote loopbacks on user ports, specific VLAN local
loopback on network port
When the VLAN mode is set to VLAN-aware: Specific VLAN remote
loopback on network port, specific VLAN local loopback on user ports
When the VLAN mode is set to VLAN-unaware and Host Tagging to
Untagged: specific VLAN local loopback on user ports
Forced Source MAC (A MAC address to be used instead of the original
source MAC address)
Forced Destination MAC (A MAC address to be used instead of the original
destination MAC address)
Loopback Timeout (Specifies a period of time, after which the loopback is
automatically disabled. Setting timeout to 0 disables the timeout.):
03600 seconds.
State (Controls loopback activation)
Enable Loopback is activated
Disable Loopback is deactivated.
Note
Only one loopback can be run at a time.

ETX-102
Diagnostics>Loopbacks
Port Label (1)
Port (Network)
1. MAC Swap (Enable)
2. Looped Data (Specific VLAN)
3. VLAN ID [1 - 4095] (1)
4. Direction (Remote)
5. Forced Source Mac ... (00-00-00-00-00-00)
6. Forced Destination Mac ... (00-00-00-00-00-00)
7. Loopback Timeout (sec) [0-3600] ... (0)
8. State (Disable)
>
F - Forward S - Save
Figure 5-13. Loopbacks Menu (MAC Swap is Enabled)
Testing the Cables

The user can check the quality of the copper cables, connectors and terminations
by running a Virtual Cable Test (VCT). During the test ETX-102 transmits a signal
of known amplitude (+1V) down each of the two pairs of an attached cable,
testing the Rx and Tx pairs sequentially. The signal travels down the cable until it
reflects off of a cable imperfection. By measuring magnitude of the reflection and
the time it takes for the reflection to come back, ETX-102 estimates an
approximate distance to the location of a cable break or short.
To run the VCT:

1. From the Diagnostics menu, select VCT Test.
The VCT Test menu is displayed (see Figure 5-14).
2. From the VCT Test menu, type f to select an ETX-102 user port, which cable
you intend to test.
3. From the VCT Test menu, select Start Test to initiate the VCT on the selected
port.
The VCT results are displayed for the receive and transmit wires:
Tx/Rx test results:
Fail The CAT5 cable pair has a non-compliant termination i.e. less
than 85 or greater than 115.
Normal The CAT5 cable pair is normal and has a termination between
the IEEE specified limits of 85 to 115
Open The CAT5 cable pair is not terminated.
Short The CAT5 cable pair is shorted
Short to Pair A/B/C/D The CAT5 cable pair is shorted to pair A/B/C/D

Coupled with Pair A/B/C/D The CAT5 cable pair has abnormal
coupling with pair A/B/C/D i.e. the impedance between the pairs is
between 40 and 200.
Rx/Tx distance of reflection: Approximate distance to the location of a
cable break or short in meters.
ETX-102
Diagnostics>VCT Test
Port Label > (3)
Port > (User 2)
Pair A Test Result > (Normal)

Pair A Distance of Reflection ... (0 m)
Pair B Test Result > (Normal)
Pair B Distance of Reflection ... (0 m)
Pair C Test Result > (Normal)
Pair C Distance of Reflection ... (0 m)
Pair D Test Result > (Normal)
Pair D Distance of Reflection ... (0 m)
1. Start Test (No Op)
>
F - Forward
Figure 5-14. VCT Test Menu
Running the VLAN Test

ETX-102 can be configured to collect and display transmitted and received packet
and octets count per specified port and VLAN.
To run the VLAN test:

1. From the Diagnostics menu, select VLAN Test.
The VLAN Test menu is displayed (see Figure 5-15).
2. From the VLAN Test menu, select the following:
VLAN ID (ID of the VLAN to be tested)
Ethernet Port (ETX-102 network or user port)
State (Enables or disables or VLAN testing)
VLAN test results:
Rx Octets (Number of bytes received on the selected VLAN and port)
Tx Octets (Number of bytes transmitted on the selected VLAN and port)
Rx Frames (Number of frames received on the selected VLAN and port)
Tx Frames (Number of frames transmitted on the selected VLAN and port)

Note VLAN test cannot be run on network port 2 or management VLAN (ID of the
VLAN to be tested must be different from the host VLAN ID.
Only one VLAN test can be run at a time.
To clear the VLAN test results:

From the VLAN Test menu, type C.
The VLAN test counters are cleared.
ETX-102
Diagnostics>VLAN Test
Rx Octets (0)
Tx Octets (0)
Rx Frames (0)
Tx Frames (0)
1. VLAN ID[1 4094] (1)

2. Ethernet Port (Network 1)
3. State (Enable)
>
F - Forward C - Clear counters
Figure 5-15. VLAN Test Menu
5.4 Frequently Asked Questions

Q: What is the flip time from the main link to the backup link when link
redundancy is enabled?
A: For ETX-102 with two fiber uplinks the flip time is below 50 ms. For ETX-102
with two copper network links, the flip time is 400700 ms.
ETX-102 Ver. 3.8 Technical Support 5-19

5.5 Technical Support

Technical support for this product can be obtained from the local partner from
whom it was purchased.
RADcare Global Professional Services offers a wide variety of service, support and
training options, including expert consulting and troubleshooting assistance,
online tools, regular training programs, and various equipment coverage options.
For further information, please contact the RAD partner nearest you or one of
RAD's offices worldwide.
RAD Data Communications would like your help in improving its product
documentation. Please send us an e-mail with your comments.
Thank you for your assistance!
5-20 Technical Support ETX-102 Ver. 3.8

Chapter 6
Software Upgrade
This chapter explains how to upgrade ETX-102 to version 3.8.
Software upgrade is required to fix product limitations, enable new features, or
to make the unit compatible with other devices that are already running the new
software version.
The information in this chapter includes the following:
Detailed conditions required for the upgrade
Any impact the upgrade may have on the system
Overview of downloading options
Upgrade via the File Utilities menu
Upgrade via the Boot menu.
6.1 Compatibility Requirements

Following are the software releases that can be upgraded to version 3.8 or
higher, as well as the hardware revisions that can accept the software version
3.8.
Software 3.5 and above
Hardware 2.0 and above.
6.2 Impact
ETX-102 resets automatically after the software upgrade, resulting in up to
two minutes of downtime.
Upgrade to version 3.8 does not affect any user settings.
6.3 Software Upgrade Options

Application software can be downloaded to ETX-102 the File Utilities menu using
TFTP, or via the Boot menu, using XMODEM or TFTP.
ETX-102 Ver. 3.8 Software Upgrade Options 6-1

Chapter 6 Software Upgrade Installation and Operation Manual
6.4 Prerequisites
This section lists the software file names and outlines system requirements
needed for the upgrade procedure.
Software Files
The version 3.8 release is distributed as a software file named ETX-102 3.8.img.
The file can be obtained from the local RAD business partner from whom the
device was purchased.
System Requirements
Before starting the upgrade, verify that you have the following:
For upgrade via TFTP:
Operational ETX-102 unit with valid IP parameters configured for the host
Connection to a PC with a TFTP server application (such as 3Cdaemon or
PumpKIN) and a valid IP address
Software file (ETX-102 3.8.img) stored on the PC
For upgrade via XMODEM:
Operational ETX-102 unit
Connection to a PC with a terminal emulation application (such as
HyperTerminal)
Software file (ETX-102 3.8.img) stored on the PC.
6.5 Upgrading ETX-102 Software via the File

Utilities Menu
The recommended software downloading method is to use the S/W & File
Transfer using TFTP option in the File Utilities menu.
Network administrators can use this procedure to distribute new software
releases to all the managed ETX-102 units in the network from a central location.
Figure 6-1. Downloading a Software Application File to ETX-102 via TFTP
6-2 Upgrading ETX-102 Software via the File Utilities Menu ETX-102 Ver. 3.8
Installation and Operation Manual Chapter 6 Software Upgrade
Use the following procedure to download software release 3.8 to ETX-102 via the
File Utilities menu.
1. Verify that ETX-102 3.8.img is stored on the PC with the TFTP server
application.
2. Verify that the ETX-102 host has valid IP parameters.
3. Ping the PC to verify the connection.
4. Activate the TFTP server application.
5. Download ETX-102 3.8.img from the PC to ETX-102.
Note Configuration values shown in this chapter are examples only.
Verifying the Host Parameters

The ETX-102 host must have host IP parameters configured according to your
network requirements. Otherwise you will not be able to establish a proper
communication session with the TFTP server. Refer to the following manual
sections for additional information:
Connecting to the ASCII Terminal in Chapter 2
Working with Terminal in Chapter 3
Configuring IP Host Parameters and Configuring the Host Encapsulation in
Chapter 4.
To verify the ETX-102 host parameters:

1. Display the Host IP menu (Configuration > System > Host IP), and verify that
the host IP address, IP mask, and default gateway are configured according to
your network requirements.
ETX-102
Configuration>System>Host IP
1. IP address ... (192.168.10.2)

2. IP mask ... (255.255.255.0)
3. Default gateway ... (192.168.10.3)
4. DHCP (Disable)
5. Default IP ... (0.0.0.0
>

Figure 6-2. Host IP Menu
2. Display the Encapsulation menu (Configuration > System > Management >
Host > Encapsulation), and verify that the host encapsulation parameters
(host VLAN, security definition) are configured according to your network
requirements.
ETX-102 Ver. 3.8 Upgrading ETX-102 Software via the File Utilities Menu 6-3
ETX-102

2. Host VLAN ID [1 - 4094] ... (300)
>
Figure 6-3. Host Encapsulation Menu
Pinging the PC
Check the integrity of the communication link between ETX-102 and the PC by
sending a ping from the unit to the PC.
To ping the PC:

1. From the Ping menu (Diagnostics > Ping), enter the IP address of the PC as
the destination IP address of the ping.
2. Select Send Ping to start sending pings.
A reply from the PC indicates a proper communication link
3. If the ping request times out, check the link between ETX-102 and the PC
(physical path, configuration parameters, etc.)
ETX-102
Diagnostics>Ping

2. Number of Frames to Send[0 - 50] ... (1)
3. Send Ping
4. Stop Ping
>
Figure 6-4. Pinging the PC
Activating the TFTP Server

Once the TFTP server is activated on the PC, it waits for any TFTP file transfer
request originating from the product, and carries out the received request
automatically. The Transferring Software and Configuration Files section in
Chapter 4 explains how to prepare your PC for the TFTP file transfer.
TFTP file transfers are carried out through Port 69. Make sure that the firewall
you are using on the server allows communication through this port
To run the TFTP server:

Activate a TFTP server application, such as 3Cdaemon (available from
www.3com.com) or PumpKIN (available from http://kin.klever.net/pumpkin/).
To allow communication through Port 69 in Windows XP:

1. Double-click the My Network Places icon, located on the desktop.
The My Network Place window appears.
2. On the Network Tasks sidebar, click View network connections.
The available network connections are displayed.
Figure 6-5. View Network Connections
3. On the Network Tasks sidebar, click Change Windows Firewall settings.

The Windows Firewall dialog box appears.
Figure 6-6. Change Firewall Settings
4. Click the Exceptions tab.
ETX-102 Ver. 3.8 Upgrading ETX-102 Software via the File Utilities Menu 6-5
Figure 6-7. Windows Firewall Dialog Box Exceptions Tab
5. Check whether Port 69 appears on the exceptions list. If it does not, click
Add Port and add it to the list of exceptions.
Note Different firewall types require different configuration. Refer to your firewall's
documentation to check how TFTP file transfers can be allowed to pass through it
using a UDP-type port.
Downloading the New Software Release File to ETX-102

This procedure is used to replace the current software version with the new
software release (ETX-102 3.8.img).
To download the new software release file:

1. From the S/W & File Transfer using TFTP menu (Utilities > File Utilities > S/W
& File Transfer using TFTP), enter the following:
File name ETX-102 3.8.img
Command Software Download
Server IP IP address of the PC.
2. Save your changes to initiate the download.
The software download begins. When the process is completed, ETX-102

resets automatically. After the reset, the new software release
(ETX-102 3.8.img) replaces the current software version and becomes
active.
ETX-102
Utilities>File Utilities>S/W & File Transfer using TFTP
1. File name ... (ETX-102 3.8.img)

2. Command > (Software Download)
3. Server IP ... (192.168.10.20)
4. Retry timeout(sec)[0 - 1000] ... (1)
5. Total timeout(sec)[0 - 1000] ... (5)
6. View transfer status >
>
Figure 6-8. Transferring New Software Release Using TFTP
6.6 Upgrading ETX-102 Software via the Boot Menu

Software downloading can also be performed using the Boot menu. The Boot
menu can be reached while ETX-102 performs initialization, for example, after
power-up.
You may need to start the loading from the Boot menu when it is not possible to
activate TFTP from the S/W & File Transfer using TFTP menu (for example,
because the ETX-102 software has not yet been downloaded or is corrupted).
Caution The Boot menu procedures are recommended only for use by authorized
personnel, because this menu provides many additional options that are intended
for use only by technical support personnel.
Two software downloading options are available from the Boot menu:
Downloading using the XMODEM protocol. This is usually performed by
downloading from a PC directly connected to the CONTROL DCE port of the
unit.
Figure 6-9. Downloading a Software Application File to ETX-102 via XMODEM
ETX-102 Ver. 3.8 Upgrading ETX-102 Software via the Boot Menu 6-7
Downloading using TFTP. This is usually performed by downloading from a

remote location that provides an IP communication path to an Ethernet port
of ETX-102.
To access the Boot menu:

1. Configure the communication parameters of the selected PC serial port for
asynchronous communication to the data rate configured in ETX-102 for the
control port (see Configuring Control Port Parameters in Chapter 4), no parity,
one start bit, eight data bits, and one stop bit. Turn all types of flow control
off.
2. Turn off ETX-102.
3. Activate the terminal application.
4. Turn on ETX-102 and immediately start pressing the <Enter> key several
times in sequence until you see the Boot screen. A typical screen is shown
below (the exact version and date displayed by your ETX-102 may be
different).
Note If you miss the timing, ETX-102 performs a regular reboot process (this process
starts with Loading and ends with a message to press <Enter> a few times to
display the log in screen).
RAD ETX_102 Boot Version 1.00 (Nov 9 2004)

RAD Boot Manager Version 7.01 (Nov 9 2004)
0 - Exit Boot-Manager
1 - Dir
2 - Set Active Software Copy
3 - Delete Software Copy
4 - Download Files or an Application by XMODEM
5 - Format flash
6 - Show basic hardware information
7 - Reset board
8 - System Configuration.
9 - Download an Application by TFTP
Press the ESC key to go back to the Main Menu.
Select:
Figure 6-10. Boot Menu
Using the XMODEM Protocol

Use the following procedure to download software release 3.8 to ETX-102 via
XMODEM.
To download software release via XMODEM:

1. Verify that ETX-102 3.8.img is stored on the PC with the terminal application.
2. From the Boot menu, select Download Files or an Application by XMODEM.
6-8 Upgrading ETX-102 Software via the Boot Menu ETX-102 Ver. 3.8
A message is displayed that requests the partition number to which the

new software is to be downloaded, and offers a recommended value.
Select Copy number for download ( 1 )
3. If there is no special reason to select a different value, type the

recommended number and then press <Enter>.
Select: 1
4. The process starts, and the following is displayed:

Erasing Partition please wait ....
Please start the XMODEM download.
5. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
The Send File window is displayed:
Select the prescribed ETX-102 software file name (you can use the
Browse function to find it).
In the Protocol field, select Xmodem.
When ready, press Send in the Send File window.
You can now monitor the progress of the downloading in the Send File
window.
Note If downloading fails, the partially downloaded software is erased. In this case,
only active software is left in the flash memory. To download the new software,
you must repeat the whole procedure.
Once the downloading is completed, ETX-102 saves the new release as

the active image, the former active image becomes the backup, and the
boot sequence continues normally. A sequence of messages similar to
the following is displayed:
Loading ...
Decompressing to RAM.
Processing archive: FLASH

Extracting ETX-102.BIN
..........................................................
.................................................................... CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
6. At this stage, press the <Enter> key several times to go to the login screen.
ETX-102 Ver. 3.8 Upgrading ETX-102 Software via the Boot Menu 6-9
Using TFTP
Use the following procedure to download software release 3.8 to ETX-102 via
TFTP.
1. Verify that ETX-102 3.8.img is stored on the PC with the TFTP server
application.
2. Define IP parameters via the Boot Manager menu.
3. Activate the TFTP server application.
Note Configure the connection timeout of the TFTP server to be more than 30 seconds
to prevent an automatic disconnection during the backup partition deletion
(about 25 seconds).
4. Download ETX-102 3.8.img from the PC to ETX-102.
To define IP parameters via the Boot Manager menu:

1. From the Boot menu (Figure 6-10), select System Configuration to start the
configuration of the ETX-102 IP communication parameters, as needed for
TFTP transfer.
The parameters are displayed in consecutive lines. For each parameter,
you can accept the current values by simply pressing <Enter> to continue,
or type a new value:
IP Address: Used to select the IP address of ETX-102. To change the
current value, type the desired IP address in the dotted quad format,
and then <Enter> to continue.
IP Mask: Used to select the IP subnet mask of ETX-102. To change the
current value, type the IP subnet mask address in the dotted quad
format, and then <Enter> to continue.
Default Gateway Address: When the TFTP server is located on a
different LAN, you must define the IP address of the default gateway
to be used by ETX-102. Make sure to select an IP address within the
subnet of the assigned ETX-102 IP address. To change the current
value, type the desired IP address in the dotted quad format, and
then <Enter> to end the configuration.
If no default gateway is needed, for example, because the TFTP
server is attached to the same LAN as the ETX-102 device being
upgraded, enter 0.0.0.0.
2. Press <Enter> to display the Boot menu.
3. Select Reset board to reset ETX-102.
The new parameters take effect after the reset is completed.
To download software from the Boot menu using TFTP:

1. From the Boot menu, select Download an Application by TFTP and then press
<Enter> to start the TFTP transfer.
Please Enter the Target File Name message is displayed.
6-10 Upgrading ETX-102 Software via the Boot Menu ETX-102 Ver. 3.8
2. Enter the name of the desired software distribution file (make sure to include
the path, when necessary). When done, press <Enter> to continue.
Please Enter the Server IP address message is displayed.
3. Enter the IP address of the server on which the software distribution file
resides and then <Enter> to continue.
If no errors are detected, ETX-102 automatically erases the backup
partition (it takes about 25 seconds), and the downloading process
starts. Once the downloading is completed, ETX-102 saves the new
release as the active image, and the former active image becomes the
backup.
4. After the transfer is successfully completed, return to the Boot menu and
select Exit Boot-Manager.
When the ETX-102 initialization is ended, the unit loads the new
software.
Note If downloading fails, repeat the whole procedure.
6.7 Verifying Upgrade Results

To verify that the upgrade was successful, use the Terminal application and log
on to ETX-102 via HyperTerminal to view the Inventory screen (Main Menu >
Inventory), indicating the active software version in the SW Rev column.
ETX-102 Ver. 3.8 Verifying Upgrade Results 6-11

6-12 Verifying Upgrade Results ETX-102 Ver. 3.8

Chapter 7
Application Tutorial
This chapter provides detailed instructions for setting up a typical application
using two ETX-102 units.
7.1 Configuring the VLAN Stacking Application

This section provides an overview of an Ethernet access application, with two
ETX-102 units operating opposite each other (see Figure 7-1).
Figure 7-1. VLAN Stacking Application

VLAN stacking application requirements:
Receiving three user traffic feeds via separate user ports:
Port 1 real time traffic
Port 2 priority data
Port 3 best effort data
Service level definition (SLD):
Assigning rate limit to each data stream
Configuring per port ingress priority.
Assigning different port VID to each data stream.
ETX-102 Ver. 3.8 Configuring the VLAN Stacking Application 7-1

Chapter 7 Application Tutorial Installation and Operation Manual
Configuration Sequence
There are four basic configuration steps that need to be followed when deploying
ETX-102 units. Configure:
1. System parameters (setting host IP, defining network managers, configuring
management VLAN)
2. Network and user interfaces at the physical layer (if necessary)
3. The internal bridge (bridge mode, port VIDs)
4. QoS (priority and rate limitation).
Table 7-1. Configuration Summary (System)
Device Host IP Manager IP Manager VLAN, Priority
ETX-102 (A) 192.168.10.2 192.168.10.100 7, 7
ETX-102 (B) 192.168.10.1 192.168.10.100 7, 7
Table 7-2. Configuration Summary (Bridge and QoS)
Traffic Type Allocated Rate SPVLAN Default Priority Tag Priority Queue
Real time traffic 5 Mbps 4 2 Priority 2
Priority data 10 Mbps 5 1 Priority 1
Best effort data 40 Mbps 6 0 Priority 0
Configuring System Parameters

This section explains how to configure ETX-102 units. The configuration
procedure is similar for both units, except for defining different host IP
addresses. Refer to Chapter 3 for explanation of how to select management
options and save the changes.
Configuring Host IP Parameters

To configure the host IP parameters:
1. Display the Host IP menu (Configuration > System > Host IP), and configure
the IP address and mask of the host:
ETX-102 (A) host IP address 192.168.10.2
ETX-102 (B) host IP address 192.168.10.1
7-2 Configuring the VLAN Stacking Application ETX-102 Ver. 3.8

Installation and Operation Manual Chapter 7 Application Tutorial
ETX-102
Configuration>System>Host
1. IP address ... (192.168.10.2)
2. IP mask ... (255.255.255.0)
3. Default gateway ... (0.0.0.0)
4. DHCP (Disable)
5. Default IP ... (0.0.0.0)
>

Figure 7-2. Configuring Host IP Parameters for ETX-102 (A)
Defining Management VLAN

To define management VLAN:
1. Display the Encapsulation menu (Configuration > System > Management >
Host > Encapsulation), and configure the following:
Host Tagging Tagged
Host VLAN ID 7
Host VLAN Priority 7
ETX-102
2. Host VLAN ID [1 - 4094] ... (7)
>
Figure 7-3. Defining Management VLAN
Adding a Network Manager

To add a network manager:
1. Display the Manager List menu (Configuration > System > Management >
Manager List), and add a new network manager as follows:
2. Type a to enter the Add mode.
3. When in Add mode, select Manager IP, and enter the IP address of the
management station 192.168.10.100.

ETX-102
Configuration>System> Management > Manager List
Manager ID (1)
1. IP Address ... (192.168.10.100)
2. Trap Mask ... (Disable)
3. SNMP Traps UDP Port ... (162)
4. Save All
>
Figure 7-4. Manager List Menu, Add Mode
Configuring Ethernet Interfaces at the Physical Layer

To configure the Ethernet interfaces at the physical layer:
Display the Ethernet menu (Configuration > Physical Ports > Ethernet), and
configure the following parameters according to your application
requirements:
Autonegotiation
Maximum advertised capability
Speed and duplex mode
Flow control
Fault propagation.
Configuring the Bridge Mode

In the VLAN stacking application, it is necessary to configure the ETX-102 internal
bridge to the VLAN-unaware mode.
To configure the bridge mode:
Display the Bridge menu (Configuration > Bridge), and set the VLAN mode to
Unaware.

ETX-102
1. VLAN Mode (Unaware)

2. Forwarding Mode (Transparent)
3. Aging Time[300 - 4080] ...(300)
5. Erase MAC Table
6. Bridge Port >
7. VLAN Membership >
Figure 7-5. Configuring Bridge Mode
Configuring the Bridge User Ports

To configure the bridge ports:
Display the Bridge Port menu (Configuration > Bridge > Bridge Port), and
perform the following:
1. Type f to select User1 (user port 1).
2. Set Port VID\Stacking VID to 4
3. Set Default Priority Tag to 2
4. Set Tag Handling to Stack.
5. Repeat steps 14 for user ports 2 and 3, selecting the following values:
User 2 Port VID\Stacking VID 5, User 2 Default Priority Tag 1
User 3 Port VID\Stacking VID 6, User 3 Default Priority Tag 0
ETX-102
Bridge Port (User1)

5. Tag Handling (Stack)
>
f - forward
Figure 7-6. Configuring User Bridge Ports

Configuring QoS
It is necessary to select priority type and ingress rate limit for all user ports.
Selecting the Priority Type

To select the priority type:
Display the Priority menu (Configuration > QoS > Priority), and set the
Classification to Port Default Priority. In this case the use traffic coming from
the different port is to prioritized according to the default priority tag setting
(see Configuring the Bridge User Ports above).
ETX-102
Configuration>QoS>Priority
1. Classification >(Port Default Priority)
2. Mapping >
S - save
>
Figure 7-7. Configuring Priority

ETX-102
Configuration>QoS>Priority>Mapping>Port Default Priority

>
S - Save
Figure 7-8. Mapping Priorities to Traffic Classes
Selecting the Rate Limit

To select the rate limit:
Display the Port Rate Limitation menu (Configuration > QoS > Rate Limitation
> Ingress), and perform the following:

Type f to select User1 (user port 1).

Set Priority 0 to 5 Mbps.
Repeat steps 12 for user ports 2 and 3, selecting the following values:
User 2 Priority 10 Mbps
User 3 Priority 40 Mbps.
ETX-102
Configuration>QoS>Rate Limitation>Ingress
Port Label > (1)
Port > (User1)
1. Rate Limitation > (5 Mbps)
2. Burst Size (in kB) > (96)
3. Limit Packet Type > (All)
>
F - Forward S Save
Figure 7-9. Defining Port Rate Limits
7.2 Configuring a VLAN-Aware Application

Figure 7-10 illustrates a typical Ethernet switching application. The application is
as follows:
ETX-102 (A):
When receiving untagged user data from its user ports 1 and 2, it adds
two different VIDs to the data streams
Sends the user data to the remote ETX-102 (B) and ETX-102 (C) via its
network interface
When receiving tagged data from the remote ETX-102 (B) and ETX-102
(C), it strips the VID tags and forwards the untagged data to the user
equipment via its user ports 1 and 2.
Remote ETX-102 (B) and ETX-102 (C):
Receive tagged data from the local ETX-102 (A)
Strip the VID tags and forward the untagged data to the user equipment via
their user ports: user port 1 for ETX-102 (B) and user port 2 for ETX-102
(C).
When receiving untagged data from the user equipment, they add VID tags
to it and forward the data to the local ETX-102 (A) via their network
interfaces.
ETX-102 Ver. 3.8 Configuring a VLAN-Aware Application 7-7

Figure 7-10. VLAN-Aware Application
Configuration Sequence
There are four basic configuration steps that need to be followed when deploying
ETX-102 units. Configure:
1. System parameters (setting host IP, defining network managers, configuring
management VLAN)
2. Network and user interfaces at the physical layer (if necessary)
3. The internal bridge (bridge mode, port VID)
4. VLAN membership.
Table 7-3. Configuration Summary (System)
Device Host IP Manager IP Manager VLAN, Priority
ETX-102 (A) 192.168.10.2 192.168.10.100 7, 7
ETX-102 (B) 192.168.10.1 192.168.10.100 7, 7
ETX-102 (C) 192.168.10.3 192.168.10.100 7, 7
Table 7-4. Configuration Summary (Bridge Ports)
Device Port Port VID
ETX-102 (A) User 1 10
ETX-102 (A) User 2 20
ETX-102 (B) User 1 10
ETX-102 (C) User 2 20
7-8 Configuring a VLAN-Aware Application ETX-102 Ver. 3.8

Table 7-5. Configuration Summary (VLAN Membership)
Device VLAN Egress Tagged Port Egress Untagged Port
ETX-102 (A) 10 1 (network) 2 (user 1)
ETX-102 (A) 20 1 (network) 3 (user 2)
ETX-102 (B) 10 1 (network) 2 (user 1)
ETX-102 (C) 20 1 (network) 3 (user 2)
Configuring System Parameters

Refer to the Configuring System Parameters section above for instruction on how
to configure the system parameters of the ETX-102 units.
Configuring Ethernet Interfaces at the Physical Layer

Refer to the Configuring Ethernet Interfaces at the Physical Layer section above
for instruction on how to configure physical layer of the Ethernet parameters.
Configuring the Bridge Mode

In the VLAN-aware application, it is necessary to configure the ETX-102 internal
bridge to the VLAN-aware mode.
To configure the bridge mode:
Display the Bridge menu (Configuration > Bridge), and set the following:
VLAN Mode Aware
Forwarding Mode Filter.
ETX-102
1. VLAN Mode (Aware)

2. Forwarding Mode (Filter)
3. Aging Time[300 - 4080] ...(300)
5. Erase MAC Table
6. Bridge Port >
7. VLAN Membership >
Figure 7-11. Configuring Bridge Mode

Configuring the User Bridge Ports

To configure the user bridge ports:
Display the Bridge Port menu (Configuration > Bridge > Bridge Port), and
perform the following:
Type f to select the ETX-102 (A) user port 1 (User1).
Set Port VID\Stacking VID to 10.
Repeat steps 12 for ETX-102 (A) user port 2, setting its VID to 10.
Repeat steps 12 for ETX-102 (B) user port 1, setting its VID to 10.
Repeat steps 12 for ETX-102 (C) user port 2, setting its VID to 20.
ETX-102
Port Label (2)
Bridge Port (User1)

5. Tag Handling (None)
>
f - forward
Figure 7-12. Configuring User Bridge Ports (ETX-102 (A))
Configuring VLAN Membership.

To configure VLAN membership:
1. From the VLAN Membership menu (Configuration > Applications > Bridge >
VLAN Membership), type a to invoke the Add mode.
2. In the Add mode, set VLAN ID to 10 (see Figure 7-13).

ETX-102
Configuration>Bridge>Vlan Membership
Vlan Id[1 - 4094] ... (10)

1. Egress Tagged Ports > (-)
2. Egress Untagged Ports > (-)
>
a add new VLAN; f - forward; b - backward
Figure 7-13. Defining VLAN ID 10 for ETX-102 (A)

4. Select Egress Tagged Ports and type a to invoke the Add mode.
5. In the Add mode, set Egress Tagged Port to 1 and Egress Untagged Port to 2.
6. Repeat steps 15 to add VLAN 20 and configure Egress Tagged Port to 1 and
Egress Untagged Port to 3.
7. Repeat steps 15 for ETX-102 (B) to add VLAN 10 and configure Egress
Tagged Port to 1 and Egress Untagged Port to 2.
8. Repeat steps 15 for ETX-102 (C) to add VLAN 20 and configure Egress
Tagged Port to 1 and Egress Untagged Port to 3.
ETX-102
Configuration>Bridge>Vlan Membership
Vlan Id[1 - 4094] ... (10)

1. Egress Tagged Ports > (1)
2. Egress Untagged Ports > (2)
>
a add new VLAN; f - forward; b - backward
Figure 7-14. Configuring User 1 and Network Port as VLAN 10 Members


Appendix A
Connector Wiring
A.1 Ethernet Connectors

The Ethernet electrical interface terminates in 8-pin RJ-45 connectors, wired in
accordance with Table A-1.
Table A-1. Ethernet Connector Pinout
Pin Function
1 Rx+
2 Rx
3 Tx+
4, 5
6 Tx
7, 8
A.2 CONTROL Connector

The control terminal interface terminates in a V.24/RS-232 9-pin D-type female
DCE connector. Table A-2 lists the CONTROL connector pin assignments.
Table A-2. CONTROL Connector Pinout
Pin Function
1
2 Transmit Data (output)
3 Receive Data (input)
4
5
6
7
8
9
ETX-102 Ver. 3.8 CONTROL Connector A-1

Appendix A Connector Wiring Installation and Operation Manual
A-2 CONTROL Connector ETX-102 Ver. 3.8

Appendix B
Operation,
Administration, and
Maintenance (OAM)
B.1 Introduction
ETX-102 supports standard implementation of Ethernet OAM based on Y.1731
and IEEE P802.1ag, and pre-standard implementation based on Y.1731. The
pre-standard implementation is only used for performance measurements when
using two RAD units working opposite each other or when working opposite a
RAD device with an older version of RAD Ethernet OAM software. This appendix
describes the pre-standard implementation. The standard implementation can be
found in the documentation of standards Y.1731 and IEEE P802.1ag.
ETX-102 has the following capabilities for providing operation, administration,
and maintenance (OAM) in packet-switched networks:
Continuity check
Non-intrusive loopback which is used to detect loss of bidirectional continuity
Performance measurements (per service).
Table B-1 lists the Ethernet OAM-related terms used in the appendix.
Table B-1. Ethernet OAM Terminology
Term Description
UNI User Network Interface. The physical demarcation point

between the responsibility of the Service Provider and the
responsibility of the Subscriber
UNI_C Customer side of a UNI link
UNI_N Network side of a UNI link
Service frame An Ethernet frame transmitted across the UNI toward the
Service Provider or an Ethernet frame transmitted across the
UNI toward the Subscriber.
Flow Ethernet Virtual Connection : An association of two or more

UNIs that limits the exchange of Service Frames to UNIs in the
Ethernet Virtual Connection
Point-to-point Flow Flow connecting exactly two UNIs
ETX-102 Ver. 3.8 Introduction B-1

Appendix B Operation, Administration, and Maintenance (OAM) Installation and Operation Manual
Term Description
Multipoint-to-Multipoint Flow connecting two or more UNIs

Flow
Service Instance / Class A set of Service Frames that have a commitment from the
of service (CoS) Service Provider to receive a particular level of performance
Service Instance Service Frame delivery performance is specified for all Service
Identifier (CoS ID) Frames transported within a flow with a particular Class of
Service instance. The Class of Service instance is identified by a
Class of Service Identifier associated with each Service Frame
(Class of service can be identified by more than one
parameter/frame attribute)
MEP Proactive OAM reference point which is capable to initiate and

terminate proactive OAM frames. MEP is also capable to initiate
and react to diagnostics OAM frames.
MIP A provisioned OAM reference point which is capable to respond

to diagnostics OAM frames initiated by the MEP.
MEP Service Instance The receiver of OAM frames in each Service Instance
Source
MEP Service Instance The transmitter of OAM frames in each Service Instance
Destination
B.2 Reference Architecture

Figure B-1 illustrates two OAM flows:
OAM flow originating from the CPE
The CPE-to-CPE OAM flow is transferred transparently by ETX-102 and treated
as data.
OAM flow originating from the ETX-102 devices.
The ETX-102 OAM flow runs on a data flow on the same VLAN.
The ETX-102 units terminate the OAM flow and can be referred as a
Maintenance Entity (ME). Each device supports up to 8 such MEs. In this case,
the ETX-102 units act as MEPs (Maintenance End-Points) and not as a MIP
(Maintenance Intermediate Points) and all measurements are performed on
the UNI_N to UNI_N segment.
B-2 Reference Architecture ETX-102 Ver. 3.8

Installation and Operation Manual Appendix B Operation, Administration, and Maintenance (OAM)
Figure B-1. OAM Architecture
Handling of OAM Levels
UNI_C to UNI_N Direction

In the UNI_C to UNI_N direction ETX-102 blocks all OAM messages with OAM level
greater than 2. Messages with other OAM levels are passed transparently.
Network Ingress to UNI_N Direction

All OAM messages coming from the network ingress with the ETX MAC address or
with the special OAM multicast address are sent to the CPU. All other OAM
messages are passed transparently to the user ports as per the respective flow
definition.
B.3 OAM Entities

This section describes the OAM entities hierarchy. Figure B-2 illustrates the
relationship between UNI, flow and Service Instance (COS ID), when one or more
service instances belong to one flow and one or more flow belong to a UNI. From
the OAM perspective, the continuity messages and defects are activated per flow,
and the PM is activated per service instance.
Note A flow can belong only to one UNI in the same ETX-102.
Figure B-2. UNI, Flow and Service Instance (COS ID)
Figure B-3, Figure B-4 and Figure B-5 illustrate different combinations of UNIs,
flows and service instances. Each UNI contains at least one flow, which contain at
least one service instance.
In the one flow per UNI case (Figure B-3), the PM and CC are transmitted
once.
ETX-102 Ver. 3.8 OAM Entities B-3

Figure B-3. One Flow per UNI
In case of multiple flows per UNI (Figure B-4), PM and CC are transmitted
three times.
Figure B-4. Multiple Flows per UNI
In case of one flow and multiple CoS (Service Instances) per UNI (Figure B-5),
the PM is transmitted three times and the CC once.
Figure B-5. One Flow and Multiple CoS (Service Instances) per UNI
B.4 OAM Flows

Figure B-6 illustrates a typical OAM traffic flow. The OAM message is transmitted
from the source MEP 1 to the destination MEP 2 and the reply is transmitted back
The source is also a destination for messages from the other direction.
The OAM interval is one second, so each NTU transmits one request and one
reply and receive one request and one reply. Total of four messages are
transmitted per second per service instance.
OAM Message
Request
MEP 1 MEP 2
OAM Message
Reply
Source Destination
Figure B-6. OAM Flow
OAM Message Addressing

The OAM defines two modes of addressing, unicast and multicast. Unicast
addressing is used for point-to-point connections, while multicast addressing is
B-4 OAM Flows ETX-102 Ver. 3.8

used in cases where the MAC address of the destination MEP is not known.
ETX-102 supports only point-to-point flows.
OAM Message Association

On the receiver side the OAM frame is associated with a flow and a service.
Flow Association
When an OAM frame is associated with a flow, the following steps are performed:
Request message reception
When a request message is received, the VLAN is extracted to find the Flow
ID. The Flow ID found at the receiver is compared against the Flow ID in the
frame. If the IDs are equal, further service association is made. If it is not
found, the Flow ID no match notification is returned in the reply message.
Reply message reception
When a reply message is received, the VLAN is extracted to find the Flow ID.
The Flow ID found at the receiver is compared against the Flow ID in the
frame. If the IDs are equal, further service association is made. If it is not
found, the frame is discarded and connectivity alarm is issued.
Service Association
When an OAM frame is associated with a service, the following steps are
performed:
Request message reception
The class of service characteristics are extracted from the frame and must be
matched to an entry in the flows <-> services table at the receiver. If they are
matched, the frame is processed. If not, the service ID is returned with the
Not Found notification.
Reply message reception
The class of service characteristics are extracted from the frame and must be
matched to an entry in the flow <-> services table at the receiver. If they are
matched, the frame is processed. If not, the frame is discarded.
Ethernet Loopback (ETH-LB)

The ETH-LB can be used to verify connectivity. The ETH-LB is performed by
sending a request ETH-LB message to the remote unit and expecting an ETH-LB
reply message back to verify connectivity. When the insertion rate of ETH-LB
messages is much slower compared to data rate between the flow points, ETH-LB
is suitable to perform in-service connectivity verification and to measure round
trip delays.
The message is initiated by the local device and runs periodically making it
suitable for fault detection.
Unicast ETH-LB request message is sent from a MEP to a specific MEP (remote
device). The DA of the request message is a unicast MAC address of destination
device. Upon receipt of the request message, the MEP responds with unicast ETH-
ETX-102 Ver. 3.8 OAM Flows B-5

LB reply message. The DA of the reply message is a unicast MAC address of

requesting device, learned from request message.
Continuity Check (ETH-CC)

Ethernet Continuity Check (ETH-CC) can be used to detect continuity failures
across flows between a given pair of edge service point on a flow. Continuity
failures are caused by:
Major failures (link failure, device failure, network path failure etc)
Minor failures (software failure, memory corruption, incorrect configuration
etc).
The ETH-CC signal is generated by one MEP. Upon receipt of the first ETH-CC
signal from a sending MEP, the receiving MEP detects continuity with sending MEP
and expects to receive further periodic ETH-CC signals. Once the receiving MEP
stops receiving periodic ETH-CC signals from sending MEP, it declares continuity
failure. The MEP that detects the continuity failure notifies the operator by
sending an alarm or a trap.
OAM Procedures
This section discusses the continuity check (CC) and the performance
measurement (PM) procedures.
Continuity Check Procedure

The loopback message and the ETH-CC messages are used for continuity check. In
case the services are defined and PM collection is enabled, they are also used to
carry PM messages. If PM collection is disabled, the messages are used for
continuity check only.
If the RX CC mode of the receiver is configured to CC-based, the continuity
detection is based on ETH-CC. If the mode is set to LB-based, the continuity
detection is based on ETH-LB. If the mode is disabled, the continuity detection is
not performed.
ETH-LB Method
The ETH-LB method includes the following elements:
Unicast ETH-LB transmission
Unicast ETH-LB request message is transmitted by a MEP (ETX-102) every
1 second. The transmitted Transaction Identifier is retained for at least
5 seconds after the unicast ETH-LB signal is transmitted. The Transaction
Identifier must be changed for every unicast ETH-LB message, and no
Transaction Identifier from the same MEP is allowed to be repeated within
1 minute.
Unicast ETH-LB reception and reply transmission
Whenever a valid unicast ETH-LB request message is received by MEP
(ETX-102), a unicast ETH-LB reply message is generated and transmitted to
the requesting MEP. Every field in the unicast ETH-LB request message is
copied to the unicast ETH-LB reply message with the following exceptions:

The source and destination MAC addresses are swapped.

The OpCode field is vendor-specific oxFE.
The Flow and MEP ID are processed as follows: if the Flow/MEP ID do not
exist in the device, it changes them to No Match otherwise they are left
intact.
Unicast ETH-LB reply receipt
When a unicast ETH-LB reply message is received by a MEP (ETX-102)
diagnostic flow termination function, it examines the TLVs returned in the
unicast ETH-LB reply message. The signal is declared invalid if the TLVs do not
match those sent in the corresponding unicast ETH-LB request signal,
including MEP ID and Flow ID.
Continuity declarations
Loss of Continuity and Connectivity Mismatch states are declared by the
ETH-LB mechanism.
Loss of continuity declaration
After the source device sends an ETH-LB message a timer is set with a
3.52 second timeout. If the destination device does send reply within the
timeout, the source enters the loss of continuity state. Upon reply from
the destination, the source resets the timer to 23.5 seconds. Regarding
the continuity check message, the source checks only the Flow ID with
the MEP ID. When the source enters the loss of continuity state, it adds
24 to Unavailable Seconds counter. The 23.5 second period is calculated
as a sliding window.
Loss of continuity state is cleared after 3.52 seconds with at least
21 reply messages from the destination. In this case the Unavailable
Seconds counter decreased by 24.
Connectivity mismatch declaration
If the source Flow ID is not equal to the destination Flow ID as recorded
in the reply message for 10 consecutive times, the source enters in to
misconnection state.
Misconnection state is cleared after 10 consecutive reply messages with
the correct flow name from the destination.
The Unavailable counter is maintained by the service according to the
number of PM messages that did not receive replies. If a mismatch
notification is received to the LB request, the frame is dropped and reply
message is not sent. This is why the service becomes unavailable (no
reply) in case of mismatch and the unavailable counter is raised.
ETH-CC Method
The ETH-CC method includes the following elements:
ETH-CC transmission
Unicast ETH-CC request message is transmitted by a MEP (ETX-102) every
1 second. The transmitted Transaction Identifier is retained for at least
5 seconds after the unicast ETH-CC signal is transmitted. The Transaction
Identifier must be changed for every Unicast ETH-CC message, and no
ETX-102 Ver. 3.8 OAM Flows B-7

Transaction Identifier from the same MEP is allowed to be repeated within

1 minute.
Unicast ETH-CC reply receipt
When a unicast ETH-CC message is received by a MEP (ETX-102) diagnostic
flow termination function, it examines the TLVs returned in the unicast
ETH-CC message, and declares the signal invalid if the TLVs do not match
those sent in the corresponding exiting MEP ID and Flow ID.
Continuity declarations
Loss of Continuity and Connectivity Mismatch states are declared by the
ETH-CC mechanism.
Loss of continuity declaration
When the MEP receives the ETH-CC message a timer is set with a
3.5 seconds timeout. If the source does send another message during
this period, the destination enters the loss of continuity state. Upon
receipt of the ETH-CC message, the destination resets the timer to
3.5 seconds. Regarding the continuity check message, the destination
check the Flow ID and the MEP ID. When the destination enters the loss
of continuity state, it adds 4 to the Unavailable Seconds counter. The
3.5 second period is calculated as a sliding window.
Loss of continuity state is cleared after 3.5 seconds with at least
2 messages from the source. In this case the Unavailable Seconds counter
is decreased by 4.
Connectivity mismatch declaration
If the source Flow ID is not equal to the destination Flow ID for
10 consecutive times, the destination enters in to misconnection state.
Misconnection state is cleared after 10 consecutive reply messages with
the correct flow name from the source.
The Unavailable counter is maintained by the service according to the
number of PM messages that did not receive replies. If a mismatch
notification is received to the LB request, the frame is dropped and reply
message is not sent. This is why the service becomes unavailable (no
reply) in case of mismatch and the unavailable counter is raised.
Performance Measurement
ETX-102 measures performance in 15-minute intervals. It also stores
performance history data from the last 24 hours (96 intervals). Table B-2 lists the
PM counters supported by ETX-102.
Table B-2. PM Counters
Frames Above Delay Obj. Number of frames that exceeded delay objective
Frames Below Delay Obj. Number of frames below or equal delay objective
Frames Above DV Obj. Number of frames that exceeded delay variation objective
Frames Below DV Obj. Number of frames below or equal delay variation objective

Frames Transmitted Total number of OAM frames transmitted in the current interval
Frames Lost Number of frames lost in the current interval
Unavailable Seconds Number of seconds during which the service was unavailable in the current
interval
Elapsed Time Time (in seconds) elapsed from beginning of the interval 0900
Min. RT Delay Minimum round trip delay (in mseconds) calculated in the interval (or up to
Avg. RT Delay Average round trip delay (in mseconds) calculated in the interval (or up to
Max. RT Delay Maximum round trip delay (in mseconds) calculated in the interval (or up
to elapsed time in current interval)
Avg. DV Average delay variation (in mseconds) calculated in the interval (or up to
Max. DV Maximum delay variation (in mseconds) calculated in the interval (or up to
OAM Transmitted Frames Total number of OAM frames transmitted since the service was enabled
Counter
OAM Frames Loss Counter Total number of OAM frames lost since the service was enabled
OAM Frame Loss Ratio Total number of lost OAM frames divided by total number of transmitted
OAM frames since the service was enabled
Elapsed Time Time (in seconds) elapsed since the service was enabled
Unavailable Seconds Total number of unavailable seconds since the service was enabled
Unavailability Ratio Total number of unavailable seconds divided by elapsed time
B.5 RMON Counters

In addition to the regular statistics collection, ETX-102 supports proactive SLA
measurements per ETX-102 port, as per RMON-based RFC 2819. The device
sends reports when one of the available counters (physical layer or OAM) rise
above or drop below the set thresholds within the specified sampling period of
time. These reports can be sent as SNMP traps to the defined network
management stations or be written to the event log.
The following counters can be monitored:
Frame Loss Ratio
Frames Above Delay
Frames Above Delay Variation
Unavailability Ratio.
ETX-102 Ver. 3.8 RMON Counters B-9

B-10 RMON Counters ETX-102 Ver. 3.8

Supplement
AC/DC Adapter
(AD) Plug
for DC Power Supply Connection
Note Ignore this supplement if the unit is AC-powered.
Certain units are equipped with a wide-range

AC/DC power supply. These units are equipped
with a standard AC-type 3-prong power input
connector located on the unit rear panel. This
power input connector can be used for both AC
and DC voltage inputs.
For DC operation, a compatible straight or
90-degree AC/DC Adapter (AD) plug for attaching Figure 1. Straight AD Plug
to your DC power supply cable is supplied with
your RAD product (see Figure 1 and Figure 2).
Connect the wires of your DC power supply cable
to the AD plug, according to the voltage polarity
and assembly instructions provided on page 2.
Figure 2. 90-Degree AD Plug
Caution
Prepare all connections to the AD plug before inserting it into the units power
connector.
Publication No. SUP-930-07/08 The Access Company

AC/DC Adapter (AD) Plug
To prepare the AD plug and connect it

to the DC power supply cable:
1. Loosen the cover screw on the bottom
of the AD plug to open it (see
Figure 3).
2. Run your DC power supply cable
through the removable cable guard
and through the open cable clamp.
3. Place each DC wire lead into the
appropriate AD plug wire terminal
according to the voltage polarity
mapping shown. Afterwards, tighten
the terminal screws closely.
4. Fit the cable guard in its slot and then
close the clamp over the cable.
Tighten the clamp screws to secure
the cable.
5. Reassemble the two halves of the AD
Figure 3. AD Plug Details
plug and tighten the cover screw.
6. Connect the assembled power supply
cable to the unit.
Note: You have to flip over the
non-90-degree AD plug type by
180 degrees to insert it into the unit.
After inserting it, verify that the blue
(negative) wire is connected to the
POWER and the brown (positive) wire is
connected to the RETURN.
Reversing the wire voltage polarity will not cause damage to the unit, but the
internal protection fuse will not function.
Warning Always connect a ground wire to the AD plugs chassis (frame) ground
terminal. Connecting the unit without a protective ground, or interrupting the
grounding (for example, by using an extension power cord without a
grounding conductor) can damage the unit or the equipment connected to it!
The AD adapter is not intended for field wiring.
2
Supplement
Terminal Block
Connector
for DC Power Supply Connection
Note Ignore this supplement if the unit is AC-powered.
Certain DC-powered units are equipped

with a plastic 3-pin VDC-IN power input
connector, located on the unit rear
panel. Different variations of the
connector are shown in Figure 1. All
0
are functionally identical.

Supplied with such units is a kit
including a mating Terminal Block (TB)
type connector plug for attaching to
your power supply cable.
Connect the wires of your power
supply cable to the TB plug, according
to the voltage polarity and assembly
instructions provided on the following
pages. Figure 1. TB DC Input Connector Types
Appearing on Unit Panels
Caution
Prepare all connections to the TB plug before inserting it into the units VDC-IN
connector.
Publication No. SUP-220-06/08 The Access Company

Terminal Block Connector
To prepare and connect the power

supply cable with the TB Plug:
Note: Refer to Figure 2 for assistance.
1
1. Strip the insulation of your power

supply wires according to the
dimensions shown.
2. Place each wire lead into the
appropriate TB plug terminal according
to the voltage polarity mapping shown
in Figure 3. (If a terminal is not already
2
open, loosen its screw.) Afterwards,

tighten the three terminal screws to
close them.
Figure 2. TB Plug Assembly
3. Pull a nylon cable tie (supplied) around
the power supply cable to secure it
firmly to the TB plug grip, passing the
tie through the holes on the grip.
4. Isolate the exposed terminal
screws/wire leads using a plastic
sleeve or insulating tape to avoid a
short-circuit.
5. Connect the assembled power supply
cable to the unit by inserting the
TB plug into the units VDC-IN
connector until it snaps into place. Figure 3. Mapping of the Power Supply Wire
Leads to the TB Plug Terminals
Reversing the wire voltage polarity can cause damage to the unit!
Always connect a ground wire to the TB plugs chassis (frame) ground
Warning terminal. Connecting the unit without a protective ground, or interruption of
the grounding (for example, by using an extension power cord without a
grounding conductor) can cause harm to the unit or to the equipment
connected to it!
2
Note: Certain TB plugs are equipped with

captive screws for securing the assembled
cables TB plug to the units VDC-IN
connector (C and E types only). To secure
the plug, tighten the two screws on the
plug into the corresponding holes on the
sides of the input connector as shown in
Figure 4.
3
Figure 4. TB Plug with Captive Screws (optional)
To disconnect the TB plug:

1. If the TB plug is equipped with captive screws, loosen the captive screws
(see Figure 4).
4
2. If the units VDC-IN connector is type B, lift the locking latch (see Figure 1).
5
3. Pull out the TB plug carefully.
Caution Always lift the locking latch of type B connectors before disconnecting the
TB plug, to avoid damaging the TB plug.
3
4
Supplement
Drilling Template for Wall Installation
Front Panel
1 1
176 mm (6.92 in)
3 3
2 2
101.6 mm (4 in)
This panel is drawn to scale.

To drill the holes for a wall installation, tear this page out
of the manual or print it on letter-size paper (8.5"x11.0") and
hold it against the wall.
LEDs facing up - drill at 1.
LEDs facing down - drill at 2.
LEDs facing left - drill at 3.
377-901-02/06
Publication No. 377-200-0(/1#
Order this publication by Catalog No. 803612
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North America Headquarters

900 Corporate Drive
Mahwah, NJ 07430, USA
Tel. 201-5291100
Toll free 1-800-4447234
Fax 201-5295777
E-mail market@rad.com
www.rad.com The Access Company

Basic Ethernet Demarcation Device: The Access Company

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

Basic Ethernet Demarcation Device: The Access Company

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

The Access Company

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

20042011 RAD Data Communications Ltd. Publication No. 377-200-0(/1#

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Achtung Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In Wohngebieten

Afin de faciliter la rutilisation, le recyclage ainsi que d'autres formes de

Instructions gnrales de scurit

Mise la terre de protection : la cosse ou la borne marque devrait tre connecte

Manipuler des produits sous tension

Rgles gnrales de scurit

Assurez-vous que l'installation lectrique est conforme la rglementation locale.

Manufacturer's Name: RAD Data Communications Ltd.

Manufacturer's Address: 24 Raoul Wallenberg St.

Declares that the product:

Product Name: ETX-102

Conforms to the following standard(s) or other normative document(s):

EMC EN 55022:2006 + Information technology equipment Radio disturbance

EN 55024:1998 + Information technology equipment Immunity characteristics

EN 61000-3-2:2006 Electromagnetic compatibility (EMC) - Part 3-2: Limits

EN 61000-3-3:1995 Electromagnetic compatibility (EMC) Part 3-3: Limits

Safety EN 60950-1:2005 Information technology equipment Safety Part 1:

Tel Aviv, 15 July 2010

European RAD Data Communications GmbH

Address A coded representation of the origin or destination of data.

Agent In SNMP, this refers to the managed system.

Analog A continuous wave or signal (such as human voice).

ANSI American National Standards Institute.

Balanced A transmission line in which voltages on the two conductors are

Bandwidth The range of frequencies passing through a given circuit. The

Baud Unit of signaling speed equivalent to the number of discrete

Best Effort A QoS class in which no specific traffic parameters and no

Bit The smallest unit of information in a binary system. Represents

Bit A process used in time division multiplexing where individual bits

Buffer A storage device. Commonly used to compensate for differences

Bus A transmission path or channel. A bus is typically an electrical

Byte A group of bits (normally 8 bits in length).

Channel A path for electrical transmission between two or more points.

Clock A term for the source(s) of timing signals used in synchronous

Data Information represented in digital form, including voice, text,

dB (Decibel) A unit used to measure relative increase or decrease in power,

dBm A measure of power in communications: the decibel in reference

Decibel See dB.

Diagnostics The detection and isolation of a malfunction or mistake in a

Digital The binary (1 or 0) output of a computer or terminal. In data

E3 The European standard for high speed digital transmission,

Encapsulation Encapsulating data is a technique used by layered protocols in

Flow Control A congestion control mechanism that results in an ATM system

Frame A logical grouping of information sent as a link-layer unit over a

Full Duplex A circuit or device permitting transmission in two directions

Gateway Gateways are points of entrance and exit from a communications

Half Duplex A circuit or device capable of transmitting in two directions, but

Impedance The combined effect of resistance, inductance and capacitance on

Interface A shared boundary, defined by common physical interconnection

IP Address Also known as an Internet address. A unique string of numbers

Laser A device that transmits an extremely narrow and coherent beam

Loopback A type of diagnostic test in which the transmitted signal is