ETX-5 MN

OPERATION MANUAL
INSTALLATION AND
ETX-5
Ethernet Service Aggregation Platform
Version 2.8
ETX-5
Ethernet Service Aggregation Platform
Version 2.8
Installation and Operation Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD").
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the ETX-5 and any
software components contained therein are proprietary products of RAD protected under
international copyright law and shall be and remain solely with RAD.
The ETX-5 product name is owned by RAD. The ETX-5 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, and the
product names MiNID, Optimux, Airmux, and IPmux, are registered trademarks of RAD Data
Communications Ltd. All other trademarks are the property of their respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
ETX-5. 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-5, based
on or derived in any way from the ETX-5. Your undertaking in this paragraph shall survive the
termination of this Agreement.
This Agreement is effective upon your opening of the ETX-5 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-5 and all copies and portions
thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters North America Headquarters

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

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

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

The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates
potential safety hazards regarding product operation or maintenance to
operator or service personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while
the product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the

building protective ground bus.
Some products may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may be also attached.
Warning Please observe the following precautions:
• Before turning on the equipment, make sure that the fiber optic cable is
intact and is connected to the transmitter.
• Do not attempt to adjust the laser drive current.
• Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
• The use of optical devices with the equipment will increase eye hazard.
• Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
ETX-5 iii
Handling Energized Products
General Safety Practices

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

Data and telecommunication interfaces are classified according to their safety status.
The following table lists the status of several standard interfaces. If the status of a given port
differs from the standard one, a notice will be given in the manual.
Ports Safety Status

V.11, V.28, V.35, V.36, RS-530, X.21, SELV Safety Extra Low Voltage:
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.
ETX-5 v
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention Pour 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.
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.
vi ETX-5
FCC-15 User Information

This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Canadian Emission Requirements

This Class A digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulation.
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel
brouilleur du Canada.
Warning per EN 55022 (CISPR-22)

Warning This is a class A product. In a domestic environment, this product may cause
radio interference, in which case the user will be required to take adequate
measures.
Avertissement Cet appareil est un appareil de Classe A. Dans un environnement 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.
ETX-5 vii
Mise au rebut du produit

Français
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.
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.
viii ETX-5
Certains produits peuvent être équipés d'une diode laser. Dans de tels cas,
Français
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.
ETX-5 ix
Connexion au courant du secteur

Français
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.
x ETX-5
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-5300A (may be followed by several suffixes separated by slashes)
Product Options: All
conforms to the following standard(s) or other normative document(s)

in accordance with the relevant European Union harmonization
legislation:
EMC EN 55022:2010 Information technology equipment; Radio disturbance characteristics;

Limits and methods of measurement.
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, 4 April 2016
Nathaniel Shomroni
Homologation Team Leader
European Contact: RAD Data Communications GmbH

Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
ETX-5 xi
Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
Analog A continuous wave or signal (such as human voice).
ANSI American National Standards Institute.
AWG The American Wire Gauge System, which specifies wire width.
Balanced A transmission line in which voltages on the two conductors are equal
in magnitude, but opposite in polarity, with respect to ground.
Bandwidth The range of frequencies passing through a given circuit. The greater
the bandwidth, the more information can be sent through the circuit
in a given amount of time.
Baud Unit of signaling speed equivalent to the number of discrete

conditions or events per second. If each signal event represents only
one bit condition, baud rate equals bps (bits per second).
Bit The smallest unit of information in a binary system. Represents either

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

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

connection with one or more conductors, where all attached devices
receive all transmissions at the same time.
Byte A group of bits (normally 8 bits in length).
Carrier A continuous signal at a fixed frequency that is capable of being

modulated with a second (information carrying) signal.
Cell The 53-byte basic information unit within an ATM network. The user
traffic is segmented into cells at the source and reassembled at the
destination. An ATM cell consists of a 5-byte ATM header and a 48-
xii ETX-5
byte ATM payload, which contains the user data.
Channel A path for electrical transmission between two or more points. Also
called a link, line, circuit or facility.
Clock A term for the source(s) of timing signals used in synchronous

transmission.
Compression Any of several techniques that reduce the number of bits required to
represent information in data transmission or storage, thereby
conserving bandwidth and/or memory.
Concentrator Device that serves as a wiring hub in a star-topology network.

Sometimes refers to a device containing multiple modules of network
equipment.
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.
Data Link Layer Layer 2 of the OSI model. The entity, which establishes, maintains,
and releases data-link connections between elements in a network.
Layer 2 is concerned with the transmission of units of information, or
frames, and associated error checking.
dB (Decibel) A unit used to measure relative increase or decrease in power, voltage

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

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

communications device, network or system.
Differential Delay Differential delay is caused when traffic is split over different lines
that may traverse shorter and longer paths. Products like the RAD
IMX-2T1/E1 inverse multiplexer compensate for any differential delay
(up to 64 msec) between the T1 lines, to properly reconstruct the
original stream.
Digital The binary (“1” or “0”) output of a computer or terminal. In data

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

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

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

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

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

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

network. Viewed as a physical entity, a gateway is that node that
translates between two otherwise incompatible networks or network
segments. Gateways perform code and protocol conversion to
facilitate traffic between data highways of differing architecture.
Grooming In telecommunications, the process of separating and segregating

channels by combing, such that the broadest channel possible can be
assembled and sent across the longest practical link. The aim is to
minimize de-multiplexing traffic and reshuffling it electrically.
Half Duplex A circuit or device capable of transmitting in two directions, but not at
the same time.
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.
xiv ETX-5
Laser A device that transmits an extremely narrow and coherent beam of

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

the sending device after passing through all or part of a
communications link or network.
MAN (Metropolitan Area A network that provides regional connectivity within a metropolitan
Network) area (such as a city).
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.
Master Clock The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Multimode Fiber A fiber with a large core diameter; 50-200 microns compared with the
wavelength of light. It therefore propagates more than one mode.
With multimode fiber, light traverses multiple paths, some longer than
others. This leads to dispersion, which reduces optical range.
Multiplexer At one end of a communications link, a device that combines several

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

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

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

terminals and modems.
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.
QoS (Quality of Service) Refers to the capability of a network to provide better service to
selected network traffic over various technologies, including Frame
Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1
networks.
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.
Serial Transmission A common mode of transmission, where the character bits are sent
sequentially one at a time instead of in parallel.
Single Mode Describing an optical wave-guide or fiber that is designed to

propagate light of only a single wavelength (typically 5-10 microns in
diameter).
Space In telecommunications, the absence of a signal. Equivalent to a binary

0.
Sync See Synchronous Transmission.
Synchronous Transmission in which data bits are sent at a fixed rate, with the
Transmission transmitter and receiver synchronized.
T1 A digital transmission link with a capacity of 1.544 Mbps used in North

America. Typically channelized into 24 DS0s, each capable of carrying
a single voice conversation or data stream. Uses two pairs of twisted
pair wires.
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.
xvi ETX-5
VLAN-Aware A device that is doing the Layer 2 bridging according to the VLAN tag
in addition to the standard bridging parameters. A VLAN-aware device
will not strip or add any VLAN header.
ETX-5 xvii
xviii ETX-5
Quick Start Guide
This section describes the minimum configuration needed to prepare ETX-5 for
operation.
1. Installing the Unit

Perform the following steps to install the unit:
1. Determine the required configuration of ETX-5, according to your application.
2. Connect the main and I/O card ports as required for the application.
3. Connect the ASCII terminal to the CONTROL DCE port on an E4-MC-4 card.
4. Connect power to the unit.
Connecting the Interfaces

 To connect the interfaces:
1. Insert the XFP/SFP modules (if applicable) into the relevant ports.
2. Connect the optical cables.
3. Connect the network port(s) to the service provider network equipment.
4. Connect the user port(s) to the customer network equipment.
Notes • The number of available Ethernet ports depends on the options you
purchased.
• Lock the wire latch of each XFP or SFP module by lifting it up until it clicks into
place. For additional information, refer to Chapter 2.
Connecting to a Terminal
 To connect the unit to a terminal:
1. Connect the male DB-9 connector of terminal cable to the 9-pin D-type
female connector on E4-MC-4 card, designated CONTROL DCE.
2. Connect the other side of the cable to the ASCII terminal equipment.
ETX-5 Installing the Unit 1

Quick Start Guide Installation and Operation Manual
Connecting the Power

The unit can be connected to AC or DC power.
 To connect to AC power:
• Connect each power cable first to the connector on the E5-PIM/AC module,
and then to the power outlet.
The unit turns on automatically upon connection to the mains, and the
PWR indicator lights up.
 To connect to DC power:
1. Strip 7 mm (1/4 inch) of insulation from the leads.
Caution
Pay attention to polarity. For each source, connect the positive lead first, and the
negative lead second.
Refer to the Connection of DC Mains section at the beginning of this manual.
2. Use a narrow blade screwdriver to release the terminal screw.

3. Push the lead into the terminal up to its insulating sleeve.
4. When the lead is in position, fasten the screw to secure the lead.
5. Verify that the lead is securely held by pulling on it lightly.
6. Insert the plug into the socket of the E5-PIM/DC module.
7. Secure the plug by tightening the two screws.
8. Connect the cable to the DC power source.
2. Configuring the Unit for Management

Configure ETX-5 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-5 cables and connectors are properly connected.
2. Turn on the control terminal or start the PC terminal emulation program to
create a new terminal connection.
3. 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.
4. Set the terminal input delay between characters to at least 10 msec.
5. Power-up the unit.
6. ETX-5 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
7. Press <ENTER> until you receive the login prompt.
2 Configuring the Unit for Management ETX-5

Installation and Operation Manual Quick Start Guide
8. To log in, enter your user name (su for full configuration and monitoring
access) and your password.
9. The device prompt appears:
ETX-5#
You can now type the necessary CLI commands.
Note RAD recommends using the 115.2 kbps data rate for CLI management sessions.
10. Navigate to config>terminal# prompt and change the default terminal baud
rate (9.6 kbps) to 115.2 kbps.
11. Configure the PC communication port parameters to a baud rate of
115.2 kbps to match the new ETX-5 setting.
12. Continue with product configuration.
Configuring Management Flows

To manage the ETX-5 from a remote NMS, you must first preconfigure the basic
parameters using a supervision terminal connected to the ETX-5 CONTROL DCE
port. RAD recommends Layer-3 management access via the out-of-band Ethernet
management port.
 To preconfigure ETX-5 for Layer-3 management access:

1. Add a router-type SVI.
2. Create classifier profiles for matching all traffic and matching untagged
traffic.
3. Add two flows (incoming and outgoing) connecting 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.
5. Configure SNMPv3 parameters:
 OID tree visibility, mask and type
 Access group
 Trap report policy.
The following script provides all necessary configuration steps. Replace IP
addresses and entity names with values relevant for your network environment.
#*******************************Adding_SVI***********************************
config port svi 99 router
exit all
#**********************************End***************************************
#***************************Adding Classifier_Profiles***********************
config flows classifier-profile classall match-any
match all
exit all
config flows classifier-profile classutg match-any
ETX-5 Configuring the Unit for Management 3

match untagged
exit all
#*********************************End****************************************
#***************************Configuring_Flows********************************
config flows flow mng_in
classifier classutg
ingress-port mng-ethernet main-a/0
egress-port svi 99
no shutdown
exit all
config flows flow mng_out

classifier classall
ingress-port svi 99
egress-port mng-ethernet main-a/0
no shutdown
exit all
#**********************************End***************************************
#*********************Configuring_Router_Interface***************************
configure router 1 interface 1
address 172.18.219.116/24
bind svi 99
no shutdown
exit
static-route 0.0.0.0/0 address 172.18.219.1
exit all
#**********************************End***************************************
#*********************Configuring_SNMP_View/Mask/Type************************
configure management snmp
view internet 1
mask 1
type included
no shut
exit all
#**********************************End***************************************
#*********************Configuring_SNMP_Access_Group************************
access-group initial usm no-auth-no-priv
context-match prefix
exit all
#**********************************End***************************************
#**************************Configring_SNMP_Traps*****************************
target-params p
message-processing-model snmpv3
version usm
security name initial level no-auth-no-priv
no shutdown
exit
4 Configuring the Unit for Management ETX-5

Installation and Operation Manual Quick Start Guide
target a
target-params p
tag-list unmasked
address udp-domain 172.17.176.35
no shutdown
exit
notify unmasked
tag unmasked
no shutdown
exit all
#**********************************End************************************
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 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. Chapter 5 details different scenarios for
provisioning supported Ethernet services.
ETX-5 Configuring Services 5

6 Configuring Services ETX-5

Contents
Chapter 1. Introduction
1.1 Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-1
Applications ....................................................................................................................... 1-1
Features ............................................................................................................................ 1-2
Carrier-Class Layer 2 Aggregation Switch ...................................................................... 1-2
Forwarding Schemes ..................................................................................................... 1-3
Remote Provisioning and Traffic Management............................................................... 1-3
Hardware-Based Ethernet OAM and Performance Monitoring ....................................... 1-3
Service Resiliency and Protection .................................................................................. 1-4
Synchronization and Timing over Packet ....................................................................... 1-4
Management and Security ............................................................................................. 1-4
1.2 New in This Version .............................................................................................................. 1-5
1.3 Physical Description ............................................................................................................. 1-5
Front Panel ........................................................................................................................ 1-5
Rear Panel ......................................................................................................................... 1-6
Available Cards ................................................................................................................... 1-6
1.4 Functional Description .......................................................................................................... 1-7
System Structure ............................................................................................................... 1-7
I/O-to-Main and Main-to–I/O Traffic Path .......................................................................... 1-8
I/O Card to Main Card Direction ..................................................................................... 1-9
Main Card to I/O Card Direction ..................................................................................... 1-9
Port Types ......................................................................................................................... 1-9
Data Path ........................................................................................................................ 1-10
Main Cards ....................................................................................................................... 1-11
Main Card Functionality ............................................................................................... 1-11
10GbE Interface .......................................................................................................... 1-12
Packet Processor ......................................................................................................... 1-13
Timing Subsystem ....................................................................................................... 1-15
Management Subsystem ............................................................................................. 1-16
The SFP/SFP+ Main Card ................................................................................................... 1-17
Ethernet Service Cards ..................................................................................................... 1-17
GbE and 10GbE Interface Cards ................................................................................... 1-18
Packet Processor ......................................................................................................... 1-18
I/O Card Data Flow Schematics .................................................................................... 1-19
SDH/SONET Card .............................................................................................................. 1-20
SDH/SONET Interfaces................................................................................................. 1-21
T1 mapping to OC-12 is performed using G.707 mapping scheme: T1 > VT1.5 > VT group
> STS-1 > OC-12E5-cTDM-STM4 and E5-cTDM-4 cards ................................................ 1-22
Pseudowire Services .................................................................................................... 1-22
Adaptive Timing .......................................................................................................... 1-25
Timing Mechanism ........................................................................................................... 1-26
Physical Port Clock ...................................................................................................... 1-27
External (BITS) Clock.................................................................................................... 1-28
IEEE 1588v2 Clock ....................................................................................................... 1-28
GPS Clock .................................................................................................................... 1-29
Performance Management Portal ..................................................................................... 1-29
Temperature-Hardened and NEBS-Compliant Chassis....................................................... 1-29
ETX-5 i
Table of Contents Installation and Operation Manual
1.5 Technical Specifications...................................................................................................... 1-29
Chapter 2. Installation and Setup

2.1 Safety .................................................................................................................................. 2-1
Grounding .......................................................................................................................... 2-2
Laser Safety ....................................................................................................................... 2-3
Protection against ESD .................................................................................................. 2-3
Proper Handling of Modules .......................................................................................... 2-4
2.2 Site Requirements and Prerequisites .................................................................................... 2-4
Power ................................................................................................................................ 2-4
AC Power ...................................................................................................................... 2-5
DC Power ...................................................................................................................... 2-5
Panel Clearance ................................................................................................................. 2-5
Ambient Requirements ...................................................................................................... 2-5
Electromagnetic Compatibility Considerations .................................................................... 2-6
2.3 Package Contents................................................................................................................. 2-6
2.4 Required Equipment ............................................................................................................. 2-6
2.5 Installing AC Power Supply Modules...................................................................................... 2-7
2.6 Installing the ETX-5 Enclosure .............................................................................................. 2-7
Installing Cable Managers ................................................................................................... 2-7
Installing ETX-5 in Racks .................................................................................................... 2-8
2.7 Installing a Fan Tray ........................................................................................................... 2-11
2.8 Cleaning or Replacing Air Filter ........................................................................................... 2-12
Air Filter Maintenance ...................................................................................................... 2-12
Intake Module Panel Maintenance .................................................................................... 2-13
2.9 Installing Power Inlet Modules ............................................................................................ 2-13
E5-PIM/AC Module............................................................................................................ 2-13
E5-PIM/DC Modules .......................................................................................................... 2-13
Installing PI Modules ........................................................................................................ 2-13
2.10 Installing a Main Card ......................................................................................................... 2-14
Inserting the Main Card .................................................................................................... 2-14
Removing the Main Card .................................................................................................. 2-15
Replacing a Main Card during Equipment Operation ......................................................... 2-15
ETX-5 Chassis with two CONTROL Modules ................................................................. 2-15
ETX-5 Chassis with Single Main Card ........................................................................... 2-16
2.11 Connecting to Power .......................................................................................................... 2-16
Grounding ........................................................................................................................ 2-16
Connecting to AC Power .................................................................................................. 2-16
Connecting to DC Power .................................................................................................. 2-17
2.12 Installing I/O Cards ............................................................................................................. 2-18
2.13 Installing Blank Panels ........................................................................................................ 2-18
2.14 Installing SFP/SFP+ or XFP Modules .................................................................................... 2-19
2.15 Connecting to 10Gb Ethernet Equipment ........................................................................... 2-20
2.16 Connecting to Gigabit Ethernet Equipment ......................................................................... 2-20
2.17 Connecting to STM-1/OC-3 Equipment ............................................................................... 2-21
2.18 Connecting to STM-4/OC-12 Equipment ............................................................................. 2-21
2.19 Connecting to External Clock Devices ................................................................................. 2-22
2.20 Connecting to GPS Clock Devices ........................................................................................ 2-22
2.21 Connecting to a Terminal ................................................................................................... 2-23
2.22 Connecting to a Network Management Station .................................................................. 2-23
2.23 Connecting to an External Alarm Device ............................................................................. 2-24
2.24 Labeling Cables .................................................................................................................. 2-24
ii ETX-5
Installation and Operation Manual Table of Contents
Chapter 3. Operation and Maintenance

3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-2
3.3 Startup ................................................................................................................................. 3-3
Configuration and Application Software Files ..................................................................... 3-3
Loading Sequence .............................................................................................................. 3-4
3.4 Working with Custom Configuration Files ............................................................................. 3-5
Zero Touch......................................................................................................................... 3-5
Saving Configuration Changes ............................................................................................ 3-5
Confirming the Configuration File....................................................................................... 3-6
Handling Configuration File Errors ...................................................................................... 3-7
3.5 Turning Off the Unit ............................................................................................................. 3-7
Chapter 4. Management and Security

4.1 Management Access............................................................................................................. 4-2
Factory Defaults ................................................................................................................ 4-3
Configuring Management Access........................................................................................ 4-3
4.2 Management Access Methods .............................................................................................. 4-3
Layer 2 Management Access .............................................................................................. 4-3
Layer 3 Management Access .............................................................................................. 4-4
4.3 CLI-Based Configuration ....................................................................................................... 4-6
Working with Terminal ....................................................................................................... 4-6
Working with Telnet and SSH ............................................................................................. 4-6
Login ................................................................................................................................. 4-7
Using the CLI ...................................................................................................................... 4-8
CLI Prompt .................................................................................................................... 4-8
Navigating ..................................................................................................................... 4-8
Command Tree .............................................................................................................. 4-9
Command Structure .................................................................................................... 4-10
Special Keys ................................................................................................................ 4-10
Getting Help ................................................................................................................ 4-11
Refreshing Output ...................................................................................................... 4-16
Filtering Output ........................................................................................................... 4-17
Enabling Entitites ........................................................................................................ 4-19
Using Scripts .................................................................................................................... 4-19
Reconfiguring ETX-5 for SNMP Management .................................................................... 4-20
4.4 Access Policy ...................................................................................................................... 4-20
Factory Defaults .............................................................................................................. 4-20
Configuring Access Policy ................................................................................................. 4-20
4.5 Authentication via RADIUS Server ....................................................................................... 4-21
Standards ........................................................................................................................ 4-21
Benefits ........................................................................................................................... 4-21
Functional Description ..................................................................................................... 4-21
Configuring RADIUS Parameters ....................................................................................... 4-22
Displaying RADIUS Status ................................................................................................. 4-22
Displaying RADIUS Statistics............................................................................................. 4-23
4.6 Authentication via TACACS+ Server..................................................................................... 4-24
Standards ........................................................................................................................ 4-24
Benefits ........................................................................................................................... 4-24
Components................................................................................................................ 4-25
ETX-5 iii
Accounting .................................................................................................................. 4-26

Defining TACACS+ Server ................................................................................................. 4-26
Configuring Accounting Groups ........................................................................................ 4-27
Example – Defining Server ............................................................................................... 4-27
Example – Defining Accounting Group .............................................................................. 4-28
Displaying Statistics ......................................................................................................... 4-28
Defining Accounting Groups ............................................................................................. 4-29
4.7 Access Control List (ACL) .................................................................................................... 4-30
Applicable Products.......................................................................................................... 4-30
Standards ........................................................................................................................ 4-30
Benefits ........................................................................................................................... 4-30
Binding Access Control Lists ........................................................................................ 4-31
Filtering and Marking ................................................................................................... 4-31
Show Me Demo ........................................................................................................... 4-31
Statistics ..................................................................................................................... 4-32
Configuring ACL ............................................................................................................... 4-32
102BAccess-Control-Level Tasks ......................................................................................... 4-32
103BManagement-Level Tasks ............................................................................................ 4-34
104BExample ...................................................................................................................... 4-35
105BConfiguration Errors .................................................................................................... 4-36
106BDisplaying Status......................................................................................................... 4-36
107BDisplaying Statistics .................................................................................................... 4-37
4.8 Default IP ........................................................................................................................... 4-37
Benefits ........................................................................................................................... 4-37
4.9 GUI-Based Configuration .................................................................................................... 4-38
Working with RADview ..................................................................................................... 4-40
Performance Management .......................................................................................... 4-40
Viewing Performance Management Configuration ....................................................... 4-44
Examples ..................................................................................................................... 4-44
Configuration Errors .................................................................................................... 4-46
PM Flow Scale ............................................................................................................. 4-46
Working with Shelf View .................................................................................................. 4-47
Working with Third-Party Network Management Systems ................................................ 4-47
4.10 IPv6 for Management ......................................................................................................... 4-48
Benefits ........................................................................................................................... 4-48
4.11 OAM CFM ........................................................................................................................... 4-49
Standards ........................................................................................................................ 4-49
OAM Elements............................................................................................................. 4-49
OAM Functions ............................................................................................................ 4-51
OAM Connectivity ........................................................................................................ 4-51
MEPs and Services ....................................................................................................... 4-52
MIPs ............................................................................................................................ 4-56
Messaging System ....................................................................................................... 4-60
Performance Monitoring.............................................................................................. 4-64
Configuring OAM .............................................................................................................. 4-65
Configuring Maintenance Domains .............................................................................. 4-65
Configuring Maintenance Associations ........................................................................ 4-67
Configuring Mainteance Endpoints .............................................................................. 4-68
iv ETX-5
Configuring Maintenance Intermediary Points ............................................................. 4-70

Configuring Maintenance Endpoint Services ................................................................ 4-71
Configuring Destination NEs ........................................................................................ 4-73
127BConfiguring a Measurement Bin Profile........................................................................ 4-74
Displaying OAM Statistics ............................................................................................ 4-75
Performing OAM Loopback .......................................................................................... 4-79
Performing OAM Link Trace ......................................................................................... 4-79
Examples ......................................................................................................................... 4-79
Example 1. Down MEP between Main Card Ports ......................................................... 4-79
Example 2. Down MEP between Main and I/O Card Ports............................................. 4-82
Example 3. Up MEP between Main Card and Bridge Ports ............................................ 4-86
Example 4. RMEP Configuration ................................................................................... 4-90
Configuration Errors ......................................................................................................... 4-90
4.12 OAM EFM............................................................................................................................ 4-93
Standards ........................................................................................................................ 4-93
Benefits ........................................................................................................................... 4-93
Layer-2 Operation ....................................................................................................... 4-94
OAMPDUs .................................................................................................................... 4-94
Configuring OAM EFM ...................................................................................................... 4-95
Displaying OAM EFM Status .............................................................................................. 4-96
Displaying OAM EFM Statistics ......................................................................................... 4-97
Example ........................................................................................................................... 4-97
4.13 Services for Management Traffic ........................................................................................ 4-98
4.14 SNMP Management ............................................................................................................ 4-98
Standards ........................................................................................................................ 4-98
Benefits ........................................................................................................................... 4-99
SNMP Engine ID ......................................................................................................... 4-100
SNMPv3 Message Processing ..................................................................................... 4-100
User-Based Security Model (USM) ............................................................................. 4-101
View-Based Access Control Model (VACM) ................................................................. 4-101
SNMP Security Level .................................................................................................. 4-102
SNMPv3 Administrative Features ............................................................................... 4-102
Factory Defaults ............................................................................................................ 4-102
SNMPv3 Configuration ................................................................................................... 4-103
Example ......................................................................................................................... 4-111
4.15 Syslog .............................................................................................................................. 4-113
Standards and MIBs ....................................................................................................... 4-113
Benefits ......................................................................................................................... 4-113
Functional Description ................................................................................................... 4-114
Elements ................................................................................................................... 4-114
Transport Protocol .................................................................................................... 4-114
Message Format........................................................................................................ 4-114
Facilities and Severitie ............................................................................................... 4-114
Syslog Configuration ...................................................................................................... 4-115
Example .................................................................................................................... 4-117
Configuration Error ................................................................................................... 4-117
4.16 Terminal Control Port ....................................................................................................... 4-118
Configuring Control Port Parameters .............................................................................. 4-118
Configuring STP.............................................................................................................. 4-118
ETX-5 v
BPDU Peer ................................................................................................................. 4-119

CLI Configuration Example ......................................................................................... 4-120
Chapter 5. Services
5.1 Service Elements .................................................................................................................. 5-1
Profiles .............................................................................................................................. 5-1
Scheduling and Shaping Entities......................................................................................... 5-2
Physical Ports .................................................................................................................... 5-2
Logical Ports ...................................................................................................................... 5-3
Forwarding Entities ............................................................................................................ 5-4
Flows ............................................................................................................................ 5-5
Bridge ........................................................................................................................... 5-5
Router........................................................................................................................... 5-5
5.2 E-Line Service ....................................................................................................................... 5-6
I/O-to-Main Path ................................................................................................................ 5-6
Main-to-I/O Path ................................................................................................................ 5-9
I/O-to-I/O Path................................................................................................................. 5-11
Main-to-Main Path ........................................................................................................... 5-13
5.3 E-LAN Service ..................................................................................................................... 5-15
5.4 Routing Services ................................................................................................................. 5-18
I/O-to-Main via Router Path ............................................................................................. 5-18
Router-to-Bridge Path ..................................................................................................... 5-21
5.5 Pseudowire Services ........................................................................................................... 5-25
Point-to-Point L2 Pseudowire Service .............................................................................. 5-25
L2 Pseudowire Service over Bridge ................................................................................... 5-28
L3 Pseudowire Service ..................................................................................................... 5-31
Chapter 6. Cards and Ports

6.1 Cards.................................................................................................................................... 6-1
Displaying Card Summary .............................................................................................. 6-2
Resetting I/O Cards ....................................................................................................... 6-5
Displaying Card Status................................................................................................... 6-5
Configuration Errors ...................................................................................................... 6-5
6.2 E1 Ports ............................................................................................................................... 6-6
Standards and MIBs ........................................................................................................... 6-6
Functional Description ....................................................................................................... 6-7
E1 Line Signal Characteristics ........................................................................................ 6-7
E1 Signal Structure ........................................................................................................ 6-7
Timeslot 0 ..................................................................................................................... 6-8
Multiframes ................................................................................................................... 6-9
Channel Associated Signaling ...................................................................................... 6-10
CRC-4 Error Detection ................................................................................................. 6-10
E1 Alarm Conditions .................................................................................................... 6-10
E1 Port Diagnostics ..................................................................................................... 6-11
Configuring Internal E1 Interfaces .................................................................................... 6-12
Displaying Status ............................................................................................................. 6-14
Testing Internal E1 Ports .................................................................................................. 6-16
Running Loopbacks ..................................................................................................... 6-16
Example ........................................................................................................................... 6-16
vi ETX-5
6.3 Ethernet Ports .................................................................................................................... 6-18

Standards and MIBs ......................................................................................................... 6-18
LLDP Benefits .................................................................................................................. 6-18
Autonegotiation .......................................................................................................... 6-19
Flow Control ................................................................................................................ 6-19
Frame Format ............................................................................................................. 6-19
Jumbo Frames ............................................................................................................. 6-20
Ethertype .................................................................................................................... 6-20
L2CP Handling ............................................................................................................. 6-20
Classification Key ........................................................................................................ 6-20
Queue Group Profile .................................................................................................... 6-20
Configuring Ethernet Ports............................................................................................... 6-21
Displaying Port Status ...................................................................................................... 6-23
Displaying Optical Link SFP/XFP Status ............................................................................. 6-26
Example ........................................................................................................................... 6-28
Port Loopback.................................................................................................................. 6-28
6.4 SDH/SONET Ports ............................................................................................................... 6-29
Benefits ........................................................................................................................... 6-29
SDH Implementation Principles .................................................................................... 6-30
General Structure of SDH Signals ................................................................................ 6-31
SDH Frame Organization ............................................................................................. 6-32
VC Assembly/Disassembly Process ............................................................................... 6-34
STM-1/STM-4 Frame Structure .................................................................................... 6-34
Pointers ...................................................................................................................... 6-35
SDH Overhead Data .................................................................................................... 6-36
SDH Tributary Units ..................................................................................................... 6-40
SDH Maintenance Signals and Response to Abnormal Conditions ................................ 6-43
SONET Environment .................................................................................................... 6-47
SDH/SONET Port Diagnostics ....................................................................................... 6-48
Configuring SDH/SONET Interfaces................................................................................... 6-49
Configuring AUG/OC-3 Interfaces ..................................................................................... 6-51
Configuring TUG3/AU3/STS-1 Interfaces ........................................................................... 6-52
Configuring VC-12/VC-11/VT-1.5 Interfaces...................................................................... 6-53
Configuring SOH Profile ................................................................................................... 6-53
Configuring Path Profile ................................................................................................... 6-54
Example ........................................................................................................................... 6-55
Testing SDH/SONET Ports ................................................................................................ 6-61
6.5 Service Aggregation Group (SAG) ....................................................................................... 6-64
Benefits ........................................................................................................................... 6-64
Configuring SAGs ............................................................................................................. 6-65
Example ........................................................................................................................... 6-66
ETX-5 vii
6.6 Service Virtual Interface (SVI) ............................................................................................. 6-66

Configuring SVIs ............................................................................................................... 6-68
Example ........................................................................................................................... 6-68
6.7 T1 Ports ............................................................................................................................. 6-69
T1 Signal Structure ...................................................................................................... 6-70
T1 Alarm Conditions .................................................................................................... 6-71
T1 Port Diagnostics ..................................................................................................... 6-71
Configuring Internal T1 Interfaces .................................................................................... 6-74
Example ........................................................................................................................... 6-77
6.8 Terminal Control Port ......................................................................................................... 6-78
Chapter 7. Resiliency
7.1 Dual Homing ........................................................................................................................ 7-1
Benefits ............................................................................................................................. 7-1
Protection Groups ......................................................................................................... 7-2
Port Combinations in Dual Homing Groups .................................................................... 7-2
Traffic Switching ........................................................................................................... 7-4
Switching Triggers ......................................................................................................... 7-5
Timers ........................................................................................................................... 7-5
Force Switch Command ................................................................................................. 7-5
Configuring Dual Homing ................................................................................................... 7-5
Displaying Ethernet Group Status ...................................................................................... 7-6
Example ............................................................................................................................. 7-7
Configuration Errors ........................................................................................................... 7-7
7.2 Ethernet Link Aggregation (LAG) .......................................................................................... 7-8
Benefits ............................................................................................................................. 7-9
Intra-Card LAG............................................................................................................... 7-9
Inter-Card LAG ............................................................................................................ 7-10
Load-Balancing LAG..................................................................................................... 7-11
Configuring a LAG ............................................................................................................ 7-14
LACP Traffic ................................................................................................................. 7-14
Special Considerations for I/O Cards............................................................................ 7-15
Deleting the LAG .............................................................................................................. 7-20
Displaying LAG Members .................................................................................................. 7-21
Displaying LAG Status ...................................................................................................... 7-21
Displaying LACP Status ..................................................................................................... 7-21
Displaying LACP Statistics ................................................................................................ 7-23
Displaying LAG Statistics .................................................................................................. 7-23
Examples ......................................................................................................................... 7-27
viii ETX-5
Inter-Card LAG between Two Main Cards..................................................................... 7-27

Inter-Card LAG between Two I/O Cards ....................................................................... 7-29
7.3 Ethernet Ring Protection (ERP) ........................................................................................... 7-35
Standards ........................................................................................................................ 7-35
Benefits ........................................................................................................................... 7-35
Ring Topology ............................................................................................................. 7-35
R-APS Messaging ......................................................................................................... 7-40
Mechanism of Operation ............................................................................................. 7-40
Timers ......................................................................................................................... 7-41
Administrative Commands ........................................................................................... 7-41
Ring over Load Balancing LAG ..................................................................................... 7-42
Configuring ERP ............................................................................................................... 7-43
Displaying ERP Status....................................................................................................... 7-46
Displaying ERP Statistics .................................................................................................. 7-48
Example ........................................................................................................................... 7-49
7.4 Fault Propagation ............................................................................................................... 7-58
Standards ........................................................................................................................ 7-59
Benefits ........................................................................................................................... 7-59
Trigger Sources ........................................................................................................... 7-60
Destination Actions ..................................................................................................... 7-60
RMEP Auto-configuration ................................................................................................. 7-60
Adding Fault Propagation Group ...................................................................................... 7-61
Configuring Fault Propagation .......................................................................................... 7-62
Disabling Fault Propagation ............................................................................................. 7-63
Example 1 ........................................................................................................................ 7-63
Example 2 ........................................................................................................................ 7-64
7.5 Main Card Redundancy ....................................................................................................... 7-65
Benefits ........................................................................................................................... 7-65
Configuring Main Card Redundancy .................................................................................. 7-66
Displaying Main Card Protection Status ............................................................................ 7-66
7.6 SDH/SONET Protection ....................................................................................................... 7-67
Benefits ........................................................................................................................... 7-67
APS/MSP Architecture .................................................................................................. 7-68
Automatic Switchover Conditions ................................................................................ 7-69
Manual Switching Commands ...................................................................................... 7-70
Configuring I/O Card Protection ....................................................................................... 7-70
Configuring APS/MSP........................................................................................................ 7-71
Displaying APS/MSP Status ............................................................................................... 7-72
Examples ......................................................................................................................... 7-73
Intra-Card APS/MSP ..................................................................................................... 7-73
Inter-Card APS/MSP ..................................................................................................... 7-73
Card Protection ........................................................................................................... 7-73
ETX-5 ix
Port APS ...................................................................................................................... 7-74

Chapter 8. Traffic Processing

8.1 Bridge .................................................................................................................................. 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-1
Bridge Model ................................................................................................................. 8-2
E-Tree Service ............................................................................................................... 8-3
VLAN Editing at Bridge Port Ingress and Egress ............................................................. 8-4
Deleting Bridge Elements .............................................................................................. 8-5
Spanning Tree Protocol ................................................................................................. 8-6
Configuring Bridge ............................................................................................................. 8-8
Configuring Bridge Ports ............................................................................................... 8-9
Configuring VLAN Membership .................................................................................... 8-10
Configuring RSTP/MSTP ............................................................................................... 8-10
Configuring STP ........................................................................................................... 8-16
Displaying MAC Address Table .......................................................................................... 8-17
Displaying VLAN Information ............................................................................................ 8-17
Displaying Bridge Port Status ........................................................................................... 8-18
Example ........................................................................................................................... 8-18
8.2 Cross-Connection ............................................................................................................... 8-19
Benefits ........................................................................................................................... 8-19
Configuring Cross-Connection .......................................................................................... 8-20
Examples ......................................................................................................................... 8-20
Cross-Connection ........................................................................................................ 8-20
Pseudowire Service ..................................................................................................... 8-20
8.3 Ethertype ........................................................................................................................... 8-24
Benefits ........................................................................................................................... 8-24
Configuring Ethertype ...................................................................................................... 8-26
Example ........................................................................................................................... 8-26
8.4 Flows ................................................................................................................................. 8-27
Benefits ........................................................................................................................... 8-27
Classification ............................................................................................................... 8-28
I/O Ingress Flows ......................................................................................................... 8-37
Flow MAC Swap LB at IO Card Egress ........................................................................... 8-38
Other Flow Types ........................................................................................................ 8-39
Flow Processing .......................................................................................................... 8-39
Drop Action ................................................................................................................. 8-40
Flow Counters ............................................................................................................. 8-41
RFC-2544 Loopback Responder................................................................................... 8-42
x ETX-5
VLAN Editing ............................................................................................................... 8-43

RADview Performance Management Services .............................................................. 8-49
Classifier Profiles ............................................................................................................. 8-49
Examples ..................................................................................................................... 8-50
Error Messages ........................................................................................................... 8-50
Configuring Flows ............................................................................................................ 8-51
Displaying Flow Summary ................................................................................................. 8-57
Examples ......................................................................................................................... 8-59
Multiple CoS Point-to-Point Service ............................................................................. 8-59
Multipoint Service ....................................................................................................... 8-64
8.5 Layer 2 Control Protocol (L2CP).......................................................................................... 8-71
Standards ........................................................................................................................ 8-71
Benefits ........................................................................................................................... 8-71
L2CP Profile Settings ................................................................................................... 8-72
L2CP Profiles and Traffic Classification Keys ................................................................ 8-73
L2CP Tunnel with MAC Swap (L2PT)............................................................................. 8-73
Adding Layer 2 Control Processing Profiles ...................................................................... 8-74
Deleting Layer 2 Control Processing Profiles .................................................................... 8-74
Configuring Layer 2 Control Processing Profile Parameters .............................................. 8-75
Adding Layer 2 Control Processing Profiles .................................................................. 8-76
Deleting Layer 2 Control Processing Profiles ............................................................... 8-76
Examples ......................................................................................................................... 8-76
Viewing L2CP Statistics .................................................................................................... 8-77
8.6 Link Layer Discovery Protocol (LLDP) .................................................................................. 8-78
Standards ........................................................................................................................ 8-78
Benefits ........................................................................................................................... 8-78
LLDP Bridge Types ....................................................................................................... 8-78
LLDP Packets ............................................................................................................... 8-79
Configuring LLDP.............................................................................................................. 8-80
LLDP Traffic ................................................................................................................. 8-81
LLDP on Main Card Using L2CP Profile at the Flow Level .............................................. 8-81
Special Considerations for LLDP on I/O Cards Using L2CP Profile at the Flow Level ...... 8-81
System Parameters ..................................................................................................... 8-82
Port Parameters .......................................................................................................... 8-83
Example ........................................................................................................................... 8-85
LLDP on Main Cards..................................................................................................... 8-85
8.7 Peers .................................................................................................................................. 8-90
Benefits ........................................................................................................................... 8-90
Configuring Remote Peers ............................................................................................... 8-90
Example ........................................................................................................................... 8-91
8.8 Router ................................................................................................................................ 8-92
Standards ........................................................................................................................ 8-92
Benefits ........................................................................................................................... 8-92
ETX-5 xi

Router Scaling ............................................................................................................. 8-93
Connection to Physical and Bridge Ports ..................................................................... 8-93
Management ............................................................................................................... 8-94
Port Loopback ............................................................................................................. 8-94
Loopback Router Interfaces ........................................................................................ 8-94
Routing and ARP Tables .............................................................................................. 8-95
Configuring the Router .................................................................................................... 8-95
Displaying ARP Table ........................................................................................................ 8-96
Displaying Routing Table .................................................................................................. 8-96
Displaying Interface Table ................................................................................................ 8-97
Displaying Router Interface Status ................................................................................... 8-97
Example ........................................................................................................................... 8-97
Configuration Errors ....................................................................................................... 8-101
8.9 TDM Pseudowires ............................................................................................................. 8-103
Standards ...................................................................................................................... 8-103
Benefits ......................................................................................................................... 8-103
Pseudowire Packet Processing Subsystem ................................................................. 8-104
Jitter Buffer ............................................................................................................... 8-110
Packet Loss ............................................................................................................... 8-111
ToS ........................................................................................................................... 8-111
OAM Protocol ............................................................................................................ 8-111
Alarm Indications and Fault Propagation ................................................................... 8-112
Adaptive Timing ........................................................................................................ 8-115
Configuring Pseudowires ................................................................................................ 8-116
Displaying PW Statistics ................................................................................................. 8-119
Clearing Statistics .......................................................................................................... 8-120
Viewing the Pseudowire Status and Configuration Summary .......................................... 8-120
Example ......................................................................................................................... 8-122
Chapter 9. Timing and Synchronization

9.1 Clock Selection ..................................................................................................................... 9-1
Benefits ............................................................................................................................. 9-1
Clock Domain ................................................................................................................ 9-3
SEC Module ................................................................................................................... 9-5
Input Sources ................................................................................................................ 9-8
Redundancy ................................................................................................................ 9-10
Configuring the Clock ....................................................................................................... 9-11
Configuring the Clock Domain ..................................................................................... 9-11
Configuring the Clock Sources ..................................................................................... 9-13
Configuring Station Clock ............................................................................................ 9-18
Configuring Y-Cable Protection .................................................................................... 9-20
Example ...................................................................................................................... 9-21
9.2 1588v2 Timing ................................................................................................................... 9-23
xii ETX-5
Benefits ........................................................................................................................... 9-24

1588v2 Master Mode .................................................................................................. 9-25
1588v2 Slave Mode ..................................................................................................... 9-28
Configuring 1588v2 Master Clock ..................................................................................... 9-29
Displaying Status......................................................................................................... 9-30
Displaying Statistics .................................................................................................... 9-32
Configuring 1588v2 Slave Clock Configuration ................................................................. 9-33
Defining 1588v2 Slave Entity ...................................................................................... 9-34
Configuring a Peer 1588v2 Master .............................................................................. 9-35
Displaying Status......................................................................................................... 9-36
Displaying Statistics .................................................................................................... 9-37
Configuring ToD Clock ...................................................................................................... 9-40
Example ........................................................................................................................... 9-41
Chapter 10. Administration

10.1 Administrative Information ................................................................................................. 10-1
10.2 Copying Files within ETX-5.................................................................................................. 10-2
File Names in the Unit...................................................................................................... 10-2
Displaying Files within ETX-5 ............................................................................................ 10-4
Displaying the List of Configuration Files and their Contents ........................................... 10-5
Example – Displaying the List of Configuration Files .................................................... 10-5
Example – Displaying the Contents of startup-config File ............................................ 10-5
Example – Displaying the Contents of Application Files ............................................... 10-6
Deleting Files .............................................................................................................. 10-6
Saving the Configuration ............................................................................................. 10-6
10.3 Date and Time.................................................................................................................... 10-7
Benefits ........................................................................................................................... 10-7
Transport Protocol ...................................................................................................... 10-8
Client Operation Mode ................................................................................................ 10-8
Configuring Date and Time............................................................................................... 10-8
Displaying the Date and Time .......................................................................................... 10-9
Example ........................................................................................................................... 10-9
SNTP Configuration .......................................................................................................... 10-9
Defining SNTP Servers ................................................................................................. 10-9
Configuring SNTP Server Parameters ......................................................................... 10-10
Example .................................................................................................................... 10-10
10.4 Displaying CPU Utilization Information .............................................................................. 10-11
10.5 Displaying Login Banner ................................................................................................... 10-12
10.6 Displaying Memory Utilization Information ....................................................................... 10-12
10.7 Downloading/Uploading Files ........................................................................................... 10-13
Configuration and Software Files ................................................................................... 10-14
Example – Download via SFTP ........................................................................................ 10-14
Example – Upload via SFTP ............................................................................................. 10-15
10.8 Inventory.......................................................................................................................... 10-15
Displaying Inventory Information ................................................................................... 10-15
Displaying Inventory Component Information ................................................................ 10-15
ETX-5 xiii
Displaying Manufacture Information .............................................................................. 10-16

Setting Administrative Inventory Information ................................................................. 10-17
Example ......................................................................................................................... 10-17
10.9 Resetting ETX-5 ............................................................................................................... 10-19
Resetting to Factory Defaults ........................................................................................ 10-19
Resetting to Prior-to-Shipment State............................................................................. 10-19
Resetting to User Defaults ............................................................................................. 10-20
Rebooting the ETX-5 Chassis ......................................................................................... 10-20
Resetting the Module .................................................................................................... 10-20
10.10 Scheduling ................................................................................................................ 10-21
Benefits ......................................................................................................................... 10-21
Scheduling Commands .............................................................................................. 10-21
Scheduling Summer Time .......................................................................................... 10-22
Configuring Command Scheduling .................................................................................. 10-22
Configuring Summer Time Scheduling ............................................................................ 10-23
Viewing Scheduling Information ..................................................................................... 10-24
Examples ....................................................................................................................... 10-25
10.11 Technical Support Status ........................................................................................... 10-27
Benefits ......................................................................................................................... 10-27
Default show Commands .......................................................................................... 10-27
Custom show tech-support Command List ................................................................ 10-28
Show tech-support Command Output File ................................................................. 10-28
Examples ................................................................................................................... 10-29
Chapter 11. Monitoring and Diagnostics

11.1 Detecting Problems ............................................................................................................ 11-1
Indicators......................................................................................................................... 11-1
Alarms and Traps ............................................................................................................. 11-1
Statistic Counters ............................................................................................................ 11-2
Configuration Error Messages .......................................................................................... 11-2
11.2 Handling Events ................................................................................................................. 11-2
Masking ........................................................................................................................... 11-3
Alarm Buffer .................................................................................................................... 11-3
Alarm Relays .................................................................................................................... 11-4
Configuring Alarm Reporting ............................................................................................ 11-4
Examples ..................................................................................................................... 11-6
Controlling Popup Behavior .............................................................................................. 11-7
Working with the Alarm and Event Logs ........................................................................... 11-7
Example 1: Displaying Active Alarms ............................................................................ 11-9
Example 2. Displaying Active Alarms Details ................................................................ 11-9
Example 3: Displaying Information of LOF alarm on SDH/SONET port .......................... 11-9
Example 4. Alarm Log ................................................................................................ 11-10
Example 5. Alarm List ................................................................................................ 11-10
Example 6. Displaying Brief Log ................................................................................. 11-11
Clearing Alarms ......................................................................................................... 11-11
Alarms and Events ......................................................................................................... 11-11
11.3 Running Diagnostic Tests ................................................................................................. 11-12
Running a Ping Test ....................................................................................................... 11-12
Tracing the Route .......................................................................................................... 11-12
xiv ETX-5
Testing Flows ................................................................................................................. 11-12

Ingress Flow Loopback .............................................................................................. 11-12
Egress Flow Loopback ............................................................................................... 11-13
Port Loopback ........................................................................................................... 11-15
11.4 Y.1564 Ethernet Service Activation Test ........................................................................... 11-16
Standards ...................................................................................................................... 11-16
Benefits ......................................................................................................................... 11-16
SLAs .......................................................................................................................... 11-17
Policing ..................................................................................................................... 11-17
Y.1564 Standard ....................................................................................................... 11-17
Test Elements ........................................................................................................... 11-19
Capacity .................................................................................................................... 11-19
Operation ................................................................................................................. 11-19
Test Procedures ........................................................................................................ 11-24
Configuring Y.1564 Test ................................................................................................ 11-27
Adding Y.1564 Test Profile ........................................................................................ 11-27
Adding Y.1564 Generator .......................................................................................... 11-29
Displaying Test Status (Generator Side) .................................................................... 11-31
Displaying Test Results.............................................................................................. 11-32
Adding Y.1564 Responder ......................................................................................... 11-36
Displaying Test Status (Responder Side) ................................................................... 11-37
Example ......................................................................................................................... 11-38
11.5 OAM CFM ......................................................................................................................... 11-42
Standards ...................................................................................................................... 11-42
OAM Elements........................................................................................................... 11-43
OAM Functions .......................................................................................................... 11-44
OAM Connectivity ...................................................................................................... 11-44
MEPs and Services ..................................................................................................... 11-45
MIPs .......................................................................................................................... 11-49
Messaging System ..................................................................................................... 11-53
Performance Monitoring............................................................................................ 11-56
Configuring OAM ............................................................................................................ 11-58
Configuring Maintenance Domains ............................................................................ 11-59
Configuring Maintenance Associations ...................................................................... 11-60
Configuring Maintenance Endpoints .......................................................................... 11-61
Configuring Maintenance Intermediary Points ........................................................... 11-63
Configuring Maintenance Endpoint Services .............................................................. 11-65
Configuring Destination NEs ...................................................................................... 11-66
Configuring a Measurement Bin Profile...................................................................... 11-67
Displaying OAM Statistics .......................................................................................... 11-68
Performing OAM Loopback ........................................................................................ 11-72
Performing OAM Link Trace ....................................................................................... 11-72
Examples ....................................................................................................................... 11-73
Example 1. Down MEP between Main Card Ports ....................................................... 11-73
Example 2. Down MEP between Main and I/O Card Ports........................................... 11-75
Example 3. Up MEP between Main Card and Bridge Ports .......................................... 11-79
Example 4. RMEP Configuration ................................................................................. 11-83
11.6 OAM EFM.......................................................................................................................... 11-86
ETX-5 xv
Standards ...................................................................................................................... 11-86

Benefits ......................................................................................................................... 11-86
Layer-2 Operation ..................................................................................................... 11-87
OAMPDUs .................................................................................................................. 11-87
Configuring OAM EFM .................................................................................................... 11-88
Displaying OAM EFM Status ............................................................................................ 11-89
Displaying OAM EFM Statistics ....................................................................................... 11-90
Example ......................................................................................................................... 11-90
11.7 Port/VLAN Mirroring ......................................................................................................... 11-91
Standards ...................................................................................................................... 11-91
Benefits ......................................................................................................................... 11-91
Inbound Mirroring ..................................................................................................... 11-91
Outbound Mirroring................................................................................................... 11-91
Configuring Port/VLAN Mirroring .................................................................................... 11-92
11.8 In-Service Ping.................................................................................................................. 11-95
Benefits ......................................................................................................................... 11-95
11.9 Quality of Service (QoS) ................................................................................................. 11-101
Standards .................................................................................................................... 11-102
Benefits ....................................................................................................................... 11-102
Factory Defaults .......................................................................................................... 11-102
Functional Description ................................................................................................. 11-102
Scheduling Elements ............................................................................................... 11-102
Dual Shaper and EIR Sharing ................................................................................... 11-102
Queuing .................................................................................................................. 11-105
Congestion Avoidance ............................................................................................. 11-106
Traffic Management Entities ................................................................................... 11-107
Post-Forwarding Traffic Management Entities ......................................................... 11-108
Pre-Forwarding Traffic Management Entities ........................................................... 11-119
Default Queue Profiles ............................................................................................ 11-120
Shaper ......................................................................................................................... 11-120
Factory Defaults ...................................................................................................... 11-121
Configuring Shaper .................................................................................................. 11-121
Example .................................................................................................................. 11-122
Configuration Errors ................................................................................................ 11-122
Congestion Avoidance (WRED) ..................................................................................... 11-122
Configuring WRED ................................................................................................... 11-123
Example .................................................................................................................. 11-123
Internal Queue ............................................................................................................. 11-124
Configuring Internal Queues .................................................................................... 11-125
Example .................................................................................................................. 11-125
Queue Block ................................................................................................................ 11-125
Configuring Queue Block ......................................................................................... 11-126
Example .................................................................................................................. 11-126
Queue Group ............................................................................................................... 11-126
xvi ETX-5
Configuring Queue Group ........................................................................................ 11-127

Example .................................................................................................................. 11-128
CoS Mapping ................................................................................................................ 11-130
Functional Description............................................................................................. 11-130
Configuring CoS Mapping ........................................................................................ 11-133
Example .................................................................................................................. 11-133
Color Mapping .............................................................................................................. 11-133
Configuring Color Mapping ...................................................................................... 11-135
Example .................................................................................................................. 11-135
Policing ........................................................................................................................ 11-135
Configuring Policer Profile ....................................................................................... 11-138
Configuring Policer Aggregate Profile ...................................................................... 11-139
Example .................................................................................................................. 11-139
Marking ........................................................................................................................ 11-140
Configuring Color-Blind Marking Profile ................................................................... 11-141
Configuring Color-Aware Marking Profile ................................................................. 11-141
Example .................................................................................................................. 11-141
Priority Queue Mapping ............................................................................................... 11-142
Example ....................................................................................................................... 11-142
11.10 Frequently Asked Questions .................................................................................... 11-151
11.11 Technical Support.................................................................................................... 11-152
Chapter 12. Software Upgrade

12.1 Compatibility Requirements................................................................................................ 12-1
12.2 Impact ................................................................................................................................ 12-1
12.3 Prerequisites ...................................................................................................................... 12-2
Software Files .................................................................................................................. 12-2
System Requirements ...................................................................................................... 12-2
12.4 Software Upgrade Options ................................................................................................. 12-2
12.5 Upgrading Software using the CLI....................................................................................... 12-2
Using SFTP ....................................................................................................................... 12-3
Pinging the PC .................................................................................................................. 12-3
Activating the SFTP Server ............................................................................................... 12-3
Downloading the New Software Release File to ETX-5 Flash Disk .................................... 12-3
Installing the New Software Release File from the Flash Disk........................................... 12-5
Confirmation of Software Application File ........................................................................ 12-6
Displaying Software Upgrade Status ................................................................................ 12-7
12.6 Upgrading Software via the Boot Menu .............................................................................. 12-8
Starting Boot Manager ..................................................................................................... 12-9
Using the FTP Protocol ................................................................................................... 12-11
12.7 Verifying the Upgrade Results .......................................................................................... 12-13
12.8 Restoring the Previous Software Version.......................................................................... 12-18
ETX-5 xvii
Chapter 13. Application Tutorial

13.1 Equipment List ................................................................................................................... 13-2
13.2 Installing the Units ............................................................................................................. 13-2
13.3 Preliminary Configuration ................................................................................................... 13-7
Resetting to Factory Defaults .......................................................................................... 13-7
Configuring Administrative Parameters ............................................................................ 13-8
Assigning Name to the Chassis ................................................................................... 13-8
Disabling CLI Timeout .................................................................................................. 13-8
Provisioning I/O Cards ................................................................................................. 13-8
Configuring Queue Groups ............................................................................................... 13-9
ETX-5 Queue Group Configuration............................................................................... 13-9
ETX-2 Queue Group Configuration............................................................................. 13-13
13.4 Configuring for Management ............................................................................................ 13-17
Configuring ETX-5 Management Flows ........................................................................... 13-18
Configuring ETX-203AX (1) Management Flows ............................................................. 13-25
Configuring ETX-205A Management Flows ..................................................................... 13-27
Configuring MiNID for Management ............................................................................... 13-29
13.5 Configuring Ethernet Ring Protection ............................................................................... 13-30
Configuring ERP Instance for ETX-203AX (1) .................................................................. 13-31
Configuring ERP Instance for ETX-5 ................................................................................ 13-34
13.6 Configuring LAG ............................................................................................................... 13-41
Configuring LAG for ETX-203AX (2) ................................................................................ 13-42
Configuring LAG for ETX-5.............................................................................................. 13-44
13.7 Configuring E-Line Service ................................................................................................ 13-48
Configuring E-Line for ETX-203AX (1) ............................................................................ 13-49
Configuring E-Line for ETX-5 .......................................................................................... 13-50
Configuring E-Line for ETX-205A .................................................................................... 13-53
Checking E-Line Connectivity .......................................................................................... 13-54
13.8 Configuring a Pseudowire Service ..................................................................................... 13-54
Configuring Pseudowire Service for ETX-205A ................................................................ 13-54
Configuring Pseudowire Service for ETX-5 ...................................................................... 13-56
Checking Pseudowire Connectivity ................................................................................. 13-58
13.9 Configuring OAM (CFM) .................................................................................................... 13-59
Configuring OAM (CFM ) for ETX-203AX (2) ................................................................... 13-59
Configuring OAM (CFM) for MiNID .................................................................................. 13-61
Displaying Traffic Statistics ............................................................................................ 13-63
13.10 Testing the Application ............................................................................................. 13-64
Checking E-line Connectivity .......................................................................................... 13-64
Checking Port/Flow Statistics ......................................................................................... 13-65
Appendix A. Connection Data

Appendix B. Test Plan
xviii ETX-5
Chapter 1
Introduction
1.1 Overview
ETX-5 is a 10G Carrier Ethernet access platform for aggregating SLA-based
business Ethernet, legacy TDM and mobile backhaul services.
ETX-5 Carrier Ethernet aggregator enables advanced rate policing and shaping,
and performs class of service differentiation through traffic editing. MEF-9, MEF-
14, MEF-22 and MEF-26 certified for E-Line (EPL, EVPL), E-LAN (EPLAN, EVPLAN),
E-Tree (EP-Tree and EVP-Tree) and E-Access services, ETX-5 ensures five nines
(99.999%) service reliability and exact service level agreement (SLA)
management. Its automatic fault localization capabilities also help carriers and
service providers to reduce operational costs and minimize expensive truck rolls.
In addition, ETX-5 delivers high-quality E1/T1, STM-1/OC-3 and STM-4/OC-12
streams, using Circuit Emulation Services (CES).
The ETX-5 system also features advanced Timing over Packet capabilities, allowing
for clock synchronization over packet switched networks. Clocking mechanisms
include Precision Time Protocol (IEEE 1588-2008), Synchronous Ethernet and
adaptive clock recovery. These Timing over Packet features, combined with
powerful Carrier Ethernet service delivery attributes, make the ETX-5 an ideal
solution for LTE mobile backhaul applications.
Product Options
ETX-5 is available with the following interface cards:
• GbE card with 20 copper or fiber optic GbE ports
• 10GbE card with two 10GbE ports
• STM-1/OC-3 card with up to four channelized STM-1/OC3 ports
• E5-cTDM-STM4 card with one channelized STM-4/OC12 port, or two ports
when using line APS
In addition, the chassis is designed to receive power from AC and/or DC sources.
Applications
In a typical service aggregation application, ETX-5 concentrates SLA-based traffic
coming from RAD’s or third-party Ethernet NTUs. It performs class of service
differentiation through traffic editing, uses advanced rate policing and shaping
techniques to ensure service reliability and exact service level agreement (SLA)
management.
ETX-5 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
Figure 1-1. SLA-Based Service Aggregation
In a mobile backhaul application (Figure 1-2), carrier-owned ETX-5 and ETX-2

devices use smart traffic management and Ethernet OAM tools to ensure
end-to-end service control and provisioning from the service hand-off points.
Access Network
Core Metro Aggregation First Mile
ETX-5
PCRF MME GbE DSL

G.8023v2
10GbE Ring
ETX-2
ETX-5 DSLAM BTS/Node B
GbE, TDM
10GbE
P-GW S-GW G.8023v2 GbE, 10GbE

10GbE Ring
TDM
ETX-5 ETX-2
RNC BSC BTS/Node B
Figure 1-2. Mobile Backhaul
Features
ETX-5 aggregates SLA-based business Ethernet, mobile backhaul and legacy TDM
services. It combines high-capacity aggregation and carrier-grade performance,
enabling cost optimization and freeing up expensive capacity at the PE (provider
edge). With efficient traffic management techniques, hardware-based OAM and
performance monitoring, carrier-grade service resiliency and strong Timing over
Packet capabilities, ETX-5 represents a robust multifunctional Ethernet service
delivery platform.
Carrier-Class Layer 2 Aggregation Switch

The ETX-5 powerful aggregation platform works opposite the ETX Carrier Ethernet
demarcation devices and the IPmux TDM pseudowire gateways. Together, they
provide a complete end-to-edge solution that allows carriers and service
providers to easily migrate from SDH/SONET to packet technology and to
converge voice and data services – both TDM- and packet-based –over Ethernet,
IP or MPLS networks.
Supported services include:
1-2 Overview ETX-5

Installation and Operation Manual Chapter 1 Introduction
• E-Line (EPL and EVPL) for LAN-to-LAN, VoIP and IP-VPN connectivity, as well
as for storage and dedicated Internet access
• E-LAN (EP-LAN and EVP-LAN) for multipoint Layer 2 VPN, transparent LAN
services and multicast networks
• E-Tree (point-to-multipoint) for combining multiple Ethernet technologies
across different domains
• E-Access for reaching the service provider’s out-of-franchise subscriber
locations as part of the end-to-end service
• 2G, 3GPP and LTE transport.
The 3U modular system features high port density for space-restricted facilities,
delivering user traffic via the following interfaces:
• Two redundant main cards, each housing four 10GbE network ports
• Up to four service cards, each housing either 20 UTP/SFP 1-GbE tributary
ports, or four channelized STM-1/OC-3 ports, or two 10GbE ports or their
combinations.
Forwarding Schemes
Traffic forwarding is performed using point-to-point (E-Line), bridge (E-LAN) or
static router mechanisms.
Remote Provisioning and Traffic Management

ETX-5 efficiently handles multi-priority traffic on a per-flow basis, with ultra-high
capacity that enables simultaneous processing of thousands of 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.
Enhanced quality of service is further supported by a 3-level hierarchical
scheduling mechanism that combines Strict Priority (SP) and weighted fair queue
(WFQ) scheduling, to efficiently handle real-time, premium and best-effort traffic.
Scheduling and shaping are supported at the EVC, tunnel and port levels.
ETX-5 also uses weighted random early detection (WRED) policy for intelligent
queue management and congestion avoidance. Packet editing capabilities include
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 and
WANs.
Hardware-Based Ethernet OAM and Performance Monitoring

ETX-5 features a comprehensive Ethernet OAM suite that includes Ethernet
Service OAM (IEEE 802.1ag) and Performance Monitoring (ITU-T Y.1731).
Hardware-based processing capabilities allow ETX-5 to perform OAM and PM
measurements in nanoseconds with maximum precision.
ETX-5 offers advanced SLA assurance tools, including user-defined KPI (key
performance indicators) threshold configuration for jitter, latency, packet loss
and availability. Other tools include real-time SLA violation alerts and per-flow
daily statistics reporting.
ETX-5 Overview 1-3

Service Resiliency and Protection

ETX-5 offers various tools to ensure five nines (99.999%) availability and sub-50
ms restoration in the event of network outages. These include Ethernet Link
Aggregation (LAG), dual homing (1:1 bidirectional Ethernet port redundancy) and
1+1 APS protection on the TDM ports. In addition, ETX-5 supports Ethernet Ring
Protection Switching (ERPS) per G.8032v2.
Synchronization and Timing over Packet

Incorporating RAD’s SyncToP synchronization and Timing over Packet feature set,
the ETX-5300A utilizes standard technologies to ensure highly accurate clock
recovery and distribution over both the physical and packet layers:
• Synchronous Ethernet (Sync-E) master and slave clock support per ITU-T
G.8261-G.8266, with primary/secondary clock redundancy
• 1588v2 Precision Time Protocol master, transparent and slave clock with
hardware-based time-stamping as well as ToD (time of day) synchronization
• 1 PPS, 10-MHz signal phase and frequency synchronization.
ETX-5’s SyncToP capabilities also include a built-in input/output clock interface
and support for multiple clock domains.
These provide exceptional value for wholesale mobile backhaul service providers,
ensuring the required service quality – such as ±16 ppb (parts per billion)
accuracy – while eliminating the need for costly dedicated hardware.
Management and Security

ETX-5 features flexible management capabilities, including local management via
an ASCII terminal (RS-232). In addition, remote management can be performed
either inband using the network or user ports, or out-of-band using a dedicated
management port, while maintaining separation between management and user
traffic via the use of VLANs. Advanced FCAPS (Fault, Configuration,
Administration, Performance, Security) and diagnostic tools are provided by
RADview-EMS, RAD’s carrier-class element management system, via an SNMP-
based GUI.
ETX-5 also supports a variety of access protocols, including CLI over Telnet, SNMP,
and TFTP. Incorporated security features include Secure Shell (SSH), Web-based
Secure Socket Layer (SSL), SNMPv3, RADIUS and Terminal Access Controller
Access-Control System (TACACS+).
1-4 Overview ETX-5

1.2 New in This Version

Version 2.8 of ETX-5 features L2CP profile enhancements (see section 8.5).
1.3 Physical Description

Figure 1-3 shows a general front view of an ETX-5 chassis. The ETX-5 chassis is
modular, and has a height of 3U.
The chassis is intended for installation in 19-inch (ANSI) and ETSI racks using rack
mounting kits available from RAD (not shown in Figure 1-3), however it can also
be installed on shelves. Air intake and discharge vents are located on the side
walls.
Figure 1-3. ETX-5 Front View
Front Panel
The front side of the chassis has physical slots in which plug-in modules are
installed to obtain the desired equipment configuration:
• The main and power inlet modules, and the fan tray, are always installed in
dedicated chassis slots, called system slots
• GbE, 10GbE and SDH/SONET service modules are installed in the other chassis
slots (called I/O slots).
All the external connections are made to connectors located on the plug-in
modules.
Figure 1-4 shows typical ETX-5 rear views, and identify the functions of the
various slots.
ETX-5 Physical Description 1-5

Main Cards Power Inlet Cards
10GbE EXT CLK GPS MNG

1 2 3 4
EXT CLK IN OUT TOD 1PPS MNG ETH CONTROL PRI E5-PIM
RAD
FLT
DCE
CLK PWR ETX-5300A
LINK ACT LINK ACT LINK ACT LINK ACT 10MHz LINK ACT FLT
RMV
E5-MC-4 10/100/1000BASE-T
1 2 3 4 MNG ETH PRI
EXT CLK IN OUT TOD 1PPS CONTROL E5-PIM
FLT
CLK PWR
DCE ALARM CRITICAL
LINK ACT LINK ACT LINK ACT LINK ACT 10MHz LINK ACT FLT
RMV MAJOR
E5-MC-4 10/100/1000BASE-T
MINOR
11 20 LINK ACT
TEST
LINK FLT 11 FLT
ACT LED
RMV RMV
1 1
E5-GBE-20 100/1000BASE-X E5-GBE-20 10/100/1000BASE-T FAN
OK
11 20 20
FLT OC-3/STM-1 FLT FLT
LINK FLT FLT FLT FLT
ACT LINK 1 LINK 2 LINK 3 LINK 4 F MAIN-B PS-B
I
RMV RMV L MAIN-A PS-A F
1 T A
I/O 2 I/O 4 N
LOS LOS LOS LOS E
E5-GBE-20 100/1000BASE-X E5-cTDM-4 R I/O 1 I/O 3 E5-FAN
Service (I/O) Cards Fan Tray
Figure 1-4. Typical ETX-5 Front View
Rear Panel
The ETX-5 rear panel may have mechanical extension for housing two AC power
supplies.
Available Cards
Table 1-1 lists the cards currently available for the ETX-5, their functions, and
ETX-5 system capacity.
Table 1-1. ETX-5 Cards
Card Function Maximum Chassis Capacity
E5-PIM/AC Single port AC power input module (110–240 VAC, 2

50/60 Hz)
E5-PIM/DC Single port DC power input module (48 VDC) 2
E5-MC-4 Main card, contains 4 × 10GbE ports, system control 2

circuits and its timing subsystem
E5-MC-SFP-P-4 Main card, contains 4 x 1/10 GbE SFP+ ports, system 2

control circuits and its timing subsystem
E5-FAN Fan tray with eight fans and alarm relay port 1
E5-GBE-20 GbE card with20 × GbE ports, SFP or UTP 4
E5-10GBE-2 10GbE card with2 × 10GbE ports 4
E5-cTDM-4 SDH/SONET card with 4 × channelized STM-1/OC-3 ports 4
E5-cTDM-STM4 SDH/SONET card with 2 × channelized STM-4/OC-12 ports 4

(second port for APS only, does not support 2x622)
1-6 Physical Description ETX-5

1.4 Functional Description

This section provides a functional description of the ETX-5 system that
supplements the information above.
System Structure
The ETX-5 is a fully redundant 3U chassis for Ethernet aggregation applications.
The chassis accommodates four I/O cards and two main cards.
Figure 1-5 illustrates a high-level structure of an ETX-5 system, in which:
• Two main cards include forwarding engines (packet processors) responsible
for bridging, point-to-point VLAN cross-connect, and Level-3 forwarding
(router). They also perform post-forwarding scheduling and shaping (at port
egress). Four 10GbE ports on each main card forward aggregated traffic
towards network.
• Four I/O cards are interconnected with the main card via the chassis
backplane in a star topology. Ethernet I/O cards include 20 GbE or two 10GbE
ports. The cards perform ingress traffic processing and management
(pre-forwarding scheduling and shaping).
TDM I/O cards include four channelized STM-1/OC-3 ports. The TDM cards
handle TDM pseudowire traffic.
• System modules (power inlets and AC power supplies, fan module) provide
DC or AC power to the system and cool the chassis.
ETX-5 Functional Description 1-7

4 x 10GbE 4 x 10GbE
Main Card Main Card
Timing Timing
Packet Common Packet Common

Processor Logic Processor Logic
Power
GbE, 10GbE or
SDH/SONET
I/O Card
Fans
Figure 1-5. High-Level Architecture of ETX-5
I/O-to-Main and Main-to–I/O Traffic Path

Figure 1-6 illustrates the data flow and main traffic management functions
performed by Ethernet I/O and main cards.
Main and I/O cards are interconnected via two 10GbE internal ports, which
provide 20 GbE bandwidth path with a non-blocking arch.
1-8 Functional Description ETX-5

I/O to Main Card Direction
Pre-Forwarding Post-Forwarding
Map CoS Scheduling Scheduling and
Classify Police Forward Edit
and Color and Shaping Shaping
20 x GbE Ethernet Main Card

or Ethernet I/O Card 2 x 10GbE or 4 x 10GbE
2 x 10GbE SFP+ Main Card
Post-Forwarding
Scheduling and Map CoS
Edit Forward Classify
Shaping and Color
Main to I/O Card Direction
Figure 1-6. Ingress and Egress Data Flow
I/O Card to Main Card Direction

In general, the I/O card performs flow classification, CoS and color mapping and
policing. It supports a hierarchical scheduling and shaping at its egress to do a
pre-forwarding scheduling and shaping (post-forwarding shaping at network
egress is done by the main card).
Editing and forwarding (bridging, EVC cross-connect, routing) is done by the main
card. Classification, as well as packet CoS and color information is available for
the main card for further processing.
Main Card to I/O Card Direction

Classification, forwarding decisions, editing and user port egress scheduling and
shaping are done by the main card. Packets from the main card are sent to the
appropriate port without any packet processing (no policing, priority mapping
etc).
Port Types
ETX-5 ports can be either of two types:
• Attached directly to the main card packet processor (directly-attached ports).
These are 10GbE ports on the main cards.
• Attached to the packet processor via the classification and traffic
management engine (indirectly-attached ports). These are GbE, 10GbE and
TDM ports on the I/O cards.
These ports differ in the way they admit traffic, classify flows, and perform traffic
management.

Data Path
Figure 1-7 illustrates the general traffic path within the ETX-5 system in the
ingress-to-egress direction.
Figure 1-7. Data Path
Note SAG (Service Aggregation Group) is a logical port (management entity) that
represents a physical connection between Ethernet I/O and main cards. Pre-
forwarding scheduling and shaping are performed at the SAG level.
Flow aggregation and pseudowire aggregation entities are logical ports that
create an aggregated classification identification for all Ethernet flows and
pseudowires going in the same direction. This identification allows the main card
to make forwarding decisions. The Ethernet flow aggregation entity is referred to
as SAP (Service Attachment Point); for pseudowires it is called SVI (Service Virtual
Interface).

Pre-forwarding
Processing Drop Precedence
(VLAN/Ethertype Per Port L2CP Classification Per Flow L2CP Traffic Class
Handling to Flows Handling (CoS) Mapping (Color) Ingress
recognition and Mapping
admission)
Ingress Scheduling First-Level VLAN Second-Level VLAN

and Shaping (using Editing (using traffic Forwarding (bridge, Editing (using traffic
Policing router or VLAN
traffic classes and classes and drop classes and drop
drop precedence) precedence) cross-connect) precedence)
Ethernet I/O Post-forwarding

Cards only Scheduling and
Shaping (using
traffic classes and
drop precedence)
Figure 1-8. Detailed Ingress-to-Egress Packet-Processing Flow
Main Cards
Two types of main card are supported by the ETX-5:
• E5-MC-4 - Standard Main Card
• E5-MC-SFP-P-4 - SFP/SFP+ Main Card
The ETX-5 automatically detects the card type upon card insertion. Both card
types can be used at the same time, each in one of the two main card slots.
Main Card Functionality

Main cards perform three primary functions:
• Control functions:
 Interfacing with the network management stations, supervision terminals,
and Telnet hosts.
 Control of ETX-5 system operation.
 Storage of application software, which determines the capabilities and
features provided by the ETX-5.
 Storage of configuration databases.
 Collection of operational history (alarms, performance statistics, etc.).
• 10GbE interface function: Each card provides the interface to 10GbE packet-
switched networks for the ETX-5 packet traffic. It has four external ports,
which can be ordered with XFP transceivers with optical interfaces.
• Clock and timing generation functions: generates nodal clock signals for the
ETX-5 system, locked to user-selected internal or external sources.
Only one main card is required per ETX-5 chassis; however, the chassis has two
slots dedicated to this type of module. The second slot is used to install a
redundant main card, thereby providing a hot-standby capability for the ETX-5
10GbE, system control and timing functions. The active and second main card can

be either a standard main card or an SFP+ main card. A protection LAG is

supported between these two card types.
When a second card is installed, the two cards operate as an active/standby pair;
one module is the active card, and the other serves as a hot standby.
Additionally, the four 10GB ports of the standby card can be used without any
limitation, exactly as the active main card ports.
However, only the active card communicates with the management
station/terminal and actively manages the ETX-5 system. The standby card is
automatically updated by the active card with all the configuration and status
data, and therefore the standby can take over at any time without disrupting
system operation. The standby card communicates only with the master module.
Moreover, the transmit line in the standby serial port connectors is disabled, to
enable physical connection in parallel (e.g., by means of a Y-cable) to a
management facility.
Figure 1-9 illustrates main card block diagram for both types of main card.
Backplane
Bus
Power
4 x 10GbE Quad 10GbE

Packet
XFPs Physical
Processor
Interface
ToD/1 PPS
Timing
BITS/10 MHz
RS-232
CPU
10/100/1000BT
Figure 1-9. Main Card Block Diagram
10GbE Interface
ETX-5 main cards provide four interfaces (10GBase-SR, 10GBase-LR, 10GBase-ER)
for full duplex connection to 10GbE packet-switched networks. They support IP
and Ethernet networks, and are capable of processing data at wire speed. In the
case of the SFP+ card, each interface is equipped with SFP+ interfaces.
Each 10GbE port has its own MAC address, and can be assigned its own IP
address for Layer-3 forwarding.

In addition to forwarding user data, the 10GbE interfaces distribute synchronous

Ethernet timing (master and slave mode).
Packet Processor
With 100 Gbps full duplex performance, the packet processor (PP) serves as:
• Main engine for point-to-point (E-Line), bridging (E-LAN, E-Tree) and routing
(Layer-3) forwarding schemes
• Post-forwarding scheduler and shaper (see Figure 1-10, Figure 1-11 and
Figure 1-12)
• Hardware-based OAM utility.
With 2- or 3-levels hierarchical scheduler, multiple queues per shaper, strict and
WFQ priorities, WRED congestion avoidance, the egress traffic management (TM)
mechanism consists of the following queue group types:
Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
WFQ 3
Up to 8 Up to 8
WFQ 4
CIR WFQ 5
Shapers
WFQ 6
SP 1
WFQ 7
SP 2
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Figure 1-10. Type 1 Queue Group

Level-0 SEs
CIR
Shapers Level-1 SEs
SP 1 WFQ 1
CIR/EIR
SP 2 Shapers WFQ 2
CIR/EIR
SP 3
Shapers
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 383
WFQ 2
CIR
WFQ 4 WFQ 384
Shaper
Up to 384 Up to 384 Up to 64 Up to 64
CIR WFQ 1
Shapers
WFQ 2
SP 1 WFQ 63
WFQ 64
SP 2
SP 3
SP4
WFQ 1 WFQ 383
WFQ 2 WFQ 384
WFQ 3
WFQ 4
Level-1 SEs
WFQ 1
Level-0 SEs WFQ 2
CIR/EIR CIR/EIR
SP 1 Shapers Shapers
SP 2
Level-2 SE
SP 3
SP4 WFQ 1
WFQ 383 WFQ 2 CIR

Shaper
WFQ 384
WFQ 1
WFQ 2 WFQ 63
SP 1 WFQ 64
SP 2
SP 3
SP4
WFQ 383
WFQ 384

Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
Up to 40 Up to 40
CIR
Shapers
SP 1
SP 2
WFQ 40
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
WFQ 3
Up to 50 Up to 50
WFQ 4
CIR WFQ 5
Shapers
WFQ 6
SP 1
WFQ 7
SP 2
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Timing Subsystem
See Timing Mechanism section below for detailed description of clocking schemes
supported by ETX-5.

Management Subsystem
The main functions of the management subsystem located on the main card
module are as follows:
• Interfacing with external management and monitoring functions. The
following options are available:
 Supervision terminal: ASCII terminal or a PC running a terminal emulation
program, connected directly to ETX-5. This terminal can perform all the
ETX-5 supervision and configuration functions, and in particular the
preliminary system configuration.
 Telnet: by means of any host capable of IP communication with ETX-5.
The functions available under the Telnet protocol are similar to those
available from a supervisory terminal.
 SSH: secure access using the SSH (Secure Shell) protocol, using any
standard SSH client utility running on a PC or laptop capable of IP
communication with ETX-5.
 SNMP: ETX-5 includes an internal SNMP agent that enables full SNMP
management by SNMP-based network management, for example, the
RADview family of management stations for element and network
management available from RAD.
 Syslog: ETX-5 supports automatic event notification to user-specified
Syslog servers in accordance with the Syslog protocol per RFC 3164. ETX-
5 can report all the supported traps and alarms, but also enables
configuring the minimal severity level for reporting to each Syslog server.
To protect network operations against unauthorized access, ETX-5 supports a
wide range of security features for every management facility: RADIUS
authentication for supervision terminal and Telnet access, SSH for secure
Telnet access, and SNMP management with authentication and privacy per
SNMPv3 using selectable security models, with support for SNMPv1 and
SNMPv2.
To record and track information on device operation and user activity on it,
ETX-5 supports TACACS+ client application. The application provides shell,
system and command accounting.
• Control of ETX-5 system operation.
• Storage of application software, which determines the capabilities and
features provided by the ETX-5. This software can be remotely downloaded
and updated through the management link without taking the equipment off-
line. The stored software includes both system software, run by the main
card, and software for the other modules installed in the chassis.
• Storage of configuration databases (factory-default, running, startup or user-
default). See Chapter 3 for explanation of startup procedure and different
types of configuration databases.
• Collection of operational history (alarms, performance statistics, etc.), and of
internal chassis temperature, as read by an internal temperature sensor. The
collected information can be read by maintenance personnel through the
management link.

A real-time clock provides time stamps for all the collected information. The
real-time clock can be set either manually or automatically, using the NTP
(Network Time Protocol). A network operator can use NTP to periodically
synchronize the local equipment time within the managed network to the
accurate time provided by the worldwide network of NTP time servers, and
thus is able to reliably correlate alarm reports from different sources. To use
NTP, it is necessary to configure the IP address of the desired NTP server, and
select a time zone.
The performance statistics collected for the modules installed in the chassis
are also synchronized to the real-time clock.
Out-of-Band Ethernet Port

The main card has an internal Layer-2 Ethernet switch that serves management
communications. The switch is connected to the chassis buses to provide
management access to the ETX-5 management subsystem network or user
interfaces. The switch is also connected to external 10/100/1000BaseT Ethernet
interface terminated in the CONTROL ETH RJ-45 connector serves, which serves
for out-of-band management access.
Serial Port
The supervisory port of the ETX-5 has a serial RS-232 asynchronous DCE interface
terminated in a 9-pin D-type female connector, designated CONTROL DCE. This
port is connected directly to terminals using the CBL-DB9F-DB9M-STR cable
available from RAD.
The SFP/SFP+ Main Card

The SFP/SFP+ main card, E5-MC-SFP-P-4, provides the same level of support as
the E5-MC-4 standard main card, described above, with the following differences:
Interfaces:
• On card 4x10GbE XFP interfaces
• On card 4x1/10GbE SFP+ interfaces
 Automatic recognition of SFP type and Rate (1GbE or 10GbE)
 Card type is provisioned automatically upon card insertion
• The port ‘MAU Type’ parameter determines if the port is 1G or 10GbE.
• The default ‘MAU Type is 10GbE. Changing the MAU type can be done only if
the port is in ‘shutdown’. A port can have a No shutdown status only if it’s
MAU type is the same as the second port MAU Type (ONLY if the second port
is in ‘no shutdown’, otherwise ‘no shutdown’ is allowed with no limitation).
Ethernet Service Cards

ETX-5 supports two types of Ethernet I/O cards:
• E5-GbE-20 with 20 fiber optic (SFP) or electrical GbE interfaces
• E5-10GbE-2 with two fiber optic (XFP) 10GbE interfaces.

The cards provide physical connection to user equipment, perform packet

processing and distribute synchronous Ethernet timing (master and slave mode).
Figure 1-15 illustrates block diagram of the Ethernet I/O cards.
Backplane
Bus
Power
20 x GbE
SFPs/RJ-45s Physical Packet
or Interface Processor
2 x 10GbE XFPs
Timing
CPU
E5-GbE-20 or E5-10GbE-2 Card
Figure 1-15. E5-GbE-20 and E5-10GbE-2 Block Diagram
GbE and 10GbE Interface Cards

E5-GbE-20 cards provide 20 interfaces (1000BaseSx, 1000BaseLx, 100BaseFX,
10/100/1000BaseT) for connection to GbE packet-switched networks.
E5-10GbE-2 cards provide two interfaces (10GBase-SR, 10GBase-LR,
10GBase-ER) for full duplex connection to 10GbE packet-switched networks.
Ethernet interfaces support autonegotiation (except for 100BaseFX), flow control
with maximum frame size of up to 12K.
Packet Processor
Packet processor (PP) located on the E5-GbE-20 and E5-10GbE-2 cards serves for
classification, CoS/color mapping, policing and pre-forwarding traffic management
(Figure 1-16).

Level-0 SEs
SP 1
SP 2
CIR
SP 3
Shapers
SP4
WFQ 1 Level-1 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 2
WFQ 4
Up to 50 Up to 50
SP 1
SP 2 WFQ 49
SP 3 WFQ 50
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Figure 1-16. Pre-Forwarding Traffic Management
Timing Subsystem
See Timing Mechanism section below for detailed description of clocking schemes
supported by ETX-5.
I/O Card Data Flow Schematics

GbE and 10GbE cards introduce logical ports that serve as management entities
(SAG) and flow aggregation points (SAP). Figure 1-17 illustrates Ethernet I/O card
schematics.
Each Ethernet I/O card has two SAGs, serving ports 1–10 and 11–20, respectively,
on the E5-GbE-20 card. Likewise, SAG 1 serves port 1 and SAG 2 serves port 2 on
the E5-10GbE-2 card. Each SAG includes 1024 SAPs, which aggregate ingress
flows from I/O card ports.

Flow
SAP
1-10 GbE ports on E5-GbE-20

1 10GbE port on E5-10GbE-2 SAG
Flow SAP
Flow
SAP

Flow SAP
Figure 1-17. Ethernet I/O Card, Data Forwarding Entities
SDH/SONET Card
The E5-cTDM-4 and E5-cTDM-STM4 cards operate as a quad/dual-port
SDH/SONET terminal multiplexer for the ETX-5 chassis that terminates STM-1/OC-
3 or STM-4/OC-12 links and their overhead. The E5-cTDM-4 card has four
independent channelized STM-1/OC-3 ports, where each port is capable of
multiplexing up to 63 E1 or 84 T1 internal streams into one STM-1 or OC-3 data
stream. The card uses pseudowire emulation to deliver E1/T1 streams over
packet-switched networks (UDP/IP or Ethernet MEF-8).
The E5-cTDM-4 card features two STM-4/OC-12 ports which can support a single
channelized STM-4 interface (second port for APS and cannot be an independent
interface). The card supports 252 E1s or 336 T1s with TDM pseudowire
emulation ( UDP/IP or Ethernet MEF-8)
Figure 1-18 illustrates the E5-cTDM-4 card block diagram.

Figure 1-18. E5-cTDM-4 Block Diagram
SDH/SONET Interfaces
The TDM interfacing subsystem provides interfaces to the TDM user’s equipment
or network. The physical STM-1/OC-3 or STM-4/OC-12 ports support a wide
variety of SFP transceivers with optical interfaces for meeting a wide range of
operational requirements.
SDH Interface
The SDH interface provides physical STM-1/STM-4 interfaces for direct access to
the Synchronous Digital Hierarchy (SDH) transmission cores at the STM-1 level
(155.520 Mbps) or STM-4 level(622,080 Mbps), and also handle the TDM traffic
flow between ETX-5 internal E1 ports, and the SDH network. Total module
capacity is 252 E1 data streams.
For the E5-cTDM-4 Card:
E1/T1 mapping to STM-1 is performed using the G.707 mapping scheme:
• E1 > VC-12 > TU-12 > TUG-2 > TUG-3 > VC-4 > AU-4 > STM-1
• T1 > VC-11 > TU-11 > TUG-2 > VC-3 > AU-3 > STM-1.
For the E5-cTDM-STM4 Card:
E1 mapping to STM-4 is performed using the G.707 mapping scheme:
• E1 > VC-12 > TU-12 > TUG-2 > TUG-3 > VC-4 > AU-4 > STM-4

SONET Interface
SONET interface provides physical OC-3/OC-12 interfaces for direct access to the
Synchronous Digital Hierarchy (SONET) transmission cores at the OC-3 level
(155.520 Mbps) or at the OC-12 level (622.080 Mbps), and also handles the TDM
traffic flow between ETX-5 internal T1 ports, and the SONET network. Total
module capacity of 336 T1 data streams.
T1 mapping to OC-3 is performed using the G.707 mapping scheme: T1 > VT1.5 >
VT group > STS-1 > OC-3.
T1 mapping to OC-12 is performed using G.707 mapping

scheme: T1 > VT1.5 > VT group > STS-1 > OC-12E5-cTDM-
STM4 and E5-cTDM-4 cards
APS supports the following schemes:
• MSP 1+1 unidirectional as per ITU G.841
• supported for STM-1/OC-3 for inter card and intra card ports.
• supported for E5-cTDM-STM4/OC-12 for inter and intra card ports.
• Inter card APS for E5-cTDM-STM4/OC-12 supported using port #1
• Intra card APS for E5-cTDM-STM4/OC-12 supported using port #1 as working,
and port #2 as protection
STM-1/OC-3 and STM-4/OC-12 line loopbacks are supported for diagnostics.
Pseudowire Services
The pseudowire processing subsystem performs the conversion between the
circuit-switched (TDM) and packet-switched networks, using pseudowire
emulation technology. The main steps of the circuit emulation procedure are the
following:
• SDH/SONET payload received via STM-1or STM-4interfaces is processed by
the framer to extract timing information and separate E1/T1 timeslots (the
framer creates an internal E1/T1 ports, which are connected through the
mapper to the SDH/SONET link).
• The resulting payload is provided to packet processor. The packet processor
converts the payload of each E1/T1 into packets suitable for transmission
over the packet-switched network.
• The resulting packets are encapsulated in Ethernet frames and sent to the
main card for analyses and forwarding to the UDP/IP or Ethernet (MEF-8)
network.
ETX-5 uses the following payload encapsulation techniques during packet
processing:
• CESoPSN transports raw TDM data, that is, packets are formed by inserting a
user-specified number of complete TDM frames in the packet payload area.
Therefore, CESoPSN pseudowires can only be configured on framed ports.
• SAToP is different from the CESoPSN, in that it is used to transparently
transfer a bit stream at the nominal port rate (2.048Mbps for E1 or 1.544

Mbps for T1). Therefore, SAToP can be used only when the port uses the
unframed mode.
Notes Only one pseudowire can be configured per port. In ETX-5 this is the only option
for both SAToP and CESoPSN.
The SAToP packet overhead is large, and therefore, for efficient bandwidth
utilization, the number of raw TDM bytes per packet should be as large as
possible.
Packetizing Considerations
The number of TDM bytes per frame affects several performance aspects:
• Bandwidth utilization. Because of the relatively short payload, the bandwidth
utilization efficiency depends on the overhead that must be transmitted to
the network in order to support the transmission of a certain amount of
payload.
 The overhead depends on the packet structure: for example, for UDP/IP
networks the overhead is 50 bytes when using VLANs, and 46 bytes
without VLANs
 The payload depends on the number of TDM bytes.
For example, when using the payload size of 48 bytes, bandwidth utilization
efficiency is around 50%.
• Packetizing delay. Bandwidth utilization efficiency increases when using a
large payload size per frame. However, there is additional aspect
(packetization time) that must be considered when selecting the size of the
packet payload. When E5-cTDM-4 or E5-cTDM-STM4 card builds a frame, a
packetization delay is introduced. The packet creation time (PCT) is different
for the different payload encapsulation methods. It is calculated according to
the following formulas:
Mode Delay
CESoPSN PCT (ms) = N × 0.125

Where:
N = Number of TDM frames in packet
SAToP N × 0.125
PCT (ms) = TS
N – Number of TDM bytes in packet

TS – Number of timeslots in one frame (32 for E1 or 24 for T1)
• Round-trip delay. The voice path round-trip delay is a function of all

connections and network parameters. The delay value, ±2 msec, is given by:
RT Delay(msec) = 2 × (PCT + Jitter Buffer Level) + network round trip delay
Increasing payload size reduces the ratio between the IP/Ethernet header
segment in the packet and the payload, thus reducing the total Ethernet
throughput.

On the other hand, packetization delay is increased; this contributes to a

higher end-to-end delay. This effect can be small and negligible when a full
E1/T1 (or many timeslots) are transferred, but can be very significant when
few timeslots are transferred.
Configuring the TDM bytes per frame (TDM bytes/frame) parameter has
impact on the Ethernet throughput (bandwidth or traffic traveling through
the Ethernet). This parameter controls the number of TDM bytes
encapsulated in one frame.
Sometimes, it is necessary to evaluate the transmission bandwidth required on
the PSN, which also depends on the number of TDM bytes.
Jitter Buffer Functions

The packets of each pseudowire are transmitted by pseudowire emulation
modules at essentially fixed intervals towards 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: in this case, the packets arrive at regular
intervals (these intervals are equal to the intervals at which they had been
transmitted). In reality, however, 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, each
pseudowire emulation module 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:
• Since 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 out 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, the pseudowire packet processing subsystem 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, the pseudowire packet processing
subsystem starts processing the packets and empty out 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 0 to 32 msec.
• The read-out rate must be equal to the average rate at which frames are
received from the network. For this purpose, the read-out rate must be
continuously adapted to the packet rate, a function performed by the
adaptive clock recovery mechanism of each packet processor.
After the jitter buffer mechanism reaches a stable state, there may still be
temporary changes in network delay, which occur before the mechanism can
readjust.
Adaptive Timing
Each PDH port can use the adaptive timing mode to lock its transmit timing to the
clock signal associated with the payload carried by this pseudowire.
The adaptive clock recovery mechanism estimates the average rate of the
payload data received in the frames arriving from the packet-switched network.
Assuming that the packet-switched network does not lose data, the average rate
at which payload arrives will be equal to the rate at which payload is transmitted
by the source.
Note
Generally, lost packets, as well as packets that did not arrive in the correct order,
are replaced by special dummy packets. However, for CESoPSN and SAToPSN,
packets can be reordered.
The method used to recover the payload clock of a pseudowire is based on

monitoring the fill level of the selected pseudowire jitter buffer: the clock
recovery mechanism monitors the buffer fill level, and generates a read-out clock
signal with adjustable frequency. The frequency of this clock signal is adjusted so
as to read frames out of the buffer at a rate that keeps the jitter buffer as near
as possible to the half-full mark. This condition can be maintained only when the
rate at which frames are loaded into the buffer is equal to the rate at which
frames are removed. Therefore, the adaptive clock recovery mechanism actually
recovers the original payload transmit clock.
The performance of the clock recovery mechanism can be optimized for the
operating environment, by specifying the following parameters:
• The accuracy of the original timing source, in accordance with the standard
SDH/SONET terminology (Stratum 1, 2, 3, 3E, or 4/unknown)
• The type of PSN that transports the traffic: router-based network (for
example, UDP/IP) versus switch-based network (for example, Ethernet).

Timing Subsystem
See Timing Mechanism section below for detailed descriptions of clocking
schemes supported by ETX-5.
Timing Mechanism
ETX-5 timing subsystem includes a central timing subsystem, located on the main
card, and local timing subsystems located on the individual I/O modules. Since
ETX-5 is normally equipped with two main cards, redundancy is also available for
the central timing subsystem.
The figure below shows the functional block diagram of the ETX-5 timing
mechanism.
Main Card
System 10GbE
Clock Ports
I/O
Clock 1
I/O
Clock 2
1588v2 T0 1588v2
(master) SEC Mux (slave) Station Clock
Station Clock Output (T4)
(BITS/GPS)
Station Clock
Output (T4)
Secondary Clock via

Standby Main Card
I/O Card 1
I/O Card 2
I/O Card 3
I/O Card 4
Figure 1-19. Timing Mechanism
The timing system in ETX-5 is based on one domain with master and fallback
clocks. The domain has its own system clock derived after selection process
implemented via SEC (Synchronous Equipment Clock). Clock sources (SEC inputs)
are based on:
• Clock derived from a physical port on a main or I/O card
• External clock (BITS)

• IEEE 1588v2 clock

• GPS clock.
The SEC outputs a clock with Stratum-3 accuracy, jitter and holdover, complying
with the following requirements:
• GR-253-CORE for SONET Stratum 3 and SONET minimum clock (SMC)
• GR-1244-CORE Stratum 3
• ITU-G813 Option 1 and Option 2 for SDH Equipment Clock (SEC).
Physical Port Clock

The ETX-5 clock domain can be configured to use timing information derived from
an STM-1, OC-3 or SM-4/OC-12, E1, T1 or GbE or 10GbE port located on an I/O or
main card.
Ethernet Ports
Ethernet ports located on E5-MC-4, E5-MC-SFP-P-4, E5-10GbE-2 or E5-GbE-20
support Synchronous Ethernet (Sync-E) master and slave modes according to ITU-
T G.8261–G.826 requirements. This allows each port to:
• Extract the port clock to be used a source clock to the clock selection
mechanism
• Set the port Tx clock according the domain clock available from the main card.
Sync-E mode can be used for clock frequency distribution. If the ToD (time) is not
required, the 2-way 1588v2 slave entities can be used. The main advantage of
Sync-E over 1588v2 clock is that it is distributed over physical layer; it is a
Stratum-3 clock with near SDH/SONET holdover properties; it is not packet-
oriented and is considered to be more stable.
SDH/SONET Ports
An Rx clock of any STM-1/OC-3 or STM-4/OC-12 port on the E5-cTDM-4 card can
be extracted and supplied to the main card clock selection mechanism (via
backplane clock bus).
Note When APS is enabled, the clock is used from a selected interface and not from an
APS group.
A Tx clock of an SDH/SONET port can be locked to:

• ETX-5 system clock
• Rx clock of the port.
E1/T1 Ports
An Rx clock of any internal E1 or T1 port on the E5-cTDM-4 or E5-cTDM-STM4
card can be extracted and supplied to the main card clock selection mechanism
(via backplane clock bus). Moreover, ETX-5 can use an adaptive clock, recovered
from a TDM pseudowire stream as an Rx clock source.
A Tx clock of an internal E1/T1 port can be locked to:
• ETX-5 system clock

• Rx clock of the same port

• Adaptive clock (clock signal associated with payload carried by a pseudowire
connected to this E1/T1 port).
External (BITS) Clock

The external clock interface has two functions:
• Input for external (station) clock signal
• Output for the ETX-5 nodal clock. This output provides a convenient means
for distributing the ETX-5 nodal clock signal to other equipment.
ETX-5 recovers Building-Integrated Timing Supply (BITS) clock via the station clock
interface ports on E5-MC-4 or E5-MC-SFP-P-4 card. See Appendix A for the
external clock connector pinout.
The following clock signals are supported:
• 2.048 Mbps, ITU-T G.703, 120Ω balanced, 75Ω balanced
• 1.544 Mbps, ANSI T1-403, 100Ω balanced
• 2.048 MHz squarewave, RS-485
• 64 kHz, ITU-T G.703, composite clock interface, 110Ω balanced.
When only one external clock source is available, you can improve hardware
protection by connecting the external clock inputs in parallel, by means of a
Y-cable.
IEEE 1588v2 Clock

ETX-5 fully supports IEEE 1588v2 clock distribution scheme. The chassis can be a
grand master and distribute 1588 streams; it can terminate 1588 stream to
recover the clock; or it can forward 1588 packets transparently to other devices
for clock termination.
IEEE 1588v2 clock signals are received and transmitted via 10GbE and GbE ports
on the main and I/O cards. Synchronization rate of the received clock can be at
16, 32, 64 or 128 pps. The output clock signal is at 2.048 MHz / 1 pps + TOD.
Master Mode
Using 1588v2 master mode eliminates the need for an external timing device
installed in the core of the network to support 1588v2 timing distribution. The
ETX-5 device can be located near the core of the network to supply up to 512
clock reference streams to remote Ethernet CPEs. Currently, only UDP/IP
encapsulation is supported.
Slave Mode
In the 1588v2 slave mode, ETX-5 provides clock recovery mechanism with
frequency and phase alignment. Currently, only UDP/IP encapsulation is
supported.
Transparency Mode
If there is a 1588v2 grandmaster in the network, ETX-5 can operate in
transparent clock mode, transferring 1588 packets to remote Ethernet CPEs with

updated correction field. In this case remote a CPE can operate in a slave mode, if
a NodeB has no slave clock capabilities, or in transparent mode if a NodeB
supports 1588v2.
GPS Clock
ETX-5 accepts GPS-based frequency and phase reference signal from GPS units,
using the following interfaces on the E5-MC-4 or E5-MC-SFP-P-4 card:
• Input or output of 10 MHz sinewave synchronization signal via mini-BNC
connector
• Input and output of ToD timestamp signal via RJ-45 connector with RS-422
interface
• Input or output of 1 pps TTL synchronization signal via mini-BNC (DIN 1.0/2.3)
connector.
When only one GPS clock source is available, you can improve hardware
protection by connecting the GPS clock inputs in parallel, by means of a Y-cable.
Performance Management Portal

ETX-5 supports real-time monitoring of QoS and CoS, producing real-time
statistics and interval statistics. You can collect full device statistics in
compressed format, minimizing bandwidth use by management traffic. You can
also export CSV ASCII files to OSS or third-party management systems.
The Performance Management 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
Temperature-Hardened and NEBS-Compliant Chassis

ETX-5 is available as temperature-hardened or NEBS-compliant (DC only) chassis
intended for street-cabinet and cellular-tower installations. The
temperature-hardened chassis operates within extended temperature range –20
to 65°C (-4 to 149°F). The temperature-hardened model requires hardened main,
I/O and service cards, as well as industrially hardened SFPs and XFPs.
1.5 Technical Specifications
System Number of I/O Cards Up to 4

Capacity
ETX-5 Technical Specifications 1-29

Number of Main UP to 2; second card provides redundancy

Cards
Max Throughput 100 Gbps, full duplex (100 Gbps ingress and 100 Gbps
egress)
10GbE Number of Ports 4 per E5-MC-4 or E5-MC-SFP-P-4 card

Interface
2 per E5-10GbE-2 card
Transceiver Type Fiber optic SFP+/XFP, flow control:

• 10GBase-SR, 850 nm, 550m (1804 ft)
• 10GBase-LR, 1550 nm, 10 km (6.2 mi)
• 10Gbase-ER, 1550 nm, 40 km (24.8 mi)
Maximum Frame 12 kbytes (12284 bytes for I/O card ports)

Size
Maximum MTU • configurable port MTU, range <64-12,284>, for IO card

ports only. By default, set to 12,284,
• MTU for main card ports is set to 12,284 and cannot
be changed.
• Packets, forwarded to a specific port that exceed the
port’s Egress MTU limit are dropped
Connector LC
GbE Interface Number of Ports 20 per E5-GbE-20 card
Transceiver Type Fiber optic SFP/SFP+:

• 1000BaseSX, multimode, 850 nm, autonegotiation,
flow control
• 1000BaseLX, single mode, 1300 nm, autonegotiation,
flow control
• 100BaseFX, full duplex only, flow control
Electrical Interface 10/100/1000BaseT, full duplex only, autonegotiation,

flow control, MDI-X
Maximum Frame 12 kbytes

Size
Connector LC (fiber optic)

RJ-45 (electrical)
SFP+ Interface ETX-5 supports the SFP-P-4D

following SFP+ types: Standards: 10GBASE-SR
Wavelength: 850nm
Length: 300m over 50/125 MM fiber
1-30 Technical Specifications ETX-5

SFP-P-1DH
Standards: 10GBASE-LR
Wavelength: 1310nm
Length: 10KM over 9/125 SM fiber
SDH/SONET Number of Ports 4 STM-1/OC-3 per E5- cTDM-4 card

Interface
2 per E5-cTDM-STM4 card
Physical Layer SDH: ITU-T Rec. G.957

SONET: ITU-T Rec. G.703, Para. 12
Nominal Bit Rate 155.520/622.080 Mbps
Framing SDH: ITU-T Rec. G.707, G.708, G.709

SONET: GR-253-CORE and ANSI T1.105
Transceiver Type Fiber optic SFP
Channelization 63 E1 or 84 T1 per G.707/Y.1322
Mapping SDH: E1 > VC-12 > TU-12 > TUG-2 > TUG-3 > VC-4 > AU-4
> STM-1
• T1 > VC-11 > TU-11 > TUG-2 > VC-3 > AU-3 > STM-1
SONET: T1 > VT1.5 > VT group > STS-1 > OC-3
Jitter G.958, G.825
Tributaries E1, 2.048 Mbps or T1, 1.544 Mbps
E1 Framing Unframed, multiframe with or without CRC-4
T1 Framing Unframed, SF, ESF
SDH/SONET System, port Rx clock (loopback) when chosen as a RX

Transmit Clock clock source of a system domain clock
E1/T1 Transmit System, port Rx clock (loopback), adaptive

Clock
E5-cTDM- Number of Ports 2 per card

STM4
Physical Layer G.707/Y.1322
Nominal Bit Rate 622.080 Mbps
Framing SDH: ITU-T Rec. G.707, G.708, G.709

SONET: GR-253-CORE and ANSI T1.105

Transceiver Type Fiber optic SFP
Channelization 252 E1 or 336 T1 per G.707/Y.1322
Mapping • E1 -> VC-12 -> TU-12 -> TUG-2 -> TUG-3 -> VC-4 ->
AU-4 -> STM-N
• T1 -> VT1.5 -> VT Group -> STS-1 -> OC-N
Jitter G.958, G.825
Tributaries E1, 2.048 Mbps or T1, 1.544 Mbps
E1 Framing Unframed, multiframe with or without CRC-4
T1 Framing Unframed, SF, ESF
STM Transmit Clock System, port Rx clock (loopback) when chosen as a RX

clock source of a system domain clock.
E1/T1 Transmit System, port Rx clock (loopback), adaptive

Clock
Ethernet Forwarding 802.1D, 802.1Q, 802.1ad

Forwarding
Number of EVCs 4K
Number of Shaped 384 (per network port)

EVCs
Services E-Line (EPL, EVPL), E-LAN (EPLAN, EVPLAN), E-Tree (EP-Tree,

EVP-Tree)
Compliance MEF 9, MEF 14, MEF 22, MEF 26
Traffic QoS Mechanism SP + WFQ

Management
Policer Dual Token Bucket mechanism (two rates, three colors)

CIR, CBS, EIR, EBS
Color Mode Color-aware and color-blind
Standard MEF 10.1
CIR/EIR Range Indirectly-attached ports: 0–10 Gbps

(1 kbps Granularity)
Directly- attached ports: 0, 64 kbps – 10 Gbps

CIR/EIR Resolution 0–16.384 Mbps: 1 kbps

(Actual Rate)
0–16.384 –163.84 Mbps: 10 kbps
163.84 Mbps–1.6384 Gbps: 100 kbps
1.6384–10 Gbps: 1 Mbps
Note: The actual rate is rounded up according to the
resolution.
CBS/EBS Range Indirectly-attached ports: 0–2 Mbytes

(1 byte Granularity)
Directly-attached ports: 0–1 Mbyte
CIR/EIR Resolution 1 byte

(Actual Value)
Policer 0–63 byte (indirectly-attached ports only)

Compensation
Policers : 2000 per IO card , 8k per main card
Policer BW profiles : Up to 128
Hierarchical 3-level
Scheduler
Queue Group Profiles Up to 128 (user-defined and default)
Default: 4 (3 egress and 1 ingress)
Queue Block Profiles Up to 384 (user-defined and default)

Default: 4
Queue Profiles Up to 16K
Shaper Profiles Up to 256
Congestion Control WRED
Bridge Mode VLAN-aware, IVL
Number of Instances Up to 32
Number of Ports Up to 128 per bridge instance
Number of Broadcast Up to 4K per system

Domains
Number of MAC 256K (max)

Table Entries
MAC Table Size 64 (default), 256, 512, 1024, 4094, 16384, user-
configurable per broadcast domain
MAC Address Aging 300–3600 sec

Router Number of Router 1

Instances
Number of Interfaces Up to 128

(RIFs)
Number of Routing Up to 1K, static

Table Entries
Number of ARP Table Up to 1000, dynamic

Entries
Multiple IP addresses Up to 10 for IPv4 and IPv6

per router interface
Pseudowire Number of TDM 1344 (336 per E5-cTDM-4 and E5-cTDM-STM4 cards)
Pseudowires
Payload CESoPSN, SAToP

Encapsulation
Network UDP/IP, MEF-8

Encapsulation
Protection Chassis E5-MC-4 or E5-MC-SFP-P-4 card, E5-PIM card
E5-cTMD-4 and For SDH: 1+1 unidirectional MSP per G.841 (section 7.1),
E5-cTDM-STM4
For SONET: 1+1 unidirectional APS per GR-253-CORE
cards
(section 5.3)
E5-MC-4, E5-MC- LAG, Ethernet Ring Protection per G.8032

SFP-P-4, E5-GBE-20
Up to 64 G.8032 Rings per shelf (Main rings + sub rings)
Cards
Up to 63 sub rings per ring
Timing Number of Clock 1 (master and fallback)

Domains
Nodal Clock • GR-253-CORE for SONET Stratum 3 and SONET

minimum clock (SMC)
• ITU-G813 Option 1 and Option 2 for SDH Equipment
Clock (SEC)
Clock Sources Up to 4 inputs for selection mechanism

1588v2 recovered, station (BITS/GPS) , I/O port Rx, main
card port Rx
1588v2 Master/slave/transparent (TC)

Sync-E Master/slave, ITU-T G.8261–G.8266, with

primary/secondary clock redundancy
Station Clock (BITS) Input and output:

• 2.048 Mbps, ITU-T G.703, 120Ω balanced,
75Ω balanced
• 64 kHz, ITU-T G.703, composite clock interface, 110Ω
balanced
GPS 10 MHz, sinewave via mini BNC (DIN 1.0/2.3), input or

output
ToD, RS-422 via RJ-45 (input and output)
1 PPS TTL interface via mini BNC (DIN 1.0/2.3), input or
output
OAM CFM 8021.1ag, Y.1731
Number of MDs Up to 4K
Number of MAs Up to 4K, with up to 4K MA defined under one MD
Number of Up to 4K (256 MIPs)

MEPs/MIPs
Up to 1 Down MEP per MA
Up to 88 Up MEPs per MA
Up to 1K/2K MEPs with LM (Low PM scale/High PM scale)
Up to 1K/2K MEPS with DM (Low PM scale/High PM scale)
Number of PM Up to 2K
Services
Number of PM flow 2k in low PM scale, 4k in high PM scale

counters
EVC’s supporting OAM 1000/2000 per PM scale configuration

PM
Number of RMEPs Up to 8K MEP-RMEP pairs per shelf with up to 512 RMEPs

per MEP
Number of Loss Up to 2K (single and synthetic) per chassis

Measurement
Sessions
Diagnostics SDH/SONET, E1/T1 User-activated loopback, inband T1 loopback
IP Connectivity Ping, trace route

Management Management Supervision terminal

Capabilities
Telnet
SSH
SNMP (RADview-EMS and other SNMP-based network

management stations)
LLDP
Management Utility CLI
SNMP Management SNMPv1, SNMPv2, SNMPv3

Capabilities
Management • Serial ports on main card

Interfaces • 10/100/1000BaseT port on main card, supports
Telnet, SSH, and SNMP
• Inband via network or user ports, supports for Telnet,
SSH, and SNMP
• LLDP
Serial Control Port Interface: RS-232 asynchronous DCE

Characteristics
Data Rate: 0.3, 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 57.6 and
115.2 kbps
Connector: 9-pin D-type female
User Authentication Password-protected login, RADIUS, TACACS+
Out-Of-Band Interface – 10/100/1000BaseT

Ethernet
Duplex mode – Full duplex only.
Management Port
Default maximum capability –100 Mbps full duplex.
Autonegotiation, MDI-X, no flow control
Maximum frame size – 1518 bytes
Connector –RJ-45
Default IP Address The IP address of the RI is 169.254.1.1/16

for Management
Flows, SVI and RI are assigned with indexes at the high
end of the range and reserved flow names.
• SVI # : 4000
• RI # : 128
• Flows : mng_access_default_in , mng_access_default_out
Alarm Alarms Last 256 time-stamped alarms stored in buffer

Collection and
Alarm synchronization, correlation, severity indication,
Monitoring
masking

RMON RFC 2819
Syslog RFC 3164
Alarm Relay Alarm Outputs Major alarm indication by floating change-over dry-
contact contacts
Minor alarm indication by floating change-over contacts
Output Contact Max. 60 VDC/30 VAC across open contacts

Ratings
Max. 1 ADC through closed contacts
Max. load switching capacity: 60W
External Alarm Input One active-low input, RS-232 levels
Indicators E5-PIM PWR (green) – Input power is OK

FLT (red) – Hardware failure is detected
E5-FAN OK (green) – Fans are operating properly

FLT (red) – Hardware failure is detected
CRITICAL (red) – Critical alarm is detected
MAJOR (orange) – Major alarm is detected
MINOR (yellow) – Minor alarm is detected
TEST (yellow) – Test in progress
E5-MC-4 RMV (blue) – Safe extract mode

FLT (red) – Hardware, software or power failure is detected
PRI (green) – Primary/secondary card mode
CLK (red) – Station clock status
LINK (green) – 10GbE or GbE link status
ACT (yellow) – 10GbE or GbE activity status
E5-MC-SFP-P-4 RMV (blue) – Safe extract mode

PRI (green) – Primary/secondary card mode
CLK (red) – Station clock status
LINK (green) – 10GbE or GbE link status
ACT (yellow) – 10GbE or GbE activity status
E5-10GBE-2 LINK (green) – 10GbE link status

ACT (yellow) – 10GbE activity status
RMV (blue) – Safe extract mode

E5-GBE-20 LINK (green) – 10GbE link status

ACT (yellow) – 10GbE activity status
E5-cTDM-4 and E5- ON LINE (green) – Card administrative status

cTDM-STM4 cards
LOS (red) – Loss of synchronization is detected
Power AC Power 100 to 240 VAC (115/230 VAC nominal), 50/60 Hz
DC Power 40–72 VDC (48 or 60 VDC nominal)
Power Consumption AC: 590W max, 540W average under full traffic load
DC: 520W max, 480W average under full traffic load
Physical Regular Enclosure Height: 133 mm (5.2 in)

Width: 440 mm (17.3 in)
Depth: 380 mm (15 in), DC version
Depth: 455 mm (23.6 in), AC version
Weight: 12 kg (26.4 lb), maximum
NEBS-Compliant Height: 132.5 mm (5.2 in)

Enclosure (DC only) Width: 541.6 mm (21.3 in)
Depth: 385.2 mm (15.1 in)
Weight: 20 kg (44 lb), maximum
Environment Temperature Storage: -20 to +70°C (0 to 150°F)

Operating:
• Regular enclosure: 0 to 50°C (32 to 122°F)
• Temperature-hardened enclosure: –20 to 65°C (-4 to
149°F)
Humidity 0 to 93%, non-condensing
Cooling Internal fan tray

Chapter 2
Installation and Setup
This chapter provides installation instructions for the ETX-5 systems, including
the installation of the modules that are part of the basic system configuration.
This chapter presents the following information:
• General description of the equipment enclosure and its panels.
• Mechanical and electrical installation instructions for the enclosure itself and
the fan tray, power inlets, AC extension shelf and AC power supplies, main
and I/O cards.
After the system is installed, it must be configured it in accordance with the
specific user's requirements. The preliminary system configuration is always
performed by means of a supervision terminal (procedures for using the terminal
are detailed in Chapter 4). The software necessary for using the terminal is
stored in the main cards: if the main cards are not yet loaded with the required
software, refer to Chapter 12 for detailed software installation instructions.
After the preliminary configuration, the system can also be managed by means of
Telnet hosts or SNMP-based network management stations, e.g., RADview. Refer
to the User's Manual of the network management station for operating
instructions.
2.1 Safety
Before starting, read the following safety precautions, which are applicable
throughout the installation procedures. Where necessary, specific precautions
also appear before certain procedures.
No internal settings, adjustment, maintenance, and repairs may be performed by

either the operator or the user; such activities may be performed only by a skilled
technician who is aware of the hazards involved. Always observe standard safety
Warning precautions during installation, operation, and maintenance of this product.
ETX-5 Safety 2-1

Chapter 2 Installation and Setup Installation and Operation Manual
Caution Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the ETX-5 cards. To prevent physical damage:
• Always keep cards in their protective packaging until installed in the
ETX-5 chassis, and return them to the packaging as soon as they are removed
from the enclosure.
• Do not stack cards one above the other, and do not lay any objects on PCBs.
• After removing a card from a slot, wait at least four seconds before
reinserting it.
• When inserting a card into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the card PCB does not touch
the adjacent cards, or any part of the chassis. If resistance is felt before the
card fully engages the mating backplane connector, retract the card, realign it
with the slot guides and then re-insert.
Grounding
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the lines connected to the equipment, the ETX-5 case must be properly
grounded (earthed) at any time. Any interruption of the protective (grounding)
Grounding connection inside or outside the equipment, or the disconnection of the
protective ground terminal can make this equipment dangerous. Intentional
interruption is prohibited.
Dangerous voltages may be present on the electrical cables connected to the

ETX-5 and its cards.
Warning • Never connect cables to ETX-5 if not properly installed and grounded.
• Disconnect all the cables connected to the electrical connectors of the
ETX-5 before disconnecting its grounding connection.
Before connecting any other cable and before applying power to this equipment,
the protective ground terminal of the equipment must be connected to protective
ground. The grounding connection is made to the grounding terminal located on
the ETX-5 rear panel.
Whenever ETX-5 units are installed in a rack, make sure that the rack is properly
grounded and connected to a reliable, low-resistance grounding system, as the
rack can also provide a connection to the ground.
In addition, the grounding connection is also made through each one of the AC
power cables. Therefore, the power cable plug must always be inserted in a
socket outlet provided with a protective ground.
2-2 Safety ETX-5

Installation and Operation Manual Chapter 2 Installation and Setup
Laser Safety
ETX-5 modules 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
For your safety:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the optical transmitter.
• Do not use broken or unterminated fiber-optic cables/connectors.
• Do not look straight at the laser beam, and do not directly into the optical
connectors while the unit is operating.
• Do not attempt to adjust the laser drive current.
• The use of optical instruments with this product will increase eye hazard.
Laser power up to 1 mW at 1300 nm and 1550 nm could be collected by an
optical instrument.
• Use of controls or adjustment or performing procedures other than those
specified herein may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
ETX-5 modules equipped with laser devices provided by RAD comply with laser
product performance standards set by governmental agencies for Class 1 laser
products. The modules do not emit hazardous light, and the beam is totally enclosed
during all operating modes of customer operation and maintenance.
In some cases, the users may insert their own SFP or XFP laser transceivers into
ETX-5 modules. 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.
Wherever applicable, ETX-5 modules are shipped with protective covers installed
on all the optical connectors. Do not remove these covers until you are ready to
connect optical cables to the connectors. Keep the covers for reuse, to reinstall
the cover over the optical connector as soon as the optical cable is disconnected.
Protection against ESD

An electrostatic discharge occurs between two objects when an object carrying
static electrical charges touches, or is brought near enough, the other object.
Static electrical charges appear as result of friction between surfaces of insulating
materials, separation of two such surfaces and may also be induced by electrical
fields. Routine activities such as walking across an insulating floor, friction
between garment parts, friction between objects, etc. can easily build charges up
to levels that may cause damage, especially when humidity is low.
Caution ETX-5 modules contain components sensitive to electrostatic discharge (ESD). To

prevent ESD damage, always hold a module by its sides, and do not touch the
module components or connectors. If you are not using a wrist strap, before
touching a module, it is recommended to discharge the electrostatic charge of
your body by touching the frame of a grounded equipment unit.
ETX-5 Safety 2-3

Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistance,
yet are not insulators.
Proper Handling of Modules

ETX-5 modules include small components installed on both sides of the printed
circuit boards. These components are exposed as long as the modules are not
installed in the chassis, are therefore may be unintentionally damaged. To
prevent physical damage to modules:
1. Always keep the modules in their protective shipping containers until installed
in the chassis. These containers also protect against ESD.
2. Do not pile up modules.
3. When inserting modules into chassis slots, support the modules and make
sure their components do not touch the chassis structure, or other modules.
2.2 Site Requirements and Prerequisites
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
Warning
Caution ETX-5 does not have a power switch, and therefore will start operating as soon
as power is applied to one of the power supply inlets.
The external circuit breaker used to protect the input power line can be used as
an ON/OFF power switch, or an external ON/OFF switch may be installed.
Power
ETX-5 can be equipped with either AC or DC power inlet (PI) modules, which
conduct power from external sources to the ETX-5 backplane. There are two PI
module types:
• DC for 40–72 VDC (48 or 60 VDC nominal), up to 12A current
• AC for 100–240 VAC, up to 6A current. It operates in conjunction with AC
power supplies installed in a hardware extension at the back of the chassis.
The AC power supplies convert AC voltage into 48 VDC voltage.
ETX-5s with AC power supplies can be powered via any combination of PI cards: 2
× AC, AC and DC, 2 × DC.
ETX-5 without AC power supplies can be powered only via 2 × DC PI cards.
If one of the power feeds fails all the power is delivered by the redundant feed.
2-4 Site Requirements and Prerequisites ETX-5

AC Power
AC-powered ETX-5 units should be powered via easily-accessible grounded AC
outlets capable of furnishing 100, 115 or 230 VAC, 50/60 Hz.
The connection of AC power is made through the front panel AC power inlet
module. This module has a separate input connector for each AC power supply
module installed in the mechanical extension at the back of the chassis.
It is necessary to arrange a single ON/OFF power switch to simultaneously apply
power to all the ETX-5 power inlets. Powering AC power supply modules one at a
time may cause undesirable effects.
DC Power
DC-powered ETX-5 units require a 48 or 60 VDC (nominal voltage) power source
supplied over 14 AWG (1. 5 mm2) wires. The connection of DC power is made
through DC power inlet modules, which deliver the DC input voltage to power
supplies installed on main and I/O cards via two redundant backplane buses.
The second DC input enables connecting a separate DC input voltage, and thus
when power is connected to both DC input connectors, availability is increased by
having a redundant power source. The two DC inputs are isolated, and therefore
it is not possible for current to flow from one DC input to the other.
Caution The same nominal DC voltage must be supplied to both DC input connectors.
Each DC input must be protected by its own circuit breaker rated at 25A
maximum.
Warning
Within the ETX-5, the DC input supply lines are not referenced to the chassis
(frame) ground.
Panel Clearance
ETX-5 can be installed on shelves and in telecommunication racks. RAD offers
rack mount kits for installation in 19 inch (ANSI) racks or in ETSI racks.
Allow at least 70 mm (2.7 inches) of clearance at front, top, bottom and side for
cables and module replacement.
Note 70 mm (2.7 inches) clearance is sufficient for most telecommunication and power
connections (including fiber optic lines), but some more rigid cables (such as
Krone) require as much as 110 mm (4.3 inches) of clearance.
Ambient Requirements
The ambient operating temperature range of the ETX-5 is 32 to 122°F
(0 to +50°C), at a relative humidity of up to 93%, non-condensing.
ETX-5 Site Requirements and Prerequisites 2-5

Caution Do not operate ETX-5 without the fan tray installed. Irreversible damage to
hardware will occur if the chassis is operated without the fan tray installed, even
for a few minutes (maximum allowed at room temperature is 5 minutes).
Electromagnetic Compatibility Considerations

ETX-5 is designed to comply with the electromagnetic compatibility (EMC)
requirements of Sub-Part J of FCC Rules, Part 15 and EC regulations, for Class A
electronic equipment, and additional applicable standards.
To meet these standards, it is necessary to perform the following actions:
• Connect the ETX-5 case to a low-resistance grounding system.
• Install blank panels to cover all empty slots. Appropriate blank panels can be
ordered from RAD.
• Whenever possible, use shielded telecommunication cables.
Covering all empty slots is also required for reasons of personal safety and for
efficient cooling of the chassis.
Warning
2.3 Package Contents

The ETX-5 package includes the following items:
• ETX-5 chassis
• Power cords
• Hardware kit for rack installation
• Cable manager.
Cards are shipped either separately, or preinstalled in the chassis, in accordance
with your order. If your chassis is shipped with preinstalled cards, skip the card
installation procedures described below
2.4 Required Equipment

The cables needed to connect to ETX-5 depend on your specific application. You
can prepare the appropriate cables yourself in accordance with the information
given in Appendix A, or you can order cables from RAD.
2-6 Required Equipment ETX-5

2.5 Installing AC Power Supply Modules

AC-powered chassis have a mechanical extension at the back that accommodates
up to two AC power supplies.
The chassis accepts two power supplies that share the load. Each module can
supply a maximum of 500W.
 To install an AC power supply:

1. If necessary, disconnect the power cable connected to the corresponding
E5-PIM/AC connector or E5-PIM/DC terminal strip.
2. Check that the two fastening screws of the module are free to move.
3. Insert the PS module into upper or lower section of the mechanical extension
at the back of the chassis, and slide it in as far as possible.
4. Secure the PS module by tightening its two screws.
2.6 Installing the ETX-5 Enclosure

The ETX-5 is designed for installation on shelves and racks. Do not connect
power to the enclosure before it is installed in its designated position.
Installing Cable Managers

Cable managers provide cost-effective solution for organizing and protecting
telecommunication and power cables connected to ETX-5. Cable managers are
attached to the 19” and 23” brackets.
Figure 2-1 shows how to attach cable managers to 19” rack brackets.
Figure 2-1. Attaching Cable Managers to 19” Rack Brackets
ETX-5 Installing the ETX-5 Enclosure 2-7

Installing ETX-5 in Racks

For rack installation, it is necessary to install two brackets to the sides of the
unit. RAD offers the following rack mount kits:
• RM-ETX-5300-3U-19-FRONT, for front-edge installation in 19 “ racks
• RM-ETX-5300-3U-23-FRONT, for front-edge installation in 23” racks
• RM-ETX-5300-3U-23-FRAME, for mid-chassis installation in 23” racks
• RM-ETX-5300-AC-3U-19-FRONT, for front-edge installation and rear-end
fastening in 19” racks
Figure 2-2 shows how to attach the brackets supplied in the
RM-ETX-5300-3U-19-FRONT kit for front edge installation in 19” racks.
Figure 2-2. Attaching Brackets for Front Edge Installation in 19” Racks

RM-ETX-5300-3U-23-FRONT kit for front edge installation in 23” racks.
Figure 2-3. Attaching Brackets for Front Edge Installation in 23” Racks

RM-ETX-5300-3U-23-FRAME kit for mid-chassis installation in 23” racks.
2-8 Installing the ETX-5 Enclosure ETX-5

Figure 2-4. Attaching of Brackets for Mid-Chassis Installation in 23” Racks
Note Mid-chassis fitting, using the R RM-ETX-5300-3U-23-FRAME kit, meets the

requirements for seismic Zone 4 installations.
Figure 2-5 shows how to attach the front and rear brackets supplied in the
RM-ETX-5300-AC-3U-19-FRONT kit for front edge installation of AC-powered ETX-
5 devices in 19” racks.
AC power supplies increase the unit’s depth and weight. Installation of
AC-powered ETX-5 devices in 19” racks requires additional brackets attached to
the rear of the chassis.
Figure 2-5. Attaching Brackets for Front Edge Installation and Rear Fastening in 19” Racks
 To install ETX-5 in the rack:

1. Identify the prescribed position of each ETX-5 in the rack, in accordance with
the rack installation plan.
2. With help from an additional person, place ETX-5 in its prescribed position,
and then insert the guide posts located on each bracket in the matching
holes in the rack side rails. This will help keep ETX-5 in position until it is
fastened to the rack with the screws.
ETX-5 Installing the ETX-5 Enclosure 2-9

3. While the other person holds ETX-5 in place, fasten the chassis to the rack
side rails with four screws, washers and nuts.
4. After installing the enclosure, check and install the required modules, in
accordance with the installation plan.
Figure 2-6 illustrates a 19” rack fully populated with twelve ETX-5 units.
Figure 2-6. Full Rack Installation
2-10 Installing the ETX-5 Enclosure ETX-5

2.7 Installing a Fan Tray

This section provides instructions for installing a fan tray in an empty chassis. The
same procedure is used to replace the fan tray.
The fan tray includes a total of eight fans that provide cooling air. The fans are
divided into two groups (four fans each), which are independently controlled by
main cards A and B.
The rotation speed of the fans, and thus the airflow, can be varied to adapt to
the cooling requirements; for example, when the temperature inside the
enclosure is sufficiently low, the speed is decreased to reduce wear and noise.
Figure 2-7 shows a view of the fan tray panel. The fan tray has two indicators,
pertaining to fan operation. The panel also has a 15-pin D-type female connector
serving as an alarm relay with LED indicators for alarm monitoring. The fan and
alarm relay indicators are described in Chapter 3.
RAD
ETX-5300A
ALARM CRITICAL
MAJOR
MINOR
TEST
LED
FAN
OK
FLT
F MAIN-B PS-B
I
L MAIN-A PS-A F
T A
I/O 2 I/O 4 N
E
R I/O 1 I/O 3 E5-FAN
Figure 2-7. Fan Tray Panel
Note The I/O slots labels are located on the fan tray panel.
 To install the fan tray:

1. Carefully check the fan tray for foreign objects and dirt that may be trapped
inside, and remove them.
2. Insert the fan tray in the chassis slot, and slide it in until its rear connector
engages the mating connector on the backplane.
3. Secure the fan tray by tightening its two spring screws.
Caution The cooling fan tray exhausts air from the chassis. The chassis cooling vents are
located in the side panel. Do not obstruct these vents. Leave at least 80 mm
(3.1 inch) clearance for sufficient airflow.
When replacing the ETX-5 fan tray in an operating chassis, do it quickly;
irreversible damage to hardware will occur if the chassis is operated without the
fan tray installed, even for a few minutes (maximum allowed at room
temperature is 5 minutes).
ETX-5 Installing a Fan Tray 2-11

2.8 Cleaning or Replacing Air Filter

The NEBS-compliant ETX-5 chassis is equipped with a user-serviceable air filter
which removes dust drawn into the chassis. In environments with exposure to
dust, examine the air filter and intake module panel for damage and cleanliness
at least once a month.
Caution Damage to the air filter and intake panel can restrict the airflow, causing
overheating in ETX-5, and degrading its performance. Be careful when cleaning
and replacing the air filter.
Air Filter Maintenance

Follow the procedure described below to remove the air filter assembly. If the air
filter is dirty, clean the filter, using pressurized air. Change the air filter if it is
torn or worn out.
Caution Do not vacuum the air filter while it is installed in the chassis. You must remove
the air filter completely before you clean it to prevent contaminants from being
drawn into the enclosure.
 To remove the air filter assembly:

1. Loosen the four screws on the intake panel.
2. Slide out the filter assembly.
3. If necessary, loosen the two screws on the side of the intake panel to
disconnect the air filter from the panel.
Figure 2-8. Removing the Air Filter Assembly
2-12 Cleaning or Replacing Air Filter ETX-5

Intake Module Panel Maintenance

Visually check the condition of the intake panel (if the air filter assembly is fitted
on the intake panel, remove it). If the intake panel is dirty, you need to clean the
panel. Remove the intake panel from the chassis. Clean the intake panel using
high pressurized air and replace it in the ETX-5 chassis.
2.9 Installing Power Inlet Modules

The connection of power to the ETX-5 power supply modules is made through
hot-swappable PI modules. Figure 2-9 and Figure 2-10 show the offered PI
modules. Chapter 3 describes the PI module indicators. DC connector pinout is
given in Appendix A.
E5-PIM
PWR
FLT
Figure 2-9. Power Inlet Module for DC Input
E5-PIM
PWR
FLT
Figure 2-10. Power Inlet Module for AC Input
E5-PIM/AC Module
The E5-PIM/AC module is used for connecting to 100–240 VAC power sources. The
E5-PIM/AC can be used only in ETX-5 units, that have AC power supplies installed
in the mechanical extension at the back of the chassis.
E5-PIM/DC Modules
The E5-PIM/DC modules are used for connecting to 40–72 VDC (48 VDC nominal)
power sources.
Installing PI Modules
Caution ETX-5 units with AC power supplies can be powered via any combination of PI
cards: 2 × AC, AC and DC, 2 × DC. ETX-5 without AC power supplies can be
powered only via 2 × DC PI cards.
 To install a PI module:
1. Check that the two fastening screws of the PI module move freely.
2. Insert the PI module in its chassis slot, and slide it in until its rear connector
engages the mating connector on the backplane.
3. Secure the PI module by tightening its two screws.
ETX-5 Installing Power Inlet Modules 2-13

2.10 Installing a Main Card

The ETX-5 chassis can be equipped with two main cards. At any time, only one
card is active, and the other serves as hot standby.
Figure 2-11 shows the front panel of the main card. Chapter 3 explains the
functions of the indicators located on the panel.
1 2 3 4 MNG ETH PRI
EXT CLK IN OUT TOD 1PPS CONTROL
FLT
CLK
LINK ACT LINK ACT LINK ACT LINK ACT 10MHz LINK ACT DCE
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-11. Main Card Panel
Inserting the Main Card

 To insert a main card:
1. Disconnect all cables from the main card to be installed.
2. Check that the two fastening screws of the card move freely.
3. Open the locking levers, see Figure 2-12.
1P
P
S
M
NG
ET MN
H G
10
M
Hz
LI N CO
K NT
10 AC RO
/1 0 T L
0 /1
00 PR
0B I
AS DC
E- E FL
T T
CL
K
RM
V
Figure 2-12. Opening the Locking Lever
4. Insert the card in its chassis slot, and slide the card in. Make sure that the
inner side of the locking levers (item 3 in Figure 2-12) engages the chassis
frame.
5. Push the locking levers forward to fully insert the rear connector of the card
into the mating connector on the backplane.
Make sure that the locking hooks (item 2 in Figure 2-12) snap into place.
6. Secure the main card by tightening its two screws.
2-14 Installing a Main Card ETX-5

Removing the Main Card

 To remove the main card:
1. Fully release the two screws fastening the module to the chassis.
2. Move the central plate (item 1 in Figure 2-12) of the locking levers to
disengage locking hooks (item 2 in Figure 2-12) from the frame and …
3. …swing the locking levers to disengage the rear of the card from the
backplane connectors.
4. Pull the card out.
Replacing a Main Card during Equipment Operation

ETX-5 Chassis with two CONTROL Modules
In an ETX-5 equipped with two functional main cards, the standby card can be
removed/replaced without disrupting ETX-5 services.
If you replace the on-line main card, ETX-5 automatically switches to the standby
card, provided that card is functional. However, because the active main card also
houses 10GbE ports and provides clock signals to all the ETX-5 subsystems, there
will be a short disruption in service. This disruption can be avoided by first
switching (flipping) to the standby card before replacing the on-line module. You
can identify the active and standby modules by their PRI (primary) indicators.
Caution
To prevent service disruption, check that the PRI indicator of the main card you
want to remove is blinking. If not, use the supervisory terminal (or any other
management facility) to instruct the ETX-5 to flip to the other main card, and
wait for execution of the command before continuing.
 To flip to the other main card using the supervision terminal:

1. Identify the on-line main card: this is the card with the steadily lit ACT
indicator.
2. Connect the supervision terminal directly to the CONTROL DCE connector of
the on-line main card, and log in as administrator.
3. Use the manual-switch command in the config>protection>main-card#
prompt to flip to the standby main card (the card with the blinking PRI
indicator).
4. Wait for the flipping to be executed. After it is executed, the PRI indicator of
the main card to which the supervision terminal is connected starts blinking;
the indicator of the other module stops blinking and lights steadily.
Note
The command is not executed if a fault is detected in the module that is to
become the on-line module. In this case, the PRI indicators state do not change.
5. You can now disconnect the supervision terminal, and remove the module.
ETX-5 Installing a Main Card 2-15

ETX-5 Chassis with Single Main Card

In an ETX-5 equipped with a single main card, it is recommended that before
replacing that main card, a functional main card be installed in the free slot. The
card replacement can be temporary.
After inserting the additional main card, first let it update its database from the
information provided by the existing main card. For this purpose, wait about 10
minutes before starting the replacement procedure described above for an ETX-5
with two main cards.
When replacing a single main card in the chassis, ETX-5 services will always be
disrupted to some extent while no main card is present. Therefore, be prepared
and perform the replacement as rapidly as possible.
2.11 Connecting to Power
Before connecting any cables and before switching on this instrument, the
protective ground terminal of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
Warning be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Caution ETX-5 does not have a power switch, and therefore it will start operating as soon
as power is applied to one of the power supply inlets.
The external circuit breaker used to protect the input power line can be used as
an ON/OFF power switch, or an external ON/OF switch may be installed.
Before connecting power to an AC-powered device, verify that every power inlet
card has a corresponding AC power supply installed in the chassis. The top E5-PIM
card is connected to AC power supply B, and the bottom E5-PIM card is
connected to AC power supply A.
Grounding
A grounding terminal is located on the front panel of the ETX-5 chassis.
 To ground the chassis:

1. Connect an 8 AWG (3.2 mm/0.12 inch) thick copper wire between the
grounding terminal on the ETX-5 front panel and a nearby grounding point.
2. Crimp the terminal to tighten the grounding connection.
Connecting to AC Power
 To connect to AC power:
• Connect each power cable first to the connector on the E5-PIM/AC module,
and then to the power outlet.
2-16 Connecting to Power ETX-5

Note When redundant power supplies are used, it is recommended to connect the
power cables to outlets powered by different circuits. However, it is necessary to
use one ON/OFF switch to simultaneously connect/disconnect all of them.
Connecting to DC Power
 To connect to DC power:
1. Strip 7 mm (1/4 inch) of insulation from the leads.
Caution
Pay attention to polarity. For each source, connect the positive lead first, and the
negative lead second.
Refer to the Connection of DC Mains section at the beginning of this manual.
2. Use a narrow blade screwdriver to release the terminal screw.

3. Push the lead into the terminal up to its insulating sleeve.
4. When the lead is in position, fasten the screw to secure the lead.
5. Verify that the lead is securely held by pulling on it lightly.
6. Insert the plug into the socket.
7. Secure the plug by tightening the two screws.
4 8/
PW 6 0V
R
F LT
-
+
E5
-PI
M
d
ea
eL
ti v
g a ad
Ne Le
e
s iti v
Po
Figure 2-13. Connection to E5-PIM/DC Terminals
ETX-5 Connecting to Power 2-17

2.12 Installing I/O Cards

The ETX-5 chassis can be equipped with up to four hot-swappable I/O (service)
cards.
Note Temperature-hardened chassis supports up to two temperature-hardened

E5-GBE-20 or E5-10GBE-2 cards.
Figure 2-11 shows the front panel of the main card. Chapter 3 explains the
functions of the indicators located on the panel.
11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
Figure 2-14. E5-GBE-20 Card Panel
10GbE
1 2
FLT
RMV
LINK ACT LINK ACT
E5-10GBE-2
Figure 2-15. E5-10GBE-2 Card Panel
20
OC-3/STM-1 FLT
FLT LINK 1 FLT LINK 2 FLT LINK 3 FLT LINK 4
RMV
LOS LOS LOS LOS
E5-cTDM-4
Figure 2-16. E5-cTDM-4 Card Panel
OC-12/STM-4
APS FLT
ON LINE 1 ON LINE 2
LASER
RMV
CLASS
1
LOS LOS
E5-cTDM-1
Figure 2-17. E5-cTDM-STM4 Card Panel
 To install an I/O card:

• Follow the procedure for main card installation to install each I/O module in
the prescribed I/O slot, in accordance with the installation plan.
2.13 Installing Blank Panels

Install blank panels in all the chassis slots that are not occupied by modules.
2-18 Installing Blank Panels ETX-5

2.14 Installing SFP/SFP+ or XFP Modules

ETX-5 uses SFP (GbE and SDH/SONET ports), or XFP (10GbE ports) modules with
LC fiber optic connectors.
Third-party SFP or XFP optical transceivers must be agency-approved, complying

with the local laser safety regulations for Class 1 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
the signal loss, leave a 3 dB margin. For example, instead of the 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/SFP+/XFP Transceivers data sheet.
 To install the SFP/SFP+ or XFP modules:

1. Lock the wire latch of each SFP/SFP+ or XFP module by lifting it up until it
clicks into place, as illustrated in Figure 2-18.
Note
Some SFP/SFP+ or XFP models have a plastic door instead of a wire latch.
Figure 2-18. Locking the SFP/SFP+ Wire Latch
2. Carefully remove the dust covers from the SFP/SFP+ or XFP slot.
3. Insert the rear end of the SFP/SFP+ or XFP into the socket, and push it in
slowly until the SFP/SFP+ or XFP clicks into place. If you feel resistance before
the connectors are fully mated, retract the transceiver using the latch wire as
a pulling handle, and then repeat the procedure.
Caution Insert the transceiver gently. Using force can cause damage to the connecting
pins.
4. Remove the protective rubber caps from the SFP/SFP+ or XFP modules.
ETX-5 Installing SFP/SFP+ or XFP Modules 2-19

 To remove the SFP or XFP module:

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

ETX-5 is connected to 10Gb Ethernet equipment via the fiber optic SFP/SFP+
transceivers with LC ports located on E5-MC-4, E5-MC-SFP-P-4, or E5-10GBE-2
cards. These ports are designated 10GbE.
Figure 2-19 and Figure 2-20 illustrate typical E5-MC-4 and E5-10GBE-2 cards with
10GbE ports.
 To connect to 10GbE equipment
• Connect ETX-5 to the 10GbE equipment at provider’s edge or customer
premises using standard fiber optic cables terminated with LC connectors.
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-19. 10GbE Ports on E5-MC-4 Card
10GbE
1 2
FLT
RMV
LINK ACT LINK ACT
E5-10GBE-2
Figure 2-20. 10GbE Ports on E5-10GBE-2 Card
2.16 Connecting to Gigabit Ethernet Equipment

ETX-5 is connected to Gigabit Ethernet equipment via the fiber optic SFP
transceivers with LC ports or RJ-45 electrical ports located E5-GBE-20 cards.
These ports are designated 100/1000BASE-X or 10/100/1000BASE-T,
respectively. Refer to Appendix A for the RJ-45 connector pinout.
Figure 2-21 and Figure 2-22 illustrate typical E5-GBE-20 cards with fiber optic and
electrical GbE ports.
 To connect to Gigabit Ethernet equipment with fiber optic interface:
• Connect ETX-5 to the Gigabit Ethernet equipment at customer premises using
standard fiber optic cables terminated with LC connectors.
2-20 Connecting to Gigabit Ethernet Equipment ETX-5

11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
Figure 2-21. Fiber Optic GbE Ports on E5-GBE-20 Card
 To connect to Ethernet equipment with a copper interface:

• Connect ETX-5 to the Gigabit Ethernet equipment at customer premises using
standard straight UTP cables terminated with RJ-45 connectors.
LINK ACT
11 FLT
RMV
1
E5-GBE-20 10/100/1000BASE-T
Figure 2-22. Electrical GbE Ports on E5-GBE-20 Card
2.17 Connecting to STM-1/OC-3 Equipment

ETX-5 is connected to STM-1/OC-3 equipment via the fiber optic SFP transceivers
with LC ports located on E5-cTDM-4 cards. These ports are designated OC-3/STM-
1.
Figure 2-23 illustrates typical E5-cTDM-4 cards with STM-1/OC-3 ports.
 To connect to STM-1/OC-3 equipment
• Connect ETX-5 to STM-1/OC-3 equipment at customer premises using
20
OC-3/STM-1 FLT
RMV
LOS LOS LOS LOS
E5-cTDM-4
Figure 2-23. STM-1/OC-3 Ports on E5- cTDM-4 Card
2.18 Connecting to STM-4/OC-12 Equipment

ETX-5 is connected to STM-4/OC-12 equipment via the fiber optic SFP
transceivers with LC ports located on E5-cTDM-STM4 cards. These ports are
designated OC-4/STM-12.
Figure 2-24 illustrates typical E5-cTDM-STM4 cards with STM-4/OC-12 ports.
 To connect to STM-4/OC-12 equipment
• Connect ETX-5 to STM-4/OC-12 equipment at customer premises using
OC-12/STM-4
APS FLT
ON LINE 1 ON LINE 2
LASER
RMV
CLASS
1
LOS LOS
E5-cTDM-1
ETX-5 Connecting to STM-4/OC-12 Equipment 2-21

Figure 2-24. STM-4/OC-12 Ports on E5-cTDM-STM4 Card
2.19 Connecting to External Clock Devices

ETX-5 supports station clock input and output via balanced RJ-45 or unbalanced
BNC ports on the E5-MC-4 or E5-MC-SFP-P-4 card. The external clock ports are
designated EXT CLK.
 To connect to external clock devices with balanced interface:

1. Prepare a cable in accordance with your particular application requirements,
using the information presented in Appendix A.
2. Connect the external clock source and/or slave clock device to the RJ-45
connector on the card designated EXT CLK. (RJ-45 uses different pins for
clock input and output.)
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-25. EXT CLK Port on E5-MC-4 Card
 To connect to external clock devices with unbalanced interface:

• Use two 75Ω coaxial cables to connect the external clock source and/or slave
clock device to the two BNC connectors on the card designated IN (input) and
OUT (output).
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-26. IN and OUT Ports on E5- MC-4 Card
2.20 Connecting to GPS Clock Devices

ETX-5 supports GPS-based Time of Day (ToD) clock input and output via RS-422
RJ-45 port on the E5-MC-4 or E5-MC-SFP-P-4 card designated TOD.
1 PPS and 10 MHz GPS-based clock input or output are provided via mini BNC (DIN
1.0/2.3) connectors on the card designated 1PPS and 10MHz, respectively.
 To connect to ToD clock device:

1. Prepare a cable in accordance with your particular application requirements,
using the information presented in Appendix A.
2. Connect the GPS-based ToD clock source and/or slave ToD clock device to the
RJ-45 connector on the card designated TOD. (RJ-45 TOD connector uses
different pins for clock input and output.)
2-22 Connecting to GPS Clock Devices ETX-5


1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-27. TOD Port on E5-MC-4 Card
 To connect to 1 PPS and 10 MHz GPS clock devices:

• Use coaxial cables with mini BNC (DIN 1.0/2.3) connectors to connect the GPS
1 PPS or 10 MHz clock source or slave clock device to the mini BNC
connectors designated IN (input) and OUT (output).
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-28. 1PPS and 10MHz Ports on E5-MC-4 Card
2.21 Connecting to a Terminal

ETX-5 is connected to an ASCII terminal via a 9-pin D-type female connector on
the E5-MC-4 or E5-MC-SFP-P-4 card designated CONTROL DCE. Refer to Appendix
A for the connector pinout.
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-29. CONTROL DCE Port on E5-MC-4 Card
 To connect to an ASCII terminal:

1. Connect the male 9-pin D-type connector of the CBL-DB9F-DB9M-STR
straight cable available from RAD to the CONTROL DCE.
2. Connect the other connector of the CBL-DB9F-DB9M-STR cable to an ASCII
terminal.
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 supervisory
terminal port.
2.22 Connecting to a Network Management Station

ETX-5 is connected to a network management workstation via a dedicated 8-pin
RJ-45 copper connector on the E5-MC-4 or E5-MC-SFP-P-4 card designated MNG-
ETH.
ETX-5 Connecting to a Network Management Station 2-23


1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
Figure 2-9 MNG-ETH Port on E5-MC-4 Card
 To connect to a network management station:

• Connect ETX-5 to network management station using a standard straight or
cross UTP cable terminated with an RJ-45 connector.
2.23 Connecting to an External Alarm Device

ETX-5 is connected to an external alarm device via the 15-pin D-type connector
on the E5-FAN card. Refer to Appendix A for the connector pinout.
 To connect to an external alarm source:
1. Prepare a cable in accordance with the alarm connector pinout given in
Appendix A.
2. Connect the ALARM port on the E5-FAN card to an external alarm device,
such as a buzzer, using a prepared cable.
RAD
ETX-5300A
ALARM CRITICAL
MAJOR
MINOR
TEST
LED
FAN
OK
FLT
F MAIN-B PS-B
I
L MAIN-A PS-A F
T A
I/O 2 I/O 4 N
E
R I/O 1 I/O 3 E5-FAN
Figure 2-9 ALARM Port on E5-FAN Card
2.24 Labeling Cables

Keep your data and power cables organized and clearly labeled according to the
cable management system adopted by your company. RAD recommends adhering
to the relevant EIA standards when designing you inter-building power
distribution and telecommunication network.
2-24 Labeling Cables ETX-5

Chapter 3
Operation and
Maintenance
This chapter provides general operating instructions and preliminary configuration
instructions for ETX-5 units.
3.1 Turning On the Unit

When turning on the ETX-5, it is useful to monitor the power-up sequence.
 To turn on ETX-5:
Caution
ETX-5 does not have a power on/off switch, and will start operating as soon as
power is applied.
For an ETX-5 equipped with AC-powered power supply modules, be sure to
simultaneously connect the power to all the installed PS modules, for example, by
means of a common circuit breaker or an ON/OFF switch.
1. Connect the ETX-5 to power (see detailed instructions in Chapter 2). The PWR
indicators on all the E5-PIM PS modules that are powered light up, and remain
lit as long as the ETX-5 is powered.
You may also hear the fans in the ETX-5 fan tray start operating.
2. Wait for the completion of the power-up initialization process (this takes
about one minute). During this interval, monitor the power-up indications:
 After power is applied, all the ETX-5 indicators turn on for a few seconds.
This allows you to check that the equipment indicators are functioning
properly.
 After a few seconds, all the indicators turn off (except for the E5-PIM
PWR indicators as ETX-5 performs its power-up initialization.
3. After the power-up initialization ends, all the PWR indicators and the PRI
indicator of the active main card are lit steadily; the PRI indicator for the
standby main card starts blinking.
ETX-5 performs the startup procedure. See the Startup section below.
4. After startup ends, you may log in, using the supervision terminal.
ETX-5 Turning On the Unit 3-1

Chapter 3 Operation Installation and Operation Manual
3.2 Indicators
The unit's LEDs are located on the system and I/O modules. Table 3-1 lists the
functions of the ETX-5 LED indicators.
Table 3-1. ETX-5 LEDs
Name Color Function Location
PWR Green ON – Power inlet module is providing power to chassis E5-PIM

OFF – No power is applied to the inlet module
FLT Red ON – Card hardware, software or power failure has been E5-PIM, E5-FAN,
detected E5-MC-4,
OFF – No hardware, software or power fault has been E5-MC-SFP-P-4,
detected E5-10GBE-2,
E5-GBE-20,
E5-cTDM-4
E5-cTDM-STM4
OK Green ON – E5-FAN receives power and all fans are operational E5-FAN
CRITICAL Red ON –Critical alarm has been detected E5-FAN
MAJOR Orange ON –Major alarm has been detected E5-FAN
MINOR Yellow ON –Minor alarm has been detected E5-FAN
TEST Yellow ON – Diagnostic test is in progress E5-FAN
RMV Blue Blinks – Power-up is in progress E5-MC-4, ,

ON – Card can be safely extracted from chassis, after it E5-MC-SFP-P-4,
has been administratively shut down E5-10GBE-2,
E5-GBE-20,
OFF – Hardware, software or power failure
E5-cTDM-4
E5-cTDM-STM4
PRI Green ON – Main card is primary E5-MC-4,

Blinking – Main card is secondary E5-MC-SFP-P-4,
CLK Red ON – Station clock is configured, but is not synchronized E5-MC-4,

OFF – Station clock is not configured, or station clock is E5-MC-SFP-P-4,
configured and synchronized
LINK Green ON – Ethernet interface has been connected E5-MC-4, ,

E5-MC-SFP-P-4,
E5-10GBE-2,
E5-GBE-20
ACT Yellow ON – Data is being transmitted/received at the Ethernet E5-MC-4, ,

interface E5-MC-SFP-P-4,
E5-10GBE-2,
E5-GBE-20
ON LINE Green ON – Card is administratively enabled E5-cTDM-4

E5-cTDM-STM4
3-2 Indicators ETX-5

Installation and Operation Manual Chapter 3 Operation
Name Color Function Location
LOS Red ON – Loss of signal has been detected E5-cTDM-4

Blinking – Other signal failure (LOF, AIS, RFI etc) has been E5-cTDM-STM4
detected
3.3 Startup
Configuration and Application Software Files

The following are system files that contain configuration settings or application
software:
• factory-default – Contains the factory default settings
• running-config – Contains full configuration (default and user).
• startup-config – Contains the saved user configuration. You must save the
file startup-config; it is not automatically created.
• user-default-config – Contains the default user configuration.
• rollback-config –Contains configuration settings to be used if the user
confirmation of loading startup-config file has not been received. See
Confirming the Configuration File.
• restore-point-config – Contains the configuration saved during software
installation. System configuration can be restored from this file, if the
installation process fails.
• sw-pack-1, sw-pack-2, sw-pack-3, sw-pack-4 – Contain up to four software
images.
Refer to Chapter 10 for details on file operations.
Note Configuration files should contain only printable ASCII characters (0x20–0x7E),
<Enter> (0x0D), <Line Feed> (0x0A), and <Tab> (0x09).
Note It is recommended to use only 3 sw-pack files (and not 4). When the device is
configured to full scale and 4 sw-pack files are in use – there may not be enough
free space on the disk. In such a case, it is recommended to delete one of the
unused sw-pack files.
Caution Always wait until all main cards installed in the chassis are up and running before
executing any file operation commands.
Note The save command is used to save the user configuration. Some commands that
reset the device also erase the saved user configuration by copying another file
to it before the reset.
ETX-5 Startup 3-3

Figure 3-1. Commands That Reset Device/Copy Configuration Files
Loading Sequence
At startup, the device boots from the startup-config file, the user-default file, or
the factory-default file, in the sequence shown in Figure 3-2 . If none of these
files exist, the device boots using hard-coded defaults.
Start
Boot from Pass Sanity Yes

Startup-config exist?
Startup-config Check
Fail
No
Boot from Pass Sanity Yes User-default-config

User-default-config Check exist?
Fail No
Boot from
Factory-default-config
End
Figure 3-2. Loading Sequence
3-4 Startup ETX-5

3.4 Working with Custom Configuration Files

In large deployments, a central network administrator often sends configuration
scripts to the remote locations, and the local technician only needs to replace the
IP address in the script or make other small changes (using any text editor), and
then download the file to the device.
To download the configuration file, use the copy command, as explained in
Chapter 10. Normally, user-default-config contains a configuration common to all
of the provider’s devices of the same type, while startup-config contains a
device-specific configuration, based on user-default-config.
After downloading the configuration file, the unit must be reset in order to
execute the file. After the unit completes its startup, the custom configuration is
complete.
Zero Touch
The Zero Touch feature allows ETX-5 to receive software and configuration files
automatically, eliminating the need to manually log into ETX-5 in order to transfer
the required files to it.
You can specify that ETX-5 sends a trap periodically to the management system
to notify it of its existence in the network (by default, this trap is not sent).
 To enable sending the trap:

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

You can 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. Figure 3-1 indicates the
commands that copy to startup-config, and whether the device resets after
copying.
ETX-5 Working with Custom Configuration Files 3-5

Figure 3-3. Commands That Reset Device/Copy Configuration Files
Confirming the Configuration File

ETX-5 allows you to enable active confirmation of the startup-config file after
reboot. The startup-config confirmation prevents loss of the management link to
a remote device due to an erroneous configuration.
If confirmation of the startup configuration file is enabled, you must confirm the
startup-config within a defined period of time. On issuing the startup-confirm-
required command, ETX-5 copies running-config or any other user-specified
configuration file to rollback-config. If the new startup-config is not confirmed,
rollback-config is ready to be loaded.
The startup-config-confirm command is used to confirm startup-config.
 To enable startup-config confirmation:

• In the admin# prompt, enter the startup-confirm-required command
according to the table below.
Task Command Comments
Enabling or disabling startup-confirm-required [time-to- Default time-to-confirm –

confirmation of configuration confirm <1–65535>] [rollback {startup- 5 min.
file after reboot config | user-default-config | factory- You can define any
default-config | running-config}] configuration file to be a
no startup-confirm-required source for your rollback-config
file.
The default option is running-
default, which is guaranteed to
maintain management
connectivity, as it is the
configuration currently run by
the user.
no before startup-confirm-
required cancels the previously
enabled startup-config
confirmation.
3-6 Working with Custom Configuration Files ETX-5

Handling Configuration File Errors

By default, ETX-5 executes commands in configuration files or scripts one by one
and skips any invalid command. You can change this behavior and require
execution to stop upon error, or reject the file with a subsequent device reboot.
 To configure handling errors in configuration file:

• Enter on-configuration-error {ignore | stop | reject} into the configuration file
to select the required mode.
3.5 Turning Off the Unit

 To power off the unit:
• Remove the power cord from the power source.
ETX-5 Turning Off the Unit 3-7

3-8 Turning Off the Unit ETX-5

Chapter 4
Management and Security
This chapter provides general operating instructions and preliminary configuration
instructions for ETX-5 units.
This chapter presents information about the following topicsn:
• Management Access
• Access Policy
• Access Control List (ACL)
• Authentication via RADIUS Server
• Authentication via TACACS+ Server
• CLI-based Configuration
• Default IP
• GUI-based Configuration
• IPv6 for Management
• OAM CFM and OAM EFM
• Terminal Control Port
• Services for Management Traffic
• SNMP Management
• Syslog
• Telnet Client
• Terminal Control Port
• Show tech-support Command
• User Access
The table below summarizes management alternatives for ETX-5.
ETX-5 1BManagement Access 4-1

Chapter 4 Management and Security Installation and Operation Manual
Table 4-1. Management Alternatives
Manager Management
Method Port Transport Method Comments
Location Protocol
Terminal emulation
Running CLI commands &
applications such as
scripts from prompt
HyperTerminal, Procomm,
CONTROL Local Out-of-band RS-232
Putty, SecureCRT, Tera Term
(see Working with Terminal
below)
MNG-ETH Local, remote Out-of-band Terminal emulation

FE, GbE, Telnet, SSH application (see Working with
Local, remote Inband Telnet and SSH below)
10GbE
config file via CLI
Downloading a
CONTROL Local Out-of-band Full or partial device

configuration by dowloading
MNG-ETH Local, remote Out-of-band
SFTP/TFTP configuration file. See Using
FE, GbE, a Custom Configuration File
Local, remote Inband in Chapter 3.
10GbE
Method Port Manager Transport Management Comments

Location Method Protocol
RADview (see Working with

RV Shelf View or
other NMS GUI
MNG-ETH Local, remote Out-of-band RADview below)

Third-party NMS (see
SNMP
Working with Third-Party
FE, GbE,
Local, remote Inband Network Management
10GbE
Systems below)
Downloading a config
file via RV Jobs
MNG-ETH Local, remote Out-of-band Full or partial device

configuration by dowloading
SFTP/TFTP configuration file. See Using
a Custom Configuration File
FE, GbE,
Local, remote Inband in Chapter 3.
10GbE
Note
By default, terminal, Telnet (SSH) and SNMP management access methods are
enabled.
4.1 Management Access
You can enable or disable access to the ETX-5 management system via Telnet,
SSH, or SNMP applications. By disabling Telnet, SSH, or SNMP, you prevent
unauthorized access to the system when security of the ETX-5 IP address has
been compromised. When Telnet, SSH, and SNMP are disabled, ETX-5 can be
4-2 1BManagement Access ETX-5

Installation and Operation Manual Chapter 4 Management and Security
managed via an ASCII terminal only. In addition, you can limit SFTP and TFTP
operation.
Factory Defaults
By default, access is enabled via Telnet, SSH, and SNMP.
Configuring Management Access

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

no telnet
Allowing SSH (Secure Shell) access ssh no ssh blocks access by SSH
no ssh
Allowing SNMP access snmp no snmp blocks access by SNMP

no snmp
Allowing SFTP operation sftp no sftp blocks SFTP operation

no sftp
Allowing TFTP operation tftp no tftp blocks TFTP operation

no tftp Use TFTP for transferring small files, such as
configuration files.
4.2 Management Access Methods

This section describes two methods used to access the ETX-5 management host
via Layer 2 or Layer 3 networks.
Layer 2 Management Access

Figure 4-1 illustrates a typical Layer-2 management scheme. Network
management station (NMS), ETX-5 and remote ETX-2xxA devices share the same
Layer-2 broadcast domain (VLAN X) and Layer-2 forwarding entity (bridge) is
used for access.
ETX-5 and remote ETX-2xxA devices can be managed using:
• Out-of-band traffic via a dedicated Ethernet management port, or
• Inband traffic via a 10GbE port.
The ETX-5 host is an IP address of a router interface, connected to a bridge port.
ETX-5 2BManagement Access Methods 4-3

ETX-5
LB IP
Router
RIF
SVI
ETX-2 NMS
SVI
Management SVI BP SVI Management
Network Network
VLAN X VLAN X
VLAN X VLAN X
User BP BP OOB Out-of-Band
VLAN X VLAN X Access
Bridge
PSN VLAN X VLAN X PSN
VLAN X VLAN X
User BP BP NET Inband
VLAN X VLAN X Access
SVI SVI
ETX-2 NMS
Figure 4-1. Layer-2 Management Access
Layer 3 Management Access

The figure below illustrates a typical Layer-3 management scheme. ETX-5 and
remote ETX-2xxA devices are managed using one of the following:
• Out-of-band traffic via a dedicated Ethernet management port
• Inband traffic via a 10GbE port
4-4 2BManagement Access Methods ETX-5

ETX-5
ETX-2 NMS
SVI SVI
Layer-3 PSN User RIF 4 RIF 1 OOB Layer-3 PSN
Out-of-Band
Access
Router
SVI SVI
Layer-3 PSN Layer-3 PSN
User RIF 3 RIF 2 NET
Inband
Access
ETX-2 LB IP NMS
Figure 4-2. Layer-3 Management Access
The ETX-5 host can be accessed by defining IP address and enabling management
on any of the internal router interfaces (RIFs), including virtual loopback (LB) IP
addresses.
By default, ETX-5 has RIF 1 connected to an out-of-band Ethernet management
port via ingress and egress untagged flows (see the figure below).
To enable remote management, it is necessary to:
• Define IP address of RIF 1
• Enable management access for RIF 1
• Enable RIF 1.
ETX-5
SVI
Router RIF 1 OOB
Figure 4-3. Default Management Access via Out-Of-Band Ethernet Port
Note Management is disabled for loopback RIFs, which are used for TDM pseudowire or
Precision Time Protocol (IEEE 1588v2) traffic.
ETX-5 2BManagement Access Methods 4-5

4.3 CLI-Based Configuration
Working with Terminal

ETX-5 includes a V.24/RS-232 asynchronous DCE port, designated CONTROL DCE
and terminated in a 9-pin D-type female connector on E4-MC-4 and E5-MC-SFP-
P-4 cards. The control port continuously monitors the incoming data stream and
immediately responds to any input string received through this port.
The ETX-5 control port can be configured to communicate at the following rates:
9.6, 19.2, 38.4, 57.6 or 115.2 kbps.
 To start a terminal control session:

1. Make sure all ETX-5 cables and connectors are properly connected.
2. Turn on the control terminal or start the PC terminal emulation program to
create a new terminal connection.
3. 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.
4. Set the terminal input delay between characters to at least 10 msec.
5. Power-up the unit.
6. ETX-5 boots up. When the startup process is completed, you are prompted to
press <ENTER> to receive the login prompt.
7. Press <ENTER> until you receive the login prompt.
8. To log in, enter your user name (su for full configuration and monitoring
access) and your password.
9. The device prompt appears:
ETX-5#
You can now type the necessary CLI commands.
Note RAD recommends using the 115.2 kbps data rate for CLI management sessions.
10. Navigate to config>terminal# prompt and change the default terminal baud
rate (9.6 kbps) to 115.2 kbps.
11. Configure the PC communication port parameters to a baud rate of
115.2 kbps to match the new ETX-5300A settings.
12. Continue with product configuration.
Working with Telnet and SSH

Typically, the Telnet host is a PC or a Unix station with the appropriate suite of
TCP/IP protocols.
To enable a Telnet host to communicate, it is necessary to configure the IP
address of router interface 1, which is connected via default ingress and egress
flows to out-of-band Ethernet management port. After this preliminary
4-6 3BCLI-Based Configuration ETX-5

configuration, you can use a Telnet host connected to it directly or via a local
area network.
 To configure router interface 1 for management:

Define IP address of RIF 1
1. Enable management access for RIF 1
2. Enable RIF 1.
ETX-5#
ETX-5# configure
ETX-5>config# router 1
ETX-5>config>router(1)# interface 1
ETX-5>config>router(1)interface(1)# address 1.1.1.1/1
ETX-5>config>router(1)interface(1)# management-access allow-all
ETX-5>config>router(1)interface(1)# no shutdown
By default, ETX-5 has Telnet and SSH access enabled.
Login
To prevent unauthorized modification of the operating parameters, ETX-5
supports four 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 default users cannot be deleted, but can be disabled (shut down). 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.
 To enter as a superuser:
1. Enter su for user name.
2. Enter 1234 for password.
 To enter as an operator:
3. Enter oper for user name.
 To enter as a technician:
1. Enter tech for user name.
 To enter as a user:
1. Enter user for user name.
ETX-5 3BCLI-Based Configuration 4-7

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 ETX-5). 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 ETX-5 by default (the
device name can be configured in the system level; refer to the Device
Information section in this manual). 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>, ETX-5 responds
according to the command entered.
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.
ETX-5# configure system date-and-time date-format yyyy-mm-dd
ETX-5# show configure system system-date
2013-06-10 15:08:20 UTC +00:00
ETX-5#

In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX-5# configure
ETX-5>config# system
ETX-5>config>system# date-and-time
ETX-5>config>system>date-time# date-format yyyy-mm-dd
ETX-5>config>system>date-time# exit
ETX-5>config>system# show system-date
2013-06-10 15:13:23 UTC +00:00
ETX-5>config>system#
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):

1. At the root level, type tree.
ETX-5# tree
|
+---admin
| |
| +---factory-default-all
| |
| +---factory-default
| |
| +---reboot
| |
| +---software
| | |
| | +---install
| | |
| | +---software-confirm-required
| | |
| | +---undo-install
| | |
| | +---show status
| |
| +---startup-confirm-required
more..
1. 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:

2. Navigate to the required context by typing level names separated by a
space and press <Enter>.

3. Type tree detail and press <Enter>.

ETX-5>config# tree detail
configure
|
+---access-control
| |
| +---access-list [ipv4] <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>
4. 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 autocompleteCommand-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
<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>+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 + Administrative commands
configure + Configure device
file + File commands
logon - Logon to debug level
on-configuration-error - Determine the device behavior if
error found in configuration file
Global commands:
copy - Copy file
echo - Display a line of text (command) on the
screen
exec - Execute a file.
exit - Return to the next higher command level
(context)
help - Display information regarding commands
in the current level
history - Display the history of commands issued
since the last restart
info - Display the current device
configuration
level-info - Display the current device
configuration - commands from the
current level only
logout - Log off the device
ping - Ping request to verify reachability of
remote host
[no] popup-suspend - Suspend popup messages
save - Save current settings
schedule - Create schedule
telnet - Open telnet client session
trace-route - Check the path connectivity to a remote
device
tree - Display the command levels from the
current context downwards
Hotkeys:
<Del> -Delete character left of cursor
<Backspace> -Delete character left of cursor
<Tab> -Completion token
<?> -Interactive help token
Left arrow -Move cursor one character to the left
Right arrow -Move cursor one character to the right
Up arrow -History forward
Down arrow -History backward
<Ctrl>+<C> -Interrupt current command
<Ctrl>+<Z> -Return to CLI root
<Ctrl>+<D> -Delete character right of cursor
<Ctrl>+<H> -Delete character left of cursor

<Ctrl>+<U> -Delete text up to cursor

<Ctrl>+<K> -Delete text from cursor to end of line
<Ctrl>+<A> -Move to beginning of line
<Ctrl>+<B> -Move cursor one character left
<Ctrl>+<E> -Move cursor to end of line
<Ctrl>+<L> -Redisplay current line
<Ctrl>+<P> -History forward
<Ctrl>+<S> -Pause transmission (XOFF)
<Ctrl>+<Q> -Resume transmission (XON)
<Ctrl>+<_> -Exit CLI
<Ctrl>+<G> -Return to upper level
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-5 Installation and Operation Manual : http://goo.gl/123456
ETX-5 Shelf View User Manual : http://goo.gl/654321
Command Help
Enter help <command> to display command and parameter information.
ETX-5>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.
ETX-5>file# ?
delete - Deletes a file from the device
dir - Lists all files in the device
show banner-text - Displays banner-text file content

show configuration-files - Displays configuration files properties
show copy - Displays copy status
show factory-default-config - Displays factory-default-config file content
show rollback-config - Displays rollback-config file content
show running-config - Displays running-config file content
show startup-config - Displays startup-config file content
show sw-pack - Displays the existing sw-packs and their content
show user-default-config - Displays user-default-config file content
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, ETX-5 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, ETX-5 creates this entity with the selected name.

• If the command-line entity name can be completed in only one way, when
you press <Tab>, ETX-5 autocompletes the entire name and appends a space.
• If the command-line entity name can be completed in more than one way,
ETX-5 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.
The following tables show examples of string completion.
Table 4-2. String Completion
Level String Result After Pressing <Tab> Possibilities for Completion
file show c show co show configuration-files

show copy
file show con show configuration-files<space> show configuration-files
config>flows class classifier-profile<space> classifier-profile
config>sys name name name
config mgm mgm No possibilities
Table 4-3. 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 ETX-5 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.
ETX-5>config>flows# classifier-profile myclass m?
match-any
ETX-5>config>flows# classifier-profile myclass m
ETX-5>admin# fact?
factory-default-all - Resets all configuration and counter
factory-default - Loads factory default configuration
ETX-5>admin# fact
ETX-5>admin# factory-default?
factory-default-all - Resets all configuration and counters
<CR>
ETX-5>admin# factory-default
When a string cannot be completed, ETX-5 displays “cli error: Invalid Command”.
ETX-5>admin# stac?
# cli error: Invalid Command
ETX-5>admin# stac
ETX-5>file# da ?
# cli error: Invalid Command
ETX-5>file# da
Typing <?> after a space between a command or level name and the ? tells ETX-5
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.
ETX-5>admin# factory?
factory-default-all - Resets all configuration and counters

factory-default - Loads factory default configuration
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.

ETX-5>admin# factory ?
# cli error: Ambiguous Command
ETX-5>admin# factory
A string that is a complete command name followed by a space ? displays all
possible command parameters.
ETX-5>config>flows# show ?
summary - Displays list of flows
ETX-5>config>flows# show
ETX-5>config>flows# classifier-profile ?
<classification-n*> : [1..32 chars]
ETX-5>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>.
ETX-5>config>access-control# resequence access-list acl_1 ?
<CR>
<number> : [0..100000]
The next example shows a complete command that has no parameters.
ETX-5>config>flows# classifier-profile myclass match-any ?
<CR>
ETX-5>config>flows# classifier-profile myclass match-any
Refreshing Output
You can specify that ETX-5 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).
ETX-5 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 ETX-5
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.
ETX-5# configure port eth 1/1

ETX-5>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
ETX-5>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>
I.e., add a pipe, one of the following keywords and a 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.
ETX-5>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 place
holders 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 4-4 describes filter metacharacters.
Table 4-4. 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 4-5. 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 Entitites
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.
ETX-5# configure flows flow flow1

ETX-5>config>flows>flow(flow1)$ ingress-port ethernet 0/3
ETX-5>config>flows>flow(flow1)$ egress-port ethernet 1/1 queue 1 block 0/1
ETX-5>config>flows>flow(flow1)$ classifier Classifier1
ETX-5>config>flows>flow(flow1)$ no shutdown
ETX-5>config>flows>flow(flow1)$exit
ETX-5>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 ETX-5 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 chapter.

In order to execute a CLI script, you have to copy/paste it to the CLI terminal, or
send it to ETX-5 via the RADview Jobs mechanism, CLI script option.
Reconfiguring ETX-5 for SNMP Management
4.4 Access Policy

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

 To define the access policy:
• In the config>mngmnt>access# prompt, enter the necessary commands
according to the tasks listed below.
Specifying authentication method auth-policy 1st-level radius [2nd-level ETX-5 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 ETX-5 attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then ETX-5
attempts to authenticate according to
3rd-level:
• local – ETX-5 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, ETX-5 ends the
authentication process and does not
attempt authentication at the next level.
4-20 4BAccess Policy ETX-5

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 ETX-5
authenticates via the local database. .If the
TACACS server rejects the authentication
request, ETX-5 ends the authentication
process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
4.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.
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS)
RFC 2618, RADIUS Authentication Client MIB
Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network.
Functional Description
When a login attempt occurs at ETX-5, it submits an authentication request to
the RADIUS server. The RADIUS server checks the database and replies with either
Access Rejected or Access Accepted.
Factory Defaults
By default, no RADIUS servers are defined. When the RADIUS server is first
defined, it is configured as shown below.
Parameter Default Value
address 0.0.0.0
retry 2
ETX-5 5BAuthentication via RADIUS Server 4-21

timeout 2
auth-port 1812
Configuring RADIUS Parameters

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

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

request attempts
Defining timeout (in seconds) for timeout <seconds> Range 1–5

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

disables the server
Displaying RADIUS Status

 To display RADIUS status:
• At the config>mngmnt>radius# prompt, enter show status.
RADIUS status appears as shown below.
ETX-5>config>mngmnt>radius# show status
Server IP Address Access Status
----------------------------------------------------------
1. 0.0.0.0 Disable Not connected
4-22 5BAuthentication via RADIUS Server ETX-5


Figure 4-4. RADIUS Status
Displaying RADIUS Statistics

 To display RADIUS statistics:
• In the config>mngmnt>radius# prompt, enter show statistics.
RADIUS statistics appear as shown in the figure below.
 To clear RADIUS statistics:

• In the config>mngmnt>radius# prompt, enter clear-statistics.
ETX-5>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
Timeouts :0 0 0 0
Unknown Types :0 0 0 0
Packets Dropped :0 0 0 0
Figure 4-5. RADIUS Statistics
Table 4-6. RADIUS Statistic Counters
Counter Description
Access Requests Number of Access-Requests packets sent to RADIUS server
Access Retransmits The number of RADIUS Access-Request packets retransmitted to RADIUS

server
Access Accepts Number of Access-Accept packets sent to RADIUS server
Access Rejects Number of Access-Reject packets received from the RADIUS server
Access Challenges Number of Access-Challenge packets sent to RADIUS server
Malformed Response Number of malformed Access-Requests packets received
Bad Authenticators Number of Access-Requests packets with invalid Signature attributes

received
Pending Requests The number of RADIUS Access-Request packets destined for this server
that have not yet timed out or received a response. This counter is
incremented when an Access-Request is sent and decremented due to
receipt of an Access-Accept, Access-Reject or Access-Challenge, a
timeout or retransmission.
ETX-5 5BAuthentication via RADIUS Server 4-23

Counter Description
Timeouts Number of times a server did not respond, and the RADIUS server re-
sent the packet
Unknown Types Number of RADIUS packets of unknown type which were received
Packets Dropped Number of incoming packets silently discarded for some reason other
than malformed, bad authenticators or unknown types
4.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.
Because TACACS+ is based on TCP, implementations are typically resilient against
packet loss.
Standards
RFC 1492, An Access Control Protocol, sometimes called TACACS.
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet but leaves a
standard TACACS+ header.
Factory Defaults
By default, no TACACS+ servers are defined. When the TACACS+ server is first
defined, it is configured as shown below.
retry 1
timeout 5 seconds
authentication-port 49
accounting-port 49
Administrative status shutdown
Accounting group membership None
4-24 6BAuthentication via TACACS+ Server ETX-5

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 AAA model:
• Authentication – The action of determining who a user is.
• 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.
The TACACS+ client can be configured to use authentication/authorization with or
without accounting functionality.
When configuring users on external TACACS+ servers, refer to Table 4-6 to define
authorization levels for ETX-5 standard users.
Table 4-7. 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 user in the

database
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
• The access client is an entity which seeks the services offered by the
network.
• TACACS+ client running on ETX-5, processes the requests from the access
client and pass this data to TACACS+ server for authentication.
• The 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
ETX-5 6BAuthentication via TACACS+ Server 4-25

accounting. TACACS+ supports authentication by using a user name and a fixed

password.
Accounting
ETX-5 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
 Successful logoff
 ETX-5-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 ETX-5
 Any level that was successfully changed in a shell.
Defining TACACS+ Server

ETX-5 provides connectivity to up to five TACACS+ authentication servers. You
must specify the associated server IP address, key, number of retries, etc.
 To define TACACS+ server:

1. If you intend to use TACACS+ for authentication, verify that TACACS+ is
selected as level-1 authentication method (see Access Policy).
2. 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 a new TACACS+ server server <ip-address> no server deletes a TACACS+

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. It is
hashed if specified.
Defining the TCP port to be used for accounting-port Range 1–65535

accounting <tcp-port-number>

Defining the TCP port to be used for authentication-port Range 1–65535

authentication <tcp-port-number>
Binding accounting group to TACACS+ group <string> no group detaches accounting

server group from server
Defining the number of authentication retry <number-of-retries> Permanently set to 1

request attempts
Defining timeout (in seconds) for timeout <seconds> Range 1–10

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

disables the server
Displaying statistics show statistics
Clearing statistics clear-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]
Note You can enter any combination of shell, system, and commands, but you must
enter at least one of them.
3. Type exit to return to the TACACS+ level.

The config>mngmnt>tacacsplus# prompt is displayed.
4. Type server <ip-address> to select the TACACS+ server to which to bind the
group.
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.
Example – Defining Server

The example below illustrates the procedure for defining a TACACS+ server.
• Server IP address: 175.18.172.150
• Key: TAC_server1.

ETX-5# configure management tacacsplus

ETX-5>config>mngmnt>tacacsplus# server 175.18.172.150
ETX-5>config>mngmnt>tacacsplus>server(175.18.172.150)$ key TAC_server1
ETX-5>config>mngmnt>tacacsplus>server(175.18.172.150)$ no shutdown
ETX-5>config>mngmnt>tacacsplus>server(175.18.172.150)$ information 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.
ETX-5# configure management tacacsplus
ETX-5>config>mngmnt>tacacsplus# group TAC1
ETX-5>config>mngmnt>tacacsplus>group(TAC1)$ accounting shell system commands
ETX-5>config>mngmnt>tacacsplus>group(TAC1)$ info detail
accounting shell system commands
ETX-5>config>mngmnt>tacacsplus>group(TAC1)$ exit
ETX-5>config>mngmnt>tacacsplus# server 175.18.172.150
ETX-5>config>mngmnt>tacacsplus>server(175.18.172.150)# group TAC1
ETX-5>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89829AB8AB0FE50885" hash
retry 1
timeout 5
accounting-port 49
group "TAC1"
no shutdown
Displaying Statistics
 To display TACACS+ statistics:
• At the config>mngmnt>tacacsplus>server <ip-address># prompt, type:
show statistics.
The TACACS+ statistic counters are displayed.
ETX-5>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 4-8. 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
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.
Defining Accounting Groups

 To define an accounting group:
1. At the config>mngmnt>tacacsplus# prompt, type group <string> to create an
accounting group.
The config>mngmnt>tacacsplus>group(string)# prompt is displayed.
3. At the config>mngmnt>tacacsplus# prompt, type server ip-address to display
previously defined TACACS+ server.
displayed.
4. At the config>mngmnt>tacacsplus>server(ip-address)# prompt, enter group
<string> to bind a previously defined accounting group to the TACACS+
server.

Creating an accounting group group no group deletes accounting

group
Enabling TACACS+ accounting for the accounting [shell] [system] Accounting can be of any
group [commands] combination
no accounting disables
TACACS+ accounting for the
group
4.7 Access Control List (ACL)

Access control lists are used to flexibly filter and mark incoming and management
traffic.
Applicable Products
This feature is applicable to all ETX-5 products, with the following conditions:
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)
4-30 7BAccess Control List (ACL) ETX-5

• UDP port – UDP/161 (SNMP)

• 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, only inbound direction
is supported.
Only one IPv4 ACL is supported per management entity and direction. An
additional IPv6 ACL may coexist with one IPv4 access list on the same
management entity and direction.
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. The device discards the packets and returns an ICMP Host
Unreachable message.
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 5 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
Note If the video cannot be viewed, make sure that you have the latest version of
Adobe Reader.
ETX-5 7BAccess Control List (ACL) 4-31

Statistics
The device collects ACL statistics per management entity and direction. 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 and direction pair.
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.
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 (such as logging interval and ICMP
Unreachable messages), 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 8-9. 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). The
[<dst-port-range>] [log] [sequence command is repeated three times, each
<sequence-number>] protocol with its relevant arguments.
Management-bound ACLs have the
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) or
udp/161 (SNMP).
• The source port must remain any (i.e.
optional src-port-range field should not
be configured).
• DSCP and IP Precedence are not
supported.
Sequence number range is 1–
2147483648.
log enables logging match events of the
rule into the event log and sending SNMP
traps.

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] The command is repeated three times,
[sequence <sequence-number>] each protocol with its relevant arguments.
Management-bound ACLs have the
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), or
udp/161 (SNMP).
• The source port must remain any (i.e.
optional src-port-range field should not
be configured).
• DSCP and IP Precedence are not
supported.
Sequence number range is 1–
2147483648.
log enables logging match events of the
rule into the event log and sending SNMP
traps.
Adding remarks remark <description> [sequence <sequence- The description contains up to 255
to an ACL number>] characters.
Reseqencing the resequence access-list <acl-name> The value range is 1–100000

rules in an ACL [<value>]
Removing rules delete <sequence-number> The value range is 1–2147483647

from an ACL seconds.
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 4-10. Management-Level Commands
Binding the ACL access-group <acl-name> {in | out} The management entity supports the ACLs
to a no access-group {in | out} 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) or udp/161
(SNMP).
• DSCP, IP precedence or 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
Example
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
Configuration Errors
The table below lists the messages generated by the device when a configuration
error is detected.
Table 4-11. Configuration Error Messages
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 Resequence 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), the
entity that the ACL is bound to and its direction. 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
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 the show access-list statistics
command.
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)
4.8 Default IP
ETX-5 allows local management access using a PC to an ‘out-of-the-box’ ETX-5
over the OOB management port in the factory default configuration. This is an
untagged management access.
Benefits
Default IP allows you to power up a device and connect a local management
console to it out-of-the-box with no configuration necessary.
The IP address of the RI is 169.254.1.1/16. When the PC is using DHCP, access to
ETX-5 is automatically established (the PC address defaults to 169.254.x.y as no
DHCP server according to Microsoft protocol). The configuration includes flows to
and from an SVI Router and a Router interface.
ETX-5 8BDefault IP 4-37

Flows, SVI and RI are assigned with indexes at the high end of the range and
reserved flow names.
• SVI # : 4000
• RI # : 128
• Flows : mng_access_default_in , mng_access_default_out
A ‘no route’ configuration is supported per RI and is configured by default over
this RI. There is no default Gateway configuration.
The factory default configuration is only loaded if there is no startup-config or
user-default-config.
Note If you copy a script and paste it to the terminal after factory-default-config is
loaded, make sure the configuration the pasted script contains does not conflict
with the factory default configuration.
A fresh startup-config can be downloaded to replace the factory-default by

performing a reset.
Remote access can be enables by adding an additional IP address over the default
RI. In this case, the local IP address 169.254.1.1/16 can be deleted remotely.
• Shall not be backward compatible to
 user scripts configuring OOB port
 Under user responsibility to delete that.
4.9 GUI-Based Configuration

ETX-5 can be managed by any SNMP-based network management station. For
example, in the RADview family of network management stations, provided IP
communication is possible with the management station, as well as with the
standalone RADview stations.
To manage the ETX-5 from a remote NMS, it is necessary to preconfigure the
basic parameters using a supervision terminal connected to the ETX-5 CONTROL
DCE port. RAD recommends Layer-3 management access via out-of-band
Ethernet management port.
 To preconfigure ETX-5 for Layer-3 management access:

1. Add a router-type SVI.
2. Create classifier profiles for match all and untagged traffic
3. Add two flows (incoming and outgoing) connecting 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.
5. Configure SNMPv3 parameters:
 OID tree visibility, mask and type
4-38 9BGUI-Based Configuration ETX-5

 Access group
 Trap report policy.
Script below provides all necessary configuration steps. Replace IP addresses and
entity names with values relevant for your network environment.
#*******************************Adding_SVI***********************************
exit all
#**********************************End***************************************
#***************************Adding Classifier_Profiles***********************
match all
exit all

match untagged
exit all
#*********************************End****************************************
config flows flow mng_in
classifier classutg
egress-port svi 99
no shutdown
exit all
config flows flow mng_out
classifier classall
ingress-port svi 99
no shutdown
exit all
#**********************************End***************************************
#*********************Configuring_Router_Interface***************************
address 172.18.219.116/24
bind svi 99
no shutdown
exit
exit all
#**********************************End***************************************
#*********************Configuring_SNMP_View/Mask/Type************************
view internet 1
mask 1
type included
no shut
exit all
#**********************************End***************************************
ETX-5 9BGUI-Based Configuration 4-39

#*********************Configuring_SNMP_Access_Group************************
access-group initial usm no-auth-no-priv
context-match prefix
exit all
#**********************************End***************************************
#**************************Configring_SNMP_Traps*****************************
target-params p
message-processing-model snmpv3
version usm
security name initial level no-auth-no-priv
no shutdown
exit
target a
target-params p
tag-list unmasked
address udp-domain 172.17.176.35
no shutdown
exit
notify unmasked
tag unmasked
no shutdown
exit all
#**********************************End************************************
Working with RADview

RADview is a user-friendly and powerful SNMP-based element management
system, used for planning, provisioning and managing heterogeneous networks.
RADview provides a dedicated graphical user interface (GUI) for monitoring RAD
products via their SNMP agents. RADview for ETX-5 is bundled in the RADview
package for PC (Windows-based) or Unix.
For more details about this network management software, and for detailed
instructions on how to install, set up, and use RADview, contact your local RAD
partner or refer to the RADview User's Manual at the RAD website.
Performance Management
ETX-5 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 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.
The PM data is useful for analyzing ETX-5 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 maintenance is configured for specific entities. PM statistics
are maintained and collected for the following types of entities:
• Ethernet ports

• Flows
• OAM CFM services
• OAM CFM destination NEs.
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.
In order to conserve resources, by default ETX-5 does not maintain PM statistics

for all Ethernet ports and flows. In order for PM statistics for Ethernet ports and
flows to be sent to the RADview PM portal, you have to enable statistics
maintenance in addition to statistics collection for the specific entity. If you
enable only statistics collection for the entity, there are no statistics available for
collection. If you enable only statistics maintenance for the entity, ETX-5
maintains PM statistics that can be viewed via SNMP or CLI, but the statistics are
not collected for retrieval by RADview.
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 maintenance (if applicable) and 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-5 collects
the PM statistics starting with the interval that has the highest frequency, and
ending with the interval that has the lowest frequency. If ETX-5 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-5 collects the higher
frequency interval statistics and then resumes collecting the lower frequency
interval statistics. The PM data is retrieved from ETX-5 by RADview via TFTP or
SFTP. After PM data is retrieved, ETX-5 deletes the file and opens a new one
for further data.
The factory defaults are as follows:
Command Level under config Default Remarks
pm reporting pm PM statistics collection in device

is globally enabled by default

Command Level under config Default Remarks
pm-collection eth reporting Disabled PM statistics collection for

Ethernet ports is not explicitly
configured by default,
therefore is disabled
pm-collection flow reporting Disabled PM statistics collection for

flows is not explicitly configured
by default, therefore is disabled
pm-collection reporting Disabled PM statistics collection for OAM

dest-ne CFM destination NEs is not
explicitly configured by default,
therefore is disabled
pm-collection Specific entity level Disabled PM statistics collection for

specific entities is not explicitly
configured by default;
therefore is disabled until
statistics collection is enabled
for the entity type or entity,
and statistics maintenance is
enabled for the entity
pm-enable Specific entity level no pm-enable PM statistics maintenance for

specific entities is disabled by
default
PM statistics collection is configured for the entire device via the pm command,
and for entity types via the pm-collection command, in the reporting level. For
specific entities, PM statistics collection is configured via pm-collection and PM
statistics maintenance is configured via pm-enable, in the specific entity level.
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. 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.
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
Globally enabling PM reporting pm Type no pm to disable all

statistics collection for PM statistics collection in
device ETX-5
Enabling PM statistics reporting pm-collection eth Type no pm-collection eth

collection for Ethernet interval <seconds> to disable PM statistics
ports collection for Ethernet
ports

Task Level under config Command Comments
Enabling PM statistics reporting pm-collection flow Type no pm-collection flow

collection for flows interval <seconds> to disable PM statistics
collection for flows
Enabling PM statistics reporting pm-collection dest-ne Type no pm-collection

collection for OAM CFM interval <seconds> dest-ne to disable PM
destination NEs statistics collection for all
OAM CFM destination NEs
Enabling PM statistics port > pm-collection interval Type no pm-collection to

collection for a specific ethernet(<slot>/<port-num>) <seconds> disable PM statistics
Ethernet port (other collection for the Ethernet
than the management port
port)
Enabling PM statistics port > pm-enable Type no pm- enable to

maintenance for a ethernet(<slot>/<port-num>) disable PM maintenance
specific Ethernet port collection for the Ethernet
(other than the port
management port)
Enabling PM statistics port > mng-eth pm-collection interval Type no pm-collection to

collection for the <seconds> disable PM statistics
Ethernet management collection for the Ethernet
port and defining management port
interval
Enabling PM statistics port > mng-eth pm-enable Type no pm-enable to

collection for the disable PM statistics
Ethernet management collection for the Ethernet
port management port
Enabling PM statistics flows > flow(<flow-name>) pm-collection interval Type no pm-collection to

collection for a specific <seconds> disable PM statistics
flow and defining collection for the flow
interval
Enabling PM statistics flows > flow(<flow-name>) pm-enable Type no pm-enable to

collection for a specific disable PM statistics
flow collection for the flow
Enabling PM statistics oam > cfm > md(<mdid>) > pm-collection interval Type no pm-collection to
collection for a specific ma(<maid>) > mep(<mepid>) <seconds> disable PM statistics
OAM CFM service and > service(<serviceid>) collection for the service
defining interval
Enabling PM statistics oam > cfm > md(<mdid>) > pm-collection interval Type no pm-collection to
collection for a specific ma(<maid>) > mep(<mepid>) <seconds> disable PM statistics
OAM CFM destination > service(<serviceid>) > collection for the
NE and defining interval dest-ne(<dest-ne-index>) destination NE

Note PM statistics are collected for entities for which PM statistics collection is
specifically enabled in the entity level via pm-collection and statistics
maintenance (if applicable) is enabled via pm-enable, 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:
1. Navigate to configure reporting.
2. Enter info detail | include pm to view PM-related commands in the
configuration.
 To view the performance management configuration for specific entities:

3. Navigate to the specific entity level.
4. Enter info detail | include pm to view PM-related commands in the
configuration.
Examples
 To enable PM for all relevant entities in ETX-5:

• 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 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 maintenance enabled for flow10
• PM statistics collection for Ethernet port 0/3 configured to every minute, and
PM statistics maintenance enabled
• PM statistics collection enabled for OAM CFM dest NEs, every 15 minutes.

Note In this example, PM statistics are collected only for flow10 and Ethernet port 3.
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 dest NEs, collection interval=15 min
exit all
#**** Create flow10 and enable statistics maintenance

configure flows
classifier-profile v10 match-any
match vlan 10
exit
flow flow10
ingress-port ethernet 1/1
egress-port ethernet 0/3 queue 0 block 0/1
classifier v10
pm-enable
no shutdown
#**** Configure PM statistics collection interval for Eth port 0/3, to 1 min
configure port ethernet 0/3
pm-collection interval 60
pm-enable
exit all
save
 To display PM configuration from above example:

ETX-5# configure reporting
ETX-5>config>reporting# info detail | include pm
pm
ETX-5>config>reporting# exit all
ETX-5# configure flows flow flow10

ETX-5>config>flows>flow(flow10)# info detail | include pm
pm-enable
ETX-5>config>flows>flow(flow10)# exit all
ETX-5# configure port ethernet 0/3

ETX-5>config>port>eth(0/3)# info detail | include pm
pm-enable
pm-collection interval 60

The table below lists the messages displayed by ETX-5 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
PM Flow Scale
Statistics Scaling
Main card flows statistics:
• Device level Configuration of flow PM scale.
 Small PM scale of 2000 flows or flow pairs (Bridge case) , involves per
flow counter set including color aware counters.
 Large PM scale of 4000 flows or flow pairs (Bridge case) , involves per
flow counter set excluding color aware counters
• Changing PM scale configuration involves a device reset
• PM scale change from high scale to low scale is possible if no more than 2000
flows or flow pairs are configured with PM enabled (sanity)
• PM scale change from low scale to high scale is supported with no limitation.
The CLI command to change the PM scale is: config>flows>pm-scale {low | high}
PtP flows and MP flows at bridge port Ingress support the following running and
interval statistics counters (interval statistics are supported only in PM portal
phase 3.0).
Scaling
• Small-scale flow PM mode: Up to 1000 MEPs (EVCs) support PM (LM/DM)
• High-scale flow PM mode: Up to 2000 MEP’s (EVC’s) shall support PM
(LM/DM)
• Up to a total of 2000 PM sessions
Counters
A different set of counters is supported for the two PM scale modes as shown
below.

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 manual) are available via RAD partners.
Working with Third-Party Network Management Systems

ETX-5 can be integrated into third-party management systems at different levels:
• Viewing device inventory and receiving traps (see Chapter 5 for trap list)
• Managing device, including configuration, statistics collection, diagnostics,
using 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).
 RAD private MIB.

4.10 IPv6 for Management

ETX-5 supports management using IPv6.
Benefits
Allows management of devices over IPv6.
ETX-5 supports IPv6 for device management. The ETX-5 router is an internal
Layer-3 interworking device that forwards traffic between its interfaces. Each
router interface is assigned an IP address and can be bound to one of the
following:
• Physical port on Ethernet I/O or main card
 No limit on number of RIF’s per port (up to the RIF shelf limit).
• Bridge port
The router uses service virtual interfaces (SVIs) for connecting 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.
Note 1588 UDP/IP and UDP/IP TDM PW are not supported for IPv6
Each RI supports dual stack forwarding, i.e concurrent IPv4 and IPv6 forwarding.
Each router interface can simultaneously support both IPv4 and IPv6 packets.
Each packet is forwarded per the Routing table according to packet type (IPv4 or
IPv6). Multiple IP addresses (IPv4, IPv6) are supported per Router interface.
Note The section of RFC-4213 related to “Configured tunneling of IPv6 over IPv4” is
not supported.
The IPv6 host supports the following management applications:

• SNMPv3
• Telnet : Shall Not supported
• SSH
• Radius
• Syslog
• Tacacs+
• SNTP
• Ping6
• Trace route6
• DHCPv6 (RFC-3315) – client
4-48 10BIPv6 for Management ETX-5

• TFTP
• SFTP
4.11 OAM CFM

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-5 also
supports performance monitoring per Y.1731.
Standards
IEEE 802.1ag-D8, ITU-T Y.1731
LLDP
MEF 36
Factory Defaults
By default, OAM functionality is disabled.
OAM (Operation, Administration, and Maintenance) describes the monitoring of
network operation by network operators. OAM is a set of functions used by the
user that enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM may trigger
control plane or management plane mechanisms, by activating rerouting or by
raising alarms, for example, but such functions are not part of the OAM itself.
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.
OAM Elements
The Ethernet OAM mechanism monitors connectivity in Maintenance Association
(MA) groups, identified by a Maintenance Association Identifier (MAID). Each
maintenance association consists of two or more maintenance end points (MEP).
Every 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).
• Maintenance Domain (MD) – The network or the 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.
ETX-5 11BOAM CFM 4-49

• 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 PDUs and tracks responses.
• Maintenance Intermediate Points (MIPs) are intermediate entities that are

created in the middle of the domain. Unlike MEPs, MIPs are passive points,
responding only when triggered by CFM trace route and loopback messages.
A MIP consists of two MIP Half Functions (MHFs), uUnlike MEPs, which are
directional entities acting as service termination points. There are two types
of intermediate entities: service-level and MD-level MIPs. These MIP modes
cannot be activated simultaneously:
 Service-level MIPs are defined under the MD level. This type of MIP
inherits its source MAC address from the directly or indirectly attached
physical port. Service-level MIPs respond to link trace messages (LTMs)
and loopback messages (LBMs) whose MD level is equal to the MIP MD
level.
 MD-level MIPs are activated per device per MD level (or several MD levels).
When MD-level MIP mode is activated, ETX5 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. Each MIP inherits its source
MAC address from the adjacent port. MD-level MIPs respond to link trace
messages (LTMs) whose MD level is equal to the MIP MD level.
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 or
router interface.
• MD-level MIPs can be defined only over flows with the classification: Single
VLAN, or outer + inner VLAN.
• MD-level MIPS do not reply to loopback messages (LBMs).
MEPs that are created at the same MD level as the MIPs do not support
multicast loopbacks.
4-50 11BOAM CFM ETX-5

OAM Functions
RAD’s carrier Ethernet aggregation and demarcation devices feature a
comprehensive hardware-based Ethernet OAM and performance monitoring for
SLA assurance:
• 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-2xxA devices serve as a MIPs
• End-to-end OAM session (EVC ME) between two ETX-2xxAs, which serve as
MEPs. ETX-5 devices act as MIPs.
• Segment OAM session (operator service ME) between ETX-2xxA 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 4-6. Multi-Domain Ethernet Service OAM
MEPs and Services

ETX-5 Ethernet main cards support Ethernet OAM functionality and host MEPs as
illustrated in the figure below. A MEP can be either Down or Up, depending on its
position and port association, as explained below.

GbE SAP 10 GbE

MEP
I/O Ethernet Card
10 GbE BP 10 GbE
MEP Bridge BP MEP
10 GbE MEP 10 GbE
Main Ethernet Card
Figure 4-7. Ethernet Main Card MEPs
A MEP is transparent to OAM frames whose MD level is higher than the MEP level,
and drops OAM packets whose MD level is lower than the MEP level. It fully
supports connectivity check (CC), loopback, link trace and PM counters,
Down MEP
Down MEPs reside at port egress and are bound to physical ports. These MEPs
receive and send CFM PDU from and to the network. Down MEPs are supported
for either point-to-point (E-Line) or multipoint (E-LAN) services. Different MEP
locations are illustrated below.
The figure below illustrates a point-to-point service between two main card ports
with the MEP bound to port B. Tx flow in the service is directed to a queue block.
Tx Flow
MEP
Rx Flow
Main Card Main Card
Port A Port B
Figure 4-8. PtP Service with Down MEP Bound to Main Card Port B
The figure below illustrates a point-to-point service between main and I/O card
ports with the MEP bound to port B. Tx flow in the service is directed to a queue
block.

Tx Flow
MEP
SAP
Rx Flow
Main Card I/O Card
Port A Port B
Figure 4-9. PtP Service with Down MEP Bound to I/O Card Port B
ports with MEP bound to port A. Tx flow in the service is directed to a queue
block.
Rx Flow
MEP
SAP
Tx Flow
Main Card I/O Card
Port A Port B
Figure 4-10. PtP Service with Down MEP Bound to Main Card Port A
Figure 8-46 illustrates a point-to-point service between two I/O card ports with
the MEP bound to port B. Tx flow in the service is directed to a queue block.
Tx Flow
SAP
MEP
SAP
Rx Flow
I/O Card I/O Card
Port A Port B
Figure 4-11. PtP Service between Two I/O Card Ports with Down MEP Bound to Port B
The figure below illustrates a multipoint service between main card 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 SVI MEP
Rx Flow
Main Card
Port A
Figure 4-12. Multipoint Service with Down MEP Bound to Main Card 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. If configured over an IO port, the flow from the corresponding
SAP must be used. It also needs a classification profile to specify the
packet tag structure (as it cannot be taken from the flow classification
profile).
• Tx flow to a destination queue to forward OAM frames.
Up MEP
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.
Different E-Line MEP locations are illustrated below.
with the Up MEP bound to port A.
Tx Flow
MEP
Rx Flow
Main Card Main Card
Port A Port B
Figure 4-13. PtP Service with Up MEP Bound to Main Card Port A
The figure below illustrates a point-to-point service between two I/O card ports

Tx Flow
SAP
MEP
SAP
Rx Flow
I/O Card I/O Card
Port A Port B
Figure 4-14. PtP Service between Two I/O Card Ports 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). Different E-LAN Up MEP locations are illustrated below.
The figure below illustrates a multipoint service between I/O card and bridge
ports with the Up MEP bound to the bridge port. Tx flow in this service is directed
to the BP SVI.
Rx Flow
BP Bridge BP SVI MEP SAP
Tx Flow
I/O Card
Port A
Figure 4-15. Multipoint Service with Up MEP Bound to Bridge Port
to the BP SVI.
Rx Flow
Tx Flow
Main Card
Port A
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.
MIPs
Unlike MEP, which is a directional entity acting as a service termination point, MIP
is defined as a bidirectional intermediate entity, consisting of half functions
(MHFs). There are two types of intermediate entities: service-level and MD-level

MIPs. These MIP modes differ in functionality, scale, configuration, and cannot be
activated simultaneously.
Service-Level MIPs
Service-level MIP responds to link trace messages (LTMs) and loopback messages
(LBMs), whose MD level is equal to the MIP MD level. ETX-5 supports up to 256
service-level MIPs.
MIP
LBM/LTM LBM/LTM
Flow X Flow X
LBR/LTR LBR/LTR
MHF MHF
Figure 4-17. Service-Level MIP Functionality
Like MEPs, the MIPs are bound to physical ports (directly- or indirectly-attached),
inheriting the MAC address of the port for LTM purposes. The MIPs have 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 MD level and are characterized by the following:
• The physical port to which they are bound, inheriting the port’s MAC source
address
• Rx flow, originating from the MIP-bound port, which faces MHF 1, and whose
classification profile can be one of the following:
 Untagged
 Single VLAN
• Rx classification, when Rx flow originates from SA with the Match All
classification profile
• Tx flow, originating from the physical port facing MHF 2
• CoS mapping profile
• Optional egress queue for the Tx flow.
The two figures below illustrate service-level MIPs in point-to-point and
multipoint services.

MIP
(bound to port B)
Rx Flow
Tx Flow
Main Card MHF 2 MHF 1 Main Card
Port A Port B
MIP
(bound to port B)
Rx Flow
SAP
Tx Flow
Main Card MHF 2 MHF 1 I/O Card
Port A Port B
Figure 4-18. Service-Level MIPs in Point-to-Point Service
MIP
(bound to port B)
Rx Flow
BP Bridge BP SVI
Tx Flow
MHF 2 MHF 1 Main Card
Port B
Figure 4-19. Service-Level MIP in Multipoint Service
MD-Level MIPs
MD-level MIPs are activated per device per MD level (or several MD levels).
Flows
When MD-level MIP mode is activated, ETX-5 creates a MIP for each flow at each
Ethernet port and bridge port. This includes the flows that already existed in the
system, and the new ones, which are added after device-level MIP creation. The
MIP inherits source MAC address from the adjacent Ethernet port.
MD-level MIPs can be defined over flows with one of the following classification
profiles:
• Single VLAN
• Single outer + single inner VLAN
MD-level MIPs cannot be provisioned over flows connected to router- and
pseudowire-type SVIs.
The two figures below illustrate device-level MIPs over point-to-point and

MIP MIP
(bound to port A) (bound to port B)
Main Card MHF 2 MHF 1 MHF 2 MHF 1 Main Card

Port A Port B
MIP MIP
SAP
Main Card MHF 2 MHF 1 MHF 2 MHF 1 I/O Card

Port A Port B
Figure 4-20. Device-Level MIPs in Point-to-Point Service
MIP
(bound to port A)
SAP BP
MIP
Port A MHF 2 MHF 1 (bound to port C)
MIP
Bridge BP SVI
(bound to port B)
Port C
MHF 2 MHF 1
SAP BP
Port B MHF 2 MHF 1

I/O Card Main Card
Figure 4-21. Device-Level MIPs in Multipoint Service
Measurements
MD-level MIPs respond to link trace messages (LTMs), whose MD level is equal to
the MIP MD level. 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 learned 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 4-22. MD-Level MIP Functionality
Limitations and Exclusions

The following limitations exist, when MD-level MIPs are defined:
• MD-level MIPS do not reply to loopback messages (LBMs)
• MEPs, created at the same MD level as the MIPs, do not support multicast
loopbacks.
• If a MD-level MIP is configured and a MEP with an equal or higher MD level is
• If a MEP with an equal or higher MD level is configured on a flow, a MD-level
MIP cannot be added to the flow.
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 4-23. 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 detailed in
the table below.
Table 4-13. 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

01-80-C2-00-00-3y
1 1
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 table 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
MEP
LTR
Main Card Main Card
Port A Port B
Figure 4-24. MEP with LTM Sent from the Card Port in Point-to-Point Service

In the figure below, the MEP responds with LTR if the target MAC address of the
LTM
LTR Main Card

Port A
Figure 4-25. 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
LTR
MIP
Main Card Main Card
Port A Port B
Figure 4-26. MIP with LTM Sent from the Card 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 learnt at all. If the target MAC address has been learned on another
bridge port, the LTM is discarded.
LTM LTM
BP Bridge BP SVI
LTR
MIP
Main Card
Port A
Figure 4-27. MIP with LTM Sent from the Bridge Port in Multipoint Service
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 SVI
LTR
MIP
Main Card
Port A
Figure 4-28. MIP with LTM Sent from the Card Port in Multipoint Service

Performance Monitoring
ETX-5 Ethernet service OAM PM functionality complies with the Y.1731
requirements. ETX-5 provides per-service loss and delay measurement and event
reporting.
statistic counters enabled (pm-enable).
The following performance parameters are measured by appropriate OAM messages:

• Frame Loss Ratio (FLR) – FLR, expressed as a percentage, is the ratio of the
number of service frames not delivered, divided by the total number of
service frames during a time interval, where the number of service frames not
delivered is the difference between the number of service frames sent to an
ingress UNI and the number of service frames received at an egress UNI.
ETX-5 supports single-ended and proprietary synthetic loss measurement
(LM) with proactive LMM transmission and automatic LM response. OAM MEPs
measure frame loss only if statistic counters have been enabled on the
incoming and outgoing flows. LM is not supported over tunnels. Both single-
ended and synthetic methods can co-exist on the same MEP/service. See
User-Data Loss Measurement and Synthetic Loss Measurement below.
• Frame Delay (FD) – FD is specified as round trip delay for a frame, where FD
is defined as the time elapsed since the start of transmission of the first bit
of the frame by a source node, until the reception of the last bit of the loop
backed frame by the same source node, when the loopback is performed at
the frame’s destination node.
ETX-5 supports dual-ended delay measurement (DM) with proactive DMM
transmission and automatic DM response. Measurement is performed for
delays of up to 1 second with full DM over tunnels.
User-Data Loss Measurement

Single-ended loss measurements are supported on user data in the following
cases:
• For Up and Down MEPs, when the egress flows have their original P-bit
modified via CoS marking profile, assuming the CoS marking profile is
coordinated with the MEP CoS mapping profile (CoS per p-bit for multiCoS
service or fixed CoS for single CoS).
• For Down MEP, when no P-bit change is performed at the exit to the network
(P-bit is copied to S-tag).
• For Up MEP, when no P-bit change is performed at the exit to the network
assuming a 1-to-1 CoS mapping profile is configured on the Tx flow of the Up
MEP and on the MEP itself.
Synthetic Loss Measurement

Synthetic loss measurement is a RAD-proprietary method, which uses standard
LMM/LMR frames for counting DMM and DMR. Synthetic LM is supported over

tunnels. It can be activated even if the MEP flows do not have statistic counters
enabled (no pm-enable). Up to 64 destination NEs are supported by a MEP
service (E-Line and E-L AN). Figure 8-64 details standard Y.1731 counters used in
the synthetic loss measurements.
LMM
TxFcf: Tx DMM+DMR Counter
MEP MEP
From LMR LMR

TxFcf: Copy from LMM TxFcf: Copy from LMM
RxFcf: Rx DMM+DMR Counter RxFcf: Rx DMM+DMR Counter
TxFcb: Tx DMM+DMR Counter TxFcb: Tx DMM+DMR Counter
Local Counter
RxFcl: Rx DMM+DMR Counter
Figure 4-29. Synthetic Loss Measurement Counters
Configuring OAM
Ethernet OAM configuration procedure includes the following steps, detailed in
this section:
Note Before deleting any of the OAM CFM components, verify that it is not used by
other ETX-5 elements, such as ERP.
1. Configure maintenance domains (MDs)

2. Define maintenance associations (MAs)
3. Add maintenance endpoints (MEPs)
4. Add maintenance intermediary points (MIPs)
5. Define endpoint services
6. Add destination network elements (NEs)
7. Configuring counter thresholds.
8. Configure a measurement bin profile.
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.
Note MD name is no name.

 To add a maintenance domain:

• At the config>oam>cfm# prompt, enter maintenance-domain <mdid>
where <mdid> is 1–4096.
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 it has all its MEPs/MIPs deleted or
disabled.
 To configure a maintenance domain:

1. Navigate to configure oam cfm maintenance-domain <mdid> to select the
maintenance domain to configure.
The config>oam>cfm>md(<mdid>)# prompt is displayed
2. Enter all necessary commands according to the tasks listed below.
Configuring maintenance maintenance -association <maid> Refer to Configuring Maintenance

association for the MD no maintenance –association <maid> Associations.
no maintenance –association <maid>
deletes the MA
Specifying the maintenance md-level <md-level> The allowed range for md-level is 0–7
domain level Note: If the pre-standard OAM protocol
is used, the only value allowed for the
maintenance domain level is 3.
Specifying the name of the name string <md-name-string> • Maximum length of MD name string is
maintenance domain no name 43 characters
• Maximum combined length of MD
name and MA name strings is
44 characters
• ETX-5 supports up to 2048 MEPs with
MDs and/or MAs, using name strings
Defining MIPs mip <mip id> Refer to Configuring Maintenance

no mip <mip id> Intermediary Points.
no mip <mip id> deletes the MIP.
Displaying information on show maintenance-association <maid>

configured MAs
Displaying information on show mip <mip id>

configured MIPs

Configuring Maintenance Associations

A maintenance domain contains maintenance associations, for each of which you
can configure the continuity check interval and maintenance endpoints (MEPs).
 To add a maintenance association (MA):
• At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance-association <maid>
where <maid> is 1–4096.
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 it has all its MEPs/MIPs 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 MA name in UINT, name uint <0–65535> • Maximum length of MD name string is
string, or icc format name string <ma-name-string> 43 characters
name icc <ma-name-icc> • Maximum combined length of MD name and

MA name strings is 44 characters
• ETX-5 supports up to 2048 MEPs with MDs
and/or MAs, using name strings
• 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.
ETX-5 supporte up to 2048 MEPs with
MAs using name icc.

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

between continuity check 100ms | 1s | 10s | 1min | 10min}
messages
Configuring MEP for the MA mep <mepid> Refer to Configuring Maintenance Endpoints
Configuring Mainteance Endpoints

Maintenance endpoints reside at the edge of a maintenance domain. They initiate
and respond to CCMs, link trace requests, and loopbacks, in order to detect,
localize, and diagnose connectivity problems. ETX-5 supports up to 4K MEPs and
MIPs.
 To add a maintenance endpoint (MEP):
• At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
mep <mepid>
where <mepid> is 1–4096.
The MEP is created and the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)$ is displayed.
 To delete a maintenance endpoint:

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.
Enabling AIS sending and ais [ interval { 1s | 1min }] To disable AIS sending, enter no ais
defining interval [priority <priority>]
Binding the MEP to an bind ethernet <slot/port> To remove the MEP from an Ethernet port,
Ethernet port, LAG or SVI bind lag <port_number> LAG or SVI, enter no bind
bind svi <port_number>

no bind

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> The allowed range for <priority> is 0–7
CCMs, LBMs and LTMs
transmitted by the MEP
Associating the MEP with a classification profile <profile_name> Classifier profile is needed when the MEP
classifier profile no classification profile Rx flow has the SAP ingress port (in this
case the flow classifier profile is Match
All).
To delete classifier profile assignment,
enter no classification profile.
Defining client MD level client-md-level <md_level> Client MD level is a level for sending
upstream AIS
Associating the MEP with a cos-mapping profile <profile_name> The CoS mapping profile must be
CoS profile no cos-mapping profile P-bit-to-CoS to assign the class of service
to the packets transmitted by the MEP
(CCMs, LBTs etc).
To delete CoS mapping profile assignment,
enter no cos-mapping profile.
Defining the MEP direction direction {up | down}
Assigning unidirectional Rx flow uni-direction rx <rx_flow_name> [tx To delete flow assignment, enter no flow
and Tx flows to the MEP <tx-name>] uni-direction
no flow uni-direction
Activating OAM loopback lbm See Performing OAM Loopback
Activating OAM link trace linktrace See Performing OAM Link Trace
Defining the queue for the queue queue-mapping To delete queue assignment, enter no
MEP <queue_mapping_profile_name> queue queue-mapping
[block <level_id>/<queue_id>]
no queue queue-mapping
Defining remote MEP with remote-mep <remote_mep_id> Allowed range for remote MEP is 1–8191
which the MEP no remote-mep <remote_mep_id> The MEP ID and the remote MEP ID must
communicates be different. You can define up to 512
remote MEPs for the local MEP 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.
To delete remote MEP, enter no
remote-mep <remote_mep_id>
Configuring service for the service <service_id> Refer to Configuring Maintenance

MEP Endpoint Services
Displaying MEP status show status

Displaying remote MEP show remote-mep <remote-mep-id>

status status
Displaying MEP service show service <service_id>

status
Administratively enabling no shutdown To deactivate the MEP, enter shutdown.

MEP When a MEP is no shutdown, its services
are not being activated automatically.
Administratively disabling a shutdown When a MEP is shutdown,its active

MEP services (services that are in no shutdown)
are moved automatically to shutdown as
well. No error or warning message is
displayed.
Configuring Maintenance Intermediary Points
MD-Level MIP
Ethernet port and bridge port. The MIPs are added for each specified MD level, or
MD level range.
 To add a 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.
Using no before the command removes the MIP.
Service-Level MIP
MIPs are bidirectional intermediate entities, consisting half functions (MHFs). MIPs
respond to link trace messages (LTMs) and loopback messages LBMs, whose MD
level is equal to the MIP MD level. ETX-5 supports up to 256 MIPs.
 To add a maintenance intermediate point (MIP):
• At the config>oam>cfm>md(<mdid>)# prompt enter: mip <mipid>
The maintenance intermediary point is created and the
config>oam>cfm>md(<mdid>)>mip(<mipid>)$ prompt is displayed.
 To delete a maintenance intermediary point:

• At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mipid>
The maintenance intermediary point is deleted.
 To configure a maintenance intermediary point:

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

Enter all necessary commands according to the tasks listed below.
Binding the MIP to an bind ethernet <slot/port> To remove the MIP from an Ethernet port,

no bind
and Tx flows to the MIP <tx-name>] uni-direction
Configuring MIP half mhf 1 See table below

functions (MHF) mhf 2
Administratively enabling no shutdown To deactivate the MIP, enter shutdown

MIP
Displaying MIP status show status
The following marking actions can be performed at the mhf level, at the
config>oam>cfm> md(<mdid>)>mip(<mipid>)>mhf(1 or 2)# prompt.
Associating the MHF with a classification profile <profile_name> Classifier profile is needed when the MHF
All).
Associating the MHF with a cos-mapping profile <profile_name> The CoS mapping profile must be
to the packets transmitted by the MHF
(CCMs, LBTs etc).
MHF <queue_mapping_profile_name> queue queue-mapping
Configuring Maintenance Endpoint Services

You can configure up to eight services on a MEP. The service configures
performance monitoring (Y.1731) functionality for loss and delay measurements.
The statistics are disaplyed at the destination NE level.

 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 following prompt is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#
Associating this service with a classification priority-bit <p-bit> The allowed range is 0–7
priority for LMMs and DMMs
Specifying delay threshold in delay-threshold <delay-thresh> The allowed range for delay
microseconds threshold is: 1–5,000,000. If the
threshold is exceeded, the
service is declared as degraded.
Specifying delay variation delay-var-threshold <delay-var-thresh> The allowed range for delay
threshold in microseconds variation threshold is:
1–5,000,000. If the threshold is
exceeded, the service is
declared as degraded.
Specifying the interval for dmm-interval {100ms | 1s | 10s}

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

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

service below. The value range is
1–255. One NE per service is
allowed for user-data LM and up
to 64 NEs for synthetic LM.
To delete a destination NE,
enter no dest-ne.
Selecting loss measurement loss { single-ended} [{synthetic | user- no loss disables loss
method data}] measurement
no loss

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.
Configuring Destination NEs

For performance measurement, the exact address of the destination NE must be
known. You can configure the remote MAC address of the NE, or ETX-5 can learn
it from the CCM messages. You can define a single NE per MEP service.
If the remote MAC address is not configured and needs to be learned,
performance measurement messages are sent with all 0s in the MAC address until
the address is learned.
 To add a destination NE:

• At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service
(<serviceid>)#, enter: dest-ne <dest-ne-index>
where <dest-ne-index> is 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.
Defining the MAC address or remote mac-address <mac>

mep-id of the destination NE
Enabling two-way delay delay two-way

measurement method no delay
Enabling loss measurement loss { single-ended }

method no loss
Defining the delay delay-measurement-bin profile <name>

measurement bin profile to
use as delay bin policy

Defining the delay variation delay-var-measurement-bin profile

measurement bin profile to <name>
use as delay variation bin
policy
Displaying the delay show delay-measurement-bins

measurement bins
Collecting performance pm-collection [interval <1–900>] Statistic collection interval can

monitoring data to be no pm-collection be defined in the 1–900
presented via RADview second range
Performance Management no pm-collection disables
portal statistic data collection
Displaying statistics data show statistics
Configuring a Measurement Bin Profile

The maintenance bin profile aggregates performance monitoring data into
measurement bins. Each bin stores a counter of the results for a user-defined
range of values (in milliseconds). The user creates a measurement bin profile,
containing a range of sample values with a counter of the number of samples
that were received that fall within that range. This measurement bin profile is
attached to a destination NE within a MEP service (see Configuring Destination
NEs). You can configure measurement bins in the range of 0 to 1000 msec.
 To configure a measurement bin profile:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed
2. Enter the measurement profile level: measurement-bin-profile
<profile_name>.
The prompt config>oam>cfm>measurement-bin-prof(<name>)# is
displayed.
3. Define bins by entering their upper levels, separated by commas without
spaces between the values: thresholds <bin_value>,<bin_value>. You can also
enter each value separately.
 To delete the measurement bin profile:

• At the config>oam>cfm# prompt, enter no measurement-bin-profile
<profile_name>.
For example:
 To create profile 1 containing 0–20, 21–40 and 41–100 measurement bins:

ETX-5>config>oam>cfm measurement-bin-profile 1
ETX-5>config>oam>cfm>measurement-bin-prof(1)$ 20,40,100

Displaying OAM Statistics

You can display end-to-end performance monitoring data for the destination NEs.
ETX-5 measures current performance and stores performance data for the last 24
hours (96 intervals).
You can view the following types of statistics for services:
• Running – OAM statistics collected since the service was activated
• Day – OAM statistics for the last 24 hours, or the amount of time since the
service was activated, if less than 24 hours
• Interval – OAM statistics for the current interval or a selected interval. You
can select an interval only if it has already ended.
When a service is first activated, you can view statistics for the current
interval only. 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.
You can view the following types of statistics for destination NEs:
• Running – OAM statistics collected since performance measurement of the NE
started
• Day – OAM statistics for the last 24 hours
• Interval – OAM statistics for the current interval or a selected interval.
 To display the OAM CFM statistics for a destination NE:

1. Navigate to the level corresponding to the destination NE for which you wish
to view the statistics (configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index>).
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>
service(<serviceid>)>dest-ne(<dest-ne-index>)#.
Viewing running statistics show statistics running The statistics are displayed
as listed in Table 8-62
Viewing statistics for the current show statistics current The statistics for the current
interval interval are displayed as
listed in Table 8-62

Viewing the statistics for a show statistics interval <interval-num> Allowed values for
selected interval interval-num: 1–96
The statistics for the
selected interval are
displayed as listed in
Table 8-62
If you specified an interval
that has not yet ended, a
message indicates that the
interval does not exist.
Viewing statistics for current day show statistics current-day The statistics for the current
day, as listed in Table 8-62
Viewing statistics for previous show statistics previous-day The statistics for the
day previous day, as listed in
Table 8-62
Viewing running statistics, show statistics all All available performance

statistics for the current interval, measurement counters, as
statistics for all intervals, and day listed in Table 8-62
statistics
Viewing statistics for all intervals show statistics all-intervals Performance measurement
counters for all available
Intervals, as listed in
Table 8-62
Clearing the statistics for the clear-statistics Running and current

destination NE statistical data for the
service is cleared. Interval
statistics are preserved.
Table 4-14. OAM Statistic Counters
Parameter Description
Far End Tx Frames Total number of OAM frames transmitted from the local MEP to the
remote MEP since the service was activated
Far End Rx Frames Total number of OAM frames received by the remote MEP since the
service was activated
Far End Lost Frames Total number of OAM frames lost from the local MEP to the remote MEP
since the service was activated
Far End Frame Loss Ratio (%) Total number of OAM frames lost from the local MEP to the remote MEP,
divided by the total number of OAM frames transmitted since the service
was activated
Far End Unavailable Seconds Total number of unavailable seconds in the remote MEP since the service
(sec) was activated

Near End Tx Frames Total number of OAM frames transmitted from the remote MEP to the
local MEP since the service was activated
Near End Rx Frames Total number of OAM frames received by the local MEP since the service
was activated
Near End Lost Frames Total number of OAM frames lost from the remote MEP to the local MEP
Near End Frame Loss Ratio (%) Total number of near end lost OAM frames divided by the total number
of near end transmitted OAM frames
Near End Unavailable Seconds Total number of unavailable seconds in the local MEP since the service
(sec) was activated
Average Two Way Delay (msec) Average delay
Frames Above Delay Threshold Number of frames that exceeded the delay threshold
Frames Above Delay Variation Number of frames that exceeded the delay variation threshold
Threshold
Min Two-Way Frame Delay The minimum two-way frame dealy measurement in microseconds
(interval statistics only)
Max Two-Way Frame Delay The maximum two-way frame dealy measurement in microseconds
Average Two Way Delay Var The average (arithmetic mean) two-way FDV measurement in
(mSec) microseconds (interval statistics only)
Min Two-Way Frame Delay The minimum two-way frame dealy variation measurement in
Variation microseconds (interval statistics only)
Max Two-Way Frame Delay The maximum two-way frame dealy variation measurement in
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated
ETX-5>config>oam>cfm>md(1)>ma(1)>mep(205)>service(1)>dest-ne(1)# show
statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Unavailable Seconds : 119 119
Two Way Delay (mSec) : 0.000 mSec

Two Way IFDV (mSec) : 0.000 mSec
Frames Above Delay Threshold : 0
Frames Above IFDV Threshold : 0
Elapsed Time (sec) : 58812

Figure 4-30. OAM CFM Running Statistics

statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Min Average Max

(mSec) (mSec) (mSec)
Two Way Delay : 0.000 mSec 0.000 0.000 mSec
Two Way IFDV : 0.000 mSec 0.000 0.000 mSec


Figure 4-31. OAM CFM Current Statistics
statistics interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Valid Data : Valid
Time Stamp : 2014-07-06 08:45:00.0
Duration (Sec) : 900
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Min Average Max

Figure 4-32. OAM CFM Interval Statistics

Performing OAM Loopback

This diagnostic utility verifies OAM connectivity on Ethernet connections. You can
execute the loopback according to the destination 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 <1–

MAC or mep-id address 50>]
lbm remote-mep <mep-id> [1..8191]
Checking OAM loopback show lbm-results

results
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified by MAC
address.
 To run an OAM link trace:

Specifying remote the MEP by linktrace address <mac-address> The TTL parameter specifies
MAC or mep-id address [ttl <1–64>] the number of hops. Each unit
linktrace remote-mep <mep-id> in the link trace decrements
[1..8191] the TTL until it reaches 0,
which terminates the link trace.
Destnation MAC address LTM
cannot be multicast.
Checking the OAM link trace show linktrace-results

results
Examples
This section illustrates OAM configuration for three MEP instances (two Down
MEPs and one Up MEP).
Example 1. Down MEP between Main Card Ports

This example shows how to create a Down MEP located between two main card
ports and bound to one of them (see the figure below).
 To configure a Down MEP between main card ports:

1. Assign default queue groups to the main card ports.
2. Select classification keys for the main card ports.

3. Enable the main card ports.

4. Configure a VLAN-type classifier profile.
5. Configure two policer profiles.
6. Configure a CoS mapping profile to map user priorities to internal CoS values.
7. Configure two flows from main card port 1 to port 2 and vice versa.
8. Configure measurement bin profiles for the delay and delay variation ranges.
9. Define a Down MEP bound to port 1 with CCM sent over P-bit 0.
10. Configure MEP service with LMMs and DMMs sent over P-bit 1.
11. Configure OAM event reporting thresholds for:
 Delay and delay variation
 Loss ratio
 Unavailability ratio.
CCMs
EVC1_ing
LMMs
MEP PSN MEP
EVC1_eg LMRs DMMs
Main Card B Main Card B DMRs

Remote NE
Port 2 Port 1
Figure 4-33. Down MEP between Main Card Ports
**********************Assigning_Default_Queue_Group_Profiles*********************
config port ethernet main-b/1 queue-group profile q_group_2_level_default
exit all
#*********************************End********************************************
**********************Assigning_Classification_Keys******************************
config port ethernet main-b/1 classification-key vlan p-bit
exit all
#*********************************End********************************************
************************Enabling_Main_Card_Ports*********************************
config port ethernet main-b/1 no shutdown
exit all
#*********************************End********************************************
************************Defining_Classifier_Profile******************************
config flows classifier-profile class20 match-any
match vlan 20
exit all
#*********************************End****************************************
************************Defining_Policer_Profiles********************************
config qos policer-profile "1" bandwidth cir 5000 cbs 10000 eir 0 ebs 0

exit all
#*********************************End********************************************
************************Defining_CoS_Mapping_Profile*****************************
cos-map-profile cos1 classification p-bit
map 0 to-cos 0
map 1 to-cos 1
map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
configure flows flow EVC1_eg
classifier class20
ingress-port ethernet main-b/1
egress-port ethernet main-b/2 queue-map-profile QueueMapDefaultProfile block 0/1
ingress-color profile color1
cos-mapping profile cos1
no shutdown
exit all
configure flows flow EVC1_ing

classifier class20
no shutdown
exit all
#*********************************End********************************************
*********************Defining_Measurement_Bin_Profiles***************************
config oam cfm measurement-bin-profile bin_profile_delay1 thresholds
20,100,300,1000
config oam cfm measurement-bin-profile bin_profile_delay_var1 thresholds
40,200,600,1000
exit all
#*********************************End********************************************
#**************************Defining_MEP_and_MEP_Service**************************
config oam cfm
maintenance-domain 1
md-level 4
maintenance-association 1
name uint 265
mep 1
bind ethernet main-b/1
direction down

flow uni-direction rx EVC1_eg tx EVC1_ing

queue queue-mapping QueueMapDefaultProfile block 0/1
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1
classification priority-bit 1
dest-ne 1
remote mac 00-20-d2-50-1d-28
delay-measurement-bin bin_profile_delay1
delay-var-measurement-bin bin_profile_delay_var1
exit
no shutdown
exit all
#*********************************End********************************************
#*******************Configring_OAM_Reporting_Thresholds**************************
config fault cfm service 1 1 1 1 above-delay frames-report 20 10 60
config fault cfm service 1 1 1 1 above-delay-var frames-report 20 10 60
config fault cfm service 1 1 1 1 far-end-loss-ratio frames-report 1e-6 1e-8

config fault cfm service 1 1 1 1 near-end-loss-ratio frames-report 1e-6 1e-8
config fault cfm service 1 1 1 1 far-end-unavailability-ratio frames-report 10 9

config fault cfm service 1 1 1 1 near-end-unavailability-ratio frames-report 10 9
exit all
#*********************************End********************************************
Example 2. Down MEP between Main and I/O Card Ports

T This example shows how to create a Down MEP located between the I/O and
main card ports and bound to the main card port (see the figure below).
 To configure a Down MEP between main and I/O card ports:

1. Assign default queue groups to the I/O and main card ports, and to SAG 1.
2. Select classification keys for the main and I/O card ports.
3. Enable the main and I/O card ports.
4. Configure classifier profiles:
 VLAN 100 + P-bit 6
 VLAN 300 + inner VLAN 100.
7. Configure the following flows:
 From I/O card port 1 to SAP (classification VLAN 100 + P-bit 6)

 From SAP to main card port 1

 From main card port 1 to I/O card port 1.
 Loss ratio
SAG
SAP
CCMs
ECV2COS1
EVC2_eg LMMs
Port 1 SAP 1 Port 1 PSN MEP
ECV2COS2 MEP LMRs DMMs
EVC2_ing
DMRs
Remote NE
SAP
I/O Ethernet Card Main Ethernet Card
Figure 4-34. Down MEP between Main and I/O Card Ports
config port ethernet 1/1 queue-group profile q_group_2_level_default
config port sag 1/1 queue-group profile q_group_SAG_2_level_default
exit all
#*********************************End********************************************
config port ethernet main-b/1 classification-key vlan inner-vlan p-bit
config port ethernet 1/1 classification-key vlan p-bit
exit all
#*********************************End********************************************
************************Enabling_Main_and_I/O_Card_Ports*************************
config port ethernet 1/1 no shutdown
exit all
#*********************************End********************************************

************************Defining_Classifier_Profiles*****************************
config flows classifier-profile class100pbit6 match-any
match vlan 100 p-bit 6
exit all


match vlan 300 inner-vlan 100
exit all
#*********************************End****************************************
exit all
#*********************************End********************************************
map 0 to-cos 0
map 1 to-cos 1
map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
configure flows flow ECV2COS1
classifier class100pbit6
cos-mapping fixed 0
ingress-color green
egress-port sap 1/1/1 queue-map-profile QueueMapDefaultProfile block 0/1
policer profile 1
no shutdown
exit all
configure flows flow EVC2COS2

cos-mapping fixed 1
ingress-color green
policer profile 2
no shutdown
exit all


classifier match-all
ingress-port sap 1/1/1
vlan-tag push vlan 300 p-bit copy
no shutdown
exit all

classifier class300100
egress-port ethernet 1/1 queue-map-profile QueueMapDefaultProfile block 0/1
vlan-tag pop vlan
no shutdown
exit all
#*********************************End********************************************
20,100,300,1000
40,200,600,1000
exit all
#*********************************End********************************************
config oam cfm
name uint 22
mep 2
direction down
flow uni-direction rx EVC2_ing tx EVC2_eg
ccm-initiate
ccm-priority 0
remote-mep 110
no shutdown
service 1
dest-ne 1
remote mac 00-20-d2-50-2e-55
exit
no shutdown
exit all
#*********************************End********************************************



exit all
#*********************************End********************************************
Example 3. Up MEP between Main Card and Bridge Ports

This example shows how to create an UP MEP located between main card and
bridge ports and bound to the bridge port via SVI (see the figure below).
 To configure an Up MEP between main card and bridge ports:

4. Configure VLAN-based classifier profile
6. Define bridge-type SVIs, bind the bridge ports to the SVIs, and configure the
ports as members of VLAN 20.
7. Configure six flows from the main card ports to the SVIs and vice versa.
9. Define an Up MEP bound to port 1 with CCM sent over P-bit 0.
 Loss ratio

SVI
Flow 1 1
Port 1 MEP BP 1
Flow 2
SVI
Flow 3 2
Port 2 BP 2
Flow 4
SVI
Flow 5 3
Port 3 BP 3
Flow 6
Bridge
Main Ethernet Card
Figure 4-35. Up MEP between Main Card and Bridge Ports
config port ethernet main-a/1 queue-group profRile q_group_2_level_default
config port ethernet main-a/2 queue-group profile q_group_2_level_default
exit all
#*********************************End********************************************
config port ethernet main-a/1 classification-key vlan p-bit
exit all
#*********************************End********************************************
config port ethernet main-a/1 no shutdown
exit all
#*********************************End********************************************
exit all
#*********************************End****************************************
map 0 to-cos 0
map 1 to-cos 1

map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
***********************Configuring_Bridge_and_Bridge_Ports***********************
config port svi 1 bridge
exit all

exit all

exit all
config bridge 1 port 1

bind svi 1
no shutdown
exit all

bind svi 2
no shutdown
exit all

bind svi 3
no shutdown
exit all
config bridge 1 vlan 20 tagged-egress 1..3

exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
config flows flow 1
classifier class20
ingress-port ethernet main-a/1
egress-port svi 1
no shutdown
exit all
config flows flow 2

classifier class20
ingress-port svi 1
egress-port ethernet main-a/1 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all

config flows flow 3

classifier class20
egress-port svi 2
no shutdown
exit all
config flows flow 4

classifier class20
ingress-port svi 2
no shutdown
exit all
config flows flow 5

classifier class20
egress-port svi 3
no shutdown
exit all
config flows flow 6

classifier class20
ingress-port svi 3
no shutdown
exit all
#*********************************End********************************************
20,100,300,1000
40,200,600,1000
exit all
#*********************************End********************************************
config oam cfm
md-level 3
name uint 37
mep 3
bind svi 1
direction up
flow uni-direction rx 2 tx 1
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1

dest-ne 1
remote mac 00-20-d2-50-1d-28
exit
no shutdown
exit all
#*********************************End********************************************


exit all
#*********************************End********************************************
Example 4. RMEP Configuration

The example below shows the CLI configuration of the remote-mep in service.
config oam cfm
md-level 3
ccm-interval 1s
name uint 256
mep 201
bind ethernet main-a/1
direction down
cos-mapping profile cos7_0
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1
delay-threshold 100
delay-var-threshold 10
dest-ne 1
remote mep-id 101
exit
no shutdown
The table below lists the messages generated by ETX-5 when a configuration
error is detected.

Message Description
Mismatch between flow and MIP The classification profile bound to the MIP and the classification
classification profiles profiles of its Rx/Tx flows do not match
Flow must be enabled The flow must be administratively enabled before it is bound to
the MEP/MIP
Maximum number of MEPs (8) associated A single flow can be bound to up to eight MEPs
with the flow has been reached
Different MEPs/MIPs, using the same When the same flow is bound to different MEPs/MIPs, the flow
flow, must have different MD levels must have different MD levels
MIP bound to Ethernet port or LAG must When a MIP is bound to an Ethernet port or LAG, the MIP must
have classification profile have a classification profile assigned to it
MIP-bound bridge port is not a member The bridge port of the SVI to which the MIP is bound is not a
of the MHF’s classification profile VLAN member of the VLAN defined in the VLAN-based classification
profile used by the MIP’s MHF
MEP is not bound to a port A MEP must be bound to an Ethernet port, LAG or bridge-type
SVI
Cannot bind CoS mapping profile to a The CoS profile cannot be bound to a MEP bound to an Ethernet
MEP bound to an Ethernet port or LAG port or LAG
Cannot bind queue mapping profile to a The queue mapping profile cannot be bound to a MEP bound to
MEP bound to an Ethernet port or LAG an Ethernet port or LAG
Up MEPs are bound to SVI (B), Down The Up MEP must be bound to a bridge-type SVI. The Down MEP
MEPs are bound to Ethernet port or LAG must be bound to an Ethernet port or LAG
MA number is out of range The MA number is out of range (1–2048)
Cannot delete MA with MEPs The MA cannot be deleted if it has MEPs defined under it
Current MA name is already in use A name assigned to the MA already exists
Cannot change MA with MEPs The MA parameters cannot be changed if the MA has MEPs
defined under it
Cannot change MA with MIPs The MA parameters cannot be changed if the MA has MIPs
defined under it
The value is out of range The value entered not within the allowed range
MA name is out of range The MA name value is not within the allowed range (0–6535)
Max number of MEs has been reached The maximum number of MEs (4096) has been reached
Max value has been reached The maximum value for the current parameters has been
reached. This may refer to the number of MEPs/MIPs, remote
MEPs, destination NEs, etc.
Max number of Down MEPs per MA has Only one Down MEP is allowed per MA
been reached
Max number of Up MEPs per MA has Up to 88 Up MEPs are allowed per MA

been reached

Message Description
Entity must be in shutdown The entity (MEP, MIP, port, etc.) must be administratively
disabled in order to delete or change its parameters
Port does not exist The port to which you are trying to bind a MEP/MIP does not
exist
MEP/MIP port is not Ethernet, LAG or SVI The port to which you are trying to bind a MEP/MIP is not
Ethernet, LAG or SVI
SVI must be of bridge type The SVI to which you are trying to bind a MEP/MIP is not a bridge
type
VLAN ID is out of range The selected VLAN ID is not within the allowed range (0–4094)
VLAN ID can be changed in MEP/MIP The VLAN ID can be changed only when the MEP/MIP is
shutdown administratively disabled
Classification profile can be changed in Assigned classification profile can be changed only when the
MEP/MIP shutdown MEP/MIP is administratively disabled
Invalid classification profile The classification profile bound to the MEP/MIP is not valid.
Profile does not exist A non-existing classification or CoS mapping profile has been
bound to MEP/MIP
CoS mapping profile must be P-bit-to- Only a P-bit-to-CoS CoS mapping profile can be bound to
CoS MEP/MIP
Only default queue mapping profile is Only a default queue mapping profile (QueueMapDefaultProfile)
allowed can be bound to MEP/MIP
Port can be changed, when MEP/MIP is in The port to which a MEP/MIP is bound can be changed only
shutdown when the MEP/MIP is administratively disabled
LTM destination MAC cannot be multicast The destination MAC address for OAM link trace messages
cannot be a multicast type
Cannot enable OAM service if no The OAM service can be administratively enabled only if a
destination NE exists destination NE has been defined for it
destination NE MAC exists destination NE MAC address has been defined
Destination NE MAC can be unicast only The MAC address of the destination NE can be a unicast type
only
MEP Rx flow must be configured The Rx flow for the MEP has not yet been configured
MEP Tx flow must be configured The Tx flow for the MEP has not yet been configured
I/O port-to-SAP flow must be configured For Rx flow with ingress port defined as SAP, there must be a
for Rx flow with SAP as ingress port matching flow between I/O port and SAP
Illegal ingress port for Rx or Tx flow The ingress port for Rx and Tx flows must be an Ethernet port,
LAG, bridge-type SVI or SAP
Classification profile must be bound to If Rx flow uses the Match All classification mode, a separate
MEP/MIP, if Rx flow uses Match All classification profile must be bound to the MEP/MIP
classification

Message Description
Classification profile must be bound to If Tx flow uses the Match All classification mode, a separate
MEP/MIP, if Tx flow uses Match All classification profile must be bound to the MEP/MIP
classification
Classification profile cannot be bound to If Rx flow does not use the Match All classification mode, a
MEP/MIP, if Rx flow uses other than separate classification profile cannot be bound to the MEP/MIP
Match All classification
OAM service must be in shutdown The OAM service must be administratively disabled for this
action
MEP must be in no shutdown The MEP to be administratively enabled for this action
Illegal number of MDs The number of MDs is out of range (1–2048)
Cannot delete MD with MA or MIP under An MD with existing MAs or MIPs cannot be deleted
it
Illegal MD level The MD level value is out of allowed range (0–7)
Cannot change MD level The MD level cannot be changed if the MD has MEPs/MIPs under
it
Max number of MDs has been reached The maximum number of MDs (4096) has been reached
Bin profile is in use and cannot be The measurement bit profile is in use and cannot be deleted or
changed modified
4.12 OAM EFM

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-5 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.
Standards
IEEE 802.3ah
Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
65B
ETX-5 12BOAM EFM 4-93

Factory Defaults
By default, OAM EFM is not enabled for Ethernet ports.
OAM EFM is specified by IEEE 802.3ah and can be implemented on any full-duplex
point-to-point or emulated point-to-point Ethernet link.
OAM EFM messages are sent in untagged slow protocol frames called OAM
Protocol Data Units, or OAMPDUs. They cannot propagate beyond a single hop
within an Ethernet network and have modest bandwidth requirements (frame
transmission rate is limited to a maximum of 10 frames per second).
802.3ah 802.3ah
Ethernet Ethernet
OAMPDUs MPLS OAMPDUs
Access Access
Core Network
Network Network
Customer Service Provider Service Provider Customer

Router Router
Equipment Edge Device Edge Device Equipment
Figure 4-36. 802.3ah OAM
Layer-2 Operation
OAM EFM operates purely at the Ethernet layer, and so (unlike SNMP or ping)
does not require an IP address. This means that Ethernet service providers do not
need to run IP protocols or manage IP addresses. Furthermore, special Ethernet
features may be directly supported, such as Ethernet multicast and slow protocol
frames. When an OAM frame is received by an OAM-enabled Ethernet MAC, it is
passed to the OAM client for processing; such a frame is simply discarded if
received by a MAC that does not support link-layer OAM. In any case, link-layer
OAM frames are never forwarded.
Since the IEEE link-layer OAM is generally used over a link between a service
provider and a customer, it defines two modes for OAM entities: active or
passive. The elements of the provider network (e.g. DSLAMs or provider Ethernet
switches) operate in active mode, and can exert control over the passive-mode
devices (e.g. DSL modems or customer premises switches). Thus, the active-mode
entity can send an LB command forcing the passive-mode device into loopback
mode, and query the configuration parameters of the passive-mode device.
However, the reverse is not possible.
OAMPDUs
The OAMPDUs perform the following functions:
• Discovery is the procedure whereby OAM-enabled entities discover each
other and exchange information regarding their OAM capabilities and
configuration. The OAM capabilities may be used to determine whether it is
worthwhile to run the OAM protocol.
Disovery is initiated by an active ETX-5 Ethernet port. It advertises the
following capabilities:
 Mode
4-94 12BOAM EFM ETX-5

 Maximum PDU size

 Loopback support (active port only)
 Variable retrieval (not supported)
 Event notification
 Unidirectional operation.
• ETX-5 transmits link failure indication to the peer. ETX-5 terminates the
following 802.3ah events:
 Remote fail indication
 Critical alarm
 Dying gasp indication on remote device.
• Loopback control used by an active-mode OAM entity to enable or disable
intrusive loopback in the remote passive-mode device. Active ETX-5 ports
support EFM loopback request. Passive ports identify loopback requests, and
close the EFM loop.
RAD OUI
OAMPDUs use RAD OUI (Organizationally Unique Identifier) – 00-20-D2.
MAC Address
OAMPDUs use the relevant port MAC as the MAC SA. To support OAM EFM, the
user must configure trap the 01-80-C2-00-02, using L2CP mechanism.
To ensure correct distribution of EFM traffic, you must configure flow with an
L2CP profile with peer action for the OAM EFM address (01-80-c2-00-00-02). The
flow must have the following attributes:
• Untagged classification
• Ingress port – Ethernet port
• Egress port – according to application requirements.
If you use the flow only to peer the EFM frames and do not need to forward the
untagged traffic, discard it, using the drop command on the flow.
Configuring OAM EFM

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

1. Navigate to configure>oam>efm.
2. Enter: descriptor <number> {active | passive}.
 To configure OAM EFM for Ethernet port:

1. Navigate to configure port ethernet <slot/port>.
The config>port>eth(<slot/port>)# prompt is displayed.

Enabling OAM EFM, and defining efm-descriptor <1–2> {active | The EFM descriptor must exist
its operation mode passive} before you can assign it to a
port.
Note: In order for OAM EFM to
function properly, the relevant
Ethernet port must be
associated with an L2CP profile
that specifies peer action for
MAC 01-80-C2-00-02.
Disabling OAM EFM no efm
Requesting OAM EFM loopback loopback no loopback disables OAM EFM

activation from remote device no loopback loopback initaition request.
This command is relevant for
active OAM EFM mode only.
Displaying OAM EFM status show oam-efm
Displaying OAM EFM statistics show oam-efm-statistics
Clearing OAM EFM statistics clear oam-efm-statistics
Displaying OAM EFM Status

OAM CFM status is supported at the port level.
 To display OAM EFM status:

• In the config>port>eth(<slot/port>)# prompt, enter show oam efm.
The status screen appears.
ETX-5>config>port>eth(1/1)# show oam efm
Administrative Status : Enabled
Operetional Status : Operational
Loopback Status : Off
OAM EFM Information

---------------------------------------------------------------
Local Remote
MAC Address : 00-20-D2-F8-80-5B 00-20-D2-F8-80-5C
Mode : Active Active
Unidirectional : Supported Supported
Vars Retrieval : Not Supported Not Supported
Link Events : Not Supported Supported
Loopback : Not Supported Supported
PDU Size : 1500 1518
Vendor OUI : 0x0020D2 0x0020D2
4-96 12BOAM EFM ETX-5

Displaying OAM EFM Statistics

OAM EFM statistic collection is supported at the port level.
 To display OAM EFM statistics:

• In the config>port>eth(<slot/port>)# prompt, enter show oam efm statistics.
The statistics screen is displayed.
ETX-5>config>port>eth(1/1)# show oam efm statistics
OAM EFM Statistics

---------------------------------------------------------------
Rx Tx
Information : 31 31
Loopback Control : 0 0
Example
 To enable OAM EFM on Ethernet port B/4:
#******************Assigning_Default_Queue_Group_Profiles********************
#*********************************End****************************************
************************Defining_Classifier_Profiles*************************
config flows classifier-profile untagged match-any
match untagged
exit all
config flows classifier-profile all match-any

match all
exit all
#*********************************End****************************************
#***************************Adding_L2CP_Profile******************************
configure port l2cp-profile l2cp1 mac 01-80-c2-00-00-02 peer
#*********************************End****************************************
#**************************Adding_Flow_for_Peering_EFM_Traffic***************
config flows flow 121
classifier classutg
egress-port ethernet main-a/3 queue-map-profile QueueMapDefaultProfile block
0/1
l2cp profile l2cp1
drop
pm-enable
no shutdown
exit all
#*********************************End****************************************
#***************************Adding_OAM_EFM_Descriptor************************
configure oam efm-descriptor 2 passive

exit all
#*********************************End****************************************
#**************************Configuring_Ethernet_Port*************************
configure port ethernet main-b/4 efm descriptor 2
exit all
config port ethernet main-b/4

no shutdown
exit all
#*********************************End****************************************
4.13 Services for Management Traffic

To gain access to the devices, as explained in Management Access Methods, you
must provision an E-LAN (Layer-2) or routing (Layer-3) service. Services are
explained in Chapter 5.
4.14 SNMP Management

SNMP stands for Simple Network Management Protocol. It is an application layer
protocol that provides a message format for the communication between
managers and agents. SNMP systems consist of an SNMP manager, an SNMP
agent and a MIB. The NMS can be part of a management network system. To
configure SNMP, you must define the relationship between the manager and the
agent. ETX-5 supports SNMPv3, the latest SNMP version to date. SNMPv3
provides secure access to devices in the network by using authentication and
data encryption.
Standards
This section lists the standards on which the supported SNMP versions are
based.
• 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
4-98 14BSNMP Management ETX-5

• RFC 1906, Transport Mappings for Version 2 of the Simple Network

Management Protocol (SNMPv2).
• RFC 1907, Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group.
• RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework. SNMPv2 Working Group.
• RFC 2104, Keyed Hashing for Message Authentication.
• RFC 2271, Architecture for Describing SNMP Management Frameworks.
• RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP).
• RFC 2273, SNMPv3 Applications.
• RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3).
• RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP).
• RFC 3412, Version 3 Message Processing and Dispatching.
• RFC 3414, User-based Security Model for SNMPv3
• RFC 3416, Update for RFC 1904.
Benefits
The SNMP protocol allows you to remotely manage multiple units from a central
work station using RADview EMS. RADview EMS offers a graphical user interface
that resembles the front panel of your unit with its interfaces and LEDs.
ETX-5 supports SNMPv3, which 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.
SNMPv1 and SNMPv2 can neither authenticate the source of a management
message, nor provide privacy (encryption).
To overcome these limitations, SNMPv3 provides a security framework for
SNMPv1 and SNMPv2 that adds the following main capabilities:
• Security features:
 Authentication – checks the integrity of management data and verifies its
origin, and thus ensures that unauthorized users cannot masquerade as
authorized users
 Privacy – ensures that unauthorized users cannot monitor the
management information passing from managed systems to the
management system
 Authorization and access control – ensures that only authorized users
can perform SNMP network management functions and contact the
managed entities.
ETX-5 14BSNMP Management 4-99

• Administrative features:
 Naming of entities
 People and policies
 Usernames and key management
 Notification destinations
 Proxy relationships
 Remote dynamic configuration of agents via SNMP operations.
SNMP Engine ID
An important parameter related to SNMPv3 is the SNMP engine ID, a unique and
unambiguous identifier of the function that processes SNMP messages. It also
identifies the SNMP entity that corresponds to the engine.
The SNMP engine ID is a string that has three segments:
• An automatically-generated, fixed segment
• A selectable segment that identifies the configuration type (method) used to
derive the user-defined segment
• A user-defined segment, which must be unique within the SNMP-managed
network. The method used to configure this segment depends on the
configuration type.
The automatically-generated segment of the SNMP engine ID changes after each
restart (reboot) of the SNMPv3 protocol. As explained below in the SNMPv3
Administrative Features section, the SNMP engine ID is the first parameter to be
set whenever SNMPv3 is used and the configuration data and authorized users
must be reconfigured.
SNMPv3 Message Processing

SNMPv3 message processing requires two mechanisms (models): the message
processing model, and a specific security model.
The message processing model performs the following tasks:
• In the transmit direction: accepts SNMP protocol data units (PDUs) from the
SNMP agent central processor, encapsulates them in messages, and then
subjects the message to the security model, to insert security-related
parameters in the message header
• In the receive direction: accepts incoming messages, uses the security model
to process the security-related parameters in the message header, and
delivers the encapsulated PDU to the SNMP agent central processor
The message processing models supported by ETX-5 are as follows:
 SNMPv2c: SNMPv2 with community-based security model
 SNMPv2u: SNMPv2 with user-based security model (USM)
 SNMPv3
The security models available for ETX-5 are as follows:
 SNMPv2c: SNMPv2 with community-based security model

 User-based security model (USM)

You can also enable using any of the above-mentioned models, to match
different management station capabilities: the appropriate model is automatically
selected, in accordance with the model used in the incoming SNMP message.
User-Based Security Model (USM)

The USM, defined in RFC 2272, provides authentication and privacy services for
SNMP, to protect against modification of information in transit from an
authorized entity (including modification of message order, delaying or replaying
of valid messages to change their effect, etc.), to prevent an unauthorized entity
from performing management operations by assuming the identity of an
authorized entity, and to prevent disclosure of the contents of the messages
exchanged between a management station and an agent.
To achieve these goals, USM uses authentication to check the integrity of
transmitted messages, and encryption to prevent disclosure:
• Authentication mechanisms. Mechanisms that provide integrity checks based
on a secret key are usually called message authentication codes (MAC).
Typically, message authentication codes are used between two parties that
share a secret key in order to validate the information transmitted between
these parties. Therefore, an SNMP engine requires an authentication key and
a privacy key. Separate values of these two keys are maintained for each
local and remote user, and their values must be stored by each user, because
the keys are not accessible via SNMP.
USM authentication protocol is based on the key-Hashing Message
Authentication Code (HMAC), described in RFC2104. HMAC uses a user-
selected secure hash function and a secret key to produce a message
authentication code. USM allows the use of one of two alternative
authentication protocols, where both generate a 96-bit output that is used
to check message integrity:
 HMAC-MD5-96: HMAC is used with MD5 (Message Digest algorithm 5) as
the underlying hash function.
 HMAC-SHA-96: HMAC is used with SHA-1 (Secure Hashing Algorithm 1).
• Encryption mechanism. USM uses the cipher block chaining (CBC) mode of the
Data Encryption Standard (DES) for encryption, with a key length of 56 bits.
View-Based Access Control Model (VACM)

SNMP manager authorizations are defined by means of the view-based access
security model (the name of the model is derived from the method used to
define the authorizations: control over the MIB parts that can be viewed by each
manager).
VACM makes it possible to configure each SNMPv3 agent to allow different levels
of access to different managers; for example, the ETX-5 SNMPv3 agent may limit
some managers to viewing only the ETX-5 performance statistics, and allow
others to view and update ETX-5 configuration parameters. Moreover, the
SNMPv3 agent can also limit what a manager can do by accepting only commands
that invoke parameters included in certain parts of the relevant MIBs (for

example, read-only access to the configuration parameters part of a MIB, and

read-write access to the diagnostics part).
The access control policy used by the agent for each manager must be
preconfigured (the policy essentially consists of a table that details the access
privileges of each authorized manager). For ETX-5, the VACM parameters can be
configured only by means of a MIB browser, and/or by SNMP commands
SNMP Security Level

The USM capabilities enable the user to select the level of security at which SNMP
messages can be sent or with which operations they are processed. The options
are as follows:
• No authentication and no privacy (encryption) – the lowest protection.
• With authentication, but without privacy
• With authentication and with privacy – the best protection level.
SNMPv3 Administrative Features

The administrative features of SNMPv3 enable definition of the entities that are
allowed to manage an entity; for example, the ETX-5. There are two
administrative elements:
• User management. During SNMPv3 configuration, it is necessary to define
allowed users and their security attributes. For each user, it is possible to
select the security level, and the passwords used for each type of protection
(authentication and/or privacy) needed at the selected level.
• Target and notification management. As part of the SNMPv3 configuration,
you can also define the notification capabilities for a list of entities referred
to as targets (of notification messages). For each target, you can specify a
message processing model, a security model, and the required security level.
You can also define a list of notifications that can be sent to the
corresponding target.
Factory Defaults
The default configuration of the SNMP parameters is as follows:
• 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".
• Group for SNMPv2c named “v2_read”:
 Security level: no authentication and no privacy

 Read view = “internet”

 Write view = “”
 Notify view = “internet”
• Group for SNMPv2c named “v2_write”:
 Read view = “internet”
 Write view = “internet”
 Notify view = “internet”
• Group for SNMPv2c named “v2_trap”:
 Read view = “”
 Write view = “”
 Notify view = “internet”.
• Notifications with tag “unmasked” for the device traps.
SNMPv3 Configuration
ETX-5 supports SNMP version 3, providing 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
graphical 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 ETX-5 default configuration provides only one standard user named
“initial” with no encryption and the lowest security level.
 To configure SNMPv3:
1. Set SNMP engine ID if necessary
3. Add users, specifying authentication protocol and privacy protocol
4. Add groups, specifying security level and protocol
5. Connect users to groups
6. Add notification entries with assigned traps and tags
7. Configure target parameter sets to be used for targets
8. Configure targets (SNMPv3 network management stations to which ETX-5
should send trap notifications), specifying target parameter sets and
notification tags
 To configure SNMPv3 parameters:
1. Navigate to configure management snmp.
2. 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 group access-group <group-name> snmp no access-group deletes the

{ snmpv2c | usm } group
{ no-auth-no-priv | auth-no-priv | auth-priv }
Defining context context-match {exact | prefix} snmp>access-group

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

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

group
Setting write view write-view <name> snmp> access-group

of group
Administratively no shutdown snmp> access-group

enabling group
Configuring community <community-index> snmp

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

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

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

enabling community community

Enabling/disabling config-change-notification snmp> Configuration change trap is

generation of sent upon any configuration
configuration change in the device
change trap (initiated from CLI or SNMP).
It contains information
about all the modified
entries and variables; if trap
has too many variables, it is
divided into several
configuration change traps.
Enable configuration change
notifications only after I/O
card have been provisioned,
using the card-type
command. Otherwise, the
system will be flooded with
mandatory notifications,
generated, when a card type
is changed.
Configuring notify <notify-name> snmp>

notifications

Assigning trap to bind {coldStart | linkDown | linkUp | snmp>notify You can assign more than
notification authenticationFailure | one trap to a notification, in
systemDeviceTemperatureOra | separate commands
systemSoftwareInstallEnd |
systemAlternateConfigLoaded |
systemDyingGasp | systemDeviceStartup |
systemSwUnconfirmed |
systemStartupConfigUnconfirmed | fanFailure |
systemSuccessfulLogin | systemFailedLogin |
systemLogout | powerDeliveryFailure |
systemTrapHardSyncStart |
systemTrapHardSyncEnd | systemUserReset |
smartSfpMismatch | systemRfc2544TestStart |
systemRfc2544TestEnd |
clockDomainSystemClockUnlock |
sourceClockFailure | stationClockLos |
clockDomainStationClockUnlock |
ptpRecoveredUnacceptableFrequencyAccuracy
| ptpRecoveredMasterDisqualification |
ptpRecoveredPtpStateChange |
ptpRecoveredSevereFrequencyCondition |
epsConfigurationMismatch | epsPortSwitchover
| sfpRemoved | ethLos |
oamEfmRemoteLoopback |
oamEfmRemoteLoopbackOff |
oamEfmCriticalLinkIndication |
oamEfmFeCriticalLinkIndication |
oamEfmDyingGaspIndication |
oamEfmFeDyingGaspIndication | sdhSonetLos |
e3t3Los | e1t1Los | systemDownloadEnd |
oamCfmMepAis | oamCfmMepLck |
oamCfmMepMismatch | oamCfmRmepLoc |
oamCfmRmepRdi | oamCfmDestNeDelayTca |
oamCfmDestNeDelayTcaOff |
oamCfmDestNeDelayVarTca |
oamCfmDestNeDelayVarTcaOff |
oamCfmDestNeLossRatioTca |
oamCfmDestNeLossRatioTcaOff |
oamCfmDestNeLossRatioTcaFe |
oamCfmDestNeLossRatioTcaFeOff |
oamCfmDestNeUnavailableRatioTca |
oamCfmDestNeUnavailableRatioTcaOff |
oamCfmDestNeUnavailableRatioTcaFe |
oamCfmDestNeUnavailableRatioTcaFeOff}
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

notification filter to
define access to a
particular part of
the MIB hierarchy
for trap variables
Specifying the part mask [<mask>] snmp>notify-filter

of the subtree OID
to use in order to
define the MIB
subtree
Defining whether type {included | excluded} snmp>notify-filter

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

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

notification filter
profile
Configuring profile-name <argument> snmp>filter-profile

notification filter
profile name
Administratively no shutdown snmp>filter-profile

enabling
notification filter
profile
Connecting security security-to-group { snmpv2c | usm } snmp no security-to-group

name to group (e.g. sec-name <security-name> removes security-to-group
connecting user or entity
community to
group)
Specifying group to group-name <group-name> snmp>security-to-group

which to connect
security name
Administratively no shutdown snmp>security-to-group shutdown disables the

enabling security-to-group entity
security-to-group
entity

Setting SNMP snmp-engine-id mac [ <mac-address> ] snmp If you use the mac option
engine ID, as MAC snmp-engine-id ipv4 [ <ip-address> ] and don’t specify the MAC
address or IP address, the SNMP engine ID
snmp-engine-id text <string>
address or string is set to the device MAC
address
If you use the ipv4 option
and don’t specify the IP
address, the SNMP engine ID
is set to the device IP
address
Configuring target target <target-name> snmp no target removes target

(SNMPv3 network
manager)
Specifying target address udp-domain <ip-address> address snmp>target

address as IP oam-domain <oam-port>
address or OAM
port
Assigning tag(s) to tag-list <tag> snmp>target If you specify more than one
target (the tag(s) tag-list [ <tag> ] tag, you must enclose the
must be defined in list in square brackets; if you
tag-list [ <tag1>,<tag2>,…<tagn> ]
notification entries) specify just one tag, the
brackets are optional
Specifying set of target-params <params-name> snmp>target

target parameters
for target
Specifying trap trap-sync-group <group-id> • If the group does not

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

enabling target
Configuring set of target-params <target-param-name> snmp no target-params removes

target parameters, target parameters
to be assigned to
target

Specifying message message-processing-model snmp>target

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

whose behalf SNMP [ level { no-auth-no-priv |
messages are to be auth-no-priv | auth-priv } ]
generated for the
set of target
parameters
Specifying SNMP version { snmpv2c | usm } snmp>target Use usm for SNMPv3 version
version to be used
when generating
SNMP messages for
the set of target
parameters
Administratively no shutdown snmp>target shutdown disables target

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

parameters and group must be previously
tags for trap defined in the target level
synchronization
group
Specifying tags tag-list <list> snmp>trap-sync-group To remove the tag list,

enter: no tag-list
Specifying set of target-params <params-name> snmp>trap-sync-group To remove the tag list,

target parameters enter: no target-params
<params-name>
Configuring user user <security-name> snmp If you don’t specify the

[md5-auth [ {des | none} ] ] authentication method
user <security-name> when creating a user, the
[sha-auth [ {des | none} ] ] default is MD5 with DES
privacy protocol. To create a
user <security-name> [none-auth]
user with no authentication,
specify none-auth.
no user <security-name>
deletes the user

Setting user authentication [ password <password> ] snmp>user no authentication disables

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

enabling user authentication and
privacy method before
you can enable the user,
unless the user was
defined with no
authentication
(none-auth)
• shutdown disables the
user.
Defining access to a view <view-name> <sub-tree-oid> snmp view-name –Name of view,

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

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

access to the MIB the subtree
subtree is allowed excluded – Disables access
to the subtree
Administratively no shutdown snmp>view

enabling view

Displaying trap show trap-sync snmp

synchronization
groups and
members for
SNMPv3 manager
groups
Displaying SNMPv3 show snmpv3 information snmp

information, such
as the number of
times the SNMPv3
engine has booted,
and how long since
the last boot
Example
 To create SNMPv3 user and connect it to group:
• User named “MD5_priv”:
 Security level – MD5 authentication, DES privacy
• Group named "SecureGroup":
 All security levels
 Contains set of views named "internet" (from default configuration).
ETX-5# configure management snmp
ETX-5>config>mngmnt>snmp# user MD5_priv md5-auth des
ETX-5>config>mngmnt>snmp>user(MD5_priv)$ privacy password MD654321
ETX-5>config>mngmnt>snmp>user(MD5_priv)$ authentication password MD654321
ETX-5>config>mngmnt>snmp>user(MD5_priv)$ no shutdown
ETX-5>config>mngmnt>snmp>user(MD5_priv)$ exit
ETX-5>config>mngmnt>snmp# access-group MD5Group usm no-auth-no-priv
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ context-match prefix
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ read-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ write-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ notify-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ no shutdown
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ exit
ETX-5>config>mngmnt>snmp# access-group MD5Group usm auth-no-priv
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ context-match prefix
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ read-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ write-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ notify-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ no shutdown
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ exit
ETX-5>config>mngmnt>snmp# access-group MD5Group usm auth-priv
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ context-match prefix
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ read-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ write-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ notify-view internet
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ no shutdown
ETX-5>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ exit

ETX-5>config>mngmnt>snmp# security-to-group usm sec-name MD5_priv

ETX-5>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ group-name MD5Group
ETX-5>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ no shutdown
ETX-5>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ exit
ETX-5>config>mngmnt>snmp#
 To create notifications:
• Notification named “TrapData”:
 Tag = “Data”
 Bound to agnStatusChangeTrap, agnUploadDataTrap.
• Notification named “TrapPower”:
 Tag = “Power”
 Bound to agnPowerFailureTrap, coldStart.
ETX-5>config>mngmnt>snmp# notify TrapPort
ETX-5>config>mngmnt>snmp>notify(TrapPort)$ tag Port
ETX-5>config>mngmnt>snmp>notify(TrapPort)$ bind ethLos
ETX-5>config>mngmnt>snmp>notify(TrapPort)$ bind sfpRemoved
ETX-5>config>mngmnt>snmp>notify(TrapPort)$ no shutdown
ETX-5>config>mngmnt>snmp>notify(TrapPort)$ exit
ETX-5>config>mngmnt>snmp# notify TrapPower
ETX-5>config>mngmnt>snmp>notify(TrapPower)$ tag Power
ETX-5>config>mngmnt>snmp>notify(TrapPower)$ bind powerDeliveryFailure
ETX-5>config>mngmnt>snmp>notify(TrapPower)$ bind systemDeviceStartup
ETX-5>config>mngmnt>snmp>notify(TrapPower)$ no shutdown
ETX-5>config>mngmnt>snmp>notify(TrapPower)$ exit
 To create target parameters and target:

• Target parameters named “TargParam1”:
 Message processing model SNMPv3
 version USM
 User “MD5_priv”
 Security level authentication and privacy
• Target named “TargNMS1”:
 Target parameters “TargParam1”
 Tag list = “Data”, “Power”
 IP address 192.5.4.3.
ETX-5>config>mngmnt>snmp# target-params TargParam1
ETX-5>config>mngmnt>snmp>target(TargParam1)$ message-processing-model snmpv3
ETX-5>config>mngmnt>snmp>target(TargParam1)$ version usm
ETX-5>config>mngmnt>snmp>target(TargParam1)$ security name MD5_priv level auth-priv
ETX-5>config>mngmnt>snmp>target(TargParam1)$ no shutdown
ETX-5>config>mngmnt>snmp>target(TargParam1)$ exit
ETX-5>config>mngmnt>snmp# target TargNMS1
ETX-5>config>mngmnt>snmp>target(TargNMS1)$ target-params TargParam1

ETX-5>config>mngmnt>snmp>target(TargNMS1)$ tag-list [Port,Power]

ETX-5>config>mngmnt>snmp>target(TargNMS1)$ address udp-domain 192.5.4.3
ETX-5>config>mngmnt>snmp>target(TargNMS1)$ no shutdown
ETX-5>config>mngmnt>snmp>target(TargNMS1)$ exit
 To display SNMPv3 information:

ETX-5> config>mngmnt>snmp# show snmpv3 information
SNMPv3 : enable
Boots : 2
Boots Time (sec) : 102
EngineID : 800000a4030020d2202416
4.15 Syslog
ETX-5 uses the Syslog protocol to generate event notification messages and
transport them over IP networks to Syslog servers.
Standards and MIBs

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.
Factory Defaults
By default, Syslog operation is disabled. When enabled, the default parameters
are as follows:
facility local1
port 514
severity-level informational
ETX-5 15BSyslog 4-113

The Syslog protocol provides an instrument for generating and transporting event
notification messages from ETX-5 to servers across IP networks.
Mess
ages
PSN
ETX-5
Syslog
ages Server
Mess
ETX-5
Figure 4-37. Syslog Functionality
Elements
Typical Syslog topology includes message senders (devices) and message
receivers (servers). ETX-5 supports up to five Syslog servers. The receiver
displays, stores or forwards logged information. The standard designates two
types of receivers:
• Relay, which forwards messages
• Collector which displays and stores messages.
Transport Protocol
Syslog uses User Datagram Protocol (UDP) for its transport. The UDP port
assigned to Syslog is 514, 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)
• Host name or IP address of the device
• Timestamp
• Message content.
A typical Syslog message looks like this: <145>Jan 15 13:24:07 172.17.160.69
Eth 1: Loss of signal (LOS)
Facilities and Severitie

Facility designates a device or application that sends a message. The standard
includes some pre-defined facilities in the 0–15 range. ETX-5 uses facilities
local1–7 for originator identification.
Severity is assigned to a message to specify its importance. ETX-5 uses the
following severity designations:
4-114 15BSyslog ETX-5

Table 4-16. Syslog Severities
Code Syslog Type Description
0 Emergency Emergency message
1 Alert Critical alarm
2 Critical Major alarm
3 Error Minor alarm
4 Warning Event
5 Notice Cleared alarm
6 Informational Informational message, not in use
7 Debug Debug-level messages, not in use
Syslog Configuration
When configuring Syslog parameters, it is necessary to define Syslog device and
servers.
 To configure a Syslog device:

1. Navigate to the syslog device context (config>system>syslog device).
The config>system>syslog(device)# prompt is displayed.
Defining a facility from which Syslog facility {local1 | local2 | local3 |

messages are sent local4 | local5 | local6 | local7}
Defining Syslog device UDP port for port <udp-port-number> Range is 1–65535
communication Port configuration is allowed
only if a Syslog device is
administratively disabled
Defining severity level severity-level { emergency | alert | The log messages that contain
critical | error | warning | notice | severity level above or equal
informational | debug} the specified level are
transmitted
Administratively enabling Syslog device no shutdown shutdown administratively

disables Syslog device
Clearing statistics clear statistics
Example below illustrates procedure for defining a Syslog device.

• Facility: local2
• UDP port: 155
• Severity level: major.

ETX-5# configure system syslog device

ETX-5>config>system>syslog(device)#
ETX-5>config>system>syslog(device)# facility local2
ETX-5>config>system>syslog(device)# port 155
ETX-5>config>system>syslog(device)# severity-level major
ETX-5>config>system>syslog(device)# no shutdown
 To display Syslog statistics:

2. At the config>system>syslog(device)# prompt, enter show statistics.
Syslog statistics appear as shown in Figure 4-10. The counters are
described in Table 4-9.
ETX-5>config>system>syslog(device)# show statistics
Total Tx Messages : 356
Non-queued Dropped Messages : 265
Figure 4-38. Syslog Statistics
Table 4-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
 To clear Syslog statistics:

2. At the config>system>syslog(device)# prompt, enter clear statistics.
The Syslog statistic counters are set to 0.
 To define a Syslog server:

1. Navigate to system context (config>system).
The config>system# prompt is displayed.
2. At the config>system# prompt, enter server <server-ID> to specify server to
receive Syslog messages, from 1 to 5.
The config>system>syslog(server/1–5)# prompt is displayed.
Defining Syslog server IP address

<0.0.0.0–255.255.255.255>
Enabling logging of command entries accounting commands no accounting commands

disables command logging
4-116 15BSyslog ETX-5

Defining Syslog server UDP port for port <udp-port-number> Range 1–65535
communication Port configuration is allowed
only if a Syslog server is
Administratively enabling Syslog server no shutdown shutdown administratively

disables Syslog server
Example
• Server IP address: 178.16.173.152
• UDP port: 155
ETX-5# configure system syslog server 1
ETX-5>config>system>syslog(server/1)#
ETX-5>config>system>syslog(server/1)# address 178.16.173.152
ETX-5>config>system>syslog(server/1)# port 155
ETX-5>config>system>syslog(server/1)# no shutdown
Configuration Error
The table below lists messages generated by ETX-5 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
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

4.16 Terminal Control Port

You can configure the serial port parameters, which include specifying the data rate,
security timeout, and screen size from which you are accessing the device.
Factory Defaults
Parameter defaults are listed in the table below.
baud-rate 9600bps
timeout 10
Configuring Control Port Parameters

 To define the control port parameters:
• At the config>terminal# prompt, enter the necessary commands according to
the tasks listed below.
Specifying the desired data baud-rate {300bps | The default data rate is 9600 bps.
rate 1200bps | 2400bps|
9600bps | 19200bps |
38400bps | 57800bps |
115200bps}
Defining whether in case timeout forever

of inactivity, device timeout limited <0–60>
remains connected or
disconnects after a
specified time period
Specifying the number of length <0–20> The number of rows can be 0, to indicate no limit
rows to display on the number of lines displayed, or 20.
Configuring STP
When configuring STP it is required to peer BPDU packets for protocol handling to CPU.
For this purpose user should configure an untagged flow from port / LAG with an L2CP
profile attached to it with the MAC address:
01-80-c2-00-00-00 with ‘peer’ action
Note The flow should be configured with action ‘drop.
4-118 16BTerminal Control Port ETX-5

BPDU Peer
For proper STP functionality, you must configure an L2CP profile with peer action
for the BPDU address (01-80-c2-00-00-00). The flow must have the following
attributes:
• Ingress port – Port/LAG
• Egress port – according to application requirements
If the STP runs over a VLAN aware bridge (VLAN traffic), than you use the
untagged flow only to peer the BPDU frames, and do not need to forward the
untagged traffic, discard it using the drop command on the flow.
The figure below illustrates BPDU peer configuration for main card ports.
Figure 4-39. Peer Configuration for Main Card Ports
Untagged flow
L2CP profile: BPDU
address peer
Traffic flow
Figure 4-40. Port/LAG Traffic Flows
The figure below illustrates BPDU peer configuration for main card ports
ETX-5 16BTerminal Control Port 4-119

Untagged flow
L2CP profile: BPDU address
peer
Traffic flow
(VLAN)
Figure 4-41. BPDU Peer Configuration for Main Card Ports
CLI Configuration Example

#*************************Configuring_L2CP_Profile***************************
config port l2cp l2cpl
mac 01-80-c2-00-00-00 peer
exit all
#*******************************End******************************************
config flows flow1
classifier classutg
l2cp profile l2cp1
drop
no shutdown
exit all
config flows flow2

classifier classAll
egress-port Ethernet main-a/3 queue-map-profile QueueMapDefaultProfile block
0/1
no shutdown
exit all
4-120 16BTerminal Control Port ETX-5

ETX-5 16BTerminal Control Port 4-121

Chapter 5
Services
This chapter presents information on the service elements and services
supported by ETX-5.
5.1 Service Elements

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 (NNI, UNI)
• Logical ports (SAG, SAP, SVI, LAG)
• Forwarding entities (flow, bridge, router)
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 5-1. Profile Types
Profile Type Applied to Description Scale per Chassis
Classifier Flow Defines criteria for flow classification 24K
Shaper Queue, queue block Defines CIR, CBS, EIR and EBS 256
parameter
WRED Queue Defines green and yellow packet 8

thresholds and drop probabilities
Queue Queue block Defines queue type with shaper and 16K
WRED profile
Queue block Queue block within Defines queue block parameters 384
queue group (queues, scheduling scheme,
weights)
ETX-5 Service Elements 5-1

Chapter 5 Services Installation and Operation Manual
Profile Type Applied to Description Scale per Chassis
Queue group Port Defines level-1, -2 and -3 scheduling 128

elements and structures within
queue group
L2CP Port, flow Defines actions for L2CP processing 16

(drop, peer, tunnel, and tunnel with
MAC swap)
Policer, policer Flow Defines CIR, CBS, EIR and EBS 128
aggregate parameters
Ingress color mapping Flow Defines method and values for 36

mapping different flow attributes (P-
bit, DSCP, DEI etc) to packet color
CoS mapping Flow Defines method and values for 36

mapping packet attributes (P-bit,
DSCP, IP-Precedence) to internal CoS
values
Marking Flow Defines method of mapping CoS and 16

packet color values into P-bit and DEI
Scheduling and Shaping Entities

ETX-5 schedules traffic using the following hierarchical scheduling entities:
• Queue – a lowest-level scheduling element. Its priority can be strict or weight
fair. Queues have shaper and WRED profiles assigned to them.
• 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 three levels of
queue blocks. Queue blocks 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-5 provides the following shaping tools:
• Dual token bucket shaper (CIR/EIR)
• Single token bucket shaper (CIR).
Congestion is avoided by using the WRED mechanism.
Physical Ports
GbE and 10GbE ports located in I/O and main cards 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
5-2 Service Elements ETX-5

Installation and Operation Manual Chapter 5 Services
• L2CP profile for defining L2CP frame handling (discard, peer, tunnel, and
tunnel with MAC swap)
• Queue group profile for associating a port with a queue group
• Classification key for mapping traffic into flows according to classification profiles.
ETX-5 ports can be either of two types:
• Attached directly to the main card packet processor (directly-attached ports).
These are 10GbE ports on the main cards.
• Attached to the packet processor via the classification and traffic
management engine (indirectly-attached ports). These are GbE, 10GbE and
TDM ports on the I/O cards.
Logical Ports
Logical ports maintained by ETX-5 serve as internal aggregation or forwarding
points for Ethernet flows. The following logical ports exist:
• Service Virtual Interface (SVI) used for binding flows to bridge ports, router
interfaces or Layer-2 TDM pseudowires. SVIs serve as intermediaries for
bridges and routers, which must comply with standards of their own (VLAN
domains for bridge ports or IP address for router interfaces) and do not have
physical port attributes. They also serve as aggregation points for TDM PWs.
ETX-5
LB IP
Router
RIF
SVI
SVI
SVI BP SVI
User BP BP OOB
Bridge
User BP BP NET
SVI SVI
Figure 5-1. Router and Bridge Connections with SVIs Identified

MEF-8 SVI SVI BP SVI

Pseudowires
Main Card Ethernet Ports

Flow
TDM Pseudowire Processing

BP BP
I/O Card STM-1/OC-3 Port

Bridge
SVI
Flow BP BP
SVI SVI
SVI
Flow
Figure 5-2. Layer-2 Pseudowire Connection
• Service Aggregation Group (SAG) – used for pre-forwarding traffic shaping by

means of attaching queue groups. SAGs have Service Aggregation Points
(SAPs) associated with them. In all, ETX-5 provides single SAG for every ten
GbE or one 10GbE port on an I/O card.
• SAPs – serve as ingress/egress ports for flows. They help avoid traffic
re-classification and aggregate several ingress flows. ETX-5 supports up to
512 SAPs per SAG.
Ingress Egress
SAG
Ethernet Port
I/O Card

SAP
Ethernet Port
I/O Card
SAP
Figure 5-3. Flow Termination and Aggregation at SAG
• Link Aggregation Groups (LAGs) – used for link protection. They have the
same attributes as the physical ports that serve as their members.
Forwarding Entities
Several internal entities carry traffic and make forwarding and switching
decisions. These are:
• Flows – the main traffic-carrying elements
• Bridge – traffic-forwarding element for Layer-2 E-LAN services
• Router – traffic-forwarding element for Layer-3 services.
5-4 Service Elements ETX-5

Flows
Flows are unidirectional 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 Class of
Service (CoS) according to a CoS mapping profile or assignment per flow.
• User priority (P-bit, IP Precedence, DSCP or DEI) can be mapped to packet
color (yellow or green) according to a color mapping profile or assignment per
flow.
• 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 CoS marking profile.
CoS marking profile maps CoS value and/or packet color into the egress
priority tags (P-bit, DEI).
• A single policer can be applied to a flow or a policer aggregate can be
assigned to a group of flows, using a policer profile or policer aggregate
profile.
• A flow is mapped to a specific queue block within a queue group associated
with an egress port. A specific queue in the queue block is defined 1:1 by the
packet CoS (0–7) according to a CoS-mapping profile.
Bridge
The bridge is a forwarding entity used by ETX-5 for delivering E-LAN services in
multipoint-to-multipoint topology and G.8032 ring protection. With up to 32
bridge instances, ETX-5 provides up to 128 bridge ports per bridge entity. The
bridge uses SVIs for connecting to logical and physical ports.
The bridge is defined by a bridge number, bridge ports and a VLAN membership
table that specifies which bridge ports are members in a certain broadcast
domain (VLAN). The bridge supports one level of VLAN editing on ingress and one
level on egress. The editing is performed at the flow level.
Router
The ETX-5 router is an internal Layer-3 interworking device that forwards traffic
between its interfaces. Each router interface is assigned an IP address and can be
bound to one of the following:
• Bridge port
• TDM pseudowire card for UDP/IP forwarding or 1588v2 clock entity, by
defining a virtual loopback address on a router interface.
The router uses service virtual interfaces (SVIs) for connecting 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.

5.2 E-Line Service

This section describes different scenarios for provisioning E-Line services.
I/O-to-Main Path
Figure 5-4 illustrates a typical Ethernet service created in I/O-to-main card
direction. Table 5-2 details the configuration steps needed for service
provisioning.
5-6 E-Line Service ETX-5

WRED Shaper
Queue
Queue block Shaper
1. Define profiles L2CP Classifier CoS mapping Queue group
Queue mapping Color mapping Policer Marking
SAG
Flow N x 1
I/O Card Flow 2 Main Card
SAP
Ethernet Port Ethernet Port
Configure I/O card Configure main

2. Configure ports Ethernet port card Ethernet port
Configure Configure
physical layer physical layer
Define Define
classifier key classifier key
Bind L2CP Bind L2CP

profile profile
Define VLAN tag Define VLAN tag

TPID TPID
Bind queue Bind queue

group profile group profile
3. Configure flows Configure flow 1 Configure flow 2
Bind ingress and Bind ingress and

egress ports egress ports
Bind L2CP Bind classifier

profile profile
Bind classifier Define VLAN

profile editing actions
Bind CoS Bind marking
mapping profile profile
or use fixed value
Bind color Define TPID
mapping profile
or use fixed value editing policy
Bind policer Bind queue

profile mapping profile

Legend: mapping profile block instance
Mandatory Bind queue
Optional block instance
Figure 5-4. I/O-to-Main Path
ETX-5 E-Line Service 5-7

Table 5-2. E-Line I/O-to-Main Service Provisioning
Sequence Step Commands Comments
Layer 2 Control l2cp-profile Define policy for L2CP traffic handling by port
Protocol (L2CP) and/or flow (peer, tunnel, tunnel with MAC swap,
or drop)
Classifier Profiles classifier-profile Define classification profile for traffic originating

from I/O port (flow 1) and SAP (flow 2). Use
Match All setting for flow 2.
CoS Mapping cos-map-profile Define criteria for mapping flow 1 user priority
into internal CoS values. Not relevant for flow 2.
When creating a flow, you can either bind it to
the CoS mapping profile or use a fixed value.
Color Mapping color-map-profile Define criteria for mapping flow 1 user priority
into color values. Not relevant for flow 2.
When creating a flow, you can either bind it to
the color mapping profile or use a fixed color
value.
1. Define profiles
Policing policer-profile Create a policer bandwidth profile with required

CIR, CBS, EIR, EBS values. Not relevant for flow 2.
Priority Queue queue-map-profile Define profile for mapping CoS values to queues.
Mapping Always use 1:1 mapping
(QueueMapDefaultProfile)
Congestion wred-profile Define WRED profiles to be attached to queue

Avoidance (WRED) profiles
Shaper shaper-profile Define shaper profiles to be attached to a queue

and queue group profiles
Internal Queue internal-queue- Define internal queue profiles to be attached to

profile queue block profiles
Queue Block queue-block-profile Define queue block profiles to be attached to

queue group profiles
Queue Group queue-group-profile Define queue group profile for SAG and main
card port
Marking marking-profile Define profile for conversion of CoS and packet

color values into P-bit and DEI when push or
mark tag editing is used. Not relevant for flow 1.

Ethernet Ports port Configure physical layer parameters
Define classifier keys for I/O and main card

2. Configure ports
Ethernet ports
Bind previously created L2CP profile
Select VLAN tag TPID (8100 or select another

value)
Bind the queue group profile intended for flow 1

to SAG; bind queue group profile intended for
flow 2 to main card port
Flows flow Define two flows:

• Flow 1: ingress port – I/O card port, egress
port – SAP
• Flow 2: ingress port – SAP, egress port – main
card port
Bind L2CP profile to flow 1
Bind classifier profiles to flow 1 and 2

3. Configure flows
Bind CoS mapping profile to flow 1 or use a fixed

value
Bind color mapping profile to flow 1 or use a

fixed value
Bind policer profile to flow 1
Bind queue mapping profile to flow 1 and 2
Bind queue block instance to flow 1 and 2
Define required VLAN editing actions (push, pop,

mark) for flow 2
Bind marking profile to flow 2
Define TPID editing policy for flow 2
Main-to-I/O Path
Figure 5-5 illustrates a typical service created in main-to-I/O card directions. See
Table 5-3 details the configuration steps needed for service provisioning.

1. Define profiles See Figure 5.1
I/O Card Flow Main Card


2. Configure ports Ethernet port card Ethernet port
See Figure 5.1 See Figure 5.1
3. Configure flows Configure flow
Bind ingress and

egress ports
Bind L2CP
profile
Bind classifier
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define VLAN
editing actions
Bind marking
profile
Define TPID
editing policy
Bind queue
Legend: mapping profile
Mandatory
Bind queue
Figure 5-5. Main-to-I/O Path
Table 5-3. E-Line Main-to-I/O Service Provisioning
Same as detailed in Same as detailed in Flows with ingress main card ports do not
1. Define profiles
Table 5-2 Table 5-2 support policing

Same as detailed in Same as detailed in

2. Configure ports
Table 5-2 Table 5-2
Same as detailed in Same as detailed in Define flow with ingress port set to main card
Table 5-2 Table 5-2 port, and egress port set to I/O card port
Bind L2CP profile
Bind classifier profile

3. Configure flows
Bind CoS mapping profile or use a fixed value
Bind color mapping profile or use a fixed value
Bind queue mapping profile
Bind queue block instance

mark)
Bind marking profile
Define TPID editing policy
I/O-to-I/O Path
Figure 5-6 illustrates a typical service created in I/O-to-I/O direction. Table 5-4
details the configuration steps needed for service provisioning.

SAG SAG
Flow N x 1 Flow 2
I/O Card I/O Card
Ethernet Port SAP SAP Ethernet Port
Configure I/O card Configure I/O card

2. Configure ports Ethernet port Ethernet port
Configure SAG
3. Configure flows Configure flow 1 Configure flow 2

Bind L2CP Bind classifier

profile profile
Bind classifier Define VLAN

profile editing actions
Bind CoS Bind marking
mapping profile profile
or use fixed value
Bind color Define TPID
mapping profile
or use fixed value editing policy
Bind policer Bind queue

profile mapping profile

mapping profile block instance
Legend:
Figure 5-6. I/O-to-I/O Path
Table 5-4. E-Line I/O-to-I/O Service Provisioning

1. Define profiles
Table 5-2 Table 5-2

2. Configure ports
Table 5-2 Table 5-2

Same as detailed in Same as detailed in Define two flows:

Table 5-2 Table 5-2 • Flow 1: ingress port – I/O card port, egress
port – SAP
• Flow 2: ingress port – SAP, egress port – I/O
card port

3. Configure flows

value

fixed value

mark) for flow 2
Main-to-Main Path
Figure 5-6 illustrates a typical service created in main-to-main direction. Table 5-4
details the configuration steps needed for service provisioning.

Main Card Flow Main Card

Configure main Configure main

2. Configure ports card Ethernet port card Ethernet port
3. Configure flows Configure flow
Bind ingress and

egress ports
Bind L2CP
profile
Bind classifier
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define VLAN
editing actions
Bind marking
profile
Define TPID
editing policy
Bind queue
Legend: mapping profile
Mandatory
Bind queue
Figure 5-7. Main-to-Main Path
Table 5-5. E-Line Main-to-Main Service Provisioning

1. Define profiles
Table 5-2 Table 5-2


2. Configure ports
Table 5-2 Table 5-2
Same as detailed in Same as detailed in Define one flow with ingress and egress port set
Table 5-2 Table 5-2 to main card ports

value
3. Configure flows

fixed value

mark) for flow 2
5.3 E-LAN Service

This section describes various scenarios for provisioning E-LAN services.
Depending on flow topology, different classification methods and VLAN editing
actions are used at bridge port ingress. All valid combinations are listed in VLAN
Editing section of Chapter 8.
Figure 5-8 illustrates a typical E-LAN service. Table 5-6 details the configuration
steps needed for service provisioning.
ETX-5 E-LAN Service 5-15

SAG Bridge
Flow 1 Flow 2a Flow 3a
I/O Card SAP Main Card
SVI BP BP SVI Flow 3b
Ethernet Port Flow 2b Ethernet Port
2. Configure ports Configure I/O card Configure main

Ethernet port Configure SAG card Ethernet port
3. Define bridge Define bridge
4. Define SVIs and Define SVIs (B) and

bridge ports bridge ports
Define
bridge-type SVI
Define bridge
port
Bind bridge port

to SVI
Configure VLAN
membership
5. Configure VLAN
membership Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
table size
6. Configure Configure flow 1 Configure flow 2a Configure flow 2b Configure flow 3a Configure flow 3b
flows
Bind ingress and Bind ingress and Bind ingress and Bind ingress and Bind ingress and
egress ports egress ports egress ports egress ports egress ports
Bind L2CP Define VLAN Bind classifier Define VLAN Bind classifier
profile editing actions profile editing actions profile
Bind classifier Bind marking Bind queue Bind marking Bind CoS
mapping profile
profile profile mapping profile profile or use fixed value
Bind CoS Define TPID Bind queue Bind queue Bind color
mapping profile mapping profile
or use fixed value editing policy block instance mapping profile or use fixed value
Bind color Bind classifier Bind queue Define VLAN
mapping profile Define VLAN
or use fixed value profile editing actions block instance editing actions
Bind policer Bind marking

profile profile
Bind queue Define TPID

mapping profile editing policy
Legend:
Mandatory Bind queue Bind queue
block instance mapping profile
Optional
Bind queue
block instance
Figure 5-8. E-LAN Service
5-16 E-LAN Service ETX-5

Table 5-6. E-LAN Service Provisioning

1. Define profiles
Table 5-2 Table 5-2

2. Configure ports
Table 5-2 Table 5-2
Bridge bridge Define, assign a number and configure a bridge

3. Define bridge
entity
Service Virtual svi Define bridge-port type SVIs, add ports to the
4. Define SVIs and
Interface (SVI) bridge bridge and bind the bridge ports to the SVIs
bridge ports
Bridge
Bridge bridge Add VLANs, define bridge ports as VLAN members

5. Configure VLAN
and specify MAC table size for each VLAN

membership
Same as detailed in Same as detailed in Define five flows:

Table 5-2 Table 5-2 • Flow 1: ingress – I/O card port, egress – SAP
•
6. Configure flows
Flow 2a: ingress – SAP, egress – SVI

• Flow 2b: ingress – SAP, egress – I/O card port
• Flow 3a: ingress – SVI, egress – main card
port
• Flow 3b: ingress – main card port, egress –SVI
Bind classifier profiles to all flows
ETX-5 E-LAN Service 5-17

Bind CoS mapping profile to flow 1 and 3b or use

a fixed value
Bind color mapping profile to flow 1 and 3b or

use a fixed value
Bind queue mapping profile to flow 1, 2b and 3a
Bind queue block instance to flow 1, 2b and 3a
Define required VLAN editing actions for flow 2a,

2b, 3a and 3b
Bind marking profile to flow 3a and 3b
Define TPID editing policy for flow 2a and 3b
5.4 Routing Services

ETX-5 supports a static router. Each router interface is assigned an IP address
and can be bound to one of the following:
• Bridge port
• Virtual loopback address – on a router interface on a TDM pseudowire card
for UDP/IP forwarding or on an IEEE 1588v2 master or slave entity.
I/O-to-Main via Router Path

L3 forwarding services are provisioned by directing flows from indirectly- and
directly-attached ports to a Service Virtual Interface (SVI), and then binding the
SVI to a RIF. RIFs are L3 entities identified by an IP address and a mask; L2
characteristics (VLAN tag structure) and connection to a physical port are
determined by the flows.
To ensure that only untagged traffic reaches router interfaces, ingress flows
(untagged, tagged, double tagged (without P-bit)) must be edited at the SVI to
remove tags, using pop (single VLAN) or pop-pop (double VLAN classification).
User priority is mapped to the required CoS value.
Egress flows must use Match All classification profile. To restore VLAN and priority
tagging, the following editing actions must be performed:
• Push and map CoS to P-bit (single VLAN)
• Push-push and map CoS to P-bit, using the same CoS profile for both push
actions (double VLAN).
5-18 Routing Services ETX-5

Note • Ingress flows with an untagged classification profile do not require VLAN
editing. In this case editing must be set to None.
• Egress editing action for untagged flows must be set to None.
Depending on flow topology, different classification methods and VLAN editing

actions are used at RIF ingress or egress. All valid combinations are listed in VLAN
Editing section of Chapter 8.
SAG Router
Flow 1 Flow 2a Flow 3a
SVI RIF RIF SVI Flow 3b
Ethernet Port Flow 2b Ethernet Port
2. Configure ports Configure I/O card Configure main

Ethernet port Configure SAG card Ethernet port
3. Define SVIs Define SVIs (R)
4. Configure flows Configure flow 1 Configure flow 2a Configure flow 2b Configure flow 3a Configure flow 3b
Bind classifier Bind classifier Bind queue Bind marking Bind CoS
mapping profile
profile profile mapping profile profile or use fixed value
Bind CoS Bind queue Bind queue Bind color
Define TPID mapping profile
mapping profile
or use fixed value editing policy block instance mapping profile or use fixed value
Bind color Bind queue Define VLAN
or use fixed value editing actions block instance editing actions
Bind policer Bind marking

profile profile

mapping profile mapping profile

block instance block instance
5. Define and bind router interfaces

Define RIFs
Define router
interfaces
Legend:
Mandatory Bind router
interfaces to SVIs
Optional
Figure 5-9. I/O-to-Main via Router Path
ETX-5 Routing Services 5-19

Table 5-7. I/O-to-Main via Router Service Provisioning

1. Define profiles
Table 5-2 Table 5-2

2. Configure ports
Table 5-2 Table 5-2
Service Virtual svi Define router-type SVIs

Interface (SVI)
4. Define SVIs

Table 5-2 Table 5-2 • Flow 1: ingress – I/O card port, egress – SAP
• Flow 2a: ingress – SAP, egress – SVI
• Flow 3a: ingress – SVI, egress – main card
port

5. Configure flows

a fixed value

use a fixed value

2b, 3a and 3b
Bind marking profile to flow 3a and 2b

Router router Add interfaces to the router and bind the RIFs to
6. Add RIFs and
bind them to
the SVIs
SVIs
Router-to-Bridge Path
When adding Layer-3 services to Layer-2 topology, such as G.8032 Ethernet ring,
a router interface must be connected to a bridge port.

1. Define
profiles See Figure 5.1
SAG Router Bridge

Flow 1 Flow 2a Flow 3a Flow 4a
SVI RIF RIF SVI SVI BP BP SVI Flow 4b
Ethernet Port Flow 2b Flow 3b Ethernet Port

2. Configure Ethernet port Configure SAG card Ethernet port
ports
3. Define bridge Define bridge
Define SVIs (B and R)

4. Define SVIs and and bridge ports
bridge ports
Define bridge-
and router-type
SVIs
Define bridge
ports
Bind bridge ports

to SVIs
Configure VLAN
5. Configure VLAN membership
membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
address ranges
6. Configure Configure flow 1 Configure flow 2a Configure flow 2b Configure flow 3a Configure flow 3b
flows 1-3
Bind classifier Bind classifier Bind queue Bind marking Define VLAN
profile profile mapping profile profile editing actions
Bind CoS Define TPID Bind queue Define TPID
mapping profile
or use fixed value editing policy block instance editing policy
Bind color Bind queue
or use fixed value editing actions mapping profile
Bind policer Bind marking Bind queue

profile profile block instance
Bind queue
mapping profile
Bind queue
block instance
Define RIFs
Define router
interfaces
Bind router
interfaces to SVIs
8. Configure flows Configure flow 4a Configure flow 4b

4a and 4b
Legend: Bind ingress and Bind ingress and

Mandatory
Optional Bind classifier Bind classifier
profile profile
Define VLAN Bind CoS

mapping profile
editing actions or use fixed value
Bind marking Bind color
mapping profile
profile or use fixed value
Bind queue Define VLAN
mapping profile editing actions
Bind queue Bind marking

block instance profile
Define TPID
editing policy
Figure 5-10. Router-to-Bridge Path

Table 5-8. Router-to-Bridge Service Provisioning

1. Define profiles
Table 5-2 Table 5-2

2. Configure ports
Table 5-2 Table 5-2

3. Define bridge
entity
4. Define SVIs and
bridge ports
Bridge

5. Configure VLAN
and specify MAC address ranges for each VLAN

membership

Table 5-2 Table 5-2 •
6. Configure flows 1–3
Flow 1: ingress – I/O card port, egress – SAP

• Flow 2a: ingress – SAP, egress – SVI (R)
• Flow 3a: ingress – SVI (R), egress – SVI (B)
• Flow 3b: ingress – SVI (B), egress –SVI (R)


a fixed value

use a fixed value

2b, 3a and 3b
Bind marking profile to flow 3a
Define TPID editing policy for flow 3a and 4b
Router router Add interfaces to the router and bind the RIFs to
7. Add RIFs and
bind them to
the SVIs
SVIs
Same as detailed in Same as detailed in Define flows 4a and 4b:

8. Configure flows 4a and 4b
Table 5-2 Table 5-2 • Flow 4a: ingress – SVI (B), egress – main card
port
(B)
Configure flows 4a and 4b in the same manner

as flows 3a and 3b

5.5 Pseudowire Services

ETX-5 can be used for extending TDM-based services over packet-switched
networks. It utilizes various payload (CESoPSN, SAToP) and network (UDP over IP,
MEF-8 Ethernet) encapsulation techniques to deliver synchronous traffic over
asynchronous infrastructure with the same service quality as of a legacy
SDH/SONET network. The circuit emulation traffic has the highest priority,
ensuring extremely low packet-loss transport, low latency and minimal jitter.
Depending on network type and topology, the pseudowire traffic can be
delivered as:
• Point-to-point L2 service for MEF-8-encapsulated PWs
• Bridge L2 for MEF-8-encapsulated PWs
• L3 forwarding over router for UDP/IP-encapsulated PWs.
Point-to-Point L2 Pseudowire Service

Figure 5-11 illustrates a point-to-point L2 pseudowire service. Table 5-9 details
the configuration steps needed for service provisioning.
ETX-5 Pseudowire Services 5-25

Flow 1a
I/O Card TDM PW Main Card
Port
SVI Ethernet Port
Flow 1b

2. Configure ports TDM port card Ethernet port
Configure SDH/
SONET ports See Figure 5.1
Configure E1/T1
ports
3. Define SVI
Define SVI (PW)
4. Define PW peer Define PW peer
5. Add a pseudowire Add and configure a

pseudowire
6. Configure timeslot
cross-connections Configure cross-
connections
Configure timeslot
cross-connection
for CESoPSN PW
7. Configure flows Configure flow 1a Configure flow 1b

Define VLAN Bind classifier

editing actions profile
Bind marking Bind CoS

mapping profile
Define TPID Bind color
editing policy mapping profile
or use fixed value
mapping profile editing actions

block instance mapping profile
Legend:
block instance
Optional
Figure 5-11. Point-to-Point L2 Pseudowire Service
5-26 Pseudowire Services ETX-5

Table 5-9. Point-to-Point L2 Pseudowire Service Provisioning
Same as detailed in See Table 5-2

1. Define profiles
Table 5-2
SDH/SONET Ports port Configure physical layer parameters of the

2. Configure ports
E1 Ports SDH/SONET and E1/T1 ports
T1 Ports
Service Virtual svi Define PW-type SVI.

Interface (SVI) Remember that PW SVIs represent untagged
3. Define SVIs
traffic termination points. This means that VLAN

tags must be pushed on exiting it and popped on
the flows terminating at SVI.
Pseudowire Peer peer Configure pseudowire peer by defining its MAC

4. Define PW peer
address
Pseudowires pwe Add and configure pseudowires

pseudowire
5. Define
Cross-Connections cross-connection Assign timeslots to pseudowire

timeslot cross-
6. Configure
connections
See Table 5-2 See Table 5-2 Define two flows:

7. Configure
•
flows
Flow 1a: ingress – SVI, egress – main card

port

Bind classifier profile to flow 1b
Bind CoS mapping profile to 1b or use a fixed

value
Bind color mapping profile to flow 1b or use a

fixed value
Define required VLAN editing actions
Define TPID editing policy for flow 1a
L2 Pseudowire Service over Bridge

Figure 5-12 illustrates a L2 pseudowire service over the bridge. Table 5-10 details
the configuration steps needed for service provisioning.

Flow Bridge
PW 1a Flow 2a
I/O Card TDM
SVI SVI BP BP SVI Flow 2b Main Card
Port
Ethernet Port
Flow
Configure I/O card 1b
2. Configure ports TDM port Configure main
card Ethernet port
Configure SDH/
SONET ports See Figure 5.1
Configure E1/T1
ports
3. Define bridge
Define bridge
4. Define SVIs and

bridge ports Define Define SVIs (B) and
SVI (P) bridge ports
Define Define
PW-type bridge-type SVIs
SVI
Define bridge
ports
Bind bridge ports

to SVIs
5. Configure VLAN Configure VLAN

membership membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
table size
6. Define PW peer Define PW peer
7. Add a pseudowire Add and configure a

pseudowire
Configure cross-
cross-connections
connections
Configure timeslot
cross-connection
for CESoPSN PW
9. Configure flows
Configure flow 1a Configure flow 1b Configure flow 2a Configure flow 2b
Bind ingress and Bind ingress and Bind ingress and Bind ingress and
egress ports egress ports egress ports egress ports
Bind classifier Bind classifier Bind classifier Bind classifier

profile profile profile profile
Define VLAN Define VLAN Define VLAN Bind CoS

mapping profile
editing actions editing actions editing actions or use fixed value
Bind marking Bind marking Bind marking Bind color
mapping profile
profile profile profile or use fixed value
Legend:
Mandatory Define TPID Define TPID Bind queue Define VLAN
editing policy editing policy mapping profile editing actions
Optional
Bind queue Bind marking
block instance profile
Define TPID
editing policy
Bind queue
mapping profile
Bind queue
block instance
Figure 5-12. Pseudowire Service over the Bridge

Table 5-10. Pseudowire Service over the Bridge Service Provisioning

1. Define profiles
Table 5-2 Table 5-2
SDH/SONET Ports port Configure physical layer parameters of the

2. Configure ports
E1 Ports SDH/SONET and E1/T1 ports
T1 Ports

3. Define bridge
entity
4. Define SVIs and
bridge ports
Bridge

5. Configure VLAN
and specify MAC table size for each VLAN

membership
Pseudowire Peer peer Configure pseudowire peer by defining its MAC

6. Define PW peer
address


pseudowire
7. Define

timeslot cross-
8. Configure
connections
Same as detailed in Same as detailed in Define four flows:

Table 5-2 Table 5-2 • Flow 1a: ingress – PW SVI, egress – bridge SVI
• Flow 1b: ingress – bridge SVI, egress – PW SVI
• Flow 2a: ingress – bridge SVI, egress – main
card port
• Flow 2b: ingress – main card port, egress –
bridge SVI
9. Configure flows
Bind classifier profile
Bind CoS mapping profile to flow 2b or use a

fixed value

fixed value
Bind queue mapping profile to flow 2a and 2b
Bind queue block instance to flow 2a and 2b
Bind marking profile
Define TPID editing policy
L3 Pseudowire Service
Figure 5-13 illustrates a L3 pseudowire-over-router service. Table 5-11 details the
configuration steps needed for service provisioning.

Router
PW LB Flow 1a
Main Card
I/O TDM Card RIF SVI Flow 1b
RIF Ethernet Port
Define loopback
2. Define LB RIF RIF
Define loopback
router interface
3. Configure ports Configure TDM I/O Configure main

card and its ports card Ethernet port
Define TDM I/O See Figure 5.1

card in slot
Configure SDH/
SONET ports
Configure E1/T1
ports
4. Define SVI
Define SVI (R)
Define router-
type SVI
5. Define PW peer
Define PW peer
Define
pseudowire peer
6. Add a pseudowire Add a pseudowire
Add and
configure a
pseudowire
cross-connections Configure cross-
connections
Configure timeslot
cross-connection
for CESoPSN PW
8. Define and bind Define RIFs

router interfaces
Define router
interfaces
Bind router
interfaces to SVIs
9. Configure flows
Configure flow 1a Configure flow 1b

Define VLAN Bind classifier

editing actions profile
Bind marking Bind CoS

mapping profile
Bind queue Bind color
mapping profile
mapping profile or use fixed value
block instance editing actions
Bind queue
mapping profile
Legend:
Bind queue
Mandatory block instance
Optional
Figure 5-13. L3 Pseudowire Service

Table 5-11. L3 Pseudowire Service Provisioning

1. Define profiles
Table 5-2 Table 5-2
Router router Define a loopback router interface and assign an

2. Define loopback
router interface
IP address to it.
SDH/SONET Ports port When defining TDM I/O card in chassis slot, bind
3. Configure TDM
I/O card and card
E1 Ports it to the IP address used by loopback router

interface.
ports
T1 Ports
Configure physical layer parameters of the
SDH/SONET and E1/T1 ports.
Service Virtual svi Define router-type SVI.

Interface (SVI) Remember that router SVI represents an
4. Define SVIs
untagged traffic termination point. This means

VLAN tags must be pushed on exiting it, and
popped on the flows terminating at SVI.
Peer peer Configure pseudowire peer by defining its IP

5. Define PW peer
address

pseudowire
6. Define


timeslot cross-
7. Configure
connections
Same as detailed in Same as detailed in Define two flows:

Table 5-2 Table 5-2 • Flow 1a: ingress – SVI, egress – main card
port
Bind classifier profile to flow 1b

8. Configure flows
Bind CoS mapping profile to 1b or use a fixed

value

fixed value

Chapter 6
Cards and Ports
This chapter presents information on the following physical and logical ports in
ETX-5:
• Cards
• E1 Ports
• Ethernet Ports
• SDH/SONET Ports
• Service Aggregation Group (SAG)
• Service Virtual Interface (SVI).
• T1 Ports
6.1 Cards
Table 6-1 lists the cards currently available for the ETX-5, their functions, and
ETX-5 system capacity.
Table 6-1. ETX-5 Cards
Card Function Maximum Chassis Capacity
E5-PIM/AC Single port AC power input module (110–240 VAC, 2

50/60 Hz)
E5-PIM/DC Single port DC power input module (48 VDC) 2
E5-MC-4 Main card, contains 4 × 10GbE ports, system control 2

circuits and its timing subsystem
E5-MC-SFP-P-4 Main card, contains 4 × 10GbE ports, system control 2

circuits and its timing subsystem with SFP/SFP+ capability
E5-FAN Fan tray with eight fans and alarm relay port 1
E5-GBE-20 GbE card with20 × GbE ports, SFP or UTP 4
E5-10GBE-2 10GbE card with2 × 10GbE ports 4
E5-cTDM-4 SDH/SONET card with 4 × channelized STM-1/OC-3 ports 4
E5-cTDM-STM4 SDH/SONET card with 2 × channelized STM-4/OC-12 ports 4

(second port for APS only, does not support 2x622)
ETX-5 Cards 6-1

Chapter 6 Cards and Ports Installation and Operation Manual
Displaying Card Summary

Use the following procedures to provision cards in the ETX-5 chassis. After
physical installation in the chassis, each card must be provisioned manually. The
system identifies card types, but powers up the cards and downloads operation
software only after cards are provisioned by the user.
Before programming cards, run show card-summary command to display a list of
cards installed and identified by the chassis and their current status.
 To display the card summary

1. Navigate to configure.
The config# prompt is displayed.
2. Enter show card-summary command
The card summary screen is displayed:
ETX-5# configure
ETX-5>config>show card-summary
Slot Actual Provisioned Admin Oper Mode
-----------------------------------------------------------------------------
PS-A PSU PSU Up Up Standalone
PS-B PSU PSU Up Up Standalone
Main-A Main 10GbEx4 Main 10GbEx4 Up Up Standalone
Main-B Main 10GbEx4 Main 10GbEx4 Up Up Standalone
1 STM-1 Ch-4 STM-1 Ch-4 Up Up Standalone
3 STM-1 Ch-4 Empty Down Down Standalone
4 STM-1 Ch-4 Empty Down Down Standalone
Fan Fan Fan Up Up Standalone
Figure 6-1. Card Summary Screen
Table 6-2. Card Summary
Parameter Description Possible Values
Slot Chassis slot PS-A/B – power supply slots

Main-A/B – main card slots
1–4 – I/O card slots
Fan – fan card slot
Actual Slot status (vacant or occupied) Empty – slot is vacant

Card name – a specific card is installed in the slot
Provisioned Card provisioning status Empty –card is not yet provisioned

Card name –card is successfully provisioned
Admin Card administrative status Up – card is administratively enabled

Down – card is administratively disabled
6-2 Cards ETX-5

Installation and Operation Manual Chapter 6 Cards and Ports
Parameter Description Possible Values
Oper Card operational status Not present – slot is vacant

Up – card is provisioned and operational
Down – card provisioning command has been received,
and card software download is in progress
Mode Card protection status Standalone – Card is not a protection group member
Protection – Card is a protection group member
This section explains how to provision Main cards in slots A and B.

The default provisioned card type (in case no other configuration exist) of main
card is the actual main card type.
The following occurs when there is mismatch between the provisioned main card
type and the actual main card type:
• Main card powers up and is provisioned (except in case the configuration
includes 1 GbE port and the actual card is XFP).
• Card type or any other provisioning is not be changed.
• Card Mismatch alarm is issued.
In order to clear the card type Mismatch alarm, the provisioned card type should
be changed to the actual card type.
 To provision Main cards:

1. Navigate to configure slot (main-a or main-b)#.
The config>slot(main-a or main-b)# prompt is displayed.
2. Enter card-type command according to the task listed below:
Provisioning I/O Cards main {main-10ge-4 | main- main-10ge-4 – Main card with 4 XFP ports
Provisioning Main cards sfp-plus-4} main-sfp-plus-4 – Main card with 4 SFP+
ports
This section explains how to provision I/O cards in slots 1 to 4. ETX-5 service
cards (power inlets, power supplies, fan card) and main cards are detected and
provisioned automatically.
 To provision I/O cards:

1. Navigate to configure slot(1–4)#.
The config>slot(1–4)# prompt is displayed.
2. Enter card-type command according to the tasks listed below:
Provisioning Ethernet I/O cards eth {gbe-20-sfp | gbe-20-utp | gbe-20-sfp – GbE card with 20 SFP ports
10g-2-xfp} gbe-20-utp – GbE card with 20 UTP ports
10g-2-xfp – 10GbE card with two XFP ports
ETX-5 Cards 6-3

Provisioning TDM I/O cards sdh-sonet [stm-1-ch-4 | stm-1- Provisioning of a TDM card defines its
t1-ch-4 | oc-3-ch-4] | stm-4-ch- interface type:
1 | oc-12-ch-1] stm-1-ch-4 – STM-1 E1 card with four TDM
ports
stm-1-t1-ch-4 – STM-1 AU-3 card with four
TDM ports
oc-3-ch-4 – OC-3 card with four TDM ports
stm-4-ch-1 – STM-4 E1 card with one* TDM
port
oc-12-ch-1 – OC-12 card with one* TDM
port
* The second TDM port is operational in the Line

APS mode only.
Binding TDM I/O card to bind loopback-address <value> Binding TDM I/O card to loopback router
previously configured loopback interface is required for PW operation on
router interface UDP/IP networks.
The card can be bound only if it is in
shutdown state.
no before bind loopback-address unbinds
from loopback router interface.
Defining slot as vacant no card-type no card-type defines all unused chassis slots
as vacant
3. Use no shutdown command to activate a card in a specific slot.

4. Wait until the card initialization process is complete before starting service
configuration.
For example:
 To configure a chassis with:
• Two AC power supplies
• Two main cards
• One E5-GbE-20 card with SFP ports in slot 1
• Two E5-cTDM-4 cards with E1 interfaces in slots 2–3. The card in slot 2 is
bound to loopback router interface with IP address 10.10.10.10
• Empty slot 4.
ETX-5>config>slot(1)# card-type eth gbe-20-sfp
ETX-5>config>slot(1)# no shutdown
ETX-5>config>slot(2)# card-type sdh-sonet stm-1-ch-4
ETX-5>config>slot(2)# bind loopback-address 10.10.10.10
ETX-5>config>slot(3)# card-type sdh-sonet stm-1-ch-4
ETX-5>config>slot(4)# no card-type
6-4 Cards ETX-5

 To verify card provisioning:

• At the config# prompt, enter the show card-summary command.
ETX-5300A# configure
ETX-5300A>config>show card-summary
-----------------------------------------------------------------------------
1 ETH GBE-20-SFP Up Up Standalone
4 Empty Empty Down Not Present Standalone
Resetting I/O Cards

 To reset an I/O card:

Displaying Card Status

2. Enter reset to reset the card installed in the selected slot.
 To display card status:

2. Enter show status to display status the card installed in the selected slot.
ETX-5>config>slot(2)# show status
Actual Type : STM-1 Ch-4
Provisioned Type : STM-1 Ch-4
Operational Status : Up
Status : OK
Protection Mode : Standalone
Software Version : 0.92D001
Table 6-3 lists messages generated by ETX-5 when a configuration error is
detected.
Message Description
No protection. Shutdown is not allowed. Card cannot be shut down if no backup card has been
configured
ETX-5 Cards 6-5

Message Description
Cannot reset card in shutdown A card cannot be reset if it is shut down
Cannot change card type in no shutdown The type of an active card cannot be changed
Cannot change card IP address in no IP address of an active card cannot be changed

shutdown
Cannot change card type in requested The type of card in the selected slot cannot be modified
slot
Cannot set the card type in requested The type of card in the selected slot cannot be set
slot
A service is defined on a card, card type the type of card cannot be changed if a service is configured on
cannot be changed the card
Remove a card before changing card The type of card cannot be changed if the card is in a slot;
type remove it
A card port is used by flow: card type The type of card cannot be changed if a flow is configured on
cannot be changed/deleted the card
A card port is used by PW: card type The type of card cannot be changed if a pseudowire connection
cannot be changed/deleted (PW) is configured on the card
6.2 E1 Ports
Internal E1 ports of the E5-cTDM-4 and E5-cTDM-STM4 cards deliver pseudowire
services, emulating PDH traffic over PSN. Each internal E1 is permanently mapped
to a VC-12 channel, handling its payload in accordance with the defined ITU-T
framing mode and signaling format.
Standards and MIBs

The E1 link interfaces meet the applicable requirements of ITU-T Rec. G.703,
G.704, G.706, G.732, and G.823.
Factory Defaults
ETX-5 is supplied with all E1 ports disabled. Other parameter defaults are listed in
the table below.
line-type g732n
path-interval-threshold cv 0
path-interval-threshold es 80
path-interval-threshold ses 10
path-interval-threshold sefs 0
6-6 E1 Ports ETX-5

path-interval-threshold css 0
path-interval-threshold uas 10
idle-code 7F
out-of-service 00
tx-clock-source domain 1
loopback no loopback
trail-mode terminated
E1 Line Signal Characteristics

E1 signal characteristics are specified in ITU-T Rec. G.703. The nominal data rate
of the E1 signal is 2.048 Mbps. The E1 line signal is encoded in the High-Density
Bipolar 3 (HDB3) code.
HDB3 is based on the alternate mark inversion (AMI) code. In the AMI code, “1”s
are alternately transmitted as positive and negative pulses, whereas “0”s are
transmitted as a zero voltage level. To prevent the transmission of long strings of
“0”s, which do not carry timing information, the HDB3 coding rules restrict the
length of a “0” string that can be transmitted through the line to a maximum of
three pulse intervals. Longer strings of “0”s are encoded at the transmit end to
introduce non-zero pulses.
To allow the receiving end to detect the artificially-introduced pulses and enable
their removal, in order to restore the original data string, the encoding introduces
intentional coding violations in the sequence transmitted to the line. The
receiving end detects these violations; when they appear to be part of an
encoded “0” string, they are removed.
Coding violations may also be caused by transmission errors. Therefore, coding
violations that cannot be interpreted as intentional coding violations can be
counted, and thus provide information on the quality of the transmission link.
E1 Signal Structure
The E1 line operates at a nominal rate of 2.048 Mbps. The data transferred over
the E1 line is organized in frames. Each E1 frame includes 256 bits.
The E1 frame format, as defined in ITU-T Rec. G.704, is shown in Figure 6-2.
below.
ETX-5 E1 Ports 6-7

Time Slot 0 Time Slot 16 Time Slots 1-15, 17-31
a. Even Frames (0,2,4-14) a. Frame 0

8 Bits per
Time Slot 1 0 0 1 1 0 1 1 0 0 0 0 X Y X X
FAS MAS
Channel Data
b. Odd Frames (1,3,5-15) b. Frames 1-15
I 1 A N N N N N A B C D A B C D 1 2 3 4 5 6 7 8
TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS
32 Time Slots/Frame 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR
16 Frames/Multiframe 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Notes
I International Bit ABCD ABCD Signaling Bits
N National Bits (Sa4 through Sa8) X Extra Bit
A Alarm Indication Signal (Loss of Frame Alignment - Red Alarm) Y Loss of Multiframe Alignment
FAS Frame Alignment Signal, occupies alternate MAS Multiframe Alignment Signal
(but not necessarily even) frames
Figure 6-2. E1 Frame Format
The 256 bits included in a frame are organized in 32 timeslots of eight bits each.
The frame repetition rate is 8,000 per second; therefore the data rate supported
by each timeslot is 64 kbps.
Timeslot 0
Timeslot 0 of E1 frames is used for two main purposes:
• Delineation of frame boundaries. For this purpose, in every second frame,
timeslot 0 carries a fixed pattern, called frame alignment signal (FAS). Frames
carrying the FAS are defined as even frames, because they are assigned the
numbers 0, 2, 4, etc. when larger structures (multiframes) are used.
The receiving equipment searches for the fixed FAS pattern in the data
stream using a special algorithm, a process called frame synchronization.
Once this process is successfully completed, the equipment can identify each
bit in the received frames.
• Interchange of housekeeping information. In every frame without FAS (odd
frames), timeslot 0 carries housekeeping information. This information is
carried as follows:
 Bit 1 – this bit is called the international (I) bit. Its main use is for error
detection using the optional CRC-4 function (CRC-4 stands for Cyclic
Redundancy Check, using a fourth-degree polynomial). This function is
described below.
 Bit 2 is always set to 1, and used by the frame alignment algorithm.
 Bit 3 is used as a remote alarm indication (RAI), to notify the equipment
at the other end that the local equipment lost frame alignment, or did
not receive an input signal.
 The other bits, identified as Sa4 through Sa8, are designated national
bits, and are actually available to the users, if there is an agreement
6-8 E1 Ports ETX-5

regarding their use. The total data rate that can be carried by each
national bit is 4 kbps.
Multiframes
To increase the information carrying capacity without wasting bandwidth, the
frames are organized in larger patterns, called multiframes. ITU-T Rec. G.704
recommendations define the following types of multiframes:
• Basic G.704 framing
• G.704 framing with timeslot 16 multiframe.
Basic G.704 Multiframe

The basic G.704 structure consists of two frames, which are identified by means
of the information included in timeslot 0:
• The even frame of the pair includes the frame alignment signal (FAS).
• The odd frame has a 1 in bit position 2, and housekeeping information in the
other bits.
The number of timeslots available for user data is 31, and therefore the
maximum payload rate is 1984 kbps.
To enable the transmission of network management information, a separate
timeslot may have to be assigned within the frame. This procedure is called
common channel signaling (CCS). The CCS information is often transmitted in
timeslot 16.
G.704 Framing with Timeslot 16 Multiframe (“G.704 Multiframe”)

The G.704 multiframe structure has 16 frames, which are identified by means of a
separate multiframe alignment signal (MAS) contained in timeslot 16 of each frame.
The G.704 multiframe structure is generally used when timeslot 16 serves for the
end-to-end transmission of channel-associated signaling (CAS). A typical
application in which timeslot 16 serves for the transmission of signaling is the
transfer of voice channels by means of voice modules, which use
channel-associated signaling.
Since timeslot 16 must be reserved for the transmission of the MAS and system
signaling, only 30 timeslots are available for the user payload, and the maximum
payload rate is 1920 kbps.
When using the G.704 multiframe format, timeslot 16 of each of the 16 frames in
each multiframe carries the following information:
• The first four bits of timeslot 16 in multiframe 16 always carry the multiframe
alignment sequence, 0000.
• Bit 6 in timeslot 16 in multiframe 0 is used to notify the equipment at the
other end of the link that the local equipment lost multiframe alignment.
• The other bits of this timeslot do not have mandatory functions.
ETX-5 E1 Ports 6-9

Channel Associated Signaling

When using the G.704 multiframe format, timeslots 16 in frames 1 through 15 of
each multiframe are available for carrying user information. In general, this
information is the signaling information for the 30 payload timeslots (channels).
As shown in Figure 6-2, four signaling bits, designated A, B, C, and D, are
available for each channel, thereby enabling end-to-end transmission of four
signaling states. Each frame in the multiframe carries the signaling information of
two channels.
CRC-4 Error Detection

The ETX-5 system supports the CRC-4 function in accordance with ITU-T Rec.
G.704 and G.706. The CRC-4 function is used to detect errors in the received
data, and therefore can be used to evaluate data transmission quality over E1
links.
This function can be enabled or disabled independently for each link by the user.
To enable error detection, additional information must be provided to the
receiving equipment. The additional information is transmitted to the receiving
equipment by using a multiframe structure called CRC-4 multiframes. A CRC-4
multiframe is an arbitrary group of 16 frames. This group is not related in any
way to the G.704 16-frame multiframe structures explained above.
• A CRC-4 multiframe always starts with an even frame (a frame that carries
the frame alignment signal). The CRC-4 multiframe structure is identified by a
six-bit CRC-4 multiframe alignment signal, which is multiplexed into bit 1 of
timeslot 0 of each odd-numbered (1, 3, 5, etc.) frame of the CRC-4
multiframe (i.e., in frames 1 through 11 of the CRC-4 multiframe).
• Each CRC-4 multiframe is divided into two submultiframes of 8 frames (2048
bits) each. The detection of errors is achieved by calculating a four-bit
checksum on each 2048-bit block (submultiframe). The four checksum bits
calculated on a given submultiframe are multiplexed, bit by bit, in bit 1 of
timeslot 0 of each even-numbered frame of the next submultiframe.
• At the receiving end, the checksum is calculated again on each submultiframe
and then compared against the original checksum (sent by the transmitting
end in the next submultiframe). The results are reported by two bits
multiplexed in bit 1 of timeslot 0 in frames 13, 15 of the CRC-4 multiframe,
respectively. Errors are counted and used to prepare statistic data on
transmission performance.
E1 Alarm Conditions
• Excessive bit error rate. The bit error rate is measured on the frame
-3
alignment signal. The alarm threshold is an error rate higher than 10 that
persists for 4 to 5 seconds. The alarm condition is canceled when the error
-4
rate decreases below 10 for 4 to 5 consecutive seconds.
• Loss of frame alignment (also called loss of synchronization). This condition
is declared when too many errors are detected in the frame alignment signal
(FAS); for example, when 3 or 4 FAS errors are detected in the last 5 frames.
Loss of frame alignment is cleared after no FAS errors are detected in two
consecutive frames.
6-10 E1 Ports ETX-5

The loss of frame alignment is reported by means of the A bit (Figure 6-2).
• Loss of multiframe alignment (applicable only when the G.704 multiframe
structure is used). This condition is declared when too many errors are
detected in the multiframe alignment signal (MAS) (same conditions as for
loss of frame alignment).
The loss of multiframe alignment is reported by means of the Y bit
(Figure 6-2).
• Alarm indication signal (AIS). The AIS signal is an unframed “all-ones” signal,
and is used to maintain line signal synchronization in case of loss of input
signal; for example, because an alarm condition occurred in the equipment
that supplies the line signal. The equipment receiving an AIS signal loses
frame synchronization.
E1 Port Diagnostics
Diagnostic tools at the E1 level include local and remote loopback for checking
connections to E1 ports.
Note If an E1 port belongs to an SDH port, which is a working member of an APS

group, any loopback started on the E1 is also activated on the peer E1 port of
the protection SDH interface. Likewise, a loopback deactivated on the E1
interface of a working SDH port, is also deactivated on the peer E1 interface of
the protection SDH port. When the protection port is removed from the APS
group while the E1 loopback is still active, the E1 loopback must be deactivated
manually.
Local Loopback
Figure 6-3 shows the signal paths during a local loopback on an internal E1 port.
Internal E1
TDM PSN
Framer Mapper
Figure 6-3. Local Loopback on Internal E1 Port, Signal Paths
As shown in Figure 6-3, when a local loopback is activated on a local internal E1

port, the receive signal of the port is connected by the port E1 framer to the
input of the port transmit path. The signal is then returned toward the remote
side through the port packet processor, the remaining sections of the local
transmit path, and the link through the packet-switched network.
While the loopback is activated, the transmit signal arriving from the local end
user equipment is ignored, but the local E1 port continues to send the received
signal to the local end user equipment.
ETX-5 E1 Ports 6-11

To ensure that the remote equipment is capable of providing a good signal, the
local loopback should be activated on the local E1 port only after checking that
the remote end user’s equipment connected to the tested E1 port operates
normally while its own local loopback is activated.
While the local loopback is activated on the local port, the remote end user
equipment must receive its own signal, and thus it must be frame-synchronized.
This test fully checks the operation of the local E1 path serving the tested port; it
also checks the signal paths that end at the corresponding E1 port, including the
transmission through the packet network connecting the remote equipment to
ETX-5.
Remote Loopback
Figure 6-4 shows the signal paths during a remote loopback on an internal E1
port.
As shown in Figure 6-4 when a remote loopback is activated on an internal E1
port, the E1 framer of that port returns the transmit signal via the receive path of
the same port. The transmit signal is received from the local end user equipment
served by the tested port, through the corresponding E5-cTDM-4 or E5-cTDM-
STM4 card.
While the loopback is activated, the signal received from the remote E1 port is
ignored. The signal received from the local end user equipment remains
connected to the packet processor and it is transmitted to the remote E1 port.
To ensure that the user equipment is capable of providing a good signal, the
remote loopback should be activated on E1 port only after checking that the local
end user equipment operates normally while its own local loopback is activated.
Internal E1
TDM PSN
Framer Mapper
Figure 6-4. Remote Loopback on Internal E1 Port, Signal Paths
While the remote loopback is activated on the local E1 port, the local end user
This test checks the transmission path between the local end user equipment to
the local port, including the transmission plant and SDH equipment connecting
the user’s equipment to the ETX-5, and part of the internal ETX-5 signal path that
handle the routing of the signals up to the tested E1 port, including the SDH
mapper of the E5-cTDM-4 or E5-cTDM-STM4 card.
Configuring Internal E1 Interfaces

 To configure internal E1 parameters:
1. Navigate to configure port e1 <slot/port/tributary> to select the E1 port to
configure.
6-12 E1 Ports ETX-5

The config>port>e1>(slot/port/tributary)# prompt is displayed.

Note An internal E1 port becomes active only if an enabled pseudowire with a valid
cross-connection is assigned to the port.
Assigning short name <string> no name removes the name

description to port
Masking/unmasking no shutdown shutdown masks alarms generated by the

alarms generated by the internal E1. When the E1 interface is
internal E1 disabled, it sends AIS downstream.
Specifying E1 framing line-type {unframed | g732n When using one of the framed modes, you
mode | g732n-crc} select specific timeslots for transport by
configuring the appropriate bundle at the
pwe# prompt.
The specific timeslots are selected using the
pw-tdm command at the cross-connect#
prompt.
Enabling/disabling pm-enable no pm-enable disables PM data collection

performance monitoring no pm-enable
data collection
Setting path CV, ES, SES, path-interval-threshold [cv <cv-value 0–

SEFS, CSS and UAS 16383>] [es <es-value 0–900>] [ses <ses-
counter value during a value 0–900>] [sefs <sefs-value 0–900>]
15-min interval starting [css <css-value 0–900>] [uas <uas-value
from which a trap is sent 0–900>]
Specifying the code idle-code { 00 to FF (hexa) } This parameter is valid for framed modes
transmitted to fill unused only.
timeslots in E1 frames Only one idle code value is allowed per the
E5-cTDM-4 and E5-cTDM-STM4 card.
Selecting the code out-of-service <00–FF> The hexadecimal number is in the range of 0
transmitted during to FF (two digits).
out-of-service period The selected out-of-service code is also
sent, instead of the external data stream,
during out-of-service periods when the
unframed mode is used.
Only one out-of-service code value is
allowed per the E5-cTDM-4 or E5-cTDM-
STM4 card.
Controls the propagation trail-mode {terminated | extended} See Alarm Indications and Fault Propagation
of alarm indications in the TDM Pseudowires of Chapter 8
ETX-5 E1 Ports 6-13

Selects the reference tx-clock-source {domain <domain-num> | Tx clock setting becomes active only after a
source used by the loopback | pw } E1 port is disabled and enabled (shutdown
transmit path of this port > no shutdown).
If an E1 port is assigned to a PW, reset
(disable and enable) the PW after any
change in the tx-clock-source parameter.
Activating diagnostic loopback { local | remote } [ duration <0– Loopback duration is within 0 (forever) –
loopback 86400>] 86400 second range.
no loopback no loopback deactivates loopback.
Displaying port status show status See Displaying Status
Displaying port statistics show statistics See Displaying Statistics
Displaying Status
You can display current status of any internal E1 port on an E5-cTDM-4 or E5-
cTDM-STM4 card.
 To display E1 port status:

• At the config>port>e1(slot/port/tributary)#prompt, enter show status.
The E1 port status is displayed.
ETX-5>config>port>e1(1/1/1)# show status
Name : E1-1-1-1
Administrative Status : Down
Loopback : Off
The E1 interface status screens provide information on the port name,
administrative/operational status, and loopback status.
Internal E1 ports of ETX-5 collect performance monitoring data at the path level.
 To display the internal E1 port statistics:

1. Verify that statistics collection is enabled (pm-enable) for the E1 port.
2. At the prompt config>slot>port>e1 (<slot/port/tributary>)#, enter show
statistics followed by parameters listed below.
E1 statistics are displayed. The counters are described in Table 6-10.
6-14 E1 Ports ETX-5

Displaying statistics show statistics {current | interval <interval- • current –Displays the current
num 1..96> | current-day | previous-day | interval statistics
all-intervals | all} • interval (1–96) – Displays
statistics for a selected interval
• current-day – Displays statistics
for current day starting from
12:00 midnight
• previous-day – Displays statistics
for 24 hours before last 12:00
midnight
• all-intervals – Displays statistics
for all existing intervals (up to
96)
• all –Displays all statistics in
succession: current > all intervals
> current day > previous day
ETX-5300A>config>port>e1(4/1/1)# show statistics current

Current
---------------------------------------------------------------
Time Elapsed (Sec) : 0
Valid Intervals : 0
Path
---------------------------------------------------------------
CV : 0 UAS : 0
ES : 0 FC : 0
BES : 0
SES : 0
SEFS : 0
Note
For unframed E1 ports, only FC counter is available.
Table 6-4. Internal E1 Statistics
CV Number of CRC-4 errors
ES Number of seconds during which at least one FE or CS was detected or a SEF defect or
an AIS defect was present
UAS Number of seconds for which the E1 path is unavailable. The E1 path becomes
unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in
unavailable time. Once unavailable, the E1 path becomes available at the onset of 10
contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from
unavailable time.
BES Number of seconds during which at least 2 and no more than 804 CRC-4 errors were
detected while neither OOF nor AIS defects were present.
ETX-5 E1 Ports 6-15

FC Number of E1 path failure events. A failure event begins when a LOF failure or an AIS
failure is declared, and ends when the failure is cleared. A failure event that begins in
one period and ends in another period is counted only in the period in which it begins.
SES Number of seconds during which 805 or more CRC-4 errors were detected or an OOF
defect was present
SEFS Number of seconds during which at least one OOF defect or an AIS defect was present
 To clear statistics:
• At the prompt config>slot>port>t1 (<slot/port/tributary>)#, enter
clear-statistics.
Testing Internal E1 Ports

Diagnostic tools at the E1 level include local and remote loopback for checking
connections to E1 ports.
Running Loopbacks
ETX-5 supports activation of local and remote loopbacks at the E1 level. You can
initiate a local loopback on a single E1 port and remote loopbacks on any number
of E1 ports on an E5-cTDM-4 or E5-cTDM-STM4 card at a time. E1 Port
Diagnostics section above details signal paths when local and remote loopbacks
are activated.
 To activate a loopback:
1. Navigate to configure port e1 <slot/port/tributary> to select the E1 port to
test.
The config>port>e1>(slot/port/tributary)# prompt is displayed.
2. At the config>port>e1>(slot/port/tributary)# prompt, enter loopback,
followed by loopback type (local or remote) and its duration 0–86400 sec.
 To deactivate a loopback:
• In the config>port>e1>(slot/port/tributary)# prompt, enter no loopback.
Example
 To configure internal E1 interface:
• E1 name – e1_1_1_1
• Line type – G.732N
• Idle code – 0xFF
• Transmit clock source – Loopback
• Performance monitoring is enabled
• Administratively enabled.
6-16 E1 Ports ETX-5

ETX-5# configure port e1 1/1/1

ETX-5>config>port>e1(1/1/1)# name e1_1_1_1
ETX-5>config>port>e1(1/1/1)# line-type g732n
ETX-5>config>port>e1(1/1/1)# idle-code 0xFF
ETX-5>config>port>e1(1/1/1)# tx-clock-source loopback
ETX-5>config>port>e1(1/1/1)# pm-enable
ETX-5>config>port>e1(1/1/1)# no shutdown
ETX-5 E1 Ports 6-17

Table 6-5 below lists messages generated by ETX-5 when a configuration error is
detected.
Message Description
Cannot change line type when service is Line type cannot be changed if a pseudowire service has been
defined defined on a port
Cannot change loopback type, disable Loopback type cannot be changed while the loopback is active
the loopback first
Invalid CV threshold value CV threshold value is out of range (0–16383)
Invalid ES threshold value ES threshold value is out of range (0–900)
Invalid SES threshold value SES threshold value is out of range (0–900)
Invalid SEFS threshold value SEFS threshold value is out of range (0–900)
Invalid CSS threshold value CSS threshold value is out of range (0–900)
Invalid UAS threshold value UAS threshold value is out of range (0–900)
Invalid LES threshold value LES threshold value is out of range (0–900)
Invalid Dsx1IdleCode value Invalid idle code value
Invalid loopback timeout value Loopback duration value is out of range (0–86400 sec)
6.3 Ethernet Ports

This section details the configuration procedure for Ethernet ports located on the
main and I/O cards, including out-of-band management port.
GbE ports on E5-GBE-20 card can host up to ten unmanaged smart SFPs for
Ethernet over TDM (MiRICi-E1/T1 or MiRICi-E3/T3) or pseudowire (MiTOP-E1/T1 or
MiTOP-E3/T3) functionality.
Standards and MIBs

IEEE 802.3, RFC 4836, RFC 3635
LLDP Benefits
Ethernet interfaces located on the E5-MC-4, E5-MC-SFP-P-4, E5-GBE-20 and E5-
10GBE-2 cards provide high-speed connection to GbE and 10GbE networks using
fiber optic (SFP/SFP+/XFP) or copper RJ-45 ports.
Factory Defaults
By default, Ethernet ports are not enabled.
6-18 Ethernet Ports ETX-5

Autonegotiation
The speed and duplex mode of an Ethernet interface is set either manually by the
operator or negotiated with the peer interface. The autonegotiation procedure
enables automatic selection of the operating mode on a LAN. It allows equipment
connecting to an operating LAN to automatically adopt the LAN operating mode
(if it is capable of supporting that mode). In ETX-5 all Ethernet ports operate in
full duplex mode only.
When autonegotiation is disabled, the user must manually define MAU (Medium
Attachment Unit) type. The port ‘MAU Type’ parameter determines if the port is
1G or 10GbE. The default ‘MAU Type is 10GbE. Changing the MAU type can be
done only if the port is in ‘shutdown’ mode.
Note A port can have a No shutdown status only if it’s MAU type is the same as the
second port MAU Type (ONLY if the second port is in ‘no shutdown’, otherwise
‘no shutdown’ is allowed with no limitation).
Flow Control
A flow control is a mechanism that allows an Ethernet receiving end that is
unable to process all the traffic sent to it, to hold the transmitted traffic until it is
able to process packets again.
The mechanism uses a PAUSE frame, which is a packet that instructs the far-end
device to stop transmission of packets until the receiver is able to handle traffic
again. The PAUSE frame includes a timer value (set by the originating receiver),
which tells the far-end device how long to suspend transmission. If that timer
expires or is cleared by getting a PAUSE frame whose timer value is set to 0, the
far-end device can then send packets again. Flow control is an optional port-level
parameter.
Flow control is supported on both directly- and indirectly-attached ports:
• Directly-attached ports support symmetrical flow control (both Rx and Tx)
• Indirectly-attached ports support Rx flow control only, without issuing Tx
PAUSE frames (asymmetric flow control).
When autonegotiation is enabled, flow control mode is negotiated and a port
advertises its user-selected flow control capabilities to the peer. The actual flow
control mode, as well as duplex mode and transmission speed are set after the
negotiation is completed.
When autonegotiation is disabled, the flow control mode is manually selected by
the user.
All ETX-5 Ethernet interfaces, except the OOB management port, support flow
control.
Frame Format
ETX-5 supports Ethernet II frames. It does not support IEEE 802.3 LLC packets.
ETX-5 Ethernet Ports 6-19

Jumbo Frames
All Ethernet ports, except out-of-band management port, support jumbo frames
(12 kbytes). The OOB management port accepts frames of up to 1518-byte size.
Ethertype
Ethertype configured per-port is used for identification of VLAN-tagged frames at
ingress and Ethertype stacking at egress. This refers to 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). See the Ethertype section in Chapter 8 for
details.
L2CP Handling
ETX-5 handles Layer-2 control protocol traffic on a per-port and/or per-flow
basis. If no per-flow L2CP profile is configured, per-port-level profile is used. It
affects both tagged and untagged L2CP frames.
L2CP traffic is processed using a two-stage mechanism comprising per-port or
per-flow profiles (set of rules for traffic handling). In total, ETX-5 supports up to
16 L2CP profiles:
• Up to 4 (including default) port-level and a single flow-level profile can be
defined on directly-attached ports
• Up to 32 different addresses/protocols selected per L2CP profile.
If no default action is configured for unspecified address or protocol, this traffic
is tunneled.
Note If an L2CP profile has been attached to a port or a flow, the profile cannot be
deleted or modified.
See the Layer 2 Control Protocol (L2CP) section in Chapter 8 for details.
Classification Key
The ingress traffic is first classified into flows according to classification profiles.
A per-port classifier key configuration defines which types of classification
profiles are supported for this type of port. The classifier key also defines the
CoS mapping and color mapping methods.
See the Classification section in Chapter 8 for details.
Queue Group Profile

Queue group profiles are the largest entities used in pre- and post-forwarding
traffic management. They are attached to physical ports and consist of queue
block and shaper profiles. See the Quality of Service (QoS) section in Chapter 8
for details.

Configuring Ethernet Ports

 To configure the Ethernet port parameters:
1. Navigate to configure port ethernet <slot/port> to select the Ethernet port to
configure.
2. For configuring Ethernet out-of-band management port, navigate to
configure port mng-ethernet.
The config>port>mng-eth# prompt is displayed.
Assigning description to port name <string> no name removes the name

no name
Enabling autonegotiation auto-negotiation no auto-negotiation disables

no auto-negotiation autonegotiation.
Autonegotiation is not supported for 10GbE
ports.
Defining Ethernet interface type, mau-type { 10-t | 100-t | 1000- mau-type is also used to define SFP/XFP
when autonegotiation is disabled t | 10-100-1000-t | 100-any | 1000- type
any | 10g-any | 100-fx | 1000-
sx | 1000-lx | 10g-sr | 10g-
lr | 10g-er }
Enabling flow control flow-control no flow-control disables flow control

no flow-control function
Setting maximum frame size (in bytes) egress-mtu <size> <64–12288> default packet size 1790
to transmit (frames above the Note:
specified size are discarded) The MTU can be set only on IO card ports.
The MTU on Main card ports is fixed to
12288 and cannot be changed.
Enabling transmitting of Sync-E clock tx-ssm no tx-ssm disables SSM egress

availability and quality via SSM
Assigning queue group profile to queue-group <queue- no queue-group removes queue group
Ethernet port group-profile-name> association
no queue-group
Defining classifier key for Ethernet classification-key {vlan | inner-

port vlan | p-bit | ip-precedence |
ip-dscp}
Setting the VLAN tagged frame tag-ethernet-type <0x0000-0xFFFF> This value must be either 8100 or the same
Ethertype (tag protocol identifier) as Ethertype value configured at chassis
level

Associating a Layer-2 control l2cp <l2cp-profile-name> Defines discarding or tunneling policy for
processing profile with the port no l2cp Layer-2 protocols. To enable LACP (LAG) on
the port, the port must have an untagged
flow with an L2CP profile defined at the
flow level that specifies peer action for MAC
0x02.
no l2cp removes association with L2CP
profile.
Associating a policer profile with the policer-profile <policer-profile-name> Policer profiles can be bound, unbound or
port no policer-profile replaced with another profile on-the-fly.
Policer profile with traffic type “all” cannot
be bound to an Ethernet port.
Policer profile with traffic type “unknown-
unicast” cannot be bound to Ethernet ports
on I/O cards.
no policer-profile removes association with
policer profile.
Restarting autonegotiation process restart-auto-negotiation
Enabling 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.
Controlling OAM EFM loopback loopback no loopback disables OAM EFM loopback.
no loopback This command is relevant for active OAM
EFM ports.
Displaying OAM EFM status show oam efm
Displaying OAM EFM statistics show oam efm statistics
Administratively enabling port no shutdown shutdown disables the port
Enabling/disabling performance pm-enable no pm-enable disables PM data collection

monitoring data collection no pm-enable
Displaying port status show status
Displaying port statistics show statistics
Displaying L2CP statistics Show l2cp-statistics (see Viewing L2CP

Statistics in Chapter 8)
Displaying SFP status show sfp-status
Clearing port statistic counters clear-statistics
Clearing SFP counters clear-sfp-counters

Displaying Port Status

You can display the current status of an Ethernet port on a main or I/O card.
 To display the Ethernet port status:

1. Navigate to config>port>eth(slot/port)#.
2. Type show status.
The port status is displayed, for example as follows:
ETX-5>config>port>eth(main-a/1)# show status
Name : GBE-5-1
Connector Type : XFP In
Actual Mau Type : 10G Based SR
Provisioned Mau Type : 10g-any
Auto Negotiation : Disabled
Flow Control : Disabled
MAC Address : 00-20-D2-AA-18-00
Ethernet ports of ETX-5 collect performance monitoring data.
 To display the Ethernet port statistics:

• At the prompt config>slot>port>eth(<slot/port>)#, enter show statistics
running.
Ethernet statistics are displayed. The counters are described in Table 6-6.
ETX-5>config>port>eth(1/1)# show statistics running

Running
---------------------------------------------------------------
Counter Rx Tx
Total Octets 0 0
Total Frames 0 0
Unicast Frames 0 0
Multicast Frames 0 0
Broadcast Frames 0 0
Jabber Frames 0 0
L2CP Discarded 0 0
OAM Discarded 0 0
ACL Discarded 0 0
FCS Error Frames 0 0

MAC Error Frames 0 0

MAC Overflow Frames 0 0
Too Short Frames 0 0
Discarded Frames -- 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
Too Long Frames 0 0
Table 6-6. Ethernet Statistic Counters (I/O Card Port)
Description
Parameter Note
Rx Tx
Total Frames Total number of received packets, Total number of transmitted

including packets with bad CRC, packets
and excluding short packets and
packets dropped due to Rx MAC
overflow
Total Octets Total number of received octets, Total number of transmitted

including FCS and bad packet octets
octets, and excluding framing bits
Unicast Frames Total number of received good Total number of transmitted good
unicast packets, excluding packets unicast packets
with bad CRC and short packets
Multicast Total number of received multicast Total number of transmitted good

Frames packets, excluding packets with multicast packets
bad CRC and short packets
Broadcast Total number of received Total number of transmitted good

Frames broadcast packets, excluding broadcast packets
packets with bad CRC and short
packets
Jabber Frames The number of received frames I/O card ports

that exceeded the maximum only
allowed packet size and contained
an CRC error, or were not well
formed
Discarded – The number of frames dropped in Not available

Frames Tx MAC for main card
ports
Error Frames Total number of received bad –

packets, including packets with

Description
Parameter Note
Rx Tx
L2CP Discarded The number of packets discarded – I/O card ports

by the L2CP processing mechanism only
OAM Discarded The number of packets discarded – I/O card ports

by the OAM processing mechanism only
ACL Discarded The number of packets discarded – I/O card ports

by the ACL processing mechanism only
FCS Error The number of received packets – I/O card ports

Frames with bad CRC only
MAC Error The number of packets discarded – I/O card ports

Frames in Rx MAC due to PHY error or only
incorrect packet termination, such
as badly formed packets
MAC Overflow The number of packets discarded –

due to the FIFO overflow
Too Short The number of received well- – Not available

Frames formed frames that were less than for OOB
64 octets long, excluding framing management
bits and including FCS octets port
64 Octets Total number of received packets Total number of transmitted Not available
(including bad packets) that were packets (including bad packets) for OOB
64 octets in length, excluding that were 64 octets in length, management
framing bits and including FCS excluding framing bits and port
octets including FCS octets
65–127 Octets Total number of received packets Total number of transmitted Not available
65–127 octets in length, excluding that were 65–127 octets in management
framing bits and including FCS length, excluding framing bits and port
octets including FCS octets
128–255 octets in length, that were 128–255 octets in management
excluding framing bits and length, excluding framing bits and port
including FCS octets including FCS octets
512–1023 Total number of received packets Total number of transmitted Not available
Octets (including bad packets) that were packets (including bad packets) for OOB

Description
Parameter Note
Rx Tx
1024–1518 Total number of received packets Total number of transmitted Not available
1519-2047 Total number of received packets Total number of transmitted Not available
2048-Max Total number of received packets Total number of transmitted Not available
2048 to maximum allowed size that were 2048 to maximum management
octets in length, excluding framing allowed size octets in length, port
bits and including FCS octets excluding framing bits and
including FCS octets
Too Long Total number of received packets Total number of transmitted Not available
Frames that exceeded the maximum packets that exceeded the for OOB
allowed packet size maximum allowed packet size management
port
 To clear port statistics:

• At the prompt config>slot>port>eth(<slot/port>)#, enter clear-statistics.
Displaying Optical Link SFP/XFP Status

For viewing the status of the optical link SFP/XFP, follow the instructions below.
 To view the status of a local optical link SFP/XFP:

1. Navigate to port ethernet (<slot>/<port>)#
2. Type show sfp-status.
The status is displayed, for example as follows:
ETX-5>config>port>eth(main-a/1)# show sfp-status
SFP
---------------------------------------------------------------
Detailed Status : No Defect
Connector Type : LC
Transceiver Code : 10GBASE-SR
Vendor Name : SOURCEPHOTONICS
Vendor Part Number : XPXESRCDFA

Vendor Revision : 1a
Vendor Serial Number : B9A2005955
Enhanced Monitoring : Yes
Typical Maximum Range (Meter) : 15000
Wave Length (nm) : 850
Fiber Type : MM
SFP
---------------------------------------------------------------
Current Minimum Maximum
RX Power (dBm) : -8.2 -8.2 -7.9
TX Power (dBm) : -2.4 -2.4 -2.1
Laser Bias (mA) : 1.3 1.2 1.3
Laser Temperature (Celsius) : 32.4 18.0 32.5
Power Supply (V) : 3.2 3.2 3.2
Table 6-7 explains the parameters of the SFP installed for selected link port.
Table 6-7. Link SFP/XFP Parameters
Detailed Status SFP/XFP status
Connector Type SFP/XFP connector type
Transceiver Code SFP/XFP transceiver mode
Vendor Name The original manufacturer’s name
Vendor Part Number The original vendor’s part number
Vendor Revision The original vendor’s firmware revision
Vendor Serial Number The original vendor’s serial number
Enhanced Monitoring Enhanced SFP/XFP monitoring support
Typical Maximum The maximum range expected to be achieved over typical optical fibers, in meters
Range (Meter)
Wave Length (nm) The exact operating wavelength of the SFP/XFP, in nm
Fiber Type The type of optical fiber for which the SFP/XFP is optimized: SM (single mode) or MM
(multimode)
RX Power (dBm) The current optical power, in dBm, received by the SFP/XFP
TX Power (dBm) The current optical power, in dBm, transmitted by the SFP/XFP
Laser Bias (mA) The measured laser bias current, in mA
Laser Temperature The measured laser temperature, in °C

(Celsius)
Power Supply (V) The SFP/XFP power supply voltage

 To reset SFP counters:

• At the prompt config>slot>port>eth(<slot/port>)#, enter clear-sfp-counters.
Example
 To configure Ethernet interface:
• Port – port 2 on main card A
• Autonegotiation – enabled
• Classification key – VLAN
• L2CP profile – l2cp_prof_1
• Queue group profile – queue_group_1
ETX-5# configure port eth main-a/2
ETX-5>config>port>eth(main-a/2)# auto-negotiation
ETX-5>config>port>eth(main-a/2)# classification-key vlan
ETX-5>config>port>eth(main-a/2)# l2cp l2cp_prof_1
ETX-5>config>port>eth(main-a/2)# queue-group queue_group_1
ETX-5>config>port>eth(main-a/2)# pm-enable
ETX-5>config>port>eth(main-a/2)# no shutdown
Port Loopback
ETH Port level loopback is supported, and applies for the following ports:
• 1GbE IO card
• Main Card
This is a PHY-level loopback.
• Local loopback is supported (ETH Tx looped back into the PSN).
• Remote loopback is supported (ETH Rx looped back toward ETH line)
The loopback is timed per a configurable value. When initiated it affects the
‘TEST’ LED. Events Loopback on/off is supported
CLI: 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 disabled
• Loopback is released after device reset
Note Port loopback does not work on 10GbE Ethernet IO card.
detected.

Message Description
Autonegotiation enabled not allowed for Autonegotiation cannot be enabled for 10GbE ports
10G port
Invalid MAU type for 10G port Invalid MAU type has been selected for a 10GbE port
Invalid MAU type for SFP port Invalid MAU type has been selected for an SFP port
Invalid MAU type for UTP port Invalid MAU type has been selected for a UTP port
Invalid MAU type for autonegotiation Autonegotiation must be disabled for 100BaseFX interfaces
enabled
Invalid MAU type for autonegotiation Autonegotiation must be enabled for 1000BaseBT interfaces
disabled
Modify failed: Ethertype tag value is in The Ethertype cannot be changed if an active flow is attached to
use the port
Invalid port Ethertype tag value The selected default Ethertype value is different from 0x8100 or
the second Ethertype value is equal to 0x8100
Max number of allowed Ethertype tag Only two Ethertype values (default and another one) are
values has been exceeded allowed
Cannot delete default Ethertype tag The default Ethertype value 0x8100 cannot be deleted
value
Delete failed: Ethertype tag value is in The Ethertype value cannot be deleted because it is use by
use another port
6.4 SDH/SONET Ports

Four SDH/SONET ports located on the E5-cTDM-4 and E5-cTDM-STM4 cards serve
for terminating STM-1/OC-3 links and their overheads.
Standards and MIBs

Telcordia GR-253-CORE (issue 4 December 2005), ITU-T G.707/Y.1322 (01/2007),
JT-G707, ITU-T G.783 (03/2006), ITU-T G.784 (03/2008),
ATIS-0300231.04.2003(2007), ITU-T G.828 (03/2000), ITU-T G.829 (12/2002),
RFC 359.
Benefits
TDM ports provide access to SDN/SONET networks at STM-1 and OC-3 levels
(155.520 Mbps), and STM-4 and OC-12 levels (622.080Mbps), using fiber optic
SFP ports.
In addition, the SDH/SONET interface operation can be configured to comply with
the TTC standard requirements (STM-1J).
ETX-5 SDH/SONET Ports 6-29

Factory Defaults
ETX-5 is supplied with all SDH/SONET ports disabled. Other parameter defaults
are listed in the table below.
j0-pathtrace string 0x01 (SONET), www.rad.com (SDH)
j1-pathtrace string 0x00
j2-pathtrace string 0x00
overhead-mode itu-ansi
loopback disabled
tx-ssm disabled
ber-threshold eed e-3
ber-threshold sd e-6
The TDM interfacing subsystem provides interfaces to the TDM user equipment or
network. The physical STM-1/OC-3 and STM-4/OC-12 ports support many types of
SFP transceivers with optical interfaces to meet a wide range of operational
requirements.
SDH Implementation Principles

This section describes the implementation principles for the Synchronous Digital
Hierarchy (SDH), as background for the detailed presentation of the SDH signal
structures. The descriptions of SDH networks use the following terms:
• Network node. An SDH network node is a facility at which signals built in
accordance with the SDH frame structure are generated and/or terminated. A
network node is thus a convenient access point to add or drop payload
signals; for example, PDH tributary signals, for transmission over the SDH
network.
• SDH transport system. An SDH transport system provides the technical means
to transfer SDH signals between two network nodes.
• SDH network. An SDH network is formed by interconnecting the required
number of network nodes by means of SDH transport systems.
Basic SDH Principles

The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two
principles:
• Direct synchronous multiplexing of individual tributary signals within the
structure of the higher-rate multiplexed signal.
6-30 SDH/SONET Ports ETX-5

• Transparent transporting of each individual tributary signal through the

network, without any disassembly except at the two network nodes that
exchange information through that particular signal.
To enable synchronous multiplexing, SDH equipment is designed to permit
efficient and reliable synchronization of the entire network to a single timing
reference.
Direct Multiplexing Approach

Direct multiplexing means that individual tributary signals can be inserted into the
SDH multiplexed signal and removed without intermediate multiplexing and
demultiplexing steps. This capability results in the following characteristics:
• Efficient signal transport, because the same SDH transport system can carry
various types of payloads (tributary signals).
• Flexible routing, because any tributary can be inserted into the SDH signal
and removed as a single unit, without any effect on the other tributary
signals carried by the same SDH signal. This permits the building of
cost-effective add/drop multiplexers, the key component of flexible networks,
instead of implementing digital cross-connect systems as entities separated
from multiplexing equipment.
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore gives the network operator full control
over all the operational aspects of SDH networks and equipment units. This
overhead permits the integration of the network management and maintenance
functions within the transport network itself.
General Structure of SDH Signals

The SDH signal is a serial signal stream with a frame structure. Figure 6-5 shows
the general structure of SDH signals.
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure. Each SDH frame starts with framing bytes, which enable
equipment receiving the SDH data stream to identify the beginning of each
frame. The location of the other bytes within this frame structure is determined
by its position relative to the framing byte.
The organization of the frame can be easily understood by representing the
frame structure as a matrix of cells arranged in N rows and M columns, where
each cell carries one byte. In accordance with this representation, the framing
byte appears in the top left-hand cell (the byte located in row 1, column 1),
which by convention is referred to as byte 1 of the SDH frame.

N x M Bytes
Order of
Transmission
F F F F
F B B
B B B
N x M Bytes 1
N Rows
2
Order of
Transmission
B B B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure 6-5. General Structure of SDH Signals
The frame bytes are transmitted bit by bit, sequentially, starting with those in the
top row (see arrow in Figure 6-5). After the transmission of a row is completed,
the bits in the next row are transmitted. Transmission within each row is from
left to right. After transmission of the last byte in the frame (the byte located in
row N, column M), the whole sequence repeats - starting with the framing byte
of the following frame.
SDH Frame Organization

As shown in Figure 6-6, an SDH frame comprises two distinct parts:
• Section Overhead (SOH)
• Virtual Container (VC).
F F F F
Path Overhead (One Column)
Section
Virtual Container
N Rows Overhead
(VC)
M Columns
Figure 6-6. SDH Frame Organization

Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type.
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
Virtual Container (VC)

The VC is an envelope (i.e., a special type of signal structure, or frame) that is
used to transport a tributary signal across the SDH network.
The path followed by a VC within the network may include any number of nodes;
therefore the VC may be transferred repeatedly from one SDH transport system
to another on its path through the network. Nevertheless, in most cases the VC is
assembled at the point of entry to the SDH network and disassembled only at
the point of exit.
Since the VC is handled as an envelope that is opened only at the path end
points, some of its signal carrying capacity is dedicated to path overhead. The
path overhead provides the facilities (e.g., alarm and performance monitoring),
required to support and maintain the transportation of the VC between the end
points.

VC Assembly/Disassembly Process
The concept of inserting a tributary signal into a virtual container for end-to-end
transport across a SDH network, is fundamental to the operation of SDH
networks. This process of inserting the tributary signal into the proper locations
of a VC is referred to as “mapping”.
In all SDH signal structures, the carrying capacity provided for each individual
tributary signal is always slightly greater than that required by the tributary rate.
Thus, the mapping process must compensate for this difference. This is achieved
by adding stuffing bytes, e.g., path overhead bytes, to the signal stream as part
of the mapping process. This increases the bit rate of the composite signal to the
rate provided for tributary transport in the SDH structure. In the TTC mode
(STM-1J), synchronous byte mapping is used.
At the point of exit from the SDH network, the tributary signal must be recovered
from the virtual container, by removing the path overhead and stuffing bits. This
process is referred to as “demapping”. After demapping, it is necessary to
restore the original data rate of the recovered tributary data stream.
STM-1/STM-4 Frame Structure

ETX-5 handles the base-level SDH signal, which is called Synchronous Transport
Mode Level 1 (STM-1). Figure 6-7 below shows the STM-1 frame structure.
2430 Bytes/Frame
Serial Signal
Stream
F F F F
155.52 Mbps
Path Overhead (9 Bytes)
STM-1 Virtual Container (VC-4)

Section
9 Rows Overhead
Container Capacity = 150.34 Mbps
Payload Capacity = 149.76 Mbps
9 Columns 260 Columns
1 Column
2430 Bytes/Frame x 8 Bits/Byte x 8000 Frames/sec = 155.52 Mbps
Figure 6-7. STM-1 Frame Structure
STM-1 frames are transmitted at a fixed rate of 8000 frames per second.
Note At a transmission rate of 8000 frames per second, each byte supports a data rate
of 64 kbps.
The STM-1 signal frame comprises 9 rows by 270 columns, resulting in a total
signal capacity of 2430 bytes (19440 bits per frame). Considering the STM-1
frame repetition rate, 8000 frames per second, this yields a bit rate of
155.520 Mbps.

The STM-1 frame comprises the following parts:

• Section Overhead. The STM-1 section overhead occupies the first nine
columns of the STM-1 frame, for total of 81 bytes.
• Virtual Container. The remaining 261 columns of the STM-1 frame, which
contain a total of 2349 bytes, are allocated to the virtual container. The
virtual container itself comprises a container for the payload signal (260
columns), preceded by one column of path overhead. The virtual container
carried in an STM-1 frame is referred to as a Virtual Container Level 4, or
VC-4. VC-4, which is transported unchanged across the SDH network,
provides a channel capacity of 150.34 Mbps.
The VC-4 structure includes one column (9 bytes) for the VC-4 path overhead,
leaving 260 columns of signal carrying capacity (149.76 Mbps). This carrying
capacity is sufficient for transporting a 139.264 Mbps tributary signal (the
fourth level in the PDH signal hierarchy). The VC-4 signal carrying capacity can
also be subdivided, to permit the transport of multiple lower-level PDH
signals.
Pointers
In Figure 6-7, the VC-4 appears to start immediately after the section overhead
part of the STM-1 frame.
Actually, to facilitate efficient multiplexing and cross-connection of signals in the
SDH network, VC-4 structures are allowed to float within the payload part of
STM-1 frames. This means that the VC-4 may begin anywhere within the STM-1
payload part. The result is that a given VC-4 typically begins in one STM-1 frame
and ends in the next.
Were the VC-4 not allowed to float, buffers would be required to store the VC-4
data up to the instant it can be inserted in the STM-1 frame. These buffers
(called slip buffers), which are often used in PDH multiplex equipment, introduce
long delays. Moreover, they also cause disruptions in case a slip occurs.
Identifying VC-4 Beginning in the STM-1 Frame

When a VC-4 is assembled into the STM-1 frame, a pointer (byte) located in the
section overhead of the STM-1 frame indicates the location of the first byte (J1)
of the VC-4 that starts in that STM-1 frame.
Using Pointers to Correct Timing Differences

SDH network are intended to operate as synchronous networks. Ideally, this
means that all SDH network nodes should derive their timing signals from a single
master network clock. However, in practical applications, network implementation
must accommodate timing differences (clock offsets). These may be the result of
an SDH node losing network timing reference and operating on its standby clock,
or it may be caused by timing differences at the boundary between two separate
SDH networks.
The VC-4 is allowed to float freely within the space made available for it in the
STM-1 frame; therefore phase adjustments can be made as required between the
VC-4 and the STM-1 frame.
To accommodate timing differences, the VC-4 can be moved (justified), positively
or negatively three bytes at time, with respect to the STM-1 frame. This is

achieved by simply recalculating and updating the pointer value at each SDH
network node. In addition to clock offsets, updating the pointer will also
accommodate any other adjustment required between the input SDH signal rate
and the timing reference of the SDH mode.
Pointer adjustments introduce jitter. Excessive jitter on a tributary signal degrades
signal quality and may cause errors. Therefore, SDH networks must be designed
to permit reliable distribution of timing to minimize the number of pointer
adjustments.
SDH Overhead Data
SDH Overhead Data Types

In SDH networks, a transmission path can include three equipment functions:
• SDH terminal multiplexer –performs the insertion/removal of tributary signals
into SDH frames
• SDH cross-connect switch – permits changing the routing of tributary signals
carried in SDH frames
• Regenerator – used to increase the physical range of the transmission path.
The resulting structure of an SDH transmission path is shown in Figure 6-8.
Multiplexer
Section Multiplexer Section
Regenerator Regenerator Regenerator

Section Section Section
Tributary Tributary
Signals Signals
.. SDH SDH ..
Terminal Terminal
. Multiplexer Multiplexer
.
SDH Cross-Connect
VC Path VC
Assembly Disassembly
Figure 6-8. Structure of Transmission Path in SDH Network
As shown in Figure 6-8, a transmission path can comprise three types of

segments:
• Multiplexer section – a part of a transmission path located either between a
terminal multiplexer and an adjacent SDH cross-connect equipment, or
between two adjacent SDH terminal multiplexers.
• Regenerator section – a part of a transmission path located either between a
terminal multiplexer or SDH cross-connect equipment and the adjacent
regenerator, or between two adjacent regenerators. A multiplexer section can
include up to three regenerator sections.
• Path – the logical connection between the point at which a tributary signal is
assembled into its virtual container, and the point at which it is disassembled
from the virtual container.

To provide the support and maintenance signals associated with transmission

across each segment, each of these segments has with its own overhead data,
hence three types of overhead data:
• Section overhead, carried in the first nine columns of the STM-1 frame:
 Multiplexer section (MS) overhead – carried in overhead rows 5 to 9
 Regenerator section (RS) overhead – carried in overhead rows 1 to 3
 AU pointers– carried in overhead row 4.
• Path overhead, carried in the first column of a VC-4. The path overhead
carried in the VC-4 is called high-order path overhead; see the SDH Tributary
Units section for a description of the low-order path overhead.
Figure 6-9 shows the detailed structure of the overhead data in STM-1 frames.
Path
Section Overhead Overhead
Framing Framing Framing Framing Framing Framing ID Path Trace

A1 A1 A1 A2 A2 A2 C1 J1
Regenerator
BIP-8 Orderwire User BIP-8
Section B1 E1 F1 B3
Overhead
(Rows 1 - 3)
DCC DCC DCC Signal Label
D1 D2 D3 C2
AU Pointers Pointer Pointer Pointer Pointer Pointer Path Status

(Row 4) H1 H2 H3 H3 H3 G1
BIP-24 APS APS

User Channel
B2 B2 B2 K1 K2 F2
DCC DCC DCC Multiframe

D4 D5 D6 H4
Multiplex
DCC DCC DCC
Section D7 D8 D9
Z3
Overhead
(Rows 5 - 9)
DCC DCC DCC
D10 D11 D12
Z4
Orderwire
Z1 Z1 Z1 Z2 Z2 Z2
E2
Z5
Bytes reserved for future use
Figure 6-9. Organization of STM-1 Overhead Data
Regenerator Section Overhead (RSOH)

A regenerator section of an SDH network comprises the transmission medium
and associated equipment either between a network element and the adjacent
regenerator, or between two adjacent regenerators. The associated equipment
includes the aggregate interfaces and SDH processing equipment which either
originates or terminates the regenerator section overhead.
The functions of the various bytes carried in the STM-1 regenerator section
overhead are described below.

Framing (A1, A2 Bytes)

The six framing bytes carry the framing pattern, and are used to indicate the start
of an STM-1 frame.
Channel Identifier (C1 Byte)

The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
Parity Check (B1 Byte)

An 8-bit wide bit-interleaved parity (BIP-8) checksum is calculated over all the bits
in the STM-1 frame, to permit error monitoring over the regenerator section. The
computed even-parity checksum is placed in the RSOH of the following STM-1
frame.
Data Communication Channel (D1, D2, D3 Bytes)

The 192 kbps Data Communication Channel (DCC) can be used to provide the
capability to transfer network management and maintenance information
between regenerator section terminating equipment.
Orderwire Channel (E1 Byte)

The E1 byte can be used to provide a local orderwire channel for voice
communications between regenerators and remote terminal locations.
User Communication Channel (F1 byte)

The F1 byte is intended to provide the network operator with a channel that is
terminated at each regenerator location, and can carry proprietary
communications.
The information transmitted on this channel can be passed unmodified through a
regenerator, or overwritten by data generated by the regenerator.
AU Pointers (H1, H2, H3 bytes)

The Administration Unit (AU) pointer bytes are used to enable the transfer of
STM-1 frames within STM-N frames, and therefore are processed by multiplexer
section terminating equipment. Separate pointers are provided for each STM-1
frame in an STM-N frame.
AU pointers link the section overhead and the associated virtual container(s).
Multiplexer Section Overhead (MSOH)

A multiplexer section of an SDH network comprises the transmission medium,
together with the associated equipment (including regenerators) that provide the
means of transporting information between two consecutive network nodes
(e.g., SDH multiplexers). One of the network nodes originates the multiplexer
section overhead (MSOH) and the other terminates this overhead.
The functions of the various bytes carried in the STM-1 multiplexer section
overhead are described below.

Parity Check (B2 Bytes)

A 24-bit wide bit-interleaved parity (BIP) checksum is calculated over all the bits
in the STM-1 frame (except those in the regenerator section overhead). The
computed checksum is placed in the MSOH of the following STM-1 frame.
Protection Switching (K1, K2 Bytes)

The K1 and K2 bytes carry the information needed to activate/deactivate the
switching between the main and protection paths on a multiplexer section.
Data Communication Channel (D4 to D12 Bytes)

Bytes D4 to D12 can be used to provide a 576 kbps data communication channel
(DCC) between multiplexer section termination equipment. This channel is used
to carry network administration and maintenance information.
Orderwire Channel (E2 Byte)

The E2 byte can be used to provide a local orderwire channel for voice
communications between multiplexer section terminating equipment.
Alarm Signals
Alarm information is included as part of the MSOH. These functions are explained
in the SDH Maintenance Signals and Response to Abnormal Conditions section
below.
VC-4 Path Overhead Functions

The path overhead (POH) is contained within the virtual container portion of the
STM-1 frame. The POH data of the VC-4 occupies all the 9 bytes of the first
column. The functions of the various bytes carried in the VC-4 path overhead are
described below.
Path Trace Message (J1 Byte)

The J1 byte is used to repetitively transmit a 64-byte string (message). The
message is transmitted one byte per VC-4 frame.
A unique message is assigned to each path in an SDH network. Therefore, the
path trace message can be used to check continuity between any location on a
transmission path and the path source.
Parity Check (B3 Byte)

An 8-bit wide bit-interleaved parity even checksum, used for error performance
monitoring on the path, is calculated over all the bits of the previous VC-4. The
computed value is placed in the B3 byte.
Signal Label (C2 Byte)

The signal label byte, C2, indicates the structure of the VC-4 container. The signal
label can assume 256 values, however two of these values are of particular
importance:
• The all “0”s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)

• The code “00000010 (0x02)” represents the Floating VT mode (SONET) or

TUG structure (SDH).
Path Status (G1 Byte)

The G1 byte is used to send status and performance monitoring information from
the receive side of the path terminating equipment to the path originating
equipment. This allows the status and performance of a path to be monitored
from either end, or at any point along the path.
Multiframe Indication (H4 byte)

The H4 byte is used as a payload multiframe indicator, to provide support for
complex payload structures, such as payload structures carrying multiple tributary
units (TUs – see the SDH Tributary Units section). If, for example, the TU
overhead is distributed over four TU frames, these four frames form a TU
multiframe structure. The H4 byte then indicates which frame of the TU
multiframe is present in the current VC-4.
User Communication Channel (F2 Byte)

The F2 byte can be used to support a user channel that enables proprietary
network operator communications between path terminating equipment.
Alarm Signals
Alarm and performance information is included as part of the path overhead.
These functions are explained in SDH Maintenance Signals and Response to
Abnormal Conditions.
SDH Tributary Units

The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the
transport of a fourth level (139.264 Mbps) PDH multiplex signal.
To enable the transport and switching of lower-rate tributary signals within the
VC-4, several special structures, called Tributary Units (TUs), have been defined.
The characteristics of each TU type have been specifically selected to carry one of
the standardized PDH signal rates. In addition, a fixed number of whole TUs may
be mapped within the container area of a VC-4.
Tributary Unit Frame Structure

The structure of the tributary unit frame is similar to the SDH frame structure.
With reference to Figure 6-6, the tributary unit frame also includes a section
overhead part and a virtual container part, which comprises a container and path
overhead.
In general, the tributary unit frame is generated in three steps:
• A low rate tributary signal is mapped into the TU “container”
• Low-path path overhead is added before the container, to form the
corresponding virtual container (VC-11, VC-12, VC-2 or VC-3, depending on
the TU type)
• A TU pointer is added to indicate the beginning of the VC within the TU
frame. This is the only element of TU section overhead.

The TU frame is then multiplexed into a fixed location within the VC-4.
Because of the byte interleaving method, a TU frame structure is distributed over
four consecutive VC-4 frames. It is therefore more accurate to refer to the
structure as a TU multiframe. The phase of the multiframe structure is indicated
by the H4 byte contained in the VC-4 path overhead.
Tributary Unit Types

As mentioned above, specific containers (C), virtual containers (VC) and
associated TU structures have been defined for each standard PDH multiplex
signal level. These structures are explained below:
• TU-11: Each TU-11 frame consists of 27 bytes, structured as 3 columns of
9 bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 1.728 Mbps and will accommodate the mapping of a North American DS1
signal (1.544 Mbps). 84 TU-11s may be multiplexed into the STM-1 VC-4.
of 2.304 Mbps and will accommodate the mapping of a CEPT 2.048 Mbps
signal. 63 TU-12s may be multiplexed into the STM-1 VC-4.
of 6.912 Mbps and will accommodate the mapping of a North American DS2
signal. 21 TU-2s may be multiplexed into the STM-1 VC-4.
of 49.54 Mbps and will accommodate the mapping of a CEPT 34.368 Mbps
signal or a North American 44.768 DS3 signal. Three TU-3s may be
multiplexed into the STM-1 VC-4.
Figure 6-10 illustrates the assembly (multiplexing) of TUs in the VC-4 structure,
for the specific case of the TU-12. For other multiplexing options, see
Figure 6-11.
2430 Bytes/Frame
Serial Signal
Stream
F F F F
155.52 Mbps
VC-4 Path Overhead
Section TU-12 TU-12 No.2 TU-12

9 Rows Overhead No. 1 to No. 63
TU-12 No.62
9 Columns 260 Columns
1 Column
Figure 6-10. VC-4 Carrying TU-12 Payload

As shown in Figure 6-10, 63 TU-12s can be packed into the 260 columns of
payload capacity (i.e., the C-4 container) provided by a VC-4. This leaves
8 unused columns in the C-4 container. These unused columns result from
intermediate stages in the TU-12 to VC-4 multiplexing process, and are filled by
fixed stuffing bytes.
SDH Multiplexing Hierarchy

Figure 6-11 shows a general view of the SDH multiplexing hierarchy. The
hierarchy illustrates both the European and North American PDH multiplex levels.
Figure 6-11 also shows the utilization of additional SDH signal structures:
• TUG: tributary unit group, is the structure generated by combining several
lower level tributaries into the next higher level tributary. For example, TUG-2
is generated by combining 3 TU-12 or 4 TU-11, and TUG-3 is generated by
combining 7 TUG-2.
• AU: administrative unit, is a structure that includes a VC and a pointer to the
beginning of the VC. For example, AU-3 contains one VC-3 and includes a
pointer to the beginning of the VC.
• AUG: administrative unit group, is the structure generated by combining
several lower level administrative units into the next higher level
administrative unit. For example, AUG for the STM-1 level is generated by
combining 3 AU-3 (several AUG can be combined for generating STM-N (N =
4, 16, etc.) structures).
Note For simplicity, reference is made only to VCs (the actual structure needed to
transport a VC can be found in the SDH or SONET multiplexing hierarchy).

STM-4 ×1 599.040 Mbps

AUG4 AU-4-4c VC-4-4c C-4-4c
(622.080 Mbps) (E4)
×4 ×1 139.264 Mbps
×1 AU-4 VC-4
C-4
(E4)
STM-1
AUG1
(155.520 Mbps) ×1
AU-3 VC-3
×3
44.736 Mbps
(DS3)
×3 VC-3
C-3
TU-3
×7
34.368 Mbps
×1 (E3)
TUG-
3
C-2 6.312 Mbps
TU-2 VC-2
×1 (DS2)
×7
×2 3.152 Mbps
VT3
TUG- (DS1C)
2
Legend ×4
TU-11 C-11
1.544 Mbps
VC-11
Pointer Processing (DS1)
×3
TU-12 C-12
2.048 Mbps
Mapping VC-12
(E1)
Figure 6-11. SDH Multiplexing Hierarchy
The flexibility of the SDH multiplexing approach is illustrated by the many paths
that can be used to build the various signal structures. For example, Figure 6-11
shows that the E1 signal is incorporated into STM-1/STM-4 signal using following
multiplexing paths:
• Each E1 signal is mapped into a VC-12, which is then encapsulated in a TU-12.
• Each group of 3 TU-12 is combined to obtain a TUG-2 (3 E1 signals per TUG-2.)
• Seven TUG-2 are combined to obtain one TUG-3 (21 E1 signals per TUG-3).
TUG-3 is carried in a VC-3.
• Three VC-3 are combined to generate one VC-4 (63 E1 signals per VC-4). The
STM-1 signal carries one VC-4.
• Four AUG-1 are combined to generate one AUG-4 (63 E1 signals per each
VC-4). The STM-4 signal carries four VC-4.
SDH Maintenance Signals and Response to Abnormal

Conditions
The maintenance signals transmitted within the SDH signal structure are
explained in Table 6-9.

Table 6-9. SDH Maintenance Signal Definitions
Signal Description
Loss of Signal (LOS) LOS defect is declared if an all zeros pattern is detected for more than 100 ms. If
an all-zeros pattern lasts 2.3 ms or less, a LOS defect is not declared. A LOS
defect is terminated if no 100 ms of zero pattern is detected during a 250 ms
period.
Out of Frame (OOF) OOF state entered when 4 or 5 consecutive SDH frames are received with invalid
(errored) framing patterns. Maximum OOF detection time is therefore 625 µs.
OOF state exited when 2 consecutive SDH frames are received with valid framing
patterns.
Loss of Frame (LOF) LOF state entered when OOF state exists for up to 3 ms. If OOFs are
intermittent, the timer is not reset to zero until an in-frame state persists
continuously for 0.25 ms.
LOF state exited when an in-frame state exists continuously for 1 to 3 ms.
Loss of Pointer (LOP) LOP state entered when N consecutive invalid pointers are received where N = 8,
9 or 10.
LOP state exited when 3 equal valid pointers or 3 consecutive AIS indications are
received.
Note
The AIS indication is an “all 1’s” pattern in pointer bytes.
Multiplexer Section AIS Sent by regenerator section terminating equipment (RSTE) to alert downstream
MSTE of detected LOS or LOF state. Indicated by STM signal containing valid
RSOH and a scrambled “all 1’s” pattern in the rest of the frame.
Detected by MSTE when bits 6 to 8 of the received K2 byte are set to “111” for
3 consecutive frames. Removal is detected by MSTE when 3 consecutive frames
are received with a pattern other than “111” in bits 6 to 8 of K2.
Far End Receive Failure Sent upstream by multiplexer section terminating equipment (MSTE) within
(FERF or MS-FERF) 250 µs of detecting LOS, LOF or MS-AIS on incoming signal. Optionally
transmitted upon detection of excessive BER defect (equivalent BER, based on B2
bytes, exceeds 10 ). Indicated by setting bits 6 to 8 of transmitted K2 byte to
-3
“110”.
Detected by MSTE when bits 6 to 8 of received K2 byte are set to “110” for 3
consecutive frames. Removal is detected by MSTE when 3 consecutive frames are
received with a pattern other than “110” in bits 6 to 8 of K2.
Transmission of MS-AIS overrides MS-FERF
AU Path AIS Sent by MSTE to alert downstream high order path terminating equipment (HO
PTE) of detected LOP state or received AU Path AIS. Indicated by transmitting “all
1’s” pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when “all 1’s” pattern is received in bytes H1 and H2 for 3
consecutive frames. Removal is detected when 3 consecutive valid AU pointers
are received

Signal Description
High Order Path Remote Generated by high order path terminating equipment (HO PTE) in response to
Alarm Indication received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
(HO Path RAI, also known POH G1 byte to “1”.
as HO Path FERF) Detected by peer HO PTE when bit 5 of received G1 byte is set to “1” for 10
consecutive frames. Removal detected when peer HO PTE receives 10
consecutive frames with bit 5 of G1 byte set to “0”
TU Path AIS Sent downstream to alert low order path terminating equipment (LO PTE) of
detected TU LOP state or received TU path AIS. Indicated by transmitting “all 1’s”
pattern in entire TU-1, TU-2 and TU-3 (i.e., pointer bytes V1-V3, V4 byte, plus all
bytes of associated VC-1, VC-2 and VC-3 loaded by “all 1’s” pattern).
Detected by LO PTE when “all 1’s” pattern received in bytes V1 and V2 for 3
consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Note
TU Path AIS is only available when generating and/or receiving “floating
mode” tributary unit payload structures.
Low Order Path Remote Generated by low order path terminating equipment (LO FTE) in response to
Alarm Indication received TU Path AIS. Sent upstream to peer LO PTE.
(LO Path RAI, also known Indicated by setting bit 8 of LO POH V5 byte to “1”.
as LO Path FERF)
Detected by peer LO PTE when bit 8 of received V5 byte is set to “1” or 10
consecutive multiframes. Removal detected when peer LO PTE receives 10
consecutive multiframes with bit 8 of V5 byte set to “0”.
Note
LO Path RAI is only available when generating and/or receiving “floating
mode” tributary unit payload structures.
This section describes the response to the various conditions that can be
detected by the maintenance functions built into the SDH frames, and the flow
of alarm and indication signals.
Figure 6-12 provides a graphical representation of the flow of alarm and
indication signals through an SDH transmission path.

Low Order Path
High Order Path
Multiplexer Section
Regenerator Regenerator
Section Section
LO PTE HO PTE MS TE RS TE MS TE HO PTE LO PTE

LOP LOP LOP
LOS LOS
LOF LOF
Tributary
AIS (X2) AIS AIS AIS
(H1H2) (V1V2)
FERF
(X2)
RAI RAI (G1)
(G1)
RAI
(VS) RAI (VS)
B1(BIP-8) B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE FEBE
(G1)
(G1)
BIP-2
(VS)
FEBE FEBE
(VS) (VS)
Legend
Collection LO Low Order PTE Path Terminating Equipment
Transmission HO High Low Order RS TE Regenerator Section Terminating Equipment
Generation MS TE Multiplexer Section Terminating Equipment
Figure 6-12. Flow of Alarm and Indication Signals through an SDH Transmission
Path
Flow of Alarm and Response Signals

The major alarm conditions, such as Loss of Signal (LOS), Loss of Frame (LOF),
and Loss of Pointer (LOP), cause various types of Alarm Indication Signals (AIS) to
be transmitted downstream.
In response to detection of AIS signals and detection of major receiver alarm
conditions, other alarm signals are sent upstream to warn of trouble
downstream:
• Far End Receive Failure (FERF) is sent upstream in the multiplexer overhead
after multiplexer section AIS, or LOS, or LOF has been detected by equipment
terminating in a multiplexer section span;
• A Remote Alarm Indication (RAI) for a high order path is sent upstream after
a path AIS or LOP condition has been detected by equipment terminating a
path

• A Remote Alarm Indication (RAI) for a low order path is sent upstream after a
low order path AIS or LOP condition has been detected by equipment
terminating a low order path.
Performance monitoring at each level in the maintenance hierarchy is based on
the use of the byte interleaved parity (BIP) checksums calculated on a frame by
frame basis. These BIP checksums are sent downstream in the overhead
associated with the regenerator section, multiplexer section and path
maintenance spans.
In response to the detection of errors using the BIP checksums, the equipment
terminating the corresponding path sends upstream Far End Block Error (FEBE)
signals.
SONET Environment
SONET (Synchronous Optical Network) is an alternative standard to SDH, widely
used in North America and other parts of the world. SONET uses implementation
principles and even frame structures that are very similar to those used by SDH.
Therefore, the following description is based on the information already
presented for SDH.
Figure 6-13 shows the SONET multiplexing hierarchy.
STS-12 ×1 ×1 STS-12c 599.040 Mbps

STS-12 STS-12c SPE
(622.080 Mbps)
139.264 Mbps
×1 STS-3c ×1 STS-3c
STS-3 (E4)
STS-3 SPE
(155.520 Mbps)
×3 ×3
44.736 Mbps
(DS3)
VT6
VT6 6.312 Mbps
SPE (DS2)
×1
×2 VT3 3.152 Mbps

VT3
STS-1 SPE (DS1C)
SPE ×7 VT
STS-1 Group
Legend
×4 VT1.5 1.544 Mbps
VT1.5
SPE (DS1)
Pointer Processing
×3
VT2 2.048 Mbps
Mapping VT2
SPE (E1)
Figure 6-13. SONET Multiplexing Hierarchy
The main signal structures in the SONET hierarchy are designated as follows:
• Containers are replaced by synchronous payload envelopes (SPE) for the
various virtual tributaries (VTs)

• Virtual containers (VCs) are replaced by virtual tributaries (VTs); however the
rates are similar to those used in the SDH hierarchy
• Tributary unit groups (TUGs) are replaced by virtual tributary groups
• The VC-3 level is replaced by the Synchronous Transport Signal level 1
(STS-1), and has the same rate (51.840 Mbps).
• 3 STS-1 can be combined to obtain one Synchronous Transport Signal level 3
(STS-3) at the same rate as STM-1 (155.520 Mbps). The corresponding
optical line signal is designated OC-3.
• 12 STS-1 can be combined to obtain one Synchronous Transport Signal level
12 (STS-12) at the same rate as STM-4 (622.080 Mbps). The corresponding
optical line signal is designated OC-12.
SDH/SONET Port Diagnostics

Diagnostic tools at the STM-1/OC-3 and STM-4/OC-12 level include local and
remote loopback for checking connections to TDM ports.
Remote Loopback
The recovered STM-1/OC-3 and STM-4/OC-12 receive signal provided by the
STM-1/OC-3 and STM-4/OC-12 transceiver of the tested port is returned by the
remote loopback toward the equipment connected to the local STM-1/OC-3 or
STM-4/OC-12 port. The loopback is activated at the line side of the STM-1/OC-3
or STM-4/OC-12 framer serving the tested port.
Figure 6-14 shows the signal paths when a remote loopback is activated.
E5-cTDM-4 Card
RX
Transceiver Framer
TX
RX
Transceiver Framer
TX
Figure 6-14. Remote Loopback
The test signal is provided by the equipment connected to the local STM-1/OC-3
or STM-4/OC-12 port, that must receive its own transmission. While the loopback
is activated, the local STM-1/OC-3 or STM-4/OC-12 port continues sending the
received payload to the ETX-5 transmit path, for transmission through the packet
network to the equipment at the remote end of the link.
This test checks the connections to the local STM-1/OC-3 or STM-4/OC-12 port,
including the transmission plant connecting the local equipment to the E5-cTDM-
4 or E5-TDM-1 card, and the STM-1 transceiver of the E5-cTDM-4 or E5-TDM-1
card.

Local Loopback
The local loopback connects the STM-1/OC-3 or STM-4/OC-12 transmit signal
generated by the STM-1/OC-3 or STM-4/OC-12 framer of the tested port, to the
receive input of the framer. This returns the STM-1/OC-3 or STM-4/OC-12 signal
toward the equipment at the remote end of the link.
Figure 6-15 shows the signal paths when a local loopback is activated.
E5-cTDM-4 Card
RX
Transceiver Framer
TX
RX
Transceiver Framer
TX
Figure 6-15. Local Loopback
While the loopback is activated, the local STM-1/OC-3 port continues sending the
transmit signal to the STM-1/OC-3 or STM-4/OC-12 line.
The test signal is provided by the remote equipment whose payload is routed to
the tested STM-1/OC-3 or STM-4/OC-12 port; that equipment must receive its
own transmission.
This test fully checks the operation of the local STM-1/OC-3 or STM-4/OC-12 port,
except for the STM-1/OC-3 or STM-4/OC-12 line interface (transceiver). It also
checks the ETX-5 signal paths that end at the corresponding STM-1/OC-3 or
STM-4/OC-12 port, including the transmission through the packet network
connecting the remote equipment to ETX-5.
Configuring SDH/SONET Interfaces

 To configure external SDH/SONET parameters:
1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to configure.
The config>port>sdh-sonet>(slot/port)# prompt is displayed.
Defining the administrative unit aug <aug number> AUG is relevant for SDH modes. See
group (AUG) Configuring AUG/OC-3 below.
Assigning short description to name <string> no name removes the name

port no name

Setting the type of operation in frame-type {sdh | sonet} frame-type parameter is included for
accordance with the SDH or information only. Interface type is
SONET standards selected when a TDM module is defined
in chassis slot.
Controlling EED response eed-action [ { soh } ] [ { EED response is enabled for SOH, path
(sending AIS downstream and path } ] [ { vt } ] and VT levels
RDI upstream) no eed-action
Defining transmitted and j0-pathtrace [ {tx-string <tx- When TIM monitoring is enabled and
expected section trace labels trace-string> ] [exp-string ETX-5 receives J0 trace string that is
(carried in byte J0 of the <exp-string>}] different from the expected one, it
SOHoverhead) declares section TIM defectETX-5
*In SONET mode [0-0xFF]
Activating diagnostic loopback loopback { local | remote } Loopback duration is within 0 (forever) -
[ duration <0-86400>] 86400 second range.
no loopback no loopback deactivates the loopback.
Controlling TIM response tim-action [ { soh } ] [ { path TIM response is enabled for EOH, path
(sending AIS downstream and } ] [ { vt } ] and VT levels
RDI upstream) no tim-action
Defining STM-1 frame overhead overhead-mode { itu-ansi | This value defines value for unused
type ttc } overhead bytes.
Note: This parameter is valid for STM-1
mode of E5-cTDM-4 card only
It is valid for STM-1 T1 mode only. In the
TTC mode (STM-1J), the unused bytes are
filled with FFs.
Selecting the timing reference tx-clock-source {loopback | Tx clock source set for one SDH/SONET
source used by the port for the domain <domain-number>} port is automatically copied to the rest
transmit-to-network direction three TDM ports of the card.
Currently, it is recommended to use
domain clock as a Tx clock source.
Defining OC-3 oc3<oc3 number> This parameters is valid for SONET mode
only (for E5-cTDM-4 card must be set to
1)
Assigning SOH profile soh <profile_name> SOH profile configuration is detailed in

Configuring SOH Profile
monitoring data collection at no pm-enable
port level
Displaying SFP status show sfp-status
Clearing statistic counters clear-statistics
Clearing SFP statistic counters clear-sfp-counters

Controlling carrying SSM code in tx-ssm If enabled, the TDM port carries SSM
S1 byte for system clock quality no tx-ssm code in S1 byte for system clock QL. In
level definition the following cases, the S1 byte is set to
DNU (SDH) or DUS (SONET) mode:
• SSM transmission is disabled
• Port Rx clock is set to loopback
• Port clock is used as a selected source
for system timing.
Configuring AUG/OC-3 Interfaces

E5-cTDM-4 cardETX-5 supports a single AUG (STM-1) or OC-3 (OC-3) per TDM
port.
E5-cTDM-STM4 card supports four AUGs (STM-1) or OC-3 (OC-3) per TDM port.
 To configure AUG/OC-3:
1. At the config>port>sdh-sonet(slot/port)# prompt, enter aug <aug number*>
or oc3 <oc3 number*>.
The config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)# prompt is
displayed.
* For E5-cTDM-4 card <aug number> must be set to 1
Defining transmitted and J1-pathtrace [ {tx-string <tx- When TIM monitoring is enabled and ETX-
expected path trace labels trace-string> ] [exp-string 5 receives path trace string that is
(carried in byte J1 of the AUG <exp-string>}] different from the expected one, it
overhead) declares path TIM defect
Assigning path profile to AUG or path <profile_name> Path profile configuration is detailed in
OC-3 Configuring Path Profile
Selecting path width path-width { au4 | au3} This value defines T1-AU-3 and E1 to
AU-4 mapping mode. It is valid for SDH
mode only.
Note: not relevant for E5-cTDM-STM4
card

AUG level
Defining TUG-3 (Tributary Unit tug3 { 1 | 2 | 3} This parameter is valid for both STM-1
Group) and STM-4 E1 ports.

Defining AU-3 (Administrative au3 { 1 | 2 | 3} This parameter is valid for STM-1 T1

Unit) ports only. See Configuring
TUG3/AU3/STS-1 below.
card
Defining STS-1 port sts1 { 1 | 2 | 3} This parameter is valid for both OC-3 and
OC-12 ports. See Configuring
TUG3/AU3/STS-1 below.
Configuring TUG3/AU3/STS-1 Interfaces

ETX-5 supports three TUG3 (STM-1 E1), AU3 (STM-1 T1) or STS-1 (OC-3) per TDM
port.
 To configure TUG3/AU3/STS-1:
1. At the config>port>sdh-sonet(slot/port)>aug(number) or oc3(number)#
prompt, enter tug3 1–3, au3 1–3 or sts1 1–3.
The config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)>tug3(number),
au3(number) or sts1(number)# prompt is displayed.
Definingtransmitted and J1-pathtrace [ {tx-string <tx- When TIM monitoring is enabled and ETX-
(carried in byte J1 of the <exp-string>}] different from the expected one, it
STS1overhead) declares path TIM defectETX-5
Assigning path profile to STS-1 path <profile_name> Path profile configuration is detailed in
or AU3 Configuring Path Profile

STS-1 and AU3 level

port no name
Defining VC-12 ports vc12 {<1–7> | <1–3>} Use space to separate TUG2 and VC-12
values. This parameter is valid for STM-1
E1 ports only.
Defining VC-11 ports vc11{ <1–7> | 1–4>} Use space to separate TUG2 and VC-11
values. This parameter is valid for STM-1
T1 ports only. See Configuring VC-12/VC-
11/VT-1.5 below.
card

Defining VT-1.5 ports vt1-5 {<1–7> | <1–4>} Use space to separate TUG2 and VT-1.5
values. This parameter is valid for OC-
3and OC-12 ports.
Configuring VC-12/VC-11/VT-1.5 Interfaces

ETX-5 allows configuration of internal ports at the VC-12 (STM-1 E1), VC-11
(STM-1 T1) or VT-1.5 (OC-3) level.
 To configure VC-12/VC-11/VT-1.5:
1. At the config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)>tug3(number),
au3(number) or sts1(number)# prompt, enter vc12 number number, vc11
number number or vt1-5 number number.
The config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)>tug3(number),
au3(number) or sts1(number)> vc12 (TUG2 number/VC-12 number), vc11
(TUG2 number/VC-11 number) or vt1-5 (TUG2 number/VT-1.5 number)#
prompt is displayed.
Defining transmitted and J2-pathtrace [ {tx-string <tx- When TIM monitoring is enabled and ETX-
(carried in byte J2 of the VC/VT <exp-string>}] different from the expected one, it
overhead) declares path TIM defectETX-5
Assigning path profile to VC-12, path <profile_name> Path profile configuration is detailed in
VC-11 or VT-1.5 Configuring Path Profile
monitoring data collection at VC- no pm-enable
12, VC-11 or VT-1.5 levels

port no name
Configuring SOH Profile

In the ETX-5 architecture, SDH/SONET units can have SOH profiles bound to them.
You can create up to four SOH profiles to define various monitoring thresholds
for SOH examination process. The profiles are used for detecting whether
transmission degradations have reached unacceptable levels. SOH profiles are
assigned to SDH/SONET interfaces.

 To configure SOH profile:

1. At the config>port# prompt, enter soh-profile <profile_name> for SOH
profile.
The config>port>soh-profile(profile_name)# prompt is displayed.
Note Using no before soh-profile, deletes SOH profile.
Defining EED (error rate ber-threshold [eed {e-3 | e- If the selected BER value is exceeded,
degradation) and SD (signal 4 | e-5} ] [ sd {e-5 | e-6 | e-7 ETX-5 generates the relevant (EED or SD)
degrade) thresholds | e-8 | e-9}] alarm.
Currently, SD BER threshold uses E-5
only.
Setting far-end CV, ES, SES fe-line-interval-threshold [cv

and/or UAS counter value during <cv-value 0–16383>] [es
a 15-min interval starting from <es-value 0–900>] [ses
which a trap is sent <ses-value 0–900>] [uas
<uas-value 0–900>]
Setting near-end CV, ES, SES line-interval-threshold [cv

a 15-min interval starting from <es-value 0-900>] [ses
Setting section CV, ES, SES section-interval-threshold

and/or UAS counter value during [cv <cv-value 0–16383>] [es
which a trap is sent <ses-value 0–900>] [sefs
<sefs-value 0–900>]
Defining a padding character padding<value>

(null or space) used when an
SDH trace message string is
shorter than 15 characters
Controlling TIM defect tim-monitoring no tim-monitoring disables TIM defect

monitoring no tim-monitoring monitoring at SOH level
Configuring Path Profile

In the ETX-5 architecture, SDH/SONET units can have path profiles bound to
them. You can create up to eight path profiles to define various monitoring
thresholds for path examination process. The profiles are used for detecting
whether transmission degradations have reached unacceptable levels. Path
profiles are assigned to AUG/VC-12, AU3/VC-11, STS-1/VT-1.5 ports.

 To configure path profile:

1. At the config>port# prompt, enter path-profile <profile_name> for high-order
path profile.
The config>port>path-profile(profile_name)# prompt is displayed.
Note Using no before path-profile, deletes path profile.
Defining EED (error rate ber-threshold [eed {e-3 | e- If the selected BER value is exceeded,
degradation) and SD (signal 4 | e-5} ] [ sd {e-5 | e-6 | e-7 ETX-5 generates the relevant (EED or SD)
degrade) thresholds | e-8 | e-9}] alarm
Currently, SD BER threshold uses E-5
only.
Setting far-end CV, ES, SES fe-line-interval-threshold [cv

Setting near-end CV, ES, SES interval-threshold [cv

Defining a padding character padding<value>

(null or space) used when an
SDH trace message string is
shorter than 15 characters
Defining the expected payload-label<value>

higher-order path signal label
(byte C2)
Controlling TIM defect tim-monitoring no tim-monitoring disables TIM defect

monitoring no tim-monitoring monitoring at path level
Example
The script below shows the configuration of SDH/SONET port 1 on the E5-cTDM-4
card installed in slot 1.
#***************************Defining_SDH_SONET_Card**************************
configure slot 1
card-type sdh-sonet stm-1-ch-4
no shutdown
exit all
#*********************************End****************************************
#**************************Configuring_SOH_Profile***************************

configure port soh-profile SOH-PROFILE-1

ber-threshold eed e-3 sd e-5
tim-monitoring
exit all
#*********************************End****************************************
#**************************Configuring_HVC_Profile***************************
configure port path-profile PATH-PROFILE-1
payload-label hvc 0x02
tim-monitoring
exit all
#*********************************End****************************************
#**************************Configuring_LVC_Profile***************************
configure port path-profile VC-PROFILE-1
payload-label lvc asynchronous
tim-monitoring
exit all
#*********************************End****************************************
#**************************Configuring_SDH_Port******************************
configure port sdh-sonet 1/1
j0-pathtrace tx-string "ETX-5300A" exp-string "EGATE-2000"
soh profile SOH-PROFILE-1
tim-action soh
tim-action path
tim-action vt
eed-action soh
eed-action path
eed-action vt
tx-ssm
no shutdown
#*********************************End****************************************
#**************************Configuring_HVC***********************************
aug 1
path-width au-4
j1-pathtrace tx-string "ETX-AUG-1" exp-string "EGATE-AUG-1"
path profile PATH-PROFILE-1
pm-enable
no shutdown
#*********************************End****************************************
#**************************Configuring_LVC***********************************
tug3 1
vc12 1 1
j2-pathtrace tx-string "ETX-VC12-1-1" exp-string "EGATE-VC12-1-1"
path profile VC-PROFILE-1
pm-enable
no shutdown
exit all
#*********************************End****************************************

Displaying Status
You can display current status of TDM port on E5-cTDM-4 card at any level. For
viewing the status of the SDH/SONET hierarchical entities, follow the instructions
below.
 To display SDH/SONET port status:

• At the config>port>sdh-sonet(slot/port)#prompt, enter show status.
The SDH/SONET port status is displayed.
ETX-5>config>port>sdh-sonet(1/1)# show status
Name : SDH/SONET- 1-1
MAC Address : 00-07-45-00-0F-08

SFP Status : OK
Connector Type : SFP In
Loopback : None
Trace Message (J0)

Expected : 0x01
Received : 0x01
The TDM interface status screens provide information on the port name,
administrative/operational status, trace message strings, signal labels, RDI
code and connector type (SDH/SONET level only).
 To display AUG status:

1. Navigate to config>port>sdh-sonet(slot/port)>aug(1)#.
ETX-5>config>port>sdh-sonet(l/1)>aug(1)# show status
Name : HVC-1/1/1
Trace Message (J0)

Expected : 0x01
Received : 0x01
Signal Label
Expected : 0x00
Received : 0x00
RDI Code : No Defect
 To display STS-1 status:

1. Navigate to config>port>sdh-sonet(slot/port)>oc3(1)>sts1(1)#


ETX-5>config>port>sdh-sonet(4/1)>oc3(1)>sts1(1)# show status
Name : HVC-4/1/1
Trace Message (J1)

Expected : 0x01
Received : 0x01
Signal Label
Expected : 0x00
Received : 0x00
 To display VC12/VT-1.5 status:

1. Navigate to:
STM-1 E1
config>port>sdh-sonet(slot/port)>aug(1)>tug3(1)>vc12(tug2_num/vc12_num)#
OC-3:
config>port>sdh-sonet(slot/port)>oc3(1)>sts1(1)>vt1-5(tug2_num/vt1.5_num)#
ETX-5>config>port>sdh-sonet(4/1)>oc3(1)>sts1(1)# show status
Name : LVC-4/1/1
Trace Message (J2)

Expected : 0x01
Received : 0x01
Signal Label
Expected : 0x00
Received : 0x00
SDH/SONET ports of ETX-5 feature the collection of performance monitoring data
at different hierarchical levels, per ANSI T1.403. The PM data is collected for 15-
minute and 24-hour intervals.
 To display the SDH/SONET statistics:

1. Verify that collection of performance data has been enabled for the TDM level
that you intend to monitor.

2. At the prompt config>slot>port>sdh-sonet (<slot/port>)#, navigate to the

required level and enter show statistics followed by parameters listed below.
SDH/SONET statistics are displayed. The counters are described in
Table 6-10, Table 6-11 and Table 6-12.
12:00 midnight
• previous-day – Displays
statistics for 24 hours before
last 12:00 midnight
96)
succession: current > all
intervals > current day >
previous day
ETX-5>config>port>sdh-sonet(l/1)# pm-enable
ETX-5>config>port>sdh-sonet(l/1)# show statistics current
Current
Valid Intervals : 0
Invalid Intervals : 0
Section
ES : 0 SES : 0
SEFS : 0 CV : 0
Line
ES : 0 SES : 0
UAS : 0 CV : 0
FC : 0
Far End
ES : 0 SES : 0
UAS : 0 CV : 0
FC : 0
Figure 6-16. SDH/SONET Statistics
ETX-5>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)# vt1-5 1 1
ETX-5>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)>vt1.5(1/1)# pm-enable

ETX-5>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)>vt1.5(1/1)# show statistics

current
Current
-----------------------------------------------------------------------------
Valid Intervals : 0
Invalid Intervals : 0
ES : 0 SES : 0
UAS : 0 CV : 0
FC : 0
Far End
ES : 0 SES : 0
UAS : 0 CV : 0
FC : 0
Figure 6-17. SDH/SONET Statistics, VT-1.5 Level
Table 6-10. SDH/SONET Statistics, Section Counters
ES SONET: Number of seconds during which at least one Section BIP error was detected
or an SEF or LOS defect was present
SDH: Number of seconds during which at least one RS errored block was detected or
an SEF or LOS defect was present
SES SONET: Number of seconds during which 155 or more Section BIP errors were
detected or an SEF or LOS defect was present
SDH: Number of seconds during which 2400 or more RS errored blocks were detected
or an SEF or LOS defect was present
SEFS Number of the seconds during which an SEF defect was present
CV SONET: Number of BIP errors detected at the Section layer (B1 byte)
SDH: Number of errored blocks at the RS layer (B1 byte)
Table 6-11. SDH/SONET Statistics, Line Counters
ES SONET: Number of seconds during which at least one Line BIP error was detected or a
compound AIS-LINE defect was present
SDH: Number of seconds during which at least one MS errored block was detected or
a compound AIS-LINE defect was present
SES SONET: Number of seconds during which 154 or more Line BIP errors were detected or
a compound AIS-LINE defect was present
SDH: Number of seconds during which 2400 or more MS errored blocks were detected
or a compound AIS-LINE defect was present

UAS Number of seconds for which the Line is unavailable. The line becomes unavailable at
the onset of 10 contiguous SES-Ls. The 10 SES-Ls are included in unavailable time.
Once unavailable, the line becomes available at the onset of 10 contiguous seconds
with no SES-Ls. The 10 seconds with no SES-Ls are excluded from unavailable time.
CV SONET: Number of BIP errors detected at the Line layer (B2 byte)
SDH: Number of errored blocks at the MS layer (B2 byte)
FC Number of Line failure events. A failure event begins when a compound AIS-LINE
Table 6-12. SDH/SONET Statistics, Far-End Line Counters
ES SONET: Number of seconds during which at least one Line BIP error was reported by
the far-end (using the REI-L) or an RDI-LINE defect was present
SDH: Number of seconds during which at least one MS errored block was reported by
the far-end (using the REI-L) or an RDI-LINE defect was present
SES SONET: Number of seconds during which154 or more Line BIP errors were reported by
the far-end or an RDI-LINE defect was present
SDH: Number of seconds during which 2400 or more MS errored blocks were reported
by the far-end or an RDI-LINE defect was present
UAS Number of seconds for which the Line is unavailable at the far-end. The far-end line
becomes unavailable at the onset of 10 contiguous FE-SES-Ls. The 10 FE-SES-Ls are
included in unavailable time. Once unavailable, the line becomes available at the onset
of 10 contiguous seconds with no FE-SES-Ls. The 10 seconds with no FE-SES-Ls are
excluded from unavailable time.
CV SONET: Number of Line BIP errors detected by the far-end and reported back to the
near-end using the REI-L indication in the LOH (M1 byte)
SDH: Number of MS errored blocks detected by the far-end and reported back to the
near-end using the REI-L indication in the MSOH (M1 byte)
FC Number of far-end Line failure events. A far-end failure event begins when an RFI-LINE
• At the prompt config>slot>port>sdh-sonet (<slot/port>)#, enter
clear-statistics.
Testing SDH/SONET Ports

ETX-5 supports activation of local and remote loopbacks at the SDH/SONET level.
You can initiate up to four simultaneous loopbacks (one per port) on a single E5-
cTDM-4 or one loopback on a single E5-cTDM-STM4card at a time. 12 STS 1 can
be combined to obtain one Synchronous Transport Signal level 12 (STS 12) at the
same rate as STM 4 (622.080 Mbps). The corresponding optical line signal is

designated OC 12. 12 STS-1 can be combined to obtain one Synchronous

Transport Signal level 12 (STS-12) at the same rate as STM-4 (622.080 Mbps).
The corresponding optical line signal is designated OC-12.
SDH/SONET Port Diagnostics section above details signal paths when local and
remote loopbacks are activated.
 To activate a loopback:
1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to test.
The config>port>sdh-sonet>(slot/port)# prompt is displayed.
2. At the config>port>sdh-sonet>(slot/port)# prompt, enter loopback , followed
by loopback type (local or remote) and its duration 0 (forever) - 86400
seconds..
 To deactivate a loopback:
• At the config>port>sdh-sonet>(slot/port)# prompt, enter no loopback.
The table below lists messages generated by ETX-5 when a configuration error is
detected.
Message Description
the loopback first
Invalid entity for VC profile to be added Invalid port entity has been assigned to a SOH or path profile
The profile is not defined yet Non-existing SOH or path profile has been assigned to a port
Invalid inband loopDown length Invalid length of inband loopback deactivation code
PathWidth is wrong for the LineType Invalid path width value for STM-1 port
Invalid SonetMedium SsmTX value Invalid value for SSM code carried in S1 byte
Invalid loopback timeout value Loopback duration value is out of range (0 - 86400)
Invalid transmitted trace length Invalid length of J0, J1 or J2 transmitted path trace label
Invalid expected trace length Invalid length of J0, J1 or J2 expected path trace label
Invalid CV section interval threshold CV section threshold value is out of range (0–16383)

Message Description
Invalid ES section interval threshold ES section threshold value is out of range (0–900)
Invalid SES section interval threshold SES section threshold value is out of range (0–900)
Invalid SEFS section interval threshold SEFS section threshold value is out of range (0–900)
Invalid CV line interval threshold CV line threshold value is out of range (0–16383)
Invalid ES line interval threshold ES line threshold value is out of range (0–900)
Invalid SES line interval threshold SES line threshold value is out of range (0–900)
Invalid CvFe line interval threshold CV far-end line threshold value is out of range (0–16383)
Invalid EsFe line interval threshold ES far-end line threshold value is out of range (0–900)
Invalid SesFe line interval threshold SES far-end line threshold value is out of range (0–900)
Invalid UasFe line interval threshold UAS far-end line threshold value is out of range (0–900)
Invalid EED response value Invalid EED response value has been selected
Invalid EED threshold value Invalid EED threshold value has been selected
Invalid CV1 5min interval threshold value CV 5-min interval threshold value is out of range (0–16383)
Invalid ES1 5min interval threshold value ES 5-min interval threshold value is out of range (0–900)
Invalid SES1 5min interval threshold SES 5-min interval threshold value is out of range (0–900)
value
Invalid UAS1 5min interval threshold UAS 5-min interval threshold value is out of range (0–900)
value
Invalid FeCv1 5min interval threshold CV far-end 5-min interval threshold value is out of range (0–
value 16383)
Invalid FeEs1 5min interval threshold ES far-end 5-min interval threshold value is out of range (0–
value 900)
Invalid FeSes1 5min interval threshold SES far-end 5-min interval threshold value is out of range (0–
value 900)
Invalid FeUas1 5min interval threshold UAS far-end 5-min interval threshold value is out of range (0–
value 900)
Invalid payload label Invalid expected higher order path signal label (byte C2) has
been selected
Medium type SONET does not match Frame type is not compatible with selected card type
card type
Medium type SDH does not match card Frame type is not compatible with selected card type
type
Path width sts1 is illegal for SDH E1 Selected STS-1 path width value is incompatible with SDH E1
port type
Path width sts3cSTM1 is illegal for SONET Selected STS-3 path width value is incompatible with SONET port
type
Default profile cannot be deleted Default SOH or path profile cannot be deleted

Message Description
Profile can't be created: max number of Maximum number or SOH or path profiles has been reached
profiles has been reached
Profile name must be unique SOH or path profile name is already taken
Profile name cannot be changed SOH or path profile name cannot be changed when it has ports
assigned to it
Profile does not exist Cannot assign a port to a non-existing SOH or path profile
6.5 Service Aggregation Group (SAG)

SAG (Service Aggregation Group) is a logical port (management entity) that
represents a physical connection between I/O and main Ethernet cards.
Benefits
SAGs represent blocks of I/O card ports with ability to aggregate their flows into
Service Attachment Points (SAPs), supporting pre-forwarding scheduling and
shaping.
Factory Defaults
By default, two SAGs exist per I/O Ethernet card.
6-64 Service Aggregation Group (SAG) ETX-5

GbE and 10GbE cards introduce logical ports that serve as management entities
(SAG) and flow aggregation points (SAP). Figure 6-18 illustrates Ethernet I/O card
schematics. The SAPs aggregate several I/O ingress flows to a single forwarding
path (E-Line or E-LAN) towards the main card and help avoid re-classification to
different forwarding paths from the same SAG.
Flow
SAP

Flow SAP
Flow
SAP

Flow SAP
Figure 6-18. I/O Ethernet Card
Each I/O Ethernet card has two SAGs, serving 1–10 and 11–20 ports on
E5-GbE-20 card respectively. Likewise, SAG 1 serves port 1 and SAG 2 serves port
2 on E5-10GbE-2 card. Each SAG includes 1024 SAPs, which aggregate ingress
flows from I/O card ports.
Configuring SAGs
 To configure a SAG:
1. Navigate to config>port.
2. Enter sag <slot/port>.
The config>port>sag(slot/port)# prompt is displayed.
ETX-5 Service Aggregation Group (SAG) 6-65

Associating SAG with queue group queue-group < queue-group-name> no queue-group removes SAG
association with the queue group
Assigning a name to SAG name <string> no name removes SAG name
Example
 To configure a SAG:
• Slot 1
• Port 1
• Name – SAG_1_1
• Queue group – q_group_SAG_2_level_default.
ETX-5>config>port>sag 1/1
ETX-5>config>port>sag(1/1)# name SAG_1_1
ETX-5>config>port>sag(1/1)# queue-group profile q_group_SAG_2_level_default
detected.
Message Description
Illegal ingress/egress SAP number Maximum number of ingress/egress SAPs (1024) has been
reached
Cannot bind SAG queue group to A queue group that has already been bound to a SAG cannot be
Ethernet port or LAG used for an Ethernet group or LAG
Cannot bind level-3 queue group to SAG A level-3 queue group cannot be bound to a SAG
Shaping profile is bound to level-1 SAG Level-1 queue block bound to SAG cannot include shaper
queue block
6.6 Service Virtual Interface (SVI)

Service Virtual Interface (SVI) is a logical port that is used for binding flows to
bridge ports, router interfaces or Layer-2 TDM pseudowires.
Factory Defaults
By default, ETX-5 does not have SVIs.
6-66 Service Virtual Interface (SVI) ETX-5

SVIs are used as ingress and egress ports for flows, serving as intermediaries for
bridges and routers, which must comply with standards of their own (VLAN
domains for bridge ports or IP address for router interfaces). They do not have
physical port attributes. They also serve as aggregation points for TDM PWs (see
Figure 6-20). ETX-5 supports up to 4000 SVIs.
Note For bridge-type SVIs, each ingress flow within a certain VLAN domain must have
an accompanying egress flow.
ETX-5
LB IP
Router
RIF
SVI
SVI
SVI BP SVI
User BP BP OOB
Bridge
User BP BP NET
SVI SVI
Figure 6-19. Router and Bridge Connections with SVIs Identified
MEF-8 SVI SVI BP SVI

Pseudowires
Flow
BP BP
I/O Card STM-1/OC-3 Port
Bridge
SVI
MEF-8
Pseudowire Flow BP BP
SVI SVI
MEF-8 SVI
Pseudowire Flow
TDM Pseudowire
Processing
Figure 6-20. Layer-2 Pseudowire Connection
ETX-5 Service Virtual Interface (SVI) 6-67

Configuring SVIs
 To configure an SVI:
2. Enter the svi <svi_number>, followed by the SVI type (bridge | pw | router),
depending on whether you intend to attach a flow to a bridge, a pseudowire
or a router.
The config>port>svi(number)# prompt is displayed.
Note no svi <svi_number> entered at the config>port prompt, deletes the SVI.
Assigning a name to SVI name <string> no name removes SVI name
Example
 To configure SVI:
• Number – 1
• Type – bridge
• Name – svi_1_bridge
ETX-5>config>port>svi 1 bridge
ETX-5>config>port>svi(1)# name svi_1_bridge
detected.
Message Description
SVI cannot be created: max number of SVI cannot be created because the maximum number of SVIs per
SVIs has been reached chassis (4000 interfaces) has 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: only bridge-type SVI can SVI cannot be modified because only bridge-type SVIs can be
be bound bound to this entity
6-68 Service Virtual Interface (SVI) ETX-5

Message Description
Modify failed: SVI is already bound to SVI cannot be modified because it is already bound to another
another bridge port bridge port
Modify failed: flow is bound to SVI SVI cannot be modified because flows are bound to it
6.7 T1 Ports
Internal T1 ports of the E5-cTDM-4 and E5-cTDM-STM4 cards deliver pseudowire
services, emulating PDH traffic over PSN. Each internal T1 is permanently mapped
to a VT-1.5 channel, handling its payload in accordance with the defined ITU-T
framing mode and signaling format.
Standards and MIBs

The T1 interface complies with ANSI T1.403-1989, AT&T Pub. 54016, AT&T
TR-62411 and ANSI T1.107.4 standards.
Factory Defaults
ETX-5 is supplied with all T1 ports disabled. Other parameter defaults are listed in
the table below.
line-type unframed
path-interval-threshold cv 0
path-interval-threshold es 80
path-interval-threshold ses 10
path-interval-threshold sefs 0
path-interval-threshold css 0
path-interval-threshold uas 10
idle-code 7F
out-of-service 00
tx-clock-source loopback
loopback no loopback
trail-mode terminated
ETX-5 T1 Ports 6-69

T1 Signal Structure
The T1 line operates at a nominal rate of 1.544 Mbps. The data transferred over
the T1 line is organized in frames.
The T1 frame format is shown in the figure below.
8 Other Frames Bit B Conveys
Byte Organization 8 Bits/Channel 1 2 3 4 5 6 7 A Frame 6 Signaling
(D4 Frame - See NOTE) B Frame 12 Information
Ft C H C H CH CH
Frame 24 Channels/Frame
or
Organization Frame = 193 Bits 1 2 13 24
Fs
Multiframe
FR FR FR FR FR
Organization
1 2 7 11 12
Multiframe
SF (D4) 12 Frames
NOTE: ESF: 24 Frames
In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24
Figure 6-21. T1 Frame Format
Each T1 frame includes 193 bits. 192 bits are organized in 24 timeslots of eight
bits each that carry the payload data. An additional timeslotconsisting of one bit
(the F-bit) carries framing and supervision information. As a result, the data rate
supported by each payload timeslot is 64 kbps. The data rate of the framing slot
is 8 kbps.
The T1 frame does not include a dedicated timeslot for the transfer of channel
signaling. When end-to-end transfer of signaling is necessary, a technique called
“robbed-bit signaling” is used. The robbed-bit is the least significant bit (bit 8) of
the channel byte, and is actually “robbed” only once in every six frames. A
channel signaling information is transmitted transparently without any special
treatment.
In order to enhance link/system supervision capabilities, the frames are organized
in larger patterns, called super-frames. Two types of super-frames are used:
• SF (also called D4), consists of 12 T1 frames.
• Extended SF (ESF), consists of 24 T1 frames
The SF format provides limited supervision capabilities, such as end-to-end
reporting of local loss-of-signal (yellow alarm), and line loopback.
The ESF format provides improved supervision capabilities, and allows better
utilization of the 8 kbps framing timeslots. The major advantage of the ESF
format is that it supports on-line link performance monitoring (by means of a
2 kbps Cyclic Redundancy Check (CRC) channel) and also provides a 4 kbps
end-to-end supervision and control data link. The data link can be used for
performance monitoring and failure reporting, for activation of maintenance
loopbacks, and for transmission of various commands to the far end equipment.
The implementation of the multiframing format is based on the use of various
F-bit patterns. The F-bit pattern is used to perform three functions:
6-70 T1 Ports ETX-5

• Framing Pattern Sequence (FPS) – defines frame and multiframe boundaries.

• Facility Data Link (FDL) – allows transfer of supervisory data, e.g. alarms,
error performance, test loop commands, etc. to be passed through the T1
link.
• Cyclic Redundancy Check (CRC) – allows the measurement of the bit error
rate and enhances the reliability of the framing algorithm.
The F-bit pattern defines the structure of frames and multiframes. In the D4 (SF)
frame format, the F-bit of consecutive frames is alternately interpreted as an
Ft bit (terminal framing bit) or Fs bit (frame signaling bit).
• Ft pattern: alternating 0s and 1s, defines the frame boundaries.
• Fs pattern: fixed 001110 pattern, defines the multiframe boundaries, so that

one frame may be distinguished from another. In particular, the Fs pattern is
needed so that frames 6 and 12 may be identified for the recovery of
signaling bits.
In the ESF frame format, the multiframe structure is extended to 24 frames, but
the frame and channel structure are the same as in the D4 (SF) format.
T1 Alarm Conditions
The basic alarm conditions are the red alarm and the yellow alarm. Note that with
the ESF format, the FDL link can be used for more sophisticated status
transmissions, in accordance with the ANSI Standard T1.403-1989 and AT&T Pub.
54016.
• Red Alarm. A red alarm is generated when the local unit has lost frame
synchronization for more than 2.5 consecutive seconds, or the bit error rate
-2
exceeds 10 for 2.5 consecutive seconds. Loss of frame synchronization may
be caused either by Fs or Ft errors, by the reception of an AIS signal, or by
the loss of the input signal (receive data remains zero for 31 consecutive
bits). In accordance with AT&T TR-62411, a system automatically recovers
synchronization when there has been a period of 10 to 20 consecutive
seconds free of the loss of sync condition.
• Yellow Alarm. A yellow alarm is sent from the remote unit to inform the local
unit that a red alarm exists at the remote end.
• Alarm Indication Signal (AIS). The AIS signal is an unframed “all-ones” signal,
and is used to maintain line signal synchronization when an alarm condition
occurs in the equipment that supplies the line signal.
T1 Port Diagnostics
Diagnostic tools at the T1 level include:
• Local and remote loopback for checking connections toT1 ports
• Code-activated local and remote loopbacks. These loopbacks are activated
and deactivated by the detection of user-specified patterns in the TDM data,
a function enabled and configured as part of the physical parameters of the
port.
ETX-5 T1 Ports 6-71

Note You can run only one regular or inband-activated local loopback per the
E5-cTDM-4 and E5-cTDM-STM4 cards.
Local Loopback
The figure below shows the signal paths during a local loopback on an internal T1
port.
Internal T1
TDM PSN
Framer Mapper
Figure 6-22. Local Loopback on Internal T1 Port, Signal Paths
As shown in the above figure, when a local loopback is activated on a local

internal T1 port, the receive signal of the port is connected by the port T1 framer
to the input of the port transmit path. The signal is then returned toward the
remote side through the port packet processor, the remaining sections of the
local transmit path, and the link through the packet-switched network.
While the loopback is activated, the transmit signal arriving from the local end
user equipment is ignored, but the local T1 port continues sending the received
signal to the local end user equipment.
To ensure that the remote equipment is capable of providing a good signal, the
local loopback should be activated on the local T1 port only after checking that
the remote end user equipment connected to the tested T1 port operates
normally while its own local loopback is activated.
While the local loopback is activated on the local port, the remote end user
This test fully checks the operation of the local T1 path serving the tested port. It
also checks the signal paths that end at the corresponding T1 port, including the
transmission through the packet network connecting the remote equipment to
ETX-5.
Remote Loopback
Figure 6-23 shows the signal paths during a remote loopback on an internal E1
port.
As shown in Figure 6-23 when a remote loopback is activated on an internal E1
port, the T1 framer of that port returns the transmit signal via the receive path of
the same port. The transmit signal is received from the local end user equipment
served by the tested port, through the corresponding E5-cTDM-4 or E5-cTDM-
STM4 cards.
While the loopback is activated, the signal received from the remote T1 port is
ignored. The signal received from the local end user equipment remains
connected to the packet processor and it is transmitted to the remote T1 port.
To ensure that the user equipment is capable of providing a good signal, the
remote loopback should be activated on T1 port only after checking that the local
end user equipment operates normally while its own local loopback is activated.
6-72 T1 Ports ETX-5

Internal T1
TDM PSN
Framer Mapper
Figure 6-23. Remote Loopback on Internal T1 Port, Signal Paths
While the remote loopback is activated on the local T1 port, the local end user
This test checks the transmission path between the local end user equipment to
the local port, including the transmission plant and SONET equipment connecting
the user equipment to the ETX-5, and part of the internal ETX-5 signal path that
handle the routing of the signals up to the tested T1 port, including the SONET
mapper of the E5-cTDM-4 or E5-cTDM-STM4 cards.
Inband Loopbacks
ETX-5 supports code-activated local and remote loopbacks. These loopback
functions are activated and deactivated by the detection of user-specified
patterns in the TDM data.
When a T1 port is configured to activate a local loopback in response to the
configured pattern sent using PW OAM messaging, it monitors the incoming TDM
data stream:
• To activate the loopback, the user equipment sends the configured activation
pattern several times in sequence.
• When the configured activation pattern is detected, the port activates its
local loopback.
• The user equipment detects the activation of the loopback because it starts
receiving the loopback activation pattern. After detecting the loopback, the
equipment can stop transmitting the activation pattern, and send any other
desired test signals.
• To deactivate the loopback and return the port to normal operation, the user
equipment sends the configured deactivation pattern several times in
sequence, until it detects the deactivation of the local loopback.
ETX-5 supports the following inband loopback activation methods:
• CSU, according to ANSI T1.403 and AT&T TR 54016. This method is relevant
for framed modes only.
• NIU (FAC1 and FAC2), according to Telecordia GR-312. This method is relevant
for framed and unframed modes.
• Custom, user-defined 3–8 bit long loopback activation and deactivation
patterns. This method is relevant for framed and unframed modes.
ETX-5 T1 Ports 6-73

Configuring Internal T1 Interfaces

 To configure internal T1 parameters:
1. Navigate to configure port t1 <slot/port/tributary> to select the SDH/SONET
port to configure.
The config>port>t1>(slot/port/tributary)# prompt is displayed.
Note An internal T1 port becomes active only if an enabled pseudowire with a valid
cross-connection is assigned to the port.
Assigning short name <string> no name removes the name

description to port
Masking/unmasking no shutdown shutdown masks alarms generated by the

alarms generated by the internal T1. When the T1 interface is
internal T1 disabled, it sends AIS downstream.
Specifying T1 framing line-type {unframed | esf | sf} When using one of the framed modes, you
mode select specific timeslots for transport by
configuring the appropriate bundle at the
pwe# prompt.
The specific timeslots are selected using the
pw-tdm command at the cross-connect#
prompt.
Enabling/disabling pm-enable no pm-enable disables PM data collection

performance monitoring no pm-enable
data collection
Setting path CV, ES, SES, path-interval-threshold [cv <cv-value 0–

SEFS, CSS and UAS 16383>] [es <es-value 0–900>] [ses <ses-
counter value during a value 0–900>] [sefs <sefs-value 0–900>]
15-min interval starting [css <css-value 0–900>] [uas <uas-value
from which a trap is sent 0–900>]
Controlling inband inband-loopback {local | remote} csu no inband-loopback disables inband

loopback activation inband-loopback {local | remote} niu {fac1 loopback.
| fac2} loop-up and loop-down values are entered
inband-loopback {local | remote} program in hexadecimal format.
<loop-up-code> <loop-up-len> loop-up-len and loop-down-len values are
entered in decimal format.
<loop-down-code> <loop-down-len>
One loopback activation and one loopback
no inband-loopback
deactivation code are allowed per the
E5-cTDM-4 and E5-cTDM-STM4 cards.
To activate an inband loopback in a far-end
unit, you must enable pseudowire OAM
functionality.
6-74 T1 Ports ETX-5

Specifying the code idle-code { 00 to FF (hexa) } This parameter is valid for framed modes
transmitted to fill unused only.
timeslots in T1 frames Only one idle code value is allowed per the
E5-cTDM-4 or E5-cTDM-STM4 cards.
Selecting the code out-of-service <00–FF> The hexadecimal number is in the range of 0
transmitted during to FF (two digits)
out-of-service period The selected out-of-service code is also
sent during out-of-service periods instead
of the external data stream when the
unframed mode is used.
Only one out-of-service code value is
allowed per the E5-cTDM-4 or E5-cTDM-
STM4 card.
Controls the propagation trail-mode {terminated | extended} See Alarm Indications and Fault Propagation
of alarm indications in the TDM Pseudowires of Chapter 8
Selects the reference tx-clock-source {domain <domain-num> | Tx clock setting becomes active only after a
source used by the loopback | pw } T1 port is disabled and enabled (shutdown
transmit path of this port > no shutdown).
If a T1 port is assigned to a PW, reset
(disable and enable) the PW after any
change in the tx-clock-source parameter.
Activating diagnostic loopback { local | remote } [ duration <0– Loopback duration is within 0 (forever) –
loopback 86400>] 86400 second range.
no loopback no loopback deactivates it.
Displaying Status
You can display current status of any internal T1 port on an E5-cTDM-4 or E5-
cTDM-STM4 card.
 To display T1 port status:

• At the config>port>t1(slot/port/tributary)#prompt, enter show status.
The T1 port status is displayed.
ETX-5>config>port>t1(1/1/1)# show status
Name : T1-1-1-1
Loopback : Off
The T1 interface status screens provide information on the port name,
administrative/operational status, and loopback status.
ETX-5 T1 Ports 6-75

Internal T1 ports of ETX-5 collect performance monitoring data at path level.
 To display the internal T1 port statistics:

1. Verify that statistics collection is enabled (pm-enable) for the T1 port.
2. At the prompt config>slot>port>t1 (<slot/port/tributary>)#, enter show
statistics followed by parameters listed below.
T1 statistics are displayed. The counters are described in Table 6-16.
12:00 midnight
• previous-day – Displays statistics
for 24 hours before last 12:00
midnight
96)
succession: current > all intervals
> current day > previous day
ETX-5>config>port>t1(4/1/1)# show statistics current

Current
---------------------------------------------------------------
Valid Intervals : 0
Path
---------------------------------------------------------------
CV : 0 UAS : 0
ES : 0 FC : 0
BES : 0
SES : 0
SEFS : 0
Note
For unframed T1 ports, only FC counter is available.
Table 6-16. Internal T1 Statistics
CV Number of CRC-4 errors
6-76 T1 Ports ETX-5

ES Number of seconds during which at least one FE or CS was detected or a SEF defect or
an AIS defect was present
UAS Number of seconds for which the T1 path is unavailable. The T1 path becomes
unavailable at the onset of 10 contiguous SESs. The 10 SESs are included in
unavailable time. Once unavailable, the T1 path becomes available at the onset of 10
contiguous seconds with no SESs. The 10 seconds with no SESs are excluded from
unavailable time.
BES Number of seconds during which at least 2 and no more than 319 CRC-4 errors were
detected while neither OOF nor AIS defects were present.
FC Number of T1 path failure events. A failure event begins when a LOF failure or an AIS
SES Number of seconds during which 805 or more CRC-4 errors were detected or an OOF
defect was present
SEFS Number of seconds during which at least one OOF defect or an AIS defect was present
• At the prompt config>slot>port>t1 (<slot/port/tributary>)#, enter
clear-statistics.
Example
 To configure internal T1 interface:
• T1 name – t1_1_1_1
• Line type – ESF
• Idle code – 0xFF
• Transmit clock source – Loopback
ETX-5# configure port t1 1/1/1
ETX-5>config>port>t1(1/1/1)# name t1_1_1_1
ETX-5>config>port>t1(1/1/1)# line-type esf
ETX-5>config>port>t1(1/1/1)# idle-code 0xFF
ETX-5>config>port>t1(1/1/1)# tx-clock-source loopback
ETX-5>config>port>t1(1/1/1)# pm-enable
ETX-5>config>port>t1(1/1/1)# no shutdown
Table 6-17 below lists messages generated by ETX-5 when a configuration error
is detected.
ETX-5 T1 Ports 6-77

Message Description
Cannot change line type when service is Line type cannot be changed if a pseudowire service has been
defined defined on a port
the loopback first
Invalid Dsx1InbandLoopLength value Invalid length of inband loopback activation code
Invalid inband loopDown length Invalid length of inband loopback deactivation code
Invalid LES threshold value LES threshold value is out of range (0–900)
Invalid Dsx1IdleCode value Invalid idle code value
Invalid loopback timeout value Loopback duration value is out of range (0–86400 sec)
6.8 Terminal Control Port

See section 4.16.
6-78 Terminal Control Port ETX-5

Chapter 7
Resiliency
The modular, distributed architecture of ETX-5 enables redundancy at different
levels of the network and provides a resilient system with no single point of
failure.
• Power system (redundant power supplies, see Chapter 2)
• Management and timing system (redundant main cards)
• Port and service:
 LAG
 G.8032 ring (ERP)
 APS/MSP for SDH/SONET ports
 Dual homing.
This chapter describes port and service protection mechanisms (LAG, ERP and
APS/MSP, dual homing), as well as main card redundancy and fault propagation.
Timing system redundancy is detailed in Chapter 9.
7.1 Dual Homing

As an alternative to link aggregation, two ETX-5 Ethernet ports can be configured
for 1:1 bidirectional Ethernet group protection mode.
Benefits
Dual homing technology enhances network reliability by activating a backup
connection, when a main link fails. This allows traffic re-routing and protection,
using an alternative communication path through the network.
Factory Defaults
By default, no dual homing groups exist. A new group is created with the
following default settings:
Domain Parameter Default Value
Recovery mode no revertive
wait-to-restore 300 sec
tx-down-duration-upon-flip 2 sec
ETX-5 Dual Homing 7-1

Chapter 7 Resiliency Installation and Operation Manual
In the 1:1 bidirectional mode, two Ethernet ports are connected to different
switch/routers, as illustrated in Figure 7-1. This topology is referred to as
Ethernet group protection or dual homing.
PE
Tx
Working
Rx
PSN
PE
Protection
ETX-5300
PE
Figure 7-1. 1:1 Bidirectional Redundancy Mode (Dual Homing)
Note Switchover time for 1000BaseT ports, using physical layer indication only, may
exceed 50 ms due to the link failure detection time requirements in the IEEE
802.3 standard.
Protection Groups
ETX-5 supports up to eight Ethernet protection groups with two GbE or 10GbE
member ports per group. An Ethernet port cannot be a member of more than
one dual homing protection groups. A port in LAG or ERP cannot be defined as a
group member. Likewise, a dual homing group member cannot belong to a LAG or
to an ERP.
Following member port combinations are supported:
• Ethernet ports residing on the same type card: E5-MC-4, E5-MC-SFP-P-4 or
E5-GbE-20 or E5-10GbE-2. For example, port residing on the main and I/O
cards cannot be mixed.
• Ethernet ports residing on the same or different main cards
• Ethernet ports residing on the same or different I/O cards.
Port Combinations in Dual Homing Groups

This section describes valid and invalid combinations of I/O card ports in dual
homing groups.
Valid Combinations
The following ports can be combined into dual homing groups:
• (A) Ports belonging to the different 10-port groups on the same E5-GBE-20
card
• (B) Ports belonging to the same 10-port groups on the different E5-GBE-20
cards
• (C) The same ports on the same E5-10GBE-2 card
• (D) The same ports on different E5-10GBE-2 cards
7-2 Dual Homing ETX-5

Installation and Operation Manual Chapter 7 Resiliency
• (E) Any two ports on the same E5-MC-4 or E5-MC-SFP-P-4 card

• (F) Any two ports on different E5-MC-4 or E5-MC-SFP-P-4 cards.
A
LINK
11
1
E5-GBE-20
B
LINK
11
1
E5-GBE-20
LINK
11
1
E5-GBE-20
C
1 2
E5-10GBE-2
D
1 2
E5-10GBE-2
1 2
E5-10GBE-2
E
1 2 3 4
E5-MC-4
F
1 2 3 4
E5-MC-4
1 2 3 4
E5-MC-4

Figure 7-2. Valid Port Combinations
Invalid Combinations
The following ports cannot be combined into dual homing groups:
• (A) Ports belonging to the same 10-port group on the same E5-GBE-20 card
• (B) Ports belonging to the different 10-port groups on the different
E5-GBE-20 cards
• (C) Different ports on different E5-10GBE-2 cards.
A
LINK
11
1
E5-GBE-20
B
LINK
11
1
E5-GBE-20
LINK
11
1
E5-GBE-20
C
1 2
E5-10GBE-2
1 2
E5-10GBE-2
Figure 7-3. Invalid Port Combinations
Traffic Switching
Dual homing protection technique requires defining one port as “working” and
the other as “protection”. Unlike the LAG, which has the Rx line blocked on the
protection port, the dual homing mechanism requires opening the Rx and Tx lines
on the working port only. The protection port does not receive or transmit traffic.
When the working port fails, the traffic is switched to the protection port. The
switch is performed only if the protection port is enabled and operates properly.
The traffic is flipped back to the working port, when the protection port fails and
working port is restored, and the dual homing operates in the revertive mode. If

the non-revertive mode is enabled, the traffic remains to be sent and received via
the protection port, even when the working port is restored.
Switching Triggers
There are two events that trigger switching traffic between working and
protection ports:
• Ethernet link signal failure
Note Currently, propagation of failure conditions from the OAM (CFM) layer is not
supported.
• Port shutdown
• Card extraction, reset or failure.
Timers
To further improve flexibility of the dual homing mechanism, ETX-5 provides the
following timers:
• Wait-to-restore (WTR). The WTR timer defines a period of time (1–720 sec)
between the port recovery and switching traffic back to the working port.
• Tx down duration. The Tx down duration timer specifies a period of time
(0-30 sec) during which the failed port transmits the Tx down signal upon link
flip. This timer is used together with the force switch and clear commands
(see below) to inform the opposite device about intended traffic switch.
Force Switch Command

The force switch command permanently switches traffic to one of the protection
group ports. When one of the ports is configured to be a permanently active link,
the traffic does not switch to the second port, even if this port fails.
The clear command cancels the force switch, reverting to the regular traffic
switching rules.
Note Using the force switch or clear command when the Tx down duration timer is
running, may cause loss of traffic for several seconds.
Configuring Dual Homing

Configuring a 1:1 protection requires defining an Ethernet group.
 To add an Ethernet group:

1. Navigate to configure protection.
2. Type eth-group and enter a group identification number.
The config>protection>eth-group (group-id)# prompt is displayed.
Note Using no before ethernet-group (group-id), deletes the Ethernet group.

 To configure the Ethernet group:

• At the config>protection> eth-group (group name)# prompt, enter all
necessary commands according to the tasks listed below:
Assigning a name name <string> no name removes Ethernet group

name
Administratively enabling no shutdown Ethernet groups can be enabled

Ethernet group only if it has working and
protection ports bound to it.
shutdown disables Ethernet
group. Ethernet group can be shut
down only if its port members has
no flows attached to them.
Defining operation mode oper-mode { 1-to-1 } Permanently set to 1-to-1
Defining working (active) and bind { working ethernet <slot/port> Using no before bind removes a
protection (standby) links | protection ethernet <slot/port>} link from protection group
Selecting port recovery mode revertive no revertive sets recovery to

no revertive non-revertive mode
Setting the WTR timer wait-to-restore { 1–720 }
Setting the Tx down duration tx-down-duration-upon-flip

timer { 0–30 }
Manually switching traffic to the force

protection port
Clearing force command clear
Displaying Ethernet group status show status
Displaying current Ethernet info

group configuration
Displaying Ethernet Group Status

You can display current status of configured Ethernet group.
 To display Ethernet group status:

• In the config>protection>eth-group(number)$ prompt, enter show status.
The Ethernet protection group status is displayed.
ETX-5>config>protection>eth-group(1)$ show status
Group
-----------------------------------------------------------------------------
Mode : 1:1
Last Switchover Time : 2013-04-07 21:08:58
Last Switchover Reason : User Initiated
Last Command : Clear

Ports
-----------------------------------------------------------------------------
Working Type Slot Admin Oper Active
-----------------------------------------------------------------------------
Protection Ethernet main-b/3 Up Up --
Working Ethernet main-a/3 Up Up Yes
Ethernet group status screen provides information on:
• Protection mode: 1:1
• Administrative status:
 Up – Ethernet group is enabled
 Down – Ethernet group is disabled
• Last Switchover Time: Last time the link switchover occurred
• Last Switchover Reason: Reason for last link switchover
 None – No switchover has occurred
 Port fail (SF) – Switchover occurred due to the Signal Failure condition on
the working port
 User initiated – Switchover occurred due to the force command
 Port recovers (revertive) – Switchover to the working port occurred
because the working port has been restored (revertive mode only)
• Administrative and operational status of Ethernet group port members.
Example
 To define link protection:
• Ethernet group 1
• Working port – Ethernet port 1 on main card A
• Protection port – Ethernet port 1 on main card B.
exit all
configure protection ethernet-group 1
bind eth working ethernet main-a/1 protection ethernet main-b/1
exit all
detected.
Message Description
Max number of Ethernet protection The maximum number of Ethernet protection groups (8) per
groups has been reached chassis has been reached. Delete a group to add a new one.

Message Description
Cannot delete Ethernet protection group: An Ethernet protection group with ports bound to it cannot be
a port is bound the group deleted
Cannot activate Ethernet protection An Ethernet protection group with less than two ports bound to
group: only one port is bound to the it cannot be activated
group
Manual switch failure: secondary card is Traffic cannot be manually switched to a protection port,
not active because its card has not been activated yet
Cannot modify Ethernet protection An active Ethernet protection group cannot be modified, disable
group: the group is active it first
Invalid card type for Ethernet protection Selected working or protection port resides on an I/O card that
group cannot be used for Ethernet protection
Card type has not been defined yet A port on an Ethernet I/O card that has not been provisioned
yet, cannot be bound to an Ethernet protection group
Invalid port number for the current card Invalid Ethernet port number has been selected
type
This port is already bound to an Ethernet Ethernet port cannot be bound to more than one Ethernet
protection group protection group
Cannot bind LAG member to Ethernet Ethernet ports that serve as LAG members cannot be bound to
protection group an Ethernet protection group
Cannot bind ERP member to Ethernet Ethernet ports that serve as Ethernet ring members cannot be
protection group bound to an Ethernet protection group
Cannot bind protection port: the port An Ethernet port with flows attached to it cannot be bound to
has flows attached to it an Ethernet protection group as a protection port
Cannot delete Ethernet protection group: An Ethernet protection group cannot be deleted if its working
working port has flows attached to it port has flows attached to it
Cannot modify ports bound to Ethernet Ethernet ports bound to an Ethernet protection group that has
protection group that has ever been been activated in the past, cannot be modified. Delete and re-
activated create the group.
Cannot execute force command twice, A force command is currently active, use the clear command to
use clear command first terminate it and try again
7.2 Ethernet Link Aggregation (LAG)

Ethernet link aggregation technique allows one or more links to be combined to
form a Link Aggregation Group (LAG). LAG can be used for Ethernet card/port
protection and for bandwidth expansion.
ETX-5 supports LAG for up to two members, consisting of Ethernet ports located
on the same or different cards.
7-8 Ethernet Link Aggregation (LAG) ETX-5

Standards and MIBs

IEEE 802.3-2005, 802.1ax
LLDP
Benefits
Ethernet link aggregation ensures increased service availability. If a link within a
LAG fails or is replaced, the traffic is not disrupted and communication is
maintained.
Factory Defaults
By default, no LAG groups exist.
The two Ethernet ports can be operated as a single logical interface, using link
aggregation in accordance with IEEE 802.3-2005. The two ports must be
connected to the same switch/router. LAG uses 1:1 distribution mechanism. ETX-
5 supports up to 44 LAGs per chassis.
Using link aggregation inherently provides redundancy; if one of the GbE ports
fails, the other can continue transferring traffic. Link failure is detected by
sensing the loss of valid signals, or receiving a failure report via Link Aggregation
Control Protocol (LACP) if applicable, in which case all traffic is sent through the
other link.
ETX-5 supports LAG for up to two members, consisting of Ethernet ports located
on the same or different cards.
Note Switchover time for 1000BaseT ports, using physical layer indication only, may
exceed 50 ms due to the link failure detection time requirements in the IEEE
802.3 standard. To achieve a sub-50 ms switchover, use LACP for signal failure
indication.
Intra-Card LAG
With intra-card LAG, the two aggregation group members reside on the same
E5-MC-4, E5-MC-SFP-P-4, E5-10GBE-2 or E5-GBE-20 card. For E5-GBE-20 card,
the LAG ports must belong to the different 10-port groups (ports 1–10 or ports
11–20). In this case, and in the case of the E5-10GBE-2 cards, the LACP is
permanently enabled. The LACP uses the STBY option to force the opposite party
to receive and transmit on the same port.
For the E5-MC-4 and E5-MC-SFP-P-4 cards, LACP can be enabled or disabled by
the user. In this mode, both ports receive traffic at the same time, but only one
of them transmits data.
ETX-5 Ethernet Link Aggregation (LAG) 7-9

LAG
Rx
Tx
Main or I/O Card
Tx
Rx
Figure 7-4. Intra-Card LAG
Inter-Card LAG
With inter-card LAG, the two aggregation group members reside on different
E5-MC-4, E5-MC-SFP-P-4, E5-GBE-20 or E5-10GBE-2 card. However, the ports
must belong to:
• The same card type (LAG between ports residing on I/O and main cards is not
allowed)
• The same 10-port group on E5-GBE-20 cards:
 Permitted – port 2/1 (port 1 on E5-GBE-20 card in slot 2) and port 3/3
(port 3 on E5-GBE-20 card in slot 3)
 Not permitted – Port 2/1 and port 3/12.
• The same port on E5-10GBE-2 cards:
 Permitted – port 1/1 (port 1 on E5-10GBE-2 card in slot 1) and port 3/1
(port 1 on E5-10GBE-2 card in slot 3)
 Not permitted – Port 2/1 and port 3/2.
In this LAG scheme, data flow redundancy can be provided at a card and port
levels.
LAG
Rx
Main or I/O Card
Tx
Tx
Main or I/O Card
Rx
Figure 7-5. Inter-Card LAG
When an inter-card LAG is active, only one port receives and transmits traffic. The
second LAG member is forced by LACP to be out-of-sync. In this type of link
aggregation LACP is always enabled.

Load-Balancing LAG
In addition to protection mode, ETX-5 LAGs can be configured to operate as a
load-balancing group. In this mode, traffic load is distributed among different
ports assigned as members of a LAG, according to user-configured distribution
method. When LACP is enabled for a load-balancing LAG, the STBY LACP option is
not in use.
Port Combinations
Below are the port combinations allowed for load-balancing link aggregation
groups:
• E5-GBE-20 card: the ports must belong to the same 10-port group (ports 1–
10 or ports 11–20) on the same card
• E5-10GBE-2:
 Same card
 Different cards
 Mix of the above (some LAG ports may reside on the same card and some
– on a different one)
• E5-MC-4 and E5-MC-SFP-P-4: the ports must belong to the same card.
Scale
ETX-5 supports up to 44 LAGs of any type (protection or load-balancing).
However, the following limitations apply to the different port types:
• GbE ports on E5-GBE-20 cards – up to 40 load-balancing LAGs
• 10GbE ports on E5-MC-4, E5-MC-SFP-P-4 and E5-10GBE-2 cards – up to 8
load-balancing LAGs.
Traffic Distribution
TLAG traffic distributed across LAG members according to the following criteria:
• MAC SA
• MAC DA
• MAC SA + MAC DA
• IP SA (default)
• IP DA
• IP SA + IP DA
• MAC SA + MAC DA + IP SA + IP DA.
All load-balancing LAGs on the same E5-GBE-20 card must use the same
distribution method.
All load-balancing LAGs with 10GbE ports (E5-10GBE-2, E5-MC-4 and E5-MC-SFP-
P-4 cards) must use the same distribution method.

Fail Criteria (Minimum Links)

ETX-5 allows you to set a minimum number of active physical links in a load-
balancing LAG. When the number of active ports falls below the configured value
(1–4), the LAG is declared failed.
Note An active link is a link a physical layer status OK and synchronized LACP (if LACP is
enabled for the LAG).
Traffic Management
This section details traffic management conventions for load-balancing LAG
traffic.
GbE Ports
For load-balancing LAG on GbE ports, traffic distribution and load balancing are
performed after queuing.
SP 1
SP 2
SP 3
SP4
WFQ 1
WFQ 2
WFQ 1
WFQ 3
WFQ 2
WFQ 4
WFQ 3 GbE Port
WFQ 4
SP 1 WFQ 5
LAG Traffic
SP 2 WFQ 6
Distribution
SP 3 WFQ 7
SP4 WFQ 8
WFQ 1 GbE Port

Level-1 SE
WFQ 2
WFQ 3
Shapers
WFQ 4
Level-0 SEs
Figure 7-6. Traffic Distribution for Load-Balancing LAG on GbE Ports
Note When ETX-5 performs L3 forwarding, the source MAC distribution method uses
the ingress port frame MAC address (MAC of the ingress router interface). This
means that SA MAC traffic distribution is not available (single MAC).
10GbE Ports
For load-balancing LAG on 10GbE ports, traffic distribution and load balancing are
performed before queuing.

SP 1
SP 2
SP 3
SP4
WFQ 1
WFQ 2 10GbE Port
WFQ 3
WFQ 4
LAG Traffic SP 1
Distribution SP 2
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3 10GbE Port
Shapers
WFQ 4
Level-0 SEs
Figure 7-7. Traffic Distribution for Load-Balancing LAG on 10GbE Ports
Note When ETX-5 performs L3 forwarding, the destination MAC distribution method
uses the egress port frame MAC address (MAC of the egress router interface).
This means that DA MAC traffic distribution is not available (single MAC).
Load-balancing LAG for 10GbE ports (main or I/O cards) uses a single queue block
per member port. Each queue block has eight queues.
Only the first queue block in a queue group (0/1) can be used as a port queue
block. This means that all flows with egress port at load-balancing LAG must have
destination queue block 0/1 only.
Policing
For load-balancing LAGs over 10GbE ports on I/O cards, port policers are
supported at port level, and not at the LAG level.
When a policer is applied to a flow, using an I/O 10GbE load-balancing LAG as an
ingress port, the policer is applied to each of the 10GbE port members of the
LAG. The user must adjust the policer rate, according to the number of ports and
Rx distribution requirements.
Load-Balancing LAG
1/1
100 Mbps Policer
1/2
E5-10GBE-2 Card
A. User Configuration

Load-Balancing LAG
1/1 100 Mbps Policer
1/2 100 Mbps Policer

E5-10GBE-2 Card
B. Actual Configuration
Figure 7-8. Policer for Load-Balancing LAG on 10GbE Ports
Shaping
Aggregate egress for load-balancing LAG can be shaped at the LAG level to the
maximum rate of 10 Gbps, using a level-1 shaper.
Configuring a LAG
This section explains how to define a link aggregation group (LAG) and enable link
aggregation control protocol (LACP). ETX-5 supports up to 44 LAGs.
LAG is defined with two Ethernet ports bound to the group. LAG serves as a
logical port with all relevant port attributes (queue block profile, classification
key, L2CP profile, etc). Service flows to and from the LAG, use the LAG as their
ingress/egress port.
LACP Traffic
To ensure correct distribution of LACP traffic among the members of the LAG,
you must configure an L2CP profile with peer action at the port or flow level. (See
Layer 2 Control Protocol in chapter 8.3) The peer must be directed to the MAC
address (01-80-c2-00-00-02).
When configuring the L2CP profile at the flow level, the flow must have the
following attributes:
• Ingress port – LAG
If you use the flow only to peer the LACP frames and do not need to forward the
Note When LAG is used, it recommended to always have LACP enabled.
Figure 7-9 illustrates flows in inter-card LAG between two main cards. LACP flow
can be optionally dropped.

Flow 1*
Port
A/X (LACP)
Flow 2 Any
LAG (Data) Port
Port Flow 3
B/X (Data)
* Flow 1 can be dropped, if unnecessary
Figure 7-9. LAG between Main Cards
Special Considerations for I/O Cards

This section describes special requirements that must be followed when creating
LAG on I/O cards.
LAG/SAP Connection
When configuring LAG between ports on the E5-GBE-20 or E5-10GBE-2 cards,
follow these guidelines for establishing flows between the LAG and the SAP:
• Intra-card LAG: Connect LAG to a SAP, belonging to the first 10-port group
(SAP slot/1/x)
LACP SAP LACP

Port 1/1/X Any
1/2 Flow Flow Port
LAG Data Data

Flow Flow
SAP
Port 1/1/X Any
1/3 Port
Data
Flow
Figure 7-10. LAG-SAP Connection in Intra-Card LAG
• Inter-card LAG for E5-GBE-20 cards:

 LAG between ports belonging to the first ten-port group (1–10): Connect
LAG to a SAP, belonging to the first 10-port group (SAP slot/1/x)

LACP SAP LACP

Port 1/1/X Any
1/2 Flow Flow Port
LAG Data Data

Flow Flow
SAP
Port 1/1/X Any
2/3 Port
Data
Flow
Figure 7-11. LAG-SAP Connection in Inter-Card LAG over Ports 1–10 in E5-GBE-20 Cards
 LAG between ports belonging to the second ten-port group (11–20):

Connect LAG to a SAP, belonging to the second 10-port group
(SAP slot/2/x)
LACP SAP LACP

Port 1/2/X Any
1/11 Flow Flow Port
LAG Data Data

Flow Flow
SAP
Port 1/2/X Any
2/12 Port
Data
Flow
Figure 7-12. LAG-SAP Connection in Inter-Card LAG over Ports 11–20 in E5-GBE-20 Cards
• Inter-card LAG for E5-10GBE-2 cards:

 LAG between ports 1 and 1: Connect LAG to a SAP, belonging to the first
10-port group (SAP slot/1/x)
LACP SAP LACP

Port 1/1/X Any
1/1 Flow Flow Port
LAG Data Data

Flow Flow
SAP
Port 1/1/X Any
2/1 Port
Data
Flow
Figure 7-13. LAG-SAP Connection in Inter-Card LAG over Ports 1 and 1 in E5-10GBE-2 Cards
 LAG between ports 2 and 2: Connect LAG to a SAP, belonging to the

second 10-port group (SAP slot/2/x)

LACP SAP LACP

Port 1/2/X Any
1/2 Flow Flow Port
LAG Data Data

Flow Flow
SAP
Port 1/2/X Any
2/2 Port
Data
Flow
Figure 7-14. LAG-SAP Connection in Inter-Card LAG over Ports 2 and 2 in E5-10GBE-2 Cards
Note • The same rules apply to flows carrying LACP traffic from LAG to SAP.
• Always leave the mirror SAPs located on the second I/O card unused (i.e. have
no flows attached to them). These SAPs serve as internal peers for SAPs which
are used by the LACP and data flows.
Point-to-Point Flows
ETX-5 does not support point-to-point flows between ports that belong to the
same 10-port group. In the same manner, point-to-point flows from a LAG to a
port which is in the same 10-port group as one of the LAG members is not
allowed. For example:
• Permitted: Flow from the LAG on port 1/2 and port 3/2 to port 1/15.
Flow 1 SAP Flow 2

Port Any
(LACP) 1/1/1 (LACP)
1/2 Port
LAG Flow 3 Flow 4

(Data) (Data)
SAP
Port 1/1/2 Port
3/2 1/15
Flow 5
(Data)
Figure 7-15. Permitted PtP Flow for LAG
• Not permitted: Flow from the LAG on port 1/2 and port 3/2 to port 1/3.

Flow 1 SAP Flow 2

Port Any
(LACP) 1/1/1 (LACP)
1/2 Port
LAG Flow 3 Flow 4

(Data) (Data)
SAP
Port 1/1/2 Port
3/2 1/3
Flow 5
(Data)
Figure 7-16. Not Permitted PtP Flow for LAG
 To configure the LAG:

1. Navigate to configure port lag 1–44.
The config>port>lag(1–44)# prompt is displayed.
Assigning an admin key to the admin-key { fast-ethernet | You must define admin key before
LAG to indicate the port speed giga-ethernet | ten-giga-ethernet } binding ports to the LAG. If the
admin-key setting does not match
the port type, LAG configuration will
fail.
For copper ports, autonegotiation
must be either disabled or
configured to a value (rate or
capability) matching the admin-key
setting.
Defining anchor port for load- ancor-port <slot/port >

balancing LAG
Adding a port to the LAG bind etherent <slot/port > no bind removes a link from the LAG
Selecting classification key classification-key [ {vlan }] [{ inner- See the Classification section in
vlan }] [ { p-bit }] [ { ip-precedence
Chapter 8 for description of
}] [ { ip-dscp }]
classification keys available for
directly- and indirectly-attached
ports

Defining sharing method for LAG distribution-method [src-mac | src-mac – Distribution according to
traffic load dest-mac | src-and-dest-mac |src-ip source MAC address. When ETX-5
| dest-ip | src-dest-mac-ip} performs L3 forwarding (routing),
this method cannot be used for
load-balancing GbE LAG.
dest-mac –Distribution according to
destination MAC address. When ETX-
5 performs L3 forwarding (routing),
this method cannot be used for
load-balancing 10GbE LAG.
src-and-dest-mac – Distribution
according to source and destination
MAC addresses
src-ip – Distribution according to
source IP address
dest-ip – Distribution according to
destination IP address
src-dest-mac-ip – Distribution
according source and destination
MAC and IP addresses
Assigning L2CP profile l2cp profile <l2cp profile name> no l2cp profile removes L2CP profile
association source and destination
MAC and IP addresses
Enabling LACP and setting LACP lacp [tx-activity {active | passive}] tx-activity:
parameters: operation mode [tx-speed {slow | fast}] • active – LAG interface periodically
(active or passive) and time to [sys-priority <sys-priority>] transmits LACP frames (LACPDUs)
wait before sending LACP frames to all links with LACP enabled
(long or short)
• passive – LAG interface does not
initiate the LACP exchange, but
replies to received LACPDUs.
tx-speed:
• slow – Three seconds
• fast_– 90 seconds.
• no lacp disables LACP protocol.
It is recommended to set the
tx-activity as follows:
• ETX-5 – active
• Opposite device – passive.
Defining a minimum number of minimum-link-number <1–4>

active links in a load-balancing
LAG
Defining LAG operation mode mode { redundancy | load-balance} redundancy – Link redundancy LAG
load-balance – Load-balancing LAG

Assigning a queue group profile queue-group profile <profile name> See the Quality of Service (QoS)
section in Chapter 8 for description
of queue groups and their elements.
no queue-group removes queue
group association
Associating a policer profile with policer-profile <policer-profile- Policer profiles can be bound,
the LAG name> unbound or replaced with another
no policer-profile profile on-the-fly.
Policer profile with traffic type “all”
cannot be bound to a LAG.
Policer profile with traffic type
“unknown-unicast” cannot be bound
to a LAG consisting of Ethernet ports
on I/O cards.
no policer-profile removes
association with policer profile.
Administratively enabling LAG no shutdown shutdown disables the LAG
Selecting Ethertype for LAG tag-ethernet-type <value> See the Ethertype section in
Chapter 8 for description of
Ethertype values available for
directly- and indirectly-attached
ports.
no tag-ethernet-type removes
Ethertype association
Assigning a name name <string> no name removes LAG name
Displaying bound ports show bind
Displaying LAG status show status
Displaying the LACP statistics show lacp-statistics ethernet

<slot/port>
Displaying LACP status show lacp-status ethernet

<slot/port>
Displaying LAG statistics show statistics
Deleting the LAG

Before deleting the LAG verify that:
• A queue group profile is removed from the LAG.
• All ingress and egress flows attached to the LAG are either disabled or
deleted.
• The LAG is disabled.

 To delete the LAG:

• At the config>port# prompt, enter no lag(1–44)#.
Displaying LAG Members

You can display all ports bound to the current LAG.
 To display LAG members:

• At the config>port>lag(1–44) #prompt, enter show bind.
The higher level section displays the current LAG and the lower level
section displays slot/port of the LAG members.
ETX-5>config>port>lag(5)$ show bind
Higher Layer
-----------------------------------------------------------------------------
0/5
0/5
Lower Layer
-----------------------------------------------------------------------------
Ethernet 6/3
Ethernet 6/4
=============================================================================
Displaying LAG Status

You can display current status of existing link aggregation group.
 To display LAG status:

• At the config>port>lag(1–44) #prompt, enter show status.
The LAG status is displayed.
ETX-5>config>port>lag(1) show status
Group
Name : <lag_1>
Administrative Status : {up}
Operational Status : {up}
MAC Address : 11:22:33:44:55:66
Links
Port Admin Oper LACP Protection
main-a/1 up up sync active
main-a/2 up up out-of-sync active
The LAG status screen provides information on the current state of the
aggregation group and individual group members.
Displaying LACP Status

You can display the current status of LACP for each LAG member.

 To display LACP status:

• At the config>port>lag(1–44) #prompt, enter show lacp-status ethernet
<slot/port>.
The LACP statistic counters are displayed.
ETX-5>config>port>lag(1)$ show lacp-status ethernet main-a/1
Ports
-----------------------------------------------------------------------------
Actor Partner
Port Number : 45 167
Port Priority : 1000 1000
System ID : 00-00-01-02-02-03 00-00-09-08-07-44
System Priority : 7 8000
Operational Key : 1 1
Activity : active passive
Timeout : short long
Synchronized : yes yes
Collecting : yes yes
Distributing : yes yes
The LACP status screen provides information on current state of the local
(actor) and remote (partner) interfaces in an LACP exchange.
Table 7-2. LACP States
Counter Description
Actor Local device participating in LACP negotiation
Partner Remote device participating in LACP negotiation
Activity Actor or partner's port activity. Passive indicates the port's preference
for not transmitting LAC PDUs unless its partner's control value is Active.
Active indicates the port's preference to participate in the protocol
regardless of the partner's control value.
Timeout LACP timeout preference. Periodic transmissions of LACP PDUs occur at

either a slow or fast transmission rate, depending upon the expressed
LACP timeout preference (Long Timeout or Short Timeout)
Synchronized If the value is Yes, the link is considered synchronized. It has been
allocated to the correct link aggregation group, the group has been
associated with a compatible aggregator, and the identity of the link
aggregation group is consistent with the system ID and operational key
information transmitted. If the value is No, the link is not synchronized.
It is currently not in the right aggregation.
Collecting Yes indicates collection of incoming frames on the link is currently

enabled and is not expected to be disabled. Otherwise, the value is No.
Distributing No indicates distribution of outgoing frames on the link is currently

disabled and is not expected to be enabled. Otherwise, the value is Yes.

Displaying LACP Statistics

You can display current LACP statistics for each LAG member.
 To display LACP statistics:

• At the config>port>lag(1–44) #prompt, enter show lacp-statistics ethernet
<slot/port>.
The LACP statistic counters are displayed.
ETX-5>config>port>lag(1)$ show lacp-statistics ethernet main-a/1
Rx LACP Frames : 5,000

Rx Marker Frames : 8,000
Rx Unknown Frames : 11,000
Rx Illegal Frames : 12,000
Tx LACP Frames : 5,000
Tx Marker Response Frames : 10,000
Table 7-3. LACP Statistic Counters
Counter Description
Rx LACP Frames Number of valid LACP PDUs received
Rx Marker Frames Number of valid Marker PDUs received

Rx Unknown Frame Number of unrecognized packet errors
Rx Illegal Frames Number of invalid packets received
Tx LACP Frames Number of valid LACP PDUs transmitted
Tx Marker Response Frames Number of valid Marker Response PDUs received
Displaying LAG Statistics

You can display running statistics for any link aggregation group.
 To running statistics for LAG:

• At the config>port>lag(1–44) #prompt, enter show statistics running.
The LAG statistic counters are displayed.
ETX-5>config> port>lag(10)$ show statistics running
Rates Sampling Window

-----------------------------------------------------------------------------
Window Size [Min.] : 15
Window Remain Time [Min.] : 11
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
FCS Errors 0 --
Error Frames 0 --
L2CP Discarded 0 --
CFM Discarded 0 --
ACL Discarded 0 --
MAC Overflow 0 --
Unknown Protocol Discarded 0 --
Undersize Frames 0 --
Jabber Errors 0 --
Discard Frames -- 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
1519-Max Octets 0
2048-Max Octets 0 0
Rate of Total
-----------------------------------------------------------------------------
Port Rx Total Frames Tx Total Frames
(%) (%)
-----------------------------------------------------------------------------
Ethernet main-a/1 0 0
Ethernet main-a/2 0 0

Table 7-4. LAG Statistic Counters
Description
Parameter
Rx Tx
Total Frames Total number of received packets, Total number of transmitted packets
including packets with bad CRC,
and excluding short packets and
packets dropped due to Rx MAC
overflow
Total Octets Total number of received octets, Total number of transmitted octets
including FCS and bad packet
octets, and excluding framing bits
Total Total FPS Rx rate Total FPS Tx rate

Frames/Sec
Total Bits/Sec Total BPS Rx rate Total BPS Tx rate
Minimum Minimum BPS Rx rate Minimum BPS Tx rate

Bits/Sec
Maximum Maximum BPS Rx rate Maximum BPS Tx rate

Bits/Sec
Unicast Frames Total number of received good Total number of transmitted good unicast packets
unicast packets, excluding packets
with bad CRC and short packets
Multicast Total number of received multicast Total number of transmitted good multicast
Frames packets, excluding packets with packets
Broadcast Total number of received Total number of transmitted good broadcast

Frames broadcast packets, excluding packets
packets with bad CRC and short
packets
FCS Error The number of received packets –

Frames with bad CRC
Error Frames Total number of received bad –

packets, including packets with
L2CP Discarded The number of packets discarded –

by the L2CP processing mechanism
CFM Discarded The number of packets discarded –

by the CFM processing mechanism
ACL Discarded The number of packets discarded –

by the ACL processing mechanism
MAC Overflow The number of packets discarded –

due to the FIFO overflow

Description
Parameter
Rx Tx
Unknown The number of discarded –

Protocol unidentified packets
Discarded
Undersize The number of received well-

Frames formed frames that were less than
64 octets long, excluding framing
bits and including FCS octets
Jabber Frames The number of received frames

that exceeded the maximum
allowed packet size and contained
an CRC error, or were not well
formed
Discard Frames – The number of frames dropped in Tx MAC
Oversize Frames Total number of received packets Total number of transmitted packets that exceeded
that exceeded the maximum the maximum allowed packet size
allowed packet size
64 Octets Total number of received packets Total number of transmitted packets (including bad
(including bad packets) that were packets) that were 64 octets in length, excluding
64 octets in length, excluding framing bits and including FCS octets
framing bits and including FCS
octets
65–127 Octets Total number of received packets Total number of transmitted packets (including bad
(including bad packets) that were packets) that were 65–127 octets in length,
65–127 octets in length, excluding excluding framing bits and including FCS octets
framing bits and including FCS
octets
128–255 octets in length, excluding framing bits and including FCS octets
excluding framing bits and
512–1023 Total number of received packets Total number of transmitted packets (including bad
Octets (including bad packets) that were packets) that were 512–1023 octets in length,

Description
Parameter
Rx Tx
1024–1518 Total number of received packets Total number of transmitted packets (including bad
1519-2047 Total number of received packets Total number of transmitted packets (including bad
2048-Max Total number of received packets Total number of transmitted packets (including bad
Octets (including bad packets) that were packets) that were 2048 to maximum allowed size
2048 to maximum allowed size octets in length, excluding framing bits and
octets in length, excluding framing including FCS octets
bits and including FCS octets
Rate of Total Percentage of frames received by Percentage of frames transmitted by the LAG
the LAG member from total member from total frames transmitted by all
frames received by all bonded bonded members
members
Examples
Examples below illustrate how to configure different types of link aggregation
groups.
Inter-Card LAG between Two Main Cards

LAG configuration involves configuring a LAG group containing the two LAG port
members and the LAG group attributes.
To peer LACP frames, configure a L2CP profile with peer action for the LACP
address on the LAG ports or on a dedicated flow with untagged classifier from
the LAG. As the only purpose of this flow is to peer LACP traffic, you can discard
its traffic by using a drop action.
Data-carrying flows use the LAG as their ingress or egress ports.
 To configure inter-card LAG between two main cards:

1. Enable the relevant main card ports.
2. Configure LAG 1 for port 2 on main card A and port 4 on main card B.
3. Configure two classifier profiles:
 Untagged for LACP peer flow
 VLAN 100 for user data flows
4. Configure L2CP profile with peer action on the LAG ports (as configured in #2
above) for the LACP address (01-80-c2-00-00-02).

5. Configure these flows:

 Flow 1 from port 3 on main card A to LAG 1 with VLAN 100 classification
 Flow 2 from LAG 1 to port 3 on main card A with VLAN 100 classification.
Port
A/2
Flow 1 Port
LAG (Data) A/3
Port Flow 2
B/4 (Data)
Figure 7-17. Inter-Card LAG between Two Main Cards
#***************************Configuring_L2CP_Profile*************************
config port l2cp l2cp1
mac 01-80-c2-00-00-02 peer
exit all
#***************************Assigning_L2CP_Profile_on_LAG_Ports**************
config port ethernet main-a/2 l2cp profile l2cp1
config port ethernet main-b/3 l2cp profile l2cp1
#*****************************Enabling_Ethernet_Ports************************
config port ethernet main-a/2
pm-enable
no shutdown
exit all

pm-enable
no shutdown
exit all

pm-enable
no shutdown
exit all
#*****************************Configuring_LAG********************************
config port lag 1
admin-key ten-giga-ethernet
queue-group profile q_group_2_level_default
lacp tx-activity active tx-speed slow
no shutdown
exit all
#***************************Assigning_Queue_Group_Profile********************
#***************************Configuring_Classifier_Profiles******************


match untagged
exit all

match vlan 100
exit all
config flows flow 2

classifier class100
egress-port lag 1 queue-map-profile QueueMapDefaultProfile block 0/1
pm-enable
no shutdown
exit all
config flows flow 3

classifier class100
0/1
ingress-port lag 1
pm-enable
no shutdown
exit all
#*********************************End****************************************
Inter-Card LAG between Two I/O Cards

LAG configuration involves configuring a LAG group containing the two LAG port
members and the LAG group attributes.
Note The I/O card ports combined in LAG must belong to the same 10-port group. See
Inter-Card LAG above.
To peer LACP frames, configure a dedicated flow with untagged classifier from
the LAG. This flow must have an L2CP profile attached to it. The L2CP profile must
have a peer action for the LACP address. As the only purpose of this flow is to
peer LACP traffic, you can discard its traffic by using a drop action on the flow.
Follow the LAG/SAP Connection guidelines described above when directing flows
from the LAG to the relevant SAPs. Keep in mind that the mirror SAP 3/1/1 and
SAP 3/1/2 located on I/O card in slot 3 must be left unused (i.e. have no flows
attached to them). These SAPs serve as internal peers for SAP 1/1/1 and SAP
1/1/2, which are used by the LACP and data flows.
Data-carrying flows use the LAG as their ingress or egress ports.
 To configure inter-card LAG between two I/O cards:

1. Enable the relevant I/O and main card ports.
2. Configure LAG 1 for port 2 on I/O card 1 and port 2 on I/O card 3.
3. Attach queue group profiles to all relevant ports and SAGs.
4. Configure three classifier profiles:

 Untagged for incoming LACP peer flow

 Match All for outgoing LACP peer flow
 VLAN 100 for user data flows
5. Configure L2CP profile with peer action for the LACP address (01-80-c2-00-
00-02).
6. Configure six flows:
 Flow 1 from LAG 1 to SAP 1/1/1 with untagged classification for incoming
LACP data
Discard the flow data.
 Flow 2 from SAP 1/1/1 to port 3 on main card A with Match All
classification for outgoing LACP data.
 Flow 3 from LAG 1 to SAP 1/1/2 with VLAN 100 classification
 Flow 4 from SAP 1/1/2 to port 13 on I/O card 1 with Match All
classification
 Flow 5 from port 13 on I/O card 1 to LAG 1 with VLAN 100 classification.
Flow 1 SAP Flow 2

Port 1/1/1 Port
1/2 (LACP) (LACP) A/3
LAG Flow 3 Flow 4

(Data) (Data)
SAP
Port 1/1/2 Port
3/2 1/13
Flow 5
(Data)
SAP
3/1/1
Leave
Unused
SAP
3/1/2
Figure 7-18. Inter-Card LAG between Two I/O Cards
config port ethernet 1/13
no shutdown
exit all

no shutdown
exit all


no shutdown
exit all

no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_LAG********************************
config port lag 1
admin-key giga-ethernet
bind ethernet 1/2
bind ethernet 3/2
lacp tx-activity active tx-speed slow
no shutdown
exit all
#*********************************End****************************************
#***************************Assigning_Queue_Group_Profiles*******************
#*********************************End****************************************
match untagged
exit all
config flows classifier-profile classAll match-any

match all
exit all

match vlan 100
exit all
#*********************************End****************************************
config port l2cp l2cp1
mac 01-80-c2-00-00-02 peer
exit all
#*********************************End****************************************
config flows flow 1
classifier classutg
ingress-port lag 1

l2cp profile l2cp1

drop
no shutdown
exit all
config flows flow 2

classifier classAll
0/1
no shutdown
exit all
config flows flow 3

classifier class100
ingress-port lag 1
no shutdown
exit all
config flows flow 4

classifier classAll
no shutdown
exit all
config flows flow 5

classifier class100
no shutdown
exit all
#*********************************End****************************************

detected.
Message Possible Cause Corrective Action
Bind failed: Ports in LAG You attempted to configure a LAG member for Bind the LAG to ports on
must reside on same card ports on two different card types. the same card type.
type
Bind failed: Services are You attempted to bind an Ethernet port that has Remove the flows that are
configured on port flows assigned to it. assigned to the port before
binding it to the LAG.
Error : Exceeded You have exceeded the maximum number of Lags Remove LAGs so that there
maximum number of that is supported per chassis. are no more than 44 LAGs
LAGs per chassis.
Error : Given port is not a You attempted to remove an Ethernet port that You may only remove
LAG member was not a member of the LAG. Ethernet ports from a LAG
if they are bound to it.
Error : Invalid LAG ID You configured a LAG with an ID that is beyond Configure the LAG ID within
the range of 1–44. the range of1–44.
Error : Invalid port The port you have attempted to bind to the LAG Bind a port with the same
Bandwidth does not have the same bandwidth capacity as bandwidth capacity as the
the LAG. LAG or change the admin-
key of the LAG according to
the required bandwidth
capacity.
Error : Invalid port You attempted to bind a port that has an invalid Bind a port with a valid
number (nonexistent) number to the LAG. (existing) number to the
LAG.
Error : LAG is enabled You attempted to delete or modify an active LAG. Shut down all flows and the
LAG and then change the
required parameters in the
LAG.
Error : LAG members The same Ethernet port has been bound twice to Bind a different Ethernet
duplicated a LAG. port to the LAG.
Error : Membership is not You did not bind any ports to the LAG. Bind a port to the LAG
specified before activating it.

Error : Number Of Ports You attempted to bind more than the supported Bind only two ports to the
Exceeds Maximum number of ports to the LAG. The maximum LAG protection or up to
number that is supported is two for LAG four to the LAG load
protection and four for LAG load balancing. balancing.
Error : Port already used You attempted to select a port that has already Use a port that is not being
in another LAG been used in another LAG. used in another LAG.
LAG removal failed: used You attempted to remove a LAG that is currently Remove this LAG from the
by destination port being used by a destination port mirroring mirroring session before
mirroring port session. removing the LAG.
LAG removal failed: used You attempted to remove a LAG that is currently Remove this LAG from the
by source port mirroring being used by a source port mirroring session. mirroring session before
session removing the LAG.
No shutdown failed: L2CP You did not attach an LACP profile to the Attach LACP profile to the
profile must be aggregation group. aggregation group.
configured when LACP is
enabled
No shutdown failed: L2CP You did not configure an L2CP profile that To enable LACP for the LAG,
profile must define a peer specifies peer action for MAC 0x02. This L2CP configure an L2CP profile
action for LACPDUs. profile must be bound either directly to the LAG that specifies peer action
port members or to an untagged flow whose for MAC 0x02.
ingress port is the LAG..
No shutdown failed: LACP You did not enable the link aggregation protocol Enable LACP before
must be enabled when (LACP). Therefore, inter-card LAG cannot be activating inter-card LAG.
LAG is between 2 cards activated.
No shutdown failed: LAG You attempted to activate more than two LAG Bind only two LAG members
must have exactly 2 members. The maximum number of LAG members to LAG protection.
members that is supported in LAG protection is two.
Port cannot be bound, You attempted to bind a port that is already Only bind ports that are not
since it is already used by being used by a destination mirroring port. being used by a destination
destination mirroring port port mirroring session.
Port cannot be bound, You attempted to bind a port that is already Only bind ports that are not
since it is already used by being used by a source mirroring port. being used by a source port
source mirroring port mirroring session.

7.3 Ethernet Ring Protection (ERP)

A G.8032 Layer-2 Ethernet ring is used by ETX-5 for traffic protection. This
technology builds a logical ring, defined as a set of IEEE 802.1-compliant bridges,
and protects against link and node failures. ETX-5 supports 63 rings (major and
sub-rings) per shelf.
Standards
ITU-T G.8032v2, Y.1731.
Benefits
G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and
prevent loops at the Ethernet layer.
Factory Defaults
No Ethernet protection rings are configured in the system by default.
Ethernet Ring Protection 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)
functions. It is independent of any physical-layer technologies and can be utilized
in any carrier network.
In ERP every ring node uses heartbeat messaging to determine availability of its
neighbor. When a link failure occurs, it is detected via LOS or heartbeat R-APS
messaging. Upon failure, node forwarding information is recalculated to ensure
that data traffic reaches its destination, using an alternative path.
Ring ports can reside on Ethernet ports belonging to the same main or I/O card,
providing port redundancy. In addition, they can reside on ports belonging to
different cards, providing port and card redundancy. In total, ETX-5 supports up
to 63 major rings and sub-rings.
Notes • Recommendation to provide sub-50ms protection and recovery switching for

Ethernet traffic in a ring topology, and at the same time ensure that there are
no loops formed at the Ethernet layer.
G.8032v1 supports a single ring topology and G.8032v2 supports multiple
rings/ladder topology
• Switchover time using physical layer indication only, may exceed 50 ms due to
the link failure detection time requirements in the IEEE 802.3 standard. To
achieve a sub-50 ms switchover, use OAM MEP.
Ring Topology
ETX-5 supports ITU-T G8032 ring topologies, for example:
ETX-5 Ethernet Ring Protection (ERP) 7-35

Single Ring
Figure 7-19. Single Ethernet Ring
Sub Rings Topology
Figure 7-20. Interconnected Ethernet Rings
G.8032 specifies support for a network of interconnected rings. (as

shown in the above figure)
Sub-ring with an R-APS virtual channel: It is "tunnel" for the sub R-APS messages
from one interconnection node to the other interconnection over the Major
ring.ETX-5 supports
.
• Up to 63 G.8032 Rings are supported per device (Main rings + sub rings).
• Up to 62 sub rings per ring
7-36 Ethernet Ring Protection (ERP) ETX-5

• R-APS virtual channel enable – The R-APS virtual channel is the R-APS channel
connection between two interconnection nodes of a sub-ring over a network
or other ring.
• Multi-ring/ladder network
• Revertive/ Non-revertive mode, after the condition that caused the switch
has been cleared
• Administrative commands: Forced Switch (FS), Manual Switch (MS) for
blocking a particular ring port
• Flush FDB (Filtering database) Logic, which significantly reduces amount of
flush FDB operations in the ring
• Support of multiple ERP instances on a single ring
In a stable state the rings have one RPL owner that prevent the traffic from
looping in the network. When a non-shared link fails in the network, the RPL
owner that controls the ERPS instance containing that link unblocks the RPL port
while the distant RPL port, which is not a part of this instance, remains blocked.
Follow these guidelines, when configuring major and sub-rings:
• The sub-ring number (index) must be lower than the number of the major
ring it is assigned to.
• R-APS VLAN and all data VLANs used by the sub-ring must be added as “Data
VLANs” to all major rings (including the interconnection nodes).
• .
The following example illustrates the correct VLAN distribution for major and sub-
rings.
Major Ring
A B
Ring 10
Ring 2
G
Sub-Ring
Figure 7-21. VLAN Distribution for Major and Sub-Rings
• Ring 10 (major ring)

 R-APS VLAN 777
 Data VLAN 100
• Ring 2 (sub-ring)
 R-APS VLAN 888

 Data VLAN 200

• Node A, node B
 R-APS VLAN 777
 Data VLANs 100, 888, 200
• Node D (interconnection)
 Ring 10 VLANs
 R-APS VLAN 777
 Data VLANs 100, 888, 200
 Ring 2 VLANs
 R-APS VLAN 888
 Data VLAN 200
• Node G
 R-APS VLAN 888
 Data VLAN 200.
Multiple (Virtual) Rings Definitions

The ETX-5 supports multiple ERP instances on the same physical ports, where:
• An ERP instance comprises a set of “protected” VLANs
• Multiple ERP instances can be configured on a single physical ring
• An ERP instance protects a subset of the VLANs that transport traffic over
the same physical ring
• Each ERP instance is independent of other ring instances
Figure 7-22. Multiple Ring Instances
Multiple Ethernet rings, allow the creation of many ring instances over the same
physical infrastructure. Multiple rings provide better bandwidth utilization in the
“Idle” ring states. In addition, they can be used to improve deployment flexibility
by creating multiple sub-rings.

A/3
A/1 B/2
B1
Site 2
A/1 A/1
A/3 B/1 A/2 A/3

B1 B1
Site 1 Site 3
Figure 7-23. Improved Bandwidth Utilization

Site 5
A/1 B/2
B1 B2
A/3
Site 4 Site 6
A/1 B/2 A/1 B/2

B1 B1
A/3 A/3
A/3
A/1 B/2
B1
Site 2
A/1 A/1
A/3 B/1 A/2

B1 B1
Site 1 Site 3
Figure 7-24. Improved Deployment Flexibility
R-APS Messaging
Ethernet ring protection is achieved by means of a dedicated protocol,
Automated Protection Switching (APS). Every ring link is bound by two adjacent
nodes. At any time, traffic flows on all, but one of the ring links. This link is called
the ring protection link (RPL). Under normal conditions this link is blocked. RPL is
controlled by a single node called an RPL owner, which prevents traffic from using
the RPL. When a failure is detected, the RPL owner unblocks the RPL port,
allowing the RPL to be used for traffic.
R-APS messages require a designated transmission channel (R-APS channel),
which is separated from the service traffic channel. An R-APS channel is
configured using a separate dedicated VLAN to enable handling of the R-APS
messages differently from the service traffic. An R-APS channel and service traffic
blocking is performed via VID filtering by the bridge.
Mechanism of Operation
Every failure along the ring triggers an R-APS Signal Fail (SF) message in both
directions from the nodes adjacent to the failed link. Before sending the R-APS,
these nodes block the ports facing the failed link. On receiving these messages,
the RPL owner unblocks the RPL port. An SF message is triggered even if only one

node adjacent to the failed link recognizes the failure. Moreover, to overcome
scenarios in which link failures are not recognized via LOS (Loss of signal), ERPS
can also use the standard Ethernet OAM 802.1ag Continuity Check Messages
(CCMs) to expose the failure to the two adjacent nodes.
During a recovery phase, when a failed link is restored and a node continually
detects a Clear SF, it sends an R-APS No Request (NR) message and keeps the
failed port blocked. When receiving the R-APS (NR), the RPL owner starts its
Wait-To-Restore (WTR) timer. When that timer expires, it blocks the RPL port and
sends RAPS (NR, RB) (R-APS no request, RPL block blocked) messages in both
directions of the ring. Nodes receiving the R-APS (NR, RB) message flush their
learning table, unblock their blocked ports, and return to idle state.
Figure 7-25 illustrates a stable-state Ethernet ring with blocked RPL to prevent a
loop. Each node is monitored, using Ethernet CCM OAM messages, and the ring
protection is triggered by loss of continuity or server layer failure, as defined in
Y.1731.
Figure 7-25. Fault-Free ERP
Timers
The following timers are used to facilitate ERP operation:
• Wait-to-Restore (WTR) – Period of time used by RPL owner to verify that the
ring has stabilized before blocking the RPL after signal recovery (1 to 12
mins.)
• Guard – Period of time during which all received A-RPS messages are ignored
by the ERP mechanism. This prevents the ring nodes from receiving outdated
A-RPS messages circulating the network (0 to 2000 mSec.).
• Hold-off – Period of time during which the underlying Ethernet layer attempts
to filter out intermittent link faults before reporting them to the ERP
mechanism (0 to 1000 mSec.)..
Administrative Commands
If there is a need to intervene into ERP operation for maintenance or any other
reason, the operator can issue a forced or manual switch command.
• Forced switch command forcefully blocks a particular ring port. It can be
issued even if an SF condition exists on the ring, with multiple force switch
commands supported per ring instance.

• Manual switch command manually blocks a particular ring port with only one
manual switch command per ring instance. It can be overridden by SF
condition or a force switch command.
• Clear switch command clears all existing force and manual switch command
on the ERP.
Note The manual and forced switch commands are temporary commands and do not
permanently change the location of the RPL.
Ring over Load Balancing LAG

Ring protection can be configured over a load balancing LAG. The ring port can be
either a 1GbE or 10GbE port either on the main or IO cards. A LAG is implicitly
configured based on the flows. This type of ring is configured the same as a
standard ring.
 To configure a ring over a load balancing LAG:

1. Create the LAG. See Configuring a LAG.
2. Create the ring. See Configuring ERP.
Service Failure Triggers

Service failure over a ring can be triggered by a physical layer failure based on a
‘minimum links’ configuration. You can configure the minimum number of links for
a ring. If this minimum limit is passed, a service failure is triggered. A service
failure can also be triggered based on OAM: CCM-LOC or RDI.
Note Ring over a protection LAG is not supported.

ETX-5
HQ
ETX-5
Up to ETX-5
40/4 Gbps ETX
Ring
ETX-5
Figure 7-26. Ring over Load Balancing LAG
Configuring ERP
 To configure ERP:
1. In the configure>protection# prompt, enter erp followed by ring number (1–
63) and ring type (major or sub).
An ERP instance with is created and the config>protection>erp(1)#
2. Configure the ERP as illustrated and explained below.
Note no before erp (ERP_number) deletes an ERP instance.
Making the ring compatible with backward-compatibility

previous ERP implementations no backward-compatibility
(VI)
Assigning node to a bridge bridge <1–32>

instance

Assigning VLAN ID to user data data-vlan <1–4094> Using no before data-vlan

no data-vlan removes VLAN ID assignment to
user data.
A VLAN to be used as a data
VLAN for ERP must already exist,
even as an empty entry.
Flows, which are intended for
data VLAN, must be created only
after the data VLAN is added.
Before issuing the no data-vlan
command, verify that all flows,
using this VLAN with the SVI as
their ingress or egress, have
been disabled. For the major
rings, these are flows used by
the East and West ports.
For the sub-ring, these are flows
used by the East port of the sub-
ring, and the East and West
ports of the major ring.
Data VLANs cannot be defined as
tagged egress on ring ports.
Defining bridge port as an East east-port <bridge_port_number> Port type cannot be changed
port of ERP node after ring creation.
Sub-rings have East ports only.
Defining bridge port as a West west-port <bridge_port_number> Port type cannot be changed
port of ERP node after ring creation.
Sub-rings do not have West
ports
Defining ERP node as an interconnection-node Creating an interconnection

interconnection node, sharing no interconnection-node node automatically adds the
more than one ring protected VLAN to all the major
ports by issuing the data-vlan
command at the sub-ring. There
is no need to repeat it at the
interconnection node.
Defining node port type in port-type owner {east | west} owner – RPL owner
relation to RPL owner port-type neighbor {east | west} neighbor – port directly
port-type next-neighbor {east | west} connected to RPL owner
port-type ring-node next-neighbor – port connected

to RPL owner via neighbor
ring-node – regular ring port,
which is not connected to RPL
owner
Configuring dedicated VLAN for r-aps [vlan <1–4094>] [vlan-priority R-APS settings must be the same
R-APS messages <0–7>] [mel <0–7>] for all ring members

Configuring the revertive mode revertive This mode is relevant to the RPL
no revertive owner node.
In the revertive mode, after
condition, causing the switch, is
cleared, traffic is blocked at the
RPL owner and restored to the
working state.
After the node has entered the
pending state in non-revertive
mode, use the Clear command to
exit the state.
no revertive enables
non-revertive mode.
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 relevant CFM
Ethernet OAM service layer no sf-trigger {east | west} parameters have been
configured.
MEPs used for SF propagation
cannot reside on R-APS VLAN;
they must be bound to data
VLANs only.
Administratively enabling the no shutdown To avoid traffic loops, always

ERP interface enable Ethernet ports only after
enabling Ethernet rings.
shutdown disables the ERP.
Connecting previously defined sub-ring <ring_number> This option available for major
sub-ring to a major ring no sub-ring rings only. The sub-ring number
must be lower than the number
of the major ring it is assigned
to. For example, sub-ring 2 can
be connected to major ring 10,
but sub-ring 15 cannot be
connected to major ring 8.

Defining guard and hold-off timers [guard <10–2000>] [holdoff Guard timer is used by the ERP
periods in msec <0–10000] mechanism to prevent ring
nodes from receive outdated R-
APS messages. While the guard
timer is active, all received R-APS
messages are ignored by the
node. The guard timer is
configured in 10-ms steps. Its
recommended value for all ring
nodes is 2 sec.
Hold-off timer is used by
Ethernet layer to filter out
intermittent faults. Faults are
reported to the ERP mechanism
only after the hold-off timer
expires. The guard timer is
configured in 100-ms steps.
Defining wait-to restore period wait-to-restore <60–720> Wait-to-restore timer defines

for RPL owner period of time used by RPL
owner to verify that the ring has
stabilized before blocking the
RPL after signal recovery. The
WTR timer is configured in
60-sec. steps. (1 – 12mins.)
Blocking the East or West port of manual-switch {east-port | west-port } The manual switch command can
a ring node be applied to a single ring node
only. When the command is
active, all ring nodes shift to the
manual switch mode.
Blocking the East or West port of forced-switch {east-port | west-port } The forced switch can be applied
a ring node to any number of nodes in the
ring.
Clearing the existing switch clear

commands
Displaying ERP status show status
Displaying ERP statistics show statistics
Clearing ERP statistics clear statistics
The following marking actions can be performed in the sub-ring level, at the
config>protection>erp(erp_number)>sub-ring(sub-ring_number)# prompt.
Enabling virtual channel over virtual-channel Currently, the virtual channel is

shared link no virtual-channel permanently enabled

Displaying ERP Status

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

• In the config>protection>erp(erp_number)$ prompt, enter show status.
The ERP status is displayed.
ERP Ring : 10 R-APS VLAN : 777 Ring State : Idle
Bridge Number : 1 WTR (Sec) : Stop Of : 120
East Bridge Port : 10 Physical Port : main-a/1 Role : Node

West Bridge Port : 20 Physical Port : main-a/2 Role : RPL
Port State
-----------------------------------------------------------------------------
East Port Status : Forward Signal Fail : No Error
West Port Status : Block R-APS and Data Signal Fail : No Error
Data Vlan
-----------------------------------------------------------------------------
1000..1255,
Figure 7-27. ERP Status, Idle State
ERP Ring : 10 R-APS VLAN : 777 Ring State : Protection

Bridge Number : 1 WTR (Sec) : Stop Of : 120
East Bridge Port : 10 Physical Port : main-a/1 Role : Node-Port

West Bridge Port : 20 Physical Port : main-a/2 Role : RPL
Port State
-----------------------------------------------------------------------------
East Port Status : Forward Signal Fail : No Error
West Port Status : Block R-APS and Data Signal Fail : Server Layer
Data Vlan
-----------------------------------------------------------------------------
1000..1255,
Figure 7-28. ERP Status, Protection State
ERP Ring : 1 R-APS VLAN : 777 Ring State : Idle

Bridge Number : 1
East Bridge Port : 10 Physical Port : LAG 1 Role : Neighbor

West Bridge Port : 20 Physical Port : LAG 2 Role : Node
Port State

-----------------------------------------------------------------------------
East Port Status : Block R-APS and Data Signal Fail : No Error
West Port Status : Forward Signal Fail : No Error
Data Vlan
-----------------------------------------------------------------------------
100

Figure 7-29. ERP Status, Ring over Load Balancing LAG
ERP status provides information on:

 Ring number
 R-APS VLAN number
 Ring state:
 Init – The node is not yet participating in the ring
 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).
 Protection – A failure occurred on the ring. A not-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.
 Pending – The ring is recovering from the failure and the WTR timer is
running
 Bridge number
 WTR status:
 Stop – Timer is inactive, when ERP status is idle, init, or protection
 Run – Timer is active, when the ERP status is pending
o Of – Configured WTR value
 Bridge ports assigned to be East and West ring ports
 Physical ports assigned to the ring ports
 RPL node role:
 Node – 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– This node owns the RPL and blocks or unblocks the RPL as
conditions require. This node initiates the R-APS message exchange.
 East/West Port Status:
 Forward – Port is forwarding data
 Block R-APS and Data – Port is blocked
 East/West Port Signal Fail – Local Signal Failure source:

 Server Layer (signal fail)

 OAM CFM
 No Error
Note If the ERP fails to reach the IDLE state:

• Verify that ring port status is OK.
• Run the show statistics command (see below) and verify that the NR,RB Tx
counters.
• Verify that the WTR timer has expired.
• Make sure that flows, carrying R-APS data, were added after the ERP had been
enabled.
• Verify that all protected sites use the same VLAN for R-APS messages, and the
same MEL value (MD level).
Displaying ERP Statistics

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

• In the config>protection>erp(erp_number)$ prompt, enter show statistics..
The ERP statistic counters are displayed.
ETX-5>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-6. 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.

Counter Description
R-APS NR Message Tx/Rx Total number of R-APS No Request (NR) messages received or
transmitted by East/West port.
Received R-APS No Request message indicates absence of failed ports in
the ring.
Transmitted R-APS No Request message indicates that the node fixed its
failed port.
R-APS NR, RB Tx/Rx Total number of R-APS No Request (NR), RPL Blocked (RB) messages
received or transmitted by East/West port.
Received R-APS No Request, RPL Blocked message indicates that RPL
port is blocked and all other not-failed blocked ports are unblocked in
the ring.
Transmitted from the RPL No Request, RPL Blocked message indicates
that RPL port is blocked.
Total Valid Rx/Tx Total number of valid R-APS messages received or transmitted by
East/West port.
R-APS messages, generated by Force switch or Manual switch, increment
the Total Valid Rx/Tx counter, but are not displayed separately.
Total Errors Rx/Tx Total number of errored R-APS messages received or transmitted by
East/West port
Example
Figure 7-30 and script below illustrate configuration a G.8032v2 ring over main
card ports.
Ethernet
Ring
Fl. 34
Flow 1 SAP
VLAN
Flow 2 Fl. 35 1500
Port 1 VLAN Port 1
Flow 15 1500
Flow 16
East VLAN
SVI 1 SVI 3
Main Ethernet Flow 30 1500 I/O Ethernet
Card A BP 1 BP 3 Card 1
Flow 31 Fl. 36
Bridge
BP 2 BP 4
Fl. 10 SAP Fl. 9
West
Fl. 3 Fl. 4 (RPL Owner) VLAN
500 VLAN
SVI 2 SVI 4 900
Fl. 17 Fl. 18
Port 1 VLAN Port 1

Fl. 32 500
Fl. 33
Fl. 11
Main Ethernet I/O Ethernet

Card B Card 2
Figure 7-30. ERP Configuration

 To configure the ERP:

1. Assign previously configured queue groups to card ports and SAPs.
2. Select classification keys (VLAN + P-bit for the main and I/O card ports.
3. Configure four bridge-type SVIs.
4. Add four bridge ports and bind them to the SVIs.
5. Define bridge port VLAN membership for bridge ports that are not ring
members:
 BP 3 – member of VLAN 1500
 BP 4 – member of VLAN 500
6. Configure the ring:
 BP 1 – East port
 BP 2 – West port
 R-APS VLAN – 777
 Data VLANs – 500, 1500
7. Configure flows for R-APS messages (red flows in Figure 7-30):
 Classifier profile for VLAN 777
 Configure flows 1, 2, 3, 4 between main card ports and BPs
 Configure the color-aware marking profile.
8. Configure data flows (blue flows in Figure 7-30):
 Classifier profiles for VLANs 500, 900 and 1500
 Configure data flows, as illustrated in Figure 7-30
Note VLAN 900 is swapped to VLAN 500 on flow 9. VLAN 500 is swapped to VLAN 900
on flow 11.

#*********************Assigning_Queue_Group_Profiles*************************
exit all
#*********************************End****************************************
#*********************Selecting_Classification_Keys**************************
exit all
#*********************************End****************************************

#***************************Configuring_SVIs*********************************
exit all

exit all

exit all

exit all
#*********************************End****************************************
#*************************Binding_Bridge_Ports_to_SVIs***********************
bind svi 1
no shutdown
exit all

bind svi 2
no shutdown
exit all

bind svi 3
no shutdown
exit all

bind svi 4
no shutdown
exit all
#*********************************End****************************************
#******************** Configuring_VLAN_Membership****************************
config bridge 1 vlan 500 tagged-egress 4
config bridge 1 vlan 500 maximum-mac-addresses 64
config bridge 1 aging-time 300
exit all
config bridge 1 vlan 1500 tagged-egress 3

config bridge 1 vlan 1500 maximum-mac-addresses 64
config bridge 1 aging-time 300
exit all
#*********************************End****************************************
#************************ Configuring_the_Ring*******************************
config protection erp 1 major
bridge 1
east 1
west 2
r-aps vlan 777 vlan-priority 1 mel 1
port-type east node-port

port-type west rpl

wait 120
data-vlan 500
data-vlan 1500
no shutdown
exit all
#*********************************End****************************************
#************************ Configuring_R-APS_Flows****************************
config flows classifier-profile class_R_APS match-any
match vlan 777
exit all
config flows flow 1

classifier class_R_APS
egress-port svi 1
no shutdown
exit all
config flows flow 2

ingress-port svi 1
0/1
no shutdown
exit all
config flows flow 3

egress-port svi 2
no shutdown
exit all
config flows flow 4

ingress-port svi 2
egress-port ethernet main-b/1 queue-map-profile QueueMapDefaultProfile block
0/1
no shutdown
exit all
#*********************************End****************************************
#************************ Configuring_Marking_Profile************************
config qos
marking-profile mark1 classification cos color-aware green-yellow dei-copy
mark 0 green to 0 dei green
exit all
#*********************************End****************************************
#************************ Configuring_Data_Flows****************************
config flows classifier-profile class_900 match-any
match vlan 900

exit all
config flows classifier-profile class_500 match-any

match vlan 500
exit all

match vlan 1500
exit all
config flows flow 9

classifier class_900
pm-enable
no shutdown
exit all

classifier classall
egress-port svi 4
mark all
vlan 500
exit
pm-enable
no shutdown
exit all

ingress-port svi 4
mark all
vlan 900
exit
pm-enable
no shutdown
exit all

egress-port svi 1
pm-enable
no shutdown
exit all

ingress-port svi 1
0/1
pm-enable
no shutdown

exit all

egress-port svi 2
pm-enable
no shutdown
exit all

ingress-port svi 2
0/1
pm-enable
no shutdown
exit all

egress-port svi 1
pm-enable
no shutdown
exit all

ingress-port svi 1
0/1
pm-enable
no shutdown
exit all

egress-port svi 2
pm-enable
no shutdown
exit all

ingress-port svi 2
0/1
pm-enable
no shutdown
exit all



pm-enable
no shutdown
exit all

egress-port svi 3
pm-enable
no shutdown
exit all

ingress-port svi 3
pm-enable
no shutdown
exit all
#*********************************End****************************************
#****************************Enabling_Ports**********************************
exit all
#*********************************End****************************************
detected.
Message Description
Invalid bridge port number Invalid bridge port number is selected
Invalid East port number Invalid East port number is selected
Invalid West port number Invalid West port number is selected
Invalid Guard timer value Invalid Guard timer value is selected
Invalid Holdoff timer value Invalid Holdoff timer value is selected
Invalid R-APS VLAN ID Invalid R-APS VLAN ID value is selected
Invalid R-APS MEL value Invalid R-APS MEL value is selected
Invalid R-APS VLAN priority Invalid R-APS VLAN priority value is selected
Maximum number of rings exceeded Maximum number of rings (16) is exceeded
Invalid traffic VLAN ID Invalid traffic VLAN ID value is selected

Message Description
VLAN does not exist Selected VLAN does not exist
Cannot disable the ring with active physical The ring cannot be disabled if it has active physical ports
ports attached to its nodes. First, disable the physical ports.
Invalid SF trigger, OAM service is not defined SF trigger cannot be enabled if no valid OAM service has
been configured
Cannot modify active ring An active Ethernet ring cannot be modified
Ring ports are not defined Ring ports are not defined yet
Invalid parameter value Invalid value for the parameter is selected
Cannot modify WTR timer for of non-RPL WTR timer can be set only for RPL Owner
Owner
Invalid ring number Invalid ring number is selected
Cannot enable SF propagation for inactive ring Signal failure propagation can be enabled only for an active
ring
Cannot run command on inactive ring Manual or force switch command can be run only on an
active ring
East and West ports must be different Different bridge ports must be defined as East and West
Cannot assign ERP node to bridge instance A ring node must be assigned to a bridge instance before
after configuring East/West ports configuring East/West ports
Cannot modify East/West port before East/West ports can be modified after assigning a ring
assigning ERP node to bridge instance node to a bridge instance
Cannot add data VLAN before assigning ERP Data VLAN must be defined after assigning a ring node to a
node to bridge instance bridge instance
Cannot disable major ring with active sub- A major ring cannot be disabled if it has a sub-ring
rings attached to it
Major ring of the specified sub-ring is not The major ring of the specified sub-ring has not been
active enabled
Major ring of the specified sub-ring does not A sub-ring cannot be configured if a major ring does not
exist exist
Illegal node port type in relation to another Not a valid value for the current node configuration. For
ring member example, if an East port is defined as RPL owner, the West
port can be configured only as a ring node.
Cannot set node port type to ring-node The owner, neighbor or next-neighbor port type of the
node cannot be changed back to the ring-node (default
value). First, delete the ring, then set the port type of the
node.
Invalid ring type Invalid ring type is selected
Cannot modify ring type Ring type (major or minor) cannot be modified
Invalid node type Invalid type for the node is selected

Message Description
Cannot run FS or MS command in backward- Force switch and manual switch commands are not
compatibility mode supported in the backward-compatible mode
FS or MS command is already active Cannot run a force or manual switch command if an active
command instance exist on the ring
Cannot configure R-APS VLAN ID for inactive R-APS VLAN ID can be set only for an active virtual channel
virtual channel
Cannot configure R-APS VLAN priority for R-APS VLAN priority can be set only for an active virtual
inactive virtual channel channel
Cannot modify virtual channel bound to sub- A virtual channel attached to a sub-ring cannot be modified
ring
Cannot modify this parameter, delete and re- This parameter cannot be modified, you must delete and
create the ring re-create the ring
Maximum number of sub-rings per major ring The maximum number of sub-rings (5) per major ring has
exceeded been reached
Sub-ring with specified index does not exist The selected sub-ring does not exist
Major ring node must be configured as One of the major ring nodes must be configured as an
interconnection node interconnection node to accommodate a sub-ring
Sub-ring node must be configured as One of the sub-ring nodes must be configured as an
interconnection node interconnection node
Cannot enable backward-compatibility mode Disable the force switch command to operate the ring in
when FS command is active the backward-compatibility mode
First, remove all sub-rings of the major ring This action requires deleting all sub-rings belonging to the
major ring
This node must be configured as Configure this node as an interconnection node to operate
interconnection node a sub-ring
First, remove all sub-rings bound to the major This action requires deleting all sub-rings belonging to the
ring major ring
This command is available for major ring only This command can be run only on a major ring
Cannot change bridge number for a ring with A ring with configured data VLAN
configured data VLAN
Major ring is assigned to a different bridge The major ring is already assigned to another bridge
instance instance
The sub-ring is already bound to another The sub-ring cannot be attached to the ring, because it is
major ring already bound to another major ring
The port is already in use by another ring The port cannot be attached to the ring because it is in use
by another ring
Cannot activate a ring without configured A ring without a port assigned to the bridge instance
bridge number cannot be activated
Cannot activate a ring without configured A ring without configured East port cannot be activated
East port

Message Description
Cannot activate a ring without configured A ring without configured West port cannot be activated
West port
Cannot activate a ring without configured R- A ring without configured R-APS VLAN cannot be activated
APS VLAN
Cannot activate a ring without configured R- A ring without configured R-APS MEL cannot be activated
APS MEL
Cannot activate a ring without R-APS VLAN A ring without R-APS VLAN ID, configured for the virtual
configured for virtual channel channel, cannot be activated
Cannot activate a ring without R-APS VLAN A ring without R-APS VLAN priority, configured for the
priority configured for virtual channel virtual channel, cannot be activated
Cannot activate a virtual channel without A virtual channel without R-APS VLAN ID and priority,
configured R-APS VLAN ID and priority for configured for the sub-ring, cannot be activated
sub-ring
7.4 Fault Propagation

Fault propagation mechanism allows propagating failures from the Ethernet port,
LAG or OAM (CFM) level to Ethernet port, LAG or OAM (CFM) level.
Standards
Benefits
Fault propagation ensures that the traffic is sent via links that have not failed. If
a failure occurs, fault propagation can be used to trigger redundancy mechanisms
at user equipment.
The fault propagation mechanism defines whether a fault of a source entity
(Ethernet port, LAG or MEP) triggers a certain action at a destination entity
(Ethernet port, LAG or MEP).
ETX-5 supports up to 128 fault propagation sessions. Table 7-8 lists all possible
combinations of the sources and destinations used during fault propagation.
Table 7-8. Fault Propagation Sources and Destinations
Trigger Source Action Destination
Ethernet port or LAG Ethernet port or LAG
Ethernet port or LAG MEP
ETX-5 Fault Propagation 7-59

Trigger Source Action Destination
MEP Ethernet port or LAG
MEP MEP
Multiple triggers and multiple actions configuration can be supported in one fault
propagation session/command. To prevent a deadlock, an action destination
triggered by a certain action, disables all triggers which use it as a trigger source.
For example, in the configuration shown below, the action MEP 1 AIS (Tx) is not
initiated because port 1 failed as a result of the fault propagation rule (MEP 1 AIS
(Rx)).
• Trigger: MEP 1 AIS (Rx) > Action: Port 1: Fail
• Trigger: Port 1: Fail > Action: MEP 1 AIS (Tx)
Fault propagation Fault propagation
ETH-FAIL to MEP-AIS MEP-AIS to ETH-FAIL
ETH-FAIL
Network
ETX-2
CPE ETX-5 CPE
CPE moves to Triggers CPE to

alternative path move to alternative
path
Network
Figure 7-31. Fault Propagation
Trigger Sources
A single GbE/10GbE, LAG or MEP can serve as a fault propagation trigger, with
multiple propagation commands sharing the same source. A trigger source can be
used as an action destination in another fault propagation command/session for
a bidirectional fault propagation functionality.
ETX-5 supports the following triggers:
• Ethernet failure (Ethernet port or LAG).
For LAG, it is declared when a physical layer failure is detected on both LAG
member ports.
• OAM (CFM) LOC detection
• OAM (CFM) RDI detection
• OAM (CFM) AIS detection
• OAM E-LAN failure per MEP, when all RMEPs of the MEP report LOC,.
If a trigger is cleared or deleted, the destination action defined for it is initiated.
In addition, ETX-5 maintains a wait-to-restore timer, which defines a period of
time between clearing a trigger condition and reporting the clearing to the fault
propagation mechanism.
7-60 Fault Propagation ETX-5

Destination Actions
A single GbE/10GbE, LAG or MEP can serve as a fault propagation destination,
with multiple propagation commands sharing the same action. An action
destination can be used as a trigger source in another fault propagation
command/session for a bidirectional fault propagation functionality.
ETX-5 supports the following destination actions:
• Deactivate interface (Ethernet port or LAG).
 For LAG, it causes a physical layer failure for both LAG member ports.
 For fiber optic Ethernet port, it shuts down the laser
 For copper Ethernet ports, it disables the port PHY
• Sends OAM (CFM) AIS to indicate failure.
Factory Defaults
By default, no fault propagation is configured. When you configure fault
propagation for a particular interface pair, the default configuration is as follows:
• No trigger defined for fault detection
• No action defined to be performed when fault is detected
• Wait-to-restore time = 0.
RMEP Auto-configuration
ETX-5 has the ability to learn RMEP MAC address from CCM sessions. It can show
MEP level configuration parameters and status as follows:
• Show MEP status: MEP status screen indicates all its RMEP CC monitoring
status and MEP info.
 RMEP Oper status can be: O.K, Fail or RDI
 MEP status includes RMEP MAC address.
• Initiate LBM:
 Unicast: By specifying
 Remote MAC address and number of LBM packets to send (range 1-
50 and time interval between consecutive LBM’s Tx is 1 second)
 RMEP ID and number of LBM packets to send (only if RMEP learnt by
CCM, otherwise shall not be initiated)
• Initiate LTM (Link Trace Massage):
LTM is a Multicast message, the destination (embedded in the packet ) can be
set by specifying:
 Remote MAC address
 RMEP ID (only if RMEP learnt by CCM, otherwise shall not be initiated)
• PM configuration:
 Dest NE configuration

 Define a remote MAC destination for the LMM/S-LMM and DMM/1-DM

messages ( One destination per dest NE) by:
 Explicit MAC address
 RMEP ID (only if RMEP learnt by CCM, otherwise shall not be initiated)
Adding Fault Propagation Group

 To configure fault propagation:
1. If you intend to use LAG or MEP as your triggers or destinations, verify that
these entities have been created already.
2. Add a fault propagation entry for a pair of interfaces.
3. Configure the fault propagation parameters for the entry:
a. Specify the trigger(s)
b. Specify the action
c. Specify the wait-to-restore time if you do not want to use the default
value (0).
 To add fault propagation for a pair of interfaces:
1. Navigate to configure fault.
2. Type the command:
fault-propagation <from-interface> to <to-interface> and enter the desired
interfaces, as shown in Table 7-9.
A prompt is displayed:
config>fault>fp(<from-interface>/to/<to-interface>)$
3. Configure the fault propagation parameters as needed (see Configuring Fault
Propagation).
Table 7-9. Fault Propagation Command Options
From Interface To Interface Command
Ethernet port Ethernet port fault-propagation port ethernet <slot/port> { to } port

ethernet <slot/port>
Ethernet port LAG fault-propagation port ethernet <slot/port> { to } port lag

<to-port-number>
Ethernet port MEP fault-propagation port ethernet <slot/port> { to } mep

<to-mdid> <to-maid> <to-mepid>
LAG Ethernet port fault-propagation port lag <to-port-number>{ to } port

ethernet <slot/port>
LAG LAG fault-propagation port lag <to-port-number>{ to } port lag

<to-port-number>
LAG MEP fault-propagation port lag <to-port-number>{ to } mep

<to-mdid> <to-maid> <to-mepid>

From Interface To Interface Command
MEP Ethernet port mep <to-mdid> <to-maid> <to-mepid> { to } port ethernet

<slot/port>
MEP LAG mep <to-mdid> <to-maid> <to-mepid> { to } port lag <to-

port-number>
MEP MEP mep <to-mdid> <to-maid> <to-mepid> { to } mep

<to-mdid> <to-maid> <to-mepid
Configuring Fault Propagation

 To configure fault propagation parameters:
1. Navigate to configure fault fault-propagation <from-interface> to
<to-interface> to select the fault propagation entry to configure.
A prompt is displayed:
config>fault>fp(<from-interface>/to/<to-interface>)#
Specifying the trigger(s) trigger { los | oam-cfm-loc | oam-cfm-rdi | Typing no before the command removes the
oam-cfm-ais | oam-cfm-all-rmep-fail} specified trigger.
Note: The los trigger is allowed only if the
from-interface is an Ethernet port or LAG.
The OAM CFM triggers are allowed only if
the from-interface is a MEP.
Specifying the action to take when action-on-group { interface-deactivation | Typing no action-on-group removes the
fault propagation is triggered oam-cfm-ais } action.
Note: The action interface-deactivation is
allowed only if the to-interface is an
Ethernet port or LAG. The action oam-cfm-
ais is allowed only if the to-interface is a
MEP.
Specifying the wait-to-restore time wait-to-restore <seconds> The range is 0–3600
Disabling Fault Propagation

 To disable fault propagation for a pair of interfaces:
1. Navigate to configure fault.
2. Type the command:
no fault-propagation <from-interface> to <to-interface> to select the
interfaces for which to disable fault propagation.
The specified fault propagation is disabled.

Example 1
 To enable Ethernet port to MEP fault propagation:
• From Ethernet port 3 on I/O card in slot 1
• 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 alarm indication signal
• Wait-to-restore time = 120 seconds.
exit all
config fault
fault-propagation port ethernet 1/3 to mep 2 3 3
trigger los
action-on-group oam-cfm-ais
wait-to-restore 120
exit all
 To display information on the fault propagation configured above:

ETX-5# config fault fault-propagation port ethernet 1/3 to mep 2 3 3
ETX-5>config>fault>fp(port/ethernet/3/to/mep/2/3/3)$ info detail
action-on-group oam-cfm-ais
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-ais
no trigger oam-cfm-rdi
wait-to-restore 120
Example 2
 To enable Ethernet port to Ethernet port fault propagation:
• From Ethernet port 1 on main card A
• To Ethernet port 3 on I/O card in slot 1
• Trigger: LOS
• Action: Shut down Ethernet port on the I/O card
• Wait-to-restore time = 90 seconds.
exit all
config fault fault-propagation port ethernet main-a/1 to port ethernet 1/3
trigger los
action-on-group interface-deactivation
wait-to-restore 90
exit all
 To display information on the fault propagation configured above:

ETX-5# config fault fault-propagation port ethernet main-a/1 to port ethernet
1/3
ETX-5>config>fault>fp(port/ethernet/main-a/1/to/port/ethernet/1/3)# info
detail

action-on-group interface-deactivation
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-ais
no trigger oam-cfm-rdi
wait-to-restore 90
detected.
Message Description
Illegal action for destination port Illegal action has been selected for the destination Ethernet port
or LAG
Illegal action for destination MEP Illegal action has been selected for the destination MEP
Illegal trigger for source port Illegal trigger has been selected for the source Ethernet port or
LAG
Illegal trigger for source MEP Illegal trigger has been selected for the source MEP
Max number (128) of fault propagation Maximum number of fault propagation sessions (128) has been
definitions has been reached reached
Illegal wait-to-restore value (0–3600) Illegal value for the wait-to-restore timer has been selected. The
WTR value must be in the 0–3600 sec. range.
Source or destination Ethernet port does Ethernet port selected as a source or destination entity has not
not exist been activated
Source or destination LAG does not exist LAG selected as a source or destination entity has not been
defined or activated
Source MEP does not exist MEP selected as a source entity has not been defined or
activated
Source and destination entities must be The same entity (Ethernet port, LAG or MEP ) cannot be selected
different as source and destination for fault propagation session
7.5 Main Card Redundancy

Redundancy for the ETX-5 control subsystem is supported only when the ETX-5
chassis includes two operational main cards. If only one is installed, it is
automatically selected and redundancy cannot be activated.
ETX-5 provides 1:1 main card protection, when one of the cards is defined as
primary, and the other one as secondary. The primary card manages the chassis
with its I/Os and peripherals, performs data plane forwarding, and controls the
timing subsystem. The secondary main card stores a copy of the configuration
database, serving as a hot standby.
ETX-5 Main Card Redundancy 7-65

Benefits
Main card redundancy with automatic switchover ensures continuous service
provisioning. It provides a hot-standby capability for the ETX-5 management and
timing subsystems.
Only one main card per chassis is necessary; however, the chassis has two slots
dedicated to this type of module. The second slot can be used by a redundant
main card, thereby providing a hot-standby capability for the ETX-5 system
control functions.
When a second main card is installed, the two modules operate as a master/slave
pair; one module is the active (online) module, and the other is off-line and
serves as a hot standby.
Only the online main card communicates with the management station/terminal
and actively manages the ETX-5 system. The off-line main card is automatically
updated by the online card with all the configuration and status data. The off-line
card can take over at any time without disrupting system operation. The switch-
over to the off-line card occurs automatically when one of the following occurs:
• Extraction of the primary main card
• Power failure of the primary main card
• Diagnostics indication primary main card failure
• User-initiated or automatic reset of the primary main card
• A manual switch command
• Administratively disabling of the primary main card.
Configuring Main Card Redundancy

When two main cards are installed in the chassis, you can manually switch
between active and standby main cards.
 To switch between main cards:

3. Navigate to configure protection main-card.
The config>protection>main-card# prompt is displayed.
4. At the config>protection>main-card# prompt, enter manual-switch to toggle
between main card A and B.
ETX-5#config protection main-card
ETX-5#config>protection>main-card# manual-switch
Displaying Main Card Protection Status

 To display main card protection status:
1. Navigate to configure protection main-card.
The config>protection>main-card# prompt is displayed.
7-66 Main Card Redundancy ETX-5

2. At the config>protection>main-card# prompt, enter show status.

ETX-5#config protection main-card
ETX-5#config>protection>main-card# show status
Active Card : main-a
Primary Card : main-a
Redundancy Status : OK
Last Switchover Time :
Last Switchover Reason : none
The main card protection status screen provides information on the currently
active and primary main card, redundancy status, last switchover time and
reason.
detected.
Message Description
Manual switch cannot be performed: Manual switch has failed because the secondary main card is not
Mate card's operational status is down. operational
Manual switch cannot be performed: Manual switch has failed because only one main card is installed
Mate card doesn't exist. in the chassis
Manual switch cannot be performed: SW Manual switch has failed because a new software release is
Install is in progress being installed
Manual switch cannot be performed: Manual switch has failed because a card switchover is being
Switchover is in progress performed
7.6 SDH/SONET Protection

ETX-5 provides 1+1 APS/MSP line redundancy for rapid restoration of service in
case of line failure. When two TDM cards operate in APS/MSP mode for hardware
redundancy, they ensure 50 ms restoration of service in case of line faults.
Standards and MIBs

Telecordia GR-253-CORE, RFC 3498, ITU-T G.841 (Annex B)
Benefits
APS/MSP switches over traffic with minimal loss of data, thus avoiding time-
consuming reroutes. With APS/MSP, there is no indication beyond the affected
network element that a failure has occurred; other nodes stay intact. SDH/SONET
APS performs switchovers at Layer 1 significantly faster than at Layer 2 or Layer
ETX-5 SDH/SONET Protection 7-67

3. The effect of a failure is greatly minimized, and a fast switchover guarantees

minimal effect on the network.
Factory Defaults
By default, SDH/SONET protection is disabled.
In 1+1 APS/MSP, ETX-5 provides a unidirectional protection facility (backup line)
for each working facility. At the near end of the line, the optical signal is bridged
permanently (split into two signals) and sent over both the working and the
protection facilities simultaneously, producing identical working and protection
signals.
At the far end of the line, both signals are monitored independently for failures.
The receiving equipment selects either working or the protection signal. This
selection is based on switch initiation criteria, which can be a signal fail (hard
failure such as loss of frame), a signal degrade (soft failure caused by the error
rate exceeding some pre-defined value), or a response to user-initiated
commands.
When the TDM ports belong to a slot configured to comply with the TTC standard
requirements (STM-1J), APS/MSP can be set to the 1+1 bidirectional optimized
mode. The 1+1 bidirectional optimized APS functionality is implemented in
accordance with the ITU-T G.841 (Annex B) requirements. It is similar to the 1+1
unidirectional APS/MSP, but the switchover of the failed Rx path is performed
after negotiation with the opposite device. The opposite system must approve
the switchover, even if the failure occurred at one end only.
Working and protection ports can reside on the same or different E5-cTDM-4 or
E5-cTDM-STM4 cards. When the working and the protection ports reside on
different cards, each card is protected against failures.
The working and protection ports can reside on the same E5-cTDM-4 or E5-cTDM-
STM4 card (intra-card APS/MSP), provided that the card is not a member of an I/O
card protection group (standalone card).
The working and protection ports can reside on two different E5-cTDM-4 or E5-
cTDM-STM4 cards (inter-card APS/MSP) that are already assigned to an I/O card
protection group, provided that:
• The working port is on the working card
• The protection port is on the protection card
• The working and protection ports have the same port number (In the case of
E5-cTDM-STM4 card, port 1 is used for inter-card APS/MSP)
• APS/MSP is defined for cards in the following slot pairs:
 1 and 2
 3 and 4.
This means that working and protection ports cannot reside on cards in slots
1 and 3, 1 and 4, 2 and 3, or 2 and 4.
7-68 SDH/SONET Protection ETX-5

Note PW services cannot be assigned to SDH/SONET ports which are not APS/MSP
members, when an inter-card APS/MSP has been defined on at least two ports of
different I/O TDM cards. For example, if two ports 1 on I/O TDM cards in slot 1
and slot 2 are inter-card APS/MSP members, no pseudowire services are available
on ports 2, 3 and 4 of both cards.
Each APS/MSP group includes up to two members. ETX-5 can have up to eight
APS/MSP instances per chassis.
APS/MSP Architecture
ETX-5 APS/MSP is a 1+1 unidirectional protection switching. In this mode, all
communication from the near end to the far end is carried out over the APS/MSP
channel, using the K1 and K2 bytes of the SONET/SDH overhead on the
protection line.
The line selection is based only on the local conditions and requests. Therefore,
each end operates independently of the other end, and the K1 and K2 bytes are
not needed to coordinate switch actions. However, the K1 byte is still used to
inform the other end of the local action.
The K2 byte is set to indicate that the K1 byte is being received (by indicating the
same channel number as the received K1) and to inform the other end of the
provisioned architecture and mode of operation.
Working Line
Tx
Rx
Tx
Rx
Protection Line
Figure 7-32. APS/MSP Architecture
The K1 byte contains both the switching pre-emption priorities (in bits 1-4) and
the channel number of the channel requesting action (in bits 5-8). The K2 byte
contains the channel number of the channel that is bridged onto the protection
(bits 1-4) and the mode type (bit 5) as well bits 6 to 8 contain various condition
such as AIS-L, RDI-L.
I/O card maintains a protection status for every port in a protection group. The
status values arranged in the following ascending priority order:
• active(1)
• standby(2)

• waitToRestore(3)
• manualSwitched(4)
• sd(5)
• sf(6)
• forcedSwitched(7)
• lockedOut(8) (protection only)
• notPresent(9)
The switch occurs whenever the protection status of the active port changed to a
higher priority than the standby as a result of a user command (shutdown, reset,
switch) or protection event.
Automatic Switchover Conditions

The following automatic switch conditions are defined for APS/MSP:
• Signal Fail (SF): LOS, LOF, AIS-L, Line BER above configurable EED threshold
(10-3 to 10-5)
• Signal Degrade (SD) above configurable SD threshold (10-5 to 10-9)
Manual Switching Commands

During normal operation, ETX-5 automatically switches traffic between the
working and protection circuits if a link failure occurs. The following commands
are available for manually switching the circuits. They are listed in order of
priority, from lowest to highest.
• Manual – manually switches to a working or protection link
• Force – forces switching to a working or protection link
• Lockout – prevents a working link from switching to a protection link
A higher priority command overrides the lower priority command. Signal failures
and signal degradations override manual switch, but are overridden by force and
lockout commands.
Table 7-12. Behavior of Manual Switching Commands
Interface Conditions Allowed Command (1+1 Unidirectional Mode)
Working is not present, protection is active None
Working is active, protection is not present Lockout-of-protection
Working is shut down, protection is active Lockout-of-protection

Force-switch-to-working (causes a switchover)
Working is active, protection is shut down Lockout-of-protection
Working is reset, protection is active Lockout-of-protection

Force-switch-to-working (causes a switchover)
Working is active, protection is reset Lockout-of-protection

Configuring I/O Card Protection

If you intend to configure inter-card APS/MSP, when working and protection ports
belong to different I/O TDM cards, you must first define a 1+1 I/O card protection
group according to the following rules:
• Working port of the inter-card APS/MSP must reside on the working card of
the I/O card protection group
• Protection port of the inter-card APS/MSP must reside on the protection card
of the I/O card protection group.
• Only two adjusted slots may be part of the same IO protection group (#1 and
#2, #3 and #4)
• The card in the odd slot (#1,#3) should be defined as working
• In main service card protection mode: all four SONET/SDH ports shall be
protected (APS/MSP) respectively by a port on the other TDM card (e.g. ports
1/1, 2/1 etc.)
 To add an I/O card protection group:

2. Type io-group and enter an I/O card protection group name.
The config>protection>io-group (group name)# prompt is displayed.
Note Using no before io-group (group name), deletes the I/O card protection group.
I/O protection group can be deleted when it is disabled and has no cards
assigned to it.
 To configure I/O card protection group:

• At the config>protection> io-group (group name)# prompt, enter all
necessary commands according to the tasks listed below:
Defining working (active) and bind {working <slot> | protection Using no before bind removes a
protection (standby) I/O cards <slot>} card from I/O card protection
group
Administratively enabling I/O no shutdown When the APS/MSP group is

card protection group activated (no shutdown
command), the protection TDM
I/O card is reset. This allows error-
free transfer of configuration
parameters from the working to
the protection TDM I/O card.
shutdown disables I/O card
protection group
Displaying I/O card protection show status

group status

Configuring APS/MSP
Use the following procedure to configure redundancy for the ETX-5 SDH/SONET
links.
Note In the following procedures, the aps command is used to configure both MSP and
APS protection. There is no difference whether the network is SDH or SONET. The
same command executes the same protection for both.
 To add an APS/MSP group:

2. Type aps and enter an APS group name.
The config>protection>aps(group name)# prompt is displayed.
Note Using no before aps (group name), deletes the APS group.
 To configure APS/MSP:
• At the config>protection>aps(group name)# prompt, enter all necessary
commands according to the tasks listed below:
Defining protection (standby) bind {protection sdh-sonet Using no before bind removes a
and working (active) links <slot/port> | working sdh-sonet link from protection group
<slot/port>}
Configuring APS mode oper-mode {uni-directional | 1+1 optimized mode is available

optimized-1-plus-1}
only for the ports on a TDM I/O
card, configured as stm-1-t1-ch-4
Administratively enabling APS no shutdown shutdown disables APS/MSP group

group
Forcing traffic to the working force-switch-to-working Manually switches to the working

port link, unless a request of equal or
higher priority is in effect
Forcing traffic to the protection force-switch-to-protection Manually switches to the

port protection link, unless a request
of equal or higher priority is in
effect.
Signal failure on the protection
line (null channel) has higher
priority than the
force-switch-to-protection
command.
Manually switching traffic to the manual-switch-to-working Use this command to revert the
working port communication link back to the
working interface before the wait
to restore (WTR) time has expired

Manually switching traffic to the manual-switch-to-protection Use this command when you need
protection port to perform maintenance on the
working port
Preventing a working link from lockout-of-protection This command prevents the circuit
switching to a protection link from switching to a protection
interface in the event that the
working circuit becomes
unavailable
Clearing manual, force and clear

lockout commands
Displaying APS status show status
Displaying APS/MSP Status

You can display current status of existing APS/MSP group and its member links.
 To display APS/MSP status:

• In the config>protection>aps(group name)# prompt, enter show status.
The APS status is displayed.
ETX-5>config>protection>aps(aps_group_1)# show status
Group
Mode : uni-directional
Administrative Status : up
Rx K1K2 : 100
Tx K1K2 : 100
Last Switchover Time :
Last Switchover Reason :
Ports
Port Admin Status Active
Working sdh-sonet 4/1 up up yes
Protection sdh-sonet 3/1 down sf --
Examples
Intra-Card APS/MSP
 To configure intra-card APS/MSP:

• APS/MSP group name – aps_1
• Working interface – STM-1/OC-3 port 1 on E5-cTDM-4 card in slot 1
• Protection interface – STM-1/OC-3 port 2 on E5-cTDM-4 card in slot 1
ETX-5# config protection aps aps_1
ETX-5>config>protection>aps(aps_1)$ bind working sdh-sonet 1/1
ETX-5>config>protection>aps(aps_1)$ bind protection sdh-sonet 1/2
ETX-5>config>protection>aps(aps_1)$ no shutdown

Inter-Card APS/MSP
• I/O card protection group name – io-group_1
• Working card – E5-cTDM-4 in slot 1
• Protection card – E5-cTDM-4 in slot 2
• APS/MSP group name – aps_1
• Working interface – STM-1/OC-3 port 1 on E5-cTDM-4 card in slot 1
• Protection interface – STM-1/OC-3 port 1 on E5-cTDM-4 card in slot 2
ETX-5# config protection io-group io-group_1
ETX-5>config>protection>io-group(io-group_1)$ bind working 1
ETX-5>config>protection>io-group(io-group_1)$ bind protection 2
ETX-5>config>protection>io-group(io-group_1)$ no shutdown
ETX-5>config>protection>io-group(io-group_1) exit all
ETX-5# config protection aps aps_1
ETX-5>config>protection>aps(aps_1)$ bind working sdh-sonet 1/1
ETX-5>config>protection>aps(aps_1)$ bind protection sdh-sonet 2/1
ETX-5>config>protection>aps(aps_1)$ no shutdown
Card Protection
ETX-5>config>protection>io-group(1)#
bind working 1
bind protection 2
no shutdown
Port APS
ETX-5300->config>protection>aps(1)#
bind working sdh-sonet 1/1
bind protection sdh-sonet 2/1
no shutdown
no shutdown
no shutdown
no shutdown
detected.

Message Description
Bind failed: port is already bound to an SDH/SONET port cannot be bound to more than one APS/MSP
existing APS/MSP group group
Bind failed: Services exist on port SDH/SONET port with PWs defined on it cannot be bound to an
APS/MSP
Bind failed: Ports should reside on same For intra-card APS/MSP, the working and protection port must
card reside on the same card
Bind failed: APS/MSP ports should be of Only SDH/SONET ports can be defined as APS/MSP group
type SONET-SDH members
Un-bind failed: APS/MSP group must be A port can be removed from the APS/MSP group only after the
shutdown before unbinding a port group is shut down
Bind failed: Protection port must reside Protection port must reside on a card defined as protection card
on protection card in group in the I/O protection group (inter-card APS/MSP)
Bind failed: Working port must be Working port must reside on a card defined as working card in
configured on working card in group the I/O protection group (inter-card APS/MSP)
Bind failed: Working and protection ports For inter-card APS/MSP, the working and protection port must
must have the same port number have the same number
Bind failed: Working and protection slots For intra-card APS/MSP, the working and protection port must
must be the same reside on the same card
Sonet/sdh port number is not valid Invalid SDH/SONET port number has been selected
Sonet/sdh card is not defined yet An SDH/SONET port on a TDM card that has not been
provisioned yet, cannot be bound to an APS/MSP group
APS/MSP group remove failed: Ports are APS/MSP group cannot be deleted if it has ports bound to it
bound to the group
APS/MSP group creation failed: Maximum Maximum number of APS/MSP groups per chassis (8) has been
number of APS/MSP groups is already reached
configured
Max length of APS/MSP group name is 32 APS/MSP group name length has exceeded 32 alphanumeric
characters characters
Command failed: Protection line is in Traffic cannot be manually switched to a port with signal failure
signal fail or signal degrade or signal degrade condition
Command failed: Working line is in signal Traffic cannot be manually switched to a port with signal failure
fail or signal degraded or signal degrade condition
Modify failed: Group should be shutdown Active APS/MSP group cannot be modified
in order to perform modification
APS/MSP create failed: Exactly 2 ports Number of APS/MSP members cannot exceed two ports
should be bound to group


Chapter 8
Traffic Processing
This chapter explains how to configure networking entities in ETX-5. It presents
the following information:
• Bridge and RSTP
• Cross-Connection
• Ethertype
• Flows
• Layer 2 Control Protocol (L2CP)
• Link Layer Discovery Protocol (LLDP
• Peers
• Router
• TDM Pseudowires
8.1 Bridge
The ETX-5 bridge is a VLAN-aware Layer-2 forwarding entity.
Standards
IEEE 802.1D, 802.1Q
Benefits
A bridge is used to deliver EPLAN and EVPLAN (any-to-any) services.
Factory Defaults
By default, no bridge instances exist in the ETX-5 system. The default STP
parameters are as follows:
mode mstp
max-age 20 sec
forward-time 30 sec
hello-time 10 sec
ETX-5 Bridge 8-1

Chapter 8 Traffic Processing Installation and Operation Manual
priority (bridge) 32768
tx-hold-count 3
max-hops 20
name Empty string
revision 0
priority (bridge MSTI) 32768
cost (bridge port) 0
priority (bridge port) 128
admin-edge Disable
auto-edge Enable
restricted-role Disable
restricted-tcn Disable
cost (bridge port MSTI) 0
priority (bridge port MSTI) 128
A bridge is a forwarding entity used by ETX-5 for delivering E-LAN services in
multipoint-to-multipoint topology and G.8032 ring protection. With up to 32
bridge instances, ETX-5 provides up to 128 bridge ports.
The bridge operates in VLAN-aware mode (IVL) with ingress filtering. It accepts
tagged frames only. To be admitted to the bridge, a frame’s VID must be
configured as a part of the bridge port VLAN member set. Untagged frames must
receive a relevant VID at port ingress (tag push) or they will be dropped.
The ETX-5 bridge supports up to 4K broadcast domains (bridge/VLAN) and a MAC
table with up to 256K entries. MAC table size is configurable per broadcast
domain with up to 4K entries per broadcast domain. The MAC table flush is
supported per bridge instance and the MAC table list is available in a file. MAC
address aging time is configured per chassis in the range of 300 (default) to
660 seconds.
Bridge Model
A bridge is defined by a bridge number, bridge ports and a VLAN membership
table that specifies which bridge ports are members in a certain broadcast
domain (VLAN).
Traffic in and out of a bridge port is configured using flows. This allows editing
action at ingress and egress bridge ports. Valid and invalid bridge configurations
are described below.
Different flows from one physical port can be mapped to bridge ports on
different bridge instances, as shown in the figure below:
8-2 Bridge ETX-5

Installation and Operation Manual Chapter 8 Traffic Processing
Bridge
Port
Bridge
Figure 8-1. Mapping Flows from the Same Physical Port to Different Bridges
However, different flows from the same physical port cannot be mapped to the
same bridge port and broadcast domain (VLAN):
VID A
VID B Push C
Port Bridge
VID C
Figure 8-2. Mapping Flows with the Same VID to One Bridge Port
Likewise, flows from the same bridge port cannot be mapped to different
physical ports:
Port
Bridge
Port
Figure 8-3. Mapping Flows with the Same Bridge Port to Different Physical Ports
E-Tree Service
Unlike regular E-LAN (multipoint-to-multipoint), E-Tree is a point-to-multipoint
E-LAN service. As defined by MEF, its topology includes root and leaf nodes. The
leaves communicate with the roots, but not with each other. The root-leaf
forwarding functionality is provided at bridge port/VLAN level. Figure 8-21
illustrates the E-Tree forwarding functionality.
ETX-5 Bridge 8-3

Leaf
Root Leaf
Broadcast, multicast, unknown unicast
Known unicast
Broadcast, multicast, unicast
Figure 8-4. E-Tree Forwarding
Forwarding mode (E-LAN or E-Tree) is configured at the VLAN level; node

functionality (root or leaf) is assigned at the VLAN/port level, as shown below.
Leaf Leaf
BP2
Bridge
BP3
VLAN
Domain Y
BP4 BP1
Root
Leaf
Root
VLAN
Domain X
BP6
Leaf BP5 Root

Leaf Root
Figure 8-5. Root/Leaf Functionality
VLAN Editing at Bridge Port Ingress and Egress

The ETX-5 bridge supports one level of VLAN editing on ingress and one level on
egress. The editing is performed at the flow level. For details, see the section see
VLAN Editing above.
Note For bridge-type SVIs, each ingress flow within a certain VLAN domain must have
an accompanying egress flow.
Certain restrictions apply to the type of port of flow origin (directly- or indirectly-
attached) and flow classification method.
• Directly-attached ports:
8-4 Bridge ETX-5

 Flows with a classification profile that includes P-bit (VLAN+P-bit or outer

VLAN + P-bit + Inner VLAN) cannot be bound to a bridge port.
 Tag stripping (pop) at bridge port ingress can be configured only if the
flow classification method is configured to Outer + Inner VLAN. (If pop
action exists, the flow must be classified with two VLANs.)
 Untagged flows must have a push action configured at bridge port
ingress.
Table 8-42 specifies valid combinations of flow classification method, ingress
VLAN editing action, and flow VID for flows originating at directly-attached
ports.
Table 8-1. Flows Originating at Directly-Attached Port
Classification Method Ingress Editing Action Bridge Broadcast Domain
Untagged Push X VLAN X

None VLAN X
VLAN X Push Y VLAN Y
Swap (mark) Y VLAN Y
None VLAN X
Outer VLAN X + Pop VLAN Y

Inner VLAN Y Push Z VLAN Z
Swap (mark) Z VLAN Z
• Indirectly-attached ports:
 Up to 255 different bridge ports with ingress pop action can be defined.
 Flows originating at SAP with a double tag classification (Outer VLAN + Inner VLAN)
cannot be bound to a bridge port.
Table 8-43 specifies valid combinations of flow classification method, ingress

VLAN editing action, and flow VID for flows originating at indirectly-attached
ports.
Table 8-2. Flows Originating at Indirectly-Attached Ports (via SAP)
Swap (mark) X VLAN X

Match All
Push X VLAN X
Outer VLAN X None VLAN X
Note
All flows from the same SAP must have the same classification mode.
Deleting Bridge Elements

Deletion of bridge elements is performed in the following manner:
ETX-5 Bridge 8-5

• All flows on the VLAN must be deleted before a VLAN member can be deleted
from a bridge port.
• All VLAN members of a bridge port must be deleted before the bridge port
can be deleted.
• All bridge ports must be deleted before the bridge can be deleted.
• E-LAN/E-Tree and root/leaf functionalities cannot be changed if active flows
are configured for bridge ports and VLANs.
Spanning Tree Protocol

Spanning Tree Protocols (STPs) are Layer-2 loop avoidance techniques used in
Ethernet networks. Loops are created in bridge-based networks with more than
one path between two endpoints, when the bridges repeatedly rebroadcast the
broadcast/multicast messages, flooding the network. So, STPs are used to
identify the best path to the destination, and block all other paths. The blocked
links are not always discarded. They are connected and kept inactive, creating
automatic backup links.
Figure 8-23 illustrates STP operation. Bridge 3 is connected directly to Bridge 1
and Bridge 2. Another physical link connects directly Bridge 1 to Bridge 2. Under
normal conditions, there will be 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.
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-6. STP Operation
ETX-5 supports up to 32 STP instances 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-23
serves as a root in the application
The root bridge is elected by selecting the bridge with the lowest bridge ID. It can
be done manually, or the bridges in the network elect a root bridge themselves
automatically. If the root bridge fails, the other bridges select a new root device.
The other bridges in the network are referred to as designated bridges.
Link Cost
Every link in the network receives a certain cost. Usually, higher-bandwidth links
that are adjacent to the root bridge are assigned a lower cost. Lower-bandwidth
8-6 Bridge ETX-5

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 designated 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 designated bridges adjust their
tables to determine the new routes to the terminals.
Rapid Spanning Tree Protocol

Rapid Spanning Tree Protocol (RSTP) provides significantly faster spanning tree
convergence after a topology change, supporting a loop-free Layer-2 forwarding
over a mesh/ring physical topology. In RSTP, the link status of each port is
monitored pro-actively (instead of waiting for the BPDU messages) to detect
changes in network topology.
ETX-5 supports RSTP per bridge as required by 802.1Q.
Multiple Spanning Tree Protocol

Multiple Spanning Tree Protocol (MSTP) maps a group of VLANs into a single
Multiple Spanning Tree instance (MSTI). This means, the Spanning Tree Protocol is
applied separately for a set of VLANs instead of 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-5 supports up to
64 MSTIs per chassis, excluding MSTI0.
Figure 8-24 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 rest of the VLANs in the network.
ETX-5 Bridge 8-7

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-7. MSTP Operation
A group of bridges that collectively define multiple Spanning Tree instances is

called an MST Region. A single bridge can belong to only one region. Bridges
belong to the same MSTP region if they have the same configuration parameters.
A bridge serves a region boundary if it receives BPDUs from:
• An MSTP bridge with different configuration attributes, or
• An STP or RSTP switch.
MSTP dynamically determines MST region boundaries based on the content of the
MST BPDUs it receives. Every MST bridge creates a message digest of the table
that associates VLANs with spanning tree instances and transmits that digest in
BPDUs. When it receives a BPDU, an MST-enabled bridge extracts the digest and
compares the transmitted digest with its own digest. If the name and digest
match, the bridge that sent the BPDU is part of the same region as the receiving
bridge. If the name and digest do not match, the bridges are in different regions.
The ports involved in the transaction are considered a boundary between the
regions.
Configuring Bridge
Bridge configuration includes the following steps:
1. Adding and configuring a bridge instance (1–32)
2. Binding bridge ports to SVIs
3. Adding VLANs and defining bridge ports as egress tagged VLAN members.
4. Configuring RSTP/MSTP (optional).
5. Configuring STP (optional)
8-8 Bridge ETX-5

 To configure a bridge:
1. At the configure prompt, enter bridge followed by bridge number (1–32).
A bridge instance with the specified number is created and the
config>bridge(1)# prompt is displayed.
2. Configure the bridge as illustrated and explained below.
Note Using no before bridge (bridge_number) deletes a bridge instance.
Defining aging time for MAC aging-time <300–660>

table entries (seconds)
Clearing addresses in MAC table clear-mac-table
Configuring bridge ports, see port <1–128> no port (port_number), deletes

below no port <1–128> a bridge port
Configuring VLAN membership, vlan <1–4094> no vlan (VLAN_number),

see below no vlan <1–4094> deletes a VLAN
Displaying MAC address table show mac-address-table [vlan-id] Adding VLAN ID after the show
mac-address-table all displays
MAC table only for selected
VLAN
Displaying VLAN information show vlans
Configuring STP parameters at spanning-tree See Configuring

the bridge level
Configuring Bridge Ports

The following actions can be performed at the port level, at the
config>bridge(bridge_number)>port(port_number)# prompt.
Note In order to change the physical port connected to the bridge port, you must
delete all flows connected to the SVI bound to the bridge port and then configure
the bridge again with the new physical port.
Binding bridge port to a bridge- bind svi <svi_number> no bind svi (svi_number),
type SVI no bind svi <svi_number> unbinds bridge port from SVI
Assigning a name to bridge port name <value> no name deletes bridge port
no name name
Enabling the bridge port no shutdown shutdown disables the bridge

port
Configuring STP parameters at spanning-tree See Configuring

the bridge port level
Displaying bridge port status show status
ETX-5 Bridge 8-9

Configuring VLAN Membership

The following actions can be performed at the vlan membership level, at the
config>bridge(bridge_number)>vlan(vlan_number)# prompt.
Selecting operation mode mode { e-tree | e-lan }
Defining a bridge port as a root root < bridge_port_number> no root defines a bridge port
in E-Tree mode no root < bridge_port_number> as a leaf in E-Tree mode
Defining maximum MAC table maximum-mac-addresses <64 | 256 |

size supported by the VLAN 512 | 1024 | 4096>
Assigning a name to VLAN name <value> no name deletes VLAN name

no name
Defining bridge ports as egress tagged-egress<bridge_port_number> Bridge ports in a list can be

tagged VLAN members no tagged-egress separated by a comma or given
<bridge_port_number> as a range, for example: 1..3,
5.
no before the command
deletes VLAN membership for
the bridge port.
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.
Selecting spanning tree mode { rstp | mstp} MSTP-related parameters are

operation mode masked, when bridge operated
in RSTP mode
Defining maximum aging time for max-age <6–40> sec

spanning tree operation
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-5 hello-time <1–10> sec

broadcasts hello messages to
other devices to indicate that
the bridge is alive
8-10 Bridge ETX-5

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.
Selecting the maximum number tx-hold-count <1–10>

of BPDUs that can be
transmitted to a port in one
second
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
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
Configuring bridge-level MSTI mst <1–4094> no mst (msti_number) deletes

no mst MST instance.
See configuration instructions
below.
 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.
Specifying MSTI priority priority<0, 4096, 8192, 12288,

16384, 20480, 24576, 28672, 32768,
36864, 40960, 45056, 49152, 53248,
57344, 61440>
ETX-5 Bridge 8-11

Mapping VLANs to MSTI vlan <1–4094> no vlan (vlan_number) removes

no vlan 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 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-5 to compute the best
possible cost according to the
link bandwidth (Table 8-44).
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).
8-12 Bridge ETX-5

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 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).
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.
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.
ETX-5 Bridge 8-13

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 the MSTP or RSTP
mode.
mcheck forces protocol
renegotiation with neighboring
devices, to check if they are
MSTP- or RSTP-compatible.
Activating spanning tree on the shutdown shutdown disables spanning

bridge port no shutdown tree on bridge port
Displaying bridge port spanning show status See Displaying Spanning Tree
tree status Status below
Configuring bridge-port-level mst <1–4094> no mst (msti_number) deletes

MSTI no mst MST instance.
See configuration instructions
below.
Table 8-3. 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>
8-14 Bridge ETX-5

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:

• In the relevant prompt (bridge, bridge MSTI, bridge port, bridge port MSTI),
enter 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-8. 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-9. 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
Port 1, Port Priority 128, Cost 200000000
ETX-5 Bridge 8-15

Regional Root: Priority 32768, Address 00:11:22:33:44:55, Cost 200000000

Hello Timer 10
Forward Transitions: 11
Figure 8-10. 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-11. Spanning Tree Status, Bridge Port MSTI Level
Configuring STP
When configuring STP, it is necessary to configure an L2CP profile with MAC
address:
01-80-C2-00-00-00 and action set to peer, and attach the L2CP profile to an
untagged flow from each port that is part of the spanning tree.
The examples below show the necessary configuration.
 To configure an L2CP profile for 01-80-C2-00-00-00 with peer action:

ETX-5# configure port
ETX-5>config>port# l2cp profile BPDUpeer
ETX-5>config>port>l2cp profile(BPDUpeer)$ mac 01-80-C2-00-00-00 peer
 To configure an untagged flow from each port:

Example for 10GbE main port:
config flows flow 1
classifier classutg
ingress-port lag 1
0/1 // Egress port can be any main card port either used or unused in any
case this flow would not carry traffic and this egress port is just a dummy
port.
l2cp profile BPDUpeer
drop
no shutdown
exit all
Example for 1GbE IO card port and 10GbE IO port:
config flows flow 1
classifier classutg
ingress-port eth 1/1
l2cp profile BPDUpeer
drop
no shutdown
exit all
config flows flow 2

classifier classAll
8-16 Bridge ETX-5


0/1 // Egress port can be any main card port either used or unused in any
case this flow would not carry traffic and this egress port is just a dummy
port.
no shutdown
exit all
Displaying MAC Address Table

You can display an ETX-5 MAC table, which provides information on static
addresses, bridge ports and VLANs associated with them.
 To display MAC address table:

• At the config>bridge(bridge_number)# prompt, enter show mac-address-
table.
The MAC address table is displayed.
Note ETX-5 displays only first 1000 entries. To view the whole MAC table, download it
to your PC, using SFTP. See File Operations in Chapter 10.
ETX-5>config>bridge(1)# show mac-address-table

VLAN MAC Address Port Status
---------------------------------------------------------------
100 00:00:11:00:00:01 1 dynamic
100 00:00:11:00:00:02 1 dynamic
200 00:00:11:00:00:01 1 dynamic
200 00:00:11:00:00:02 1 dynamic
300 00:00:11:00:00:01 1 dynamic
300 00:00:11:00:00:02 1 dynamic
400 00:00:11:00:00:01 1 dynamic
400 00:00:11:00:00:02 1 dynamic
 To display MAC address table for a specific VLAN:

• At the config>bridge(bridge_number)# prompt, enter show mac-address-table
vlan-id.
The MAC address table for the selected VLAN is displayed.
ETX-5>config>bridge(1)# show mac-address-table vlan 100
VLAN MAC Address Port Status
---------------------------------------------------------------
100 00:00:11:00:00:01 1 dynamic
100 00:00:11:00:00:02 1 dynamic
Displaying VLAN Information

VLAN information includes port name, egress tagged VLAN members, and, if
Ethernet ring protection is configured, VLAN ERP role.
ETX-5 Bridge 8-17

 To display VLAN information:

• At the config>bridge(bridge_number)# prompt, enter show vlans.
The VLAN information is displayed.
ETX-5>config>bridge(1)# show vlans
VLAN ID : 20 Name : vlan_20
Tagged Ports : 1..4
Ring : 1 East : 1 West : 2 Data
Displaying Bridge Port Status

You can display status of ETX-5 bridge ports, including their roles in Ethernet
protection rings, ERP status and source of local signal failure.
 To display bridge port status:

• At the config>bridge(bridge_number)>port(port_number)# prompt, enter
show status.
The bridge port status information is displayed.
ETX-5>config>bridge(1)>port(1)# show status
Name : Bridge Port-1-1
Operational Status : UP
ERP Ring : 1 East

ERP Status : Forward
Local SF Source : Not Applicable
Example
Flow configuration example (see Multipoint Service) includes bridge configuration
procedure.
Table 8-45 lists the messages generated by ETX-5 when a configuration error is
detected.
Message Description
Modify failed: shut down the port before Active bridge ports cannot be modified
modification
Modify failed: bridge port is bound Bound bridge ports cannot be modified
Modify failed: bridge port is bound to ERP-bound bridge ports cannot be modified
ERP
Modify failed: VLAN does not exist VLAN cannot be modified because it does not exist
8-18 Bridge ETX-5

Message Description
Modify failed: no bridge ports are VLAN with no bridge ports attached to it cannot be modified
configured to be this VLAN members
Modify failed: max number of bridge Maximum number of bridge instances per chassis (32) has been
instances has been reached reached
Modify failed: max number of VLANs has Maximum number of broadcast domains (4K) has been reached
been reached
Modify failed: VLAN is used for RAPS VLAN cannot be modified because it is used as a messaging
messaging in ERP VLAN in ERP
Modify failed: VLAN is used as data VLAN VLAN cannot be modified because it is used as a data VLAN in
in ERP ERP
Modify failed: VLAN index is out of range VLAN numbering index is out of allowed range
Modify failed: only bound bridge ports Bridge ports must be bound to SVIs prior to their activation
can be activated
Modify failed: bridge port must be shut Active bridge ports cannot be modified
down
Modify failed: bridge has active ports or Bridge entity has active ports or VLANs
VLANs
Modify failed: bridge port index is out of Bridge port index is out of allowed range
range
8.2 Cross-Connection
The cross-connect function is used to assign TDM timeslots for pseudowire
connections.
Note DS1 (E1/T1) services can be activated only after defining cross-connections.
Factory Defaults
By default, there are no cross-connections in the ETX-5 system.
Benefits
Cross-connects allow flexible mapping of individual DS0 channels or full DS1
streams into pseudowires.
The ETX-5 cross-connect matrix supports two types of cross-connect, selectable
at the level of the individual E1 and T1 port:
ETX-5 Cross-Connection 8-19

• DS0 cross-connect mode –used when necessary to control the routing of

individual timeslots, and is therefore relevant only when using a framed mode
with CESoPSN pseudowires
• DS1 (TDM) cross-connect mode –used when necessary to transparently
transfer entire E1 or T1 streams into SAToP pseudowires.
Configuring Cross-Connection
 To configure a pw-tdm cross connection:
1. At the config# prompt, enter cross-connect or cr.
The config>cross-connect# prompt appears.
2. Configure the cross connection as illustrated and explained below.
Establishing pw-tdm pw <pw number> ds1 <slot>/<port> Timeslots in a list can be separated
cross-connection [time-slots <ts list>] by a comma or given as a range, for
between this example: 1..3, 5.
pseudowire and Using no before the command
timeslots on the removes the cross-connection
ds1 port
Examples
Cross-Connection
 To assign timeslots 1–6, 8, and 10–15:
• PW number 1
• E1 interface 1 in TDM port 1 of E5-cTDM-4 card installed in slot 1
ETX-5>config>cross-connect# pw-tdm pw 1 e1 1/1/1 time-slots
[1..6, 8, 10..15]
 To remove PW1:
ETX-5>config>cross-connect# no pw-tdm pw 1
 To display information on all assigned timeslots:

ETX-5>config>cross-connect# info
pw-tdm pw 1 e1 1/1/1 [1..31]
pw-tdm pw 3 t1 2/1/1 [1..4]
Pseudowire Service
The following script illustrates the configuration of point-to-point L2 pseudowire
service for unframed T1.
#****************************Provisioning_I/O_TDM_Card***********************
configure slot 1
8-20 Cross-Connection ETX-5

card-type sdh-sonet oc-3-ch-4

no shutdown
exit all
#*********************************End****************************************
#*********************Activating_Ethernet_Port_1_on_Main_Card_A**************
configure port ethernet main-a/1
no shutdown
exit all
#*********************************End****************************************
#**************Activating_SDH_SONET_Port_1_on_TDM_Card_in_Slot_1 ************
configure port sdh-sonet 1/1
no shutdown
exit all
#*********************************End****************************************
#*******Activating_SDH_SONET_STS-1_1_on_Port_1_on_TDM_Card_in_Slot_1*********
configure port sdh-sonet 1/1 oc3 1 sts1 1
no shutdown
exit all
#*********************************End****************************************
#*****Activating_SDH_SONET_VC/VT_on_STS-1_1_Port_1_on_TDM_Card_in_Slot_1*****
configure port sdh-sonet 1/1 oc3 1 sts1 1 vt1-5 1 1
no shutdown
exit all
#*********************************End****************************************
#************************Configuring_Clock_Domain****************************
configure system clock domain 1
sync-network-type 1
source 1 rx-port sdh-sonet 1/1
quality-level prs
wait-to-restore 0
exit all
#*********************************End****************************************
#*********************Configuring_Pseudowire_Peer****************************
configure peer 1 mac 00-20-d2-31-bf-01 name ETX-205A
exit all
#*********************************End****************************************
#*********************Configuring_Classifier_Profile*************************
config flows classifier-profile classAll match-any
match all
exit all
match vlan 1000
exit all
match vlan 2000
exit all

match vlan 3000

exit all
match vlan 4000
exit all
#*********************************End****************************************
#********************Assigning_Queue_Group_Profile***************************
configure port ethernet main-a/1 queue-group profile q_group_2_level_default

exit all
#*********************************End****************************************
#*************************Selecting_Classification_Key***********************
exit all
#*********************************End****************************************
#***********************Configuring_Marking_Profile**************************
config qos marking-profile mark1 classification cos color-aware green-yellow
dei mapping
exit all
#*********************************End****************************************
#*****************************Configuring_SVI********************************
configure port svi 1 pw
name pw-dataS1
no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_T1*********************************
configure port t1 1/1/1
line-type unframed
no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_Pseudowire*************************
configure pwe
pw 1 type t1satop psn ethernet
label in 1 out 1
peer 1
egress-port svi 1
tdm-payload size 96
8-22 Cross-Connection ETX-5

jitter-buffer 3000
no oam
no shutdown
exit all
#*********************************End****************************************
#**************************Configuring_Cross-Connect*************************
configure cross-connect pw-tdm pw 1 t1 1/1/1
exit all
#*********************************End****************************************
#************************Configuring_T1_to_Ethernet_Flow*********************
configure flows flow 1
classifier classAll
ingress-port svi 1
0/1
vlan-tag push vlan 1000 p-bit profile mark1
no shutdown
exit all
#*********************************End****************************************
#************************Configuring_Ethernet_to_T1_Flow*********************
egress-port svi 1
vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
detected.
Message Description
PW XC set failed: Only one PW can be Cannot configure a timeslot cross-connection because unframed
configured on an Unframed port ports support only a single PW
PW XC set failed: Timeslots do not match Cannot configure a timeslot cross-connection because there is a
with PW payload size and rate mismatch between the number of assigned timeslots and the
selected PW TDM payload size or rate
PW XC set failed: The timeslot belongs to Cannot configure a timeslot cross-connection because a timeslot
another bundle is already assigned to another PW
Pw-TDM cross-connection failed: Cannot configure a timeslot cross-connection because there is a

Timeslot(s) out of range mismatch between the number of timeslots and the PW type

Message Description
Pw-TDM cross-connection failed: PW Cannot configure a timeslot cross-connection because there is a

type doesn't match card configured in mismatch between a PW type and a card configured for the slot
slot
PW XC set failed: card in specified slot Cannot configure a timeslot cross-connection because an
must be of type TDM Ethernet card has been configured in the chassis slot
PW XC create failed: more than one Cannot configure a timeslot cross-connection because only one
multi-service card cannot use same the TDM card can use a single SVI
SVI
PW XC set failed: Mismatch between port Cannot configure a timeslot cross-connection because a PW
line-type (unframed) and pw type (ces- type (CESoPSN) requires a framed line type
psn-data)
PW XC set failed: Mismatch between port Cannot configure a timeslot cross-connection because a PW
line-type (framed) and pw type (SAToP) type (SAToP) requires an unframed line type
PW XC set failed: Mismatch between port Cannot configure a timeslot cross-connection because there is a
interface type and PW type mismatch between an interface type (E1 or T1) and a PW type
(e1satop or t1satop)
PW XC set failed: only 1 PW can be Cannot configure a timeslot cross-connection because only one
configured per port PW can be configured for this port type
8.3 Ethertype
Ethertype (tag protocol ID, or TPID) configured per chassis and per port is used
for:
• Identifying VLAN-tagged frames at ingress
• Setting Ethertype value used in VLAN editing at egress.
Standards and MIBs

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.
8-24 Ethertype ETX-5

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 packet must match the configured Ethertype of the
port in order to be considered as a VLAN-tagged frame (otherwise the frame is
considered untagged or dropped).
ETX-5 supports two Ethertype tag values:
• Default 8100
• Any other type.
The second Ethertype tag value is configured globally, and can thus be used
in per port configuration.
Per-port Ethertype tag configuration allows identification of incoming and
outgoing VLAN-tagged frames. The configured tag protocol ID (TPID) refers to
outer tag. As for the inner TPID, the following assumptions are maintained:
• Indirectly-attached ports – inner VID (if exists) is 8100
• Directly-attached ports – inner VID is either the same as outer VID Ethertype
or 8100.
Note Ethertype tag cannot be changed if a port (Ethernet or LAG) has flows attached
to it.
The following tables describe the admission rules for different port and TPID
types.
Table 8-6. Indirectly-Attached Ports with Port TPID 8100
Outer TPID Inner TPID Admit/Drop Recognized Tag Levels
8100 None Admit 1

8100 8100 Admit 2
8100 X (other than 8100) Admit 1
X (other than 8100) Don’t care Admit Untagged
None – Admit Untagged
Table 8-7. Indirectly-Attached Ports with Port TPID Y (other than 8100)
Y None Admit 1
Y 8100 Admit 2
Y X (other than 8100) Admit 1
Z (other than Y) Don’t care Admit Untagged
ETX-5 Ethertype 8-25

Table 8-8. Directly-Attached Ports with Port TPID 8100
8100 None Admit 1

8100 8100 or Y Admit 2
8100 X (other than 8100) Admit 1
X (other than 8100) Don’t care Admit Untagged
Table 8-9. Directly-Attached Ports with Port TPID Y (other than 8100)
Y None Admit 1
Y 8100 or Y Admit 2
Y B (other than 8100 or Y) Admit 1
8100 Don’t care Drop –
B (other than 8100 or Y) Don’t care Admit Untagged
Note
TPID is also used to indicate the Ethertype tag used in VLAN stacking.
Configuring Ethertype
Any Ethertype tag, in addition to the default 8100 value, must first be defined at
the chassis level. Afterwards, the additional tag value is used in the port
configuration. If the second value is not defined for a port, the port uses default
setting (8100).
 To configure Ethertype tag at chassis level:

2. Enter tag-ethernet-type <0x0000-0xFFFF>.
Note Using no before tag-ethernet-type, removes additional Ethertype tag value.
Example
 To configure global Ethertype tag 0x88a8:
ETX-5>config>port>tag-ethertype 0x88a8
detected.
8-26 Ethertype ETX-5

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
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
8.4 Flows
Flows are unidirectional entities that connect two physical or logical ports.
Benefits
The user traffic can be classified into different Ethernet flows (EVC, EVC.CoS) to
provide services in a flexible manner.
Factory Defaults
By default, there are no flows in the ETX-5 system.
The ingress traffic is first classified into flows according to classification profiles.
A per-port classification key configuration defines what types of classification
profiles are supported for this type of port. The classification key also defines the
CoS mapping and color mapping methods.
The Classification section below specifies the supported classification keys and
the associated CoS and color mapping methods. It also details the different
classifier profile types supported per classifier key.
Flows connect physical and/or logical ports. They are used for E-Line and E-LAN
services, or to provide L3 connectivity over router interfaces. In total, ETX-5
supports up to 24K of Ethernet flows.
ETX-5 Flows 8-27

Flows include information about traffic forwarding (flow destination); traffic

mapped into flows is further processed according to user-defined profiles and
VLAN editing actions. See the Flow Processing section below.
Classification
The ingress traffic is first classified to flows according to classifier profiles. A per
port classification key defines the types of classifier profiles supported for this
type of port. The classification key also defines the CoS mapping and color
mapping methods. Table 8-1 and Table 8-2 specify the supported classification
keys and the associated CoS and color mapping methods. The different types of
classifier profiles supported per classification key are detailed in Table 8-3,
Table 8-4, Table 8-5, Table 8-6, Table 8-7, Table 8-8, Table 8-9, Table 8-10,
Table 8-11.
Table 8-11. Classification Keys for Indirectly-Attached Ports
Classification Key (Port + …) CoS Mapping Method Ingress Color Mapping Method
VLAN+P-bit (see Note below) Flow, P-bit Flow, P-bit, DEI

VLAN+IP Precedence Flow, IP Precedence Flow, IP Precedence
VLAN+DSCP Flow, DSCP Flow, DSCP
P-bit Flow, P-bit Flow, P-bit, DEI
IP Precedence Flow, IP Precedence Flow, IP Precedence
DSCP Flow, DSCP Flow, DSCP
Outer VLAN + Inner VLAN + Outer P-bit Flow, P-bit Flow, P-bit, DEI
Table 8-12. Classification Keys for Directly-Attached Ports
Classification Key (Port + …) CoS Mapping Method Ingress Color Mapping Method
VLAN+P-bit (see Note below) Flow, P-bit, DSCP Flow, P-bit, DEI, DSCP
Outer VLAN + Inner VLAN + Outer P-bit Flow, P-bit, DSCP Flow, P-bit, DEI, DSCP
Note IA port classification key cannot be changed when the port has flows attached to
it. Flows must be deleted first.
Indirectly-Attached Ports with VLAN+P-Bit

Classifier profile types for the VLAN+P-bit key that can be used for traffic
originating from indirectly-attached ports are detailed in Table 8-3.
Table 8-13. Indirectly-Attached Ports with VLAN+P-Bit Classifier Key
Classifier Profile Type Range (per Flow) Priority
VLAN (see note 1 below) Single VLAN range, single P-bit 2

VLAN + P-bit range
VLAN + Src MAC (see Note 1 below) Single VLAN, single MAC 1
VLAN + Dst MAC (see note 1 below)
8-28 Flows ETX-5

VLAN + Src IP (see Note 1 below) Single VLAN, single IP 1

VLAN + Dst IP (see Note 1 below)
Src MAC Single MAC 1

Dst MAC
Src IP Single IP 1
Dst IP
Ethertype Single Ethertype 1

Untagged 2
Match All (Unclassified), default 3
Note
• Some of the VLAN-based classifier profile types (VLAN, VLAN + Src/Dst MAC,
VLAN + Src/Dst IP) are supported without explicit P-bit indication, but they
actually imply a full P-bit range (0–7).
• ETX-5 recognizes only one level of VLAN tagging on the flows created with this
classifier key. This means that for a double-tag packet, IP level is not detected.
• A packet with an Ethertype tag that does not match the port Ethertype tag is
considered to be untagged.
Priority
Flow priority, as shown in Table 8-3, is a hard-coded attribute of a flow that
cannot be changed. Two flows having the same priority cannot overlap.
For example, if a flow with VID 5 exists (classifier profile type VLAN, priority 2), a
flow with VID 5 and P-bit 0 (classifier profile type VLAN+P-bit, priority 2) is not
allowed and vice versa. In this case, two flows must be created: VID 5 and P-bit 0
and VID 5 and P-bit 1–7.
When flows have different priorities, they can overlap. For example, it is possible
to configure a flow with VLAN 5 (classifier profile type VLAN, priority 2) and VLAN
5 and Src MAC x (classifier profile type VLAN + Src MAC, priority 1).
Classification Type Groups

Some of the classification types under VLAN + P-bit key are divided into two
groups that have certain configuration restrictions:
• Group 1 – VLAN + Src MAC, VLAN + Dst MAC, VLAN + Src IP, VLAN + Dst IP
• Group 2 – Src MAC, Dst MAC, Src IP, Dst IP, Ethertype.
Group 1 and Group 2 classification types cannot be used on the same port.
Moreover, only one Group 1 classification type is allowed per VLAN. Thus, if the
VID 5 and Dest MAC 1 (Group 1) classifier profile is configured on a port, you can
add a flow based on VID 5 Dest MAC 2 (Group 1), but cannot use VID 5 Src IP x
(Group 2) profile.
In total, up to 128 Group 1 or Group 2 flows can be defined on Ethernet ports 1–
10 or 11–20 of the E5-GbE-20 card, or on ports 1 or 2 of the E5-10GbE-2 card.
ETX-5 Flows 8-29

Indirectly-Attached Ports with VLAN + IP Precedence

Classifier profile types for the VLAN + IP Precedence key that can be used for
traffic originating from indirectly-attached ports are detailed in Table 8-4.
Table 8-14. Indirectly-Attached Ports with VLAN + IP Precedence Classifier Key
VLAN (see Note 1 below) Single VLAN range, single IP-P 2

VLAN + IP Precedence range
VLAN + Dst MAC (see Note 1 below)


Dst MAC
Src IP Single IP 1
Dst IP

Untagged 2
Non-IP 2
VLAN + Non-IP Single VLAN range 2
Note
• Some of the VLAN-based classifier profile types (VLAN, VLAN + Src/Dst MAC,
VLAN + Src/Dst IP) are supported without explicit IP precedence indication, but
they actually imply a full IP Precedence range (0–7). Packets with VLANs, but
without IP Precedence (non-IP) will not match these classifier profiles.
• ETX-5 recognizes only one level of VLAN tagging on the flows created with this
• A packet with an Ethertype tag that does not match the port Ethertype tag is
considered to be untagged.
Priority
Flow priority, shown in Table 8-4, is a hard-coded attribute of a flow that cannot
be changed. Two flows having the same priority cannot overlap.
For example, if a flow with VID 5 exists (classifier profile type VLAN, priority 2), a
flow with VID 5 and IP-P 0 (classifier profile type VLAN + IP-P, priority 2) is not
allowed and vice versa. In this case, two flows must be created: VID 5 and IP-P 0
and VID 5 and IP-P 1–7.
to configure a flow with VLAN 5 (classifier profile type VLAN, priority 2) and VLAN
5 and Src MAC x (classifier profile type VLAN + Src MAC, priority 1).
8-30 Flows ETX-5


Some of the classification types under VLAN + IP Precedence key are divided into
two groups that have certain configuration restrictions:
• Group 2 – Src MAC, Dst MAC, Src IP, Dst IP, Ethertype
(Group 2) profile.
10 or 11–20 of E5-GbE-20 card, or on ports 1 or 2 of E5-10GbE-2 card.
Indirectly-Attached Ports with VLAN + DSCP

Classifier profile types for the VLAN + DSCP key that can be used for traffic
Table 8-15. Indirectly-Attached Ports with VLAN + DSCP Classifier Key
VLAN (see Note 1 below) Single VLAN range, single DSCP 2

VLAN + DSCP range


Dst MAC
Src IP Single IP 1
Dst IP

Untagged 2
Non-IP 2
VLAN + Non-IP Single VLAN range 2
Note
• (1) Some of the VLAN-based classifier profile types (VLAN, VLAN + Src/Dst
MAC, VLAN + Src/Dst IP) are supported without explicit DSCP indication, but
they actually imply a full DSCP range (0–63). Packets with VLANs, but without
DSCP (non-IP) will not match these classifier profiles.
• (2) ETX-5 recognizes only one level of VLAN tagging on the flows created with
this classifier key. This means that for a double-tag packet, IP level is not
detected.
ETX-5 Flows 8-31

Priority
For example, if a flow with VID 5 exists (classification type VLAN, priority 2), a
flow with VID 5 and DSCP 0 (classification type VLAN + DSCP, priority 2) is not
allowed and vice versa. In this case, two flows must be created: VID 5 and DSCP 0
and VID 5 and DSCP 1–63.
to configure a flow with VLAN 5 (classification type VLAN, priority 2) and VLAN 5
and Src MAC x (classification type VLAN + Src MAC, priority 1).

Some of the classification types under VLAN + DSCP key are divided into two
• Group 1 – VLAN + Src MAC, VLAN + Dst MAC, VLAN + Src IP, VLAN + Dst IP,
VLAN + Ethertype
(Group 2) profile.
Indirectly-Attached Ports with P-Bit

Classifier profile types for P-bit key that can be used for traffic originating from
indirectly-attached ports are detailed in Table 8-6.
Table 8-16. Indirectly-Attached Ports with P-Bit Classifier Key
P-bit Single P-bit range 2

Dst MAC
Src IP Single IP 1
Dst IP

Untagged 2
Note
ETX-5 recognizes only one level of VLAN tagging on the flows created with this
8-32 Flows ETX-5

Priority
For example, if a flow with P-bit 0–7 exists (classification type P-bit, priority 2), a
flow with P-bit 3 (classification type P-bit, priority 2) is not allowed and vice
versa. In this case, three flows must be created: P-bit 0–2, P-bit 3 and P-bit 4–7.

Some of the classification types under the P-bit key belong to a group that has
certain configuration restrictions: Group 2 – Src MAC, Dst MAC, Src IP, Dst IP,
Ethertype.
Only one flow based on Group 2 classification method can be created on the
same port. For example, if Src MAC x flow exists on port 1 of the E5-GbE-20 card
in slot 1, no other flows created using Group 2 classification method (Dst MAC,
Src IP, Dst IP or Ethertype) are allowed on this port.
In total, up to 128 Group 2 flows can be defined on Ethernet ports 1–10 or 11–
20 of the E5-GbE-20 card, or on ports 1 or 2 of the E5-10GbE-2 card.
Indirectly-Attached Ports with IP Precedence

Classifier profile types for the IP Precedence key that can be used for traffic
Table 8-17. Indirectly-Attached Ports with IP Precedence Classifier Key
IP Precedence Single IP-P range 2

Dst MAC
Src IP Single IP 1
Dst IP

Non-IP 1
Priority
be changed. Two flows with the same priority cannot overlap.
For example, if a flow with IP-P 0–7 exists (classification type IP Precedence,
priority 2), a flow with IP-P 3 (classification type IP Precedence, priority 2) is not
allowed and vice versa. In this case, three flows must be created: IP-P 0–2, IP-P 3
and IP-P 4–7.
ETX-5 Flows 8-33


Some of the classification types under the IP Precedence key belong to a group
that has certain configuration restrictions: Group 2 – Src MAC, Dst MAC, Src IP,
Dst IP, Ethertype.
Only one flow based on Group 2 classification method can be created on the
same port. For example, if Src MAC x flow exists on port 1 of the E5-GbE-20 card
in slot 1, no other flows created using Group 2 classification method (Dst MAC,
Src IP, Dst IP or Ethertype) are allowed on this port.
Indirectly-Attached Ports with DSCP

Classifier profile types for the DSCP key that can be used for traffic originating
from indirectly-attached ports are detailed in Table 8-8.
Table 8-18. Indirectly-Attached Ports with DSCP Classifier Key
DSCP Single P-bit range 2

Dst MAC
Src IP Single IP 1
Dst IP
Untagged 2
Priority
be changed. Two flows with the same priority cannot overlap.
For example, if a flow with DSCP 0–63 exists (classification type DSCP, priority 2),
a flow with DSCP 3 (classification type DSCP, priority 2) is not allowed and vice
versa. In this case, three flows must be created: DSCP 0–2, DSCP 3 and DSCP 4–
63.

Some of the classification types under DSCP key belong to a group that has
certain configuration restrictions: Group 2 – Src MAC, Dst MAC, Src IP, Dst IP,
Ethertype.
Only one Group 2 classification type per port can be used. For example, if Src
MAC x flow exists on port 1 of the E5-GbE-20 card in slot 1, no other flows
created using Group 2 classification method (Dst MAC, Src IP, Dst IP or Ethertype)
are allowed on this port.
8-34 Flows ETX-5

Indirectly-Attached Ports with Outer VLAN + P-bit + Inner VLAN

Classifier profile types for the Outer VLAN + P-bit + Inner VLAN key that can be
used for traffic originating from indirectly-attached ports are detailed in
Table 8-9.
Note • TPID of outer VLAN is expected to match the user-configured port Ethertype
tag.
• TPID of inner VLAN must be 8100, otherwise the inner VLAN and IP level are
not recognized.
Table 8-19. Indirectly-Attached Ports with Outer VLAN + P-bit + Inner VLAN Classifier Key
Outer VLAN + P-bit + Inner VLAN Single outer VLAN, single P-bit 2
Outer VLAN + Inner VLAN range, single inner VLAN range
(see Note 1 below)
VLAN (see notes 1 and 2 below) Single VLAN, single P-bit range 2
VLAN + P-bit (see Notes 1 and 2 below)
VLAN + Src MAC (see note 1 below) Single VLAN, single MAC 1

Src IP Single IP 1
Dst IP

Untagged 2
Note
• (1) Some of the VLAN-based classifier profile types (VLAN, Outer VLAN + Inner
VLAN, VLAN + Src/Dst MAC, VLAN + Src/Dst IP) are supported without explicit
P-bit indication, but they actually imply a full P-bit range (0–7).
• (2) VLAN and VLAN + P-bit classifier profile types relate to packets with single
VLAN level only.
Priority
Flow priority, as it appears in Table 8-9, is a hard-coded attribute of a flow that
flow with VID 5 and P-bit 0 (classification type VLAN+P-bit, priority 2) is not
to configure a flow with VLAN 5 (classification type VLAN, priority 2) and VLAN 5
and Src MAC x (classification type VLAN + Src MAC, priority 1).
ETX-5 Flows 8-35


Some of the classification types under the VLAN + P-bit key are divided into two
(Group 2) profile.
Directly-Attached Ports with VLAN+P-bit

Classifier profile types for the VLAN+P-bit key that can be used for traffic
originating from directly-attached ports are detailed in Table 8-10.
Table 8-20. Directly-Attached Ports with VLAN+P-bit Classifier Key
VLAN (see note 1 below) Single VLAN range, Single P-bit 1

VLAN + P-bit range
Untagged 2
Note
• (1) VLAN classifier profile type is supported without explicit P-bit indication,
but it actually implies a full P-bit range (0–7).
• (2) When a two-level VLAN frame is received, this classification refers to the
outer VLAN.
Flow priority, shown in Table 8-10, is a hard-coded attribute of a flow that

cannot be changed. Two flows with the same priority cannot overlap.
Directly-Attached Ports with Outer VLAN + P-bit + Inner VLAN

Classifier profile types for the Outer VLAN + P-bit + Inner VLAN key that can be
used for traffic originating from directly-attached ports are detailed in
Table 8-11.
Note A packet with an outer Ethertype tag that does not match the port Ethertype tag
is considered untagged.
8-36 Flows ETX-5

Table 8-21. Directly-Attached Ports with Outer VLAN + P-bit + Inner VLAN Classifier Key
Outer VLAN + P-bit + Inner VLAN Single outer VLAN, single P-bit 1
Outer VLAN + Inner VLAN range, single inner VLAN range
(see note 1 below)
VLAN (see notes 1 and 2 below) Single VLAN, single P-bit range 1
VLAN + P-bit (see note 2 below)
Untagged 1
Note
• (1) VLAN classifier profile type is supported without explicit P-bit indication,
but it actually implies a full P-bit range (0–7).
• (2) VLAN and VLAN + P-bit classification profile type relate to packets with
single VLAN level only.
Flow priority, shown in Table 8-11, is a hard-coded attribute of a flow that

I/O Ingress Flows

I/O ingress flows originate in GbE and 10GbE ports of the Ethernet I/O cards. Up
to 64 ingress flows from the same I/O port can be mapped to a SAP (Service
Attachment Point). Each set of ten ports (1–10 and 11–20) of the E5-GbE-20
card and each single port of the E5-10GbE-2 card provide up to 1K of I/O ingress
flows, with up to 2K flows per Ethernet I/O card.
Figure 8-1 illustrates point-to-point and multipoint flows originating in I/O and
main Ethernet cards. I/O ingress flows are marked in red.
I/O Ingress SAG SVI SVI

Ethernet Port
Flows
I/O Card
SAP BP BP
Ethernet Port
Main Card
SVI
Bridge BP
SVI
Ethernet Port
I/O Ingress
I/O Card
Ethernet Port
Flows BP
Main Card
SAP
I/O Ethernet Card
Figure 8-12. I/O Ingress Flows
ETX-5 Flows 8-37

Flow MAC Swap LB at IO Card Egress

In a device based on chassis and IO cards, diagnostics loop location is an
important aid in fault localization. It is preferable that this diagnostic loop is
performed at the network-facing IO card, so pass/fail of the test would eliminate,
or prove, whether the problem is in the cloud or in the device.
Egress flow MAC swap loopback is supported for the following flows in which the
egress port is:
• IO card port (1GbE , 10GbE)
 Up to one loop instances per 10x1GbE port group at IO card ( or per
1x10GbE IO port)
• IO card LAG (Protection or Load balancing)
Ingress port can be:
 Main card port
 SAP
The relevant cases are illustrated below.
I/O Card Port
I/O Card Port

Flow Loop
Egress SAP
I/O Card Port
I/O Card Port

SAP
I/O Card Main Card I/O Card
Figure 8-13. Egress Loop on a Flow from SAP
8-38 Flows ETX-5

I/O Card Port
Main Card
Port
Flow Loop
SAP
Egress
I/O Card Port
Main Card
Port
I/O Card Main Card
Figure 8-14. Egress Loop on a Flow from Main Card Port
CLI : Test command with MAC swap LB and loop location indication.
test [{egress|ingress}] [{mac-swap|lbm-responder}]
no test
Default :’ ingress port’

• Flows with egress port which is IO card port:
 Supports ‘Egress-port’ loop
 Does not support ‘ingress-port’ loop (sanity)
• Flows with Egress port SAP:
 Supports ‘ingress-port’ loop
 does not support ‘egress-port’ loop (sanity)
• Flows with ingress port main and egress port main does not support any
loops
• Loop Command is cleared after reset.
• Can be assigned and cleared over a flow, on the fly.
• Affects the chassis ‘Test’ LED
Other Flow Types

Up to 1024 flows can originate from all SAPs on a single SAG (up to 1K per
Ethernet I/O card). ETX-5 also supports flows originating from and directed to
main Ethernet card ports.
Flow Processing
Flow processing includes the following:
• Ingress traffic is mapped in flows using the classification match criteria
defined in the classifier profile.
ETX-5 Flows 8-39

• L2CP frames are handled per flow according to L2CP profile settings.
• User priority (P-bit, IP Precedence, DSCP) is mapped to an internal Class of
Service (CoS) according to CoS mapping profile or fixed CoS mapping value
• User priority (P-bit, IP Precedence, DSCP) or DEI can be mapped to a packet
color (yellow or green) according to color mapping profile.
• A single policer can be applied to a flow or a policer aggregate can be
assigned to a group of flows, using policer profile or policer aggregate profile
• 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 CoS marking profile.
CoS marking profile maps CoS value and/or packet color into the egress
priority tags (P-bit, DEI).
• Flow is mapped to a specific queue block within a queue group associated
with the egress port. A specific queue in the queue block is defined 1:1 by
the packet CoS (0–7) according to CoS-mapping profile.
Table 8-12 details processing actions supported by different flow types.
Table 8-22. Processing Actions per Flow Type
Ingress Classifier Drop L2CP CoS Mapping Color Mapping Policing VLAN
Port Profile Action Profile Profile Profile Profile Editing
Main card      – 
I/O card       –
SAP  – – – – – 
SVI PW  – – – – – 
SVI bridge  – – – – – 
SVI router  – – – – – 
Note
All flows can be mapped to a queue block, if the flow egress port is on an I/O or
main Ethernet card.
Drop Action
Traffic carried by I/O ingress flows or by flows originating from directly-attached
(main card) ports can be dropped and thereby prevented from reaching its egress
port.
For example, if you plan to accept traffic marked by a certain VLAN, but to drop
this traffic if it comes from a specific MAC address, you can define two flows:
• Flow 1 with VLAN classification
• Flow 2 with VLAN + specific MAC classification and drop action.
This action can also be used to direct LACP traffic to the CPU, and preventing it
from reaching an egress port. This is done by creating an untagged flow with an
L2CP profile defining a drop action for it.
8-40 Flows ETX-5

Flow Counters
Statistic counters can be enabled on the following flows:
• Up to 512 of I/O ingress flows per each I/O card
• Up to 2046 main card flows per chassis. These flows include:
 Point-to-point (E-Line) flows
 Multipoint (E-LAN) flows.
Note Each pair of the multipoint flows (at bridge port ingress and egress) is counted as
a single flow. PM counters must be either enabled or disabled for both multipoint
flows.
ETX-5 maintains counters for current statistics per flow.

• I/O ingress flows, point-to-point flows (E-Line) and multipoint (E-LAN) flows
at bridge port ingress support the following counters:
 Received:
 Number of received packets
Number of received bytes
 Transmitted:
 Number of transmitted packets
 Number of transmitted green packets
 Number of transmitted yellow packets
 Number of transmitted bytes
 Number of transmitted green bytes
 Number of transmitted yellow bytes
 Total packet transmit rate (packet/sec)
 Green packet transmit rate (packet/sec)
 Yellow packet transmit rate (packet/sec)
 Total bit transmit rate (bit/sec)
 Green bit transmit rate (bit/sec)
 Yellow bit transmit rate (bit/sec)
 Dropped:
 Number of dropped packets
 Number of dropped green packets
 Number of dropped yellow/red packets
 Number of dropped bytes
 Number of dropped green bytes
 Number of dropped yellow/red bytes
 Total packet drop rate (packet/sec)
ETX-5 Flows 8-41

 Green packet drop rate (packet/sec)

 Yellow/red packet drop rate (packet/sec)
 Total bit drop rate (bit/sec)
 Green bit drop rate (bit/sec)
 Yellow/red bit drop rate (bit/sec)
 Peak:
 Maximum transmit bit rate
 Minimum transmit bit rate
 Maximum drop bit rate
 Minimum drop bit rate
• Multipoint (E-LAN) flows at bridge port egress support the following counters:
 Transmit:
 Number of transmitted packets
 Number of transmitted bytes
 Total packet transmit rate (packet/sec)
 Total bit transmit rate (bit/sec)
 Peak:
 Maximum transmit bit rate
 Minimum transmit bit rate.
RFC-2544 Loopback Responder

ETX-5 responds to the application layer loopbacks in accordance with the RFC-
2544 requirements. In this mode, ETX-5 loops back the RFC-2544 frames sent by
the remote device, replying to the LBM packets with LBRs.
Ports
The RFC-2544 testing is supported only on the flows whose ingress port is one of
the following:
• An indirectly-attached port (Ethernet port on I/O cards)
• A LAG with ports bound to indirectly-attached ports.
Functionality
Before running the flow test, you must configure and enable a Down MEP, bound
to an indirectly-attached port (see OAM) with live ingress and egress flows.
When the flow testing is enabled, ETX-5 loops back all LBM packets received on
the flow by swapping the MAC address and changing the LBM code to the LBR
code.
8-42 Flows ETX-5

Tx Flow
SAP
Rx Flow
Main or I/O Card Down MEP I/O Card
Port A Bound to Port B Port B
A. Normal Operation
Tx Flow
LBR
SAP Code
Rx Flow
Main or I/O Card Down MEP I/O Card
Port A Bound to Port B LBM Code Port B
Loop
B. Operation after Enabling the RFC-2544 Loopback Responder
Figure 8-15. RFC-2544 Loopback Responder
ETX-5 continues to forward all other, non-LBM packets. This includes the OAM
packets, such as CCMs and DMMs. The testing mode has no impact on the user
traffic. This mode can be activated dynamically, without disabling the flow.
The LBM packets that are sent back during the RFC-2544 responder operation are
not registered by the statistical counters of the flow.
Notes All packets carrying the LBM code are looped back without any filtering according
to the destination MAC address, MD level etc.
The RFC-2544 testing functions only if the ingress and egress flows use the same
port and have the same VLAN settings.
VLAN Editing
The VLAN tag editing mechanism allows service providers to carry customer-
tagged traffic on its network using its own VLANs. You can configure tag editing
operations to stack (push), remove (pop), or swap (mark) tags on single-, or
double-tagged packets.
Note When configuring VLAN editing via CLI, swap is referred to as mark.
ETX-5 performs the VLAN editing in the following cases:

• E-Line
• E-LAN
 At bridge ingress port
 At bridge egress port
• Router
 At ingress router interface
 At egress router interface
ETX-5 Flows 8-43

When a VLAN is pushed or swapped, the inner bits (P-bit, CFI/DFI) are either
copied from the original VLAN or set according to CoS marking profile.
E-Line VLAN Editing

Table 8-13 details VLAN editing options available for E-Line (point-to-point)
services.
Table 8-23. VLAN Editing Options for E-Line Services
Action 1 Action 2 CLI Command
None None –
Pop (outer) None vlan-tag pop vlan
Pop (outer) Pop (inner) vlan-tag pop vlan inner vlan
Push (copy P-bit and DEI) None vlan-tag push vlan <vid> p-bit copy
Push (set P-bit and DEI None vlan-tag push vlan <vid> p-bit profile <profile name>
according to CoS marking
profile)
Swap (copy P-bit and DEI) None mark all

vlan <vid>
Swap (set P-bit and DEI None mark all

according to CoS marking vlan <vid>
profile)
marking-profile <profile name>
Swap (copy P-bit and DEI) Push (set P-bit and DEI mark all
profile)
exit
vlan-tag push vlan <vid> p-bit profile <profile name>
Swap (copy P-bit and DEI) Push (copy P-bit and DEI) mark all
vlan <vid>
exit
vlan-tag push vlan <vid> p-bit copy
Push (copy P-bit and DEI) Push (copy P-bit and DEI) vlan-tag push vlan <vid> p-bit copy inner-vlan <vid> p-
bit copy
Push (copy P-bit and DEI) Push (set P-bit and DEI vlan-tag push vlan <vid> p-bit profile <profile name>
according to CoS marking inner-vlan <vid> p-bit copy
profile)
Push (set P-bit and DEI Push (set P-bit and DEI vlan-tag push vlan <vid> p-bit profile <profile name>
according to CoS marking according to CoS marking inner-vlan <vid> p-bit profile <profile name>
profile), see Note below profile), see Note below
Pop Swap (copy P-bit and DEI) mark all

inner-vlan <vid>
exit
vlan-tag pop vlan
8-44 Flows ETX-5

Action 1 Action 2 CLI Command
Pop Swap (set P-bit and DEI mark all

profile)
marking-profile <profile name>
exit
vlan-tag pop vlan
Note
Both VLAN editing actions must use the same CoS marking profile.
The TPID (Ethertype) editing policy for specific actions in E-Line topology is
detailed below:
• Push: TPID of the egress port
• Swap: TPID of the egress port
• Swap-push:
 Swap: User-configured TPID. Default setting is 8100.
 Push: TPID of the egress port
• Push-push:
 Push 1: User-configured TPID. Default setting is 8100.
 Push 2: TPID of the egress port
• Pop: Not relevant
• Pop-swap:
 Pop: Not relevant
 Swap: TPID of the egress port
• Pop-pop: Not relevant.
E-LAN VLAN Editing

The VLAN editing options available for E-LAN services at ingress and egress bridge
ports are detailed in the tables below.
Table 8-24. VLAN Editing Options at Bridge Port Ingress
Action CLI Command
None –
Pop (outer) vlan-tag pop vlan
Push (copy P-bit and DEI) vlan-tag push vlan <sp-vlan> p-bit copy
[tag-ether-type <tag-ether-type>]
Push (set P-bit to a user-configured vlan-tag push vlan <sp-vlan>p-bit fixed

value, set DEI to 0) <fixed-p-bit>[tag-ether-type <tag-ether-
type>]
Swap (copy P-bit and DEI) mark all vlan <vlan-value> p-bit copy [tag-
ether-type <tag-ether-type>]
ETX-5 Flows 8-45

Table 8-25. VLAN Editing Options at Bridge Port Egress
Action CLI Command
None –
Pop (outer) vlan-tag pop vlan
Push (copy P-bit and DEI) vlan-tag push vlan <sp-vlan> p-bit copy
Push (set P-bit and DEI according to CoS vlan-tag push vlan <sp-vlan> p-bit profile
marking profile) <marking-profile-name>
Swap (copy P-bit and DEI) mark all vlan <vlan-value> p-bit copy
Swap (set P-bit and DEI according to CoS mark all vlan <vlan-value> p-bit profile
marking profile) <marking-profile-name>
Note
• The VLAN editing options allowed at bridge port ingress also depend on the
configured flow classification method. Valid combinations are listed in
Table 8-42 and Table 8-43.
• VLAN tag swap is not available if the associated broadcast domain is
connected to a router interface.
The TPID (Ethertype) editing policy for specific actions in E-LAN topology is
detailed below:
• Bridge port egress push: TPID of the egress port
• Bridge port egress swap: TPID of the egress port
• Bridge port ingress push/swap: user-configured TPID. Default setting is 8100.
Table 8-42 details allowed combinations of flow classification method, ingress
VLAN editing action and flow VID for flows originating at directly-attached ports.
Table 8-26. Flows Originating at Directly-Attached Port
Untagged Push X VLAN X

None VLAN X
VLAN X Push Y VLAN Y
Swap (mark) Y VLAN Y
None VLAN X

Inner VLAN Y Push Z VLAN Z
Swap (mark) Z VLAN Z
Table 8-43 details allowed combinations of flow classification method, ingress

VLAN editing action and flow VID for flows originating at indirectly-attached
ports.
8-46 Flows ETX-5

Table 8-27. Flows Originating at Indirectly-Attached Ports (via SAP)
Swap (mark) X VLAN X

Match All
Push X VLAN X
Outer VLAN X None VLAN X
Inner VLAN Y
Router VLAN Editing

Router-type SVIs are considered to be untagged entities, inheriting their VLAN
properties from attached flows. Table 8-18 and Table 8-19 detail VLAN editing
options available for router interfaces.
VLAN editing option type at ingress must be the same as the one at egress (1, 2
or 3). For example, if pop (outer)/none actions (type 2) are used at ingress,
push/none (type 2) actions must be used at egress.
Table 8-28. VLAN Editing Options at Ingress Router Interface
Type Action 1 Action 2 CLI Command Remarks
1 None None – Untagged packets only
2 Pop (outer) None vlan-tag pop vlan Tagged packets only. This is the only
allowed action, when a router
interface is connected to a bridge
port.
3 Pop (outer) Pop (inner) vlan-tag pop vlan Double-tagged packets only. This
vlan-tag pop inner- action is not available, when a router
vlan interface is connected to a bridge
port.
Table 8-29. VLAN Editing Options at Egress Router Interface
1 None None –
2 Push (set P-bit None vlan-tag push vlan Tagged packets only. This is the only
and DEI <sp-vlan> p-bit profile allowed action, when a router
according to < marking-profile- interface is connected to a bridge
CoS marking name> port.
profile)
3 Push (set P-bit Push (set P- vlan-tag push vlan

and DEI bit and DEI <sp-vlan> p-bit profile
according to according to < marking-profile-
CoS marking CoS marking name> inner vlan
profile) profile) <inner-sp-vlan>
p-bit profile <inner-
marking-profile-name>
ETX-5 Flows 8-47

Note All bridge ports with flows originating from indirectly-attached ports and sharing
the same RIF broadcast domain (RIF over bridge/VLAN) must use the same VLAN
editing options.
TPID (Ethertype) editing policy for specific actions for internal router is detailed
below:
• Push:
 If a router interface is connected to a physical port, TPID is copied from a
port TPID
 If a router interface is connected to a bridge port, TPID is user-
configured. If TPID is not configured, default setting is used (8100).
• Push-push:
 Inner tag: TPID is user-configured. If TPID is not configured, default
setting is used (8100).
 Outer tag: TPID is copied from a port TPID.
SVI PW Editing
PW-type SVIs are considered to be untagged entities, inheriting their VLAN
properties from attached flows. Table 8-20 and Table 8-21 detail VLAN editing
options available for PW-type SVIs. VLAN editing option type at ingress must be
used with the similar option at egress, as detailed below:
• Ingress type 1 – egress type 1
• Ingress type 2 – egress types 3 and 4
• Ingress type 3 – egress type 3.
Table 8-30. VLAN Editing Options at Ingress PW-Type SVI
1 None None – Untagged packets only
2 Pop (outer) None vlan-tag pop vlan Single-tagged packets only
3 Pop (outer) Pop (inner) vlan-tag pop vlan vlan- Double-tagged packets only
tag-pop inner-vlan
Table 8-31. VLAN Editing Options at Egress PW-Type SVI
1 None None PtP flows
2 Push (set P-bit None vlan-tag push vlan PtP flows

and DEI according <sp-vlan> p-bit profile
to CoS marking <marking-profile-name>
profile)
8-48 Flows ETX-5

3 Push (set P-bit Push (set P-bit vlan-tag push vlan PtP flows
and DEI according and DEI according <sp-vlan> p-bit profile
to CoS marking to CoS marking <marking-profile-name>
profile) profile) inner vlan <inner-sp-vlan>
p-bit profile <inner-
marking-profile-name>
4 Push (set P-bit to None vlan-tag push vlan Multipoint flows

a fixed value and <sp-vlan> p-bit fixed
DEI=0) <fixed-p-bit>
Marking Profile
P-bit/DEI translation is further enhanced by using marking profiles that convert
CoS and packet color values into P-bit and DEI. ETX-5 supports up to 16 color-
aware and color-blind marking profiles:
• The color-aware profile translates CoS (0–7) and packet color (all, green,
yellow) into P-bit (0–7) and DEI (yellow, green) values
• The color-blind profile translates CoS (0–7) into P-bit (0–7) and DEI (yellow,
green 1) values.
Note If the DEI value is omitted during configuration, it is automatically set to 0.
RADview Performance Management Services

Flows must be tagged with a service ID to facilitate service discovery by the NMS,
running RADview Performance Monitoring portal. In addition to service ID, the
user must enable collecting performance monitoring data, using the pm-collection
command. See Configuring Flows below.
Classifier Profiles
You can define up to 24K classifier profiles to apply to flows to ensure the
desired flow classification.
 To define a classifier profile:

1. Navigate to the flows context (config>flows).
2. Define a classifier profile and assign a name to it: classifier-profile <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 <X>..<Y> ] [ inner-vlan <X>..<Y> ] [ p-bit <X>..<Y> ]
[ ip-precedence <X>..<Y> ] [ ip-dscp <X>..<Y> ] [src-mac <src-mac-low>]
[dst-mac <dst-mac-low>] [src-ip <src-ip-low>] [to-src-ip <src-ip-high>]
[dst-ip <dst-ip-low>] [to-dst-ip <dst-ip-high>] [ether-type <0xhhhh>] [untagged]
[non-ip] [all]
ETX-5 Flows 8-49

4. Using no before match deletes classification criteria, but does not delete the
classifier profile. A classifier profile can be edited only if it is not attached to
a flow.
5. no classifier-profile(<profile-name>) deletes classifier profile. A classifier
profile can be deleted only if it is not attached to a flow.
6. When you have completed specifying the criteria, enter exit to exit the
classifier profile context.
Examples
 To create classifier profile with criteria VLAN 100 to VLAN 150:

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

ETX-5# configure flows classifier-profile all match-any
ETX-5>config>flows>classifier-profile(all)$ match all
ETX-5>config>flows>classifier-profile(all)$ exit all
 To create classifier profile with criteria VLAN 10 and P-bit 5:

ETX-5# configure flows classifier-profile vlan_10+p-bit_5 match-any
ETX-5>config>flows>classifier-profile(vlan_10+p-bit_5)$ match vlan 10 p-bit 5
ETX-5>config>flows>classifier-profile(vlan_10+p-bit_5)$ exit all
Error Messages
detected.
Message Description
Illegal value Invalid value for the parameter
Classifier profile is in use and cannot be Classifier profile is being used by a flow. Remove the flow
changed/deleted association before attempting to delete or modify classifier
profile.
Classifier profiles overlap Classifier profile ranges or values overlap
Invalid VLAN ID range Invalid VLAN ID range is selected for classifier profile
This profile is not supported Invalid classifier profile for the current classification key or port
type
8-50 Flows ETX-5

Message Description
Classifier profile cannot use more than Only one match classification criteria is allowed per classifier
one match criteria for classification profile
Outer and inner VLAN classifier profile When configuring an outer and inner VLAN classifier profile, use
does not support outer VLAN range a single value for outer VLAN ID
Classifier profile: illegal range Invalid range of values for this classifier profile
Classifier profile: use of value range is This classifier profile supports a single value only
not allowed
Classifier profile cannot be added, max The maximum number of profiles (24K) has been reached and
number of profiles has been reached no additional classifier profiles can be added
Profile name must be unique The classifier profile name is not unique
Profile name cannot be changed The profile name cannot be changed because the profile is in
use
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> no classifier removes the flow
classifier profile association with the classifier
profile
Specifying the ingress port ingress-port ethernet <slot/port> no ingress-port removes the flow
ingress-port lag <port-number> association with the ingress port
ingress-port svi <port-number>

ingress-port mng-ethernet <slot/port>
ingress-port sap <slot/port/tributary>
no ingress-port
ETX-5 Flows 8-51

Specifying the egress port, and egress-port ethernet <slot/port> [queue-map-profile The queue map profile maps CoS to
the egress queue block and the <queue-map-profile-name> block <level_id/queue_id>] a queue. In ETX-5 it is permanently
queue within the block egress-port lag <port-number> [queue-map-profile set to 1:1 mapping (CoS 0 to queue
<queue-map-profile-name> block <level_id/queue_id>] 0 etc.)
egress-port svi <port-number><bridge | router | pw> If you intend to use an I/O card
port as an egress port for the flow,
egress-port mng-ethernet <slot/port>
verify that the port already has a
egress-port sap <slot/port/tributary> [queue-map- queue group profile attached to it.
profile <queue-map-profile-name> block
no egress-port removes the flow
<level_id/queue_id>]
association with the egress port
no egress-port
Assigning CoS mapping profile, or cos-mapping {[fixed <0..7>] [profile <cos-mapping-

using a fixed value for mapping profile-name>]}
user priority to internal Class of
Service values
Assigning color mapping profile, ingress-color {[ green | yellow] [profile <color-mapping-

or using a fixed value for profile-name>]}
assigning a color (green or yellow)
to incoming packets
Associating the flow with a policer policer profile <policer-profile-name> no policer removes the flow
profile or policer aggregate policer aggregate <policer-aggregate-name> association with the policer.
Policer profiles can be
added/removed or replaced on the
fly. This action affects the flow
traffic.
Associating a Layer-2 control l2cp profile <l2cp-profile-name> L2CP profiles can be attached to
protocol profile with the flow certain types of flows, as detailed
in the Layer 2 Control Protocol
(L2CP) section below.
no l2cp profile removes the flow
association with the L2CP profile
Defining swapping actions for the mark Refer to the Table 8-24 for the
flow such as overwriting the VLAN swapping action descriptions
ID or inner VLAN ID or setting the
priority
Defining window size for sampling rate-sampling-window

flow rate statistics
Administratively enabling the flow no shutdown • You can activate a flow only if it
is associated at least with a
classifier profile, an ingress
port, and an egress port.
• Flows are created as inactive by
default.
• shutdown disables the flow.
8-52 Flows ETX-5

Discarding traffic transmitted via drop

the flow
Activating the RFC-2544 test [lbm-responder] no test disables the RFC-2544

responder mode no test responder mode
Defining service ID name for its service-name <string> The flows that belong to the same
subsequent discovery by the NMS, service must be tagged in both
running RADview Performance directions
Monitoring portal
Collecting statistics calculated by pm-collection Collection can be enabled only if

current or running counters and no pm-collection statistic calculation is enabled
presented via RV Performance (pm-enable)
Management portal no pm-collection disables statistic
data collection
Enabling calculating statistic data pm-enable no pm-enable disables statistic

and incrementing intervals no pm-enable calculation.
ETX-5 supports up to 2032
PM-enabled flows per chassis.
Statistics calculation can be
enabled or disabled for inactive
(shutdown) flows only.
For the flow pairs, serving the same
bridge port, make sure that the
pm-enable setting is the same
(enabled or disabled).
Notes:
PM collection mode must be the same for the following flows:
• Ingress and egress flows within the same VLAN domain connected to the same bridge-type SVI.
• Flows with VLAN + P-bit classification with ingress port located on a main card. In this case, flows using the same VLAN and
different P-bit values (0–7) are grouped together, having the same PM collection mode.
Use these guidelines, when configuring PM collection mode for such flows:
1. Prior to flow activation, verify that the flows have the same PM collection mode (enabled or disabled).
2. Activate the flows (no shutdown).
3. If you intend to change the PM collection mode, deactivate all relevant flows (shutdown), change PM collection mode for all of
them and reactivate the flows again.
Activating MAC swap loopback on test mac-swap<ingress-port | egress-port> no test disables the loopback.
the I/O port-to-SAP flow no test The active loopback is deactivated
if ETX-5 is reset.
Displaying flow status show status See Displaying Status
Displaying current flow info

configuration
Table 8-23 lists all VLAN pushing and popping actions supported by ETX-5. For
allowed combinations of VLAN editing for E-Line, E-LAN and router and PW SVIs,
see VLAN Editing above.
ETX-5 Flows 8-53

Table 8-33. VLAN Pushing and Popping Actions
Pushing VLAN tag vlan-tag push vlan <sp-vlan>
Removing outer VLAN tag, or vlan-tag pop vlan [inner vlan]

optionally inner VLAN tag
Pushing inner VLAN tag inner-vlan <inner-sp-vlan>
Setting P-bit to a specific value p-bit fixed <fixed-p-bit>
Setting P-bit value according to p-bit profile <marking-profile-name>

marking profile
Setting P-bit value by copying p-bit copy

from the incoming frame
Setting TPID tag-ether-type <tag-ether-type>
Setting inner TPID inner-tag-ether-type <inner-tag-ether-type>
The following VLAN swapping (marking) actions can be performed at the mark
level in the config>flows>flow(flow-name)>mark# prompt.
Table 8-34. VLAN Swapping (Marking) Actions
Overwriting VLAN ID with a new vlan <vlan-value> no vlan disables the overwriting of
value VLAN ID
Overwriting inner VLAN ID with a inner-vlan <inner-vlan-value> no inner-vlan disables the

new value overwriting of inner VLAN ID
Overwriting P-bit with a new value p-bit <p-bit-value> no p-bit disables the overwriting of
P-bit
Overwriting inner P-bit with a new inner-p-bit <inner-p-bit-value > no inner-p-bit disables the
value overwriting of inner P-bit
Overwriting TPID with a new value tag-ether-type <tag-ether-type> no tag-ether-type disables the
overwriting of TPID
Overwriting inner TPID with a new inner-tag-ether-type <inner-tag-ether-type> no inner-tag-ether-type disables the
value overwriting of TPID
Overwriting P-bit according to marking-profile <marking-profile-name>

marking profile
8-54 Flows ETX-5

Overwriting inner P-bit according inner-marking-profile <inner-marking-profile-name> If a marking profile is used, it must
to marking profile be compatible with the classification
criteria of the flow.
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.
no marking-profile or
no inner-marking-profile disables the
overwriting of marking profile or
inner marking profile respectively
Exiting the marking context and exit

returning to the flow context
ETX-5 collects the current performance monitoring data for the following flow
types:
• Point-to-point flows (E-Line) and multipoint (E-LAN) flows at the bridge port
ingress
• Multipoint (E-LAN) flows at the bridge port egress.
 To display flow statistics:

• At the prompt config>flow>flow(<number>)#, enter show statistics running.
Flow statistics are displayed.
Note Interval statistic counters for flows are via RV-EMS Performance Management
portal. See the RV-EMS system manual. Enable statistic data collection, using the
pm-collection command.
ETX-5>config>flows>flow(1)# show statistics running
Rate Sampling Window

-----------------------------------------------------------------------------
Window Size [Min.] : 0
Window Remain Time [Min.] : 0
Rx
-----------------------------------------------------------------------------
Packets Bytes
Total : 26858717 3384198342
Drop
ETX-5 Flows 8-55

-----------------------------------------------------------------------------
Packets Bytes
Total : 26657156 3358801656
Green : 26657156 3358801656
Yellow/Red : 0 0
Packets/Sec Bits/Sec
Total : 838377 845084016
Green : 838377 845084016
Yellow/Red : 0 0
Tx
-----------------------------------------------------------------------------
Packets Bytes
Total : 282067 35540442
Green : 282067 35540442
Yellow : 0 0
Packets/Sec Bits/Sec
Total : 6209 6258672
Green : 6209 6258672
Yellow : 0 0
Peak Measurement
-----------------------------------------------------------------------------
Minimum Maximum
Tx Bit Rate [bps] : 6143760 9326016
Drop Bit Rate [bps] : 658197792 859194000
• At the prompt config>flow>flow (number)#, enter clear-statistics.
Displaying Status
You can display current status of existing flows.
 To display flow status:

• In the config>flows>flow(flow-name)# prompt, enter show status.
The flow status is displayed.
ETX-5>config>flows>flow(3) show status
Service Name : VOD
Status Details
-----------------------------------------------------------------------------
Ingress Port Oper Status : Up
Egress Port Oper Status : Up
8-56 Flows ETX-5

OAM CFM Details

-----------------------------------------------------------------------------
Type MD MA Entity
-----------------------------------------------------------------------------
MEP 1 1 1
MIP 1
Flow status screen provides information on:

• Operational status of the flow
• Name of the RADview service to which the flow belongs
• Operational status of the ingress port
• Operational status of the egress port
• MAP and MIP details if the flow is used in OAM CFM.
Displaying Flow Summary

You can display a brief or detailed summary of all flows that exist in the system.
 To display brief flow summary:

• In the config>flows# prompt, enter show summary brief.
The brief flow summary is displayed.
ETX-5>config>flows# show summary brief
Name Ingress Tx
Admin | Oper | Classification Egress Rx
mng_in MNG ETH main-a/0 0

Ena | Up | untag SVI 1 0
mng_out SVI 1 0
Ena | Up | all MNG ETH main-a/0 0
a1_l2cp Ethernet main-a/1 1452

Ena | Down | untag Ethernet main-a/4 1452
8_10 Ethernet main-a/1 0

Ena | Up | 10 SVI 8 0
8_10_1 SVI 8 0
Ena | Up | 10 Ethernet main-a/1 0

Ena | Up | 20 SVI 8 0
ETX-5 Flows 8-57

8_20_1 SVI 8 0

Ena | Up | 30 SVI 8 0
8_30_1 SVI 8 0
more..
 To display detailed flow summary:

• In the config>flows# prompt, enter show summary detailed.
The detailed flow summary is displayed.
ETX-5>config>flows# show summary detailed
Name : mng_in
Admin Status : Up
PM : Disable
Service Name :
Test : Off
Classifier : untag
Ingress Port : MNG ETH main-a/0

Egress Port : SVI 1
OAM CFM Details

-----------------------------------------------------------------------------
Type MD MA Entity
-----------------------------------------------------------------------------
Name : mng_out
Admin Status : Up
PM : Disable
Service Name :
Test : Off
Classifier : all
Ingress Port : SVI 1

Egress Port : MNG ETH main-a/0
OAM CFM Details

-----------------------------------------------------------------------------
Type MD MA Entity
8-58 Flows ETX-5

-----------------------------------------------------------------------------
Name : a1_l2cp
Admin Status : Up
more..
Examples
The following examples show the configuration of point-to-point (E-Line) and
multipoint (E-LAN) flows.
Multiple CoS Point-to-Point Service

This section gives an example of configuring an E-Line application for multi-CoS
point-to-point service. Incoming traffic is classified into four EVC.CoS flows with
policing and traffic prioritization. The aggregated EVC traffic is scheduled, shaped
and forwarded to the egress port on the main card. The SVLAN tag (VLAN 300) is
also pushed at this stage. On the return path, the traffic is classified and
forwarded back to the I/O Ethernet card port with the SVLAN tag popped on the
way.
Figure 8-5 shows the flows to be configured for this application.
Figure 8-16. Multi-CoS Point-to-Point Service Flows
 To configure multiple CoS point-to-point service:

3. Assign previously configured queue groups to the I/O card port, main card
port and SAG.
Note Queue group configuration is omitted in this example.
ETX-5 Flows 8-59

4. Select classification keys for the I/O and main card ports.
5. Enable the I/O and main card ports.
6. Configure the policer profiles to distribute available bandwidth among flows
11–14.
7. Configure the CoS mapping profile to map user priorities to internal CoS
values.
8. Configure the color mapping profile to map user color to internal color values.
9. Configure six classifier profiles:
 Four profiles for traffic from I/O card to SAP
 One profile for traffic from SAP to main card
 One profile for traffic from main to I/O card.
10. Configure six flows:
 Four flows from I/O card port to SAP with per-flow policing, CoS and color
mapping
 One flow from SAP to main card port, push S-VLAN to this flow with S-VID
P-bit and DEI values set by a marking profile
 One returning flow from main card port to I/O card port, pop S-VLAN.
#***************************Defining_Policer_Profiles************************
config qos policer-profile "3" bandwidth cir 10000 cbs 10000 eir 100000 ebs
64000
config qos policer-profile "4" bandwidth cir 55000 cbs 10000 eir 100000 ebs
64000
exit all
#*********************************End****************************************
#***************************Assigning_Queue_Groups***************************
config port ethernet main-a/1 queue-group profile 3level_1
exit all
#*********************************End****************************************
#***************************Selecting_Classification_Key*********************
exit all
#*********************************End****************************************
#***************************Enabling_Ports***********************************
exit all
#*********************************End****************************************
8-60 Flows ETX-5


exit all

exit all

exit all

exit all
config flows classifier-profile match-all match-any

match all
exit all

exit all
#*********************************End****************************************
#************************Configuring_CoS_Mapping_Profile*********************
config qos cos-map-profile cosvzb classification p-bit
map 0 to-cos 6
map 1 to-cos 5
map 2 to-cos 5
map 3 to-cos 5
map 4 to-cos 5
map 5 to-cos 4
map 6 to-cos 0
map 7 to-cos 0
exit all
#*********************************End****************************************
#**************************Configuring_Color_Mapping_Profile*****************
config qos color-map-profile color_all_green classification p-bit
map 0 to green
map 1 to green
map 2 to green
map 3 to green
map 4 to green
map 5 to green
map 6 to green
map 7 to green
exit all
#*********************************End****************************************
#*****************Configuring_Marking_Profile *******************************
ETX-5 Flows 8-61

configure qos marking-profile mark1 classification cos color-aware green-

yellow dei mapping
mark 0 yellow to 7 dei green
mark 6 yellow to 0 dei yellow
exit all
#*********************************End****************************************
#****************************************************************************
#****************************************************************************
#********************Configuring_EVC.CoS_Flows_from_I/O_to_SAP***************
cos-mapping profile cosvzb
ingress-color profile color_all_green
policer profile 1
no shutdown
exit all

policer profile 2
no shutdown
exit all

policer profile 3
8-62 Flows ETX-5

no shutdown
exit all

policer profile 4
no shutdown
exit all
#********************Configuring_EVC_Flow_from_SAP_to_Main_Card**************
0/1
vlan-tag push vlan 300 p-bit profile mark1
no shutdown
exit all
#********************Configuring_Flow_from_Main_to_I/O_Card******************

vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
ETX-5 Flows 8-63

Multipoint Service
This section provides an example of configuring an E-LAN application built on a
four-port bridge with all bridge ports sharing the same VLAN domain (VLAN 10).
Figure 8-6 shows the flows to be configured for this application.
Figure 8-17. Multipoint Service Configuration

 To configure a multipoint service:
1. Assign previously configured queue groups to the I/O card port, main card
port and SAG.
2. Select the classification key for I/O and main card ports.
2. Enable the I/O and main card ports.
values one-to-one.
4. Configure the color mapping profile to convert CoS values to green color.
5. Add the bridge-type SVIs and bind them to the bridge ports.
6. Define the bridge port VLAN membership (VLAN domain for bridge ports 1–4
for VLAN 10 with MAC table size of 256.
7. Configure the classifier profile (VLAN + P-bit).
8. Define eleven flows according to Figure 8-6.
#***********************Assigning_Queue_Group_Profiles***********************
exit all
8-64 Flows ETX-5

#*********************************End****************************************
#****************************Selecting_Classification_Key********************
exit all
#*********************************End****************************************
#****************************Enabling_Ports**********************************
exit all
#*********************************End****************************************
#****************************Configuring_Classifier_Profile******************
match vlan 10
exit all
#*********************************End****************************************
#***************************Configuring_COS_Mapping_Profile******************
config qos color-map-profile color1 classification p-bit
exit

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
exit all
#*********************************End****************************************
#************************** Configuring_Color_Mapping_Profile ***************

map 0 to green
map 1 to green
map 2 to green
map 3 to green
map 4 to green
map 5 to green
map 6 to green
map 7 to green
exit all
#*********************************End****************************************
#*************************Defining_Bridge_SVIs*******************************
ETX-5 Flows 8-65


exit all
exit all
exit all
exit all
#*********************************End****************************************
#*************************Binding_Bridge_Ports_to_SVIs***********************
bind svi 11
exit all

bind svi 12
exit all

bind svi 13
exit all

bind svi 14
exit all
#*********************************End****************************************
#************** Configuring_VLAN_Membership_and_MAC_Table_Size **************

config bridge 1 vlan 10
tagged-egress 1..4
maximum-mac-addresses 256
exit all
#*********************************End****************************************
#************************Configuring_Flows_to/from_Bridge_Port_1*************
classifier class10
egress-port svi 11
no shutdown
exit all

classifier class10
ingress-port svi 11
0/1
no shutdown
exit all
#*********************************End****************************************
8-66 Flows ETX-5


classifier class10
no shutdown
exit all

classifier class10
egress-port svi 12
no shutdown
exit all

classifier class10
ingress-port svi 12
no shutdown
exit all
#*********************************end****************************************
classifier class10
no shutdown
exit all

classifier class10
egress-port svi 13
no shutdown
exit all

classifier class10
ingress-port svi 13
no shutdown
exit all
#*********************************End****************************************
classifier class10
ETX-5 Flows 8-67


no shutdown
exit all

classifier class10
egress-port svi 14
no shutdown
exit all

classifier class10
ingress-port svi 14
no shutdown
exit all
#*********************************End****************************************
detected.
Message Description
Ethertype tag is unknown, setting Not a valid value for the Ethertype tag
failed
L2CP profile does not exist The L2CP profile cannot be assigned to the flow because the profile
has not been defined
Illegal value Invalid value for parameter
Flow creation failure: max number of The maximum number of flows (24K) has been reached and no
flows reached flows can be added
Flow is in use The current flow is being used and cannot be deleted or modified
A MIP/MEP is defined on the flow A flow is assigned to a MIP or MEP instance
Active MIP is defined on the flow, A flow cannot be shut down if it has a MIP assigned to it
shutdown failed
Active MEP is defined on the flow, A flow cannot be shut down if it has a MEP assigned to it
shutdown failed
SVI is not configured An SVI must be defined before a flow can be bound to it
Illegal flow-SAG combination in policer The policer profile cannot be used because not all of its flows are
aggregate profile bound to the same SAG
Max number of flows per policer The maximum number of flows per policer aggregate (16) has been
aggregate profile has been reached reached and no flows can be added to the profile
Classifier profile is not attached The required classifier profile has not been attached to the flow
8-68 Flows ETX-5

Message Description
CoS or color profile is missing The CoS or color profile has not been assigned to a flow
CoS or color profile are unnecessary The CoS or color profile cannot be attached to an ingress flow,
originating from a TDM port
CoS and color profile mismatch A discrepancy between the CoS and color mapping methods
Illegal CoS method Invalid CoS mapping method for the current flow type or ingress
color mapping method
Illegal color method Invalid color mapping method for the current flow type or ingress
CoS mapping method
Port classification key and CoS Invalid combination of port classification key and CoS mapping
method mismatch method
Port classification key and color Invalid combination of port classification key and color mapping
method mismatch method
Max number of CoS or color profiles The maximum number of CoS or color profiles per I/O card (36) has
for I/O card has been reached been reached and no profiles can be added to flows originating
from the I/O card
Max number of color profiles for I/O The maximum number of color profiles per I/O card (36) has been
card has been reached reached and no profiles can be added to flows originating from the
I/O card
Policer is not supported Policer and policer aggregate profiles can be attached to flows
originating from indirectly-attached ports only
Flow is in use, change failed The flow is being used and cannot be modified
Ingress I/O card port does not match Mismatch between ingress port of the flow and SAG number
SAG
Mismatch between flow SVI (B) and Flows originating from the same bridge-type SVI must terminate in
egress port the same port
Mismatch between flow SVI (B) and Flows originating from the same bridge-type SVI must terminate in
egress slot the same slot
Inner editing action error Invalid editing action for inner VLAN
Outer editing action error Invalid editing action for outer VLAN
Inner + outer editing action error Invalid editing action for inner and outer VLANs
Inner + outer editing action error for Invalid editing action for inner and outer VLANs on a flow in
bridge service multipoint service
Inner + outer editing action error for Invalid editing action for inner and outer VLANs on a flow in
P2P service point-to-point service
Inner + outer editing action error for Invalid editing action for inner and outer VLANs on a flow in Layer-3
router service service
Classification + editing error for Invalid classification and VLAN editing action on a flow in multipoint
bridge service service
Bridge port is not a member of The bridge port must be a member of an outer VLAN of the frame
identified VLAN remaining at the entrance to the bridge port
ETX-5 Flows 8-69

Message Description
VLAN editing error for a P2P flow Invalid VLAN editing action for a point-to-point flow starting from
starting from PW SVI PW-type SVI
Editing of ingress I/O flows is not Cannot perform VLAN editing on ingress I/O flows
allowed
Max number of L2CP profiles bound The maximum number of L2CP profiles per port (4, including
to a port has been reached default) has been reached and no profiles can be added
Max number of L2CP profiles bound The maximum number of L2CP profiles per flow (1) has been
to a flow has been reached reached and no profiles can be added
Ingress port has not been defined yet The ingress port selected for a flow has not yet been defined
Egress port has not been defined yet The egress port selected for a flow has not yet been defined
Ingress LAG port has less than 2 ports If a LAG serves as a flow ingress port, it must have two ports
bound to it assigned to it
Egress LAG port has less than 2 ports If a LAG serves as a flow egress port, it must have two ports
bound to it assigned to it
Number of ingress SAPs has been Cannot define a SAP as an ingress port for a flow if the SAP number
exceeded is higher than 1024
Number of egress SAPs has been Cannot define a SAP as an egress port for a flow if the SAP number
exceeded is higher than 1024
Specified queue group does not exist A queue group assigned to a flow has not yet been defined
Flow type is not valid
Classification type is not valid for the A discrepancy between the classification key of port and the
ingress port classification method of the flow
Classification type cannot include P- The P-bit classification cannot be used for flows originating from
bit bridge-type SVIs
Max number of port-based flows per The maximum number (128) of port-based flows per SAG has been
SAG has been exceeded exceeded
Max number of VLAN-based flows per The maximum number (128) of VLAN-based flows per SAG has been
SAG has been exceeded exceeded
Classification type must be VLAN or Only VLAN or untagged classification is allowed

untagged
Classification type must be VLAN Only VLAN classification is allowed
Classification type must be VLAN or Only VLAN or Inner VLAN classification is allowed
Inner VLAN
Classification type must be VLAN, Only VLAN, Inner VLAN or Match All classification is allowed
Inner VLAN or Match All
Classification type must be Match All Only Match All classification is allowed for flows originating from
for ingress port SVI (R) router-type SVI
Classification type must be Match All Only Match All classification is allowed for flows originating from
for ingress port SVI (PW) PW-type SVI
8-70 Flows ETX-5

Message Description
Classification type must be Match All Only Match All classification is allowed for point-to-point flows
for P2P SAP flow originating from SAP
Classification type must be untagged Only untagged classification is allowed
VLAN number is out of limit VLAN number exceeded maximum allowed value
Other classification type already Another classification type has already been defined for the VLAN.
defined for the VLAN Source MAC, destination MAC, source IP, destination IP and
Ethertype classifications must be unique per VLAN.
Classification entry already exists for Another type of classification entry already exists for the port. The
the P-bit classification type must be unique for the port.
Only single VLAN is allowed for this VLAN ranges are not allowed for the selected classification type
classification type
Only single VLAN is allowed for SVI VLAN ranges are not allowed for flows terminating in router- or
router/bridge egress port bridge-type SVIs
Only single VLAN is allowed for SVI VLAN ranges are not allowed for flows originating from router- or
router/bridge ingress port bridge-type SVIs
Only single MAC is allowed for this MAC ranges are not allowed for the selected classification type
classification type
Only single IP is allowed for this IP ranges are not allowed for the selected classification type
classification type
Only single P-bit is allowed for this P-bit ranges are not allowed for the selected classification type
classification type
Only one P-bit range is allowed for A single P-bit is not allowed for the selected classification type
this classification type
8.5 Layer 2 Control Protocol (L2CP)

ETX-5 tunnels, discards or peers (trap to host for protocol processing) L2CP
packets. These actions are defined by L2CP profiles, which also provide different
L2CP addresses. L2CP profiles are attached to ports or flows.
Standards
IEEE 802.3
Benefits
ETX-5 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-5 Layer 2 Control Protocol (L2CP) 8-71

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 the flow traffic
behaves, by default, according to the port profile.
ETX-5 handles Layer-2 control protocol traffic on a per-port and/or a per-flow
basis. If no per-flow L2CP profile is configured, a per-port-level profile is used. It
affects both tagged and untagged L2CP frames.
L2CP traffic is processed using a two-stage mechanism comprising per-port or
per-flow profiles (set of rules for traffic handling). In total, ETX-5 supports up to
16 L2CP profiles:
• Up to 4 (including default) port-level and a single flow-level profiles can be
defined on directly-attached ports
• Up to 32 different addresses/protocols can be selected per L2CP profile.
If no default action is configured for an unspecified address or protocol, this
traffic is tunneled.
Note If an L2CP profile has been attached to a port or a flow, the profile cannot be
deleted or modified.
L2CP Profile Settings

ETX-5 can tunnel, discard, or peer (trap to host for protocol processing) L2CP
packets . These actions are defined by L2CP profiles per MAC address or protocol
loopback.
The following MAC addresses are supported by L2CP profiles:
• 01-80-C2-00-00-00, 01-80-C2-00-00-02 –10
• 01-80-C2-00-00-20 – 2F
In addition to the L2CP address range defined by MEF, the L2CP profile supports
handling (discard or tunnel) proprietary protocols:
• 01-00-0C-CC-CC-CC: PAGP, UDLD, CDP, VTP, DTP
• 01-00-0C-CC-CC-CD: PVSTP
• Loopback (Ethertype 0x9000)
Note • PAUSE frames (01-80-C2-00-00-01) are not part of L2CP profiles. They are
either peered or discarded according to the flow control setting of a port.
• Peer action at flow level is supported only for 01-80-C2-00-00-02 frames
(LACP, marker protocol, SSM).
L2CP profiles are configured at the port, and, optionally, at the flow level.
According to per-port or flow L2CP profiles, ETX-5 performs the following:
8-72 Layer 2 Control Protocol (L2CP) ETX-5

• Discards L2CP traffic. In this case, per-port L2CP handling configuration

supersedes per-flow profile, as the L2CP traffic is dropped before it is
processed by per-flow profile.
• Tunnels L2CP traffic. ETX-5 forwards the traffic according to its configuration
(flows, etc). The final decision (drop, tunnel or peer) is made according the
per-flow profile setting. If no per-flow profile is configured, the L2CP traffic is
handled according to per-port profile setting.
• Tunnel with MAC swap. ETX-5 forwards L2CP protocols with the destination
MAC address swapped to a preconfigured MAC address. This address is
swapped back in the opposite direction.
• Peer: Forwards traffic to the CPU. This means that for LACP support, for
example, a peer action should be configured in the port level profile.
L2CP Profiles and Traffic Classification Keys

L2CP profiles can be attached only to flows created using the classification types
detailed in Table 8-31.
Table 8-36. L2CP Profiles and Classification Keys
Classification Key Flow Classification Type
VLAN + P-bit VLAN, VLAN + P-bit

Untagged (used for per-port L2CP profiles as well)
Unclassified (indirectly-attached ports only)
VLAN + Src/Dest MAC (indirectly-attached ports only)
Outer VID + P-bit + VLAN (outer)
Inner VID Outer VLAN + P-bit + Inner VLAN
Unclassified (indirectly-attached ports only)
VLAN + Src MAC
VLAN + IP-P or LAN + Non IP
VLAN + DSCP Untagged (used for per-port L2CP profiles as well)
Unclassified
P-bit P-bit
Unclassified
IP-P, Non IP (used for per-port L2CP profiles as well)
DSCP Unclassified
L2CP Tunnel with MAC Swap (L2PT)

ETX-5 allows MAC swap to be performed on L2CP packets, which means that L2CP
packets can be forwarded over networks that are not transparent to L2CP. The
L2CP profile that includes the L2CP MAC swap can be bound to IO ports only.
L2CP tunnel with MAC Swap is not supported on main card ports and at flow
level.
L2PT functionality in ETX-5 is as follows:

1. User to Network: IO port ingress traffic identified with the configured

protocols is MAC swapped to a user preconfigured multicast address and
proceeds with the original traffic path as set by classification (tunnel). The
actual functionality for these protocols is a tunnel with MAC swap.
9. Nework to User: IO port ingress traffic identified with the pre configured L2PT
multicast MAC address is MAC swapped to the original protocol MAC. Traffic
then proceeds with the original graffic path as set by classification to the
egress port.
The following protocols are supported:
• LACP
• STP
• VTP
• CDP
• LLDP
• PVSTP
• PAGP
• UDLDd
• DTP
A single MAC address (per device) is supported for L2CP MAC swap. The last L2PT
MAC bound is the MAC used.
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.
3. Configure the L2CP profile as needed (refer to Configuring Layer 2 Control
Processing Profile Parameters).
Deleting Layer 2 Control Processing Profiles

You can delete an L2CP profile only if it is not assigned to any port.
 To delete an L2CP profile:
2. Type no l2cp-profile <l2cp-profile-name>
The L2CP profile with the specified name is deleted if it is not assigned to any
port.

Configuring Layer 2 Control Processing Profile Parameters
 To configure an L2CP profile:

1. Navigate to configure port l2cp <l2cp-profile-name> to select the L2CP profile
to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
Specifying the default action for default {discard | tunnel}

undefined control protocols
Specifying the L2CP action for MAC mac <mac-addr-last-byte-value-list> {discard | tunnel | discard – L2CP frames are
addresses (discard, tunnel, or peer) peer} discarded
tunnel – L2CP frames are
forwarded across the network
as ordinary data
peer –ETX-5 peers with the user
equipment to run the protocol.
L2CP frames are forwarded to
the ETX-5 CPU. Unidentified
L2CP frames are forwarded
across the network as ordinary
data. The peer actions are
supported at the flow level
only.
no mac
<mac-addr-last-byte-value-list>
removes the action for the
specified MAC address
Defining a loopback protocol for Typing no protocol loopback
protocol loopback discard
removes the action for the
discarding
Loopback protocol.

Specifying the protocols in which protocol { lacp | stp | vtp | cdp | lldp | pvstp| pagp | udld | protocol – list of L2CP protocols
MAC swap is desired dtp} tunnel mac-change [<mac-address>] in which L2CP MAC swap is
required
mac-address – the MAC address
to be used as an alternative to
the original MAC. The mac-
address configured should be
multicast 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
protocol.
Adding Layer 2 Control Processing Profiles

 To add an L2CP profile:
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.
3. Configure the L2CP profile as needed (refer to Configuring Layer 2 Control
Processing Profile Parameters).
Deleting Layer 2 Control Processing Profiles

You can delete an L2CP profile only if it is not assigned to any port.
 To delete an L2CP profile:
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.
Examples
 To add L2CP profile named layer2ctrl1 with peer action:
ETX-5>config>port# l2cp profile layer2ctrl1

ETX-5>config>port>l2cp profile(layer2ctrl1)$ mac 01-80-C2-00-00-02 peer
 To add L2CP MAC swap configuration for layer2ctrl1 profile on stp packets
ETX-5>config>port>l2cp-profile(layer2ctrl1)# protocol stp tunnel mac-change
01-23-45-67-89-DD
 To delete L2CP profile named layer2ctrl1:

ETX-5>config>port# no l2cp-profile layer2ctrl1
ETX-5>config>port#
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.

For 1GbE IO ports, only the number of encapsulated packets for each protocol is
displayed.
ETX-5300A>config>port>eth(1/1)# show l2cp-statistics
Protocol Encapsulated Decapsulated
LACP 0 0
STP 0 0
CDP 0 0
VTP 0 0
8.6 Link Layer Discovery Protocol (LLDP)

LLDP is a standard layer-2 protocol that allows Ethernet network devices to
advertise information about themselves, and to 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.
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
management port. LLDP information is exchanged by means of LLDP packets.
LLDP Bridge Types

LLDP works according to the following bridge types (user-configurable via
bridge-type in config>sys>lldp):
• Nearest bridge – The propagation of LLDP packets is limited to a single
physical link, and is stopped by any type of bridge.
• Nearest customer bridge – The propagation of LLDP packets is limited by
customer bridges - supported by Tx LLDP messages only (no termination).
• Nearest non-TPMR bridge – The propagation of LLDP packets is limited by
non-TPMR bridges. Typically this mode is used in provider bridged networks -
supported by Tx LLDP messages only (no termination).
TPMR (Two-port MAC Relay) indicates a bridge that has only two
externally-accessible bridge ports, and supports a subset of the regular
8-78 Link Layer Discovery Protocol (LLDP) ETX-5

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 ETX5 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 address – Set to 01-80-C2-00-00-0E
• Source MAC address – Set to port MAC address
• Ether Type – Set to 0x88CC
• LLDP Protocol Data Unit (LLDPDU) – contains a variable number of
information units called TLVs: mandatory TLVs, optional TLVs, and an
EndOfLLDPDU 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, etc.
Table 8-38. 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 IfDesc perRFC 2863, which is port name Optional
System Name Device name as configured by CLI (per Optional

RFC 3418 )
System Description SysDesc 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
ETX-5 Link Layer Discovery Protocol (LLDP) 8-79

TLV Name Description TLV Appears in

LLDPDU
End Of LLDPDU N/A; indicates end of LLDPDU Mandatory
Table 8-39. 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)
• ERPv2 if G.8032 ring is configured on the port
Table 8-40. Organization-Specific IEEE 802.3 TLVs
TLV Name Description
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.
Parameter Default Remarks
bridge-type nearest-bridge
hold-multiplier 4 Value is in seconds
shutdown no shutdown LLDP is administratively enabled for

all relevant interfaces
tx-interval 30 Value is in seconds
Configuring LLDP
This section explains how to define LLDP and enable LLDP Packet Data Unit
(LLDPDU). ETX-5 supports up to 90 LLDP connections.
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, to specify which
TLVs to send for the port.
LLDP Traffic
To ensure correct distribution of LLDP traffic, you must configure a L2CP profile
with peer action at the port or flow level. The peer must be directed to the LLDP
address (01-80-C2-00-00-0E).
When configuring the L2CP profile at the flow level, the flow must have the
following attributes:
• Ingress port – LLDP required port
If you use the flow only to peer the LLDP frames and do not need to forward the
LLDP on Main Card Using L2CP Profile at the Flow Level

When configuring LLDP on main card ports Connect LLDP Port to a single flow as
defain above.
The figure below illustrates LLDP flows in main cards.
Figure 8-18. LLDP in Main Cards
• LLDP on management ports.

When configuring LLDP on management ports, make sure to insert L2CP
profie to the flow that going form the management ports to the SVI in order
to recive LLDPDUs
• LLDP on ports that are bind to LAG.
When configuring LLDP on ports that are bind to LAG make sure to insert
both MAC peer addresss to the same L2CP profie and use it with both LAG
and LLDP relevant Flows
Special Considerations for LLDP on I/O Cards Using L2CP

Profile at the Flow Level
This section describes special requirements that must be followed when creating
LLDP on I/O cards using a L2CP profile at the flow level.

Port/SAP Connection
When configuring LLDP between ports on the E5-GBE-20 or E5-10GBE-2 cards,
follow these guidelines for establishing flows between the LLDP port and the
SAP:
• Connect LLDP Port to a SAP, belonging to the first 10-port group
(SAP slot/1/x) and then use second flow to Connect to the
The figure below illustrates LLDP flows in IO cards.
Figure 8-19. LLDP in IO Cards
Note If the L2CP is configured on the relevant LLDP port, the flows for LLDP should not
be created.
System Parameters
This section explains how to configure global parameters such as bridge type, as
well as enable or disable LLDP for the device.
Note Currently only one management address is supported. If a global management

address was configured, it is sent. If not, the lowest address from which the
device can be managed is sent on all ports that allow management access. If no
management IP address is configured, then the TLV won’t be sent.
 To configure LLDP system parameters:

1. Navigate to configure system lldp.
The config>system>lldp# prompt is displayed.
Specifying device bridge type bridge-type {nearest-bridge | customer-bridge | • nearest-bridge – Propagation of

non-tpmr-bridge } LLDP packets is stopped by any
type of bridge
• customer-bridge – Propagation
of LLDP packets is stopped by
customer bridges
• non-tpmr-bridge – Propagation
of LLDP packets is stopped by
non-TPMR bridges

Specifying how long device should hold hold-multiplier <seconds>

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 (seeTable 8-33 to Table 8-35 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.
In case of management port, navigate to configure port mng-ethernet main-
[<slot>/]<port>.
The prompt config>port> mng-eth(main ([<slot>/]<port>)# is displayed.
Enabling or disabling 802.1-management-vlan-id Not supported

transmission of IEEE 802.1
management VLAN ID
Enabling or disabling 802.1-protocol-identity {efm | cfm |

transmission of the specified lag-lacp | rstp-mstp | erp-v2 | etp |
protocol in the IEEE 802.1 elmi}
protocol identity TLV (see
Table 8-34)
Enabling or disabling 802.1-vlan-name <vlan-id> Not supported

transmission of IEEE 802.1 VLAN
name
Enabling or disabling customer-bridge-802.1 port-vlan-id

transmission of IEEE 802.1 port
VLAN ID TLV (see Table 8-34) in
customer bridge mode
Enabling or disabling customer-bridge-802.3 • mac-phy-configuration:

transmission of IEEE 802.3 TLVs [mac-phy-configuration] MAC/PHY
(see Table 8-35) in customer [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 TLV
Table 8-33) in customer bridge [management-address]
• sys-description: System
mode
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.1 port-vlan-id

nearest bridge mode
Enabling or disabling nearest-bridge-802.3 • mac-phy-configuration:

(see Table 8-35) 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

Table 8-33) in nearest bridge [management-address]
mode
description TLV
capabilities 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.1 port-vlan-id

non-TPMR bridge mode

Enabling or disabling non-tpmr-802.3 • mac-phy-configuration:

(see Table 8-35) 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

Table 8-33) in non-TPMR bridge [management-address]
mode
description TLV
capabilities TLV
Specifying transmission mode in non-tpmr-bridge-mode {tx | rx | • tx: Transmit LLDP packets

non-TPMR bridge mode tx-rx} •
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
Examples below illustrate how to configure different types of LLDP.
LLDP on Main Cards

To peer LLDP frames, configure a L2CP profile with peer action for the LLDP
address. This profile can be associated to the LLDP port or to a dedicated flow
with untagged classifier from the LLDP port. As the only purpose of this flow is to
peer LLDP traffic, you can discard its traffic by using a drop action.
 To configure LLDP on Main Card Ports (with L2CP profile over port).
#*********************************Configuring_LLDP in system*****************
configure system lldp

tx-interval 30
hold-multiplier 2
no shutdown
exit all

configure port l2cp lldp
mac 01-80-c2-00-00-0e peer
exit all
#*****************************Configuring_LLDP in port***********************
configure port ethernet main-a/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 port-description
nearest-bridge-basic-management management-address
nearest-bridge-802.3 max-frame-size
nearest-bridge-802.3 mac-phy-configuration
802.1-protocol-identity lldp
802.1-protocol-identity efm
802.1-protocol-identity cfm
802.1-protocol-identity lag-lacp
802.1-protocol-identity rstp-mstp
802.1-protocol-identity erp-v2
exit all
#***************************** Assigning l2cp profile************************
configure port ethernet main-a/1 l2cp profile lldp
configure port ethernet main-a/1 no shutdown
#*********************************End****************************************
 To configure LLDP on Main Card Ports (with L2CP profile over flow):
confure system lldp

tx-interval 30
hold-multiplier 2
no shutdown
exit all
configure port ethernet main-a/1 lldp


exit all

no shutdown
exit all
#************************Configuring_Classifier_Profiles*********************
configure flows classifier-profile classunt match-any

match untagged
exit all
configure port l2cp lldp
mac 01-80-c2-00-00-0e peer
exit all
classifier classunt
0/1
l2cp profile lldp
no shutdown
exit all
#*********************************End****************************************
 To configure LLDP on IO Card Port (with L2CP profile over port):


tx-interval 30
hold-multiplier 2

no shutdown
exit all
configure port l2cp lldp_io
mac 01-80-c2-00-00-0e peer
exit all
configure port ethernet 1/10 lldp

exit all
#***************************** Assigning L2CP profile************************
configure port ethernet 1/10 l2cp profile lldp_io
configure port ethernet 1/10 queue-group profile q_group_2_level_default
configure port ethernet 1/10 no shutdown
#*********************************End****************************************
 To configure LLDP on IO Card Port (with L2CP profile over flow):

tx-interval 30
hold-multiplier 2
no shutdown
exit all
configure port ethernet 1/10 lldp

exit all

configure port ethernet 1/10 queue-group profile q_group_2_level_default
configure port sag 1/1 queue-group profile q_group_SAG_2_level_default
configure port ethernet 1/10

no shutdown
exit all
configure flows classifier-profile classutg match-any

match untagged
exit all
configure flows classifier-profile classAll match-any

match all
exit all
configure flows classifier-profile classunt match-any

match untagged
configure port l2cp lldp_io
mac 01-80-c2-00-00-0e peer
exit all

classifier classutg
l2cp profile lldp_io
no shutdown

exit all

classifier classAll
0/1
no shutdown
exit all
#*********************************End****************************************
8.7 Peers
Remote devices that are destinations for pseudowire traffic or serve as a
grandmaster for 1588v2 slave clock entities are referred to as peers.
Factory Defaults
By default, there are no peers in the ETX-5 system.
Benefits
Peers serve as destinations for pseudowire connections for transporting a TDM
payload over packet-switched networks. In addition, they are configured to be
sources for the master clock used by 1588v2 slave entities.
Peers are remote devices operating opposite router interfaces. You can define up
to 1334 peers for pseudowire or 1588v2 traffic, with each assigned a unique
index number. The index number is used to specify the pseudowire destination,
instead of directly providing the necessary destination information. To configure
a UDP/IP peer, you must provide its IP address. For MEF-8 peers, you must specify
the MAC address of the destination device.
Configuring Remote Peers

 To add a remote peer:
• At the config>peer # prompt, type the peer number in the range of 1 to
1334.
 To configure a remote peer:

• At the config>peer (number) # prompt, enter all necessary commands
according to the tasks listed below:
8-90 Peers ETX-5

Defining the IP address of a ip <valid IP address>

remote peer in UDP/IP networks
Assigning a name to a remote name <alphanumeric string >

peer
Specifying number of a router router <1> This parameter is permanently

instance set to 1
Defining MAC address of a mac<valid MAC address>

remote peer in MEF-8 networks
 To remove a remote peer:

• At the config>peer (peer number) # prompt, type no peer (peer number).
Note Setting remote peers as destinations is done under:

• configure>pwe for PWs
• config>system>clock>recovered(main-a/1 or main-b/1)>master 1 or master 2
for 1588v2 traffic.
 To display the remote peer table:

• At the config# prompt, type info and scroll to the corresponding section.
ETX-5>config# info
peer 1 ip 6.6.6.7
peer 2 ip 172.17.153.191 name "peer_2"
peer 3 ip 172.17.154.192 name "peer_3"
Example
 To configure remote peer 1 for UDP/IP PSN:
• IP address: 9.9.9.9
• Name: peer1.
ETX-5>configure peer 1 ip 9.9.9.9 name peer1
 To configure remote peer 1 for MEF-8 PSN:

• MAC address: 00-20-d6-54-bf-05
• Name: peer2.
ETX-5>configure peer 1 mac 00-20-d6-54-bf-05 name peer2
 To delete remote peer 1:

ETX-5>config# no peer 1
Note
See Pseudowire Service section for a detailed example of a pseudowire
configuration.
ETX-5 Peers 8-91

detected.
Message Description
Peer is in use: Peer cannot be updated if Cannot modify a peer that is being used by a pseudowire
used
Peer is in use: Peer cannot be removed if Cannot delete a peer that is being used by a pseudowire
in use
Peer index is invalid Peer index is out of allowed range
Peer set failed: Maximum number of Cannot create a peer because the maximum number of
targeted peers already configured pseudowire peers (1334) has been reached
Peer set failed: Peer IP must not be a IP address of pseudowire peer on UDP/IP network cannot be
multicast IP multicast
Peer set failed: Maximum number of Cannot create a peer because the maximum number of
peers already configured pseudowire peers (1334) has been reached
Peer set failed: Peer name too long Peer name has exceeded the maximum allowed number of
characters (32)
8.8 Router
The ETX-5 static router is a Layer-3 interworking device that forwards traffic
between its interfaces. The router is also used as a forwarding plane for UDP/IP
TDM pseudowires and 1580v2 entities, as well as acting as a forwarding plane for
IPv4 and IPv6 packets. Any flow related to IP forwarding, management traffic, or
timing must be via an SVI or PPP that is bound to a router interface.
Standards
RFC 4292
Benefits
The router is used for segmenting a LAN, increasing network performance, and
making packet forwarding more efficient.
Factory Defaults
By default, there is one router instance in the ETX-5 system.
8-92 Router ETX-5

The ETX-5 static router is an internal interworking device that forwards traffic
between its interfaces. ETX-5 supports a single router instance with up to 128
router interfaces (RIFs), up to 1K of routing table and up to 1000 ARP table
entries.
Each router interface can be assigned up to 10 IP addresses (IPv4 and IPv6) and
can be bound to one of the following:
• Bridge port
• Virtual loopback address on a router interface on a TDM pseudowire card for
UDP/IP forwarding or IEEE 1588v2 master or slave entity.
A router interface can be activated only if it has active ingress and egress flows
connected to it. Likewise, to delete or deactivate flows connected to a router SVI,
the RIF must be deactivated first.
ETX-5 supports IPv6 for device management.
Note 1588 UDP/IP and UDP/IP TDM PW are not supported for IPv6
Each RI supports dual stack forwarding, i.e concurrent IPv4 and IPv6 forwarding.
Each router interface can simultaneously support both IPv4 and IPv6 packets.
Each packet is forwarded per the Routing table according to packet type (IPv4 or
IPv6). Multiple IP addresses (IPv4, IPv6) are supported per Router interface.
Note The section of RFC-4213 related to “Configured tunneling of IPv6 over IPv4” is
not supported.
Router Scaling
ETX-5 supports:
• Up to 128 Router interfaces per shelf
• Up to 10 IP addresses per RI (IPV4 & IPv6)
• Up to 1k ARP table entries for IPv4
• Up to 1k IPv4 routing table entries
• Total of 512 entries are supported for:
 IPv6 router interfaces
 IPv6 routing
 IPv6 neighbors (IPv6 “ARP”)
• A single RIF on the same broadcast domain ( one RIF per SVI)
Connection to Physical and Bridge Ports

Figure 8-29 illustrates the connection of router interfaces (RIFs) to directly-
attached (NET, OOB) and indirectly-attached (User) ports. Connection is always
made by directing flows from a port to a Service Virtual Interface (SVI), and then
binding the SVI to a RIF.
ETX-5 Router 8-93

When adding Layer-3 services to Layer-2 topology, such as G.8032 Ethernet ring,
a router interface must be connected to a bridge port. Such connections are also
made via SVIs. Figure 8-29 illustrates a RIF-to-BP connection.
ETX-5
SVI LB IP
User RIF Router
NET
RIF
SVI
SVI
SVI
SVI BP SVI
User BP BP OOB
Bridge
User BP BP NET
SVI SVI
Figure 8-20. Router Connection to Physical and Bridge Ports
Management
ETX-5 can be managed via any router interface, if it is configured to accept
management traffic. RIF management modes are as follows:
• Disabled
• Enable
• Allow only ping
Port Loopback
See section 8.1
Loopback Router Interfaces

Any router interface can be declared a loopback type. ETX-5 supports up to six
virtual loopback addresses, which can connect to:
• TDM pseudowire card for UDP/IP-encapsulated PW traffic (up to four loopback
addresses)
• IEEE 1588v2 master and slave entities on main cards for Precision Timing
Protocol traffic (one or two loopback addresses, one per main card).
8-94 Router ETX-5

Notes To enable connection of UDP/IP PW and/or 1588v2 PTP traffic, the TDM
pseudowire cards and 1588v2 agents on the main cards must be allocated the
same IP addresses as the corresponding loopback RIFs. Loopback router
interfaces must be configured prior to using them for TDM PW or 1588v2 traffic.
Loopback interfaces are not bound to SVIs.
Routing and ARP Tables

The ETX-5 router provides a static routing table. The ARP table supports up to
1000 dynamic entries with a 20-minute refresh. The ARP table adds entries
according to:
• ARP replies received by the router
• ARP requests sent to the router.
Configuring the Router

Router configuration includes the following steps:
1. Adding a router instance
2. Add and configure router interfaces (1–128).
 To configure a router:
1. At the configure prompt, enter router followed by router number (1).
A router instance with number 1 is created and the config>router(1)#
2. Configure the router as illustrated and explained below.
Assigning a name to router name <value> no name deletes router name

no name
Clearing dynamic entries from clear-arp-table

ARP table
Configuring router interfaces, interface <1–128> no interface (port_number),

see below no interface <1–128> deletes router interface
Configuring the static route and static-route The next hop must be a subnet
the next gateway (next hop) <IP-address/IP-mask-of-static-route> of one of the router interfaces
using the next hop’s IP address address <IP-address-of-next-hop>
[metric <metric>]
Displaying the address show arp-table

resolution protocol (ARP) table,
which lists the original MAC
addresses and the associated
(resolved) IP addresses
Displaying the router interface show interface-table

table
ETX-5 Router 8-95

Displaying the routing table show routing-table
The following marking actions can be performed at the interface level, at the
config>router(1)>interface(interface_number)# prompt.
Defining router interface to be loopback

of the loopback type
Assigning an IP address and a address <IP-address/IP-mask>

subnet mask to the router
interface
Binding router interface to an bind svi <port-number> no bind removes RIF link to SVI
SVI or out-of-band management bind mng-ethernet <slot/port> or management Ethernet port
Ethernet port
no bind
Configuring interface management-access {allow-all | no management-access

management access allow-ping} disables management via RIF
no management-access
Assigning a name to the router name <interface-name>

interface
Administratively enabling router no shutdown shutdown disables the

interface interface
Displaying interface status show status
Displaying ARP Table

You can display the Address Resolution Protocol table with original MAC
addresses and resolved IP addresses.
 To display ARP table:

• At the config>router(1)# prompt, enter show arp-table.
The ARP table is displayed.
ETX-5>config>router(1)# show arp-table
IP Address MAC Address Status
---------------------------------------------------------------
15.15.15.55 00-20-D2-55-44-33 Dynamic
Displaying Routing Table

The routing table stores the routes to network destinations, including destination
IP address/mask, next hop IP address, outgoing port, protocol and metric (route
cost).
 To display the routing table:

• At the config>router(1)# prompt, enter show routing-table.
8-96 Router ETX-5

The routing table is displayed.

ETX-5>config>router(1)# show routing-table
IP Address/Mask Next Hop Port Protocol Metric
---------------------------------------------------------------
15.15.15.124/24 0.0.0.0 svi 1 Local 1
Displaying Interface Table

You can display a list of configured router interfaces, including their IP
addresses/masks, bound interfaces and statuses.
 To display interface table:

• At the config>router(1)# prompt, enter show interface-table.
The interface table is displayed.
ETX-5>config>router(1)# show interface-table
Interface Name IP Address/Mask

Admin Bound to Port
Status Port Status
---------------------------------------------------------------
1 15.15.15.124/24 Up svi 1 Up
Displaying Router Interface Status

You can display information on IP addresses router interface and DHCP server (if
DHCP client for this RIF is enabled).
 To display router interface status:

• In the config>router(1)>interface(interface_number)# prompt, enter show
status.
The interface status information is displayed.
ETX-5>config>router(1)>interface(1)# show status
IP Address : 15.15.15.124/24
Default Router : --
Example
Figure 8-30 and script below illustrate configuration of router with one router
interface connected to a bridge port.
ETX-5 Router 8-97

SVI
6
Port 1 Fl. 9 Port 1
SVI Fl. 11
BP 2
Fl. 10 7
BP 3 Fl. 12
SVI Bridge
5
Port 2 Port 2
BP 1
Fl. 1
Fl. 7
SVI SVI Fl. 8

Port 3 Port 3
Fl. 2 1 4
Fl. 5
RIF 1 RIF 4
Fl. 3
SVI Router SVI Fl. 6
2 3
Port 4 Port 4
Fl. 4
RIF 2 RIF 3
Main Ethernet Main Ethernet

Card A Card B
Figure 8-21. Router-over-Bridge Service
 To configure router interfaces and bridge ports:

2. Assign previously configured queue group profiles to main card ports.
Note Queue group configuration is omitted in this example.
3. Configure seven SVIs (four router-type and three bridge-type).

4. Add bridge 1 with three tagged bridge ports (VLAN 20) and bind them to
bridge-type SVIs.
5. Configure four classifier profiles:
 One profile (untagged) for traffic from main card A to router
 One profile (match all) for traffic:
 From router to main card A
 From router to main card B
 From router to bridge
 One profile (VLAN 600) for traffic from main card B to router
 One profile (VLAN 20) for traffic:
 From bridge to router
 From bridge to main card A
 From bridge to main card B
 From main card B to bridge.
6. Use default CoS mapping and color mapping profiles (color –green, CoS – CoS
0).
8-98 Router ETX-5

7. Configure color-aware marking profile for flows connecting BP 1 with main

card A.
8. Add four router interfaces, configure their IP addresses and bind them to
router-type SVIs; add static route.
9. Configure twelve flows:
 Flow 1 from main card A port 2 to SVI 1, untagged classifier
 Flow 2 from SVI 1 to main card A port 2, match all classifier
 Flow 3 from main card A port 3 to SVI 2, untagged classifier
 Flow 4 from SVI 2 to main card A port 3, match all classifier
 Flow 5 from main card B port 2 to SVI 3, VLAN 600 classifier, pop VLAN
 Flow 6 from SVI 3 to main card B port 2, match all classifier, push VLAN
600 with VID P-bit and DEI values set by marking profile
 Flow 7 from SVI 4 to SVI 5, match all classifier, push VLAN 20 with VID
P-bit and DEI values set by marking profile
 Flow 8 from SVI 5 to SVI 4, VLAN 20 classifier, pop VLAN
 Flow 9 from SVI 6 to main card A port 1, VLAN 20 classifier
 Flow 10 from main card A port 1 to SVI 6, VLAN 20 classifier
 Flow 11 from SVI 7 to main card B port 1, VLAN 20 classifier
 Flow 12 from main card B port 1 to SVI 7, VLAN 20 classifier.
#**********************Enabling_Ports_on_Main_Cards*************************
config port
ethernet main-a/1
no shutdown
exit
ethernet main-a/2
no shutdown
exit
ethernet main-a/3
no shutdown
exit
ethernet main-b/1
no shutdown
exit
ethernet main-b/2
no shutdown
exit
exit all
#*********************************End****************************************
#*********************Assigning_Queue_Group_Profiles*************************
exit all
#*********************************End****************************************
ETX-5 Router 8-99

exit all

exit all

exit all

exit all

exit all

exit all

exit all
#*********************************End****************************************
#************************Configuring_Bridge_Ports****************************
bind svi 5
no shutdown
exit all

bind svi 6
no shutdown
exit all

bind svi 7
no shutdown
exit all
config bridge 1
vlan 20
tagged-egress 1..3
exit all
#*********************************End****************************************
#***********************Configuring_Classifier_Profiles**********************
match all
exit all

match untagged
exit all
8-100 Router ETX-5


match vlan 600
exit all

match vlan 20
exit all
#*********************************End****************************************
#***********************Configuring_Marking_Profile**************************
config qos
marking-profile mark1 classification cos color-aware green-yellow dei mapping
exit all
#*********************************End****************************************
#*******************Configuring_Router_Interfaces****************************
address 10.10.52.1/24
bind svi 1
no shutdown
exit all

address 10.10.53.1/24
bind svi 2
no shutdown
exit all

address 10.10.62.1/24
bind svi 3
no shutdown
exit all

address 172.18.219.180/24
bind svi 4
no shutdown
exit all
configure router 1
exit all
#*********************************End****************************************
detected.
ETX-5 Router 8-101

Message Description
The interface table is not empty Router cannot be deleted if at least one RIF exists in the system
The ARP table is not empty Router cannot be deleted if its ARP table is not empty
Cannot add router, maximum number of The maximum number of routers (1) has been reached
routers is reached
Cannot clear ARP table ARP table clear failure
Wrong value for set Invalid parameter value (e.g., invalid IP address, invalid IP
address type)
Wrong length for string The maximum number of characters in router name has been
exceeded
The static route table is not empty Cannot shut down or delete a RIF if it is still in use by a static
route
Cannot set value when interface is active Cannot change a RIF parameter (IP address/mask, DHCP,
management access, VLAN etc) when a RIF is active
Cannot add interface, maximum number Cannot add a new RIF if the maximum number of RIFs has been
has been reached reached or the RIF IP address/mask overlaps the subnet of an
existing RIF
The interface must have an IP mask RIF IP mask has not been configured
assigned to it
Wrong IP address for interface, in the Invalid RIF IP address is for the current subnet (first/last address
current subnet of the subnet or 0.0.0.0)
This address already exists in a static A static route with the same destination IP address and the
route entry same cost (metric) has already been added
This interface already created with Cannot change RIF type when RIF is active
different loopback argument
The interface must have an IP address Cannot activate a RIF with no IP address assigned to it
assigned to it
The interface must be bound first Cannot activate a RIF which has not yet been bound to a port
The values for the IP address and the Destination IP address and IP mask of a static route do not
mask must be consistent match
Wrong value for priority The metric value (cost) of a static route is out of range (1–255)
The address must be an IP address in the The next hop of a static route is not in the subnet of any
local network existing RIF
The interface number is not a router Destination RIF defined for a static route does not exist
interface of this router
The interface must be bound to a P2P Destination RIF defined for a static route must be bound to a
port P2P port
Cannot add static route, maximum The maximum number of static routes has been reached
number has been reached
8-102 Router ETX-5

Message Description
The address must be different from a The next hop IP address of a static route must be different from
router interface IP address a RIF IP address
8.9 TDM Pseudowires

TDM pseudowires (PWs) are an emulation of Layer-2 point-to-point connection-
oriented services over packet-switching networks (PSN).
Standards
• Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service
over Packet Switched Network (CESoPSN), RFC 5086
• Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP), RFC
4553
• MEF 8, Implementation Agreement for the Emulation of PDH Circuits over
Metro Ethernet Networks, October 2004
• ITU-T Recommendation Y.1453 (03/2006), TDM-IP interworking – User plane
interworking
• Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit
Connectivity Verification (VCCV), draft-ietf-pwe3-vccv-bfd-05
• Pseudo Wire (PW) OAM Message Mapping, draft-ietf-pwe3-oam-msg-map-10
• Definitions of Textual Conventions for Pseudowire (PW) Management, RFC
5542
• Pseudowire (PW) Management Information Base (MIB), draft-ietf-pwe3-pw-
mib-14
• Managed Objects for TDM over Packet Switched Network (PSN), draft ietf
pwe3 tdm mib 11
• ITU-T Recommendation G.823 (03/2000), The control of jitter and wander
within digital networks which are based on the 2048 kbps hierarchy
• ITU-T Recommendation G.824 (03/2000), The control of jitter and wander
within digital networks which are based on the 1544 kbps hierarchy.
Factory Defaults
By default, there are no pseudowire connections in the ETX-5 system.
Benefits
Pseudowire circuit emulation technology enables packet-based infrastructure to
provide TDM services with the service quality of an SDH/SONET network.
ETX-5 TDM Pseudowires 8-103

The pseudowire services convert TDM payload to packets and transfer these
packets through Layer-2 (E-Line, E-LAN) or Layer-3 (router) services.
The pseudowire subsystem is located on the E5-cTDM-4 card (four channelized
STM-1/OC-3 ports with 63 E1 or 84 T1 channels per port) or the E5-cTDM-1 card
(one channelized STM-4/OC-12 port with 252 E1 or 336 T1 channels). The traffic
to the internal E1/T1 ports is directed by means of a pseudowire cross-connect
matrix (a timeslot cross-connect matrix similar to the TDM cross-connect matrix),
which routes traffic from the internal ports to the pseudowire packet processors
with total capacity of up to 336 pseudowires per card and 1344 per chassis.
Note For additional information on the ETX-5 pseudowire system, see also Link Layer
Discovery Protocol (LLDP) and Cross-Connection.
Each pseudowire terminated on the E5-cTDM-4 can be independently configured

to handle the particular type of traffic:
• Transparent transfer of data (unframed E1/T1 streams) using SAToP.
• Transfer of framed E1/T1 streams, using CESoPSN.
To support voice payload, the signaling information can also be transported.
Note that when using CESoPSN, any timeslots carrying signaling information
(either channel-associated signaling (CAS), or common-channel signaling
(CCS) such as Signaling Scheme 7 (SS7), ISDN PRI signaling, etc.) can be
transparently transferred within the pseudowire, as regular data timeslots.
Packet structure is independently selectable for each pseudowire, for
compatibility with the various pseudowire protocols (CESoPSN, SAToP). The PSN
type (UDP/IP or ETH) is selected per E5-cTDM-4 card. For maximum flexibility in
system applications, the framing format of the pseudowire device at the
destination (referred to as a pseudowire peer) can also be taken into account.
Therefore, in CESoPSN, for example, traffic using the E1 standards can be
directed at destinations using the T1 standards, and vice versa.
Pseudowire Packet Processing Subsystem

The packet processors in the E5-cTDM-4 packet processing subsystem perform
the functions necessary for converting TDM traffic directed to the E5-cTDM-4
internal DS1 ports into packetized traffic for transmission over pseudowires.
The basic format of a TDM-PW packet is illustrated below:
Ethernet Header
PSN and Multiplexing Layer Headers
Control Word
Packetized TDM Data (Payload)
Ethernet Header
The Ethernet header contains the DA, SA and Ethernet type information. It may
also contain an optional VLAN tag.
8-104 TDM Pseudowires ETX-5

UDP over IP
For UDP/IP-type PSN, the Ethernet header is as follows:
• SA MAC – MAC address of the router interface used for packet forwarding
• DA MAC – MAC address of the resolved next hop, default gateway or host
• VLAN –VLAN assigned to the router interface used for packet forwarding
• P-bit – CoS of PW is set to 1. P-bit is a RIF attribute (CoS > P-bit).
MEF-8
For the MEF-type PSN, the Ethernet header is as follows:
• SA MAC – MAC address of the E5-cTDM-4 card
• DA MAC – MAC address of the peer
• VLAN – Flow (E-Line/E-LAN) VLAN
• P-bit – CoS of PW is set to 1. P-bit is a flow attribute (marking profile, CoS >
P-bit)
• Packet color – green.
PSN and Multiplexing Layer Headers

Each pseudowire has a header whose structure depends on the selected PSN
type, and includes labels that uniquely specify the pseudowire source and
destination. ETX-5 supports the following PSN types:
• UDP over IP
• MEF-8 (CESoETH).
UDP over IP
For UDP/IP-type PSN, the TDM-PW packet structure is as follows:
6 6 2 2 2 20 8 4
Type VLAN Type UDP
DA SA IP Header CW TDM Payload
8100 Tag 800 Header
Where:
• DA – MAC address of the next hop (taken from the forwarding table)
• SA – MAC address of the applicable router interface
• VLAN type 0x8100 + VLAN tag, optional
• Type – 0x800 (IP packet)
• IPv4 Header – the protocol field of the IP header is set to 17 (UDP)
• UDP Header – the PW label/s, manually configured (see below)
For UDP/IP-type PSN IP, the TOS byte in the IP header can be configured per PW.
The UDP header is used to multiplex between the different PWs. UDP port values
are as follows:
• UDP Source Port – source PW label (1 to 8191) + 49152

• UDP Destination Port – destination PW label (1 to 8191) + 49152

• Classification (Rx side) – configured destination port together with both the
source and destination IP addresses uniquely identifies the PW for the
receiver (a match is checked between the destination port within the Rx
packet and the pre-configured source PW label)
Note The constant value of 49152 is added to the PW labels configured by the
operator. It is inserted in the outgoing packet at the UDP ports fields. For
example, a PW label ‘1’ is transmitted as port ‘49153’.
MEF-8 (CESoETH)
For MEF-8-type PSN, the TDM-PW packet structure is as follows:
6 6 2 2 2 4 4
Type VLAN Type
DA SA ECID CW TDM Payload
8100 Tag 88D8
Where:
• DA – MAC address of the peer device
• SA – MAC address of the associated SVI (per E5-cTDM-4 card)
• VLAN type 0x8100 + VLAN tag, optional
• Type – 0x88D8 (CESoETH packet)
• ECID – Emulated Circuit Identifier, a manually configured unique label which
identifies the PW.
Control Word
The control word structure for different encapsulation methods is illustrated
below.
CESoPSN:
0 1 2 3 4 5 6 7 8 9 10 15 16 31
0 0 0 0 L R M FRG LEN (6) Sequence Number (16)
SAToP:
0 1 2 3 4 5 6 7 8 9 10 15 16 31
0 0 0 0 L R RSV FRG LEN (6) Sequence Number (16)
Bits 0-3 – Set to zero.

L – local attachment circuit abnormal condition. If set, indicates that the source
has detected or has been notified of a TDM fault condition that is affecting the
data to be transmitted. If the TDM fault is cleared, the L bit is also cleared.
R – remote loss of frame. If set, indicates that packet loss or buffer underflow
condition is detected at the PSN.
M/RSV – a 2-bit modifier field in CESoPSN. If L=0, it allows detection of signaling
packets, carrying RDI across the PSN. If L=1, only value ‘00’ for M bits is currently
defined. In SAToP it is reserved and must be set to 0.

L & M can be treated as a 3-bit code point that is described in the table below.
Table 8-43. L & M Code Point Interpretations
L M Code Point Interpretation
0 00 Normal situation, no failure
0 01 Reserved
0 10 RDI condition of the attachment circuit (TDM link). The payload is

received, and upon configuration RDI can be generated on the
outgoing TDM trunk.
0 11 Reserved for CESoPSN signaling packets.
1 00 TDM data is invalid. The payload is replaced by an “Idle” bit

pattern towards the TDM trunk. Additionally, it can be pro
configured to generate an AIS pattern or “Channel Idle” signal
towards the local CE on the TDM trunk.
1 01 Reserved
1 10 Reserved
1 11 Reserved
FRG – fragmentation field. This field is used for fragmenting multiframe

structures into multiple packets in case of structured CESoPSN with CAS bundles.
Must be set to zero.
LEN – the length of the TDM-PW packet (header + payload) if it is less than 64
bytes. Otherwise, it is set to zero.
Sequence Number – provides the common PW sequencing function as well as
detection of lost packets. Its generation rules:
• Its space is a 16-bit unsigned circular number
• Its initial value is random (unpredictable)
• It is incremented with each TDM-PW data packet sent in the specific PW.
TDM Payload
This section details the two payload encapsulation methods supported by ETX-5.
CESoPSN
CESoPSN transports raw TDM data; that is, packets are formed by inserting a
user-specified number of complete TDM frames (4 to 360 frames) in the packet
payload area. Therefore, CESoPSN pseudowires can only be configured on framed
ports.
The TDM frames are considered serial data, even if they carry voice and CAS.
Since a CESoPSN pseudowire transports raw TDM frames, a CESoPSN pseudowire
can only be directed to another framed port.
The amount of TDM data in the CESoPSN packet is an integer multiple of the
basic structure size (the basic structure consists of N octets filled with the data
of the corresponding N×DS0 channels belonging to same PW):

N – number of timeslots (DS0 channels) in the PW

L – packet payload size in bytes
L = m×N
The resulting payload format is illustrated below.
0 1 2 3 4 5 6 7
Timeslot 1
Timeslot 2
Frame 1
…
Timeslot N
Timeslot 1
Timeslot 2
Frame 2
…
Timeslot N
Timeslot 1
Timeslot 2
Frame 3
…
Timeslot N
…
Timeslot 1
Timeslot 2
Frame m
…
Timeslot N
The first structure in the packet starts immediately at the beginning of the packet
payload.
The timeslots to be placed into the payload do not need to be contiguous, and
the payload can contain any combination of timeslots from the TDM circuit. The
timeslots are placed into the payload in the same order that they occur in the
TDM circuit.
Maximum payload size for a CESopSN PW is up to 512 bytes. It is calculated as
N × number of timeslots in the PW,
Where N = 8, 16, 24, 32, 40, 48, 56, 64.
SAToP
SAToP is used to transfer a bit stream transparently at the nominal port rate
(2.048 Mbps or 1.544 Mbps). Therefore, SAToP can be used only when the port
uses the unframed mode, and thus only one pseudowire can be configured per
port.
The SAToP packet payload consists of a user-specified number of raw TDM bytes
(4 to 1440 bytes), and is treated as data payload.

Note The SAToPSN packet overhead is large, and therefore, for efficient bandwidth
utilization, the number of raw TDM bytes per packet should be as large as
possible.
The receiving end restores the original bit stream. Therefore, a SAToP pseudowire
can only be directed to another unframed TDM port.
Maximum payload size for a SAToP PW is as follows:
• E1 – N × 32
Where N = 1–8, 16, 24, 32 (payload size is an multiple integer of 32 bytes)
• T1 – N × 24
Where N = 1–8, 16, 24, 32 (payload size is an multiple integer of 24 bytes)
All SAToP implementations support the following payload sizes (other sizes are
optional):
• E1 - 256 bytes
• T1 - 192 bytes.
Selection Guidelines for TDM Payload Bytes per Frame

The pseudowire technology enables transmitting the continuous data stream
generated by TDM equipment as a stream of discrete packets, having a structure
suitable for transmission over packet-switched networks. This process is called
packetizing.
The number of TDM bytes inserted in each packet affects two important
performance parameters:
• Bandwidth utilization efficiency. The smaller the number of TDM bytes per
packet, the lower the efficiency. The overhead can be a significant fraction of
the total packet when the TDM payload parameter is small.
• Packetizing delay and the associated delay variance. Considering that any
given TDM byte is received only once per TDM frame, the rate at which TDM
bytes are received for filling packets is 8000 bytes per timeslot per second.
Since a packet will be sent only after its payload field has been filled, the
maximum possible filling rate occurs for PWs carrying 32 timeslots (unframed
mode) and a payload of 32 bytes per frame (E1). In this case, the filling of
the 32 bytes takes 1 internal TDM frame (125 ps).
However, the filling time increases significantly for PWs with few timeslots;
for example, a voice channel can be carried by a single-timeslot PW.
Considering the nominal filling rate (approximately one byte every
0.125 msec), the filling time can easily become very significant. As a
worst-case example, consider the time needed to fill a single-timeslot PW:
 At 32 TDM bytes per frame: approx. 4 msec
 At 768 TDM bytes per frame: approx. 96 msec.
The round-trip (or echo) delay for voice channels is at least twice the
packetizing delay; any other delays encountered along the end-to-end
transmission path only add to this minimum. Another problem introduced by
packetizing is intrinsic jitter. Because the instant when a packet is filled up is
usually not synchronized with its transmission to network, and occurs after
an essentially random delay, some jitter is inherently introduced.

Jitter Buffer
The packets of each pseudowire are transmitted by E5-cTDM-4 at essentially
fixed intervals towards 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, E5-cTDM-4
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:
• Since 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, E5-cTDM-4 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, E5-cTDM-4 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 16 ms.
• The read-out rate must be equal to the average rate at which frames are
received from the network. For this purpose, the read-out rate must be

continuously adapted to the packet rate, a function performed by the

adaptive clock recovery mechanism of each packet processor.
Packet Loss
In order to handle packet loss and misordering, E5-cTDM-4 has a packet
sequence integrity mechanism. It uses a sequence number in the control word (or
in the RTP header, if used) to detect lost and misordered packets. This
mechanism tracks the serial numbers of arriving packets and takes appropriate
action when anomalies are detected. When lost packets are detected, the
mechanism outputs filler data in order to retain TDM timing.
Packets arriving in incorrect order are reordered. Misordered packets that cannot
be reordered are discarded and treated as lost.
ToS
The ToS specifies the Layer 3 priority assigned to the traffic generated by this
pseudowire.
For IP networks, this priority is indicated by the IP type-of-service parameter for
this pseudowire. The specified value is inserted in the IP TOS field of the
pseudowire IP packets.
When supported by an IP network, the type-of-service parameter is interpreted,
in accordance with RFC 791 or RFC 2474, as a set of qualitative parameters for
the precedence, delay, throughput and delivery reliability to be provided to the IP
traffic generated by this pseudowire.
Each network that transfers the pseudowire IP traffic can use these qualitative
parameters to select specific values for the actual service parameters of the
network, to achieve the desired quality of service.
OAM Protocol
The OAM protocol, supported only by packet payload version V2, is used by
pseudowire emulation modules to check for a valid bundle connection: this
includes checks for compatible configuration parameters at the packet processors
at the two endpoints of a bundle, and detection of inactive bundle status.
The bundle state information is collected by the continuous, periodic handshake
between the two endpoints of a bundle, which generates little traffic, but ensures
that each endpoint recognizes the connection, and that it is enabled. If no response
is received by OAM packets within a predefined interval (a few tens of seconds), the
bundle is declared inactive.
When the use of the OAM protocol is enabled, little traffic flows until the connection
between the two bundle endpoints is established: only after the connection is
confirmed by the OAM exchange is transmission at the normal (full) rate started,
and the bundle starts carrying traffic. In case the connection is lost, the transmitted
traffic is again significantly decreased (several packets per second per connection).
The OAM connectivity check also prevents network flooding if the connection is
lost.
OAM packets are identified, using the following methods:

• UDP/IP – In accordance with source port: in this case the OAM packets run
over a UDP port number that is assigned only for OAM traffic, but use the
same VLAN ID and ToS of the originating connection.
• MEF-8 – In accordance with the contents of the control word, which is
included in version V2 packets (Virtual Circuit Connection Verification – VCCV).
The first four bits of an OAM control word are always set to 0001.
Alarm Indications and Fault Propagation

For TDM ports, the applicable standards specify the methods used to report loss
of signal, loss of frame alignment, AIS reception, reception of a remote defect
indication (RDI) from the equipment connected to the TDM port, etc.
TDM emulation requires transfer of defect conditions end-to-end. This
mechanism is referred to as TDM-PSN fault propagation. The following condition
must be propagated:
• TDM link failure
• PSN failure
• TDM RDI
ETX-5 uses set of flags in TDM PW control word (CW) to indicate defect
conditions:
• L-bit – TDM forward defect indication used by the local PW device to signal
TDM link defects to the remove PW device
• M-bit – Modification indication, used to change meaning of the received
defects
• R-bit – PW reverse defect indication used by the local PW device to signal PSN
failures to the remote PW device.
The following sections detail the ETX-5 fault propagation techniques.
Structure-Agnostic Mode
In the structure-agnostic mode TDM defect indications are carried within the
TDM frame and passed transparently via the pseudowire connection. PSN defects
are mapped to TDM defects (TDM AIS).
Figure 8-9 illustrates fault propagation in structure-agnostic mode when LOS or
AIS is detected on the TDM link. In this case, remote ETX-5 ignores or propagates
the AIS condition, according to the user configuration. If the AIS is generated, the
ETX-5 sets the CW bits as follows: L-bit – 1, M-bit – 00. When ETX-5 detects the
CW bit settings, it generates the AIS towards the local TDM device.
L-bit = 1
M-bit = 00
LOS, AIS
AIS PSN AIS
TDM TDM
Device ETX-5 ETX-5 Device
Figure 8-22. Structure-Agnostic Mode, TDM Failure

Figure 8-10 illustrates fault propagation in structure-agnostic mode, when

persistent packet loss or jitter buffer underflow conditions are detected. In this
case, AIS is generated towards the local TDM device. ETX-5 sets the CW R-bit to 1
in the packets transmitted towards the PSN.
R-bit = 1
Packet
Loss
PSN AIS
TDM TDM
ETX-5 ETX-5
Device Device
Figure 8-23. Structure-Agnostic Mode, PSN Failure
Figure 8-11 illustrates fault propagation in structure-agnostic mode, when RDI

signal is received on the TDM interface. The RDI is carried transparently over PSN
without any modification.
PSN
RDI
TDM TDM
Figure 8-24. Structure-Agnostic Mode, TDM RDI
Structure-Aware Trail-Terminated Mode

In structure-aware trail-terminated mode, TDM PW defects are translated into
TDM conditions on a specific bundle in a remote TDM link. PSN defects are also
mapped to TDM conditions a specific bundle in a remote TDM link.
Figure 8-12 illustrates fault propagation in structure-aware trail-terminated
mode, when LOS/OOF is detected on the local TDM interface or AIS is present on
a local TDM pseudowire. In this case, ETX-5 ignores or propagates the AIS
condition, according to the user configuration. If the AIS is generated, ETX-5 sets
the CW bits as follows: L-bit – 1, M-bit – 00. If the LOS or OOF conditions are
detected, ETX-5 sends the RDI towards the local TDM device.
ETX-5 detects the CW bit settings and generates the OOS code for all DS0
channels belonging to a specific pseudowire in the local TDM circuit.
L-bit = 1
M-bit = 00
LOS, AIS, OOF

AIS OOS Code
PSN
RDI
TDM TDM
Figure 8-25. Structure-Aware Trail-Terminated Mode, TDM Failure

mode, when persistent packet loss or jitter buffer underflow conditions are
detected. ETX-5 detects the fault condition and generates the OOS code for all
DS0 channels belonging to a specific pseudowire in the local TDM circuit. In
addition, it sets the CW R-bit to 1 in all packets transmitted towards the PSN.

R-bit = 1
Packet
Loss
PSN OOS Code
TDM TDM
Figure 8-26. Structure-Aware Trail-Terminated Mode, PSN Failure

mode, when RDI signal is received on the TDM interface. ETX-5 sets the CW bits
as follows: L-bit – 0, M-bit – 10, in all packets transmitted towards the PSN.
L-bit = 0
M-bit = 10
PSN
RDI
TDM TDM
ETX-5 ETX-5
Device Device
Figure 8-27. Structure-Aware Trail-Terminated Mode, TDM RDI
Structure-Aware Trail-Extended Mode

In structure-aware trail-extended mode, TDM PW defects are regenerated on the
remote TDM interface in the fashion similar to the structure-agnostic mode. PSN
defects are mapped to TDM defects (AIS/RDI) on the whole TDM interface.
This fault propagation mode is suitable when only a single PW is connected to the
TDM interface, because failure propagates on the whole TDM link.
Figure 8-15 illustrates fault propagation in structure-aware trail-extended mode,
when LOS, OOF or AIS is detected on the local TDM interface. In this case, ETX-5
ignores or propagates the AIS condition, according to the user configuration. If
the AIS is generated, ETX-5 sets the CW bits as follows: L-bit – 1, M-bit – 00. If
the LOS or OOF conditions are detected, ETX-5 sends the RDI towards the local
TDM device.
ETX-5 detects the bit settings and generates the AIS towards the local TDM
device.
L-bit = 1
M-bit = 00
LOS, OOF, AIS

AIS AIS
PSN
RDI
TDM TDM
Figure 8-28. Structure-Aware Trail-Extended Mode, TDM Failure

when persistent packet loss or jitter buffer underflow conditions are detected. In
this case, AIS is generated towards the local TDM device. In addition, ETX-5 sets
the CW R-bit to 1 in all packets transmitted towards the PSN. When ETX-5 detects
the CW bit settings, it generates the RDI towards the local TDM device.

R-bit = 1
Packet
Loss
AIS
PSN
RDI
TDM ETX-5 ETX-5 TDM

Device Device
Figure 8-29. Structure-Aware Trail-Extended Mode, PSN Failure

when RDI signal is received on the TDM interface. ETX-5 sets the CW bits as
follows: L-bit – 0, M-bit – 10, in all packets transmitted towards the PSN. When
ETX-5 detects the CW bit settings, it generates the RDI towards the local TDM
device.
L-bit = 0
M-bit = 10
PSN
RDI RDI
TDM TDM
Figure 8-30. Structure-Aware Trail-Extended Mode, TDM RDI
Adaptive Timing
For each pseudowire, the E5-cTDM-4 cards have independent adaptive clock
recovery mechanisms, which recover the original timing (clock rate) of the far-
end source of each pseudowire. The clock recovery mechanisms can provide
recovered clock signals to serve as timing references for the ETX-5 nodal timing
subsystem.
The receive path of each pseudowire must use a clock recovery mechanism to
recover a clock signal at the original payload transmit rate used at the far end.
This mechanism is referred to as adaptive clock recovery mechanism.
Each pseudowire has its own adaptive timing recovery mechanism, in accordance
with the options listed in RFC 4197. The recovered pseudowire clocks can be
used as timing reference signals for the nodal ETX-5 timing subsystem; therefore,
E5-cTDM-4 allows flexible timing distribution.
The adaptive clock recovery mechanism estimates the average rate of the
payload data received in the frames arriving from the packet-switched network.
Assuming that the packet-switched network does not lose data, the average rate
at which payload arrives will be equal to the rate at which payload is transmitted
by the source.
Note
Generally, lost packets, as well as packets that did not arrive in the correct order,
are replaced by special dummy packets. However, for CESoPSN and SAToPSN,
packets can be reordered.
The method used to recover the payload clock of a pseudowire is based on

monitoring the fill level of the selected pseudowire jitter buffer. The clock
recovery mechanism monitors the buffer fill level, and generates a read-out clock
signal with adjustable frequency. The frequency of this clock signal is adjusted to
read frames out of the buffer at a rate that keeps the jitter buffer as near as

possible to the half-full mark. This condition can be maintained only when the
rate at which frames are loaded into the buffer is equal to the rate at which
frames are removed. Therefore, the adaptive clock recovery mechanism actually
recovers the original payload transmit clock.
The performance of the clock recovery mechanism can be optimized for the
operating environment, by specifying the following parameters:
• The accuracy of the original timing source, in accordance with the standard
SDH/SONET terminology.
• The type of PSN that transports the traffic: router-based network (for
example, UDP/IP) versus switch-based network (for example, Ethernet).
• Handling of transient conditions: even after the adaptive clock recovery
mechanism reaches a stable state, temporary changes in the network delay
may still occur, and be on a timescale that does not allow for the mechanism
to fully readjust. To provide the best possible user experience, delay
sensitivity is disabled to optimize performance for accurate clock recovery.
Configuring Pseudowires
A new pseudowire bundle is added by defining its number (1–1344), its type
(connection mode) and a type of the PSN.
 To define and configure a pseudowire:

1. If you intend to use UDP/IP PSN type, verify that:
 Loopback router interface with valid IP address has been configured (see
Router).
 The TDM I/O card has been bound to the loopback router interface, using
card-type > bind loopback-address commands in the slot(1–4)# prompt.
2. At the config>pwe# prompt, enter the syntax illustrated in the table below.
The config>pwe>pw(<pw-number>)# prompt appears.
Note An internal E1 or T1 port becomes active only if at least one enabled pseudowire
with a valid cross-connection is assigned to the port.
Note In order to change the SVI number of an active TDM PW, you must first remove
the cross connect and only then change the SVI number.

Assigning the pw <pw-number> [type PW number: 1..1344

pseudowire number, {ces-psn-data | e1satop | PW type (must be configured for the first time):
selecting the t1satop ]
• e1satop: SAToP, for carrying unframed E1 data
encapsulation [psn {udp-over-ip |
streams, depends on selected card type
protocol for the ethernet}]
selected pseudowire • t1satop: SAToP, for carrying unframed T1 data
and specifying the streams, depends on selected card type
PSN type (selecting • ces-psn-data: CESoPSN protocol, for carrying
the type of PSN framed data streams
header) psn (must be configured for the first time):
• udp-over-ip – UDP over IP network
encapsulation
• ethernet – MEF-8 Ethernet network
encapsulation
Using no before pw <number> deletes the
pseudowire.
10. At the config>pwe>pw(<pw-number>)# prompt, enter the parameters

specified in the table below.
Assigning a name to the name <up to 32 Using no before name deletes the pseudowire name
pseudowire characters>
Specifying the PW label used label [in <number>] Out PW label:

in the inbound and [out < number>] • For udp-over-ip: Specifies the UDP destination
outbound directions port number used by the pseudowire for Tx PW
packets (source port for Rx PW packets)
• For ethernet: Specifies the Emulated Circuit ID
(ECID) for Tx PW packets
In PW label:
• For udp-over-ip: Specifies the UDP source port
number used by the pseudowire for the Tx PW
packets (destination port for Rx PW packets)
• For ethernet: Specifies the expected Emulated
Circuit ID (ECID) Rx PW packets
The allowed range is 1–8191.
Defining the jitter buffer jitter-buffer <value in Use the shortest feasible buffer, to minimize
size µsec> connection latency.
The allowed range is 1000–16000 µsec, in 1-µsec
steps.

Enabling/disabling the OAM oam The selection must be compatible with the
connectivity protocol for this equipment at the far end of the connection
PW The pseudowire OAM messaging system is also used
for transferring inband loopback activation codes for
T1 interfaces.
no oam disables the OAM protocol.
Defining a remote peer peer <peer number> Range: from 1 to 1334.

terminating this PW no peer removes the remote peer
Configuring TDM payload tdm-payload <value in A larger value increases the bandwidth utilization
size bytes> efficiency, but also increases the connection intrinsic
latency, in particular when the bundle is configured
to carry a small number of timeslots.
The values are:
• E1 SAToP – n×32, n = 1–8, 16, 24, 32 (32, 64,
96, 128, 160, 192, 256, 512, 768, 1024)
• T1 SAToP – n×24, n = 1–8, 16, 24, 32 (24, 48,
72, 96, 120, 144, 168, 192, 384, 576, 768)
• CESoPSN – Number of timeslots × 8, 16, 24, 32,
40, 48, 56, 64 (up to 512 bytes)
Specifying the value for the tos <tos number> Range: from 1 to 255.
TOS byte used on outbound In accordance with RFC 2474, it is recommended to
traffic use only values which are multiples of 4.
This parameter is relevant only when psn is
udp-over-ip.
Selecting the response to psn-oos {1-bit | stop- 1-bit – Packets filled with all ones (AIS) are sent over
out-of-service conditions tx} PSN. In this case L-bit is also set in PW packet
detected at the local TDM control word.
port stop-tx – no packets are sent over PSN
Assigning egress port for L2 egress-port svi This parameter is relevant only when psn is ethernet
forwarding <svi_number>
Enabling statistic data pm-enable no pm-enable disables statistic data collection

collection no pm-enable
Enabling the pseudowire no shutdown shutdown disables the pseudowire.

Note: An internal E1/T1 port becomes active only if
an enabled pseudowire with a valid cross-connection
is assigned to the port.

Displaying PW Statistics
ETX-5 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 parameters listed below.
Displaying show statistics { current | interval | all- • current – Displays the current statistic
statistics intervals | all } counters
• interval – Displays statistics for selected
interval
• all-intervals – Displays statistics for all
intervals since the PW statistics
collection has been enabled
• all – Displays current statistics and
statistics for all intervals
ETX-5>config>pwe>pw(1)# show statistics current
Current
---------------------------------------------------------------
Rx Packets : 354994
Tx Packets : 354995
Missing Packets : 0
Misordered Dropped Packets : 0
Reordered Packets : 0
Malformed Packets : 0
Jitter Buffer Underrun : 0
Jitter Buffer Overrun : 0
Table 8-44. TDM PW Statistic Counters
Rx Packets Number of packets received on the PW from the PSN
Tx Packet Number of packets transmitted on the PW towards 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
Jitter Buffer Overrun Number of times jitter buffer was overrun state
Clearing Statistics
 To clear the PW statistics:
• At the prompt config>pwe>pw<pw_number>)#, enter clear-statistics.
The statistics for the specified PW are cleared.
Viewing the Pseudowire Status and Configuration Summary

 To display a single PW status:
1. At the config#pwe prompt, enter the desired pseudowire (pw <pw_number>).
The config>pwe>pw(<pw_number>)$ prompt appears.
2. Enter show status.
The status screen appears. For information on the OAM status values,
refer to the table below.
ETX-5>config>pwe>pw(1)# show status
PW : 1
Name : pw-1
PW Type : SAToP
PSN Type : Ethernet
OAM Status : Disabled
Out Label : 1
In Label : 101
SVI : 101
Attachment Circuit : E1/T1 3/1/1
Table 8-39 explains the OAM status values of the selected pseudowire.
Table 8-45. Pseudowire OAM Status Values
Displayed
Disable The pseudowire is disabled

Displayed
Up The pseudowire carries traffic, and both the remote and the local
pseudowire endpoints receive Ethernet frames. However, there
may be problems such as sequence errors, underflows, overflows,
etc., which can be displayed using the Statistics function.
Unavailable The pseudowire reports loss of connectivity (it did not receive
either OAM or data packets for 10 seconds or more; OAM link then
reports loss of synchronization). This is often caused by network
problems or configuration errors.
Down The pseudowire is waiting for a timeslot assignment
Local Fail A failure has been detected at the local pseudowire endpoint
Remote Fail A failure is reported by the remote pseudowire endpoint
Validation Fail The remote pseudowire endpoint replied to OAM packets, but
there is a configuration mismatch (the configuration parameters
used at two endpoints of the pseudowire are different).
 To display PW configuration summary:

• At the config>pwe# prompt, enter the show summary command.
For example:
ETX-5>config>pwe# show summary
PW : 1 PW Type : SAToP
PSN Type : UDP Over IP Status : Not present
Out Label : 1 In Label : 1
Peer : 1
Jitter Buffer : 1000 Payload Size : 24
 To display PW detailed information:

• At the config>pwe# prompt, enter the info detail command.
For example:
ETX-5>config>pwe# info detail
name: pwe-1
peer 1
label in 22 out 33
no oam
tdm-payload size 248 rate 31
jitter buffer 10000
psn-oos 1-bit
egress-port svi 1
no pm-enable
no shutdown

Example
 To configure a pseudowire:
• PW number 1
• PW type – T1 SAToP
• PSN type – Ethernet
• Out (destination) label – 1
• In (source) label – 1
• Jitter buffer – 3000
• OAM –disabled
• Peer – 1
• Egress port – SVI 1
• TDM payload size – 96
ETX-5>config>pwe# pw 1 type t1satop psn ethernet
ETX-5>config>pwe>pw(1) label out 1 in 1
ETX-5>config>pwe>pw(1) jitter-buffer 3000
ETX-5>config>pwe>pw(1) no oam
ETX-5>config>pwe>pw(1) peer 1
ETX-5>config>pwe>pw(1) egress-port svi 1
ETX-5>config>pwe>pw(1) tdm-payload 96
Note
See Pseudowire Service section for detailed example of a pseudowire
configuration.
detected.
Message Description
PW peer number has not been Cannot configure a pseudowire because PW peer number is
configured missing
PW inbound label hasn't been configured Cannot configure a pseudowire because inbound label is missing
PW outbound label hasn't been Cannot configure a pseudowire because outbound label is
configured missing
PW egress-port hasn't been configured Cannot configure a pseudowire because egress port is missing
PW TDM mandatory fields: tdm payload Cannot configure a pseudowire because TDM payload size, or
size/rate/jitter buffer, must be rate, or jitter buffer values are missing
configured
Peer must have a MAC assigned to it Cannot configure a pseudowire because a destination peer does
not have a MAC address assigned to it

Message Description
PW removal failed: PW is connected to a Cannot delete a pseudowire because it has timeslots assigned
cross-connection to it
PW egress-port SVI must be of type PW The SVI used by the pseudowire must be PW type
PW set failed: Payload size is below the Cannot configure a pseudowire because the TDM payload size is
minimum value below the minimum value
PW set failed: Payload size exceeds the Cannot configure a pseudowire because the TDM payload size is
maximum value above the minimum value
PW set failed: PW is connected to a Cannot configure a pseudowire because it has timeslots

cross-connection assigned to it
PW set failed: Maximum number of PWs Cannot configure a pseudowire because the maximum number
already configured of allowed PWs per chassis has been reached
PW set failed: PW number exceeds Cannot configure a pseudowire because its number is above the
maximum maximum allowed value (1344)
PW set failed: PW number fails to meet Cannot configure a pseudowire because its number is below the
minimum minimum allowed value (1)
PW PSN type must be of type IP in order Only PWs with UDP/IP network encapsulation support ToS
to set TOS field configuration
Egress port can only be set if PSN type is Only PWs with Ethernet or MPLS network encapsulation require
Ethernet egress port configuration
Egress port has not been configured Cannot configure a pseudowire because its egress port has not
been configured
Peer must have an IP assigned to it Cannot configure a pseudowire because its peer does not have
an IP address assigned to it
UDP mux method can only be updated if Only PWs with UDP/IP network encapsulation support UDP
PSN type is UDPoIP multiplexing method configuration
PW set failed: combination of peer and Cannot configure a pseudowire because its peer/outbound label
outbound label should be unique combination is not unique
PW set failed: TDM payload size or rate Cannot configure a pseudowire because selected TDM payload
invalid type or rate value is not valid
PW set failed: A peer must be configured Cannot configure a pseudowire because no PW peer has been
first configured yet
PW set failed: PW label value must be Cannot configure a pseudowire because the PW In label value is
unique already in use
PW set failed: Changing this parameter is Cannot modify pseudowire parameters when a PW is not shut
not allowed down


Chapter 9
Timing and
Synchronization
ETX-5 timing subsystem includes a central timing subsystem, located on the main
card, and local timing subsystems located on the individual I/O modules. This
chapter presents the following information on the ETX-5 clock capabilities:
• Clock Selection
• 1588v2 Timing.
9.1 Clock Selection

This section discusses clock selection mechanism provided by ETX-5,
synchronization sources supported by the chassis and their configuration
methods.
Standards and MIBs

ETX-5 timing functionality complies with following standards: G.703, G.704,
G.706, G.707, G.783, G.803, G.810–813, G.8261, G.8262, G.8264, IEEE 802.3
Part 3, IEEE 802.1D.
Benefits
Flexible timing mechanism utilizes standard technologies to ensure highly
accurate clock recovery and distribution over both the physical and packet layers
with powerful frequency, phase and ToD alignment capabilities.
Factory Defaults
Parameter defaults are listed in the tables below.
sync-network-type 2
quality min-level-station Network type 1 –SEC

Network type 2 – ST3
max-frequency-deviation 1200 × 100 ppm
mode auto
ETX-5 Clock Selection 9-1

Chapter 9 Timing and Synchronization Installation and Operation Manual
force-t4-as-t0 Enabled
Source Parameter Default Value
priority 4
wait-to-restore 300
hold-off 300
Station Clock Parameter Default Value
interface-type t1
line-type ESF for T1

G732N-CRC for E1
8 kHz for 64 kHz
rx-sensitivity short-haul
ssm-channel sa4
tx-ssm no tx-ssm
The figure below is a diagram of the ETX-5 timing mechanism.
Main Card
System 10GbE
Clock Ports
I/O
Clock 1
I/O
Clock 2
1588v2 T0 1588v2
(master) SEC Mux (slave) Station Clock
Station Clock Output (T4)
(BITS/GPS)
Station Clock
Output (T4)
Secondary Clock via

Standby Main Card
I/O Card 1
I/O Card 2
I/O Card 3
I/O Card 4
Figure 9-1. Timing Mechanism
9-2 Clock Selection ETX-5

Installation and Operation Manual Chapter 9 Timing and Synchronization
Clock Domain
The timing system in ETX-5 provides a single clock domain. The clock domain
distributes a system clock derived from up to four configured sources after
selection process implemented via Synchronous Equipment Clock (SEC). Clock
sources (SEC inputs) are as follows:
• Station clock (BITS/GPS–10 MHz)
• IEEE 1588v2 clock.
The synchronization network type identifies the type of synchronization network
and its levels. 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:
• Option I (Europe)
• Option II (USA), default.
Clock Quality Levels

You can define the timing quality level of the source (which can be fixed or SSM-
based) and the minimum quality level for the domain, or work without a quality
level at all (see Clock Selection). The supported quality levels are according to the
synchronization network type, as shown in the following tables. The quality levels
are listed in order of highest to lowest quality level.
Table 9-1. Option I Quality Levels
Quality Level Description Rank
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-2. Option II Quality Levels
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

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
To prevent transmission (via station clock interface) of a timing signal of inferior

quality, you must configure the quality level (QL) minimum parameter with the
minimum quality allowed. If the transmitted signal quality becomes lower than QL
minimum parameter, the external clock interface is squelched (or AIS is sent in E1
/ T1 mode).
SSM/ESSM Support
ETX-5 supports automatic learning/distributing clock QL using Sync Status
Message (SSMs) or Ethernet Synchronization Message Channel (ESMC) systems.
In the receive direction, an ESMC-FAILED state is declared if no ESMC messages
are received for a period of 5 seconds or more (with issuing SSF).
In the transmit direction, an ESMC message is transmitted every 1 second or
immediately if a change in QL is detected.
For synchronization source signals/interfaces that do not support SSM, it is
possible to force the quality level to a fixed value. This allows use of these
signals/interfaces as synchronization sources in the automatic reference clock
selection process in QL-enabled mode. You must configure a specific QL for all
the ingress synchronization interfaces that do not support SSM.
Clock Mode
The domain clock mode can be one of the following:
• Auto mode – domain timing is determined by the clock selection algorithm
(default)
• Free-run mode – the domain clock is based on the main card local oscillator
(TCXO)
• Force T0 holdover – the domain clock uses data stored by the T0 timing
generator during normal operation for timing output.

Note QL in free-run mode is SEC/ST3.
By default, ETX-5 uses free-run mode, until a valid clock source is selected.
Clock Domain States

Clock domain states indicate operation modes of the system clock (T0 timing
generator) and station clock output (T4 timing generator).
System clock:
• Locked – Locked to selected clock source
• Free-run – Locked to internal oscillator
• Holdover – Input lock is lost, the clock mechanism uses data stored during
normal operation for timing output.
Note By default, the ETX-5 system clock is in free-run state, until a valid clock source is
selected.
Station clock output:

• Locked – Locked to a valid clock input
• Unlocked – Not locked to a valid clock input.
Note By default, ETX-5 station clock output is in free-run state, until a valid clock
source is selected.
External Switch Commands

You can issue manual or forced switch commands to choose a specific clock
source. The manual command overrides the clock priority setting and allows
selection of a clock with priority a lower than an automatically selected clock
source. Both clock sources must have the same quality level.
The forced switch command allows selection of any clock source, regardless of its
priority or quality level. It overrides the previously issued manual switch
command.
The manual and forced switch commands are cleared using the clear command.
SEC Module
The clock domain provides the system clock according to one of the four timing
inputs, as selected by the SEC unit. The SEC module performs physical clock
selection, hitless switching, clock filtering and holdover. It consists of two timing
generators:
• T0 for system clock output
• T4 for station clock output.

Internal
Oscillator
(TXCO)
SEC Source Clock 1

System
Clock Source Clock 2
T0
Source Clock 3
T4 Source Clock 4
Station
Clock
Output
Figure 9-2. SEC Module
Quality Level
The SEC unit supports input prioritization and source quality level configuration,
according to network type:
Table 9-3. SEC Input Quality Level
Network Type Quality Level
Option I PRC, SSU-A, SSU-B, SEC, DNU, SSM-based
Option II PRS, STU, ST2, TNC, ST3E, ST3, SMC, ST4, DUS, SSM-based
Clock Selection
The clock selection algorithm is based on ITU-T Recommendation G.781. During
the selection process, the best synchronization source from the SEC inputs is
selected as the system clock. The selection process operates in two modes:
• QL-enabled, in which the following parameters are considered:
 Quality level
 Signal failure
 Priority
 External switch commands
If no overriding external commands are active, the algorithm selects the
reference clock that has the highest quality level without signaling a fail
condition. If both inputs have the same quality level, the input with the
highest priority is selected. If all inputs have the same highest priority, an
arbitrary reference clock is chosen. If no input clock is available, the SEC uses
internal oscillator timing.
• QL-disabled, in which the following parameters are considered:
 Signal failure
 Priority
 External switch commands

If no overriding external commands are active, the algorithm selects the reference
clock that has the highest priority without signal fail condition. If all inputs have
the same highest priority, an arbitrary reference clock is chosen. If no input clock
is available, the SEC uses internal oscillator timing.
Timers
For additional flexibility in clock restoration, the SEC module has two timers:
• Wait-To-Restore. The timer defines the time (in seconds) that a previously failed
synchronization source must be fault-free in order to be considered available.
• Hold-Off. The timer defines the time (in milliseconds) that a signal failure
must be active before it is relayed to the clock selection unit.
Switchover
Clock switchover (changing current reference clock) occurs if:
• An external clock switch command is received
• A locked source clock becomes invalid
• A higher priority/quality clock becomes available.
A source clock is considered invalid if any of the following is detected:
• Physical failure – Clock failure has been detected at the physical layer
• Monitoring failure – Clock failure has been detected by the clock monitoring
entity of the domain
• ESMC failure – Ethernet port only with SSM-based clock has not received valid
ESMC-packet stream for 5 seconds.
Note Switch over is always revertive. For non-revertive mode, you can configure several
sources with the same priority.
SEC Output
The SEC unit outputs a clock with Stratum-3 accuracy, jitter and holdover, in
compliance with the following requirements:
• GR-253-CORE for SONET Stratum 3 and SONET minimum clock (ST3)
• ITU-G813 Option 1 and Option 2 for SDH Equipment Clock (SEC).
The T0 timing generator of the SEC unit delivers a system (domain) clock to I/O
cards and to the second main card. In addition, the T4 timing generator outputs
an external clock for distribution to other network devices.
Note By default, the T4 generator is forced to use the same clock source as the T0
generator.

Main Card System

Clock
Bus
Source Clock 1 SEC I/O Card 1

System
Source Clock 2 T0 Clock I/O Card 2
Source Clock 3 I/O Card 3
T4
Source Clock 4 I/O Card4
Main card Ethernet ports
Station
Clock 1588v2 master entity
Output
Figure 9-3. SEC Output
Input Sources
The four clock sources (SEC inputs) are based on:
• Station clock (BITS or GPS-10 MHz)
• IEEE 1588v2 clock.
Note The following limitations apply to clock sources:

• Up to three SEC inputs can originate from main cards.
• One or two SEC inputs can originate from I/O cards (Ethernet or TDM).
Physical Port Clock

The ETX-5 clock domain can be configured to use timing information derived from
an STM-1/STM-4, OC-3/OC-12 or GbE/10GbE port located on an I/O card or a main
card.
Ethernet Ports
Ethernet ports located on E5-MC-4, E5-MC-SFP-P-4, E5-10GbE-2 or E5-GbE-20
support Synchronous Ethernet (Sync-E) master and slave modes according to ITU-
T G.8261–G.8266 requirements. This allows each port to:
• Extract the port clock. The derived clock will be used by the clock selection
mechanism as a source clock
• Set the port Tx clock according the domain clock available from the main card
• Act as a source of ESMC messages for SSM-based clock modes.
Sync-E mode can be used when phase synchronization or Time of Day (ToD) is
not required. The main advantages of Sync-E over 1588v2 clock are:
• It is propagated over physical layer

• It is a Stratum-3 clock with near SDH/SONET holdover properties

• It is not packet-oriented and considered to be more stable.
SDH/SONET Ports
The Rx clock of any SDH/SONET port on the E5-cTDM-4 or E5-cTDM-STM4cards
can be extracted and supplied to the main card clock selection mechanism (via
backplane clock bus).
Note When APS is enabled, clock is used from a selected interface and not from an APS
group.
The Tx clock of an SDH/SONET port is always locked to ETX-5 system clock.

When loopback timing is required, select Rx clock of the desired SDH/SONET port
Note
via main card clock selection mechanism
E/T1 Ports
The internal E1/T1 ports cannot be used as clock sources for the system clock.
The Tx clock of internal E1/T1 ports can be locked to:
• System clock
• Rx clock of the port
• Adaptive clock recovered from pseudowire stream connected to this E1/T1
port.
Station Clock
The station clock interface has two functions:
• Input for station clock signal (BITS and GPS clocks)
• Output for the ETX-5 nodal clock. This output provides a convenient means
for distributing the ETX-5 nodal clock signal to other equipment (BITS clock
only).
BITS Clock
ETX-5 recovers Building-Integrated Timing Supply (BITS) clock via the station clock
interface ports on E5-MC-4 and E5-MC-SFP-P-4 cards. See Appendix A for the
external clock connector pinout.
The following clock signals are supported:
• 2.048 Mbps, ITU-T G.703, 120Ω balanced, 75Ω unbalanced
• 64 kHz, ITU-T G.703, composite clock interface, 110Ω balanced.
When only one external clock source is available, you can improve hardware
protection by connecting the external clock inputs in parallel, by means of a
Y-cable.

GPS Clock
ETX-5 receives/transmits (1588v2 master/slave) GPS-based frequency and phase
reference signal from GPS units, using the following interfaces on the E5-MC-4 or
E5-MC-SFP-P-4 card:
• Input or output of 10 MHz sinewave synchronization signal via mini-BNC (DIN
1.0/2.3) connector
• Input and output of ToD timestamp signal via Rj-45 connector with RS-422
interface
• Input or output of 1PPS TTL synchronization signal via mini-BNC connector.
When only one GPS clock source is available, you can improve hardware
protection by connecting the GPS clock inputs in parallel, by means of a Y-cable.
IEEE 1588v2 Clock

See 1588v2 Timing section below.
Redundancy
When ETX-5 is equipped with two main cards, clock selection and distribution
mechanisms are mirrored in the active and backup cards. This ensures full timing
system redundancy.
SEC Redundancy
When a clock source is configured for the active main card, the action is
duplicated in the backup card. This results in the same clock source feeding both
SECs. The SECs are connected internally to improve switchover time and reduce
phase difference when a flip occurs.
The two SEC outputs (active and backup) are master to the I/O cards, which use
only the active one.
Station Clock
Any station clock can be used as a clock input on an active or backup main card.
Each SEC can use input from both station clock sources.

Active Main Card
System Primary
Clock Station Clock
SEC Mux
Secondary
From backup card To backup card
Backup Main Card
System Secondary
Clock Station Clock
SEC Mux
Primary
From active card
Figure 9-4. Station Clock Redundancy
Configuring the Clock

The clock configuration procedure consists of the following steps:
• Domain configuration
• Timing source configuration
• Station clock configuration (if needed)
• Recovered clock configuration (if needed).
Configuring the Clock Domain

By default, ETX-5 has one clock domain (domain 1).
 To configure the clock domain:

1. Navigate to configure system clock domain 1.
The config>system>clock>domain(1)# prompt is displayed.

Setting the type of sync-network-type { 1 | 2 } Type 1 – Europe

synchronization network Type 2 – USA
When you change the synchronization network
type, you must redefine the clock sources.
Synchronization network type defines the Rx input
clock type that can be used as a domain source.
For example, only an E1 Rx clock can be selected as
an input clock for type 1 (European)
synchronization network.
This parameter cannot be modified if a clock
source has been configured. Remove the clock
source before changing network type.
Setting minimum quality of quality min-level-station { prc | ssu-a | Minimum clock quality definition is needed to
outgoing station clock ssu-b | sec | dnu } prevent outputting low-quality clock via external
quality min-level-station { prs | stu | clock interface.
st2 | tnc | st3e | st3 | smc | st4 | dus | no quality removes the quality parameter. If no
prov } quality is defined for the domain you cannot
configure quality level for the sources.
The quality values are according to the
synchronization network type defined for the
domain (refer to Table 9-1)
Verify that the force-t4-as-t0 option is disabled.
Setting the clock mode mode { auto | free-run | force-t0- auto –Clock selection mechanism functions
holdover } normally; that is, the best available clock source is
selected for synchronization.
free-run – Internal oscillator is used for
synchronization
force-t0-holdover – Forces the T0 timing generator
to holdover mode (no force-t0-holdover clears T0
from holdover mode)
Setting maximum max-frequency-deviation <value> 381–6096 × 100 ppm

frequency deviation When a frequency deviation of an input clock
source exceeds defined value, this clock source is
declared invalid
Forcing T4 timing force-t4-as-t0 no force-t4-as-t0 prevents T4 timing generator

generator to use the same from using the same clock source as the T0
clock source as the T0 generator
generator
Forcing a selection of a force <source-id>

particular clock source
when the sources have
different quality levels

Manually selecting a manual <source-id>

particular clock source in
the following conditions:
• No quality is defined
for the clock domain
• The sources have the
same qualities
• The sources have
different priorities.
Canceling a previously clear

issued force or manual
command
Adding clock source (refer

to Configuring the Clock
Sources)
Configuring clock source no source <src-id> deletes the source
(refer to Configuring the
Clock Sources)
Displaying status show status
 To display clock status;

2. At the config>system>clock>domain(1)# prompt, enter show status.
Clock status provides information on:
 Current system clock source, state and quality:
 Locked – Locked to selected clock source
 Free-run – Locked to internal oscillator
 Holdover – Input lock is lost, the clock mechanism uses data stored
during normal operation for timing output
 Current station out clock source and state
 Forced and manual switch command status
ETX-5>config>system>clock>domain(1)# show status
System Clock Source : 0 State : Freerun Quality : ST3

Station Out Clock Source : 0 State : Unlocked
Force Switch : InActive
Manual Switch : InActive
Configuring the Clock Sources

You can define up to four clock sources for the domain. The sources can be:
• Ethernet port on main card or I/O Ethernet card

• SDH/SONET port on a TDM I/O card

• Station clock
• Recovered clock (1588v2).
Note The following limitations apply to clock sources:

• Up to three sources can originate from main cards.
• One or two sources can originate from I/O cards (Ethernet or TDM).
 To add a clock source:

1. Verify that the clock source to be used as an input is valid.
Note You can choose an invalid clock source. However, this input will be rejected by
the domain during the clock selection process.
2. Verify that the card whose port will be used as a source clock is provisioned.
3. Verify that the port to be used as a source clock is enabled (no shutdown).
Note If you choose an invalid clock source, this input will be rejected by the domain
during the clock selection process.

5. Type one of the following, according to the required clock source:
 For Ethernet port: clock source <1–4> rx-port ethernet <slot/port>
Use main-a or main-b designation for main card ports.
Note To ensure correct distribution of SSM traffic, you must configure flow with an
L2CP profile with peer action on the 01-80-c2-00-00-02 address. The flow must
have the following attributes:
• Ingress port – Ethernet port/LAG, serving as the SSM source (Sync-E port
If you use the flow only to peer the SSM frames and do not need to forward the
untagged traffic, discard it, using the drop command on the flow
 For SDH/SONET port: clock source <1–4> rx-port sdh-sonet <slot/port>

 For station clock: clock source <1–4> station <main-a/1 or main-b/1>
 For recovered clock: clock source <1–4> recovered < main-a/1 or
main-b/1>
6. Enter all necessary commands according to the tasks listed below the next
procedure.
 To configure a clock source for which the port has been defined:


2. Type source <1–4> to select the source to configure.
The config>system>clock>domain(1)>source(<1–4>)# prompt is
displayed.
Setting the priority to be taken priority <num> 1–4

into account during the clock Priority 1 is the highest.
selection process
no priority disables clock source priority
Setting quality level of the quality-level { prc | ssu-a | ssu-b | sec | Clock source quality, as well as source priority are
clock source dnu | ssm-based } taken into account during clock selection process.
quality-level { prs | stu | st2 | tnc | st3e | If no quality is defined for the domain, this
st3 | smc | st4 | dus | ssm-based | prov } command is not available.
The quality level values are according to the
synchronization network type defined for the
domain.
The quality level ssm-based indicates the quality
level is learned automatically via SSM messages
or S1 byte of SDH/SONET frames.
When using SSM-based clock source, add a flow
supplying ESMC messages to the port.
Defining the amount of time wait-to-restore <seconds> 0–720

that a previously failed
synchronization source must
be fault free in order to be
considered available
Defining the amount of time hold-off <milliseconds> 300–1800

that signal failure must be
active before it is transmitted
Canceling the wait-to-restore clear-wait-to-restore This is useful if a timing source fault is cleared
timer of a clock source and you want the source to be available
immediately
Displaying status show status
Displaying Clock Source Status
 To display the source clock status:

1. Navigate to configure system clock domain 1 source <src-id>.
config>system>clock>domain(1)>source(<src-id>)#.
The clock source status is displayed.

ETX-5>config>system>clock>domain(1)>source(1)#
ETX-5>config>system>clock>domain(1)>source(1)# show status
Status : OK
Tx Quality : DNU
Rx Quality : PRC
ESMC State : Unlocked
WTR State : Inactive
Clock status provides information about:
 Clock source status:
 OK – The clock source is valid and can be considered as clock input
candidate for the system clock
 Physical Fail – Clock failure has been detected at the physical level
 Monitoring Fail – Clock failure has been detected by the clock
monitoring entity of the domain. One reason for declaring a
monitoring failure state is that the maximum frequency deviation of
the clock source has been exceeded.
 ESMC Fail – Ethernet port with SSM-based clock has not received a
SSM-packet stream for 5 seconds. Make sure the Ethernet port has
been configured to supply SSMs and a dedicated flow has been
directed to the port.
 Tx quality – Transmit clock quality
 Rx quality – Receive clock quality
 ESMC State – State of the Ethernet Synchronization Messaging Channel
(ESMC)
 WTR State – Wait-to-restore counter status
Displaying Clock Source Statistics

You can display the Ethernet Synchronization Messaging Channel (ESMC) statistics
for the clock sources. ESMC is used as a transport layer for SSMs in Sync-E. The
ESMC statistic counters are available for GbE and 10GbE ports only.
 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.
ETX-5>config>system>clock>domain(1)>source(1)#
ETX-5>config>system>clock>domain(1)>source(1)# show statistics
ESMC Failure Counter : 1
Rx Tx
ESMC Events : 0 1
ESMC Information : 0 29
 ESMC Events – Number of changed quality level messages sent and
received
 ESMC Information – Number of quality level information messages sent
and received
Example
 To configure clock selection:

• Domain 1:
 Synchronization network type 1
 Source 1: Station clock port on main card A
 Source 2: Ethernet port 1 on main card A.
#***************************Defining_Station_Clock_Source********************
configure system clock station main-a/1
interface-type e1
no shutdown
show status
exit all
#*********************************End****************************************
#***************************Configuring_Clock_Domain*************************
configure system clock domain 1
sync-network-type 1
source 1 station main-a/1
priority 1
wait-to-restore 0
exit
source 2 rx-port ethernet main-a/1

priority 2
wait-to-restore 0
exit all
#*********************************End****************************************
#***************************Configuring_Ethernet_Ports***********************
tx-ssm
no shutdown
exit all


no shutdown
exit all
#*********************************End****************************************
#*******************Configuring_Classifiier_Profile_for_SSM_Flow*************
configure flows classifier-profile class1 match-any match untagged
#*********************************End****************************************
#*******************Configuring_L2CP_Profile_for_SSM_Flow********************
configure port l2cp-profile l1
mac 01-80-c2-00-00-02 peer
exit all
#********************************Adding_SSM_Flow*****************************
classifier class1
0/1
l2cp profile l1
no shutdown
exit all
#*********************************End****************************************
Configuring Station Clock

The ETX-5 system clock can also use a signal received from a station (external)
source as reference.
The station clock interface has two functions:
• Input for external clock signal
• Output for the ETX-5 clock. This output provides a convenient means for
distributing the ETX-5 clock signal to other equipment or loop it back.
oNote • The station clock input can be looped back directly via station clock output.
• The station clock interface does not provide Tx clock, if it uses a GPS 10 MHz
signal.
The station clock ports are located on the main cards and provide the following
timing interfaces:
• E1 via RJ-45 balanced and BNC unbalanced ports
• T1 via RJ-45 balanced port
• 2 MHz square-wave synchronization via RJ-45 balanced and BNC unbalanced
ports
• 64 kHz composite via RJ-45 balanced port
• GPS 10 MHz via mini BNC port (input only).

 To configure the station clock:

1. Navigate to configure system clock station main-a/1 or main-b/1.
The config>system>clock>station(main-a/1 or main-b/1)# prompt is
displayed.
Setting the interface type interface-type {e1 | t1 | 2mhz | 64khz | gps} You can configure the interface
type only if the station clock is
(shutdown).
If you specify e1 or 2mhz and do
not specify balanced or
unbalanced, by default the
interface is set as balanced.
Changing the interface type resets
all other related parameters to
their default values.
Setting impedance for E1 impedance {balanced | unbalanced}

and 2-MHz interfaces
Setting line type for E1, T1 line-type {g732n | g732n-crc}

or 64 kHz interfaces line-type {sf | esf}
line-type {8khz | 8khz-400hz}
Assigning a name to a name <string> no name removes the station

station clock source clock source name
Setting receiver sensitivity rx-sensitivity {short-haul | long-haul} Used to adjust the signal’s
for E1 and 2-MHz capability to reach destinations
interfaces. close by or farther away
Defining transmit (output) tx-clock-source {station-rclk | domain <domain-number>} The output station clock can be
clock type locked to station Rx clock
(loopback) or to domain (T4) clock
Defining E1 G.732N–CRC ssm-channel {sa4 | sa5 | sa6 | sa7 | sa8} For T1 ESF interface, SSM
bits to carry SSM information is carried over FD.
information
Enabling SSM transmission tx-ssm Enabling SSM transmission allows

for E1 G.732N–CRC and T1 using station clock as a SSM–
ESF interfaces based input clock for domain.
no tx-ssm disables SSM
transmission
Administratively enabling no shutdown shutdown disables the station

station clock clock
Displaying station clock show status

status

Displaying Station Clock Status

The station clock status screen displays information about the station clock
name, its statuses and received SSM quality.
 To display station clock status:

1. Navigate to configure system clock station main-a/1 or main-b/1.
The config>system>clock>station(main-a/1 or main-b/1)# prompt is
displayed.
The station clock status is displayed.
ETX-5>config>system>clock>station(main-a/1)# show status
Name : Station Clk-5-1
Detailed Status :
Received SSM : Quality Unknown
Example
 To configure clock selection:

• Main card A
• Interface type: E1
• Line type: G732N-CRC
• Name: E1_Station_Clock_1
• Transmit clock source: domain 1
• SSM transmission enabled.
ETX-5# configure system clock station main-a/1
ETX-5>config>system>clock>station(main-a/1)# shutdown
ETX-5>config>system>clock>station(main-a/1)# interface-type e1
ETX-5>config>system>clock>station(main-a/1)# line-type g732n-crc
ETX-5>config>system>clock>station(main-a/1)# name E1_Station_Clock_1
ETX-5>config>system>clock>station(main-a/1)# tx-clock-source domain 1
ETX-5>config>system>clock>station(main-a/1)# tx-ssm
ETX-5>config>system>clock>station(main-a/1)# no shutdown
Configuring Y-Cable Protection

For the best protection of a clock subsystem, it is recommended to connect the
two station clock interfaces to two separate station clock sources. When only
one station clock source is available, you can achieve better hardware protection
by connecting the station clock inputs in parallel, by means of a simple Y-cable. In
such an instance, configure the clock domain to use two station clocks on
different main cards as inputs 1 and 2. This configuration ensures that if one of
the main cards fails, the clock domain continues receiving timing from the
remaining main card. The two station clocks used for Y-cable redundancy must be
identical.

Main Card A
Input 1
Station Clock SEC
Input 2
Y-Cable
Clock Source Main Card B
Station Clock SEC
Figure 9-5. Y-Cable Redundancy
Note Although not shown in Figure 9-5, inputs 1 and 2 are doubled in main card B for
redundancy.
 To control Y-cable redundancy:

1. Verify that both station clocks to be used in Y-cable redundancy have been
configured with the same parameters (interface type, line type etc).
2. Navigate to configure system clock

The config>system>clock# prompt is displayed.
3. Enter station-y-cable to enable Y-cable protection or no station-y-cable to
disable it.
Example
This example shows the configuration procedure for defining two clock sources:
• Source 1 – E1 station clock
• Source 2 – SDH/SONET port 1 on TDM card in slot 1.
#*************************Activating_SDH_SONET_Port**************************
ETX-5# configure port sdh-sonet 1/1
ETX-5>config>port>sdh-sonet(1/1)# no shutdown
ETX-5>config>port>sdh-sonet(1/1)# exit all
#*********************************END****************************************
#*************************Configuring_Station_Clock**************************
ETX-5# configure system clock station main-a/1
ETX-5>config>system>clock>station(main-a/1)# shutdown
ETX-5>config>system>clock>station(main-a/1)# interface-type e1

ETX-5>config>system>clock>station(main-a/1)# no shutdown
ETX-5>config>system>clock>station(main-a/1)# show status

Name : Station Clk-5-1
Detailed Status :
Received SSM : PRC
#*********************************END****************************************
#*************************Configuring_Clock_Domain***************************
ETX-5# configure system clock domain 1
ETX-5>config>system>clock>domain(1)# sync-network-type 1
#*********************************END****************************************
#**********************Configuring_Station_Clock_as_Source_1*****************
ETX-5>config>system>clock>domain(1)# source 1 station main-a/1
ETX-5>config>system>clock>domain(1)>source(1)$ wait-to-restore 10
ETX-5>config>system>clock>domain(1)>source(1)$ show status

Status : Monitoring Fail
Tx Quality : SEC
Rx Quality : SSM Based
WTR State : Running <===== WTR Timer is running
ETX-5>config>system>clock>domain(1)>source(1)$ clear-wait-to-restore
Status : OK
Tx Quality : DNU
Rx Quality : PRC
ETX-5>config>system>clock>domain(1)>source(1)$ exit
System Clock Source : 1 State : Locked Quality : PRC
Station Out Clock Source : 0 State : Unlocked Force Switch:

InActive

#*********************************END****************************************
#**********************Configuring_SDH_SONET_Port_as_Source_2****************
ETX-5>config>system>clock>domain(1)# source 2 rx-port sdh-sonet 1/1
ETX-5>config>system>clock>domain(1)>source(2)$ quality-level ssu-a
ETX-5>config>system>clock>domain(1)>source(2)$ wait-to-restore 10
Status : OK
Tx Quality : PRC

Rx Quality : SSU-A
System Clock Source : 1 State : Locked Quality : PRC
Station Out Clock Source : 2 State : Locked Force Switch:

InActive

#*********************************END****************************************
detected.
Message Description
Duplicated Source Selected clock source is already in use
Existing sources should be removed first Domain parameters cannot be modified before removing the
clock sources connected to it
Invalid Domain Mode Selected domain mode is invalid
Invalid Domain Number Clock domain number is not 1
Invalid Holdoff Timer Selected holdoff timer value is out of allowed range (300–1800)
Invalid Priority Clock priority number is out of allowed range (1–4)
Invalid Source ID Selected source ID is invalid
Invalid Source Number Clock source number is not within range (1–4)
Invalid Source Type Selected source type is invalid
Invalid Source Configured clock source is invalid
Invalid WTR Timer Selected holdoff timer value is not within range (0–720)
Source is not Configured Selected clock source has not yet been configured
Interface is in conflict with domain Interface and domain do not have the same network type
network type
9.2 1588v2 Timing

ETX-5 fully supports IEEE 1588v2 Precision Time Protocol for distribution of
synchronization signals over packet-switched networks. The device operates in
master, transparent and slave clock modes with hardware-based time-stamping
as well as ToD (time of day) synchronization.
ETX-5 1588v2 Timing 9-23

Standards and MIBs

G.8265.1 IEEE 1588 profile
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. The use of
PTP is beneficial for applications that cannot bear the cost of a GPS receiver at
each node, or for which GPS signals are inaccessible.
Factory Defaults
By default, each 1588v2 entity is disabled and configured as neither master nor
slave. When enabled, it has the following default settings:
Master Parameter Default Value
ip-address –
ptp-domain 4
maximum-slaves 256
mode time-frequency
sync-rate 64pps
tx-clock domain 1
Slave Parameter Default Value
ip-address –
ptp-domain 4
BMCA revertive
wait-to-restore 300
recovery-mode time-frequency
priority 1
network-type Automatic
peer 0
sync rate – 128pps

grant-period –300
announce rate – 2sec

grant-period –300
delay-respond rate – 128pps

grant-period –300
9-24 1588v2 Timing ETX-5

Slave Parameter Default Value
quality-level type2SsmBased
When implementing the 1588v2 PTP, ETX-5 operates in the following roles:
• 1588v2 master, eliminating the need for an external timing device installed in
the core of the network to support 1588v2 timing distribution. The ETX-5
system is located near the core of the network and supplies clock reference
to remote Ethernet CPEs operating in 1588v2 mode.
• 1588v2 slave, regenerating frequency and time from 1588v2 packets received
from grandmaster
• 1588v2 transparent. In the transparent mode, ETX-5 timestamps the
correction field of traversing 1588v2 (UDP/IP) packets to reflect time in
ingress to egress direction. The device updates the correction field directly
and does not use follow-up messages for the time-correction functionality.
1588v2 Master Mode

ETX-5 supports one or two redundant 1588v2 master entities (one per main
card) with a total of up to:
• 512 slaves at 64 PPS rate
• 256 slaves at 128 PPS rate.
Note Currently, ETX-5 supports up to 128 slaves per main card.
ETX-5 1588v2 master entities comply with the G.8265.1 (PTP telecom profile)
requirements. They operate in one-way and two-way modes, providing frequency
and frequency/time information to the slaves. With one-step synchronization,
ETX-5 does not use follow-up messaging.
Figure 9-6 illustrates the basic schematics of the 1588v2 master functionality.
Both 1588v2 master entities reside on loopback addresses of the router. The
1588v2 entities generate PTP packets, which are encapsulated with UDP/IP and
forwarded to 1588v2 slaves via PSN.

Main Card A
Loopback RIF
1588v2
1588v2 ETH
Slave
Master
I/O Card
RIF
1588v2
Router RIF ETH Slave
1588v2
RIF ETH Slave
Loopback RIF
1588v2
Master
Main Card B
Figure 9-6. 1588v2 Master
Two independent master clock systems reside on active and backup main cards.
They have the same clock input and distribute timing signals to all slaves in their
domains. Up to 512 1588v2 slaves are supported. 1588v2 packets are
transmitted via GbE and 10GbE ports on the Ethernet main and I/O cards.
Sources
Each 1588v2 master entity has three inputs (frequency and time):
• Frequency from the SEC
• Time of Day (ToD) from the RS-422 interface (NMEA 0183)
• Phase (1 PPS, or Pulse Per Second) from the RS-422 or mini BNC interface.

Active Main Card
Time of Day
RS-422
Phase Mini
BNC
ToD
and
1PPS
1588v2 Frequency Clock 1PPS
Master SEC Inputs
10 MHz GPS
Backup Main Card Source
ToD
1588v2 Frequency Clock and
Master SEC Inputs 1PPS
1PPS
Time of Day RS-422
Phase Mini
BNC
Figure 9-7. 1588v2 Timing Inputs
ToD, 1 PPS and 10 MHz GPS (via SEC) inputs to the active and backup main cards
can be connected to the same GPS source via a Y-cable for clock system
redundancy.
Redundancy
When ETX-5 is equipped with two main cards, the chassis provides two
independent 1588v2 master entities. 1588v2 slaves use the Best Master Clock
(BMC) algorithm for selecting the clock source with the best quality.
ETX-5 supports two 1588v2 protection topologies, illustrated in Figure 9-8 and
Figure 9-9:
• Redundant main cards –1588v2 slave operates opposite a single ETX-5 with
two main cards. One of the 1588v2 masters is defined as active (primary),
and the other one – as backup (secondary).
• Redundant chassis – 1588v2 slave operates opposite two ETX-5s with a
single 1588v2 master entity each.

ETX-5
Main Card A
1588v2
Master
1588v2
Slave Main Card B
1588v2
Master
Legend:
Active
Backup
Figure 9-8. Card Redundancy
ETX-5
Main Card A
1588v2
Master
1588v2
Slave ETX-5
Main Card A
1588v2
Master
Legend:
Active
Backup
Figure 9-9. Chassis Redundancy
1588v2 Slave Mode

The slave clock works in a dynamic mode with the master clock, requesting
synchronization signal transmission and specifying the period of time and
frequency for signal transmission. When the master clock grants signal
transmission, it notifies the slave clock of the master clock quality level and
source port identification, and then periodically transmits synchronization signals.

The 1588v2 slave entity receives TOD information from the master clock source
and outputs NMEA messages via TOD RJ-45 connector.
Recovery Modes
The 1588v2 slave entities operate in two-way mode to recover synchronization
information, using sync, delay request and delay response messages. The
message exchange modes are as follows:
• Frequency. In this mode, the 1588v2 slave entity reconstructs remote clock,
using sync and delay request/response messages, while ignoring TOD
information (time indication and time-related status/alarm messages).
• Frequency and time. In this mode, the 1588v2 slave entity reconstructs
remote clock, using sync and delay request/response messages, while
providing TOD information via TOD interface.
Forwarding
The 1588v2 slave entity uses a dedicated router loopback interface for message
forwarding, similar to 1588v2 master (Figure 9-6). This LB RIF cannot be shared
with either a 1588v2 master entity or a PW.
Redundancy
The ETX-5 1588v2 slaves support non-revertive clock redundancy, using the Best
Master Clock (BMC) algorithm for selecting the clock source with the best quality.
If a failure is detected (no sync massages within 10 seconds), the 1588v2 slave
entity switches to the secondary master clock source.
Configuring 1588v2 Master Clock

ETX-5 chassis with two main cards supports two independent 1588v2 master
entities. Each 1588v2 master has its own configuration database which is
mirrored in both active and backup main cards.
 To configure 1588v2 master:

1. Verify that you have defined a loopback-type router interface with a valid IP
address. This IP address must be used as the IP address of 1588v2 master
entity.
2. Navigate to configure system clock.
3. At the config>system>clock# prompt, enter master[ main-a/1 | main-b/1 ]
{ptp}.
The config>system>clock>master(main-a/1 or main-b/1)# prompt is
displayed.
Note • no master disables PTP master mode, setting the 1588v2 entity to be neither
master nor slave (recovered) mode.
• Slave mode cannot be activated, while the 1588v2 entity is in the master
mode. Use no master command prior to switching between slave and master
modes.

4. In the config>system>clock>master(main-a/1 or main-b/1)#prompt, enter all

necessary commands according to the tasks listed below.
Activating the 1588v2 no shutdown shutdown deactivates the 1588v2 master entity
master entity
Defining IP address of ip-address <value> The IP address of 1588v2 master entity must be
1588v2 master entity the same as the IP address of the router loopback
interface
Creating a PTP domain ptp-domain <4–23> 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 a maximum maximum-slaves <1–512 > The total number of slaves supported by 1588v2
number of slaves master entities residing on both main cards is 512
Defining the 1588v2 mode {frequency | time-frequency} In frequency mode the master transmits sync and
message exchange mode announce messages to slaves
In time-frequency mode the master transmits sync,
announce and delay response messages to slaves
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 1588v2 master show status

status
Displaying 1588v2 slave slave <value > show status The slave is identified by its IP address
status
Enable statistic collection pm-collection no pm-collection resets statistic counters and

stops further collection of performance monitoring
data
Displaying statistics show statistics running
Displaying Status
You can display the current status of the 1588v2 master and the slaves in its
domain.
 To display 1588v2 master status:

• At the config>system>clock>master(main-a/1 or main-b/1)#prompt, enter
show status.
The 1588v2 master status is displayed.
ETX-5>config>system>clock>master(main-a/1)# show status

Administrative Status: Up
Detailed Status : OK
Slave IP Address Oper Clock Identity Announce Delay Rs
Mode Rate Rate
(pps) (pps)
1 1.1.1.1 Frq xx:xx:xx:xx:xx:xx:xx:xx:xx:xx 16 --
2 2.2.2.2 Frq+T xx:xx:xx:xx:xx:xx:xx:xx:xx:xx 16 16
The 1588v2 master status provides information about:
 Administrative status:
 Up –1588v2 master is administratively enabled
 Down – 1588v2 master is administratively disabled
 Operational status:
 Up –1588v2 master is operating properly
 Down – 1588v2 master has failed
 LLD – Lower Link Down
 Detailed status:
 OK –1588v2 master is operating properly
 TOD Failure – ToD source failure
 1PPS Failure – 1PPS source failure
 Slave status, including its number, IP address, message exchange mode,
identifier (MAC address), announce and delay response message rates.
 To display 1588v2 slave status:

slave <IP address> show status.
The 1588v2 slave status is displayed.
ETX-5>config>system>clock>master(main-a/1)# slave 1.1.1.1 show status
Validity : On
Operational Mode : Frequency+Time
Clock Identity : xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Announce Rate (pps) : 4
Announce Period (sec) : 6
Delay Response Rate (pps) : 4
Delay Response Period (sec) : 5
The 1588v2 slave status provides information about:
 Validity –Slave validity
 Operational Mode – Message exchange mode
 Clock Identity – Unique slave identifier (MAC address)
 Announce Rate – Current rate of Announce messages
 Announce Period – Period of time for which an Announce message is
transmitted
 Delay Response Rate – Current rate of Delay Response messages

 Delay Response Period – Period of time for which an Delay Response

message is transmitted
If the collection of performance monitoring data is enabled, you can display the
current statistics for 1588v2 master or slave.
 To display statistics:
show statistics running to display master statistics.
or
• At In the config>system>clock>master(main-a/1 or main-b/1)#prompt, enter
slave < IP address> show statistics running to display slave statistics.
The 1588v2 master or slave statistics are displayed.
ETX-5>config>system>clock>master(main-a/1)# show statistics running
Running
-----------------------------------------------------------------------------
Tx Packets : 1
Tx Sync Packets : 1
TX Follow Up Packets : 1
TX Delay Response Packets : 1
TX Announce Packets : 1
TX Signaling Packets : 1
Rx Packets : 1
RX Signaling Packets : 1
RX Delay Request : 1
Discarded Signaling Packets : 1
ETX-5>config>system>clock>master(main-a/1)>slave(1.1.1.1)#show statistics running
Running
------------------------------------------------------------------------------
Tx Sync Packets : 1
TX Follow Up Packets : 1
TX Delay Response Packets : 1
TX Announce Packets : 1
TX Signaling Packets : 1
RX Signaling Packets : 1
RX Delay Request : 1
Discarded Signaling Packets : 1
Table 9-5. 1588v2 Master Statistic Counters
Counter Description
Tx Packets Number of all packets transmitted by 1588v2 master
Tx Sync Packets Number of Sync packets transmitted by 1588v2 master or slave
TX Follow Up Packets Number of Follow-up packets transmitted by 1588v2 master

Counter Description
TX Delay Response Packets Number of Delay Response packets transmitted by 1588v2 master or
slave
TX Announce Packets Number of Announce packets transmitted by 1588v2 master or slave
TX Signaling Packets Number of Signaling packets transmitted by 1588v2 master or slave
Rx Packets Number of all packets received by 1588v2 master
RX Signaling Packets Number of Signaling packets received by 1588v2 master or slave
RX Delay Request Number of Delay Request packets received by 1588v2 master or slave
Discarded Signaling Packets Number of Signaling packets discarded by 1588v2 master or slave
detected.
Message Description
Distributed must be defined as none The 1588v2 clock cannot be changed from master to recovered,
or vice versa, skipping the None state
Distributed PTP must be in shutdown The 1588v2 master cannot be modified while it is active
Domain must be 1 The Tx clock domain is not 1
Invalid IP Address The defined IP address is invalid
IP must be configured as a router LB The defined IP address must be the router loopback interface
address address
Maximum number of slaves per shelf The maximum number of allowed 1588v2 slaves per chassis has
must be less than 512 been exceeded
Maximum slave is out of range The number of 1588v2 slaves is not within range (1–512 per
chassis)
Missing IP address configuration The IP address must be defined before attempting to enable the
1588v2 masters
PTP domain is out of range The PTP domain number is not within range (4–23)
Sync rate is out of range The synchronization message rate value is not within range
Configuring 1588v2 Slave Clock Configuration

Configuration of the ETX-5 1588v2 entity to slave mode requires:
• Defining 1588v2 slave entity
• Configuring a peer 1588v2 master entity for the slave.

Defining 1588v2 Slave Entity
 To define a 1588v2 slave entity:

1. Verify that you have defined a loopback-type router interface with a valid IP
address. This IP address must be used as the IP address of the 1588v2 slave
entity.
3. At the config>system>clock# prompt, enter recovered [ main-a/1 | main-b/1 ]
{ptp}.
The config>system>clock>recovered(main-a/1 or main-b/1/ptp)# prompt
is displayed.
Note • no recovered disables the PTP slave mode, setting the 1588v2 entity as
neither slave (recovered mode) nor master.
• Slave mode cannot be activated, while the 1588v2 entity is in the master
mode. Use no recovered prior to switching between slave and master modes.
4. At the config>system>clock>recovered(main-a/1 or main-b/1)# prompt, enter

all necessary commands according to the tasks listed below.
Activating 1588v2 slave no shutdown shutdown deactivates 1588v2 slave entity

entity
Defining IP address of ip-address <value> The IP address of the 1588v2 slave entity must be
1588v2 slave entity the same as the IP address of the router loopback
interface
Creating a PTP domain ptp-domain <4–23> A domain consists of one or more PTP devices
(masters or slaves) communicating with each other
according to PTP requirements. For the correct
distribution of timing signals, a 1588v2 master and
the slaves operating with it must belong to the
same PTP domain.
Defining BMCA (Best revertive Revertive mode – if a higher priority master

Master Clock Algorithm) nonRevertive becomes available, the 1588v2 slave uses it as its
mode active master
Non-revertive – if a higher priority master becomes
available, the 1588v2 slave remains with its current
active master
Defining amount of time wait-to-restore <0–720>

that previously failed clock
must be fault free in order
to be considered available

Defining the 1588v2 mode recovery-mode {frequency | time- frequency – the 1588v2 slave entity reconstructs
frequency} remote clock, using sync, delay request/response
messages, and ignoring TOD information (time
indication and time-related status/alarm messages)
time-frequency –the 1588v2 slave entity
reconstructs remote clock, using sync, delay
request/response messages, providing also TOD
information via TOD interface
Displaying 1588v2 slave show status Displaying 1588v2 slave status

status
Displaying statistics show statistics running
Configuring a Peer 1588v2 Master
 To configure a peer 1588v2 master:

1. Verify that you have defined a peer with a valid IP address. This IP address
must be used as the IP address of the master clock for the slave entity.
2. Navigate to configure system clock recovered main-a/1 or main-b/1.
The config>system>clock>recovered(main-a/1 or main-b/1)# prompt is
displayed.
3. At the config>system>clock>recovered(main-a/1 or main-b/1)# prompt, enter
master<1 or 2>.
The config>system>clock>recovered(main-a/1 or main-b/1)>master 1 or
master 2# prompt is displayed.
Note To delete a peer 1588v2 master, use no master 1 or no master 2 syntax.
4. At the config>system>clock>recovered(main-a/1 or main-b/1)>master 1 or

master 2# prompt, enter all necessary commands according to the tasks
listed below.
Activating peer 1588v2 no shutdown shutdown deactivates peer 1588v2 master

master
Defining peer master master-identity {clock-id<value> port Default clock ID value (0xFFFFFFFFFFFFFFFFFFFF)
source port ID <value>} indicates that the slave retrieves the master source
port ID from the Announce messages.
Any other value indicates that the slave ignores the
value delivered in the Announce messages and
uses the one that has been configured by the user.

Defining peer master priority { 1 | 2} When a 1588v2 slave operates opposite two
priority 1588v2 masters with the same quality level, it
selects a clock source with the highest priority
(priority 1)
Specifying the peer device peer <peer-number>

that transmits the clock
signal
Defining synchronization sync {rate [16pps |32pps | 64pps | All slaves within a domain must use the same sync
message rate requested by 128pps] [grant-period <60–1000>} message rate parameters
the slave and duration of
sync message transmission
Defining Announce announce {rate [16sec |8sec |4sec All slaves within a domain must use the same
message rate requested by |2sec |1sec | 500msec | 250msec | Announce message rate parameters
the slave and duration of 125msec] [grant-period <60–1000>}
Announce message
transmission
Defining Delay Response delay-respond {rate [16pps |32pps | All slaves within a domain must use the same Delay
message rate requested by 64pps | 128pps] [grant-period <60– Response message rate parameters
the slave and duration of 1000>}
Delay Response message
transmission
Setting quality level quality-level { prc | ssu-a | ssu-b | The quality level values are according to the
type1-sec | type1-dnu | network type
type1-ssm-based }
quality-level { prs | stu | st2 | tnc | st3e
| st3 | smc | st4 | dus |
type2-ssm-based | prov }
quality-level { unk | type3-sec |
type3-dnu | type3-ssm-based }
Displaying Status
You can display current status of the 1588v2 slave entity.
 To display 1588v2 slave status:

• At the config>system>clock>recovered (main-a/1 or main-b/1)#prompt, enter
show status.
The 1588v2 master status is displayed.
ETX-5>config>system>clock>recovered(main-a/1)# show status
Clock State : Free Run
Indicated QL : Type-1 PRC
Clock Identity : 1
Active Master : 1 Ip Address : 30.30.30.30
Master Num : 1
IP : 30.30.30.30
PTSF : ACT

Clock Identity :
Received QL : Type-1 DNU
Granted Sync Rate (pps) : 64
Granted Sync Period (sec) : 0
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 0
Granted Delay Respond Rate (pps) : 64
Granted Delay Respond Period (sec) : 0
The 1588v2 slave status provides the following information
• Current state of the slave clock (free run, locked, acquisition, holdover)
• Indicated and received quality level
• Master clock identity, IP address and number
• PTSF (Packet Timing Signal Fail) indication. Its Active state indicates that the
1588v2 slave has not received a sync, delay respond or announce message
for 10 seconds.
• Granted sync, delay respond and announce rates and periods
You can display current statistics for 1588v2 slave entity.
 To display statistics:
• At the config>system>clock>recovered(main-a/1 or main-b/1)#prompt, enter
show statistics running or measured to display running or measured slave
statistics.
The 1588v2 slave running or measured statistics are displayed.
ETX-5>config>system>clock>recovered(main-a/1)# show statistics running
Running
-----------------------------------------------------------------------------
Unicast Announce Request : 2
Unicast Announce Accept : 1
Unicast Announce Reject : 0
Unicast Announce Timeout : 0
Unicast Sync Request : 2
Unicast Sync Accept : 4
Unicast Sync Reject : 0
Unicast Sync Timeout : 0
Unicast Delay Respond Request : 3
Unicast Delay Respond Accept : 1
Unicast Delay Respond Reject : 0
Unicast Delay Respond Timeout : 1
Rx Unicast Sync Miss Ordered : 0
No Sync Total Elapsed Time : 10
No Sync Elapsed Time : 0
No Announce Total Elapsed Time : 6
No Announce Elapsed Time : 0
No Delay Respond Total Elapsed Time : 11
No Delay Respond Elapsed Time : 0

Rx Sync Packets : 9595

Rx Sync Lost : 0
Rx Delay Respond Packets : 9467
Figure 9-10. 1588v2 Slave Running Statistics
ETX-5>config>system>clock>recovered(main-a/1)# show statistics measured
Measured
-----------------------------------------------------------------------------
Sync Rate Delay Respond Rate
Current : 128 128
Maximum : 128 128
Minimum : 128 128
Figure 9-11. 1588v2 Slave Measured Statistics
Table 9-7. 1588v2 Slave Running Statistic Counters
Counter Description
Unicast Announce Request Number of unicast announce messages sent by the slave
Unicast Announce Accept Number of unicast announce messages accepted by the slave
Unicast Announce Reject Number of unicast announce messages rejected by the slave
Unicast Announce Timeout Number of unicast announce messages that timed out
Unicast Sync Request Number of unicast sync messages sent by the slave
Unicast Sync Accept Number of unicast sync messages accepted by the slave
Unicast Sync Reject Number of unicast sync messages rejected by the slave
Unicast Sync Timeout Number of unicast sync messages that timed out
Unicast Delay Respond Request Number of unicast delay respond messages sent by the slave
Unicast Delay Respond Accept Number of unicast delay respond messages accepted by the slave
Unicast Delay Respond Reject Number of unicast delay respond messages rejected by the slave
Unicast Delay Respond Timeout Number of unicast delay respond messages that timed out
Rx Unicast Sync Miss Ordered Number of received unicast sync messaged that are misordered
No Sync Total Elapsed Time Total time in seconds during which sync messages were not received
No Sync Elapsed Time Time in seconds elapsed after the last received sync message
No Announce Total Elapsed Time Total time in seconds during which announce messages were not
received
No Announce Elapsed Time Time in seconds elapsed after the last received announce message
No Delay Respond Total Elapsed Total time in seconds during which delay respond messages were not
Time received
No Delay Respond Elapsed Time Time in seconds elapsed after the last received delay respond message
Rx Sync Packets Total number of received sync packets
Rx Sync Lost Total number of lost sync packets
Rx Delay Respond Packets Total number of received delay respond packets

Table 9-8. 1588v2 Slave Measured Statistic Counters
Counter Description
Current Sync Rate Current rate of sync messages

Maximum Sync Rate Maximum rate of sync messages
Minimum Sync Rate Minimum rate of sync messages
Current Delay Respond Rate Current rate of delay respond messages
Maximum Delay Respond Rate Maximum rate of delay respond messages
Minimum Delay Respond Rate Minimum rate of delay respond messages
Note
Delay respond rate counters are not available in time-frequency recovery mode.
detected.
Message Description
All Masters within slave module must be A 1588v2 slave cannot be disabled while it still has peer 1588v2
deleted masters attached to it
Configuration fail. Grant-period out of The grant period value is not within range (60–1000 sec)
range
Configuration fail. The minimum- The selected minimum expected value for Synchronization,
expected value cannot be higher than Announce or Delay Response messages is higher than the
the rate value configured message rate
Invalid IP Address The defined IP address is not valid
IP must be configured as a router LB The defined IP address is different from the router loopback
address interface address
Master number should be 1 or 2 only The peer 1588v2 master must be 1 or 2
Master still active A peer 1588v2 master cannot be disabled while it is active
Missing IP address configuration The maximum number of allowed 1588v2 slaves per chassis has
been exceeded
PTP domain is out of range The IP address must be defined before the 1588v2 slave can be
enable
PTP wait-to-restore is out of range The PTP domain number is not within range (4–23)
Recovered must be defined as none The PTP WTR value is not within range (0–720)
Recovered PTP must be in shutdown The 1588v2 clock cannot be changed from recovered to master
or vice versa, skipping the None state
Recovered PTP: The delay-respond rate A 1588v2 slave cannot be modified while it is active
must be equal or lower that the sync
rate

Configuring ToD Clock

ToD clock configuration process includes defining ToD clock parameters and
enabling/disabling ToD Y-cable redundancy.
 To configure ToD clock:

2. At the config>system>clock# prompt, enter tod[ main-a/1 | main-b/1 ].
The config>system>clock>tod(main-a/1 or main-b/1)# prompt is
displayed.
3. At the config>system>clock>tod(main-a/1 or main-b/1)#prompt, enter all
necessary commands according to the tasks listed below.
Activating ToD clock no shutdown shutdown deactivates the ToD clock
Defining ToD clock baud baudrate {2400bps | 4800bps |

rate 9600bps | 14400bps | 19200bps |
38400bps | 57600bps | 115200bps}
Assigning name to ToD name <tod_name > no name removes the ToD clock name
clock
Defining input interface for interface-type {rj-45 | mini-bnc} rj-45 – 1PPS is supplied via RJ-45 TOD connector
1PPS phase stream mini-bnc – 1PPS is supplied via mini BNC 1PPS
connector
Displaying ToD status show status
 To enable/disable ToD Y-cable redundancy:

1. Verify that both ToD clocks to be used in Y-cable redundancy are active and
have been configured with the same parameters (interface type, baud rate
etc).
2. At the config>system>clock# prompt, enter tod-y-cable to enable or no tod-
y-cable to disable the ToD Y-cable redundancy.
detected.
Message Description
TOD Y-cable must be disabled before ToD clock cannot be modified, when Y-cable redundancy is
changing TOD enabled
TOD must be in shutdown ToD clock cannot be modified if it is active (no shutdown)
Both TODs must be in no shutdown and To enable ToD Y-cable redundancy, configure both ToD clock to
have the same parameters the same parameters

Message Description
Both PTP 1588 must be the same: slave To use ToD Y-cable redundancy,1588v2 entities residing on two
or master main cards must be the same type: both master or both slave
Example
This example illustrates configuration of 1588v2 slave and master entities.
• Slave clock
 Router interface (RIF) – 1
 RIF IP address – 15.15.15.15/32
 Physical port – Ethernet port 3 on main card A
 Peer IP address – 30.30.30.30
 Slave entity IP address – 15.15.15.15
 Quality level – PRC
ETX-5
Port 1
Port 2
1588v2
Slave LB
Peer Master RIF 1
Clock Source
Entity
PSN 15.15.15.15/32
15.15.15.15 Router
Port 3
RIF 2
30.30.30.30
SVI
Port 4
Main Ethernet
Card A
Figure 9-12. Slave Clock Configuration
• Master clock
 Router interface (RIF) – 2
 RIF IP address – 16.16.16.16/32
 Physical port – Ethernet port 1 on main card B
 Master entity IP address – 16.16.16.16

 Sync rate – 128 pps
 To configure 1588v2 slave clock:
#***************************Adding_Loopback_RIF******************************
configure router 1 interface 1 loopback
address 15.15.15.15/32
no shutdown
exit all
#*********************************END****************************************
#***************************Configuring_Peer_Master**************************
configure peer 1 ip 30.30.30.30
exit all
#*********************************END****************************************
#**************************Configuring_1588v2_Slave**************************
configure system clock recovered main-a/3 ptp
ip-address 15.15.15.15
master 1
peer 1
quality-level prc
no shutdown
#*********************************End****************************************
 To verify that the slave is locked:

#***************************Displaying_Slave_Clock_Status********************
config>system>clock>recovered(1/ptp) show status
# Clock State: Frequency : Locked Time : Locked
Indicated QL : Type-1 DNU
Clock Identity : 0
Active Master : 1
Ip Address : 15.15.15.15
Master Num : 1
IP : 30.30.30.30
PTSF : NACT
Clock Identity :
Received QL : Type-1 DNU
Granted Sync Rate (pps) : 128
Granted Sync Period (sec) : 60
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 300
Granted Delay Respond Rate (pps) : 128
Granted Delay Respond Period (sec) : 300
#*********************************End****************************************
 To configure 1588v2 master clock:

#***************************Adding_Loopback_RIF******************************
configure router 1 interface 2 loopback
address 16.16.16.16/32
no shutdown
exit all

#*********************************END****************************************
#**************************Configuring_1588v2_Master*************************
configure system clock master main-b/1 ptp
ip-address 16.16.16.16
sync-rate 128pps
no shutdown
#*********************************End****************************************


Chapter 10
Administration
This chapter covers administrative tasks such as entering contact info, file
management, etc. It also includes a section with instructions for resetting the
unit.
10.1 Administrative Information

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

1. Navigate to configure system.
The config>system# prompt is displayed.
Assigning device name name <device-name> The device name has unlimited length, but if you
enter a name with more than 20 characters, the
prompt displays only the first 20 characters
followed by 0. For example, this command that
defines a 25-character device name:
ETX-5# config sys name
ETXETXETXETXETXETX-512345
results in this prompt that shows the first
20 characters, followed by 0:
ETXETXETXETXETXETX-50#
Specifying location location no location removes user-assigned location

<device-location>
Specifying contact person contact <contact-person> no contact removes user-assigned contact

information
Displaying device show device-information

information, MAC
address, and amount of
time device has been
running
ETX-5 Administrative Information 10-1

Chapter 10 Administration Installation and Operation Manual
 To configure device information:

• Device name – ETX-5-HQ
• Location – floor-8
• Contact –Engineer-1.
ETX-5# configure system
ETX-5>config>system# name ETX-5-HQ
ETX-5-HAC >config>system# location floor-8
ETX-5-HAC >config>system# contact Engineer-1
ETX-5-HAC >config>system# show device-information
Description : ETH NTU: Boot; 1.10, Hw: 0.0, Main Sw: 3.0, Back-up Sw: 3.0
Name : ETX-5-HQ
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-30-CC-9D
Engine Time : 000:00:04:10
10.2 Copying Files within ETX-5

You can copy files within the ETX-5 unit with the copy command. Figure 10-1
shows the commands that can copy configuration files in a visual diagram.
Figure 10-1. Commands that Copy Configuration Files
File Names in the Unit

ETX-5 uses the following reserved file names:
• factory-default – Contains the factory default settings
• running-config – Contains full configuration (default and user)
10-2 Copying Files within ETX-5 ETX-5

Installation and Operation Manual Chapter 10 Administration
• startup-config – Contains saved user configuration. You must save the file
startup-config; it is not automatically created. Refer to Saving the
Configuration for details on how to save the user configuration.
• user-default-config – Contains default user configuration. Refer to Saving the
Configuration for details on how to save the default user configuration.
• rollback-config –Contains configuration settings to be used if user
confirmation of loading startup-config file is not received.
• restore-point-config – Contains configuration saved during software
installation. System configuration can be restored from this file, if the
installation process fails.
• sw-pack-1, sw-pack-2, sw-pack-3, sw-pack-4 – Contain up to four software
images
• log –Alarm and event log
• mac-table – MAC address table
• ltm – Activity trace file for debug purpose.
You can copy files via the copy command, or via the commands shown in
Table 10-1.
Table 10-1. Commands That Copy Files
Command Level Copies… Manual Section
factory-default admin factory-default-config to startup-config Resetting to Factory Defaults

and resets device
user-default admin user-default-config to startup-config and Resetting to User Defaults

resets device
save global running-config to startup-config Saving the Configuration
software-confirm- admin running-config or any other user- Confirmation of Configuration

required specified configuration file to rollback- File in Chapter 3
config
 To copy files within the device:

• At the file# prompt, enter: copy <source-file> <dest-file>.
For example:
• Source file name – running-config
• Destination file name – startup-config.
ETX-5# file
ETX-5>file# copy running-config startup-config
 To display the last copy command result:

• At the file# prompt, enter: show copy.
ETX-5 Copying Files within ETX-5 10-3

ETX-5# show file copy

Network to Device, Transferring Data
Src: sftp://172.17.174.56/etx1_03_00b06.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Transferred : 665600 Bytes in: 16 seconds (41600 Bytes/Second)
 To view the copy command history:

• At the file# prompt, enter: show copy summary.
For example:
ETX-5>file# show copy summary
Direction Source Destination End Time Status
1 Local running-config user-default-conf 13-3-2011 Ended OK
14:6:51
2 Local running-config startup-config 13-3-2011 Ended OK
14:7:35
3 Dev to Net startup-config DB 13-3-2011 Ended OK
14:7:40
Displaying Files within ETX-5

The dir command is used to display the files within the device.
 To display the files:

• At the file# prompt, enter dir.
A list of the file names and types is displayed.
For example:
ETX-5>file# dir
Codes C - Configuration S - Software LO - Log O - Other
Name Type Size(Bytes) Creation Date Status
mac-table O -- 2012-01-02 Read Only

09:25:01 valid
sw-pack-1 S 70250901 2011-12-10 File In Use
05:58:01 valid
startup-config C 508671 2012-01-01 valid
16:08:11 valid
rollback-config C 509453 2012-01-01 valid
19:58:30 valid
factory-default-config C 34 2012-01-02 Read Only
09:25:01 valid
running-config C -- 2012-01-02 File In Use
11:19:24 valid
log LO 26598 2011-12-27 Read Only
15:48:10 valid
Total Bytes : 817209344 Free Bytes : 672849920

Displaying the List of Configuration Files and their Contents

You can display the list of existing configuration files, as well as contents of any
configuration and application files.
 To display the list of configuration and application files and their contents:
• At the file# prompt, enter the show command according to the table below.
Displaying the list of show configuration-files

configuration files
Displaying the factory-default- show factory-default-config

config file contents
Displaying the rollback-config show rollback-config

file contents
Displaying the startup-config show startup-config

file contents
Displaying the contents of all show sw-pack Application files contain

application files saved in the information on application
system software running on main and
I/O cards installed in the
chassis
Displaying the user-default- show user-default-config

config file contents
Example – Displaying the List of Configuration Files

ETX-5>file# show configuration-files
Configuration Last Modified Valid
-----------------------------------------------------------------------------
startup-config 2012.01.01 16:08:11 Yes
rollback-config 2012.01.01 19:58:30 Yes
factory-default-config 2012.01.02 09:25:01 Yes
running-config 2012.01.02 11:48:29 Yes
Device loaded from : startup-config
running-config has been modified since last time it was equal to startup-
config
Example – Displaying the Contents of startup-config File

ETX-5>file# show startup-config
# configuration file
exit all
configure
# Terminal Configuration
terminal
timeout forever
exit
# System Configuration
ETX-5 Copying Files within ETX-5 10-5

system
# Clock Configuration
clock
# Station Clock Configuration
station main-a/1
shutdown
name "Station Clk-5-1"
exit
station main-b/1
shutdown
more..
Example – Displaying the Contents of Application Files

ETX-5>file# show sw-pack
Name Version Creation Time Actual

------------------------------------------------------
sw-pack-1 1.00A9 2011-12-26 00:00:00 active
sw-pack-1 Size (Bytes) : 70250901

Type Name Version H/W Ver
Size
(Bytes)
------------------------------------------------------
main main.bin 1.00A9 1.1 29194087
eth1g eth1g.bin 1.00A9 1.1 9353713
stm1ch stm1ch.bin 1.00A9 1.1 15768873
eth2X10g eth2X10g.bin 1.00A9 1.1 15933988
Deleting Files
You can delete files. Before deleting the file, make sure the file is not in use. For
additional information on configuration files and the consequences of deleting,
refer to Configuration Files and Loading Sequence in Chapter 3.
 To delete a file:
1. At the file# prompt, enter: delete <file-name>.
You are prompted to confirm the deletion.
For example:
ETX-5# file
ETX-5>file# delete sw-pack-1
File will be erased. Are you sure?? [yes/no] _yes
2. Confirm the deletion.
Saving the Configuration

You must save your configuration if you wish to have it available after reboot, as
it is not saved automatically. You can save your configuration as outlined below.
 To save your current configuration in the startup-config file:

• At any level, enter save.

or
• At the file# prompt, enter copy running-config startup-config.
10.3 Date and Time

You can set the date and time for the ETX-5 internal real-time clock or use the
NTP server clock signal as a time/date reference. ETX-5 can synchronize with up
to ten servers, sending NTP requests to the servers at user-defined intervals.
You can set one of the active NTP servers as the preferred server, so that ETX-5
sends NTP requests to the preferred server. If there is no preferred server or if
the preferred server does not answer, then ETX-5 sends NTP requests to any
enabled servers.
Standards and MIBs

• DISMAN-SCHEDULE-MIB, RFC 3231
• IF-MIB, RFC 2863
• SNMPv2-MIB, RFC 3418
• RFC 4330.
Benefits
Simple Network Time Protocol (SNTP) synchronizes the internal clocks of network
devices to a single time reference source. SNTP provides 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.
Factory Defaults
The default configuration of the SNTP parameters is:
• No SNTP servers defined
• Polling interval set to 15 minutes.
When an SNTP server is defined, its default configuration is:
• IP address set to 0.0.0.0
• Not preferred.
SNTP is a time-maintenance protocol that helps synchronize networked
hardware. It is based on a server-client topology. A client (ETX-5) sets its system
date and time by retrieving this information from an SNTP server. The information
ETX-5 Date and Time 10-7

is used for time-stamping log file messages, SNMP traps, Syslog entries and so
on. SNTP uses Coordinated Universal Time (UTC) as a reference.
Requ
est Reference
Time Source
Resp PSN
ETX-5 onse
Request
est
Requ Response
SNTP
onse Server
Resp
ETX-5
Figure 10-2. SNTP Functionality
Transport Protocol
SNTP uses User Datagram Protocol (UDP) for its transport. The UDP port that has
been assigned to SNTP is 123, but devices and servers can be defined to use any
port for communication.
Client Operation Mode

SNTP client operates in one of the following modes:
• Unicast, sending requests to configured server addresses
• Broadcast, listening to an unsolicited broadcast address and learning
timestamps from any broadcast server sending messages to this address
The client checks each message received from an SNTP server by performing
sanity checks to verify it validity (SNTP server IP match, source/destination port
match etc).
Configuring 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 format date-format {yyyy-mm-dd | dd-mm-yyyy |

mm-dd-yyyy | yyyy-dd-mm}
Defining the date date <date> Date is according to the configured date
format
Defining the time zone relative to zone utc [<[{+|-}]hh[:mm]>] Allowed range of values:
Coordinated Universal Time (UTC) -12:00 to +12:00, in 30-minute increments
Defining the time time <hh:mm[:ss]>
10-8 Date and Time ETX-5

Displaying the Date and Time

 To display the date and time:
• From the system context (config>system), enter:
show date-and-time.
Example
 To set the date and time:
• Format = mm-dd-yyyy
• Date = May 17, 2011
• Time = 5:40pm
• Zone = UTC–4 hours and 30 minutes.
ETX-5#configure system date-and-time
ETX-5>config>system>date-time# date-format mm-dd-yyyy
ETX-5>config>system>date-time# date 05-17-2011
ETX-5>config>system>date-time# time 17:40
ETX-5>config>system>date-time# zone utc -04:30
ETX-5>config>system>date-time#
SNTP Configuration
 To configure SNTP parameters:
1. Navigate to config system date-and-time sntp.
The config>system>date-time>sntp# prompt is displayed.
Enabling ETX-5 to listen to NTP broadcast no broadcast disables

broadcast messages to obtain broadcast mode.
accurate timestamps
Setting the polling interval (in poll-interval interval <minutes> Allowed range is 1–1440
minutes) for SNTP requests
Defining and configuring SNTP server <server-id>

servers (refer to Defining SNTP
Servers and Configuring SNTP
Server Parameters)
Displaying SNTP status show status
Defining SNTP Servers

 To define an SNTP server:
ETX-5 Date and Time 10-9

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 Default.
3. Configure the SNTP server parameters as needed, as described in Configuring
SNTP Server Parameters.
Configuring SNTP Server Parameters

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

server
Setting SNTP server as the prefer no prefer removes preference

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

displaying result
Example
 To define SNTP server:

• Server ID = 1
• IP address = 192.1.1.1
• Preferred
ETX-5# configure system date-and-time sntp
ETX-5>config>system>date-time>sntp# server 1
ETX-5>config>system>date-time>sntp>server(1)# address 192.1.1.1
ETX-5>config>system>date-time>sntp>server(1)# prefer
ETX-5>config>system>date-time>sntp>server(1)# no shutdown
ETX-5>config>system>date-time>sntp>server(1)# query-server
Query Server Replay
-----------------------------------------------------------------------------
10-10 Date and Time ETX-5

Server : 192.1.1.1 UDP : 123

Date : 00-00-0000 Time : 00:00:00
Stratum : 0
ETX-5>config>system>date-time>sntp>server(1)# exit
ETX-5>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 --

ETX-5>config>system>date-time>sntp#
10.4 Displaying CPU Utilization Information

ETX-5 displays CPU utilization information for main card A and B. The information
is based on 1 second samples. The average, minimum and maximum values are
calculated for the period of time elapsed since the last power up or clear-cpu-
utilization command.
 To display CPU utilization information:

• In the config>system# prompt, enter show cpu-utilization, followed by one of
the following options:
 all – displays CPU utilization information for both main cards
 slot main-a – displays CPU utilization information for main card A
 slot main-b – displays CPU utilization information for main card B.
ETX-5>config>system show cpu-utilization all
CPU Utilization
-----------------------------------------------------------------------------
Slot Min Cur Max Average
(%) (%) (%) (%)
-----------------------------------------------------------------------------
main-a 0 14 100 12
main-b 0 0 0 0
 To clear CPU utilization information:

• In the config>system# prompt, enter clear cpu-utilization.
ETX-5 Displaying CPU Utilization Information 10-11

10.5 Displaying Login Banner

You can define a banner to be displayed before the login prompt for user name.
Note If you are accessing ETX-5 via SSH, the banner is printed between the user name
prompt and the password prompt.
 To define the banner:

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 ETX-5.

At the next login, the banner is displayed.
You can display the banner defined for ETX-5 by navigating to the file level and
entering show banner-text, as shown in the example below.
ETX-5# file
ETX-5>file# show banner-text
******* Authorized users only *******
Given the above banner file, the banner is displayed before the login as shown
below.
******* Authorized users only *******
user>
10.6 Displaying Memory Utilization Information

ETX-5 displays memory utilization information for main and I/O cards. The
information details the total and used amount of memory for the following:
• Kernel – Operating system processes
• User – Device application operations.
In addition, detailed memory usage screen presents information on memory
utilization for each real-time process (RTP), running on the main and I/O cards.
 To display general memory usage information:

• In the config>system# prompt, enter show memory.
ETX-5>config>system show memory
Kernel Kernel User User

Total (KB) Free (KB) Total (KB) Free (KB)
-----------------------------------------------------------------------------
main-a 307493968 200861328 557407357 257732608
1 33275248 5313432 55864529 3690496
10-12 Displaying Memory Utilization Information ETX-5

2 33496520 5603784 56236330 4120576
 To display detailed memory usage information:

• In the config>system# prompt, enter show memory-details.
ETX-5>config>system show memory-details
Slot : main-a
Kernel Total(KB) : 307493968 Free : 200861328
User Total (KB) : 557407357 Free : 257732608
RTP : rInfrastructure
Total (KB) : 2666672 Free : 16512
RTP : rCardManager
Total (KB) : 65280 Free : 60704
more..
10.7 Downloading/Uploading Files

You can download or upload files to the ETX-5 unit via SFTP. The following types
of files can be uploaded or downloaded:
• startup-config
• rollback-config
• user-default-config
• factory-default-config (upload only)
• log (upload only)
• sw-pack-1, -2, -3, -4
• mac-table (upload only)
• ltm_1 (upload only).
The maximum allowed values for SFTP parameters are:
• Username – 1 – 60 characters
• Password –1– 60 characters
• File name – 1–100 characters
• Port – 1–65535.
The SFTP protocol is used to provide secure file transfers via the device’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
ETX-5 Downloading/Uploading Files 10-13

computer. SFTP file transfers use Port 22. You must check that the firewall you
are using on the server computer allows communication through this port.
A variety of third-party applications offer SFTP server software. For more
information, refer to the documentation of these applications.
Application file is
transferred to
ETX-5
Ethernet
PC with an Active ETX-5

SFTP Server and
Application File
Figure 10-3. Downloading a Software Application File via SFTP
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
software 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 ETX2x 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
• 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.
• Configuration files should contain only printable ASCII characters (0x20-
Note
0x7E), <Enter> (0x0D), <Line Feed> (0x0A), and <Tab> (0x09).
Example – Download via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – ETX-5.img
10-14 Downloading/Uploading Files ETX-5

• Destination file name – sw-pack-1.

ETX-5# file
ETX-5>file# copy sftp://<admin>:<1234>@192.20.20.20/ETX-5.img sw-pack-1
Note
Destination file name can be only sw-pack-1, sw-pack-2, sw-pack-3 or sw-pack-4.
Example – Upload via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – startup-config
• Destination file name –db1conf.cfg
ETX-5# file
ETX-5>file# copy startup-config
sftp://<admin>:<1234>@192.20.20.20/db1conf.cfg
Note
Source file name can be one of the following: startup-config, user-default-config
or rollback-config.
10.8 Inventory
The ETX-5 inventory table displays the unit’s components, hardware, software
and firmware revisions. You can display an inventory table that shows all installed
components, and you can display more detailed information for each component.
In addition, you can display manufacture information on items installed in specific
chassis slots, their serial numbers, software and hardware revisions and number
of defined MAC addresses.
Displaying Inventory Information

The ETX-5 inventory table displays the unit’s components, hardware, software
and firmware revisions.
 To display the inventory table:

• In the config>chassis# prompt, enter show summary-inventory.
The inventory table is displayed (refer to Example to see a typical
inventory table output).
Displaying Inventory Component Information

You can display more information for each installed inventory component. To do
this, enter the inventory level with the corresponding inventory component index.
The component index is determined by the position of the corresponding row in
ETX-5 Inventory 10-15

the output of show inventory-summary, which changes according to what is

installed in the unit.
 To display the inventory component information:

1. Navigate to configure chassis inventory <index>.
Information for the corresponding inventory component is displayed
(refer to Table 10-2 for information on the parameters).
Table 10-2. Inventory Parameters

Description Description of component type, in the form:
Device_name.< Physical Class>, e.g. ETX-5.PortSlot
Contained In Index of the component that contains the component for which
information is being displayed. This is 0 for the chassis, as it is not
contained in any component, and 1 for all other components, as they are
all contained in the chassis.
Physical Class Class of component
Possible values: Chassis, Backplane, Container, Module, Port
Relative Position Contains the relative position of this component among other similar
components
Name Name of component
HW Rev Hardware revision (relevant only for chassis)
SW Rev Software revision (relevant only for chassis)
FW Rev Firmware revision (relevant only for chassis)
Serial No. Serial number (blank if unknown for component)
MFG Name Manufacturer name (blank if unknown for component)
Module Name Model name (blank if unknown for component)
Alias Alias name for component
Asset ID Identification information for component
FRU Indicates whether this component is a field replaceable unit that can be
replaced on site
Displaying Manufacture Information

You can display manufacture information on items installed in specific chassis
slots, their serial numbers, software and hardware revisions and number of
defined MAC addresses.
 To display manufacture information:

• At the config>chassis# prompt, enter show manufacture-info slot
<slot_number> or show manufacture-info all to display information on items
installed in a specific slot, or all existing items, respectively.
ETX-5# configure chassis
ETX-5>config>chassis# show manufacture-info slot 1
10-16 Inventory ETX-5

Slot Type Serial Number HW Ver FW Ver
Main-A Main 10GEx4 0.0 2.0
Shelf Type : N/A

Serial Number :
HW Version : 0.0
FW Version : 2.0
Number of MACs : 0
Setting Administrative Inventory Information

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

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

component 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> no asset-id removes the asset
to the component (usually for ID
removable physical components)
Assigning vendor-specific serial serial-number <string> no serial-number removes the

number to the component serial number
Example
 To display the following inventory information:
• Inventory table
• Inventory information for the ETX-5 chassis.
ETX-5# config>chassis# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW Ver
-----------------------------------------------------------------------------
1001 Chassis AC-chassi N/A N/A N/A
ETX-5 Inventory 10-17

2001 Backplane Backplane 0.0 N/A N/A

3001 Container 1 N/A N/A N/A
3005 Container main-a N/A N/A N/A
3006 Container main-b N/A N/A N/A
3007 Container Slot 5 Port 1 N/A N/A N/A
3095 Container AC Slot N/A N/A N/A
3097 Container FAN N/A N/A N/A
4001 Power Supply PS_AC 1 0.0 N/A N/A
4003 Fan FAN 0.0 N/A N/A
5002 Module IO Card 2 65535.0 1.00A10T1 2.0
5005 Module Main Card A
5006 Module Main Card B 0.0 1.00A10T1 2.0
7005 Port Ethernet port main-b/1 N/A N/A N/A
7010 Port RS_232 Control Port N/A N/A N/A
7011 Port Clock RJ45 Port N/A N/A N/A
7012 Port Clock BNC Port N/A N/A N/A
7013 Port Time Of Day BNC Port N/A N/A N/A
7014 Port Time Of Day RS422 Port N/A N/A N/A
7015 Port MNG Port N/A N/A N/A
7041 Port Ethernet Port 2/1 N/A N/A N/A

ETX-5# config>chassis# inventory 1001
ETX-5# config>chassis>inventory(1001)# show status
Description : ETX-5300A.AC-chassis
Contained In : 0
Physical Class : Chassis
Relative Position : 0
Name : AC-chassi
HW Ver : N/A
SW Ver : N/A
FW Ver : N/A
10-18 Inventory ETX-5

Serial Number :
MFG Name : RAD
Module Name : ETX-5300A-AC
Alias :
Asset ID :
FRU : True
10.9 Resetting ETX-5

ETX-5 supports the following types of reset:
• Reset to factory defaults
• Reset to prior-to-shipment state
• Reset to user defaults
• Overall reset (restart, reboot) of the device.
Resetting to Factory Defaults

 To reset ETX-5 to factory defaults:
1. In the device prompt, enter admin.
The admin> prompt appears.
2. 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]
3. Enter yes to confirm resetting to factory defaults.
The factory-default file is copied to the startup -config file. Now at the
device startup, the factory defaults are loaded.
Resetting to Prior-to-Shipment State

Unlike resetting to factory defaults which loads device setting stored in the
factory-default file, this procedure deletes the startup-config file and after
reboot loads the user-default-config file. If the user-default-config file does not
exist, ETX-5 loads the factory-default-config file.
Caution Use discretion when executing the factory-default-all command. RAD

recommends utilizing less disruptive factory-default or user-default commands
instead. Be advised that resetting ETX-5 to the prior-to-shipment state may
adversely affect its SNMP connectivity. If the network management link is lost,
remove ETX-5 from the SNMP map and add it again to restore the connection.
 To reset ETX-5 to the prior-to-shipment state:

ETX-5 Resetting ETX-5 10-19


2. Enter factory-default-all.
The device will delete its entire database and reboot!
3. Enter yes to confirm resetting to the prior-to-shipment state.
ETX-5 clears all information, including log files, except for factory-default-
config, user-default-config, licenses and the application software.
Resetting to User Defaults

 To reset ETX-5 to user defaults:
2. Enter user-default.
Current configuration will be erased and device will reboot with user
default configuration. Are you sure? [yes/no] _
3. Enter yes to confirm resetting to user defaults.
The user-default config file is copied to the startup-config file. Now at
the device startup, the user defaults are loaded.
Rebooting the ETX-5 Chassis

Chassis reboot is a service-disruptive procedure, which resets all ETX-5
components, including active/standby main and I/O cards.
 To reboot the chassis:

1. At the admin# prompt, enter the reboot command.
Device will reboot. All configuration since last save will be discarded. Are
you sure? [yes/no]
2. Enter yes to confirm the reset.
The chassis restarts.
Resetting the Module

Use the following procedure to reset a module installed in a specified slot.
Note Resetting a module will temporarily disrupt services supported by that module.
 To reset a module:
1. Navigate to configure slot <slot>.
The config>slot<slot># prompt is displayed.
10-20 Resetting ETX-5 ETX-5

2. Enter reset.
Card will reset. Are you sure?? [yes/no]
3. Enter yes to confirm the reset.
The module restarts.
10.10 Scheduling
You can schedule the execution of CLI commands at a future date and time. In
addition, you can schedule adjusting the device system time for the start and end
of summer time.
Benefits
You can ensure the execution of CLI commands, and adjusting device time to
reflect the start and end of summer time, at a specific date and time.
Factory Defaults
By default, no scheduling is configured.
The default value for summer time offset is 60 minutes.
Scheduling Commands
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 ETX-5 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 in the CLI root level.
ETX-5 tests the command specified to be 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 schedule 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 permanent ETX-5 memory; it is deleted at
device reboot whether or not it was executed.
• At <date-and-time> – Executed once at the specified date and time. This type
of schedule can be optionally saved in permanent memory, in order to be
available after device reboot.
ETX-5 Scheduling 10-21

Note Schedules for date and time are saved in system local time. If the local time
changes, <Product> does not modify the schedules to compensate for the
change, therefore changing the time could cause schedules to be executed twice
or not executed at all.
Schedules are marked as finished after they are executed.

When executing scheduled commands, ETX-5 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.
Scheduling Summer Time

You can specify when the device local system time should reflect the start of
summer time by adding an offset, and when it should reflect the end of summer
time by subtracting the offset.
The summer time can be scheduled in one of the following ways:
• One shot – Summer time starts and ends once, at a specified date and time
(e.g. 15 October).
• Recurring – Summer 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 summer time schedule is saved in permanent memory, in order to be
available after device reboot.
Note ETX-5 logs the start and end of summer time with the events
summer_time_started and summer_time_ended, respectively. Each event is also
sent as an SNMP notification to management stations.
Configuring Command Scheduling
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 configure schedules:
• 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> [permanent]
10-22 Scheduling ETX-5

The schedule is saved with its name set to <name> (in permanent
memory if permanent 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.
 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
Configuring Summer Time Scheduling

When you configure summer-time scheduling, the first set of parameters in the
commands specifies when summer time starts, and the second set of parameters
specifies when summer time ends.
 To configure summer time:

• Navigate to the system date-and-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 which week of the month.
For both schedule types, <offset> specifies (in minutes) the time to add at
summer time start, or subtract at summer time end. Its range is 1–1440.
 To delete summer-time scheduling:

• Navigate to the system date-and-time level and enter:
no summer-time

Viewing Scheduling Information

You can view scheduling information with or without the details of scheduled
commands.
 To view scheduling without command details:

• Navigate to the admin scheduler level and enter:
show scheduler
ETX-5# admin scheduler
ETX-5>admin>scheduler# show scheduler
Current Time: 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
ETX-5# admin scheduler
ETX-5>admin>scheduler# show scheduler-details
Current Time: 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

Table 10-3. Scheduling Display Parameters
Current Time 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 summer time scheduling, displays summer time start date and time
End (Date) For one-shot summer time scheduling, displays summer time end date and time
Start (Recurring) For recurring summer time scheduling, displays the configured week of the month,
weekday, month, and time for summer time start
End (Recurring) For recurring summer time scheduling, displays the configured week of the month,
weekday, month, and time for summer time end
Start For recurring summer time scheduling:

• If the device is currently not in summer time, displays the next scheduled date and
time for summer time to start
• If the device is currently in summer time, displays the date and time at which the
summer time started
End For recurring summer time scheduling, displays the next scheduled date and time for
summer time end
Examples
 To schedule copying log file in two hours:
schedule sched-copy-2hrs in 120 “copy log tftp://1.1.1.1”

 To schedule copying 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 summer time starting March 27 2015 at 1:00 and ending October 27
2015 at 2:00:
exit all
configure system date-and-time
summer-time date march 27 2015 01:00 october 27 02:00
save
 To schedule summer time starting on the first Friday in March at 2:00 and ending
on the last Sunday in October at 3:00:
exit all
configure system date-and-time
summer-time recurring 1 friday march 02:00 last sunday october 03:00
save
The following table lists the messages generated by the device when a
configuration error is detected.
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; ETX-5 does not allow the
may not be scheduled the command to schedule logout command to be scheduled
Summer-time already You entered the summer-time command Delete the existing summer-time
configured to configure summer time, but the configuration; and then re-enter the
scheduling of summer-time has already summer-time command
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

10.11 Technical Support Status

The show tech support command outputs all or part of device’s status and/or
statistics into a file. The command script executes a list of show commands and
outputs the results to the terminal by default. If the file option is specified, the
output is saved in the script-result file.
Benefits
The show tech-support command provides a easy way to gather device
information for troubleshooting and assisting technical support.
Default show Commands

By default, the show tech-support command includes a fixed list of command
output. The default list includes the following commands:
• show system-date
• show device-information
• show card-summary
• show summary : inventory
• File> dir
• show sw-pack
• show copy
• show summary : port
• show summary : LAG (TBD, not exist)
• show svi
• show service
• show summary : flows
• show summary : oam-cfm
• show summary : pw
• show status : clock domain1
• show status : main-card
• show summary : erp
• show arp-table
• show routing-table
• show (management) : users
• show active alarms
• show debug meta MIB tables
ETX-5 Technical Support Status 10-27

Custom show tech-support Command List

You can download a customized file, containing a custom list of CLI commands, in
a user-script. When the file option is selected in the show tech-support
command, the user script is executed instead of the default script.
Managing user-script Files

You can manage user-script files for the show tech-support command just as you
do any other user-script.
 To display user-script file contents

Navigate to config>system.
4. At the CLI prompt, enter show user-script.
5. config>system# show tech-support file
 To execute a user-script:
• At the CLI prompt, enter exec user-script [file|terminal].
• By default, the output (the executed commands and their output) is sent to
the terminal screen.
• If file is chosen, the output is saved in the script-result file.
 To Upload a user-script file:

• At the CLI prompt, enter copy user-script tftp://…/my_file.txt.
 To download a user-script file:

• At the CLI prompt, enter copy tftp://…/my_file.txt user-script.
 To delete a user-script file:

• At the CLI prompt, enter delete user-script.
Show tech-support Command Output File

By default the output of CLI commands and user-script files is directed to the
terminal. However, you can save the output in a script-result file. The script-result
file is automatically cleared when the show tech-support or exec user-script file
command is invoked, so if you want to preserve the contents of this file, upload
it to a storage device.
The script-result file is size limited to ???? and zipped on-the-fly during creation.
It is unzipped on-the-fly when displayed in the terminal.
Managing user-script Files

You can display, upload and delete a script-result file.
 To display user-script file contents

• At the CLI prompt, enter show user-script.
10-28 Technical Support Status ETX-5

 To Upload a user-script file:

• At the CLI prompt, enter copy user-script tftp://…/my_file.txt.
 To delete a user-script file:

• At the CLI prompt, enter delete user-script.
Examples
Below is an example of the show tech-support command output directed to the
terminal. When the output is directed at a file, the output is the same.
bridge_1_2>config>system# show tech-support
# Execute tech-support-script
# 2015-10-26 08:58:45 UTC +00:00, system uptime: 315444 seconds

show configure system system-date
2015-10-26 08:58:45 UTC +00:00

show configure system device-information
Description : ETX-5300A HW Version: 0.0, SW Version: 2.6.0(0.24)
Name : bridge_1_2
Location : The location of this device
Contact : Name of contact person
MAC Address : 00-20-D2-F0-62-58
Engine Time : 3 days, 14:52:35

show configure cards-summary
-----------------------------------------------------------------------------
1 GBEx20 SFP Empty Down Down Standalone
2 10Gx2 XFP 10Gx2 XFP Up Up Standalone

show configure chassis summary-inventory
-----------------------------------------------------------------------------
1001 Chassis AC-chassis 2.6.0(0.24)
2001 Backplane Backplane 0.0/A
3001 Container slot 1
3005 Container slot a
3006 Container slot b
3007 Container Slot 5 Port 1


3095 Container AC Slot 1
3096 Container AC Slot 2
3097 Container FAN
4001 Power Supply PS_AC 1 0.1/A
4002 Power Supply PS_AC 2 0.1/A
4003 Fan FAN 0.0/B
5001 Module IO Card 1 255.255/- 2.6.0(0.16) 0.00/02.02
5002 Module IO Card 2 255.255/- 2.6.0(0.16) 0.00/02.02
5005 Module Main Card A 0.0/H 2.6.0(0.26) 02.02
5006 Module Main Card B 0.0/H 2.6.0(0.26) 00.00
7001 Port Etherent port main-a/1
7005 Port Etherent port main-b/1
7008 Port Etherent port main-b/4
7009 Port MNG Port
7010 Port RS_232 Control Port
7011 Port Clock RJ45 Port
7012 Port Clock BNC Port
7013 Port Time Of Day BNC Port
7014 Port Time Of Day RJ45 Port
7015 Port MNG Port
7016 Port RS_232 Control Port
7017 Port Clock RJ45 Port
7018 Port Clock BNC Port
7019 Port Time Of Day BNC Port
7020 Port Time Of Day RJ45 Port
7041 Port Ethernet Port 2/1
7042 Port Ethernet Port 2/2

file dir
Codes: C-Configuration S-Software L-License LO-Log O-Other B-Banner
db-config LO -- 2015-10-22 File In Use

17:22:09
db-schema LO -- 2015-10-22 Read Only

17:22:09
mac-table LO -- 2015-10-22 Read Only
17:22:09
pm-0 LO 18 2015-10-22 File In Use
17:23:43
schedule-log LO 5000 2015-10-22 Read Only
17:22:09 File In Use
sw-pack-3 S 126336553 2015-10-22 File In Use
13:54:28
startup-config C 19835 2015-10-22
18:04:45
factory-default-config C 694 2015-10-22 Read Only
17:22:10
running-config C -- 2015-10-22 File In Use
18:07:41
log LO 2640 2015-07-26 Read Only
06:13:41
Bytes Available for PM : 11199982

show file sw-pack
-----------------------------------------------------------------------------
sw-pack-3 2.6.0(0.24) 2015-10-22 17:00:00 active

Size
(Bytes)
-----------------------------------------------------------------------------
main main.bin 2.6.0(0.26) 1.1 43136151
eth1g eth1g.bin 2.6.0(0.16) 1.1 5166751
stm1ch stm1ch.bin 2.6.0(0.13) 1.1 20611800
eth2X10g eth2X10g.bin 2.6.0(0.16) 1.1 5181179
stm4ch stm4ch.bin 2.6.0(0.13) 1.1 18353383
arria360_varria360_v1_20x2.4.0(0.01) 1.1 8627548
arria360_varria360_v2_20x2.4.0(0.01) 1.1 8632320
arria360_varria360_v1_2x12.4.0(0.01) 1.1 8306529
arria360_varria360_v2_2x12.4.0(0.01) 1.1 8320652

show file copy
Device to Network, Ended OK
Src: startup-config
Dst: tftp://.../RSTP_1
Started: 2015-10-22 18:08:33, Ended 2015-10-22 18:08:33
Transferred:19835 bytes in:1 secs(19835 bytes/sec)

show configure port summary
Port Admin Speed Tx Packets Rx Packets

Oper Error Packets
Ethernet main-a/0 Enabled 1G 10 1841365
Up 10
Up 74

Not Prsnt 0
Not Prsnt 0
Not Prsnt 0
Ethernet main-b/0 Enabled 1G 0 1840254
Up 0
Up 0
Not Prsnt 0
Not Prsnt 0
Up 0
Ethernet 2/1 Enabled 10G 40094527 51314951
Up 0
Ethernet 2/2 Enabled 10G 51228654 41173771
Up 0
Station Clk main-a/1 Disabled -- N/A N/A
Down N/A
Station Clk main-b/1 Disabled -- N/A N/A
Down N/A
SAG 2/1 Enabled -- N/A N/A
Up N/A
SAG 2/2 Enabled -- N/A N/A
Up N/A
TOD main-a/1 Disabled -- N/A N/A
Up N/A
TOD main-b/1 Disabled -- N/A N/A
Up N/A
SVI 1 Enabled -- N/A N/A
Up N/A
Up N/A
Up N/A
Up N/A
Up N/A
Up N/A
SAP 2/1/1 Enabled -- N/A N/A
Up N/A
Up N/A
Up N/A
Up N/A
Up N/A

show configure port svi-summary
SVI Number Type Admin Oper MAC Address Bound to
-----------------------------------------------------------------------------
1 Bridge Enabled Up 00-20-D2-F0-62-1D Bridge Port 1/1


4000 Router Enabled Up 00-20-D2-F0-62-87 Router 1/128

show configure service-summary

show configure flows summary brief
Name Ingress Tx
Admin | Oper | Classification Egress Rx
mng_access_default_in MNG ETH main-a/0 0

Ena | Up | classutg SVI 4000 0
mng_access_default_out SVI 4000 0

Ena | Up | classall MNG ETH main-a/0 0
4_1_1 SVI 4 40791862

Ena | Up | 100 Ethernet 2/1 40791862
5 Ethernet 2/2 40515084

Ena | Up | 100 SAP 2/2/1 40515084
1 Ethernet main-a/1 40094326

Ena | Up | 100 SVI 1 40094326
1_1 SVI 1 51783086

2 Ethernet main-b/1 28719711

Ena | Up | 100 SVI 2 28719711
2_1 SVI 2 24587303

Ena | Up | 100 Ethernet main-b/1 24587303
3 Ethernet main-b/4 36232044

Ena | Up | 100 SVI 3 36232044
3_1 SVI 3 51324873

Ena | Up | 100 Ethernet main-b/4 51324873
4 Ethernet 2/1 50403349

Ena | Up | 100 SAP 2/1/1 50403349
4_1 SAP 2/1/1 51157461

Ena | Up | 100 SVI 4 51157461
5_1 SAP 2/2/1 41172462

Ena | Up | 100 SVI 5 41172462
5_1_1 SVI 5 51071708

Ena | Up | 100 Ethernet 2/2 51071708
A1_l2cp Ethernet main-a/1 0

Dis | Down | utg Ethernet main-a/4 0
B1_l2cp Ethernet main-b/1 0

Dis | Down | utg Ethernet main-b/3 0

b4_l2cp Ethernet main-b/4 0

Dis | Down | utg Ethernet main-b/3 0
2/1_l2cp Ethernet 2/1 0

Dis | Down | utg SAP 2/1/10 0
2/1_l2cp_1 SAP 2/1/10 0

Dis | Down | all Ethernet main-a/4 0
2/2_l2cp Ethernet 2/2 0

Dis | Down | utg SAP 2/2/10 0
2/2_l2cp_1 SAP 2/2/10 0

Dis | Down | all Ethernet main-a/4 0

show configure oam cfm summary all
MEP
-----------------------------------------------------------------------------
Index MD Name Level Port Classification Admin
MA Name Vlan OK/RMEP
MIP
-----------------------------------------------------------------------------
Index MD Name Level Port Admin

show configure pwe summary

show configure system clock domain 1 status
System Clock Source : 0 State : Freerun Quality : ST3
Station Out Clock Source : 0 State : Unlocked
Force Switch : InActive
T4 is derived from T0 : Active

show configure slot main-a status
Actual Type : Main 10GbEx4
Provisioned Type : Main 10GbEx4
Status Details : OK
Status Details Specific : Ready Complete
Software Version : 2.6.0(0.26)

show configure slot main-b status
Actual Type : Main 10GbEx4
Provisioned Type : Main 10GbEx4
Status Details : OK
Status Details Specific : Ready Complete

show configure protection erp-summary

Ring Type R-APS Bridge East East West West State

Port Physical Port Physical
-----------------------------------------------------------------------------

show configure router 1 arp-table
IP Address MAC Address Status
-----------------------------------------------------------------------------
172.18.92.1 E0-2F-6D-19-CA-C6 Dynamic
172.18.92.89 AC-16-2D-08-5E-F9 Dynamic
172.18.92.216 B4-B5-2F-B9-48-30 Dynamic

show configure router 1 routing-table
IP Address/Prefix Length Next Hop Interface Protocol Metric
-----------------------------------------------------------------------------
169.254.0.0/16 0.0.0.0 128 Local 0
172.18.92.0/24 0.0.0.0 128 Local 0
IPv6 Address/Prefix Length via Next Hop Interface Protocol Metric

-----------------------------------------------------------------------------

show configure management users
Num User Access Level Source IP Address
-----------------------------------------------------------------------------
1. su Su Terminal 0.0.0.0

show configure reporting active-alarms
Total : 6 Critical : 1 Major : 5 Minor : 0
Total Masked : 0 Critical : 0 Major : 0 Minor : 0
1 Ethernet main-a/2 sfp_removed Maj Unmasked

4 Ethernet main-b/2 sfp_removed Maj Unmasked
5 Ethernet main-b/3 sfp_removed Maj Unmasked
6 Power Supply 2 power_delivery_failure Crt Unmasked
bridge_1_2>config>system#


Chapter 11
Monitoring and
Diagnostics
This chapter explains fault management procedures supported by ETX-5. It
presents the following information:
• Detecting Problems
• Handling Events
• Running Diagnostic Tests
• Y.1564 Ethernet Service Activation Test
• OAM EFM
• OAM CFM
• Port/VLAN Mirroring
• Quality of Service
• Frequently Asked Questions (FAQs)
• Technical Support
11.1 Detecting Problems

To detect problems on the hardware level, you can, for example, run the self-test
and monitor the LED behavior. On the software level, you can follow statistical
counters and events and errors returned by the system.
Indicators
ETX-5 cards and the ETX-5 chassis itself have various status indicators that can
be used to identify problems.
Refer to Chapter 3 of this manual for details regarding the functions and
indications of each system indicator.
Alarms and Traps

ETX-5 generates various alarms that can be displayed at a supervision terminal,
and sends alarm traps to management stations so that operators can identify
problems.
ETX-5 Handling Events 11-1

Chapter 11 Monitoring and Diagnostics Installation and Operation Manual
ETX-5 maintains a cyclic event log file that stores up to 5000 time-stamped
events. In addition, an internal system log agent can send all reported events to a
centralized repository or remote server.
Statistic Counters
ETX-5 collects statistics per physical and logical ports (see the list below) and per
connection in 15-minute intervals. This enables the network operator to monitor
the transmission performance, and thus the quality of service provided to users,
as well as identify transmission problems. Performance parameters for all the
active entities are continuously collected during equipment operation.
Statistics for the last 24 hours are stored in the device and can be retrieved at
the network management station.
Statistic counters provide information on possible abnormal behavior and failures.
Configuration Error Messages

ETX-5 includes an extensive subsystem that checks the validity of the user’s
configuration activities, and reports any conflicts and errors. These error
messages are referred to as “sanity errors”, because they are detected by the
so-called sanity check that is automatically performed to confirm proper
configuration of the equipment. For further information, refer to the relevant
sections in the configuration chapters.
11.2 Handling Events

Reported events can be events, traps and alarms. The difference between them
is as follows:
• Alarm. A message that reports a failure. Alarm is a persistent indication of
fault of an entity, which may be the device itself or any of its components.
• Event. An occurrence that may be of interest, such as a fault, a change in
status, a crossed threshold, or an external input to the system.
• Trap. An SNMP message issued by an agent that reports an alarm or event.
The term trap refers to the SNMPv3 notification. The SNMP version is usually
omitted, unless it is important to specify it. Traps may be generated and sent
as a result of event or alarm.
Alarms and events have the following properties:
• Source –An entity for which alarms and events can be generated. The source
consists of a source ID, source type (e.g., system, fan, Ethernet), and source
name.
• ID – Unique numeric identification of the alarm/event
• Name – Unique alphanumeric identification of the alarm/event, of up to
32 characters
11-2 Handling Events ETX-5

Installation and Operation Manual Chapter 11 Monitoring and Diagnostics
• Description –Alphanumeric description that provides details about the

alarm/event
• Severity (alarms only) – Critical, Major, or Minor.
Masking
Alarms and events can be masked per source type, source ID, or minimum
severity. When masking by source type (such as Ethernet) or source ID (such as
Ethernet port 1 on card in slot 1), choose a specific alarm or event, or apply the
change to all the alarms and events of the selected source type or ID.
When masking an alarm/event, you can:
• Prevent the alarm/event from being written to the history log, sent to Syslog
servers, and displayed in the default view of the active alarms table
• Prevent any corresponding traps from being sent to management stations,
regardless of masking in the SNMP manager configuration
• Deactivate alarm reporting via LED and alarm relay.
When an alarm/event is not masked, any corresponding traps are sent only to
management station for which the traps are not masked in the SNMP manager
configuration. In addition, you can:
• Change alarm severity
• Mask a specific reporting method
• Mask alarms per their severity.
You can also acknowledge alarm logs. The last acknowledgement time is recorded
by ETX-5. When displaying the log, only entries entered after the last
acknowledgment time are displayed (or calculated, as for the brief log). This
action does not delete any data from the log, and you can also display
acknowledged data by using a designated keyword.
Alarm Buffer
ETX-5 continuously monitors critical signals and signal processing functions. In
addition, it can monitor an external alarm line, connected to the ALARM
connector.
If a problem is detected, ETX-5 generates time-stamped alarm messages. These
messages are explained below.
Internally, the ETX-5 stores alarms in an alarm buffer. The alarm buffer can store
up to 5000 alarm messages, together with their time-stamps. The alarm history
buffer is organized as a FIFO queue; after 5000 alarms have been written into the
buffer, new alarms overwrite the oldest alarms.
Alarm messages can also be sent automatically as traps to the user-specified
network management stations.
The alarms can be read on-line by the network administrator using the network
management station, a Telnet host, or a supervision terminal. The network
administrator can then use the various diagnostic tests to determine the causes of
the alarm messages and to restore the system to normal operation.

When ETX-5 is powered down, the alarm messages are not erased. When using
the terminal, a Web browser or a Telnet host, you can also clear (delete) the
alarms stored in this buffer after reading them.
Alarm Relays
In addition to the alarm reporting facility, ETX-5 has alarm relays with floating
change-over contacts for indicating the presence of critical, major and minor
alarms. Each relay changes state whenever the first alarm is detected, and
returns to its normal state when all the alarms of the corresponding severity
disappear.
The relay contacts can be used to report internal system alarms to outside
indicators, e.g., lights, buzzers, bells, located on an alarm bay or remote
monitoring panel.
Configuring Alarm Reporting

This section describes how to configure alarm/event properties and mask them
and rebuild active alarms.
 To configure alarm/event properties:

1. Navigate to configure reporting.
The config>reporting# prompt is displayed.
Configuring alarm input alarm-input <port-number> [active {high | low | high – Active alarm input is
off}] [description <description>] indicated by high voltage
low – Active alarm input is
indicated by low voltage
off – Alarm input is disabled

Masking alarm/event from a alarm-source-attribute <source-type> Use the no form to mask

specific source, defining [<source-id>] alarm <alarm-list> [severity alarms/events. The following
alarm severity, and masking {critical | major | minor}] [log] [snmp-trap] apply:
reporting methods, and [led-relay] [popup] [vtypopup] • If a trap is masked according
popups alarm-source-attribute<source-type> to alarm/event attribute, it is
Note: Severity and LED- [<source-id>] event <alarm-list> [log] not sent to any management
Relay apply only to alarms. [snmp-trap] [popup] [vtypopup] 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.
popup setting controls popup
behavior in serial management
sessions.
vtypopup setting controls popup
behavior in Telnet/SSH
management sessions.
Masking alarm/event from a alarm-source-type-attribute <source-type> Use the no form to mask

specific source type, alarm <alarm-list> [severity {critical | major | alarms/events. The following
defining alarm severity, and minor}] [log] [snmp-trap] [led-relay] [popup] apply:
masking reporting methods, [vtypopup] • If a trap is masked according
and popups alarm-source-type-attribute <source-type> to alarm/event attribute, it is
Note: Severity, LED and LED- event <alarm-list> [log] [snmp-trap] [popup] not sent to any management
Relay apply only to alarms. [vtypopup] 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.
Masking and controlling mask-minimum-severity [log {critical | major | Masking a minimum severity
popup behavior per alarm minor}] [snmp-trap {critical | major | minor}] means that lower severities are
per severity [led-relay {critical | major | minor}] [popup also masked
{critical | major | minor | event}] [vty-popup
{critical | major | minor | event}]
no mask-minimum-severity [log] [snmp-trap
[led-relay] [popup] [vtypopup]

Rebuilding active alarm table active-alarm-rebuild [send-traps] To ensure that no active alarms
from scratch, and, optionally are lost due to a system failure,
resending traps for all open the user can rebuild the active
alarms alarm table.
The optional traps sent by the
system have an indication that
are sent because of the
configuration change.
Acknowledging the logs acknowledge {log | brief-log | all-logs}
Defining method of log-file-timestamp-type {utc | local} utc – Alarms and events are
timestamping alarms and timestamped according to UTC
events in the uploaded log local – Alarms and events are
file timestamped according to local
time
Log file time type log-file-timestamp-type {utc|local} Time in log display in local time
or in UTC time
Displaying alarms show

See Working with the Alarm and
Event Logs
Note
If alarm/event is masked using one of the masking commands
(alarm-source-attribute, alarm-source-type-attribute, mask-minimum-severity),
there is no need to repeat the procedure using the other commands.
Examples
 To mask alarm for a specific source type:

• Source type – All E1s
• Alarm – excessive-bpv
• Reporting methods – log
ETX-5>config# reporting
ETX-5>config>reporting# alarm-source-type-attribute e1
excessive-bpv log

 To mask event for a specific source:

• Source type –E1 1 in port 1 on card in slot 1
• Event – css-path-tca
• Reporting methods – SNMP trap
ETX-5>config>reporting# alarm-source-attribute e1 1/1/1 event
css-path-tca snmp-trap
 To mask alarms per severity:

• Severity –major and lower
• Reporting method – LED and alarm relay
ETX-5>config>reporting# mask-minimum-severity led-relay major
Controlling Popup Behavior

Alarms and events are briefly 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 Reporting).
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-5# configure management 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
Working with the Alarm and Event Logs

This section explains how to acknowledge, display and clear the alarm and event
logs.

 To display the alarm/event log:

1. Navigate to configure>reporting# context.
2. Type show followed by the display option parameter listed in the following
table.
Display Option Meaning Example

Number
active-alarms Shows the active alarms table. Counters of active alarms in 1

the output appear at the top of the screen, listed in order
of severity
active-alarms-details Same as above but with time-stamp and alarm description 2

added to active alarms.
alarm-information Detailed information about the alarm type. For example, if 3

you need to know what the LOF alarm is on SDH/SONET in
Examples 1 or 2, see Example 3.
alarm-input Displays information about alarm inputs (also known as 4

alarm relays) connected to external sources. Information
includes alarm status, voltage assigned to it (high or low),
and alarm description.
alarm-log Log of active and cleared alarms (without events). The 5

default view of the alarm log (i.e., alarm history) shows
one line per raised alarm and one for cleared alarm.
alarm-list List of all ETX-5 alarms for a specific source ID and severity 6
[<source ID> [severity value, or for all the alarms in the system
{critical|major|minor}]]
brief-alarm-log Brief log of active and cleared alarms (without events).

Unlike the full alarm log (show log), which displays all alarm
instances, the brief log provides only one alarm entry with
the number of times it was recorded since last
acknowledged. The brief log is cleared at reboot.
brief-log Brief log of active alarms, cleared alarms and events. The 7
brief log is cleared at reboot.
event-information Detailed information about event type (similar to alarm-

information).
event-list List of all ETX-5 events for a specific source IDs or of all
the events available in the system
log Log of active alarms, cleared alarms and events

Example 1: Displaying Active Alarms

This command shows the table of active alarms. Counters of active alarms in the
output appear at the top of the screen in order of severity: critical, major and
minor.
ETX-5>config>reporting# show active-alarms

Total : Critical : 2 Major : 1 Minor : 0
1 Domain Clock 1 station_clock_unlock Maj Unmasked

2 Card 1 card_provision_failure Crt Unmasked
3 FAN 1 fan_failure Crt Unmasked
Example 2. Displaying Active Alarms Details

This command shows the table of active alarms with their time-stamp. Counters
of active alarms in the output appear at the top of the screen in order of
severity: critical, major and minor.
ETX-5>config>reporting# show active-alarms-details
Total : Critical : 0 Major : 3 Minor : 0
1 Domain station clock state changed to unlocked
2011-12-20 Domain Clock station_clock_unlock Major Unmasked

20:55:23.00 1
2 Provisioning failure
2011-12-22 Card card_provision_failure Critical Unmasked

01:52:05.00 1
3 Fan failure
2011-12-20 FAN fan_failure Critical Unmasked

20:56:11.00 1
Example 3: Displaying Information of LOF alarm on

SDH/SONET port
This command displays detailed information about a specific alarm. The output
shows the configuration of the source type, followed by a table of sources whose
configurations differ from the source type’s configuration.
For example, use this command if you need to know what the LOF alarm is on
SDH/SONET in Examples 1 or 2. In this example the table of sources is empty
because all the sources are configured the same as their type.
ETX-5>config>reporting# show alarm-information sdh-sonet lof
Source : SDH-SONET
Name : LOF
Description : Loss of frame (LOF)
Alarm ID : 100003
Severity : Major
LED Relay : No
Logged : No

SNMP Trap : No
SNMP trap OID : 1.3.6.1.4.1.164.3.1.6.2.0.22
Source Source ID Severity LED Logged SNMP Trap

-----------------------------------------------------------------------------
Example 4. Alarm Log

This command displays the log of active and cleared alarms (without events). The
default view of the alarm log (i.e., alarm history) shows one line per raised alarm
and one per cleared alarm. The alarm severity is shown on the left. Its possible
values are critical, major, minor, or cleared. The field on the left shows the reason
for alarm on removal: resolved, user-initiated, alarm suppression. On rasing
rebuild or not applicable.
The rebuild reason indicates that the alarm was set after sending a rebuild
command, or manual switch or after install. During manual switch and install
there is a request from components to resend the active alarms in order to make
sure that there is no miss of alarm. The date and time of those alarms are the
original data and time and not the time that the rebuild was set.
ETX-5>config>reporting# show alarm-log
Last Acknowledge On : 64-149-1203 00:206:27.
1 Loss of signal (LOS)
2011-12-18 Ethernet los Cleared
02:17:00.00 main-a/0 Suppression
2 Loss of signal (LOS)
2011-12-18 Ethernet los Major
02:16:58.00 main-a/0
Example 5. Alarm List

This command displays the list of all ETX-5 alarms for source IDs and severity
value. The table also shows whether the alarm is masked or unmasked for the log
and whether these parameters are set to default or have been modified by the
user. This specific example displays the beginning of the list of all the alarms
available in the system.
ETX-5>config>reporting# show alarm-list
Source
Name ID Severity Logged
System
SYSTEM_TEMPERATURE_ORA 20002 Major Yes (Default)
----------------------------------------------------------------------------
System
hardware_failure_fe 20012 Yes (Default)
-----------------------------------------------------------------------------
System

configuration_mismatch_fe 20013 Yes (Default)

-----------------------------------------------------------------------------
System
INTERFACE_MISMATCH_FE 20014 Major Yes (Default)
-----------------------------------------------------------------------------
System
NO_INTERFACE_FE 20015 Yes (Default)
-----------------------------------------------------------------------------
Power Supply
POWER_DELIVERY_FAILURE 20201 Major Yes (Default)
-----------------------------------------------------------------------------
Alarm Input
Alarm_Relay_Input 20401 Major Yes (Default)
-----------------------------------------------------------------------------
Card
HARDWARE_FAILURE 40001 Major Yes (Default)
-----------------------------------------------------------------------------
Card
CARD_MISMATCH 40002 Major Yes (Default)
-----------------------------------------------------------------------------
To scroll up and down in the list, use the arrow keys.
Example 6. Displaying Brief Log

This command displays a brief log of active and cleared alarms and events.
ETX-5>config>reporting# show brief-log
Last Acknowledge On : 64-149-1203 00:206:27.
Critical Major Minor Events
Total : 9 1 0 7
Since Ack : 9 1 0 7
Source Name Last Raised Last Cleared Total Times

Severity Since Ack
System sw_install_end 2011-12-22 -- 1

Event 02:50:14.00 -- 1
System alternate_configuration_loaded 2011-12-22 -- 1
Event 02:51:05.00 -- 1
Clearing Alarms
 To clear a log:
• At the config>reporting# prompt, enter clear followed by log, brief-log or all-
logs to clear the full log, brief log or all alarm/event logs in ETX-5.
The log is cleared.
Alarms and Events

You can view the full lists of alarms and events supported by ETX5.
 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.
11.3 Running Diagnostic Tests

System-level diagnostic capabilities of ETX-5 include ping and trace route utilities.
Running a Ping Test

You can ping a remote IP host to check the ETX-5 IP connectivity with that host.
 To ping an IP host:
1. At any level, start pinging the desired host specifying its IP address and,
optionally, the number of packets to send, and payload size:
ping <1.1.1.1–255.255.255.255> [number-of-packets <1–10000>] [payload-
size <32–1450 bytes>]
2. To stop the ping test, enter <Ctrl> + <c>.
Tracing the Route

This diagnostic utility traces the route through the network from ETX-5 to the
destination host. The trace route utility supports up to 30 hops.
 To trace a route:
• At any level, start the trace route and specify the IP address of the host to
which you intend to trace route:
trace-route <1.1.1.1–255.255.255.255>
Testing Flows
Ingress Flow Loopback

You can set up a permanent flow loopback to check a path from an I/O port to
SAP. This Ethernet loopback is performed by swapping the source and destination
MAC addresses within the Ethernet frame, reversing ingress traffic of the flow
towards the I/O port egress. The MAC swap makes the frame appear to be
sourced from the destination of the original frame and destined to the original
source.
Figure 11-1 illustrates a MAC-swap loopback on an ingress flow. The loopback is
closed after a flow policer (if configured).
11-12 Running Diagnostic Tests ETX-5

Ingress Egress
I/O Ethernet Card Main Card
SAG
I/O ETH
Port

Flow 1 Flow 2
SAP
Flow 3
Tester I/O ETH
Port
SAP
Figure 11-1. Flow Loopback
Egress Flow Loopback

ETX-5300 supports flow MAC swap LB location at the flow egress port.
• Egress flow mac swap LB shall only be supported for flows which the egress
port is:
 IO card port (1GbE , 10GbE).
 IO card LAG ( Protection or Load balancing)
• The relevant cases are illustrated below
• Up to one loop instances per 10x1GbE port group at IO card (or per 1x10GbE
IO port)
ETX-5 Running Diagnostic Tests 11-13

IO Main Card IO
SAP
SAP
IO Main Card
SAP
Egress loop location is illustrated below:
11-14 Running Diagnostic Tests ETX-5

Egress loop location
Loop and MAC swap

Egress loop on this flow
IO Main Card
Policer SAP
Port Loopback
ETH Port level loopback is supported, and applies for the following ports:
• 1GbE IO card
• Main Card
This is a PHY-level loopback.
• Local loopback is supported (ETH Tx looped back into the PSN).
• Remote loopback is supported (ETH Rx looped back toward ETH line)
The loopback is timed per a configurable value. When initiated it affects the
‘TEST’ LED. Events Loopback on/off is supported
CLI: 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 disabled
• Loopback is released after device reset
ETX-5 Running Diagnostic Tests 11-15

11.4 Y.1564 Ethernet Service Activation Test

The Y.1564 Ethernet Service Activation Test provides an out-of-service test
methodology to assess the proper configuration and performance of an Ethernet
service prior to customer notification and delivery.
Standards
ITU-T Y.1564
LLDP
Benefits
The Y.1564 testing methodology provides 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:
ethernet-type 0x22e8
frame-size 512
round-trip-thresholds flr – 200

ftd – 26000
fdv – 11000
availability – 9990
scope configuration performance
direction bidirectional
color-aware color-aware
traffic-policing traffic-policing
Burst test no burst-test
cir-steps s1-percent – 25
s2-percent – 50
s3-percent – 75
s4-percent – 100
configuration-duration 60
11-16 Y.1564 Ethernet Service Activation Test ETX-5

performance-duration 120
rate-convention data-rate
responder type Y1564
To assure quality of service (QoS), providers must properly configure their
networks to define how the traffic is prioritized in the network. This is
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-5 has the ability to set different traffic policing parameters. When a policer is
activated it will monitor the incoming frames and determine their color mode
(CM). If CM is set to Color-Aware it then 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.
Y.1564 Standard
The ITU-T Y.1564 testing methodology ensures that the 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.
See the figure below for the test flowchart.
ETX-5 Y.1564 Ethernet Service Activation Test 11-17

Enter test
parameters
Start test
Service Fail Troubleshoot

configuration service
test configuration
Pass
Service
performance
test
Pass
Test completed
Figure 11-2. Y.1564 Test Flowchart
Configuration Test
The configuration test validates that the 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
Service Acceptance Criteria (SAC).
The configuration tests are as follows:
• CIR (simple or stepped)
• EIR (color-aware or color-blind)
• CBS (color-aware or color-blind)
• EBS (color-aware or color-blind)
• Traffic policing (color-aware or color-blind).

Note When CBS or EBS for an EVC.CoS are set to 0, the corresponding configuration
test is skipped.
Test procedures and success criteria are described in the Test Procedures below.
Performance Test
The performance test validates the quality of the services over user-defined
period of time (1–7200 minutes). Traffic is generated for all services at
configured CIR levels; all Ethernet performance parameters are measured
simultaneously. The bandwidth test as performed according to the bandwidth
profile of a policer assigned to a flow or created for the test. This means that the
Y.1564 test requires a policer to be configured prior to the test.
Test procedures and success criteria are described in the Test Procedures below.
Note If there are two bandwidth profiles (flow and test), the test bandwidth profile is
used.
Test Elements
The Y.1564 test is an intrusive procedure and includes the two main elements:
• Generator – an entity that initiates test, sends out the test and OAM frames,
and receives responses from the responder in a single-ended session
• Responder – an entity that receives the test and OAM frames from the
generator, and transmits a response to the generator in a single-ended
session.
The test operation is bidirectional. This means that the service performance is
measured on the frames that make a round trip (generator > receiver >
generator), see the figure below.
PSN
Forward
Backward
Generator Responder
Figure 11-3. Y.1564 Test Elements
Capacity
ETX-5 supports up to 64 simultaneous Y.1564 tests, with up to 64 generators
and up to 40 responders. The generators and responders can be activated over
EVC or EVC.CoS.
The rate of the Y.1564 traffic for a single generator/responder or several
generators/responders, running in parallel, cannot exceed 1 Gbps.
Operation
The generators and responders are supported over Down MEPs (E-Line service) or
Up MEPs (E-Line service over bridge/ring). Test traffic flow is illustrated and
explained below. The Y.1564 testing is disruptive; the user traffic is blocked on
the tested EVC during diagnostic procedure.

DMMs are used during Y.1564 test to measure frame delay and frame delay
variations. The DMM size is the same as the one that is configured for the Y.1564
operation during test profile creation.
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-4. Full Y.1564 Traffic Path for EVC with Single CoS (Down MEP)
Note The responder can be configured to inject the test frames into the policer or
bypass it.
The testing 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. 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. The responder loops back the frames.
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, provide the round-trip delay measurements.
Down MEP
Depending on the specific implementation, a single MEP per EVC or a separate
MEP per EVC.CoS is required to provision the test. In a case of multiple MEPs, all
of the MEPs must belong to the same MA.
The three figures below illustrate down MEP configurations for the Y.1564
testing.

Generator
Test
Frames
Policer
SAP
Ethernet Down Ethernet

Port MEP Port
Figure 11-5. EVC: Single CoS and Single Down MEP
Generator
Test
Frames
EVC.CoS 1
Policer
Policer EVC.CoS 2
EVC.CoS 3
Policer
SAP

Port MEP Port
Figure 11-6. EVC: Multiple CoSs and Single Down MEP

Generator
MA 1
Test
Frames
VLAN A
P-bit X
Policer
SAP

Port MEP Port
VLAN A
P-bit Y
Policer
SAP

Port MEP Port
Figure 11-7. EVC: Multiple CoSs and Multiple Down MEPs
Up MEP
For multipoint-to-multipoint (E-LAN) services, the Y.1564 testing is performed
over an Up MEP. The testing frames are transmitted into the bridge, and the
VLAN tag value of the test traffic is defined by the Rx flow classification.
Generator
Test
Frames
BP
Tx Flow
Policer
BP Bridge BP
Rx Flow
Ethernet
Up MEP SVI
Port
Figure 11-8. EVC: Single CoS and Single Up MEP

Generator
Test
Frames
EVC.CoS 1
Policer BP
Policer EVC.CoS 2
BP Bridge BP
EVC.CoS 3
Policer
SAP
Ethernet
Up MEP SVI
Port
Figure 11-9. EVC: Multiple CoSs and Single Up MEP
Y.1564 Test with MAC Swap

Y.1564 test can be performed with MEPs configured at the generator side and
MAC swap loopback performed 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-10. Y.1564 Test with MAC Swap
The Y.1564 test is performed as follows:

1. At the generator side, the source transmits test frames at different rates that
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 test and OAM frames.
4. When the generator receives the looped DMM and LMM frames, it sends back
DMR and LMR frames.
5. The responder loops back all frames, including DMRs and LMRs.
 Round-trip loss is measured by the sum of LMR count and local count at
the generator ingress.
 Round-trip delay is measured by DMR timestamps divided by two.

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-Aware EIR Test

Transmission rate is equal to CIR of green frames + EIR of yellow frames.
Success criteria –FLR-G, FTD-G and FDV-G 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-Aware Traffic Policing Test

Transmission rate is set as follows:
• EIR ≥ 20% of CIR - CIR of green frames + 125% of EIR of yellow frames
• EIR < 20% of CIR – CIR of green frames + 25% of CIR of yellow frames + EIR
of yellow frames.
Success criteria –FLR-G, FTD-G and FDV-G are within SAC limits and 0.99 ×
CIR (1-FLR) ≤ IR-T ≤ 1.01 × (CIR + EIR)
Color-Blind Traffic Policing Test

Transmission rate is set as follows:
• EIR ≥ 20% of CIR - CIR + 125% of EIR
• EIR < 20% of CIR – 125% of CIR + EIR.
Success criteria – 0.99 × CIR (1-FLR) ≤ IR ≤ 1.01 × (CIR + EIR)
Color-Aware EBS Test

Based on test case 37 in MEF 19.
Objective: To form the transmission pattern shown in the following diagram for
the duration of the test.

rate
1.1EBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-11. Transmission Pattern (Color-Aware EBS Test)
This can be realized by utilizing two generators:

• First generator (G1) should transmit at CIR for ~200msec, turn off for
100 msec, and start over.
• Second generator (G2) should inject a burst of length 110% (EBS) at
maximum rate every 300 msec.
• The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 × number of cyles × C × (1-FLR) ≤ total number of frames.
C = ceiling (200 msec × CIR/bitsInFrame).
N = number of frames in CBS w/o excess = floor (CBS/frameLength)
Color-Blind EBS Test

rate
1.1(CBS+EBS)
PHY
CIR+EIR
100 200 300 400 500 600 700 time [ms]
Figure 11-12. Transmission Pattern (Color-Blind EBS Test)


• First generator (G1) should transmit at CIR+EIR for ~200msec, turn off for
• Second generator (G2) should inject a burst of length 110% (CBS+EBS) at
maximum rate every 300 msec.
• The number of EIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 × number of cyles × (C + N) × (1-FLR) ≤ total number of frames.
C = ceiling (200msec × CIR/bitsInFrame).
Where:
frameLength = the size of the test frame in bytes.
Color-Aware and Color-Blind CBS Test

rate
1.1CBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-13. Transmission Pattern (CBS Test)

• First generator (G1) should transmit at CIR for ~200msec, turn off for
• Second generator (G2) should inject a burst of length 110% CBS at maximum
rate every 300 msec.
• The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
• For color-aware test: 0.99 × number of cyles × (C + N) × (1-FLR) ≤ number of
green frames.

• For color-blind test: 0.99 × number of cyles × (C + N) × (1-FLR) ≤ total

number of frames.
C = number of frames at CIR per cycle, defined above.
Where:
frameLength = the size of the test frame in bytes.
Performance Test
Transmission rate is equal to CIR.
Success criteria –FLR, FTD, FDV and Availability are within SAC limits.
Configuring Y.1564 Test
Note Y.1564 test is not supported during manual switch.

When manual switch occur, Y.1564 tests will be deactivated automatically.
Y.1564 test configuration procedure includes the following steps, detailed in this
section:
1. Add and configure a Y.1564 test profile
2. Add, configure and activate a Y.1564 test responder
3. Add, configure and activate a Y.1564 test generator.
Adding Y.1564 Test Profile

You can define up to 16 Y.1564 test profiles to be applied to generator and
responder to ensure the desired test functionality.
 To add and configure 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 Y.1564 test profile.
Defining Ethertype of the test ethernet-type <hex-number>

frames
Defining test frame size frame-size <64 | 128 | 256 | 512 |

1024 | 1280 | 1518 | custom_bytes>

Setting the round-trip service round-trip-thresholds <flr <ppm> | ftd flr – bidirectional Frame Loss
acceptance criteria <μs> | fdv <μs> | availability Ratio, measured in 1E-6 units
<percent/100> ftd – bidirectional Frame
Transfer Delay, measured in
microseconds
fdv – bidirectional Frame Delay
Variation, measured in
microseconds
availability – bidirectional
availability, measured in
hundredths of percent units
Setting the scope of the test: scope{ configuration performance |

configuration test, performance configuration | performance }
test, or both
Setting the direction in which direction bidirectional Permanently set to

the test is performed bidirectional
Setting the color mode used in color-aware

the test no color-aware
Specifying whether to include or burst-tests [cbs] [ebs] You can enter the command
exclude the CBS and EBS sub- no burst-tests 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.
Including or excluding the traffic traffic-policing

policing sub-test from the no traffic-policing
configuration phase
Setting the number of steps and cir-steps<s1-percent | s1-percent s2- s1-percent –transmission rate,
their transmission rate in the CIR percent | s1-percent s2-percent s3- as percentage of CIR, at the
sub-test percent |s1-percent s2-percent s3- first step of the CIR sub-test
percent s4-percent> (1–100)
s2-percent – transmission rate,
as percentage of CIR, at the
second step of the CIR sub-test
(1–100)
third step of the CIR sub-test
(1–100)
fourth step of the CIR sub-test
(1–100)
Defining the duration of the configuration-duration <seconds> 18–360 seconds

configuration test for each P-bit

Defining the duration of the performance-duration <15m | 2h | 24h Custom performance test
performance test | custom [1–7200]> duration is measured in
minutes (1–7200)
Defining whether rate rate-convention <data-rate | line-

measurements are be shown in rate>
the test report as 'data-rate' (IR)
or converted to 'line rate' (ULR)
Defining responder type responder-type <y1564 | mac-swap> y1564 – Standard Y.1564

responder that requires MEP
configuration
mac-swap – Responder that
requires performing MAC swap
loopback
Creating, modifying or deleting a p-bit<0–7> The P-bit test profile allows to

Y.1564 test P-bit profile configure a separate test to be
run on a specific P-bit. The rest
of the P-bits are tested, using
the general profile.
See P-bit configuration details
below.
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 |

1024 | 1280 | 1518 | custom_bytes>
Setting the round-trip service round-trip-thresholds <flr <ppm> | ftd flr – bidirectional Frame Loss
acceptance criteria <μs> | fdv <μs> | availability Ratio, measured in 1E-6 units
<percent/100> ftd – bidirectional Frame
Transfer Delay, measured in
microseconds
fdv – bidirectional Frame Delay
Variation, measured in
microseconds
availability – bidirectional
availability, measured in
hundredths of percent units
Adding Y.1564 Generator

You can define up to 64 Y.1564 test generators.
 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 Y.1564 generator.
Assigning a test profile to the test-profile <profile-name>

generator
Defining the service to be tested bind <md <id> ma <id> [p-bit <0–7>] md –The maintenance domain
no bind 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 pre-configured
P-bits, if none are specified
no bind removes generator
association with the service
Defining a bandwidth profile for policer p-bit <value> bandwidth [cir p-bit – The CoS to which the
the test <kbps>] [cbs <bytes>] [eir <kbps>] configuration applies (0–7)
[ebs <bytes>] bandwidth – The committed
policer p-bit <value> profile <policer- information rate, committed
profile-name> burst size, excessive
no policer p-bit <value> information rate and excessive
burst size for the EVC.CoS
(0–4294967295)
For example:
policer p-bit 3 bandwidth cir 50000 profile – An optional
cbs 5000 pre-defined policer profile to
be used in the test
policer p-bit 3 profile test
no policer p-bit 3
Activating or deactivating the activate

test at the generator side no activate
Displaying the Y.1564 test show status See Displaying Test Status
status (Generator Side)
Displaying the test results and show report <summary | detailed> See Displaying Test Results.
measurements

Displaying Test Status (Generator Side)
 To display the test status (generator side):

• In the config>test>y1564>generator<generator-name># prompt, enter show
status.
The status screen appears. For information on the test status values,
ETX-5>config>test>y1564>generator(1)# show status
Status : In Progress
Time Remaining : 00:20:00

Test Phase : Performance
Associated EVC
---------------------------------------------------------------
--------------Inner-Tag 500 Outer-Tag 200
MEP Service P-BIT Tx Flow Rx Flow

---------------------------------------------------------------
--------------
11 1 1 abc mopq
12 1 3 bcd opqr
13 1 5 cde pqrs
MEP Service P-BIT

CIR EIR BWP In Use
(Mbps) (Mbps)
---------------------------------------------------------------
--------------
11 1 1 10.0 2.0 Flow
12 1 3 20.0 5.0 Flow
13 1 5 30.0 10.0 Test
The table below explains the Y.1564 test status values.
Table 11-1. Y.1564 Test Status Values (Generator Side)
Displayed
Idle Test is not ready for activation; some of the mandatory attributes
are not configured yet
In progress Test is currently running
Passed Test has been completed successfully
Failed Test has failed; the results are not within the SAC limits
User Aborted Test has been stopped by the operator (future option)
System Aborted Test has been autonomously stopped by the system (future option)

Table 11-2. Y.1564 Test Values (Generator Side)
Displayed
Time Remaining The time remaining till the end of the test
Test Phase The current phase of the test
Inner Tag The value of the inner VLAN (usually C-Tag)
Outer Tag The value of the outer VLAN (usually S-Tag)
MEP The identifier of the MEP that is associated with the specific P-bit
Service The identifier of the service that is associated with the specific P-bit
P-bit A P-bit that is included in the tested service
Tx Flow The egress flow corresponding to the MEP and P-bit
Rx Flow The ingress flow corresponding to the MEP and P-bit
CIR The provisioned CIR of the egress flow
EIR The provisioned EIR of the egress flow
BWP in use The origin of the associated bandwidth profile for the EVc.CoS (test
or flow)
Displaying Test Results

When displaying the Y.1564 test results, you can choose to generate a test
summary or a detailed test report.
 To display the summary test results:

report summary.
The summary report screen is displayed. For information on the test
report summary counters, see table below.
ETX 5300A>config>test>y1564>generator(1)# show report summary
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-11-22-33-44-55
Source MAC Address : 00-22-33-44-55-66
Inner-Tag : 500 Outer-Tag 200
P-bit/s : 1
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance
Profile Name : y1564_profile_1
Start Date & Time : 2013–02–17 21:30:00
End Date & Time : 2013–02–17 22:00:00
Total Duration : 30:00
Overall Result : Passed
Configuration Test Report

-----------------------------------------------------------------------------
P-bit : 1
Duration [sec] : 1800
Configuration Result : Passed
Test Result Tx Rate IR FLR FTD FDV

[Mbps] [Mbps] [ms] [ms]
CIR Test
-----------------------------------------------------------------------------
Step 1 Pass 3.73 3.75 4.9E-4 0.032 0.01
Step 2 Pass 7.50 7.50 0.0E-3 0.032 0.01
Step 3 Pass 11.25 11.25 0.0E-4 0.032 0.01
Step 4 Pass 15.0 15.0 2.4E-4 0.032 0.01
EIR Test
-----------------------------------------------------------------------------
Green Pass 15.0 39.6 2.4E-4 0.032 0.01
Total 40.0 39.6 2.4E-2 -- --
CBS Test
Pass
EBS Test
Pass
Traffic Policing
-----------------------------------------------------------------------------
Green Pass 15.0 39.1 1.8E-3 0.032 0.01
Total 46.25 39.1 1.8E-1 -- --
Performance Test Report

-----------------------------------------------------------------------------
Duration [min] : 30
Performance Result : Pass
P-bit Result Tx Rate [Mbps]

-----------------------------------------------------------------------------
1 Pass 15.0
IR [Mbps]
-----------------------------------------------------------------------------
P-bit IR FLR FTD FDV Avail
[Mbps] [ms] [ms] [%]
-----------------------------------------------------------------------------
1 14.2 4.9E-4 0.032 0.01 94.0

Table 11-3. Y.1564 Test Counters (Summary)
Counter Description
Tx Rate (Mbps) The transmission rate to which the generator is configured in the
sub-test
IR (Mbps) The average calculated Information Rate
FLR The calculated Frame Loss Ratio
FTD (ms) The average calculated Frame Transfer Delay
FDV (ms) The average calculated Frame Delay Variation
Avail The 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 below.
ETX 5300A>config>test>y1564>generator(1)# show report detailed
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-11-22-33-44-55
Source MAC Address : 00-22-33-44-55-66
Inner-Tag : 500 Outer-Tag 200
P-bit/s : 1
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance
Profile Name : y1564_profile_1
Start Date & Time : 2013–02–17 21:30:00
End Date & Time : 2013–02–17 21:45:18
Total Duration : 15:18
Overall Result : Passed
Configuration Test Report

-----------------------------------------------------------------------------
P-bit 1 .
Duration [sec] : 18
Configuration Result : Passed
CIR Test
-----------------------------------------------------------------------------
Parameter Step #1 Step #2 Step #3 Step #4 Thr
----------------- -------- -------- -------- -------- -------
Tx Rate [Mbps] 3.25 7.50 11.25 15.0
IR – min [Mbps] 3.73 7.50 11.22 15.0
IR – mean [Mbps] 3.75 7.50 11.25 15.0
IR – max [Mbps] 3.76 7.50 11.26 15.0
FL – count 41 0 0 83
FLR 4.9E-4 0.0E-3 0.0E-4 2.4E-4 5.0E-4
FTD – min [ms] 0.022 0.022 0.022 0.022

FTD – mean [ms] 0.032 0.032 0.032 0.032 0.04

FTD – max [ms] 0.042 0.042 0.042 0.042
FTD – std [ms] 0.091 0.091 0.091 0.091
FDV – mean [ms] 0.01 0.01 0.01 0.01 0.012
FDV – max [ms] 0.02 0.02 0.02 0.02
----------------- -------- -------- -------- -------- -------
Result Pass Pass Pass Pass
EIR Test & Traffic Policing Test

-----------------------------------------------------------------------------
EIR EIR Policing Policing
Parameter Green Total Green Total Thr
Tx Rates [Mbps] 15.0 40.0 15.0 46.25
IR – min [Mbps] 36.3 -- 33.2 --
IR – mean [Mbps] 39.6 39.6 39.1 39.1
IR – max [Mbps] 40.0 -- 39.5 --
FL – count 20 2000 150 15601
FLR 2.4E-4 2.4E-2 1.8E-3 1.8E-1 5.0E-4
FTD – min [ms] 0.022 -- 0.022 --
FTD – mean [ms] 0.032 -- 0.032 -- 0.04
FTD – max [ms] 0.042 -- 0.042 --
FTD – std [ms] 0.091 -- 0.091 --
FDV – mean [ms] 0.01 -- 0.01 -- 0.012
FDV – max [ms] 0.02 -- 0.02 --
Result Pass Pass
Burst Tests
Parameter CBS EBS

Number of Cycles 24 24
Frames per Cycle 21 158
Minimum Expected Frames 104834 100871
Actual Received Frames 110915 221705
Result Pass Pass
Performance Test Report

-----------------------------------------------------------------------------
Duration [min] : 15
Performance Result : Passed
P-bit Result Tx Rate [Mbps]

-----------------------------------------------------------------------------
1 Pass 15.0
IR [Mbps]
-----------------------------------------------------------------------------
P-bit Min Mean Max
-----------------------------------------------------------------------------
1 14.2 14.2 14.2
FL
-----------------------------------------------------------------------------
P-bit Count FLR Thr
-----------------------------------------------------------------------------
1 19 4.9E-4 5.0E-4

FTD [ms]
-----------------------------------------------------------------------------
P-bit Min Max Std Mean Thr
-----------------------------------------------------------------------------
1 0.022 0.042 0.091 0.032 0.04
FDV [ms]
-----------------------------------------------------------------------------
P-bit Max Mean Thr
-----------------------------------------------------------------------------
1 0.02 0.01 0.09
Availability
-----------------------------------------------------------------------------
P-bit UAS % Thr [%]
-----------------------------------------------------------------------------
1 54 94.0 93.99
Table 11-4. Y.1564 Test Counters (Detailed)
Counter Description
Tx Rate (Mbps) The transmission rate to which the generator is configured in the
sub-test
IR – min (Mbps) The minimum measured Information Rate
IR – mean (Mbps) The average calculated Information Rate
IR – max (Mbps) The maximum measured Information Rate
FL – count The number of lost frames
FLR The calculated Frame Loss Ratio
FLR Thr The FLR service acceptance criteria for the reported P-bit
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
FTD Thr The FTD service acceptance criteria for the reported P-bit
FDV –mean (ms) The average calculated Frame Delay Variation
FDV –max (ms) The maximum calculated Frame Delay Variation
FDV Thr The FDV service acceptance criteria for the reported P-bit
UAS The number of unavailable seconds
% The percentage of available time
Availability Thr The Availability service acceptance criteria for the reported P-bit
Adding Y.1564 Responder

You can define up to 40 Y.1564 test responders.

 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 Y.1564 responder.
Assigning a test profile to the test-profile <profile-name>

responder
Defining the service to be tested bind <md <id> ma <id> md –The maintenance domain
no bind to which the service belongs
(1–65535)
ma – The maintenance
association to which the
service belongs (1–65535)
no bind removes responder
association with the service
Activating or deactivating the activate

test at the responder side no activate
Displaying the Y.1564 test show status See Displaying Test Status
status (Responder Side)
Displaying Test Status (Responder Side)
 To display the test status (responder side):

• In the config>test>y1564>responder<responder-name># prompt, enter show
status.
The status screen appears. For information on the test status values,
ETX-5>config>test>y1564>responder(1)# show status
Status : In Progress
MEP Service P-bit Rx Packets Tx Packets

21 1 1 1001 1001
22 1 3 1000 1000
23 1 5 765 765
The table below explains the Y.1564 test status values.

Table 11-5. Y.1564 Test Status (Responder Side)
Idle – Test is not ready for activation; some of the mandatory

Status attributes are not configured yet
In progress – Test is currently running
Rx Packets The number of packets received by the ingress flow corresponding

to the MEP and P-bit
Tx Packets The number of packets transmitted by the egress flow

corresponding to the MEP and P-bit
Example
This example shows how to create a Y.1564 test generator over a Down MEP
located between two main card ports and bound to one of them. The test is to
be run over OAM (CFM) service defined on P-bit 1.
 To configure Y.1564 test generator over a Down MEP:

5. Configure a policer profile.
8. Define a Down MEP bound to port 4.
10. Configure the Y.1564 test profile.
11. Add the Y.1564 generator, bind it to the relevant MD, MA, OAM service and
test profile.
Generator
Test
Frames
Flow 1 P-bit 1
Policer
Flow 2

Port 1 MEP Port 4
Figure 11-14. Y.1564 Test Generator over Down MEP

no shutdown
exit all

no shutdown
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
config flows classifier-profile vlan100 match-any
match vlan 100
exit all
#*********************************End********************************************
************************Defining_Policer_Profile*********************************
config qos policer-profile 1 bandwidth cir 100000 cbs 10000 eir 10000 ebs 20000
exit all
#*********************************End********************************************
config qos cos-map-profile cos_OAM classification p-bit
map 0 to-cos 0
map 1 to-cos 1
map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
shutdown
classifier vlan100
policer profile 1
pm-enable
no shutdown

exit all

shutdown
classifier vlan100
pm-enable
no shutdown
exit all
#*********************************End********************************************
config oam cfm
ccm-interval 1s
name uint 260
mep 4
direction down
queue queue-mapping "QueueMapDefaultProfile" block 0/1
cos-mapping profile cos_OAM
ccm-initiate
ccm-priority 7
remote-mep 3
no shutdown
service 7
delay-threshold 100
lmm-interval 100ms
dmm-interval 100ms
dest-ne 1
remote mac-address 00-20-D2-F8-1D-AB
exit
no shutdown
dest-ne 1
clear-statistics
exit all
#*********************************End********************************************
#*******************Configring_Y.1564_Test_Profile_and_Generator*****************
config test y1564
profile 1
ethernet-type 0x8550
frame-size 128
no color-aware
direction bidirectional
configuration-duration 60
performance-duration customer 10
rate-convention data-rate
scope configuration performance

exit
generator 1
bind md 1 ma 1 p-bit 1
test-profile 1
activate
exit all
#*********************************End********************************************
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
Illegal command value Invalid value for the parameter
Max number of active generators has The maximum number of Y.1564 generators (eight) has been
been exceeded reached and no additional generators can be added
Max number of active responders has The maximum number of Y.1564 responders (20) has been
been exceeded reached and no additional responders can be added
Y.1564 profile is in use Y.1564 profile is in use and cannot be modified
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 classification types MEPs within selected MD/MA have different classification types

Message Description
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
I/O flow with matching CoS has not been The Y.1564 test mechanism failed to identify a MEP Tx flow with
found a P-bit, matching testing criteria. This is relevant for the Tx flows
originating from the I/O card port (via SAP).
Impossible to define more than 16 The maximum number of profiles have been defined.
profiles
Impossible to activate more than 1

generator
Impossible to activate a generator that is A generator can’t be activated without p-bit definition while the
bounded to an OAM, but without p-bit OAM contains services with p-bit definition.
definition and starting from main-card
while the OAM contains some services
with more than one p-bit.
11.5 OAM CFM

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-5 also
supports performance monitoring per Y.1731.
Standards
LLDP
MEF 36
Factory Defaults
By default, OAM functionality is disabled.
11-42 OAM CFM ETX-5

OAM (Operation, Administration, and Maintenance) describes the monitoring of
network operation by network operators. OAM is a set of functions used by the
user that enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM may trigger
control plane or management plane mechanisms, by activating rerouting or by
raising alarms, for example, but such functions are not part of the OAM itself.
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.
OAM Elements
The Ethernet OAM mechanism monitors connectivity in Maintenance Association
(MA) groups, identified by a Maintenance Association Identifier (MAID). Each
maintenance association consists of two or more maintenance end points (MEP).
Every 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).
• Maintenance Domain (MD) – The network or the 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 PDUs and tracks responses.
• Maintenance Intermediate Points (MIPs) are intermediate entities that are

created in the middle of the domain. Unlike MEPs, MIPs are passive points,
responding only when triggered by CFM trace route and loopback messages.
A MIP consists of two MIP Half Functions (MHFs), uUnlike MEPs, which are
directional entities acting as service termination points. There are two types
of intermediate entities: service-level and MD-level MIPs. These MIP modes
cannot be activated simultaneously:
 Service-level MIPs are defined under the MD level. This type of MIP
inherits its source MAC address from the directly or indirectly attached
physical port. Service-level MIPs respond to link trace messages (LTMs)
and loopback messages (LBMs) whose MD level is equal to the MIP MD
level.
 MD-level MIPs are activated per device per MD level (or several MD levels).
When MD-level MIP mode is activated, ETX5 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. Each MIP inherits its source
MAC address from the adjacent port. MD-level MIPs respond to link trace
messages (LTMs) whose MD level is equal to the MIP MD level.
ETX-5 OAM CFM 11-43

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
• 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 or
router interface.
• MD-level MIPs can be defined only over flows with the classification: Single
VLAN, or outer + inner VLAN.
• MD-level MIPS do not reply to loopback messages (LBMs).
MEPs that are created at the same MD level as the MIPs do not support
multicast loopbacks.
OAM Functions
RAD’s carrier Ethernet aggregation and demarcation devices feature a
comprehensive hardware-based Ethernet OAM and performance monitoring for
SLA assurance:
• 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).
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-2xxA devices serve as a MIPs
• End-to-end OAM session (EVC ME) between two ETX-2xxAs, which serve as
MEPs. ETX-5 devices act as MIPs.
• Segment OAM session (operator service ME) between ETX-2xxA and the
network side of ETX-5.
11-44 OAM CFM 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-15. Multi-Domain Ethernet Service OAM
MEPs and Services

ETX-5 Ethernet main cards support Ethernet OAM functionality and host MEPs as
illustrated in the figure below. A MEP can be either Down or Up, depending on its
position and port association, as explained below.
ETX-5 OAM CFM 11-45

GbE SAP 10 GbE

MEP
I/O Ethernet Card
10 GbE BP 10 GbE
MEP Bridge BP MEP
10 GbE MEP 10 GbE
Main Ethernet Card
Figure 11-16. Ethernet Main Card MEPs
A MEP is transparent to OAM frames whose MD level is higher than the MEP level,
and drops OAM packets whose MD level is lower than the MEP level. It fully
supports connectivity check (CC), loopback, link trace and PM counters,
Down MEP
Down MEPs reside at port egress and are bound to physical ports. These MEPs
receive and send CFM PDU from and to the network. Down MEPs are supported
for either point-to-point (E-Line) or multipoint (E-LAN) services. Different MEP
locations are illustrated below.
Tx Flow
MEP
Rx Flow
Main Card Main Card
Port A Port B
Figure 11-17. P
ports with the MEP bound to port B. Tx flow in the service is directed to a queue
block.
11-46 OAM CFM ETX-5

Tx Flow
MEP
SAP
Rx Flow
Main Card I/O Card
Port A Port B
Figure 11-18. PtP Service with Down MEP Bound to I/O Card Port B
ports with MEP bound to port A. Tx flow in the service is directed to a queue
block.
Rx Flow
MEP
SAP
Tx Flow
Main Card I/O Card
Port A Port B
Figure 11-19. PtP Service with Down MEP Bound to Main Card Port A
Tx Flow
SAP
MEP
SAP
Rx Flow
I/O Card I/O Card
Port A Port B
Figure 11-20. PtP Service between Two I/O Card Ports with Down MEP Bound to Port B
ports with the MEP bound to port A. Tx flow in the service is directed to a queue
block.
Tx Flow
Rx Flow
Main Card
Port A
Figure 11-21. Multipoint Service with Down MEP Bound to Main Card 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
ETX-5 OAM CFM 11-47


 Match all. If configured over an IO port, the flow from the corresponding
SAP must be used. It also needs a classification profile to specify the
packet tag structure (as it cannot be taken from the flow classification
profile).
• Tx flow to a destination queue to forward OAM frames.
Up MEP
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.
Different E-Line MEP locations are illustrated below.
Tx Flow
MEP
Rx Flow
Main Card Main Card
Port A Port B
Figure 11-22. PtP Service with Up MEP Bound to Main Card Port A
Tx Flow
SAP
MEP
SAP
Rx Flow
I/O Card I/O Card
Port A Port B
Figure 11-23. PtP Service between Two I/O Card Ports 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). Different E-LAN Up MEP locations are illustrated below.
11-48 OAM CFM ETX-5

The figure below illustrates a multipoint service between I/O card and bridge
to the BP SVI.
Rx Flow
BP Bridge BP SVI MEP SAP
Tx Flow
I/O Card
Port A
to the BP SVI.
Rx Flow
Tx Flow
Main Card
Port A
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.
MIPs
Unlike MEP, which is a directional entity acting as a service termination point, MIP
is defined as a bidirectional intermediate entity, consisting of half functions
(MHFs). There are two types of intermediate entities: service-level and MD-level
MIPs. These MIP modes differ in functionality, scale, configuration, and cannot be
activated simultaneously.
Service-Level MIPs
Service-level MIP responds to link trace messages (LTMs) and loopback messages
(LBMs), whose MD level is equal to the MIP MD level. ETX-5 supports up to 256
service-level MIPs.
MIP
LBM/LTM LBM/LTM
Flow X Flow X
LBR/LTR LBR/LTR
MHF MHF
Figure 11-26. Service-Level MIP Functionality
ETX-5 OAM CFM 11-49

Like MEPs, the MIPs are bound to physical ports (directly- or indirectly-attached),
inheriting the MAC address of the port for LTM purposes. The MIPs have 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 MD level and are characterized by the following:
• The physical port to which they are bound, inheriting the port’s MAC source
address
• Rx flow, originating from the MIP-bound port, which faces MHF 1, and whose
classification profile can be one of the following:
 Untagged
 Single VLAN
• Rx classification, when Rx flow originates from SA with the Match All
classification profile
• Tx flow, originating from the physical port facing MHF 2
• CoS mapping profile
• Optional egress queue for the Tx flow.
The two figures below illustrate service-level MIPs in point-to-point and
11-50 OAM CFM ETX-5

MIP
(bound to port B)
Rx Flow
Tx Flow
Main Card MHF 2 MHF 1 Main Card
Port A Port B
MIP
(bound to port B)
Rx Flow
SAP
Tx Flow
Port A Port B
MIP
(bound to port A)
Tx Flow
SAP
Rx Flow
Port A Port B
Figure 11-27. Service-Level MIPs in Point-to-Point Service
MIP
(bound to port B)
Rx Flow
BP Bridge BP SVI
Tx Flow
MHF 2 MHF 1 Main Card
Port B
Figure 11-28. Service-Level MIP in Multipoint Service
MD-Level MIPs
MD-level MIPs are activated per device per MD level (or several MD levels).
Flows
Ethernet port and bridge port. This includes the flows that already existed in the
system, and the new ones, which are added after device-level MIP creation. The
MIP inherits source MAC address from the adjacent Ethernet port.
MD-level MIPs can be defined over flows with one of the following classification
profiles:
• Single VLAN
• Single outer + single inner VLAN
MD-level MIPs cannot be provisioned over flows connected to router- and
pseudowire-type SVIs.
The two figures below illustrate device-level MIPs over point-to-point and
ETX-5 OAM CFM 11-51

MIP MIP
Main Card MHF 2 MHF 1 MHF 2 MHF 1 Main Card

Port A Port B
MIP MIP
SAP
Main Card MHF 2 MHF 1 MHF 2 MHF 1 I/O Card

Port A Port B
Figure 11-29. Device-Level MIPs in Point-to-Point Service
MIP
(bound to port A)
SAP BP
MIP
Port A MHF 2 MHF 1 (bound to port C)
MIP
Bridge BP SVI
(bound to port B)
Port C
MHF 2 MHF 1
SAP BP
Port B MHF 2 MHF 1

I/O Card Main Card
Figure 11-30. Device-Level MIPs in Multipoint Service
Measurements
MD-level MIPs respond to link trace messages (LTMs), whose MD level is equal to
the MIP MD level. 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 learned 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.
11-52 OAM CFM ETX-5

MIP
LTM LTM
Flow X Flow X
LTR LTR
MHF MHF
Figure 11-31. MD-Level MIP Functionality
Limitations and Exclusions

The following limitations exist, when MD-level MIPs are defined:
• MD-level MIPS do not reply to loopback messages (LBMs)
• MEPs, created at the same MD level as the MIPs, do not support multicast
loopbacks.
• If a MD-level MIP is configured and a MEP with an equal or higher MD level is
• If a MEP with an equal or higher MD level is configured on a flow, a MD-level
MIP cannot be added to the flow.
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
ETX-5 OAM CFM 11-53

• 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-32. 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-7. CCM Group Destination MAC
01-80-C2-00-00-3y
7 7
6 6
5 5
4 4
3 3
2 2
1 1
0 0
11-54 OAM CFM ETX-5

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.
LTM
MEP
LTR
Main Card Main Card
Port A Port B
Figure 11-33. MEP with LTM Sent from the Card Port in Point-to-Point Service
ETX-5 OAM CFM 11-55

LTM
LTR Main Card

Port A
Figure 11-34. 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
LTR
MIP
Main Card Main Card
Port A Port B
Figure 11-35. MIP with LTM Sent from the Card Port in Point-to-Point Service
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 learnt at all. If the target MAC address has been learned on another
bridge port, the LTM is discarded.
LTM LTM
BP Bridge BP SVI
LTR
MIP
Main Card
Port A
Figure 11-36. MIP with LTM Sent from the Bridge Port in Multipoint Service
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 SVI
LTR
MIP
Main Card
Port A
Figure 11-37. MIP with LTM Sent from the Card Port in Multipoint Service
ETX-5 Ethernet service OAM PM functionality complies with the Y.1731
requirements. ETX-5 provides per-service loss and delay measurement and event
reporting.
11-56 OAM CFM ETX-5

statistic counters enabled (pm-enable).
The following performance parameters are measured by appropriate OAM messages:

• Frame Loss Ratio (FLR) – FLR, expressed as a percentage, is the ratio of the
number of service frames not delivered, divided by the total number of
service frames during a time interval, where the number of service frames not
delivered is the difference between the number of service frames sent to an
ingress UNI and the number of service frames received at an egress UNI.
ETX-5 supports single-ended and proprietary synthetic loss measurement
(LM) with proactive LMM transmission and automatic LM response. OAM MEPs
measure frame loss only if statistic counters have been enabled on the
incoming and outgoing flows. LM is not supported over tunnels. Both single-
ended and synthetic methods can co-exist on the same MEP/service. See
User-Data Loss Measurement and Synthetic Loss Measurement below.
• Frame Delay (FD) – FD is specified as round trip delay for a frame, where FD
is defined as the time elapsed since the start of transmission of the first bit
of the frame by a source node, until the reception of the last bit of the loop
backed frame by the same source node, when the loopback is performed at
the frame’s destination node.
ETX-5 supports dual-ended delay measurement (DM) with proactive DMM
transmission and automatic DM response. Measurement is performed for
delays of up to 1 second with full DM over tunnels.
User-Data Loss Measurement

Single-ended loss measurements are supported on user data in the following
cases:
• For Up and Down MEPs, when the egress flows have their original P-bit
modified via CoS marking profile, assuming the CoS marking profile is
coordinated with the MEP CoS mapping profile (CoS per p-bit for multiCoS
service or fixed CoS for single CoS).
• For Down MEP, when no P-bit change is performed at the exit to the network
(P-bit is copied to S-tag).
• For Up MEP, when no P-bit change is performed at the exit to the network
assuming a 1-to-1 CoS mapping profile is configured on the Tx flow of the Up
MEP and on the MEP itself.
Synthetic Loss Measurement

Synthetic loss measurement is a RAD-proprietary method, which uses standard
LMM/LMR frames for counting DMM and DMR. Synthetic LM is supported over
tunnels. It can be activated even if the MEP flows do not have statistic counters
enabled (no pm-enable). Up to 64 destination NEs are supported by a MEP
service (E-Line and E-L AN). The figure below presents standard Y.1731 counters
used in the synthetic loss measurements.
ETX-5 OAM CFM 11-57

LMM
TxFcf: Tx DMM+DMR Counter
MEP MEP
From LMR LMR

TxFcf: Copy from LMM TxFcf: Copy from LMM
RxFcf: Rx DMM+DMR Counter RxFcf: Rx DMM+DMR Counter
TxFcb: Tx DMM+DMR Counter TxFcb: Tx DMM+DMR Counter
Local Counter
RxFcl: Rx DMM+DMR Counter
Figure 11-38. Synthetic Loss Measurement Counters
Configuring OAM
Ethernet OAM configuration procedure includes the following steps, detailed in
this section:
Note Before deleting any of the OAM CFM components, verify that it is not used by
other ETX-5 elements, such as ERP.
• Configure maintenance domains (MDs)
11-58 OAM CFM ETX-5

Define maintenance associations (MAs)

1. Add maintenance endpoints (MEPs)
2. Add maintenance intermediary points (MIPs)
3. Define endpoint services
4. Add destination network elements (NEs)
5. Configuring counter thresholds.
6. Configure a measurement bin profile.
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.
Note MD name is no name.
 To add a maintenance domain:

• At the config>oam>cfm# prompt, enter maintenance-domain <mdid>
where <mdid> is 1–4096.
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 it has all its MEPs/MIPs deleted or
disabled.
 To configure a maintenance domain:

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

association for the MD no maintenance –association <maid> Associations.
no maintenance –association <maid>
deletes the MA
Specifying the maintenance md-level <md-level> The allowed range for md-level is 0–7
domain level Note: If the pre-standard OAM protocol
is used, the only value allowed for the
maintenance domain level is 3.
ETX-5 OAM CFM 11-59

Specifying the name of the name string <md-name-string> • Maximum length of MD name string is
maintenance domain no name 43 characters
• Maximum combined length of MD
name and MA name strings is
44 characters
• ETX-5 supports up to 2048 MEPs with
MDs and/or MAs, using name strings
Defining MIPs mip <mip id> Refer to Configuring Maintenance

no mip <mip id> Intermediary Points.
no mip <mip id> deletes the MIP.
Displaying information on show maintenance-association <maid>

configured MAs
Displaying information on show mip <mip id>

configured MIPs
Configuring Maintenance Associations

A maintenance domain contains maintenance associations, for each of which you
can configure the continuity check interval and maintenance endpoints (MEPs).
 To add a maintenance association (MA):
• At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance-association <maid>
where <maid> is 1–4096.
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 it has all its MEPs/MIPs deleted
or disabled.
 To configure a maintenance association:

• 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
11-60 OAM CFM ETX-5

Specifying MA name in UINT, name uint <0–65535> • Maximum length of MD name string is
string, or icc format name string <ma-name-string> 43 characters
name icc <ma-name-icc> • Maximum combined length of MD name and

MA name strings is 44 characters
• ETX-5 supports up to 2048 MEPs with MDs
and/or MAs, using name strings
• 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.
ETX-5 supporte up to 2048 MEPs with
MAs using name icc.
Specifying the interval ccm-interval {3.33ms | 10ms |

between continuity check 100ms | 1s | 10s | 1min | 10min}
messages
Configuring MEP for the MA mep <mepid> Refer to Configuring Maintenance Endpoints
Configuring Maintenance Endpoints

Maintenance endpoints reside at the edge of a maintenance domain. They initiate
and respond to CCMs, link trace requests, and loopbacks, in order to detect,
localize, and diagnose connectivity problems. ETX-5 supports up to 4K MEPs and
MIPs.
 To add a maintenance endpoint (MEP):
mep <mepid>
where <mepid> is 1–4096.
The MEP is created and the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)$ is displayed.
 To delete a maintenance endpoint:

no mep <mepid>
The maintenance endpoint is deleted.
Note You can remove a maintenance endpoint regardless of whether it contains

services.
ETX-5 OAM CFM 11-61

 To configure a maintenance endpoint:

maintenance-association <maid> mep <mepid>to select the maintenance
endpoint to configure.
The prompt config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
is displayed.
Enabling AIS sending and ais [ interval { 1s | 1min }] To disable AIS sending, enter no ais
defining interval [priority <priority>]
Binding the MEP to an bind ethernet <slot/port> To remove the MEP from an Ethernet port,

no bind
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> The allowed range for <priority> is 0–7
CCMs, LBMs and LTMs
transmitted by the MEP
Associating the MEP with a classification profile <profile_name> Classifier profile is needed when the MEP
All).
Defining client MD level client-md-level <md_level> Client MD level is a level for sending
upstream AIS
Associating the MEP with a cos-mapping profile <profile_name> The CoS mapping profile must be
to the packets transmitted by the MEP
(CCMs, LBTs etc).
Defining the MEP direction direction {up | down}
and Tx flows to the MEP <tx-name>] uni-direction
Activating OAM loopback lbm See Performing OAM Loopback
Activating OAM link trace linktrace See Performing OAM Link Trace
11-62 OAM CFM ETX-5

MEP <queue_mapping_profile_name> queue queue-mapping
Defining remote MEP with remote-mep <remote_mep_id> Allowed range for remote MEP is 1–8191
which the MEP no remote-mep <remote_mep_id> The MEP ID and the remote MEP ID must
communicates be different. You can define up to 512
remote MEPs for the local MEP 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.
To delete remote MEP, enter no
remote-mep <remote_mep_id>
Configuring service for the service <service_id> Refer to Configuring Maintenance

MEP Endpoint Services
Displaying MEP status show status
Displaying remote MEP show remote-mep <remote-mep-id>

status status
Displaying MEP service show service <service_id>

status
Administratively enabling no shutdown To deactivate the MEP, enter shutdown.

MEP When a MEP is no shutdown, its services
are not being activated automatically.
Administratively disabling a shutdown When a MEP is shutdown,its active

MEP services (services that are in no shutdown)
are moved automatically to shutdown as
well. No error or warning message is
displayed.
Configuring Maintenance Intermediary Points
MD-Level MIP
Ethernet port and bridge port. The MIPs are added for each specified MD level, or
MD level range.
 To add a 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.
Using no before the command removes the MIP.
ETX-5 OAM CFM 11-63

Service-Level MIP
MIPs are bidirectional intermediate entities, consisting half functions (MHFs). MIPs
respond to link trace messages (LTMs) and loopback messages LBMs, whose MD
level is equal to the MIP MD level. ETX-5 supports up to 256 MIPs.
 To add a maintenance intermediate point (MIP):
• At the config>oam>cfm>md(<mdid>)# prompt enter: mip <mipid>
The maintenance intermediary point is created and the
config>oam>cfm>md(<mdid>)>mip(<mipid>)$ prompt is displayed.
 To delete a maintenance intermediary point:

• At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mipid>
The maintenance intermediary point is deleted.
 To configure a maintenance intermediary point:

• Navigate to configure oam cfm maintenance-domain <mdid> mip <mipid> to
select the maintenance association to configure.
The config>oam>cfm>md(<mdid>)>mip(<mipid>)# prompt is displayed
Binding the MIP to an bind ethernet <slot/port> To remove the MIP from an Ethernet port,

no bind
and Tx flows to the MIP <tx-name>] uni-direction
Configuring MIP half mhf 1 See table below

functions (MHF) mhf 2
Administratively enabling no shutdown To deactivate the MIP, enter shutdown

MIP
Displaying MIP status show status
The following marking actions can be performed at the mhf level, at the
config>oam>cfm> md(<mdid>)>mip(<mipid>)>mhf(1 or 2)# prompt.
Associating the MHF with a classification profile <profile_name> Classifier profile is needed when the MHF
All).
11-64 OAM CFM ETX-5

Associating the MHF with a cos-mapping profile <profile_name> The CoS mapping profile must be
to the packets transmitted by the MHF
(CCMs, LBTs etc).
MHF <queue_mapping_profile_name> queue queue-mapping
Configuring Maintenance Endpoint Services

You can configure up to eight services on a MEP. The service configures
performance monitoring (Y.1731) functionality for loss and delay measurements.
The statistics are disaplyed at the destination NE level.
 To add a MEP service:

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> The allowed range is 0–7
priority for LMMs and DMMs
Specifying delay threshold in delay-threshold <delay-thresh> The allowed range for delay
microseconds threshold is: 1–5,000,000. If the
threshold is exceeded, the
service is declared as degraded.
ETX-5 OAM CFM 11-65

Specifying delay variation delay-var-threshold <delay-var-thresh> The allowed range for delay
threshold in microseconds variation threshold is:
1–5,000,000. If the threshold is
exceeded, the service is
declared as degraded.
Specifying the interval for dmm-interval {100ms | 1s | 10s}

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

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

service below. The value range is
1–255. One NE per service is
allowed for user-data LM and up
to 64 NEs for synthetic LM.
To delete a destination NE,
enter no dest-ne.
Selecting loss measurement loss { single-ended} [{synthetic | user- no loss disables loss
method data}] measurement
no loss
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.
Configuring Destination NEs

For performance measurement, the exact address of the destination NE must be
known. You can configure the remote MAC address of the NE, or ETX-5 can learn
it from the CCM messages. You can define a single NE per MEP service.
If the remote MAC address is not configured and needs to be learned,
performance measurement messages are sent with all 0s in the MAC address until
the address is learned.
 To add a destination NE:

• At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service
(<serviceid>)#, enter: dest-ne <dest-ne-index>
where <dest-ne-index> is 1–255.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)$ is displayed.
11-66 OAM CFM ETX-5

 To configure a destination 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.
Defining the MAC address or remote mac-address <mac>

mep-id of the destination NE
Enabling two-way delay delay two-way

measurement method no delay
Enabling loss measurement loss { single-ended }

method no loss
Defining the delay delay-measurement-bin profile <name>

measurement bin profile to
use as delay bin policy
Defining the delay variation delay-var-measurement-bin profile

measurement bin profile to <name>
use as delay variation bin
policy
Displaying the delay show delay-measurement-bins

measurement bins
Collecting performance pm-collection [interval <1–900>] Statistic collection interval can

monitoring data to be no pm-collection be defined in the 1–900
presented via RADview second range
Performance Management no pm-collection disables
portal statistic data collection
Displaying statistics data show statistics
Configuring a Measurement Bin Profile

The maintenance bin profile aggregates performance monitoring data into
measurement bins. Each bin stores a counter of the results for a user-defined
range of values (in milliseconds). The user creates a measurement bin profile,
containing a range of sample values with a counter of the number of samples
that were received that fall within that range. This measurement bin profile is
attached to a destination NE within a MEP service (see Configuring Destination
NEs). You can configure measurement bins in the range of 0 to 1000 msec.
 To configure a measurement bin profile:

1. Navigate to configure oam cfm.
ETX-5 OAM CFM 11-67

The config>oam>cfm prompt is displayed

2. Enter the measurement profile level: measurement-bin-profile
<profile_name>.
The prompt config>oam>cfm>measurement-bin-prof(<name>)# is
displayed.
3. Define bins by entering their upper levels, separated by commas without
spaces between the values: thresholds <bin_value>,<bin_value>. You can also
enter each value separately.
 To delete the measurement bin profile:

• At the config>oam>cfm# prompt, enter no measurement-bin-profile
<profile_name>.
For example:
 To create profile 1 containing 0–20, 21–40 and 41–100 measurement bins:

ETX-5>config>oam>cfm measurement-bin-profile 1
ETX-5>config>oam>cfm>measurement-bin-prof(1)$ 20,40,100
Displaying OAM Statistics

You can display end-to-end performance monitoring data for the destination NEs.
ETX-5 measures current performance and stores performance data for the last 24
hours (96 intervals).
You can view the following types of statistics for services:
• Running – OAM statistics collected since the service was activated
• Day – OAM statistics for the last 24 hours, or the amount of time since the
service was activated, if less than 24 hours
• Interval – OAM statistics for the current interval or a selected interval. You
can select an interval only if it has already ended.
When a service is first activated, you can view statistics for the current
interval only. 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.
You can view the following types of statistics for destination NEs:
• Running – OAM statistics collected since performance measurement of the NE
started
• Day – OAM statistics for the last 24 hours
• Interval – OAM statistics for the current interval or a selected interval.
11-68 OAM CFM ETX-5

 To display the OAM CFM statistics for a destination NE:

1. Navigate to the level corresponding to the destination NE for which you wish
to view the statistics (configure oam cfm maintenance-domain <mdid>
<dest-ne-index>).
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>
service(<serviceid>)>dest-ne(<dest-ne-index>)#.
Viewing running statistics show statistics running The statistics are displayed
as listed in the table below.
Viewing statistics for the current show statistics current The statistics for the current
interval interval are displayed as
listed in the table below.
Viewing the statistics for a show statistics interval <interval-num> Allowed values for
selected interval interval-num: 1–96
The statistics for the
selected interval are
displayed as listed in the
table below.
If you specified an interval
that has not yet ended, a
message indicates that the
interval does not exist.
Viewing statistics for current day show statistics current-day The statistics for the current
day, as listed in the table
below.
Viewing statistics for previous show statistics previous-day The statistics for the
day previous day, as listed in the
table below.
Viewing running statistics, show statistics all All available performance

statistics for the current interval, measurement counters, as
statistics for all intervals, and day listed in the table below.
statistics
Viewing statistics for all intervals show statistics all-intervals Performance measurement
counters for all available
Intervals, as listed in the
table below.
Clearing the statistics for the clear-statistics Running and current

destination NE statistical data for the
service is cleared. Interval
statistics are preserved.
ETX-5 OAM CFM 11-69

Table 11-8. OAM Statistic Counters
Far End Tx Frames Total number of OAM frames transmitted from the local MEP to the
remote MEP since the service was activated
Far End Rx Frames Total number of OAM frames received by the remote MEP since the
service was activated
Far End Lost Frames Total number of OAM frames lost from the local MEP to the remote MEP
Far End Frame Loss Ratio (%) Total number of OAM frames lost from the local MEP to the remote MEP,
divided by the total number of OAM frames transmitted since the service
was activated
Far End Unavailable Seconds Total number of unavailable seconds in the remote MEP since the service
(sec) was activated
Near End Tx Frames Total number of OAM frames transmitted from the remote MEP to the
local MEP since the service was activated
Near End Rx Frames Total number of OAM frames received by the local MEP since the service
was activated
Near End Lost Frames Total number of OAM frames lost from the remote MEP to the local MEP
Near End Frame Loss Ratio (%) Total number of near end lost OAM frames divided by the total number
of near end transmitted OAM frames
Near End Unavailable Seconds Total number of unavailable seconds in the local MEP since the service
(sec) was activated
Average Two Way Delay (msec) Average delay
Frames Above Delay Threshold Number of frames that exceeded the delay threshold
Frames Above Delay Variation Number of frames that exceeded the delay variation threshold
Threshold
Min Two-Way Frame Delay The minimum two-way frame dealy measurement in microseconds
Max Two-Way Frame Delay The maximum two-way frame dealy measurement in microseconds
Average Two Way Delay Var The average (arithmetic mean) two-way FDV measurement in
(mSec) microseconds (interval statistics only)
Min Two-Way Frame Delay The minimum two-way frame dealy variation measurement in
Max Two-Way Frame Delay The maximum two-way frame dealy variation measurement in
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated
11-70 OAM CFM ETX-5

statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Two Way Delay (mSec) : 0.000 mSec

Two Way IFDV (mSec) : 0.000 mSec

Figure 11-39. OAM CFM Running Statistics
statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Min Average Max



Figure 11-40. OAM CFM Current Statistics
statistics interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Valid Data : Valid
Time Stamp : 2014-07-06 08:45:00.0
Duration (Sec) : 900
Forward Backward
ETX-5 OAM CFM 11-71

Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Min Average Max

Figure 11-41. OAM CFM Interval Statistics
Performing OAM Loopback

This diagnostic utility verifies OAM connectivity on Ethernet connections. You can
execute the loopback according to the destination MAC address.
 To run an OAM loopback:

Specifying remote MEP by lbm address <mac_address> [repeat <1–

MAC or mep-id address 50>]
lbm remote-mep <mep-id> [1..8191]
Checking OAM loopback show lbm-results

results
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified by MAC
address.
 To run an OAM link trace:

Specifying remote the MEP by linktrace address <mac-address> The TTL parameter specifies
MAC or mep-id address [ttl <1–64>] the number of hops. Each unit
linktrace remote-mep <mep-id> in the link trace decrements
[1..8191] the TTL until it reaches 0,
which terminates the link trace.
Destnation MAC address LTM
cannot be multicast.
Checking the OAM link trace show linktrace-results

results
11-72 OAM CFM ETX-5

Examples
This section illustrates OAM configuration for three MEP instances (two Down
MEPs and one Up MEP).
Example 1. Down MEP between Main Card Ports

This example shows how to create a Down MEP located between two main card
ports and bound to one of them (see the figure below).
 To configure a Down MEP between main card ports:

 Loss ratio
CCMs
EVC1_ing
LMMs
MEP PSN MEP
EVC1_eg LMRs DMMs
Main Card B Main Card B DMRs

Remote NE
Port 2 Port 1
Figure 11-42. Down MEP between Main Card Ports
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
ETX-5 OAM CFM 11-73


exit all
#*********************************End********************************************
match vlan 20
exit all
#*********************************End****************************************
exit all
#*********************************End********************************************
map 0 to-cos 0
map 1 to-cos 1
map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
classifier class20
no shutdown
exit all

classifier class20
no shutdown
exit all
#*********************************End********************************************
20,100,300,1000
40,200,600,1000
11-74 OAM CFM ETX-5

exit all
#*********************************End********************************************
config oam cfm
md-level 4
name uint 265
mep 1
direction down
flow uni-direction rx EVC1_eg tx EVC1_ing
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1
dest-ne 1
remote mac 00-20-d2-50-1d-28
exit
no shutdown
exit all
#*********************************End********************************************


exit all
#*********************************End********************************************
Example 2. Down MEP between Main and I/O Card Ports

T This example shows how to create a Down MEP located between the I/O and
main card ports and bound to the main card port (see the figure below).
 To configure a Down MEP between main and I/O card ports:

1. Assign default queue groups to the I/O and main card ports, and to SAG 1.
2. Select classification keys for the main and I/O card ports.
4. Configure classifier profiles:
ETX-5 OAM CFM 11-75


 VLAN 300 + inner VLAN 100.
 From SAP to main card port 1
 From main card port 1 to I/O card port 1.
 Loss ratio
SAG
SAP
CCMs
ECV2COS1
EVC2_eg LMMs
Port 1 SAP 1 Port 1 PSN MEP
ECV2COS2 MEP LMRs DMMs
EVC2_ing
DMRs
Remote NE
SAP
I/O Ethernet Card Main Ethernet Card
Figure 11-43. Down MEP between Main and I/O Card Ports
exit all
#*********************************End********************************************
11-76 OAM CFM ETX-5

config port ethernet main-b/1 classification-key vlan inner-vlan p-bit
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
exit all


exit all
#*********************************End****************************************
exit all
#*********************************End********************************************
map 0 to-cos 0
map 1 to-cos 1
map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
configure flows flow ECV2COS1
cos-mapping fixed 0
ingress-color green
policer profile 1
no shutdown
exit all
ETX-5 OAM CFM 11-77

configure flows flow EVC2COS2

cos-mapping fixed 1
ingress-color green
policer profile 2
no shutdown
exit all

vlan-tag push vlan 300 p-bit copy
no shutdown
exit all

vlan-tag pop vlan
no shutdown
exit all
#*********************************End********************************************
20,100,300,1000
40,200,600,1000
exit all
#*********************************End********************************************
config oam cfm
name uint 22
mep 2
direction down
flow uni-direction rx EVC2_ing tx EVC2_eg
ccm-initiate
ccm-priority 0
remote-mep 110
11-78 OAM CFM ETX-5

no shutdown
service 1
dest-ne 1
remote mac 00-20-d2-50-2e-55
exit
no shutdown
exit all
#*********************************End********************************************


exit all
#*********************************End********************************************
Example 3. Up MEP between Main Card and Bridge Ports

This example shows how to create an UP MEP located between main card and
bridge ports and bound to the bridge port via SVI (see the figure below).
 To configure a Up MEP between main card and bridge ports:

4. Configure VLAN-based classifier profile
6. Define bridge-type SVIs, bind the bridge ports to the SVIs, and configure the
ports as members of VLAN 20.
7. Configure six flows from the main card ports to the SVIs and vice versa.
9. Define an Up MEP bound to port 1 with CCM sent over P-bit 0.
 Loss ratio
ETX-5 OAM CFM 11-79

SVI
Flow 1 1
Port 1 MEP BP 1
Flow 2
SVI
Flow 3 2
Port 2 BP 2
Flow 4
SVI
Flow 5 3
Port 3 BP 3
Flow 6
Bridge
Main Ethernet Card
Figure 11-44. Up MEP between Main Card and Bridge Ports
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
exit all
#*********************************End****************************************
map 0 to-cos 0
map 1 to-cos 1
11-80 OAM CFM ETX-5

map 2 to-cos 2
map 3 to-cos 3
map 4 to-cos 4
map 5 to-cos 5
map 6 to-cos 6
map 7 to-cos 7
exit all
#*********************************End********************************************
***********************Configuring_Bridge_and_Bridge_Ports***********************
exit all

exit all

exit all

bind svi 1
no shutdown
exit all

bind svi 2
no shutdown
exit all

bind svi 3
no shutdown
exit all
config bridge 1 vlan 20 tagged-egress 1..3

exit all
#*********************************End********************************************
******************************Adding_Flows***************************************
config flows flow 1
classifier class20
egress-port svi 1
no shutdown
exit all
config flows flow 2

classifier class20
ingress-port svi 1
no shutdown
exit all
ETX-5 OAM CFM 11-81

config flows flow 3

classifier class20
egress-port svi 2
no shutdown
exit all
config flows flow 4

classifier class20
ingress-port svi 2
no shutdown
exit all
config flows flow 5

classifier class20
egress-port svi 3
no shutdown
exit all
config flows flow 6

classifier class20
ingress-port svi 3
no shutdown
exit all
#*********************************End********************************************
20,100,300,1000
40,200,600,1000
exit all
#*********************************End********************************************
config oam cfm
md-level 3
name uint 37
mep 3
bind svi 1
direction up
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1
11-82 OAM CFM ETX-5

dest-ne 1
remote mac 00-20-d2-50-1d-28
exit
no shutdown
exit all
#*********************************End********************************************


exit all
#*********************************End********************************************
Example 4. RMEP Configuration

The example below shows the CLI configuration of the remote-mep in service.
config oam cfm
md-level 3
ccm-interval 1s
name uint 256
mep 201
direction down
ccm-initiate
ccm-priority 0
remote-mep 101
no shutdown
service 1
delay-threshold 100
dest-ne 1
remote mep-id 101
exit
no shutdown
error is detected.
ETX-5 OAM CFM 11-83

Message Description
Mismatch between flow and MIP The classification profile bound to the MIP and the classification
classification profiles profiles of its Rx/Tx flows do not match
Flow must be enabled The flow must be administratively enabled before it is bound to
the MEP/MIP
Maximum number of MEPs (8) associated A single flow can be bound to up to eight MEPs
with the flow has been reached
Different MEPs/MIPs, using the same When the same flow is bound to different MEPs/MIPs, the flow
flow, must have different MD levels must have different MD levels
MIP bound to Ethernet port or LAG must When a MIP is bound to an Ethernet port or LAG, the MIP must
have classification profile have a classification profile assigned to it
MIP-bound bridge port is not a member The bridge port of the SVI to which the MIP is bound is not a
of the MHF’s classification profile VLAN member of the VLAN defined in the VLAN-based classification
profile used by the MIP’s MHF
MEP is not bound to a port A MEP must be bound to an Ethernet port, LAG or bridge-type
SVI
Cannot bind CoS mapping profile to a The CoS profile cannot be bound to a MEP bound to an Ethernet
MEP bound to an Ethernet port or LAG port or LAG
Cannot bind queue mapping profile to a The queue mapping profile cannot be bound to a MEP bound to
MEP bound to an Ethernet port or LAG an Ethernet port or LAG
Up MEPs are bound to SVI (B), Down The Up MEP must be bound to a bridge-type SVI. The Down MEP
MEPs are bound to Ethernet port or LAG must be bound to an Ethernet port or LAG
MA number is out of range The MA number is out of range (1–2048)
Cannot delete MA with MEPs The MA cannot be deleted if it has MEPs defined under it
Current MA name is already in use A name assigned to the MA already exists
Cannot change MA with MEPs The MA parameters cannot be changed if the MA has MEPs
defined under it
Cannot change MA with MIPs The MA parameters cannot be changed if the MA has MIPs
defined under it
The value is out of range The value entered not within the allowed range
MA name is out of range The MA name value is not within the allowed range (0–6535)
Max number of MEs has been reached The maximum number of MEs (4096) has been reached
Max value has been reached The maximum value for the current parameters has been
reached. This may refer to the number of MEPs/MIPs, remote
MEPs, destination NEs, etc.
Max number of Down MEPs per MA has Only one Down MEP is allowed per MA
been reached
Max number of Up MEPs per MA has Up to 88 Up MEPs are allowed per MA

been reached
11-84 OAM CFM ETX-5

Message Description
Entity must be in shutdown The entity (MEP, MIP, port, etc.) must be administratively
disabled in order to delete or change its parameters
Port does not exist The port to which you are trying to bind a MEP/MIP does not
exist
MEP/MIP port is not Ethernet, LAG or SVI The port to which you are trying to bind a MEP/MIP is not
Ethernet, LAG or SVI
SVI must be of bridge type The SVI to which you are trying to bind a MEP/MIP is not a bridge
type
VLAN ID is out of range The selected VLAN ID is not within the allowed range (0–4094)
VLAN ID can be changed in MEP/MIP The VLAN ID can be changed only when the MEP/MIP is
shutdown administratively disabled
Classification profile can be changed in Assigned classification profile can be changed only when the
MEP/MIP shutdown MEP/MIP is administratively disabled
Invalid classification profile The classification profile bound to the MEP/MIP is not valid.
Profile does not exist A non-existing classification or CoS mapping profile has been
bound to MEP/MIP
CoS mapping profile must be P-bit-to- Only a P-bit-to-CoS CoS mapping profile can be bound to
CoS MEP/MIP
Only default queue mapping profile is Only a default queue mapping profile (QueueMapDefaultProfile)
allowed can be bound to MEP/MIP
Port can be changed, when MEP/MIP is in The port to which a MEP/MIP is bound can be changed only
shutdown when the MEP/MIP is administratively disabled
LTM destination MAC cannot be multicast The destination MAC address for OAM link trace messages
cannot be a multicast type
destination NE exists destination NE has been defined for it
destination NE MAC exists destination NE MAC address has been defined
Destination NE MAC can be unicast only The MAC address of the destination NE can be a unicast type
only
MEP Rx flow must be configured The Rx flow for the MEP has not yet been configured
MEP Tx flow must be configured The Tx flow for the MEP has not yet been configured
I/O port-to-SAP flow must be configured For Rx flow with ingress port defined as SAP, there must be a
for Rx flow with SAP as ingress port matching flow between I/O port and SAP
Illegal ingress port for Rx or Tx flow The ingress port for Rx and Tx flows must be an Ethernet port,
LAG, bridge-type SVI or SAP
Classification profile must be bound to If Rx flow uses the Match All classification mode, a separate
MEP/MIP, if Rx flow uses Match All classification profile must be bound to the MEP/MIP
classification
ETX-5 OAM CFM 11-85

Message Description
Classification profile must be bound to If Tx flow uses the Match All classification mode, a separate
MEP/MIP, if Tx flow uses Match All classification profile must be bound to the MEP/MIP
classification
Classification profile cannot be bound to If Rx flow does not use the Match All classification mode, a
MEP/MIP, if Rx flow uses other than separate classification profile cannot be bound to the MEP/MIP
Match All classification
OAM service must be in shutdown The OAM service must be administratively disabled for this
action
MEP must be in no shutdown The MEP to be administratively enabled for this action
Illegal number of MDs The number of MDs is out of range (1–2048)
Cannot delete MD with MA or MIP under An MD with existing MAs or MIPs cannot be deleted
it
Illegal MD level The MD level value is out of allowed range (0–7)
Cannot change MD level The MD level cannot be changed if the MD has MEPs/MIPs under
it
Max number of MDs has been reached The maximum number of MDs (4096) has been reached
Bin profile is in use and cannot be The measurement bit profile is in use and cannot be deleted or
changed modified
11.6 OAM EFM

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-5 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.
Standards
IEEE 802.3ah
Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
11-86 OAM EFM ETX-5

Factory Defaults
By default, OAM EFM is not enabled for Ethernet ports.
OAM EFM is specified by IEEE 802.3ah and can be implemented on any full-duplex
point-to-point or emulated point-to-point Ethernet link.
OAM EFM messages are sent in untagged slow protocol frames called OAM
Protocol Data Units, or OAMPDUs. They cannot propagate beyond a single hop
within an Ethernet network and have modest bandwidth requirements (frame
transmission rate is limited to a maximum of 10 frames per second).
802.3ah 802.3ah
Ethernet Ethernet
OAMPDUs MPLS OAMPDUs
Access Access
Core Network
Network Network
Customer Service Provider Service Provider Customer

Router Router
Equipment Edge Device Edge Device Equipment
Figure 11-45. 802.3ah OAM
Layer-2 Operation
OAM EFM operates purely at the Ethernet layer, and so (unlike SNMP or ping)
does not require an IP address. This means that Ethernet service providers do not
need to run IP protocols or manage IP addresses. Furthermore, special Ethernet
features may be directly supported, such as Ethernet multicast and slow protocol
frames. When an OAM frame is received by an OAM-enabled Ethernet MAC, it is
passed to the OAM client for processing; such a frame is simply discarded if
received by a MAC that does not support link-layer OAM. In any case, link-layer
OAM frames are never forwarded.
Since the IEEE link-layer OAM is generally used over a link between a service
provider and a customer, it defines two modes for OAM entities: active or
passive. The elements of the provider network (e.g. DSLAMs or provider Ethernet
switches) operate in active mode, and can exert control over the passive-mode
devices (e.g. DSL modems or customer premises switches). Thus, the active-mode
entity can send an LB command forcing the passive-mode device into loopback
mode, and query the configuration parameters of the passive-mode device.
However, the reverse is not possible.
OAMPDUs
The OAMPDUs perform the following functions:
• Discovery is the procedure whereby OAM-enabled entities discover each
other and exchange information regarding their OAM capabilities and
configuration. The OAM capabilities may be used to determine whether it is
worthwhile to run the OAM protocol.
Disovery is initiated by an active ETX-5 Ethernet port. It advertises the
following capabilities:
 Mode
ETX-5 OAM EFM 11-87

 Maximum PDU size

 Loopback support (active port only)
 Variable retrieval (not supported)
 Event notification
 Unidirectional operation.
• ETX-5 transmits link failure indication to the peer. ETX-5 terminates the
following 802.3ah events:
 Remote fail indication
 Critical alarm
 Dying gasp indication on remote device.
• Loopback control used by an active-mode OAM entity to enable or disable
intrusive loopback in the remote passive-mode device. Active ETX-5 ports
support EFM loopback request. Passive ports identify loopback requests, and
close the EFM loop.
RAD OUI
OAMPDUs use RAD OUI (Organizationally Unique Identifier) – 00-20-D2.
MAC Address
OAMPDUs use the relevant port MAC as the MAC SA. To support OAM EFM, the
user must configure trap the 01-80-C2-00-02, using L2CP mechanism.
To ensure correct distribution of EFM traffic, you must configure flow with an
L2CP profile with peer action for the OAM EFM address (01-80-c2-00-00-02). The
flow must have the following attributes:
• Ingress port – Ethernet port
If you use the flow only to peer the EFM frames and do not need to forward the
Configuring OAM EFM

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

1. Navigate to configure>oam>efm.
2. Enter: descriptor <number> {active | passive}.
 To configure OAM EFM for Ethernet port:

1. Navigate to configure port ethernet <slot/port>.
11-88 OAM EFM ETX-5

Enabling OAM EFM, and defining efm-descriptor <1–2> {active | The EFM descriptor must exist
its operation mode passive} before you can assign it to a
port.
Note: In order for OAM EFM to
function properly, the relevant
Ethernet port must be
associated with an L2CP profile
that specifies peer action for
MAC 01-80-C2-00-02.
Requesting OAM EFM loopback loopback no loopback disables OAM EFM

activation from remote device no loopback loopback initaition request.
This command is relevant for
active OAM EFM mode only.
Displaying OAM EFM status show oam-efm
Displaying OAM EFM statistics show oam-efm-statistics
Clearing OAM EFM statistics clear oam-efm-statistics
Displaying OAM EFM Status

OAM CFM status is supported at the port level.
 To display OAM EFM status:

• In the config>port>eth(<slot/port>)# prompt, enter show oam efm.
The status screen appears.
ETX-5>config>port>eth(1/1)# show oam efm
Administrative Status : Enabled
Operetional Status : Operational
Loopback Status : Off
OAM EFM Information

---------------------------------------------------------------
Local Remote
MAC Address : 00-20-D2-F8-80-5B 00-20-D2-F8-80-5C
Mode : Active Active
Unidirectional : Supported Supported
Vars Retrieval : Not Supported Not Supported
Link Events : Not Supported Supported
Loopback : Not Supported Supported
PDU Size : 1500 1518
Vendor OUI : 0x0020D2 0x0020D2
ETX-5 OAM EFM 11-89

Displaying OAM EFM Statistics

OAM EFM statistic collection is supported at the port level.
 To display OAM EFM statistics:

• In the config>port>eth(<slot/port>)# prompt, enter show oam efm statistics.
The statistics screen is displayed.
ETX-5>config>port>eth(1/1)# show oam efm statistics
OAM EFM Statistics

---------------------------------------------------------------
Rx Tx
Information : 31 31
Loopback Control : 0 0
Example
 To enable OAM EFM on Ethernet port B/4:
#******************Assigning_Default_Queue_Group_Profiles********************
#*********************************End****************************************
************************Defining_Classifier_Profiles*************************
match untagged
exit all

match all
exit all
#*********************************End****************************************
#***************************Adding_L2CP_Profile******************************
configure port l2cp-profile l2cp1 mac 01-80-c2-00-00-02 peer
#*********************************End****************************************
#**************************Adding_Flow_for_Peering_EFM_Traffic***************
classifier classutg
0/1
l2cp profile l2cp1
drop
pm-enable
no shutdown
exit all
#*********************************End****************************************
#***************************Adding_OAM_EFM_Descriptor************************
configure oam efm-descriptor 2 passive
11-90 OAM EFM ETX-5

exit all
#*********************************End****************************************
#**************************Configuring_Ethernet_Port*************************
configure port ethernet main-b/4 efm descriptor 2
exit all

no shutdown
exit all
#*********************************End****************************************
11.7 Port/VLAN Mirroring

Port/VLAN mirroring allows traffic flows to be inspected without disrupting the
flow. Traffic on the mirrored port is duplicated and sent to the mirror port. ETX-5
supports both in-bound mirroring of port ingress traffic and out-bound mirroring
of port egress traffic.
Standards
N/A
Benefits
Port/VLAN mirroring allows traffic flows to be inspected without disrupting the
flow.
Inbound Mirroring
Inbound mirroring can be configured on a main card port or main card as per-port
mirroring or per-port + VLAN, with a list of up to six VLANs. The destination mirror
port must be a main card port.
Outbound Mirroring
Outbound mirroring can be configured on a main card port or main card LAG as
per-port mirroring only.
The destination mirror port can be configured as follows:
• Main card ports
• Up to two different mirror ports
• TDM card redundancy consumes outbound mirroring resources. For example,
if TDM card redundancy is configured, only one mirror port is available. If two
TDM card redundancy pairs are configured, outbound mirroring is not
available.
ETX-5 Port/VLAN Mirroring 11-91

Factory Defaults
N/A
Configuring Port/VLAN Mirroring

 To configure mirroring:
1. Navigate to config#.
Enable/disable mirroring [no] mirroring-session<num> [no] mirroring-session

enables/disables flow mirroring.
<num> is the mirroring-session
number
Configure port/port+VLAN [no] source {port <port-type> add/remove source

<port-index> [vlan <vlan-list>] | {tx port/port+VLAN from the mirroring
| rx | tx-rx} session
tx – enable inbound mirroring
rx – enable outbound mirroring
tx-rx – enable both inbound and
outbound mirroring; supported for
port mirroring only
• vlan-list is not supported for
outbound mirroring (tx)
• Up to 6 vlans can be
configured per main card port
or LAG
• Up to 7 source ports or port +
vlan list can be configured per
mirroring sessions
[no] destination <port-type> add/remove destination port from

<port-index> the mirroring session
In the following example, all the traffic coming into (inbound) main a/1 and going out of (outbound)
main a/1 is mirrored to port b/1.
ETX-5>config# mirroring-session 1
ETX-5>config>mirroring-session(1)# source port ethernet main-a/1 tx-rx
ETX-5>config>mirroring-session(1)# destination ethernet main-b/1
In the following example, all the traffic going out of LAG 1 (LAG between main card ports) is
mirrored to port b/3.
ETX-5>config# port lag 1
11-92 Port/VLAN Mirroring ETX-5

ETX-5>config>port>lag(1)admin-key ten-giga-ethernet
ETX-5>config>port>lag(1)bind ethernet main-a/2
ETX-5>config>port>lag(1)bind ethernet main-b/2
ETX-5>config>port>lag(1)queue-group profile q_group_2_level_default
ETX-5>config>port>lag(1)lacp tx-activity active tx-speed slow
ETX-5>config>port>lag(1)no shutdown
ETX-5>config>mirroring-session(2)# source port ethernet lag 1 tx
In the following example, all the traffic coming into main a/3 with VLANs 100-103,110,120,130 and
all the traffic coming into main a/4 with VLANs 100,200-205 is mirrored to port b/4.
ETX-5>config>mirroring-session(3)# source port ethernet main-a/3 vlan-list
100..103,110,120,130 rx
ETX-5>config>mirroring-session(3)# source port ethernet main-a/4 vlan-list
100,200..204 rx
error is detected.
Table 11-10. Configure Error Messages
A destination port can only You used the wrong kind of Use either a main card or a
be a main card or a LAG port. The destination port LAG port that is bound to a
port. must either be a main card main card as a destination
or a LAG port that is bound port.
to a main card port.
A source port can only be a You used the wrong kind of Use either a main card or a
main card or a LAG port. port. The source port must LAG port as a source port.
either be a main card or a
LAG port that is bound to a
main card.
LAG members should only The LAG members of this Use one of the following as
be ports on main cards. LAG are not ports on a a source or destination of
main card. Therefore, this the mirroring session:
LAG cannot serve as a • One of the ports on the
source or destination port main card
for a mirroring session.
• A LAG whose the
members are ports on a
main card
ETX-5 Port/VLAN Mirroring 11-93

Outbound mirroring is not The outbound source port Select an outbound source
supported for port+VLAN. had a VLAN configuration port without a VLAN
defined for it. Outbound configuration.
source ports may not have
a VLAN configuration
defined for them.
The maximum number of You attempted to open a Remove one of the

mirroring sessions has new mirroring session even mirroring sessions in order
already been configured: Up though the maximum to create new mirroring
to seven mirroring sessions number (seven) of session.
are supported. supported mirroring
sessions was already
configured.
The maximum number of You attempted to configure Remove some of the

outbound mirroring more than two outbound outbound mirroring
sessions has already been mirroring sessions/TDM sessions so that there are
configured: Up to two card protection sessions. no more than two
outbound mirroring outbound mirroring
sessions/TDM card sessions.
protection sessions are
supported.
The maximum number of You attempted to configure Remove one of the source
source ports has already more than seven source ports in order to add a new
been configured: Up to ports in the same mirroring source port.
seven source ports are session.
supported in each session.
The maximum number of You attempted to configure Remove some of the VLANs
VLANs per source port has more than six VLANs on the so that there are no more
already been configured: Up same source port. than six VLANs per port.
to six VLANs per source
port are supported.
The mirroring session index You have attempted to Configure a mirroring

is wrong: Mirroring sessions configure a mirroring session with an index
1...7 are supported. session with an index number 1…7.
number that is not
supported.
The port/LAG should be in You did not activate the Activate the port/LAG.
no-shutdown in order to port/LAG.
perform this action.
The same destinations You used the same Define a different

cannot be defined for destination for several destination for each
different sessions. different sessions. The session.
same destination may not
be defined for more than
one session at a time.
11-94 Port/VLAN Mirroring ETX-5

The specified destination The destination port that Bind the port to a queue
port is not bound to a you specified is not bound group.
queue group. to a queue group.
This port is a LAG member You attempted to define Select the LAG itself or
and cannot be defined as a this port as a destination another main card port that
destination port. port. Since this port is a is not part of the LAG as
LAG member, it may not be the destination port.
defined as a destination
port.
This port is a LAG member You attempted to define Select the LAG itself or
and cannot be defined as a this port as a source port. another main card port that
source port. Since this port is a LAG is not part of the LAG as a
member, it may not be source port.
defined as a source port.
This port is already being You attempted to define Select another main card
used as a destination port this port as a source port. port as a source port.
and cannot be defined as a Since this port is already
source port. being used as a destination
port, it may not be defined
as a source port.
This port is already being You cannot define this port Select another main card
used as a source port and as a source port because it port and define it as your
cannot be defined as a is already being used as a destination port.
destination port. destination port.
This source port is already This source port is already Do not use a source port
being used as a source port being used in another that is being used in
in another session. session. another session.
This source port+VLAN is This source port+VLAN is Use a source port+VLAN

already being used as a already being used as a that is not being used in
source port+VLAN in source port+VLAN in another session.
another session. another session.
11.8 In-Service Ping
Benefits
In-service ping provides a simple connectivity test across L2 service paths.
ETX-5 In-Service Ping 11-95

In-Service Ping enables a single CLI command to perform a simple connectivity
check across L2 service paths without the need for complicated configuration
such as required in TWAMP.
In addition, In-Service Ping includes a mechanism to enable a connectivity test
across the flow inside the device, by configuring the entry point of ICMP packets
to the flow (either at flow ingress or egress).
E
t
E
p
t
p
L
L2 (VPLS)
2 Network
P s
i e
n r
g v
i
c
e
In-Service Ping is supported for the following topologies:

• Point-to-point E-line service
• Multipoint-to-multipoint E-LAN (Bridge) services
In-Service ping is supported for IPv4 IP interfaces only (for both point-to-point
and multipoint-to-multipoint). One In-Service Ping instance is supported. In-
Service Ping runs independently of working routers and occupies a dedicated VRF.
ETX-5 can initiate the connectivity test, as well as respond to In-Service Ping
requests sent over L2 services to a configured IP address.
You can invoke two types of command:
• In-service ping request –run this command at the device generating the ping
test
• In-service ping response –run this command at the device that responds to
the ping-request packets with ping-response packets. This command
11-96 In-Service Ping ETX-5

configures the IP stack to listen to ping-requests being sent over a particular

flow, targeted to a provisioned IP address.
When you invoke an in-service ping test, a temporary IP interface is created on
the device, as well as a routing entry in the static routing table.
Note In-service Ping is not supported over Multicast IP.

The IP range 240.0.0.0/4 is reserved. Do not use these addresses for in-service
Ping.
In-service ping is available from the ‘flow’ level of the CLI.
 To initiate an in-service ping request:

1. Navigate to device configure flows.

Table 11-11. In-service Ping Request/Response Command Parameters
Perform standard in- service-ping local-ip <src-ip- local-ip – The temporary IP address
service ping for egress address/mask> dst-ip <dst-ip- provisioned on the sender/responder for the
ports address> next-hop <next-hop-ip- duration of the test, combined with subnet-
address> {egress- mask.
port {ethernet <[slot/]port> | lag dst-ip – The IP address to which in-service
<number>} [vlan <vlan-id ping request packets are destined.
0..4095> ] [inner-vlan <inner-vlan-
next-hop – Next hop to use when
id 0..4095> ] [ p-bit <p-bit-id
destination IP is out of the source subnet.
0..7> ] [inner-p-bit <inner-p-bit-id
0..7>] [number-of- egress-port – This is either physical or
packets <1..10000>] [payload- logical interface to which the ping request is
size <32.. 1450 bytes>] sent . The supported egress ports are
ethernet and lag.
vlan (optional) – the VLAN ID defining the

flow the service runs in
inner-vlan (optional) –inner VLAN ID defining
the flow the service runs in
p-bit –The service VLAN priority bit used
when encapsulating the ping packet
inner-p-bit –The inner-VLAN priority bit used
The vlan-related parameters are possible
only in the following combinations:
• You cannot configure p-bit without vlan.
• You cannot configure inner-p-bit without
inner-vlan.
• You cannot configure inner-vlan without
vlan.
number-of-packets – Number of in-service
ping request packets for the test <1-10000>
(default=5)
payload-size – Payload size of the in-service
ping request packets <32-1450>
(default=32)
The dst-ip IP address must be the same as
the IP address in local-ip in the service-ping-
response command configured on the
opposite device.

Perform standard in- service-ping local-ip <src-ip- local-ip – The temporary IP address
service ping for bridge address/mask> dst-ip <dst-ip- provisioned on the sender/responder for the
ports address> next-hop <next-hop-ip- duration of the test, combined with subnet-
address> bridge <number> mask.
vlan <vlan-id 0..4095> [inner- dst-ip – The IP address to which in-service
vlan <inner-vlan-id ping request packets are destined.
0..4095> ] [number-of-packets
next-hop – Next hop to use when
<1..10000>] payload-size <32..
destination IP is out of the source subnet.
1450 bytes>]
bridge – Number of the bridge to which the
ping request is sent.
vlan (mandatory) – the VLAN ID defining the
number-of-packets – Number of in-service
ping request packets for the test
payload-size – Payload size of the in-service
ping request packets
opposite device.

Initiate an in-service service-ping-response local-ip <src- local-ip – The temporary IP address

ping response for ip-address/mask> next-hop <next- provisioned on the sender/responder for the
egress ports hop-ip-address> { egress- duration of the test, combined with subnet-
port {ethernet <[slot/]port> | lag mask.
<number> } [vlan <vlan-id next-hop – Next hop to use when
0..4095> ] [inner-vlan <inner-vlan- destination IP is out of the source subnet.
id 0..4095> ] [ p-bit <p-bit-id
egress-port – This is either physical or
0..7> ] [inner-p-bit <inner-p-bit-id
logical interface from which the ping
0..7>]
response is received. The supported egress
ports are ethernet and lag.
vlan (optional) – the VLAN ID defining the
p-bit –The service VLAN priority bit used
inner-p-bit –The inner-VLAN priority bit used
The vlan-related parameters are possible
only in the following combinations:
• You cannot configure p-bit without vlan.
• You cannot configure inner-p-bit without
inner-vlan.
• You cannot configure inner-vlan without
vlan.
opposite device.
Initiate an in-service service-ping-response local-ip <src- local-ip – The temporary IP address
ping response for ip-address/mask> next-hop <next- provisioned on the sender/responder for the
bridge ports hop-ip-address> bridge <number> duration of the test, combined with subnet-
vlan <vlan-id 0..4095> [inner- mask
vlan <inner-vlan-id 0..4095> ] next-hop – Next hop to use when
destination IP is out of the source subnet
bridge –Number of the bridge from which
the ping request is received
vlan (mandatory) – the VLAN ID defining the
The IP address in local-ip command must be
the same as the dst-ip IP address in the
service-ping command configured on the
opposite device.

 To initiate an in-service ping response:

1. Navigate to flow configuration.
2. Enter all necessary commands according to the tasks listed in the table
above.
The maximum transmission rate of in-service-ping requests is 1/Sec. If a response
packet is received before the 1 second maximum rate, the next request is sent 1
second after the previous request. A ping packet is declared lost if no response is
received within 2 seconds. In this case, a corresponding message (“Destination
net unreachable”) is echoed back to the requesting screen, and the next in-
service ping request is transmitted immediately.
You can terminate the in-service ping test before the indicated number of
packets has been transmitted by pressing Ctrl-C.
KPIs (Key Performance Indicators) returned by the In-service ping test are:
• Packet RTT
• Packet loss percentage
• Minimum/average/maximum RTT per the entire test
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
You can block responses from the target and ping requests from the source.
Ping requests and responses can be blocked using the following commands:
no service-ping The device stops sending requests. A termination message

and test summary are displayed.
device>config>flows# no service-ping-response
current in-service test is interrupted
no service-ping- The device stops listening to in-ping-requests and clears
response any generated command context (the local IP address and
routing entry). Additionally, the device echos a termination
message to the user.
Current in-service ping test is interrupted:
<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>
11.9 Quality of Service (QoS)

ETX-5 employs enhanced traffic engineering techniques for efficient handling of
multi-priority traffic on per-flow basis. It performs pre- and/or post-forwarding
traffic management (TM), using advanced queuing, shaping, policing and mapping
mechanisms.
ETX-5 Quality of Service (QoS) 11-101

As illustrated in the data flow diagram in Chapter 1, pre-forwarding (ingress)

traffic management is performed at the Service Aggregation Group (SAG) of an
Ethernet I/O card for indirectly-attached ports ingress traffic. Post-forwarding
(egress) traffic management is done at both directly- and indirectly-attached
ports egress.
Standards
IEEE 802.1p, IEEE 802.1Q.
Benefits
Flexible Ethernet QoS and extensive TM capabilities allow ETX-5 to offer, monitor
and enforce different levels of Service Level Agreements (SLAs) for various
service types.
Factory Defaults
Refer to the following sections for the specific default for each type of QoS.
ETX-5 traffic management entities are called queue groups. They are configured
over SAGs or physical ports. The queue groups consist of 2- or 3-level scheduling
elements (queue blocks) per port type (see the description of Type-1, Type-2,
Type-3, Type-4, and Type 5 queue groups below). The queue blocks consist of
separate internal strict-priority or WFQ queues.
Scheduling Elements
Each scheduling element consists of strict or weight fair queues. In addition,
single- and dual-rate shapers operate at per-queue and per-scheduling-element
level to shape traffic into a required traffic profile (CIR, CBS or CIR/EIR, CBS/EBS).
The TM entities allow hierarchical scheduling and shaping at several levels. For
example, a 3-level TM entity schedules and shapes traffic at EVC, tunnel and port
levels. This means that several shaped EVCs can be bundled into one shaped
tunnel. A dual shaper at the EVC level ensures committed EVC CIR on the
aggregated tunnel while sharing the remaining traffic between the EIR part of the
other EVCs (see Dual Shaper and EIR Sharing below).
Similar bandwidth allocation can be made among the different tunnels at the port
level by committing on tunnel’s CIR and sharing the remaining port bandwidth
between tunnel’s EIR.
Dual Shaper and EIR Sharing

When using a dual shaper, the next level SE (aggregating several SEs from the
previous level) ensures committed traffic (as long as it is not oversubscribed) and
shares the remaining bandwidth with the EIR traffic of aggregated SEs per the
configured weights. As explained above, this allows a tunnel to aggregate several
EVCs while ensuring CIR of each one, and to share the remaining tunnel
11-102 Quality of Service (QoS) ETX-5

bandwidth with the EVCs EIR. The same procedure can be performed for tunnels
at the port level.
The figure below illustrates the hierarchical TM concept and the dual shaper
functionality. The magnified portion of the diagram details functionality of a
level-1 SE.

WFQ 1
CIR/EIR WFQ 2
Shaper
WFQ 383
SP 1
WFQ 384
WFQ 1
WFQ 2 SP 2
CIR/EIR
Shaper
WFQ 383
WFQ 384
Level-0 SEs
CIR
Shapers Level-1 SEs
SP 1 WFQ 1
CIR/EIR
SP 2 Shaper WFQ 2
CIR/EIR
SP 3 Shaper
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 383
WFQ 2
CIR
WFQ 4 WFQ 384
Shaper
CIR
Shapers
SP 1 WFQ 1
CIR/EIR WFQ 2
SP 2 Shaper CIR/EIR WFQ 63
SP 3 Shaper
WFQ 64
SP4
WFQ 1
WFQ 2
WFQ 3 WFQ 383
WFQ 384
WFQ 4
CIR
Shapers
SP 1
SP 2 CIR/EIR
Shaper
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
EVC Level Tunnel Level Port Level
Figure 11-46. Traffic Management Hierarchy and Dual Shaper Functionality

Queuing
Each flow is assigned to a queue block as its destination. Each queue block
includes scheduling queues in accordance with CoS delivery priorities. A flow
packet is mapped to a specific queue according to the packet’s CoS (set by CoS
mapping profile at the ingress), whereby CoS 7 is mapped to the lower priority
queue, and CoS 0 to the highest.
Level-0 SEs
CIR
Shapers Level-1 SEs
Packets mapped to queue SP 1 WFQ 1
according to their CoS
SP 2 CIR/EIR WFQ 2 CIR/EIR
Shapers Shapers
Flow mapped to SE (queue block) SP 3
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 383
WFQ 2
CIR
WFQ 4 WFQ 384
Shaper
CIR WFQ 1
Shapers
WFQ 2
SP 1 WFQ 63
WFQ 64
SP 2
SP 3
SP4
WFQ 1 WFQ 383
WFQ 2 WFQ 384
WFQ 3
WFQ 4
Figure 11-47. Packet Queuing
ETX-5 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 weight fair queuing
(WFQ):
• 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 will always be 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.
A queue block consists of several internal queues and each queue is defined by
its profile. The user defines an internal queue profile and then assigns it to a
queue block.
An internal queue profile has the following attributes:
• Queue type (strict or WFQ)

• Queue weight for WFQ

• Shaper profile (relevant for level-1 queue blocks of post-forwarding shaping
only). See Post-Forwarding Traffic Management Entities below.
• WRED profile (relevant for level-1 queue blocks of post-forwarding shaping
only). See Congestion Avoidance below.
ETX-5 provides three queue group types for post-forwarding traffic management
(TM) and one queue group type for pre-forwarding TM.
Congestion Avoidance
As the queues fill up, new packets face a growing risk of being discarded due to
lack of buffer space. The packets can be dropped as the queue becomes totally
full (tail-drop) or dropped selectively before all buffers are filled, using a
statistical probability. Selective dropping of packets when the queues are filling
up is referred to as congestion avoidance. Congestion avoidance mechanisms are
complementary to queuing algorithms; queuing algorithms manage the front of a
queue, congestion avoidance mechanisms manage the end of the queue.
The ETX-5 traffic management engine solves such issues by employing 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.
Near-empty queues accept all incoming packets, but as the queues begin to fill,
the drop probability for new packets increases. The different queues are
allocated different occupancy thresholds, above which incoming packets are
discarded at random at a growing rate as the queue fills, until the queue has
reached a maximum threshold and all incoming packets are dropped.
WRED Profile
A congestion control policy is defined by a WRED profile attached to an internal
queue (level-0 SE only). Each WRED profile includes two curves – one for green
and one for yellow packets. A packet is mapped into a curve according to its
color, with green packets having priority over the yellow ones. ETX-5 supports up
to eight WRED profiles.
Each WRED profile includes the following parameters:
• Minimum threshold: a percentage of maximum queue depth of 200 kBytes.
• Maximum threshold: a percentage of maximum queue depth of 200 kBytes
• Maximum drop probability: a drop probability of the maximum threshold
queue size, measured in percentages.
Enqueueing Process
When a packet is about to be enqueued, the queue status is checked and
enqueuing decision is taken according to the queue fill level:
• When the queue size is below the minimum threshold, the packet is admitted.
• When the queue size is in the range between minimum and maximum
threshold, the packet is dropped at the drop probability of the particular
queue size (per the WRED graph curve).

• When the queue size is at maximum threshold, the packet is dropped.
Drop
Probability
100%
Max Drop
Probability
75% 85% 100% Queue

Min Max Depth
Threshold Threshold
Figure 11-48. WRED Profile
Default WRED Profile

By default, ETX-5 has one WRED profile with the following settings:
• Green packets
 Minimum threshold – 100%
 Maximum threshold – 100%
 Maximum probability – 100%
• Yellow packets:
 Maximum probability – 100%.
Traffic Management Entities

ETX-5 supports several types of queue groups characterized by the following:
• Number of supported SE levels
• Scale (maximum number of SEs at each level)
• SE type (maximum number of queues and their scheduling scheme, strict or
WFQ)
• Shaping element type (single or dual rate).

When configuring and using queue groups, you may not exceed maximum allowed
number of its elements. For example, you can activate less than 384 level-0 SEs,
supported by 3-level queue groups (see Type 2 Queue Group).
To facilitate the configuration process, ETX-5 provides default queue groups for
every available type. These default entities can be used as a basis for creating
customized queue groups according to user requirements.
The post- and pre-forwarding traffic management entities are described below.
Post-Forwarding Traffic Management Entities

Post-forwarding (egress) traffic management is performed by the main card for
both directly- and indirectly-attached ports. Three queue group types handle
post-forwarding traffic.
Queue Group Resource Management

ETX-5 maintains a queue credit system for flexible management of scheduling
elements. Each main card is issued with 17408 queue credits. Each queue block
utilizes eight credits. When the queue budget is depleted, no additional queue
groups can be created or assigned.
The following rules apply to queue credit utilization:
• When a queue block is assigned to a main card port or intra-card LAG, credits
are collected from the main card to which the port or LAG belong.
• When a queue block is assigned to an inter-card LAG on main cards, credits
are collected from both main cards.
• When a queue block is assigned to an I/O card port or LAG, credits are
collected from both main cards.
Type 1 Queue Group

The type 1 queue group is a two-level TM entity with single and dual token
bucket shapers. ETX-5 supports up to 88 type-1 queue group instances per
device.

Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
WFQ 3
Up to 8 Up to 8
WFQ 4
CIR WFQ 5
Shapers
WFQ 6
SP 1
WFQ 7
SP 2
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
The type 1 queue group consists of:

• Up to eight level-0 scheduling elements (queue blocks) with four strict
priority queues and four weight fair queues in each block. Each queue in the
block can be configured to a different weight (1–63) with fixed queue depth
(200 kbytes).
• One level-1 scheduling element (SE) consisting of eight WFQs, one per each
level-1 queue block. Each queue in the block can be configured to a different
weight (1–63).
• Shaping elements:
 Single token bucket shaper per internal queue in level-0 SE
 Dual token bucket shaper per level-0 SE queue block
 Single token bucket shaper at level-1 SE egress.
Default Queue Group Profile

By default, ETX-5 provides a type-1 queue group profile with the following
attributes:
• Eight level-0 SEs connected to one level-1 SE
• Queue block profiles, as described below
• No shaper profiles.
The default queue group profile can be viewed and bound to a port as is, or used
as the basis for a new queue group (copy default queue group, rename and edit),
and then bound to a port.
When a queue group is bound to a port, the following configuration actions are
allowed:

• Replacing queue block profiles

• Replacing or deleting shaper profiles (a shaper profile cannot be edited while
it is in use in a queue group).
A queue group that is bound to a port cannot be replaced; you must verify that
no flows are attached to it, delete it, and then bind a new one.
Default Queue Block Profiles

By default, ETX-5 provides a level-0 queue block profile with the following
attributes:
• Four strict priority and four weight fair queues with default priority queue
profiles (see Default Queue Profiles below).
• No shaper profile.
The default queue block profile can be used as is, or as the basis for a new queue
block (copy, rename, edit), and bound to a queue group.
A queue block that is bound to a queue group cannot be edited (you can replace
it with a different queue block).
ETX-5 supports up to 128 different weight combinations for level-0 queue block.
The default level-1 queue block profile uses queues with the default WFQ queue
profile (weight fair queues, weight = 10, no shaper).
Type 2 Queue Group

The type 2 queue group is a three-level TM entity with single and dual token
bucket shapers. ETX-5 supports up to 88 type 2 queue group instances per
device.
Level-0 SEs
CIR
Shapers Level-1 SEs
SP 1 WFQ 1
CIR/EIR
SP 2 Shapers WFQ 2
CIR/EIR
SP 3
Shapers
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 383
WFQ 2
CIR
WFQ 4 WFQ 384
Shaper
CIR WFQ 1
Shapers
WFQ 2
SP 1 WFQ 63
WFQ 64
SP 2
SP 3
SP4
WFQ 1 WFQ 383
WFQ 2 WFQ 384
WFQ 3
WFQ 4


• Up to 384 level-0 scheduling elements (queue blocks) with four strict priority
queues and four weight fair queues in each block. Each queue in the block
can be configured to a different weight (1–63) with a fixed queue depth of
200 kBytes).
• Up to 64 level-1 scheduling elements (queue blocks) with 384 WFQs in each
block, one per each level-0 queue block. Each WFQ in the level-1 queue block
can be configured to a different weight (1–63).
• One level-2 scheduling element consisting of 64 WFQs with each queue user-
configurable to a different weight (1–4096).
Weight granularity: each of the 64 WFQs belonging to the level-2 SE (queue
block) can have one of 127 predetermined weights, according to the table
below. When a weight is selected in the range of two consecutive values, the
highest value is automatically selected. For example, if you set a WFQ weight
to 3000, which falls between the two allowed values of 2048 and 4096, ETX-
5 rounds it to 4096.

1 11 21 31 41 51 61 71 87 110 151 240 585
2 12 22 32 42 52 62 73 89 113 157 256 682
3 13 23 33 43 53 63 74 91 117 163 273 819
4 14 24 34 44 54 64 75 93 120 170 292 1024
5 15 25 35 45 55 65 77 95 124 178 315 1365
6 16 26 36 46 56 66 78 97 128 186 341 2048
7 17 27 37 47 57 67 80 99 132 195 372 4096
8 18 28 38 48 58 68 81 102 136 204 409
9 19 29 39 49 59 69 83 105 141 215 455
10 20 30 40 50 60 71 85 107 146 227 512
 Dual token bucket shaper per level-0 SE queue block (see Egress Shaping
below)
 Dual token bucket shaper per level-1 SE queue block(see Egress Shaping
below)

attributes:
• 384 level-0 SEs, 64 level-1 SEs and one levl-2 SE:
 Every six level-0 SEs are connected to one level-1 SE
 All level-1 SEs are connected to level-2 SE
• Queue block profiles, described below
allowed:
• Editing connections between level-0 and level-1 queue blocks. You can
connect up to 384 level-0 SE to a single level-1 SE.
A queue group that is bound to a port cannot be replaced, you must verify that


attributes:
The default queue block profile can be used as is, or as a basis for a new queue
Default level-1 and level-2 queue block profiles use queues with default WFQ
queue profile (weight fair queues, weight = 10, no shaper).
Type 3 Queue Group

The type 3 queue group is a three-level TM entity with single and dual token
bucket shapers. ETX-5 supports up to four type-3 queue group instances per
main card.
Level-1 SEs
WFQ 1
Level-0 SEs WFQ 2
CIR/EIR CIR/EIR
SP 1 Shapers Shapers
SP 2
Level-2 SE
SP 3
SP4 WFQ 1
WFQ 383 WFQ 2 CIR

Shaper
WFQ 384
WFQ 1
WFQ 2 WFQ 63
SP 1 WFQ 64
SP 2
SP 3
SP4
WFQ 383
WFQ 384
Type 3 queue group consists of:

queues in each block. Each queue has a fixed depth of 200 kBytes.
• Up to 64 level-1 scheduling elements (queue blocks) with 384 WFQs in each
block. Each WFQ in the level-1 queue block can be configured to a different
weight (1–63).
• One level-2 scheduling element is attached to a physical port. It consists of
64 WFQs with each queue user-configurable to a different weight (1–4096).

• Weight granularity: each of the 64 WFQs belonging to the level-2 SE (queue

block) can have one of 127 predetermined weights, according to the table
below. When a weight is selected in the range of two consecutive values, the
highest value is automatically selected. For example, if you set a WFQ weight
to 3000, which falls between the two allowed values of 2048 and 4096, ETX-
5 rounds it to 4096.
1 11 21 31 41 51 61 71 87 110 151 240 585
2 12 22 32 42 52 62 73 89 113 157 256 682
3 13 23 33 43 53 63 74 91 117 163 273 819
4 14 24 34 44 54 64 75 93 120 170 292 1024
5 15 25 35 45 55 65 77 95 124 178 315 1365
6 16 26 36 46 56 66 78 97 128 186 341 2048
7 17 27 37 47 57 67 80 99 132 195 372 4096
8 18 28 38 48 58 68 81 102 136 204 409
9 19 29 39 49 59 69 83 105 141 215 455
10 20 30 40 50 60 71 85 107 146 227 512
 Dual token bucket shaper per level-0 SE queue block (see Egress Shaping
below)
 Dual token bucket shaper per level-1 SE queue block(see Egress Shaping
below)

attributes:
• 768 level-0 SEs, 64 level-1 SEs and one levl-2 SE:
 Every 12 level-0 SEs are connected one level-1 SE
 All level-1 SEs are connected to level-2 SE
allowed:

• Editing connections between level-0 and level-2 queue blocks. You can
connect up to 384 level-0 SE to a single level-2 SE.

attributes:
• Four strict priority queues with default priority queue profiles (see Default
Queue Profiles below).
The default queue block profile can be used as is or used as the basis for a new
queue block (copy, rename, edit), and bound to a queue group
The default level-2 and level-3 queue block profiles use queues with default WFQ
queue profile (weight fair queues, weight = 10, no shaper).
Type 4 Queue Group

bucket shapers.
Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
Up to 40 Up to 40
CIR
Shapers
SP 1
SP 2
WFQ 40
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4


can be configured to a different weight (1–63) with fixed queue depth (200
kbytes).
• One level-1 scheduling element (SE) consisting of 40 WFQs, one per each
weight (1–63).

attributes:
• 40 level-0 SEs connected to one level-1 SE
allowed:

attributes:

Type 5 Queue Group

bucket shapers.
Level-0 SEs
CIR
Shapers
SP 1
SP 2 CIR/EIR
SP 3 Shapers
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2 CIR
WFQ 4
Shaper
WFQ 3
Up to 50 Up to 50
WFQ 4
CIR WFQ 5
Shapers
WFQ 6
SP 1
WFQ 7
SP 2
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4

can be configured to a different weight (1–63) with fixed queue depth
(200 kbytes).
• One level-1 scheduling element (SE) consisting of eight WFQs, one per each
weight (1–63).

attributes:
• 50 level-0 SEs connected to one level-1 SE

allowed:

attributes:
Egress Shaping
As described above, ETX-5 provides the following post-forwarding shaping
elements:
• Single token bucket shaper (CIR/CBS) per each level-0 SE queue
• Dual token bucket shaper per each level-0 SE queue block
• Dual token bucket shaper per each level-1 SE queue block
• Single token bucket shaper per level-2 SE queue block.
In total, ETX-5 supports up to 256 shaper profiles with the following
configuration ranges:
• CIR/EIR: 0, 256 kbps–10 Gbps (configured in kbps)
• CBS/EBS: 0, 10–512 kBytes (configured in bytes).
Note • EBS = 0 is valid only if EIR = 0.

• CBS = 0 is valid only if CIR = 0.

Pre-Forwarding Traffic Management Entities

Pre-forwarding (ingress) traffic management is performed by the Ethernet I/O
cards for indirectly-attached ports at the SAG level. One queue group type is
intended for pre-forwarding traffic.
Level-0 SEs
SP 1
SP 2
CIR
SP 3
Shapers
SP4
WFQ 1 Level-1 SE
WFQ 2
WFQ 1
WFQ 3 WFQ 2
WFQ 4
Up to 50 Up to 50
SP 1
SP 2 WFQ 49
SP 3 WFQ 50
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Figure 11-54. Pre-Forwarding Queue Group
The pre-forwarding queue group consists of:

queues and four weight fair queues in each block. Each of the WFQs queues
in the block can be configured to a different weight (3–110) with fixed queue
depth of 200 kBytes.
• One level-1 scheduling element (queue block) has 50 WFQs. Each WFQ in the
level-1 queue block has the same weight of 10.
• The pre-forwarding queue group includes one single token bucket shaper per
each level-0 queue block.
The ingress CIR/CBS shaper has the following configuration ranges:
• CIR: 0–1 Gbps (configured in kbps)
• CBS: 0–64 kBytes (configured in bytes)
• Compensation: 0–63 bytes.

By default, ETX-5 provides two-level queue group profile for pre-forwarding
scheduling with the following attributes:
• 50 level-0 SEs with all of them connected to one fixed and non-configurable
SE with the same weight.

allowed:
no flows are attached to it, delete it and bind a new one.

attributes:
block (copy, rename, edit), and bind to a queue group.
The default level-1 queue block profile uses queues with default WFQ queue
Default Queue Profiles

By default, ETX-5 provides two queue profiles – one for strict, and one for weight
fair queue:
• Strict priority profile without shaper profile and with WRED profile
• WFQ profile with weight set at 10, without shaper profile and with default
WRED profile.
Shaper
Traffic coming from level-0 internal queues and from level-0, -1 and -2 queue
blocks, is shaped to smooth out bursts and avoid buffer overruns in subsequent
network elements. At this stage, output packets from each buffer block undergo
a shaping function so that the overall traffic volume from each block does not
exceed a preset bandwidth value. Shaping is performed according to a single or
dual token bucket algorithm.
Traffic shaping is performed by creating shaper profiles with the following
bandwidth parameters:
• Committed Information Rate (CIR): The bandwidth that the service provider
guarantees the enterprise, regardless of network conditions.

• Excess Information Rate (EIR): The bandwidth allowance for “best effort”
delivery, for which service performance is not guaranteed and traffic may be
dropped if the network is congested.
• Committed Burst Size (CBS): The maximum size, expressed in bytes, of a burst
of back-to-back Ethernet frames for guaranteed delivery.
• Excess Burst Size (EBS): The maximum size of a burst of back-to-back
Ethernet frames permitted into the network without performance
guarantees. EBS frames may be queued or discarded if bandwidth is not
available.
Defined shaper profiles (up to 256 per chassis) are assigned to relevant
scheduling elements (SE). Functional Description above details the ETX-5 SEs and
shapers supported by them. Single-rate shapers are defined with CIR/CBS values
only; dual-rate shapers have both CIR/CBS and EIR/EBS values.
Shaper bandwidth values are different for pre-forwarding (ingress) and post-
forwarding (egress) traffic management.
Pre-Forwarding (Ingress) TM Post-Forwarding (Egress) TM
CIR CBS CIR/EIR CBS/EBS
0–1 Gbps 0–64 kbyte 0.256 kbps – 10 Gbps 0, 10–512 kbyte
Factory Defaults
By default, there are no shaper profiles in the system.
Configuring Shaper
 To define a shaper profile:

3. At the configure>qos# prompt, enter shaper-profile followed by profile name.
The config>qos>shaper-profile(profile_name)$ prompt is displayed.
4. Configure the shaper profile as illustrated and explained below.
5. Assign the shaper profile to a relevant scheduling element (internal queue or
queue block within queue group).
Note Using no before shaper-profile (profile _name) deletes the shaper profile.
Defining CIR, EIR data rate and bandwidth [cir <cir-kbit-sec>] [cbs For single-rate shapers, use
CBS, EBS burst rate <cbs-bytes>] [eir <eir-kbit-sec>] [ebs only CIR/CBS values.
<ebs-bytes>] EBS = 0 is valid when EIR = 0.
CBS=0 is valid when CIR= 0.

Compensating for Layer-1 compensation <0–63> For pre-forwarding (ingress)

overhead and additional VLAN compensation <0, 20> traffic management the
tag (in bytes) compensation is configurable in
the 0–63 range.
For post-forwarding (egress)
traffic management the
compensation is applied to
level-0 shapers only. It can be
set to 0 (data rate) or 20 (line
rate).
Example
See the Example at the end of the QoS section.
error is detected.
Message Description
Illegal value The value entered for the parameter is not valid
Shaper/policer profile is in use and The shaper profile is being used by a queue or queue block; or
cannot be changed/deleted policer profile is being used by a flow. Remove the association
to delete or modify a shaper/policer profile.
Shaper/policer profile cannot be added, The maximum number of profiles (128) has been reached and
max number of profiles has been no additional shaper/policer profiles can be added
reached
Profile name must be unique The shaper/policer mapping profile name is not unique
use
Illegal indices for bandwidth profile The values entered for the bandwidth profile are not valid
Congestion Avoidance (WRED)

The ETX-5 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.
A congestion control policy is defined by a WRED profile attached to an internal
queue (level-0 SE only). A WRED profile includes two curves, one for green and
one for yellow packets. You can configure up to eight WRED profiles per chassis.
A profile includes the following parameters:

• Minimum threshold: a percentage of the maximum queue depth (200 kBytes).

• Maximum threshold: a percentage of the maximum queue depth
(200 kBytes).
• Maximum drop probability: a percentage of the maximum threshold queue
size that defines the drop probability.
Factory Defaults
By default, ETX-5 provides one WRED profile (DefaultWREDProfile) with the
following settings:
• Green packets
 Maximum probability – 100%
• Yellow packets:
 Maximum probability – 100%.
Note The name of the default WRED profile (DefaultWREDProfile) is case-sensitive.
Configuring WRED
 To define a WRED profile:

6. At the configure>qos# prompt, enter wred-profile followed by profile name.
The config>qos>wred-profile(profile_name)$ prompt is displayed.
7. Configure the WRED profile as illustrated and explained below.
8. Assign WRED profile to an internal scheduling queue (see Internal Queue
below).
Note Using no before wred-profile (profile _name) deletes the WRED profile.
Defining minimum and maximum color green [min <0–100> max <0– A WRED profile must include
thresholds and maximum 100> [probability <0–100>] both green and yellow packet
probability color yellow [min <0–100> max <0– types
100> [probability <0–100>]
Example
See Example at the end of the QoS section.

error is detected.
Message Description
WRED profile is in use and cannot be The WRED profile is being used by an internal queue. Remove
changed/deleted the queue association to delete or modify WRED profile.
WRED profile cannot be added, max The maximum number of profiles (8) has been reached and no
number of profiles has been reached additional WRED profiles can be added
Profile name must be unique The WRED profile name is already in use
use
Default WRED profile cannot be It is not possible to modify or delete a default WRED profile
changed/deleted
Internal Queue
Internal queues are tier-1 scheduling elements of ETX-5, that use strict or WFQ
scheduling techniques. They have shaper and WRED profiles assigned to them,
and, at a later stage, they are combined into queue blocks. ETX-5 supports up to
16K of internal queue profiles per chassis.
Factory Defaults
By default, ETX-5 provides the following internal queue profiles:
• DefaultStrictInternalQ
 Strict scheduling
 WRED profile –DefaultWREDProfile
• DefaultWfqInternalQWithWred
 WFQ scheduling, weight 10
 WRED profile –DefaultWREDProfile
• DefaultWfqInternalQWithoutWred
 WFQ scheduling, weight 10
 No WRED profile

Configuring Internal Queues
 To define an internal queue:

1. At the configure>qos# prompt, enter queue-internal-profile followed by
profile name.
The config>qos>queue-internal-profile(profile_name)$ prompt is
displayed.
2. Configure the internal queue profile as illustrated and explained below.
3. Assign an internal queue profile to a queue block (see Queue Block below).
Note Using no before queue-internal-profile (profile _name) deletes the internal queue
profile.
Assigning a WRED profile to the congestion-avoidance wred profile You can assign a user-defined
internal queue <wred-profile-name> or default (DefaultWREDProfile)
no congestion-avoidance wred to the internal queue.
no congestion-avoidance wred
removes a WRED profile
association.
Setting scheduling method scheduling { strict | wfq <weight>} The weight range is 0–4095
Assigning a shaper profile to the shaper profile <shaper-profile-name> no shaper-profile removes a

internal queue no shaper profile shaper profile association
Example
Queue Block
The queue block is a tier-2 scheduling element in the ETX-5 traffic management
system. It consists of internal queues, and, in turn, serves as part of a tier-3
element – a queue group.
Factory Defaults
ETX-5 provides several queue block profiles, depending on the queue group types
that use them. The default queue block profiles are as follows:
• q_block_4_WFQ_4_SP_default
• q_block_8_queue_WFQ_default
• q block 40 queue WFQ default
• q_block_4_SP_default.

Configuring Queue Block
 To define a queue block:

1. Verify that you have configured all necessary internal queue profiles.
At the configure>qos# prompt, enter queue-block-profile followed by profile
name.
The config>qos>queue-block-profile(profile_name)$ prompt is displayed.
2. At the config>qos>queue-block-profile(profile_name)$ prompt, enter queue,
followed by internal queue number.
Note The number of internal queues per queue block is different for different types of
queue block.
The config>qos>queue-block-profile(profile_name)>queue(queue_number)$
3. Assign an internal queue profile to each internal queue within the queue
block (see internal-profile in table below).
4. Assign the queue block to a queue group and bind it to a queue within a
higher queue block (see Queue Group below).
Note • Using no before queue-block-profile (profile _name) deletes the queue block
profile.
• Using no before queue (queue_number) deletes the queue from the queue
block.
Assigning an internal queue internal-profile profile no internal-profile removes an

profile to the queue within the <internal_profile_name> internal queue profile
queue block no internal-profile association from the queue
within the queue block
Example
Queue Group
Queue group is a tier-3 scheduling element in the ETX-5 traffic management
system. Queue groups perform pre- and post-forwarding (ingress and egress)
traffic management and are subdivided into the different types.
Factory Defaults
ETX-5 provides several queue group profiles, depending group type. The default
queue group profiles are as follows:
• q_group_2_level_default
• q_group_3_level_default

• q_group_3_level_768_default
• q_group_SAG_2_level_default.
Configuring Queue Group
 To configure a queue group:

1. Verify that you have configured all necessary queue block and shaper profiles.
2. At the configure>qos# prompt, enter queue-group-profile followed by profile
name.
The config>qos>queue-group-profile(profile_name)$ prompt is displayed.
3. At the configure>qos# prompt, select a queue block in level 0, 1 or 2 to
configure:
 queue-block 0/<1–N>
Note • The queue block number depends on the queue group type that the queue
block belongs to. Functional Description above details the exact numbers of
queue blocks supported by different queue group types.
• The queue blocks must be added sequentially (queue-block 0/1, queue-block
0/2 etc).
The config>qos>queue-group-profile(profile_name)>queue-block(level/ID)#
5. If you wish to configure another queue block, type exit to return to the queue
group profile context, and start again.
Note Using no before queue-block (queue_block_name) deletes the queue block from
the queue group.
6. Alternatively, you can create a new queue group by copying parameters from
an existing one. Use the inherited-from command in the
queue-group-profile(profile_name) prompt, followed the name of the queue
group from which you want to copy parameters.
Assigning a name to the queue name <block_name>

block
Assigning a queue block profile profile <queue_block_profile>

Binding a queue block to a queue in bind queue <queue_number> block Level-2 (highest)
the next-level queue block <level/number> queue block cannot
be bound to anything
Assigning a shaper profile shaper profile <shaper_profile>
Example
error is detected.
Table 11-14. Queue Configuration Error Messages
Message Description
Internal queue profile is in use and The internal queue profile is being used by a queue block.
cannot be changed/deleted Remove the queue block association to delete or modify an
internal queue profile.
Queue block profile is in use and cannot The queue block profile is being used by a queue group. Remove
be changed/deleted the queue group association to delete or modify a queue block
profile.
Only first 4 internal queues in the queue The first four internal queues in a queue block must use a strict
block can be strict priority mechanism
Dual shaper cannot be bound Use single-rate shaper
Profile does not exist The selected profile does not exist
Profile cannot be added, max number of The maximum number of internal queue profiles has been
profiles has been reached reached and no additional profiles can be added
Profile name must be unique The queue profile name is not unique
use
Default profile cannot be It is not possible to modify or delete a default queue profile
changed/deleted
Illegal indices for profile The values entered for a profile are not valid
Illegal CIR value in shaper The CIR value entered is not valid for a shaper assigned to a
specific scheduling element
Illegal CBS value in shaper The CBS value entered is not valid for a shaper assigned to a
Illegal EIR value in shaper The EIR value entered is not valid for a shaper assigned to a

Message Description
Illegal EBS value in shaper The EBS value entered is not valid for a shaper assigned to a
Illegal shaper compensation value The compensation value entered is not valid for a shaper
assigned to a specific scheduling element
Queue block name is already in use at A queue block with the same name already exist in the same
the same level level
Source group queue group profile for Indicates an attempt to use a non-existing queue group profile
inherit action does not exist as a source for a new queue group profile
Specified queue group profile does not Indicates an attempt to use a non-existing queue group profile
exist
Next level queue block does not exist Indicates an attempt to bind a queue block profile to a queue in
a next-level queue block that does not exist
Assigned internal queue does not exist Indicates an attempt to bind a non-existing internal queue a
queue block
Internal queue is already in use by Indicates an attempt to bind an internal queue already in use to
another queue bock a queue block
Assigned queue block cannot be deleted A queue block cannot be deleted while it is assigned to a queue
group.
Queue group profile cannot be added, The maximum number of queue group profiles has been reached
max number of profiles has been and no additional profiles can be added
reached
Internal queue mismatch in level-0 queue Invalid queue combination in a level-0 queue block
block
Strict internal queues cannot be Level-1 and level-2 queue blocks can have only WFQ queues
assigned to level-1 and level-2 queue
blocks
WRED profiles cannot be assigned to Internal queues in level-1 and level-2 queue blocks cannot have
internal queues in level-1 and level-2 WRED profiles assigned to them
queue blocks
Green or yellow color settings are No color values are defined in a WRED profile assigned to an
missing from WRED profile internal queue
Strict internal queues are missing from Mandatory internal queues with strict priority have not been
level 0 queue block assigned to a level-0 queue block.
WFQs are missing from level 0 queue Mandatory internal queues with WFQ priority have not been
block assigned to a level-0 queue block
Illegal weight value for internal queues in The weight values entered are not valid for internal queues with
level 0 queue block WFQ priority in a level-0 queue block
Illegal weight value for internal queues in The weight values entered are not valid for internal queues with
level 1 queue block WFQ priority in a level-1 queue block
Illegal number of internal queues The number of internal queues defined in a queue block is not
valid

Message Description
Dual shaper cannot be bound to level 0 Dual shaper profiles cannot be assigned to a level 0 queue block
queue block in an ingress (pre-forwarding) queue group
Dual shaper cannot be bound to level 1 Dual shaper profiles cannot be assigned to a level 1 queue block
queue block in an ingress (pre-forwarding) queue group
Cannot be bound to internal queues in Shaper profiles cannot be assigned to internal queues in level-1
level-1 and level-2 queue blocks and level-2 queue blocks
CoS Mapping
User priorities must be mapped to internal Class of Service (CoS) values, as
detailed below.
User priorities are mapped to internal Class of Service (CoS) values, according to
P-bit, DSCP, IP Precedence or per-flow criteria. The newly defined CoS can then
be used for:
• P-bit handling during VLAN editing process
• Queue mapping.
In other words, each packet is first “normalized” to a CoS value (0–7), then this
CoS is used for VLAN editing (P-bit) or priority queue mapping.
CoS Mapping CoS to P-bit (VLAN Editing)
Profiles to map packet to CoS: Profiles to map:

• P-bit to CoS (0–7) • CoS to P-bit
→
Ingress Traffic → • DSCP to CoS (0–7) Queue Mapping
• IP Precedence to CoS (0–7)
Profiles to map:
• Flow to CoS
• CoS to priority queue (0–7)
The tables below provide detailed descriptions of CoS mapping methods

supported by directly- and indirectly-connected ports, depending on a
classification key used for traffic classification.
Note Unmapped traffic is assigned to the default (lowest, 7) CoS.
Capacity
ETX-5 supports up to 36 user-defined CoS mapping profiles per I/O card. There
are three default profiles for P-bit to CoS, IP Precedence to CoS, DSCP to CoS
mapping. These profiles are considered part of the 36 CoS mapping profiles
supported per system.
Table 11-15. P-bit to CoS Default Mapping Profile
P-bit CoS
0 7

P-bit CoS
1 6
2 5
3 4
4 3
5 2
6 1
7 0
Table 11-16. IP Precedence to CoS Default Mapping Profile
IP-P CoS
0 7
1 6
2 5
3 4
4 3
5 2
6 1
7 0
Table 11-17. DSCP to CoS Default Mapping Profile
DSCP CoS
0 7
1 6
2 5
3 4
4 3
5 2
6 1
7–63 0
Indirectly-attached ports support up to 12 profiles. The CoS mapping method for

indirectly-attached ports depends on the selected classification key
(seeTable 11-15). The number of CoS mapping profiles supported by directly-
attached ports depends on the selected ingress color mapping. For any flow, the
methods used for CoS and ingress color mapping are related in the following way:
• The flow to CoS mapping method is supported only with flow to ingress color
mapping

• The P-bit to CoS mapping method is supported only with either DEI or P-bit to
ingress color mapping methods
• The DSCP to CoS mapping method is supported only with DSCP to ingress
color mapping method.
Up to 15 different combinations of X to CoS + X to color are supported for
directly-attached ports.
CoS mapping method for directly-attached ports depends on the selected
classification key (see Table 11-16).
Table 11-18. Possible Combinations of CoS and Ingress Color Mapping Methods
for Directly-Attached Ports
CoS Mapping Method Ingress Color Mapping Method
Per flow (flow to CoS) Per flow (flow to color)
Per P-bit (P-bit to CoS) Per P-bit (P-bit to color)
Per P-bit (P-bit to CoS) Per DEI (DEI to color)
Per DSCP (DSCP to CoS) Per DSCP (DSCP to color)
Note
See Color Mapping for details on the color mapping methods.
Priority Queue Mapping

When an Ethernet flow is connected to a level-0 scheduling element (SE), CoS
values are mapped into SE queues according to the default queue mapping profile
(QueueMapDefaultProfile). This profile is fixed and cannot be changed. This
profile is the only queue mapping profile that can be attached to a flow.
Note The name of the default queue mapping profile (QueueMapDefaultProfile) is

case-sensitive.
Table 11-19. CoS to Priority Queue Mapping
CoS Queue
0 1
1 2
2 3
3 4
4 5
5 6
6 7
7 8

Factory Defaults
ETX-5 has three default profiles for P-bit to CoS, IP Precedence to CoS, and DSCP
to CoS mapping. These profiles are part of 36 CoS mapping profiles supported per
system.
Configuring CoS Mapping
 To define a CoS mapping profile:

7. At the configure>qos# prompt, enter cos-map-profile followed by profile
name and classification method: classification {p-bit | ip-precedence |
ip-dscp}
Note Using no before cos-map-profile (profile_name) deletes the CoS mapping profile.
8. Map the user priority to a CoS value (user priority values 0–7 for P-bit and IP
Precedence, 0–63 for DSCP; CoS values 0–7):
 map <0–7> to-cos <0–7>
 map <0–63> to-cos <0–7>.
Example
See Example at the end of the Traffic Management section.
error is detected.
Message Description
CoS mapping profile is in use and cannot The CoS mapping profile is being used by a flow. Remove the
be changed/deleted flow association to delete or modify the CoS mapping profile.
Default CoS mapping profile cannot be It is not possible to modify or delete a default CoS profile
changed/deleted
Profile name must be unique The CoS mapping profile name is not unique
use
Max number of profiles using one CoS The maximum number of profiles (12 or 16) using the same CoS
mapping method has been reached mapping method (P-bit to CoS, DSCP to CoS, etc.) has been
reached
Color Mapping
ETX-5 supports an ingress color mapping mechanism as a part of its traffic
policing features.

The mechanism inspects incoming packets and assigns a color (green or yellow)
value according to configured color mapping profiles. The following mapping
profiles are supported:
• P-bit to color
• DSCP to color
• IP Precedence to color
• DEI to color (fixed mapping, 0 to green and 1 to yellow)
• Flow to color
• Mark all green (default).
In total, ETX-5 supports up to 36 ingress color mapping profiles (12 of each
type).
Packet color is used afterwards by WRED mechanism for congestion prevention
and during VLAN editing process (setting DEI value).
Note Ingress color mapping method for both directly- and indirectly-attached ports
depends on a classification key used for the port. See Table 11-15 and
Table 11-16 for details.
Color Mapping for Indirectly-Attached Ports

In addition to color mapping, indirectly-attached port flows have policers applied
to them. Thus, the final color of the packet also depends on the policing result.
Two policer modes relate to ingress color mapping:
• Color-blind policer that configures packet color without taking into account
any preexisting markings that may be set for a packet by another traffic
policer at a previous network node
• Color-aware policer that adds color information packet color taking into
account previously configured packet color
Color Mapping for Directly-Attached Ports

Directly-attached ports do not support the policing mechanism, and map
previously configured packet color to the same egress color directly.
Note The ingress color mapping method for directly-attached ports depends on
selected CoS mapping for a flow. See Table 11-18 for possible combinations of
CoS mapping and color mapping profiles.
Factory Defaults
By default, ETX-5 marks all incoming packets as green.

Configuring Color Mapping
 To define a color mapping profile:

9. At the configure>qos# prompt, enter color-map-profile followed by profile
name and classification method: classification {p-bit | ip-precedence | ip-dscp
| dei}.
Note Using no before color-map-profile (profile_name) deletes the color mapping

profile.
10. Map the user priority to a color value (user priority values 0–7 for P-bit and IP
Precedence, 0–63 for DSCP, or DEI 0–1; color values: green and yellow):
 map <0–7> to green or yellow
 map <0–63> to green or yellow
Note DEI to color mapping is fixed: 0 to green and 1 to yellow.
Example
See Example at the end of the Traffic Management section.
error is detected.
Message Description
Color mapping profile is in use and The color mapping profile is being used by a flow. Remove the
cannot be changed/deleted flow association to delete or modify the color mapping profile.
Color mapping profile cannot be added, The maximum number of profiles (36) has been reached and no
max number of profiles has been additional color mapping profiles can be added
reached
Profile name must be unique The color mapping profile name is not unique
use
Max number of profiles using one color The maximum number of profiles (12) using the same color
mapping method has been reached mapping method (P-bit to color, DSCP to color, etc.) has been
reached
Policing
When the flows are established, a metering and policing function can be applied
for each ingress flow on directly – and indirectly-attached ports to regulate traffic
according to the contracted CIR, EIR, CBS and EBS bandwidth profiles. In addition,
policing can be applied to Ethernet ports on the main and I/O cards, and LAG.

Rate limitation is performed according to the Dual Token Bucket mechanism (two
rates, three colors) in color-aware or color-blind modes.
The final color of a packet is determined by a policer (color-aware or color-blind).
If a policer is not applied on a specific flow, the ingress color mapping determines
packet color.
Policer Bandwidth Profiles

Policing is implemented by defining policer bandwidth profiles and assigning them
to one or more (up to 16) flows (aggregate policer profile) or Ethernet ports.
ETX-5 supports up to:
• 128 regular policer bandwidth profiles per chassis
• 4k aggregate policer profiles per chassis (relevant for Ethernet I/O cards only)
• 4k regular policer instances per each Ethernet main card.
• 2k policer instances per Ethernet I/O card (includes aggregate policer
instances).
Actual values are:
 2021 in 10G IO card
 1994 in 1G IO card
Policer Parameters
Policer uses the following for bandwidth control:
• Committed Information Rate (CIR) for the current profile. The CIR specifies a
bandwidth with committed service guarantee (“green bucket” rate).
• Committed Burst Size (CBS) for the current profile. The CBS specifies the
maximum guaranteed burst size (“green bucket” size).
• Excess Information Rate (EIR). The EIR specifies an extra bandwidth with no
service guarantee (“yellow bucket” rate).
• Excess Burst Size (EBS). The EBS specifies the extra burst with no service
guarantee (“yellow bucket” size).
• Coupling Flag. This parameter is relevant for color-aware mode only. See
Color-Aware Policer section below.
Overhead Compensation
For ingress flows on indirectly attached ports, you can also specify the amount of
bytes that the shaper or policer can use to compensate for the overhead of
Layer-1 (preamble and IFG) and the overhead for the added VLAN header in case
of stacking.
Color-Aware Policer
When determining whether or not a packet conforms to a bandwidth profile, the
color-aware policer takes into account any preexisting color markings that may
have been set for a packet by another traffic policer.
The packet ingress color is resolved by a color mapping profile.

The color-aware policing mechanism conforms to MEF 10.1 requirements and is

illustrated below:
Arriving packet is Yes

green and CIR bucket Packet is green
is not exceeded
No Packets are admitted

to network
EIR bucket is not Yes

exceeded Packet is yellow
(see Note below)
No
Packet is red and it is

dropped
Figure 11-55. Color-Aware Policing
Note When the Coupling Flag is enabled, a sum of CIR and EIR volumes is taken into
account. Coupling flags are described below.
The coupling flag allows a choice between two modes of operations for the rate
enforcement algorithm. The chosen value for CF has the effect of controlling the
volume of the yellow packets.
• When CF is disabled, the long term average bit rate of yellow packets is set
by EIR.
• When CF is enabled, the long term average bit rate of yellow packets is set by
CIR + EIR, depending on volume of the green packets.
In both cases the burst size of the yellow packets is limited by EBS.
In other words, when the CF is enabled, a yellow packet arrives with an empty EIR
bucket, and the policer forwards the packet, using tokens from the CIR bucket.
This allows the EIR to be extended to the value of “configured CIR” + “extended
EIR”.
Color-Blind Policer
In the color-blind mode, the policer ignores the packet color (if any) when
determining whether or not a packet conforms to a bandwidth profile.
Broadcast Storm Control

A port-level policing can be applied to admitted packets to limit Broadcasts,
Multicasts and Unknown Unicasts. The following traffic types are supported:
• Broadcast: Limits the total port broadcast rate to CIR/CBS
• Multicast: Limits the total port multicast rate to CIR/CBS
• Broadcast and Multicast (policer profiles on indirectly-attached ports only):

 Limits the total port broadcast rate to CIR/CBS

 Limits the total port multicast rate to CIR/CBS
Note This type of policer profile is not an aggregate rate police for broadcast +
multicast packets.
• Unknown unicast (policer profiles on directly-attached ports only): Limits the

total port unknown unicast rate to CIR/CBS.
• All (default): Storm control is disabled. This is relevant for policers profiles
bound to flows.
Note Flows from different I/O port groups (1–10, 11–20) of the E5-GBE-20 card and
flows from different ports of the E5-10GBE-2 card cannot share the same
aggregate policer.
Factory Defaults
By default, ETX-5 does not have policer profiles.
Configuring Policer Profile
 To define a policer profile:

1. At the configure>qos# prompt, enter policer-profile followed by profile name.
The config>qos>policer-profile(profile_name)$ prompt is displayed.
Defining bandwidth profile, using bandwidth [cir <cir-kbit-sec>] [cbs <cbs- For flows with ingress port
CIR/CBS and EIR/EBS rates bytes>] [eir <eir-kbit-sec>] [ebs <ebs- located on E5-MC-4 or E5-
bytes>] MC-SFP-P-4 cards, the
minimum EIR and CIR values
are 64 kbps.
The minimum CIR/CBS rate
for policers to be assigned to
E5-MC-4/ E5-MC-SFP-P-4
ports is 38.4 Mbps.
Configurable CIR/CBS rate for
the policers has granularity
n
of 38.4 Mbps × 2 , where n
is 0–8.
Configuring color awareness of the color-aware no color-aware enables the

policer no color-aware color blind mode of the
policer
Compensating for Layer-1 overhead compensation <0–63> Compensation is not

and additional VLAN tag (in bytes) supported for flows with an
ingress port residing on a
main card port

Defining traffic type traffic-type { all | broadcast | multicast | broadcast – port or LAG
unknown-unicast | broadcast-and- multicast – port or LAG
multicast }
broadcast-and-multicast –
I/O card port or LAG
unknown-unicast – main card
ports or LAG consisting of
main card ports
all – flow
Enabling coupling flag to control coupling-flag no coupling-flag disables

the volume of yellow packets no coupling-flag coupling flag usage
Configuring Policer Aggregate Profile

If you want to set bandwidth limits that are divided among two or more flows,
you can create policer aggregate profiles. Policer aggregate profiles can be
applied only to the flows with an ingress port residing on an I/O card port.
 To define a policer aggregate profile:

1. Verify that you have configured a regular policer profile, whose settings will
be used by the aggregate policer profile.
2. At the configure>qos# prompt, enter policer-aggregate-profile followed by
profile name.
The config>qos>policer-aggregate-profile(profile_name)$ prompt is
displayed.
Assigning policer profile policer profile <policer_profile_name>
Displaying the associated show flows

flows
Example
See the Multiple CoS Point-to-Point Service example in the section Flows above.
This example shows how to create four policer profiles to allocate bandwidth to
four flows (11–14).
Table 11-22 lists the messages generated by ETX-5 when a policer configuration
error is detected. Table 11-23 lists the messages generated by ETX-5 when a
policer aggregate configuration error is detected.

Table 11-22. Policer Configuration Error Messages
Message Description
Shaper/policer profile is in use and The shaper profile is being used by a queue or queue block; or
cannot be changed/deleted the policer profile is being used by a port/flow. Remove the
association to delete or modify a shaper/policer profile.
Shaper/policer profile cannot be added, The maximum number of profiles (128) has been reached and
max number of profiles has been no additional shaper/policer profiles can be added
reached
Profile name must be unique The shaper/policer mapping profile name is not unique
use
Illegal indices for bandwidth profile The values entered for the bandwidth profile are not valid
Table 11-23. Policer Aggregate Configuration Error Messages
Message Description
Policer aggregate profile is in use and The policer aggregate profile is being used by a flow. Remove
cannot be changed/deleted the association to delete or modify a policer aggregate profile.
Policer aggregate profile cannot be The maximum number of profiles (128) has been reached and
added, max number of profiles has been no additional policer aggregate profiles can be added
reached
Profile name must be unique The policer aggregate mapping profile name is not unique
use
Policer profile does not exist A policer profile, whose setting are to be used for the policer
aggregate profile, has not been defined
Marking
Marking profiles map CoS and packet color values into egress priority tags. The
marking is done per color (green and/or yellow) to support color re-marking, and
optionally the Drop Eligible Indicator (DEI) bit is specified in the frame header.
ETX-5 supports up to 16 color-aware and color-blind marking profiles.
• A color-aware profile translates CoS (0–7) and packet color (all, green,
yellow) into P-bit (0–7) and DEI (yellow, green) values
• A color-blind profile translates CoS (0–7) into P-bit (0–7) and DEI (yellow,
green) values.
Note If DEI value is omitted during configuration, it is automatically set to 0.
Marking profiles are used during VLAN editing procedures applied to flows.

Factory Defaults
By default, ETX-5 does not have any marking profiles.
Configuring Color-Blind Marking Profile

When a color-blind marking profile is used, ETX-5 converts user CoS (set via CoS
mapping profile) into P-bit priority and sets the egress DEI to green or yellow,
ignoring the packet color (set via color mapping profile).
 To configure a color-blind marking profile:

1. At the configure>qos# prompt, enter marking-profile followed by profile
name and fixed classification method (classification cos), disabled color
awareness mode (color-aware none) and dei mapping or always-green at the
end.
The configure>qos>marking-profile(profile_name)# prompt is displayed.
2. Map the CoS value to P-bit value and define DEI color as follows: mark <0–7>
to <0–7> dei <green | yellow>.
Configuring Color-Aware Marking Profile

When a color-aware marking profile is used, ETX-5 converts user CoS (set via CoS
mapping profile) and the packet color (set via color mapping profile or policer)
into P-bit priority and converts the packet color (set via color mapping profile)
into egress DEI value (green or yellow).
 To configure a color-aware marking profile:

1. At the configure>qos# prompt, enter marking-profile followed by profile
name and fixed classification method (classification cos), enabled color
awareness mode (color-aware green-yellow) and dei mapping or always-
green at the end.
The configure>qos>marking-profile(profile_name)# prompt is displayed.
2. Map the CoS value to P-bit value and define DEI color as follows: mark <0–7>
<green | yellow> to <0–7> dei <green | yellow>.
Example
See Multiple CoS Point-to-Point Service example in the Flows section above. This
example shows how to create color-aware marking profile.
error is detected.
Message Description
Color mapping profile is in use and The color mapping profile is being used by a flow. Remove the
cannot be changed/deleted flow association to delete or modify color mapping profile.

Message Description
Marking profile cannot be added, max The maximum number of profiles (16) has been reached and no
number of profiles has been reached additional marking profiles can be added
Profile name must be unique The marking profile name is not unique
use
Illegal marking profile method The selected marking method is not supported
Mark value in marking profile is out of The selected mark valuemust be within the range 0–7
range
Priority Queue Mapping

When an Ethernet flow is connected to a level-0 scheduling element (SE), CoS
values are mapped into SE queues according to the default queue mapping profile
(QueueMapDefaultProfile). This profile is fixed and cannot be changed. This
profile is the only queue mapping profile that can be attached to a flow.
Table 11-25. CoS to Priority Queue Mapping
CoS Queue
0 1
1 2
2 3
3 4
4 5
5 6
6 7
7 8
Example
This example shows how to create multiple CoS point-to-point service with traffic
management. Traffic management is performed using a 3-level queue group,
illustrated in the figure below.
 To configure multiple CoS point-to-point service:

1. Configure single- and dual rate shaper profiles.
2. Configure WRED profiles with a small queue depth for delay-sensitive high-
priority queues. This WRED profile defines a queue with a depth at 30% of
the nominal (100%) value. This is done by setting maximum threshold to
30%. Keep in mind that the ETX-5 queue length is fixed at 200 kBytes.

Note Congestion control (WRED profiles) is not applicable to queues in level-1 and
level-2 SEs.
1. Define internal queue profiles, specifying their scheduling types, shaping and
WRED profiles (where applicable).
2. Configure level-0, level-1 and level -2 queue block profiles with queues, using
internal queue profiles.
3. Define the queue group profile, adding queue blocks to the group, binding
the queue blocks to the next level queues and assigning the relevant shaper
profiles. Queue blocks are added to queue groups in the reverse order:
level-2 > level-1 > level 0.
4. Assign the queue group to the main card ports.
7. Configure 12 VLAN-type classifier profiles.
values.
9. Configure the color mapping profile to map user color to internal color values.
10. Configure 12 flows from port 1 to port 2 on the main card and direct them to
the relevant level-0 queue blocks.

Level-0 SEs
q_block_4_WFQ_4_SP_10_40
CIR 0/1
Shapers
Flow 1
WR.1 SP 1 Sh. 7
Flow 2
CIR/EIR
WR.1 SP 2 Sh. 7
Flow 3 Shapers
WR.1 SP 3 Sh. 7
Flow 4
WR.1 SP4 Sh. 7
Flow 5
Def. WR. WFQ 10 Sh. 7
Flow 6 Sh. 1
Def. WR. WFQ 20
Flow 7
Def. WR. WFQ 30
Def. WR. WFQ 40
Level-1 SEs
CIR 0/2
Shapers q_block_11_queue_WFQ_10_20_30
WR.1 SP 1 Sh. 7 CIR/EIR 1/1
WR.1 Shapers CIR/EIR

SP 2 Sh. 7
WFQ 10 Shapers
Flow 10 WR.1 SP 3 Sh. 7 WFQ 20
WR.1 SP4 Sh. 7 WFQ 30
Def. WR. WFQ 10 Sh. 7 Sh. 2
Sh. 4
Def. WR. WFQ 20
Def. WR. WFQ 30
Def. WR. WFQ 40
CIR 0/3
Shapers
WR.1 SP 1 Sh. 7
WR.1 SP 2 Sh. 7
CIR/EIR Level-2 SE
WR.1 SP 3 Sh. 7 Shapers q_block_21_queue_WFQ_10_20
CIR
Flow 20 WR.1 SP4 Sh. 7 2/1 Shaper
Def. WR. WFQ 40 WFQ 10
Def. WR. WFQ 30 WFQ 20

Sh. 3
Def. WR. WFQ 20
Sh. 6
CIR 0/4
Shapers
WR.1 SP 1 Sh. 7
CIR/EIR
WR.1 SP 2 Sh. 7 Shapers
WR.1 SP 3 Sh. 7
Flow 30 WR.1 SP4 Sh. 7
Sh. 3
Def. WR. WFQ 20
Def. WR. WFQ 30 q_block_11_queue_WFQ_10_20
1/2
Def. WR. WFQ 40 CIR/EIR
Shapers
q_block_4_WFQ_4_SP_10_40 WFQ 10
CIR 0/5 WFQ 20

Shapers
Sh. 5
WR.1 SP 1 Sh. 7
CIR/EIR
WR.1 SP 2 Sh. 7 Shapers
WR.1 SP 3 Sh. 7
Flow 40 WR.1 SP4 Sh. 7
Sh. 1
Def. WR. WFQ 20
Def. WR. WFQ 30
Def. WR. WFQ 40
Figure 11-56. Traffic Management Example

************************Configuring_Shaper_Profiles**************************
config qos shaper-profile sh1 bandwidth cir 10000 cbs 100000 eir 50000 ebs
200000
200000
200000
200000
200000
config qos shaper-profile sh6 bandwidth cir 130000 cbs 100000
200000
exit all
#*********************************End****************************************
**************************Configuring_WRED_Profiles**************************
config qos wred-profile 1 color green min 30 max 30 probability 100
config qos wred-profile 1 color yellow min 20 max 30 probability 100
#*********************************End****************************************
**********************Configuring_Internal_Queue_Profiles********************
config qos queue-internal-profile qstrict
congestion-avoidance wred profile 1
scheduling strict
shaper profile sh7
exit all
config qos queue-internal-profile q10
congestion-avoidance wred profile DefaultWREDProfile
scheduling wfq 10
shaper profile sh7
exit all
scheduling wfq 20
exit all
scheduling wfq 30
exit all
scheduling wfq 40
exit all
config qos queue-internal-profile q10_no_wred
scheduling wfq 10
exit all

scheduling wfq 20
exit all
scheduling wfq 30
exit all
scheduling wfq 40
exit all
#*********************************End****************************************
#****************************************************************************
*********************Configuring_Queue_Block_Profiles************************
#****************************************************************************
#*******************Configuring_Queue_Block_Profile_L2-1*********************
config qos queue-block-profile "q_block_21_queue_WFQ_10_20"
queue 1 internal-profile profile q10_no_wred
exit all
#*********************************End****************************************
#********************Configuring_Queue_Block_Profile_L1-1********************
config qos queue-block-profile "q_block_11_queue_WFQ_10_20_30"
exit all
#*********************************End****************************************
#*********************Configuring_Queue_Block_Profile_L1-2*******************
config qos queue-block-profile "q_block_12_queue_WFQ_10_20"
exit all
#*********************************End****************************************
#**********************Configuring_Queue_Block_Profile_L0-1******************
config qos queue-block-profile "q_block_4_WFQ_4_SP_10_40"
queue 1 internal-profile profile qstrict
queue 5 internal-profile profile q10
exit all
#*********************************End****************************************
#**********************Configuring_Queue_Block_Profile_L0-2******************
config qos queue-block-profile "q_block_4_WFQ_4_SP_40_10"


exit all
#*********************************End****************************************
#**********************Configuring_Queue_Group_Profile***********************
configure qos queue-group-profile 3level_1
queue-block 2/1
name "3Level_2_1"
profile "q_block_21_queue_WFQ_10_20"
shaper profile sh6
exit
queue-block 1/1
name "3Level_1_1"
profile "q_block_11_queue_WFQ_10_20_30"
bind queue 1 queue-block 2/1
shaper profile sh4
exit
queue-block 1/2
name "3Level_1_2"
profile "q_block_12_queue_WFQ_10_20"
shaper profile sh5
exit
queue-block 0/1
name "3Level_0_1"
profile "q_block_4_WFQ_4_SP_10_40"
shaper profile sh1
exit
queue-block 0/2
name "3Level_0_2"
shaper profile sh2
exit
queue-block 0/3
name "3Level_0_3"
shaper profile sh3
exit
queue-block 0/4
name "3Level_0_4"
shaper profile sh3
exit

queue-block 0/5
name "3Level_0_5"
shaper profile sh1
exit all
#*********************************End****************************************
#**********************Assigning_Queue_Group_to_Main_Card_Ports**************
config port ethernet main-b/1 queue-group profile 3level_1
config port ethernet main-b/2 queue-group profile 3level_1
exit all
#*********************************End****************************************
#***********************Defining_Classification_Keys*************************
exit all
#*********************************End****************************************
#*************************Enabling_Main_Card_Ports***************************
exit all
#*********************************End****************************************
#***********************Defining_Classifier_Profiles*************************
match vlan 100
exit all
match vlan 101
exit all
match vlan 102
exit all
match vlan 103
exit all
match vlan 104
exit all
match vlan 105
exit all
match vlan 106
exit all
match vlan 107
exit all
match vlan 200
exit all


match vlan 300
exit all
match vlan 400
exit all
match vlan 500
exit all
#*********************************End****************************************
#************************Configuring_CoS_Mapping_Profile*********************
config qos cos-map-profile cos7_0 classification p-bit
map 0 to-cos 7
map 1 to-cos 6
map 2 to-cos 5
map 3 to-cos 4
map 4 to-cos 3
map 5 to-cos 2
map 6 to-cos 1
map 7 to-cos 0
exit all
#*********************************End****************************************
#*********************** Configuring_Color_Mapping_Profile*******************
map 0 to green
map 1 to green
map 2 to green
map 3 to green
map 4 to green
map 5 to green
map 6 to green
map 7 to green
exit all
#*********************************End****************************************
classifier class100
0/1
no shutdown
exit all

classifier class101
0/1

no shutdown
exit all

classifier class102
0/1
no shutdown
exit all

classifier class103
0/1
no shutdown
exit all

classifier class104
0/1
no shutdown
exit all

classifier class105
0/1
no shutdown
exit all

classifier class106
0/1
no shutdown
exit all

classifier class107


0/1
no shutdown
exit all

classifier class200
0/2
no shutdown
exit all

classifier class300
0/3
no shutdown
exit all

classifier class400
0/4
no shutdown
exit all

classifier class500
0/5
no shutdown
exit all
#*********************************End************************************
11.10 Frequently Asked Questions

Below are five frequently asked questions as well as the answers to these
questions.
ETX-5 Frequently Asked Questions 11-151

1. Q: What kind of Vlan editing actions are available per flow?
A: VLAN editing consists of:

• VLAN Marking – Swap VLAN + definition of p-bit values by
either copy, fixed per flow or using marking-profile
• VLAN tagging – Push/POP VLAN + definition of p-bit values by
either copy, fixed per flow or using marking-profile
2. Q: In what cases does the ETX-5 boot from the Rollback-config?
A: The ETX-5 boots from Rollback-config when there is no startup-

config.
3. Q: What is the default classification key on the Main Card Port?
A: The default classification key on the Main Card Port is ‘VLAN + P-

bit’, which means that single VLAN definitions are supported.
4. Q: What should the classification key be on the Main Card Port to
support double tagged frame classification?
A: If you wish to support double tagged frame classification (in
addition to single tagged frame classification) on the Main Card
port, you need to change the classification key on the port to
‘Outer VLAN + Inner VLAN + P-bit’.
5. Q: What are the different default Q-Group scalabilities?
A: The following scalabilities are for both main and I/O ports in total:
1. UP to two q_group_3_level_768_default per single Main card. If
you assign it on IO ports, the scale is one per chassis.
2. Up to four q_group_3_level_384_default per single Main card. If
you assign it on IO ports, the scale is 4 per chassis.
3. Up to 88 q_group_2_level_default, please note that the limitation
with this queue group is 8 EVCs per port. (8 queue blocks in
level 0)
11.11 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.
11-152 Technical Support ETX-5

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-5 Technical Support 11-153

11-154 Technical Support ETX-5

Chapter 12
Software Upgrade
This chapter explains how to upgrade the ETX-5 software.
Software upgrades may be required to fix product limitations, to enable new
features, or to make the unit compatible with other devices that are already
running the new software version. New software releases are distributed as *.bin
files, to be downloaded to ETX-5.
ETX-5 can store four software versions, one in each of the four partitions of its
flash memory, which also contains a boot program. The software is stored in
compressed format.
12.1 Compatibility Requirements

The compatibility requirements for ETX-5 are as follows:
• Software – Version 1.5X, 2.0x, 2.2x, 2.4x, 2.6x
• Main card hardware – o.o/H and above
12.2 Impact
The software upgrade process is designed to minimize service disruption, as long
as following criteria are met:
• Two main cards are installed in the chassis
Note If your system has two main cards, you must upgrade only the active card. The
active card transfers new application software to the standby card to ensure
seamless redundancy after the upgrade. Verify that both main cards are
administratively enabled (no shutdown).
• Ethernet services are protected, using inter-card LAG or ERP

• TDM services are protected, using IO Card protection (inter-card APS).
ETX-5 Impact 12-1

Chapter 12 Software Upgrade Installation and Operation Manual
12.3 Prerequisites
This section details the software file names and outlines system requirements
needed for the upgrade procedure.
Software Files
New version releases are distributed as software files named *.bin, for example
sw-pack.bin. The files can be obtained from the local RAD business partner from
whom the device was purchased.
The software upgrade utility includes four partitions called sw-pack-1, sw-pack-2,
sw-pack-3, sw-pack-4 for downloading and storing the software versions. To
activate the specified software version, one of these partitions is set to active.
Each software pack consists of a set of image files for each module with
appropriate headers. The software pack can be ordered for the entire chassis
only.
The software pack consists of five internal image files for the E5-MC-4, E5-MC-
SFP-P-4, E5-GBE-20/E5-1-GBE-2 E5-cTDM-4 and E5-cTDM-STM4 cards. The
software pack is installed as a whole entity; internal software files cannot be
changed or installed separately.
The software package version, as well as version of internal image files can be
viewed using the show sw-pack command entered at the file# prompt.
System Requirements
Before starting the upgrade using SFTP or FTP, verify that you have the following:
• ETX-5 unit with valid network connection to a PC with the SFTP/FTP server
application, and a valid IP address.
• Software file stored on the PC.
12.4 Software Upgrade Options

Application software can be downloaded to ETX-5 via CLI (using SFTP) or via the
boot menu (using FTP).
12.5 Upgrading Software using the CLI

The recommended method for downloading software to the flash disk is to use
the file copy command of the CLI environment. This can be done remotely and
does not require booting. Only CL modules need to be reset after this procedure.
The upgrade consists of two stages:
12-2 Upgrading Software using the CLI ETX-5

Installation and Operation Manual Chapter 12 Software Upgrade
• The application software is downloaded from a PC to the ETX-5 flash disk.

This is done via SFTP, using the file>copy command
• The software pack is downloaded from the flash disk to the CL. This is done,
using the admin>software>install command.
Using SFTP
Network administrators use the SFTP protocol to securely distribute new
software releases to all the managed ETX-5 units in the network from a central
location. A central SFTP server application is installed on a PC on the network.
Application file is
transferred to
ETX-5
Ethernet
PC with an Active ETX-5

SFTP Server and
Application File
Figure 12-1. Downloading a Software Application File to ETX-5 via SFTP
 To download the software release to ETX-5 using the copy command.

1. Verify that the required image file is stored on the PC together with the SFTP
server application.
2. Verify that ETX-5 has a valid network connection to the PC
3. Ping the PC to verify the connection.
4. Activate the SFTP server application, as explained in Activating the SFTP
Server.
5. Download the image file to the unit, as explained in Downloading the New
Software Release File to ETX-5 Flash Disk.
Note Configuration values shown in this chapter are examples only.
Pinging the PC
Check the integrity of the communication link between ETX-5 and the PC by
pinging the ETX-5 from the PC.
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 executes the received request
automatically.
 To run the SFTP server:

• Activate a third-party SFTP server application.
Downloading the New Software Release File to ETX-5 Flash Disk

Use this procedure to download the new software release to the ETX-5 flash disk.
ETX-5 Upgrading Software using the CLI 12-3

 To download an application file to the ETX-5 flash disk via CLI:

• At the file# prompt, enter the copy command, as follows:
copy sftp://<SFTP_user_name>:<SFTP_password>@<sftp_ip_address>/
<image_file_name> sw-pack-<index 1..4>
where sftp-ip-address is the IP address of the PC in which the SFTP server is
installed.
• For example, to download the sw-pack.bin file to sw-pack-4 partition from
the PC at 10.10.10.10 with user name admin and password 1234:
ETX-5>file# sftp://<admin>:<1234>@10.10.10.10/sw-pack.bin sw-
pack-4
You are prompted to confirm the request:
Are you sure? [yes/no] _ y
The application file begins downloading.
Note Issuing the dir command (file# prompt) while installing a new software release
causes the CLI to stop responding during the installation process. The CLI
connection is restored after the SW installation is complete.
 To check the flash memory contents:

• At the file# prompt, enter the dir command, for example:
ETX-5>file# dir
Codes C - Configuration S - Software LO – Log
sw-pack-1 S 6306207 21-12-2010 valid
13:44:58
sw-pack-2 S 6305847 21-2-2011 valid
7:48:0
sw-pack-3 S 6278526 21-2-2011 valid
9:57:47
sw-pack-4 S 6289552 6-1-2011 valid
10:23:13
startup-config C 95872 13-3-2011 valid
14:7:35
user-default-config C 95872 13-3-2011 valid
14:6:51
factory-default-conf C 796 1-1-1970 Read Only
0:0:9
running-config C 0 1-1-1970 Read Only
0:0:9
 To monitor the copy progress:

• At the file# prompt, enter the show copy command, for example:
ETX-5# show file copy
Network to Device, Transferring Data
Src: sftp://172.17.174.56/2.27.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Transferred : 665600 Bytes in: 16 seconds (41600 Bytes/Second)

Finally, the application file is downloaded and saved in partition 4 of the

flash disk.
File copy command was completed.
sftp://172.17.174.56/ sw-pack.bin copied to sw-pack-4
successfully
6306207 bytes copied in 133 secs (47415 bytes/sec)
Once the file is downloaded, the following message is displayed:
ETX-5>file# sw-pack.bin copied to sw-pack-4 successfully
 To display the partition contents:

• At the file# prompt, enter the show sw-pack command, for example:
ETX-5>file# show sw-pack
---------------------------------------------------------------
--------------
sw-pack-1 1.0.0(1.39) 2012-08-06 00:00:00 ready

Size
(Bytes)
---------------------------------------------------------------
main main.bin 1.0.0(1.91) 1.1 31728762
eth1g eth1g.bin 1.0.0(1.65) 1.1 10698214
stm1ch stm1ch.bin 1.0.0(1.53) 1.1 18829047
eth2X10g eth2X10g.bin 1.0.0(1.65) 1.1 15883998
Installing the New Software Release File from the Flash Disk
Once a file is saved on the ETX-5 flash disk, it must be copied to the main card to
replace the current software. The sw-pack file includes the new software version
for all the main and I/O cards, according to your purchase order.
Simultaneously download the new software release file to all the main and I/O
cards installed in the chassis.
During the installation process, ETX-5 stores active software and startup-config in
the restore-point-config file. As long as the restore point remains valid, you can
return the device to the restore point (the application software and startup-
config the device ran before the last software installation).
When ETX-5 includes redundant main cards, the chassis performs in-service
software upgrade (ISSU) and uses card protection to achieve a sub-100 ms
service disruption.
Caution ETX-5 cannot be configured during software installation process.
 To download the new software release file:

1. At the admin>software # prompt, enter the install command. For example:
ETX-5# admin
ETX-5>admin# software
ETX-5>admin>software# install sw-pack-3

Note If you intend to skip creation of a restore point, enter the no-restore-point
parameter in the following form: install <filename> [no-restore-point].
ETX-5 displays confirmation request:

! Device will install file and reboot. Are you sure? [yes/no] _
2. For ETX-5 with a single main card:
 Confirm the install.
The previous software pack is deleted from the active partition:
deleting file /tffs0/Sw-Pack/Active/main.bin
deleting file /tffs0/Sw-Pack/Active/eth1g.bin
deleting file /tffs0/Sw-Pack/Active/eth2X10g.bin
deleting file /tffs0/Sw-Pack/Active/stm1ch.bin
The software pack stored in sw-pack-3 partition is transferred to the
active partition and sent to all relevant cards that are found in the
chassis. ETX-5 performs reboot automatically and is now ready for
operation with new software version.
ETX-5 is upgraded and starts with the new software version.
or
3. For ETX-5 with redundant main cards:
 Confirm the install.
 The primary main card resets the secondary main card.
 The secondary main card starts up with the new software.
 When the secondary main card is online, the primary card resets
itself.
 The secondary main card becomes primary.
 The former primary card starts up with the new software and
becomes secondary.
 Reset the I/O cards manually to complete the installation process.
Confirmation of Software Application File

ETX-5 allows users to enable active confirmation of application software file after
reboot. Software file confirmation serves to prevent loss of the management link
to a remote device due to an invalid file.
If confirmation of application software file is enabled, you must confirm the
software within a defined period of time. If you fail to confirm the software, ETX-
5 copies the previous application software from the restore-point-config file,
reboots, and runs the previous application software version.
Note For ETX-5 with redundant main cards, you can confirm the software application
files only after the main card flip.

 To enable software application confirmation:

• At the admin>software# prompt, enter the software-confirm-required
command according to the table below.
Enabling or disabling software-confirm-required [time-to- Default time-to-confirm –

confiramation of application confirm <5–1440>] 5 min.
software file after reboot no software-confirm-required
to disable application software
confirmation
Displaying Software Upgrade Status

You can display the current software upgrade status for the system and all cards
installed in the chassis.
 To display the software upgrade status:

• At the admin>software # prompt, enter show status.
ETX-5300A>admin>software# show status
Software Installation Status : Idle
Remaining Time to Confirm Software Installation : --
Active Software : sw-pack-1 Version : 1.0.0

Restore Point Software : sw-pack-1 Version : 1.0.0
Slot Upgrade Status

---------------------------------------------------------------
main-a Ready
main-b Ready
1 Empty
2 Empty
3 Empty
4 Empty
The chassis software installation statuses are as follows:
• Idle – No software installation performed since the last reboot
• In Progress – New software is being installed, reboot has not been performed
yet
• Ended Successfully – New software installed, with or without reboot
• Failed – Software installation has failed
• Main Card Reset Failed – Installation failed due to failure of the secondary
main card to reset correctly
• Ended with Error – Unknown error has occurred during software installation
• Aborted By User – Installation failed due to user intervention
• Software Unconfirmed:
 Software confirmation was not received on time
 ETX-5 was reset before receiving software confirmation

 Previous software version is about to be reinstalled

• Awaiting Confirmation –Installation is on hold, pending user confirmation of
the software file
• Awaiting Card Reset – The software was confirmed, or no confirmation was
required, and ETX-5 waits for reset of at least one I/O card
• Software Installed From Boot – ETX-5 detected a new software release
installed via the Boot menu
• Unconfirmed Software Used in Lack Of Valid Software – ETX-5 uses
unconfirmed software due to the lack of confirmed file
The slot software installation statuses are as follows:
• Ready – The card is installed and ready to accept the software package
• Empty – The card slot is empty
• In Progress – The card has been reset and software installation is in progress
• Manual Wait – Software installation has started, but the card has not been
reset yet
• Failure – Software installation has failed.
12.6 Upgrading Software via the Boot Menu

Software download may also be performed using the Boot menu.
The upgrade consists of two stages:
• The application software is downloaded from a PC to the ETX-5 flash disk.
This is done via FTP, using the download command
• The software pack is downloaded from the flash disk to the CL. This is done,
using the set-active command.
The Boot menu can be accessed while ETX-5 is performing initialization, such as
after power-up.
You may need to start the loading from the Boot menu when it is not possible to
activate SFTP using the CLI because, for example, the ETX-5 software has not yet
been downloaded or is corrupted.
Caution The Boot menu procedures are recommended for use only by authorized
personnel, because this menu provides many additional options that are intended
for use only by technical support personnel.
You can upgrade via the Boot menu using the FTP. This is usually performed by
downloading from a remote location that provides an IP communication path to
an Ethernet port of ETX-5.
Note All the screens shown in this section are for illustration purposes only. Your ETX-5
may display different software versions and port profiles.
12-8 Upgrading Software via the Boot Menu ETX-5

The preparations for using the FTP protocol via the Boot menu are similar to the
preparations for downloading software using the SFTP protocol via the CLI. The
main difference is that you need to define the IP communication parameters
associated with the corresponding Ethernet port -- IP addresses and the
associated subnet mask, and a default gateway IP address.
Starting Boot Manager

Prior to initiating the VXWORKS Boot Manager functionality, connect the ASCII
terminal or PC with terminal emulation to the CONTROL DCE (serial) port of
ETX-5.
 To start VXWORKS Boot Manager:

4. Verify that the *.bin file is stored on the PC with the terminal application.
5. Configure the communication parameters of the selected PC serial port for
asynchronous communication for 115.2 kbps, no parity, one start bit, eight
data bits and one stop bit. Turn all types of flow control off.
6. Turn off ETX-5.
7. Activate the terminal application.
8. Turn on ETX-5.
Information about the System Boot, Boot version, and information about
CPU, OS-version, BSP version and Boot Manager version is displayed.
The following message appears:
Use '?'/help to view available commands.
Press any key to stop auto-boot....
9. Press any key to stop the auto-boot and get a boot prompt.
The boot prompt is displayed:
[boot]:
10. Press <?> to display the Help list.
The Help list is displayed.
• Commands:
?/help - print this list
p - print boot parameters
c [param] - change boot parameter(s)
v - print boot logo with
versions information
run - load active sw pack and
execute
delete <FileName> - delete a file
dir - show list of files
show <index> - show sw pack info
download <index> [,<FileName|x>] - download a sw pack to
specific index (x - by Xmodem)
set-active <index> - Set a sw pack index to be
the active application
control-x/reset - reboot/reset
Figure 12-2. VXWORKS Boot Manager Help List
ETX-5 Upgrading Software via the Boot Menu 12-9

11. Press <P> to display all boot parameters.

The boot parameters list appears. A typical boot parameters list is shown
in Figure 12-3. The parameters are described in Table 12-1.
[boot]: p
file name (fn) : vxworks

device IP (ip) : 10.10.10.88
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.10
gateway IP (g) : 10.10.10.10
user (u) : vxworks
ftp password (pw) : *******
device name (dn) : ETX-5
quick autoboot (q) : yes
protocol (p) : ftp
baud rate (b) : 9600
Figure 12-3. Typical Boot Parameters Screen
Table 12-1. Boot Parameters
Parameter Command Description
file name fn The binary software pack file (*.bin) name
device ip ip The IP address of ETX-5
device mask dm The IP subnet mask of ETX-5
server IP sip The FTP server IP address
gateway ip g The FTP server default gateway IP-address if the server

is located on a different LAN.
Note: Be sure to select an IP address within the subnet
of the assigned ETX-5 IP address.
Note: If no default gateway is needed, for example,
because the FTP server is attached to the same LAN as
ETX-5 being upgraded, enter 0.0.0.0.
user u The user name, as registered at the FTP server.

Note: Displayed only when using FTP Protocol.
ftp password vx The user password, as registered at the FTP server.

Note: Displayed only when using FTP Protocol.
device name dn ETX-5
quick autoboot q Enabling or disabling the quick autoboot feature
protocol p The file transfer protocol in use: FTP only
baud b Transmission bit rate (in kbps): 9600, 19200, 115200

rate
Note The CLI commands are case insensitive.

12. Press <C> to change the boot parameters and type valid values in each field.
 Type 'c' to modify all parameters
 Type 'c [parameter]' to modify the specific parameter (for example, to
change the filename to sw-pack.bin, type: c fn vxworks sw-pack.bin).
'.' = clear field; '-' = go to previous field; ^D = quit
file name (fn) : vxworks sw-pack.bin

device IP (ip) : 10.10.10.88
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.10
gateway IP (g) : 10.10.10.10
user (u) : vxworks
ftp password (pw) (blank = use rsh): *******
device name (dn) : ETX-5
quick autoboot [y/n] : y
protocol [tftp/ftp] : ftp
baud rate [9600/19200/115200]: 9600
13. To complete the upgrade and log on again, follow the onscreen instructions.
Using the FTP Protocol

Use the following procedure to download software release to ETX-5 via FTP.
 To download software file(s) from the Boot menu to ETX-5 via FTP:
14. Verify that the *.bin file is stored on the PC with the FTP server application.
15. Activate the FTP server application.
Note When working with FTP server, the user name and password in Boot parameters
must be the same as defined in FTP server.
16. Turn on ETX-5 and enter the Boot menu. Set FTP protocol.
17. From the Boot menu, type download <index 1..4> [<FileName>] command to
start downloading the software pack file from the PC to the corresponding
partition of the ETX-5 flash disk.
Note [<FileName>] is used if you did not specify the filename in the Boot menu
earlier.
For example: Download the file to sw-pack-2

[boot]: download 2
The file is being copied to sw-pack-2 partition:
File transferring - 7580KB
226 Transfer finished successfully.
Please wait, old file is being erased and written with new one.
File writing to flash: - 7580KB
File downloaded successfully to :2
[boot]:
ETX-5 Upgrading Software via the Boot Menu 12-11

18. Using dir command, check which partition is currently active. In this example it
is sw-pack-1.
[boot]: dir
SIZE FILE-NAME
796 factory-default-config
6296759 sw-pack-1
6305902 sw-pack-2
6278526 sw-pack-3
6289552 sw-pack-4
Active SW-pack is: 2
19. Use set-active command to activate the partition to which the file has been
downloaded (in this example: sw-pack-2).
[boot]: set-active 2
set-active may take few minutes...
deleting file /tffs0/Sw-Pack/Active/main.bin
deleting file /tffs0/Sw-Pack/Active/mainHdr.bin
SW set active 2 completed successfully.
The new software release is now stored in partition 2 and will be
activated after reset.
20. Perform one of the following:
 Type “@” or “run”.
The following message is displayed and the new software release is
activated:
[boot]: run
External file header passed validation!
Loading/un-compressing main.bin...
Starting the APPLICATION off address 0x10000...
 Press <Ctrl + X> to perform a cold (hard) reboot with turning power off
and then on.
 Type “reset” to perform a warm (soft) reboot without turning off power.
The following message is displayed:
Are you sure (y/n)?
Press <Y>.
When the downloading process is successfully completed, you will see a
sequence of messages similar to the following:
Instantiating /ram as rawFs, device = 0x20001

Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x20001
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0

Root dir entries 0, sysId (null) , serial number 7d0000

Label:" " ...
Disk with 64 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 54 clusters, 1 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 2
Root dir entries 112, sysId VXDOS12 , serial number 7d0000
Adding 71349 symbols for standalone.


21. Press <Enter> to start working with the new SW release downloaded.
Note The new parameters take effect only after the reset is completed.
12.7 Verifying the Upgrade Results

To verify that the upgrade was successful, log on to ETX-5 to view the Inventory
summary.
 To verify the upgrade result:

• At the config# prompt, enter show inventory-summary and verify the active
software version in the SW Ver column.
ETX-5# config>chassis# show inventory-summary
-----------------------------------------------------------------------------
1001 Chassis AC-chassi N/A 1.0.0(1.39) N/A
2001 Backplane Backplane 0.0/A N/A N/A
3005 Container main-a N/A N/A N/A
3006 Container main-b N/A N/A N/A
ETX-5 Verifying the Upgrade Results 12-13

12-14 Verifying the Upgrade Results ETX-5

3097 Container FAN N/A N/A N/A
4001 Power Supply PS_AC 1 0.0/- N/A N/A
4002 Power Supply PS_AC 2 0.0/- N/A N/A
4003 Fan FAN 0.0/A N/A N/A
5001 Module IO Card 1 0.1/- 1.0.0(1.65) 2.0
5004 Module IO Card 4 0.1/- 1.0.0(1.65) 2.0
5005 Module Main Card A 0.0/G 1.0.0(1.91) 2.0

5006 Module Main Card B N/A N/A N/A
7001 Port Etherent port main-a/1 N/A N/A N/A
7009 Port MNG Port N/A N/A N/A
12-16 Verifying the Upgrade Results ETX-5


Note If downloading failed, repeat the entire procedure.
12.8 Restoring the Previous Software Version

ETX-5 can roll back to previous application software version, as long as the valid
restore-point-config file exists in the system.
 To roll back to previous software version:

22. At the admin>software# prompt, enter the undo-install command.
ETX-5 displays confirmation request:
! This action will revert system to restore point. Are you sure? [yes/no] _
23. Confirm the install.
ETX-5 reverts to the previous software version and _reboots.
12-18 Restoring the Previous Software Version ETX-5

Chapter 13
Application Tutorial
This chapter provides configuration guidelines for a typical application of an ETX-
5 system.
The configuration activities presented in this chapter assume that ETX-5 is
configured using a standard ASCII terminal, and that you are familiar with ETX-5
management as described in Chapter 4.
This section illustrates how to set up typical E-Line service with Ethernet ring and
LAG protection. In addition, it details procedures for creating a pseudowire
connection and collecting OAM statistics.
Figure 13-1 illustrates the application layout. Table 13-1 details a summary of
port connections.
ETX-203AX (1)
(172.17.191.11)
GbE
GbE ERP
NMS
ETX-1
(172.17.191.14)
GbE
GbE GbE
MiNID Traffic Generator
(172.17.191.13)
GbE GbE
ETX-204A
(172.17.191.19)
ETX-5 GbE
(172.17.191.10)
LAG ETX-203AX (2)
STM-1 GbE
(172.17.191.16)
GbE
E1
ETX-205A
(172.17.191.12) E1 Tester
Figure 13-1. Application Diagram
Table 13-1. Connection Summary
From Device/Port To Device/Port Service Comments
E5-MC-4, MNG ETH Ethernet on NMS Management Telnet for CLI-based

configuration
E5-GBE-20, 1/1 ETX-203AX (1), port 2 E-Line

ERP
E5-GBE-20, 1/14 ETX-1 via MiNID E-Line
E5-GBE-20, 1/2 ETX-203AX (2), port 1 E-Line LAG
Equipment List 13-1

Chapter 13 Installation and Operation Manual
From Device/Port To Device/Port Service Comments
E5-GBE-20, 1/13 ETX-205A, port 1 E-Line
E5-cTDM-4, 3/1 PW CES SFP loopback plug
ETX-203AX (1), port 3 ETX-204A, port 3 E-Line
ETX-1, port 3 ETX-204A, port 4 E-Line
ETX-203AX (2), port 3 ETX-204A, port 5 E-Line
ETX-205A, port 3 ETX-204A, port 6 E-Line
ETX-205A, port E1-1 E1 tester PW CES
13.1 Equipment List

Table 13-2 lists the devices required for the application.
Table 13-2. Required Equipment
Device Quantity
ETX-5 chassis with fan unit 1

E5-MC-4 card 1
E5-GBE-20 card 1
E5-cTDM-4 card 1
ETX-203AX 2
ETX-1 1
MiNID 1
ETX-205A 1
ETX-204A 1
E1 tester 1
Fiber optic cables with LC connectors 9
Cat.5 cross Ethernet cable 1
Cat.5 straight Ethernet cable 1
Cat.5 straight E1 cable 1
Network management station 1
SFP loopback plug 1
13.2 Installing the Units

Before starting configuration, install units as follows:
13-2 Installing the Units

Installation and Operation Manual Chapter 13
1. Connect the PC to the MNG ETH port on E5-MC-4 card, using a cross Ethernet
cable.
1 2 3 4 MNG ETH PRI
FLT
CLK
RMV
E5-MC-4 10/100/1000BASE-T
E5-MC-4
Cross Ethernet Cable
LAN
PC
Figure 13-2. Connecting the PC to E5-MC-4
2. Connect port 1 on E5-GBE-20 card to port 2 on ETX-203AX (1), using a fiber

optic Ethernet cable.
11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
Fiber Optic Ethernet Cable
CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (1)
Figure 13-3. Connecting E5-GBE-20, Port 1 to ETX-203AX (1), Port 2

Installing the Units 13-3

11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (1)
4. Install MiNID in port 1 on ETX-1.

5. Connect port 14 on E5-GBE-20 card to MiNID, using a fiber optic Ethernet
cable.
11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
USER - 10/100/1000BT
10/100BaseT 100BASE-FX/1000BASE-X
CONTROL MNG-ETH
NET/USER NET
DCE
2 1
ETX-1 with MiNID
Figure 13-5. Connecting E5-GBE-20, Port 14 to MiNID in ETX-1, Port 1

11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (2)


11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (2)
8. Connect port 13 on E5-GBE-20 card to SFP port 1 on ETX-205A, using a fiber

11 20
LINK FLT
ACT
RMV
1
E5-GBE-20 100/1000BASE-X
E5-GBE-20
GbE/100Fx E1/T1
EXT CLK TOD/1PPS EXT CLK 1 2 3 4
NET NET-USER USER
ETX-205A
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
1 LINK/ACT 2 3 4 5 6 LOC REM POWER POWER
PWR
DCE LINK ACT 10/100/ PS1 PS2
1000BT
ETX-205A
Figure 13-8. Connecting E5-GBE-20, Port 13 to ETX-205A, Port 1
9. Connect port 3 on ETX-203AX (1) to SFP port 3 on ETX-204A, using a fiber

CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (1)
NET NET/USER USER

EXT CLK TOD/1PPS EXT-CLK 1 2 3 4 5 6 ETX-204A
1PPS
CONTROL GbE/100Fx
1 2 3 4 5 6
DCE
MNG-ETH RAD
10/100/1000BT
ETX-204A
Figure 13-9. Connecting ETX-203AX (1), Port 3 to ETX-204A, Port 3
10. Connect port 3 on ETX-1 to RJ-45 port 4 on ETX-204A, using a straight

Ethernet cable.
Installing the Units 13-5

USER - 10/100/1000BT
10/100BaseT 100BASE-FX/1000BASE-X
CONTROL MNG-ETH
NET/USER NET
DCE 5 3 6 4 2 1
ETX-1 with MiNID
Straight Ethernet Cable
NET NET/USER USER

1PPS
CONTROL GbE/100Fx
1 2 3 4 5 6
DCE
MNG-ETH RAD
10/100/1000BT
ETX-204A
Figure 13-10. Connecting ETX-1, Port 3 to ETX-204A, Port 4
11. Connect port 3 on ETX-203AX (2) to SFP port 5 on ETX-204A, using a fiber
CONTROL
NET NET/USER USER
1 2 3 4 5 6
MNG-ETH ETH
ETX-203AX (2)
NET NET/USER USER

1PPS
CONTROL GbE/100Fx
1 2 3 4 6
DCE
MNG-ETH RAD
10/100/1000BT
ETX-204A
Figure 13-11. Connecting ETX-203AX (2), Port 3 to ETX-204A, Port 5
12. Connect SFP port 3 on ETX-205A to SFP port 6 on ETX-204A, using a fiber
GbE/100Fx E1/T1
NET NET-USER USER
ETX-205A
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
1000BT
ETX-205A
NET NET/USER USER

1PPS
CONTROL GbE/100Fx
1 2 3 4 6
DCE
MNG-ETH RAD
10/100/1000BT
ETX-204A
Figure 13-12. Connecting ETX-205A, Port 3 to ETX-204A, Port 6
13. Connect E1 tester to E1 port 1 on ETX-205A.

GbE/100Fx E1/T1
NET NET-USER USER
ETX-205A
1PPS
RAD TST/
ALM CONTROL
SD
MNG-ETH
PWR
1000BT
ETX-205A
Straight E1 Cable
E1 Tester
Figure 13-13. Connecting E1 Tester to ETX-205A, E1 Port 1
14. Install the SFP loopback plug in SDH port 1 of E5-cTDM-4 card to loop the
TDM traffic back to the network tester.
20
OC-3/STM-1 FLT
RMV
LOS LOS LOS LOS
E5-cTDM-4
Figure 13-14. Installing the SFP Loopback Plug in Port 1 on E5-cTDM-4
13.3 Preliminary Configuration

Preliminary configuration includes the following steps:
1. Resetting the chassis to factory defaults (recommended)
2. Configuring ETX-5 administrative parameters
3. Configuring queue groups.
Resetting to Factory Defaults

Before starting the configuration process, it is recommended to reset ETX-5 to
factory defaults.
 To reset ETX-5 to factory defaults:

1. At the device prompt, enter admin.
2. Enter factory-default.
Current configuration will be erased and device will reboot with factory
default configuration.
3. Enter yes to confirm resetting to factory defaults.
Preliminary Configuration 13-7

The factory-default file is copied to the startup-config file. Now at device

startup, the factory defaults are loaded.
Configuring Administrative Parameters

Administrative parameter configuration includes defining system name, setting
CLI timeout and provisioning I/O cards.
Assigning Name to the Chassis

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

ETX-5# config sys name Central ETX-5
Central ETX-5# exit
Disabling CLI Timeout

You can prevent ETX-5 from disconnecting automatically from the NMS by
disabling the CLI security timeout.
 To disable CLI timeout:

config terminal timeout forever
exit
Provisioning I/O Cards

You must provision (initialize) the I/O cards installed in slot 1 and slot 3. ETX-5
service cards (power inlets, power supplies, fan card) and main cards are
detected and provisioned automatically.
Before provisioning, you can verify that ETX-5 have detected the E5-GBE-20 and
E5-cTDM-4 cards in their slot respective slots. After it, provision the cards and
verify that the procedure is successful.
 To check the installed I/O cards:

show config cards-summary
-----------------------------------------------------------------------------
Main-B Empty Main 10GbEx4 Up Not Present Standalone
1 GBEx20 SFP Down Down Down Standalone
3 STM-1 4-Ch Empty Down Down Standalone
13-8 Preliminary Configuration

 To provision I/O cards:

configure slot {1}
card-type {eth gbe-20-sfp}
exit all
configure slot {3}

card-type {sdh-sonet stm-1-ch-4}
exit all
 To verify the successful operation:

show config slot 1 status
Actual Type : GBEx20 SFP
Provisioned Type : GBEx20 SFP
Configuring Queue Groups

This section describes configuration of queue groups to be used by ETX-5 and
ETX-2 units for traffic management.
Note The actual queue group parameters depend on network design and service
requirements. The traffic management parameters appearing in these examples
are used for illustration only.
ETX-5 Queue Group Configuration

ETX-5 uses two-level queue groups to manage R-APS, management and service
1–3 traffic.
 To configure traffic management within ETX-5:

1. Add a new queue group profile (QG_ring_node), based on the default queue
group profile – q_group_2_level_default.
2. Configure queue block profile (q_block_ring_port) for level-1 scheduling
element 1/1.
a. Define internal queue profiles for q_block_ring_port, specifying their
scheduling types.
b. Add level-1 queue block profile and assign internal queue profiles to it.
3. Configure two single-rate shapers for 1 Mbps and 10 Mbps to be applied to
R-APS and management traffic (level-0 scheduling elements 0/1 and 0/2).
4. Configure queue block profile (q_block_service_cos) for level-0 scheduling
elements 0/4 and 0/5.
a. Define internal queue profiles for q_block_service_cos, specifying their
scheduling types and WRED profiles.
b. Add level-0 queue block profile and assign internal queue profiles to it.

5. Configure the QG_ring_node queue group profile, binding the queue block
profiles. Queue blocks are added to queue group in the reverse order: level 1
> level 0.
 Queue block 1/1 – modified weighted priority queues, no shaper
 Queue block 0/1 – default strict and weighted priority queues, 1 Mbps
shaper
 Queue block 0/2 – default strict and weighted priority queues, 10 Mbps
shaper
 Queue block 0/3 – default strict and weighted priority queues, no shaper.
This queue block uses default values and does not need to be modified.
 Queue block 0/4 – modified strict and weighted priority queues, no
shaper
shaper.
Figure 13-15 illustrates traffic scheduling and shaping within ETX-5. Detailed
configuration instructions are provided in the script below.

QG_ring_node
0/1
sp
sp
sp
R-APS Traffic sp 1 Mbps
wfq Shaper
wfq
wfq
wfq
0/2 Weight = 1
sp
sp
sp 10 Mbps
Management Traffic sp Shaper
wfq
wfq
wfq
wfq Weight = 1
0/3 1/1
sp wfq, 1
sp wfq, 1
sp wfq, 33
Service 1 Traffic sp Weight = 33 wfq, 60
wfq wfq, 60
wfq wfq, 1
wfq wfq, 1
Weight = 60
wfq wfq, 1
0/4
sp
sp
sp
Service 2 Traffic sp Weight = 60
wfq, 3
wfq, 2
wfq, 1
wfq, 1
0/5
sp
sp
sp
Service 3 Traffic sp
wfq, 3
wfq, 2
wfq, 1
wfq, 1
Figure 13-15. ETX-5 Traffic Management
#*************************Adding_Queue_Group_Profile*************************
configure qos queue-group-profile QG_ring_node
inherited-from q_group_2_level_default
exit all
#*********************************End****************************************

#***********************Configuring_1/1_Queue_Block_Profile******************
config qos queue-internal-profile q_raps
scheduling wfq1
exit all
config qos queue-internal-profile q_mng

scheduling wfq1
exit all
config qos queue-internal-profile q_srv_1

scheduling wfq33
exit all

scheduling wfq60
exit all
scheduling wfq60
exit all
config qos queue-block-profile q_block_ring_port

queue 1 internal-profile profile q_raps
queue 2 internal-profile profile q_mng
queue 3 internal-profile profile q_srv_1
exit all
#*********************************End****************************************
#*************************Configuring_Shaper_Profiles************************
config qos shaper-profile sh1_1M bandwidth cir 1000 cbs256000
exit all
config qos shaper-profile sh1_10M bandwidth cir 10000 cbs256000

exit all
#*********************************End****************************************
#******************Configuring_0/4_and_0/5_Queue_Block_Profile***************
config qos queue-internal-profile qstrict
scheduling strict
exit all
config qos queue-internal-profile BBE

scheduling wfq 3
exit all
config qos queue-internal-profile BE

scheduling wfq 2
exit all

config qos queue-internal-profile LBE

scheduling wfq1
exit all
config qos queue-block-profile q_block_service_cos

queue 5 internal-profile profile BBE
queue 6 internal-profile profile BE
queue 7 internal-profile profile LBE
queue 8 internal-profile profile LBE
exit all
#*********************************End****************************************
#***********************Configuring_Queue_Group_Profile**********************
configure qos queue-group-profile QG_ring_node
queue-block 1/1
profile q_block_ring_port
exit
queue-block 0/1
shaper profile sh1_1M
exit
queue-block 0/2
shaper profile sh1_10M
exit
queue-block 0/4
profile q_block_service_cos
exit
queue-block 0/5
profile q_block_service_cos
exit all
#*********************************End****************************************
ETX-2 Queue Group Configuration

ETX-2 units use two-level queue group to manage traffic.
 To configure traffic management within an ETX-2 unit:

1. Configure queue block profile (profile11) for level-1 scheduling element 1/1.
Queues 0–2 are configured as weighted queues with 10, 10 and 33 weights.
2. Configure queue block profile (profile012) for level-0 scheduling elements 0/1
and 0/2.
 Queues 0–3 are configured as strict priority queues.
 Queues 4–7 remain weighted queues with default weights (100) and do
not need to be modified.

3. Configure queue block profile (profile013) for level-0 scheduling element 0/3.
 Queues 0–3 are configured as strict priority queues.
 Queues 4–7 are configured as weighted queues with 3, 2, 1 and 1
weights.
4. Configure a single-rate shaper for 1 Mbps to be applied to traffic coming via
level-0 scheduling elements 0/1 and 0/2.
5. Configure the q_group_test queue group profile, binding the queue block
profiles. Queue blocks are added to queue group in the reverse order: level 1
> level 0.
 Queue block 1/1 – modified weighted priority queues, no shaper
 Queue block 0/1 – modified strict priority and default weighted priority
queues, 1 Mbps shaper
 Queue block 0/2 – modified strict priority and default weighted priority
queues, 1 Mbps shaper
shaper.
Figure 13-16 illustrates traffic scheduling and shaping within ETX-5. Detailed
q_group_test
0/1
sp
sp
sp 1 Mbps
sp Shaper
wfq
wfq
wfq
wfq Weight = 10
0/2 1/1
sp wfq, 10
sp 1 Mbps wfq, 10
sp Shaper wfq, 33
sp Weight = 10 wfq, 1
wfq wfq, 1
wfq wfq, 1
wfq wfq, 1
Weight = 33
wfq wfq, 1
0/3
sp
sp
sp
sp
wfq, 3
wfq, 2
wfq, 1
wfq, 1
Figure 13-16. ETX-2 Traffic Management

#***********************Configuring_1/1_Queue_Block_Profile******************
config qos queue-block-profile profile11
queue 0
scheduling wfq10
exit
queue 1
scheduling wfq10
exit
queue 2
scheduling wfq33
exit all
#*********************************End****************************************
#******************Configuring_0/1_and_0/2_Queue_Block_Profile***************
queue 0
scheduling strict
exit
queue 1
scheduling strict
exit
queue 2
scheduling strict
exit
queue 3
scheduling strict
exit
exit all
#*********************************End****************************************
#**********************Configuring_0/3_Queue_Block_Profile*******************
queue 0
scheduling strict
exit
queue 1
scheduling strict
exit
queue 2
scheduling strict
exit
queue 3
scheduling strict
exit
queue 4
scheduling wfq3

exit
queue 5
scheduling wfq2
exit
queue 6
scheduling wfq1
exit
queue 7
scheduling wfq1
exit
exit all
#*********************************End****************************************
#*************************Configuring_Shaper_Profile*************************
config qos shaper-profile shape1 bandwidth cir 1000 cbs256000
exit all
#*********************************End****************************************
configure qos queue-group-profile q_group_test
queue-block 1/1
profile profile11
exit
queue-block 0/1
profile profile012
exit
queue-block 0/2
profile profile012
exit
queue-block 0/3
profile profile03
exit
queue-block 0/1
shaper profile shape1
exit
queue-block 0/2
shaper profile shape1
exit
#*********************************End****************************************

13.4 Configuring for Management

This section describes how to:
• Establish a link for IP-based management traffic from MNG-ETH port to the
ETX-5 management entity via router and bridge (see Configuring ETX-5
Management Flows).
• Ensure that management traffic reaches ETX-203AX (1) and protect the
traffic via ERP (see Configuring ETX-203AX (1) Management Flows and
Configuring ERP Instance for ETX-203AX (1)).
• Ensure that management traffic reaches ETX-203AX (2) and configure LAG
(see Configuring LAG for ETX-203AX (2)).
• Ensure that management traffic reaches ETX-205A (see Configuring ETX-5
Management Flows and Configuring ETX-205A Management Flows).
• Ensure that management traffic reaches MiNID (see Configuring ETX-5
Management Flows and Configuring MiNID for Management).
• Establish a tunnel between ETX-5 port 1/14 connected to MiNID and LAG
(port 1/2 and 1/12). The tunnel is necessary for demonstration MiNID ability
to serve as an OAM monitor. See Configuring ETX-5 Management Flows and
Configuring OAM (CFM).
Figure 13-17 illustrates management connections in the setup.
Telnet
IP Network
Management Router Bridge Bridge
ETX-203AX (1)
Management Router MiNID

Router
ETX-1
Management Router
Management
ETX-205A
ETX-5
Management Router
ETX-203AX (2)
Figure 13-17. Management Connectivity
Configuring for Management 13-17

Configuring ETX-5 Management Flows

Access from the MNG-ETH port to management entity is provided via a series of
concatenated flows, linking the port, bridge and router.
This section includes configuration instructions for creating flows used for inband
management of ETX-205A and MiNID units. Configuration of flows used for
managing ETX-203AX (1) and ETX-203AX (2) is explained in the Configuring
Ethernet Ring Protection and Configuring LAG sections below.
 To configure management traffic flows within ETX-5:

1. Configure two queue group profiles:
 workshop_SAG_level_2_profile to be applied to SAG 1/1 and SAG 1/1
 workshop_level_2_profile to be applied to port 1/13 (ETX-205A) and port
1/14 (MiNID).
It is recommended to create new queue group profiles and not to use the
default ones. ETX-5 Queue Group Configuration section above details how to
create queue group profiles for ETX-5.
2. Configure SVIs:
 Router-type 101
 Bridge-type 40
 Bridge-type 45
 Bridge-type 50
 Bridge-type 51
3. Add router interface 1 (RIF 1), configure IP address for the management
entity (172.17.191.10/24) and bind it to SVI 101.
4. Add bridge 1, bridge ports 40, 45, 50 and 51 and bind them to the respective
SVIs.
5. Define management VLAN 4094 and tagged egress ports.
6. Define classifier profiles (v4094, v3000, all and untagged).
7. Define marking profile (mark 1) for use by SVI 101 to SVI 51 flow.
Traffic leaving SVI 101 must be marked by VLAN 4094; a P-bit value and green
color must be assigned to it as well. As the router traffic receives internal
priority and CoS attributes, these attributes must be converted to P-bit and
DEI values, which are added to outgoing packets.
8. Activate port 1/13 (ETX-205A) and port 1/14 (MiNID).
 Four flows for forwarding management traffic from MNG-ETH port to
management entity
 From MNG-ETH port to SVI 50 (MNG_MA0toSVI50)
 From SVI 50 to MNG-ETH port (SVI50toMNG_MA0)
 From SVI 51 to SVI 101 (SVI51toSVI101)
13-18 Configuring for Management

 From SVI 101 to SVI 51 (SVI101toSVI51

 Three flows for ETX-205A inband management
 From port 1/13 to SAP 1/2/40 (1_13toSAP1_2_40_v4094)
 From SAP 1/2/40 to SVI 40 (SAP1_2_40toSVI40_v4094)
 From SVI 40 to port 1/13 (SVI40to1_13)
 Three flows for MiNID inband management
 From SVI 45 to port 1/14 (SVI45to1_14)
 Four flows for tunneling traffic between port 1/14 and LAG.
 From port 1/14 to SAP 1/2/400 (1_14to1_SAP1_2_400_v3000)
 From SAP 1/2/400 to LAG 1 (SAP1_2_400toLAG1_v3000)
 From LAG 1 to SAP 1/1/401 (LAG1to1_SAP1_1_401_v3000)
 From SAP 1/1/401 to port 1/14 (SAP1_1_401to1_14_v3000)
Note See Configuring LAG below for LAG configuration instructions.
10. Add a static route to default gateway (NMS at 172.17.191.1).

11. Display flow summary.
12. Ping ETX-5 from the NMS to verify the connectivity.
Figure 13-18 illustrates flow of the management traffic within ETX-5. Detailed
MNG-ETH
E5-GBE-20 E5-MC-4
SAP
SVI 40 SVI 50
SAP 40 50
Bridge
SAP
45 51
SAG 1
SVI 45 SVI 51
SAP SVI 101

1
SAP
Router
SAP
SAG 2
Management
ETX-5
Figure 13-18. Management Traffic Flow within ETX-5
Notes • Flows for MiNID inband management via BP 45 and SVI 45 are similar to the
flows used for ETX-205A management via BP 40 and SVI 40.
• Flows for tunneling VLAN 3000 traffic are created directly between port 1/14
and LAG without going via bridge ports.

#**************Assigning_Queue_Group_Profiles_to_SAGs_and_Ports**************
config port sag 1/1
queue-group profile workshop_SAG_level_2_profile
exit all
config port sag 1/2

exit all

queue-group profile workshop_level_2_profile
exit all

exit all

exit all
#*********************************End****************************************
exit all

exit all

exit all

exit all

exit all
#*********************************End****************************************
#***********************Configuring_Router_Interface*************************
address 172.17.191.10/24
bind svi 101
no shutdown
exit all
#*********************************End****************************************
#*************************Configuring_Bridge_Ports***************************

bind svi 40
no shutdown
exit all


bind svi 45
no shutdown
exit all

bind svi 50
no shutdown
exit all

bind svi 51
no shutdown
exit all
#*********************************End****************************************
#*************************Configuring_Management_VLAN************************
configure bridge 1 vlan 4094 tagged-egress 40,45,50,51
exit all
#*********************************End****************************************
#************************Defining_Classifier_Profiles************************
config flows classifier-profile v4094 match-any
match vlan 4094
exit all
configure flows classifier-profile v3000 match-any

match vlan 3000
exit all

match all
exit all

match untagged
exit all
#*********************************End****************************************
#*********************Configuring_Marking_Profile****************************
configure qos marking-profile mark1 classification cos color-aware green-
yellow dei mapping


exit all
#*********************************End****************************************
#*************************Activating_Physical_Ports**************************
pm-enable
no shutdown
exit all

pm-enable
no shutdown
exit all
#*********************************End****************************************
#*********************Configuring_ETX-5_Management_Flows*********************
config flows flow MNG_MA0toSVI50
classifier untagged
egress-port svi 50
vlan-tag push vlan 4094 p-bit fixed 0
pm-enable
no shutdown
exit all
config flows flow SVI50toMNG_MA0

classifier v4094
ingress-port svi {50}
vlan-tag pop vlan
pm-enable
no shutdown
exit all
config flows flow SVI51toSVI101

classifier v4094
ingress-port svi 51
egress-port svi 101
vlan-tag pop vlan
no shutdown
exit all
config flows flow SVI101toSVI51

classifier all
ingress-port svi 101
egress-port svi 51
vlan-tag push vlan 4094
p-bit profile mark1
no shutdown
exit all
#*********************************End****************************************

#********************Configuring_ETX-205A_Management_Flows*******************
configure flows flow 1_13toSAP1_2_40_v4094
classifier v4094
egress-port sap 1/2/40 queue-map-profile QueueMapDefaultProfile" block 0/1
pm-enable
no shutdown
exit all
configure flows flow SAP1_2_40toSVI40_v4094

classifier v4094
egress-port svi 40
pm-enable
no shutdown
exit all
configure flows flow SVI40to1_13

classifier "v4094"
ingress-port svi 40
pm-enable
no shutdown
exit all
#*********************************End****************************************
#*********************Configuring_MiNID_Management_Flows*********************
classifier v4094
pm-enable
no shutdown
exit all

classifier v4094
egress-port svi 45
pm-enable
no shutdown
exit all

classifier v4094
ingress-port svi 45
pm-enable
no shutdown
exit all
#*********************************End****************************************
#*******************Configuring_Tunneling_Flows_for_VLAN_3000****************
configure flows flow 1_14to1_SAP1_2_400_v3000
classifier v3000


pm-enable
no shutdown
exit all
configure flows flow SAP1_2_400toLAG1_v3000

classifier all
ingress-port 1/2/400
egress-port lag 1 queue-map-profile QueueMapDefaultProfile" block 0/1
pm-enable
no shutdown
exit all
configure flows flow LAG1to1_SAP1_1_401_v3000

classifier v3000
ingress-port lag 1
pm-enable
no shutdown
exit all
configure flows SAP1_1_401to1_14_v3000

classifier all
egress-port ethernet 1/14 queue-map-profile QueueMapDefaultProfile" block 0/1
pm-enable
no shutdown
exit all
#*********************************End****************************************
#***************************Adding_Default_Gateway***************************
static-route 0.0.0.0/0
address 172.17.191.1
exit all
#*********************************End****************************************
#***************************Displaying_Flow_Summary**************************
show configure flows summary
Name : MNG_MA0toSVI50
Admin Status : Up
PM : Disable
Service Name :
Test : Off
Classifier : untagged
Ingress Port : MNG ETH main-a/0

Egress Port : SVI 50
OAM CFM Details

---------------------------------------
Type MD MA Entity
---------------------------------------
more..
#*********************************End****************************************
Configuring ETX-203AX (1) Management Flows

Inband access to management entity is provided via a series of concatenated
flows, linking the physical ports, bridge and router. To protect the management
traffic, we use ERP to connect the ETX-5 and ETX-203AX (1) bridges.
 To configure management traffic flows within ETX-203AX (1):

1. Add SVI 1.
2. Add router interface 1, configure IP address for inband management
(172.17.191.11/24) and bind SVI 1 to router interface 1.
3. Add bridge 1 with VLAN 4094.
4. Add bridge ports 1 (ring), 2 (ring) and 3 (management).
5. Define classifier profiles (v4094, all and untagged).
6. Configure two flows:
 From BP 3 to SVI 1 (BP3toSVI1)
 From SVI 1 to BP 3 (SVI1toBP3)
7. Configure queue group profile (workshop_level_2_profile). It is recommended
to create a new queue group profile and not to use the default one. ETX-2
Queue Group Configuration section above details how to create queue group
profiles for ETX-2 devices.
8. Bind the workshop_level_2_profile to Ethernet ports 1 and 2.
9. Continue with Ethernet ring configuration as explained in Configuring
Ethernet Ring Protection below.
Figure 13-19 illustrates flow of the management traffic within ETX-203AX (1)
prior to ERP configuration. Detailed configuration instructions are provided in the
script below.
2
ETH 2
Bridge
3 1
SVI 1
1
Router
ETH 1
Management
ETX-203AX (1)
Figure 13-19. Management Traffic Flow within ETX-203AX (1)

#*****************************Configuring_SVI********************************
configure port svi 1
no shutdown
exit all
#*********************************End****************************************
address 172.17.191.11/24
bind svi 1
no shutdown
exit all
#*********************************End****************************************
configure bridge 1 vlan 4094
exit all
#*********************************End****************************************
configure bridge 1
port 3
no shutdown
exit all
configure bridge 1
port 1
no shutdown
exit all
configure bridge 1
port 2
no shutdown
exit all
#*********************************End****************************************
match vlan 4094
exit all

match all
exit all

match untagged
exit all
#*********************************End****************************************
config flows flow BP3toSVI1
classifier v4094
no policer
ingress-port bridge-port 1 3

egress-port svi 1
vlan-tag pop vlan
no shutdown
exit all
config flows flow SVI1toBP3

classifier all
no policer
ingress-port svi 1
egress-port bridge-port 1 3
no shutdown
exit all
#*********************************End****************************************
configure qos queue-group-profile workshop_level_2_profile
exit all
#*********************************End****************************************
#*****************Binding_Queue_Group_Profile_to_Ethernet_Ports**************
configure port ethernet 1
exit all

exit all
#*********************************End****************************************
Configuring ETX-205A Management Flows

Inband access to management entity is provided via a series of concatenated
flows, linking the physical ports and the router.
 To configure management traffic flows within ETX-205A:

1. Add SVI 1.
to create a new queue group profile and not to use the default one. ETX-2
Queue Group Configuration section above details how to create queue group
profiles for ETX-2 devices.
5. Bind the workshop_level_2_profile to port 1.
 From SVI 1 to port 1 (MNG_OUT_v4094)
 From port 1 to SVI 1 (MNG_IN_v4094)
7. Activate router interface.


Figure 13-20 illustrates flow of the management traffic within ETX-205A. Detailed
SVI 1
1
Router
2
Management
ETX-205A
Figure 13-20. Management Traffic Flow within ETX-205A
#*****************************Configuring_SVI********************************
no shutdown
exit all
#*********************************End****************************************
address 172.17.191.11/24
bind svi 1
exit all
#*********************************End****************************************
match vlan 4094
exit all

match all
exit all

match untagged
exit all
#*********************************End****************************************
exit all
#*********************************End****************************************
exit all

#*********************************End****************************************
configure flows flow MNG_OUT_v4094
classifier all
ingress-port svi 1
egress-port ethernet 1 queue 0 block 0/1
no shutdown
exit all
configure flows flow MNG_IN_v4094

classifier v4094
vlan-tag pop vlan
ingress-port ethernet 1
egress-port svi 1 queue 0
no shutdown
exit all
#*********************************End****************************************
#************************Activating_Router_Interface*************************
no shutdown
exit all
#*********************************End****************************************
address 172.17.191.1
exit all
#*********************************End****************************************
Configuring MiNID for Management

MiNID is prepared to accept management traffic by defining a dedicated
management VLAN (4094) in order to separate management traffic from the user
data.
 To configure MiNID for management:

2. Navigate to the Host IP menu (Configuration > System > Management > Host
IP).
2. Configure the following:
 IP Address IP address of the MiNID device) –172.17.191.13
 Default GW (IP address of the NMS) – 172.17.192.1
 Host VLAN ID (management traffic VLAN) – 4094
 Host VLAN Priority (management traffic priority) – 7.

MiNID
Configuration > System > Management > Host IP
DHCP Client Disable

IP Address 172.17.191.13
Network Mask 255.255.255.0
Default GW 172.17.192.1
Host Vlan Tagged
Host Vlan ID 4094
Host Vlan Priority 7
Figure 13-21. MiNID Host IP Parameters
13.5 Configuring Ethernet Ring Protection

This section explains how to establish a major G.8032v2 ring to protect
management traffic flowing between ETX-5 and ETX-203AX (1).
The configurable scale of Ethernet rings is:
• Up to 64 G.8032 Rings are supported per shelf ( Main rings + sub rings).
• Up to 63 sub rings per ring .
The ring runs between the bridge instances in the devices. The bridge port (BP)
roles are as follows:
• ETX-5 BP 1 – East port, RPL owner
• ETX-5 BP 2 –West port, node
• ETX-203AX (1) BP 1 – West port, neighbor
• ETX-203AX (1) BP 2 – East port, node.
Figure 13-22 illustrates the general ERP layout. See sections below for detailed
description of how to configure ERP instances for ETX-203AX (1) and ETX-5.
13-30 Configuring Ethernet Ring Protection

MNG-ETH
E5-GBE-20 E5-MC-4 VLAN

4094
2 SVI 1 SVI 50
ETH 2 1/1
Bridge RPL 1 50
3 1 Bridge
2 51
SVI 2 SVI 51
SVI 1
1 SVI 101
Router 1
ETH 1 1/11
Router
Management
Management
ETX-203AX (1)
ETX-5
Figure 13-22. ERP Layout
Configuring ERP Instance for ETX-203AX (1)

Figure 13-23 illustrates ERP instance in ETX-203AX (1).
West port,
neighbor 2 ETH 2
Bridge
3 1 MEP 12
East port,
node
SVI 1 MEP 22
1
Router
ETH 1
Management
Figure 13-23. ERP Instance in ETX-203AX (1)
 To configure an ERP instance for ETX-203AX (1):

3. Define an ERP instance with VLAN 777 used for R-APS traffic.
2. Define VLAN 4094 (management traffic) for the ERP, making it present on
both BPs (1 and 2).
By default, R-APS traffic (VLAN 777) goes to queue block 0/1.
As the management traffic (VLAN 4094) is generated internally, it does not
require classification. When being forwarded towards ETX-5, the management
traffic exits via queue block 0/2, using queues defined by the default P-bit to
queue mapping.
In the ingress direction (from ETX-5) via ETH 1 and ETH 2 ports, traffic tagged
with VLAN 4094 is delivered to bridge 1. This is possible because ERP 1 is
defined for VLAN 4094 and includes bridge 1, ETH 1 and ETH 2 ports.
3. Add a classifier profile for VLAN 1503. This VLAN will be used by CCMs to
detect ring failures.
4. Add VLAN 1503 to the ERP.
Configuring Ethernet Ring Protection 13-31

5. Define OAM (CFM) session to create MEPs 12 and 22, and bind them to port
ETH 2 and ETH 1, respectively.
6. Add SF triggers to ERP 1.
Detailed configuration instructions are provided in the script below.
#****************************Adding_ERP_Instance*****************************
timers guard 2000 holdoff 0
bridge 1
east-port 1 ethernet 1
west-port 2 ethernet 2
r-aps vlan 777 vlan-priority 1
mel 1
port-type east node-port
port-type west neighbor
exit all
#*********************************End****************************************
#************************Defining_VLAN_4094_for_ERP_1************************
vlan 4094
queue-block east 0/2 west 0/2
no shutdown
exit all

no shutdown
exit all
#*********************************End****************************************
#*******************Defining_Classifier_Profile_for_VLAN_1503****************
configure flows classifier-profile class1503 match-any
match vlan 1503
exit all
#*********************************End****************************************
vlan 1503
no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_OAM_CFM****************************
configure oam cfm
no name
md-level 4
ccm-interval 3.33ms
name uint 11
classification vlan 1503

mep 12
ccm-initiate
ccm-priority 0
remote-mep 11
bind ethernet 2
queue fixed 0 block 0/1
no shutdown
exit all
configure oam cfm

no name
md-level 4
ccm-interval 3.33ms
name uint 21
mep 22
ccm-initiate
ccm-priority 0
remote-mep 21
bind ethernet 1
no shutdown
exit all
#*********************************End****************************************
#***************************Configuring_SF_Triggers**************************
configure protection erp 1
sf-trigger west mep 1 1 12
sf-trigger east mep 1 2 22
exit all
#*********************************End****************************************
address 172.17.191.1
exit all
#*********************************End****************************************

Configuring ERP Instance for ETX-5

Figure 13-24 illustrates an ERP instance in ETX-5.
MNG-ETH
E5-GBE-20 E5-MC-4 VLAN

4094
SAP 1
SVI 1 SVI 50
1/1
MEP 11 1 50
Bridge
SAG 1
2 51
SVI 2 SVI 51
SAP 1
MEP 21 SVI 101
1
1/11
Router
SAG 2
Management
ERP Path
Flow Path
Management Traffic
Figure 13-24. ERP Instance in ETX-5
 To configure an ERP instance for ETX-5:

 workshop_level_2_profile to be applied to port 1/1 and port 1/11.
default ones. The section ETX-5 Queue Group Configuration above details
how to create queue group profiles for ETX-5.
2. Configure two bridge-type SVIs: 1 and 2.
3. Bind the SVIs to the bridge ports 1 and 2.
4. Define an ERP instance with VLAN 777 used for R-APS traffic.
5. Define ERP members (RPL owner and node).
6. Define a protected VLAN (VLAN 4094) and activate the ERP.
7. Add a classifier profile for R-APS traffic (VLAN 777).
8. Define six flows to carry R-APS traffic from physical ports to bridge ports:
 From port 1/1 to SAP 1/1/1 (Ring_1_1 to SAP1_1_1)
 From SAP 1/1/1 to SVI 1 (Ring_SAP1_1_1 to SVI1)
 From SVI 1 to port 1/1 (Ring_SVI1to1_1)
 From port 1/11 to SAP 1/2/1 (Ring_1_11 to SAP1_2_1)
 From SAP 1/2/1 to SVI 2 (Ring_SAP1_2_1 to SVI2)
 From SVI 2 to port 1/11 (Ring_SVI2 to 1_11)

9. Activate port 1/1 and port 1/11.

10. Define six flows to carry management traffic (VLAN 4094) from physical ports
to bridge ports:
 From port 1/1 to SAP 1/1/1 (1_1 to SAP1_1_1)
 From SAP 1/1/1 to SVI 1 (SAP1_1_1 to SVI1)
 From SVI 1 to port 1/1 (SVI1 to 1_1)
 From port 1/11 to SAP 1/2/1 (1_11 to SAP1_2_1)
 From SAP 1/2/1 to SVI 2 (SAP1_2_1 to SVI2)
 From SVI 2 to port 1/11 (SVI2 to 1_11)
11. Configure VLAN 1503 for use by CCMs to detect ring failures.
 Add VLAN 1503 to the bridge
 Add VLAN 1503 to the ERP
 Define a classifier profile for VLAN 1503.
12. Define six flows to carry OAM traffic from physical ports to bridge ports:
 From port 1/1 to SAP 1/1/1 (RING_OAM_1/1_to_SAP1/1/1)
 From SAP 1/1/1 to SVI 1 ("RING_OAM_SAP1/1/1_to_SVI1)
 From SVI 1 to port 1/1 (RING_OAM_SVI1_to_1/1)
 From port 1/11 to SAP 1/2/1 (RING_OAM_1/11_to_SAP1/2/1)
 From SAP 1/2/1 to SVI 2 (RING_OAM_SAP1/2/1_to_SVI2)
 From SVI 2 to port 1/11 (RING_OAM_SVI2_to_1/11)
13. Configure CoS mapping profile to convert P-bit values to internal CoS to be
used by MEPs.
14. Define OAM (CFM) session to create MEPs 11 and 21, and bind them to port
1/1 and port 1/11, respectively.
15. Add SF triggers to the ERP 1.
16. Detailed configuration instructions are provided in the script below.
#**************Assigning_Queue_Group_Profiles_to_SAGs_and_Ports**************
config port sag 1/1
exit all
config port sag 1/2

exit all

exit all

exit all
#*********************************End****************************************

exit all

exit all
#*********************************End****************************************
#************************Binding_SVIs_to_Bridge_Ports************************
bind svi 1
no shutdown
exit all

bind svi 2
no shutdown
exit all
#*********************************End****************************************
#****************************Adding_ERP_Instance*****************************
bridge 1
east-port 1
west-port 2
r-aps vlan 777 vlan-priority 1 mel 1
exit all
#*********************************End****************************************
#****************************Defining_ERP_Members****************************
port-type east rpl
port-type west node-port
wait 300
timers guard 2000
exit all
#*********************************End****************************************
data-vlan 4094
exit all

no shutdown
exit all
#*********************************End****************************************
#*******************Defining_Classifier_Profile_for_VLAN_777*****************
config flows classifier-profile 777 match-any
match vlan 777
exit all
#*********************************End****************************************

#***********************Configuring_Flows_for_VLAN_777***********************
configure flows flow Ring_1_1toSAP1_1_1
classifier 777
egress-port sap 1/1/1
queue-map-profile QueueMapDefaultProfile block 0/1
pm-enable
no shutdown
exit all
configure flows flow Ring_SAP1_1_1toSVI1

classifier 777
egress-port svi 1
pm-enable
no shutdown
exit all
configure flows flow Ring_SVI1to1_1

classifier 777
ingress-port svi 1
egress-port ethernet 1/1
pm-enable
no shutdown
exit all
configure flows flow Ring_1_11toSAP1_2_1

classifier 777
pm-enable
no shutdown
exit all
configure flows flow Ring_SAP1_2_1toSVI2

classifier 777
egress-port svi 2
pm-enable
no shutdown
exit all
configure flows flow Ring_SVI2to1_2_1

classifier 777
ingress-port svi 2
pm-enable
no shutdown
exit all
#*********************************End****************************************
#***********************Activating_Ports_1/1_and_1/11************************
config slot 1

no shutdown
exit all

no shutdown
exit all

no shutdown
exit all
#*********************************End****************************************
#***********************Configuring_Flows_for_VLAN_4094**********************
configure flows flow 1_1toSAP1_1_1
classifier v4094
pm-enable
no shutdown
exit all
configure flows flow SAP1_1_1toSVI1

classifier v4094
egress-port svi 1
pm-enable
no shutdown
exit all

classifier v4094
ingress-port svi 1
pm-enable
no shutdown
exit all
configure flows flow 1_11toSAP1_2_1

classifier v4094
pm-enable
no shutdown
exit all
configure flows flow SAP1_2_1toSVI2

classifier v4094
egress-port svi 2
pm-enable
no shutdown
exit all


classifier v4094
ingress-port svi 2
pm-enable
no shutdown
exit all
#*********************************End****************************************
#***********************Configuring_VLAN_1503_for_CCMs***********************
config bridge 1
vlan 1503
exit all

data-vlan 1503
exit all

match vlan 1503
exit all
#*********************************End****************************************
#***********************Configuring_Flows_for_VLAN_1503**********************
configure flows flow RING_OAM_1/1_to_SAP1/1/1
classifier "v1503"
pm-enable
no shutdown
exit all
configure flows flow RING_OAM_SAP1/1/1_to_SVI1

classifier v1503
egress-port svi 1
pm-enable
no shutdown
exit all
configure flows flow RING_OAM_SVI1_to_1/1

classifier v1503
ingress-port svi 1
pm-enable
no shutdown
exit all
configure flows flow RING_OAM_1/11_to_SAP1/2/1

classifier v1503


pm-enable
no shutdown
exit all
configure flows flow RING_OAM_SAP1/2/1_to_SVI2

classifier v1503
egress-port svi 2
pm-enable
no shutdown
exit all
configure flows flow RING_OAM_SVI2_to_1/11

classifier v1503
ingress-port svi 2
pm-enable
no shutdown
exit all
#*********************************End****************************************
#**************************Configuring_CoS_Mapping***************************
config qos cos-map-profile cos_map
classification p-bit
map 0 to-cos 7
map 1 to-cos 6
map 2 to-cos 5
map 3 to-cos 4
map 4 to-cos 3
map 5 to-cos 2
map 6 to-cos 1
map 7 to-cos 0
exit all
#*********************************End****************************************
#*****************************Configuring_OAM_CFM****************************
configure oam cfm
md-level 4
ccm-interval 3.33ms
name uint 11
mep 11
bind ethernet 1/1
cos-mapping profile cos_map
flow uni-direction rx RING_OAM_SAP1/1/1_to_SVI1 tx RING_OAM_SVI1_to_1/1
ccm-initiate
ccm-priority 0
remote-mep 12
no shutdown
exit all

configure oam cfm

md-level 4
ccm-interval 3.33ms
name uint 21
mep 21
bind ethernet 1/11
cos-mapping profile cos_map
flow uni-direction rx RING_OAM_SAP1/2/1_to_SVI2 tx RING_OAM_SVI2_to_1/11
ccm-initiate
ccm-priority 0
remote-mep 22
no shutdown
exit all
#*********************************End****************************************
#***************************Configuring_SF_Triggers**************************
sf-trigger east mep 1 1 11
sf-trigger west mep 1 2 21
exit all
#*********************************End****************************************
13.6 Configuring LAG

This section explains how to establish a Link Aggregation Group (LAG) to protect
management traffic, flowing between ETX-5 and ETX-203AX (2).
Figure 13-25 illustrates the general LAG layout. See sections below for a detailed
description of how to configure link aggregation for ETX-203AX (2) and ETX-5.
MNG-ETH
E5-GBE-20 E5-MC-4
ETH 1 1/2 SVI 30
30
Bridge
51
LAG SVI 51
SVI 1
1 SVI 101
Router 1
ETH 2 1/12
Router
Management
Management
ETX-203AX (2)
ETX-5
Figure 13-25. LAG Layout
Configuring LAG 13-41

Configuring LAG for ETX-203AX (2)

Figure 13-25 illustrates LAG in ETX-203AX (2).
 To configure LAG for ETX-203AX (2):

1. Create a LAG port (virtual entity, consisting of two physical ports).
2. Add a L2CP profile to peer (interpret) LACP packets. This profile will be
applied to both physical ports. LACP traffic uses MAC DA 01-80-C2-00-00-02.
3. Assign the L2CP profile to both LAG member ports.
4. Add SVI 1.
7. Configure a queue group profile (profile-LAG). It is recommended to create a
new queue group profile and not to use the default one. The section ETX-2
Queue Group Configuration above details how to create queue group profiles
for ETX-2 devices.
 From SVI 1 to port 1 (MNG_OUT_v4094)
 From port 1 to SVI 1 (MNG_IN_v4094)
9. Activate the router interface.
#******************************Creating_LAG_Port*****************************
configure port lag 1
bind ethernet 1
bind ethernet 2
lacp tx-activity active tx-speed fast
admin-key giga-ethernet
no shutdown
exit all
#*********************************End****************************************
#****************************Adding_L2CP_Profile*****************************
configure port l2cp-profile LACP
mac 0x02 peer
exit all
#*********************************End****************************************
#****************************Assigning_LACP_Profile**************************
l2cp profile LACP
exit all

l2cp profile LACP
exit all
13-42 Configuring LAG

#*********************************End****************************************
#*****************************Configuring_SVI********************************
no shutdown
exit all
#*********************************End****************************************
address 172.17.191.16/24
bind svi 1
no shutdown
exit all
#*********************************End****************************************
match vlan 4094
exit all

match all
exit all

match untagged
exit all
#*********************************End****************************************
configure qos queue-group-profile profile-LAG
exit all
#*********************************End****************************************
queue-group profile profile-LAG
exit all

queue-group profile profile-LAG
exit all
#*********************************End****************************************
configure flows flow MNG_OUT_v4094
classifier all
ingress-port svi 1
no shutdown
exit all
configure flows flow MNG_IN_v4094

classifier v4094
vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
#************************Activating_Router_Interface*************************
no shutdown
exit all
#*********************************End****************************************
address 172.17.191.1
exit all
#*********************************End****************************************
Configuring LAG for ETX-5

Figure 13-26 illustrates LAG in ETX-5.
MNG-ETH
E5-GBE-20 E5-MC-4
CPU
SAP 31
1/2 SVI 30
30
Bridge
SAP 30
51
SAG 1
LAG SVI 51
Cre
auto ated SAP 31 SVI 101
matic
au Crea ally
tom te 1
ati d
1/12 ca
lly Router
SAP 30
SAG 2
Management
ETX-5
LACP Traffic
Management Traffic
Figure 13-26. LAG in ETX-5
 To configure LAG for ETX-5:

1. Activate Ethernet ports 1/2 and 1/12.
2. Create a LAG port.
 workshop_level_2_profile to be applied to port 1/2, port 1/12 and LAG 1.

default ones. The section ETX-5 Queue Group Configuration above details
how to create queue group profiles for ETX-5.
4. Add bridge-type SVI 30.
5. Add bridge 1, bridge port 30 (BP 30) and bind it to SVI 30.
6. Define management VLAN 4094 and tagged egress ports (1, 2, 30, 50, 51).
Note Any bridge ports that have already been associated with this VLAN must be
repeated in the command.
7. Add an L2CP profile to peer (interpret) LACP packets. This profile will be
applied to both physical ports. LACP traffic uses MAC DA 01-80-C2-00-00-02.
8. Define two flows for LACP traffic:
 From LAG 1 to SAP 1/1/31 (LACP_LAG1toSAP1_1_31).
Drop action applied to the flow ensures that non-LACP packets are
dropped and prevented from being delivered to the CPU.
 Enable port A/3 to serve as an egress port for LACP traffic.
You can indicate any main card port as an egress port of the flow. This is
required for technical reasons and does not influence the port in any
way, as LACP packets are forwarded to the CPU.
 From SAP 1/1/31 to port A/3 (LACP_SAP1_1_31toMA3).
 Verify that the SAP serving the second port member in the LAG is not in
use (has flows attached to it). This SAP (in this example SAP 1/2/31) is
used by the LAG-to-SAP-1/2/31 flow which is created automatically.
9. Define three flows for management traffic:
 From LAG 1 to SAP 1/1/30 (LAG1 to SAP1_1_30_v4094)
 From SAP 1/1/30 to SVI 30 (SAP1_1_30 to SVI30_v4094)
 From SVI 30 to LAG 1 (SVI30 to LAG1)
 Verify that SAP serving the second port member in the LAG is not in use
(has flows attached to it). This SAP (in this example SAP 1/2/30) is used
by the LAG-to-SAP-1/2/30 flow, which is created automatically.
#*************************Activating_Ethernet_Ports**************************
pm-enable
no shutdown
exit all

pm-enable
no shutdown
#*********************************End****************************************
#******************************Adding_LAG_Port*****************************
bind ethernet 1/2

bind ethernet 1/12

lacp tx-activity active tx-speed fast
no shutdown
exit all
#*********************************End****************************************
#**********Assigning_Queue_Group_Profiles_to_SAGs_Ports_and_LAG**************
config port sag 1/1
exit all
config port sag 1/2

exit all

exit all

exit all

no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_SVI********************************
configure port svi 30 bridge
no shutdown
exit all
#*********************************End****************************************
bind svi 30
no shutdown
exit all
#*********************************End****************************************
configure bridge 1 vlan 4094 tagged-egress 1,2,30,50,51
exit all
#*********************************End****************************************
#****************************Adding_L2CP_Profile*****************************
configure port l2cp-profile LACP
mac 01-80-c2-00-00-02 peer
exit all
#*********************************End****************************************
#**********************Configuring_Flows_for_LACP_Traffic********************
configure flows flow LACP_LAG1toSAP1_1_31

classifier untagged
ingress-port lag 1
l2cp profile LACP
drop
pm-enable
no shutdown
exit all

pm-enable
no shutdown
configure flows flow LACP_SAP1_1_31toMA3

classifier all
0/1
pm-enable
no shutdown
exit all
#configure flows flow LACP_LAG1toSAP1_2_31

#classifier untagged
#l2cp profile LACP
#ingress-port lag 1
#egress-port sap 1/2/31 queue-map-profile QueueMapDefaultProfile block 0/1
#no shutdown
#exit all
#*********************************End****************************************
#******************Configuring_Flows_for_Management_Traffic******************
configure flows flow LAG1toSAP1_1_30_v4094
classifier v4094
ingress-port lag 1
pm-enable
no shutdown
exit all

classifier v4094
egress-port svi 30
pm-enable
no shutdown
exit all
configure flows flow SVI30toLAG1

classifier v4094
ingress-port svi 30
pm-enable

no shutdown
exit all
#configure flows flow LACP_LAG1toSAP1_2_31

#classifier untagged
#l2cp profile LACP
#ingress-port lag 1
#egress-port sap 1/2/31 queue-map-profile QueueMapDefaultProfile block 0/1
#no shutdown
#exit all
#*********************************End****************************************
13.7 Configuring E-Line Service

This section describes how to configure an E-Line service running between
ETX-203AX (1) and ETX-205A via ETX-5. The service is based on untagged user
traffic, which will be marked by S-VLAN 600.
In the ring part of the setup (ETX-203AX (1) – ETX-5), the E-Line service is
implemented, using bridging and ERP protection.
In the linear part of the setup (ETX-205A – ETX-5), the E-Line service is
implemented, using direct cross-connect.
E5-GBE-20 E5-MC-4
SAP 1
4 2 ETH 2 1/1 SVI 1
ETH 3
Untagged
user traffic Bridge SAP 1
3 1 Bridge
SAP
2 41
SAG 1
SVI 2 SVI 41
SVI 1
ETH 1 1/11
1 SAP 1
Router
SAP
1/13
SAP 41
Management
SAG 2
ETX-203AX (1)
ETX-5
3 1
Untagged
user traffic
SVI 1
1
Router
2
Management
ETX-205A
Figure 13-27. E-Line Service Overview
13-48 Configuring E-Line Service

Configuring E-Line for ETX-203AX (1)

 To configure E-Line service within ETX-203AX (1):
1. Activate bridge port 4 with VLAN 600 on bridge 1.
2. Configure a queue group profile (workshop_level_2_profile). It is
recommended to create a new queue group profile and not to use the default
one. ETX-2 Queue Group Configuration section above details how to create
queue group profiles for ETX-2 devices.
3. Bind the workshop_level_2_profile to Ethernet port 3.
4. Define classifier profile v600_DATA for traffic tagged with VLAN 600.
5. Configure a bi-directional data flow from Ethernet port 3 to BP 4
(ETH3toBP4), pushing VLAN 600 and popping it in the reverse direction. The
egress flow from BP 4 to Ethernet port 3 is created automatically.
6. Add VLAN 600 to the ERP 1.
#*************************Activating_Bridge_Port_4***************************
configure bridge 1
port 4
no shutdown
exit
vlan 600
exit all
#*********************************End****************************************
exit all
#*********************************End****************************************
#****************Binding_Queue_Group_Profile_to_Ethernet_Port_3**************
exit all
#*********************************End****************************************
#******************Defining_Classifier_Profile_for_VLAN_600******************
configure flows classifier-profile v600_DATA match-any
match vlan 600
exit all
#*********************************End****************************************
#***********************Configuring_Bidirectional_Flow***********************
config flows flow ETH3toBP4
classifier untagged
egress-port bridge-port 1 4
reverse-direction block 0/1
no shutdown
exit all
Configuring E-Line Service 13-49

#*********************************End****************************************
vlan 600
no shutdown
exit
no shutdown
exit all
#*********************************End****************************************
Configuring E-Line for ETX-5

Figure 13-28 illustrates E-Line flows in ETX-5.
E5-GBE-20 E5-MC-4
SAP 1
1/1 SVI 1
SAP 1
Bridge
SAP
2 41
SAG 1
SVI 2 SVI 41
1/11
SAP 1
SAP
1/13
SAP 41
SAG 2
ETX-5
Figure 13-28. E-Line Flows in ETX-5
 To configure E-Line service within ETX-5:

2. Add bridge-type SVI 41 for connection to port 1/13.
2. Add bridge port 41, bind it to SVI 41 and define tagged egress ports for VLAN
600.
3. Add VLAN 600 to the ERP 1.
4. Define classifier profile v600 for VLAN 600.
5. Bind the workshop_level_2_profile to port 1/13.
 Six flows for forwarding VLAN 600 traffic from port 1/1 to port 1/11 and
vice versa:
 From SVI 1 to port 1/1 (SVI1to1_1_v600)


 Three flows for forwarding VLAN 600 traffic to and from port 1/13:
#*********************************Adding_SVI_41******************************
configure port svi 41 bridge
exit all
#*********************************End****************************************
#**************************Configuring_SVI_41********************************
configure bridge 1
port 41
bind svi 41
no shutdown
exit
vlan 600
tagged-egress 1..2,41
exit
exit all
#*********************************End****************************************
configure protection erp 1
data-vlan 600
exit all
#*********************************End****************************************
#******************Defining_Classifier_Profile_for_VLAN_600******************
match vlan 600
exit all
#*********************************End****************************************
#*************Binding_Queue_Group_Profile_to_Ethernet_Port_1/13**************
queue-group profile Workshop_level_2_profile
exit all
#*********************************End****************************************
#*****************************Configuring_Flows******************************
classifier v600
pm-enable
no shutdown
exit all

classifier v600
egress-port svi 1
pm-enable
no shutdown

exit all
configure flows flow SVI1to1_1_v600

classifier v600
ingress-port svi 1
pm-enable
no shutdown
exit all

classifier v600
ingress-port svi 2
pm-enable
no shutdown
exit all

classifier v600
pm-enable
no shutdown
exit all

classifier v600
egress-port svi 2
pm-enable
no shutdown
exit all

classifier v600
ingress-port svi 41
pm-enable
no shutdown
exit all

classifier v600
pm-enable
no shutdown
exit all

classifier v600
egress-port svi 41
pm-enable

no shutdown
exit all
#*********************************End****************************************
Configuring E-Line for ETX-205A

 To configure E-Line service within ETX-205A:
1. Define two classifier profiles:
 untagged for untagged traffic
 v600 for traffic tagged with VLAN 600
to create a new queue group profile and not to use the default one. The
section ETX-2 Queue Group Configuration above details how to create queue
group profiles for ETX-2 devices.
3. Bind the workshop_level_2_profile to Ethernet port 3.
 From port 3 to port 1 (ETH3_to_ETH1_v600)
 From port 1 to port 2 (ETH1_to_ETH3_v600)
#*************************Defining_Classifier_Profiles***********************
configure flows classifier-profile untagged match-any
match untagged
exit all
configure flows classifier-profile v600

match-any
match vlan 600
#*********************************End****************************************
exit all
#*********************************End****************************************
#****************Binding_Queue_Group_Profile_to_Ethernet_Port_3**************
exit all
#*********************************End****************************************
#*******************************Configuring_Flows****************************
configure flows flow ETH3_to_ETH1_v600
classifier untagged
vlan-tag push vlan 600
p-bit fixed 0
egress-port ethernet 1
queue 0 block 0/2
no shutdown

exit all
configure flows flow ETH1_to_ETH3_v600

classifier v600
vlan-tag pop vlan
egress-port ethernet 3
queue 0 block 0/2
no shutdown
exit all
#*********************************End****************************************
Checking E-Line Connectivity

E-Line configuration must be verified by checking its end-to-end connectivity.
 To check E-Line connectivity:

• Run untagged traffic from ETX-204A traffic generator and verify the end-to-
end connectivity.
13.8 Configuring a Pseudowire Service

This section describes how to configure a typical pseudowire service, which is
used to deliver unframed E1 stream over Ethernet (MEF 8) infrastructure.
MNG-ETH
E5-cTDM-4 E5-MC-4
3/1
STM-1 E1
DS1 XC PW 1
SVI 70
E1-1 1
ETH 1 50
E1 ETH
PW 1 SVI 2
Bridge
2 51
E5-GBE-20
SVI 1
1
SAP 70
Router 1
SAP Router
1/13
Management SAP
Management
SAG 2
ETX-205A
ETX-5
Figure 13-29. Pseudowire Service
Configuring Pseudowire Service for ETX-205A

 To configure pseudowire service within ETX-205A:
1. Configure E1 port 1 for unframed operation with Tx clock recovered from PW
stream.
13-54 Configuring a Pseudowire Service

2. Configure PW peer (MAC address of the ETX-5 PW host). Use the show
configure port sdh-sonet 3/1 status command on ETX-5 to identify the MAC
address.
3. Define SVI 2.
4. Configure a pseudowire connection (pw 1).
5. Configure TDM cross-connect (assign E1 1 to pw 1).
6. Define a classifier profile v555 for traffic tagged with VLAN 555.
 From SVI 2 to port 1 (E1_SVI2toETH1)
 From port 1 to SVI 2 (E1_ETH1toSVI2)
#*****************************Configuring_E1_Port_1**************************
config port e1 1
no shutdown
line-type unframed
tx-clock-source pw 1
pm-enable
exit all
#*********************************End****************************************
#*****************************Configuring_PW_Peer****************************
config peer 1 mac 00-20-D2-F5-8F-30
exit all
#*********************************End****************************************
#********************************Adding_SVI_2********************************
config port svi 2
no shutdown
exit all
#*********************************End****************************************
#**********************Configuring_Pseudowire_Connection_1*******************
config pw pw 1 type e1satop psn ethernet
peer 1
label in 11 out 22
tdm-payload size 192
pm-enable
egress-port svi 2
no shutdown
exit all
#*********************************End****************************************
#************************Configuring_TDM_Cross_Connect***********************
config cross-connect pw-tdm pw 1 e1 1
exit all
#*********************************End****************************************
#*************************Defining_Classifier_Profile************************
match vlan 555
Configuring a Pseudowire Service 13-55

exit all
#*********************************End****************************************
configure flows flow E1_SVI2toETH1
classifier all
ingress-port svi 2
no shutdown
exit all
config flows flow E1_ETH1toSVI2

classifier v555
vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
Configuring Pseudowire Service for ETX-5

 To configure pseudowire service within ETX-5:
1. Configure the Tx clock source for port 3/1 on the E5-cTDM-4 card.
2. Activate the E1 stream in the STM-1 stream
3. Configure the internal E1 interface.
4. Configure PW peer (MAC address of ETX-205A). Use the show configure
system device-information command on ETX-205A to identify its MAC
address.
5. Add a PW-type SVI (SVI 70).
6. Configure a pseudowire connection (pw 1).
7. Configure a TDM cross-connect (assign E1 3/1/49 to pw 1).
8. Assign the workshop_level_2_profile queue group profile to port 1/13 on
E5-GBE-20 card.
9. Define a classifier profile v555 for traffic tagged with VLAN 555.
10. Configure three flows:
 From SVI 70 to port 1/13 (SVI_70_to_ETH_1/13)
 From port 1/13 to SAP 1/2/70 (ETH_1/13_to_SAP_1/2/70)
 From SAP 1/2/70 to SVI 70 (SAP_1/2/70_to_SVI_70)
11. Activate port 3/1.
12. Activate slot 3.
#********************Configuring_Tx_Clock_Source_for_Port_3/1****************
config port sdh-sonet 3/1

exit all
#*********************************End****************************************
#**************************Activating_E1_in_STM-1****************************
configure port sdh-sonet 3/1 aug 1 tug 3 2 vc 12 6 1
no shutdown
exit all
#*********************************End****************************************
#**************************Cinfiguring_Internal_E1***************************
config port e1 3/1/49
line-type unframed
pm-enable
no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_PW_Peer****************************
config peer 1 mac 00-20-D2-51-15-9A
exit all
#*********************************End****************************************
#********************************Adding_SVI_70*******************************
config port svi 70 pw
no shutdown
exit all
#*********************************End****************************************
#**********************Configuring_Pseudowire_Connection_1*******************
config pwe pw 1 type e1satop psn ethernet
label in 22 out 11
peer 1
egress-port svi 70
tdm-payload size 192
pm-enable
jitter buffer 8000
no shutdown
exit all
#*********************************End****************************************
#************************Configuring_TDM_Cross_Connect***********************
config cross-connect pw-tdm pw 1 e1 3/1/49
exit all
#*********************************End****************************************
#*************Binding_Queue_Group_Profile_to_Ethernet_Port_1/13**************
exit all
#*********************************End****************************************
#*************************Defining_Classifier_Profile************************
Configuring a Pseudowire Service 13-57

match vlan 555

exit all
#*********************************End****************************************
config flows flow SVI_70_to_ETH_1/13
classifier all
ingress-port svi 70
pm-enable
vlan-tag push vlan555 p-bit profile mark1
no shutdown
exit all
config flows flow ETH_1/13_to_SAP_1/2/70

classifier v555
pm-enable
no shutdown
exit all
config flows flow SAP_1/2/70_to_SVI_70

classifier all
egress-port svi 70
pm-enable
vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
#****************************Activating_Port_3/1*****************************
config port sdh-sonet 3/1
no shutdown
exit all
#*********************************End****************************************
#****************************Activating_Slot_3*******************************
config slot 3
no shutdown
exit all
#*********************************End****************************************
Checking Pseudowire Connectivity

Pseudowire service configuration must be verified by checking its end-to-end
connectivity.
 To check pseudowire connectivity:

• Run an unframed E1 stream from the tester and verify the end-to-end
connectivity.

13.9 Configuring OAM (CFM)

This section describes how to configure an OAM (CFM) service for fault
monitoring a flow based on VLAN 3000. The flow runs between the LAG
established in ETX-203AX (2) and a MiNID installed in ETX-1.
For ETX-2 devices, OAM measurements are activated only on existing flows. For
this purpose we will create a flow based on VLAN 200 (C-tag) to which the OAM
VLAN tag (S-tag 300) will be added.
Instructions for creating flows between LAG and ETX-5 port 1/14 are given in
Configuring ETX-5 Management Flows.
MiNID
ETH 3
ETX-1
E5-GBE-20 E5-MC-4
1/14
ETH 1 1/2
VLAN 300
LAG
ETH 3
ETH 2 1/12
ETX-203AX (2)
ETX-5
Figure 13-30. OAM (CFM)
Configuring OAM (CFM ) for ETX-203AX (2)

 To configure an OAM service within ETX-203AX (2):
1. Define classifier profiles v200 and v3000.
2. Define two flows:
 From port 3 to LAG (ETH3toLAG1_v200)
 From LAG to port 3 (LAG1toETH3_v3000)
3. Configure and activate OAM CFM.
Configuring OAM (CFM) 13-59

#***********************Defining_Classifier_Profiles*************************
match vlan 200

match vlan 3000
#*********************************End****************************************
configure flows flow ETH3toLAG1_v200
classifier v200
vlan-tag push vlan3000 p-bit fixed 4
configure flows flow LAG1toETH3_v3000

classifier v3000
vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
#**************************Configuring_OAM_CFM*******************************
configure oam cfm
no name
md-level 6
name string Workshop_MA
ccm-interval 100
mep 2
bind ethernet1
ccm-priority 4
remote-mep1
client-md-level 7
no shutdown
service 1
lmm-interval 100ms
dmm-interval 100ms
dest-ne 1
remote mep-id 1
loss single-ended
lmm-synthetic
exit
no shutdown
exit
exit
#*********************************End****************************************
13-60 Configuring OAM (CFM)

Configuring OAM (CFM) for MiNID

MiNID is prepared to accept OAM traffic by defining a relevant MD, MA, MEP and
activating a PM service.
 To configure OAM (CFM) for MiNID:

1. Navigate to the CFM menu (Configuration > OAM > CFM).
MiNID
Configuration > OAM > CFM
MA Name MD Level VLAN ID

MA-1 3 2000
New MA Remove MA Config MA
Figure 13-31. CFM Menu
2. Click New MA to add a new maintenance association.

The New MA menu is displayed.
3. Configure the following MA parameters:
 MD Level – 6
 MA Name – Workshop_MA
 MA Format – Character String
 VLAN ID – 3000
 Priority – 2
 Drop Eligible – False
 CCM Interval – 100ms
4. Save the changes.
The new MA is added to the CFM Menu.
MiNID
Configuration > OAM > CFM
MA Name MD Level VLAN ID

MA-1 3 2000
Workshop_MA
New MA Remove MA Config MA
Figure 13-32. CFM Menu, Workshop_MA is Added

5. In the CFM menu, select Workshop_MA and click Config MA to configure the
new maintenance association.
The Config MA menu is displayed.
6. In the Config MA menu, click Create MEP to add a new maintenance endpoint.
The New MEP menu is displayed.
7. In the New MEP menu, configure the following parameters:
 MEP Enable – Disable
 MEP ID – 1
 Remote MEP ID – 2
 Ingress Port – SFP
 CCM Enable –Disable
 CCM Transmission Mode – Multicast
 Client MD Level – 7
 AIS Enable – Disable
8. Save the changes.
The Config MA menu is displayed.
Previous Menu Refresh
Configuration > OAM > CFM > Config MA

Update MA Parameters
Create MEP
Create MIP
MEP (ID: 1) Remove MEP Config MEP
Figure 13-33. Config MA Menu, MEP 1 is Added
9. In the Config MA menu, click Config MEP.

The Config MEP menu is displayed.
10. In the Config MEP menu, click Update MEP Params.
The Update MEP menu is displayed.
11. In the Update MEP menu, set MEP Enable to Enable and save the change.
The Config MEP menu is displayed.
12. In the Config MEP menu, click Add PM Service to add and configure a
performance monitoring service.
The PM Service menu is displayed.
13. In the PM Service menu, configure the following parameters:
 Service Enable – Enable
 Service Priority – 0
13-62 Configuring OAM (CFM)

 Loss Measurement Service – Proprietary

 Delay Measurement Service – Enable
 Delay Threshold – 1
 Delay Var Threshold – 1
 Service Interval – 100 ms
14. Save the changes to finish OAM CFM configuration for MiNID.
Displaying Traffic Statistics

OAM statistics for the flow are displayed via ETX-203AX (2). Before displaying
OAM statistics, it is recommended to clear the PM counters for MEP 2.
 To clear the PM counters:

• Enter:
configure oam cfm
mep 2
service 1
clear statistics-running
exit all
 To display OAM statistics:

• Enter:
configure oam cfm
mep 2
service 1
show statistics-running
ETX-203AX-2>config>oam>cfm>md(1)>ma(1)>mep(2)>service(1)# show statistics
running
Running Counters
-----------------------------------------------------------------------------
Far End TX Frames : 7743033
Far End RX Frames : 6311365
Far End Lost Frames : 0
Near End TX Frames : 6325987

Near End RX Frames : 6311631
Near End Lost Frames : 0
Current Delay (uSec) : 0.001 mSec

Current Delay Variation (uSec) : 0.000 mSec
Frames Above Delay Variation Threshold : 0

Loss and Delay Measurements Messages

-----------------------------------------------------------------------------
Transmitted
LMMs : 7679413
DMMs : 7679413
Received
LMRs : 6247747
DMRs : 6247742
13.10 Testing the Application
Checking E-line Connectivity

In order to check the E-Line service on the Ethernet ring and the LAG protection,
and in order tocreate a pseudowire connection, verify the following:
Eline service on ERP -ETX-5 port 1/1,1/11 against ETX-203AX(1)

• Only VLAN 1503 packets pass between CPEs
• Traffic passes from end to end between CPEs
• MNG traffic VLAN 4094 packets manage the ETX-5
Eline service on LAG -ETX-5 port 1/2,1/12 against ETX-203AX(2)

Eline serviceon-ETX-5 port 1/14 against ETX-1-Minid

Pseudowire connection ETX-5 port 1/13 against ETX-205A

• TDM traffic pass between CPEs
13-64 Testing the Application

Checking Port/Flow Statistics

To check the statistics on port 1/1:
1. Connect ETX-5, and view user port 1/1 statistics.
2. Verify that counters are as expected according to the generated traffic
rate and type.
The following shows an example of the statistics:
Testing the Application 13-65

13-66 Testing the Application

Appendix A
Connection Data
A.1 CONTROL DCE Connector

The CONTROL DCE connector is a 9-pin D-type female connector with RS-232
asynchronous DCE interface, intended for direct connection to a supervision
terminal. The connector is wired in accordance with Table A-1.
Table A-1. CONTROL DCE Connector Wiring
Pin Designation Function
1, 4, 6, 7, 8, 9 – Not connected
2 Tx + Transmit
3 Rx – Receive
A.2 MNG ETH Connector

Each ETX-5 MNG ETH port has a 10/100BASE-TX Ethernet station interface
terminated in an RJ-45 connector. The port supports the MDI/MDIX crossover
function, and therefore can be connected by any type of cable (straight or
crossed) to any type of 10/100BASE-TX Ethernet port. The port also corrects for
polarity reversal in the 10BASE-T mode.
Connector pin functions for the MDI state are listed in Table A-2. In the MDIX
state, the receive and transmit pairs are interchanged.
Table A-2. MNG ETH Interface Connector, Pin Functions
1 TxD+ Transmit data output, + wire
2 TxD– Transmit data output, – wire
3 RxD+ Receive data input, + wire
4, 5 – Not connected
6 RxD– Receive data input, – wire
ETX-5 MNG ETH Connector A-1

Appendix A Connection Data Installation and Operation Manual
A.3 Gigabit Ethernet Connector

The Gigabit Ethernet connectors on the E5-GBE-20 card have 10/100/1000BASE-T
Ethernet station interface terminated in an RJ-45 connector. Connector pin
functions are listed in Table A-3.
Table A-3. Gigabit Ethernet Interface Connector, Pin Functions
Pin Signal Function
1 BI_DA+ Bi-directional pair +A
2 BI_DA- Bi-directional pair -A
3 BI_DB+ Bi-directional pair +B
4 BI_DC+ Bi-directional pair +C
5 BI_DC- Bi-directional pair -C
6 BI_DB- Bi-directional pair -B
7 BI_DD+ Bi-directional pair +D
8 BI_DD- Bi-directional pair -D
A.4 EXT CLK Connector

The balanced external clock interface on the E5-MC-4 and E5-MC-SFP-P-4 cards
terminates in an RJ-45 connector, wired in accordance with Table A-4.
Table A-4. EXT CLK Interface Connector, Pin Functions
1 RRING Receive data input
2 RTIP Receive data input
4 TRING Transmit data output
5 TTIP Transmit data output
A.5 TOD Connector

The RS-422 GPS-based ToD clock interface on the E5-MC-4 and E5-MC-SFP-P-4
cards terminates in an RJ-45 connector, wired in accordance with Table A-5.
A-2 TOD Connector ETX-5

Installation and Operation Manual Appendix A Connection Data
Table A-5. TOD Interface Connector, Pin Functions
1 TOD Rx – Receive data input, – wire
2 TOD Rx + Receive data input, + wire
3 1 pps Tx/Rx – Transmit/receive 1 pps, – wire
6 1 pps Tx/RX+ Transmit/receive 1 pps, + wire
4, 5 GND GND
7 TOD Tx/Rx – Transmit/receive TOD, – wire
8 TOD Tx/Rx + Transmit/receive TOD, + wire
A.6 ALARM Connector

The ALARM connector is a 15-pin D-type female connector which provides
connections to the following functions:
• Critical, major and minor alarm relay contacts
• +12V auxiliary voltage output
• External alarm sense input
Connector pin functions are listed in Table A-6.
Caution To prevent damage to alarm relay contacts, the maximum current that can flow
through the contacts must be limited by external means. (The maximum current
through closed contacts is 1A; load switching capacity is 60W). The maximum
voltage across the open contacts is 60 VDC/30 VAC.
Table A-6. ALARM Connector, Pin Functions
Pin Function
1 Minor Alarm Normally Open
2 Minor Alarm Normally Close
3 GND
4 Major Alarm Normally Open
5 Major Alarm Normally Close
6 8–15V output
7 Critical Alarm Normally Open
8 Critical Alarm Normally Close
9 Minor Alarm common
10 Input Alarm 0, RS-232 level
ETX-5 ALARM Connector A-3

Appendix A Connection Data Installation and Operation Manual
Pin Function
12 Major Alarm common
15 Critical Alarm common
A-4 ALARM Connector ETX-5

Appendix B
Test Plan
This appendix describes basic verification tests for ETX-5. The aim is to perform a
series of short tests that check the following:
• Basic functionality
• TDM APS
• LAG
• ERP
• ERP OAM
• Dual homing
• Y.1564 testing
• Chassis reboot
• Software upgrade.
Note All tests should pass if the following procedures are performed precisely.
B.1 Required Equipment

Table B-1 lists devices required for conducting the tests.
Table B-1. Required Equipment
Device Quantity
ETX-5 chassis with fan units 4

E5-MC-4 cards 5
E5-GBE-20 card 1
E5-10GBE-2 card 1
E5-cTDM-4 or E5-cTDM-STM4 cards 2
Spirent Test Center (STC) with GbE/10GbE interfaces 1
Egate-100 2
ETX-205A 2
MiNID 1
FireBerd tester 1
Ethernet switch 1
RADview management station 1
ETX-5 Required Equipment B-1

Appendix B Test Plan Installation and Operation Manual
B.2 Preparing Test Layout

Figure B-1 illustrates the test layout.
ETX-5 (2)
172.18.219.128
RIF 30.30.30.20
1588 Slave, 40.40.40.20
E5-MC-4
A/1 Down MEP, East, Neighbor, MD1, MA2, MEP2, UINT2
A/2 Down MEP, West, Node, MD1, MA4, MEP2, UINT4
ETX-5 (1) A/3 STC traffic input, VLAN 600
172.18.219.179 A/4 STC traffic input, VLAN 800
RIF 30.30.30.10
1588 Master 1, 10.10.10.10
1588 Master 2, 20.20.20.10 ETX-5 (3)
Major Ring (2) 172.18.219.129
E5-MC-4
G.8032v2
EXT CLK System Clock (E1 2.048 MHz) R-APS on VLAN 777 RIF 30.30.30.30
A/1 Down MEP, East, RPL Owner, MD1, MA2, MEP1, UINT2 1588 Slave, 50.50.50.30
Ext. Clk. ST1
A/2 untagged STC traffic input, push VLAN 1600
Dual
Homing A/3 STC traffic input, VLAN 1111 E5-MC-4
A/1 Down MEP, East, Node, MD1, MA4, MEP1, UINT4
E5-MC-4
B/1 Down MEP, West, Node, MD1, MA3, MEP1, UINT3
A/3 STC traffic input VLAN 50, Up MEP, MD2, MA1, MEP2, UINT1
B/3 Down MEP, East, RPL Owner, MD1, MA6, MEP1, UINT4
B/4 STC traffic input, VLAN 1111 A/4 Down MEP, East, Node, MD1, MA5, MEP1, UINT5
E5-GBE-20 E5-10GBE-2
1/1 STC traffic input VLAN 500, Up MEP, MD2, MA1, MEP1, UINT1 1/1 STC traffic input, VLAN 800
1/2 Source-IP classification, STC traffic input, VLAN 600 1/2 E-line service traffic input, VLAN 700
Sub-Ring (1)
1/3 STC traffic input, VLAN 1200 G.8032v2 E5-cTDM-4
1/4 untagged STC traffic input R-APS on VLAN 888
ETX-205A (1) Net 2 3/1 TDM loopback, adaptive clock
1/7 management traffic input, RADview 3/2 TDM loopback, adaptive clock
1/8 Ethertype 88A8, E-line service traffic input, VLAN 900
User 3
Net 1 1/9 STC traffic input, VLAN 4000, P-bit 0-7
LAG,
VLAN 1600 1/14 untagged STC traffic input
1/15 STC traffic input, VLAN 1500, 2500
ETX-205A (2) 1/18 Ethertype 88A8, E-line service traffic input, VLAN 900
ETX-5 (4)
1/19 Y.1564 test, STC traffic input, VLAN 4000, P-bit 0-7 172.18.219.239
Net 2
1/20 E-line service traffic input, VLAN 900 E5-MC-4
A/2 STC traffic input, VLAN 1200
E5-cTDM-4
OC-3/84 x T1 A/3 Down MEP, East, Neighbor, MD1, MA6, MEP2, UINT4
3/1 TDM traffic input (BERT)
3/2 TDM traffic input (BERT)
2 x Egate-100
APS
Figure B-1. Test Layout
ETX-5 Preparing Test Layout B-2

Connecting the Test Layout
Table B-2, Table B-3, Table B-4, Table B-5 detail port connectivity for the test
application.
Table B-2. ETX-5 (1) Port Connectivity
Port Number Cable Device Name Port Number
E5-MC-4 EXT CLK E1 FireBerd
E5-MC-4 A/1 Cat.5 Ethernet ETX-5 (2) E5-MC-4 A/1
E5-MC-4 A/2 Cat.5 Ethernet STC
E5-MC-4 B/1 Cat.5 Ethernet ETX-5 (3) E5-MC-4 A/2
E5-MC-4 B/3 Cat.5 Ethernet ETX-5 (4) E5-MC-4 A/3
E5-MC-4 B/4 Cat.5 Ethernet STC
E5-GBE-20 1/1 Cat.5 Ethernet STC
E5-GBE-20 1/4 Cat.5 Ethernet ETX-205A (1) NET 2
E5-GBE-20 1/7 Cat.5 Ethernet NMS
E5-cTDM-4 3/1 Fiber optic with LC Egate-100 (1) STM-1/OC3 port 1

connectors
E5-cTDM-4 3/2 Fiber optic with LC Egate-100 (2) STM-1/OC3 port 1

connectors
ETX-5 Preparing Test Layout B-3

E5-MC-4 A/2 Cat.5 Ethernet ETX-5 (1) E5-MC-4 B/1
E5-10GBE-2 1/1 Cat.5 Ethernet STC
E5-10GBE-2 1/2 Cat.5 Ethernet STC
E5-cTDM-4 3/1 SFP loopback plug – –
E5-cTDM-4 3/2 SFP loopback plug – –
E5-MC-4 A/3 Cat.5 Ethernet ETX-5 (1) E5-MC-4 B/3
Configuring Devices
This section explains how to configure test equipment and RAD devices.
Configuring Spirent TestCenter

Spirent TestCenter is used for traffic generation and analysis. Below is the script
used for the TestCenter configuration.
Configuring FireBerd
FireBerd is used for supplying timing signal to ETX-5 (1). Configure it to T1
unframed mode, with Gen CLK = Synth.
Configuring ETX-5 (1)

ETX-5 (1) is a central unit in the test application. It accepts and distributes timing
signals, includes RPL owners for major and sub-rings, provides connection to the
NMS etc. Below is the script used for the ETX-5 (1) configuration.

ETX-5 (2) hosts East neighbor and West node of the main ring and accepts STC
traffic input. Below is the script used for the ETX-5 (2) configuration.
B-4 Preparing Test Layout ETX-5

Installation and Operation Manual Appendix B Test Plan

ETX-5 (3) hosts East and West nodes of the main and sub-rings, accepts STC
traffic input and loops TDM traffic. Below is the script used for the ETX-5 (3)
configuration.

ETX-5 (2) hosts East neighbor and West node of the sub-ring and accepts STC
traffic input. Below is the script used for the ETX-5 (4) configuration.
Configuring ETX-205A (1)

ETX-205A (1) is used for creating a link aggregation group (LAG) with ETX-5 (1)
ports 1/4 and 1/14. Below is the script used for the ETX-205A (1) configuration.
Configuring ETX-205A (2)

ETX-205A (2) is used for testing Y.1564 functionality via ETX-5 (1) port 1/19.
Below is the script used for the ETX-205A (1) configuration.
Configuring Egate-100s
Egate-100 units are used for supplying framed TDM T1 traffic to E5-cTDM-4 c
card. Configure both Egate-100 units to SONET frame type, internal transmit
clock, T1 ESF mode, and allocate timeslots 1–24.
B.3 Testing Basic Functionality

The objective of the test is to verify the overall success of the setup
configuration.
Test Duration
1 hour
Test Procedure
Table B-6 details procedure of the basic functionality test.
Table B-6. Basic Functionality Test Procedure
# Action Expected Result Result
1 Verify major and sub-ring status Both Ethernet rings are in idle state
2 Verify status of all MEPs All Up and Down MEPs are OK
3 Verify status of clock domain and Clock domains are locked.

1588v2 masters and slaves 1588v2 masters and slaves are synchronized.
4 Verify LAG status LAG and LACP sessions are synchronized
ETX-5 Testing Basic Functionality B-5

5 Ping the units to verify network Devices reply to ping

connectivity
6 Verify Telnet/SSH connectivity Telnet/SSH sessions are established

successfully
7 Run Ethernet traffic from the STC Ethernet traffic is running properly without
packet loss
8 Run BERT on the ports 3/1 and 3/2, No errors are detected in pseudowire traffic
using Egate-100s
9 Initiate SNMP management session Devices reply to ping and appear on RADview
from RADview NMS and verify map
management connectivity to all
devices
10 Run a Syslog server application, The Syslog server is operational

such as Kiwi
11 Set up TACACS+ and SNTP servers The servers reply to ping

and ping them
12 Clear alarm logs in all devices Logs are empty with no active alarms. Ethernet
and pseudowire data is running error-free.
B.4 Testing TDM APS

The objective of the test is to verify the correct functionality of traffic switchover
between two TDM ports, working in APS mode.
Test Duration
1 hour
Test Procedure
Table B-7 details the TDM APS test procedure.
B-6 Testing TDM APS ETX-5

Table B-7. TDM APS Test Procedure
1 Verify the following on E5-cTDM-4 TDM traffic is running error-free

card installed in slot 3 of ETX-5 (1):
• APS is defined between port 3/1
and 3/2
• 3/1 is a working port and 3/2 is
a protection port
• TDM traffic is running via port
3/1
2 Test the APS mechanism: APS is working properly.

• Disconnect/reconnect TDM ports No errors are detection in data transmission
• Switch between working and after switchover.
protection ports, using manual Relevant alarms are stored in log file and Syslog
commands server
3 Perform manual switch of the main TDM traffic is running error-free

cards
B.5 Testing LAG

The objective of the test is to verify the correct functionality of traffic switchover
between two Ethernet ports, combined in LAG.
Test Duration
1 hour
Test Procedure
Table B-8 details the LAG test procedure.
Table B-8. LAG Test Procedure
1 Verify the following on E5-GBE-20 Ethernet traffic is running error-free, no packet

card installed in slot 1 of ETX-5 (1): loss is detected
• LAG is defined between port 1/4
and 1/14
• LAG is up, and LACP is
synchronized
• 1/4 is working port and 1/14 is
protection port
• Ethernet traffic is running via
port 1/4
ETX-5 Testing LAG B-7

2 Test the LAG: LAG is working properly.

• Disconnect/reconnect GbE ports No errors are detection in data transmission
• Switch between working and after switchover.
protection ports, using manual Relevant alarms are stored in log file and Syslog
commands server.
3 Perform manual switch of the main Ethernet traffic is running error-free

cards
B.6 Testing ERP

The objective of the test is to verify the correct functionality the main and
sub-rings.
Test Duration
1 hour
Test Procedure
Table B-9 details the ERP test procedure.
Table B-9. ERP Test Procedure
1 Verify that the main and sub-rings Main and sub-rings are in Idle state.
are in Idle state and traffic is Ethernet and pseudowire traffic is running
running through all relevant ports error-free, no packet loss is detected.
2 Disconnect port B/1 on ETX-5 (1) to ERP states change to Protection.

initialize traffic switchover Ethernet and pseudowire traffic is running
through all relevant ports.
Domain clock in all devices is in Locked state.
3 Reconnect port B/1 on ETX-5 (1) to ERP states change to Pending.

restore the rings After the WTR timer expires, the ERP states
change to Idle.
Ethernet and pseudowire traffic is running
through all relevant ports.
Note: E-Line service based on VLAN 700 is
disrupted, because its traffic is not protected
by the ERPs.
B-8 Testing ERP ETX-5

B.7 Testing ERP OAM

The objective of the test is to verify the correct functionality of the Up and Down
MEPs, serving as SF triggers on the main and sub-rings.
Test Duration
1 hour
Test Procedure
Table B-10 details the ERP OAM test procedure.
Table B-10. ERP OAM Test Procedure
1 Verify that all MEPs in the All Up and Down MEPs in the application are up
application are up
2 With traffic running on the ERPs, Correlation between frame counts for the far-
check OAM PM services on Up MEPs and near-end counters on both devices
defined on ETX-5 (1) and ETX-5 (3)
3 Run OAM link trace between the Link trace has been successful
MEPs
4 Run OAM loopback between the Loopback has been successful

MEPs
5 Initialize traffic switchover on the All MEPs are in Up state.

ERP and verify that: Ethernet and pseudowire traffic is running
• All MEPs are OK. through all relevant ports after the switchover.
• Ethernet and pseudowire traffic
is running through all relevant
ports.
B.8 Testing Ethernet Group Protection (Dual

Homing)
The objective of the test is to verify the correct functionality of the Ethernet
group protection.
Test Duration
1 hour
ETX-5 Testing Ethernet Group Protection (Dual Homing) B-9

Test Procedure
Table B-11 details the Ethernet group protection test procedure.
Table B-11. Ethernet Group Protection Test Procedure
1 Verify the following on E5-MC-4 Both 10GbE ports are administratively enabled
cards installed in slot A and slot B and operational
of ETX-5 (1):
• 10GbE ports A/3 and B/4 are
combined into protection group
• A/3 is a working port, B/4 is a
protection port
• Recovery mode is non-revertive
2 Run Ethernet traffic based on The traffic is running error-free via port A/3
VLAN 1111 from port 1/6 towards (working)
port he Ethernet protection group
3 Disconnect port A/3 to initialize the Port B/4 (protection) changes to Active and
switchover traffic is running error-free via port B/4.
Protection group status is correct.
4 Reconnect port A/3 The traffic is running error-free via port B/4.
Port flip did not occur, because recovery mode
is non-revertive.
B.9 Testing Y.1564 Service Activation Test

The objective of the test is to verify the correct functionality of the Y.1564
configuration and performance testing.
Test Duration
0.5 hour
Test Procedure
Table B-12 details the Y.1564 test procedure.
B-10 Testing Y.1564 Service Activation Test ETX-5

Table B-12. Y.1564 Test Procedure
1 Verify that Y.1564 responder on Traffic over VLAN 400 has stopped on both
has been activated on ETX-205A (2) devices.
followed by activation of Y.1564 The Y.1564 tests are running properly.
generator on ETX-5 (1).
The Y.1564 test results are correct and match
Run Y.1564 configuration and the policer configuration (CIR 60 Mbps and EIR
performance test. 10 Mbps).
2 Reverse the Y.1564 actors by Traffic over VLAN 400 has stopped on both
activating the responder on ETX-5 devices.
(1) and generator on ETX-205A (2). The Y.1564 tests are running properly.
Run Y.1564 configuration and The Y.1564 test results are correct and match
performance test. the policer configuration.
B.10 Testing Chassis Reboot Procedure

The objective of the test is to verify the correct execution of chassis reboot
procedure, and to make sure that all configured services, protection and testing
tools operate properly after the reboot.
Test Duration
1 hour
Test Procedure
Table B-13 details the Y.1564 test procedure.
Table B-13. Chassis Reboot Test Procedure
1 Save configuration in all ETX-5 Configuration has been saved successfully in all
devices ETX-5 devices under test
2 Verify that traffic is running through Ethernet and pseudowire traffic is running
all relevant ports error-free, no packet loss is detected
ETX-5 Testing Chassis Reboot Procedure B-11

3 Reboot ETX-5 (2) and wait until the Management connection to all devices
system is restored. Verify the functions properly.
following: ERP status is Idle.
• The devices respond to ping Ethernet and pseudowire traffic is running
requests properly.
• Management access has been LAG is synchronized.
restored (Telnet/SSH, RADview)
Connection to TACACS+, SNTP and Syslog
• Major and sub-ring status is Idle servers operates properly.
• Ethernet and pseudowire traffic Domain clocks in all ETX-5 devices are locked.
is running error-free
Relevant alarms are stored in the log file and
• LAG is synchronized on Syslog server.
• Connectivity to TACACS+, SNTP
and Syslog servers has been
restored
• Domain clocks in all ETX-5
devices are locked.
5 Reboot all ETX-5 devices in the Management connection to all devices

application setup. Verify the functions properly.
following: ERP status is Idle.
• The devices respond to ping Ethernet and pseudowire traffic is running
requests properly.
• Management access has been LAG is synchronized.
restored (Telnet/SSH, RADview)
Connection to TACACS+, SNTP and Syslog
• Major and sub-ring status is Idle servers operates properly.
• Ethernet and pseudowire traffic Domain clocks in all ETX-5 devices are locked.
is running error-free
1588v2 masters and slaves are synchronized.
• LAG is synchronized
Relevant alarms are stored in the log file and
• Connectivity to TACACS+, SNTP on Syslog server.
and Syslog servers has been
restored
• Domain clocks in all ETX-5
devices are locked
• 1588v2 masters and slaves are
synchronized.
B.11 Testing Software Upgrade

The objective of the test is to verify the correct functionality of the software
upgrade process. The test includes procedures for upgrading:
B-12 Testing Software Upgrade ETX-5

• To a major release (ver. 1.0.0 to ver. 1.5.0)

• To a minor release (1.5.0 (0.xx) 1.5.0 (0.yy)).
Test Duration
3 hours
Test Procedure
Table B-14 details the software upgrade test procedure.
Table B-14. Software Upgrade Test Procedure
1 Upgrade all ETX-5 devices from sw- Software upgrade has been successful.
pack 1.0.0 (0.67) R1.0 to sw-pack Ethernet and pseudowire traffic is running
1.5.0 (0.xx) R1.5 properly
2 Upgrade all ETX-5 devices from sw- Software upgrade has been successful.
pack 1.5.0 (0.xx) R1.5 to sw-pack Ethernet and pseudowire traffic is running
1.5.0 (0.yy) R1.5 properly
ETX-5 Testing Software Upgrade B-13

B-14 Testing Software Upgrade ETX-5

Publication No. 570-200-08/16
Order this publication by Catalog No. 80501
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North America Headquarters

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

ETX-5 MN

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-5 MN

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

© 1988–2017 RAD Data Communications Ltd. Publication No. 570-200-08/16

General Safety Instructions

Protective ground: the marked lug or terminal should be connected to the

Handling Energized Products

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Avertissement Cet appareil est un appareil de Classe A. Dans un environnement résidentiel,

Achtung Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In

Mise au rebut du produit

Afin de faciliter la réutilisation, le recyclage ainsi que d'autres formes de

Instructions générales de sécurité

Danger de choc électrique ! Evitez tout contact avec la surface marquée

Mise à la terre de protection : la cosse ou la borne marquée devrait être

Manipuler des produits sous tension

Règles générales de sécurité

Connexion au courant du secteur

Assurez-vous que l'installation électrique est conforme à la réglementation locale.

Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 6971920, Israel

declares under its sole responsibility that the product:

Product Name: ETX-5300A (may be followed by several suffixes separated by slashes)

Product Options: All

conforms to the following standard(s) or other normative document(s)

EMC EN 55022:2010 Information technology equipment; Radio disturbance characteristics;

EN 55024:2010 Information technology equipment; Immunity characteristics;

EN 61000-3-2:2014 Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic

EN 61000-3-3:2013 Electromagnetic compatibility (EMC); Section 3-3: Limits -

Safety EN 60950-1:2006 + Information technology equipment; Safety – Part 1:

European Contact: RAD Data Communications GmbH

Agent In SNMP, this refers to the managed system.

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

ANSI American National Standards Institute.

Baud Unit of signaling speed equivalent to the number of discrete

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

Buffer A storage device. Commonly used to compensate for differences in

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

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

Carrier A continuous signal at a fixed frequency that is capable of being

byte ATM payload, which contains the user data.

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

Concentrator Device that serves as a wiring hub in a star-topology network.

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

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

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

Decibel See dB.

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

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

E3 The European standard for high speed digital transmission, operating

Encapsulation Encapsulating data is a technique used by layered protocols in which a

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

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

Full Duplex A circuit or device permitting transmission in two directions (sending

Gateway Gateways are points of entrance and exit from a communications

Grooming In telecommunications, the process of separating and segregating

Interface A shared boundary, defined by common physical interconnection

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