Etx-2 MN 0 Manual Etx 203A

OPERATION MANUAL
INSTALLATION AND
ETX-2
Carrier Ethernet Demarcation
Carrrier Ethernet Demarcation Version 6.5
ETX-2
Carrrier Ethernet Demarcation
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-2 and any
software components contained therein are proprietary products of RAD protected under
international copyright law and shall be and remain solely with RAD.
ETX-2 is a registered trademark of RAD. The ETX-2 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. RAD
products/technologies are protected by registered patents. To review specifically which product is
covered by which patent, please see ipr.rad.com. The RAD name, logo, logotype, the term
Distributed GM, and the product names MiNID, Optimux, Airmux, IPmux, and MiCLK 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-2. 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-2, based on
or derived in any way from the ETX-2. Your undertaking in this paragraph shall survive the
termination of this Agreement.
This Agreement is effective upon your opening of the ETX-2 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-2 and all copies and portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters North American Headquarters

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

Tel Aviv 69719, Israel Mahwah, NJ 07430, USA
Tel: 972-3-6458181 Tel: (201) 5291100, Toll free: 1-800-4447234
Fax: 972-3-6498250, 6474436 Fax: (201) 5295777
E-mail: market@rad.com E-mail: market@radusa.com
© 1988–2018 RAD Data Communications Ltd. Publication No. 666-200-05/18

Front Matter Installation and Operation Manual
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the ETX-2 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-2, and in no event shall RAD's
liability exceed the purchase price of the ETX-2.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to ETX-2 and for ensuring that replacements and other adjustments required in connection
with the said warranties are satisfactory.
Software components in the ETX-2 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-2 shall not
exceed the sum paid to RAD for the purchase of the ETX-2. 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 unit’s use, customers should provide for its
collection for reuse, recycling or other form of environmentally conscientious
disposal.
ii ETX-2 Carrrier Ethernet Demarcation

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.
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.
This symbol appears on the top of the ETX203AX model specially designed
for installation in a small cell cabinet.
Hot surface! Contact may cause burn. Do not touch.
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!
ETX-2 Carrrier Ethernet Demarcation iii

Caution Some products may be equipped with a replaceable battery. There is danger
of explosion if batteries are mishandled or incorrectly replaced. On systems
with replaceable batteries, replace only with the same manufacturer and type
or equivalent type recommended by the manufacturer per the instructions
provided in the product service manual. Do not disassemble batteries or
attempt to recharge them outside the system. Do not dispose of batteries
in fire. Dispose of batteries properly in accordance with the manufacturer’s
instructions and local regulations.
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.
The ETX203AX unit that is specially designed for small cell cabinets, is restricted to installation in
Restricted Access Locations only.
In Denmark, Finland, Norway and Sweden, the unit is restricted to installation by service personnel
in Restricted Access Locations only.
Apparatets stikprop skal tilsluttes en stikkontakt med jord, som giver forbindelse
DK
til stikproppens jord
FI Laite on liitettävä suojamaadoituskoskettimilla varustettuun pistorasiaan
NO Apparatet må tilkoples jordet stikkontakt
SE Apparaten skall anslutas till jordat uttag
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.
iv ETX-2 Carrrier Ethernet Demarcation

Connecting AC Mains
The following applies only to ETX203AM and ETX205A:
The unit may be equipped with surge protectors between the AC mains and
ground. The connection to the protective ground must be maintained
whenever the unit is connected to AC mains.
Warning
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be readily
disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF position.
When connecting the DC supply wires, first connect the ground wire to the corresponding terminal,
then the positive pole and last the negative pole. Switch the circuit breaker back to the ON
position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
ETX-2 Carrrier Ethernet Demarcation v

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:
10BaseT, 100BaseT, 1000BaseT, Ports which do not present a safety hazard. Usually
Unbalanced E1, E2, E3, STM, DS-2, up to 30 VAC or 60 VDC.
DS-3, S-Interface ISDN, Analog voice
E&M
xDSL (without feeding voltage), TNV-1 Telecommunication Network Voltage-1:
Balanced E1, T1, Sub E1/T1, POE Ports whose normal operating voltage is within the
limits of SELV, on which overvoltages from
telecommunications networks are possible.
FXS (Foreign Exchange Subscriber) TNV-2 Telecommunication Network Voltage-2:
Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are not possible. These
ports are not permitted to be directly connected to
external telephone and data lines.
FXO (Foreign Exchange Office), xDSL TNV-3 Telecommunication Network Voltage-3:
(with feeding voltage), U-Interface Ports whose normal operating voltage exceeds the
ISDN limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are possible.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both ends.
The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk, there
are restrictions on the diameter of wires in the telecom cables, between the equipment and the
mating connectors.
Caution To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention Pour réduire les risques s’incendie, utiliser seulement des conducteurs de
télécommunications 26 AWG ou de section supérieure.
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.
vi ETX-2 Carrrier Ethernet Demarcation

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 with the exception of 1000BaseT ports that must always use shielded
twisted pair cables of good quality (CAT 5E or higher). 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.
ETX-2 Carrrier Ethernet Demarcation vii

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. (ETX203AM has been tested and found to comply with the
limits of the Class A digital device (when equipped with E1/T1/T3 network module) or the Class B
digital device (when equipped with GbE or SHDSL network module); ETX203AX-DSL has been
tested and found to comply with the limits of the Class B digital device; ETX205A has been tested
and found to comply with the limits of the Class B digital device.) 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 numérique de la classe A respecte toutes les exigences du Règlement sur le matériel
brouilleur du Canada.
Warning per EN 55032 (CISPR-32)

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 résidentiel,

cet appareil peut provoquer des brouillages radioélectriques. Dans ces cas, il
peut être demandé à l’utilisateur de prendre les mesures appropriées.
Achtung Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In

Wohngebieten können beim Betrieb dieses Gerätes Rundfunkströrungen
auftreten, für deren Behebung der Benutzer verantwortlich ist.
viii ETX-2 Carrrier Ethernet Demarcation

Français
Mise au rebut du produit
Afin de faciliter la réutilisation, le recyclage ainsi que d'autres formes de
récupération d'équipement mis au rebut dans le cadre de la protection de
l'environnement, il est demandé au propriétaire de ce produit RAD de ne pas
mettre ce dernier au rebut en tant que déchet municipal non trié, une fois que le
produit est arrivé en fin de cycle de vie. Le client devrait proposer des solutions
de réutilisation, 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 générales de sécurité

Les instructions suivantes servent de guide général d'installation et d'opération sécurisées des
produits de télécommunications. Des instructions supplémentaires sont éventuellement indiquées
dans le manuel.
Symboles de sécurité
Ce symbole peut apparaitre sur l'équipement ou dans le texte. Il indique des
risques potentiels de sécurité pour l'opérateur ou le personnel de service,
quant à l'opération du produit ou à sa maintenance.
Avertissement
Danger de choc électrique ! Evitez tout contact avec la surface marquée tant
que le produit est sous tension ou connecté à des lignes externes de
télécommunications.
Surface chaude. Ne pas toucher.
Mise à la terre de protection : la cosse ou la borne marquée devrait être

connectée à la prise de terre de protection du bâtiment.
ETX-2 Carrrier Ethernet Demarcation ix

Certains produits peuvent être équipés d'une diode laser. Dans de tels cas,
une étiquette indiquant la classe laser ainsi que d'autres avertissements, le
cas échéant, sera jointe près du transmetteur optique. Le symbole
d'avertissement laser peut aussi être joint.
Avertissement
Veuillez observer les précautions suivantes :
• Avant la mise en marche de l'équipement, assurez-vous que le câble 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 câbles ou connecteurs de fibre optique cassés ou sans
terminaison et n'observez pas directement un rayon laser.
• L'usage de périphériques optiques avec l'équipement augmentera le
risque pour les yeux.
• L'usage de contrôles, ajustages ou procédures autres que celles spécifiées
ici pourrait résulter en une dangereuse exposition aux radiations.
ATTENTION : Le rayon laser peut être invisible !
Les utilisateurs pourront, dans certains cas, insérer leurs propres émetteurs-récepteurs Laser SFP
dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas être tenue responsable de
tout dommage pouvant résulter de l'utilisation d'émetteurs-récepteurs non conformes. Plus
particulièrement, les utilisateurs sont avertis de n'utiliser que des produits approuvés par l'agence
et conformes à la réglementation locale de sécurité laser pour les produits laser de classe 1.
Respectez toujours les précautions standards de sécurité durant l'installation, l'opération et la
maintenance de ce produit. Seul le personnel de service qualifié et autorisé devrait effectuer
l'ajustage, la maintenance ou les réparations de ce produit. Aucune opération d'installation,
d'ajustage, de maintenance ou de réparation ne devrait être effectuée par l'opérateur ou
l'utilisateur.
Manipuler des produits sous tension
Règles générales de sécurité

Ne pas toucher ou altérer l'alimentation en courant lorsque le câble d'alimentation est branché.
Des tensions de lignes peuvent être présentes dans certains produits, même lorsque le
commutateur (s'il est installé) est en position OFF ou si le fusible est rompu. Pour les produits
alimentés par CC, les niveaux de tension ne sont généralement pas dangereux mais des risques de
courant peuvent toujours exister.
Avant de travailler sur un équipement connecté aux lignes de tension ou de télécommunications,
retirez vos bijoux ou tout autre objet métallique pouvant venir en contact avec les pièces sous
tension.
Sauf s'il en est autrement indiqué, tous les produits sont destinés à être mis à la terre durant
l'usage normal. La mise à la terre est fournie par la connexion de la fiche principale à une prise
murale équipée d'une borne protectrice de mise à la terre. Si une cosse de mise à la terre est
fournie avec le produit, elle devrait être connectée à tout moment à une mise à la terre de
protection par un conducteur de diamètre 18 AWG ou plus. L'équipement monté en châssis ne
devrait être monté que sur des châssis et dans des armoires mises à la terre.
Branchez toujours la mise à la terre en premier et débranchez-la en dernier. Ne branchez pas des
câbles de télécommunications à un équipement qui n'est pas mis à la terre. Assurez-vous que tous
les autres câbles sont débranchés avant de déconnecter la mise à la terre.
x ETX-2 Carrrier Ethernet Demarcation

Connexion au courant du secteur

Assurez-vous que l'installation électrique est conforme à la réglementation locale.
Branchez toujours la fiche de secteur à une prise murale équipée 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
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de court-
circuit dépassant 35A (40A aux Etats-Unis et Canada).
Branchez toujours le câble 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 câble d'alimentation ne
peut pas être facilement débranché en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est installé dans l'installation du bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si le système de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par
rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.
A cause de la capacité de courant des systèmes à alimentation CC, des précautions 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 isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation 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
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de court-
circuit dépassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des câbles 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 câbles d'alimentation CC, connectez d'abord le conducteur
de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le pôle négatif.
Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
ETX-2 Carrrier Ethernet Demarcation xi

Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
ANSI American National Standards Institute.
APS (Automatic An automatic service restoration function by which a network

protection switching) senses a circuit or node failure and automatically switches traffic
over an alternate path.
Attenuation Signal power loss through equipment, lines or other transmission

devices. Measured in decibels.
Azimuth The horizontal direction from the GPS satellite, measured clockwise
with reference to north as the base direction. For example, a
coordinate due north has an azimuth of 0°, one due east has an
azimuth of 90°, one due south has an azimuth of 180°, etc.
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.
Byte A group of bits (normally 8 bits in length).
Carrier A continuous signal at a fixed frequency that is capable of being

modulated with a second (information carrying) signal.
Cell The 53-byte basic information unit within an ATM network. The user
traffic is segmented into cells at the source and reassembled at the
destination. An ATM cell consists of a 5-byte ATM header and a 48-
byte ATM payload, which contains the user data.
ETX-2 Carrrier Ethernet Demarcation xiii

Channel A path for electrical transmission between two or more points. Also
called a link, line, circuit or facility.
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).
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.
ERP Ethernet Ring Protection. A G.8032 Layer-2 Ethernet ring is a logical

ring that protects against link and node failures.
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).
EVC An Ethernet Virtual Connection is an association between two or

more user/network interfaces that identifies a point-to-point or
multipoint-to-multipoint path within the network
Flow Control A congestion control mechanism that results in an ATM system

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

transmission medium. The terms packet, datagram, segment, and
message are also used to describe logical information groupings.
Framing At the physical and data link layers of the OSI model, bits are fit
into units called frames. Frames contain source and destination
information, flags to designate the start and end of the frame, plus
information about the integrity of the frame. All other information,
xiv ETX-2 Carrrier Ethernet Demarcation

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.
GFP (Generic Framing Defined by ITU-T G.7041, generic framing procedure allows efficient
Procedure) mapping of variable length, higher-layer client signals, such as
Ethernet, over a transport network like SDH/SONET. Recently, GFP
has been extended to lower speed PDH networks.
Interface A shared boundary, defined by common physical interconnection

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

identifies a computer or device on a TCP/IP network. The format of
an IP address is a 32-bit numeric address written as four numbers
from 0 to 255, separated by periods (for example, 1.0.255.123).
Jitter The deviation of a transmission signal in time or phase. It can

introduce errors and loss of synchronization in high speed
synchronous communications.
Laser A device that transmits an extremely narrow and coherent beam of

electromagnetic energy in the visible light spectrum. Used as a light
source for fiber optic transmission (generally more expensive,
shorter lived, single mode only, for greater distances than LED).
Latency The time between initiating a request for data and the beginning of
the actual data transfer. Network latency is the delay introduced
when a packet is momentarily stored, analyzed and then forwarded.
Link The definition of a physical connection on the RV-SC/TDM map
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.
Logical MAC A concept used to describe and map the Ethernet traffic passing over
different media (E1/T1, SDH/SONET, etc). Logical MAC represents the
MAC layer of the entity. It should be bound to a GFP, HDLC or MLPPP
port, which, in its turn, should be bound to the physical layer.
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.
MA (Maintenance See MEG (Maintenance Entity Group).
ETX-2 Carrrier Ethernet Demarcation xv

Association)
ME (Maintenance An ME is a maintenance entity as defined by ITU-T Y.1731 that

Entity) requires management.
MEG (Maintenance MEs are grouped into ME groups. For a point-to-point Ethernet
Entity Group) connection/S-VLAN, a MEG contains a single ME. For a multipoint
Ethernet connection, a MEG contains n*(n-1)/2 MEs, where n is the
number of Ethernet connection end points. Each MEG is assigned a
unique ID that is used in OAM messages. (MEGs are also referred to
as Maintenance Associations or MAs in IEEE language.)
MEP (Maintenance MEPs are located at the ends of managed entities. MEPs generate
Entity Group End Point) and process OAM frames to monitor and maintain the ME.
MIP (Maintenance A MIP is located at an intermediate point along the end-to-end

Entity Group Ethernet path . It can respond to OAM messages, but cannot
Intermediate Point) originate them.
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.
Metering This feature is intended for support of payphones, and therefore

includes dedicated circuits for the detection of polarity and of 16
kHz or 12 kHz metering pulses.
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.
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.
xvi ETX-2 Carrrier Ethernet Demarcation

Path A service defined over network links is referred to as path in RV-

SC/TDM.
Payload The 48-byte segment of the ATM cell containing user data. Any
adaptation of user data via the AAL will take place within the
payload.
Physical Layer Layer 1 of the OSI model. The layer concerned with electrical,
mechanical, and handshaking procedures over the interface
connecting a device to the transmission medium.
Policing A method for verifying that the incoming VC complies with the
user’s 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.
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
few nodes to thousands of nodes.
SNR Signal to Noise Ratio is the ratio of signal strength to the level of
background noise, usually expressed in decibels (dB)
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.
ETX-2 Carrrier Ethernet Demarcation xvii

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.
Sync See Synchronous Transmission.
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.
TLV Type-length-value element used to encode optional information in a

data communication protocol such as LLDP or OAM CFM
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.
TWAMP Two-Way Active Measurement Protocol. Mechanism for measuring

metrics between network elements by sending test packets from
generators to responders.
Zero suppression Technique used to ensure a minimum density of marks.
xviii ETX-2 Carrrier Ethernet Demarcation

EU Declaration of Conformity
Manufacturer's Name: RAD Data Communications Ltd.
Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 6971920, Israel
declares under its sole responsibility that the product:
Product Name: ETX-203AM
Product Options: All options (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative

document(s) in accordance with the relevant European Union
harmonization legislation:
EMC EN 55032: 2012+ Electromagnetic Compatibility of multimedia equipment – Emissions

AC/2013 requirements.
EN 55024:2010 Information technology equipment; Immunity characteristics;

(in accordance with Limits and methods of measurement.
EN 61000-4-
2/3/4/5/6/11)
EN 61000-3-2:2014 Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic

current emissions (equipment input current ≤ 16A per phase)
EN 61000-3-3:2013 Electromagnetic compatibility (EMC); Section 3-3: Limits -

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

A11:2009, A1:2010 General requirements.
A12:2011, A2:2013
Supplementary Information: The product herewith complies with the requirements of the EMC
Directive 2014/30/EU, the Low Voltage Directive 2014/35/EU and the
ROHS Directive 2011/65/EU.
The product was tested in typical configurations.
Signed for and on behalf of
RAD Data Communications Ltd.
Tel Aviv, 26 February 2017
Zohar Zosmanovich
Compliance Team Leader
European Contact: RAD Data Communications GmbH

Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
ETX-2 Carrrier Ethernet Demarcation xix

Product Name: ETX-203AX



EN 61000-4-
2/3/4/5/6/11)



A12:2011, A2:2013
Zohar Zosmanovich

xx ETX-2 Carrrier Ethernet Demarcation

Product Name: ETX-205A



EN 61000-4-
2/3/4/5/6/11)



A12:2011, A2:2013
Zohar Zosmanovich

ETX-2 Carrrier Ethernet Demarcation xxi

Product Name: ETX-220A



EN 61000-4-
2/3/4/5/6/11)



A12:2011, A2:2013
Zohar Zosmanovich

xxii ETX-2 Carrrier Ethernet Demarcation

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

Perform the following steps to install the unit:
1. Determine the required configuration of ETX-2 according to your application.
2. Connect the ASCII terminal to the CONTROL port.
3. Connect power to the unit.
Connecting to Terminal
 To connect the unit to a terminal:
1. Connect the male 8-pin RJ-45 connector of the CBL-RJ45/D9/F/6FT terminal
cable to the unit’s 8-pin female connector, designated CONTROL.
2. Connect the other end of the CBL-RJ45/D9/F/6FT terminal cable to the ASCII
terminal equipment.
Connecting to Power
Regular units are available with AC, DC, or universal AC/DC power supply,
depending on the ordering option. AC/DC plugs or terminal block connectors are
available for DC power supplies.
Before connecting or disconnecting any 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 are using an extension cord (power cable) make sure it
Warning is grounded as well.
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.
Connecting to AC Power
For indoor installations, a standard K.21 power cable is supplied to provide AC
power to the unit.
For connection to unprotected AC power networks, devices that do not have
built-in AC surge protection are provided with an Enhanced AC power cable per
ITU-T K.21E enhanced mode.
ETX-2 Installing the Unit 1

Quick Start Guide Installation and Operation Manual
 To connect to AC power:
1. Connect the relevant AC power cable to the power connector on ETX-2.
2. Connect the power cable to the mains outlet.
The unit turns on automatically once connected to the mains.
Connecting to DC Power
For indoor installations, a standard K.21 power cable is supplied to provide AC
power to the unit.
All DC options support NEBS level 3 on port type 8b (DC inlet).
 To connect to DC power:
1. Connect the standard power cable to the power connector on ETX-2.
The unit turns on automatically once connected to the mains.
Refer to the relevant DC Power Supply Connection section at the end of Chapter
2 in this manual for instructions on wiring the DC connection.
2. Configuring the Unit for Management

Configure ETX-2 for management, using a local ASCII-based terminal.
Starting a Terminal Session for the First Time

 To start the terminal session:
1. Make sure all ETX-2 cables and connectors are properly connected.
2. Connect ETX-2 to a PC equipped with an ASCII terminal emulation application.
Refer to the Installation and Setup chapter for details on connecting to the
control port.
3. Start the PC terminal emulation program and create a new terminal
connection.
4. Configure the PC communication port parameters to a baud rate of 9.6 kbps,
8 bits/character, 1 stop bit, no parity and no flow control.
5. Power-up the unit.
The boot manager of ETX-2 starts, and displays a message that you can
stop the auto-boot and enter the boot manager by pressing any key. A
running countdown of the number of seconds remaining until auto-boot
is displayed. If it reaches 0 before you press a key, then after a few
seconds a message is displayed showing that the active software pack is
being loaded.
After a few more seconds, the login prompt is displayed.
2 Configuring the Unit for Management ETX-2

Installation and Operation Manual Quick Start Guide
6. Log in with your user name (default: su for full configuration and monitoring
access) and password (default: 1234).
The device prompt appears:
ETX-2#
7. Type the necessary CLI commands.
8. Continue with product configuration.
Configuring Management Flows

To manage the ETX-2 from a remote NMS, you must first preconfigure the basic
parameters using a supervision terminal connected to the ETX-2 CONTROL port.
You can manage ETX-2 by setting up management flows between the
out-of-band Ethernet management port and an SVI bound to a router interface.
 To configure ETX-2 for management access:

1. Add an SVI port.
2. Create classifier profiles for matching all traffic and matching untagged
traffic.
3. Add two flows (incoming and outgoing) connecting the out-of-band Ethernet
management port and the SVI.
4. Add a router interface, bind it to the SVI, and add a static route to the next
hop.
The following script provides the necessary configuration steps. Replace IP
addresses and entity names with values suitable for your network environment.
#*******************************Adding_SVI***********************************
config port
svi 1
no shutdown
exit all
#***************************Adding Classifier_Profiles***********************
config flows
classifier-profile all match-any match all
classifier-profile untagged match-any match untagged
#***************************Configuring_Flows********************************
flow mng_in
classifier untagged
no policer
ingress-port ethernet 101
egress-port svi 1
no shutdown
exit
ETX-2 Configuring the Unit for Management 3

Quick Start Guide Installation and Operation Manual
flow mng_out
classifier all
ingress-port svi 1
egress-port ethernet 101 queue 0 block 0/1
no shutdown
exit all
#*********************Configuring_Router_Interface***************************
configure router 1
interface 1
bind svi 1
address 172.18.141.39/24
no shutdown
exit
static-route 172.17.0.0/16 address 172.18.141.1
exit all
save
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:

• Enter the following commands:
exit all
file copy startup-config user-default-config
4. Verifying Connectivity
At the ASCII terminal, ping the IP address assigned to the management router
interface and verify that replies are received. If there is no reply to the ping,
check your configuration and make the necessary corrections.
5. Configuring Services
Proceed with service configuration (refer to the Services chapter for details of
different scenarios for provisioning supported services).
4 Configuring Services ETX-2

Contents
Chapter 1. Introduction
1.1 Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-2
ETX203AX .................................................................................................................... 1-2
ETX203AM ................................................................................................................... 1-3
ETX205A ...................................................................................................................... 1-5
ETX220A ...................................................................................................................... 1-6
Timing Options .................................................................................................................. 1-6
Applications ....................................................................................................................... 1-6
Ethernet Demarcation for Retail and Wholesale Services............................................... 1-6
Mobile Demarcation Device for Mobile Backhauling Applications ................................... 1-7
Features ............................................................................................................................ 1-8
Traffic Processing .......................................................................................................... 1-8
Resiliency and Optimization .......................................................................................... 1-9
Timing and Synchronization ........................................................................................ 1-10
Integrated x86 Processor and PMC .............................................................................. 1-10
Management and Security ........................................................................................... 1-11
Monitoring and Diagnostics ......................................................................................... 1-12
1.2 New in This Version ............................................................................................................ 1-14
1.3 Physical Description ........................................................................................................... 1-14
1.4 Functional Description ........................................................................................................ 1-15
1.5 Technical Specifications...................................................................................................... 1-17
Chapter 2. Installation and Setup

2.1 Safety .................................................................................................................................. 2-1
2.2 Site Requirements and Prerequisites .................................................................................... 2-2
Special Bonding and Grounding Considerations .................................................................. 2-3
2.3 Package Contents................................................................................................................. 2-4
2.4 Required Equipment ............................................................................................................. 2-5
2.5 Mounting the Unit ................................................................................................................ 2-5
2.6 Installing the GNSS Antenna ................................................................................................. 2-7
Positioning the GNSS Antenna ........................................................................................... 2-7
Mounting the Lightning Arrestor ........................................................................................ 2-7
2.7 Installing SFP/XFP Modules ................................................................................................... 2-9
2.8 Connecting to Power .......................................................................................................... 2-10
Connecting to AC Power .................................................................................................. 2-10
Connecting to DC Power .................................................................................................. 2-11
AC/DC Adapter (AD) Plug for DC Power Supply Connection.......................................... 2-12
Terminal Block Connector for DC Power Supply Connection ......................................... 2-13
2.9 Connecting to Ethernet Equipment..................................................................................... 2-16
2.10 Connecting to SHDSL Equipment ........................................................................................ 2-18
2.11 Connecting to VDSL Equipment .......................................................................................... 2-19
2.12 Connecting to E1/T1 Equipment ......................................................................................... 2-20
2.13 Connecting to T3 Equipment .............................................................................................. 2-21
2.14 Connecting to Station Clock ............................................................................................... 2-21
Connecting to a Balanced Clock Source ....................................................................... 2-22
Connecting to an Unbalanced Clock Source ................................................................. 2-22
2.15 Connecting to Synchronization Equipment ......................................................................... 2-23
2.16 Connecting to a Terminal ................................................................................................... 2-24
ETX-2 i
Table of Contents Installation and Operation Manual
2.17 Connecting to a Network Management Station .................................................................. 2-25

2.18 Basic Connectivity Tests ..................................................................................................... 2-26
Chapter 3. Operation and Maintenance

3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-1
LED Behavior...................................................................................................................... 3-1
ETX203AM ................................................................................................................... 3-2
ETX203AX .................................................................................................................... 3-3
ETX205A ...................................................................................................................... 3-4
ETX220A ...................................................................................................................... 3-5
LED Signaling ..................................................................................................................... 3-6
Configuring LED Signaling .............................................................................................. 3-6
Viewing LED Blinking Status........................................................................................... 3-7
3.3 Startup ................................................................................................................................. 3-8
Applicable Products............................................................................................................ 3-8
Configuration and Software Files ....................................................................................... 3-8
Loading Sequence .............................................................................................................. 3-9
3.4 Working with Custom Configuration Files ............................................................................. 3-9
Applicable Products.......................................................................................................... 3-10
Saving Configuration Changes .......................................................................................... 3-10
Confirming Startup Configuration..................................................................................... 3-11
On-Net Zero Touch .......................................................................................................... 3-11
Benefits ...................................................................................................................... 3-11
Functional Description................................................................................................. 3-12
Configuring On-Net Zero Touch Provisioning Via DHCP ................................................ 3-14
Verifying Zero Touch Success ...................................................................................... 3-19
Configuring Zero Touch via Trap .................................................................................. 3-20
3.5 Configuration and Management ......................................................................................... 3-20
3.6 Management Access Methods ............................................................................................ 3-21
Functional Description ..................................................................................................... 3-21
Inband and Out-of-Band (OOB) Management Access .................................................. 3-21
Limiting SSH Encryption Algorithms ............................................................................. 3-23
Factory Defaults .............................................................................................................. 3-23
3.7 CLI-Based Configuration ..................................................................................................... 3-24
Working with Terminal ..................................................................................................... 3-24
Accessing a Remote Terminal ...................................................................................... 3-26
Working with Telnet and SSH ........................................................................................... 3-27
Adding a Telnet Client Session .................................................................................... 3-28
Login ............................................................................................................................... 3-29
Logging In ................................................................................................................... 3-30
Changing Password ..................................................................................................... 3-31
Lost Superuser Password ............................................................................................ 3-31
Using the CLI .................................................................................................................... 3-31
CLI Prompt .................................................................................................................. 3-31
CLI Inactivity Timeout .................................................................................................. 3-32
Navigating ................................................................................................................... 3-32
Command Tree ............................................................................................................ 3-33
Command Structure .................................................................................................... 3-34
Special Keys ................................................................................................................ 3-34
Getting Help ................................................................................................................ 3-35
Scheduling CLI Commands ........................................................................................... 3-41
ii ETX-2
Installation and Operation Manual Table of Contents
Viewing the Device Configuration ................................................................................ 3-45

Refreshing Output ...................................................................................................... 3-45
Filtering Output ........................................................................................................... 3-46
Enabling Entities.......................................................................................................... 3-48
Using Scripts .................................................................................................................... 3-48
Examples ......................................................................................................................... 3-49
3.8 SNMP-Based Network Management ................................................................................... 3-49
Preconfiguring ETX2 for SNMP Management ................................................................... 3-49
Configuring Management Access...................................................................................... 3-51
Working with RADview ..................................................................................................... 3-52
Overview ..................................................................................................................... 3-52
Preconfiguration for Service Discovery ........................................................................ 3-52
Working with Shelf View .................................................................................................. 3-53
Working with Other SNMP-Based NMS ............................................................................. 3-53
3.9 Maintenance ...................................................................................................................... 3-54
3.10 Turning Off the Unit ........................................................................................................... 3-54
Chapter 4. Service Provisioning

4.1 Service Entities ..................................................................................................................... 4-1
Profiles .............................................................................................................................. 4-1
Scheduling and Shaping Entities......................................................................................... 4-2
Physical Ports .................................................................................................................... 4-3
Logical Ports ...................................................................................................................... 4-3
Forwarding Entities ............................................................................................................ 4-3
Flows ............................................................................................................................ 4-3
Bridge ........................................................................................................................... 4-4
Router........................................................................................................................... 4-4
4.2 E-LAN Service ....................................................................................................................... 4-4
Ethernet to Bridge ............................................................................................................. 4-4
Bridge to Ethernet ............................................................................................................. 4-5
4.3 E-Line Service ....................................................................................................................... 4-7
User to Network ................................................................................................................ 4-7
Network to User ................................................................................................................ 4-8
4.4 Smart SFP Service ............................................................................................................... 4-10
Network to User .............................................................................................................. 4-10
User to Network .............................................................................................................. 4-13
4.5 Service Summary ................................................................................................................ 4-16
Benefits ........................................................................................................................... 4-16
Viewing Service Summary ................................................................................................. 4-16
Examples ......................................................................................................................... 4-17
Chapter 5. Cards and Ports

5.1 Cards.................................................................................................................................... 5-1
Benefits ............................................................................................................................. 5-2
Functional Description ....................................................................................................... 5-2
Factory Defaults ................................................................................................................ 5-2
Configuring Module ............................................................................................................ 5-2
5.2 DS1 (E1/T1) Ports ................................................................................................................ 5-3
Benefits ............................................................................................................................. 5-3
ETX-2 iii

Configuring E1/T1 Ports ..................................................................................................... 5-4
5.3 E1 Ports ............................................................................................................................... 5-4
Standards .......................................................................................................................... 5-5
Benefits ............................................................................................................................. 5-5
Configuring E1 Ports .......................................................................................................... 5-6
Configuring Built-in E1 Ports ......................................................................................... 5-6
Configuring Modular E1 Ports ...................................................................................... 5-10
Configuring Smart SFP E1 Ports ................................................................................... 5-12
5.4 E3 Ports ............................................................................................................................. 5-15
Standards ........................................................................................................................ 5-15
Benefits ........................................................................................................................... 5-16
Configuring E3 Ports ........................................................................................................ 5-16
5.5 Ethernet Ports .................................................................................................................... 5-18
Options ....................................................................................................................... 5-18
Numbering .................................................................................................................. 5-19
MAC Addresses ........................................................................................................... 5-20
Ethertype .................................................................................................................... 5-20
Layer-2 Control Protocol (L2CP) Processing ................................................................. 5-21
Silent Start .................................................................................................................. 5-21
Configuring Ethernet Port Parameters .............................................................................. 5-24
Setting Functional Mode to Network or User Port ............................................................ 5-29
Viewing Ethernet Port Status ........................................................................................... 5-31
Testing Ethernet Ports ..................................................................................................... 5-36
Example ...................................................................................................................... 5-37
Viewing Ethernet Port Statistics ....................................................................................... 5-37
Setting Sampling Interval for Port Statistics ................................................................ 5-37
Displaying Port Statistics ............................................................................................. 5-37
Example ...................................................................................................................... 5-37
Displaying Layer-2 Control Processing Statistics .......................................................... 5-40
Example ...................................................................................................................... 5-40
Clearing Statistics ........................................................................................................ 5-41
Viewing Ethernet Port Data Rate and Line Rate ............................................................... 5-41
Example ...................................................................................................................... 5-41
5.6 Ethertype ........................................................................................................................... 5-42
Standards ........................................................................................................................ 5-42
Benefits ........................................................................................................................... 5-42
Configuring Ethertype ...................................................................................................... 5-43
Example ........................................................................................................................... 5-43
Configuration Errors ......................................................................................................... 5-43
5.7 GFP Ports ........................................................................................................................... 5-44
iv ETX-2
Standards ........................................................................................................................ 5-44

Benefits ........................................................................................................................... 5-44
Configuring GFP Ports ...................................................................................................... 5-45
Examples ......................................................................................................................... 5-46
5.8 HDLC Ports ......................................................................................................................... 5-47
Configuring HDLC Ports .................................................................................................... 5-47
5.9 Internal Ports for x86 Interconnection................................................................................ 5-47
Benefits ........................................................................................................................... 5-48
Configuring the Internal Port Parameters ......................................................................... 5-49
5.10 Logical MAC Ports ............................................................................................................... 5-49
Benefits ........................................................................................................................... 5-49
Configuring Logical MAC Ports .......................................................................................... 5-50
Examples ......................................................................................................................... 5-53
5.11 PCS Ports ........................................................................................................................... 5-53
Standards ........................................................................................................................ 5-53
Benefits ........................................................................................................................... 5-54
Configuring PCS Port Parameters ..................................................................................... 5-54
Viewing PCS Port Statistics ............................................................................................... 5-56
5.12 Peers .................................................................................................................................. 5-58
Configuring Peers............................................................................................................. 5-59
5.13 SDH/SONET Ports ............................................................................................................... 5-59
Standards ........................................................................................................................ 5-59
Benefits ........................................................................................................................... 5-59
Configuring SDH/SONET Ports .......................................................................................... 5-60
5.14 SFPs ................................................................................................................................... 5-61
5.15 Smart SFPs ......................................................................................................................... 5-62
Benefits ........................................................................................................................... 5-62
Configuring Smart SFPs .................................................................................................... 5-63
Examples ......................................................................................................................... 5-64
5.16 SHDSL Ports ....................................................................................................................... 5-65
Standards ........................................................................................................................ 5-66
Benefits ........................................................................................................................... 5-66
ETX-2 v

Configuring SHDSL Port Parameters ................................................................................. 5-66
Viewing SHDSL Port Status............................................................................................... 5-67
Viewing SHDSL Port Statistics .......................................................................................... 5-68
5.17 Service Virtual Interfaces (SVIs) .......................................................................................... 5-69
Benefits ........................................................................................................................... 5-69
Configuring Service Virtual Interfaces ............................................................................... 5-71
Examples ......................................................................................................................... 5-71
5.18 T1 Ports ............................................................................................................................. 5-72
Standards ........................................................................................................................ 5-73
Benefits ........................................................................................................................... 5-73
Configuring T1 Ports ........................................................................................................ 5-74
Configuring Built-in T1 Ports ....................................................................................... 5-74
Configuring Modular T1 Ports ...................................................................................... 5-78
Configuring Smart SFP T1 Ports ................................................................................... 5-80
5.19 T3 Ports ............................................................................................................................. 5-82
Standards ........................................................................................................................ 5-83
Benefits ........................................................................................................................... 5-83
Configuring T3 Ports ........................................................................................................ 5-83
Configuring Modular T3 Ports ...................................................................................... 5-83
Configuring Smart SFP T3 Ports ................................................................................... 5-85
5.20 VCGs .................................................................................................................................. 5-87
Standards ........................................................................................................................ 5-87
Benefits ........................................................................................................................... 5-87
Configuring VCG Ports ...................................................................................................... 5-88
Examples ......................................................................................................................... 5-89
5.21 VDSL2 Ports ....................................................................................................................... 5-90
Standards ........................................................................................................................ 5-90
Benefits ........................................................................................................................... 5-90
Configuring the VDSL2 Port Parameters ........................................................................... 5-91
Viewing VDSL2 Port Status ............................................................................................... 5-92
Viewing VDSL2 Port Statistics........................................................................................... 5-92
Example ...................................................................................................................... 5-92
Chapter 6. Management and Security

6.1 Access Control List (ACL) ...................................................................................................... 6-1
Standards .......................................................................................................................... 6-1
vi ETX-2
Benefits ............................................................................................................................. 6-1

Binding Access Control Lists .......................................................................................... 6-2
Filtering and Marking ..................................................................................................... 6-2
Show Me Demo ............................................................................................................. 6-2
Statistics ....................................................................................................................... 6-3
Configuring ACL ................................................................................................................. 6-3
Access-Control-Level Tasks ........................................................................................... 6-4
Management-Level Tasks .............................................................................................. 6-5
Examples ....................................................................................................................... 6-6
Configuration Errors ...................................................................................................... 6-7
Displaying Status........................................................................................................... 6-7
Displaying Statistics ...................................................................................................... 6-8
6.2 Access Policy ........................................................................................................................ 6-8
Configuring Access Policy ................................................................................................... 6-8
6.3 Management Source IP Address ........................................................................................... 6-9
6.4 Management DSCP Value .................................................................................................... 6-10
6.5 Authentication via RADIUS Server ....................................................................................... 6-10
Standards ........................................................................................................................ 6-10
Benefits ........................................................................................................................... 6-11
Configuring RADIUS Parameters ....................................................................................... 6-12
Viewing RADIUS Statistics ................................................................................................ 6-13
6.6 Authentication via TACACS+ Server..................................................................................... 6-14
Standards ........................................................................................................................ 6-14
Benefits ........................................................................................................................... 6-14
Components................................................................................................................ 6-15
Accounting .................................................................................................................. 6-16
Mapping Privilege Levels .............................................................................................. 6-16
Configuring TACACS+ Server ............................................................................................. 6-17
Configuring Accounting Groups ........................................................................................ 6-18
Mapping CLI Levels to TACACS+ Privilege Levels................................................................ 6-18
Example – Defining Server ............................................................................................... 6-19
Example – Defining Accounting Group .............................................................................. 6-19
Example – Mapping CLI Level to Privilege Level ................................................................. 6-20
Viewing TACACS+ Statistics .............................................................................................. 6-20
6.7 Control Port ....................................................................................................................... 6-21
Configuring Control Port Parameters ................................................................................ 6-22
6.8 DHCP Relay ........................................................................................................................ 6-22
Standards ........................................................................................................................ 6-23
Benefits ........................................................................................................................... 6-23
ETX-2 vii
DHCP Messages ........................................................................................................... 6-23

DHCP Snooping ........................................................................................................... 6-24
DHCP Option 82 .......................................................................................................... 6-24
Configuring DHCP Relay ................................................................................................... 6-25
System Parameters ..................................................................................................... 6-26
6.9 Point-to-Point Protocol over Ethernet (PPPoE) ................................................................... 6-27
Standards ........................................................................................................................ 6-28
Benefits ........................................................................................................................... 6-28
Discovery .................................................................................................................... 6-28
PPP Session ................................................................................................................. 6-28
Configuring PPPoE and PPP Entities ............................................................................. 6-30
Configuring PPP Port ........................................................................................................ 6-30
Example ........................................................................................................................... 6-32
Viewing PPP and PPPoE Status ......................................................................................... 6-33
6.10 SNMP Management ............................................................................................................ 6-34
Standards ........................................................................................................................ 6-34
Benefits ........................................................................................................................... 6-35
Configuring SNMPv3 Parameters ...................................................................................... 6-35
Examples ......................................................................................................................... 6-43
6.11 User Access ........................................................................................................................ 6-47
Password Hashing ....................................................................................................... 6-48
SSH Authentication ..................................................................................................... 6-48
Configuring Users ............................................................................................................ 6-49
Deleting a User ................................................................................................................ 6-50
Viewing Users .................................................................................................................. 6-50
Viewing User Information ................................................................................................. 6-50
Viewing SSH Server Information ....................................................................................... 6-51
Viewing Failed Login Attempts ......................................................................................... 6-51
Example ........................................................................................................................... 6-52
Defining Users ............................................................................................................ 6-52
Chapter 7. Resiliency and Optimization

7.1 Ethernet Linear Protection ................................................................................................... 7-1
Standards .......................................................................................................................... 7-1
Benefits ............................................................................................................................. 7-2
ETP Flow Attributes ....................................................................................................... 7-2
EVC Protection Switching............................................................................................... 7-3
Master and Slave ETPs ................................................................................................... 7-3
Management over ETP ................................................................................................... 7-3
EVC and OAM ................................................................................................................ 7-3
EVC Fault Propagation ................................................................................................... 7-4
viii ETX-2
EVC Loopback ................................................................................................................ 7-4

Configuring ETPs ................................................................................................................ 7-4
Configuring ETP Protection................................................................................................. 7-5
Examples ........................................................................................................................... 7-7
7.2 Ethernet Ring Protection (ERP) ............................................................................................. 7-8
Standards .......................................................................................................................... 7-8
Benefits ............................................................................................................................. 7-8
Ring Topology ............................................................................................................... 7-9
Ring Protection Links .................................................................................................. 7-11
R-APS Control Messages ............................................................................................. 7-11
Multiple Ring Instances on a Single Port ...................................................................... 7-11
Passthrough VLANs ..................................................................................................... 7-12
Protection Switching Functionality .............................................................................. 7-12
ERP Timers .................................................................................................................. 7-13
Ring Commands .......................................................................................................... 7-13
Color Mapping ............................................................................................................. 7-13
CoS Mapping ............................................................................................................... 7-13
Configuring Ethernet Ring Protection ............................................................................... 7-15
Examples ......................................................................................................................... 7-18
Viewing ERP Status .......................................................................................................... 7-20
Viewing ERP Statistics ...................................................................................................... 7-22
7.3 Fault Propagation ............................................................................................................... 7-23
Standards ........................................................................................................................ 7-23
Benefits ........................................................................................................................... 7-23
Configuring Fault Propagation .......................................................................................... 7-25
Adding Fault Propagation Entry ................................................................................... 7-25
Configuring Fault Propagation Rules ............................................................................ 7-27
Disabling Fault Propagation ......................................................................................... 7-29
Examples ......................................................................................................................... 7-29
7.4 Link Aggregation ................................................................................................................ 7-32
Standards ........................................................................................................................ 7-33
Benefits ........................................................................................................................... 7-33
Protection ................................................................................................................... 7-33
Load Balancing ............................................................................................................ 7-34
Configuring LAG ............................................................................................................... 7-35
Examples ......................................................................................................................... 7-38
Protection LAG ............................................................................................................ 7-38
Load Balancing LAG ..................................................................................................... 7-39
Viewing LAG Status .......................................................................................................... 7-46
Examples ......................................................................................................................... 7-47
7.5 Link Protection ................................................................................................................... 7-48
Standards ........................................................................................................................ 7-48
ETX-2 ix
Benefits ........................................................................................................................... 7-48

Configuring Link Protection .............................................................................................. 7-49
Example ........................................................................................................................... 7-51
Chapter 8. Traffic Processing

8.1 Bridge .................................................................................................................................. 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-1
Admission to Bridge ...................................................................................................... 8-3
Packet Editing on Reverse Flows ................................................................................... 8-3
Management via Bridge ................................................................................................. 8-4
Spanning Tree Protocol ................................................................................................. 8-4
Configuring the Bridge ....................................................................................................... 8-8
Configuring Bridge Ports ............................................................................................. 8-10
Configuring VLAN ........................................................................................................ 8-11
Configuring RSTP/MSTP ............................................................................................... 8-11
Examples ......................................................................................................................... 8-17
VLAN-Aware Bridge ..................................................................................................... 8-17
Displaying VLAN Information ....................................................................................... 8-20
VLAN-Unaware Bridge ................................................................................................. 8-20
Creating Static MAC Address ....................................................................................... 8-22
Viewing the MAC Address Table................................................................................... 8-22
8.2 Classification by Flow ......................................................................................................... 8-23
Standards ........................................................................................................................ 8-23
Benefits ........................................................................................................................... 8-23
Flow Classification ....................................................................................................... 8-24
Configuring a Classifier Profile ......................................................................................... 8-36
Configuring Flows ............................................................................................................ 8-36
Configuring Port Classification ......................................................................................... 8-42
Examples ......................................................................................................................... 8-44
Classifier Profiles ......................................................................................................... 8-44
Traffic Flows ............................................................................................................... 8-45
ETP Flows .................................................................................................................... 8-46
Unidirectional Hub....................................................................................................... 8-46
Multi-CoS Flow ............................................................................................................ 8-48
Testing Flows and Flow Diagnostics Loopback ................................................................. 8-49
Use Case 1 – Application Layer Loopback .................................................................... 8-49
Example ...................................................................................................................... 8-50
Method 2 – Flow Diagnostics Loopback ...................................................................... 8-50
Example – Flow Diagnostics Loop ................................................................................ 8-51
Viewing Flow Statistics ..................................................................................................... 8-51
Examples ..................................................................................................................... 8-52
Viewing Flow Status ......................................................................................................... 8-56
Example ...................................................................................................................... 8-56
Viewing Flow Data Rate and Line Rate ............................................................................. 8-56
x ETX-2
Example ........................................................................................................................... 8-56

8.3 Layer-2 Control Protocol (L2CP) Processing ........................................................................ 8-57
Standards ........................................................................................................................ 8-57
Benefits ........................................................................................................................... 8-57
Layer-2 Protocol Tunneling (L2PT) Over Bridge ........................................................... 8-58
Adding Layer 2 Control Processing Profiles ...................................................................... 8-59
Deleting Layer 2 Control Processing Profiles .................................................................... 8-60
Configuring Layer 2 Control Processing Profile Parameters .............................................. 8-60
Examples ......................................................................................................................... 8-63
Viewing L2CP Statistics .................................................................................................... 8-65
8.4 Link Layer Discovery Protocol (LLDP) .................................................................................. 8-66
Standards ........................................................................................................................ 8-66
Benefits ........................................................................................................................... 8-66
LLDP Bridge Types ....................................................................................................... 8-67
LLDP Packets ............................................................................................................... 8-67
Configuring LLDP.............................................................................................................. 8-69
System Parameters ..................................................................................................... 8-69
Port Parameters .......................................................................................................... 8-70
Example ........................................................................................................................... 8-71
Viewing LLDP Neighbor Information ................................................................................. 8-72
8.5 MLDv2 Snooping ................................................................................................................ 8-73
Standards ........................................................................................................................ 8-73
Benefits ........................................................................................................................... 8-74
MAC-based Forwarding Addresses............................................................................... 8-75
Port Aging ................................................................................................................... 8-76
Source-Specific Multicast ............................................................................................ 8-77
MLD Snooping and Ethernet Ring Protection ............................................................... 8-77
Configuring MLD Snooping ............................................................................................... 8-77
Displaying MLD Snooping Status ...................................................................................... 8-78
8.6 Pseudowire Connections .................................................................................................... 8-79
Standards ........................................................................................................................ 8-80
Pseudowire Packet Structure ....................................................................................... 8-80
TDM Service Encapsulation .......................................................................................... 8-81
Encapsulation over Different PSN Types ...................................................................... 8-85
Jitter Buffer ................................................................................................................. 8-85
Configuring Pseudowire Bundles ...................................................................................... 8-86
Adding Pseudowire Bundles ........................................................................................ 8-87
Configuring Pseudowire Bundle Parameters ................................................................ 8-88
Deleting Pseudowire Bundles ...................................................................................... 8-91
Viewing Pseudowire Configuration ................................................................................... 8-91
Viewing PW Statistics ....................................................................................................... 8-92
ETX-2 xi
Viewing PW Connectivity Statistics ................................................................................... 8-93

Examples ......................................................................................................................... 8-94
8.7 PW Cross Connects............................................................................................................. 8-96
Configuring PW Cross Connects........................................................................................ 8-97
Examples ......................................................................................................................... 8-97
8.8 Router ................................................................................................................................ 8-98
Standards ........................................................................................................................ 8-98
Benefits ........................................................................................................................... 8-98
Overview ..................................................................................................................... 8-99
Router Interface Forwarding ..................................................................................... 8-100
DHCPv6 Option Request ............................................................................................ 8-100
Factory Defaults ............................................................................................................ 8-100
Configuring the Router .................................................................................................. 8-102
Configuring Router Interfaces ................................................................................... 8-104
Deleting a Router ...................................................................................................... 8-108
Deleting a Router Interface ....................................................................................... 8-108
Viewing Router Interface Information ............................................................................ 8-108
Viewing IPv6 Neighbors .................................................................................................. 8-109
Viewing Routing Information .......................................................................................... 8-110
Viewing RIB .................................................................................................................... 8-111
Viewing Router Interface Status..................................................................................... 8-112
Configuration Errors ....................................................................................................... 8-114
8.9 Quality of Service (QoS) ................................................................................................... 8-116
Applicable Products........................................................................................................ 8-117
Standards ...................................................................................................................... 8-117
Benefits ......................................................................................................................... 8-117
Functional Description ................................................................................................... 8-117
Traffic Management .................................................................................................. 8-117
Scheduling ................................................................................................................ 8-118
Queue Mapping Profiles ................................................................................................. 8-118
Factory Defaults ........................................................................................................ 8-119
Adding Queue Mapping Profiles................................................................................. 8-120
Configuring Queue Mappings .................................................................................... 8-120
Examples ................................................................................................................... 8-121
CoS Mapping Profiles ..................................................................................................... 8-122
Configuring CoS Mapping Profiles .............................................................................. 8-124
Examples ................................................................................................................... 8-124
Color Mapping Profiles ................................................................................................... 8-125
Configuring Color Mapping Profiles ............................................................................ 8-125
Example .................................................................................................................... 8-125
Marking Profiles ............................................................................................................. 8-126
Configuring Marking Profiles ...................................................................................... 8-126
Bandwidth Profiles ......................................................................................................... 8-127
Envelope Bandwidth Profiles ..................................................................................... 8-129
xii ETX-2
Configuring Granularity Rounding .............................................................................. 8-130

Configuring Shaper Profiles ....................................................................................... 8-131
Configuring Policer Profiles........................................................................................ 8-133
Configuring Policer Aggregates .................................................................................. 8-137
Configuring Envelope Profiles .................................................................................... 8-138
Queue Block Profiles ...................................................................................................... 8-140
Adding Queue Block Profiles...................................................................................... 8-141
Configuring Queue Block Profile Parameters.............................................................. 8-141
Examples ................................................................................................................... 8-143
Queue Group Profiles ..................................................................................................... 8-143
Adding Queue Group Profiles .................................................................................... 8-144
Configuring Queue Group Parameters ....................................................................... 8-144
Assigning High-Scale Queue Group to Ports .............................................................. 8-145
Examples ................................................................................................................... 8-145
WRED Profiles ................................................................................................................ 8-146
Applicable Products ................................................................................................... 8-146
Functional Description............................................................................................... 8-146
Configuring WRED Profiles ......................................................................................... 8-147
Example .................................................................................................................... 8-148
Chapter 9. Timing and Synchronization

9.1 1588v2 Timing ..................................................................................................................... 9-1
Standards .......................................................................................................................... 9-1
Benefits ............................................................................................................................. 9-2
PTP Protocols ................................................................................................................ 9-2
1588v2 Entities ............................................................................................................. 9-2
PTP Port ........................................................................................................................ 9-2
Best Master Clock Algorithm (BMCA) ............................................................................. 9-3
Slave Clock .................................................................................................................... 9-3
Boundary Clock ............................................................................................................. 9-4
Master Clock (Standalone) ............................................................................................ 9-4
Forwarding .................................................................................................................... 9-4
Configuring PTP Ports ........................................................................................................ 9-5
Configuring the Slave Clock ................................................................................................ 9-6
Configuring the Master Clock ............................................................................................. 9-9
Viewing Clock Recovery Metrics........................................................................................ 9-10
Examples ......................................................................................................................... 9-12
Configuring Slave Clock ............................................................................................... 9-12
Configuring Boundary Clock ......................................................................................... 9-17
Configuring Master Clock ............................................................................................. 9-25
Viewing Current Metrics .............................................................................................. 9-30
Viewing Metrics for Selected Interval ........................................................................... 9-31
9.2 Clock Selection ................................................................................................................... 9-32
Standards ........................................................................................................................ 9-32
Benefits ........................................................................................................................... 9-32
ETX-2 xiii
Clock Domain ................................................................................................................... 9-33

Factory Defaults .......................................................................................................... 9-34
Configuring the Clock Domain ..................................................................................... 9-34
Clock Sources ................................................................................................................... 9-36
Configuring the Clock Sources ..................................................................................... 9-36
Viewing Clock Source Statistics.................................................................................... 9-38
Configuring the Station Clock ........................................................................................... 9-38
Examples ......................................................................................................................... 9-39
9.3 Date and Time.................................................................................................................... 9-40
Standards and MIBs ......................................................................................................... 9-41
Benefits ........................................................................................................................... 9-41
Setting the Date and Time ............................................................................................... 9-42
Viewing the Date and Time .............................................................................................. 9-43
Working with SNTP........................................................................................................... 9-43
Configuring SNTP Parameters ...................................................................................... 9-43
Defining SNTP Servers ................................................................................................. 9-44
Working with NTP ............................................................................................................ 9-44
Configuring NTP Parameters ........................................................................................ 9-44
Defining NTP Servers ................................................................................................... 9-45
Examples ......................................................................................................................... 9-45
Setting Date and Time ................................................................................................ 9-45
Defining SNTP Server .................................................................................................. 9-46
Viewing SNTP Server Information ................................................................................ 9-46
Defining NTP Server .................................................................................................... 9-46
9.4 Daylight Saving Time .......................................................................................................... 9-47
Configuring Daylight Saving Time Scheduling.................................................................... 9-48
Viewing Scheduling Information ....................................................................................... 9-48
Examples ......................................................................................................................... 9-48
9.5 GNSS Receiver .................................................................................................................... 9-49
Benefits ........................................................................................................................... 9-50
Configuring GNSS ............................................................................................................. 9-50
Example ........................................................................................................................... 9-51
Viewing GNSS Status ........................................................................................................ 9-51
Chapter 10. Administration

10.1 CPU and Memory Utilization ............................................................................................... 10-1
Viewing CPU Utilization .................................................................................................... 10-1
Viewing Memory Pool Utilization ...................................................................................... 10-2
10.2 Device Information ............................................................................................................. 10-2
Standards ........................................................................................................................ 10-3
xiv ETX-2
Configuring Device Information ........................................................................................ 10-3

Examples ......................................................................................................................... 10-5
10.3 Environment ....................................................................................................................... 10-5
Device Temperature .................................................................................................... 10-6
Device Fan .................................................................................................................. 10-6
Overheat Auto Shutdown ............................................................................................ 10-6
Configuring the Chassis.................................................................................................... 10-7
Examples ......................................................................................................................... 10-7
10.4 File Operations ................................................................................................................... 10-9
Device Files ................................................................................................................. 10-9
User Directory ............................................................................................................. 10-9
Commands for Copying Files ..................................................................................... 10-10
Using SFTP or TFTP .................................................................................................... 10-10
Adding a File Description ............................................................................................... 10-12
Copying Files .................................................................................................................. 10-12
Examples ................................................................................................................... 10-13
Viewing Copy Status ...................................................................................................... 10-14
Viewing Information on Files .......................................................................................... 10-15
Viewing Device Files .................................................................................................. 10-15
Example .................................................................................................................... 10-16
Viewing User Directory Files ...................................................................................... 10-16
Example .................................................................................................................... 10-17
Viewing Device Configuration Files ............................................................................ 10-17
Viewing File Details ................................................................................................... 10-17
Viewing File Contents ................................................................................................ 10-18
Deleting Files ................................................................................................................. 10-19
Example .................................................................................................................... 10-20
10.5 Inventory.......................................................................................................................... 10-20
Standards ...................................................................................................................... 10-20
Benefits ......................................................................................................................... 10-20
Viewing Inventory Information ....................................................................................... 10-20
Setting Administrative Inventory Information ................................................................. 10-22
Examples ....................................................................................................................... 10-23
10.6 Licensing .......................................................................................................................... 10-29
Benefits ......................................................................................................................... 10-29
Fault Propagation Event Manager License ................................................................. 10-30
Configuring Licenses ...................................................................................................... 10-30
Viewing License Status Summary ................................................................................... 10-31
Example ......................................................................................................................... 10-31
10.7 Login Banner .................................................................................................................... 10-32
Defining Login Banners .................................................................................................. 10-32
Defining Login Banners via CLI Commands ................................................................ 10-32
Defining Pre-Login Banner Using a Banner File .......................................................... 10-34
10.8 Sending a Message to Connected Users ........................................................................... 10-34
ETX-2 xv

Benefits ......................................................................................................................... 10-35
Example ......................................................................................................................... 10-35
10.9 Reset ............................................................................................................................... 10-36
Resetting to Factory Defaults ........................................................................................ 10-36
Resetting to User Defaults ............................................................................................. 10-37
Restarting the Unit ........................................................................................................ 10-38
Resetting the x86 Card .................................................................................................. 10-38
10.10 Tech-Support Commands .......................................................................................... 10-39
Benefits ......................................................................................................................... 10-39
Showing the Tech-Support Commands........................................................................... 10-40
Chapter 11. Monitoring and Diagnostics

11.1 In-Service ICMP Echo Ping Test ........................................................................................... 11-1
Benefits ........................................................................................................................... 11-2
PtP E-line Service ........................................................................................................ 11-2
MP to MP E-LAN (bridge) Services ............................................................................... 11-3
MP to MP (or P to MP) E-Tree Services ........................................................................ 11-3
Configuring the In-Service ICMP Echo Ping Test ................................................................ 11-4
Configuring In-Service ICMP Echo Ping Response ......................................................... 11-4
Configuring In-Service ICMP Echo Ping Request ........................................................... 11-5
In-Service ICMP Echo Ping Test Results ........................................................................ 11-6
Examples ......................................................................................................................... 11-7
11.2 OAM CFM (Connectivity Fault Management) ....................................................................... 11-9
Standards ........................................................................................................................ 11-9
Benefits ......................................................................................................................... 11-10
OAM Elements........................................................................................................... 11-10
OAM Functions .......................................................................................................... 11-11
OAM Connectivity ...................................................................................................... 11-11
Maintenance End Points (MEPs) ................................................................................ 11-12
Maintenance Intermediate Points (MIPs) ................................................................... 11-14
Messaging System ..................................................................................................... 11-17
OAM Performance Monitoring ................................................................................... 11-20
OAM Packet Handling ................................................................................................ 11-21
MEF46 Latching Loopback ......................................................................................... 11-23
Configuring OAM CFM .................................................................................................... 11-25
Configuring General Parameters ................................................................................ 11-26
Configuring Maintenance Domains ............................................................................ 11-28
Configuring Maintenance Associations ...................................................................... 11-30
Configuring Maintenance Endpoints .......................................................................... 11-32
Viewing MEF46 Latching Loopback Status ................................................................. 11-36
Configuring Maintenance Intermediate Points ........................................................... 11-37
xvi ETX-2
Configuring Maintenance Endpoint Services .............................................................. 11-38

Configuring Destination NEs ...................................................................................... 11-40
Configuring OAM CFM Service Event Reporting .......................................................... 11-43
Viewing OAM CFM Statistics ...................................................................................... 11-45
Performing OAM Loopback ............................................................................................. 11-50
Performing OAM Link Trace ............................................................................................ 11-51
Examples ....................................................................................................................... 11-51
Configuring MD, MA, and MEP ................................................................................... 11-51
Configuring Service for Discovery .............................................................................. 11-52
Viewing MEP Status and Remote MEP ........................................................................ 11-54
Configuring Service and Destination NE ..................................................................... 11-54
Configuring Service Event Reporting .......................................................................... 11-55
Viewing MIP Status .................................................................................................... 11-57
Viewing Running Statistics ........................................................................................ 11-57
Viewing Current Statistics.......................................................................................... 11-59
Viewing Interval Statistics.......................................................................................... 11-60
Configuring and Viewing Delay Measurement Bins..................................................... 11-62
11.3 OAM EFM.......................................................................................................................... 11-71
Standards ...................................................................................................................... 11-72
Benefits ......................................................................................................................... 11-72
Configuring OAM EFM .................................................................................................... 11-72
Examples ....................................................................................................................... 11-73
11.4 TWAMP ............................................................................................................................. 11-74
Standards ...................................................................................................................... 11-75
Benefits ......................................................................................................................... 11-75
OAM TWAMP ............................................................................................................. 11-75
PMC TWAMP .............................................................................................................. 11-76
TWAMP Light ............................................................................................................. 11-77
Full TWAMP ............................................................................................................... 11-78
ICMP Echo Test .......................................................................................................... 11-81
UDP Echo Test........................................................................................................... 11-82
RADM ........................................................................................................................ 11-83
MOS On Demand ....................................................................................................... 11-84
Configuring TWAMP ........................................................................................................ 11-84
Configuring Controllers .............................................................................................. 11-85
Running Test Sessions Via Controller Peers ............................................................... 11-87
Configuring Test Profiles ........................................................................................... 11-90
Configuring Responders ............................................................................................ 11-91
Viewing TWAMP Status................................................................................................... 11-93
Viewing TWAMP Reports ................................................................................................ 11-94
Examples ....................................................................................................................... 11-96
Example – Configuring TWAMP in Layer-2 E-Line Service Mode .................................. 11-96
Example – Configuring TWAMP in Layer-2 E-LAN Service Mode .................................. 11-99
Example – Configuring TWAMP in Layer-3 Mode ...................................................... 11-103
Example – Configuring Management for TWAMP in PMC (relevant for ETX205A with PMC)
............................................................................................................................... 11-106
Example – Configuring TWAMP in PMC (relevant for ETX205A with PMC) ................ 11-109
ETX-2 xvii
Example – Viewing TWAMP Status ........................................................................... 11-111

Example – Viewing TWAMP Reports ......................................................................... 11-112
Configuration Errors ..................................................................................................... 11-115
11.5 Layer-3 Service Activation Test ...................................................................................... 11-117
Applicable Products...................................................................................................... 11-117
Standards .................................................................................................................... 11-117
Benefits ....................................................................................................................... 11-118
Functional Description ................................................................................................. 11-119
Test Phases ............................................................................................................. 11-119
Test Elements ......................................................................................................... 11-121
Configuring L3 SAT Entities .......................................................................................... 11-122
Configuring Generators ........................................................................................... 11-123
Configuring Peers .................................................................................................... 11-124
Configuring Peer Profiles ......................................................................................... 11-124
Configuring Session Profiles .................................................................................... 11-126
Configuring Responders .......................................................................................... 11-126
Viewing L3 SAT Test Status .......................................................................................... 11-127
Viewing L3 SAT Test Reports ........................................................................................ 11-128
Examples ..................................................................................................................... 11-135
11.6 RFC-2544 Testing ........................................................................................................... 11-141
Standards .................................................................................................................... 11-141
Benefits ....................................................................................................................... 11-141
Performing Tests ......................................................................................................... 11-143
Examples ..................................................................................................................... 11-146
Running RFC-2544 Test ........................................................................................... 11-146
Viewing Test Report ................................................................................................ 11-147
Viewing Test Status ................................................................................................. 11-151
Viewing Lost Frames Per Test Attempt .................................................................... 11-152
Viewing Test Results ............................................................................................... 11-152
11.7 Syslog ............................................................................................................................ 11-153
Standards .................................................................................................................... 11-153
Benefits ....................................................................................................................... 11-153
Elements ................................................................................................................. 11-154
Transport Protocol .................................................................................................. 11-154
Message Format...................................................................................................... 11-154
Facilities and Severities ........................................................................................... 11-155
Local Syslog Accounting .......................................................................................... 11-155
Configuring Syslog Parameters ..................................................................................... 11-156
Configuring the Syslog Device ................................................................................. 11-157
Configuring the Syslog Server.................................................................................. 11-157
Viewing Syslog Statistics .............................................................................................. 11-158
Clearing Syslog Statistics.............................................................................................. 11-159
Viewing the Syslog Local Accounting Log ..................................................................... 11-159
Clearing the Syslog Local Accounting Log ..................................................................... 11-159
Example ....................................................................................................................... 11-160
11.8 Y.1564 Ethernet Service Activation Test ......................................................................... 11-160
xviii ETX-2

Standards .................................................................................................................... 11-161
Benefits ....................................................................................................................... 11-161
SLAs ........................................................................................................................ 11-162
Policing ................................................................................................................... 11-162
Blocking User Traffic ............................................................................................... 11-162
Y.1564 over LAG ..................................................................................................... 11-162
Y.1564 Standard ..................................................................................................... 11-163
Test Elements ......................................................................................................... 11-165
Capacity .................................................................................................................. 11-166
Test Cases............................................................................................................... 11-166
Operation – Internal MEP Case ................................................................................ 11-166
Operation – Service MEP Case ................................................................................. 11-168
Running Test on MEP with No Configured Services .................................................. 11-171
Test Procedures ...................................................................................................... 11-171
Configuring Y.1564 Test .............................................................................................. 11-176
Adding Y.1564 Test Profile ...................................................................................... 11-176
Adding Y.1564 Responder ....................................................................................... 11-181
Viewing Test Status (Responder Side) ..................................................................... 11-183
Adding Y.1564 Generator ........................................................................................ 11-184
Viewing MEF46 Latching Loopback Generator Status............................................... 11-187
Viewing Test Status (Generator Side) ...................................................................... 11-188
Viewing Test Results ............................................................................................... 11-190
Examples ..................................................................................................................... 11-196
11.9 Performance Management ............................................................................................. 11-202
Benefits ....................................................................................................................... 11-203
Configuring Performance Management ........................................................................ 11-205
Viewing Performance Management Configuration ........................................................ 11-208
Examples ..................................................................................................................... 11-208
11.10 Detecting Problems ................................................................................................. 11-209
LEDs ............................................................................................................................ 11-210
Alarms and Traps ......................................................................................................... 11-210
Statistic Counters ........................................................................................................ 11-210
11.11 Handling Alarms and Events .................................................................................... 11-210
Alarm Soaking .............................................................................................................. 11-211
Configuring Alarm and Event Properties ....................................................................... 11-212
Controlling Popup Behavior .......................................................................................... 11-215
Working with Alarm and Event Logs ............................................................................. 11-215
Alarms and Events ....................................................................................................... 11-217
11.12 Troubleshooting ...................................................................................................... 11-218
11.13 Performing Diagnostic Tests.................................................................................... 11-220
Running a Ping Test ..................................................................................................... 11-220
Example .................................................................................................................. 11-220
Tracing the Route ........................................................................................................ 11-221
11.14 Frequently Asked Questions .................................................................................... 11-221
11.15 Technical Support.................................................................................................... 11-221
ETX-2 xix
Chapter 12. Software Upgrade

12.1 Compatibility Requirements................................................................................................ 12-1
12.2 Impact ................................................................................................................................ 12-2
12.3 Prerequisites ...................................................................................................................... 12-2
SFTP/FTP/TFTP Prerequisites ............................................................................................ 12-2
XMODEM Prerequisites ..................................................................................................... 12-2
Software Packs ................................................................................................................ 12-2
12.4 Upgrading Software via CLI ................................................................................................. 12-3
Verifying the Host Parameters ......................................................................................... 12-4
Pinging the PC .................................................................................................................. 12-4
Activating the SFTP Server ............................................................................................... 12-4
Activating the TFTP Server ............................................................................................... 12-4
Downloading the New Software Release File ................................................................... 12-5
Activating the Software ................................................................................................... 12-5
12.5 Upgrading ETX2 Software via the Boot Screen .................................................................. 12-7
Accessing the Boot Screen ............................................................................................... 12-7
Using FTP ....................................................................................................................... 12-10
Using TFTP ..................................................................................................................... 12-10
Using XMODEM .............................................................................................................. 12-11
Activating the Software ................................................................................................. 12-12
12.6 Verifying Upgrade Results ................................................................................................ 12-12
12.7 Restoring the Previous Version ......................................................................................... 12-12
Chapter 13. Application Tutorial

13.1 Equipment List ................................................................................................................... 13-2
13.2 Installing the Units ............................................................................................................. 13-2
13.3 Configuring the E-Line Service ............................................................................................ 13-2
Configuring E-Line for ETX205A ...................................................................................... 13-2
Configuring E-Line for ETX203AX .................................................................................... 13-3
Configuring E-Line for ETX-5 ............................................................................................ 13-3
13.4 Testing the Application ...................................................................................................... 13-5
Checking E-Line Connectivity ............................................................................................ 13-5
Checking Port/Flow Statistics ........................................................................................... 13-5
Appendix A. Connection Data

Appendix B. Test Plan
Appendix C. Clock Selection and Management (CSM)
xx ETX-2
Chapter 1
Introduction
1.1 Overview
ETX2 is RAD’s family of Carrier Ethernet demarcation and aggregation devices,
delivering RAD’s Service Assured Access solution, offering Ethernet services to the
customer premises in native Ethernet access networks over various infrastructure
types. ETX2 includes the demarcation devices ETX203AX, ETX203AM, and
ETX205A, as well as ETX220A, a 10 GbE demarcation and aggregation device. It
provides carrier-grade packet and TDM services for carriers, mobile operators,
and wholesalers, seeking to offer their customers unified SLA-based Ethernet
business services over any access technology.
ETX2 provides E-LAN, E-Line, and E-Tree Ethernet services over FE/GbE and
10GbE interfaces. It offers the same services over SHDSL, VDSL, PDH, and SDH
access lines. ETX2 supports an integrated Bridge functionality to allow full
support of E-LAN and E-Tree services, as well as ring topologies. Multiple VRFs (up
to 10) are supported when the TWAMP license is enabled.
ETX2 supports a rich offering of QoS functionality, including MEF 10.3 rank
policers that deliver high-scale multi-CoS services with hierarchical Quality of
Service (HQoS). It supports advanced scheduling, WRED per CoS, shaping per EVC
and port, and flexible classification rules with flexible access lists. Additionally, it
supports multicast with MLD snooping.
Featuring ultra-fast, hardware-powered processing, ETX2 performs OAM and PM
measurements with microsecond precision, offering powerful benefits such as
measuring and reporting bandwidth utilization per flow (EVC.CoS), collection of
PM parameters, and Y.1731-based measurement of frame loss, delay, and delay
variation. It also offers immediate detection of loss of continuity (LOC), triggering
sub 50 ms protection switching in ring topologies (G.8032v2) and end-to-end
service protection (G.8031).
ETX2 provides these types of Ethernet OAM:
• Single-segment (link) OAM according to IEEE 802.3-2005, active and passive
mode
• End-to-end connectivity OAM based on IEEE 802.1ag
• End-to-end service and performance monitoring based on ITU-T Y.1731
ETX2 supports L3 PM measurements based on TWAMP Light. It also offers
diagnostic tools that include MAC and IP-based intrusive and non-intrusive
loopbacks with MAC and IP swap, as well as advanced RFC-2544, Y.1564, and
L3 SAT generators and analyzers for service-oriented SLA validation and service
“birth certificate” reports.
ETX2 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
Furthermore, incorporating RAD’s SyncToP platform of synchronization and timing

over packet feature set, ETX2 utilizes standard technologies such as IEEE 1588v2
transparent clock (TC), slave clock, and boundary clock, as well as synchronous
Ethernet to ensure highly accurate timing delivery in packet-based mobile
backhaul networks. ETX2 can also act as an IEEE 1588v2 grandmaster (GM) with
an integrated GNSS receiver.
PMC (Performance Monitoring Controller) with integrated Intel x86 core is
available on ETX205A and provides the following high-scale (up to 3,000
sessions, 10 pps) features: TWAMP Light, Full TWAMP, ICMP Echo, and UDP Echo.
Product Options
Several product options of the unit are available, offering different combinations
of ports, enclosures, and functionalities. Available product options in the ETX2
family are ETX203AX, ETX203AM, ETX205A, and ETX220A. The following SW
licenses are available:
FE Provides Fast Ethernet of 100 Mbps (default)
GE Stronger than FE (default SW license option); 1 Gbps per

port; also provides Ethernet service
GE30 Strongest SW license option; 1 Gbps per port and 64

shaped EVCs per port; also provides smart GbE services
(ETX203AM, ETX203AX)
ETX203AX
ETX203AX device has six Ethernet ports. ETX203AX-E1 has five Ethernet ports
and one E1 port: ETX203AX-DSL has one Ethernet port and four SHDSL ports
(eight-wire).
• Network ports:
 In the device option without E1 port, up to two SFP or copper, depending
on whether port 2 is configured as a network or user port.
 In the device option with E1 port, the port 2 default functional mode is
network. However, you can only use this port once you change its
functional mode to user.
• User ports – up to four SFP or copper, or five if port 2 is configured as a user
port
• E1 port – a single integrated port for ETH and voice access applications
• SHDSL port – four ports (eight-wire); two ports per RJ-45 connector
The device has a universal AC/DC power supply in a plastic 8.6” enclosure or in a
metal enclosure for NEBS and temperature hardened options.
ETX203AX is offered with three SW licenses, as described in Table 1-1.
1-2 Overview ETX2

Installation and Operation Manual Chapter 1 Introduction
Table 1-1. ETX203AX SW Licenses
SW License FE GE GE30 Remarks
Part /GE /GE30 No notation for FE option.

number
notation
Maximum 100M 1G 1G
capability
of UTP port
Support 100BaseFx and 100BaseFx and 100BaseFx The FE option supports GE SFP,
SFP types 1000BaseFx 1000BaseFx and allowing for upgrade to GE or
1000BaseFx GE30 without having to change
HW. BW is limited by the shaper
rates.
Maximum 100 1000 1000

rate per
shaper
(Mbps)
Maximum 2 2 64
shapers per
NNI port
Maximum 2 2 8
shapers per
UNI port
Maximum 12 12 128
shapers per
device
ETX203AM
The ETX203AM device has a modular interface with network ports, as well as
four fixed SFP or copper ports that are user ports unless otherwise specified
below. The module has the following options:
• Two GbE SFP/copper combo ports (port 2 can be configured as a user port)
• Two SHDSL ports (four-wire)
• Four SHDSL ports (eight-wire)
• Four VDSL ports (eight-wire)
• Four E1/T1 ports (EoPDH)
• Eight E1/T1 ports (EoPDH)
• One T3 port (EoPDH)
• Two T3 ports (EoPDH)
• No module – The first fixed port can be configured as a user or network port.
• The device has an AC or DC power supply and a metal 8.5” enclosure.
ETX2 Overview 1-3

ETX203AM is offered with three SW licenses, as described in Table 1-2.
Table 1-2. ETX203AM SW Licenses
SW License FE GE GE30 Remarks
Part /GE /GE30 No notation for FE option.

number
notation
Maximum 100M 1G 1G
capability
of UTP port
Support 100BaseFx and 100BaseFx and 100BaseFx The FE option supports GE SFP,
SFP types 1000BaseFx 1000BaseFx and allowing for upgrade to GE or
1000BaseFx GE30 without having to change
HW. BW is limited by the shaper
rates.
Maximum 100 1000 1000

rate per
shaper
(Mbps)
Maximum 2 2 64 In ETX203AM, Port 3 is

shapers per considered an NNI port.
NNI port
Maximum 2 2 8
shapers per
UNI port
Maximum 12 12 128
shapers per
device
1-4 Overview ETX2

ETX205A
The ETX205A device has the following different options according to the metal
enclosure type:
Table 1-3. ETX205A Options
Metal Network Ports User Ports E1/T1 Ports X86 Card AC/DC Power
Enclosure Supply
Type
19” • Up to two Up to four (Optional) - Single or dual

enclosure SFP/copper SFP/copper combo Four or eight AC or DC power
Regular or combo ports. ports, or up to five E1/T1 ports supply
NEBS • Port 2 can be if port 2 is that can be
configured as configured as a configured to
a network or user port work in E1 or
user port. T1 mode, and
provide TDM
pseudowire
functionality
19” Up to two • Up to two - Internal x86 Single AC

enclosure SFP/copper SFP/copper card integrated power supply
with PMC combo ports. combo ports, or in the ETX205A
option Port 2 can be up to three if architecture
configured as a port 2 is Runs in Native
network or user configured as a mode –
port. user port. dedicated PMC
• An additional software runs
user port over embedded
appears on the LINUX.
panel but is not
usable.
Half 19” • Up to two Up to four Optional Single AC or DC

enclosure SFP/copper SFP/copper combo Four E1/T1 power supply
combo ports. ports, or up to five ports that can
• Port 2 can be if port 2 is be configured
configured as configured as a to work in E1
a network or user port or T1 mode,
user port. and provide
TDM
pseudowire
functionality
ETX205A (19” enclosure, non-NEBS and PMC) can be ordered with SyncE/1588v2
timing options, in which case the device provides the ports specified in Timing
Options.
ETX2 Overview 1-5

ETX220A
The ETX220A device has two, three, or four 10GbE ports, and 10 or 20GbE ports,
as follows:
• Network ports – two 10GbE XFP-based ports (The second port can be
configured as a network or user port.)
• User ports:
 Up to two 10GbE XFP-based ports
 0, 10, or 20GbE user ports (the first two ports can be configured as
network or user ports)
The following software license options are available:
• Basic Software Key (BSK) – one level of QoS with two shapers per NNI port
(2×8 CoS)
• Enhanced Software Key (ESK) – full QoS
The device has a single or dual AC or DC power supply and a metal 17.4”
enclosure.
ETX220A can be ordered with SyncE/1588v2 timing options, in which case the
device provides the ports specified in Timing Options.
Timing Options
If ETX205A or ETX220A are ordered with the timing option (PTP), the following
features are supported:
• Clock selection mechanism to select and distribute the device system clock,
including the holdover mechanism
• SyncE
• 1588 slave
• 1588 BC
In this option, the device also provides these additional timing ports:
• Station clock port (RJ-45) if the unit provides SyncE or 1588v2 timing
• ToD/1PPS RS-422 port (RJ-45) if the unit provides 1588v2 timing
• SMA port supplying external clock if the unit provides 1588v2 timing, or in
case of ETX220A if the unit provides SyncE
• SMA port supplying 1 pps if the unit provides 1588v2 timing
Applications
Ethernet Demarcation for Retail and Wholesale Services

ETX2 can function as an Ethernet demarcation device, separating the service
provider network, the access provider network, and the customer network.
Figure 1-1 illustrates a complete access solution with full service visibility. ETX2,
placed at connection points in the network, greatly contributes to monitoring and
1-6 Overview ETX2

troubleshooting the network, using its enhanced Ethernet OAM and performance
monitoring capabilities.
Core Services Metro/Core Access Aggregation Access Network First Mile
Internet
FE/GbE
Access
Management MiNID
1/10 GbE
ETX-2
Cell-Site
ETX-5 PDH/
Cloud/Data Center SDH
SDH/
SONET ETX-2
10 GbE
IP/MPLS
Ring
ETX-5 ETX-5 GbE xDSL

Carriers Interconnection
MSAN ETX-2
Customer
Premises
1/10 GbE
ETX-5 Ring
RAN Controller Site ETX-2
ETX-2
FE/GbE/10GbE
ETX-2
Service Assured Access
Service Assurance – End-to-End
Service Assurance – End-to-End (VPN)
Figure 1-1. Ethernet Demarcation Device
Mobile Demarcation Device for Mobile Backhauling

Applications
As a mobile demarcation device (MDD), ETX2 is installed at the operator tower
and controller sites equipped with an Ethernet port, connecting the IP-NodeB or
eNodeB to the packet network (see Figure 1-2). It features sophisticated traffic
management and service assurance capabilities, including proactive service
monitoring and fault identification throughout the entire network. Furthermore,
statistics analysis allows backhaul wholesalers to execute effective capacity
planning to overcome the “peak to mean” gap, such that bandwidth is added
only when needed, based on actual usage. ETX2 also backhauls legacy 2G and
3G E1/T1 traffic with TDM pseudowire services offering a “one box solution” for
mixed Ethernet and TDM services over a unified packet network.
ETX2 Overview 1-7

Mobile Network Transport Network Mobile Network

End-to-end SLA assurance, circuit validation, traffic management, TDM PWE
Macro or Small
Cells
RADview with ETH

PM portal
Node B
GPS ETX-2 TDM
BTS
RNC/aGW Router
ETX-5 MiNID
Packet
Switched G.8032 v2 eNB
Network 1/10 GbE
n x STM-1/ Ring
OC-3 ETX-5
BSC ETX-2 ETH

G.8032 v2
1/10 GbE
ETX-2 Ring Node B
ETX-2 TDM
BTS
ETX-2
Timing (1588PTP/SyncE)
Figure 1-2. Mobile Demarcation Device – ETX205A
Features
Traffic Processing
ETX2 incorporates a complete set of CE 2.0-certified Ethernet service tools that
allow the service provider to distinguish between high- and low-priority traffic,
and to optimize TCP sessions.
Forwarding
Traffic forwarding is performed via point-to-point or bridge mechanisms.
The ETX2 bridge operates in VLAN-aware or VLAN-unaware mode.
TDM Pseudowire
Note This feature is applicable to ETX203AX with a built-in E1 port, ETX205A with
built-in E1/T1 ports , and devices that support smart SFP MiTOP functionality.
ETX203AX can be ordered with an E1 port and ETX205A can be ordered with
integrated four or eight E1/T1 interfaces for TDM over packet pseudowire
services. Devices that have integrated MiTOPs also allow TDM over packet
pseudowire services. Each TDM pseudowire (PW) carries a single bundle (group of
timeslots) to a predefined far-end bundle.
The following standard payload encapsulation methods are supported:
CESoPSN (with or CES (Circuit Emulation Services) over PSN, for framed
without CAS) traffic, according to IETF RFC 5086
SAToP Structure-Agnostic TDM over Packet, for unframed traffic,

according to IETF RFC 4553
1-8 Overview ETX2

The pseudowire connections can be encapsulated by the device for the following
types of PSN transport networks:
• MEF 8 (Ethernet)
• UDP over IP
Layer-2 Control Processing (L2CP)

You can create L2CP profiles to define the handling of Layer-2 Control Protocol
traffic. You can assign a profile to Ethernet ports and flows. ETX2 then tunnels,
discards, or peers L2CP packets, according to the profile definition.
Link Layer Discovery Protocol (LLDP)

LLDP packets are sent periodically between ETX2 and neighboring devices on the
same physical LAN, advertising information about itself and obtaining neighbor
information. This automated discovery of devices simplifies management and
network maintenance, reducing general setup costs of new equipment.
MLDv2 Snooping
ETX2 IPv6 routers support Multicast Listener Discovery Version 2 (MLDv2)
protocol to discover multicast listeners on attached links and addresses that are
of interest to them. Bridges use MLDv2 Snooping to reduce multicast traffic by
analyzing MLDv2 messages and limiting multicast traffic to ports interested in it.
Routing
Device management, as well as other L3 ‘modules’, such as 1588 (8265.1), TDM
PW (UDP/IP), and TWAMP, use the ETX2 routing scheme.
When the TWAMP license is enabled, ETX2 supports multiple VRFs (up to 10);
management is supported over VRF1 only.
Resiliency and Optimization

ETX2 provides the following to ensure five nines (99.999%) availability and
sub-50 ms restoration in the event of network outages:
• Link redundancy in a LAG architecture that supports the LACP protocol
according to 802.3-2005
• LAG delivery of link protection and link redundancy between two network
ports or two user ports
• Dual homing technology in a 1:1 architecture allows ETX2 to be connected to
two different upstream devices
• Ethernet protection switching in the following modes for network ports per
ITU-T G.8031:
 1:1 bidirectional with APS protocol – Endpoints negotiate using APS
protocol.
 1:1 unidirectional without APS protocol – Endpoints act independently
and do not negotiate with each other. Unidirectional mode is suitable for
EVC level dual homing applications.
ETX2 Overview 1-9

• Ethernet Ring Protection per G.8032v2 Layer-2 to protect against link and
node failures. This supports ring topology, and delivers low-cost traffic
protection and rapid service restoration, with SDH/SONET type resilience.
The ETX2 fault propagation mechanism enables propagating user port failures to
the network and the remote end, as well as propagating network failures back to
the user port. The mechanism has a set of triggers and actions (i.e. rules) that
are based on the physical layer (e.g. port failure) or ETH OAM (AIS, RDI, LOC,
etc.). Up to 32 fault propagation rules can be defined.
A Traffic Management Fault Propagation (TMFP) license can be enabled to provide
the Fault Propagation mechanism with a set of triggers and actions for queue
block shaper and flow policer (Event Manager).
The additional fault propagation actions are:
• Change policer rate
• Change shaper rate
Configuration of these actions enables you to implement network/application
level redundancy schemes while controlling the bandwidth of the different
redundant paths.
Timing and Synchronization
Note This section is relevant only when ETX205A or ETX220A are ordered with the
appropriate timing options.
The unit’s SyncToP™ suite includes clock recovery using IEEE 1588v2 Precision
Timing Protocol, Synchronous Ethernet (SyncE), and a built-in input/output clock
interface.
The ETX2 domain (system) clock is selected from up to two user-configurable
sources. Each source can be an Ethernet port (recovered SyncE clock), the station
clock, the internal GPS (for device with GNSS), or the recovered 1588v2 clock (i.e.
1588v2 slave clock; relevant only for devices without GNSS).
The clock selection mechanism (CSM) selects the best clock according to its
quality level (by SSM) and configured priority. The selected domain clock and its
quality level are distributed to all Ethernet ports (Tx SyncE and SSM) and is the
reference clock for the 1588v2 master.
A dedicated IEEE 1588v2 clock recovery module allows ETX2 to recover the clock
from a remote 1588v2 master clock. Furthermore, ETX2 supports a 1588v2
master clock that can function in a boundary clock application or as a standalone
grandmaster (relevant for GNSS option of ETX205A).
The Network Time Protocol (NTP) provides the means of synchronizing all
managed elements across the network to a reliable clock source provided by
multiple servers. ETX2 supports the client side of NTP v.3 (RFC 1305).
Integrated x86 Processor and PMC
Note This section is relevant only for ETX205A with PMC.
1-10 Overview ETX2

ETX2 can be ordered with an integrated Intel® x86 core.

The Intel® x86 core can work in the following operation mode:
• PMC – x86 processor with a dedicated PMC application that runs in native
mode (Linux environment); provides multiple testing tools for measuring
service performance monitoring over Ethernet packet networks.
The ETX2 NID and x86 card are interconnected via internal Ethernet ports 5
and 6; you configure flows over these ports in order to route data to the x86
card.
The PMC option is not available with the following:
• Timing options
• NEBS-compliant enclosure
• Power supply redundancy
• Temperature-hardened option
PMC can be used to test thousands of Layer-3 services simultaneously.
It includes the following high-scale (3,000 sessions, 10pps) features:
• TWAMP Light
• Full TWAMP (with TWAMP Control protocol)
• ICMP Echo
• UDP Echo
• MOS on demand
• Responder Agnostic Delay Measurement (RADM)
• Multiple VRFs
PMC delivers up to 3000 sessions @10 pps for Full TWAMP and TWAMP Light. It
provides a subset of ETX2 features configured via standard RAD CLI, and
interoperates with the ETX2 main module.
Management and Security

ETX2 access control lists (ACLs) are used to flexibly filter and mark management
traffic.
ETX2 can be managed as follows:
• Local management via ASCII terminal, connected to the V.24/RS-232 DCE
control port
• Local management via dedicated out-of-band management port
• Remote management via an Ethernet port using Telnet, SSH, or RADview,
RAD’s SNMP-based management system
• Remote management using Point-to-Point Protocol over Ethernet (PPPoE) -
establishes a management channel that a remote management system can
use to send software and configuration files and manage ETX2.
ETX2 Overview 1-11

ETX2 supports a variety of access protocols including CLI over Telnet, SNMP, and
TFTP/SFTP. You can create databases and scripts of commonly used commands
and easily apply them to multiple units in your infrastructure.
To ensure client-server communication privacy and correct user authentication,
ETX2 supports the security protocols listed below:
• SNMPv3 (provides secure access to the device by authenticating and
encrypting packets transmitted over the network)
• RADIUS (client authentication)
• TACACS+ (client authentication)
• SSH for Secure Shell communication session
The ETX2 DHCP client enables plug-and-play zero touch provisioning via standard
TFTP functionality. This includes downloading the latest SW version and
configuration files.
ETX2 provides integrated management for RAD’s smart SFP devices, allowing
TDM over packet pseudowire services (using MiTOP devices), and Ethernet over
TDM (using MiRICi devices). The following devices are supported:
• MiRICi-E1/T1/E3/T3
• MiRICi-155
• MiTOP-E1/T1/E3/T3
Monitoring and Diagnostics

ETX2 offers several types of diagnostic procedures:
• Ping test – checks IP connectivity by pinging remote IP hosts
• In-service ICMP Echo ping test – checks the connectivity across Layer-2
service paths
• Trace route – quickly traces a route from ETX2 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, disrupting the traffic. This loopback cannot pass
through Ethernet bridges.
 Layer-2/Layer-3 loopback on flows, with optional MAC and/or IP address
swapping. When the loopback is active, ETX2 can exchange the source
and destination MAC/IP addresses of the incoming packets. This loopback
passes through Ethernet bridges and routers, and does not disrupt traffic
flows that are not being tested.
• Service activation tests:
 RFC-2544 traffic generator and analyzer
 L3 SAT for Layer-3 testing
 ITU-T Y.1564 traffic generator and analyzer for Layer-2 testing
• Syslog – protocol that generates and transports event notification messages
from the device to servers across IP networks
1-12 Overview ETX2

Hardware-Based Ethernet OAM and Performance Monitoring

Featuring ultra-fast, hardware-based processing capabilities, ETX2 performs OAM
and PM measurements in under 1 microsecond with maximum precision. The
device has a comprehensive Ethernet OAM suite that includes Ethernet Service
OAM (IEEE 802.1ag), Ethernet link OAM (IEEE 802.3-2005, formerly IEEE 802.3ah),
and Performance Monitoring (ITU-T Y.1731), providing tools to monitor and
troubleshoot an Ethernet network and quickly detect failures.
Quality of Service (H-QoS)

ETX2 efficiently handles multi-priority traffic on a per-flow basis, with ultra-high
capacity that enables simultaneous processing of multiple service flows. The
device enables multi-criteria traffic classification as well as metering, policing, and
shaping to help carriers rate-limit user traffic according to predefined CIR
(committed information rate) and EIR (excess information rate) profiles.
Additionally, ETX220A provides MEF 10.3 rank policers, delivering high-scale
multi-CoS services with hierarchical Quality of Service (HQoS).
Enhanced quality of service is further supported by a hierarchical scheduling
mechanism that combines strict priority (SP), weighted fair queue (WFQ), and
best effort (BE) scheduling, to efficiently handle real-time, premium, and best-
effort traffic. Scheduling and shaping are supported at the EVC and port levels.
The queue mapping functionality associates user priorities (packet attributes) to
egress queues. The marking functionality maps user priorities (packet attributes)
and the packet color (green/yellow) to the SP priority (p-bit) and DEI.
ETX2 also uses weighted random early detection (WRED) policy for intelligent
queue management and congestion avoidance. Packet editing capabilities include
IEEE 802.1ad Q-in-Q tagging and color-sensitive P-bit re-marking, which ensures
metering continuity across color-aware and color-blind Metro networks.
RADview Performance Management

The Performance Management (PM) portal is an SLA assurance system that is part
of the RADview management system, enabling real-time monitoring of Ethernet
service performance by collecting KPI (key performance indicators) data from RAD
devices. Measured metrics are based on ITU-T Y.1731 and include Frame Delay,
Delay Variation, Frame Loss, and Availability. Latency and jitter results are based
on round-trip measurements. It allows service providers to easily evaluate actual
performance over time and compare it to their committed SLA guarantees. In
addition, it enables immediate detection of service degradation, so that remedial
actions are taken to quickly restore performance levels.
Note In order to ensure discovery of the Ethernet services by RADview, you need to
assign a service name to the relevant flows, as well as ensure that collecting
performance monitoring data is enabled for the relevant flows, services, and
destination NEs.
ETX2 Overview 1-13

1.2 New in This Version

The following features have been added for Version 6.5:
• ETX203AX-DSL device with built-in eight-wire SHDSL uplink
• ETX220A – increased MEP/MIPs to 500
• LED signaling
• Overheat auto shutdown
• File management enhancements – new user file directory
• SSH ciphers code limiting
• Login timer
• No activity timer
• Local Syslog accounting
• Ordering option identification through CLI (ETX203AX, ETX205A, ETX220A)
• Credentials masked on TACACS server accounting log.
• Ability to send messages to other connected users (local and remote)
• Configurable TFTP server timeout and retry-timeout settings
• Up to 32 Event Manager rules
1.3 Physical Description

The following figure shows the ETX2 devices:
• Top row – ETX203AM with T3 network module, and ETX203AX
• Middle row – ETX205A
• Bottom row – ETX220A
Figure 1-3. ETX2
1-14 Physical Description ETX2

Refer to the Installation and Setup chapter for a detailed description of the ETX2
interface connections.
1.4 Functional Description

Figure 1-4 and Figure 1-5 show the data flow in the device. Table 1-4 provides an
overview of the traffic handling stages.
CoS/Queue Color CIR/EIR VLAN

Flow: Video
Mapping Mapping Policing Editing
Scheduling EVC 1
(WFQ, SP, Shaping
Flow: Data
CoS/Queue Color CIR/EIR VLAN BE)
EVC 1
EVC 2
WFQ
Classification
Flow: Voice
EVC n
CoS/Queue Color CIR/EIR VLAN Scheduling

Flow: Mngt. Shaping
Mapping Mapping Policing Editing (WFQ, SP, EVC n
BE)
Flow: Clock
Figure 1-4. Data Flow Including Scheduling and Shaping at Level 0 (ETX203AM, ETX203AX, and
ETX205A)

Flow: Video
Scheduling EVC 1
(WFQ, SP, Shaping
CoS/Queue Color CIR/EIR VLAN BE)
Flow: Data
EVC 1
EVC 2
WFQ
Shaping
Classification
Flow: Voice
Mapping Mapping Policing Editing EVC n
CoS/Queue Color CIR/EIR VLAN Scheduling

Flow: Mngt. Shaping
Mapping Mapping Policing Editing (WFQ, SP, EVC n
BE)
Flow: Clock
Figure 1-5. Data Flow Including Scheduling and Shaping at Level 0 and 1 (ETX220A)
Table 1-4. Traffic Handling Stages
Processing Stage Description
Classification Classifying traffic by flows per EVC/EVC.Cos
CoS/queue mapping Mapping traffic to queues by packet attributes (or to a

specific queue).
Another method to map traffic to queues is by internal Cos
assignment; used in certain configuration scenarios.
Color mapping Mapping traffic to ingress color by packet attributes (or to a

specific color)
Policer per Flow or Policing the traffic of the flow or group of flows.
Group of Flows If color aware policer, uses the packet ingress color as set by
color mapping.
ETX2 Functional Description 1-15

Processing Stage Description
VLAN Editing Performing VLAN manipulations, such as push s-tag, pop,

mark, and more, as well as marking the p-bit and DEI on the
outer VLAN header (per packet attribute or internal CoS).
Queues Egress traffic buffered into configurable size queues.

Congestion avoidance policy is per color:
• Green packets – tail drop
• Yellow packets – per WRED profile
Scheduling and Scheduling the various queues to transmit per queue priority
Shaping at Level 0 and weight
(EVC Level) Shaping the aggregate EVC traffic
Scheduling and Scheduling the various queues to transmit per queue priority
Shaping at Level 1 and weight
(Port Level) Shaping the aggregate port traffic (ETX220A only)
1-16 Functional Description ETX2

1.5 Technical Specifications
Ethernet Interfaces Number of Ports Six for device without E1 port; five for device with E1
(ETX203AX) port (ETX203AX-E1); one (User) for device with
embedded SHDSL ports (ETX203AX-DSL)
Network: up to two (Port 2 can be configured as a
network or user port.)
User: one, four, or five (if port 2 is configured as
user)
Note: In ETX203AX-E1, you can only use Port 2 after
you configure it as a user port.
Type SFP or copper port

Fast or Gigabit Ethernet
Fiber Optic See SFP Transceivers data sheet.

Specifications and
Ranges
Electrical Operation 10/100 Mbps or 10/100/1000 Mbps, full duplex,

Mode autonegotiation, MDI/MDIX
Connector SFP slot or RJ-45
E1 Interface Number of Ports One

(TDM PW)
Compliance G.703, G.732n, G.732s
(ETX203AX)
Operation Mode GFP – single VCG

HDLC – single group over unframed E1
Framing Unframed – for HDLC encapsulation only
G.732n-crc framing – for GFP encapsulation only
Data Rate 2.048 Mbps
Impedance 120Ω, balanced
Line Coding HDB3/AMI
Connector Electrical, RJ-45
SHDSL Interface Number of Ports Four (8-wire); two per connector

(ETX203AX)
Type 2-wire unconditioned dedicated line (twisted pair)
Operation Mode STU-R (remote customer premises equipment)
Line Coding DMT; support for 16TCPAM and 32TCPAM line code
ETX2 Technical Specifications 1-17

Line Rate (pair) 192 kbps–5696 kbps with steps of n × 64 kbps per
2-wire
Impedance 135Ω
Connector Two RJ-45
Standards ITU-T G.991.2 (SHDSL.bis)

ITU-T G.994.1 (DSL Handshake)
EFM 802.3ah (EFM and EFM bonding)
Power (ETX203AX) AC/DC AC/DC inlet connector with auto detection
Wide-range AC: 100-240 VAC (-10%, +6%), 50/60 Hz
DC: 48 VDC (40–60 VDC)
Power Consumption 15W max
Physical Height Regular enclosure: 43.7 mm (1.7 in)

(ETX203AX)
Metal enclosure: 43.7 mm (1.7 in)
Width Regular enclosure: 220 mm (8.7 in)

Metal enclosure: 215.5 mm (8.5 in)
Depth Regular enclosure: 170 mm (6.7 in)

Metal enclosure: 152.5 mm (6 in)
Weight 0.7 kg (1.54 lb)

Note: ETX203AX with E1 port only comes in metal
non-hardened enclosure.
Environment Storage -40 to 85°C (-40 to 185°F)

(ETX203AX) Temperature
Operating Regular: 0 to 50°C (32 to 122°F)

Temperature
Temperature-hardened and NEBS (only for device
without E1 port): -20 to 65°C (-4 to 149°F)
Notes:
• In the temperature-hardened device, a single
SFP-30H is supported at temperature up to 62°C.
• In the regular enclosure (plastic), it is
recommended to use a hardened SFP only, in
order to operate the device at ambient
temperature up to 50°C.
Humidity Up to 90%, non-condensing
1-18 Technical Specifications ETX2

Modular Network Number of Ports Two on slot 1 (The second port can be configured as
GbE Interface a network or user port.)
(ETX203AM)
Type SFP/copper combo


Specifications and
Ranges

Connector RJ-45 or SFP
Modular Network Number of Ports Four or eight on slot 1

E1/T1 Interface
Compliance G.703, G.823, G.7041, G.7042, G.7043, G.8040
(EoPDH), E1 mode
(ETX203AM) Framing Framed (G.732N with CRC)

75Ω, unbalanced (via adapter cable)
Line Coding HDB3
Connector Electrical, four RJ-45 connectors:

Four E1 ports – One E1 interface per RJ-45
Eight E1 ports – Two E1 interfaces per RJ-45, with
adapter cable
Modular Network Number of Ports Four or eight on slot 1

E1/T1 Interface
Compliance ANSI T1.101, ANSI T1.403, G.7041, G.7042, G.7043,
(EoPDH), T1 mode
G.8040
(ETX203AM)
Framing ESF
Line Coding B8ZS
Connector Electrical, four RJ-45 connectors:

Four T1 ports – one T1 interface per RJ-45
Eight T1 ports – two T1 interfaces per RJ-45, with
adapter cable

Modular Network T3 Number of Ports 1 or 2 on slot 1

Interface (EoPDH)
Compliance G.703, G.823, G.7041, G.7042, G.7043, G.8040
(ETX203AM)
Framing C-bit parity
Impedance 75Ω, unbalanced
Line Coding B3ZS
Connector Coaxial BNC (one pair per port)
Modular Network Number of Ports Four (8-wire); two per connector

SHDSL Interface
(ETX203AM)
Line Coding DMT; support for 16TCPAM and 32TCPAM line code
Line Rate (pair) 192 kbps–5696 kbps with steps of n × 64 kbps per
2-wire
Impedance 135Ω
Connector 4-wire ordering option: One RJ-45

8-wire ordering option: Two RJ-45
Standards ITU-T G.991.2 (SHDSL.bis)

Modular Network Number of Ports Four (8-wire) on slot 1

VDSL Bonding Card
(ETX203AM)
Line Coding 16 or 32 TC-PAM
Payload Rate 100Mbps DL/50Mbps UL per line
Impedance VDSL2 over POTS: 100Ω

VDSL2 over ISDN: 135Ω
Connectors Two RJ-45s (UTP)
Standard ITU-T G.993.2, G.997.1, G.998.2, IEEE 802.3

Temperature Operates in non-hardened device of up to 35°C
(90°F). Above this temperature, requires hardened
device.

Fixed Ethernet Number of Ports Four on slot 0

Interfaces
Type Copper or fiber optic (SFP-based)
(ETX203AM)

Specifications and
Ranges

Power AC 100–230 VAC (-10%, +6%), 0.4A-0.2A, 50/60 Hz

(ETX203AM)
DC 48 VDC (40-60 VDC), 0.4/0.3A
Power Consumption Modular base: 12W max

Modular uplink: 5W max
VDSL: 10W max
Physical Height 43.7 mm (1.7 in)

(ETX203AM)
Width 215 mm (8.5 in)
Depth 300 mm (11.8 in)

(ETX203AM) Temperature

Temperature Temperature-hardened and NEBS:-20 to 65°C
(-4 to 149°F)
Ethernet Interfaces Number of Ports Network: two (The second port can be configured as
(ETX205A) a network or user port.)
User: four
Type SFP/copper combo


Specifications and
Ranges
Electrical Operation 10/100/1000 Mbps, full duplex, autonegotiation,

Mode MDI/MDIX
Connector RJ-45 or SFP

E1/T1 Interface Number of Ports Four or eight (for half 19” enclosure, only 4)
(TDM PW), E1 Mode
Compliance G.703, G.732n, G.732s
(ETX205A)
Framing Unframed or framed

75Ω, unbalanced (via adapter cable)
Line Coding HDB3
E1/T1 Interface Number of Ports Four or eight (for half 19” enclosure, only 4)
(TDM PW), T1 Mode
Compliance ANSI T1.101, ANSI T1.403
(ETX205A)
Framing Unframed or ESF
Line Coding B8ZS
Station Clock Mode Input and output

(ETX205A)
Bit Rate 2.048 MHz/2.048 Mbps (E1)
Line Code AMI/HDB3
Nominal Impedance 120Ω balanced

75Ω unbalanced (via adapter cable)
Connector RJ-45 shielded
ToD/1PPS Mode Output

(ETX205A)
Line/connector RS-422 RJ-45 (NMEA 0183)
EXT-CLK (ETX205A) Mode Output
Signal type Square wave
Bit Rate 2.048 MHz
Amplitude 2.0 Vpp (5.0 unloaded)
Nominal Impedance 50Ω unbalanced

Connector SMA (mini BNC)
1PPS (ETX205A) Mode Output
GNSS (ETX205A) Frequency L1 (1.575 GHz)
RF Cable Impedance 50Ω
Receiver Sensitivity -148 dBm
Maximum Gain 50 dB
Recommended 1.5 dB
Noise Figure
RF DC Voltage 3.3V
Supply
Maximum DC 50mA
Current
Connector SMA (F)
Power (ETX205A) AC 100–240 VAC (-10%, +6%), 50/60 Hz
DC 19” enclosure: 24/48 VDC (20-60 VDC)

½ 19” enclosure: 48 VDC (40-60 VDC)
Power Consumption 19” enclosure: 22W max

½ 19” enclosure: 21W max
PMC option: 90W max
Physical (ETX205A) Height 43.7 mm (1.7 in)
Width 19” enclosure: 440 mm (17.4 in)

½ 19” enclosure: 215 mm (8.5 in)
Depth 19” enclosure: 240 mm (9.5 in)

½ 19” enclosure: 300 mm (11.8 in)
Weight 19” enclosure: 3.1 kg (6.8 lb)

½ 19” enclosure: 2.4 kg (5.2 lb)

PMC option: 3.9 kg (8.6 lb)

(ETX205A) Temperature

Temperature
PMC option: 0 to 45°C (32 to 113°F)
Temperature-hardened and NEBS: -40 to 65°C
(-40 to 149°F)
10GbE Interfaces Number of Ports 2 or 3:

(ETX220A)
• Network: 2 on slot 4 (The second port can be
configured as a network or user port.)
• User: Up to 2 on slot 3
The following Ethernet configurations can be
ordered:
• 2 × 10GbE + 20 × 1GbE
• 3 × 10GbE + 10 × 1GbE
• 4 × 10GbE + 10 × 1GbE
• 4 × 10GbE
Type Fiber optic (XFP-based)

10-Gigabit Ethernet
Connector XFP
Transceiver Types 10GBaseSR, 10GBaseER, 10GBaseLR, 10GBaseZR
1GbE Interfaces Number of Ports 0, 10, or 20 (the first two ports can be configured as
(ETX220A) network or user ports)
Refer to the 10GbE specification for the Ethernet
configurations.
Type Copper or fiber optic (SFP-based)


Specifications and
Ranges
Station Clock Mode Input and output

(ETX220A)
Bit Rate 2.048 MHz/2.048 Mbps (E1)

Line Code AMI/HDB3
Nominal Impedance 120Ω balanced

75Ω unbalanced (via adapter cable)
Connector RJ-45 shielded
ToD/1PPS Mode Output

(ETX220A)
Line/connector RS-422 RJ-45 (NMEA 0183)
EXT-CLK (ETX220A) Mode Output
Bit Rate 2.048 MHz
1PPS (ETX220A) Mode Output
Power (ETX220A) AC 100-240 VAC (-10%, +6%), 1A-0.5A, 50/60 Hz
DC 48 VDC (40-60 VDC), 0.4/0.3A
Power Consumption 70W max
Physical (ETX220A) Height 43.7 mm (1.7 in)
Width 440 mm (17.4 in)
Depth 240 mm (9.5 in)


(ETX220A) Temperature

Temperature Temperature-hardened and NEBS: -20 to 65°C
(-4 to 149°F)
Flows and Max. Number Flows/ ETX203AX, ETX203AM, ETX205A: 270

Classification Classification
ETX220A: 1,860 (can include up to 1,000 multi-CoS
Profiles
flows)
Note: In ETX220A, classification matches may also
be a scaling factor.
Max. Number ETX203AM, ETX203AX, and ETX205A:

Classification 1,024ETX220A: Resource is allocated to the ports
Matches per Device according to the ETX220A ordering options, as
follows:
2x10GbE + 20x1GbE - 930 matches for 1/1-1/10,
2/1-2/10; 930 matches for 4/1, 4/2
3x10GbE + 10x1GbE - 930 matches for 1/1-1/10, 3/1;
930 matches for 4/1, 4/2
4x10GbE + 10x1GbE - 930 matches for 1/1-1/5, 3/1,
3/2; 930 matches for 1/6-1/10, 4/1, 4/2
Max. Number 30
Classification
Matches per Profile
Max. Number Up to 10 per classifier profile

Matches for IP
Classification
Max. Number Flows Five

in a Unidirectional
Hub
Max. Number Seven

Unidirectional Hubs
per Device
Bridge Mode VLAN-aware, VLAN-unaware
Bridge Instances 1

Max. Number Bridge ETX203AM, ETX203AX, ETX205A: 16

Ports
ETX220A: 80
Max. Number MAC ETX203AM, ETX203AX, ETX205A: 32K

Table Entries (per
ETX220A: 16K
device/per VLAN)
Max. Number ETX203AM, ETX203AX, ETX205A: 40

Broadcast Domains
ETX220A: 300
(VLANs) in
E-Tree/E-LAN Mode
SFP Transceivers Power For all non-temperature-hardened options, use SFP

transceivers with maximum operating temperature
70°C (158°F). For all temperature-hardened options,
use SFP transceivers with maximum operating
temperature 85°C (185°F).
Router General IPv4, IPv6, static router
Number of VRFs 10
(Router Instances)
PMC in ETX205A: four
Number of Router 32
Interfaces
PMC in ETX205A: 64
Notes:
• Only one router interface is supported when
working with PWs.
• Only two router interfaces can be configured for
management.
• In PMC, one router interface can be shared
between the TWAMP controller/responder and
management access.
OAM CFM 8021.1ag, Y.1731
Max. Number MDs ETX203AM, ETX203AX, ETX205A: 127

per Device*
ETX220A: 500
Max. Number MAs ETX203AM, ETX203AX, or ETX205A : 127

per Device*
ETX220A: 500
Max. Number MEPs Up to eight (configuration on EVC.cos)

per MA*

Max. Number MEPs ETX203AM, ETX203AX, or ETX205A: 127

per Device*
ETX220A: 500
Notes:
• In ETX220A, the number of MEPs is limited to 128
when the CCM period is set to 3.3 ms; if it is set
to 10 ms and up, 255 MEPs are supported.
• In ETX203AX, ETX203AM, and ETX205A, a
maximum of 10 Up MEP instances are supported.
Max. Number ETX203AM, ETX203AX, or ETX205A: 512

Remote MEPs per
ETX220A: 1,024
Device*
Max. Number Eight

MD-level MIPs
Max. Number Eight

Services (CoS) per
MEP*
Max. Number ETX203AM, ETX203AX, or ETX205A: 255

Services per Device*
ETX220A: 500
Max. Number Dest ETX203AM, ETX203AX, or ETX205A: 255

NEs (PM sessions –
ETX220A: 500
LM/DM pairs) per
Device* Notes:
• Loss Measurement (LM) can be LMM or SLM.
• Single SLM session per Dest NE is supported.
• Single Test ID per EVC.CoS and RMEP is supported.
• SLM is limited to 600 pps Tx and 600 pps Rx.
• No PPS limitation for LMM (HW implementation)
*
Note: The above OAM (CFM) values are subject to
the limit of 600 received PPS (packets per second).
This includes SLM, AIS, linktrace (LTM/LTR), and other
management packets. It does not include continuity
check (CC), loopback (LBM/LBR), delay measurement
messages (DMM/DMR), or loss measurement
messages (LMM/LMR), which are subject to the
hardware rate of 1 Gbps.
OAM TWAMP Max. Number Layer-2 E-Line service: three

TWAMP Entities
Layer-2 E-LAN service over bridge: seven
(Controllers or
Responders) Layer-3: 15

Max. Number 150

Sessions Per Device
Max. Rate 150 pps

Supported For
TWAMP Sessions
Per Device
Max. Number Peers 15

Supported for
TWAMP Controllers
Max. Rate Per 10 pps

Session
PMC TWAMP Max. Number 64

(ETX205A) TWAMP Controllers
Max. Number
Eight
TWAMP Responders
Max. Number 3,000

Sessions
Max. Number Peers 3,000
Max. Rate per 10 pps for Full TWAMP and TWAMP Light
TWAMP Session 1 pps for ICMP Echo and UDP Echo
Quality of Service Policer Dual Token Bucket mechanism (two rates, three
(Traffic colors)
Management)
CIR, CBS, EIR, EBS
Color Mode Color blind, color aware with coupling flag support
Standard MEF 10.3
Max. Number Policer ETX203AX, ETX203AM, ETX205A: 270

Instances
ETX220A: 1860
Max. Number Policer ETX203AM, ETX203AX, ETX205A: 192

Profiles
ETX220A: 1000 (envelope/regular/aggregate); up to
250 different profiles
Max. Number Policer ETX203AM, ETX203AX, ETX205A: 30160

Aggregates
ETX220A: 160
Max. Flows per 100

Policer Aggregate

Max. Number Ranks Four (ETX220A only)

in Envelope Policer
Max. Number 1000 (ETX220A only)

Envelope Instances
Max. Number 64 (ETX220A only)

Envelope Profiles
Max. Number ETX203AM, ETX203AX, ETX205A: 60

Shaper Profiles
ETX220A: 126
Max. Number Queue ETX203AM, ETX203AX, ETX205A: 116

Blocks in Device
ETX220A: 250
Max Number Queue ETX203AX, ETX205A : Network ports – 63; User

Blocks per Port ports – Eight
ETX203AM: Network ports and port 3 – 63,

Other ports – Eight
ETX220A: 10GbE user/network ports – 239,
1GbE ports 1/1 to 1/2 – 32,
1GbE ports 1/3 to 1/4 – 32,
1GbE ports 1/5 to 1/10 – 16,
1GbE ports 2/1 to 2/10 – 8
Max. Queue Size ETX203AX, ETX203AM, ETX205A: 511 frame

buffers, 1 Mbyte
ETX220A: 4k frame buffers, 8 Mbytes
Max. Number WRED 8

Profiles
Max. Number Queue 24

Group Profiles

Block Profiles
Max. Number 12
Marking Profiles

Mapping Profiles
Timing (per relevant Number of Clock One (master and fallback)

ordering options) Domains

Standards Normal operation (locked to upstream clock source):

Compliance ITU-T G.8262 and G.813 ETH/SDH clock
specifications, as well as G.8264 for Ethernet clock
SSM (ESSM) handling.
Holdover with Stratum 3 TCXO: ITU-T G.8262/G.813
long-term transient response (holdover)
specifications.
Holdover with Stratum 3E OCXO: ITU-T G.8262/G.813
and ITU-T G.812 Type III clock long-term transient
response (holdover) specifications.
Clock Sources Up to two inputs for selection mechanism

1588v2 recovered, station (BITS/GPS) , ETH port Rx
1588v2 Master/slave/transparent (TC), ITU G.8265.1,

G.8275.1
G.8273.2 clock specification support for G.8275.1
Sync-E Master/slave, ITU-T G.8261–G.8266, with

primary/secondary clock redundancy
Standards CE 2.0, MEF 6 (E-Line – EPL and EVPL, E-LAN – EPLAN

Compliance and EVPLAN), MEF 10, MEF 9, MEF 14, MEF 20,
IEEE 802.3, 802.3ad, 802.3ae, 802.3u, 802.1D,
802.1Q, 802.1p, 802.3-2005, 802.1ag-D8,
ITU-T Y.1731, G.8031, G.8032v2, G.8262, G.8273.2,
G.8275.1, 1588v2, RFC-2544, ITU-T Y.1564
Management Local V.24/RS-232 asynchronous DCE

Data rates: 9.6, 19.2, 115.2 kbps
RJ-45 connector


Chapter 2
Installation and Setup
This chapter describes installation and setup procedures for the ETX2 unit.
After installing the unit, refer to the Operation and Maintenance chapter for
operating instructions and the Management and Security chapter for
management instructions.
If you encounter a problem, refer to the Monitoring and Diagnostics chapter 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 Safety
ETX2 devices are provided with the following types of grounding lugs:
• ETX2 NEBS-compliant enclosures (except for ETX203AM) for central office
or cell-sites have a UL-recognized dual grounding lug.
Figure 2-1. Dual Grounding Lug

• ETX2 enclosures that are not NEBS-compliant, as well as ETX203AM, are
provided with a single ring tongue grounding lug.
Figure 2-2. Single Ring Tongue Grounding Lug
ETX2 Safety 2-1

Chapter 2 Installation and Setup Installation and Operation Manual
Screws are provided for attaching the grounding lug to ETX2, as well as star or
spring washers that ensure proper contact and preclude loosening of the screws.
 To connect a grounded wire to the grounding lug:

1. Remove the grounding lug from ETX2, ensuring that you keep the washers.
2. Use AWG 8 copper wire (approximately 6 mm2) for the dual grounding lug
and AWG 16 copper wire (approximately 1.25 mm2) for the ring tongue
grounding lug.
Note Do not use any wires other than copper wires for grounding.
3. If isolated wire is used, remove the insulation at the end.

4. Coat the bare wire with an antioxidant material and crimp the bare wire end
to the lug, using the proper tool.
5. Reconnect the lug with the crimped wire to ETX2, using the provided screws
and washers, and connect the other end to the ground bar of the site,
keeping the grounding wire as short as possible. Ensure that you remove
paint that may interfere with good contact.
2.2 Site Requirements and Prerequisites

It is advisable to install AC-powered units within 1.5m (5 ft) of an
easily-accessible grounded AC outlet capable of furnishing the voltage in
accordance with the nominal supply voltage.
DC-powered units require a -48 VDC power source. Adequately isolate the units
from the main supply.
In order to protect equipment from surges on AC lines that exceed 2000V, install
a suitable surge protection device (SPD) at the AC power service entrance. The
SPD should be an approved component according to local regulations and codes,
and be capable of handling 6000V/3000A surges.
You should ground ETX2 equipment installed in a Central Office (CO) to a
common bonding network. This is the grounding system where all metal parts
and constructional materials of the building and installation are deliberately
bonded together and to the structure’s ground electrodes.
Seek the help of professionals to design the complex grounding system of cell-
sites. A poor grounding system may cause very high voltages between various
types of site equipment, due to ground potential rise.
Note Refer also to the Connecting AC Mains and Connecting DC Power sections in the
Front Matter of this manual.
Allow at least 90 cm (36 in) of frontal clearance for operating and maintenance
accessibility. Allow at least 10 cm (4 in) clearance at the rear of the unit for signal
lines and interface cables.
The following table displays the ambient operating temperature of ETX2
products:
2-2 Site Requirements and Prerequisites ETX2

Installation and Operation Manual Chapter 2 Installation and Setup
Table 2-1. Ambient Operating Temperature
Device Connectors
ETX203AM Regular enclosure: 0 to 50°C (32 to 122°F)

Temperature-hardened enclosure: -20 to 65°C (-4 to 149°F)
ETX203AX Regular enclosure: 0 to 50°C (32 to 122°F)

ETX205A Regular enclosure: 0 to 50°C (32 to 122°F)

ETX220A Regular enclosure: 0 to 50°C (32 to 122°F)

The ambient operating temperature of ETX2 is at a relative humidity of 5% to

90%, non-condensing.
Special Bonding and Grounding Considerations

In addition to the general bonding and grounding instructions given in various
parts of this manual, this section presents procedures that are needed for
network telecommunication equipment that is installed in large
telecommunication centers (central offices) and cell-sites. These requirements
are an integral part of Telcordia GR-1089-CORE®, but are applicable to all such
systems.
The main goals of adequate bonding and grounding are as follows:
• Equalize the potential between several telecommunication units and reduce
voltage differences that might damage the equipment or present safety
hazards.
• Ensure that overcurrent devices such as fuses and circuit breakers operate
properly during a fault.
• Divert as much as possible of unwanted energy from lightning strikes or
transient phenomena on the mains supply to ground, by means of surge and
transient absorbers.
• Improve electromagnetic compatibility.
Use the following methods in order to achieve proper bonding and grounding:
• Connect the mains plug to a socket outlet with a ground connection; this
method protects the user from electrical shock but is not sufficient to
achieve adequate grounding and bonding.
• Connect the ground lug on the front or rear panel of the equipment to a
ground bus bar by means of a short grounding wire (see Safety).
• Install the equipment in an adequately grounded rack by means of the
mounting brackets provided with the equipment, to improve the ground
connection of the ETX2 equipment. To mount ETX2, connect the provided
mounting adapters to ETX2 using star and spring washers. Remove any paint
that may interfere with the connection.
ETX2 Site Requirements and Prerequisites 2-3

• Plan carefully the grounding system for the central office or cell-site.
If a ground lug is provided on the product, connect it to the protective ground at

all times, using a wire of diameter 18 AWG or wider.
Warning
2.3 Package Contents

The ETX2 package includes the following items:
• ETX2 unit
• Matching SFP/XFP module(s) (for relevant ordering option)
• CBL-E1-SPLT to extract two E1/T1 ports from each RJ-45 connector (supplied
with ETX203AM option for network module with eight E1/T1 ports)
• RM-34 rack-mount kit for mounting ETX2 unit with 19” enclosure in a 19"
rack (ETX205A, ETX220A)
• Standard CBL-K21 AC external power cable (per ITU-K.21) – always supplied
with ETX203AX; supplied with other options if AC power supply is ordered
• DC connection kit (supplied if DC power supply was ordered)
• Manual download form
The ETX2 package also includes the following optional accessories, if ordered:
• Cables:
 CBL-RJ45/D9/F/6FT control port cable
 CBL-RJ45/2BNC/E1/X adaptor cable to convert balanced E1 interface
(RJ-45) to unbalanced E1 interface (2 BNC) (if unit has E1/T1 ports or
station clock port)
 CBL-E1-SPLT to extract two E1/T1 ports from each RJ-45 connector of
ETX203AM with eight E1/T1 network module (optional if network module
with eight E1/T1 ports is not ordered)
 Enhanced CBL-K21E AC external power cable (per ITU-K.21 Enhanced
mode)
• Mounting kits:
 RM-33-2 rack-mount kit for mounting one or two ETX203AX units in a
19" rack)
 RM-35 rack-mount kit for mounting one or two ETX203AM units in a
19" rack. RM-35/P1 includes all accessories required for installing one
unit; RM-35/P2 includes all elements accessories required for installing
two units.
 RM-34-23 rack-mount kit for mounting ETX2 unit with 19” enclosure in a
23" rack (ETX205A, ETX220A)
 RM-35/23-TYPE1-NEBS rack-mount kit for mounting one or two NEBS-
compliant units in a 19" rack (ETX203AM, ETX203AX)
2-4 Package Contents ETX2

 WM-34 wall-mount kit for ETX2 unit with 19” enclosure (ETX205A,
ETX220A)
 WM-35 wall-mount kit for ETX203AM unit
• Network interface modules for modular ordering options (ETX203AM)
• AC/DC adapter
• Power supply according to ordering options:
 Single AC power supply: ETX205A, ETX220A
 Single DC power supply: ETX205A, ETX220A
• Lightning arrestor (also called lightning protector (LP)) for ETX205A with
GNSS option
2.4 Required Equipment

Prior to installing the unit, prepare the following, as required:
• Phillips screwdriver to mount the ETX2 unit in a rack or on the wall.
• Standard CBL-K21 AC external power cable (per ITU-K.21) – to connect the
unit to a socket indoors.
• Enhanced CBL-K21E AC external power cable (per ITU-K.21 Enhanced mode)
to connect the unit to a socket in an unprotected power network (such as AC
cell site, AC street cabinet, AC pole, or rural area).
• CBL-E1-SPLT to extract two E1/T1 ports from each RJ-45 connector
(ETX203AM with network module having eight E1/T1 ports)
• CBL-RJ45/D9/F/6FT control port cable
• CBL-RJ45/2BNC/E1/X adaptor cable to convert balanced E1 interface (RJ-45)
to unbalanced E1 interface (2 BNC) (if unit has E1/T1 ports or station clock
port)
• Any other cables required to connect the unit to remote equipment as per
the specific application.
2.5 Mounting the Unit

ETX2 is designed for installation as a desktop unit in horizontal orientation only.
It can also be mounted in a 19" rack, in a small cell cabinet (for specially designed
ETX203AX model only), or on a wall.
ETX2 units (with the exception of ETX203AX model specially designed for
installation in a small cell cabinet) are intended for use in horizontal orientation
Warning only.
In case of vertical mounting orientation, install the unit on top of concrete or
ETX2 Mounting the Unit 2-5

other non-combustible surface, such as an external baffle or tray, due to safety

considerations.
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 (ETX203AX) or the associated installation kit manual (ETX203AM,
ETX205A, ETX220A).
If you are using ETX2 as a desktop unit, place and secure the unit on a stable,
non-movable surface.
See the clearance and temperature requirements in Site Requirements and
Prerequisites.
The following procedure describes how to mount an ETX203AX model specially
designed for installation in a small cell cabinet.
The ETX203AX model specially designed for installation in a small cell cabinet is
restricted for installation in Restricted Access Locations only.
Warning
 To mount the specially designed ETX203AX unit in a small cell cabinet:
1. Remove the bottommost vacant metal tray from the cabinet.
2. Place the ETX203AX unit vertically on the metal tray, with the ventilation
holes facing outward, and leaving at least 1U (44.5 mm; 1.75”) distance
between the unit edges and tray edges.
3. Connect the unit to the metal tray, using 632UNC*8mm length screws.
4. Mount the tray vertically inside the cabinet, making sure to leave at least 10
mm between trays in the cabinet.
2-6 Mounting the Unit ETX2

Upper Side
Openings in the Cover

Toward Open Space
Bottom Side
2.6 Installing the GNSS Antenna

Use of ETX205A with the GNSS ordering option requires installation of a GNSS
antenna on the roof of the building.
Positioning the GNSS Antenna

Damage to an antenna or GNSS receiver is more often due to lightning strikes on
nearby objects, rather than direct strikes on the antenna. These direct or indirect
lightning strikes are likely to induce damaging voltages in the antenna system.
Therefore, it is advisable to place the GNSS antenna below and at least 15 meters
away from towers, lightning rods, or structures that attract lightning.
Mounting the Lightning Arrestor

It is recommended to install a Lightning Arrestor to further protect your GNSS
circuit from lightning strikes. A Lightning Arrestor is able to handle lightning
currents by reducing the pulse energy of the input surge.
ETX2 Installing the GNSS Antenna 2-7

Figure 2-3. GPS In-Line Lightning Arrestor
 To mount the Lightning Arrestor:

1. Mount the Lightning Arrestor on good earth ground (low impedance),
between the GNSS antenna and the point where the cable enters the
building.
2. Connect the GNSS antenna on the roof to the surge side connector at the
top of the Lightning Arrestor using the shortest possible interconnection
cable.
3. Connect the protected side connector at the bottom of the Lightning Arrestor
to the GPS receiver (the device) using a coax cable.
4. If the coax cable length connecting the Lightning Arrestor to the GPS receiver
is no longer than 20 m, no further safety measures are required.
For longer cable distances, a further fine protector may be needed to protect
the receiver against induced voltages caused by magnetic coupling. If this is
the case, contact RAD Technical Support for more information.
Figure 2-4. Mounting GPS In-Line Lightning Arrestor
2-8 Installing the GNSS Antenna ETX2

2.7 Installing SFP/XFP Modules

You can install into an ETX2 Ethernet SFP port, a recognized SFP or XFP
(ETX220A only) module with LC fiber optic connector.
If you insert an unrecognized SFP into an SFP port, even if it is the same speed as
the port, the SFP does not work, but does not raise an alarm or generate a
message.
Third-party SFP/XFP optical transceivers must be agency-approved, complying

with the local laser safety regulations for Class I laser equipment.
Warning
Caution When calculating optical link budget, always take into account adverse effects of
temperature changes, optical power degradation, and so on. To compensate for
signal loss, leave a 3 dB margin. For example, instead of maximum receiver
sensitivity of -28 dBm, consider the sensitivity measured at the Rx side to be
-25 dBm. Information about Rx sensitivity of fiber optic interfaces is available in:
• SFP/XFP Transceivers data sheet for devices using SFPs or XFPs
• Chapter 1 of the installation and operation manual for devices with built-in
fiber optic interfaces
 To install the SFP/XFP modules:

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

2. Carefully remove the dust covers from the SFP/XFP slot.
3. Insert the rear end of the SFP/XFP into the socket, and push slowly
backwards to mate the connectors until the SFP/XFP clicks into place. If you
feel resistance before the connectors are fully mated, retract the SFP/XFP
using the wire latch as a pulling handle, and then repeat the procedure.
ETX2 Installing SFP/XFP Modules 2-9

Caution Insert the SFP/XFP gently. Using force can damage the connecting pins.
4. Remove the protective rubber caps from the SFP/XFP modules.
 To remove the SFP/XFP module:

1. Disconnect the fiber optic cables from the SFP/XFP module.
2. Unlock the wire latch by lowering it downwards (as opposed to locking).
3. Hold the wire latch and pull the SFP/XFP module out of the Ethernet port.
Caution Do not remove the SFP/XFP while the fiber optic cables are still connected. This
may result in physical damage (such as a chipped SFP/XFP module clip or socket),
or cause malfunction (e.g., the network port redundancy switching may be
interrupted).
2.8 Connecting to Power

Regular units are available with AC, DC, or universal AC/DC power supply,
depending on the ordering option. For exact specifications, refer to Technical
Specifications in the Introduction chapter.
Before connecting or disconnecting any cable, you must connect the protective
ground terminals of this unit to the protective ground conductor of the mains (AC
or DC) power cord. If you are using an extension cord (power cable) make sure it
Warning is grounded as well.
Any interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting of the protective ground terminal can make this
unit dangerous. Intentional interruption is prohibited.
Note Refer also to the Connecting AC Mains and Connecting DC Power sections in the
Front Matter of this manual.
Connecting to AC Power
ETX2 units installed indoors require a 1.5m (5 ft) standard CBL-K21 AC external
power cable (per ITU-K.21) terminated by a standard 3-prong socket, to provide
AC power to the unit.
Hardened options of ETX2 units used in an unprotected power network, such as
AC cell site, AC street cabinet, AC pole, or rural area, require an AC Surge
Protection Unit to prevent hardware damage caused by current surges and
voltage spikes. In this unit, a single-phase AC power supply line protector
protects against lightning overvoltage for both common and differential modes.
ETX205A hardened devices have a built-in AC Surge Protection Unit, and
therefore, in unprotected power networks, can use the standard CBL-K21 AC
external power cable (per ITU-K.21) to provide AC power to the unit.
2-10 Connecting to Power ETX2

ETX203AX, ETX203AM, and ETX220A hardened devices do not have a built-in

AC Surge Protection unit, and therefore require an Enhanced CBL-K21E AC
external power cable (per ITU-K.21E).
The following table summarizes K.21E support in the ETX2 family:
Table 2-2. K.21E support in ETX2 family
Device K.21E Support
ETX203AX Enhanced CBL-K21E AC external power cable
ETX203AM Enhanced CBL-K21E AC external power cable
ETX205A No additional support required; has built-in K.21E AC surge

protection unit.
ETX220A Enhanced CBL-K21E AC external power cable
 To connect to AC power:
1. Connect the relevant power cable to the power connector on ETX2.
 For indoor installation – standard CBL-K21 AC power cable
 For connection of hardened units to an unprotected power network:
 For ETX203AX, ETX203AM, and ETX220A – Enhanced CBL-K21E AC
external power cable
 For ETX205A (with built-in AC Surge Protection Unit) – Standard
CBL-K21 AC external power cable
The unit turns on automatically.
Connecting to DC Power
AC/DC plugs or terminal block connectors are available for wiring the DC
connection to the power cable (see AC/DC Adapter (AD) Plug for DC Power Supply
Connection and Terminal Block Connector for DC Power Supply Connection).
All DC options support NEBS level 3 on port type 8b (DC inlet).
 To connect to DC power:
1. Wire the DC connection to the power cable, and connect it to the unit.
See the relevant DC Power Supply Connection section below for instructions
on wiring the DC connection –AC/DC Adapter (AD) Plug for DC Power Supply
Connection or Terminal Block Connector for DC Power Supply Connection.
The unit turns on automatically.
ETX2 Connecting to Power 2-11

AC/DC Adapter (AD) Plug for DC Power Supply Connection

Certain units are equipped with a wide-range AC/DC power supply. These units
are equipped with a standard AC-type 3-prong power input connector located on
the unit rear panel. This power input connector can be used for both AC and DC
voltage inputs.
For DC operation, a compatible straight AC/DC Adapter (AD) (see Figure 2-6) or
90-degree AD plug (see Figure 2-7) for attaching to your DC power supply cable
is supplied with your RAD product.
Figure 2-6. Straight AD Plug
Figure 2-7. 90-Degree AD Plug

The DC power supply cable wiring requirements are as follows:
• Solid or stranded wires
• Wire gauge – AWG 12-18 according to product’s current consumption
Connect the wires of your DC power supply cable to the AD plug, according to the
voltage polarity and assembly instructions provided below.
Caution Prepare all connections to the AD plug before inserting it into the unit’s power
connector.
 To prepare the AD plug and connect it to the DC power supply cable:

1. Loosen the cover screw on the bottom of the AD plug to open it (see figure
below).
2. Run your DC power supply cable through the removable cable guard and
through the open cable clamp.
3. Place each DC wire lead into the appropriate AD plug wire terminal according
to the voltage polarity mapping shown. Afterwards, tighten the terminal
screws closely.
4. Fit the cable guard in its slot and then close the clamp over the cable. Tighten
the clamp screws to secure the cable.
5. Reassemble the two halves of the AD plug and tighten the cover screw.
6. Connect the assembled power supply cable to the unit. After inserting the
plug, verify that the blue (negative) wire is connected to POWER and the
brown (positive) wire is connected to RETURN.

Figure 2-8. AD Plug Details
• Reversing the wire voltage polarity will not cause damage to the unit, but the
internal protection fuse will not function.
Warning • Always connect a ground wire to the AD plug’s chassis (frame) ground
terminal. Connecting the unit without a protective ground, or interrupting the
grounding (for example, by using an extension power cord without a
grounding conductor) can damage the unit or the equipment connected to it!
• The AD adapter is not intended for field wiring.
Terminal Block Connector for DC Power Supply Connection

Certain DC-powered units are equipped with a plastic 3-pin VDC-IN power input
connector, located on the unit rear panel. Different variations of the connector
are shown in Figure 2-9. All are functionally identical.
Figure 2-9. TB DC Input Connector Types Appearing on Unit Panels

Supplied with such units is a kit including a mating Terminal Block (TB) type
connector plug for attaching to your power supply cable.

The DC power supply cable wiring requirements are as follows:

• Solid or stranded wires
• Wire gauge – AWG 12-18 according to product’s current consumption
Connect the wires of your power supply cable to the TB plug, according to the
voltage polarity and assembly instructions provided on the following pages.
Caution Prepare all connections to the TB plug before inserting it into the unit’s VDC-IN
connector.
 To prepare and connect the power supply cable with the TB Plug:
Note See Figure 2-10 for assistance.
1. Strip the insulation of your power supply wires according to the dimensions
shown.
2. Place each wire lead into the appropriate TB plug terminal according to the
voltage polarity mapping shown in Figure 2-11. (If a terminal is not already
open, loosen its screw.) Afterwards, tighten the three terminal screws to
close them.
3. Pull a nylon cable tie (supplied) around the power supply cable to secure it
firmly to the TB plug grip, passing the tie through the holes on the grip.
4. Isolate the exposed terminal screws/wire leads using a plastic sleeve or
insulating tape to avoid a short-circuit.
5. Connect the assembled power supply cable to the unit by inserting the
TB plug into the unit’s VDC-IN connector until it snaps into place.
Figure 2-10. TB Plug Assembly

Figure 2-11. Mapping of the Power Supply Wire Leads to the TB Plug Terminals
• Reversing the wire voltage polarity can cause damage to the unit!
• Always connect a ground wire to the TB plug’s chassis (frame) ground
Warning terminal. Connecting the unit without a protective ground, or interruption of
the grounding (for example, by using an extension power cord without a
grounding conductor) can cause harm to the unit or to the equipment
connected to it, and can be a safety hazard to personnel operating it!
Note Certain TB plugs are equipped with captive screws for securing the assembled
cable’s TB plug to the unit’s VDC-IN connector (C and E types only). To secure the
plug, tighten the two screws on the plug into the corresponding holes on the
sides of the input connector as shown in Figure 2-12.
Figure 2-12. TB Plug with Captive Screws (optional)
 To disconnect the TB plug:

1. If the TB plug is equipped with captive screws, loosen the captive screws
(see Figure 2-12).
2. If the unit’s VDC-IN connector is type B, lift the locking latch
(see Figure 2-9).
3. Pull out the TB plug carefully.

Caution Always lift the locking latch of type B connectors before disconnecting the
TB plug, to avoid damaging the TB plug.
2.9 Connecting to Ethernet Equipment

You can connect ETX2 to Ethernet equipment via the connectors described in
the following table, according to the relevant option:
Table 2-3. Device Connectors
Device Connectors
ETX203AM Network port with GbE option:

• Fiber optic LC (combo port)
• 8-pin RJ-45 electrical port (combo port)
User port:
• Fiber optic LC port
• 8-pin RJ-45 electrical port
ETX203AX • Fiber optic LC designated ETH

• 8-pin RJ-45 electrical port designated ETH
ETX205A • Fiber optic LC (combo port)

• 8-pin RJ 45 electrical port (combo port)
ETX220A • Fiber optic LC connector designated 10GbE/1000Fx

• 8-pin RJ-45 electrical port designated 10/100/1000BT
The instructions below are illustrated with sample configurations.
 To connect to the Ethernet equipment with fiber optic interface:

• Connect ETX2 to the Ethernet equipment using a standard fiber optic cable
terminated with an LC connector.
Note Use shielded cables when connecting to the Ethernet ports.
Figure 2-13. GbE Fiber Optic Connectors – ETX203AM
2-16 Connecting to Ethernet Equipment ETX2

Figure 2-14. GbE Fiber Optic Connectors – ETX203AX
GbE/100Fx E1/T1
EXT CLK TOD/1PPS EXT CLK 1 2 3 4
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
1 LINK/ACT 2 3 4 5 6 LOC REM POWER POWER
PWR
DCE LINK ACT PS1 ~100-240VAC ~100-240VAC PS2
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-15. GbE Fiber Optic Connectors – ETX205A
Figure 2-16. 10GbE Fiber Optic Connectors – ETX220A
 To connect to the Ethernet equipment with a copper interface:

• Connect ETX2 to the Ethernet network equipment using a standard straight
STP cable terminated with an RJ-45 connector. Refer to the Connection Data
appendix for the RJ-45 connector pinout.
The following applies to all intra-building Ethernet ports with a copper interface
(RJ-45) that are indicated in Figures 2-17 through Figure 2-20:
Warning • The ports are suitable for connection to intra-building or unexposed wiring or
cabling only. The intra-building port(s) of the equipment or subassembly MUST
NOT be metallically connected to interfaces that connect to the OSP or its
wiring. These interfaces are designed for use as intra-building interfaces only
(Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation
from the exposed OSP cabling. The addition of primary protectors is not
sufficient protection in order to connect these interfaces metallically to OSP
wiring.
• The ports must use shielded intra-building cabling/wiring that is grounded at
both ends. The ground connection must be stable and with low impedance, in
order to ensure that surge currents, which can develop due to ground
potential rise, do not cause very high voltages to develop on the ETH isolation
transformer.
Note In order to comply with electromagnetic compatibility requirements, it is

recommended to use Category 6E shielded twisted pairs (STP) cables.
ETX2 Connecting to Ethernet Equipment 2-17

Figures 2-17. Ethernet Electrical Connectors – ETX203AM
Figure 2-18. Ethernet Electrical Connectors – ETX203AX

GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-19. Ethernet Electrical Connectors – ETX205A
Figure 2-20. Ethernet Electrical Connectors – ETX220A
2.10 Connecting to SHDSL Equipment
Note This section is relevant for ETX203AM with SHDSL network module, and for
ETX203AX with embedded eight-wire SHDSL uplink.
You can connect ETX2 to SHDSL equipment via one or two RJ-45 connectors
designated SHDSL; one RJ-45 connector for the 4-wire option and two RJ-45
connectors for the 8-wire option.
2-18 Connecting to SHDSL Equipment ETX2

Figure 2-21. SHDSL Connectors – ETX203AM (eight-wire ordering option)
Figure 2-22. ETX203AX with SHDSL (eight-wire) Front Panel
 To connect to SHDSL equipment:

• Connect the device’s SHDSL ports to SHDSL equipment using standard
straight UTP cables (one for the 4-wire option and two for the 8-wire option)
terminated with RJ-45 connectors. Refer to the Connection Data appendix for
the RJ-45 connector pinout.
Note Use unshielded cables when connecting to SHDSL ports.
2.11 Connecting to VDSL Equipment

Note This section is relevant only for ETX203AM with VDSL network module.
You can connect ETX203AM to VDSL equipment via the two RJ-45 (UTP)
connectors designated VDSL.
Figure 2-23. VDSL Connectors – ETX203AM
 To connect to VDSL equipment:

• Connect ETX203AM to the VDSL equipment using standard straight UTP
cables terminated with RJ-45 connectors. Refer to the Connection Data
ETX2 Connecting to VDSL Equipment 2-19

Note Use unshielded cables when connecting to the VDSL ports.
2.12 Connecting to E1/T1 Equipment
Note This section is relevant only for the following:

• ETX203AM with E1/T1 network module
• ETX205A with built-in E1/T1 ports
ETX203 AX with a built-in E1 port
If you ordered ETX2 with E1/T1 network ports, you can connect ETX2 to E1/T1
equipment via the RJ-45 connectors designated E1/T1.
Note • You must configure the module with the correct module type (ETX203AM
only).
• Configure the E1/T1 ports as E1 or T1 ports.
Refer to the Cards and Ports chapter for details on configuring the module type
or E1/T1 ports.
 To connect to E1 or T1 equipment:
• Connect an E1 or T1 line to the RJ-45 connector designated E1/T1 (1–4/8).
Refer to the Connection Data appendix for the RJ-45 connector pinout.
Note • If the network module has eight E1/T1 ports, use the cable CBL-E1-SPLT
(ETX203AM only).
• For unbalanced E1 connections, use the adaptor cable CBL-RJ45/2BNC/E1/X
(ETX205A only).
Figure 2-24. E1/T1 Ports – ETX203AM
Figure 2-25. E1 Port - ETX203AX (1 E1, 3 SFP, and 2 UTP)
2-20 Connecting to E1/T1 Equipment ETX2

GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-26. E1/T1 Ports – ETX205A
2.13 Connecting to T3 Equipment
Note This section is relevant only for ETX203AM with T3 network module.
You can connect ETX203AMto T3 equipment via the BNC coaxial connectors on
the network module.
Note You must configure the module with the correct module type. Refer to the Cards
and Ports chapter for details.
 To connect to T3 equipment:
1. Connect the Rx cable to the BNC connector labeled Rx.
2. Connect the Tx cable to the BNC connector labeled Tx.
Figure 2-27. T3 Ports – ETX203AM
2.14 Connecting to Station Clock
Note This section is relevant only for ETX205A or ETX220A ordered with a timing
option that includes a station clock port.
You can connect ETX2 to an external clock source via a dedicated station clock
port, an RJ-45 connector designated EXT-CLK. Refer to the Connection Data
appendix for the connector pinout.
ETX2 Connecting to Station Clock 2-21

GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-28. EXT-CLK Connector – ETX205A
Figure 2-29. EXT-CLK Connector – ETX220A

You can connect the station clock port to a balanced or unbalanced clock source.
Make sure that you configure the station clock interface type accordingly (refer
to the Timing and Synchronization chapter for details on configuring the station
clock).
Note The cable length between the station clock port and the external clock source
must not exceed six meters (19.7 feet).
Connecting to a Balanced Clock Source
 To connect ETX2 to a balanced clock source:

• Connect the station clock port to the clock source using a shielded standard
UTP cable terminated with an RJ-45 connector. Refer to the Connection Data
Connecting to an Unbalanced Clock Source

Connecting to equipment with an unbalanced interface requires you to convert
the RJ-45 connector to a pair of BNC female connectors, in order to receive the
clock signal via one of the connectors and transmit the signal via the other.
RAD offers a suitable adapter cable, CBL-RJ45/2BNC/E1/X, with an RJ-45
connector at one end and two BNC female connectors at the other end. For this
particular cable, the receiving BNC connector is green and the transmitting BNC
connector is red.
 To connect ETX2 to an unbalanced clock source:

1. Connect the RJ-45 connector of the adapter cable to the station clock port.
2. Connect the external clock source to the receiving BNC connector of the
adapter cable.
3. Connect the transmitting BNC connector of the adapter cable to the
equipment that should receive the clock signal.
2-22 Connecting to Station Clock ETX2

2.15 Connecting to Synchronization Equipment
Note This section is relevant only for ETX205A or ETX220A ordered with a timing
option that includes the EXT-CLK/1PPS ports and/or the ToD/1PPS port.
ETX2 can transmit a 1PPS signal for synchronization, as well as connect to an

external clock, via two mini BNC connectors designated EXT-CLK and 1PPS.
Alternatively, the device can transmit a ToD (Time of Day) and 1PPS signal for
synchronization, via an RS-422 RJ-45 connector designated ToD/1PPS. Refer to
the Connection Data appendix for the ToD/1PPS connector pinout.
Note The cable length between the ToD/PPS and EXT CLK/1PPS ports, and the external
synchronization equipment, must not exceed six meters (19.7 feet).
 To connect to EXT-CLK and 1PPS:

• Connect ETX2 to the synchronization equipment using standard BNC cables
terminated with BNC connectors.
 To connect to ToD/1PPS:
• Connect ETX2 to the synchronization equipment using a proprietary RAD
RS-422 cable terminated with a male RS-422 RJ-45 connector.
GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-30. EXT-CLK and 1PPS Connectors – ETX205A
Figure 2-31. EXT-CLK and 1PPS Connectors – ETX220A
GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-32. ToD/1PPS Connector – ETX205A
Figure 2-33. ToD/1PPS Connector – ETX220A
ETX2 Connecting to Synchronization Equipment 2-23

2.16 Connecting to a Terminal

You can connect ETX2 to a laptop equipped with an ASCII terminal emulation
application, such as PuTTY, via an 8-pin RJ-45 connector designated CONTROL.
Refer to the Connection Data appendix for the connector pinout.
Caution Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to the supervisory
terminal port.
 To connect to an ASCII terminal:

1. Connect the RJ-45 connector of CBL-RJ45/D9/F/6FT cable, available from RAD,
to the CONTROL connector.
2. Connect the other end of the CBL-RJ45/D9/F/6FT cable to a computer
equipped with an ASCII terminal emulation application.
Note
After completing the configuration of the terminal, disconnect the terminal and
leave the CONTROL port open.
Figure 2-34. CONTROL Connector – ETX203AM
Figure 2-35. CONTROL Connector – ETX203AX

GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-36. CONTROL Connector – ETX205A
2-24 Connecting to a Terminal ETX2

Figure 2-37. CONTROL Connector – ETX220A
2.17 Connecting to a Network Management Station

You can connect ETX2 to a remote network management station via the
dedicated Ethernet management port, an 8-pin RJ-45 connector designated
MNG-ETH. Refer to the Connection Data appendix for the connector pinout.
 To connect to an NMS:
• Connect ETX2 to an Ethernet switch.
Note
After completing the configuration of the Ethernet switch, disconnect the switch
and leave the MNG-ETH port open.
Figure 2-38: Ethernet Management Connector – ETX203AM
Figure 2-39: Ethernet Management Connector – ETX203AX

GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 2-40: Ethernet Management Connector – ETX205A
Figure 2-41: Ethernet Management Connector – ETX220A
ETX2 Connecting to a Network Management Station 2-25

2.18 Basic Connectivity Tests
Caution Before leaving the installation site, it is highly recommended that you test
network connectivity between the device and the remote network management
station (for example, by sending a ping).
2-26 Basic Connectivity Tests ETX2

Chapter 3
Operation and
Maintenance
3.1 Turning On the Unit

 To turn on ETX2:
• Connect the power cord to the mains.
The PWR indicator lights up and remains lit as long as ETX2 receives
power.
The enclosure of the specially designed ETX203AX unit installed in a small cell
cabinet can become very hot. Do not touch! Contact may cause burn.
Warning
ETX2 requires no operator attention once installed, with the exception of
occasional monitoring of front panel indicators. Intervention is only required
when ETX2 must be configured to its operational requirements, or diagnostic
tests are performed.
3.2 Indicators
The ETX2 unit’s LED indicators are located on the device’s front panel. These
LEDs enable the user to quickly observe the state of the device. Each LED has a
default “normal” functionality (see LED Behavior below).
You can also configure the TST/ALM or TST/ALM/PWR LED for LED signaling,
instead of its normal function (see LED Signaling below).
LED Behavior
The following tables summarize the normal functions of the ETX2 LED indicators
per device.
ETX2 Indicators 3-1

Chapter 3 Operation and Maintenance Installation and Operation Manual
ETX203AM
Figure 3-1. ETX203AM Front Panel (GbE option)
Table 3-1. ETX203AM Front Panel Controls and Indicators
Name Color State
LINK/ACT Green ON – Management Ethernet link is synchronized.

MNG-ETH Blinking – Data is being transmitted or received on the management
Ethernet link.
Network ports Red ON – Local synchronization loss (LOS, LOF, or AIS occurred)
(E1/T1 option): OFF –No local synchronization alarm
LOC
Network ports Green ON – Corresponding Ethernet link is synchronized.
(GbE option): Blinking – Data is being transmitted or received on the corresponding
LINK/ACT Ethernet link.
Network ports Green/red ON (green) – SHDSL line is synchronized.
(SHDSL option): ON (red) – SHDSL line is not synchronized.
SHDSL SYNC Blinking (red/green): SHDSL line is activating, after exchanging connection
parameters (handshaking) with remote side.
Network ports Yellow ON – AIS (Alarm Indication Signal) occurred.
(T3 option): OFF – No AIS alarm
AIS
Network ports Red ON – Local synchronization loss (LOS)
(T3 option): OFF – No local synchronization alarm
LOS
PWR/TST/ALM Green/Red ON (green) – Power is ON.
ON (red) – There is at least one active alarm.
Blinking – Diagnostic loopback is active.
USER Green ON – Corresponding Ethernet link is synchronized.
3,4,5,6 Blinking – Data is being transmitted or received on the corresponding
Ethernet link.
3-2 Indicators ETX2

Installation and Operation Manual Chapter 3 Operation and Maintenance
ETX203AX
Figure 3-2. ETX203AX Front Panel
Figure 3-3. ETX203AX-E1 Front Panel
Figure 3-4. ETX203AX-DSL Front Panel
Figure 3-5. ETX203AX Hardened Option Front Panel
Table 3-2. ETX203AX Front Panel Controls and Indicators
N ame Color State
CONTROL Green ON – Device is connected to terminal.

Blinking – Data is being connected to terminal.
E1 Red ON – E1 LOS (Loss of Signal)
Ethernet link.
ETX2 Indicators 3-3

N ame Color State
NET 1 Green ON – Corresponding Ethernet link is synchronized.

Blinking – Data is being transmitted or received on the corresponding
Ethernet link.
Not relevant for ETX203AX with E1 EoPDH device.
NET/USER 2 Green ON – Corresponding Ethernet link is synchronized.
Blinking – Data is being transmitted or received on the corresponding
Ethernet link.
SHDSL 1, 2, 3, 4 Green/Red ON (green) – SHDSL line is synchronized.
ON (red) – SHDSL line is not synchronized.
Blinking – SHDSL line is activating, after exchanging connection parameters
(handshaking) with remote side.
TST/ALM/PWR Green/Red ON (green) – Power is ON.
ON (red) – There is at least one active alarm.
USER n Green ON – Corresponding Ethernet link is synchronized.
(1,2,3,4,5) Blinking – Data is being transmitted or received on the corresponding
Ethernet link.
ETX205A
GbE/100Fx E1/T1
LASER
NET NET-USER USER
ETX-205A
CLASS
1
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
10/100/1000BT LOC 5 6 7 8 REM
Figure 3-6. ETX205A Front Panel
Table 3-3. ETX205A Front Panel Controls and Indicators
Name Color State
LINK/ACT Green ON – Corresponding Ethernet link is synchronized.

1–6 Blinking – Data is being transmitted or received on the corresponding
Ethernet link.
Ethernet link.
LOC (E1/T1 ports) Red ON – Local synchronization loss (LOS, LOF, or AIS occurred)
1–8 OFF – No local synchronization alarm
POWER Green/Red ON (green) – This power supply is connected to power and output voltage
is okay.
ON (red) – This power supply is not connected to power or output voltage
failed (in case of dual power supply with redundancy mode).
PWR Green ON – Power is ON.
OFF – Power is OFF.
3-4 Indicators ETX2

Name Color State
REM Red ON – Remote synchronization loss (RDI)

(E1/T1 ports) OFF – No remote synchronization alarm
1–8
SD Green ON – Station clock port is connected.
EXT-CLK
TST/ALM Red ON – There is at least one active alarm.
ETX220A
Figure 3-7. ETX220A Front Panel
Table 3-4. ETX220A Front Panel Controls and Indicators
Name Color State
ACT Yellow ON – Data is being transmitted/received at the GbE Ethernet link.

1/1-1/10
2/1-2/10
ACT Yellow ON – Data is being transmitted/received at the 10GbE Ethernet link.

3/1, 3/2, 4/1, 4/2
LINK Green ON – GbE Ethernet interface is synchronized.

1/1-1/10
2/1-2/10
LINK Green ON – 10GbE Ethernet interface is synchronized.

3/1, 3/2, 4/1, 4/2

Ethernet link.
POWER Green/Red ON (green) – This power supply is connected to power and output voltage
is okay.
ON (red) – This power supply is not connected to power or output voltage
failed (in case of dual power supply with redundancy mode).
PWR Green ON – Power is ON.
OFF – Power is OFF.
SD Green ON – Station clock port is connected.
EXT-CLK
TST/ALM Red ON – There is at least one active alarm.
ETX2 Indicators 3-5

LED Signaling
ETX2 supports LED signaling (blinking) using the following LEDS:
• TST/ALM/ – on ETX205A and ETX220A
• TST/ALM/PWR – on ETX203AM and ETX203AX
LED signaling is typically activated from the NOC to pass information to a
technician on the field, by blinking the device LED in agreed patterns. For
example, if the technician is not sure which device to reset in a rack, someone at
the NOC can point to it by blinking its LED.
You can configure the led-blink command to set the color, pattern, and duration
of a LED signal that is activated (see configuration details in the table below).
While this command is active, it overrides normal LED behavior. Once you cancel
an active command (by entering the no led-blink command or rebooting the
device), the LED behavior returns to normal.
Configuring LED Signaling

 To configure LED signaling:
1. Navigate to configure reporting.
2. At the prompt, enter all necessary commands according to the tasks listed
below.
3-6 Indicators ETX2

Task Command Comments
Configuring LED blinking pattern led-blink <color> on <on-milliseconds> off color – LED color
<off-milliseconds> [forever | duration Possible values: red, green, yellow
<seconds>] (provided the device has these colors)
no led-blink on-milliseconds – time the LED is on
Possible values: 100-10000
off-milliseconds – time the LED is off
seconds – total time of LED blinking
Notes:
• The number of milliseconds (off or
on) must be a multiple of 100ms. If
you configure a different number,
the device rounds it up to the
nearest valid value and prints: Note:
On-time/Off-time was rounded up to
the nearest multiple of 100 not
above 10000.
• This command is not saved in the
configuration and cannot be
executed from a configuration file.
• If this command is repeated while a
previous one is active, it replaces the
previous one.
• Entering no led-blink cancels an
active command (if one exists), stops
the blinking, and returns the LED
behavior to normal.
• When the blinking is finished, the
device disables LED signaling.
Displaying the LED blinking status show led-blink-status For detailed information on the LED
blinking status report parameters, see
Viewing LED Blinking Status.
Viewing LED Blinking Status

 To display LED blinking status:
• Navigate to configure reporting show led-blink-status.
A status report is displayed.
LED Blinking Status : On
Remaining Time (Seconds) : 147
LED Color : Green

On Time (Milliseconds) : 100
Off Time (Milliseconds) : 100
Blinking Duration (Seconds): 200
ETX2 Indicators 3-7

Note If LED Blinking Status is Off, only the first row of the report is displayed.
Table 3-5. LED Blinking Status Parameters
Parameter Description
LED Blinking Status LED blink status

Possible values: On, Off
Remaining Time (Seconds) LED blinking remaining time

Possible values: Forever, number
Note: Only displayed if Blinking Duration has been
configured.
LED Color Possible values: Green, Red, Yellow
On Time (Milliseconds) LED blink on time (in milliseconds)
Off Time (Milliseconds) LED blink off time (in milliseconds)
Blinking Duration (Seconds) LED blinking remaining time

Possible values: Forever, number
3.3 Startup
Applicable Products
All configuration and software files, as well as the loading sequence, are
applicable to all ETX2 products and to PMC in ETX205A.
Configuration and Software Files

Software files are named sw-pack-1 through sw-pack-4. One of the software
packs is designated as active.
Note Although the CLI allows sw-pack-1 through sw-pack-4, you can define only two
SW packs simultaneously.
The following files contain configuration settings:

• factory-default-config – contains the manufacturer default settings. At
startup, factory-default-config is loaded if startup-config, rollback-config, and
user-default-config are missing or invalid.
• 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.
• restore-point-config – created by ETX2 when software is installed with
restore point option. Refer to the Software Upgrade chapter for more details.
• running-config – contains the current configuration that the device is
running. This file is deleted and rebuilt at device reboot.
3-8 Startup ETX2

• 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 default user configuration. This file is not
automatically created. You can use the copy command to create it. At
startup, user-default-config is loaded if startup-config and rollback-config,
are missing or invalid.
Note Configuration files should contain only printable ASCII characters (0x20–0x7E),
<Enter> (0x0D), <Line Feed> (0x0A), and <Tab> (0x09).
Refer to File Operations in the Administration chapter 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
• 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, to either stop loading the file when the first error is
encountered, or reject the file and reboot; after rebooting, the next file in the
loading sequence is loaded).
To display the parameter values after startup, use the info [detail] command.
3.4 Working with Custom Configuration Files

In large deployments, often a central network administrator sends configuration
files to remote locations and all that remains for the local technician to do is
replace the IP address in the file or other similar minor changes, and then
download the file to the device. Alternatively, the technician can download the
file as is to the device, log in to the device and make the required changes, and
then save the configuration.
You download the configuration file using the copy command (refer to the
Administration chapter), and then reset the unit in order to execute the file. After
the unit completes its startup, the custom configuration is complete.
To ease deployment of large numbers of devices, you can automatically distribute
software and configuration files in the following ways:
ETX2 Working with Custom Configuration Files 3-9

• Use On-Net Zero Touch provisioning (ZTP) to enable units to automatically

receive an IP address, and software and configuration files (see On-Net Zero
Touch for details).
• Use PPPoE (Point-to-Point Protocol over Ethernet) to establish a management
channel through which an IP address can be acquired (refer to Point-to-Point
Protocol over Ethernet (PPPoE) in the Management and Security chapter, for
details). For instance, the IP address can be acquired from a broadband
remote access server (BRAS). The BRAS then notifies a Radius server, which
in turn reports to a management system, such as RADview, that a new device
is up. The management system then sends software and configuration files
to the device.
Applicable Products
These file operations are applicable to all ETX2 products.
PMC in ETX205A supports saving configuration changes; however, it does not
support Zero Touch.
Saving Configuration Changes

You must save your configuration if you wish to have it available, as it is not
saved automatically.
Save your configuration as follows:
• Use the save command to save running-config as startup-config.
• Use the copy command to copy running-config to startup-config or
user-default-config.
Additionally, some commands erase the configuration saved in startup-config by
copying another file to it and then resetting the device. The following figure
indicates the commands that copy to startup-config, and whether the device
resets after copying.
Figure 3-8. Commands That Reset Device/Copy Configuration Files
 To save the user configuration in startup-config:

1. In any level, enter: save.
3-10 Working with Custom Configuration Files ETX2

2. At the file# prompt, enter: copy running-config startup-config.
 To save the user default configuration in user-default-config:

• At the file# prompt, enter: copy running-config user-default-config.
Confirming Startup Configuration

You can request that startup-config be confirmed after the next reboot. When
you execute the request, the next time the device reboots, if startup-config is
loaded successfully, you must confirm startup-config within the configured
timeout period. If the confirmation is not received before timeout, the device
rejects startup-config, reboots, and attempts to load the next available
configuration file (rollback-config, user-default-config, factory-default-config).
 To request confirmation of startup-config after next reboot;

• At the admin# prompt enter:
startup-confirm-required [time-to-confirm <minutes>] [rollback
{startup-config | user-default-config | factory-default-config |
running-config}]
The <minutes> parameter defines the confirmation timeout, range 1–65535
(default 5). If rollback <config-file> is specified, the specified configuration
file is copied to rollback-config.
 To confirm confirmation of startup-config after reboot;

• In any level, enter:
startup-config-confirm
On-Net Zero Touch

The Zero Touch feature allows ETX2 to receive software and configuration files
automatically, eliminating the need to manually log into ETX2 in order to transfer
the required files to it.
The following Zero Touch mechanisms enable automatic provisioning of ETX2:
• Zero Touch via DHCP – ETX2 retrieves configuration information from the
DHCP server (see Zero Touch via DHCP/DHCPv6).
• Zero Touch via DHCPv6 – ETX2 retrieves configuration information from the
DHCPv6 server (see Zero Touch via DHCP/DHCPv6).
• Zero Touch via trap – ETX2 sends a notification trap to a management
system, such as RADview, so that the management system can perform the
appropriate provisioning (see Zero Touch via Trap).
Benefits
Zero Touch Provisioning (ZTP) allows a fully automated device field installation
with a minimal and set device initial configuration. ZTP automates tasks typically
performed by system and network managers, enabling you to install or upgrade

many devices automatically, instead of logging into each device, transferring

software and configuration files to it, and then resetting each device.
Functional Description
Show Me Demo
The video below describes Zero Touch via DHCP.
 To view the video:

• Click to play.
Note If you cannot view the video, ensure that you have the latest version of Adobe
Reader.
Zero Touch via DHCP/DHCPv6

The following describes the sequence of Zero Touch Provisioning via DHCP (for
IPv4) or DHCPv6 (for IPv6):
1. At reboot, ETX2 initiates a DHCP session and obtains a DHCP lease from the
DHCP server and/or a DHCPv6 lease from the DHCPv6 server. If ETX2 receives
more than one lease that contains ZTP directives (from multiple interfaces), it
processes them one by one. After the first one is finished, either successfully
or not (e.g. reaching a timeout during file download), the device proceeds
with the directives received in the second lease.
2. For DHCP: The lease provides the device IP address (for device management),
TFTP server IP address, either via option 150, or as a string via option 66 (the
string is interpreted as an IP address rather than a device name). Option 66 is
valid only if the string is formatted as (‘xxx.xxx.xxx.xxx’). Optionally, the DHCP
lease provides the path and/or the file name of the ZTP file via DHCP
option 67.
3. For DHCPv6: The lease provides the device IP address (for device
management), TFTP server address via CableLabs vendor-specific (17) sub-
option 32, provided that ETX2 supports it. If multiple TFTP server addresses
are received, only the first one is used. Optionally, the DHCPv6 lease provides
the path and/or the file name of the ZTP file via DHCPv6 sub-option 33.
4. If a valid TFTP server address is not obtained, the ZTP process finishes
unsuccessfully.

5. ETX2 downloads the ZTP file from the TFTP server according to the
information received in the lease. If not specified in the lease, the default
path is rad/, and the default file name is rad.xml.
6. If the ZTP file is loaded successfully, ETX2 sends the event download_end
(with success indication) to all configured network managers, and saves the
ZTP file as zero-touch-config-xml.
7. If zero-touch-config-xml contains directives for a software file, ETX2 does
one of the following, according to the action specified in the directives:
 upgrade-only – loads software file if it is newer than the active software
image
 downgrade-only – loads software file if it is older than the active
software image
 replace – loads software file if different from the active software image
8. If zero-touch-config-xml contains directives for a configuration file, then if
the action specified in the directives is replace-cfg, ETX2 loads the specified
configuration file if it is different than the last configuration file loaded via
the ZTP mechanism, and saves it as specified by cfg-dst-file.
9. If a software file was downloaded, ETX2 installs it as the active software
pack.
10. If a software file and/or configuration file was downloaded, ETX2 reboots.
After startup, the normal startup loading sequence is performed, so that if
startup-config is loaded in the sequence, ETX2 executes the CLI commands
in the file.
11. If no reboot was needed, ETX2 performs the normal startup loading
sequence.
If an error occurs during the ZTP process, ETX2 does the following:
• Sends the event download_end (with failed indication) to all configured
network managers
• Starts a 10-minute timer
• Performs the normal startup loading sequence
• When the timer expires, ETX2 again attempts the ZTP process.
Zero Touch via Trap

You can specify that ETX2 send a trap periodically to the management system
(e.g. RADview) to notify it of its existence in the network (by default, this trap is
not sent).
In this method, all the devices are preloaded with a minimal user configuration
file, containing just enough configuration to allow them to connect to a
management system. The management system, upon receiving such a trap,
accesses the device with SNMP (or other means), completes its provisioning, and
disables further sending of the trap.

Configuring On-Net Zero Touch Provisioning Via DHCP
Prerequisites
• A Zero Touch Provisioning (ZTP) XML file, containing directives for the
software and configuration files. See Preparing the Zero Touch XML File for
details on the file structure.
• A DHCP or DHCPv6 server for providing the TFTP server address, in addition to
regular device IP address allocation (for management), default gateway, etc.
The DHCP server should support the following options:
 Option 67 – ZTP XML file name
 Option 150 – TFTP server address (option 66 may substitute option 150,
with the IP address expressed as a string formatted xxx.xxx.xxx.xxx)
The DHCPv6 server should support the following options:
 Option 17, sub-option 32 – TFTP server IP address
 Option 17, sub-option 33 – ZTP XML path and/or file name
• A TFTP server from which to download the following:
 ZTP XML file
 Software image file, if required by the directives
 Configuration file, if required by the directives
• A preliminary configuration file in the device, which includes a Router
Interface (possibly configured over a known management VLAN) with
DHCP/DHCPv6 enabled.
Perform the following steps to ensure that on-net ZTP is performed on your
device when software or configuration files are changed:
1. Prepare the Zero Touch XML file with software and configuration file
directives.
2. Set up your DHCP or DHCPv6 server.
3. Place the software, configuration, and ZTP XML files in your TFTP server
directory.
4. Configure ETX2 for management access and enable as DHCP/DHCPv6 client.
Preparing the Zero Touch XML File

This section describes the ZTP directives in the ZTP file, which is written in
standard XML, based on the NETCONF schema. The file contains directives for
one or more types of devices. ZTP File Example below shows a ZTP file containing
directives for three device types: ETX-100, ETX-200, and ETX-300.
The directives are enclosed in the element pair <zero-touch-configuration>
</zero-touch-configuration>. The ZTP directives for a particular device are
enclosed by an element pair such as <ETX-100></ETX-100>. The element
contents are according to the chassis name in the inventory display (refer to
Inventory in the Administration chapter). The file can contain software-related
directives and/or configuration-related directives for each device.

Software Directives
The following directives supply information about the software file to download:
• sw-version – version of the software to download; must be formatted in the
same way as the chassis software revision displayed in the inventory display
(refer to Inventory in the Administration chapter).
• sw-action – software action to perform:
 upgrade-only – Load software file if sw-version specifies a newer version
than the chassis software revision.
 downgrade-only – Load software file if sw-version specifies an older
version than the chassis software revision.
 replace – Load software file if sw-version specifies a version that is
different from the chassis software revision.
• sw-src-file – path and name of the software to download (must match the
file name in the TFTP server directory)
• sw-dst-file – file name for saving the downloaded software :
 sw-pack-<n> – File is saved as the specified name, if it is not the active
software.
 auto – File is saved as follows:
 If there is an unused software pack number, and there is enough
space in the file system, then the file is saved as sw-pack-<n>, where
<n> is the smallest unused software pack number.
 If all software packs numbers are in use, or if there is not enough
space to save the software, then the file is saved as sw-pack-<n>,
where <n> is the software pack number of the oldest version.
Configuration Directives
The following directives supply information about the configuration file to
download:
• cfg-version – version of configuration to download
• cfg-action – action to take regarding configuration:
 replace-cfg – loads configuration file if cfg-version is different than the
last ZTP configuration version.
• cfg-src-file – path and name of the configuration file to download (must
match the file name in the TFTP server directory)
• cfg-dst-file – specifies the name under which to save the downloaded
configuration file; must contain startup-config
ZTP File Example

The file shown below specifies the following:

• ETX-100:
 If version 4.3.30.10 is newer or older than the active software version,
download /rad/etx/etx100.sw and save it as specified for the auto option
in Software Directives.
 If the last downloaded ZTP configuration version was not etx100 4.3.20,
download /rad/etx/etx100.cfg and save it as startup-config.
• ETX-200:
 If version 4.3.50 is newer than the active software version, download
/rad/etx/etx200.sw and save it as specified for the auto option in
Software Directives.
• ETX-300:
 If version 4.3.10 is older than the active software version, download
/rad/etx/etx300.sw and save it as specified for the auto option in
Software Directives.
<rpc message-id="1"
xsi:schemaLocation="urn:ietf:params:xml:ns:netconf:base:1.0
netconf.xsd http://www.rad.com/schema/zero-touch-
configuration/1.0 ztc_netconf.xsd">
<edit-config>
<target>
<running/>
</target>
<config>
<zero-touch-configuration>
<ETX-100>
<sw-version>4.3.30.10</sw-version>
<sw-action>replace</sw-action>
<sw-src-file>/rad/etx/etx100.sw</sw-src-file>
<sw-dst-file>auto</sw-dst-file>
<cfg-version>etx100 4.3.20</cfg-version>
<cfg-action>replace-cfg</cfg-action>
<cfg-src-file>/rad/etx/etx100.cfg</cfg-src-file>
<cfg-dst-file>startup-config</cfg-dst-file>
</ETX-100>
<ETX-200>
<sw-version>4.3.50</sw-version>
<sw-action>upgrade-only</sw-action>
</ETX-200>
<ETX-300>
<sw-version>4.3.10</sw-version>

<sw-action>downgrade-only</sw-action>
</ETX-300>
</zero-touch-configuration>
</config>
</edit-config>
</rpc>
Note
You can navigate to file dir, to check if your device has a ZTP file (zero-touch-
confg-xml). If it does not, this means that the ZTP process has not yet been
performed on your device. The zero-touch-config-xml appears in the file directory
once ZTP has been performed on the device.
The following procedure describes how to prepare the ZTP XML file with software
image and configuration file directives, as required, before performing ZTP on
your device the first time. Once this file is prepared, place it on the TFTP server
(see Setting Up the TFTP Server) and update it, as required.
 To prepare the ZTP XML file:

1. Enclose the directives for all devices in the element pair
<zero-touch-configuration> </zero-touch-configuration>.
2. Enclose the directives for each device by an element pair,
<device name></ device name >. For example, <ETX-100></ETX-100>.
3. Enter values for the software directives (sw-version, sw-action, sw-src-file,
sw-dst-file) to supply information about the software file to download. See
Software Directives for a detailed explanation of each software directive.
4. Enter values for the configuration directives (cfg-version, cfg-action,
replace-cfg, cfg-src-file, cfg-dst-file) to supply information about the
configuration file to download. See Configuration Directives for a detailed
explanation of each configuration directive.
Note Steps 3 and 4 are optional, depending on whether the device requires
configuration, software, or both.
Setting Up the TFTP Server
Note If required, you can install a TFTP server application on your PC (refer to TFTP
Application in the Administration chapter).
 To set up the TFTP server:

1. Add the following files to the TFTP root directory:
 Prepared Zero Touch XML file

 Software image file for current ETX2 SW version – if required by ZTP XML
file directives
 Configuration file – if required by ZTP XML file directives
Setting Up the DHCP/DHCPv6 Server
Note If required, you can install a DHCP server application on your PC.
 To set up the DHCP server:

1. Configure the lease on your DHCP/DHCPv6 server with the required DHCP IP
address range, TFTP server IP address, and optionally, the path and/or file
name of the ZTP file.
Configuring ETX2 Device for On-Net Zero Touch

Before performing Zero Touch Provisioning the first time, configure your device
for management access, and enable the DHCP/DHCPv6 client for the Router
Interface. Save this configuration directly to startup-config, or load it as user-
default-config.
Note DHCP/DHCPv6 is a common method for providing the device with an IP address,
but it is not mandatory. The IP address can be manually configured, or provided
by other methods, such as PPPoE.
 To configure ETX2 for Zero Touch:

1. Add an SVI port.
2. Create classifier profiles for matching all traffic and matching untagged
traffic.
3. Add two flows (incoming and outgoing) connecting the out-of-band Ethernet
4. Add a router interface (possibly over VLAN), enter dhcp to enable as a DHCP
client or dhcpv6-client to enable as a DHCPv6 client, and bind it to the SVI.
The DHCP server typically provides route to the next hop; if not, manually
configure this as well.
5. Enter no shutdown to activate the router interface.
6. Enter save to save your configuration as initial startup-config.
The following script shows an example of the implementation of the
configuration steps above. The IP address and default gateway do not have to be
configured if they are sent by the DHCP server.
Note The script below shows enabling the device as a DHCP client. You can enable the
device as a DHCPv6 client by replacing dhcp in the example below with dhcpv6-
client.

#*******************************Adding_SVI***********************************
config port
svi 1
no shutdown
exit all
#***************************Adding Classifier_Profiles***********************
config flows
#***************************Configuring_Flows********************************
flow mng_in
classifier untagged
no policer
egress-port svi 1
no shutdown
exit
flow mng_out
classifier all
ingress-port svi 1
no shutdown
exit all
#*********************Configuring_Router_Interface***************************
configure router 1
interface 1
bind svi 1
vlan 4094
dhcp
address 172.18.141.39/24
no shutdown
exit
exit all
save
Verifying Zero Touch Success

If the settings on your device, DHCP Server, and TFTP Server have been
configured correctly, on device reboot, Zero Touch Provisioning starts
immediately.
If a software file and/or configuration file is downloaded during ZTP, upon
completion of the process, the device reboots with the new software and
configuration files.
Upon successful completion of ZTP, ETX2 sends the download_end (with success
indication) event to all configured network managers. Otherwise, if an error
occurs, ETX2 sends the download_end (with failed indication) event.
The following procedure lists how to verify success of ZTP.

 To verify success of ZTP:

1. Navigate to file show sw-pack.
The new SW pack should appear with its creation date.
2. Navigate to file dir.
Zero-touch-config-xml should appear with its creation date and time.
2. Navigate to config router (1) info.
The router interface should now have the static IP defined in the CFG file.
Configuring Zero Touch via Trap
 To enable sending the trap:

3. Navigate to configure management snmp.
The config>mngmnt>snmp# prompt is displayed.
4. Enter:
bootstrap-notification
ETX2 sends the systemBootstrap trap every 120–240 seconds, until the
command no bootstrap-notification is entered, or the management
system acknowledges the trap. If ETX2 is rebooted before the trap is
acknowledged, it continues to send the trap after it completes its
startup.
3.5 Configuration and Management

Usually, initial configuration of the management parameters is performed via an
ASCII terminal. Once the management flows and corresponding router interface
have been configured, it is possible to access ETX2 via Telnet (IPv4 only) or
SNMP for operation configuration. See Preconfiguring ETX2 for SNMP
Management for an example of management configuration. For details on
configuring the router, refer to the Router section in the Traffic Processing
chapter.
The following table summarizes management options for ETX2.
Table 3-6. 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 (IPv4 Terminal emulation application

only), SSH (see Working with Telnet and SSH
below)
3-20 Configuration and Management ETX2

Port Manager Transport Method Management Application

Location Protocol
SNMP RADview (see Working with

RADview below)
Third-party NMS (see Working
with below)
Ethernet Local, remote Inband Telnet (IPv4 RADview (see Working with
FE/GbE/ only), SSH RADview below)
10GbE Terminal emulation application
(see Working with Telnet and SSH
below)
SNMP Third-party NMS (see Working

with below)
Note
By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled. See Management Access Methods for details on enabling/disabling a
particular method.
3.6 Management Access Methods

You can enable or disable access to the ETX2 management system via Telnet (IPv4
only), SSH, or SNMP applications. By disabling Telnet, SSH, or SNMP, you prevent
unauthorized access to the system when security of the ETX2 IP address has been
compromised. When Telnet, SSH, and SNMP are disabled, ETX2 can be managed
via an ASCII terminal only. Additionally, you can enable or disable file transfer via
SFTP/TFTP.
Applicable Products
This feature is applicable to all ETX2 products and to PMC in ETX205A.
Inband and Out-of-Band (OOB) Management Access

Two types of ETX management access are supported:
• Inband – ETX host (management RI) resides directly over one or two VLANs in
a specific port or over a Bridge port (for example, to allow management
access in a Ring topology).
ETX2 Management Access Methods 3-21

MNG RI
(ETX Host)
Router NNI
Figure 3-9. ETX Host over VLANs

Ring Port East
NNI
MNG RI
(ETX Host)
Router Bridge Bridge Port
Ring Port West
NNI
Figure 3-10. ETX Host over Bridge Port

• Out-of-band (OOB) – In all ETX2 devices, MNG access via OOB port is
supported to access the device host only, and not the management VLAN
Bridge domain. In ETX220A, it is also possible to configure the OOB port to
reside over a management VLAN bridge domain, so that it can access the
local host and also be accessible inband to any device/NMS connected over
this management broadcast domain (VLAN).
MNG RI
(ETX Host)
OOB
Router MNG
Port
Figure 3-11. Direct Host OOB MNG Access (all ETX2 devices)
OOB
MNG
Port
MNG RI
(ETX Host)
Router Bridge Bridge Port
NNI
Figure 3-12. Bridge Domain OOB MNG Access (ETX220A only)
3-22 Management Access Methods ETX2

Limiting SSH Encryption Algorithms

By default, when a user accesses a device with SSH, the device accepts any
supported SSH encryption algorithm.
ETX2 enables you to limit the SSH server to up to six of the following supported
SSH algorithms:
• AES-CBC 128, 192, 256
• AES-CTR 128, 192, 256
• 3DES-CBC 168
• 3DES-EDE-CBC 112
• ARC4 128, 256
Factory Defaults
By default, access is enabled for all the applications.
In the default factory configuration, ETX2 allows management from the OOB
management port.
The default factory configuration includes the following:
• Allows untagged management access from the OOB port
• Default IP address of the Router Interface is 169.254.1.1/16
• No default Gateway configuration
• Allows local management access using a PC to an ‘out of the box’ ETX2
device:
 When PC uses DHCP, access to ETX2 device is automatically established
(PC address defaults to 169.254.x.y as no DHCP server  Microsoft
protocol).
• Includes flows to and from an SVI Router and a Router Interface with a fixed
and set IP address
• SVI, RI, and flow are assigned with indexes at the end of the device range and
reserved flow names (to coexist with existing scripts).
 SVI #: 96 (highest valid SVI index)
 RI #: highest valid RI number (for example, for ETX205A: 32)
 Flows: mng_access_default_in, mng_access_default_out
• Not backward compatible to user configuration CLI scripts that configure OOB
port
ETX2 Management Access Methods 3-23

Figure 3-13. Untagged Management Access from OOB MNG Port

The factory default configuration is only loaded if there is no startup-config or
user-default-config (for example, after executing the factory-default command).
If you copy a script and paste it to the terminal after factory-default-config is
loaded, it is important to verify that the configuration in the script does not
conflict with the factory default configuration.
You can delete the factory default configuration. You can also replace the
factory-default with a download of a fresh startup-config, by performing Reset.
You can add an additional IP address over the RI to allow remote access.
When accessing remotely, it is possible to delete the local IP 169.254.1.1/16.
3.7 CLI-Based Configuration
Working with Terminal

ETX2 has a V.24/RS-232 asynchronous DCE port, designated CONTROL, and
terminated in an RJ-45 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 (such as
HyperTerminal or PuTTY) to manage ETX2 via the control port. The following
procedure shows how to start a terminal control session using HyperTerminal.
 To start a terminal control session:

Make sure that ETX2 is connected to a laptop, as explained in Connecting to
a Terminal section in the Installation and Setup chapter.
Start the terminal emulation program.
For example, start HyperTerminal by navigating to
Start>Programs>Accessories>Communications>HyperTerminal.
From the menu of the New Connection –HyperTerminal window that opens,
create a new terminal connection by selecting File>New Connection, and in
the Connection Description window that opens, assign a Name to the
connection, and click OK.
3-24 CLI-Based Configuration ETX2

Figure 3-14. Creating Terminal Connection using HyperTerminal

In the Connect To window that opens, in Connect using, select COM1, and
then click OK.
The Com Properties window opens.
In the Com Properties window, configure the following laptop communication
port parameters, and then click OK.
 Bits per second (speed) – baud rate of 9.6 kbps (9600)
 Data bits – 8 bits/character
 Parity – no parity
 Stop bits – 1 stop bit
 Flow control – no flow control
Figure 3-15. Configuring Laptop Communication Port Parameters

Configure character delay by navigating in the home page menu to
File>Properties, and in the Serial Properties window that opens, clicking the
Settings tab, and then the ASCII Setup button.
In Character delay, select 10, and then click OK. The terminal input delay
between characters is now at least 10 msec.
ETX2 CLI-Based Configuration 3-25

Figure 3-16. Configuring Character Delay

Power-up ETX2.
The boot manager of ETX2 starts, and displays a message that you can
stop the auto-boot and enter the boot manager by pressing any key. A
running countdown of the number of seconds remaining until auto-boot
is displayed. If it reaches 0 before you press a key, then after a few
seconds a message is displayed showing that the active software pack is
being loaded.
After a few more seconds, the login prompt is displayed. See Login for
details on logging in.
Figure 3-17. Powering Up Device
Accessing a Remote Terminal

You can access the terminal for the x86 card of PMC enabled devices (relevant for
ETX205A with PMC option), from the ETX2 CLI, without the need for a separate
terminal.

Characters typed at the ETX2 CLI prompt are redirected to and from either the
local terminal (if managing ETX2 via the control port) or the Telnet/SSH session
(if managing ETX2 remotely) to the x86 host, via the RS-232 connection
between the ETX2 NTU and the x86 card.
Note You can also run a Telnet (IPv4 only) or SSH session directly to the x86 processor
(SSH only in the case of PMC).
 To access an x86 terminal:

1. Navigate to configure chassis ve-module.
2. To switch from the ETX2 terminal to the x86 terminal, at the prompt, enter:
remote-terminal
The x86 terminal prompt is displayed, and you can type commands for
the x86 terminal.
3. When you need to exit the x86 terminal, press:
<ctrl>+<shift> + -.
Working with Telnet and SSH

Typically, the Telnet/SSH host is a PC or Unix station with the appropriate suite of
TCP/IP protocols. Telnet is supported in IPv4 only.
To enable the Telnet/SSH host to communicate with ETX2, it is necessary to
configure the ETX2 IP address settings (refer to the Router section in the Traffic
Processing chapter for details). This is usually done via a terminal emulation
program (see Working with Terminal). After this preliminary configuration, you
can use a Telnet/SSH host connected directly or via a local area network.
The following procedure describes how to connect to ETX2 via Telnet. You can
connect to ETX2 via SSH (more secure) using a program, such as PuTTY.
 To connect to ETX2 via Telnet:

1. At the Telnet host, enter the necessary command (e.g. at a PC enter:
telnet <IP-address>).
The Telnet login window appears for the device as shown below.
Figure 3-18. Telnet Connection to Unit

2. Log into the device as explained in Login. See the Using the CLI section for
details on using the CLI commands.

Adding a Telnet Client Session

The ETX2 management system allows you to open an additional Telnet session
(terminal, Telnet, or SSH) to a remote device while you are in an active CLI
management session (Standard IETF RFC 854).
The Telnet client allows you to manage a remote unit without IP connectivity to
the host device. Moreover, the remote unit usually treats the Telnet client traffic
as originating from a secure source (ETX2). This traffic is unlikely to be filtered
out by an ACL rule of the remote unit, in contrast to non-secure PC traffic.
Network
Telnet RS-232
Remote RAD
Device RAD Device
PC
Figure 3-19. Managing Remote Device, Using Telnet Client Functionality
Source IP Address
The source IP address depends on the location in the CLI tree from which the
Telnet client command is activated:
• If the Telnet client command is activated from the router context, the routing
table of the current router defines the IP address that the packets are sent
from.
• If the Telnet client command is activated outside the router context, the
routing table of Router 1 defines the IP address that the packets are sent
from.
If the destination IP address is not a valid unicast IP address, ETX2 rejects the
command.
Special Characters
When the client session is open, its parent session passes all special characters
(such as <Ctrl> + <any key>) without parsing or acting upon them. The only
exception is the <Ctrl> + <_> key combination, which closes the client Telnet
session. This allows you to terminate the connection and return to the parent
session if the client session becomes unresponsive, rather than waiting for the
inactivity timeout to end the connection.
Inactivity Timeout
When a Telnet client is used, the inactivity timer of the parent session rearms.
This ensures that as long as the client session is active, its parent session is not
terminated due to an inactivity timeout. Likewise, when the inactivity timer of the
parent session expires, it is terminated together with its client session.
Termination
The client session is terminated if one of the following occurs:
• You quit the client session by using the <Ctrl> + <_> key combination. When
this key combination is entered, ETX2 terminates the client session and

returns to the parent session prompt. This is useful when the remote device
stops responding or the connection to it is lost.
• You quit the parent session.
• The parent session is terminated due to inactivity timeout.
Configuring Telnet Client

Telnet client sessions can be invoked from any CLI context.
 To start a client Telnet session:

• At any level, start a client Telnet session by specifying the IP address of the
remote device and (optionally) destination TCP port (default 23):
telnet <ip-address> [port <0–65535>]
 To close a client Telnet session:

• At any level, enter:
<Ctrl> + <_>
ETX2 terminates the client Telnet session and returns to the parent
session prompt.
Viewing Telnet Client Session Information

The details of the client Telnet session (destination IP address and duration) are
available in the output of the command show users-details.
Activation and termination of a client Telnet session generate the
remote_terminal_started and the remote_terminal_ended events, respectively.
The events are stored in the ETX2 log file, and generate SNMP traps.
 To display the Telnet client session information:

• In the configure>management# prompt, enter:
show users-details.
The result of the command show users-details is displayed.
The Connected To and the For (sec) fields in the third line for user 123456 detail
the destination IP/ protocol type and duration of the active client Telnet session.
ETX2# configure management
ETX2>config>mngmnt# show users-details
User:1234 Level:su Popup:Disabled
From:1.1.1.1/SSH For(sec):120
User:123456 Level:oper Popup:Disabled
From:100.100.100.100/Telnet For(sec):120
Connected To:1111:2222:3333:4444:5555:6666:7777:8888/Telnet For(sec):100
Figure 3-20. Output of users-details
Login
ETX2 supports various access levels to prevent unauthorized modification of the
operating parameters. Refer to User Access in the Management and Security
chapter for more information on the access levels, as well as a list of the default
users defined in the device and information on configuring additional users.

Note The superuser (su) can perform all the activities supported by the ETX2
management facility.
You can log into your device with your username and password.
If you fail to log in to the terminal five times (due to wrong username or
password) in less than five minutes, from the same IP address (or the local
console), the device does the following:
• Blocks further login attempts from the same IP (or the local console) for ten
minutes (the default) or the number of minutes configured in the login timer
(refer to timeout configuration in Control Ports section of Management and
Security chapter). Attempts from remote are answered with immediate TCP
reset, without trying to authenticate the user. Attempts from the local
console are rejected, and the following error is generated: Console temporary
blocked due to excessive failed login attempts.
• Blocks any management protocol from the same IP (or the local console),
such as SNMP and NETCONF, for ten minutes (the default) or the number of
minutes configured in the login timer (timeout).
• Logs the failed_login event, with the maximum number of attempts exceeded
string.
When the locking period is over, the device lifts the block, even if there were
further attempts during this time. Afterwards, you can fail five more attempts
before being locked again.
Note • SNMP access attempt with wrong credentials does not count as a failed login
attempt, and the user is not blocked due to it.
• Information on recent failed login attempts (of sources that failed since last
being unblocked) can be displayed by invoking the show failed-login-attempts
command (under the management level). Refer to Viewing Failed Login
Attempts in the Management and Security chapter.
• <CR> for either username or password is ignored, and not considered a failed
login attempt.
Logging In
 To log in to ETX2:
1. At the user prompt (user>), enter the user name and press <Enter>.
The password prompt (password>) appears.
2. Enter the password (default is 1234) and press <Enter>.
The base prompt ETX2# appears.
Note You can display a banner at login. Refer to the Administration chapter for details.

Changing Password
It is recommended that you change the users’ default passwords to prevent
unauthorized access to the unit using the special option chngpass. This option is
also useful in case the user has forgotten their password.
 To change/restore a password:
1. At the User prompt (config>mngmnt# user>), enter chngpass and press
<Enter>.
2. Enter user as user name and press <Enter> to receive a temporary password.
With this password you can enter as user and change the password to your
own.
A key code is displayed.
3. Send the key code to RAD Technical Support department.
RAD technical support department will generate a temporary password
which is valid for a single login.
4. Use this temporary password to log in and set a new permanent user name
and password.
Lost Superuser Password

If your superuser password has been lost, contact RADCare Global Professional
Services.
Using the CLI

The CLI consists of commands organized in a tree structure of levels, starting at
the base level. Each level (also referred to as context) can contain levels and
commands (see Navigating for more information on the levels and commands
available in ETX2). The level is indicated by the CLI prompt.
Note Most commands are available only in their specific context. Global commands are
available in any context. You can type ? at any level to display the available
commands.
CLI Prompt
The base level prompt contains the device name, which is ETX2 by default (the
device name can be configured in the system level; refer to Device Information in
the Administration chapter). The prompt ends with $, #, or >, depending on the
type of entity being configured and the user level.
If a new dynamic entity is being configured, the last character of the prompt is $.
Examples of dynamic entities include flows, QoS profiles, and OAM CFM entities.
If a new dynamic entity is not being configured, the last character of the prompt
is > (for tech or user access levels) or # (for other access levels).

Note The examples in this manual use # as the last character of the prompt, unless the
creation of a new dynamic entity is being illustrated.
After you type a command at the CLI prompt and press <Enter>, ETX2 responds
according to the command entered.
CLI Inactivity Timeout

If a CLI session is inactive (i.e. no input received) for ten minutes (the default) or
the number of minutes configured in the inactivity timer (refer to console-
timeout configuration in Control Ports section of Management and Security
chapter), the device terminates the session and logs the logout event, with the
due to inactivity timeout string.
Navigating
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location. To navigate up, use the global command exit. To
navigate all the way up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed (or not) 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) followed by 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 did not change.
ETX2# configure system date-and-time date-format yyyy-mm-dd
ETX2# show configure system system-date
2013-06-10 15:08:20 UTC +00:00
ETX2#
In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX2# configure
ETX2>config# system
ETX2>config>system# date-and-time
ETX2>config>system>date-time# date-format yyyy-mm-dd
ETX2>config>system>date-time# exit
ETX2>config>system# show system-date
2013-06-10 15:13:23 UTC +00:00
ETX2>config>system#
Full-Path Command
Full-path command allows you to enter a CLI command anywhere in the tree as if
the current level was the CLI root, by preceding the command or level change

with a backslash character. The device executes the command as if it were

invoked from the CLI root.
If you enter a level change (preceded by \) without a command, the CLI does not
return to the prompt of the level that the command was invoked from, but
remains at the changed level. For example, the \configure system command,
when invoked from any level in the CLI tree, returns the
ETX2>config>system# prompt. However, if you enter a level change followed
by a command, the system performs the command and then returns the prompt
of the level that the command was invoked from. For example, if following the
command ETX2>admin>scheduler#, you type \configure system name
my-device, the latter command sets the device name to my-device and then
returns the prompt my-device>admin>scheduler#.
Note Before executing a full path command, the CLI engine exits to the CLI root. Some
commands (e.g. ping) behave differently, depending on the location they were
executed from. The following command, for example, would use a router 1 source
address, although executed from router 2:
ETX2>config>router(2)# \configure router 1 ping 192.168.1.1.
Command Tree
The tree command displays a hierarchical list of all the commands in the CLI tree,
starting from the current context.
 To view the entire CLI tree (commands only):

At the root level, type tree.
ETX2# tree
|
+---admin
| |
| +---factory-default-all
| |
| +---factory-default
| |
| +---license
| | |
| | +---license-enable
| | |
| | +---show summary
| |
| +---reboot
| |
| +---scheduler
| | |
| | +---clear-finished-schedules
more..
Press <Enter> to see more or <CTRL-C> to return to the prompt.
When adding the detail parameter, the output also includes the parameters and
values for each command.

 To view the CLI tree including all parameters and values:

1. Navigate to the required context by typing level names separated by a space
and press <Enter>.
2. Type tree detail and press <Enter>.
ETX2>config# tree detail
configure
|
+---access-control
| |
| +---access-list [{ipv4|ipv6}] <acl-name>
| | no access-list <acl-name>
| | |
| | +---delete <sequence-number>
| | |
| | +---deny udp <src-address> [<src-port-range>] <dst-address>
[<dst-port-range>] [dscp <dscp-value>] [log] [sequence
<sequence>]
| | | deny tcp <src-address> [<src-port-range>] <dst-address>
[<dst-port-range>] [dscp <dscp-value>] [log] [sequence
<sequence>]
| | | deny icmp <src-address> <dst-address> [icmp-type <icmp-type-
number>]
[icmp-code <icmp-code-number>] [dscp <dscp-value>] [log]
[sequence <sequence>]
| | | deny ip [protocol <ip-protocol-number>] <src-address> <dst-
address>
Press <Enter> to see more or <CTRL-C> to return to the prompt.
Command Structure
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 the user according to
parameter requirements
You can type only as many letters of the level, command, or parameter as
required by the system to identify it. For example, you can enter config manag to
navigate to the management level.
Special Keys
The following keys are available at any time:
? List all commands and levels available at the current level.

<Tab> Command-line completion; complete the unambiguous

characters of the command, and display a list of available
commands beginning with those characters (as when
pressing ?).
↑ Display the previous command (history forward).
↓ Display the next command (history backward).
<Backspace> Delete character before cursor.
<Delete> Delete character before cursor.
<- Move cursor one character left.
-> Move cursor one character right.
<Alt>+B, <Esc>+B Move cursor left one word (or go to start of word).
<Alt>+D, <Esc>+D Delete until end of word starting from the cursor.
<Alt>+F, <Esc>+F Move cursor right one word (or go to end of word).
<Ctrl>+<_> Exit CLI.
or
<Ctrl>+<Shift>+<->
<Ctrl>+A Move cursor to start of line.

<Ctrl>+B Move cursor one character left.
<Ctrl>+C Interrupt current command.
<Ctrl>+D Delete character to right of cursor.
<Ctrl>+E Move cursor to end of line.
<Ctrl>+G Return to upper level.
<Ctrl>+H Delete character to left of cursor.

<Ctrl>+K Delete text from cursor to end of line.
<Ctrl>+L Redisplay current line.
<Ctrl>+P Display the previous command (history forward).
<Ctrl>+Q Resume transmission (XON).
<Ctrl>+S Pause transmission (XOFF).

<Ctrl>+U Delete text up to cursor.
<Ctrl>+W Delete word to the left of cursor.
<Ctrl>+Y Paste text last deleted by a shortcut.
<Ctrl>+Z Navigate to base level.
Getting Help
You can get help in the following ways:
• Type help to display general help (see General Help).

• Type help <command> to display information on a command and its

parameters (see Command Help).
• Type ? to display the commands available in the level (see Level Help).
• Use <Tab> while typing commands and parameters, for string completion
(see Command-Line Completion).
• Use ? after typing a command or parameter, for interactive help (see
Interactive Help).
General Help
Enter help at any level to display general CLI help, including:
• Short description of CLI interactive help
• Commands and levels available at the current level
• Globally available commands
• CLI special keys (hotkeys)
• Output modifiers for filtering output
• URLs for device manual and shelf view manual
Example of help command output from the root level:

1. Full help - 'help <cmd>'.

2. To complete level name, command, keyword, argument - <tab> ('conf<tab>' =>
'configuration').
3. To display all currently valid levels, commands, keywords or arguments -
'?' ('name ?' => '<name-of-device>').
Commands and levels:
admin + Adminstrative commands
clear-statistics - Clear all statistics
configure + Configure device
debug +
file + File commands
logon - Allows to logon to debug level
on-configuration-error - Determines the device behavior when
encountering an error in configuration
file
Global commands:
copy - Copy file
echo - Displays a line of text (command) on
the screen
exec - Execute script of CLI commands
exit - Returns to the next higher command
level (context)
help - Displays information regarding commands
in the current level
history - Displays the history of commands issued
since the last restart
info - Displays the current device
configuration
level-info - Displays the current device
configuration - commands from the
current level only
logout - Logs the device off
ping - Ping request to verify reachability of
remote host
[no] popup-suspend - Suspends popup messages
save - Save current settings
[no] schedule - Schedule a command to run in a future
time
telnet - Open telnet client session
trace-route - Checks the path connectivity to a
remote device
tree - Displays the command levels from the
current context downwards
Hotkeys:
Ctrl-H, Del, Backspace -Delete character left of cursor
Ctrl-D -Delete character right of cursor
Ctrl-U -Delete text up to cursor
Ctrl-K -Delete text from cursor to end of line
Ctrl-W -Delete word left of cursor
Alt-D, Esc-D -Delete word right of cursor
Ctrl-Y -Paste last deleted text
Tab -Completion token
? -Interactive help token
Ctrl-P, Up arrow -History forward
Down arrow -History backward
Ctrl-B, Left arrow -Move cursor left one character
Right arrow -Move cursor right one character
Ctrl-A -Move cursor to beginning of line
Ctrl-E -Move cursor to end of line
Alt-B, Esc-B -Move cursor left one word

Alt-F, Esc-F -Move cursor right one word

Ctrl-L -Redisplay current line
Ctrl-S -Pause transmission (XOFF)
Ctrl-Q -Resume transmission (XON)
Ctrl-C -Interrupt current command
Ctrl-G -Return to upper level
Ctrl-Z -Return to CLI root
Ctrl-_ -Exit CLI
Output Modifiers (usage: 'command | modifier'):
begin <regular-expression> -Start printing once expression found
exclude <regular-expression> -Print lines not containing expression
include <regular-expression> -Print lines containing expression
Show commands can be printed repeatedly by appending 'refresh' to them
ETX-2 Installation and Operation Manual : https://goo.gl/z8ULBp Command Help

Enter help <command> to display command and parameter information.
ETX2>config>system# help name
- name <name-of-device>
- no name
<name-of-device> : Adds free text to specify the device name [0..255 chars]
Level Help
Enter ? at the command prompt to display the commands available in the current
level.
ETX2>file# ?
delete - Delete file
delete-user - Deletes a file from the device
[no] description - Description of the file
dir - Display file directory
user-file-dir - List of all user files in the device
show banner-text - Display banner

show configuration-files - Displays configuration files
properties
show copy - Display Copy progress
show factory-default-config - Display factory-default-config
show file-details - Displays the details of the file
show rollback-config - Display rollback-config
show schedule-log - Display schedule-log
show startup-config - Display startup-config
show sw-pack - Display SW packs
show user-default-config - Display user-default-config
show user-dir
Command-Line Completion
Command-line completion saves you command-line entry time and reminds you
the syntax of command-line entities (levels, commands, parameters, flows, and
profiles).
In a command-line, ETX2 completes command-line entities, when you press
<Tab> immediately following a string (one or more characters).

Some user-defined entity names, such as flow names or profile names, can be
completed as well. If you enter an entity name (flow, profile, or similar) that does
not exist in the database, ETX2 creates this entity with the selected name.
• If the command-line entity name can be completed in only one way, when
you press <Tab>, ETX2 autocompletes the entire name and appends a space.
• If the command-line entity name can be completed in more than one way,
ETX2 appends the characters that are common to all possibilities, and
displays a list of the completion possibilities beginning with those characters.
• If the string is already a complete entity name
(level/command/parameter/flow/profile) or cannot be completed to a
complete name, no completion is done.
• Pressing <Tab> following a complete command name (followed by a space),
displays a list of available command arguments, if they exist (same behavior
as ?).
• Pressing <Tab> following a string and a space returns a CLI error: Ambiguous
Command. This is because the string entered could be completed to more
than one command and is therefore ambiguous.
• Pressing <Tab> at the beginning of a command line behaves like a regular
tab, and unlike ?, does not display a list of available commands.
The following tables show examples of string completion.
Table 3-7. String Completion
Level String Possibilities for Completion Result After Pressing <Tab>
file show c show configuration-files show co

show copy
file show con show configuration-files show configuration-files<space>
config>flows class classifier-profile classifier-profile<space>
config>sys name name name
config mgm No possibilities mgm
config>flows flows# flow my-f my-flow-1 my-flow-

my-flow-2
config>flows flows# flow my-flow-1 my-flow-1 my-flow-1<space>
config>flows flows# flow my-flow-3 No possibilities my-flow-3

This is a new flow, as my-flow-3
did not exist before.
Interactive Help
To get interactive help, type ?.
In general, typing a ? directly after a string displays possibilities for string
completion, while typing <space> and then a ? displays possibilities of the next
argument.

When a <CR> appears in a ? list, the string you entered is itself a valid command
needing no further additions. Pressing <Enter> executes the command or
navigates to the indicated level.
Typing ? immediately after a command or partial command with no space before
the ?, tells ETX2 to display all possibilities for completing the string. Help output
is always followed by the string you typed with the cursor at the end of the
string waiting for input.
ETX2>config>flows# classifier-profile myclass m?
match-any
ETX2>config>flows# classifier-profile myclass m
ETX2>admin# fact?
factory-default-all - Return to factory default and reboot
factory-default - Return to factory default configuration and
reboot
ETX2>admin# fact
ETX2>admin# factory-default?
<CR>
ETX2>admin# factory-default
Current configuration will be erased and device will reboot with factory
default configuration. Are you sure ? [yes/no] _
When a string cannot be completed, ETX2 displays “cli error: Invalid Command”.
ETX2>admin# stac?
# cli error: Invalid Command
ETX2>admin# stac
ETX2>file# da ?
# cli error: Invalid Command
ETX2>file# da
Typing <?> after a space between a command or level name and the ? tells ETX2
to display possibilities of the next argument. If the string preceding the ? is
ambiguous or invalid, an explanatory message is displayed. The string does not
have to be a complete command.
If there is only one possible command starting with that string, pressing <Enter>
will execute the command. If there is more than one command that starts with
the string, the CLI displays a message that it can’t clarify which command you
want.
ETX2>admin# factory?

factory-default - Return to factory default configuration
and reboot
A command followed by a ? without a space, shown above, returns a list of
possible completions. The same command followed by a space and then ? returns
an ambiguous command message. This means the string entered could be
completed to more than one command and is therefore ambiguous, as shown
below.
ETX2>admin# factory ?
# cli error: Ambiguous Command

ETX2>admin# factory
A string that is a complete command name followed by a space ? displays all
possible command parameters.
ETX2>config>flows# show ?
summary - Displays list of flows
ETX2>config>flows# show
ETX2>config>flows# classifier-profile ?
<classification-n*> : [1..32 chars]
ETX2>config>flows# classifier-profile
The next example shows a complete command to which a parameter could be
appended. It also shows how a string that is a complete command is executed by
pressing <CR>, or <Enter>.
ETX2>config>access-control# resequence access-list acl_1 ?
<CR>
<number> : [0..100000]
The next example shows a complete command that has no parameters.
ETX2>config>flows# classifier-profile myclass match-any ?
<CR>
ETX2>config>flows# classifier-profile myclass match-any
Scheduling CLI Commands

You can schedule the execution of CLI commands at a future date and time. By
default, no scheduling is configured.
The global schedule command is used to configure the scheduling of a command.
You can specify any command to be scheduled except the logout command.
When you schedule a command, before saving it, ETX2 prefixes the command
with the path from which the schedule command was executed. To specify a CLI
command with a full CLI level path, you should schedule it at the CLI root level.
ETX2 tests the command that is configured as scheduled in the same way that it
would be tested when executed; if the tests fail, you are notified of this, but the
command is still scheduled, since it may be valid when the scheduled time arrives.
The following types of schedules can be configured:
In <minutes> Executed once, after the specified number of minutes. This

type of schedule is not saved in nonvolatile (permanent)
ETX2 memory; it is deleted at device reboot whether or
not it was executed.
At Executed once at the specified date and time. This type of

<date-and-time> schedule can be optionally saved in permanent memory, in
order to be available after device reboot.
Note
Schedules for date and time are saved in system local time. If the local time
changes, ETX2 does not modify the schedules to compensate for the change;
therefore, changing the time can cause schedules to be executed twice or not
executed at all.

Schedules are marked as finished after they are executed.

When executing scheduled commands, ETX2 assumes a Yes answer for any
confirmation questions. When a scheduled command is executed, it is sent to
TACACS+ and Syslog accounting, as if it were executed by a CLI user.
Configuring Command Scheduling
 To schedule a command:
• In any level, enter the schedule command according to the type of schedule:
 In <minutes> – Enter:
schedule <name> in <minutes> “<command>”
The schedule is saved with its name set to <name>, and the specified
<command> is executed after the specified amount of <minutes> has
elapsed, regardless of changes to the local system time.
Range for <minutes>: 1–14400 [10 days]
 At <date-and-time> – Enter:
schedule <name> at {january | february | march | april | may | june | july |
august | september | october | november | december} <dd> <yyyy>
<hh>:<mm> <command> [volatile | nonvolatile]
The schedule is saved with its name set to <name> (in permanent
memory if nonvolatile was specified), and the specified <command> is
executed at the specified date and time. If the local system time is
changed after the schedule is configured, the scheduled command might
not be executed, or might be executed twice.
Note An invalid date and time is not allowed; however, a date and time in the past is
allowed; a schedule with its date and time in the past will never be executed
unless the device date/time is changed such that the schedule date and time is
no longer in the past.
Note Schedules can be added or deleted, but not changed. If you wish to change the
details of a schedule, you have to delete it and then recreate it with the changes.
 To delete schedules:
• To delete a specific schedule, in any level enter:
no schedule <name>
• To delete all finished schedules, navigate to the admin scheduler level and
enter:
clear-finished-schedules
Viewing Scheduling Information

You can view the following scheduled information:
• Commands, with or without details of the commands
• Daylight saving time (For an explanation on the configuration of daylight
saving time, refer to Daylight Saving Time in the Timing and Synchronization
chapter.)

Note You can also enter the info command from the root of the device to view all
commands of the device, including scheduled commands (see Viewing the Device
Configuration section below).
 To view scheduling without command details:

•
Navigate to the admin scheduler level and enter:
show scheduler
ETX2# admin scheduler
ETX2>admin>scheduler# show scheduler
Current date: 27 December 2014 00:01 (UTC +2)
Schedule Name Type Prm Fin Activation

---------------------------------------------------------------------------
sched-1 Once (In) No No 1 day, 02:00:10
sched-2 Once (At) Yes Yes --
sched-n Once (At) Yes No 1 October 2015 12:21
Summer Time
Start (Recurring): Last Sunday of May, 02:00
End (Recurring): Last Thursday of October, 02:00
Offset : 60 minutes
Start : 31 May 2015 12:21
End : 25 October 2015 12:21
 To view scheduling with command details:

• Navigate to the admin scheduler level and enter:
show scheduler-details
ETX2# admin scheduler
ETX2>admin>scheduler# show scheduler-details
Current date: 16 September 2014 10:45 (UTC +2)
Schedule Name : sched-1
Type : Once (At)
Permanent : Yes
Finished : No
Activation (Local Time) : 22 March 2015 09:00
Activation In(Seconds) : 186 days 22:45:00
Command: copy log tftp://1.1.1.1
Schedule Name : sched-2

Type : Once (In)
Permanent : No
Finished : No
Activation In(Seconds) : 207 days 12:45:00
Command: copy log tftp://1.1.1.1
Summer Time
Start (Recurring): Last Sunday of May, 02:00
End (Recurring): Last Thursday of October, 02:00
Offset : 60 minutes
Start : 31 May 2015 12:21
End : 29 October 2015 12:21
Offset : 60

Table 3-8. Scheduling Display Parameters
Current date Current date and time, and current offset from UTC
Schedule Name Name of schedule
Type Type of schedule:

• Once (In) – to be executed in specified number of minutes
• Once (At) – to be executed at a specified date and time
Prm/Permanent Indicates if schedule is saved in permanent memory
Fin/Finished Indicates if schedule is marked as finished
Activation In output of show scheduler, indicates the amount of time before the scheduled
command will be executed, according to the type of schedule:
• Once (In) – Amount of time before the scheduled command will be executed, in the
form <hh:mm:ss>, <1 day hh:mm:ss> or <ddd days, hh:mm:ss>
• Once (At) – Date and time at which the scheduled command will be executed
• For either type, -- is displayed if the schedule is marked as finished.
Activation (Local In output of show scheduler-details for schedule type Once (At), displays the date and
Time) time at which the scheduled command will be executed.
Activation In In output of show scheduler-details for schedule types Once (In) and Once (At), displays
(Seconds) the amount of time before the scheduled command will be executed.
Command In output of show scheduler-details, displays the scheduled command.
Start (Date) For one-shot daylight saving time scheduling, displays daylight saving time start date
and time.
End (Date) For one-shot daylight saving time scheduling, displays daylight saving time end date and
time.
Start (Recurring) For recurring daylight saving time scheduling, displays the configured week of the
month, weekday, month, and time for daylight saving time start.
End (Recurring) For recurring daylight saving time scheduling, displays the configured week of the
month, weekday, month, and time for daylight saving time end.
Start For recurring daylight saving time scheduling:

• If the device is currently not in daylight saving time, displays the next scheduled date
and time for daylight saving time to start.
• If the device is currently in daylight saving time, displays the date and time at which
the daylight saving time started.
End For recurring daylight saving time scheduling, displays the next scheduled date and time
for daylight saving time end.
Offset Number of minutes to move the clock during daylight saving time
Configuration Errors
The following table lists the messages generated by the device when a command
scheduling configuration error is detected.

Table 3-9. Configuration Error Messages
Message Cause Corrective Action
Schedule with this name You tried to create a new schedule with Specify a name that is not being used
already configured a name that is used by an existing by an existing schedule.
schedule.
Warning: Scheduled The command that you specified to Check the command; if changes are
command failed sanity schedule may fail when executed. needed, delete the schedule and
re-enter it with the changed
command.
The logout command You specified the logout command as None. You are not allowed to
may not be scheduled the command to schedule. schedule the logout command.
Viewing the Device Configuration

You can enter the info command at the device root, to view all commands that
have been configured for the device. This includes scheduled commands, as they
are global commands. See Examples below.
 To view commands of a device:

• At the device root, type info.
Refreshing Output
You can specify that ETX2 should periodically refresh the output of a show
command.
 To periodically refresh the output of a show command:

• Append refresh [<sec>] to the command. The allowed range for <sec> is 3–
100 seconds (default is 5 seconds).
ETX2 enters refresh mode and displays the output of the command
periodically, along with an indication of how to exit refresh mode, at the
interval specified by <sec>. You cannot enter any commands while ETX2
is in refresh mode.
To exit refresh mode, type <ESC> or <Ctrl>+C.
The example below shows the result of refreshing the status of an Ethernet port
every 15 seconds, and typing <Ctrl>+C after the status is displayed twice.
Note The example uses a slot number to reference the port, which may not be
applicable to every device.
ETX2# configure port eth 1/1

ETX2>config>port>eth(1/1)# show status refresh 15
Name ETH-1/1
Administrative Status : Up
Operational Status : Down
Connector Type : SFP Out

Auto Negotiation : Other

MAC Address : 00-20-D2-50-E3-84
To exit the refresh-mode press ESC or Ctrl+C
Name ETH-1/1
Connector Type : SFP Out
Auto Negotiation : Other
MAC Address : 00-20-D2-50-E3-84
To exit the refresh-mode press ESC or Ctrl+C
ETX2>config>port>eth(1/1)#
Filtering Output
Some commands, such as info and show display large amounts of information as
their output. It is possible to control the type and amount of information
displayed, by filtering the output.
To filter a command’s output, append to the command:
| [include | exclude | begin] <filter-expression>
Keyword Description
include The output includes only lines that match the filter
expression.
exclude The output includes only lines that do not match the filter
expression.
begin The output starts with the first line that matches the filter
expression and continues with all further lines.
<filter-expression> A filter expression is a regular expression that defines what

to exclude, include or match at the beginning. Filter
expressions can contain letters, numbers, and
metacharacters (see below). Filter expressions are case
sensitive.
One and only one keyword is allowed. If no keyword is specified, no filtering is

performed.
The following example illustrates filtering output.
ETX2>config>system# info detail | include date
date-and-time
date-format yyyy-mm-dd
Metacharacters
Metacharacters are characters with special meaning. They allow you to define
filter criteria, while not being part of the filter criteria themselves. Some are
placeholders or wildcards. Some allow you to define ranges of characters to
either include or exclude. You can construct complex filter expressions to see the
exact output you want. Table 3-10 describes filter metacharacters.

Table 3-10 Filter Metacharacters
Metacharacter Description Example
. Matches any single character. r.t matches the strings rat, rut, and r t, but not
root.
$ Matches the end of a line. device$ matches the end of the string header
device but not the string header device-name.
^ Matches the beginning of a line. ^device matches the beginning of the string
device loaded from but not the string header
device-name.
* Matches zero or more occurrences of .* means match any number of any characters.
the preceding character.
\ This character is used to treat the \$ is used to match the $ character rather than
following metacharacter as an ordinary match the end of a line.
character. \. is used to match a period rather than match
any single character.
[] Matches any one of the characters r[aou]t matches rat, rot, and rut, but not ret.
[c1-c2] between the brackets. [0-9] matches any digit.
[^c1-c2] Ranges of characters are specified by a [A-Za-z] matches any upper or lower case letter.
beginning character (c1), a hyphen,
[^269A-Z] matches any character except 2, 6, 9,
and an ending character (c2); multiple
and uppercase letters.
ranges can be specified as well.
To match any character except those in
the range, use ^ as the first character
after the opening bracket.
| Logical OR two conditions together (band|comp) matches the lines bandwidth cir
999936 cbs 65535 and compensation 0.
+ Matches one or more occurrences of 9+ matches 9, 99, and 999

the character or filter expression
immediately preceding it.
“” Matches the string enclosed in the “e s” matches "double star"

quotation marks. The string may
include spaces. See Regular Expression
Syntax.
{i} Matches a specific number (i) or range A[0-9]{3} matches A followed by exactly three
{i,j} (i through j) of instances of the digits, i.e. it matches A123 but not A1234.
preceding character. [0-9]{4,6} matches any sequence of 4, 5, or 6
digits.
Regular Expression Syntax

A filter expression is a regular expression. A regular expression can be composed
of characters and metacharacters. Any combination of metacharacters can be
used. If you want spaces as part of the filter expression, enclose the expression
with quote metacharacters. All characters found after a space not enclosed by
quotes are ignored by the CLI.

The following table provides some example of regular expressions and the
resulting string that will be used to filter the CLI output.
Table 3-11. Examples of Regular Expression Syntax
Regular Expression Resulting Filter String
“str” str
“s t r” str
“str “str
“str\”str” str”str
“str\”str “str\”str
“str”str str
\”str” \”str”
“str1” | include str2 First expression – str1, second expression – str2
Enabling Entities
Some dynamic entities are created as inactive by default. After the configuration
is completed, the no shutdown command activates the entity, as shown below.
Note The example uses a slot number to reference the port, which may not be
applicable to every device.
ETX2# configure flows flow flow1

ETX2>config>flows>flow(flow1)$ ingress-port ethernet 0/3
ETX2>config>flows>flow(flow1)$ egress-port ethernet 1/1 queue 1 block 0/1
ETX2>config>flows>flow(flow1)$ classifier Classifier1
ETX2>config>flows>flow(flow1)$ no shutdown
ETX2>config>flows>flow(flow1)$exit
ETX2>config>flows#
The shutdown command is also used to deactivate/disable a hardware element
(such as a port), while no shutdown enables/activates it.
Using Scripts
CLI commands can be gathered into text files. They may be created using a text
editor, by recording the user commands or by saving the current configuration.
These files can be configuration files or scripts. Configuration files have specific
names and contain CLI commands that ETX2 can use to replace the current
configuration, while scripts contain CLI commands that add to the current
configuration. Configuration files can be imported from and exported to RAD
devices via file transfer protocols.
For more information on configuration files, refer to the description in the
Operation and Maintenance chapter.
In order to execute a CLI script, you have to copy/paste it to the CLI terminal, or
send it to ETX2 via the RADview Jobs mechanism, CLI script option.

Examples
 To schedule copying a log file in two hours:
schedule sched-copy-2hrs in 120 “copy log tftp://1.1.1.1”
 To schedule copying a log file on April 2 at 6:00, with the schedule saved in
permanent memory:
schedule sched-copy-Apr2 at april 2 2015 06:00 “copy log tftp://1.1.1.1” permanent
save
 To schedule shutdown of the device in five minutes:

ETX205A>config>flows>flow(v100in)$ schedule sched1 in 5
“shutdown”
 To display commands configured for the device (including scheduled shutdown

command):
ETX205A# info
.
Bridge Configuration
bridge 1
name "BRIDGE 1"
echo "Bridge Port Configuration"
# Bridge Port Configuration
port 1
spanning-tree
cost 10
no shutdown
exit
no shutdown
exit
port 2
spanning-tree
cost 20
no shutdown
exit
no shutdown
exit
.
schedule "sched1" in 5 "configure flows flow v100in shutdown"
ETX205A#
3.8 SNMP-Based Network Management
Preconfiguring ETX2 for SNMP Management

ETX2 can be managed by any SNMP-based network management station, such
as via the RADview family of network management stations, provided IP
communications is possible with the management station, as well as by the
standalone RADview stations.
ETX2 SNMP-Based Network Management 3-49

To manage ETX2 from a remote NMS, it is necessary to preconfigure the basic

parameters using a supervision terminal connected to the ETX2 CONTROL DCE
port. RAD recommends Layer-3 management access via the out-of-band Ethernet
management port.
 To configure ETX2 for management access:

Add an SVI port.
Create classifier profiles for matching all traffic and matching untagged
traffic.
Add two flows (incoming and outgoing) connecting the out-of-band Ethernet
Add a router interface, bind it to the SVI, and add a static route to the next
hop.
The following script provides the necessary configuration steps for ETX203AX
and ETX205A. The configuration steps for ETX203AM and ETX220A are the
same, with the exception that ingress-port Ethernet and egress-port Ethernet are
0/101 (and not 101). Replace IP addresses and entity names with values suitable
for your network environment.
#*******************************Adding_SVI*********************
config port
svi 92
no shutdown
exit all
#***************************Adding Classifier_Profiles*********
config flows
#***************************Configuring_Flows******************
flow mng_in
classifier untagged
no policer
egress-port svi 92
no shutdown
exit
flow mng_out
classifier all
ingress-port svi 92
no shutdown
exit all
#*********************Configuring_Router_Interface*************
configure router 1
interface 1
bind svi 92
address 172.18.141.39/24
no shutdown
exit
3-50 SNMP-Based Network Management ETX2


exit all
save
Configuring Management Access

This section describes how to configure general management parameters. It also
describes the command for selecting a subset of the supported SSH encryption
algorithms, when using SSH management access.
Note There is no explicit configuration for inband and outband management access.
 To configure management access:

• At the configure management access prompt enter the necessary commands
according to the tasks listed below.
Allowing SFTP access sftp Typing no sftp blocks access by SFTP.
Allowing SSH (Secure Shell) access ssh Typing no ssh blocks access by SSH.
Selecting acceptable SSH encryption algorithms ssh-encryption {all | Possible values:

algorithm <algorithm-1> all – all algorithms are accepted (default)
[algorithm-2] [algorithm-
algorithm-1 to algorithm-6 – one of the
3] [algorithm-4]
following: aes-cbc-128, aes-cbc-192, aes-cbc-
[algorithm-5] [algorithm-
256, aes-ctr-128, aes-ctr-192, aes-ctr-256,
6]}
3des-cbc-168, arc4-128, arc4-256
Notes:
• If all is selected, there is no need to select
any algorithms, and if you do, your
selection is ignored.
• If the command is repeated, the latest
instance replaces the previous one.
• If all is not selected, you must select at
least one algorithm.
• If multiple algorithms are selected, they
must be different ones.
• The order of the algorithms is not
important; usually the strongest is
negotiated first.
Allowing SNMP access snmp Typing no snmp blocks access by SNMP.
Allowing Telnet access (for IPv4 only) telnet Typing no telnet blocks access by Telnet.
Allowing TFTP access tftp Typing no tftp blocks access by TFTP.

Working with RADview
Overview
RADview is a Windows-based modular, client-server, scalable management
system that can be used in a distributed network topology or a single-station
configuration. RADview consists of the system and the following optional
modules:
• Service Manager (SM) – end-to-end Carrier Ethernet service provisioning for
Ethernet Access products. This module includes the Service Center (SC)
module, which is an end-to-end Carrier Ethernet and TDM service provisioning
for AXCESS+ products.
• Performance Monitor (PM) – portal for service SLA monitoring for both
carriers and their customers
The ETX2 element and network management systems include a CORBA
northbound interface, enabling easy integration into the customer’s umbrella
NMS. CORBA enables interconnectivity and communication across heterogeneous
operating systems and telecommunications networks. CORBA effectively supplies
a software interface that defines data models used between various
management layers. It supports multi-vendor distributed network management
applications, providing the data interface between clients and servers.
For more details about the RADview network management software, and for
detailed instructions on how to install, set up, and use RADview, contact your
local RAD partner.
Preconfiguration for Service Discovery

You can discover services via RADview, and view statistics for services and ports
in the RADview Performance Monitoring portal. This also allows you to ensure
that SLAs are being met. In order to do so, you need to perform the following:
• Configure service with parameters that enable RADview to recognize the
flows that correspond to the service, as follows:
 Configure Rx and Tx traffic flows with the same service ID.
 Assign the above Rx and Tx flows to the MEP corresponding to the
service.
Note The service name configuration is necessary only in the endpoint devices.
• Enable PM collection for the Rx and Tx flows, as well as for the corresponding
destination NE.
• All flows belonging to the same service End Point must use the same port.
• Only one S-tag should be used for the service.
• Run the RADview Discovery Service function (refer to the RADview online
help).
Discovery can be performed only on the user port (UNI). For more information,
refer to Performance Management in the Monitoring and Diagnostics chapter.
3-52 SNMP-Based Network Management ETX2

Note Multi-port E-Line services can't be discovered and statistics can't be collected on
the flows.
Working with Shelf View

Shelf View is an SNMP-based application with fully FCAPS-compliant element
management. It displays a dynamic graphic representation of the device panel(s),
providing an intuitive, user-friendly GUI. Shelf View includes port and/or card
interfaces and their operational and communication statuses.
Shelf View is distributed as an executable (*.exe) file. It can be run under
Windows 7 and Windows 8 with Java Runtime Environment 1.7.0 and above. The
application (and its online help) is available via RAD partners.
Working with Other SNMP-Based NMS

ETX2 can be integrated into third-party network management systems at the
following levels:
• Viewing device inventory and receiving traps
• 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)

3.9 Maintenance
The enclosure of the specially designed ETX203AX unit installed in a small cell
cabinet can become very hot. Therefore, it is recommended to power off the unit
and wait for it to cool down prior to servicing.
Hot surface! Do not touch! Contact may cause burn. Allow to cool before
servicing.
Warning
3.10 Turning Off the Unit

 To power off the unit:
• Remove the power cord from the power source.
3-54 Turning Off the Unit ETX2

Chapter 4
Service Provisioning
This chapter shows the data flow and configuration steps for services.
In order for services to be discovered using the RADview service discovery
function, refer to Preconfiguration for Service Discovery.
4.1 Service Entities

This section describes the managed elements that need to be configured during
service provisioning.
Service provisioning elements are as follows:
• Profiles
• Scheduling and shaping entities
• Physical ports (E1/T1/T3 (depending on product), Ethernet)
• Logical ports (LAG, logical MAC, PCS (for ETX203AM with an SHDSL or VDSL2
module, and ETX203AX with embedded SHDSL ports), and SVI)
• Forwarding entities (flow, bridge)
Profiles
Most packet processing features are defined by creating and applying various
profiles. Profiles comprise sets of attributes related to a specific service entity.
Profiles must be defined before other managed objects.
Table 4-1. Profile Types
Profile Type Applied to Description
L2CP Ethernet/logical MAC port, Defines actions for L2CP processing (drop, peer,
PCS flow tunnel, and tunnel with MAC swap)
Classifier Flow Defines criteria for flow classification
CoS mapping ETP/bridge flow/MultiCoS Defines method and values for mapping packet
flow (10.3 policer) attributes (P-bit, DSCP, IP precedence) to internal
CoS values
Color mapping Flow Defines method and values for mapping packet
attributes (P-bit, DSCP, IP precedence) to internal
color values
ETX-2 Service Entities 4-1

Chapter 4 Service Provisioning Installation and Operation Manual
Profile Type Applied to Description
Marking Flow Defines method of mapping internal CoS or packet

attributes (p-bit, DSCP, IP Precedence), and packet
color values into (S-Tag) P-bit and DEI
Policer, policer Ethernet port, flow Defines CIR, CBS, EIR, and EBS parameters
aggregate
Envelope policer Flow Defines policer attributes per rank, per MEF 10.3
Queue block Queue block within queue Defines queue and queue parameters. This
group includes defining all the queues forming the queue
block and defining per queue its parameters, such
as scheduling mode (strict, WFQ, BE), queue depth,
and queue WRED profile.
Queue group Ethernet/logical MAC Defines the group of queue blocks in a two-stage
port/PCS port hierarchy
Also sets the queue block profiles used and the
queue block shaper profile
Queue mapping Flow Defines method and values for mapping packet
attributes (P-bit, DSCP, IP precedence, CoS) to
internal priority queues
Shaper Queue, queue block Defines CIR and CBS
WRED Queue Defines yellow packet thresholds and drop

probabilities
Scheduling and Shaping Entities

ETX-2 schedules traffic using the following hierarchical scheduling entities:
Queue A lowest-level scheduling element. Its priority can be strict,

weight fair, or best effort. Queues have shaper and WRED
profiles assigned to them, as well as a configurable depth.
Queue block Also referred to as scheduling elements, or SEs. A mid-level

scheduling element that consists of several queues. Queue
blocks are created by associating queues with queue block
profiles. There are two levels of queue blocks. Queue
blocks may have shaper profiles assigned to them.
Queue Group A top-level scheduling element that consists of several

queue blocks. Queue groups are created by associating
queue group profiles to ports.
ETX-2 supports the following shaping tools:

• Dual token bucket shaper (CIR/EIR) (no EIR for ETX220A)
• Single token bucket shaper (CIR)
Congestion avoidance is per color:
Green Tail drop
4-2 Service Entities ETX-2

Installation and Operation Manual Chapter 4 Service Provisioning
Yellow WRED profile
Physical Ports
Ethernet ports serve as ingress (UNI) and egress (NNI) ports for Ethernet flows.
The following packet processing attributes are assigned to them:
• Tag Ethertype for identifying VLAN-tagged frames at ingress and setting
Ethertype value for VLAN editing (stack, swap) at egress
• L2CP profile for defining L2CP frame handling (discard, peer, tunnel, or tunnel
with MAC swap)
• Queue group profile for associating a port with a queue group
• Policer profile for broadcast/multicast traffic (BUM filter)
Logical Ports
Logical ports maintained by ETX-2 serve as internal aggregation or forwarding
points for Ethernet flows. The following logical ports exist:
Logical MAC Provides a logical port to access smart SFP ports (via GFP
ports)
Link Aggregation Provides link protection. LAGs have the same attributes as
Group (LAG) the physical ports that serve as their members.
PCS Provides a logical port to access SHDSL or VDSL2 ports
Service Virtual Binds flows to router interfaces

Interface (SVI)
Forwarding Entities
Several internal entities carry traffic and make forwarding and switching
decisions. These are:
• Flows – Traffic-forwarding interconnection elements
• Bridge
Flows
Flows are entities that interconnect two physical or logical ports. Flow processing
is performed as follows:
• Ingress traffic is mapped in flows using classification match criteria defined
via a classification profile.
• L2CP frames are handled per flow according to L2CP profile settings.
• User priority (P-bit, IP Precedence, DSCP) is mapped into internal queue
according to a queue mapping profile or assignment per flow.
• Packet attributes may map packets to the ingress color, which together with
the color-aware policer (if applied), sets the egress packet color. Packet color
may be used in the marking and congestion avoidance process.
ETX-2 Service Entities 4-3

Alternately, packet attributes (L2-L4) can be mapped to an internal CoS,

which maps to queues (1:1). This scheme is supported by certain
configuration scenarios.
• VLANs can be edited per flow by stacking (pushing), removing (popping), or
swapping (marking) tags on single or double-tagged packets. P-bit and DEI
values are either copied or set according to a marking profile (per packet
attributes or internal CoS).
• A single policer can be applied to a flow or a policer aggregate can be
assigned to a group of flows. Envelope policer is also supported and can be
assigned to a flow.
• A flow is mapped to a queue block or queue group associated with the egress
port.
Bridge
The bridge is a forwarding entity used by ETX-2 for delivering E-LAN and E-Tree
services in multipoint-to-multipoint topology and G.8032 ring protection. The
bridge uses SVIs to connect logical and physical ports.
The bridge is defined by bridge ports and a VLAN membership table that specifies
which bridge ports are members in a certain broadcast domain (VLAN). The bridge
supports up to two VLAN editing actions, on ingress and/or egress. The editing is
performed at the flow level.
Router
The router uses service virtual interfaces (SVIs) to connect to logical and physical
ports. The connection is always made by directing flows from a port to an SVI,
and then binding the SVI to a router interface.
Device management, as well as other L3 ‘modules’, such as 1588 (8265.1), TDM
PW (UDP/IP), and TWAMP, use the ETX-2 routing scheme.
4.2 E-LAN Service
Ethernet to Bridge
In Figure 4-1, the rectangles illustrate the data flow for user traffic from an
Ethernet port to a bridge port. The rounded rectangles indicate the features that
need to be configured, numbered according to the order of configuration.
Table 4-2 shows the configuration steps corresponding to the numbers.
Ingress Egress bridge

Classification Flow
Ethernet port port
5) Ethernet ports 2) Classification 3) Marking 1) Bridge ports
4) CoS mapping
6) Flows
Figure 4-1. E-LAN Traffic Data Flow – Ethernet to Bridge
4-4 E-LAN Service ETX-2

Table 4-2. E-LAN Traffic Configuration – Ethernet to Bridge
Sequence Step Commands Comments
1 Configuring the Bridge port

shutdown
2 Configuring a Classifier classifier-profile The classifier profile defines the

Profile match criteria for the flow.
3 Marking Profiles marking-profile Necessary only if a profile is needed

mark for non-default mapping of p-bit, IP
precedence, DSCP, or CoS
classifications to egress priority tags
4 CoS Mapping Profiles cos-map-profile Necessary only if a profile is needed

map for non-default mapping of user
priorities to CoS
5 Ethernet Ports name Necessary only if you need to define

auto-negotiation non-default configuration for the
egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
6 Configuring Flows classifier You must define the flow for the user
ingress-port traffic from the Ethernet port to the
bridge port.
egress-port
mark
reverse-direction
vlan-tag
shutdown
Bridge to Ethernet
In Figure 4-2, the rectangles illustrate the data flow for user traffic from a bridge
port to an Ethernet port. The rounded rectangles indicate the features that need
to be configured, numbered according to the order of configuration. Table 4-3
shows the configuration steps corresponding to the numbers.
Ingress bridge Queueing Queueing Egress

Classification Flow Shaping
port level 0 level 1 Ethernet port
1) Bridge ports 2) Classification 3) Marking 6) Queue blocks 5) Shaping 6) Queue blocks 8) Ethernet ports
4) CoS mapping 7) WRED
9) Flows
Figure 4-2. E-LAN Traffic Data Flow – Bridge to Ethernet
ETX-2 E-LAN Service 4-5

Table 4-3. E-LAN Traffic Configuration – Bridge to Ethernet
1 Configuring the Bridge port

shutdown

Profile match criteria for the flow.

4 CoS Mapping Profiles cos-map-profile Necessary only if a profile is needed

priorities to CoS
5 Configuring Shaper Profiles shaper-profile Necessary only if you need to define

bandwidth non-default bandwidth limits or
overhead compensation for the
compensation
outgoing traffic of the flow (via
attaching shaper profile to queue
group profile attached to egress port)
6 Configuring Queue Block queue-block-profile Necessary only if you need to define

Profile Parameters queue non-default queue configuration for
the flow, or the egress port
scheduling
depth
7 WRED Profiles wred-profile Necessary only if you need to define

color non-default WRED configuration for
the queue blocks

ingress or egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
ingress-port traffic from the bridge port to the
Ethernet port.
egress-port
policer
mark
vlan-tag
shutdown
4-6 E-LAN Service ETX-2

4.3 E-Line Service
User to Network
In Figure 4-3, the rectangles illustrate the data flow for Ethernet user traffic from
a user port to a network port. The rounded rectangles indicate the features that
Queueing Queueing
Ingress UNI Classification Flow Policing Shaping Egress NNI
level 0 level 1
9) Ethernet ports 1) Classification 2) Marking 4) Policing 6) Queue blocks 5) Shaping 6) Queue blocks 8) Queue groups
3) Queue mapping 7) WRED 9) Ethernet ports
10) Flows
Figure 4-3. Ethernet User Traffic Data Flow – User to Network
Table 4-4. Ethernet User Traffic Configuration – User to Network

Profile match criteria for the user-to-network flow.

for the user-to-network flow
3 Queue Mapping Profiles queue-map-profile Necessary only if a profile is needed

priorities to queues for the
user-to-network flow
4 Configuring Policer Profiles policer-profile Necessary only if you need to define

compensation
incoming traffic of the

compensation
outgoing traffic of the
user-to-network flow (via attaching
shaper profile to queue group profile
attached to egress port)

the user-to-network flow, or the
scheduling
egress port
depth
ETX-2 E-Line Service 4-7


the queue blocks
8 Queue Group Profiles queue-group-profile Necessary only if you need to define

queue-block non-default queue group
configuration for the egress port
name
profile
shaper

ingress or egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
ingress-port traffic from the user port to the
network port.
egress-port
policer
mark
vlan-tag
shutdown
Network to User
In Figure 4-4, the rectangles illustrate the data flow for Ethernet user traffic from
a network port to a user port. The rounded rectangles indicate the features that
Queueing
Ingress NNI Classification Flow Policing Shaping Egress UNI
level 0
9) Ethernet ports 1) Classification 2) Marking 4) Policing 6) Queue blocks 5) Shaping 8) Queue groups
3) Queue mapping 7) WRED 9) Ethernet ports
10) Flows
Figure 4-4. E-Line Traffic Data Flow – Network to User
4-8 E-Line Service ETX-2

Table 4-5. E-Line Traffic Configuration – Network to User

Profile match criteria for the network-to-user flow.

for the network-to-user flow

network-to-user flow

compensation

compensation
network-to-user flow (via attaching

the network-to-user flow
scheduling
depth

the queue blocks

name
profile
shaper
ETX-2 E-Line Service 4-9


egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
ingress-port traffic from the network port to the
user port.
egress-port
policer
mark
vlan-tag
shutdown
4.4 Smart SFP Service
Network to User
The following figure illustrates the data flow from a network port provisioned as
a TDM port via a smart SFP, to an Ethernet user port. Table 4-6 shows the
configuration steps corresponding to the figure callouts.
Figure 4-5. TDM User Traffic Data Flow – TDM Network to Ethernet User
4-10 Smart SFP Service ETX-2

Table 4-6. TDM User Traffic Configuration – TDM Network to Ethernet User
1 Smart SFPs smart-sfp You must provision the smart SFP for
type the network port.
shutdown
2 E1 Ports e1 Necessary only if non-default

name configuration is needed for the TDM
port
line-code
Note: The specific step is according to
line-type
the TDM port type.
rx-sensitivity
tx-clock-source
shutdown
T1 Ports t1
name
line-code
line-length
line-type
rx-sensitivity
tx-clock-source
shutdown
E3 Ports e3
name
tx-clock-source
shutdown
T3 Ports t3
name
line-length
line-type
shutdown
SDH/SONET Ports sdh-sonet

name
frame-type
threshold
tim-response
tx-clock-source
shutdown
3 GFP Ports gfp You must configure a GFP port, and

bind bind the TDM port to it.
fcs-payload
name
ETX-2 Smart SFP Service 4-11

4 Logical MAC Ports logical-mac You must configure a logical MAC port,
name and bind the GFP port to it. The logical
MAC port is used as the ingress port
bind
of the flow.
egress-mtu
queue-group
tag-ethernet-type
shutdown

Profile match criteria for the network-to-user flow.

for the network-to-user flow


compensation

the network-to-user flow
scheduling
depth

the queue blocks
ingress-port traffic from the network port (logical
MAC port) to the user port.
egress-port
policer
mark
vlan-tag
shutdown

12 Configuring Shaper shaper-profile Necessary only if you need to define

Profiles bandwidth non-default bandwidth limits or
compensation
network-to-user flow (via attaching

name
profile
shaper

egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
User to Network
The following figure illustrates the data flow from a user port provisioned as a
TDM port via a smart SFP, to an Ethernet network port. Table 4-7 shows the
configuration steps corresponding to the figure callouts.
Figure 4-6. TDM User Traffic Data Flow – TDM User to Ethernet Network

Table 4-7. TDM User Traffic Configuration – TDM User to Ethernet Network User to Network
1 Smart SFPs smart-sfp You must provision the smart SFP for
type the user port.
shutdown
2 E1 Ports e1 Necessary only if non-default

name configuration is needed for the TDM
port
line-code
Note: The specific step is according to
line-type
the TDM port type.
rx-sensitivity
tx-clock-source
shutdown
T1 Ports t1
name
line-code
line-length
line-type
rx-sensitivity
tx-clock-source
shutdown
E3 Ports e3
name
tx-clock-source
shutdown
T3 Ports t3
name
line-length
line-type
shutdown
SDH/SONET Ports sdh-sonet

name
frame-type
threshold
tim-response
tx-clock-source
shutdown
3 GFP Ports gfp You must configure a GFP port, and

bind bind the TDM port to it.
fcs-payload
name

4 Logical MAC Ports logical-mac You must configure a logical MAC port,
name and bind the GFP port to it. The logical
MAC port is used as the ingress port
bind
of the flow.
egress-mtu
queue-group
tag-ethernet-type
shutdown

Profile match criteria for the user-to-network flow.

for the user-to-network flow


compensation

the user-to-network flow, or the
scheduling
egress port
depth

the queue blocks
ingress-port traffic from the user port to the
network port.
egress-port
policer
mark
vlan-tag
shutdown

12 Configuring Shaper shaper-profile Necessary only if you need to define

Profiles bandwidth non-default bandwidth limits or
compensation
user-to-network flow (via attaching

name
profile
shaper

egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
4.5 Service Summary

You can display the associations between service names and their associated
flows/MEPs.
Benefits
Viewing the entities associated with service names is useful for service
administration, and to ensure correct discovery of service-related entities by
network management systems.
If you have defined service names for flows, you can display the flows and
corresponding MEPs associated with the service names.
Viewing Service Summary

You can view a list of defined service names, as well as information about the
associated flows and MEPs.
4-16 Service Summary ETX-2

 To view the service information:

• In the CLI, go to the config>service context, and enter one of the following:
show status list Display a list of all defined service names.
show status name For specific service name, display summary information of
<name-string> associated flows/MEPs.
summary
show status name For specific service name, display details of associated
<name-string> flows/MEPs.
details
Examples
 To view list of defined service names:
ETX-2# configure service
ETX-2>config>service# show status list
Name : s1
Name : s2
 To view summary information of flows/MEPs associated with service:

ETX-2>config>service# show status name s1 summary
Flows
-----------------------------------------------------------------------------
Name Admin Oper Egress Port MEP
-----------------------------------------------------------------------------
S.29.1_1_1_s1 Up Down ETH 6 101
S.29.1_1_s1 Up Down ETH 1 101
OAM CFM MEPs

-----------------------------------------------------------------------------
MD : 1 MA : 1
MD Level : 6
MD Name : ---
MA Name : 1
MEPs
-----------------------------------------------------------------------------
ID Status Defects Service Pbit RMEPs OK/Total
-----------------------------------------------------------------------
101 up No 7 0/1
 To view details of flows/MEPs associated with service:

ETX-2>config>service# show status name s1 details
Flows
---------------------------------------------------------------
Name : S.29.1_1_1_s1
Admin : Up
ETX-2 Service Summary 4-17

Test Status : Off

Classifier Profile : S.29.1_s1_1
Ingress Port : Ethernet 1
Egress Port : Ethernet 6
Name : S.29.1_1_s1
Admin : Up
Test Status : Off
Classifier Profile : S.29_s1_1
Egress Port : Ethernet 1
OAM CFM MEPs

---------------------------------------------------------------
MD : 1 MA : 1
MD Level : 6
MD Name : ---
MA Name : 1
MEPs
---------------------------------------------------------------
ID : 101
Status : up
Defects : No
Remote MEP Remote MEP

---------------------------------------------------------------
201 Fail
4-18 Service Summary ETX-2

Chapter 5
Cards and Ports
This chapter describes card and port-related features:
Note
Ports are referenced generally as [<slot>/]<port>[/<tributary>], with the
following conditions according to product:
• ETX203AM – <slot>/<port> or <slot>/<port>/<tributary>:
• <slot> = 1 for modular ports
• <slot> = 0 for user Ethernet ports
• <tributary> is required only for smart SFP E1/T1/E3/T3/SDH/SONET ports,
and is always set to 1.
• ETX203AX – <port> or <port>/<tributary>:
• ETX205A – <port> or <port>/<tributary>:
• ETX220A – <slot>/<port> or <slot>/<port>/<tributary>:
• <slot> = 0: All timing interfaces and ETH MNG port
• <slot> = 1: Lower row of GbE ports (1/1–1/10, left to right)
• <slot> = 2: Higher row of GbE ports (2/1–2/10, left to right)
• <slot> = 3: 10GbE ports ( 3/1 , 3/2 , leftmost 10GbE pair, left to right)
• <slot> = 4: 10GbE ports (4/1 , 4/2 , rightmost 10GbE pair, left to right)
5.1 Cards
This section describes how to configure the module type (card type) of the
network uplink.
Applicable Products
This feature is applicable to the ETX203AM modular option.
ETX-2 Cards 5-1

Chapter 5 Cards and Ports Installation and Operation Manual
Benefits
The ability to preprovision the module type before actually inserting the module
provides more flexibility.
The ETX-2 module can contain ports of type GbE, E1, T1, T3, VDSL2, or SHDSL.
You can preprovision the module type before physically inserting the module. The
configured module type must match the actual module installed, for correct
operation.
When ETX-2 starts up, it verifies that the configured module type matches the
module that is installed. If they do not match, the card_mismatch alarm is sent.
The ETX-2 module is defined as slot 1; therefore, the ports on the module are
referenced with slot 1. The device ports that are not on the module are
referenced with slot 0.
Note The ETX-2 module is not hot swappable; it can be removed/replaced only when
ETX-2 is powered off.
Factory Defaults
By default, the module type is set according to the module type that is actually
installed.
Configuring Module
Note You can display the module type from the device level by typing
show cards-summary.
 To configure the module:

1. Navigate to configure slot 1.
The config>slot(1)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
5-2 Cards ETX-2

Installation and Operation Manual Chapter 5 Cards and Ports
Configuring the module type as one of card-type eth 1g-2-full Type no card-type to set the module type
the following: card-type tdm {e1-t1-4-ch | e1-t1-8-ch} to null.
• Ethernet GbE card-type tdm {t3-1-ch | t3-2-ch} Notes:
• E1/T1 with four channels card-type shdsl {shdsl-4w | shdsl-8w} • If the configured module type does not
• E1/T1 with eight channels match the actual installed module, the
card-type vdsl2 {vdsl2-4p-pots | vdsl2-4p-
card_mismatch alarm is sent. This
• T3 with one channel isdn}
includes the case of changing the
• T3 with two channels module type to null while a module is
• SHDSL with 4-wire option installed.
• SHDSL with 8-wire option • When the module type is changed to
• VDSL2 with 8-wire option null, ETX-2 automatically deletes all the
interfaces that exist in the module.
• You are not allowed to change the
module type in the following cases:
• An active service is defined over one
or more of the module interfaces.
• One or more of the module
interfaces is being used as a timing
reference (e.g. domain clock source).
Administratively enabling the module no shutdown Type shutdown to administratively disable

interfaces the module interfaces.
Resetting module SW reset Supported for VDSL only
Displaying module status show status
5.2 DS1 (E1/T1) Ports

The E1/T1 ports can be configured to work as E1 ports or T1 ports, in the ds1
(digital signal) level.
Applicable Products
This feature is applicable to following:
• ETX203AM with an E1/T1 module:
 The E1/T1 ports are bound to VCGs via GFP ports and logical MAC ports.
 The port numbers contain slot numbers.
• ETX205A with built-in E1/T1 ports – The E1/T1 ports are associated with
pseudowire (PW).
Benefits
There is no need to choose E1 or T1 when ordering the unit.
ETX-2 DS1 (E1/T1) Ports 5-3

All ports must work in the same mode; therefore, configuring any port sets all
ports to the same mode.
Before changing the E1/T1 port mode, any corresponding GFP ports/VCGs/logical
MAC ports/pseudowires/PW cross connects must be deleted. After changing the
mode, ETX-2 must be restarted.
Factory Defaults
By default, the E1/T1 ports are set to E1 mode.
Configuring E1/T1 Ports

 To configure E1/T1 ports:
1. At the config>port# prompt, type:
ds1 [<slot>/]<port>
The config>port>ds1([<slot>/]<port>)# prompt is displayed.
2. To configure the E1/T1 port to E1 or T1 mode, type:
frame-type { e1 | t1 }
5.3 E1 Ports
The European Conference of Postal and Telecommunications Administrations
(CEPT) standardized the E-Carrier system, which was then adopted by the
International Union Telecommunication Standardization sector (ITU-T), and is
used in almost all countries outside the USA, Canada, and Japan.
The most commonly used versions are E1 and E3. E1 circuits are very common in
most telephone exchanges and used to connect medium and large companies to
remote exchanges. In many cases, E1 connects exchanges with each other.
Applicable Products
E1 ports are applicable to the ETX-2 products as follows:
• All ETX-2 products:
 Smart SFP E1 ports are available when smart SFPs such as MiRICi-E1 or
MiTOP-E1 are provisioned (see Smart SFPs).
 Smart SFP E1 ports do not support encapsulation via VCG.
 Smart SFP E1 ports are referenced as [<slot>/]<port>/<tributary>:
 <slot> is relevant to ETX203AM and ETX220A.
 <tributary> is always set to 1.
5-4 E1 Ports ETX-2

• ETX203AX with a built-in E1 port (numbered 1):

 Built-in E1 port supports TDM pseudowire.
 Built-in E1 port is referenced as <port>.
 E1 port is supported in the following operation modes:
 GFP – single VCG
 HDLC – single group over unframed E1
 Modular E1/T1 ports can be configured to E1 mode (see DS1 (E1/T1)
Ports). The default mode is E1.
 Modular E1 ports support encapsulation via VCG (see VCGs).
 Modular E1 ports are referenced as <slot>/<port>.
• ETX205A with built-in E1/T1 ports:
 Built-in E1/T1 ports can be configured to E1 mode (see DS1 (E1/T1)
 Built-in E1 ports support TDM pseudowire.
 Built-in E1 ports are referenced as <port>.
Standards
CCITT G.732
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
E1 lines are high-speed dedicated lines that enable large volume usage.
An E1 link operates over a twisted pair of cables. A nominal 3-volt peak signal is
encoded with pulses using a method that avoids long periods without polarity
changes. The line data rate is 2.048 Mbps at full duplex, which means 2.048 Mbps
downstream and 2.048 Mbps upstream. The E1 signal splits into 32 timeslots
each of which is allocated 8 bits. Each timeslot sends and receives an 8-bit
sample 8000 times per second (8 x 8000 x 32 = 2,048,000), which is ideal for
voice telephone calls where the voice is sampled into an 8-bit number at that
data rate and restored at the other end. The timeslots are numbered from 0 to
31.
Factory Defaults
By default, no smart SFP E1 ports exist.
ETX-2 E1 Ports 5-5

By default, built-in/modular E1/T1 ports are set to E1 mode and have the
following configuration.
Parameter Value Remarks
interface-type balanced Line impedance type
line-code hdb3 Transmission line code
line-interval-threshold es 80 Threshold to trigger line ES

Note: Built-in E1 ports only
line-type Unframed Port framing mode
name E1 <slot>/<port> DS1 <port>
path-interval-threshold cv 0 es 80 ses 10 sefs 0 css 0 uas 10 Note: Built-in E1 ports only
pm-enable no pm-enable Performance monitoring is

disabled
rx-sensitivity short-haul Attenuation level of

received signal
source-clock-quality stratum1 Note: Built-in E1 ports only
trail-mode terminated No forwarding of E1 port

alarms toward TDM line
Note: Built-in E1 ports only
tx-clock-source loopback Note: Built-in E1 ports only
shutdown shutdown Administratively disabled
If the line type for built-in E1/T1 ports is changed to g732s or g732s-crc, the
default configuration of the built-in E1 port is the same as shown above, with the
addition of the following parameters.
cas-oos-pattern space
cas-oos-codes space 0x01 mark 0x0d
Configuring E1 Ports
Configuring Built-in E1 Ports
 To configure E1 ports:
1. Navigate to configure port e1 <port>.
e1 <port>/<tributary>
The prompt config>port>e1(<port>/<tributary>)# is displayed.
5-6 E1 Ports ETX-2

Specifying out-of-service cas-oos-codes space <space-code> mark • Space signaling code

indication to transmit for E1 port <mark-code> allowed range: 0x0–0xf
with CAS signaling • Mark signaling code
allowed range: 0x0–0xf
Notes:
• This command is relevant
only with line type g732s
or g732s-crc.
• When R bits and L bits are
used to indicate E1 CAS
faults on the remote side,
the OOS code sent to the
E1 CAS interface is the
default (0xFF), rather than
the actual OOS code.
Specifying transmission sequence cas-oos-pattern {space | mark | Note: This command is

for out-of-service indication for space-mark} relevant only with line type
E1 port with CAS signaling g732s or g732s-crc.
Specifying code transmitted to fill idle-code <idle-code-val> Possible values: 0x00–0xFF

idle (unused) timeslots in the E1 (default 0x7E)
frames CAS idle-code has fixed value
of 0x5 (0101).
Specifying E1 port impedance interface-type { balanced | unbalanced } Specifying impedance of E1

port:
• balanced – 120Ω balanced
interface
• unbalanced
Defining the transmission line line-code { hdb3 | ami } • HDB3 – Referred to as

code High Density Bipolar of
order 3 code, it is a
telecommunication line
code based on AMI and
used in E1 lines. It is
similar to B8ZS used in T1
lines.
• AMI – Referred to as
Alternate Mark Inversion
because a 1 is referred to
as a mark and a 0 as a
space.
Specifying threshold at which to line-interval-threshold es <es-value >

trigger threshold crossing alert
for line ES (errored seconds)
ETX-2 E1 Ports 5-7

Specifying the framing mode of line-type { unframed | g732n | g732n-crc | • unframed – no framing;
the port g732s | g732s-crc } in ETX203AX with
E1oPHDH, unframed line
type is relevant only for E1
port with HDLC
encapsulation
• g732n – G.732N framing
with CRC disabled
• g732n-crc – G.732N
framing with CRC enabled;
in ETX203AX with
E1oPHDH, g732n-crc line
type is relevant only for E1
port with GFP
encapsulation
• g732s – G.732S framing
(CAS) with CRC disabled
• g732s-crc – G.732S
framing (CAS) with CRC
enabled.
Running loopback test on E1 port loopback {local | remote} • local – returns the
[duration <seconds>] transmitted data at the
physical layer to the
receiving path
• remote – returns the
received data at the
transmitting path
Remote loopback test is
currently not supported
for ETX203AM EoPDH
ports.
• duration – specifies the
duration of the loopback
(in seconds).
Possible values: 1 to 3600
If duration is not
specified, the loopback
test runs forever, until
stopped.
Use no loopback to disable
the loopback test.
Assigning a name to the port name <string>
5-8 E1 Ports ETX-2

Defining the value to be out-of-service <oos> Possible values: 0x00–0xFF

transmitted if the corresponding (default 0xFF)
PW is out of service If the corresponding PW is out
of service, ETX-2 transmits
the configured value on a
time slot that is assigned to
the PW toward the TDM side
(relevant only for framed E1
ports).
Specifying thresholds at which to path-interval-threshold cv <cv-value>

trigger threshold crossing alert es <es-value> ses <ses-value>
for path coding violation (CV), ES sefs <sefs-es-value> css <css-value>
(errored seconds), SES (severely uas <uas-value>
errored seconds), SEFS (severely
errored framing seconds), CSS
(controlled slip seconds), UAS
(unavailable seconds)
Specifying if performance pm-enable

reporting is enabled for the port
Specifying the attenuation level rx-sensitivity {short-haul | long-haul} • short-haul – low

of the received signal, sensitivity
compensated for by the interface • long-haul – high sensitivity
receive path
Specifying the port clock quality source-clock-quality {stratum1 | stratum2 | Clock quality used in adaptive
stratum3 | stratum3e | stratum4} clock recovery set according
to parameter specified:
• stratum1 – PRC G.811
• stratum2 – Type II G.812
• stratum3 – Type IV G.812
• stratum3e – Type III G.812
• stratum4 – Free running
Defining whether the E1 port trail-mode { extended | terminated } extended – ETX-2 forwards
alarms are forwarded toward the the E1 port alarms from the
TDM line PW toward the TDM line.
terminated – ETX-2 does not
forward the E1 port alarms
toward the TDM line.
ETX-2 E1 Ports 5-9

Selecting the transmit clock tx-clock-source {loopback | internal | • loopback – clock retrieved
source domain <number> | pw <number>} from the port's incoming
(Rx) data
• internal – clock provided
by internal oscillator
• domain – clock provided
by clock domain, if device
has timing option
• pw – clock provided by PW
bundle
Note: After changing
tx-clock-source, you are
required to reset the device.
Administratively disabling or shutdown Type no shutdown to

enabling the port administratively enable the
port.
Displaying list of interfaces bound show bind Displays ports bound to E1

to E1 port (GFP or HDLC)
Displaying loopback test status show loopback
Displaying E1 port operational show status

status
Displaying the port statistics show statistics current E1 current and interval
show statistics interval <interval-num> statistics for E1 unframed and
E1 framed with CRC.
show statistics all-intervals
show statistics all
Clearing the statistics clear-statistics
Configuring Modular E1 Ports
1. If the module type is not E1/T1, power off ETX-2, insert the E1/T1 module,
and then power on ETX-2.
2. Provision the module type as E1/T1 (see Configuring Module).
3. Configure the port to E1 mode (see Configuring E1/T1 Ports).
e1 [<slot>/]<port>/<tributary>
The prompt config>port>e1([<slot>/]<port>/<tributary>)# is displayed.
Specifying if E1 interface is interface-type { balanced | unbalanced }

balanced or unbalanced
5-10 E1 Ports ETX-2

Defining the transmission line line-code { hdb3 | ami } • HDB3 – Referred to as

code High Density Bipolar of
order 3 code, it is a
telecommunication line
code based on AMI and
used in E1 lines. It is
similar to B8ZS used in T1
lines.
• AMI – Referred to as
Alternate Mark Inversion
because a 1 is referred to
as a mark and a 0 as a
space.
Note: Only HDB3 can be
configured for modular E1
ports.
Specifying the framing mode of line-type { unframed | g732n | g732n-crc | • unframed – no framing
the port g732s | g732s-crc } • g732n – G.732N framing
with CRC disabled
• g732n-crc – G.732N
framing with CRC enabled
• g732s – G.732S framing
(CAS) with CRC disabled
• g732s-crc – G.732S
framing (CAS) with CRC
enabled
Note: Only g732n-crc can be
configured for modular E1
ports.
ETX-2 E1 Ports 5-11

Running loopback test on E1 port loopback {local | remote} • local – returns the
[duration <seconds>] transmitted data at the
receiving path
• remote – returns the
received data at the
transmitting path.
Currently not supported.
• duration – specifies the
duration of the loopback
(in seconds).
If duration is not
specified, the loopback
test runs forever, until
stopped.
Use no loopback to disable
the loopback test.

reporting is enabled for the port
Specifying the attenuation level rx-sensitivity {short-haul | long-haul} • short-haul – low

of the received signal, sensitivity
compensated for by the interface • long-haul – high sensitivity
receive path
Administratively disabling or shutdown Type no shutdown to

enabling the port administratively enable the
port.
Displaying list of interfaces bound show bind

to port
Displaying the port status show status
Displaying the port statistics show statistics current

show statistics interval <interval-num>
show statistics all
Configuring Smart SFP E1 Ports
 To configure smart SFP E1 ports:

1. Provision a smart SFP port with type MiRICi-E1 or MiTOP-E1 (see Smart SFPs).
5-12 E1 Ports ETX-2

2. Insert the MiRICi-E1/MiTOP-E1 into the Ethernet port.
Note Initialize the database of the MiTOP before inserting it into the device. Refer to
Setting the Switches in the Installation and Setup chapter of the MiTOP E1T1
Installation and Operation manual.

4. Enter all necessary commands according to the tasks listed below, and the
type of smart SFP.
Task Command Comments MiRICi MiTOP
Defining the line-code { hdb3 | ami } • HDB3 – Referred to as High Density  

transmission line code Bipolar of order 3 code, it is a
telecommunication line code based on
AMI and used in E1 lines. It is similar to
B8ZS used in T1 lines.
• AMI – Referred to as Alternate Mark
Inversion because a 1 is referred to as
a mark and a 0 as a space.
Specifying the framing line-type { unframed | g732n | • unframed – no framing  

mode of the port g732n-crc | g732s | g732s-crc } • g732n – G.732N framing with CRC
disabled
• g732n-crc – G.732N framing with CRC
enabled
• g732s – G.732S framing (CAS) with
CRC disabled
• g732s-crc – G.732S framing (CAS) with
CRC enabled
Notes:
• For MiRICi, only g732n and g732n-crc
are relevant.
• For MiRICi-E1, only g732n-crc is
relevant.
• For MiTOP, only g732n, g732n-crc, and
unframed are relevant.
• Selecting incorrect line-type generates
an “Unsupported line type” error.
ETX-2 E1 Ports 5-13

Running loopback test loopback {local | remote} • local – returns the transmitted data at  
on E1 port [duration <seconds>] the physical layer to the receiving path
• remote – returns the received data at
the physical layer to the transmitting
path
• duration – specifies the duration of the
loopback (in seconds).
If duration is not specified, the
loopback test runs forever, until
stopped.
Use no loopback to disable the loopback.
test.
Assigning a name to the name <string>  

port
Specifying if pm-enable  
performance reporting
is enabled for the port
Specifying the rx-sensitivity {short-haul | • short-haul – low sensitivity  

attenuation level of the long-haul} • long-haul – high sensitivity
received signal,
compensated for by the
interface receive path
Specifying the port source-clock-quality {stratum1 | Clock quality used in adaptive clock × 
clock quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
stratum4} specified:
Selecting the transmit tx-clock-source {loopback | • loopback – Rx clock; clock retrieved  

clock source internal | domain <number> | from the port's incoming (Rx) data
pw <number>} • internal – clock provided by internal
oscillator
• domain – clock provided by clock
domain, if device has timing option (for
all devices, except ETX203AM).
For ETX203AM, domain clock
configuration selects the NTR clock as
the Tx clock source.
• pw – clock provided by PW bundle
Note: The domain and pw options are
available only for MiTOP.
5-14 E1 Ports ETX-2

Administratively shutdown Type no shutdown to administratively  

disabling or enabling enable the port.
the port Note: Following shutdown and then no
shutdown of Smart SFP port, you must
perform shutdown and then no shutdown
of PW.
Displaying list of show bind  

interfaces bound to
port
Displaying loopback test show loopback  

status
Displaying the port show status  

status
Displaying the port show statistics current  

statistics show statistics interval
<interval-num>
show statistics all
Clearing the statistics clear-statistics  
5.4 E3 Ports
Groups of E1 circuits are bundled into higher-capacity E3 links, which are mainly
used between exchanges, operators, and/or countries, and have a transmission
speed of 34.368 Mbps.
E3 ports are available when smart SFPs such as MiRICi-E3 or MiTOP-E3 are
provisioned (see Smart SFPs).
Applicable Products
This feature is applicable to all ETX-2 products. Smart SFP E3 ports are referenced
as [<slot>/]<port>/<tributary>:
• <slot> is relevant to ETX203AM and ETX220A.
• <tributary> is always set to 1.
Standards
ITU-T G.703
ITU-T G.704
ITU-T G.823
ETX-2 E3 Ports 5-15

Benefits
E3 lines provide high-capacity circuits.
Each E3 signal has 16 E1 channels, and each channel transmits at 2.048 Mbps. E3
links use all eight bits of a channel.
Factory Defaults
By default, no E3 ports exist.
Configuring E3 Ports
1. Provision a smart SFP such as MiRICi-E3 or MiTOP-E3 and insert it into an
Ethernet port (see Smart SFPs).
Setting the Switches in the Installation and Setup chapter of the MiTOP E1T1
Installation and Operation manual.

type of smart SFP.
Specifying the framing line-type { framed | unframed } • framed – framing  

mode of the port • unframed – no framing
5-16 E3 Ports ETX-2

Running loopback test loopback {local | remote } • local – returns the transmitted  
on E3 port [start <seconds> ] data at the physical layer to the
[duration <seconds>] receiving path
• remote – returns the received data
at the physical layer to the
transmitting path
• start – specifies the time (in
seconds) until the loopback starts.
• duration – specifies the duration
of the loopback (in seconds).
Possilbe values: 1 to 3600
stopped.
Use no loopback to disable the
loopback test.
Assigning a name to name <string>  

the port
Specifying the port source-clock-quality {stratum1 | Clock quality used in adaptive clock × 
clock quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
Selecting the transmit tx-clock-source {loopback | internal | • loopback – clock retrieved from  
clock source pw <number>} the port's incoming (Rx) data
• internal – clock provided by
internal oscillator
Note: The pw option is available only
for MiTOP.
Administratively shutdown Type no shutdown to administratively  

the port

interfaces bound to
port
ETX-2 E3 Ports 5-17

Displaying loopback show loopback  

test status
Displaying the port show status  

status
Displaying the port show statistics current  

statistics show statistics interval
<interval-num>
show statistics all
5.5 Ethernet Ports
Applicable Products
This feature is applicable to all ETX-2 products, with the following conditions:
• Port types and configurations differ according to product, and this is
indicated where relevant; additionally the following apply:
 Ethernet FE/GbE ports are applicable to all products.
 Ethernet 10GbE ports are applicable to ETX220A.
• SFP/RJ-45 combo ports are applicable to ETX205A or ETX203AM network
ports when GbE module is inserted.
• <slot> is applicable to ETX203AM and ETX220A.
• Maximum advertised capability and speed/duplex parameters differ according
to product; this is indicated where relevant.
• Clock-related parameters are applicable to ETX205A or ETX220A with timing
options.
Options
ETX203AM ordered with the network GbE option has two fiber optic / copper
(combo) Gigabit Ethernet network ports. Regardless of the network port option,
the device has four fixed fiber optic or copper Fast/Gigabit Ethernet ports that act
as user ports. The first fixed port can be configured to act as a network port if no
module is inserted.
ETX203AX has two fiber optic or copper Fast or Gigabit Ethernet network ports
and up to four fiber optic or copper Fast or Gigabit Ethernet user ports.
5-18 Ethernet Ports ETX-2

ETX203AX-E1 has one E1 uplink, one fiber optic Gigabit Ethernet network port,
and four Gigabit Ethernet user ports (two copper and two fiber optic).
ETX203AX-DSL has an 8-wire DSL uplink and one copper Gigabit Ethernet user
port.
ETX205A has two network ports and up to four user ports that are SFP/UTP
combo ports. If ETX205A is ordered with a PM controller (PMC) option, it has up
to two user ports, as the last two user ports are used as internal ports to
interconnect with the integrated x86 processor.
ETX220A has two, three, or four 10GbE ports that consist of two network ports
and two optional user ports. The device also has 0, 10, or 20 GbE user ports.
Numbering
The following table shows how to refer to the ports when configuring them with
CLI commands.
Table 5-1. Ethernet Port Reference
Port Unit CLI
Port Number [Slot/]Port Number
ETX203AM
I/O 1 1/1
I/O 2 1/2
User 3 0/3
User 4 0/4
User 5 0/5
User 6 0/6
MNG-ETH 0/101
ETX203AX or ETX205A
Net or E1 1 1
Net/User 2 2
User 3 3
User 4 4
User 5 5
User 6 6
MNG-ETH 101
ETX203AX-DSL
User 1 1
MNG-ETH 101
SHDSL 1 1
ETX-2 Ethernet Ports 5-19

Port Unit CLI
Port Number [Slot/]Port Number
SHDSL 2 2
SHDSL 3 3
SHDSL 4 4
ETX220A
10GbE [User] 1 3/1
10GbE [User] 2 3/2
10GbE [Network] 3 4/1
10GbE [Net/User] 4 4/2
1000Fx (lower row, left to right) 1–10 1/1, 1/2, …, 1/10

[1/1, 1/2: Net/User]
[1/3…1/10: User]
1000Fx (upper row, left to right) 1–10 2/1, 2/1, …, 2/10

[User]
MNG-ETH 0/101
Note For ETX205A with PMC option, user ports 5 and 6 are not available.
MAC Addresses
In older hardware versions, ETX-2 has two MAC addresses: One is assigned to
network ports and the Ethernet management port, and one is assigned to the
user ports. The MAC clients in the device (e.g. router interfaces, MEPs, etc.)
inherit their MAC addresses from the relevant port.
In newer hardware versions, ETX-2 has multiple MAC addresses. Each of the
following ports is assigned a different MAC address:
• Two network ports (10GbE for ETX220A)
• Four user ports (ETX203AM, ETX203AX, and ETX205A)
• Up to two 10GbE user ports (ETX220A)
• Twenty GbE user ports (ETX220A)
• Ethernet management port
You can view the MAC address assigned to an Ethernet port via show status (see
Viewing Ethernet Port Status). For information on which MAC address is used by a
particular feature, refer to the relevant section in this manual.
Ethertype
Ethertype configured per-port is used for identification of VLAN-tagged frames at
ingress and Ethertype stacking at egress. This refers to the outer VLAN only. The
outer VLAN of an incoming packet must match the configured Ethertype of the
port in order to be considered a VLAN-tagged frame (otherwise frame is

considered untagged or dropped). Refer to the Ethertype section in the Traffic

Processing chapter for details.
Layer-2 Control Protocol (L2CP) Processing

You can configure L2CP profiles (for details, refer to Layer-2 Control Protocol
(L2CP) Processing in the Traffic Processing chapter), and then assign relevant
L2CP profiles to the Ethernet ports (see below) and/or to flows (refer to
Configuring Flows in the Traffic Processing chapter). You can also display the
L2CP port statistics for an Ethernet port associated with an L2CP profile that is
configured with tunneling and MAC swap (see Displaying Layer-2 Control
Processing Statistics).
Note An L2CP profile that is attached to a port or flow can be modified or replaced; it
cannot be deleted.
ETX-2 supports Layer-2 Protocol Tunneling (L2PT) – L2CP tunneling with MAC
swap, which means that L2CP packets can be forwarded over networks that are
not transparent to L2CP.
L2PT is supported at the port level and applies for PTP flows, as well as for
bridged traffic.
• ETX-2 supports multiple network ports with L2PT functionality for both PTP
and Bridge applications.
• Any port configured as NNI is L2PT Network, by default.
• Any other port can be configured to be L2PT Network (default ‘no’).
• Any port assigned with an L2CP profile with MAC swap, including port 1, can
function as an L2PT user port.
You can bind an L2CP profile configured with L2CP MAC swap to a user port; it
cannot be bound to a flow. A port assigned with an L2PT profile expects “native”
L2CP frames. MAC swap is performed toward the relevant network port or user
port that is configured for use as L2PT network ports.
Silent Start
Network operators use both point-to-point and point-to-multipoint Optical
Access Networks (OANs), depending on the application. For example, a Passive
Optical Network (PON) is a point-to-multipoint OAN. One of the major challenges
to operating and maintaining such OANs securely is that misconnecting a point-
to-point Optical Network Terminal (ONT) or Ethernet equipment to a branch of a
PON can cause a service outage in the PON system. In order to address this issue,
a Silent Start function is introduced in all types of ONTs, which inhibits an ONT
transmitter's power at startup until the receiver recognizes consistent incoming
data. On recovery of "understandable" data by the receiver, the transmitter is
enabled to enter a handshaking process with the Optical Line Terminal (OLT).
Optical Network Units (ONUs) transmit in assigned time slots to avoid disturbing
each other over the shard fiber, as a non-GPON device transmitting continuously
is likely to bring down a GPON segment.
Ethernet equipment can also be connected by mistake to a PON network and
bring down the PON segment, to address this the ETX also supports a silent start

functionality which once enabled would allow optical Tx only once a valid Ethernet
signal is received.
Figure 5-1. Passive Optical Network (PON)
ETX-2 supports Silent Start functionality for the following ports:

• Both 1GbE and 10GbE ports
• Optical Ethernet port only
• Ports configured to Autonegotiation disabled (1GbE ports):
 Sanity prevents user from enabling Silent Start if Autoneg is enabled.
 Sanity prevents user from enabling Autoneg if Silent Start is enabled.
When Silent Start is enabled, Rx optical power down detection at the optical
transceiver (no ‘Signal Detect’) leads to Tx power shutdown (laser shutdown).
• Signal Detect down brings down Tx power and restarts the Silent Start ‘ETH
search’ functionality.
When Silent Start is enabled, optical Tx power becomes enabled when all the
following conditions apply:
• Rx optical power is detected.
• Ethernet level synchronization is detected (PCS, PMD level).
A Silent Start alarm is issued if Silent Start In Progress state lasts for at least one
minute.

Figure 5-2. Silent Start
Factory Defaults
By default, the non-management Ethernet ports have the following configuration.
Parameter Description Default Value
auto-negotiation Enable or disable auto-negotiation auto-negotiation

Note: Not relevant to 10GbE ports
classification-key Classification key legacy
dhcp-trust Trust server DHCP packets no dhcp-trust (i.e. trust client

DHCP packets)
efm Enable or disable OAM EFM no efm
egress-mtu Packet size 1790
functional-mode Note: Relevant to the following network for all relevant ports
ports: except ETX220A ports 1/1
• ETX203AM – Second modular and 1/2, where the default is
GbE port if GbE module is user
inserted, or first fixed port
(port 0/3) if there is no
module
• ETX203AX or ETX205A –
Second network interface
• ETX220A – Second 10GbE
network interface (port 4/2)
and first two GbE interfaces
on slot 1 (ports 1/1 and 1/2)
l2cp L2CP profile L2cpDefaultProfile

lldp 802.1-management-vlan-id LLDP: no transmission of IEEE no

802.1 management VLAN ID 802.1-management-vlan-id
lldp customer-bridge-mode LLDP: no customer bridge mode no customer-bridge-mo de
lldp nearest-bridge-mode LLDP: no nearest bridge mode no nearest-bridge-mode
lldp non-tpmr-bridge-mode LLDP: no non-TPMR bridge mode no non-tpmr-bridge-mode
max-capability Maximum advertised capability 1000-full-duplex

Note: Not relevant to 10GbE ports
max-ql Maximum quality level of clock prc

source
name Port name ETH [<slot>/]<port-number>
policer Policer profile no policer
queue-group Queue group profile DefaultQueueGroup
shutdown Administrative status no shutdown
silent-start Silent start functionality no silent-start
tag-ethernet-type Ethernet tag protocol identifier 0x8100
tx-ssm Transmit SSM no tx-ssm
Configuring Ethernet Port Parameters
Note If a smart SFP has been provisioned, the Ethernet port parameters are not
accessible for configuration.
 To configure the Ethernet port parameters:

1. Navigate to configure port ethernet [<slot>/]<port-num> to select the
Ethernet port to configure.
The config>port>eth([<slot>/]<port-num>)# prompt is displayed.
Note The only parameter that can be configured for the management Ethernet port is
PM collection. To configure the management Ethernet port, navigate to configure
port mng-ethernet.

Enabling autonegotiation for FE/GbE auto-negotiation [{sfp | rj45}] Entering no auto-negotiation disables
port autonegotiation.
auto-negotiation can be enabled only if
silent-start is disabled (sanity check).
Note: Use sfp or rj45 for combo ports to
configure different values for the SFP and
RJ-45 modes. If neither sfp nor rj45 is
specified, the command applies to both
modes. The device works with the values
that apply according to whether an SFP is
inserted.
Specifying classification key per port classification-key [src-ip-addr] src-ip-addr – classification key according to
[dst-ip-addr] [legacy] [vlan] [inner-vlan] source IP
dst-ip-addr – classification key according to
destination IP
legacy – No classification key is used.
vlan – classification key according to VLAN
inner-vlan – classification key according to
VLAN + Inner VLAN
You can change the port classification key
only if all flows using this port are
administratively disabled.
Refer to the relevant table in Classification
Keys in the Traffic Processing chapter to see
the queue/priority mapping methods for the
selected classification key, as well as the
flows / flow parameters that can be
configured for the key.
Clearing OAM EFM statistics clear-efm-statistics
Clearing L2CP statistics clear-l2cp-statistics See Clearing Statistics.
Clearing port statistics clear-statistics See Clearing Statistics.
Configuring port to trust DHCP packets dhcp-trust Client ports must always be untrusted
sent from server (no dhcp-trust); otherwise, the DHCP relay
discards the discovery messages sent from
the client port to the server.
Relevant only if DHCP snooping is enabled.
Configuring OAM EFM descriptor efm descriptor <efm-descriptor-index> Refer to OAM EFM in the Monitoring and
Diagnostics chapter.
Setting maximum frame size (in bytes) egress-mtu <64–12288>

to transmit (frames above the
specified size are discarded)

Setting port to function as network or functional-mode {network | user} Note: Relevant to the following ports:
user • ETX203AM – Second modular GbE port if
GbE module is inserted, or first fixed port
(port 0/3) if there is no module
• ETX203AX or ETX205A – Second
network interface
• ETX220A – Second 10GbE network
interface (port 4/2) and first two GbE
interfaces on slot 1 (ports 1/1 and 1/2).
See Table 5-2 for further information.
Associating a Layer-2 control l2cp profile <l2cp-profile-name> Be sure to assign the same L2CP profile to
processing profile with the port both network ports.
The associated L2CP profile must specify
peer action for MAC 0x02 in the following
cases:
• The port needs to receive clock
signals (i.e. is defined as clock source).
• LACP (LAG) is enabled for the port.
• Link OAM (EFM) is enabled for port.
For an explanation on how to configure an
L2CP profile, refer to Layer-2 Control
Protocol (L2CP) Processing in the Traffic
Processing chapter.
Configuring user port with L2PT l2pt-network Configurable for user ports only.
network functionality Enter no l2pt-network to disable user port
from functioning as L2PT network port.
Configuring LLDP parameters lldp Refer to Link Layer Discovery Protocol (LLDP)
in the Traffic Processing chapter for details.
Executing loopback test loopback {local | remote} See Testing Ethernet Ports.
[duration <seconds>]

Setting maximum advertised capability max-capability {10-full-duplex | 10-full-duplex – 10baseT full duplex
(highest traffic handling capability to 100-full-duplex | 1000-full-duplex | 100-full-duplex – 100baseT full duplex
be advertised during the 1000-x-full-duplex } [{sfp | rj45}]
1000-full-duplex – 1000base T full duplex
autonegotiation process) for FE/GbE
port if autonegotiation is enabled 1000-x-full-duplex – 1000 BaseX,
1000 BaseLX, 1000 BaseSX, or 1000 BaseCX
full duplex
Notes:
• The values 1000-full-duplex and
1000-x-full-duplex are relevant only for
GbE ports, not for FE ports.
• Use sfp or rj45 for combo ports to
inserted.
• Maximum advertised capability for combo
fiber optic ports is permanently set to
1000-x-full duplex.
• For ETX220A, maximum advertised
capability for GbE ports is permanently
set to 1000-x-full duplex.
Defining maximum quality level of max-ql {prc | ssu-a | ssu-b | sec | dnu | The quality level of the SyncE transmitted
clock source, if SyncE is transmitted ssm-based | prs | stu | st2 | tnc | st3e | st3 over this port is the minimum of the quality
over the port | smc | st4 | dus | ssm-based | prov | unk | level set by this command, and the system
sec | dnu | ssm-based} quality level set by clock selection.
Note: Refer to the Clock Selection section in
the Timing and Synchronization chapter for
an explanation of the quality levels.
Assigning description to port name <string> Entering no name removes the name.
Configuring collection of performance pm-collection interval <seconds> Note: You can enable PM statistics collection
management statistics for the port, for all Ethernet ports rather than enabling it
that are presented via the RADview for individual ports. In addition to enabling
Performance Management portal PM statistics collection for the ports, it must
be enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Associating a policer profile for policer profile <policer-profile-name> Typing no policer removes any policer profile
broadcast/multicast traffic with the from the port.
port
Associating a queue group profile with queue-group profile

the port <queue-group-profile-name>

Measuring port data rate and line rate rate-measure interval <seconds> Possible values: 10–300
See Viewing Ethernet Port Data Rate and
Line Rate for details.
Enabling/disabling Silent Start [no] silent-start This parameter is visible for optical ports
only.
silent-start can be configured only if auto-
negotiation is disabled (no uto-negotiation).
Setting data rate and duplex mode of speed-duplex {10-full-duplex | 10-full-duplex – 10baseT full duplex
FE/GbE port 100-full-duplex | 1000-full-duplex | 100-full-duplex – 100baseT full duplex
1000-x-full-duplex [{sfp | rj45}]
1000-full-duplex – 1000base T full duplex
1000-x-full-duplex – 1000 BaseX,
1000 BaseLX, 1000 BaseSX, or 1000 BaseCX
full duplex
Notes:
• The values 10-full-duplex,
100-full-duplex, 1000-full-duplex, and
1000-x-full-duplex are relevant only when
auto-negotation is disabled.
• The values 1000-full-duplex and
1000-x-full-duplex are relevant only for
GbE ports, not for FE ports.
• Use sfp or rj45 for combo ports to
inserted.
• Speed/duplex for combo fiber optic ports
is permanently set to 1000-x-full duplex.
• For ETX205A, speed/duplex is relevant
only for RJ-45 copper ports when
autonegotiation is disabled.
• For ETX220A, speed/duplex for GbE
ports is permanently set to 1000-x-full
duplex.
Setting data rate and duplex mode of speed-duplex 10g-x-full-duplex 10g-x-full-duplex – 10GbaseER/SR full duplex
10GbE port
Setting the VLAN tagged frame ETH II tag-ethernet-type <0x0000-0xFFFF>

frame Ethertype (tag protocol
identifier)

Enabling transmitting of clock tx-ssm You should enable this for Ethernet ports
availability and quality via SSM that transmit clock signals. The MAC address
of the transmitting port is used in the SSM
message.
Entering no tx-ssm disables sending SSM
messages.
Displaying L2CP statistics show l2cp-statistics See Displaying Layer-2 Control Processing
Statistics.
Displaying OAM EFM status show oam-efm
Displaying OAM EFM statistics show oam-efm-statistics
Displaying measured port data rate show rate See Viewing Ethernet Port Data Rate and
and line rate Line Rate for details.
Displaying the port statistics show statistics See Viewing Ethernet Port Statistics.
Displaying the port status show status See Viewing Ethernet Port Status.
Administratively enabling port no shutdown Using shutdown disables the port.
Table 5-2. Classification Key Priority Map Scheme
Classification Key Queue Mapping Method
Legacy (current ‘key’) NA

IPv4DA+DSCP 1. Flow
src-ip-addr 2. DSCP
IPv4SA+DSCP 1. Flow
dst-ip-addr 2. DSCP
VLAN Flow (Fixed)

vlan DSCP
P-bit
VLAN Inner VLAN Flow (Fixed)

inner-vlan DSCP
P-bit
Setting Functional Mode to Network or User Port

You can set the following Ethernet ports to function as network or user.
• ETX203AM:
 GbE module – second modular GbE port
 No module – first fixed port (port 0/3)

• ETX203AX or ETX205A – second network interface

• ETX220A:
 Second 10GbE network interface (port 4/2)
 First two GbE interfaces on slot 1 (ports 1/1 and 1/2)
If you have only one network port after changing the functional mode, then
redundancy is not possible.
By default, the functional mode of the second Ethernet interface (ETH2) in
ETX203AX-E1 is network. In order to configure this port, you are required to
change its functional mode to user.
Notes • 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 Ethernet interface:

1. Navigate to configure port ethernet [<slot>/]<port>.
The config>port>eth([<slot>/]<port>)# 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.
4. Type no shutdown to administratively enable the port.
Examples
 To change the second network interface functional mode to user port for
ETX203AM:
exit all
configure port ethernet 1/2
shutdown
no shutdown
save
 To change the second network interface functional mode to user port for
ETX203AX or ETX205A:
exit all
configure port ethernet 2
shutdown
no shutdown
save

 To change the second 10GbE network interface functional mode to user port:
exit all
shutdown
no shutdown
Viewing Ethernet Port Status

You can display the following:
• Summary information showing the status and speed of all Ethernet ports.
Information is presented in a table (one row per port); first 16 characters of
port name are displayed.
• Summary information as above, but with full port name (up to 255
characters) and different speed format. Presents all information per port, in
ascending order of port numbers.
• Status and configuration of an individual Ethernet port, including SFP
information if an SFP is inserted
Note The port operational status indicates if the port is down to fault propagation.
Display of an optical Ethernet port status includes the Silent Start status,
provided Silent Start has been enabled. Silent Start status can be one of the
following:
In Progress Rx signal was detected but Ethernet was not completely

recognized (Eth sync and Eth frames).
Completed Ethernet was recognized.
No Signal No Rx optical signal detected (fiber disconnected).

Detected
 To display the status of all Ethernet ports (in tabular format):

• At the prompt config>port#, enter:
show summary
The statuses 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 the status of all Ethernet ports with full port names:
show summary-full-name
 To display the status of a specific Ethernet port:

• At the prompt config>port>eth(<port-num>)#, enter:
show status
The Ethernet port status parameters are displayed, including SFP
information if applicable.

Notes • The SFP/XFP wavelength values display the exact values from the SFP/XFP
registers.
• In case of DDM SFP/XFP, 1/100 nano meter resolution is supported
(e.g 1536.61).
Examples
 To display the status of all Ethernet ports for ETX203AM:

ETX203AM# configure port
ETX203AM>config>port# show summary
Port Number Name Admin Oper Speed
-----------------------------------------------------------------------------
Ethernet 0/3 ETH-0/3 Up Up 1000000000
Ethernet 0/5 ETH-0/5 Up Testing 1000000000
Ethernet 0/101 MNG-ETH Up Up 100000000
 To display the status of all Ethernet ports for ETX203AX or ETX205A:

ETX-2# configure port
ETX-2>config>port# show summary
-----------------------------------------------------------------------------
Ethernet 1 ETH 1 Up Up 1000000000
Ethernet 3 ETH 3 Up Testing 1000000000
Ethernet 101 MNG-ETH Up Up 100000000
 To display the status of all Ethernet ports for ETX220A:

ETX220A# configure port
ETX220A>config>port# show summary
-----------------------------------------------------------------------------
Ethernet 0/101 MNG-ETH Up Up 100000000
Ethernet 1/1 ETH-1/1 Up Down 1000000000


 To display the status of all Ethernet ports for ETX203AX with full name:
ETX-203AX>config>port# show summary-full-name
Port : Ethernet Number : 1
Name : testing
Admin : Up
Oper : Up
Speed : 1Gbps
Name : ETH-2
Admin : Up
Oper : Down
Speed : 1Gbps
Name : ETH-3
Admin : Up
Oper : Up
Speed : 1Gbps
Name : ETH-4
Admin : Up
Oper : Up
Speed : 1Gbps
Name : ETH-5
Admin : Up
Oper : Down
Speed : 1Gbps

Name : ETH-6
Admin : Up
Oper : Down
Speed : 1Gbps
Name : MNG-ETH
Admin : Up
Oper : Up
Speed : 100Mbps
Port : SVI Number : 96
Name : SVI 96
Admin : Up
Oper : Up
Speed : 0
ETX-203AX>config>port#
 To display the status of Ethernet port 3 in ETX203AM:

ETX203AM# configure port ethernet 0/3
ETX203AM>config>port>eth(0/3)# show status
Name : ETH-0/3
Operational Status : Up
Connector Type : RJ45
Auto Negotiation : Complete
Speed And Duplex : 1000 Full Duplex
MAC Address : 00-20-D2-50-A2-57
 To display the status of Ethernet port 3 in ETX203AX:

ETX203AX# configure port ethernet 3
ETX203AX>config>port>eth(3)# show status
Name : ETH 3
Operation Status : Up
Connector Type : RJ45
Auto Negotiation : Complete
Speed And Duplex : 10 Full Duplex
MAC Address : 00-20-D2-F6-68-D0

 To display the status of Ethernet port 3 in ETX205A if the port is up and no SFP
is inserted:
ETX205A# configure port ethernet 3
ETX205A>config>port>eth(3)# show status
Name : ETH 3
Connector Type : Combo RJ45+SFP Out - RJ45 Active
Auto Negotiation (SFP) : Complete
MAC Address : 00-20-D2-FA-04-CB
 To display the status of Ethernet port 3 in ETX205A if the port is down due to
fault propagation, and no SFP is inserted:
Name : ETH 3
Operation Status : Down (Fault-Propagation)
Connector Type : Combo RJ45+SFP Out - RJ45 Active
Auto Negotiation (SFP) : Other
MAC Address : 00-20-D2-F8-80-81
 To display the status of Ethernet port 3 in ETX205A if an SFP is inserted:

Name : ETH-3
Connector Type : Combo RJ45+SFP In - SFP Active
Auto Negotiation (SFP) : Complete
Speed And Duplex (SFP) : 1000 FX Full Duplex
MAC Address : 00-20-D2-ED-3C-86
SFP
---------------------------------------------------------------
Connector Type : LC
Manufacturer Name : WTD
Manufacturer Part Number : RTXM191-551-C05
Typical Maximum Range (Meter) : 550
Wave Length (nm) : 850
Fiber Type : MM
Port Status
---------------------------------------------------------------
: OK
 To display the status of Ethernet port 4/2 in ETX220A:

ETX220A# configure port ethernet 4/2
ETX220A>config>port>eth(4/2)# show status
Name ETH-4/2

Connector Type : XFP In

Auto Negotiation : Disabled
Speed And Duplex : 10G FX Full Duplex
MAC Address : 00-20-D2-F0-D2-C3
SFP
---------------------------------------------------------------
Connector Type : LC
Manufacturer Name : FINISAR CORP.
Manufacturer Part Number : FTLX1412D3BCL
Typical Maximum Range (Meter) : 10000
Wave Length (nm) : 1310 Laser
Fiber Type : SM
RX Power (dBm) : -2.8 dBm

TX Power (dBm) : -1.6 dBm
Laser Bias (mA) : 8.9 mA
Laser Temperature (Celsius) : 38.0 C
Power Supply (V) : 3.03 V
 To display the status of Ethernet port 1 with Silent Start enabled:

ETX205A# show con port eth 1 status
Name Eth-1
Connector Type : SFP
Auto Negotiation ……….. : Disabled
Speed And Duplex ……….. : 1000 Full Duplex
MAC Address : 00-20-D2-51-0C-50
Silent Start : In progress
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 toward the user interface.
Remote Loopback is closed toward the network interface.
 To run a physical layer loopback test:

1. Navigate to configure port ethernet [<slot>/]<port-num> to select the
Ethernet port to test.
2. Enter:
loopback {local | remote} [duration <seconds>]
The duration is in seconds, with range 0–86400. Entering 0 or not specifying
the duration disables the timer, e.g. the loopback runs forever until you
disable it.

While the test is running, entering show summary at the port level displays
the port’s operational status as Testing (see Viewing Ethernet Port Status).
3. To end the loopback test, enter:
no loopback
Example
 To run loopback on Ethernet port 3 in ETX203AX or ETX205A:

exit all
configure port ethernet 3
loopback remote duration 30
 To display loopback status:

ETX-2>config>port>eth(3)# show loopback
Loopback : Remote Remain (sec) : 21
Viewing Ethernet Port Statistics

You can display statistics for the Ethernet ports, as well as L2CP statistics. The
sampling interval for the Ethernet port statistics can be configured.
Setting Sampling Interval for Port Statistics

The sampling interval can be configured from one to 30 minutes. The default is
15 minutes.
 To set the sampling interval:

rate-sampling-window <1–30>
The sampling interval is set to the specified number of minutes.
Displaying Port Statistics
 To display the Ethernet port statistics:

• At the prompt config>port>eth([<slot>/]<port-num>)#, enter:
show statistics
Ethernet port statistics are displayed. The counters are described in the
following table.
Example
 To display the statistics for Ethernet port 2/4 in ETX220A:

ETX-2# configure port ethernet 2/4
ETX-2>config>port>eth(2/4)# show statistics
Rates Sampling Window
---------------------------------------------------------------
Window Size [Min.] : 15
Window Remain Time [Min.] : 14

Running
---------------------------------------------------------------
Counter Rx Tx
Total Frames 312248842 0
Total Octets 41216847144 0
Total Frames/Sec 0 0
Total Bits/Sec (L1) 0 0
Minimum Bits/Sec (L1) 0 0
Maximum Bits/Sec (L1) 0 0
Total Bits/Sec (L2) 0 0
Minimum Bits/Sec (L2) 0 0
Maximum Bits/Sec (L2) 0 0
Unicast Frames 312248842 0
Multicast Frames 0 0
Broadcast Frames 0 0
CRC Errors 0
Error Frames 0 0
L2CP Discarded 0
OAM Discarded 0
Unknown Protocol Discarded 0
CRC Errors/Sec 0
Jabber Errors 0
Oversize Frames 0 0
Unmapped Cos Frames 0 --
MTU Discarded -- 0
64 Octets 0 0
65-127 Octets 0 0
128-255 Octets 312248842 0
256-511 Octets 0 0
512-1023 Octets 0 0
1024-1518 Octets 0 0
1519-2047 Octets 0 0
2048-Max Octets 0 0
MTU Discarded Flow -- --
Table 5-3. Ethernet Statistics Counters
Window Size [Min.] Interval for sampling statistics, user-configurable (see Setting Sampling
Interval for Port Statistics)
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 (L1) Number of bits received/transmitted per second in Layer 1, using the line
rate: [Total number of bytes + (number of packets x 20 bytes of line
overhead)] divided by the time interval

Minimum Bits/Sec (L1) Minimum number of bits received/transmitted per second in Layer 1, using
the line rate: [Total number of bytes + (number of packets x 20 bytes of line
Maximum Bits/Sec (L1) Maximum number of bits received/transmitted per second in Layer 1, using
the line rate: [Total number of bytes + (number of packets x 20 bytes of line
Total Bits/Sec (L2) Number of bits received/transmitted per second in Layer 2, using the data
rate: [Total number of bytes (not including line overhead) divided by the
time interval
Minimum Bits/Sec (L2) Minimum number of bits received/transmitted per second in Layer 2, using
the data rate: [Total number of bytes (not including line overhead) divided
by the time interval
Maximum Bits/Sec (L2) Maximum number of bits received/transmitted per second in Layer 2, using
the data rate: [Total number of bytes (not including line overhead) divided
by the time interval
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
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
excludes frames received with Frame-Too-Long or Frame-Too-Short error.
Error Frames Total number of discarded Rx/Tx error frames
L2CP Discarded Total number of L2CP frames discarded
OAM Discarded Total number of OAM frames discarded. Refer to OAM Packet Handling in the
Monitoring and Diagnostics chapter for all cases when OAM packet is
discarded.
Unknown Protocol Discarded Total number of frames with unknown protocol, which are discarded. This
includes:
• Packets dropped as they were not matched by a classifier profile
• Packets dropped by the L2PT mechanism as a result of a non-existent
forwarding path
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
Jabber Errors Total number of frames received with jabber errors
Oversize Frames Total number of oversized frames received/transmitted
Unmapped CoS Frames
MTU Discarded Total number of packets dropped due to exceeding the egress-mtu limit
configured over the port. Relevant to Ethernet, PCS, and Logical MAC ports in
ETX220A.
64 Octets Total number of received/transmitted 64-byte packets
65–127 Octets Total number of received/transmitted 65 to 127-byte packets

2048–Max Octets Total number of received/transmitted packets with 2048 bytes and up to
maximum
MTU Discarded Flow The last flow from which MTU packets were discarded. Relevant to Ethernet,
PCS, and Logical MAC ports in ETX220A.
Displaying Layer-2 Control Processing Statistics

The following procedure describes how to generate L2CP statistics for an
Ethernet port. (You can use the same CLI command to display L2CP statistics for
Logical MAC and PCS ports.) The counters displayed relate to L2CP MAC swap
functionality.
 To display the Layer-2 control processing statistics for an Ethernet port:

show l2cp-statistics
L2CP statistics are displayed for the specified port, showing the number
of encapsulated and decapsulated packets for each protocol.
Example
 To display the L2CP statistics for Ethernet port 1 in ETX203AX:

ETX203AX>config>port>eth(1)# show l2cp-statistics
Protocol Encapsulated Decapsulated
---------------------------------------------------------------
LACP 0 0
STP 0 0
CDP 0 0
VTP 0 0
LLDP 0 0
PVSTP 0 0
PAGP 0 0
UDLD 0 0
DTP 0 0
LAMP 0 0
Link OAM 0 0
ELMI 0 0
802.1x 0 0
GVRP 0 0
GMRP 0 0
MMRP 0 0
MVRP Customer Bridge 0 0
MVRP Provider Bridge 0 0
MSRP 0 0
MIRP 0 0

Clearing Statistics
 To clear the statistics for an Ethernet port:

clear-statistics
The statistics for the specified port are cleared.
 To clear the L2CP statistics for an Ethernet port:

clear-l2cp-statistics
The L2CP statistics for the specified port are cleared.
Viewing Ethernet Port Data Rate and Line Rate

You can measure the data rate and line rate at which Ethernet ports transmit and
receive, for a configurable time interval of 10–300 seconds. After you enter the
command to measure the rates, ETX-2 automatically displays the results when
the specified time interval ends. The data rate is calculated by dividing the total
number of bytes (not including line overhead) by the time interval. The line rate is
calculated by dividing (total number of bytes + (number of packets x 20 bytes of
line overhead)) by the time interval.
 To start data rate and line rate measurements for an Ethernet port:
rate-measure interval <seconds>
The rate measurement starts. You can use show rate to monitor how
much of the time interval has elapsed. The result is automatically
displayed, without the need to enter show rate, after the specified time
interval ends.
Example
 To display the data rate and line rate for Ethernet port 1/2 in ETX203AM:
ETX-2>config>port>eth(1/2)# rate-measure interval 30
ETX-2>config>port>eth(1/2)# show rate

Name : ETH-1/2
Status : In Progress
Time Left to Elapse (Sec) : 23
ETX-2>config>port>eth(1/2)#
Name : ETH-1/2
Status : Passed
Start Time : 2014-11-13 12:14:16 UTC +00:00
Duration (Sec) : 30
L1 L2
Rx Rate (bps) : 1000 950
Tx Rate (bps) : 1500 1400

5.6 Ethertype
Ethertype tag configuration of a packet allows identification of incoming and
outgoing VLAN-tagged packets.
Ethertype (tag protocol ID, or TPID) configured per port is used for:
• Identification of (outer) VLAN-tagged packets at ingress
• Setting the Ethertype value used in VLAN editing actions (Mark, Push) at
egress
Standards
IEEE 802.1Q
Benefits
Per-port tag Ethertype configuration allows identification of incoming and
outgoing VLAN-tagged frames.
Factory Defaults
By default, Ethertype is set to 8100.
Global tag Ethertype values, other than 8100 (the default), must be configured at
the device (chassis) level before they can be used to configure the port level
Ethertype.
ETX-2 supports up to two Ethertype tag values:
• 8100 – preconfigured default; cannot be deleted or changed
• 88a8
Configuration of a packet’s outer tag Ethertypes allows ingress identification of a
packet’s outer VLAN tags, as follows:
• The packet’s outer VLAN tag is identified if the packet’s outer tag Ethertype
equals the port’s configured tag Ethertype.
Ethertype configured per port is used for the identification of VLAN-tagged
frames at ingress and VLAN editing at egress. This refers to outer VLAN only. The
outer VLAN of the incoming frame must match the configured Ethertype of the
port in order to be considered a VLAN-tagged frame (otherwise the frame is
considered untagged or dropped).
Note Ethertype tag cannot be changed if a port (Ethernet or LAG) has flows attached
to it.
The following table describes the admission rules for different port and TPID
types.
5-42 Ethertype ETX-2

Table 5-4. Ports with Configured Port TPID Y (Tag Ethertype port configuration)
Outer TPID Inner TPID Admit/Drop Recognized Tag Levels
Y None Admit 1
Y 8100 Admit 2
Y Other than 8100 Admit 1
Z (other than Y) Don’t care Admit Untagged
None – Admit Untagged
Configuring Ethertype
ETX-2 comes preconfigured with one global Ethertype tag value – 8100. This
Ethernet tag value cannot be modified or deleted.
You can configure an additional global Ethertype tag so that it can be used in
Ethertype tag configuration of a packet or port.
If an additional tag value is not defined, the port and packet can only use the
default global value 8100.
 To configure the Ethertype tag at the device level:

1. Navigate to config>port.
2. Enter tag-ethernet-type <0x0000-0xFFFF>.
Example
 To configure a port with global Ethertype tag 0x88a8:
ETX-2>config>port>tag-ethertype 0x88a8
The following table lists the messages generated by ETX-2 when a configuration
error is detected.
Message Description
Modify failed: Ethertype tag value is in The Ethertype tag value cannot be changed because it is
use currently used by a port of a flow.
Invalid port Ethertype tag value The Ethertype tag value for a port cannot be configured to the
default value (0x8100), and cannot be different from the one
configured at system level.
Cannot delete default Ethertype tag The default Ethertype tag value (0x8100) cannot be deleted.
value
Delete failed: Ethertype tag value is in The Ethertype tag value cannot be deleted because it is
use currently being used by a port of a flow.
ETX-2 Ethertype 5-43

Message Description
Setting failed: Ethertype tag value is The Ethertype tag value for a port or a flow is different from the
unknown one configured at system level.
Ethertype tag cannot be modified for a The Ethertype tag value is in use by the LAG.
port attached to LAG
5.7 GFP Ports
Applicable Products
• E1/T1/T3 module and VCG ports are relevant to ETX203AM.
Standards
G.7041
Benefits
GFP logical ports provide a logical link to smart SFP E1/T1/T3/SDH/SONET ports or
modular E1/T1/T3 ports.
ETX-2 uses GFP (Generic Framing Procedure) ports to provide a logical link to the
TDM ports that become available when smart SFPs are inserted (see Smart SFPs),
or an E1/T1/T3 module is installed.
ETX-2 supports up to 16 GFP ports when inserting up to 16 Smart SFPs (MiRICs)
into ETX220A ports; in other devices, supports up to four GFP ports.
When using the GFP module (ETX203AM), up to eight E1/T1 or two T3 can be
supported in a single GFP VCAToPDH group. ETX203AM supports four or eight
E1/T1 GFP ports as a single GFP group; it cannot be a central site to four RICs
(each with a single E1/T1).
Notes • If a module with multiple E1/T1/T3 ports is installed, the GFP port is bound to
the VCG port that is bound to the E1/T1/T3 ports.
• If a module with a single T3 port is installed, the GFP port is bound directly to
the T3 port.
Factory Defaults
By default, no GFP ports exist. When a GFP port is created, it is configured as
shown below.
5-44 GFP Ports ETX-2

Parameter Default Remarks
name GFP <port>
scrambler-payload rx-tx Scrambling on the GFP packet payload in

both directions is enabled.
fcs-payload no fcs-payload CRC-32 sequence of GFP packet payload

is disabled.
Configuring GFP Ports

 To configure a GFP port:
gfp <port>
The port is created if it does not already exist, and the
config>port>gfp(<port>)# prompt is displayed.
Binding GFP port to E1, T1, T3, bind e1 [<slot>/]<port> Notes:

or SDH/SONET port bind t1 [<slot>/]<port> • The relevant smart SFP port must
bind e3 [<slot>/]<port> exist, or if binding to a modular T3
port, a module with a single T3
bind t3 [<slot>/]<port>
port must be installed.
bind sdh-sonet [<slot>/]<port>
• The GFP port index must match
the TDM port index.
• Use the no bind form to remove
the binding.
Binding GFP port to VCG port bind vcg <port> Notes:

• The VCG port must exist.
• The GFP port index must match
the VCG port index.
• Use the no bind form to remove
the binding.
Enabling/disabling CRC-32 fcs-payload Type no fcs-payload to disable.

sequence of GFP packet payload
Assigning name to GFP port name <string>
Enabling/disabling scrambling on scrambler-payload rx-tx

the GFP packet payload in both
directions
ETX-2 GFP Ports 5-45

Enabling/disabling VLI byte vcat-header If enabled, VCAT header is added to

insertion on VCAT trunk or PDH frames.
Notes:
• Not relevant to GFP port bound to
SDH/SONET port, modular T3 port,
or VCG port.
• VCAT is supported only under E1
framing with line type set to
G.732 with CRC.
Displaying a list of interfaces show bind Lower level binds to E1.

bound to the port Higher level binds to VCG.
Displaying GFP port statistics show statistics Not displayed for ETX203AX with E1.
Clearing port statistics clear-statistics
Displaying GFP port status show status Operation Status:

Up – if lower layer is up (if E1 is up)
Down – if lower layer is down (if E1 is
down)
Examples
 To configure GFP logical port 1:
• Bind to VCG port 1, which must be bound to multiple E1/T1/T3 ports on the
module.
exit all
config port gfp 1bind vcg 1exit all
 To display information on GFP logical port 1:
ETX-2# config port gfp 1ETX-2>config>port>gfp(1)# info detail
name "GFP 1 "
bind vcg 1 no fcs-payload
scrambler-payload rx-tx
ETX-2>config>port>gfp(1)# show status
Name : GFP 1Operation Status : Up
ETX-2>config>port>gfp(1)# show bind
Higher Layer
---------------------------------------------------------------
Lower Layer
---------------------------------------------------------------
VCG 1
 To configure GFP logical port 3:
• Bind to smart SFP E1 port 3 on ETX203AM.
exit all
config port gfp 3
bind e1 0/3/1
5-46 GFP Ports ETX-2

exit all
 To display the status of GFP logical port 3:
ETX-2# config port gfp 3
ETX-2>config>port>gfp(3)# show status
Name : GFP 3
5.8 HDLC Ports
Applicable Products
This feature is applicable to ETX203AX with a built-in E1 port.
Factory Defaults
ETX203AX with E1 is supplied with all HDLC logical ports disabled.
Configuring HDLC Ports

 To configure an HDLC logical port:
hdlc <port>
config>port>hdlc(<port>)# prompt is displayed.
Binding HDLC port to E1 port bind e1 <port> Type no bind form to remove the
binding.
Assigning name to HDLC port name <string>
Displaying E1 bound to the port show bind Lower level bind to E1.
Displaying HDLC port status show status Displays Operation Status:

Up – if lower layer is up (if E1 is up)
Down – if lower layer is down (if E1 is
down)
5.9 Internal Ports for x86 Interconnection

Two predefined internal Ethernet ports are used for interconnection between the
ETX-2 NID and x86 processor, if applicable.
ETX-2 Internal Ports for x86 Interconnection 5-47

• Ethernet 1, interconnected to ETX-2 internal Ethernet port 6

• Ethernet 2, interconnected to ETX-2 internal Ethernet port 5
Note
For ETX205A with PMC option, regular user ports 5 and 6 are not available.
Applicable Products
This feature is applicable to ETX205A with a PMC option.
Benefits
The internal ports enable interconnection with the x86 processor.
Factory Defaults
By default, the internal Ethernet ports have the following configuration.
dhcp-trust Trust server DHCP packets Disabled (trust client DHCP

packets)
name Port name INT ETH <port-num>
queue-group Queue group profile DefaultQueueGroup
shutdown Administrative status no shutdown
The internal ports are always administratively enabled. They can be ingress or
egress ports in flows, to enable transmitting data between the ETX-2 NID and the
x86 processor.
The internal ports cannot be members of a LAG or be assigned Ethernet
protection group.
You can configure flows between the internal ports and the following types of
ports:
• Bridge port
• Ethernet port
• ETP Subscriber port
• LAG
You cannot configure flows between the internal Ethernet ports and the
following types of ports:
• ETP subscriber port
• SVI assigned to router interface
5-48 Internal Ports for x86 Interconnection ETX-2

Configuring the Internal Port Parameters

The internal ports are referred to in the CLI as int-ethernet <port-num>, where
<port-num> is 5 or 6.
 To configure the internal port parameters:
1. Navigate to configure port int-ethernet <port-num> to select the internal
port to configure.
The config>port>int-eth(<port-num>)# prompt is displayed.
Assigning description to port name <string> Entering no name removes the name.

the port <queue-group-profile-name>
Displaying port status show status
Displaying port statistics show statistics
5.10 Logical MAC Ports

Logical MAC ports are used to connect E1/T1/T3 ports to flows.
Applicable Products
• E1/T1/T3 module and VCG ports are relevant to ETX203AM.
Benefits
The logical MAC ports connect between flows and GFP or HDLC ports.
ETX-2 uses logical MAC ports to connect flows to GFP (Generic Framing
Procedure) or HDLC ports that provide a logical link to modular E1/T1/T3 ports, or
to the TDM ports that become available when smart SFPs are inserted (see Smart
SFPs).
ETX-2 Logical MAC Ports 5-49

Factory Defaults
By default, no logical MAC ports exist. When a logical MAC port is created, it is
configured as shown below.
Description Default Value
Port name LOGICAL MAC <logical-mac-port-number>
Administrative status Disabled
Trust server DHCP packets Disabled
Port to which the logical MAC is bound GFP 1
Ethernet tag protocol identifier 0×8100
Egress MTU 1790
Functional mode Network
Queue group profile DefaultQueueGroup
L2CP profile L2cpDefaultProfile
Configuring Logical MAC Ports

 To configure logical MAC ports:
1. At the config>port# prompt, type
logical-mac <port>
config>port>log-mac(<port>)# prompt is displayed.
Task Command Possible Values
Binding logical MAC port to GFP port bind gfp <port> • The GFP port must exist.
• Use the no bind form to
remove the binding.
Binding logical MAC port to HDLC port bind hdlc <port> • The HDLC port must exist.
• Use the no bind form to
remove the binding.
5-50 Logical MAC Ports ETX-2

Specifying classification key per port classification-key [src-ip-addr] src-ip-addr – Classification

[dst-ip-addr] [legacy] [vlan] key according to source IP
[inner-vlan] dst-ip-addr – Classification
key according to destination IP
legacy – No classification key is
used.
vlan – Classification key
according to VLAN
inner-vlan – Classification key
according to VLAN + Inner
VLAN
You can change the port
classification key only if all
flows using this port are
Refer to the relevant table in
Classification Keys in the Traffic
Processing chapter to see the
queue/priority mapping
methods for the selected
classification key, as well as
the flows / flow parameters
that can be configured for the
key.
Configuring port to trust DHCP packets dhcp-trust Client ports must always be
sent from server untrusted (no dhcp-trust);
otherwise, the DHCP relay
discards the discovery
messages sent from the client
port to the server.
Relevant only if DHCP snooping
is enabled.
Configuring OAM EFM descriptor efm descriptor Refer to Configuring OAM EFM
<efm-descriptor-index> in the Monitoring and
Diagnostics chapter.
Setting maximum frame size to transmit egress-mtu <size> Maximum size is 12,288.
(frames above the specified size are
discarded)
Associating a Layer-2 control processing l2cp profile For an explanation on how to

profile with the port <l2cp-profile-name> configure an L2CP profile, refer
to Layer-2 Control Protocol
(L2CP) Processing in the Traffic
Processing chapter.
Configuring LLDP parameters lldp Refer to Link Layer Discovery

Protocol (LLDP) in the Traffic
ETX-2 Logical MAC Ports 5-51

Running loopback test on port loopback {local|remote} Use the no loopback command
[duration <seconds>] to stop the test.
Local and remote loopback test
are currently not supported in
ETX203AM EoPDH ports.
Associating a policer profile with the policer profile

port <policer-profile-name>
Configuring collection of performance pm-collection interval Note: In addition to enabling

management statistics for the port, <seconds> PM statistics collection for the
that are presented via the RADview port, it must be enabled for
Performance Management portal the device. Refer to
Performance Management in
the Monitoring and Diagnostics
chapter for details.
the port <queue- profile-name>
Setting the VLAN tagged frame ETH II tag-ethernet-type

frame Ethertype (tag protocol <0x0000-0xFFFF>
identifier)
Administratively enabling port no shutdown Using shutdown disables the

port.
Displaying the interfaces that are bound show bind

to the port
Displaying link OAM (EFM) parameters show oam-efm
Displaying L2CP statistics show l2cp-statistics See Displaying Layer-2 Control

Processing Statistics.
Displaying port statistics show statistics
Clearing L2CP statistics clear-l2cp-statistics
Clearing port statistics clear-statistics
 To change the logical MAC port back to ETH:

no logical-mac <port>
The port mode changes from Logical MAC to ETH.
2. Type shutdown and then no shutdown.
5-52 Logical MAC Ports ETX-2

The ETH port hardware is disabled and then enabled, synchronizing the
ETH port, provided that line/cable/fiber is connected.
Examples
 To configure logical MAC port 3:
• Bind to GFP port 3.
exit all
logical-mac 3
bind gfp 3
no shutdown
exit all
 To display information on logical MAC port 3:
ETX-2>config>port# logical-mac 3
ETX-2>config>port>log-mac(3)# info detail
name "LOGICAL MAC 3"
no shutdown
bind gfp 3
tag-ethernet-type 0x8100
egress-mtu 1790
queue-group profile "DefaultQueueGroup"
l2cp profile "L2cpDefaultProfile
classification-key legacy
ETX-2>config>port>log-mac(3)# show status

Name : LOGICAL MAC 3
5.11 PCS Ports

The PCS port is the logical link to SHDSL or VDSL2 ports.
Applicable Products
This feature is applicable to:
• ETX203AM with an SHDSL or VDSL2 module
• ETX203AX with embedded SHDSL ports
Standards
ITU-T G.991.2
ETSI TS 101524
ETX-2 PCS Ports 5-53

Benefits
You can create flows over the PCS port.
The PCS (physical coding sublayer) port represents the bundling of the
SHDSL/VDSL2 interfaces. By default, all SHDSL/VDSL2 lines are bound to a single
PCS port.
Factory Defaults
The PCS port default configuration is shown below.
Port name PCS 1
Administrative status Enabled
Classification key Legacy
DHCP trust no dhcp-trust
Ethernet tag protocol identifier 0×8100
Egress MTU 1790
OAM EFM Disabled
Queue group profile DefaultQueueGroup
L2CP profile L2cpDefaultProfile
Policer profile None
Configuring PCS Port Parameters

 To configure the PCS port parameters:
1. Navigate to configure port pcs <port> to select the PCS port to configure.
The config>port>pcs(<port>)# prompt is displayed.
5-54 PCS Ports ETX-2

Specifying classification key per port classification-key [src-ip-addr] src-ip-addr – Classification key according to
[dst-ip-addr] [legacy] [vlan] [inner-vlan] source IP
dst-ip-addr – Classification key according to
destination IP
legacy – No classification key is used.
vlan – Classification key according to VLAN
inner-vlan – Classification key according to
VLAN + Inner VLAN
You can change the port classification key
only if all flows using this port are
Refer to the relevant table in Classification
Keys in the Traffic Processing chapter to see
the queue/priority mapping methods for the
selected classification key, as well as the
flows / flow parameters that can be
configured for the key.
Configuring OAM EFM descriptor efm descriptor <efm-descriptor-index> Refer to Configuring OAM EFM in the
Monitoring and Diagnostics chapter.
Setting maximum frame size to egress-mtu <size> Possible values: 64–1580

transmit (egress MTU)
Associating a Layer-2 control l2cp profile <l2cp-profile-name> For an explanation on how to configure an
processing profile with the port L2CP profile, refer to Layer-2 Control
Protocol (L2CP) Processing in the Traffic
Processing chapter.
Typing no l2cp disassociates Layer-2 control
processing from the port.
Configuring LLDP parameters lldp See Link Layer Discovery Protocol (LLDP) for
details
Running loopback test on port loopback {local|remote} [duration Use the no loopback command to stop the
<seconds>] test.
Assigning description to port name <string> Typing no name removes the description
from the port.
Configuring collection of performance pm-collection interval <seconds> Note: In addition to enabling PM statistics
management statistics for the port, collection for the ports, it must be enabled
that are presented via the RADview for the device. Refer to Performance
Performance Management portal Management in the Monitoring and
Diagnostics chapter for details.

Associating a policer profile with the policer profile <policer-profile-name> Typing no policer removes any policer
port profile from the port.
Associating a queue group profile with queue-group profile Typing no queue-group removes any queue
the port <queue-group-profile-name> group profile from the port.
Setting the VLAN tag Ethertype tag-ethernet-type <0x0000-0xFFFF>
Displaying the interfaces that are show bind

bound to the port
Displaying link OAM (EFM) parameters show oam-efm
Displaying L2CP statistics show l2cp-statistics See Displaying Layer-2 Control Processing
Statistics.
Displaying port statistics show statistics running See Viewing PCS Port Statistics.
Clearing L2CP statistics clear-l2cp-statistics
Clearing statistics clear-statistics

Note: If the PCS is disabled there is no
traffic forwarding from/to the network side,
although the lines may be physically
synchronized.
Viewing PCS Port Statistics

You can display running statistics for the PCS ports.
 To display the PCS port running statistics:

• At the prompt config>port>pcs(<port>)#, enter:
show statistics running
PCS port statistics are displayed. The counters are described in
Table 5-6.
Example
 To display the statistics for PCS port 1:

ETX-2# configure port pcs 1
ETX-2>config>port>pcs(1)# show statistics running
---------------------------------------------------------------
5-56 PCS Ports ETX-2

Running
---------------------------------------------------------------
Counter 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
CRC Errors 0
Error Frames 0 --
L2CP Discarded 0 --
CFM Discarded 0 --
MTU Discarded 0 56
Unknown Protocol Discarded 0 --
CRC Errors/Sec 0
Jabber Errors 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-2047 Octets 0 0
2048-Max Octets 0 0
MTU Discarded Flow : --/EVC1-TLV
Table 5-6. PCS Statistics Counters
Window Size [Min.] Interval for sampling statistics, user-configurable (see Setting Sampling
Interval for Port Statistics)
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
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

Error Frames Total number of frames with errors received
L2CP Discarded Total number of L2CP frames discarded
CFM Discarded Total number of CFM frames discarded. Refer to OAM Packet Handling in the
Monitoring and Diagnostics chapter for all cases when OAM packet is
discarded.
MTU Discarded Total number of packets dropped due to exceeding the egress-mtu limit
configured over the port (displayed in ETX220A only)
Unknown Protocol Discarded Total number of frames with unknown protocol discarded
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
Jabber Errors Total number of frames received with jabber errors
Oversize Frames Total number of oversized frames received/transmitted
64 Octets Total number of received/transmitted 64-byte packets
2048–Max Octets Total number of received/transmitted packets with 2048 bytes and up to
maximum
MTU Discarded Flow The last flow from which MTU packets were discarded (displayed in ETX220A
only)
5.12 Peers
Configuring peers provides access to remote devices.
Applicable Products
• 1588v2 clock is relevant to ETX205A and ETX220A.
• TDM pseudowires are relevant to ETX205A.
Peers are remote devices operating opposite router interfaces that can be linked
in order to access TDM pseudowires or the 1588v2 master clock.
Factory Defaults
By default, no peers are defined in ETX-2.
5-58 Peers ETX-2

Configuring Peers
You can define up to 64 peers as explained below.
 To define a peer:
• At the config# prompt, do one of the following:
 To define the peer according to IP address, type:
peer <number> ip <ip-address> [name <name>]
 To define the peer according to MAC address, type:
peer <number> mac <mac-address> [name <name>]
5.13 SDH/SONET Ports

SDH/SONET ports are available when smart SFPs such as MiRICi-155 are
provisioned (see Smart SFPs).
SDH (Synchronous Digital Hierarchy) and SONET (Synchronous Optical Network)
are standardized transport protocols that transfer multiple digital bit streams
over optical fiber using lasers or light-emitting diodes (LEDs). SONET is the United
States version and SDH is the international version.
Applicable Products
This feature is applicable to all ETX-2 products. Smart SFP SDH/SONET ports are
referenced as [<slot>/]<port>/<tributary>.
• <tributary> is always set to 1.
Standards
SDH is defined by ITU-T G.707, G.781, G.782, G.783, and G.803. SONET is an ANSI
standard defined in T1.105 and T1.119.
Benefits
SDH and SONET allow many different circuits from different sources to be
transported simultaneously within one single framing protocol.
SDH is based on STM-1 which has a data rate of 155.52 Mbps, equivalent to
STS-3. SONET is based on transmission at speeds of multiples of 51.840 Mbps, or
STS-1.
Factory Defaults
By default, no SDH/SONET ports exist.
ETX-2 SDH/SONET Ports 5-59

Configuring SDH/SONET Ports

 To configure SDH/SONET ports:
1. Provision a smart SFP such as MiRICi-155 and insert it into an Ethernet port
(see Smart SFPs).
sdh-sonet [<slot>/]<port>/<tributary>
The prompt config>port>sdh-sonet([<slot>/]<port>/<tributary>)# is
displayed.
Specifying the cell frame-type { sdh | sonet }

frame type
Running loopback test loopback {local | remote } • local – returns the transmitted
on port [start <seconds> ] [duration <seconds>] data at the physical layer to the
receiving path
transmitting path
seconds) until the loopback starts
• duration – specifies the duration of
the loopback (in seconds). If
duration is not specified, the
stopped.
loopback test.
Assigning a name to name <string>

the port
Specifying if pm-enable
5-60 SDH/SONET Ports ETX-2

Defining thresholds: threshold [ eed { 1e-3 |1e-4 | 1e-5 }]

• EED (Excessive [ sd { 1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 }]
Error Defect) –
detected if the
equivalent BER (bit
error rate) exceeds
the selected
threshold
parameters
• SD (Degraded
Signal Defect) –
detected if the
equivalent BER
exceeds the
selected threshold
parameter.
Selecting the transmit tx-clock-source {internal | loopback} • internal – clock provided by

clock source internal oscillator
• loopback – clock retrieved from the
port's incoming (Rx) data
Displaying list of show bind

interfaces bound to
port
Displaying the port show status

status
Displaying the port show statistics current

statistics show statistics interval <interval-num>
show statistics all
5.14 SFPs
Depending on the product ordering options, some Ethernet ports can be fiber
optic SFP slots that require SFPs to be inserted, or can be combo ports that have
an RJ-45 connector and SFP slot, and the port can function as either. In the case
of combo ports, some of the Ethernet port commands can be used to configure
parameters for RJ-45 mode and for SFP mode (see Ethernet Ports for more
information).
The Ethernet ports that are fiber optic SFP slots, or are combo ports functioning
as SFP slots, are configured as shown in Ethernet Ports. When you display the
port status, the SFP information is shown if applicable (see Viewing Ethernet Port
ETX-2 SFPs 5-61

Status). You can insert regular SFPs into the SFP slots, or you can insert smart
SFPs that provide integrated configuration and management (see Smart SFPs).
Note For all ETX203AX, ETX203AM, ETX205A, and ETX220A temperature-hardened

options, use hardened SFPs with maximum operating temperature 85°C (185°F).
5.15 Smart SFPs

ETX-2 supports integrated configuration and management of smart SFPs (such as
MiRICi/MiTOP devices) to provide TDM port functionality. The following are
supported:
• MiRICi-E1/T1/E3/T3
• MiRICi-155
• MiTOP-E1/T1/E3/T3
The following table specifies the maximum number of smart SFPs supported by
each ETX-2 device, according to whether the smart SFP is managed.
Table 5-7. Maximum Smart SFPs
ETX203AX ETX203AM ETX205A ETX220A
Managed 2 2 2 2
MiRICi-E1/T1/E3/T3
Unmanaged 4 4 4 20
Managed 2 2 2 2
MiRICi-155
Unmanaged 4 4 4 20
Managed 1 1 2 1
MiTOP-E1/T1/E3/T3
Unmanaged 4 4 4 20
Applicable Products
• <slot> is relevant to ETX203AM or ETX220A.
Benefits
ETX-2 offers the use of a wide variety of TDM E1/T1/E3/T3 OC-3/STM-1 ports via
the smart SFP feature.
The smart SFP is provisioned in the specific Ethernet port where the SFP shall be
inserted. After this provisioning, the Ethernet port is no longer available for
normal Ethernet port functioning. If the smart SFP is provisioned in a combo
Ethernet port, the copper connector can no longer be used.
5-62 Smart SFPs ETX-2

The TDM port/s are automatically created when the smart SFP is provisioned, and
can be configured. For information on configuring the TDM port, see the
respective TDM port section.
After you provision a smart SFP, you can do the following:
• Define a logical GFP interface over the smart SFP port (see GFP Ports).
• Define a logical MAC interface over the GFP interface (see Logical MAC Ports).
• Create a flow over the logical MAC interface (refer to Classification by
Port/Flow in the Traffic Processing chapter).
Note If a smart SFP is inserted into ETX-2 while it is powered on, the smart SFP
becomes operational only after resetting ETX-2.
Factory Defaults
By default, no smart SFPs are provisioned. When a smart SFP interface is created,
it is administratively disabled by default, with type set to not-applicable.
Configuring Smart SFPs

To provision a smart SFP, you use the smart-sfp command to specify the Ethernet
port, and then you assign the type of smart SFP.
 To configure smart SFPs:
1. At the config>port# prompt, type smart-sfp [<slot>/]<port>, where
[<slot>/]<port> indicates the Ethernet port where the SFP is (or shall be)
inserted (see Table 5-1 for the port numbers).
Note You can provision the smart SFP before you insert it.
The smart SFP interface is created if it does not already exist and the
config>port>smart-sfp([<slot>/]<port>)$ prompt is displayed.
Assigning the type of smart SFP type {mirici-e1 | mirici-t1 | mirici-e3 | • The smart SFP port must be
mirici-t3 | mirici-155 | mitop-e1 | administratively disabled
mitop-t1 | mitop-e3 | mitop-t3 | before you can change the
not-applicable } type.
• To change the type, you
must first set it to
not-applicable.
Resetting smart SFP reset
Displaying interface status show status
ETX-2 Smart SFPs 5-63

Administratively enabling no shutdown You cannot administratively

interface enable the smart SFP port if
its type is set to
not-applicable.
Using shutdown disables the
interface.
Examples
This example shows how a smart SFP can be provisioned, and a flow created over
the logical MAC port corresponding to a logical GFP port.
 To provision a smart SFP and corresponding flow in ETX203AX or ETX205A:

• Ethernet GbE port 1
• Smart SFP type = MiRICi-E1
• GFP port 1
• Logical MAC port 1
• Flow = flow1, with classification criterion VLAN 1
#*****************Provision the smart SFP
exit all
configure port smart-sfp 1
shutdown
type not-applicable
type mirici-e1
no shutdown
exit
#*****************Create the GFP and bind it to the E1 port

gfp 1
bind e1 1/1
exit
#*****************Create the logical MAC port and bind it to GFP port 1

logical-mac 1
bind gfp 1
no shutdown
exit all
#*****************Create the flow and activate it

configure flows
classifier-profile v1 match-any match vlan 1
flow flow1
lassifier v1
ingress-port logical-mac 1
egress-port eth 3 queue 0 block 0/1
no shutdown
exit all
5-64 Smart SFPs ETX-2

 To display information on the entities configured in the above script:

ETX-2# configure port smart-sfp 1
ETX-2>config>port>smart-sfp(1)# info detail
type mirici-e1
no shutdown
ETX-2>config>port>smart-sfp(1)# exit
ETX-2>config>port# gfp 1
ETX-2>config>port>gfp(1)# info detail
name "GFP 1"
bind e1 1/1
no fcs-payload
scrambler-payload rx-tx
no vcat-header
ETX-2>config>port>gfp(1)# exit
ETX-2>config>port# logical-mac 1
ETX-2>config>port>log-mac(1)# info detail
name "LOGICAL MAC 1"
no shutdown
bind gfp 1
tag-ethernet-type 0x8100
egress-mtu 1790
queue-group profile "DefaultQueueGroup"
l2cp profile "L2cpDefaultProfile"
classification-key legacy
ETX-2>config>port>log-mac(1)#exit all
ETX-2# configure flows
ETX-2>config>flows>flow(flow1)# info detail
classifier "v1"
no drop
policer profile "Policer1"
no mark all
no vlan-tag
no l2cp
ingress-port logical-mac 1
no shutdown
5.16 SHDSL Ports

ETX203AM is optionally equipped with a module that has two or four Single Pair
High-speed Digital Subscriber Line (SHDSL) ports (4-wire or 8-wire). ETX203AX-
DSL is an ETX203AX ordering option with four embedded SHDSL ports (8-wire).
The SHDSL interfaces are bundled into one PCS (physical coding sublayer) port.
See PCS Ports for commands related to the PCS port.
Applicable Products
This feature is applicable to:
ETX-2 SHDSL Ports 5-65

• ETX203AM with an SHDSL module

• ETX203AX-DSL with an embedded SHDSL interface
ETX-2 supports CPE mode (STU-R) only. K.21 is not supported.
Standards
ITU-T G.991.2 (SHDSL.bis)
Benefits
ETX-2 can aggregate traffic over the SHDSL.bis links.
SHDSL is a data communications technology that enables faster data
transmission over copper telephone lines than a conventional voice band modem
can provide. Compared to ADSL, SHDSL employs frequencies that include those
used by traditional POTS telephone services to provide equal data rates to
transmit and receive. As such, a telephone line cannot be used by both an SHDSL
service and a POTS service at the same time. Support of symmetric data rates has
made SHDSL a popular choice by businesses for PBX, VPN, web hosting and other
data services.
The SHDSL uplink supports up to eight wires with ordering options of either four
or eight wires. Each four wires is supported over an RJ-45 connector, meaning
that a four-wire ordering option is supported with a single RJ-45 and an eight-
wire option is supported with two RJ-45.
SHDSL.bis per G.991.2 features symmetrical data rates in both
upstream and downstream directions, Up to 5696 kbit/s of payload in for one
pair of wires is supported. The reach varies according to
the loop rate and noise conditions (more noise or higher rate means decreased
reach) and may be up to 3,000 meters.
SHDSL ports support EFM Bonding. The EFM Aggregation layer allows multiple
pairs of copper ports used as a single, high-capacity link. This enables carrying far
more bandwidth over the existing copper infrastructure.
Dying Gasp is supported over an SHDSL port, using OAM-EFM messages per IEEE
802.3-2005.
Configuring SHDSL Port Parameters

This section explains how to configure the SHDSL port.
 To configure the SHDSL port parameters:

1. For ETX203AM: Navigate to configure port shdsl 1/<port> to select the
SHDSL port to configure, where 1 is the module slot number.
5-66 SHDSL Ports ETX-2

For ETX203AX-DSL: Navigate to configure port shdsl <port>.

2. At the prompt, enter all necessary commands according to the tasks listed
below.
Displaying port status show status See Viewing SHDSL Port Status.
Displaying port statistics show statistics { current | interval SHDSL port statistics are supported per wire
<interval-num> | current-day | all-intervals pair for the following:
| all-days-intervals | all } current – current 15-minute interval
interval – specific 15-minute interval
interval-num – 1-96 (48 intervals per wire)
current-day – today’s statistics
all-intervals – statistics of all intervals
all-days-intervals – statistics of all of
today’s intervals
all – all statistics
See Viewing SHDSL Port Statistics.
Clearing the port statistics clear-statistics
Assigning port name name
Administratively enabling port no shutdown Entering shutdown disables the SHDSL port,
stops issuing alarms for the port, and turns
off the SHDSL LED.
Viewing SHDSL Port Status

 To display the status of SHDSL port 1:
ETX203AM# config port shdsl 1/1
ETX203AM>config>port>shdsl(1/1)# show status
Name : SHDSL-1/1
Operation Status : Down
Wires : 2
Transmission Mode : B-G
Payload Rate (Kbps) : 0
Wires
-----------------------------------------------------------------------------
State SNR Loop Tx PSD Power
Margin Attenuation Power Mask Backoff
(db) (db) (dBm)
-----------------------------------------------------------------------------
Data 18 1 8.5 Symmetric 6
Table 5-8. SHDSL Status Information
Name Port name
ETX-2 SHDSL Ports 5-67

Administrative Status SHDSL line administrative status

Up or Down
Operation Status SHDSL line operational status
Up or Down
Wires Number of wires in port
Transmission Mode Possible values: A-F, B-G
Payload Rate (Kbps) Actual payload rate without the framing overhead of 8Kbps
Wires
State Possible values: Pre Activation, Activation, Data

SNR Margin (dB) Actual Rx SNR on this link
Loop Attenuation (dB) Actual Rx Loop Attenuation on this link
Tx Power (dBm) Actual Tx power (dBm)
PSD Mask Masks for upstream and downstream
Possible values: Symmetric, Assymetric
Power Backoff Current Tx power backoff
Viewing SHDSL Port Statistics

 To display the SHDSL port 1 current statistics:
ETX203AX-DSL# config port shdsl 1
ETX203AX-DSL>config>port>shdsl(1)# show statistics current
Current
-----------------------------------------------------------------------------
Time Elapsed (Sec) : 712
Valid Intervals : 96
ES : 0 LOSWS : 0
SES : 0 CRC Anomalies : 0
UAS : 0
Table 5-9. SHDSL Statistics Parameters
Time Elapsed (Sec) The elapsed time (in seconds) for the current interval/day
Valid Intervals Number of valid intervals for which statistics are displayed; default is 15-
minute intervals.
ES Number of Errored Seconds where one or more CRC error events or one or
more LOSW error events have been detected. This parameter is inhibited
during UAS state.
SES Number of Severely Errored Seconds where 50 or more CRC error events or
one or more LOSW error events have been detected. This parameter is
inhibited during UAS state.
5-68 SHDSL Ports ETX-2

UAS Number of Unavailable Seconds. This state begins after 10 consecutive

severely-errored seconds, and ends after 10 consecutive error-free seconds.
LOSWS Number of seconds during which Loss Of Sync Word events have been
detected
CRC Anomalies Number of errors detected by cyclic redundancy checks
5.17 Service Virtual Interfaces (SVIs)

Service Virtual Interface (SVI) is a virtual (logical) port that is used for binding
router interfaces to Ethernet, Logical MAC, and PCS ports (via Layer-2 flows).
Applicable Products
This feature is applicable to all ETX-2 products.
Benefits
SVIs are used as ingress and egress ports for flows, serving as intermediaries for
routers.
You can define three types of SVIs:
• Router – SVI that can be bound to router interface via Layer-2 flows
• TWAMP – In TWAMP Layer-2 Probe mode; TWAMP SVI enables performing no
shutdown to the router interface, even though there are no flows to and
from the SVI. After defining the TWAMP controller and responder, it becomes
possible to bind SVI to the router interface via Layer-2 flows.
Note • Router SVI is the default. In the CLI command, you do not specify a type for a
Router SVI.
• ETX-2 supports up to 96 SVIs.
Perform the following steps to create an SVI port between an Ethernet port and a
router.
1. Create an SVI port of a specific number and name, and if other than a Router
SVI, specify its type (TWAMP).
2. Enable the SVI by entering no shutdown.
3. Configure a flow with:
 Ingress Ethernet port and egress SVI port (defined in step 1).
 Ingress SVI port (defined in step 1) and egress Ethernet port.
(Refer to Configuring Flows in the Traffic Processing chapter.)
ETX-2 Service Virtual Interfaces (SVIs) 5-69

4. For Router or TWAMP SVI: Bind the router interface to the SVI (of type Router
or TWAMP). (Refer to Configuring Router Interface in the Traffic Processing
chapter.)
Note You can follow the steps above to create an SVI port between a Logical Mac or
PCS port (instead of Ethernet port) and a router.
Factory Defaults
By default, SVI 96 (the highest SVI ID) is configured in no shutdown mode.
The following is the configuration of SVI in the ETX205A factory default file.
# Factory Default File
configure
port
svi 96
no shutdown
exit
exit
flows
classifier-profile mng_untagged match-any
match untagged
exit
classifier-profile mng_all match-any
match all
exit
flow mng_access_default_in
classifier mng_untagged
no policer
ingress-port ethernet 0/101
egress-port svi 96
no shutdown
exit
flow mng_access_default_out
classifier mng_all
no policer
ingress-port svi 96
egress-port ethernet 0/101
no shutdown
exit
exit
router 1
interface 32
address 169.254.1.1/16
bind svi 96
no shutdown
exit
exit
exit
You can delete this default configuration, as required.
5-70 Service Virtual Interfaces (SVIs) ETX-2

Configuring Service Virtual Interfaces

You can enable and operate up to eight service virtual interfaces.
 To configure the SVI parameters:
1. Navigate to configure port svi <svi-num> [twamp] | [gre] to select the SVI to
configure.
 svi-num can be 1-96.
 twamp – if SVI port is intended for use with TWAMP
The config>port>svi(<svi-num>)# prompt is displayed.
Note Entering no svi <svi-num> at the config>port prompt, deletes the SVI.
Setting the port name name <string>
Administratively enabling SVI no shutdown Using shutdown disables the SVI.
Examples
 To configure router SVI:
• Number – 1
• Type – router
• Name – svi_3
ETX203AX>config>port>svi 3
ETX203AX>config>port>svi(3)# name svi_3
ETX203AX>config>port>svi(3)# no shutdown
 To configure TWAMP SVI:

• Number – 1
• Type – TWAMP
• Name – svi_1_twamp
ETX203AX>config>port>svi 1 twamp
ETX203AX>config>port>svi(1)# name svi_1_twamp
ETX203AX>config>port>svi(1)# no shutdown
The following table lists messages that ETX-2 generates when a configuration
error is detected.
ETX-2 Service Virtual Interfaces (SVIs) 5-71

Message Description
SVI cannot be created: max number of SVI cannot be created because the maximum number of SVIs has
SVIs has been reached been reached
SVI number is out of range SVI number cannot be used because it is out of allowed range
Delete failed: SVI is bound SVI cannot be deleted because it is currently in use
Delete failed: SVI is used by flow SVI cannot be deleted because it has flows bound to it
SVI is not configured Binding to the SVI failed because the SVI does not exist
Modify failed: flow is bound to SVI SVI cannot be modified because flows are bound to it
5.18 T1 Ports
The T-carrier signaling scheme was devised by Bell Labs and is a widely used
standard in telecommunications in the USA, Canada, and Japan to transmit voice
and data between devices. T1, also referred to as DS-1, is a dedicated data line
that transmits information at the speed of 1.544 Mbps.
Applicable Products
T1 ports are applicable to ETX-2 products as follows:
 Smart SFP T1 ports are available when smart SFPs such as MiRICi-T1 or
MiTOP-T1 are provisioned (see Smart SFPs)
 Smart SFP T1 ports do not support encapsulation via VCG.
 Smart SFP T1 ports are referenced as [<slot>/]<port>/<tributary>:
 Modular E1/T1 ports can be configured to T1 mode (see DS1 (E1/T1)
 Modular T1 ports support encapsulation via VCG (see VCGs).
 Modular T1 ports are referenced as <slot>/<port>.
• ETX205A with built-in E1/T1 ports:
 Built-in E1/T1 ports can be configured to T1 mode (see DS1 (E1/T1)
 Built-in T1 ports support TDM pseudowire.
 Built-in T1 ports are referenced as <port>.
5-72 T1 Ports ETX-2

Standards
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
T1 lines are high-speed dedicated lines that enable large volume usage.
A T1 link operates over a twisted pair of cables. A nominal 3-volt peak signal is
encoded with pulses using a method that avoids long periods without polarity
changes. The line data rate is 1.544 Mbps at full duplex, which means 1.544 Mbps
for downstream and 1.544 Mbps for upstream. The T1 signal splits into 24
timeslots each which is allocated 8 bits. Each timeslot sends and receives an 8-bit
sample 8000 times per second (8 x 8000 x 24 = 1,544,000), which is ideal for
voice telephone calls where the voice is sampled into an 8-bit number at that
data rate and restored at the other end. The timeslots are numbered from 0 to
24.
Factory Defaults
By default, no smart SFP T1 ports exist.
By default, modular or built-in E1/T1 ports are set to E1 mode. When they are
configured to T1 mode, they have the following configuration.
idle-code 0x7e Code for idle timeslots

Note: Built-in T1 ports only
line-code b8zs Zero code suppression
line-interface dsu Line interface is digital service

unit.
line-interval-threshold es 80 Threshold to trigger line ES

line-length 0-133
line-type Built-in T1 port: unframed

Modular T1 port: ESF
name Built-in T1 port: DS1 <port>

Modular T1 port: T1 <slot>/<port>
ETX-2 T1 Ports 5-73

out-of-service 0xff Code to indicate out of

service
path-interval-threshold cv 0 es 80 ses 10 sefs 0 css 0 uas 10 Note: Built-in T1 ports only
rx-sensitivity Short-haul Attenuation level of received

signal
trail-mode terminated No forwarding of T1 port

alarms toward TDM line
tx-clock-source Loopback Note: Built-in T1 ports only
Configuring T1 Ports
Configuring Built-in T1 Ports
 To configure T1 ports:
1. Configure the port to T1 mode (see Configuring E1/T1 Ports)
t1 <port>/<tributary>
The prompt config>port>t1(<port>/<tributary>)# is displayed.
Specifying out-of-service cas-oos-codes space • Space signaling code allowed

indication to transmit for T1 <space-code> mark <mark-code> range: 0x0–0xf
port with CAS signaling • Mark signaling code allowed
range: 0x0–0xf
Notes:
• This command is relevant only
with line type esf or sf(D4).
• When R bits and L bits are used to
indicate T1 CAS faults on the
remote side, the OOS code sent
to the T1 CAS interface is the
default (0xFF), rather than the
actual OOS code.
Specifying transmission cas-oos-pattern {space | mark | Note: This command is relevant only
sequence for out-of-service space-mark} with line type esf or sf(D4).
indication for T1 port with CAS
signaling
5-74 T1 Ports ETX-2

Specifying code transmitted to idle-code <idle-code-val> Possible values: 0x00–0xFF (default

fill idle (unused) timeslots in 0x7E)
the frames transmitted CAS idle-code has fixed value of 0x5
through the port (0101)
Specifying inband loopback inband-loopback {local | remote}

csu
inband-loopback {local | remote}
niu {fac1 | fac2}
inband-loopback {local | remote}
program <loop-up-code>
<loop-up-len>
<loop-down-code>
<loop-down-len>
Specifying TX gain of the DSL line-buildout {0db | -7dot5db • 0db: No db

line (dB), when line-interface | -15db | -22dot5db} • -7dot5db: -7.5 db
is set to csu
• -15db: -15 db
• -22dot5db: -22.5 db
Specifying the variety of zero line-code { ami | b8zs } • AMI – Referred to as Alternate
code suppression used for this Mark Inversion because a 1 is
port referred to as a mark and a 0 as a
space.
• B8ZS – Bipolar 8-zero
substitution, in which two
successive ones (bipolar
violations) are inserted whenever
the stream of user data contains
a string of eight or more
consecutive zeros. This insertion
is done in a way that allows each
of the 24 channels to carry 64
kbsp of data.
Specifying T1 operation mode line-interface {dsu | csu} • dsu – Digital Service Unit
• csu – Channel Service Unit
Specifying threshold at which line-interval-threshold es

to trigger threshold crossing <es-value >
alert for line ES (errored
seconds)
Specifying the length (in feet) line-length {0-133 | 134-266 |

of the T1 line, in DSU mode 267-399 | 400-533 | 534-655}
ETX-2 T1 Ports 5-75

Specifying the T1 line type line-type { unframed | esf | sf } • unframed – No framing (this type
is relevant only for built-in T1
ports)
• sf (D4) – Super Frame (12 T1
frames)
• esf – Extended Super Frame (24
T1 frames, with on-line
performance monitoring and
4 Kbps control data link)
Running loopback test on T1 loopback {local | remote } • local – returns the transmitted
port [duration <seconds>] data at the physical layer to the
receiving path
• remote – returns the received
data at the physical layer to the
transmitting path
seconds) until the loopback
starts. Possible values: 1 to 3600
stopped.
loopback test.
Defining the value to be out-of-service <oos> Possible values: 0x00–0xFF (default

transmitted if the 0xFF).
corresponding PW is out of If the corresponding PW is out of
service service, ETX-2 transmits the
configured value on a time slot that
is assigned to the PW toward the
TDM side (relevant only for framed
E1 ports).
Specifying thresholds at which path-interval-threshold

to trigger threshold crossing cv <cv-value> es <es-value>
alert for path ES (errored ses <ses-value>
seconds), SES (severely sefs <sefs-es-value>
errored seconds), SEFS css <css-value> uas <uas-value>
(severely errored framing
seconds), CSS (controlled slip
seconds), UAS (unavailable
seconds)
5-76 T1 Ports ETX-2


reporting is enabled for the
port
Specifying attenuation level of rx-sensitivity { short-haul |

the receive signal that is long-haul }
Specifying the port clock source-clock-quality {stratum1 | Clock quality used in adaptive clock
quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
Defining whether the T1 port trail-mode { extended | extended – ETX-2 forwards the E1
alarms are forwarded toward terminated } port alarms from the PW toward the
the TDM line TDM line.
terminated – ETX-2 does not forward
the E1 port alarms toward the TDM
line.
Selecting the transmit clock tx-clock-source {loopback | • loopback – clock retrieved from
source internal |domain <number> | the port's incoming (Rx) data
pw <number> } • internal – clock provided by
internal oscillator
domain, if device has timing
option
Note: After changing tx-clock-source,
in ETX205A, you are required to
reset the device.
Administratively disabling or shutdown Type no shutdown to administratively

enabling the port enable the port.
Displaying list of interfaces show bind

bound to port
Displaying loopback test show loopback

status
ETX-2 T1 Ports 5-77


show statistics interval
<interval-num>
show statistics all
Configuring Modular T1 Ports
 To configure T1 ports:
1. If the module type is not E1/T1, power off ETX-2, insert the E1/T1 module,
and then power on ETX-2.
2. Provision the module type as E1/T1 (see Configuring Module).
3. Configure the port to T1 mode (see Configuring E1/T1 Ports).
t1 [<slot>/]<port>/<tributary>
The prompt config>port>t1([<slot>/]<port>/<tributary>)# is displayed.
Specifying TX gain of the DSL line-buildout {0db | -7dot5db • 0db: No db

line (dB), in CSU mode | -15db | -22dot5db} • -7dot5db: -7.5 db
• -15db: -15 db
• -22dot5db: -22.5 db
This command appears in the CLI only
if rx-sensitivity is configured to
long-haul, which indicates CSU mode.
Specifying the variety of zero line-code { ami |b8zs } • AMI – Referred to as Alternate
code suppression used for this Mark Inversion because a 1 is
port referred to as a mark and a 0 as a
space.
kbsp of data.
Note: Only B8ZS can be configured
for modular T1 ports.
5-78 T1 Ports ETX-2

Specifying the length (in feet) line-length {0-133 | 134-266 | This command appears in the CLI only
of the T1 line, in DSU mode 267-399 | 400-533 | 534-655} if rx-sensitivity is configured to
short-haul, which indicates DSU
mode.
Specifying the T1 line type line-type { unframed |esf | sf } • unframed – No framing

• sf – Super Frame (12 T1 frames)
Note: Only esf can be configured for
modular T1 ports.
Running loopback test on T1 loopback {local | remote } • local – returns the transmitted
port [duration <seconds>] data at the physical layer to the
receiving path
transmitting path
Possible values: 1–3600
• duration – Specifies the duration
of the loopback (in seconds)
stopped.
loopback test.

reporting is enabled for the
port
Specifying attenuation level of rx-sensitivity { short-haul | short-haul indicates DSU mode.

the receive signal that is long-haul } long-haul indicates CSU mode.
Administratively disabling or shutdown Type no shutdown to administratively

Displaying list of interfaces show bind

bound to port

status
ETX-2 T1 Ports 5-79


<interval-num>
show statistics all
Configuring Smart SFP T1 Ports
 To configure smart SFP T1 ports:

1. Provision a smart SFP port with type MiRICi-T1 or MiTOP-T1 (see Smart SFPs).
2. Insert the MiRICi-T1/ MiTOP-T1 into the Ethernet port.
the Setting the Switches section in the Installation and Setup chapter of the
MiTOP E1T1 Installation and Operation manual.

type of smart SFP.
Task Command Possible Values MiRICi MiTOP
Specifying TX gain of the DSL line line-buildout { -7dot5db • -7dot5db: -7.5 db × 

(dB), when line-interface is set to | -15db | -22dot5db} • -15db: -15 db
csu
• -22dot5db: -22.5 db
Specifying the variety of zero code line-code { ami | b8zs } • AMI – Referred to as Alternate  
suppression used for this port Mark Inversion because a 1 is
referred to as a mark and a 0 as a
space.
kbsp of data.
Specifying T1 operation mode line-interface {dsu | csu} • dsu – Digital Service Unit × 
• csu – Channel Service Unit
5-80 T1 Ports ETX-2

Specifying the length (in feet) of line-length {0-133 | 134-266 |  

the T1 line 267-399 | 400-533 | 534-655}
Specifying the T1 line type line-type { unframed |esf | sf } • unframed – No framing (relevant  
only for MiTOP)
• sf – Super Frame (12 T1 frames)
Running loopback test on T1 port loopback {local | remote } • local – returns the transmitted  
[duration <seconds>] data at the physical layer to the
receiving path
transmitting path
stopped.
loopback test.
Assigning a name to the port name <string>  
Specifying if performance reporting pm-enable  

Specifying attenuation level of the rx-sensitivity { short-haul |  

receive signal that is compensated long-haul }
for by the interface receive path
Specifying the port clock quality source-clock-quality {stratum1 Clock quality used in adaptive clock × 
| stratum2 | stratum3 | recovery set according to parameter
stratum3e | stratum4} specified:
ETX-2 T1 Ports 5-81

Selecting the transmit clock source tx-clock-source {loopback | • loopback – clock retrieved from  
internal | domain <number> | the port's incoming (Rx) data
pw <number> } • internal – clock provided by
internal oscillator
domain, if device has timing
option
Note: The domain and pw options are
available only for MiTOP.
Administratively disabling or shutdown Type no shutdown to administratively  

Displaying list of interfaces bound show bind  

to port
Displaying loopback test status show loopback  
Displaying the port status show status  
Displaying the port statistics show statistics current  

<interval-num>
show statistics all
5.19 T3 Ports
T3, also referred to as DS-3 (Digital Signal Level 3), equates to 28 T-1 lines or
44.736 million bits per second (roughly 43-45 Mbps upstream/downstream
speeds). DS-3s have enough bandwidth to allow very large database transfers
over busy wide area networks.
Applicable Products
T3 ports are applicable to the ETX-2 products as follows:
 Smart SFP T3 ports are available when smart SFPs such as MiRICi-T3 or
MiTOP-T3 are provisioned (see Smart SFPs)
 Smart SFP T3 ports do not support encapsulation via VCG
 Smart SFP T3 ports are referenced as [<slot>/]<port>/<tributary>:
5-82 T3 Ports ETX-2

• ETX203AM with a T3 module:

 Modular T3 ports support encapsulation via VCG (see VCGs).
 Modular T3 ports are referenced as <slot>/<port>.
Standards
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
T3 lines enable high-capacity Ethernet services in remote locations and
transparently connect corporate LANs over existing PDH infrastructure.
In North America, DS-3 translates into T-3, which is the equivalent of 28 T-1
channels, each operating at 1.544 Mbps. Four T-1s are multiplexed to a T-2
frame, then seven T-2 frames are multiplexed, through an M23 (‘Multiplex 2-to-3’
multiplexer). As each frame is transmitted 8,000 times per second, the total T-3
signaling rate is 44.736 Mbps.
Factory Defaults
By default, no smart SFP T3 ports exist.
If a T3 module is inserted, the modular T3 ports have the following configuration.
line-length up-to-225ft
line-type c-bit-parity
name T3 <slot>/<port>
pm-enable pm-enable Performance monitoring is enabled
Configuring T3 Ports
Configuring Modular T3 Ports
 To configure modular T3 ports:

1. If the module type is not T3, power off ETX-2, insert the T3 module, and then
power on ETX-2.
2. Provision the module type as T3 (see Configuring Module).
ETX-2 T3 Ports 5-83


Specifying the length line-length { up-to-225ft | over-225ft }

(in feet) of the T3 line
Specifying type of T3 line-type { c-bit-parity } • c-bit-parity – The c-bit parity

line framing format is an enhancement
of the M13 application, providing
greater management and
performance functions.
Running loopback test loopback {local | remote } [start • local – returns the transmitted
on T3 port <seconds> ] [duration <seconds>] data at the physical layer to the
receiving path
transmitting path
seconds) until the loopback starts.
• duration – specifies the duration of
the loopback (in seconds).
stopped.
loopback test.
Assigning a name to the name <string>

port
Specifying if pm-enable
Selecting the transmit tx-clock-source {loopback | internal } • loopback – clock retrieved from the
clock source port's incoming (Rx) data
internal oscillator
Note: This command is relevant only if
the module has a single T3 port. In the
case of a module with two T3 ports,
the Tx clock source is configured at
the VCG port level (see Configuring
VCG Ports).
5-84 T3 Ports ETX-2

Administratively shutdown Type no shutdown to administratively

the port
Displaying list of show bind

interfaces bound to
port

status
Displaying the port show status

status
Displaying the port show statistics current

statistics show statistics interval <interval-num>
show statistics all
Configuring Smart SFP T3 Ports
 To configure smart SFP T3 ports:

1. Provision a smart SFP port with type MiRICi-T3 or MiTOP-T3 (see Smart SFPs).
2. Insert the MiRICi-T3/ MiTOP-T3 into the Ethernet port.
the Setting the Switches section in the Installation and Setup chapter of the
MiTOP E1T1 Installation and Operation manual.

type of smart SFP.
Specifying the line-length { up-to-225ft |  

length (in feet) over-225ft }
of the T3 line
ETX-2 T3 Ports 5-85

Specifying type line-type {m23 | c-bit-parity | • m23 – Four DS1 signals are are  
of T3 line unframed } multiplexed into one DS2 signal, then
seven DS2 signals are multiplexed into one
DS3 signal.
• c-bit-parity – The c-bit parity framing
format is an enhancement of the M13
application, providing greater management
and performance functions.
• unframed – No framing (relevant only for
MiTOP).
Running loopback loopback {local | remote } [start • local – Returns the transmitted data at the  
test on T3 port <seconds> ] [duration <seconds>] physical layer to the receiving path
• remote – Returns the received data at the
physical layer to the transmitting path
• start – Specifies the time (in seconds)
until the loopback starts.
• duration – Specifies the duration of the
loopback (in seconds).
If duration is not specified, the loopback
test runs forever, until stopped.
Use no loopback to disable the loopback test.
Assigning a name name <string>  

to the port
performance
reporting is
enabled for the
port
Specifying the source-clock-quality {stratum1 | Clock quality used in adaptive clock recovery × 
port clock quality stratum2 | stratum3 | stratum3e | set according to parameter specified:
stratum4} • stratum1 – PRC G.811
Selecting the tx-clock-source {loopback | internal | • loopback – clock retrieved from the port's  
transmit clock pw <number>} incoming (Rx) data
source • internal – clock provided by internal
oscillator
Note: The pw option is available only for
MiTOP.
5-86 T3 Ports ETX-2

Administratively shutdown Type no shutdown to administratively enable  

disabling or the port.
enabling the port

interfaces bound
to port
Displaying show loopback  

loopback test
status
Displaying the show status  

port status
Displaying the show statistics current  

port statistics show statistics interval
<interval-num>
show statistics all
Clearing the clear-statistics  

statistics
5.20 VCGs
VCG ports provide a logical link to modular E1/T1/T3 ports.
Applicable Products
This feature is applicable to ETX203AM with an E1/T1/T3 module.
Standards
ITU-T G.7042
ITU-T G.7043
Benefits
The VCG port provides a logical link to modular E1/T1/T3 ports.
A VCG (Virtual Concatenation Group) logical port is used to group the E1/T1/T3
ports that are available if the appropriate type of module has been provisioned
and inserted.
ETX-2 VCGs 5-87

By default, the Tx clock of the E1/T1/T3 ports in the module is the internal clock
provided by the internal oscillator of the module. You have the option of
selecting instead the loopback clock retrieved from the port's incoming (Rx) data,
as the Tx clock of the E1/T1/T3 ports.
Note
The VCG logical port is used only if the module contains multiple E1/T1/T3 ports,
and a GFP port is then bound to the VCG port. If a module with a single T3 port is
installed, the GFP port is bound directly to the T3 port.
Factory Defaults
By default, no VCG ports exist. When a VCG port is created, it is configured as
shown below.
lcas lcas LCAS enabled
minimum-number-of-links 1 Minimum number of links

when working with LCAS
name VCG <port>
shutdown no shutdown Administratively enabled
tx-clock-source internal Clock source for transmitted

data
Configuring VCG Ports
Note One VCG port is available in ETX-2.
 To configure VCG ports:

vcg <port>
config>port>vcg(<port>)# prompt is displayed.
Binding VCG port to E1 port bind e1 <slot>/<port> Note: Successful only if the
no bind e1 <slot>/<port> E1/T1 module is installed.
Binding VCG port to T1 port bind t1 <slot>/<port> Note: Successful only if the
no bind t1 <slot>/<port> E1/T1 module is installed.
Binding VCG port to T3 port bind t3 <slot>/<port> Note: Successful only if the T3
no bind t3 <slot>/<port> module is installed.
Enabling link capacity adjustment lcas

scheme (LCAS) no lcas
5-88 VCGs ETX-2

Enabling loop detection loop-detection Note: Relevant only in the case

no loop-detection of modular E1 ports.
Specifying minimum number of links minimum-number-of-links

when working with LCAS <links>

no name
Selecting the transmit clock source tx-clock-source {loopback | • loopback – clock retrieved
internal } from the port's incoming
(Rx) data
internal oscillator of the
E1/T1/T3 module
•
Administratively enabling port no shutdown Using shutdown disables the

port.
Displaying list of interfaces bound to show bind

the port
Displaying the VCG port status show status
Examples
 To configure VCG port 1 with module containing two E1 ports:
#*****ports E1 configuration***************************
configure port
e1 1/1
no shutdown
exit
e1 1/2
no shutdown
exit all
#*****ports GFP bind MAC configuration******************
configure port
vcg 1
bind e1 1/1
bind e1 ½
exit
gfp 1
bind vcg 1
exit
logical-mac 1
bind gfp 1
no shutdown
exit all
 To configure VCG port 1 with module containing two T3 ports:
ETX-2>config>port# vcg 1
ETX-2>config>port>vcg(1)$ bind t3 1/1
ETX-2 VCGs 5-89

ETX-2>config>port>vcg(1)$ bind t3 1/2

ETX-2>config>port>vcg(1)$ no shutdown
ETX-2>config>port>vcg(1)$ info detail
Name "VCG 1 "
no shutdown
bind t3 1/1
bind t3 1/2
tx-clock-source internal
lcas
minimum-number-of-links 1
ETX-2>config>port>vcg(1)$ show bind
Higher Layer
---------------------------------------------------------------
Lower Layer
---------------------------------------------------------------
T3 1
T3 2
5.21 VDSL2 Ports

ETX-2 is optionally equipped with a module having four VDSL2 ports (8-wire). The
VDSL2 interfaces are bundled into one PCS (physical coding sublayer) port. See
PCS Ports for commands related to the PCS port.
Applicable Products
This feature is applicable to ETX203AM with a VDSL2 module; operates in CPE
mode only.
Standards
ITU-T G.993.2, G.997.1, G.998.2
IEEE 802.3
Benefits
ETX-2 can aggregate traffic over the VDSL.bis links.
Very High Speed Digital Subscriber Line Transceivers 2 (VDSL2) is an access
technology that enables delivery of very high-speed internet access over copper
telephone lines – much higher than a conventional voice band modem can
provide.
VDSL2 main features include:
• Four VDSL2 ports
• One bonding group; supports up to four VDSL port(s)
5-90 VDSL2 Ports ETX-2

• Payload rate 100Mbps DL/ 50Mbps UL per line

• G.998.2 VDSL2 PTM (64/65-octet encapsulation) bonding
• Bonding payload rate up to 400Mbps DL/ 200Mbps UL, with packet
forwarding throughput 380Mbps DL/180Mbps UL
• Supports VDSL2 profiles 8a, 8b, 8c, 8d, 12a, 12b and 17a
• Operation frequency scope up to 17.7MHz
• Supports ADSL2/ADSL2+ fall back in PTM mode
• Comply ITU-T Rec. G.993.2 Annex A and Annex B power spectrum mask
• Supports two HW SKUs - one for POTS overlay, the other for ISDN overlay
• Supports Trellis coding and reed-Solomon code
• SRA (Seamless Rate Adaptation)
• Bit Swap
• Upstream power backoff (UPBO)
• Downstream power backoff (DPBO)
• RFI notch
• DMT as line coding
• G.INP (impulse noise protection)
• G.993.2 DELT
• G.993.5 vectoring system for NEXT and FEXT
• G.993.2 Amd 7, timing synchronization
• Dying Gasp
Configuring the VDSL2 Port Parameters

This section explains how to configure the VDSL2 port.
 To configure the VDSL2 port parameters

1. Navigate to configure port vdsl2 1/<port> to select the VDSL2port to
configure.
The config>port>vdsl2(1/<port>)# prompt is displayed.
Displaying port status show status See Viewing VDSL2 Port Status.
Displaying port statistics show statistics See Viewing VDSL2 Port Statistics.
Clearing the port statistics clear-statistics
Assigning port name name <string> Typing no name removes the port name.
ETX-2 VDSL2 Ports 5-91

Viewing VDSL2 Port Status

 To display the status of VDSL2 port 1:
ETX-2# config port vdsl2 1/1
ETX-2>config>port>vdsl2(1/1)# show status
Name : VDSL2-1/1
Transmission System : g9932AnnexB
Attainable Line Rate Downstream (Kbps) : 143439
Attainable Line Rate Upstream (Kbps) : 62592
Loop Attenuation (dB) : 0.2dB
SNR Margin (dB) : 9.2dB
Far-End Vendor ID : 26 00 52 41 44 00 00
00
Table 5-11. VDSL2 Status Information
Name Port name

Administrative Status VDSL2 line administrative status
Up or Down
Operation Status VDSL2 line operational status
Up or Down
Attainable Line Rate The maximum downstream net data-rate currently attainable on the
Downstream [Kbps] VDSL2 line, in Kbps
Valid only during VDSL2 line showtime
Attainable Line Rate Upstream The maximum upstream net data-rate currently attainable on the VDSL2
[Kbps] line, in Kbps
Valid only during VDSL2 line showtime
SNR Margin [dB] The average SNR margin
Far-end Vendor ID VTU-C vendor ID
Viewing VDSL2 Port Statistics

 To display the VDSL2 port statistics:
• At the config>port>vdsl2(1/<port>)# prompt, enter show statistics [{current |
interval |current-day | day} {interval-num<interval-num> | day-num<day-
num>}].
Relevant VDSL2 statistic parameters are displayed.
Example
 To display the VDSL2 current interval statistics for port 1:

ETX-2# config port vdsl2 1/1
ETX-2>config>port>vdsl2(1/1)# show statistics current
Current

---------------------------------------------------------------
Valid Intervals : 6 Invalid Intervals : 90
ES : 0 SES : 0
UAS : 0 FEC : 2
LOSS : 0
Table 5-12. VDSL2 Statistics Counters
Time Elapsed Total elapsed seconds for current interval/day
Monitored Time Total seconds for this historical interval
Interval Validity Indicates if the data for this historical interval is valid
Valid Intervals The number of 15-minute PM intervals for which data was
collected. The value is typically equal to the maximum number of 15-
minute intervals the implementation is planned to store, unless the
measurement was (re-)started recently, in which case the value is the
number of complete 15-minute intervals for which the agent has at
least some data. In certain cases (e.g., in the case where the agent is a
proxy), it is possible that some intervals are unavailable, in which case,
this interval is the maximum interval number for which data is available.
Invalid Intervals The number of 15-minute PM intervals for which no data is

available. The value is typically zero, except in cases where the data for
some intervals are not available (for example, in proxy situations).
ES Number of errored seconds during this interval
SES Number of severely errored seconds during this interval
UAS Number of seconds in Unavailability State during this interval
FEC Number of seconds with at least one FEC correction during this interval
LOSS Number of seconds that there was LOS during this interval
ETX-2 VDSL2 Ports 5-93


Chapter 6
Management and Security
6.1 Access Control List (ACL)

Access control lists are used to flexibly filter and mark management traffic.
Applicable Products
This feature is applicable to all ETX2 products, with the following condition:
• ETX203AM, ETX203AX, ETX205A, and ETX220A – ACL can be applied only
to management packets.
Standards
Relevant sections of RFC 1812
Benefits
Service providers use ACLs to maintain network security by preventing malicious
traffic from entering the device. ACLs can be used to save network resources by
dropping unwanted packets.
When management data is marked via ACLs, service providers can apply various
traffic management techniques to the marked packets, such as allocating more
bandwidth to a certain traffic type.
Devices featuring ACLs can flexibly filter management traffic, by denying or
permitting IP packets to enter the host, according to the packet’s
source/destination address, protocol type, or other criteria.
ACL entries are sequentially numbered rules containing statements (Deny, Permit,
or Remark) and conditions. Remarks are free-text ACL entries used for
commenting and visually organizing ACLs.
Packets are permitted or denied access, based on the following conditions:
• IP source and destination address or address range
• IP protocol
• TCP port – TCP/23 (TELNET), TCP/22 (SSH)UDP port – UDP/161 (SNMP)
ETX2 Access Control List (ACL) 6-1

Chapter 6 Management and Security Installation and Operation Manual
• ICMP type and code

The ACL structure is illustrated in the Example section.
If there is a need to add a rule between already existing rules with consecutive
numbers, the rules can be interspaced to accommodate additional rules between
them. For example, if you apply resequencing to an ACL including rules 1, 2, and
3, with an interspacing value of 30, the rule numbers will change to 30, 60 and
90. Sequence numbers can also be set at the rule level.
Binding Access Control Lists

Once created, ACLs are applied (bound) to the virtual management entity for
filtering management traffic. For the management entity, ACLs can be used in the
inbound direction only.
Only one IPv4 ACL is supported per management entity. An additional IPv6 ACL
may coexist with one IPv4 access list on the same management entity.
Filtering and Marking

Packets attempting to enter an entity to which the ACL is bound are checked
against the access list rules, one by one. Access of matching packets is denied
(packets are dropped) or permitted (packets are forwarded and possibly marked),
as directed by the ACL statement.
Packets matching a Deny statement (rule) are dropped unless permitted by a
previous rule.
Packets matching a Permit statement (rule) are permitted to access an entity
unless denied by a previous statement. Permit statements may also set the ToS
byte or Layer-2 priority of packets matching them.
When a rule match occurs, an entry is added to the event log if logging is
enabled. To prevent log overflow, it is possible to disable logging (per rule or
device) or define the minimal logging interval of packets matching ACL entries
(per device).
Note By default, logging is disabled. If you choose to enable it, the default logging
interval is five minutes.
Two packets matching the same rule on the same entity in the same direction are
logged only if the time between them exceeds the logging interval.
After a match, the rest of the rules are ignored. Packets not matching any rule
are dropped. Empty ACLs deny access of all packets matched to them.
Show Me Demo
6-2 Access Control List (ACL) ETX2

Installation and Operation Manual Chapter 6 Management and Security
Note If the video cannot be viewed, ensure that you have the latest version of Adobe
Reader.
Statistics
The device collects ACL statistics per management entity. The statistic counters
include the number of rule matches that occurred since the counters were last
cleared. The statistic counters are cleared upon device reboot. The user may also
clear ACL statistics of any entity.
Factory Defaults
Parameter defaults are alphabetically listed in the tables below.
Topic Parameter Default Value
Access Control logging minimum interval 300 (seconds)
Access List access-list type ipv4
All ACL Rules ACL statement sequence Highest number in use in the ACL plus 10
Management access-list direction in
Deny/Permit Rule dscp-value All values are filtered.
dst-port-range All values are filtered.
icmp-code All values are filtered.
icmp-type-number All values are filtered.
ip-precedence-value All values are filtered.
ip-protocol-number All values are filtered.
log Disable
sequence-number –
src-port-range All values are filtered.
Management access-list direction in
Configuring ACL
The ACL configuration tasks are performed at the access control and
management levels.
 To configure ACL:
1. Create an access control list.
2. Add deny and permit rules to the ACL.
3. Bind the ACL to a management entity.

4. Configure additional ACL parameters (logging interval, ICMP Unreachable

messages etc), if necessary.
Access-Control-Level Tasks
The following commands are available in the CLI access-control context:
config>access-control#. The exception to this are the deny, permit and remark
commands, which are performed in the access-list(acl_name) context:
configure>access-control>access-list(acl_name)#.
Table 6-1. Access-Control-Level Commands
Creating and access-list [{ipv4 | ipv6}] <acl_name> Creating an ACL is performed by assigning
deleting an ACL no access-list <acl_name> a name and specifying the ACL IP type.
The ACL names must be unique.
The ACL name contains up to
252 alphanumeric characters.
Adding deny deny {tcp | udp} {any | <src-address> [/<src- The arguments of the deny rule vary
rules to an ACL prefix-length>]} [<src-port-range>] any depending on the protocol (TCP, UDP).
[<dst-port-range>] [log] [sequence Management-bound ACLs have the
<sequence-number>] following configuration limitations:
• Only TCP- or UDP-based rules can be
defined.
• The destination IP address must be
any.
• For TCP/UDP, the destination port must
be tcp/23 (Telnet), tcp/22 (SSH), ,
udp/161 (SNMP), or any..
• The source port must remain any (i.e.
optional src-port-range field should not
be configured).
• DSCP and IP Precedence are not
supported.
log enables logging match events of the
rule into the event log and sending SNMP
traps.
Possible values for sequence:
1–2147483648.
Note: If the ACL already has a statement
with the same sequence number, the old
statement is replaced with the new one.

Adding permit permit {tcp | udp} {any | <src- The arguments of the permit rule vary
rules to an ACL address>[/<src-prefix-length>]} [<src-port- depending on the protocol (TCP, UDP).
range>] any [<dst-port-range>] [log] Management-bound ACLs have the
[sequence <sequence-number>] following configuration limitations:
• Only TCP- or UDP-based rules can be
defined.
• The destination IP address must be
any.
• For TCP/UDP, the destination port must
be tcp/23 (Telnet), tcp/22 (SSH),
udp/161 (SNMP) , or any..
• The source port must remain any (i.e.
optional src-port-range field should not
be configured).
• DSCP and IP Precedence are not
supported.
log enables logging match events of the
rule into the event log and sending SNMP
traps.
Possible values for sequence:
1–2147483648.
Note: If the ACL already has a statement
with the same sequence number, the old
statement is replaced with the new one.
Adding remarks remark <description> [sequence <sequence- The description contains up to 255
to an ACL number>] characters.
Reseqencing the resequence access-list <acl-name> Possible values for value: 1–100000
rules in an ACL [<value>]
Removing rules delete <sequence-number> Possible values for sequence-number:

from an ACL 1–2147483648.
Setting the logging access-list <value> Enable logging at the maximum rate of the
logging interval no logging access-list value set at Access Control level. <0> is
of all ACLs equivalent to no logging access-list
command.
no logging access-list disables event
logging for all rules in the ACL.
Management-Level Tasks
The following commands are available in the CLI management context:
configure>management>access#.

Table 6-2. Management-Level Commands
Binding the ACL access-group <acl-name> in The management entity supports the ACLs
to a no access-group in {ipv4 | ipv6} only in the in direction.
management When binding the ACL to the management
entity and entity, or when adding/editing rules in an
defining the ACL ACL that is bound to the management
direction entity, the rules must conform to the
following limitations:
• The protocol rules must be of TCP/UDP
type.
• The destination address must be set to
any.
• The source port must be set to any.
• The destination port must be tcp/23
(Telnet), tcp/22 (SSH), udp/161
(SNMP), or any.
• DSCP, IP precedence, and P-bit cannot
be used.
Displaying ACL show access-list statistics See Displaying Statistics below.

statistics
Clearing ACL clear-statistics access-list

statistics
Displaying the show access-list summary Displays ACL status at the current level
summary of ACLs See Displaying Status below.
bound to a
management
entity
Examples
Management ACL
 To create management ACL:

The example below illustrates a typical ACL applied to the incoming management
traffic:
• Allows SSH (TCP port 22) traffic from any source
• Denies and logs incoming Telnet (TCP port 23) connections from any source,
except for 192.168.1.0 subnet
access-control>access-list(mng)#
remark Allow incoming SSH traffic
permit tcp any any 22
remark Allow Telnet traffic coming from 192.168.1.0 subnet
permit tcp 192.168.1.0/24 any 23
remark Deny and log incoming Telnet traffic
deny tcp any any 23 log

The table below summarizes the rules configured for the ACL. Items in red are
either implied or unavailable for the current parameter or serve as system
settings that cannot be changed. The deny rule appearing in the bottom row is a
system rule that is used to deny all non-compliant data.
Sequence Action Protocol Source IP TCP/UDP Dest. IP TCP/UDP Dest. Port Log
Number Source Port
10 Permit TCP Any Any Any 22 No
20 Permit TCP 192.168.1.0/24 Any Any 23 No
30 Deny TCP Any Any Any 23 Yes
40 Deny IP Any N/A Any N/A No
Table 6-3 lists the messages generated by the device when a configuration error
is detected.
Message Description
Cannot execute; invalid statement Invalid matching rule. For example, binding the ACL with a rule,
using a protocol other than TCP or UDP to the management
entity.
Cannot add statement; sequence Invalid sequence number of the rule. Allowed sequence number
number out of range range is 1–2147483648.
Cannot resequence; sequence number Resequencing has failed because the ACL interspace value is
out of range invalid.
Cannot clear; no such router interface Statistic counters cannot be cleared on the non-existing router
interface.
Cannot bind; no such access list A non-existing ACL cannot be bound to the router interface or
the management entity.
Cannot show; no such router interface Statistic counters cannot be displayed on the non-existing
router interface.
Cannot bind; invalid statement An access list with statements, which are not supported by the
management ACL, cannot be attached to the management
entity.
Displaying Status
The ACL status displays information on the ACL name, type (IPv4 or IPv6), and the
entity that the ACL is bound to. The status information is available for the ACLs at
the management access levels.
 To display the ACL status (management):

• In the config>mngmnt>access# prompt, enter the show access-list summary
command.

The following status information is displayed:

ACL Name Type Bound to Direction
---------------------------------------------------------------
MNG_port_1 IPv4 management inbound
Displaying Statistics
The ACL statistic counters gather information on the number of rule matches
registered on the ACL since the last reboot or counter clearing.
Note All ACLs have an implied last rule that denies all packets. The device does not
provide statistic counters for this rule. If you intend to collect statistics on the
number of packets discarded by the default ACL mechanism, you must add the
deny ip any any rule at the end of the ACL.
 To display the ACL statistics (management):

• In the config>mngmnt>access# prompt, enter show statistics ipv4 access-list
(for IPv4) or show statistics ipv6 access-list (for IPv6).
The following statistic information is displayed:
IPv4 access list: MNG_port_1 (in)
Bound to: Management
Matches counted for: 0 days 0 hours 2 minutes 33 seconds
---------------------------------------------------------------
10 permit tcp 172.17.154.154/24 any 22 log (0 matches)
20 permit tcp 172.17.154.154/24 any 23 log (0 matches)
30 permit udp 172.17.154.154/24 any 161 log (0 matches)
6.2 Access Policy

The access policy allows specifying up to three user authentication methods
(local, RADIUS, TACACS+). If an authentication method is not available, the next
method is used if applicable.
Applicable Products
This feature is applicable to all ETX2 products.
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.
6-8 Access Policy ETX2

Specifying authentication via locally auth-policy 1st-level local

stored database
Specifying authentication method auth-policy 1st-level tacacs+ [2nd-level { If 2nd-level is set to local, authentication is
preferably via TACACS+, then local | none } ] performed via the TACACS server. If the
optionally local TACACS server does not answer the
authentication request, then ETX2
authenticates via the local database. .If the
TACACS server rejects the authentication
request, ETX2 ends the authentication
process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
Specifying authentication method auth-policy 1st-level radius [2nd-level ETX2 first attempts authentication via the
preferably via RADIUS/ TACACS+, then tacacs+ [3rd-level {local | none}]] server specified by 1st-level. If the server
optionally TACACS+/ RADIUS, then auth-policy 1st-level tacacs+ [2nd-level does not answer the authentication
optionally local radius [3rd-level {local | none}]] request, then ETX2 attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then ETX2
attempts to authenticate according to
3rd-level:
• local – ETX2 authenticates via the local
database
• none – No further authentication is
done, and the authentication request is
rejected.
Note: If at any time in this process, an
authentication server rejects an
authentication request, ETX2 ends the
authentication process and does not
attempt authentication at the next level.
6.3 Management Source IP Address

The management source IP address provides a single point of contact for
management applications that interface with ETX2.
When a router interface responds to management packets, the responding
packet source IP address is set to the router interface IP address. If the router
interface sends a management packet that is not a response, the packet source
IP address is set to the ETX2 management source IP address. If the management
source IP address is not configured or the corresponding router interface is
down, the packet source IP address is set to the router interface IP address. You
can configure a single management source address for IPv4 and IPv6 to be used
ETX2 Management Source IP Address 6-9

in all client management applications, including: SNMPv3 (for trap), Radius,

Tacacs+. Syslog, SNTP, TFTP, and SFTP.
 To configure the management source IP address:

1. Navigate to configure management.
The config> mngmnt# prompt is displayed.
2. Type:
management-address <ip-address>
Note According to the format of the IP address (IPv4 or IPv6), it is saved as the IPv4 or
IPv6 management source IP address.
The management source IP address is set to the specified IP address.

3. To delete the IPv4 or IPv6 management address, type:
no management-address {ipv4 | ipv6}
6.4 Management DSCP Value

The management packets transmitted by the router have a configurable DSCP
value, so that each router entity can control its traffic priority by setting its DSCP
value for its management protocols. (Refer to Traffic Processing chapter to
configure the DSCP value for control packets.)
 To configure the management DSCP value:

1. Navigate to configure management.
The config> mngmnt# prompt is displayed.
2. Type dscp <dscp-value>. dscp-value can be 0-63.
6.5 Authentication 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.
Applicable Products
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS)
6-10 Authentication via RADIUS Server ETX2

RFC 2618, RADIUS Authentication Client MIB
Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device in the
network.
Due to its generic nature, the RADIUS protocol can easily be used by service
providers and enterprises to manage access to the Internet, internal networks,
wireless networks, and integrated email services. These networks may
incorporate DSL, access points, VPNs, network ports, and more.
RADIUS servers have built-in mapping of users to service-types (Table 6-4). Note
that each user has the rights of all users above it. All users have default password
1234. It is highly recommended to change the default password when setting up
your device (Refer to Changing Password on how to change a password).
Table 6-4. RADIUS Service-Types
Name Prompt RADIUS Service-Type (User Access Level)
user ETX2% 1 (login)
tech ETX2% 7 (NAS prompt)
oper ETX2# 8 (authenticate only)
su ETX2# 6 (administrative)
When a user attempts to log in to ETX2, the following occurs:

1. User is prompted to enter their username and password.
2. RADIUS client submits an authentication request to the RADIUS server. The
username and encrypted password is transmitted over the network. (A hash
code is generated over the entered password and a previously defined shared
secret (string of free text) is transmitted between the RADIUS server and
ETX2 unit.)
3. The RADIUS server verifies the user information against a database stored at
the RADIUS server, and sends one of the following responses:
 Access Rejected – User is not authenticated and access to all resources is
denied. User is prompted to reenter their username and password.
 Access Accepted – User is authenticated. Access to the requested
network resources is granted. The RADIUS service type is sent, indicating
what services the user can access.
ETX2 Authentication via RADIUS Server 6-11

Verifying credentials and privileges via RADIUS data base
Logon request to ETX-203AX
Network
Logging on to ETX-203AX or
returning authentication error ETX-203AX
RADIUS Server
Management Work Station Access accepted or denied
Shared Secret
Figure 6-1. RADIUS Server Operation Scheme
Factory Defaults
By default, no RADIUS servers are defined. When the RADIUS server is first
defined, it is configured as shown below.
IP address of server 0.0.0.0
Key Empty string
Max number of authentication attempts 3
Time interval between two authentication attempts 3 seconds
UDP port used for authentication 1812
Configuring RADIUS Parameters

ETX2 provides connectivity to up to four RADIUS authentication servers. You
have to specify access parameters such as Radius server ID, associated server IP
address, the number of allowed authentication request attempts, etc.
 To define a RADIUS server:

1. At the config>mngmnt>radius# prompt, type server <1..4> to specify which
server to configure.
The config>mngmnt>radius>server(<1..4>)# prompt is displayed.
2. Enter the necessary commands according to the tasks listed below.
Assigning an IP address to the server address <ip-address> A valid unicast IP address
6-12 Authentication via RADIUS Server ETX2

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.
The hash keyword denotes that
the string is hashed, rather than
clear text; usually it is added by
the device after hashing the clear
text that the user enters, before
saving it in the database.
If you enter the password as a
text string, do not use the hash
parameter. Use it only if you are
specifying the password as a
hashed value (obtained by using
the info command to display
RADIUS data).
Defining the number of authentication retry <number-of-retries> Possible values: 0–10

request attempts
Defining timeout (in seconds) for timeout <seconds> Possible values: 1–5
response from RADIUS server
Defining the UDP port to be used for auth-port <udp-port-number> Possible values: 1–65535
authentication
Administratively enabling server no shutdown Type shutdown to

administratively disable the
server.
Displaying status show status
Viewing RADIUS Statistics

 To display RADIUS statistics:
• At the config>mngmnt>radius# prompt, enter:
show statistics
RADIUS statistics appear as shown below.
ETX2>config>mngmnt>radius# show statistics
Server1 Server2 Server3 Server4
--------------------------------------------------------------------------
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
ETX2 Authentication via RADIUS Server 6-13

Timeouts :0 0 0 0
Unknown Types :0 0 0 0
Packets Dropped :0 0 0 0
 To clear the statistics for RADIUS:

• At the config>mngmnt>radius# prompt, enter:
clear-statistics
The RADIUS statistics are cleared.
6.6 Authentication 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.
Applicable Products
Standards
TACACS+ Protocol Version 1.78 (IETF draft-grant-tacacs-02)
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.
Customers do not have to adapt their TACACS+ server privilege levels to RAD CLI
default values; CLI levels can be remapped in accordance with the customer’s
TACACS+ levels.
Factory Defaults
By default, no TACACS+ servers are defined. When the TACACS+ server is first
defined, it is configured as shown below.
Parameter Default Value
key “” hash
retry 1
6-14 Authentication via TACACS+ Server ETX2

timeout 5 seconds
authentication-port 49
accounting-port 49
Administrative status shutdown
Accounting group membership no group
TACACS+ is a protocol that provides access control for routers, network access
servers, and other networked computing devices via one or more centralized
servers. TACACS+ is based on the AAA model:
• Authentication – The action of determining identity of a user
• Authorization – The action of determining what a user is allowed to do. It can
be used to customize the service for the particular user.
• Accounting – The action of recording what a user is doing, and/or has done
Note TACACS+ performs authorization according to the user level; it does not send
each command to the server for authorization.
The TACACS+ client can be configured to use authentication/authorization with or

without accounting functionality.
When configuring users on external TACACS+ servers, see Table 6-5 to define
authorization levels for ETX2 standard users. Note that each user has the rights
of all users below it, in addition to those explained in its description.
Table 6-5. TACACS+ Authorization Levels
Level User Allowed Actions Description
3 user Monitoring Commands that do not affect

services, traffic, or configuration
6 tech Diagnostics Commands that may affect services

and traffic, but are not saved in the
database
9 oper Configuration Commands that change

configuration parameters
permanently
12, 15 su User management Commands that manage users in the

database
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
ETX2 Authentication via TACACS+ Server 6-15

• The access client is an entity which seeks the services offered by the
network.
• TACACS+ client, running on ETX2, processes the requests from the access
client and passes this data to TACACS+ server for authentication.
• TACACS+ server authenticates the request, and authorizes services over the
connection. The TACACS+ server does this by matching data from the
TACACS+ client`s request with entries in a trusted database.
TACACS+ server decides whether to accept or reject the user's authentication or
authorization. Based on this response from the TACACS+ server, the TACACS+
client decides whether to establish the user's connection or terminate the user's
connection attempt. The TACACS+ client also sends accounting data to the
TACACS+ server to record in a trusted database.
TACACS+ uses TCP for its transport and encrypts the body of each packet.
TACACS+ client and server can agree to use any port for authentication and
accounting. TACACS+ supports authentication by using a user name and a fixed
password.
Accounting
ETX2 supports up to five accounting groups, with up to five TACACS+ servers per
group. However, each TACACS+ server can be bound to a single accounting group
only.
A group can be defined with its own accounting level:
• Shell accounting, which logs the following events:
 Successful logon
 Logon failure
 Logoff
 ETX2 - terminated management session
• System accounting, which records system events/alarms registered in local
log file
• Command accounting, which logs the following events:
 Any shell command that was successfully executed by ETX2
 Any level that was successfully changed in a shell
Note The password that you enter when creating a new user (configure management
login-user <name> password <password>, or when copying a file (file copy
<source-file-url> <destination-file-url> sftp://<username>:<password>) is masked
in TACACS+ under CLI command accounting. The password entered appears in the
TACACS+ command log as asterisks (*), thus providing protection from sniffers.
Mapping Privilege Levels

ETX2 supports software configuration of mapping CLI levels to TACACS+ privilege
levels.
• There are 16 TACACS+ privilege levels.
• You can map a CLI level to multiple TACACS+ levels.

• You cannot map a TACACS+ level to multiple CLI levels. If the command is
repeated for a TACACS+ level, the new mapping replaces the old one.
• You can unmap both TACACS+ and CLI levels, with the exception of su, which
must be mapped to at least one TACACS+ level.
Configuring TACACS+ Server

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

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 the TCP port to be used for accounting-port <port-number> Possible values: 1–65535
accounting
Defining the TCP port to be used for authentication-port <port-number> Possible values: 1–65535
authentication
Binding accounting group to TACACS+ group <string> no group detaches accounting

server group from server.
Defining a non-disclosed string (shared key <string> [hash] The shared secret is a secret
secret) used to encrypt the user key consisting of free text
password known to the client and the
server for encryption.
The hash keyword denotes
that the string is hashed,
rather than clear text; usually
it is added by the device after
hashing the clear text that
the user enters, before saving
it in the database.
If you enter the password as
a text string, do not use the
hash parameter. Use it only if
you are specifying the
password as a hashed value
(obtained by using the info
command to display TACACS+
data).

Defining the number of authentication retry <number-of-retries> Permanently set to 1

request attempts
Defining timeout (in seconds) for timeout <seconds> Possible values: 1–30
response from TACACS+ server
Administratively enabling server no shutdown shutdown administratively

disables the server.
Displaying statistics show statistics
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]
Notes • You can enter any combination of the parameters shell, system, or commands,
but you must enter at least one of them
• Type no accounting to disable TACACS+ accounting for the group.
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.
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.
Mapping CLI Levels to TACACS+ Privilege Levels

 To map a CLI level to a TACACS+ privilege level:
At the config>mngmnt>tacacsplus# prompt, type
privilege-level <tacacs-privilege-level> {su|oper|tech|user}.
The tacacs-privilege-level value can be 0-15.
Note Type no privilege-level <tacacs-privilege-level> to remove TACACS+ privilege level

mapping.

Example – Defining Server

The example below illustrates the procedure for defining a TACACS+ server.
• Server IP address: 175.18.172.150
• Key: TAC_server1
exit all
configure management tacacsplus
server 175.18.172.150
key TAC_server1
no shutdown
exit all
save
 To display the configuration from the above example:

ETX2# configure management tacacsplus server 175.18.172.150
ETX2>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89225048C6571135EF" hash
retry 1
timeout 5
accounting-port 49
no group
no shutdown
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
exit all
configure management tacacsplus
group TAC1
accounting shell system commands
exit
server 175.18.172.150
group TAC1
exit all
 To display the configuration from the above example:

ETX2# configure management tacacsplus server 175.18.172.150
ETX2>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89829AB8AB0FE50885" hash
retry 1
timeout 5
accounting-port 49
group "TAC1"
no shutdown

Example – Mapping CLI Level to Privilege Level

 To map TACACS+ level 7 to the CLI user level:
ETX2# configure management tacacsplus privilege-level 7 user
 To delete the mapping of TACACS+ level 7 to the CLI user level:

ETX2# configure management tacacsplus no privilege-level 7
The following table lists the messages generated by ETX2 when a configuration
error is detected.
su level must be mapped to a You tried removing the last Leave at least one mapping of su.
TACACS+ level mapping of su, but su must be
mapped to at least one
TACACS+ level.
Viewing TACACS+ Statistics

 To display TACACS+ statistics:
• At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, type:
show statistics.
The TACACS+ statistic counters are displayed.
ETX2>config>mngmnt>tacacsplus>server(175.18.172.150)$ 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
Table 6-7. TACACS+ Statistic Counters
Counter Description
Requests Number of authentications performed toward a specific TACACS+ server
Request Timeouts Number of transaction timeouts that occurred between the client and
server
Unexpected Responses Number of times the TACACS+ client receives a TACACS+ packet that is
not expected at that time. Usually, this occurs due to a delayed response
to a request that has already timed out

Counter Description
Server Error Responses Number of errors received from the TACACS+ server
Incorrect Responses Number of times the TACACS+ client:

• Fails to decrypt the packet
• Detects an invalid field in the TACACS+ packet
• Receives a response that is not valid according to the initial request
Transaction Successes Number of successful transactions between the client and TACACS+
server
Transaction Failures Number of times the TACACS+ client’s request is aborted by the TACACS+
server or the server fails to respond after maximum retry is exceeded
Pending Requests Number of TACACS+ client’s requests minus number of TACACS+ server
responses or timeouts
 To clear TACACS+ statistics:

• At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, type:
clear-statistics
TACACS+ statistic counters are set to 0.
6.7 Control Port

You can configure the control port parameters, which include specifying the data rate,
security terminal timeout, console timeout, and screen size from which you are
accessing the device.
Applicable Products
ETX2 enables you to configure the following:
• Login timer – timer for local management login after login failure. In terminal
timeout, you configure the minimum amount of time that must pass before
you can log in after failed login attempts.
• Inactivity timer – Timer for local management session. In terminal console-
timeout, you configure the maximum amount of time that a CLI session on
the local console can be without activity, before it is automatically
disconnected.
ETX2 Control Port 6-21

Factory Defaults
baud-rate 9600 bps
console-timeout limited 10 (minutes)
timeout limited 10 (minutes)
length 20
Configuring Control Port Parameters

 To define the control port parameters:
1. Navigate to configure terminal.
2. At the config>terminal# prompt, enter the necessary commands according to
the tasks listed below.
Specifying the desired data rate baud-rate { 9600bps | 19200bps | The control port data rate of ETX205A with
38400bps | 57600bps | 115200bps PMC should be set to 9600 bps or higher to
be compatible with the x86 terminal.
Setting console inactivity timeout console-timeout {forever | limited forever – no timeout

<minutes>} minutes – maximum number of minutes that
CLI session can be without activity before
device disconnects.
Specifying the number of rows to length <number-of-rows> The number of rows to print before
display pausing, or 0 for no pausing (i.e. no limit on
the number of lines displayed).
Setting terminal timeout timeout {forever | limited <minutes>} forever – no timeout

minutes – maximum number of minutes of
inactivity before terminal disconnects
Note: This command does not affect local
console sessions.
6.8 DHCP Relay

A device can function as DHCP client and relay at the same time.
This section describes the DHCP relay component, including how it receives,
intercepts, and forwards DHCP requests and replies not destined to the device
itself.
6-22 DHCP Relay ETX2

Note Packets sent from or to the device itself are not related to the DHCP relay
functionality.
You can enable the following Layer-2 DHCP Relay agent features on your device
or on specific services of your device:
• DHCP Snooping – Configuration of servers and relay ports as trusted, and
client ports as untrusted.
• DHCP Option 82 – Add additional information to the DHCP request, including
Remote ID and Circuit ID.
Note DHCP Relay applies to DHCPv4 only.
Standards
[RFC 1542] — Clarifications and Extensions for the Bootstrap Protocol
[RFC 2131] — Dynamic Host Configuration Protocol
[RFC 2132] — DHCP Options and BOOTP Vendor Extensions
[RFC 3046] — DHCP Relay Agent Information Option
Benefits
• Layer-2 DHCP Snooping verifies DHCP transactions and protects against rogue
DHCP servers and clients.
• The DHCP server uses the Remote ID and Circuit ID information provided by
DHCP option 82 for the address allocation scheme.
A DHCP relay agent at Layer-2 forwards requests and replies between clients and
servers that are on the same Layer-2 subnet but not on the same physical
subnet. Unlike normal Layer-2 forwarding, in which IP datagrams are switched
transparently, a relay agent receives DHCP messages and generates new ones to
send on output interfaces.
DHCP servers are assumed to reside in trusted locations, usually beyond network
ports, while DHCP clients reside in untrusted locations, usually behind user ports.
Each port is configured as either DHCP trusted or untrusted (refer to the Cards
and Ports chapter - configuration of dhcp-trust parameter in Ethernet, LAG,
Logical MAC, and PCS ports).
The device can be configured with two DHCP functionalities:
• DHCP Snooping
• DHCP Option 82
DHCP Messages
The following table [per RFC 2131] describes the various DHCP client and server
messages:
ETX2 DHCP Relay 6-23

Table 6-8. DHCP Messages
Message Use Sent By
DHCPDISCOVER Locate available servers. Client
DHCPOFFER Offer configuration parameters in response to DHCPDISCOVER. Server
DHCPREQUEST Accept, confirm, or extend an offer, implicitly declining others. Client
DHCPACK Commit client request. Server
DHCPNAK Decline client request. Server
DHCPDECLINE Indicate that the committed address is already in use. Client
DHCPRELEASE Relinquish address and cancel remaining lease. Client
DHCPINFORM Ask for configuration; address has been externally configured. Client
DHCP Snooping
DHCP relay supports DHCP snooping on the device (or specific services), for
added security. Servers and relay ports should be configured as trusted, and
client ports as untrusted.
In addition to verifying the validity of incoming DHCP messages, when enabled,
the DHCP relay does the following:
• Blocks server DHCP messages (DHCPOFFER, DHCPACK, and DHCPNACK)
arriving from untrusted ports; allows from trusted ports.
• Blocks client DHCP messages (DHCPDISCOVER, DHCPREQUEST, DHCPDECLINE,
DHCPRELEASE and DHCPINFORM) when they arrive from trusted ports; allows
from untrusted ports.
• Forwards DHCP server packets only to untrusted ports and DHCP client
packets only to trusted ports.
• DHCP snooping over a specific EVC is indicated by its Service ID (configured
over all EVC flows).
DHCP Option 82
The device (or specific services) can also be configured to enable DHCP option 82
(the relay agent information option). If enabled, upon intercepting a client DHCP
packet the relay agent adds option 82 to the DHCP request before forwarding the
packet to the DHCP server.
The following information is added to the DHCP request:
• Remote ID – the agent identification; usually agent MAC address
• Circuit ID – usually identification of the port and VLAN of the switch from
which the request was received.
Note The format of the Remote ID and Circuit ID suboptions is configurable.
The reply from the server is forwarded back to the client after removing option
82.

Figure 6-2 describes the flow of DHCP packets through a relay when option 82 is
enabled.
1. The DHCP client broadcasts a DHCP request.
2. The DHCP relay agent intercepts the request, and performs a sanity check on
the packet.
3. If it is not valid, it discards the message.
4. Otherwise, if it is valid, inserts option 82 in the packet and broadcasts it
towards the DHCP server. Option 82 information includes the two configured
suboptions: Circuit ID and Remote ID.
5. The DHCP server assigns an IP address based on the option 82 suboptions
and sends a lease back to the client.
6. The relay agent performs a sanity check on the packet and strips option 82
(Remote ID and Circuit ID fields) off the packet before forwarding the packet
to the client.
Figure 6-2. – DHCP Relay Agent Process
Factory Defaults
By default, no DHCP relay parameters are configured for ports. The system DHCP
relay parameters have the default values shown in the following table.
dhcp-option-82 no dhcp-option-82
dhcp-snooping no dhcp-snooping
Configuring DHCP Relay

DHCP relay is configured as follows:
• System level – DHCP relay features (Option 82 and snooping) must be
enabled or disabled for the entire device or a specific service.
• Port level – For each port through which DHCP packets can be received and
sent (Ethernet, internal Ethernet, LAG, Logical MAC, and PCS), the device
supports configuration of the port as DHCP trusted or untrusted.
ETX2 DHCP Relay 6-25

• The snooping functionality can be enabled for all ingress traffic from the
ports or to traffic of specific services as configured in dhcp-snooping (see
table below).
• Refer to port configuration sections in Cards and Ports chapter to set port
dhcp-trust/untrust.
System Parameters
This section explains how to enable or disable DHCP Option 82 and DHCP
Snooping for the device.
You can enable DHCP Option 82 and DHCP Snooping globally for the entire device
(i.e. all services) or for a specific service. You can repeat the command for each
service on which to enable the feature.
Note If a feature is enabled for all services, the feature applies to all services,
regardless of service-specific configuration. If it is not enabled for all services, it
applies only to those services for which it was explicitly enabled.
It is possible to enable DHCP option 82 for the entire device, but set the format
of its sub-options (Circuit ID and Remote ID) either globally or per service.
You can disable these features on all services using the no form of the command.
 To configure DHCP relay system parameters:
1. Navigate to configure system dhcp-relay.
The config>system>dhcp-relay# prompt is displayed.

Enabling DHCP option 82 dhcp-option-82 {all | service <service-name>} service – the service on which to
[circuit-id {vlan-card-port | string <circuit-id- enable option 82
string>}] [remote-id {mac | hostname | string Possible values: all, service name (1-
<remote-id-string>} 31 characters)
no dhcp-option-82 {all | service <service-name>} circuit-id – circuit ID format
Possible values: vlan-card-port
(default) , string (0-253 characters)
remote-id – remote ID format
Possible values: mac (default),
hostname (SNMP sysName), or
string (0-253 characters)
Notes:
• If hostname is chosen, if SNMP
sysName is > 253 characters, or
if SNMP sysName > 253
characters is configured while it
is in use by option 82, the
following message is displayed:
Only first 253 characters of
hostname are used in DHCP
option 82 remote ID.
• Option 82 suboptions format
can be configured for a specific
service to be different from the
global configuration; however,
option 82 cannot be disabled on
a specific service if it is globally
enabled.
• Both circuit-ID and remote-ID
suboptions are always sent if
option 82 is enabled.
Enabling DHCP snooping [no] dhcp-snooping {all | service <service-name>} service – the service on which to
enable snooping.
Possible values: all, service name (1-
31 characters)
all – All ports traffic is subjected to
snooping functionality.
6.9 Point-to-Point Protocol over Ethernet (PPPoE)

The Point-to-Point Protocol (PPP) provides a standard method for transporting
multi-protocol packets over point-to-point links. PPP over Ethernet (PPPoE) is
used to encapsulate PPP packets over Ethernet. It allows ETX2 to connect to a
ETX2 Point-to-Point Protocol over Ethernet (PPPoE) 6-27

remote access concentrator to establish a PPPoE session, and then build a PPP
link to the peer at the other end of the PPP link.
Applicable Products
Standards
RFC 1332 – The PPP Internet Protocol Control Protocol (IPCP)
RFC 1334 – PPP Authentication Protocols
RFC 1661 – The Point-to-Point Protocol (PPP)
RFC 1994 – PPP Challenge Handshake Authentication Protocol (CHAP)
RFC 2516 – A Method for Transmitting PPP Over Ethernet (PPPoE)
RFC 5072 – IP Version 6 over PPP
Benefits
PPPoE in ETX2 is used to establish a management channel through which an IP
address can be acquired and the unit can be managed. You can connect ETX2 to
a central server for authentication and to acquire an IP address, and establish a
management channel that a remote management system can use to send
software and configuration files and manage ETX2.
PPPoE consists of the following stages:
• Discovery
• PPP Session
Discovery
ETX2 locates a remote access concentrator by broadcasting a request to initiate
a PPPoE session. The request can contain a user-configurable service name (sent
as empty string if service name has not been configured). When an access
concentrator answers the request and the PPPoE initiation message sequence is
performed successfully, the PPPoE session can be established.
If ETX2 cannot establish the session due to timeout (after a set number of
retries), or if the session is terminated or rejected by the access concentrator,
ETX2 restarts the session initiation process.
PPP Session
After discovering the access concentrator, ETX2 builds a PPP link with the remote
peer, in the following stages:
• Link Control Protocol (LCP) Negotiation
• Authentication
6-28 Point-to-Point Protocol over Ethernet (PPPoE) ETX2

• Internet Protocol Control Protocol (IPCP) Negotiation
Link Control Protocol (LCP) Negotiation

The LCP negotiation is used to establish with the peer the link encapsulation
options, packet size, error detection, termination options, etc.
If timeout occurs during LCP negotiation (after a set number of retries), or if LCP
negotiation is terminated or rejected, ETX2 restarts the LCP negotiation process.
Authentication
ETX2 does not attempt to authenticate the PPP peer, but does respond to a
peer that requires authenticating ETX2.
The following authentication methods are supported (you can specify whether to
refuse a particular method if it is offered by the peer):
• Challenge Handshake Authentication Protocol (CHAP) – This is the
recommended authentication method if authentication is being performed, as
the username and password are not sent in clear text.
If CHAP authentication is performed, ETX2 receives a challenge from the
peer, and authenticates as follows:
 If the user name in the challenge matches a configured user, ETX2 uses
the login-user and its password.
 If the user name in the challenge does not match any of the configured
users, ETX2 uses the default CHAP password. If no default CHAP
password has been configured, the CHAP authentication fails.
• Password Authentication Protocol (PAP) –This authentication method is less
secure, as the username and password are sent in clear text. If the PAP
username and password have not been configured, ETX2 cannot perform
PAP authentication.
• No authentication
If authentication should be performed, ETX2 sends an authentication request to
the peer according to the method being performed, and the peer responds
accordingly.
If timeout occurs during authentication, ETX2 retries the authentication. After a
set number of retries, ETX2 terminates the PPPoE session, and then restarts the
session initiation process as described in Discovery.
If the peer rejects the authentication request, ETX2 terminates the PPPoE
session, and then restarts the session initiation process as described in
Discovery.
Internet Protocol Control Protocol (IPCP) Negotiation

Before it can send IP packets over the PPP connection, ETX2 has to negotiate
IPCP with the peer.
If timeout occurs during IPCP negotiation or the negotiation is rejected, ETX2
retries the negotiation for a set number of retries; if the retries fail, then ETX2
restarts the IPCP negotiation process. If IPCP negotiation is terminated, ETX2
restarts the IPCP negotiation process.

Configuring PPPoE and PPP Entities

In order for PPPoE and PPP to function, you configure a PPP port bound to an SVI
port, to bind to a router interface; additionally you configure incoming and
outgoing flows over the SVI port. You can bind one ETX2 router interface to a
PPP port. See Example for a PPPoE configuration example.
Factory Defaults
By default, no PPP port exists. When a PPP port is created, it is configured as
shown below.
Parameter Description or value
name PPP <ppp-port-num>, e.g. PPP 1 for PPP port 1
no refuse-chap Do not refuse CHAP authentication.
refuse-no-auth Refuse skipping authentication.
refuse-pap Refuse PAP authentication.
no service-name Service name is not configured.
Configuring PPP Port

 To configure the PPP port:
1. Navigate to configure port ppp <ppp-port-num> to select the PPP port to
configure.
The config>port>ppp(<ppp-port-num>)# prompt is displayed.
Binding PPP port to SVI bind svi <port-number>
Defining host name to send to PPP chap-hostname <name> If the CHAP host name is not configured,
peer if CHAP authentication is used ETX2 identifies itself by its device name
(assigned via the name command in the
system level).

Defining default password for CHAP chap-password <password> [hash] The default CHAP password is used for
authentication authentication if the username in a
received CHAP challenge does not match
any of the defined users.
The hash keyword denotes that the
string is hashed, rather than clear text;
usually it is added by the device after
hashing the clear text that the user
enters, before saving it in the database.
If you enter the password as a text
string, do not use the hash parameter.
Use it only if you are specifying the
password as a hashed value (obtained
by using the info command to display
PPP data).
Defining name of PPP port name <string>
Defining user name and password for pap-username <name> password <password> See above comments about the hash
PAP authentication [hash] parameter.
Specifying whether to refuse CHAP refuse-chap • If you do not want ETX2 to use CHAP
authentication if it is offered by the authentication for the PPP session,
peer enter refuse-chap.
• If you do want ETX2 to use CHAP
authentication if offered by the peer,
enter no refuse-chap.
Specifying whether to refuse not using refuse-no-auth • If you do not want ETX2 to skip
authentication (i.e. whether to refuse authentication for the PPP session,
skipping authentication), if that is enter refuse-no-auth.
offered by the peer • If you do want ETX2 to skip
enter no refuse-no-auth.
Specifying whether to refuse PAP refuse-pap • If you do not want ETX2 to use PAP
authentication if it is offered by the authentication for the PPP session,
peer enter refuse-pap.
• If you do want ETX2 to use PAP
enter no refuse-pap.
Displaying PPP port status show status See Viewing PPP and PPPoE Status.
Entering PPPoE level pppoe
Commands in pppoe level
Defining service name for PPPoE service-name <string> If the service name is configured, ETX2
session accepts PPPoE offers only if the service
name in the offer matches.
Displaying PPPoE status show status See Viewing PPP and PPPoE Status.

Example
 To configure for PPPoE:
• Bind to SVI 1, router interface 1.
• Authentication – CHAP or PAP must be used.
 CHAP hostname=ETXCHAP, default password=ppp1
 PAP username=ETXPAP, password=ppp1
• Incoming flow: Untagged, ingress ETH 6, egress SVI 1
• Outgoing flow: Untagged, ingress SVI 1, egress ETH 6
exit all
configure
port
# Configure SVI 1
svi 1
no shutdown
exit
# Configure PPP port
ppp 1
bind svi 1
chap-hostname ETXCHAP
chap-password ppp1
pap-username ETXPAP password ppp1
no refuse-chap
no refuse-pap
refuse-no-auth
exit
exit
flows
# Configure classifier to match untagged packets
classifier-profile untagged match-any
match untagged
exit
# Configure incoming flow
flow ppp_in
classifier untagged
egress-port svi 1
no shutdown
exit
# Configure outgoing flow
flow ppp_out
classifier untagged
ingress-port svi 1
no shutdown
exit
exit
# Configure router interface bound to PPP port
router 1
interface 1
bind ppp 1
ipv6-autoconfig

no shutdown
exit
exit
# Save configuration
save
exit all
Viewing PPP and PPPoE Status

 To view the PPP port status:
• At the config>port>ppp(<ppp-port-num>)# prompt, type:
show status
The PPP port status is displayed as shown below (based on the
configuration from Example).
ETX2# configure port ppp 1
ETX2>config>port>ppp(1)# show status
Name : PPP 1
Router Interface : Router 1/If 1

Physical Port : svi 1
LCP
-----------------------------------------------------------------------------
state : Opened
MRU Local : 1500 Peer : 1500
Authentication
-----------------------------------------------------------------------------
Of Us : CHAP State : Completed Identity : admin
IPCP
-----------------------------------------------------------------------------
State : Opened
Local IPv4 address : 22.22.22.22 Negotiated
Peer IPv4 address : 10.0.0.1
IPV6CP
-----------------------------------------------------------------------------
State : Opened
Local IPv6 address : fe80::d31:494c:56c:71b0 Negotiated
Peer IPv6 address : fe80::8828:1bab:8cf5:2477

Global IPv6 address : 2001:db8::284d:3190:e15a:e814
 To view the PPPoE status:

• At the config>port>ppp(<ppp-port-num>)>pppoe # prompt, type:
show status
The PPPoE status is displayed as shown below (based on the
configuration from Example).
ETX2>config>port>ppp(1)# pppoe
ETX2>config>port>ppp(1)>pppoe# show status
Router Interface : Router 1/If 1
Physical Port : svi 1

State : Up
Service Name Requested :
6.10 SNMP Management

Simple Network Management Protocol (SNMP) is an application layer protocol
that provides a message format for communication between managers and
agents.
ETX2 and PMC support SNMPv3, the latest SNMP version to date. SNMPv3
provides secure access to devices in the network by using authentication and
data encryption.
Applicable Products
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
• 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
6-34 SNMP Management ETX2

• RFC 3414, User-based Security Model for SNMPv3

• RFC 3416, Update for RFC 1904
Benefits
SNMP allows you to remotely manage multiple units from a central workstation
using a network management system.
SNMPv3 allows data to be collected securely from SNMP devices. Confidential
information such as SNMP commands can thus be encrypted to prevent
unauthorized parties from being able to access them.
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 reports information via SNMP back to the
managing workstations.
Factory Defaults
The following is the default configuration of the SNMP parameters (see
Configuring SNMPv3 Parameters for explanations of the parameters):
• SNMP engine ID set to device MAC address
• View named “internet” providing access to IETF MIBs and IEEE MIBs
• User named "initial", with security level no authentication and no privacy
• 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"
• Notifications with tag “unmasked” for the device traps
Configuring SNMPv3 Parameters

SNMP version 3 provides secure SNMP access to the device by authenticating and
encrypting packets transmitted over the network.
The SNMPv3 manager application in RADview-EMS provides a user-friendly GUI
interface to configure SNMPv3 parameters. If you intend to use it, you must first
use the device CLI to create users with the required encryption method and
security level, as the application can create users based only on existing users;
the new user has the same encryption method, and the same security level or
lower. The ETX2 default configuration provides one standard user named “initial”
with no encryption and the lowest security level (see Factory Defaults for
details).
A Network Management Station (NMS) relies on traps in order to display device
alarms. As traps are not reliable, the NMS needs to be aware which traps got lost
ETX2 SNMP Management 6-35

and be able to ask a device to resend them. This mechanism is called trap
synchronization.
NMSs (targets; such as RADview or third party) may be organized into trap sync
groups in order to provide redundancy between these NMSs. You can define the
tags and target parameters in each trap sync group – for example, you can define
one trap sync group for critical alarms such as linkDown and coldStart, and
another group for all other traps.
Each trap is sent to all targets attached to the group, and therefore it is
recommended to set identical traps masking for all group members.
Notes • ETX2 supports up to two trap synchronization groups.

• A single trap synchronization group can support multiple NMS.
• If you would like all NMS to receive all traps, there is no need to configure trap
synchronization groups.
Follow this procedure 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 views.
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 ETX2
should send trap notifications), specifying target parameter sets, 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.
Note When you enter password parameters, they should contain at least eight
characters.
Task Command Level Comments
Configuring access-group <group-name> { snmpv2c | usm } snmp Using no access-group

group { 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

match the entire context.
context sent in prefix – Match the first
frames by the part of the context.
NMS
Note: ETX2
automatically identifies
the NMS context,
therefore you can
configure exact match.
Normally prefix is used
for devices with
multiple instances.
Setting view for notify-view <name> snmp>access-group See the description of

traps the view command for
information on how to
Setting view read-view <name> snmp>access-group
limit the parts of the
with read-only
MIB hierarchy that the
access
view can access.
Setting view write-view <name> snmp>access-group
with write
access
Administratively no shutdown snmp>access-group Using shutdown

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

community
Configuring name <community-string> snmp>community

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

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

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

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

notification
Assigning trap bind <trap-name> snmp>notify You can assign more

to notification than one trap to a
notification, in
separate commands.

Assigning tag to tag <tag-value> 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

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

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

whether traps with trap variables
with trap belonging to the
variables MIB subtree are
belonging to sent.
the MIB subtree • excluded – Traps
are sent 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 –

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

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

enabling
notification
filter profile
Connecting security-to-group { snmpv2c | usm } snmp Using

security name sec-name <security-name> no security-to-group
to group (e.g. removes
connecting user security-to-group
or community entity.
to group)
Specifying group-name <group-name> snmp>security-to-group

group to which
to connect
security name
Administratively no shutdown snmp>security-to-group Using shutdown

enabling disables the
security-to-grou security-to-group
p entity entity.
Setting SNMP snmp-engine-id mac [ <mac-address> ] snmp If you use the mac
engine ID, as snmp-engine-id ipv4 [ <ip-address> ] option and don’t
MAC address or specify the MAC
snmp-engine-id text <string>
IP address or address, the SNMP
string engine ID is set to the
device MAC address.
If you use the ipv4
option and don’t
specify the IP address,
the SNMP engine ID is
set to the device IP
address.
Configuring target <target-name> snmp Using no target

target (SNMPv3 removes target.
network
manager)

Specifying address udp-domain <ip-address> snmp>target

target address address oam-domain <oam-port>
as IP address or
OAM port
Assigning tag(s) tag-list <tag> snmp>target If you specify more

to target (the tag-list [ <tag> ] than one tag, you must
tag(s) must be enclose the list in
tag-list [ <tag1> <tag2>…<tagn> ]
defined in quotes; however, if you
notification are specifying just one
entries) tag, the quotes are
optional.
Specifying set target-params <params-name> snmp>target

of target
parameters for
target
Specifying the trap-sync-group <group-id> snmp>target • If the group does

trap not exist, it is
synchronization created.
group to be • Enter no
associated with trap-sync-group
the SNMP <group-id> to
target (NMS) remove the
manager (NMS)
from the group. If
the removed
manager was the
last to be
associated with the
trap-sync-group,
the group is
automatically
deleted.
• ETX2 supports up
to two trap
synchronization
groups.
Administratively no shutdown snmp>target Using shutdown

enabling target disables the target.
Configuring set target-params <target-param-name> snmp Using no target-params

of target removes target
parameters, to parameters.
be assigned to
target

Specifying message-processing-model { snmpv2c | snmpv3 } snmp>target

message
processing
model (SNMP
version) to be
used when
generating
SNMP messages
for the set of
target
parameters
Specifying user security [ name <security-name> ] snmp>target

on whose [ level { no-auth-no-priv | auth-no-priv | auth-priv } ]
behalf SNMP
messages are
to be generated
for the set of
target
parameters
Specifying version { snmpv2c | usm } snmp>target Use usm for SNMPv3

SNMP version to version.
be used when
generating
SNMP messages
for the set of
target
parameters
Administratively no shutdown snmp>target Using shutdown

enabling target disables target
parameters parameters.
Configuring trap-sync-group <group-id> snmp The trap

target synchronization group
parameters and must be previously
tags for trap defined at the target
synchronization level.
group
Specifying tags tag-list <list> snmp>trap-sync-group To remove the tag list,

in trap-sync- enter: no tag-list.
group
Specifying set target-params <params-name> snmp>trap-sync-group To remove the set of

of target target parameters,
parameters in enter: no
trap-sync-group target-params
<params-name>.

Configuring user user <security-name> snmp If you don’t specify the

[md5-auth [ {des | aes128 | none} ] ] authentication method
user <security-name> [sha-auth [ {des | aes128 | none} ] ] when creating a user,
the default is MD5 with
user <security-name> [none-auth]
DES privacy protocol.
To create a user with
no authentication,
specify none-auth.
Typing
no user <security-name
> deletes the user.
Setting user authentication [ password <password> ] snmp>user Using

authentication [ key <key-change> ] no authentication
password and disables the
optional key for authentication
changes protocol.
Setting user privacy [ password <password> ] [ key <key-change> ] snmp>user Using no privacy
privacy disables privacy
password and protocol
optional key for Note: Password
changes minimum length is 10
for AES128 and 8 for
DES.
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).
• Using shutdown
disables the user.
Defining access view <view-name> <sub-tree-oid> snmp view-name – name of

to a particular view, which can be
part of the MIB associated to a group
hierarchy 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 mask <mask> snmp>view The mask is comprised

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

whether access to the subtree.
to the MIB excluded – Do not
subtree is allow access to the
allowed subtree.
Administratively no shutdown snmp>view

enabling view
Displaying trap show trap-sync snmp

synchronization
groups and
members for
SNMPv3
manager groups
Displaying show snmpv3 information snmp

SNMPv3
information,
such as the
number of
times the
SNMPv3 engine
has booted, and
how long since
the last boot
Examples
 To create an SNMPv3 user and connect it to group:
• User named “MD5_priv”:
 Security level – MD5 authentication, DES privacy
• Group named "MD5Group":
 All security levels
 Contains set of views named "internet" (from default configuration)
exit all
configure management snmp
#********* Configure user MD5_priv with authentication method MD5 with DES privacy protocol

user MD5_priv md5-auth des

privacy password MD654321
authentication password MD654321
no shutdown
exit
#******** Configure access group MD5Group with various authentication and privacy options
access-group MD5Group usm no-auth-no-priv
context-match exact
read-view internet
write-view internet
notify-view internet
no shutdown
exit
access-group MD5Group usm auth-no-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit
access-group MD5Group usm auth-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit
#******** Connect user MD5_priv to group MD5Group

security-to-group usm sec-name MD5_priv
group-name MD5Group
no shutdown
exit all
save
 To create notifications:
• Notification named “TrapPort”:
 Tag=“Port”
 Bound to ethLos, sfpRemoved
• Notification named “TrapPower”:
 Tag=“Power”
 Bound to powerDeliveryFailure, systemDeviceStartup
exit all
#******** Configure notification TrapPort
notify TrapPort
tag Port
bind ethLos
bind sfpRemoved
no shutdown
exit
#******** Configure notification TrapPower

notify TrapPower
tag Power
bind powerDeliveryFailure
bind systemDeviceStartup
no shutdown
exit all
save
 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
exit all
#******** Configure target parameters TargParam1
target-params TargParam1
message-processing-model snmpv3
version usm
security name MD5_priv level auth-priv
no shutdown
exit
#******** Configure target TargNMS1

target TargNMS1
tag-list “port power”
address udp-domain 192.5.4.3
no shutdown
exit
 To create communities, target parameters, and target for network devices that
are working with SNMPv1:
• Community “read”:
 Name: “public”
 Security name: “v1_read” (defined in default configuration)
• Community “write”:
 Name: “private”
 Security name: “v1_write” (defined in default configuration)
• Community “trap”:
 Name: “public”
 Security name: “v1_trap” (defined in default configuration)

• Target parameters named “snv1”:

 Message processing model SNMPv1
 Version SNMPv1
 Security name: “v1_trap”
 Security level: no authentication and no privacy
• Target named “NMSsnmpv1”:
 Target parameters “snv1”
 Tag list=“unmasked”
 IP address 192.5.6.7
exit all
#******** Configure communities
snmpv3
community read
name public
sec-name v1_read
no shutdown
exit
community write
name private
sec-name v1_write
no shutdown
exit
community trap
name public
sec-name v1_trap
no shutdown
exit
#******** Configure target parameters

target-params snv1
version snmpv1
security name v1_trap level no-auth-no-priv
no shutdown
exit
#******** Configure target

target NMSsnmpv1
target-params snv1
tag-list unmasked
no shutdown
exit all
save
 To display SNMPv3 information:

ETX2# configure management snmp
ETX2> config>mngmnt>snmp# show snmpv3 information
SNMPv3 : enable
Boots : 2

Boots Time (sec) : 102

EngineID : 800000a4030020d2202416
 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
exit all
#******** Configure targets and trap synchronization group
target NMS1
trap-sync-group 1
exit
target NMS2
trap-sync-group 1
exit
target NMS3
trap-sync-group 2
exit
target NMS4
trap-sync-group 2
exit
trap-sync-group 1
tag-list “port power”
exit all
save
 To display trap synchronization configured in above example:

ETX2>config>mngmnt>snmp# show trap-sync
Group ID Member
---------------------------------------------------------------
1 NMS1
1 NMS2
2 NMS3
2 NMS4
6.11 User Access

ETX2 management software allows you to define new users, and their
management and access rights. You can also view connected users, their details,
and their failed login attempts.
ETX2 User Access 6-47

Applicable Products
Factory Defaults
By default, the following users exist, with default password 1234:
• su
• oper
• tech
• user
The default users cannot be deleted, but can be disabled (shut down).
ETX2 supports the following four user access levels:
• Superuser (su) can perform all the activities supported by the system,
including creating new users, changing its and other user access levels and
passwords, deleting and disabling other users.
• Operator (oper) can perform all the activities, except for defining, deleting or
disabling other users.
• Technician (tech) can monitor the device (info, show status, show statistics).
• User (user) can monitor the device (info, show status, show statistics).
The regular users (oper, tech, user) cannot define, delete or disable other users,
or change their own access levels. They are allowed to change their current
passwords. All users can view all CLI levels.
Password Hashing
You can specify a user’s password as a text string or as a hashed value, that you
obtain by using info detail 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, 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.
SSH Authentication
ETX2 supports management by SSHv2, enabling user authentication using one of
two methods:
6-48 User Access ETX2

• Password (default) – ETX2 has default usernames and passwords.

• Public key (1024-bit RSA) – more robust and secure
Configuring Users
 To add a new user:
1. Verify that you are logged on as superuser (su).
2. Navigate to the management context (config>mngmnt).
3. Enter login-user, followed by a new user name if you intend to create a new
user, or an existing name, if you intend to change previously defined user.
Note Maximum user name length is 20 characters.
4. The prompt changes to config>mngmnt>login-user<user-name>#.

5. Enter the necessary commands according to the tasks listed in the table
below.
Specifying user authentication-method The default user authentication method is

authentication method {password | public-key} password. ETX2 has default usernames and
passwords.
If you change the authentication method of a
user with access level su to public key, and no
public key has been defined, you are warned
that the super user is going to be disabled,
and prompted to confirm the operation.
Note: You can create a public key, by
configuring config>mngmnt>login-user<user-
name> public-key <public-key>. Alternately,
you can create a public key using any
application that supports SSHv2 RSA 1024-bit
key generation.
Defining a user access level { su | oper | tech | user }

level
Specifying user password password <password> [hash] Maximum password length is as follows:
• Non-hashed – 20 characters
• Hashed – 40 characters
The use of hash function is illustrated in the
example below.

Setting user public key for public-key <public-key> Public key configuration is relevant only for the
authentication public key authentication method.
Public key format: “ ssh-rsa <space> public key
string <space> comment “ [1..512 chars]
Use the Base64 encoding (ASCII ‘A’ to ‘Z’, ‘a’
to ‘z’, ‘0’ to ‘9’, ’+’, ‘/’ and ‘space’) for the
public key configuration.
Entering no public-key deletes the public key.
Note: ETX2 does not have default public keys.
Enabling/disabling a user shutdown Default users (su, oper, tech, user) can be
no shutdown disabled, but cannot be deleted.
Deleting a User
 To delete an existing user:
1. Verify that you are logged on as superuser (su).
2. Navigate to the management context (config>mngmnt).
3. Enter no login-user, followed by the name of the user that you intend to
delete.
Viewing Users
 To display all connected users:
• At the config>mngmnt# prompt, 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.
ETX2>config>mngmnt# show users
Num User Access Level Source IP Address
-----------------------------------------------------------------------------
1. su Su Terminal 0.0.0.0
Viewing User Information

The details of the currently logged-in users are available in the show users-details
screen.
The screen for show users-details provides the following information:
User User name
Level User access level
Popup Alarm/event popup status (enabled or disabled)

From Source IP address of the management session, followed by

protocol type (serial, Telnet, SSH)
For (sec) Duration of the current management session in seconds
Connected To Destination IP/ protocol type of the active client Telnet

session (to a remote device)
For (sec) Duration of the active client Telnet session (to a remote
device) in seconds
 To display the user information:

• In the configure>management# prompt, enter show users-details.
ETX2>config>mngmnt# show users-details
From:1.1.1.1/SSH For(sec):120
User:123456 Level:oper Popup:Disabled
From:100.100.100.100/Telnet For(sec):120
Connected To:1111:2222:3333:4444:5555:6666:7777:8888/Telnet For(sec):100
User:su Level:su Popup:Enabled
From:Serial For(sec):94
Viewing SSH Server Information

You can display the fingerprint of the SSH server public key.
 To display the SSH server information:

• At the config>mngmnt# prompt, enter show ssh-server fingerprint.
The SSH fingerprint information stored on the SSH server is displayed.
ETX2>config>mngmnt# show ssh-server fingerprint
RSA key fingerprint is ef:ab:28:81:53:c2:a3:8d:77:0d:06:e7:89:2b:81:9c
Viewing Failed Login Attempts

You can view failed login attempts to the device.
 To display failed login attempts:

• At the config>mngmnt# prompt, enter show failed-login-attempts.
ETX2>config>mngmnt# show failed-login-attempts
Recent Failed Login Attempts
Source Attempts First Attempt Blocked for

-------------------------------------------------------
1.1.1.1 5 302 seconds ago 277 seconds
100.100.100.100 2 100 seconds ago --

Table 6-9. Failed Login Attempts Parameters
Source Source that failed login due to wrong username or password

Possible values: Local Console, <IP address>
Attempts Number of failed login attempts since the source was last unblocked
Possible values: <number>
First Attempt The first failed login attempt recorded from the source
Possible values: <number> second
Blocked for Time remaining until the source will be unblocked from login
Possible values:
-- (if the source is not blocked)
<number> seconds (if the source is blocked)
Example
Defining Users
 To define a new user:

• User name – staff
• Access level – su
• Password – 1234
exit all
configure management
login-user staff
level su
password 1234
no shutdown
exit
 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 detail 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)
exit all
login-user staff1

level su
password 4222
no shutdown
exit
exit all
configure management login-user staff1 info detail
level su
password "3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
no shutdown
exit all
login-user staff2
level su
no shutdown
exit
exit all
configure management login-user staff2 info detail
level su
no shutdown


Chapter 7
Resiliency and
Optimization
This chapter describes features related to resiliency and optimization:
• Ethernet Linear Protection
• Ethernet Ring Protection (ERP)
• Fault Propagation
• Link Aggregation
• Link Protection
7.1 Ethernet Linear Protection

ETX-2 provides bidirectional and unidirectional protection switching for network
ports per ITU-T G.8031, optionally using APS protocol.
The triggers are:
• Port signal loss
• CCM LOC, RDI, or interface status TLV indicating interface down
• ETH-AIS
The protection time is as follows:
• One EVC pair – 50ms protection
• Four EVC pairs – 200ms protection
Applicable Products
• PCS port is relevant to ETX203AM with an SHDSL or VDSL2 module, and
ETX203AX with embedded SHDSL ports.
Standards
ITU-T G.8031
ETX-2 Ethernet Linear Protection 7-1

Chapter 7 Resiliency and Optimization Installation and Operation Manual
Benefits
The Ethernet linear protection provides a way to protect the flows belonging to
an EVC.
The protection is based on an EVC Termination Point (ETP). An ETP has one
subscriber port and one or more transport ports. Multiple transport ports are
used for protection only. There are two kinds of flows connected to the ETP
ports, subscriber flows and transport flows.
• Subscriber flows run between UNIs and ETP subscriber port. You can define
classification and policing on subscriber flows, as well as marking.
• Transport flows run between ETP transport ports and NNIs. You can define
actions such as push, pop, and marking on transport flows.
Note You can define transport flows between ETP transport ports and logical MAC
ports corresponding to MiRICi-155 smart SFPs.
Flows entering the ETP assign an internal CoS value to every frame using mapping
profiles (priority-to-CoS) or by setting fixed CoS values.
Flows exiting the ETP perform queuing based on the internal CoS value using
mapping profiles (CoS-to-queue).
ETP Flow Attributes

The following table shows which attributes you can configure for ETP flows.
Table 7-1. ETP Flow Attributes
Attribute Subscriber Subscriber Transport Transport

(UNI to ETP) (ETP to UNI) (NNI to ETP) (ETP to NNI)
Ingress port Required Required Required Required
Egress port Required Required Required Required
Classifier profile Required, with any type of Required, with Required, with Required, with
criteria criteria: criteria: criteria:
Unclassified or SP VLAN Unclassified
VLAN
Policer profile Optional Optional Not allowed Not allowed
Queue / block Not allowed Required, with Not allowed Required, with
queue mapping queue mapping
profile classified by profile classified
CoS by CoS
CoS Required, with CoS Not allowed Required, with Not allowed
mapping profile CoS mapping
profile
VLAN tag (push) Optional Not allowed Not allowed
7-2 Ethernet Linear Protection ETX-2

Installation and Operation Manual Chapter 7 Resiliency and Optimization
Attribute Subscriber Subscriber Transport Transport

(UNI to ETP) (ETP to UNI) (NNI to ETP) (ETP to NNI)
Mark Required, with marking Required, with CoS For at least one For at least one of
profile classified by CoS mapping profile of the actions, the actions,
CoS mapping marking profile
profile classified by CoS
VLAN tag (pop) Not allowed Optional Not allowed
Drop Optional Optional Optional Optional
EVC Protection Switching

EVC protection (1:1) is based on the ETP model. One of the transport ports is the
working transport entity and the other port serves as the protection transport
entity.
Monitoring both working and protection transport entity is done via MEPs
exchanging CCMs. In addition, the protection transport optionally runs APS
protocol.
When working without APS, switchover is affected by local events only (signal
failure trigger, switch back to port after failure ends, manual switchover due to
command). In one-to-one bidirectional mode, upon switchover both the EVC Rx
and Tx flows move to the second path.
Master and Slave ETPs

You can define one master ETP and several slave ETPs. The master ETP must have
all the configuration of the protection, same as single ETP. The slave ETPs point
to the master ETP via master command and bind each port ID to
working/protection.
The master ETP index MUST be lower than the index of the slave ETPs. You must
create the master ETP before creating the slave ETPs.
Management over ETP

ETX-2 can be managed via a router interface connected to the ETP subscriber
port.
EVC and OAM

On each transport entity, you must define a MEP to use as the signal failure
trigger if working in APS mode, in order to monitor the connection using CCM.
The MEPs must be activated so that the protection switching mechanism can
monitor both working and protection transport entities. Monitoring can be
accomplished by exchanging CCMs as defined in ITU-T Rec. Y.1731. In non-APS
mode, the signal failure trigger can be a MEP or port status.
In addition, the MEP can be defined to perform other Y.1731 services such as
measuring delay and loss on the specific EVC. If an Up MEP associated with the
transport is associated with an untagged classifier profile, services can still be
defined for it; the Up MEP is transparent to the CVLAN, and the OAM transmitted
from the ETP transport ports can be edited according to the SVLAN.

EVC Fault Propagation

You can define fault propagation based on EVC failure detection (ETP operation
status) to shut down the UNIs that connect to it. The fault trigger can be one of
the following:
• In case of protection – the signal failure trigger MEP for ETP transport ports
• In other cases – the NNI operation status
EVC Loopback
You can activate a loopback on any of the transport ports toward the network
and on the subscriber port toward the user or network.
In most cases you would activate a loop on the subscriber port toward the
network, thus you can loop the EVC traffic without affecting protection.
If you wish to run a loop on a specific EVC path when you activate the loop on
the transport ports, you have two options:
• Loopback on a transport port affects OAM, as any traffic EVC path
redundancy is triggered if present.
• Loopback only data without affecting redundancy.
Factory Defaults
By default, no ETPs are configured.
When you create an ETP port, by default it is configured as follows:
• Name = “ETP <etp-name> Subscriber Port <port-index>” or
““ETP <etp-name> Transport Port <port-index>”, according to whether port is
subscriber or transport
• Administratively enabled
When you first enter the ETP protection level, by default the protection is
configured as follows:
ETX-2#configure etps etp ETP1 protection
ETX-2>config>etps>etp(ETP1)>protection$ info detail
shutdown
no master-etp
mode bi-directional-1-to-1
no aps-protocol
revertive
wait-to-restore 300
ETX-2>config>etps>etp(ETP1)>protection$
Configuring ETPs
This section describes how to configure ETPs.
 To configure ETPs:
1. Navigate to configure etps etp <name> to select the ETP to configure.

The ETP is created if it does not already exist, and the

config>etps>etp(<name>)# prompt is displayed.
Configuring ETP port port {subscriber | transport} <port-id> Use the no form to remove the port.
The port-id range is 1–2.
See the procedure below for more
information on configuring ETP ports.
Configuring ETP protection protection See Configuring ETP Protection for more
information.
Displaying ETP status show status
Displaying ETP statistics show statistics running
Displaying flows show flows-summary

corresponding to ETP
Clearing ETP statistics clear-statistics
 To configure ETP ports:

1. Navigate to configure etps etp <name> to select the ETP to configure.
The config>etps>etp(<name>)# prompt is displayed.
2. Type the following command to configure a port, where port-index can be 1
for subscriber ports, or 1–2 for transport ports:
port {subscriber | transport} <port-index>
The prompt is displayed according to whether you typed subscriber or
transport:
config>etps>etp(<name>)>port(subscriber/<port-index>)#
config>etps>etp(<name>)>port(transport/<port-index>)#
Activating loopback loopback [local | remote] [duration <seconds>]
Assigning name to ETP port name <string>
Displaying loopback status show loopback
Administratively enabling no shutdown Entering shutdown disables the port.

ETP port Note: When the port is created, it is
enabled by default.
Configuring ETP Protection

To configure ETP protection, you define the working and protection ports, as well
as other protection parameters.

 To configure ETP protection:

1. Navigate to configure etps etp <name> protection to configure protection for
the selected ETP.
The config>etps>etp(<name>)>protection# prompt is displayed.
Defining APS protocol for ETP aps-protocol
Defining transport port ID for bind {protection | working} transport

protection or working port <protection-port>
Clearing the active near end clear

lockout of Protection, Forced
Switch, Manual Switch, WTR
state, or Exercise command
Forcing normal traffic signal to force-switch

be selected from the
protection transport entity,
meaning jump to next port
even if it is down
Preventing a working signal lockout

from being selected from the
protection transport entity,
effectively disabling the
protection group
Forcing normal traffic signal to manual-switch

be selected from the
protection transport entity in
the absence of failure of
working or protection transport
entity, meaning jump to next
port only if it is not down
Defining master ETP master-etp <etp-name>
Configuring protection mode mode {uni-directional-1-plus-1 | uni-directional-1-plus-1 – provides 1:1

bi-directional-1-plus-1 | bi-directional-1-to-1} unidirectional protection
bi-directional-1-plus-1 – not supported
bi-directional-1-to-1 – provides 1:1
bidirectional protection
Indicating if mode is revertive revertive

Defining signal failure trigger sf-trigger { protection | working } port You can use MEPs from flows other
ethernet [<slot>/]<port-index> than the ETP transport flows.
sf-trigger { protection | working } port
logical-mac <port-number>
sf-trigger { protection | working } mep
<md-id> <ma-id> <mep-id>
sf-trigger { protection | working } port pcs
<port-number>
Defining time between wait-to-restore <seconds>

recovery and resumption of
transmission
Displaying protection status show status
Administratively enabling ETP shutdown

protection
Examples
 To configure an ETP:
• Name = ETP1
• Port members = subscriber 1, transport 1, transport 2
exit all
configure etps etp ETP1
port subscriber 1
exit
port transport 1
exit
port transport 2
exit all
 To configure ETP protection:

• ETP name = ETP1, port members = subscriber 1, transport 1, transport2
• Protection mode = bidirectional 1:1
• APS protocol used for protection
• Working port = transport 1
• Protection port = transport 2
• Signal failure triggers = working MEP: MD 3 MA 2 MEP 1, protection MEP:
MD 4 MA 2 MEP 1
Note The MEPs must be active.
• Revertive mode
• Time to wait before restoring transmission = 300 seconds
exit all

configure etps etp ETP1 protection

mode bi-directional-1-to-1
aps-protocol
bind working transport 1
bind protection transport 2
sf-trigger working mep 3 2 1
sf-trigger protection mep 4 2 1
revertive
wait-to-restore 300
no shutdown
exit all
7.2 Ethernet Ring Protection (ERP)

A G.8032 Layer-2 Ethernet ring is a logical ring that protects against link and
node failures. ETX-2 supports multiple rings (up to eight; including sub-rings) over
a single bridge.
Applicable Products
• ETX203AX, ETX203AM, and ETX205A support up to four ring instances on
the same port.
• ETX220A supports up to eight ring instances on the same port.
Standards
ITU-T G.8032v2, Y.1731
Benefits
G.8032 rings provide sub 50 ms protection for Ethernet traffic.
Ethernet Ring Protection (ERP) technology provides a 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) functionality. It is independent of any physical layer technologies and can
be utilized in any carrier network.
A ring can be configured on network or user ports. If a ring is configured, LAG or
protection on the network ports is not allowed.
7-8 Ethernet Ring Protection (ERP) ETX-2

Note Rings are color-aware via the setting of the DEI bit:
• Set to 0 – maps to green
• Set to 1 – maps to yellow
No additional configuration is needed for the color-aware functionality.
You can also define the color-aware functionality of the ring by associating the
ring with a predefined color mapping profile (see Color Mapping).This is an
alternative method to using the DEI bit setting.
Ring Topology
ETX-2 supports the following topologies:
• Multi-ring
Figure 7-1. Multi-Ring
• Major ring with multiple sub-rings
Figure 7-2. Major Ring with Multiple Sub-rings
Multiple rings with a common link are usually referred to as ladder network (see
Figure 7-3).
The following terms are commonly used for describing ladder ring topology:
• Interconnection nodes – ring nodes that are common to both interconnected
rings (nodes C and G in Figure 7-3)
• Major ring – an Ethernet ring that controls a full physical ring and is
connected to the interconnection nodes on two ports (ring A-H-G-C-B in
Figure 7-3)
• Sub-ring – an Ethernet ring that is connected to a major ring at the
interconnection nodes. By itself, the sub-ring does not constitute a closed
physical ring. A sub-ring is connected to the interconnection nodes on only
one port (ring C-D-E-F-G in Figure 7-3). Link C–G is not a part of the sub-ring;
ETX-2 Ethernet Ring Protection (ERP) 7-9

it is controlled by the major ring.

G.8032 supports two operation modes of sub-rings:
 Sub-ring with an R-APS virtual channel – A virtual R-APS channel
connection is established between two interconnection nodes of the sub-
ring over a network or other ring, to tunnel R-APS messages. In this
mode, R-APS of the sub-ring is configured as a data VLAN in the Major
ring.
 Sub-ring without an R-APS virtual channel – The R-APS channel is
terminated at the interconnection nodes and its R-APS messages are not
tunneled between the interconnection nodes. In this mode, R-APS of the
sub-ring is not configured as a data VLAN in the Major ring.
H G F
Virtual Channel
A Major Ring Sub-Ring E
B C D
Figure 7-3. Physical Ladder Topology for Sub-Ring with R-APS Virtual Channel
Note Sub-rings without R-APS virtual channel do not have a Virtual Channel between G
and C.
H G G F
A Major Ring Sub-Ring E
B C C D
Figure 7-4. Major Ring and Sub-Ring
In ladder networks, a common VLAN is shared on more than one physical ring. For
example, in Figure 7-3, a user connected to node E communicates with a user
connected to node A over the same VLAN. Ring topology includes a physical link
between nodes G and C. It belongs to the major ring and is used by the sub-ring
as its R-APS channel. Note that a sub-ring without a virtual channel would not
have an R-APS virtual channel between nodes G and C.

Ring Protection Links

An Ethernet ring consists of multiple Ethernet nodes, each connected to adjacent
Ethernet nodes using two independent ring links. In order to prevent loops, the
ring uses a specific link to protect the ring, designated as the Ring Protection Link
(RPL). When there are no failures in the ring, the RPL is blocked. When a failure is
detected, the RPL is unblocked.
R-APS Control Messages

Nodes on the ring use Ring Automatic Protection Switching (R-APS) messages to
coordinate ring protection switching. R-APS messages are transmitted over a
VLAN designated as the R-APS VLAN.
ETX-2 supports the configuration of a Ring ID parameter per ring instance (both
major and sub). The configured Ring ID parameter is used as the suffix of the
R-APS DA MAC address, so that R-APS messages are sent to 01-19-A7-00-00-
<Ring ID>. For example, if you configure Ring ID of ring 3 as 03, R-APS messages
will be sent to 01-19-A7-00-00-03.
Note A single R-APS session is supported per VLAN.
Multiple Ring Instances on a Single Port

ETX-2 with Virtual Ring support enables multiple ring instances to reside over the
same physical port, allowing better bandwidth utilization of the ring in Idle state.
• ETX203AX, ETX203AM, ETX205A – four ring instances per physical port
• ETX220A – eight ring instances per physical port
Each ring instance resides on a different set of bridge ports, and supports R-APS
on a different VLAN.
It is not possible to allocate the same VLANs to ring instances residing on the
same physical port; this results in a sanity error.
The same MEP can be used as an sf-trigger to multiple rings residing on the same
physical link.
Figure 7-5. Multiple Rings on Single Physical Port

Passthrough VLANs
Passthrough VLANs over the ring are those VLANs that are not added/dropped to
the ring at the local ring node (ETX), but only traverse via the ring node (East to
West or vice versa).
By default, added/dropped VLANs at the local ring node, as well as passthrough
VLANs, must be configured as data VLANs, and each one is assigned a bridge
broadcast domain (device resource).
ETX-2 ring configuration supports a passthrough attribute, which automatically
assigns a ring/bridge bypass (East to West, West to East) for all passthrough
traffic (i.e. all traffic other than the local added/dropped VLANs that are
configured as data VLANs and use bridge broadcast domains). Passthrough traffic
can be configured for the full VLAN range other than the VLANs defined as data
VLANs.
As they do not go through the bridge and use its resources, ETX-2 allows an
unlimited number of passthrough VLANS to enter the ring, and does not require
configuring them as data VLANs. Added/dropped VLANs at the local ring node still
need to be configured as data VLANs. The number of added/dropped VLANs is
limited, because they go through the bridge and use up its resources (bridge
broadcast domains).
Use of passthrough VLANs upscales the ring capacity – an unlimited number of
passthrough services can travel through the ring; there is only a limit to the
number of ring services added/dropped at the local ring node (maximum number
of broadcast domains per local node). Without using the passthrough attribute,
the maximum broadcast domain supported in a single local node limits the
number of VLANs at the entire ring to this number.
Protection Switching Functionality

In idle state, traffic flows over all the ring links except the RPL. The RPL is
controlled by a node called the RPL owner, which blocks the RPL when in idle
state, in order to prevent loops. Each link is monitored by its two adjacent nodes
(east and west ports) using standard ETH CC OAM messages per Y.1731
(optional), or port physical status.
When a node detects link failure, it transmits an R-APS Signal Fail (SF) message
periodically, until link recovery is detected. Upon receiving the R-APS (SF), the RPL
owner unblocks the RPL port.
When a node detects link recovery, it sends R-APS No Request (NR) periodically
until R-APS No Request, RPL Blocked (NR, RB) is received from the RPL owner.
R-APS (NR, RB) is sent by the RPL owner to indicate that the ring has no failure
and the RPL has been blocked. Nodes receiving R-APS (NR, RB) flush their MAC
learning table, unblock their ports, and return to idle state.
After link recovery is detected, the adjacent nodes (to the initial failure) start to
send R-APS with (NR,NB). When these packets get to the RPL owner, it starts a
WTR (Wait To Restore) timer. If during the predefined value of this timer, no
additional link failure is detected, the RPL Owner starts to send R-APS with
(NR,RB) (RB = RPL Blocked) and blocks the RPL. Nodes receiving R APS (NR, RB)
flush their MAC learning table, unblock their ports, and return to idle state.

ERP Timers
The following timers are used in ERP operation:
Wait to Restore Period of time used by RPL owner to verify that the ring
(WTR) has stabilized before blocking the RPL after signal recovery.
Non-configurable; permanently set to 300 seconds.
Guard Period of time during which all received R-APS messages

are ignored by the ERP mechanism. This prevents the ring
nodes from receiving outdated R-APS messages.
Holdoff Period of time during which the Ethernet layer does not
report link faults to the ERP mechanism. This filters out
intermittent link faults.
Ring Commands
In addition to failure detection, protection switching can be initiated by the
following commands:
Force switch Forcefully blocks a particular ring port. It can be issued

even if an SF condition exists on the ring, with multiple
force switch commands allowed in the ring.
Manual switch Manually blocks a particular ring port. It can be overridden

by SF condition or a force switch command. Only one
manual switch command is allowed in the ring.
Clear Clears all existing force and manual switch commands in

the ERP.
Color Mapping
ETX-2 supports color mapping configuration at ring nodes, in order to manage
ring QoS.
A ring can be configured with color mapping, according to either of the following
methods:
• DEI – the default; DEI value is not configurable; its default color aware
functionality is as follows:
 DEI = 0 maps to green.
 DEI = 1 maps to yellow.
• Color mapping profile – associating ring with a predefined color mapping
profile (p-bit to color). Refer to Color Mapping Profiles in Traffic Processing
chapter on how to define a color mapping profile.
By default, a ring is configured with DEI color mapping.
CoS Mapping
ETX-2 supports CoS mapping configuration at ring nodes, in order to manage ring
QoS.

By default, the ring is associated with a default one-to-one p-bit to CoS profile,
where CoS 0 maps to the highest p-bit 7.
Figure 7-6. Default P-bit to CoS Profile
You can associate a predefined CoS mapping profile to the ring. Refer to CoS
Mapping Profiles in the Traffic Processing chapter on how to define a CoS
mapping profile.
Factory Defaults
By default, there is no Ethernet protection ring created in the ETX-2 system.
When the ring is created, it has the following default configuration.
backward-compatibility no backward-compatibility Backward compatibility to G.8032v1
bridge 0
color-mapping dei
cos-mapping no-cos-mapping Associates the ring with the default one-to-

one p-bit to CoS profile, where CoS 0 maps
to the highest p-bit 7
east-port 0
interconnection-node no interconnection-node
passthrough-vlan no passthrough vlan Default is No Passthrough VLAN mode, i.e.

added/dropped VLANs at the local ring node,
as well as passthrough VLANs, must be
configured as data VLANs, and each one is
assigned a bridge broadcast domain (device
resource).
port-type east node-port

west node-port
r-aps vlan 0 vlan-priority 0 mel 255
shutdown shutdown
timers guard 500 holdoff 0 wtr 300

west-port 0
Configuring Ethernet Ring Protection

The ring configuration sequence is as follows:
1. Configure the bridge (refer to Configuring the Bridge in the Traffic Processing
chapter).
2. Configure the ring.
3. Configure flows (refer to Configuring Flows in the Traffic Processing chapter).
4. Configure the router (refer to Configuring the Router in the Traffic Processing
chapter).
 To configure ERP:
1. At the config>protection# prompt, enter:
erp <ring-number> [{major | sub}]
An ERP instance of the specified type is created if it does not already
exist, and the config>protection>erp(<ring-number>)# prompt is
displayed.
Making the ring compatible with backward-compatibility

previous ERP implementations no backward-compatibility
Assigning ring to bridge bridge 1
Clearing any existing clear

force-switch or manual-switch
command
Clearing ERP statistics clear-statistics [{east | west}]
Defining color mapping type for color-mapping {dei | profile <profile- Packet at ring ingress and at any
ring name>} node mapped to color according
to one of the following:
dei – DEI (default)
profile – predefined p-bit color
mapping profile (p-bit to color);
string 1-32 characters
Associating CoS profile with ring cos-mapping profile <cos-mapping- profile – predefined p-bit color
profile-name> mapping profile (p-bit to color);
no cos-mapping string 1-32 characters
no cos-mapping associates the
ring with a default one-to-one
p-bit to CoS profile, where CoS 0
maps to the highest p-bit.

Defining description text for ring description <string>
Defining the east port of a ring east-port <bridge-port-number>

node ethernet [<slot>/]<port-index>
east-port <bridge-port-number>
east-port <bridge-port-number>
pcs <port-number>
Blocking the east or west port of force-switch {east | west} The force switch can be applied
a ring node, regardless of any to any number of nodes in the
failure conditions ring.
Defining ERP node as an interconnection-node

interconnection node, sharing
more than one ring
Blocking the east or west port of manual-switch {east | west} The manual switch command can
a ring node manually be applied to a single ring node
only.
Defining description text for port port-description {east | west} <string>
Defining ring port type port-type { east | west } { node-port | node-port – Port is not
rpl | neighbor | next-neighbor } connected to RPL.
rpl – Port is designated as RPL.
neighbor – Port is directly
connected to RPL owner.
next-neighbor – Port is
connected to RPL owner via
neighbor.
Configuring dedicated VLAN for r-aps [vlan <vlan-id>] Range for vlan-id: 1–4094
R-APS messages [vlan-priority <vlan-priority>] Range for vlan-priority: 0–7
[mel <level>]
Range for level: 0–7.
The mel parameter specifies the
maintenance entity group (MEG)
level (MEL) of the R-APS
messages.
Defining whether ring reverts revertive Enter no revertive to specify

back to original RPL when failure non-revertive operation.
is cleared
Configuring the ring ID ring-id <number> Used to configure destination of

no ring-id R-APS messages. ring-id is
appended to the R-APS DA MAC
address as follows:
01-19-A7-00-00-<Ring ID>
Possible values: 1-255 (00-FF)

Enabling propagation of Signal sf-trigger {east | west} mep <md-id> Before enabling SF propagation,
Failure (SF) condition from the <ma-id> <mep-id> verify that the relevant CFM
Ethernet OAM service layer no sf-trigger {east | west} parameters have been
configured.
Connecting previously defined sub-ring <sub-ring-number> Note: This is available for major
sub-ring to a major ring rings only. The sub-ring number
must be lower than the number
of the major ring it is assigned
to.
Defining ring timers timers [guard <guard-msec>] guard – While the guard timer is
[holdoff <holdoff-msec>] active, all received R-APS
messages are ignored by the
node; thus preventing the
receipt of outdated R-APS
messages. The range is 10 ms to
2 seconds in 10 ms steps.
holdoff – specifies the amount
of time an ERP-enabled node
waits from the point it
recognizes a local failure until it
reacts to the failure, i.e. it blocks
the port adjacent to the failed
link and send R-APS (SF) to the
RPL owner. The range is 0 to
10 seconds in 100 ms steps.
Defining data VLANs for user vlan <vlan-id> If using No Passthrough VLAN
traffic mode (the default), configure
both added/dropped and
passthrough VLANs as data
VLANs. If configuring
passthrough VLANs, configure
dropped VLANs only.
Note: In Passthrough VLAN
mode, if you configure a
passthrough VLAN as a data
VLAN, it will behave as an added/
dropped VLAN, and go through
the bridge, instead of bypassing
it.
To remove the VLAN assignment,
enter: no vlan <vlan-id>.
Before removing the VLAN
assignment, verify that all flows
using this VLAN have been
disabled.

Enabling passthrough VLANs passthrough-vlan [queue-block east Configure all VLANs, excluding
<qb-east> west <qb-west>] those defined as data VLANs, as
no passthrough-vlan passthrough VLANs.
East and west queue blocks can
optionally be configured.
Enter no passthrough-vlan (the
default) to use the regular mode,
where both added/dropped
VLANs at the local ring node and
passthrough VLANs must be
configured as data VLANs and
are each assigned a bridge
broadcast domain (device
resource).
Commands in vlan level
Defining the queue blocks for queue-block east <east-block>

the VLAN west <west-block>
Assigning service name to VLAN service-name <name>
Administratively enabling the no shutdown Type shutdown to disable the

VLAN VLAN.
Defining amount of time for RPL wait-to-restore <seconds> This timer specifies how long the
owner to wait before blocking RPL owner waits to verify that
RPL after failure recovery ring failures have been cleared,
before blocking the RPL. The
range is 1 min (60 sec) to 12
min (720 sec).
Defining the west port of a ring west-port <bridge-port-number>

node ethernet [<slot>/]<port-index>
west-port <bridge-port-number>
west-port <bridge-port-number>
pcs <port-number>
Administratively enabling the no shutdown Type shutdown to disable the

ERP ERP.
Displaying ERP status show status See Viewing ERP Status.
Displaying ERP statistics show statistics See Viewing ERP Statistics.
Examples
This section illustrates the following configuration for ETX203AX or ETX205A:
• VLAN-aware bridge, with bridge ports 1–4
• Ring:
 East port – Bridge port 1, Ethernet port 1

 West port – Bridge port 2, Ethernet port 2

 R-APS VLAN – 57
 User traffic VLANs – 100, 4000
• Management flows (unidirectional) between SVI 1 and bridge port 4, over
VLAN 4000
• Traffic flow (bidirectional) between Ethernet port 3 and bridge port 3, with
classification VLAN 100
#*******Configure SVI
exit all
configure port svi 1
no shutdown
exit all
# *******Configure bridge and bridge ports

configure bridge 1
port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
no shutdown
exit
port 4
no shutdown
exit all
# *******Configure Ethernet Ring Protection

configure protection
erp 1 major
bridge 1
east-port 1 ethernet 1
west-port 2 ethernet 2
r-aps vlan 57 vlan-priority 0 mel 3
port-type east node-port
port-type west node-port
color-mapping dei
cos-mapping my-p-bit
vlan 100
queue-block east 0/1 west 0/1
no shutdown
exit
vlan 4000
queue-block east 0/2 west 0/2
no shutdown
exit
timers holdoff 0
no shutdown
exit all

#*******Configure classifier profiles

configure flows
classifier-profile v100 match-any
match vlan 100
exit
match vlan 4000
exit
classifier-profile all match-any
match all
exit
#*******Configure flows
flow data
classifier v100
egress-port bridge-port 1 3
reverse-direction block 0/1
no shutdown
exit
flow mng_in
classifier v4000
no policer
vlan-tag pop vlan
ingress-port bridge-port 1 4
egress-port svi 1
no shutdown
exit
flow mng_out
classifier all
no policer
vlan-tag push vlan 4000 p-bit fixed 0
ingress-port svi 1
no shutdown
exit all
#*******Configure router
interface
configure router 1
interface 1
address 172.18.141.11/24
bind svi 1
no shutdown
exit
exit all
save
Viewing ERP Status

You can display the current status of an ERP entity.

 To display ERP status:

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

RPL Link : Not Owner
Ring State : Init
East Port Status : Block R-APS and Data Local SF Source

West Port Status : Block R-APS and Data Local SF Source
ERP status provides information on:
 Bridge number
 Bridge ports assigned to be East and West ring ports
 RPL link role:
 Not owner – All other nodes on the ring (that is, those that are not
the RPL owner node) operate as normal nodes and have no special
role on the ring.
 RPL owner – This node owns the RPL and blocks or unblocks the RPL
as conditions require. This node initiates the R-APS message.
 Ring state:
 Init – The node is disabled (in ‘shutdown’).
 Idle – The node is performing normally (there is no link failure on the
ring). In this state, traffic is unblocked on both ring ports, except for
the RPL owner node, which blocks the RPL port (the other RPL owner
port is unblocked) and the RPL neighbors port.
 Pending – transition state between ‘Protected’ and ‘Idle’ (only in this
direction). This state means that the device detected that a signal
failure state was cleared, and started the WTR timer. After the WTR
timer consumes itself, the state changes to ‘Idle’.
 Protected – A failure occurred on the ring. A non-owner node has
traffic blocked on the ring port that connects to the failed link. The
RPL owner, if it is not at one end of the failed link, unblocks the RPL
port so both ports are active.
 East/West Port Status:
 Forward – Port is forwarding data.
 Block R-APS and Data – Port is blocked.
 East/West Port Local SF Source – Local Signal Failure source:
 OK – Port forwarding
 CFM CC – OAM failure

 Server Layer – Port down failure
Viewing ERP Statistics

You can view statistics on R-APS messages sent and received by the East and West
ports.
 To display ERP statistics:

• At the config>protection>erp(<erp-number>)# prompt, enter
show statistics
The ERP statistic counters are displayed.
ETX-2>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.

Counter Description
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
7.3 Fault Propagation

Fault propagation enables you to specify which entities to shut down if link
failure occurs.
Applicable Products
Standards
IEEE 802.1ag-D8
ITU-T Y.1731
Benefits
You can ensure that you are sending packets via links that have not failed.
Failures are propagated end-to-end via actions such as OAM CFM messages and
entity deactivation.
In the network-to-user or user-to-network direction, if a link fails for which fault
propagation is enabled, the corresponding port shuts down or OAM CFM message
indicating failure is sent, thus signaling the connected CPE to stop forwarding
frames through the link.
You can enable fault propagation to be triggered by failure detection on a
network/user interface or entity, which causes a user-configurable action (such
as deactivation or OAM CFM message indicating failure sent) to be performed on
a user/network interface or entity. You can enable fault propagation in the
network-to-user or user-to-network direction, for a pair of entities such as PCS
port, Ethernet ports, MEPs, queue block shaper, flow policer, card (VDSL), TWAMP
sessions, and ETPs.
ETX-2 Fault Propagation 7-23

You can define the following when you enable fault propagation for a pair of
entities:
• Trigger:
 Failure detected on port or MEP:
 LOS – link down detected
 Failure detected on 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
 OAM CFM E-LAN failure – LOC has occurred for all the remote MEPs of
the MEP.
 Failure detected in VDSL card connection (relevant for ETX203AM with
VDSL card). This is detected via ping to a remote station using ICMP Echo.
75% lost pings in one minute (i.e. unavailable minute) indicates an ICMP
Echo fail event.
• Action to take when fault propagation is triggered:
 Action performed on port:
 Deactivate interface.
 Action performed on MEP:
 Send OAM CFM alarm indication signal to indicate failure.
Or
 Send OAM CFM interface status TLV to indicate failure.
 Action performed on queue block shaper:
 Change shaper rate according to specified shaper-profile.
 Action performed on flow policer:
 Change policer rate according to specified policer-profile.
 Action performed on VDSL card (relevant for ETX203AM with VDSL card):
 Reset VDSL card.
• Wait-to-restore time – the time period before enabling the shut-down entity
or ceasing to send OAM CFM interface status once the failed entity has been
restored
• Holdoff timer – Action is triggered only if detected fault propagation persists
for the amount of time configured in the holdoff timer. Holdoff timer enables
timing the fault propagation action and synchronizing with other network
redundancy mechansims.
7-24 Fault Propagation ETX-2

Factory Defaults
By default, no fault propagation is configured. When you configure fault
propagation for a particular entity pair, the default configuration is as follows:
• No trigger is defined for fault detection.
• No action is defined to be performed when a fault is detected.
• No holdoff is defined. Trigger activates fault propagation as soon as it is
detected.
• Wait-to-restore time = 0
Configuring Fault Propagation

Follow this procedure to configure fault propagation:
1. Add a fault propagation entry for a pair of entities.
2. Configure up to 32 fault propagation rules for the entry:
a. Specify the trigger(s).
b. Specify the action.
c. Define the holdoff timer.
d. For applicable actions, specify the wait-to-restore time if you do not want
the default value 0.
Adding Fault Propagation Entry

 To add fault propagation for a pair of entities:
1. Navigate to configure fault.
2. Type the command:
fault-propagation <from-entity> to <to-entity> and enter the desired
entities, as shown in Table 7-3.
A prompt is displayed:
config>fault>fault-propogation(<from-entity>/to/<to-entity>)$
3. Configure the fault propagation parameters as needed (see Configuring Fault
Propagation Rules).
Table 7-3. Fault Propagation Command Options
From Entity To Entity Command
ETP Ethernet port fault-propagation etp <etp-name> to

port ethernet [<slot>/]<port>
ETP PCS fault-propagation etp <etp-name> to port pcs <port>
ETP Logical MAC fault-propagation etp <etp-name> to port logical-

mac <port>
ETP MEP fault-propagation etp <etp-name> to

mep <to-mdid> <to-maid> <to-mepid>

Ethernet port Ethernet port fault-propagation port ethernet [<slot>/]port> to

Ethernet port Logical MAC fault-propagation port ethernet [<slot>/]port> to

port logical-mac <port>
Ethernet port MEP fault-propagation port ethernet [<slot>/]port> to

Ethernet port PCS fault-propagation port ethernet [<slot>/]port> to

port pcs <port>
Ethernet port Queue block fault-propagation port ethernet [<slot>/]port> to shaper

shaper port <eth-port> queue-block <level>/<queue-block>
Ethernet port Policer instance fault-propagation port ethernet [<slot>/]port> to policer

flow <flow-name>
LAG port Ethernet port fault-propagation port lag <port> to port

ethernet [<slot>/]<port>
LAG port Logical MAC fault-propagation port lag <port> to port logical-
mac <port>
LAG port MEP fault-propagation port lag <port> to

LAG port PCS port fault-propagation port lag <port> to port pcs <port>
Logical MAC Ethernet port fault-propagation port logical-mac <port> to port

ethernet [<slot>/]<port>
Logical MAC Logical MAC fault-propagation port logical-mac <port> to port logical-
mac <port>
Logical MAC MEP fault-propagation port logical-mac <port> to

Logical MAC PCS port fault-propagation port logical-mac <port> to port pcs
<port>
MEP Ethernet port fault-propagation mep <md-id> <ma-id> <mep-id> to

MEP Logical MAC fault-propagation mep <md-id> <ma-id> <mep-id> to

port logical-mac <port>
MEP MEP fault-propagation mep <md-id> <ma-id> <mep-id> to

MEP PCS fault-propagation mep <md-id> <ma-id> <mep-id> to

port pcs <port>
MEP Queue block fault-propagation mep <md-id> <ma-id> <mep-id> to

shaper shaper port <eth-port> queue-block <level>/<queue-
block>
MEP Policer instance fault-propagation port mep <md-id> <ma-id> <mep-id> to

policer flow <flow-name>

PCS port (only Ethernet port fault-propagation port pcs <port> to port
with SHSDL ethernet [<slot>/]<port>
module/port)
PCS port (only Logical MAC fault-propagation port pcs <port> to port logical-
with SHSDL mac <port>
module/port)
PCS port (only MEP fault-propagation port pcs <port> to

with SHSDL mep <to-mdid> <to-maid> <to-mepid>
module/port)
PCS port (only PCS port (only fault-propagation port pcs <port> to port pcs <port>
with SHSDL with SHSDL
module/port) module/port)
TWAMP session Card (VDSL) fault-propagation twamp-session controller <name> peer

<ip-address> session-id <number> to slot <number>
Configuring Fault Propagation Rules

You can configure up to 32 fault propagation rules for a pair of entities.
 To configure fault propagation rules:
1. Navigate to configure fault fault-propagation <from-entity> to <to-entity> to
select the fault propagation entry to configure.
A prompt is displayed:
config>fault>fault-propagation(<from-entity>/to/<to-entity>)#

Specifying the action to take when action-on-group { interface-deactivation | The following actions are supported:
fault propagation is triggered oam-cfm-if-status-tlv | oam-cfm-ais| • interface-deactivation – Deactivate
shaper-swap <shaper-profile> | policer- interface.
swap <policer-profile> | reset }
• oam-cfm-if-status-tlv – Send OAM CFM
interface status TLV to indicate failure.
• oam-cfm-ais – Send OAM CFM alarm
indication signal to indicate failure.
• shaper-swap – Change shaper rate
according to shaper-profile.
• policer-swap – Change policer rate
according to policer-profile.
• reset – Reset the card. Relevant for
ETX203AM with VDSL card.
Typing no action-on-group removes the
action.
Notes:
• The interface-deactivation action is
allowed only if the to-entity is an
Ethernet port.
• The oam-cfm-if-status-tlv or
oam-cfm-ais action is allowed only if
the to-entity is a MEP.
• The shaper-swap action is relevant
only for the Queue Block Shaper
destination.
• The policer-swap action is relevant
only for the Flow Policer destination.
• shaper-swap and policer-swap
actions are enabled only if you have
activated the tmfp license for
enhanced fault propagation features.
Defining the number of milliseconds to holdoff <milliseconds> Possible values:

wait before a trigger activates fault no holdoff 0 – default; no holdoff; trigger activates
propagation. fault propagation as soon as it is detected.
>0 – number of milliseconds

Specifying the trigger(s) trigger { los | oam-cfm-loc | oam-cfm-rdi | The following triggers are supported:
oam-cfm-if-status-tlv | oam-cfm-ais | • los – link down
oam-cfm-all-rmep-fail | oam-cfm-cfs-clos |
• oam-cfm-loc – LOC detected
unavailable }
• oam-cfm-rdi – RDI detected
• oam-cfm-if-status-tlv
• oam-cfm-ais – AIS detected
• oam-cfm-all-rmep-fail – All remote MEPs
failed.
• oam-cfm-csf-clos
• unavailable – VDSL connection to remote
station is down.
Typing no before the command removes the
specified trigger.
Note: The los trigger is allowed only if the
from-entity is an Ethernet port or ETP. The
OAM CFM triggers are allowed only if the
from-entity is a MEP.
Specifying the wait-to-restore time wait-to-restore <seconds> Possible values: 0–3600
Disabling Fault Propagation

 To disable fault propagation for a pair of entities:
1. Navigate to configure fault.
2. Type the command:
no fault-propagation <from-entity> to <to-entity> to select the entities for
which to disable fault propagation.
The specified fault propagation is disabled.
Examples
 To enable fault propagation on ETX220A:
• From Ethernet port 1/3
• To MEP 3 in maintenance association 3 in maintenance domain 2 (this
example assumes the MEP has been created)
• Trigger: LOS
• Action: Send OAM CFM interface status TLV.
• Wait-to-restore time = 120 seconds
• Holdoff timer = 150 milliseconds
exit all
config fault
fault-propagation port ethernet 1/3 to mep 2 3 3
trigger los
action-on-group oam-cfm-if-stat

wait-to-restore 120
holdoff 150
exit all
 To display information on the fault propagation configured above:

ETX-2# config fault fault-propagation port eth 1/3 to mep 2 3 3
ETX-2>config>fault>fault-propagation(port/ethernet/1/3/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
wait-to-restore 120
holdoff 150
 To enable fault propagation:

• To Ethernet port 1/3
• Trigger: LOS
• Action: Shut down Ethernet port.
• Holdoff time = 320 milliseconds
exit all
config fault fault-prop port ethernet 3/1 to port ethernet 1/3
trigger los
action interface-deact
wait-to-restore 90
holdoff 320
exit all

ETX-2# config fault fault-prop port eth 3/1 to port eth 1/3
ETX-2>config>fault>fault-propagation(port/ethernet/3/1/to/port/ethernet/1/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
wait-to-restore 90
holdoff 320

• From MEP 1 in maintenance association 1 in maintenance domain 1 (this
• To MEP 2 in maintenance association 2 in maintenance domain 1 (this
• Trigger: Any OAM CFM error

• Action: Send OAM CFM interface status TLV

exit all
config fault
fault-propagation mep 1 1 1 to mep 1 2 2
trigger oam-cfm-loc
trigger oam-cfm-rdi
trigger oam-cfm-if-status-tl
action-on-g oam-cfm-if-stat
wait-to-restore 300
exit all

ETX-2# config fault fault-propagation mep 1 1 1 to mep 1 2 2
ETX-2>config>fault>fault-propagation(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
wait-to-restore 300

• To Shaper port 1/3
• Trigger: LOS
• Action: Change shaper rate to 100M.
exit all
config fault fault-prop port ethernet 3/1 to shaper port ethernet 1/3 queue-
block 0/2
wait-to-restore 100
trigger los
action-on-group shaper-swap rate_100M
exit all

• To policer flow tlv1
• Trigger: LOS
• Action: Change policer rate to 70M.
config fault fault-propagation port ethernet 3/1 to policer flow tlv1
wait-to-restore 100
trigger los
action-on-group policer-swap rate_70M
exit all

The following table lists the messages generated by the device when a
configuration error is detected.
Cannot delete entity while it You tried to delete an entity

participates in fault propagation used in fault propagation
existent configuration.
Fault propagation source does You tried to configure fault

not exist propagation with a non-
existent source.
Fault propagation destination You tried to configure fault

does not exist propagation with an existent
source but non-existent
destination.
7.4 Link Aggregation

In link aggregation (LAG) mode according to IEEE 802.3ad, Ethernet interfaces can
be aggregated into a single logical link for protection or load balancing.
Applicable Products
• Ethernet 10GbE ports are relevant only to ETX220A.
• LAG is supported with or without LACP (user-configurable), with 50ms LAG
switchover time.
• Protection LAG groups can have up to two members, and load-balancing LAG
goups can have up to four members.
• A protection LAG group can be made up of one or two adjacent network
ports or user ports; not both types.
• A LAG group can include ports of the same speed only (1G or 10G).
• ETX203AM, ETX203AX, or ETX205A – You can configure up to three LAG
groups that function in protection mode.
A LAG group can contain one or two adjacent network or user ports in one of
the following combinations: ports 1 and 2; 3 and 4; 5 and 6. Any other
combinations are not valid and result in a sanity error.
• ETX220A – You can configure up to 11 LAG groups that function in
protection or load-balancing mode.
7-32 Link Aggregation ETX-2

A protection LAG group can contain one or two network or user ports of the
same speed (both 10GbE or both GbE), in one of the following combinations:
1/1 and 1/2, 1/3 and 1/4, …, 1/9 and 1/10; 2/1 and 2/2,...,2/9 and 2/10; 3/1
and 3/2; 4/1 and 4/2. Any other combinations are not valid and result in a
sanity error.
A load-balancing LAG group can be made up of ports from the same slot only.
Exception: In case of the 4x10G + 10x1G ordering option, members in a load-
balancing LAG group can include ports from one of the following groups: (A
single LAG group cannot contain some ports from one group and other ports
from the other group.)
 1/1 – 1/5
 1/6 – 1/10
Standards
IEEE 802.3ad
Benefits
ETX-2 can continue to route traffic even if one of the links fails.
All LAG ports receive traffic at the same time and one port transmits. The LAG
members can be network or user interfaces, and must be connected to the same
switch. If LACP is activated, then LACP control frames are periodically transmitted
in order to locate failures as they occur.
Note LAG on user ports is not supported when the user ports are connected to bridge
ports (E-LAN).
You can configure an anchor port for a LAG group, which you can use to
configure flows to/from the LAG group. The default anchor port is the first port
bound to the LAG group. The MAC address of the anchor port is used for logical
port level entities (router interface over the LAG, OAM MEP over the LAG, etc.).
Protection
If the transmitting port fails, ETX-2 switches to a standby link. The equipment
connected to the Ethernet ports must use compatible switching criteria for
redundancy to be available:
• For networks using Layer 2 switching – The criterion is signal loss.
• For networks using Layer-3 routing – The router must support IEEE 802.3ad
or other link aggregation protocol that views the aggregated link as a single
logical interface.
Using link aggregation inherently provides redundancy, because if a port fails,
another port can continue transferring traffic. Failure of a link is detected by
sensing the loss of valid signals, or receiving a failure report via Link Aggregation
ETX-2 Link Aggregation 7-33

Control Protocol (LACP) if applicable, in which case all traffic is sent through the
other link.
Load Balancing
In a load balancing LAG group, traffic is distributed to the different ports
according to the configured distribution method. You can configure the following
distribution methods:
• MAC source address
• MAC destination address
• MAC source address and MAC destination address
• IP source address
• IP destination address
• IP source address and IP destination address
• MAC source/destination address and IP source/destination address
For distribution method based on IP address, all non IP packets are forwarded on
the same port. For distribution method based on MAC source/destination address
+ IP source/destination address, fallback for non IP packets is based on MAC
address info.
Note All load balancing LAG groups in the device must use the same distribution
method.
The load balancing and distribution is performed after the queuing mechanism.
The port policer is supported at the port level, not on LAG aggregate ingress
traffic. Aggregate LAG egress traffic can be shaped at the LAG level up to a
maximum of 10 Gbps (level 1 shaper supported for rates up to 10 Gbps).
You can configure the minimum number of active ports in the LAG for it to be
considered operationally active. A port is considered as active if it has no physical
layer failure and LACP is synched (if LACP is enabled).
If there are flows over the anchor port when the LAG group is created and
enabled, the flows are inherited by the LAG group. The LAG group can be
administratively enabled if flows exist over the anchor port, but not if flows exist
over a non-anchor port. If the LAG group is deleted or administratively disabled,
the flows and traffic remain on the anchor port; they are not distributed to other
ports.
Factory Defaults
By default, no LAG groups are configured. When a LAG group is created, it has
the following default configuration.
admin-key giga-ethernet LAG admin key is GbE port
dhcp-trust no dhcp-trust
lacp no lacp LACP not enabled

mode redundancy LAG is protection LAG
If the mode is changed to load-balance, the default configuration is as shown

below.
admin-key giga-ethernet LAG admin key is GbE port
distribution-method src-ip Packets distributed according to source IP address
lacp no lacp LACP not enabled
minimum-link-number 1 One LAG port must be active
mode load-balance LAG is load balancing LAG
Configuring LAG
This section explains how to define a link aggregation group (LAG) and enable link
aggregation control protocol (LACP).
Notes • In order to enable LACP for the LAG, the ports bound to the LAG must be
associated with an L2CP profile that specifies peer action for MAC 0x02.
• In a load-balancing LAG, all non-anchor ports bound to the LAG must not be
associated with a queue group profile (use command no queue-group).
 To configure the LAG:

1. Navigate to configure port lag <num>.
The config>port>lag(<num>)# prompt is displayed.
Assigning an admin key to the admin-key {giga-ethernet | You must define admin key
LAG to indicate the port speed fast-ethernet | ten-giga-ethernet} before binding ports to the
LAG.
Defining the LAG anchor port anchor-port ethernet <port-index>

anchor-port logical-mac <port-number>
Adding a port to the LAG bind ethernet [<slot>/]<port-num> Entering no bind removes a link
bind logical-mac <port-num> from the LAG.

Configuring port to trust DHCP dhcp-trust Client ports must always be

packets sent from server untrusted (no dhcp-trust);
otherwise, the DHCP relay
discards the discovery
messages sent from the client
port to the server.
Relevant only if DHCP snooping
is enabled (refer to DHCP Relay
in the Management and
Security chapter).
Assigning method of distribution-method {src-mac | dest-mac src-mac – Packets are

distributing traffic within LAG | src-or-dest-mac | src-and-dest-mac | distributed according to their
src-ip | dest-ip | src-dest-mac-ip | source MAC addresses.
round-robin | source-port | one-to-one | dest-mac – Packets are
src-dest-ip} distributed according to their
destination MAC addresses.
src-or-dest-mac – not
supported
src-and-dest-mac – Packets are
distributed according to their
source and destination MAC
addresses.
src-ip – Packets are distributed
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.
round-robin – not supported
source-port – not supported
one-to-one – Packets are
distributed one to one.
src-dest-ip – Packets are
source and destination IP
addresses.
Note: The one-to-one
parameter is relevant only for
redundancy LAG; the other
parameters are relevant only
for load balancing LAG.

Enabling LACP and setting lacp [tx-activity {active | passive}] tx-activity – Defines operation
LACP parameters [tx-speed { slow | fast }] [sys-priority mode:
<sys-priority>] • active – LAG interface
periodically transmits LACP
frames (LACPDUs) to all
links with LACP enabled.
• passive – LAG interface
does not initiate the LACP
exchange, but replies to
received LACPDUs.
tx-speed – Defines time to wait
before sending LACP frames:
• fast – three seconds
• slow – 90 seconds
sys-priority – determines
aggregation precedence. If
there are two partner devices
competing for the same LAG,
LACP compares the priorities
for each grouping of ports. The
LAG with the lower priority is
given precedence.
Defaults:
• If you type lacp without
specifying tx-activity, it is
set to active.
• If you type lacp without
specifying tx-speed, it is set
to fast.
Typing no lacp disables LACP
protocol.
Configuring LLDP parameters lldp Refer to Link Layer Discovery

Protocol (LLDP) in the Traffic
Defining the minimum number minimum-link-number <number> Range is 1 to maximum number

of links required for load of LAG members.
balancing LAG If less than the minimum
number of links function
properly, LAG failure is
reported.
Specifying if LAG is for mode {redundancy | load-balance} Note: The load-balance

redundancy or load balancing parameter is valid only for
ETX220A.
Administratively enabling LAG no shutdown Using shutdown disables the

LAG.

Displaying bind status show bind
Displaying LACP statistics show lacp-statistics ethernet

[<slot>/]<port-id>
Displaying LACP status show lacp-status ethernet

[<slot>/]<port-id>
Displaying LAG statistics show statistics running
Clearing LAG statistics clear-statistics
Displaying LAG status show status See Viewing LAG Status.
Examples
Protection LAG
 To define LAG for ETX203AX or ETX205A:
• L2CP profile mac2peer, with mac0x02 set to peer action
• LAG members – Ethernet ports 1 and 2
• LACP operation mode – active
• Distribution method – one to one
• System priority –32768
#****************Create L2CP profile mac2peer
exit all
configure port l2cp-profile mac2peer
mac 0x02 peer
exit
#****************Assign L2CP profile mac2peer to network ports

eth 1 l2cp profile mac2peer
eth 2 l2cp profile mac2peer
#****************Configure LAG 1
lag 1
bind ethernet 1
bind ethernet 2
lacp tx-activity active tx-speed slow sys-priority 32768
distribution-method one-to-one
no shutdown
exit all
 To display LACP status:

ETX-2#configure port lag 1
ETX-2>config>port>lag(1)# show lacp-status eth 1
Ports
-----------------------------------------------------------
Actor Partner
Port Number : 1 1
Port Priority : 32768 0

System ID : 0020D250E70A 0020D2F5AD58

System Priority : 32768 32768
Operational Key : 2 32
Activity : Active Active
Timeout : Long Long
Synchronized : Yes No
Collecting : No No
Distributing : No No
 To display LACP statistics:

ETX-2>config>port>lag(1)# show lacp-statistics ethernet 1
LACP
---------------------------------------------------------------
Rx LACP Frames : 3221
Rx Marker Frames : 0
Rx Unknown Frames : 0
Rx Illegal Frames : 0
Tx LACP Frames : 5783
Tx Marker response Frames : 0
Load Balancing LAG
 To define load balancing LAGs in ETX220A:

• L2CP profile mac2peer, with mac0x02 set to peer action
• LAG members:
 LAG 1: – GbE ports 1/3 to 1/6
 LAG 5: – 10GbE ports 4/1 and 4/2
• LACP operation mode – active
• Distribution method – Destination MAC address
• Flows:
 Flows for LAG 1 – between GbE 1/1 and 1/3, VLAN 100
 Flows for LAG 5 – between GbE 1/1 and 10GbE 4/1, VLAN 500
exit all
#***********Configure L2CP profile
mac 0x02 peer
exit
#***********Associate ports with the L2CP profile

#***********Specify no queue group profile for non-anchor ports

ethernet 1/3
l2cp profile mac2peer
no shutdown
exit
ethernet 1/4
no queue-group
no shutdown
exit
ethernet 1/5
no queue-group
no shutdown
exit
ethernet 1/6
no queue-group
no shutdown
exit
ethernet 1/7
no shutdown
exit
ethernet 1/8
no queue-group
no shutdown
exit
ethernet 1/9
no queue-group
no shutdown
exit
ethernet 1/10
no queue-group
no shutdown
exit
ethernet 2/1
no shutdown
exit
ethernet 2/2
no queue-group

no shutdown
exit
ethernet 2/3
no queue-group
no shutdown
exit
ethernet 2/4
no queue-group
no shutdown
exit
ethernet 2/5
no shutdown
exit
ethernet 2/6
no queue-group
no shutdown
exit
ethernet 2/7
no queue-group
no shutdown
exit
ethernet 2/8
no queue-group
no shutdown
exit
ethernet 2/9
no shutdown
exit
ethernet 2/10
no shutdown
exit
ethernet 4/1
no shutdown
exit
ethernet 4/2

no queue-group
no shutdown
exit
#***********Configure LAGs
lag 1
mode load-balance
distribution-method dest-mac
admin-key giga-ethernet
bind ethernet 1/3
bind ethernet 1/4
bind ethernet 1/5
bind ethernet 1/6
lacp tx-activity active tx-speed fast
anchor-port ethernet 1/3
no shutdown
exit
lag 2
mode load-balance
bind ethernet 1/7
bind ethernet 1/8
bind ethernet 1/9
bind ethernet 1/10
no shutdown
exit
lag 3
mode load-balance
bind ethernet 2/1
bind ethernet 2/2
bind ethernet 2/3
bind ethernet 2/4
no shutdown
exit
lag 4
mode load-balance
bind ethernet 2/5
bind ethernet 2/6
bind ethernet 2/7
bind ethernet 2/8
no shutdown

exit
lag 5
mode load-balance
admin-key ten-giga-ethernet
bind ethernet 4/1
bind ethernet 4/2
no shutdown
exit
#***********Configure classification profiles for flows

exit
flows
classifier-profile vlan100 match-any match vlan 100
exit
#***********Configure flow for LAG 1

flow lag1_1_to_3
classifier vlan100
no policer
egress-port ethernet 1/3 queue 0 block 0/1
no shutdown
exit
flow lag1_3_to_1
classifier vlan100
no policer
no shutdown
exit

flow lag2_1_to_7
classifier vlan200
no policer
no shutdown
exit
flow lag2_7_to_1
classifier vlan200
no policer
no shutdown

exit

flow lag3_21_to_3
classifier vlan300
no policer
no shutdown
exit
flow lag3_3_to_21
classifier vlan300
no policer
no shutdown
exit

flow lag4_25_to_3
classifier vlan400
no policer
no shutdown
exit
flow lag4_3_to_25
classifier vlan400
no policer
no shutdown
exit

flow lag4_41_to_3
classifier vlan500
no policer
no shutdown
exit
flow lag4_3_to_41
classifier vlan500
no policer
no shutdown
exit all
save

 To display LACP status:

ETX-2>config>port>lag(1)# show lacp-status ethernet 1/3
Ports
-----------------------------------------------------------
Actor Partner
Port Number : 3 3
Port Priority : 32768 0
System ID : 0020D2EE5ED8 0020D2EE62E1
System Priority : 32768 0
Operational Key : 2 31
Activity : Active Active
Timeout : Short Short
Synchronized : Yes Yes
Collecting : Yes Yes
Distributing : Yes Yes
 To display LACP statistics:

ETX-2>config>port>lag(1)# show lacp-statistics ethernet 1/3
LACP
---------------------------------------------------------------
Rx LACP Frames : 386
Rx Marker Frames : 0
Rx Unknown Frames : 0
Rx Illegal Frames : 0
Tx LACP Frames : 386
Tx Marker response Frames : 0
 To display LAG status:

ETX-2>config>port>lag(1)# show status
Group
---------------------------------------------------------------
Administrative Status: Up
MAC Address : 00-20-D2-EE-5E-D8
Links
---------------------------------------------------------------
Port Admin Oper LACP Redundancy
---------------------------------------------------------------
1/3 Up Up Sync Active
 To display LAG statistics:

ETX-2>config>port>lag(1)# show statistics running
Rate of Total
---------------------------------------------------------------
Port Rx Total Frames Tx Total Frames

(%) (%)
---------------------------------------------------------------
1/3 25.00 25.00
1/4 25.00 25.00
1/5 25.00 25.00
1/6 25.00 25.00
Viewing LAG Status

You can display the LAG status, including the information specified in Table 7-5.
 To display the LAG status:

• At the prompt config>port>lag(<num>)#, enter:
show status
ETX-2# configure port lag 1
Group
---------------------------------------------------------------
Name : LAG 1
Group
---------------------------------------------------------------
Mode : Redundancy
Speed : 1Gbps
MAC Address : 00-20-D2-50-C0-D3
Links
---------------------------------------------------------------
---------------------------------------------------------------
1 Up Up Sync Active
2 Up Up Sync Active
Table 7-5. LAG Status
Group
Name Displays name assigned to LAG
Administrative Status Indicates if LAG is administratively enabled or disabled: Up

or Down

Operational Status Indicates if LAG is operational:

Up – LAG is operational.
Down – LAG is not operational, for reason such as being
administratively disabled or link shut down for Fault
propagation.
LLD (all links down) – Both protection LAG ports are down,
in case of protection LAG).
LLD (minimum links down) – Minimum links are down, in
case of load balancing LAG.
Mode Displays LAG mode: Redundancy or Load Balance
Speed Indicates LAG speed as one of the following, according to

X (port speed in case of protection LAG, or number of
active links × link rate in case of load balancing LAG):
• X >=1 Gbps – Speed indicated as X Gbps
• 0 < X < 1 Gbps – Speed indicated as X Mbps
• X = 0 – Speed indicated as Not Applicable
MAC Address Displays MAC address of LAG
Links
Port Displays port number of link
Admin Indicates if link is administratively enabled or disabled: Up

or Down
Oper Indicates if link is operational: Up or Down
LACP Indicates if LACP is synchronized
Redundancy Indicates if redundancy is active
Examples
 To display the status of a protection LAG with all links down:
Group
---------------------------------------------------------------
Name : LAG 1
Group
---------------------------------------------------------------
Operational Status : LLD (all links down)
Mode : Redundancy
Speed : Not Applicable
MAC Address : 00-20-D2-50-C0-D3
Links

---------------------------------------------------------------
---------------------------------------------------------------
1 Up Down Not Sync Active
2 Up Down Not Sync Active
 To display the status of a load balancing LAG with minimum links down:
Group
---------------------------------------------------------------
Operational Status : LLD (minimum links down)
Mode : Load Balance
Speed : Not Applicable
MAC Address : 00-20-D2-EE-41-C1
Links
---------------------------------------------------------------
---------------------------------------------------------------
1/1 Up Down Not Sync Active
1/2 Up Down Not Sync Active
7.5 Link Protection

Two Ethernet network interfaces can operate in 1:1 bidirectional protection
(redundancy) mode. In this mode, only one port is active at a time to carry
traffic. If it fails, the second port takes over. The recovery mode (revertive or
non-revertive) and the restoration time in revertive mode can be selected
according to the application requirements.
Applicable Products
• Ethernet 10GbE ports are relevant only to ETX220A.
Standards
IEEE 802.3ad
Benefits
ETX-2 can continue to route traffic even if one of the links fails.
7-48 Link Protection ETX-2

Link protection offers an alternative to link aggregation, if protection without
LACP is acceptable. You can configure parameters such as revertive/non-revertive
mode, the restoration time in revertive mode, forcing active link, etc., however
the switchover time to the standby link is longer than for LAG.
In 1:1 bidirectional mode mode, the following topologies can be used:
• Connection of both ports to the same switch/router
• Connection of the ports to different switch/routers. The main advantage of
this topology is its higher availability, because each port can be routed along
a different path through the network. This topology is also referred to as
dual homing.
With 1:1 bidirectional redundancy mode, at any time only one of the ports is
actively carrying traffic, and the other port serves as the backup port. A RAD
proprietary redundancy algorithm, based on loss of Ethernet signal, is used to
detect line failure. The protection switching (flipping) time is less than 1 second.
It also depends on the network “relearning“ time or aging.
The recovery mode after protection switching can be selected in accordance with
the application requirements:
• Non-revertive mode – ETX-2 does not automatically flip back after the failed
port returns to normal operation, but only when the currently used port fails,
or after a manual flip command.
• Revertive mode – ETX-2 flips back to the original port when it returns to
normal operation. Flipping back can be delayed by specifying a restoration
time, during which alarms are ignored. As a result, ETX-2 starts evaluating the
criteria for protection switching (flipping) only after the restoration time
expires, thereby ensuring that another flip cannot occur before the specified
time expires.
Factory Defaults
By default, bidirectional redundancy is not enabled.
Configuring Link Protection

Configuring a 1:1 protection requires defining an Ethernet group.
 To define an Ethernet group:

• At the Protection context (config>protection), enter:
ethernet-group <group-id>
The system switches to the context of the specified Ethernet group
(config>protection>eth-group(<group-id>)).
 To add/remove protection and working ports – in manual mode:

• At the Ethernet Group context (config>protection>eth-group(<group id>)),
enter
bind ethernet primary [<slot>/]<port>
ETX-2 Link Protection 7-49

• To remove protection and working ports, enter:

no bind ethernet primary
 To add/remove protection and working ports – in 1–to–1 mode:

enter:
bind ethernet [primary [<slot>/]<port>] [secondary [<slot>/]<port>]
• To remove protection and working ports, enter:
no bind ethernet primary
no bind ethernet secondary
 To define the operation mode:

enter:
oper-mode { 1-to-1 | manual }
 To define the port recovery mode as revertive:

enter:
revertive
Traffic is switched back to the primary port after it recovers.
 To define the port recovery mode as non-revertive:

• At the Ethernet Group context config>protection>eth-group(<group id>)),
enter:
no revertive
Traffic continues being transmitted over the secondary port after the primary
port recovers.
 To define the time between recovery and resumption of transmission

enter
wait-to-restore <seconds>
The primary port resumes transmitting traffic once the specified time has
been restored and the specified time has elapsed. You can choose between 1
and 720 seconds.
 To define the period of time that the failed link stops transmitting to report the
failure:
enter
tx-down-duration-upon-flip <seconds>
The secondary port resumes transmitting after the specified ‘reporting’ time.
You may specify a time in the range between 0 and 30 seconds. This function
is useful if there is no autonegotiation between the link end points.

 To force a port to transmit:

• At the EthernetGroup context (config>protection>eth-group(<group id>)),
enter:
force-active-port ethernet [<slot>/]<port>
The specified port is set to be active. You can choose the primary port (1) or
the secondary port (2).
 Port 1. Port 1 is configured as a permanently active link. Even if port 1
fails, the traffic is not switched to the standby port.
 Port 2. Port 2 is configured as a permanently active link. Even if port 2
fails, the traffic is not switched to the standby port.
To specify that neither of the ports is forced to remain active, enter:
no force-active-port
 To display the Ethernet group status:

enter:
show status
The Ethernet group status parameters are displayed.
Example
 To define link protection for ETX203AM:
• Ethernet group 1
• Protection port – Ethernet port 1/1
• Working port – Ethernet port 1/2
• Operation mode –One-to-one
exit all
configure protection ethernet-group 1
bind eth primary 1/1 secondary 1/2
oper-mode 1-to-1
exit all
 To display configuration information for the link protection:
ETX-2#configure protection ethernet-group 1
ETX-2>config>protection>eth-group(1)# info detail
bind ethernet primary 1/1 secondary 1/2
oper-mode 1-to-1
revertive
wait-to-restore 0
tx-down-duration-upon-flip 0
no shutdown
ETX-2 Link Protection 7-51


Chapter 8
Traffic Processing
This chapter describes traffic processing features:
• Bridge
• Classification by Port/Flow
• Layer-2 Control Protocol (L2CP) Processing
• Link Layer Discovery Protocol (LLDP)
• MLDv2 Snooping
• Pseudowire Connections
• PW Cross Connects
• Router
• Quality of Service (QoS)
8.1 Bridge
The ETX-2 bridge is a Layer-2 forwarding entity that can be VLAN-aware or
VLAN-unaware.
Applicable Products
• PCS port is relevant to ETX203AM with an SHDSL or VDSL2 module and
Standards
IEEE 802.1D
IEEE 802.1Q
Benefits
The bridge delivers E-LAN and E-Tree services.
ETX-2 Bridge 8-1

Chapter 8 Traffic Processing Installation and Operation Manual
The bridge operates in VLAN-aware or VLAN-unaware mode.
When the bridge is working in VLAN-aware mode:
• Bidirectional flows are supported.
• Each VLAN can work in E-LAN or E-Tree mode.
When the bridge is working in VLAN-unaware mode:
• Bidirectional flows are not supported.
• Only one egress flow per bridge port can be configured.
• The bridge can work in E-LAN or E-Tree mode.
Traffic through the bridge is configured via flows between non-bridge ports (e.g.
Ethernet, ETP, logical MAC, PCS, SVI) and bridge ports, allowing editing action at
the bridge ports.
Notes • Flow classifications source/destination MAC address or source/destination IP

address are not supported via bridge.
• If flows use the same queue before relevant MAC addresses are learned, the
policing does not function properly.
Different flows from the same port can be mapped to different bridge ports (see
Figure 8-1). However, different flows from one bridge port cannot be mapped to
different ports (see Figure 8-2).
Figure 8-1. Flows Mapped from Same Port to Different Bridge Ports – Allowed
Figure 8-2. Flows Mapped from Same Bridge Port to Different Ports –Not Allowed
In ETX220A devices, it is possible to configure bridge flows from the

management port. These flows are configured like all other bridge flows. Over
these flows, it is possible to both manage the device and pass other
management packets to devices on the network.
8-2 Bridge ETX-2

Installation and Operation Manual Chapter 8 Traffic Processing
Admission to Bridge
In order for a frame to be admitted to the bridge, its classification must match
the flow classification configured for the bridge port.
In VLAN-aware mode, VLAN membership is read-only and automatically learned
from the VLAN classification used in bridge port flows. Additionally, flows with
untagged classification must have a push editing action.
In VLAN-unaware mode, any packet may be admitted according to the configured
flow classifications.
Packet Editing on Reverse Flows

In the case of a bidirectional flow, the editing action can be specified for the flow
to the bridge port, but not for the reverse direction. ETX-2 performs editing on
the reverse direction according to the flow classification and specified editing
actions. The following table shows the editing action on the reverse flow, as well
as the VLAN learned from the flow.
Classification Editing of Flow with Editing of Reverse VLAN Value

Bridge Port as Egress Directional Flow
Port
VLAN X + any None None X
VLAN X..Y None Not allowed Not allowed
Untagged None None Not supported; use

push action
VLAN X None None X

Inner VLAN Y
Any classification Push X Pop X

(including untagged) p-bit fixed/copy/profile
Any classification Push X push inner Y Pop twice X

(including untagged and p-bit and inner p-bit
all) fixed/copy/profile
VLAN X Pop Push X Y

Inner vlan Y
VLAN X Pop Not allowed Not allowed

Inner vlan Y..Z
VLAN X Pop Not allowed Not allowed
VLAN X + any Swap VLAN Y Swap VLAN X Y

p-bit fixed/copy/profile
VLAN X Swap VLAN Z Swap VLAN X Z

Inner VLAN Y p-bit fixed/copy/profile
VLAN Y..Z Swap VLAN Y Not allowed Not allowed

VLAN X Push VLAN Y, swap VLAN Z Pop, swap X Y

ETX-2 Bridge 8-3

Classification Editing of Flow with Editing of Reverse VLAN Value

Bridge Port as Egress Directional Flow
Port
VLAN Y..Z Push VLAN X, swap VLAN Z Not allowed Not allowed
VLAN X Pop, swap VLAN Z Push X Z

Inner VLAN Y p-bit fixed/copy/profile Inner swap to Y
VLAN X Pop, swap 200 Not allowed Not allowed

Inner VLAN Y..Z p-bit fixed/copy/profile
VLAN X Swap VLAN Z, Swap X, inner swap Y Z

Inner VLAN Y inner swap VLAN K
VLAN X Swap VLAN Z, Not allowed Not allowed

Inner VLAN Y..Z inner swap VLAN K
Management via Bridge

In order to manage via the bridge, you need to configure the following (see
VLAN-Aware Bridge for an example of configuring the bridge for management):
• Router interface for management, bound to SVI
• Flow between SVI and bridge port (only one SVI<->bridge port flow can be
created per bridge port)
• Flow between Ethernet port and bridge port
Note It is recommended to manage ETX-2 via the bridge only if the bridge is
VLAN-aware.
Spanning Tree Protocol

Spanning Tree Protocol (STP) (802.1Q; previously 802.1D) is a Layer-2 loop
avoidance technique used in Ethernet networks. Loops are created in bridge-
based networks with more than one path between two endpoints. STP is used to
identify the best path to the destination, and block all other paths. The blocked
links are connected and kept inactive, creating automatic backup links.
Figure 8-4 illustrates STP operation. Bridge 3 is directly connected to Bridge 1 and
Bridge 2. Another physical link directly connects Bridge 1 to Bridge 2. Under
normal conditions, there is looping of data, causing broadcast congestion on the
network. When an STP is applied, Link A is blocked from transmitting any data,
but it remains on standby and listens to the network. If Link B or Link C fails, Link
A is activated, providing link and switch redundancy in the network.
8-4 Bridge ETX-2

Link A Link A
Bridge 1 Bridge 2 Bridge 1 Bridge 2
Link B Link C Link B Link C
Bridge 3 Bridge 3
Physical Topology Logical Topology
Figure 8-3. STP Operation
ETX-2 supports a single STP instance per chassis.
STP Bridge Types

The root bridge is the central reference bridge in the STP. It serves as a reference
for other bridges to determine their best cost path. Bridge 3 in Figure 8-4 serves
as a root in the application.
The root bridge is elected by automatically selecting the bridge in the network
with the lowest bridge ID. If the root bridge fails, the other bridges select a new
root device.
Link Cost
Each link in the network is allocated a certain cost. Usually, higher-bandwidth
links that are adjacent to the root bridge are assigned a lower cost. Lower-
bandwidth links that are multiple hops away from the root bridge are assigned a
higher cost. Once link costs are estimated, STP determines the lowest cost
connections from each bridge to the root bridge to determine the lowest-cost
path. It also blocks all the other higher cost links to prevent loops in the network.
Bridge Protocol Data Units

The bridges use Bridge Protocol Data Units (BPDUs) to exchange information
about network topology, bridge IDs, link costs etc. BPDUs help establish the best
route (least cost path) to the root bridge.
When there is a change in the network, relevant BPDUs are sent to all the
bridges/bridge ports by the root bridge. The bridges adjust their tables to
determine the new routes to the terminals.
Rapid Spanning Tree Protocol and Multiple Spanning Tree Protocol

Rapid Spanning Tree Protocol (RSTP) (802.1Q; previously 802.1W) is an evolution
of STP with some protocol enhancements, providing significantly faster spanning
tree convergence following a topology change. In RSTP, the link status of each
port is monitored proactively (instead of waiting for the BPDU messages) to
detect changes in network topology.
ETX-2 supports a single instance of RSTP over a VLAN aware or VLAN unaware
bridge (ETX-2 supports only one bridge).
ETX-2 Bridge 8-5

Multiple Spanning Tree Protocol (MSTP) (802.1Q; previously 802.1S) supports

several instances of forwarding topology on the same physical topology for load
balancing purposes (per a group of VLANs).
MSTP is supported over a VLAN-aware bridge only. MSTP maps a group of VLANs
(that have been configured at the bridge ports) into a single Multiple Spanning
Tree instance (MSTI). This means that the Spanning Tree Protocol is applied
separately for a set of VLANs instead of every VLAN in the whole network.
Different root bridges and different STP parameters can be individually configured
for each MSTI. So, one link can be active for one MSTI and the other link active
for the second MSTI. This enables some degree of load-balancing and generally
two MSTIs are used in the network for easier implementation. ETX-2 supports up
to 16 MSTIs per chassis, excluding MSTI0 (IST). All VLANs in the bridge that are
not configured to a specific MSTI, belong to MSTI0 (IST).
Figure 8-5 illustrates MSTP operation. MSTI 1 is used for forwarding traffic
marked with VLANs 10 and 20; MSTI 2 is used for VLANs 30 and 40; MSTI 0 – for
the remaining VLANs in the network.
Bridge 1 Bridge 2
Bridge 3
Physical Topology
Root Root
Bridge 1 Bridge 2 Bridge 1 Bridge 2 Bridge 1 Bridge 2
Root
Bridge 3 Bridge 3 Bridge 3

MSTI 1 Logical Topology MSTI 2 Logical Topology MSTI 0 Logical Topology
Figure 8-4. MSTP Operation
RSTP and MSTP uses OOB MNG MAC as the Bridge Identifier.
Note Before using RSTP or MSTP, you are required to configure trapping of
01-80-C2-00-00-00 using an L2CP profile with a peer action for
01-80-C2-00-00-00.
ETX-2 supports RSTP and MSTP per 802.1Q over a bridge with the following port
types:
• User
• Network
8-6 Bridge ETX-2

• PCS
• Logical MAC
Note ETX-2 does not support RSTP and MSTP over a bridge with the following port
types:
• OOB
• LAG group
• Ports configured with ETH protection
• Ports configured as G.8032 ring nodes
• Ports not connected to a physical port (such as a router interface or MEF 8
PW)
STP interoperability is supported per bridge port; when the RSTP/MSTP bridge
identifies STP messages on a port, it reverts to STP mode on that port.
Factory Defaults
By default, the bridge is not created in ETX-2. When the bridge is created, its
default configuration is VLAN-aware, filtering enabled, with no bridge ports or
VLANs. When VLANs are created, the default configuration is E-LAN mode.
ETX-2>config# bridge 1
ETX-2>config>bridge(1)$ info detail
name "BRIDGE 1"
vlan-aware
filtering
aging-time 300
echo "Spanning Tree Configuration"
# Spanning Tree Configuration
spanning-tree
mode rstp
max-age 20
forward-time 15
hello-time 2
priority 32768
tx-hold-count 6
exit
echo "MLD Snooping"
# MLD Snooping
mld-snooping
shutdown
host-aging-interval 260
router-aging-interval 260
exit
ETX-2>config>bridge(1)$ vlan 333
ETX-2>config>bridge(1)>vlan(333)$ info detail
maximum-mac-addresses 0
mode e-lan
The default STP parameters are as follows:
ETX-2 Bridge 8-7

admin-edge Disable
auto-edge Enable
cost (bridge port) 0
forward-time 15 sec
hello-time 2 sec
max-age 20 sec
max-hops 20
mcheck Disable
mode rstp
name empty string
priority (bridge port) 128
priority (bridge) 32768
restricted-role Disable
restricted-tcn Disable
revision 0
tx-hold-count 6
Configuring the Bridge

To configure the bridge, perform the following steps:
1. Configure the bridge.
2. Configure the bridge ports.
3. If working in VLAN-unaware mode:
 For E-Tree service, configure bridge mode to E-Tree and configure root.
4. If working in VLAN-aware mode:
 Configure VLANs. For E-Tree service in a VLAN, configure VLAN mode to
E-Tree and configure root.
5. Configure flows between non-bridge ports and bridge ports.
6. Configure RSTP/MSTP (optional).
7. Configure spanning tree L2CP profile.
Note In Bridge configuration, different bridge ports that egress to the same ETH port
with different VLAN editing cannot share the same queue block.
 To configure the bridge:

1. At the config# prompt, enter:
bridge 1
8-8 Bridge ETX-2

The config> bridge(1)# prompt is displayed.

Defining aging time for MAC aging-time <seconds> Possible values: 60–3000
table entries (seconds)
Clearing addresses in MAC table clear-mac-table
Enabling or disabling filtering [no] filtering To disable filtering forwarding

mode, type no filtering.
Configuring multicast snooping mld-snooping See MLDv2 Snooping.

at the bridge level
Configuring VLAN-unaware mode {e-tree | e-lan} Changing to E-Tree mode

bridge to E-Tree or E-LAN mode requires you to define a bridge
port as root.
Note: This command is
available only if the bridge is
VLAN-unaware.
Assigning a name to the bridge name <bridge-name> bridge-name – 1-32 character

string
Configuring bridge ports [no] port <port-number> port-number – number of

bridge port
Possible values:
1-16 for ETX203AM,
ETX203AX, ETX205A
1-80: ETX220A
See Configuring Bridge Ports.
To delete a bridge port, enter
no port <port-number>.
Configuring bridge port as root root <bridge-port> Notes:

port in E-Tree mode • This command is available
only if the bridge is
VLAN-unaware and the
mode is E-Tree.
• ETX220A: Supports more
than one root; the number
of roots supported is
equivalent to the number of
bridge ports.
• ETX203AX, ETX203AM,
and ETX205A: Support one
root. The following sanity
error appears if another
root port has already been
configured under the same
VPN: Root port is already
allocated.
ETX-2 Bridge 8-9

Displaying MAC address table show mac-address-table static See Viewing the MAC Address
(static addresses, dynamic show mac-address-table dynamic Table.
addresses, or all addresses)
show mac-address-table all
See Displaying MAC Table.
Searching MAC address table for show mac-table [vlan <vlan>] Vlan – VLAN to search for
specific MAC address [mac-address <mac-address>] mac-address – MAC address to
search for
Displaying VLAN information, show vlans Note: This command is

including which bridge ports available only if the bridge is
have been automatically added VLAN-aware.
as tagged VLAN members
Configuring STP parameters at spanning-tree See Configuring Bridge-Level

the bridge level RSTP Parameters.
Configuring static MAC address [no] static-mac <vlan-id> Note: Before creating the static
<mac-address> <bridge-port> MAC, you must create a flow
with the bridge port, and VLAN
(if applicable).
Defining VLANs (see below) [no] vlan <vlan-id> Possible values: 1–4094
To delete a VLAN, enter
no vlan <vlan-id>
Note: This command is
available only if the bridge is
VLAN-aware.
Setting mode to VLAN-aware or [no] vlan-aware To set mode to VLAN-unaware,

VLAN-unaware enter no vlan-aware.
Note: The VLAN aware mode
cannot be changed if bridge
port flows exist.
Configuring Bridge Ports

The following commands are available in the port level, at the
config>bridge(1)>port(<port-number>)# prompt.
Assigning a name to the bridge name <port-name> To delete the bridge port
port name, enter no name.
Administratively enabling the no shutdown To administratively disable the

bridge port bridge port, enter shutdown.
Note: Shutting down the
bridge port does not stop the
traffic.
Configuring STP parameters at spanning-tree See Configuring Bridge-Port-

the bridge port level Level RSTP/MSTP Parameters.
8-10 Bridge ETX-2

Configuring VLAN
The following commands are available in the vlan level, at the
config>bridge(1)>vlan(<vlan-id>)# prompt.
Defining maximum MAC table maximum-mac-addresses <max-mac> Possible values: 0–32000

size supported by the VLAN When using the bridge VLAN
MAC table limitation
(maximum-mac-addresses
limit), the first packet of each
learned MAC address is
dropped.
Configuring VLAN to work in mode {e-tree | e-lan} If you change to E-Tree, you
E-Tree or E-LAN mode need to define a bridge port as
root.
Configuring bridge port as root root <bridge-port number> Possible values: 1–16.
port in E-Tree mode no root < bridge-port_number> no root defines a bridge port
as a leaf in E-Tree mode.
Notes:
• This command is available
only if the VLAN mode is
E-Tree.
• Supports one root per VLAN
• ETX220A: Supports more
than one root per VLAN; the
number of roots supported
is equivalent to the number
of bridge ports.
• ETX203AX, ETX203AM,
and ETX205A: Support one
root per VLAN. The
following sanity error
appears if another root port
has already been configured
under the same VPN: Root
port is already allocated.
Configuring RSTP/MSTP
RSTP and MSTP are configured at the bridge and bridge-port levels.
Configuring Bridge-Level RSTP/MSTP Parameters
 To configure the bridge-level RSTP/MSTP parameters:

• In the config>bridge(bridge_number)# prompt, enter spanning-tree and
configure the bridge-level RSTP/MSTP parameters as illustrated and explained
below.
ETX-2 Bridge 8-11

Configuring the amount of time forward-time <4–30> sec When configuring forwarding
a port remains in the listening time, follow this rule:
and learning states before 2 × (forwarding time - 1) =>
entering the forwarding state maximum aging time
Defining how often ETX-2 hello-time <1–10> sec Limitation: Define hello-time
broadcasts hello messages to must be configured so that
other devices to indicate that 2 × (hello-time - 1) <= max-
the bridge is alive age.
Defining maximum aging time for max-age <6–40> sec

spanning tree operation
Defining the number of hops in max-hops <6–40>

an MST region before the BDPU
is discarded and the port
information is aged out
Selecting spanning tree mode {rstp | mstp} MSTP-related parameters are

operation mode masked, when the bridge
operates in RSTP mode.
Configuring bridge-level MST mst <1–4094> no mst (msti_number) deletes

instance level no mst MST instance.
See configuration instructions
below.
Specifying spanning tree priority priority <0, 4096, 8192, 12288, This is the value of the first
of the bridge 16384, 20480, 24576, 28672, 32768, two octets of the bridge ID. It
36864, 40960, 45056, 49152, 53248, is used to make the bridge
57344, 61440> more (or less) likely to be
chosen as the root bridge.
The lower the number, the
more likely the bridge will be
chosen as the root bridge.
Defining MSTP configuration name <string> For two or more bridges to be

name in the same MST region, they
must have the same
Defining MSTP configuration revision <0–65535>
configuration revision number
revision number
and name.
Displaying bridge-level spanning show status See Displaying Spanning Tree

tree status Status below.
Selecting the maximum number tx-hold-count <1–10> BPDUs per sec

of BPDUs that can be
transmitted to a port in one
second
 To configure bridge-level MST instance:

• In the config>bridge(bridge_number)>spanning-tree # prompt, enter mst
(msti_number) and configure the bridge-level MSTI parameters as illustrated
and explained below.
8-12 Bridge ETX-2

Specifying MSTI priority priority<0, 4096, 8192, 12288,

16384, 20480, 24576, 28672, 32768,
36864, 40960, 45056, 49152, 53248,
57344, 61440>
Mapping VLANs to MST instance vlan <1–4094> Map list of VLANS to MST
no vlan instance.
no vlan (vlan_lsit) removes
VLAN mapping from the MSTI.
This command can be repeated
to configure additional VLAN
mappings.
For two or more bridges to be
in the same MST region, they
must have the same VLAN-to-
MSTI mapping.
Displaying bridge-level MSTI show status See Displaying Spanning Tree

status Status below.
Configuring Bridge-Port-Level RSTP/MSTP Parameters
 To configure the bridge-port-level RSTP/MSTP parameters:

• In the config>bridge(bridge_number)>port(port_number)# prompt, enter
spanning-tree and configure the bridge-port-level RSTP/MSTP parameters as
illustrated and explained below.
Defining bridge port as an edge admin-edge no admin-edge disables edge

port no admin-edge port functionality.
An edge port is put into the
forwarding state upon linkup,
for faster convergence.
An edge port connected to a
bridge could prevent the
spanning tree from detecting
and disabling loops.
Enabling/disabling automatic auto-edge no auto-edge disables

identification of edge ports no auto-edge automatic edge port
identification.
The edge status of an auto
edge port is automatically
disabled upon receiving a BPDU
(regardless of the configured
admin-edge value).
ETX-2 Bridge 8-13

Defining port path cost cost <0–200000000> If a loop occurs, the path cost
is used to select an interface
to place into the forwarding
state.
A lower path cost represents
higher speed links. It is
recommended to use the
default cost value (0) to let
ETX-2 to compute the best
possible cost according to the
link bandwidth (Table 8-44).
Activating migration check by mcheck If a port connects to a bridge

the port running STP, this port
automatically migrates to the
STP-compatible mode, and
does not revert automatically
back to MSTP/RSTP mode.
mcheck forces protocol
renegotiation with neighboring
devices, to check if they are
MSTP/RSTP-compatible.
Configuring bridge-port-level mst <1–4094> no mst (msti_number) deletes

MSTI no mst MST instance.
See configuration instructions
below.
Defining bridge port priority port-priority <0, 16, 32, 48, 64, 80, This is the value of the first
96, 112, 128, 144, 160, 176, 192, octet of the bridge port ID. If a
208, 224, 240> loop occurs, the MSTP uses the
port priority, when selecting an
interface to put into the
forwarding state.
The lower the number, the
higher the port priority (the
lowest numbered port is
selected if a tie breaker is
needed).
Preventing/allowing bridge port restricted-role no restricted-role removes

to become a root port no restricted-role bridge port restriction.
Restricted port cannot become
a root port, even it is the most
likely candidate.
8-14 Bridge ETX-2

Enabling/disabling propagation restricted-tcn no restricted-tcn enables

of topology changes by the port no restricted-tcn propagation of topology
changes by the port.
A restricted-tcn port does not
propagate received topology
change notifications and
topology changes to other
ports.
Restricting propagation of
topology changes can be used
to prevent bridges external to a
network core influencing the
active spanning tree topology.
Usually, it is applied to bridges
which are not under the full
control of the network
administrator.
Displaying bridge port spanning show status See Displaying Spanning Tree
tree status Status below.
Activating spanning tree on the shutdown shutdown disables spanning

bridge port no shutdown tree on bridge port.
Table 8-1. Bandwidth Values for Bridge Port Path Cost
Link Bandwidth Cost
<= 100 kbps 200 000 000
1 Mbps 20 000 000
10 Mbps 2 000 000
100 Mbps 200 000
1 Gbps 20 000
10 Gbps 2 000
100 Gbps 200
1 Tbps 20
10 Tbps 2
 To configure bridge-port-level MST instance:

• In the config>bridge(bridge_number)>port(port_number)>spanning-tree #
prompt, enter mst (msti_number) and configure the bridge-level MSTI
parameters as illustrated and explained below.
Defining MSTI port path cost cost <0–200000000>
ETX-2 Bridge 8-15

Specifying MSTI port priority port-priority <0, 16, 32, 48, 64, 80,
96, 112, 128, 144, 160, 176, 192,
208, 224, 240>
Displaying bridge-port-level MSTI show status See Displaying Spanning Tree

status Status below.
Displaying Spanning Tree Status

You can display spanning tree status at the following levels:
• Bridge
• Bridge MSTI
• Bridge port
• Bridge port MSTI
 To display spanning tree status:

• At the relevant prompt (bridge, bridge MSTI, bridge port, bridge port MSTI),
type show status.
One of the following status screens is displayed.
Mode MSTP, Root, Regional Root
Bridge: Priority 32768, Address 00:11:22:33:44:55
Root: Priority 32768, Address 00:11:22:33:44:55,
Cost 012, Port 1 (Eth 1/2)
Regional Root: Priority 32768, Address 00:11:22:33:44:55, cost
012
Configured Times:
Max Age 01, Hello 01, Forward Delay 01
Actual Times:
Max Age 01, Hello 01, Forward Delay 01, Hold 01
Topology Change Total 012, Since Last 2 days 00:11:22
Figure 8-5. Spanning Tree Status, Bridge Level
MST Instance 1, Root

VLANs Mapped 1-10, 20
Bridge: Priority 32768, Address 00:11:22:33:44:55, Root
Root: Priority 32768, Address 00:11:22:33:44:55
Cost 32768, Port 1 (Eth1/1)
Topology Change: Total 1234, Since Last 2 days 22:11:00
BP Interface Role State

-- --------- ---------- ----------
01 Eth1/1 Backup Blocking
02 Eth1/2 Designated Forwarding
Figure 8-6. Spanning Tree Status, Bridge MSTI Level
Port 1 (Eth1/1), Root, Forwarding, Edge (default)

Path Cost 200000000, Priority 128, Up 2 days 00:11:22
Designated Root: Priority 32768, Address 00:11:22:33:44:55
Designated Bridge: Priority 32768, Address 00:11:22:33:44:55
8-16 Bridge ETX-2

Port 1, Port Priority 128, Cost 200000000

Regional Root: Priority 32768, Address 00:11:22:33:44:55, Cost 200000000
Hello Timer 10
Forward Transitions: 11
Figure 8-7. Spanning Tree Status, Bridge Port Level
Port 1 (Eth1/1), MSTI 1000, Root, Forwarding, Edge (default)

Up 2 days 22:11:00
VLANs mapped 1-20, 100
Designated Root: Priority 32768, Address 00:11:22:33:44:55, Port 10
Regional Root: Priority 32768, Address 00:11:22:33:44:55, Cost 200000000
Figure 8-8. Spanning Tree Status, Bridge Port MSTI Level
Configuring BPDU Peers

When configuring RSTP/MSTP, attach L2CP profile directly to the physical port,
with MAC 0x00 and action set to peer.
The following example shows the necessary configuration.
 To configure an L2CP profile for MAC 0x00 with peer action:

ETX-2 >config>port# l2cp-profile RSTP
ETX-2 >config>port>l2cp-profile RSTP# mac 0x00 peer
exit
Examples
VLAN-Aware Bridge
This section illustrates the following configuration for ETX203AM:
• VLAN-aware bridge, with bridge ports 1–4
• VLAN 51 used for management, in E-LAN mode
• VLAN 100 used for traffic, in E-Tree mode, with root bridge port 2
• VLAN 200 used for traffic, in E-LAN mode
• Management flows (unidirectional) between SVI 1 and bridge port 1
• Traffic flows (bidirectional) between:
 Ethernet port 1/1 and bridge port 2, with classification VLAN 100 and
VLAN 200
 Ethernet port 0/3 and bridge port 3, with classification VLAN 100
 Ethernet port 0/4 and bridge port 4, with classification VLAN 100
#*******Configure SVI
no shutdown
exit all
#*******Configure bridge
configure bridge 1
vlan-aware
ETX-2 Bridge 8-17

#*******Configure bridge ports

port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
no shutdown
exit
port 4
no shutdown
exit
#*******Configure VLANs
vlan 51
exit
vlan 100
mode e-tree
root 2
exit
vlan 200
exit all
#*******Configure classifier profiles

configure flows
classifier-profile 51 match-any
match vlan 51
exit
match vlan 100
exit
match vlan 200
exit
classifier-profile unt match-any
match untagged
exit
#*******Configure management flows

flow mng_in
classifier 51
egress-port svi 1 queue 0
no policer
no shutdown
exit
flow mng_out
classifier unt
ingress-port svi 1
no shutdown
8-18 Bridge ETX-2

exit
#*******Configure management flow to physical port

flow 1toBP2_51
classifier 51
no shutdown
exit
#*******Configure bidirectional traffic flows

flow 1toBP2_100
classifier 100
no shutdown
exit
flow 1toBP2_200
classifier 200
no shutdown
exit
flow 3toBP3_100
classifier 100
no shutdown
exit
flow 4toBP4_100
classifier 100
no shutdown
exit all
#*******Configure router interface

configure router 1
interface 1
address 10.10.10.20/24
bind svi 1
dhcp-client
client-id mac
exit
no shutdown
exit all
save
ETX-2 Bridge 8-19

Displaying VLAN Information

This section illustrates displaying VLAN information after performing the
configuration specified in VLAN-Aware Bridge. The VLAN information shows the
following:
VLAN 51 Bridge ports 1–2 were automatically added as tagged

ports.
VLAN 100 Bridge ports 2–4 were automatically added as tagged

ports.
VLAN 200 Bridge port 2 was automatically added as a tagged port.

ETX-2# configure bridge 1
ETX-2>config>bridge(1)# show vlans
VLAN ID : 51
Tagged Ports : 1..2

Untagged Ports : 0
VLAN ID : 100
Tagged Ports : 2..4

Untagged Ports : 0
VLAN ID : 200
Tagged Ports : 2
Untagged Ports : 0
VLAN-Unaware Bridge
This section illustrates the following configuration for ETX203AX or ETX205A:
• VLAN-unaware bridge, with bridge ports 1–4
• Traffic flows (unidirectional), with classification to match all, between:
 Ethernet port 1 and bridge port 2
configure bridge 1
no vlan-aware

port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
8-20 Bridge ETX-2

no shutdown
exit
port 4
no shutdown
exit all
#*******Configure classifier profile

configure flows
match all
exit
#*******Configure unidirectional traffic flows

flow 1toBP2
class all
no shutdown
exit
flow BP2to1
class all
egress-port ethernet 1 block 0/1
no policer
no shutdown
exit
flow 3toBP3
class all
no shutdown
exit
flow BP3to3
class all
no policer
no shutdown
exit
flow 4toBP4
class all
no shutdown
exit
flow BP4to4
class all
no policer
ETX-2 Bridge 8-21

no shutdown
exit
Creating Static MAC Address

This section illustrates creating a static MAC address after performing the
configuration specified in VLAN-Aware Bridge.
exit all
configure bridge 1
static-mac 100 01-02-03-04-05-06 2
exit all
Viewing the MAC Address Table

You can display an ETX-2 MAC table, which provides information on static and
dynamic addresses, and the bridge ports and VLANs associated with them.
 To display MAC address table:

• At the config>bridge(bridge_number)# prompt, enter show mac-address-table
{static | dynamic | all}.
The MAC address table is displayed.
Note ETX-2 displays only the first 1000 entries. To view the entire MAC table,
download it to your PC, using SFTP. Refer to File Operations in the Administration
chapter.
ETX-2# configure bridge 1

ETX-2>config>bridge(1)# show mac-address-table all
Total MAC Addresses : 22
Static MAC Addresses : 12
Dynamic MAC Addresses : 10
VLAN MAC Address Port Status

---------------------------------------------------------------
20 00-00-00-00-00-01 2 Static
40 00-00-00-00-00-01 2 Static
50 00-00-00-00-00-01 2 Static
60 00-00-00-00-00-01 2 Static
60 00-00-00-00-00-E1 7 Dynamic
100 00-00-00-00-00-E1 7 Dynamic
100 01-02-03-04-05-06 2 Static
130 00-00-00-00-00-E1 7 Dynamic
150 00-00-00-00-00-E1 7 Dynamic
160 00-00-00-00-00-E1 7 Dynamic
170 00-00-00-00-00-01 2 Static
180 00-00-00-00-00-01 2 Static
190 00-00-00-00-00-01 2 Static
200 00-00-00-00-00-01 2 Static
200 00-00-00-00-00-E1 7 Dynamic
230 00-00-00-00-00-E1 7 Dynamic
250 00-00-00-00-00-E1 7 Dynamic
260 00-00-00-00-00-E1 7 Dynamic
270 00-00-00-00-00-01 2 Static
8-22 Bridge ETX-2

280 00-00-00-00-00-01 2 Static

290 00-00-00-00-00-01 2 Static
290 00-00-00-00-00-E1 7 Dynamic
8.2 Classification by Flow

Traffic is classified into flows, which are unidirectional or bidirectional entities
that connect two physical or logical ports. You define classifier profiles to specify
the criteria for flows. The classification is per port and is applied to the ingress
port of the flow.
Applicable Products
• PCS port is relevant to ETX203AM with an SHDSL or VDSL2 module and
• Pseudowire (PW) is relevant to ETX205A with built-in E1/T1 ports.
• Multi-CoS flows per MEF 10.3 are relevant only for ETX220A.
Standards
IEEE 802.1ad, IEEE 802.1Q
Benefits
User traffic can be classified into different Ethernet flows (EVC.CoS) to provide
services in a flexible manner.
Ethernet flows are unidirectional, or in the case of bridge flows, can also be
bidirectional. For unidirectional flows, you have to define two flows between the
two ports, one for each direction. For bidirectional flows, you only need to define
one flow from a port to a bridge port, and specify the reverse-direction
command.
ETX-2 Classification by Flow 8-23

Note • In the case of bridge flows, you can configure two flows between a physical
port and a bridge port (one flow in each direction) or one bidirectional flow
(reverse-flow)).
• RAD recommends using bidirectional flows for bridge flows, as all testing is
performed with bidirectional flows – a newer and more advanced method
(than unidirectional flows).
• When configuring two unidirectional flows, in the flow from the egress bridge
port to the ingress physical port, the physical port automatically takes the
queue from the CoS configured in the flow. Therefore, in the configuration of
the flow in the other direction, from the ingress bridge port to the egress
physical port, you cannot configure a queue in the egress physical port. Doing
so results in the following error: A flow from bridge port must not use a
Queue Mapping or a Queue Mapping profile.
Flow Classification
The ingress traffic is first classified into flows according to classification profiles.
The classification is per port and is applied to the ingress port of the flow.
Packets can be classified by means of their VLAN IDs and other criteria, fully
specified in Configuring a Classifier Profile.
In the following descriptions, VLAN refers to the service provider (outer) VLAN,
sometimes referred to as SP-VLAN, while inner VLAN refers to the Customer
Entity VLAN, sometimes referred to as CE-VLAN or C-VLAN.
Flow classifications that apply to the same port are allowed in the combinations
shown in Table 8-2. The priority shown is used to determine which classification
is used if incoming packets for the port fit the criteria of more than one
classification. Priority 4 is the lowest, priority 1 is the highest. NNI indicates
ingress network port, UNI indicates ingress user port.
Table 8-2. Flow Classification Combinations
Classification Other Classifications Allowed On Range Max Number Priority NNI/UNI

Same Ingress Port Ranges
Unclassified VLAN – 1 4 Both

(all-to-one VLAN + IP precedence
bundling) VLAN + DSCP
VLAN + VLAN priority
VLAN + Non-IP
VLAN priority
IP precedence
DSCP
Source MAC address
Destination MAC address
My-MAC
Source IP address
Destination IP address
My-IP
Non-IP
Untagged
8-24 Classification by Flow ETX-2


VLAN VLAN + VLAN priority 0–4094 30 2 Both

See Note 1 VLAN + IP precedence
VLAN + DSCP
VLAN + source MAC address
VLAN + destination MAC address
VLAN + source IP address
VLAN + destination IP address
VLAN + inner VLAN
VLAN + VLAN priority + inner VLAN
Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Untagged
VLAN + VLAN VLAN 0–4094 + 0–7 30 2 Both

priority VLAN + source MAC address
See Note 1 VLAN + destination MAC address
VLAN + inner VLAN
Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Untagged
VLAN + IP VLAN 0–4094 + 0–7 30 2 Both

precedence Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Non-IP
Untagged


VLAN + DSCP VLAN 0–4094 + 0–63 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Non-IP
Untagged
VLAN + source MAC VLAN 0–4094 + One VLAN value 1 Both

address VLAN + VLAN priority MAC address + one MAC
VLAN + inner VLAN address range
VLAN + destination VLAN 0–4094 + One VLAN value 1 Both

MAC address VLAN + VLAN priority MAC address + one MAC
VLAN + inner VLAN address range
VLAN + source VLAN 0–4094 + 10 × VLAN 2 Both

IP address VLAN + VLAN priority IP address value + IP
VLAN + inner VLAN address/range
VLAN + inner VLAN + VLAN priority
VLAN + destination VLAN 0–4094 + 10 × VLAN 2 Both

IP address VLAN + VLAN priority IP address value + IP
VLAN + inner VLAN address/range
VLAN + inner VLAN + VLAN priority
VLAN + inner VLAN VLAN Single value for 30 (for inner 3 Both
VLAN + VLAN priority VLAN and range range)
VLAN + VLAN priority + inner VLAN for inner VLAN
VLAN + source MAC address
VLAN + inner VLAN VLAN Single value for 30 (for inner 3 Both
+ VLAN priority VLAN + inner VLAN VLAN and range range)
VLAN + source MAC address for inner VLAN


VLAN + non-IP Unclassified 0–4094 30 1 Both

VLAN
VLAN + IP precedence
VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP
Untagged
VLAN priority Unclassified 0–7 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Untagged
IP precedence Unclassified 0–7 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Non-IP
DSCP Unclassified 0–63 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Non-IP
Source MAC address VLAN MAC address 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged


Destination MAC VLAN MAC address 1 1 Both

address VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
My-MAC
Unclassified
Non-IP
Untagged
My-MAC VLAN 1 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Source IP address VLAN IP address 10 1 Both

See Note 2 VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Destination VLAN IP address 10 1 Both

IP address VLAN priority
See Note 2 VLAN + VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
My-IP
Unclassified
Non-IP
Untagged


My-IP VLAN 1 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Non-IP Unclassified – 1 1 Both

VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP
Untagged Unclassified – 1 2 Both

VLAN
VLAN priority
VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP

Note 1 If you combine the classifications VLAN and VLAN + VLAN priority, the VLANs must
be different.
For example, the following combination is not allowed:
• VLAN 100
• VLAN 100 + p-bit 5
The following combination is allowed:
• VLAN 100
You can achieve the combination VLAN 100 and VLAN 100 + p-bit 5 via the
following:
• VLAN 100 + p-bit 0–4, 6–7
You cannot create flows with VLAN classification overlap.
For example, the following combination is not allowed:
• VLAN 100..300 + p-bit 3
A sanity check detects that VLAN 200 is in the range 100-300 (i.e. VLAN overlap),
and does not allow this configuration.
Note 2 If you apply two classification profiles with IP address ranges to a port, the
profiles must have the same mask.
For example:
The following is valid (mask1 equal to mask2):
Classification #1: 10.10.0.0 –10.10.0.255 -> mask1 = 255.255.255.0
The following is invalid (mask1 not equal to mask2):
Classification #1: 10.10.0.0–0.10.0.255 -> mask1 = 255.255.255.0
Classification Keys
The following classification keys are supported per port:
• Legacy
• IPv4DA+DSCP
• IPv4SA+DSCP
• VLAN
• VLAN Inner VLAN
Table 8-3 shows for the IPv4DA+DSCP and IPv4SA+DSCP classification keys, the
queue mapping method and the flows that can be configured, the range per flow,
and the flow priority.
Table 8-4 and Table 8-5 show for the VLAN and VLAN Inner VLAN classification
keys, respectively, the queue mapping method and the parameters that can be
configured in a flow, the range per classification rule, maximum number of rules

per flow, and the internal flow priority. See Table 8-2 for the combinations of
flow classifications that are allowed per port.
Table 8-3. Queue Mapping Method and Configurable Flows – IPv4DA+DSCP and IPv4SA+DSCP
Classification Keys
Key and Flow Range (per defined flow) Flow Priority Comments
Queue/Priority
Mapping Method
Key: IPv4DA+DSCP IPDA/length Up to 10 IPDA ranges. 1 If DSCP is not

Mapping Method: configured, it
implies that the
1. Flow
DSCP range is 0–63.
2. DSCP
IPDA/length+DSCP Up to 10 pairs of one IPDA 1 Mix of IPDA rules
range and one DSCP range and IPDA+DSCP
rules on the same
flow is supported.
None IP 1
Key: IPv4SA+DSCP IPSA/length Up to 10 IPSA ranges. 1 If DSCP is not

Mapping Method: configured, it
implies that the
3. Flow
DSCP range is 0–63.
4. DSCP
IPSA/length+DSCP Up to 10 pairs of one IPSA 1 Mix of IPSA rules
range and one DSCP range and IPSA+DSCP rules
on the same flow is
supported.
None IP 1
Table 8-4. Queue Mapping Method and Configurable Flow Classification Parameters – VLAN
Classification Key
Queue/Priority Classification Profile Parameter Range (per defined Max. # of Internal

Mapping Method classification rule) Rules per Flow Flow
priority
5. Flow Untagged NA 1 3
6. DSCP Unclassified NA 1 2
7. P-bit
VLAN VLAN range [0..4094] 30 2
VLAN+P-bit VLAN range [0..4094]; 30 2
P-bit range [0..7]
VLAN+DSCP VLAN range [0..4094]; 30 2A
DSCP range [0..63]
VLAN+IP-P VLAN range [0..4094]; 30 2A
IP-P range [0..7]
VLAN+MAC SA Single VLAN value 1 1
SA MAC range

Queue/Priority Classification Profile Parameter Range (per defined Max. # of Internal

Mapping Method classification rule) Rules per Flow Flow
priority
VLAN+MAC DA Single VLAN value 1 1

DA MAC range
VLAN+IP SA VLAN range [0..4094], 10 1
SRC IP
VLAN+IP DA VLAN range [0..4094], 10 1
Dest IP
VLAN+Ethertype Single VLAN value and 1 1
single Ethertype value
VLAN+Non IP VLAN Range [0..4094] 30 2
MAC SA SA MAC Range 1 1
MAC DA DA MAC Range 1 1
IP SA SRC IP Range 1 1
IP DA DST IP Range 1 1
Ethertype Single VLAN value 1 1
Non IP NA 1 2
Table 8-5. Queue Mapping Method and Configurable Flow Classification Parameters – VLAN Inner
VLAN Classification Key
Queue/Priority Classification Profile Range (per defined Max. # of Internal

Mapping Method Parameter classification rule) Rules per Flow Flow
priority
8. Flow Untagged NA 1 3
9. DSCP Unclassified NA 1 2
10. P-bit
VLAN, Inner VLAN Single Outer value 30 2
Inner VLAN range
[0..4094]
VLAN, Inner VLAN, p-bit Single Outer value 30 2
Inner VLAN range
[0..4094]
P-bit range [0..7]
VLAN, Inner VLAN, DSCP Single Outer value 30 2
Inner VLAN range
[0..4094]
DSCP range [0..63]
VLAN, Inner VLAN, non IP VLAN range [0..4094] 30 2
VLAN (one tag level only) VLAN range [0..4094] 30 2
MAC SA SA MAC range 1 1

Queue/Priority Classification Profile Range (per defined Max. # of Internal

Mapping Method Parameter classification rule) Rules per Flow Flow
priority
MAC DA DA MAC range 1 1

IP SA SRC IP range 1 1
IP DA DST IP range 1 1
Ethertype Single VLAN value 1 1
Non IP NA 1 2
VLAN Actions
You can perform marking and tagging actions on the outer and inner VLAN such
as adding, replacing, or removing, as well as marking with p-bit. Only certain
combinations of actions on the outer and inner VLAN are allowed. If no action is
performed for the outer VLAN, then for the inner VLAN there must be no action
performed. Table 8-6 shows valid VLAN action combinations 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. Any
combination not shown in the table is not supported.
In the ETX-2 bridge, if one of the bridge ports is configured with VLAN
classification, and another bridge port with VLAN + p-bit classification, in order to
mark the p-bit of the inner VLAN, you must mark the required p-bit at the VLAN +
p-bit bridge port.
Table 8-6. Valid VLAN Action Combinations
Action on: Egress VLAN(s) and P-bit(s) for Ingress Frame Types:
Outer VLAN Inner VLAN Untagged One VLAN (X) Double VLANs
(X and Y)
None None Untagged X X, Y

Pop None Not applicable – Untagged Y
unsupported
Pop Mark with VLAN A Not applicable – Not applicable – A
unsupported unsupported
Pop Pop Not applicable – Not applicable – Untagged
unsupported unsupported
Push VLAN A None A A, X A, X, Y
Push VLAN A Mark with VLAN B A A, B A, B, Y
Push VLAN A Mark with p-bit D A A A,
X + p-bit D X + p-bit D,
Y
Push VLAN A Mark with profile F A A, A,
See Note 1 X + p-bit according X + p-bit according
to F to F,
Y

Action on: Egress VLAN(s) and P-bit(s) for Ingress Frame Types:
Outer VLAN Inner VLAN Untagged One VLAN (X) Double VLANs
(X and Y)
Push VLAN A. Push VLAN B, A + p-bit 7 A + p-bit according A + p-bit according
mark with profile E mark with p-bit D according to E, to E, to E,
B + p-bit D B + p-bit D, B + p-bit D,
X X,
Y
Push VLAN A. Push VLAN B, A + p-bit C, A + p-bit C, A + p-bit C,
mark with p-bit C mark with p-bit D B + p-bit D B + p-bit D, B + p-bit D,
X X,
Y
Push VLAN A. Push VLAN B. A + p-bit 7 A + p-bit according A + p-bit according
mark with profile E mark with profile F according to E, to E, to E,
See Note 1 B + p-bit 7 B + p-bit according B + p-bit according
according to F to F, to F,
X X,
Y
Push VLAN A. Push VLAN B. A + p-bit C, A + p-bit C, A + p-bit C,
mark with p-bit C mark with profile F B + p-bit 7 B + p-bit according B + p-bit according
according to F to F, to F,
X X,
Y
Mark with VLAN A None Untagged A A, Y
Mark with VLAN A Mark with p-bit D Not applicable – Not applicable – A,
unsupported unsupported Y + p-bit D
Mark with p-bit C Mark with p-bit D Not applicable – Not applicable – X+ p-bit C,
unsupported unsupported Y + p-bit D
Mark with VLAN A Mark with p-bit D Not applicable – Not applicable – A + p-bit,
+ p-bit unsupported unsupported Y + p-bit D
Mark with VLAN A Mark with VLAN B Not applicable – Not applicable – A + p-bit according
+ profile E +p-bit D unsupported unsupported to E,
B +p-bit D
Permanent Flow Loopbacks

You can set up a permanent flow loopback by specifying MAC and IP address
swap for flow traffic in the marking context, and saving it as part of the
configuration.
Unidirectional Hubs
You can configure a unidirectional hub (UDH) by defining a group of flows with
the same ingress port, classifier profile, and policer aggregate, and different
egress ports. The egress ports must be physical Ethernet ports, not virtual ports
such as SVI, ETP, etc. Only one queue-mapping profile and one marking profile
can be used for the flows in a UDH group; however, VLAN tag editing can be
different in the different flows.

In unidirectional hub mode, the rate of each flow that is part of the group cannot
exceed the rate of the queue with the lowest rate; therefore, it is not possible to
use different rates for different p-bits.
Multi-CoS Flows
A multi-CoS flow per MEF 10.3 contains multiple classes of service. It can be
assigned an envelope policer (see Envelope Bandwidth Profiles) to enable sharing
bandwidth between the CoSs, where each CoS is assigned a rank. Alternatively, if
bandwidth policing is not required but per-CoS counters are required.you can
specify that a multi-CoS flow has per-CoS counters.
Figure 8-9. Multi-CoS Flow
The CoS-to-rank mapping is done automatically by the device, according to the

CoSs that are configured in the assigned envelope policer. CoS 0 is mapped to
the highest rank needed for the number of configured CoSs, then CoS 1 is
mapped to the next highest rank, ending with mapping the last configured CoS to
1. For example, if CoS 1, CoS 5, and CoS 6 are configured, then three ranks are
used, and the mappings are:
• CoS 1 to rank 3
• CoS 5 to rank 2
• CoS 6 to rank 1
Traffic that is mapped to a CoS that does not correspond to a CoS configured in
the envelope profile is dropped (the port-level counter Unmapped CoS Frames
indicates how many frames were dropped for this reason).
Multi-CoS flows must be assigned a CoS mapping profile, which can be used to
specify the mapping of untagged traffic to CoS in case of p-bit method, or non IP
to CoS in the case of DSCP.
Multi-CoS flows support only the following ingress/egress ports:
• Ingress and egress port are Ethernet or logical MAC.
• Egress port is bridge port (unidirectional and reverse flows supported).
• Egress port is ETP subscriber or transport port.
The queue block mapping for the egress port in a multi-CoS flow is done as CoS
to queue mapping as follows: Cos 0 to queue 0, Cos 1 to queue 1, CoS 2 to
queue 2, etc. There is a predefined queue map profile with this mapping, with the
reserved name q-map-for-cos. This profile cannot be modified.
If a marking profile is assigned to a multi-CoS flow, it must be type CoS to p-bit.

Factory Defaults
By default, no flows are configured.
Configuring a Classifier Profile

You can define classifier profiles to apply to flows for flow classification.
Note When a classification profile is assigned to a flow, each match in the profile is
allocated one of the available internal classification match entries, according to
the flow ingress port.
For example, if a classification profile is defined with matches to two different
VLANS, then if the profile is assigned to two flows that use different ingress
ports, the result is that four internal classification match entries are allocated. If
the profile is assigned to two flows that use the same ingress port, the result is
that two internal classification match entries are used.
 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 <profile-name> match-any
The system switches to the context of the classifier profile
(config>flows>classifier-profile(<profile-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 <src-ip-low>] [to-src-ip <src-ip-high>]
[dst-ip <dst-ip-low>] [to-dst-ip <dst-ip-high>] [ether-type <ether-type>]
[untagged] [non-ip] [my-mac] [my-ip] [all]
Note Using the matching type my-mac or my-ip is equivalent to using the matching
type dest-mac <device-MAC-address> or dest-ip <host-IP-address>.
4. When you have completed specifying the criteria, enter exit to exit the
classifier profile context.
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 <classifier-profile-name> If the flow is multi-CoS, the
classifier profile classification must be one of the
following:
• VLAN, VLAN + inner VLAN, VLAN
range
• Match all
• Untagged
Associating multi-CoS flow with cos-mapping-profile <cos-mapping-profile-name>

CoS mapping profile
Discarding traffic transmitted via drop

the flow
Specifying the ingress packet ingress-color green You can set the packet color to
color ingress-color yellow green or yellow, or use a color
ingress-color profile <color-mapping-profile-name> mapping profile (see Color Mapping
Profiles).
Specifying the ingress port ingress-port ethernet [<slot>/]<port> Note: If working with PW, packets
ingress-port bridge-port <bridge-number> forwarded to the SVI must be
<bridge-port-number> untagged, and pop any VLAN.
ingress-port etp <etp-name> {subscriber | transport}
<port-number>
ingress-port logical-mac <port>
ingress-port pcs <port>
ingress-port svi <port>

Specifying the egress port, and egress-port ethernet [<slot>/]<port> [queue If a queue mapping profile is used,
defining queue <queue-id> block <level-id/queue-id>] it must be compatible with the
egress-port ethernet [<slot>/]<port> classification criteria of the flow,
[queue-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 ethernet <port> [block <level-id/queue-id>]
egress-port bridge-port <bridge-number> For multi-CoS flows, the predefined
<bridge-port-number> [cos <cos-id>] q-map-for-cos queue mapping
profile should be used.
egress-port bridge-port <bridge-number>
<bridge-port-number> [cos-map-profile Notes:
<cos-map-profile-name>] • In the case that you choose to
egress-port etp <etp-name> {subscriber | transport} configure two flows between a
<port-number> [cos <cos-id>] bridge port and physical port (as
opposed to one bidirectional
egress-port etp <etp-name> {subscriber | transport}
flow), you cannot configure a
<port-number> [cos-map-profile
queue number in the egress
<cos-map-profile-name>]
physical port of the flow where
egress-port logical-mac <port> [queue <queue-id>
the bridge port is the ingress
block <level-id/queue-id>]
port, as the physical port’s
egress-port logical-mac <port> [queue-map-profile queue is automatically taken
<queue-map-profile-name> block <level-id/queue-id>] from the CoS configured in the
egress-port logical-mac <port> flow in the other direction (with
[block <level-id/queue-id>] egress bridge port and ingress
egress-port pcs <port> [queue <queue-id> physical port). Doing so results
block <level-id/queue-id>] in the following error: A flow
from bridge port must not use a
egress-port pcs <port> [queue-map-profile
Queue Mapping or a Queue
<queue-map-profile-name> block <level-id/queue-id>]
Mapping profile.
egress-port pcs <port> [block <level-id/queue-id>]
• If working with PW, packets
egress-port svi <port> [queue <queue-id>]
forwarded from the SVI must be
egress-port svi <port> [queue-map-profile untagged or match all, and push
<queue-map-profile-name>] any necessary VLAN.
Associating a Layer-2 control l2cp profile <l2cp-profile-name> L2CP profile can be attached only
processing profile with the flow to flows with the following
classification types:
• VLAN/VLAN+P-bit
• Outer+Inner VLAN / Outer +P-bit
+ Inner VLAN
• P-bits
• VLAN+Non IP
• Untagged
For an explanation on how to
configure an L2CP profile, see
Layer-2 Control Protocol (L2CP)
Processing.

Defining marking actions for the mark all See the following table for the
flow such as overwriting the VLAN marking actions.
ID or inner VLAN ID or setting the
priority, or specifying MAC and IP
address swap
Specifying that the flow is a multi-cos-counters <cos-list> <cos-list> is the list of CoS values
multi-CoS flow with counters for for the flow; the list can be a range
the multiple CoSs such as 1..3 or a list of values such
as 2,4,5
You can assign either multiple CoS
counters or an envelope policer to
a multi-CoS flow; you cannot assign
both.
Configuring collection of pm-collection interval <seconds> Note: In addition to enabling PM

performance management statistics collection for the flow, it
statistics for the flow, that are must be enabled for the device.
presented via the RADview Refer to the Performance
Performance Management portal Management section in the
Monitoring and Diagnostics chapter
for details.
Associating regular flow with a policer profile <policer-profile-name> Note: You cannot assign a policer
non-envelope policer profile or policer aggregate <policer-aggregate-name> profile to a flow with a bridge port
policer aggregate as ingress port.
Associating multi-CoS flow with policer envelope <policer-profile-name> You can assign either an envelope
envelope policer policer or multiple CoS counters to
a multi-CoS flow; you cannot assign
both.
Measuring data rate and line rate rate-measure interval <seconds> Possible values: 10–300
of flow See Viewing Flow Data Rate and
Line Rate for details.
Defining flow to bridge port as reverse-direction block <queue-block-id> Note: This command is allowed only
bidirectional, if bridge is if the bridge is VLAN-aware and the
VLAN-aware egress port is a bridge port.
Assigning service name to flow for service-name <name> The flows that belong to the same
its subsequent discovery by service must be tagged in both
RADview directions.
Displaying measured flow data show rate See Viewing Flow Data Rate and
rate and line rate Line Rate for details.
Displaying flow status show status Fault propagation actions are
visible only for flows configured
with fault propagation and
activated fault propagation license.
See Viewing Flow Status.

Specifying whether transmitted statistics-count-oam Enter no statistics-count-oam if

and received OAM packets are you do not want to include
included in the statistics counters transmitted and received OAM
for Rx and Tx statistics packets in the statistics; this
applies to the following OAM
packets:
AIS
CCM’s
DMM/DMR’s
LMM/LMR’s
LBM/LBR’s
LTM/LTR’s
Port status TLV
Adding VLAN ID with p-bit set to vlan-tag push vlan <sp-vlan> p-bit fixed <fixed-p-bit>
specific value, and optionally [inner-vlan <inner-sp-vlan>
adding inner VLAN ID with p-bit p-bit fixed <inner-fixed-p-bit>]
set to specific value
specific value, and optionally [inner-vlan <inner-sp-vlan>
adding inner VLAN ID with p-bit p-bit profile <inner-marking-profile-name>]
set via marking profile
specific value, and optionally [inner-vlan <inner-sp-vlan> p-bit copy]
adding inner VLAN ID with p-bit
set by copying from the incoming
frame
Adding VLAN ID with p-bit set via vlan-tag push vlan <sp-vlan>
marking profile, and optionally p-bit profile <marking-profile-name>
adding inner VLAN ID with p-bit [inner-vlan <inner-sp-vlan>
set to specific value p-bit fixed <inner-fixed-p-bit>]
adding inner VLAN ID with p-bit [inner-vlan <inner-sp-vlan>
set via marking profile p-bit profile <inner-marking-profile-name>]
adding inner VLAN ID with p-bit [inner-vlan <inner-sp-vlan> p-bit copy]
set by copying from the incoming
frame
Adding VLAN ID with p-bit set by vlan-tag push vlan <sp-vlan> p-bit copy
copying from the incoming frame, [inner-vlan <inner-sp-vlan>
and optionally adding inner VLAN p-bit fixed <inner-fixed-p-bit>]
ID with p-bit set to specific value:

copying from the incoming frame, [inner-vlan <inner-sp-vlan>
and optionally adding inner VLAN p-bit profile <inner-marking-profile-name>]
ID with p-bit set via marking
profile
copying from the incoming frame, [inner-vlan <inner-sp-vlan> p-bit copy]
and optionally adding inner VLAN
ID with p-bit set by copying from
the incoming frame
Removing VLAN ID, and optionally vlan-tag pop vlan [inner-vlan]

removing inner VLAN ID
Removing pushing of inner VLAN no vlan-tag [push inner-vlan]
Displaying the flow statistics show statistics running See Viewing Flow Statistics.
Administratively enabling the flow no shutdown • You can activate a flow only if it
is associated with at least a
classifier profile, ingress port,
and egress port.
• A flow from a bridge port to a
physical port cannot be
activated if another flow from
the same bridge port, in the
same VPN, exits to a different
egress cluster (physical port and
queue block). This applies to
unidirectional flows and to the
reverse direction of bidirectional
flows.
• Type shutdown to disable the
flow.
The following marking actions can be performed in the mark level, at the
config>flows>flow(<flow-name>)>mark# prompt.
Specifying permanent flow ip swap

loopback with IP address swap
Specifying permanent flow mac swap

loopback with MAC address swap


Overwriting p-bit according to marking-profile <marking-profile-name> If a marking profile is used, it must
marking profile be compatible with the classification
criteria of the flow, e.g. if the flow
classification is according to DSCP
then the marking classification
should not be according to p-bit.
If the flow is multi-CoS, the marking
profile must be of type CoS to p-bit.
If a color-aware marking profile is
applied for the outer VLAN of a flow,
then if marking is applied to the
inner VLAN, either the same
color-aware marking profile must be
used for the inner VLAN, or a
non-color-aware marking profile
must be used for the inner VLAN.
Typing no marking-profile or
no inner-marking-profile removes
the overwriting of marking profile
or inner marking profile
respectively.
Overwriting inner p-bit according inner-marking-profile <inner-marking-profile-name> See comments for marking-profile.
to marking profile
Overwriting p-bit with a new value p-bit <p-bit-value> Typing no p-bit removes the
overwriting of p-bit.
Overwriting inner p-bit with a new inner-p-bit <inner-p-bit-value> Typing no inner-p-bit removes the
value overwriting of inner p-bit.
Overwriting VLAN ID with a new vlan <vlan-value> Typing no vlan removes the
value overwriting of VLAN ID.
Overwriting inner VLAN ID with a inner-vlan <inner-vlan-value> Typing no inner-vlan removes the
new value overwriting of inner VLAN ID.
Exiting the marking context and exit

returning to the flow context
Configuring Port Classification

Port classification can be configured for the following ports:
• Ethernet ports
• Redundancy LAG ports (the port classifier rules must be configured for the
anchor port)
• Logical MAC
• PCS port

 To configure port classification for Ethernet/LAG/logical MAC/PCS port:

1. Navigate to configure port ethernet [<slot>/]<port> classifier,
configure port lag <port> classifier, configure port logical-mac <port>
classifier, or configure port pcs <port> classifier, respectively.
The prompt config>port>eth([<slot>/]<port>)>classifier#,
config>port>lag(<port>)>classifier#,
config>port>log-mac(<port>)>classifier#, or
config>port>pcs(<port>)>classifier# is displayed.
Note In the case of LAG port, the port classifier rules must be configured for the
anchor port.
Adding comment rule comment <description> description – text description

[sequence <sequence-number>] sequence-number – sequence
number for comment
Removing rule delete <sequence-number>
Adding drop rule drop [dst-mac <dst-mac-address>] Up to five criteria can be

[src-mac <src-mac-address>] specified; they must be in the
[ether-type <ether-type>] [vlan <vlan>] same order in which they
[p-bit <p-bit>] [dei {0 | 1}] appear in the command syntax
[inner-ether-type <inner-ether-type>]
[inner-vlan <inner-vlan>]
[inner-p-bit <inner-p-bit>] [ip-dscp <ip-dscp>]
[ip-precedence <ip-precedence>] [tos <tos>]
[protocol <protocol>] [src-ip <src-ip-address>]
[dst-ip <dst-ip-address>]
[tcp-src-port <tcp-src-port>]
[tcp-dst-port <tcp-dst-port>]
[udp-src-port udp-src-port>]
[udp-dst-port <udp-dst-port>] [any]
[sequence <sequence-number>]

Adding match rule match [dst-mac <dst-mac-address>] • Up to five criteria can be

[src-mac <src-mac-address>] specified; they must be in
[ether-type <ether-type>] [vlan <vlan>] the same order in which
[p-bit <p-bit>] [dei {0 | 1}] they appear in the
[inner-ether-type <inner-ether-type>] command syntax
[inner-vlan <inner-vlan>] • The flow specified by
[inner-p-bit <inner-p-bit>] [ip-dscp <ip-dscp>] to-flow <flow-name> has
[ip-precedence <ip-precedence>] [tos <tos>] to be defined as a flow
[protocol <protocol>] [src-ip <src-ip-address>] with parameter
[dst-ip <dst-ip-address>] port-classifier.
[tcp-src-port <tcp-src-port>]
• CoS is optional; it can be
[tcp-dst-port <tcp-dst-port>]
specified via to-cos-fixed
[udp-src-port udp-src-port>]
as a fixed value or via
[udp-dst-port <udp-dst-port>] [any]
to-cos-profile as a profile.
[sequence <sequence-number>]
to-flow <flow-name>
{[to-cos-fixed <fixed-cos>] |
[to-cos-profile <profile-cos>]}
Reseqencing the rules resequence [<step>] If you need to add a rule

between existing rules with
consecutive sequence
numbers, use this command to
add space between the rule
sequence numbers.
The <step> parameter
specifies the interspacing
value. For example, if you
apply resequence 30 to a port
classification that contains
rules 1, 2, and 3, the rule
sequence numbers change to
30, 60, and 90.
Displaying port classifier show status

status
Examples
Classifier Profiles
 To create classifier profile with criteria VLAN 100 to VLAN 150:

exit all
configure flows classifier-profile v100_150 match-any
match vlan 100..150
exit all
 To create classifier profile with criteria VLAN 20 and inner VLAN 30:
exit all
configure flows classifier-profile v20_inner_30 match-any

match vlan 20 inner-vlan 30

exit all
 To create classifier profile that matches all criteria:

exit all
configure flows classifier-profile all match-any
match all
exit all
Traffic Flows
This section provides an example of configuring the following flows in ETX220A:
• Outgoing traffic from port ETH 1/3 to port ETH 4/1:
 Accept only traffic tagged with VLAN 10.
 Add VLAN 100 with p-bit 5 (this causes VLAN 100 to be the outer VLAN
and VLAN 10 to be the inner VLAN).
• Incoming traffic from port ETH 4/1 to port ETH 1/3:
 Accept only traffic tagged with VLAN 100 and inner VLAN 10.
 Remove the outer VLAN (VLAN 100).
 To configure the flows:

#*******Configure v10 classifier profile for outgoing flow
exit all
configure flows
match vlan 10
exit
#*******Configure outgoing flow with v10 classifier profile,

#********* with ingress at ETH 1/3, egress at ETH 4/1,
#********* and pushing VLAN 100 with p-bit 5
flow f10_out
classifier v10
service-name v10
pm-collection interval 900
no shutdown
exit
#*******Configure v100_inner_v10 classifier profile for incoming flow

classifier-profile v100_inner_v10 match-any
match vlan 100 inner-vlan 10
exit
#*******Configure flow with v100_inner_v10 classifier profile,

#********* ingress at ETH 4/1, egress at ETH 1/3, and popping the outer VLAN
flow f100_in
classifier v100_inner_v10


vlan-tag pop vlan
service-name v10
no shutdown
exit all
ETP Flows
This section provides an example of configuring the following flows in ETX203AX
or ETX205A:
• Flow sub1:
 Ingress = ethernet 3
 Egress = etp ETP1 subscriber 1, CoS mapping profile my-p-bit (see CoS
Mapping Profiles for details on CoS mapping profiles)
• Flow trans1:
 Ingress = etp ETP1 transport 1
 Egress = ethernet 1, queue 0, block 0/1
 To configure ETP flows:

#**************Configure flow sub1
exit all
configure flows
flow sub1
egress-port etp ETP1 subscriber 1 cos-mapping my-p-bit
exit
#**************Configure flow trans1

flow trans1
ingress-port etp ETP1 transport 1
exit all
Unidirectional Hub
This section provides an example of configuring a unidirectional hub with five
flows in ETX220A:
• Ingress port = ETH 4/1
• Egress ports:
 ETH 1/3, queue 0, block 0/1
• Criteria = VLAN 100
• Policer profile bandwidth limits = CIR 10000, CBS 5000, EIR 0, EBS 0

 To configure the hub:

#**************** Configure policer profile and aggregate for UDH
exit all
configure qos
policer-profile udh_pol bandwidth cir 10000 cbs 5000 eir 0 ebs 0
policer-aggregate udh_agg policer profile udh_pol
exit all
#*************** Configure classifier profile for UDH

configure flows
classifier-profile udh_class match-any match vlan 100
exit
#*************** Configure flow udh1

flow udh1
classifier udh_class
policer aggregate udh_agg
no shutdown
exit

flow udh2
no shutdown
exit

flow udh3
no shutdown
exit

flow udh4
ingress-port ethernet ethernet 4/1
egress-port e ethernet 1/5 queue 1 block 0/2
no shutdown
exit

flow udh5


no shutdown
exit all
Multi-CoS Flow
This section provides an example of configuring multi-CoS flows per MEF 10.3 in
ETX220A:
• Flow with multi-CoS counters:
 Ingress port = ETH 4/1
 Egress port: ETH 1/1
 Criteria = VLAN 10
• Flow with envelope policer:
 Ingress port = ETH 1/1
 Egress port: ETH 4/1
 Criteria = VLAN 10
• Envelope profile bandwidth limits:
 CIR 1000; maximum CIR 10,000; CBS 2000; EIR 0; EBS 0; maximum EIR 0
 To configure the multi-CoS flows:

#**************** Configure CoS mapping profile
exit all
configure
qos
cos-map-profile cos-pbit classification p-bit
untagged-map to-cos 0
exit
#**************** Configure envelope profile

envelope-profile env1
cf-policy uncoupled-BW-sharing
cos 0 bandwidth cir 1000 cir-max 10000 cbs 2000 eir 0 eir-max 0 ebs 0
cos 1 bandwidth cir 2000 cir-max 10000 cbs 2000 eir 0 ebs 0
exit
exit
#*************** Configure classifier profile

flows
exit
#*************** Configure multi-cos-counters flow

flow multi2
classifier v10
cos-mapping profile cos-pbit
no policer
multi-cos-counters 0..3
egress-port ethernet 1/1 queue-map-profile q-map-for-cos block 0/1
no shutdown
exit
#*************** Configure flow with envelope policer

flow env2
classifier v10
policer envelope env1
cos-mapping profile cos-pbit
egress-port ethernet 4/1 queue-map-profile q-map-for-cos block 0/1
no shutdown
exit all
save
Testing Flows and Flow Diagnostics Loopback

MAC swap loopback tests support two different use cases:
• Use Case 1: Application layer loopback – MAC swap loopback of traffic with
certain characteristics (e.g MAC address, VLAN+MAC, etc.) by configuring a
dedicated flow for this purpose
• Use Case 2: Flow diagnostics loopback – performs MAC swap loopback over
an existing configured flow
Note MAC swap is not performed if the flow is part of a unidirectional hub.
Use Case 1 – Application Layer Loopback

In this use case, an application layer loopback test is applied over a dedicated
configured flow with a test mac-swap attribute. In this case, the egress port must
be configured to be equal to the ingress port.
You can run application layer loopbacks on a flow, with exchange of source and
destination MAC addresses or IP addresses of incoming packets. This applies to all
the data associated with the flow.
Note Regardless of whether the mac-swap or ip-swap option is specified, if there is an

IP header in the frames, then both MAC and IP addresses are swapped; otherwise
only the MAC address is swapped.
The following procedure shows how to run an application layer loopback test
using a flow.
 To run an application layer flow loopback test:

1. Navigate to configure flows flow <flow-name> to select the above flow.
The config>flows>flow(<flow-name>)# prompt is displayed.

2. Create a flow with the ingress port equal to the egress port with a test mac-
swap attribute.
test [{mac-swap | ip-swap}] [duration <seconds>] [ttl-force <ttl>]
The flow is activated upon flow ‘no-shutdown’, and the TEST LED is
turned on. The test runs for the duration specified. If 0 is specified for
the duration, the test runs until it is stopped manually, and the loop
remains after reset (including MAC/IP swap).
 To end the test:

• Delete the flow
OR
1. Navigate to configure flows flow <flow-name> to select the flow being
tested.
2. Enter:
no test
Example
Note This example uses the classifier profile ‘da mac aa’, created in the classifier
profile examples.
 To configure the mac-swap loopback:

exit all
configure flows flow Tflow
classifier da_mac_aa
test mac-swap duration 50
no shutdown
exit all
ETH1
Figure 8-10. Application Layer Loopback Test on Flow with Three Attributes
 To display flow test status:

ETX-2>config>flows>flow(Tflow)# show test
Test : MAC Swap Duration (Sec) : 50 Remain (sec) : 40
No TTL
Method 2 – Flow Diagnostics Loopback

This method, supported over a point to point service, performs the loopback test
using only one flow attribute – test mac-swap. No other changes are required to
the flow; there is no need to configure egress port = ingress port, or to shut
down the flow and associated MEPs. The loop command is cleared after reset.

 To run flow diagnostic loopback:

1. Navigate to configure flows flow <flow-name> to select an existing flow.
2. Enter:
test [{mac-swap|] [duration <seconds>]
The TEST LED is turned on. The test runs for the duration specified. If 0 is
specified for the duration, the test runs until it is stopped manually.
 To end the test:

1. Navigate to configure flows flow <flow-name> to select the flow being
tested.
2. Enter:
no test
Example – Flow Diagnostics Loop

In the following example, two flows of an EVC are configured. The diagnostics
loop is performed over evc1_in the flow (back to the network).
Note This example uses the classifier profile ‘all’, created in the classifier profile
examples.
 To configure the mac-swap loopback:

exit all
ETX-2x configure flows flow (evc1_in)# test mac-swap duration
50
 To display flow test status:

ETX-2>config>flows>flow(evc1_in)# show test
Test : MAC Swap Duration (Sec) : 50 Remain (sec) : 40
No TTL
ETH 3 ETH 1
Loop performed on this flow (evc1_in)
Figure 8-11. Application Layer Loopback Test on Flow with a Single Attribute
Viewing Flow Statistics

You can display the number of forwarded and discarded packets and bytes for a
flow.

The statistics do not include transmitted and received OAM packets if no

statistics-count-oam was specified for the flow. The counters are displayed per
CoS in the case of multi-CoS flow.
ETP subscriber flow statistics include:
• Red dropped counters at policer, as the logical flow extends to the ETP and
not to the Egress port.
• Green and yellow dropped counters, reflecting the statistic of the flow up to
the Egress port.
Note See Configuring Policer Aggregate Parameters for information on displaying

statistics for flows associated with policer aggregates.
 To display the statistics for a flow:

• At the relevant flow context (config>flows>flow(<flow-id>)), enter:
show statistics running
Flow statistics are displayed.
 To clear the statistics for a flow:

• At the relevant flow context (config>flows>flow(<flow-id>)), enter:
clear-statistics
The statistics for the flow are cleared.
Examples
ETP Subscriber Flow Statistics

This example displays statistics of ETP subscriber flow sub1 (see configuration in
the ETP Flows example above).
 To display flow statistics (ETP):

ETX-2# configure flows flow sub1
ETX-2>config>flows>flow(sub1)# show statistics running
Rate Sampling Window
-----------------------------------------------------------------------------
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 20000
Bytes : 20000000
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0

Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
pps L1 (bps) L2(bps)
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Yellow(Rate) : 0 0 0
Red(Rate) : 0 0 0
Yellow/Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
L1 Min. L2 Min L1 Max L2 Max.
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
Multi-CoS Flow Statistics

This example displays statistics of multi-cos flow multi2 (see configuration in
Multi-CoS Flow example).
 To display multi-CoS flow statistics:

ETX-2# configure flows flow multi2
ETX-2>config>flows>flow(multi2)# show statistics running
-----------------------------------------------------------------------------
Cos Number : 2
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0

Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 0 0
Drop Bit Rate [bps]: 0 0 0 0
Cos Number : 3
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes

Total : 197941 197941000

Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
Cos Number : 5
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 0 0

Drop Bit Rate [bps]: 0 0 0 0
Viewing Flow Status

You can display the operational status and reverse operational status of a flow,
as well as the service name for flows configured with a service. Fault propagation
actions are visible only for flows configured with fault propagation and fault
propagation license activated.
Example
 To display flow status:

ETX-2# configure flows flow a1
ETX-2>config>flows>flow(a1)# show status
Reverse Operational Status : Up
Service Name :
Fault propagation actions:

Policer changed : ‘policer profile’
Shaper changed
Status Details
-----------------------------------------------------------------------------
: Ingress Port Oper Status: Down
Viewing Flow Data Rate and Line Rate

You can measure the data rate and line rate at which flows transmit and receive,
for a configurable time interval of 10–300 seconds. After you enter the command
to measure the rates, ETX-2 automatically displays the results when the specified
time interval ends. The data rate is calculated by dividing the number of total
bytes (not including line overhead) by the time interval. The line rate is calculated
by dividing (number of total bytes + (number of packets x 20 bytes of line
overhead)) by the time interval.
 To start data rate and line rate measurements for flow:

• At the prompt config>flows>flow(<name>)#, enter:
rate-measure interval <seconds>
The rate measurement starts. You can use show rate to monitor how
much of the time interval has elapsed. The result is automatically
displayed, without the need to enter show rate, after the specified time
interval ends.
Example
 To display data rate and line rate for flow:
ETX-2# configure flows flow f10_out
ETX-2>config>flows>flow(f10_out)# rate-measure interval 30

ETX-2>config>flows>flow(f10_out)# show rate

Name : f10_out
Time Left to Elapse (Sec) : 18
ETX-2>config>flows>flow(f10_out)#
Name : f10_out
Status : Passed
Start Time : 2014-11-13 12:24:36 UTC +00:00
Duration (Sec) : 30
Cos : 255
L1 L2
Rx Rate (bps) : 1000 950
Tx Rate (bps) : 1500 1400
Green Drop (bps) : 100 95
Yellow Drop (bps) : 100 95
Red Drop (bps) : 100 90
8.3 Layer-2 Control Protocol (L2CP) Processing

ETX-2 tunnels, discards, or peers (traps to host for protocol processing) L2CP
packets. These actions are defined by Layer-2 Control Protocol (L2CP) profiles,
which also provide different L2CP addresses. The L2CP profiles are attached to
ports and flows.
Applicable Products
Standards
IEEE 802.3
Benefits
ETX-2 offers high flexibility in handling L2CP packets. According to application
requirements, these packets can be tunneled, tunneled with MAC swap,
discarded, or trapped to the host CPU.
ETX-2 supports L2CP profiles to define the handling of Layer-2 Control Protocol
traffic. You can create and configure L2CP profiles to pass through Layer-2
control frames (including other vendors’ L2CP frames) across the network, peer
(trap to host for protocol processing) supported protocols, or discard L2CP
frames. You can also configure L2CP profiles to perform protocol tunneling with
MAC address swap, and discard Loopback packets (Ethertype 0x9000).
ETX-2 Layer-2 Control Protocol (L2CP) Processing 8-57

You can configure L2CP profiles (as described below), and then assign relevant
L2CP profiles to ports (Ethernet, PCS, or Logical MAC; refer to the relevant
configuration section in the Cards and Ports chapter) and/or to flows (see
Configuring Flows). You can also display the L2CP port statistics for a port
associated with an L2CP profile that is configured with tunneling and MAC swap
(refer to Displaying Layer-2 Control Processing Statistics in the Cards and Ports
chapter).
ETX-2 handles Layer-2 control protocol traffic on a per-port and per-flow basis.
L2CP traffic (both tagged and untagged L2CP frames) is processed using a two-
stage mechanism comprising per-port or per-flow profiles (set of rules for traffic
handling). If no per-flow L2CP profile is configured, a per-port-level profile is
used.
If no default action is configured for an address or protocol, this traffic is
tunneled.
Note An L2CP profile that is attached to a port or flow can be modified or replaced; it
cannot be deleted.
Layer-2 Protocol Tunneling (L2PT) Over Bridge

ETX-2 supports Layer-2 Protocol Tunneling (L2PT) – L2CP tunneling with MAC
swap, which means that L2CP packets can be forwarded over networks that are
not transparent to L2CP.
L2PT is supported at the port level and applies for PTP flows, as well as for
bridged traffic (refer to Configuring Ethernet Port Parameters in Cards and Ports
chapter).
• ETX-2 supports multiple network ports with L2PT functionality for both PTP
and Bridge applications.
• Any port configured as NNI is L2PT Network, by default.
• Any Ethernet user port can be configured to be L2PT Network (default ‘no’).
• Any port assigned with an L2CP profile with MAC swap, including port 1, can
function as an L2PT user port.
You can bind an L2CP profile configured with L2CP MAC swap to a user port; it
cannot be bound to a flow. A port assigned with an L2PT profile expects “native”
L2CP frames. MAC swap is performed toward the relevant network port or user
port that is configured for use as L2PT network ports.
L2PT functionality in ETX-2 is as follows:
1. User to L2PT network port: IO port ingress traffic identified with the
configured protocols is MAC swapped to a user preconfigured multicast
address (e.g 01-70-00-00-00-00) and proceeds with the original traffic path
as set by the classification (tunnel). The actual functionality for these
protocols is a tunnel with MAC swap.
2. L2PT network port to user: IO port ingress traffic identified with the
preconfigured L2PT multicast MAC address (e.g 01-70-00-00-00-00) is MAC
swapped to the original protocol MAC. Traffic then proceeds with the original
traffic path as set by classification to the egress port.
8-58 Layer-2 Control Protocol (L2CP) Processing ETX-2

Notes • An L2PT network port is an NNI port or any other user port configured as an
L2PT network port (for tunnel with MAC swap).
• A single MAC address (per device) is supported for L2CP MAC swap. The last
L2PT MAC bound is the MAC used.
MAC SWAP L2PT

User
Network
Port
SWAP Back Port
Figure 8-12. Supported Topology
UNI
Port 3
Bridge
UNI L2PT Network Port
Port 1 Port 2
Figure 8-13. Bridge Flows and Ports
Factory Defaults
By default, a “tunnel all” profile is attached to every port. However, no default
L2CP profile is attached to a newly created flow, meaning that the flow traffic
behaves, by default, according to the port profile.
When you create a new L2CP profile, it has the configuration of
L2cpDefaultProfile, the ETX-2-provided default L2CP profile. It is configured as
follows:
• For MAC hex byte 0x00 through 0x2f, action = tunnel
• Default action = tunnel
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.
3. Configure the L2CP profile as needed (see 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-profile <l2cp-profile-name> to select the
L2CP profile to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
Specifying the default action for default {discard | tunnel}

undefined control protocols

Specifying the L2CP action for MAC mac <mac-addr-last-byte-value-list><mac-addr> mac-addr –can be either of the
addresses (discard, tunnel, or peer) {discard | tunnel | peer} following:
• Long MAC address, i.e. full
valid MAC adress [xx-xx-xx-
xx-xx-xx]
For example:
01-80-c2-00-00-02
Possible values:
01-80-c2-00-00-xx, where
xx= 0H-10H, 20H-2FH;
01-00-0c-cc-cc-cc
01-00-0c-cc-cc-cd
• Short MAC address, i.e. last
byte of the control protocol
MAC address
[0x00..0x10,0x20..0x2F]
For example: 0x02 is the
short MAC address of
01-80-c2-00-00-02.
Possible values: 0H-10H,
20H-2FH
discard – L2CP frames are
discarded.
tunnel – L2CP frames are
forwarded across the network
as ordinary data.
peer – ETX-2 peers with the
user equipment to run the
protocol. L2CP frames are
forwarded to the ETX-2 CPU.
Unidentified L2CP frames are
forwarded across the network
as ordinary data.
Notes:
• Peer action cannot be used
with the MAC addresses 01-
00-0c-cc-cc-cc and 01-00-
0c-cc-cc-cd.
• ETX-2 supports a single MAC
address per chassis. This
address is used by all L2PT
profiles and protocols that
user asks to tunnel. If you
configure different MACs in
different ports, the last MAC
you configured is the one
used.
Typing no mac
<mac-addr-last-byte-value-list>
<mac-addr> removes the


action for the specified MAC
address.
Defining a Loopback protocol for protocol loopback discard Typing no protocol loopback
discarding removes the action for the
Loopback protocol.
Defining a protocol for tunneling and protocol { lacp | stp | vtp | cdp | lldp | pvstp| pagp | udld | protocol – list of L2CP protocols
specifying MAC swap (for L2PT dtp | lamp | link-oam | e-lmi | 802.1x | gvrp | gmrp | in which tunneling, and
functionality) if desired mmrp | mvrp-customer-bridge | mvrp-provider-bridge | optionally MAC swap, can be
msrp | mirp } tunnel [mac-change [<mac-address>]] performed.
mac-address – the MAC address
to be used as an alternative to
the original MAC. This is an
optional parameter; its default
value is 01-00-0C-CD-CD-D0.
The last mac-address
configured is the MAC used.
Typing no protocol { lacp | stp |
vtp | cdp | lldp | pvstp| pvstp |
pagp | udld | dtp } removes the
action for the specified
protocols.
Notes:
• Supported over a user port
only.
• <mac-address> must be a
valid multicast address. Must
have a 1 value in the least-
significant bit of the first
octet (for example, 01-03-
05)
• You must use the same
<mac-address> for all
tunneled protocols.
• You can configure either
gmrp or gvrp in a single
profile; not both.
• You can configure either
mvrp-customer-bridge or
mvrp-provider-bridge in a
single profile; not both.
• For ETX203AM, ETX203AX,
and ETX205A, if the L2CP
profile is associated with a
flow, the MAC swap
functions only if the flow
uses network port 1, and
not network port 2.

Examples
 To add L2CP profile named layer2ctrl1 with discard action for hex byte 0x01 and
0x03 (short MAC format):
exit all
ETX-2#configure port
l2cp-profile layer2ctrl1
ETX-2>config>port>l2cp-profile (layer2ctrl1)#mac 0x01 discard
mac 0x03 discard
exit all
 To add L2CP profile named layer2ctrl2 with tunnel action for long MAC addresses
01-80-c2-00-00-00 and 01-80-c2-00-00-01 (long MAC format):
exit all
ETX-2#configure port
l2cp-profile layer2ctrl2
ETX-2>config>port>l2cp-profile(layer2ctrl2)#
mac 01-80-c2-00-00-00 tunnel
mac 01-80-c2-00-00-01 tunnel
exit all
 To add L2CP profile 1 that uses LACP protocol for tunneling with L2CP MAC swap:
ETX-2#configure port l2cp-profile 1
ETX-2>config>port>l2cp-profile(1)#
protocol lacp tunnel mac-change 01-23-45-67-89-DD
exit all
 To display the layer2ctrl1 L2CP profile:
ETX-2#configure port l2cp-profile layer2ctrl1
ETX-2>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 0x10 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
default tunnel
mac "01-80-c2-00-00-00" tunnel
mac "01-80-c2-00-00-01" tunnel
mac "01-80-c2-00-00-02" tunnel
mac "01-80-c2-00-00-03" tunnel
mac "01-80-c2-00-00-04" tunnel
mac "01-80-c2-00-00-05" discard
mac "01-80-c2-00-00-06" tunnel
mac "01-80-c2-00-00-07" tunnel
mac "01-80-c2-00-00-08" tunnel
mac "01-80-c2-00-00-09" tunnel
mac "01-80-c2-00-00-0a" tunnel
mac "01-80-c2-00-00-0b" tunnel
mac "01-80-c2-00-00-0c" tunnel
mac "01-80-c2-00-00-0d" tunnel
mac "01-80-c2-00-00-0e" tunnel
mac "01-80-c2-00-00-0f" tunnel
mac "01-80-c2-00-00-10" tunnel
mac "01-80-c2-00-00-20" tunnel
mac "01-80-c2-00-00-21" tunnel
mac "01-80-c2-00-00-22" discard
mac "01-80-c2-00-00-23" tunnel
mac "01-80-c2-00-00-24" tunnel
mac "01-80-c2-00-00-25" tunnel
mac "01-80-c2-00-00-26" tunnel
mac "01-80-c2-00-00-27" tunnel
mac "01-80-c2-00-00-28" tunnel
mac "01-80-c2-00-00-29" tunnel
mac "01-80-c2-00-00-2a" tunnel
mac "01-80-c2-00-00-2b" tunnel
mac "01-80-c2-00-00-2c" tunnel
mac "01-80-c2-00-00-2d" tunnel
mac "01-80-c2-00-00-2e" tunnel
mac "01-80-c2-00-00-2f" tunnel
mac "01-00-0c-cc-cc-cc" tunnel
mac "01-00-0c-cc-cc-cd" discard
default tunnel
ETX-2#configure port l2cp-profile layer2ctrl1
ETX-2>config>port>l2cp-profile(layer2ctrl1)# info
mac "01-80-c2-00-00-05" discard
mac "01-80-c2-00-00-22" discard
mac "01-00-0c-cc-cc-cd" discard
Note
The info detail command displays all actions (including the default action (in
above example, tunnel). The info command only displays non-default actions.

 To configure L2PT network on a user port:

ETX203AX# config>port>eth(3)# l2pt-network
 To delete L2CP profile layer2ctrl1:

no l2cp-profile layer2ctrl1
The following table lists the messages generated by ETX-2 when a configuration
error is detected.
Message Description
Cannot add MAC address: Max number of Cannot specify an L2CP processing action for a MAC address
MAC addresses has been reached because the maximum number of addresses has been reached.
Illegal L2CP processing action for this The L2CP processing action selected for the current MAC
MAC address type address type is not valid.
Illegal MAC address for peer action The MAC address selected for the peer processing action is not
valid. The address must be 01-80-C2-00-00-02.
Invalid L2PT protocol An invalid protocol was used to configure the L2CP MAC swap.
L2CP MAC swap available only on IO The L2CP MAC swap is not supported for ports that are not IO
ports ports.
L2CP MAC swap not available on flows L2CP MAC swap can only be configured for ports.
L2CP profile creation failure: Max number The L2CP profile cannot be added because the maximum number
of L2CP profiles has been reached of L2CP profiles has been reached.
L2CP profile deletion/modification The L2CP profile cannot be deleted or modified because it is
failure: L2CP profile is in use currently attached to a port or a flow.
L2CP profile does not exist Cannot bind an L2CP profile that has not yet been created.
Only tunnel supported MAC change An invalid action was used to configure the L2CP MAC swap.
Peer action is not allowed for port- An L2CP profile bound to a port cannot perform a peer action.
bound L2CP profile
Viewing L2CP Statistics

 To display the L2CP statistics for an Ethernet port:
• At the prompt config>port>eth(1/1)#, enter show l2cp-statistics
L2CP statistics are relevant to the tunnel with the MAC swap function
only and are displayed for the specified port, showing the number of
encapsulated and decapsulated packets for each protocol.
ETX203AX>config>port>eth(1)# show l2cp-statistics
Protocol Encapsulated Decapsulated
---------------------------------------------------------------

LACP 0 0
STP 0 0
CDP 0 0
VTP 0 0
LLDP 0 0
PVSTP 0 0
PAGP 0 0
UDLD 0 0
DTP 0 0
LAMP 0 0
Link OAM 0 0
ELMI 0 0
802.1x 0 0
GVRP 0 0
GMRP 0 0
MMRP 0 0
MVRP Customer Bridge 0 0
MVRP Provider Bridge 0 0
MSRP 0 0
MIRP 0 0
8.4 Link Layer Discovery Protocol (LLDP)

LLDP is a standard layer-2 protocol that allows Ethernet network devices to
advertise information about themselves, and receive information from other
Ethernet network devices. The devices store this information in local MIB
databases accessible via SNMP; therefore the information can be accessed by a
network management system.
Applicable Products
This feature is applicable to all ETX-2 products, with the following condition:
Standards
IEEE 802.1AB-2009
IEEE 802.3az-2010
Benefits
Automated discovery of devices simplifies management and network
maintenance, and reduces general setup costs of new equipment.
LLDP is a neighbor discovery protocol that enables network devices to advertise
information to peer devices on the same physical LAN and store information
about the network. LLDP is supported for all Ethernet ports, including the
8-66 Link Layer Discovery Protocol (LLDP) ETX-2

management port and Ethernet ports that are bound to LAG. LLDP information is
exchanged by means of LLDP packets.
Note LLDP runs on physical links and is configured on each individual physical port; it
neither runs nor is configured over the LAG logical layer.
LLDP Bridge Types

LLDP works according to the following bridge types:
Nearest bridge The propagation of LLDP packets is limited to a single

physical link, and is stopped by any type of bridge.
Nearest customer The propagation of LLDP packets is limited by customer

bridge bridges.
Nearest non-TPMR The propagation of LLDP packets is limited by non-TPMR

bridge bridges. Typically this mode is used in provider bridged
networks.
TPMR (Two-port MAC Relay) indicates a bridge that has only two
externally-accessible bridge ports, and supports a subset of the regular functions
of a MAC bridge. A TPMR bridge is transparent to all frame-based
media-independent protocols except for packets with destinations that terminate
at the bridge, or packets with destinations that are reserved MAC addresses that
are not defined for forwarding by the relay function of the TPMR bridge.
LLDP Packets
LLDP packets are sent periodically between ETX-2 and neighboring devices, in
order to obtain neighbor information. The information from the LLDP packets is
stored for a period of time, determined by the time-to-live (TTL) value in the
received packet. When the TTL expires, the LLDP information is discarded.
LLDP packets contain the following information:
Destination MAC Set to 01-80-C2-00-00-00 (nearest customer bridge),

address 01-80-C2-00-00-03 (nearest non-TPMR bridge) or
01-80-C2-00-00-0E (nearest bridge), depending on
configuration
Source MAC Set to port MAC address

address
EtherType Set to 0x88CC
LLDP Protocol Contains a variable number of information units called

Data Unit TLVs: mandatory TLVs, optional TLVs, and an EndOfLLDPDU
(LLDPDU) TLV. LLDPDUs are always sent untagged. TLVs consist of
basic management TLVs and organizationally specific TLVs.
The organizationally specific TLVs are differentiated by
IEEE 802.1, IEEE 802.3, and more.
ETX-2 Link Layer Discovery Protocol (LLDP) 8-67

Table 8-8. Basic Management TLVs
TLV Name Description TLV Appears in

LLDPDU
Chassis ID Management MAC address Mandatory
Port ID Interface name per RFC 2863 Mandatory
Time To Live Time in seconds that specifies the validity Mandatory

period of the information
Port Description ifDescr per RFC 2863, which is port name Optional
System Name Device name as configured by CLI (per Optional

RFC 3418 )
System Description sysDescr per RFC 3418 includes: Optional

• Device name
• HW version
• SW version
System Capabilities Includes indications for the following: Optional

• MAC bridge
• Router
• C-VLAN component of VLAN bridge
• S-VLAN component of VLAN bridge
• Two-port MAC relay (TPMR)
Management Address Management IP address Optional
End Of LLDPDU N/A; indicates end of LLDPDU Mandatory
Table 8-9. Organization-Specific IEEE 802.1 TLVs
TLV Name Description
Protocol Identity Protocols configured on the port. The following protocols

are supported:
• LLDP
• EFM if configured
• CFM
• LAG-LACP if the port is in a LAG group
• ESMC if tx-ssm is enabled for the port)
• ERP-v2 if G.8032 ring is configured on the port
Table 8-10. Organization-Specific IEEE 802.3 TLVs
MAC/PHY Configuration/Status • Autonegotiation support/status

• Autonegotiation advertised capability
• MAU type (data rate and duplex mode)

Maximum Frame Size Egress MTU
Factory Defaults
By default, no LLDP parameters are configured for ports. The system LLDP
parameters have the default values shown in the following table.
hold-multiplier 4
shutdown shutdown LLDP is administratively enabled for

all relevant interfaces.
tx-interval 30 Value is in seconds.
Configuring LLDP
LLDP parameters are configured at the following levels:
• Global LLDP parameters that apply to the entire device are configured at the
system level.
• Port LLDP parameters are configured at the Ethernet port level, to specify
which TLVs to send for the port.
Note In order for LLDP to function properly for the port, an L2CP profile must be
associated with it that specifies peer action for MAC address 01-80-C2-00-00-00,
01-80-C2-00-00-03 or 01-80-C2-00-00-0E, depending on the LLDPDUs
destination addresses configured.
System Parameters
This section explains how to configure global parameters such as bridge type, as
well as enable or disable LLDP for the device.
 To configure LLDP system parameters:
1. Navigate to configure system lldp.
The config>system>lldp# prompt is displayed.
Specifying how long device should hold hold-multiplier

received information before discarding
it
Specifying the amount of time between tx-interval <seconds>

LLDP transmissions
Enabling or disabling LLDP for device shutdown Enter no shutdown to enable LLDP.

Port Parameters
This section explains how to configure which TLVs to transmit for the port for the
different LLDP bridge types (see Table 8-8, Table 8-9, and Table 8-10 for details
on TLVs).
 To configure LLDP parameters for Ethernet port:

1. Navigate to configure port ethernet [<slot>/]<port>.
The prompt config>port>eth([<slot>/]<port>)# is displayed.
Enabling or disabling 802.1-protocol-identity {lldp | efm |

transmission of the specified cfm | lag-lacp | rstp-mstp | esmc
protocol in the IEEE 802.1 |erp-v2}
protocol identity TLV (see
Table 8-9)
Enabling or disabling customer-bridge-802.3 • mac-phy-configuration –
transmission of IEEE 802.3 TLVs [mac-phy-configuration] MAC/PHY
(see Table 8-10) in customer [power-via-mdi] [max-frame-size] Configuration/Status TLV
bridge mode • power-via-mdi – not
supported
• max-frame-size – maximum
Frame Size TLV
Enabling or disabling customer-bridge-basic-management • port-description – port

transmission of basic [port-description] [sys-name] description TLV
management TLVs (see [sys-description] [sys-capabilities] • sys-name – system name
Table 8-8) in customer bridge [management-address] TLV
mode
• sys-description – system
description TLV
• sys-capabilities – system
capabilities TLV
• management-address –
management address TLV
Specifying transmission mode in customer-bridge-mode {tx | rx | • tx – Transmit LLDP packets

customer bridge mode tx-rx} • rx – Receive LLDP packets
• tx-rx – Transmit and Receive
LLDP packets
Enabling or disabling nearest-bridge-802.3 • mac-phy-configuration –

(see Table 8-10) in nearest [max-frame-size] Configuration/Status TLV
bridge mode • max-frame-size – maximum
Frame Size TLV

Enabling or disabling nearest-bridge-basic-management • port-description – port

management TLVs (see [sys-description] [sys-capabilities] • sys-name – system name TLV
Table 8-8) in nearest bridge [management-address]
mode
description TLV
capabilities TLV
management address TLV
Specifying transmission mode in nearest-bridge-mode {tx | rx | tx-rx} • tx – Transmit LLDP packets

nearest bridge mode • rx – Receive LLDP packets
• tx-rx: Transmit and Receive
LLDP packets
Enabling or disabling non-tpmr-802.3 • mac-phy-configuration –

(see Table 8-10) in non-TPMR [max-frame-size] Configuration/Status TLV
bridge mode • max-frame-size – Maximum
Frame Size TLV
Enabling or disabling non-tpmr-basic-management • port-description – port

management TLVs (see [sys-description] [sys-capabilities] • sys-name – system name TLV
Table 8-8) in non-TPMR bridge [management-address]
mode
description TLV
capabilities TLV
Management address TLV
Specifying transmission mode in non-tpmr-bridge-mode {tx | rx | • tx – Transmit LLDP packets

non-TPMR bridge mode tx-rx} • rx – Receive LLDP packets
• tx-rx – Transmit and Receive
LLDP packets
Viewing detailed information show neighbors-details

about neighboring devices
Viewing brief summary of show neighbors-summary

neighboring devices
Viewing LLDP statistics show statistics
Clearing LLDP statistics clear-statistics
Example
The following example illustrates how to configure LLDP in the system.

#*********************************Configuring_LLDP in
system*****************
conf system lldp
tx-interval 10
hold-time 2
bridge-type nearest-bridge
no shutdown
exit all
#***************************Configuring_L2CP_Profile***********
**************
configure port
l2cp-profile lldp
mac 0x0e peer
exit all
configure port eth 1

l2cp profile lldp
no shutdown
exit all
#*****************************Configuring_LLDP in
port***********************
configure port ethernet 1 lldp
nearest-bridge-mode tx-rx
nearest-bridge-basic-management sys-description
nearest-bridge-basic-management sys-name
nearest-bridge-basic-management sys-capabilities
nearest-bridge-basic-management management-
address
nearest-bridge-basic-management port-description
nearest-bridge-802.3 mac-phy-configuration max-
frame-size
Viewing LLDP Neighbor Information

You can display detailed information about neighboring devices or display a brief
summary of neighboring devices.
 To display detailed information about neighboring devices:

1. Navigate to configure port ethernet [<slot>/]<port> lldp.
The prompt config>port>eth([<slot>/]<port>)>lldp# is displayed.
2. Enter show neighbors-details.
For example:
ETX-2# configure port ethernet 1 lldp
ETX-2>config>port>eth(1)>lldp# show neighbors-details
Name : RAD-ETX-2 ID : 00 01 00 00 00 03 02
Basic-Management Info
Bridge-Type : NEAREST
Chassis-type : MAC_ADDRESS
Chassis-id : 00:01:00:00:00:03
Port-Type : Locally Assigned
Port-id : eth-0/1

Port-Descr : Ethernet Port

System-name : RAD-ETX-205
System-Descr : RAD SWITCH
System Capabilities : REPEATER, MAC_BRIDGE
Enabled Capabilities : REPEATER, MAC_BRIDGE
Remote Management Address
Type : IPV4
Address : 192.168.200.10
802.1
Port-vlanId : 10
Port-protocol Vlan-id : --
Vlan Name : --
Protocol Identity : Link-aggregation, OAM, ELMI
VID Usage : --
Management VID : --
Link-Aggregation
Link Aggregation Status : Enabled
Lag-portId : 100
802.3
MAC/PHY configuration
Auto Negotiation Support Status : Supported
Auto Negotiation Current Status : Enabled
Auto-negotiation-advertised Capability : --
Operational MAU Type : --
POWER/MDI configuration
Port-class : --
MDI Support Status : --
MDI Current Status : Disabled
PSE Pair Control Ability : --
Power Class : --
Max Frame Size : 1500
8.5 MLDv2 Snooping

Multicast Listener Discovery Version 2, or MLDv2, is a protocol used by IPv6
routers to discover multicast listeners on attached links and addresses that are of
interest to them.
Multicast Listener Discovery Version 2 Snooping, or MLDv2 Snooping, is a practice
employed by IPv6 bridges to reduce multicast traffic by analyzing MLDv2
messages and limiting multicast traffic to ports interested in it.
Applicable Products
Standards
ETX-2 support MLD Snooping version 2.
ETX-2 MLDv2 Snooping 8-73

Note MLDv1 is not supported.
Benefits
Enables reduction in traffic by reducing the number of unneeded packets on the
network.
Factory Defaults
By default, MLD Snooping is disabled.
Table 8-11. MLD Snooping Factory Defaults
router port aging timer 260 seconds
member port aging timer 260 seconds
ETX-2 supports MLD Snooping for both VLAN-unaware and VLAN-aware bridges.
MLDv2 snooping can be enabled and disabled per bridge. In VLAN-aware bridges
it can also be enabled and disabled per VLAN. If snooping is disabled at the bridge
level, the per-VLAN configuration is ignored. This allows MLDv2 snooping to be
disabled on the entire bridge, without changing the per-VLAN configuration (e.g.
for troubleshooting).
When MLDv2 snooping is enabled, the bridge keeps two lists, per port (in VLAN-
unaware bridges) or per port and VLAN (in VLAN-aware bridges).
Router port list Ports from which MLDv2 router traffic is received
Member port list Pairs of port and multicast group address, to which
multicast traffic is to be forwarded
The bridge listens to messages on all MLDv2-snooping-enabled ports and

dynamically adds and removes ports to the router and member port lists.
The router-port list is maintained per port in VLAN-unaware bridges and per port
and VLAN in VLAN-aware bridges.
ETX-2 can receive multicast traffic from all ports and VLANs. MLDv2 snooping
builds a multicast forwarding database, rather than always forwarding multicast
traffic to all ports (in VLAN-unaware bridges) or all ports of a VLAN (in VLAN-
aware bridges).
ETX-2 supports MLDv2 Snooping on up to 16 VPNs.
Note Snooping is only enabled on a VLAN if it is enabled at both bridge and VLAN
levels. A command at either level does not change configuration of other levels.
8-74 MLDv2 Snooping ETX-2

MAC-based Forwarding Addresses

MLDv2 snooping supports forwarding databases that are either IPv6-based or
MAC-based. The ETX-2 has a MAC-based forwarding database. However, there are
some limitations when using MAC-based address forwarding.
When using a MAC-based forwarding database, IPv6 addresses are mapped to
MAC addresses by ANDing their last 32 bits with 0xffffffff, and adding a prefix of
0x3333. The IPv6 multicast address group ID, however, is 112 bits long. Since the
higher 80 bits of the group ID are omitted when mapping IPv6 addresses to MAC
addresses, then if the bits left of the right-most 32 bits are used in a group ID,
then multiple multicast IP addresses could be mapped to the same MAC address.
Since multiple IPv6 addresses could be mapped to single MAC addresses, the
following limitations apply:
• An IPv6 multicast address has the following format:
ffxx.xxxx.xxxx.xxxx.xxxx.xxxx.zzxx.xxxx. If the bridge receives a multicast IPv6
address with zz = 0xff or 0x00, MLDv2 snooping is not performed on the
packet, and it is forwarded to all ports in the VLAN except the port it was
received from. These address scopes contain special addresses, e.g. all
MLDv2-capable routers, which must be forwarded to all ports.
• To avoid one MAC address affecting multiple IPv6 addresses, make use of
only the lower 32 bits when choosing IPv6 multicast addresses.
If the ETX-2 bridge receives a report asking to join a multicast group with an
address of ffxx.xxxx.xxxx.xxxx.xxxx.xxxx.zzxx.xxxx, where zz = 0xff or 0x00, the
mld_snooping_unsupported_ip event is generated.
Note Data for unsupported addresses is forwarded to all ports, including ones behind
which there is no host interested in the address. To avoid this, use addresses out
of the unsupported ranges.
ETX-2 maintains a table of learned multicast IPv6 addresses. When it receives a

report asking to join a group that maps to the same MAC address as a different
group in that table, the new address ignored and the mld_snooping_duplicate_ip
event is generated.
Note Data for the duplicate address will be forwarded to the ports used by the one
already in the forwarding database. Duplicate addresses should either be
changed or configured statically.
Note
ETX-2 does not analyze group-specific and group-and-source-specific queries.
These queries are sent to group addresses, (unlike general queries, which are
sent to a fixed address). Information that could be learned from these queries
will eventually be learned from the periodic general queries, but it will take more
time for MLDv2 Snooping to adjust to that information.

Port Aging
Router port is the ETX-2 port facing the multicast router. Router port is learned
from receiving general queries and can age out. ETX-2x sets the router port aging
timer when a port is added to the router port list.
• The timer is rearmed when receiving an MLDv2 general query or an IPv6 PIM
hello message with source address different from 0::0.
• If the timer expires, the port is removed from the router port list.
• The router port list is maintained per bridge port in VLAN-unaware bridges, or
per VLAN and bridge port in VLAN-aware bridges.
A member port is the ETX-2 port facing a multicast client. Member port is learned
from report messages and is subjected to agin. The ETX-2 sets the member port
aging timer when a port joins an IPv6 multicast group.
• The timer is rearmed when receiving an MLDv2 report message.
• If the timer expires, the port is removed from the multicast group forwarding
table.
• The member port list is maintained per bridge port and multicast group in
VLAN-unaware bridges, or per VLAN, bridge port and multicast group in VLAN-
aware bridges.
ETX-2 must listen to MLDv2 general queries, sent to the link-scope all-nodes
multicast address (FF02::1), on all ports and all VLANs. General queries are sent
periodically by MLDv2 queries, to find the ports on which group members reside.
If a general query is received the bridge must:
• Forward the query to all ports (VLAN-unaware bridges) of all ports in the
VLAN (VLAN-aware bridges) except the receiving port.
• If the receiving port is not on the router-port list, add it to the list and set
the aging timer.
• If the receiving port is on the router-port list, rearm its aging timer.
ETX-2 must listen to MLDv2 reports, sent to FF02::16, to which all MLDv2
multicast routers listen, on all ports and all VLANs. Reports are sent by listeners
as responses to router queriers or when asking to join or leave a multicast group.
If MLDv2 report is received the bridge must:
• Peruse the report and update the member port list accordingly; that is, if a
host asks to join a group, add the receiving port to the member port list of
the group. Conversely, if a host is leaving a group the receiving port is not
immediately removed from the member list, since there may be other hosts
interested in the group on the port. Ports are only removed from the member
port list if the aging timer expires.
• Forward it to all router ports (in VLAN-unaware bridges) or all router ports in
the VLAN (in VLAN-aware bridges).
• If the receiving port is not on the member port list, add it to the list and set
the aging timer.
• If the receiving port is on the member port list, rearm the aging timer.
ETX-2 must receive all multicast traffic from all ports and VLANs. If multicast
packet that is not MLDv2 protocol traffic is received, the device must:

• In case of an unregistered multicast packet, i.e. a packet for a group with no

current members, forward it to all router ports (in VLAN-unaware bridges) or
all ports in the VLAN (in VLAN-aware bridges).
• In case of a registered multicast packet, forward it to:
 All router ports (in VLAN-unaware bridges) or all router ports in the VLAN
(in VLAN-aware bridges).
 All member ports (in VLAN-unaware bridges) or all member ports in the
VLAN (in VLAN-aware bridges) that are members of the multicast group.
Note A static router port is always on the router port list; it is not subjected to timer
aging.
A static member port is always on the member port list; it is not subjected to
timer aging.
Source-Specific Multicast
Source-Specific Multicast, or SSM, is a multicast service allowing hosts to
subscribe to specific multicast sources, and thus further reducing multicast traffic
in the network.
In addition to subscribing to a multicast group, hosts may ask to receive traffic
from a specific host. ETX-2, however, does not maintain a per-source database.
This means that multicast traffic sent to a specific group will be forwarded to all
members of that group, regardless of whether or not they are interested in the
traffic source.
MLD Snooping and Ethernet Ring Protection

When an ERP ring port changes state, all nodes in the ring receive a Signal Failure
(SF) message. If such a signal is received from a port on which MLDv2 snooping is
enabled, ETX-2 removes from the multicast forwarding database all the addresses
that are forwarded to either ring port (the addresses are removed from all ports,
including ones that are not ring members). This causes multicast traffic to be
forwarded to both ring ports until the new topology is learned from subsequent
reports and queries.
Configuring MLD Snooping

MLD Snooping must be enabled globally. VLAN related commands and arguments
apply only to VLAN-aware bridges.
 To configure MLD Snooping:

1. At the config>bridge <x> prompt, enter mld-snooping.
Where x is the bridge on which you want to configure MLD Snooping.
The config> bridge(x)> mld-snooping# prompt is displayed.

Enable/disable MLD snooping [no]shutdown [no] shutdown enables/disables

MLD Snooping globally on the
bridge. In addition, if the bridge is
VLAN aware you can enable and
disable MLD snooping on specific
VLANs, using the vlan command.
Configure host aging interval host-aging-interval<seconds> Possible values: 3–11264

Default: 260
Configure router aging interval router-aging-interval Possible values: 3–11264

Default: 260
Display MLD snooping status show status See Displaying MLD Snooping
Status.
Configure static multicast group static-group static-group <group-address> vlan

<vid> port <port-number-list>
no static-group <group-address>
[vlan <vid>]
Configure static router port static-router-port static-router-port vlan <vid> port

<port-number-list>
no static-router-port vlan <vid>
Configure MLD snooping VLANs vlan [no] vlan <vid-list>

If the command is repeated, it
does not replace the current
configuration; vid-list is either
added to the current configuration
or removed from it (using the no
option).
Displaying MLD Snooping Status

 To display MLD Snooping status:
• At the config>bridge x>mld-snooping# prompt, enter show status.
The MLD Snooping status is displayed.
Status output is displayed in the following format:
MLD Snooping Is Globally admin-state
MLD Snooping Is Enabled for VLAN snooping-vlans
Aging Interval
Host Ports (seconds): host-aging
Router Ports (seconds): router-aging
Router Ports:
VLAN Type Ports
------------------
r-v r-type r-ports

Host Ports:
VLAN IP Address Type Ports
----------------------------------------------------------
h-v h-ip h-type h-ports
Note
Port member tables are sorted by VLAN, then (the host port list) IP address, and
then type (static first).
MLD Snooping Status Example

MLD snooping is globally enabled
MLD Snooping Is Enabled for VLAN 1-100, 200
Aging Interval (seconds)
Host Ports : 260
Router Ports: 260
Router Ports:
VLAN Type Ports
------------------
1 static 1-5, 7
2000 learned 2, 7-10
Host Ports:
VLAN Group IP Address Type Ports
----------------------------------------------------------
100 ff00:1111:2222:3333:4444:5555:6666:7777 static 1-5, 7
2000 ff11:1111:1111:1111:1111:1111:1111:1111 learned 2, 7-10
Table 8-12. MLD Snooping Status Fields
admin-state MLD snooping admin state at bridge level; possible values: enabled,
disabled.
snooping-vlans VLANs for which MLD snooping is enabled
host-aging Aging time of host ports (in seconds)
router-aging Aging time of router ports (in seconds)
r-v VLAN the router ports of this entry are on; possible values: 1-4094.
r-type Type of this entry; possible values: static, learned
r-ports List of router ports
h-v VLAN the host ports of this entry are on; possible values: 1-4094.
h-ip Multicast IPv6 address this entry is on
h-type Type of this entry; possible values: static, learned
h-ports List of host ports
8.6 Pseudowire Connections

A pseudowire (PW) bundle provides emulation of Layer-2 point-to-point
connection-oriented services over packet-switching networks (PSN). The PW
ETX-2 Pseudowire Connections 8-79

parameters define the way a payload is transported via the E1/T1 ports through
the PSN network. You can configure up to 64 PW bundles.
Note If you have performed shutdown and then no shutdown of a PW cross connect or
smart SFP port, you must perform shutdown and then no shutdown of the PW.
Applicable Products
This feature is applicable to ETX205A with built-in E1/T1 ports and devices that
support smart SFP MiTOP functionality.
Standards
• IETF RFC 5086 (CESoPSN)
• IETF RFC 4553 (SAToP)
• ITU-T Y.1413 (CESoPSN, SAToP)
• ITU-T Y.1453 (CESoPSN, SAToP)
The device supports the CESoPSN and SAToP network encapsulation methods,
transmitting E1/T1 traffic over Ethernet (MEF 8) or UDP/IP packet-switched
networks. TDM PW is supported over G.8032 rings, for MEF 8 and UDP/IP.
Note
If the E1/T1 port is in CAS mode, only CESoPSN with CAS encapsulation over
UDP/IP PSN is permitted.
Pseudowire Packet Structure

A PW packet comprises the following data components (see the figure below):
Ethernet Header Contains the DA (destination MAC address), SA (local MAC

address), and Ethernet network type
PSN Header Defines the PSN transport type: Ethernet or UDP/IP
Control Word Data control as defined in the relevant IETF RFCs and drafts
Payload TDM service payload containing the actual traffic data
Figure 8-14. Basic PW Structure
Note The source MAC address is the egress port MAC address for MEF 8 (Ethernet)
PWs, or the MAC address of the egress router interface for UDP/IP PWs.
8-80 Pseudowire Connections ETX-2

TDM Service Encapsulation

TDM traffic can be encapsulated over PSN in two modes:
CESoPSN CES (Circuit Emulation Services) over PSN, for framed E1/T1
traffic with or without CAS
SAToP Structure-Agnostic TDM over Packet, for unframed E1/T1

traffic
CESoPSN
The CESoPSN method is a structure-aware format for framed E1/T1 services. It
converts structured E1/T1 data flows into IP packets and vice versa with static
assignment of timeslots inside a bundle according to IETF RFC 5086 and
ITU-T Y.1413. The CESoPSN packet size is a multiple of TDM frame size. The
following figure illustrates CESoPSN encapsulation without CAS.
TDM Payload
L2/L3 Control
4 25 4 25 4 25 CRC Ethernet Packet
Header Word
FRG bits = 00 Frame Frame Frame

(no fragmentation) 1 2 N
4 25 4 25 4 25
Frame 1 Frame 2 Frame N
Figure 8-15. CESoPSN Encapsulation – E1 without CAS, Bundle with Timeslots 4 and 25
CESoPSN with CAS is configurable in the following cases only:

• The corresponding E1 is configured to framed mode with CAS (with or
without CRC).
• The corresponding T1 is configured to SF (D4) or ESF. It is the user’s
responsibility to configure both ends with the same frame type.

If CESoPSN with CAS is used (ETX205A) , the timeslot structure is according to

IETF RFC 5086 and ITU-T Y.1453, as shown below.
Figure 8-16. CESoPSN with CAS – Timeslot Structure
CESoPSN with CAS supports the following E1 fragmentation options:

• Four E1 frames per packet – packetization delay of 0.5 ms
• Eight E1 frames per packet – packetization delay of 1 ms
• 16 E1 frames per packet (no fragmentation) – packetization delay of 2 ms
CESoPSN with CAS supports the following T1 fragmentation options:
• Four T1 frames per packet – packetization delay of 0.5 ms
• 12 T1 frames per packet (no fragmentation for SF) – packetization delay of
1.5ms
• 24 T1 frames per packet (no fragmentation for ESF) – packetization delay of
3 ms. This value is not applicable for SF (sanity).
Note When there is no fragmentation, 16 E1 frames + CAS info are encapsulated into
one packet, causing a greater packetization delay than the two options with
fragmentation. The other two options have a lower packetization delay, but the
PW has increased bandwidth.
Similarly, when there is no fragmentation, 12 T1 frames + CAS info (for SF) or 24
T1 frames + CAS info (for ESF) are encapsulated into one packet, causing a
greater packetization delay than the option with fragmentation.

Figure 8-30 illustrates CESoPSN encapsulation with CAS, without fragmentation.

In a PW bundle structured with CAS, the TDM payload includes N × TDM frame
data blocks (each data block is assembled from the bundle-assigned timeslots)
from a whole multiframe (e.g. – N is 16 for E1) followed by the CAS signaling
substructure that contains the CAS information of the corresponding multiframe
of the bundle-assigned timeslots.
Figure 8-17. CESoPSN Encapsulation – E1 with CAS, Bundle with Timeslots 2, 4,

and 25 (No Fragmentation)
Figure 8-30 illustrates CESoPSN encapsulation with CAS, with fragmentation.

CESoPSN supports fragmentation in order to reduce the packetization time of a
bundle structured with CAS packet. In CESoPSN mode, the multiframe data
structure is divided into several packets. Each packet contains M × TDM frame
blocks. The last packet contains M × TDM blocks followed by the entire
multiframe CAS information.

Figure 8-18. CESoPSN Encapsulation – E1 with CAS, Bundle with Timeslots 2, 4,

and 25 (with Fragmentation)
SAToP
The SAToP encapsulation method is used to convert unframed E1/T1 data flows
into Ethernet or IP packets and vice versa according to ITU-T Y.1413 and
IETF RFC 4553. It provides flexible packet size configuration and low end-to-end
delay.
L2/L3 Control Ethernet

TDM Payload CRC
Header Word Packet
FRG bits = 00
(no fragmentation)
TDM
Bitstream
N TDM Bytes
Figure 8-19. SAToP Encapsulation

Encapsulation over Different PSN Types

ETX-2 can encapsulate the pseudowire connections for the following types of
PSN transport networks:
• UDP/IP (UDP over IP)
• MEF 8 (Ethernet)
When the PSN type is UDP over IP, ETX-2 enables you to select the mode of
configuring the IP priority of the IP/UDP packet: DSCP or ToS. Once you select the
mode, you can configure the DSCP or ToS value.
Jitter Buffer
The packets of each pseudowire are transmitted by ETX-2 at essentially fixed
intervals toward the PSN. The packets are transported by the PSN and arrive to
the far end after some delay. Ideally, the PSN transport delay should be constant,
meaning the packets arrive at regular intervals (equivalent to the intervals at
which they were transmitted). However, in reality, packets arrive at irregular
intervals, because of variations in the network transmission delay. The term
Packet Delay Variation (PDV) is used to designate the maximum expected
deviation from the nominal arrival time of the packets at the far end device.
Note
The deviations from the nominal transmission delay experienced by packets are
referred to as jitter, and the PDV is equal to the expected peak value of the jitter.
However, nothing prevents the actual delay from exceeding the selected PDV
value.
To compensate for deviations from the expected packet arrival time, ETX-2 uses
jitter buffers that temporarily store the packets arriving from the PSN (that is,
from the far end equipment) before being transmitted to the local TDM
equipment, to ensure that the TDM traffic is sent to the TDM side at a constant
rate.
For each pseudowire, the jitter buffer must be configured to compensate for the
jitter level expected to be introduced by the PSN; that is, the jitter buffer size
determines the Packet Delay Variation Tolerance (PDVT).
Two conflicting requirements apply:
• As packets arriving from the PSN are first stored in the jitter buffer before
being transmitted to the TDM side, TDM traffic suffers an additional delay.
The added delay time is equal to the jitter buffer size configured by the user.
• The jitter buffer is filled by the incoming packets and emptied to fill the TDM
stream. If the PSN jitter exceeds the configured jitter buffer size,
underflow/overflow conditions occur, resulting in errors at the TDM side:
 A jitter buffer overrun occurs when it receives a burst of packets that
exceeds the configured jitter buffer size + packetization delay. When an
overrun is detected, ETX-2 clears the jitter buffer, causing an underrun.
 A jitter buffer underrun occurs when no packets are received for more
than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is
automatically filled with a conditioning pattern up to the PDVT level in order to

compensate for the underrun. Then, ETX-2 starts processing the packets and
emptying the jitter buffer toward the TDM side.
To minimize the possibility of buffer overflow/underflow events, two conditions
must be fulfilled:
• The buffer must have sufficient capacity. For this purpose, the buffer size can
be selected by the user in accordance with the expected jitter characteristics,
separately for each pseudowire, in the range of 1 to 180 ms.
• TDM clocks at both ends should be synchronized so that the read-out rate
shall be equal to the average rate at which frames are received from the
network. One way to achieve this is by adaptive clock recovery, which
continuously adapts the recovered clock to the packet rate. Other ways may
be by distributing the same clock to ETX’s by SyncE, 1588, or External clock
input.
Factory Defaults
No PWs are included in the ETX-2 factory defaults. You must define the necessary
PWs in accordance with your application requirements.
When you create a PW, it is configured by default, as shown below.
ETX205A>config>pwe>pw(1)# inf d
shutdown
name "Put your string here"
description "Put your string here"
no peer
label in 0 out 0
no oam
vlan priority 0
ip-priority-type tos
tos 184
tdm-payload size 0 rate 0
jitter-buffer 2000
psn-oos stop-tx
udp-mux-method dst-port
pm-enable
Configuring Pseudowire Bundles

The configuration of a PW bundle comprises the following steps:
1. Verify that all the necessary ports have been configured as needed and are
administratively enabled.
2. Verify that the peer to be used for the PW has been defined.
3. Verify that Layer-2 and Layer-3 entities have been defined (e.g. flows, router,
etc.).
4. If you are configuring PW encapsulation for PSN – UDP over IP (see step 6),
configure the router interface for PWE, making sure to set the router
interface to no management-access (mandatory). You are not required to
configure the router interface for PSN MEF 8 (Ethernet).
Only one router interface can be configured for PWE.

5. Select the PW connection type: CESoPSN for framed E1/T1 packets, SAToP for
unframed E1/T1 packets.
6. Select the PSN type: UDP over IP or Ethernet.
Note All PWs must have the same PSN type.
7. Configure the PW parameters in accordance with the selected connection

type and PSN type.
See Examples below on how to create a CES PW with UDP encapsulation and a
SaTOP PW with Ethernet encapsulation.
Note
When an E1/T1 clock source is configured to adaptive, it uses the first configured
PW bundle as the adaptive clock source.
Adding Pseudowire Bundles

You can create up to 64 pseudowire bundles per device and one pseudowire per
MiToP, and link to each one a predefined peer (up to 64 can be defined per
device).
You create a new pseudowire bundle in the level configure pwe. When you define
the PW bundle, you define its number (1–64), connection type, and PSN type.
You can configure up to eight PW bundles per E1/T1 port, with the exception that
you can create up 16 PW bundles for an E1/T1 port working in CAS mode.
 To add a PW:
• At the config>pwe# prompt, enter:
pw <pw> [type {ces-psn-data|e1satop|t1satop }] [psn {ethernet | udp-over-ip
}] [manually].
Table 8-13. PW Parameters
type Specifies connection type

ces-psn-data – PW bundle using the CESoPSN protocol, for carrying framed data
streams
e1satop – PW bundle using the SAToP protocol, for carrying an unframed E1 data
stream
t1satop – PW bundle using the SAToP protocol, for carrying an unframed T1 data
stream
psn Specifies packet-switched network type

ethernet – MEF 8 packet structure
udp-over-ip – UDP over IP with standard packet structure
provisioning Specifies the provisoning mode

manually – The pseudowire labels are manually established.
As manually is the only setting for the PW provisioning, it is not necessary to type
the manually parameter.

Note When the PW encapsulation type is SAToP and the PSN type is Ethernet, alarms
are forwarded toward E1 ports only if the E1 port trail mode is configured to
extended (refer to Configuring E1 Ports in the Cards and Ports chapter).
Configuring Pseudowire Bundle Parameters

ETX-2 presents configuration parameters relevant only to the PW type and PSN
type. The table of tasks below specifies if a parameter is relevant only for a
certain PW type/PSN type.
 To configure a PW bundle:
1. Add a PW bundle as explained in Adding Pseudowire Bundle above.
2. At the config>pwe>pw(<pw-number>)# prompt, enter all necessary
commands according to the tasks listed below.
Defining the fragmentation cas-frames-per-packet {4 | 8 Relevant only for CESoPSN with CAS
option for CESoPSN with | 12 | 16 | 24} • 4 – Four E1/T1 frames per packet
CAS (fragmented)
• 8 – Eight E1 frames per packet (fragmented)
• 12 – 12 T1 frames per packet (for SF, not
fragmented)
• 16 E1 frames per packet (not fragmented)
• 24 – 24 T1 frames per packet (for ESF, not
fragmented)
Clearing PW statistics clear statistics The current and running counters are cleared;
the interval counters are not cleared.
Configuring the value of dscp <number> number – the value of the IP DSCP field in egress
the IP header DSCP field packets.
Note: Relevant only when IP priority type is
DSCP, and PSN type is UDP over IP.
Providing pseudowire description <pw-descr> For identification of the PW customer
description no description
Defining the egress port egress-port svi Relevant only if the PSN type is Ethernet.
for PW with Ethernet <port-number> Note: If you need to change the egress SVI port
encapsulation for an active PW configured over a built-in E1/T1
port, you need to do the following:
• Administratively disable the PW.
• Change the egress SVI.
• Delete the relevant cross connect entry.
• Administratively re-enable the PW.
• Configure the cross connect.

Selecting the IP priority ip-priority-type {tos | dscp} Note: Relevant only when PSN type is UDP over
field used to configure the IP.
IP priority of the IP/UDP If you select IP priority type ToS, configure the
packet: ToS or DSCP tos value (see command in this table).
Otherwise, if you select IP priority type DCSP,
configure the dscp value (see command in this
table).
Defining the jitter buffer Jitter-buffer <jitter-size> Possible values: 1000–180000

size in µsec. It is recommended to use the shortest feasible
buffer, to minimize connection latency.
Selecting source and label [in <in-pw-label>] in-pw-label – the PW label used in the inbound
destination circuit bundle [out <out-pw-label>] direction
identifiers (CBID), also out-pw-label – the PW label used in the
referred to as PW labels outbound direction
Possible values for labels: 1–8191
Each PW bundle must have a unique in (source)
label.
It is not recommended to reuse the same out
(destination) value on PW bundles terminating at
the same peer.
Assigning a name to the name <pw-name> For identification of the PW service

pseudowire no name
Enabling OAM for the PW, oam [rising-threshold The delay threshold is set as follows:
and specifying rate in ms <rising>] [falling-threshold • rising-threshold – 1–180 ms
<falling>]
• falling-threshold – 1–180 ms
no oam
The falling threshold must be less than or equal
to the rising threshold.
Defining the peer for the peer <peer-number> peer-number – the number of the remote peer
PW no peer which terminated this PW
The peer type must be according to the PSN
type:
• IP address for UDP/IP
• MAC address for Ethernet
Specifying if PM collection pm-enable Entering no pm-enable disables PM collection.

is enabled for the PW
Selecting the response to psn-oos {l-bit | stop-tx} Out-of-service conditions receive a response by
out-of-service conditions transmitting PW frames filled with all ones, or by
detected at the local E1/T1 stopping transmission.
physical port

Specifying TDM payload tdm-payload size <size> Note: TDM payload size can be configured for
size in bytes and rate rate <rate> CESoPSN only if the associated E1/T1 port is not
(number of time slots for in CAS mode.
each frame in the packet) if Size according to PW type:
applicable e1satop – N×32; range 32–1440
t1satop – N×24; range 24–1440
ces-psn-data – N × number of time slots in a
bundle; range 4–1440
Rate: 1–31 for E1; 1–24 for T1
Note: Rate is relevant only for PW type
ces-psn-data.
It is recommended to specify the parameter
values such that the ratio size/rate is between 2
and 256.
A larger size increases the bandwidth utilization
efficiency, but also increases the connection
intrinsic latency, in particular when the PW
bundle is configured to carry a small number of
timeslots.
Specifying the Layer-3 tos <tos> tos – the value of the IP TOS byte in egress
priority assigned to the packets
traffic generated by the PW Possible values: 0–255
In accordance with RFC 2474, it is recommended
to use only values that are multiples of 4.
Note: Relevant only when IP priority type is TOS,
and PSN type is UDP over IP.
Specifying the UDP port udp-mux-method dst-port dst-port – Standard multiplexing method:
multiplexing method UDP destination port = 0xC000 + <out-PW-label>
UDP source port is 0xC000 + <in-PW-label>
Note: Relevant only for PSN type UDP over IP
Enabling the VLAN tag on vlan priority <vlan-priority> vlan-priority – the VLAN priority on every
every transmitting packet no vlan transmitted packet for this PW
for the PW and specifying Possible values: 0-7
the VLAN priority.
Entering no vlan disables the VLAN tag on the
transmitting packets for the PW.

Displaying PW statistics show statistics { current | • current – displays PW statistic counters for
interval <interval-num> | all- the current interval
intervals | all } • interval – displays PW statistics for the
selected interval
• all-intervals – displays PW statistics for all
intervals since the PW statistics collection has
been enabled
• all – displays PW statistics for current
interval and all intervals
Note: The statistics are visible only when
performance management is enabled for the
corresponding E1/T1 port.
See Viewing PW Statistics.
Displaying PW connectivity show connectivity-statistics Note: The statistics are visible only when
statistics performance management is enabled for the
corresponding E1/T1 port.
See Viewing PW Connectivity Statistics.
Displaying PW status show status
Administratively enabling no shutdown Type shutdown to administratively disable the

the PW bundle PW.
Deleting Pseudowire Bundles
 To delete a PW:
1. At the config>pwe>pw(<pw-number>)# prompt, enter:
shutdown
The PW is administratively disabled.
2. At the config>pwe# prompt, enter:
no pw <pw-number>.
The PW is removed.
Viewing Pseudowire Configuration

You can display information about the PW configuration.
 To display PW information:
• At the prompt config>pwe#, enter show summary.
For example,
ETX-2>config>pwe# show summary
PW : 1 PW Type : CES PSN Data

PSN Type : UDP Over IP Oper : Not present

Out Label : 0 In Label : 0

Peer : 0 Port : Unknown port 0
Jitter Buffer : 2000 Payload Size : 0

See above table for field descriptions.
Viewing PW Statistics
ETX-2 PWs feature the collection of statistical diagnostics, thereby allowing the
carrier to monitor the transmission performance of the links.
The pseudowire transmission statistics enable analysis of pseudowire traffic
volume, and evaluation of the end-to-end transmission quality (as indicated by
sequence errors) and jitter buffer performance. By resetting the status data at
the desired instant, it is possible to ensure that only current, valid data is taken
into consideration.
 To display the PW statistics:

• At the prompt config>slot>pwe>pw(<pw_number>)#, enter show statistics
followed by current | interval <interval-num> | all-intervals | all.
For example, show current statistics:
ETX-2>config>pwe>pw(1)# show statistics current

PW : 1
Port : Unknown port 0
Current
---------------------------------------------------------------
Valid Intervals : 0
Rx Packets : 354994
Tx Packets : 354995
Missing Packets : 0
Mis-order Dropped Packets : 0
Reordered Packets : 0
Malformed Packets : 0
Jitter Buffer Underrun : 0
The fields are:
Table 8-14. TDM PW Statistic Counters
Rx Packets Number of packets received on the PW from the PSN
Tx Packets Number of packets transmitted on the PW toward the PSN
Missing Packets Number of missing packets as detected via CW sequence number gaps. This
count does not include misordered dropped packets.
Misordered Dropped Number of packets detected via CW sequence number to be out of sequence,
Packets and could not be re-ordered, or could not fit in the jitter buffer. This count
includes duplicated packets.

Reordered Packets Number of packets detected via CW sequence number to be out of sequence,
but successfully reordered
Malformed Packets Number of packets with mismatch between the expected packet and the actual
packet sizes
Jitter Buffer Underrun Number of times jitter buffer was in underrun state
Viewing PW Connectivity Statistics

ETX-2 PWs feature the collection of connectivity statistics for the current,
running, previous, or all intervals. These statistics display the jitter buffer level
(average/current, minimum, and maximum), and round trip delay
(average/current, minimum, and maximum) for a specific interval or for all
intervals.
 To display the PW connectivity statistics:

• At the prompt config>slot>pwe>pw(<pw_number>)#, enter show
connectivity-statistics followed by current | interval <interval-num> | all-
intervals | running.
For example, show connectivity statistics for interval 1:
ETX-2# config pwe pw 1 show connectivity-statistics interval 1
Interval Number : 1
Valid Data : Valid
Start Time : 23-06-2015 13:15:10 UTC +00:00
Duration (Sec) : 901
Minimum Average Maximum

Jitter Buffer Level (msec): 1.500 2.097 2.500
Round Trip Delay (msec) : 0.200 0.230 0.261
The fields are:
Table 8-15. TDM PW Connectivity Statistic Counters
Jitter Buffer Level Minimum – displays the minimum level of the jitter buffer since the last reset (in
msec)
Average/Current – for current and previous intervals, displays the average level
of the jitter buffer; for running interval, displays the current level of the jitter
buffer (in msec)
Maximum Units – displays the maximum level of the jitter buffer since the last
reset (in msec)
Round Trip delay Minimum – displays the minimum round trip delay since the last reset (in msec)
Average/Current – for current and previous intervals, displays the average round
trip delay; for running interval, displays the current round trip delay (in msec)

Maximum Units – displays the maximum round trip delay since the last reset (in
msec)
Examples
 To create and activate a CES PW with UDP encapsulation:
Note The E1 port must be configured for framed traffic.
exit all
config flow
match untagged
exit
flow 1
classifier "mng_untagged"
no shutdown
exit
flow 2
ingress-port svi 1
no shutdown
exit all
config router 1 interface 1

address 10.10.10.10/24
bind svi 1
no management-access
no shutdown
exit all
config peer 1 ip 10.10.10.11
configure pw
pw 1 type ces-psn-data psn udp-over-ip
peer 1
label in 100 out 100
tdm-payload size 40 rate 10
no shutdown
exit all
configure cross-connect
pw-tdm pw 1 e1 1 time-slots 1..10
exit all
 To create and activate a SaTOP PW with Ethernet encapsulation:
Note The E1 port must be configured for unframed traffic.
config flow

match untagged
exit
flow 1
no shutdown
exit
flow 2
ingress-port svi 1
no shutdown
exit all
config peer 1 mac 00-00-00-00-00-01

configure pw
pw 1 type e1satop psn ethernet
egress-port svi 1
peer 1
label in 100 out 100
tdm-payload size 34
no shutdown
exit all
configure cross-connect
pw-tdm pw 1 e1 1
 To create and activate a CESoPSN with CAS PW with UDP encapsulation:
Note The E1 port must be configured for framed traffic with signaling.
configure
peer 1 ip 10.10.20.100
port
svi 1
no shutdown
exit
e1 1
tx-clock-source pw 1
line-type g732s
pm-enable
no shutdown
exit
exit
flows
classifier-profile "all" match-any
match all
exit
classifier-profile "unt" match-any
match untagged
exit
flow "in"
classifier "unt"
no policer

no shutdown
exit
flow "out"
classifier "all"
no policer
ingress-port svi 1
no shutdown
exit
exit
router 1
interface 1
address 10.10.20.200/24
bind svi 1
dhcp-client
client-id mac
exit
no shutdown
exit
exit
pwe
pw 1 type ces-psn-cas psn udp-over-ip
peer 1
label in 20 out 20
no vlan
jitter-buffer 10000
psn-oos 1-bit
pm-enable
cas-frames-per-packet 16
no shutdown
exit
exit
cross-connect
exit
exit
8.7 PW Cross Connects
Applicable Products
This feature is applicable to ETX205A with built-in E1/T1 ports anddevices that
support smart SFP MiTOP functionality.
PW cross-connects are used to connect E1/T1 ports to pseudowire bundles.
8-96 PW Cross Connects ETX-2

Factory Defaults
No PW cross-connects are included in the ETX-2 factory defaults.
Configuring PW Cross Connects

 To configure PW cross-connects for E1/T1 ports:
• At the config>cross-connect# prompt, enter the pw-tdm command as
follows:
pw-tdm pw <pw> {e1|t1} <port> [time-slots <list>]
where:
 <pw> – specifies number of pseudowire bundle that must already exist
and be active
 <port> – specifies the E1/T1 port number
 <list> – list of timeslots to assign to the PW bundle. Note that time-slots
<list> option can be used only if the PW type is CESoPSN. The list can be
a single value or range (in the form <ts1..ts2>). The specified timeslots
must be compatible with the payload size and rate specified for the PW
via the tdm-payload command.
The E1/T1 port line-type must be compatible with the PW type, as follows:
• If the PW type is ces-psn-data, the E1/T1 port line-type must be g723n or
g723n-crc for E1; esf for T1.
• If the PW type is e1satop or t1satop, the E1/T1 port line-type must be
unframed.
Note
Following shutdown and then no shutdown of PW cross connects, you must
perform shutdown and then no shutdown of PW.
Examples
In these examples, PW 1 must be active; see Examples in Pseudowire Connections
for instructions on configuring and enabling PWs.
 To assign E1 port timeslots 1–31:
exit all
config cross-connect
exit all
 To remove the E1 port timeslot assignment for PW 1:

exit all
config cross-connect
no pw-tdm pw 1 e1
exit all
ETX-2 PW Cross Connects 8-97

8.8 Router
The router provides an IP forwarding plane for IPv4 and IPv6 packets, and also
interconnects internal Layer-3 support modules, such as management and
1588v2 (recovered clock). Any flow related to IP forwarding, management traffic,
or timing must be via an SVI or PPP that is bound to a router interface.
Applicable Products
This feature is applicable to all ETX-2 products and to the PMC in ETX205A, with
the following conditions:
• Clock is relevant to ETX205A and ETX220A.
• Pseudowire connections are relevant to ETX205A.
Standards
RFC 1812 – Requirements for IP Version 4 Routers
RFC 2460 – Internet Protocol, Version 6 (IPv6) Specification
RFC 2464 – Transmission of IPv6 Packets over Ethernet Networks
RFC 4291 – IP Version 6 Addressing Architecture
RFC 4294 – IPv6 Node Requirements
RFC 4443 – Internet Control Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification
RFC 4862 – IPv6 Stateless Address Autoconfiguration
RFC 5880 – Bidirectional Forwarding Detection general protocol
RFC 5881 – Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single
Hop) protocol
RFC 5882 – Generic Application of Bidirectional Forwarding Detection (BFD)
RFC 2663 – IP Network Translator (NAT) Terminology and considerations
RFC 2766 – Traditional IP Address Translator
RFC 3489 – Simple Traversal of User Datagram Protocol through Network Address
Translator (STUN)
RFC 7857 –Traditional IP Address Translator
Benefits
The router provides IP Routing and Forwarding for IPv4 and IPv6 packets.
8-98 Router ETX-2

Notes • An ETX-2 router supports up to 32 router interfaces; however, only one router
interface is supported when working with PWs, and only two router interfaces
can be configured for management access.
• In order 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.
Overview
Any flow into/out of the device, which is related to management/timing, 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 should be enabled for
management access.
Figure 8-20. Router and SVIs
The router maintains a table of IPv6 neighbors, via discovery of neighboring IPv6
nodes. It is recommended to manage ETX-2 via a router interface defined as a
loopback interface, as this router interface remains active. To ensure that packets
generated by the router are transmitted with the loopback IP address, you need
to define the management source IP address for IPv4 and IPv6 (refer to
Management Source IP Address in the Management and Security chapter).
The MAC addresses used by router interfaces are as follows:
• Router interface that resides directly on a port uses that port’s MAC address
• Router interface that resides on a bridge port uses the Ethernet management
port MAC address
• Router interface connected to an ETP subscriber port uses the Ethernet
management port MAC address.
The management and control packets transmitted by the router have a
configurable IP DSCP value, so that each router entity can control its traffic
priority by setting its DSCP value for its protocols (see Configuring the Router on
how to configure the DSCP).
ETX-2 Router 8-99

Router Interface Forwarding

The following tables specify the classification, editing, and queue/CoS mapping
for flows to and from a router interface.
Table 8-16. Flows to Router Interface
Classification VLAN editing CoS mapping Comments
Untagged None None Mapped to CoS = 0
DSCP None DSCP mapping profile

(DSCP to CoS) or none
Non IP None None Mapped to CoS = 0
VLAN + DSCP Pop DSCP mapping profile

VLAN Pop DSCP mapping profile

VLAN + non IP Pop None Mapped to CoS = 0
Outer VLAN, inner VLAN Pop,pop DSCP mapping profile

Outer VLAN, Pop,pop DSCP mapping profile

inner VLAN + DSCP (DSCP to CoS) or none
Outer VLAN, Pop,pop None

inner VLAN + non IP
Table 8-17. Flows from Router Interface
Classification VLAN editing CoS mapping Comments
Untagged None, push single VLAN, push VLAN DSCP to queue or fixed DSCP to p-bit or fixed
and inner VLAN
DHCPv6 Option Request

In the ETX203AX device, you can configure the DHCP client to request the
DHCPv6 server for vendor-specific option 17 (using the dhcpv6-option-request
command). The DHCPv6 server offers this option only if you configure the
device’s DHCP client to request it.
Vendor-specific option (17) is used to pass data needed to run the Zero Touch
process (refer to Zero Touch in the Operation and Maintenance chapter for a
description). This data includes TFTP server IP and the name of the file to
download (optional).
Factory Defaults
By default, ETX-2 is configured with Router 1 and Router Interface 32. The
default values of the router interface parameters are configured as shown in the
following table.
8-100 Router ETX-2

address 169.254.1.1/16
bind svi 96
shutdown no shutdown
Once you create a new router, its dynamic entities are configured with the
default values shown in the following table.
name "Router#n” n – number of the router

dhcp-client dhcpv6-option- no dhcpv6-option-request

request
dhcp-client vendor-class-id ent-physical-name In the DHCP client, the entity physical name
is used as the vendor class ID.
dscp 0
static-preference ipv4 1
static-preference ipv6 1
Once you create a new router interface, its dynamic entities are configured with
the default values shown in the following table.
name no name No router interface name
bind no bind Router interface not bound.
vlan no vlan No router interface VLAN
management-access allow-all
mtu 1500
dhcp no dhcp DHCP client disabled
dhcp-client client-id mac
dhcpv6-client no dhcpv6-client DCHPv6 client disabled
ip-forwarding ip-forwarding IP forwarding enabled
shutdown shutdown Router interface disabled
ipv6-autoconfig no ipv6-autoconfig IPv6 autoconfiguration disabled
unreachables unreachables ICMP unreachables enabled
dhcp-relay no dhcp-relay DHCP relay disabled
bfd bfd min-tx 1s min-rx 1s Assignment of BFD control packets

multiplier 3
ETX-2 Router 8-101

Configuring the Router

The router functionality allows ETX-2 to establish links to Ethernet ports via SVIs,
or to peers that provide the 1588v2 master clock, or to establish PPPoE sessions
via PPP ports.
You can configure up to ten routers on a device.
 To configure the router:

1. At the config# prompt, enter:
router <number>; number can be 1 to 10.
The config>router(<number>)# prompt is displayed.
Starting session with BFD bfd-neighbor <ip-address> {associated |

neighbor non-associated}
Deleting dynamic ARP entities clear-arp-table [<address>] Specify the IP address to clear only
the entries corresponding to it.
Clearing BFD statistics clear-bfd-statistics <ip-address>
Clearing IPv6 neighbor table clear-neighbor-table
Clearing router statistics clear-statistics all Router statistics include:

clear-statistics ipv4 {access-list | traffic} • IPv4 and IPv6 router system
clear-statistics ipv6 {access-list | traffic} statistics
• IPv4 and IPv6 router interface
statistics
• Statistics of all (either IPv4 or
IPv6) access lists bound to the
router
Creating a router interface interface <interface-num> [{loopback } ] interface-num – a unique number

assigned to the router interface
loopback – configures interface as a
loopback interface
Type no interface <interface-num>
to delete a router interface.
See the Configuring Router
Interfaces section for a list of tasks
that can be configured on a router
interface.
Assigning name to router name <string> Alphanumeric string
Setting the priority of static static-preference {ipv4 | ipv6} <priority> Possible values for number: 0–255
routes for IPv4 and IPv6 RTM Default: 1
8-102 Router ETX-2

Enabling the static route and static-route The next hop must be a subnet of
the next gateway (next hop) <ip-address/ip-mask-of-static-route> address one of the router interfaces.
using the next hop’s IP address <ip-address-of-next-hop> [metric <metric>][ To set the default-gateway,
install | no-install ] configure the static route of address
no static-route <ip-address/prefix-length> 0.0.0.0/0 to next hop default
address address gateway address.
no static-route deletes static route
entry.
metric specifies the priority of the
static route
Default: 1
install option forwards a specific
route entry into the FIB.
no-install option does not forward a
specific route entry into the FIB.
Enabling the static route and static-route no static-route deletes static route
the router interface number <ip-address/ip-mask-of-static-route> entry.
toward which the destination interface <router-interface-num> [metric metric specifies the priority of the
subnet is to be routed <metric>][ install | no-install ] static route: 1–255 (default: 1).
no static-route <ip-address/prefix-length> install option forwards a specific
interface <router-interface-num> route entry into the FIB.
no-install option does not forward a
specific route entry into the FIB.
Displaying the summary of show access-list summary Refer to Access Control List (ACL) in
ACLs bound to router interface the Management and Security
chapter for further information.
Displaying the address show arp-table [ address <ip-address> ]

resolution protocol (ARP) table,
which lists the original MAC
addresses and the associated
(resolved) IP addresses
Displaying BFD neighbor table show bfd-neighbors

show bfd-neighbors-details
Displaying the interface table show summary-interface See Viewing Router Interface
Information.
Displaying IPv6 neighbors table show neighbor-table [address <ip-address>] See Viewing IPv6 Neighbors.
Displaying the routing table show routing-table [ address ip-address/ip-mask – View routing
<ip-address/ip-mask> ] information for a specific IP address
of a specified prefix length.
See Viewing Routing Information.
Displaying the IPv4 or IPv6 RIB show rib { ipv4 | ipv6 } See Viewing RIB.
(Routing Information Base)
table
ETX-2 Router 8-103

Displaying router statistics show statistics ipv4 access-list {in | out}

show statistics ipv4 traffic
show statistics ipv6 access-list {in | out}
Configuring DHCP client for the dhcp-client

router interface
Commands in level dhcp-client
Configuring DHCP client to dhcpv6-option-request [vendor-specific- Vendor specific option 17 is used

request DHCPv6 server for information-17] to pass data needed for the Zero
option 17 no dhcpv6-option-request Touch process.
Notes:
• The command behaves the
same regardless of whether you
specify vendor-specific-
information-17 optional
keyword.
• Entering no dhcpv6-option-
request results in DHCP client
not explicitly requesting option
17.
Providing host name to DHCP host-name name <string> You can specify a name, or specify
server host-name sys-name sys-name to indicate that the
system name should be used as
no host-name
the host name.
Providing vendor ID to DHCP vendor-class-id name <string> You can specify an ID, or specify
server vendor-class-id ent-physical-name ent-physical-name to indicate that
the device name should be used as
the vendor ID.
Configuring DSCP value for dscp <number> Possible values: 0–63

router entity traffic Default: 0
Configuring Router Interfaces

You can configure up to 32 router interfaces. However, only one routing interface
is supported when working with PWs, and only two routing interfaces can be
configured for management.
 To configure router interfaces:

1. At the config>router(<number>)# prompt, enter:
interface <interface-num> [loopback]
The config>router(<number>)>interface(<interface-num>)# prompt is
displayed.
8-104 Router ETX-2

Binding ACL to router interface access-group Refer to Access Control List (ACL)
in the Management and Security
Assigning an IP address and address • The IP address can be IPv4 (e.g.

prefix length to the router <ip-address/prefix-length> 10.10.10.1) or IPv6 format (e.g.
interface no address 10:10:10:10:10:10:10:10)
<ip-address/prefix-length> • Prefix length: IPv4 1–32;
IPv6 1–128
• You cannot define an IP address
if the router interface is bound
to a PPP port.
Specifying parameters for BFD bfd min-tx {100ms | 1s | 10s} • min-tx – minimum time interval
sessions min-rx {100ms | 1s | 10s} for periodic transmission of BFD
multiplier <multiplier-val> control packets
• min-rx – minimum interval for
periodic reception of BFD
control packets
• multiplier – detection time
multiplier: BFD session
detection time is calculated by
multiplying the negotiated
transmit interval by this value.
Binding router interface to SVI bind svi <port-number> • You can bind one SVI
logical port (predefined; see Service Virtual
Interface section in the Cards
and Ports chapter) to a router
interface.
• Enter no bind to unbind the
router interface.
Note: This command is available
only if the interface is not
loopback.
Binding router interface to PPP bind ppp <port-number> • Only one router interface can
port for PPPoE be bound to a PPP port.
• Enter no bind to unbind the
router interface.
Clearing router interface clear-statistics all

statistics clear-statistics ipv4 access-list
{in | out}
clear-statistics ipv4 traffic
clear-statistics ipv6 access-list
{in | out}
clear-statistics ipv6 traffic
ETX-2 Router 8-105

Enabling/disabling DHCP client dhcp You cannot enable DHCP (for IPv4)
no dhcp in the following cases:
• Router interface is bound to a
PPP port.
• IPv4 address is configured.
• Router interface is not
unnumbered.
• DHCPv6 is enabled.
•
Configuring DHCP client for the dhcp-client

router interface
Command in level dhcp-client
Providing client ID to DHCP server client-id id <string> You can specify an ID, or specify
client-id mac mac to indicate that the device
MAC address should be used as the
client ID.
Enabling or disabling DHCPv6 dhcpv6-client You can enable DHCPv6 client

client for the router interface no dhcpv6-client provided that the following
conditions exist:
• Router entity is Router # 1.
• There is no other DHCPv6 client
defined in the device.
• DHCPv4 is not enabled.
• The router interface is not
defined as loopback.
• The router interface is not
bound to a PPP port.
•
Enabling or disabling IPv6 ipv6-autoconfig Enter no ipv6-autoconfig to disable

autoconfiguration on router no ipv6-autoconfig IPv6 autoconfiguration.
interface
Configuring interface management-access {allow-all | • You can set management

management access allow-ping} access to allow-all for up to two
router interfaces.
• Enter no management-access
to remove management access
from router interface.
Configuring maximum allowed mtu <bytes> • Possible values: 1280–12,288

length of transmitted unit (in Default: 1500
bytes) Note: This command is available
loopback.
8-106 Router ETX-2

Assigning a name to the router name <interface-name>

interface no name
Displaying the summary of ACLs show access-list summary Refer to Access Control List (ACL)
bound to router interface in the Management and Security
Displaying router interface show statistics ipv4 access-list

statistic show statistics ipv4 traffic
show statistics ipv6 access-list
Displaying router interface status show status See Viewing Router Interface
Status.
Enabling or disabling sending of unreachables

ICMP unreachable messages, to no unreachables
notify that the destination
unicast address is unreachable
Removing VLAN assignment no vlan VLAN can be removed, only when

router interface is in non-active
state.
Note: This command is available
loopback.
Administratively enabling or no shutdown You can administratively enable the

disabling the router interface shutdown router interface only if one of the
following is true:
• The router interface is bound to
an administratively enabled SVI,
and the following are true:
• An IP address was assigned
via the address command.
• Flows have been defined to
and from the SVI, and are
administratively enabled.
• The router interface is bound to
a PPP port that is bound to an
administratively enabled SVI,
and the following are true:
• No IP address has been
assigned via the address
command.
• DHCP has not been enabled.
Using shutdown disables the
interface.
ETX-2 Router 8-107

Deleting a Router
You can delete a router if there are no router interfaces associated with it.
 To delete a router:
• At the config# prompt, enter:
no router <number>
Deleting a Router Interface
 To delete a router interface:

• At the config>router(<number>)# prompt, enter:
no interface <interface-num>
Viewing Router Interface Information

You can view information on each router interface by using the show summary-
interface command:
config>router(<number>)>show summary-interface
 To display the interface summary:

ETX-2>config>router(1)# show summary-interface
Router Interface: 1
Name: RI001
Admin:Up Oper: Up Bound to: svi 1
3.3.3.2/24 (manual) (preferred)
Router Interface: 3
Name: RI003
Admin:Up Oper: Up Bound to: svi 31
4.4.4.3/24 (manual) (preferred)

The above fields are:
Table 8-18. Router Interface Parameters
Field Description
number Unique number assigned to the router interface
Name Name of the router interface (alphanumeric string)
Admin Administrative status:

• up – ready to pass packets
• down
8-108 Router ETX-2

Field Description
Oper Operational status:

• down
• LLD – Lower Layer Down; down due to state of lower-layer
interface(s)
Bound to The port that the router interface is bound to
IP Addresses
IP Address/prefix IPv4 or IPv6 address and prefix length

length Note: Supported for DHCPv6
origin Origin of the IP address.

Possible origins are:
• other – for example, link local address
• manual – indicates that the address was manually configured to a
specified address
• dhcp – indicates an address that was assigned to this system by a
DHCP server
• link layer – indicates an address created by IPv6 stateless auto-
configuration
• random – indicates an address chosen by the system at random
status Status of the IP address.

Available statuses (from the IPv6 Stateless Address Autoconfiguration
protocol) are:
• preferred (default)
• deprecated
• invalid
• inaccessible
• unknown
• tentative
• duplicate
• optimistic
Viewing IPv6 Neighbors

You can view information on each each IPv6 neighbor by using the show
neighbor-table command:
config>router(<number>)>show neighbor-table
 To display the neighbor table:

ETX-2>config>router(1)# show neighbor-table
IPv6 Address MAC address State Interface
=============================================================================
1234:1234:1234:1234:1234:1234:1234:1234 01-01-01-01-01-01 reachable 1
1234:1234:1234:1234:1234:1234:1234:1234 01-01-01-01-01-01 incomplete 28
ETX-2 Router 8-109

FE80::200:E8FF:FE00:2A2B 00-00-e8-00-2a-2b stale 2

Table 8-19. IPv6 Neighbor Parameters
Field Description
IPv6 address
MAC address
State The Neighbor Unreachability Detection state for the interface when
the address mapping in this entry is used:
• reachable – confirmed reachability
• stale – unconfirmed reachability
• delay – waiting for reachability confirmation before entering
probe state
• probe – actively probing
• invalid – invalidated mapping
• unknown – state cannot be determined for some reason
• incomplete – address resolution is being performed
interface Router interface number
Viewing Routing Information

You can view all routing information or only information on dynamic or static
routes, for all IP addresses or for a specific IP address and prefix length of a
dynamic or static by using the show routing-table command:
config>router(<number>)>show routing-table [ address <IP-address/IP-mask> ]
[ protocol { dynamic | static } ]
 To display the routing table:

ETX-2>config>router(1)# show routing-table
IP Address/Prefix Length Next Hop Interface Protocol Metric
-----------------------------------------------------------------------------
0.0.0.0/0 172.17.92.1 1 Static 1
11.11.101.0/24 0.0.0.0 2 Local 0
22.22.202.0/24 0.0.0.0 3 Local 0
172.17.92.0/24 0.0.0.0 1 Local 0
IPv6 Address/Prefix Length via Next Hop Interface Protocol Metric
Table 8-20. Routing Parameters
Field Description
IP address/Prefix IPv4/IPv6 address and prefix length

Length
Next Hop Route entry next hop IP address
8-110 Router ETX-2

Field Description
Interface Router interface number
Protocol Source protocol:

• other
• local
• mngmnt
• icmp
• egp
• ggp
• hello
• rip
• isis
• esis
• ciscoigrp
• bbnspflgp
• idpr
• cisco-eigrp
• dvmrp
Metric Route entry metric
Viewing RIB
You can view the RIB (Routing Information Base) by using the command show rib.
This command is available in the CLI contexts for IPv4 or IPv6, at the router level:
config>router(<number>)#.
 To display the IPv4 RIB:

ETX-2>config>router(1)# show rib ipv4
* = Active Route
Network > Next Hop RI Proto Metric
=============================================================================
* 0.0.0.0/0 > 172.17.171.1 2 Static 1
* 3.3.3.0/24 > 0.0.0.0 1 Local 0
* 111.222.111.0/24 > 0.0.0.0 2 Local 0
 To display the IPv6 RIB:

ETX-2>config>router(1)# show rib ipv6
* = Active Route
Network > Next Hop RI Proto Metric
=============================================================================
* ::/0 > 11:11:11:11::1 1 Static 1
* 11:11:11:11::/64 > :: 1 Local 0
* abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd/126
> abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 1 Static 1
* fe80::/64 > :: 1 Local 0
ETX-2 Router 8-111

Table 8-21. RIB Field Descriptions
Field Description
Status Marks with a “*” an ‘Active Route’, i.e. route entry is forwarded to the
(Active FIB (Forwarding Information Base)
Route)
Network IPv4 or IPv6 network address (prefix and prefix length)

IPv4 prefix length can be 0–32; IPv6 prefix length can be 0–128.
Next hop Route entry next hop IP address
RI Local interface through which the next hop of this route should be
reached
Protocol Source protocol
Metric Route entry metric
Viewing Router Interface Status

You can view the router interface status by using the show status command:
config>router(<number>)>interface(<interface-num>)>show status
 To display the router interface status:

ETX-2>config>router(1)interface(1)# show status
Admin: up Oper: down
IP Addresses:
101.101.101.1/24 (DHCP) (preferred)
1234:1234:1234:1234:1234:1234:1234:1234/126 (manual) (preferred)
1234:1234:1234:1234:1234:1234:1234:1234/126 (link layer) (preferred)
IPv4 Default Router: 1.1.1.254
DHCP Client Information /*section appears if DHCP is enabled*/

Status: Holding Lease
Server: 10.110.110.110
Lease Obtained: 01-01-2010 00:00:01
Lease Expires: 10-01-2010 00:00:01
Lease Renewal: 05-01-2010 00:00:01
Lease Rebinding: 07-01-2010 00:00:01
Router: 101.201.1.111, 101.201.1.222
Static Routes: IP: 2.2.2.2 NH: 1.1.1.7
IP: 10.10.10.10 NH 1.1.1.8
TFTP Server: 2.2.2.2
Bootfile Name: path/filename
Host Name: Mao-Ze-Dong
DHCPv6 Client Information /*section appears if DHCPv6 is enabled*/

Server: 1234:1234:1234:1234:1234:1234:1234:1234
TFTP Server: 1234:1234:1234:1234:1234:1234:1234:1234
Filename: path/filename
8-112 Router ETX-2

Table 8-22. Router Interface Status Parameters
Field Description
Admin Administrative status:

• down
Oper Operational status:

• down
IP Addresses
IP Address/prefix IPv4 or IPv6 address and prefix length

length Note: Supported for DHCPv6
origin Origin of the IP address.

Possible origins are:
• other
• manual
• DHCP
• link layer
• random
status Status of the IP address.

Available statuses (from the IPv6 Stateless Address Autoconfiguration
protocol) are:
• preferred (default)
• deprecated
• invalid
• inaccessible
• unknown
• tentative
• duplicate
• optimistic
IPv4 Default Router IP address of the IPv4 default router
DHCP Client Information (Section appears only when DHCP is enabled.)
Status DHCP client operational status. Available options are:

• Holding Lease
• Not Holding Lease
• Failed to Obtain Lease
• Waiting for Lease
• Initializing
• No Lease Address In Use
ETX-2 Router 8-113

Field Description
Server Displays client server’s address
Lease Obtained Date and time when the DHCP lease was obtained
Lease Expires Date and time when the DHCP lease will expire, if not renewed
Lease Renewal Date and time when the device will try to renew the DHCP lease.
renewal time = (expired - obtained) * 0.5
If the lease last chance for renewal time passes, -- is displayed.
Otherwise, the next renewal time is displayed, as follows:
• Date and time, formatted like other date and time values in the
device (by default as dd mm-yyyy hh:mm:ss)
• If real time clock is not available, time in seconds since startup.
Lease Rebinding Date and time when the device will try to rebind the DHCP lease
Router List of default routers, in order of preference

If the first router is in use, (active) is displayed following its address.
The first router is not in use if:
• There is a different static default router.
• The DHCP default router is invalid, i.e., not on the device’s
networks.
Static Routes File to obtain from TFTP server, received by DHCP
TFTP Server IP address of TFTP server, received by DHCP
Bootfile Name File to obtain from TFTP server, received by DHCP
Host Name Host name, received by DHCP
DHCPv6 Client Information (Section appears only if DHCPv6 is enabled.)
Server (IPv6) Displays DHCPv6 server’s IP address
TFTP Server IP address of TFTP server, received by DHCPv6
Filename File to obtain from TFTP server, received by DHCPv6
Cannot delete; interface You tried to delete a router Disassociate router interfaces from
associated with the router entity that has router router.
interfaces associated with it.
Cannot add; IP address not legal
8-114 Router ETX-2

Cannot set address; DHCP You tried adding an IPv4 Disable DHCP.
enabled address when DHCP is
enabled.
Cannot set address; too many You tried adding an IP address, Delete one of the associated addresses
addresses already configured but the amount of IP before associating a new IP address.
addresses already reached its
limit.
Cannot set address; invalid You tried adding a multicast IP

address or an interface IPv4
address with prefix length 32
(, which is only allowed for
loopback interface).
When configuring static-route,
you tried to do one of the
following:
• Add a multicast IP network
address.
• Add an IP network address
when it was not allowed.
Use /31 prefix-length on non You tried adding an IPv4

point-to-point interface interface address with prefix
cautiously length 31.
Cannot set address; Router You tried adding an IP address Unbind the router interface from the
Interface bound to PPP port when the router interface is PPP port.
bound to a PPP port.
Cannot modify; activated router You tried modifying or Shut down the router interface and try
interface removing a bound port while again.
the router interface was
activated (no shutdown).
You tried adding, modifying, or
removing a VLAN while the
router interface was activated
(no shutdown).
Cannot enable; IPv4 address You tried enabling DHCP even

exists though manual IPv4 address
exists.
Cannot enable; DHCPv6 is You tried enabling DHCP even Disable DHCPv6.
enabled though DHCPv6 is enabled.
Cannot set; Router Interface You tried enabling DHCP while Unbind the router interface from the
bound to PPP port the router interface is bound PPP port.
to a PPP port.
OR
You tried enabling DHCPv6
client while router interface is
bound to PPP port.
ETX-2 Router 8-115

Cannot enable; DHCP client is You tried enabling DHCP relay Disable DHCP client.
enabled while DHCP client is enabled.
Cannot set; DHCPv6 client is You tried enabling DHCPv6 Remove existing DHCPv6 client.
already defined client when there is already
one defined in the device.
Cannot enable; DHCP (v4) is You tried enabling DHCPv6 Disable DHCPv4.
enabled while DHCPv4 is enabled.
Cannot set; Router Interface is You tried enabling DHCPv6 Associate DHCPv6 client with a router
loopback interface client while router interface is interface that is not defined as a
defined as loopback interface. loopback interface.
Cannot activate; must be bound You tried activating a router Bind the router interface to a loopback
to port interface, which is neither a interface or a port.
loopback interface nor bound
to a port.
Cannot activate; bound port in You tried activating the router

use by another router interface interface, while the bound
port is already in use by
another router interface.
Cannot activate; bound You tried activating the router

port+vlan in use by another interface that is bound to port
router interface + vlan, while bound pair
port+vlan is already in use by
another router interface.
Cannot activate; ip address is You tried activating the router

set interface bound to PPP port,
when IP address was set.
Cannot activate; dhcp is enable You tried activating the router

interface bound to PPP port,
when DHCP is enabled.
Cannot activate; PPP lower layer You tried activating the router
is not bound interface bound to PPP port,
when PPP lower layer port is
not bound.
8.9 Quality of Service (QoS)

The ETX-2 Quality of Service (QoS) parameters include the following profiles:
• Queue map profiles
• CoS map profiles
• Color mapping profiles
• Marking profiles
8-116 Quality of Service (QoS) ETX-2

• Bandwidth profiles
• Queue block profiles
• Queue group profiles
These profiles can be applied to the traffic flows to ensure the desired flow
prioritization.
Applicable Products
This feature is applicable to all ETX-2 products, with the following exceptions:
• Best effort queues are relevant only for ETX220A.
• The non-envelope policer coupling flag is relevant only for ETX220A.
• Multi-CoS flows and envelope policers are relevant only for ETX220A.
Standards
The following standards are supported:
• IEEE 802.1p
• IEEE 802.1Q
• MEF 10.3
Benefits
QoS allows you to optimize bandwidth, avoiding the need to allocate excessive
bandwidth to facilitate the necessary bandwidth for traffic at different
requirements of speed and quality.
Traffic Management
ETX-2 traffic management entities are called queue groups. They are configured
over physical ports. The queue groups consist of 2-level scheduling elements
(queue blocks) per port. The queue blocks consist of internal queues.
Additionally, shapers operate at per-scheduling-element level to shape traffic into
a required traffic profile (CIR, CBS or CIR/EIR, CBS/EBS).
Each flow is assigned to a queue block as its destination. Each queue block
includes scheduling queues in accordance with CoS delivery priorities. Flow
packets are mapped in the following ways to queues:
• Mapped explicitly to a specific queue
• Mapped to a queue according a queue mapping profile (p-bit or DSCP to
queue)
• Mapped according to the packet’s CoS, in case of bridge or ETP (set by CoS
mapping profile at the ingress), whereby CoS 7 is mapped to the lower
priority queue, and CoS 0 to the highest
ETX-2 Quality of Service (QoS) 8-117

Scheduling
ETX-2 supports a combination of traffic scheduling techniques, whereby
applications requiring low latency and jitter are mapped to Strict priority queues,
while other services are mapped to the remaining slots using weighted fair
queuing (WFQ) and best effort (BE):
• The Strict priority queues ensure minimal latency and jitter for the RT traffic,
even when a large amount of bursty data traffic is sent over the same uplink.
Strict priority traffic is always processed first, while flows mapped to the WFQ
slots are buffered until the strict priority queues are empty.
• The WFQ technique avoids scheduling starvation of lower priority queues and
ensures relatively fair allocation of bandwidth by sharing it among all flows. In
this manner, packets belonging to lower classes of service are not penalized
when higher priority queues are not empty and may still receive transmission
time. QoS-conformant scheduling is handled by assigning different weights to
the various queues instead of equally dividing overall bandwidth among all
active flows.
• BE (best-effort) queues transmit packets only if there are no packets in
higher level queues.
Congestion avoidance is provided by WRED profiles (see WRED Profiles).
Factory Defaults
See the following sections for each QoS type’s specific defaults.
Queue Mapping Profiles

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 between 0 and 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 treated when assigned to a specific priority value is
only generally defined and left to implementation. The general definitions are as
follows:
Table 11-24. User Priorities
User Priority Traffic Type
0 Best effort
1 Background
2 Spare
3 Excellent effort
4 Controlled load
5 Video
6 Voice
7 Network control

Queue mapping profiles are used to convert the following user priorities into
internal priority queues.
p-bit When ingress traffic is prioritized according to the 802.1p

requirements
Ip-dscp When ingress traffic is prioritized according to DSCP; for

both IPv4 and IPv6
Ip-precedence When ingress traffic is prioritized according to

IP precedence; for both IPv4 and IPv6
Class of Service When ingress traffic is mapped to an internal CoS (e.g p-bit
(CoS) or DSCP to CoS) at the Bridge port ingress, ETP subscriber
ingress, and flow that uses an envelope policer
For each profile, you have to define the queue mapping to map the user priority
values to the internal queue values. The internal queues are combined into a
queue profile, which can be assigned to a queue block.
Factory Defaults
Default Queue Mapping Profile

ETX-2 provides a default queue mapping profile named CosProfile1, which can be
used when the ingress traffic is prioritized according to the 802.1p requirements.
It is defined with classification p-bit, and the following mappings:
• Map p-bit 0 to queue 7.
There is also a predefined queue mapping profile named q-map-for-cos, which
can be used for multi-Cos flows when you wish to map CoS 0 to queue 0, CoS 1
to queue 1, etc.
Default Configuration for IP Precedence Classification

When a new queue mapping profile is created with classification IP precedence, it
contains the following mappings:


Default Configuration for DSCP Classification

When a new queue mapping profile is created with classification DSCP, it contains
the following mappings:
• Map p-bit 7 through 63 to queue 0.
Adding Queue Mapping Profiles

When you create a queue mapping profile, you specify the name and the
classification method (p-bit, IP precedence, or DSCP).
 To add a queue mapping profile:

1. Navigate to configure qos.
The config>qos# prompt is displayed.
2. Type:
queue-map-profile <queue-map-profile-name> classification
{p-bit|ip-precedence|ip-dscp|cos}
A queue mapping profile with the specified name and classification
method is created and the following prompt is displayed:
config>qos>queue-map-profile(<queue-map-profile-name>)$.
The mappings for the new profile are configured by default as described
in Factory Defaults.
3. Configure the queue profile mappings as described in Configuring Queue
Mappings.
Configuring Queue Mappings
 To configure queue mappings:

1. Navigate to config qos queue-map-profile <queue-map-profile-name> to
select the queue mapping profile to configure.
The following prompt is displayed:
config>qos>queue-map-profile(<queue-map-profile-name>)#
2. Map the user priorities to queue IDs as necessary:

 Classification p-bit or IP precedence:

map <0-7> to-queue <0-7>
 Classification DSCP:
 Classification CoS:
Examples
 To create and configure a queue mapping profile named QMapPbit with

classification p-bit:
• Map priority 0 to queue 3.
• Map priority 4 and 6 to queue 2.
exit all
configure qos queue-map-profile QMapPbit classification p-bit
map 0 to 3
map 4 to 2
map 6 to 2
exit all
 To display the configuration information for queue mapping profile QMapPbit:

ETX-2# configure qos queue-map-profile QMapPbit
ETX-2>config>qos>queue-map-profile(QMapPbit)# info detail
map 0 to-queue 3
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4..6 to-queue 2
map 7 to-queue 0
 To create and configure a queue mapping profile named QMapIPprec with

classification IP precedence:
• Map priority 2 and 3 to queue 3.
exit all
configure qos queue-map-profile QMapIPprec classif ip-precedence
map 2 to 3
map 3 to 3
exit all
 To display the configuration information for queue mapping profile QMapIPprec:

ETX-2# configure qos queue-map-profile QMapIPprec
ETX-2>config>qos>queue-map-profile(QMapIPprec)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2..4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0

 To create and configure a queue mapping profile named QMapDSCP with

classification DSCP:
exit all
configure qos queue-map-profile QMapDSCP classif ip-dscp
map 7 to 6
map 55 to 4
map 63 to 5
exit all
 To display the configuration information for queue mapping profile QMapDSCP:

ETX-2# configure qos queue-map-profile QMapDSCP
ETX-2>config>qos>queue-map-profile(QMapDSCP)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 6
map 8..54 to-queue 0
map 55 to-queue
4
map 56..62 to-queue 0
map 63 to-queue 5
 To create and configure a queue mapping profile named QMapCoS with

classification CoS:
• Map CoS 6–7 to-queue 0.
exit all
configure qos queue-map-profile QMapCoS classification cos
map 6..7 to-queue 0
map 3..5 to-queue 1
map 0..2 to-queue 2
exit all
CoS Mapping Profiles

CoS mapping profiles can be used at the following levels:
• Flow level — ingress Bridge port flows, ETP subscriber flows, and flows using
envelope policer (MEF 10.3 BW profiles)
• Ring level

Class of Service (CoS) mapping profiles map the following user priorities to
internal CoS values:
p-bit Relevant at flow and ring levels; when ingress traffic is

prioritized according to 802.1p requirements
ip-dscp Only relevant at flow level; when ingress traffic is

prioritized according to DSCP
ip-precedence Only relevant at flow level; when ingress traffic is

prioritized according to IP precedence
Note
If the flow from UNI to NNI is classified with one of the above classifications
(p-bit only, ip-dscp, or ip-precedence), Up MEP and customer-tag-excluded MEP
do not work and it is therefore recommended not to use them.
Internal CoS is used:

• To map a packet to a specific egress queue (fixed mapping: CoS 0 maps to
queue 0, CoS 1 maps to queue 1, etc.)
• By marking profiles to set p-bits of remarked packets (‘CoS to p-bit’ marking
profiles)
• By flows with MEF 10.3 envelope BW profiles to map traffic to the different
envelope ranks identified by CoS
Factory Defaults
By default, there are no CoS mapping profiles. When you create a CoS mapping
profile, it is configured as follows:
• Classification p-bit
• Mappings:
 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.
 Untagged to CoS 7, for profile assigned to multi-Cos flow in case of p-bit
mapping
 Non-IP to CoS 7, for profile assigned to multi-Cos flow in case of DSCP
mapping

Configuring CoS Mapping Profiles
 To define a CoS mapping 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-precedence | ip-dscp }]
Note that you can only configure classification p-bit for a CoS mapping
profile to be associated with a ring.
3. Map the user priority to a CoS value (user priority values 0–7 for p-bit and IP
precedence, 0–63 for the other priority types; CoS values 0–7):
map <0-7> to <0-7>
map <0-63> to <0-7>
4. If the CoS mapping profile is intended for use with a multi-Cos flow:
a. Define the mapping of untagged traffic in case of p-bit mapping:
map untagged to <0-7>
b. Define the mapping of non IP traffic in case of DSCP mapping:
map non-ip to <0-7>
Examples
 To create and configure a CoS mapping profile (for a flow or ring):

• Profile name: my-p-bit
• Classification: p-bit
• Map priority 6–7 to CoS 0.
exit all
configure qos cos-map-profile my-p-bit classification p-bit
map 6..7 to-cos 0
map 3..5 to-cos 1
map 0..2 to-cos 2
exit all
 To create and configure a CoS mapping profile for a multi-CoS flow:

• Profile name: p-bit-multi
• Classification: p-bit
• Map priority 0 to CoS 7.
.
.
• Map priority 7 to CoS 0.
• Map untagged traffic to CoS 0.
exit all
configure qos cos-map-profile p-bit-multi classification p-bit

untagged-map to-cos 0
exit all
Color Mapping Profiles

Color mapping profiles map p-bits or the drop eligible indicator (DEI) bit to packet
color:
• Color mapping profiles with classification type p-bit are used to map p-bit
values to green or yellow.
• Color mapping profiles with classification type DEI are used to map the DEI bit
to green or yellow as follows:
 DEI=0: Maps to green
 DEI=1: Maps to yellow
Color mapping profiles with classification type p-bit are configurable, whereas
color mapping profiles with classification type DEI are not configurable.
Color mapping profiles can be assigned to flows and rings.
Factory Defaults
By default, there is no color mapping profile. When a color mapping profile with
classification type p-bit is created, all the p-bit values are mapped to green.
Configuring Color Mapping Profiles
 To define a color mapping profile:

2. Define a color mapping profile according to classification type:
 P-bit classification:
a. Enter:
color-map-profile <color-mapping-profile-name> classification p-bit
b. Map the p-bits to a color as needed:
map <class-value> to {green|yellow}
 DEI classification:
color-map-profile <color-mapping-profile-name> classification dei
Example
 To create a color mapping profile kcolpb to map odd p-bit values to green, and
even to yellow:
exit all
configure qos
color-map-profile kcolpb classification p-bit
map 0 to yellow
map 2 to yellow
map 4 to yellow
map 6 to yellow
exit all

save
Marking Profiles
Marking profiles map the p-bit, IP precedence, DSCP, or CoS classifications to the
egress priority tags (p-bit)). The marking can also be done per color (green
and/or yellow), to support color re-marking, optionally specifying the Drop Eligible
Indicator (DEI) bit in the frame header.
Factory Defaults
ETX-2 provides a default non color-aware marking profile named MarkingProfile1,
which can be used when the ingress traffic is prioritized according to the 802.1p
requirements. It is defined with classification p-bit and method p-bit, and the
following markings:
• P-bit 0 => priority 0
• P-bit 1 =>priority 1
When a non color-aware marking profile is created, it has the same configuration
as MarkingProfile1.
Configuring Marking Profiles
 To define a marking profile and assign a priority mark to it:

2. Define the marking profile and assign a classification and method to it:
marking-profile <marking-profile-name>
[classification {p-bit | ip-precedence | ip-dscp |cos}] [method p-bit ]
[color-aware {none | green-yellow} [dei {always-green | always-yellow |
by-policer}]
To define a color-aware profile, specify color-aware green-yellow.
Note You must specify cos if the marking profile is intended for use with a multi-CoS
flow.
The dei parameter affects the Drop Eligible Indicator (DEI) bit in transmitted
frames as follows:
 always-green — Frames transmitted from the device are marked via the
DEI bit as not eligible to be dropped. In this case, the color-aware
parameter can be none or green-yellow.

 always-yellow — Frames transmitted from the device are marked via the
DEI bit as eligible to be dropped. In this case, the color-aware parameter
must be green-yellow.
 by-policer — Yellow frames transmitted from ETX-2 are marked via the DEI
bit as eligible to be dropped, and green frames transmitted from ETX-2
are marked as not eligible to be dropped. In this case, the color-aware
parameter can be none or green-yellow.
3. Map the user priority (and packet color, if it is a color-aware marking profile)
to a priority marking value according to the specific profile parameters
(classification and method), as follows.
At the config>qos>marking-profile(<profile-name>)$ prompt, enter:
 Non color-aware profile:
mark <user-priority> to <priority-marking>
 Color-aware profile:
mark <user-priority> {all|green|yellow} to <priority-marking>
Where user-priority value can be set to:
 0-7 – for marking profile configured with classification p-bit, ip-
precedence, or cos
And priority-marking value can be set to:
 0-7 – for marking profile configured with method p-bit
Bandwidth Profiles
ETX-2 supports the following bandwidth profiles:
Shaper profile Applied to queue group blocks
Policer profile Applied to flows to limit flow traffic, or to Ethernet ports

(non-envelope) to limit broadcast/multicast traffic
Envelope policer Specifies set of bandwidth profiles to apply to multi-CoS

profile flows
Policer aggregate Specifies non-envelope policer profile to apply to a group

of flows
You can control the egress bandwidth utilization by defining the committed
information rate (CIR) and committed burst size (CBS) in shaper and policer
profiles. You can also define the excessive information rate (EIR), excessive burst
size (EBS), and compensation in policer profiles.
CIR Defines the Committed Information Rate (CIR) for the

current profile. The CIR specifies a bandwidth with
committed service guarantee (“green bucket” rate).
CBS Defines the Committed Burst Size (CBS) for the current
profile. The CBS specifies the maximum guaranteed burst
size (“green bucket” size).

EIR Defines the Excess Information Rate (EIR). The EIR specifies
an extra bandwidth with no service guarantee (“yellow
bucket” rate).
EBS Defines the Excess Burst Size (EBS). The EBS specifies the
extra burst with no service guarantee (“yellow bucket”
size).
Compensation Defines the amount of bytes that the shaper or policer can
compensate for Layer-1 overhead (preamble and IFG) and
the overhead for the additional VLAN header in case of
stacking.
Color Aware You can specify the policer profile as color aware.
If the policer profile is specified as color aware, you can set the packet color as
follows:
1. If the arriving packet is marked green and the CIR bucket complies, the packet
color is set to green.
2. If the result of the preceding test is not true, then ETX-2 checks if the EIR
bucket complies (if the coupling flag is set, the CIR+EIR bucket is used):
 If the test result is true, the packet color is set to yellow.
 If the test result is false, the packet color is set to red (packet is
dropped).
Factory Defaults
The default for bandwidth-round-up is no bandwidth-round-up.
ETX-2 provides default bandwidth profiles, as specified in the following table.
Table 11-25. Default Bandwidth Profiles
Profile Type Shaper Policer (non-envelope)
Profile Name Shaper1 Policer1
cir ETX203AM, ETX203AX, 0

ETX205A: 999936
ETX220A: 9999872
cbs ETX203AM, ETX203AX, 0

ETX205A: 65535
ETX220A: 16000000
eir [not applicable] ETX203AM, ETX203AX,

ETX205A: 1000000
ETX220A: 10000000
ebs [not applicable] 32767
color-aware [not applicable] no color-aware
compensation 0 0

Profile Type Shaper Policer (non-envelope)
coupling-flag [not applicable] no coupling-flag

(ETX220A)
traffic-type [not applicable] all
When an envelope profile is created, it has the default values shown in the
following table.
Table 11-26. Default Envelope Profile
Parameter Value
compensation 0
cf-policy sharing-excess-bw
color-aware no color-aware
cos <n> bandwidth cir 0 cir-max 10000000 cbs 0 eir 0 eir-max 10000000 ebs 0
Envelope Bandwidth Profiles

An envelope profile as defined in MEF 10.3 contains a set of bandwidth profiles,
each of which has been assigned a unique rank from 1 (lowest) to 4 (highest).
Excess bandwidth from a higher rank can overflow to a lower rank to be shared,
either to the committed or to the excess bucket. In ETX-2, each profile
corresponds to a separate CoS. Figure 11-21 illustrates an envelope profile with
three CoSs. The coupling flags specify the path of overflow bandwidth. For the
CoS coupling flags (CFi), 0 = committed token bucket of the next lower rank, and
1 = excess token bucket of the same rank. For coupling flag 0, 0 = discard, and 1
= excess token bucket of the highest rank.
CIR3
EIR3
1
Rank #3 CBS 3 CF3
0
EBS3
CIR2
EIR2
1
Rank #2 CBS 2
CF 2
0
EBS2 Envelope
2
CIR
EIR1
1
Rank #1 CBS1 CF1
0
EBS1
0 0 1
CF
Figure 11-21. MEF 10.3 Bandwidth Profiles
When the envelope profile is assigned to a multi-CoS flow (see Multi-CoS Flows),
it enables the flow to share excess bandwidth. The bandwidth sharing can be

overflowed to the excess bucket (see Figure 11-22) or independent from the
excess bucket (see Figure 11-23).
CIR3
EIR3
1
3 3
CBS CF
EBS3
CIR2
EIR2
2
1
2
CBS CF
EBS2
2
CIR
EIR1
1
1
1
CBS CF
EBS1
Figure 11-22. Sharing Excess Bandwidth
CIRenv
EIRenv
CBS3 CF3
0
EBS3
CBS2 CF2
0
EBS2
CBS1 CF1
0
EBS1
Figure 11-23. Sharing Excess Bandwidth, Uncoupled from EIR/EBS
Configuring Granularity Rounding

When policer or shaper profiles are configured, the configured values are rounded
either up or down for granularity, according to whether the command
bandwidth-round-up has enabled rounding up or has disabled it. The rounded
value is stored in the device database, and is displayed when you display
information on the profile.
 To configure granularity rounding:

2. To enable rounding up to the higher granular value, type:

bandwidth-round-up
When policer or shaper profiles are configured, the configured value is
rounded to the higher granular value.
3. To enable rounding down to the lower granular value, type:
no bandwidth-round-up
When policer or shaper profiles are configured, the configured value is
rounded to the lower granular value.
If you change the behavior from rounding up to rounding down, then after device
reset, the rates that were actually configured are rounded up to the higher
granularity values.
Configuring Shaper Profiles

You can configure shaper profiles and apply them to queue group blocks as
needed.
ETX220A supports a single rate shaper at level 0 and level 1 queue blocks.
Adding Shaper Profiles

 To add a shaper profile:
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 (Kbps) and CBS bandwidth [cir <cir-kbit-sec>] [cbs <cbs-bytes>] Notes:
(bytes) bandwidth limits • CIR allowed values:
ETX203AM, ETX203AX,
ETX205A: 0–1,000,000
ETX220A: 0–10,000,000
(see Table 11-27 for the
shaper CIR granularity)
• CBS allowed values:
ETX203AM, ETX203AX,
ETX205A:
0, or 64–65535
ETX220A:
0, or 64–16777215
Compensating for Layer-1 overhead compensation <0–63> For pre-forwarding (ingress)
and additional VLAN tag (in bytes) traffic management, the
compensation is configurable in
the 0-63 range.
For post-forwarding (egress),
traffic management, the
compation is applied to level-0
shapers only. It can be set to 0
(data rate) or 20 (line rate).
Table 11-27. Shaper CIR Granularity
Device CIR > 130 Mbps (fast) CIR <= 130 Mbps
(slow)
ETX203AM, 256 Kbps 32 Kbps

ETX203AX,
ETX205A
ETX220A 512 Kbps 512 Kbps
Examples
 To create and configure a shaper profile named Shap2:

• CIR = 99,840 Kbps
• CBS = 32,000 bytes
• Compensation = 48
exit all
configure qos shaper-profile Shap2
bandwidth cir 99840 cbs 32000
compensation 48
exit all

Configuring Policer Profiles

This section explains functionality and configuration of non-envelope policer
profiles for traffic policing and rate limit. Policer profiles can be applied to flows
or Ethernet ports.
A port policer profile (also known as BUM filter (Broadcast, Unknown Unicast,
Multicast filter)), is supported by binding a policer BW profile to the Ethernet
port. This BW profile can only be configured with CIR and CBS bandwidth
parameters.
Whereas a policer BW profile bound to a flow relates to the entire traffic over
this flow, a policer BW profile bound to an Ethernet port can be configured to
limit Broadcast, Multicast, Unknown Unicast, and their combinations (see below).
You can configure the policer BW prile bound to Ethernet port to rate limit the
following traffic types:
Broadcast Broadcast traffic from the port is limited per the

configured CIR and CBS bandwidth limits..
Multicast Multicast traffic from the port is limited per the configured
CIR and CBS bandwidth limits.
Unknown Unicast Unknown Unicast traffic from the port is limited per the
configured CIR and CBS bandwidth limits. This is relevant
only for traffic into a bridge.
Broadcast + Aggregate traffic of Broadcast + Multicast from the port is

Multicast limited per the configured CIR and CBS bandwidth limits.
For ETX203AX, ETX203AM, and ETX205A, CIR and CBS
relate to Broadcast and Multicast traffic separately (CIR
and CBS for BC; and CIR and CBS for MC).
For ETX220A, CIR and CBS relate to the aggregate traffic
of Broadcast and Multicast.
Broadcast + Aggregate traffic of Broadcast + Multicast + Unknown

Multicast + Unicast from the port is limited per the configured CIR and
Unknown Unicast CBS bandwidth limits.
For ETX203AX, ETX203AM, and ETX205A, CIR and CBS
relate to Broadcast, Multicast, and Unkown Unicast traffic
separately (CIR and CBS for BC; CIR and CBS for MC; and CIR
and CBS for Unknown Unicast).
For ETX220A, CIR and CBS relate to the aggregate traffic
of Broadcast, Multicast, and Unknown Unicast.
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 (Kbps), CBS bandwidth [cir <cir-kbit-sec>] [cbs <cbs-bytes>] Notes:
(bytes), EIR (Kbps), and EBS (bytes) [eir <eir-kbit-sec>] [ebs <ebs-bytes>] • CIR & EIR allowed values:
bandwidth limits
ETX203AM, ETX203AX,
ETX205A:
0–1000000
ETX220A: 0–10000000
• CBS & EBS allowed values:
ETX203AM, ETX203AX,
ETX205A:
0, or 64–1000000
ETX220A:
0, or 64–2097151
• CIR can be set to zero only if
CBS is set to zero.
• EIR can be set to zero only if
EBS is set to zero.
• CIR + EIR must not exceed the
maximum available bandwidth.
• CBS should be greater than the
maximum frame size.
• For policer profiles that will be
attached to Ethernet ports to
limit broadcast/multicast
traffic, only the CIR and CBS
parameters are relevant (EIR
and EBS should be set to 0).
• A high-speed policer (CIR or
EIR >= 100,000 Kbps) cannot
be associated with more than
64 flows.
• The CIR and EIR granularity
depend on the configured
values, as described in
Table 11-28 and Table 11-29.
• The actual rate is rounded
down or up according to the
setting of
bandwidth-round-up.
• The CBS must be greater than
or equal to the CIR divided by
policer granularity.
Specifying if the policer profile is color-aware

color aware
Compensating for Layer-1 overhead compensation <0–63>

and additional VLAN tag (in bytes)

Specifying whether to check CIR+EIR coupling-flag Relevant only for color-aware

when determining packet color policer profile in ETX220A
Specifying the traffic type traffic-type {all | broadcast | multicast | Notes:

unknown-unicast | broadcast-and-multicast | • Traffic types other than all are
broadcast-and-multicast-and-unknown-unicast} relevant only for policer
profiles attached to ports.
• Aggregate profiles are
supported for ETX220A only.
Table 11-28. Granularity Rounding of Policer CIR/EIR for ETX203AM, ETX203AX, or ETX205A
Policer Type CBS/EBS <= 64,000 Bytes < 128,000 Bytes < 256,000 Bytes < 512,000 Bytes <
64,000 Bytes CBS/EBS <= CBS/EBS <= CBS/EBS <= CBS/EBS <=
128,000 Bytes 256,000 Bytes 512,000 Bytes 1,048,575 Bytes
Port policer, or 64 Kbps 128 Kbps 256 Kbps 512 Kbps 1 Mbps
flow policer with
CIR and EIR <
100,000 Kbps
Flow policer with 500 Kbps 1 Mbps 2 Mbps 4 Mbps 8 Mbps

CIR or EIR >=
100,000 Kbps
Note: The info command displays the CIR/EIR value:

• Rounded to 64 Kbps granularity for low-speed policers
• Rounded to 500 Kbps granularity for high-speed policers
Table 11-29. Granularity Rounding of Policer CIR/EIR for ETX220A
CBS CBS < 2 MB 2 MB <= CBS < 4 MB <= CBS < 8 MB <= CBS < 16 MB <= CBS <
IR (CIR, EIR) 4 MB 8 MB 16 MB 32 MB
IR < 10000 Kbps 10 Kbps 20 Kbps 40 Kbps 80 Kbps 160 Kbps

(10Mbps)
10000 <= IR < 100 Kbps 200 Kbps 400 Kbps 800 Kbps 1600 Kbps
100000 Kbps
(100Mbps)
100000 <= IR < 1 Mbps 2 Mbps 4 Mbps 8 Mbps 16 Mbps

1000000 Kbps
(1Gbe)
IR < 10000000 IR 10 Mbps 20 Mbps 40 Mbps 80 Mbps 160 Mbps

Kbps (10Gb)
Factor 1 2 4 8 16

Examples
 To create and configure a policer profile named Policer4:

• CIR = 50,000 Kbps
• CBS = 28,000 bytes
• EIR = 30,000 Kbps
• EBS = 20,000 bytes
• Compensation = 56
Note CIR and EIR are rounded down to 64K granularity, as this is a low-speed policer
with burst size < 64,000 bytes.
exit all
configure qos policer-profile Policer4
bandwidth cir 50000 cbs 28000 eir 30000 ebs 20000
compensation 56
exit all
 To display the configuration information for policer profile Policer4:

ETX-2# configure qos policer-profile Policer4
ETX-2>config>qos>policer-profile(Policer4)# info detail
traffic-type all
compensation 56
Configuring Policer Aggregates

You can define a policer aggregate that specifies a non-envelope policer profile
to apply to a group of flows. This is useful if you want to set bandwidth limits
that are divided among more than one flow.
Factory Defaults
By default, no policer aggregates exist. When a policer aggregate is created, it
has the following configuration:
• No assigned policer profile
• No assigned flows
• Rate sampling window (interval for sampling the associated flow statistics)
set to 15 minutes
Adding Policer Aggregates

2. Type:
policer-aggregate <policer-aggregate-name>
A policer aggregate with the specified name is created and the
config>qos>policer-aggregate(<policer-aggregate-name>)$ prompt is

displayed. The new policer aggregate parameters are configured by

default as described in Factory Default.
3. Configure the policer aggregate as described in Configuring Policer Aggregate
Parameters.
Configuring Policer Aggregate Parameters

1. Navigate to configure qos policer-aggregate <policer-aggregate-name> to
select the policer aggregate to configure.
config>qos>policer-aggregate(<policer-aggregate-name>)#
Note You assign flows to the policer aggregate in the flow level (see Configuring Flows
for details).
Assigning policer profile policer profile <policer-profile-name>
Specifying rate sampling window rate-sampling-window <1–30>

(minutes)
Displaying the associated flows show flows
Displaying statistics for the show statistics running

associated flows
Clearing the statistics for the clear-statistics

associated flows
Examples
 To create and configure a policer aggregate named Aggr1:

• Policer profile: Policer4 (created in policer profile example).
exit all
configure qos
policer-aggregate Aggr1
policer profile Policer4
exit all
Configuring Envelope Profiles

This section explains how to configure envelope profiles, to apply to multi-Cos
flows per MEF 10.3.
Adding Envelope Policer Profiles

2. Type:
envelope-profile <envelope-profile-name>

An envelope profile with the specified name is created and the following
prompt is displayed:
config>qos>envelope-profile(<envelope-profile-name>)$
The new envelope profile parameters are configured by default as
described in Factory Defaults.
3. Configure the envelope profile as described in Configuring Envelope Profile
Parameters.
Configuring Envelope Profile Parameters

1. Navigate to configure qos envelope-profile <envelope-profile-name> to
select the envelope profile to configure.
The config>qos>policer-profile(<envelope-profile-name>)# prompt is
displayed.
Defining policy for excess cf-policy {sharing-excess-bw | uncoupled-bw-sharing} • sharing-excess-bw – Excess

bandwidth sharing bandwidth is shared to excess
token bucket (see Figure 11-22).
Selecting this parameter
automatically sets coupling-flag-0
to 0, and sets each CoS coupling
flag to 1.
• uncoupled-bw-sharing – Excess
bandwidth is shared independently
from EIR/EBS (see Figure 11-23).
Selecting this parameter
automatically sets coupling-flag-0
to 0, and sets each CoS coupling
flag to 0.
If you enter no cf-policy, you can
configure coupling-flag-0; each CoS
coupling flag determines the
bandwidth sharing.
Specifying if the envelope color-aware

profile is color aware
Specifying the compensation compensation <value> Possible values: 0–63

(bytes)

Specifying the CIR (Kbps), CBS cos <value> bandwidth [cir <cir-kbit-sec>] • Range for cos value is 0–7; you can
(bytes), EIR (Kbps), and EBS [cir-max <cir-max-kbit-sec>] [cbs <cbs-bytes>] define up to four cos values in an
(bytes) bandwidth limits, for a [eir <eir-kbit-sec>] [eir-max <eir-max-kbit-sec>] envelope profile.
particular CoS [ebs <ebs-bytes>] [coupling-flag <coupling-flag>] • Range for <cir-kbit-sec>,
<cir-max-kbit-sec>, <eir-kbit-sec>,
and <eir-max-kbit-sec>:
0–10000000 (0–10 Gbps)
• Range for <cbs-bytes>,
<ebs-bytes>:
0–2000000 (0–2Mbytes)
• <cir-max-kbit-sec> must be greater
than or equal to <cir-kbit-sec>.
• <eir-max-kbit-sec> must be greater
than or equal to <eir-kbit-sec>.
• coupling-flag controls the path of
overflow tokens: 0=overflow to
committed token bucket, 1=
overflow to excess token bucket.
Specifying path of overflow coupling-flag-0 <value> <value> is 0–1:

bandwidth (see CF0 in 0=discard, and 1=excess token bucket
Figure 11-21) of the highest rank
Queue Block Profiles

In order 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 0–7, 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.
 WFQ (weighted fair queuing) – If one port does not transmit, its unused
bandwidth is shared by the ‘transmitting’ queues according to the
assigned weight. WFQ frames are transmitted only after transmission of
any frames associated with Strict queues is completed.
 BE (best effort) – lowest priority queue(s). One or both of the lowest
queues (Queue 6 and/or Queue 7) in a level 0 queue block can be
configured as BE. Packets in BE queues are transmitted only if there are
no packets in the WFQ or Strict queues.
 Strict BE – When a BE queue is defined, it is strict in relation to the
queues beneath it.
• Depth (queue size), in bytes.

Factory Defaults
ETX-2 provides a default queue block profile named DefaultQueue1, which
defines queues 0–7 as follows:
• Congestion avoidance – WRED profile corresponding to queue
• Scheduling method – WFQ, with weight set to 100
• Depth – 49,152
Adding Queue Block Profiles

This section explains how to define queue block profiles.
 To add a queue block profile:

2. Type:
queue-block-profile <queue-block-profile-name> [number-of-queues
<number>]
A queue block profile with the specified name, and number of queues, is
created, and the following prompt is displayed:
config>qos>queue-block-profile(<queue-block-profile-name>)$
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.
Specifying WRED profile that congestion-avoidance wred profile wred-profile-name – name of predefined wired
provides congestion avoidance policy <wred-profile-name> profile.

Specifying queue depth (in bytes) depth <value> Possible values: 64–1048576 for ETX-2 1GbE port;
64-8380416 for ETX220A 10GbE port
Notes:
• If queue depth is configured to below 64, it is
automatically rounded up to 64 bytes.
• The queue depth that you configure might be
changed by ETX-2 due to granularity (see
Table 11-30 for ETX203AM, ETX203AX, or
ETX205A; Table 11-31 for ETX220A). After you
configure the queue depth, it is recommended to
use info detail to see the actual value
• A queue contains 511 buffers, therefore it is
possible for the queue to be full when every
buffer is in use, even if the queue size has not
reached the maximum. This is more likely to
happen in the case of relatively small frame sizes.
Setting scheduling method scheduling { strict | wfq <weight>| The WFQ weight range is 3–1000
best-effort} Strict queues must have queue indices lower than
WFQ or best-effort queues, and WFQ queues must
have queue indices lower than best-effort queues.
Table 11-30. Queue Depth Granularity for ETX203AM, ETX203AX, and

ETX205A
Entered Via CLI Granularity
0–1024 64
1025–16383 1024
16384–262143 16384
262144–1048576 262144
Table 11-31. Queue Depth Granularity for ETX220A
Entered Via CLI Granularity
0–65535 64
65536–131071 128
131072–262143 256
262144–524287 512
524288–1048575 1024
1048576–2097151 2048
2097152–4194303 4096
4194304– 8380416 8192

Examples
 To create and configure a queue block profile named QBlockProf1:

• Queue 0 set to strict scheduling and depth 524,288
• Queue 1 set to strict scheduling and depth 212,992
• Queues 2 and 3 set to WFQ scheduling with weight 75
• Queues 6 and 7 set to Best Effort and depth 49,152
exit all
configure qos queue-block-profile QBlockProf1
queue 0
scheduling strict
depth 524288
exit
queue 1
scheduling strict
depth 212992
exit
queue 2
scheduling wfq 75
exit
queue 3
scheduling wfq 75
exit
queue 6
scheduling best-effort
depth 49152
exit
queue 7
scheduling best-effort
depth 49152
exit all
Queue Group Profiles

In order to facilitate congestion management, you can sort traffic by applying
queue group profiles. ETX220A supports two levels of queue groups.
Factory Defaults
ETX-2 provides a default queue group profile named DefaultQueueGroup,
configured as shown:
ETX-2# configure qos queue-group-profile DefaultQueueGroup
ETX-2> config>qos>queue-group-profile(DefaultQueueGroup)# info
detail
queue-block 1/1
name "Level1QueueBlock"
profile "Scheduling1"
no shaper
exit
queue-block 0/1

profile "DefaultQueue1"
bind queue 0 queue-block 1/1
shaper profile "Shaper1"
exit
queue-block 0/2
exit
Adding Queue Group Profiles
 To add a queue group profile:

2. Type:
queue-group-profile <queue-group-profile-name>.
A queue group profile with the specified name is created and the
following prompt is displayed:
config>qos>queue-group-profile(<queue-group-profile-name>)$
The queue group profile parameters are configured by default as
described in Factory Defaults.
3. Configure the queue group profile as described in Configuring Queue Group .
Configuring Queue Group Parameters

 To configure a queue group profile:
1. Navigate to config qos queue-group-profile <queue-group-profile-name> to
select the queue group profile to configure.
The config>qos>queue-group-profile(<queue-group-profile-name>)#
prompt is displayed.
2. Select a queue block in level 0 or 1 to configure:
queue-block 0/<1–31>
queue-block 1/1
config>qos>queue-group-profile(<q-grp-profile-name>)>queue-block(<level/ID>)#
4. If you wish to configure another queue block, type exit to return to the queue
group profile context, and start again at step 2.
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>

Note: Only for queue blocks in
level 0, for ETX203AM, ETX203AX,
or ETX205A
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.
You cannot use the bind command if the queue group contains a single
queue block in level 0.
Assigning High-Scale Queue Group to Ports

By default, in ETX220A, 10GbE ports 4/1 and 4/2 are assigned high-scale queue
groups and 1GbE ports 1/1 and 1/2 are assigned queue groups, with 32 queue
blocks each.
A device-level configuration parameter is provided, enabling you to switch the
assignment of up to 79 blocks of the high-scale queue groups to 1GbE ports 1/1
and 1/2 in either Network mode or User mode (the default), and the queue
groups having 32 queue blocks to 10GbE ports 4/1 and 4/2 (; in this case 1/1 and
1/2 would be assigned 79 queue blocks each).
This change is supported under the following conditions and limitations:
• The current high-scale queue group does not use more than 32 queue blocks.
It is the user’s responsibility to shut down these flows.
• The change involves some traffic hit.
 To configure high-scale queue group mapping:
2. Type:
hs-queue-group-mapping {slot-4|slot-1}.
The default is slot-4.
Following configuration, reboot the device by typing admin reboot.
Examples
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
Note Queue blocks 1/1 and 0/2 are automatically created.

exit all
configure qos queue-group-profile QGroupProf1
queue-block 0/1
profile QBlockProf1
shaper profile Shap2
exit all
 To display the configuration information for queue group profile QGroupProf1

ETX-2# configure qos queue-group-profile QGroupProf1
ETX-2>config>qos>queue-group-profile(QGroupProf1)# info detail
queue-block 1/1
name "Level1QueueBlock"
profile "Scheduling2"
exit
queue-block 0/1
profile "QBlockProf1"
shaper profile "Shap2"
exit
queue-block 0/2
exit
WRED Profiles
The ETX-2 traffic management engine employs a weighted random early discard
(WRED) mechanism for intelligent queue management and congestion avoidance.
The WRED algorithm monitors the fill level of each queue and determines
whether an incoming packet should be queued or dropped, based on statistical
probabilities.
Applicable Products
Congestion control policy is defined by:
• Tail drop for green packets – Packets are queued if there is room in the
queue, and are dropped if the queue is full.
• WRED profile for yellow packets
WRED profiles include the following parameters:
Maximum drop A percentage of the maximum threshold queue size that

probability defines the drop probability
Minimum Set to a percentage of the maximum queue depth. If a

threshold packet is queued and the queue size is between 0 and the
minimum threshold, the packet is admitted.

Maximum Set to a percentage of the maximum queue depth. If a

threshold packet is queued and the queue size is between the
minimum threshold and the maximum threshold, the
packet is dropped according to the drop probability of the
particular queue size.
Probability Set to a percentage of the maximum threshold queue size

that defines the drop probability
The following graph illustrates congestion control in ETX-2.

WRED profile for
Drop yellow packets
probability (%)
100%
Tail drop for
green packets
Queue depth
Min Max 100% (% of maximum)
threshold threshold
Figure 11-24. Congestion Control
There are eight WRED profiles available, named WREDProfile0 through

WREDProfile7. They are bound to the internal queues automatically: WREDProfile0
is bound to queue 0, WREDProfile1 is bound to queue 1, etc. You cannot delete
the WRED profiles, and you cannot add more WRED profiles. The binding of the
profiles to the queues is set and cannot be changed, but you can change the
profile parameters. You can view the assignment of WRED profiles to queues via
the info command in the queue block profile level.
Factory Defaults
There are eight WRED profiles available, named WREDProfile0 through
WREDProfile7, bound to the corresponding queues.
Configuring WRED Profiles
 To configure WRED profiles:

1. Navigate to configure qos and type wred-profile WREDProfile<n> where n is 0
through 7.
The config>qos>wred-profile(WREDProfile<n>)# prompt is displayed.
2. Enter:
color yellow min <min-threshold> max <max-threshold> [probability
<max-probability>]
 min-threshold – queue usage minimum threshold in percentage, 0–100

 max-threshold – queue usage maximum threshold in percentage, 0–100

 max-probability – percentage of packets to be dropped when the queue
usage reaches the maximimum limit
Note You can configure the parameters for the color yellow only.
Example
 To configure WRED profile 4:

• Minimum threshold 64
• Maximum threshold 100
• Probability 50
exit all
configure qos wred-profile WREDProfile4
color yellow min 64 max 100 probability 50
exit all
save
 To display the configuration information for WRED profile 4:

ETX-2 # configure qos wred-profile WREDProfile4
ETX-2 >config>qos>wred-profile(WREDProfile4)# info detail
color yellow min 64 max 100 probability 50

Chapter 9
Timing and
Synchronization
This chapter describes timing and synchronization features:
• 1588v2 Timing
• Clock Selection
• Date and Time
• Daylight Saving Time
• GNSS Receiver
9.1 1588v2 Timing

ETX2 supports IEEE 1588v2 Precision Time Protocol for distribution of
synchronization signals over packet-switched networks.
Applicable Products
This feature is applicable to ETX205A and ETX220A with PTP options, with the
following conditions:
• The following 1588v2 entities are supported by ETX205A and ETX220A:
 Standalone slave clock
 Standalone master clock (only for ETX205A with GNSS option)
 Boundary clock
• For G.8275.1, the PTP port limits are as follows:
 PTP ports with master role per device:
 ETX205A: Up to 6
 ETX220A: Up to 13
 PTP ports with slave role per device (ETX205A, ETX220A): Up to 2
• <slot> is relevant for ETX220A.
Standards
IEEE 1588 Precision Time Protocol
ETX2 1588v2 Timing 9-1

Chapter 9 Timing and Synchronization Installation and Operation Manual
ITU-T G.8265.1 Precision Time Protocol Telecom Profile

ITU-T G.8275.1 Precision Time Protocol Telecom Profile
ITU-T G.8273.2 Telecom Boundary Clock (T-BC) Specification
Benefits
The Precision Time Protocol (PTP), defined in the IEEE 1588 standard, is a
high-precision time protocol for synchronization of clocks over a PSN. PTP is
beneficial for applications that recover or distribute timing information.
Best Master Clock Algorithm (BMCA) improves clock synchronization.
PTP Protocols
G.8265.1 is an end-to-end protocol based on IP packets. The synchronization
message rate and announce rate are negotiated between the slave and master.
The G.8265.1 protocol is used to obtain frequency and time.
G.8275.1 is a point-to-point protocol based on Layer-2 multicast messages. There
is no signaling phase; the message rate is always 16 PPS and the announce rate is
8 PPS. The G.8275.1 protocol is used to obtain time rather than frequency. It
obtains frequency from SyncE to get a more accurate time. The reference time is
taken from the CSM source if it is PRC; otherwise from the 1588v2 frequency.
1588v2 Entities
ETX2 supports the following 1588v2 entities:
Standalone slave Recovers the clock signal from master clocks
Boundary clock Transfers time of day (ToD) and frequency from a remote
master clock to one or more slave clocks. The boundary
clock is implemented as a back-to-back master and slave
clock.
Standalone master Distributes frequency and frequency/time information to

remote slaves. Standalone master is the only mode
available if there is GNSS (relevant for ETX205A only), and
is not available if there is no GNSS.
Note
Only IPv4 addresses are supported in the timing/synchronization messaging.
PTP Port
When a 1588v2 entity acts according to G.8275.1, you need to configure a PTP
port entity for each clock entity. The PTP port has a provisioned state that you
configure, as well as an actual state. The provisioned state can be one of the
following:
Slave Acts as the time source of ETX2
9-2 1588v2 Timing ETX2

Installation and Operation Manual Chapter 9 Timing and Synchronization
Master Provides the distribution path for the device time
The actual state can be one of the following:

• Slave (one per device)
• Master
• Passive – neither master nor slave
Best Master Clock Algorithm (BMCA)

ETX2 uses Best Master Clock Algorithm (BMCA) to select the best clock from the
ports provisioned as slave. The selection is done according to port priority and
quality level received in announce messages.
The actual state of the provisioned slave port that is selected as the best clock is
set to slave. The actual state of the provisioned slave ports not selected is set to
passive.
Under G.8275.1, BMCA is supported over two PTP Slave Ports only. Automatic PTP
port state settings are not supported, and therefore G.8275.1 is not applicable
over G.8032 Ring or RSTP topologies.
Slave Clock
The standalone slave clock complies with G.8265.1 or G.8275.1. The slave clock
complies with the standard G.8265.1 Telecom Profile 1 (E2E), as well as
Symmetricom Telecom-2008, when working according to G.8265.1.
G.8265.1
The G.8265.1 slave clock can work in one-way mode, where it receives only
frequency from up to two IEEE 1588 master clocks, or in two-way mode (full
synchronization), where it receives frequency and time. When the master clock
grants signal transmission it notifies the slave clock of the master clock quality
level and source port identification, then periodically transmits synchronization
signals.
The slave clock works in the following recovery modes:
Time (also The slave uses its regenerated frequency to reconstruct

referred to as the remote clock, or uses a high-quality clock (PRC/PRS)
Hybrid) from the clock domain. Therefore, the time accuracy
depends on the quality of the reconstructed frequency;
noise in the frequency generation impacts the time
accuracy.
Frequency The slave reconstructs the remote clock using Sync

messages and delay request/response sent from master to
slave. Time-related status and alarms, as well as time
indication over the ToD interface, are not supported.
Frequency and The slave provides frequency information and time

Time information as described above. As the slave uses the
frequency for time recovery, a high-quality reference clock
usually improves the time recovery, except in the case of
network asymmetry.

1588v2 traffic is transmitted only via Ethernet port 1.
G.8275.1
The G.8275.1 slave clock receives frequency from one or more IEEE 1588 master
clocks that periodically transmit synchronization signals.
The slave clock works in time (also referred to as hybrid) recovery mode. The slave
uses both Sync and Delay messages to reconstruct the remote clock, and takes
the reference frequency is taken from the clock domain (same the G.8265.1 slave
in hybrid mode).
G.8273.2 clock specification supports G.8275.1.
Boundary Clock
The boundary clock is defined in ETX2 as a back-to-back master and slave clock
sharing the same IP address and PTP domain. The slave can be a G.8265.1 or
G.8275.1 entity, and the master can be a G.8265.1 or G.8275.1 entity, or it can be
a dual mode master that supports both G.8265.1 and G.8275.1.
The boundary clock performs the following tasks:
• The local slave recovers reference ToD and frequency from a remote master.
• The local master uses the local slave recovered ToD as its reference ToD.
• The local master uses the local slave recovered frequency as its reference
frequency.
Master Clock (Standalone)

The standalone master is available only for ETX205A with GNSS, and is the only
mode available with GNSS. The master distributes timing information to up to
64 slaves.
The master clock receives frequency and time information as follows:
• Frequency from the selected clock (system clock)
• Time of Day (ToD) from the GNSS
The standalone master clock can comply with G.8265.1 or G.8275.1, or it can
function as a dual mode master, also called a Distributed PTP Grandmaster
(DISTRIBUTED GM®), which supports PTP and Sync-E Time and Frequency
distribution. PTP distribution is based on both G.8265.1 and G.8275.1.
Forwarding
G.8265.1
You need to configure the following for the G.8265.1 clock entities to function
correctly:
• Corresponding SVI
• Corresponding flows
• Corresponding router interface. For the G.8265.1 boundary clock, the SVI
corresponding to the router interface must be connected via flow to a bridge
port. For the G.8265.1 master standalone clock, the SVI corresponding to the

router interface must be connected via flow to a bridge port if using more than
one Ethernet port.
Note The G.8265.1 standalone master clock can forward over a ring.
In order to communicate with the remote master of the G.8265.1 boundary clock,
a peer must be defined with the remote master IP address; additionally, if the
remote master is not in the same subnet as ETX2, a static route must be
configured to define how to reach the remote master.
G.8275.1
1588v2 traffic for PTP ports is transmitted and received by the 1588 entity
to/from an Ethernet port. You need to configure the following for the G.8275.1
clock entities to function correctly:
• Corresponding SVI
• Corresponding PTP port
• Corresponding flows. The traffic from the Ethernet port to the SVI port should
be classified as untagged. The traffic from the SVI port to the Ethernet port
should be classified to match all packets.
Dual Mode Master

You configure a dual mode master, also called a Distributed PTP Grandmaster
(DISTRIBUTED GM®), by configuring a G.8265.1 master entity and a G.8275.1
master entity:
• Any configuration change to the dual mode master (Grandmaster) requires
that you first remove and then add the G.8265.1 master entity.
• The two masters must be configured with different PTP clock domains.
• Each master can support different 1588 message rates. A G.8265.1 master
supports message rates per slave negotiation, and a G.8275.1 master supports
the standard sync rate of 16 PPS.
Factory Defaults
By default, there is no configured master or slave clock.
Configuring PTP Ports

You need to configure a PTP port entity for each G.8275.1 clock entity.
 To configure a PTP port:

1. For ETX205A: Navigate to configure system clock ptp-port 1 g.8275-1 port
<port>.
The config>system>clock>ptp-port(1)>port (<port>)# prompt is displayed.
2. For ETX220A: Navigate to configure system clock ptp-port 0/1 g.8275-1 port
<port>.

The config>system>clock>ptp-port(0/1)>port(<port>)# prompt is

displayed.
Configuring asymmetry asymmetry-correction

correction to compensate <nano-sec>
for possible network
asymmetry
Binding SVI to port bind svi <port-number>
Specifying which mac {01-1b-19-00-00-00 | Layer-2 IEEE 1588 packets have destination
destination MAC address to 01-80-c2-00-00-0e} MAC address 01-1B-19-00-00-00 or
use 01-80-C2-00-00-0E
Setting port priority priority <value> Priority is used when selecting the best
source from the PTP ports that are
provisioned as slaves.
Provisioning PTP port state state {master | slave | auto | master – distributes time
auto-no-slave} slave – provides time source
auto – reserved for future use
auto-no-slave – reserved for future use
See Configuring PTP Ports for more details
on the PTP port state.
Viewing PTP port status show status
Viewing PTP port statistics show statistics running
Administratively enabling no shutdown Using shutdown disables the port.

port
Configuring the Slave Clock

The slave clock is configured in the clock recovered 1 ptp level for ETX205A; clock
recovered 0/1 ptp level for ETX220A, specifying g.8275-1 if you are configuring a
G.8275.1 slave clock. Additionally, for G.8275.1 you need to configure PTP ports.
For examples of configuring G.8265.1 and G.8275.1 slave clocks, see Configuring
Slave Clock and Configuring Boundary Clock.
 To configure the recovered clock:

1. For ETX205A: Navigate to configure system clock recovered 1 ptp [g.8275-1].
The config>system>clock>recovered(1)# prompt is displayed.
2. For ETX220A: Navigate to configure system clock recovered 0/1 ptp
[g.8275-1].
The config>system>clock>recovered(0/1)# prompt is displayed.

Configuring clock quality clock-quality log-variance

<value>
Configuring IP address ip-address <ip-address>
Defining master recovered master <id> Possible values: 1–2

clock See the commands in the master level
below.
Configuring multicast multicast <ip-address>

IP address
Specifying the peer device peer <peer-number>

that transmits the clock
signal
Defining Telecom Profile profile-type

{telecom-end-to-end |
telecom-peer-to-peer}
Setting precision time ptp-domain <number> Recommended values:

protocol (PTP) domain 4–23 – for 8265.1
24–43 – for 8275.1
Possible values: 0, 4-127
Default: 4 for 8265.1; 5 for 8275.1
Setting clock recovery recovery-mode { frequency | • frequency – frequency only

mode time-frequency | time } • time-frequency – time and frequency
(allowed only in two-way mode; see
description of delay-respond in master
level.)
• time – Hybrid mode (allowed only in
two-way mode; see description of
delay-respond in master level.)
Defining whether revertive

recovered clock is revertive
Defining amount of time wait-to-restore <seconds> Possible values: 0–720

that previously failed clock
must be fault free in order
to be considered available
Clearing network metrics clear-network-metrics See Viewing Clock Recovery Metrics.

{master-to-slave |
slave-to-master | all}
Viewing network metrics show network-metrics See Viewing Clock Recovery Metrics.
Displaying status show status Displays the recovered clock status,

including master/slave
Administratively enabling no shutdown Using shutdown disables the recovered

recovered clock clock.

Commands in level master
Specifying the requested announce [rate { 16sec | 8sec | The allowed range for grant-period is
rate for announce 4sec | 2sec | 1sec | 500msec | 60–1000 (default 300)
messages 250msec | 125msec }
[minimum-expected { 16sec |
8sec | 4sec | 2sec | 1sec |
500msec | 250msec |
125msec }]
[grant-period <grant-period>
Configuring asymmetry asymmetry-correction

correction to compensate <nano-seconds>
for possible asymmetry
between the slave and the
grandmaster
Configuring port associated clock-identity clock-id <id> If this is not configured, by default a
with clock port [<slot>/]<number> standard clock ID is generated.
Specifying if recovered delay-respond [rate {16pps | The recovered clock works in one-way mode
clock works in one-way or 32pps | 64pps | 128pps }] if no delay-respond is entered. It works in
two-way mode, and [minimum-expected { 16pps | two-way mode if delay-respond is entered
desired rate if applicable 32pps | 64pps | 128pps }] with parameters.
[grant-period <grant-period>] The allowed range for grant-period is
60–1000 (default 300).
Configuring network type network-type { automatic |

dsl }
Specifying the peer device peer <peer-number>

that transmits the clock
signal
Setting priority priority <value>
Setting quality level quality-level { prc | ssu-a | The quality level values are according to the
ssu-b | type1-sec | type1-dnu | network type.
type1-ssm-based }
quality-level { prs | stu | st2 |
tnc | st3e | st3 | smc | st4 | dus
| type2-ssm-based | prov }
Specifying the requested sync [rate { 16pps | 32pps | The allowed range for grant-period is
rate for synchronization 64pps | 128pps }] 60–1000 (default 300).
messages [minimum-expected { 16pps |
32pps | 64pps | 128pps }]
[grant-period <grant-period>]
Clearing measured clear-measured-statistics

statistics

Displaying statistics show statistics running Displaying the 1588v2 statistic counters
Displaying measured show measured-statistics Displaying the measured rates of the

statistics received 1588v2 messages
Administratively enabling no shutdown Using shutdown disables the master clock.

master
Configuring the Master Clock

The master clock is configured in the clock master 1 ptp level for ETX205A; clock
master 0/1 ptp level for ETX220A, specifying g.8275-1 if you are configuring a
G.8275.1 master clock. Additionally, for G.8275.1 you need to configure PTP ports.
For examples of configuring G.8265.1 and G.8275.1 master clocks, see Configuring
Boundary Clock and Configuring Master Clock.
Note When configuring a boundary clock, the slave clock must be configured before the
master clock.
 To configure the master clock:

1. For ETX205A: Navigate to configure system clock master 1 ptp [g.8275-1].
The config>system>clock>master(1)# prompt is displayed.
2. For ETX220A: Navigate to configure system clock master 0/1 ptp [g.8275-1].
The config>system>clock>master(0/1)# prompt is displayed.
Defining the 1588v2 distributed-mode {frequency | In frequency mode, the master transmits sync and
message exchange mode time-frequency} announce messages to slaves.
In time-frequency mode, the master transmits
sync, announce, and delay response messages to
slaves.
Defining the PTP domain domain-number <number> Recommended values:

4–23 – for 8265.1
24–43 – for 8275.1
Possible values: 0, 4-127
Default: 4 for 8265.1; 5 for 8275.1
Note: A domain consists of one or more PTP
devices (masters or slaves) communicating with
each other according to PTP requirements. For
correct distribution of timing signals, a 1588v2
master and slaves operating with it must belong to
the same PTP domain.
Defining the master IP ip-address <address> The IP address must be the same as the IP address
address of the dedicated router interface.

Defining remote slave slave <ip> See the commands in the slave level below.
Defining maximum number maximum-slaves <number> Possible values: 1–64

of slaves
Enabling statistic collection pm-collection no pm-collection resets statistic counters and

stops further collection of performance monitoring
data.
Defining Telecom Profile profile-type {telecom-end-to-end |

telecom-peer-to-peer}
Defining the sync-rate { 16pps | 32pps | 64pps | All slaves within the domain must use the same
synchronization message 128pps } message rate.
rate
Selecting Tx clock domain tx-clock {domain <1>}
Displaying status of master show status

clock
Enabling the master clock no shutdown shutdown disables the master clock.
Displaying statistics for show statistics running

master clock
Clearing statistics for clear-statistics

master clock
Commands in level slave
Displaying slave status show status
Displaying statistics for show statistics running

slave clock
Viewing Clock Recovery Metrics

You can display the network performance metrics of the recovered timing. The
metrics apply to the network packet delay variation (PDV) sequence and are useful
for projecting the required system bandwidth. The metrics are displayed for the
slave clock for the following directions:
• Master to slave (based on Sync messages)
• Slave to master (based on Delay Request messages)
You can display current metrics, metrics for a selected interval of one hour, or for
all intervals.
 To display the clock recovery metrics:

1. For ETX205A: Navigate to configure system clock recovered 1 ptp [g.8275-1].
The config>system>clock>recovered(1)# prompt is displayed.
2. For ETX220A: Navigate to configure system clock recovered 0/1 ptp
[g.8275-1].

The config>system>clock>recovered(0/1)# prompt is displayed.

Viewing current metrics show network-metrics current The metrics for the current
interval are displayed as
shown in Viewing Current
Metrics; see Table 9-1.
Viewing the metrics for a selected show network-metrics interval • Allowed values for
interval <interval-number> interval-num: 1–24
• The metrics for the

selected interval are
displayed as shown in
Viewing Metrics for
Selected Interval; see
Table 9-1.
Viewing all metrics show network-metrics all The metrics are displayed as
shown in Viewing Current
Metrics and Viewing Metrics
for Selected Interval; see
Table 9-1.
Viewing metrics for all intervals show network-metrics all-intervals The metrics for all intervals
are displayed as shown in
Viewing Metrics for Selected
Interval; see Table 9-1.
Clearing the metrics clear-network-metrics {master-to-slave • master-to-slave – Clear

| slave-to-master | all} the metrics for the
direction master->slave.
• slave-to-master – Clear
the metrics for the
direction slave -> master.
• all – Clear all metrics.
Table 9-1. Network Metrics
Master ID Master clock identification

Id Index of metric observation window (1–22)
Tau (Sec) Metric observation window
Tdev (ns) Time Deviation PDV metric that characterizes PDV spectral noise, as
defined in ITU-T G.8260
Note: The Tdev values displayed in the network metrics are squares
of the actual Tdev values; therefore, you must compute the square
roots to obtain the correct values.

minTdev (ns) Minimum Time Deviation PDV metric that characterizes floor delay
PDV spectral noise, as defined in ITU-T G.8260
Note: The minTdev values displayed in the network metrics are
squares of the actual minTdev values; therefore, you must compute
the square roots to obtain the correct values.
Elapsed Time This time counter, in seconds, shows the statistics total information
gathering time and indicates the statistics reliability (tightness).
Sampling Time Time of sample
Sampling Date Date of sample
Examples
Configuring Slave Clock
G.8265.1
 To configure a G.8265.1 slave clock for ETX205A:

exit all
config port
svi 1
no shutdown
exit all
configure qos policer-profile policer1

exit all
config flows
classifier-profile "Router_All" match-any
match all
exit
classifier-profile "Router_Untagged" match-any
match untagged
exit
flow "Router_In"
classifier "Router_Untagged"
policer profile policer1
no shutdown
exit
flow "Router_Out"
classifier "Router_All"
policer profile policer1
ingress-port svi 1
no shutdown
exit all

config router 1
interface 1
address 172.18.141.15/24
bind svi 1
no shutdown
exit
static-route 172.17.171.0/24 address 172.18.141.1 metric 1
exit
peer 1 ip 172.17.171.158
exit all
configure
system
clock
domain 1
source 1 recovered 1
priority 1
quality-level ssm-based
wait-to-restore 0
clear-wait-to-restore
exit
exit
recovered 1 ptp
wait-to-restore 0
master 1
peer 1
priority 1
sync grant-period 60
announce grant-period 60
delay-respond grant-period 60
quality-level type1-ssm-based
no shutdown
exit
no shutdown
exit

 To display recovered clock information for ETX205A:

ETX2# configure system clock recovered 1 ptp
ETX2>config>system>clock>recovered(1/ptp)# info d
multicast 0.0.0.0
no revertive
wait-to-restore 0
no ip-address
ptp-domain 4
recovery-mode time-frequency
master 1
clock-identity clock-id ffffffffffffffff port ffff
priority 1
network-type automatic
peer 1
sync rate 64pps minimum-expected 64pps grant-period 300
announce rate 2sec minimum-expected 2sec grant-period 300
delay-respond rate 64pps minimum-expected 64pps grant-period 300
quality-level type1-ssm-based
no shutdown
exit
no shutdown
 To display recovered clock status for ETX205A:

ETX2# configure system clock recovered 1 ptp
ETX2>config>system>clock>recovered(1/ptp)# show status
Clock State: Time-Frequency : Acquisition
Indicated QL : Type-1 SSU-A
Clock Identity : 1
Active Master : 2 Ip Address : 222.18.159.59
Master Num : 1
IP : 222.17.171.158
PTSF : NACT
Clock Identity : 00B0AEFFFE011BC10001
Received QL : Type-1 SEC
Granted Sync Rate (pps) : 64
Granted Sync Period (sec) : 60
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 60
Granted Delay Respond Rate (pps) : 64
Granted Delay Respond Period (sec) : 60
Master Num : 2
IP : 222.18.159.59
PTSF : NACT
Clock Identity : 00B0AEFFFE011BC10001
Received QL : Type-1 SEC
Granted Sync Rate (pps) : 64
Granted Sync Period (sec) : 60
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 60
Granted Delay Respond Rate (pps) : 64
Granted Delay Respond Period (sec) : 60

G.8275.1
 To configure a G.8275.1 slave clock for ETX205A:

• Clock sources: Ethernet port 1 and Ethernet port 4
• Flows between:
 Ethernet port 1 and SVI 1
• PTP ports:
 Port 1 bound to SVI 1

#****************Configure SVIs
exit all
no shutdown
exit
svi 4
no shutdown
exit
#**************Configure L2CP profile for SSM and Ethernet ports

l2cp-profile SSM
mac 0x02 peer
exit
ethernet 1
l2cp profile SSM
tx-ssm
exit
ethernet 4
l2cp profile SSM
tx-ssm
exit
exit
#****************Configure classifier profiles

flows
#****************Configure flows
flow eth1_svi1
classifier untagged
egress-port svi 1
no shutdown
exit
flow svi1_eth1
classifier all
ingress-port svi 1
no shutdown
exit
flow eth4_svi4
classifier untagged
egress-port svi 4
no shutdown
exit
flow svi4_eth4
classifier all
ingress-port svi 4
no shutdown
exit

exit
#****************Configure PTP ports
system clock ptp-port 1 g.8275-1
port 1
bind svi 1
no shutdown
exit
port 4
bind svi 4
no shutdown
exit
exit
#****************Configure slave clock

recovered 1 ptp g.8275-1
no shutdown
exit
#**************** Configure clock sources

domain 1
source 1 rx-port ethernet 1
priority 1
wait-to-restore 0
clear
exit

priority 2
wait-to-restore 0
clear
exit all
save
Configuring Boundary Clock
G.8265.1
 To configure a boundary clock with G.8265.1 slave and master (for ETX220A):
#**************************** Configure slave clock ************
exit all
configure
system
clock
recovered 0/1 ptp
no ptp-domain
master 1
priority 0
peer 1
sync-rate 128pps
delay-respond 128pps
no shutdown
exit

no shutdown
exit
#************************* Configure master clock **************

master 0/1 ptp
ip-address 172.17.163.140
domain-number 0
sync-rate 128pps
no shutdown
exit all
#************************* Save configuration ******************

save
G.8275.1
 To configure a boundary clock with G.8275.1 slave and master for ETX205A:
• Clock source: Ethernet port 1
• Flows between:
• PTP ports:

#****************Configure SVIs
exit all
no shutdown
exit
svi 4
no shutdown
exit
svi 6
no shutdown
exit
#**************Configure L2CP profile for SSM and Ethernet ports

l2cp-profile SSM
mac 0x02 peer
exit
ethernet 1
l2cp profile SSM
tx-ssm
exit
ethernet 3
tx-ssm
exit
ethernet 5
tx-ssm
exit
exit

flows
flow eth1_svi2
classifier untagged
egress-port svi 2
no shutdown
exit
flow svi2_eth1
classifier all
ingress-port svi 2
no shutdown
exit
flow eth3_svi4
classifier untagged
egress-port svi 4
no shutdown
exit
flow svi4_eth3
classifier all

ingress-port svi 4
no shutdown
exit
flow eth5_svi6
classifier untagged
egress-port svi 6
no shutdown
exit
flow svi6_eth5
classifier all
ingress-port svi 6
no shutdown
exit
exit
#****************Configure PTP ports

port 3
bind svi 2
no shutdown
exit
port 5
bind svi 4
state master
no shutdown
exit
port 7
bind svi 6
state master
no shutdown
exit
exit
#****************Configure slave clock

recovered 1 ptp g.8275-1
no shutdown
exit
#****************Configure master clock

master 1 ptp g.8275-1
no shutdown
exit
#**************** Configure clock source

domain 1
priority 1
wait-to-restore 0
clear
exit all

save
Dual Mode
 To configure a boundary clock with G.8265.1 slave, and dual mode master for
ETX205A:
• G8265.1 slave:
 PTP domain 4
 SVI port 1
 VLAN 2385
 Flows between Ethernet port 1 and bridge port 1
 Flows between SVI port 1 and bridge port 2
 Remote master IP address 172.19.171.100
• G8265.1 master:
 PTP domain 4
 IP address 172.19.171.101
 Flows between Ethernet ports 2, 4, 6 and bridge ports 3, 5, 7
• Router interface 1 (used for both G8265.1 slave and G8265.1 master):
 IP address 172.19.171.101
 SVI port 1
• G8275.1 master:
 PTP domain 5
 Flows between Ethernet ports 3–5 and SVI ports 3–5
 PTP ports 3–5 bound to SVI ports 3–5

#**************** Configure SVI ports

exit all
config port
svi 1
no shutdown
exit
svi 3
no shutdown
exit
svi 4
no shutdown
exit
svi 5
no shutdown
exit
exit
#**************** Configure classifier profiles

flows
#**************** Configure flows for G.8265.1 slave

flow 8265_in
classifier v2385
no shutdown
exit
flow 8265_out
classifier all
ingress-port svi 1
reverse-direction
no shutdown
exit
#**************** Configure flows for G.8265.1 master

flow "in1"
classifier "v2385"
no shutdown
exit
flow "in4"
classifier "v2385"
no shutdown
exit
flow "in6"
classifier "v2385"

no shutdown
exit
#**************** Configure flows for G.8275.1 master

flow "eth3_svi3"
classifier "untagged"
egress-port svi 3
no shutdown
exit
flow "svi3_eth3"
classifier "all"
ingress-port svi 3
no shutdown
exit
flow "eth4_svi4"
ingress-color green
egress-port svi 4
no shutdown
exit
flow "svi4_eth4"
classifier "all"
ingress-port svi 4
no shutdown
exit
flow "eth5_svi5"
egress-port svi 5
no shutdown
exit
flow "svi5_eth5"
classifier "all"
ingress-port svi 5
no shutdown
exit
#******* Configure router interface for G8265.1 slave and master

config router 1
interface 1
address 172.19.171.101/24
bind svi 1
no shutdown
exit
exit

#*********** Configure peer for remote master, for G8265.1 slave

peer 1 172.19.171.100
exit

system clock domain 1
source 1 recovered 1
priority 1
wait-to-restore 0
exit
exit
#**************** Configure PTP ports

ptp-port 1 g.8275-1
port 3
bind svi 3
state master
no shutdown
exit
port 4
bind svi 4
state master
no shutdown
exit
port 5
bind svi 5
state master
no shutdown
exit
exit
#**************** Configure G8265.1 slave

recovered 1 ptp
ptp-domain 4
wait-to-restore 0
no shutdown
master 1
peer 1
priority 1
network-type automatic
no shutdown
exit
exit
#**************** Configure G8265.1 master
master 1 ptp
ip-address 172.19.171.101
domain-number 4
tx-clock domain 1
no shutdown
exit
#**************** Configure G8275.1 master

domain-number 5

no shutdown
exit all
save
Configuring Master Clock
G.8265.1
 To configure a standalone G.8265.1 master clock for ETX205A:

#************************* Configure master clock **************
exit all
configure
system
clock
master 1 ptp
ip-address 16.16.16.2
domain-number 5
sync-rate 128pps
no shutdown
exit all
#************************* Save configuration ******************

save
G.8275.1
 To configure a standalone G.8275.1 master clock for ETX205A:

• Clock source: System
• Flows between Ethernet port 1 and SVI 1
• PTP port 1 bound to SVI 1

#****************Configure SVI
exit all
no shutdown
exit
#****************Configure Ethernet port

ethernet 1
tx-ssm
exit

flows
flow eth1_svi1
classifier untagged
egress-port svi 1
no shutdown
exit
flow svi1_eth1
classifier all
ingress-port svi 1
no shutdown
exit
#****************Configure PTP port

port 1
bind svi 1
state master
no shutdown
exit
#****************Configure master clock

no shutdown
exit

domain 1
source 1 internal 1
quality prc
priority 1
wait-to-restore 0
clear-wait-to-restore
exit all
save
Dual Mode

 To configure a dual mode master clock for ETX205A:

• G.8265.1 master:
 PTP domain 4
 IP address 172.20.171.200
 SVI port 10
 VLAN 1637
• G.8275.1 master:
 PTP domain 5
 Clock source: GNSS
 Flows between Ethernet ports 1–3 and SVI ports 1–3
 PTP port 1 bound to SVI ports 1–3

#****************Configure SVI ports

exit all
no shutdown
exit
no shutdown
exit
no shutdown
exit
no shutdown
exit

flows
flow eth1_svi1
classifier untagged
egress-port svi 1
no shutdown
exit
flow svi1_eth1
classifier all
ingress-port svi 1
no shutdown
exit
flow eth2_svi2
classifier untagged
egress-port svi 2
no shutdown
exit
flow svi2_eth2
classifier all
ingress-port svi 2
no shutdown
exit
flow eth3_svi3
classifier untagged
egress-port svi 3
no shutdown
exit
flow svi3_eth3
classifier all
ingress-port svi 3


no shutdown
exit
flow G8265_in
classifier v1637
vlan-tag pop vlan
no shutdown
exit
flow G8265_out
classifier all
ingress-port svi 10
no shutdown
exit
#****************Configure PTP port

port 1
bind svi 1
state master
no shutdown
exit
port 2
bind svi 2
state master
no shutdown
exit
port 3
bind svi 3
state master
no shutdown
exit
exit
#****************Configure G.8265.1 master clock

master 1 ptp
ip-address 172.20.171.200
domain-number 4
tx-clock domain 1
profile-type telecom-end-to-end
no shutdown
exit
#****************Configure G.8275.1 master clock
domain-number 5
no shutdown
exit
#**************** Configure clock source GNSS

gnss 1
antenna-delay 115
no shutdown

exit
domain 1
sync-network-type 1
quality min-level-station dnu
max-frequency-deviation 1200
source 1 gnss 1
priority 1
quality-level prc
wait-to-restore 0
exit all
save
Viewing Current Metrics

ETX220A>config>system>clock>recovered(0/1/ptp)# show network-metrics current
Current
-----------------------------------------------------------------------------
Master ID : 1
Master To Slave
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elasped Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 100 501 00:33:29
2 2 55 452 00:33:28
3 4 41 400 00:33:28
4 8 39 400 00:33:29
5 12 71 400 00:33:25
6 16 121 438 00:33:21
7 24 171 411 00:33:14
8 32 231 520 00:33:06
9 48 180 484 00:32:51
10 64 162 593 00:33:07
11 96 63 674 00:32:06
12 128 115 402 00:32:07
13 196 146 547 00:32:41
14 256 138 673 00:29:57
15 384 132 879 00:32:07
16 512 96 400 00:25:46
17 768 172 400 01:04:00
18 1024 116 400 00:51:14
19 2048 1 1 00:34:14
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
Slave To Master
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elasped Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 128 449 00:33:30
2 2 63 400 00:33:30
3 4 45 400 00:33:28
4 8 54 406 00:33:29
5 12 75 400 00:33:25

6 16 122 420 00:33:21

7 24 187 406 00:33:14
8 32 233 428 00:33:06
9 48 189 477 00:32:51
10 64 158 400 00:33:07
11 96 64 400 00:32:06
12 128 122 400 00:32:07
13 196 135 400 00:32:41
14 256 130 569 00:29:57
15 384 129 400 00:32:07
16 512 107 400 00:25:46
17 768 103 400 00:51:13
18 1024 25 400 00:51:13
19 2048 1 1 00:34:09
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
Viewing Metrics for Selected Interval

ETX205A>config>system>clock>recovered(1/ptp)# show network-metrics interval 1
Interval Number : 1
Master ID : 1
Sampling Time : 08:00:00
Sampling Date : 26-07-2012
Master To Slave
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elapsed Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 41448968 58527396 00:05:49
2 2 18079422 28993502 00:05:48
3 4 5276496 15718937 00:05:48
4 8 1201367 12813626 00:05:45
5 12 691645 12206705 00:05:49
6 16 506413 8053903 00:05:38
7 24 622610 3623477 00:05:39
8 32 347378 4017002 00:05:22
9 48 78378 9761690 00:05:39
10 64 139133 6660025 00:05:23
11 96 606 139842 00:04:53
12 128 1 1 00:04:19
13 196 1 1 00:03:19
14 256 1 1 00:04:21
15 384 1 1 00:00:11
16 512 1 1 00:00:13
17 768 1 1 00:00:14
18 1024 1 1 00:00:15
19 2048 1 1 00:00:15
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19

Slave To Master
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elapsed Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 617756 400 00:30:44
2 2 770042 400 00:30:44
3 4 344708 400 00:30:44
4 8 246177 2935 00:30:41
5 12 226724 65673 00:30:37
6 16 159360 316373 00:30:41
7 24 218542 1682603 00:30:27
8 32 231636 3483920 00:30:27
9 48 203230 6556856 00:30:29
10 64 166905 9179698 00:29:55
11 96 103179 14061712 00:30:29
12 128 88556 19896568 00:29:55
13 196 79678 34140880 00:29:25
14 256 50201 47704072 00:29:57
15 384 60187 119676112 00:25:45
16 512 60686 237447312 00:25:46
17 768 1 1 00:25:47
18 1024 1 1 00:17:10
19 2048 1 1 00:00:15
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
9.2 Clock Selection

This section discusses the clock selection mechanism provided by ETX2.
Applicable Products
This feature is applicable to ETX205A and ETX220A with timing options. The
<slot> parameter is relevant for ETX220A.
Standards
ITU-T G.8261/G.8262-G.8264
Benefits
The clock selection provides synchronization over packet transport networks.
You can configure a slave (recovered) clock that complies with the IEEE-1588
Precision Time Protocol (PTP). You need to configure the clock domain before
configuring the recovered clock.
9-32 Clock Selection ETX2

ETX2 supports one clock domain with up to two clock sources. The sources can be
network/user Ethernet ports, station clock, or internal GPS clock (in the case of
ETX205A with GNSS).
The timing subsystem automatically selects the best timing source to use for
synchronization.
Clock Domain
The domain parameters include the synchronization network type and the timing
quality level.
The synchronization network type identifies the type of synchronization network
connections and the synchronization level. Each synchronization network
connection is provided by one or more synchronization link connections, each
supported by a synchronized PDH trail, SDH multiplex section trail, or 802.3
physical media trail.
The synchronization network types are:
i. Option I (Europe)
ii. Option II (USA)
You can define the timing quality level of the domain and source, or work without
quality level. The supported quality levels are according to the synchronization
network type, as shown in the following tables. The quality levels are shown in
order of highest quality level to lowest quality level.
Table 9-2. Option I Quality Levels
Quality Description Rank

Level
PRC Timing source is Primary Reference Clock as defined in Recommendation Highest

G.811
SSU-A Timing source is Type I or V Synchronization Supply Unit (SSU) clock as |

defined in Recommendation G.812
SSU-B Timing source is Type VI Synchronization Supply Unit (SSU)clock as defined |

in Recommendation G.812
SEC Timing source is Synchronous Equipment Clock as defined in |

Recommendation G.813 or G.8262, Option I
DNU Do Not Use – This signal should not be used for synchronization. Lowest
Table 9-3. Option II Quality Levels

Level
PRS Timing source is Primary Reference Source clock as defined in Highest

Recommendation G.811
STU Synchronization Traceability Unknown – Timing signal does not carry a |

quality level indication of the source.
ETX2 Clock Selection 9-33


Level
ST2 Timing source is Stratum 2 clock as defined in Recommendation G.812, |

Type II.
TNC Timing source is Transit Node Clock as defined in Recommendation G.812, |

Type V.
ST3E Timing source is Stratum 3E clock as defined in Recommendation G.812, |

Type III.
ST3 Timing source is Stratum 3 clock as defined in Recommendation G.812, |

Type IV.
SMC Timing source is SONET/Ethernet self-timed clock as defined in |

Recommendation G.813 or G.8262, Option II.
ST4 Timing source is Stratum 4 free-running clock (applicable only to 1.5 |

Mbit/s signals).
PROV Provisionable by the network operator |
DUS Don't Use for Sync – This signal should not be used for synchronization. Lowest
Factory Defaults
By default, if a timing card is installed in the unit a clock domain entry is created
with the following configuration:
• Synchronization network type 1
• Minimum quality DNU
• Mode auto (clock selection mechanism functions normally)
Configuring the Clock Domain
 To configure the clock domain:

1. Navigate to configure system clock domain 1.
The config>system>clock>domain(1)# prompt is displayed.
Canceling previously issued clear

force or manual command
Clearing statistics for clock clear-statistics

sources
Forcing selection of a force <source-id>

particular clock source
when the sources have
different quality levels

Forcing T4 (station clock) force-t4-as-t0 Use no-force-t4-as-t0 to

timing generator to use prevent T4 timing generator
the same clock source as from using the same clock
the T0 (system clock) source as the T0 generator.
generator
Manually selecting a manual <source-id> This command in the following

particular clock source conditions:
• No quality is defined for the
clock domain.
• The sources have the same
qualities.
• The sources have different
priorities.
Setting maximum max-frequency-deviation <value> Range is 381–6096, in units of

frequency deviation PPM*100 (e.g. specifying 381
sets maximum frequency
deviation to 3.81).
When frequency deviation of
an input clock source exceeds
the defined maximum
frequency deviation, the clock
source is declared invalid.
Setting clock mode mode { auto | free-run | force-t0-holdover } auto – Clock selection
mechanism functions normally,
e.g. the best available clock
source is selected for
synchronization.
free-run – Internal oscillator is
used for synchronization.
force-t0-holdover – Clock is no
longer synchronized to
reference clock source.
Setting minimum quality of quality min-level-station { prc | ssu-a | ssu-b | sec | dnu } Typing no quality removes the
clock quality min-level-station { prs | stu | st2 | tnc | st3e | st3 | minimum quality parameter. If
smc | st4 | dus | prov } no minimum quality is defined
for the domain you cannot
quality min-level-station { unk | sec | dnu }
configure quality level for the
sources. A clock source with
quality level lower than the
defined minimum quality is
ignored by the clock selection
mechanism.
Note: The quality values are
according to the
synchronization network type
defined for the domain (see
Table 9-2 and Table 9-3).

Displaying domain status show status
Configuring clock source source <src-id> Typing no source <src-id>

deletes the source.
See Clock Sources.
Adding clock source source <src-id> internal-gps 1 See Clock Sources.

source <src-id> recovered [<slot>/]<port>
source <src-id> rx-port ethernet [<slot>/]<port>source
<src-id> station [<slot>/]<port>
Setting synchronization sync-network-type { 1 | 2} Type 1 – Europe

network type Type 2 – USA
Note: When you change the
synchronization network type,
you have to redefine the clock
sources.
Clock Sources
You can define up to two clock sources for the domain. The sources can be:
• Ethernet ports
• Recovered clock
• Station clock
• Internal GPS clock (for ETX205A with GNSS)
Note • If an Ethernet port is defined as a clock source, it must be associated with an

L2CP profile that specifies peer action for MAC 0x02. It is also recommended to
enable the transmitting of SSM messages by the port (via tx-ssm), as it may
need to transfer clock signals.
Factory Defaults
When a clock source is created, its default configuration is the following (see the
task list below for explanations of the parameters):
• Priority = 2
• Wait-to-restore = five minutes (300 seconds)
• Hold-off = 300 milliseconds
Configuring the Clock Sources
 To add a clock source:


2. Type one of the following, according to the type of clock source:

source <1–2> rx-port ethernet [<slot>/]<port>
source 1 recovered [<slot>/]<port>
source <1–2> station [<slot>/]<port>
source 1 internal-gps 1
The clock source is created and the
config>system>clock>domain(1)>source(<1–2>)$ prompt is displayed.
3. Enter all necessary commands according to the tasks listed below the following
procedure.
 To configure a clock source that has already been created:

2. Type source <1–2> to select the source to configure.
The config>system>clock>domain(1)>source(<1–2>)# prompt is displayed.
Canceling the wait-to-restore clear-wait-to-restore

timer of a clock source. This is
useful if a timing source fault is
cleared and you want the
source to be immediately
available.
Defining amount of time (in hold-off <milliseconds> Possible values: 300–1800

milliseconds) that signal failure
must be active before it is
transmitted
Setting priority priority <num> Possible values: 1–2

Note: Priority 1 is the highest.

Setting quality level quality-level { prc | ssu-a | ssu-b | sec | dnu | ssm-based } Notes:
quality-level { prs | stu | st2 | tnc | st3e | st3 | smc | st4 | • If no minimum quality is
dus | ssm-based | prov } defined for the domain, this
command is not available.
• The quality level values are
according to the
synchronization network
type defined for the domain
(see Table 9-2 and
Table 9-3)
• The quality level ssm-based
indicates the quality level is
based on SSM messages.
This option requires that if
an Ethernet port is being
used as the clock source,
the port is associated with
an L2CP profile that
specifies peer action for
MAC 0x02.
Defining amount of time (in wait-to-restore <seconds> Possible values: 0–720

seconds) that a previously
failed synchronization source
must be fault free in order to
be considered available
Displaying statistics show statistics
Viewing Clock Source Statistics

You can display the Ethernet Synchronization Messaging Channel (ESMC) statistics
for the clock sources.
 To display the ESMC statistics for a clock source:

1. Navigate to configure system clock domain 1 source <src-id>.
config>system>clock>domain(1)>source(<src-id>)#.
2. Enter:
show statistics
The ESMC statistics are displayed.
Configuring the Station Clock

The station clock is an E1/2MHz port that can be used for synchronization.

 To configure the station clock:

1. For ETX205A: Navigate to configure system clock station 1.
The config>system>clock>station(1)# prompt is displayed.
2. For ETX220A: Navigate to configure system clock station 0/1.
The config>system>clock>station(0/1)# prompt is displayed.
Setting interface type interface-type e1 [{balanced | unbalanced}] If you specify e1 or 2mhz and
Note: You can configure interface-type 2mhz [{balanced | unbalanced}] do not specify balanced or
the interface type only if unbalanced, by default the
the station clock is interface is set as balanced.
administratively disabled
(shutdown).
Setting line code line-code { ami | hdb3 } ami – Referred to as Alternate

Note: You can configure Mark Inversion because a 1 is
the line code only if the referred to as a mark and a 0
interface type is E1 and as a space.
the station clock is hdb3 – Referred to as High
administratively disabled Density Bipolar of order 3, this
(shutdown). code is a telecommunication
line code based on AMI and
used in E1 lines.
Setting receiver sensitivity rx-sensitivity {short-haul | long-haul}

to adjust the signal’s
capability to reach
destinations close by or
farther away
Setting clock timing to be tx-clock-source {system | loopback-timing} system – timing based on

based on internal system internal system
or external source loopback-timing – timing based
on E1/2MHz external source
Administratively enabling no shutdown Using shutdown disables the

station clock station clock.
Examples
 To configure clock selection for ETX205A:
• Domain 1:
 Synchronization network type 2
 Quality level: Timing source is Stratum 3E clock
 Source 1: Ethernet port 3 (which is configured with L2CP profile with peer
for MAC 0x02, and transmitting of clock SSM messages)

exit all
configure port l2cp-profile ssm
mac 0x02 peer
exit
ethernet 3
l2cp profile ssm
tx-ssm
exit all
configure system clock domain 1

sync-network-type 2
quality min-level-station st3e
exit all
 To display the clock source statistics:

ETX2# configure system clock domain 1 source 1
ETX2>config>system>clock>domain(1)>source(1)# show statistics
ESMC Failure Counter : 0
Rx Tx
ESMC Events : 1 2
ESMC Information : 1 255
ETX2>config>system>clock>domain(1)>source(1)$ exit
ETX2>config>system>clock>domain(1)# info detail
sync-network-type 2
quality min-level-station st3e
max-frequency-deviation 1200
mode auto
force-t4-as-t0
echo "Clock Source Configuration"
# Clock Source Configuration
priority 2
wait-to-restore 300
hold-off 300
exit
9.3 Date and Time

You can configure the ETX2 internal real-time clock as free running or with Simple
Network Time Protocol (SNTP).
For ETX205A with PMC, you can configure its integrated x86 processor internal
real-time clock as free running or with Network Time Protocol (NTP).
9-40 Date and Time ETX2

Applicable Products
This feature is applicable to all ETX2 products, and to the integrated x86
processor, with the following restrictions:
• Manual configuration of the date and time is relevant for ETX2 products, as
well as the integrated x86 processor.
• SNTP configuration is relevant for ETX2 products.
• NTP configuration is relevant for integrated x86 processors (in ETX205A with
PMC).
Standards and MIBs

• DISMAN-SCHEDULE-MIB, RFC 3231
• IF-MIB, RFC 2863
• SNMPv2-MIB, RFC 3418
• RFC 4330
Benefits
SNTP and NTP synchronize the internal clocks of network devices to a single time
reference source. SNTP and NTP provide comprehensive mechanisms to access
national time dissemination services, organize the NTP subnet of servers and
clients, and adjust the system clock in each participant. It improves the
timekeeping quality of the network by using redundant reference sources and
diverse paths for time distribution.
Network Time Protocol (NTP) is a networking protocol for clock synchronization
between computer systems over packet-switched, variable-latency data networks.
It is a large and very complex application for the synchronization of computers and
computer networks, incorporating complex statistical algorithms that filter out
small discrepancies in time and makes time adjustments. It synchronizes all
participating computers to within a few milliseconds of Coordinated Universal Time
(UTC).
Simple Network Time Protocol (SNTP), a less complex implementation of NTP, uses
the same protocol without requiring the storage of state over extended periods of
time. It synchronizes the internal clocks of network devices to a single time
reference source.
The SNTP client operates in one of the following modes:
Unicast Sends requests to configured server addresses
Broadcast Listens to an unsolicited broadcast address and learns

timestamps from any broadcast server sending messages
to this address
ETX2 Date and Time 9-41

Note • SNTP is not supported on OOB ports.
Factory Defaults
The default configuration of the SNTP/NTP parameters is:
• No SNTP/NTP servers are defined.
• Polling interval is set to 15 minutes (relevant for SNTP only).
When an SNTP/NTP server is defined, its default configuration is:
• IP address is set to 0.0.0.0
• Not preferred
• Administratively disabled (shutdown)
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 desired date date-format {yyyy-mm-dd | dd-mm-yyyy |

format mm-dd-yyyy | yyyy-dd-mm}
Defining the date date <date> Date is according to the configured date
format.
Configuring NTP ntp For configuration of internal clock in

integrated x86 processor (relevant for
ETX205A with PMC).
See Working with NTP.
Configuring SNTP sntp For configuration of ETX2 device internal

clock.
See Working with SNTP.
Scheduling adjustment of device summer-time See Configuring Daylight Saving Time

time for daylight saving time Scheduling.
start and stop
Displaying daylight saving time show summer-time For details and an example on how to to
scheduling information view scheduled daylight saving time in your
device, refer to Viewing Scheduling
Information in the Operation and
Maintenance chapter.
Defining the time time <hh:mm[:ss]>

Defining the time zone relative zone utc [<[{+|-}]hh[:mm]>] Possible values:
to Universal Time Coordinated -12:00 to +12:00, in 30-minute increments
(UTC)
Viewing the Date and Time

 To display the date and time:
• From the system context (config>system), enter:
show system-date
Working with SNTP

You can configure the time on the internal clock of the ETX2 device, with the time
on an SNTP server.
This section explains how to receive the clock signal from NTP servers in the
network. ETX2 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 ETX2
sends NTP requests to the preferred server. If there is no preferred server or if the
preferred server does not answer, then ETX2 sends NTP requests to any enabled
servers.
Configuring SNTP Parameters

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

broadcast messages to obtain broadcast mode.
accurate timestamps
Setting polling interval for SNTP poll-interval interval <minutes> • If interval parameter is
requests poll-interval fast-mode specified, the allowed
range of minutes is:
1–1440
• If fast-mode parameter is
specified, the interval is set
to 4 seconds (for accuracy
of TWAMP one-way
metrics).
Defining and configuring SNTP server <server-id>

servers (see Defining SNTP
Servers)

Displaying SNTP status show status
Defining SNTP Servers

 To define an SNTP server:
1. Navigate to config system date-and-time sntp.
The config>system>date-time>sntp# prompt is displayed.
2. Type server <server-id> to define an SNTP server with ID <server-id>.
config>system>date-time>sntp>server(<server-id>)$. The SNTP server
parameters are configured by default as described in Factory Defaults
above.
Setting the IP address of the address <IP-address>

server
Set SNTP server as preferred prefer Type no prefer to remove

server. preference.
Note: Only one server can be
preferred.
Setting UDP port for NTP udp port <udp-port> Possible values: 1–65535
requests, to a specific UDP port udp default
or to default UDP port (123)
Administratively enabling server no shutdown Using shutdown disables the

server.
Sending query to server and query-server

displaying result
Working with NTP

You can configure the time on the internal clock of the integrated x86 processor in
ETX205A with PMC, with the time on an NTP server.
This section explains how to receive the clock signal from NTP servers in the
network. One of the active NTP servers can be designated the preferred server, so
that NTP requests are sent to the preferred server. If there is no preferred server
or if the preferred server does not answer, then NTP requests are sent to any
enabled servers.
Configuring NTP Parameters

 To configure NTP parameters:
1. Navigate to configure system date-and-time ntp.
The config>system>date-time>ntp# prompt is displayed.

Defining and configuring NTP server <server-id>

servers (see Defining NTP
Servers)
Displaying NTP status show status
Defining NTP Servers

 To define an NTP server:
1. Navigate to config system date-and-time ntp.
The config>system>date-time>ntp# prompt is displayed.
2. Type server <server-id> to define an NTP server with ID <server-id>.
config>system>date-time>ntp>server(<server-id>)$.
Setting the IP address of the address <IP-address>

server
Set NTP server as preferred prefer Type no prefer to remove

server. preference.
Note: Only one server can be
preferred.
Administratively enabling server no shutdown Using shutdown disables the

server.
Sending an NTP polling request query-server

to check server status
Examples
Setting Date and Time
 To set the date and time:

• Format = mm-dd-yyyy
• Date = May 17, 2012
• Time = 5:40pm
• Zone = UTC –4 hours and 30 minutes

exit all
configure system date-and-time
date-format mm-dd-yyyy
date 05-17-2012
time 17:40
zone utc -04:30
Defining SNTP Server
 To define SNTP server:

• Server ID = 1
• IP address = 192.1.1.1
• Preferred
exit all
configure system date-and-time sntp
server 1
address 192.1.1.1
prefer
no shutdown
Viewing SNTP Server Information
 To display server information:

ETX2# configure system date-and-time sntp server 1
ETX2>config>system>date-time>sntp>server(1)# query-server
Query Server Replay
-----------------------------------------------------------------------------
Server : 192.1.1.1 UDP : 123
Date : 00-00-0000 Time : 00:00:00
Stratum : 0
ETX2>config>system>date-time>sntp>server(1)# exit
ETX2>config>system>date-time>sntp# show status
System Uptime : 000 Days 00:19:55
System Time : 2009-09-14 13:01:09
Current Source : 1 127.0.0.1
NTP Server Type UDP Port Tstap Date Time Strat Received
192.1.1.1 Prefer 123 00-00-0000 00:00:00 0 --
Defining NTP Server
 To define NTP server:

• Server ID = 1
• IP address = 172.17.171.141
• Preferred

exit all
configure system
date-and-time
zone utc +03:00
ntp
server 1
address 172.17.171.141
prefer
no shutdown
exit
9.4 Daylight Saving Time

You can schedule your device to change its system time to daylight saving time
(also known as summer time), at a specific date and time.
Applicable Products
Factory Defaults
By default, no scheduling is configured.
The default value for daylight saving time offset is 60 minutes.
You can specify when the device local system time should reflect the start of
daylight saving time by adding an offset, and when it should reflect the end of
daylight saving time by subtracting the offset.
Daylight saving time can be scheduled in one of the following ways:
One shot Daylight saving time starts and ends once, at a specified
date and time (e.g. November 6 2016).
Recurring Daylight saving time starts and ends every year at a

specified time, and a date specified according to the
weekday and month (e.g. first Sunday in October).
The daylight saving time schedule is saved in nonvolatile (permanent) memory, in

order to be available after device reboot.
Note ETX2 logs the start and end of daylight saving time with the events
summer_time_started and summer_time_ended, respectively. Each event is also
sent as an SNMP notification to management stations.
ETX2 Daylight Saving Time 9-47

Configuring Daylight Saving Time Scheduling

When you configure daylight saving time scheduling, the first set of parameters in
the commands specifies when daylight saving time starts, and the second set of
parameters specifies when daylight saving time ends.
 To configure daylight saving time:

• Navigate to the config>system>date-time level and enter the summer-time
command according to the type of schedule:
 One shot – Enter:
summer-time date {january | february | march | april | may | june | july |
august | september | october | november | december} <dd> <yyyy>
<hh>:<mm> {january | february | march | april | may | june | july | august |
september | october | november | december} <dd> <yyyy> <hh>:<mm>
[<offset>]
 Recurring – Enter:
summer-time recurring { 1 | 2 | 3 | 4 | last} {sunday | monday | tuesday |
wednesday | thursday | friday | saturday} {january | february | march | april |
may | june | july | august | september | october | november | december}
<hh>:<mm> { 1 | 2 | 3 | 4 | last} {sunday | monday | tuesday | wednesday |
thursday | friday | saturday} {january | february | march | april | may | june |
july | august | september | october | november | december}
<hh>:<mm>[<offset>]
The parameter {1 | 2 | 3 | 4 | last} specifies the week of the month.
For both schedule types, <offset> specifies (in minutes) the time to add at
daylight saving time start, or subtract at daylight saving time end. Its range is 1–
1440.
 To delete daylight saving time scheduling:

• Navigate to the config>system>date-time level and enter:
no summer-time
Viewing Scheduling Information

For details and an example on how to view scheduled daylight saving time in your
device, refer to Viewing Scheduling Information in the Operation and Maintenance
chapter.
Examples
 To schedule daylight saving time starting March 27 2016 at 1:00 and ending
October 27 2016 at 2:00:
exit all
summer-time date march 27 2016 01:00 october 27 02:00
save
9-48 Daylight Saving Time ETX2

 To schedule daylight saving time starting on the first Friday in March at 2:00 and
ending on the last Sunday in October at 3:00:
exit all
summer-time recurring 1 friday march 02:00 last sunday october
03:00
save
Schedule with this name You tried to create a new schedule with Specify a name that is not being used
already configured a name that is used by an existing by an existing schedule.
schedule.
Summer-time already You entered the summer-time command Delete the existing summer-time
configured to configure daylight saving time, but configuration; and then re-enter the
the scheduling of summer-time has summer-time command.
already been configured.
Recurring summer-time You tried to configure summer-time start Enter the summer-time command
start and end must be and end in the same month. with summer-time start and end in
on different months different months.
Summer-time cannot You entered the summer-time command Enter the summer-time command
end before it starts (with one-shot schedule type) with with summer-time start time earlier
summer-time end time earlier than than the end time.
summer-time start.
9.5 GNSS Receiver

ETX2 supports a 1588v2 standalone master clock with a built-in global navigation
satellite system (GNSS) receiver.
Applicable Products
This feature is applicable to ETX205A with GNSS port.
ETX205A with GNSS ordering option includes the following:
• 1588v2 grandmaster
• GNSS antenna
• 1PPS interface
• Station clock
ETX2 GNSS Receiver 9-49

Benefits
The GNSS antenna receives accurate timing data from the global navigation
satellite system, to aid in recovering the clock timing.
GNSS satellites continuously broadcast satellite position and timing data. The GNSS
antenna receives accurate timing data by tracking satellites and locking onto 1PPS
signals.
The GNSS antenna cable could potentially introduce delays in the timing signal
delivered to ETX205A; therefore, it is possible to configure a delay that can be
taken into account.
Factory Defaults
The default configuration is shown below.
name GNSS PORT 1
antenna-delay 0
shutdown no shutdown
Configuring GNSS
 To configure the GNSS receiver:
1. Navigate to configure system clock gnss 1.
The config>system>clock>gnss(1)# prompt is displayed.
Configuring antenna cable antenna-delay <nsec> Possible values: 0–999999

delay in nanoseconds
Assigning name to GNSS name <string>

port
Administratively enabling no shutdown Using shutdown disables the GNSS receiver.

GNSS receiver
Viewing GNSS status show status See Viewing GNSS Status.
9-50 GNSS Receiver ETX2

Example
 To configure the GNSS receiver antenna delay to 150 nanoseconds:
exit all
configure system clock gnss 1
antenna-delay 150
exit all
save
Viewing GNSS Status

You can view the GNSS status to see if the GNSS receiver is fully locked to the
GNSS signals, and view the satellite statuses, if applicable.
 To view the GNSS status:

1. Navigate to configure system clock gnss 1.
The config>system>clock>gnss(1)# prompt is displayed.
2. Enter:
show status
ETX2 GNSS Receiver 9-51

ETX205A# configure system clock gnss 1

ETX205A>config>system>clock>gnss(1)# show status
Name : GNSS PORT 1
Mode : GPS
Tracking : GNSS Locked
Latitude : N32:06:40.730
Longitude : E034:50:22.031
Height : 83.235
GPS Satellite Status

----------------------------------------------------------------
Num SNR Healthy Azimuth Elevation
----------------------------------------------------------------
2 49 Yes 53 45
5 43 Yes 116 17
6 44 Yes 39 11
10 45 Yes 68 10
12 49 Yes 66 63
14 42 Yes 267 9
21 41 Yes 210 5
24 48 Yes 178 35
25 47 Yes 337 58
29 48 Yes 275 44
31 32 Yes 322 11
120 40 No 246 25
126 45 No 197 51
127 0 No 145 47
128 0 No 115 27
The Tracking field can contain one of the following values:
GNSS Locked GNSS is fully operational (both tracking satellites and

locked to 1PPS signal).
Not Tracking GNSS is not operational (neither tracking satellites nor

locked to 1PPS signal).
Tracking Satellites GNSS is tracking satellites, but is not locked to 1PPS signal.
9-52 GNSS Receiver ETX2

Chapter 10
Administration
This chapter describes administrative features:
• CPU and Memory Utilization
• Device Information
• Environment
• File Operations
• Inventory
• Licensing
• Login Banner
• Sending a Message to Connected Users
• Reset
• Tech-Support Commands
10.1 CPU and Memory Utilization

You can view CPU and memory pool usage.
Applicable Products
Viewing CPU Utilization

 To display CPU usage:
• From the system context (config>system), enter:
show cpu-utilization
The CPU usage is displayed.
ETX-2>config>system# show cpu-utilization
CPU Utilization
---------------------------------------------------------------
Min (%) : 2
Cur (%) : 2
Max (%) : 65
Average (%) : 10
ETX2 CPU and Memory Utilization 10-1

Chapter 10 Administration Installation and Operation Manual
Viewing Memory Pool Utilization

 To display memory pool usage:
1. From the system context (config>system), enter the following to display
memory pool usage:
show memory
The memory pool usage is displayed, showing the total amount allocated
to the pool, as well as the amount that is free.
ETX-2>config>system# show memory
Kernel Kernel
Total (KB) Free (KB)
---------------------------------------------------------------
Memory 3166141899 1051027919
2. From the system context (config>system), enter the following to display
details of memory pool usage:
show memory–details
ETX-2>config>system# show memory-details
Kernel Total(KB) : 3166141899 Free : 1051027919
10.2 Device Information

By default, the system name for a device is the same as the description, and is
the actual name of the unit. In the case of ETX203AX, ETX205A, and ETX220A,
the system name reflects the device ordering option. This is the system name
displayed in the CLI prompt before the pound sign (#). The following table shows
the available system names for the available ETX2 devices.
Table 10-1. System Name Parameter Default Values
Ordering Option Key Features System Name
ETX203AX
ETX203AX ETX203AX
ETX203AX/E1 ETX203AX-E1
ETX203AX/DSL ETX203AX-DSL
ETX203AM
ETX203AM ETX203AM
ETX205A
ETX205A/PTP ETX205A-PTP
ETX205A/4E1/SYE ETX205A-4E1/T1-SYE
ETX205A/8E1/SYE ETX205A-8E1/T1-SYE
ETX205A/SYE ETX205A-SYE
10-2 Device Information ETX2

Installation and Operation Manual Chapter 10 Administration
Ordering Option Key Features System Name
ETX220A
ETX220A/3XFP/10SFP or UTP ETX220A-3XFP-10x1G
ETX220A/2XFP/20SFP or UTP ETX-220A-2XFP-20x1G
ETX220A/4XFP ETX220A-4XFP
ETX220A/4XFP/10UTP or UTP ETX220A-4XFP-10x1G
The ETX2 management software allows you to assign a different name to the
unit, specify its location to distinguish it from the other devices installed in your
system, and assign a contact person. You cannot change the description of the
unit (, which by default, is the same as the name).
Applicable Products
Standards
The commands below are based on RFC 3841.
Configuring Device Information

 To configure device information:
1. Navigate to configure system.
The config>system# prompt is displayed.
Specifying contact person contact <contact-person> Typing no contact removes contact person.
Assigning device name name <device-name> The device name can be 0-255 characters; however, the device
prompt displays only up to 20 characters, therefore if you enter a
name with more than 20 characters, the prompt displays the first
19 characters followed by *.
For example, a command that defines a device with a name
longer than 20 characters:
ETX2# config sys name 12345678901234567ETX2
results in the prompt:
12345678901234567ET*#
You can view the complete device name by typing
show device-information.
Typing no name removes the name entirely.
Specifying location location <device-location>
ETX2 Device Information 10-3

Displaying device show device-information

information, MAC address,
and amount of time device
has been running
10-4 Device Information ETX2

Examples
 To configure device information for ETX203AX:
• Device name – ETX203AX
• Location – floor-8
• Contact – Engineer-1
exit all
configure system
name ETX-203AX location floor-8
contact Engineer-1
exit all
 To display device information for ETX205A/PTP:

ETX-205Al-PTP>config>system# show device-information
Description : ETX-205A-PTP Hw: 0.1/6xGbE SFP, Sw: 6.51 (0.11)

Name : ETX-205A-PTP
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-30-CC-9D
Engine Time : 05:13:31
 To display device information for ETX220A/4XFP:

ETX-220A-4XFP>config>system# show device-information
Description :
Name : ETX-220A-4XFP Hw: 1.0/A, Sw: 6.51 (0.11)
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-30-CC-9D
 To display the default device information for ETX203AX/DSL:

ETX-203AX-DSL>config>system# show device-information
Description : ETX-203AX-DSL Hw: 0.0/, Sw: 6.5.0(0.2)
Name : ETX-203AX-DSL
Location : The location of this device
Contact : Name of contact person
MAC Address : 00-20-D2-58-94-86
10.3 Environment
You can define the temperature threshold of a chassis, enable or disable
overheat auto shutdown, and display information about chassis components.
ETX2 Environment 10-5

Applicable Products
These features are applicable to all ETX2 products, with the following conditions:
• Redundant power supplies are applicable to ETX205A and ETX220A.
• Fans are applicable to ETX203AM, ETX205A, and ETX220A.
• Temperature sensors are applicable to ETX205A and ETX220A.
• Temperature threshold can be configured for ETX205A and ETX220A.
• Overheat auto shutdown is applicable to ETX205A and ETX220A only.
Device Temperature
You can define minimum and maximum temperature thresholds, as well as
temperature unit (Celsius or Fahrenheit), in order to receive trap notification that
the device temperature has left the allowed range or returned to the allowed
range.
You can optionally use a hysteresis mechanism to avoid sending an excessive
amount of traps when a threshold is repeatedly crossed. The hysteresis defines
the margin around the temperature thresholds for sending trap notification of
temperature threshold crossed:
• Sends trap notification of temperature too high when the temperature rises
above <maximum temperature + hysteresis value>.
• After sending a trap notification of temperature too high, it sends a trap
notification of temperature OK when the temperature falls below <maximum
temperature - hysteresis value>.
• Sends trap notification of temperature too low when the temperature falls
below <minimum temperature - hysteresis value>.
• After sending a trap notification of temperature too low, it sends the trap
notification of temperature OK when the temperature rises above <minimum
temperature + hysteresis value>.
Device Fan
The device fan is activated when the temperature of the device exceeds a certain
limit (defined by RAD HW engineers; non-configurable). When the device
temperature once again drops below that limit, the fan stops.
A Fan Failure alarm is issued if the device fan stops working or its speed drops
below 100RPM.
Overheat Auto Shutdown

By default, ETX2 supports automatic shutdown upon over heat detection. You
can enable or disable automatic shutdown, as required.
When auto shutdown upon heat detection is enabled, and the ETX2 temperature
exceeds the configured maximum temperature threshold, the device sends a
dying gasp event with an indication of the overheat reason (“Dying gasp:
10-6 Environment ETX2

temperature overheat”), and then immediately enters over heat shutdown state.
During shutdown, the following occurs:
• All physical interfaces (ETH, SFP lasers, E1), including Rx and Tx, shut down.
• FPGA remains in reset state.
• CPU remains in low power mode.
ETX2 leaves over heat shutdown state, when the device temperature drops
below the minimum temperature threshold. The device then automatically resets
and boots up.
Configuring the Chassis

 To configure the chassis:
1. Navigate to configure chassis.
The config>chassis# prompt is displayed.
Enabling or disabling [no] overheat-auto-shutdown By default, overheat auto shutdown is enabled.

overheat auto shutdown
Setting lowest and highest temperature-threshold

allowed device { celsius | fahrenheit }
temperature min <min-value>
max <max-value>
[ hysteresis <hysteresis-value> ]
Displaying environment show environment Displays information about the following:

information • Type and status of the power supplies – AC, DC, or -- (if it is
absent or has failed)
• Status of fans – indicates whether the fan is present and
functioning properly, is absent (does not exist), or has failed.
• Temperature sensor – indicates the temperature, and whether
the sensor is functioning correctly
Examples
 To define temperature thresholds:
• Minimum temperature = -20 degrees Celsius
• Maximum temperature = 50 degrees Celsius
• Hysteresis = 4
exit all
ETX-2>configure chassis
ETX-2>config chassis#
temperature-threshold celsius min -20 max 50 hysteresis 4
exit all
save
ETX2 Environment 10-7

 To view environment information for ETX203AM:

ETX-2# configure chassis
ETX-2>config>chassis# show environment
Power Supply Type Status
---------------------------------------------------------------
1 AC OK
FAN Status
---------------------------------------------------------------
1 OK
 To view environment information for ETX203AX:

---------------------------------------------------------------
1 AC-DC OK
 To view environment information for ETX205A:

---------------------------------------------------------------
1 AC OK
2 -- Not exist
FAN Status
---------------------------------------------------------------
1 OK
2 OK
Sensor Value Status

---------------------------------------------------------------
1. 32 Celsius OK
 To view environment information for ETX220A:

ETX-2 # configure chassis
---------------------------------------------------------------
1 AC OK
2 -- Not exist
FAN Status
---------------------------------------------------------------
1 OK
2 OK
3 OK
4 OK
5 OK
Sensor Value Status

---------------------------------------------------------------
1. 36 Celsius OK
10-8 Environment ETX2

10.4 File Operations

You can perform the following operations on files:
• Transfer files via SFTP/TFTP
• Add a description to a file
• Copy files within the ETX2 unit
• Display files
• Display file details and contents
• Delete files
Applicable Products
Device Files
ETX2 supports the following files:
• Software files: sw-pack-1..sw-pack-4
• License files: license-1..license-n
• Configuration files: running-config, rollback-config, startup-config, user-
default-config, factory-default-config, restore-point-config
• Alarm and event logs: log, brief-log
• Performance management: pm-0
• Banner file: banner-text
• Zero touch configuration file: zero-touch-config-xml
• DB schema file: db-schema
• DB configuration file: db-config
• Sniffer file: sniffer-file
• Scheduler log: schedule-log
• User script: user-script
• Script result: script-result
• User files: user/<filename>
• Syslog accounting log: accounting-log
User Directory
The ETX2 file system supports a directory for user files, called user. The size of
the user directory varies per device and is determined by the disk space that the
device can allot. You can copy files to and from the user directory, and delete
ETX2 File Operations 10-9

files that are not in use. User file names are strings between 1 and 32 characters
long.
Commands for Copying Files

You can copy or transfer files via the copy command, or via the commands shown
in Table 10-2. As shown in the table, some commands that reset the device also
erase the saved user configuration by copying another file to it before the reset.
Table 10-2. Commands That Copy Files
Command Level Copies… Additional Manual Section

Actions
save Global running-config to startup-config None Saving Configuration

Changes (in Operation
chapter)
factory-default Admin factory-default to startup-config Unit resets Resetting to Factory

after copying Defaults
user-default Admin user-default-config to startup-config Unit resets Resetting to User

after copying Defaults
Using SFTP or TFTP

You can download or upload files to the ETX2 unit via SFTP/TFTP. Normally the
types of files copied are configuration files and software files.
The software files can also be downloaded to ETX2 via the Boot Manager, using
XMODEM, SFTP, or TFTP. For details on upgrading the device software, refer to
the Software Upgrade chapter.
SFTP Application
The SFTP protocol is used to provide secure file transfers via the product's
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.
A variety of third-party applications offer SFTP server software. For more
information, refer to the documentation of these applications.
Setting up SFTP Server

If you use a local laptop and SFTP is the preferred transfer method, a SFTP server
application must be installed on it.
As mentioned above, third-party applications are available and you should refer
to their setup documentation.
Note SFTP file transfers are carried out through TCP port 22. You should check that the
firewalls you are using on the server and Windows allow communication through
this port. If not, configure the firewall settings to open TCP port 22.
10-10 File Operations ETX2

TFTP Application
The TFTP protocol is typically used for remote IP-to-IP file transfers via the
product's Ethernet interface. It can be used, however, for local file transfer as
well, 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. As it runs in the background, the TFTP server waits for any
TFTP file transfer request originating from the product, and carries out the
received request automatically.
A variety of third-party TFTP applications are available that allow the instant
creation of a TFTP server on a client computer. For more information, refer to the
documentation of these applications.
Setting up a TFTP Server

If you use a local laptop and TFTP is the preferred transfer method, a TFTP server
application must be installed on it.
As mentioned above, third-party applications are available and you should refer
to their setup documentation.
Note TFTP file transfers are carried out through UDP port 69. You should check that
the firewalls you are using on the server and Windows allow communication
through this port. If not, configure the firewall settings to open UDP port 69.
Configuring TFTP Server Timeout Settings

You can set the following TFTP server timeout settings from the system context.
• retry-timeout – the minimum number of seconds between attempts to
reconnect to the TFTP server. If the TFTP server connection fails, the device
can resend a request only after the time defined in retry-timeout has
elapsed. Retries to reconnect to the TFTP server can continue until the time
defined in timeout (following command) has elapsed.
• timeout – TFTP session timeout in seconds. When the TFTP connection fails
for the defined timeout (in seconds), despite retries, the connection to the
TFTP server times out, and a timeout error message is generated.
 To set the TFTP timeouts:

2. At the config>system prompt, perform the required tasks from the following
table.
Setting the number of retry-timeout <seconds> timeout-seconds – the number of seconds required between
seconds required between attempts to reconnect to the TFTP server
attempts to reconnect to Possible values: 1-60
TFTP server Default: 15

Setting the TFTP server timeout <timeout-seconds> timeout-seconds – the number of seconds after which the TFTP
connection timeout server connection terminates
Default: 60
Adding a File Description

You can use the description command to attach a description to any file.
Note Although you can add a description to any file, it is typically added to user files.
 To add a description to a file:

• At the file prompt, enter description <filename> <string>
If a user file, filename comprises the directory name (user) followed by a /
and the filename. For example: user/my-user-file.
string – up to 255 characters. If string is more than one word, it should be
enclosed in quotes (“”).
Note You can remove the file description by entering no description. This sets the
description to an empty string (the default).
Copying Files
You can use the copy command to copy files within the ETX2 unit, or
download/upload files to the ETX2 unit via SFTP/TFTP.
Note Syslog local accounting-log file can be uploaded; it cannot be downloaded.
 To copy files:
• At any prompt, enter:
copy <source-file-url> <destination-file-url>
Where:
• <file-url> = <url-prefix> <file>
• <url-prefix> can be empty, or one of the following:
 tftp://<ipv4-address>/
 tftp://[<ipv6-address>]/
 sftp://<username>:<password>@<ipv4-address>[:<port>]/
 sftp://<username>:<password>@<ipv6-address>[:<port>]/
 xmodem:
Note It is not necessary to specify <port> when using the well-known SFTP port.

• <file> can be empty, or one of the following files, or the file name on a
remote computer if applicable. If <file> is on a remote computer it can
contain a path and file name, or just a file name.
 startup-config
 restore-point-config
 rollback-config
 running-config
 user-default-config
 factory-default-config
 log
 sw-pack-1
 sw-pack-2
 sw-pack-3
 sw-pack-4
 zero-touch-config-xml
 banner-text
 pm-0
 db-schema
 mac-table
 db-config
 1tm_1
 1tm_2
 1tm_9
 schedule-log
 accounting-log (can be uploaded; not downloaded)
 sniffer-file
 user-script
 script-result
• The maximum length/range is:
 <username> – 1–60 characters
 <password> – 1–60 characters
 <file> – 1–96 characters
 <port> – 1–65535
Examples
Copying Files Within Device

• Source file name – running-config

• Destination file name – startup-config

copy running-config startup-config
Downloading via TFTP

• TFTP server address – 192.10.10.10
• Source file name – d:/img/ETX2.img
• Destination file name – sw-pack-2
copy tftp://192.10.10.10/d:/img/ETX-2.img sw-pack-2
Uploading via TFTP

• TFTP server address – 192.10.10.10
• Source file name – startup-config
• Destination file name – c:/etx/config/db1conf.cfg
copy startup-config tftp://192.10.10.10/c:/etx/config/db1conf.cfg
Downloading via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – bin/ETX2.img
• Destination file name – sw-pack-2
copy sftp://admin:1234@192.20.20.20/bin/ETX-2.img sw-pack-2
Uploading via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – startup-config
• Destination file name – config/db1conf.cfg
copy startup-config sftp://admin:1234@192.20.20.20/config/db1conf.cfg
Viewing Copy Status

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

• At the file# prompt, enter:
show copy [summary]

Viewing Information on Files

You can display the following information:
• Files within the device
• User files within the User directory
• Information on the configuration files
• Contents of configuration text files
• File details
• Information on the software files (software packs). For information on
upgrading to a different software pack, refer to the Software Upgrade
chapter.
Viewing Device Files

ETX2 supports the dir command to show a list of all non-hidden files on the
device, sorted by type and then by name.
 To display the files within the device:

• At the file# prompt, enter dir.

Example
ETX-2# file
ETX-2>file# dir
Codes: C-Configuration S-Software L-License LO-Log O-Other B-Banner U-
User
Name Type Size(Bytes) Creation Date Status
accounting-log LO 4078 1970-01-01 Read Only

00:00:03 File In
Use
db-config LO -- 1970-01-01 File In
Use
00:00:03
db-schema LO -- 1970-01-01 Read Only
00:00:03
mac-table LO -- 1970-01-01 Read Only
00:00:03
pm-0 LO 18 1970-01-01 File In
Use
00:00:12
schedule-log LO 2500 1970-01-01 Read Only
00:00:03 File In
Use
sw-pack-1 S 21434853 1970-01-01
14:06:12
sw-pack-2 S 21430702 1970-01-01 File In
Use
00:15:41
startup-config C 18897 1970-01-01
00:06:35
user-default-config C 10226 1970-01-01
00:07:33
factory-default-config C 903 1970-01-01 Read Only
00:00:04
running-config C -- 1970-01-01 File In
Use
15:35:04
restore-point-config C 8124 1970-01-01 Prev In
Use
14:45:50
log LO 660000 1970-01-01 Read Only
00:00:13
Total Bytes : 85618688 Free Bytes : 41121792
Bytes Available for PM : 4999982
Viewing User Directory Files

ETX2 supports the dir folder [user] command to list the user files in the device’s
user directory, sorted by name.
 To display user files:

• At the file# prompt, enter dir folder [user].

Note It is optional to enter folder-name, as user is currently the only available folder in
the device.
Example
ETX-2# file
ETX-2>file# user-file-dir
Name Type Size (bytes) Created Status
------------------------------------------------------------
my-default-config U 2500 01.10.2017 read only
00:00:10
Bytes Used: 100202600, Available: 948373400
Viewing Device Configuration Files
 To display information on the configuration files:

show configuration-files
Information on the configuration files is displayed.
Example
ETX-2# file
ETX-2>file# show configuration-files
Configuration Last Modified Valid
-----------------------------------------------------------------------------
startup-config 2012-08-02 18:19:07 Yes
factory-default-config 2012-08-13 17:18:07 Yes
running-config 2012-04-10 00:00:06 Yes
Device loaded from : startup-config
running-config has been modified since last time it was equal to startup-config
Viewing File Details

You can use the file-details command to display file details. Possible Status values
are: --, error in file, invalid header, not confirmed, loading failed, CRC error,
temporarily in use, read only, copy in progress, corrupted, migration failed, error
in migration, in use.
 To display file details:

At the file# prompt, enter:
show file-details <filename>
filename - for a user file, filename comprises the directory name (user) followed
by a / and the filename. For example: user/my-user-file.

ETX-2# file
ETX-2>file# show file-details user/my-user-file
Name : user/my-user-file
Size (bytes): 5000
Created : 01.10.1949
Status : --
Description : Running configuration backup from 1 October
Viewing File Contents

You can use the show command to display the contents of text files stored in the
file system.
 To display the contents of non-user 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 the contents of user text files (i.e. files stored in the /user directory):
• At the file# prompt, enter show user-dir <filename>.
Note You can only display the contents of a user file that is not binary.
 To display the contents of the running-config file:

• From any level (global command), enter show running-config.
 To display information on the software files:

show sw-pack [refresh [<sec>]]
where sec represents the refresh timeout, with range 3–100.
Information on the software files is displayed. The State of a SW file can
be one of the following: active, ready, corrupted, downloading, previous
active.

Example
ETX-2# file
ETX-2>file# show sw-pack
Name Version Creation Time State
-------------------------------------------------
sw-pack-1 2.10 01-10-1949 00:00:01 active
sw-pack-2 2.15 01-10-1949 00:00:10 ready
sw-pack-1 Size (bytes): 100000000

Type Name Ver H/W Ver Size (bytes)
------------------------------------------
Main SW mc 2.10 1.0 10000000
GBE SW gbe 2.10 1.0 20000000
MS SW ms 2.10 1.0 70000000
sw-pack-2 Size (bytes): 6700

Type Name Ver H/W Ver Size (bytes)
------------------------------------------
Main SW mc 2.15 1.0 1100
GBE SW gbe 2.10 1.0 2200
MS SW ms 2.15 1.0 3400
Deleting Files
You can delete the following files:
• restore-point-config
• rollback-config
• script-result
• startup-config
• sw-pack-<n>
• user-default-config
• user-script
• zero-touch-config-xml
When you delete or override a software pack file, ETX2 displays a message:
Previous software deleted; restore point lost.
When you delete the restore-point-config file, ETX2 displays a message: restore-
point-config delete; restore point lost.
Note Use caution in deleting files.
 To delete a file:
1. At the file# prompt, enter:
delete <file-name>
You are prompted to confirm the deletion.
2. Confirm the deletion.

Example
ETX-2# file
ETX-2>file# delete startup-config
! The file will be erased. Are you sure? [yes/no] _yes
10.5 Inventory
The ETX2 inventory table displays the unit’s components, hardware and software
revisions, and power supply types. You can display an inventory table that shows
all installed components, and you can display more detailed information for each
component. You can configure an alias name, asset ID, and serial number for
inventory components.
Applicable Products
This feature is applicable to all ETX2 products; however, the inventory display
differs for each product according to the different chassis components and port
configurations. <slot> is relevant for ETX203AM or ETX220A.
Note
PMC does not support the show summary-inventory command. However,
inventory information is stored in the MIB table entityTable, which can be read via
SNMP.
Standards
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.
Viewing Inventory Information

 To display the inventory table:
• At the config>system# prompt, enter:
show summary-inventory
The inventory table is displayed (see Example for a typical inventory table
output).
You can display more information for each installed inventory component. To do
so, you need to enter the inventory level with the corresponding inventory
component index, which is displayed in the Index column in the output of
show summary-inventory.
10-20 Inventory ETX2

 To display the inventory component information:

1. Navigate to configure system inventory <index>.
2. Enter:
show status
Information for the corresponding inventory component is displayed (see
Table 10-3 for information on the parameters).
Table 10-3. Inventory Parameters
Description Description of component type, in the form:
RAD.<device-name>.< Physical Class>, e.g. RAD.ETX2.Port
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 1001 for all other components, as they
are all contained in the chassis.
Physical Class Class of component
Possible values: Chassis, CPU, Power Supply, Fan, Sensor, Port, Container,
Module
Relative Position Contains the relative position of this component among other components
in the same index range (e.g. index 4001–4002, etc.)
Name Name of component

Possible values (according to component type):
<device-name> – Chassis
CPU
PS-AC/DC <n>
PS-AC <n>
PS-DC <n>
Fan <n>
Temperature Sensor <n>
External Clock
ETH Port [<slot>/]<n>
MNG Port
RS-232 Control Port
Time of Day Port
Mini BNC
External Clock Port
HW Rev Hardware version (relevant only for chassis)
SW Rev Software version (relevant only for chassis)
FW Rev Firmware version (relevant only for chassis)
Serial No. 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
ETX2 Inventory 10-21

FRU Indicates whether this component is a field replaceable unit that can be
replaced on site.
For ETX2 this is normally true only for the chassis, and for the dual power
supplies.
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 shown in the
Index column in the output of show summary-inventory.
 To set inventory component information:

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

component the alias.
Note: Configuring the alias is
meaningful only for the chassis
component. It can be used by a
network manager as a
non-volatile identifier for the
device.
Assigning user-specific asset identifier asset-id <id> Using no before asset-id

to the component (usually for removes the asset ID.
removable physical components)
Assigning vendor-specific serial serial-number <string> Using no before serial-number

number to the component removes the serial number.

Examples
 To display inventory summary for ETX203AM with SHDSL module:
ETX-203AM# configure system
ETX-203AM# config>system# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW Ver
-----------------------------------------------------------------------------
1001 Chassis ETX-203AM 0.00 6.51 (0.11) 1.5.1.0.0.0.0.8
3001 Container Slot 1
4001 Fan Fan 1
4002 Power Supply PS-AC 1
5001 Module SHDSL 8W
7001 Port RS-232 Control Port
7002 Port MNG Port
7003 Port ETH Port 0/3
7007 Port SHDSL Port 1/1
8001 CPU CPU
 To display inventory information for ETX203AM SHDSL port 1/1:

ETX-203AM>config>system# inventory 7007
ETX-203AM>config>system>inventory(7007)# show status
Description : ETX-203AM SHDSL Port 2W/4W/8W
Contained In : 5001
Physical Class : Port
Relative Position : 7
Name : SHDSL Port 1/1
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : False

 To display inventory summary for ETX203AM with VDSL module:

ETX-203AM# configure system
ETX-203AM# config>system# show summary-inventory
-----------------------------------------------------------------------------
1001 Chassis ETX-203AM 1.0/E 6.51 (0.11) 1.5.1.0.0.0.0.9
4001 Fan Fan 1
5001 Module VDSL-MODULE ACB 1.00(UHZ.0)b9 1.2
5002 Module VDSL PORT 1/1
5006 Module PCS PORT 1
7002 Port MNG Port
8001 CPU CPU
 To display inventory information for ETX203AM VDSL port 1/1:

ETX-203AM>config>system# inventory 5002
ETX-203AM>config>system>inventory(5002)# show status
Description : VDSL-PORT-1
Contained In : 0
Physical Class : Module
Name : VDSL PORT 1/1
HW Ver :
SW Ver :
FW Ver :
Serial Number : Put your string here
MFG Name : Put your string here
Model Name : Put your string here
Alias :
Asset ID : Put your string here
FRU :

 To display inventory summary for ETX203AX-DSL:

ETX-203AX-DSL>config# system
ETX-203AX-DSL>config>system# show summary-inventory
-----------------------------------------------------------------------------
1001 Chassis ETX-203AX-DSL 0.0/ 6.5.0(0.2) 1.5.1.0.0.0.0.9
4001 Power Supply PS 1
7002 Port MNG Port
7003 Port ETH Port 1
7004 Port SHDSL Port 1
8001 CPU CPU
Note
The ETX203AX factory default chassis name specifies the ordering option; in this
example, ETX203AX-DSL.
 To display inventory summary for ETX203AX (fiber):

ETX-203AX# configure system
ETX-203AX# config>system# show summary-inventory
-----------------------------------------------------------------------------
1001 Chassis ETX-203AX 0.00 6.51 (0.11) 1.5.1.0.0.0.0.8
4001 Power Supply PS-AC/DC 1
7002 Port MNG Port
8001 CPU CPU

 To display inventory information for ETX203AX Ethernet management port:

ETX-203AX>config>system# inventory 7002
ETX-203AX>config>system>inventory(7002)# show status
Description : MNG Port
Contained In : 1001
Name : MNG Port
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : False
 To display inventory summary for ETX205A:

ETX-205A# configure system
ETX-205A# config>system# show summary-inventory
-----------------------------------------------------------------------------
1001 Chassis ETX-205A 0.00 6.51 (0.11) 1.5.1.0.0.0.0.8
4001 Fan Fan 1
4002 Fan Fan 2
4003 Sensor Temperature Sensor 1
4004 Power Supply PS-AC 1 0
7001 Port Time of Day Port
7002 Port Mini BNC
7003 Port External Clock Port
7005 Port MNG Port
8001 CPU CPU

 To display inventory information for ETX205A power supply:

ETX-205A>config>system# inventory 4004
ETX-205A>config>system>inventory(4004)# show status
Description : ETX-205A Power Supply 1
Contained In : 3001
Physical Class : Power Supply
Name : PS-AC 1
HW Ver : 0
SW Ver :
FW Ver :
Serial Number : EA100390472
MFG Name : RAD DATA COMMUNICATIONS Ltd.
Model Name :
Alias : POWER-SUPPLY-1
Asset ID :
FRU : True

 To display inventory summary for ETX220A:

ETX-220A# configure system
# config>system# show summary-inventory
-----------------------------------------------------------------------------
1001 Chassis ETX-220A 0.00 6.51 (0.11) 3.0.0.0.0.0.1.5
4001 Fan Fan 1
4002 Fan Fan 2
4003 Fan Fan 3
4004 Fan Fan 4
4005 Fan Fan 5
4006 Sensor Temperature Sensor 1
7001 Port External Clock Port
7003 Port MNG Port
8001 CPU CPU

 To display inventory information for ETX220A 10GbE port 4/1:

ETX-220A>config>system# inventory 7004
ETX-220A>config>system>inventory(7004)# show status
Description : ETX-220A Ethernet Port
Contained In : 1001
Name : ETH Port 4/1
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : False
10.6 Licensing
Some features require a license to be enabled before the feature can be
configured.
The following licenses are available:
• TWAMP
• Traffic Management Fault Propagation (TMFP)
Note You should only activate features on a device after acquiring the appropriate
license from RAD (through a license order or specific device ordering options).
Activating a license-based feature without acquiring the appropriate license shall
be considered a breach of your undertakings and entitles RAD to stop supporting
the device and may also result in legal action.
Applicable Products
Benefits
The license mechanism enables fewer software version variants to be produced.
Also, it can be used to track licensed feature usage.
Factory Defaults
By default, feature licenses are disabled.
ETX2 Licensing 10-29

A feature that requires a license can be configured only if the feature license is
enabled.
For backward compatibility, in the event that a feature was defined as requiring a
license after having already been released without a license in a previous
software release, the feature configuration is allowed if it was done in a release
that did not require a license. In this case, a command enabling the license is
automatically added to the running-config file.
If ETX2 loads a configuration file that configures a feature requiring a license
when the license is not enabled, the device rejects that feature’s configuration if
the configuration file was created by a software version that requires a license.
Fault Propagation Event Manager License

Use of standard fault propagation features does not require a license. However,
use of enhanced Fault Propagation Event Manager actions, such as shaper-swap
(for changing queue block shaper rate) and policer-swap (for changing flow
policer rate), as well as use of enhanced triggers, requires an enabled Traffic
Management Fault Propagation (TMFP) license.
Configuring Licenses
The ETX2 TWAMP and enhanced Fault Propagation Event Manager features
require a license.
Traffic Management Fault Propagation (TMFP) license and TWAMP license in a VNF
(not in a device) are protected by a hardcoded password only known to you.
Configuration of the enhanced FP Event Manager or TWAMP (in VNF) features
requires you to enable the respective password-protected licenses.
 To enable licenses:
1. Navigate to admin license.
The admin>license# prompt is displayed.
Enabling TWAMP license in license-enable twamp

device
Enabling TWAMP license in license-enable twamp password – hardcoded password assigned to the device
VNF <password> [hashed] hashed – If this option is specified, the device assumes the
Enabling Traffic license-enable tmfp <password> entered password is hashed. If not specified, the device assumes
Management Fault [hashed] the password is plain text (non-ecrypted), and if correct, hashes
Propagation (TMFP) license the password, and saves the hashed result in the license hard
password feature.
10-30 Licensing ETX2

Disabling license no license-enable <feature> feature – licensed feature

Possible values:
tmfp
twamp
Notes:
• You can disable a license, provided running-config does not
contain a configuration that is prohibited without a license.
• You can disable the TMFP license, provided enhanced Fault
Propagation Event Manager actions have not been configured.
• You can disable the TWAMP license, provided TWAMP entities
have not been configured.
Viewing License Status Summary

You can generate a summary of all the feature licenses in the device.
Example
This example displays the license summary.
ETX-2>admin>license# show summary
Feature Status Amount In Use
-----------------------------------------------
TWAMP Disabled -- --
TMFP Enabled -- Yes
Table 10-4. License Summary Parameters
Feature Feature name
Possible values:
TMFP (Traffic Management Fault Propagation)

TWAMP
Status License status
Possible values: Enabled, Disabled
Amount License amount
Possible values:
-- : not applicable (for TMFP and TWAMP)
In Use Indicates whether or not the license is in use.

Possible values:
-- : not applicable (for disabled license)
Yes/No: indicates whether or not enabled TMFP or TWAMP license is in use
ETX2 Licensing 10-31

The following table lists messages generated by ETX2 when a configuration error
is detected.
Message Description
License needed by running configuration You attempted to disable the license for a feature that is
configured in the device running configuration.
License required You attempted to configure a feature that requires a license,

and the license is disabled.
Wrong password You failed to set the correct password for the device.
10.7 Login Banner
Applicable Products
Defining Login Banners

You can define a banner to be displayed before the login prompt for user name,
as well as a banner to be displayed following successful login. You can define the
pre-login banner using the CLI command login-message, and the post-login
banner using the CLI command announcement. A banner file can also be used to
define a pre-login banner, provided it is supported in the device. Although the
banner file is maintained for backward compatibility, it is recommended to use a
CLI command to define the pre-login banner. Note that a device cannot
simultaneously support a banner file and banner command.
Note If you are accessing ETX2 via SSH, the banner is printed between the user name
prompt and the password prompt.
Defining Login Banners via CLI Commands

You can define a banner to be displayed before login, as well as another banner
to be displayed following login.
Pre-login and post-login banner messages must satisfy the following:
• Message must be enclosed in single quotation marks.
• Pressing <Enter> before entering a closing quotation mark, results in the
device displaying the warning message:
Enter message. End with the single quotation character (‘).
• A message that spans multiple lines is interpreted as if it were written in one
line; <cr> and <lf> between lines in the configuration file or command are
ignored.
10-32 Login Banner ETX2

• A message can contain printable characters, as well as the following special

characters (only relevant for CLI; from SNMP, these characters should be
entered normally):
 \n – new line
 \t – horizontal tab
 \’ – single quotation mark
 \\ – backslash
• Usage of special characters reduces the maximum number of printable
characters that the banner can contain. For example, if the banner contains
\n, up to 1998 additional printable characters can be used.
• The banner can be up to 2000 characters (including the escape / characters).
If you try to configure a longer banner, the device prints the following CLI
error: Banner may not exceed 2000 characters.
 To configure a pre-login banner:

2. Type login-message <message>, enclosing the message in quotes.
At the next login, this pre-login banner is displayed.
If a bannertext file already exists in the device, the device rejects the
command and displays the CLI error message:
Cannot configure banner while bannertext file exists
Note Type no login-message to remove a previously configured pre-login banner.
 To configure a post-login banner:

2. Type announcement <message>, enclosing the message in quotes.
After the next login, this post-login banner is displayed.
Note Type no announcement to remove a previously configured post-login banner.
You can display the banners configured for ETX2 by navigating to the device level
and entering info. For example:
ETX2 Login Banner 10-33

ETX-2# info
version "3.01A14" sw "5.9.1(0.08)"
configure
echo "System Configuration"
# System Configuration
system
login-message 'Authorized Users Only'
announcement 'Successful Login!'
exit
The configured banners are displayed before and after login, as shown below.
Authorized Users Only
user>su
password>****
Successful Login!
ETX-2#
Defining Pre-Login Banner Using a Banner File
 To define the banner using a banner file:

1. Create a text file called banner-text that contains the banner to display.
Notes • The banner must contain only printable ASCII characters (0x20–0x7E), <Enter>
(0x0D), <Line Feed> (0x0A), and <Tab> (0x09)
• The banner can contain up to 2,000 characters.
2. Transfer the file banner-text to ETX2.

At the next login, the banner is displayed.
If the device already contains the pre-login CLI command login-message,
the device rejects the banner-text file download and displays the CLI
error: Cannot load bannertext file while login-message is configured.
You can display the banner defined for ETX2 by navigating to the file level and
entering show banner-text, as shown in the example below.
ETX-2# file
ETX-2>file# show banner-text
******* Authorized users only *******
Given the above banner file, the banner is displayed before login, as shown
below.
******* Authorized users only *******
user>
10.8 Sending a Message to Connected Users

ETX2 enables any connected su level user – local or remote (console, TELNET,
SSH, and more) to send a message of up to 2000 characters to all other
connected CLI users.
10-34 Sending a Message to Connected Users ETX2

• The command is not saved in the configuration file and cannot be invoked
from a configuration file.
• The message cannot be sent while the running configuration is being saved.
 To send a message:
1. Navigate to admin.
2. Execute send <message>.
where message is a character string up to 2000 characters long.
Confirmation is requested to send the message:
Send message? [yes/no]
3. Enter yes to confirm sending the message.
The device outputs the following:
***
*** Message from <terminal name> to all terminals:
***
<message>
Where <terminal name> is either tty or vty#.
Applicable Products
Benefits
Allowing users to send messages to other users simplifies on-site operation.
Example
This example displays sending a message to other users.
ETX-2>admin# send Reminder: System rebooting at 21:00
Send message? [yes/no] _ yes
***
*** Message from vty1 to all terminals:
***
Reminder: System rebooting at 21:00
The following table lists the message generated by ETX2 when a configuration
error is detected.
ETX2 Sending a Message to Connected Users 10-35

Message Description
Message may not exceed 2000 You entered a message longer than 2000 characters.
characters
10.9 Reset
ETX2 supports the following types of reset:
• Reset to factory defaults
• Reset to user defaults
• Overall reset (restart) of the device
• Reset x86 card of PMC-enabled devices
Note You can request that the active software pack be confirmed after the next reboot
of ETX2. Refer to the description of installing software in the Software Upgrade
chapter for details.
Applicable Products
This feature is applicable to all ETX2 products, with the exception that reset of
the x86 card is applicable only to ETX205A with PMC option.
Resetting to Factory Defaults

You can reset ETX2 to its factory defaults using either of the following
commands:
• factory-default – for customer use
factory-default-all – for use by RAD Operations personnel prior to releasing the
device for shipment, in order to revert the device to its prior-to-shipment
stateThe factory-default and factory-default-all commands have the following
differences:
• factory-default always reloads the device with factory-default-config.
factory-default-all reloads the device with user-default-config, if it exists;
otherwise, with factory-default-config.
• factory-default only deletes startup-config.
factory-default-all clears the log files and deletes most files, with the
exception of factory-default-config, user-default-config, licenses, banners,
software, mac-table, pm (including the legacy statistics collection file),
db-schema, and db-config. It also resets file creation times in the file system.
• factory-default-all resets the snmpEngineBoots parameter to 1. This
parameter counts the number of times the SNMP engine was restarted, and
is maintained throughout reboots to prevent replay attacks.
10-36 Reset ETX2

Note It is not recommended for customers to use the factory-default-all command, as

it resets the SNMP object (snmpEngineBoots). This can result in the management
station incorrectly assuming that the original device was replaced by another
impersonating device, and therefore the management station will refuse to
communicate with the device. In such cases, the manager must manually delete
the device from the map and then redraw it. To avoid such issues resulting from
the resetting of snmpEngineBoots, it is recommended to use instead user-default
or factory-default and then manually delete unneeded files and clear logs, as
required.
 To reset ETX2 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
unit resets, and after it completes its startup the factory defaults are
loaded. If a startup-config confirm request was active, it is canceled.
 To reset ETX2 to factory defaults and revert the device to its prior-to-shipment
state:
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 explained above is performed, the
unit resets, and after it completes its startup the factory defaults are
loaded. If a startup-config confirm request was active, it is canceled.
Resetting to User Defaults

You can use the user-default command to reset ETX2 to the configuration
stored in user-default-config, a file which contains user default parameters that
are usually different from RAD’s factory default parameters.
 To reset ETX2 to user defaults:

user-default
Current configuration will be erased and device will
ETX2 Reset 10-37

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 unit
resets, and after it completes its startup the user defaults are loaded. If a
startup-config confirm request was active, it is canceled.
Restarting the Unit

If necessary, you can restart ETX2 without interrupting the power supply.
Note Rebooting ETX205A with PMC also reboots the x86 card.
 To restart ETX2:
reboot
Device will reboot. Are you sure? [yes/no]
2. Enter yes to confirm the reset.
The unit restarts.
Resetting the x86 Card

When restarting the ETX205A unit with x86 card using admin reboot, the x86
card also restarts. This section describes how to reset the x86 card only, without
rebooting the device.
Note You can reset the x86 card from the x86 screen only (chassis ve-module).
 To reset the x86 card:

1. Navigate to configure chassis ve-module.
The config>chassis>ve-module# prompt is displayed.
2. Enter:
reset
If the x86 card is up and running, it resets.
10-38 Reset ETX2

10.10 Tech-Support Commands

ETX2 supports a show tech-support command, which you can use to display on
the terminal a predefined series of CLI commands, such as general device status
and statistics, and if specified, store in a script file.
Applicable Products
Benefits
You can view or save in a file general device status and statistics.
Factory Defaults
By default, the show tech-support command is predefined with the following
commands in order:
• show configure system system-date
• show configure system device-information
• show configure system memory-details
• show configure system buffers
• show configure system summary-inventory
• show file sw-pack
• show file copy
• show configure port summary
• show configure service
• show configure flows summary details
• show configure oam cfm summary
• show configure pwe summary
• show configure system clock domain1 status
• show configure protection erp-summary
• show configure router 1 arp-table
• show configure router 1 routing-table
• show configure management users-details
• show configure reporting active-alarms
ETX2 Tech-Support Commands 10-39

When the tech-support command is invoked, its output is displayed on your
terminal, and if specified, stored in a script file called script-result (, which can
afterwards be displayed or downloaded).
For each command, the following is displayed:
• A timestamp – formatted <date> <time> UTC {+|-}<hours>:<minutes>; for
example: 2015-05-35 11:10:09 UTC +02:00
• The executed command
• The command output, including errors and other messages, provided that the
command was invoked with the terminal argument (If the file argument is
invoked, the command output is stored in a file instead of being displayed on
the CLI terminal.)
Unlike other commands, the output is sent to the screen continuously, without
pausing after each page.
The CLI prompt does not return until all commands included in the script are
executed, or you stop the execution.
The terminal inactivity timer does not decrease while the script is being executed,
so the terminal remains open even if it takes a long time.
The script-result file is automatically cleared each time the show tech-support
command is invoked.
Showing the Tech-Support Commands

 To show the tech support commands:
2. At the config>system# prompt, enter show tech-support [file|terminal].
The commands and their output are displayed.
10-40 Tech-Support Commands ETX2

Chapter 11
Monitoring and
Diagnostics
The following are described in this chapter:
• In-Service ICMP Echo Ping Test
• OAM CFM (Connectivity Fault Management)
• OAM EFM
• TWAMP
• Layer-3 Service Activation Test
• RFC-2544 Testing
• Syslog
• Y.1564 Ethernet Service Activation Test
• Performance Management
• Detecting Problems
• Handling Alarms and Events
• Troubleshooting
• Performing Diagnostic Tests
• Frequently Asked Questions
• Technical Support
11.1 In-Service ICMP Echo Ping Test

In many cases, users want to be able to ping the Layer-2 EVC at the device for
diagnostic purposes. The in-service ICMP Echo ping test provided by ETX-2
enables you to activate a simple command to send a ping and check the
connectivity across Layer-2 service paths for diagnostic purposes.
Applicable Products
ETX-2 In-Service ICMP Echo Ping Test 11-1

Chapter 11 Monitoring and Diagnostics Installation and Operation Manual
Benefits
This test requires a single CLI command to perform a simple connectivity check
across Layer-2 service paths, without the need for configuration of a full TWAMP
controller and responder.
Layer-2 Ether-Access devices have the ability to initiate a connectivity test, and
also respond to in-service ping requests sent over Layer-2 services to a
configured IP address.
The in-service ICMP Echo ping test pings the Layer-2 EVC of the device from the
flow level. The in-service ping includes a mechanism to enable performing a
connectivity test across the flow inside the device, by configuring ICMP packets’
entry-point to the flow, either at the flow ingress or egress. The in-service ping
runs independently of working routers.
The in-service test requires that the devices be activated in two modes:
Generator Device sends ping messages.
Responder Device receives ping messages and sends a reply.
A single ICMP Echo instance is supported – Generator or Responder.

In-service ICMP Echo is supported in the following topologies:
• PtP E-line service
• MP to MP E-LAN (bridge) services
• MP to MP (or P to MP) E-Tree services
PtP E-line Service

• IPv4 only
• Two configurable probing scopes:
Up In-service ping request/response packets are injected at

the ingress port of the service and mimic frame traverse of
the UNI/NNI flow chain.
Down In-service ping request/response packets are injected

directly at the egress port of the service using the highest
priority queue.
11-2 In-Service ICMP Echo Ping Test ETX-2

Installation and Operation Manual Chapter 11 Monitoring and Diagnostics
ETX-2
Ping VRF
TWAMP
Router
Inte rfa ce
Ping
ETH Policer ETH

Port Port
Figure 11-1. ICMP Echo – PtP E-Line Services
MP to MP E-LAN (bridge) Services

• IPv4 only
• Where bridge is used, in-service ping probing-scope is injected to the bridge
only, and generated towards any port connected to the specific VPN.
ETX-2
Ping VRF
Router
Inte rfa ce
Bridge
Port
Ping
ETH ETH
Port Bridge Port
Figure 11-2. ICMP Echo – Bridge Services
MP to MP (or P to MP) E-Tree Services

• IPv4 only
• Where bridge is used, in-service ping probing-scope is injected to the bridge
only, and generated towards any port connected to the specific VPN.
• The internal bridge port from which the in-service ping-request is sent must
be configured as root for the given Layer-2 VPN. The responder listens to in-
service ping-requests received from the root bridge port on the specified
VPN and replies with an in-service ping response on the same root bridge
port.
• Not supported for ETX-203/205 (A sanity check is performed, and if it fails,
an error message is generated.)

Configuring the In-Service ICMP Echo Ping Test

To configure the in-service ICMP Echo ping test:
1. Configure the in-service ping response – at the device that responds to the
ping-request packets with ping-response packets. You can configure the IP
stack to start and listen to ping-requests being sent over a particular flow,
targeted to a provisioned IP address.
2. Configure the in-service ping request – at the device generating the ping
test.
It is not possible to save the in-service ping responder configuration. It is erased
on reset, and does not appear in the info command.
When you invoke the commands, a temporary IP interface is created on the
device, as well as a routing entry in the static-route table. When the test has
completed, all IP context on the generator side that is related to the test is
cleared; the IP context on the responder side must be cleared manually.
Configuring In-Service ICMP Echo Ping Response
Note In PtP mode, a service (flows) with corresponding classification must exist on the
requested ingress port prior to in-service ping-response commands generation;
it is optional to configure an opposite matching flow. In the case that an
opposite matching flow does not exist, the service ping works in “down scope“
(default) without any warning.
 To configure an in-service ping response:

1. Navigate to ETX-2 configure flows.
The ETX-2>config>flows# prompt is displayed.
2. Type the following command, using the parameters described in Table 11-1:
service-ping-response {local-ip <local_ip_addr_and_subnetmask>} {next-hop
<next_hop_ip_address>} {egress-port <egress_port>|bridge <bridge_id>} [vlan
< vlan_id>] [inner-vlan <inner_vlan_id>] [p-bit < p_bit_id] [inner-p-bit
<inner_p_bit_id>][probe-scope <up|down>]
At any time, you can configure the device to cease listening to in-ping-requests,
by typing the command:
no service-ping-response
The device clears any generated command context (the local IP address and
routing entry).
Note Invoking no service-ping-response terminates the command that was initiated in

the same database session or in a different database session (same user or
different user).

Configuring In-Service ICMP Echo Ping Request
Note In PtP mode, a service (flows) with corresponding classification must exist on the
requested ingress port prior to in-service ping commands generation; it is
optional to configure an opposite matching flow. In the case that an opposite
matching flow does not exist, the service ping works in “down scope“ (default)
without any warning.
 To configure an in-service ping request:

1. Navigate to ETX-2 configure flows.
The ETX-2>config>flows# prompt is displayed.
2. Type the following command, using the parameters described in Table 11-1:
service-ping {local-ip <local_ip_addr_and_subnetmask>} {dst-ip
<destination_ip_addr>} {next-hop|<next_hop_ip_address>} {egress-
port<egress_port>|bridge<bridge_id>} [vlan < vlan_id] [inner-vlan
<inner_vlan_id>] [p-bit< p_bit_id] [inner-p-bit <inner_p_bit_id>] [probe-scope
<up|down>] [number-of-packets<number_of_packets>] [payload-
size<number_of_bytes>]
The next in-service ping request is transmitted after at least one second (hard-
coded) has elapsed from the transmission of the previous in-service ping
request, provided the previous in-service ping response packet has been
received. If the in-service ping response packet has not been received within
two seconds since it was sent (hard-coded timeout), the ping-packet is declared
lost, a message is echoed back to your-screen, and the next in-service ping
request is immediately transmitted.
The in-service ping test is automatically terminated after the transmission of the
‘number-of-packets’ in the in-service ping request and the reception of the
corresponding echoes.
You can terminate the in-service ping test before the number-of-packets have
been exhausted by clicking Ctrl-C or by typing the command:
no service-ping
The initiator interrupts the current in-service ping test and returns the following
termination message and test summary:
Ping is terminated by user:
<num_packet_tx> packets transmitted. < num_packet_rx> packets
received, <loss_percentage>% packet loss
round-trip (ms) min/avg/max = <rt_min>/<rt_avg>/<rt_max>
Note
Invoking no service-ping terminates the command that was initiated in the same
database session or in a different database session (same user or different
user).
Table 11-1. In-Service Ping Parameters
Parameter Description Value
local-ip The temporary IP address provisioned on the Valid IP address and subnet
sender/responder for the duration of the test, mask
combined with subnet-mask [0.0.0.0/32|0:0:0:0::0/128]

dst-ip The IP address to which in-service ping request packets Valid IP address
are destined [0.0.0.0|0:0:0:0::0]
next-hop Next hop to use when destination IP is out of the Valid IP address
source subnet [0.0.0.0|0:0:0:0::0]
egress-port Egress port for PtP services (E-Line). The physical (e.g. ethernet, pcs, or logical-
Ethernet port) or logical (e.g. bridge ID) interface from mac
which the ping request/response exits. Valid attribute
only when bridge parameter is not introduced.
bridge Bridge ID for bridged services (E-LAN/E-Tree service Valid bridge ID

probing). Valid attribute only when egress-port
parameter is not introduced.
vlan Together with egress-interface, defines the flow Possible values: 0–4094
Default: -1 (untagged)
inner-vlan Together with egress-interface, defines the flow Possible values: 0–4094
Default: -1 (untagged)
p-bit The service VLAN priority bit used when encapsulating Possible values: 0–7
the ping packet Default: 0 (untagged)
inner-p-bit The inner-VLAN priority bit used when encapsulating the Possible values: 0–7
ping packet Default: 0 (untagged)
probe-scope The in-service ping request/response probing mode. up/down

Applicable only for E-Line services, when egress-port is Default: up
selected. Not applicable when user selects bridge.
number-of-packets Number of in-service ping request packets for the test Possible values: 1–10000
Default: 5
payload-size Payload size of the in-service ping request packets Possible values: 32–1450
Default: 32
In-Service ICMP Echo Ping Test Results

Echo results (including RTT) are echoed back to the user terminal in a format
similar to the existing ping format.
For example, pinging IP address 172.17.155.83 with number-of-packets = 6 and
payload-size = 32:
Reply from 172.17.155.83: bytes = 32, packet number = 0, time < 10 ms
5 packets transmitted. 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0

Examples
The following example illustrates configuring in-service ping test over Eth
services. Layer-2 E-Line service is provisioned between device UNI and NNI.
 To configure the responder with an in-service ping response:

exit all
#********* Configure classifier for VLAN 100
configure
flows
match vlan 100
exit
#********* Configure Service between ETH 3 & 4
flow ping_E3toE4
classifier v100
no policer
no shutdown
exit
flow ping_E4toE3
classifier v100
no policer
no shutdown
exit
#*********In-Service Ping ********************************
service-ping-response local-ip 10.10.10.30/24 next-hop

10.10.10.20 egress-port ethernet 4 vlan 100
 To configure the generator with an in-service ping request:

exit all
configure
flows
match vlan 100
exit
#********* Configure Service between ETH 3 & 4
flow ping_E3toE4
classifier v100
no policer
no shutdown
exit
flow ping_E4toE3
classifier v100


no policer
no shutdown
exit
#*********In-Service Ping ********************************
service-ping local-ip 10.10.10.20/24 dst-ip 10.10.10.30 next-

hop 10.10.10.30 egress-port ethernet 4 vlan 100 probe-scope
down number-of-packets 5 payload-size 64
The following example illustrates configuring an in-service ping test over bridge
services. Layer 2 E-LAN service is provisioned between device UNI and an
internal bridge port.
exit all
configure bridge 1
vlan-aware
port 1
no shutdown
exit all
configure
flows
match vlan 100
exit
#********* Configure flows between ETH 3 & BP11

flow ping_E03_BP11
classifier v100
no policer
no shutdown
exit
service-ping-response local-ip 10.10.10.30/24 next-hop

10.10.10.20 bridge 1 vlan 100
#*********In-Service Ping ********************************
#*********In-Service Ping ********************************#

Parameter or keyword missing The entered service (outer) Configure a service (outer) VLAN that
or wrong VLAN, does not also populate also populates the customer (inner)
the customer (inner) VLAN in VLAN in the command.
the command.
Invalid parameter value; local-ip The next-hop address does Choose local IP and next-hop IP
and next-hop must belong to not belong to the same addresses in the same network.
the same network network as the sender address
(local IP address).
Invalid parameter value; local-ip The destination IP address Make next hop address equal to the
and next-hop must be equal as belongs to the same network local IP address.
dst-ip belongs to the same as the sender, but the next-
network hop address is not equal to
the local IP address.
11.2 OAM CFM (Connectivity Fault Management)

Ethernet OAM (Operation, Administration, and Maintenance) functions provide
end-to-end connectivity checks and performance monitoring.
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 is capable of transporting Ethernet service frames. ETX-2
also supports performance monitoring per Y.1731.
ETX-2 can act as a Maintenance Entity Group Intermediate Point (MIP) or
Maintenance Entity Group End Point (MEP). When ETX-2 acts as a MIP, it
forwards OAM CFM messages transparently, responding only to OAM link trace
(LTM) and unicast OAM loopback (LBM).
Applicable Products
• Dimensioning differs between the products; this is indicated where relevant.
Standards
IEEE 802.1ag-D8
ITU-T Y.1731
MEF 36
ETX-2 OAM CFM (Connectivity Fault Management) 11-9

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, the operators can offer binding service-level agreements.
Note OAM may trigger control plane or management plane mechanisms; for example,
by activating rerouting or raising alarms. However, such functions are not part of
the OAM itself.
OAM Elements
Maintenance entities (ME) that require management are grouped into ME groups
(MEGs, referred to as Maintenance Associations or MAs). The Ethernet OAM
mechanism monitors connectivity in Maintenance Association (MA) groups, each
identified by a Maintenance Association Identifier (MAID). Each MA consists of
two or more maintenance end points (MEPs). Each MA belongs to a maintenance
domain (MD), and inherits its level from the MD to which it belongs. The MD
levels are used to specify the scope of the MA (provider, operator, customer,
etc). The following entities are used for monitoring:
• Maintenance Domain (MD) – the network or part of the network for which
faults in connectivity can be managed. Each maintenance domain has an MD
level attribute which designates the scope of its monitoring.
• Maintenance Association (MA) – a set of MEPs, each configured with the
same MAID and MD level, established to verify the integrity of a single
service instance.
• Maintenance End Point (MEP) – an actively managed CFM entity. A MEP is
both an endpoint of a single MA, and an endpoint of a separate
Maintenance Entity for each of the other MEPs in the same MA. A MEP
generates and receives CFM connectivity messages and tracks responses.
See full description in Maintenance End Points (MEPs) section below.
• Maintenance Intermediate Points (MIPs) – intermediate entities that are
created in the middle of the domain. See full description in Maintenance
Intermediate Points (MIPs) section below.
• Services – used for performance monitoring of the relevant MEP
• Destination Network Elements (Dest NEs) – provide performance monitoring
for the relevant service
The MAC addresses used in the OAM CFM entities are as follows:
• Down MEPs use the MAC address assigned to the port bound to the MEP.
11-10 OAM CFM (Connectivity Fault Management) ETX-2

• Up MEPs use the MAC address assigned to the port to which the relevant
bridge port connects.
• MIPs use the MAC address assigned to the port they are bound to.
OAM Functions
RAD’s carrier Ethernet aggregation and demarcation devices feature
comprehensive hardware-based Ethernet OAM and performance monitoring for
SLA assurance.
ETX-2 provides the OAM (CFM) functions listed below in packet-switched
networks:
• End-to-end Connectivity Fault Management (CFM) per IEEE 802.1ag:
 Continuity check (CC)
 Non-intrusive loopback
 Link trace for fault localization
• End-to-end service and performance monitoring per ITU-T Y.1731
 Loss measurement (single-ended)
 Delay measurement (two-way).
Note Loss measurement is supported only if the MEP-connected flows have their
statistic counters enabled (PM-enabled).
OAM Connectivity
The figure below shows how the various levels of OAM sessions supported by
RAD equipment allow each entity to monitor the layers under its responsibility
and easily isolate problems. The Maintenance Entities (MEs) are created at
different levels:
• Lowest-level OAM session (subscriber ME) between two subscriber devices
(devices 1 and 8). ETX-2 devices serve as MIPs.
• End-to-end OAM session (EVC ME) between two ETX-2 devices, which serve
as MEPs. ETX-5 devices act as MIPs.
• Segment OAM session (operator service ME) between ETX-2 and the
network side of ETX-5.
• Transport OAM session (tunnel ME) between network ports of two ETX-5
devices.

Subscriber Subscriber
Equipment Operator A NEs Service Provider Operator B NEs Equipment
1 2 3 4 5 6 7 8
Subscriber ME
EVC ME
Ethernet
Operator A Service ME
Operator B Service ME
UNI ME UNI ME
Transport Tunnel ME
ETX-2 ETX-2
ETX-5 Router Router ETX-5
Legend:
Triangle – MEP (Maintenance End Point)
Circle – MIP (Maintenance Intermediary Point)
Figure 11-3. Multi-Domain Ethernet Service OAM
Maintenance End Points (MEPs)

MEPs are referred to as Up MEPs or Down MEPs, depending on their position and
port association.
• Down MEPs reside at port egress and are bound to physical ports. These
MEPs receive and send CFM PDUs from and to the network.
• Up MEPs reside at bridge ingress and are bound to bridge ports. These MEPs
receive and send CFM PDUs from and to the bridge.
A MEP is transparent to OAM frames that have an MD level higher than the MEP
level, and drops OAM packets that have an MD level lower than the MEP level. It
fully supports connectivity check (CC), loopback, link trace, and PM counters,
You can enable or disable (the default) Latching Loopback Function (LLF) for a
Down or Up MEP, which is configured with Rx and Tx flows (and not
Classification). This enables the MEP to perform simultaneous loopbacks for
different source MAC addresses. When LLF is enabled at the MEP level, the MEP
level responder can work with a third party generator. For example, the Y.1564
test generator can work with the MEP-level responder having LLF enabled,
eliminating the need to add a Y.1564 test responder.
The OAM packets transmitted by MEPs usually contain a service VLAN ID (S-tag)
and customer VLAN ID (C-tag). However, there are cases where the user side
C-tag is unknown. To handle this case, you can specify for E-line Up MEPs that
customer tags are excluded.
Down MEP
Down MEPs are supported for either point-to-point (E-Line) or multipoint (E-
LAN) services.

The figure below illustrates a point-to-point service between two ports with the
MEP bound to port B. Tx flow in the service is directed to a queue block.
Tx Flow
Port A MEP Port B
Rx Flow
Figure 11-4. Point-to-Point Service Between Two Ports; MEP Bound to Port B
The figure below illustrates a multipoint service between port and bridge ports
with the MEP bound to port A. Tx flow in the service is directed to a queue block.
Tx Flow
BP Bridge BP MEP Port A
Rx Flow
Figure 11-5. Multipoint Service with Down MEP Bound to Port A
The Down MEP is defined over the physical port, inheriting its MAC address. The
Down MEP EVC/location is characterized by:
• Rx flow, whose classification profile can be one of the following:
 Untagged
 Single VLAN
 Single VLAN+P-bit
 Single outer + single inner VLAN
 Single outer VLAN + P-bit + single inner VLAN
 Match all.
• Tx flow to a destination queue to forward OAM frames.
Up MEP
Up MEPs reside at bridge ingress and are bound to bridge ports. These MEPs
receive and send CFM PDUs from and to the bridge.
Up MEPs are supported for either point-to-point (E-Line) or multipoint (E-LAN)
services.
E-Line Up MEP
Up MEPs can be used on point-to-point (port-to-port) services. The Up MEP is
bound to an adjacent Ethernet port, inheriting its MAC address; it also faces the
egress port of the service.
The E-Line Up MEP is characterized by:
• Rx flow
• Tx flow

The figure below illustrates a point-to-point service between two ports with the
Up MEP bound to port A.
Tx Flow
Port A MEP
Port B
Rx Flow
Figure 11-6. PtP Service with Up MEP Bound to Port A
E-LAN Up MEP
Up MEPs may reside at bridge ingress and are bound to bridge ports. These MEPs
receive and send CFM PDU from and to the bridge entity. The Up MEPs inherit
their MAC addresses from the corresponding physical ports (egress ports of Tx
flows).
The figure below illustrates a multipoint service between port and bridge ports
with the Up MEP bound to the bridge port.
Rx Flow
Tx Flow
Figure 11-7. Multipoint Service with Up MEP Bound to Bridge Port
Multipoint Up MEP is defined over the bridge port. The Up MEP is characterized
by:
• Rx flow with a single VLAN classification profile
• Tx flow
Maintenance Intermediate Points (MIPs)

Unlike MEP, which is a directional entity acting as a service termination point,
MIP is defined as a bidirectional intermediate entity, comprising two half
functions (MHFs). Also, MIPs are passive points (unlike MEPs), responding only
when triggered by CFM trace route and loopback messages.
There are two types of MIPs: service-level (the default) and MD-level. These MIP
modes differ in functionality, scale, and configuration.
Note Service-level and MD-level MIPs cannot be activated simultaneously on the same
MD level. However, you can configure an MD-level MIP and service MIP on two
different MD-levels, in order to get LBM\LBR capabilities on this MIP.
Service-Level MIPs
Service-level MIP (defined under the MD level) responds to those link trace
messages (LTMs) and loopback messages (LBMs) that have their MD level equal
to the MIP MD level.

MIP
LBM/LTM LBM/LTM
Flow X Flow X
LBR/LTR LBR/LTR
MHF MHF
Figure 11-8. Service-Level MIP Functionality
Like MEPs, MIPs are bound to physical ports (directly- or indirectly-attached),

inheriting the MAC source address of the port as the Ingress port of the MIP (for
LTM purposes). A MIP is composed of two MHFs (up and down), each directed
towards a physical port or bridge port. They also have Rx and Tx flows attached
to them:
• MHF 1 facing the physical port to which the MIP is bound
• MHF 2 facing the physical or bridge port.
MIP locations are similar to those of MEP.
The MIPs are defined under the MD level and are characterized by the following:
• The physical port to which they are bound
• Rx flow, originating from the MIP-bound port, which faces MHF 1
• Tx flow, originating from the physical port facing MHF 2
The two figures below illustrate service-level MIPs in point-to-point and
multipoint services.
MIP
(bound to Port B)
Rx Flow
Port A Port B
Tx Flow
MHF 2 MHF 1
Figure 11-9. Service-Level MIP in Point-to-Point Service
MIP
(bound to Port B)
Rx Flow
BP Bridge BP Port B
Tx Flow
MHF 2 MHF 1
Figure 11-10. Service-Level MIP in Multipoint Service
By default, service-level MIPs are in manual mode, meaning that you create
them manually under the MD level.
Note The ability to create service-level MIPs in automatic mode is maintained for
backward compatibility only. For new deployments, it is recommended to use
service-level MIPs in manual mode only.

Manual MIPs require the following:

• MIP must have active Rx flows and Tx flows.
• Up to total of 256 MEPs and/or MIPs can be configured.
• MIP Bind info (Bound port, Rx flow, Tx flow) cannot be changed on the fly;
requires MIP shutdown first.
• MIP inherits its SA MAC address from the port it is bound to.
MD-Level MIPs
MD-level MIPs are activated per device per MD level (or several MD levels).
When MD-level MIP mode is activated, ETX-2 automatically creates a MIP for
each flow at each physical port, bridge port, and ring port. This includes the
flows that already exist in the system, and the flows that are created after
MD-level MIP mode is activated. Also, ETX-2 automatically creates MIP on each
EVC (VLAN). Each MIP inherits its source MAC address from the adjacent port.
The following figure illustrates device-level MIPs over point-to-point service.
MIP MIP
(bound to Port A) (bound to Port B)
Port A Port B
MHF 2 MHF 1 MHF 2 MHF 1
Figure 11-11. Device-Level MIPs in Point-to-Point Service
Measurements
MD-level MIPs respond to those link trace messages (LTMs) that have their MD
level equal to the MIP MD level. They do not respond to LBM. MD-level MIPs do
not interfere with active MAC swap loopbacks on specific flows.
When a valid LTM is received:
• LTR is sent back:
 E-Line – always
 E-LAN – if a target MAC address in LTM is learned by the bridge
LTM is relayed:
 E-Line – always
 E-LAN – If a target MAC islearned by the bridge, LTM is relayed to the
port from which the MAC address is learned.
LTR includes:
• Ingress TLV replied with ingress MIP MAC address
• Egress TLV replied with egress MIP MAC address.

MIP
LTM LTM
Flow X Flow X
LTR LTR
MHF MHF
Figure 11-12. MD-Level MIP Functionality
Limitations and Exclusions

The following limitations apply to MD-level MIPs:
• If an MD-level MIP is configured and a MEP with an equal or higher MD level
is added on a specific flow, the MIP is removed from the flow.
• If a MEP with an equal or higher MD level is configured on a flow, an
MD-level MIP cannot be provisioned for the flow.
• MD-level MIPs are not provisioned for flows connected to an MEF-8 PW SVI,
ETP subscriber/transport port, or router interface.
• MD-level MIPs can be defined only over flows with the classification: Single
VLAN, or Single outer + single inner VLAN.
• MD-level MIPS do not reply to loopback messages (LBMs).
• MEPs created at the same MD level as MIPs do not support multicast
loopbacks.
Messaging System
The Ethernet service OAM mechanism uses cyclic messages for availability
verification, fault detection, and performance data collection. The main message
types are detailed below.
Note OAM cyclic messages (CCMs, LBMs, and LTMs) packet priority (P-bit value) is
user-configurable at MEP level.
CC Messages
Continuity Check Messages (CCMs) are sent from the service source to the
destination node at regular periodic intervals. They are used to detect loss of
continuity or incorrect network connections. A CCM is multicast to each MEP in a
MA at each administrative level. CCM status information is available at the MEP
and RMEP levels.
CCM Priority and Color

The CCMs are always marked green. CCM priority is configurable as a P-bit value
at the MEP level. CCM CoS is also set at the MEP level according to P-bit-to-CoS
profile with up to four such profiles per chassis.
AIS
When a MEP detects a connectivity failure at a physical port, it propagates an
Alarm Indication Signal (AIS) in the direction away from the detected failure to

the next higher level. The AIS is sent over the MEP Rx flow with the level as
configured by the client MD level (default is the MEP level + 1) for the following
trigger events:
• LOC
• LCK
• Rx AIS
The signal is carried in dedicated AIS frames. The transmit interval is configured
per MEP, and can be set to one frame per second (default) or one frame per
minute. The AIS message priority is set per MEP via P-bit (0–7) configuration.
AIS, LCK, LOC
Rx Flow
MEP
Tx Flow
Port A AIS Port B

(with client MD level)
Figure 11-13. AIS Transmission
RDI
When a downstream MEP detects a defect condition, such as a receive signal
failure or AIS, it sends a Remote Defect Indication (RDI) upstream in the
opposite direction of its peer MEP or MEPs. This informs the upstream MEPs that
there has been a downstream failure. The Tx RDI is also initiated when a LOC is
detected on at least one of the associated RMEPs.
CCM Interval
CCM interval is user-configurable at the MA level to 3.33 ms, 10 ms, 100 ms, 1s,
1m, 10m.
CCM Multcast DA
CCM multicast destination MAC addresses per 802.1ag definition are presented
in the table below.
Table 11-3. CCM Group Destination MAC
01-80-C2-00-00-3y
CCM MD Level Four Address Bits “y”
7 7
6 6
5 5
4 4
3 3
2 2
1 1

01-80-C2-00-00-3y
CCM MD Level Four Address Bits “y”
0 0
Loopback Messages
MEPs send loopback messages (LBMs) to verify connectivity with another MEP or
MIP for a specific MA. Loopback is a ping-like request/reply function. A MEP
sends a loopback request message to another MEP or MIP, which generates a
subsequent LBR (loopback response). LBMs/LBRs are used to verify bidirectional
connectivity.
The LBMs are always marked green. LBM priority uses the CCM priority that is
configurable as a P-bit value at the MEP level. LBM CoS is set according to a P-
bit-to-CoS profile, with up to four such profiles per chassis.
LBMs are generated on demand and sent up to 500 times at a rate of 10 pps.
Link Trace Messages

MEPs multicast LTMs on a particular MA to identify adjacency relationships with
remote MEPs and MIPs at the same administrative level.
LTMs can also be used for fault isolation. The message body of an LTM includes
a destination MAC address of a target MEP that terminates the link trace. When
a MIP or MEP receives an LTM, it generates a unicast LTR to the initiating MEP. It
also forwards the LTM to the target MEP destination MAC address. An LTM
effectively traces the path to the target MEP.
LTM Priority
The LBMs are always marked green. CCM priority is configurable as a P-bit value
at the MEP level, according to a P-bit-to-CoS profile with up to four such profiles
per chassis.
LTM Response and Relay Behavior

This section describes how MEPs and MIPs relay and respond to LTMs, according
to the Y.1731 requirements.
In the figure below, the MEP responds with LTR if the target MAC address of the
received LTM is the same as the MEP MAC address (inherited from the port to
which the MEP is bound). LTM is not relayed.
LTM
Port A MEP Port B
LTR
Figure 11-14. MEP with LTM Sent from the Port in Point-to-Point Service
In the figure below, the MEP responds with LTR if the target MAC address of the
received LTM is the same as the MEP MAC address (inherited from the port to
which the MEP is bound). LTM is not relayed.

LTM
LTR
Figure 11-15. MEP with LTM Sent from the Bridge Port in Multipoint Service
In the figure below, the MIP always responds with LTR and relays the LTM.
LTM LTM
Port A Port B
LTR
MIP
Figure 11-16. MIP with LTM Sent from the Port in Point-to-Point Service
In the figure below, the MIP responds with LTR if the target MAC address of the
received LTM has been learned on the bridge port. The MIP relays the LTM if the
target MAC address of the received LTM has been learned on the bridge port or
has not been learned at all. If the target MAC address has been learned on
another bridge port, the LTM is discarded.
LTM LTM
BP Bridge BP Port A
LTR
MIP
Figure 11-17. MIP with LTM Sent from the Bridge Port in Multipoint Service
In the figure below, the MIP responds with LTR if the target MAC address of the
received LTM has been learned on another bridge port. The MIP relays the LTM
to the bridge port with the target MAC address. If the target MAC is unknown,
the MIP floods the LTM.
LTM LTM
BP Bridge BP Port A
LTR
MIP
Figure 11-18. MIP with LTM Sent from the Port in Multipoint Service
OAM Performance Monitoring

The OAM PM functionality complies with ITU-T Y.1731 and MEF 36. ETX-2
provides loss and delay measurements, as well as event reporting. ETX-2
supports the following measurement methods:
• User data – This method measures user data and CCM messages. You can
specify that this method measure only green packets (color-aware loss

measurement); additionally you can specify that it does not measure CCM
messages.
In the case of color-aware loss measurement, the following statistic
counters are based on green packets only:
 Forward/backward Tx/Rx frames
 Forward/backward Frame Loss Ratio (FLR)
 Forward/backward Availability/Unavailability
• Synthetic – This method measures DM frames. It is recommended when
working with devices that do not count user data frames.
• LMM synthetic – This method measures synthetic frames as well. It is
recommended for working with ETX-201A/202A.
• SLM synthetic – This method measures synthetic SLM/SLR frames.
ETX203AM, ETX203AX, and ETX205A calculate one-way IFDV (frame delay
variation) measurement by dividing the two-way measurement result by two.
ETX220A performs actual one-way IFDV calculation.
Notes • While working in a Bridge application, not learned user data packets, and
multicast and broadcast transmitted frames are counted several times.
• When the delay is 1 second or more the delay counters in the service and
destination NE statistics do not show accurate results.
OAM Packet Handling

This section describes how an OAM packet is handled in the following:
• MEP – CCM
• MEP – LB/LT
• MEP – LM/DM
• MIP
For each of these modes, a description is provided as to how packets are
discarded and counted in the port counters, per port, under the ‘OAM Discarded’
counter, at the following levels:
• Low MD level – Packet’s OAM level is lower than the defined MEP’s level.
• Equal MD level – Packet’s OAM level is equal to the defined MEP’s level.
• High MD level – Packet’s OAM level is higher than the defined MEP’s level.
MEP – CCM
Lower MD-Level:
• Multicast / unicast My-MAC / unicast different MAC
 Packet received from Active side –> MEP defect
 Cross Connected CCM (mismatch; unexpected MD level): On
 Packet received from Passive side –> OAM discarded on port.
Equal MD-Level:

• Multicast / unicast My-MAC

 Packet received from Active side –> OK
 Packet received from Passive side –> OAM discarded on port
• Unicast different MAC (not My-MAC DA)
 Packet received from Active side –> DA MAC is not analyzed. No discard,
no alarm – MEP in OK status.
Higher MD-Level:
• Multicast /unicast different MAC
 Packet received from both sides –> considered as user data
• Unicast My-MAC
 Packet received from both sides –> OAM discarded on port
MEP – LB/LT
Lower MD-Level:
• LB/LT multicast / unicast My-MAC / unicast different MAC
Equal MD-Level:
• Multicast / Unicast My-MAC (LB/LT)
 LB
 Packet received from both sides –> OAM discarded on port
 LT
 Packet received from Active side –> discarded by CPU; no indication
 Packet received from Passive side –> OAM discarded on port
Higher MD-Level:
• Unicast My-MAC (relevant to LB only)
MEP – LM/DM
Lower MD-Level:
• Multicast / unicast My-MAC / unicast different MAC
Equal MD-Level:

• Multicast / unicast My-MAC

Higher MD-Level:
• Unicast My-MAC
MIP
Note Not relevant to global MIP.
Lower MD-Level received packet:

• Multicast / unicast different MAC –> considered as user data
• Unicast My-MAC –> OAM discarded on port
Equal MD-Level received packet:
• Linktrace (LT) (always MC DA)
 Answer LTR. Forward LTM, if not HIT
• Loopback (LB)
 MC -> considered as user data
 Unicast My-MAC–> answer LBR
 Unicast different MAC -> considered as user data
• Other OAM packet
 MC -> considered as user data
 Unicast My-MAC –> OAM discarded on port
 Unicast different MAC -> considered as user data
Higher MD-Level received packet:
• Unicast My-MAC
MEF46 Latching Loopback

MEF46 enables associating a Latching Loopback State Machine (LLSM) with a
MEP. You can enable or disable the Latching Loopback functionality (LLF) per
MEP, which is configured with Rx and Tx flows (and not Classification). By
default, LLF is disabled. LLF is supported in either a service down or up MEP that

is connected to a physical or LAG port. When LLF is enabled, the operational

status of the MEP is set to mef46Loop. Latching Loopback is supported in all
network topologies that support Y.1564, i.e. E-Line, E-LAN, and E-Tree.
Factory Defaults
By default, OAM functionality is disabled. There are no MDs, MAs, or MEPs.
The OAM CFM general parameters have the following default configuration.
alarm-type legacy
availability delta-t 1 n 10 forward-thr 50 Forward threshold and backward threshold

backward-thr 50 default values are 50% (unit is %).
md-level-mip no md-level-mip Service-level MIP is the default.
mip-assign manual Manual MIP creation is the default.
multicast-addr 01-80-C2-00-00-30
When a maintenance domain is created, it has the following default

configuration.
proprietary-cc no proprietary-cc Standard OAM protocol
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.
interface-status-tlv interface-status-tlv
classification vlan 0
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.
ais no ais
bind no bind
ccm-initiate ccm-initiate Initiate continuity check messages.
ccm-priority 0

client-md-level 4
customer-tags-excluded no customer-tags-excluded
dest-addr-type ccm multicast pm unicast • Destination address type for CCM

messages – multicast
• Destination address type for performance
measurement messages – unicast
direction down
forwarding-method e-line
queue fixed 0
When a service is created, it has the following default configuration.
delay-threshold 1000
delay-var-threshold 1000
dmm-interval 1s
lmm-interval 1s
When a destination NE is created, it has the following default configuration.
bck-delay-var-bin no bck-delay-var-bin
delay two-way data-tlv-length 0
delay-measurement-bin no delay-measurement-bin
delay-var-measurement-bin no delay-var-measurement-bin
description "Put your string here"
fwd-delay-var-bin no fwd-delay-var-bin
loss single-ended user-data lm-mode

tx-rx
remote mac-address
00-00-00-00-00-00
Configuring OAM CFM

Ethernet OAM configuration includes the steps detailed in this section:

Note Before deleting any OAM CFM component, verify that it is not used by other
ETX-2 elements, such as ERP.
 To configure the service OAM:

1. Configure general OAM parameters.
2. Add and configure maintenance domain(s) (MD).
3. Configure maintenance associations for the added MDs.
4. If ETX-2 is acting as a MIP, then configure the necessary MIPs.
5. If ETX-2 is acting as a MEP:
a. Configure MA endpoints, referred to as MEPs.
b. Configure MEP services.
c. Configure Destination NEs.
Configuring General Parameters

You can define general OAM CFM parameters, as well as displaying OAM CFM
information.
 To define general OAM CFM parameters:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
Defining whether legacy alarm-type { legacy | soam } legacy – OAM alarm names remain the same
alarms or newer alarms as in previous versions.
are used soam – OAM alarm names change as
follows:
• defErrorCCM – MEP level alarm: invalid
CCM received with CCM Interval that has
not yet timed out; replaces mismatch
• defMACstatus – RMEP level alarm: Defect
reported by interface or port status TLV
• defRDICCM – RMEP level alarm: RDI
(remote defect); replaces rdi
• defRemoteCCM – RMEP level alarm: Loss
of continuity (LOC); replaces loc
• defXconCCM – MEP level alarm:
Unexpected CCM received from MAID or
lower MD level; replaces mismatch

Defining parameters for availability [delta-t {1 | 2 | 3 | 4 | 5 | 6 | 10 These parameters define availability

availability calculations |12|15|20}][n<n>] performance measurement, based on frame
[forward-thr <forward-thr-percents>] loss during a sequence of consecutive small
[backward-thr <backward-thr-percents>] time intervals:
• delta-t – time interval (in seconds)
• n – number of consecutive small time
intervals over which to measure
availability
• forward-thr – Forward frame loss ratio
threshold, for which unavailability occurs
if exceeded (%)
forward-thr = 0 recommended for
measuring low levels of loss
• backward-thr – Backward frame loss
ratio threshold, for which unavailability
occurs if exceeded (%)
forward-thr = 0 recommended for
measuring low levels of loss.
Configuring [no] maintenance-domain <mdid> See Configuring Maintenance Domains for

Maintenance Domain more details.
(MD)
Configuring MD-level [no] md-level-mip <md-level-list> See MD-Level MIPs for more details.
MIP
Configuring [no] measurement-bin-profile <name> See Configuring Measurement Bin Profiles

measurement bin for more details.
profiles
Configuring service-level mip-assign {automatic | manual} Command available for backward

MIP creation mode compatibility only. mip-assign automatic
(automatic MIP creation mode) is available
but not recommended.
Recommended to create MIPs only in
manual mode (the default mip-assign
manual). In this mode, you create MIPs
under the MD level using the mip command
(see Configuring Maintenance Intermediate
Points).
Configuring the MAC multicast-addr <mac-address>

address used in
multicasts
Displaying information show mips Shows all service-level MIPs; not MD-level
on MIPs MIPs.
Displaying OAM CFM show summary See Viewing OAM CFM Information for more
information such as details.
MDs, MAs, MEPs, etc.

Configuring Measurement Bin Profiles

You can define measurement bin profiles to define sets of threshold ranges (in
microseconds (μs)) for displaying delay measurements in destination NEs. See
Configuring and Viewing Delay Measurement Bins for a configuration example.
 To define measurement bin profiles:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
Enter the measurement bin profile level by typing the following:
measurement-bin-profile <name>
The prompt config>oam>cfm>measurement-bin-prof(<name>)# is
displayed.
2. Specify the thresholds (single value, or values separated by commas) in
microseconds (μs).
thresholds <thresholds-list>
Each value is used as the upper range of a set of thresholds, up to
5,000,000. For instance, entering thresholds 500,1000,15000 results in this
set of threshold ranges:
 0–500
 501–1,000
 1,001–15,000
 15,001–5,000,000
Viewing OAM CFM Information

You can display OAM CFM information by typing show summary, as shown in the
following.
ETX-2# configure oam cfm
ETX-2# config>oam>cfm# show summary
md slot/ classifi admin mep ok/total
md/ma/mepid md/ma name lvl port cation status def r.meps
001/001/001 MD1/MA1 3 eth1 100 enable off 1/1

002/002/8191 1234567890123456789012 3 eth1 0 disable
34567890/1234567801234
002/005/123 1234567890123456789012 3 eth1 100/ enable off 0/2
34567890/155 200
002/006/101 1234567890123456789012 3 eth3 untagged enable off 0/3
003/001/001 /iccname 4 eth1 100.1 enable off 0/1
004/001/001 20-64-32-AB-CD-64 120/ 0 eth1 4000 enable off 0/1
MA1
004/002/001 20-64-32-AB-CD-64 120/ 0 eth1 3000/ enable off 0/3
12345678901234567890123
Configuring Maintenance Domains

MDs are domains for which the connectivity faults are managed. Each MD is
assigned a name that must be unique among all those used or available to an

operator. The MD name facilitates 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 1–4095
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.
Note A maintenance domain can be deleted only if all its MEPs/MIPs are deleted or
disabled.
 To configure a maintenance domain:

1. Navigate to configure oam cfm maintenance-domain <mdid> to select the
maintenance domain to configure.
2. The config>oam>cfm>md(<mdid>)# prompt is displayed.
Configuring maintenance [no] maintenance-association <maid> See Configuring Maintenance

association (MA) for the Associations.
MD no maintenance –association <maid>
deletes the MA.
Specifying the MD level md-level <md-level> The allowed range for md-level is 0–7.
Notes:
• If prestandard OAM protocol is being
used, the only allowed value for the
maintenance domain level is 3.
• When md-level is set to 7, client md-
level, even if configured, becomes
meaningless, as it must have a higher
value than md-level but cannot
exceed 7.
Configuring service-level [no] mip <mipid> This parameter is visible only for manual
MIP MIP creation mode (the default and
recommended mode).
See Configuring Maintenance
Intermediate Points for full configuration
details.
no mip <mip id> deletes the MIP.

Defining service-level MIP mip-policy { explicit | default } This command is available for backward
policy compatibility only, when you select
automatic MIP creation mode (not
recommended).
Specifying the name format name string <md-name-string> • Maximum length of md-name-string is
and name of the name dns <md-name-string> 43 characters.
maintenance domain • Maximum combined length of
name mac-and-uint <md-name-mac>
<md-name-uint> md-name-string and ma-name-string
(maintenance association name) is
no name
48 characters.
• Format mac-and-uint – Specify
md-name-mac as xx-xx-xx-xx-xx-xx,
and md-name-uint as an unsigned
integer decimal number (0–65535).
• If prestandard OAM protocol is being
used, the maintenance domain must
have no name (use command no
name).
Specifying the OAM no proprietary-cc • Use no proprietary-cc for standard

protocol type proprietary-cc OAM protocol.
• Use proprietary-cc for prestandard
OAM protocol.
Note: The MD must have no name (via
no name) and the level must be 3 before
you can set the protocol to prestandard.
Configuring Maintenance Associations

A maintenance domain contains maintenance associations (MAs).
 To add a maintenance association (MA):
• At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance- association <maid>
where <maid> is 1–4095
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.
Note A maintenance association can be deleted only if all its MEPs/MIPs are deleted or
disabled.

 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 {3.33ms | 10ms | Note: When ccm-interval is set to 3.33ms, then
between continuity check 100ms | 1s | 10s | 1min | 10min} if you have defined the maximum number of
messages MEPs (255), the interval is not enough time to
activate them with all the corresponding
remote MEPs.
Associating the MA with a classification vlan <vlan-id> Verify that the VLAN is the same as the VLAN
VLAN associated with the MEP.
Note: If a classifier profile is associated with
the MEP, the VLAN should be set to 0.
Specifying if Interface Status interface-status-tlv

TLV is in continuity check
messages
Configuring MEP for the MA mep <mepid> See Configuring Maintenance Endpoints.
Defining a general MIP policy mip-policy This command is available for backward
for the MA { explicit | default | defer } compatibility only, when you select automatic
MIP creation mode (not recommended).
Specifying the name format name string <ma-name-string> • Maximum length of ma-name-string is
and name of the name primary-vid 45 characters.
maintenance association <ma-name-vid> • Maximum combined length of md name
name uint <ma-name-uint> string and ma name string is 48 characters.
name icc <ma-name-icc> • Format primary-vid (primary VLAN ID) –

Specify ma-name-vid as 1–4094.
• Format uint – Specify ma-name-uint as an
unsigned integer decimal number
(0–65535).
• 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. icc name length
supported is 1-13 charcters.
Note: If the icc option is selected or
prestandard OAM protocol is being used, 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, a flow must be configured with the same classification as the
MEP, in the direction UNI to NNI. This can be achieved using either of the
following methods:
• Classification method – Configure the MEP classification; the SW automatically
finds and matches the corresponding flows to the MEP according to the
MEP’s configured classification.
• Rx, Tx flows method – Explicitly bind flows on a MEP. The MEP derives its
classification from its bound flows.
 To add a maintenance endpoint (MEP):

• At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
mep <mepid>
where <mepid> is 1–8191
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.
Note You can remove a maintenance endpoint regardless of whether it contains

services.
 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.
Note When changing the MEP classification method, you must delete the MEP and
then create a new MEP.

Defining sending of AIS ais [ interval { 1s | 1min }] When md-level is set to 7, client-md-level,
[priority <priority>] even if configured, becomes meaningless.
In this case, the MEP cannot be defined to
AIS transmission and must be set to no-
ais.
Binding the MEP to an bind ethernet [<slot>/]<port> To remove the MEP from an Ethernet port,
Ethernet port enter no bind.
Binding the MEP to an ETP bind etp <etp-name> To remove the MEP from an ETP port,
port if ETP is used {subscriber | transport} <port-id> enter no bind.
Binding the MEP to a logical bind logical-mac <port-number> To remove the MEP from a logical MAC
MAC port port, enter no bind.
Binding the MEP to PCS bind pcs <port-number> To remove the MEP from a PCS port, enter
port no bind.
Note: Relevant only for the SHSDL module
option.
Binding the MEP to bridge bind bridge-port <bridge-number> The bridge port must not be used by a
port <port-number> flow.
Enabling initiation of ccm-initiate To disable initiating continuity check

continuity check messages messages, enter no ccm-initiate.
(CCM)
Specifying the priority of ccm-priority <priority> Possible values: 0–7

CCMs and LTMs transmitted Note: For ETX220A, before changing the
by the MEP CCM priority,you need to administratively
disable the MEP, and then re-enable it
after the change, in order to avoid
possible Up MEP Tx/Rx frame counter
corruption.
Associating the MEP with a classification vlan <vlan-id> You can associate more than one MEP to
classifier profile or VLAN classification profile <profile-name> the same VLAN if the MEPs belong to MDs
with different levels.
Verify that the VLAN is the same as the
VLAN associated with the MA.
If using a classifier profile, it must be
EVC.cos or VLAN+inner-VLAN.
Clearing MEP statistics clear-statistics
Defining client MD level client-md-level <md-level> Possible values: 0–7

Client MD level must be higher than MD
level.
Note: When md-level is set to 7,
client- md-level, even if configured,
becomes meaningless, as it must have a
higher value than md-level but cannot
exceed 7.

Specifying continuity continuity-verification <cc-based | This parameter is visible only in

verification method lb-based> prestandard mode and can be configured
only if ccm-initiate is enabled as explained
above. Use lb-based only for RAD
proprietary OAM functionality.
Specifying that MEP customer-tags-excluded This parameter is visible only for up MEPs,
transmits OAM PDUs with and is relevant to E-line only; it is not
only S-tag, and no C-tag applicable for up MEPs over bridge or ETP.
Defining the MAC address dest-addr-type [ccm {unicast|multicast}] If more than one remote MEP ID has been
type sent in OAM [pm {unicast|multicast}] defined for the MEP and you change the
continuity check messages CCM destination address type from
(CCM) and performance multicast to unicast, all remote MEP IDs
measurement messages are deleted except for the lowest remote
(PM) MEP ID.
If the MAC address type for PM messages
is unicast, then the MAC address for the
transmission of PM messages is
determined by the configuration of the
destination NE. If a remote MAC address is
configured for the destination NE, that
MAC is used. Otherwise if a remote MEP ID
is configured for the destination NE, the
remote MAC address is learned from CCM
messages. See 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 } If the MEP is bound to a bridge or ETP

port, the direction must be up.
Assigning unidirectional or flow uni-direction rx <rx-name> [ Rx flow: Flow with ingress port that is the
bidirectional Rx or Tx flow tx <tx-name>] MEP facing port
to the MEP flow bi-direction <name> Tx flow: Flow with egress port that is MEP
facing port
Up to eight Tx flows and eight Rx flows
can be assigned to the MEP.
Rx/Tx flows cannot be assigned if one of
the following is true:
• VLAN is configured at the MA level.
• VLAN or profile is configured at the
MEP level for the Rx classification.
To delete flow assignment, enter no flow
uni-direction or no flow bi-direction,
respectively.

Defining forwarding forwarding-method { e-line | e-lan } Note: The e-line parameter is not available
method for ETX220A.
Activating CFM loopback lbm See Performing OAM Loopback for details.
(LBM)
Activating linktrace (LTM) linktrace See Performing OAM Link Trace for details.
Enabling/disabling Latching mef46-ll Note: MEF-46 can only be enabled on MEP

Loopback Function (LLF) on no mef46-ll configured with Rx and Tx flows. It cannot
MEP be enabled on MEP configured with
classification.
Defining the queue for the queue fixed <queue-id> Note: The block parameter is not allowed
MEP [block <level-id>/<queue-id>] for up MEPs.
queue queue-mapping
<queue-map-profile-name>
[block <level-id>/<queue-id>]
Defining remote MEP with remote-mep[<rmep1>..<rmep2>,<rmep3> Possible values for remote MEP IDs:
which the MEP ] 1–8191
communicates You can define multiple remote MEP IDs in
one remote-mep command by specifying a
list of values separated by commas (with
no spaces between the values), using .. to
indicate ranges. You can end the
command line with <CR> and then input
another list. Up to 10 elements (where
each element is either a single remote
MEP or a range of multiple remote MEPs
having consecutively numbered IDs) can be
configured in a list.
The MEP ID must be different than the
remote MEP ID(s). You can use multiple
remote-mep commands to define up to
100 remote MEPs for the local MEP (up to
1024 total remote MEPS in ETX220A; up
to 100 in ETX203AX, ETX203AM, and
ETX205A) if standard OAM protocol is
being used for the MD and the destination
address type is multicast, otherwise you
can define only one remote MEP.
Configuring service for the service <serviceid> See Configuring Maintenance Endpoint
MEP Services.
Displaying MEF46 Latching show mef46-ll-status This parameter is visible only for MEF-46
Loopback status enabled (see above).
See Viewing MEF46 Latching Loopback
Status.
Displaying MEP status show status
Displaying loopback status show lbm-results See Performing OAM Loopback for details.

Displaying linktrace status show linktrace-results See Performing OAM Link Trace for details.
Displaying remote MEP show remote-mep-status { remote-mep-id If a remote MEP was never learned, its
status <remote-mep-id> | all } status is “NEW”. As a result, the following
takes place:
• Dest NE that is configured under this
MEP’s services cannot learn the remote
MAC address and therefore, does not
transmit LMM and DMM.
• “unavailability” is not indicated and
therefore the unavailability counters
are not incremented.
• Available counter increments, as it is
ready for use as soon as the remote
MEP is configured.
Administratively enabling no shutdown To deactivate the MEP, enter shutdown.

MEP When shutdown is performed on a MEP,
its active services (i.e. no shutdown
services) are moved automatically to
shutdown as well. No error or warning
message is displayed.
When no shutdown is performed on a MEP
is in, its services are not activated
automatically.
Note: Following no shutdown of MEP, the
following warning message appears to
notify you to activate relevant MEP
services: “Warning: Relevant MEP services
must be activated following MEP
reactivation”.
Viewing MEF46 Latching Loopback Status

You can view MEF46 Latching Loopback (LL) status of an MEF-46 enabled MEP
that is configured with Rx and Tx flows.
 To display the MEF46 LL status:

• In the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,
enter show mef46-ll-status.
The status screen appears. For information on the MEF46 LL status
values, see Table 11-4.
ETX220A>config>oam>cfm>md(1)>ma(1)>mep(2)# show mef46-ll-status
Rx Unicast LLMs : 2

Rx Multicast LLMs : 0
Rx Discarded LLMs : 0
Tx LLRs : 2
Tx Autonomous LLRs : 0
Num First Source MAC Address Last Source MAC Address Time Remaining
-----------------------------------------------------------------------------
1 00-20-D2-54-11-92 00:06:43
ETX220A config>oam>cfm>md(1)>ma(1)>mep(2)#
Table 11-4. MEF46 Latching Loopback Status
Displayed
Administrative Status Current status of the LLF

Possible values: Up, Down
Note: The parameters of this report are only displayed when
Administrative Status is Up.
Rx Unicast LLMs Number of unicast LLM PDUs received by the LLF
Rx Multicast LLMs Number of multicast LLM PDUs received by the LLF
Rx Discarded LLMs Number of invalid LLM PDUs discarded by the LLF
Tx LLRs Number of LLR PDUs sent by the LLF
Tx Autonomous LLRs Number of autonomous LLR PDUs sent by the LLF. An

autonomous LLR has a response code of Timeout or Prohibited.
First Source MAC Addre Start of a block of source MACs in incoming frames that are
looped
Last Source MAC Addre End of a block of source MACs in incoming frames that are
looped
Time Remaining Time remaining until deactivation of the loop
Configuring Maintenance Intermediate Points
MD-Level MIP
You can create MD-level MIPs at the OAM CFM level, as described in this section.
When MD-level MIP mode is activated, ETX-2 provisions a MIP for each flow at
each physical port, bridge port, and ring port, subject to the limitations specified
above in OAM Elements. The MIPs are added for each specified MD level, or MD
level range.
 To add an MD-level MIP:

• At the config>oam>cfm# prompt, enter md-level-mip <md-level-list>.
The MD levels in the list can be separated by a comma or given as a range,
for example: 1..3, 5.
Note Do not type a space after any commas in the list.

Typing no md-level-mip <md-level-list> removes the specified MD-level MIP.
Service-Level MIP (manual mode)
Note
This section is relevan t only for service-level MIPs in the recommended default m anual MI P creation mode (m i p-assign parameter under OAM CFM confi guration is configured as manu al).
Service-level MIPs are bidirectional intermediate entities defined in the

maintenance domain level.
You can create a service-level MIP under the MD level, as described below, when
in manual mode.
 To add a service-level MIP in manual mode:

1. Navigate to configure oam cfm maintenance-domain <mdid>.
2. At the config>oam>cfm>md(<mdid># prompt, enter:
mip <mipid>
The MIP is created and the prompt
config>oam>cfm>md(<mdid>)>mip(<mipid>)$ is displayed.
 To delete a MIP:
• At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mipid>
The maintenance intermediary point is deleted.
 To configure a service-level MIP in manual mode:

1. Navigate to configure oam cfm maintenance-domain <mdid> mip <mipid> to
select the MIP to configure.
The config>oam>cfm>md(<mdid>)>mip(<mipid>)# prompt is displayed
Binding the MIP to an bind ethernet [<slot>/]<port> To unbind the MIP, enter no bind.
Ethernet port, logical MAC bind logical-mac <port-number>
port, or PCS port
bind pcs <port-number>
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.
Administratively enabling no shutdown To deactivate the MIP, enter shutdown.

MIP
Displaying MIP status show status Displayed for active MIP only. See Viewing
MIP Status below.
Configuring Maintenance Endpoint Services

You can configure up to eight services on a MEP, corresponding to each p-bit.
Note Only one service is allowed if the classifier profile associated with the MEP is
according to 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 1–8.
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 1–8).
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> Possible values: 0–7
priority Note: Before changing the
classification, you need to
administratively disable the
service, and then re-enable it
after the change.
Clearing service statistics clear-statistics
Specifying delay threshold in delay-threshold <delay-thresh> Possible values: 1–5,000,000

microseconds Note: The configured value is
rounded down to
100 microsecond granularity,
e.g. values 0–99 are rounded
to 0, values 100–199 are
rounded to 100, etc.
Specifying delay variation delay-var-threshold <delay-var-thresh> Possible values: 1–5,000,000

threshold in microseconds Note: The configured value is
rounded down to
100 microsecond granularity.
Configuring destination NE for dest-ne <dest-ne-index> Possible values: 1–255

service

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} When changing lmm-interval,
measurement messages, to be you must perform NO LM and
used by all remote NEs defined then LM.
for service
Configuring collection of pm-collection interval <seconds> Note: In addition to enabling

performance management PM statistics collection for the
statistics for the service, that service, it must be enabled for
are presented via the RADview the device. See Performance
Performance Management Management.
portal
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.
Note: Following no shutdown
of MEP, the following warning
message appears to remind
you to activate relevant MEP
services: “Warning: Relevant
MEP services must be activated
following MEP reactivation.”
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-2
can learn it from the CCM messages, provided that the remote MEP of the
destination NE has been learned (its status is not “NEW”).
If the remote MAC address is not configured and needs to be learned,
performance measurement messages (lmm and dmm) 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(<service
id>)#, enter:
dest-ne <dest-ne-index>
where <dest-ne-index> is 1–255
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.
Assigning the delay variation bck-delay-var-bin-profile profile <name>

measurement bin profile for
backward delay variation
measurement
Clearing statistics clear-statistics The destination network element

running counters are cleared; the
interval and current counters are not
cleared.
Specifying delay measurement delay {one-way | two-way}

method and length of DMM [data-tlv-length <length-val>]
data TLV
Assigning the delay delay-measurement-bin profile <name> The delay measurement bin profiles
measurement bin profile are defined in the conf>oam>cfm
level.
Assigning the delay variation delay-var-measurement-bin The delay measurement bin profiles
measurement bin profile profile <name> are defined in the conf>oam>cfm
level.
Configuring description string description <string>
Assigning the delay variation fwd-delay-var-bin-profile profile

measurement bin profile for <name>
forward delay variation
measurement

Defining single-ended/dual- loss {single-ended |dual-ended} • user-data – measures user data

ended loss measurement [user-data [green-only] [no-ccm] and CCM messages. Do not use
method [lm-mode {rx | tx-rx}]] user-data on up MEPs in the
loss {single-ended |dual-ended} Bridge application.
[user-data [lm-mode {rx | tx-rx}]] • green-only – measures green
loss {single-ended |dual-ended} packets only, for user data
[user-data-green [lm-mode {rx | tx-rx}]] single-ended/dual-ended loss
loss single-ended [synthetic measurement
[lm-mode {rx | tx-rx}]] • no-ccm – does not include CCMs
loss single-ended [lmm-synthetic in user data single-ended/dual-
[lm-mode {rx | tx-rx}]] ended loss measurement
loss single-ended [slm • user-data-green – measures green

[slm-data-tlv-length <slm-length-val>] packets only, for user data
[lm-mode {rx | tx-rx}] single-ended/dual-ended loss
measurement
Note: Green and yellow frames are
identified by DEI (0=green, 1=yellow).
Therefore in order for color-aware
loss measurement to function
properly, you need to do the
following:
• Mark green/yellow frames by
DEI in the Tx flow.
• Configure ingress-color by DEI.
• Specify no_policer for the flow.
• synthetic – measures DM frames;
recommended when working with
devices that do not count user
data frames
• lmm-synthetic – measures
synthetic frames as well;
recommended for working with
ETX-201A/202A
• slm – measures synthetic SLM/SLR
frames
• lm-mode – specifies loss
measurement message mode:
• rx indicates to respond with
LMR/SLR when LMM/SLM is
received.
• tx-rx indicates to transmit
LMMs/SLMs, and respond with
LMR/SLR when LMM/SLM is
received.
• slm-data-tlv-length – specifies
length of SLM data TLV.
Possible values: 0–1800 (default:
0)

Configuring collection of pm-collection interval <seconds> Note: In addition to enabling PM

performance management statistics collection for the
statistics for the destination destination NE, it must be enabled
NE, that are presented via the for the device. See Performance
RADview Performance Management.
Management portal
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
Displaying the delay show delay-measurement-bins {rt-delay Relevant only if profiles were
measurement bins for delay | rt-delay-var | fw-delay-var | bw-delay- assigned via delay-measurement-bin,
measurements via DMRs var } current delay-var-measurement-bin.
show delay-measurement-bins {rt-delay • rt-delay – Round trip delay
| rt-delay-var | fw-delay-var | bw-delay- • <rt-delay-var> – Round trip delay
var } interval <interval-num> variation
show delay-measurement-bins {rt-delay • <fw-delay-var> – Forward delay
| rt-delay-var | fw-delay-var | bw-delay- variation
var } all
• <bw-delay-var> – Backward delay
variation
• <current> – Current statistics
• <interval> – Interval statistics
• interval-num> – Interval number
[number]
• all – all statistics
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,
see Configuring Maintenance Endpoint Services).
In addition to the regular OAM statistics collection, ETX-2 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 (see Syslog for more details).
The following counters can be monitored:
Far End Frame Total number of OAM frames lost from local MEP to remote
Loss Ratio MEP, divided by total number of transmitted OAM frames
since the service was activated

Near End Frame Total number of OAM frames lost from remote MEP to local
Loss Ratio MEP, divided by total number of transmitted OAM frames
since the service was activated
Frames Above Number of frames that exceeded delay threshold

Delay
Frames Above Number of frames below or equal delay variation threshold

Delay Variation
(Jitter)
Far End Total number of far end unavailable seconds divided by

Unavailability Ratio elapsed time since service was activated
Near End Total number of near end unavailable seconds divided by

Unavailability Ratio 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 pre-defined
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-end-unavailability-ratio}
The prompt
config>fault>cfm>service(<mdid>/<maid>/<mepid>/<serviceid>)# is
displayed.
3. Specify the type of event reporting for the counter (see Table 11-5):
 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:
{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-thousandth>] [falling-threshold
<falling-threshold-thousandth>]
4. Type no shutdown to activate the event reporting for the counter.

Table 11-5. 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 1–60
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
(measured in milliseconds):
1–1000
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
• Sampling interval value must be
at least double rising threshold.
Viewing OAM CFM Statistics

You can display end-to-end performance monitoring data for the MEPs, OAM
services, and destination NEs. The statistics for a service are calculated from the
statistics for its destination NEs.
ETX-2 measures performance in fixed intervals (the interval length can be
configured by the interval-duration command).
You can view the following types of statistics for MEPs, services, and destination
NEs:
Running OAM statistics collected since the corresponding service

was activated

Current OAM statistics for the current interval
Interval OAM statistics for 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.
OAM CFM supports checking Availability status within an interval as well as
across intervals. In the case that there are less than n consecutive delta-t small
time intervals at the end of an interval that have changed Availability status
(become Available or Unavailable), the delta-t small time intervals at the
beginning of the next interval are checked to see if there is a total of n
consecutive delta-t small time intervals across the intervals (the end of the
current interval and the beginning of the next interval). If so, the delta-t small
time intervals at the end of the current interval are all considered to have a
changed Availability status (Available or Unavailable).
For example, when Availability is defined for ten one-second intervals, and there
are three SES seconds at the end of the current interval, those seconds are
considered Unavailable only if the first seven seconds of the next interval are
also SES, i.e. ten consecutive SES.
An interval is closed only after the following Availability and Unavailability
counters are updated accordingly, taking into consideration the Availabilty status
change of Delta-t’s in the current interval that are affected by the Availability
status of Delta-t’s in the new interval (see Table 11-6 for a description of the
counters):
• Tx Frames [Forward]
• Tx Frames [Backward]
• Rx Frames [Forward]
• Rx Frames [Backward]
• Unavailable Seconds [Forward]
• Unavailable Seconds [Backward]
• Frame Loss Ratio (%) [Forward]
• Frame Loss Ratio (%) [Backward]
Also, the statistics of the last History interval (i.e. the interval before the
current) can only be viewed n * Delta_t seconds after the current interval has
commenced.
 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 }

Notes • If RADview is being used to manage ETX-2, then when the interval duration is
changed, it is recommended to clear the statistics of all relevant Dest NEs, in
order to avoid any inconsistencies.
• interval-duration must be configured to a larger value than availability (delta_t
* n) calculation; otherwise, a sanity error occurs.
 To display the OAM CFM statistics for a MEP, service, or destination NE:
1. Navigate to the level corresponding to the OAM MEP, service, or destination
NE for which you wish to view the statistics
configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> mep <mepid>
or
maintenance-association <maid> mep <mepid> service <serviceid>
or
maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index>).
The prompt for MEP, service, or destination NE is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<ser
viceid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<ser
viceid>)>
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 Viewing Running Statistics;
statistics running see Table 11-6 and Table 11-7.
Viewing statistics show statistics The statistics for the current interval are displayed as shown in
for the current current Viewing Current Statistics; see Table 11-6 and Table 11-7.
interval
Viewing the show statistics • Allowed values for interval-num: 1–48

statistics for a interval • The statistics for the selected interval are displayed as shown in
selected interval <interval-num> Viewing Interval Statistics; see Table 11-6 and Table 11-7.
• If you specified an interval that has not yet ended since the
service was activated, a message is displayed that the interval
doesn’t exist.

Viewing running show statistics The statistics are displayed as shown in Viewing Running Statistics,
statistics, all Viewing Current Statistics, Viewing Interval Statistics; see Table 11-6
statistics for the and Table 11-7.
current interval,
and statistics for
all intervals
Viewing statistics show statistics The statistics for all intervals are displayed as shown in Viewing
for all intervals all-intervals Interval Statistics; see Table 11-6 and Table 11-7.
Clearing the clear-statistics The running statistics for the MEP, service, or destination NE are
statistics for the cleared (the interval and current counters are not cleared).
service or
destination NE
Table 11-6. OAM Statistic Counters
Tx Frames [Forward] Total number of frames transmitted from local destination NE to

remote destination NE since the service was activated
Note: Counts Tx frames during Available time only.
Tx Frames [Backward] Total number of frames transmitted from remote destination NE to
local destination NE since the service was activated
Note: Counts Tx frames during Available time only.
Rx Frames [Forward] Total number of frames received by remote destination NE since the
service was activated
Note: Counts Rx frames during Available time only.
Rx Frames [Backward] Total number of frames received by local destination NE since the
service was activated
Note: Counts Rx frames during Available time only.
Lost Frames [Forward] (in service Total number of frames lost from local destination NE to remote
statistics) destination NE since the service was activated
Frames Loss[Forward] (in dest-ne Note: This counter is called Lost Frames for Services, and Frames Loss
statistics) for dest NEs.
Lost Frames [Backward] (in service Total number of frames lost from remote destination NE to local
statistics) destination NE since the service was activated
Frames Loss[Backward] (in dest-ne Note: This counter is called Lost Frames for Services, and Frames Loss
statistics) for dest NEs.
Frame Loss Ratio (%) [Forward] Lost Frames [Forward] divided by Tx Frames [Forward]
Note: Counts FLR during Available time only.
Frame Loss Ratio (%) [Backward] Lost Frames [Backward] divided by Tx Frames [Backward]
Note: Counts FLR during Available time only.
Unavailable Seconds [Forward] Number of seconds the remote destination NE is considered
unavailable
Note: This counter is displayed only for dest NEs.
Unavailable Seconds [Backward] Number of seconds the local destination NE is considered unavailable

Available Seconds [Forward] Number of seconds the remote destination NE is considered available
Two Way Unavailable Seconds Number of seconds that either the remote destination NE (forward)
and/or local destination NE (backward) are unavailable.
Note: This counter is displayed only for dest NEs current and interval
statistics.
Available Seconds [Backward] Number of seconds the local destination NE is considered available
Two Way Available Seconds Number of seconds that both the remote destination NE (forward)
and local destination NE (backward) are available.
Note: This counter is displayed only for dest NEs current and interval
statistics.
Two Way Delay (mSec) Round trip frame delay
Two Way IFDV (mSec) Round trip frame delay variation
Current Forward IFDV (mSec) Difference between the current delay value and the previous current
delay value, for forward direction
Current Backward IFDV (mSec) Difference between the current delay value and the previous current
delay value, for backward direction
Frames Above Delay Threshold Number of DM frames whose delay value exceeded the configured
delay threshold
Frames Above IFDV Threshold Number of DM frames whose delay variation exceeded the configured
delay variation threshold
Two Way Delay (msec) [Min] Minimum frame delay value received in DM frame
Two Way Delay (mSec) [Average] Average of all frame delay values received in DM frames
Two Way Delay (msec) [Max] Maximum frame delay value received in DM frame
Two Way IFDV (msec) [Min] Minimum difference between the frame delay values received in DM
frames
Two Way IFDV (mSec) [Average] Average difference between the frame delay values received in DM
frames
Two Way IFDV (msec) [Max] Maximum difference between the frame delay values received in DM
frames
Forward IFDV [Min] Minimum difference between the frame delay values received in DM
frames for forward direction
Forward IFDV [Average] Average difference between the frame delay values received in DM
Forward IFDV [Max] Maximum difference between the frame delay values received in DM
Backward IFDV [Min] Minimum difference between the frame delay values received in DM
frames for backward direction
Backward IFDV [Average] Average difference between the frame delay values received in DM

Backward IFDV [Max] Maximum difference between the frame delay values received in DM
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated.
Exception: Following shutdown and then no shutdown of a service,
current statistics of the first interval display in Elapsed Time the time
that is aligned to the wall clock, and not the elapsed time since the
service was activated. Hence, all current statistics calculated using
Elapsed Time are not valid for the first interval following shutdown
and no shutdown.
CCM P-bit P-bit where CCM resides
MD Level MD level munber where CCM resides
CCM Tx frames Number of CCM Tx frames per MEP
RMEP ID The ID of the remote MEP associated with the MEP
CCM Rx frames Number of CCM Rx frames per remote MEP
Table 11-7. OAM Delay and Loss Measurement Counters
Tx LMMs Number of transmitted loss measurement messages

Tx DMMs Number of transmitted delay measurement messages
Rx LMRs Number of received loss measurement replies
Rx DMRs Number of received delay measurement replies
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-2 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 lbm address <mac-address> [repeat • MAC address is in the
MAC address <repeat-num>] [data-tlv-length format <xx-xx-xx-xx-xx-xx>.
<length-val>] • Allowed range of
Specifying remote MEP by lbm remote-mep <mep-id> [repeat repeat-num is 1–500.
MEP ID <repeat-num>] [data-tlv-length • Allowed range of
<length-val>] data-tlv-length is 0–1900.

Sending LBM messages to lbm multicast [repeat <repeat-num>] The only allowed value for
default multicast MAC repeat-num is 1.
address
Checking OAM loopback show lbm-results

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-2 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 1–64. This parameter
specifies 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 show linktrace-results

results
Examples
Configuring MD, MA, and MEP

This example illustrates configuring the following for ETX203AX or ETX205A:
• MD ID 1
• MA ID 1
• MEP ID 1:
 Remote MEP ID 2
 Classification VLAN 100
 To configure MD, MA, and MEP:

#**************************Configure MD
exit all

configure oam cfm

maintenance-domain 1
#**************************Configure MA
maintenance-association 1
#**************************Configure MEP
mep 1
bind ethernet 1
queue fixed 1 block 0/1
remote-mep 1..5,7,15..25,54,68,73..75,80,88..99,100,102,120
remote-mep 150,160..164,180
no shutdown
exit all
 To display the configured MD, MA, and MEP:

ETX-2# configure oam cfm maintenance-domain 1
ETX-2>config>oam>cfm>md(1)# info detail
no proprietary-cc
md-level 3
name string "MD1"
name string "MA1"
ccm-interval 1s
mep 1
bind ethernet 1
remote-mep 1..5,7,15..25,54,68,73..75,80,88..99,100,102,120,150,160..164,180
dest-addr-type ccm multicast pm unicast
ccm-initiate
ccm-priority 0
forwarding-method e-line
direction down
client-md-level 4
no ais
no shutdown
exit
exit
Configuring Service for Discovery

This example illustrates configuring a service with MEP and Rx/Tx flows, with the
flow and OAM parameters configured for service discovery by RADview, and with
PM statistics collection enabled for the service components, for the RADview PM
portal.
• Rx flow parameters:
 Ingress port=Ethernet port 1, egress port=Ethernet port 3
 Classification=VLAN 21
 Service name=gold

• Tx flow parameters:
 Ingress port=Ethernet port 3, egress port=Ethernet port 1
 Classification=VLAN 1
 Service name=gold
• MEP parameters:
 MD ID=10
 MA ID=10
 MEP ID=101
Note VLAN classification must not be configured for the MEP, in order to facilitate the
service discovery.
 Remote MEP ID=20

 Service ID=1
 Dest NE ID=1
#**************************Enable PM in device
exit all
configure
reporting
pm
exit
#**************************Configure classifiers
flows
match vlan 1
exit
match vlan 21
exit
#**************************Configure Rx flow
flow v21_v1
classifier v21
service-name gold
no shutdown
exit
#**************************Configure Tx flow
flow v1_v21
classifier v1
service-name gold
no shutdown
exit all

#**************************Configure MEP, service, and dest NE

configure oam cfm
mep 101
bind ethernet 1
flow uni-direction rx v21_v1
flow uni-direction tx v1_v21
remote-mep 20
no shutdown
service 1
dest-ne 1
loss single-ended lmm-synthetic lm-mode tx-rx
remote mep-id 20
exit
no shutdown
exit all
Viewing MEP Status and Remote MEP

The following illustrates displaying MEP status and remote MEP.
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)# show status
Direction : Down
Classification Profile : Class_A
CCM Priority : 7
MD Name : MD1
MA Name : MA1
Test Status : Off
MEP Defect : Status

Rx LCK : Off
Rx AIS : Off
Cross Connected CCM (Mismatch; Unexpected MD Level) : Off
Invalid CCM (Unexpected MEP; Unexpected CCM Period) : Off
Remote MEP Remote MEP Address Operational Status

-----------------------------------------------------------------------------
4 00-20-D2-2C-97-A9 OK
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)# show remote-mep 4 status

Remote MEP Address : 00-20-D2-2C-97-A9
Operational Status : OK
Configuring Service and Destination NE

This section illustrates configuring the following 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
 To configure service and destination NE:

exit all
configure oam cfm ma 1 ma 1 mep 1
service 1
dest-ne 3
exit
no shutdown
exit all
 To display the configured service and destination NE:

ETX-2# configure oam cfm ma 1 ma 1 mep 1 service 1
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)#info detail
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 user-data
no delay-measurement-bin
no delay-var-measurement-bin
exit
no shutdown
Configuring Service Event Reporting

This section illustrates configuring OAM CFM event reporting as follows:
• 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

Counter Event Type Rising Threshold Falling Threshold Sampling Interval
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-2 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-2 to
the network) exceed 10^-4, i.e. more than one frame out of 10,000 LMMs sent
for this service are lost.
 To configure OAM CFM event reporting:

#************** Define the service delay thresholds
exit all
configure oam cfm ma 5 ma 8 mep 3 service 4
delay-threshold 10
exit all
#************** Define the service event reporting counters

#****************** Counter: Frames Above Delay
configure fault cfm
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
#****************** Counter: Frames Above Delay Variation

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
#****************** Counter: Far End Frame Loss Ratio

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
#****************** Counter: Near End Frame Loss Ratio

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
#****************** Counter: Far End Unavailability Ratio

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
#****************** Counter: Near End Unavailability Ratio

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 all
 To display the defined service event reporting counters:

ETX-2# configure fault cfm
ETX-2>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
Viewing MIP Status

You can display the status of an active MIP.
ETX205A>config>oam>cfm>md(1)>mip(1)# show status
Rx Flow : Rx_v20
Bind Port : Ethernet 1
MAC Address : 00-20-D2-53-45-50
Tx Flow : Tx_v20
MD Name : MD1
MD Level : 3
Viewing Running Statistics

ETX-2>config>oam>cfm>md(1)>ma(100)# mep 100
ETX-2>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics running

Running
-----------------------------------------------------------------------------
CCM P-bit : 2 MD Level : 3

CCM Tx frames : 1286
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames
-----------------------------------------------------------------------------
101 1286
102 0
103 0
ETX-2>config>oam>cfm# ma 1 ma 1 mep 1 serv 1
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
TX Frames : 1548 1548
RX Frames : 1548 1548
Lost Frames : 0 0
Two Way Delay (mSec) : 0.062

Two Way IFDV (mSec) : 0.004
Frames Above Delay Threshold : 0
Frames Above IFDV Threshold : 0
Elapsed Time (sec) : 31271
Loss and Delay Measurements Messages

-----------------------------------------------------------------------------
Tx Rx
LMMs : 31271 LMRs : 0
DMMs : 31278 DMRs : 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# dest-ne 3
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 1759 1759
Rx Frames : 1759 1759
Frames Loss : 0 0
Unavailable Seconds : 0 0
Available S
Two Way Delay (mSec) : 0.062

Two Way IFDV (mSec) : 0.004
Current Forward IFDV (mSec) : 0.002
Current Backward IFDV (mSec) : 0.002

-----------------------------------------------------------------------------

Tx Rx
LMMs : 1759 LMRs : 1759
DMMs : 1759 DMRs : 1760
Viewing Current Statistics

ETX-2>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics current
Current
-----------------------------------------------------------------------------

Elapsed Time : 135
CCM Tx frames: 137
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames
-----------------------------------------------------------------------------
101 136
102 0
103 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 1863 1863
Rx Frames : 1863 1863
Lost Frames : 0 0
Frame Loss Ratio (%) : 0.0000 0.0000
Min Average Max

(mSec) (mSec) (mSec)
Two Way Delay : 0.037 0.059 0.084
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018


-----------------------------------------------------------------------------
Tx Rx
LMMs : 722 LMRs : 0
DMMs : 722 DMRs : 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 739 739

Rx Frames : 739 739

Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Available Seconds : 739 739
Two Way Unavailable Seconds : 0

Two Way Available Seconds : 739
Min Average Max

Two Way Delay : 0.037 0.059 0.084
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018


-----------------------------------------------------------------------------
Tx Rx
LMMs : 740 LMRs : 740
DMMs : 739 DMRs : 739
Viewing Interval Statistics

ETX-2>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics interval 1
Interval
-----------------------------------------------------------------------------

Interval : 1
Time Stamp : 28-10-2015 11:09:59
Valid Data : Valid
CCM Tx frames : 303
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames
-----------------------------------------------------------------------------
101 303
102 0
103 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statist interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Forward Backward
Tx Frames : 1541 1541

Rx Frames : 1541 1541

Lost Frames : 0 0
Frame Loss Ratio (%) : 0.0000 0.0000
Min Average Max

Two Way Delay : 0.039 0.059 0.083
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018

-----------------------------------------------------------------------------
Tx Rx
LMMs : 900 LMRs : 0
DMMs : 900 DMRs : 0
ETX-205A>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)#
ETX-205A>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)# show statistics total-intervals
Total Intervals
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Lost Frames : 0 0
Min Average Max

Two Way Delay : 0.000 0.000 0.000
Two Way IFDV : 0.000 0.000 0.000

-----------------------------------------------------------------------------
Tx Rx
LMMs : 0 LMRs : 0
DMMs : 0 DMRs : 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statist interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Valid Data : Valid
Time Stamp : 19-05-2014 10:25:06
Forward Backward
Tx Frames : 899 899
Rx Frames : 899 899
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Two Way Unavailable Seconds : 0

Two Way Available Seconds : 1195

Min Average Max

Two Way Delay : 0.039 0.059 0.083
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018

-----------------------------------------------------------------------------
Tx Rx
LMMs : 899 LMRs : 899
DMMs : 900 DMRs : 900
ETX-2>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)>dest-ne(1)#
ETX-2>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)>dest-ne(1)# show statistics total-
intervals
Total Intervals
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ration (%) : 0.0000% 0.0000%
Min Average Max

Two Way Delay : 0.000 0.000 0.000
Two Way IFDV : 0.000 0.000 0.000
Forward IFDV : 0.000 0.000 0.000
Backward IFDV : 0.000 0.000 0.000

-----------------------------------------------------------------------------
Tx Rx
LMMs : 0 LMRs : 0
DMMs : 0 DMRs : 0
Configuring and Viewing Delay Measurement Bins

This section illustrates configuring delay measurement bins as follows:
• Bin1 used for round trip delay measurements, with threshold ranges (in
microseconds (μs)):
 0–15,000
 15,001–49,000
 49,001–55,000
 55,001–250,000
 250,001–5,000,000

• Bin2 used for round trip delay variation measurements, with threshold
ranges (in microseconds (μs)):
 0–15,000
 15,001–55,000
 55,001–105,000
 105,001–205,000
 205,001–5,000,000
 To configure delay measurement bins:

#*****************Configure delay measurement bin: bin1
exit all
config oam cfm
measurement-bin-profile bin1
thresholds 15000,49000,55000,250000
exit
#*****************Configure delay measurement bin: bin2

measurement-bin-profile bin2
thresholds 15000,55000,105000,205000
exit
#*****************Configure dest NE 3 with the delay

measurement bins
ma 1 ma 1 mep 1 serv 1 dest-ne 3
delay-measurement-bin profile bin1
delay-var-measurement-bin profile bin2
exit all
 To display delay measurement bins:

ETX-2# config oam cfm ma 1 ma 1 mep 1 service 1 dest-ne 3# ETX-
2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)#show
delay-measurement-bins rt-delay all
Type : rt Delay
Current
Bin range Rx DMR

(us)
---------------------------------------------------------------
1 0..15000 0
2 15001..49000 0
3 49001..55000 0
4 55001..250000 0
5 250001..5000000 0
Type : rt Delay
Interval Bin
range Rx DMR
(us)
---------------------------------------------------------------
1 1 0..15000 36
1 2 15001..49000 0

1 3 49001..55000 0
1 4 55001..250000 0
1 5 250001..5000000 0
2 1 0..15000 753
2 2 15001..49000 0
2 3 49001..55000 0
2 4 55001..250000 0
2 5 250001..5000000 0
3 1 0..15000 713
3 2 15001..49000 0
3 3 49001..55000 0
3 4 55001..250000 0
3 5 250001..5000000 0
ETX-2>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)#
show delay-measurement-bins rt-delay-var all
Type : rt Delay Var
Current
---------------------------------------------------------------
Bin range Rx DMR
(us)
---------------------------------------------------------------
1 0..15000 0
2 15001..55000 0
3 55001..105000 0
4 105001..205000 0
5 205001..5000000 0
Type : rt Delay Var
Interval Bin
range Rx DMR
(us)
---------------------------------------------------------------
1 1 0..15000 36
1 2 15001..55000 0
1 3 55001..105000 0
1 4 105001..205000 0
1 5 205001..5000000 0
2 1 0..15000 753
2 2 15001..55000 0
2 3 55001..105000 0
2 4 105001..205000 0
2 5 205001..5000000 0
3 1 0..15000 713
3 2 15001..55000 0
3 3 55001..105000 0
3 4 105001..205000 0
3 5 205001..5000000 0

OAM CFM: A service with the You tried to configure more Check the priority bit classification and
same priority already exists than one service on the same verify that there is no other configured
priority bit. service on it.
OAM CFM: A Maintenance You previously configured Configure the MA with another name
Association with this format and another MA with the same or format.
name already exists configuration.
OAM CFM: A Maintenance You previously configured Configure the MD with another format,
Domain with this format name another MD with the same name, or level.
and level already exists configuration.
OAM CFM: Active MEP cannot You tried to delete or shut Disassociate the flow from the MEP,
work without a flow down a flow that is being used and then delete or shut down the flow.
by a MEP.
OAM CFM: Active MEP requires You did not configure a single Configure at least one remote MEP.
at least 1 remote MEP remote ID on the MEP.
OAM CFM: Active MIP cannot You did not configure a TX or Configure a TX or Rx flow on the
work without a flow Rx flow on the manual manual MIP that you configured.
MIP that you configured.
OAM CFM: Active MIP cannot The Tx or RX flow that you Configure the MIP with an active Tx or
work without an active flow configured on the MIP is not Rx flow.
active.
OAM CFM: AIS cannot be You configured MEP on a Configure MEP on a maintenance
enabled when MD level equals maintenance Domain with Domain other than Level 7.
seven (7) Level 7, and therefore AIS
could not be enabled on it.
OAM CFM: Cannot activate a You tried to activate a Service Configure a Dest NE under Service.
service without a dest-NE that has no Dest NE
configured under it.
OAM CFM: Cannot activate MIP You did not configure a bound Configure a bound port on the manual
without a bound port port on a manual MIP. MIP.
OAM CFM: Cannot change You tried to change Disable Fault CFM entity, and then
parameters when active parameters on an active Fault change parameters.
CFM entity.
OAM CFM: Cannot change pm to You tried to configure a Configure a multicast destination
multicast because there is a multicast destination address address on a Dest NE that does not
destne that counts loss on a Dest NE that has user have user data loss measurements.
data loss measurements.
OAM CFM: Cannot configure You configured a MEP to work Configure only one remote MEP per
destination address type unicast with unicast destination MEP.
and more than one remote MEP address, but also assigned to
it more than one remote MEP.
OAM CFM: Cannot configure ICC It is not legal to configure MD Change MA name to format other ICC.
with MD name name when MA name format
is ICC.

OAM CFM: Cannot delete a You tried to delete a remote Disassociate the remote MEP from the
remote MEP that is being used MEP from MEP configuration, Dest NE and then delete it.
by a dest-ne while this remote MEP is being
used in one of the MEP’s Dest
NEs as remote peer address.
OAM CFM: Cannot delete destne; You tried to delete or shut Wait until RFC2544 test has completed,
it is bound to rfc2544 test. down a Dest NE that is used and then delete or shut down the Dest
on an active RFC2544 test. NE.
OAM CFM: Cannot delete MEP; You tried to delete a MEP Finish using the MEP under the Y.1564
MEP is under Y.1564 test. which is being used in a test, and then delete it.
Y.1564 test.
OAM CFM: Cannot delete or You tried to modify or delete a Remove the Bin profile from the Dest
change measurement profile used Bin profile. NE, and then modify or delete it.
first remove from dest-NE
OAM CFM: Cannot enable loss You tried to configure user Configure Dest NE without a multicast
measurement because pm is in data loss measurements on a address or use another loss
multicast Dest NE with multicast measurement method.
destination address.
OAM CFM: Cannot enable more You enabled more than the Enable up to 600 Rx SLM PPS.
than 600 PPS 600 Rx SLM PPS limit of the
device.
OAM CFM: Cannot enable service You are trying to enable (no Enable the MEP (no shutdown).
while the MEP is not active shutdown) a service of one of
the MEP’s priority bits, while
the MEP is not enabled
(shutdown).
OAM CFM: Cannot have a dest- You tried to configure remote Activate MEP’s CCM or use remote-mac.
NE remote MEP-ID when CCM is MEP Id on the Dest NE while
disabled MEP’s CCM is not active.
OAM CFM: Cannot modify a You tried to change remote Shut down the service, delete the Dest
remote MEP while it is being MEP parameters in MEP NE that uses this remote MEP or
used configuration while the change its configuration to remote
Remote MEP is being. used MAC.
OAM CFM: Cannot resolve this You are using remote MEP ID Use a remote MEP ID only of remote
remote MEP MAC address for loopback or linktrace MEP MAC address that was learned by
transmission, but the remote the CCM.
MEP MAC address was not
learned by the CCM yet.
OAM CFM: Cannot send more You sent more than one Send only one LB message to multicast
than one LB to multicast loopback message to the same address.
address multicast destination address
of the MEP. All relevant remote
MEPs should answer – one LBR
from every remote MEP.

OAM CFM: Cannot shutdown You tried to disable a MEP Finish using the MEP under the Y.1564
MEP; MEP is under Y.1564 test. which is being used in a test, and then disable it.
Y.1564 test.
OAM CFM: Classification: Conflict You previoulsy configured Configure the MEP with a different
with another MEP classification another MEP with the same classification.
parameters.
OAM CFM: Classification: Inner You tried to configure a MEP Configure the MEP with a supported
VLAN range is not supported with a non-supported flow flow classification.
classification.
OAM CFM: Classification: You tried to configure a MEP Configure the MEP with a supported
Unsupported criteria with a non-supported flow flow classification.
classification.
OAM CFM: Classification: VID=0 You configured an Illegal VLAN Configure a VLAN with ID other than 0
is invalid on a MEP. on the MEP.
OAM CFM: Client MD level must You tried to configure a client Configure client MD level higher than
be higher than MD level Maintenance Domain Level MD level.
(MDL) lower than or equal to
the MDL.
OAM CFM: Conflict between You configured a destination Select a valid destination MAC address.
OAM destination MAC address MAC address that conflicts
and device MAC address with the device’s MAC address.
OAM CFM: Deactivate service You did not deactivate service Deactivate service, and then erase last
before erasing last dest-NE before erasing last active Dest active Dest NE under it.
NE under it.
OAM CFM: dest-NE out of range You configured Dest NE ID out Confiugre a Dest NE ID between 1 and
the range 1..255. 255.
OAM CFM: EVC.COS: Illegal You did not configure Local Configure Local MEP Id.
remote MEP configuration MEP Id (can only occur via
SNMP).
OAM CFM: EVC.COS: More than 1 You tried to configure two Configure only one MEP on the same
MEP on the same MA is only MEPs on the same MA. MA or use vlan.p_bit classification for
allowed when all classifications all MEPs on MA.
are VLAN + pBit
OAM CFM: EVC.COS: Priority bit You did not configure EVC.cos Configure the EVC.cos MEP’s flow
doesn't match classifier MEP’s flow classification to classification to match the MEP’s
match the MEP’s configured configured priority.
priority.
OAM CFM: EVC.COS: Two MEPs You tried to configure two Configure two MEPs on the same MA
on the same MA must use MEPs on the same MA with with different priorities.
classifiers with same VLAN and same priority.
different priorities

OAM CFM: Event type must be You tried to configure for Configure an event for the Fault CFM
different than none unavailability, a Fault CFM frame report entity.
frame report entity that has
no event.
OAM CFM: Exceeded number of You tried to define more than Define only up to 100 fault CFM
entries in alarmTable 100 fault CFM entities. entities.
OAM CFM: Falling On Fault CFM entity, you Configure a lower limit for alarm falling,
alarm_threshold must be less configured a lower limit for which is lower than the higher limit of
than rising alarm_threshold alarm falling, which is higher alarm rising.
than the higher limit of alarm
rising.
OAM CFM: FPGA supports up to You tried to configure Bin Configure Bin profile limit which is up
1000000 uSec (1 second) profile limit which is higher to 1 second.
threshold than 1 second.
OAM CFM: Illegal change of You tried to change the

bounded port bounded port from a Bridge
Port to a regular port or vice
versa.
OAM CFM: Illegal MAC address You configured the MAC Configure a valid MAC address.
address with all zeroes or all
ones.
OAM CFM: Illegal queue block You did not configure a queue Configure a queue block on the MEP.
block on the MEP.
OAM CFM: Illegal value CFM entity was configured Configure CFM entity with legal indices.
with illegal or out of range
indices (for example, loopback
on an active CFM loopback).
OAM CFM: Invalid falling You configured the falling Configure the falling threshold
threshold threshold to less than one-of- between one-of-thousand and 1000
thousand or higher than 1000 one-of-thousand. Make sure that the
one-of-thousand. Or you falling threshold value is lower than the
configured the falling rising threshold.
threshold to a higher value
than the rising threshold.
OAM CFM: Invalid forwarding You configured E-LAN Configure another forwarding method.
method for MEP with direction forwarding method on a Down
set to down MEP.
OAM CFM: Invalid rising You configured the rising Configure the rising threshold between
threshold threshold to less than one-of- one-of-thousand and 1000 one-of-
thousand or higher than 1000 thousand. Make sure that the rising
one-of-thousand. Or you threshold value is higher than the
configured the rising threshold falling threshold.
to a lower value than the
falling threshold.

OAM CFM: Invalid time interval You tried to configure a fault Configure an interval between 1 and
CFM interval which is shorter 60 seconds.
than 1 second or longer than
60 seconds.
OAM CFM: Lmm and dmm You configured lmm-synthetic Configure one second on both lmm and
intervals must be equal if lmm- while in the service level, but dmm.
synthetic was selected you also set lmm or dmm
intervals to be different than 1
second.
OAM CFM: Local MEP-ID and You assigned the same ID to a Configure the remote MEP and local
remote MEP-ID are equal remote MEP and local MEP. MEP with different IDs.
OAM CFM: MA and MEP VLAN You configured a classification Configure a classification VLAN on the
don't match VLAN on MA level that does MA level to match the configured
not match the configured classification VLAN on the MEP level.
classification VLAN on the MEP
level.
OAM CFM: MA name max length You configured an MA name in Configure an MA name in ICC format up
is 13 characters when format is ICC format more than 13 to 13 characters long.
ICC characters long.
OAM CFM: MA-ID size exceeds You defined an MD or MA Define an MD or MA name that is not
limit name length that is longer longer than the maximum allowed
than the maximum allowed length.
length.
OAM CFM: Max allowed dest-NEs You tried to add more than Configure up to the allowed number of
in active services already allowed maximum Dest NEs. Dest NEs.
reached
OAM CFM: Max allowed number You already configured the Configure up to the allowed number
of remote MEPs reached maximum allowed number of remote MEPs per device.
remote MEPs on the device.
OAM CFM: MD level out of range You configured an MD level Configure an MD level between 0 and
that is smaller than 0 or bigger 7.
than 7 (can happen only via
SNMP).
OAM CFM: MEP direction is not You bound the MEP to the Bind a MEP of the correct direction to a
correct for port type wrong port. For example: You port.
bound a Down MEP to a Bridge
port or an UP MEP to an SVI.
OAM CFM: MEP must be active You tried to send LBM or LTM Activate MEP, and then send LBm or
for this action on a non-active MEP. LTM.
OAM CFM: MEP out of range You configured a MEP ID Configure a MEP ID between 1 and
outside the range 1..8191 8191.
OAM CFM: Name cannot be You did not configure an MD Configure a name for MD or MA.
empty or MA name.

OAM CFM: Name length too long You configured an illegal MD or Configure an MD/MA name up to 43
MA name length (more than characters.
43 characters).
OAM CFM: NE remote MEP-ID or You tried to define Dest NE Define a Dest NE that has different
MAC address conflicts with that has same indices as an indices than an existing Dest NE.
another NE on the current existing Dest NE.
service
OAM CFM: No port is bound to You tried to activate a MEP Bind a port to the MEP.
MEP with no bounded port.
OAM CFM: Only 10 TX flows per You tried to configure more Configure up to 10 Tx flows.
MEP are allowed than 10 Tx flows on a MEP.
OAM CFM: Only one destne can You tried to configure more Configure only one Dest NE on a
be configured if loss user data than one Dest NE on a service service with User Data Loss
was selected with User Data Loss measurement method.
measurement method.
OAM CFM: Only one RX flow per You tried to configure more Configure only one Rx flow on the MEP.
MEP is allowed than one Rx flow on a MEP.
OAM CFM: Please make sure you You configured a MEP to work When MEP is shutdown, configure a
configure a unicast type and with unicast destination valid unicast address as destination
MAC address when MEP is address, but did not configure address.
shutdown a valid unicast address as
destination address.
OAM CFM: Port is occupied with You tried to send loopback or Send loopback or linktrace only when
another action linktrace while there is another no other loopback or linktrace
active loopback or linktrace respectively, is active.
respectively.
OAM CFM: Port level MEP: Only You tried to configure more Configure only one MEP on an
one allowed per port than one MEP on an untagged untagged port.
port.
OAM CFM: Priority out of range You configured a Priority that Configure a Priority between 0 and 7.
is smaller than 0 or bigger
than 7 (can happen only via
SNMP).
OAM CFM: Profile must have You tried to use a flow with Use a flow with only one VLAN
only one entry multiple VLANs matching matching classification.
classification.
OAM CFM: Profile was not found You used a wrong or non- Use a correct or existing profile.
existing profile.
OAM CFM: Remote MEP doesn't You tried to configure a Configure the remote MEP ID at the
exist remote MEP Id at the Dest NE, MEP as Remote.
as remote peer address, but
this Remote MEP Id is not
configured at the MEP as
Remote.

OAM CFM: Remote MEP ID You tried to configure a Configure the remote MEP with an ID
cannot be equal to local MEP ID remote MEP with the same ID that is different than the MEP ID.
as the MEP itself.
OAM CFM: rfc2544 test is in You tried to change the status Wait until RFC2544 test terminates,
progress; cannot enable service of a service that one of its and then change the service’s status.
Dest NEs is used on an active
RFC2544 test.
OAM CFM: Service out of range You configured a service ID Configure a service ID between 1 and
OAM CFM: The Rx and Tx flows You configured Rx and Tx Configure Rx and Tx flows to start and
must be in opposite directions. flows so that they do not start end on opposite Ingress and Egress
and end on opposite Ingress ports.
and Egress ports.
OAM CFM: The Rx flow must You configured manual MIP, so Configure the Rx flow’s Ingress port to
originate from the bound port. that Rx flow’s Ingress port is be equal to the MIP’s bound port.
not equal to the MIP’s bound
port.
OAM CFM: There is no MEP with You tried to create an entry in Connect the flow to a MEP that already
those indices the MepFlow table and to exists.
connect between a flow and a
MEP that does not exist (can
only occur via SNMP).
OAM CFM: VID out of range You configured a VLAN ID Configure a VLAN ID between 1 and
OAM CFM: When using untagged You tried to configure a MEP Configure a MEP with EVC.cos
or EVC.COS MEP classification with EVC.cos classification and classification and Service Id equal to 1.
only service index 1 is permitted Service Id other than 1.
OAM CFM: MEF-46 should have You tried to configure MEF-46 Configure MEF-46 on a MEP that is
Tx/Rx flow classification on a MEP that is configured configured with Rx and Tx flows.
with a classifier profile or
VLAN.
11.3 OAM EFM

Ethernet OAM (Operation, Administration, and Maintenance) functions provide
end-to-end connectivity checks and performance monitoring.
Ethernet in the First Mile (EFM) is a link-layer OAM protocol that operates at the
level of the single link for remote management and fault indication. ETX-2 can
act as the active or passive side in an IEEE 802.3ah application.
The term last mile is often used by core network engineers to refer to access
links from an operator’s central office to the customer’s locations. The opposite
term first mile refers to the same access links but from the customer’s
perspective.
ETX-2 OAM EFM 11-71

This section covers the monitoring of the Ethernet links using OAM EFM (OAM
Ethernet at the First Mile). ETX-2 can act as the active or passive side in an IEEE
802.3-2005 application.
Applicable Products
Standards
IEEE 802.3-2005
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, loopback support, etc. 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 Ethernet/logical MAC/PCS ports.
Configuring OAM EFM

There are two available OAM EFM descriptors. Each can be configured to indicate
active or passive OAM EFM. When you enable OAM EFM for a port, you assign a
descriptor to the port.
11-72 OAM EFM ETX-2

You can configure OAM EFM for Ethernet/logical MAC/PCS ports. When link OAM
(EFM) is enabled for a port, you can view its status by displaying the port status
(show status). You can also display the OAM (EFM) parameters and OAM (EFM)
statistics.
 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/logical MAC/PCS port:

1. Navigate to configure port ethernet [<slot>/]<port> or
configure port logical-mac <port> or configure port pcs <port>, respectively.
The prompt config>port>eth([<slot>/]<port-num>)# or
config>port>log-mac(<port>)# or config>port>pcs(<port>)# is
displayed.
Enabling link OAM (EFM) efm descriptor <1–2> The EFM descriptor must exist
before you can assign it to a port
Note: In order for link OAM (EFM)
to function properly, 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 Note: Relevant only for
parameters Ethernet/PCS ports, if link OAM
(EFM) is enabled.
Displaying link OAM (EFM) show oam-efm-statistics Note: Relevant only for
statistics Ethernet/PCS ports, if link OAM
(EFM) is enabled.
Commands in level efm
Enabling loopback loopback Type no loopback to disable

loopback.
Enabling SNMP tunneling for OAM snmp-tunneling Type no snmp-tunneling to

EFM disable snmp tunneling.
Examples
 To enable active link OAM (EFM) for ETX203AM Ethernet port 1/1:
#************** Configure L2CP profile for OAM EFM
ETX-2 OAM EFM 11-73

exit all
mac 0x02 peer
exit all
#************** Configure OAM EFM descriptor

configure oam efm
descriptor 2 active
exit all
#************** Configure Ethernet port 1/1:

#************** Associate L2CP profile and OAM EFM descriptor
efm descriptor 2
exit all
 To display the link OAM (EFM) status for Ethernet port 1/1
ETX-2>config>port>eth(1/1)# show oam-efm
Administrative Status : Enabled
Operational Status : Link Fault
Loopback Status : Off
Information
---------------------------------------------------------------
Local Remote
Mode : Active --
MAC Address : 00-20-D2-30-CC-9D --
Unidirectional : Not Supported --
Vars Retrieval : Supported --
Link Events : Supported --
Loopback : Supported --
PDU Size : 1518 --
Vendor OUI : 0x0020D2 --
11.4 TWAMP
ETX-2 provides a low-scale (150 sessions) OAM TWAMP Light mechanism for
measurement of one-way and two-way metrics between Layer-2 or Layer-3
network elements.
ETX205A with the PMC option provides a high-scale (3000 sessions) TWAMP
mechanism for measurement of the IP performance of Layer-3 networks at all
locations, without the need for a special performance management system.
Applicable Products
11-74 TWAMP ETX-2

• Full TWAMP, UDP test, and RADM are relevant for ETX205A with the PMC
option.
Standards
RFC 5357 – A Two-Way Active Measurement Protocol (TWAMP)
RFC 2330 – Framework for IP Performance Metrics
RFC 2681 – A Round-trip Delay Metric for IPPM
RFC 4656 – A One-way Active Measurement Protocol (OWAMP)
RFC 5481 – Packet Delay Variation Applicability Statement
RFC 4737 – Packet Reordering Metrics
RFC 5560 – A One-Way Packet Duplication Metric
ITU-T Y.1540 – Internet protocol data communication service – IP packet
transfer and availability performance parameters
ITU-T Y.1541 – Network performance objectives for IP-based services
ITU-T Y.1543 – Measurements in IP networks for inter-domain performance
assessment
Benefits
OAM TWAMP measures the IP performance of Layer-2 or 3 networks at all
locations, without the need for a special performance management system. Its
ICMP Echo service is useful for probing and general debugging, such as path
continuity and integrity verification.
PMC (in ETX205A) is a powerful application for ensuring SLA parameters in
Layer-3 networks, by testing thousands of Layer-3 services simultaneously.
OAM TWAMP
ETX-2 supports low-scale (150 sessions @10 pps) OAM TWAMP, in the following
scale:
• Up to 15 Layer-3 controllers (Router interfaces of HW Router)
• Up to a total of seven Layer-2 controllers (RI over Bridge or RI over L2
probe)
• Up to three Layer-2 controllers over L2 probe
• Up to 15 peers per device are supported for TWAMP controllers.
• Multiple TWAMP sessions (up to 150) can be supported over a single Layer-2
service / TWAMP controller.
ETX-2 TWAMP controllers and responders can operate in the following modes:
• Layer-2 E-Line (pont-to-point) service – L2 probe configuration. The TWAMP
controller/responder is associated with a router interface and bound to an
Ethernet/logical MAC/PCS port and flow.
ETX-2 TWAMP 11-75

 IPv6 test sessions are not supported in this mode.

 Up to a total of three controllers and responders are supported.
Figure 11-19. TWAMP Controller over L2 E-Line Service
• Layer-2 E-LAN service over bridge – The TWAMP controller/responder is

associated with a router interface that is connected to a bridge port via an
SVI.
Figure 11-20. TWAMP Controller over Bridge (E-LAN Service)
TWAMP can be configured on an independent VRF. A total of seven

controllers/responders can be configured (for example, three controllers and
four responders).
PMC TWAMP
ETX205A with PMC provides TWAMP controllers and responders with higher
limits than ETX-2 TWAMP for measurement of the IP performance of your
Layer-3 network at all locations.
ETX205A with PMC supports TWAMP with the following capabilities:
• TWAMP Light
• Full TWAMP, including TWAMP Control protocol
• ICMP echo
• UDP echo
• Responder Agnostic Delay Measurement (RADM) – one-way measurement
without local/remote node TOD (NTP) lock
11-76 TWAMP ETX-2

The PM protocol is defined per peer towards specific responder. It is possible to

operate mixed protocols per peer in the same TWAMP controller.
TWAMP Light is recommended for use in a high-scale environment, to avoid the
TCP overhead. In a low-scale environment, Full TWAMP is recommended, as the
test can be configured on the controller side only, reducing operation overhead.
PMC in ETX205A supports up to 64 TWAMP controllers and eight responders.
Responder Light functionality is supported on a different IP address than the
controller. Each controller and responder is associated with a router interface
(up to 64) within the configured router entity, with the same IP address as the
controller/responder, which is bound to an x86 Ethernet port, and assigned a
VLAN.
You can configure PMC controllers (one or more) with a total of 3,000 sessions
@10 pps and up to 3,000 peers. You can divide the 3,000 sessions between the
peers, as desired. For example, all 3,000 sessions for a single peer, or 3,000
sessions for 3,000 peers (i.e. one session per peer). You can configure PMC
responders (one or more) with a total of 100 test sessions, simultaneously with
the 3,000 sessions initiated by the controllers.
TWAMP Light
Note You can activate TWAMP Light on any ETX-2 device, as well as on PMC in
ETX205A.
TWAMP Light architecture comprises two hosts:

Controller Functions as Session-Sender
Responder Functions as Session-Reflector
TWAMP Controller TWAMP Responder
Session-Sender Session-Reflector
TWAMP Test
Figure 11-21. TWAMP Light Logical Model
Information is exchanged between TWAMP controllers and responders, using the

TWAMP Light mechanism, thus enabling the monitoring of sessions.
TWAMP Light works as follows:
1. The controller establishes a test session with the responder.
2. After the TWAMP test session is established, the controller transmits test
packets to the responder.
3. The responder adds information to the packet, including Rx stamp and Tx
stamp.
4. The responder reflects the test packets to the controller.
The controller processes the resulting measurements and calculates metrics (one
way or round-trip) that can be displayed in test reports (see Viewing TWAMP
Reports).
ETX-2 TWAMP 11-77

In addition to viewing the metrics in the test reports, you can also view them via
a network management system portal, such as the RADview Performance
Management portal, if collection of PM statistics for the OAM TWAMP
component is enabled (via pm-collection command in the reporting level). See
Performance Management below for details.
Full TWAMP
Note You can configure Full TWAMP only on the PMC in ETX205A.
Full TWAMP on ETX205A with PMC supports the following:

• IPv4 and IPv6, tagged and untagged, TWAMP frame format
• PCP, DSCP, and TC (IPv6) for TWAMP generated traffic
• Up to 64 TWAMP controllers and eight responders. Each controller and
responder is associated with a router interface within the configured router
entity, with the same IP address as the controller/responder. Controllers and
responders can reside on the same VRF or on different VRFs (up to four).
• TWAMP controller supports up to 3,000 peers and up to 3,000 test sessions.
• Maximum rate per session: 10 pps for TWAMP peers.
• PMC controllers and responders each support timestamp accuracy of at least
50 usec; 80 usec for one-way and 2 msec for RADM.
• Status and statistics
• Responder functionality, at a different IP address than the controller.
• Up to eight responders that together handle a total of 100 test sessions,
simultaneously with the 3000 sessions initiated by the controllers residing
on the same device.
• Multiple VRFs – up to 4
Full TWAMP architecture comprises two hosts:
Controller Functions as Control-Client and Session-Sender
Responder Functions as Session-Reflector and Server
TWAMP Controller TWAMP Responder
Session Sender Session Reflector
TWAMP Test
Vendor Vendor
Specific Specific
TWAMP Control
Control Client Server
Figure 11-22. Full TWAMP Logical Model
Full TWAMP consists of two inter-related protocols:
11-78 TWAMP ETX-2

TWAMP Control Layered over TCP; used to initiate, start, and stop
measurement sessions.
TWAMP Test Layered over UDP; used to exchange test packets between
two measurement nodes.
TWAMP Control supports the negotiation of two-way active measurement

sessions in a straightforward manner. At session initiation, there is a negotiation
of sender and receiver port numbers, and some attributes of the very general
[RFC 2330] notion of packet type, including per-hop behavior (PHB) [RFC2474],
which are used to support the measurement of two-way network characteristics
across differentiated services networks.
The initiator of the measurement session establishes a TCP connection to the
default well-known port 862, or other configurable port, on the target point and
this connection remains open for the duration of the TWAMP Test sessions. A
TWAMP server listens to this port.
TWAMP-Control messages are transmitted only before TWAMP-Test sessions are
actually started and after they are completed (with the possible exception of an
early Stop-Sessions message).
The TWAMP-Control protocol resolves different capability levels between the
Control-Client and Server (e.g. mode selection – authentication/encryption).
As the TWAMP Control protocol transmits information between controller and
responder, there is no need to configure the responder. It is configured
automatically, according to the information transmitted from the controller via
the TWAMP Control protocol.
Before test sessions can begin, a TCP Control connection between the TWAMP
Controller and TWAMP Responder must be set up, as described below.
The following table shows the steps you need to perform in order to configure
the TWAMP generator in the PMC.
Table 11-9. TWAMP Generator Configuration Steps
# Step Where Performed
1 Configure router interfaces for management and TWAMP. TWAMP generator in PMC
2 Configure TWAMP controllers and responders. TWAMP generator in PMC
3 Configure SNMPv3. TWAMP generator in PMC
4 Configure NTP servers. TWAMP generator in PMC
5 Configure internal ports. ETX-2
6 Configure management and data flows, taking into account the ETX-2
VLANs used in the PMC TWAMP generator.
The implementation of TWAMP Control protocol enables:

• Interoperability of RAD TWAMP controller with 3rd party peers (routers,
CPEs); standard RAD TWAMP controller can activate test sessions to 3rd
party responders using a standard control protocol (specified in RFC5357,
RFC4656)
• Interoperability of 3rd party controller with RAD responders
ETX-2 TWAMP 11-79

• Reduction of operation overhead at the beginning of the session, as the test

can be configured on the controller side only. This is practical for low-scale
testing; in a high-scale environment, especially when there are many
configured peers, it is recommended to use TWAMP Light to avoid the TCP
overhead.
Setting Up a Connection on the Client Side

A connection is established between a TWAMP Controller and Responder on the
Client side, as follows:
1. You request (via CLI or SNMP) to create a peer between a TWAMP Controller
and a TWAMP Responder.
2. You optionally configure the TCP port on which the control connection
(peer) to the server is to be established. Default is 862.
3. The agent validates that the TCP port value that you selected is < 49151. If
not, it rejects your configuration attempt.
4. The control-client connection to the TWAMP server takes place on the TCP
port (default or configured), via the TWAMP connection setup procedure.
5. The client automatically selects the source TCP port for the control
connection in the range of 49152–65535. This TCP port number shall be
used for all control connection to different responders, and client shall
distinguish received control traffic based on source IP address of the
responders. Note that you cannot configure the source TCP port.
6. The client supportsonly unauthenticated, unencrypted mode ( ‘open mode’).
7. When the connection is established with the server, the client timestamps
its local time, and uses it when you request peer-information (peer-level
‘show status’ command).
Setting Up Connection on Server Side

A connection between a TWAMP Controller and Responder is established on the
Server side, as follows:
1. You enable Control protocol at the server side by configuring the Responder
without an IPPM type.
2. You optionally configure the TCP port on which the server is to listen for
connection attempts from the client. Default is 862.
3. The agent validates that the TCP port value that you selected is < 49151. If
not, it rejects the configuration attempt.
4. The server supports multiple peers, initiated from different clients.
5. The server accepts or rejects client attempt for connection.
After a connection has been made between the client and zerver, the client
must send to the server a request for each test session it wants to open on the
peer, as described below.
TWAMP Session Request on Client Side

1. The client sends a single request for each test session it wishes to open on
the peer.
11-80 TWAMP ETX-2

2. The source and destination UDP port of the outgoing TWAMP test packets
for the requested sessions are conveyed to the server.
3. The client monitors whether the test session has been accepted by the
server. If it has been rejected, the client raises an event.
TWAMP Session Request on Server Side

1. The server listens to TWAMP control messages from the client. If the request
is not valid, the server rejects it and raises an event.
2. If the request is valid, the server sends the client the UDP port value, so that
the client is aware that the UDP port is available at the reflector, and the
sender can commence test session on this UDP port. This UDP port is used
by the session sender as the destination UDP port for the transmitted test
packets.
3. If this UDP port is not available at the responder side, server sends an
alternate UDP port value.
4. Server configures the reflector to listen on this UDP port.
Starting Test Session – Client Side

1. The client sends a request to initiate all test sessions provisioned with the
server’s endpoint.
2. If the start session request is accepted by the TWAMP server, it must
commence as soon as possible. Otherwise, if it is rejected, the client
terminates the TCP connection with the server, and raises an event.
3. When you send a “no activate” command on the selected peer, or the peer’s
configured test duration expires, all test sessions on the peer are
terminated.
Starting Test Session – Server Side

• If the server decides to acknowledge starting the test session request from
the client, it configures the reflector to start processing the test packets to
be received from all peers’ test sessions. It then sends to the client the
acknowledgement to initiate test sessions.
You can configure the PMC to run full TWAMP, as described in Configuring PMC.
ICMP Echo Test
Note
This test can be run on any ETX-2 device, as well as on PMC in ETX205A.
ETX-2 supports the two-way (round trip) ICMP Echo test, a member of the
TWAMP tests. It is a useful tool for testing and debugging path continuity and
integrity verification.
The test, supported for both IPv4 and IPv6, is based on ICMP/ICMPv6 Echo
request/reply packets. The ICMP Echo test is defined per peer towards a specific
responder, which can be any device or workstation with standard IPv4/IPv6 stack
that responds to standard ICMP/ICMPv6 Echo request packets. The ICMP peer can
generate multiple ICMP Echo test sessions to the same responder; these tests
ETX-2 TWAMP 11-81

differ in ICMP identifier, and possibly in packet length and DSCP. The ICMP peer
can generate ICMP Echo tests in continuous and non-continuous modes.
You do not configure peer parameters for the ICMP Echo test. The calculation
mode is not configurable; it is automatically set to default (round-trip). The
responder sequence number is also set to its default (off).
ICMP Echo test is performed as follows:
1. ICMP Echo IPv4/IPv6 test generates test packets based on IPv4/IPv6 ICMP
Echo request standard packets.
2. ICMP Echo builds test packets with:
 Test session identifier
 Controller’s transmit sequence number
 Controller’s transmit timestamp
3. Controller identifies received packet according to ICMP identifier (represents
test session).
4. Packet’s round trip delay is calculated according to received and transmitted
timestamps.
5. Loss, duplicate, and reorder are calculated according to sequence number.
6. Metrics are calculated for roll-up window, current interval, and report interval
(as defined for TWAMP).
7. Metrics are collected, according to PM collection mechanism (as defined for
TWAMP).
8. ICMP Echo test events and alarms are generated as TWAMP events and
alarms with the same definitions.
 Delay result (na/pass/fail)
 DV result (na/pass/fail)
 Loss result (na/pass/fail)
UDP Echo Test
Note This test can only be configured on PMC in ETX205A.
UDP Echo is a client-server service, defined at the UDP port level, which uses
user packets for its measurements. As routers process pings at a lower priority
than actual user packets and sometimes even block them, UDP Echo’s method of
measuring packet transmission is more accurate than ICMP Echo, which uses
pings for its measurements, and may delay or discard ICMP Echo requests in a
manner that skews the measurement results.
UDP Echo packets traverse the same intermediate nodes and logical queuing
paths as the user data traffic of the same class of service. The class of service is
dictated by DSCP code bit settings, etc. or other network operator specific
criteria.
UDP Echo is performed as follows:
1. Once the peer of IPPM type udp-echo is activated, the UDP client (sender)
commences sending periodic UDP packets (udp-echo-request) to the UDP
11-82 TWAMP ETX-2

server (reflector), according to its test-profile attributes. It stores the

transmission time for performance metric calculations.
2. UDP server processes these packets and reflects them back to the UDP client
(udp-echo-response). UDP client validates the received UDP Echo response
packet, and stores the reception time for performance metric calculations.
Configure UDP Echo on PMC, as follows:
1. Configure the UDP client side:
a. Configure the controller peer with IPPM type: udp-echo.
b. At the peer level, configure multiple test sessions, differentiating
between them by their UDP port. For each test session, configure the
name, UDP port, test session, and DSCP.
2. Configure the UDP server side:
a. Configure the TWAMP responder with IPPM type: udp-echo.
b. Under the UDP Echo responder, configure multiple test sessions for the
peer, differentiating between them by their UDP port.
Note The TWAMP controller and responder can be configured with UDP Echo as its
IPPM type; however, UDP Echo can only be tested vs. third party equipment.
RADM
Note RADM can only be configured on the PMC in ETX205A.
Responder Agnostic Delay Measurement (RADM), a virtual ToD sync mechanism

implemented at the controller, enables calculating one-way KPIs, even in the
case that the controller and/or responder are not locked to an external ToD
source, such as NTP, SNTP, or PTP (i.e. the controller and responder are not
ToD-locked to each other).
The RADM algorithm retrieves the responder’s standard TWAMP timestamps T2
and T3 every TWAMP test packet, calculating the time-error between the
controller and responder. It then provides the TWAMP engine with new time
error compensated T2 and T3 timestamps for further delay/PDV calculations.
The RADM algorithm operates under the assumption that the network under test
is symmetric in nature, meaning that the minimum delay experienced during the
TWAMP test period is approximately the same on both forward (controller-to-
responder) and backward (responder to controller) directions.
As RADM operates at the TWAMP session level, the algorithm estimates and
compensates for controller-responder time error for each TWAMP session
independently, regardless of the session’s peer identity. This way, the calculated
controller-responder time error estimation represents the true controller-
responder time error experienced by the specific TWAMP session.
The initial RADM algorithm convergence takes time. While converging, TWAMP
provides approximate results. The convergence period depends mainly on the
quality of the network on which the TWAMP test is running. For instance, it is
expected that the RADM convergence period will last longer on Best-Effort
networks compared to real well-engineered carrier grade networks. In any case,
initial convergence time should not last more than a few minutes.
ETX-2 TWAMP 11-83

RADM, a relatively new technology, must meet both these conditions:

• The clock at the responder should be free-running rather than disciplined to
an external reference (such as NTP or PTP).
• The minimum physical one-way delay in the network should exceed 0.5
msec. Lower minimum physical one-way delays may render the estimated
one-way delay inaccurate in cases that the network one-way delay actually
falls below 0.5 msec.
Operation with the RADM mechanism is configurable at the peer level (see
Running Test Sessions Via Controller Peers).
MOS On Demand
Note This measurement is only displayed in the RADview Performance Management

portal for the PMC in ETX205A.
Voice call quality depends on a variety of factors, including:

• Type of handset and microphone
• Ambient noise in the room
• Network propagation delay
• Loss of bandwidth in narrow-band (telephony grade) voice
• Codec voice degradation
• Effect of a lost packet on the decoder
• Effect of a burst of packet losses
• Effect of packet delay variation (as some packets may arrive too late to be
used in the decoding)
Subjectively perceived voice quality is conventionally quantified on a scale of 1 to
5, where 5 is the highest score for excellent voice quality. People listen to a
voice call and rate its quality. The average score is then recorded as the mean
opinion score (MOS).
For the PMC, RAD has a similar MOS estimation mechanism based on TWAMP PM
KPIs (delay, delay-variation, loss, and more). It estimates the MOS that a caller
will experience based on measured packet loss ratio and one-way packet delay.
Its results can be used for planning purposes, for statistical monitoring of
customer satisfaction, and to proactively identify problematic network
conditions.
Factory Defaults
By default, no controllers or responders are configured.
Configuring TWAMP
You can configure low-scale (150 sessions) TWAMP in an ETX-2 device, as well
as high-scale (3,000 sessions) TWAMP in the PMC of an ETX205A device.
11-84 TWAMP ETX-2

To configure TWAMP in an ETX-2 device, perform the following steps:

1. In the responder device:
a. Configure SVI port of type TWAMP (relevant for ETX-2 TWAMP; not in
PMC TWAMP in ETX205A), router interface, and flows.
b. Configure relevant SNTP server(s).
c. Configure and activate TWAMP responder and relevant test session(s).
2. In the controller device:
a. Configure SVI port of type TWAMP (relevant for ETX-2 TWAMP; not in
PMC TWAMP in ETX205A), router interface, and flows.
b. Configure relevant SNTP server(s).
c. Configure TWAMP profile(s).
d. Configure and activate TWAMP controller, relevant peers, and test
sessions.
The TWAMP controller and responder can reside over the same router interface
(configured with the same IP address). Over the x86 platform, the TWAMP
controller and responder can be on the same subnet, but cannot share the same
IP address (cannot coexist on the same router interface). TWAMP controller
resides on the x86 card, and TWAMP responder resides on the ETX-2 card.
The TWAMP controller/responder is defined to have IP connectivity when the
following conditions are met:
• Controller/responder local IP address is configured.
• Associated router interface is configured and administratively enabled.
• Controller/responder is bound to a port (if TWAMP mode is layer-2 E-Line).
• Related SVI and flows are configured (TWAMP in ETX-2)
• Related flows are configured (TWAMP in PMC of ETX205A)
Configuring Controllers
 To configure a TWAMP Light controller of an ETX-2 device:
1. Navigate to configure oam twamp.
The config>oam>twamp# prompt is displayed.
2. Enter controller <name> [<number>] [light] [l2-probe]
Note The parameter l2-probe specifies that the controller is working in mode Layer-2
E-Line service (see Functional Description).
The config>oam>twamp>controller(<name>/light)# prompt is displayed.

3. Enter all necessary commands according to the tasks listed in the table
below.
 To configure a TWAMP controller in PMC (relevant for ETX205A with PMC):
2. The config>oam>twamp# prompt is displayed.
3. Enter controller <name> [<number>
ETX-2 TWAMP 11-85

4. The config>oam>twamp>controller(<name># prompt is displayed.

below.
Binding controller to a port bind ethernet <port-index> Can bind controller to a port, only if
bind logical-mac <port-number> controller is in layer-2 probe mode.
bind pcs <port-number> Typing no bind deletes definition of
TWAMP ingress and egress port.
Note: It is only possible to bind a PMC
responder to an Ethernet port
(relevant for PMC in ETX205A).
Configuring controller local IP local-ip-address <ip-address> Possible values:

address 0 (default) – no IP address
IPv4 or IPv6 network address
Defining peer entity peer <ip-address> twamp-light | twamp (Full TWAMP, which includes
(corresponding to responder), icmp-echo | twamp | udp-echo TWAMP Light and TWAMP control)
to run TWAMP test sessions and udp-echo options are only
relevant for configuration of PMC in
ETX205A.
See Running Test Sessions Via
Controller Peers.
Associating controller with a router-entity <number> The parameter <number> is the

router that contains a suitable router number, in which a router
router interface interface must be configured with the
same IP address as local-ip-address.
Possible values:
0 (default) – no router entity
1-Maximum number of router entities
Associating controller with vlan-tag vlan <vlan> [p-bit <p-bit>] Can associate controller with VLAN
VLAN [inner-vlan <inner-vlan>] only if controller is in layer-2 probe
[inner-p-bit <inner-p-bit>] mode.
Possible values for vlan, inner-vlan:
0-4095, 0xFFFFFFFF (i.e. not
applicable)
Possible values for p-bit, inner p-bit:
0-7
Typing no vlan deletes VLANs for L2
service definition in L2 probe mode.
Note: This parameter is not relevant
for configuration of PMC in ETX205A.
Administratively enabling or no shutdown Type shutdown to administratively

disabling the controller shutdown disable the controller.
You should enable the controller only
after the responder has been
configured and enabled.
11-86 TWAMP ETX-2

Viewing controller status show status
Defining the TCP port number tcp-port Possible values: 862 (default)
for the TWAMP control session 1024–65535
Note: This parameter is available only
for ETX205A with PMC when the
peer test session is TWAMP.
Running Test Sessions Via Controller Peers

On an ETX-2 device, you can configure up to 150 test sessions of TWAMP Light
(default) and/or ICMP Echo protocols on each peer of a controller.
On the PMC of an ETX205A device, you can configure up to 3,000 test sessions
of TWAMP Light, Full TWAMP, ICMP Echo, and/or UDP Echo on each peer of a
controller.
This section describes how to define the peer entity for a group of TWAMP test
sessions.
Note On the PMC, before activating a TWAMP session (RTT or RADM), verify that the
NTP client on board has moved into LOCKED state.
 To configure TWAMP test sessions in ETX-2:

1. Navigate to configure oam twamp controller <name> [<number>] light
[l2-probe] peer <ip-address> [twamp-light | icmp-echo].
The config>oam>twamp>controller (<name>/light)> peer(<ip-address>)
[twamp-light | icmp-echo]# prompt is displayed.
below.
 To configure TWAMP test sessions in PMC (relevant for ETX205A with PMC):
1. Navigate to configure oam twamp controller <name> [<number>] peer
<ip-address> [twamp-light | icmp-echo | twamp | udp-echo].
The config>oam>twamp>controller (<name>)>peer(<ip-address>
twamp-light [twamp-light | icmp-echo | twamp | udp-echo]# prompt is
displayed.
below.
Activating all configured test activate duration <minutes> The tests run for the specified amount
sessions in one-time mode of time.
Type no activate to deactivate the
one-time (non-continuous) command.
Possible values for minutes: 1-10080
ETX-2 TWAMP 11-87

Activating all configured test activate continuous The tests run until they are stopped.
sessions in continuous mode Type no activate to deactivate the
continuous command.
Defining the type of calculation-mode { round-trip | one-way | round-trip: TWAMP controller peer
calculation for the TWAMP one-way-radm}} calculates standard TWAMP metrics
metrics and partial one-way metrics:
• Two-way metrics – availability, loss,
delay, PDV (packet delay variation),
IPDV (inter-packet delay variation)
• Partial one-way metrics – IPDV,
duplicate packets, reordered
packets, fragmented packets (no
one-way delay or PDV metrics)
• One-way loss and availability
one-way: TWAMP controller peer
calculates one-way metrics:
• One-way metrics – delay, PDV,
IPDV, duplicate packets, reordered
packets, fragmented packets
• One-way loss and availability
one-way-radm: For configuration of
PMC on ETX205A. Same as enabled
KPI one-way calculation when
responder and/or controller are not
ToD locked to an external reference,
such as NTP.
The TWAMP controller peer calculates
responder agnostic one-way metrics.
11-88 TWAMP ETX-2

Notes:
• This parameter is masked when
using ICMP Echo protocol, as its
value is always round-trip (the
default).
• This parameter can be changed
only if there is no active test
session.
• You can set one-way mode only if
both the controller and responder
are ToD locked.
• One-way loss and availability is
available only if responder is
configured to transmit an
independent sequence number
(tx-seq-num enabled), and
controller is configured accordingly
(responder-seq-num enabled).
• One-way delay and PDV metrics are
available only if tx-extended-info
has been enabled in responder, and
it sent indication that its ToD (Time
of Day) is synchronized; the metrics
are accurate only if the controller
ToD is also synchronized.
• The fragmented packet count in
the forward direction (controller to
responder) is available only if tx-
extended-info has been enabled in
the responder, and it sent
indication of fragmentation.
Specifying whether the responder-seq-num Notes:

responder transmits an no responder-seq-num • The controller calculates one-way
independent sequence loss and availability only if this is
number enabled.
• The corresponding responder must
be configured to transmit the
responder sequence number (via
command tx-seq-num).
• This parameter is masked when
using ICMP Echo protocol, as its
value is always off (the default).
ETX-2 TWAMP 11-89

Defining the TCP port tcp-port Possible values: 862 (default)

number for the TWAMP 1024–65535
control session Note: This parameter is available only
for configuration of PMC peer with
TWAMP test session in ETX205A with
PMC.
Configuring test session test-session <number> The UDP and DSCP can be used to
[name <name-string>] distinguish between test sessions.
[udp-port <udp-port-number>] UDP port number: 1–65535
[test-profile <profile-name>]
Test profile name: Up to 32 characters
[dscp <dscp-number>]
DSCP number: 0–63 (default: 63)
Notes:
• The udp-port parameter is masked
when using the ICMP Echo protocol.
• The udp-port parameter is optional,
when onfiguring PMC peer with
TWAMP test session in ETX205A
with PMC.
Viewing test report show report <name> all See Viewing TWAMP Reports.
show report <name> current
show report <name> interval
<interval-num>
Viewing summary of test show summary-report See Viewing TWAMP Reports.

reports
Viewing test status show status See Viewing TWAMP Status.
Configuring Test Profiles

You can configure test profiles to associate with a test session.
 To configure TWAMP test profiles:
2. To configure a test profile, enter:
profile <name> [<number>]
The config>oam>twamp>profile(<name>) prompt# is displayed.
Defining delay threshold in delay-threshold <μs>

microseconds
11-90 TWAMP ETX-2

Configuring delay variation delay-variation-event-type {pdv | ipdv} pdv – Packet delay variation metric
event type to define whether ipdv – Inter-packet delay variation
the PDV or IPDV metric is metric
used for the delay threshold
See RFC 5481 for details on these
metrics.
Defining delay variation delay-variation-threshold <μs>

threshold in microseconds
Defining test packet loss loss-timeout <msec>

timeout in microseconds
Defining test session loss- loss-ratio-threshold <ppm> This parameter is available only for
ratio-threshold in ppm configuration of PMC in ETX205A with
(packet per million) PMC.
Possible values: 1000–10000 ppm
Default: 1000 ppm
Defining test packet payload payload-length <bytes> Possible values: 37–1472

length in bytes
Defining test profile packet transmit-rate <pps> Note: In layer-2 probe mode, 150 pps
transmit rate in PPS is possible only if the test packet
payload length is not greater than 170
bytes.
Configuring Responders
This section describes how to create a TWAMP responder entity.
 To configure a TWAMP Light responder of an ETX-2 device:
2. To configure the TWAMP Light responder, enter:
responder <name> [<number>] [light] [l2-probe]
Note The parameter l2-probe specifies that the responder is working in mode Layer-2
E-Line service (see Functional Description).
The config>oam>twamp>responder(<name>/light)# prompt is displayed.

below.
 To configure a TWAMP responder in PMC (relevant for ETX205A with PMC):
2. To configure the TWAMP responder, enter:
responder <name> [<number>
The config>oam>twamp>responder(<name># prompt is displayed.
ETX-2 TWAMP 11-91

below.
Binding responder to a port bind ethernet <port-index> Can bind responder to a port, only if
bind logical-mac <port-number> responder is in layer-2 probe mode.
bind pcs <port-number> Typing no bind deletes definition of
TWAMP ingress and egress port.
Note: It is only possible to bind a PMC
responder to an Ethernet port
(relevant for ETX205A with PMC).
Defining whether to provide tx-extended-info

indication of fragmentation no tx-extended-info
in forward path, and status
of ToD (Time Of Day)
synchronization
Configuring responder local local-ip-address <ip-address> Possible values:

IP address 0 (default) – no IP address
IPv4 or IPv6 network address
Associating responder with a router-entity <number> The parameter <number> is the router
router that contains a number, in which a router interface
suitable router interface must be configured with the same IP
address as local-ip-address.
Possible values:
0 (default) – no router entity
1-Maximum number of router entities
Associating responder with a test-session <number> Typing no test-session <number>

test session [name <name-string>] [name <name-string>] deletes the test
[udp-port <udp-port-number>] session entity.
Notes:
• For TWAMP Light only
• udp-port is masked if responder
IPPM type is TWAMP (relevant for
PMC configuration in ETX205A with
PMC).
Defining whether responder tx-seq-num Notes:

transmits an independent no tx-seq-num • The responder independent
sequence number, rather sequence number can be used by
than copying the received the controller to calculate one-way
sequence number into the loss and availability.
transmitted packet
• The corresponding controller must
be configured to indicate that the
responder sequence number is
being transmitted (via command
responder-seq-num).
11-92 TWAMP ETX-2

Associating responder with vlan-tag vlan <vlan> [p-bit <p-bit>] Can associate responder with VLAN
VLAN [inner-vlan <inner-vlan>] only if responder is in layer-2 probe
[inner-p-bit <inner-p-bit>] mode.
Possible values for vlan, inner-vlan:
0-4095
Possible values for p-bit, inner p-bit: 0-
7
Typing no vlan deletes VLANs for L2
service definition in L2 probe mode.
The p-bit in the transmitted frame can
be either configured (fixed, default
option) or copied from received frame.
Note: This parameter is not relevant
for configuration of PMC in ETX205A.

disabling the responder shutdown disable the responder.
Defining TCP port number for tcp-port Relevant for PMC configuration in
the TWAMP control session. ETX205A.
Possible values: 862 (default)
1024–65535
Defining TWAMP test session reflector-timeout Relevant for PMC configuration in

inactivity timeout no reflector-timeout ETX205A.
Possible values: 0, 60–3600 seconds
Default: 900
Defining TWAMP control server-timeout Relevant for PMC configuration in

session inactivity timer no server-timeout ETX205A.
Possible values: 0, 60–3600 seconds
Default: 900
Viewing responder status show status See Viewing TWAMP Status.
Viewing TWAMP Status

You can view the status of the controller, responder, or peer test sessions, in
any device, as well as in the PMC of ETX205A with PMC, using the show status
command in the following levels.
Controller status show status in level config oam twamp controller
Responder status show status in level config oam twamp responder
Peer test sessions show status in level config oam twamp controller peer
status
ETX-2 TWAMP 11-93

Viewing TWAMP Reports

After you configure round-trip or one-way metrics calculation for each peer via
command calculation-mode (see Running Test Sessions Via Controller Peers) you
can generate the TWAMP report.
The TWAMP controller calculates performance measurement metrics according to
the received test packets for each peer and its active test sessions. The metrics
are recalculated every minute. In the TWAMP report, you can view the metrics
for the current interval, selected interval, or all intervals. You can also view the
metrics via the RADview Performance Management portal if TWAMP PM
collection is enabled (see the Performance Management section for details).
 To view a summary report of all peer test sessions:

1. Navigate to configure oam twamp controller peer.
The config>oam>twamp>controller>peer# prompt is displayed.
2. Type show summary-report.
 To view a report of all intervals in a specific peer test session:

2. Type show report <name> all.
 To view a report of the current interval in a specific peer test session:

2. Type show report <name> current.
 To view a report of a specific interval in a specific peer test session:

2. Type show report <name> interval <interval-num>.
The following table lists the metrics that are displayed in the TWAMP reports,
subject to the restrictions specified above for the calculation modes. See
Example – Viewing TWAMP Reports for examples of TWAMP reports.
Table 11-10. TWAMP Report Metrics
Counter Description
Tx Packets Fwd Number of packets transmitted in forward direction (controller to responder)
Tx Packets Back Number of packets transmitted in backward direction (responder to controller)
Loss Packets Fwd Number of packets lost in forward direction, calculated by Tx Packets Fwd –
Rx valid count
Loss Packets Back Number of packets lost in backward direction, calculated by Tx Packets Back –
Rx valid count
11-94 TWAMP ETX-2

Counter Description
Loss Ratio Fwd Loss Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Loss Ratio Back Loss Packets Back divided by Tx Packets Back, converted to a percentage
Availability Count Fwd (sec) Number of available seconds in forward direction. A (forward) minute is declared
as unavailable if it has more than 75% packet loss in forward direction,
therefore it is available if packet loss in forward direction is 25% or less. When a
minute is declared unavailable, the delay, delay variation, loss measurements,
and their derived metrics are ignored for that minute.
Availability Count Back (sec) Number of available seconds in backward direction. A (backward) minute is
declared as unavailable if it has more than 75% packet loss in backward
direction therefore it is available if packet loss in backward direction is 25% or
less. When a minute is declared unavailable, the delay, delay variation, loss
measurements, and their derived metrics are ignored for that minute.
Duplicate Packets Fwd Number of duplicate packets in forward direction. A packet is considered
duplicate (forward) if its controller sequence number or controller Tx timestamp
matches that of a previously received packet in forward direction.
Duplicate Packets Back Number of duplicate packets in backward direction. A packet is considered
duplicate (backward) if its responder Tx timestamp matches that of a previously
received packet in backward direction.
Duplicate Ratio Fwd Duplicate Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Duplicate Ratio Back Duplicate Packets Back divided by Tx Packets Back, converted to a percentage
Reordered Packets Fwd Number of reordered packets in forward direction. A packet is considered
reordered (forward) if its controller sequence number or controller Tx timestamp
is smaller than that of a previously received packet in forward direction.
Reordered Packets Back Number of reordered packets in backward direction. A packet is considered
reordered (backward) if its responder sequence number is smaller than that of a
previously received packet in backward direction.
Reordered Ratio Fwd Reordered Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Reordered Ratio Back Reordered Packets Back divided by Tx Packets Back, converted to a percentage
Fragmented Packets Fwd Number of fragmented packets in forward direction. When the TWAMP
responder receives a fragmented packet, when it reflects it to the controller, the
responder sends indication of fragmentation, if tx-extended-info was enabled.
When this indication is received, the controller increments the Fragmented
Packets Fwd counter.
Fragmented Packets Back Number of fragmented packets in backward direction. When the TWAMP
controller recognizes a fragmented packet, it increments the Fragmented
Packets Back counter.
Delay-Fwd Threshold Crossing Number of packets in forward direction with delay larger than the delay
Count threshold configured for the corresponding test profile
Delay-Back Threshold Number of packets in backward direction with delay larger than the delay
Crossing Count threshold configured for the corresponding test profile
Delay-Fwd Min (ms) Minimum of packet delay values in forward direction
Delay-Fwd Max (ms) Maximum of packet delay values in forward direction
ETX-2 TWAMP 11-95

Counter Description
Delay-Fwd Average (ms) Average of packet delay values in forward direction
Delay-Back Min (ms) Minimum of packet delay values in backward direction
Delay-Back Max (ms) Maximum of packet delay values in backward direction
Delay-Back Average (ms) Average of packet delay values in backward direction
PDV-Fwd Max (ms) Maximum of PDV (Packet Delay Variation) values in forward direction. Packet
Delay Variation is calculated according to ITU-T Y.1540, by subtracting the
minimum delay from the 99.9% percentile of the delay values
PDV-Fwd Average (ms) Average of PDV (Packet Delay Variation) values in forward direction, calculated
by subtracting Delay-Fwd Min from Delay-Fwd Average
PDV-Back Max (ms) Maximum of PDV (Packet Delay Variation) values in backward direction
PDV-Back Average (ms) Average of PDV (Packet Delay Variation) values in backward direction
IPDV-Fwd Max (ms) Maximum of IPDV (Inter Packet Delay Variation) values in forward direction. Inter
Packet Delay Variation is calculated according to RFC 5481, from the variations
of the delays between valid packets.
IPDV-Fwd Average (ms) Average of IPDV (Inter Packet Delay Variation) values in forward direction
IPDV-Back Max (ms) Maximum of IPDV (Inter Packet Delay Variation) values in backward direction
IPDV-Back Average (ms) Average of IPDV (Inter Packet Delay Variation) values in backward direction
Examples
Example – Configuring TWAMP in Layer-2 E-Line Service Mode

This example illustrates configuring TWAMP in mode Layer-2 E-Line service:
• Controller is ETX203AX or ETX205A with IP address = 11.11.11.1
• Responder is ETX203AX or ETX205A with IP address = 11.11.11.2
 To configure the responder:

• Router: Associate Interface 2 with SVI 2.
• Flows between Ethernet ports 1 and 3:
 VLAN 100
 No policer
• Test session:
 UDP port 999
exit all
#*********Configure SVI for TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit
11-96 TWAMP ETX-2


flows
match vlan 100
exit
#********* Configure flows between ETH 1 & 3

flow E1toE3
classifier v100
no policer
no shutdown
exit
flow E3toE1
classifier v100
no policer
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for TWAMP

router 1
interface 2
address 11.11.11.2/24
address 11:11:11::2/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP responder

oam
twamp
responder 1 light l2-prob
bind ethernet 1
vlan-tag vlan 100
router-entity 1
local-ip-address 11.11.11.2
test-session 1 udp-port 999
tx-extended-info
tx-seq-num
no shutdown
exit all
save
 To configure the controller:

• Flows between Ethernet ports 1 and 3:
 VLAN 100
ETX-2 TWAMP 11-97

 No policer
• Test session:
 Profile with payload length 150, and loss timeout 1 second
 UDP port 999
 DSCP 0
exit all
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit

flow E1toE3
classifier v100
no policer
no shutdown
exit
flow E3toE1
classifier v100
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.11.1/24
address 11:11:11::1/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile

oam
twamp
profile twp1
payload-length 150
loss-timeout 1000000
11-98 TWAMP ETX-2

exit
#*********Configure TWAMP controller

controller 1 light l2-probe
bind ethernet 1
vlan-tag vlan 100
router-entity 1
peer 11.11.11.2
test-session 1 name twamp1 udp-port 999 test-profile twp1 dscp 0
calculation-mode round-trip
responder-seq-num
exit
no shutdown
exit all
save
Example – Configuring TWAMP in Layer-2 E-LAN Service Mode

This example illustrates configuring TWAMP in mode Layer-2 E-LAN service:
• Controller is ETX203AX or ETX205A with IP address = 11.11.101.6
• Responder is ETX220A with IP address = 11.11.101.116

• Bridge – Activate ports 1, 2, and 3; associate VLAN 1.
• Router – Associate Interface 2 with SVI 2.
• Flows between Ethernet port 1/1 and bridge port 1, and Ethernet port 4/1
and bridge port 2:
 Match VLAN 1
 No policer
• Flows between bridge port 3 and SVI 2:
 Bridge port to SVI – Match VLAN 1, and pop VLAN.
 SVI to bridge port – Match all traffic, and push VLAN 1.
 No policer
• Test session:
 UDP port 900
exit all
configure
port svi 2 twamp
no shutdown
exit
exit
#*********Configure bridge ports

configure bridge 1
port 1 no shutdown
port 2 no shutdown
ETX-2 TWAMP 11-99

port 3 no shutdown
vlan 1
exit all
#*********Configure classifier for VLAN 1

configure
flows
match vlan 1
exit
#*********Configure flows between Ethernet port 1/1 and bridge port 1

flow E1_1toBP1
classifier v1
no policer
no shutdown
exit
flow BP1to E1_1

classifier v1
egress-port ethernet 1/1 block 0/1
no policer
no shutdown
exit
#*********Configure flows between Ethernet port 4/1 and bridge port 2

flow E4_1toBP2
classifier v1
no policer
no shutdown
exit
flow BP2toE4_1
classifier v1
egress-port ethernet 4/1 block 0/1
no policer
no shutdown
exit
#*********Configure flows between bridge port 3 and SVI 2

flow BP3toSVI2
classifier v1
egress-port svi 2
vlan-tag pop vlan
no policer
no shutdown
exit
flow SVI2toBP3
11-100 TWAMP ETX-2

classifier all
ingress-port svi 2
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.101.116/24
address 11:11:101::116/64
bind svi 2
no shutdown
exit
exit

oam
twamp
responder 1 light
router-entity 1
test-session 1 udp-port 900
tx-extended-info
tx-seq-num
no shutdown
exit all
save

• Bridge – Activate ports 1, 2, and 3; associate VLAN 1.
• Router – Associate Interface 2 with SVI 2.
• Flows between Ethernet port 1 and bridge port 1, and Ethernet port 3 and
bridge port 2:
 Match VLAN 1
 No policer
• Flows between bridge port 3 and SVI 2:
 Bridge port to SVI: Match VLAN 1, and pop VLAN.
 SVI to bridge port: Match all traffic, and push VLAN 1.
 No policer
• Test session:
 Profile with default values
 UDP port 900
 DSCP 22
exit all
ETX-2 TWAMP 11-101


configure
port svi 2 twamp
no shutdown
exit
exit
#*********Configure bridge ports

configure bridge 1
port 1 no shutdown
port 2 no shutdown
port 3 no shutdown
vlan 1
exit all
#*********Configure classifier for VLAN 1

configure
flows
match vlan 1
exit
#*********Configure flows between Ethernet port 1 and bridge port 1

flow E1toBP1
classifier v1
no policer
no shutdown
exit
flow BP1to E1
classifier v1
no policer
no shutdown
exit
#*********Configure flows between Ethernet port 3 and bridge port 2

flow E3toBP2
classifier v1
no policer
no shutdown
exit
flow BP2to E3
classifier v1
no policer
no shutdown
exit
11-102 TWAMP ETX-2

#*********Configure flows between bridge port 3 and SVI 2

flow BP3toSVI2
classifier v1
egress-port svi 2
vlan-tag pop vlan
no policer
no shutdown
exit
flow SVI2toBP3
classifier all
ingress-port svi 2
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.101.6/24
address 11:11:101::6/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile with default values

oam
twamp
profile twp1
exit

controller 1 light
router-entity 1
peer 11.11.101.116
calculation-mode round-trip
responder-seq-num
exit
no shutdown
exit all
save
Example – Configuring TWAMP in Layer-3 Mode

This example illustrates configuring TWAMP in Layer-3 mode:
• Controller is ETX203AX or ETX205A with IP address=12.12.12.1
• Responder is ETX203AX or ETX205A with IP address=22.22.22.1
ETX-2 TWAMP 11-103

Note This example assumes for the routers in the controller and responder:
• In the controller, the next hop to reach the 22.22.22.0/24 subnet is
12.12.12.2
• In the responder, the next hop to reach the 12.12.12.0/24 subnet is
22.22.22.2

• Flows between Ethernet port 1 and SVI 2:
 Untagged traffic from Ethernet port 1 to SVI 2
 Untagged traffic from SVI 2 to Ethernet port 1
 No policer
• Test session:
 UDP port 999
exit all
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifier for untagged traffic

flows
match untagged
exit
#********* Configure flows between Eth port 1 & SVI 2

flow E1toSVI2
classifier untagged
no policer
no shutdown
exit
flow SVI2toE1
classifier untagged
ingress-port svi 2
no policer
no shutdown
exit
exit
#*********Configure router with interface 2 for TWAMP

router 1
interface 2
11-104 TWAMP ETX-2

address 22.22.22.1/24
address 22:22:22::1/64
bind svi 2
no shutdown
exit
exit

oam
twamp
responder 1 light
router-entity 1
test-session 1 name "twamp1" udp-port 999
tx-extended-info
tx-seq-num
no shutdown
exit all
save

 Untagged traffic from Ethernet port 1 to SVI 2
 Untagged traffic from SVI 2 to Ethernet port 1
 No policer
• Test session:
 Profile with payload length 150, and loss timeout 1 second
 UDP port 999
 DSCP 0
exit all
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifier for untagged traffic

flows
match untagged
exit

flow E1toSVI2
classifier untagged
ETX-2 TWAMP 11-105


no policer
no shutdown
exit
flow SVI2toE1
classifier untagged
ingress-port svi 2
no policer
no shutdown
exit
exit
#*********Configure router with interface 2 for TWAMP

router 1
interface 2
address 12.12.12.1/24
address 12:12:12::1/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile

oam
twamp
profile twp1
payload-length 150
loss-timeout 1000000
exit

controller 1 light
router-entity 1
peer 22.22.22.1
calculation-mode one-way
responder-seq-num
exit
no shutdown
exit all
save
Example – Configuring Management for TWAMP in PMC

(relevant for ETX205A with PMC)
This example illustrates configuring the ETX-2 NID and x86 card for management,
according to the flows shown below.
11-106 TWAMP ETX-2

x86
Eth1 Eth2
Internal Internal
Port 6 Port 5 ETX-205A
Push/Pop
Bridge 1 SVI 1
VLAN 4094
Push/Pop
VLAN 4094
NNI Port 1
ETX-205A
MNG Traffic
VLAN 4094
Figure 11-23. Management for TWAMP Generator in PMC
 To configure management in ETX-2:

• SVI port 1, bridge
• Management VLAN 4094
• Flows:
 Flows between bridge port and Ethernet port 1, pushing/popping
VLAN 4094
 Flows between bridge port and internal Ethernet port 6, with criterion
VLAN 4094
 Flows between bridge port and SVI port 1, pushing/popping VLAN 4094
 Router interface with IP address 192.168.205.5, bound to SVI port 1
#********* Configure SVI *********
exit all
configure port
svi 1
no shutdown
exit all
********* Configure bridge and VLAN*********

configure bridge 1
port 1 no shutdown
port 6 no shutdown
port 9 no shutdown
vlan 4094
ETX-2 TWAMP 11-107

exit all
#********* Configure flows *********

configure flows
flow eth1_bp1_untagged
classifier untagged
no policer
no shutdown
exit
flow int_eth6_bp6_v4094
classifier v4094
ingress-port int-ethernet 6
no policer
no shutdown
exit
flow svi1_bp9_all
classifier all
ingress-port svi 1
no policer
reverse-direction
no shutdown
exit
#********* Configure router *********

configure router 1
interface 1
address 192.168.205.5/24
bind svi 1
no shutdown
exit all
#********* Save configuration *********

save
 To configure in x86 card:

 Router interface with IP address 192.168.205.6, bound to Ethernet
port 1 and VLAN 4094
11-108 TWAMP ETX-2

Notes • The ETX-2 internal Ethernet port 6 is connected to Ethernet port 1 on the
x.86 card.
• Configure the x86 card by accessing the x86 remote terminal via command
configure chassis ve-module remote-terminal (refer to Remote Terminal in
the Management and Security chapter).
#********* Configure router *********

exit all
configure router 1
interface 1
address 192.168.205.6/24
bind ethernet 1
vlan 4094
no shutdown
exit all

save
Example – Configuring TWAMP in PMC (relevant for ETX205A

with PMC)
This example illustrates configuring TWAMP in ETX-2 and the x86 card.
 To configure TWAMP in the x86 card:

• Router interfaces:
 Router interface 1: Management, IP address 172.18.141.37, VLAN 4094
 Router interface 2: TWAMP, IP address 11.11.101.6, bound to Ethernet
port 1, VLAN 101
• TWAMP controller:
 IP address 11.11.101.6
 Peer IP address 33.33.116.6
 Router interface 2
• SNMPv3 target and traps
• NTP servers
#********* Configure router interface for management *********
exit all
configure router 1
interface 1
bind ethernet 1
vlan 4094
address 172.18.141.37/24
no shutdown
exit
#********* Configure router interface for TWAMP *********

interface 2
address 11.11.101.6/24
ETX-2 TWAMP 11-109

mtu 2000
bind ethernet 1
vlan 101
no shutdown
exit
exit all
#********* Configure TWAMP controller *********

configure oam twamp profile 1
exit all
configure oam twamp controller 1
router-entity 1
no shutdown
peer 33.33.116.6 twamp-light
calculation-mode one-way
responder-seq-num
test-session 1 name 1 udp-port 50000 test-profile 1 dscp 1
exit all
#********* Configure control port *********

configure terminal
timeout forever
exit all
#*********Configure SNMPv3 target and traps

configure
management
access snmp
snmp
target MyPC
target-params "tp1"
no shutdown
tag-list "unmasked"
exit
target-params tp1
version usm
security name "initial" level no-auth-no-priv
no shutdown
exit all
#********* Configure NTP servers *********

zone utc +03:00
ntp server 1
address 172.17.171.141
prefer
no shutdown
exit
server 2
address 172.17.171.142
no shutdown
exit
11-110 TWAMP ETX-2

server 3
address 172.17.172.65
no shutdown
exit all

save
 To configure flows in ETX-2:

• Data VLAN 101
• Flows for data
#********* Configure flows *********
exit all
configure flows
flow Eth1_Int6_101
classifier v101
egress-port int-ethernet 6 queue 0 block 0/1
no policer
no shutdown
exit
flow Int6_Eth1_101
classifier v101
ingress-port int-ethernet 6
no policer
no shutdown
exit all

save
Example – Viewing TWAMP Status
 To view controller status:

ETX-2>config>oam>twamp>controller(1/light)# show status
IPPM Type : TWAMP Light
Router Entity : 1
Router Interface : 2
Router Interface oper status : UP
Controller Status : In Progress
 To view responder status:

ETX-2>config>oam>twamp>responder(1/light)# show status
Router Entity : 1
Responder Status : Ready
ETX-2 TWAMP 11-111

Responder Test Name UDP Port Tx Packets Rx Packets

---------------------------------------------------------------
TwampResponderSession 900 1107 1107
 To view peer test status for TWAMP Light continuous test:

ETX-2>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show status
Activation Mode : Continuous
Start Time : 2013-11-24 14:13:28
Controller Test Name Peer UDP Status Tx Packets Rx Packets

-----------------------------------------------------------------------------
twamp1 900 In Progress 600 599
 To view peer test status for TWAMP Light non-continuous test:

ETX-2>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show status
IPPM type : TWAMP Light
Activation mode : non-continuous
Calculation Mode : round-trip
Start time : 2013-05-30 15:29:45
Duration [ min ] : 120
Elapsed Time [ min ] : 20
Controller test name Peer UDP Status Tx packets Rx packets

-----------------------------------------------------------------------------
XXXX 30000 In progress 2000 1900
YYYY 35000 Ready 2000 1900
ABCD 40000 In progress 42000000 600000
 To view peer test status for ICMP Echo continuous test:

ETX-2>config>oam>twamp>controller(1)>peer(33.33.116.6)# show status
IPPM type : ICMP Echo
Activation mode : continuous
Start time : 2013-05-30 15:29:45
Controller test name Status Tx packets Rx packets

-----------------------------------------------------------------------------
XXXX In progress 2000 1900
YYYY Ready 2000 1900
ABCD In progress 42000000 600000
Example – Viewing TWAMP Reports
 To view a TWAMP Light test summary report (one-way calculation mode):

ETX-2>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show summary-report
Controller IP Address : 11.11.101.6
Responder IP Address : 33.33.116.6
Activation Mode : Off
Calculation Mode : one-way
TOD status controller/peer : Sync / Out of sync
Start / Elapsed / Duration (min) : 2014-06-01 10:36:41 / 1 / 1
Controller Test Name Dir IP Size Loss Delay PDV IPDV Result
11-112 TWAMP ETX-2

DSCP
Ratio Max Max Max
(bytes) (ms) (ms) (ms)
----------------------------------------------------------------------------
1 fwd 22 1280 2.0E-2 0.658 0.065 0.048 Fail
1 bck 22 1280 0 0.263 0.014 0.011 Pass
 To view a TWAMP Light test summary report (round-trip calculation mode):

ETX-2>config>oam>twamp>controller(2/light)>peer(33.33.117.6)# show summary-report
Controller IP Address : 11.11.102.6
Responder IP Address : 33.33.117.6
Activation Mode : Continuous
Calculation Mode : round-trip
Start Time / Elapsed Time (sec) : 2014-06-02 00:27:30 / 240
Controller Test Name IP Size Loss Delay PDV IPDV Result

DSCP Ratio Max Max Max
(bytes) (ms) (ms) (ms)
-----------------------------------------------------------------------------
6 6 512 6.9E-1 179.292 3.415 2.312 NA
7 7 512 6.7E-1 181.170 5.494 3.888 NA
8 8 512 6.9E-1 183.131 5.817 4.545 NA
9 9 512 6.7E-1 185.145 7.609 6.323 NA
10 10 512 6.7E-1 187.108 10.949 9.789 NA
 To view a TWAMP Light test report:

ETX-2>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show report 1 all
Test Name : 1
Controller IP Address : 11.11.101.6 / 56568
Responder IP Address : 33.33.116.6 / 50000
IP DSCP : 22
Payload Length (bytes) : 256
Calculation Mode : one-way
Start Time : 2014-06-01 14:13:28
Test Interval : Current

Time Stamp : 2014-06-01 16:14:53
TOD Sync Count (sec) : 0
Tx Packets Fwd / Back : 5400 5360

Loss Packets Fwd / Back : 40 17
Loss Ratio Fwd / Back : 7.4E-3 3.2E-3
Availability Count Fwd / Back (sec) : 540 540
Duplicate Packets Fwd / Back : 0 0

Duplicate Ratio Fwd / Back : 0 0
Reordered Packets Fwd / Back : 0 0
Reordered Ratio Fwd / Back : 0 0
Fragmented Packets Fwd / Back : 0 0
Delay-Fwd Threshold Crossing Count : 0

Delay-Back Threshold Crossing Count : 8
Delay-Fwd Min / Max / Average (ms) : 0.530 0.892 0.615
ETX-2 TWAMP 11-113

Delay-Back Min / Max / Average (ms) : 0.226 775.498 0.899

PDV-Fwd Max / Average (ms) : 0.351 0.085
PDV-Back Max / Average (ms) : 377.482 0.673
IPDV-Fwd Max / Average (ms) : 0.306 0.010
IPDV-Back Max / Average (ms) : 775.263 0.293
Loss Result : Pass

Delay Result : Pass
DV Result : Pass
 To view an ICMP Echo test summary report (continuous, round-trip calculation

mode):
ETX-2>config>oam>twamp>controller(1)>peer(234.234.56.100)icmp-echo# show
summary-report
IPPM : ICMP Echo
Controller ip address : 1.1.1.1
Responder ip address : 234.234.56.100
Activation mode : continuous
Start time / Elapsed time [sec] : 2013-05-30 15:29:45 / 500
Controller test name DSCP Size Loss

Delay PDV IPDV Result
[bytes] Ratio
Max Max Max
[ms] [ms] [ms]
--------------------------------------------------------------------------------
AAAAA 02 100 6.5E-5 5.000 1.000 2.000 NA
 To view an ICMP Echo test report (non-countinuous, round trip calculation

mode):
ETX-2>config>oam>twamp>controller(1)>peer(33.33.116.6)icmp-echo# show report
AABBCC current
Test Name : AABBCC

IPPM type : ICMP Echo
Controller ip address : 1.1.1.1
Responder ip address : 234.234.56.100
IP DSCP : 34
Payload length [bytes] : 1500
Start Time : 2013-05-30 15:29:45
-------------------------------------------------------------------------------
Test interval : current
Elapsed time [sec] : 180
Tx packets : 1800
Loss packets : 10
Loss Ratio : 1.2E-3
Availability count [sec] : 180
Duplicate packets : 2
Duplicate Ratio : 1.2E-3
Reordered packets : 3
Reordered Ratio : 1.2E-3
Delay threshold crossing count : 7
Delay min / max / average [ms] : 1.000 2.000 1.500
PDV max / average [ms] : 2.000 1.000
IPDV max / average [ms] : 2.000 1.000
Loss result : fail // for non-continuous
only
11-114 TWAMP ETX-2

Delay result : pass // for non-continuous

only
DV result : pass // for non-continuous
only
Cannot modify; TWAMP Tried modifying the bound Shut down the controller and then
controller is active port definition while controller modify the bound port definition.
was active (status was not
‘shutdown’).
Tried modifying VLAN Shut down the controller and then

definition while controller was modify the VLAN definition
active (status was not
‘shutdown’).
Tried modifying controller’s Shut down the controller and then

router entity number while modify the router entity number.
controller was active (status
was not ‘shutdown’).
Tried modifying local IP Shut down the controller and then

address while controller was modify the local IP address.
‘shutdown’).
Cannot modify; TWAMP Tried modifying the bound Wait for the active test to terminate
controller has active test port definition while controller and then modify the bound port
had an active test. definition.
Tried modifying VLAN Wait for the active test to terminate

definition while controller had and then modify the VLAN definition.
an active test.
Tried modifying controller’s Wait for the active test to terminate

router entity number while and then modify the controller’s router
controller had an active test. entity number.
Tried modifying local IP Wait for the active test to terminate

address while controller had and then modify the local IP address.
an active test.
Cannot delete; TWAMP controller Tried removing the bound port Shut down the controller and then
is active while controller was active remove the bound port.
(status was not ‘shutdown’).
ETX-2 TWAMP 11-115

Tried removing the VLAN Shut down the controller and then
definition while controller was remove the VLAN definition.
‘shutdown’).
Cannot delete; TWAMP controller Tried removing the bound port Wait for the active test to terminate
has active test while controller had an active and then remove the bound port.
test.
Tried removing the VLAN Wait for the active test to terminate
definition while controller had and then remove the VLAN definition.
an active test.
Cannot activate; router entity Tried activating controller Define router entity and local IP
and local ip address must be when router entity and/or local address, and then activate controller.
defined IP address were not defined.
Tried activating responder Define router entity and local IP

when router entity and/or local address, and then activate responder.
IP address were not defined.
Cannot activate; router entity, In l2-probe mode, tried Define router entity, local IP address,
local ip address and port must activating controller when and port, and then activate controller.
be defined router entity, local IP address,
and/or port were not defined.
In l2-probe mode, tried Define router entity, local IP address,

activating responder when and port, and then activate responder.
router entity, local IP address,
and/or port were not defined.
Cannot delete; peer has active Tried deleting peer entity, Wait for active test to terminate, and
test while there was an active test. then delete peer entity.
Cannot create; name already in Tried giving a test session a Give test session a unique name.
use name that already exists under
peer context.
Tried giving a test profile a Give test profile a unique name.

name that already exists under
TWAMP contest.
Tried giving a responder a Give responder a unique name.

TWAMP context.
Tried giving a test session a Give test session a unique name.

responder contest.
Cannot activate; controller not Tried activating peer test Wait for controller to be ready, and
ready sessions when controller then activate peer test sessions.
status was ‘idle’ (not ready).
Cannot activate; peer has active Tried activating peer test Wait for active tests to terminate, and
test sessions while there were then activate peer test sessions.
active tests.
11-116 TWAMP ETX-2

Cannot delete; TWAMP Tried removing active Shut down the responder and then
responder is active responder (status ‘idle’ or delete it.
‘ready’).
Tried deleting the bound port Shut down the responder and then
definition while responder was delete the bound port definition.
active (status ‘idle’ or ‘ready’).
Tried removing VLAN definition Shut down the responderer and then
while responder was active remove the VLAN definition.
(status ‘idle’ or ‘ready’).
Cannot modify; TWAMP Tried modifying the bound Shut down the responder and then
responder is active port definition while responder modify the bound port definition.
was active (status ‘idle’ or
‘ready’).
Tried modifying VLAN Shut down the responder and then

definition while responder was modify the VLAN definition.
active (status ‘idle’ or ‘ready’).
Tried modifying responder’s Shut down the responder and then

router entity number while modify the router entity number.
responder was active (status
‘idle’ or ‘ready’).
Tried modifying responder’s Shut down the responder and then

local IP address while modify the local IP address.
responder was active (status
‘idle’ or ‘ready’).
Tried deleting a test profile

that is in use by a test session.
11.5 Layer-3 Service Activation Test

The Layer-3 service activation test (L3 SAT) provides an out-of-service (intrusive)
IP/UDP test to assess the proper configuration and performance of an IP
transport service prior to customer notification and delivery.
Applicable Products
This feature is applicable to all ETX-2 products, except for capacity differences
between products that are specified where relevant.
Standards
ITU-T Y.1564
ETX-2 Layer-3 Service Activation Test 11-117

Benefits
The Y.1564 testing methodology allows service providers to have a standard way
of measuring the performance of IP transport services. The tests are performed
per multiple traffic streams simultaneously, confirming policing per EVC or
EVC.CoS.
Factory Defaults
By default, there are no L3 SAT entities configured in ETX-2.
When a peer profile is created, it has the following default configuration.
bw-steps 25 50 75 100
configuration-duration 100
performance-duration 120
policing-test policing-test
report-type no-clock-sync
scope configuration performance
udp-port 53248
When a session profile is created, it has the following default configuration.
availability-threshold 9990
delay-variation-threshold 100000
ip-size 256
loss-ratio-threshold 1000
When a peer is created, there is no default configuration.

When a test session is created, it has the following default configuration.
<name> <Not applicable> <name> must be specified when the test

session is created.
session-profile <Not applicable> <profile-name> must be specified when the

test session is created.
bw <Not applicable> <kbps> must be specified when the test

session is created.
dscp 0
11-118 Layer-3 Service Activation Test ETX-2

When a generator is created, it has the following default configuration.
bind <not applicable> This parameter has no default configuration.
local-ip-address <not applicable> This parameter has no default configuration.
router-entity 1
vlan-tag <not applicable> This parameter has no default configuration.
When a responder is created, it has the following default configuration.
bind <not applicable> This parameter has no default configuration.
local-ip-address <not applicable> This parameter has no default configuration.
router-entity 1
udp-port 53248
vlan-tag <not applicable> This parameter has no default configuration.
L3 SAT testing has the following objectives:
• Validate that the IP transport service is correctly configured.
• Validate the quality of the services as delivered to the end user.
L3 SAT tests can be performed over Layer-3 networks, or as a Layer-3 service
over a Layer-2 network.
Test Phases
The methodology has a service configuration test phase followed by a service
performance test phase; the service configuration test is short in order to
prevent wasted time caused by failed service performance tests. The test
flowchart below illustrates the two phases.

Enter test
parameters
Start test
Service Fail Troubleshoot

configuration service
test configuration
Pass
Service
performance
test
Pass
Test completed
Figure 11-24. L3 SAT Test Flowchart
Configuration Test
The configuration test validates that services are configured as intended before
proceeding to the service performance test. The following are performed:
• Preliminary (common for all test sessions):
 Verify connectivity – If the connectivity subtest fails, the configuration
test fails and the L3 SAT to the relevant peer is stopped. Otherwise, the
detected responder type is recorded and shown in the test report.
 Determine the path MTU – If the MTU subtest fails, the configuration
test fails and the L3 SAT to the relevant peer is stopped. Otherwise, the
discovered MTU is recorded and shown in the test report.
Note The preliminary tests are always performed, even if the configuration phase is
not included in the scope of the test.
• Bandwidth subtests (one test session at a time):

 Step load
 Policing
The bandwidth subtests are performed for the packet sizes configured for the
test session. They are performed in increasing order of packet size, one packet

size at a time. The bandwidth subtest is successful if the subtest results are
within the configured Service Acceptance Criteria (SAC) limits.
If a bandwidth subtest fails for a particular packet size, the testing for that
packet size continues and all remaining bandwidth subtests are performed.
If packet sizes larger than the discovered MTU were configured for the test
session, the bandwidth subtest is considered failed for these packet sizes; it is
not performed for packet sizes larger than the MTU.
A test session is declared successful only if the results for all tested packet sizes
are within SAC limits.
Note When the report-type parameter is clock-sync (report includes parameters

requiring synchronization) and the responder type is loop and timestamp, an
additional requirement for a test session to be declared successful is that there
were no out-of-sync seconds during the test.
The configuration test is declared successful if the results for all the test
sessions are successful.
Performance Test
The performance test validates the quality of the services over a
user-configurable period of time, as follows:
• Traffic is generated for all services at the configured bandwidth level.
• For all the test sessions, test packets are sent simultaneously at 100% of
the bandwidth configured per test session.
• Per test session, the duration of the performance test is evenly divided
between the different packet sizes, e.g. per test session, each packet size is
transmitted for an equal amount of time.
The performance test is declared successful if the results are within SAC limits.
Note When the report-type parameter is clock-sync (report includes parameters

requiring synchronization) and the responder type is loop and timestamp, an
additional requirement for the performance test to be declared successful is
that during the test, at least one minute was not excluded due to unavailability
or out-of-sync.
Test Elements
L3 SAT includes the following elements:
Generators Initiate multiple test sessions for multiple responders, send

out the test and OAM frames, receive responses from the
responder(s), process the resulting measurements, and
display test reports. Generators can support mixed
responder types.
Peers Used to run TWAMP test sessions. One or more peers can
be configured per generator with IP address(es)
corresponding to responder(s).
Test Sessions One or more test sessions can be configured per peer.

Responders Receive test and OAM frames from generator, and transmit
responses to generator. Responders can be the following
types:
IP loop – filters incoming traffic by destination IP address,
and loops it back while performing MAC address swap and
IP address swap
UDP loop – filters incoming traffic by destination IP address
and UDP port, and loops it back while performing MAC
address swap, IP address , and UDP port swap
Loop and timestamp – filters incoming traffic by
destination IP address and UDP port and performs IP loop
for loss measurement packets, UDP loop with timestamp
for delay measurement packets
Note
Responders can be ETX-2 devices or third-party devices. Third-party responders
can be only IP loop or UDP loop types. Only ETX-2 can be a loop and timestamp
responder, and only an ETX-2 responder can provide one-way metrics.
Figure 11-25. L3 SAT Generators and Responders
Configuring L3 SAT Entities

To configure L3 SAT, perform the following steps:
1. In the responder device:
a. Configure relevant SVI port, router interface, and flows.
b. Configure and activate L3 SAT responder.
2. In the generator device:
a. Configure relevant SVI port, router interface, and flows.
b. Configure L3 SAT peer and session profile(s).

c. Configure and activate L3 SAT generator and relevant peers and test
sessions.
Configuring Generators
 To configure L3 SAT generators:
1. Navigate to configure test l3sat.
The config>test>l3sat# prompt is displayed.
2. Enter:
generator <name> [l2-probe]
Note The optional parameter l2-probe is used to specify Layer-3 over Layer-2
operation. The default without the parameter is Layer-3 service.
The config>test>l3sat>generator(<name>)# prompt is displayed.

Binding generator to the port bind ethernet <port-index>

over which to test the service, bind logical-mac <port-number>
if the generator is working in bind pcs <port-number>
layer-2 probe mode
Configuring generator IP local-ip-address <ip-address>

address
Defining peer entity peer <ip-address> See Configuring Peers.

(corresponding to responder)
Associating generator with a router-entity <number> The parameter <number> is the

router that contains a suitable router number, in which a router
router interface interface must be configured with the
same IP address as local-ip-address.
Associating generator with vlan-tag <vlan> p-bit fixed <p-bit> • <vlan> – Outer VLAN tag of test
VLAN, if the generator is [inner-vlan <inner-vlan>] packets
working in layer-2 probe mode [inner-p-bit <inner-p-bit>] • <p-bit> – Outer VLAN priority of
vlan-tag <vlan> p-bit marking test packets
<dscp-to-pbit-profile> [inner-vlan • <inner-vlan> – Inner VLAN tag of
<inner-vlan>] [inner-p-bit <inner-p-bit>] test packets
• <inner-p-bit> – Inner VLAN priority
of test packets
• <dscp-to-pbit-profile> – Marking
profile used to mark outer VLAN
priority of test packets

disabling the generator disable the generator.
You should enable the generator only
after at least one responder has been
configured and enabled.
Viewing generator status show status

Configuring Peers
 To configure L3 SAT peers:
1. Navigate to configure test l3sat generator <name>.
The config>test>l3sat>generator(<name>)# prompt is displayed.
2. Enter:
peer <ip-address>
The prompt config>test>l3sat>generator(<name>)> peer(<ip-address>)#
is displayed.
Activating or deactivating the activate You can activate a peer only if

peer test sessions no activate at least one test session has
been configured.
Assigning a peer profile to use peer-profile <profile-name>

for the peer parameters
Assigning a test session test-session <name> session-profile Multiple test sessions can be
<profile-name> bw <kbps> defined in the peer.
[dscp <number>] bw – rate of the test session
traffic in Kbps
dscp – priority value for the
test session traffic
Displaying results and show report <test-name> Available only if peer was
measurements for a specific test activated
Displaying summary of test show summary-report Available only if peer was

results and measurements activated
Displaying the peer status show status
Configuring Peer Profiles

 To configure L3 SAT peer profiles:
2. Enter:
peer-profile <name>
The prompt config>test>l3sat> peer-profile(<name>)# is displayed.

Setting the number of steps and bw-steps <s1-percent> <s1-percent> – transmission

their transmission rate in the bw-steps <s1-percent> <s2-percent> rate, as percentage of
bandwidth subtest configured bandwidth, at the
bw-steps <s1-percent>
first step of the step load
<s2-percent><s3-percent>
subtest (1–100)
bw-steps <s1-percent> <s2-percent>
<s2-percent> – transmission
<s3-percent><s4-percent>
rate, as percentage of
configured bandwidth, at the
second step of the step load
subtest (1–100)
third step of the step load
subtest (1–100)
fourth step of the step load
subtest (1–100)
Note: You can define fewer than
four steps as long as the last
step is 100%.
Defining the duration of the configuration-duration <seconds> Possible values: 60–300 seconds
configuration phase for each
test session
Defining the duration in minutes performance-duration <minutes> Possible values: 45–7200

of the performance phase minutes
Specifying whether to include or policing-test

exclude the traffic policing no policing-test
subtest from the configuration
phase
Defining which parameters are report-type {clock-sync | • clock-sync – Include

included in the test report no-clock-sync} parameters requiring
synchronization.
• no-clock-sync – Do not
include parameters requiring
synchronization.
See Viewing L3 SAT Test Reports
for details on which parameters
are included in the test report.
Setting the scope of the test: scope [configuration] [performance] You can enter the command
configuration test, performance with one or both parameters.
test, or both

Specifying start of the range of udp-port <port> Possible values: 0–65504

UDP ports that are used in the
tests
Configuring Session Profiles

 To configure L3 SAT session profiles:
2. Enter:
session-profile <name>
The prompt config>test>l3sat>session-profile(<name>)# is displayed.
Defining Availability service availability-threshold <availability> Availability is measured in

acceptance criteria hundredths of percent units
(for example, use value 8930 in
order to define 89.3%).
Defining Packet Transfer Delay delay-threshold <μs> Possible values: 0–1000000

service acceptance criteria, in
microseconds
Defining Packet Delay Variation delay-variation-threshold <μs> Possible values: 0–1000000

microseconds
Defining test packet size ip-size [64] [128] [256] [512] [1024] • You can specify up to four
[1280] [1500] [mtu] [custom <size>] packet sizes.
• Range for custom <size>:
52–2094
Defining Packet Loss Ratio loss-ratio-threshold <ppm> Possible values: 0–1000000

ppm (1E-6 units)
Configuring Responders
 To configure L3 SAT responders:
2. Enter:
responder <name> [l2-probe]
Note The optional parameter l2-probe s used to specify Layer-3 over Layer-2
operation. The default without the parameter is Layer-3 service.

The config>test>l3sat>responder(<name>)# prompt is displayed.

Binding responder to the bind ethernet <port-index>

port over which to test the bind logical-mac <port-number>
service, if the responder is bind pcs <port-number>
working in layer-2 probe
mode
Configuring responder IP local-ip-address <ip-address>

address
Associating responder with a router-entity <number> The parameter <number> is the router
router that contains a number, in which a router interface
suitable router interface must be configured with the same IP
address as local-ip-address.
Specifying start of the range udp-port <port> • Possible values: 53248–65520

of UDP ports that are used in
the tests
Associating responder with vlan-tag <vlan> p-bit fixed <p-bit> • <vlan> – Outer VLAN tag of test
VLAN, if the responder is [inner-vlan <inner-vlan>] packets
working in layer-2 probe [inner-p-bit <inner-p-bit>] • <p-bit> – Outer VLAN priority of
mode vlan-tag <vlan> p-bit marking test packets
<dscp-to-pbit-profile> [inner-vlan • <inner-vlan> – Inner VLAN tag of
<inner-vlan>] [inner-p-bit <inner-p-bit>] test packets
• <inner-p-bit> – Inner VLAN priority
of test packets
• <dscp-to-pbit-profile> – Marking
profile used to mark outer VLAN
priority of test packets

disabling the responder disable the responder.
Viewing responder status show status
Viewing L3 SAT Test Status

You can view the status of the test as it is running.
 To display the test status (generator side):

• At the
config>test>l3sat>generator(<generator-name>)>peer(<IP-address>)#
prompt, enter:
show status
ETX-2>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show status
Last Connectivity Sub-test : Passed
Last MTU Sub-test : Not Applicable
Responder Type : Loop & Timestamp

Elapsed Time : 00:00:02

Time Remaining : 00:13:26
Current Phase :
TOD Status : Unknown
Test Name LM UDP Ports DM UDP Ports Status

-----------------------------------------------------------------------------
test1 53249, 53249 53248, 53248 In Progress
test2 53251, 53251 53250, 53250 In Progress
test3 53253, 53253 53252, 53252 In Progress
test4 53255, 53255 53254, 53254 In Progress
test5 53257, 53257 53256, 53256 In Progress
test6 53259, 53259 53258, 53258 In Progress
test7 53261, 53261 53260, 53260 In Progress
test8 53263, 53263 53262, 53262 In Progress
Note
Elapsed Time includes the time it has so far taken to perform the steps,
including the inter-step wait time.
 To display the test status (responder side):

• At the config>test>l3sat>responder(<responder-name>)# prompt, enter:
show status
ETX-2>config>test>l3sat>responder(1)# show status
Application Type : L3 Over L2
Router Entity : 1
Responder Status : Ready
Total LM / DM Rx. Packets : 312164 / 1007
Viewing L3 SAT Test Reports

The generator calculates performance parameters according to the received test
packets, for each peer and its active test sessions. The performance parameters
are recalculated every minute. The performance parameters are presented in
test reports that can be viewed per peer and test session.
Note Unavailable and out-of-sync time affect parameter evaluation as follows:

• A minute is considered as unavailable if it has more than 75% packet loss,
therefore is considered as available if it has packet loss less than or equal to
25%. Unavailable time is not used for performance parameter evaluation and
comparison with test objectives.
• A minute is considered as out-of-sync if during the minute there was not
accurate TOD synchronization between the generator device and the
responder device. Out-of-sync time is not used for forward and backward
packet transfer delay (PTD) evaluation and comparison with test objectives.
 To display summary test results:

• At the

prompt, enter:
show summary-report
ETX-2>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show summary-report
End Points
Generator Address : 50.50.50.100
Responder Address : 50.50.50.101
MTU (bytes) : 1500
Test
Scope : Configuration + Performance
Peer Profile Name : peer1
Start Date & Time : 2014-12-04 13:28:10
End Date & Time : 2014-12-04 13:31:23
Total Duration : 193
Overall Result : Failed
Test Name BW DSCP Conf. Result Perf. Result

(Mbps)
-----------------------------------------------------------------------------
test1 2.000 3 Failed Not Applicable
test2 1.000 3 Failed Not Applicable
 To display detailed test results:

• At the
prompt, enter:
show report <test-name>
The detailed report is displayed. For information on the detailed test
report counters, see Table 11-12.
ETX-2>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show report test1
End Points
Generator Address : 50.50.50.100
Responder Address : 50.50.50.101
LM UDP Ports : 53248, 53248
DM UDP Ports : 53249, 53249
MTU (bytes) : 1500
Test
Scope : Configuration + Performance
Peer Profile Name : peer1
Report Type : No Clock Sync
BW (Mbps) : 1.000
DSCP : 3
IP Sizes (bytes) : 128, 512, 750
Session Profile Name : session3
Start Date & Time : 2014-12-04 13:33:55
End Date & Time : 2014-12-04 13:42:08
Total Duration : 493
Configuration Phase

-----------------------------------------------------------------------------
Duration (sec) : 100
Configuration Result : Passed
IP Size (bytes) : 128
Step Load
-----------------------------------------------------------------------------
Parameter Step#1 Step#2 Step#3 Step#4 Thr
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.249 0.500 0.749 1.001
IR - mean (Mbps) 0.249 0.499 0.750 1.001
PL - count 1 0 0 1
PLR 6.0E-4 0 0 1.0E-4 1.000E-3
PTD - min (ms) 4.075 4.073 4.062 4.077
PTD - mean (ms) 4.142 4.137 4.132 4.132 200.000
PTD - max (ms) 4.248 4.268 4.267 4.265
PTD - std (ms) 0.032 0.040 0.041 0.042
PDV - mean (ms) 0.067 0.064 0.070 0.070 0.150
PDV - max (ms) 0.173 0.195 0.205 0.188
IPDV-Fwd - mean (ms) 0.023 0.039 0.032 0.030
IPDV-Fwd - max (ms) 0.139 0.087 0.103 0.102
IPDV-Bck - mean (ms) 0.020 0.023 0.017 0.020
IPDV-Bck - max (ms) 0.057 0.075 0.063 0.112
---------------- -------- -------- -------- -------- --------
Result Passed Passed Passed Passed
Policing
-----------------------------------------------------------------------------
Parameter Policing Thr
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - mean (ms) 0.150
PDV - max (ms)
IPDV-Fwd - mean (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - mean (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Step Load
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.250 0.498 0.749 0.997
IR - mean (Mbps) 0.250 0.497 0.750 0.997

PL - count 0 0 0 0
PLR 0 0 0 0 1.000E-3
PTD - min (ms) 4.780 4.753 4.764 4.769
PTD - mean (ms) 4.864 4.856 4.872 4.872 200.000
PTD - max (ms) 5.190 5.225 5.164 5.250
PTD - std (ms) 0.060 0.080 0.093 0.077
PDV - mean (ms) 0.084 0.103 0.108 0.108 0.150
PDV - max (ms) 0.410 0.472 0.400 0.481
IPDV-Fwd - mean (ms) 0.038 0.031 0.051 0.050
IPDV-Fwd - max (ms) 0.296 0.133 0.330 0.295
IPDV-Bck - mean (ms) 0.032 0.057 0.067 0.039
IPDV-Bck - max (ms) 0.314 0.394 0.315 0.138
---------------- -------- -------- -------- -------- --------
Policing
-----------------------------------------------------------------------------
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - max (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Step Load
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.250 0.498 0.748 0.999
IR - mean (Mbps) 0.250 0.498 0.748 0.998
PL - count 0 0 0 1
PLR 0 0 0 9.0E-4 1.000E-3
PTD - min (ms) 5.233 5.249 5.198 5.233
PTD - mean (ms) 5.296 5.297 5.318 5.318 200.000
PTD - max (ms) 5.577 5.357 5.731 5.757
PTD - std (ms) 0.052 0.025 0.099 0.102
PDV - mean (ms) 0.063 0.048 0.120 0.120 0.150
PDV - max (ms) 0.344 0.108 0.533 0.524
IPDV-Fwd - mean (ms) 0.028 0.021 0.064 0.058
IPDV-Fwd - max (ms) 0.079 0.064 0.470 0.488
IPDV-Bck - mean (ms) 0.024 0.013 0.039 0.046
IPDV-Bck - max (ms) 0.313 0.048 0.224 0.416

---------------- -------- -------- -------- -------- --------

Policing
-----------------------------------------------------------------------------
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - max (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Performance Phase
-----------------------------------------------------------------------------
Duration (min) : 5
Configuration Result : Failed
Parameter IP Size #1 IP Size #2 IP Size #3 IP Size #4 Thr
128 bytes 512 bytes 750 bytes 0 bytes
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.999 0.997 0.998
IR - mean (Mbps) 0.999 0.997 0.998
PL - count 0 0 0
PLR 0 0 0 0 1.000E-3
UAS - count 0 0 0
Availability (%) 100.00 100.00 100.00 99.90
PTD - min (ms) 4.046 4.764 5.187
PTD - mean (ms) 4.171 4.899 5.401 5.401 200.000
PTD - max (ms) 4.444 5.337 5.875
PTD - std (ms) 0.064 0.112 0.158
PDV - mean (ms) 0.125 0.135 0.214 0.214 0.150
PDV - max (ms) 0.398 0.573 0.688
IPDV-Fwd - mean (ms) 0.049 0.077 0.110
IPDV-Fwd - max (ms) 0.234 0.399 0.593
IPDV-Bck - mean (ms) 0.037 0.047 0.097
IPDV-Bck - max (ms) 0.165 0.358 0.543
PD-Fwd - count 0 0 0
PDR-Fwd 0 0 0 0
PD-Bck - count 0 0 0
PDR-Bck 0 0 0 0
PR-Fwd - count 0 0 0
PRR-Fwd 0 0 0 0
PR-Bck - count 0 0 0
PRR-Bck 0 0 0 0
---------------- -------- -------- -------- -------- --------

Result Passed Passed Failed

The following table shows the test report parameters. The columns CS and NCS
indicate if the parameter is presented for report type clock-sync and
no-clock-sync, respectively. The forward direction refers to generator to
responder, and backward direction refers to responder to generator.
Table 11-12. L3 SAT Report Parameters
Counter Description CS NCS
Information Rate (IR) Number of received test packets times test packet Ethernet frame  
length (in bits), divided by the elapsed time (in seconds)
Note: The test packet Ethernet frame length starts with the first
MAC address bit, and ends with the last FCS bit.
Packet loss (PL) Number of lost test packets. A test packet is considered lost in the  
following cases:
• Test packet was not received back at the generator, or was
received with a round-trip delay of over two seconds.
• Report type parameter is clock-sync and the responder type is
loop and timestamp, and test packet was received with a
forward and/or backward delay over one second.
Packet loss ratio (PLR) Number of lost packets divided by the number of transmitted  
packets
Unavailable seconds Total number of unavailable seconds.  
Available seconds (%) Percentage of available seconds  
Round-trip packet transfer Minimum round-trip PTD. The round-trip PTD is calculated from the × 
delay (PTD) – min test packet embedded timestamps. A round-trip PTD over two
seconds is ignored, as the packet is considered lost.
Round-trip PTD – mean Average round-trip PTD × 
Round-trip PTD – max Maximum round-trip PTD × 
Round-trip PTD – std Standard deviation round-trip PTD × 
One-way packet transfer delay Minimum forward PTD. The forward PTD is calculated from the test  ×
(PTD), forward – min packet embedded timestamps. A forward PTD over one second is
ignored, as the packet is considered lost.
Note: The one-way PTD measurements are valid only when there is
TOD synchronization between the generator device and the
responder device, and accurate TOD synchronization is feasible only
with a responder of type loop and timestamp.
One-way packet transfer delay Average forward PTD  ×

(PTD), forward – mean
One-way packet transfer delay Maximum forward PTD  ×

(PTD), forward – max
One-way packet transfer delay Standard deviation forward PTD  ×

(PTD), forward – std

One-way packet transfer delay Minimum backward PTD. The backward PTD is calculated from the  ×
(PTD), backward – min test packet embedded timestamps. A backward PTD over one
second is ignored, as the packet is considered lost.
One-way packet transfer delay Average backward PTD  ×

(PTD), backward – mean
One-way packet transfer delay Maximum backward PTD  ×

(PTD), backward – max
One-way packet transfer delay Standard deviation backward PTD  ×

(PTD), backward – std
Round-trip delay variation (PDV) Average round-trip PDV. The round-trip PDV is calculated according × 
– mean to ITU-T Y.1540, by subtracting the minimum PTD from the 99.9%
percentile of the PTD values.
Round-trip delay variation (PDV) Maximum round-trip PDV × 

– max
One-way packet transfer delay Average forward PDV  ×

variation (PDV), forward – mean
One-way packet transfer delay Maximum forward PDV  ×

variation (PDV), forward – max
One-way packet transfer delay Average backward PDV  ×

variation (PDV), backward –
mean
One-way packet transfer delay Maximum backward PDV  ×

variation (PDV), backward – max
One-way inter-packet delay Average forward IPDV. IPDV is calculated according to RFC 3393,  
variation (IPDV) ), forward – from the variations of the delays between valid packets.
mean Note: Appears in report only if responder type is loop and
timestamp.
One-way inter-packet delay Maximum forward IPDV  

variation (IPDV) ), forward – Note: Appears in report only if responder type is loop and
max timestamp.
One-way inter-packet delay Average backward IPDV. IPDV is calculated according to RFC 3393,  
variation (IPDV) ), backward – from the variations of the delays between valid packets.
mean Note: Appears in report only if responder type is loop and
timestamp.
One-way inter-packet delay Maximum backward IPDV  

variation (IPDV) ), backward – Note: Appears in report only if responder type is loop and
max timestamp.

One-way Packet Duplication Number of duplicate packets in forward direction. A packet is  

(PD), forward considered duplicate (forward) if its generator Tx timestamp
matches that of a previously received packet, and the responder Tx
timestamps are different.
Note: Appears in report only if responder type is loop and
timestamp.
One-way Packet Duplication Number of duplicate packets in backward direction. A packet is  

(PD), backward considered duplicate (backward) if its responder Tx timestamp
matches that of a previously received packet.
timestamp.
One-way Packet Duplication PDR (forward) is calculated as PD (forward) divided by the number  ×
Ratio (PDR), forward of received valid packets, converted to a percentage.
One-way Packet Duplication PDR (backward) is calculated as PD (backward) divided by the  ×

Ratio (PDR), backward number of received valid packets, converted to a percentage.
One-way Packets Reordered Number of reordered packets in forward direction. A packet is  

(PR), forward considered reordered (forward) if its generatorTx timestamp is
smaller than that of a previously received packet in forward
direction. Duplicated and lost packets are not included in the
calculation.
timestamp.
One-way Packets Reordered Number of reordered packets in backward direction. A packet is  

(PR), backward considered reordered (backward) if its responder Tx timestamp is
smaller than that of a previously received packet in backward
direction. Duplicated and lost packets are not included in the
calculation.
timestamp.
One-way Packets Reordered PRR (forward) is calculated as PR (forward) divided by the number  ×
Ratio (PRR), forward of received valid packets, converted to a percentage.
One-way Packets Reordered PRR (backward) is calculated as PR (backward) divided by the  ×

Ratio (PRR), backward number of received valid packets, converted to a percentage.
Examples
Layer-2 Probe Mode

This example illustrates configuring L3 SAT in layer-2 probe mode:
• Generator is ETX203AX or ETX205A with IP address = 20.20.20.101

• Router: Associate Interface 2 with SVI 2 (type TWAMP).

• Flows between Ethernet ports 1 and 3, classified to VLAN 100

exit all
#*********Configure SVI type TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit
flow E1toE3
classifier v100
no shutdown
exit
flow E3toE1
classifier v100
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.20/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT responder

test
l3sat
responder res1 l2-probe
bind ethernet 3
router-entity 1
vlan-tag vlan 100 pbit fixed 3
no shutdown
exit all
save
 To configure the generator:

• Router: Associate Interface 2 with SVI 2 (type TWAMP).
• Flows between Ethernet ports 1 and 3, classified to VLAN 100

• Test sessions:
 Session1:
 Packet sizes 128, 512, and 750
 Bandwidth 10000
 DSCP 11
 Session2:
 Default packet size (256)
 Bandwidth 5000
 DSCP 12
exit all
#*********Configure SVI type TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit

flow E1toE3
classifier v100
no shutdown
exit
flow E3toE1
classifier v100
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.101/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT peer profile

test
l3sat

peer-profile peer1
performance-duration custom 5
exit
#*********Configure L3 SAT session profiles

session-profile session1
ip-size 128 512 custom 750
exit
exit
#*********Configure L3 SAT generator
generator gen1 l2-probe
bind ethernet 3
router-entity 1
vlan-tag vlan 100 pbit fixed 3
no shutdown
peer 20.20.20.20
peer-profile peer1
test-session test1 session-profile session1 bw 10000
dscp 11
dscp 12
activate
exit
exit all
save
Layer-3
This example illustrates configuring L3 SAT in Layer-3 mode:
• Generator is ETX203AX or ETX205A with IP address = 20.20.20.101

 Ethernet port 3 to SVI 2: Traffic tagged with VLAN 12, VLAN popped
 SVI 2 to Ethernet port 3: All traffic, VLAN 12 pushed
exit all
#*********Configure SVI for L3 SAT
configure
port
svi 2
no shutdown
exit
exit
#********* Configure classifiers for VLAN 12 & all traffic

flows
match vlan 12

exit
match all
exit
flow E3toSVI2
classifier v12
vlan-tag pop vlan
no shutdown
exit
flow SVI2toE3
ingress-port svi 2
classifier all
no shutdown
exit
exit
#*********Configure router with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.20/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT responder

test
l3sat
responder res1
router-entity 1
no shutdown
exit all
save
 To configure the generator:

 Ethernet port 3 to SVI 2: Traffic tagged with VLAN 12, VLAN popped
 SVI 2 to Ethernet port 3: All traffic, VLAN 12 pushed
• Test sessions:
 Session1:
 Packet sizes 512, 700
 Bandwidth 10000
 DSCP 11

 Session2:
 Default packet size (256)
 Bandwidth 5000
 DSCP 12
exit all
#*********Configure SVI for L3 SAT
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifiers for VLAN 12 & all traffic

flows
match vlan 12
exit
match all
exit

flow E3toSVI2
classifier v12
vlan-tag pop vlan
no shutdown
exit
flow SVI2toE3
ingress-port svi 2
classifier all
no shutdown
exit
exit
#*********Configure router with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.101/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT peer profile

test
l3sat
peer-profile peer1

exit
#*********Configure L3 SAT session profiles
ip-size 512 custom 700
exit
exit
#*********Configure L3 SAT generator

generator gen1
router-entity 1
no shutdown
peer 20.20.20.20
peer-profile peer1
dscp 11
dscp 12
activate
exit all
save
11.6 RFC-2544 Testing

You can perform BERT testing based on RFC-2544:
Throughput test Detect the maximum frame rate without lost frames.
Packet loss test Detect the point at which frame loss does not occur.
Latency test Determine average frame roundtrip time.
Note
You can run the RFC-2544 tests up to 1 GbE at a time.
Applicable Products
Standards
RFC-2544, Benchmarking Methodology for Carrier Ethernet Networks
Benefits
You can evaluate the performance of network devices to provide performance
metrics of the Ethernet network and validate the SLA.
ETX-2 RFC-2544 Testing 11-141

RFC-2544 testing uses OAM CFM messages such as Loopback (LB), Loss
Measurements (LM), and Delay Measurements (DM) frames. Therefore,
end-to-end OAM CFM is necessary for the testing. User data can’t be
transmitted via associated OAM service data/flows while an RFC-2544 test is
running.
In a bidirectional throughput test, the local ETX-2 generates LBM + data TLV
messages towards the far-end device, which responds with LBR messages. The
local ETX-2 calculates the round trip throughput.
In a unidirectional throughput test, the local ETX-2 generates 1DM messages
towards the far-end device, which verifies the frames and calculates
unidirectional throughput. The convergence algorithm is based on a binary
search using LMM and LMR messages.
The packet loss test is performed as follows for all selected frame sizes:
• Transmit x frames at a rate of 100% throughput.
• Calculate frame loss with the formula: (tx - rx) / 100 * tx
• Decrease rate by 10% and repeat the test until two trials result in no frame
loss.
The latency test is performed as follows:
• Transmit DMM frames at throughput rate for 10 seconds.
• Calculate the latency using DMM and DMR frames that are transmitted after
1 second.
• The test result is the average of the number of iterations per frame size (up
to 5 minutes per frame size).
• Applicable for round-trip mode
Note If the remote MEP status is NEW, ETX-2 does not launch the RFC-2544 test,
unless the relevant dest NE is configured with the remote MAC address.
Factory Defaults
By default, no profiles or tests are defined.
When you create a test profile, it is configured by default as shown below.
ETX-2# config test rfc2544
ETX-2>config>test>rfc2544# profile-name Testprf
ETX-2>config>test>rfc2544>profile-nam(Testprf)$ inf d
frame-size 64
pattern all-ones
tlv-type data
test-direction bidirectional
frames-number-in-attempt 200000
frame-loss-tolerance 20
throughput-measurement-accuracy 100000
number-of-trials 1
no learning-frames
11-142 RFC-2544 Testing ETX-2

When you create a test, it is configured by default as shown below.

ETX-2# config test rfc2544
ETX-2>config>test>rfc2544# test 1
ETX-2>config>test>rfc2544>test(1)$ inf d
no bind
max-rate 0 convention data-rate compensation 0
type throughput
no max-test-duration
no associated-flow
Performing Tests
In order to perform RFC-2544 tests, you must configure:
• Bidirectional data flows that are administratively enabled. If one of the flows
is associated with the test, its egress port and queue block must be identical
to the associated port and queue block of the MEP to which the test is
bound.
• MEP and Destination NE
• RFC-2544 profile – Template to create test runs. You can configure up to
eight test profiles.
• RFC-2544 test – Associated with RFC-2544 profile. Up to eight tests can use
the same test profile. In one RFC-2544 test, you can perform one or more of
the three test types.
Note Up to eight RFC-2544 tests can run concurrently.
If you are performing more than one type of test, they are performed in the
following order:
• Throughput
• Packet loss
• Latency – Up to 20 latency test attempts are performed in the remaining
time, according to the configured maximum test duration (each attempt
requires 15 seconds).
 To configure RFC-2544 test profiles:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
profile-name <name>
A test profile with the specified name is created if it does not already
exist, and the config>test>RFC2544> profile-nam(<name>)# prompt is
displayed.

Configuring frame loss tolerance 1/1 frame-loss-tolerance <frames> Defines the success criteria for
(one to one) the throughput test.
Each throughput attempt is
defined as a success only if the
amount of lost packets is less
than or equal to the number of
frames configured for frame-
loss-tolerance.
Success in a throughput
attempt sets the next attempt
to a higher rate, while a failure
in an attempt sets the next
attempt to a lower rate.
Configuring frame sizes for the test frame-size [64] [128] [256] [512] [1024] [1280] You can specify one or more
[1518] [1700] [1900] [2000] [custom <custom>] standard frame sizes, as well as
a custom frame size (64–2000).
Configuring how many frames in frames-number-in-attempt The maximum number of frames

attempt (transmitted packets) is the
maximal value of unsigned long
(4294967295 (0xffffffff)).
Configuring amount and frequency of learning-frames number <value> frequency { once |

learning frames once-per-trial }
no learning-frames
Configuring the number of trials for number-of-trials <value> Possible values: 1–3
the test
Configuring pattern of test frame pattern { all-ones | all-zeros-without-crc |

payload all-zeros-with-crc | alternate | prbs-with-crc |
prbs-without-crc }
Configuring direction of test test-direction { unidirectional | bidirectional }

(unidirectional or bidirectional)
Configuring accuracy of throughput throughput-measurement-accuracy <bps>

measurement
Disabling ETH-LCK frame when no eth-lck By default, ETH-LCK is enabled.

activating RFC-2544 test
Configuring TLV type as test or data tlv-type { test | data }
 To configure RFC-2544 tests:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
test <id>
The config>test>rfc2544> test(<id>)# prompt is displayed.

Activating the test activate date <dd-mm-yyyy> <hh:mm:ss> Type no activate to stop the
activate recurring <hours> test.
Associating test with flow in order to associated-flow <name> Flow must be active and its
retrieve bandwidth profile and QoS egress port and queue block
information. must be identical to the
associated port and queue
block of the MEP to which the
test is bound.
Binding to destination NE bind oam-cfm md <md-id> ma <ma-id> mep <mep-id> There must be bidirectional
service <service-id> dest-ne <dest-ne-id> flows using the same
classification and port
associated with the MEP.
Configuring maximum rate for test max-rate <bps> [convention {line-rate | data-rate}] max-rate – The maximum rate
[compensation <compensation>] applies to throughput and loss
tests.
convention – Determines
whether the interpacket gap is
included in test result
calculations:
line-rate – Interpacket gap is
included.
data-rate – Interpacket gap is
not included.
compensation – Allowed range
is 0–63. The compensation
value is added to frame size, to
allow for Layer-1 overhead in
the network.
Note: It is not necessary to
configure the maximum rate if
associated-flow is used to
associate the test with a flow
that has a policer profile, as in
that case the maximum rate is
derived from the flow policer
profile.
Configuring maximum duration of max-test-duration <minutes> Possible values: 0, or 2–60
test The value 0 indicates no limit;
the test runs until it completes.
If a value from 2–60 is
configured, the test is stopped
when the configured maximum
duration has elapsed, whether
or not all the configured test
types have completed.

Associating a test profile with the test-profile <name>

test
Defining the type(s) of benchmark type [throughput] [latency] [frame-loss]

test to perform on this run
Clearing test report clear-reports
Displaying number of lost frames for show attempt-lost-frames See Viewing Lost Frames Per
each test attempt Test Attempt.
Displaying test report show report all See Viewing Test Report.
show report iteration <iteration-number>
Displaying test status show status See Viewing Test Status.
Displaying test summary show summary See Viewing Test Results.
Examples
Running RFC-2544 Test

 To run RFC-2544 test:
• Test direction – bidirectional
• Number of trials – 2
• Frame sizes – 64, 256, 1400 [custom]
• Test types – throughput, frame loss, latency
• Bound to MD 1 MA 1 service 1 MEP 1 Destination NE 1
• Associated to flow test_flow1, that has associated policer profile
test_policer with CIR=9984, EIR = 0, and is associated with classification,
port, and queue block of the above MEP
• Maximum test duration – 1 hour
ETX-2# configure test rfc2544
ETX-2>config>test>rfc2544# profile-name p1
ETX-2>config>test>rfc2544>profile-nam(p1)$
ETX-2>config>test>rfc2544>profile-nam(p1)$ frame-size 64 256 custom 1400
ETX-2>config>test>rfc2544>profile-nam(p1)$ pattern all-ones
ETX-2>config>test>rfc2544>profile-nam(p1)$ tlv-type data
ETX-2>config>test>rfc2544>profile-nam(p1)$ test-direction bidirectional
ETX-2>config>test>rfc2544>profile-nam(p1)$ frames-number-in-attempt 5000
ETX-2>config>test>rfc2544>profile-nam(p1)$ frame-loss-tolerance 10
ETX-2>config>test>rfc2544>profile-nam(p1)$ number-of-trials 2
ETX-2>config>test>rfc2544>profile-nam(p1)$ no learning-frames
ETX-2>config>test>rfc2544>profile-nam(p1)$ no eth-lck
ETX2x>config>test>rfc2544>profile-nam(p1)$ exit
ETX-2>config>test>rfc2544# test 1
ETX-2>config>test>rfc2544>test(1)$ test-profile p1
ETX-2>config>test>rfc2544>test(1)$ type throughput latency frame-loss
ETX-2>config>test>rfc2544>test(1)$ bind oam-cfm md 1 ma 1 mep 1 service 1
dest-ne 1

ETX-2>config>test>rfc2544>test(1)$ associated-flow test_flow1

ETX-2>config>test>rfc2544>test(1)$ max-test-duration 60
ETX-2>config>test>rfc2544>test(1)$ activate
ETX-2>config>test>rfc2544>test(1)$ show status
Activity Status : In Progress
Elapsed Time <dd:hh:mm:ss> : <00:00:15:24>
ETX-2>config>test>rfc2544>test(1)$ show status
Activity Status : Completed
ETX-2>config>test>rfc2544>test(1)$ show summary

Iteration Start Start Duration Duration
Date Time Days Time
-----------------------------------------------------------------------------
1 08-01-2012 11:31:43 0 <00:38:25>
Viewing Test Report

You can display the test report for all iterations, or for a specific iteration.
The following illustrates displaying the test report for the test from the above
section (all iterations).
 To display the complete test report:

• In the config>test>rfc2544>test<test number># prompt, enter show report
all.
The complete report screen is displayed. For information on the test
report counters, see Table 11-13.
ETX-2>config>test>rfc2544>test(1)$ show report all
Test ID : 1
Iteration Number : 1
Date & Time : 08-01-2012 11:31:43
Profile Name : p1
Number of Trials : 2
Duration <dd:hh:mm:ss> : <00:00:38:25>
Test Parameters
-----------------------------------------------------------------------------
Bind: MD : 1 MA : 1
MEP : 1
P-Bit : 0 VLAN : 200
Max Rate (bps) : 1000000000
Convention : Data Rate Compensation : 0
Frames in Burst : 200000
Pattern : All Ones
Frame Type : Data
Search Resolution : 1 Tolerance : 5
Learning Frames: : 0 Frequency :
Direction : Bidirectional
Flow Parameters
-----------------------------------------------------------------------------
Flow Name : test_flow1
Fixed Queue : 0 Mapping Profile :
Policer Name : test_policer
CIR (Kbps) : 9984 EIR (Kbps) : 0

Throughput Report
-----------------------------------------------------------------------------
Trial : 1
Status : Success Duration : <00:00:00:49>
Frame Size Theoretical Max Throughput Throughput Success
(FPS) (FPS) (Mbps) (%)
-----------------------------------------------------------------------------
64 1953125 1490312 763.040 76
256 488281 453309 928.379 92
1400 97656 96173 984.812 98
Throughput Report
-----------------------------------------------------------------------------
Trial : 2
Frame Size Theoretical Max Throughput Throughput Success
(FPS) (FPS) (Mbps) (%)
-----------------------------------------------------------------------------
64 1953125 1490312 763.040 76
256 488281 453309 928.379 92
1400 97656 96173 984.812 98
Loss Report
-----------------------------------------------------------------------------
Trial : 1
Frame Size : 64
Theoretical Max (FPS) : 1953125
Throughput of Max Success

(%) (%)
-----------------------------------------------------------------------------
100 76
90 84
80 95
70 100
60 100
Frame Size : 256


(%) (%)
-----------------------------------------------------------------------------
100 92
90 100
80 100
Frame Size : 1400


(%) (%)

-----------------------------------------------------------------------------
100 98
90 100
80 100
Loss Report
-----------------------------------------------------------------------------
Trial : 2
Frame Size : 64

(%) (%)
-----------------------------------------------------------------------------
100 76
90 84
80 95
70 100
60 100
Frame Size : 256

(%) (%)
-----------------------------------------------------------------------------
100 92
90 100
80 100
Frame Size : 1400


(%) (%)
-----------------------------------------------------------------------------
100 98
90 100
80 100
Latency Report
-----------------------------------------------------------------------------
Trial : 1

Num of Attempts : 20
Frame Size Latency

(micro-sec)
-----------------------------------------------------------------------------
64 1

256 1
1400 1
Latency Report
-----------------------------------------------------------------------------
Trial : 2

Num of Attempts : 20
Frame Size Latency

(micro-sec)
-----------------------------------------------------------------------------
64 0
256 0
1400 0
ETX-2>config>test>rfc2544>test(1)$
 To display the test report for a specific iteration:

• In the config>test>rfc2544>test<test number># prompt, enter show report
iteration <iteration number>.
The report screen is displayed for the requested iteration. For
information on the test report counters, see Table 11-13.
ETX-2>config>test>rfc2544>test(1)# show report iteration 1
Test ID : 1
Iteration Number : 1
Date & Time
Profile Name : p1
Number of Trials : 1
Duration <dd:hh:mm:ss>
Test Parameters
-----------------------------------------------------------------------------
Bind: MD : 1 MA : 1 MEP
: 1
P-Bit : 0 VLAN : 100
Max Rate (bps) : 100000
Convention : Data Rate Compensation : 0
Frames in Burst : 100000 Pattern : All
Ones Frame Type : Data
Search Resolution : 10000 Tolerance : 50
Learning Frames : 0 Frequency :
Direction : Bidirectional
Table 11-13. RFC-2544 Test Parameters
Counter Description
Bind The MEP parameters that the RFC-2544 test is running on
P-Bit The P-Bit of the tested service

Counter Description
VLAN The VLAN on which test is performed
Max Rate (bps) The maximum rate at which the test starts
Convention Convention used for this test:

Line Rate or Data Rate
Compensation Indicates whether compensation due to editing will be performed in

the test and the number of bytes that will be compensated
Frames in Burst The number of frames transmitted in each attempt
Pattern The data pattern in the transmitted packets
Frame Type The frame type (TLV) used in the transmitted packets:
Data or Test
Search Size of the smallest search resolution step

Resolution
Tolerance The number of packets that can be lost without declaring Fail
Learning Frames Indicates whether some frames are transmitted before the test
starts, in order to enable the network learning
Frequency Indicates whether learning frames are transmitted once per test or
once per trial
Direction Bidirectional or Unidirectional
Viewing Test Status
 To display the test status:

• In the config>test>rfc2544>test<test number># prompt, enter show status.
The status screen appears. For information on the test status values,
see Table 11-14.
ETX-2>config>test>rfc2544>test(1)# show status
Activity Status : In Progress
Elapsed Time <dd:hh:mm:ss> : <00:00:16:39>
Current Test Type : Throughput Current Frame Size : 64

Trial No. : 1 Attempt No. : 1
Remote MEP Status : OK
Table 11-14. RFC-2544 Test Status
Displayed
Current Test Type Test type can be:

Throughput
Packet Loss
Latency
Current Frame Size Current tested frame size

Displayed
Trial No. Current trial number. 1–3
Attempt No. Current performed attempt number
Remote MEP Peer OAM status

Status
Viewing Lost Frames Per Test Attempt

The following illustrates displaying the number of lost frames for each test
attempt.
ETX-2>config>test>rfc2544>test(1)$ show attempt-lost-frames
Test ID : 4
Number of Frames in Attempt : 700000
Trial : 1
Frame Size : 128
Attempt Throughput Loss Frames

---------------------------------------------------------------
1 999999488 559210
2 499999744 419391
3 249999872 139756
4 124999936 0
5 187499904 0
6 218749888 59908
7 203124896 10805
8 195312400 0
9 199218648 0
10 201171772 4070
11 200195210 650
Viewing Test Results

You can display a summary of the RFC-2544 test results.
 To display the summary test results:

• In the config>test>rfc2544>test<test number># prompt, enter show
summary.
The summary report screen is displayed. For information on the test
report summary counters, see the following table.
ETX-2>config>test>rfc2544>test(5)# show summary
Iteration Start Start Duration Duration
Date Time Days Time
---------------------------------------------------------------
1 10-08-2015 15:16:40 0 <04:17:04>

Table 11-15. RFC-2544 Test Counters (Summary)
Counter Description
Iteration The iteration number of the test
Start Date The date that the test started (dd-mm-yyyy)
Start Time The time of day that the test started (hh:mm:ss)
Duration Days The duration of the test in days
Duration Time The duration of the test (hh:mm:ss)
11.7 Syslog
ETX-2 uses the Syslog protocol to generate event notification messages and
transport them over IP networks to Syslog servers.
Applicable Products
Standards
RFC 3164, RFC 5674
Benefits
Syslog protocol collects heterogeneous data into a single data repository. It
provides system administrators with a single point of management for collecting,
distributing, and processing audit data. Syslog standardizes log file formats,
making it easier to examine log data with various standard tools. Data logging
can be used for:
• Long-term auditing
• Intrusion detection
• Tracking user and administrator activity
• Product operation management
When an alarm or event occurs, if it is not masked for logging, it is saved in the
log file. The Syslog protocol provides an instrument for generating and
transporting event notification messages from ETX-2 logs to servers across IP
networks.
Optionally, you can enable Syslog servers to also log accounting commands.
You can log these events on remote Syslog servers, or locally (i.e. on the
device), in which case you configure a local Syslog server with IP address
127.0.0.1 (see Local Syslog Accounting below).
ETX-2 Syslog 11-153

Note The password that you enter when creating a new user (configure management
login-user <name> password <password>, or when copying a file (file copy
<source-file-url> <destination-file-url> sftp://<username>:<password>) is
masked in Syslog under CLI command accounting. The password entered appears
in the Syslog command-log as asterisks (*), thus providing protection from
sniffers.
PSN
ETX-203AX
Syslog
Server
ETX-203AM
Figure 11-26. Syslog Functionality
Elements
Typical Syslog topology includes message senders (clients) and message
receivers (servers). ETX-2 supports Syslog client functionality. It can send
messages to up to five Syslog servers. The receiver displays, stores, or forwards
logged information. The standard designates two types of receivers:
Relay Forwards messages
Collector Displays and stores messages
Transport Protocol
Usually, Syslog uses UDP port 514 for its transport, but devices and servers can
be defined to use any port for communication.
Message Format
The length of a Syslog message is 1024 bytes or less. It contains the following
information:
• Facility and severity (see below)
• Timestamp – local time of the device when it sent the message
• Hostname – IP address of the device that sent the message
• Message content – tag and message content.
 Tag:
 For an alarm or event – Tag is the source of the alarm/event, which
is a string combining source type and source ID (such as system, Eth
1, E1 1/1).
 For an accounting command – Tag is CMD_ACCT.
 Message content – a colon : followed by:
 For an alarm or event – the alarm/event description, as sent in SNMP
traps.
11-154 Syslog ETX-2

 For an accounting command – user@device: command, where

user – username logged in or out. If the command was executed by
the device scheduler, the user is sched.
device – IP address of the user’s machine (in case of Telnet or SSH),
console if the session is from the local ACSII terminal, or sched if the
command was executed by the device scheduler.
command – command or level change that was executed, e.g. level-1
or no shutdown.
A typical Syslog message for an event looks like this:
<145>Jan 15 13:24:07 172.17.160.69 Eth 1: Loss of signal (LOS)
A typical Syslog message for an accounting command looks like this:
<146>Jan 22 13:00:08 172.17.160.69 CMD_ACCT: sched sched no shutdown
Facilities and Severities

Facility designates a device or application that sends a message. The standard
includes some predefined facilities in the 0–15 range. For originator
identification, you can configure ETX-2 to use facilities local1– local7; local1 is
the default facility.
Severity is assigned to a message to specify its importance. The device sends to
Syslog servers messages with severity equal to or higher than the configured
severity level.
Note Alarms and events masked for logging are not sent to Syslog regardless of the
severity.
ETX-2 uses the following severity designations:
Table 11-16. Syslog Severities
Code Syslog Type Description
0 Emergency Emergency message, not in use
1 Alert Critical alarm
2 Critical Major alarm
3 Error Minor alarm
4 Warning Event
5 Notice Cleared alarm and accounting message
6 Informational Informational message, not in use
7 Debug Debug-level messages, not in use
Local Syslog Accounting

ETX-2 supports saving into a local cyclic accounting file, called accounting-log,
each CLI configuration command. This includes Netconf RPC converted into CLI
commands.
ETX-2 Syslog 11-155

You can configure local Syslog accounting by configuring a local Syslog server
with IP address 127.0.0.1, and using the regular Syslog commands (except port,
which is irrelevant).
Accounting messages are saved in the accounting-log file in the same format
used when sending them to external Syslog servers.
The accounting-log file has the following features:
• The file has two partitions. When both partitions become full, the partition
with the older records is cleared.
• The file can be cleared of its records, but not deleted.
• The file is not affected by device reboot, as it is saved in permanent
memory.
• The file can be uploaded using the copy command, but cannot be
downloaded.
You can display the accounting-log file using the show accounting-log command
(see Viewing the Syslog Local Accounting Log), or clear it using the clear-
accounting-log command (see Clearing the Syslog Local Accounting Log).
Factory Defaults
By default, Syslog operation is disabled. When enabled, the default parameters
are as follows:
Syslog device
facility local1
port 514
severity-level informational
shutdown shutdown
Syslog server
address 0.0.0.0
port 514
accounting no accounting
shutdown shutdown
Configuring Syslog Parameters

When configuring Syslog parameters, it is mandatory to enable the Syslog device
(client) and define Syslog servers. The remaining configuration is optional.
11-156 Syslog ETX-2

Configuring the Syslog Device
 To configure the Syslog device:

1. Navigate to configure system syslog device.
The config>system>syslog(device)# prompt is displayed.
Clearing Syslog statistics clear-statistics See Clearing Syslog Statistics.
Defining a Syslog facility from which facility {local1 | local2 | local3 |

Syslog messages are sent local4 | local5 | local6 | local7}
Defining Syslog device UDP port for port <udp-port-number> Possible values: 1–65535
communication Port configuration is allowed
only if a Syslog device is
Defining severity level severity-level { emergency | alert | The log messages that contain
critical | error | warning | notice | severity level above or equal to
informational | debug} the specified level are
transmitted.
• emergency – emergency
messages
• alert – critical alarms
• critical – major alarms
• error – minor alarms
• warning – events
• notice – cleared alarms,
accounting messages
• informational –
informational messages
• debug – debug messages
Administratively enabling Syslog device no shutdown shutdown administratively

disables the Syslog device.
Displaying Syslog statistics show statistics See Viewing Syslog Statistics.
Configuring the Syslog Server
 To configure the Syslog server:

2. At the config>system# prompt, enter syslog server <server-ID> to specify
the server to receive Syslog messages, where <server-ID> is 1 to 5.
The config>system>syslog(server/<server-ID>)# prompt is displayed.
ETX-2 Syslog 11-157

Enabling Syslog accounting (i.e. logging) [no] accounting commands To disable command logging,
of command entries enter no accounting.
Note: Currently, only commands
accounting is available.
Defining Syslog server IP address address <ip-address> Possible values:

0.0.0.0–255.255.255.255
Note: For local Syslog
accounting, enter ip-address
127.0.0.1.
Defining Syslog server UDP port for port <udp-port-number> Possible values: 1–65535
communication Note: For local Syslog
accounting (server 127.0.0.1),
the Syslog port is not open to
packets entering from out of
the device. In this case, port
command is not available.
Administratively enabling Syslog server no shutdown shutdown administratively

disables Syslog server.
Note: shutdown command is
available only after you assign
an IP address to the Syslog
server.
Viewing Syslog Statistics

 To display Syslog statistics:
2. At the config>system>syslog(device)#, enter show statistics.
Syslog statistics appear as shown below. The counters are described in
the following table.
ETX-2>config>system>syslog(device)# show statistics
Total Tx Messages : 356
Non-queued Dropped Messages : 265
Table 11-17. 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
11-158 Syslog ETX-2

Clearing Syslog Statistics

 To clear Syslog statistics:
2. At the config>system>syslog(device)# prompt, enter clear-statistics.
The Syslog statistic counters are set to 0.
Viewing the Syslog Local Accounting Log

 To display the Syslog local accounting log:
2. At the config> reporting# prompt, enter show accounting-log.
The Syslog local accounting log is displayed, as shown in the following
example.
ETX-2>config>reporting# show accounting-log
<141>Jan 1 00:08:47 127.0.0.1 CMD_ACCT:su@172.17.230.68: no shutdown
<141>Jan 1 00:08:47 127.0.0.1 CMD_ACCT:su@172.17.230.68: exit
<141>Jan 1 00:08:56 127.0.0.1 CMD_ACCT:su@172.17.230.68: configure reporting
<141>Jan 1 00:09:00 127.0.0.1 CMD_ACCT:su@172.17.230.68: show accounting-log
<141>Jan 1 00:09:12 127.0.0.1 CMD_ACCT:su@172.17.230.68: system
<141>Jan 1 00:09:29 127.0.0.1 CMD_ACCT:su@172.17.230.68: syslog server 1
<141>Jan 1 00:10:00 127.0.0.1 CMD_ACCT:su@172.17.230.68: no shutdown
Clearing the Syslog Local Accounting Log

You can clear the local accounting-log file of its contents. You cannot delete the
file.
 To clear the Syslog accounting log:

2. At the config> reporting# prompt, enter clear-accounting-log.
The following table lists messages generated by ETX-2 when a configuration
error is detected.
Message Description
Syslog Port is out of range Selected UDP port value is out of allowed range (1–65535).
Port is illegal or Device Port is already in Selected UDP port is already in use.
use
ETX-2 Syslog 11-159

Message Description
Parameter cannot be changed if Logging Device/server UDP port or server IP address cannot be changed
Status/Server Access is enabled while Syslog server is enabled.
Illegal Severity Invalid severity value
Illegal Facility Invalid facility value
Illegal Server IP Address Invalid server IP address
Example
• Syslog device
 Facility: local2
 UDP port: 155
 Severity level: major
• Syslog server
 Server IP address: 178.16.173.152
 UDP port: 155
exit all
configure system
syslog device
facility local2
port 155
severity-level major
no shutdown
exit
syslog server 1
address 178.16.173.152
port 155
no shutdown
save
exit all
11.8 Y.1564 Ethernet Service Activation Test

The Ethernet service activation test provides out-of-service test methodology to
assess the proper configuration and performance of an Ethernet service prior to
customer notification and delivery.
Applicable Products
This feature is applicable to all ETX-2 products, except for capacity differences
between products that are specified where relevant.
Y.1564 over LAG is relevant for ETX220A only.
11-160 Y.1564 Ethernet Service Activation Test ETX-2

Standards
ITU-T Y.1564
Benefits
The Y.1564 testing methodology allows service providers to have a standard way
of measuring the performance of Ethernet-based services. The tests are
performed per multiple traffic streams simultaneously, confirming policing per
EVC or EVC.CoS.
Factory Defaults
By default, Ethernet service activation testing functionality is disabled.
When a Y.1564 test profile is added, it has the following default settings:
Parameter Default Value Units
auto-cos-completion no auto-cos-completion
ethernet-type 0x22e8
frame-size 512 Bytes
round-trip-thresholds flr – 200 PPM (1E-6)

ftd – 26000 Microseconds
fdv – 11000 Microseconds
availability – 9990 Hundredths of percent
direction bidirectional
color-aware color-aware
traffic-policing traffic-policing
cir-steps s1-percent – 25
s2-percent – 50
s3-percent – 75
s4-percent – 100
configuration-duration 60 Seconds
performance-duration 120 Minutes
rate-convention data-rate
responder-type y1564
user-traffic-blocked user-traffic-blocked
To assure quality of service (QoS), providers must properly configure their
networks to define how the traffic is prioritized in the network. This is
ETX-2 Y.1564 Ethernet Service Activation Test 11-161

accomplished by assigning different levels of priority to each type of service and

accurately configuring network prioritization algorithms. QoS enforcement refers
to the method used to differentiate the traffic of various services via specific
fields in the frames, thus providing better service to some frames over other
ones.
SLAs
The service-level agreement (SLA) is a binding contract between a service
provider and a customer, which guarantees the minimum performance that is
assured for the services provided.
Customer traffic is classified into three traffic classes, and each is assigned a
specific color: green for committed traffic, yellow for excess traffic, and red for
discarded traffic.
Policing
ETX-2 can set different traffic policing parameters. When a policer is activated, it
monitors the incoming frames and determines their color mode (CM). If CM is set
to color aware, ETX-2 monitors incoming frames and assigns them the relative
color (green or yellow) based on the frame header matching the policer setting
and current information rate.
Notes • When the Y.1564 test is configured as bidirectional, it may fail if the policer
profiles for the directions generator->responder and responder->generator
are different. For instance, the test could fail if a policer profile is defined for
the Rx and Tx flows in the generator, and the bandwidth of the ingress
policer is lower than that of the egress policer.
• You should configure a non-default policer profile for the Tx flow, and
configure no profile for the Rx flow.
• If multiple Tx flows are attached to the same MEP in the responder, any
policer profile attached to the Tx flows is not used in the responder egress
direction (back towards the generator).
• The Y.1564 generator discovers the test rate per service or service.CoS
policer, even when the policer is not an aggregate policer.
Blocking User Traffic

By default, user traffic on the flows associated with the test is automatically
blocked by the device from the time a test is activated until it is completed. You
can leave this default or configure the test to allow user traffic on the flows
associated to the test.
Y.1564 over LAG
Note Y.1564 over LAG is relevant for ETX220A only.
When LAG exists on the network path, Y.1564 is limited in its ability to test the
full path SLA of the EVC. To overcome this limitation, ETX220A supports
changing the source MAC address (SA) in each transmitted frame (instead of the
default, where the SA of the test frame is automatically inherited from the port

that the associated MEP is bound to), so that the frames pass through all the
links in the network LAG.
In the Y.1564 test profile, you can select this operation mode, by setting a block
of 32 consecutive MACs as SA. The SAs of generated test frames are then
cyclically selected from the block of 32 consecutive MAC addresses. By default,
0x0020D2000100 is the first MAC address in the block of MACs used as SA in
test frames. However, you have the option of setting another first address,
provided it is a multiple of 32.
When the hashing function of the network LAG is set to SA+DA MAC, the Y.1564
frames pass through all the links of the LAG, enabling testing the SLA of the
different links.
LAG (SA+DA MAC HASH) Y.1564 Gen
L2
Network ETX-220A
Router
Figure 11-27. Y.1564 over LAG
Y.1564 Standard
The ITU-T Y.1564 testing methodology ensures that quality is maintained across
networks with multiple streams and different policing parameters. Service
providers use the SAC (Service Acceptance Criteria) information which is normally
based on a subset of the users SLA to set pass/fail parameters.
There are two main objectives:
• To validate that each Ethernet-based service is correctly configured
• To validate the quality of the services as delivered to the end user
The test flowchart below illustrates the test phases.

Enter test
parameters
Start test
Service Fail Troubleshoot

configuration service
test configuration
Pass
Service
performance
test
Pass
Test completed
Figure 11-28. Y.1564 Test Flowchart
Configuration Test
The configuration test validates that services are configured as intended before
proceeding to the service performance test. Each service is tested individually
and the information rate (IR), Frame Transfer Delay (FTD), Frame Delay Variation
(FDV), and Frame Loss Ratio (FLR) are measured simultaneously. The test is
declared successful if the information rate and frame counters are within the
Service Acceptance Criteria (SAC).
The configuration test consists of the following procedures (mandatory to
implement and optional to perform):
• CIR (simple or stepped)
• EIR (color-blind)
• Traffic policing (color-blind); can be disabled
In addition, the configuration test consists of the following burst test
procedures (optional to implement):
• CBS (color-aware or color-blind)
• EBS (color-aware or color-blind)

The CBS and EBS burst sub-tests can be disabled (the default) or enabled. These
tests cannot coexist with another configuration test; if they do, a sanity error
occurs. However, they can coexist with other running performance tests.
A burst sub-test (CBS, EBS) consists of at least one transmission cycle. If
needed, the actual duration of a burst sub-test is automatically extended i.e. by
increasing the total duration of the configuration test.
Performance Test
The performance test validates the quality of the services over a
user-configurable period of time (one minute to five days). Traffic is generated
for all services at configured CIR levels; all Ethernet performance parameters are
measured simultaneously. The bandwidth test is performed according to the
bandwidth profile of a policer assigned to the associated flow, or a policer
assigned to the test.
Note • If there are two bandwidth profiles (flow and test), the test bandwidth
profile is used.
• OAM relevant packets are calculated as part of the test bandwidth.
Test Elements
The Y.1564 test is an intrusive procedure that includes two main elements:
• Generator – an entity that initiates the test, sends out the test and OAM
frames, receives responses from the responder, processes the resulting
measurements and displays test reports. In the case of a MEF46 LL
responder, the generator executes the Latching Loopback (LL) controller
functionality.
• Responder – an entity that receives the test and OAM frames from the
generator, and transmits a response to the generator. The responder can be
of the following types:
 Regular responder – adds time stamps to the OAM frames that it returns
to the generator
 MAC swap responder – does not add time stamps to the OAM frames
that it returns to the generator
 MEF46 Latching Loopback responder – Upon receiving LLM from the
generator, replies with LLRs. OAM frames are not looped back.
While performing/running the Y.1564 test, the responder does not transmit
PM packets.
The test operation can be configured as unidirectional or bidirectional (the
default). When bidirectional, service performance is measured on the frames
that make a round trip (generator > receiver > generator).
PSN
Forward
Backward
Generator Responder
Figure 11-29. Y.1564 Test Elements

Capacity
ETX-2 supports up to 8/64 simultaneous Y.1564 tests, with:
• Up to eight generators for ETX203AX, ETX203AM, and ETX205A, and up to
64 for ETX220A; one MEP per generator
• Up to 20 responders for ETX203AX, ETX203AM, and ETX205A, and up to
64 for ETX220A
The 8/64 generators and 20/64 responders can be activated over EVC, EVC.CoS,
or a combination of EVC and EVC.CoS. The Y.1564 generator is limited to two
VLANs.
The rate of the Y.1564 traffic for a single generator/responder or several
generators/responders running in parallel, cannot exceed 1 Gbps for ETX203AM,
ETX203AX or ETX205A; 10 Gbps for ETX220A (in the case of ports that
support 10 Gbps).
The test requires that the corresponding ingress and egress flows (or a
bidirectional flow) be preconfigured at both ends.
Test Cases
The Y.1564 test supports two cases:
Internal MEP case Supported for E-Line, E-LAN, and E-Tree services over PTP
or Bridge, in which MEPs are not preconfigured
Service MEP case Full support over point-to-point and E-LAN services, where
Down or Up MEPs are preconfigured
Operation – Internal MEP Case

The test traffic flow for Y.1564 tests – Internal MEP case is illustrated and
explained below.
In Internal MEP case, if a service MEP does not already exist, an Up MEP is
automatically created at the generator side under the first unused MA number at
MD level 7. An ACL is also automatically created on the receive side of the
generator. The ACL forwards to the internal MEP only frames having source MAC
address equal to the configured destination MAC address.
This automatically created MEP is automatically deleted at the end of the test.
In Internal MEP case, the Y.1564 test is associated with only one of the
following options:
• A single multi-CoS flow with an optional list of CoS values (default is “all
CoS”)
• One or more single CoS flows
• A service (identified by service name) with an egress port ID and an optional
list of CoS values (default is “all CoS”). In this case, the flows on which the
test is performed are automatically found.
If the EVC is classified by VLAN, the test is performed using P-bit value 5.
Note This P-bit value often represents high priority data.

Key=crs_mac
Generator Responder
Test
ETH Internal ETH ETH Automatic ETH
Frames
Port Up MEP ACL Port Port Block of User Port
Service Traffic
MAC Swap
Loopback
ETX-2 ETX-2
Figure 11-30. Y.1546 Test - Internal MEP Case (E-Line Services over PTP)
On all Flows to a
Bridge-port
Generator Responder
Test
ETH Internal ETH ETH Automatic ETH
Frames B
Port Up MEP ACL Port Port Block of User Port
Service Traffic
MAC Swap
Loopback
ETX-2 ETX-2
Figure 11-31. Y.1546 Test - Internal MEP Case (E-Line Services over Bridge)
Note When running the Y.1564 test in a device, without configuring the OAM (Internal
MEP case), configure the destination MAC address on the generator to the
responder NNI MAC, as per the device used.
The Y.1564 test for the Internal MEP case is performed as follows:
1. At the generator side, a unique MAC is configured.
2. At the generator side, an internal up MEP is automatically created.
3. At the generator side, the source transmits test frames at data rate
(different rates are used during different steps of the test) toward the
configured MAC.
4. DMM and LMM frames, transmitted periodically by the MEP at the generator
side, are interleaved with the test data.
5. At the responder side, the same unique MAC as used in the generator is
configured.
6. The responder loops back only frames with a destination MAC equal to the
configured MAC. If egress-port is a bridge-port, loop and ACL on all ingress
flows to a bridge-port.
7. At the generator receive side, an ACL forwards only frames whose source
MAC equals to the configured MAC.
8. When the generator receives the looped DMM and LMM frames, it
“responds” by sending DMR and LMR frames, respectively.
9. The responder loops back also the DMRs and LMRs.
10. Round-trip loss is measured by the sum of the LMR frame count and the
local count at the generator ingress.

11. Round-trip delay is measured by the DMR frame timestamps divided by two.
Operation – Service MEP Case

Generators and responders are supported over the following:
• Down MEPs for E-Line and E-LAN services:
 Down MEP facing network ports
 Down MEP facing PCS port
 Down MEP facing EoPDH (logical MAC)
• Up MEPs for E-Line and E-LAN services over bridge/ring:
 Up MEP facing bridge port
 Up MEP facing ETP
 Up MEP facing port (E-Line up MEP)
Note If a Y.1564 test is running over an ERP or ETP, any protection switchover causes
the test to fail.
Y.1564 test is supported over E-LAN in the presence of user traffic in the
following cases:
• E-LAN service is newly installed.
• E-LAN service is already installed and running on E-LAN nodes, and you add
a new node to the service. In this case, you can run the non-intrusive
Y.1564 test on the new node without disrupting (blocking) the traffic on the
other nodes.
For the Service MEP case, the MA of the service MEPs used by the test, must be
manually configured. The CoS on which the test is performed can optionally be
configured with a single value or several values from 0 to 7; the default ‘all CoS’
indicates that all the preconfigured EVC.CoS will be tested. The MEPs and flows
on which the test is performed are automatically learned from the configured
MA and CoS.
Regular Y.1564 Test

The test traffic flow for regular Y.1564 tests is illustrated and explained below.
The Y.1564 testing is disruptive; user traffic is blocked on the tested EVC during
diagnostic procedure.

Generator Responder
Test
Frames Test Frames,
DMMs, LMMs
Policer
PSN
Policer
Ethernet Down Ethernet Ethernet Down Ethernet
Looped Test Frames,
Port MEP Port Port MEP Port
DMRs, LMRs
Figure 11-32. Full Y.1564 Traffic Path for EVC with Single CoS (Down MEP)
Generator Responder
Test Test
ETH Down ETH ETH Down ETH
Frames B B Frames
Port MEP Port Port MEP Port
Service Service
ETX-2 ETX-2
Figure 11-33. Full Y.1564 Traffic Path
Note The responder can be configured to inject the test frames into the policer or
bypass it.
The regular Y.1564 test is performed as follows:

1. At the generator side, the source transmits test frames at specified data
rate (different rates are used during the different steps of the test).
2. The test frames are counted by the MEP LMM counters as they exit the
generator.
3. The test frames are counted again as they enter the responder by the MEP
LMM counters.
4. At the responder, the sink either drops the test frames or loops them back
(unidirectional or bidirectional test configuration).
5. LMR frames, returned by the MEP at the responder, plus local count at the
generator ingress, provide the round-trip loss measurements (looped test
frames are also counted by the LMR counters).
6. DMM frames, transmitted periodically by the MEP at the generator side, are
interleaved with the test data. The DMR frames, returned by the MEP at the
responder side with two additional timestamps, provide the one-way and/or
round-trip delay measurements.
Y.1564 MAC Swap Loopback Test

When the responder device has limited capabilities i.e. no service MEP is defined
or the test frames cannot be identified and/or counted by the MEP, there is an

alternative form of the responder – MAC swap loopback. Only bidirectional

(round-trip) measurements are supported in this case.
This test is supported over point-to-point services where MEPs are
preconfigured at the generator side and a MAC swap loopback is activated at the
responder side.
Generator Responder
Test MAC Swap

Frames Test Frames, Loopback
DMMs, LMMs, DMRs, LMRs
Policer
PSN
Policer
Ethernet Down Ethernet Ethernet Ethernet
Port MEP Port Port Port
Figure 11-34. Y.1564 Test with MAC Swap
The Y.1564 MAC swap loopback test is performed as follows:

1. At the generator side, the source transmits test frames at specified data
rate (different rates are used during different steps of the test).
2. DMM and LMM frames, transmitted periodically by the MEP at the generator
side, are interleaved with the test data.
3. The responder loops back all the frames (the test frames as well as the OAM
frames).
4. When the generator receives the looped DMM and LMM frames it responds
by sending DMR and LMR frames, respectively.
5. The responder loops back the DMRs and LMRs received from the generator.
6. Round-trip loss is measured by the sum of the LMR frame count and the
local count at the generator ingress.
7. Round-trip delay is measured by the DMR frame timestamps divided by two.
Note In the case of a MAC swap loopback responder, the DMR timestamps include the
time spent by the packet in the responder, therefore the round-trip delay
measurements are less accurate.
Y.1564 Launching Loopback Test

When Launching Loopback functionality (LLF) is enabled on a MEP, the
responder at the MEP level is used in the Y.1564 test. There is no need to define
a Y.1564 responder especially for the Y.1564 test.
The Y.1564 Launching Loopback test is performed as follows:
1. Enable the responder at MEP level.
2. A generator having profile with responder type MEF4622, sends LLMs to
responder. Some LMMs request status of LL; others request to activate or
deactivate loopback.

3. Upon receiving the LLM, the responder identifies the port, VLAN tags, and
source MAC address of the generator.
4. The Responder returns an LLR.
5. If a reply is received, the Generator sends an LL Activate Request.
Down MEP
Depending on the specific implementation, a single MEP per EVC, or a separate
MEP per single or multiple EVC.CoS is required to provision the test. In all cases,
the service is supported with ‘regular’ and aggregate policer. In case of a single
MEP, the Rx flow classification can be VLAN or Outer VLAN. In case of multiple
MEPs, all the MEPs must belong to the same MA, and the Rx flow classification
can only be VLAN + p-bit.
Up MEP
For multipoint-to-multipoint (E-LAN) services, the Y.1564 testing is performed
over an Up MEP, for either a single Cos (EVC) or multi CoS (EVC) service. The
testing frames are transmitted into the bridge, and the VLAN tag value of the
test traffic is defined by the Rx flow classification. In both cases, the service is
supported with ‘regular’ and aggregate policer.
Generator
Test
Frames
BP
Tx Flow
Policer
BP Bridge BP
Rx Flow
Ethernet
Up MEP SVI
Port
Figure 11-35. EVC: Single CoS and Single Up MEP
Running Test on MEP with No Configured Services

The Y.1564 profile supports the auto-cos-completion option, which enables
running the Y.1564 test on a MEP without preconfiguration of services on some
or all of the CoS p-bits of the MEP. Use of this option requires you to explicitly
configure the p-bit in the MEP on which the test is to be run.
The auto-cos-completion and p-bit options should be configured in both the
generator and responder.
Test Procedures
This section describes Y.1564 test procedures and success criteria.
Stepped CIR Test

Transmission rate is according to the configured steps in percentage of CIR. For
example, 25% of CIR, 50% of CIR, 75% of CIR and CIR.
Success criteria –FLR, FTD, and FDV are within SAC limits.

Color-Blind EIR Test

Transmission rate is equal to CIR + EIR.
Success criteria – 0.99 × CIR (1-FLR) ≤ IR ≤ 1.01 × (CIR + EIR)
Color-Blind Traffic Policing Test

Transmission rate is set as follows:
• If EIR ≥ 20% of CIR, Tx rate is set to: CIR + 125% of EIR
• If EIR < 20% of CIR, Tx rate is set to: 125% of CIR + EIR
Success criteria – 0.99 × CIR (1-FLR) ≤ IR ≤ 1.01 × (CIR + EIR)
Color-Aware and Color-Blind CBS Test

Based on test case 36 in MEF 19.
Objective: To form the transmission pattern shown in the following diagram for
the duration of the test.
rate
1.1CBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-36. Transmission Pattern (CBS Test)
This can be realized by utilizing two generators:

• First generator (G1) should transmit at CIR for ~200 msec, turn off for
100 msec, and start over.
Note If (8 × CBS/CIR) > 90 msec, the transmission off period should be floor(9 ×
CBS/CIR) instead of 100 msec.
• Second generator (G2) should inject a burst of length 110% CBS at maximum
rate every 300 msec.
Note If (8f × CBS/CIR) > 90 msec, the burst should be transmitted every floor (9 ×
CBS/CIR) + 200 msec instead of every 300 msec.
Preparation:
• Set EIR = 0 and EBS = 0 for the duration of the test.
• Stop DMM transmission for the duration of the test.

• Transmit LMM once at the beginning of the test (when the generators are
off) and once at the end of the test (when the generators are off).
Procedure:
• G1 transmits green C frames at CIR.
 C = ceiling (200 msec × CIR/bitsInFrame)
where
bitsInFrame = the size of the test frame in bits
• G2 transmits green B frames at maximum rate (1G or 10G).
 B = ceiling (1.1 × CBS/frameLength)
where
frameLength = the size of the test frame in bytes
• The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
• For color-aware test – 0.99 × number of cycles × (C + N) × (1-FLR) ≤ number
of green frames
• For color-blind test – 0.99 × number of cycles × (C + N) × (1-FLR) ≤ total
number of frames
C = number of frames at CIR per cycle, defined above
N = number of frames in CBS w/o excess = floor (CBS/frameLength)
Where:
Color-Aware EBS Test

rate
1.1EBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-37. Transmission Pattern (Color-Aware EBS Test)

• First generator (G1) should transmit at CIR for ~200 msec, turn off for
Note If (8 × EBS/EIR) > 270 msec, the transmission off period should be floor (9 ×
EBS/EIR) – 200 msec instead of 100 msec.
• Second generator (G2) should inject a burst of length 110% (EBS) at

maximum rate every 300 msec.
Note If (8 × EBS/EIR) > 270 msec, the burst should be transmitted every floor(9 ×
EBS/EIR) instead of every 300 msec.
Preparation:
Procedure:
• G1 transmits green C frames at CIR.
 C = ceiling (200 msec × CIR/bitsInFrame)
where
bitsInFrame = test frame size in bits
• G2 transmits yellow B frames at maximum rate (1G or 10G).
 B = ceiling (1.1 × EBS/frameLength)
where
frameLength = test frame size in bytes
• The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 × number of cycles × C × (1-FLR) ≤ total number of frames
C = ceiling (200 msec × CIR/bitsInFrame)
Color-Blind EBS Test


rate
1.1(CBS+EBS)
PHY
CIR+EIR
100 200 300 400 500 600 700 time [ms]
Figure 11-38. Transmission Pattern (Color-Blind EBS Test)

• First generator (G1) should transmit at CIR+EIR for ~200 msec, turn off for
Note T = max(CBS/CIR, EBS/EIR); If (8 × T) > 90 msec, the transmission off period

should be floor(9 × T) instead of 100 msec.
• Second generator (G2) should inject a burst of length 110% (CBS+EBS) at

maximum rate every 300 msec.
Note T = max(CBS/CIR, EBS/EIR); If (8 × T) > 90 msec, the burst is transmitted every

floor(9 × T) + 200 msec instead of every 300 msec.
Preparation:
Procedure:
• G1 transmits E frames at (CIR+EIR).
 E = ceiling (200 msec × (CIR+EIR)/bitsInFrame)
where
bitsInFrame = test frame size in bits
• G2 transmits B frames at maximum rate (1G or 10G).
 B = ceiling (1.1 × (CBS+EBS)/frameLength)
where
frameLength = test frame size in bytes
• The number of EIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 × number of cycles × (C + N) × (1-FLR) ≤ total number of frames
C = ceiling (200 msec × CIR/bitsInFrame)


Where:
Performance Test
Transmission rate is equal to CIR.
Success criteria – FLR, FTD, FDV, and Availability are within SAC limits.
Configuring Y.1564 Test

Y.1564 test configuration procedure includes the following steps, detailed in this
section:
1. Add and configure a Y.1564 test profile in the generator and responder
devices.
2. Add, configure, and activate a Y.1564 test responder.
3. Add, configure, and activate a Y.1564 test generator.
Note For the Y.1564 test – Service MEP case, in devices with OAM MEP configured
with MEF46 Latching Loopback, there is no need to add a Y.1564 responder.
Adding Y.1564 Test Profile

You can define up to 16 Y.1564 test profiles for ETX203AX, ETX203AM, and
ETX205A, and up to 64 for ETX220A to be applied to the generator and
responder to ensure the desired test functionality.
The test profiles are defined at the EVC level, and can also contain profiles at
the EVC.Cos (P-bit) level with frame size and threshold definitions. Any EVC.Cos
configuration overrides the EVC configuration. This enables the definition of
different frame sizes and thresholds according to P-bit.
Note The DMM frame size in the Y.1564 test is set according to the frame size
configured for the test profile, rather than according to the dest NE
data-tlv-length configuration.
 To add and configure a Y.1564 test profile:

1. Navigate to config>test>y1564.
2. Define a Y.1564 test profile and assign a name to it: profile <profile-name>
The system switches to the context of the profile
(config>test>y1564>profile<profile-name>).
Note no profile <profile-name> deletes the Y.1564 test profile.

Specifying whether OAM CFM auto-cos-completion Use of auto-cos-completion

services should be automatically no auto-cos-completion requires you to explicitly
created for tested p-bit values configure the p-bit command
for the test (see parameter
description below).
Specifying whether to include or burst-tests [cbs] [ebs] You can enter the command
exclude the CBS and EBS sub- with one or both parameters.
tests (burst tests) in the To specify not to include any
configuration phase burst tests in the configuration
phase, enter: no burst-tests.
Setting the number of steps and cir-steps s1 <s1-percent> <s1-percent> – transmission

their transmission rate in the CIR [s2 <s2-percent>] [s3 <s3-percent>] rate, as percentage of CIR, at
subtest [s4 <s4-percent>] the first step of the CIR subtest
(1–100)
rate, as percentage of CIR, at
the second step of the CIR
subtest (1–100)
the third step of the CIR
subtest (1–100)
the fourth step of the CIR
subtest (1–100)
Note: You can define fewer
than four steps as long as the
last step is 100%.
Setting the color mode used for color-aware

the test no color-aware
Defining the duration of the configuration-duration <seconds> Possible values: 18–360

configuration test for each P-bit seconds
Setting the direction in which direction {unidirectional | Default: bidirectional

the test is performed bidirectional}
Defining EtherType of the test ethernet-type <hex-number> Note: The EtherType

frames configuration is only applicable
for the Y.1564 generator. It is
not applicable for the
responder, as it loops all test
frames that it receives from
the generator, regardless of
their EtherType.

Defining test frame size frame-size {64 | 128 | 256 | 512 | Range for custom bytes:
1024 | 1280 | 1518 | custom <bytes>} ETX220A: 64–9,600 (jumbo
frames)
All other devices: 64–2000
Setting the source MAC address multiple-sa-mac Relevant for ETX220A only.
in test frames multiple-sa-mac base The source MAC addresses of
(for Y.1564 over LAG) <first-mac-address> generated test frames are
no multiple-sa-mac cyclically selected from a block
of 32 consecutive MAC
addresses beginning at default
address 0x0020D2000100 or
at configured base address.
base - the start of a block of
MACs to be used as the source
address in test frames.
Must be a multiple of 32.
Example: multiple-sa-mac base
0x000012345600
Setting the one-way service one-way-thresholds flr <ppm> ftd flr – unidirectional Frame Loss
acceptance criteria <μs> fdv <μs> availability Ratio, measured in 1E-6 units
<percent/100> ftd – unidirectional Frame
Transfer Delay, measured in
microseconds
fdv – unidirectional Frame
Delay Variation, measured in
microseconds
availability – unidirectional
availability, measured in
hundredths of percent units
order to define 89.3%)
Creating, modifying, or deleting p-bit <0..7> The P-bit test profile allows
a Y.1564 test P-bit profile configuring separate frame
sizes and thresholds for
specific P-bits. The rest of the
P-bits are tested using the
general profile.
See P-bit configuration details
below.
Type no p-bit <0..7> to delete
a specific test P-bit profile.
Defining the duration of the performance-duration minutes Possible values: 1–7200

performance test, in minutes minutes

Defining the convention of the rate-convention <data-rate | The convention of the rate
rate measurements in the line-rate> measurements section in the
Y.1564 test report Y.1564 test report is
determined by the option that
you select:
• data rate – section title is IR
[Mbps].
• line rate – section title is
ULR [Mbps].
Note: Configuring
rate-convention only changes
the title in the generated
Y.1564 test report according to
your selection (IR for data-rate;
ULR for line-rate). It does not
change the values of the
measurements in the report.
Therefore, after changing
rate-convention in the profile,
you must run the Y.1564 test
again to display the
measurements in the newly
selected rate-convention.
Defining the type of responder responder-type {y1564 | mac-swap | See Operation section.
that receives the test and OAM mef46-ll}
frames from the generator in
the Y.1564 test: regular
responder, MEF46 Latching
Loopback responder, or MAC
swap responder.
Setting the round-trip service round-trip-thresholds flr <ppm> ftd flr – bidirectional Frame Loss
acceptance criteria <μs> fdv <μs> availability <availability> Ratio, measured in 1E-6 units
ftd – bidirectional Frame
microseconds
fdv – bidirectional Frame Delay
Variation, measured in
microseconds
availability – bidirectional
Setting the scope of the test: scope [configuration] [performance] You can enter the command
configuration test, performance with one or both parameters
test, or both To specify with no scope
parameters, enter: no scope

Specifying whether to apply traffic-policing This command affects the

traffic policing no traffic-policing following, according to which
side:
• Generator side – including
or excluding the traffic
policing subtest from the
configuration phase
• Responder side – passing or
not passing the data
through the responder
policer
Specifying whether user traffic is user-traffic-blocked

to be blocked/allowed during the no user-traffic-blocked
test
The following P-bit test profile parameters can be configured at the p-bit level in
the config>test>y1564>profile(profile-name)>p-bit<value># prompt.
Defining test frame size frame-size {64 | 128 | 256 | 512 | Range for custom bytes:
1024 | 1280 | 1518 | custom <bytes>} ETX220A: 64–9,600 (jumbo
frames)
All other devices: 64–2000
Setting the one-way service one-way-thresholds flr <ppm> ftd flr – service acceptance criteria
acceptance criteria <μs> fdv <μs> availability <availability> for unidirectional Frame Loss
Ratio, measured in 1E-6 units
ftd – service acceptance
criteria for unidirectional Frame
microseconds
fdv – service acceptance
criteria for unidirectional Frame
microseconds
availability – service acceptance
criteria for unidirectional

Setting the round-trip service round-trip-thresholds flr <ppm> ftd flr – service acceptance criteria
acceptance criteria <μs> fdv <μs> availability <availability> for bidirectional Frame Loss
Ratio, measured in 1E-6 units
ftd – service acceptance
criteria for bidirectional Frame
microseconds
fdv – service acceptance
criteria for bidirectional Frame
microseconds
availability – service acceptance
criteria for bidirectional
Adding Y.1564 Responder
Note For the Y.1564 test - Service MEP case, in devices with OAM MEP configured with
MEF46 Latching Loopback, there is no need to add a Y.1564 responder.
You can define up to 20 Y.1564 test responders for ETX203AX, ETX203AM,

and ETX205A, and up to 64 for ETX220A, when each OAM MA includes eight
services (p-bits). These 20/64 responders can be all EVC, all EVC.CoS, or any
combination of EVCs and EVC.CoSs. All the responders can be activated
simultaneously.
 To add and configure Y.1564 responder:

2. Define a Y.1564 test responder and assign a name to it:
responder<responder-name>
The system switches to the context of the responder
(config>test>y1564>responder<responder-name>).
Note no responder <responder-name> deletes the Y.1564 responder.
Activating or deactivating the activate

test at the responder side no activate

Defining the service to be tested bind <md <id> ma <id> [p-bit <0..7>] md – the maintenance domain
no bind <md <id> ma <id> to which the service belongs
(1–65535)
ma – the maintenance
association to which the
service belongs (1–65535)
p-bit – the specific P-bits to be
tested, or all preconfigured
P-bits if none are specified
no bind md <id> ma <id>
removes responder association
with the service.
When enabling
auto-cos-completion, it is
mandatory to explicitly
configure the normally optional
p-bit command.
Defining the service to be tested bind flow <flow-name> Mutual exclusion with the other
no bind flow <flow-name> bind formats.
flow – the multi-CoS flow that
carries the service OR a single-
CoS flow that is part of the
service.
Possible values: Variable length
string, up to 32 characters.
A corresponding flow must
already exist in the RAD flow
table.
no bind removes responder
association with the service.
Defining the service to be tested bind service <service-name> Mutual exclusion with the other
{ethernet} <port-index> bind formats
bind service <service-name> {lag | pcs service – the name of the
| logical-mac | svi} <port-number> tested service. A flow
bind service <service-name> corresponding to service name,
bridge-port <bridge-number> port must already exist in the
<port-number> RAD flow table.
bind service <service-name> Possible values: Variable length

etp <etp-name> string, up to 32 characters
{subscriber|transport} <port- ethernet, lag, pcs, logical-mac,
number> svi, bridge-port, etp subscriber,
no bind service <service-name> etp transport – the port over
which the service is tested
no bind removes responder

Setting the local MAC address local-mac mac <mac-address> Note: Command available only
used for the multipoint test no local-mac when responder is bound to a
flow.
mac – the MAC address that
the responder uses for E-LAN
and E-Tree tests
Default value: 0x000000
Setting the destination MAC destination mac <mac-address> mac – a configurable MAC
address or remote MEP number destination remote-mep <rmep-id> address that identifies the
generator side
Note: When there is more than
one generator on a certain
E-LAN service, each generator
has a unique remote MAC.
remote-mep – identifier of a
remote MEP at the generator
side, towards which the test is
conducted.
Note: You can disassociate the
destination remote MEP from
the responder by entering
destination remote-mep 0 (and
not no destination).
Assigning a test profile to the test-profile <profile-name>

responder
Displaying the Y.1564 test show status See Viewing Test Status
status (Responder Side)
Viewing Test Status (Responder Side)
 To display the test status (responder side):

• In the config>test>y1564>responder<responder-name># prompt, enter
show status.
see Table 11-19.
ETX-2>config>test>y1564>responder(1)# show status
MEP Service P-BIT

21 1 1
22 1 3
23 1 5

Table 11-19. Y.1564 Test Status (Responder Side)
Status Current status of the test (responder):

Idle – Test has been configured and has not yet been run.
Ready – Test is ready to run.
In progress – Test is currently running.
MEP Identifier of the MEP that is associated with the responder and
specific P-bit
Service Identifier of the service that is associated with the responder and
specific P-bit
Possible values: 1–8 or —
P-BIT P-bit that is included in the tested service

Adding Y.1564 Generator

You can define up to eight Y.1564 test generators for ETX203AX, ETX203AM,
and ETX205A, and up to 64 for ETX220A, each with up to eight p-bits. These
eight/64 generators can be all EVC, all EVC.CoS, or any combination of EVCs and
EVC.CoSs. All the generators can be activated simultaneously. You can activate
generators on up to eight p-bits simultaneously (a p-bit is equivalent to an OAM
MEP service).
 To add and configure Y.1564 generator:

2. Define a Y.1564 test generator and assign a name to it:
generator<generator-name>
The system switches to the context of the generator
(config>test>y1564>generator<generator-name>).
Note no generator<generator-name> deletes the Y.1564 generator.
Activating or deactivating the activate

test at the generator side no activate

Defining the service to be tested bind md <id> ma <id> [p-bit <0..7>] md – maintenance domain to
no bind md <id> ma <id> which the service belongs (1–
65535)
ma – maintenance association
to which the service belongs
(1–65535)
p-bit – specific P-bits to be
no bind md <id> ma <id>
removes generator association
with the service.
When enabling
auto-cos-completion, it is
mandatory to explicitly
configure the normally optional
p-bit command.
Defining the service to be tested bind flow <flow-name> [multi-cos] Mutual exclusion with the other
[p-bit <0..7>] bind formats; if the optional
no bind flow <flow-name> multi-cos attribute does not
exist, several bind commands
with different flow names can
be configured.
flow – the multi-CoS flow that
carries the service OR a single-
CoS flow that is part of the
service. A corresponding flow
must already exist in the RAD
flow table.
Possible values: Variable length
string, up to 32 characters
multi-cos – indicates that the
specified flow name is a
multi-CoS flow
p-bit – specific P-bits to be
Valid only together with the
optional multi-cos attribute.
For each specified P-bit, a
corresponding CoS (rank) must
already exist in the envelope
policer of the multi-CoS flow.
no bind removes generator

Defining the service to be tested bind service <service-name> Mutual exclusion with the other
{ethernet} <port-index> bind formats
[p-bit [<0..7>]] service – the name of the
bind service <service-name> {lag | pcs tested service. A flow
| logical-mac | svi} <port-number> corresponding to service name,
[p-bit [<0..7>]] port must already exist in the
bind service <service-name> RAD flow table.
bridge-port <bridge-number> Possible values: Variable length
<port-number> [p-bit [<0..7>]] string, up to 32 characters
bind service <service-name> ethernet, lag, pcs, logical-mac,
etp <etp-name> {subscriber|transport} svi, bridge-port, etp subscriber,
<port-number> [p-bit <p-bit>] etp transport – the port over
no bind service <service-name> which the service is tested
p-bit – the specific P-bits to be
P-bits if none are specified.
For each specified P-bit, a
corresponding flow must
already exist in the RAD flow
table.
no bind removes generator
Setting the destination MAC destination mac <mac-address> mac – a configurable MAC
address or remote MEP number destination remote-mep <rmep-id> address that identifies the
responder side
Note: When there is more than
one responder on a certain E-
LAN service, each reponder has
a unique remote MAC.
remote-mep – identifier of a
remote MEP at the responder
side, towards which the test is
conducted
Note: Destination remote MEP
can be disassociated from the
generator by entering
destination remote-mep 0 (and
not no destination).

Assigning policer to test policer <p-bit> bandwidth If a policer is defined for the
[cir <cir-value>] [cbs <cbs-value>] test, then the test is
[eir <eir-value>] [ebs <ebs-value>] performed according to the
[compensation <compensation-value>] test policer, rather than
policer <p-bit> profile according to the associated
<policer-profile-name> flow policer.
p-bit – CoS to which the
configuration applies
Possible values: 0..7
cir – committed information
rate
cbs – committed burst size
eir – excessive information rate
ebs – excessive burst size
compensation – extra bytes
added to frame size to take
into account Layer-1 overhead
(preamble and IFG) in the
network and the overhead for
the added VLAN header.
Possible values: 0..63
profile – an optional
predefined policer profile to be
used in the test
Note: The option to define a
test policer is useful if there is
no flow policer, or the flow
policer has different limits than
you wish to use for the test.
Assigning a test profile to the test-profile <profile-name>

generator
Displaying the status of the show mef46-ll-status See Viewing MEF46 Latching
MEF46 Latching Loopback Loopback Generator Status..
generator
Displaying the Y.1564 test show status See Viewing Test Status
status (Generator Side).
Displaying the test results and show report <summary | detailed> See Viewing Test Results.
measurements
Viewing MEF46 Latching Loopback Generator Status
 To display the MEF46 LL generator status:

• In the config>test>y1564>generator<generator-name># prompt, enter show
mef46-ll-status.

see Table 11-21.
ETX205A>config>test>y1564>generator(1)# show mef46-ll-status
Tx LLMs : 3
Rx LLRs : 3
Rx Autonomous LLRs : 0
Last Received LLR

---------------------------------------------------------------
--------------
Flags : Status : Inactive Direction :
NA Unrecognized TLV : No
Response Code : No Error
ETX205A >config>test>y1564>generator(1)#
Table 11-20. MEF46 Latching Loopback Generator Status
Displayed
Tx LLMs Number of LLM PDUs sent by the LL controller
Rx LLRs Number of LLR PDUs received by the LL controller
Rx Autonomous LLRs Number of autonomous LLR PDUs received by the LL controller
Status Latching Loopback status:

Possible values: Inactive, Active
Direction Latching Loopback direction:

Possible values: NA, Internal, External
Unrecognized TLV Indicates whether one or more of the included TLVs were not
recognized
Possible values: No, Yes
Response Code Response code in the last received LLR PDU

Possible values: No Error, Malformed Request, Max Session
Exceeded, Resource Unavailable, Already Active, Already Inactive,
Unsupported, Wrong MP, Timeout, Prohibited, Unknown
Message Type, Unknown Error
Viewing Test Status (Generator Side)
 To display the test status (generator side):

status.
see Table 11-21.
ETX-2>config>test>y1564>generator(1)# show status
Time Remaining : 00:00:24

Test Phase : Performance
Associated EVC
---------------------------------------------------------------
Inner VLAN : --- Outer VLAN : 20
MEP Service P-BIT Tx Flow Rx Flow

---------------------------------------------------------------
1 2 1 flow2_3to1
flow2_1to3
MEP Service P-BIT

CIR EIR BWP In Use
(Mbps) (Mbps)
---------------------------------------------------------------
--------------
1 2 1 37.5 75.0 Flow
Table 11-21. Y.1564 Test Status (Generator Side)
Displayed
Status Current Test status (generator):

Idle – Test has been configured and has not yet been run.
In Progress – Test is currently running.
Passed – Test has been completed successfully.
Failed – Test has failed.
User Aborted – Test has been stopped by the operator.
Time Remaining Time remaining until the end of the test

Displayed when Status is In Progress
Test Phase Current phase of the test

Possible values: Configuration, Performance
Displayed when Status is In Progress
Inner VLAN Value of the inner VLAN (usually C-Tag)

If there is no inner tag, the string “—“ is displayed.
Displayed when Status is other than Idle
Outer VLAN Value of the outer VLAN (usually S-Tag)

If there is no outer tag, the string “—“ is displayed.
Displayed when Status is other than Idle.
MEP Identifier of the MEP that is associated with the P-bit


Displayed
Service Identifier of the service that is associated with the P-bit

Possible values: 1–8 or —
Displayed when Status is other than Idle.
P-BIT P-bit that corresponds to the tested service

Displayed when Status is other than Idle and when EVC is untagged
Tx Flow Egress flow corresponding to the MEP and P-bit

Rx Flow Ingress flow corresponding to the MEP and P-bit

CIR (Mbps) Provisioned CIR of the egress flow

EIR (Mbps) Provisioned EIR of the egress flow

BWP in use Origin of the associated bandwidth profile for the EVc.CoS
Possible values: Test, Flow
Viewing Test Results

When displaying the Y.1564 test results, you can choose to generate a test
summary or a detailed test report.
Note In detailed test report, in case a step is Not Applicable, all step parameters
display value --- and not 0.
 To display the summary test results:

report summary.
The summary report screen is displayed. For information on the test
report summary counters, see the following table.
ETX-220A>config>test>y1564>generator(1)# show report summary
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-20-D2-54-11-92
Source MAC Address : 00-20-d2-f1-d1-66
Inner Tag : --- Outer Tag : 1
P-bit/s : 0
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance
Profile Name : 1

Start Date & Time : 2016-07-24 13:04:44

End Date & Time : 2016-07-24 13:05:05
Total Duration : 00:00:21
Configuration Test Report

-----------------------------------------------------------------------------
P-bit : 0
Duration (Sec) : 20
Result : Failed CIR,EIR,Policing
Test Result Tx Rate IR FLR FTD FDV

(Mbps) (Mbps) (ms)
(ms)
CIR Test
-----------------------------------------------------------------------------
Step#1 Failed FLR 25.0 0.0 1.0E+00 0.004 0.0
Step#2 Failed FLR 50.0 0.0 1.0E+00 0.004 0.0
Step#3 Failed FLR 75.0 0.0 1.0E+00 0.004 0.0
Step#4 Failed FLR 100.0 0.0 1.0E+00 0.004 0.0
EIR Test
-----------------------------------------------------------------------------
Failed IR 101.0 0.0 1.0E+00 0.004 0.0
Traffic Policing Test

-----------------------------------------------------------------------------
Failed IR 126.0 0.0 0.0E+00 0.0 0.0
CBS Test
-----------------------------------------------------------------------------
Passed
EBS Test
-----------------------------------------------------------------------------
Passed
Performance Test Report

-----------------------------------------------------------------------------
Duration (Min) : 1
Result : Failed P-bit/s 0
P-bit Result Tx Rate

-----------------------------------------------------------------------------
0 Failed IR,Avail. 100.0
IR (Mbps)
-----------------------------------------------------------------------------
P-bit IR FLR FTD FDV Avail
(ms) (ms) (%)
-----------------------------------------------------------------------------
0 0.0 0.0E+00 0.0 0.0 1.66

Table 11-22. Y.1564 Header and Test Counters (Summary)
Counter Description
Name Name of the tested service
Destination MAC Address MAC address of the remote MEP
Source MAC Address MAC address of the local MEP
Inner Tag Value of the inner VLAN
Outer Tag Value of the outer VLAN
P-bit/s List of the P-bit values that were actually tested
Scope Scope of the test: configuration test, performance test, or both

phases
Possible values: Configuration, Performance, Configuration +
Performance
Profile Name Profile used in the test
Start Date & Time Date and time at the last test activation
End Date & Time Date and time when the last test ended (regardless of the end
result passed/failed/aborted)
Total Duration Duration of the last test
Overall Result Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Configuration Test report (summary)
P-bit
Duration Duration of the configuration test (in seconds)
Result Result of the last configuration test for the specific P-bit and if it
failed, the reason for failure
Possible Result values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Possible reasons for failure: CIR, EIR, Policing, and/or CBS test
Test Name of the sub-test: CIR Test, EIR Test, Traffic Policing Test, CBS
Test, EBS Test
Result Result of the sub-test

Possible Result values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Reason for failure If sub-test failed, shows the reason(s) for failure.
Possible reasons for failure:
• CIR Test – FLR, FTD, or FDV
• EIR Test – IR
• Traffic Policing Test – IR
• CBS Test – Burst size
• EBS Test – Burst size

Counter Description
Tx Rate (Mbps) Transmission rate to which the generator is configured in the

subtest
IR (Mbps) Average calculated Information Rate
FLR Calculated Frame Loss Ratio
FTD (ms) Average calculated Frame Transfer Delay
FDV (ms) Average calculated Frame Delay Variation
Performance test report (summary)
Duration Duration of the performance test (in minutes)
Result Performance test result summary for all CoS (p-bits)

Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
If test failed, displays the failed CoS (p-bit(s))
P-bit P-bit (sub-test) that is included in the tested service
Result Result of the sub-test for the CoS (p-bit)

Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Reason for failure If sub-test failed, displays the reason for failure: FLR, FTD, or FDV
Tx Rate (Mbps) Transmission rate to which the generator is configured in the

subtest
IR (Mbps) Average calculated Information Rate
FLR Calculated Frame Loss Ratio
FTD (ms) Average calculated Frame Transfer Delay
FDV (ms) Average calculated Frame Delay Variation
Avail (%) Percentage of available time
 To display the detailed test results:

report detailed.
The detailed report screen is displayed. For information on the detailed
test report counters, see Table 11-5.
ETX-2>config>test>y1564>generator(1)# show report detailed
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-20-D2-50-95-A3
Source MAC Address : 00-20-D2-54-EF-EB
Inner Tag : --- Outer Tag : 20
P-bit/s : 1
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance

Profile Name : 1
Start Date & Time : 2017-05-21 13:04:44
End Date & Time : 2017-05-21 13:05:05
Total Duration : 00:00:21
Configuration Test Report

-----------------------------------------------------------------------------
P-bit : 0
Duration (Sec) : 20
Result : Failed CIR,EIR,Policing
CIR Test
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- ----
Tx Rate (Mbps) 25.0 --- 75.0 100.0
IR - Min (Mbps) 0.0 --- 0.0 0.0
IR - Mean (Mbps) 0.0 --- 0.0 0.0
IR - Max (Mbps) 0.0 --- 0.0 0.0
Tx Count 6101 --- 18301 24391
Rx Count 0 --- 0 0
FL Count 6101 --- 18301 24391
FLR 1.0E+00 --- 1.0E+00 1.0E+00 3.0E-04
FTD - Min (ms) 0.004 --- 0.004 0.004
FTD - Mean (ms) 0.004 --- 0.004 0.004 26.000
FTD - Max (ms) 0.004 --- 0.004 0.004
FTD - Std (ms) 0.0 --- 0.0 0.0
FDV - Mean (ms) 0.0 --- 0.0 0.0 11.000
FDV - Max (ms) 0.0 --- 0.0 0.0
---------------- -------- -------- -------- -------- ----
Result Failed Not Applicable Failed Failed
EIR Test & Traffic Policing Test
-----------------------------------------------------------------------------
EIR Policing Thr
---------------- -------- -------- --------
Tx Rate (Mbps) 101.0 126.0
IR - Min (Mbps) 0.0 0.0
IR - Mean (Mbps) 0.0 0.0 0.0 - 10.128
IR - Max (Mbps) 0.0 0.0
Tx Count 24633 0
Rx Count 0 0
FL Count 24633 0
FLR 1.0E+00 0.0E+00
FTD - Min (ms) 0.004 0.0
FTD - Mean (ms) 0.004 0.0
FTD - Max (ms) 0.004 0.0
FTD - Std (ms) 0.0 0.0
FDV - Mean (ms) 0.0 0.0
FDV - Max (ms) 0.0 0.0
---------------- -------- -------- --------
Result Failed Failed
Burst Tests
-----------------------------------------------------------------------------
Parameter CBS EBS
--------------------------------- -------- --------
Number of Cycles 24 24
Frames per Cycle 70 140
Minimum Expected Frames 105881 105730
Actual Received Frames 106733 159260
--------------------------------- -------- --------
Result Passed Passed

Performance Test Report

-----------------------------------------------------------------------------
Duration (Min) : 1
Result : Failed P-bit/s 0
P-bit Result Tx Rate

-----------------------------------------------------------------------------
0 Failed IR,Avail. 100.0
IR (Mbps)
-----------------------------------------------------------------------------
P-bit Min Mean Max
-----------------------------------------------------------------------------
0 0.0 0.0 0.0
FL
-----------------------------------------------------------------------------
P-bit Count FLR Thr
-----------------------------------------------------------------------------
0 0 0.0E+00 3.0E-04
FTD (ms)
-----------------------------------------------------------------------------
P-bit Min Max Std Mean Thr
(ms) (ms) (ms) (ms)
-----------------------------------------------------------------------------
0 0.0 0.0 0.0 0.0 26.000
FDV (ms)
-----------------------------------------------------------------------------
P-bit Max Mean Thr
(ms) (ms)
-----------------------------------------------------------------------------
0 0.0 0.0 11.000
Availability
-----------------------------------------------------------------------------
P-bit UAS % Thr (%)
-----------------------------------------------------------------------------
0 59 1.66 99.90
Table 11-23. Y.1564 Test Counters (Detailed)
Counter Description
Tx Rate (Mbps) The transmission rate to which the generator is configured in the
subtest
IR – Min (Mbps) The minimum measured Information Rate
IR – Mean (Mbps) The average calculated Information Rate

Note: For EIR and Traffic Policing tests, displays under Thr column,
the service acceptance criteria (SAC).
IR – Max (Mbps) The maximum measured Information Rate
Tx Count Number of transmitted frames
Rx Count Number of received frames
FL Count The number of lost frames
FLR The calculated Frame Loss Ratio

Counter Description
FTD – Min (ms) The minimum measured Frame Transfer Delay
FTD – Mean (ms) The average calculated Frame Transfer Delay
FTD – Max (ms) The maximum measured Frame Transfer Delay
FTD – Std (ms) The calculated standard deviation of the Frame Transfer Delay
FDV – Mean (ms) The average calculated Frame Delay Variation
FDV – Max (ms) The maximum calculated Frame Delay Variation
UAS The number of unavailable seconds
% The percentage of available time
Availability Thr The Availability service acceptance criteria for the reported P-bit
Burst Tests
Number of Cycles The number of burst transmission cycles
Frames per Cycle The number of frames in a single burst transmission cycle
Minimum The minimum total number of frames expected to be received in the

Expected Frames sub-test
Actual Received The actual total number of frames received during the sub-test
Frames
Examples
This example shows how to create a Y.1564 test generator over a MEP located
between two Ethernet ports and bound to one of them. The Y.1564 test
(Service MEP case) is run over an OAM (CFM) service defined on P-bit 0. The test
in this example is run on a network port, but Y.1564 tests can also be run on
user ports.
 To configure Y.1564 test generator over a MEP in ETX203AX or ETX205A:

1. Configure a policer profile.
2. Configure a VLAN-type classifier profile.
3. Configure two flows from Ethernet port 1 to port 4 and vice versa.
4. Define a MEP bound to port 1.
5. Configure MEP service with LMMs and DMMs sent over P-bit 0.
6. Configure a Y.1564 test profile.
7. Add a Y.1564 generator, bind it to the relevant MD, MA, P-bit, and test
profile.

Generator
Test
Frames
Flow 1 P-bit 0
Policer
Flow 2
Ethernet MEP Ethernet

Port 1 Port 4
Figure 11-39. Y.1564 Test Generator over Down MEP
************************Defining_Policer_Profile*****************************
exit all
config qos policer-profile v10 bandwidth cir 100000 cbs 10000 eir 10000 ebs
5000
#*********************************End****************************************
************************Defining_Classifier_Profile**************************
config flows classifier-profile vlan10 match-any
match vlan 10
exit all
#*********************************End****************************************
******************************Adding_Flows***********************************
configure flows flow v10_1to4
classifier vlan10
no policer
no shutdown
exit all
configure flows flow v10_4to1

classifier vlan10
policer profile v10
no shutdown
exit all
#*********************************End****************************************
ff
#**************************Defining_MEP_and_MEP_Service**********************
configure oam cfm
ccm-interval 1s
mep 1
flow uni-direction rx v10_1to4 tx v10_4to1
bind ethernet 1
remote-mep 2

dest-addr-type ccm multicast

client-md-level 6
ais
no shutdown
service 1
classification priority-bit 0
lmm-interval 100ms
dmm-interval 100ms
dest-ne 1
remote mep 2
loss single-ended
delay two-way
exit
no shutdown
exit all
#*********************************End****************************************
#*******************Configuring_Y.1564_Test_Profile_and_Generator************
config test y1564
profile 1
ethernet-type 0x22e8
frame-size 512
one-way-thresholds flr 100 ftd 13000 fdv 8000 availability 9990
round-trip-thresholds flr 200 ftd 26000 fdv 11000 availability 9990
direction bidirectional
color-blind
traffic-policing
cir-steps s1 25 s2 50 s3 75 s4 100
configuration-duration 60
rate-convention data-rate
exit
generator 1
test-profile 1
bind md 1 ma 1 p-bit 0
activate
exit all
save
#*********************************End****************************************
The following example shows the configuration of the Y.1564 test (Service MEP
case) over E-LAN service. Note that the node in the target device must be
explicitly configured with the remote MEP number.
 To run the Y.1564 test on an E-LAN service:

generator "1"
test-profile "1"
bind md 1 ma 1
destination remote-mep 1
responder "1"
test-profile "1"

bind md 1 ma 1
destination remote-mep 1
The following example shows the configuration of both the generator and
responder when the Y.1564 test runs in a device without configuring the OAM
(Internal MEP case). In this case, both generator and responder are bound to a
flow (and not to an MA or MD). Also, the destination MAC address on the
generator is configured to the responder NNI MAC.
#generator :
configure
qos
policer-profile "CIR10M-EIR20M"
bandwidth cir 9984 cbs 64000 eir 19968 ebs
64000
exit
exit
flows
classifier-profile "v100" match-any
match vlan 100
exit
classifier-profile "v1502-p3" match-any
match vlan 1502 p-bit 3
exit
flow "gd-dn"
classifier "v1502-p3"
no policer
vlan-tag pop vlan
no shutdown
exit
flow "gd-up"
classifier "v100"
policer profile "CIR10M-EIR20M"
no shutdown
exit
exit
exit
configure
test
echo "Configure Y1564"
# Configure Y1564
y1564
echo "Y1564 - Profile Configuration"
# Y1564 - Profile Configuration
profile "2"
exit
echo "Y1564 - Generator Configuration"
# Y1564 - Generator Configuration
generator "Generator1"
test-profile "2"
bind flow "gd-up"

Destination 00-20-D2-EE-1B-B7
exit
exit
exit
exit
#responder
configure
qos
policer-profile "CIR10M-EIR20M"
bandwidth cir 9984 cbs 64000 eir 19968 ebs
64000
exit
exit
flows
classifier-profile "v100" match-any
match vlan 100
exit
classifier-profile "v1502-p3" match-any
match vlan 1502 p-bit 3
exit
flow "gd-dn"
classifier "v1502-p3"
no policer
vlan-tag pop vlan
no shutdown
exit
flow "gd-up"
classifier "v100"
policer profile "CIR10M-EIR20M"
no shutdown
exit
exit
exit
configure
test
echo "Configure Y1564"
# Configure Y1564
y1564
echo "Y1564 - Profile Configuration"
# Y1564 - Profile Configuration
profile "2"
exit
echo "Y1564 - Responder Configuration"
# Y1564 - Responder Configuration
responder "Responder1"
test-profile "2"
bind flow "gd-up"
exit
exit

exit
The following example shows the configuration of the policer under the Y.1564
generator.
 To configure the policer under the Y.1564 generator:

ETX205A>config>test>y1564>generator(1)$ policer 5 bandwidth
cir 10000 cbs 32767 eir 5000 ebs 32767 compensation 20
Table 11-24 lists the messages generated by ETX-2 when a configuration error is
detected.
Message Description
Illegal frame size value Invalid test frame size for Y.1564 profile
Unidirectional measurement is not Only bidirectional measurement is supported.

supported
Illegal threshold value Invalid round-trip service acceptance criteria for Y.1564 profile
Illegal color value Invalid color mode for Y.1564 profile
Illegal traffic policing value Invalid traffic policer for Y.1564 profile
Illegal CIR step value Invalid CIR step for Y.1564 profile
Illegal configuration duration value Invalid duration of the configuration test for Y.1564 profile
Illegal performance duration value Invalid duration of the performance test for Y.1564 profile
Illegal rate convention value Invalid rate measurement convention for Y.1564 profile
Illegal P-bit value Invalid P-bit value for Y.1564 profile or generator
MD does not exist Maintenance domain selected for Y.1564 generator or

responder has not been configured yet.
MA does not exist Maintenance association selected for Y.1564 generator or

responder has not been configured yet.
Y.1564 profile does not exist (SNMP only) The configured Y.1564 test profile does not exist.
Illegal command value Invalid value for the parameter
Max number of active generators has The maximum number of Y.1564 generators (eight; 64 for
been exceeded ETX220A) has been reached and no additional generators can
be added.
Max number of active responders has The maximum number of Y.1564 responders (20; 64 for
been exceeded ETX220A) has been reached and no additional responders can
be added.
Entity cannot be added. Table entries You tried to define a 65th profile, generator, or responder.
have reached maximum.
Y.1564 profile is in use Y.1564 profile is in use and cannot be modified.

Message Description
Y.1564 profile has not been attached No Y.1564 profile has been attached to generator or responder.
Active generator cannot be changed Active Y.1564 generators cannot be modified.
Active responder cannot be changed Active Y.1564 responders cannot be modified.
MEP or service have not been found MEP or OAM service within selected MD/MA does not exist.
MEPs have different destination MAC Y.1564 Generator works opposite one remote only. In EVC.cos,
address the MEPs under the MA are opposite several remotes, and
therefore the test does not work.
The device didn't learn the remote's No CCM was received from the remote MEP and its MAC address
mac-address. was not learned. This is relevant only if remote-mep is
configured on the DestNE.
MEPs have different source MAC All MEPs under the same MA must be bound to the same port.
addresses
MEPs have different classification types MEPs within selected MD/MA have different classification types.
MEPs have different VLANs MEPs within selected MD/MA have different VLANs.
MEPs have different inner VLANs MEPs within selected MD/MA have different inner VLANs.
MEP or service are not active MEP or OAM service within selected MD/MA has not been
activated yet.
OAM CFM: Max number of remote MEP The maximum number of remote MEP elements in a line has
elements in a line has been exceeded. been reached and no additional MEP elements can be added.
OAM CFM: Max allowed number of Adding MEPs to previously configured MEPs exceeds the allowed
<512/1024> remote MEPs has been maximum number of remote MEP elements that can be
reached. configured (512/1024).
Policer profile is missing No Policer is configured on the relevant Tx flow.
I/O flow with matching CoS has not been The Y.1564 test mechanism failed to identify a MEP Tx flow with a
found P-bit, matching testing criteria.
Generator can test only one P-bit If there is only one Tx flow with the non-envelope Policer, only
one P-bit can be tested.
MEP is already under test A test is already running on this MEP.
11.9 Performance Management

ETX-2 maintains performance management (PM) statistics for selected entities in
the device. The PM statistics are collected into a file periodically, for retrieval by
RADview, for display in the RADview PM portal (refer to the RADview System
User’s Manual for further details on the PM portal). The PM file includes the
following information: buffer (kernel) memory utilization and TCA, CPU
utilization, memory utilization, flash memory utilization, and device uptime. The
PM collection process can be globally enabled or disabled for the entire device.
In addition, the statistics collection can be enabled for all entities of a specific
type, or for specific entities.
11-202 Performance Management ETX-2

Applicable Products
This feature is applicable to all ETX-2 products and to PMC in ETX205A, with the
following conditions:
• PCS ports are relevant only to ETX203AM.
• When <slot>/ is shown before a port number, it is relevant only to
ETX203AM and ETX220A.
• Scripts containing port numbers may have to be edited according to the
product port numbering.
Benefits
The PM data is useful for analyzing ETX-2 service quality. The flexible statistics
collection allows only the necessary data to be collected.
PM statistics collection is configured for the device, entity type, and specific
entities. PM statistics are collected for the following types of entities:
• Ethernet ports
• Flows
• OAM TWAMP sessions
• OAM CFM services
• OAM CFM destination NEs
• System parameters: memory usage and CPU utilization
Notes • PM statistics collection is performed only if it is enabled for the entire device,
regardless of whether it is enabled for any entity
• PM statistics are not collected for entities that are administratively disabled.
If PM statistics collection is disabled for a particular entity type, then no PM

statistics collection is done for any entity of that type, except those for which
PM statistics collection is enabled.
When PM statistics collection is enabled for all entities of the same type, then
when a new entity of that type is added the device automatically starts
collecting PM statistics for it, as soon as PM statistics maintenance (if applicable)
is enabled for the entity.
Note
If you are using the RADview PM Portal, it is recommended to enable PM
statistics collection for all relevant entities. See Examples for a script that you
can use for this purpose.
PM statistics collection is performed at user-configurable intervals of one second

to 15 minutes. A different interval can be configured for each entity type, and
for specific entities.
If different intervals are scheduled for collection at the same time, ETX-2 collects
the PM statistics starting with the interval that has the highest frequency, and
ETX-2 Performance Management 11-203

ending with the interval that has the lowest frequency. If ETX-2 has not finished
collecting the statistics for an interval when the scheduled time for another
interval arrives, the following action is taken according to whether the new
interval is the next interval, or an interval with higher frequency:
• If it is the next interval, then the next interval is canceled, and a PM record
indicating the cancellation is inserted in the PM data.
• If it is an interval with higher frequency, then ETX-2 collects the higher
frequency interval statistics and then resumes collecting the lower frequency
interval statistics. The PM data is retrieved from ETX-2 by RADview via TFTP
or SFTP. After PM data is retrieved, ETX-2 deletes the file and opens a new
one for further data.
Factory Defaults
Command Level under config Default Remarks
pm reporting pm PM statistics collection in device

is globally enabled by default.
pm-collection Specific entity level Disabled PM statistics collection for

specific entities is not explicitly
configured by default;
therefore, it is disabled until
statistics collection is enabled
for the entity type or entity.
pm-collection dest- reporting Disabled PM statistics collection for OAM

ne CFM destination NEs is not
explicitly configured by default;
therefore, it is disabled.
pm-collection eth reporting Disabled PM statistics collection for

Ethernet ports is not explicitly
pm-collection flow reporting Disabled PM statistics collection for

flows is not explicitly configured
by default; therefore, it is
disabled.
pm-collection reporting Disabled PM statistics collection for OAM

oam-cfm-service CFM services is not explicitly
pm-collection reporting Disabled PM statistics collection for

system memory usage and CPU
utilization is not explicitly

Command Level under config Default Remarks
pm-collection twamp reporting Disabled PM statistics collection for

TWAMP is not explicitly
Configuring Performance Management

You can configure PM statistics collection for the entire device via the pm
command, and for entity types via the pm-collection command, in the reporting
level. For specific entities, you can configure PM statistics collection via
pm-collection, in the specific entity level.
You can configure the device to record statistics at fixed intervals using the
pm-collection interval <seconds> command or at the close of an interval using
the pm-collection on-interval-close command. For parameters that are not
zeroed regularly, it is recommended to record statistics at fixed intervals. For
parameters zeroed at fixed intervals (interval statistics), it is recommended to
record statistics whenever an interval is about to expire, i.e. right before the
parameters are zeroed, in order to avoid losing data. This option is available for
interval statistics only.The interval parameter for the pm-collection command
can range from 1 to 900 seconds (15 minutes); however, the value must divide
evenly into 3600. Different intervals can be specified for an entity type and for
specific entities of that type, up to a supported maximum number of intervals.
For example, if the PM statistics collection interval for all flows is configured to
15 minutes, and the PM statistics collection interval for flow-1 is configured to
1 minute, the data displayed in the RADview PM portal shows flow data for
every 15 minutes, and flow-1 data for every minute. You can also collect PM
statistics on interval close.
The following shows the PM statistics collection configuration tasks, and their
corresponding commands, as well as the level of each command.
Task Level under config Command Comments
Enabling PM statistics flows > flow(<flow-name>) pm-collection PM collection can be

collection for a specific { interval <seconds> | enabled at a defined
flow on-interval-close } interval or before an
interval expires.
Type no pm-collection to
disable PM statistics
collection for the flow.
Enabling PM statistics oam > cfm > md(<md-id>) > pm-collection PM collection can be
collection for a specific ma(<ma-id>) > mep(<mep- { interval <seconds> | enabled at a defined
OAM CFM service id>) > service(<service-id>) on-interval-close } interval or before an
interval expires.
collection for the service.

Enabling PM statistics oam > cfm > md(<md-id>) > pm-collection PM collection can be
collection for a specific ma(<ma-id>) > mep(<mep- { interval <seconds> | enabled at a defined
OAM CFM destination id>) > service(<service-id>) > on-interval-close } interval or before an
NE dest-ne(<dest-ne-index>) interval expires.
collection for the
destination NE.
Enabling PM statistics port > pm-collection PM collection can be

collection for a specific ethernet(<slot>/<port-num>) { interval <seconds> | enabled at a defined
Ethernet port (other on-interval-close } interval or before an
than the management interval expires.
port) Type no pm-collection to
collection for the Ethernet
port.
Enabling PM statistics port > mng-eth pm-collection PM collection can be

collection for the { interval <seconds> | enabled at a defined
Ethernet management on-interval-close } interval or before an
port interval expires.
collection for the Ethernet
management port.
Globally enabling PM reporting pm Type no pm to disable all

statistics collection for PM statistics collection in
device ETX-2.
Note: no pm stops all PM
collection regardless of
other PM configuration;
however, it does not
change other
configurations.
It deletes any collected PM
data and PM files, as well.
Enabling PM statistics reporting pm-collection dest-ne PM collection can be

collection for OAM CFM { interval <seconds> | enabled at a defined
destination NEs on-interval-close } interval or before an
interval expires.
Type no pm-collection
dest-ne to disable PM
statistics collection for all
OAM CFM destination NEs.

Enabling PM statistics reporting pm-collection eth PM collection can be

collection for Ethernet { interval <seconds> | enabled at a defined
ports on-interval-close } interval or before an
interval expires.
Type no pm-collection eth
to disable PM statistics
collection for Ethernet
ports.
Enabling PM statistics reporting pm-collection flow PM collection can be

collection for flows { interval <seconds> | enabled at a defined
on-interval-close } interval or before an
interval expires.
Type no pm-collection flow
to disable PM statistics
collection for flows.
Enabling PM statistics reporting pm-collection PM collection can be

collection for OAM CFM oam-cfm-service enabled at a defined
services { interval <seconds> | interval or before an
on-interval-close } interval expires.
oam-cfm-service to disable
PM statistics collection for
OAM CFM services.
Enabling PM statistics reporting pm-collection system PM collection can be

collection for system { interval <seconds> | enabled at a defined
parameters on-interval-close } interval or before an
interval expires.
system to disable PM
statistics collection for
system parameters.
Enabling PM statistics reporting pm-collection twamp PM collection can be

collection for OAM { interval <seconds> | enabled at a defined
TWAMP component on-interval-close } interval or before an
interval expires.
twamp to disable PM
statistics collection for
OAM TWAMP component.
Note
PM statistics are collected for entities for which PM statistics collection is
specifically enabled in the entity level via pm-collection, even if PM statistics
collection for the entity type is disabled.

Viewing Performance Management Configuration

You can use the info detail command to view the performance management
configuration.
 To view the performance management configuration for the device and for
entity types:
2. Enter info detail | include pm to view PM-related commands in the
configuration.
 To view the performance management configuration for specific entities:

1. Navigate to the specific entity level.
2. Enter info detail | include pm to view PM-related commands in the
configuration.
Examples
 To enable PM for all relevant entities in ETX-2:
• PM statistics collection enabled for device
• PM statistics collection enabled for all relevant entities, every five minutes.
exit all
configure reporting
#**** Enable PM in device
pm
#**** Enable PM for Eth ports, collection interval=5 min
pm-collection eth interval 300
#**** Enable PM for flows, collection interval=5 min
pm-collection flow interval 300
#**** Enable PM for OAM CFM services, collection interval=5 min
pm-collection oam-cfm-service interval 300
#**** Enable PM for OAM CFM dest NEs, collection interval=5 min
pm-collection dest-ne interval 300
exit all
save
 To configure the following PM:

• PM statistics collection enabled for device.
• PM statistics collection enabled for Ethernet ports, every two minutes.
• PM statistics collection enabled for flows, every five minutes.
• PM statistics collection for Ethernet port 0/3 configured to every minute.
• PM statistics collection enabled for OAM CFM services, every 15 minutes.
• PM statistics collection enabled for OAM CFM dest NEs, every 15 minutes.
exit all
configure reporting
#**** Enable PM in device
pm

#**** Enable PM for Eth ports, collection interval=2 min

#**** Enable PM for flows, collection interval=5 min
#**** Enable PM for OAM CFM services, collection interval=15 min
#**** Enable PM for OAM CFM dest NEs, collection interval=15 min
exit all
#**** Configure PM statistics collection interval for Eth port 0/3, to 1 min
exit all
save
 To display PM configuration from above example:

ETX-2# configure reporting
ETX-2>config>reporting# info detail | include pm
pm
ETX-2>config>reporting# exit all

ETX-2>config>port>eth(0/3)# info detail | include pm
Table 11-25 lists the messages displayed by ETX-2 when a configuration error is
detected.
Message Description
Invalid interval; must divide evenly into The pm-collection command was entered with an interval value
3600 that does not divide evenly into 3600.
Cannot execute; too many different Attempt was made to configure more intervals than the
intervals supported maximum.
11.10 Detecting Problems

The LED indicators indicate errors on the hardware level.
ETX-2 Detecting Problems 11-209

LEDs
A red LED is usually an indication of a problem. Check the port that is associated
with the LED to further investigate the problem. Refer to the Operation chapter
for a description of the unit LEDs.
Alarms and Traps

Alarms serve as notification of a fault in the device, and are indicated by an
entry in the alarm and event history log, and/or an SNMP trap to a management
station. See Handling Alarms and Events for further details on alarms, events,
and traps.
Statistic Counters
Statistic counters provide information on possible abnormal behavior and
failures. You can collect statistics on the following:
• Ethernet ports
• E1/T1 ports, if applicable
• SHDSL ports, if applicable
• VDSL ports, if applicable
• Flows
• RADIUS server
• OAM CFM
For further information, refer to the relevant sections in Chapters 6 –10 and the
relevant sections in the troubleshooting chart.
You can clear the statistics for Ethernet ports, flows, and OAM services.
Statistics clearing is globally enabled by default. Once statistics are cleared from
an interval, the interval becomes “not valid”.
 To clear the statistics:

• At the device prompt, enter:
clear-statistics
The statistics for Ethernet ports, flows, and OAM services (running
counters only; not current counters) are cleared. The OAM interval
statistics are not cleared.
Note PW and E1 do not support running-statistics; therefore, clear-statistics clears

only the current statistics.
11.11 Handling Alarms and Events

An alarm is an indication of a fault in the device. An event is an occurrence in
the device that may be a fault or may be a user login, change in port status, etc.
11-210 Handling Alarms and Events ETX-2

Alarms and events can be written to the alarm and event history log. In addition
to the history log containing alarms and events, the device maintains statistics
for alarms and events in a brief log. Alarms can also be written to the active
alarm table. An SNMP trap can be sent to management stations as the result of
an alarm/event. Additionally, you can configure alarms and events to pop up on
the serial CLI terminal.
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, and source
name.
Alarms and events can be generated for any of the
following source types: system, fan, power-supply, station-
clock, recovered-clock, g82751-recovered*, g82751-
master-cl*, gnss, card, ethernet, vdsl, shdsl, pcs, sdh-
sonet, e1, t1, e3, t3, vcg, bridge, logical-mac, etp, gfp, lag,
oam-efm, oam-cfm-mep, oam-cfm-destne, eps, erp, eth-
protection, router-interface, pw, bgp, domain-clock
recovered-clock-*, domain-clock-sou*, master-clock,
smart-sfp, oam-cfm-r-mep, erp-port, ospf, ospf-neighbor,
ospf-interface, twamp-session, twamp-peer, all
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 stations for
which the traps are not masked in the SNMP manager configuration.
Alarm Soaking
ETX-2 supports alarm soaking. This means that the device does not raise an
alarm immediately upon detecting an abnormal condition (i.e. defect); only after
the abnormal condition has occurred uninterrupted for a certain amount of time
(called the rising soaking time). Similarly, the alarm is cleared only after the
abnormal condition is resolved and remains resolved for a certain amount of
time (called the falling soaking time or clear time). In this way, alarm soaking
prevents fleeting alarms, i.e. alarms that rise and fall multiple times in a short
period. Instead of sending a flood of alarms to RADview, only one initial alarm is
sent, and the final clear alarm is sent only upon stabilization of the link.
The device supports alarm soaking, provided the following requirements are met:
• The device supports configurable alarm rising and falling soaking times, as
follows:
ETX-2 Handling Alarms and Events 11-211

 Rising and falling soaking times may be configured to different values.

 The configurable soaking time range is 0 (i.e. no soaking time) to 10,000
milliseconds.
 The default rising soaking time is 2,500 milliseconds (2½ seconds);
default falling soaking time is 10,000 milliseconds (10 seconds).
 The actual soaking time may deviate by up to ½ second from the
configured value.
 The configured soaking times apply only for those entities that do have
a standard dictating a different behavior. If there is such a standard,
such as SDH/SONET and DS1, the standard is followed.
• When a defect occurs, the device must wait the rising soaking time (either
configured or dictated by a standard) before raising the alarm. An alarm is
raised only if the defect exists for the entire soaking time. If the defect is
cleared and reoccurs, the rising soaking timer must be rearmed.
• When a condition that caused an alarm is resolved, the device must wait the
falling soaking time (either configured or dictated by a standard) before
clearing the alarm. Only if the condition stays resolved for the entire soaking
time, the alarm is cleared. If the defect reoccurs, the soaking timer must be
rearmed.
Configuring Alarm and Event Properties

This section explains how to configure alarm/event properties.
Note In the commands alarm-source-attribute, alarm-source-type-attribute, and

mask-minimum-severity, the popup parameter controls popup behavior in serial
management sessions, and the vtypopup parameter controls popup behavior in
Telnet/SSH management sessions.
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.
 To configure alarm/event properties:

The config>reporting# prompt is displayed.

Configuring alarm input alarm-input <port-number> [active {high | low | If you set alarm-input to active
off}] [description <description>] state, configure alarm input’s
activation mode to one of the
following:
• high – active alarm input
indicated by high voltage
• low – active alarm input
indicated by low voltage
• off – active alarm input
disabled
In description, enter a
description of the alarm
generated by the alarm-input.
This description is saved in the
log and sent with snmp traps
when the alarm occurs.
Configuring alarm/event alarm-source-attribute <source-name> Use the no form to mask

severity and masking per [<source-id>] alarm {<alarm-list> | all} [severity alarms/events. The following
source {critical | major | minor}] [log] [snmp-trap] [led] apply:
Note: Severity applies [popup] [vtypopup] • If a trap is masked according
only to alarms. alarm-source-attribute <source-name> to alarm/event attribute, it
[<source-id>] event {<alarm-list> | all} [log] is not sent to any
[snmp-trap] [popup] [vtypopup] 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/event alarm-source-type-attribute <source-type> Use the no form to mask

severity and masking per [<source-id>] alarm {<alarm-list> | all} [severity alarms/events. The following
source type {critical | major | minor}] [log] [snmp-trap] [led] apply:
Note: Severity applies [popup] [vtypopup] • If a trap is masked according
only to alarms. alarm-source-type-attribute <source-type> to alarm/event attribute, it
[<source-id>] event {<alarm-list> | all} [log] is not sent to any
[snmp-trap] [popup] [vtypopup] 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 mask-minimum-severity [log {critical | major |

masking and popup minor}] [snmp-trap {critical | major | minor}] [led
behavior per severity {critical | major | minor}] [popup {critical | major |
minor}] [vtypopup {critical | major | minor}]
Configuring alarm rising soaking-time interval [rising rising-msec] clear rising, falling: 0–10,000 ms
and falling soaking times [falling falling-msec] Default:
rising – 2500 ms
falling – 10000 ms
Note: The configured soaking
times apply only for entities for
which there is no standard
dictating a different behavior. If
there is such a standard (e.g.
for SDH/SONET and DS1), the
standard must be followed.
Displaying information on show alarm-information <source-type> show alarm-information

specified alarms and {<alarm-list> | all} <source-type> all indicates to
source type display information on all
alarms of the specified source
type.
Displaying information on show alarm-input The following is displayed:

alarm inputs • Port – port number
• Status – active or inactive
• Voltage – high, low, or off
• Description

Displaying list of show alarm-list

supported alarms, show alarm-list [<source-type> [<source-id>]
optionally for specified [severity {critical | major | minor}]]
source/severity
Displaying information on show event-information <source-type>

specified event and [<event-list>]
source type
Displaying list of show event-list

supported events show event-list <source-type> [<event-list>]
Controlling Popup Behavior

Alarms and events are displayed (pop up) on active CLI terminals as soon as they
occur. You can disable the popups per management session, without saving this
setting in the configuration. It is relevant only for a management session (serial
or Telnet/SSH) for which it is configured, and does not affect any other active
session.
If the popups are disabled for the current management session, they are not
displayed, no matter how they are configured for a specific alarm or event (see
Configuring Alarm and Event Properties).
The current alarm/event popup status is available in the show users-details
screen (see below).
 To disable or enable alarm/event popups:

• At any level, enter popup-suspend to disable alarm/event popups.
• Enter no popup-suspend to enable alarm/event popups.
 To display the user information:

• In the configure>management# prompt, enter show users-details.
ETX-2# configure management show users-details
From:Serial For(sec):281744
User:123456 Level:su Popup: Enabled
From:100.100.100.100/SSH For(sec):4510
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:

The config>reporting# prompt is displayed.

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>] |
specified criteria all} [minimum-severity {critical | major | minor}]
[masked-included] [instance <instance-number>]]
Displaying active alarms show active-alarms-details

with details, optionally show active-alarms-details {<source-type>
according to specified [<source-id>] | all} [minimum-severity {critical |
criteria 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>]}
Displaying alarms in brief show brief-alarm-log

alarm and event history show brief-alarm-log {<source-type> [<source-id>] |
log, optionally according all} [minimum-severity {critical | major | minor |
to specified criteria cleared}] [order-ascending] [time-zone-utc]
[<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]

Displaying brief alarm and show brief-log

event history log, show brief-log {<source-type> [<source-id>] | all}
[<hh:mm[:ss]>]]
show brief-log {<source-type> [<source-id>] | all}
Displaying alarm and show log

event history log, show log {<source-type> [<source-id>] | all}
[<hh:mm[:ss]>]]
show log {<source-type> [<source-id>] | all}
Alarms and Events

You can view the full lists of alarms and events supported by ETX2x.
 To view the alarms table:
• Double-click the paper clip image on the following line.
 To view the events table:
• Double-click the paper clip image on the following line.

Notes • Entries with source type card are relevant only for ETX203AM with SHDSL or
VDSL module.
• Entries with source type pcs or shdsl are relevant for ETX203AM with SHDSL
or VDSL module , and ETX203AX with embedded SHDSL ports.
• Entries with source type e1t1 are relevant for ETX203AM with E1/T1 module,
and ETX205A with E1/T1 ports.
• Entries with source type ptp-recovered or ptp-recovered-master are relevant
only for ETX205A or ETX220A with PTP ordering options.
• Entries with source type clock-domain, clock-domain-source, or station-clock
are relevant only for ETX205A and ETX220A with timing ordering options.
11.12 Troubleshooting
This section contains a general troubleshooting chart that lists possible failures
and provides workarounds.
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 the
Operation and Maintenance chapter.
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-26. Troubleshooting Chart
Fault/Problem Probable Cause Corrective Action
The unit is “dead” No power • Verify that both ends of the power
(POWER LED is off) cable are properly 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

fan or power supply show inventory at the config>system
error. prompt.
• Restart the unit.
• In case of failure, replace the entire
unit.
11-218 Troubleshooting ETX-2

Fault/Problem Probable Cause Corrective Action
The unit is unreachable Incorrect management settings • Using a local serial connection, enable
the relevant management access type
by entering telnet, snmp, 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.
Management path disconnected • In case of remote management,

analyze this issue using 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.
Physical link fails to Link may be administratively • Administratively enable the link.
respond disabled. • In case of Ethernet links, make sure
that the autonegotiation, speed, and
duplex modes match the configured
values on the access switch/router.
Ethernet LINK LED Ethernet cable problem • Check the Ethernet cable to see
is off whether a cross or 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.
ETX-2 Troubleshooting 11-219

11.13 Performing Diagnostic Tests
Running a Ping Test

You can ping a remote IPv4 or IPv6 host to check the ETX-2 IP connectivity with
that host. You can define the number of pings (packets) to generate, or
configure a continuous ping (infinite). The ping generator continues to generate
ping requests according to the number of configured pings, or until you manually
disrupt it (by pressing Ctrl+C).
 To ping an IP host:
In any level, start pinging the host, specifying its IP address (IPv4 or IPv6)
and optionally the number of packets to send, payload size (in bytes), and
router entity number:
ping <ip-address> [number-of-packets <packets>] [payload-size <bytes>]
[router-entity <number>]
Table 11-27. Ping Parameters
<ip-address> Destination IP address Valid IPv4 or IPv6 address

1.1.1.1–255.255.255.255
Note: Multicast address is not
allowed.
number-of-packets Number of pings Possible values:

0 (forever), 1-10000
Default: 5
payload-size Packet size Possible values:

32-1450 bytes
router-entity Related router-entity Possible values: 1-max-vrf-number
If the remote host answers, ETX-2 displays the ping results including the round
trip delay, rounded as in the following table.
Table 11-28. Ping Round Trip Results
Round Trip Delay Displayed in Ping Results
<= 10 msec time < 10 ms
>= 11 msec and <= 20 msec time < 20 ms
: :
: :
Example
ETX-2# ping 10.10.10.10
11-220 Performing Diagnostic Tests ETX-2


Reply from 10.10.10.10.44: bytes = 32, packet number = 2, time < 10 ms
Tracing the Route

This diagnostic utility traces the route through the network from ETX-2 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 (IPv4 or IPv6) of
the host to which you intend to trace route:
trace-route <1.1.1.1–255.255.255.255>
11.14 Frequently Asked Questions
Q How should ETX-2 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.
Q If I change the functional mode of a network Ethernet port to user, what

happens to the associated flows?
A When you change the functional mode, all flows related to the port are
deleted.
11.15 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!
ETX-2 Technical Support 11-221

11-222 Technical Support ETX-2

Chapter 12
Software Upgrade
This chapter explains how to upgrade ETX2 for software version 6.5.
Software upgrade is required to fix product limitations, enable new features, or
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. It
is recommended to name these software packs sw-pack-1 and sw-pack-2.
Note You can define only two software packs simultaneously. Although the CLI allows
you to name the SW packs sw-pack-1 through sw-pack-4, it is recommended to
name them sw-pack-1 and sw-pack-2.
You can designate any of the software packs as active. The non-active software
pack serves as a backup that can be used if the active software becomes
corrupted.
The information in this chapter includes the following:
• Software packs that can be loaded into each device
• Detailed conditions required for the upgrade
• Any impact the upgrade may have on the system
• Description of downloading options
Application software can be downloaded to ETX2 via SFTP/TFTP with the copy
command, or via XMODEM, FTP, or TFTP, from the Boot screen.
The downloaded software pack can be installed as the active software via the
admin software install command, or from the Boot screen.
Note Software upgrade relates to upgrading from the product’s previous version to
current version. To upgrade from an older version, you may not be able to
upgrade directly to the latest version, but may be required to upgrade one
version at a time. Refer to the relevant User Manual for upgrade instructions.
12.1 Compatibility Requirements

Following are the software releases that can be upgraded to version 6.5, as well
as the hardware revisions that can accept the software version 6.5.
• Software – Ver. 4.5x, 5.0x, 5.5x, 5.7x , 5.8x, 5.9x, 6.0x, 6.2x, 6.3x, 6.4x
• Hardware – 1.0 and above
ETX2 Compatibility Requirements 12-1

Chapter 12 Software Upgrade Installation and Operation Manual
12.2 Impact
During the software upgrade process, service is disrupted.
12.3 Prerequisites
SFTP/FTP/TFTP Prerequisites
Prior to upgrading via SFTP/FTP/TFTP, verify that you have the following:
• Operational ETX2 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.
XMODEM Prerequisites
Prior to upgrading via XMODEM, verify that you have the following:
• Operational ETX2 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.
Software Packs
Each ETX2 software download can contain two sw-packs from the available
options listed in the following table.
Note As ETX220A is available with more than one chassis type, take special care to
download the software versions suitable to the chassis type.
Table 12-1. Software Packs per Device
Device File Name Description
ETX203AM ETX2_x.x.x(x.x)_sw-pack_203am.bin Full capabilities of the device
ETX2_x.x.x(x.x)_sw-pack_203am_f2.bin User ports can sync on Fast only; device has only two
queue blocks.
ETX2_x.x.x(x.x)_sw-pack_203am_g2.bin User ports can sync on Giga only; device has only two
queue blocks.
ETX203AX ETX2_x.x.x(x.x)_sw-pack_203n.bin Full capabilities of the device
12-2 Prerequisites ETX2

Installation and Operation Manual Chapter 12 Software Upgrade
Device File Name Description
ETX2_x.x.x(x.x)_sw-pack_203ng_f2.bin User ports can sync on Fast only; device has only two
queue blocks.
ETX2_x.x.x(x.x)_sw-pack_203ng_g2.bin User ports can sync on Giga only; device has only two
queue blocks.
ETX205A ETX2_x.x.x(x.x)_sw-pack_205.bin Full capabilities of the device
ETX220A ETX2_x.x.x(x.x)_sw-pack_220a.bin Full capabilities of the device; device should be

4x10GbE or 4x10GbE + 10x1GbE ports.
ETX2_x.x.x(x.x)_sw-pack_220A_10x1g.bin Full capabilities of the device; device should be

3x10GbE + 10x1GbE ports.
ETX2_x.x.x(x.x)_sw-pack_220A_20x1g Full capabilities of the device; device should be

ETX2_x.x.x(x.x)_sw-pack_220a_bsk.bin 2QB capabilities only; device should be 4x10GbE or

ETX2_x.x.x(x.x)_sw-pack_220A_10x1g_bsk.bin 2QB capabilities only; device should be 3x10GbE +

10x1GbE ports.
ETX2_x.x.x(x.x)_sw-pack_220A_20x1g_bsk.bin 2QB capabilities only; device should be 2x10GbE +

20x1GbE ports.
12.4 Upgrading Software via CLI

You can upgrade the following software using CLI commands:
• ETX2 software
• PMC software (in ETX205A)
Note Old PMC software (with TWAMP Light only) cannot be upgraded to new PMC
software (with Full TWAMP, TWAMP Light, ICMP Echo, and UDP Echo). Upgrades
are available only after the new PMC has been installed.
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 ETX2 units in the network from a central location.
Use the following procedure to download software release 6.5 to ETX2x via CLI.
1. Verify that the image file is stored on the PC with the SFTP/TFTP server
application.
2. Verify that the ETX2 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 ETX2.
6. Install the image as the active software.
ETX2 Upgrading Software via CLI 12-3

Note Configuration values shown in this chapter are examples only.
Verifying the Host Parameters

In order to be able to establish communication with the SFTP/TFTP server, the
ETX2 router must have IP parameters configured according to your network
requirements. Refer to the following manual sections for additional information:
• Connecting to a Terminal in the Installation and Setup chapter
• Working with Terminal in the Operation and Maintenance chapter
• Router in the Traffic Processing chapter
Pinging the PC
Check the integrity of the communication link between ETX2 and the PC by
pinging the PC from ETX2.
 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 <num-packets>][payload-size
<bytes>]
Where
num-packets can be 1-10,000 or 0 (forever) for a continuous ping. Default is
5.
bytes can be 32-1450.
A reply from the PC indicates a proper communication link.
2. If the ping request times out, check the link between ETX2 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 carries out the received request
automatically.
SFTP file transfers are carried out through TCP port 22. Make sure that the
firewall you are using on the server allows communication through this port (refer
to the Administration chapter 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 carries out the received request
automatically.
12-4 Upgrading Software via CLI ETX2

TFTP file transfers are carried out through port 69. Make sure that the firewall
you are using on the server allows communication through this port (refer to the
Administration chapter for details).
Note Configure the connection timeout of the TFTP server to be more than 30 seconds
to prevent an automatic disconnection during the backup partition deletion
(about 25 seconds).
Downloading the New Software Release File

This procedure is used to download a new software version.
 To copy the image file to the ETX2 unit:

• In any level, enter:
copy sftp://<username>:<password>@<ip-address>/<image-file-name>
<sw-pack-n>
Where <ip-address> is the IP address of the PC where the SFTP server is
installed and <n> is the index of the software pack.
Or
copy tftp://<tftp-ip-address>/<image-file-name> <sw-pack-n>
Where tftp-ip-address is the IP address of the PC where the TFTP server is
installed and <n> is the index 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. See Activating the Software for

instructions on installing the downloaded software as the active
software.
Note
ETX220A, which has several SW builds, automatically handles mismatch of a
downloaded SW version. After the new software release file has finished
downloading, the device automatically checks that the downloaded software
version matches the device. If not, the device reboots and reverts to the previous
version.
Activating the Software

After software is downloaded to ETX2, it has to be installed via the install
command as the active software. When you install software, by default ETX2
creates a restore point, so that if there is a problem with the new software pack,
you can perform a rollback to the previous software pack and startup-config file.
This ensures that if you changed the startup-config file before noticing that
something was wrong with the newly installed software, you can restore the
startup-config that was running before the last installation.
ETX2 Upgrading Software via CLI 12-5

Note The file startup-config must exist before you can install software with creation of
a restore point.
Prior to installing the software, you can request (via command

software-confirm-required) that the user confirm the next installed software (via
command software-confirm) following the next ETX2 reboot. This software
confirmation command verifies that the user has regained connection to the
device following installation. If confirmation is requested, but the user does not
confirm the software (via command software-confirm) within the configured
timeout period, ETX2 automatically falls back to its previous software. This
precaution prevents a permanent loss of connection to the remote device
following installation.
 To request software confirmation:

• At the admin>software# prompt, enter:
software-confirm-required [time-to-confirm <minutes>]
The confirmation timeout can be from 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.
Next time ETX2 reboots and loads new software, it starts a confirmation
timer. See the following procedure for more details on the confirmation.
 To install a software pack as active:
Notes • If startup-config does not exist, you must install the software pack without
creating a restore point.
• As a defective startup-config can cause a loss of connection, it is not
recommended to install software and change startup-config at the same time.
However, if you must do both at the same time, first install the software and
only after verifying it, make the needed configuration changes (or vice versa).
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-4). If you specify no-restore-point, then after
the software is installed, it is not possible to roll back to the previous
software.
You are prompted to confirm the operation.
!Device will install file and reboot. Are you sure? [yes/no] _
2. Type yes to confirm.

If a restore point is being created, then startup-config is copied to
restore-point-config. ETX2 designates the specified software pack as
active, then reboots.
3. If a software confirmation request is active, ETX2 starts a timer with the
specified timeout period.
12-6 Upgrading Software via CLI ETX2

Note While the confirmation timer is running, ETX2 does not allow any commands that
change its configuration.
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, ETX2 designates the previously active
software pack as active, then reboots.
12.5 Upgrading ETX2 Software via the Boot Screen

Software downloading can also be performed from the Boot screen. The Boot
screen can be reached while ETX2 performs initialization, such as after
power-up.
You may need to start the loading from the Boot screen if you are unable to use
the copy command (for example, because the ETX2 software has not yet been
downloaded or is corrupted).
Caution The Boot screen procedures are recommended only for use by authorized
personnel, because it provides many additional options that are intended for use
only by technical support personnel.
The following software downloading options are available from the Boot screen:
• Downloading using the XMODEM protocol. This is usually performed by
downloading from a PC directly connected to the CONTROL DCE port of the
unit.
• 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 ETX2.
Accessing the Boot Screen

The Boot screen can be accessed when the device is powered up, before logging
in.
 To access the Boot screen:

1. Connect the ASCII terminal or PC with terminal emulation to the ETX2
CONTROL port.
2. 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.
3. Power off ETX2.
4. Activate the terminal application.
5. Power on ETX2 and immediately start pressing the <Enter> key several times
in sequence until you see the prompt to press any key to stop the autoboot.
ETX2 Upgrading ETX2 Software via the Boot Screen 12-7

6. Press any key.

The Boot screen appears. A typical Boot screen is shown below (the exact
version and date displayed by your ETX2 unit may be different).
Note If you miss the timing, ETX2 performs a regular reboot process (this process
starts with Loading/un-compressing sw-pack-<n> and ends with the login
screen).
System Boot
Copyright 1984-2008 RAD Data Communications, Ltd.
Boot version: 1.04 [05-May-11]
CPU : Freescale MPC8313E

OS version : VxWorks 6.7
BSP version: 1.15
Boot-Manager version: 2.13 [11-Jan-11]
Use '?'/help to view available commands
Press any key to stop auto-boot...

7
[boot]:
Figure 12-1. Boot Screen
7. Enter ? to display a list of boot commands.

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
8. Enter p to display all boot parameters.
The boot parameters appear. A typical boot parameter list is shown
below (see Table 12-2 for details on the boot parameters).
[boot]: p
file name (fn) : vxWorks

device IP (ip) : 10.10.10.101
device mask (dm) : 255.255.255.0
12-8 Upgrading ETX2 Software via the Boot Screen ETX2

server IP (sip) : 10.10.10.2

gateway IP (g) : 10.10.10.2
user (u) : vxworks
ftp password (pw) : *******
device name (dn) : ETX2
quick autoboot (q) : no
protocol (p) : ftp
baud rate (b) : 9600
Figure 12-2. Typical Boot Parameters Screen
Table 12-2. Boot Parameters
Parameter Command Description
file name fn The binary software pack file (*.bin) name to be

downloaded via FTP/TFTP
device ip ip ETX2 IP address
device mask dm ETX2 IP subnet mask
server IP sip FTP/TFTP server IP address
gateway ip g FTP/TFTP server default gateway IP address
user u User name for FTP server

Note: Displayed only when using FTP protocol.
ftp password pw User password for FTP server

Note: Displayed only when using FTP protocol.
device name dn ETX2
quick autoboot q Enables or disables the quick autoboot feature
protocol p File transfer protocol to use: FTP or TFTP
baud rate b Transmission bit rate (in kbps): 9600, 19200, or 115200
9. Enter c to configure the boot parameters.

The boot parameters are displayed line by line. For each parameter, you
can type a different value, or click <Enter> to go to the next parameter.
The example below illustrates changing the file name to ETX2.bin, and
the protocol to TFTP.
'.' = clear field; '-' = go to previous field; ^D = quit
file name (fn) : vxworks ETX2.bin

device IP (ip) : 10.10.10.101
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.2
gateway IP (g) : 10.10.10.2
user (u) : vxworks
ftp password (pw) (blank = use rsh): *******
device name (dn) : ETX2
quick autoboot [y/n] : n
protocol [tftp/ftp] : ftp tftp
baud rate [9600/19200/115200]: 9600

10. See the following sections for instructions on downloading via XMODEM, FTP,
or TFTP.
Note ETX220A, which has several SW builds, automatically handles mismatch of a

downloaded SW version. If you download the wrong software pack to the device,
the device boots up with the mismatch version and issues an HW SW mismatch
alarm.
Using FTP
Use the following procedure to download software release 6.5 to ETX2 via FTP.
 To download software release via FTP:

1. Verify that the image file is stored on the PC with the FTP server application.
2. Enter the Boot screen and set the boot parameters as needed (see Accessing
the Boot Screen). For example, set the FTP user and password, and set
protocol to FTP.
3. At the boot prompt, enter:
download <index>[, <FileName>]
If no errors are detected, the downloading process starts, and the file is
downloaded via FTP.
Notes • The <index> parameter corresponds to the software pack number to which to
copy the image file.
• If you have set the file name in the boot parameters, you do not need to
specify <FileName>.
For example, to download the file name configured in the boot

parameters to sw-pack-2, enter:
download 2
4. See Activating the Software for instructions on activating the downloaded
software.
Using TFTP
Use the following procedure to download software release 6.5 to ETX2 via TFTP.
 To download software release via TFTP:

1. Verify that the image file is stored on the PC with the TFTP server application.
the Boot Screen). For example, set protocol to TFTP.
download <index>[, <FileName>]
If no errors are detected, the downloading process starts, and the file is
downloaded via TFTP.
12-10 Upgrading ETX2 Software via the Boot Screen ETX2

Notes • The <index> parameter corresponds to the software pack number to which to
copy the image file
• If you have set the file name in the boot parameters, you do not need to
specify <FileName>.
For example, to download the file name configured in the boot

parameters to sw-pack-2, enter:
download 2
software.
Using XMODEM
Use the following procedure to download software release 6.5 to ETX2 via
XMODEM.
 To download software release via XMODEM:

1. Verify that the image file is stored on the PC with the terminal application.
the Boot Screen).
download <index>, x
Note The <index> parameter corresponds to the software pack number to which to
copy the image file.
The process starts, and the following is displayed:

The terminal will become disabled !!!
Please send the file in XMODEM
4. 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 ETX2 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.
When the downloading process has successfully completed, a sequence
of messages similar to the following is displayed:

File writing to flash: - 4030KB

File downloaded successfully to :2

software.
Activating the 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

You can verify that the upgrade was successful by logging on to ETX2 via a
terminal emulation program, and in the Inventory table (show summary-inventory
at prompt config>system#), checking the active software version in the SW Rev
column.
12.7 Restoring the Previous Version

If the installed software malfunctions and was installed with a restore point
(restore-point-config must exist on device), you can perform rollback to the
previous active software.
 To roll back to the previous active software pack:

1. At the admin>software# prompt, enter:
undo-install
You are prompted to confirm the operation.
! Falling back to restore point ! Are you sure? [yes/no] _
2. Type yes to confirm.
12-12 Restoring the Previous Version ETX2

The file restore-point-config is renamed to startup-config. ETX2

designates the previously active software pack as active, then reboots.
ETX2 Restoring the Previous Version 12-13

12-14 Restoring the Previous Version ETX2

Chapter 13
Application Tutorial
This chapter provides configuration guidelines for setting up a typical E-Line
service.
The configuration activities presented in this chapter assume that ETX2 is
configured using a standard ASCII terminal, and that you are familiar with ETX2
management as described in the Management and Security chapter.
Figure 13-1 illustrates the application layout. Table 13-1 details a summary of
port connections.
Figure 13-1. E-Line Application
Ethernet Private Line (EPL) is implemented using a point-to-point EVC. All service
frames at the UNI are mapped to a single EVC.
The data traffic flow in the application behaves as follows (from left to the right):
1. PC transmits untagged packets, traffic enters ETX205A User port #3.
2. ETX205A adds VLAN ID 10 towards the network.
3. ETX-5 accepts only traffic with VLAN 10 in port 1/10 and forwards the
packets to port 1/20 in the same I/O card.
4. ETX203AX accepts only traffic tagged with VLAN 10, removes the VLAN, and
forwards the untagged packets to PC.
Table 13-1. Connection Summary
From Device/Port To Device/Port
ETX205A, port 3 PC network interface #2
ETX205A, port 1 ETX-5, port 1/10
ETX-5, port 1/20 ETX203AX, port 1
ETX203AX, port 3 PC network interface #3
ETX2 Equipment List 13-1

Chapter 13 Application Tutorial Installation and Operation Manual
13.1 Equipment List

Table 13-2 lists the devices required for the application.
Table 13-2. Required Equipment
Device Quantity
ETX205A 1
ETX203AX 1
ETX-5 1
PC with application such as Ostinato that can 1
simulate traffic, and three network cards for
following:
• Management (one network card)
• Connect to simulate traffic (two network
cards)
13.2 Installing the Units

Before starting configuration, install the units as follows:
1. Configure PC network interface #1 with static IP address 172.17.192.10.
2. Connect PC network interface #2 to ETX205A port 3.
3. Connect ETX205A port 1 to ETX-5 port 1/10.
4. Connect ETX-5 port 1/20 to ETX203AX port 1.
5. Connect ETX203AX port 3 to PC network interface #3.
13.3 Configuring the E-Line Service

This section describes how to configure the E-Line service.
Configuring E-Line for ETX205A

You need to create the following:
• Outgoing data traffic from user to network:
 Classifier profile that accepts traffic untagged (data traffic entering
ETX205A from user port #3)
 Flow named 3t1 from user port #3 to network port #1, using the above
profile, and adding VLAN 10 (with P-bit 0)
• Incoming data traffic from network to user:
13-2 Configuring the E-Line Service ETX2

Installation and Operation Manual Chapter 13 Application Tutorial
 Classifier profile that accepts only traffic tagged with VLAN ID 10 (data
traffic entering ETX205A from the network)
 Flow named 1t3 from network port #1 to user port #3, using the above
profile, and removing the SP-VLAN
exit all
#*********** Create classifier profiles
configure flows
match untagged
exit

match vlan 10
exit
#*********** Create flows

flow 3t1
classifier untagged
no shutdown
exit
flow 1t3
classifier v10
vlan-tag pop vlan
no shutdown
exit all
save
Configuring E-Line for ETX203AX

As ETX203AX and ETX205A have the same configuration in this application,
either repeat the same commands listed in Configuring E-Line for ETX205A, or
copy the commands to a script, transfer it to ETX203AX, and run it.
Configuring E-Line for ETX-5

You need to create the following:
• Queue group profile assigned to ports 1/10 and 1/20, and the ports enabled
• SAG (service aggregation group) queue group profiles
• Data traffic from port 1/10 to port 1/20:
 Flow from port 1/10 to SAP
 Flow from SAP to port 1/20
• Data traffic from port 1/20 to port 1/10:
 Flow from port 1/20 to SAP
ETX2 Configuring the E-Line Service 13-3

 Flow from SAP to port 1/10

exit all
#*********** Configure Ethernet port queue groups
config port
ethernet 1/10
queue-group profile q_group_2_level_default
no shutdown
exit
ethernet 1/20
queue-group profile q_group_2_level_default
no shutdown
exit
#*********** Configure SAG queue group profiles

sag 1/1
queue-group profile q_group_SAG_2_level_default
exit
sag 1/2
queue-group profile q_group_SAG_2_level_default
exit all
#*********** Configure classifier profiles

configure flows
match vlan 10
exit

match all
exit
#*********** Configure flows

flow 10_sap
classifier v10
egress-port sap 1/1/2 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
flow sap_20
classifier all
ingress-port sap 1/1/2
egress-port eth 1/20 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
flow 20_sap
classifier v10
egress-port sap 1/2/2 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
13-4 Configuring the E-Line Service ETX2

configure flows flow sap_10

classifier all
ingress-port sap 1/2/2
egress-port eth 1/10 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all
save
13.4 Testing the Application
Checking E-Line Connectivity

To check the E-Line application, use the data traffic application on the PC to
verify the following:
• Only untagged packets pass between CPEs.
• Traffic passes from end to end between CPEs.
Checking Port/Flow Statistics

 To check the statistics:
1. Connect ETX203AX, and view user port #3 statistics.
2. Verify that counters are as expected according to the generated traffic rate
and type. The following shows an example of the statistics:
ETX2 Testing the Application 13-5

ETX2# configure port ethernet 3ETX2>config>port>eth(3)# show

statistics
--------------------------------------------------------------
Running
--------------------------------------------------------------
Rx Tx
Total Frames : 120368 40674
Total Octets : 182716280 61743132
Total Frames/Sec : 192 65
Total Bits/Sec (L1) : 0 0
Minimum Bits/Sec (L1) : 0 0
Maximum Bits/Sec (L1) : 0 0
Total Bits/Sec (L2) : 2342512 791576

Minimum Bits/Sec (L2) : 14572800 4972968
Maximum Bits/Sec (L2) : 14773176 4985112
Unicast Frames : 120366 40674
Multicast Frames : 0 0
Broadcast Frames : 2 0
CRC Errors : 0 --
Error Frames : 0 --
L2CP Discarded : 0 --
OAM Discarded : 0 --
MTU Discarded : 0 56
Unknown Protocol Discarded : 0 --
CRC Errors/Sec : 0 --
Jabber Errors : 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-1528 Octets : 121575 41084
1519-2047 Octets : 0 0
2048-Max Octets : 0 0
MTU Discarded Flow : --/EVC1-TLV
3. View statistics for flow 3t1, and verify that counters are as expected
according to the generated traffic rate and type. The following shows an
example of the statistics:
13-6 Testing the Application ETX2

ETX2# configure flows flow 3t1

ETX2>config>flows>flow(3t1)# show statistics running
-----------------------------------------------------------------------------
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 20000
Bytes : 20000000
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
ETX2 Testing the Application 13-7

13-8 Testing the Application ETX2

Appendix A
Connection Data
A.1 Ethernet Connector

The Ethernet electrical interfaces terminate in 8-pin RJ-45 connectors, of type
10/100BaseT or 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 E1/T1 Connector
Note This section is relevant for ETX203AM ordered with a 4 or 8 port E1/T1 module,
ETX203AX with a built-in E1 port, and ETX205A with 4 or 8 built-in E1/T1 ports.
The E1/T1 connectors are wired as follows, according to the device type:
• ETX203AM with Ethernet Uplink E1/T1 module having four or eight E1/T1
ports – The E1/T1 ports terminate in four RJ-45 connectors. In module with
four E1/T1 ports, each connector provides one port; in module with eight
E1/T1 ports, each connector provides two ports. Table A-2 and Table A-3 list
the pin assignments for four and eight E1/T1 ports, respectively. In the case
of eight E1/T1 ports, you can use RAD cable CBL-E1-SPLT to connect
ETX203AM to the E1/T1 equipment.
• ETX203AX-E1 – A single E1 terminates with a single RJ-45 connector.
Table A-2 lists the pin assignments.
ETX2 E1/T1 Connector A-1

Appendix A Connection Data Installation and Operation Manual
• ETX205A – The E1/T1 connectors terminate in four RJ-45 connectors for

ordering option with four E1/T1 ports; or eight RJ-45 connectors for ordering
option with eight E1/T1 ports. Table A-2 lists the pin assignments.
Table A-2. E1/T1 Connector Pinout – One E1/T1 Port per Connector (for
ETX203AX-E1, ETX203AM with 4-port E1/T1 module, ETX205A with 4 or 8 built-
in E1/T1 ports)
PIN Function Direction
1 RX Ring Input
2 RX Tip Input
3 NC NC
4 TX Ring Output
5 TX Tip Output
6 NC NC
7 NC NC
8 NC NC
Table A-3. E1/T1 Connector Pinout – Two E1/T1 Ports per Connector (ETX203AM
with 8-port E1/T1 module)
Channels 1–4 Channels 5–8
PIN Function Direction Function Direction
1 RX Ring Input NC NC
2 RX Tip Input NC NC
3 NC NC TX Ring Output
4 TX Ring Output NC NC
5 TX Tip Output NC NC
6 NC NC TX Tip Output
7 NC NC RX Ring Input
8 NC NC RX Tip Input
Note
Do not connect wires to the NC pins.
A.3 CONTROL Connector

The CONTROL connector is an 8-pin RJ-45. The following table lists the CONTROL
connector pin assignments.
A-2 CONTROL Connector ETX2

Installation and Operation Manual Appendix A Connection Data
Table A-4. CONTROL Connector Pinout
Pin Name Function
1, 2, 3 N.A. –
4 GND Ground
5 TXD Transmit Data (output)
6 RXD Receive Data (input)
7, 8 N.A. –
A.4 EXT CLK Connector
Note This section is relevant only for ETX205A or ETX220A if a timing option was
ordered.
The station clock port terminates in an 8-pin RJ-45 connector, wired in

accordance with Table A-5.
Table A-5. EXT CLK Connector Pinout
Pin Direction Function
1,2 Input T3 (Input)
3 – Not connected
4,5 Output T4 (Output)
6, 7, 8 – Not connected
A.5 MNG Connector

The ETX2 Ethernet management port terminates in an RJ-45, 8-pin connector
that supports MDI and MDIX modes. Table A-6 lists the pin assignments.
Table A-6. 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
ETX2 MNG Connector A-3

Pin Designation Function
6 TxD- Transmit Data input, – wire
7,8 – Not connected
A.6 SHDSL Connector
Note This section is relevant for ETX203AM with an SHDSL module, or ETX203AX with
embedded SHDSL ports. One 8-pin RJ-45 connector is used for the 4-wire
ordering option, and two 8-pin RJ-45 connectors are used for the 8-wire ordering
option. Each pin is wired as in the table below.
The SHDSL electrical interface is an 8-pin RJ-45 connector, wired in accordance

with Table A-7.
Table A-7. SHDSL Connector Pinouts
Pin Function
1 NC
2 NC
3 Loop 2
4 Loop 1
5 Loop 1
6 Loop 2
7 NC
8 NC
Note Do not connect wires to the NC pins.
A.7 VDSL Connector
Note This section is relevant only for ETX203AM with VDSL module.
The VDSL AIO electrical interface is made up of two 8-pin RJ-45 connectors – one
connector for Loop 1 and Loop 2; the other for Loop 3 and Loop 4. Each
connector is wired in accordance with Table A-8.
A-4 VDSL Connector ETX2

Installation and Operation Manual Appendix A Connection Data
Table A-8. VDSL Connector Pinout
Pin Function
1 NC
2 NC
3 Loop 2 / Loop 4
4 Loop 1 / Loop 3
5 Loop 1 / Loop 3
6 Loop 2 / Loop 4
7 NC
8 NC
Note Do not connect wires to the NC pins.
A.8 ToD/1PPS Connector
Note This section is relevant only for ETX205A or ETX220A if a PTP option was
ordered.
The ToD/1PPS interface terminates in an RS-422 (half duplex) 8-pin RJ-45

connector. Table A-9 lists the pin assignments.
Table A-9. ToD/1PPS Connector Pinout
Pin Function
1 Option, NC
2 Option, NC
3 Tx/Rx 1PPS -
4 GND
5 GND
6 Tx/Rx 1PPS +
7 Tx/Rx TOD -
8 Tx/Rx TOD +
ETX2 ToD/1PPS Connector A-5

A-6 ToD/1PPS Connector ETX2

Appendix B
Test Plan
B.1 Introduction
This document describes basic tests to verify ETX-2 functionality for the following
features:
• Basic functionality (connectivity, passing traffic without errors)
• Protection (link protection, LAG )
• OAM (CFM)
• RFC-2544
• Device reset
Note All tests should pass if the following procedures are performed precisely.
B.2 Required Equipment

Table B-1 lists devices required for conducting the tests.
Table B-1. Required Equipment
Device Description Quantity
Unit under test (UUT) Setup in Figure B-1: ETX203AM, ETX203AX, or 6 (at least two
ETX205A ETX203AM
devices, with
SHDSL 4-wire
network module
and SHDSL 8-wire
network module,
respectively)
Setup in Figure B-2: ETX203AM with GbE 4

network module, ETX203AX, ETX205A, or
ETX220A
DSLAM DSLAM working in central office mode, for 2

verifying SHDSL traffic via ETX203AM
Network management station PC or Unix workstation equipped with RADview 1
ETX-2 Required Equipment B-1

Appendix B Test Plan Installation and Operation Manual
Device Description Quantity
Network Tester Network testing equipment with Ethernet 1

interfaces such as IXIA 400T, Spirent Test Center,
etc.
Switch Traffic switch such as Cisco 1
Traffic Generator Traffic generating equipment, for verifying SHDSL 2

traffic via ETX203AM
B.3 Preparing the Test Layout

The following diagrams illustrate the test plan setups.
Notes • The numbers enclosed in boxes are port numbers

• The Network Tester icons represent the various ports of a single network
testing device.
EFM EFM EFM EFM

3 Active Passive Passive Active 3
4 4
5 SHDSL 4-wire SHDSL 8-wire 5
6 UUT-5 UUT-6 6
Traffic DSLAM-1 DSLAM-2 Traffic
Gen-1 Gen-2
EFM
Passive
EFM 1
2
1 3 Active 3
1 1 3 UUT-3
2 4 5
LAG/LACP Protection EFM
3 5 2 2 4 6
Passive
4 6 UUT-1 Switch UUT-2 EFM 2 7
1
Network Active 8
VID 51 3
Tester OOB Network
UUT-4
Tester
NMS
Figure B-1. Test Setup – Basic with DSLAM (ETX203AM, ETX203AX, or ETX205A)
Notes • UUT-1 through UUT-4: ETX203AM with GbE network module, ETX203AX, or
ETX205A
• UUT-5: ETX203AM with SHDSL 4-wire network module
• UUT-6: ETX203AM with SHDSL 8-wire network module
B-2 Preparing the Test Layout ETX-2

Installation and Operation Manual Appendix B Test Plan
3 4
Network
Tester
[0/]3 [0/]4
Node, 1/3 1/4 Node,
east west
[1/]1 [1/]2
NMS 4/1 4/2
UUT-2
Node,
east Switch Node,
Main data path east
[1/]1 [1/]1
[0/]3 4/1 [0/]3
4/1 5
1 2/9 1/1
2 [0/]4 [1/]2 [0/]4 6
2/10 [1/]2 1/2
UUT-1 4/2 4/2 UUT-3
Network Network
Protection data path Node,
Tester RPL, Tester
west
west
Neighbor, Node,
west east
[1/]2 [1/]1
4/2 4/1
[0/]3 UUT-4 [0/]4
1/1 1/2
7 8
Network
Tester
Figure B-2. Test Setup – Ring (ETX203AM with GbE network module, ETX203AX, ETX205A, or
ETX220A)
Note The following applies when there is more than port number in a box:
• The top number is relevant for the following UUTs:
• ETX203AM (slot number in brackets applicable)
• ETX203AX (slot number in brackets not applicable)
• ETX205A (slot number in brackets not applicable)
• The bottom number is relevant for ETX220A.
Connecting the Test Layout

The following tables list the connections between the devices, and the cable
required for each connection.
Note In Table B-2, the slot number [0/] or [1/] is applicable only if the UUT is
ETX203AM.
Table B-2. Test Layout Connections for Figure B-1
Device Cable Device
UUT-1 port [1/]1 Straight Ethernet cable Switch
UUT-1 port [0/]3 Straight Ethernet cable Network Tester port 1
ETX-2 Preparing the Test Layout B-3

Device Cable Device
UUT-2 port [0/]3 Straight Ethernet cable UUT-3 port [1/]1
UUT-4 out-of-band (OOB) Straight Ethernet cable Switch

Ethernet management port
UUT-5 port 1/1 Straight SHDSL cable DSLAM-1
UUT-5 port 0/3 Straight Ethernet cable Traffic Gen-1
DSLAM-1 Straight SHDSL cable UUT-5 port 1/1

Device Cable Device
Network Tester port 1 Straight Ethernet cable UUT-1 port 0/3
Network Tester port 7 Straight Ethernet cable UUT-4 port [1/]2
Switch Straight Ethernet cable UUT-1 port [1/]1
Switch Straight Ethernet cable UUT-4 out-of-band (OOB)

Ethernet management port
Traffic Gen-1 Straight Ethernet cable UUT-5 port 0/3
Table B-3. Test Layout Connections for Figure B-2
Note The following applies when there is more than port number in a table cell:
• The top number is relevant for the following UUTs:
• ETX203AM (slot number in brackets applicable)
• ETX203AX (slot number in brackets not applicable)
• ETX205A (slot number in brackets not applicable)
• The bottom number is relevant for ETX220A.
Device Cable Device

UUT-1 port 2/9

UUT-1 port 2/10

Device Cable Device

UUT-1 port 4/1

UUT-1 port 4/2 UUT-4 port 4/2

UUT-2 port 1/3

UUT-2 port 1/4

UUT-2 port 4/1


UUT-3 port 1/1

UUT-3 port 1/2



UUT-4 port 1/1

UUT-4 port 1/2



UUT-1 port 2/9

UUT-1 port 2/10

UUT-2 port 1/3

UUT-2 port 1/4

Device Cable Device

UUT-3 port 1/1

UUT-3 port 1/2

UUT-4 port 1/1

UUT-4 port 1/2

UUT-1 port 4/1

UUT-2 port 4/1
Configuring Devices
This section presents the device configurations. The data such as VLAN IDs, IP
addresses, etc. were randomly selected for test purposes, and can be changed to
suit your particular configuration.
Configuring the Switch

Configure the Switch as follows:
• Connectivity for Figure B-1:
 Connect all ports to SFP Giga Fiber.
 Set the ports that are connected to UUT-1 for LAG and LACP.
 Set the ports that are connected to UUT-2 for protection 1:1.
• Configuration:
 Set all ports to transfer the VLANs in the configuration scripts in
Configuring ETX-2 Devices .
 Enable the SNTP servers in the configuration scripts in Configuring ETX-2
Devices.
Configuring ETX-2 Devices

The following table presents the configuration files for the ETX-2 devices,
according to test functionality and device type. You can open or save the
configuration files as follows:
• To open the file – Double-click the icon .
• To save the file – Right-click the icon and select Save Embedded File to
Disk.

Table B-4. Configuration Scripts for Setup in Figure B-1
Device ETX203AM ETX203AX ETX205A
UUT-1
UUT-2
UUT-3
UUT-4
UUT-5 Not applicable Not applicable
UUT-6 Not applicable Not applicable
Table B-5. Configuration Scripts for Setup in Figure B-2
Device ETX203AM ETX203AX ETX205A ETX220A
UUT-1
UUT-2
UUT-3
UUT-4

B.4 Testing Basic Functionality

This test verifies that the test setup functions properly.
Estimated Duration
The estimated duration of this test is one hour.
Setup and Configuration

See Figure B-1 or Figure B-2, and Configuring Devices.
Test Procedure
# Action Expected Result Result
1 Ping the UUTs to verify network connectivity. The UUTs reply to ping.
2 Open Telnet and SSH sessions to the UUTs. Telnet and SSH sessions are established successfully.
3 Initiate SNMP management session from RADview Devices reply to ping and appear on RADview map.
NMS and verify management connectivity to all
devices.
4 Display UUT inventory (via config system show The inventory display is correct for the following:
summary-inventory). • Ports
• Fans
• Power supplies
• Software version
• MAC address
ETX-2 Testing Basic Functionality B-9

5 If the UUT is ETX203AM, check the card status. The card status shows the correct type of network module that
is installed, e.g.:
UUT-5>config>slot(1)# show status
Actual Type : SHDSL 4W
Provisioned Type : SHDSL 4W
Status Details : OK
UUT-6>config>slot(1)# show status

Actual Type : SHDSL 8W
Provisioned Type : SHDSL 8W
Status Details : OK
6 Run Ethernet traffic for at least 15 minutes as The traffic passes without errors or packet loss.
follows, according to the test setup:
• Test setup in Figure B-1: From Network Tester
port 1 and port 5, send packets with frame
size 1518 bytes, VLAN 4040, at 98% line rate.
• Test setup in Figure B-2: From Network Tester
port 1, send packets with VLAN 1002 & inner
VLAN 102; from Network Tester port 7, send
packets with VLAN 102.
7 To test SHDSL traffic, send from both traffic The traffic passes without errors or packet loss.
generators for at least 15 minutes: Untagged
frames with frame size 1500 bytes, rate 10 Mbps
between UUT-5 port 3 and UUT-6 port 3.
B-10 Testing Basic Functionality ETX-2

8 Set up SNTP servers and ping them The servers reply to ping.
9 Check date and time status in UUTs. The date and time is according to the SNTP server.
10 Verify status of all MEPs. Verify that all MEPs are OK, e.g.:
• Operational status is OK.
• No defects are displayed.
• Remote MEP address matches the remote device MAC
address.
11 Clear alarm logs in all devices. Logs are empty with no active alarms.
B.5 Testing ERP

This test verifies the Ethernet Ring Protection (ERP) functionality.
Estimated Duration

See Figure B-2 and Configuring Devices.
ETX-2 Testing ERP B-11

Test Procedure
Notes The term [<slot>/] has the following meaning, according to the UUT:
• ETX203AX or ETX205A – empty, e.g. [<slot>/]1 = 1
• ETX203AM –1/ (must have a GbE network module)
• ETX220A –4/
1 In UUT-1, check the ERP status. The ERP status in UUT-1 indicates:
• East port: [<slot>/]1
• West port: [<slot>/]2
• RPL link: West
• Ring state: Idle
• East port status: Forward
• West port status: Block R-APS and Data
• Local SF source: OK
• Local SF source: OK
2 Test ring with reversion to active link: In • Traffic packets are not lost during the five minutes that it takes
UUT-1, disconnect port eth [<slot>/]1, start for the ring to reroute traffic.
Ethernet traffic, and then reconnect • During the first five minutes, the ERP status in UUT-1 indicates
port eth [<slot>/]1. that the West port status has changed to Forward:
 East port: [<slot>/]1
 West port: [<slot>/]2
 RPL link: West
 Ring state: Pending
 East port status: Block R-APS and Data
 West port status: Forward
 Local SF source: OK
B-12 Testing ERP ETX-2

3 Wait 5 minutes • Traffic packets are not lost.

• After five minutes, the ERP status in UUT-1 indicates that the East
port status has changed back to Forward, as it was in step 1:
 RPL link: West
 Ring state: Idle
 East port status: Forward
 West port status: Block R-APS and Data
4 Test ring with nonreversion to active link: In The ERP is set to not revert back to the active link when the failure is
UUT-1, enter no revertive in the level config cleared.
protection erp 1 major .
5 In UUT-1, disconnect and then reconnect • Traffic packets are not lost.
port eth [<slot>/]1. • The ERP status in UUT-1 indicates that the West port status has
changed to Forward:
 RPL link: West
ETX-2 Testing ERP B-13

6 Wait five minutes. • Traffic packets are not lost.

• After five minutes, the ERP status in UUT-1 indicates that the
West port status is still Forward:
 RPL link: West
7 In UUT-1, disconnect and then reconnect • Traffic packets are not lost.
port eth [<slot>/]2. • The ERP status in UUT-1 indicates that the East port status has
changed to Forward:
 RPL link: West
B-14 Testing ERP ETX-2

8 Wait five minutes. • Traffic packets are not lost.

• The ERP status in UUT-1 indicates that the East port status is still
Forward:
 RPL link: West
9 Configure the ring with reversion to active link: The ERP is set to revert back to the active link when the failure is
In UUT-1, enter revertive in the level config cleared.
protection erp 1 major.
B.6 Testing LAG

This test verifies the LAG functionality.
Estimated Duration

ETX-2 Testing LAG B-15

Test Procedure
1 Run Ethernet traffic between Network Tester In UUT-1, verify the following:
port 1 and Network Tester port 5: For • Ethernet traffic is running with no errors or packet loss.
example, send:
• UUT-1 replies to ping.
• From Network Tester port 1: Frames with
• Telnet session to UUT-1 can be established.
VLAN 301, at rate 9 Mbps
• MEPs 12–18 have operational status set to OK.
VLAN 541
VLAN 4001, at rate 9 Mbps)
2 In UUT-1, disconnect/reconnect the ports in • No errors are detected in data transmission after switchover.
the LAG. • UUT-1 replies to ping.
• MEP’s 12–18 have operational status set to OK.
B.7 Testing Link Protection

This test verifies the link protection functionality.
Estimated Duration

B-16 Testing Link Protection ETX-2

Test Procedure
1 Run Ethernet traffic between Network Tester In UUT-2, verify the following:
port 1 and Network Tester port 5: For • Ethernet traffic is running with no errors or packet loss.
example, send:
VLAN 301, at rate 9 Mbps
VLAN 4001, at rate 9 Mbps)
2 In UUT-2, disconnect port 1. In UUT-2, verify the following:

• Traffic has switched to the backup port, with no errors detected
in data transmission after switchover.
3 In UUT-2, reconnect port 1. In UUT-2, verify the following:

• Traffic has returned to the main port, with no errors detected in
data transmission after switchover.
• Port statistics show that only port 1 counters are incremented.
B.8 Testing OAM (CFM)

This test verifies the functionality of the MEPs.
ETX-2 Testing OAM (CFM) B-17

Estimated Duration

Test Procedure
1 To verify MEP Status when remote MEP is According to the test setup:
down, do the following, according to the test • Test setup in Figure B-1:
setup:
 In UUT-1, display MEP 12 status and verify that operational
• Test setup in Figure B-1: In UUT-2 set status has changed to fail and then to RDI.
MEP 16 to administratively disabled (via
 Verify that the loss of continuity has been indicated in the
command shutdown).
alarm log, as well as at the NMS, for: MD 3 MA 2 MEP 12
• Test setup in Figure B-2: In UUT-2 set R.MEP 16.
MEP 1 to administratively disabled (via
• Test setup in Figure B-2:
command shutdown).
status has changed to fail and then to RDI.
 Verify that the loss of continuity has been indicated in the
alarm log, as well as at the NMS, for: MD 1 MA 1 MEP 1001
R.MEP 1.
B-18 Testing OAM (CFM) ETX-2

2 To verify MEP Status when remote MEP returns According to the test setup:
to up, do the following, according to the test • Test setup in Figure B-1:
setup:
• Test setup in Figure B-1: In UUT-2 set status has returned to OK.
MEP 16 to administratively enabled (via
 Verify that the alarm for loss of continuity was cleared in the
command no shutdown).
alarm log, as well as at the NMS.
• Test setup in Figure B-2: In UUT-2 set
• Test setup in Figure B-2:
MEP 1 to administratively enabled (via
command no shutdown).  In UUT-1, display MEP 1001 status and verify that operational
status has returned to OK.
 Verify that the alarm for loss of continuity was cleared in the
alarm log, as well as at the NMS.
3 Run OAM link trace between the various pairs Link trace is successful.
of MEPs and their corresponding remote MEPs.
4 Run OAM loopback between the various pairs Loopback is successful.

of MEPs and their corresponding remote MEPs
5 To verify service statistics for the test setup in In UUT-1 MEP 1 verify that for service 1 statistics:
Figure B-1, do the following: • Far end Tx and Rx Frames=Network Tester port 1 total Tx frames
• In UUT-1 MEP 1 clear the statistics for • Near end Tx and Rx Frames=Network Tester port 5 total Tx frames
service 1 and Dest-NE 1.
• Far end lost frames=0
• Run Ethernet traffic for at least 15 minutes
• Near end lost frames=0
from Network Tester port 1 and port 5:
Packets with frame size 1518 bytes, VLAN
4040, at 98% line rate
B.9 Testing RFC-2544

This test verifies the functionality of the RFC-2544 benchmark testing.
ETX-2 Testing RFC-2544 B-19

Estimated Duration

Test Procedure
1 Test throughput for 64-byte frame size: In The test starts.

UUT-1, run the RFC-2544 throughput test that
uses profile 1 (via command config test
rfc2544 test 1 activate).
2 Check the test status (via command show The command output shows that the test is in progress; after about
status). four minutes, the command output shows that the test has
completed.
3 Display the test results (via command show Verify that that measured results match the expected results:
summary). • Success column displays approximately 14%
• Throughput (FPS) column displays a value such that the result of
[FPS × Frame Size × 8] is approximately 30 Mbps.
B.10 Testing Device Reset

This test verifies the correct execution of device reboot, and verifies that all configured entities operate properly after the
reboot.
B-20 Testing Device Reset ETX-2

Estimated Duration

Test Procedure
1 Save the UUT configuration. File is saved successfully.
2 Upload configuration file. File is uploaded successfully.
3 Verify that traffic is running through all relevant Traffic is running without errors or packet loss.
ports.
4 Reboot UUT. • UUT retains its configuration after the reboot.

• The device responds to pings.
• Management access (Telnet/SSH)has been restored.
• Traffic is running error-free.
5 Upload the device configuration file, and compare The uploaded configuration files before and after the reboot are
it to the configuration file uploaded before the the same.
reboot.
ETX-2 Testing Device Reset B-21

B-22 Testing Device Reset ETX-2

Appendix C
Clock Selection and
Management (CSM)
Contents
Clock Selection and Management (CSM).................................................................................... C-1
C.1 Overview ..................................................................................................................... C-2
C.2 Terms and Definitions.................................................................................................. C-2
Timing loop .............................................................................................................. C-2
QL_minimum ............................................................................................................. C-2
Clock-Source Quality-Level ....................................................................................... C-2
Station Clock ............................................................................................................ C-3
Squelch .................................................................................................................... C-3
Synchronous Equipment Clock .................................................................................. C-3
C.3 Abbreviations .............................................................................................................. C-4
C.4 Standards Compliance ................................................................................................. C-6
C.5 CSM Features ............................................................................................................... C-7
C.6 CSM Structure Overview ............................................................................................... C-8
C.7 Detailed Description .................................................................................................... C-9
Clock Domains .......................................................................................................... C-9
Supported Physical Synchronization Interfaces ......................................................... C-9
Clock-Source Quality Levels (QL) Supported ........................................................... C-11
Synchronization Status Messages (SSM) ................................................................. C-15
CSM Selection Process ............................................................................................ C-21
Signal Fail ............................................................................................................... C-22
Hold-Off and Wait-to-Restore Delay Support ......................................................... C-23
Synchronization Source Priorities ........................................................................... C-24
External Commands ................................................................................................ C-25
Automatic Reference Selection Process .................................................................. C-26
Timing Loop Prevention .......................................................................................... C-27
Delay Times ............................................................................................................ C-30
ESMC Support ......................................................................................................... C-31
CSM State Machine ................................................................................................. C-33
C.8 CSM CLI Commands .................................................................................................... C-35
Clock Selection Module Commands ......................................................................... C-35
Clock Client Commands........................................................................................... C-36
Status and Statistics Commands............................................................................. C-36
ETX-2 Contents C-1

Appendix C Clock Selection and Management (CSM) Installation and Operation Manual
C.1 Overview
Note This appendix is applicable only to devices that contain an SEC/EEC clock module
(ETX205A and ETX220A).
This appendix describes RAD’s clock selection and management SW module

version 1.55. The detailed functionality of this module is described as well as the
specific CLI commands that control it.
The specifications in this appendix apply to three regional standards bodies.
When different processing within a single function is required to support the
specific regional processing, this is identified by means of Options I, II and III
processing. "Option I" applies to networks optimized for the 2048 kbit/s
hierarchy. "Option II" applies to networks optimized for the 1544 kbit/s hierarchy.
"Option III" applies to networks optimized for the 1544 kbit/s hierarchy.
The SSM based clock selection algorithm specified in this appendix is only
generally applicable to SEC/EEC (Recommendation G.813 and G.8262) clock
equipment.
C.2 Terms and Definitions
Timing loop
This is a network condition where a slave clock providing synchronization
becomes locked to its own timing signal. It is generally created when the slave
clock timing information is looped back to its own input, either directly or via
other network equipments. Timing loops should be prevented in networks by
careful network design.
QL_minimum
QL_minimum is a user configurable parameter used in the squelching of clock
output signals. If the QL of the signal used to derive the output falls below
QL_minimum then the output is squelched (cut-off or set to AIS).
Clock-Source Quality-Level
The clock-source quality-level of a SEC or SASE is defined as the grade of clock to
which it is ultimately traceable; i.e. the grade-of-clock to which it is synchronized
directly or indirectly via a chain of SECs, and SASEs however long this chain of
clocks is. For example, the clock-source quality-level may be a Primary Reference
Clock complying with Recommendation G.811, or it may be a Slave Clock in
holdover-mode, complying with Recommendation G.812, or a Recommendation
G.813 or G.8262 Clock in holdover or free-run.
The clock-source quality-level is essentially, therefore, an indication only of the
long-term accuracy of the NE Clock.
C-2 Overview ETX-2

Installation and Operation Manual Appendix C Clock Selection and Management (CSM)
Station Clock
This is a node clock as defined in Recommendation G.810.
The functional definitions are given in Recommendation G.783.
The symbols and diagrammatic conventions are given in Recommendation G.783.
Squelch
An action that cuts-off (i.e. shuts down) an output signal. For some signals
(e.g. 2 Mbit/s) squelching may be realized by means of inserting AIS, instead of
shutting down the signal.
Synchronous Equipment Clock

A generic term representing both the SDH Equipment Clock (G.813) and the
Ethernet Equipment Clock (G.8262).
ETX-2 Terms and Definitions C-3

C.3 Abbreviations
This appendix uses the following abbreviations:
AIS Alarm Indication Signal
BITS Building Integrated Timing Supply
CI Characteristic Information
CK Clock signal (Timing information)
CLR Clear
CS Clock Source (Timing information)
CSid Clock Source identifier
DNU Do Not Use
DUS Don't Use for Sync
ESF Extended Super Frame
ESMC Ethernet Synchronization messaging Channel
ESSM Ethernet Synchronization Status Messages
FSw Forced Switch
HO Hold Off time
HO HoldOver mode
ID IDentifier
LO Lockout
LO Locked mode
LOS Loss Of Signal
LSB Least Significant Bit
MSB Most Significant Bit
MSw Manual Switch
NE Network Element
NSUPP Not supported
PDH Plesiochronous Digital Hierarchy
PRC Primary Reference Clock
PRS Primary Reference Source
QL Quality Level
SASE Stand Alone Synchronization Equipment
SDH Synchronous Digital Hierarchy
SEC Synchronous Equipment Clock
SF Signal Fail
SMC SONET Minimum Clock
SQLCH Squelch
SSF Server Signal Fail
C-4 Abbreviations ETX-2

SSM Synchronization Status Message

SSU Synchronization Supply Unit
SSU-A primary level SSU
SSU-B second level SSU
ST2 Stratum 2
ST3 Stratum 3
ST3E Stratum 3 Enhanced
ST4 Stratum 4
STM-N Synchronous Transport Module, level N
STU Synchronization Traceability Unknown
UNC UNConnected
UNK Unknown
WTR Wait to Restore
ETX-2 Abbreviations C-5

C.4 Standards Compliance

[1] ITU-T Recommendation G.703 (1998), Physical/electrical characteristics of hierarchical digital
interfaces
[2] ITU-T Recommendation G.704 (1998), Synchronous frame structures used at 1544, 6312,
2048, 8448 and 44 736 kbit/s hierarchical levels
[3] CCITT Recommendation G.706 (1991), Frame alignment and cyclic redundancy check (CRC)
procedures relating to basic frame structures defined in Recommendation G.704
[4] ITU-T Recommendation G.707 (1996), Network node interface for the synchronous digital
hierarchy (SDH)
[5] ITU-T Recommendation G.783 (1997), Characteristics of synchronous digital hierarchy (SDH)
equipment functional blocks
[6] ITU-T Recommendation G.803 (1997), Architecture of transport networks based on the
synchronous digital hierarchy (SDH)
[7] ITU-T Recommendation G.810 (1996), Definitions and terminology for synchronization
networks
[8] ITU-T Recommendation G.811 (1997), Timing characteristics of primary reference clocks
[9] ITU-T Recommendation G.812 (1998), Timing requirements of slave clocks suitable for use
as node clocks in synchronization networks
[10] ITU-T Recommendation G.813 (1996), Timing characteristics of SDH equipment slave
clocks (SEC)
[11] ITU-T Recommendation G.8261 (2006), Timing and synchronization aspects in packet
networks
[12] ITU-T Recommendation G.8262 (2007), Timing characteristics of Synchronous Ethernet
Equipment slave clock (EEC)
[13] ITU-T Recommendation G.8264 (2008), Distribution of timing through packet networks
[14] IEEE Standard 802.3 TM -2005, Part3, CSMA/CD access method and physical layer
specifications
[15] DS3102 Stratum 3 Timing Card IC with Synchronous Ethernet Support data sheet
C-6 Standards Compliance ETX-2

C.5 CSM Features

The clock selection & management SW module described in this appendix is
integrated in every RAD device that comprises an SEC/EEC clock module and
constitutes the upper SW control and management plane for such modules. It is
largely based on the ITU-T G.781 standard and presents the following features:
(1) Selects the best synchronization reference for the equipment system clock
among a group of assigned synchronization sources (physical or higher-layer
ports).
(2) Accepts legitimate user preferences and acts accordingly.
(3) Controls the different clock routing HW modules such as the assigned
synchronization references HW MUXs and the main clock processing HW
(central timing module).
(4) Supports input clock synchronization frequency and activity monitoring.
(5) Only one clock domain is supported per SW module.
(6) Manages all SSM processing in the equipment (QL interception and
generation).
(7) Supports timing loop prevention.
(8) Supports QL-enabled and QL-disabled modes of operation.
(9) Supports option I, II, and III regional requirements (only one option is
supported at a time according to user configuration).
(10) Supports CLI and SNMP management.
ETX-2 CSM Features C-7

C.6 CSM Structure Overview

RAD CSM general block diagram is shown in Figure C-1. RAD CSM General Block
Diagram
RAD CSM is basically comprised of five major components:
• A SEC/EEC clock module implemented in HW.
• Data ports HW based on the specific product attributes. The data ports can
be legacy TDM/SDH or more modern Synchronous Ethernet capable Ethernet
ports (FE/GE).
• Logical higher layers clock distribution scheme ports (e.g. PTP) that can be
used either as a synchronization source to the CSM (e.g. output of a PTP
slave) or as an outgoing synchronization source from the CSM (e.g. input to a
PTP master). (Not shown in the figure below).
• A dedicated external clock input/output port HW. This port can be either a
standard E1/T1 port (dedicated for sync) or an analog 2.048MHz port (T12).
• A CSM control SW that controls the various HW components and the clock
selection process based on ITU-T Recommendation G.781
Figure C-1. RAD CSM General Block Diagram
RAD CSM can support up to eight synchronization sources (including the T3

external input clock interface) simultaneously supplied to the SEC/EEC input clock
interfaces. Based on the control CSM SW configuration the SEC/EEC performs the
physical clock selection, hitless switching, filtering and holdover. The SEC/EEC HW
comprises two internal DPLL blocks (not shown in the figure) dedicated for the
T0 (system clock) and T4 (external clock) output interfaces. The T0 output
interface is used to frequency lock the outgoing data links and possibly a higher-
layer clock distribution function (e.g. PTP master), while the T4 output interface is
used to frequency lock the external clock output port.
C-8 CSM Structure Overview ETX-2

The CSM control SW runs all the G.781 based attributes such as the clock
selection algorithms, external user commands etc. It receives and transmits
Quality Level (QL) and Server Signal Fail (SSF) information from/to the relevant
data and external clock ports. It is also responsible for correctly configuring the
SEC/EEC according to the relevant standards and user preferences (e.g. G.8262
option I…).
C.7 Detailed Description
Clock Domains
The CSM module supports one clock domain (one primary long-term frequency
source) only. In products that require to support multiple clock domains (e.g. to
support multiple service providers, each having its own primary long-term
frequency source), multiple instances of the CSM module are required.
The clock domain ID shall be configured by the user using the following CLI
command:
configure >system>clock> domain <id> // <id> - domain number
Supported Physical Synchronization Interfaces

Synchronization trails can be carried through the network by a number of
interfaces. The following physical synchronization interfaces are supported:
Option I Synchronization Networking

Traffic interfaces:
• 2048 kHz (T12) 1;
• 2048 kbit/s (E12+P12s)
Dedicated sync interfaces:
• 155 520 kbit/s (OS1 (or ES1)+RS1+MS1);
• 2048 kbit/s (E12+P12s)
• 100 000 kbit/s (ETY2[+ETH])
• 1 000 000 kbit/s (ETY3[+ETH])
• 10 000 000 kbit/s (ETY4[+ETH])
Note
ETYn synchronization interfaces are full duplex with continuous bit stream, as
specified in G.8262.
Option II Synchronization Networking

Traffic interfaces:
1
For more information regarding the terms in brackets see ITU-T
G.703/G.704/G.781.
ETX-2 Detailed Description C-9

• 1544 kbit/s (E11+P11s);

• 155 520 kbit/s (OS1 (or ES1)+RS1+MS1);
• 1544 kbit/s (E11+P11s)
• 100 000 kbit/s (ETY2[+ETH])
• 1 000 000 kbit/s (ETY3[+ETH])
• 10 000 000 kbit/s (ETY4[+ETH])
Note
specified in G.8262.
Option III Synchronization Networking

Traffic interfaces:
• 155 520 kbit/s (OS1 (or ES1)+RS1+MS1)
• 100 000 kbit/s (ETY2[+ETH])
• 1 000 000 kbit/s (ETY3[+ETH])
• 10 000 000 kbit/s (ETY4[+ETH])
Note
specified in G.8262
STM-N
The STM-N transport signals carry (in addition to the payload) reference timing
information and an indication of the quality level of the source generating this
timing information, via the Synchronization Status Message (SSM) as defined in
Recommendation G.707.
2 Mbit/s (E1)
The 2 Mbit/s transport signals may carry (in addition to the payload) reference
timing information.
The 2 Mbit/s timing reference signals (without payload) carry reference timing
information to specific synchronization ports.
Both signals can carry an indication of the quality level of the source generating
the timing information via the SSM as specified in Recommendation G.704.
2 MHz (T12)
Synchronization can be carried through 2 MHz signals to specific synchronization
ports (so called station clock ports). This signal does not carry an indication of
the quality level of the source generating the timing information.
1.5 Mbit/s (T1)

The 1.5 Mbit/s transport signals may carry (in addition to the payload) reference
timing information.
The 1.5 Mbit/s timing reference signals (without payload) carry reference timing
information to specific synchronization ports.
C-10 Detailed Description ETX-2

Both signals can carry an indication of the quality level of the source generating
the timing information via the SSM transported within the 1544 kbit/s signal's
Extended Super Frame (ESF) Data Link (DL) as specified in Recommendation
G.704.
100 Mbit/s, 1 Gbit/s, 10 Gbit/s

The 802.3 transport signals may carry (in addition to the payload) reference
timing information and an indication of the quality level of the source generating
this timing information, via the Synchronization Status Message (SSM) as defined
in ITU-T Recommendation G.8264.
Notes • Equipment developed prior to this first revision of the Recommendation may
not be able to carry reference timing information and/or support SSM via its
802.3 interfaces
• The equipment can have both nonsynchronous and synchronous 802.3
interfaces as defined in G.8264. Nonsynchronous 802.3 interfaces are
excluded from the synchronization distribution process
The relevant synchronization input/output ports (type and ID) that are to take
part in the clock selection process are user configured using the following CLI
command:
configure >system>clock>domain (id)#[no] source <src-id> {type}
[<id>] [{port type} <port-index>]
// type - {domain <domain-id>| rx-port {port-type}
<port-index>| station <station-id> | recovered
<recovered-id>}.
// rx-port {port-type} - E1, T1, Ethernet, SDH/SONET.
Note
For further details regarding the specific CLI structure, refer to Chapter 4
Clock-Source Quality Levels (QL) Supported
Clock-Source Quality-Level Definitions

SDH and packet transport networks throughout the world are based on different
synchronization philosophies. Those differences are identified as three Options: I,
II, and III in the relevant standards and are all supported by the CSM SW module.
The relevant network option shall be configured by the user using the following
CLI command:
configure >system>clock>domain (id)# sync-network { type-1 | type-2 | type-3 }
// default type-2A change in the sync-network Type configuration can only take
place if no clock sources are configured. An attempt to change the sync-network
Type when one or more clock sources are configured in the system result in the
following error message:
‘Existing sources should be removed first’
Thus, before changing the sync-network Type, the user must delete all configured
clock sources.


The following clock source quality levels are defined in the CSM synchronization
process of Option I network corresponding to 4 levels of synchronization quality
(based in ITU-T Recommendation G.803).
QL-PRC This synchronization trail transports a timing quality

generated by a Primary Reference Clock that is
defined in Recommendation G.811.
QL-SSU-A This synchronization trail transports a timing quality
generated by Types I or V slave clock that is defined
in Recommendation G.812.
QL-SSU-B This synchronization trail transports a timing quality
generated by a Type VI slave clock that is defined in
QL-SEC This synchronization trail transports a timing quality
generated by a Synchronous Equipment Clock (SEC)
that is defined in Recommendation G.813 or G.8262,
Option I.
QL-DNU This signal should not be used for synchronization.

Clock source quality levels of Option II networks have been expanded from 7
levels to 9 levels. The 7 quality level set is referred to as First generation and the
new 9 quality level set is referred to as Second generation. First generation
quality levels are a subset of Second generation.
Note RAD equipment is always defined as second generation equipment.
The following clock source quality levels are defined in the CSM synchronization
selection process of Option II network corresponding to Second generation.
QL-PRS PRS traceable (Recommendation G.811)
QL-STU Synchronized – Traceability Unknown
QL-ST2 Traceable to Stratum 2 (Recommendation G.812, Type II)
QL-TNC Traceable to Transit Node Clock (Recommendation G.812, Type V)
QL-ST3E Traceable to Stratum 3E (Recommendation G.812, Type III)
QL-ST3 Traceable to Stratum 3 (Recommendation G.812, Type IV)
QL-SMC Traceable to SONET Clock Self Timed (Recommendation G.813 or
G.8262, Option II)
QL-ST4 Traceable to Stratum 4 Freerun (only applicable to 1.5 Mbit/s
signals)
QL-PROV Provisionable by the Network Operator
QL-DUS This signal should not be used for synchronization.

The following clock source quality levels are defined in the synchronization
process of Option III SDH network corresponding to 2 levels of synchronization
quality.

QL-UNK This synchronization trail transports a timing quality

generated by an unknown clock source. It is at least of
quality SSU.
QL-SEC This synchronization trail transports a timing quality
generated by a Synchronous Equipment Clock (SEC) that is
defined in ITU-T Recommendation G.813 or G.8262, Option I.
External Synchronization Interface Output (T4) Squelching

The CSM module supports ‘squelching’ of the external synchronization interface
output. The first purpose of the "squelch" function is to prevent transmission of
a timing signal with a quality that is lower than the quality of the clock in the
receiving network element or SASE. It is also used for the prevention of timing
loops.
Squelching is done according to the user configured QL_minimum value, by
comparing this user configured value to the reported quality level of the current
selected synchronization source.
Note Squelching (signal cutoff) is applicable only for 2.048 MHz (T12) clock interfaces.
In case 2.048 Kb/s (E1) or 1.544 Kb/s (T1) are used, upon a ‘squelching’ event
the interface would start transmitting AIS.
Supported Hierarchy of Clock-Sources Quality Levels (QL)

The following tables define the QL hierarchy.
Table C-1. Hierarchy of quality levels in Option I
Quality Level Order
QL-PRC highest
QL-SSU-A |
QL-SSU-B |
QL-SEC |
QL-DNU |
QL-INVx, -FAILED, -UNC, -NSUPP lowest
Note
The quality levels QL-INVx, QL-FAILED, QL-UNC and QL-NSUPP are internal QLs
inside the NE and are never generated at an output port.

Table C-2. Hierarchy of quality levels in Option II
Quality Level Order
QL-PRS highest
QL-STU |
QL-ST2 |
QL-TNC (See note) |
QL-ST3E (See note) |
QL-ST3 |
QL-SMC |
QL-ST4 |
QL-PROV (default position) |
QL-DUS |
Note
The quality level QL-PROV is provisionable by the network operator and may take
different order positions. The default position for QL-PROV is as shown in
Table C-2.
Note The implementation in RAD CSM always assumes this default position for
QL-PROV.
Table C-3. Hierarchy of quality levels in Option III
Quality Level Order
QL-UNK highest
QL-SEC |
Note
Forcing and Defaulting Clock-Source Quality-Levels

For synchronization source signals/interfaces not supporting SSM
transport/processing, it is possible to force the quality level to a fixed provisioned

value. This allows using these signals/interfaces as synchronization sources in an

automatic reference selection process operating in QL-enabled mode.
Forcing of quality levels is used for new equipment operating in QL-enabled mode
in order to:
• Interwork with old equipment not supporting SSM generation
• Interwork with new equipment operating in QL-disabled mode
• Select interfaces not supporting SSM processing
• Select signals for which SSM is not defined (e.g. 2 MHz)
Note Valid SSM synchronization sources can also be overwritten using the ‘Force QL’
procedure.
In RAD CSM, when working in QL-enabled mode, the user must configure (‘force’)
a specific QL level for all the ingress synchronization interfaces (assigned sync
sources) that does not support SSM (outputting the default QL-NSUPP).
A synchronization source issuing signal fail (SSF) cannot be QL overwritten by
user configuration (QL_FAILED is always distributed to the selection algorithm).

The quality level of the input signal (STM-N, 2 Mbit/s, 2 MHz) can be forced to
either QL-PRC, QL-SSU-A, QL-SSU-B or QL-SEC.

The quality level of the input signal can be forced to either QL-PRS, QL-STU,
QL-ST2, QL-TNC, QL-ST3E, QL-ST3, QL-SMC, QL-ST4, QL-PROV or QL-DUS.

The quality level of the input signal can be forced to either QL-UNK or QL-SEC.
Synchronization Status Messages (SSM)

The following supported signals have a four-bit SSM channel defined:
• STM-N (N = 1, 4, 16) – bits 5 to 8 of the byte S1 (called SSMB,
Synchronization Status Message Byte) of the multiplex section overhead as
defined in Recommendation G.707
• 2 Mbit/s octet structured according to Recommendation G.704: bits Sax1 to

Sax4 (x = 4, 5, 6, 7, or 8) of TS0
• 1.5 Mbit/s octet structured according to 2.1/G.704
• 100 Mbit/s, 1 Gbit/s, 10 Gbit/s as defined in IEEE Std. 802.3: 4-bit SSM field in
the SSM PDU as defined in Recommendation G.8264
SSM Message Sets

Five SSM codes are defined to represent clock source QL as listed below:

• Code 0010 (Quality PRC) means that the source of the trail is a PRC clock
(Recommendation G.811).
• Code 0100 (Quality SSU-A), means that the source of the trail is a Type I or V
SSU clock as defined in Recommendation G.812.
• Code 1000 (Quality SSU-B), means that the source of the trail is a Type VI
SSU clock (Recommendation G.812).
• Code 1011 (Quality SEC), means that the source of the trail is a SEC clock
(Recommendation G.813 or G.8262, Option I).
• Code 1111 (quality DNU), means that the signal carrying this SSM shall not be
used for synchronization because a timing loop situation could result if it is
used.

Nine SSM codes are defined to represent clock source QL as listed below on STM-
N signals:
• Code 0001 (Quality PRS) means that the source of the trail is a PRS clock
• Code 0000 (Quality STU) means that the signal does not carry the QL
message of the source of the trail.
• Code 0111 (Quality ST2), means that the source of the trail is a Stratum 2
clock (Recommendation G.812, Type II).
• Code 0100 (Quality TNC), means that the source of the trail is a Transit Node
Clock (Recommendation G.812, Type V).
• Code 1101 (Quality ST3E), means that the source of the trail is a stratum 3E
clock (Recommendation G.812, Type III).
• Code 1010 (Quality ST3), means that the source of the trail is a stratum 3
clock (Recommendation G.812, Type IV).
• Code 1100 (Quality SMC), means that the source of the trail is a
SONET/Ethernet self timed clock (Recommendation G.813 or G.8262, Option
II).
• Code 1110 (Quality PROV), is provisionable by the network operator.
• Code 1111 (Quality DUS), means that the signal carrying this SSM shall not be
used.
Ten SSM codes are defined to represent clock source QL as listed below on
1544 kbit/s signals:
• Code 04FFH (Quality PRS) means that the source of the trail is a PRS clock
• Code 08FFH (Quality Unknown) means that the source of the trail is unknown.
• Code 0CFFH (Quality ST2) means that the source of the trail is a Stratum 2
clock (Recommendation G.812, Type II).
• Code 78FFH (Quality TNC) means that the source of the trail is a Transit Node
Clock (Recommendation G.812, Type V).

• Code 7CFFH (Quality ST3E) means that the source of the trail is a Stratum 3E
clock (Recommendation G.812, Type III).
• Code 10FFH (Quality ST3) means that the source of the trail is a Stratum 3
clock (Recommendation G.812, Type IV).
• Code 22FFH (Quality SMC) means that the source of the trail is a
SONET/Ethernet self-timed clock (Recommendation G.813 or G.8262, Option
II).
• Code 28FFH (Quality ST4) means that the source of the trail is a Stratum 4
clock.
• Code 40FFH (Quality PROV) is provisionable by the network operator.
• Code 30FFH (Quality DUS) means that the signal carrying this SSM shall not be
used.

Two SSM codes are defined to represent clock source QL as listed below:
• Code 0000 (Quality Unknown) means that the source of the trail is unknown.
• Code 1011 (Quality SEC) means that the source of the trail is a SEC clock
(Recommendation G.813 or G.8262, Option I).
SSM Code Word Generation (SSM Tx Function)

The SSM can be viewed as an application specific data communication channel
with a limited message set. The message is generated and inserted depending on
the applied selected reference quality level indication. The following tables
present the relation between the existing set of QLs and SSM codes generation
for the three options.
In the CSM module it is possible to disable the SSM Tx function , generation and
inserting "1111", independently for each interface. An application for this could
be e.g. at network boundaries where timing information should not be forwarded
to the other network.
Note SSM disable for an Ethernet port causes it to stop transmitting ESMC frames.
Table C-4. Quality Level Set and Coding in Synchronization Status Message in Option I
Synchronization Networks
Quality Level (QL) SSM usage SSM coding [MSB..LSB]
QL-PRC enabled 0010
QL-SSU-A enabled 0100
QL-SSU-B enabled 1000
QL-SEC enabled 1011
QL-DNU enabled 1111

– disabled 1111
Table C-5. Quality Level Set and Coding in Synchronization Status Message in Option II
Quality SSM usage Second Generation SSM

Level (QL)
SSM SSM
coding [MSB..LS coding [MSB..LS
B] in STM-N B] in 1544
signal kbit/s signal
(BINARY) with ESF (HEX)
QL-PRS enabled 0001 04FF
QL-STU enabled 0000 08FF
QL-ST2 enabled 0111 0CFF
QL-TNC enabled 0100 78FF
QL-ST3E enabled 1101 7CFF
QL-ST3 enabled 1010 10FF
QL-SIC enabled 1100 22FF
QL-ST4 enabled – 28FF
QL-PROV enabled 1110 40FF
QL-DUS enabled 1111 30FF
– disabled 1111 08FF
Table C-6. Quality Level Set and Coding in Synchronization Status Message in Option III
Quality Level (QL) SSM coding [MSB..LSB]
QL-UNK 0000
QL-SEC 1011
SSM Code Word Interpretation (SSM Rx Function)

At the receive side, the received SSM bits are to be validated by a persistency
check and then interpreted to determine the QL.

Table C-7. Interpretation of Synchronization Status Message Codes in Option I Synchronization

Networks
SSM code [MSB..LSB] QL interpretation
0000 QL-INV0
0001 QL-INV1
0010 QL-PRC
0011 QL-INV3
0100 QL-SSU-A
0101 QL-INV5
0110 QL-INV6
0111 QL-INV7
1000 QL-SSU-B
1001 QL-INV9
1010 QL-INV10
1011 QL-SEC
1100 QL-INV12
1101 QL-INV13
1110 QL-INV14
1111 QL-DNU
Table C-8. Interpretation of Synchronization Status Message Codes in STM N Signals in Option II
SSM code [MSB..LSB] in STM-N signals QL interpretation
0000 QL-STU
0001 QL-PRS
0010 QL-INV2
0011 QL-INV3
0100 QL-TNC
0101 QL-INV5
0110 QL-INV6
0111 QL-ST2
1000 QL-INV8

SSM code [MSB..LSB] in STM-N signals QL interpretation
1001 QL-INV9
1010 QL-ST3
1011 QL-INV11
1100 QL-SMC
1101 QL-ST3E
1110 QL-PROV
1111 QL-DUS
Table C-9. Interpretation of Synchronization Status Message Codes in 1544 kbit/s Signals in Option
II Synchronization Networks
SSM code in 1544 kbit/s signals QL interpretation
0xxx xxx0 1111 1111 HEX --
000 010 04FF QL-PRS
000 100 08FF QL-STU
000 110 0CFF QL-ST2
111 100 78FF QL-TNC
111 110 7CFF QL-ST3E
001 000 10FF QL-ST3
010 001 22FF QL-SMC
010 100 28FF QL-ST4
011 000 30FF QL-DUS
100 000 40FF QL-PROV
other (see Note 1) other (see Note 1) QL-INV
Table C-10. Interpretation of Synchronization Status Message Codes in Option III Synchronization
Networks
0000 QL-UNK
0001 QL-INV1
0010 QL-INV2
0011 QL-INV3
0100 QL-INV4
0101 QL-INV5

0110 QL-INV6
0111 QL-INV7
1000 QL-INV8
1001 QL-INV9
1010 QL-INV10
1011 QL-SEC
1100 QL-INV12
1101 QL-INV13
1110 QL-INV14
1111s QL-INV15
Note
Interworking between Option I and II, Option I and III and Option II and III
synchronization networks is not defined.
CSM Selection Process

The process of selecting a synchronization source from the set of physical ports
is performed in three steps plus one for use of the station clock output:
Figure C-2. Visualization of the Synchronization Source Selection Process(Es)
1. Assignment of a physical port to be a synchronization source: Select a

(limited) set of interface signals (from the total set of interfaces) to act as
synchronization sources. This is performed by means of adding a fixed (not
changing during runtime) physical mapping between a group of inputs
(connected to the transport layer) and outputs (connected to the SEC/EEC
device). This functionality is usually realized by HW MUXs that are SW

managed according to user preferences. Generally speaking, only the

assigned synchronization sources take part in the automatic selection
process. In other words, a synchronization source that has not been mapped
into the assigned group of sources, cannot be used as a synchronization
reference.
2. Nomination of a synchronization source for an automatic selection process:
Select a subset of the synchronization sources to contribute to a selection
process. This is performed in the CSM by means of assigning a priority to the
synchronization source. Under any circumstance, the T3 synchronization
source cannot be nominated for T4 selection process.
3. Automatic Selection Process: Selects the "best" synchronization source of the
set from nominated sources according to the selection algorithm. Two
independently selection process for T0 and T4 are being carried.
Signal Fail
RAD CSM supports three levels (or sources) of signal fail triggering:
1. Signal fail for a synchronization source is activated in case of defects
detected in the transport layers. In addition an unconnected synchronization
signal has also signal fail active in order to allow correct processing in the QL
disabled mode.
2. Inclusion of specific synchronization failures conditions based on dedicated
detection mechanism embedded within the SEC/EEC device are also
supported. More specifically, RAD’s SEC/EEC implementation is capable of
detecting a large frequency deviation, beyond a pre-configured threshold, as
well as lack of activity on each one of the assigned synchronization sources.
Those alarm indications are also used to issue a Server Signal Fail (SSF) signal
towards the CSM.
An SSF signal is issued by the SEC/EEC HW in the following cases:
 Activity alarm (leaky bucket mechanism). The configuration of the activity
detector is fixed and preconfigured for all RAD products.
 10,000 ppm coarse frequency monitoring (fixed for all RAD products).
 User configured HARD limit frequency monitoring. The user can configure
a HARD frequency limit within the range of ±3.81 ppm to ±60.96 ppm in
0.01 ppm steps using the following CLI command:
configure >system>clock>domain (id)># max-frequency-deviation
<value>
3. Synchronous Ethernet ports that fail to receive a valid ESMC message
immediately for a period of 5 seconds, issue a signal fail indication.
In order to avoid reactions on short pulses or intermittent signal fail information,
the signal fail information is passed through a hold-off and wait-to-restore
processes before it is considered by the selection process.
In QL enabled mode the QL of a synchronization source with active signal fail is
set to QL-FAILED. The selection process reacted to this QL value instead of the
signal fail signal in this mode.

When it comes to the user failure indications for a specific clock source, the
priority of presenting the specific SSF event cause is as follows:
1. A problem reported by the PHY (physical-fail)
2. Violation of the HARD frequency limit (monitoring-fail)
3. Lack of ESMC messages reception (if the interface is an Ethernet one) (esmc-
fail)
In other words, a violation of the HARD frequency limit would mask a concurrent
ESMC messages timeout indication. A problem reported from the PHY would mask
both concurrent HARD frequency violation and ESMC messages timeout
indications.
It should be stressed again that only the user indication would be masked, not
the actual failure signal (SSF). Moreover, new versions of CSM support
dedicated/independent user indications for each cause.
Hold-Off and Wait-to-Restore Delay Support
Hold-Off Time
The hold-off time ensures that short activation of signal fail is not passed to the
selection process.
In QL-disabled mode signal fail is active for the hold-off time before it is passed
to the selection process.
In QL-enabled mode a QL value of QL-FAILED exists for the hold-off time before it
is passed to the selection process. In the mean time the previous QL value is
passed to the selection process.
Note Other QL values than QL-FAILED are passed to the selection process immediately.
Separate hold-off timers are used for each input to a selection process
(nominated source). The hold-off time is user configured within the range of 300
ms to 1800 ms using the following CLI command:
configure >system>clock>domain (id)> source (src-id)# hold-off
<seconds>
Wait-to-Restore Time
The wait to restore time ensures that a previous failed synchronization source is
only again considered as available by the selection process if it is fault free for a
certain time.
In QL-disabled mode after deactivation of signal fail, it remains false for the wait
to restore time before signal fail false is passed to the selection process. In the
meantime, signal fail true is passed to the selection process.
In QL-enabled mode after a change of the quality level from QL-FAILED to any
other value, the quality value QL-FAILED is maintained for the wait to restore
time before the new QL value is passed to the selection process. In the
meantime, the quality level QL-FAILED is passed to the selection process.

Separate wait to restore timers are used for each input to a selection process
(nominated source).
The wait to restore time is user configurable (user configuration) in the range of
0 to 12 minutes in steps of 1 minute for all inputs of the selection process in
common using the following CLI command. The default value is 5 minutes.
configure >system>clock>domain (id)> source (src-id)#
wait-to-restore <seconds>
Each wait to restore timer can be cleared with a separate (user) Clear command
using the CLI command shown below. If a wait to restore timer is cleared the new
QL value (in QL-enabled mode), or signal fail value (in QL-disabled mode), is
immediately passed to the selection process.
configure >system>clock>domain (id)> source (src-id)#
wait-to-restore-clear //command
A new WTR state status was added to the source/show status command to
give the user more clarity regarding the current ‘WTR state’ of each
synchronization source.
configure >system>clock>domain (id)> source (src-id)# show status
.
.
.
WTR State : { Inactive | Running }
Synchronization Source Priorities

In order to define a preferred network synchronization flow, priority values are
allocated to assigned synchronization sources within a network element (see
Table C-11).
Different priorities reflect a preference of one synchronization source over the
other. Equal synchronization source priorities reflect that no preference exists
between the synchronization sources.
Within the group of synchronization sources with equal priorities, the selection
process has a non-revertive behavior.
Table C-11. Priority Order
Priority value Order
1 highest
2 |
3 |
: |
K lowest
Disable (no priority) Cannot be used for

clock selection T0/T4

Notes • The priority value is not ordered numerically. The following relation is present:
"1" > "2" > "3" > .. >"K"
• The assigning of equal priorities to synchronization sources, in order to allow
for non-revertive operation, does not allow for a predefined initialization state
of known synchronization configuration following failure of a higher priority
source.
The CSM synchronization source ports priority is configured by the user using the
following CLI command:
configure >system>clock>domain (id)> source (src-id)#no
priority <num> ock-
// If no option is chosen, then this source is not taken to the
selection process
External Commands
Several external commands are available to the user via the product’s
management level (e.g. for maintenance purposes). These commands are
independent and have different impact on the selection processes.
The activation and deactivation of external commands associated with the
synchronization selection process are defined below. Furthermore, only one of
these external commands is active at a time as per the selection process.
Clear Command
A clear (CLR) command clears the forced switch and manual switch commands.
Forced Switch #p Command

A forced switch (FSw) to #p command can be used to override the currently
selected synchronization source, assuming the synchronization source #p is
enabled.
The forced switch overrides the manual switch and a subsequent forced switch
pre-empts the previous forced switch.
If the source selected by the forced switch command (#p) is disabled (using the
‘no priority’ command), the forced switch command is automatically rejected. The
forced switch command can be cleared by the "clear" command.
Note A forced switch command to a synchronization source #p, which is in the SF state
or has a QL of DNU in QL enabled mode, results in the network element entering
holdover.
A new Force switch state status was added to the domain/show status
command to give the user more clarity regarding the current ‘Force switch’ state
of the clock domain.
configure >system>clock>domain (id) # show status
.
.
.
Force Switch: {InActive | Active}

Manual Switch #p Command

A manual switch (MSw) to #p command selects the synchronization source #p,
assuming it is enabled, not in signal fail condition, and has a QL better than DNU
in QL enabled mode. Furthermore, in the QL enabled mode, a manual switch can
be performed only to a source which has the highest available QL. As such, these
conditions have the effect that manual switching can only be used to override the
assigned synchronization source priorities.
A manual switch request overrides a previous manual switch request.
If the source selected by the manual switch command (#p) is in signal fail, or has
a QL of DNU or lower than one of the other source signals, the manual switch
command is automatically rejected.
The manual switch command can be cleared by the "clear" command.
The following CLI commands allow the user to impose external commands on the
CSM:
configure >system>clock>domain (id)# force < source-id >
configure >system>clock>domain (id)# manual < source-id >
configure >system>clock>domain (id)# clear
The Manual switch state status is available under the domain/show status
command to give the user more clarity regarding the current ‘Manual switch’
state of the clock domain.
.
.
.
Manual Switch: {InActive | Active}
Force T4=T0 Set Command

Activating the ‘Force T4 to T0’ command deactivates the T4 DPLL and uses the T0
DPLL to feed both the T0 and T4 output clock paths.
configure >system>clock>domain (id)# [no] force-t4-as-
t0 //project dependent
Automatic Reference Selection Process

One or more reference selection processes operate independently to select the
reference signal for the internal (system) clock (T0) and, where present, the
station clock output(s) (T4).
The selection process(es) can work in two distinct modes: QL-enabled or
QL-disabled. If multiple selection processes are present in a network element, all
processes work in the same mode.
The following is a brief description of the automatic reference selection process.
The relevant QL mode shall be configured by the user using dedicated CLI
commands. To switch the CSM into QL-disabled mode the following CLI command
shall be used:
configure >system>clock>domain (id)# no quality

To switch the CSM back into QL-enabled mode the following CLI command should
be used. Through this CLI command the user also configures the QL_minimum
level used for the T4 ‘squelching’ mechanism.
configure >system>clock>domain (id)# quality min-level {level}
QL-enabled Mode
In QL-enabled mode the following parameters contribute to the selection
process:
• Quality Level
• Signal fail via QL_FAILED
• Priority
• External commands
If no overriding external commands are active, the algorithm selects the reference
with the highest quality level, which is not experiencing a signal fail condition. If
multiple inputs have the same highest quality level, the input with the highest
priority is selected. For the case that multiple inputs have the same highest
priority and quality level, the current existing selected reference is maintained if it
belongs to this group, otherwise an arbitrary reference from this group is
selected.
If no input could be selected, the CSM moves the SEC/EEC to holdover state while
distributing the internal oscillator QL level towards the output synchronization
interfaces (T4 immediately moves to ‘squelch’ mode).
QL-disabled Mode
In QL-disabled mode the following parameters contribute to the selection
process:
• Signal fail
• Priority
• External commands
If no overriding external commands are active, the algorithm selects the reference
with the highest priority which is not experiencing a signal fail condition. For the
case that multiple inputs have the same highest priority, the current existing
selected reference is maintained if it belongs to this group, otherwise an arbitrary
reference from this group is selected.
If no input could be selected, the CSM moves the SEC/EEC to holdover state (T4
immediately moves to ‘squelch’ mode).
Timing Loop Prevention

Timing loops are formed when a clock is traceable to itself. Such a situation can
develop when the synchronization distribution flow in the network losses its pure
tree-like topology, due to an erroneous distribution configuration, and a timing
‘circle’ is formed.
Synchronization network architectures should be designed such that timing loops
do not occur under fault free or failure conditions. Special timing loop prevention

techniques should be used within network elements and SASEs that might open
the potential loop. Some of these are described hereafter that affect the
synchronization distribution functionality within a product.
Between RAD CSM and Network Elements with SEC/EEC Type

Clock
The master-slave synchronization over several NEs with multiple possible
synchronization inputs for protection of synchronization as defined in ITU-T
Recommendation G.803 could lead to timing loops between NEs. To avoid timing
loops the CSM module would insert a SSM value of DNU in direction of the NE
which is used as actual synchronization source for the CSM.
NEx NEy NEz

MI_CSid=1 MI_CSid=3
SSM=0010 input CI_CS=1 CI_CS=3 input
RI_CS=1 RI_CS=3
do not use as SSM=1111 CI_CS=1 CI_CS=1 SSM=0010 can be used as
synchronization output output synchronization
source source
transport MI_CSid=2 MI_CSid=4 transport
ports ports
input input
RI_CS=2 RI_CS=4
SSM=0010 CI_CS=1 CI_CS=1 SSM=0010
output output
T1530620-99
Figure C-3. RAD CSM Automatic DNU Generation Towards NE with SEC/EEC Timing
The clock source identifier CSid has been introduced to support the above feature
as shown in Figure C-3. To each transport and station clock input port a unique
CSid is assigned. This ID is processed in the CSM together with the clock and
quality level of the port. The CSid of the selected source for the SEC/EEC is
distributed to all output ports. If a transport output port receives the same CSid
as its associated input port the outgoing is set to DNU.
Between RAD CSM and NE or SASE/BITS with a SSU/ST2 Clock

RAD’s product can be interconnected with SASE/BITS via its (2 MHz, 2 Mbit/s,
1.5 Mbit/s) station clock input and output ports (unidirectional). If the SASE/BITS
is used as the actual synchronization source for RAD CSM, the mechanism
defined above has to be extended to support automatic DNU insertion also for
this case.
It is not possible to detect that the SASE/BITS has selected the station clock
output port of the NE as actual clock source, but several conditions exist that
indicate that the station clock output port is not used as clock source by the
SASE/BITS.
If a RAD CSM is connected to a SASE/BITS that does not process QL/SSM
information, a squelched/AIS station clock output port is the only criteria that
indicates that the output port is not used as clock source by the SASE/BITS. As
long as the station clock output is not squelched (for 2 MHz station clock ports)
or set to AIS (for 2 Mbit/s station clock ports), it is assumed that the SASE/BITS
selects the station clock output of RAD CSM as reference clock. The station clock

input port uses, in this case, the remote CSid (from the station clock output) as
CSid for the clock signal to the selection process (RI_CS = CI_CS) instead of its
own CSid (MI_CSid). This results in DNU insertion in the traffic output port
associated with the traffic input port used as source for the station clock (see
Figure C-4). If the station clock output is squelched or set to AIS, the remote CSid
is replaced by the own CSid (MI_CSid) and the automatic DNU insertion in the
traffic output port associated with the traffic input port used as source for the
station clock is removed (see Figure C-5).
SASE
station clock
active ports
RI_CS=1
output
MI_CSid=5
input
NEy
NEx NEz
CI_CS=1 CI_CS=1
MI_CSid=1 MI_CSid=3
SSM=0010 CI_CS=1 CI_CS=3
input input
SSM=1111 RI_CS=1 CI_CS=1 CI_CS=1 RI_CS=3 SSM=0010

do not use as output output can be used as
synchronization synchronization
source transport MI_CSid=2 MI_CSid=4 transport source
ports ports
input input

output output
T1530660-99
Figure C-4. Automatic DNU Generation in RAD CSM with SASE/BITS Timing (SSM/QL not Supported)

SASE
station clock
squelched/AIS
ports
RI_CS=none
output
MI_CSid=5
input
NEy
NEx NEz
CI_CS=1 CI_CS=5
MI_CSid=1 MI_CSid=3
SSM=1011 CI_CS=1 CI_CS=3
input input

can be used as output output can be used as
synchronization synchronization
source transport MI_CSid=2 MI_CSid=4 transport source
ports ports
input input

output output
T1530670-99
Figure C-5. Removal of Automatic DNU Generation in RAD CSM with SASE/BITS Timing (SSM/QL not
Supported)
Delay Times
The following delay times are respected by the CSM module:
1. Holdover message delay THM – This delay applies when the CSM (SEC/EEC)
switches to holdover because of loss of signal of the input reference and lack
of any other available reference. When this event occurs, the CSM (and
SEC/EEC) goes immediately into holdover but changes the output SSM to the
holdover code after a delay which has been defined to be between 500 ms
and 2000 ms.
2. Non-switching message delay TNSM – This delay applies when the QL of the
selected synchronization source changes but no switchover to another source
is performed by the CSM. The outgoing SSM follows this change at the input
within a time defined to be less than 200 ms.
3. Switching message delay TSM – This delay applies when a new synchronization
source is selected by the CSM. The output SSM change, if any, is done after a
delay that has been defined to be between 180 ms and 500 ms.

ESMC Support
If the interface type of the clock is Ethernet, that the CSM supports ESSM
(Ethernet SSM) messages transmission and reception for this port as per ITU-T
ESMC Operational Mode Overview

The protocol is related to the slow protocols group defined in [15]. The slow
protocol should transmit not more than 10 frames per second. The protocol PDUs
carry the characteristic of the clock quality as defined in ITU-T Recommendation
G.8264. The quality parameter is encoded as the QL TLV, where the informative
quality element is the SSM code. The SSM codes values for the Ethernet SSM are
defined in ITU-T Recommendation G.8264.
RAD CSM ESMC process transmits a periodic ESMC message each 1 sec and an
immediate event ESMC message per selected synchronization source quality level
change event. The quality information that is encoded in the transmitted ESMC
frames is enquired from the T0 selection process.
At the receiving end, RAD CSM ESMC process supports reception of ESMC frames
as well as informing the clock selection process about the received clock source
quality level. In addition, it maintains the continuity of the ESMC process; that is if
no ESMC message is received during 5 sec time interval the quality level of that
clock source is declared as QL-FAILED (SSF is issued).
ESMC PDU Format
Table C-12. ESMC PDU Format
Octet number Size/bits Field
1-6 6 octets Destination Address =01-80-C2-00-00-02 (hex)
7-12 6 octets Source Address
13-14 2 octets Slow Protocol Ethertype = 88-09 (hex)
15 1 octets Slow Protocol Subtype =0A (hex)
16-18 3 octets ITU-OUI = 00-19-A7 (hex)
19-20 2 octets ITU Subtype
21 bits 7:4 (see Note 1) Version
bit 3 Event flag
bits 2:0 (see Note 2) Reserved
22-24 3 octets Reserved
25-1532 36-1490 octets Data and Padding (See point J)

Last 4 4 octets FCS
Note 1: Bit 7 is the most significant bit of Byte 21. Bit7 to bit 4 (bits 7:4) represent the four bit version
number for the ESMC.
Note 2: The three least significant bits (bits 2:0) are reserved.
ESSM is sent with the slow protocol multicast MAC address (01 80 C2 00 00 02),
slow protocol Ethernet type (8809) and a specific sub type (0x0A). The OUI, ITU
subtype and version field values are shown in Table C-12. The E bit designates
the event that is the QL value changed. The R symbol designates the reserved
field.
The payload of the PDU contains one TLV 2 defined by the standard QL TLV. The
format of this TLV is given in Table C-13.
Table C-13. ESSM TLV Format
1 8 bits Type:0x01
2-3 16 bits Length: 0x0004
4 bits 7:4 0 (unused)
bits 3:0 SSM code
Note 1: Bit 7 of Octet 4is the most significant bit. The least significant nibble, bit 3 to bit 0
(bits 3:0) contain the four bit SSM code.
The codes to be used for Synchronous Ethernet SSM are: EEC1=1011 and
EEC2=1010 as defined in ITU-T Recommendation G.8264.
ESMC Process Functional Requirements

The implementation of the ESMC is fully compliant with ITU-T Recommendation
G.8264. The ESMC process maintains independent receive and transmit state
machines.
The receive state machine is comprised of two states: LOCKED and UNLOCKED.
The state machine enters the LOCKED state once it receives valid ESMC messages.
The state machine enters UNLOCKED state if it doesn’t receive ESMC message
during 5 consecutive seconds. Upon such an event, the ESMC client would send
QL-FAILED quality level towards the selection process. While in LOCKED state, the
last received QL value is maintained. Upon a detection of a QL level change in the
incoming messages, the new QL level is immediately propagated to the selection
process (after going through the required Holdoff delay).
The ESMC client transmits state machine supports periodic transmission of ESMC
frames. The transmitting state machine sends an ESMC message every 1 sec in a
periodic manner. The QL code used in those ESMC messages is enquired from the
T0 clock selection process. The ESMC client sends DNU to the port, whose clock is
currently selected by the T0 selection process (timing loop prevention). The ESMC
2
Future ESMC applications may require additional TLVs.

transmit state machine also supports “transmission per demand”. This

transmission is performed immediately upon request from selection process.
Such request may happen if the selection process selects a new reference
clocked with a different QL value (or alternatively its current selected sync source
has altered its quality level).
The transmission of ESMC frames on a specific port can be enabled/disabled by
user configuration. In QL-disbaled mode, ESMC frames are being transmitted on
the relevant ports (unless they have been disabled by the user) with QL value set
to QL_DNU.
CSM State Machine

This CSM SW module is controlling a clock selection HW (SEC/EEC) that is
responsible for physical clocks selection, jitter attenuation and holdover according
to ITU-T Recommendation G.813/G.8262.
Three operational modes are supported:
• Normal (Auto) operational mode, working in the Locked or Holdover states
depending on the input signals
• Forced Freerun operational mode, working in the Freerun state
• Forced Holdover operational mode, working in the Holdover state
These three types of operational modes are toggled by user configuration.
Figure C-6 shows the relationship between the different operational modes.
Figure C-6. SEC/EEC Operational Modes and Clock States

While in Freerun operational mode, the internal oscillator clock signal is

propagated to the relevant output clock synchronization ports, and the quality
level of the internal oscillator is being distributed on those ports (sent by the CSM
module).
The Auto (normal) operational mode is comprised of two clock states: Locked and
Holdover (an additional ‘Unlocked’ clock state also exists but this is only an
intermediate ‘ghost’ state and therefore does not have any significance):
Locked This is the steady-state of the system. The CSM is locking

to a synchronization clock source.
Holdover Upon losing its synchronization references, the system
immediately transits to Holdover state where the holdover
information, gathered so far, is being used to steer the
output frequency. At this state, holdover memory is no
longer updated by the incoming reference clock (holdover
memory freeze). When a new synchronization source
becomes valid, the system returns to the Locked state.
In Auto operational mode, the selection between the clock states is done
automatically depending on the quality and availability of the incoming reference
signal and the selected QL mode.
When in Auto operational mode, a ‘forced holdover’ command would force the
CSM to move into the Holdover operational mode (Holdover state) regardless of
the current clock state.
In QL-enabled mode, the Locked state is automatically selected if the incoming
reference is not in the signal fail state (SSF = false) and the quality level of the
incoming reference is better or equal to the configured QL_minimum level.
The Holdover state is automatically selected without delay when the incoming
reference goes into the signal fail state (SSF = true) or the quality level of the
incoming signal is lower than the configured QL_minimum level. The Holdover
state is left when both the signal fail clears (SSF = false) and the quality level of
the incoming signal is equal or better than the configured QL_minimum level.
In QL-disabled mode the Locked state is automatically selected if the incoming
reference is not in the signal fail state (SSF = false). The Holdover state is
automatically selected when the incoming reference goes into the signal fail state
(SSF = true).
The CSM state can be forced by the user using the following CLI command:
configure >system>clock>domain (id)# mode { auto | free-run |
holdover } //default auto

C.8 CSM CLI Commands
Note For detailed information regarding the CSM CLI, refer to Chapter 4.
configure
system
clock
domain
- master
- fallback
-source
station
The Master and Fallback Clocks are kept for the backward compatibility with the
existing old projects, in order to have just one Clock XML file. TBD
Clock Selection Module Commands

Clock Domain definition:
configure >system>clock> domain <id> // <id> - domain number
Synchronization Network Type:
configure >system>clock>domain (id)# sync-network { type-1 | type-2 | type-3 }
// default type-2
Note
This parameter can be changed if no clock sources are configured. Upon attempt
to change it when there are existing sources the following error message is
displayed: Existing sources should be removed first.
QL Minimum:
configure >system>clock>domain (id)# no quality
configure >system>clock>domain (id)# quality min-level {level}
// level – {lprc, ssu-a, ssu-b, sec, dnu } // option I
// {prs, stu, st2, tnc, st3e, st3, smc, st4, dus} // option II
// {unk, sec} // option III.
HW inputs monitoring:
configure >system>clock>domain (id)># max-frequency-deviation <value>
// value in units of 0.01 ppm in the range of 381-6096 (3.81 ppm to 60.96 ppm).
// the value configured here is effective for all HW inputs.
// the default value is 1524.
Operational mode:
ETX-2 CSM CLI Commands C-35

configure >system>clock>domain (id)# mode { auto | free-run | holdover

} //default auto
Note
Mode holdover is relevant only for T0 and once is selected forces T0 to go and
stay in Holdover state. This mode is also applicable for system maintenance and
troubleshooting
Synchronization of T4 on T0:
configure >system>clock>domain (id)# [no] force-t4-as-t0 //project dependent
Note
This command causes T4 clock output to be fed by DPLL T0 and to be locked on
the same source as T0.
External commands:
configure >system>clock>domain (id)# force < source-id >
configure >system>clock>domain (id)# manual < source-id >
configure >system>clock>domain (id)# clear
Notes
• Command force never becomes inactive; even if the input is in SSF state only
clear deactivates it
• Command manual becomes inactive if the input is SSF or QL changed
• Command clear deactivates all commands; it returns to auto mode and cancels
force and manual.
Clock Client Commands

configure >system>clock>domain (id)#[no] source <src-id> {type} [<id>] [{port
type} <port-index>]
// type – {domain <domain-id>| rx-port {port-type} <port-index>| station <station-id> |
recovered <recovered-id>}.
// rx-port {port-type} – E1, T1, Ethernet, SDH/SONET.
configure >system>clock>domain (id)> source (src-id)# no priority <num> // If no
option is selected , then this source is not taken to the corresponding selection
process (for T0 or T4)
configure >system>clock>domain (id)> source (src-id)# wait-to-restore
<seconds>
configure >system>clock>domain (id)> source (src-id)# hold-off <milliseconds>
configure >system>clock>domain (id)>source (src-id) # quality-level <ql>
// ql can be {prc, ssu-a, ssu-b, sec, dnu} // option I
{prs, stu, st2, tnc, st3e, st3, smc, st4, dus} // option II
{unk, sec} // option III.
configure >system>clock>domain (id)> source (src-id)# wtr-clear //command
Status and Statistics Commands

C-36 CSM CLI Commands ETX-2

System Clock: {source id} {quality} {state} // state has values: holdover, free-run
and locked.
Station-out Clock: {source id} {state} // state has values locked or unlocked
Force Switch: {InActive | Active}
Manual Switch: {InActive | Active}
configure >system>clock>domain (id)> source (src-id)# show status
Status: { ok, physical-fail, monitoring-fail, esmc-fail }
Tx quality: {ql }
Rx quality: {ql }
ESMC state: { locked | unlocked } // masked if disabled
WTR State : { Inactive | Running }
Notes
• Tx and Rx quality and ESMC state are visible only for quality enabled mode.
• ESMC state is visible only for Ethernet port type.
• Tx quality is visible only if Tx SSM is enabled for this port.
configure >system>clock>domain (id)> source (src-id) # show statistics

ESMC Failure Counter:
ESMC frames: Tx Rx
configure >system>clock>domain (id)> source (src-id) # clear statistics
ETX-2 CSM CLI Commands C-37

C-38 CSM CLI Commands ETX-2

Supplement
Drilling Template for Wall Installation
Front Panel
1 1
176 mm (6.92 in)
3 3
2 2
101.6 mm (4 in)
This panel is drawn to scale.

To drill the holes for a wall installation, hold it against the wall.
LEDs facing up - drill at 1.
LEDs facing down - drill at 2.
LEDs facing left - drill at 3.
377-901-03/14
Publication No. 666-200-05/18
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North American Headquarters

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

Etx-2 MN 0 Manual Etx 203A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Etx-2 MN 0 Manual Etx 203A

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

International Headquarters North American Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

© 1988–2018 RAD Data Communications Ltd. Publication No. 666-200-05/18

ii ETX-2 Carrrier Ethernet Demarcation

General Safety Instructions

Protective ground: the marked lug or terminal should be connected to the

ETX-2 Carrrier Ethernet Demarcation iii

Handling Energized Products

General Safety Practices

iv ETX-2 Carrrier Ethernet Demarcation

ETX-2 Carrrier Ethernet Demarcation v

Connecting Data and Telecommunications Cables

Ports Safety Status

vi ETX-2 Carrrier Ethernet Demarcation

Electromagnetic Compatibility (EMC)

ETX-2 Carrrier Ethernet Demarcation vii

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55032 (CISPR-32)

Avertissement Cet appareil est un appareil de Classe A. Dans un environnement résidentiel,

Achtung Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In

viii ETX-2 Carrrier Ethernet Demarcation

Instructions générales de sécurité

Surface chaude. Ne pas toucher.

Mise à la terre de protection : la cosse ou la borne marquée devrait être

ETX-2 Carrrier Ethernet Demarcation ix

Manipuler des produits sous tension

Règles générales de sécurité

x ETX-2 Carrrier Ethernet Demarcation

Connexion au courant du secteur

ETX-2 Carrrier Ethernet Demarcation xi

Agent In SNMP, this refers to the managed system.

ANSI American National Standards Institute.

APS (Automatic An automatic service restoration function by which a network

Attenuation Signal power loss through equipment, lines or other transmission

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

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

Buffer A storage device. Commonly used to compensate for differences in

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

Carrier A continuous signal at a fixed frequency that is capable of being

ETX-2 Carrrier Ethernet Demarcation xiii

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 A state in which the network is overloaded and starts to discard

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

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 64

E3 The European standard for high speed digital transmission,

ERP Ethernet Ring Protection. A G.8032 Layer-2 Ethernet ring is a logical

Ethernet OAM Ethernet operation, administration and maintenance (OAM) are a

EVC An Ethernet Virtual Connection is an association between two or

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

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

xiv ETX-2 Carrrier Ethernet Demarcation

such as network protocols and the actual payload of data, is

Full Duplex A circuit or device permitting transmission in two directions

G.703 An ITU standard for the physical and electrical characteristics of

Gateway Gateways are points of entrance and exit from a communications

Interface A shared boundary, defined by common physical interconnection