Manual Rad ETX-1

OPERATION MANUAL
INSTALLATION AND
ETX-1
Ethernet Demarcation Switch
Version 1.2
ETX-1
Ethernet Demarcation Switch
Version 1.2
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-1 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-1 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-1. 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-1, based
on or derived in any way from the ETX-1. Your undertaking in this paragraph shall survive the
termination of this Agreement.
This Agreement is effective upon your opening of the ETX-1 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-1 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: [email protected] E-mail: [email protected]
19882013 RAD Data Communications Ltd. Publication No. 659-200-08/13

Front Matter Installation and Operation Manual
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the ETX-1 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-1, and in no event shall
RAD's liability exceed the purchase price of the ETX-1.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to ETX-1 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the ETX-1 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-1 shall not
exceed the sum paid to RAD for the purchase of the ETX-1. 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.
ii ETX-1 Ver. 1.2

Installation and Operation Manual Front Matter
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.
ETX-1 Ver. 1.2 iii

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.
iv ETX-1 Ver. 1.2

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.
ETX-1 Ver. 1.2 v

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.
vi ETX-1 Ver. 1.2

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.
ETX-1 Ver. 1.2 vii

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.
viii ETX-1 Ver. 1.2

Certains produits peuvent tre quips d'une diode laser. Dans de tels cas,
Franais
une 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.
ETX-1 Ver. 1.2 ix

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.
Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
x ETX-1 Ver. 1.2

ANSI American National Standards Institute.
APS (Automatic An automatic service restoration function by which a network senses

protection switching) a circuit or node failure and automatically switches traffic over an
alternate path.
AWG The American Wire Gauge System, which specifies wire width.
Backhaul Transporting traffic between distributed sites (typically access points)

and more centralized points of presence
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.
Bipolar Signaling method in E1/T1 representing a binary 1 by alternating

positive and negative pulses, and a binary 0 by absence of pulses.
Bit The smallest unit of information in a binary system. Represents either

a one or zero (1 or 0).
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.
CESoPSN Structure-aware TDM Circuit Emulation Service over Packet Switched

Network. A method for encapsulating structured (NxDS0) Time
Division Multiplexed (TDM) signals as pseudo-wires over packet
switched networks (PSN).
Channel A path for electrical transmission between two or more points. Also
called a link, line, circuit or facility.
CIR (Committed A term, which defines the information rate that the network is
committed to provide to the user, under any network conditions.
ETX-1 Ver. 1.2 xi

Information Rate)
Circuit Emulation New technology for offering circuit emulation services over packet-
Service switched networks. The service offers traditional TDM trunking (at n x
64 kbps, fractional E1/T1, E1/T1 or E3/T3) over a range of transport
protocols, including Internet Protocol (IP), MPLS and Ethernet.
CLI Command Line Interface (CLI) is a mechanism for interacting with a

RAD product by typing commands in response to a prompt.
Clock A term for the source(s) of timing signals used in synchronous

transmission.
Congestion A state in which the network is overloaded and starts to discard user
data (frames, cells or packets).
Congestion Control A resource and traffic management mechanism to avoid and/or

prevent excessive situationthat can cause the network to collapse.
Data Information represented in digital form, including voice, text, facsimile

and video.
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.
E1 Line A 2.048 Mbps line, common in Europe, that supports thirty-two

64 kbps channels, each of which can transmit and receive data or
digitized voice. The line uses framing and signaling to achieve
synchronous and reliable transmission. The most common
configurations for E1 lines are E1 PRI, and unchannelized E1.
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.
EIR Excess Information Rate. The rate that exceeds a specified threshold
(CIR) for brief periods of time.
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).
xii ETX-1 Ver. 1.2

Ethertype A two-octet field in an Ethernet frame that indicates type of the

protocol encapsukated in the Ethernet frame payload
Flow Unidirectional traffic entity that connects two physical or logical ports
Flow Control A congestion control mechanism
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.
G.703 An ITU standard for the physical and electrical characteristics of

various digital interfaces, including those at 64 kbps and 2.048 Mbps.
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.
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).
J1 Digital interconnection protocol similar to T1 and E1 used in Japan.
Jitter The deviation of a transmission signal in time or phase. It can

introduce errors and loss of synchronization in high speed
synchronous communications.
L2CP Set of Layer-2 control (slow) protocols that operate across a number
of access and aggregation network technologies
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).
Latency The time between initiating a request for data and the beginning of
the actual data transfer. Network latency is the delay introduced
ETX-1 Ver. 1.2 xiii

when a packet is momentarily stored, analyzed and then forwarded.
Load Balancing A technique that distributes network traffic along parallel paths in
order to maximize the available network bandwidth while providing
redundancy.
Loading The addition of inductance to a line in order to minimize amplitude

distortion. Used commonly on public telephone lines to improve voice
quality, it can make the lines impassable to high speed data, and
baseband modems.
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.
Mark In telecommunications, this means the presence of a signal. A mark is

equivalent to a binary 1. A mark is the opposite of a space (0).
Master Clock The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Modular Modular interfaces enable field-changeable conversion.
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.
NodeB The name of the BTS for 3G cellular traffic
NTP The Network Time Protocol, a protocol for synchronizing the clocks of
computer systems over packet-switched, variable-latency data
networks. NTP uses UDP on port 123 as its transport layer.
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.
xiv ETX-1 Ver. 1.2

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.
Policing A method for verifying that the incoming traffic complies with the
users service contract.
Polling See Multidrop.
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.
Prompt One or more characters in a command line interface to indicate that

the computer is ready to accept typed input.
Protocol A formal set of conventions governing the formatting and relative

timing of message exchange between two communicating systems.
Pseudowire Point-to-point connections set up to emulate (typically Layer 2) native

services like TDM, or SONET/SDH over an underlying common packet-
switched network (Ethernet, MPLS or IP) core. Pseudowires are
defined by the IETF PWE3 (pseudowire emulation edge-to-edge)
working group.
Queuing Technique used in the QoS architecture during periods of congestion.

The packets are held in queues for subsequent processing. After being
processed by the router, the packets are then sent to their
destination based on priority. Strict priority and Weighted Fair queuing
methods are used for traffic differentiation.
Q-in-Q See MAC-in-MAC.
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.
Scalable Able to be changed in size or configuration to suit changing

conditions. For example, a scalable network can be expanded from a
ETX-1 Ver. 1.2 xv

few nodes to thousands of nodes.
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).
SAToP Structure-Agnostic Time Division Multiplexing (TDM) over Packet. A

method for encapsulating Time Division Multiplexing (TDM) bit-
streams (T1, E1, T3, E3) that disregards any structure that may be
imposed on these streams, in particular the structure imposed by the
standard TDM framing.
SONET (Synchronous A North American standard for using optical media as the physical
Optical Network) transport for high speed long-haul networks. SONET basic speeds
start at 51.84 Mbps and go up to 2.5 Gbps.
Space In telecommunications, the absence of a signal. Equivalent to a binary

0.
SSH (Secure Shell) A network protocol that allows data to be exchanged over a secure
channel between two computers. Encryption provides confidentiality
and integrity of data.
SVI A logical port used for binding flows to bridge ports, router interfaces
or Layer-2 TDM pseudowires
Sync See Synchronous Transmission.
Syslog Communcation standard for data logging. It collects heterogeneous

data into a single data repository, providing system administrators
with a single point of management for collecting, distributing and
processing audit data. The Syslog operation is standartized by RFC
3164 and RFC 5674.
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.
T3 A digital transmission link with a capacity of 45 Mbps, or 28 T1 lines.
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.
Throughput The amount of information transferred through the network between

two users in a given period, usually measured in the number of
packets per second (pps).
Timeslot A portion of a serial multiplex of timeslot information dedicated to a

single channel. In E1 and T1, one timeslot typically represents one 64
kbps channel.
Traffic Management Set of actions and operations performed by the network to guarantee
the operability of the network, exercised in the form of traffic control
xvi ETX-1 Ver. 1.2

and flow control.
Traffic Policing Mechanism whereby any traffic which violates the traffic contract
agreed to at connection setup, is detected and discarded.
Traffic Shaping A method for smoothing the bursty traffic rate that might arrive on an
access virtual circuit so as to present a more uniform traffic rate on
the network.
Trunk A single circuit between two points, both of which are switching
centers or individual distribution points. A trunk usually handles many
channels simultaneously.
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.
Zero suppression Technique used to ensure a minimum density of marks.
ETX-1 Ver. 1.2 xvii

Quick Start Guide
This section describes the minimum configuration needed to prepare ETX-1 for
operation.
1. Installing the Unit

Perform the following steps to install ETX-1:
1. Determine the required configuration of ETX-1, according to your application.
2. Connect the user/network ports as required for the application.
3. Connect the ASCII terminal to the control port.
4. Connect power to the unit.
Connecting the Interfaces

To connect the interfaces:
1. Insert the SFP modules (if applicable) into the relevant SFP-based Ethernet
ports.
2. Connect the optical cables.
3. Connect the network port(s) to the service provider network equipment.
4. Connect the user port(s) to the customer network equipment.
Notes The number of available Ethernet ports depends on the options you
purchased.
Lock the wire latch of each SFP module by lifting it up until it clicks into place.
For additional information, refer to Chapter 2.
Connecting to a Terminal
To connect the unit to a terminal:
1. Connect the mini-USB connector of the cable supplied by RAD to the control
connector.
2. Connect the other side of the cable to the ASCII terminal equipment.
2. Configuring the Unit for Management

Configure ETX-1 for management, using a local ASCII-based terminal.
ETX-1 Ver. 1.2 Configuring the Unit for Management 1

Quick Start Guide Installation and Operation Manual
Starting a Terminal Session for the First Time

To start the terminal session:
1. Connect an ASCII terminal to the CONTROL port.
2. Configure the ASCII terminal to the settings listed below and then set the
terminal emulator to VT100 emulation for optimal view of system menus.
Baud Rate: 9,600 bps
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
3. If you are using HyperTerminal, set the terminal mode to 132-column mode
for optimal view of system menus (Properties> Settings> Terminal Setup>
132 column mode).
4. Power-up ETX-1.
5. ETX-1 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
6. Press <ENTER> until you receive the login prompt.
7. To log in, enter your user name (su for full configuration and monitoring
access) and your password.
8. The device prompt appears:
ETX-1#
You can now type the necessary CLI commands.
Configuring SVI
SVI 1 must be administratively enabled in order to administratively enable the
corresponding flows and router interface.
To administratively enable SVI 1:

Enter the following commands:
configure port svi 1
no shutdown
exit all
Configuring Management Flows

The following is an example of configuring management flows for out-of-band
management via the Ethernet management port. The management flows are set
up between the Ethernet management port and SVI 1.
2 Configuring the Unit for Management ETX-1 Ver. 1.2

Installation and Operation Manual Quick Start Guide
To define the management flows:

configure flows
# Classifier-profile to allow untagged traffic
classifier-profile untagged match-any match untagged
# Classifier-profile to allow all traffic
classifier-profile all match-any match all
# Flow from management Ethernet port to SVI 1

flow mng_in
classifier untagged
no policer
ingress-port ethernet 101
egress-port svi 1 queue 1
no shutdown
exit
# Flow from SVI 1 to management Ethernet port

flow mng_out
classifier all
ingress-port svi 1
egress-port ethernet 101 queue 0 block 0/1
no shutdown
exit all
Configuring Router
The router must be configured with a router interface that is bound to the SVI
used for the management flows, and assigned an IP address. In addition, a static
route must be set up for the default gateway.
This section illustrates the following configuration:
Router interface 1:
Bound to SVI 1
IP address 192.168.99.238 with mask 255.255.255.0
Router: Static route associated with IP address 192.168.99.1 (default
gateway).
To define the router:

ETX-1 Ver. 1.2 Configuring the Unit for Management 3

Quick Start Guide Installation and Operation Manual
configure router 1
interface 1
bind svi 1
# IP address 192.168.99.238 with mask 255.255.255.0
address 192.168.99.238/24
no shutdown
exit
# Default gateway 192.168.99.1
static-route 0.0.0.0/0 address 192.168.99.1
exit all
3. Saving Management Configuration
Saving Configuration
Type save in any level to save your configuration in startup-config.
Copying User Configuration to Default Configuration

In addition to saving your configuration in startup-config, you may also wish to
save your configuration as a user default configuration.
To save user default configuration:

exit all
file copy startup-config user-default-config
Are you sure? [yes/no] _ yes
4 Saving Management Configuration ETX-1 Ver. 1.2

Contents
Introduction ............................................................................................................................ 1-1
1.1 Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-1
Applications ....................................................................................................................... 1-1
Features ............................................................................................................................ 1-2
Service Types ................................................................................................................ 1-2
Flow Classification ......................................................................................................... 1-3
Tagging and Marking ..................................................................................................... 1-4
Quality of Service (QoS) ................................................................................................ 1-4
Ethernet OAM ............................................................................................................... 1-5
Jumbo Frames and Egress MTU ...................................................................................... 1-5
Link Aggregation ........................................................................................................... 1-5
G.8032v2 Ethernet Ring Protection (ERP)...................................................................... 1-5
L2CP Handling ............................................................................................................... 1-5
Fault Propagation .......................................................................................................... 1-5
Management ................................................................................................................. 1-6
SFTP .............................................................................................................................. 1-6
Statistics Collection ....................................................................................................... 1-6
Simple Network Time Protocol ...................................................................................... 1-7
Diagnostic Tools ............................................................................................................ 1-7
1.2 New in This Version .............................................................................................................. 1-7
1.3 Physical Description ............................................................................................................. 1-7
1.4 Functional Description .......................................................................................................... 1-8
1.5 Technical Specifications........................................................................................................ 1-9
Installation and Setup .............................................................................................................. 2-1

2.1 Site Requirements and Prerequisites .................................................................................... 2-1
2.2 Package Contents................................................................................................................. 2-1
2.3 Mounting the Unit ................................................................................................................ 2-2
2.4 Installing SFP Modules .......................................................................................................... 2-2
2.5 Connecting to Ethernet Equipment....................................................................................... 2-3
Connecting the Copper Interface ....................................................................................... 2-3
Connecting the Fiber Optic Interface.................................................................................. 2-3
2.6 Connecting to ASCII Terminal ................................................................................................ 2-4
2.7 Connecting to Power ............................................................................................................ 2-4
Connecting to AC Power .................................................................................................... 2-5
External AC Power: ........................................................................................................ 2-5
Internal AC Power: ........................................................................................................ 2-5
2.8 Connecting to Management Station ..................................................................................... 2-5
Operation ............................................................................................................................... 3-1

3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-1
3.3 Startup ................................................................................................................................. 3-2
Configuration Files ............................................................................................................. 3-2
Loading Sequence .............................................................................................................. 3-3
3.4 Using a Custom Configuration File ........................................................................................ 3-3
3.5 Turning Off the Unit ............................................................................................................. 3-3
ETX-1 Ver. 1.2 i

Table of Contents Installation and Operation Manual
Management and Security ........................................................................................................ 4-1

4.1 Management Access Methods .............................................................................................. 4-1
4.2 Working with Terminal.......................................................................................................... 4-2
Login ................................................................................................................................. 4-6
Using the CLI ...................................................................................................................... 4-7
Command Tree .................................................................................................................. 4-9
4.3 Working with Telnet and SSH ............................................................................................. 4-23
4.4 Working with RADview ....................................................................................................... 4-24
4.5 Working with SNMP ............................................................................................................ 4-24
4.6 Configuring Device Information .......................................................................................... 4-25
Displaying Device Information .......................................................................................... 4-26
4.7 Configuring SNMP Management ......................................................................................... 4-26
Standards ........................................................................................................................ 4-26
Benefits ........................................................................................................................... 4-27
Functional Description ..................................................................................................... 4-27
Factory Defaults .............................................................................................................. 4-27
Setting SNMP Parameters ................................................................................................ 4-29
Example ........................................................................................................................... 4-35
4.8 Controlling Management Access ......................................................................................... 4-40
Setting Management Access Parameters .......................................................................... 4-40
4.9 Defining Access Policy ........................................................................................................ 4-41
Configuring Access Policy ................................................................................................. 4-41
4.10 Authenticating via RADIUS Server ....................................................................................... 4-42
Standards ........................................................................................................................ 4-42
Benefits ........................................................................................................................... 4-42
Configuring RADIUS Parameters ....................................................................................... 4-43
Example ........................................................................................................................... 4-43
Displaying RADIUS Statistics............................................................................................. 4-44
4.11 Authenticating via TACACS+ Server ..................................................................................... 4-44
Standards ........................................................................................................................ 4-45
Benefits ........................................................................................................................... 4-45
Configuring TACACS+ Servers ........................................................................................... 4-45
Example Defining Server ............................................................................................... 4-46
Example Displaying Statistics ........................................................................................ 4-46
Configuring Accounting Groups ........................................................................................ 4-47
Example Defining Accounting Group .............................................................................. 4-47
4.12 Configuring Terminal Control Port ...................................................................................... 4-48
Setting Control Port Parameters ...................................................................................... 4-48
4.13 Configuring User Access ..................................................................................................... 4-49
Example Defining Users................................................................................................. 4-49
Example Displaying Users .............................................................................................. 4-51
Services .................................................................................................................................. 5-1

5.1 Ethernet Flow Mode ............................................................................................................. 5-1
5.2 Ethernet Bridge Mode .......................................................................................................... 5-2
ii ETX-1 Ver. 1.2

Installation and Operation Manual Table of Contents
Ports ....................................................................................................................................... 6-1

6.1 Ethernet Ports ...................................................................................................................... 6-1
Configuring Ethernet Port Parameters ................................................................................ 6-2
Setting Second Network Interface as Network or User Port ............................................... 6-3
Displaying Ethernet Port Status ......................................................................................... 6-4
Testing Ethernet Ports ....................................................................................................... 6-5
Displaying Ethernet Port Statistics ..................................................................................... 6-6
Displaying Port Statistics ............................................................................................... 6-6
Example ........................................................................................................................ 6-7
Clearing Statistics .......................................................................................................... 6-8
6.2 Service Virtual Interface ....................................................................................................... 6-9
Configuring Service Virtual Interfaces ................................................................................. 6-9
Resiliency ................................................................................................................................ 7-1

7.1 Link Aggregation .................................................................................................................. 7-1
Standards and MIBs ........................................................................................................... 7-1
Benefits ............................................................................................................................. 7-1
Functional Description ....................................................................................................... 7-1
Factory Defaults ................................................................................................................ 7-1
Configuring LAG ................................................................................................................. 7-1
Example ............................................................................................................................. 7-3
Displaying LAG Status ........................................................................................................ 7-4
7.2 Fault Propagation ................................................................................................................. 7-4
Standards .......................................................................................................................... 7-4
Benefits ............................................................................................................................. 7-4
Configuring Fault Propagation ............................................................................................ 7-5
Adding Fault Propagation Entry ..................................................................................... 7-6
Configuring Fault Propagation Parameters .................................................................... 7-6
Example ........................................................................................................................ 7-7
Disabling Fault Propagation ........................................................................................... 7-8
7.3 Ethernet Ring Protection (ERP) ............................................................................................. 7-9
Standards .......................................................................................................................... 7-9
Benefits ............................................................................................................................. 7-9
Ring Topology ............................................................................................................... 7-9
R-APS Messaging ......................................................................................................... 7-10
Mechanism of Operation ............................................................................................. 7-10
Timers ......................................................................................................................... 7-10
Administrative Commands ........................................................................................... 7-10
Configuring ERP ............................................................................................................... 7-11
Displaying ERP Status .................................................................................................. 7-13
Displaying ERP Statistics.............................................................................................. 7-13
Example ...................................................................................................................... 7-14
Networking ............................................................................................................................. 8-1

8.1 Layer 2 Control Processing ................................................................................................... 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-1
ETX-1 Ver. 1.2 iii

Adding Layer 2 Control Processing Profiles ........................................................................ 8-1

Deleting Layer 2 Control Processing Profiles ...................................................................... 8-2
Configuring Layer 2 Control Processing Profile Parameters ................................................ 8-2
Example ............................................................................................................................. 8-3
8.2 Ethernet Bridge .................................................................................................................... 8-4
Standards .......................................................................................................................... 8-4
Configuring the Bridge ....................................................................................................... 8-5
Example Defining RSTP.................................................................................................... 8-8
Example Defining Bridge .................................................................................................. 8-9
Displaying VLAN Members ................................................................................................ 8-11
Displaying MAC Address Table .......................................................................................... 8-11
8.3 Quality of Service (QoS) ..................................................................................................... 8-13
Standards ........................................................................................................................ 8-13
Benefits ........................................................................................................................... 8-13
Queue Mapping Profiles ................................................................................................... 8-14
Factory Defaults .......................................................................................................... 8-14
Configuring Queue Mappings ...................................................................................... 8-14
CoS Mapping Profiles ....................................................................................................... 8-15
Configuring CoS Mapping Profiles ................................................................................ 8-15
Example ...................................................................................................................... 8-16
Bandwidth Profiles ........................................................................................................... 8-16
Configuring Shaper Profiles ......................................................................................... 8-17
Configuring Policer Profiles.......................................................................................... 8-18
Queue Block Profiles ........................................................................................................ 8-19
Adding Queue Block Profiles........................................................................................ 8-19
Configuring Queue Block Profile Parameters................................................................ 8-20
Example ...................................................................................................................... 8-20
Queue Group Profiles ....................................................................................................... 8-21
Adding Queue Group Profiles ...................................................................................... 8-21
Configuring Queue Group Parameters ......................................................................... 8-21
Example ...................................................................................................................... 8-22
8.4 Flows ................................................................................................................................. 8-22
Standards ........................................................................................................................ 8-23
Benefits ........................................................................................................................... 8-23
Defining Classifier Profiles ............................................................................................... 8-28
Example Defining Classifier Profiles ............................................................................... 8-29
Configuring Flows ............................................................................................................ 8-29
Example Defining flows ................................................................................................. 8-31
Example Displaying Flow Summary ................................................................................ 8-33
Example Defining P2MP Flows ....................................................................................... 8-33
8.5 Ethernet OAM .................................................................................................................... 8-34
OAM CFM (Connectivity Fault Management) ..................................................................... 8-34
Standards ................................................................................................................... 8-35
Benefits ...................................................................................................................... 8-35
Functional Description................................................................................................. 8-35
iv ETX-1 Ver. 1.2


Configuring OAM CFM General Parameters .................................................................. 8-37
Configuring Maintenance Domains .............................................................................. 8-38
Configuring Maintenance Associations ........................................................................ 8-39
Configuring Maintenance Endpoints ............................................................................ 8-40
Configuring Maintenance Intermediate Points Manually............................................... 8-42
Configuring Maintenance Intermediate Points Automatically ....................................... 8-43
Examples ..................................................................................................................... 8-43
Configuring Maintenance Endpoint Services ................................................................ 8-46
Configuring Destination NEs ........................................................................................ 8-47
Example ...................................................................................................................... 8-48
Configuring OAM CFM Service Event Reporting ............................................................ 8-49
Example ...................................................................................................................... 8-51
Displaying OAM CFM Statistics..................................................................................... 8-53
Examples ..................................................................................................................... 8-58
Performing OAM Loopback .......................................................................................... 8-62
Performing OAM Link Trace ......................................................................................... 8-63
OAM EFM ......................................................................................................................... 8-63
Standards ................................................................................................................... 8-64
Benefits ...................................................................................................................... 8-64
Functional Description................................................................................................. 8-64
Configuring OAM EFM .................................................................................................. 8-64
Example ...................................................................................................................... 8-66
8.6 Router ................................................................................................................................ 8-66
Benefits ........................................................................................................................... 8-66
Factory Default ................................................................................................................ 8-66
Configuring the Router .................................................................................................... 8-67
Timing and Synchronization ..................................................................................................... 9-1

9.1 Working with SNTP ............................................................................................................... 9-1
Factory Defaults ............................................................................................................ 9-1
Configuring SNTP Parameters ........................................................................................ 9-1
Defining SNTP Servers ................................................................................................... 9-2
Configuring SNTP Server Parameters ............................................................................. 9-2
Example ........................................................................................................................ 9-3
Administration ....................................................................................................................... 10-1

10.1 Clearing Device Statistics .................................................................................................... 10-1
10.2 Date and Time.................................................................................................................... 10-1
Setting the Date and Time ............................................................................................... 10-1
Displaying the Date and Time .......................................................................................... 10-2
10.3 Working with the Inventory ................................................................................................ 10-2
Standards and MIBs ......................................................................................................... 10-2
Benefits ........................................................................................................................... 10-2
Displaying Inventory Information ..................................................................................... 10-2
Setting Administrative Inventory Information ................................................................... 10-4
Example ........................................................................................................................... 10-4
10.4 Displaying Environment ...................................................................................................... 10-6
10.5 Displaying Software Versions ............................................................................................. 10-7
10.6 Displaying CPU and Memory Utilization ............................................................................... 10-7
ETX-1 Ver. 1.2 v

10.7 File Operations ................................................................................................................... 10-8

Downloading/Uploading Files ........................................................................................... 10-9
SFTP Application .......................................................................................................... 10-9
TFTP Application ........................................................................................................ 10-11
Using CLI to Download/Upload Files ............................................................................... 10-14
Example Download via TFTP ................................................................................... 10-14
Example Download via SFTP ................................................................................... 10-14
Example Upload via TFTP ........................................................................................ 10-14
Example Upload via SFTP ........................................................................................ 10-15
Copying Files within Device ............................................................................................ 10-15
Example .................................................................................................................... 10-15
Displaying Copy Status ................................................................................................... 10-15
Displaying Information on Files ...................................................................................... 10-15
Deleting Files ................................................................................................................. 10-17
10.8 Saving Configuration ........................................................................................................ 10-17
10.9 Reset ............................................................................................................................... 10-18
Resetting to Factory Defaults ........................................................................................ 10-18
Resetting to User Defaults ............................................................................................. 10-19
Restarting the Unit ........................................................................................................ 10-19
Monitoring and Diagnostics .................................................................................................... 11-1

11.1 Detecting Problems ............................................................................................................ 11-1
LEDs ................................................................................................................................ 11-1
Alarms and Traps ............................................................................................................. 11-1
Statistic Counters ............................................................................................................ 11-1
11.2 Handling Alarms and Events ............................................................................................... 11-1
Configuring Alarm and Event Properties ........................................................................... 11-2
Working with Alarm and Event Logs ................................................................................. 11-4
Alarms and Events Supported by Device .......................................................................... 11-5
Traps Supported by Device ............................................................................................ 11-10
Configuring the Global Performance Monitoring Function .............................................. 11-13
11.3 Syslog .............................................................................................................................. 11-14
Configuring Syslog Parameters ....................................................................................... 11-14
Displaying Syslog Statistics ............................................................................................ 11-15
11.4 Troubleshooting ............................................................................................................... 11-16
Troubleshooting Chart ................................................................................................... 11-16
11.5 Performing Diagnostic Tests ............................................................................................. 11-17
Running a Ping Test ....................................................................................................... 11-17
Tracing the Route .......................................................................................................... 11-17
11.6 Frequently Asked Questions ............................................................................................. 11-18
11.7 Technical Support ............................................................................................................. 11-18
Software Upgrade ................................................................................................................. 12-1

12.1 Compatibility Requirements................................................................................................ 12-1
12.2 Impact ................................................................................................................................ 12-1
12.3 Prerequisites ...................................................................................................................... 12-1
12.4 Upgrading the Device Software via CLI ............................................................................... 12-2
Verifying the Host Parameters ......................................................................................... 12-2
Pinging the PC .................................................................................................................. 12-2
Activating the SFTP Server ............................................................................................... 12-3
Activating the TFTP Server ............................................................................................... 12-3
Downloading the Software .............................................................................................. 12-3
vi ETX-1 Ver. 1.2

Installing Software ........................................................................................................... 12-4

Restoring Previous Active Software.................................................................................. 12-5
12.5 Upgrading the Device Software via the Boot Menu ............................................................. 12-5
Accessing the Boot Menu................................................................................................. 12-6
Using the XMODEM Protocol ............................................................................................ 12-7
Using FTP ......................................................................................................................... 12-8
Using TFTP ....................................................................................................................... 12-8
Activating Software ......................................................................................................... 12-9
12.6 Verifying Upgrade Results .................................................................................................. 12-9
Application Tutorial ................................................................................................................ 13-1

13.1 Flow-Based Application ...................................................................................................... 13-1
Configuring the ETX-36 Server ......................................................................................... 13-1
Accessing the Unit ...................................................................................................... 13-1
Configuring Management Flow .................................................................................... 13-2
Configuring Data Flow ................................................................................................. 13-3
Configuring the ETX-36 Client .......................................................................................... 13-4
Accessing the Unit ...................................................................................................... 13-4
Configuring Data Flow ................................................................................................. 13-6
13.2 Ethernet Ring Protection .................................................................................................... 13-7
Equipment List ................................................................................................................. 13-7
Installing the Units ........................................................................................................... 13-7
Configuration Sequence ................................................................................................... 13-8
Configuring Ethernet Ring Protection ............................................................................... 13-9
Configuring Bridge Port ............................................................................................... 13-9
Configuring VLAN ........................................................................................................ 13-9
Configuring Ethernet Ring Protection .......................................................................... 13-9
Connector Wire Data ............................................................................................................... A-1
ETX-1 Ver. 1.2 vii

viii ETX-1 Ver. 1.2

Chapter 1
Introduction
1.1 Overview
ETX-1 is a carrier Ethernet demarcation device owned and operated by the service
provider and installed at the customer premises, which delivers SLA-based
Ethernet business services to the customer premises over native Ethernet access.
It serves as a clear demarcation point between the user and operator networks.
Incoming customer traffic is classified and mapped according to port-based
(all-to-one) bundling, or by user port and CE VLAN-ID, VLAN priority, DSCP, IP
precedence, MAC, IP address, and Ethertype. This offers operators the flexibility
to differentiate services using different kinds of classification methods, police the
traffic, and enforce SLA per service.
ETX-1 supports powerful bandwidth profiles such as CIR/CBS for differentiated
Ethernet services and includes comprehensive Ethernet OAM (Operation,
Administration, and Maintenance) functionality together with SLA monitoring.
The network ports support configurable static LAG link aggregation. At the
physical layer, ETX-1 supports auto-negotiation and fault propagation.
The unit can be managed via a local terminal port, or via a dedicated out-of-band
Ethernet port. Additionally, ETX-1 can be managed inband, via a user or network
port.
Product Options
The basic port type is Fast Ethernet, which can be optionally increased to Gigabit
Ethernet.
Network ports Up to two SFP-based fiber optic or electrical, depending on
whether port 2 is configured as network or user port.
User ports Up to four electrical, or five if port 2 is configured as user port.
Applications
ETX-1 delivers Ethernet services as defined by the MEF standards.
Packet
Switched
ETX-1 Network ETX-1
CPE CPE
Figure 1-1. EPL Service
ETX-1 Ver. 1.2 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
CPE
ETX-1
PSN
ETX-2
CPE
ETX-1
CPE
Figure 1-2. EVPL Service
Features
Service Types
ETX-1 provides port-based and flow-based services.
Port-Based Service
In a typical port-based (all-to-one bundling) application ETX-1 receives different
services via different network ports (Figure 1-3). This method achieves clearer
service separation, it does not require any marking for CoS, and provides
straightforward SLA measurement.
Provider Node Customer Premises
Ethernet FE VoIP
PE Aggregator
Packet GbE FE Premium
Switched Network Data
(ETH, IP or MPLS)
ETX-1
FE Best Effort
Data
Figure 1-3. Port-Based Service
Flow-Based Service
In a typical flow-based application different services are assigned to different
Ethernet flows received by the same network port (Figure 1-4). This provides a
cheaper, more scalable solution, with the possibility of mixing different types of
service.
1-2 Overview ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 1 Introduction
Provider Node Customer Premises
Ethernet
PE Aggregator
Fast Ethernet (FE)
Packet GbE Premium Best Effort
Switched Network VoIP
Data Data
(ETH, IP or MPLS)
ETX-1
Figure 1-4. Flow-Based Service
Flow Classification
The ingress user traffic is mapped to the Ethernet flows using the following list of
per-port classification criteria. In the classifications, VLAN refers to the service
provider (outer) VLAN, previously referred to as SP-VLAN, while inner VLAN refers
to the Customer Entity VLAN, previously referred to as CE-VLAN.
vlan
p-bit
ip-precedence
ip-dscp
src-mac/ dst-mac
src-mac + to-src-mac (Source MAC address to source MAC address)/dst-mac +
to-dst-mac (Destination MAC address to destination MAC address)
src-ip/ dst-ip
src-ip + to-src-ip (Source IP address to source IP address)/dst-ip + to-dst-ip
(Destination IP address to destination IP address)
ether-type
untagged
non-ip
all
vlan + inner-vlan
vlan + p-bit
vlan + ip-dscp
vlan + src-mac/dst-mac
vlan + src-ip/dst-ip
vlan + ether-type
vlan + non-ip
vlan + src-ip + to-src-ip
vlan +dst-ip + to _dst_ip
vlan +src_mac + to_src_mac
vlan +dst_mac + to_dst_mac
vlan + inner-vlan + p-bit

vlan + ip-precedence
ETX-1 supports up to 32 Ethernet flows. Flows are unidirectional. Flow
classification variant is limited to only one or one same combination for the same
interface. On same Ethernet port, cannot accept different flow classification
combination, except VLAN and untagged, IP and non-IP.
Tagging and Marking

ETX-1 supports several options for marking and tagging.
You can perform the following marking actions:
Overwrite inner or outer VLAN with a new value
Overwrite inner or outer VLAN p-bit with a new value.
You can perform the following tagging actions:
Add (push) outer VLAN with a p-bit value. When you add a new VLAN, the
original outer VLAN becomes the inner VLAN.
Remove (pop) outer VLAN and p-bit. When you remove a VLAN, the inner
VLAN becomes the outer VLAN.
Add (push) inner VLAN with p-bit value
Remove (pop) inner VLAN and p-bit.
Only certain combinations of actions on the outer and inner VLAN are allowed.
Refer to Chapter 8 for details on the permitted combinations of actions.
Quality of Service (QoS)

Different types of service require different levels of QoS to be provided end-to-
end. QoS can be defined per subscriber as well as per flow. QoS has three
aspects: rate limitation, traffic shaping, and traffic prioritization.
Traffic Prioritization
Once traffic is classified to a flow, it can be mapped to Strict (Strict Priority)
queues or WRR (Weighted Round Robin):
Strict: Strict Priority strictly complies with the priority sequence from high to
low, and it sends packets in the high-priority queue first. When that queue is
empty, strict priority begins to send packets in lower priority queue. By
putting the key service packets in the high priority queues, you can ensure
that they can always be served first. At the same time, the common service
packets can be put in the low priority queues and transmitted when there are
no key service packets waiting for transmission.
WRR: Weighted Round Robin is a scheduling algorithm that uses weights
assigned to queues to determine how much frames will be sent from a queue
before moving to the next queue.

Ethernet OAM
ETX-1 provides OAM to monitor and troubleshoot an Ethernet network and
quickly detect failures:
CFM OAM (End-to-end OAM) based on IEEE 802.1ag and Y.1731 for continuity
check, non-intrusive loopback, and Frame loss, frame delay and frame delay
variation measurement.
EFM OAM (Link OAM) according to IEEE 802.3-2005 (formerly IEEE 802.3ah)
for remote management and fault indication, including dying gasp, and MIB
parameter retrieval.
Jumbo Frames and Egress MTU

ETX-1 supports large frames of up to 9216 bytes. The egress MTU is a global
parameter, it should be same on all ports.
Link Aggregation
ETX-1 supports static link aggregation (LAG) without the LACP protocol according
to 802.3-2005.
G.8032v2 Ethernet Ring Protection (ERP)

G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and
prevent loops at the Ethernet layer.
Ethernet Ring Protection technology provides scalable solution for low-cost traffic
protection and rapid service restoration.
One particular link is called the ring protection link (RPL), and under normal
conditions this link is blocked. One designated node, the RPL owner, is
responsible to block traffic over the RPL. Under a ring failure condition, the RPL
owner is responsible to unblock the RPL, allowing the RPL to be used for traffic.
An APS protocol is used to coordinate the protection actions over the ring.
Note ETX-1 supports only one ring protection for network port 1 and 2.
L2CP Handling
ETX-1 can be configured to pass through Layer-2 control frames (including other
vendors L2CP frames) across the network, to peer-supported protocols
(IEEE 802.3-2005), or to discard L2CP frames.
Fault Propagation
The unit provides the following types of fault propagation:
Network-to-user fault propagation mechanism on the port and OAM CFM
levels When fault propagation is enabled, the user port shuts itself down or
an OAM CFM indication of failure is sent when a link failure is detected at the
network port or when an OAM CFM indication of failure is received.

User-to-network fault propagation mechanism on the port and OAM CFM

levels. When fault propagation is enabled, an OAM CFM indication of failure is
sent to the Network port once a failure is detected on User port.
Management
ETX-1 can be managed as follows:
Local management via ASCII terminal connected to the V.24/RS-232 DCE
control port based on a mini-USB connector.
Local management via dedicated out of band (OOB) management port.
Remote management via an Ethernet port using Telnet SSH or an
SNMP-based management system. ETX-1 supports the SNMP version 3 entity,
providing secure access to the device by authenticating and encrypting
packets transmitted over the network.
Command Line Interface

You can create data bases and scripts of commonly used commands and easily
apply them to multiple units in your infrastructure using RADs new command line
interface.
Security
To ensure client-server communication privacy and correct user authentication,
ETX-1 supports the following security protocols:
SSH
SNMPv3
SFTP
RADIUS (client authentication)
TACACS+ (client authentication)
Syslog
The syslog protocol is a client/server-type protocol, featuring a standard for
forwarding log messages in an IP network. It supports up to four syslog servers. A
syslog sender sends a small text message of less than 1024 bytes to the syslog
server. Syslog messages are sent via UDP in cleartext.
SFTP
SFTP (Secure File Transfer Protocol) is supported, to provide secure encrypted file
transfer using SSH.
Statistics Collection
ETX-1 collects performance statistics for the physical layers of the network/user
ports, and Radius.

Simple Network Time Protocol

ETX-1 supports Simple Network Time Protocol (SNTP) for propagating and
receiving time information on a network, according to SNTPv4 (RFC 4330)
requirements. SNTP is used to configure date and time by learning the
information from a single or multiple NTP servers. The clock can be configured to
a local time by defining UTC and DST offsets.
Diagnostic Tools
ETX-1 offers several types of diagnostic procedures:
Ping test Check IP connectivity by pinging remote IP hosts.
Trace route Quickly trace a route from ETX-1 to any other network device
Loopback tests:
Layer-1 loopback performed at the PHY of the physical ports. When the
loopback is active the data forwarded to a port is looped from the Tx
path to the Rx path, thereby disrupting the traffic. This loopback cannot
pass through Ethernet bridges.
1.2 New in This Version

Below are the ETX-1 features introduced in version 1.2:
Rapid Spanning Tree Protocol
1.3 Physical Description

Figure 1-5 shows a 3D view of a typical of ETX-1.
The ETX-1 interface connections are described in greater detail in Chapter 2.
Figure 1-5. ETX-1, 3D View
ETX-1 Ver. 1.2 Physical Description 1-7

1.4 Functional Description

Figure 1-6 shows the data flow in the device. Table 1-1 provides an overview of
the traffic handling stages.
ETX-1 OAM is compatible with other RAD products that support standard OAM
functionality.
ETX-1
Figure 1-6. Data Flow
Table 1-1. Traffic Handling Stages
Processing Stage Description
Classiffier Classifying the traffic to classes of service
Flow Engine Classifying the traffic to flow. Unclassified traffic will be

forwarded based on the bridge decision to the queue manage.
Flow Policer Enabling per flow rate limitation
Queue Manage Reassign per flow port/queue. Traffic not classified to flows
will go to port/queue according to DA/CoS
Egress Queue The queues can be configured to be strict priority, Weighted

round robin or hybrid mode. Weights are user configurable.
Shaping is done per queue or per port. Network port has 6
COS whereas user port has 4 CoS.
Flow Editing Enabling flow P-bit remarking and Vlan stacking
1-8 Functional Description ETX-1 Ver. 1.2

1.5 Technical Specifications
Network Interface Number of Ports Up to 2 (RJ-45 or fiber optic SFPs). The second port
can be configured as a network or user port.
Type Fast or Gigabit Ethernet
Electrical Operation 10/100 Mbps or 10/100/1000 Mbps, full duplex,

Mode autonegotiation, MDI/MDIX
User Interface Number of Ports Up to 4 (RJ-45). If the second network port is

configured as a user port, there are five user ports.
Type Fast or Gigabit Ethernet
Electrical Operation 10/100 Mbps or 10/100/1000 Mbps, full duplex,

Mode autonegotiation, MDI/MDIX
Standards IEEE 802.3, 802.1d, 802.1q, 802.1p, 802.1ax, 802.1ad,

Compliance 802.3-2005, 802.1ag, 802.3ah
Ethernet Flows Number of Flows 32
Management Local Via dedicated terminal port; V.24/RS-232 DCE;

9.6, 19.2, 38.4, 57.6, 115.2 kbps; Mini-USB
connector
Inband Via one of the Ethernet ports
Out-of-band Via dedicated management port
Power External AC Input: 100-240VAC

(Plastic Enclosure) Output: 12VDC
Power Consumption 6W max
Power Internal AC 100 - 240V; 47- 63 Hz

(Metal Enclosure)
Power Consumption 6W max
Physical Height 42 mm (1.7 in)

(Plastic Enclosure)
Width 218 mm (8.6 in)
Depth 170 mm (6.7 in)
Weight 0.4 kg (0.9 lb)
ETX-1 Ver. 1.2 Technical Specifications 1-9

Physical Height 45 mm (1.8 in)

(Metal Enclosure)
Width 215 mm (8.5 in)
Depth 300 mm (11.8 in)
Weight 1.9 kg (4.2 lb)
Environment Temperature 0C to 50C (32F to 122F)
Humidity Up to 90%, non-condensing
1-10 Technical Specifications ETX-1 Ver. 1.2

Chapter 2
Installation and Setup
This chapter describes installation and setup procedures for the ETX-1 unit.
After installing the unit, refer to Chapter 3 for operating instructions and
Chapter 4 for management instructions.
If a problem is encountered, refer to Chapter 11 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.
2.1 Site Requirements and Prerequisites

Internal AC-powered units should be installed within 1.5 m (5 ft) of an
easily-accessible grounded AC outlet capable of furnishing the voltage in
accordance with the nominal supply voltage.
External AC-powered units require an AC power adapter.
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-1 is 0C to 50C (32F to 122F) at a
relative humidity of up to 90%, non-condensing.
2.2 Package Contents

The ETX-1 package includes the following items:
One ETX-1 unit
Compatible SFP module(s) (if ordered)
V.24/RS-232 control port cable based on the mini-USB connector
AC power cord if AC power supply ordered
RM-33-2 rack mount kit (if ordered).
ETX-1 Ver. 1.2 Package Contents 2-1

Chapter 2 Installation and Setup Installation and Operation Manual
2.3 Mounting the Unit

ETX-1 is designed for installation as a desktop unit. It can also be mounted in a
19-inch"- rack or on a wall.
For rack mounting instructions, refer to the associated installation kit manual
For wall mounting instructions, refer to the drilling template at the end of
this manual.
Refer to the clearance and temperature requirements in Site Requirements and
Prerequisites.
2.4 Installing SFP Modules

ETX-1 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 I laser equipment.
Warning
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 the SFP into the socket, and gently push the SFP until
the it 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.
2-2 Installing SFP Modules ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 2 Installation and Setup
Caution Insert the SFP gently. Using force can damage the connecting pins.
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 (as opposed to locking).
3. Hold the wire latch and pull the SFP module out of the Ethernet port.
Caution Do not remove the SFP while the fiber optic cables are still connected. This may
result in physical damage (such as a chipped SFP module clip or socket), or cause
malfunction (e.g., the network port redundancy switching may be interrupted)
2.5 Connecting to Ethernet Equipment
Connecting the Copper Interface

Figure 2-2 shows a typical rear panel of an ETX-1 unit with four copper
interfaces.
To connect to the Ethernet equipment with a copper interface:

Connect ETX-1 to the Ethernet equipment using a standard straight UTP
cable terminated with an RJ-45 connector.
Figure 2-2. Electrical Connectors
Connecting the Fiber Optic Interface

Figure 2-3 shows a typical rear panel of the ETX-1 unit with the fiber optic
interfaces.
To connect user Ethernet equipment to an SFP with LC connector:

Connect ETX-1 to the Ethernet equipment using a standard fiber optic cable
terminated with an LC connector.
ETX-1 Ver. 1.2 Connecting to Ethernet Equipment 2-3

Figure 2-3. Fiber Optic Connectors
2.6 Connecting to ASCII Terminal

To connect to an ASCII terminal:
1. Connect the mini-USB connector of V.24/RS-232 cable to the CONTROL
connector.
2. Connect the other connector of the V.24/RS-232 cable to an ASCII terminal.
Caution Terminal cables must have a frame ground connection

Use ungrounded cables when connecting a supervisory terminal to a external
AC unit with floating ground
Using improper terminal cable may result in damage to supervisory terminal
port.
Figure 2-4. Control Connectors
2.7 Connecting to Power
Before connecting this unit to a power source and connecting or disconnecting

any other cable, the protective ground terminals of this unit must be connected
to the protective ground conductor of the mains (AC or DC) power cord. If you
Warning
are using an extension cord (power cable) make sure it is grounded also.
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.
2-4 Connecting to Power ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 2 Installation and Setup
Connecting to AC Power
AC power should be supplied via a 1.5 m (5 ft) standard power cable terminated
by a standard 3-prong socket. A cable is provided with the unit.
External AC Power:
AC power is supplied with the external AC power adapter provided with the unit.
To connect AC power:
1. Connect the power adapter output cable to the power connector on the
ETX-1 rear panel.
2. Connect the power adapter to the main outlet.
The unit turns on automatically upon connection to the mains.
Internal AC Power:
To connect AC power:
1. Connect the power cable to the power connector on the ETX-1 rear panel.
2. Connect the power cable to the main outlet.
The unit turns on automatically once connected to the mains.
2.8 Connecting to Management Station

ETX-1 is connected to remote network management stations via the dedicated
Ethernet management port, an 8-pin RJ-45 connector designated MNG-ETH. Refer
to Appendix A for the connector pinout.
To connect to an NMS:
Connect ETX-1 to an Ethernet switch.
Note
To provide protection against surges, use shielded cables when connecting to the
MNG-ETH port.
Figure 2-5: Ethernet Management Connector
ETX-1 Ver. 1.2 Connecting to Management Station 2-5

2-6 Connecting to Management Station ETX-1 Ver. 1.2

Chapter 3
Operation
This chapter provides the following information:
Power-on and power-off procedures
A detailed description of the front panel controls and indicators, and their
functions.
For a detailed explanation of parameters, see Chapter 6-10.
3.1 Turning On the Unit

To turn on ETX-1:
Connect the power cord to the mains.
The PWR indicator lights up and remains lit as long as ETX-1 receives
power.
ETX-1 requires no operator attention once installed, with the exception of
occasional monitoring of front panel indicators. Intervention is required only
when configuring ETX-1 to its operational requirements, or performing diagnostic
tests.
3.2 Indicators
The unit's LEDs are located on the front panel (see Figure 3-1). Table 3-1 lists the
functions of the ETX-1 LED indicators.
ETX-1
Figure 3-1. Device LEDs
Table 3-1. LEDs and Controls
Name Color Function

PWR/TST/ALM Green/red ON (green) Power is ON
ON (red) There is at least one active alarm
Blinking Diagnostic loopback is active
ETX-1 Ver. 1.2 Indicators 3-1

Chapter 3 Operation Installation and Operation Manual
Name Color Function

NET 1 Green ON Corresponding Ethernet link is OK
Blinking Data is being transmitted or received on the corresponding
Ethernet link
NET/ USER 2 Green ON Corresponding Ethernet link is OK
Blinking Data is being transmitted or received on the corresponding
Ethernet link
USER Green ON Corresponding Ethernet link is OK
3,4,5,6 Blinking Data is being transmitted or received on the corresponding
Ethernet link
MNG-ETH Green ON Corresponding Ethernet link is OK
Blinking Data is being transmitted or received on the management Ethernet
link
Note The number of network and user ports and their corresponding LEDs depends on
the hardware configuration.
3.3 Startup
Configuration Files
The following files contain configuration settings:
factory-default-config Contains the manufacturer default settings
rollback-config Serves as a backup for startup-config. At startup,
rollback-config is loaded if it exists and is valid, and if startup-config is
missing or invalid.
running-config Contains the configuration that the device is currently
running
startup-config Contains saved non-default user configuration. This file is
not automatically created. You can use the save or copy command to create
it. At startup, startup-config is loaded if it exists and is valid.
user-default-config Contains the default user configuration. This file is not
automatically created. You can use the copy command to create it. At
startup, startup-config is loaded if it exists and is valid.
Refer to Chapter 10 for details on file operations.
Loading Sequence
At startup, the device attempts to load configuration files in the following
sequence until a valid one is found:
startup-config
rollback-config
3-2 Startup ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 3 Operation
user-default-config
factory-default-config.
If an error is encountered while loading a file, the default is to ignore the error
and continue loading. You can use the on-configuration-error command to
change this behavior, either to stop loading the file and go to the next
configuration file, or to reject the file and reboot.
To display the parameter values after startup, use the command info
[detail].
3.4 Using a Custom Configuration File

In large deployments, a central network administrator often sends configuration
scripts to the remote locations. The local technician only needs to replace the IP
address in the script or make other minor changes (using any text editor), and
then download the file to the unit.
Note To edit configuration files, it is recommended to use a text editor such as

Wordpad or Notepad++.
To download the configuration file, use the copy command, as explained in

Chapter 10.
After downloading the configuration file, the unit must be reset in order to
execute the file. After the unit completes its startup, the custom configuration is
complete.
3.5 Turning Off the Unit

To power off the unit:
Remove the power cord from the power source.
ETX-1 Ver. 1.2 Turning Off the Unit 3-3

Chapter 3 Operation Installation and Operation Manual
3-4 Turning Off the Unit ETX-1 Ver. 1.2

Chapter 4
Management and Security
This chapter describes the following:
Management and configuration options
Working with a terminal connected to the ETX-1 control port
Using the command line interface (CLI)
CLI command tree
Management Flows
Management-related features.
Initial configuration of the management parameters is usually performed via ASCII
terminal. Once the management flows and corresponding router interface have
been configured, it is possible to access ETX-1 via Telnet or SNMP for operation
configuration. Refer to the Quick Start Guide for an example of management
configuration. For details on configuring the router, refer to Chapter 8.
4.1 Management Access Methods

Table 4-1 summarizes management alternatives for ETX-1.
Table 4-1. Management Alternatives
Port Manager Transport Method Management Application

Location Protocol
CONTROL Local Out-of-band RS-232 Terminal emulation applications

such as HyperTerminal, Procomm,
Putty, SecureCRT, Tera Term (see
Working with Terminal below)
MNG-ETH Local, remote Out-of-band Telnet, SSH Terminal emulation application

(see Working with Telnet and SSH
below)
SNMP Third-party NMS (see Working

with SNMP below)
NET Local, remote Inband Telnet, SSH Terminal emulation application

NET/USER (see Working with Telnet and SSH
USER below)
SNMP Third-party NMS (see Working

with SNMP below)
ETX-1 Ver. 1.2 Management Access Methods 4-1

Chapter 4 Management and Security Installation and Operation Manual
Note By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled. Refer to the section on Controlling Management Access for details
on enabling/disabling a particular method.
4.2 Working with Terminal

ETX-1 has a V.24/RS-232 control port based on mini-USB connector. The control
port continuously monitors the incoming data stream and immediately responds
to any input string received through this port. You can use any terminal
emulation program to manage ETX-1 via the control port; the following procedure
uses HyperTerminal.
To start a terminal control session:

1. Make sure all ETX-1 cables and connectors are properly connected.
2. Connect ETX-1 to a PC equipped with an ASCII terminal emulation application
(for example, HyperTerminal). Refer to Chapter 2 for details on connecting to
the control port.
3. Start the PC terminal emulation (in Windows XP: Select Start > All Programs >
Accessories > Communications> HyperTerminal to create a new terminal
connection).
The HyperTerminal application opens, and the Connection Description
dialog box is displayed.
4-2 Working with Terminal ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 4 Management and Security
Figure 4-1. HyperTerminal with Connection Description Dialog Box
4. Enter a name for the connection.

5. Select an icon to represent the terminal connection, or keep the selected
default icon.
6. Click <OK>.
The Connect To dialog box is displayed.
Figure 4-2. Connect To Dialog Box
ETX-1 Ver. 1.2 Working with Terminal 4-3

7. Select a PC COM port to be used to communicate with ETX-1, and click <OK>.
The COM Properties dialog box is displayed.
Figure 4-3. COM1 Properties Dialog Box
8. Configure the communication port parameters as follows:

Bits per second: 9,600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
9. Click <OK> to close the COM Properties dialog box.
HyperTerminal is now ready for communication with the unit.
Note It is not necessary to set the emulation type.
10. Power-up ETX-1.

The boot manager of ETX-1 starts, and displays a message stating that
you can stop the auto-boot and enter the boot manager by pressing any
key. It also displays a countdown of the number of seconds remaining
until auto-boot. If it reaches 0 before you press a key, then a message
appears after a few seconds, stating that the active software pack is
being loaded.

Figure 4-4. HyperTerminal Window after Startup
After a few more seconds, the login prompt user>_ is displayed. Refer to
Login for details on logging in.

Figure 4-5. Login Prompt
Login
To prevent unauthorized modification of the operating parameters, ETX-1
supports two access levels:
Superuser can perform all the activities supported by the ETX-1 management
facility, including defining new users.
User 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 superuser:
1. At the User prompt (user>), enter su and press <Enter>.
The Password prompt (password>) appears.
2. Enter 1234 as password and press <Enter>.
The base prompt ETX-1# appears.

Superuser allows you to configure all parameters of ETX-1 and to change the su
and user passwords.
To enter as user:
1. Enter user as user name and press <Enter>.
2. Enter 1234 as password and press <Enter>.
The base prompt ETX-1# appears.
Using the CLI

The CLI consists of commands organized in a tree structure, starting at the base
prompt. The base prompt is the device name, which can be configured at the
system level (refer to Configuring Device Information). By default the device
name is ETX-1.
Commands that are not global are available only at their specific tree location. To
find out what commands are available at the current location, type ?. For a list of
the commands and their levels, refer to Command Tree.
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location, followed by #. To navigate up, use the global command
exit. To navigate directly up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed optionally by a command. If only level names are typed, navigation is
performed and the prompt changes to reflect the current location in the tree. If
the level names are followed by a command, the command is executed, but no
navigation is performed and the prompt remains unchanged.
Note To use show commands without navigating, type show followed by the level
name(s) and the rest of the show command.
In the following example, the levels and command were typed together and
therefore no navigation was performed, so the prompt has not changed.
ETX-1#
ETX-1# configure port ethernet 1 loopback local
ETX-1# show configure port ethernet 1 loopback
Loopback : Local Forever
ETX-1#
Figure 4-6. Commands Without Level Navigation

In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX-1#
ETX-1# configure
ETX-1>config# port
ETX-1>config>port# ethernet 1
ETX-1>config>port>eth(1)# loopback local
ETX-1>config>port>eth(1)# show loopback
Loopback : Local Forever
ETX-1>config>port>eth(1)#
Figure 4-7. Commands With Level Navigation
Note Level names are abbreviated in the prompt.
You can type only as many letters of the level or command as required by the
system to identify the level or command; for example, you can enter
config manag to navigate to the management level.
In addition to being the default prompt, the character # also indicates a static
entity (such as a port) or already configured entity. The character $ indicates a
new dynamic entity (such as a flow) that takes several commands to configure.
The dynamic entity is created as inactive. After the configuration is completed, it
is activated by using the no shutdown command, as shown in the following
example.
ETX-1#
ETX-1# configure flows flow flow1
ETX-1>config>flows>flow(flow1)$ ingress-port ethernet 3
ETX-1>config>flows>flow(flow1)$ egress-port ethernet 1 queue 0 block 0/1
ETX-1>config>flows>flow(flow1)$ classifier Classifier1
ETX-1>config>flows>flow(flow1)$ no shutdown
ETX-1>config>flows>flow(flow1)$ exit
ETX-1>config>flows#
Figure 4-8. Creating and Activating Flow
The shutdown command is also used to deactivate/disable a hardware element

(such as a port), while no shutdown enables/activates it.
CLI commands have the following basic format:
command [parameter]{ value1 | value2 | | valuen }
[ optional parameter <value> ]
where:
{} Indicates that one of the values must be selected

[] Indicates an optional parameter
<> Indicates a value to be typed by user according to
parameter requirements
The following keys are available at any time:
? Lists all commands available at the current level

<Tab> Command autocomplete

Displays the previous command
Displays the next command
<Backspace> Deletes character
<Ctrl-C> Interrupts current command
<Ctrl-Z> Returns to configuration root
<Ctrl-E> Exit CLI
The commands shown in Table 4-5 are available at any level.

CLI commands can be gathered into text files called scripts. They can be created
using a text editor, by recording the user commands, or by saving the current
configuration. The scripts can be imported from and exported to RAD devices via
file transfer protocols.
Command Tree
At the CLI root, the following categories are available:
configure
file
admin
global-commands.
Each category is detailed in the tables below.
Table 4-2. Commands in the configure Category
Command Description
configure Enter configure level
| bridge Defines bridge parameters
| | aging-time Enable/Disable period for entries to age in the MAC

table
| | clear-mac-table Clear MAC addresses
| | filtering Determines the bridge forwarding mode
| | port Defines the behavior and attributes of bridge ports
| | | accept-frame-type Enable/Disable frame admission rule for the bridge

port
| | | clear-statistics Clears the statistics
| | | ingress-filtering Enable ingress filtering mode behavior
| | | name Port name
| | | pvid PVID assigned to untagged frames or priority-

tagged frames

Command Description
| | | queue-mapping Assigns a priority mapping
| | | show bind
| | | spanning-tree
| | | | admin-edge Set the edge port admin status
| | | | auto-edge Set the edge port automatically
| | | | cost Set the path-cost for the port
| | | | mcheck Force the port to transmit RST BPDUs
| | | | priority Assign the priority value on the port
| | | | shutdown Enable/Disable spanning-tree on the port
| | | | show status Display spanning-tree status for bridge port
| | static-mac Enable/Disable filtering for the bridge in VLAN-

aware mode
| | vlan Enables/disables VLAN membership specifications
| | | name VLAN name
| | | tagged-egress Add/Remove bridge port as VLAN tagged member
| | | untagged-egress Add/Remove bridge port as VLAN egress untagged

member
| | vlan-aware Enable Layer 2 bridging according to the VLAN tag
| | spanning-tree
| | | forward-time Configure the time duration in Listening and

Learning states that precede the Forwarding state,
in seconds
| | | hello-time Configure the time interval in seconds between

BPDU transmissions
| | | max-age Configure the maximum age of the configuration

BPDU can be maintained on a device.
| | | mode Select the operation mode for spanning-tree
| | | priority Assign the bridge priority value
| | | tx-hold-count Configure the maximum number of BPDUs

transmitted
| | | show status Display spanning-tree status
| | show mac-address-table Displays MAC addresses
| | show vlans Display VLAN members
| chassis Enter chassis level
| | show environment Display hardware component statuses
| | temperature-threshold Specify temperature thresholds

Command Description
| fault Enter fault level
| | cfm Enter fault CFM level
| | | service Configure event reporting for service
| | | | frames-report Define event reporting type for service
| | | | shutdown Activate or deactivate the event reporting
| | fault-propagation Configure fault propagation
| | | action-on-group Action(s) to perform in order to propagate a fault
| | | trigger Trigger for propagating fault
| | | wait-to-restore Define the time between recovery and resumption

of transmission
| flows Enter flows level
| | classifier-profile Configure a classifier profile
| | | match Specifies the criteria for the classifier profile
| | flow Configure flow
| | | classifier Associate the flow with a classifier profile
| | | drop Discard traffic transmitted via the flow
| | | egress-port Define the egress port of the flow
| | | ingress-port Define the ingress port of the flow
| | | mark Enter marking level for overwriting VLAN or inner

VLAN
| | | | inner-p-bit Overwrite p-bit for inner VLAN
| | | | inner-vlan Overwrite inner VLAN
| | | | p-bit Overwrite p-bit for VLAN
| | | | vlan Overwrite VLAN with a new value
| | | policer Associate the flow with a policer profile
| | | shutdown Activate or deactivate the flow
| | | vlan-tag Perform push/pop of VLAN or inner VLAN,

optionally with p-bits
| | show summary Display information for all flows
| management Configure management parameters
| | access Specifies access paths and rights
| | | auth-policy Configure policy of authentication
| | | sftp Configure sftp access
| | | snmp Configure SNMP access
| | | ssh Configure SSH access

Command Description
| | | telnet Configure Telnet access
| | | tftp Configure tftp access
| | radius Specifies RADIUS parameters
| | | clear-statistics Clears the RADIUS statistics
| | | server Defines the RADIUS server
| | | | address Specifies the RADIUS server's IP address
| | | | auth-port Specifies the RADIUS server authentication port
| | | | key Specifies the shared secret between client and

RADIUS server
| | | | retry Configure number of request attempts from

RADIUS server
| | | | shutdown Enable/disable RADIUS server
| | | | timeout Configure timeout for a response from RADIUS

server
| | | show statistics Displays the RADIUS server statistics
| | | show status Displays the RADIUS server status
| | snmp Configure SNMP parameters
| | | access-group Configure SNMPv access group
| | | | context-match Configure context match
| | | | notify-view Configure notify view
| | | | read-view Configure read view
| | | | shutdown Activate or deactivate SNMPv access group
| | | | write-view Configure write view
| | | community Configure SNMPv3 community
| | | | name Configure SNMPv3 community name
| | | | sec-name Configure SNMPv3 community security name
| | | | shutdown Activate or deactivate
| | | | tag Configure SNMPv3 community tag
| | | notify Configure SNMPv3 notification
| | | | bind Configure SNMPv3 notification bind
| | | | shutdown Activate or deactivate SNMPv3 notification
| | | | tag Configure SNMPv3 notification tag
| | | notify-filter Configure SNMPv3 notification filter
| | | | mask Configure SNMPv3 notification filter mask
| | | | shutdown Activate or deactivate SNMPv3 notification filter

Command Description
| | | | type Configure SNMPv3 notification filter type
| | | notify-filter-profile Configure SNMPv3 notification filter profile
| | | | profile-name Configure SNMPv3 notification filter profile name
| | | | shutdown Activate or deactivate SNMPv3 notification filter

profile
| | | security-to-group Configure security for access group
| | | | group-name Specify access group
| | | | shutdown Activate or deactivate security for access group
| | | snmp-engine-id Aadministratively assigned identification string (up

to 27 characters).
| | | target Configure SNMPv3 target
| | | | address Configure SNMPv3 target address
| | | | shutdown Activate or deactivate SNMPv3 target
| | | | tag-list Configure SNMPv3 target tag list
| | | | target-params Configure SNMPv3 target parameters
| | | | trap-sync-group Configure trap synchronization group
| | | target-params Configure SNMPv3 target parameters
| | | | message-processing-model Configure SNMPv3 target parameters message

processing model
| | | | security Configure SNMPv3 target parameters security
| | | | shutdown Activate or deactivate SNMPv3 target parameters
| | | | version Configure SNMPv3 target parameters version
| | | trap-sync-group Configure trap synchronization group with SNMPv3

managers
| | | | tag-list Configure tag list for trap synchronization group
| | | | target-params Configure target parameters for trap

synchronization group
| | | user Configure SNMPv3 user
| | | | authentication Configure authentication for SNMPv3 user
| | | | privacy Configure privacy for SNMPv3 user
| | | | shutdown Activate or deactivate SNMPv3 user
| | | view Configure SNMPv3 view
| | | | mask Configure SNMPv3 view mask
| | | | shutdown Activate or deactivate
| | | | type Configure SNMPv3 view type

Command Description
| | | show snmpv3 Displays SNMPv3 information
| | | show trap-sync Displays trap synchronization group
| | tacacsplus TACACS+ parameters
| | | group Creates a group for binding TACACS+ servers
| | | | accounting Configure TACACS+ accounting for the group
| | | server Configure TACACS+ server
| | | | accounting-port Set accounting TCP port for a TACACS+ server
| | | | authentication-port Set authentication TCP port for a TACACS+ server
| | | | clear-statistics Cleas the TACACS+ statistics
| | | | group Bind / unbind TACACS+ server to / from a group
| | | | key Specifiy the shared secret of Tacacs+ server
| | | | retry Configure number of request attempts from

TACACS server
| | | | shutdown Enable/disable TACACS+ server
| | | | timeout Configure timeout for a response from TACACS

server
| | | | show statistics Display TACACS+ server statistics
| | user Create/delete user
| | show users Display users
| oam Enter OAM level
| | cfm Enter OAM CFM level
| | | maintenance-domain Configure a maintenance domain (MD)
| | | | maintenance-association Configure a maintenance association (MA)
| | | | | ccm-interval Define the continuity check interval of the MA
| | | | | classification Associate the MA with a VLAN
| | | | | mep Configure a maintenance endpoint (MEP)
| | | | | | ais Define sending of AIS
| | | | | | bind Bind MEP to Ethernet port
| | | | | | ccm-initiate Enable or disable continuity check messages
| | | | | | ccm-priority Define the priority of the CC message
| | | | | | classification Associate the MEP with a classifier profile or VLAN
| | | | | | client-md-level Define client MD level

Command Description
| | | | | | dest-addr-type Define MAC address types sent in OAM continuity

check messages and in performance measurement
messages, as standard multicast address or
user-defined unicast address
| | | | | | dest-mac-addr Define the unicast MAC address sent in OAM CCM

messages if you defined unicast MAC address type
for CCM messages
| | | | | | direction Define direction
| | | | | | lbm Configure OAM loopback
| | | | | | linktrace Configure OAM link trace
| | | | | | queue Define queue for the MEP
| | | | | | remote-mep Define a remote MEP for the MEP
| | | | | | service Configure MEP service
| | | | | | | classification Associate service with p-bit
| | | | | | | clear-statistics Clear the OAM CFM statistics for the MEP service
| | | | | | | delay-threshold Define delay threshold for the MEP service
| | | | | | | delay-var-threshold Define delay variation threshold for the MEP service
| | | | | | | dest-ne Configure destination NE
| | | | | | | | clear-statistics Clear the OAM CFM statistics for destination NE
| | | | | | | | delay Enable two-way delay measurement method
| | | | | | | | loss Enable single-ended loss measurement method
| | | | | | | | pm-collection Enable/disable PM collection
| | | | | | | | remote Define remote MAC address or remote MEP ID
| | | | | | | | show statistics Display the OAM CFM statistics for destination NE
| | | | | | | dmm-interval Specify the interval for delay measurement

messages
| | | | | | | lmm-interval Specify the interval for loss measurement

messages
| | | | | | | pm-collection Enable/disable PM collection
| | | | | | | shutdown Activate or deactivate the MEP service
| | | | | | | show statistics Display the OAM CFM statistics for service
| | | | | | shutdown Activate or deactivate the MEP
| | | | | | show lbm-results Display result of OAM loopback
| | | | | | show linktrace-results Display result of OAM linktrace
| | | | | | show status Display status of MEP
| | | | | name Define the name of the MA

Command Description
| | | | md-level Define the level of the MD
| | | | mip Configure a maintenance intermediate point (MIP)
| | | | | bind Binding the MIP to an Ethernet port
| | | | | flow Assigning unidirectional Rx and Tx flows to the MIP
| | | | | shutdown Activate or deactivate the MIP
| | | | | show status Display status of MIP
| | | | name Define the name of the MD
| | | mip-assign Define whether MIPs are configured automatically

or manually
| | | show mips Display MIPs that currently exist
| | | show summary Display OAM CFM information
| | efm Enter OAM EFM level
| | | descriptor Configure OAM EFM descriptor
| port Enter configure port level
| | ethernet Configure Ethernet port
| | | auto-negotiation Configure auto negotiation ability
| | | clear-efm-statistics Clear OAM EFM statistics for Ethernet port
| | | clear-statistics Clear Ethernet port statistics
| | | efm Enable or disable link OAM EFM for Ethernet port
| | | | loopback Define loopback
| | | | snmp-tunneling Define SNMP tunneling for OAM EFM
| | | egress-mtu Define the maximum transmission unit (MTU)
| | | flow-control Flow control
| | | l2cp Assign L2CP profile to Ethernet port
| | | loopback This command puts the specified port into a

loopback mode. The no form of the command
disables the specified type of lookback.
| | | max-capability Configure maximum capability advertising
| | | name Define port name
| | | pm-collection Enable/disable PM collection
| | | queue-group Define queue group profile for port
| | | shutdown This command administratively disables a port. The

no form of this command administratively enables
a port.
| | | speed-duplex This command configures the speed and duplex of

an Ethernet port when autonegotiation is disabled.

Command Description
| | | tag-ethernet-type This command specifies the Ethertype expected in

Ethernet packet
| | | functional-mode Determine if second network port works in user

mode or network. If in network then redundancy is
available
| | | show loopback Display loopback status
| | | show oam-efm Display OAM EFM status
| | | show oam-efm-statistics Display OAM EFM statistics
| | | show statistics Display Ethernet port statistics
| | | show status Display Ethernet port status
| | l2cp-profile Define L2CP profile
| | | mac Define MAC address L2CP action
| | lag Configure LAG
| | | admin-key Define LAG capability
| | | bind Bind a port to the LAG
| | | distribution-method Define the distribution method
| | | shutdown Activate or deactivate the LAG
| | | show bind Display statistics for the LAG members
| | | show status Display the status of the LAG members
| | svi Configure service virtual interface
| | | name Define the name to the SVI port
| | | shutdown Activate or deactivate the SVI port
| | show summary Display the status of all Ethernet ports
| protection Enter protection level
| | erp Configure Ethernet Ring Protection
| | | backward-compatibility Make the ring compatible with previous ERP

implementations
| | | bridge Configure the bridge for the ring ports
| | | clear Clear the existing switch commands
| | | clear-statistics Clear ERP statistics
| | | data-vlan Assign VLAN ID for the data single
| | | east-port Define bridge port as an East port of ERP node
| | | force-switch Block the East or West port of a ring node
| | | manual-switch Block the East or West port of a ring node
| | | port-type Define node port type in relation to RPL owner

Command Description
| | | r-aps Configure dedicated VLAN for R-APS messages
| | | revertive Configure the revertive mode
| | | shutdown Activate or deactivate ERP
| | | timers Define guard and hold-off periods
| | | wait-to-restore Define Wait to Restore Timer
| | | west-port Define bridge port as a West port of ERP node
| | | show statistics Displaying ERP statistics
| | | show status Displaying ERP status
| qos Enter quality of service level
| | cos-map-profile Configure profile for mapping user priority to

internal cos
| | | map Define the mapping from user priority to internal

cos
| | policer-profile Configure a policer profile
| | | bandwidth Define the bandwidth for the policer profile
| | | compensation Define how many bytes to compensate for layer 1

overhead
| | queue-block-profile Configure queue block profile
| | | queue Define queue
| | | | depth Define the queue length
| | | | scheduling Define the queue scheduling method
| | | | shaper Define the shaper profile for the queue
| | queue-group-profile Configure queue group profile
| | | queue-block Configure queue block
| | | | name Define the name of the queue block
| | | | profile Define the queue block profile for the queue block
| | | | shaper Define the shaper profile for the queue block
| | queue-map-profile Configure queue map profile
| | | map Map the user priorities to queue IDs
| | shaper-profile Configure shaper profile
| | | bandwidth Define the bandwidth for the shaper profile
| reporting
| | acknowledge Acknowledge alarms
| | active-alarm-rebuild Rebuild active alarm database
| | alarm-input Configure alarm input

Command Description
| | alarm-source-attribute Configure alarm/event severity and masking per

source
| | alarm-source-type-attribute Configure alarm/event severity and masking per

source type
| | clear-alarm-log Clear alarms from log file(s)
| | mask-minimum-severity Configure alarm masking per severity
| | pm Globally enable PM collection
| | pm-collection Enable PM collection on entity type
| | show active-alarms Display active alarms, optionally according to

specified criteria
| | show active-alarms-details Display active alarms with details, optionally

according to specified criteria
| | show alarm-information Display information on specified alarm and source

type
| | show alarm-input Display information on alarm inputs
| | show alarm-list Display list of supported alarms, optionally for

specified source/severity
| | show alarm-log Display alarms in alarm and event history log,

optionally according to specified criteria
| | show brief-alarm-log Display alarms in brief alarm and event history log,
optionally according to specified criteria
| | show brief-log Display brief alarm and event history log, optionally
| | show event-information Display information on specified event and source

type
| | show event-list Display list of supported events
| | show log Display alarm and event history log, optionally

| router Configure router parameters
| | clear-arp-table Delete dynamic arp entities
| | dhcp-client Configure DHCP client for the router interface
| | | host-name Configure host name
| | | vendor-class-id Configure vendor class identifier
| | interface Configure the router interface
| | | address Configure the IP address for the router interface
| | | bind Bind the router interface to the logical port
| | | dhcp Enables/disables DHCP client

Command Description
| | | dhcp-client Configure DHCP client for the router interface
| | | | client-id Define DHCP client identifier type
| | | management-access Configure interface managment access
| | | mtu Configure the maximum transmit unit allowed
| | | name Configure the router interface name
| | | shutdown Activate or deactivate the router interface
| | | show status Display the router interface status
| | name Configure the router name
| | static-route Configure the static route entities
| | show arp-table Display the router ARP table
| | show interface-table Display the interface table
| | show routing-table Display the routing table
| system Configure system parameters
| | clear-cpu-utilization Clear CPU utilization counters
| | contact Configure contact person
| | date-and-time Configure date and time parameters
| | | date-format Configure system date format
| | | date Configure system date
| | | sntp Configure Simple Network Time Protocol

parameters
| | | | broadcast Enable/disable broadcast client mode for SNTP
| | | | poll-interval Configure SNTP polling interval
| | | | server Configure SNTP server
| | | | | address Configure SNTP server IP address
| | | | | prefer Set/Reset the SNTP server Preference
| | | | | query-server Query the timestamp from the SNTP Server
| | | | | shutdown Enable/Disable SNTP Server
| | | | | udp UDP Port of SNTP Server
| | | | show status Display SNTP Servers Status
| | | time Configure system time
| | | zone Configure time zone and offset
| | interval-duration
| | inventory Configure inventory entity
| | | alias Configure inventory entity alias

Command Description
| | | asset-id Configure inventory entity asset ID
| | | serial-number Configure inventory entity serial number
| | | show status Display inventory entity status
| | location Configure location of device
| | name Configure name of device
| | syslog Configure syslog entities
| | | address Configure target address of syslog server
| | | clear-statistics Clear the Syslog statistics
| | | facility Configure facility of device
| | | port Configure UDP port number
| | | severity-level Configure severity level of device
| | | shutdown Enable/disable logging of syslog entity
| | | show statistics Display syslog statistics
| | show buffers Display memory buffer usage
| | show cpu-utilization Show the CPU utilization
| | show date-and-time Display date and time
| | show device-information Display device information
| | show summary-inventory Display inventory information
| terminal Configure control port parameters
| | baud-rate Define control port data rate
| | length Define number of rows to display

Command Description
| | timeout Define security timeout
Table 4-3. Commands in the file Category
Command Description
file Enter file level
| delete Delete a file from the device
| dir Display files in base directory
| show configuration-files Display configuration file properties
| show copy Display the copy files
| show factory-default-config Display factory-default-config file content
| show rollback-config Display rollback-config file content
| show startup-config Display startup-config file content
| show sw-pack Display the existing sw-packs
| show user-default-config Display user-default-config file content
Table 4-4. Commands in the admin category
Command Description
admin Administrative commands
| factory-default-all Reset all configuration and counters
| factory-default Reset the device to factory defaults
| reboot Restart the device
| software Software installed vectors
| | install Instructs the device to run from another sw-pack

(upgrade)
| | software-confirm-required Configure user confirmation requirement after

reboot
| | undo-install Abort the upgrade process the return to previous

sw-pack (downgrade)
| | show status Display the status of the upgrade process
| startup-confirm-required Require startup-config confirmation after next

reboot
| user-default Reset the device to user defaults

Table 4-5. Commands in the global-commands Category
Command Description
global-commands Global commands can be typed at any level
| copy Copies files within device or uploads/downloads files

to/from remote locations
| echo Echo the text that is typed in
| exec Execute a file, optionally echoing the commands
| exit Return to previous level in the commands hierarchy
| help Displays general help, or optionally just the hotkeys

and/or global commands
| history Displays the command history for the current

session (by default the history contains the last 10
commands)
| info Displays information on the current configuration
| level-info Displays information on the current level

configuration
| logout Log out this system
| ping Verify the reachability of a remote host
| save Save user configuration
| trace-route Determine the route to a destination address
| tree Displays all lower command levels and commands

accessible from the current context level, optionally
with parameter information
4.3 Working with Telnet and SSH

The Telnet host is typically a PC or Unix station with the appropriate suite of
TCP/IP protocols.
To enable the Telnet host to communicate with ETX-1, the ETX-1 IP address
settings must be configured (refer to Router section in Chapter 8 for details).
This is usually done via a terminal emulation program (see Working with
Terminal). After this preliminary configuration, you can use a Telnet host
connected directly or via a local area network.
To connect to ETX-1 via Telnet:

1. At the Telnet host, enter the appropriate command (e.g. at a PC enter:
telnet <IP-address>).
The Telnet login window appears for the device:
ETX-1 Ver. 1.2 Working with Telnet and SSH 4-23

Figure 4-9. Telnet Connection to Unit
2. Log into the device as explained in Login. Refer to Using the CLI and
Command Tree for details on using the CLI commands.
4.4 Working with RADview

RADview-EMS is a user-friendly and powerful SNMP-based element management
system.
RADview-EMS provides a dedicated graphical user interface (GUI) for monitoring
RAD products via their SNMP agents. RADview agent for ETX-1 is bundled in the
RADview-EMS package for PC (Windows-based) or Unix.
For more details about this network management software, and for detailed
instructions on how to install, set-up and use RADview contact your local
distributor or refer to the RADview-EMS documentation.
4.5 Working with SNMP

ETX-1 can be integrated into third-party network management systems in the
following ways:
Viewing device inventory and receiving traps (see Chapter 11 for trap list)
4-24 Working with SNMP ETX-1 Ver. 1.2

Managing device, including configuration, statistics collection, and

diagnostics, using the following standard and private MIBs:
CFM MIB (IEEE8021-CFM-MIB)
IANAifType-MIB
IETF Syslog Device MIB
IEEE8023-LAG-MIB
MEF-R MIB
RAD private MIB
RFC 2819 (RMON-MIB)
RFC 2863 (IF-MIB)
RFC 3273 (Remote Network Monitoring MIB)
RFC 3411 (SNMP-FRAMEWORK-MIB)
RFC 3413 (SNMP-TARGET-MIB)
RFC 3414 (SNMP-USER-BASED-SM-MIB)
RFC 3415 (SNMP-VIEW-BASED-ACM-MIB)
RFC 3418 (SNMPv2-MIB)
RFC 3433 (ENTITY-SENSOR-MIB)
RFC 3636 (MAU-MIB)
RFC 4133 (ENTITY-MIB)
RFC 4668 (RADIUS-AUTH-CLIENT-MIB)
RFC 4836.MIB (MAU-MIB)
RFC 4878.MIB (DOT3-OAM-MIB).
4.6 Configuring Device Information

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

1. Navigate to configure system.
The config>system# prompt is displayed.
2. Enter the necessary commands according to the tasks listed below.
Task Command Comments
Assigning device name name <name-of-device> The name of the device (up to 255 characters,
case-sensitive)
ETX-1 Ver. 1.2 Configuring Device Information 4-25

Specifying location location < location-of- The location of the device (up to 255 characters,
device> case-sensitive)
Specifying contact person contact The name of the contact persion (up to 255
<contact-person> characters, case-sensitive)
Displaying device show device-information

information, MAC address, [refresh [<sec>]]
and amount of time device
has been running
Displaying Device Information

To display device information:
Device name ETX-1
Location floor-8
Contact Engineer-1.
ETX-1# configure system
ETX-1>config>system# name ETX-1
ETX-1>config>system# location floor-8
ETX-1>config>system# contact Engineer-1
ETX-1>config>system# show device-information
Description : Ethernet Demarcation Switch; Sw: 1.2.0(0.34); Hw: 2.0A(2.0);

Name : ETX-1
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-50-1A-13
Engine Time : 02:12:44
4.7 Configuring SNMP Management

SNMP stands for Simple Network Management Protocol. it is an application layer
protocol that provides a message format for communication between managers
and agents.
ETX-1 supports SNMPv3, the latest SNMP version. SNMPv3 provides secure access
to devices in the network by using authentication and data encryption.
Standards
The supported SNMP versions are based on the following standards:
RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working
Group.
RFC 1902, Structure of Management Information for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group.
4-26 Configuring SNMP Management ETX-1 Ver. 1.2

RFC 1903, Textual Conventions for Version 2 of the Simple Network

Management Protocol (SNMPv2). SNMPv2 Working Group.
RFC 1904, Conformance Statements for Version 2 of the Simple Network
RFC 1905, Protocol Operations for Version 2 of the Simple Network
RFC 1906, Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2).
RFC 1907, Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group.
RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework. SNMPv2 Working Group.
RFC 2104, Keyed Hashing for Message Authentication.
RFC 2271, Architecture for Describing SNMP Management Frameworks.
RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP).
RFC 2273, SNMPv3 Applications.
RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3).
RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP).
RFC 3412, Version 3 Message Processing and Dispatching.
RFC 3414, User-based Security Model for SNMPv3
RFC 3416, Update for RFC 1904.
Benefits
The SNMP protocol allows you to remotely manage multiple units from a central
workstation using a network management system.
The SNMPv3 protocol allows data to be collected securely from SNMP devices.
Confidential information such as SNMP commands can thus be encrypted to
prevent unauthorized parties from accessing them.
Functional Description
In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which sends reports via SNMP to the managing
workstations.
Factory Defaults
The following is the default configuration of the SNMP parameters (refer to
Setting SNMP Parameters for explanations of the parameters):
ETX-1 Ver. 1.2 Configuring SNMP Management 4-27

SNMP engine ID set to device MAC address

User named "initial", with security level no authentication
Group for SNMPv3 named "initial":
Security levels: no authentication and no privacy, authentication and no
privacy, authentication and privacy
User: initial
Views for read/write/notify: "internet".
Group for SNMPv1 named v1_read:
Security level: no authentication and no privacy
Read view = internet
Write view =
Notify view = internet
Group for SNMPv1 named v1_trap:
Read view =
Write view =
Group for SNMPv1 named v1_write:
Write view = internet
Group for SNMPv2 named v2_read:
Write view =
Group for SNMPv2 named v2_trap:
Read view =
Write view =
Group for SNMPv2 named v2_write:
Write view = internet


Security group for SNMPv1 named v1_read:
Group name = v1_read
Security group for SNMPv1 named v1_trap:
Group name = v1_trap
Security group for SNMPv1 named v1_write:
Group name = v1_write
Security group for SNMPv2 named v2_read:
Group name = v2_read
Security group for SNMPv2 named v2_trap:
Group name = v2_trap
Security group for SNMPv2 named v2_write:
Group name = v2_write
Security group for SNMPv3 named initial
Group name = initial
Notifications with tag unmasked for the device traps
Setting SNMP Parameters

ETX-1 supports SNMP version 3, providing secure SNMP access to the device by
authenticating and encrypting packets transmitted over the network.
The ETX-1 default configuration provides one standard user named initial with
no encryption and the lowest security level (refer to Factory Defaults for details).
to configure SNMPv3:
1. Set SNMP engine ID if necessary
2. Add users, specifying authentication protocol and privacy protocol
3. Add groups, specifying security level, protocol and view
4. Connect users to groups
5. Add notification entries with assigned traps and tags
6. Configure target parameter sets to be used for targets
7. Configure targets (SNMPv3 network management stations to which ETX-1
should send trap notifications), specifying target parameter sets and
notification tags, and trap synchronization groups if applicable
To configure SNMPv3 parameters:
1. Navigate to configure management snmp.
The config>mngmnt>snmp# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.

Note When you enter password parameters, they should contain at least eight
characters.
Task Command Level Comments
Setting SNMP snmp-engine-id mac [<mac-address>] snmp If you use the mac option
engine ID, as MAC snmp-engine-id ipv4 [<ip-address>] and do not specify the MAC
address or IP address, the SNMP engine ID
snmp-engine-id text <string>
address or string is set to the device MAC
address.
If you use the ipv4 option
and do not specify the IP
address, the SNMP engine ID
is set to the device IP
address.
Configuring user user <security-name> snmp To create a user with no

[md5-auth [{des | aes128 | none}] ] authentication, specify
user <security-name> none-auth.
[sha-auth [{des | aes128 | none}] ] no user <security-name>
user <security-name> [none-auth] deletes the user.
Setting user authentication [ password <password> ] snmp>user no authentication disables

authentication [ key <key-change> ] authentication protocol.
password and
optional key for
changes
Setting user privacy privacy [ password <password> ] snmp>user no privacy disables privacy
password and [ key <key-change> ] protocol.
optional key for
changes
Administratively no shutdown snmp>user You must define the

enabling user authentication and
privacy method before
you can enable the user,
unless the user was
defined with no
authentication
(none-auth)
shutdown disables the
user.
Configuring group access-group <group-name> {snmpv1 | snmp no access-group <group-

snmpv2c | usm} name>
{no-auth-no-priv | auth-no-priv | auth-priv} {snmpv1|snmpv2c|usm} {no-
auth-no-priv| auth-no-
priv|auth-priv} deletes the
group

Defining how to context-match {exact | prefix} snmp>access-group exact Match the entire
match the context context
sent in frames by prefix Match the first part
the NMS of the context.
Note: ETX-1 automatically
identifies the NMS context,
therefore you can configure
exact match. prefix is
typically used for devices
with multiple instances.
Setting read view of read-view <name> snmp>access-group
group
Setting write view write-view <name> snmp> access-group

of group
Setting notify view notify-view <name> snmp> access-group

of group
Administratively no shutdown snmp> access-group shutdown disables the

enabling group group.
Configuring community <community-index> snmp

community
Configuring name name <community-string> snmp>community
Configuring security sec-name <sec-name> snmp>community

name
Configuring tag <transport-tag> snmp>community This should normally be left

transport tag set to the default value.
Administratively no shutdown snmp>community shutdown disables

enabling community community.
Configuring notify <notify-name> snmp no notify <notify-name>

notification cancels the notification
configuration.
Assigning trap to bind {trap-list} snmp>notify You can assign more than
notification one trap to a notification, in
separate commands.
Assigning tag to tag <argument> snmp>notify

notification, to be
used to identify the
notification entry
when configuring
target
Administratively no shutdown snmp>notify

enabling
notification

Configuring notify-filter <name> <sub-tree-oid> snmp name Name of filter.

notification filter to sub-tree-oid OID that
define access to a defines the MIB subtree.
particular part of
the MIB hierarchy
for trap variables
Specifying the part mask [<mask>] snmp>notify-filter The mask is comprised of

of the subtree OID binary digits (for example,
to use in order to the mask 1.1.1 converts OID
define the MIB 1.3.6.7.8 to 1.3.6). It is not
subtree necessary to specify a mask
if sub-tree-oid is the OID
that should be used to
define the MIB subtree.
Defining whether type {included | excluded} snmp>notify-filter included Traps with

traps with trap trap variables belonging
variables belonging to the MIB subtree are
to the MIB subtree sent.
are sent excluded Traps with
trap variables belonging
to the MIB subtree are
not sent.
Administratively no shutdown snmp>notify-filter

enabling
notification filter
Configuring notify-filter-profile <params-name> snmp params-name Specifies

notification filter the target parameter set to
profile associate with the profile
Configuring profile-name <argument> snmp>filter-profile argument Specifies

notification filter notification filter to
profile name associate with the profile
Administratively no shutdown snmp>filter-profile

enabling
notification filter
profile
Connecting security security-to-group {snmpv1 | snmpv2c | usm} snmp When using no security-to-
name to group (e.g. sec-name <security-name> group
connecting user or {snmpv1|snmpv2c|usm} sec-
community to name <security-name>
group) removes security-to-group
entity, group name should
be set before set to no
shutdown.
Specifying group to group-name <group-name> snmp>security-to-group

which to connect
security name

Administratively no shutdown snmp>security-to-group shutdown disables the

enabling security-to-group entity.
security-to-group
entity
Configuring set of target-params <name> snmp no target-params <name>

target parameters removes target parameters.
Specifying message message-processing-model snmp>target-params

processing model {snmpv1 | snmpv2c | snmpv3}
(SNMP version) to
be used when
generating SNMP
messages for the
set of target
parameters
Specifying SNMP version { snmpv1 | snmpv2c | usm} snmp> target-params usm for SNMPv3 version.
version to be used
when generating
SNMP messages for
the set of target
parameters
Specifying user on security [name <security-name>] snmp> target-params

whose behalf SNMP [level {no-auth-no-priv | auth-no-priv
messages are to be | auth-priv}]
generated for the
set of target
parameters
Administratively no shutdown snmp> target-params shutdown disables target

enabling target parameters.
parameters
Configuring target target <name> snmp no target <name> removes

target .
Specifying set of target-params <params-name> snmp>target

target parameters
for target
Assigning tag(s) to tag-list <list> snmp>target If you specify more than one
target tag, the space-separated list
is enclosed within double
quotes.
Specifying target address udp-domain <ip-address> snmp>target

address as IP address oam-domain <oam-port>
address or OAM
port

Specifying trap trap-sync-group <group-id> [import-trap- snmp>target If the group does not
synchronization masking] exist, it is created.
group If you specify the
import-trap-masking
parameter, the
managers trap masking
is imported from the first
manager in the group.
Enter no trap-sync-group
to remove the manager
from the group. If the
manager was the last in
the group, the group is
deleted.
Administratively no shutdown snmp>target shutdown disables target.

enabling target
Configuring target trap-sync-group <group-id> snmp The trap synchronization

parameters and group must be previously
tags for trap defined in the target level.
synchronization
group
Specifying tags (the tag-list <list> snmp>trap-sync-group To remove the tag list, enter
tag(s) must be no tag-list.
defined in
notification entries)
Specifying set of target-params <params-name> snmp>trap-sync-group

target parameters
Defining access to a view <view-name> <sub-tree-oid> snmp view-name Name of view,

particular part of which can be associated to a
the MIB hierarchy group as a notify, read, or
write view.
sub-tree-oid OID that
defines the MIB subtree (for
example 1.3.6.1 represents
the Internet hierarchy).
Specifying the part mask <mask> snmp>view The mask is comprised of

of the subtree OID binary digits (for example,
to use in order to the mask 1.1.1 converts OID
define the MIB 1.3.6.7.8 to 1.3.6). It is not
subtree necessary to specify a mask
if sub-tree-oid is the OID
that should be used to
define the MIB subtree.

Defining whether type {included | excluded} snmp>view included Allow access to

access to the MIB the subtree.
subtree is allowed excluded Dont allow
access to the subtree.
Administratively no shutdown snmp>view

enabling view
Displaying trap show trap-sync [refresh [<sec>]] snmp

synchronization
groups and
members for
SNMPv3 manager
groups
Displaying SNMPv3 show snmpv3 information [refresh [<sec>]] snmp

information, such
as the number of
times the SNMPv3
engine has booted,
and how long since
the last boot
Example
To create SNMPv3 user and connect it to group:
User named MD5_priv:
Security level MD5 authentication, DES privacy
Group named "SecureGroup":
All security levels
Contains set of views named "internet" (from default configuration).

ETX-1# configure management snmp

ETX-1>config>mngmnt>snmp# user MD5_priv md5-auth des
ETX-1>config>mngmnt>snmp>user(MD5_priv)$ privacy password MD543210
ETX-1>config>mngmnt>snmp>user(MD5_priv)$ authentication password MD543210
ETX-1>config>mngmnt>snmp>user(MD5_priv)$ no shutdown
ETX-1>config>mngmnt>snmp>user(MD5_priv)$ exit
ETX-1>config>mngmnt>snmp# access-group SecureGroup usm no-auth-no-priv
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ context-match exact
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ read-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ write-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ notify-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ no shutdown
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/no-auth-no-priv)$ exit
ETX-1>config>mngmnt>snmp# access-group SecureGroup usm auth-no-priv
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ context-match exact
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ read-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ write-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ notify-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ no shutdown
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-no-priv)$ exit
ETX-1>config>mngmnt>snmp# access-group SecureGroup usm auth-priv
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ context-match exact
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ read-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ write-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ notify-view internet
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ no shutdown
ETX-1>config>mngmnt>snmp>access-group(SecureGroup/usm/auth-priv)$ exit
ETX-1>config>mngmnt>snmp# security-to-group usm sec-name MD5_priv
ETX-1>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ group-name SecureGroup
ETX-1>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ no shutdown
ETX-1>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ exit
ETX-1>config>mngmnt>snmp#
To create notifications:
Notification named TrapPort:
Tag = Port
Bound to ethLos, sfpRemoved.
Notification named TrapPower:
Tag = Power
Bound to powerDeliveryFailure, systemDeviceStartup.


ETX-1>config>mngmnt>snmp# notify TrapPort
ETX-1>config>mngmnt>snmp>notify(TrapPort)$ tag Port
ETX-1>config>mngmnt>snmp>notify(TrapPort)$ bind ethLos
ETX-1>config>mngmnt>snmp>notify(TrapPort)$ bind sfpRemoved
ETX-1>config>mngmnt>snmp>notify(TrapPort)$ no shutdown
ETX-1>config>mngmnt>snmp>notify(TrapPort)$ exit
ETX-1>config>mngmnt>snmp# notify TrapPower
ETX-1>config>mngmnt>snmp>notify(TrapPower)$ tag Power
ETX-1>config>mngmnt>snmp>notify(TrapPower)$ bind powerDeliveryFailure
ETX-1>config>mngmnt>snmp>notify(TrapPower)$ bind systemDeviceStartup
ETX-1>config>mngmnt>snmp>notify(TrapPower)$ no shutdown
ETX-1>config>mngmnt>snmp>notify(TrapPower)$ exit
To create target parameters and target:

Target parameters named TargParam1:
Message processing model SNMPv3
version USM
User MD5_priv
Security level authentication and privacy
Target named TargNMS1:
Target parameters TargParam1
Tag list = Port, Power
IP address 192.5.4.3.
ETX-1>config>mngmnt>snmp# target-params TargParam1
ETX-1>config>mngmnt>snmp>target-params(TargParam1)$ message-processing-model
snmpv3
ETX-1>config>mngmnt>snmp>target-params(TargParam1)$ version usm
ETX-1>config>mngmnt>snmp>target-params(TargParam1)$ security name MD5_priv
level auth-priv
ETX-1>config>mngmnt>snmp>target-params(TargParam1)$ no shutdown
ETX-1>config>mngmnt>snmp>target-params(TargParam1)$ exit
ETX-1>config>mngmnt>snmp# target TargNMS1
ETX-1>config>mngmnt>snmp>target(TargNMS1)$ target-params TargParam1
ETX-1>config>mngmnt>snmp>target(TargNMS1)$ tag-list Port Power
ETX-1>config>mngmnt>snmp>target(TargNMS1)$ address udp-domain 192.5.4.3
ETX-1>config>mngmnt>snmp>target(TargNMS1)$ no shutdown
ETX-1>config>mngmnt>snmp>target(TargNMS1)$ exit
To create communities, target parameters, and target for devices in network that
are working with SNMPv2c :
Community read:
Name: public
Security name: v2_read (defined in default configuration)

Community write:
Name: private
Security name: v2_write (defined in default configuration)
Community trap:
Name: public
Security name: v2_trap (defined in default configuration)
Target parameters named snmpv2:
Message processing model SNMPv2c
Version SNMPv2c
Security name: v2_write
Security: level no authentication and no privacy
Target named NMSsnmpv1:
Target parameters snmpv2
Tag list = unmasked
IP address 192.5.6.7.


ETX-1>config>mngmnt>snmp# community read
ETX-1>config>mngmnt>snmp>community(read)$ name public
ETX-1>config>mngmnt>snmp>community(read)$ sec-name v2_read
ETX-1>config>mngmnt>snmp>community(read)$ no shutdown
ETX-1>config>mngmnt>snmp>community(read)$ exit
ETX-1>config>mngmnt>snmp# community write
ETX-1>config>mngmnt>snmp>community(write)$ name private
ETX-1>config>mngmnt>snmp>community(write)$ sec-name v2_write
ETX-1>config>mngmnt>snmp>community(write)$ no shutdown
ETX-1>config>mngmnt>snmp>community(write)$ exit
ETX-1>config>mngmnt>snmp# community trap
ETX-1>config>mngmnt>snmp>community(trap)$ name public
ETX-1>config>mngmnt>snmp>community(trap)$ sec-name v2_trap
ETX-1>config>mngmnt>snmp>community(trap)$ no shutdown
ETX-1>config>mngmnt>snmp>community(trap)$ exit
ETX-1>config>mngmnt>snmp# target-params snmpv2
ETX-1>config>mngmnt>snmp>target-params(snmpv2)$ message-processing-model
snmpv2c
ETX-1>config>mngmnt>snmp>target-params(snmpv2)$ version snmpv2c
ETX-1>config>mngmnt>snmp>target-params(snmpv2)$ security name v2_write level
no-auth-no-priv
ETX-1>config>mngmnt>snmp>target-params(snmpv2) no shutdown
ETX-1>config>mngmnt>snmp>target-params(snmpv2) exit
ETX-1>config>mngmnt>snmp# target snmp
ETX-1>config>mngmnt>snmp>target(snmp)$ target-params snmpv2
ETX-1>config>mngmnt>snmp>target(snmp)$ tag-list unmasked
ETX-1>config>mngmnt>snmp>target(snmp)$ address udp-domain 192.5.6.7
ETX-1>config>mngmnt>snmp>target(snmp)$ no shutdown
ETX-1>config>mngmnt>snmp>target(snmp)$ exit
ETX-1>config>mngmnt>snmp#To display SNMPv3 information:

ETX-1> config>mngmnt>snmp# show snmpv3 information
SNMPv3 : enable
Boots : 5
Boots Time (sec) : 84787
EngineID : 800000a401c0a863ef
To configure trap synchronization:

Trap synchronization group 1:
Members NMS1 and NMS2
Target parameters TargParam1 (from previous example)
Tag list = Port, Power (from previous example)
Trap synchronization group 2:
Members NMS3 and NMS4.


ETX-1>config>mngmnt>snmp# target NMS1
ETX-1>config>mngmnt>snmp>target(NMS1)$ trap-sync-group 1
ETX-1>config>mngmnt>snmp>target(NMS1)$ exit
ETX-1>config>mngmnt>snmp# trap-sync-group 1
ETX-1>config>mngmnt>snmp>trap-sync-group(1)# tag-list [Port,Power]
ETX-1>config>mngmnt>snmp>trap-sync-group(1)# target-params TargParam1
ETX-1>config>mngmnt>snmp>trap-sync-group(1)# exit
ETX-1>config>mngmnt>snmp# show trap-sync
Group ID Member
-----------------------------------------------------------------------------
1 NMS1
1 NMS2
2 NMS3
2 NMS4
4.8 Controlling Management Access

You can enable or disable access to the ETX-1 management system via Telnet, SSH,
or SNMP applications. By disabling Telnet, SSH, or SNMP, you prevent unauthorized
access to the system when security of the ETX-1 IP address has been
compromised. When Telnet, SSH, and SNMP are disabled, ETX-1 can be managed
via an ASCII terminal only. Additionally, you can enable or disable access via
SFTP/TFTP.
Factory Defaults
By default, access is enabled for all the applications.
Setting Management Access Parameters

To set management access:
At the configure management access prompt enter the necessary commands
according to the tasks listed below.
Allowing Telnet access telnet Typing no telnet blocks

access by Telnet
4-40 Controlling Management Access ETX-1 Ver. 1.2

Allowing SSH (Secure Shell) access ssh Typing no ssh blocks

access by SSH
Allowing SNMP access snmp Typing no snmp blocks

access by SNMP
Allowing SFTP access sftp Typing no sftp blocks

access by SFTP
Allowing TFTP access tftp Typing no tftp blocks

access by TFTP
4.9 Defining Access Policy

The access policy allows specifying up to three user authentication methods
(local, RADIUS, TACACS+). If an authentication method is not available or the user
is not found, the next method is used if applicable.
Factory Defaults
By default, authentication is via the locally stored database (1st-level local)
Configuring Access Policy

To define the access policy:
At the config>mngmnt>access# prompt, enter the necessary commands
according to the tasks listed below.
Specifying authentication via locally auth-policy 1st-level local

stored database
Specifying authentication method auth-policy 1st-level radius [2nd-level If su (Superuser) does not exist
preferably via RADIUS, then optionally tacacs+ [3rd-level {local | none}]] in the RADIUS server database or
TACACS+, then optionally local the system loses the connection
to the RADIUS server, ETX-1
uses the local authentication
database to authenticate the
user, if 2nd-level is set to local
Specifying authentication method auth-policy 1st-level radius [2nd-level If su (Superuser) does not exist
preferably via Radius, then optionally {local | none}] in the Radius server database or
local the system loses the connection
to the Radius server, ETX-1 uses
the local authentication
database to authenticate the
user, if 2nd-level is set to local.
ETX-1 Ver. 1.2 Defining Access Policy 4-41

Specifying authentication method auth-policy 1st-level tacacs+ If su (Superuser) does not exist
preferably via TACACS+, then [2nd-level radius [3rd-level {local | in the TACACS+ and RADIUS
optionally RADIUS, then optionally none}]] server databases or the system
local loses the connection to the
TACACS+ and RADIUS servers,
ETX-1 uses the local
authentication database to
authenticate the user, if
2nd-level is set to local.
Specifying authentication method auth-policy 1st-level tacacs+ If su (Superuser) does not exist
preferably via TACACS+, then [2nd-level {local | none}] in the TACACS+ server database
optionally local or the system loses the
connection to the TACACS+
server, ETX-1 uses the local
authentication database to
authenticate the user, if
2nd-level is set to local.
4.10 Management Flows

ETX-1 management flow can be configured in two ways:
Devices using ERP and RSTP: management flow must be configured through
the bridge (bridge port 7)
Devices not using ERP and RSTP: management flow is configured through a
physical interface (ETH-1, ETH-2)
To configure management flows for ETX-1 not using ERP and RSTP:
1. Configure the Classifier Profiles:
ETX-1-SyncE# configure port svi 1
ETX-1-SyncE>config>port>svi(1)$ no shutdown
ETX-1-SyncE>config>port>svi(1)$ exit all
2. Create a profile that accepts untagged traffic:
ETX-1-SyncE# configure flows
ETX-1-SyncE>config>flows# classifier-profile untagged match-any
ETX-1-SyncE>config>flows>classifier-profile(untagged)$ match untagged
ETX-1-SyncE>config>flows>classifier-profile(untagged)$ exit
3. Create a profile that accepts only traffic tagged with mng VLAN (For example
management VLAN: 3079):
4-42 Management Flows ETX-1 Ver. 1.2

ETX-1-SyncE>config>flows# classifier-profile v3079 match-any

ETX-1-SyncE>config>flows>classifier-profile(v3079)$ match vlan 3079
ETX-1-SyncE>config>flows>classifier-profile(v3079)$ exit
ETX-1-SyncE>config>flows# flow mn_in
ETX-1-SyncE>config>flows>flow(mn_in)$ classifier v3079
ETX-1-SyncE>config>flows>flow(mn_in)$ no policer
ETX-1-SyncE>config>flows>flow(mn_in)$ ingress-port ethernet 1
ETX-1-SyncE>config>flows>flow(mn_in)$ egress-port svi 1 queue 0
ETX-1-SyncE>config>flows>flow(mn_in)$ vlan-tag pop vlan
ETX-1-SyncE>config>flows>flow(mn_in)$ no shutdown
ETX-1-SyncE>config>flows>flow(mn_in)$ exit
ETX-1-SyncE>config>flows# flow mn_out
ETX-1-SyncE>config>flows>flow(mn_out)$ classifier untagged
ETX-1-SyncE>config>flows>flow(mn_out)$ ingress-port svi 1
ETX-1-SyncE>config>flows>flow(mn_out)$ egress-port ethernet 1 queue 0 block
0/1
ETX-1-SyncE>config>flows>flow(mn_out)$ vlan-tag push vlan 3079 p-bit fixed 4
ETX-1-SyncE>config>flows>flow(mn_out)$ no shutdown
ETX-1-SyncE>config>flows>flow(mn_out)$ exit all
4. Configure the router:
ETX-1-SyncE# configure router 1
ETX-1-SyncE>config>router(1)# interface 1
ETX-1-SyncE>config>router(1)>interface(1)$ bind svi 1
ETX-1-SyncE>config>router(1)>interface(1)$ address <address for the
switch/subnet mask>
Example: (10.192.138.6/26)
ETX-1-SyncE>config>router(1)>interface(1)$ no shutdown
ETX-1-SyncE>config>router(1)>interface(1)$ exit
ETX-1-SyncE>config>router(1)# static-route 0.0.0.0/0 address <address of
default gateway>
Example: (10.192.138.62)
ETX-1-SyncE>config>router(1)# exit all
ETX-1-SyncE#save
*****running-config copied to startup-config successfully*****
*****4848 bytes copied in 1 secs (4848 bytes/sec)*****
To configure management flows for ETX-1 using ERP and RSTP:

1. Configure the SVI:
no shutdown
exit all
2. Configure the classification profile:
configure flows classifier-profile untagged match-any
match untagged
exit
classifier-profile v4 match-any
match vlan 4
exit all
3. Configure management flow:
ETX-1 Ver. 1.2 Management Flows 4-43

flow mn_in
classifier v4
ingress-port bridge-port 7
vlan-tag pop vlan
no shutdown
exit
flow mn_out
classifier untagged
ingress-port svi 1
egress-port bridge-port 7
vlan-tag push vlan 4 p-bit fixed 7
no shutdown
exit all
4. Configure the router:
configure router 1 interface 1
bind svi 1
address 192.168.100.142/24
no shutdown
exit all
4.11 Authenticating via RADIUS Server

RADIUS (Remote Authentication Dial-In User Service) is an AAA (authentication,
authorization and accounting) client/server protocol that secures networks
against unauthorized access. It is used to authenticate users and authorize their
access to the requested system or service. The RADIUS client communicates with
the RADIUS server using a defined authentication sequence.
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS)
RFC 2618, RADIUS Authentication Client MIB
Benefits
The RADIUS protocol allows centralized authentication and access control,
eliminating the need to maintain a local user data base on each device on the
network.
When a login attempt occurs at ETX-1, it submits an authentication request to
the RADIUS server. The RADIUS server checks the database and replies with either
Access Rejected or Access Accepted.
4-44 Authenticating via RADIUS Server ETX-1 Ver. 1.2

Factory Defaults
By default, four RADIUS servers are defined, they are configured as shown below.
Description Default Value
IP address of server 0.0.0.0
Max number of authentication attempts 3
Time interval between two authentication attempts 3 seconds
UDP port used for authentication 1812
Configuring RADIUS Parameters

ETX-1 provides connectivity to up to four RADIUS authentication servers. You
have to specify access parameters such as assigning Radius server IDs, specifying
the associated server IP addresses and the number of retries, etc.
To define RADIUS parameters:

1. At the config>mngmnt>radius# prompt, type server <server-id> to specify
which server to configure.
The config>mngmnt>radius>server(<server-id>)# prompt is displayed.
Assigning an IP address to the server address <ip-address> Possible IP addresses range from
1.1.1.1 to 255.255.255.255
Defining a non-disclosed string (shared key <string> [hash] The shared secret is a secret key
secret) used to encrypt the user consisting of free text known to
password. the client and the server for
encryption. It is hashed if
specified.
Defining the number of authentication retry <number-of-retries> Range 010

request attempts
Defining timeout (in seconds) for timeout <seconds> Range 15

response from RADIUS server
Defining the UDP port to be used for auth-port <udp-port-number> Range 165535
authentication
Administratively enabling server no shutdown shutdown administratively

disables the server.
Displaying status show status
Example
To define a RADIUS server:
Server IP address: 192.168.99.206
ETX-1 Ver. 1.2 Authenticating via RADIUS Server 4-45

Key: RAD_server1.
ETX-1# configure management radius
ETX-1>config>mngmnt>radius# server 1
ETX-1>config>mngmnt>radius>server(1)# address 192.168.99.206
ETX-1>config>mngmnt>radius>server(1)# key RAD_server1
ETX-1>config>mngmnt>radius>server(1)# no shutdown
ETX-1>config>mngmnt>radius>server(1)# information detail
address 192.168.99.206
key "574006ED9DDAD436E4915E482F2C7B09" hash
retry 3
timeout 3
auth-port 1812
no shutdown
Displaying RADIUS Statistics

To display RADIUS statistics:
At the config>mngmnt>radius# prompt, enter:
show statistics.
RADIUS statistics appear as shown below.
ETX-1>config>mngmnt>radius# show statistics
Server 1 Server 2 Server 3 Server 4
-----------------------------------------------------------------------------
Access Requests 0 0 0 0
Access Retransmits 0 0 0 0
Access Accepts 0 0 0 0
Access Rejects 0 0 0 0
Access Challenges 0 0 0 0
Malformed Response 0 0 0 0
Bad Authenticators 0 0 0 0
Pending Requests 0 0 0 0
Timeouts 0 0 0 0
Unknown Types 0 0 0 0
Packets Dropped 0 0 0 0
To clear the statistics for RADIUS:

clear-statistics
The RADIUS statistics are cleared.
Displaying RADIUS Status

To display RADIUS status:
show status.
RADIUS status appears as shown below.
4-46 Authenticating via RADIUS Server ETX-1 Ver. 1.2

ETX-1>config>mngmnt>radius# show status

Server IP Address Access Status
-----------------------------------------------------------------------------
1. 192.168.99.206 Enable Not connected
2. 0.0.0.0 Disable Not connected
4.12 Authenticating via TACACS+ Server

TACACS+ (Terminal Access Controller Access Control System Plus) is a security
application that provides access control for routers, network access servers, and
other networked computing devices via one or more centralized servers. TACACS+
provides separate authentication, authorization, and accounting services. It is
used to communicate between the switch and an authentication database. As
TACACS+ is based on TCP, implementations are typically resilient against packet
loss.
Standards
RFC 1492, An Access Control Protocol, Sometimes Called TACACS
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet but leaves a
standard TACACS+ header.
When a login attempt occurs at ETX-1, it submits an authentication request to
the TACACS+ server, which checks the database and then grants or refuses
access.
Factory Defaults
By default, no TACACS+ servers are defined. When a TACACS+ server is first
defined, it is configured as shown below.
The max number of authentication attempts. 1
Time interval between two authentication attempts. 5 seconds
Accounting TCP port 49
Authentication TCP port 49
ETX-1 Ver. 1.2 Authenticating via TACACS+ Server 4-47

Administratively enabled Disabled (shutdown)
Configuring TACACS+ Servers

ETX-1 provides connectivity to up to five TACACS+ authentication servers. You
must specify the associated server IP address, number of retries, etc.
Note If you intend to use TACACS+ for authentication, verify that TACACS+ is selected
as level-1 authentication method (see Defining Access Policy).
To define TACACS+ servers:

1. At the config>mngmnt>tacacsplus# prompt, type server <ip-address> to
specify the server IP address.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
Defining TCP port to be used for accounting-port <port-number> Range 165535

accounting
Defining TCP port to be used for authentication-port <port-number> Range 165535

authentication
Bind TACACS+ server to a group group <group-name> no group deletes the group.
Defining a non-disclosed string key <string> [hash] The shared secret is a secret key
(shared secret) used to encrypt the consisting of free text known to
user password the client and the server for
encryption. It is hashed if
specified.
Defining the number of authentication retry <number-of-retries> The value is 1 only

request attempts
Defining timeout (in seconds) for timeout <seconds> Range 110

response from TACACS+ server
Administratively enabling server no shutdown shutdown administratively

disables the server.
Clearing statistics clear-statistics
Displaying statistics show statistics
Example Defining Server

The example below illustrates the procedure for defining a TACACS+ server.
Server IP address: 192.168.99.208
Key: TAC_server1.
4-48 Authenticating via TACACS+ Server ETX-1 Ver. 1.2

ETX-1# configure management tacacsplus

ETX-1>config>mngmnt>tacacsplus# server 192.168.99.208
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)$ key TAC_server1
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)$ no shutdown
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)$ information detail
key "244055BF667B8F89E4915E482F2C7B09" hash
retry 1
timeout 5
authentication-port 49
accounting-port 49
no group
no shutdown
Example Displaying Statistics

To display statistics:
At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, enter:
show statistics.
RADIUS statistics appear as shown below.
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)$ show statistics
Requests 0
Request Timeouts 0
Unexpected Responses 0
Server Error Responses 0
Incorrect Responses 0
Transaction Successes 0
Transaction Failures 0
Pending Requests 0
Configuring Accounting Groups

To configure accounting groups:
1. At the config>mngmnt>tacacsplus# prompt, type group <group-name> to
configure an accounting group with the specified name.
The config>mngmnt>tacacsplus>group(<group-name>)# prompt is
displayed.
2. To define the accounting for the group, enter:
accounting [shell] [system] [commands]
Note You can enter any combination of shell, system, and commands, but you must
enter at least one of them.
3. Type exit to return to the TACACS+ level.

The config>mngmnt>tacacsplus# prompt is displayed.
4. Type server <ip-address> to select the TACACS+ server to which to bind the
group.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
ETX-1 Ver. 1.2 Authenticating via TACACS+ Server 4-49

5. At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, enter

group < group-name> to bind the previously defined accounting group to the
TACACS+ server.
Example Defining Accounting Group

The example below illustrates the procedure for defining an accounting group.
Group name: TAC1
Accounting: Shell, system, and commands
Bound to server defined in Example Defining Server.
ETX-1# configure management tacacsplus
ETX-1>config>mngmnt>tacacsplus# group TAC1
ETX-1>config>mngmnt>tacacsplus>group(TAC1)$ accounting shell system commands
ETX-1>config>mngmnt>tacacsplus>group(TAC1)$ info detail
accounting shell system commands
ETX-1>config>mngmnt>tacacsplus>group(TAC1)$ exit
ETX-1>config>mngmnt>tacacsplus# server 192.168.99.208
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)# group TAC1
ETX-1>config>mngmnt>tacacsplus>server(192.168.99.208)# info detail
key "244055BF667B8F89E4915E482F2C7B09" hash
retry 1
timeout 5
authentication-port 49
accounting-port 49
group "TAC1"
no shutdown
4.13 Configuring Terminal Control Port

You can configure the serial port parameters, which include specifying the data
rate, security timeout, and screen size from which you are accessing the device.
Factory Defaults
By default, data rate is set to 9,600 bps.
Setting Control Port Parameters

To define the control port parameters:
At the config>terminal# prompt, enter the necessary commands according to
the tasks listed below.
4-50 Configuring Terminal Control Port ETX-1 Ver. 1.2

Specifying the desired data rate baud-rate {300bps | 1200bps | The default data rate is 9,600
2400bps | 4800bps | 9600bps | bps.
19200bps | 38400bps | 57600bps |
115200bps}
Defining whether in case of timeout forever If you define a timeout, the

inactivity, device remains timeout limited <minutes> timeout value can be 160.
connected or disconnects after The default is 10 minutes.
a specified time period
Specifying the number of rows length <number-of-rows> The number of rows can be 0,
to display to indicate no limit on the
number of lines displayed. The
number of rows can be 0-255.
The default is 20.
4.14 Configuring User Access

ETX-1 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.
You can specify a users password as a text string or as a hashed value, which
you can obtain by using the info command to display user data.
Notes User passwords are stored in a database so that the system can perform
password verification when a user attempts to log in. To preserve
confidentiality of system passwords stored in text configuration files, the
password verification data is typically stored after a one-way hash function is
applied to the password, in combination with other data. When a user
attempts to log in by entering a password, the same function is applied to the
entered value and the result is compared with the stored value.
A cryptographic hash function is a deterministic procedure that takes an
arbitrary block of data and returns a fixed-size bit string, the (cryptographic)
hash value, such that any change to the data changes the hash value.
Factory Defaults
By default, the following users exist, with default password 1234:
su
tech
user
oper
ETX-1 Ver. 1.2 Configuring User Access 4-51

To add a new user:

1. Make sure that you are logged on as superuser (su).
2. Navigate to the Management context (config>mngmnt).
3. Define a new user:
user <name> [level {su | oper | tech | user}] [password <password> [hash]]
Example Defining Users

To define a new user:
User name = staff
User password = 1234.
ETX-1# configure management
ETX-1>config>mngmnt# user staff level su password 1234
# Password is encrypted successfully
ETX-1>config>mngmnt#
To add a new user with a hashed password:

1. Define a new user with a text password.
2. Use info detail to display the password hash value.
3. Define another user with the hashed password from the info output.
The second user can log in with the text password defined in step 1.
For example, to add the following users:
User name = staff1
User password = 4222
User name = staff2
User password = hash of 4222 (user staff2 can log in with password 4222).
ETX-1>config>mngmnt# user staff1 level user password 4222
# Password is encrypted successfully
ETX-1>config>mngmnt# info detail
user "staff1" level user password
"3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
ETX-1>config>mngmnt# user staff2 level user password

3fda26f8cff4123ddcad0c1bc89ed1e79977acef hash
ETX-1>config>mngmnt# info detail
4-52 Configuring User Access ETX-1 Ver. 1.2

ETX-1>config>mngmnt# logout
exiting cli
CLI session is closed
user>staff2
password>****
To delete an existing user:

At the Management context (config>mngmnt), enter no user <name>.
The specified user is deleted.
To view all connected users:

At the Management context (config>mngmnt), enter show users.
A list of all connected users is displayed, showing their access level, the
type of connection, and the IP address from which they are connected.
Example Displaying Users

ETX-1>config>mngmnt# show users
Num User Access Level Source IP Address
-----------------------------------------------------------------------------
1. su Su Terminal 0.0.0.0
ETX-1 Ver. 1.2 Configuring User Access 4-53

4-54 Configuring User Access ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 5 Services
Chapter 5
Services
ETX-1 provides flow-based and port-based services. This section shows the
configuration steps for both.
Note Flow mode is the default mode.
5.1 Ethernet Flow Mode

In Figure 5-1 the gray rectangles illustrate the data flow for Ethernet traffic. The
blue rounded rectangles indicate the functions that need to be configured,
numbered according to the sequence of configuration. Table 5-1 shows the
configuration steps in sequence.
Figure 5-1. Ethernet Flow Mode
Table 5-1. Ethernet Traffic Configuration
Sequence Step Commands Comments
1 Defining Classifier Profiles classifier-profile The classifier profile defines the

match criteria
2 Configuring Policer policer-profile Required only if you need to

Profiles bandwidth define non-default bandwidth
limits for the incoming traffic
3 Configuring Flows mark Required only if you need to
vlan define non-default configuration
for the mark
inner-vlan
p-bit
inner-p-bit
ETX--1 Ver. 1.2 Ethernet Flow Mode 5-1

Chapter 5 Services Installation and Operation Manual
4 Configuring Queue Block queue-block-profile Required only if you need to

Profile Parameters scheduling define non-default queue
configuration.
depth
For the network-to-user flow, it
supports 6 queue blocks.
For the user-to-network flow, it
supports 4 queue blocks.
5 Configuring Flows classifier You must define the flow for the
ingress-port user traffic.
egress-port
policer
mark
vlan-tag
shutdown
6 Configuring Shaper shaper-profile Required only if you need to
Profiles bandwidth define non-default bandwidth
limits for the outgoing traffic.
7 Ethernet Ports name Required only if you need to
auto-negotiation define non-default configuration
for the port.
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
5.2 Ethernet Bridge Mode
Bridge VLAN Queueing Egress

Shaping
port membership level 0 port
1) CoS mapping 3) VLAN 4) Queue group 5) Shaping 6) Ethernet port
2) Bridge port
Figure 5-2. Ethernet Bridge Mode

Table 5-2. Ethernet Bridge Configuration
1 CoS Mapping Profiles cos-map-profile Required only if you need to

define non-default cos mapping.
map
5-2 Ethernet Bridge Mode ETX--1 Ver. 1.2

Installation and Operation Manual Chapter 5 Services
2 Configuring the Bridge accept-frame-type Required only if you need to

define non-default bridge port.
ingress-filtering
name
pvid
cos-mapping
3 Configuring the Bridge name Required only if you need to

define non-default configuration
tagged-egress
for the VLAN.
untagged-egress
4 Queue Group Profiles queue-group-profile Required only if you need to

define non-default queue group
queue-block
configuration.
name
profile
shaper
5 Configuring Shaper shaper-profile Required only if you need to

Profiles define non-default bandwidth
bandwidth
limits for the outgoing traffic.
6 Ethernet Ports name Required only if you need to

define non-default configuration
auto-negotiation
for the port.
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
ETX--1 Ver. 1.2 Ethernet Bridge Mode 5-3

Chapter 5 Services Installation and Operation Manual
5-4 Ethernet Bridge Mode ETX--1 Ver. 1.2

Chapter 6
Ports
This chapter describes port-related features:
Ethernet Ports
Service Virtual Interface
6.1 Ethernet Ports

ETX-1 has up to two fiber optic or copper Fast Ethernet network ports and up to
four copper Fast Ethernet user ports.
The second network port can be configured as a user port. The following table
shows how to refer to the ports when configuring them with CLI commands.
Table 6-1. Ethernet Port Names
Port Port Number on Unit Port in CLI
Net 1 Ethernet 1
Net/User 2 Ethernet 2
User 3 Ethernet 3
User 4 Ethernet 4
User 5 Ethernet 5
User 6 Ethernet 6
MNG-ETH - Ethernet 101
The following parameters can be configured for the Ethernet ports:

Port name
Auto-negotiation
Maximum advertised capability for autonegotiation procedure (not relevant
for management Ethernet port)
Data rate and duplex mode, when autonegotiation is disabled
Administrative status
Flow control
Pm-collection (not relevant for management Ethernet port)
Network or user functional mode (second network interface only)
Tag Ethernet Type (not relevant for management Ethernet port)
ETX-1 Ver. 1.2 Ethernet Ports 6-1

Chapter 6 Ports Installation and Operation Manual
Egress MTU (not relevant for management Ethernet port)

Queue group profile (not relevant for management Ethernet port)
L2CP handling (not relevant for management Ethernet port)
Link OAM EFM (IEEE 802.3-2005) Refer to OAM EFM (not relevant for
management Ethernet port)
Loopback Refer to Testing Ethernet Ports (not relevant for management
Ethernet port)
Note ETX-1 supports SFP, but fiber optical interface needs to disable auto-negotiation
when using MiTop and MIRICI.
Configuring Ethernet Port Parameters

To configure the Ethernet port parameters:
1. Navigate to configure port ethernet <port> to select the Ethernet port to
configure.
The config>port>eth(<port>)# prompt is displayed.
Assigning description to port name <string> no name removes the name
Enabling autonegotiation auto-negotiation no auto-negotiation disables

autonegotiation
Setting maximum advertised capability max-capability {10-full-duplex | 10-full-duplex 10M full duplex
(highest traffic handling capability to 100-full-duplex | 1000-full-duplex} 100-full-duplex 100M full duplex
be advertised during the
1000-full-duplex 1000M full duplex
autonegotiation process)
Note: This parameter applies only if
autonegotiation is enabled.
Setting data rate and duplex mode of speed-duplex {10-full-duplex | 10-full-duplex 10M full duplex
the Ethernet port, when 100-full-duplex | 1000-full-duplex} 100-full-duplex 100M full duplex
autonegotiation is disabled
1000-full-duplex 1000M full duplex
Data flow control method based on flow-control no flow-control disables the data flow
Ethernet Pause frames. If the flow control.
control is enabled, ETX-1 received the
Pause frames sent by the peer device,
slowing its transmission rate.
Setting the VLAN tagged frame ETH II tag-ethernet-type <ether-type> Only network port can configure the value.
frame Ethertype (tag protocol The range is 0x0000-0xFFFF, the default is
identifier) 0x8100.
Setting the interval for performance pm-collection interval <seconds> no pm-collection disables PM data
monitoring data collection collection.
Note: Please enable the global PM function
before setting this command.
6-2 Ethernet Ports ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 6 Ports
Associating a queue group profile with queue-group profile You can associate a network port with a
the port <queue -profile-name> queue group profile containing one queue
block with up to 6 queues, but a user port
can be associated with a queue group
profile containing one queue block with up
to 4 queues.
Associating a Layer-2 control l2cp profile <l2cp-profile-name> If Ethernet port 2 is configured as a

processing profile with the port network port, then whenever you assign
an L2CP profile to one of the network
ports it is automatically assigned to the
other network port
If you intend to enable link OAM on the
port, the associated L2CP profile must
specify peer action for MAC 0x02
Setting maximum frame size to egress-mtu <size> The size is 64-9216

transmit (frames above the specified
size are discarded)
Setting port to function as network or functional-mode {network | user} Applicable to second network interface
user only
See Setting Second Network Interface as
Network or User Port for more
information
Administratively enabling port no shutdown shutdown disables the port
Setting Second Network Interface as Network or User Port

You can change the functional mode of the second network interface from
network to user port and vice versa.
Note When you change the functional mode, all flows related to the port are deleted.
The port must be administratively disabled before you can change the functional
mode.
To change the functional mode of the second network interface:

1. Navigate to configure port ethernet 2.
The config>port>eth(2)# prompt is displayed.
2. Type shutdown to administratively disable the port.
3. Enter the command to change the functional mode:
To change to user port, enter:
functional-mode user.
To change to network port, enter:
functional-mode network.
The functional mode of the port is changed.

To change the second network interface functional mode to user port, configure
the following:
ETX-1# configure port ethernet 2
ETX-1>config>port>eth(2)# shutdown
ETX-1>config>port>eth(2)# functional-mode user
ETX-1>config>port>eth(2)# no shutdown
Displaying Ethernet Port Status

You can display the following:
Summary information showing the status and speed of all Ethernet ports
Status and configuration of an individual Ethernet port.
To display the status of all Ethernet ports:

At the prompt config>port#, enter:
show summary.
The port status and speeds of the Ethernet ports are displayed. If a port
is being tested via the loopback command, it is indicated in the
operational status.
To display status of an Ethernet port:

At the prompt config>port>eth(<port-num>)#, enter:
show status.
The Ethernet port status parameters are displayed.
To display the status of all Ethernet ports:

ETX-1# configure port
ETX-1>config>port# show summary
Port Number Name Admin Oper Speed
-----------------------------------------------------------------------------
Ethernet 1 ETH 1 Up Down 1000000000
Ethernet 6 ETH 6 Up Testing 10000000
Ethernet 101 MNG-ETH Up Up 100000000
ETX-1>config>port#

To display the status of Ethernet port 1 with SFP:

ETX-1>config>port>eth(1)# show status
Name : ETH 1
Administrative Status : Up
Operation Status : Down
Connector Type : SFP In
Auto Negotiation : Complete
MAC Address : 00-20-D2-50-00-D6
SFP
-----------------------------------------------------------------------------
Connector Type : LC
Manufacturer Name : EOPTOLINK INC
Manufacturer part number : EOLS131210DRAD
Typical Maximum Range (Meter) : 10000
Wave Length (nm) : 1310 Laser
Fiber Type : SM
RX Power (dBm) : -36.9 dBm

TX Power (dBm) : -5.0 dBm
Laser Bias (mA) : 5.7 mA

Laser Temperature (Celsius) : 47.0 C
Power Supply (V) : 3.2 V
Testing Ethernet Ports

The physical layer runs at the PHY of the ports. When the loopback is active the
data forwarded to a port is looped from the Tx path to the Rx path.
The loopback can be one of the following types:
Local Loopback is closed towards the user interface (Figure 6-1)
Remote Loopback is closed towards the network interface (Figure 6-2).
Network User
Interface Interface
ETX-203A
ETX-36
Figure 6-1. Local Loopback

Network User
Interface Interface
ETX-203A
ETX-1
Figure 6-2. Remote Loopback
To run a physical layer loopback test:

1. Navigate to configure port ethernet <port> to select the Ethernet port to
test.
The config>port>eth(<port>)# prompt is displayed.
2. Enter:
loopback {local|remote} [duration <seconds>].
The duration is in seconds, with a range of 086400. Entering 0 or not
specifying the duration disables the timer; i.e. the loopback continues running
until you disable it.
While the test is running, entering show summary at the port level displays
the ports operational status as Testing (refer to Displaying Ethernet Port
Status).
3. To end the loopback test, enter:
no loopback.
To run loopback on Ethernet port 3:

ETX-1>config>port>eth(3)# loopback remote duration 30
ETX-1>config>port>eth(3)# show loopback
Loopback : Remote Remain (sec) : 21
Displaying Ethernet Port Statistics
Displaying Port Statistics
To display the Ethernet port statistics:

At the prompt config>port>eth(<port-num>)#, enter:
show statistics.
Ethernet port statistics are displayed. The counters are described in
Table 6-2.

Example
To display the statistics for Ethernet port 1 with SFP:

ETX-1>config>port>eth(1)# show statistics
Rates Sampling Window
-----------------------------------------------------------------------------
Window Size [Min.] : 15
Window Remain Time [Min.] : 14
Running
-----------------------------------------------------------------------------
Rx Tx
Total Frames : 0 0
Total Octets : 0 0
Total Frames/Sec : 0 0
Total Bits/Sec : 0 0
Minimum Bits/Sec : 0 0
Maximum Bits/Sec : 0 0
Unicast Frames : 0 0
Multicast Frames : 0 0
Broadcast Frames : 0 0
Dropped Frames : 0
CRC Errors : 0 --
Error Frames : 0
CRC Errors/Sec : 0 --
Oversize Frames : 0 0
64 Octets : 0 0
65-127 Octets : 0 0
128-255 Octets : 0 0
256-511 Octets : 0 0
512-1023 Octets : 0 0
1024-1518 Octets : 0 0
1519-Max Octets : 0 0
SFP
-----------------------------------------------------------------------------
Minimum Maximum
RX Power (dBm) : -36.9 dBm -36.9 dBm
TX Power (dBm) : -5.1 dBm -5.0 dBm
Laser Bias (mA) : 5.7 mA 6.1 mA
Laser Temperature (Celsius) : 42.0 C 51.0 C
Power Supply (V) : 3.2 V 3.2 V
Table 6-2. Ethernet Statistics Parameters
Parameter Description
Window Size [Min.] Interval for sampling statistics, user-configurable

Window Remain Time [Min.] Amount of time remaining in statistics sampling window
Total Frames Total number of frames received/transmitted
Total Octets Total number of bytes received/transmitted
Total Frames/Sec Number of frames received/transmitted per second
Total Bits/Sec Number of bits received/transmitted per second
Minimum Bits/Sec Minimum number of bits received/transmitted per second
Maximum Bits/Sec Maximum number of bits received/transmitted per second
Unicast Frames Total number of unicast frames received/transmitted
Multicast Frames Total number of multicast frames received/transmitted
Broadcast Frames Total number of broadcast frames received/transmitted
Error Frames Total number of frames with errors received
Dropped Frames Total number of frames dropped
CRC Errors Total number of frames received that are an integral number of octets in
length, but do not pass the Frame Check Sequence (FCS) check. This count
does not include frames received with Frame-Too-Long or Frame-Too-Short
error.
CRC Errors/Sec Number of frames per second received that are an integral number of octets
in length, but do not pass the Frame Check Sequence (FCS) check. This count
does not include frames received with Frame-Too-Long or Frame-Too-Short
error.
Oversize Frames Total number of oversized frames received/transmitted
64 Octets Total number of received/transmitted 64-byte packets
65127 Octets Total number of received/transmitted 65 to 127-byte packets
1519Max Octets Total number of received/transmitted packets with 1519 bytes and up to
maximum
Clearing Statistics
To clear the statistics for an Ethernet port:

At the prompt config>port>eth(<port>)#, enter:
clear-statistics.
The statistics for the specified port are cleared.

6.2 Service Virtual Interface

A service virtual interface (SVI) is a logical port used for flows.
Note ETX-1 can creates up to eight SVIs, but ETX-1 supports up to two valid
management interface (router interfaces).
Configuring Service Virtual Interfaces

You can enable and operate service virtual interfaces as explained below.
To configure the SVI parameters:
1. Navigate to configure port svi <port-number> to select the SVI to configure.
The config>port>svi(<port-number>)# prompt is displayed.
Setting the port name name <string> no name removes

the name
Administratively enabling SVI no shutdown shutdown disables

the SVI
ETX-1 Ver. 1.2 Service Virtual Interface 6-9

6-10 Service Virtual Interface ETX-1 Ver. 1.2

Chapter 7
Resiliency
7.1 Link Aggregation

Link aggregation (LAG) can be enabled when the second port works in network
mode. The two network ports can form a LAG. After LAG was enabled, both ports
receive traffic at the same time and transmit. Both network ports must be
enabled and they must have the same configuration.
Standards and MIBs

IEEE 802.3-2005
Benefits
ETX-1 can use the load balance to increase the bandwidth.
The two network Ethernet ports can be operated as a single logical interface,
using link aggregation in accordance with IEEE 802.3-2005. The two ports must
be connected to the same switch/router.
Factory Defaults
By default, no LAG is configured.
Configuring LAG
This section explains how to define a link aggregation group (LAG). ETX-1
supports one LAG.
To configure the LAG:

1. Navigate to configure port lag 1.
The config>port>lag(1)# prompt is displayed.
ETX-1 Ver. 1.2 Link Aggregation 7-1

Chapter 7 Resiliency Installation and Operation Manual
Assigning an admin key to the admin-key {fast-ethernet | You must define admin key
giga-ethernet}
LAG to indicate the port speed before binding ports to the
LAG
Adding a port to the LAG bind ethernet <port > Using no before bind removes
a link from the LAG
Assigning method of distributing distribution-method {src-mac | dest- src-mac Packets are

traffic within LAG mac | src-and-dest-mac | src-ip | dest- distrubuted according to their
ip | src-mac-and-ip | src-mac-and-dst- source MAC addresses
ip | dst-mac-and-src-ip | dst-mac-and- dest-mac Packets are
ip | src-and-dst-ip | src-dst-mac-and- distrubuted according to their
src-ip | src-dst-mac-and-dst-ip | src- destination MAC addresses
mac-and-src-dst-ip | dst-mac-and-src-
src-and-dest-mac Packets are
dst-ip| src-dest-mac-ip }
distrubuted according to their
source and destination MAC
addresses
src-ip Packets are distrubuted
according to their source IP
addresses
dest-ip Packets are
destination IP addresses
src-dest-mac-ip Packets are
source and destination MAC
and IP addresses
src-mac-and-ip Packets are
source MAC and IP addresses
src-mac-and-dst-ip Packets
are distrubuted according to
their source MAC addresses
and destination IP addresses
dst-mac-and-src-ip Packets
are distrubuted according to
their destination MAC
addresses and source IP
addresses
dst-mac-and-ip Packets are
destination MAC and IP
addresses
src-and-dst-ip Packets are
source and destination IP
addresses
src-dst-mac-and-src-ip
Packets are distrubuted
7-2 Link Aggregation ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 7 Resiliency
according to their source and

destination MAC addresses and
source IP addresses
src-dst-mac-and-dst-ip
according to their source and
destination MAC addresses and
destination IP addresses
src-mac-and-src-dst-ip
according to their source MAC
addresses and source IP
addresses and destination IP
addresses
dst-mac-and-src-dst-ip
according to their destination
MAC addresses and source IP
addresses and destination IP
addresses
Administratively enabling LAG no shutdown Using shutdown disables the

LAG
Display bind status show bind
Displaying LAG status show status
Example
To define LAG 1:
LAG members Ethernet ports 1 and 2
ETX-1>config>port# lag 1
ETX-1>config>port>lag(1)$ bind ethernet 1
ETX-1>config>port>lag(1)$ bind ethernet 2
ETX-1>config>port>lag(1)$ no shutdown
ETX-1>config>port>lag(1)$
ETX-1 Ver. 1.2 Link Aggregation 7-3

Displaying LAG Status

To display the LAG status do the following:
ETX-1#configure port lag 1
ETX-1>config>port>lag(1)# show status
Group
-----------------------------------------------------------------------------
Administrative Status : Up
Operation Status : Down
MAC Address : 00-20-D2-50-1A-13
Links
-----------------------------------------------------------------------------
Port Admin Oper Redundancy
-----------------------------------------------------------------------------
1 Up Down Standby
2 Up Down Standby
ETX-1>config>port>lag(1)#
7.2 Fault Propagation

Fault propagation enables you to specify which interfaces to shut down if link
failure occurs.
Standards
IEEE 802.1ag, ITU-T Y.1731
Benefits
You can ensure packets are being sent via links that have not failed. Failures are
propagated end-to-end via OAM CFM messages.
Network-to-user fault propagation mechanism on the port and OAM CFM levels:
When fault propagation is enabled, the user port shuts itself down or an OAM
CFM indication of failure is sent when a link failure is detected at the network
port or when an OAM CFM indication of failure is received.
User-to-network fault propagation mechanism on the port and OAM CFM levels:
When fault propagation is enabled, an OAM CFM indication of failure is sent to
Network port once a failure is detected on User port.
You can enable fault propagation to be triggered by failure detection on a
network/user interface, which causes a user-configurable action (such as
deactivation or OAM CFM failure message sent) to be performed on a
user/network interface. You can enable fault propagation in the network-to-user
direction, for a pair of interfaces such as Ethernet ports.
7-4 Fault Propagation ETX-1 Ver. 1.2

You can define the following when you enable fault propagation for a pair of
interfaces:
Trigger:
If the interface where failure is detected is an Ethernet port:
LOS Link down detected
If the interface where failure is detected is a MEP:
OAM CFM AIS Alarm indication signal detected
OAM CFM LOC Loss of continuity detected
OAM CFM RDI Remote defect indication detected
OAM CFM Interface status TLV Remote port failure detected
Action to take when fault propagation is triggered:
If the interface where action is performed is an Ethernet port:
Interface deactivation
If interface where action is performed is a MEP:
Send OAM CFM alarm indication signal to indicate failure
or
Send OAM CFM interface status TLV to indicate failure.
Wait-to-restore time The time to wait until enabling the shut-down
interface or ceasing to send OAM CFM interface status once the failed
interface has been restored.
Factory Defaults
By default, no fault propagation is configured. When you configure fault
propagation for a particular interface pair, the default configuration is as follows:
No trigger defined for fault detection
No action defined to be performed when fault is detected
Wait-to-restore time = 0.
Configuring Fault Propagation

To configure fault propagation:
1. Add a fault propagation entry for a pair of interfaces
2. Configure the fault propagation parameters for the entry:
a. Specify the trigger(s)
b. Specify the action
c. Specify the wait-to-restore time if you do not want the default value 0.
ETX-1 Ver. 1.2 Fault Propagation 7-5

Adding Fault Propagation Entry

To add fault propagation for a pair of interfaces:
1. Navigate to configure fault.
2. Type the command:
fault-propagation <from-interface> to <to-interface> and enter the desired
interfaces, as shown in Table 7-1.
A prompt is displayed:
config>fault>fp(<from-interface>/to/<to-interface>) $.
3. Configure the fault propagation parameters as needed (refer to Configuring
Fault Propagation Parameters).
Table 7-1. Fault Propagation Command Options
From Interface To Interface Command
MEP Ethernet port fault-propagation mep <mdid> <maid> <mepid> to

port ethernet <port>
LAG port Ethernet port fault-propagation port lag <port-number> to port

ethernet <port>
Ethernet port MEP fault-propagation port ethernet <port> to

mep <to-mdid> <to-maid> <to-mepid>
LAG port MEP fault-propagation port lag <port-number> to mep <to-

mdid> <to-maid> <to-mepid>
MEP MEP fault-propagation mep <md-id> <ma-id> <mep-id> to

mep <to-mdid> <to-maid> <to-mepid>
Ethernet port Ethernet port fault-propagation port ethernet <port> to

port ethernet <port>
Configuring Fault Propagation Parameters

To configure fault propagation parameters:
1. Navigate to configure fault fault-propagation <from-interface> to
<to-interface> to select the fault propagation entry to configure.
A prompt is displayed:
config>fault>fp(<from-interface>/to/<to-interface>)#
Specifying the trigger { los | oam-cfm-loc | oam-cfm-rdi Typing no before the command
trigger(s) | oam-cfm-if-status-tlv | oam-cfm-ais} removes the specified trigger
Note: The los trigger is allowed only if
the from-interface is an Ethernet port.
The OAM CFM triggers are allowed only
if the from-interface is a MEP.

Specifying the action action-on-group {interface-deactivation | Typing no action-on-group removes

to take when fault oam-cfm-if-status-tlv | oam-cfm-ais} the action
propagation is Note: The interface-deactivation action
triggered is allowed only if the to-interface is an
Ethernet port. The OAM CFM action is
allowed only if the to-interface is a
MEP.
Specifying the wait-to-restore <seconds> The range is 03600

wait-to-restore time
Example
To enable fault propagation from Ethernet port 4 to MEP 3 (in MD 2, MA 3) (this

example assumes the MEP has been created) configure the following:
Trigger: LOS
Action: Send OAM CFM interface status TLV
Wait-to-restore time = 120 seconds.
ETX-1# config fault
ETX-1>config>fault# fault-propagation port ethernet 4 to mep 2 3 3
ETX-1>config>fault>fp(port/ethernet/4/to/mep/2/3/3)$ trigger los
ETX-1>config>fault>fp(port/ethernet/4/to/mep/2/3/3)$ action-on-group oam-cfm-
if-status-tlv
ETX-1>config>fault>fp(port/ethernet/4/to/mep/2/3/3)$ wait-to-restore 120
ETX-1>config>fault>fp(port/ethernet/4/to/mep/2/3/3)$ info detail
action-on-group oam-cfm-if-status-tlv
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-if-status-tlv
no trigger oam-cfm-rdi
no trigger oam-cfm-ais
wait-to-restore 120
ETX-1>config>fault>fp(port/ethernet/4/to/mep/2/3/3)$
To enable fault propagation from Ethernet port 1 to Ethernet port 3,configure

the following:
Trigger: LOS
Action: Shut down Ethernet port
ETX-1 Ver. 1.2 Fault Propagation 7-7

ETX-1# config fault

ETX-1>config>fault# fault-propagation port ethernet 1 to port ethernet 3
ETX-1>config>fault>fp(port/ethernet/1/to/port/ethernet/3)$ trigger los
ETX-1>config>fault>fp(port/ethernet/1/to/port/ethernet/3)$ action-on-group
interface-deactivation
ETX-1>config>fault>fp(port/ethernet/1/to/port/ethernet/3)$ wait-to-restore 90
ETX-1>config>fault>fp(port/ethernet/1/to/port/ethernet/3)$ info detail
action-on-group interface-deactivation
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-if-status-tlv
no trigger oam-cfm-rdi
no trigger oam-cfm-ais
wait-to-restore 90
ETX-1>config>fault>fp(port/ethernet/1/to/port/ethernet/3)$
To enable fault propagation:

From MEP 1 in maintenance association 1 in maintenance domain 1 (this
example assumes the MEP has been created)
To MEP 2 in maintenance association 2 in maintenance domain 1 (this
example assumes the MEP has been created)
Trigger: Any OAM CFM error
Action: Send OAM CFM interface status TLV
ETX-1# config fault
ETX-1>config>fault# fault-propagation mep 1 1 1 to mep 1 2 2
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ trigger oam-cfm-loc
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ trigger oam-cfm-rdi
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ trigger oam-cfm-if-status-tlv
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ trigger oam-cfm-ais
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ action-on-group oam-cfm-if-
status-tlv
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ wait-to-restore 300
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$ info detail
action-on-group oam-cfm-if-status-tlv
no trigger los
trigger oam-cfm-loc
trigger oam-cfm-if-status-tlv
trigger oam-cfm-rdi
trigger oam-cfm-ais
wait-to-restore 300
ETX-1>config>fault>fp(mep/1/1/1/to/mep/1/2/2)$
Disabling Fault Propagation

To disable fault propagation for a pair of interfaces:
1. Navigate to configure fault.

2. Type the command:

no fault-propagation <from-interface> to <to-interface> to select the
interfaces for which to disable fault propagation.
The specified fault propagation is disabled.
7.3 Ethernet Ring Protection (ERP)

A G.8032 Layer-2 Ethernet ring is used by ETX-1 for traffic protection. This
technology builds a logical ring, defined as a set of IEEE 802.1-compliant bridges,
and protects against link and node failures. ETX-1 supports only one ring (major)
per shelf.
Standards
ITU-T G.8032-2010
Benefits
G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and
prevent loops at the Ethernet layer.
Ethernet Ring Protection technology provides scalable solution for low-cost traffic
protection and rapid service restoration, with SDH/SONET-type resilience. It is
built on traditional Ethernet MAC (IEEE 802.3) and bridging (IEEE 802.1) functions.
It is independent of any physical-layer technologies and can be utilized in any
carriers network.
In ERP there is one node designated as RPL, which periodically sends R-APS
messages, defining ring state and operation. When a link failure occurs, it is
detected via LOS. Upon failure, node forwarding information is recalculated to
ensure that data traffic reaches its destination, using alternative path.
Note The ring port cannot be bound to a LAG.

ETX-1 supports only one ring protection for network port 1 and 2.
Ring Topology
ETX-1 supports single ring topology.
Ring node A
East Port
(RPL Owner)
West Port
(Neighbor)
Ring node D Ring node B
Ring node C
Figure 7-1. Ethernet Ring
ETX-1 Ver. 1.2 Ethernet Ring Protection (ERP) 7-9

R-APS Messaging
Ethernet ring protection is achieved by means of a dedicated protocol,
Automated Protection Switching (APS). Every ring link is bound by two adjacent
nodes. At any time, traffic flows on all, but one of the ring links. This link is called
the ring protection link (RPL). Under normal conditions this link is blocked. RPL is
controlled by a single node called an RPL owner, which prevents traffic from using
the RPL. When a failure is detected, the RPL owner unblocks the RPL port,
allowing the RPL to be used for traffic. The other Ethernet Ring Node adjacent to
the RPL, the RPL Neighbor Node, may also participate in blocking or unblocking its
end of the RPL.
R-APS messages require a designated transmission channel (R-APS channel),
which is separated from the service traffic channel. An R-APS channel is
configured using a separate dedicated VLAN to enable the R-APS messages to
handled differently from the service traffic. An R-APS channel and service traffic
blocking is performed via VID filtering by the bridge.
Mechanism of Operation
Every failure along the ring triggers an R-APS (SF) (R-APS Signal Fail) message
along both directions from the nodes adjacent to the failed link. Before sending
the R-APS, these nodes block the ports facing the failed link. On receiving these
messages, the RPL owner unblocks the RPL port. An SF message is triggered even
if only one node adjacent to the failed link recognizes the failure.
During a recovery phase, when a failed link is restored and a node detects a Clear
SF continually it sends R-APS (No Request, NR) and keeps the failed port blocked.
When receiving the R-APS (NR), the RPL owner starts its Wait-To-Restore (WTR)
timer. When that timer expires it blocks the RPL port and sends RAPS (NR, RB) (R-
APS no request, root blocked) messages along both direction of the ring. Nodes
receiving the R-APS (NR, RB) message flush their learning table, unblock their
blocked ports and return back to idle state.
Timers
The following timers are used to facilitate ERP operation:
Wait-to-Restore (WTR) Period of time used by RPL owner to verify that the
ring has stabilized before blocking the RPL after signal recovery.
Guard Period of time during which all received A-RPS messages are ignored
by the ERP mechanism. This prevents the ring nodes from receiving outdated
A-RPS messages circulating the network.
Hold-off Period of time during which the underlying Ethernet layer attempts
to filter out intermittent link faults before reporting them to the ERP
mechanism.
Administrative Commands
If there is a need to intervene into ERP operation for maintenance or any other
reason, the operator can issue forced or manual switch command.
Forced switch command forcefully blocks a particular ring port. It can be
issued even if an SF condition exists on the ring.
7-10 Ethernet Ring Protection (ERP) ETX-1 Ver. 1.2

Manual switch command manually blocks a particular ring port with manual
switch command. It can be overridden by SF condition or a force switch
command.
Clear command clear all existing force and manual switch command on the
ERP.
Note The manual and forced switch are temporary commands and they do not change
the location of the RPL permanently.
Factory Defaults
No Ethernet protection ring is configured in the system by default.
Configuring ERP
To configure ERP:
1. In the configure>protection# prompt, enter erp 1 and ring type (major).
An ERP instance with is created and the config>protection>erp(ring-
number)# prompt is displayed.
2. Configure the ERP as illustrated and explained below.
Note no before erp (ring-number) deletes an ERP instance.
Making the ring compatible with backward-compatibility Using no before backward-

previous ERP implementations compatibility disables the
compatibility
Assigning node to a bridge bridge <1>

instance
Assigning VLANs to be protected data-vlan <14094> Using no before data-vlan

by the ring removes VLAN from the ring
protection
Defining bridge port as an East east-port <bridge_port_number> Only support Net Port
port of ERP node
Defining bridge port as a West west-port <bridge_port_number> Only support Net Port
port of ERP node

Defining node port type in port-type {east|west} {node- node-port regular node port,
relation to RPL owner port|rpl|neighbor|next-neighbor} which is not connected to RPL
owner
rpl RPL owner
neighbor port directly
connected to RPL owner
next-neighbor Current
software version unsupported
Configuring dedicated VLAN for r-aps [vlan <14094>] [vlan-priority R-APS settings must be same for
R-APS messages <07>] [mel <07>] all ring members
Configuring the revertive mode revertive This mode is relevant to the RPL
owner node.
In the revertive mode, after
the condition causing the switch
is cleared, traffic is blocked at
the RPL owner and restored to
the working state.
After the node has entered the
pending state in non-revertive
mode, use the Clear command
to exit the state.
no revertive enables
non-revertive mode.
Administratively enabling the no shutdown To avoid traffic loops, always

ERP interface enable Ethernet ports only after
enabling Ethernet ring.
shutdown disables the ERP.
Defining guard and hold-off timers [guard<102000>] [holdoff<0 Guard timer is used by the ERP
periods in msec 10000>] mechanism to prevent ring
nodes from receive outdated R-
APS messages. While the guard
timer is active, all received R-APS
messages are ignored by the
node. The guard timer is
configured in 10-ms steps.
Hold-off timer is used by
Ethernet layer to filter out
intermittent faults. Faults are
reported to the ERP mechanism
only after the hold-off timer
expires. The Hold-off timer is
configured in 100-ms steps.

Defining Wait to Restore Timer wait-to-restore <seconds> Wait-to-restore timer is used by

in seconds RPL owner to verify that the ring
has stabilized before blocking
the RPL after signal recovery.
Note: WTR timer may be
configured in 1 minute steps
between 1 and 12 minutes.
Blocking the East or West port of manual-switch {east-port | west-port } The manual switch command can
a ring node be applied to a single ring node
only. When the command is
active, all ring nodes shift to the
manual switch mode.
Blocking the East or West port of forced-switch {east-port | west-port } The forced switch can be applied
a ring node to any number of nodes in the
ring.
Clearing the existing switch clear

commands
Displaying ERP status show status
Displaying ERP statistics show statistics
Clearing ERP statistics clear statistics
Displaying ERP Status

You can display current status of configured ERP entity.
To display ERP status:

In the config>protection>erp(ring-number)$ prompt, enter show status.
The ERP status is displayed.
ETX-1>config>protection>erp(1)$ show status
Bridge Number : 1 East Port : 1 West Port : 2

RPL Link : Not Owner
Ring State : Init
East Port Status : Forward Local SF Source : OK

West Port Status : Forward Local SF Source : OK
Displaying ERP Statistics

When the G.8032 Ethernet Ring Protection (ERP) is enabled, ETX-1 allows collecting
statistics on R-APS messages sent and received by the East and West ports.
To display ERP statistics:

In the config>protection>erp(ring-number)$ prompt, enter show statistics..

The ERP statistic counters are displayed.

ETX-1>config>protection>erp(1)$ show statistics
East Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 0 0
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
West Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 0 0
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
Table 7-2. ERP Statistic Counters
Counter Description
R-APS SF Message Tx/Rx Total number of R-APS Signal Fail (SF) messages received or transmitted
by East/West port.
Received R-APS Signal Fail message indicates a failed port in the ring.
Transmitted R-APS Signal Fail message indicates a failed port in the
node.
R-APS NR Message Tx/Rx Total number of R-APS No Request (NR) messages received or
transmitted by East/West port.
Received R-APS No Request message indicates absence of failed ports in
the ring.
Transmitted R-APS No Request message indicates that the node fixed its
failed port.
R-APS NR, RB Tx/Rx Total number of R-APS No Request (NR), RPL Blocked (RB) messages
received or transmitted by East/West port.
Received R-APS No Request, RPL Blocked message indicates that RPL
port is blocked and all other not-failed blocked ports are unblocked in
the ring.
Transmitted from the RPL No Request, RPL Blocked message indicates
that RPL port is blocked.
Total Valid Rx/Tx Total number of valid R-APS messages received or transmitted by
East/West port
Total Errors Rx/Tx Total number of errored R-APS messages received or transmitted by
East/West port
Example
Figure 7-1 (please refer to In ERP there is one node designated as RPL, which
periodically sends R-APS messages, defining ring state and operation. When a link
failure occurs, it is detected via LOS. Upon failure, node forwarding information is

recalculated to ensure that data traffic reaches its destination, using alternative
path.
The ring port cannot be bound to a LAG.

ETX-1 supports only one ring protection for network port 1 and 2.
Ring Topology) and the following configuration is about Ring node A and Ring
node B.
Note
R-APS settings must be the same for other Ring nodes.
Only one port can be configured as RPL owner in the Ring.
Bridge ports are used in the Ring, they should be configured as ingress-filtering.
To configure the ERP:

1. Ring node A configuration:
Define VLAN membership:
VLAN 2
BP 3-6 member of VLAN 2
BP 1 and BP 2 ingress-filter
Configure the ring:
East port type rpl
West port type node-port
BP 1 East port
BP 2 West port
R-APS VLAN 1234
Data VLANs 2
#******************** Configuring_VLAN_Membership****************************
config bridge 1 vlan 2
tagged-egress 3..6
exit
port 1
ingress-filtering
exit
port 2
ingress-filtering
exit all
#************************ Configuring_the_Ring*******************************
config protection erp 1 major
port-type east rpl
port-type west node-port
bridge 1
east-port 1
west-port 2
r-aps vlan 1234 vlan-priority 1 mel 1
data-vlan 2
no shutdown
exit all
2. Ring node B configuration:

Define VLAN membership:

VLAN 2
Configure the ring:
West port type neighbor
East port type node-port
BP 1 East port
BP 2 West port
R-APS VLAN 1234
Data VLANs 2
#******************** Configuring_VLAN_Membership****************************
tagged-egress 3..6
exit
port 1
ingress-filtering
exit
port 2
ingress-filtering
exit all
#************************ Configuring_the_Ring*******************************
port-type west neighbor
port-type east node-port
bridge 1
east-port 1
west-port 2
data-vlan 2
no shutdown
exit all

Chapter 8
Networking
8.1 Layer 2 Control Processing

ETX-1 can be configured to pass through Layer-2 Control frames (including other
vendors L2CP frames) across the network, to peer the supported protocol or to
discard the L2CP frames.
You can create profiles to define the handling of Layer-2 Control Protocol traffic.
You then assign the required profile to an Ethernet port (refer to Configuring
Ethernet Port Parameters).
Standards
IEEE 802.3
Benefits
Layer 2 Control Protocol traffic can be passed or filtered to Ethernet virtual
connections.
Factory Defaults
ETX-1 provides a default L2CP profile named L2cpDefaultProfile, configured as
follows:
For MAC hex byte 0x00 through 0x2f, action = tunnel
When a new L2CP profile is created, it has the same configuration as the
L2cpDefaultProfile. You can define up to 5 L2CP profiles in addition to the
L2cpDefaultProfile.
Adding Layer 2 Control Processing Profiles

To add an L2CP profile:
1. Navigate to configure port.
The config>port# prompt is displayed.
2. Type:
l2cp-profile <l2cp-profile-name>
An L2CP profile with the specified name is created and the
config>port>l2cp-profile(<l2cp-profile-name>)$ prompt is displayed. The
new profile is configured by default as described in Factory Defaults.
ETX-1 Ver. 1.2 Layer 2 Control Processing 8-1

Chapter 8 Networking Installation and Operation Manual
3. Configure the L2CP profile as needed (refer to Configuring Layer 2 Control

Processing Profile Parameters).
Deleting Layer 2 Control Processing Profiles

You can delete an L2CP profile only if it is not assigned to any port.
To delete an L2CP profile:
1. Navigate to configure port.
The config>port# prompt is displayed.
2. Type:
no l2cp-profile <l2cp-profile-name>
The L2CP profile with the specified name is deleted if it is not assigned to
any port.
Configuring Layer 2 Control Processing Profile Parameters

To configure an L2CP profile:
1. Navigate to configure port l2cp <l2cp-profile-name> to select the L2CP profile
to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
Specifying the L2CP action for mac <mac-addr-last-byte-value-list> discard L2CP frames are
MAC addresses (discard, {discard | tunnel | peer} discarded
tunnel, or peer) tunnel L2CP frames are
forwarded across the network as
ordinary data
peer ETX-1 peers with the user
equipment to run the protocol.
L2CP frames are forwarded to the
ETX-1 CPU. Unidentified L2CP
frames are forwarded across the
network as ordinary data. Only
0x00 and 0x02 are effective
no mac
<mac-addr-last-byte-value-list>
removes the action for the
specified MAC address
8-2 Layer 2 Control Processing ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 8 Networking
Example
To add L2CP profile named layer2ctrl1 with discard action for hex byte 0x01 and
0x03:
ETX-1>config>port# l2cp-profile layer2ctrl1
ETX-1>config>port>l2cp-profile(layer2ctrl1)$ mac 0x01 discard
ETX-1>config>port>l2cp-profile(layer2ctrl1)$ mac 0x03 discard
ETX-1>config>port>l2cp-profile(layer2ctrl1)$ info detail
mac 0x00 tunnel
mac 0x01 discard
mac 0x02 tunnel
mac 0x03 discard
mac 0x04 tunnel
mac 0x05 tunnel
mac 0x06 tunnel
mac 0x07 tunnel
mac 0x08 tunnel
mac 0x09 tunnel
mac 0x0a tunnel
mac 0x0b tunnel
mac 0x0c tunnel
mac 0x0d tunnel
mac 0x0e tunnel
mac 0x0f tunnel
mac 0x20 tunnel
mac 0x21 tunnel
mac 0x22 tunnel
mac 0x23 tunnel
mac 0x24 tunnel
mac 0x25 tunnel
mac 0x26 tunnel
mac 0x27 tunnel
mac 0x28 tunnel
mac 0x29 tunnel
mac 0x2a tunnel
mac 0x2b tunnel
mac 0x2c tunnel
mac 0x2d tunnel
mac 0x2e tunnel
mac 0x2f tunnel
ETX-1>config>port>l2cp-profile(layer2ctrl1)$
To delete L2CP profile named layer2ctrl1:

ETX-1>config>port# no l2cp-profile layer2ctrl1
ETX-1>config>port#
ETX-1 Ver. 1.2 Layer 2 Control Processing 8-3

8.2 Ethernet Bridge
Standards
The following standards are supported:
IEEE 802.1ad
IEEE 802.1Q.
IEEE 802.1w
Factory Defaults
The default configuration of the bridge is as follows:
VLAN-aware Enabled
Filtering Enabled
Aging time 300 seconds
Port 1-6 named BRIDGE PORT 1-6
Bind: Ethernet 1-6
Ingress filtering Disabled
Accept-frame-type All
Port VID 1, Priority 0
Spanning-tree
Path cost 0
Priority 128
Admin-edge false
Auto-edge true
Mcheck false
Admin status shutdown
Port 7 named BRIDGE PORT 7
Port VID 1, Priority 0
Spanning-tree
Operation mode rstp
max-age 20
forward-time 15
hello-time 2
priority 32768
tx-hold-count 3
8-4 Ethernet Bridge ETX-1 Ver. 1.2

An Ethernet bridge joins two or more LAN (Local Area Network) connections,
thus creating a larger LAN. It is a device that can modulate the traffic passing
between different local area networks.
ETX-1 supports RSTP which can be used to prevent loops in Layer 2 networks and
provides rapid convergence of the spanning tree.
Configuring the Bridge

ETX-1 supports one bridge.
To configure the bridge:

1. At the config# prompt, enter:
bridge 1
The config>bridge(1)# prompt is displayed.
Defining a period of time to age, aging-time <seconds> The value is 7-458745.

in seconds
Enabling the bridge forwarding filtering

mode
Defining VLAN ID vlan <vlan-id> no vlan <vlan-id> removes the

VLAN ID
The value is 1-4094
Defining VLAN name name <string>
Transmitting tagged frames for tagged-egress <bridge-port-list> If port numbers are sequential,
the VLAN indicate by using ".."; e.g., 1..5.
If not sequential, indicate by using
","; e.g.,1,3
Transmitting untagged frames for untagged-egress <bridge-port-list> If port numbers are sequential,
the VLAN indicate by using ".."; e.g., 1..5.
If not sequential, indicate by using
","; e.g.,1,3
Adding the MAC address to the static-mac <vlan-id> <mac-address> The available numbers of MAC
specified VLAN ID <bridge-port> addresses depends on the VLAN
ID. Configure the VLAN ID to add
more than one MAC address and
vice versa. You can add up to 64
static MAC.
Defining the bridge port port <port-number>
Specifying the frame types to be accept-frame-type {all | vlan-only}

accepted by the bridge port
ETX-1 Ver. 1.2 Ethernet Bridge 8-5

Clearing the statistics clear-statistics
Controling filtering of the ingress-filtering

incoming traffic
Defining ingress VLAN tag ingress-tag push vlan <sp-vlan> p- Configurable on user port only
handling behavior bit fixed <pbit-value> sp-vlan range is 14094,
ingress-tag push vlan <sp-vlan> p- pbit-value range is 07
bit copy
no ingress-tag
Defining the bridge port name name <port-name>
Assigning PVID to the bridge port pvid <vlan-id> priority <vlan-

priority>
Assigning the priority mapping to queue-mapping <profile-name> <profile-name> must be pbit-

the bridge port profile or dscp-profile
Clearing MAC addresses clear-mac-table [{static | dynamic}]

[vlan <vlan>] [mac-address <mac-
address-low>] [to-mac-address
<mac-address-high>] [ports
<ports>]
Displaying the MAC addresses show mac-address-table {static |

dynamic | all} [vlan <vlan>] [mac-
address <mac-address-low>] [to-
mac-address <mac-address-high>]
[ports <ports>]
Displaying the VLAN members show vlans [refresh [<sec>]]
Note
ERP and RSTP should not be configured at the same time
RSTP and LAG should not be configured at the same time
To configure RSTP:
1. At the config>bridge(1)>spanning-tree# prompt, enter:
spanning-tree
The config>bridge(1)>spanning-tree# prompt is displayed.
Defining the forward-time <seconds> The value is 4-30

time duration in Note: You cannot
listening and assign forward-
learning states time a value less
that precede than max-age/2+1.
the forwarding
state, in
seconds

Defining the hello-time <seconds> The value is 1-10

time interval in
seconds
between BPDU
transmissions
Defining the max-age <seconds> The value is 6-40.

maximum age Note: You cannot
of the assign max-age a
configuration value that is less
BPDU can be than 2*(hello-
maintained on a time+1) or more
device.
than 2*(forward-
time1).
Defining the mode rstp

operation mode
for spanning-
tree
Assigning the priority

bridge priority {0|4096|8192|12288|16384|20480|24576|28672|32768|36864|40960|
value 45056|49152|53248|57344|61440}
Configure the tx-hold-count The value is 1-10

maximum
number of
BPDUs
transmitted
Displaying the show status

spanning-tree
status
To configure RSTP for port:

1. At the config>bridge(1)>port<port-number>spanning-tree# prompt, enter:
spanning-tree
The config>bridge(1)>port<port-number>spanning-tree# prompt is
displayed.
Setting the edge admin-edge {true|false}

port admin status
Setting the edge auto-edge {true|false}

port automatically
Setting the path- cost <number>

cost for the port

Forcing the port to mcheck {true|false}

transmit RST BPDUs
Assigning the priority

priority value on the {0|16|32|48|64|80|96|112|128|144|160|176|192|208|224|240}
port
Administratively no shutdown shutdown disables the

enabling the spanning-tree on the
spanning-tree on port.
the port
Displaying the show status

spanning-tree
status on the port
Example Defining RSTP

The following example illustrates the use of the RSTP:
Management Host IP
192.168.100.144
ETH 1 ETH 2
ETH 4
Management Host IP Management Host IP

192.168.100.141 192.168.100.143
ETH 2 ETH 1
NMS ETH 5
192.168.100.10
A C
ETH 1 ETH 2
ETH 6
ETH 2 ETH 1
Management Host IP
192.168.100.142
To configure RSTP:
1. Configure device A:
a. Configure the second port to be the user port:
configure port ethernet 2
shutdown
functional-mode user
no shutdown
exit all
b. Configure the physical interface management flow:

#******************** Configuring_svi ***************************************

no shutdown
exit all
#******************** Configuring_classification profile *******************

match untagged
exit all
#******************** Configuring_management flow ***************************

configure flows flow mn_in
classifier untagged
no shutdown
exit
flow mn_out
classifier untagged
ingress-port svi 1
no shutdown
exit all
#******************** Configuring_router **********************************

bind svi 1
address 192.168.100.141/24
no shutdown
exit all
c. Configure VLAN membership:
configure bridge 1 vlan 1
untagged-egress 1..6
exit
vlan 4
tagged-egress 1..4,6..7
untagged-egress 5
exit all
d. Configure PVID for port 5:
configure bridge 1 port 5
pvid 4 priority 7
exit all
e. Configure the spanning tree:
#******************** Configuring_spanning tree for bridge ******************
configure bridge 1 spanning-tree
priority 12288
exit all
#******************** Configuring_spanning tree on port ******************

configure bridge 1
port 1
spanning-tree
cost 8213818
priority 192
no shutdown
exit
exit
port 2
spanning-tree
cost 12345678
priority 224
no shutdown
exit all
1. Configure device B, C and D:
a. Configure the second port to be a user port:
configure port ethernet 2
shutdown
functional-mode user
no shutdown
exit all
b. Configure the bridge management flow:
#******************** Configuring_svi ***************************************
no shutdown
exit all
#******************** Configuring_classification profile *******************

match untagged
exit
match vlan 4
exit all
#******************** Configuring_management flow ***************************

configure flows
flow mn_in
classifier v4
ingress-port bridge-port 7
vlan-tag pop vlan
no shutdown
exit
flow mn_out
classifier untagged
ingress-port svi 1
egress-port bridge-port 7
no shutdown
exit all
#******************** Configuring_router **********************************

bind svi 1
address 192.168.100.142/24 (please configure the corresponding address for
device C and device D)
no shutdown
exit all
c. Configure VLAN membership:
configure bridge 1 vlan 1
untagged-egress 1..6
exit
vlan 4
tagged-egress 1..7
exit all
d. Configure the spanning tree:
#******************** Configuring_spanning tree for bridge ******************
Bridge spanning tree for device B:
priority 20480
exit all
Bridge spanning tree for device C:

priority 61440
exit all
Bridge spanning tree for device D (this device is the ROOT device because it
has the highest priority):
priority 0
exit all
#******************** Configuring_spanning tree on port ******************

Spanning tree configuration for device B:

configure bridge 1
port 1
spanning-tree
cost 654321
priority 160
no shutdown
exit
exit
port 2
spanning-tree
cost 65432
priority 80
no shutdown
exit
exit
port 6
spanning-tree
cost 66666
priority 176
no shutdown
exit all
Spanning tree configuration for device C:

configure bridge 1
port 1
spanning-tree
cost 55555
priority 64
no shutdown
exit
exit
port 2
spanning-tree
cost 666666
priority 96
no shutdown
exit all
Spanning tree configuration for device D:

configure bridge 1
port 1
spanning-tree
cost 333
priority 16
no shutdown
exit
exit
port 2
spanning-tree
cost 1

priority 48
no shutdown
exit
exit
port 4
spanning-tree
cost 22
priority 0
no shutdown
exit all
Example Defining Bridge

To configure bridge port:
Bridge port: 1
Port name: BridgePort1
Ingress-filtering: Enabled
Accept-frame-type: vlan-only
Port VID=5, Priority=5
ETX-1# configure bridge 1
ETX-1>config>bridge(1)# port 1
ETX-1>config>bridge(1)>port(1)# name BridgePort1
ETX-1>config>bridge(1)>port(1)# ingress-filtering
ETX-1>config>bridge(1)>port(1)# accept-frame-type vlan-only
ETX-1>config>bridge(1)>port(1)# pvid 5 priority 5
ETX-1>config>bridge(1)>port(1)# exit
To define VLAN:
VLAN ID: 5
name: VLAN5
tagged-egress: bridge port 2 and bridge port 3
untagged-egress: bridge port 4


ETX-1>config>bridge(1)# vlan 5
ETX-1>config>bridge(1)>vlan(5)# name VLAN5
ETX-1>config>bridge(1)>vlan(5)# tagged-egress 2..3
ETX-1>config>bridge(1)>vlan(5)# untagged-egress 4
ETX-1>config>bridge(1)>vlan(5)# exit
Displaying VLAN Members

To display VLAN members:
ETX-1>config>bridge(1)# show vlans
VLAN ID : 1 Name : VLAN 1
Tagged Ports : 0
Untagged Ports : 1..6
VLAN ID : 5 Name : VLAN5
Tagged Ports : 2..3

Untagged Ports : 4
Displaying MAC Address Table

To display mac address table:
ETX-1>config>bridge(1)# show mac-address-table all
Total MAC Addresses : 60
Static MAC Addresses : 0
Dynamic MAC Addresses : 60
VLAN MAC Address Port

-----------------------------------------------------------------------------
1 00-00-00-00-01-42 5 Dynamic
1 00-05-5D-67-C4-30 5 Dynamic
1 00-07-E9-19-C6-1E 5 Dynamic
1 00-09-0F-2E-7C-36 5 Dynamic
1 00-0C-76-AC-85-FF 5 Dynamic
1 00-0C-76-AC-89-22 5 Dynamic
1 00-0F-EA-B4-72-37 5 Dynamic
1 00-10-5C-E7-BB-1B 5 Dynamic
1 00-10-5C-EA-24-3E 5 Dynamic
1 00-10-5C-EA-29-5C 5 Dynamic
1 00-13-20-64-66-B4 5 Dynamic
1 00-13-C3-4F-61-80 5 Dynamic
1 00-14-78-1A-A6-2B 5 Dynamic
1 00-14-78-1A-A6-94 5 Dynamic
1 00-14-A4-59-1B-B7 5 Dynamic
1 00-19-E8-4D-A9-07 5 Dynamic
1 00-1F-D0-BB-FF-F3 5 Dynamic
1 00-20-D2-2E-CF-EE 5 Dynamic
1 00-20-D2-2F-0C-1D 5 Dynamic

1 00-20-D2-34-F0-A9 5 Dynamic
1 00-20-D2-35-1B-25 5 Dynamic
1 00-20-D2-36-9C-69 5 Dynamic
1 00-20-D2-50-17-56 5 Dynamic
1 00-24-1D-1D-7E-12 5 Dynamic
1 00-24-23-72-7F-0D 5 Dynamic
1 00-25-64-9A-C5-92 5 Dynamic
1 00-25-64-A3-25-D0 5 Dynamic
1 00-25-64-A7-54-91 5 Dynamic
1 00-25-64-B7-E8-99 5 Dynamic
1 00-25-64-C1-BB-08 5 Dynamic
1 00-25-64-C1-BB-EA 5 Dynamic
1 00-25-64-C2-34-10 5 Dynamic
1 00-25-64-C2-35-41 5 Dynamic
1 00-25-64-C2-3F-50 5 Dynamic
1 00-26-2D-F0-36-B5 5 Dynamic
1 00-30-18-A2-0D-87 5 Dynamic
1 00-50-56-E3-48-BB 5 Dynamic
1 02-50-56-C0-00-00 5 Dynamic
1 08-10-75-15-91-2B 5 Dynamic
1 0C-74-C2-ED-8D-97 5 Dynamic
1 40-16-9F-E1-CE-0E 5 Dynamic
1 44-2A-60-F5-46-EC 5 Dynamic
1 58-94-6B-84-C7-0C 5 Dynamic
1 5C-26-0A-47-B6-BF 5 Dynamic
1 5C-AC-4C-80-14-0F 5 Dynamic
1 78-A3-E4-73-D3-8E 5 Dynamic
1 7A-7A-C0-A8-D2-FE 5 Dynamic
1 8C-7B-9D-79-47-F6 5 Dynamic
1 BC-30-5B-AC-B4-AC 5 Dynamic
1 BC-30-5B-B6-C0-D9 5 Dynamic
1 BC-30-5B-B6-D1-51 5 Dynamic
1 BC-30-5B-B6-DC-21 5 Dynamic
1 BC-30-5B-B6-DD-C0 5 Dynamic
1 BC-30-5B-B6-DF-76 5 Dynamic
1 C8-3A-35-CC-F5-1F 5 Dynamic
1 C8-3A-35-D4-4A-D8 5 Dynamic
1 CC-08-E0-F6-7C-35 5 Dynamic
1 E0-05-C5-74-65-67 5 Dynamic
1 E0-05-C5-7B-E0-7B 5 Dynamic
1 F0-DE-F1-37-EB-EF 5 Dynamic
To clear mac address table:

1. Enter:
clear-mac-table
You are prompted to confirm the operation.
Learned entries within MAC table will be cleared. Are you sure?? [yes/no]
2. Type yes to confirm.
All MAC addresses are deleted.

8.3 Quality of Service (QoS)

The ETX-1 Quality of Service (QoS) parameters include the following profiles:
Queue map profiles
CoS map profiles
Bandwidth profiles
Queue block profiles
Queue group profiles.
These profiles can be applied to the traffic flows to ensure the desired flow
prioritization.
Standards
The following standards are supported:
IEEE 802.1p
IEEE 802.1Q.
Benefits
QoS allows you to optimize bandwidth, eliminating the need to ensure the
necessary bandwidth for traffic with different speed and quality requirements.
Factory Defaults
Refer to the following sections for the specific defaults of each type of QoS.
To differentiate traffic, the IEEE 802.1p standard specifies eight classes of service
per user-defined queue map profile. These classes of service are associated with
priority values, from 0 to 7, using the 3-bit user priority field in an IEEE 802.1Q
header added to VLAN-tagged frames within an Ethernet frame header. The way
traffic is handled when assigned a specific priority value is only generally defined
and left to implementation. The general definitions are as follows:
Table 8-1. User Priorities
User Priority Traffic Type
0 Best effort
1 Background
2 Spare
3 Excellent effort
4 Controlled load
8-16 Quality of Service (QoS) ETX-1 Ver. 1.2

User Priority Traffic Type
5 Video
6 Voice
7 Network control
Queue Mapping Profiles
Factory Defaults
Default Queue Mapping Profile

ETX-1 provides two default queue mapping profiles, named net-profile and user-
profile. ETX-1 supports these profiles only. They are defined by classification cos,
and cannot be modified. The mappings are shown in the following:
queue-map-profile "net-profile" classification cos
map 0 to-queue 0
map 1 to-queue 1
map 2 to-queue 2
map 3 to-queue 3
map 4 to-queue 4
map 5..7 to-queue 5
queue-map-profile "user-profile" classification cos
map 0 to-queue 0
map 1 to-queue 1
map 2 to-queue 2
map 3..7 to-queue 3
Configuring Queue Mappings

1. Navigate to config qos queue-map-profile <queue-mapping-profile-name> to
select the queue mapping profile to configure.
The following prompt is displayed:
config>qos>queue-map-profile(<queue-mapping-profile-name>)#.
2. Map the user priorities to queue IDs as necessary:
For net-profile, Classification CoS:
map <0-7> to-queue <0-5>
For user-profile, Classification CoS:
map <0-7> to-queue <0-3>
Note The second port has 6 queues and uses net-profile regardless of being a
network port or a user port.
ETX-1 Ver. 1.2 Quality of Service (QoS) 8-17

CoS Mapping Profiles

Class of Service (CoS) mapping profiles map the following user priorities to
internal CoS values.
p-bit, when the ingress traffic is prioritized according to the 802.1p
requirements
ip-dscp, when the ingress traffic is prioritized according to DSCP
Factory Defaults
By default, ETX-1 has two CoS mapping profiles, which are configured as follows:
cos-map-profile "pbit-profile" classification p-bit
map 0 to-cos 7
map 1 to-cos 6
map 2 to-cos 5
map 3 to-cos 4
map 4 to-cos 3
map 5 to-cos 2
map 6 to-cos 1
map 7 to-cos 0
cos-map-profile "dscp-profile" classification ip-dscp
map 0..7 to-cos 7
map 8..15 to-cos 6
map 16..23 to-cos 5
map 24..31 to-cos 4
map 32..39 to-cos 3
map 40..47 to-cos 2
map 48..55 to-cos 1
map 56..63 to-cos 0
Configuring CoS Mapping Profiles
To configure a CoS profile:

1. Navigate to the qos context (config>qos).
2. Define a CoS profile and assign a classification to it:
cos-map-profile <cos-mapping-profile-name> [classification {p-bit | ip-dscp}]
3. Map the user priority to a CoS value (user priority values 07 for p-bit, 063
for the other priority types; CoS values 07):
map <0-7> to-cos <0-7>
or

map <0-63> to-cos <0-7>
Note ETX-1 supports only two CoS mapping profiles pbit-profile and dscp-profile.
These profiles cannot be removed, but can be modified.
Example
To configure a CoS mapping profile named pbit-profile with classification p-bit:

Map priority 67 to CoS 0
Map priority 35 to CoS 1
Map priority 02 to CoS 2.
ETX-1# configure qos cos-map-profile pbit-profile classification p-bit
ETX-1>config>qos>cos-map-profile(pbit-profile)$ map 6..7 to-cos 0
ETX-1>config>qos>cos-mapping-profile(pbit-profile)# map 3..5 to-cos 1
ETX-1>config>qos>cos-mapping-profile(pbit-profile)# map 0..2 to-cos 2
ETX-1>config>qos>cos-mapping-profile(pbit-profile)# exit
ETX-1>config>qos#
Bandwidth Profiles
ETX-1 supports the following bandwidth profiles:
Shaper profile Applied to queue group or queue blocks
Policer profile Applied to flows
You can control the bandwidth utilization by defining the committed information
rate (CIR) and committed burst size (CBS) in shaper and policer profiles.
CIR: Defines the Committed Information Rate for the current profile. The CIR
specifies a bandwidth with committed service guarantee.
CBS: Defines the Committed Burst Size for the current profile. The CBS specifies
the maximum guaranteed burst size.
Compensation: You can specify the amount of bytes that the policer can
compensate for the layer 1 overhead (preamble and IFG) and the overhead for
the added VLAN header in case of stacking.
Factory Defaults
ETX-1 provides default bandwidth profiles, as specified in the following table.
Table 8-2. Default Bandwidth Profiles
Profile Type Shaper Policer
Profile Name Shaper1 Policer1
cir 1,000,000 1,000,000
cbs 524,288 524,288
compensation 0

Configuring Shaper Profiles

You can define up to 30 shaper profiles.
Adding Shaper Profiles

1. Navigate to configure qos.
The config>qos# prompt is displayed.
2. Type:
shaper-profile <shaper-profile-name>.
A shaper profile with the specified name is created and the
config>qos>shaper-profile(<shaper-profile-name>)$ prompt is displayed.
The new shaper profile parameters (except for name) are configured by
default, as described in Factory Defaults .
3. Configure the shaper profile as described in Configuring Shaper Profile
Parameters.
Configuring Shaper Profile Parameters

To configure shaper profiles:
1. Navigate to configure qos shaper-profile <shaper-profile-name> to select the
shaper profile to configure.
The config>qos>shaper-profile(<shaper-profile-name>)# prompt is
displayed.
Specifying the CIR bandwidth [cir <cir-kbit- no bandwidth removes the bandwidth limits
(kbps) and CBS sec>] [cbs {2048 |4096 | CIR allowed values: 321,000,000
(bytes) bandwidth 8192 | 16384 | 32768 |
The granularity is 32 kbps for CIR. If you specify a CIR
limits 131072 | 524288}]
that is not a multiple of 32 kbps, the device rounds it
down; for example if you specify 170 kbps, the device
operates as if you specified 160 kpbs.
Example
To create and configure a shaper profile named Shap2:

CIR = 99,968 Kbps
CBS = 32kbytes
ETX-1# configure qos shaper-profile Shap2
ETX-1>config>qos>shaper-profile(Shap2)$ bandwidth cir 99968 cbs 32768
ETX-1>config>qos>shaper-profile(Shap2)$
Note
No more than 28 shaper profiles and 32 policer profiles can be activated
simultaneously.

Configuring Policer Profiles

You can define up to 60 policer profiles.
Adding Policer Profiles

2. Type policer-profile <policer-profile-name>.
A policer profile with the specified name is created and the following
prompt is displayed:
config>qos>policer-profile(<policer-profile-name>)$.
The new policer profile parameters (except for name) are configured by
default, as described in Factory Defaults.
3. Configure the policer profile as described in Configuring Policer Profile
Parameters.
Configuring Policer Profile Parameters

1. Navigate to configure qos policer-profile <policer-profile-name> to select the
policer profile to configure.
The config>qos>policer-profile(<policer-profile-name>)# prompt is
displayed.
Specifying the CIR bandwidth [cir <cir-kbit-sec>] no bandwidth removes the bandwidth limits
(kbps) and CBS [cbs {4096 | 32768 | 131072 | CIR allowed values: 321,000,000
(kbytes) bandwidth 524288 | 2097152 | 8388608 |
The granularity is 32 kbps for CIR. If you specify a
limits 33554432}]
CIR that is not a multiple of 32 kbps, the device
rounds it down; for example if you specify
170 kbps, the device operates as if you specified
160 kpbs.
Specifying the compensation <063>

compensation (bytes)
Example
To create and configure a policer profile named Policer4:

CIR = 256 Kbps
CBS = 128 kbytes
Compensation = 56

ETX-1# configure qos policer-profile Policer4

ETX-1>config>qos>policer-profile(Policer4)$ bandwidth cir 256 cbs 131072
ETX-1>config>qos>policer-profile(Policer4)$ compensation 56
ETX-1>config>qos>policer-profile(Policer4)$ info detail
bandwidth cir 256 cbs 131072
compensation 56
ETX-1>config>qos>policer-profile(Policer4)$
Queue Block Profiles

To facilitate congestion management, you can sort traffic by applying queue block
profiles to queue block entities. A queue block profile contains entries for queues
05, with the following parameters:
Scheduling method:
Strict High-priority queues that are always serviced first. If a
lower-priority queue is being serviced and a packet enters a higher
queue, that queue is serviced immediately.
WRR (Weighted Round Robin) Using weights assigned to queues to
determine the number of frames to be sent from a queue before
moving to the next queue.
In configurations with Strict and WRR queues, the WRR frames are transmitted
only after the transmission of frames associated with the Strict queues is
completed.
Note If one of the internal queues is configured to WRR, queues with a higher queue ID
cannot be configured to Strict. Shaper per queue or per port cannot be set at the
same time.
Depth (queue length), in bytes.
Factory Defaults
ETX-1 provides a default queue block profile named DefaultQueue1, which
defines queues 05 as follows:
Scheduling method: WRR
Depth: 8192
Adding Queue Block Profiles

You can define up to 16 queue block profiles.
To add a queue block profile:

2. Type queue-block-profile <queue-block-profile-name>.
A queue block profile with the specified name is created and the
config>qos>queue-block-profile(<queue-block-profile-name>)$ prompt is
displayed. The queues for the new profile are configured by default as
described in Factory Defaults.

3. Configure the queue block profile as described in Configuring Queue Block

Profile Parameters.
Configuring Queue Block Profile Parameters

To configure a queue block profile:
1. Navigate to config qos queue-block-profile <queue-block-profile-name> to
select the queue block profile to configure.
The config>qos>queue-block-profile(<queue-block-profile-name>) $
prompt is displayed.
2. Perform the following for each queue that you wish to configure:
a. To configure a queue, enter:
queue <queue-id>.
config>qos>queue-block-profile(<queue-block-profile-name>)>queue(<queue-id>)#.
b. Enter all necessary commands according to the tasks listed below.
c. Type exit to return to the queue block profile context.
Setting scheduling method scheduling { strict | wrr <wrr-weight>} The weight range is 131
Specifying queue depth (in bytes) depth <value> The queue lengthes
cannot exceed 15360.
The depth granularity is
1024 bytes.
Assigning a shaper profile shaper profile <shaper-profile-name> This is used to define

shaping per queue
Example
To create and configure a queue block profile named QBlockProf1:

Queue 0 set to strict scheduling and depth 1024
Queue 1 set to WRR scheduling with weight 20.
ETX-1# configure qos queue-block-profile QBlockProf1
ETX-1>config>qos>queue-block-profile(QBlockProf1)$ queue 0
ETX-1>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ scheduling strict
ETX-1>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ depth 1024
ETX-1>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ exit
ETX-1>config>qos>queue-block-profile(QBlockProf1)# queue 1
ETX-1>config>qos>queue-block-profile(QBlockProf1)>queue(1)# scheduling wrr 20
ETX-1>config>qos>queue-block-profile(QBlockProf1)>queue(1)#
Queue Group Profiles

To facilitate congestion management, you can sort traffic by applying one queue
group profile per network or user port. You can define up to 16 queue group
profiles per ETX-1 unit.

Adding Queue Group Profiles
To add a queue group profile:

2. Type:
queue-group-profile <queue-group-name>.
A queue group profile with the specified name is created and the
config>qos>queue-group-profile(<queue-group-name>)$ prompt is
displayed.
3. Configure the queue group profile as described in Configuring Queue Group
Parameters.
Configuring Queue Group Parameters

To configure a queue group profile:
1. Navigate to config qos queue-group-profile < queue-group-name> to select
the queue group profile to configure.
The config>qos>queue-group-profile(<queue-group-name>) $ prompt is
displayed.
2. Select a queue block in level 0 to configure:
queue-block 0/1
config>qos>queue-group-profile(<queue-group-name>)>queue-block(<level_id/que
ue_id>)#.
Assigning a name to the queue block name <block-name>
Assigning a queue block profile profile <queue-block-profile-name>
Assigning a shaper profile shaper profile <shaper-profile-name> Only for queue blocks in
level 0. This is used to define
shaping per port.
Note
Normally there is no need for you to enter the bind command. When you add a
queue block in level 0 to the profile, bind is done automatically.
Example
Note This example uses the shaper profile and queue block profile created in the
examples in the preceding sections.
To create and configure a queue group profile named QGroupProf1:

Queue block 0/1:
Queue block profile: QBlockProf1

Shaper profile: Shap2.

ETX-1# configure qos queue-group-profile QGroupProf1
ETX-1>config>qos>queue-group-profile(QGroupProf1)$ queue-block 0/1
ETX-1>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ profile
QBlockProf1
ETX-1>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ shaper
profile Shap2
ETX-1>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ exit
ETX-1>config>qos>queue-group-profile(QGroupProf1)$ info detail
queue-block 0/1
name "Put your string here"
profile "QBlockProf1"
shaper profile "Shap2"
exit
8.4 Flows
ETX-1 supports up to 32 unidirectional Ethernet flows, which can be used to
provide E-Line or E-LAN service delivery over Metro Ethernet networks. Each
Ethernet flow is unidirectional and connects two ports.
This section explains how to define the flows according to specific criteria such as
VLAN. You can use classifier profiles to specify the criteria for flows. The
classification is per port and is applied to the ingress port of the flow.
Note For P2MP flow, note the following configuration:

1. When ETH port is set as ingress port and bridge port is set as egress port,
this flow is considered the master flow. The actions (such as drop, mark,
vlan-tag and policer) should be configured on this flow.
2. When bridge port is set as ingress port and ETH port is set as egress port,
this flow is considered the slave flow. The action is not configured because it
is determined by the master flow. The configured classifier must be same as
master flow.
3. If the master flow is deleted, then P2MP flow is invalid.
Standards
IEEE 802.3x
Benefits
The user traffic can be classified into different Ethernet flows (EVC.CoS) to
provide services in a flexible manner.
Packets can be classified by means of their VLAN IDs and other criteria, as
specified in Table 8-3.
ETX-1 Ver. 1.2 Flows 8-25

Classifications that apply to the same port are allowed only one or one same
combination. NNI indicates ingress network port, UNI indicates ingress user port.
Table 8-3. Classifications
Classification Range NNI/UNI
vlan 04094 Both
p-bit 07 Both
ip-precedence 07 Both
ip-dscp 063 Both
src-mac MAC address Both
src-mac + to-src-mac (Source MAC address to MAC address Both

source MAC address)
dst-mac MAC address Both
dst-mac +to-dst-mac (Destination MAC address to MAC address Both

destination MAC address)
src-ip IP address Both
src-ip + to-src-ip (Source IP address to source IP IP address Both

address)
dst-ip IP address Both
dst-ip + to-dst-ip (Destination IP address to IP address Both

destination IP address)
ether-type 0x0000-0xffff Both
untagged - Both
non-ip - Both
all - Both
vlan + inner-vlan Single value (0-4094) for VLAN and range Both
(0-4094) for inner VLAN
vlan + p-bit 0-4094 Both

0-7
vlan + ip-dscp 0-4094 Both

0-63
vlan + src-mac 0-4094 Both

MAC address
vlan + dst-mac 0-4094 Both

MAC address
vlan + src-ip 0-4094 Both

IP address
8-26 Flows ETX-1 Ver. 1.2

Classification Range NNI/UNI
vlan + dst-ip 0-4094 Both

IP address
vlan + ether-type 0-4094 Both

0x0000-0xffff
vlan + non-ip 0-4094 Both
vlan + src-ip + to-src-ip 0-4094 Both

IP address
vlan +dst-ip + to-dst-ip 0-4094 Both

IP address
vlan +src-mac + to-src-mac 0-4094 Both

MAC address
vlan +dst-mac + to-dst-mac 0-4094 Both

MAC address
vlan + inner-vlan + p-bit Single value(0-4094) for VLAN, range (0- Both
4094) for inner VLAN
0-7 for p-bit
vlan + ip-precedence 0-4094 Both

0-7

Note The VLAN may be a single value or a range for setting a classification or the same
combination classification. When setting the same combination classification with
VLAN and inner VLAN, the VLAN should be a single value.
The p-bit may be a single value or a range for setting a classification or the same
combination classification. When setting p-bit range, it should contain all values,
the following is valid: p-bit range: 0..7
The ip-precedence may be a single value or a range for setting a classification or
the same combination classification. When setting ip-precedence range, it should
contain all values, the following is valid: ip-precedence range: 0..7
The ip-dscp may be a single value or a range for setting a classification or the
same combination classification. When setting ip-dscp range, it should contain all
values, the following is valid: ip-dscp range: 0..63
If you apply the same combination classification with IP address range, the
following is valid:
1. For IP address range: the starting IP address is X.X.0.0, the end address is
X.X.255.255 or the starting IP address is X.X.X.0, the end address is X.X.X.255
2. The starting address and the end address must be in the same subnet.
For example:
IP address range: 10.10.10.0 10.10.10.255; If you apply the same combination
classification with MAC address range, the following is valid:
1. For MAC address range: the starting MAC address is XX-XX-XX-00-00-00, the
end address is XX-XX-XX-FF-FF-FF or the starting MAC address is XX-XX-XX-XX-
00-00, the end address is XX-XX-XX-XX-FF-FF or the starting MAC address is XX-
XX-XX-XX-XX-00, the end address is XX-XX-XX-XX-XX-FF
2. The prefix of the starting MACaddress and the end MACaddress must be same.
For example: IP address range: 66-66-66-66-66-00 66-66-66-66-66-FF
ETX-1 supports up to 32 Ethernet flows. Flows are unidirectional. One Ethernet
port can support one or same type classification combination. Two different flow
classification combinations are not allowed, except VLAN and untagged, IP and
non-IP.
When you configure the flow, if QinQ status is disabled (configure>bridge 1>port
(port-number)>no ingress-tag), please perform the VLAN action according to the
following rules:
Table 8-4, Table 8-5 and Table 8-6 show valid action combination rules on ingress
frame tags and the resulting egress frame tags and p-bits, according to whether
the ingress frame is untagged, contains one VLAN, or is double-tagged.
Note means this type is not supported.
When you configure the flow, if QinQ status is disabled (configure>bridge 1>port
(port-number)>no ingress-tag), please perform the VLAN action according to the
following rules:

Table 8-4. Valid VLAN Action Combination Rules
Action on Egress VLAN(s) and P-bit(s) for Ingress Frame Types

Outer VLAN Innner VLAN Untagged One VLAN(X) Double VLANS
(X and Y)
None None Untagged X X,Y

None Mark with Inner-Vlan B X,B
None Mark with Inner- p-bit X
D Y + p-bit D
None Mark with Inner-Vlan B X
+ Inner- p-bit D B + p-bit D
Pop None Untagged Y
Pop Mark with Inner-Vlan A A
Pop Mark with Inner-Vlan B B + p-bit D
and Inner- p-bit D
Pop Mark with Inner- p-bit Y + p-bit D
D
Pop Pop Untagged
Push Vlan A None A
Push Vlan A Mark with Inner-Vlan B A
B (ingress
ports default
priority)
+ Inner-p-bit D B+p-bit D
Push Vlan A Push Inner-Vlan B A

B
Mark with None A A,
Vlan A Y
Mark with Mark with inner-Vlan B A
Vlan A B
Mark with Mark with Inner- p-bit A
Vlan A D Y+p-bit D
Mark with Mark with Inner- Vlan A
Vlan A B B+ p-bit D
+ Inner-p-bit D
Mark with None X+p-bit C X+p-bit C
p-bit c Y

Mark with Mark with inner-Vlan B X+p-bit C

p-bit c B
Mark with Mark with Inner- p-bit X+ p-bit C
p-bit c D Y+p-bit D
Mark with Mark with inner-Vlan B X+ p-bit C
p-bit c + Inner- p-bit D B+p-bit D
Mark with None A+p-bit C A+p-bit C
Vlan A Y
+ p-bit c
Mark with Mark with inner-Vlan B A+p-bit C
Vlan A B
+ p-bit c
Mark with Mark with Inner- p-bit A+p-bit C
Vlan A D Y+p-bit D
+ p-bit c
Mark with Mark with inner-Vlan B A+ p-bit C
Vlan A + Inner- p-bit D B+p-bit D
+ p-bit c
When you configure the flow, if QinQ status is enabled (configure>bridge 1>port
(port-number)>ingress-tag) and the flow direction is from net port to user port,
please perform the VLAN action according to the following rules:
Note means this type is not supported.
Table 8-5. Valid VLAN Action Combination Rules
Action on Egress VLAN(s) and P-bit(s) for Ingress Frame

Types
Outer VLAN Inner VLAN Untagged One VLAN(X) Double
S VLANS
(S and C)
None None Untagged Untagged C

Pop None Untagged C
None Mark with Inner-Vlan B B B
None Mark with Inner- p-bit D C + p-bit D
None Mark with Inner-Vlan B + B + p-bit D B + p-bit D
Inner- p-bit D
Pop Mark with Inner-Vlan AB B B
Pop Mark with Inner- p-bit D C + p-bit D
Pop Pop Untagged
Pop Mark with Inner-Vlan B + B + p-bit D B + p-bit D

Inner- p-bit D
When you configure the flow, if QinQ status is enabled (configure>bridge 1>port
(port-number)>ingress-tag) and the flow direction is from user port to net port,
please perform the VLAN action according to the following rules:
Note The stag-packet is considered untagged packet.

If the TPID of the packet is 0x8100, it is a C-tag packet
means this type is not supported.
Table 8-6. Valid VLAN Action Combination Rules-3
Action on Egress VLAN(s) and P-bit(s) for Ingress Frame Types

Outer VLAN Inner VLAN Untagged One VLAN
CE-VLAN(C)
None None PVID PVID

C
None Mark with Inner-Van B PVID

B
None Mark with Inner- p-bit D PVID

C + p-bit D
None Mark with Inner-Vlan B + PVID

Inner- p-bit D B + p-bit D
Push Vlan A None A A ,C
Push Vlan A Mark with Inner-Vlan B A,B
Push Vlan A Mark with Inner- p-bit D A
C + p-bit D
+ Inner-p-bit D B+p-bit D
Push Vlan A Push Inner-Vlan B A,B
Factory Defaults
By default, no flows exist.
Defining Classifier Profiles

You can define up to 64 classifier profiles to apply to flows to ensure the desired
flow classification.
To define a classifier profile:

1. Navigate to the flows context (config>flows).
2. Define a classifier profile and assign a name to it:

classifier-profile <classification-name> match-any

The system switches to the context of the classifier profile
(config>flows>classifier-profile(<classification-name>)).
3. Specify the criteria for the classifier profile:
[no] match [vlan <vlan-range>] [inner-vlan <inner-vlan-range>]
[p-bit <p-bit-range>] [ip-precedence <ip-precedence-range>]
[ip-dscp <ip-dscp-range>] [src-mac <src-mac-low>] [to-src-mac
<src-mac-high>] [dst-mac <dst-mac-low>] [to-dst-mac <dst-mac-
high>] [src-ip <ip-address>] [to-src-ip <ip-address>] [dst-ip
<ip-address>] [to-dst-ip <ip-address>] [ether-type <ether-
type>] [untagged] [non-ip] [all]
4. When you finish specifying the criteria, enter exit to exit the classifier profile
context.
Example Defining Classifier Profiles

To create classifier profile with criteria VLAN 100 to VLAN 150:
ETX-1# configure flows classifier-profile v100_150 match-any
ETX-1>config>flows>classifier-profile(v100_150)$ match vlan 100..150
ETX-1>config>flows>classifier-profile(v100_150)$ exit all
ETX-1#
To create classifier profile with criteria VLAN 20 and inner VLAN 30:
ETX-1# configure flows classifier-profile v20_inner_30 match-any
ETX-1>config>flows>classifier-profile(v20_inner_30)$ match vlan 20 inner-vlan
30
ETX-1>config>flows>classifier-profile(v20_inner_30)$ exit all
ETX-1#
To create classifier profile that matches all criteria:

ETX-1# configure flows classifier-profile all match-any
ETX-1>config>flows>classifier-profile(all)$ match all
ETX-1>config>flows>classifier-profile(all)$ exit all
ETX-1#
To create classifier profile with criteria Ethertype 0x8100:

ETX-1# configure flows classifier-profile e8100 match-any
ETX-1>config>flows>classifier-profile(e8100)$ match ether-type 0x8100
ETX-1>config>flows>classifier-profile(e8100)$ exit all
ETX-1#
Configuring Flows
To configure flows:
1. Navigate to config>flows.
2. Enter flow <flow-name>.

If the flow already exists, the config>flows>flow(<flow-name>)# prompt

is displayed; otherwise the flow is created and the
config>flows>flow(<flow-name>)# prompt is displayed.
Associating the flow with a classifier <classification-name>

classifier profile
Specifying the ingress port ingress-port ethernet <port>

ingress-port bridge-port <port-number>
ingress-port svi <port-number>
Specifying the egress port, egress-port ethernet <port> [queue If a queue mapping profile is used, it
and defining its queues <queue-id> block <level_id/queue_id>] must be compatible with the
egress-port ethernet <port> [queue- classification criteria of the flow;
map-profile <queue-map-profile-name> e.g., if the classification is according
block <level_id/queue_id>] to DSCP, then the queue mapping
should not be according to p-bit.
egress-port bridge-port <port-number>
For network port, the range of
egress-port svi <port-number> [queue
<queue-id> is 05. For user port,
<queue-id>]
the range of <queue-id> is 03.
egress-port svi <port-number> [queue-
map-profile <queue-map-profile-
name>]
Adding VLAN ID with p-bit vlan-tag push vlan <sp-vlan> p-bit fixed
set to specific value, and <fixed-p-bit> [inner-vlan <inner-sp-vlan>
optionally adding inner p-bit fixed <inner-fixed-p-bit>]
VLAN ID with p-bit set to
specific value
Removing VLAN ID, and vlan-tag pop [vlan] [inner-vlan]

optionally removing inner
VLAN ID
Removing VLAN no vlan-tag
Associating the flow with a policer profile <policer-profile-name>

policer profile
Discarding traffic drop

transmitted via the flow
Administratively enabling no shutdown You can activate a flow only if it is

the flow associated with at least a classifier
profile, ingress port, and egress
port.
Flows are created as inactive by
default.
shutdown disables the flow.
The following marking actions can be performed in the mark level, at the
config>flows>flow(<flow-name>)>mark# prompt.

Overwriting VLAN ID with a new vlan <vlan> no vlan removes the overwriting of VLAN
value ID
Overwriting inner VLAN ID with a inner-vlan <inner-vlan> no inner-vlan removes the overwriting of
new value inner VLAN ID
Overwriting p-bit with a new value p-bit <p-bit> no p-bit removes the overwriting of p-bit
Overwriting inner p-bit with a new inner-p-bit <inner-p-bit> no inner-p-bit removes the overwriting of
value inner p-bit
Example Defining flows

This section presents an example of configuring the following flows (this example
assumes the QinQ status is disabled) and the configuration steps are shown in
the following:
Outgoing traffic from user port ETH 3 to network port ETH 1:
Accept only traffic tagged with VLAN 10
Mark inner vlan 5 and add VLAN 100 with p-bit 5 (this causes VLAN 100 to be
the outer VLAN and VLAN 5 to be the inner VLAN).
Incoming traffic from network port ETH 1 to user port ETH 3:
Accept only traffic tagged with VLAN 100 and inner VLAN 10
Remove the outer VLAN (VLAN 100).
To configure the outgoing flow:

1. Set up a classifier profile to forward frames from VLAN 10:
ETX-1# configure flows
ETX-1>config>flows# classifier-profile v10 match-any
ETX-1>config>flows>classifier-profile(v10)$ match vlan 10
ETX-1>config>flows>classifier-profile(v10)$ exit all
ETX-1#
2. Set up a flow using the previously defined classifier profile, with ingress at
ETH 3 and egress at ETH 1, and pushing VLAN 100 with p-bit 5:
ETX-1>config>flows# flow f10_out
ETX-1>config>flows>flow(f10_out)$ classifier v10
ETX-1>config>flows>flow(f10_out)$ ingress-port ethernet 3
ETX-1>config>flows>flow(f10_out)$ egress-port ethernet 1 queue 0 block 0/1
ETX-1>config>flows>flow(f10_out)$ mark all
ETX-1>config>flows>flow(f10_out)>mark$ inner-vlan 5
ETX-1>config>flows>flow(f10_out)>mark$ exit
ETX-1>config>flows>flow(f10_out)$ vlan-tag push vlan 100 p-bit fixed 5
ETX-1>config>flows>flow(f10_out)$ no shutdown
ETX-1>config>flows>flow(f10_out)$ exit all
ETX-1#

To configure the incoming flow:

1. Set up a classifier profile to forward frames from VLAN 100 and inner
VLAN 10:
ETX-1>config>flows# classifier-profile v100_inner_v10 match-any
ETX-1>config>flows>classifier-profile(v100_inner_v10)$ match vlan 100
inner-vlan 10
ETX-1>config>flows>classifier-profile(v100_inner_v10)$ exit all
ETX-1#
ETH 1 and egress at ETH 3, and popping the outer VLAN:
ETX-1>config>flows# flow f100_in
ETX-1>config>flows>flow(f100_in)$ classifier v100_inner_v10
ETX-1>config>flows>flow(f100_in)$ ingress-port ethernet 1
ETX-1>config>flows>flow(f100_in)$ egress-port ethernet 3 queue 0 block 0/1
ETX-1>config>flows>flow(f100_in)$ vlan-tag pop vlan
ETX-1>config>flows>flow(f100_in)$ no shutdown
ETX-1>config>flows>flow(f100_in)$ exit all
ETX-1#

Example Displaying Flow Summary

To display the flow summary above:
ETX-1>config>flows# show summary
Name : f10_out
Admin Status : Up
Oper Status : Up
Test : Off
Classifier : v10
Ingress Port : Ethernet

Egress Port : Ethernet
Name : f100_in
Admin Status : Up
Oper Status : Up
Test : Off
Classifier : v100_inner_v10
Ingress Port : Ethernet

Egress Port : Ethernet
Example Defining P2MP Flows

This section presents an example of configuring the P2MP flows:
Master flow from user port ETH 3 to bridge port 3:
classifier profile v100 with criteria VLAN 100
Slave flow from bridge port 1 to net port ETH 1, and bridge port 5 to user
port ETH 5:
Configure the same classifier profile v100
To configure the master flow:

1. Set up a classifier profile to forward frames from VLAN 100:
ETX-1>config>flows# classifier-profile v100 match-any
ETX-1>config>flows>classifier-profile(v100)$ match vlan 100
ETX-1>config>flows>classifier-profile(v100)$ exit all
ETX-1#

ETH 3 and egress at bridge port 3:
ETX-1>config>flows# flow master_flow
ETX-1>config>flows>flow(master_flow)$ classifier v100
ETX-1>config>flows>flow(master_flow)$ ingress-port ethernet 3
ETX-1>config>flows>flow(master_flow)$ egress-port bridge-port 3
ETX-1>config>flows>flow(f10_out)$ no shutdown
ETX-1>config>flows>flow(f10_out)$ exit all
ETX-1#
To configure the slave flow:

bridge port 1 and egress at ETH 1:
ETX-1>config>flows# flow slave_flow1
ETX-1>config>flows>flow(slave_flow1)$ classifier v100
ETX-1>config>flows>flow(slave_flow1)$ ingress-port bridge-port 1
ETX-1>config>flows>flow(slave_flow1)$ egress-port ethernet 1 queue 1 block
0/1
ETX-1>config>flows>flow(slave_flow1)$ no shutdown
ETX-1>config>flows>flow(slave_flow1)$ exit all
ETX-1#
bridge port 5 and egress at ETH 5:
ETX-1>config>flows# flow slave_flow2
ETX-1>config>flows>flow(slave_flow2)$ classifier v100
ETX-1>config>flows>flow(slave_flow2)$ ingress-port bridge-port 5
ETX-1>config>flows>flow(slave_flow2)$ egress-port ethernet 5 queue 1 block
0/1
ETX-1>config>flows>flow(slave_flow2)$ no shutdown
ETX-1>config>flows>flow(slave_flow2)$ exit all
ETX-1#
8.5 Ethernet OAM

Ethernet OAM (operation, administration, and maintenance) functions provide
end-to-end connectivity checks and performance monitoring.
OAM CFM (Connectivity Fault Management)

Ethernet Connectivity Fault Management (CFM) is a service-level OAM protocol
that provides tools for monitoring and troubleshooting end-to-end Ethernet
services. This includes proactive connectivity monitoring, fault verification, and
fault isolation. CFM uses standard Ethernet frames and can be run on any
physical media that can transport Ethernet service frames.
ETX-1 can act as a Maintenance Entity Group Intermediate Point (MIP) or
Maintenance Entity Group End Point (MEP). If ETX-1 is acting as a MIP, it forwards
ETX-1 Ver. 1.2 Ethernet OAM 8-37

OAM CFM messages transparently, responding only to OAM link trace (LTM) and
unicast OAM loopback (LBM). MIPs can be configured automatically or manually.
Standards
IEEE 802.1ag, ITU-T Y.1731
Benefits
Ethernet service providers can monitor their services proactively and guarantee
that customers receive the contracted SLA. Fault monitoring and end-to-end
performance measurement provide tools for monitoring frame delay, frame delay
variation, and frame loss and availability.
OAM enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM
functionality ensures that network operators comply with QoS guarantees, detect
anomalies before they escalate, and isolate and bypass network defects. As a
result, operators can offer binding service-level agreements.
In packet-switched networks, ETX-1 provides the following OAM (CFM) functions:
End-to-end Connectivity Fault Management (CFM) per IEEE 802.1ag:
Continuity check (CC)
Non-intrusive loopback, used to detect loss of bidirectional continuity
Link Trace for fault localization
End-to-end service and performance monitoring per ITU-T Y.1731:
Loss measurement
Delay measurement
Note OAM messages are always mapped to the queue with the lowest priority.
The device supports:

Up to 64 maintenance domains (MDs)
Up to 64 maintenance associations (MAs)
Up to 64 maintenance endpoints (MEPs)
Up to 100 remote MEPs.
Up to 100 services. Up to eight services can be configured for a MEP.
Up to 100 destination NEs. One destination NE can be configured for a
service.
To configure the service OAM:
1. Configure general OAM parameters
2. Add and configure maintenance domain(s) (MD)
3. Configure maintenance associations (MA) for the added MDs
8-38 Ethernet OAM ETX-1 Ver. 1.2

4. If ETX-1 is acting as a MIP, with automatic MIP configuration:

a. Configure the necessary flows from and to the unit(s) acting as MEP(s).
b. Configure the MA classification to correspond to the flows.
c. Configure the MIP policy (refer to Configuring MIP Automatically for an
example of MIP configuration).
5. If ETX-1 is acting as a MIP, with manual MIP configuration, then configure the
necessary MIPs.
6. If ETX-1 is acting as a MEP:
a. Configure MA endpoints, referred as MEPs.
b. Configure MEP services.
c. Configure Destination NEs.
Factory Defaults
By default, there are no MDs, MAs, or MEPs.
The default MIP configuration mode is manual.
When a maintenance domain is created, it has the following default
configuration.
Parameter Default Remarks
md-level 3
name string "MD<mdid>" For example, the default name for maintenance
domain 1 is MD1.
When a maintenance association is created, it has the following default

configuration.
ccm-interval 1s Continuity check interval is 1 second
classification vlan 0
mip-policy no mip-policy Relevant only if MIP assignment is set to automatic
name string "MA<maid>" For example, the default name for maintenance
association 1 is MA1.
When a maintenance endpoint is created, it has the following default

configuration.
bind no bind
client-md-level 4
queue fixed 0 block 0/0

dest-addr-type ccm multicast pm unicast Destination address type for CCM messages
multicast
Destination address type for performance
measurement messages unicast
ccm-initiate ccm-initiate Initiate continuity check messages
direction down
ccm-priority 0
ais no ais
shutdown shutdown Administratively disabled
When a service is created, it has the following default configuration.
delay-threshold 10 1 msec (the unit is 0.1 msec)
delay-var-threshold 10 1 msec (the unit is 0.1 msec)
classification priority-bit 0
dmm-interval 1s
lmm-interval 1s
shutdown shutdown Administratively disabled
When a destination NE is created, it has the following default configuration.
remote mac-address
00-00-00-00-00-00
delay two-way data-tlv-length 0
loss single-ended synthetic
Configuring OAM CFM General Parameters

If necessary you can define general OAM CFM parameters. You can also display
OAM CFM information.
Setting MIP Configuration Mode

You can specify whether MIPs are automatically created according to MIP policy,
or MIPs are manually configured.
To set the MIP configuration mode:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
2. Do one of the following:

To specify automatic MIP creation, enter: mip-assign automatic.

Manually created MIPs are deleted. MIPs are now automatically created
according to MIP policy.
To specify manual MIP creation, enter: mip-assign manual.
Automatically created MIPs are deleted. The manual MIP configuration
commands are available.
Displaying OAM CFM Information

You can display OAM CFM information by typing show summary, as
shown in the following.
ETX-1# configure oam cfm
ETX-1# config>oam>cfm# show summary
md slot/ classifi admin ok/total
md/ma/mepid md/ma name lvl port cation status r.meps
001/001/001 MD1/MA1 3 eth3 100 enable off 0/1
You can display information on MIPs by typing show mips (refer to
Configuring MIP for an example).
Configuring Maintenance Domains

MDs are domains for which the connectivity faults are managed. Each MD must
be assigned a name that is unique among all those used or available to an
operator. The MD name enables easy identification of administrative
responsibility for the maintenance domain.
To add a maintenance domain:
At the config>oam>cfm# prompt enter:
maintenance-domain <mdid>
where <mdid> is 164.
The maintenance domain is created and the
config>oam>cfm>md(<mdid>) # prompt is displayed.
To delete a maintenance domain:

At the config>oam>cfm# prompt enter:
no maintenance-domain <mdid>
The maintenance domain is deleted.
To configure a maintenance domain:
1. Navigate to configure oam cfm maintenance-domain <mdid> to select the
maintenance domain to configure.
The config>oam>cfm>md(<mdid>)# prompt is displayed.

Configuring maintenance-association Refer to Configuring Maintenance Associations

maintenance <maid>
association for the
MD
Specifying the md-level <md-level> The allowed range for md-level is 07

maintenance domain
level
Defining MIP policy mip-policy {explicit | default} Refer to the explanation of MIP policy in Configuring
Maintenance Associations for a description of the
parameters. You do not need to configure the MIP
policy at the MD level, unless the MIP policy in the MA
level is set to defer
Note: This command is available only if mip-assign is
set to automatic.
Specifying the name name string Maximum length of md-name-string is

format and name of <md-name-string> 43 characters
the maintenance name dns <md-name-string> Maximum combined length of md-name-string and
domain ma-name-string (maintenance association name)
name mac-and-uint
<md-name-mac> is 44 characters
<md-name-uint> Format mac-and-uint Specify md-name-mac as
no name xx-xx-xx-xx-xx-xx, and md-name-uint as an
unsigned integer decimal number (065535)
Configuring Maintenance Associations

A maintenance domain contains maintenance associations.
To add a maintenance association (MA):
At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance- association <maid>
where <maid> is 164.
The maintenance association is created and the
config>oam>cfm>md(<mdid>)>ma(<maid>)$ prompt is displayed.
To delete a maintenance association:

At the config>oam>cfm>md(<mdid>)# prompt enter:
no maintenance-association <maid>
The maintenance association is deleted.
To configure a maintenance association:

1. Navigate to configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> to select the maintenance association to
configure.
The config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt is displayed.

Specifying the interval ccm-interval {10ms | 100ms |

between continuity 1s | 10s | 1min | 10min}
check messages
Associating the MA with classification vlan <vlan-id> Verify that the VLAN is the same as the VLAN
a VLAN associated with the MEP.
Note: If a classifier profile is associated with at the
MEP, the VLAN should be set to 0.
Configuring MEP for the mep <mepid> Refer to Configuring Maintenance Endpoints
MA
Defining MIP policy mip-policy Explicit MIP is automatically created for ports
{explicit | default | defer} corresponding to VLAN classification of MA, only
if a corresponding MEP exists at a lower MD
level
Default MIP is automatically created for ports
corresponding to VLAN classification of MA
Defer MIP policy is inherited from the MD MIP
policy.
Note: This command is available only if MIP
assignment is set to automatic.
Specifying the name name string Maximum length of ma-name-string is

format and name of the <ma-name-string> 43 characters
maintenance name primary-vid Maximum combined length of md name string
association <ma-name-vid> and ma name string is 44 characters
name uint <ma-name-uint> Format primary-vid Specify ma-name-vid as
name icc <ma-name-icc> 14094
Format uint Specify ma-name-uint as an
unsigned integer decimal number (065535)
Format icc Specify ma-name-icc as the ITU
carrier code that is assigned to the relevant
network operator/service provider. The codes
are maintained by ITU-T as defined in ITU-T Rec.
M.1400
Note: If the icc option is selected, the maintenance
domain must have no name (use command no
name).
Configuring Maintenance Endpoints

Maintenance endpoints reside at the edge of a maintenance domain. They initiate
and respond to CCMs, linktrace requests, and loopbacks to detect, localize, and
diagnose connectivity problems.
Note For every MEP, you must configure a flow with the same classification as the MEP.

To add a maintenance endpoint (MEP):

At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
mep <mepid>
where <mepid> is 18191.
The MEP is created and the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# is displayed.
To delete a maintenance endpoint:

At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
no mep <mepid>
The maintenance endpoint is deleted.
To configure a maintenance endpoint:

maintenance-association <maid> mep <mepid>to select the maintenance
endpoint to configure.
The prompt config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
is displayed.
Enabling initiation of ccm-initiate no ccm-initiate disables initiation of continuity

continuity check check messages
messages (CCM)
Defining sending of AIS ais [interval {1s | 1min}]

[priority <priority>]
Binding the MEP to an bind ethernet <port> To unbind the MEP, enter no bind
Ethernet port
Specifying the priority of ccm-priority <priority> The allowed range for <priority> is 07
CCMs and LTMs
transmitted by the MEP
Associating the MEP with classification vlan <vlan-id> Verify that the VLAN is the same as the VLAN
a classifier profile or classification profile associated with the MA
VLAN <profile-name>
Defining client MD level client-md-level <md-level>

Defining the MAC dest-addr-type [ccm If the MAC address type for PM messages is
address type sent in {unicast|multicast}] unicast, then the MAC address for the
OAM continuity check [pm {unicast|multicast}] transmission of PM messages is determined by
messages (CCM) and the configuration of the destination NE. If a
performance remote MAC address is configured for the
measurement messages destination NE, that MAC is used. Otherwise if
(PM) a remote MEP ID is configured for the
destination NE, the remote MAC address is
learned from CCM messages. Refer to
Configuring Destination NEs for details.
Defining a unicast MAC dest-mac-addr <mac-addr> MAC address is in format xx-xx-xx-xx-xx-xx
address if you defined
unicast MAC address
type for CCM messages
with the dest-addr-type
command
Defining direction direction {up | down}
Defining the queue for queue fixed <queue-id>

the MEP [block <level-id>/<queue-id>]
queue queue-mapping
<queue-map-profile-name>
[block <level-id>/<queue-id>]
Defining remote MEP remote-mep <remote-mep-id> Allowed range for remote MEP is 18191
with which the MEP The MEP ID and the remote MEP ID must be
communicates different. You can define up to 100 remote
MEPs for the local MEP if the destination
address type is multicast, otherwise you can
define only one remote MEP.
Configuring service for service <serviceid> Refer to Configuring Maintenance Endpoint

the MEP Services
Displaying MEP status show status
Displaying remote MEP show remote-mep

status <remote-mep-id> status
Administratively enabling no shutdown shutdown deactivates the MEP

MEP
Configuring Maintenance Intermediate Points Manually

If you wish to configure MIPs manually, you must first configure MIP assignment
to manual mode (refer to Setting MIP Configuration Mode). When a MIP is
configured manually, it must be bound to an Ethernet port with the flow.
To add a MIP:
At the config>oam>cfm>md(<mdid># prompt, enter:
mip <mip-id>.

The MIP is created and the prompt

config>oam>cfm>md(<mdid>)>mip(<mip-id>)$ is displayed.
To delete a MIP:
At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mip-id>
The maintenance intermediary point is deleted.
To configure a MIP:
1. Navigate to configure oam cfm maintenance-domain <mdid> mip <mip-id> to
select the MIP to configure.
The config>oam>cfm>md(<mdid>)>mip(<mip-id>)# prompt is displayed
Binding the MIP to an bind ethernet <port> To unbind the MIP, enter no bind
Ethernet port
Assigning unidirectional Rx flow uni-direction rx <rx-name> tx <rx-name> Rx flow name

and Tx flows to the MIP <tx-name> <rt-name> Tx flow name
To delete flow assignment, enter no flow
uni-direction
Note: The rx flow must originate from the
bound port
Administratively enabling no shutdown To deactivate the MIP, enter shutdown

MIP
Configuring Maintenance Intermediate Points Automatically
To configure a MIP:
Configure MIP assignment to automatic (refer to Setting MIP Configuration
Mode).
Verify that you have flows configured between ETX-1 and the device(s)
acting as MEP(s) (refer to Flows for information on defining flows).
Configure the MA classification to the same classification that is used by the
flows.
Configure MIP policy to default.
Examples
Configuring MD, MA, and MEP
To configure MD, MA, and MEP:

MD ID 1
MA ID 1
Classification VLAN 100 (MA classification must be consistent with the
same classification that is used by the flows)

MEP ID 1:
Bind Ethernet 1 (The bound Ethernet port must be the port that is used
by the flows)
Remote MEP ID 2
Classification VLAN 100.


ETX-1>config>oam>cfm# maintenance-domain 1
ETX-1>config>oam>cfm>md(1)$ maintenance-association 1
ETX-1>config>oam>cfm>md(1)$ classification vlan 100
ETX-1>config>oam>cfm>md(1)>ma(1)$ mep 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)$ classification vlan 100
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)$ bind ethernet 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)$ queue fixed 1 block 0/1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)$ remote-mep 2
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)$ no shutdown
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)# exit
ETX-1>config>oam>cfm>md(1)>ma(1)# exit
ETX-1>config>oam>cfm>md(1)# info detail
md-level 3
name string "MD1"
maintenance-association 1
name string "MA1"
ccm-interval 1s
mep 1
bind ethernet 1
queue fixed 1 block 0/1
remote-mep 2
dest-addr-type ccm multicast pm unicast
ccm-initiate
ccm-priority 0
direction down
client-md-level 4
no ais
no shutdown
exit
exit
Displaying MEP Status and Remote MEP

The following illustrates the display of MEP status and remote MEP.
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)# show status
Port : Ethernet 1
Direction : Down
VLAN : 100
Priority : 0
MD Name : MD1
MA Name : MA1
Cross Connect Status : OK
Remote MEP Remote MEP Address Operational Status

-----------------------------------------------------------------------------
2 00-00-00-00-00-00 Fail

Configuring MIP Automatically

This example illustrates automatic MIP configuration. The prerequisite for the
example is that there are flows configured between ETX-1 and the device(s)
acting as MEP(s) (refer to Flows for information on defining flows).
ETX-1>config>oam>cfm# mip-assign automatic
ETX-1>config>oam>cfm# maintenance-domain 2
ETX-1>config>oam>cfm>md(2)$ maintenance-association 2
ETX-1>config>oam>cfm>md(2)>ma(2)$ classification vlan 100
ETX-1>config>oam>cfm>md(2)>ma(2)$ mip-policy default
ETX-1>config>oam>cfm>md(2)>ma(2)# exit
ETX-1>config>oam>cfm>md(2)# exit
ETX-1>config>oam>cfm# show mips
Port VLAN MD-level
-----------------------------------------------------------------------------
1 100 3
Configuring Maintenance Endpoint Services

You can configure up to eight services on a MEP, corresponding to each p-bit.
Each service sets delay and delay variation thresholds. If the thresholds are
exceeded, the service is declared as degraded. You can also define priority of
OAM messages originating from this service.
To add a MEP service:

At the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,
enter:
service <serviceid>
where <serviceid> is 18.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)$
is displayed.
To configure a MEP service:

maintenance-association <maid> mep <mepid> service <serviceid> to select
the service to configure (<serviceid> is 18).
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid
>)# is displayed.
Associating this service with a classification priority-bit <p-bit> The allowed range is 07
priority Note: Only one service can be
defined on each p-bit.
Specifying delay threshold delay-threshold <delay-thresh> 150000 in 0.1 millisec steps

Specifying delay variation delay-var-threshold <delay-var-thresh> 150000 in 0.1 millisec steps

threshold
Specifying the interval for dmm-interval {100ms | 1s | 10s}

delay measurement messages,
to be used by all remote NEs
defined for service
Specifying the interval for loss lmm-interval {100ms | 1s | 10s}

measurement messages, to be
used by all remote NEs defined
for service
Configuring destination NE for dest-ne <dest-ne-index> 1255

service
Activating the MEP service no shutdown You can activate a service only
if the corresponding MEP is
active and you have defined at
least one destination NE
Setting the interval for pm-collection interval <seconds> no pm-collection disables PM

performance monitoring data data collection.
collection Note: Please enable the global
PM function before setting this
command.
Configuring Destination NEs

For performance measurement it is necessary to know the exact address of the
destination NE. You can configure the remote MAC address of the NE or ETX-1
can learn it from the CCM messages.
If the remote MAC address is not configured and needs to be learned,
performance measurement messages are sent only after the address is learned.
To add a destination NE:

At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#,
enter:
dest-ne <dest-ne-index>
where <dest-ne-index> is 1255.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)$ is displayed.
To configure a destination NE:

maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index> to select the destination NE to configure.

The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid
>)>dest-ne(<dest-ne-index>)# is displayed.
Enabling two-way delay delay two-way

measurement method [data-tlv-length <length-val>]
Defining single-ended loss loss single-ended [synthetic] Synthetic This method

measurement method measures DM frames.
Setting the interval for pm-collection interval <seconds> no pm-collection disables PM

performance monitoring data data collection.
collection Note: Please enable the global
PM function before setting this
command.
Defining the MAC address of remote mac-address <mac> If the MAC address is
the destination NE 00-00-00-00-00-00, the
statistic counters for the
destination NE do not
increment
Defining the remote MEP ID of remote mep-id <remote-mep-id>

the destination NE
Example
To configure service and destination NE:

MD ID 1, MA ID 1, MEP ID 1 (from example in Configuring MD, MA, and MEP)
Service 1
Destination NE 3.
ETX-1# configure oam cfm ma 1 ma 1 mep 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)# service 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)$ dest-ne 3
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)$ exit
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# no shutdown
ETX-1ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# exit
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# info detail
delay-threshold 10
delay-var-threshold 10
classification priority-bit 0
lmm-interval 1s
dmm-interval 1s
dest-ne 3
remote mac-address 00-00-00-00-00-00
delay two-way data-tlv-length 0
loss single-ended synthetic
exit
no shutdown

Configuring OAM CFM Service Event Reporting

You can define dedicated event reporting counters to track OAM SLA threshold
crossing violations (for information on configuring the OAM service thresholds,
refer to Configuring Maintenance Endpoint Services).
In addition to the regular OAM statistics collection, ETX-1 supports proactive SLA
measurements per OAM service, as per RMON-based RFC 2819. The device sends
reports when one of the counters 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. If
an event is generated, this action also sends a syslog notification packet, if
Syslog reporting is active (refer to Syslog for more details)
The following counters can be monitored:
Far End Frame Loss Ratio Total number of OAM frames lost from local MEP
to remote MEP, divided by total number of transmitted OAM frames since the
service was activated
Near End Frame Loss Ratio Total number of OAM frames lost from remote
MEP to local MEP, divided by total number of transmitted OAM frames since
the service was activated
Frames Above Delay Number of frames that exceeded delay threshold
Frames Above Delay Variation (jitter) Number of frames below or equal
delay variation threshold
Far End Unavailability Ratio Total number of far end unavailable seconds
divided by elapsed time since service was activated
Near End Unavailability Ratio Total number of near end unavailable seconds
divided by elapsed time since service was activated.
For non ratio-based counters (Frames Above Delay and Frames Above Delay
Variation), you have to define a sampling interval in addition to the rising and
falling thresholds. The purpose of the interval is to define a timeline, in seconds,
in which the service OAM data is sampled and compared with the predefined
service thresholds. For the ratio-based counters, defining a sampling interval is
not required.
To configure the event reporting for a service:

1. Navigate to configure fault cfm).
2. Specify the service and counter for which you wish to configure event
reporting:
service md <mdid> ma <maid> mep <mepid> service <serviceid>
{above-delay | above-delay-var | far-end-loss-ratio |
near-end-loss-ratio | far-end-unavailability-ratio |
near-vend-unavailability-ratio}
The prompt
config>fault>cfm>service(<mdid>/<maid>/<mepid>/<serviceid>)# is
displayed.
3. Specify the type of event reporting for the counter (refer to Table 8-7):

For counters above-delay and above-delay-var:

frames-report [event {none | log | trap | logandtrap}]
[rising-threshold <rising-threshold>] [falling-threshold
<falling-threshold>] [sampling-interval <value>]
For counters near-end-loss-ratio or far-end-loss-ratio:
[rising-threshold {1e-3 | 1e-4 | 1e-5 | 1e-6 | 1e-7 |
1e-8 | 1e-9 | 1e-10}] [falling-threshold {1e-3 | 1e-4 |
1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 | 1e-10}]
For counters near-end-unavailability-ratio or far-end-unavailability-ratio:
[rising-threshold <rising-threshold-thousandth>]
[falling-threshold <falling-threshold-thousandth>]
4. Type no shutdown to activate the event reporting for the counter.
Table 8-7. Service Event Reporting Parameters
Parameter Description Possible Values
event Specifies the type of event reporting none The event is not reported
log The event is reported via the
event log
trap An SNMP trap is sent to
report the event
logandtrap The event is reported
via the event log and an SNMP trap
rising-threshold A value above rising-threshold within the For counters above-delay or

falling-threshold sampling interval for the particular event is above-delay-var (measured in
considered as rising event occurred seconds::
A value below falling-threshold within the 160
sampling interval for the particular event is For counters near-end-loss-ratio
considered as falling event occurred or far-end-loss-ratio:
1e-3
1e-4
1e-5
1e-6
1e-7
1e-8
1e-9
1e-10
For counters
near-end-unavailability-ratio or
far-end-unavailability-ratio:
11000
Note: Rising threshold must be
greater than falling-threshold.
sampling-interval Specifies the interval in seconds over which Notes:

the data is sampled and compared with the Relevant only for counters
rising and falling thresholds above-delay or above-delay-var

Example
To configure OAM CFM event reporting:

Configure counters for the following service, as shown in the table below:
Maintenance domain 5
Maintenance association 8
MEP 3
Service 4.
The delay and delay variation (jitter) threshold for this service are set to 10 and
5 milliseconds respectively. The reporting counters for this service are set as
shown in the table below.
Counter Event Type Rising Threshold Falling Threshold Sampling

Interval
Frames Above Delay Log and trap 4 2 8
Frames Above Delay Variation Log 10 5 30
Far End Frame Loss Ratio Trap 1e-4 1e-8
Near End Frame Loss Ratio Log and trap 1e-9 1e-10
Far End Unavailability Ratio Trap 40 20
Near End Unavailability Ratio Log 50 25
In this example, an SNMP trap and an event are generated as notification of the
rising threshold if during an 8-second sample interval, four DMM packets or more
exceed the 10-milliseconds delay threshold of this service. The alarm is cleared
(falling threshold) if ETX-1 detects an 8-second sample interval in which two or
fewer packets cross the thresholds.
A rising or falling threshold event is generated if a specific ratio is exceeded. For
example, an SNMP trap is sent if the far end Frame Loss Ratio (from ETX-1 to the
network) exceed 10^-4, i.e. more than one frame out of 10,000 LMMs sent for
this service are lost.
To define the service delay thresholds:

ETX-1# configure oam cfm ma 5 ma 8 mep 3 service 4
ETX-1>config>oam>cfm>md(5)>ma(8)>mep(3)>service(4)delay-threshold 10
ETX-1>config>oam>cfm>md(5)>ma(8)>mep(3)>service(4) delay-var-threshold 5
To define the service event reporting counters:

ETX-1# configure fault cfm
ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4 above-delay
ETX-1>config>fault>cfm>service(5/8/3/4/above-delay)$ frames-report event
logandtrap rising-threshold 4 falling-threshold 2 sampling-interval 8
ETX-1>config>fault>cfm>service(5/8/3/4/above-delay)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/above-delay)$ exit

ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4 above-delay-var

ETX-1>config>fault>cfm>service(5/8/3/4/above-delay-var)$ frames-report event
log rising-threshold 10 falling-threshold 5 sampling-interval 30
ETX-1>config>fault>cfm>service(5/8/3/4/above-delay-var)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/above-delay-var)$ exit
ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4 far-end-loss-ratio

ETX-1>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ frames-report
event trap rising-threshold 1e-4 falling-threshold 1e-8
ETX-1>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ exit
ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4 near-end-loss-ratio

ETX-1>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ frames-report
event logandtrap rising-threshold 1e-9 falling-threshold 1e-10
ETX-1>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ exit
ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4

far-end-unavailability-ratio
ETX-1>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ frames-report
event trap rising-threshold 40 falling-threshold 20
ETX-1>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ exit
ETX-1>config>fault>cfm# service md 5 ma 8 mep 3 service 4

near-end-unavailability-ratio
ETX-1>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ frames-report
event log rising-threshold 50 falling-threshold 25
ETX-1>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ no shutdown
ETX-1>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ exit

To display the defined service event reporting counters:

ETX-1>config>fault>cfm# info detail
service md 5 ma 8 mep 3 service 4 above-delay
frames-report event logandtrap rising-threshold 4 falling-threshold
2 sampling-interval 8
no shutdown
exit
service md 5 ma 8 mep 3 service 4 above-delay-var
frames-report event log rising-threshold 10 falling-threshold 5
sampling-interval 30
no shutdown
exit
service md 5 ma 8 mep 3 service 4 far-end-loss-ratio
frames-report event trap rising-threshold 1e-4 falling-threshold
1e-8
no shutdown
exit
service md 5 ma 8 mep 3 service 4 near-end-loss-ratio
frames-report event logandtrap rising-threshold 1e-9
falling-threshold 1e-10
no shutdown
exit
service md 5 ma 8 mep 3 service 4 far-end-unavailability-ratio
frames-report event trap rising-threshold 40 falling-threshold 20
no shutdown
exit
service md 5 ma 8 mep 3 service 4 near-end-unavailability-ratio
frames-report event log rising-threshold 50 falling-threshold 25
no shutdown
exit
Displaying OAM CFM Statistics

You can display end-to-end performance monitoring data for the OAM services
and destination NEs. The statistics for a service are calculated from the statistics
for its destination NEs.
ETX-1 measures performance in fixed intervals (the interval length can be
configured, using the interval-duration command).
You can view the following types of statistics for services and destination NEs:
Running OAM statistics collected since the corresponding service was
activated
Interval OAM statistics for the current interval or a selected interval. You
can select an interval only if it has already ended since the corresponding
service was activated.
When a service is first activated, you can view statistics for only the current
interval. The statistics data is shown for the time elapsed since the beginning
of the interval. When the current interval ends, it becomes interval 1 and you
can select it for viewing interval statistics. After each interval ends, you can
select it for viewing interval statistics.

To configure the OAM CFM statistics interval in minutes:

At the config>system prompt, use the interval-duration command as
specified: interval-duration {5 | 10 | 15}.
To display the OAM CFM statistics for a service or destination NE:

1. Navigate to the level corresponding to the OAM service or destination NE for
which you wish to view the statistics (configure oam cfm
maintenance-domain <mdid> maintenance-association <maid> mep <mepid>
service <serviceid> or configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index>).
The prompt for service or destination NE is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)#
Note The service for which you wish to view the statistics must be active. If the service
is not active, the commands to view statistics are not recognized.
Viewing running show statistics The statistics are displayed as shown in Displaying Running
statistics running Statistics; refer to Table 8-8, Table 8-9 and Table 8-10

Viewing statistics show statistics The statistics for the current interval are displayed as shown in Far
for the current current End TX Frames : 161495
interval Far End RX Frames : 161464
Far End Lost Frames : 31
Far End Unavailable Seconds (Sec) :0
Near End TX Frames : 161464

Near End RX Frames : 161462
Near End Lost Frames :0
Near End Unavailable Seconds (Sec) : 0
Current Delay (mSec) : 0.3

Current Delay Variation (mSec) : 0.1
Frames Above Delay Threshold :0
Frames Above Delay Variation Threshold : 0
Elapsed Time (sec) : 80732
Loss and Delay Measurements Messages

-----------------------------------------------------------------------------
: Transmitted
LMMs : 80733
DMMs : 80733
: Received
LMRs : 80733
DMRs : 80733
Displaying Current Statistics; refer to Table 8-8, Table 8-9 and

Table 8-10
Viewing the show statistics Allowed values for interval-num: 196

statistics for a interval
selected interval <interval-num> The statistics for the selected interval are displayed as
shown in Displaying Interval Statistics; refer to
Table 8-8, Table 8-9 and Table 8-10
If you specified an interval that has not yet ended since
the service was activated, a message is displayed that
the interval doesnt exist.
Viewing running show statistics all The statistics are displayed as shown in Displaying Running
statistics, Statistics,
statistics for the
current interval,
statistics for all
intervals
Viewing statistics show statistics all- The statistics for all intervals are displayed as shown inDisplaying
for all intervals intervals Interval Statistics; refer to Table 8-8, Table 8-9 and Table 8-10
Clearing the clear-statistics All statistics data for the service or destination NE are cleared,
statistics for the including the stored interval data, except for the elapsed time
service or since the start of the current interval
destination NE

Table 8-8. OAM Statistic Counters - Service
Far End Tx Frames Total number of frames transmitted from local service to remote
service since the service was activated
Far End Rx Frames Total number of frames received by remote service since the service
was activated
Far End Lost Frames Total number of frames lost from local service to remote service since
the service was activated (Far End Tx Frames - Far End Rx Frames)
Far End Frame Loss Ratio (%) Far End Lost Frames divided by Far End Tx Frames
Near End Tx Frames Total number of frames transmitted from remote service to local
service since the service was activated
Near End Rx Frames Total number of frames received by local service since the service was
activated
Near End Lost Frames Total number of frames lost from remote service to local service since
the service was activated (Near End Tx Frames - Near End Rx Frames)
Near End Frame Loss Ratio (%) Near End Lost Frames divided by Near End Tx Frames
Current Delay (mSec) Current delay received in the last Delay Measurement Reply (DMR)
Current Delay Variation (mSec) Difference between the current delay value and the previous current
delay value
Average Two Way Delay (mSec) Average of all frame delay values received in DM frames
Average Two Way Delay Var (mSec) Average difference between the frame delay values received in DM
frames
Frames Above Delay Threshold Number of DM frames whose delay value exceeded the delay
threshold configured for the service
Frames Above Delay Variation Number of DM frames whose delay variation exceeded the delay
Threshold variation threshold configured for the service
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated
Table 8-9. OAM Statistic Counters Destination NE
Far End Tx Frames Total number of frames transmitted from local destination NE to
remote destination NE since the service was activated (the type of
frames counted is synthetic, according to the method configured by
the loss single-ended command)
Far End Rx Frames Total number of frames received by remote destination NE since the
service was activated (the type of frames counted is synthetic,
according to the method configured by the loss single-ended
command)

Far End Lost Frames Total number of frames lost from local destination NE to remote
destination NE since the service was activated (Far End Tx Frames -
Far End Rx Frames) (the type of frames counted is synthetic,
command)
Far End Frame Loss Ratio (%) Far End Lost Frames divided by Far End Tx Frames
Far End Unavailable Seconds (Sec) Number of seconds the remote destination NE is considered
unavailable. The definition of unavailability differs according to
synthetic measurement mode, as configured by the loss single-ended
command:
Synthetic mode The destination NE is considered unavailable
after 3.5 consecutive seconds with no reception of synthetic
frames; the 3.5 seconds are part of the unavailable time. The
destination NE is considered available again when a synthetic
frame is received.
Near End Tx Frames Total number of frames transmitted from remote destination NE to
local destination NE since the service was activated (the type of
frames counted is synthetic, according to the method configured by
the loss single-ended command)
Near End Rx Frames Total number of frames received by local destination NE since the
service was activated (the type of frames counted is synthetic,
command)
Near End Lost Frames Total number of frames lost from remote destination NE to local
destination NE since the service was activated (Near End Tx Frames -
Near End Rx Frames) (the type of frames counted is synthetic,
command)
Near End Frame Loss Ratio (%) Near End Lost Frames divided by Near End Tx Frames
Near End Unavailable Seconds (Sec) Number of seconds the local destination NE is considered unavailable.
Refer to the description of Far End Unavailable Seconds for the
definition of unavailability.
Current Delay (mSec) Current delay received in the last Delay Measurement Reply (DMR)
Current Delay Variation (mSec) Difference between the current delay value and the previous current
delay value
Average Two Way Delay (mSec) Average of all frame delay values received in DM frames
Average Two Way Delay Var (mSec) Average difference between the frame delay values received in DM
frames
Frames Above Delay Threshold Number of DM frames whose delay value exceeded the delay
threshold configured for the destination NE
Frames Above Delay Variation Number of DM frames whose delay variation exceeded the delay
Threshold variation threshold configured for the destination NE
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated

Table 8-10. OAM Delay and Loss Measurement Counters
Transmitted LMMs Number of transmitted loss measurement messages

Transmitted DMMs Number of transmitted delay measurement messages
Received LMRs Number of received loss measurement replies
Received DMRs Number of received delay measurement replies
Examples
Displaying Running Statistics

ETX-1>config>oam>cfm# ma 1 ma 1 mep 1 serv 1
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics running
Running Counters
-----------------------------------------------------------------------------
Far End TX Frames : 160707
Far End RX Frames : 160676

Near End Lost Frames : 0

Frames Above Delay Threshold : 0
-----------------------------------------------------------------------------
: Transmitted
LMMs : 80344
DMMs : 80344
: Received
LMRs : 80344
DMRs : 80344

ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# dest-ne 3
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
statistics running
Running Counters
-----------------------------------------------------------------------------
Far End TX Frames : 161495
Far End RX Frames : 161464
Far End Unavailable Seconds (Sec) : 0



-----------------------------------------------------------------------------
: Transmitted
LMMs : 80733
DMMs : 80733
: Received
LMRs : 80733
DMRs : 80733

Displaying Current Statistics

ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics current
Current
-----------------------------------------------------------------------------
Far End Tx Frames : 662
Far End Rx Frames : 662
Far End Frame Loss Ratio (%) : 0.0000%
Near End Tx Frames : 662

Near End Rx Frames : 662
Near End Frame Loss Ratio (%) : 0.0000%
Average Two Way Delay (mSec) : 0.2

Average Two Way Delay Var (mSec) : 0.0

-----------------------------------------------------------------------------
: Transmitted
LMMs : 332
DMMs : 332
: Received
LMRs : 332
DMRs : 332

ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
statistics current
Current
-----------------------------------------------------------------------------



-----------------------------------------------------------------------------
: Transmitted
LMMs : 455
DMMs : 455
: Received
LMRs : 455
DMRs : 455
Displaying Interval Statistics

ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statist interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1



Loss and Delay Measurements messages

-----------------------------------------------------------------------------
: Transmitted
LMMs : 900
DMMs : 900
: Received
LMRs : 900
DMRs : 900
ETX-1>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statist
interval 1
Interval
-----------------------------------------------------------------------------
Valid Data :
Time Stamp : 27-05-2013 16:07:41
Duration (Sec) : 900

Far End Frames Loss : 0


Loss and Delay Measurements messages

-----------------------------------------------------------------------------
: Transmitted
LMMs : 900
DMMs : 900
: Received
LMRs : 900
DMRs : 900
Performing OAM Loopback

This diagnostic utility verifies OAM connectivity on Ethernet connections. You can
execute the loopback according to the destination MAC address or the remote
MEP number.
Note
The option for remote MEP ID is available only if ETX-1 can resolve at least one
remote MEP MAC address.
To run an OAM loopback:

enter all necessary commands according to the tasks listed below.

Specifying remote MEP by MAC lbm address <mac-address> repeat MAC address is in the
address <repeat-num> format <xx-xx-xx-xx-xx-xx>
Specifying remote MEP by MEP ID lbm remote-mep <mep-id> repeat Allowed range of
<repeat-num> repeat-num is 150
Sending LBM messages to default lbm multicast repeat <repeat-num>

multicast MAC address
Checking OAM loopback results show lbm-results
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified either by
the MAC address or the maintenance end point (MEP).
Note
The option to specify the destination MEP ID is available only if ETX-1 can resolve
at least one remote MEP MAC address.
To run an OAM link trace:

enter all necessary commands according to the tasks listed below.
Specifying remote MEP by MAC linktrace address <mac-address> MAC address is in the
address [ttl <ttl-value>] format <xx-xx-xx-xx-xx-xx>
Specifying remote MEP by ID linktrace remote-mep <mep-id> Allowed range for ttl-value
[ttl <ttl-value>] is 164. This parameter
specifies the number of
hops. Each unit in the link
trace decrements the TTL
until it reaches 0, which
terminates the link trace.
Checking the OAM link trace results show linktrace-results
OAM EFM
This section describes the monitoring of the Ethernet links using OAM EFM (OAM
Ethernet at the First Mile)
ETX-1 can act as the active or passive side in an IEEE 802.3-2005 application.
When link OAM (EFM) is enabled for a port, you can view its status by displaying
the port status (show oam-efm). You can also display the OAM (EFM) parameters
and OAM (EFM) statistics.
Standards
IEEE 802.3ah

Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
The OAM (EFM) discovery process allows a local data terminating entity (DTE) to
detect Ethernet OAM capabilities on a remote DTE. Once Ethernet OAM support is
detected, both ends of the link exchange state and configuration information,
such as mode, PDU size, and it can make a remote device perform loopback
function, if the remote device supports loopaback function. If both DTEs are
satisfied with the settings, OAM is enabled on the link. However, the loss of a link
or a failure to receive OAMPDUs for five seconds may cause the discovery process
to restart.
DTEs may either be in active or passive mode. DTEs in active mode initiate the
ETH-OAM (EFM) communications and can issue queries and commands to a
remote device. DTEs in passive mode generally wait for the peer device to initiate
OAM communications and respond to commands and queries, but do not initiate
them.
A flag in the OAMPDU allows an OAM entity to convey the failure condition Link
Fault to its peer. Link Fault refers to the loss of signal detected by the receiver; A
Link Fault report is sent once per second with the Information OAMPDU.
Factory Defaults
By default, OAM EFM is not enabled for the Ethernet.
Configuring OAM EFM

There are two available OAM EFM descriptors. Each can be configured to indicate
active or passive OAM EFM.
To configure OAM EFM descriptor:

1. Navigate to configure oam efm.
The config>oam>efm# prompt is displayed.
2. Enter:
descriptor <number> {active | passive}
To configure link OAM (EFM) for Ethernet:

1. Navigate to configure port ethernet <port-num>, respectively.
The prompt config>port>eth(<port-num>)# is displayed, respectively.

Enabling link OAM (EFM) efm descriptor <efm-descriptor- The EFM descriptor must exist
index> before you can assign it to a port
For proper functioning of link
OAM (EFM), the relevant Ethernet
port must be associated with an
L2CP profile that specifies peer
action for MAC 0x02.
Disabling link OAM (EFM) no efm
Displaying link OAM (EFM) show oam-efm Relevant only if link OAM (EFM) is
parameters enabled.
Displaying link OAM (EFM) statistics show oam-efm-statistics Relevant only if link OAM (EFM) is
enabled.
Commands in level configure port ethernet <port-num> efm
Enabling loopback loopback no loopback disables loopback
Enabling SNMP tunneling for OAM snmp-tunneling no snmp-tunneling disables

EFM loopback

Example
To enable active link OAM (EFM) for Ethernet port 1 and display the status:
ETX-1# configure port l2cp-profile mac2peer
ETX-1>config>port>l2cp-profile(mac2peer)# mac 0x02 peer
ETX-1>config>port>l2cp-profile(mac2peer)# exit all
ETX-1# configure oam efm
ETX-1>config>oam>efm# descriptor 1 active
ETX-1>config>oam>efm# exit all
ETX-1>config>port>eth(1)# l2cp profile mac2peer
ETX-1>config>port>eth(1)# efm descriptor 1
ETX-1>config>port>eth(1)>efm# exit
ETX-1>config>port>eth(1)# show oam-efm
Administrative Status : Enabled
Operational Status : Link Fault
Loopback Status : Off
OAM EFM Information

-----------------------------------------------------------------------------
Local Remote
MAC Address : 00-20-D2-50-1A-13 --
Mode : Active --
Unidirectional : Not Supported --
Vars Retrieval : Supported --
Link Events : Supported --
Loopback : Not Supported --
PDU Size : 1518 --
Vendor OUI : 0x0020D2 --
8.6 Router
The router in ETX-1 is used to interconnect internal Layer-3 support modules
such as management. Any flow related to management must be via an SVI that is
bound to a router interface.
Notes You can configure up to eight router interfaces

To enable management, you must configure a router interface enabled for
management access, assign it an IP address, and bind it to an SVI for which
management flows have been defined. Refer to the Quick Start Guide for an
example of management configuration.
Benefits
The router provides Layer-3 (IP) connectivity.
Factory Default
By default, the router is configured as shown in the following.
ETX-1 Ver. 1.2 Router 8-69

ETX-1# conf router 1

ETX-1>config>router(1)# inf d
name "Router#1"
dhcp-client
host-name sys-name
vendor-class-id ent-physical-name
exit
Any management-related flow entering or exiting the device must be via an SVI
that is bound to a router interface. A router interface can be associated via
binding to only one SVI. If a flow is used for management purposes, the router
interface corresponding to the SVI must be enabled for management access.
Figure 8-1. Router and SVIs
Configuring the Router

The router functionality allows ETX-1 to establish links to Ethernet ports via SVIs.
You can define only one router.
To configure the router:

1. At the config# prompt, enter:
router 1
The config>router(1)# prompt is displayed.
Deleting dynamic ARP entities clear-arp-table
Assigning name to router name <string>
8-70 Router ETX-1 Ver. 1.2

Enabling the static route and the next static-route The next hop must be a subnet of
gateway (next hop) using the next <IP-address/mask> address one of the router interfaces.
hops IP address <IP-address> [metric To set the default-gateway,configure
<metric>] static route of address 0.0.0.0/0 to
next hop default gateway address.
Displaying the address resolution show arp-table

protocol (ARP) table, which lists the
the original MAC addresses and the
associated (resolved) IP addresses
Displaying the interface table show interface-table
Displaying the routing table show routing-table
Configuring DHCP client dhcp-client
Commands in level dhcp-client
Providing host name to DHCP server host-name name <string> Specify a name, or use sys-name to
host-name sys-name indicate that the system name will be
used as the host name
Providing vendor ID to DHCP server vendor-class-id name Specify an ID, or use

<string> ent-physical-name to indicate that
vendor-class-id the device name will be used as the
ent-physical-name vendor ID
To configure router interfaces:

1. At the config>router(1)# prompt, enter:
interface <number> [loopback]
The config>router(1)>interface(<number>)# prompt is displayed.
Assigning an IP address and a address <ip-address/mask>

subnet mask to the router interface
Binding router interface to logical bind svi <port-number> You can bind one SVI to a router
port interface
Enabling/disabling DHCP client dhcp
Configuring interface management management-access {allow-all

access | allow-ping}
Configuring maximum transmit unit mtu <bytes>

allowed
Assigning a name to the router name <string>

interface
Displaying interface status show status
ETX-1 Ver. 1.2 Router 8-71

Administratively enabling interface no shutdown You can administratively enable the

router interface only if the following
are true:
An IP address was assigned via the
address command
The router interface is bound to an
administratively enabled SVI
Flows have been defined to and
from the SVI, and are
administratively enabled.
shutdown disables the interface
Configuring DHCP client dhcp-client
Commands in level dhcp-client
Providing client ID to DHCP server client-id id <string> Specify an ID, or use mac to indicate
client-id mac that the device MAC address will be
used as the client ID
8-72 Router ETX-1 Ver. 1.2

Chapter 9
Timing and
Synchronization
9.1 Working with SNTP

This section explains how to receive the clock signal from NTP servers in the
network. ETX-1 can synchronize with up to ten servers, sending NTP requests to
the servers at user-defined intervals.
You can set one of the active SNTP servers as the preferred server, so that ETX-
1 sends NTP requests to the preferred server. If there is no preferred server or if
the preferred server does not answer, then ETX-1 sends NTP requests to any
enabled servers.
Factory Defaults
The default configuration of the SNTP parameters is:
No SNTP servers defined
Polling interval set to 15 minutes.
When an SNTP server is defined, its default configuration is:
IP address set to 0.0.0.0
Not preferred
Administratively disabled (shutdown).
Configuring SNTP Parameters

To configure SNTP parameters:
1. Navigate to config system date-and-time sntp.
The config>system>date-time>sntp# prompt is displayed.
Enabling ETX-1 to listen to NTP broadcast no broadcast disables

broadcast messages to obtain broadcast mode
accurate timestamps
Setting polling interval (in poll-interval <minutes> Allowed range is 11440

minutes) for SNTP requests
ETX-1 Ver. 1.2 Working with SNTP 9-1

Chapter 9 Timing and Synchronization Installation and Operation Manual
Defining and configuring SNTP server <server-id> Refer to Defining SNTP

servers Servers and Configuring SNTP
Server Parameters
Displaying SNTP server status show status
Defining SNTP Servers

To define an SNTP server:
2. Type server <server-id> to define an SNTP server with ID.
config>system>date-time>sntp>server(<server-id>) #. The SNTP server
parameters are configured by default as described in Factory Defaults.
3. Configure the SNTP server parameters as needed, as described in Configuring
SNTP Parameters.
Configuring SNTP Server Parameters

To configure SNTP server parameters:
2. Type server <server-id> to select the SNTP server to configure.
config>system>date-time>sntp>server(<server-id>)#.
Setting the IP address of the address <ip-address>

server
Setting SNTP server as preferred prefer no prefer removes preference

server. Only one server can be
preferred
Setting UDP port for NTP udp port <udp-port> Allowed range is 123, 1024
requests, to a specific UDP port udp default 65535
or to default UDP port (123)
Administratively enabling server no shutdown shutdown disables the server
Sending query to server and query-server

displaying result
9-2 Working with SNTP ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 9 Timing and Synchronization
Example
To define SNTP server:

Server ID = 1
IP address = 192.168.99.226
Preferred
Administratively enabled.
ETX-1# configure system date-and-time sntp
ETX-1>config>system>date-time>sntp# server 1
ETX-1>config>system>date-time>sntp>server(1)# address 192.168.99.226
ETX-1>config>system>date-time>sntp>server(1)# prefer
ETX-1>config>system>date-time>sntp>server(1)# no shutdown
ETX-1>config>system>date-time>sntp>server(1)# query-server
Query Server Replay
-----------------------------------------------------------------------------
Server : 192.168.99.226 UDP : 123
Date : 00-00-0000 Time(UTC) : 00:00:00
Stratum : 0
ETX-1>config>system>date-time>sntp>server(1)# exit
ETX-1>config>system>date-time>sntp# show status
System Uptime : 000 Days 02:33:20
System Time (Local) : 05-03-2012 17:26:19
Current Source : 1 127.0.0.1
NTP Server UDP Port Tstamp DateTime(UTC) Stratum Received

192.168.99.226 123 00-00-0000 00:00:00 0 --
ETX-1>config>system>date-time>sntp#
ETX-1 Ver. 1.2 Working with SNTP 9-3

Chapter 9 Timing and Synchronization Installation and Operation Manual
9-4 Working with SNTP ETX-1 Ver. 1.2

Chapter 10
Administration
10.1 Clearing Device Statistics

You can clear the statistics for Ethernet ports.
To clear the statistics:

At the device prompt, enter:
clear-statistics.
The statistics for Ethernet ports are cleared.
10.2 Date and Time

You can set the date and time for the ETX-1 internal real-time clock, or receive
the SNTP server clock signal.
Setting the Date and Time

To set the system date and time:
1. Navigate to configure system date-and-time.
The config>system>date-time# prompt is displayed.
Specifying the date format date-format {yyyy-mm-dd | dd-mm-yyyy

| mm-dd-yyyy | yyyy-dd-mm}
Defining the date date <date> Date is according to the

configured date format
Defining the time zone relative zone utc [<[{+|-}]hh[:mm]>] Allowed range of values:
to Universal Time Coordinated -12:00 to +12:00, in
30-minute increments
Defining the time time <hh:mm[:ss]>
To set the date and time:

Format = mm-dd-yyyy
ETX-1 Ver. 1.2 Date and Time 10-1

Chapter 10 Administration Installation and Operation Manual
Date = May 03, 2012

Time = 3:32pm
Zone = UTC 4 hours and 30 minutes.
ETX-1# configure system date-and-time
ETX-1>config>system>date-time# date-format mm-dd-yyyy
ETX-1>config>system>date-time# date 05-03-2012
ETX-1>config>system>date-time# time 15:32
ETX-1>config>system>date-time# zone utc -04:30
ETX-1>config>system>date-time#
Displaying the Date and Time

To display the date and time:
From the system context (config>system), enter:
show date-and-time.
10.3 Working with the Inventory

The ETX-1 inventory table displays the units components, hardware and software
revisions, and power supply types. You can display an inventory table that shows
all installed components; you can alsodisplay more detailed information for each
component. You can configure an alias name, asset ID, and serial number for
inventory components.
Standards and MIBs

The inventory feature is implemented according to RFC 4133 Entity MIB
(RFC 2737 was made obsolete by RFC 4133 version 3).
Benefits
You can monitor the installed components and hardware/software revisions.
Displaying Inventory Information

To display the inventory table:
At the config>system# prompt, enter:
show summary-inventory.
The inventory table is displayed (refer to Example to see a typical
inventory table output).
You can display additional information for each installed inventory component by
entering the inventory level using the corresponding inventory component index.
The index corresponds to the row in the output of show summary-inventory; it
therefore changes according to the specific components installed in the unit.
10-2 Working with the Inventory ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 10 Administration
To display the inventory component information:

1. Navigate to configure system inventory <entity-index>.
2. Enter:
show status.
Information for the corresponding inventory component is displayed
(refer to Table 10-1 for information on the parameters).
Table 10-1. Inventory Parameters
Description Description of component type, in the form:
<device-name>.< Physical Class>, e.g. ETX-1.Ethernet 1
Contained In Index of the component that contains the component for which information is being
displayed. This is 0 for the chassis, as it is not contained in any component, and 1 for
all other components, as they are all contained in the chassis.
Physical Class Class of component
Possible values: Chassis, CPU, Power Supply, Port
Relative Position Contains the relative position of this component among other similar components
(with the exception of the relative positions for the chassis, management Ethernet
port).
Possible values for the various component types:
Chassis 4294967295
CPU 1
Power Supply 1
Network Port 1 or 2
User Port 3, 4, 5, 6
Management Ethernet 101
RS-232 Control Port 11
Name Name of component
Possible values (according to component type):
<device-name> Chassis
CPU
Power Supply
Ethernet <n>
MNG Port
RS-232 Control Port
HW Rev Hardware revision (relevant only for chassis)
SW Rev Software revision (relevant only for chassis)
FW Rev Firmware revision (relevant only for chassis)
Serial Number Serial number (blank if unknown for component)
MFG Name Manufacturer name (blank if unknown for component)
Model Name Model name (blank if unknown for component)
Alias Alias name for component
Asset ID Identification information for component
FRU Indicates whether the component is a field replaceable unit (can be replaced on-site).
For ETX-1 this is normally true only for the chassis.
ETX-1 Ver. 1.2 Working with the Inventory 10-3

Setting Administrative Inventory Information

If necessary, you can configure the alias, asset ID, and serial number for
inventory components. To configure the information, you need to enter the
inventory level with the corresponding inventory component index as determined
by the position of the corresponding row in the output of show summary-
inventory.
To set inventory component information:

1. Navigate to configure system inventory <entity-index>.
The config>system>inventor(<entity-index>)# prompt is displayed.
Assigning user-defined alias to alias <string> no alias removes the alias.

component Alias is relevant only for the
chassis component.
Assigning user-specific asset identifier asset-id <id> no asset-id removes the asset
to the component (usually for ID.
removable physical components)
Assigning vendor-specific serial serial-number <string> no serial-number removes the

number to the component serial number.
Example
To display the following inventory information:
Inventory table
Inventory information for the following components:
Chassis
Power Supply
User Port 1.
10-4 Working with the Inventory ETX-1 Ver. 1.2


ETX-1# config>system# show summary-inventory
Physical ClassName HW Rev SW Rev FW Rev
-----------------------------------------------------------------------------
Index Physical Class Name HW Ver SW Ver FW Ver
-----------------------------------------------------------------------------
1 Chassis ETX-1- Chassis 2.0A(2.0) 1.2.0(0.34) 0.4
2 CPU CPU
3 Power Supply Power Supply
4 Port Ethernet 1
5 Port Ethernet 2
6 Port Ethernet 3
7 Port Ethernet 4
8 Port Ethernet 5
9 Port Ethernet 6
10 Port MNG Port
11 Port RS-232 Control Port
ETX-1>config>system# inventory 1
ETX-1>config>system>inventor(1)# show status
Description : ETX-1.Chassis
Contained In : 0
Physical Class : Chassis
Relative Position : 4294967295
Name : ETX-1 - Chassis
HW Ver : 2.0A(2.0)
SW Ver : 1.2.0(0.34)
FW Ver : 0.4
Serial Number : 00-20-D2-50-1A-13
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : True
ETX-1>config>system>inventor(1)# exit
ETX-1 >config>system# inventory 3
Description : ETX-1 {AC} Power Supply
Contained In : 1
Physical Class : Power Supply
Name : Power Supply
HW Ver : 2.0A(2.0)
SW Ver : 1.2.0(0.34)
FW Ver : 0.4
Serial Number :
MFG Name :
Model Name :
Alias : POWER-SUPPLY
Asset ID :
FRU : False
ETX-1 Ver. 1.2 Working with the Inventory 10-5

Description : ETX-1 Ethernet 3
Contained In : 1
Physical Class : Port
Name : Ethernet 3
HW Rev :
SW Rev :
FW Rev :
Serial Number :
MFG Name :
Model Name :
Alias :
Asset ID :
FRU : False
ETX-1>config>system#
To set the chassis alias to ETX-test-unit:

ETX-1>config>system>inventor(1)# alias ETX-test-unit
ETX-1>config>system>inventor(1) show status
Description : ETX-1.Chassis
Contained In : 0
Physical Class : Chassis
Name : ETX-1 - Chassis
HW Ver : 2.0A(2.0)
SW Ver : 1.2.0(0.34)
FW Ver : 0.4
Serial Number : 00-20-D2-50-1A-13
MFG Name : RAD
Model Name :
Alias : ETX-test-unit
Asset ID :
FRU : True
10.4 Displaying Environment

You can display information about the type and status of the power supplies, and
the status of the fans.
To display the information:

1. Navigate to configure chassis.
The config>chassis# prompt is displayed.
10-6 Displaying Environment ETX-1 Ver. 1.2

2. Enter:
show environment
The information is displayed as shown in the example below.
The status of the power supply and fan indicates whether the unit is
present and functioning properly, or is absent (does not exist), or has
failed.
ETX-1# configure chassis
ETX-1>config>chassis# show environment
Power Supply Type Status
-----------------------------------------------------------------------------
1 AC-PFOK
FAN Status
-----------------------------------------------------------------------------
Sensor Value Status

-----------------------------------------------------------------------------
ETX-1>config>chassis#
10.5 Displaying Software Versions

You can display the active, main, and backup software file versions, dates, times
and size.
To display the versions:

At the file# prompt enter:
show sw-pack
ETX-1 Ver. 1.2 Displaying Software Versions 10-7

ETX-1# file
ETX-1>file# show sw-pack
Name Version Creation Time Actual
-----------------------------------------------------------------------------
sw-pack-1 1.2.0(0.15) 2013-05-09 08:35:15 previous active
sw-pack-2 1.2.0(0.16) 2013-05-09 08:35:15 active
sw-pack-1 Size (Bytes) : 3444378
Type Name Version H/W Ver

Size
(Bytes)
-----------------------------------------------------------------------------
main main.bin 1.2.0(0.15) 0.0 3444138
sw-pack-2 Size (Bytes) : 3444376
Type Name Version H/W Ver

Size
(Bytes)
-----------------------------------------------------------------------------
main main.bin 1.2.0(0.16) 0.0 3444136
ETX-1>file#
10.6 Displaying CPU and Memory Utilization

You can view the CPU and memory buffer usage. Refer to Table 10-2 for a
description of the memory buffers.
To display CPU usage:

show cpu-utilization
The CPU usage is displayed.
ETX-1>config>system# show cpu-utilization
CPU Utilization
-----------------------------------------------------------------------------
Min (%) : 0
Cur (%) : 2
Max (%) : 92
Average (%) : 3
To display memory buffer usage:

show buffers
The memory buffer usage is displayed.
10-8 Displaying CPU and Memory Utilization ETX-1 Ver. 1.2

ETX-1>config>system# show buffers

Pool Name Buffer Size(Bytes)Total BuffersFree BuffersAllocation FailuresFree
Failures
-----------------------------------------------------------------------------
VLAN 64 100 100 0 0
Huge 8192 100 100 0 0
Large 2048 1000 1000 0 0
Medium 512 4000 4000 0 0
Small 64 4000 3979 0
Queue 16 8000 8000 0 0
Table 10-2. Memory Buffers
Buffer Size Total Buffers Available Purpose
VLAN 64 100 Unused, except for three buffers that are used for
internal functions
Huge 8192 100 Unused
Large 2048 1000 OAM CFM and OAM EFM
Medium 512 4000 Event log and traps
Small 64 4000 Management traffic
Queue 16 8000 Application task messages
10.7 File Operations

You can perform the following operations:
Transfer files via SFTP/TFTP
Copy files within the ETX-1 unit
Display files
Delete files
Downloading/Uploading Files
You can download or upload files to the ETX-1 unit via SFTP/TFTP. Typically,
configuration files and software files are copied
The software files can also be downloaded to ETX-1 via the Boot Manager, using
XMODEM, FTP, or TFTP. For details on upgrading the device software, refer to
Chapter 12.
SFTP Application
The SFTP protocol provides secure file transfers via the devices Ethernet
interface. SFTP is a version of FTP that encrypts commands and data transfers,
keeping your data secure and your session private. For SFTP file transfers, an
SFTP server application must be installed on the local or remote computer.
ETX-1 Ver. 1.2 File Operations 10-9

Various third-party applications offer SFTP server software. For more information,
refer to the documentation of these applications.
ETX-1
ETX-1
Figure 10-1. Downloading a Software Application File via SFTP
Setting up SFTP Server

If using a local laptop and SFTP is the preferred transfer method, a SFTP server
application must be installed on the laptop.
If using a third-party application, refer to the applications setup documentation.
Checking the Firewall Settings

SFTP file transfers use TCP port 22. Be sure the firewall on the server computer
allows communication through this port.
To allow communication through port 22 in Windows XP:

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

The Windows Firewall dialog box appears.
10-10 File Operations ETX-1 Ver. 1.2

Figure 10-3. Changing Firewall Settings
4. Click the Exceptions tab.
Figure 10-4. Windows Firewall Dialog Box Exceptions Tab
5. Make sure port 22 appears in the exceptions list. If it does not, click Add Port
and add it to the list of exceptions.
Note Different types of firewalls require different configurations. Refer to your

firewall's documentation for instructions on using TCP port 22 for SFTP file
transfer.

TFTP Application
TFTP protocol is typically used for remote IP-to-IP file transfers via the device's
Ethernet interface. It can also be used, however, for local file transfer, as the
transfer rate of the Ethernet interface is much faster than that of the RS-232
interface.
For TFTP file transfers, a TFTP server application must be installed on the local or
remote computer. The TFTP server waits for any TFTP file transfer request
originating from the device, and automatically performs the request.
Various third-party TFTP applications allow instant creation of a TFTP server on a
client computer. For more information, refer to the documentation of these
applications.
ETX-1
ETX-1
Figure 10-5. Downloading a Software Application File via TFTP
Setting up a TFTP Server

If using a local laptop and TFTP is the preferred transfer method, a TFTP server
application must be installed on the laptop.
If using a third-party application, refer to the applications setup documentation
Checking the Firewall Settings

TFTP file transfers use port 69. Be sure the firewall on the server computer allows
communication through this port.
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 10-6. Viewing Network Connections
3. On the Network Tasks sidebar, click Change Windows Firewall settings.

The Windows Firewall dialog box appears.
Figure 10-7. Changing Firewall Settings
4. Click the Exceptions tab.

Figure 10-8. Windows Firewall Dialog Box Exceptions Tab
5. Make sure port 69 appears in the exceptions list. If it does not, click Add Port
and add it to the list of exceptions.
Note Different types of firewalls require different configurations. Refer to your

firewall's documentation for instructions on using a UDP-type port for TFTP file
transfer.
Using CLI to Download/Upload Files

You use the copy command to download/upload files.
To download a file via TFTP:

At any prompt, enter:
copy tftp://<host>/<source-file> <destination-file>
Example Download via TFTP

TFTP server address 192.168.99.75
Source file name ETX-1.bin
Destination file name sw-pack-2.

ETX-1# copy tftp://192.168.99.75/ETX-1.bin sw-pack-2
To download a file via SFTP:

copy sftp://<username>:<password>@<host>:<port>/<source-file>
<destination-file>.
Example Download via SFTP

SFTP server address 192.168.99.75
SFTP user name admin
SFTP password 1234
TCP port 22
Source file name ETX-1.bin
Destination file name sw-pack-2
ETX-1# copy sftp://<admin>:<1234>@192.168.99.75:22/ETX-1.bin sw-pack-2
To upload a file via TFTP:

copy <source-file> tftp://<host>/<destination-file>
Example Upload via TFTP

TFTP server address 192.168.99.75
Source file name startup-config
Destination file name conf.cfg.
ETX-1# copy startup-config tftp://192.168.99.75/conf.cfg
To upload a file via SFTP:

copy <source-file> sftp://<username>:<password>@<host>:port/<dest-file>
Example Upload via SFTP

SFTP server address 192.168.99.75
SFTP user name admin
SFTP password 1234
TCP port 22
Source file name startup-config
Destination file name conf.cfg
ETX-1# copy startup-config sftp://admin:[email protected]:22/conf.cfg
Copying Files within Device

You can copy files within the ETX-1 using the copy command.

To copy files within the device:

copy <source-file> <dest-file>
Example
Source file name running-config
Destination file name startup-config
ETX-1# copy running-config startup-config
Displaying Copy Status

You can display the status of current and past copy operations.
To display copy status:

At the file# prompt, enter:
show copy
Displaying Information on Files

You can display the following information:
Files within the device
Information on the configuration files
Contents of configuration text files
Information on the software files (software packs). For information on
upgrading to a different software pack, refer to Chapter 12.
To display the files within the device:

dir
A list of the file names and types is displayed.

ETX-1# file
ETX-1>file# dir
Codes: C-Configuration S-Software L-License LO-Log O-Other B-Banner
Name Type Size(Bytes) Creation Date Status
db-config LO -- 2013-08-09 File In Use

09:53:32
db-schema LO 16780 2013-08-09 Read Only
09:53:32
mac-table LO -- 2013-08-09 Read Only
09:53:32
pm-0 LO 18 2013-08-09 File In Use
09:53:33
sw-pack-1 S 3472304 2013-05-14 File In Use
13:17:34
sw-pack-2 S 3433902 2013-05-09
16:24:28
startup-config C 34 2013-08-09
09:51:58
factory-default-config C 34 2013-08-09 Read Only
09:53:32
running-config C -- 2013-08-09 File In Use
09:47:38
log LO 310000 2013-05-06 Read Only
14:58:32
Total Bytes : 13515776 Free Bytes : 5212160
Bytes Available for PM : 999982
To display information on the configuration files:

show configuration-files
Information on the configuration files is displayed.
ETX-1# file
ETX-1>file# show configuration-files
Configuration Last Modified Valid
-----------------------------------------------------------------------------
startup-config 1970.01.01 00:05:50 Yes
user-default-config 2015.05.19 01:00:34 Yes
factory-default-config1970.01.01 00:01:05 Yes
running-config 1970.01.01 00:00:08 Yes
Device loaded from : startup-config
running-config has been modified since last time it was equal to startup-config
To display the contents of configuration text files:

At the file# prompt, enter one of the following:
show factory-default-config
show rollback-config

show startup-config
show user-default-config
The contents of the specified configuration file are displayed.
To display information on the software files:

show sw-pack [refresh [<sec>]]
where sec represents the refresh timeout, with range 3100.
Information on the software files (up to two, named sw-pack-1 through
sw-pack-2) is displayed.
Deleting Files
You can delete the following files:
sw-pack-<n>
restore-point-config
rollback-config
startup-config
user-default-config
zero-touch-config-xml
Note Use caution in deleting files.
To delete a file:
delete <file-name>
You are prompted to confirm the deletion.
6. Confirm the deletion.
ETX-1# file
ETX-1>file# delete startup-config
! The file will be erased. Are you sure? [yes/no] _ yes
10.8 Saving Configuration

You must save your configuration if you wish to have it available, as it is not
saved automatically. You can save your configuration as follows:
To save the user configuration in startup-config:
In any level prompt enter: save
In any level prompt enter:
copy running-config startup-config.
10-18 Saving Configuration ETX-1 Ver. 1.2

To save the user default configuration in user-default-config, at the file#

prompt enter:
copy running-config user-default-config.
10.9 Reset
ETX-1 supports the following types of reset:
Reset to factory defaults
Reset to user defaults
Overall reset (restart) of the device.
Resetting to Factory Defaults

You can reset to factory defaults, or to factory defaults with configuration and
counter reset.
The configuration and counter reset comprises the following:
All files are removed, except for factory-default-config, user-default-config,
and the device software files.
Parameter snmpEngineBoots initialized to 1.
To reset ETX-1 to factory defaults:

1. At the admin# prompt enter:
factory-default
A confirmation message is displayed:
Current configuration will be erased and device will reboot with factory
default configuration. Are you sure?? [yes/no]
2. Enter yes to confirm the reset to factory defaults.
The factory-default-config file is copied to the startup-config file. The
device is reset; after startup the factory defaults are loaded. If a
startup-config confirm request was active, it is disabled.
To reset ETX-1 to factory defaults, with configuration and counter reset:

factory-default-all
The device will delete its entire database and reboot. Are you sure?
[yes/no]
2. Enter yes to confirm the reset to factory defaults with configuration and
counter reset.
The configuration and counter reset is performed, and the device is reset;
after startup the factory defaults are loaded. If a startup-config confirm
request was active, it is disabled.
ETX-1 Ver. 1.2 Reset 10-19

Resetting to User Defaults

To reset ETX-1 to user defaults:
user-default
Current configuration will be erased and device will reboot with user
default configuration. Are you sure? [yes/no]
2. Enter yes to confirm the reset to user defaults.
The user-default-config file is copied to the startup-config file. The device
resets; after startup the user defaults are loaded. If a startup-config
confirm request was active, it is disabled.
Restarting the Unit

If necessary, you can restart ETX-1 without interrupting the power supply.
To restart ETX-1:
reboot.
Device will reboot. Are you sure? [yes/no]
2. Enter yes to confirm the reset.
The unit restarts.
10-20 Reset ETX-1 Ver. 1.2

Chapter 11
Monitoring and
Diagnostics
The following topics are covered in this chapter:
Detecting problems
Alarms and traps
Performing diagnostic tests
11.1 Detecting Problems
LEDs
A red LED usually indicates a hardware problem. Check the port associated with
the LED to further investigate the problem. Refer to Chapter 3 for a description
of the LEDs.
Alarms and Traps

Alarms serve as notification of a fault in the device, and are indicated by an entry
in the event log, and/or an SNMP trap sent to a management station. Refer to
Handling Alarms and Events for further details on events and traps.
Statistic Counters
Statistic counters provide information on possible abnormal behavior and failures.
You can collect statistics on the following:
Ethernet ports
RADIUS server
For further information, refer to the relevant sections in Chapter 6-10 and the
relevant sections in the troubleshooting chart.
11.2 Handling Alarms and Events

An alarm is an indication of a fault in the device.
ETX-1 Ver. 1.2 Handling Alarms and Events 11-1

Chapter 11 Monitoring and Diagnostics Installation and Operation Manual
An event may be a fault, a user login, a change in port status, or other

occurrence in the device..
Alarms and events can be written in the alarm and event history log. The device
also maintains statistics for alarms and events in a brief log. Alarms can also be
written in the active alarm table. An SNMP trap can be sent to management
stations as the result of an alarm/event.
Alarms and events have the following properties:
Source An entity for which alarms and events can be generated. The source
consists of a source ID, source type (e.g., system, fan, Ethernet), and source
name.
ID Unique numeric identification of the alarm/event
Name Unique alphanumeric identification of the alarm/event, up to
32 characters
Description Alphanumeric description that provides details on the
alarm/event
Severity (alarms only) Critical, Major, or Minor.
Alarms and events can be masked per source type, source ID, or minimum
severity. When an alarm/event is masked, it is not written to the history log, and
any corresponding traps are not sent to management stations, regardless of
masking in the SNMP manager configuration. When an alarm/event is not masked,
any corresponding traps are sent only to management station for which the traps
are not masked in the SNMP manager configuration.
Configuring Alarm and Event Properties

This section explains how to configure alarm/event properties.
To configure alarm/event properties:

1. Navigate to configure reporting.
The config>reporting# prompt is displayed.
Configuring alarm input alarm-input <port-number> [active {high |

low | off}] [description <description>]
11-2 Handling Alarms and Events ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 11 Monitoring and Diagnostics
Configuring alarm/event alarm-source-attribute <source-name> no alarm-source-attribute masks

severity and masking per [<source-id>] alarm <alarm-list> [severity alarms/events. The following apply:
source {critical | major | minor}] [log] [snmp-trap] If a trap is masked according to
[led] alarm/event attribute, it is not
alarm-source-attribute <source-name> sent to any management
[<source-id>] event <event-list> [log] station, regardless of whether
[snmp-trap] it is masked in the SNMP
manager configuration
If a trap is unmasked according
to alarm/event attribute, it is
sent only to management
station for which it is not
masked in the SNMP manager
configuration.
Configuring alarm/event alarm-source-type-attribute <source-type> no alarm-source-type-attribute

severity and masking per alarm <alarm-list> [severity {critical | major masks alarms/events. The following
source type | minor}] [log] [snmp-trap] [led] apply:
alarm-source-type-attribute <source-type> If a trap is masked according to
event <event-list> [log] [snmp-trap] alarm/event attribute, it is not
sent to any management
station, regardless of whether
it is masked in the SNMP
manager configuration
If a trap is unmasked according
to alarm/event attribute, it is
sent only to management
station for which it is not
masked in the SNMP manager
configuration.
Configuring alarm masking per mask-minimum-severity [log {critical | major

severity | minor}] [snmp-trap {critical | major |
minor}] [led {critical | major | minor}]
Displaying information about a show alarm-information <source-type>

specified alarm and source <alarm-list>
type
Displaying information about show alarm-input [refresh [<sec>]]

alarm inputs
Displaying a list of supported show alarm-list

alarms, optionally according to show alarm-list [<source-type>
a specified source/severity [<source-id>] [severity {critical | major |
minor}]]
Displaying information about a show event-information <source-type>

specified event and source [<event-list>]
type

Displaying a list of supported show event-list

events show event-list <source-type> [<source-id
>]
Working with Alarm and Event Logs

This section explains how to work with the log files to display or acknowledge
alarm/events.
To work with alarm/event log files:

Acknowledging alarms acknowledge {log | brief-log | activity-log | all-logs}
Rebuilding active alarm active-alarm-rebuild [send-traps]

database
Clearing alarms from log clear-alarm-log {log | brief-log | activity-log | all-logs}

file(s)
Displaying active alarms, show active-alarms

optionally according to show active-alarms {<source-type> [<source-id>] | all}
specified criteria [minimum-severity {critical | major | minor}] [masked-included]
[instance <instance-number>]
Displaying active alarms with show active-alarms-details

details, optionally according show active-alarms-details {<source-type> [<source-id>] | all}
to specified criteria [minimum-severity {critical | major | minor}] [time-zone-utc]
[masked-included] [instance <instance-number>]
Displaying alarms in alarm show alarm-log

and event history log, show alarm-log {<source-type> [<source-id>] | all}
optionally according to [minimum-severity {critical | major | minor | cleared}]
specified criteria [order-ascending] [time-zone-utc] [acknowledged-included] [start
<yyyy-mm-dd> [<hh:mm[:ss]>] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]]
show alarm-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | cleared}] [order-
ascending] [time-zone-utc] [acknowledged-included] [last-seconds
<seconds> | last-entries <entries> | instance <number>]

Displaying alarms in brief show brief-alarm-log

alarm and event history log, show brief-alarm-log {<source-type> [<source-id>] | all}
optionally according to [minimum-severity {critical | major | minor | cleared}]
specified criteria [order-ascending] [time-zone-utc] [acknowledged-included] [start
<yyyy-mm-dd> [<hh:mm[:ss]>]] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]
show brief-alarm-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | cleared}] [order-
ascending] [time-zone-utc] [acknowledged-included] [last-seconds
<seconds> | last-entries <entries>]
Displaying brief alarm and show brief-log

event history log, optionally show brief-log {<source-type> [<source-id>] | all}
according to specified criteria [minimum-severity {critical | major | minor | warning | cleared}]
[order-ascending] [time-zone-utc] [acknowledged-included] [start
<yyyy-mm-dd> [<hh:mm[:ss]>]] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]
show brief-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | warning | cleared}]
[order-ascending] [time-zone-utc] [acknowledged-included]
[last-seconds <seconds>| last-entries <entries>]
Displaying alarm and event show log

history log, optionally show log {<source-type> [<source-id>] | all} [minimum-severity
according to specified criteria {critical | major | minor | warning | cleared}] [order-ascending]
[time-zone-utc] [acknowledged-included] [start <yyyy-mm-dd>
[<hh:mm[:ss]>]] [end <yyyy-mm-dd> [<hh:mm[:ss]>]]
show log {<source-type> [<source-id>] | all} [minimum-severity
{critical | major | minor | warning | cleared}] [order-ascending]
[time-zone-utc] [acknowledged-included] [last-seconds <seconds> |
last-entries <entries>]
Alarms and Events Supported by Device

The following table shows the alarms and events supported by ETX-1, along with
the traps corresponding to each alarm/event. For more information on the traps,
refer to Table 11-2.
Table 11-1. Alarms and Events
Name Description A=Alarm ID Source Trap

E=Event
sw_install_start Start software install E 1020001 system systemSoftwareInstallStart
sw_install_end End software install E 1020002 system systemSoftwareInstallEnd
download_end End download E 1020003 system systemDownloadEnd
user_reset System user reset E 1020004 system systemUserReset


E=Event
alternate_configuration_l {startup-config | E 1020005 system systemAlternateConfigLoaded

oaded user-default-config |
factory-default-config
| rollback-config}
loaded as
running-config
configuration_migration <configuration file> E 1020006 system systemConfigurationMigration

conversion <ended
successfully/ended
with errors failed>
after software
upgrade
configuration_sanity Configuration sanity E 1020007 system systemConfigurationSanity

in <configuration
file>: configuration
<loaded/rejected/
loaded till first error>
trap_hard_sync_start Trap synchronization E 1020008 system systemTrapHardSyncStart

hard sync process
started
trap_hard_sync_end Trap synchronization E 1020009 system systemTrapHardSyncEnd

hard sync process
ended
configuration_change_m Configuration change E 1020010 system systemConfigurationChangeM

ask mask ask
configuration_change_un Configuration change E 1020011 system systemConfigurationChangeU

mask unmask nmask
dying_gasp Dying gasp E 1020012 system systemDyingGasp
dying_gasp_recovery Device recovered from E 1020013 system systemDyingGaspRecovery

dying gasp without
rebooting
trace_msg_fatal_error Fatal error E 1020014 system systemTraceMsgFatalError
trace_msg_exception Exception E 1020015 system systemTraceMsgException
trace_msg_sw_watchdog_ Software watchdog E 1020016 system systemTraceMsgSwWatchdog

reset reset Reset
backup_configuration_loa Device configuration E 1020017 system systemBackupConfigurationLo

ded loaded from backup aded
database
device_startup Device startup due to E 1020018 system systemDeviceStartup

cold start coldStart
successful_login Successful login E 1020022 system systemSuccessfulLogin


E=Event
failed_login Failed login E 1020023 system systemFailedLogin
logout Logout due to E 1020024 system systemLogout

inactivity
rfc2544_test_start RFC2544 test ID E 1020025 system systemRfc2544TestStart

started
rfc2544_test_end RFC2544 test ID E 1020026 system systemRfc2544TestEnd

ended
startup_config_unconfir New startup-config E 1020028 system systemStartupConfigUnconfir

med not confirmed med
active_software_changed Active software E 1020029 system systemActiveSoftwareChange

changed from last d
reboot
running_config_saved Running configuration E 1020030 system systemRunningConfigSaved

saved to startup
configuration
sfp_opt_ora Optical power E 1050001 Ethernet sfpOptOra

transmitted (OPT) out
of range
sfp_opt_ora_off Optical power E 1050002 Ethernet sfpOptOraOff

transmitted (OPT) in
permitted range
sfp_lbc_ora Laser bias current E 1050003 Ethernet sfpLbcOra

(LBC) out of range
sfp_lbc_ora_off Laser bias current E 1050004 Ethernet sfpLbcOraOff

(LBC) in permitted
range
bridge_new_root New Root is detected E 1170001 Bridge bridgeSpanningTreeNewRoot
bridge_top_change Topology change is E 1170002 Bridge bridgeSpanningTreeTopologyC

detected hange
sub_group_switchover Switchover between E 1250001 LAG lagSubGroupSwitchover

sub-groups of inter-
card LAG
lag_failure All LAG member ports E 1250002 LAG lagFailure

are down
remote_loopback Loopback started E 1270101 oam-efm oamEfmRemoteLoopback
remote_loopback_off Loopback ended E 1270102 oam-efm oamEfmRemoteLoopbackOff
delay_tca Delay threshold E 1270401 oam- oamCfmDestNeDelayTca

crossing alert cfm-
dest-ne


E=Event
delay_tca_off Delay in permitted E 1270402 oam- oamCfmDestNeDelayTcaOff

range cfm-
dest-ne
delay_var_tca Delay variance E 1270403 oam- oamCfmDestNeDelayVarTca

threshold crossing cfm-
alert dest-ne
delay_var_tca_off Delay variance in E 1270404 oam- oamCfmDestNeDelayVarTcaOf

permitted range cfm- f
dest-ne
loss_ratio_tca Loss ratio threshold E 1270405 oam- oamCfmDestNeLossRatioTca

crossing alert cfm-
dest-ne
loss_ratio_tca_off Loss ratio in E 1270406 oam- oamCfmDestNeLossRatioTcaO

permitted range cfm- ff
dest-ne
loss_ratio_tca_fe Loss ratio threshold E 1270407 oam- oamCfmDestNeLossRatioTcaF

crossing alert at far- cfm- e
end dest-ne
loss_ratio_tca_fe_off Loss ratio in E 1270408 oam- oamCfmDestNeLossRatioTcaF

permitted range at cfm- eOff
far-end dest-ne
unavailable_ratio_tca Unavailable ratio E 1270409 oam- oamCfmDestNeUnavailRatioTc

threshold crossing cfm- a
alert dest-ne
unavailable_ratio_tca_off Unavailable ratio in E 1270410 oam- oamCfmDestNeUnavailRatioTc

permitted range cfm- aOff
dest-ne
unavailable_ratio_tca_fe Unavailable ratio E 1270411 oam- oamCfmDestNeUnavailRatioTc

threshold crossing cfm- aFe
alert at far-end dest-ne
unavailable_ratio_tca_fe_ Unavailable ratio in E 1270412 oam- oamCfmDestNeUnavailRatioTc

off permitted range at cfm- aFeOff
far-end dest-ne
erp_port_state_change ERP {east|west} port E 1291101 ERP port erpPortStateChange

state changed to
<blocked/unblocked>
device_temperature_ora Device temperature A 20002 system systemDeviceTemperatureOra

has crossed threshold
configuration_mismatch Configuration A 20004 system systemConfigurationMismatch

mismatch
hardware_failure Hardware failure A 20005 system systemHardwareFailure


E=Event
interface_mismatch Optical interface not A 20006 system systemInterfaceMismatch

supported or
misconfigured
no_interface Interface not installed A 20007 system systemNoInterface
sw_pack_corrupted Software file <sw file A 20008 system systemSwPackCorrupted

name> corrupted
hardware_failure_fe Hardware failure at A 20012 system systemFeHardwareFailure

far-end
configuration_mismatch_ Configuration A 20013 system systemFeConfigurationMismat

fe mismatch at far-end ch
interface_mismatch_fe Optical interface not A 20014 system systemFeInterfaceMismatch

supported or
misconfigured at far-
end
no_interface_fe Interface not installed A 20015 system systemFeNoInterface

at far-end
power_delivery_failure Power supply failure A 20201 system powerDeliveryFailure
power_in_ora Power-in out of range A 20202 power powerInOra

supply
power_in_low Input power near A 20203 power powerInLow

minimum supply
sfp_no_response Loss of A 50001 Ethernet sfpNoResponse

communication with
SFP
sfp_mismatch SFP mismatch A 50002 Ethernet sfpMismatch
los Loss of signal (LOS) A 50003 Ethernet linkUp/linkDown

ethLos
sfp_removed SFP not installed A 50004 Ethernet sfpRemoved
sfp_temperature_ora Laser temperature out A 50005 Ethernet sfpTemperatureOra

of range
sfp_opr_ora Optical power A 50006 Ethernet sfpOprOra

received (OPR) out of
range
fault_propagation Fault propagation A 50007 Ethernet faultPropagation
auto_negotiation_failure Auto-negotiation A 50008 Ethernet ethAutoNegotiationFailure

failed to synchronize
with remote device
los_fe Loss of signal (LOS) at A 50009 Ethernet ethFeLos

far-end


E=Event
fault_propagation_fe Fault propagation at A 50010 Ethernet feFaultPropagation

far-end
link_down Link down A 270101 oam-efm oamEfmLinkDown
link_fault_indication Link fault indication A 270102 oam-efm oamEfmLinkFaultIndication
link_fault_indication_fe Link fault indication at A 270103 oam-efm oamEfmFeLinkFaultIndication

far-end
critical_link_indication Critical link indication A 270104 oam-efm oamEfmCriticalLinkIndication
critical_link_indication_fe Critical link indication A 270105 oam-efm oamEfmFeCriticalLinkIndicatio

at far-end n
dying_gasp_indication Dying gasp indication A 270106 oam-efm oamEfmDyingGaspIndication
dying_gasp_indication_fe Dying gasp indication A 270107 oam-efm oamEfmFeDyingGaspIndicatio

at far-end n
ais Alarm indication signal A 270201 oam- oamCfmMepAis

(AIS) <mep name> cfm-mep
lck Lock (LCK) <mep A 270202 oam- oamCfmMepLck

name> cfm-mep
mismatch Mismatch due to A 270203 oam- oamCfmMepMismatch

<mismerge/ cfm-mep
unexpected MEP/
unexpected MEG level/
unexpected period>
loc Loss of continuity A 270601 oam- oamCfmRmepLoc

(LOC) <mep name> cfm-mep
rdi Remote defect A 270602 oam- oamCfmRmepRdi

indication (RDI) <mep cfm-mep
name>
erp_state_protected ERP ring state A 290301 ERP erpStateProtected

changed to protected
Traps Supported by Device

The following table shows the traps supported by ETX-1, along with the
alarm/event corresponding to each trap. For more information on the
alarm/event, refer to Table 11-1.
Note All traps are maskable, by masking the corresponding alarm/event via the
alarm-source-attribute / alarm-source-type-attribute commands, or by masking
the corresponding alarm per severity via the mask-minimum-severity command.
For details, refer to Configuring Alarm and Event Properties.

Table 11-2. Traps
Trap Name Trap OID Alarm/Event Name A=Alarm Alarm/ Alarm/

E=Event Event ID Event
Source
coldStart 1.3.6.1.6.3.1.1.5.1 device_startup E 1020018 system
systemSoftwareInstallSt 1.3.6.1.4.1.164.6.1.0.42 sw_install_start E 1020001 system

art
systemSoftwareInstallEn 1.3.6.1.4.1.164.6.1.0.43 sw_install_end E 1020002 system

d
systemDownloadEnd 1.3.6.1.4.1.164.6.2.12.18 download_end E 1020003 system

.0.2
systemUserReset 1.3.6.1.4.1.164.6.1.0.82 user_reset E 1020004 system
systemAlternateConfig 1.3.6.1.4.1.164.6.1.0.45 alternate_configuratio E 1020005 system

Loaded n_loaded
systemConfiguration 1.3.6.1.4.1.164.6.1.0.47 configuration_sanity E 1020007 system

Sanity
systemTrapHardSync 1.3.6.1.4.1.164.6.1.0.77 trap_hard_sync_start E 1020008 system

Start
systemTrapHardSync 1.3.6.1.4.1.164.6.1.0.78 trap_hard_sync_end E 1020009 system

End
systemDyingGasp 1.3.6.1.4.1.164.6.1.0.49 dying_gasp E 1020012 system
systemTraceMsgFatalErr 1.3.6.1.4.1.164.6.1.0.51 trace_msg_fatal_error E 1020014 system

or
systemTraceMsgExceptio 1.3.6.1.4.1.164.6.1.0.52 trace_msg_exception E 1020015 system

n
systemDeviceStartup 1.3.6.1.4.1.164.6.1.0.55 device_startup E 1020018 system
systemSuccessfulLogin 1.3.6.1.4.1.164.6.1.0.70 successful_login E 1020022 system
systemFailedLogin 1.3.6.1.4.1.164.6.1.0.71 failed_login E 1020023 system
systemLogout 1.3.6.1.4.1.164.6.1.0.72 logout E 1020024 system
systemStartupConfigUnc 1.3.6.1.4.1.164.6.1.15.0. startup_config_unconfi E 1020028 system

onfirmed 4 rmed
systemActiveSoftwareCh 1.3.6.1.4.1.164.6.1.15.0. active_software_chang E 1020029 system

anged 5 ed
systemRunningConfigSa 1.3.6.1.4.1.164.6.1.0.84 running_config_saved E 1020030 system

ved
bridgeSpanningTreeNew 1.3.6.1.4.1.164.4.0.1 bridge_new_root E 1170001 Bridge

Root
bridgeSpanningTreeTopo 1.3.6.1.4.1.164.4.0.2 bridge_top_change E 1170002 Bridge

logyChange


Source
oamEfmRemoteLoopbac 1.3.6.1.4.1.164.3.1.6.1.0. remote_loopback E 1270101 oam-efm

k 17
oamEfmRemoteLoopbac 1.3.6.1.4.1.164.3.1.6.1.0. remote_loopback_off E 1270102 oam-efm

kOff 19
oamCfmDestNeDelayTca 1.3.6.1.4.1.164.3.1.6.1.3. delay_tca E 1270401 oam-cfm-

0.9 dest-ne
oamCfmDestNeDelayTca 1.3.6.1.4.1.164.3.1.6.1.3. delay_tca_off E 1270402 oam-cfm-

Off 0.10 dest-ne
oamCfmDestNeDelayVar 1.3.6.1.4.1.164.3.1.6.1.3. delay_var_tca E 1270403 oam-cfm-

Tca 0.11 dest-ne
oamCfmDestNeDelayVar 1.3.6.1.4.1.164.3.1.6.1.3. delay_var_tca_off E 1270404 oam-cfm-

TcaOff 0.12 dest-ne
oamCfmDestNeLossRati 1.3.6.1.4.1.164.3.1.6.1.3. loss_ratio_tca E 1270405 oam-cfm-

oTca 0.13 dest-ne
oamCfmDestNeLossRati 1.3.6.1.4.1.164.3.1.6.1.3. loss_ratio_tca_off E 1270406 oam-cfm-

oTcaOff 0.14 dest-ne
oamCfmDestNeLossRati 1.3.6.1.4.1.164.3.1.6.1.3. loss_ratio_tca_fe E 1270407 oam-cfm-

oTcaFe 0.15 dest-ne
oamCfmDestNeLossRati 1.3.6.1.4.1.164.3.1.6.1.3. loss_ratio_tca_fe_off E 1270408 oam-cfm-

oTcaFeOff 0.16 dest-ne
oamCfmDestNeUnavailR 1.3.6.1.4.1.164.3.1.6.1.3. unavailable_ratio_tca E 1270409 oam-cfm-

atioTca 0.17 dest-ne
oamCfmDestNeUnavailR 1.3.6.1.4.1.164.3.1.6.1.3. unavailable_ratio_tca_o E 1270410 oam-cfm-

atioTcaOff 0.18 ff dest-ne
oamCfmDestNeUnavailR 1.3.6.1.4.1.164.3.1.6.1.3. unavailable_ratio_tca_f E 1270411 oam-cfm-

atioTcaFe 0.19 e dest-ne
oamCfmDestNeUnavailR 1.3.6.1.4.1.164.3.1.6.1.3. unavailable_ratio_tca_f E 1270412 oam-cfm-

atioTcaFeOff 0.20 e_off dest-ne
erpPortStateChange 1.3.6.1.4.1.164.3.1.6.1.0. erp_port_state_change E 1291101 ERP port

5
systemDeviceTemperatu 1.3.6.1.4.1.164.6.1.0.41 device_temperature_or A 20002 system

reOra a
systemSwPackCorrupted 1.3.6.1.4.1.164.6.1.0.61 sw_pack_corrupted A 20008 system
powerDeliveryFailure 1.3.6.1.4.1.164.6.1.0.73 power_delivery_failure A 20201 power

supply
linkDown 1.3.6.1.6.3.1.1.5.4 los A 50003 Ethernet
linkUp 1.3.6.1.6.3.1.1.5.3 los A 50003 Ethernet


Source
ethLos 1.3.6.1.4.1.164.3.1.6.1.0. los A 50003 Ethernet

1
sfpRemoved 1.3.6.1.4.1.164.40.3.4.0. sfp_removed A 50004 Ethernet

3
oamEfmLinkFaultIndicati 1.3.6.1.4.1.164.3.1.6.1.0. link_fault_indication A 270102 oam-efm

on 20
oamEfmFeLinkFaultIndic 1.3.6.1.4.1.164.3.1.6.1.0. link_fault_indication_fe A 270103 oam-efm

ation 21
oamEfmCriticalLinkIndica 1.3.6.1.4.1.164.3.1.6.1.0. critical_link_indication A 270104 oam-efm

tion 22
oamEfmFeCriticalLinkIndi 1.3.6.1.4.1.164.3.1.6.1.0. critical_link_indication_f A 270105 oam-efm

cation 23 e
oamEfmDyingGaspIndica 1.3.6.1.4.1.164.3.1.6.1.0. dying_gasp_indication A 270106 oam-efm

tion 24
oamEfmFeDyingGaspIndi 1.3.6.1.4.1.164.3.1.6.1.0. dying_gasp_indication_ A 270107 oam-efm

cation 25 fe
oamCfmMepAis 1.3.6.1.4.1.164.3.1.6.1.3. ais A 270201 oam-cfm-

0.4 mep
oamCfmMepLck 1.3.6.1.4.1.164.3.1.6.1.3. lck A 270202 oam-cfm-

0.5 mep
oamCfmMepMismatch 1.3.6.1.4.1.164.3.1.6.1.3. mismatch A 270203 oam-cfm-

0.6 mep
oamCfmRmepLoc 1.3.6.1.4.1.164.3.1.6.1.3. loc A 270601 oam-cfm-

0.7 mep
oamCfmRmepRdi 1.3.6.1.4.1.164.3.1.6.1.3. rdi A 270602 oam-cfm-

0.8 mep
erpStateProtected 1.3.6.1.4.1.164.3.1.6.1.0. erp_state_protected A 290301 ERP

4
authenticationFailure 1.3.6.1.6.3.1.1.5.5 Not applicable -- -- --
Configuring the Global Performance Monitoring Function

To configure the global PM collection:
2. Enter all necessary commands according to the tasks listed below:

Configuring the global pm no pm command disables the

performance monitoring data global PM function.
collection
Configuring the interval of PM pm-collection {eth |oam-cfm-service|dest-

collection for each type ne} interval <seconds>
11.3 Syslog
ETX-1 uses the Syslog protocol to generate and transport event notification
messages over IP networks to Syslog servers. The Syslog operation is compliant
with the RFC 3164 requirements.
Configuring Syslog Parameters

To configure syslog parameters:
1. Navigate to the system context (config>system).
2. Define syslog device parameters:
a. Enter:
syslog device
The system switches to the syslog device context
(config>system>syslog(device))
b. Specify the module, task, or function from which syslog messages are
sent:
facility {local1 | local2 | local3 | local4 | local5 | local6 | local7}
Default: local1
c. Specify the UDP port that transmits syslog messages (allowed only if
syslog message transmitting is administratively disabled):
port <udp-port-number>
Allowed values: 165535
Default: 514
d. Specify the severity level. The log messages that contain severity level up
to the specified level are transmitted:
severity-level {emergency | alert | critical | error | warning | notice |
informational | debug}
e. Administratively enable the transmitting of syslog messages:
no shutdown
3. Define syslog server parameters:
a. Specify the syslog server to receive syslog messages, from 1 to 5:
syslog server <server-id>.
11-14 Syslog ETX-1 Ver. 1.2

The system switches to the context of the specified syslog server

(config>system>syslog(server/<server-id>)).
b. Specify the IP address of the server (allowed only if the server is
administratively disabled):
address <ip-address>
Allowed values: IP address except 0.0.0.0 and 255.255.255.255
c. Specify the UDP port on the server that receives syslog messages
(allowed only if the server is administratively disabled):
port <udp-port-number>
Allowed values: 165535
d. Administratively enable the server:
no shutdown
e. Enter exit to exit the server context.
The system switches to the system context (config>system).
Displaying Syslog Statistics

To display syslog statistics:
1. At the system context (config>system), enter:
syslog device
The system switches to the syslog device context
(config>system>syslog(device))
2. Enter:
show statistics.
3. Syslog statistics appear as shown below. The counters are described in
Table 11-3.
ETX-1>config>system>syslog(device)# show statistics
Total Tx Messages : 356
Non-queued Dropped Messages : 265
4. To clear the statistics, enter:
clear-statistics.
Table 11-3. Syslog Statistic Parameters
Total Tx Messages The total number of syslog messages transmitted
Non-queued Dropped The total number of syslog messages that were

Messages dropped before being queued
ETX-1 Ver. 1.2 Syslog 11-15

11.4 Troubleshooting
This section contains a general troubleshooting chart that lists possible failures
and provides workarounds.
Troubleshooting Chart
Use this chart to identify the cause of a problem that may arise during operation.
For detailed description of the LED indicators functions, refer to Chapter 3.
To correct the reported problem, perform the suggested corrective actions. If a
problem cannot be resolved by performing the suggested action, please contact
your RAD distributor.
Table 11-4. Troubleshooting Chart
Fault/Problem Probable Cause Corrective Action
The unit is dead No power Verify that both ends of the power cable are properly
(POWER LED is off) connected.
Blown fuse Disconnect the power cable from both ends and replace
the fuse with another fuse of proper rating.
The event log reports a View the inventory file by entering show inventory at
fan or power supply the config>system prompt.
error. Restart the unit.
In case of failure, replace the entire unit.
The unit is unreachable Incorrect Using a local serial connection, enable the relevant
management management access type by entering telnet, snmp,
settings and/or ssh at the config>mngmnt>access prompt.
View the list of enabled management access types and
settings by entering info detail at the config>mngmnt
prompt
Verify that a router interface has been configured with
management access set to allow all, assigned an IP
address, and bound to an administratively enabled SVI.
Verify that management flows have been set up
to/from the SVI, and that the flows are enabled
Verify that the default gateway is configured in the
router.
Management path In case of remote management, analyze this issue using

disconnected a local serial connection
At the current prompt, check whether the desired unit
responds by entering ping <IP address>
Check network connectivity issues and firewall settings
Verify that the management flows have been
configured correctly.
11-16 Troubleshooting ETX-1 Ver. 1.2

Fault/Problem Probable Cause Corrective Action
Physical link fails to Link may be Administratively enable the link

respond administratively In case of Ethernet links, make sure that the
disabled. autonegotiation, speed, and duplex modes match the
configured values on the access switch/router.
Ethernet LINK LED Ethernet cable Check the Ethernet cable to see whether a cross or
is off problem straight cable is needed
Check/replace Ethernet cable
Verify that the range is within the limits
Check the port by connecting the remote end of the
cable to a different switch
Send the unit for repair.
11.5 Performing Diagnostic Tests

This section describes general diagnostic tests. For information on testing ports,
refer to Chapter 6. For information on testing OAM CFM, refer to Chapter 8.
Running a Ping Test

You can ping a remote IP host to check the ETX-1 IP connectivity with that host.
To ping an IP host:
1. In any level, start pinging the desired host specifying its IP address, optionally
the number of packets to send and the size of the payload in bytes:
ping <ip-address> [number-of-packets <packets>] [payload-size <bytes]
Allowed value: ip-address - 1.1.1.1255.255.255.255
packets 1-10000
bytes - 32-1450
Tracing the Route

This diagnostic utility traces the route through the network from ETX-1 to the
destination host. The trace route utility supports up to 30 hops.
To trace a route:
In any level, start the trace route and specify the IP address of the host to
which you intend to trace route:
trace-route <ipaddress>
Allowed value: ip-address - 1.1.1.1255.255.255.255
ETX-1 Ver. 1.2 Performing Diagnostic Tests 11-17

11.6 Frequently Asked Questions
Q How should ETX-1 be configured for management?

A You need to configure a router interface for management by assigning it an
IP address, and binding it to an SVI for which management flows have been
configured. Additionally, you need to configure the default gateway address
in the router. Refer to the Quick Start Guide for an example of configuring
ETX-1 for management.
11.7 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!
11-18 Technical Support ETX-1 Ver. 1.2

Chapter 12
Software Upgrade
This chapter explains how to upgrade ETX-1.
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 device can store up to two software images, referred to as software packs
and named sw-pack-1 through sw-pack-2. You can designate any of the software
packs as active. The non-active software packs serve as backups that can be used
if the active software becomes corrupted.
12.1 Compatibility Requirements

Following are the software releases that can be upgraded to new version. The
hardware revisions that can accept the latest software version are also listed.
Software 1.0 and above
Hardware 2.0
12.2 Impact
ETX-1 resets automatically after the software upgrade, resulting in up to
two minutes of downtime.
Upgrading to a new version does not affect any user settings after saving the
user settings.
12.3 Prerequisites
Before starting the upgrade, verify that you have the following:
For upgrade via SFTP/FTP/TFTP:
Operational ETX-1 unit with valid IP parameters configured
Connection to a PC with an SFTP/FTP/TFTP server application and a valid IP
address
Software image file stored on the PC. The image file (and exact name)
can be obtained from the local RAD business partner from whom the
device was purchased.
ETX-1 Ver. 1.2 Prerequisites 12-1

Chapter 12 Software Upgrade Installation and Operation Manual
For upgrade via XMODEM:

Operational ETX-1 unit
Connection to a PC via a terminal emulation program
Software image file stored on the PC. The image file (and exact name)
can be obtained from the local RAD business partner from whom the
device was purchased.
12.4 Upgrading the Device Software via CLI

The recommended software downloading method is to use the copy command.
Network administrators can use this procedure to distribute new software
releases to all the managed ETX-1 units in the network from a central location.
ETX-1
ETX-1
Figure 12-1. Downloading a Software Application File
Use the following procedure to download new release to ETX-1 via CLI.
1. Verify that the image file is stored on the PC with the SFTP/TFTP server
application.
2. Verify that the ETX-1 router has been configured with valid IP parameters.
3. Ping the PC to verify the connection.
4. Activate the SFTP/TFTP server application.
5. Download the image file from the PC to ETX-1.
Note Configuration values shown in this chapter are examples only.
Verifying the Host Parameters

In order to establish communication with the SFTP/TFTP server, the ETX-1 router
must have IP parameters configured according to your network requirements.
Refer to the following manual sections for additional information:
Connecting to ASCII Terminal in Chapter 2
Working with Terminal in Chapter 4
Configuring the Router in Chapter 8.
Pinging the PC
Check the integrity of the communication link between ETX-1 and the PC by
pinging the PC from ETX-1.
12-2 Upgrading the Device Software via CLI ETX-1 Ver. 1.2
Installation and Operation Manual Chapter 12 Software Upgrade
To ping the PC:

1. In any level, start pinging the PC specifying its IP address and optionally the
number of packets to send:
ping <ip-address> [number-of-packets <packets>] [payload-size <bytes>]
A reply from the PC indicates a proper communication link.
2. If the ping request times out, check the link between ETX-1 and the PC
(physical path, configuration parameters, etc.)
Activating the SFTP Server

Once the SFTP server is activated on the PC, it waits for any SFTP file transfer
request originating from the product, and performs the received request
automatically.
SFTP file transfers use TCP port 22. Make sure that the firewall on the server
allows communication through this port (refer to Chapter 10 for details).
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 performs the received request
automatically.
TFTP file transfers use port 69. Make sure that the firewall on the server allows
communication through this port (refer to Chapter 10 for details).
Downloading the Software

This procedure is used to download the new software release.
To copy the file to the ETX-1 unit:

In any level, enter:
copy sftp://<username>:<password>@<host>:<port>/<source-file>
<destination-file>
Where <host> is the IP address of the PC where the SFTP server is installed,
<source-file> is the image file name and <destination-file> is the desired
software pack name.
Or
copy tftp://<host>/<source-file> <destination-file>
Where <host> is the IP address of the PC where the TFTP server is installed,
<source-file> is the image file name, and <destination-file> is the name of
the software pack.
Note Choose an index that is not being used by the active software or by a software
pack that you do not want to overwrite.
The software download is performed. Refer to Installing Software for instructions

on installing the downloaded software as the active software.
ETX-1 Ver. 1.2 Upgrading the Device Software via CLI 12-3
Installing Software
After software is downloaded to ETX-1, it must be installed via the install
command as the active software. When you install software, ETX-1 by default
creates a restore point, so that you can perform a rollback to the previous
software pack if there is a problem with the new software pack.
Note The file startup-config must exist before you can install software with creation of
a restore point.
You can request (using command software-confirm-required) that the next

installed software be confirmed after the next reboot. After you execute the
request, the next time ETX-1 reboots and loads the new software, you will need
to confirm the software (using command software-confirm) within the configured
timeout period. If the confirmation is not received before timeout, ETX-1
automatically falls back to its previous software.
To request software confirmation:

At the admin>software# prompt, enter:
software-confirm-required [time-to-confirm <minutes>]
The confirmation timeout range is five minutes to 24 hours. If you do not
specify it, the default is five minutes.
Note You can cancel the software confirmation request by entering

no software-confirm-required
The next time ETX-1 reboots and loads new software, it starts a confirmation
timer. The next procedure has more details on the confirmation.
To install a software pack as active:
Note If startup-config does not exist, you must install the software pack without
creating a restore point.
1. At the admin>software# prompt, enter:

install <filename> [no-restore-point]
The parameter <filename> can be any of the non-active software packs
(sw-pack-1 through sw-pack-2). If you specify no-restore-point, it will not be
possible to rollback to the previous software after the software is installed.
!Device will install file and reboot. Are you sure? [yes/no] _
If a restore point is being created, then startup-config is copied to
restore-point-config. ETX-1 designates the specified software pack as
active, and then reboots.
3. If a software confirmation request is active, ETX-1 starts a timer with the
specified timeout period.
Note While the confirmation timer is running, ETX-1 does not allow any commands that
change its configuration.
12-4 Upgrading the Device Software via CLI ETX-1 Ver. 1.2
4. If the software-confirm command is entered before the timer expires, the

software is considered to be confirmed.
5. If the software-confirm command is not entered before the timer expires,
then restore-point-config is deleted, ETX-1 designates the previously active
software pack as active, and then reboots.
Restoring Previous Active Software

If the installed software malfunctions and was installed with a restore point, you
can perform rollback to the previous active software.
To rollback to the previous active software pack:

1. At the admin>software# prompt, enter:
undo-install
! Falling back to restore point ! Are you sure? [yes/no] _
The file restore-point-config is renamed to startup-config. ETX-1
designates the previously active software pack as active, then reboots.
12.5 Upgrading the Device Software via the Boot

Menu
Software downloading can also be performed using the Boot menu. The Boot
menu can be reached while ETX-1 performs initialization, for example, after
power-up.
You may need to start the loading from the Boot menu if you are unable to use
the copy command (because, for example, the ETX-1 software has not yet been
downloaded or is corrupted).
Caution The Boot menu procedures are recommended for use only by authorized
personnel, because this menu has many additional options that are intended for
use only by technical support personnel.
The following 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.
ETX-1
ETX-1
Figure 12-2. Downloading a Software Application File via XMODEM
ETX-1 Ver. 1.2 Upgrading the Device Software via the Boot Menu 12-5
Downloading using FTP/TFTP. This is usually performed by downloading from

a remote location that provides an IP communication path to an Ethernet port
of ETX-1.
Accessing the Boot Menu

The boot menu can be accessed when the device is powered up, before logging
in.
To access the Boot menu:

1. Configure the communication parameters of the selected PC serial port for
asynchronous communication with 9,600 bps, no parity, one start bit, eight
data bits and one stop bit. Turn all types of flow control off.
2. Turn off ETX-1.
3. Activate the terminal application.
4. Turn on ETX-1 and immediately start pressing the <Enter> key several times
in sequence until you see the prompt to press any key to stop the autoboot.
5. Press any key.
The boot screen appears. A typical boot screen is shown below (the exact
version and date displayed by your ETX-1 unit may be different). You can
type ? to display the available commands.
Note If you miss the timing, ETX-1 performs a regular reboot process (this process
starts with Loading and ends with the login screen).
System Boot
Copyright 1984-2008 RAD Data Communications, Ltd.
Boot version: 1.06 [05-Jul-11]
CPU : Freescale MPC8313E

OS version : VxWorks 6.7
BSP version: 1.17
Boot-Manager version: 1.00.00 [14-May-12]
Use '?'/help to view available commands
Press any key to stop auto-boot...

6
[boot]:
Figure 12-3. Boot Menu
12-6 Upgrading the Device Software via the Boot Menu ETX-1 Ver. 1.2
[boot]: ?
Commands:
?/help - print this list
p - print boot parameters
c [param] - change boot parameter(s)
v - print boot logo with versions information
run - load active sw pack and execute
delete <FileName> - delete a file
dir - show list of files
show <index> - show sw pack info
download <index> [,<FileName|x>] - download a sw pack to specific index (x -
by Xmodem)
set-active <index> - Set a sw pack index to be the active
application
control-x/reset - reboot/reset
Figure 12-4. Displaying Boot Commands
Using the XMODEM Protocol

Use the following procedure to download new release to ETX-1 via XMODEM.
To download software release via XMODEM:

1. Verify that the image file is stored on the PC with the terminal application.
2. At the boot prompt, enter:
download <index>, x
Where <index> can be 12 and corresponds to the desired software pack
number.
Note Choose an index that is not being used by the active software, or by a software
pack that you do not want to overwrite.
The process starts, and the following is displayed:

The terminal will become disabled !!!
Please send the file in XMODEM
3. 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-1 software file name (you may 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, repeat the whole procedure.
ETX-1 Ver. 1.2 Upgrading the Device Software via the Boot Menu 12-7
When the downloading process has successfully completed, a sequence

of messages similar to the following is displayed:
File writing to flash: - 3140KB
File downloaded successfully to :2
4. Refer to Activating Software for instructions on activating the downloaded
software.
Using FTP
Use the following procedure to download new release to ETX-1 via FTP.
To download software release via FTP:

1. At the boot prompt, use the c command to configure the FTP parameters as
needed.
download <index>,<FileName>
Where <index> can be 12, and corresponds to the desired software pack
number.
Note Choose an index that is not being used by a software pack that you do not want
to overwrite.
If no errors are detected, the downloading process starts, and the file is
downloaded via FTP.
software.
Using TFTP
Use the following procedure to download new release to ETX-1 via TFTP.
To download software release via TFTP:

1. At the boot prompt, use the c command to configure the TFTP parameters as
needed.
download <index>,<FileName>
Where <index> can be 12, and corresponds to the desired software pack
number.
Note Choose an index that is not being used by a software pack that you do not want
to overwrite.
If no errors are detected, the downloading process starts, and the file is
downloaded via TFTP.
software.
12-8 Upgrading the Device Software via the Boot Menu ETX-1 Ver. 1.2
Activating Software
To activate a software pack, you need to designate it as active and load it.
To activate a software pack:

1. To set the software as active, enter:
set-active <index>.
A confirmation similar to the following is displayed:
SW set active 2 completed successfully.
2. To load the active software, type: run
A sequence of messages similar to the following is displayed:
Loading/un-compressing sw-pack-2..
Starting the APPLICATION off address 0x10000...
After a few more seconds, the login prompt is displayed.
12.6 Verifying Upgrade Results

To verify that the upgrade was successful, log on to ETX-1 via a terminal
emulation program to view the Inventory table (show summary-inventory at
prompt config>system#), and verify the active software version in the SW Rev
column.
ETX-1 Ver. 1.2 Verifying Upgrade Results 12-9

12-10 Verifying Upgrade Results ETX-1 Ver. 1.2

Chapter 13
Application Tutorial
13.1 Flow-Based Application

This section provides detailed instructions on configuring, and using a flow-based
point-to-point application. It provides instructions for enabling remote
connectivity to the management station, and running data traffic streams.
Site B Site A
ETX-1 ETX-1
192.168.100.56 192.168.100.57
Untagged 3 VLAN 100 VLAN 100 Untagged 3

Data Flow Data Flow
Video Flow IP Video Flow

Client PC Network Client PC
VLAN 4090 VLAN 4090
192.168.100.33 MNG Flow MNG Flow 192.168.100.36
Host Host
PC Server
192.168.100.99
Figure 13-1. Application Diagram
Configuring the ETX-1 Server
Accessing the Unit

2. Configure the ASCII terminal to the settings listed below, and then set the
terminal emulator to VT100 emulation for an optimal view of system menus.
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
3. Power-up ETX-1.
ETX-1 Ver. 1.2 Flow-Based Application 13-1

Chapter 13 Application Tutorial Installation and Operation Manual
5. Enter the user name for Super User and the associated password. The default
user name is su and the default password is 1234.
ETX-1#
Configuring Management Flow

The management flows are set up between the Network port 1 and SVI 1.
Configuring SVI

no shutdown
exit all
Configuring Classifier Profiles

configure flows
classifier-profile untagged match-any
match untagged
exit all
2. Create a profile that accepts only traffic tagged with VLAN 4090:
configure flows
match vlan 4090
exit all

Configure one flow named mn_out from SVI 1 to Network port 1 and the other
flow named mn_in from Network port 1 to SVI 1, using the above profiles,
adding/removing VLAN 4090:
# Flow from Network port 1 to SVI 1
classifier v4090
no policer
vlan-tag pop vlan
no shutdown
exit all
13-2 Flow-Based Application ETX-1 Ver. 1.2

Installation and Operation Manual Chapter 13 Application Tutorial
# Flow from SVI 1 to Network port 1

configure flows flow mn_out
classifier untagged
ingress-port svi 1
no shutdown
exit all
Configuring Router
The router must be configured with the router interface 1 that is bound to the
SVI 1 used for the management flows, and assigned the IP address
192.168.100.57 with mask 255.255.255.0.
configure router 1
interface 1
bind svi 1
address 192.168.100.57/24
no shutdown
exit all
Type save in any level to save your configuration.
Configuring Data Flow

configure flows
classifier-profile data_out match-any
match untagged
exit all
configure flows
classifier-profile data_in match-any
match vlan 100
exit all
Configuring Data Flows

Configure one flow named data_out from User port 3 to Network port 1 and the
other flow named data_in from Network port 1 to User port 3, using the above
profiles, adding/removing VLAN 100:

# Flow from Network port 1 to User port 3

configure flows flow data_in
classifier data_in
egress-port ethernet 3 queue 2 block0/1
vlan-tag pop vlan
no shutdown
exit all
# Flow from User port 3 to Network port 1

configure flows flow data_out
classifier data_out
no shutdown
exit all
Configuring the ETX-1 Client
Accessing the Unit

2. Configure the ASCII terminal to the settings listed below, and then set the
terminal emulator to VT100 emulation for an optimal view of system menus.
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
3. Power-up ETX-1.
5. Enter the user name for Super User and the associated password. The default
user name is su and the default password is 1234.
ETX-1#

The management flows are set up between the Network port 1 and SVI 1.

Configuring SVI

no shutdown
exit all

configure flows
classifier-profile untagged match-any
match untagged
exit all
configure flows
match vlan 4090
exit all

Configure one flow named mn_out from SVI 1 to Network port 1 and the other
flow named mn_in from Network port 1 to SVI 1, using the above profiles,
adding/removing VLAN 4090:
# Flow from Network port 1 to SVI 1
classifier v4090
no policer
vlan-tag pop vlan
no shutdown
exit all
# Flow from SVI 1 to Network port 1

configure flows flow mn_out
classifier untagged
ingress-port svi 1
no shutdown
exit all
Configuring Router
The router must be configured with the router interface 1 that is bound to the
SVI 1 used for the management flows, and assigned the IP address
192.168.100.56 with mask 255.255.255.0.


configure router 1
interface 1
bind svi 1
address 192.168.100.56/24
no shutdown
exit all
Configuring Data Flow

configure flows
classifier-profile data_out match-any
match untagged
exit all
configure flows
classifier-profile data_in match-any
match vlan 100
exit all
Configuring Data Flows

Configure one flow named data_out from User port 3 to Network port 1 and the
other flow named data_in from Network port 1 to User port 3, using the above
profiles, adding/removing VLAN 100:
# Flow from Network port 1 to User port 3
configure flows flow data_in
classifier data_in
egress-port ethernet 3 queue 2 block0/1
vlan-tag pop vlan
no shutdown
exit all
# Flow from User port 3 to Network port 1

configure flows flow data_out
classifier data_out
no shutdown
exit all

13.2 Ethernet Ring Protection

The section provides detailed instructions for configuring four ETX-1 units in a ring
topology (see Figure 13-2).
User
Equipment
Management Host IP
192.168.100.3
ETX-1 (D)
Ring Link Ring Link

Management Host IP Management Host IP
192.168.100.2 192.168.100.4
IP
Network
ETX-1 (A) Ring Protection ETX-1 (C)
NMS RPL owner Link (RPL) Ring Link User
192.168.100.10 RPL Port-GbE1 Equipment
ETX-1 (B)
Management Host IP
192.168.100.5
GbE1-East Port
User GbE2-West Port
Equipment
Figure 13-2. Four ETX-1 Units in Ethernet Ring
Equipment List
The following equipment is required to set up a typical ring application:
Four ETX-1 units
PC
Four straight Ethernet cables with RJ-45 connectors.
Installing the Units

Before starting configuration, install units as follows:
1. Connect the Net 1 and Net 2 ports of ETX-1 (A), ETX-1 (B), ETX-1 (C) and
ETX-1 (D) using straight Ethernet cables to form a ring (see Figure 13-3).
ETX-1 Ver. 1.2 Ethernet Ring Protection 13-7

Ring Link
ETX-1 (A) 2 1
(RPL owner RPL port: Net1)
ETX-1 (D)
Ring Protection Link
(RPL)
2 1
ETX-1 (B)
Ring Link
2 1
Ring Link
ETX-1 (C)
Net1-East Port
Net2-West Port 2 1
Figure 13-3. Connecting ETX-1 Units in a Ring
Configuration Sequence
The following configuration steps are needed when deploying the ETX-1 units in a
ring topology:
1. Configuring the management flow
2. Configuring bridge port
3. Defining the VLAN
4. Configuring ERP parameters and enabling the ring functionality
Table 13-1. Configuration Summary
Device Management Flow Ring Traffic
ETX-1 (A) Management IP: R-APS VLAN: 1234, VLAN priority: 1,

192.168.100.2 MEL: 1
VLAN ID: 4 East port type: RPL
Management flows between West port type: Node-port
user port 5 and svi 1 interface
ETX-1 (B) Management IP: R-APS VLAN: 1234, VLAN priority: 1,
192.168.100.3 MEL: 1
VLAN ID: 4 East port type: Node-port
Management flows between West port type: Neighbor
net port 1 and svi 1 interface
ETX-1 (C) Management IP: R-APS VLAN: 1234, VLAN priority: 1,
192.168.100.4 MEL: 1
ETX-1 (D) Management IP: R-APS VLAN: 1234, VLAN priority: 1,
192.168.100.5 MEL: 1
13-8 Ethernet Ring Protection ETX-1 Ver. 1.2

Configuring Ethernet Ring Protection

The following section explains the main configuration actions for a ring
application with ETX-1(A). The configuration procedure is similar to ETX-1(A) for
ETX-1(B), ETX-1(C) and ETX-1(D)

The configuration procedure is similar to Configuring Management Flow section of
this chapter.
Configuring Bridge Port

Bridge ports are used in the Ring, they should be configured as ingress-filtering.
config bridge 1
port 1
ingress-filtering
exit
port 2
ingress-filtering
exit all
Configuring VLAN
Create VLAN 4 for management flows and VLAN 12 for bridge traffic.
tagged-egress 3..6
exit
vlan 4
exit all
Configuring Ethernet Ring Protection
Note R-APS settings must be the same for other Ring nodes.
Only one port can be configured as RPL owner in the Ring.

port-type west node-port
port-type east rpl
bridge 1
east-port 1
west-port 2
data-vlan 12
data-vlan 4
no shutdown
exit all
ETX-1 Ver. 1.2 Ethernet Ring Protection 13-9

13-10 Ethernet Ring Protection ETX-1 Ver. 1.2

Appendix A
Connector Wire Data
A.1 Ethernet Connectors

The Ethernet electrical interface terminates in 8-pin RJ-45 connectors, of type
10/100/1000BaseT, wired in accordance with Table A-1. The connector supports
both MDI and MDIX modes.
Table A-1. 10/100/1000BaseT Connector Pinout
Pin MDI MDIX
1 A+ B+
2 A- B-
3 B+ A+
4 C+ D+
5 C- D-
6 B- A-
7 D+ C+
8 D- C-
A.2 MNG Connector

The ETX--1 Ethernet management port uses an electrical interface that
terminates in an RJ-45, 8-pin connector. The port supports MDI and MDIX modes.
Table A-2 lists the pin assignments.
Table A-2. MNG Pinout
Pin Designation Function
1 RxD+ Receive Data output, + wire
2 RxD Receive Data output, wire
3 TxD+ Transmit Data input, + wire
4,5 Not connected
ETX--1 Ver. 1.2 MNG Connector A-1

Appendix A Connector Wire Data Installation and Operation Manual
Pin Designation Function
6 TxD- Transmit Data input, wire
7,8 Not connected
A.3 Control Connector

The control terminal interface terminates with a V.24/RS-232 cable based on the
mini-USB connector.
A-2 Control Connector ETX--1 Ver. 1.2

Publication No. 659-200-08/13
Order this publication by Catalog No. 805021
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail [email protected]
North America Headquarters

900 Corporate Drive
Mahwah, NJ 07430, USA
Tel. 201-5291100
Toll free 1-800-4447234
Fax 201-5295777
E-mail [email protected]
www.rad.com

Manual Rad ETX-1

Uploaded by

Copyright:

Available Formats

Manual Rad ETX-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Rad ETX-1

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

19882013 RAD Data Communications Ltd. Publication No. 659-200-08/13

ii ETX-1 Ver. 1.2

General Safety Instructions

Protective ground: the marked lug or terminal should be connected to the

ETX-1 Ver. 1.2 iii

Handling Energized Products

General Safety Practices

iv ETX-1 Ver. 1.2

Connecting Data and Telecommunications Cables

Ports Safety Status

ETX-1 Ver. 1.2 v

Electromagnetic Compatibility (EMC)

vi ETX-1 Ver. 1.2

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Avertissement Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel,

Achtung Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In

ETX-1 Ver. 1.2 vii

Mise au rebut du produit

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

Instructions gnrales de scurit

Danger de choc lectrique ! Evitez tout contact avec la surface marque

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

viii ETX-1 Ver. 1.2

Manipuler des produits sous tension

Rgles gnrales de scurit

ETX-1 Ver. 1.2 ix

Connexion au courant du secteur

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

Agent In SNMP, this refers to the managed system.

x ETX-1 Ver. 1.2

ANSI American National Standards Institute.

APS (Automatic An automatic service restoration function by which a network senses

Backhaul Transporting traffic between distributed sites (typically access points)

Baud Unit of signaling speed equivalent to the number of discrete

Bipolar Signaling method in E1/T1 representing a binary 1 by alternating

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

Buffer A storage device. Commonly used to compensate for differences in

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

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

Carrier A continuous signal at a fixed frequency that is capable of being

CESoPSN Structure-aware TDM Circuit Emulation Service over Packet Switched

ETX-1 Ver. 1.2 xi

CLI Command Line Interface (CLI) is a mechanism for interacting with a

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

Congestion Control A resource and traffic management mechanism to avoid and/or

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

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

E1 Line A 2.048 Mbps line, common in Europe, that supports thirty-two

E3 The European standard for high speed digital transmission, operating

Encapsulation Encapsulating data is a technique used by layered protocols in which a

xii ETX-1 Ver. 1.2

Ethertype A two-octet field in an Ethernet frame that indicates type of the

Flow Control A congestion control mechanism

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