ETX-5300A: Ethernet Service Aggregation Platform

INSTALLATION AND
OPERATION MANUAL
ETX-5300A
Ethernet Service Aggregation Platform
Version 1.0
ETX-5300A
Ethernet Service Aggregation Platform
Version 1.0
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-5300A 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-5300A product name is owned by RAD. No right, license, or interest to such trademark
is granted hereunder, and you agree that no such right, license, or interest shall be asserted by
you with respect to such trademark. The RAD name, logo, logotype, and the terms EtherAccess,
TDMoIP and TDMoIP Driven, and the product names Optimux and IPmux, are registered
trademarks of RAD Data Communications Ltd. All other trademarks are the property of their
respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
ETX-5300A. 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-5300A, based on or derived in any way from the ETX-5300A. Your undertaking in this
paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the ETX-5300A 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-5300A and all copies and
portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters
RAD Data Communications Ltd.
North America Headquarters

RAD Data Communications Inc.
24 Raoul Wallenberg Street

Tel Aviv 69719, Israel
Tel: 972-3-6458181
Fax: 972-3-6498250, 6474436
E-mail: market@rad.com
900 Corporate Drive

Mahwah, NJ 07430, USA
Tel: (201) 5291100, Toll free: 1-800-4447234
Fax: (201) 5295777
E-mail: market@radusa.com
20082013 RAD Data Communications Ltd.
Publication No. 570-200-03/13
Front Matter
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the ETX-5300A 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-5300A, and in no event shall
RAD's liability exceed the purchase price of the ETX-5300A.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to ETX-5300A and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the ETX-5300A 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-5300A shall
not exceed the sum paid to RAD for the purchase of the ETX-5300A. In no event shall RAD be
liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits,
even if RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal waste at
the end of its life cycle. Upon termination of the units use, customers should
provide for its collection for reuse, recycling or other form of environmentally
conscientious disposal.
ii
ETX-5300A Ver. 1.0
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
Warning
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.
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.
Warning
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.
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 or XFP laser transceivers into the product.
Users are alerted that RAD cannot be held responsible for any damage that may result if noncompliant 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-5300A Ver. 1.0
iii
Front Matter
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 14 AWG (1.4 mm2) 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 or other means.
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.
The ETX-5300A is equipped with surge protectors between the
telecommunication lines and ground. The connection to the protective
ground must be always maintained.
Warning
In Finland, Norway and Sweden, the unit is restricted to installation by service personnel in
Restricted Access Locations only.
FI
Laite on liitettv suojamaadoituskoskettimilla varustettuun pistorasiaan
NO
Apparatet m tilkoples jordet stikkontakt
SE
Apparaten skall anslutas till jordat uttag
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.
iv
ETX-5300A Ver. 1.0
Front Matter
Connecting DC Power
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.
A 25A circuit breaker must be installed for each DC input. The circuit breaker must have a high
breaking capacity and must operate at short-circuit current exceeding 60A.
Before connecting the DC supply wires, ensure that power is removed from the DC circuit.
Switch off both circuit breakers. 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 breakers 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,

10 BaseT, 100 BaseT, Unbalanced E1,
E2, E3, STM, DS-2, DS-3, S-Interface
ISDN, Analog voice E&M, Alarm
SELV
xDSL (without feeding voltage),

Balanced E1, T1, Sub E1/T1
TNV-1 Telecommunication Network Voltage-1:
FXS (Foreign Exchange Subscriber)

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

(with feeding voltage), U-Interface
ISDN
ETX-5300A Ver. 1.0
Safety Extra Low Voltage:

Ports which do not present a safety hazard. Usually
up to 30 VAC or 60 VDC.
Ports whose normal operating voltage is within the

limits of SELV, on which overvoltages from
telecommunications networks are possible.
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 possible.
Front Matter
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution
To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention
Pour rduire les risques sincendie, utiliser seulement des conducteurs de

tlcommunications 26 AWG ou de section suprieure.
Some ports are suitable for connection to intra-building or non-exposed wiring or cabling only. In
such cases, a notice will be given in the installation instructions.
Do not attempt to tamper with any carrier-provided equipment or connection hardware.
Electromagnetic Compatibility (EMC)

The equipment is designed and approved to comply with the electromagnetic regulations of
major regulatory bodies. The following instructions may enhance the performance of the
equipment and will provide better protection against excessive emission and better immunity
against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially
for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be
installed on certain cables. In such cases, special instructions are provided in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines
is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal
conversion loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
vi
ETX-5300A Ver. 1.0
Front Matter
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with
plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines.
Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive
wrist strap.
FCC-15 User Information

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

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

Warning
This is a class A product. In a domestic environment, this product may cause

radio interference, in which case the user will be required to take adequate
measures.
Avertissement
Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel,

cet appareil peut provoquer des brouillages radiolectriques. Dans ces cas, il
peut tre demand lutilisateur de prendre les mesures appropries.
Achtung
Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In

Wohngebieten knnen beim Betrieb dieses Gertes Rundfunkstrrungen
auftreten, fr deren Behebung der Benutzer verantwortlich ist.
ETX-5300A Ver. 1.0
vii
Front Matter
Franais
Mise au rebut du produit

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

Les instructions suivantes servent de guide gnral d'installation et d'opration scurises des
produits de tlcommunications. Des instructions supplmentaires sont ventuellement
indiques dans le manuel.
Symboles de scurit
Ce symbole peut apparaitre sur l'quipement ou dans le texte. Il indique des
risques potentiels de scurit pour l'oprateur ou le personnel de service,
quant l'opration du produit ou sa maintenance.
Avertissement
Danger de choc lectrique ! Evitez tout contact avec la surface marque

tant que le produit est sous tension ou connect des lignes externes de
tlcommunications.
Mise la terre de protection : la cosse ou la borne marque devrait tre

connecte la prise de terre de protection du btiment.
viii
ETX-5300A Ver. 1.0
Avertissement
Front Matter
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas,
une tiquette indiquant la classe laser ainsi que d'autres avertissements, le
cas chant, sera jointe prs du transmetteur optique. Le symbole
d'avertissement laser peut aussi tre joint.
Veuillez observer les prcautions suivantes :
Avant la mise en marche de l'quipement, assurez-vous que le cble de

fibre optique est intact et qu'il est connect au transmetteur.
Ne tentez pas d'ajuster le courant de la commande laser.
N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans

terminaison et n'observez pas directement un rayon laser.
L'usage de priphriques optiques avec l'quipement augmentera le

risque pour les yeux.
L'usage de contrles, ajustages ou procdures autres que celles

spcifies ici pourrait rsulter en une dangereuse exposition aux
radiations.
ATTENTION : Le rayon laser peut tre invisible !
Les utilisateurs pourront, dans certains cas, insrer leurs propres metteurs-rcepteurs Laser
SFP/XFP dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas tre tenue
responsable de tout dommage pouvant rsulter de l'utilisation d'metteurs-rcepteurs non
conformes. Plus particulirement, les utilisateurs sont avertis de n'utiliser que des produits
approuvs par l'agence et conformes la rglementation locale de scurit laser pour les
produits laser de classe 1.
Respectez toujours les prcautions standards de scurit durant l'installation, l'opration et la
maintenance de ce produit. Seul le personnel de service qualifi et autoris devrait effectuer
l'ajustage, la maintenance ou les rparations de ce produit. Aucune opration d'installation,
d'ajustage, de maintenance ou de rparation ne devrait tre effectue par l'oprateur ou
l'utilisateur.
Manipuler des produits sous tension

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

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

Tel Aviv 69719 Israel
Declares that the product:

Product Name
ETX-5300A
Product Options:
All
Conforms to the following standard(s) or other normative document(s):

EMC
Safety
EN 55022:2010
Information technology equipment Radio disturbance

characteristics Limits and methods of measurement.
EN 55024:2010
Information technology equipment Immunity characteristics
Limits and methods of measurement.
EN 61000-3-2:2006
Electromagnetic compatibility (EMC) - Part 3-2: Limits Limits for harmonic current emissions (equipment input
current 16A per phase)
EN 61000-3-3:2008
Electromagnetic compatibility (EMC) - Part 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.
EN 60950-1:2006 +
A11:2009,
A1:2010
+ A12:2011
Information technology
General requirements.
equipment
Safety
Part 1:
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 2004/108/EC, the
Low Voltage Directive 2006/95/EC, the R&TTE Directive 99/5/EC for wired equipment and the
ROHS Directive 2011/65/EU. The product was tested in a typical configuration.
Tel Aviv, 1 January 2013
Nathaniel Shomroni, Homologation Team Leader

European Contact:
ETX-5300A Ver. 1.0
RAD Data Communications GmbH

Otto-Hahn-Str. 28-30, 85521 Ottobrunn-Riemerling, Germany
xi
Front Matter
Glossary
Address
A coded representation of the origin or destination of data.
Agent
In SNMP, this refers to the managed system.
ANSI
American National Standards Institute.
APS (Automatic
protection switching)
An automatic service restoration function by which a network senses

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

and more centralized points of presence
Balanced
A transmission line in which voltages on the two conductors are equal

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

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

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

guarantees are provided.
Bipolar
Signaling method in E1/T1 representing a binary 1 by alternating

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

a one or zero (1 or 0).
Bridge
A device interconnecting local area networks at the OSI data link layer,
filtering and forwarding frames according to media access control
(MAC) addresses.
Buffer
A storage device. Commonly used to compensate for differences in

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

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

modulated with a second (information carrying) signal.
xii
ETX-5300A Ver. 1.0
Front Matter
CESoPSN
Structure-aware TDM Circuit Emulation Service over Packet Switched

Network. A method for encapsulating structured (NxDS0) Time
Division Multiplexed (TDM) signals as pseudo-wires over packet
switched networks (PSN).
Channel
A path for electrical transmission between two or more points. Also

called a link, line, circuit or facility.
CIR (Committed
Information Rate)
A term, which defines the information rate that the network is

committed to provide to the user, under any network conditions.
Circuit Emulation
Service
New technology for offering circuit emulation services over packetswitched networks. The service offers traditional TDM trunking (at n x
64 kbps, fractional E1/T1, E1/T1 or E3/T3) over a range of transport
protocols, including Internet Protocol (IP), MPLS and Ethernet.
CLI
Command Line Interface (CLI) is a mechanism for interacting with a

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

transmission.
Congestion
A state in which the network is overloaded and starts to discard user

data (frames, cells or packets).
Congestion Control
A resource and traffic management mechanism to avoid and/or

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

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

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

communications, an alternating, non-continuous (pulsating) signal.
E1 Line
A 2.048 Mbps line, common in Europe, that supports thirty-two

64 kbps channels, each of which can transmit and receive data or
digitized voice. The line uses framing and signaling to achieve
synchronous and reliable transmission. The most common
configurations for E1 lines are E1 PRI, and unchannelized E1.
E3
The European standard for high speed digital transmission, operating

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

low level protocol accepts a message from a higher level protocol,
then places it in the data portion of the lower-level frame. The
logistics of encapsulation require that packets traveling over a physical
network contain a sequence of headers.
EIR
Excess Information Rate. The rate that exceeds a specified threshold

(CIR) for brief periods of time.
Ethernet
A local area network (LAN) technology which has extended into the
wide area networks. Ethernet operates at many speeds, including data
rates of 10 Mbps (Ethernet), 100 Mbps (Fast Ethernet), 1,000 Mbps
(Gigabit Ethernet), 10 Gbps, 40 Gbps, and 100 Gbps.
ETX-5300A Ver. 1.0
xiii
Front Matter
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).
Ethertype
A two-octet field in an Ethernet frame that indicates type of the

protocol encapsukated in the Ethernet frame payload
Flow
Unidirectional traffic entity that connects two physical or logical ports
Flow Control
A congestion control mechanism
Frame
A logical grouping of information sent as a link-layer unit over a

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

and receiving) at the same time.
G.703
An ITU standard for the physical and electrical characteristics of

various digital interfaces, including those at 64 kbps and 2.048 Mbps.
Gateway
Gateways are points of entrance and exit from a communications

network. Viewed as a physical entity, a gateway is that node that
translates between two otherwise incompatible networks or network
segments. Gateways perform code and protocol conversion to
facilitate traffic between data highways of differing architecture.
Impedance
The combined effect of resistance, inductance and capacitance on a

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

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

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

introduce errors and loss of synchronization in high speed
synchronous communications.
L2CP
Set of Layer-2 control (slow) protocols that operate across a number

of access and aggregation network technologies
xiv
ETX-5300A Ver. 1.0
Front Matter
Laser
A device that transmits an extremely narrow and coherent beam of

electromagnetic energy in the visible light spectrum. Used as a light
source for fiber optic transmission (generally more expensive, shorter
lived, single mode only, for greater distances than LED).
Latency
The time between initiating a request for data and the beginning of
the actual data transfer. Network latency is the delay introduced
when a packet is momentarily stored, analyzed and then forwarded.
Load Balancing
A technique that distributes network traffic along parallel paths in

order to maximize the available network bandwidth while providing
redundancy.
Loading
The addition of inductance to a line in order to minimize amplitude

distortion. Used commonly on public telephone lines to improve voice
quality, it can make the lines impassable to high speed data, and
baseband modems.
Loopback
A type of diagnostic test in which the transmitted signal is returned to

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

(SNMP) information from an agent. An agent and manager share a
database of information, called the Management Information Base
(MIB). An agent can use a message called a traps-PDU to send
unsolicited information to the manager. A manager that uses the
RADview MIB can query the RAD device, set parameters, sound alarms
when certain conditions appear, and perform other administrative
tasks.
Mark
In telecommunications, this means the presence of a signal. A mark is

equivalent to a binary 1. A mark is the opposite of a space (0).
Master Clock
The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Modular
Modular interfaces enable field-changeable conversion.
Multiplexer
At one end of a communications link, a device that combines several

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

or stations connected by communications channels; the collection of
equipment through which connections are made between data
stations.
Node
A point of interconnection to a network.
NodeB
The name of the BTS for 3G cellular traffic
NTP
The Network Time Protocol, a protocol for synchronizing the clocks of

computer systems over packet-switched, variable-latency data
networks. NTP uses UDP on port 123 as its transport layer.
ETX-5300A Ver. 1.0
xv
Front Matter
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.
Physical Layer
Layer 1 of the OSI model. The layer concerned with electrical,

mechanical, and handshaking procedures over the interface
connecting a device to the transmission medium.
Policing
A method for verifying that the incoming traffic complies with the
users service contract.
Polling
See Multidrop.
Port
The physical interface to a computer or multiplexer, for connection of

terminals and modems.
Prioritization
Also called CoS (class of service), classifies traffic into categories such
as high, medium, and low. The lower the priority, the more drop
eligible is a packet. When the network gets busy, prioritization
ensures critical or high-rated traffic is passed first, and packets from
the lowest categories may be dropped.
Prompt
One or more characters in a command line interface to indicate that

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

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

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

The packets are held in queues for subsequent processing. After being
processed by the router, the packets are then sent to their
destination based on priority. Strict priority and Weighted Fair queuing
methods are used for traffic differentiation.
Q-in-Q
See MAC-in-MAC.
RADIUS (Remote
Authentication Dial-In
User Service)
An authentication, authorization and accounting protocol for

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

bridges, which logically connect at OSI Layer 2, routers provide logical
paths at OSI Layer 3. Like bridges, remote sites can be connected
using routers over dedicated or switched lines to create WANs.
Routing
The process of selecting the most efficient circuit path for a message.
Scalable
Able to be changed in size or configuration to suit changing

conditions. For example, a scalable network can be expanded from a
few nodes to thousands of nodes.
Single Mode
Describing an optical wave-guide or fiber that is designed to

propagate light of only a single wavelength (typically 5-10 microns in
diameter).
SAToP
Structure-Agnostic Time Division Multiplexing (TDM) over Packet. A

method for encapsulating Time Division Multiplexing (TDM) bitstreams (T1, E1, T3, E3) that disregards any structure that may be
imposed on these streams, in particular the structure imposed by the
standard TDM framing.
SONET (Synchronous
Optical Network)
A North American standard for using optical media as the physical

transport for high speed long-haul networks. SONET basic speeds
start at 51.84 Mbps and go up to 2.5 Gbps.
Space
In telecommunications, the absence of a signal. Equivalent to a binary

0.
SSH (Secure Shell)
A network protocol that allows data to be exchanged over a secure

channel between two computers. Encryption provides confidentiality
and integrity of data.
SVI
A logical port used for binding flows to bridge ports, router interfaces
or Layer-2 TDM pseudowires
Sync
See Synchronous Transmission.
Syslog
Communcation standard for data logging. It collects heterogeneous

data into a single data repository, providing system administrators
with a single point of management for collecting, distributing and
processing audit data. The Syslog operation is standartized by RFC
3164 and RFC 5674.
T1
A digital transmission link with a capacity of 1.544 Mbps used in North

America. Typically channelized into 24 DS0s, each capable of carrying
a single voice conversation or data stream. Uses two pairs of twisted
pair wires.
T3
A digital transmission link with a capacity of 45 Mbps, or 28 T1 lines.
Telnet
The virtual terminal protocol in the Internet suite of protocols. It lets

users on one host access another host and work as terminal users of
that remote host. Instead of dialing into the computer, the user
connects to it over the Internet using Telnet. When issuing a Telnet
session, it connects to the Telnet host and logs in. The connection
enables the user to work with the remote machine as though a
terminal was connected to it.
ETX-5300A Ver. 1.0
xvii
Front Matter
Throughput
The amount of information transferred through the network between

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

single channel. In E1 and T1, one timeslot typically represents one 64
kbps channel.
Traffic Management
Set of actions and operations performed by the network to guarantee

the operability of the network, exercised in the form of traffic control
and flow control.
Traffic Policing
Mechanism whereby any traffic which violates the traffic contract

agreed to at connection setup, is detected and discarded.
Traffic Shaping
A method for smoothing the bursty traffic rate that might arrive on an
access virtual circuit so as to present a more uniform traffic rate on
the network.
Trunk
A single circuit between two points, both of which are switching

centers or individual distribution points. A trunk usually handles many
channels simultaneously.
VLAN-Aware
A device that is doing the Layer 2 bridging according to the VLAN tag
in addition to the standard bridging parameters. A VLAN-aware device
will not strip or add any VLAN header.
VLAN Stacking
A technique that lets carriers offer multiple virtual LANs over a single
circuit. In essence, the carrier creates an Ethernet virtual private
network to tunnel customer VLANs across its WAN; this helps avoid
name conflicts among customers of service providers who connect to
the carrier. Stacking works by assigning two VLAN IDs to each frame
header. One is a "backbone" VLAN ID used by the service provider; the
other one has up to 4,096 unique 802.1Q VLAN tags.
Zero suppression
Technique used to ensure a minimum density of marks.
xviii
ETX-5300A Ver. 1.0
Quick Start Guide

This section describes the minimum configuration needed to prepare ETX-5300A
for operation.
1.
Installing the Unit
Perform the following steps to install the unit:

1. Determine the required configuration of ETX-5300A, 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-5300A Ver. 1.0
Installing the Unit
Quick Start Guide
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-5300A 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-5300A 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-5300A 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.
ETX-5300A Ver. 1.0
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-5300A#
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 setting.
12. Continue with product configuration.
Configuring Management Flows

To manage the ETX-5300A from a remote NMS, you must first preconfigure the
basic parameters using a supervision terminal connected to the ETX-5300A
CONTROL DCE port. RAD recommends Layer-3 management access via the
out-of-band Ethernet management port.
To preconfigure ETX-5300A 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.
ETX-5300A Ver. 1.0
Quick Start Guide
#*******************************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
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
ETX-5300A Ver. 1.0
Quick Start Guide
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************************************
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.
ETX-5300A Ver. 1.0
Verifying Connectivity
Quick Start Guide
5.
Configuring Services
Proceed with service configuration. Chapter 5 details different scenarios for

provisioning supported Ethernet services.
Configuring Services
ETX-5300A Ver. 1.0
Contents
Chapter 1. Introduction
1.1
1.2
1.3
1.4
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
Physical Description ............................................................................................................. 1-4
Front Panel ........................................................................................................................ 1-5
Rear Panel ......................................................................................................................... 1-6
Available Modules .............................................................................................................. 1-6
Functional Description .......................................................................................................... 1-6
System Structure ............................................................................................................... 1-6
Main Card .......................................................................................................................... 1-7
10GbE Interface ............................................................................................................ 1-9
Packet Processor ........................................................................................................... 1-9
Timing Subsystem ....................................................................................................... 1-10
Management Subsystem ............................................................................................. 1-11
Ethernet Service Cards ..................................................................................................... 1-12
GbE and 10GbE Interfaces ........................................................................................... 1-13
Packet Processor ......................................................................................................... 1-13
SDH/SONET Card .............................................................................................................. 1-14
STM-1/OC-3 Interfaces ................................................................................................ 1-15
Pseudowire Services .................................................................................................... 1-16
Adaptive Timing .......................................................................................................... 1-19
Timing Mechanism ........................................................................................................... 1-20
Physical Port Clock ...................................................................................................... 1-21
External (BITS) Clock.................................................................................................... 1-22
IEEE 1588v2 Clock ....................................................................................................... 1-22
GPS Clock .................................................................................................................... 1-23
Technical Specifications...................................................................................................... 1-23
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
Site Requirements and Prerequisites .................................................................................... 2-4
Power ................................................................................................................................ 2-4
AC Power ...................................................................................................................... 2-5
DC Power ...................................................................................................................... 2-5
ETX-5300A Ver. 1.0
Table of Contents
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
2.15
2.16
2.17
2.18
2.19
2.20
2.21
Panel Clearance ................................................................................................................. 2-5

Ambient Requirements ...................................................................................................... 2-6
Electromagnetic Compatibility Considerations .................................................................... 2-6
Package Contents................................................................................................................. 2-6
Required Equipment ............................................................................................................. 2-6
Installing AC Power Supply Modules ...................................................................................... 2-7
Installing the ETX-5300A Enclosure ...................................................................................... 2-7
Installing Cable Managers ................................................................................................... 2-7
Installing ETX-5300A in Racks ............................................................................................ 2-8
Installing a Fan Tray ........................................................................................................... 2-10
Installing Power Inlet Modules ............................................................................................ 2-11
E5-PIM/AC Module............................................................................................................ 2-12
E5-PIM/DC Modules .......................................................................................................... 2-12
Installing PI Modules ........................................................................................................ 2-12
Installing the Main Card ...................................................................................................... 2-12
Inserting the Main Card .................................................................................................... 2-13
Removing the Main Card .................................................................................................. 2-13
Replacing a Main Card during Equipment Operation ......................................................... 2-14
ETX-5300A Chassis with two CONTROL Modules ......................................................... 2-14
ETX-5300A Chassis with Single Main Card ................................................................... 2-14
Connecting to Power .......................................................................................................... 2-15
Grounding ........................................................................................................................ 2-15
Connecting to AC Power .................................................................................................. 2-15
Connecting to DC Power .................................................................................................. 2-15
Installing I/O Cards ............................................................................................................. 2-16
Installing Blank Panels ........................................................................................................ 2-17
Installing SFP or XFP Modules ............................................................................................. 2-17
Connecting to 10Gb Ethernet Equipment ........................................................................... 2-18
Connecting to Gigabit Ethernet Equipment ......................................................................... 2-19
Connecting to STM-1/OC-3 Equipment ............................................................................... 2-19
Connecting to External Clock Devices ................................................................................. 2-20
Connecting to GPS Clock Devices ........................................................................................ 2-20
Connecting to a Terminal ................................................................................................... 2-21
Connecting to a Network Management Station .................................................................. 2-22
Connecting to an External Alarm Device ............................................................................. 2-22
Labeling Cable .................................................................................................................... 2-22
Chapter 3. Operation
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
Turning On the Unit ............................................................................................................. 3-1

Indicators ............................................................................................................................. 3-2
Startup ................................................................................................................................. 3-3
Configuration and Application Software Files ..................................................................... 3-3
Loading Sequence .............................................................................................................. 3-4
Using a Custom Configuration File ........................................................................................ 3-5
Saving Configuration Changes .............................................................................................. 3-5
Confirming the Configuration File ......................................................................................... 3-5
Handling Configuration File Errors ........................................................................................ 3-6
Turning Off the Unit ............................................................................................................. 3-6
Chapter 4. Management and Security

4.1
ii
CLI-Based Configuration ....................................................................................................... 4-2

Working with Terminal ....................................................................................................... 4-2
ETX-5300A Ver. 1.0
Table of Contents
Working with Telnet and SSH ............................................................................................. 4-2

Login ................................................................................................................................. 4-3
Using the CLI ...................................................................................................................... 4-3
Command Tree .................................................................................................................. 4-5
4.2 GUI-Based Configuration .................................................................................................... 4-27
Preconfiguring ETX-5300A for SNMP Management ........................................................... 4-27
Working with RADview ..................................................................................................... 4-30
Working with 3rd Party Network Management Systems ................................................... 4-30
4.3 Management Access Methods ............................................................................................ 4-31
Layer-2 Management Access ....................................................................................... 4-31
Layer-3 Management Access ....................................................................................... 4-31
4.4 Services for Management Traffic ........................................................................................ 4-33
4.5 Terminal Control Port ......................................................................................................... 4-33
Factory Defaults .............................................................................................................. 4-33
Configuring Control Port Parameters ................................................................................ 4-33
4.6 User Access ........................................................................................................................ 4-34
Example Defining Users................................................................................................. 4-34
Example Displaying Users .............................................................................................. 4-36
4.7 SNMP Management ............................................................................................................ 4-36
Standards ........................................................................................................................ 4-36
Benefits ........................................................................................................................... 4-37
Functional Description ..................................................................................................... 4-37
SNMP Engine ID ........................................................................................................... 4-38
SNMPv3 Message Processing ....................................................................................... 4-38
User-Based Security Model (USM) ............................................................................... 4-39
View-Based Access Control Model (VACM) ................................................................... 4-39
SNMP Security Level .................................................................................................... 4-40
SNMPv3 Administrative Features ................................................................................. 4-40
SNMPv3 Configuration ..................................................................................................... 4-41
Example ........................................................................................................................... 4-48
4.8 Management Access........................................................................................................... 4-51
Configuring Management Access...................................................................................... 4-51
4.9 Access Policy ...................................................................................................................... 4-51
Configuring Access Policy ................................................................................................. 4-52
4.10 Authentication via RADIUS Server ....................................................................................... 4-52
Standards ........................................................................................................................ 4-53
Benefits ........................................................................................................................... 4-53
Configuring RADIUS Parameters ....................................................................................... 4-53
Displaying RADIUS Status ................................................................................................. 4-54
Displaying RADIUS Statistics............................................................................................. 4-54
4.11 Authentication via TACACS+ Server..................................................................................... 4-55
Standards ........................................................................................................................ 4-56
Benefits ........................................................................................................................... 4-56
Components................................................................................................................ 4-56
Accounting .................................................................................................................. 4-57
Defining TACACS+ Server ................................................................................................. 4-57
ETX-5300A Ver. 1.0
iii
Table of Contents
Configuring Accounting Groups ........................................................................................ 4-58

Example Defining Server ............................................................................................... 4-59
Example Defining Accounting Group .............................................................................. 4-59
Displaying Statistics ......................................................................................................... 4-60
Defining Accounting Groups ............................................................................................. 4-61
4.12 Syslog ................................................................................................................................ 4-61
Standards and MIBs ......................................................................................................... 4-61
Benefits ........................................................................................................................... 4-61
Elements ..................................................................................................................... 4-62
Transport Protocol ...................................................................................................... 4-62
Message Format .......................................................................................................... 4-62
Facilities and Severities ............................................................................................... 4-63
Syslog Configuration ........................................................................................................ 4-63
Example ...................................................................................................................... 4-65
Configuration Errors .................................................................................................... 4-65
4.13 Programming Cards ............................................................................................................ 4-66
Displaying Card Summary ................................................................................................. 4-66
Provisioning I/O Cards ...................................................................................................... 4-67
Resetting I/O Cards .......................................................................................................... 4-68
Displaying Card Status ..................................................................................................... 4-68
Configuration Errors ......................................................................................................... 4-69
Chapter 5. Services
5.1
5.2
5.3
5.4
5.5
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
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
E-LAN Service ..................................................................................................................... 5-15
Routing Services ................................................................................................................. 5-18
I/O-to-Main via Router Path ............................................................................................. 5-18
Router-to-Bridge Path ..................................................................................................... 5-21
Pseudowire Services ........................................................................................................... 5-24
Point-to-Point L2 Pseudowire Service .............................................................................. 5-25
L2 Pseudowire Service over Bridge ................................................................................... 5-27
L3 Pseudowire Service ..................................................................................................... 5-30
Chapter 6. Ports
6.1
iv
Ethernet Ports ...................................................................................................................... 6-1

Standards and MIBs ........................................................................................................... 6-1
Benefits ............................................................................................................................. 6-1
ETX-5300A Ver. 1.0
6.2
6.3
Table of Contents
Factory Defaults ................................................................................................................ 6-1

Functional Description ....................................................................................................... 6-1
Autonegotiation ............................................................................................................ 6-1
Flow Control .................................................................................................................. 6-2
Jumbo Frames ............................................................................................................... 6-2
Ethertype ...................................................................................................................... 6-2
L2CP Handling ............................................................................................................... 6-2
Classification Key .......................................................................................................... 6-3
Queue Group Profile ...................................................................................................... 6-3
Configuring Ethernet Ports................................................................................................. 6-3
Displaying Port Status ........................................................................................................ 6-4
Displaying Statistics ........................................................................................................... 6-5
Displaying Optical Link SFP/XFP Status ............................................................................... 6-9
Example ........................................................................................................................... 6-10
SDH/SONET Ports ............................................................................................................... 6-11
Benefits ........................................................................................................................... 6-11
SDH Implementation Principles .................................................................................... 6-12
General Structure of SDH Signals ................................................................................ 6-13
SDH Frame Organization ............................................................................................. 6-14
VC Assembly/Disassembly Process ............................................................................... 6-15
STM-1 Frame Structure ............................................................................................... 6-16
Pointers ...................................................................................................................... 6-17
SDH Overhead Data .................................................................................................... 6-17
SDH Tributary Units ..................................................................................................... 6-22
SDH Maintenance Signals and Response to Abnormal Conditions ................................ 6-25
SONET Environment .................................................................................................... 6-28
SDH/SONET Port Diagnostics ....................................................................................... 6-29
Configuring SDH/SONET Interfaces................................................................................... 6-30
Configuring AUG/OC-3 Interfaces ..................................................................................... 6-31
Configuring TUG3/AU3/STS-1 Inerfaces ............................................................................ 6-32
Configuring VC-12/VC-11/VT-1.5 Inerfaces ....................................................................... 6-33
Configuring SOH Profile ................................................................................................... 6-34
Configuring Path Profile ................................................................................................... 6-35
Example ........................................................................................................................... 6-36
Displaying Status ............................................................................................................. 6-37
Testing SDH/SONET Ports ................................................................................................ 6-42
E1 Ports ............................................................................................................................. 6-45
E1 Line Signal Characteristics ...................................................................................... 6-45
E1 Signal Structure ...................................................................................................... 6-46
Timeslot 0 ................................................................................................................... 6-46
Multiframes ................................................................................................................. 6-47
Channel Associated Signaling ...................................................................................... 6-48
CRC-4 Error Detection ................................................................................................. 6-48
E1 Alarm Conditions .................................................................................................... 6-49
E1 Port Diagnostics ..................................................................................................... 6-49
ETX-5300A Ver. 1.0
Table of Contents
6.4
6.5
6.6
Configuring Internal E1 Interfaces .................................................................................... 6-51

Testing Internal E1 Ports .................................................................................................. 6-54
Running Loopbacks ..................................................................................................... 6-54
BER Testing ................................................................................................................. 6-55
Example ........................................................................................................................... 6-55
T1 Ports ............................................................................................................................. 6-56
T1 Line Signal .............................................................................................................. 6-57
T1 Signal Structure ...................................................................................................... 6-58
T1 Alarm Conditions .................................................................................................... 6-59
T1 Port Diagnostics ..................................................................................................... 6-59
Configuring Internal T1 Interfaces .................................................................................... 6-62
Example ........................................................................................................................... 6-65
Service Aggregation Group (SAG) ....................................................................................... 6-66
Benefits ........................................................................................................................... 6-66
Configuring SAGs ............................................................................................................. 6-67
Example ........................................................................................................................... 6-67
Service Virtual Interface (SVI) ............................................................................................. 6-68
Configuring SVIs ............................................................................................................... 6-69
Example ........................................................................................................................... 6-70
Chapter 7. Resiliency
7.1
7.2
vi
Main Card Redundancy ......................................................................................................... 7-1

Benefits ............................................................................................................................. 7-1
Configuring Main Card Redundancy .................................................................................... 7-2
Displaying Main Card Protection Status .............................................................................. 7-2
Configuration Errors ........................................................................................................... 7-3
Ethernet Link Aggregation (LAG) .......................................................................................... 7-3
Benefits ............................................................................................................................. 7-3
Intra-Card LAG............................................................................................................... 7-4
Inter-Card LAG .............................................................................................................. 7-4
Configuring LAG ................................................................................................................. 7-5
LACP Traffic ................................................................................................................... 7-5
Special Considerations for I/O Cards .............................................................................. 7-6
Deleting the LAG .............................................................................................................. 7-10
ETX-5300A Ver. 1.0
7.3
7.4
Table of Contents
Displaying LAG Status ...................................................................................................... 7-11

Displaying LACP Status ..................................................................................................... 7-11
Displaying LACP Statistics ................................................................................................ 7-12
Example ........................................................................................................................... 7-13
Inter-Card LAG between Two Main Cards..................................................................... 7-13
Inter-Card LAG between Two I/O Cards ....................................................................... 7-15
Ethernet Ring Protection (ERP) ........................................................................................... 7-19
Standards ........................................................................................................................ 7-20
Benefits ........................................................................................................................... 7-20
Ring Topology ............................................................................................................. 7-20
R-APS Messaging ......................................................................................................... 7-21
Mechanism of Operation ............................................................................................. 7-21
Timers ......................................................................................................................... 7-22
Administrative Commands ........................................................................................... 7-22
Multiple Rings.............................................................................................................. 7-22
Configuring ERP ............................................................................................................... 7-24
Displaying ERP Status....................................................................................................... 7-26
Displaying ERP Statistics .................................................................................................. 7-27
Example ........................................................................................................................... 7-28
Automatic Protective Switching (APS) ................................................................................ 7-38
Benefits ........................................................................................................................... 7-38
APS Architecture ......................................................................................................... 7-39
Automatic Switchover Conditions ................................................................................ 7-40
Manual Switching Commands ...................................................................................... 7-40
Configuring I/O Card Protection ....................................................................................... 7-41
Configuring APS ............................................................................................................... 7-42
Displaying APS Status ...................................................................................................... 7-43
Example ........................................................................................................................... 7-43
Intra-Card APS ............................................................................................................. 7-43
Inter-Card APS ............................................................................................................. 7-43
Chapter 8. Networking
8.1
Flows ................................................................................................................................... 8-1

Benefits ............................................................................................................................. 8-1
I/O Ingress Flows ........................................................................................................... 8-2
Other Flow Types .......................................................................................................... 8-2
Flow Processing ............................................................................................................ 8-2
Drop Action ................................................................................................................... 8-3
Flow Counters ............................................................................................................... 8-4
RFC-2544 Loopback Responder ..................................................................................... 8-5
Classifier Profiles ............................................................................................................... 8-6
Examples ....................................................................................................................... 8-7
Error Messages ............................................................................................................. 8-7
ETX-5300A Ver. 1.0
vii
Table of Contents
8.2
8.3
8.4
8.5
8.6
viii
Configuring Flows .............................................................................................................. 8-8

Examples ......................................................................................................................... 8-11
Multiple CoS Point-to-Point Service ............................................................................. 8-11
Multipoint Service ....................................................................................................... 8-16
Statistics .......................................................................................................................... 8-20
Ethertype ........................................................................................................................... 8-25
Benefits ........................................................................................................................... 8-25
Configuring Ethertype ...................................................................................................... 8-25
Example ........................................................................................................................... 8-25
Layer 2 Control Protocol (L2CP).......................................................................................... 8-26
Standards ........................................................................................................................ 8-26
Benefits ........................................................................................................................... 8-26
Adding Layer 2 Control Processing Profiles ...................................................................... 8-27
Deleting Layer 2 Control Processing Profiles .................................................................... 8-27
Configuring Layer 2 Control Processing Profile Parameters .............................................. 8-27
Example ........................................................................................................................... 8-28
Peer ................................................................................................................................... 8-29
Benefits ........................................................................................................................... 8-29
Configuring Remote Peers ............................................................................................... 8-29
Example ........................................................................................................................... 8-30
TDM Pseudowires ............................................................................................................... 8-31
Standards ........................................................................................................................ 8-31
Benefits ........................................................................................................................... 8-32
Pseudowire Packet Processing Subsystem ................................................................... 8-33
Jitter Buffer ................................................................................................................. 8-39
Packet Loss ................................................................................................................. 8-40
ToS ............................................................................................................................. 8-40
OAM Protocol .............................................................................................................. 8-40
Alarm Indications and Fault Propagation ..................................................................... 8-41
Adaptive Timing .......................................................................................................... 8-44
Configuring Pseudowires .................................................................................................. 8-45
Displaying PW Statistics ................................................................................................... 8-47
Clearing Statistics ............................................................................................................ 8-49
Viewing the Pseudowire Status and Summary .................................................................. 8-49
Example ........................................................................................................................... 8-50
Cross-Connection ............................................................................................................... 8-52
Benefits ........................................................................................................................... 8-52
Configuring Cross-Connection .......................................................................................... 8-53
ETX-5300A Ver. 1.0
8.7
8.8
8.9
Table of Contents
Examples ......................................................................................................................... 8-53

Cross-Connection ........................................................................................................ 8-53
Pseudowire Service ..................................................................................................... 8-54
Bridge ................................................................................................................................ 8-57
Standards ........................................................................................................................ 8-57
Benefits ........................................................................................................................... 8-57
Bridge Model ............................................................................................................... 8-58
VLAN Editing at Bridge Port Ingress and Egress ........................................................... 8-59
Deleting Bridge Elements ............................................................................................ 8-60
Configuring Bridge ........................................................................................................... 8-60
Displaying MAC Address Table .......................................................................................... 8-61
Displaying VLAN Information ............................................................................................ 8-62
Displaying Bridge Port Status ........................................................................................... 8-62
Example ........................................................................................................................... 8-63
Router ................................................................................................................................ 8-64
Standards ........................................................................................................................ 8-64
Benefits ........................................................................................................................... 8-64
Connection to Physical and Bridge Ports ..................................................................... 8-65
Management ............................................................................................................... 8-65
Loopback Router Interfaces ........................................................................................ 8-65
Routing and ARP Tables .............................................................................................. 8-66
Configuring Router ........................................................................................................... 8-66
Displaying ARP Table ........................................................................................................ 8-67
Displaying Routing Table .................................................................................................. 8-67
Displaying Interface Table ................................................................................................ 8-68
Displaying Router Interface Status ................................................................................... 8-68
Example ........................................................................................................................... 8-68
Quality of Service (QoS) ..................................................................................................... 8-74
Standards ........................................................................................................................ 8-74
Benefits ........................................................................................................................... 8-74
Traffic Management ......................................................................................................... 8-74
Shaper ........................................................................................................................ 8-75
Congestion Avoidance (WRED) .................................................................................... 8-76
Internal Queue ............................................................................................................ 8-78
Queue Block ................................................................................................................ 8-80
Queue Group............................................................................................................... 8-81
CoS Mapping .................................................................................................................... 8-84
Factory Defaults .......................................................................................................... 8-85
Configuring CoS Mapping ............................................................................................ 8-85
Example ...................................................................................................................... 8-85
Color Mapping .................................................................................................................. 8-86
Configuring Color Mapping .......................................................................................... 8-86
Example ...................................................................................................................... 8-86
ETX-5300A Ver. 1.0
ix
Table of Contents

Policing ............................................................................................................................ 8-87
Configuring Policer Profile ........................................................................................... 8-88
Configuring Policer Aggregate Profile .......................................................................... 8-88
Example ...................................................................................................................... 8-89
Marking ............................................................................................................................ 8-89
Configuring Color-Blind Marking Profile ....................................................................... 8-90
Configuring Color-Aware Marking Profile ..................................................................... 8-90
Example ...................................................................................................................... 8-90
Priority Queue Mapping ................................................................................................... 8-91
Example ........................................................................................................................... 8-91
8.10 Ethernet OAM .................................................................................................................. 8-101
Standards ...................................................................................................................... 8-101
Factory Defaults ............................................................................................................ 8-101
Functional Description ................................................................................................... 8-101
OAM Elements........................................................................................................... 8-101
OAM Functions .......................................................................................................... 8-102
OAM Connectivity ...................................................................................................... 8-102
MEPs and Services ..................................................................................................... 8-103
MIPs .......................................................................................................................... 8-106
Messaging System ..................................................................................................... 8-107
Performance Monitoring............................................................................................ 8-111
Configuring OAM ............................................................................................................ 8-111
Configuring Maintenance Domains ............................................................................ 8-112
Configuring Maintenance Associations ...................................................................... 8-113
Configuring Maintenance Endpoints .......................................................................... 8-113
Configuring Maintenance Intermediary Points ........................................................... 8-115
Configuring Maintenance Endpoint Services .............................................................. 8-117
Configuring Destination NEs ...................................................................................... 8-118
Displaying OAM Statistics .......................................................................................... 8-119
Performing OAM Loopback ........................................................................................ 8-121
Performing OAM Link Trace ....................................................................................... 8-121
Examples ....................................................................................................................... 8-122
Example 1. Down MEP between Main Card Ports ....................................................... 8-122
Example 2. Down MEP between Main and I/O Card Ports ........................................... 8-124
Example 3. Up MEP between Main Card and Bridge Ports .......................................... 8-128
Configuration Errors ....................................................................................................... 8-132
Chapter 9. Timing and Synchronization
9.1
Clock Selection ..................................................................................................................... 9-1

Benefits ............................................................................................................................. 9-1
Clock Domain ................................................................................................................ 9-3
SEC Module ................................................................................................................... 9-6
Input Sources ................................................................................................................ 9-8
Redundancy ................................................................................................................ 9-10
Configuring the Clock ....................................................................................................... 9-11
ETX-5300A Ver. 1.0
9.2
Table of Contents
Configuring the Clock Domain ..................................................................................... 9-12

Configuring the Clock Sources ..................................................................................... 9-14
Configuring Station Clock ............................................................................................ 9-18
Configuring Y-Cable Protection .................................................................................... 9-20
Example ...................................................................................................................... 9-21
1588v2 Timing ................................................................................................................... 9-23
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 Date and Time.................................................................................................................... 10-2
Benefits ........................................................................................................................... 10-2
Transport Protocol ...................................................................................................... 10-3
Client Operation Mode ................................................................................................ 10-3
Configuring Date and Time............................................................................................... 10-3
Displaying the Date and Time .......................................................................................... 10-4
Example ........................................................................................................................... 10-4
SNTP Configuration .......................................................................................................... 10-4
Defining SNTP Servers ................................................................................................. 10-5
Configuring SNTP Server Parameters ........................................................................... 10-5
Example ...................................................................................................................... 10-6
10.3 Inventory............................................................................................................................ 10-6
Displaying Inventory Information ..................................................................................... 10-6
Displaying Inventory Component Information .................................................................. 10-7
Displaying Manufacture Information ................................................................................ 10-7
Setting Administrative Inventory Information ................................................................... 10-8
Example ........................................................................................................................... 10-9
10.4 Downloading/Uploading Files ........................................................................................... 10-10
Example Download via SFTP ........................................................................................ 10-11
Example Upload via SFTP ............................................................................................. 10-11
10.5 Copying Files within ETX-5300A ....................................................................................... 10-11
File Names in the Unit.................................................................................................... 10-12
ETX-5300A Ver. 1.0
xi
Table of Contents
Displaying Files within ETX-5300A.................................................................................. 10-13

Displaying the List of Configuration Files and their Contents ......................................... 10-14
Example Displaying the List of Configuration Files .................................................. 10-15
Example Displaying the Contents of startup-config File .......................................... 10-15
Example Displaying the Contents of Application Files ............................................. 10-15
Deleting Files ............................................................................................................ 10-16
Saving the Configuration ........................................................................................... 10-16
10.6 Resetting ETX-5300A ....................................................................................................... 10-17
Resetting to Factory Defaults ........................................................................................ 10-17
Resetting to User Defaults ............................................................................................. 10-17
Rebooting the ETX-5300A Chassis ................................................................................. 10-17
Rebooting the Module ................................................................................................... 10-18
Chapter 11. Monitoring and Diagnostics
11.1 Detecting Problems ............................................................................................................ 11-1
Indicators......................................................................................................................... 11-1
Alarms and Traps ............................................................................................................. 11-1
Statistic Counters ............................................................................................................ 11-1
Configuration Error Messages .......................................................................................... 11-2
11.2 Handling Events ................................................................................................................. 11-2
Masking ........................................................................................................................... 11-2
Alarm Buffer .................................................................................................................... 11-3
Alarm Relays .................................................................................................................... 11-3
Configuring Alarm Reporting ............................................................................................ 11-4
Examples ..................................................................................................................... 11-5
Working with the Alarm and Event Logs ........................................................................... 11-6
Example 1: Displaying Active Alarms ............................................................................ 11-7
Example 2. Displaying Active Alarms Details ................................................................ 11-7
Example 3: Displaying Information of LOF alarm on SDH/SONET port .......................... 11-8
Example 4. Alarm Log .................................................................................................. 11-8
Example 5. Alarm List .................................................................................................. 11-9
Example 7. Displaying Brief Log ................................................................................. 11-10
Clearing Alarms ......................................................................................................... 11-10
Alarm List ...................................................................................................................... 11-10
Event List ....................................................................................................................... 11-14
Trap List......................................................................................................................... 11-19
11.3 Running Diagnostic Tests ................................................................................................. 11-26
Running a Ping Test ....................................................................................................... 11-26
Tracing the Route .......................................................................................................... 11-26
11.4 Technical Support ............................................................................................................. 11-27
Chapter 12. Software Upgrade
12.1 Impact ................................................................................................................................ 12-1
12.2 Software Upgrade Options ................................................................................................. 12-1
12.3 Prerequisites ...................................................................................................................... 12-1
Software Files .................................................................................................................. 12-2
System Requirements ...................................................................................................... 12-2
12.4 Upgrading Software using the CLI....................................................................................... 12-2
Using SFTP ....................................................................................................................... 12-2
Pinging the PC .................................................................................................................. 12-3
Activating the SFTP Server ............................................................................................... 12-3
Downloading the New Software Release File to ETX-5300A Flash Disk ............................ 12-3
xii
ETX-5300A Ver. 1.0
Table of Contents
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.5 Upgrading Software via the Boot Menu .............................................................................. 12-8
Starting Boot Manager ..................................................................................................... 12-9
Using the FTP Protocol ................................................................................................... 12-11
12.6 Verifying the Upgrade Results .......................................................................................... 12-13
12.7 Restoring the Previous Software Version.......................................................................... 12-18
Appendix A. Connection Data

Appendix B. Data Flow and Traffic Management
ETX-5300A Ver. 1.0
xiii
Table of Contents
xiv
ETX-5300A Ver. 1.0
Chapter 1
Introduction
1.1
Overview
ETX-5300A is a 10G Carrier Ethernet access platform for aggregating SLA-based

business Ethernet, legacy TDM and mobile backhaul services.
ETX-5300A 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) and E-LAN
(EPLAN, EVPLAN) services, ETX-5300A 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-5300A delivers high-quality E1/T1 and STM-1/OC-3 streams,
using Circuit Emulation Services (CES).
The ETX-5300A 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-5300A an ideal solution for LTE mobile backhaul applications.
Product Options
ETX-5300A 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.
In addition, the chassis is designed to receive power from AC and/or DC sources.
Applications
In a typical service aggregation application, ETX-5300A concentrates SLA-based
traffic coming from RADs 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-5300A Ver. 1.0
Overview
1-1
Chapter 1 Introduction

Copper
GbE
GbE
GbE
4/8 x E1/T1
Media
Converter
PSN
ETX-203AX,
ETX-36
FO
PE
ETX-205A
GbE
GbE
10GbE
ETX-2xxA
GbE/10GbE G.8032
Ring
GbE
ETX-5300A
TDM
STM-1/OC-3
ETX-2xxA
Figure 1-1. SLA-Based Service Aggregation

In a mobile backhaul application (Figure 1-2), carrier-owned ETX-5300A and ETX2xxA 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
Metro
Core
Aggregation
First Mile
ETX-5300A
PCRF
GbE
MME
DSLAM
ETX-5300A
GbE,
10GbE
P-GW
DSL
G.8023v2
10GbE Ring
BTS/Node B
TDM
G.8023v2
10GbE Ring
S-GW
RNC
ETX-203AM
ETX-5300A
BSC
GbE, 10GbE
ETX
TDM
BTS/Node B
Figure 1-2. Mobile Backhaul
Features
ETX-5300A 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, hardwarebased OAM and performance monitoring, carrier-grade service resiliency and
strong Timing over Packet capabilities, ETX-5300A represents a robust
multifunctional Ethernet service delivery platform.
Carrier-Class Layer 2 Aggregation Switch

The ETX-5300A 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-5300A Ver. 1.0
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-Access for reaching the service providers out-of-franchise subscriber

locations as part of providing an end-to-end service
2G, 3GPP and LTE transport.
The 3U modular system features high port density for space-restricted facilities,
delivering up to 120 Gbps of user throughput 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-5300A efficiently handles multi-priority traffic on a per-flow basis, with ultrahigh 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-5300A 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-5300A 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-5300A to perform OAM and PM
measurements in nanoseconds with maximum precision.
ETX-5300A 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-5300A Ver. 1.0
Overview
1-3
Service Resiliency and Protection

ETX-5300A 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),and 1+1 APS protection on the TDM ports. In addition,
ETX-5300A supports Ethernet Ring Protection Switching (ERPS) per G.8032v2.
Synchronization and Timing over Packet

Incorporating RADs 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-5300As 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-5300A 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, RADs carrier-class element management system, via an SNMPbased GUI.
ETX-5300A also supports a variety of access protocols, including CLI over Telnet,
SNMP, and TFTP. Incorporated security features include Secure Shell (SSH), Webbased Secure Socket Layer (SSL), SNMPv3, RADIUS and Terminal Access Controller
Access-Control System (TACACS+).
1.2
Physical Description
Figure 1-3 shows a general front view of an ETX-5300A chassis. The ETX-5300A
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.
1-4
ETX-5300A Ver. 1.0
Figure 1-3. ETX-5300A 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-5300A rear views, and identify the functions of the
various slots.
Main Cards
1
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
OUT
Power Inlet Cards

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

Module
Function
Maximum Chassis Capacity
E5-PIM/AC
Single port AC power input module (110240 VAC,

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

circuits and its timing subsystem
E5-FAN
Fan tray with eight fans and alarm relay port
E5-GBE-20
GbE card with20 GbE ports, SFP or UTP
E5-10GBE-2
10GbE card with2 10GbE ports
E5-cTDM-4
SDH/SONET card with 4 channelized STM-1/OC-3 ports
1.3
Functional Description
This section provides a functional description of the ETX-5300A system that

supplements the information above.
System Structure
The ETX-5300A 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-5300A system, in which:
1-6
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.
ETX-5300A Ver. 1.0
System modules (power inlets and AC power supplies, fan module) provide
DC or AC power to the system and cool the chassis.
4 x 10GbE
4 x 10GbE
Main Card
Main Card
Timing
Packet
Processor
Power
Timing
Common
Logic
Packet
Processor
Common
Logic
GbE, 10GbE or
SDH/SONET
I/O Card
Fans
ETX-5300A
Figure 1-5. High-Level Architecture of ETX-5300A
Main Card
The main card (E5-MC-4) performs three main functions:
ETX-5300A Ver. 1.0
Control functions:
Interfacing with the network management stations, supervision terminals,

and Telnet hosts.
Control of ETX-5300A system operation.
Storage of application software, which determines the capabilities and

features provided by the ETX-5300A.
Storage of configuration databases.
Collection of operational history (alarms, performance statistics, etc.).
1-7
10GbE interface function: E5-MC-4 card provides the interface to 10GbE

packet-switched networks for the ETX-5300A 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-5300A system, locked to user-selected internal or external sources.
Only one main card is required per ETX-5300A 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 ETX5300A 10GbE, system control and timing functions.
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.
The four 10GB ports of the standby card can be used without any limitation,
exactly as the active main card ports.
Only the active card communicates with the management station/terminal and
actively manages the ETX-5300A 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-6 illustrates main card block diagram.

Backplane
Bus
Power
4 x 10GbE
XFPs
Quad 10GbE
Physical
Interface
Packet
Processor
ToD/1 PPS
Timing
BITS/10 MHz
RS-232
CPU
10/100/1000BT
E5-MC-4 Card
Figure 1-6. E5-MC-4 Block Diagram

1-8
ETX-5300A Ver. 1.0
10GbE Interface
ETX-5300A main cards provide four interfaces (10GBase-SR, 10GBase-LR,
10GBase-ER) for full duplex connection to 10GbE packet-switched networks. The
card supports IP and Ethernet networks, and is capable of processing data at wire
speed.
Each 10GbE port of the module 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 of the E5-MC-4 cards
distribute synchronous Ethernet timing (master and slave mode).
Packet Processor
With 100 Gbps full duplex performance, the packet processor (PP) located on the
E5-MC-4 cards, serves as:
Main engine for point-to-point (E-Line), bridging (E-LAN) and routing (Layer3) forwarding schemes
Post-forwarding scheduler and shaper (see Figure 1-7, Figure 1-8 and
Figure 1-9)
Note
Hardware-based OAM utility.
For details on system architecture and traffic management techniques, see

Appendix B.
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 three queue group types:
Level-0 SEs
CIR
Shapers
SP 1
SP 2
CIR/EIR
Shapers
SP 3
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 2
WFQ 4
CIR
Shaper
WFQ 3
Up to 8
CIR
Shapers
Up to 8
WFQ 4
WFQ 5
WFQ 6
SP 1
SP 2
WFQ 7
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Figure 1-7. Type 1 Queue Group
ETX-5300A Ver. 1.0
1-9

Level-0 SEs
CIR
Shapers
Level-1 SEs
SP 1
CIR/EIR
Shapers
SP 2
WFQ 1
WFQ 2
CIR/EIR
Shapers
SP 3
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 383
WFQ 4
WFQ 384
Up to 384
Up to 384
Up to 64
WFQ 2
CIR
Shaper
Up to 64
WFQ 1
CIR
Shapers
WFQ 2
WFQ 63
SP 1
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
SP 1
WFQ 2
CIR/EIR
Shapers
CIR/EIR
Shapers
SP 2
Level-2 SE
SP 3
WFQ 1
SP4
WFQ 2
WFQ 383
CIR
Shaper
WFQ 384
Up to 768
Up to 768
Up to 64
Up to 64
WFQ 1
WFQ 2
SP 1
WFQ 63
WFQ 64
SP 2
SP 3
SP4
WFQ 383
WFQ 384

See Appendix B for detailed description of Ethernet services and traffic
management.
Timing Subsystem
See Timing Mechanism section below for detailed description of clocking schemes
supported by ETX-5300A.
1-10
ETX-5300A Ver. 1.0
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-5300A. This terminal can perform all
the ETX-5300A supervision and configuration functions, and in particular
the preliminary system configuration.
Telnet: by means of any host capable of IP communication with ETX5300A. 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-5300A.
SNMP: ETX-5300A 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-5300A supports automatic event notification to

user-specified Syslog servers in accordance with the Syslog protocol per
RFC 3164. ETX-5300A 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-5300A

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-5300A supports TACACS+ client application. The application provides
shell, system and command accounting.
ETX-5300A Ver. 1.0
Control of ETX-5300A system operation.
Storage of application software, which determines the capabilities and

features provided by the ETX-5300A. 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 userdefault). 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.
1-11
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-5300A 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-5300A 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.
Ethernet Service Cards

ETX-5300A 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-10 illustrates block diagram of the Ethernet I/O cards.
1-12
ETX-5300A Ver. 1.0
Backplane
Bus
Power
20 x GbE
SFPs/RJ-45s
or
2 x 10GbE XFPs
Physical
Interface
Packet
Processor
Timing
CPU
E5-GbE-20 or E5-10GbE-2 Card
Figure 1-10. E5-GbE-20 and E5-10GbE-2 Block Diagram
GbE and 10GbE Interfaces

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-11).
ETX-5300A Ver. 1.0
1-13

Level-0 SEs
SP 1
SP 2
SP 3
CIR
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-11. Pre-Forwarding Traffic Management
Timing Subsystem
See Timing Mechanism section below for detailed description of clocking schemes
SDH/SONET Card
The E5-cTDM-4 card operates as a quad-port SDH/SONET terminal multiplexer for
the ETX-5300A chassis that terminates STM-1/OC-3 links and their overhead. The
module 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). Figure 1-12 illustrates the
E5-cTDM-4 card block diagram.
1-14
ETX-5300A Ver. 1.0
Backplane
Bus
Power
4 x STM-1/OC-3
SFPs
SDH/SONET
Mapper/
Framer
TDM
Pseudowire
Processor
Timing
CPU
E5-cTDM-4
Figure 1-12. E5-cTDM-4 Block Diagram
STM-1/OC-3 Interfaces
The TDM interfacing subsystem provides interfaces to the TDM users equipment
or network. The physical STM-1/OC-3 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 interfaces for direct access to the
Synchronous Digital Hierarchy (SDH) transmission cores at the STM-1 level
(155.520 Mbps), and also handle the TDM traffic flow between ETX-5300A
internal E1 ports, and the SDH network. Total module capacity is 252 E1 data
streams.
E1/T1 mapping to STM-1 is performed using the G.707 mapping scheme:
ETX-5300A Ver. 1.0
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.
1-15
SONET Interface
SONET interface provides physical OC-3 interfaces for direct access to the
Synchronous Digital Hierarchy (SONET) transmission cores at the OC-3 level
(155.520 Mbps), and also handles the TDM traffic flow between ETX-5300A
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.
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-1/OC-3 interfaces is processed by the

framer to extract timing information and separate E1/T1 timeslots (the
framer creates an internal E1/T1 port, which is connected through the
mapper to the SDH/SONET link).
The resulting payload is provided to packet processor. The packet processor

converts the payload into packets suitable for transmission over the packetswitched 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-5300A uses the following payload encapsulation techniques during packet

processing:
Note
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 transfer

transparently a bit stream at the nominal port rate (2.048 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 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:
1-16
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.
ETX-5300A Ver. 1.0
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 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
ETX-5300A Ver. 1.0
1-17
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:
1-18
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 200 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.
ETX-5300A Ver. 1.0
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. To provide the best possible user experience the user can specify how
to handle packets under such transient conditions:
By specifying that the handling will be sensitive to delay, the user instructs
the receiving end to automatically reset the jitter buffer when the buffer
remains at its high value for a long time (this introduces a long delay). As a
result, some packets are discarded, but for voice applications and under
normal conditions, this results in negligible voice degradation.
By specifying that the handling will be sensitive to data, the user instructs the
receiving end to do nothing until eventually an under- or overrun occurs, or
conditions return to normal. This achieves the best possible data integrity
(error correction, or higher protocols, may sometimes compensate for the
resulting problems).
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 a user-specified 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-5300A.
ETX-5300A Ver. 1.0
1-19
Timing Mechanism
ETX-5300A 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-5300A 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-5300A timing
mechanism.
Main Card
10GbE
Ports
System
Clock
I/O
Clock 1
I/O
Clock 2
1588v2
(master)
T0
SEC
Mux
1588v2
(slave)
Station Clock
(BITS/GPS)
Station Clock
Output (T4)
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-13. Timing Mechanism

The timing system in ETX-5300A 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:
1-20
ETX-5300A Ver. 1.0
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-5300A clock domain can be configured to use timing information derived
from an STM-1, OC-3, 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-10GbE-2 or E5-GbE-20 support
Synchronous Ethernet (Sync-E) master and slave modes according to ITU-T
G.8261G.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 packetoriented and is considered to be more stable.
STM-1/OC-3 Ports
An Rx clock of any STM-1/OC-3 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 STM-1/OC-3 port can be locked to:
ETX-5300A 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 card can be extracted
and supplied to the main card clock selection mechanism (via backplane clock
bus). Moreover, ETX-5300A 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-5300A Ver. 1.0
Rx clock of the port
Adaptive clock.
1-21
External (BITS) Clock

The external clock interface has two functions:
Input for external (station) clock signal
Output for the ETX-5300A nodal clock. This output provides a convenient
means for distributing the ETX-5300A nodal clock signal to other equipment.
ETX-5300A recovers Building-Integrated Timing Supply (BITS) clock via the station
clock interface ports on E5-MC-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-5300A 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-5300A 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-5300A 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-5300A 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.
1-22
ETX-5300A Ver. 1.0
GPS Clock
ETX-5300A accepts GPS-based frequency and phase reference signal from GPS
units, using the following interfaces on the E5-MC-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.
1.4
System
Capacity
10GbE
Interface
Technical Specifications
Number of I/O Cards
Up to 4
Line Rate
120 Gbps
Max Throughput
100 Gbps, full duplex (100 Gbps ingress and 100 Gbps
egress)
Number of Ports
4 per E5-MC-4 card

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

10GBase-SR, 850 nm, 550m (1804 ft)
10GBase-LR, 1310 nm, 10 km (6.2 mi)
10Gbase-ER, 1550 nm, 40 km (24.8 mi)
GbE Interface
Maximum Frame
Size
12 kbytes (12284 bytes for I/O card ports)
Connector
LC
Number of Ports
20 per E5-cTDM-4 card
Transceiver Type
Fiber optic SFP:

1000BaseSX, multimode, 850 nm, autonegotiation,
flow control
1000BaseLX, single mode, 1300 nm, autonegotiation,
flow control
100BaseFX, full duplex only, flow control
ETX-5300A Ver. 1.0
1-23
Electrical Interface
10/100/1000BaseT, full duplex only, autonegotiation,

flow control, MDI-X
Maximum Frame
Size
12 kbytes
Connector
LC (fiber optic)
RJ-45 (electrical)
SDH/SONET
Interface
Number of Ports
4 per card
Physical Layer
SDH: ITU-T Rec. G.957

SONET: ITU-T Rec. G.703, Para. 12
Nominal Bit Rate
155.520 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
Ethernet
Forwarding
1-24
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
Transmit Clock
System, port Rx clock (loopback)
E1/T1 Transmit
Clock
System, port Rx clock (loopback), adaptive
Connector
LC
Forwarding
802.1D, 802.1Q, 802.1ad
Number of EVCs
4K
ETX-5300A Ver. 1.0
Traffic
Management
Number of Shaped
EVCs
384 (per network port)
Services
E-Line (EPL, EVPL), E-LAN (EPLAN, EVPLAN)
Compliance
MEF 9, MEF 14, MEF 22, MEF 26
QoS Mechanism
SP + WFQ
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
(1 kbps Granularity)
Indirectly-attached ports: 010 Gbps
CIR/EIR Resolution
(Actual Rate)
016.384 Mbps: 1 kbps

016.384 163.84 Mbps: 10 kbps
163.84 Mbps1.6384 Gbps: 100 kbps
1.638410 Gbps: 1 Mbps
Note: The actual rate is rounded down according to the

resolution.
CBS/EBS Range
(1 byte Granularity)
Indirectly-attached ports: 02 Mbytes
CIR/EIR Resolution
(Actual Value)
1 byte
Policer
Compensation
063 byte
Hierarchical
Scheduler
3-level
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
ETX-5300A Ver. 1.0
Queue Profiles
Up to 16K
Shaper Profiles
Up to 256
1-25
Bridge
Router
Pseudowire
Protection
Timing
1-26
Congestion Control
WRED
Mode
VLAN-aware, IVL
Number of Instances
Up to 32
Number of Ports
Up to 128 per bridge instance
Number of Broadcast
Domains
Up to 4K per system
Number of MAC
Table Entries
256K (max)
MAC Table Size
64 (default), 256, 512, 1024, 4094, 16384, userconfigurable per broadcast domain
MAC Address Aging
3003600 sec
Number of Router
Instances
Number of Interfaces
(RIFs)
Up to 128
Number of Routing
Table Entries
Up to 1K, static
Number of ARP Table

Entries
Up to 1000, dynamic
Number of TDM
Pseudowires
1344 (336 per E5-cTDM-4 card)
Payload
Encapsulation
CESoPSN, SAToP
Network
Encapsulation
UDP/IP, MEF-8
Chassis
E5-MC-4 card, E5-PIM card
E5-cTMD-4 Card
1+1 unidirectional APS per G.841
E5-MC-4, E5-GBE-20
Cards
LAG, Ethernet Ring Protection per G.8032
Number of Clock
Domains
1 (master and fallback)
ETX-5300A Ver. 1.0
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.8261G.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
MEPs/MIPs
Up to 4K (512 MIPs)
Up to 1 Down MEP per MA

Up to 88 Up MEPs per MA
Up to 1K MEPs with LM
Up to 1K MEPS with DM
ETX-5300A Ver. 1.0
Number of PM
Services per MEP
1 (per predefined P-bit)
Number of RMEPs
Up to 8K MEP-RMEP pairs per shelf with up to 512 RMEPs

per MEP
1-27
Diagnostics
Management
SDH/SONET, E1/T1
User-activated loopback, inband T1, BERT
IP Connectivity
Ping, trace route
Management
Capabilities
Supervision terminal
Telnet
SSH
SNMP (RADview-EMS and other SNMP-based network
management stations)
Management Utility
CLI
SNMP Management
Capabilities
SNMPv1, SNMPv2, SNMPv3
Management
Interfaces
Serial ports on main card

10/100/1000BaseT port on main card, supports
Telnet, SSH, and SNMP
Inband via network or user ports, supports for Telnet,
SSH, and SNMP
Serial Control Port

Characteristics
Interface: RS-232 asynchronous DCE

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
Ethernet
Management Port
Interface 10/100/1000BaseT
Duplex mode Full duplex only.
Default maximum capability 100 Mbps full duplex.
Autonegotiation, MDI-X, no flow control
Maximum frame size 1518 bytes
Connector RJ-45
Alarm
Collection and
Monitoring
Alarm Relay
Alarms
Last 256 time-stamped alarms stored in buffer

Alarm synchronization, correlation, severity indication,
masking
RMON
RFC 2819
Syslog
RFC 3164
Alarm Outputs
Major alarm indication by floating change-over drycontact contacts

Minor alarm indication by floating change-over contacts
1-28
ETX-5300A Ver. 1.0
Output Contact
Ratings
Max. 60 VDC/30 VAC across open contacts

Max. 1 ADC through closed contacts
Max. load switching capacity: 60W
Indicators
External Alarm Input
One active-low input, RS-232 levels
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-10GBE-2
LINK (green) 10GbE link status

ACT (yellow) 10GbE activity status
E5-GBE-20
LINK (green) 10GbE link status

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

LOS (red) Loss of synchronization is detected
Power
ETX-5300A Ver. 1.0
AC Power
100 to 240 VAC (115/230 VAC nominal), 50/60 Hz
DC Power
4072 VDC (48 or 60 VDC nominal)
1-29
Physical
Environment
Power Consumption
500W max
Width
440 mm (17.3 in)
Height
133 mm (5.2 in), 3U
Depth
380 mm (15.0 in) DC, 455 mm (23.6 in) AC/DC
Weight
12 kg (26.4 lb), maximum
Temperature
Operating: 0 to 50C (32 to 122F)

Storage: -20 to +70C (0 to 150F)
1-30
Humidity
0 to 93%, non-condensing
Cooling
Internal fan tray
ETX-5300A Ver. 1.0
Chapter 2
Installation and Setup
This chapter provides installation instructions for the ETX-5300A 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.
Safety
Before starting, read the following safety precautions, which are applicable
throughout the installation procedures. Where necessary, specific precautions
also appear before certain procedures.
Warning
ETX-5300A Ver. 1.0
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
precautions during installation, operation, and maintenance of this product.
Site Requirements and Prerequisites
2-1
Chapter 2 Installation and Setup
Caution Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the ETX-5300A cards. To prevent physical damage:
Always keep cards in their protective packaging until installed in the
ETX-5300A 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
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-5300A case must be properly
grounded (earthed) at any time. Any interruption of the protective (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-5300A and its cards.
Warning
Never connect cables to ETX-5300A if not properly installed and grounded.

Disconnect all the cables connected to the electrical connectors of the
ETX-5300A 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-5300A rear panel.
Whenever ETX-5300A 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
ETX-5300A Ver. 1.0
Laser Safety
Warning
ETX-5300A 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.
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-5300A 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-5300A 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-5300A 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.
ETX-5300A Ver. 1.0
2-3
Caution ETX-5300A 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.
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-5300A 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.1
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-5300A 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-5300A can be equipped with either AC or DC power inlet (PI) modules, which
conduct power from external sources to the ETX-5300A backplane. There are two
PI module types:
2-4
DC for 4072 VDC (48 or 60 VDC nominal), up to 12A current
AC for 100240 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-5300A Ver. 1.0
ETX-5300As with AC power supplies can be powered via any combination of PI

cards: 2 AC, AC and DC, 2 DC.
ETX-5300A 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.
AC Power
AC-powered ETX-5300A 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-5300A power inlets. Powering AC power supply modules one
at a time may cause undesirable effects.
DC Power
DC-powered ETX-5300A 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-5300A, the DC input supply lines are not referenced to the chassis
(frame) ground.
Panel Clearance
ETX-5300A 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
ETX-5300A Ver. 1.0
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.
2-5
Ambient Requirements
The ambient operating temperature range of the ETX-5300A is 32 to 122F
(0 to +50C), at a relative humidity of up to 93%, non-condensing.
Caution Do not operate ETX-5300A 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-5300A 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-5300A 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.2
Package Contents
The ETX-5300A package includes the following items:
ETX-5300A 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.3
Required Equipment
The cables needed to connect to ETX-5300A 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-5300A Ver. 1.0
2.4 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.5 Installing the ETX-5300A Enclosure

The ETX-5300A 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-5300A. 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-5300A Ver. 1.0
Installing the ETX-5300A Enclosure
2-7
Installing ETX-5300A 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-GMUX-5300/3U/19/FRONT, for front-edge installation in 19 racks
RM-GMUX-5300/3U/23/FRONT, for front-edge installation in 23 racks
RM-ETX-5300-3U-23-NEBS, 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-GMUX-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-GMUX-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-NEBS kit for mid-chassis installation in 23 racks.
2-8
ETX-5300A Ver. 1.0
Figure 2-4. Attaching of Brackets for Mid-Chassis Installation in 23 Racks

Note
Mid-chassis fitting, using the RM-ETX-5300-3U-23-NEBS kit, meets the

requirement 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 ETX5300A devices in 19 racks.
AC power supplies increase the units depth and weight. Installation of
AC-powered ETX-5300A 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-5300A in the rack:

1. Identify the prescribed position of each ETX-5300A in the rack, in accordance
with the rack installation plan.
2. With help from an additional person, place ETX-5300A 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-5300A in position
until it is fastened to the rack with the screws.
ETX-5300A Ver. 1.0
2-9
3. While the other person holds ETX-5300A 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 ETX-5300A units.
Figure 2-6. Full Rack Installation
2.6
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.
2-10
Installing a Fan Tray
ETX-5300A Ver. 1.0
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
I
L
T
E
R
PS-B
MAIN-B
MAIN-A
PS-A F
A
I/O 2
I/O 4 N
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-5300A 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).
2.7
Installing Power Inlet Modules
The connection of power to the ETX-5300A power supply modules is made

through hot-swappable PI modules. Figure 2-8 and Figure 2-9 show the offered PI
modules. Chapter 3 describes the PI module indicators. DC connector pinout is
given in Appendix A.
ETX-5300A Ver. 1.0
Installing Power Inlet Modules
2-11
E5-PIM
PWR
FLT
Figure 2-8. Power Inlet Module for DC Input

E5-PIM
PWR
FLT
Figure 2-9. Power Inlet Module for AC Input
E5-PIM/AC Module
The E5-PIM/AC module is used for connecting to 100240 VAC power sources. The
E5-PIM/AC can be used only in ETX-5300A 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 4072 VDC (48 VDC nominal)
power sources.
Installing PI Modules
Caution ETX-5300A units with AC power supplies can be powered via any combination of
PI cards: 2 AC, AC and DC, 2 DC. ETX-5300A 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.
2.8
Installing the Main Card
The ETX-5300A 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-10 shows the front panel of the main card. Chapter 3 explains the
functions of the indicators located on the panel.
1
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
E5-MC-4
LINK
ACT
OUT
GPS
TOD
MNG
1PPS
10MHz
MNG ETH
LINK ACT
10/100/1000BASE-T
CONTROL
DCE
PRI
FLT
CLK
RMV
Figure 2-10. Main Card Panel
2-12
ETX-5300A Ver. 1.0
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-11.
1P
P
10
M
Hz
10
NG
ET
H
MN
G
CO
LI N
K
/1 0
0 /1
AC
T
00
NT
RO
L
PR
I
0B
AS
E
-T
DC
E
FL
T
CL
K
RM
2
3
1
Figure 2-11. 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-11) 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-11) snap into place.
6. Secure the main card by tightening its two screws.
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-11) of the locking levers to
disengage locking hooks (item 2 in Figure 2-11) 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.
ETX-5300A Ver. 1.0
2-13
Replacing a Main Card during Equipment Operation

ETX-5300A Chassis with two CONTROL Modules
In an ETX-5300A equipped with two functional main cards, the standby card can
be removed/replaced without disrupting ETX-5300A services.
If you replace the on-line main card, ETX-5300A 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-5300A
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-5300A 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-5300A Chassis with Single Main Card

In an ETX-5300A 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 ETX5300A with two main cards.
When replacing a single main card in the chassis, ETX-5300A 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-14
ETX-5300A Ver. 1.0
2.9 Connecting to Power
Warning
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
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-5300A 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-5300A 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-5300A 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:
Note
Connect each power cable first to the connector on the E5-PIM/AC module,
and then to the power outlet.
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.
ETX-5300A Ver. 1.0
Connecting to Power
2-15
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.
PW
R
F LT
4 8/
6 0V
E5
eL
ti v
a
g
Ne
-PI
M
d
ea
s
Po
e
iti v
ad
Le
Figure 2-12. Connection to E5-PIM/DC Terminals
2.10 Installing I/O Cards

The ETX-5300A chassis can be equipped with up to four hot-swappable I/O
(service) cards.
Figure 2-10 shows the front panel of the main card. Chapter 3 explains the
functions of the indicators located on the panel.
2-16
Installing I/O Cards
ETX-5300A Ver. 1.0

20
FLT
11
LINK
ACT
1
E5-GBE-20
RMV
100/1000BASE-X
Figure 2-13. E5-GBE-20 Card Panel

1
10GbE
FLT
RMV
LINK
ACT
LINK
ACT
E5-10GBE-2
Figure 2-14. E5-10GBE-2 Card Panel

FLT
LINK 1
FLT
OC-3/STM-1
FLT
LINK 2
LINK 3
FLT
20
FLT
LINK 4
RMV
E5-cTDM-4
LOS
LOS
LOS
LOS
Figure 2-15. E5-cTDM-4 Card Panel
To install an I/O card:
Follow the procedure for main cad installation to install each I/O module in
the prescribed I/O slot, in accordance with the installation plan.
2.11 Installing Blank Panels

Install blank panels in all the chassis slots that are not occupied by modules.
2.12 Installing SFP or XFP Modules

ETX-5300A uses SFP (GbE and STM-1/OC-3 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
To install the SFP or XFP modules:

1. Lock the wire latch of each SFP or XFP module by lifting it up until it clicks
into place, as illustrated in Figure 2-16.
Note
ETX-5300A Ver. 1.0
Some SFP or XFP models have a plastic door instead of a wire latch.
Installing SFP or XFP Modules
2-17
Figure 2-16. Locking the SFP Wire Latch

2. Carefully remove the dust covers from the SFP or XFP slot.
3. Insert the rear end of the SFP or XFP into the socket, and push it in slowly
until the 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 or XFP modules.
To remove the SFP or XFP module:

1. Disconnect the fiber optic cables from the SFP module.
2. Unlock the wire latch by lowering it downwards (as opposed to locking).
3. Hold the wire latch and pull the SFP or XFP module out of the port.
Caution Do not remove the 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.13 Connecting to 10Gb Ethernet Equipment

ETX-5300A is connected to 10Gb Ethernet equipment via the fiber optic XFP
transceivers with LC ports located on E5-MC-4 or E5-10GBE-2 cards. These ports
are designated 10GbE.
Figure 2-17 and Figure 2-18 illustrate typical E5-MC-4 and E5-10GBE-2 cards with
10GbE ports.
To connect to 10GbE equipment
2-18
Connect ETX-5300A to the 10GbE equipment at providers edge or customer

premises using standard fiber optic cables terminated with LC connectors.
Connecting to 10Gb Ethernet Equipment
ETX-5300A Ver. 1.0
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
OUT
GPS
TOD
MNG
1PPS
10MHz
ACT
E5-MC-4
MNG ETH
CONTROL
DCE
LINK ACT
10/100/1000BASE-T
PRI
FLT
CLK
RMV
Figure 2-17. 10GbE Ports on E5-MC-4 Card

1
10GbE
FLT
RMV
LINK
ACT
LINK
ACT
E5-10GBE-2
Figure 2-18. 10GbE Ports on E5-10GBE-2 Card
2.14 Connecting to Gigabit Ethernet Equipment

ETX-5300A 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-19 and Figure 2-20 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-5300A to the Gigabit Ethernet equipment at customer premises

using standard fiber optic cables terminated with LC connectors.
20
FLT
11
LINK
ACT
1
E5-GBE-20
RMV
100/1000BASE-X
Figure 2-19. Fiber Optic GbE Ports on E5-GBE-20 Card
To connect to Ethernet equipment with a copper interface:
Connect ETX-5300A to the Gigabit Ethernet equipment at customer premises

using standard straight UTP cables terminated with RJ-45 connectors.
LINK
11
1
E5-GBE-20
ACT
FLT
RMV
10/100/1000BASE-T
Figure 2-20. Electrical GbE Ports on E5-GBE-20 Card
2.15 Connecting to STM-1/OC-3 Equipment

ETX-5300A 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-21 illustrates typical E5-cTDM-4 cards with STM-1/OC-3 ports.
ETX-5300A Ver. 1.0
Connecting to STM-1/OC-3 Equipment
2-19
To connect to STM-1/OC-3 equipment
Connect ETX-5300A to STM-1/OC-3 equipment at customer premises using

standard fiber optic cables terminated with LC connectors.
FLT
LINK 1
FLT
OC-3/STM-1
FLT
LINK 2
LINK 3
FLT
20
FLT
LINK 4
RMV
LOS
E5-cTDM-4
LOS
LOS
LOS
Figure 2-21. STM-1/OC-3 Ports on E5- cTDM-4 Card
2.16 Connecting to External Clock Devices

ETX-5300A supports station clock input and output via balanced RJ-45 or
unbalanced BNC ports on E5-MC-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 E5-MC-4 card designated EXT CLK. (RJ-45 on E5-MC-4 card uses
different pins for clock input and output.)
ACT
LINK
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
OUT
GPS
TOD
ACT
MNG
1PPS
MNG ETH
CONTROL
10MHz
LINK ACT
10/100/1000BASE-T
DCE
E5-MC-4
PRI
FLT
CLK
RMV
Figure 2-22. EXT CLK Port on E5-MC-4 Card
To connect to external clock devices with unbalanced interface:
LINK
Use two 75 coaxial cables to connect the external clock source and/or slave
clock device to the two BNC connectors on the E5-MC-4 card designated IN
(input) and OUT (output).
2
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
ACT
E5-MC-4
OUT
GPS
TOD
MNG
1PPS
MNG ETH
CONTROL
10MHz
LINK ACT
10/100/1000BASE-T
DCE
PRI
FLT
CLK
RMV
Figure 2-23. IN and OUT Ports on E5- MC-4 Card
2.17 Connecting to GPS Clock Devices

ETX-5300A supports GPS-based Time of Day (ToD) clock input and output via
RS-422 RJ-45 port on E5-MC-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 E5-MC-4 card designated 1PPS and 10MHz, respectively.
2-20
Connecting to GPS Clock Devices
ETX-5300A Ver. 1.0
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 E5-MC-4 card designated TOD. (RJ-45 TOD connector
on E5-MC-4 card uses different pins for clock input and output.)
1
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
OUT
GPS
TOD
MNG
1PPS
10MHz
ACT
E5-MC-4
MNG ETH
CONTROL
LINK ACT
10/100/1000BASE-T
DCE
PRI
FLT
CLK
RMV
Figure 2-24. TOD Port on E5-MC-4 Card

To connect to 1 PPS and 10 MHz GPS clock devices:
ACT
LINK
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 on the E5-MC-4 card designated IN (input) and OUT (output).
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
OUT
GPS
TOD
MNG
1PPS
10MHz
ACT
E5-MC-4
MNG ETH
CONTROL
LINK ACT
10/100/1000BASE-T
DCE
PRI
FLT
CLK
RMV
Figure 2-25. 1PPS and 10MHz Ports on E5-MC-4 Card
2.18 Connecting to a Terminal

ETX-5300A is connected to an ASCII terminal via a 9-pin D-type female connector
on the E5-MC-4 card designated CONTROL DCE. Refer to Appendix A for the
connector pinout.
1
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
ACT
E5-MC-4
OUT
GPS
TOD
MNG
1PPS
10MHz
MNG ETH
LINK ACT
10/100/1000BASE-T
CONTROL
DCE
PRI
FLT
CLK
RMV
Figure 2-26. 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 connector on the
E5-MC-4 card.
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.
ETX-5300A Ver. 1.0
Connecting to a Terminal
2-21
2.19 Connecting to a Network Management Station

ETX-5300A is connected to a network management workstation via a dedicated
8-pin RJ-45 copper connector on the E5-MC-4 card designated MNG-ETH.
1
LINK
ACT
LINK
10GbE
ACT
LINK
EXT CLK
EXT CLK
IN
ACT
LINK
GPS
TOD
OUT
MNG
1PPS
10MHz
ACT
E5-MC-4
MNG ETH
LINK ACT
10/100/1000BASE-T
CONTROL
DCE
PRI
FLT
CLK
RMV
Figure 2-9 MNG-ETH Port on E5-MC-4 Card
To connect to a network management station:
Connect ETX-5300A to network management station using a standard

straight or cross UTP cable terminated with an RJ-45 connector.
2.20 Connecting to an External Alarm Device

ETX-5300A 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
I
L
T
E
R
PS-B
MAIN-B
MAIN-A
PS-A F
A
I/O 2
I/O 4 N
I/O 1
I/O 3
E5-FAN
Figure 2-9 ALARM Port on E5-FAN Card
2.21 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-22
Labeling Cable
ETX-5300A Ver. 1.0
Chapter 3
Operation
This chapter provides general operating instructions and preliminary configuration
instructions for ETX-5300A units.
This chapter covers the following topics:
Turning On the Unit
Indicators
Startup
Using a Custom Configuration File
Saving Configuration Changes
Confirming the Configuration File
Handling Configuration File Errors
Turning Off the Unit.
3.1
Turning On the Unit
When turning on the ETX-5300A, it is useful to monitor the power-up sequence.
Caution
To turn on ETX-5300A:
ETX-5300A does not have a power on/off switch, and will start operating as soon
as power is applied.
For an ETX-5300A 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-5300A 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-5300A is powered.
You may also hear the fans in the ETX-5300A 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:
ETX-5300A Ver. 1.0
After power is applied, all the ETX-5300A 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-5300A performs its power-up initialization.
Turning On the Unit
3-1
Chapter 3 Operation
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-5300A performs the startup procedure. See the Startup section
below.
4. After startup ends, you may log in, using the supervision terminal.
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-5300A LED indicators.
Table 3-1. ETX-5300A 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

detected
OFF No hardware, software or power fault has been
detected
E5-PIM, E5-FAN,
E5-MC-4,
E5-10GBE-2,
E5-GBE-20,
E5-cTDM-4
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,
E5-10GBE-2,
E5-GBE-20,
E5-cTDM-4
ON Card can be safely extracted from chassis, after it

has been administratively shut down
OFF Hardware, software or power failure
PRI
Green
ON Main card is primary
E5-MC-4
Blinking Main card is secondary

CLK
Red
ON Station clock is configured, but is not synchronized
E5-MC-4
OFF Station clock is not configured, or station clock is

configured and synchronized
LINK
Green
ON Ethernet interface has been connected
E5-MC-4,
E5-10GBE-2,
E5-GBE-20
ACT
Yellow
ON Data is being transmitted/received at the Ethernet

interface
E5-MC-4,
E5-10GBE-2,
E5-GBE-20
3-2
Indicators
ETX-5300A Ver. 1.0
Chapter 3 Operation
Name
Color
Function
Location
ON LINE
Green
ON Card is administratively enabled
E5-cTDM-4
LOS
Red
ON Loss of signal has been detected
E5-cTDM-4
Blinking Other signal failure (LOF, AIS, RFI etc) has been
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.
Caution Always wait until all main cards installed in the chassis are up and running before
executing any file operation commands.
Note
ETX-5300A Ver. 1.0
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.
Startup
3-3
Chapter 3 Operation
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
Pass
Boot from
Startup-config
Sanity
Check
Yes
Startup-config exist?
Fail
Boot from
User-default-config
Pass
Sanity
Check
No
Yes
User-default-config
exist?
Fail
No
Boot from
Factory-default-config
End
Figure 3-2. Loading Sequence
3-4
Startup
ETX-5300A Ver. 1.0
3.4
Chapter 3 Operation
Using a Custom Configuration File
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 providers 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.
3.5
Saving Configuration Changes
The save command is used to save the running configuration in startup-config.

Some commands reset the device, and also erase the configuration saved in
startup-config by copying another file to it before the reset. Figure 3-1 indicates
the commands that copy to startup-config, and whether the device resets after
copying.
Figure 3-3. Commands That Reset Device/Copy Configuration Files
3.6
ETX-5300A 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-confirmrequired command, ETX-5300A copies running-config or any other user-specified
ETX-5300A Ver. 1.0
3-5
Chapter 3 Operation
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
confirmation of configuration
file after reboot
startup-confirm-required [time-toconfirm <165535>] [rollback {startupconfig | user-default-config | factorydefault-config | running-config}]
Default time-to-confirm
5 min.
no startup-confirm-required
You can define any

configuration file to be a
source for your rollback-config
file.
The default option is runningdefault, which is guaranteed to
maintain management
connectivity, as it is the
configuration currently run by
the user.
no before startup-confirmrequired cancels the previously
enabled startup-config
confirmation.
3.7
Handling Configuration File Errors
By default, ETX-5300A 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.8
To power off the unit:
3-6
Turning Off the Unit
Remove the power cord from the power source.
Turning Off the Unit
ETX-5300A Ver. 1.0
Chapter 4
Management and Security
This chapter provides general operating instructions and preliminary configuration
instructions for ETX-5300A units.
This chapter presents the following information:
Terminal Control Port
User Access
SNMP Management
Management Access
Access Policy
Authentication via RADIUS Server
Authentication via TACACS+ Server
Syslog
Programming Cards.
Table 4-1 summarizes management alternatives for ETX-5300A.

Table 4-1. Management Alternatives
Port
Manager
Location
Transport Method
Management
Protocol
Application
Control
Local
Out-of-band
RS-232
Terminal emulation programs

(HyperTerminal, Procomm,
SecureCRT, Putty). See Working
with Terminal below.
Ethernet
Local, remote
Inband, out-of-band
Telnet, SSH
Procomm, SecureCRT, Putty (see
Working with Telnet and SSH

below)
SNMP
RADview (see Working with

RADview below)
3rd-party NMS (see Working with
3rd Party Network Management

Systems below)
Note
ETX-5300A Ver. 1.0
By default, terminal, Telnet (SSH) and SNMP management access methods are
enabled.
CLI-Based Configuration
4-1
Chapter 4 Management and Security
4.1
Working with Terminal

ETX-5300A 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 cards. The
control port continuously monitors the incoming data stream and immediately
responds to any input string received through this port.
The ETX-5300A 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-5300A 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-5300A 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-5300A#
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
configuration, you can use a Telnet host connected to it directly or via a local
area network.
4-2
ETX-5300A Ver. 1.0
To configure router interface 1 for management:

1. Define IP address of RIF 1
2. Enable management access for RIF 1
3. Enable RIF 1.
ETX-5300A#
ETX-5300A# configure
ETX-5300A>config# router 1
ETX-5300A>config>router(1)# interface 1
ETX-5300A>config>router(1)interface(1)# address 1.1.1.1/1
ETX-5300A>config>router(1)interface(1)# management-access allow-all
ETX-5300A>config>router(1)interface(1)# no shutdown
By default, ETX-5300A has Telnet and SSH access enabled.
Login
To prevent unauthorized modification of the operating parameters, ETX-5300A
supports three access levels.
Superuser can perform all the activities supported by the ETX-5300A

management facility.
Users have read-only access, they cannot change any settings.
Techs (technicians) read-only access, but the technicians are allowed to

reset the unit, set its parameters to defaults and use TFTP download/upload.
The su, user and tech are permanent users, they cannot be removed from the
authorization database. The su level users can define new dynamic users and
assign access levels (su, user or tech) to them.
To enter as a superuser:
1. Enter su for user name.
2. Enter 1234 for password.
To enter as a user:
1. Enter user for user name.
To enter as a technician:
1. Enter tech for user name.
Using the CLI

The CLI consists of commands organized in a tree structure, starting at the base
prompt ETX-5300A#. The base prompt is the device name, which can be
configured in the system level (refer to Configuring Device Information in
Chapter 4). By default the device name is ETX-5300A.
ETX-5300A Ver. 1.0
4-3
Commands that are not global are available only at their specific tree location. To
find out what commands are available at the current location, type ?. For a list of
the commands and their levels, refer to Command Tree.
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location, followed by #. To navigate up, use the global command
exit. To navigate 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 has not changed.
ETX-5300A#
ETX-5300A# configure port e1 1/1/1 loopback local 1
ETX-5300A#
Figure 4-1. Commands Without Level Navigation

In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX-5300A#
ETX-5300A>config# port
ETX-5300A>config>port# e1 1/1/1
ETX-5300A>config>port>e1(1/1/1)# loopback local
ETX-5300A>config>port>e1(1/1/1)#
Figure 4-2. Commands With Level Navigation

Note
Level names are abbreviated in the prompt.

You can type only as many letters of the level or command as required by the
system to identify the level or command, for example you can enter config manag
to navigate to the management level.
In addition to being the default prompt, the # symbol also indicates a static entity
(such as a port) or already configured entity. The $ symbol indicates a new
dynamic entity (such as a flow) that takes several commands to configure. The
dynamic entity is created as inactive. After the configuration is completed, it is
activated by using the no shutdown command, as shown in the following
example.
4-4
ETX-5300A Ver. 1.0
ETX-5300A#
ETX-5300A# configure flows flow flow1
ETX-5300A>config>flows>flow(flow1)$ ingress-port ethernet 1/3
ETX-5300A>config>flows>flow(flow1)$ egress-port ethernet 1/1 queue 1 block 0/1
ETX-5300A>config>flows>flow(flow1)$ classifier Classifier1
ETX-5300A>config>flows>flow(flow1)$ no shutdown
ETX-5300A>config>flows>flow(flow1)$exit
ETX-5300A>config>flows#
Figure 4-3. Creating and Activating a Flow

The shutdown command is also used to deactivate/disable a hardware element
(such as a port), while no shutdown enables/activates it.
CLI commands have the following basic format:
command [parameter]{ value1 | value2 | | valuen }
[ optional parameter <value> ]
where:
{}
Indicates that one of the values must be selected
[]
Indicates an optional parameter
<>
Indicates a value to be typed by user according to

parameter requirements
The following keys are available at any time:

?
Lists all commands available at the current level
<Tab>
Command autocomplete
Displays the previous command
Displays the next command
<Backspace>
Deletes character
<Ctrl-C>
Interrupts current command
<Ctrl-Z>
Logs out
CLI commands can be gathered into text files called scripts. They can be created
using a text editor, by recording the user commands or by saving the current
configuration. The scripts can be imported from and exported to RAD devices via
file transfer protocols.
Command Tree
At the CLI root, the following categories are available:
ETX-5300A Ver. 1.0
admin
configure
debug
file
logon
on-configuration-error
4-5
rados-versions
Each category is detailed in the tables below.
Table 4-2. Global Commands

Command
Description
copy
Copies files within device or uploads/downloads files

to/from remote locations
echo
Displays a line of text (command) on the screen
exit
Returns to the next higher command level (context)
exit-remote
Returns from the remote commands context to the host

commands tree
help
Displays information regarding commands in the current

level
history
Displays the history of commands issued since the last

restart
info
Displays the current device configuration
level-info
Displays the current device configuration (commands from

the current level only)
logout
Logs the device off
ping
Issues ping request to verify reachability of remote host
save
Saves current settings
software-confirm
Confirms newly installed software
startup-config-confirm
Confirms configuration file
trace-route
Checks the path connectivity to a remote device
tree
Displays the command levels from the current context

downwards
Table 4-3. Commands in the admin Category

Command
Description
admin
Administrative commands
factory-default
Loads factory default configuration
factory-default-all
Resets all configuration and counters
reboot
Reboots the device
software
Software installation
install
Instructs the device to run from another sw-pack (upgrade)
software-confirm-required
Requires user confirmation after reboot
show status
Displays status of upgrade process
4-6
ETX-5300A Ver. 1.0
Command
Description
Aborts the upgrade process the return to previous sw-pack

(downgrade)
startup-confirm-required
Requires user confirmation after reboot
user-default
Loads user default configuration
undo-install
Table 4-4. Commands in the configure Category

Command
Description
configure
Device configuration commands
bridge
Defines bridge parameters
aging-time
Defines aging time for the MAC table entries
clear-mac-table
Clear addresses from the MAC table
show mac-address-table
Displays MAC addresses; adds/removes static MAC address
port
Defines the behavior and attributes of bridge ports
bind
Binds the bridge port to an SVI
name
Defines the bridge port name
shutdown
Administratively enables/disables the bridge port
show status
Displays the bridge port status
vlan
Enables/disables VLAN membership
maximum-mac-addresses
Defines maximum number of supported MAC addresses
name
Specifies VLAN name
tagged-egress
Adds/remove the bridge port as VLAN egress tagged member
show vlans
show cards-summary
Displays status of product slots
chassis
Chassis configuration and status
inventory
Specifies device inventory parameters
alias
Assigns/removes an alias entity name
asset-id
Specifies/removes an asset identifier
serial-number
Enters/removes the serial number of entity
show status
Displays the status of inventory item
show summary-inventory
Displays a list with installed hardware and software
show manufacture-info
Chassis and card production information
cross-connect
Pseudowire cross-connect
TDM PW cross connect configuration
fault
pw-tdm
ETX-5300A Ver. 1.0
Displays VLAN members
OAM threshold parameters
4-7
Command
Description
cfm
Configures OAM CFM thresholds
service
Configures OAM CFM service thresholds
frames-report
OAM CFM service event reporting
shutdown
Enables/disables event reporting for OAM service
flows
Flow parameters
classifier-profile
Defines classifier profile
Creates matching criteria
flow
Configures a specific flow
classifier
Assigns classifier profile to the flow
clear-statistics
Clears flow statistics
cos-mapping
Assigns CoS mapping profile to the flow, or fixed CoS

mapping value
drop
Commands to discard traffic transmitted via the flow
egress-port
Defines egress port of the flow
ingress-color
Assigns color mapping profile to the flow, or fixed color value
ingress-port
Defines ingress port of the flow
l2cp profile
Assigns L2CP profile to the flow
mark
Defines marking action for the flow
inner-marking-profile
Overwrites inner P-bit according to marking profile
inner-tag-ether-type
Overwrites inner TPID with a new value
inner-vlan
Overwrites inner VLAN ID with a new value
marking-profile
Overwrites P-bit according to marking profile
tag-ether-type
Overwrites TPID with a new value
vlan
Overwrites VLAN ID with a new value
p-bit
Overwrites P-bit with a new value
inner-p-bit
Overwrites inner P-bit with a new value
pm-collection
Enables/disables statistic data collection
policer
Assigns policer profile to the flow
policer aggregate
Assigns policer aggregate to the flow
rate-sampling-window
Defines window size for sampling flow rate statistics
shutdown
Administratively enables/disables the flow
show statistics
Display flow statistics
show status
Display flow status
vlan-tag push vlan
Pushes VLAN tag
4-8
match
ETX-5300A Ver. 1.0
Command
Description
vlan-tag pop vlan
Pops VLAN tag
p-bit fixed
Sets P-bit to a specific value
p-bit profile
Sets P-bit value according to marking profile
p-bit copy
Sets P-bit value by copying from the incoming frame
inner-vlan
Pushes inner VLAN tag
tag-ether-type
Pushes TPID
inner-tag-ether-type
Pushes inner TPID
no vlan-tag
Leaves outer and inner VLAN tags intact
show summary
management
Management parameters
access
Specifies access paths and rights
auth-policy
Assign policy of authentication
sftp
Enables/disables SFTP access
snmp
Enables/disables SNMP access
ssh
Enables/disables Secure Shell (SSH) access
telnet
Enables/disables Telnet access
tftp
Enables/disables TFTP access
radius
Specifies RADIUS parameters
clear-statistics
Clears the RADIUS statistics
server
Defines the RADIUS server
address
Specifies the RADIUS server's IP address
auth-port
Specifies the RADIUS server authentication port
key
Specifies the shared secret between client and RADIUS server
retry
Number of authentication attempts at RADIUS server
shutdown
Administratively enables/disables RADIUS server
timeout
Specifies the timeout
show statistics
Displays the RADIUS server statistics
show status
Displays the RADIUS server status
snmp
SNMP parameters
access-group
Defines the SNMP group
context-match
Configures context match
notify-view
Defines notify view of the SNMP group
read-view
Defines read view of the SNMP group
shutdown
Administratively enables/disables the SNMP group
ETX-5300A Ver. 1.0
Displays flow configuration summary
4-9

Command

Description
community
Defines the SNMP community
name
Defines the SNMP community name
sec-name
Defines the SNMP community security name
shutdown
Administratively enables/disables the SNMP community
tag
Defines the transport tag
notify
Configures notification
bind
Assigns trap to notification
shutdown
Administratively enables/disables notification
tag
Assigns tag to notification
notify-filter
Configures notification filter
mask
Configures notification filter mask
shutdown
Administratively enables/disables notification filter
type
Configures notification filter type
notify-filter-profile
Configures notification filter profile
profile-name
Defines notification filter profile name
shutdown
Administratively enables/disables notification filter profile
security-to-group
Configures security for access group
group-name
Specifies access group
shutdown
Administratively enables/disables security for access group
snmp-engine-id
Defines SNMP engine ID
target
Defines SNMP target
address
Defines SNMP target address
shutdown
Administratively enables/disables SNMP target
tag-list
Defines SNMP target tag list
target-params
Defines SNMP target parameters
trap-sync-group
Specifies trap synchronization group for SNMP target
target-params
Defines SNMP target parameters
message-processing-model
Configures SNMP target parameters message processing

model
security
Configures SNMP target parameters security
shutdown
Administratively enables/disables SNMP target parameters
version
Configures SNMP target parameters version
show trap-sync
4-10
write-view
Defines write view of the SNMP group
Displays the trap synchronization information
ETX-5300A Ver. 1.0
Command
Description
trap-sync-group
Configures trap synchronization group with SNMP managers
tag-list
Configures tag list for trap synchronization group with SNMP

managers
target-params
Configures target parameters for trap synchronization group

with SNMP managers
user
Defines SNMP user
authentication
Configures SNMP user authentication
privacy
Configures SNMP user privacy
shutdown
Administratively enables/disables SNMP user
view
Configures SNMP view
mask
Defines SNMP view mask
shutdown
Administratively enables/disables SNMP view
type
Defines SNMP view type
tacacsplus
TACACS+ parameters
group
Creates a group for binding TACACS+ servers
Enables/disables TACACS+ accounting for the group
server
Adds or removes a TACACS+ server
accounting-port
Sets accounting TCP port for a TACACS+ server
authentication-port
Sets authentication TCP port for a TACACS+ server
clear-statistics
Clears the TACACS+ statistics
group
Binds\unbinds TACACS+ server to\from a group
key
Specifies the shared secret of TACACS+ server
retry
Defines number of authentication attempts at TACACS+

server
shutdown
Administratively enables/disables TACACS+ server
show statistics
Displays the TACACS+ server statistics
timeout
Defines TACACS+ server response timeout
oam
Defines OAM parameters
cfm
OAM CFM configuration
maintenance-domain
Creates/deletes a maintenance domain
Specifies MD level
maintenance-association
Creates/deletes a maintenance association
ma-name
Specifies MA name
ccm-interval
Defines interval between continuity check messages
mep
MEP parameters
accounting
md-level
ETX-5300A Ver. 1.0
4-11

Command

Description
ais
Enable/disable sending AIS
bind
Binds MEP to a device port
ccm-initiate
Enables/disables CCM initiation by the MEP
ccm-priority
Specifies priority of the CCMs and LTMs transmitted by the

MEP
classification profile
Associates the MEP with a classifier profile
client-md-level
Defines client MD level
cos-mapping
Associates the MEP with a CoS profile
direction
Defines the MEP direction
flow
Assigns flows to the MEP
lbm
Runs diagnostic OAM loopback
show lbm-results
Displays OAM loopback results
linktrace
Runs OAM linktrace utility
show linktrace-results
Displays OAM linktrace results
queue queue-mapping
Defines the queue for the MEP
show status
Displays MEP status
show service
Displays MEP service status
shutdown
Enables/disables the MEP
remote-mep
Creates/deletes a remote MEP
Displays remote MEP status
service
Creates/deletes a MEP service
delay-threshold
Specifies delay threshold
delay-var-threshold
Specifies Delay variation threshold
dest-ne
Defines Destination network elements for delay and loss

measurement
clear-statistics
Clears the performance measurement counters
delay
Performance management method
loss
Selects loss measurement method
remote mac-address
Defines the MAC address of the destination NE
show statistics
Displays the performance measurement counters
dmm-interval
Specifies the interval for delay measurement messages
lmm-interval
Specifies the interval for loss measurement messages
shutdown
Enables/disables the MEP service
name
4-12
show status
Define the MEP name
ETX-5300A Ver. 1.0

Command

Description
mip
MIP parameters
bind
Binds the MIP to a device port
flow
Assigns flows to the MIP
mhf
MHF parameters
classification
Associates the MHF with a classifier profile
cos-mapping
Associates the MHF with a CoS mapping profile
queue
Defines the queue for the MHF
shutdown
Enables/disables the MIP
show status
Displays MIP status
measurement-bin-profile
Measurement bin profile parameters
Defines threshold limits for measurement bin profile
show summary
peer
Peer parameters
show peer-summary
Displays peer configuration summary
port
Port parameters
e1
E1 parameters
bert
Activates/deactivates a bit error rate test (BERT)
show bert
Displays the BERT results
clear-bert-counters
Clears the BERT counters
clear-statistics
Clears the statistics
idle-code
Defines code transmitted to fill unused timeslots in E1

frames
line-type
Specifies the E1 framing mode
loopback
Enables/disables loopback mode for the port
name
Defines port name
out-of-service
Enables/disables transmission of out-of-service signal for all

services
path-interval-threshold
Setting path interval threshold
pm-collection
Enables/disables PM collection
shutdown
Administratively enables/disables the port
show statistics
Displays the port statistics
show status
Displays the port status
trail-mode
Controls the propagation of alarm indications
tx-clock-source
Specifies the source of the port's transmit clock
thresholds
ETX-5300A Ver. 1.0
Displays configuration summary
4-13
Command
Description
ethernet
Ethernet parameters
auto-negotiation
Enables/disables automatic speed and duplex mode

adjustment
classification-key
Defines traffic classification key used by the port
clear-sfp-counters
Clears SFP counters
clear-statistics
Clears all statistics
flow-control
Enables/disables the flow control
l2cp
Assigns the L2CP profile to the port
mau-type
Defines MAU type of the port
name
Assigns/removes a port name
pm-collection
queue-group
Assigns/removes a queue group profile
restart-auto-negotiation
Restarts autonegotiation process
show sfp-status
Displays the Ethernet port SFP status
shutdown
Administratively disables/enables the port
show statistics
Displays the Ethernet port statistics
show status
Displays the Ethernet port status
tag-ethernet-type
Determines the tag protocol identifier
tx-ssm
Enables/disables Synchronous Status Messages transmission
l2cp-profile
Defines L2CP profile
default
Specifies the default action for undefined control protocols
mac
Specifies the L2CP action for MAC addresses
lag
admin-key
Defines LAG capability
bind
Binds a port to the LAG
show bind
Displays ports bound to the LAG
classification-key
Selects traffic classification key for the LAG
l2cp
Assigns L2CP profile to the LAG
lacp
Enables the LACP protocol on the LAG
show lacp-statistics
Displays the LAG members statistics
show lacp-status
Displays LAG members status
name
Assigns name to the LAG
queue-group
Assigns a queue group profile to the LAG
shutdown
Administratively disables/enables the
4-14
LAG parameters
ETX-5300A Ver. 1.0
Command
Description
Selects the Ethertype for the LAG
mng-ethernet
Management Ethernet port parameters
auto-negotiation
Enables/disables automatic speed and duplex mode

adjustment
clear-statistics
Clears all statistics
mau-type
Defines MAU type of the port
name
pm-collection
shutdown
show statistics
Displays the Ethernet port statistics
show status
Displays the Ethernet port status
path-profile
Defines SDH/SONET VC profile
ber-threshold
Selects EED (error rate degradation) and SD (signal degrade)

thresholds
fe-interval-threshold
Sets CV, ES, SES and/or UAS counter value during a 15-min
interval starting with a trap sent
interval-threshold
padding
Sets character type for padding path trace label
payload-label
Specifies the expected signal label
tim-monitoring
Enables/disables TIM monitoring
sag
Create/delete Service Aggregation Group
name
Assigns name to the SAG port
queue-group
Assigns a queue group profile to the SAG
show saps
Displays information on SAPs defined on the SAG
show status
Displays the SAG status
sdh-sonet
SDH/SONET port parameters
aug
Defines the administrative unit group (AUG)
au3
Defines AUG and enters AU3 controller level
clear-statistics
j1-pathtrace
Sets section trace bytes in the section header
name
path
Defines path profile
pm-collection
shutdown
tag-ethernet-type
ETX-5300A Ver. 1.0
4-15

Command

Description
show statistics
Displays statistics of the port
show status
Displays status of the port
vc11
Defines VC-11 parameters
clear-statistics
j2-pathtrace
name
path
Sets profile configuration
pm-collection
shutdown
show statistics
show status
clear-statistics
j1-pathtrace
name
path
path-width
Selects an administrative unit (AU)
pm-collection
shutdown
show statistics
show status
tug3
Defines TUG and enters TUG3 controller
clear-statistics
j2-pathtrace
name
path
pm-collection
shutdown
show statistics
show status
vc12
Defines VC-12 parameters
clear-statistics
j2-pathtrace
name
path
4-16
ETX-5300A Ver. 1.0

Command

Description
pm-collection
shutdown
show statistics
show status
clear-sfp-counters
Clears the SFP statistic counters
clear-statistics
eed-action
Enables/disables triggering AIS/RDI on failure
frame-type
Specifies the cell frame type
j0-pathtrace
j0-pathtrace
loopback
name
oc3
Defines an OC-3 (STM-1) connection
clear-statistics
j1-pathtrace
name
path
pm-collection
shutdown
show statistics
Displays the specified SDH/SONET statistics
show status
Displays the SDH-SONET of the port
sts1
Number in the range from 1 to 3.
clear-statistics
j1-pathtrace
name
path
pm-collection
shutdown
show statistics
show status
vt1-5
Specifies VT-1.5 as SONET channelized format
clear-statistics
j2-pathtrace
name
ETX-5300A Ver. 1.0
4-17

Command

Description
path
pm-collection
shutdown
show statistics
show status
overhead-mode
Defines overhead mode of the port
show sfp-status
Displays the Ethernet port SFP status
shutdown
soh
Sets SOH profile
show statistics
show status
tim-action
Enables/disables triggering AIS/RDI on failure
tx-clock-source
tx-ssm
Enables/disables DNU/DUS transmit
soh-profile
Defines SDH/SONET VC profile
ber-threshold
Selecting EED (error rate degradation) and SD (signal

degrade) thresholds
fe-line-interval-threshold
line-interval-threshold
Setting CV, ES, SES and/or UAS counter value during a 15-min
padding
Sets character type for padding path trace label
section-interval-threshold
tim-monitoring
Enables/disables TIM monitoring
show summary
Displays a summary of a port and its parameters
svi
Creates/deletes Service Virtual Interface
name
Assigns name to the SVI port
show status
Displays SVI status
t1
bert
Activates/deactivates a bit error rate test (BERT)
show bert
Displays the BERT results
clear-bert-counters
Clears the BERT counters
clear-statistics
4-18
Specifies T1 parameters
ETX-5300A Ver. 1.0
Command
Description
idle-code
Defines code transmitted to fill unused timeslots in E1

frames
inband-loopback
Controls inband loopback activation
line-type
Specifies the T1 framing mode
loopback
name
out-of-service
Transmits out-of-service signal for all services
path-interval-threshold
Defines path interval threshold
pm-collection
shutdown
show statistics
Displays the port statistics
show status
Displays the port status
trail-mode
Controls the propagation of alarm indications
tx-clock-source
protection
Protection parameters
aps
APS parameters
bind
Adds/removes working and protection ports to/from the APS
clear
Clears all externally initiated switch commands and the WTR

timer
force-switch-to-protection
Forces traffic to the protection port
force-switch-to-working
Forces traffic to the working port
lockout-of-protection
Prevents a working link from switching to a protection link
manual-switch-to-protection
Manually switches traffic to the protection port
manual-switch-to-working
Manually switches traffic to the working port
oper-mode
Specifies the APS operation mode
shutdown
Switches the APS to standby or re-activates the APS
show status
Displays the APS status
erp
Ethernet Ring Protection parameters
bridge
Assigns ring node to a bridge instance
clear-statistics
Clears ring statistics
data-vlan
Defines data VLAN
east-port
Defines bridge port as an East port of ERP node
r-aps
Configures dedicated VLAN for R-APS messages
sf-trigger
Enables propagation of Signal Failure (SF) condition from the

Ethernet OAM service layer
ETX-5300A Ver. 1.0
4-19
Command
Description
shutdown
Administratively enables/disables the ring
show statistics
Display statistics counters
show status
Display status parameters
timers
Defines guard and hold-off periods in msec
west-port
Defines bridge port as an West port of ERP node
backward-compatibility
Makes the ring compatible with previous ERP

implementations
manual-switch
Blocks the East or West port of a ring node
force-switch
Blocks the East or West port of a ring node
clear switch-command
Clears the existing switch commands
port-type
Defines node port type in relation to RPL owner
sub-ring
Sub-ring parameters
Enables virtual channel over shared link
io-group
I/O card protection group parameters
bind
Binds a card to an I/O card group
shutdown
Enables/disables an I/O card protection group
show status
Displays status of I/O card protection group
main-card
Main card protection parameters
manual-switch
Switches to secondary card if possible
show status
Displays status of main card protection
pwe
Pseudowire parameters
pw
Creates/deletes pseudowires
clear-statistics
Clears PW statistics
egress-port
Assigns egress port for L2 forwarding
jitter-buffer
Defines the jitter buffer size
label
Specifies the PW label used in the inbound and outbound

directions
name
Assign name to the PW
oam
Enables/disables OAM protocol for the PW
peer
Defines a remote peer terminating the PW
pm-collection
psn-oos
Selects the response to out-of-service conditions detected

at the local TDM port
shutdown
Administratively enables/disables the PW
show statistics
Displays PW statistics counters
4-20
virtual-channel
ETX-5300A Ver. 1.0
Command
Description
show status
Displays PW status
tdm-payload
Specifies the number of TDM payload bytes to be inserted in

each packet
tos
Specifies the value for the TOS byte used on outbound traffic
show pw-summary
qos
Quality of Service parameters
color-map-profile
Color mapping profile parameters
Defines color mapping rules
cos-map-profile
CoS mapping profile parameters
Defines CoS mapping rules
marking-profile
Marking profile
Defines marking rules
policer-aggregate
Policer aggregate profile parameters
show flows
Displays flows associated with the policer aggregate profile
policer
Assigns a policer profile which settings will be used by the

aggregate policer profile
policer-profile
Policer aggregate profile parameters
bandwidth
Defines bandwidth profile, using CIR/CBS and EIR/EBS rates
color-aware
Configures color awareness of the police
compensation
Compensates for Layer-1 overhead and additional VLAN tag
coupling-flag
Defines the admission options for yellow packets
queue-block-profile
Queue block profile parameters
queue
Defines a queue within the queue block profile
Assigns an internal queue profile to the queue within the

queue block
queue-group-profile
Queue group profile parameters
inherited-from
Defines a queue group which settings will be copied to

create a new queue group profile
queue-block
Selects a queue block within a queue group
bind
Binds a queue block to a queue in the next-level queue block
name
Assign name to a queue block within a queue group
profile
Assigns a queue block profile to a queue block within a

queue group
shaper
Assigns a shaper profile to a queue block within a queue

group
queue-internal-profile
map
map
mark
internal-profile
ETX-5300A Ver. 1.0
Display PW configuration summary
Internal queue parameters

4-21
Command
Description
congestion-avoidance
Assigns a WRED profile to the internal queue
scheduling
Sets scheduling method
shaper
Assigns a shaper profile to the internal queue
queue-map-profile
Defines queue mapping profile (this profile is preset and

cannot be changed)
Maps CoS values to priority queues
shaper-profile
Shaper profile parameters
bandwidth
Defines CIR, EIR data rate and CBS, EBS burst rate
compensation
Configures extra bytes to be taken into account
wred-profile
Defines congestion avoidance profile
Color mapping profile parameters
reporting
Alarm/event reporting parameters
acknowledge
Acknowledges the alarm/event logs
active-alarm-rebuild
Rebuilds active alarm table
show active-alarms
Displays active alarms
show active-alarms-details
Displays detailed information about active alarm
show alarm-information
Displays information on a specific alarm
alarm-input
Configures alarm input
show alarm-input
Displays alarm input information
show alarm-list
Displays list of alarms
show alarm-log
Displays alarm log
alarm-source-attribute
Masks alarm/event from a specific source
alarm-source-type-attribute
Masks alarm/event from a specific source type
show brief-alarm-log
Displays brief alarm log
show brief-log
Displays brief alarm/event log
clear-alarm-log
Clears alarm log
show event-information
Displays information on a specific event
show event-list
Displays event list
show log
Displays alarm/event log
mask-minimum-severity
Mask alarms per their severity
router
Router parameters
show arp-table
Displays the router ARP table
clear-arp-table
Deletes dynamic ARP entities
interface
Creates/deletes router interface
4-22
map
color
ETX-5300A Ver. 1.0
Command
Description
address
Assigns an IP address and a subnet mask to the router

interface
bind
Binds router interface to physical/logical port
management-access
Configures interface management access
name
Assigns name to the router interface
shutdown
Administratively enables/disables the router interface
show status
Displays router interface status
show interface-table
Displays the interface table
name
Assigns name to the router
show routing-table
Displays the routing table
static-arp
Creates/deletes static ARP entities
static-route
Creates/deletes static route entities
slot
Provisions cards in the chassis database
bind
Binds loopback address
card-type
Provisions card in the slot
reset
Resets the card
shutdown
Enables/disables the card
show status
Displays status of the card
system
System parameters
clock
Clock parameters
domain
Defines clock domain number
clear
Clears the Forced or Manual command
clear-statistics
Clears statistics for all clock sources
force
Forces a particular clock source
force-t4-as-t0
Forces T4 timing generator to use the same clock source as

the T0 generator
manual
Selects a particular clock source
max-frequency-deviation
Sets maximum frequency deviation
mode
Defines clock mode
quality
Sets minimum quality of outgoing station clock
source
Clock source parameters
clear-wait-to-restore
Resets the WTR timer
hold-off
Defines amount of time that signal failure must be active

before it is transmitted
priority
Defines clock source priority
ETX-5300A Ver. 1.0
4-23

Command

Description
quality-level
Sets quality level of the clock source
show statistics
Displays statistics counters of the clock source
show status
Displays status of the clock source
wait-to-restore
Defines amount of time that a previously failed

synchronization source must be fault free in order to be
considered available
show status
Displays clock status
sync-network-type
Sets synchronization network type
master
1588v2 master clock parameters
clear-statistics
distributed-mode
Defines the 1588v2 distributed clock mode
domain-number
Creates a PTP domain
ip-address
Defines IP address of the master entity
maximum-slaves
Defines the maximum number of slaves
pm-collection
shutdown
Administratively enables/disables master clock
slave
1588v2 slave clock parameters
clear-statistics
show statistics
Displays statistics counters
show status
Displays status parameters
show statistics
Displays statistics counters
show status
Displays status parameters
sync-rate
Defines synchronization message rate
tx-clock
Selects Tx clock domain
recovered
1588v2 recovered clock parameters
clear-statistics
ip-address
Defines IP address of 1588v2 slave entity
ptp-domain
Creates a PTP domain
recovery-mode
Defines 1588v2 message exchange mode
revertive
Defines BMCA (Best Master Clock Algorithm) mode
shutdown
Enable/disable recovered clock
source-port-identity
Identifier number of the master clock
show status
Display status parameters
wait-to-restore
Defines amount of time that previously failed clock must be

fault free in order to be considered available
4-24
ETX-5300A Ver. 1.0

Command

Description
master
Defines peer master source port ID
announce
Defines Announce message rate requested by the slave,

minimum Announce message rate supported by the slave
and duration of Announce message transmission
clear-statistics
Clears statistics
delay-respond
Defines Delay Response message rate requested by the

slave, minimum Delay Response message rate supported by
the slave and duration of Delay Response message
transmission
peer
Specifies the peer device that transmits the clock signal
quality-level
Sets clock quality level depending on the network type
shutdown
Enables/disables recovered clock
show statistics
Displays statistics
show status
Displays status
sync
Defines sync message rate requested by the slave, minimum

sync message rate supported by the slave and duration of
sync message transmission
station
Station clock parameters
impedance
Sets impedance for E1 and 2-MHz interfaces
interface-type
Defines station clock interface type
line-type
Sets line type for E1, T1 or 64 kHz interfaces
name
Assigns a name to station clock source
rx-sensitivity
Sets receiver sensitivity for E1 and 2-MHz interfaces
shutdown
Administratively enables/disables station clock
ssm-channel
Defines E1 G.732NCRC bits to carry SSM information
show status
Displays station clock status
tx-clock-source
Assigns station transmit clock source
tx-ssm
Enables SSM transmission for E1 G.732NCRC and T1 ESF

interfaces
station-y-cable
Enables/disables Y-cable redundancy for station clock
tod
ToD parameters
baudrate
Configure baud rate
interface-type
Define interface type
name
shutdown
Enables/disables ToD clock
show status
Displays ToD status
ETX-5300A Ver. 1.0
4-25
Command
Description
Administratively enables/disables ToD Y-cable redundancy
contact
Specifies/removes a contact person
date-and-time
Date and time parameters
date
Defines system date
date-format
Defines system date format
sntp
Simple Network Time Protocol parameters
broadcast
Enables/disables broadcast client mode for SNTP
poll-interval
Defines period for polling SNTP server
server
SNTP server parameters
address
Defines SNTP server IP address
prefer
Sets/resets the SNTP server preference
query-server
Queries the timestamp from the SNTP server
shutdown
Administratively enables/disables SNTP server
udp
Defines UDP port for SNTP communication
show status
time
Defines system time
zone
Defines time zone and offset
show date-and-time
Displays current system data and time
show device-information
Displays device information
location
Specifies/removes the location of a device
name
Assigns/removes a name to the device
syslog
Syslog parameters
address
Specifies the Syslog server IP address
clear-statistics
Clears the Syslog statistics
facility
Identifies facility to send Syslog messages from
port
Defines the UDP port for Syslog communication
severity-level
Specifies the severity level of Syslog messages to be sent
shutdown
Opens/closes the connection to the Syslog server
show statistics
Displays Syslog statistics
terminal
Supervisory terminal parameters
baud-rate
Defines the data rate for terminal communication
length
Sets the length of the terminal screen
timeout
Specifies the time of inactivity after which the device

disconnects
4-26
tod-y-cable
Displays SNTP server status
ETX-5300A Ver. 1.0
Table 4-5. Commands in the file Category

Command
Description
file
Initiates file operations
show configuration-files
Displays configuration files properties
show copy
Displays results of the copy operation
delete
Deletes a file from the device
dir
Lists all files in the device
show factory-default-config
Displays factory-default-config file contents
show rollback-config
Displays rollback-config file contents
show running-config
Displays running-config file contents
show startup-config
Displays startup-config file contents
show sw-pack
Displays the existing application software packages and

their contents
show user-default-config
Displays user-default-config file contents
Table 4-6. Commands in the logon Category

Command
Description
logon
Allows to logon to debug level
Table 4-7. Commands in the on-configuration-error Category

Command
Description
on-configuration-error
Determines the device behavior when encountering

an error in configuration file
Table 4-8. Commands in the rados-versions Category

Command
Description
show rados-versions
Displays RAD-OS version
4.2
GUI-Based Configuration
Preconfiguring ETX-5300A for SNMP Management

ETX-5300A can be managed by any SNMP-based network management station.
For example, in the RADview family of network management stations, provided IP
communications possible with the management station, as well as by the
standalone RADview stations.
ETX-5300A Ver. 1.0
4-27
To manage the ETX-5300A from a remote NMS, it is necessary to preconfigure

the basic parameters using a supervision terminal connected to the ETX-5300A
CONTROL DCE port. RAD recommends Layer-3 management access via
out-of-band Ethernet management port.
To preconfigure ETX-5300A 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
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
ingress-port mng-ethernet main-a/0
egress-port svi 99
no shutdown
exit all
4-28
ETX-5300A Ver. 1.0
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***************************
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***************************************
#*********************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************************************
ETX-5300A Ver. 1.0
4-29
Working with RADview

RADview-EMS is a user-friendly and powerful SNMP-based element management
system (EMS), used for planning, provisioning and managing heterogeneous
networks. RADview-EMS provides a dedicated graphical user interface (GUI) for
monitoring RAD products via their SNMP agents. RADview-EMS for ETX-5300A is
bundled in the RADview-EMS package for PC (Windows-based) or Unix.
For more details about this network management software, and for detailed
instructions on how to install, set up, and use RADview, contact your local RAD
partner or refer to the RADview-EMS User's Manual at the RAD website.
Working with 3rd Party Network Management Systems

ETX-5300A can be integrated into 3rd-party management systems at different
levels:
4-30
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.
ETX-5300A Ver. 1.0
4.3
Management Access Methods
This section describes two methods used to access the ETX-5300A management
host via Layer 2 or Layer 3 networks.
Layer-2 Management Access

Figure 4-4 illustrates a typical Layer-2 management scheme. Network
management station (NMS), ETX-5300A 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-5300A 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-5300A host is an IP address of a router interface, connected to a bridge

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

Figure 4-5 illustrates a typical Layer-3 management scheme. ETX-5300A and
remote ETX-2xxA devices are managed using:
ETX-5300A Ver. 1.0
Out-of-band traffic via a dedicated Ethernet management port, or
Inband traffic via a 10GbE port.
4-31
ETX-5300A
ETX-2xxA
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
NET
RIF 2
Inband
Access
LB IP
ETX-2xxA
NMS
Figure 4-5. Layer-3 Management Access

The ETX-5300A 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-5300A has router interface 1 connected to out-of-band Ethernet
management port via ingress and egress untagged flows (Figure 4-6). To enable
remote management, it is necessary to:
1. Define IP address of RIF 1
2. Enable management access for RIF 1
3. Enable RIF 1.
ETX-5300A
SVI
Router
RIF 1
OOB
Figure 4-6. Default Management Access via Out-Of-Band Ethernet Port

Note
4-32
Management is disabled for loopback RIFs, which are used for TDM pseudowire or
Precision Time Protocol (IEEE 1588v2) traffic.
ETX-5300A Ver. 1.0
4.4
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.5
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.
Parameter
Default Value
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.
Task
Command
Comments
Specifying the desired data

rate
baud-rate {300bps |
1200bps | 2400bps|
9600bps | 19200bps |
38400bps | 57800bps |
115200bps}
The default data rate is 9600 bps.
Defining whether in case

of inactivity, device
remains connected or
disconnects after a
specified time period
timeout forever
Specifying the number of

rows to display
length <020>
ETX-5300A Ver. 1.0
timeout limited <060>
The number of rows can be 0, to indicate no limit

on the number of lines displayed, or 20.
4-33
4.6
User Access
ETX-5300A management software allows you to define new users, their

management and access rights. Only superusers (su) can create new users, the
regular users are limited to changing their current passwords, even if they were
given full management and access rights.
You can specify a users password as a text string or as a hashed value, that you
obtain by using info detail to display user data.
Notes
User passwords are stored in a database so that the system can perform
password verification when a user attempts to log in. To preserve

confidentiality of system passwords, the password verification data is typically
stored after a one-way hash function is applied to the password, in
combination with other data. When a user attempts to log in by entering a
password, the same function is applied to the entered value and the result is
compared with the stored value.
A cryptographic hash function is a deterministic procedure that takes an
arbitrary block of data and returns a fixed-size bit string, the (cryptographic)
hash value, such that any change to the data changes the hash value.
Factory Defaults
By default, the following users exist, with default password 1234:
su
tech
user.
To add a new user:

1. Make sure that you are logged on as superuser (su).
2. Navigate to the Management context (config>mngmnt).
3. Define a new user: user <name> [ level { su | tech | user } ]
[[ password <password> [hash] ]
Example Defining Users
To define a new user:
User name = staff
User password = 1234.
ETX-5300A# configure management

ETX-5300A>config>mngmnt# user staff level su password 1234
# Password is encrypted successfully
ETX-5300A>config>mngmnt#
To add a new user with a hashed password:

1. Define a new user with a text password.
4-34
User Access
ETX-5300A Ver. 1.0
2. Use info detail to display the password hash value.

3. Define another user with the hashed password from the info detail
output.
The second user can log in with the text password defined in step 1.
For example, to add the following users:
User name = staff1
User password = 4222
User name = staff2
User password = hash of 4222 (user staff2 can log in with password 4222).

ETX-5300A>config>mngmnt# user staff1 level user password 4222
# Password is encrypted successfully
ETX-5300A>config>mngmnt# info detail
user "staff1" level user password
"3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
user "su"
:
ETX-5300A>config>mngmnt# user staff2 level user password
3fda26f8cff4123ddcad0c1bc89ed1e79977acef hash
ETX-5300A>config>mngmnt# info
user "su"
ETX-5300A>config>mngmnt# logoutexiting cli
CLI session is closed
user>staff2
password>****
To delete an existing user:
At the config>mngmnt# prompt, enter no <user_name>.

The specified user is deleted.
ETX-5300A Ver. 1.0
User Access
4-35
To view all connected users:
At the config>mngmnt# prompt, enter show users.

A list of all connected users is displayed, showing their access level, the
type of connection, and the IP address from which they are connected.
Example Displaying Users

ETX-5300A>config>mngmnt# show users
User
Access Level
Source
IP-address
----------------------------------------------------------------------------su
SU
Terminal
0.0.0.0
4.7
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-5300A 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.
4-36
RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working

Group.
RFC 1902, Structure of Management Information for Version 2 of the Simple

Network Management Protocol (SNMPv2). SNMPv2 Working Group.
RFC 1903, Textual Conventions for Version 2 of the Simple Network

Management Protocol (SNMPv2). SNMPv2 Working Group.
RFC 1904, Conformance Statements for Version 2 of the Simple Network

RFC 1905, Protocol Operations for Version 2 of the Simple Network

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

Management Protocol (SNMPv2).
RFC 1907, Management Information Base for Version 2 of the Simple

Network Management Protocol (SNMPv2). SNMPv2 Working Group.
SNMP Management
ETX-5300A Ver. 1.0
RFC 1908, Coexistence between Version 1 and Version 2 of the Internetstandard 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-5300A 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:
ETX-5300A Ver. 1.0
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.
Administrative features:
Naming of entities
People and policies
SNMP Management
4-37
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-5300A 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-5300A are as follows:
4-38
SNMPv2c: SNMPv2 with community-based security model
User-based security model (USM)
SNMP Management
ETX-5300A Ver. 1.0
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 userselected 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-5300A SNMPv3 agent may
limit some managers to viewing only the ETX-5300A performance statistics, and
allow others to view and update ETX-5300A 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).
ETX-5300A Ver. 1.0
SNMP Management
4-39
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-5300A, 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-5300A. 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":
4-40
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 =
SNMP Management
ETX-5300A Ver. 1.0
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-5300A 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-5300A default configuration provides only one standard user
named initial with no encryption and the lowest security level.
Use the following procedure to configure SNMPv3:
1. Set SNMP engine ID if necessary
2. Add users, specifying authentication protocol and privacy protocol
3. Add groups, specifying security level and protocol
4. Connect users to groups
5. Add notification entries with assigned traps and tags
6. Configure target parameter sets to be used for targets
7. Configure targets (SNMPv3 network management stations to which
ETX-5300A should send trap notifications), specifying target parameter sets
and notification tags
To configure SNMPv3 parameters:

1. Navigate to configure management snmp.
The config>mngmnt>snmp# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below.
Note
ETX-5300A Ver. 1.0
When you enter password parameters, they should contain at least eight
characters.
SNMP Management
4-41
Task
Command
Level
Comments
Configuring group
access-group <group-name>
{ snmpv2c | usm }
{ no-auth-no-priv | auth-no-priv | auth-priv }
snmp
no access-group deletes the

group
Defining context
matching
context-match {exact | prefix}
snmp>access-group
Setting notify view

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

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

of group
write-view <name>
snmp> access-group
Administratively
enabling group
no shutdown
snmp> access-group
Configuring
community
community <community-index>
snmp
Configuring name
name <community-string>
snmp> community
Configuring security
name
sec-name <security-name>
snmp> community
Configuring
transport tag
tag <transport-tag>
snmp> community
This should be normally set

to the default value
Administratively
enabling community
no shutdown
snmp> community
shutdown disables
community
Configuring
notification
notify <notify-name>
snmp>
4-42
SNMP Management
ETX-5300A Ver. 1.0
Task
Command
Assigning trap to
notification
bind {coldStart | linkDown | linkUp |

snmp>notify
authenticationFailure |
systemDeviceTemperatureOra |
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
notification, to be
used to identify the
notification entry
when configuring
target
tag <tag-value>
ETX-5300A Ver. 1.0
Level
Comments
You can assign more than
one trap to a notification, in
separate commands
snmp>notify
SNMP Management
4-43
Task
Command
Level
Administratively
enabling
notification
no shutdown
snmp>notify
Configuring
notification filter to
define access to a
particular part of
the MIB hierarchy
for trap variables
notify-filter <name> <sub-tree-oid>
snmp
Specifying the part

of the subtree OID
to use in order to
define the MIB
subtree
mask [<mask>]
snmp>notify-filter
Defining whether
traps with trap
variables belonging
to the MIB subtree
are sent
type {included | excluded}
snmp>notify-filter
Administratively
enabling
notification filter
no shutdown
snmp>notify-filter
Configuring
notification filter
profile
notify-filter-profile <params-name>
snmp>filter-profile
Configuring
notification filter
profile name
profile-name <argument>
snmp>filter-profile
Administratively
enabling
notification filter
profile
no shutdown
snmp>filter-profile
Connecting security
name to group (e.g.
connecting user or
community to
group)
security-to-group { snmpv2c | usm }

sec-name <security-name>
snmp
Specifying group to
which to connect
security name
group-name <group-name>
snmp>security-to-group
Administratively
enabling
security-to-group
entity
no shutdown
snmp>security-to-group
4-44
SNMP Management
Comments
no security-to-group
removes security-to-group
entity
shutdown disables the

security-to-group entity
ETX-5300A Ver. 1.0
Task
Command
Level
Comments
Setting SNMP
engine ID, as MAC
address or IP
address or string
snmp-engine-id mac [ <mac-address> ]
snmp
If you use the mac option

and dont specify the MAC
address, the SNMP engine ID
is set to the device MAC
address
snmp-engine-id ipv4 [ <ip-address> ]

snmp-engine-id text <string>
If you use the ipv4 option

and dont specify the IP
address, the SNMP engine ID
is set to the device IP
address
Configuring target
(SNMPv3 network
manager)
target <target-name>
snmp
Specifying target
address as IP
address or OAM
port
address udp-domain <ip-address> address

oam-domain <oam-port>
snmp>target
Assigning tag(s) to
target (the tag(s)
must be defined in
notification entries)
tag-list <tag>
snmp>target
Specifying set of
target parameters
for target
target-params <params-name>
Specifying trap
synchronization
group
trap-sync-group <group-id>
[import-trap-masking]
tag-list [ <tag> ]
tag-list [ <tag1>,<tag2>,<tagn> ]
no target removes target
If you specify more than one

tag, you must enclose the
list in square brackets; if you
specify just one tag, the
brackets are optional
snmp>target
If the group does not

exist, it is created
If you specify the

import-trap-masking
parameter, the
managers trap masking
is imported from the first
manager in the group
Enter no trap-sync-group
<group-id> to remove
the manager from the
group. If the manager
was the last in the
group, the group is
deleted.
Administratively
enabling target
no shutdown
snmp>target
shutdown disables target
Configuring set of
target parameters,
to be assigned to
target
target-params <target-param-name>
snmp
no target-params removes
target parameters
ETX-5300A Ver. 1.0
SNMP Management
4-45
Task
Command
Level
Specifying message
processing model
(SNMP version) to
be used when
generating SNMP
messages for the
set of target
parameters
message-processing-model
{ snmpv2c | snmpv3 }
snmp>target
Specifying user on
whose behalf SNMP
messages are to be
generated for the
set of target
parameters
security [ name <security-name> ]

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

parameters
Configuring target
parameters and
tags for trap
synchronization
group
trap-sync-group <group-id>
snmp
The trap synchronization

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

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

enter: no target-params
<params-name>
Configuring user
user <security-name>
[md5-auth [ {des | none} ] ]
snmp
If you dont specify the

authentication method
when creating a user, the
default is MD5 with DES
privacy protocol. To create a
user with no authentication,
specify none-auth.
user <security-name>
[sha-auth [ {des | none} ] ]
user <security-name> [none-auth]
Comments
no user <security-name>
deletes the user
4-46
SNMP Management
ETX-5300A Ver. 1.0
Task
Command
Level
Comments
Setting user
authentication
password and
optional key for
changes
authentication [ password <password> ]

[ key <key-change> ]
snmp>user
no authentication disables
authentication protocol
Setting user privacy

password and
optional key for
changes
privacy [ password <password> ]

[ key <key-change> ]
snmp>user
no privacy disables privacy

protocol
Administratively
enabling user
no shutdown
snmp>user
You must define the

authentication and
privacy method before
you can enable the user,
unless the user was
defined with no
authentication
(none-auth)

user.
Defining access to a
particular part of
the MIB hierarchy
view <view-name> <sub-tree-oid>
snmp
view-name Name of view,

which can be associated to a
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

of the subtree OID
to use in order to
define the MIB
subtree
mask <mask>
snmp>view
The mask is comprised of

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

the subtree
Administratively
enabling view
no shutdown
excluded Disables access

to the subtree
ETX-5300A Ver. 1.0
snmp>view
SNMP Management
4-47
Task
Command
Level
Displaying trap
synchronization
groups and
members for
SNMPv3 manager
groups
show trap-sync
snmp
Displaying SNMPv3
information, such
as the number of
times the SNMPv3
engine has booted,
and how long since
the last boot
show snmpv3 information
snmp
Comments
Example
To create SNMPv3 user and connect it to group:
User named MD5_priv:
4-48
Security level MD5 authentication, DES privacy
Group named "SecureGroup":
All security levels
Contains set of views named "internet" (from default configuration).
SNMP Management
ETX-5300A Ver. 1.0
ETX-5300A# configure management snmp

ETX-5300A>config>mngmnt>snmp# user MD5_priv md5-auth des
ETX-5300A>config>mngmnt>snmp>user(MD5_priv)$ privacy password MD654321
ETX-5300A>config>mngmnt>snmp>user(MD5_priv)$ authentication password MD654321
ETX-5300A>config>mngmnt>snmp>user(MD5_priv)$ no shutdown
ETX-5300A>config>mngmnt>snmp>user(MD5_priv)$ exit
ETX-5300A>config>mngmnt>snmp# access-group MD5Group usm no-auth-no-priv
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ context-match prefix
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ read-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ write-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ notify-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ no shutdown
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/no-auth-no-priv)$ exit
ETX-5300A>config>mngmnt>snmp# access-group MD5Group usm auth-no-priv
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ context-match prefix
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ read-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ write-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ notify-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ no shutdown
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-no-priv)$ exit
ETX-5300A>config>mngmnt>snmp# access-group MD5Group usm auth-priv
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ context-match prefix
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ read-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ write-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ notify-view internet
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ no shutdown
ETX-5300A>config>mngmnt>snmp>access-group(MD5Group/usm/auth-priv)$ exit
ETX-5300A>config>mngmnt>snmp# security-to-group usm sec-name MD5_priv
ETX-5300A>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ group-name MD5Group
ETX-5300A>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ no shutdown
ETX-5300A>config>mngmnt>snmp>security-to-group(usm/MD5_priv)$ exit
ETX-5300A>config>mngmnt>snmp#
To create notifications:
ETX-5300A Ver. 1.0
Notification named TrapData:
Tag = Data
Bound to agnStatusChangeTrap, agnUploadDataTrap.
Notification named TrapPower:
Tag = Power
Bound to agnPowerFailureTrap, coldStart.
SNMP Management
4-49

ETX-5300A>config>mngmnt>snmp# notify TrapPort
ETX-5300A>config>mngmnt>snmp>notify(TrapPort)$ tag Port
ETX-5300A>config>mngmnt>snmp>notify(TrapPort)$ bind ethLos
ETX-5300A>config>mngmnt>snmp>notify(TrapPort)$ bind sfpRemoved
ETX-5300A>config>mngmnt>snmp>notify(TrapPort)$ no shutdown
ETX-5300A>config>mngmnt>snmp>notify(TrapPort)$ exit
ETX-5300A>config>mngmnt>snmp# notify TrapPower
ETX-5300A>config>mngmnt>snmp>notify(TrapPower)$ tag Power
ETX-5300A>config>mngmnt>snmp>notify(TrapPower)$ bind powerDeliveryFailure
ETX-5300A>config>mngmnt>snmp>notify(TrapPower)$ bind systemDeviceStartup
ETX-5300A>config>mngmnt>snmp>notify(TrapPower)$ no shutdown
ETX-5300A>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-5300A>config>mngmnt>snmp# target-params TargParam1
ETX-5300A>config>mngmnt>snmp>target(TargParam1)$ message-processing-model snmpv3
ETX-5300A>config>mngmnt>snmp>target(TargParam1)$ version usm
ETX-5300A>config>mngmnt>snmp>target(TargParam1)$ security name MD5_priv level auth-
priv
ETX-5300A>config>mngmnt>snmp>target(TargParam1)$ no shutdown
ETX-5300A>config>mngmnt>snmp>target(TargParam1)$ exit
ETX-5300A>config>mngmnt>snmp# target TargNMS1
ETX-5300A>config>mngmnt>snmp>target(TargNMS1)$ target-params TargParam1
ETX-5300A>config>mngmnt>snmp>target(TargNMS1)$ tag-list [Port,Power]
ETX-5300A>config>mngmnt>snmp>target(TargNMS1)$ address udp-domain 192.5.4.3
ETX-5300A>config>mngmnt>snmp>target(TargNMS1)$ no shutdown
ETX-5300A>config>mngmnt>snmp>target(TargNMS1)$ exit
To display SNMPv3 information:

ETX-5300A> config>mngmnt>snmp# show snmpv3 information
SNMPv3
: enable
Boots
: 2
Boots Time (sec) : 102
EngineID
: 800000a4030020d2202416
4-50
SNMP Management
ETX-5300A Ver. 1.0
4.8
Management Access
You can enable or disable access to the ETX-5300A 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-5300A IP address has
been compromised. When Telnet, SSH, and SNMP are disabled, ETX-5300A can be
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.
Task
Command
Comments
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
4.9
tftp
no tftp blocks TFTP operation
no tftp
Use TFTP for transferring small files, such as

configuration files.
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).
ETX-5300A Ver. 1.0
Access Policy
4-51
Configuring Access Policy
To define the access policy:
In the config>mngmnt>access# prompt, enter the necessary commands

according to the tasks listed below.
Task
Command
Comments
Specifying authentication method

preferably via RADIUS/TACACS+, then
optionally TACACS+/RADIUS, then
optionally local
auth-policy 1st-level radius [2nd-level

tacacs+ [3rd-level {local | none}]]
ETX-5300A first attempts authentication via

the server specified by 1st-level. If the
server does not answer the authentication
request, then ETX-5300A attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then ETX-5300A
attempts to authenticate according to
3rd-level:
auth-policy 1st-level tacacs+ [2nd-level

radius [3rd-level {local | none}]]
local ETX-5300A 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-5300A ends the
authentication process and does not
attempt authentication at the next level.
Specifying authentication method
preferably via TACACS+, then
optionally local
auth-policy 1st-level tacacs+ [2nd-level {

local | none } ]
If 2nd-level is set to local, authentication is

performed via the TACACS server. If the
TACACS server does not answer the
authentication request, then ETX-5300A
authenticates via the local database. .If the
TACACS server rejects the authentication
request, ETX-5300A ends the authentication
process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
4.10 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.
4-52
ETX-5300A Ver. 1.0
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.
When a login attempt occurs at ETX-5300A, 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
timeout
auth-port
1812
Configuring RADIUS Parameters

ETX-5300A 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.
Task
Command
Comments
Assigning an IP address to the server
address <ip-address>
Possible IP addresses range from

1.1.1.1 to 255.255.255.255
ETX-5300A Ver. 1.0
4-53
Task
Command
Comments
Defining a non-disclosed string (shared

secret) used to encrypt the user
password.
key <string> [hash]
The shared secret is a secret key

consisting of free text known to
the client and the server for
encryption. It is hashed if
specified.
Defining the number of authentication

request attempts
retry <number-of-retries>
Range 010
Defining timeout (in seconds) for

response from RADIUS server
timeout <seconds>
Range 15
Defining the UDP port to be used for

authentication
auth-port <udp-port-number>
Range 165535
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-5300A>config>mngmnt>radius# show status

Server
IP Address
Access
Status
---------------------------------------------------------1.
0.0.0.0
Disable
Not connected
2.
0.0.0.0
Disable
Not connected
3.
0.0.0.0
Disable
Not connected
4.
0.0.0.0
Disable
Not connected
Figure 4-7. RADIUS Status
Displaying RADIUS Statistics
To display RADIUS statistics:
In the config>mngmnt>radius# prompt, enter show statistics.

RADIUS statistics appear as shown in Figure 4-8.
To clear RADIUS statistics:
4-54
In the config>mngmnt>radius# prompt, enter clear-statistics.
ETX-5300A Ver. 1.0
ETX-5300A>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-8. RADIUS Statistics

Table 4-9. 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.
Timeouts
Number of times a server did not respond, and the RADIUS server resent 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.11 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
ETX-5300A Ver. 1.0
4-55
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.
Parameter
Default Value
retry
timeout
5 seconds
authentication-port
49
accounting-port
49
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.
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
4-56
The access client is an entity which seeks the services offered by the
network.
TACACS+ client running on ETX-5300A, processes the requests from the

access client and pass this data to TACACS+ server for authentication.
ETX-5300A Ver. 1.0
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
accounting. TACACS+ supports authentication by using a user name and a fixed
password.
Accounting
ETX-5300A 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-5300A-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-5300A
Any level that was successfully changed in a shell.
Defining TACACS+ Server

ETX-5300A 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.
ETX-5300A Ver. 1.0
4-57
Task
Command
Comments
Defining a new TACACS+ server
server <ip-address>
no server deletes a TACACS+

server
Defining a non-disclosed string (shared

secret) used to encrypt the user
password
key <string> [hash]
The shared secret is a secret

key consisting of free text
known to the client and the
server for encryption. It is
hashed if specified.
Defining the TCP port to be used for

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

authentication
authentication-port
<tcp-port-number>
Range 165535
Binding accounting group to TACACS+

server
group <string>
no group detaches accounting

group from server
Defining the number of authentication

request attempts
retry <number-of-retries>
Permanently set to 1
Defining timeout (in seconds) for

response from TACACS+ server
timeout <seconds>
Range 110
no shutdown
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.
4-58
ETX-5300A Ver. 1.0
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-5300A# configure management tacacsplus

ETX-5300A>config>mngmnt>tacacsplus# server 175.18.172.150
ETX-5300A>config>mngmnt>tacacsplus>server(175.18.172.150)$ key TAC_server1
ETX-5300A>config>mngmnt>tacacsplus>server(175.18.172.150)$ no shutdown
ETX-5300A>config>mngmnt>tacacsplus>server(175.18.172.150)$ information detail
key "244055BF667B8F89225048C6571135EF" hash
retry 1
timeout 5
authentication-port 49
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-5300A# configure management tacacsplus

ETX-5300A>config>mngmnt>tacacsplus# group TAC1
ETX-5300A>config>mngmnt>tacacsplus>group(TAC1)$ accounting shell system
commands
ETX-5300A>config>mngmnt>tacacsplus>group(TAC1)$ info detail
accounting shell system commands
ETX-5300A>config>mngmnt>tacacsplus>group(TAC1)$ exit
ETX-5300A>config>mngmnt>tacacsplus# server 175.18.172.150
ETX-5300A>config>mngmnt>tacacsplus>server(175.18.172.150)# group TAC1
ETX-5300A>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89829AB8AB0FE50885" hash
retry 1
timeout 5
authentication-port 49
accounting-port 49
group "TAC1"
no shutdown
ETX-5300A Ver. 1.0
4-59
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-5300A>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-10. 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+ clients request is aborted by the TACACS+

server or the server fails to respond after maximum retry is exceeded
Pending Requests
Number of TACACS+ clients 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.
4-60
ETX-5300A Ver. 1.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.
Task
Command
Comments
Creating an accounting group
group
no group deletes accounting

group
Enabling TACACS+ accounting for the

group
accounting [shell] [system]

[commands]
Accounting can be of any

combination
no accounting disables
TACACS+ accounting for the
group
4.12 Syslog
ETX-5300A 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:
ETX-5300A Ver. 1.0
Long-term auditing
Intrusion detection
Tracking user and administrator activity
Product operation management.

Syslog
4-61
Factory Defaults
By default, Syslog operation is disabled. When enabled, the default parameters
are as follows:
Parameter
Default Value
facility
local1
port
514
severity-level
informational
The Syslog protocol provides an instrument for generating and transporting event
notification messages from ETX-5300A to servers across IP networks.
Mess
ages
PSN
ETX-5300A
ages
Mess
Syslog
Server
ETX-5300A
Figure 4-9. Syslog Functionality
Elements
Typical Syslog topology includes message senders (devices) and message
receivers (servers). ETX-5300A 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:
4-62
Syslog
Facility and severity (see below)
Host name or IP address of the device
Timestamp
Message content.
ETX-5300A Ver. 1.0
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 Severities

Facility designates a device or application that sends a message. The standard
includes some pre-defined facilities in the 015 range. ETX-5300A uses facilities
local17 for originator identification.
Severity is assigned to a message to specify its importance. ETX-5300A uses the

following severity designations:
Table 4-11. Syslog Severities
Code
Syslog Type
Description
Emergency
Emergency message
Alert
Critical alarm
Critical
Major alarm
Error
Minor alarm
Warning
Event
Notice
Cleared alarm
Informational
Informational message, not in use
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.
Task
Command
Defining a facility from which Syslog

messages are sent
facility {local1 | local2 | local3 |

local4 | local5 | local6 | local7}
Defining Syslog device UDP port for

communication
port <udp-port-number>
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
ETX-5300A Ver. 1.0
Comments
Range is 165535
Port configuration is allowed
only if a Syslog device is
administratively disabled
Syslog
4-63
Task
Command
Comments
Administratively enabling Syslog device
no shutdown
disables Syslog device
show statistics
Clearing statistics
clear statistics
Example below illustrates procedure for defining a Syslog device.
Facility: local2
UDP port: 155
Severity level: major.
ETX-5300A# configure system syslog device

ETX-5300A>config>system>syslog(device)#
ETX-5300A>config>system>syslog(device)# facility local2
ETX-5300A>config>system>syslog(device)# port 155
ETX-5300A>config>system>syslog(device)# severity-level major
ETX-5300A>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-12.
ETX-5300A>config>system>syslog(device)# show statistics
Total Tx Messages
: 356
Non-queued Dropped Messages
: 265
Figure 4-10. Syslog Statistics

Table 4-12. Syslog Statistic Parameters
Parameter
Description
Total Tx Messages
The total number of Syslog messages transmitted
Non-queued Dropped
Messages
The total number of Syslog messages that were

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).
4-64
Syslog
ETX-5300A Ver. 1.0
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/15)# prompt is displayed.
Task
Command
Comments
Defining Syslog server IP
address
<0.0.0.0255.255.255.255>
Defining Syslog server UDP port for

communication
port <udp-port-number>
Administratively enabling Syslog server
no shutdown
Range 165535
Port configuration is allowed
only if a Syslog server is
disables Syslog server
Example
Server IP address: 178.16.173.152
UDP port: 155
ETX-5300A# configure system syslog server

ETX-5300A>config>system>syslog(server/1)#
1
address 178.16.173.152
port 155
no shutdown
Configuration Errors
Table 4-13 lists messages generated by ETX-5300A when a configuration error is
detected.
Table 4-13. Configuration Error Messages

Message
Description
Syslog Port is out of range
Selected UDP port value is out of allowed range (165535)
Port is illegal or Device Port is already in

use
Selected UDP port is already in use
Parameter cannot be changed if Logging

Status/Server Access is enabled
Device/server UDP port or server IP address cannot be changed

while Syslog server is enabled
Illegal Severity
Invalid severity value
Illegal Facility
Invalid facility value
Illegal Server IP Address
Invalid server IP address
ETX-5300A Ver. 1.0
Syslog
4-65
4.13 Programming Cards

Use the following procedure to program cards in the ETX-5300A 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.
Displaying Card Summary

Before programming cards, run show card-summary command to display 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-5300A>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
2
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 4-11. Card Summary Screen

Table 4-14. Card Summary
Parameter
Description
Possible Values
Slot
Chassis slot
PS-A/B power supply slots

Main-A/B main card slots
14 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
4-66
Programming Cards
ETX-5300A Ver. 1.0
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
Provisioning I/O Cards

This section explains how to provision I/O cards in slots 1 to 4. ETX-5300A 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(14)#.
The config>slot(14)# prompt is displayed.
2. Enter card-type command according to the tasks listed below:
Task
Command
Comments
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
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]
interface type:
stm-1-ch-4 STM-1 E1 card with four TDM
ports
stm-1-t1-ch-4 STM-1 T1 card with four
TDM ports
oc-3-ch-4 OC-3 card with four TDM ports
Binding TDM I/O card to

previously configured loopback
router interface
bind loopback-address <value> Binding TDM I/O card to loopback router

interface is required for PW operation on
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:
ETX-5300A Ver. 1.0
Programming Cards
4-67
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 23. The card in slot 2 is
bound to loopback router interface with IP address 10.10.10.10
Empty slot 4.
ETX-5300A>config>slot(1)#
card-type eth gbe-20-sfp

no shutdown
card-type sdh-sonet stm-1-ch-4
bind loopback-address 10.10.10.10
no shutdown
no shutdown
no card-type
To verify card provisioning:
At the config# prompt, enter the show card-summary command.
ETX-5300A>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
ETH
GBE-20-SFP
Up
Up
Standalone
2
STM-1 Ch-4
STM-1 Ch-4
Up
Up
Standalone
3
STM-1 Ch-4
STM-1 Ch-4
Up
Up
Standalone
4
Empty
Empty
Down
Not Present Standalone
Fan
Fan
Fan
Up
Up
Standalone
Resetting I/O Cards
To reset an I/O card:

2. Enter reset to reset the card installed in the selected slot.
Displaying Card Status
To display card status:

2. Enter show status to display status the card installed in the selected slot.
4-68
Programming Cards
ETX-5300A Ver. 1.0
ETX-5300A>config>slot(2)# show status
Actual Type
Provisioned Type
Administrative Status
Operational Status
Status
Protection Mode
Software Version
:
:
:
:
:
:
:
STM-1 Ch-4
STM-1 Ch-4
Up
Up
OK
Standalone
0.92D001
detected.

Message
Description
No protection. Shutdown is not allowed.
Card cannot be shut down if no backup card has been

configured
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

shutdown
IP address of an active card cannot be changed
Cannot change card type in requested

slot
The type of card in the selected slot cannot be modified
Cannot set the card type in requested

slot
The type of card in the selected slot cannot be set
A service is defined on a card, card type

cannot be changed
the type of card cannot be changed if a service is configured on

the card
Remove a card before changing card

type
The type of card cannot be changed if the card is in a slot;

remove it
A card port is used by flow: card type

cannot be changed/deleted
The type of card cannot be changed if a flow is configured on

the card
A card port is used by PW: card type

The type of card cannot be changed if a pseudowire connection

(PW) is configured on the card
ETX-5300A Ver. 1.0
Programming Cards
4-69
4-70
Programming Cards
ETX-5300A Ver. 1.0
Chapter 5
Services
This chapter presents information on the service elements and services
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

parameter
256
WRED
Queue
Defines green and yellow packet

thresholds and drop probabilities
Queue
Queue block
Defines queue type with shaper and

WRED profile
16K
Queue block
Queue block within

queue group
Defines queue block parameters

(queues, scheduling scheme,
weights)
384
ETX-5300A Ver. 1.0
Service Elements
5-1
Chapter 5 Services
Profile Type
Applied to
Description
Scale per Chassis
Queue group
Port
Defines level-1, -2 and -3 scheduling

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

(drop, peer, tunnel)
16
Policer, policer
aggregate
Flow
Defines CIR, CBS, EIR and EBS

parameters
128
Ingress color mapping
Flow
Defines method and values for

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

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

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

ETX-5300A 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-5300A provides the following shaping tools:
Dual leaky bucket shaper (CIR/EIR)
Single leaky 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:
5-2
Tag Ethertype for identifying VLAN-tagged frames at ingress and setting

Ethertype value for VLAN editing (stack, swap) at egress
L2CP profile for defining L2CP frame handling (discard, peer or tunnel)
Queue group profile for associating a port with a queue group
Service Elements
ETX-5300A Ver. 1.0
Chapter 5 Services
Classification key for mapping traffic into flows according to classification profiles.
ETX-5300A 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-5300A 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-5300A
LB IP
Router
RIF
SVI
SVI
BP
SVI
User
BP
SVI
BP
OOB
BP
NET
Bridge
BP
User
SVI
SVI
Figure 5-1. Router and Bridge Connections with SVIs Identified
ETX-5300A Ver. 1.0
Service Elements
5-3
MEF-8
Pseudowires
BP
SVI
SVI
Flow
BP
SVI
Main Card Ethernet Ports
I/O Card STM-1/OC-3 Port
TDM Pseudowire Processing
Chapter 5 Services
BP
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-5300A 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-5300A supports up
to 512 SAPs per SAG.
Egress
SAG
I/O Card
Ethernet Port
I/O Card
Ethernet Port
Ingress
SAP
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:
5-4
Flows the main traffic-carrying elements
Bridge traffic-forwarding element for Layer-2 E-LAN services
Router traffic-forwarding element for Layer-3 services.
Service Elements
ETX-5300A Ver. 1.0
Chapter 5 Services
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 (07) according to a CoS-mapping profile.
Bridge
The bridge is a forwarding entity used by ETX-5300A for delivering E-LAN services
in multipoint-to-multipoint topology and G.8032 ring protection. With up to 32
bridge instances, ETX-5300A 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-5300A 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
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.
ETX-5300A Ver. 1.0
Service Elements
5-5
Chapter 5 Services
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-5300A Ver. 1.0
Chapter 5 Services
WRED
Shaper
Queue
Queue block
1. Define profiles
Shaper
L2CP
Classifier
CoS mapping
Queue group
Queue mapping
Color mapping
Policer
Marking
SAG
Flow N x 1
I/O Card
Ethernet Port
2. Configure ports
SAP
Flow 2
Main Card
Ethernet Port
Configure I/O card

Ethernet port
Configure main
card Ethernet port
Configure
physical layer
Configure
physical layer
Define
classifier key
Define
classifier key
Bind L2CP
profile
Bind L2CP
profile
Define VLAN tag

TPID
Define VLAN tag

TPID
Bind queue
group profile
Bind queue
group profile
3. Configure flows
Legend:
Mandatory
Optional
Configure flow 1
Configure flow 2
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind L2CP
profile
Bind classifier
profile
Bind classifier
profile
Define VLAN
editing actions
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Bind marking
profile
Define TPID
editing policy
Bind policer
profile
Bind queue
mapping profile
Bind queue
mapping profile
Bind queue
block instance
Bind queue
block instance
Figure 5-4. I/O-to-Main Path
ETX-5300A Ver. 1.0
E-Line Service
5-7
Chapter 5 Services
Table 5-2. E-Line I/O-to-Main Service Provisioning

Sequence
Step
Commands
Comments
Layer 2 Control
Protocol (L2CP)
l2cp-profile
Define policy for L2CP traffic handling by port

and/or flow (peer, tunnel 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.
1. Define profiles
When creating a flow, you can either bind it to

the color mapping profile or use a fixed color
value.
5-8
Policing
policer-profile
Create a policer bandwidth profile with required

CIR, CBS, EIR, EBS values. Not relevant for flow 2.
Priority Queue
Mapping
queue-map-profile
Define profile for mapping CoS values to queues.

Always use 1:1 mapping
(QueueMapDefaultProfile)
Congestion
Avoidance (WRED)
wred-profile
Define WRED profiles to be attached to queue

profiles
Shaper
shaper-profile
Define shaper profiles to be attached to a queue

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

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.
E-Line Service
ETX-5300A Ver. 1.0

Step
Commands
Comments
Ethernet Ports
port
Configure physical layer parameters

Define classifier keys for I/O and main card
Ethernet ports
2. Configure ports
Sequence
Chapter 5 Services
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
3. Configure flows
Bind classifier profiles to flow 1 and 2

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.
ETX-5300A Ver. 1.0
E-Line Service
5-9
Chapter 5 Services
1. Define profiles

See Figure 5.1
Flow
I/O Card
Ethernet Port
2. Configure ports
Main Card
Ethernet Port
Configure I/O card

Ethernet port
Configure main
card Ethernet port
See Figure 5.1
See Figure 5.1
Configure flow
3. Configure flows
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
mapping profile
Legend:
Mandatory
Bind queue
block instance
Optional
Figure 5-5. Main-to-I/O Path

Table 5-3. E-Line Main-to-I/O Service Provisioning
1. Define profiles
Sequence
5-10
Step
Commands
Comments
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Flows with ingress main card ports do not

support policing
E-Line Service
ETX-5300A Ver. 1.0
2. Configure ports
Sequence
Step
Chapter 5 Services
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Comments
Define flow with ingress port set to main card

port, and egress port set to I/O card port
Bind L2CP profile
3. Configure flows
Bind classifier profile

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.
ETX-5300A Ver. 1.0
E-Line Service
5-11
Chapter 5 Services

See Figure 5.1
1. Define profiles
Flow 2
I/O Card
Ethernet Port
2. Configure ports
SAG
SAG
Flow N x 1
I/O Card
Ethernet Port
SAP
SAP
Configure I/O card

Ethernet port
Configure I/O card

Ethernet port
Configure SAG
See Figure 5.1
See Figure 5.1
3. Configure flows
Legend:
Configure flow 1
Configure flow 2
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind L2CP
profile
Bind classifier
profile
Bind classifier
profile
Define VLAN
editing actions
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Bind marking
profile
Define TPID
editing policy
Bind policer
profile
Bind queue
mapping profile
Bind queue
mapping profile
Bind queue
block instance
Mandatory
Optional
Bind queue
block instance
Figure 5-6. I/O-to-I/O Path

Table 5-4. E-Line I/O-to-I/O Service Provisioning
2. Configure ports
1. Define profiles
Sequence
5-12
Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
E-Line Service
Comments
ETX-5300A Ver. 1.0

Sequence
Step
Chapter 5 Services
Commands
Comments
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.
ETX-5300A Ver. 1.0
E-Line Service
5-13
Chapter 5 Services

See Figure 5.1
1. Define profiles
Flow
Main Card
Ethernet Port
2. Configure ports
Main Card
Ethernet Port
Configure main
card Ethernet port
Configure main
card Ethernet port
See Figure 5.1
See Figure 5.1
Configure flow
3. Configure flows
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
mapping profile
Legend:
Mandatory
Bind queue
block instance
Optional
Figure 5-7. Main-to-Main Path

Table 5-5. E-Line Main-to-Main Service Provisioning
1. Define profiles
Sequence
5-14
Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
E-Line Service
Comments
ETX-5300A Ver. 1.0
2. Configure ports
Sequence
Step
Chapter 5 Services
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Comments
Define one flow with ingress and egress port set

to main card ports
3. Configure flows

value
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 Appendix B.
Figure 5-8 illustrates a typical E-LAN service. Table 5-6 details the configuration
steps needed for service provisioning.
ETX-5300A Ver. 1.0
E-LAN Service
5-15
Chapter 5 Services

See Figure 5.1
1. Define profiles
SAG
Flow 1
I/O Card
Ethernet Port
2. Configure ports
Configure I/O card

Ethernet port
SAP
Bridge
Flow 3a
Flow 3b
Flow 2a
Flow 2b
SVI BP
BP SVI
Main Card
Ethernet Port
Configure main
card Ethernet port
Configure SAG
See Figure 5.1
See Figure 5.1
3. Define bridge
Define bridge
Define SVIs (B) and

bridge ports
4. Define SVIs and

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
flows
Legend:
Mandatory
Optional
Configure flow 1
Configure flow 2a
Configure flow 2b
Configure flow 3a
Configure flow 3b
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind L2CP
profile
Define VLAN
editing actions
Bind classifier
profile
Define VLAN
editing actions
Bind classifier
profile
Bind classifier
profile
Bind marking
profile
Bind queue
mapping profile
Bind marking
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define TPID
editing policy
Bind queue
block instance
Bind queue
mapping profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Bind classifier
profile
Define VLAN
editing actions
Bind queue
block instance
Define VLAN
editing actions
Bind policer
profile
Bind marking
profile
Bind queue
mapping profile
Define TPID
editing policy
Bind queue
block instance
Bind queue
mapping profile
Bind queue
block instance
Figure 5-8. E-LAN Service
5-16
E-LAN Service
ETX-5300A Ver. 1.0
Chapter 5 Services
Table 5-6. E-LAN Service Provisioning

Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Comments
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Bridge
bridge
Define, assign a number and configure a bridge

entity
Service Virtual
Interface (SVI)
svi
Define bridge-port type SVIs, add ports to the

bridge and bind the bridge ports to the SVIs
bridge
Bridge
Bridge
bridge
Add VLANs, define bridge ports as VLAN members

and specify MAC table size for each VLAN
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
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
6. Configure flows
5. Configure VLAN
membership
4. Define SVIs and

bridge ports
3. Define bridge
2. Configure ports
1. Define profiles
Sequence

Bind classifier profiles to all flows
ETX-5300A Ver. 1.0
E-LAN Service
5-17
Chapter 5 Services
Sequence
Step
Commands
Comments
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-5300A 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:
5-18
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).
Routing Services
ETX-5300A Ver. 1.0
Note
Chapter 5 Services
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 Appendix B.
1. Define profiles
See Figure 5.1
Router
SAG
Flow 1
I/O Card
Ethernet Port
2. Configure ports
Configure I/O card

Ethernet port
SAP
Flow 2a
Flow 2b
SVI RIF
RIF SVI
Flow 3a
Flow 3b
Main Card
Ethernet Port
Configure main
card Ethernet port
Configure SAG
See Figure 5.1
See Figure 5.1
Define SVIs (R)
3. Define SVIs
4. Configure flows
Configure flow 1
Configure flow 2a
Configure flow 2b
Configure flow 3a
Configure flow 3b
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind L2CP
profile
Define VLAN
editing actions
Bind classifier
profile
Define VLAN
editing actions
Bind classifier
profile
Bind classifier
profile
Bind classifier
profile
Bind queue
mapping profile
Bind marking
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define TPID
editing policy
Bind queue
block instance
Bind queue
mapping profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define VLAN
editing actions
Bind queue
block instance
Define VLAN
editing actions
Bind policer
profile
Bind marking
profile
Bind queue
mapping profile
Bind queue
mapping profile
Bind queue
block instance
Bind queue
block instance
5. Define and bind router interfaces
Define RIFs
Define router
interfaces
Legend:
Mandatory
Optional
Bind router
interfaces to SVIs
Figure 5-9. I/O-to-Main via Router Path
ETX-5300A Ver. 1.0
Routing Services
5-19
Chapter 5 Services
Table 5-7. I/O-to-Main via Router Service Provisioning

Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Comments
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Service Virtual
Interface (SVI)
svi
Define router-type SVIs
Same as detailed in
Same as detailed in
Define five flows:
Table 5-2
Table 5-2
Flow 2a: ingress SAP, egress SVI

port
5. Configure flows
4. Define SVIs
2. Configure ports
1. Define profiles
Sequence

a fixed value
use a fixed value
2b, 3a and 3b
Bind marking profile to flow 3a and 2b
5-20
Routing Services
ETX-5300A Ver. 1.0
6. Add RIFs and

bind them to
SVIs
Sequence
Chapter 5 Services
Step
Commands
Comments
Router
router
Add interfaces to the router and bind the RIFs to

the 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.
ETX-5300A Ver. 1.0
Routing Services
5-21
Chapter 5 Services
1. Define
profiles
See Figure 5.1
Router
SAG
Flow 1
I/O Card
Ethernet Port
2. Configure
ports
SAP
Flow 2b
Configure I/O card

Ethernet port
Bridge
Flow 2a
Flow 3a
SVI RIF
RIF SVI
Flow 3b
SVI BP
BP
SVI
Flow 4a
Flow 4b
Main Card
Ethernet Port
Configure main
card Ethernet port
Configure SAG
See Figure 5.1
See Figure 5.1
Define bridge
3. Define bridge
Define SVIs (B and R)
and bridge ports
4. Define SVIs and

bridge ports
Define bridgeand router-type

SVIs
Define bridge
ports
Bind bridge ports
to SVIs
Configure VLAN
membership
5. Configure VLAN
membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
address ranges
6. Configure
flows 1-3
Configure flow 1
Configure flow 2a
Configure flow 2b
Configure flow 3a
Configure flow 3b
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind L2CP
profile
Define VLAN
editing actions
Bind classifier
profile
Define VLAN
editing actions
Bind classifier
profile
Bind classifier
profile
Bind classifier
profile
Bind queue
mapping profile
Bind marking
profile
Define VLAN
editing actions
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define TPID
editing policy
Bind queue
block instance
Define TPID
editing policy
Define VLAN
editing actions
Bind queue
mapping profile
Bind marking
profile
Bind queue
block instance
Bind policer
profile
Bind queue
mapping profile
Bind queue
block instance
Define RIFs
Define router
interfaces
Bind router
interfaces to SVIs
8. Configure flows
4a and 4b
Legend:
Mandatory
Optional
Configure flow 4a
Configure flow 4b
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind classifier
profile
Bind classifier
profile
Define VLAN
editing actions
Bind marking
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Bind queue
mapping profile
Define VLAN
editing actions
Bind queue
block instance
Bind marking
profile
Define TPID
editing policy
Figure 5-10. Router-to-Bridge Path

5-22
Routing Services
ETX-5300A Ver. 1.0
Chapter 5 Services
Table 5-8. Router-to-Bridge Service Provisioning
6. Configure flows 13
5. Configure VLAN
membership
4. Define SVIs and

bridge ports
3. Define bridge
2. Configure ports
1. Define profiles
Sequence
Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Comments
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Bridge
bridge

entity
Service Virtual
Interface (SVI)
svi

bridge
Bridge
Bridge
bridge

and specify MAC address ranges for each VLAN
Same as detailed in
Same as detailed in
Define five flows:
Table 5-2
Table 5-2
Flow 2a: ingress SAP, egress SVI (R)
Flow 3a: ingress SVI (R), egress SVI (B)
Flow 3b: ingress SVI (B), egress SVI (R)

ETX-5300A Ver. 1.0
Routing Services
5-23
Chapter 5 Services
Sequence
Step
Commands
Comments
a fixed value
use a fixed value
2b, 3a and 3b
Bind marking profile to flow 3a
7. Add RIFs and

bind them to
SVIs
Router
router
Add interfaces to the router and bind the RIFs to

the SVIs
8. Configure flows 4a and 4b
Define TPID editing policy for flow 3a and 4b
Same as detailed in
Same as detailed in
Define 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-5300A 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:
5-24
Point-to-point L2 service for MEF-8-encapsulated PWs
Bridge L2 for MEF-8-encapsulated PWs
Pseudowire Services
ETX-5300A Ver. 1.0
Chapter 5 Services
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.
1. Define profiles
See Figure 5.1
2. Configure ports
Flow 1a
PW
I/O Card TDM

Port
SVI
Flow 1b
Main Card
Ethernet Port
Configure I/O card

TDM port
Configure main
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
5. Add a pseudowire
6. Configure timeslot
cross-connections
Define PW peer
Add and configure a

pseudowire
Configure crossconnections
Configure timeslot
cross-connection
for CESoPSN PW
7. Configure flows
Configure flow 1a
Configure flow 1b
Bind ingress and

egress ports
Bind ingress and

egress ports
Define VLAN
editing actions
Bind classifier
profile
Bind marking
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define TPID
editing policy
Legend:
Mandatory
Optional
Bind queue
mapping profile
Define VLAN
editing actions
Bind queue
block instance
Bind queue
mapping profile
Bind queue
block instance
Figure 5-11. Point-to-Point L2 Pseudowire Service
ETX-5300A Ver. 1.0
Pseudowire Services
5-25
Chapter 5 Services
Table 5-9. Point-to-Point L2 Pseudowire Service Provisioning

Step
Commands
Same as detailed in
See Table 5-2
Comments
Table 5-2
SDH/SONET Ports
port
Configure physical layer parameters of the

SDH/SONET and E1/T1 ports
Service Virtual
Interface (SVI)
svi
Define PW-type SVI.

Remember that PW SVIs represent untagged
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

address
Pseudowires
pwe
Add and configure pseudowires
Cross-Connections
cross-connection
Assign timeslots to pseudowire
See Table 5-2
See Table 5-2
Define two flows:
E1 Ports
T1 Ports
7. Configure
flows
6. Configure
timeslot crossconnections
5. Define
pseudowire
4. Define PW peer
3. Define SVIs
2. Configure ports
1. Define profiles
Sequence
5-26
Pseudowire Services

port

ETX-5300A Ver. 1.0

Sequence
Step
Chapter 5 Services
Commands
Comments
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.
ETX-5300A Ver. 1.0
Pseudowire Services
5-27
Chapter 5 Services
1. Define profiles

See Figure 5.1
I/O Card TDM

Port
2. Configure ports
Flow
1a
PW
SVI
Bridge
SVI BP
BP SVI
Flow 2a
Flow 2b
Flow
1b
Configure I/O card

TDM port
Main Card
Ethernet 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
SVI (P)
Define SVIs (B) and

bridge ports
Define
PW-type
SVI
Define
bridge-type SVIs
Define bridge
ports
Bind bridge ports
to SVIs
Configure VLAN
membership
5. Configure VLAN
membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
table size
6. Define PW peer
7. Add a pseudowire
Define PW peer
Add and configure a
pseudowire
cross-connections
Configure timeslot
cross-connection
for CESoPSN PW
9. Configure flows
Legend:
Mandatory
Optional
Configure flow 1a
Configure flow 1b
Configure flow 2a
Configure flow 2b
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind ingress and

egress ports
Bind classifier
profile
Bind classifier
profile
Bind classifier
profile
Bind classifier
profile
Define VLAN
editing actions
Define VLAN
editing actions
Define VLAN
editing actions
Bind marking
profile
Bind marking
profile
Bind marking
profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Define TPID
editing policy
Define TPID
editing policy
Bind queue
mapping profile
Define VLAN
editing actions
Bind queue
block instance
Bind marking
profile
Define TPID
editing policy
Bind queue
mapping profile
Bind queue
block instance
Figure 5-12. Pseudowire Service over the Bridge

5-28
Pseudowire Services
ETX-5300A Ver. 1.0
Chapter 5 Services
Table 5-10. Pseudowire Service over the Bridge Service Provisioning
6. Define PW peer
5. Configure VLAN
membership
4. Define SVIs and

bridge ports
3. Define bridge
2. Configure ports
1. Define profiles
Sequence
Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
SDH/SONET Ports
port

SDH/SONET and E1/T1 ports
Bridge
bridge

entity
Service Virtual
Interface (SVI)
svi

E1 Ports
Comments
T1 Ports
bridge
Bridge
Bridge
bridge

and specify MAC table size for each VLAN
Pseudowire Peer
peer
Configure pseudowire peer by defining its MAC

address
ETX-5300A Ver. 1.0
Pseudowire Services
5-29
Chapter 5 Services
Step
Commands
Comments
Pseudowires
pwe
Cross-Connections
cross-connection
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
8. Configure
7. Define
pseudowire
Sequence
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.
5-30
Pseudowire Services
ETX-5300A Ver. 1.0

1. Define profiles
Chapter 5 Services
See Figure 5.1
Router
PW
I/O TDM Card
LB
RIF
RIF SVI
Flow 1a
Flow 1b
Main Card
Ethernet Port
Define loopback
RIF
2. Define LB RIF
Define loopback
router interface
3. Configure ports
Configure TDM I/O

card and its ports
Configure main
card Ethernet port
Define TDM I/O

card in slot
See Figure 5.1
Configure SDH/
SONET ports
Configure E1/T1
ports
4. Define SVI
Define SVI (R)

Define routertype 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 timeslot
cross-connection
for CESoPSN PW
8. Define and bind

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

egress ports
Bind ingress and

egress ports
Define VLAN
editing actions
Bind classifier
profile
Bind marking
profile
Bind queue
mapping profile
Bind CoS
mapping profile
or use fixed value
Bind color
mapping profile
or use fixed value
Bind queue
block instance
Define VLAN
editing actions
Bind queue
mapping profile
Legend:
Bind queue
block instance
Mandatory
Optional
Figure 5-13. L3 Pseudowire Service

ETX-5300A Ver. 1.0
Pseudowire Services
5-31
Chapter 5 Services
Table 5-11. L3 Pseudowire Service Provisioning

Step
Commands
Same as detailed in
Same as detailed in
Table 5-2
Table 5-2
Router
router
Define a loopback router interface and assign an

IP address to it.
SDH/SONET Ports
port
When defining TDM I/O card in chassis slot, bind

it to the IP address used by loopback router
interface.
E1 Ports
T1 Ports
Comments

SDH/SONET and E1/T1 ports.
Service Virtual
Interface (SVI)
svi
Define router-type SVI.

Remember that router SVI represents an
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

address
Pseudowires
pwe
6. Define
pseudowire
5. Define PW peer
4. Define SVIs
3. Configure TDM
I/O card and card
ports
2. Define loopback
router interface
1. Define profiles
Sequence
5-32
Pseudowire Services
ETX-5300A Ver. 1.0

Step
Commands
Comments
Cross-Connections
cross-connection
Same as detailed in
Same as detailed in
Define two flows:
Table 5-2
Table 5-2

port
8. Configure flows
7. Configure
Sequence
Chapter 5 Services
Bind classifier profile to flow 1b

Bind CoS mapping profile to 1b or use a fixed
value
fixed value
ETX-5300A Ver. 1.0
Pseudowire Services
5-33
Chapter 5 Services
5-34
Pseudowire Services
ETX-5300A Ver. 1.0
Chapter 6
Ports
This chapter presents information on the following physical and logical ports
present in ETX-5300A:
Ethernet Ports
SDH/SONET Ports
E1 Ports
T1 Ports
Service Aggregation Group (SAG)
Service Virtual Interface (SVI).
6.1
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.
Standards and MIBs

IEEE 802.3, RFC 4836, RFC 3635
Benefits
Ethernet interfaces located on the E5-MC-4, E5-GBE-20 and E5-10GBE-2 cards
provide high-speed connection to GbE and 10GbE networks using fiber optic
(SFP/XFP) or copper RJ-45 ports.
Factory Defaults
By default, Ethernet ports are not enabled.
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
ETX-5300A Ver. 1.0
Ethernet Ports
6-1
Chapter 6 Ports
(if it is capable of supporting that mode). In ETX-5300A all Ethernet ports operate
in full duplex mode only.
When autonegotiation is disabled, the user must manually define MAU (Medium
Attachment Unit) type.
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-5300A Ethernet interfaces, except the OOB management port, support
flow control.
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 Appendix B for
details.
L2CP Handling
ETX-5300A 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.
6-2
Ethernet Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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-5300A 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 L2CP Handling section in Appendix B 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 Appendix B 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 Traffic Management section in Appendix B 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.
The config>port>eth(<slot/port>)# prompt is displayed.
2. For configuring Ethernet out-of-band management port, navigate to
configure port mng-ethernet.
The config>port>mng-eth# prompt is displayed.
Task
Command
Comments
Assigning description to port
name <string>
no name removes the name
no name
Enabling autonegotiation
auto-negotiation
no auto-negotiation
no auto-negotiation disables
autonegotiation.
Autonegotiation is not supported for 10GbE
ports.
ETX-5300A Ver. 1.0
Ethernet Ports
6-3
Chapter 6 Ports
Task
Command
Comments
Defining Ethernet interface type,

when autonegotiation is disabled
mau-type { 10-t | 100-t | 1000-t | 10-1001000-t | 100-any | 1000-any | 10gany | 100-fx | 1000-sx | 1000-lx | 10gsr | 10g-lr | 10g-er }
mau-type is also used to define SFP/XFP

type
Enabling flow control
flow-control
no flow-control
no flow-control disables flow control

function
Enabling transmitting of Sync-E clock

availability and quality via SSM
tx-ssm
no tx-ssm disables SSM egress
Assigning queue group profile to

Ethernet port
queue-group <queue-group-profile-name>
no queue-group removes queue group

association
Defining classifier key for Ethernet

port
classification-key {vlan | inner-vlan | p-bit |

ip-precedence | ip-dscp}
Setting the VLAN tagged frame

Ethertype (tag protocol identifier)
tag-ethernet-type <0x0000-0xFFFF>
This value must be either 8100 or the same

as Ethertype value configured at chassis
level
Associating a Layer-2 control

processing profile with the port
l2cp <l2cp-profile-name>
Defines discarding or tunneling policy for

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 queue-group
no l2cp
no l2cp removes association with L2CP

profile.
Restarting autonegotiation process
restart-auto-negotiation
Administratively enabling port
no shutdown
shutdown disables the port
Enabling/disabling performance
monitoring data collection
pm-enable
no pm-enable disables PM data collection
Displaying port status
show status
Displaying port statistics
show statistics
Displaying SFP status
show sfp-status
Clearing port statistic counters
clear-statistics
Clearing SFP counters
clear-sfp-counters
no pm-enable
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.
6-4
Ethernet Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
The port status is displayed, for example as follows:

ETX-5300A>config>port>eth(main-a/1)# show status
Name
: GBE-5-1
Administrative Status : Up
Operational Status
: Up
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-5300A 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-1.
ETX-5300A Ver. 1.0
Ethernet Ports
6-5
Chapter 6 Ports
ETX-5300A>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
L2CP Discarded
OAM Discarded
ACL Discarded
FCS Error Frames
MAC Error Frames
MAC Overflow Frames
Too Short Frames
Discarded Frames
0
0
0
0
0
0
0
0
--
0
0
0
0
0
0
0
0
0
64 Octets
65-127 Octets
128-255 Octets
256-511 Octets
512-1023 Octets
1024-1518 Octets
1519-2047 Octets
2048-Max Octets
Too Long Frames
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Table 6-1. Ethernet Statistic Counters (I/O Card Port)

Parameter
Description
Note
Rx
Tx
Total Frames
Total number of received packets,

including packets with bad CRC,
and excluding short packets and
packets dropped due to Rx MAC
overflow
Total number of transmitted

packets
Total Octets
Total number of received octets,

including FCS and bad packet
octets, and excluding framing bits

octets
Unicast Frames
Total number of received good

unicast packets, excluding packets
with bad CRC and short packets
Total number of transmitted good

unicast packets
Multicast
Frames
Total number of received multicast

packets, excluding packets with
bad CRC and short packets

multicast packets
6-6
Ethernet Ports
ETX-5300A Ver. 1.0
Parameter
Chapter 6 Ports
Description
Note
Rx
Tx
Broadcast
Frames
Total number of received

broadcast packets, excluding
packets with bad CRC and short
packets

broadcast packets
Jabber Frames
The number of received frames

that exceeded the maximum
allowed packet size and contained
an CRC error, or were not well
formed
Discarded
Frames
The number of frames dropped in

Tx MAC
Error Frames
Total number of received bad

packets, including packets with
bad CRC and short packets
L2CP Discarded
The number of packets discarded

by the L2CP processing mechanism
I/O card ports

only
OAM Discarded

by the OAM processing mechanism
I/O card ports

only
ACL Discarded

by the ACL processing mechanism
I/O card ports

only
FCS Error
Frames
The number of received packets

with bad CRC
I/O card ports

only
MAC Error
Frames

in Rx MAC due to PHY error or
incorrect packet termination, such
as badly formed packets
I/O card ports

only
MAC Overflow

due to the FIFO overflow
Too Short
Frames
The number of received wellformed frames that were less than

64 octets long, excluding framing
bits and including FCS octets
Not available
for OOB
management
port
64 Octets
Total number of received packets

(including bad packets) that were
64 octets in length, excluding
framing bits and including FCS
octets

packets (including bad packets)
that were 64 octets in length,
excluding framing bits and
including FCS octets
Not available
for OOB
management
port
ETX-5300A Ver. 1.0
I/O card ports

only
Not available
for main card
ports
Ethernet Ports
6-7
Chapter 6 Ports

Description
Parameter
Note
Rx
Tx
65127 Octets

65127 octets in length, excluding
framing bits and including FCS
octets

that were 65127 octets in
length, excluding framing bits and
Not available
for OOB
management
port
128255 Octets

128255 octets in length,

Not available
for OOB
management
port
256511 Octets


Not available
for OOB
management
port
5121023
Octets


Not available
for OOB
management
port
10241518
Octets


Not available
for OOB
management
port
1519-2047
Octets


Not available
for OOB
management
port
2048-Max
Octets

2048 to maximum allowed size
octets in length, excluding framing
bits and including FCS octets

that were 2048 to maximum
allowed size octets in length,
Not available
for OOB
management
port
Too Long
Frames

that exceeded the maximum
allowed packet size

packets that exceeded the
maximum allowed packet size
Not available
for OOB
management
port
To clear port statistics:
6-8
At the prompt config>slot>port>eth(<slot/port>)#, enter clear-statistics.
Ethernet Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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 mux-eth-tdm (<slot>/<port>)#
2. Type show sfp-status.
The status is displayed, for example as follows:
ETX-5300A>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-2 explains the parameters of the SFP installed for selected link port.
Table 6-2. Link SFP/XFP Parameters
Parameter
Description
Detailed Status
SFP/XFP status
Connector Type
SFP/XFP connector type
Transceiver Code
SFP/XFP transceiver mode
Vendor Name
The original manufacturers name
ETX-5300A Ver. 1.0
Ethernet Ports
6-9
Chapter 6 Ports
Parameter
Description
Vendor Part Number
The original vendors part number
Vendor Revision
The original vendors firmware revision
Vendor Serial Number The original vendors serial number

Enhanced Monitoring
Enhanced SFP/XFP monitoring support
Typical Maximum
Range (Meter)
The maximum range expected to be achieved over typical optical fibers, in meters
Wave Length (nm)
The nominal 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)
Displays the current optical power, in dBm, received by the SFP/XFP
TX Power (dBm)
Displays the current optical power, in dBm, transmitted by the SFP/XFP
Laser Bias (mA)
Displays the measured laser bias current, in mA
Laser Temperature
(Celsius)
Displays the measured laser temperature, in C
Power Supply (V)
Displays 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
Performance monitoring is enabled
Administratively enabled.
ETX-5300A# configure port eth main-a/2

ETX-5300A>config>port>eth(main-a/2)# auto-negotiation
ETX-5300A>config>port>eth(main-a/2)# classification-key vlan
ETX-5300A>config>port>eth(main-a/2)# l2cp l2cp_prof_1
ETX-5300A>config>port>eth(main-a/2)# queue-group queue_group_1
ETX-5300A>config>port>eth(main-a/2)# pm-enable
ETX-5300A>config>port>eth(main-a/2)# no shutdown
6-10
Ethernet Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
detected.

Message
Description
Autonegotiation enabled not allowed for

10G port
Autonegotiation cannot be enabled for 10GbE ports
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

enabled
Autonegotiation must be disabled for 100BaseFX interfaces
Invalid MAU type for autonegotiation

disabled
Autonegotiation must be enabled for 1000BaseBT interfaces
Modify failed: Ethertype tag value is in

use
The Ethertype cannot be changed if an active flow is attached to

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

values has been exceeded
Only two Ethertype values (default and another one) are

allowed
Cannot delete default Ethertype tag

value
The default Ethertype value 0x8100 cannot be deleted
Delete failed: Ethertype tag value is in

use
The Ethertype value cannot be deleted because it is use by

another port
6.2
SDH/SONET Ports
Four SDH/SONET ports located on the E5-cTDM-4 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),
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), using fiber optic SFP ports.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-11
Chapter 6 Ports
Factory Defaults
ETX-5300A is supplied with all SDH/SONET ports enabled. Other parameter
defaults are listed in the table below.
Parameter
Default Value
j0-pathtrace string
0x00
j1-pathtrace string
0x01
j2-pathtrace string
0x00
overhead-mode
itu-ansi
loopback
disabled
tx-ssm
disabled
tx-clock-source
domain 1
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 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:
6-12
Direct synchronous multiplexing of individual tributary signals within the

structure of the higher-rate multiplexed signal.
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.
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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-1 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.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-13
Chapter 6 Ports

N x M Bytes
Order of
Transmission
F B
B B
B
B
N x M Bytes
N Rows
2
Order of
Transmission
B B
B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure 6-1. 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-1). 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-2, an SDH frame comprises two distinct parts:
Section Overhead (SOH)
Virtual Container (VC).
N Rows
Section
Overhead
Path Overhead (One Column)
Virtual Container
(VC)
M Columns
Figure 6-2. SDH Frame Organization
6-14
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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.
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.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-15
Chapter 6 Ports
STM-1 Frame Structure

ETX-5300A handles the base-level SDH signal, which is called Synchronous
Transport Mode Level 1 (STM-1). Figure 6-3 shows the STM-1 frame structure.
2430 Bytes/Frame
155.52 Mbps
9 Rows
Section
Overhead
Path Overhead (9 Bytes)
Serial Signal
Stream
STM-1 Virtual Container (VC-4)
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-3. 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.
6-16
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Pointers
In Figure 6-3, 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:
ETX-5300A Ver. 1.0
SDH terminal multiplexer performs the insertion/removal of tributary signals

into SDH frames
SDH/SONET Ports
6-17
Chapter 6 Ports
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-4.

Multiplexer
Section
Multiplexer Section
Regenerator
Section
Regenerator
Section
Regenerator
Section
Tributary
Signals
.
..
SDH
Terminal
Multiplexer
SDH
Terminal
Multiplexer
Tributary
Signals
.
..
SDH Cross-Connect
VC
Assembly
Path
VC
Disassembly
Figure 6-4. Structure of Transmission Path in SDH Network

As shown in Figure 6-4, 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-5 shows the detailed structure of the overhead data in STM-1 frames.
6-18
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Path
Overhead
Section Overhead
Framing
A1
Regenerator
Section
Overhead
(Rows 1 - 3)
AU Pointers
(Row 4)
Framing
A1
Framing
A2
Framing
A1
Framing
A2
ID
C1
Path Trace
J1
BIP-8
B1
Orderwire
E1
User
F1
BIP-8
B3
DCC
D1
DCC
D2
DCC
D3
Signal Label
C2
Pointer
H1
Pointer
H2
Pointer
H3
APS
APS
K1
K2
User Channel
F2
DCC
D4
DCC
D5
DCC
D6
Multiframe
H4
DCC
D7
DCC
D8
DCC
D9
Z3
DCC
D10
DCC
D11
DCC
D12
Z4
Orderwire
E2
Z5
BIP-24
B2
B2
Multiplex
Section
Overhead
(Rows 5 - 9)
Framing
A2
Z1
Z1
B2
Z1
Z2
Z2
Z2
Pointer
H3
Pointer
H3
Path Status
G1
Bytes reserved for future use
Figure 6-5. 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.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-19
Chapter 6 Ports
Data Communication Channel (D1, D2, D3 Bytes)

The 192 kbps Data Communication Channel (DCC) provides the capability to
transfer network management and maintenance information between
regenerator section terminating equipment.
Orderwire Channel (E1 Byte)
The E1 byte is 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 provide a 576 kbps data communication channel (DCC) between
multiplexer section termination equipment. This channel is used to carry network
administration and maintenance information.
6-20
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Orderwire Channel (E2 Byte)

The E2 byte is 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 0s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)
The code 00000001 represents the VC-4 equipped state.
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
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-21
Chapter 6 Ports
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 supports 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 section below.
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-2, 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:
6-22
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
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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-6 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-7.
2430 Bytes/Frame
155.52 Mbps
9 Rows
Section
Overhead
VC-4 Path Overhead
Serial Signal
Stream
9 Columns
TU-12
No. 1
TU-12 No.2
to
TU-12 No.62
TU-12
No. 63
260 Columns
1 Column
Figure 6-6. VC-4 Carrying TU-12 Payload

As shown in Figure 6-6, 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-7 shows a general view of the SDH multiplexing hierarchy. The hierarchy
illustrates both the European and North American PDH multiplex levels.
Figure 6-7 also shows the utilization of additional SDH signal structures:
ETX-5300A Ver. 1.0
TUG: tributary unit group, is the structure generated by combining several

lower level tributaries into the next higher level tributary. For example, TUG-2
SDH/SONET Ports
6-23
Chapter 6 Ports
is generated by combining 3 TU-12 or 4 TU-11, and TUG-3 is generated by

combining 7 TUG-2.
Note
STM-1
(155.520 Mbps)
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).
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).
1
1
AU-4
VC-4
AU-3
VC-3
AUG
C-4
139.264 Mbps
(E4)
1
3
44.736 Mbps
(DS3)
3
VC-3
TU-3
C-3
34.368 Mbps
(E3)
TUG3
TU-2
1
7
2
TUG2
Legend
VC-2
C-2
3.152 Mbps
(DS1C)
VT3
TU-11
VC-11
C-11
1.544 Mbps
(DS1)
TU-12
VC-12
C-12
2.048 Mbps
(E1)
Pointer Processing
3
Mapping
6.312 Mbps
(DS2)
Figure 6-7. 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-7
shows that the STM-1 signal can be generated by the following multiplexing
paths:
6-24
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.
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
SDH Maintenance Signals and Response to Abnormal

Conditions
The maintenance signals transmitted within the SDH signal structure are
explained in Table 6-4.
Table 6-4. SDH Maintenance Signal Definitions

Signal
Description
Loss of Signal (LOS)
LOS state entered when received signal level drops below the value at which an
error ratio of 10 is predicted.
-3
LOS state exited when 2 consecutive valid framing patterns are received,
provided that during this time no new LOS condition has been detected.
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
Multiplexer Section AIS
The AIS indication is an all 1s pattern in pointer bytes.
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 1s 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

(FERF or MS-FERF)
Sent upstream by multiplexer section terminating equipment (MSTE) within

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
110.
-3
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
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-25
Chapter 6 Ports
Signal
Description
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
1s pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when all 1s pattern is received in bytes H1 and H2 for 3
consecutive frames. Removal is detected when 3 consecutive valid AU pointers
are received
High Order Path Remote

Alarm Indication
(HO Path RAI, also known
as HO Path FERF)
Generated by high order path terminating equipment (HO PTE) in response to

received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
POH G1 byte to 1.
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 1s
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 1s pattern).
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
Detected by LO PTE when all 1s pattern received in bytes V1 and V2 for 3

consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Note
Low Order Path Remote

Alarm Indication
(LO Path RAI, also known
as LO Path FERF)
TU Path AIS is only available when generating and/or receiving floating

mode tributary unit payload structures.
Generated by low order path terminating equipment (LO FTE) in response to

received TU Path AIS. Sent upstream to peer LO PTE.
Indicated by setting bit 8 of LO POH V5 byte to 1.
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-8 provides a graphical representation of the flow of alarm and indication
signals through an SDH transmission path.
6-26
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Low Order Path
High Order Path

Multiplexer Section
Regenerator
Section
Regenerator
Section
LO PTE
HO PTE
MS TE
RS TE
MS TE
LOP
HO PTE
LO PTE
LOP
LOP
AIS
(H1H2)
AIS
(V1V2)
LOS
LOF
LOS
LOF
AIS (X2)
Tributary
AIS
FERF
(X2)
RAI
(G1)
RAI (G1)
RAI
(VS)
RAI (VS)
B1(BIP-8)
B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE
(G1)
FEBE
(G1)
BIP-2
(VS)
FEBE
(VS)
FEBE
(VS)
Legend
Collection
Transmission
Generation
LO
HO
Low Order
High Low Order
PTE
RS TE
MS TE
Path Terminating Equipment

Regenerator Section Terminating Equipment
Multiplexer Section Terminating Equipment
Figure 6-8. 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:
ETX-5300A Ver. 1.0
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
SDH/SONET Ports
6-27
Chapter 6 Ports
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
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-9 shows the SONET multiplexing hierarchy.

STS-3
(155.520 Mbps)
1
STS-3
STS-3c
139.264 Mbps
(E4)
1 STS-3c
SPE
44.736 Mbps
(DS3)
1
2
STS-1
Legend
STS-1
SPE
VT
Group
VT6
VT6
SPE
6.312 Mbps
(DS2)
VT3
VT3
SPE
3.152 Mbps
(DS1C)
VT1.5
VT1.5
SPE
1.544 Mbps
(DS1)
VT2
VT2
SPE
2.048 Mbps
(E1)
Pointer Processing
3
Mapping
Figure 6-9. SONET Multiplexing Hierarchy

The main signal structures in the SONET hierarchy are designated as follows:
6-28
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
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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.
SDH/SONET Port Diagnostics

Diagnostic tools at the STM-1/OC-3 level include local and remote loopback for
checking connections to TDM ports.
Remote Loopback
The recovered STM-1/OC-3 receive signal provided by the STM-1/OC-3 transceiver
of the tested port is returned by the remote loopback toward the equipment
connected to the local STM-1/OC-3 port. The loopback is activated at the line side
of the STM-1/OC-3 framer serving the tested port.
Figure 6-10 shows the signal paths when a remote loopback is activated.
E5-cTDM-4 Card
RX
Transceiver
Framer
TX
RX
Transceiver
Framer
TX
Figure 6-10. Remote Loopback

The test signal is provided by the equipment connected to the local STM-1/OC-3
port, that must receive its own transmission. While the loopback is activated, the
local STM-1/OC-3 port continues sending the received payload to the ETX-5300A
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 port, including the
transmission plant connecting the local equipment to the E5-cTDM-4 card, and
the STM-1 transceiver of the E5-cTDM-4 card.
Local Loopback
The local loopback connects the STM-1/OC-3 transmit signal generated by the
STM-1/OC-3 framer of the tested port, to the receive input of the framer. This
returns the STM-1/OC-3 signal toward the equipment at the remote end of the
link.
Figure 6-11 shows the signal paths when a local loopback is activated.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-29
Chapter 6 Ports

E5-cTDM-4 Card
RX
Transceiver
Framer
TX
RX
Transceiver
Framer
TX
Figure 6-11. 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 line.
The test signal is provided by the remote equipment whose payload is routed to
the tested STM-1/OC-3 port; that equipment must receive its own transmission.
This test fully checks the operation of the local STM-1/OC-3 port, except for the
STM-1/OC-3 line interface (transceiver). It also checks the ETX-5300A signal paths
that end at the corresponding STM-1/OC-3 port, including the transmission
through the packet network connecting the remote equipment to ETX-5300A.
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.
Task
Command
Comments
Defining the administrative unit

group (AUG)
aug <aug number>
AUG is relevant for STM-1 E1 and STM-1

T1 modes. See Configuring AUG/OC-3
below.
Assigning short description to

port
name <string>
no shutdown
Setting the type of operation in

accordance with the SDH or
SONET standards
frame-type {sdh | sonet}
frame-type parameter is included for

information only. Interface type is
selected when a TDM module is defined
in chassis slot.
Controlling EED response

(sending AIS downstream and
RDI upstream)
eed-action [ { soh } ] [ {
path } ] [ { vt } ]
EED response is enabled for SOH, path

and VT levels
6-30
SDH/SONET Ports
no name
no eed-action
ETX-5300A Ver. 1.0
Chapter 6 Ports
Task
Command
Comments
Controlling transmitted and

expected path trace labels
(carried in byte J0 of the SDH
overhead) by the port
j0-pathtrace [ {tx-string <txtrace-string> ] [exp-string

<exp-string>}]
When ETX-5300A receives a path

trace string that is different from the
expected one, it declares TIM defect
Activating diagnostic loopback
loopback { local | remote }

[ duration <160>]
Loopback duration is within 160 minute

range.
no loopback
no loopback deactivates the loopback.
Controlling TIM response

(sending AIS downstream and
RDI upstream)
tim-action [ { soh } ] [ { path

} ] [ { vt } ]
TIM response is enabled for EOH, path

and VT levels
Defining STM-1 frame overhead

type
overhead-mode { itu-ansi |
ttc }
This value defines value for unused

overhead bytes. It is valid for STM-1 T1
mode only.
Selecting the timing reference

source used by the port for the
transmit-to-network direction
tx-clock-source {loopback |
domain <domain-number>}
Tx clock source set for one SDH/SONET

port is automatically copied to the rest
three TDM ports of the card.
no tim-action
Currently, it is recommended to use

domain clock as a Tx clock source.
Defining OC-3
oc3<oc3 number>
This parameters is valid for OC-3 mode

only and must be set to 1
Assigning SOH profile
soh <profile_name>
SOH profile configuration is detailed in
Configuring SOH Profile

monitoring data collection at
port level
pm-enable
show status
See Displaying Status
show statistics
See Displaying Statistics
Displaying SFP status
show sfp-status
Clearing statistic counters
clear-statistics
Clearing SFP statistic counters
clear-sfp-counters
Controlling carrying SSM code in

S1 byte for system clock quality
level definition
tx-ssm
no pm-enable
no tx-ssm
If enabled, the TDM port carries SSM

code in S1 byte for system clock QL. In
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

ETX-5300A supports a single AUG (STM-1) or OC-3 (OC-3) per TDM port.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-31
Chapter 6 Ports
To configure AUG/OC-3:
1. At the config>port>sdh-sonet(slot/port)# prompt, enter aug 1 or oc3 1.
The config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)# prompt is
displayed.
Task
Command
Comments

J1-pathtrace [ {tx-string <txtrace-string> ] [exp-string

<exp-string>}]
When ETX-5300A receives path trace

string that is different from the expected
one, it declares TIM defect
Assigning path profile to AUG or

OC-3
path <profile_name>
Path profile configuration is detailed in
Selecting path width
path-width { au4 | au3}
This value defines T1-AU-3 and E1 to

AU-4 mapping mode. It is valid for STM-1
ports only.
AUG level
pm-enable
Defining TUG-3 (Tributary Unit

Group)
tug3 { 1 | 2 | 3}
This parameter is valid for STM-1 E1

ports only. See Configuring
TUG3/AU3/STS-1 below.
Defining AU-3 (Administrative

Unit)
au3 { 1 | 2 | 3}
This parameter is valid for STM-1 T1

ports only. See Configuring
TUG3/AU3/STS-1 below.
Defining STS-1 port
sts1 { 1 | 2 | 3}
This parameter is valid for OC-3 ports

only. See Configuring TUG3/AU3/STS-1
below.
Configuring Path Profile
no pm-enable
Configuring TUG3/AU3/STS-1 Inerfaces

ETX-5300A 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 13, au3 13 or sts1 13.
The config>port>sdh-sonet>(slot/port)aug(1) or oc3(1)>tug3(number),
au3(number) or sts1(number)# prompt is displayed.
6-32
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Task
Command
Comments


<exp-string>}]

one, it declares TIM defect
Assigning path profile to AU3 or

STS-1
path <profile_name>
AU3 and STS-1 levels
pm-enable

port
name <string>
Defining VC-12 ports
vc12 {<17> | <13>}
Use space to separate TUG2 and VC-12

values. This parameter is valid for STM-1
E1 ports only. See Configuring VC-12/VC11/VT-1.5 below.
Defining VC-11 ports
vc11{ <17> | 14>}
Use space to separate TUG2 and VC-11

values. This parameter is valid for STM-1
T1 ports only. See Configuring VC-12/VC11/VT-1.5 below.
Defining VT-1.5 ports
vt1-5 {<17> | <14>}
Use space to separate TUG2 and VT-1.5

values. This parameter is valid for OC-3
ports only. See Configuring VC-12/VC11/VT-1.5 below.
no shutdown

no pm-enable
no name
Configuring VC-12/VC-11/VT-1.5 Inerfaces

ETX-5300A 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.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-33
Chapter 6 Ports
Task
Command
Comments


<exp-string>}]

one, it declares TIM defect.
Assigning path profile to VC-12,

VC-11 or VT-1.5
path <profile_name>
monitoring data collection at VC12, VC-11 or VT-1.5 levels
pm-enable

port
name <string>
no shutdown

no pm-enable
no name
Configuring SOH Profile

In the ETX-5300A 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.
Task
Command
Comments
Defining EED (error rate

degradation) and SD (signal
degrade) thresholds
ber-threshold [eed {e-3 | e4 | e-5} ] [ sd {e-5 | e-6 | e-7

| e-8 | e-9}]
If the selected BER value is exceeded,

ETX-5300A generates the relevant (EED
or SD) alarm.
Currently, SD BER threshold uses E-5
only.
Setting far-end CV, ES, SES

and/or UAS counter value during
a 15-min interval starting from
which a trap is sent
6-34
SDH/SONET Ports
fe-line-interval-threshold [cv
<cv-value 016383>] [es
<es-value 0900>] [ses
<ses-value 0900>] [uas
<uas-value 0900>]
ETX-5300A Ver. 1.0
Chapter 6 Ports
Task
Command
Setting near-end CV, ES, SES

line-interval-threshold [cv
<es-value 0-900>] [ses
<uas-value 0900>]
Setting section CV, ES, SES

section-interval-threshold
[cv <cv-value 016383>] [es
<ses-value 0900>] [sefs
<sefs-value 0900>]
Defining a padding character

(null or space) used when an
SDH trace message string is
shorter than 15 characters
padding<value>
Controlling TIM defect

monitoring
tim-monitoring
no tim-monitoring
Comments
no tim-monitoring disables TIM defect

monitoring

In the ETX-5300A 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.
Task
Command
Comments
Defining EED (error rate

degradation) and SD (signal
degrade) thresholds
ber-threshold [eed {e-3 | e4 | e-5} ] [ sd {e-5 | e-6 | e-7

| e-8 | e-9}]
If the selected BER value is exceeded,

ETX-5300A generates the relevant (EED
or SD) alarm
Currently, SD BER threshold uses E-5
only.
Setting far-end CV, ES, SES

ETX-5300A Ver. 1.0
fe-line-interval-threshold [cv
<uas-value 0900>]
SDH/SONET Ports
6-35
Chapter 6 Ports
Task
Command
Setting near-end CV, ES, SES

interval-threshold [cv
<uas-value 0900>]
Defining a padding character

(null or space) used when an
SDH trace message string is
shorter than 15 characters
padding<value>
Defining the expected

higher-order path signal label
(byte C2)
payload-label<value>
Controlling TIM defect

monitoring
tim-monitoring
no tim-monitoring
Comments
no tim-monitoring disables TIM defect

monitoring
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
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
6-36
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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-clock-source domain 1
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-5300A Ver. 1.0
SDH/SONET Ports
6-37
Chapter 6 Ports
ETX-5300A>config>port>sdh-sonet(1/1)# show status

Name
: SDH/SONET- 1-1
Operational Status
: Up
MAC Address
SFP Status
Connector Type
Loopback
:
:
:
:
Trace Message (J0)

Expected
Received
00-07-45-00-0F-08
OK
SFP In
None
: 0x01
: 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-5300A>config>port>sdh-sonet(l/1)>aug(1)# show status
Name
Operational Status
: HVC-1/1/1
: Down
: Down
Trace Message (J0)

Expected
Received
: 0x01
: 0x01
Signal Label
Expected
Received
: 0x00
: 0x00
RDI Code
: No Defect
To display AU3/STS-1 status:

1. Navigate to:
STM-1 T1:
config>port>sdh-sonet(slot/port)>aug(1)>au3(1)#
OC-3:
config>port>sdh-sonet(slot/port)>oc3(1)>sts1(1)#
6-38
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
ETX-5300A>config>port>sdh-sonet(4/1)>oc3(1)>sts1(1)# show
status
Name
Operational Status
: HVC-4/1/1
: Down
: Down
Trace Message (J1)

Expected
Received
: 0x01
: 0x01
Signal Label
Expected
Received
: 0x00
: 0x00
RDI Code
: No Defect
To display AU3/STS-1 status:

1. Navigate to:
STM-1 E1
config>port>sdh-sonet(slot/port)>aug(1)>tug3(1)>vc12(tug2_num/vc12_num)#
STM-1 T1:
config>port>sdh-sonet(slot/port)>aug(1)>au3(1)>vc11(tug2_num/vc11_num)#
OC-3:
config>port>sdh-sonet(slot/port)>oc3(1)>sts1(1)>vt1-5(tug2_num/vt1.5_num)#
ETX-5300A>config>port>sdh-sonet(4/1)>oc3(1)>sts1(1)# show
status
Name
Operational Status
: LVC-4/1/1
: Down
: Down
Trace Message (J2)

Expected
Received
: 0x01
: 0x01
Signal Label
Expected
Received
: 0x00
: 0x00
RDI Code
: No Defect
SDH/SONET ports of ETX-5300A 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.
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-39
Chapter 6 Ports
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-5, Table 6-6 and Table 6-7.
Task
Command
Comments
show statistics {current | interval <intervalnum 1..96> | current-day | previous-day | allintervals | all}
current Displays the current

interval statistics
interval (196) 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>sdh-sonet(l/1)# pm-enable
ETX-5300A>config>port>sdh-sonet(l/1)# show statistics current
Current
Time Elapsed (Sec) : 0
Valid Intervals
: 0
Invalid Intervals : 0
Section
ES
: 0
SEFS
: 0
ES
UAS
FC
Line
: 0
: 0
: 0
SES
CV
: 0
: 0
SES
CV
: 0
: 0
SES
CV
: 0
: 0
Far End
ES
UAS
FC
: 0
: 0
: 0
Figure 6-12. SDH/SONET Statistics
6-40
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
ETX-5300A>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)# vt1-5 1 1
ETX-5300A>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)>vt1.5(1/1)# pm-enable
ETX-5300A>config>port>sdh-sonet(1/1)>oc3(1)>sts1(1)>vt1.5(1/1)# show
statistics current
Current
----------------------------------------------------------------------------Time Elapsed (Sec) : 0
Valid Intervals
: 0
Invalid Intervals : 0
ES
UAS
FC
: 0
: 0
: 0
ES
UAS
FC
Far End
: 0
: 0
: 0
SES
CV
: 0
: 0
SES
CV
: 0
: 0
Figure 6-13. SDH/SONET Statistics, VT-1.5 Level

Table 6-5. SDH/SONET Statistics, Section Counters
Parameter
Description
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 K or more Section BIP errors were detected
SDH: Number of seconds during which 2400 or more RS errored blocks were detected
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-6. SDH/SONET Statistics, Line Counters

Parameter
Description
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 K 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
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-41
Chapter 6 Ports
Parameter
Description
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
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.
Table 6-7. SDH/SONET Statistics, Far-End Line Counters

Parameter
Description
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 which K 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
To clear statistics:
At the prompt config>slot>port>sdh-sonet (<slot/port>)#, enter

clear-statistics.
Testing SDH/SONET Ports

ETX-5300A 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 card at a time. SDH/SONET Port Diagnostics section above
details signal paths when local and remote loopbacks are activated.
6-42
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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 160 min.
To deactivate a loopback:
At the config>port>sdh-sonet>(slot/port)# prompt, enter no loopback.
detected.

Message
Description
Cannot change loopback type, disable

the loopback first
Loopback type cannot be changed while the loopback is active
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 CV threshold value
CV threshold value is out of range (016383)
Invalid inband loopDown length
Invalid length of inband loopback deactivation code
Invalid ES threshold value
ES threshold value is out of range (0900)
Invalid SES threshold value
SES threshold value is out of range (0900)
Invalid SEFS threshold value
SEFS threshold value is out of range (0900)
Invalid CSS threshold value
CSS threshold value is out of range (0900)
Invalid UAS threshold value
UAS threshold value is out of range (0900)
Invalid LES threshold value
LES threshold value is out of range (0900)
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 (160 min)
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 (016383)
Invalid ES section interval threshold
ES section threshold value is out of range (0900)
Invalid SES section interval threshold
SES section threshold value is out of range (0900)
Invalid SEFS section interval threshold
SEFS section threshold value is out of range (0900)
Invalid CV line interval threshold
CV line threshold value is out of range (016383)
ETX-5300A Ver. 1.0
SDH/SONET Ports
6-43
Chapter 6 Ports
Message
Description
Invalid ES line interval threshold
ES line threshold value is out of range (0900)
Invalid SES line interval threshold
SES line threshold value is out of range (0900)
Invalid CvFe line interval threshold
CV far-end line threshold value is out of range (016383)
Invalid EsFe line interval threshold
ES far-end line threshold value is out of range (0900)
Invalid SesFe line interval threshold
SES far-end line threshold value is out of range (0900)
Invalid UasFe line interval threshold
UAS far-end line threshold value is out of range (0900)
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 (016383)
Invalid ES1 5min interval threshold value
ES 5-min interval threshold value is out of range (0900)
Invalid SES1 5min interval threshold

value
SES 5-min interval threshold value is out of range (0900)
Invalid UAS1 5min interval threshold

value
UAS 5-min interval threshold value is out of range (0900)
Invalid FeCv1 5min interval threshold

value
CV far-end 5-min interval threshold value is out of range (0

16383)
Invalid FeEs1 5min interval threshold

value
ES far-end 5-min interval threshold value is out of range (0

900)
Invalid FeSes1 5min interval threshold

value
SES far-end 5-min interval threshold value is out of range (0

900)
Invalid FeUas1 5min interval threshold

value
UAS far-end 5-min interval threshold value is out of range (0

900)
Invalid payload label
Invalid expected higher order path signal label (byte C2) has
been selected
Medium type SONET does not match

card type
Frame type is not compatible with selected card type
Medium type SDH does not match card

type
Frame type is not compatible with selected card 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
Profile can't be created: max number of

profiles has been reached
Maximum number or SOH or path 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
6-44
SDH/SONET Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Message
Description
Profile does not exist
Cannot assign a port to a non-existing SOH or path profile
6.3
E1 Ports
Internal E1 ports of the E5-cTDM-4 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-5300A is supplied with all E1 ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
line-type
g732n
path-interval-threshold cv
path-interval-threshold es
80
path-interval-threshold ses
10
path-interval-threshold sefs
path-interval-threshold css
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.
ETX-5300A Ver. 1.0
E1 Ports
6-45
Chapter 6 Ports
HDB3 is based on the alternate mark inversion (AMI) code. In the AMI code, 1s
are alternately transmitted as positive and negative pulses, whereas 0s are
transmitted as a zero voltage level. To prevent the transmission of long strings of
0s, 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 0s 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-14.
8 Bits per
Time Slot
Time Slot 0
Time Slot 16
a. Even Frames (0,2,4-14)

1 0 0 1 1 0 1 1
a. Frame 0
0 0 0 0 X Y X X
FAS
Time Slots 1-15, 17-31
MAS
Channel Data
b. Odd Frames (1,3,5-15)

I 1 A N N N N N
32 Time Slots/Frame
16 Frames/Multiframe
TS
0
TS
1
FR
0
TS
2
TS
3
FR
1
TS
4
b. Frames 1-15
A B C D A B C D
TS
5
FR
2
TS
6
TS
7
FR
3
TS
8
FR
4
TS
9
TS
10
TS
11
FR
5
TS
12
FR
6
TS
13
TS
14
TS
15
FR
7
TS
16
TS
17
FR
8
TS
18
FR
9
TS
19
1 2 3 4 5 6 7 8
TS
20
TS
21
FR
10
TS
22
FR
11
TS
23
TS
24
TS
25
TS
26
FR
12
TS
27
FR
13
TS
28
FR
14
TS
29
TS
30
TS
31
FR
15
Notes
I
N
A
FAS
International Bit
National Bits (Sa4 through Sa8)
Alarm Indication Signal (Loss of Frame Alignment - Red Alarm)
Frame Alignment Signal, occupies alternate
(but not necessarily even) frames
ABCD
X
Y
MAS
ABCD Signaling Bits

Extra Bit
Loss of Multiframe Alignment
Multiframe Alignment Signal
Figure 6-14. 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:
6-46
E1 Ports
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.
ETX-5300A Ver. 1.0
Chapter 6 Ports
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
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
ETX-5300A Ver. 1.0
E1 Ports
6-47
Chapter 6 Ports
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.
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-14, 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-5300A 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.
6-48
E1 Ports
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
ETX-5300A Ver. 1.0
Chapter 6 Ports
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.
The loss of frame alignment is reported by means of the A bit (Figure 6-14).
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-14).
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
Bit Error Rate Test for measuring the quality of the E1 line.
Local Loopback
Figure 6-15 shows the signal paths during a local loopback on an internal E1 port.
Internal E1
TDM
PSN
Framer
Mapper
Figure 6-15. Local Loopback on Internal E1 Port, Signal Paths

As shown in Figure 6-15, 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
ETX-5300A Ver. 1.0
E1 Ports
6-49
Chapter 6 Ports
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.
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 users 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-5300A.
Remote Loopback
Figure 6-16 shows the signal paths during a remote loopback on an internal E1
port.
As shown in Figure 6-16, 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 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-16. 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 users equipment to the ETX-5300A, and part of the internal ETX-5300A
signal path that handle the routing of the signals up to the tested E1 port,
including the SDH mapper of the E5-cTDM-4 card.
6-50
E1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
BER Testing
A BERT typically consists of a test pattern generator and a receiver that is set to
the same pattern. BER testers can be used together at two ends of transmission
link to check data integrity in both directions. Alternatively, a single bit tester can
be used at one end of the link with a loopback activated at the remote end to
return the transmitted data.
BER testing can be activated on the entire internal port or on the selected
timeslots with or without the injection of errors randomly or at a constant rate.
Multiple BERTs can be run simultaneously on separate E1 ports.
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.
The config>port>e1>(slot/port/tributary)# prompt is displayed.
Note
An internal E1 port becomes active only if at least one enabled pseudowire with a
valid cross-connection is assigned to the port.
Task
Command
Comments
Assigning short
description to port
name <string>
Masking/unmasking
alarms generated by the
internal E1
no shutdown
shutdown masks alarms generated by the

internal E1
Specifying E1 framing
mode
line-type {unframed | g732n

| g732n-crc}
When using one of the framed modes, you

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
performance monitoring
data collection
pm-enable
Setting path CV, ES, SES,

SEFS, CSS and UAS
counter value during a
15-min interval starting
from which a trap is sent
path-interval-threshold [cv <cv-value 0

16383>] [es <es-value 0900>] [ses <sesvalue 0900>] [sefs <sefs-value 0900>]
[css <css-value 0900>] [uas <uas-value
0900>]
ETX-5300A Ver. 1.0
no pm-enable
E1 Ports
6-51
Chapter 6 Ports
Task
Command
Comments
Activating BER testing,

defining test pattern and
error injection
bert [pattern {2e-10 | 2e-15 | 2e-20 | 2e23 | 511 | 2047| qrss | 2e-11}] [inject-error
{none | single | 10e-1 | 10e-2 | 10e-3 |
10e-4 | 10e-5 | 10e-6 | 10e-7}]
no bert disables BER testing
no bert
Specifying the code
transmitted to fill unused
timeslots in E1 frames
idle-code { 00 to FF (hexa) }
Selecting the code

transmitted during
out-of-service period
out-of-service <00FF>
This parameter is valid for framed modes

only.
Only one idle code value is allowed per the
E5-cTDM-4 card.
The hexadecimal number is in the range of 0
to FF (two digits).
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 card.
See Alarm Indications and Fault Propagation
in the TDM Pseudowires of Chapter 8
Controls the propagation

of alarm indications
trail-mode {terminated | extended}
Selects the reference

source used by the
transmit path of this port
tx-clock-source {domain <domain-num> |

loopback | pw }
Activating diagnostic
loopback
loopback { local | remote } [ duration <1

60>]

range.
no loopback
no loopback deactivates loopback.
show status
show statistics
Displaying Status
You can display current status of any internal E1 port on an E5-cTDM-4 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-5300A>config>port>e1(1/1/1)# show status

Name
: E1-1-1-1
: Down
Operational Status
: Down
Loopback
: Off
The E1 interface status screens provide information on the port name,
administrative/operational status, and loopback status.
6-52
E1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Internal E1 ports of ETX-5300A 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-5.
Task
Command
Comments

interval statistics


12:00 midnight

midnight

96)

ETX-5300A>config>port>e1(4/1/1)# show statistics current

Current
--------------------------------------------------------------Time Elapsed (Sec) : 0
Valid Intervals
: 0
Path
--------------------------------------------------------------CV
: 0
Rx Frames Slip
: 0
ES
: 0
UAS
: 0
BES
: 0
FC
: 0
SES
: 0
SEFS
: 0
Note
For unframed E1 ports, only FC counter is available.

Table 6-9. Internal E1 Statistics
Parameter
Description
CV
Number of CRC-4 errors
ETX-5300A Ver. 1.0
E1 Ports
6-53
Chapter 6 Ports
Parameter
Description
Rx Frames Slip
Number of received Frames Slip events
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.
FC
Number of E1 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.
Testing Internal E1 Ports

Diagnostic tools at the E1 level include:
Local and remote loopback for checking connections to E1 ports
Bit Error Rate Test for measuring the quality of the E1 line.
Running Loopbacks
ETX-5300A 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 card at a time. E1 Port Diagnostics section
above details signal paths when local and remote loopbacks are activated.
To activate a loopback:
test.
2. At the config>port>e1>(slot/port/tributary)# prompt, enter loopback,
followed by loopback type (local or remote) and its duration 160 min.
To deactivate a loopback:
6-54
E1 Ports
In the config>port>e1>(slot/port/tributary)# prompt, enter no loopback.
ETX-5300A Ver. 1.0
Chapter 6 Ports
BER Testing
Bit Error Rate test is used for measuring the quality of the E1 line.
To run BER testing:

test.
2. At the config>port>e1>(slot/port/tributary)# prompt, enter bert, followed by
pattern pattern_type and inject-error none or error_type.
To display BERT results:

1. Make sure that BERT is running.
2. At the config>port>e1>(slot/port/tributary)# prompt, enter show bert.
The BERT results are displayed.
ETX-5300A>config>port>e1(1/1/1)# show bert

Status
: Sync
Bit Error Count : 0
Pattern
: None
Inject Error
: 10e-3
Run Time (Sec) : 10
ES (Sec)
: 0
Sync Loss (Sec) : 0
Result
: OK
To reset counters while BERT is running
At the config>port>e1>(slot/port/tributary)# prompt, enter clear-bertcounters.
To deactivate BER testing:
At the config>port>e1>(slot/port/tributary)# prompt, enter no bert.
Example
ETX-5300A Ver. 1.0
To configure internal E1 interface:
E1 name e1_1_1_1
Line type G.732N
Idle code 0xFF
Transmit clock source Loopback
E1 Ports
6-55
Chapter 6 Ports
ETX-5300A# configure port e1 1/1/1

ETX-5300A>config>port>e1(1/1/1)# name e1_1_1_1
ETX-5300A>config>port>e1(1/1/1)# line-type g732n
ETX-5300A>config>port>e1(1/1/1)# idle-code 0xFF
ETX-5300A>config>port>e1(1/1/1)# tx-clock-source loopback
ETX-5300A>config>port>e1(1/1/1)# pm-enable
ETX-5300A>config>port>e1(1/1/1)# no shutdown
detected.

Message
Description
Cannot change line type when service is

defined
Line type cannot be changed if a pseudowire service has been

defined on a port

the loopback first
Invalid Dsx1IdleCode value
Invalid idle code value
6.4
T1 Ports
Internal T1 ports of the E5-cTDM-4 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.
6-56
T1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Factory Defaults
ETX-5300A is supplied with all E1 ports disabled. Other parameter defaults are
listed in the table below.
Parameter
Default Value
line-type
unframed
path-interval-threshold cv
path-interval-threshold es
80
path-interval-threshold ses
10
path-interval-threshold sefs
path-interval-threshold css
path-interval-threshold uas
10
idle-code
7F
out-of-service
00
tx-clock-source
loopback
loopback
no loopback
trail-mode
terminated
T1 Line Signal
The basic T1 line signal is coded using the alternate mark inversion (AMI) rules.
The AMI format cannot transmit long strings of 0s because such strings do not
carry timing information. Therefore, the AMI signal source must generate a signal
with a guaranteed minimum of 1 density. The minimum average 1 density
required by the applicable standards is 1:8. Therefore, when a T1 signal is
transmitted over an AMI line, each frame timeslot must include at least one 1
bit. This effectively reduces user data rate to 56 kbps per timeslot, and precludes
the provisioning of clear channel capability (CCC).
This problem is circumvented by using modified line codes that perform zero
suppression by substituting special codes for long 0 strings. The generally
accepted zero suppression methods are B7 and B8ZS.
ETX-5300A Ver. 1.0
With B7, the maximum length of 0 strings in the user data must not exceed
seven zeros. (When a longer string is detected, the seventh bit is changed to
one, to meet the minimum 1 density requirement and thus ensure that
the remote end can properly recover the clock signal.). Although this
requirement can be fulfilled in many applications, it does not provide 64 kbps
clear channel capability. Therefore, when the B7 line code is used, inband
management is not supported.
Only the B8ZS zero suppression method provides clear channel capability, and
the 1 density requirement no longer restricts user data characteristics. This
means that each T1 frame timeslot can support the full 64 kbps.
T1 Ports
6-57
Chapter 6 Ports
Since the AMI coding does not affect the signal transmitted to the line, it is also
called transparent coding. This emphasizes the fact that although the other methods
are also transparent to users data, perfect transparency is achieved only when the
zero-string substitution sequences are correctly recognized. Thus, the other methods
are more sensitive to transmission errors (transmission errors may affect the
decoding of zero-string substitution sequences).
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 Figure 6-17.
8 Bits/Channel
Byte Organization
(D4 Frame - See NOTE)
Frame
Organization
Ft C H C H
24 Channels/Frame
or
1 2
Frame = 193 Bits
Fs
CH
13
FR FR
1 2
FR
7
Multiframe
Organization
NOTE:
In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24
8
A
B
Other Frames
Frame 6
Frame 12
Bit B Conveys
Signaling
Information
CH
24
FR FR
11 12
Multiframe
SF (D4) 12 Frames
ESF: 24 Frames
Figure 6-17. 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.
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.
6-58
T1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
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:
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:
ETX-5300A Ver. 1.0
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.
Bit Error Rate Test for measuring the quality of the T1 line.
T1 Ports
6-59
Chapter 6 Ports
Note
You can run only one regular or inband-activated local loopback per the
E5-cTDM-4 card.
Local Loopback
Figure 6-15 shows the signal paths during a local loopback on an internal T1 port.
Internal T1
TDM
PSN
Framer
Mapper
Figure 6-18. Local Loopback on Internal T1 Port, Signal Paths

As shown in Figure 6-15, 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-5300A.
Remote Loopback
Figure 6-16 shows the signal paths during a remote loopback on an internal E1
port.
As shown in Figure 6-16, 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 card.
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-60
T1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Internal T1
TDM
PSN
Framer
Mapper
Figure 6-19. 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-5300A, and part of the internal ETX-5300A signal
path that handle the routing of the signals up to the tested T1 port, including the
SONET mapper of the E5-cTDM-4 card.
BER Testing
A BERT typically consists of a test pattern generator and a receiver that is set to
the same pattern. BER testers can be used together at two ends of transmission
link to check data integrity in both directions. Alternatively, a single bit tester can
be used at one end of the link with a loopback activated at the remote end to
return the transmitted data.
BER testing can be activated on the entire internal port or on the selected
timeslots with or without the injection of errors randomly or at a constant rate.
Multiple BERTs can be run simultaneously on separate T1 ports.
Inband Loopbacks
ETX-5300A 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-5300A supports the following inband loopback activation methods:
ETX-5300A Ver. 1.0
CSU, according to ANSI T1.403 and AT&T TR 54016. This method is relevant
for framed modes only.
T1 Ports
6-61
Chapter 6 Ports
NIU (FAC1 and FAC2), according to Telecordia GR-312. This method is relevant
for framed and unframed modes.
Custom, user-defined 38 bit long loopback activation and deactivation

patterns. This method is relevant for framed and unframed modes.
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 at least one enabled pseudowire with a
valid cross-connection is assigned to the port.
Task
Command
Comments
Assigning short
description to port
name <string>
Masking/unmasking
alarms generated by the
internal T1
no shutdown
shutdown masks alarms generated by the

internal T1
Specifying T1 framing
mode
line-type {unframed | esf | sf}
When using one of the framed modes, you

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
performance monitoring
data collection
pm-enable
Setting path CV, ES, SES,

SEFS, CSS and UAS
counter value during a
15-min interval starting
from which a trap is sent
path-interval-threshold [cv <cv-value 0

16383>] [es <es-value 0900>] [ses <sesvalue 0900>] [sefs <sefs-value 0900>]
[css <css-value 0900>] [uas <uas-value
0900>]
Controlling inband
loopback activation
inband-loopback {local | remote} csu
no pm-enable
inband-loopback {local | remote} niu {fac1

| fac2}
inband-loopback {local | remote} program
<loop-up-code> <loop-up-len>
<loop-down-code> <loop-down-len>
no inband-loopback
6-62
T1 Ports
no inband-loopback disables inband

loopback.
One loopback activation and one loopback
deactivation code are allowed per the
E5-cTDM-4 card.
To activate an inband loopback in a far-end
unit, you must enable pseudowire OAM
functionality.
ETX-5300A Ver. 1.0
Chapter 6 Ports
Task
Command
Comments
Activating BER testing,

defining test pattern and
error injection
bert [pattern {2e-10 | 2e-15 | 2e-20 | 2e23 | 511 | 2047| qrss | 2e-11}] [inject-error
{none | single | 10e-1 | 10e-2 | 10e-3 |
10e-4 | 10e-5 | 10e-6 | 10e-7}]
no bert disables BER testing
no bert
Specifying the code
transmitted to fill unused
timeslots in T1 frames
idle-code { 00 to FF (hexa) }
Selecting the code

transmitted during
out-of-service period
out-of-service <00FF>
This parameter is valid for framed modes

only.
Only one idle code value is allowed per the
E5-cTDM-4 card.
The hexadecimal number is in the range of 0
to FF (two digits)
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 card.
See Alarm Indications and Fault Propagation
in the TDM Pseudowires of Chapter 8
Controls the propagation

of alarm indications
trail-mode {terminated | extended}
Selects the reference

source used by the
transmit path of this port
tx-clock-source {domain <domain-num> |

loopback | pw }
Activating diagnostic
loopback
loopback { local | remote } [ duration <1

60>]

range
no loopback
no loopback deactivates it.
show status
show statistics
Displaying Status
You can display current status of any internal T1 port on an E5-cTDM-4 card.
To display E1 port status:
At the config>port>t1(slot/port/tributary)#prompt, enter show status.

The T1 port status is displayed.
ETX-5300A>config>port>t1(1/1/1)# show status

Name
: T1-1-1-1
: Down
Operational Status
: Down
Loopback
: Off
The E1 interface status screens provide information on the port name,
administrative/operational status, and loopback status.
ETX-5300A Ver. 1.0
T1 Ports
6-63
Chapter 6 Ports
Internal T1 ports of ETX-5300A 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-11.
Task
Command
Comments

interval statistics


12:00 midnight

midnight

96)

ETX-5300A>config>port>t1(4/1/1)# show statistics current

Current
--------------------------------------------------------------Time Elapsed (Sec) : 0
Valid Intervals
: 0
Path
--------------------------------------------------------------CV
: 0
Rx Frames Slip
: 0
ES
: 0
UAS
: 0
BES
: 0
FC
: 0
SES
: 0
SEFS
: 0
Note
For unframed T1 ports, only FC counter is available.

Table 6-11. Internal T1 Statistics
Parameter
Description
CV
Number of CRC-4 errors
Rx Frames Slip
Number of received Frames Slip events
6-64
T1 Ports
ETX-5300A Ver. 1.0
Chapter 6 Ports
Parameter
Description
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 804 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-5300A# configure port t1 1/1/1

ETX-5300A>config>port>t1(1/1/1)# name t1_1_1_1
ETX-5300A>config>port>t1(1/1/1)# line-type esf
ETX-5300A>config>port>t1(1/1/1)# idle-code 0xFF
ETX-5300A>config>port>t1(1/1/1)# tx-clock-source loopback
ETX-5300A>config>port>t1(1/1/1)# pm-enable
ETX-5300A>config>port>t1(1/1/1)# no shutdown
detected.
ETX-5300A Ver. 1.0
T1 Ports
6-65
Chapter 6 Ports

Message
Description
Cannot change line type when service is

defined
Line type cannot be changed if a pseudowire service has been

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 Dsx1IdleCode value
Invalid idle code value
6.5
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.
GbE and 10GbE cards introduce logical ports that serve as management entities
(SAG) and flow aggregation points (SAP). Figure 6-20 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.
6-66
ETX-5300A Ver. 1.0
Chapter 6 Ports
Flow
SAP
1-10 GbE ports on E5-GbE-20

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

SAG
Flow
SAP
Figure 6-20. I/O Ethernet Card

Each I/O Ethernet card has two SAGs, serving 110 and 1120 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 512 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.
Task
Command
Comments
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:
ETX-5300A Ver. 1.0
Slot 1
6-67
Chapter 6 Ports
Port 1
Name SAG_1_1
Queue group q_group_SAG_2_level_default.
ETX-5300A>config>port>sag 1/1
ETX-5300A>config>port>sag(1/1)# name SAG_1_1
ETX-5300A>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 (512) has been

reached
Cannot bind SAG queue group to

Ethernet port or LAG
A queue group that has already been bound to a SAG cannot be

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

queue block
Level-1 queue block bound to SAG cannot include shaper
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-5300A does not have SVIs.
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-22). ETX-5300A supports up to 4000 SVIs.
6-68
ETX-5300A Ver. 1.0
Chapter 6 Ports
ETX-5300A
LB IP
Router
RIF
SVI
SVI
BP
SVI
User
SVI
BP
BP
OOB
BP
NET
Bridge
BP
User
SVI
SVI
BP
SVI
SVI
MEF-8
Pseudowires
Flow
BP
SVI
BP
Bridge
SVI
MEF-8
Pseudowire
Flow
BP
BP
SVI
SVI
SVI
MEF-8
Pseudowire
I/O Card STM-1/OC-3 Port
Figure 6-21. Router and Bridge Connections with SVIs Identified
Flow
TDM Pseudowire
Processing
Figure 6-22. Layer-2 Pseudowire Connection
Configuring SVIs
To configure an SVI:
2. Enter svi <svi_number>, followed by the SVI type (bridge | pw | router),
depending on whether you intend to attach a flow to bridge, pseudowire or
router.
The config>port>svi(number)# prompt is displayed.
ETX-5300A Ver. 1.0
6-69
Chapter 6 Ports
Note
no svi <svi_number> entered at the config>port prompt, deletes the SVI.

Task
Command
Comments
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-5300A>config>port>svi 1 bridge
ETX-5300A>config>port>svi(1)# name svi_1_bridge
detected.

Message
Description
SVI cannot be created: max number of

SVIs has been reached
SVI cannot be created because the maximum number of SVIs per

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

be bound
SVI cannot be modified because only bridge-type SVIs can be

bound to this entity
Modify failed: SVI is already bound to

another bridge port
SVI cannot be modified because it is already bound to another

bridge port
Modify failed: flow is bound to SVI
SVI cannot be modified because flows are bound to it
6-70
ETX-5300A Ver. 1.0
Chapter 7
Resiliency
The modular, distributed architecture of ETX-5300A 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 for STM-1/OC-3 ports.
This chapter describes port and service protection mechanisms (LAG, ERP and
APS), as well as main card redundancy. Timing system redundancy is detailed in
Chapter 9.
7.1
Main Card Redundancy
Redundancy for the ETX-5300A control subsystem is supported only when the
ETX-5300A chassis includes two operational main cards. If only one is installed, it
is automatically selected and redundancy cannot be activated.
ETX-5300A 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.
Benefits
Main card redundancy with automatic switchover ensures continuous service
provisioning. It provides a hot-standby capability for the ETX-5300A 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-5300A system
control functions.
ETX-5300A Ver. 1.0
7-1
Chapter 7 Resiliency
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-5300A 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:

1. Navigate to configure protection main-card.
The config>protection>main-card# prompt is displayed.
2. At the config>protection>main-card# prompt, enter manual-switch to toggle
between main card A and B.
ETX-5300A#config protection main-card

ETX-5300A#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.
2. At the config>protection>main-card# prompt, enter show status.
ETX-5300A#config protection main-card

ETX-5300A#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.
7-2
ETX-5300A Ver. 1.0
detected.

Message
Description
Manual switch cannot be performed:

Mate card's operational status is down.
Manual switch has failed because the secondary main card is not
operational
Manual switch cannot be performed:

Mate card doesn't exist.
Manual switch has failed because only one main card is installed
in the chassis
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-5300A supports LAG for up to two members, consisting of Ethernet ports
located on the same or different cards.
Standards and MIBs

IEEE 802.3-2005
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-5300A 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-5300A Ver. 1.0
7-3
ETX-5300A supports LAG for up to two members, consisting of Ethernet ports

located on the same or different cards.
Intra-Card LAG
With intra-card LAG, the two aggregation group members reside on the same
E5-MC-4, E5-10GBE-2 or E5-GBE-20 card.
For E5-GBE-20 card, when the LAG ports belong to the same 10-port group
(ports 110 or ports 1120), 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.
Rx
Main or I/O Card
LAG
Tx
Tx
Rx
Figure 7-1. Intra-Card LAG

For E5-GBE-20 card, when the LAG ports belong to the different 10-port groups,
and for the E5-10GBE-2 card, the LACP is permanently enabled. The LACP uses
the STBY option to force the opposite party to receive and transmit on the same
port.
Inter-Card LAG
With inter-card LAG, the two aggregation group members reside on different
E5-MC-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.
7-4
ETX-5300A Ver. 1.0
Main or I/O Card
Rx
LAG
Tx
Tx
Main or I/O Card
Rx
Figure 7-2. 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.
Configuring LAG
This section explains how to define a link aggregation group (LAG) and enable link
aggregation control protocol (LACP). ETX-5300A 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, you must configure flow with an
L2CP profile with peer action for the LACP address (01-80-c2-00-00-02). The
flow must have the following attributes:
Untagged classification
Ingress port LAG
Egress port according to application requirements.
If you use the flow only to peer the LACP frames and do not need to forward the
untagged traffic, discard it, using the drop command on the flow.
Figure 7-3 illustrates flows in inter-card LAG between two main cards. LACP flow
can be optionally dropped.
ETX-5300A Ver. 1.0
7-5
Flow 1*
(LACP)
Port
A/X
LAG
Flow 2
(Data)
Any
Port
Flow 3
(Data)
Port
B/X
* Flow 1 can be dropped, if unnecessary
Figure 7-3. 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
Flow
Port
1/2
LAG
SAP
1/1/X
Data
Flow
LACP
Flow
Any
Port
Data
Flow
SAP
1/1/X
Port
1/3
Any
Port
Data
Flow
Figure 7-4. LAG-SAP Connection in Intra-Card LAG
7-6
ETX-5300A Ver. 1.0
Inter-card LAG for E5-GBE-20 cards:
LAG between ports belonging to the first ten-port group (110): Connect
LAG to a SAP, belonging to the first 10-port group (SAP slot/1/x)
LACP
Flow
Port
1/2
LAG
SAP
1/1/X
Data
Flow
LACP
Flow
Data
Flow
SAP
1/1/X
Port
2/3
Any
Port
Any
Port
Data
Flow
Figure 7-5. LAG-SAP Connection in Inter-Card LAG over Ports 110 in E5-GBE-20 Cards
LAG between ports belonging to the second ten-port group (1120):

Connect LAG to a SAP, belonging to the second 10-port group
(SAP slot/2/x)
LACP
Flow
Port
1/11
LAG
SAP
1/2/X
Data
Flow
LACP
Flow
Data
Flow
SAP
1/2/X
Port
2/12
Any
Port
Any
Port
Data
Flow
Figure 7-6. LAG-SAP Connection in Inter-Card LAG over Ports 1120 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
Flow
Port
1/1
LAG
Port
2/1
SAP
1/1/X
Data
Flow
LACP
Flow
Any
Port
Data
Flow
SAP
1/1/X
Any
Port
Data
Flow
Figure 7-7. LAG-SAP Connection in Inter-Card LAG over Ports 1 and 1 in E5-10GBE-2 Cards
ETX-5300A Ver. 1.0
7-7
LAG between ports 2 and 2: Connect LAG to a SAP, belonging to the

second 10-port group (SAP slot/2/x)
LACP
Flow
Port
1/2
LAG
SAP
1/2/X
Data
Flow
LACP
Flow
Data
Flow
SAP
1/2/X
Port
2/2
Any
Port
Any
Port
Data
Flow
Figure 7-8. 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-5300A 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
(LACP)
Port
1/2
LAG
Port
3/2
SAP
1/1/1
Flow 2
(LACP)
Any
Port
Flow 4
(Data)
Flow 3
(Data)
SAP
1/1/2
Port
1/15
Flow 5
(Data)
Figure 7-9. Permitted PtP Flow for LAG
7-8
ETX-5300A Ver. 1.0
Not permitted: Flow from the LAG on port 1/2 and port 3/2 to port 1/3.
SAP
1/1/1
Flow 1
(LACP)
Port
1/2
LAG
Flow 3
(Data)
Flow 2
(LACP)
Any
Port
Flow 4
(Data)
SAP
1/1/2
Port
3/2
Port
1/3
Flow 5
(Data)
Figure 7-10. Not Permitted PtP Flow for LAG
To configure the LAG:

1. Navigate to configure port lag 144.
The config>port>lag(144)# prompt is displayed.
Task
Command
Comments
Assigning an admin key to the

LAG to indicate the port speed
admin-key { fast-ethernet |
giga-ethernet | ten-giga-ethernet }
You must define admin key before

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.
Adding a port to the LAG
bind etherent <slot/port >
no bind removes a link from the LAG
Selecting classification key
classification-key [ {vlan }] [{ innervlan }] [ { p-bit }] [ { ip-precedence

}] [ { ip-dscp }]
See the Classification section in

Appendix B for description of
classification keys available for
directly- and indirectly-attached
ports
Assigning L2CP profile
l2cp profile <l2cp profile name>
no l2cp profile removes L2CP profile

association
ETX-5300A Ver. 1.0
7-9
Task
Command
Comments
Enabling LACP and setting LACP

parameters: operation mode
(active or passive) and time to
wait before sending LACP frames
(long or short)
lacp [tx-activity {active | passive}]

[tx-speed {slow | fast}]
[sys-priority <sys-priority>]
tx-activity:
active LAG interface periodically
transmits LACP frames (LACPDUs) to
all links with LACP enabled
passive LAG interface does not
initiate the LACP exchange, but
replies to received LACPDUs.
tx-speed:
slow Three seconds
fast_ 90 seconds.
no lacp disables LACP protocol.
The sys-priority parameter
Assigning a queue group profile
queue-group profile <profile name>
See the Traffic Management section

in Appendix B for description of
queue groups and their elements.
no queue-group removes queue
group association
Administratively enabling LAG
no shutdown
shutdown disables the LAG
Selecting Ethertype for LAG
tag-ethernet-type <value>
See the Ethertype section in

Appendix B for description of
Ethertype values available for
directly- and indirectly-attached
ports.
no tag-ethernet-type removes
Ethertype association
Assigning a name
name <string>
Displaying bind status
show bind
Displaying LAG status
show status
Displaying the LAG members

statistics
show lacp-statistics ethernet

<slot/port>
Displaying LAG members status
show lacp-status ethernet

<slot/port>
no name removes LAG name
Deleting the LAG

Before deleting the LAG verify that:
7-10
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.
ETX-5300A Ver. 1.0
To delete the LAG:
At the config>port# prompt, enter no lag(144)#.
Displaying LAG Status

You can display current status of existing link aggregation group.
To display LAG status:
At the config>port>lag(144) #prompt, enter show status.

The LAG status is displayed.
ETX-5300A>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
main-a/1
main-a/2
Admin
up
up
Oper
up
up
LACP
sync
out-of-sync
Protection
active
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(144) #prompt, enter show lacp-status ethernet

<slot/port>.
The LACP statistic counters are displayed.
ETX-5300A>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.
ETX-5300A Ver. 1.0
7-11
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(144) #prompt, enter show lacp-statistics ethernet

<slot/port>.
The LACP statistic counters are displayed.
ETX-5300A>config>port>lag(1)$ show lacp-statistics ethernet main-a/1

Rx
Rx
Rx
Rx
Tx
Tx
LACP Frames
Marker Frames
Unknown Frames
Illegal Frames
LACP Frames
Marker Response Frames
:
:
:
:
:
:
5,000
8,000
11,000
12,000
5,000
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
7-12
ETX-5300A Ver. 1.0
Counter
Description
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
Example
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 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.
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 for the LACP address (01-80-c2-0000-02).
5. Configure three flows:
Flow 1 from LAG 1 to any ETX-5300A port for LACP data with untagged
classification. In this example, port 3 on main card A is used for virtual
termination of LACP traffic.
Discard the flow data.
ETX-5300A Ver. 1.0
Flow 2 from port 3 on main card A to LAG 1 with VLAN 100 classification
Flow 3 from LAG 1 to port 3 on main card A with VLAN 100 classification.
7-13
Flow 1
(LACP)
Port
A/2
LAG
Port
B/4
Flow 2
(Data)
Port
A/3
Flow 3
(Data)
Figure 7-11. Inter-Card LAG between Two Main Cards

#*****************************Enabling_Ethernet_Ports************************
config port ethernet main-a/2
pm-enable
no shutdown
exit all
config port ethernet main-b/4
pm-enable
no shutdown
exit all
pm-enable
no shutdown
exit all
#*********************************End****************************************
#*****************************Configuring_LAG********************************
config port lag 1
admin-key ten-giga-ethernet
bind ethernet main-a/2
bind ethernet main-b/4
queue-group profile q_group_2_level_default
lacp tx-activity active tx-speed slow
no shutdown
exit all
#*********************************End****************************************
#***************************Assigning_Queue_Group_Profile********************
config port ethernet main-a/3 queue-group profile q_group_2_level_default
#*********************************End****************************************
#***************************Configuring_Classifier_Profiles******************
match untagged
exit all
config flows classifier-profile class100 match-any
match vlan 100
exit all
#*********************************End****************************************
#***************************Configuring_L2CP_Profile*************************
config port l2cp l2cp1
7-14
ETX-5300A Ver. 1.0
mac 01-80-c2-00-00-02 peer

exit all
#*********************************End****************************************
config flows flow 1
classifier classutg
ingress-port lag 1
egress-port ethernet main-a/3 queue-map-profile QueueMapDefaultProfile block
0/1
l2cp profile l2cp1
drop
pm-enable
no shutdown
exit all
config flows flow 2
classifier class100
egress-port lag 1 queue-map-profile QueueMapDefaultProfile block 0/1
ingress-port ethernet main-a/3
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.
ETX-5300A Ver. 1.0
7-15
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-0000-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
(LACP)
Port
1/2
SAP
1/1/1
Flow 3
(Data)
LAG
Port
A/3
Flow 4
(Data)
SAP
1/1/2
Port
3/2
Flow 2
(LACP)
Port
1/13
Flow 5
(Data)
SAP
3/1/1
Leave
Unused
SAP
3/1/2
Figure 7-12. Inter-Card LAG between Two I/O Cards

#*****************************Enabling_Ethernet_Ports************************
7-16
ETX-5300A Ver. 1.0
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*******************
config port ethernet 1/2 queue-group profile q_group_2_level_default
config port sag 1/1 queue-group profile q_group_SAG_2_level_default
#*********************************End****************************************
match untagged
exit all
config flows classifier-profile classAll match-any
match all
exit all
match vlan 100
exit all
#*********************************End****************************************
#***************************Configuring_L2CP_Profile*************************
ETX-5300A Ver. 1.0
7-17
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
egress-port sap 1/1/1 queue-map-profile QueueMapDefaultProfile block 0/1
l2cp profile l2cp1
drop
no shutdown
exit all
config flows flow 2
classifier classAll
ingress-port sap 1/1/1
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
egress-port ethernet 1/13 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all
config flows flow 5
classifier class100
ingress-port ethernet 1/13
gress-port lag 1 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all
#*********************************End****************************************
detected.
7-18
ETX-5300A Ver. 1.0

Message
Description
Bind failed: Services are configured on

port
Ethernet ports with flows assigned to them cannot be bound to

the LAG
Bind failed: Ports in LAG must reside on

same card type
In the inter-card link aggregation, LAG member ports must

belong to the same card type
Bind failed: Ports in LAG must both be

either between 1-10 or 11-20
In the intra-card link aggregation on E5-GBE-20 card, ports 110

and ports 1120 cannot share the same LAG
No shutdown failed: LAG must have

exactly 2 members
LAG member number has been exceeded
No shutdown failed: LACP must be

enabled when LAG is between 2 cards.
Inter-card LAG cannot be activated if LACP is not enabled
No shutdown failed: L2CP profile must

define a peer action for LACPDUs
In order to enable LACP for the LAG, the ports bound to the LAG
must have an untagged flow with an L2CP profile that specifies
peer action for MAC 0x02
No shutdown failed: L2CP profile

must be configured when LACP is
enabled
LAG cannot be activated if LACP profile is not attached to

aggregation group
Error : Exceeded maximum number of

LAGs
Maximum allowed number of LAGs per chassis is greater than 44
Error : Invalid LAG ID
LAG ID is out of range (144)
Error : Membership is not specified
LAG cannot be activated if no ports are bound to it
Error : Invalid port Bandwidth
Mismatch between LAG and member port capacity
Error : Invalid port number
Ethernet ports with invalid (non-existent) numbers cannot be

bound to LAG
Error : Number Of Ports Exceeds

Maximum
Maximum number of LAG members is above two
Error : Port already used in another

LAG
Selected port has already been configured as a LAG member
Error : LAG is enabled
An active LAG cannot be deleted or modified
Error : LAG members duplicated
The same Ethernet port has been bound twice to a LAG
Error : Given port is not a LAG member
An Ethernet port cannot be removed from the LAG if the port is

not bound to it
7.3
Ethernet Ring Protection (ERP)
A G.8032 Layer-2 Ethernet ring is used by ETX-5300A 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-5300A supports 16 rings (major
and sub-rings) per shelf.
ETX-5300A Ver. 1.0
7-19
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
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-5300A supports
up to 16 major rings and sub-rings.
Note
Ring port cannot be bound to a LAG.
Ring Topology
ETX-5300A supports different ring topologies, including single and interconnected
(ladder) ring topologies.
Figure 7-13. Single Ethernet Ring
7-20
ETX-5300A Ver. 1.0
Major Ring
Sub-Ring
Figure 7-14. Interconnected Ethernet Rings
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, root 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-15 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.
ETX-5300A Ver. 1.0
7-21

Traffic is Blocked
CCM
CCM
RPL Owner
CCM
CCM
CCM
CCM
Figure 7-15. 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.
Guard Period of time during which all received A-RPS messages are ignored
by the ERP mechanism. This prevents the ring nodes from receiving outdated
A-RPS messages circulating the network.
Hold-off Period of time during which the underlying Ethernet layer attempts
to filter out intermittent link faults before reporting them to the ERP
mechanism.
Administrative Commands
If there is a need to intervene into ERP operation for maintenance or any other
reason, the operator can issue a forced or manual switch command.
Note
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.
The manual and forced switch commands are temporary commands and do not
permanently change the location of the RPL.
Multiple Rings
Multiple rings with a common link are usually referred to as ladder network (see
Figure 7-16). In such networks a common VLAN is shared on more than one
physical ring. For example, a user connected to node E is communicating with a
user connected to node A over the same VLAN.
Ring topology includes a physical link between nodes G and C. It belongs to the
major ring and is used by the sub-ring as its R-APS channel.
7-22
ETX-5300A Ver. 1.0
Virtual Channel
Major Ring
Sub-Ring
Figure 7-16. Physical Ladder Topology

H
Major Ring
Sub-Ring
Figure 7-17. Major Ring and Sub-Ring

The following terms are commonly used for describing ladder ring topology:
Interconnection nodes Ring nodes that are common to both interconnected

rings (nodes C and G in Figure 7-16).
Major ring An Ethernet ring that controls a full physical ring and is
connected to the interconnection nodes on two ports (ring A-H-G-C-B in
Figure 7-16)
Sub-ring An Ethernet ring that is connected to a major ring at the

interconnection nodes. By itself, the sub-ring does not constitute a closed
physical ring. A sub-ring is connected to the interconnection nodes on only
one port (ring C-D-E-F-G in Figure 7-16). Link CG is not a part of the subring and it is controlled by the major ring. ETX-5300A supports up to five subrings per major ring.
R-APS virtual channel 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.
In a stable state the rings in Figure 7-16 have two RPL owners that prevent the
traffic from looping in the network (nodes E, A). 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. For example, if link G-F fails, only node E unblocks its
RPL port, while node A does not change the state of its RPL port.
ETX-5300A Ver. 1.0
7-23
If a shared link fails (link G-C), the RPL owner of the main ring (node A) unblocks
its port; however, the RPL port of the sub-ring (node E) remains blocked since
that link is declared as virtual channel for this ring.
Configuring ERP
To configure ERP:
1. In the configure>protection# prompt, enter erp followed by ring number (1
16) 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.
Task
Command
Making the ring compatible with

previous ERP implementations
backward-compatibility
Assigning node to a bridge

instance
bridge <132>
Assigning VLAN ID to user data
data-vlan <14094>
Comments
no backward-compatibility
no data-vlan
Using no before data-vlan

removes VLAN ID assignment to
user data.
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 subring, and the East and West
ports of the major ring.
Defining bridge port as an East

port of ERP node
east-port <bridge_port_number>
Sub-rings have East ports only
Defining bridge port as a West

port of ERP node
west-port <bridge_port_number>
Sub-rings do not have West

ports
Defining ERP node as an

interconnection node, sharing
more than one ring
interconnection-node
7-24
no interconnection-node
ETX-5300A Ver. 1.0
Task
Command
Comments
Defining node port type in

relation to RPL owner
port-type owner {east | west}
owner RPL owner
port-type neighbor {east | west}
neighbor port directly

connected to RPL owner
port-type next-neighbor {east | west}
next-neighbor port connected

to RPL owner via neighbor
port-type ring-node
ring-node regular ring port,

which is not connected to RPL
owner
Configuring dedicated VLAN for
R-APS messages
r-aps [vlan <14094>] [vlan-priority

<07>] [mel <07>]
R-APS settings must be the same

for all ring members
Configuring the revertive mode
revertive
This mode is relevant to the RPL

owner node.
no revertive
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
Failure (SF) condition from the
Ethernet OAM service layer
sf-trigger {east | west} mep <md-id>

<ma-id> <mep-id>
no sf-trigger {east | west}
Before enabling SF propagation,

verify that relevant CFM
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

ERP interface
no shutdown
To avoid traffic loops, always

enable Ethernet ports only after
enabling Ethernet rings.
shutdown disables the ERP.
Connecting previously defined

sub-ring to a major ring
ETX-5300A Ver. 1.0
sub-ring <ring_number>
no sub-ring
This option available for major

rings only. The sub-ring number
must be lower than the number
of the major ring it is assigned
to.
7-25
Task
Command
Comments
Defining guard and hold-off

periods in msec
timers [guard <102000>] [holdoff

<010000]
Guard timer is used by the ERP

mechanism to prevent ring
nodes from receive outdated RAPS 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.
Blocking the East or West port of

a ring node
manual-switch {east-port | west-port }
The manual switch command can

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

a ring node
forced-switch {east-port | west-port }
The forced switch can be applied

to any number of nodes in the
ring.
Clearing the existing switch

commands
clear
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.
Task
Command
Comments
Enabling virtual channel over

shared link
virtual-channel
Currently, the virtual channel is

permanently enabled
no virtual-channel
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.
7-26
ETX-5300A Ver. 1.0
ETX-5300A>config>protection>erp(1)$ show status

Bridge Number : 0
RPL Link
: Not Owner
Ring State
: Init
East Port
: 0
East Port Status : Forward

West Port Status : Forward
Local SF Source
Local SF Source
West Port
: 0
: Not Applicable
: Not Applicable
ERP status provides information on:
Bridge number
Bridge ports assigned to be East and West ring ports
RPL link role:
RPL owner This node owns the RPL and blocks or unblocks the RPL
as conditions require. This node initiates the R-APS message.
Ring state:
Not owner All other nodes on the ring (that is, those that are not
the RPL owner node) operate as normal nodes and have no special
role on the ring
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).
Protected A failure occurred on the ring. A not-owner node have
traffic blocked on the ring port that connects to the failed link. The
RPL owner, if it is not at one end of the failed link, unblocks the RPL
port so both ports are active.
East/West Port Status:
Forward Port is forwarding data
Blocked Port is blocked
East/West Port Local SF Source Local Signal Failure source:
Server Layer
OAM CFM
Admin
Displaying ERP Statistics

When the G.8032 Ethernet Ring Protection (ERP) is enabled, ETX-5300A allows
collecting statistics on R-APS messages sent and received by the East and West ports.
To display ERP statistics:
ETX-5300A Ver. 1.0
In the config>protection>erp(erp_number)$ prompt, enter show statistics..
7-27
The ERP statistic counters are displayed.

ETX-5300A>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-5. ERP Statistic Counters

Counter
Description
R-APS SF Message Tx/Rx
Total number of R-APS Signal Fail (SF) messages received or transmitted

by East/West port.
Received R-APS Signal Fail message indicates a failed port in the ring.
Transmitted R-APS Signal Fail message indicates a failed port in the
node.
R-APS NR Message Tx/Rx
Total number of R-APS No Request (NR) messages received or

transmitted by East/West port.
Received R-APS No Request message indicates absence of failed ports in
the ring.
Transmitted R-APS No Request message indicates that the node fixed its
failed port.
R-APS NR, RB Tx/Rx
Total number of R-APS No Request (NR), RPL Blocked (RB) messages

received or transmitted by East/West port.
Received R-APS No Request, RPL Blocked message indicates that RPL
port is blocked and all other not-failed blocked ports are unblocked in
the ring.
Transmitted from the RPL No Request, RPL Blocked message indicates
that RPL port is blocked.
Total Valid Rx/Tx
Total number of valid R-APS messages received or transmitted by

East/West port
Total Errors Rx/Tx
Total number of errored R-APS messages received or transmitted by

East/West port
Example
Figure 7-18 and script below illustrate configuration a G.8032v2 ring over main
card ports.
7-28
ETX-5300A Ver. 1.0
Ethernet
Ring
Flow 1
Flow 2
SAP
Fl. 35
Port 1
Flow 16
Main Ethernet
Card A
Fl. 34
VLAN
1500
VLAN
1500
Flow 15
East
SVI 1
Flow 30
BP 1
Port 1
VLAN
1500
SVI 3
I/O Ethernet
Card 1
BP 3
Flow 31
Fl. 36
Bridge
BP 2
Fl. 3
Fl. 4
Fl. 17
Fl. 18
BP 4
West
(RPL Owner)
SVI 4
SVI 2
Fl. 10 SAP
Fl. 9
VLAN
500
VLAN
900
VLAN
500
Port 1
Fl. 32
Fl. 33
Port 1
Fl. 11
I/O Ethernet
Card 2
Main Ethernet
Card B
Figure 7-18. 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-18):
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-18):
ETX-5300A Ver. 1.0
7-29
Note
Classifier profiles for VLANs 500, 900 and 1500
Configure data flows, as illustrated in Figure 7-18
VLAN 900 is swapped to VLAN 500 on flow 9. VLAN 500 is swapped to VLAN 900
on flow 11.
9. Enable the main and I/O card ports.
#*********************Assigning_Queue_Group_Profiles*************************
config port ethernet main-b/1 queue-group profile q_group_2_level_default
exit all
#*********************************End****************************************
#*********************Selecting_Classification_Keys**************************
config port ethernet main-a/1 classification-key vlan p-bit
config port ethernet main-b/1 classification-key vlan p-bit
config port ethernet 1/1 classification-key vlan p-bit
exit all
#*********************************End****************************************
#***************************Configuring_SVIs*********************************
config port svi 1 bridge
exit all
exit all
exit all
exit all
#*********************************End****************************************
#*************************Binding_Bridge_Ports_to_SVIs***********************
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
7-30
ETX-5300A Ver. 1.0

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
ETX-5300A Ver. 1.0
7-31
config flows flow 3

ingress-port ethernet main-b/1
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
config flows flow 10
classifier classall
egress-port svi 4
mark all
vlan 500
exit
pm-enable
no shutdown
exit all
7-32
ETX-5300A Ver. 1.0

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

classifier class1500
egress-port svi 1
pm-enable
no shutdown
exit all
ETX-5300A Ver. 1.0
7-33
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****************************************
7-34
ETX-5300A Ver. 1.0
#****************************Enabling_Ports**********************************
config port ethernet main-a/1 no shutdown
config port ethernet main-b/1 no shutdown
config port ethernet 1/1 no shutdown
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
VLAN does not exist
Selected VLAN does not exist
Cannot disable the ring with active physical

ports
The ring cannot be disabled if it has active physical 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

Owner
WTR timer can be set only for RPL 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
ETX-5300A Ver. 1.0
7-35
Message
Description
East and West ports must be different
Different bridge ports must be defined as East and West
Cannot assign ERP node to bridge instance

after configuring East/West ports
A ring node must be assigned to a bridge instance before

configuring East/West ports
Cannot modify East/West port before

assigning ERP node to bridge instance
East/West ports can be modified after assigning a ring

node to a bridge instance
Cannot add data VLAN before assigning ERP

node to bridge instance
Data VLAN must be defined after assigning a ring node to a

bridge instance
Cannot disable major ring with active subrings
A major ring cannot be disabled if it has a sub-ring

attached to it
Major ring of the specified sub-ring is not

active
The major ring of the specified sub-ring has not been

enabled
Major ring of the specified sub-ring does not

exist
A sub-ring cannot be configured if a major ring does not

exist
Illegal node port type in relation to another

ring member
Not a valid value for the current node configuration. For

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
Cannot run FS or MS command in backwardcompatibility mode
Force switch and manual switch commands are not

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

virtual channel
R-APS VLAN ID can be set only for an active virtual channel
Cannot configure R-APS VLAN priority for

inactive virtual channel
R-APS VLAN priority can be set only for an active virtual

channel
Cannot modify virtual channel bound to subring
A virtual channel attached to a sub-ring cannot be modified
Cannot modify this parameter, delete and recreate the ring
This parameter cannot be modified, you must delete and

re-create the ring
Maximum number of sub-rings per major ring

exceeded
The maximum number of sub-rings (5) per major ring has

been reached
Sub-ring with specified index does not exist
The selected sub-ring does not exist
Major ring node must be configured as

interconnection node
One of the major ring nodes must be configured as an

interconnection node to accommodate a sub-ring
7-36
ETX-5300A Ver. 1.0
Message
Description
Sub-ring node must be configured as

One of the sub-ring nodes must be configured as an

Cannot enable backward-compatibility mode

when FS command is active
Disable the force switch command to operate the ring in

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

a sub-ring
First, remove all sub-rings bound to the major

ring
This action requires deleting all sub-rings belonging to the

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

configured data VLAN
A ring with configured data VLAN
Major ring is assigned to a different bridge

instance
The major ring is already assigned to another bridge

instance
The sub-ring is already bound to another

major ring
The sub-ring cannot be attached to the ring, because it is

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

bridge number
A ring without a port assigned to the bridge instance

cannot be activated

East port
A ring without configured East port cannot be activated

West port
A ring without configured West port cannot be activated
Cannot activate a ring without configured RAPS VLAN
A ring without configured R-APS VLAN cannot be activated
Cannot activate a ring without configured RAPS MEL
A ring without configured R-APS MEL cannot be activated
Cannot activate a ring without R-APS VLAN

configured for virtual channel
A ring without R-APS VLAN ID, configured for the virtual

channel, cannot be activated
Cannot activate a ring without R-APS VLAN

priority configured for virtual channel
A ring without R-APS VLAN priority, configured for the

virtual channel, cannot be activated
Cannot activate a virtual channel without

configured R-APS VLAN ID and priority for
sub-ring
A virtual channel without R-APS VLAN ID and priority,

configured for the sub-ring, cannot be activated
ETX-5300A Ver. 1.0
7-37
7.4
Automatic Protective Switching (APS)
ETX-5300A provides 1+1 APS line redundancy for rapid restoration of service in
case of line failure. When two TDM cards operate in APS mode for hardware
redundancy, they ensure 50 ms restoration of service in case of line faults.
Standards and MIBs

Telecordia GR-253-CORE, ITU-T G.841, RFC 3498
Benefits
APS switches over traffic with minimal loss of data, thus avoiding time-consuming
reroutes. With APS, 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 3. The effect
of a failure is greatly minimized, and a fast switchover guarantees minimal effect
on the network.
Factory Defaults
By default, APS is disabled.
In 1+1 APS, ETX-5300A provides a 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.
Working and the protection ports can reside on the same or different E5-cTDM-4
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 card
(intra-card APS), 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 cards
(inter-card APS) that are already assigned to an I/O card protection group,
provided that:
7-38
The working port is on the working card
The protection port is on the protection card
ETX-5300A Ver. 1.0
The working and protection ports have the same port number.
APS 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.
Note
PW services cannot be assigned to SDH/SONET ports which are not APS members,
when an inter-card APS 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 members, no pseudowire services are available on ports 2, 3 and 4
of both cards.
Each APS group includes up to two members. ETX-5300A can have up to eight
APS instances per chassis.
APS Architecture
ETX-5300A APS 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
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-19. APS 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
ETX-5300A Ver. 1.0
7-39
(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:
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-5300A 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-7. 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
Force-switch-to-working (causes a switchover)
7-40
ETX-5300A Ver. 1.0
Interface Conditions
Allowed Command (1+1 Unidirectional Mode)
Working is active, protection is shut down
Working is reset, protection is active
Force-switch-to-working (causes a switchover)
Working is active, protection is reset
Configuring I/O Card Protection

If you intend to configure inter-card APS, 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 must reside on the working card of the I/O
card protection group
Protection port of the inter-card APS must reside on the protection card of
the I/O card protection group.
To add an I/O card protection group:

1. Navigate to configure protection.
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:
Task
Command
Comments
Defining working (active) and

protection (standby) I/O cards
bind {working <slot> | protection

<slot>}
Using no before bind removes a

card from I/O card protection
group
Administratively enabling I/O

card protection group
no shutdown
When the APS group is 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

group status
ETX-5300A Ver. 1.0
show status
7-41
Configuring APS
Use the following procedure to configure redundancy for the ETX-5300A
SDH/SONET links.
To add an APS group:

1. Navigate to configure protection.
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:
At the config>protection>aps(group name)# prompt, enter all necessary

commands according to the tasks listed below:
Task
Command
Comments
Defining protection (standby)

and working (active) links
bind {protection sdh-sonet

<slot/port> | working sdh-sonet
<slot/port>}
Using no before bind removes a

link from protection group
Administratively enabling APS

group
no shutdown
shutdown disables APS group
Forcing traffic to the working

port
force-switch-to-working
Manually switches to the working

link, unless a request of equal or
higher priority is in effect
Forcing traffic to the protection

port
force-switch-to-protection
Manually switches to the

protection link, unless a request
of equal or higher priority is in
effect
Manually switching traffic to the

working port
manual-switch-to-working
Use this command to revert the

communication link back to the
working interface before the wait
to restore (WTR) time has expired
Manually switching traffic to the

protection port
manual-switch-to-protection
Use this command when you need

to perform maintenance on the
working port
Preventing a working link from

switching to a protection link
lockout-of-protection
This command prevents the circuit

from switching to a protection
interface in the event that the
working circuit becomes
unavailable
Clearing manual, force and

lockout commands
clear
Displaying APS status
show status
7-42
ETX-5300A Ver. 1.0
Displaying APS Status

You can display current status of existing APS group and its member links.
To display APS status:
In the config>protection>aps(group name)# prompt, enter show status.

The APS status is displayed.
ETX-5300A>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
sdh-sonet 4/1
sdh-sonet 3/1
Working
Protection
Admin
up
down
Status
up
sf
Active
yes
--
Example
Intra-Card APS
To configure intra-card APS:
APS 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-5300A# config protection aps aps_1

ETX-5300A>config>protection>aps(aps_1)$ bind working sdh-sonet 1/1
ETX-5300A>config>protection>aps(aps_1)$ bind protection sdh-sonet 1/2
ETX-5300A>config>protection>aps(aps_1)$ no shutdown
Inter-Card APS
ETX-5300A Ver. 1.0
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 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
7-43
ETX-5300A# config protection io-group io-group_1

ETX-5300A>config>protection>io-group(io-group_1)$ bind working 1
ETX-5300A>config>protection>io-group(io-group_1)$ bind protection 2
ETX-5300A>config>protection>io-group(io-group_1)$ no shutdown
ETX-5300A>config>protection>io-group(io-group_1) exit all
ETX-5300A# config protection aps aps_1
ETX-5300A>config>protection>aps(aps_1)$ bind working sdh-sonet 1/1
ETX-5300A>config>protection>aps(aps_1)$ bind protection sdh-sonet 2/1
ETX-5300A>config>protection>aps(aps_1)$ no shutdown
detected.

Message
Description
Bind failed: port is already bound to an

existing APS group
SDH/SONET port cannot be bound to more than one APS group
Bind failed: Services exist on port
SDH/SONET port with PWs defined on it cannot be bound to an

APS
Bind failed: Ports should reside on same

card
For intra-card APS, the working and protection port must reside
on the same card
Bind failed: APS ports should be of type

SONET-SDH
Only SDH/SONET ports can be defined as APS group members
Un-bind failed: APS group must be

shutdown before unbinding a port
A port can be removed from the APS group only after the group
is shut down
Bind failed: Protection port must reside

on protection card in group
Protection port must reside on a card defined as protection card

in the I/O protection group (inter-card APS)
Bind failed: Working port must be

configured on working card in group
Working port must reside on a card defined as working card in

the I/O protection group (inter-card APS)
Bind failed: Working and protection ports

must have the same port number
For inter-card APS, the working and protection port must have
the same number
Bind failed: Working and protection slots

must be the same
For intra-card APS, the working and protection port must 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 group
APS group remove failed: Ports are

bound to the group
APS group cannot be deleted if it has ports bound to it
APS group creation failed: Maximum

number of APS groups is already
configured
Maximum number of APS groups per chassis (8) has been

reached
Max length of APS group name is 32

characters
APS group name length has exceeded 32 alphanumeric

characters
7-44
ETX-5300A Ver. 1.0
Message
Description
Command failed: Protection line is in

signal fail or signal degrade
Traffic cannot be manually switched to a port with signal failure

or signal degrade condition
Command failed: Working line is in signal

fail or signal degraded
Traffic cannot be manually switched to a port with signal failure

or signal degrade condition
Modify failed: Group should be shutdown

in order to perform modification
Active APS group cannot be modified
APS create failed: Exactly 2 ports should

be bound to group
Number of APS member cannot exceed two ports
ETX-5300A Ver. 1.0
7-45
7-46
ETX-5300A Ver. 1.0
Chapter 8
Networking
This chapter explains how to configure networking entities in ETX-5300A. It
presents the following information:
Flows
Ethertype
Layer 2 Control Protocol (L2CP)
Peer
TDM Pseudowires
Cross-Connection
Bridge
Router
Quality of Service (QoS)
Ethernet OAM.
8.1
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-5300A 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 in Appendix B
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.
ETX-5300A Ver. 1.0
Flows
8-1
Chapter 8 Networking
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-5300A
supports up to 24K of Ethernet flows.
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.
Note
Data flow and traffic management are detailed in Appendix B of this manual.
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 (110 and 1120) 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
SAG
SAP
SVI
SVI
BP
BP
SVI
I/O Card
Ethernet Port
Bridge
BP
Main Card
Ethernet Port
I/O Ingress
Flows
SVI
I/O Ingress
Flows
BP
SAP
I/O Ethernet Card
Main Card
Ethernet Port
I/O Card
Ethernet Port
main Ethernet cards. I/O ingress flows are marked in red.
Figure 8-1. I/O Ingress Flows

Note
A flow between two ports that belong to the same 10-port group (110 or 11
20) on the same E5-GBE-20, cannot be defined. If an E-Line service is required
between two GbE ports, define the flows between ports belonging to the
different 10-port groups on the same E5-GBE-20 card or between ports on the
different E5-GBE-20 cards.
Other Flow Types

Up to 512 flows can originate from all SAPs on a single SAG (up to 1K per
Ethernet I/O card). ETX-5300A also supports flows originating from and directed
to main Ethernet card ports.
Flow Processing
Flow processing includes the following:
8-2
Flows
ETX-5300A Ver. 1.0
Ingress traffic is mapped in flows using the classification match criteria

defined in the classifier profile.
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 (07) according to CoS-mapping profile.
Table 8-1 details processing actions supported by different flow types.

Table 8-1. Processing Actions per Flow Type
Ingress
Port
Classifier
Profile
Drop
Action
L2CP
Profile
CoS Mapping
Profile
Color Mapping
Profile
Policing
Profile
VLAN
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:
ETX-5300A Ver. 1.0
Flow 1 with VLAN classification
Flow 2 with VLAN + specific MAC classification and drop action.
Flows
8-3
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.
Flow Counters
Statistic counters can be enabled on the following flows:
Note
Up to 512 of I/O ingress flows per each I/O card
Up to 2K minus two main card flows per chassis. These flows include:
Point-to-point (E-Line) flows
Multipoint (E-LAN) flows.
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-5300A 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:
8-4
Flows
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
ETX-5300A Ver. 1.0
Number of dropped green bytes
Number of dropped yellow/red bytes
Total packet drop rate (packet/sec)
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-5300A responds to the application layer loopbacks in accordance with the
RFC-2544 requirements. In this mode, ETX-5300A 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 Ethernet OAM) with live ingress and egress
flows.
ETX-5300A Ver. 1.0
Flows
8-5
When the flow testing is enabled, ETX-5300A loops back all LBM packets received
on the flow by swapping the MAC address and changing the LBM code to the LBR
code.
Tx Flow
SAP
Main or I/O Card
Port A
Rx Flow
I/O Card
Port B
Down MEP
Bound to Port B
A. Normal Operation
Tx Flow
LBR
Code
SAP
Main or I/O Card
Port A
Rx Flow
Down MEP
Bound to Port B
LBM Code
Loop
I/O Card
Port B
B. Operation after Enabling the RFC-2544 Loopback Responder

Figure 8-2. RFC-2544 Loopback Responder
ETX-5300A 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.
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 <profilename> 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>]
8-6
Flows
ETX-5300A Ver. 1.0
[dst-ip <dst-ip-low>] [to-dst-ip <dst-ip-high>] [ether-type <0xhhhh>] [untagged]

[non-ip] [all]
All possible combinations of classification criteria are listed under
Classification in Appendix B.
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-5300A# configure flows classifier-profile v100_150 match-any

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

ETX-5300A>config>flows>classifier-profile(v20_inner_30)$ match vlan 20
inner-vlan 30
ETX-5300A>config>flows>classifier-profile(v20_inner_30)$ exit all
To create classifier profile that matches all criteria:
ETX-5300A# configure flows classifier-profile all match-any

ETX-5300A>config>flows>classifier-profile(all)$ match all
ETX-5300A>config>flows>classifier-profile(all)$ exit all
To create classifier profile with criteria VLAN 10 and P-bit 5:
ETX-5300A# ETX-5300A# configure flows classifier-profile vlan_10+p-bit_5

match-any
ETX-5300A>config>flows>classifier-profile(vlan_10+p-bit_5)$ match vlan 10 pbit 5
ETX-5300A>config>flows>classifier-profile(vlan_10+p-bit_5)$ exit all
Error Messages
Table 8-5 lists the messages generated by ETX-5300A when a configuration error
is detected.

Message
Description
Illegal value
Not a valid value for the parameter
Classifier profile is in use and cannot be

changed/deleted
Classifier profile is being used by a flow. Remove the flow

association before attempting to delete or modify classifier
profile.
ETX-5300A Ver. 1.0
Flows
8-7
Message
Description
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
Classifier profile cannot use more than

one match criteria for classification
Only one match classification criteria is allowed per classifier

profile
Outer and inner VLAN classifier profile

does not support outer VLAN range
When configuring an outer and inner VLAN classifier profile, use

a single value for outer VLAN ID
Classifier profile: illegal range
Not a valid range of values for this classifier profile
Classifier profile: use of value range is

not allowed
This classifier profile supports a single value only
Classifier profile cannot be added, max

number of profiles has been reached
The maximum number of profiles (24K) has been reached and

no additional classifier profiles can be added
The classifier profile name is not unique
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.
Task
Command
Comments
Associating the flow with a

classifier profile
classifier <classifier-profile-name>
no classifier removes the flow

association with the classifier
profile
Specifying the ingress port
ingress-port ethernet <slot/port>
no ingress-port removes the flow

association with the ingress port
ingress-port lag <port-number>

ingress-port svi <port-number>
ingress-port mng-ethernet <slot/port>
ingress-port sap <slot/port/tributary>
no ingress-port
8-8
Flows
ETX-5300A Ver. 1.0
Task
Command
Comments
Specifying the egress port, and

the egress queue block and the
queue within the block
egress-port ethernet <slot/port> [queue-map-profile

<queue-map-profile-name> block <level_id/queue_id>]
The queue map profile maps CoS to

a queue. In ETX-5300A it is
permanently set to 1:1 mapping
(CoS 0 to queue 0 etc.)
egress-port lag <port-number> [queue-map-profile

<queue-map-profile-name> block <level_id/queue_id>]
egress-port svi <port-number><bridge | router | pw>
egress-port mng-ethernet <slot/port>
egress-port sap <slot/port/tributary> [queue-mapprofile <queue-map-profile-name> block
<level_id/queue_id>]
no egress-port
If you intend to use an I/O card

port as an egress port for the flow,
verify that the port already has a
queue group profile attached to it.
no egress-port removes the flow
association with the egress port
Assigning CoS mapping profile, or

using a fixed value for mapping
user priority to internal Class of
Service values
cos-mapping {[fixed <0..7>] [profile <cos-mappingprofile-name>]}
See Appendix B for details
Assigning color mapping profile,

or using a fixed value for
assigning a color (green or yellow)
to incoming packets
ingress-color {[ green | yellow] [profile <color-mappingprofile-name>]}
See Appendix B for details
Associating the flow with a policer

profile or policer aggregate
policer profile <policer-profile-name>
no policer removes the flow

association with the policer.
Associating a Layer-2 control

protocol profile with the flow
l2cp profile <l2cp-profile-name>
policer aggregate <policer-aggregate-name>
L2CP profiles can be attached to

certain types of flows, as detailed
in the L2CP Handling section of
Appendix B.
no l2cp profile removes the flow
association with the L2CP profile
Defining swapping actions for the

flow such as overwriting the VLAN
ID or inner VLAN ID or setting the
priority
mark
Defining window size for sampling

flow rate statistics
rate-sampling-window
Administratively enabling the flow
no shutdown
Discarding traffic transmitted via

the flow
drop
Activating the RFC-2544

responder mode
test [lbm-responder]
ETX-5300A Ver. 1.0
no test
Refer to the Table 8-4 for the

swapping action descriptions
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.
no test disables the RFC-2544

responder mode
Flows
8-9
Table 8-3 lists all VLAN pushing and popping actions supported by ETX-5300A. For
allowed combinations of VLAN editing for E-Line, E-LAN and router and PW SVIs,
see VLAN Editing in Appendix B.
Table 8-3. VLAN Pushing and Popping Actions
Task
Command
Comments
Pushing VLAN tag
vlan-tag push vlan <sp-vlan>
Removing outer VLAN tag, or

optionally inner VLAN tag
vlan-tag pop vlan [inner vlan]
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

marking profile
p-bit profile <inner-marking-profile-name>
Setting P-bit value by copying

from the incoming frame
p-bit copy
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-4. VLAN Swapping (Marking) Actions

Task
Command
Comments
Overwriting VLAN ID with a new

value
vlan <vlan-value>
no vlan disables the overwriting of

VLAN ID
Overwriting inner VLAN ID with a

new value
inner-vlan <inner-vlan-value>
no inner-vlan disables the

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

value
inner-p-bit <inner-p-bit-value >
no inner-p-bit disables the

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

value
inner-tag-ether-type <inner-tag-ether-type>
no inner-tag-ether-type disables the

overwriting of TPID
Overwriting P-bit according to

marking profile
marking-profile <marking-profile-name>
If a marking profile is used, it must

be compatible with the classification
8-10
Flows
ETX-5300A Ver. 1.0
Task
Command
Comments
Overwriting inner P-bit according

to marking profile
inner-marking-profile <inner-marking-profile-name>
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

returning to the flow context
exit
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-3 shows the flows to be configured for this application.
ETX-5300A Ver. 1.0
Flows
8-11
Figure 8-3. Multi-CoS Point-to-Point Service Flows
To configure multiple CoS point-to-point service:

1. 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.

2. Select classification keys for the I/O and main card ports.
3. Enable the I/O and main card ports.
4. Configure the policer profiles to distribute available bandwidth among flows
1114.
5. Configure the CoS mapping profile to map user priorities to internal CoS
values.
6. Configure the color mapping profile to map user color to internal color values.
7. 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.
8. Configure six flows:
8-12
Flows
Four flows from I/O card port to SAP with per-flow policing, CoS and color
mapping
One flow 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.
ETX-5300A Ver. 1.0
#***************************Defining_Policer_Profiles************************
config qos policer-profile "1" bandwidth cir 5000 cbs 10000 eir 0 ebs 0
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****************************************
config flows classifier-profile class100pbit6 match-any
match vlan 100 p-bit 6
exit all
exit all
exit all
exit all
config flows classifier-profile match-all match-any

match all
exit all

match vlan 300 inner-vlan 100
ETX-5300A Ver. 1.0
Flows
8-13
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 *******************************
configure qos marking-profile mark1 classification cos color-aware greenyellow dei mapping
mark 0 yellow to 7 dei green
mark 6 yellow to 0 dei yellow
exit all
#*********************************End****************************************
#****************************************************************************
#****************************************************************************
8-14
Flows
ETX-5300A Ver. 1.0
#********************Configuring_EVC.CoS_Flows_from_I/O_to_SAP***************
configure flows flow 11
classifier class100pbit6
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
no shutdown
exit all
policer profile 4
no shutdown
exit all
#********************Configuring_EVC_Flow_from_SAP_to_Main_Card**************
classifier match-all
0/1
vlan-tag push vlan 300 p-bit profile mark1
no shutdown
exit all
#********************Configuring_Flow_from_Main_to_I/O_Card******************
ETX-5300A Ver. 1.0
Flows
8-15

vlan-tag pop vlan
no shutdown
exit all
#*********************************End****************************************
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-4 shows the flows to be configured for this application.
Figure 8-4. 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.
3. Enable the I/O and main card ports.
values one-to-one.
5. Configure the color mapping profile to convert CoS values to green color.
6. Add the bridge-type SVIs and bind them to the bridge ports.
7. Define the bridge port VLAN membership (VLAN domain for bridge ports 14
for VLAN 10 with MAC table size of 256.
8. Configure the classifier profile (VLAN + P-bit).
9. Define eleven flows according to Figure 8-4.
8-16
Flows
ETX-5300A Ver. 1.0
#***********************Assigning_Queue_Group_Profiles***********************
exit all
#*********************************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
cos-map-profile cos1 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
ETX-5300A Ver. 1.0
Flows
8-17
map 4 to green
map 5 to green
map 6 to green
map 7 to green
exit all
#*********************************End****************************************
#*************************Defining_Bridge_SVIs*******************************
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
cos-mapping profile cos1
no shutdown
exit all
classifier class10
8-18
Flows
ETX-5300A Ver. 1.0
ingress-port svi 11
0/1
no shutdown
exit all
#*********************************End****************************************
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
ETX-5300A Ver. 1.0
Flows
8-19
#*********************************End****************************************
classifier class10
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****************************************
Statistics
ETX-5300A 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.
ETX-5300A>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
8-20
Flows
ETX-5300A Ver. 1.0
----------------------------------------------------------------------------Packets
Bytes
Total
: 26657156
3358801656
Green
: 26657156
3358801656
Yellow/Red : 0
0
Packets/Sec
Total
: 838377
Green
: 838377
Yellow/Red : 0
Bits/Sec
845084016
845084016
0
Tx
----------------------------------------------------------------------------Packets
Bytes
Total : 282067
35540442
Green : 282067
35540442
Yellow : 0
0
Packets/Sec
Total : 6209
Green : 6209
Yellow : 0
Bits/Sec
6258672
6258672
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.
is detected.

Message
Description
Ethertype tag is unknown, setting

failed
Not a valid value for the Ethertype tag
L2CP profile does not exist
The L2CP profile cannot be assigned to the flow because the profile
has not been defined
Illegal value
Not a valid value for parameter
ETX-5300A Ver. 1.0
Flows
8-21
Message
Description
Flow creation failure: max number of

flows reached
The maximum number of flows (24K) has been reached and no

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,

shutdown failed
A flow cannot be shut down if it has a MIP assigned to it
Active MEP is defined on the flow,

shutdown failed
A flow cannot be shut down if it has a MEP assigned to it
SVI is not configured
An SVI must be defined before a flow can be bound to it
Illegal flow-SAG combination in policer

aggregate profile
The policer profile cannot be used because not all of its flows are
bound to the same SAG
Max number of flows per policer

aggregate profile has been reached
The maximum number of flows per policer aggregate (16) has been
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
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

method mismatch
Invalid combination of port classification key and CoS mapping

method
Port classification key and color

method mismatch
Invalid combination of port classification key and color mapping

method
Max number of CoS or color profiles

for I/O card has been reached
The maximum number of CoS or color profiles per I/O card (36) has
been reached and no profiles can be added to flows originating
from the I/O card
Max number of color profiles for I/O

card has been reached
The maximum number of color profiles per I/O card (36) has been
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

SAG
Mismatch between ingress port of the flow and SAG number
Mismatch between flow SVI (B) and

egress port
Flows originating from the same bridge-type SVI must terminate in

the same port
8-22
Flows
ETX-5300A Ver. 1.0
Message
Description
Mismatch between flow SVI (B) and

egress slot
Flows originating from the same bridge-type SVI must terminate in

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

bridge service
Invalid editing action for inner and outer VLANs on a flow in

multipoint service

P2P service
Invalid editing action for inner and outer VLANs on a flow in

point-to-point service

router service
Invalid editing action for inner and outer VLANs on a flow in Layer-3
service
Classification + editing error for

bridge service
Invalid classification and VLAN editing action on a flow in multipoint

service
Bridge port is not a member of

identified VLAN
The bridge port must be a member of an outer VLAN of the frame

remaining at the entrance to the bridge port
VLAN editing error for a P2P flow

starting from PW SVI
Invalid VLAN editing action for a point-to-point flow starting from

PW-type SVI
Editing of ingress I/O flows is not

allowed
Cannot perform VLAN editing on ingress I/O flows
Max number of L2CP profiles bound

to a port has been reached
The maximum number of L2CP profiles per port (4, including

default) has been reached and no profiles can be added
Max number of L2CP profiles bound

to a flow has been reached
The maximum number of L2CP profiles per flow (1) has been
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

bound to it
If a LAG serves as a flow ingress port, it must have two ports

assigned to it
Egress LAG port has less than 2 ports

bound to it
If a LAG serves as a flow egress port, it must have two ports

assigned to it
Number of ingress SAPs has been

exceeded
Cannot define a SAP as an ingress port for a flow if the SAP number
is higher than 512
Number of egress SAPs has been

exceeded
Cannot define a SAP as an egress port for a flow if the SAP number
is higher than 512
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
ingress port
A discrepancy between the classification key of port and the

classification method of the flow
Classification type cannot include Pbit
The P-bit classification cannot be used for flows originating from

bridge-type SVIs
ETX-5300A Ver. 1.0
Flows
8-23
Message
Description
Max number of port-based flows per

SAG has been exceeded
The maximum number (128) of port-based flows per SAG has been
exceeded
Max number of VLAN-based flows per

SAG has been exceeded
The maximum number (128) of VLAN-based flows per SAG has been
exceeded
Classification type must be VLAN or

untagged
Only VLAN or untagged classification is allowed
Classification type must be VLAN
Only VLAN classification is allowed
Classification type must be VLAN or

Inner VLAN
Only VLAN or Inner VLAN classification is allowed
Classification type must be VLAN,

Inner VLAN or Match All
Only VLAN, Inner VLAN or Match All classification is allowed
Classification type must be Match All

for ingress port SVI (R)
Only Match All classification is allowed for flows originating from

router-type SVI

for ingress port SVI (PW)
Only Match All classification is allowed for flows originating from

PW-type SVI

for P2P SAP flow
Only Match All classification is allowed for point-to-point flows

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

defined for the VLAN
Another classification type has already been 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

the P-bit
Another type of classification entry already exists for the port. The
classification type must be unique for the port.
Only single VLAN is allowed for this

classification type
VLAN ranges are not allowed for the selected classification type
Only single VLAN is allowed for SVI

router/bridge egress port
VLAN ranges are not allowed for flows terminating in router- or

bridge-type SVIs
Only single VLAN is allowed for SVI

router/bridge ingress port
VLAN ranges are not allowed for flows originating from router- or
bridge-type SVIs
Only single MAC is allowed for this

classification type
MAC ranges are not allowed for the selected classification type
Only single IP is allowed for this

classification type
IP ranges are not allowed for the selected classification type
Only single P-bit is allowed for this

classification type
P-bit ranges are not allowed for the selected classification type
Only one P-bit range is allowed for

this classification type
A single P-bit is not allowed for the selected classification type
8-24
Flows
ETX-5300A Ver. 1.0
8.2
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.
See Ethertype in Appendix B for a detailed description of Ethertype.
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-5300A>config>port>tag-ethertype 0x88a8
is detected.
ETX-5300A Ver. 1.0
Ethertype
8-25

Message
Description
Modify failed: Ethertype tag value is in

use
The Ethertype tag value cannot be changed because it is

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

value
The default Ethertype tag value (0x8100) cannot be deleted
Delete failed: Ethertype tag value is in

use
The Ethertype tag value cannot be deleted because it is

currently being used by a port of a flow
Setting failed: Ethertype tag value is

unknown
The Ethertype tag value for a port or a flow is different from the
one configured at system level
Ethertype tag cannot be modified for a

port attached to LAG
The Ethertype tag value is in use by the LAG
8.3
ETX-5300A 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. The L2CP profiles are attached to ports and flows.
Standards
IEEE 802.3
Benefits
ETX-5300A offers high flexibility in handling customers L2CP packets. According
to application requirements, these packets can be tunneled, discarded or trapped
to the host.
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.
See L2CP in Appendix B for a detailed description of how ETX-5300A handles
Layer 2 Control Protocol packets.
8-26
ETX-5300A Ver. 1.0
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:

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

1. Navigate to configure port l2cp <l2cp-profile-name> to select the L2CP profile
to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
Task
Command
Specifying the default action for

undefined control protocols
default {discard | tunnel}
ETX-5300A Ver. 1.0
Comments
8-27
Task
Command
Comments
Specifying the L2CP action for MAC

addresses (discard, tunnel, or peer)
mac <mac-addr-last-byte-value-list> {discard | tunnel |

peer}
discard L2CP frames are

discarded
tunnel L2CP frames are
forwarded across the network
as ordinary data
peer ETX-5300A peers with
the user equipment to run the
protocol. L2CP frames are
forwarded to the ETX-5300A
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
Example
To add L2CP profile named layer2ctrl1 with peer action:
ETX-5300A# configure port

ETX-5300A>config>port# l2cp profile layer2ctrl1
ETX-5300A>config>port>l2cp profile(layer2ctrl1)$ mac 01-80-C2-00-00-02 peer
To delete L2CP profile named layer2ctrl1:
ETX-5300A# configure port

ETX-5300A>config>port# no l2cp-profile layer2ctrl1
ETX-5300A>config>port#
is detected.

Message
Description
L2CP profile creation failure: Max number

of L2CP profiles has been reached
The L2CP profile cannot be added because the maximum number

of L2CP profiles has been reached
L2CP profile deletion/modification

failure: L2CP profile is in use
The L2CP profile cannot be deleted or modified because it is

currently attached to a port or a flow
Illegal L2CP processing action for this

MAC address type
The L2CP processing action selected for the current MAC

address type is not valid
8-28
ETX-5300A Ver. 1.0
Message
Description
Cannot add MAC address: Max number of

MAC addresses has been reached
Cannot specify an L2CP processing action for a MAC address

because the maximum number of addresses has been reached
PAUSE frames are not supported
PAUSE frames must be discarded
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.
L2CP profile does not exist
Cannot bind an L2CP profile that has not yet been created
Peer action is not allowed for portbound L2CP profile
An L2CP profile bound to a port cannot perform a peer action
8.4
Peer
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-5300A 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:
ETX-5300A Ver. 1.0
At the config>peer (number) # prompt, enter all necessary commands

according to the tasks listed below:
Peer
8-29
Task
Command
Defining the IP address of a

remote peer in UDP/IP networks
ip <valid IP address>
Assigning a name to a remote

peer
name <alphanumeric string >
Specifying number of a router

instance
router <1>
Defining MAC address of a

remote peer in MEF-8 networks
mac<valid MAC address>
This parameter is permanently

set to 1
To remove a remote peer:
Note
Comments
At the config>peer (peer number) # prompt, type no peer (peer number).
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-5300A>config# info
peer 1 ip 6.6.6.7
peer 2 ip 172.17.153.191 name
peer 3 ip 172.17.154.192 name
"peer_2"
"peer_3"
Example
To configure remote peer 1 for UDP/IP PSN:
IP address: 9.9.9.9
Name: peer1.
ETX-5300A>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-5300A>configure peer 1 mac 00-20-d6-54-bf-05 name peer2
To delete remote peer 1:
ETX-5300A>config# no peer 1
Note
8-30
Peer
See Pseudowire Service section for a detailed example of a pseudowire

configuration.
ETX-5300A Ver. 1.0
is detected.

Message
Description
Peer is in use: Peer cannot be updated if

used
Cannot modify a peer that is being used by a pseudowire
Peer is in use: Peer cannot be removed if

in use
Cannot delete a peer that is being used by a pseudowire
Peer index is invalid
Peer index is out of allowed range
Peer set failed: Maximum number of

targeted peers already configured
Cannot create a peer because the maximum number of

pseudowire peers (1334) has been reached
Peer set failed: Peer IP must not be a

multicast IP
IP address of pseudowire peer on UDP/IP network cannot be

multicast
Peer set failed: Maximum number of

peers already configured
Cannot create a peer because the maximum number of

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.5
TDM Pseudowires
TDM pseudowires (PWs) are an emulation of Layer-2 point-to-point connectionoriented services over packet-switching networks (PSN).
Standards
ETX-5300A Ver. 1.0
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
TDM Pseudowires
8-31
Pseudowire (PW) Management Information Base (MIB), draft-ietf-pwe3-pwmib-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-5300A system.
Benefits
Pseudowire circuit emulation technology enables packet-based infrastructure to
provide TDM services with the service quality of an SDH/SONET network.
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 cards. Each TDM card has
four channelized STM-1/OC-3 ports with DS1 capacity at 63 E1 or 84 T1 channels
per interface. The traffic to the internal DS1 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-5300A pseudowire system, see also Peer
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) and the
PSN type (UDP/IP or ETH). 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
8-32
TDM Pseudowires
ETX-5300A Ver. 1.0
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.
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-5300A supports the following PSN types:
ETX-5300A Ver. 1.0
UDP over IP
MEF-8 (CESoETH).
TDM Pseudowires
8-33
UDP over IP
For UDP/IP-type PSN, the TDM-PW packet structure is as follows:
6
20
DA
SA
Type
8100
VLAN
Tag
Type
800
IP Header
UDP
Header
CW
TDM Payload
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:
Note
UDP Source Port source PW label (18191) + 49152
UDP Destination Port destination PW label (18191) + 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)
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:
DA
SA
Type
8100
VLAN
Tag
Type
88D8
ECID
CW
TDM Payload
Where:
8-34
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.
TDM Pseudowires
ETX-5300A Ver. 1.0
Control Word
The control word structure for different encapsulation methods is illustrated
below.
CESoPSN:
0
10
FRG
15
16
LEN (6)
31
Sequence Number (16)
SAToP:
0
RSV
10
FRG
15
16
LEN (6)
31
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-9. L & M Code Point Interpretations

L
Code Point Interpretation
00
Normal situation, no failure
01
Reserved
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.
11
Reserved for CESoPSN signaling packets.
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.
01
Reserved
10
Reserved
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.
ETX-5300A Ver. 1.0
TDM Pseudowires
8-35
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 space
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-5300A.
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 NxDS0 channels belonging to same PW):
N number of timeslots in the PW
L packet payload size in bytes
L = mxN
8-36
TDM Pseudowires
ETX-5300A Ver. 1.0
The resulting payload format is illustrated below.

0
Timeslot 1
Frame 1
Timeslot 2
Timeslot N
Timeslot 1
Frame 2
Timeslot 2
Timeslot N
Timeslot 1
Frame 3
Timeslot 2
Timeslot N
Timeslot 1
Frame m
Timeslot 2
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
ETX-5300A Ver. 1.0
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.
TDM Pseudowires
8-37
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 = 18, 16, 24, 32 (payload size is an multiple integer of 32 bytes)
T1 N 24
Where N = 18, 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. 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.
8-38
TDM Pseudowires
ETX-5300A Ver. 1.0
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:
ETX-5300A Ver. 1.0
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.
TDM Pseudowires
8-39
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.
8-40
TDM Pseudowires
ETX-5300A Ver. 1.0
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-5300A 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-5300A 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-5 illustrates fault propagation in structure-agnostic mode when LOS or

AIS is detected on the TDM link. In this case, remote ETX-5300A ignores or
propagates the AIS condition, according to the user configuration. If the AIS is
generated, the ETX-5300A sets the CW bits as follows: L-bit 1, M-bit 00.
When ETX-5300A detects the CW bit settings, it generates the AIS towards the
local TDM device.
L-bit = 1
M-bit = 00
LOS, AIS
TDM
Device
AIS
ETX-5300
AIS
PSN
ETX-5300
TDM
Device
Figure 8-5. Structure-Agnostic Mode, TDM Failure

ETX-5300A Ver. 1.0
TDM Pseudowires
8-41
Figure 8-6 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-5300A sets the CW Rbit to 1 in the packets transmitted towards the PSN.
R-bit = 1
Packet
Loss
PSN
TDM
Device
ETX-5300
AIS
TDM
Device
ETX-5300
Figure 8-6. Structure-Agnostic Mode, PSN Failure

Figure 8-7 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
Device
ETX-5300
TDM
Device
ETX-5300
Figure 8-7. 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-8 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-5300A ignores or propagates the AIS
condition, according to the user configuration. If the AIS is generated, ETX-5300A
sets the CW bits as follows: L-bit 1, M-bit 00. If the LOS or OOF conditions
are detected, ETX-5300A sends the RDI towards the local TDM device.
ETX-5300A 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
Device
ETX-5300
ETX-5300
TDM
Device
Figure 8-8. Structure-Aware Trail-Terminated Mode, TDM Failure

Figure 8-9 illustrates fault propagation in structure-aware trail-terminated mode,
when persistent packet loss or jitter buffer underflow conditions are detected.
ETX-5300A detects the fault condition and generates the OOS code for all DS0
8-42
TDM Pseudowires
ETX-5300A Ver. 1.0
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
OOS Code
PSN
TDM
Device
TDM
Device
ETX-5300A
ETX-5300
Figure 8-9. Structure-Aware Trail-Terminated Mode, PSN Failure

Figure 8-10 illustrates fault propagation in structure-aware trail-terminated
mode, when RDI signal is received on the TDM interface. ETX-5300A 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
Device
ETX-5300
TDM
Device
ETX-5300
Figure 8-10. 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-11 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-5300A ignores or propagates the AIS condition, according to the user
configuration. If the AIS is generated, ETX-5300A sets the CW bits as follows: Lbit 1, M-bit 00. If the LOS or OOF conditions are detected, ETX-5300A sends
the RDI towards the local TDM device.
ETX-5300A 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
Device
ETX-5300
ETX-5300
TDM
Device
Figure 8-11. 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-5300A
sets the CW R-bit to 1 in all packets transmitted towards the PSN. When
ETX-5300A Ver. 1.0
TDM Pseudowires
8-43
ETX-5300A detects the CW bit settings, it generates the RDI towards the local
TDM device.
R-bit = 1
Packet
Loss
AIS
PSN
RDI
TDM
Device
ETX-5300
TDM
Device
ETX-5300
Figure 8-12. Structure-Aware Trail-Extended Mode, PSN Failure

when RDI signal is received on the TDM interface. ETX-5300A sets the CW bits as
follows: L-bit 0, M-bit 10, in all packets transmitted towards the PSN. When
ETX-5300A detects the CW bit settings, it generates the RDI towards the local
TDM device.
L-bit = 0
M-bit = 10
PSN
RDI
TDM
Device
ETX-5300
RDI
ETX-5300
TDM
Device
Figure 8-13. 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 farend source of each pseudowire. The clock recovery mechanisms can provide
recovered clock signals to serve as timing references for the ETX-5300A 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-5300A 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
8-44
TDM Pseudowires
ETX-5300A Ver. 1.0
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, you can
specify how to handle such transient conditions (a capability referred to as
delay sensitivity):
By disabling delay sensitivity, performance is optimized for accurate clock

recovery. This selection is optimal for data transmission applications.
By enabling delay sensitivity, performance is optimized for constant delay.

This selection is optimal for voice transmission applications.
Configuring Pseudowires
A new pseudowire bundle is added by defining its number (11344), 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(14)# prompt.
2. At the config>pwe# prompt, enter the syntax illustrated in the table below.
The config>pwe>pw(<pw-number>)# prompt appears.
Note
ETX-5300A Ver. 1.0
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.
TDM Pseudowires
8-45
Task
Command
Comments
Assigning the
pseudowire number,
selecting the
encapsulation protocol
for the selected
pseudowire and
specifying the PSN
type (selecting the
type of PSN header)
pw <pw-number> [type {cespsn-data | e1satop |

t1satop ]
[psn {udp-over-ip |
ethernet}]
PW number: 1..1344
PW type (must be configured for the first time):
e1satop: SAToP, for carrying unframed E1 data

streams
t1satop: SAToP, for carrying unframed T1 data

streams
ces-psn-data: CESoPSN protocol, for carrying

framed data streams
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.
3. At the config>pwe>pw(<pw-number>)# prompt, enter the parameters

specified in the table below.
Task
Command
Comments
Assigning a name to the

pseudowire
name <up to 32
characters>
Using no before name deletes the pseudowire name
Specifying the PW label used

in the inbound and
outbound directions
label [in <number>]

[out < number>]
Out PW label:
For udp-over-ip: Specifies the UDP destination

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 18191.

Defining the jitter buffer
size
jitter-buffer <value in
sec>
Use the shortest feasible buffer, to minimize

connection latency.
The allowed range is 100016000 sec, in 1-sec
steps.
8-46
TDM Pseudowires
ETX-5300A Ver. 1.0
Task
Command
Comments
Enabling/disabling the OAM

connectivity protocol for this
PW
oam
The selection must be compatible with the

equipment at the far end of the connection
For pseudowires defined on redundant internal DS1
ports, make sure to select the same OAM mode.
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

terminating this PW
peer <peer number>
Configuring TDM payload

size
tdm-payload <value>
Range: from 1 to 1334.

no peer removes the remote peer
A larger value increases the bandwidth utilization
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:
Specifying the value for the

TOS byte used on outbound
traffic
tos <tos number>
E1 SAToP n32, n = 18, 16, 24, 32 (32, 64,

96, 128, 160, 192, 256, 512, 768, 1024)
T1 SAToP n24, n = 18, 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)
Range: from 1 to 255.

In accordance with RFC 2474, it is recommended to
use only values which are multiples of 4.
This parameter is relevant only when psn is
udp-over-ip.
Selecting the response to

out-of-service conditions
detected at the local TDM
port
psn-oos {1-bit | stoptx}
OOS conditions are reported by setting the 1 bit

within the PW packet overhead
Assigning egress port for L2

forwarding
egress-port svi
<svi_number>
This parameter is relevant only when psn is ethernet
Enabling the pseudowire
no shutdown
shutdown disables the pseudowire
Displaying PW Statistics
ETX-5300A 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
ETX-5300A Ver. 1.0
TDM Pseudowires
8-47
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.
Task
Command
Comments
Displaying
statistics
show statistics {total | all | current}
current Displays the current statistics
all-intervals Displays statistics for all

valid intervals (without current statistics)
total-counters Displays total statistics

of last 96 intervals
ETX-5300A>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
Table 8-10. TDM PW Statistic Counters

Parameter
Description
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
Packets
Number of packets detected via CW sequence number to be out of sequence,

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
8-48
TDM Pseudowires
ETX-5300A Ver. 1.0
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 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 connectivity status
values, refer to the table below.
ETX-5300A>config>pwe>pw(1)# show status
PW
: 1
Name
: pw-1
PW Type
PSN Type
Operational Status
Out Label
In Label
:
:
:
:
:
CESoPSN
Ethernet
Up
33
22
Table 8-11 explains the connectivity status values of the selected pseudowire.
Table 8-11. Pseudowire Connectivity Status Values
ETX-5300A Ver. 1.0
Parameter
Displayed
Description
Disable
The pseudowire is disabled
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
TDM Pseudowires
8-49
Parameter
Displayed
Description
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-5300A>config>pwe# show summary

PW
PSN Type
Out Label
Peer
:
:
:
:
1
UDP Over IP
1
1
Jitter Buffer
: 1000
PW Type
Status
In Label
: SAToP
: Not present
: 1
Payload Size
: 24
To display PW detailed information:
At the config>pwe# prompt, enter the info detail command.

For example:
ETX-5300A>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
8-50
To configure a pseudowire:
PW number 1
PW type T1 SAToP
PSN type Ethernet
Out (destination) label 1
In (source) label 1
Jitter buffer 300
OAM disabled
Peer 1
TDM Pseudowires
ETX-5300A Ver. 1.0
Egress port SVI 1
TDM payload size 96
ETX-5300A>config>pwe# pw 1
ETX-5300A>config>pwe>pw(1)
Note
type t1satop psn ethernet

label out 1 in 1
jitter-buffer 300
no oam
peer 1
egress-port svi 1
tdm-payload 10
See Pseudowire Service section for detailed example of a pseudowire

configuration.
Table 8-12 lists the messages generated by ETX-5300A when a configuration
error is detected.
Message
Description
PW peer number has not been

configured
Cannot configure a pseudowire because PW peer number is

missing
PW inbound label hasn't been configured
Cannot configure a pseudowire because inbound label is missing
PW outbound label hasn't been

configured
Cannot configure a pseudowire because outbound label is

missing
PW egress-port hasn't been configured
Cannot configure a pseudowire because egress port is missing
PW TDM mandatory fields: tdm payload

size/rate/jitter buffer, must be
configured
Cannot configure a pseudowire because TDM payload size, or

rate, or jitter buffer values are missing
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
PW removal failed: PW is connected to a

cross-connection
Cannot delete a pseudowire because it has timeslots assigned

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

minimum value
Cannot configure a pseudowire because the TDM payload size is

below the minimum value
PW set failed: Payload size exceeds the

maximum value
Cannot configure a pseudowire because the TDM payload size is

above the minimum value
PW set failed: PW is connected to a

cross-connection
Cannot configure a pseudowire because it has timeslots

assigned to it
PW set failed: Maximum number of PWs

already configured
Cannot configure a pseudowire because the maximum number

of allowed PWs per chassis has been reached
PW set failed: PW number exceeds

maximum
Cannot configure a pseudowire because its number is above the

maximum allowed value (1344)
ETX-5300A Ver. 1.0
TDM Pseudowires
8-51
Message
Description
PW set failed: PW number fails to meet

minimum
Cannot configure a pseudowire because its number is above the

minimum allowed value (1)
PW PSN type must be of type IP in order

to set TOS field
Only PWs with UDP/IP network encapsulation support ToS

configuration
Egress port can only be set if PSN type is

Ethernet or MPLS
Only PWs with Ethernet or MPLS network encapsulation require

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

PSN type is UDPoIP
Only PWs with UDP/IP network encapsulation support UDP

multiplexing method configuration
PW set failed: combination of peer and

outbound label should be unique
Cannot configure a pseudowire because its peer/outbound label

combination is not unique
PW set failed: TDM payload size or rate

invalid
Cannot configure a pseudowire because selected TDM payload

type or rate value is not valid
PW set failed: A peer must be configured

first
Cannot configure a pseudowire because no PW peer has been

configured yet
PW set failed: PW label value must be

unique
Cannot configure a pseudowire because PW label value is

already in use
PW set failed: Changing this parameter is

not allowed
Cannot modify pseudowire parameters when a PW is not shut

down
8.6
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-5300A system.
Benefits
Cross-connects allow flexible mapping of individual DS0 channels or full DS1
streams into pseudowires.
8-52
Cross-Connection
ETX-5300A Ver. 1.0
The ETX-5300A cross-connect matrix supports two types of cross-connect,
selectable at the level of the individual E1 and T1 port:
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.
Task
Command
Comments
Establishing crossconnection
between this
pseudowire and
timeslots on the
ds1 port
pw-tdm pw <pw number> ds1 <slot>/<port>

[time-slots <ts list>]
Timeslots in a list can be separated

by a comma or given as a range, for
example: 1..3, 5.
Using no before the command
removes the cross-connection
Examples
Cross-Connection
ETX-5300A Ver. 1.0
To assign timeslots 16, 8, and 1015:
PW number 1
E1 interface 1 in TDM port 1 of E5-cTDM-4 card installed in slot 1
Cross-Connection
8-53
ETX-5300A>config>cross-connect# pw-tdm pw 1 e1 1/1/1 time-slots

[1..6, 8..8, 10..15]
To remove PW1:
ETX-5300A>config>cross-connect# no pw-tdm pw 1
To display information on all assigned timeslots:

ETX-5300A>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
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****************************************
#************************Configuring_Clock_Domain****************************
configure system clock domain 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 IPmux216
exit all
#*********************************End****************************************
#*********************Configuring_Classifier_Profile*************************
config flows classifier-profile classAll match-any
match all
exit all
8-54
Cross-Connection
ETX-5300A Ver. 1.0
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
exit all
#*********************************End****************************************
#*****************************Configuring_Pseudowire*************************
configure pwe
ETX-5300A Ver. 1.0
Cross-Connection
8-55
pw 1 type t1satop psn ethernet

label in 1 out 1
peer 1
egress-port svi 1
tdm-payload size 96
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*********************
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****************************************
error is detected.
Message
Description
PW XC set failed: Only one PW can be

configured on an Unframed port
Cannot configure a timeslot cross-connection because unframed

ports support only a single PW
PW XC set failed: Timeslots do not match

with PW payload size and rate
Cannot configure a timeslot cross-connection because there is a

mismatch between the number of assigned timeslots and the
selected PW TDM payload size or rate
8-56
Cross-Connection
ETX-5300A Ver. 1.0
Message
Description
PW XC set failed: The timeslot belongs to

another bundle
Cannot configure a timeslot cross-connection because a timeslot

is already assigned to another PW
Pw-TDM cross-connection failed:

Timeslot(s) out of range

mismatch between the number of timeslots and the PW type
Pw-TDM cross-connection failed: PW

type doesn't match card configured in
slot

mismatch between a PW type and a card configured for the slot
PW XC set failed: card in specified slot

must be of type TDM
Cannot configure a timeslot cross-connection because an

Ethernet card has been configured in the chassis slot
PW XC create failed: more than one

multi-service card cannot use same the
SVI
Cannot configure a timeslot cross-connection because only one

TDM card can use a single SVI
PW XC set failed: Mismatch between port

line-type (unframed) and pw type (cespsn-data)
Cannot configure a timeslot cross-connection because a PW

type (CESoPSN) requires a framed line type

line-type (framed) and pw type (SAToP)
Cannot configure a timeslot cross-connection because a PW

type (SAToP) requires an unframed line type

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

configured per port
Cannot configure a timeslot cross-connection because only one

PW can be configured for this port type
8.7
Bridge
The ETX-5300A bridge is a VLAN-aware Layer-2 forwarding entity.
Standards
IEEE 802.1D, 802.1Q
Benefits
Bridge is used to deliver EPLAN and EVPLAN (any-to-any) services.
Factory Defaults
By default, no bridge instances exist in the ETX-5300A system.
A bridge is a forwarding entity used by ETX-5300A for delivering E-LAN services in
multipoint-to-multipoint topology and G.8032 ring protection. With up to 32
bridge instances, ETX-5300A provides up to 128 bridge ports.
ETX-5300A Ver. 1.0
Bridge
8-57
The bridge operates in VLAN-aware mode (IVL) with ingress filtering. It accepts
tagged frames only. To be admitted to the bridge, a frames 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-5300A 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
3600 seconds.
Note
Currently, ETX-5300A supports up to 32K MAC table entries.
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:
Bridge
Port
Bridge
Figure 8-14. 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
Port
Push C
Bridge
VID C
Figure 8-15. Mapping Flows with the Same VID to One Bridge Port
Likewise, flows from the same bridge port cannot be mapped to different
physical ports:
8-58
Bridge
ETX-5300A Ver. 1.0
Port
Bridge
Port
Figure 8-16. Mapping Flows with the Same Bridge Port to Different Physical Ports
VLAN Editing at Bridge Port Ingress and Egress

The ETX-5300A 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 VLAN Editing in Appendix B.
Certain restrictions apply to the type of port of flow origin (directly- or indirectlyattached) and flow classification method.
Directly-attached ports:
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-14 specifies valid combinations of flow classification method, ingress

VLAN editing action, and flow VID for flows originating at directly-attached
ports.
Table 8-14. Flows Originating at Directly-Attached Port

Classification Method
Ingress Editing Action
Bridge Broadcast Domain
Untagged
Push X
VLAN X
None
VLAN X
Push Y
VLAN Y
Swap (mark) Y
VLAN Y
None
VLAN X
Pop
VLAN Y
Push Z
VLAN Z
Swap (mark) Z
VLAN Z
VLAN X
Outer VLAN X +
Inner VLAN Y
Indirectly-attached ports:
ETX-5300A Ver. 1.0
Up to 255 different bridge ports with ingress pop action can be defined
Bridge
8-59
Table 8-15 specifies valid combinations of flow classification method, ingress

VLAN editing action, and flow VID for flows originating at indirectly-attached
ports.
Table 8-15. Flows Originating at Indirectly-Attached Ports (via SAP)

Swap (mark) X
VLAN X
Push X
VLAN X
Outer VLAN X
None
VLAN X
Outer VLAN X +
Inner VLAN Y
Pop
VLAN Y
Match All
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:
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.
Configuring Bridge
Bridge configuration includes the following steps:
1. Adding and configuring a bridge instance (132)
2. Binding bridge ports to SVIs
3. Adding VLANs and defining bridge ports as egress tagged VLAN members.
To configure a bridge:
1. At the configure prompt, enter bridge followed by bridge number (132).
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.
Task
Command
Defining aging time for MAC

table entries (seconds)
aging-time <300600>
Clearing addresses in MAC table
clear-mac-table
8-60
Bridge
Comments
ETX-5300A Ver. 1.0
Task
Command
Comments
Configuring bridge ports, see

below
port <1128>
no port (port_number), deletes

a bridge port
Configuring VLAN membership,

see below
vlan <14094>
no vlan (VLAN_number),
deletes a VLAN
Displaying MAC address table
show mac-address-table all [vlan-id]
Adding VLAN ID after the show

mac-address-table all displays
MAC table only for selected
VLAN
Displaying VLAN information
show vlans
no port <1128>
The following marking actions can be performed at the port level, at the
config>bridge(bridge_number)>port(port_number)# prompt.
Task
Command
Comments
Binding bridge port to a bridgetype SVI
bind svi <svi_number>
no bind svi (svi_number),

unbinds bridge port from SVI
Assigning a name to bridge port
name <value>
no bind svi <svi_number>
no name
Enabling the bridge port
no shutdown
Displaying bridge port status
show status
no name deletes bridge port

name
shutdown disables the bridge
port
The following marking actions can be performed at the vlan membership level, at
the config>bridge(bridge_number)>vlan(vlan_number)# prompt.
Task
Command
Defining maximum MAC table

size supported by the VLAN
maximum-mac-addresses <64 | 256 |

512 | 1024 | 4096>
Assigning a name to VLAN
name <value>
Comments
no name deletes VLAN name
no name
Defining bridge ports as egress
tagged VLAN members
tagged-egress<bridge_port_number>
no tagged-egress
<bridge_port_number>
Bridge ports in a list can be

separated by a comma or given
as a range, for example: 1..3,
5.
no before the command
deletes VLAN membership for
the bridge port.
Displaying MAC Address Table

You can display an ETX-5300A MAC table, which provides information on static
addresses, bridge ports and VLANs associated with them.
ETX-5300A Ver. 1.0
Bridge
8-61
To display MAC address table:
At the config>bridge(bridge_number)# prompt, enter show mac-address-table

all.
The MAC address table is displayed.
Note
ETX-5300A displays only first 100 entries. To view the whole MAC table,
download it to your PC, using SFTP. See File Operations in Chapter 10.
ETX-5300A>config>bridge(1)# show mac-address-table all
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

all vlan-id.
The MAC address table for the selected VLAN is displayed.
ETX-5300A>config>bridge(1)# show mac-address-table all 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.
To display VLAN information:
At the config>bridge(bridge_number)# prompt, enter show vlans.

The VLAN information is displayed.
ETX-5300A>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-5300A bridge ports, including their roles in
Ethernet protection rings, ERP status and source of local signal failure.
8-62
Bridge
ETX-5300A Ver. 1.0
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-5300A>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.
error is detected.
Message
Description
Modify failed: shut down the port before

modification
Active bridge ports cannot be modified
Modify failed: bridge port is bound
Bound bridge ports cannot be modified
Modify failed: bridge port is bound to

ERP
ERP-bound bridge ports cannot be modified
Modify failed: VLAN does not exist
VLAN cannot be modified because it does not exist
Modify failed: no bridge ports are

configured to be this VLAN members
VLAN with no bridge ports attached to it cannot be modified
Modify failed: max number of bridge

instances has been reached
Maximum number of bridge instances per chassis (32) has been

reached
Modify failed: max number of VLANs has

been reached
Maximum number of broadcast domains (4K) has been reached
Modify failed: VLAN is used for RAPS

messaging in ERP
VLAN cannot be modified because it is used as a messaging

VLAN in ERP
Modify failed: VLAN is used as data VLAN

in ERP
VLAN cannot be modified because it is used as a data VLAN in

ERP
Modify failed: VLAN index is out of range
VLAN numbering index is out of allowed range
Modify failed: only bound bridge ports

can be activated
Bridge ports must be bound to SVIs prior to their activation
ETX-5300A Ver. 1.0
Bridge
8-63
Message
Description
Modify failed: bridge port must be shut

down
Active bridge ports cannot be modified
Modify failed: bridge has active ports or

VLANs
Bridge entity has active ports or VLANs
Modify failed: bridge port index is out of

range
Bridge port index is out of allowed range
8.8
Router
The ETX-5300A 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.
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-5300A system.
The ETX-5300A static router is an internal interworking device that forwards
traffic between its interfaces. ETX-5300A 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 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 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.
8-64
Router
ETX-5300A Ver. 1.0
Connection to Physical and Bridge Ports

Figure 8-17 illustrates the connection of router interfaces (RIFs) to directlyattached (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.
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-17 illustrates a RIF-to-BP connection.
ETX-5300A
SVI
LB IP
RIF Router
User
NET
RIF
SVI
SVI
SVI
BP
SVI
User
BP
SVI
BP
OOB
BP
NET
Bridge
BP
User
SVI
SVI
Figure 8-17. Router Connection to Physical and Bridge Ports
Management
ETX-5300A 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.
Loopback Router Interfaces

Any router interface can be declared a loopback type. ETX-5300A supports up to
six virtual loopback addresses, which can connect to:
ETX-5300A Ver. 1.0
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).
Router
8-65
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-5300A 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 Router
Router configuration includes the following steps:
1. Adding a router instance
2. Add and configure router interfaces (1128).
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.
Task
Command
Comments
Assigning a name to router
name <value>
no name deletes router name
no name
Clearing dynamic entries from
ARP table
clear-arp-table
Configuring router interfaces,

see below
interface <1128>
Configuring the static route and

the next gateway (next hop)
using the next hops IP address
static-route
<IP-address/IP-mask-of-static-route>
address <IP-address-of-next-hop>
[metric <metric>]
Displaying the address

resolution protocol (ARP) table,
which lists the original MAC
addresses and the associated
(resolved) IP addresses
show arp-table
Displaying the router interface

table
show interface-table
8-66
Router
no interface <1128>
no interface (port_number),
deletes router interface
The next hop must be a subnet
of one of the router interfaces
ETX-5300A Ver. 1.0
Task
Command
Displaying the routing table
show routing-table
Comments
The following marking actions can be performed at the interface level, at the
config>router(1)>interface(interface_number)# prompt.
Task
Command
Defining router interface to be

of the loopback type
loopback
Assigning an IP address and a

subnet mask to the router
interface
address <IP-address/IP-mask>
Binding router interface to an

SVI or out-of-band management
Ethernet port
bind svi <port-number>
Configuring interface
management access
management-access {allow-all |
allow-ping}
bind mng-ethernet <slot/port>
Comments
no bind removes RIF link to SVI

or management Ethernet port
no bind
no management-access
disables management via RIF
no management-access
Assigning a name to the router
interface
name <interface-name>
Administratively enabling router

interface
no shutdown
Displaying interface status
show status

interface
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-5300A>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:
ETX-5300A Ver. 1.0
At the config>router(1)# prompt, enter show routing-table.

Router
8-67
The routing table is displayed.

ETX-5300A>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-5300A>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-5300A>config>router(1)>interface(1)# show status

IP Address
: 15.15.15.124/24
Default Router : --
Example
Figure 8-18 and script below illustrate configuration of router with one router
interface connected to a bridge port.
8-68
Router
ETX-5300A Ver. 1.0
SVI
6
Fl. 9
Port 1
SVI
7
BP 2
Fl. 10
Bridge
SVI
5
Port 2
BP 3
Fl. 11
Port 1
Fl. 12
Port 2
BP 1
Fl. 1
Fl. 7
SVI
1
Port 3
Fl. 2
SVI
4
RIF 1
Fl. 8
Port 3
Fl. 5
RIF 4
Fl. 3
SVI
2
Port 4
Fl. 4
SVI
3
Router
RIF 2
Fl. 6
Port 4
RIF 3
Main Ethernet
Card B
Main Ethernet
Card A
Figure 8-18. Router-over-Bridge Service
To configure router interfaces and bridge ports:

1. Enable the main card 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).
ETX-5300A Ver. 1.0
Router
8-69
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****************************************
8-70
Router
ETX-5300A Ver. 1.0
#***************************Configuring_SVIs*********************************
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
ETX-5300A Ver. 1.0
Router
8-71

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****************************************
error is detected.
8-72
Router
ETX-5300A Ver. 1.0

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

routers is reached
The maximum number of routers (1) has been 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

has been reached
Cannot add a new RIF if the maximum number of RIFs has been
reached or the RIF IP address/mask overlaps the subnet of an
existing RIF
The interface must have an IP mask

assigned to it
RIF IP mask has not been configured
Wrong IP address for interface, in the

current subnet
Invalid RIF IP address is for the current subnet (first/last address

of the subnet or 0.0.0.0)
This address already exists in a static

route entry
A static route with the same destination IP address and the

same cost (metric) has already been added
This interface already created with

different loopback argument
Cannot change RIF type when RIF is active
The interface must have an IP address

assigned to it
Cannot activate a RIF with no IP address 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

mask must be consistent
Destination IP address and IP mask of a static route do not

match
Wrong value for priority
The metric value (cost) of a static route is out of range (1255)
The address must be an IP address in the

local network
The next hop of a static route is not in the subnet of any

existing RIF
The interface number is not a router

interface of this router
Destination RIF defined for a static route does not exist
The interface must be bound to a P2P

port
Destination RIF defined for a static route must be bound to a

P2P port
Cannot add static route, maximum

number has been reached
The maximum number of static routes has been reached
ETX-5300A Ver. 1.0
Router
8-73
Message
Description
The address must be different from a

router interface IP address
The next hop IP address of a static route must be different from

a RIF IP address
8.9
ETX-5300A 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.
Standards
IEEE 802.1p, IEEE 802.1Q.
Benefits
Flexible Ethernet QoS and extensive TM capabilities allow ETX-5300A 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.
Appendix B details QoS capabilities of ETX-5300A, discussing the following:
Traffic management (queues, queue blocks, queue groups, shaping and

congestion avoidance)
CoS mapping
Ingress color mapping
Policing
Marking.
This QoS section describes profile creation, gives default profiles (where
applicable), and provides a configuration example.
Traffic Management
ETX-5300A devices employ various traffic engineering techniques to optimize
service delivery and ensure end-to-end QoS. They enable multi-criteria traffic
classification as well as metering, policing and shaping to rate-limit user traffic
according to CIR and EIR profiles.
8-74
ETX-5300A Ver. 1.0
A 3-level hierarchical scheduling mechanism combines strict priority and weighted

fair queue scheduling to handle different types of traffic.
Weighted random early detection (WRED) policy is used for intelligent queue
management and congestion avoidance.
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 (see Traffic Management in Appendix B for details).
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). Traffic Management in Appendix B details the
ETX-5300A 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 postforwarding (egress) traffic management.
Pre-Forwarding (Ingress) TM
Post-Forwarding (Egress) TM
CIR
CBS
CIR/EIR
CBS/EBS
01 Gbps
064 kbyte
0.256 kbps 10 Gbps
0, 10512 kbyte
Factory Defaults
By default, there are no shaper profiles in the system.
Configuring Shaper
To define a shaper profile:

1. At the configure>qos# prompt, enter shaper-profile followed by profile name.
The config>qos>shaper-profile(profile_name)$ prompt is displayed.
2. Configure the shaper profile as illustrated and explained below.
ETX-5300A Ver. 1.0
8-75
3. 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.
Task
Command
Comments
Defining CIR, EIR data rate and

CBS, EBS burst rate
bandwidth [cir <cir-kbit-sec>] [cbs

<cbs-bytes>] [eir <eir-kbit-sec>] [ebs
<ebs-bytes>]
For single-rate shapers, use

only CIR/CBS values.
EBS = 0 is valid when EIR = 0.
CBS=0 is valid when CIR= 0.
Compensating for Layer-1

overhead and additional VLAN
tag (in bytes)
compensation <063>
Compensation configuration is
available for pre-forwarding
(ingress) traffic management
only.
Example
See the Example at the end of the Traffic Management 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

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,

max number of profiles has been
reached
The maximum number of profiles (128) has been reached and

no additional shaper/policer profiles can be added
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-5300A 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.
8-76
ETX-5300A Ver. 1.0
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. If a packet is

queued and the queue size is between 0 and minimum threshold, the packet
is admitted.
Maximum threshold: a percentage of the maximum queue depth. If a packet is

queued and the queue size is between the minimum threshold and the
maximum threshold, the packet is dropped according to the drop probability
of the particular queue size.
Maximum drop probability: a percentage of the maximum threshold queue

size that defines the drop probability.
Drop
Probability
100%
Max Drop
Probability
Min
Threshold
Max
Threshold
100%
Queue
Depth
Figure 8-19. WRED Profile
Factory Defaults
By default, ETX-5300A provides one WRED profile (DefaultWREDProfile) with the
following settings:
ETX-5300A Ver. 1.0
Green packets
Minimum threshold 100%
Maximum threshold 100%
Maximum probability 100%
Yellow packets:
Maximum probability 100%.
8-77
Configuring WRED
To define a WRED profile:

1. At the configure>qos# prompt, enter wred-profile followed by profile name.
The config>qos>wred-profile(profile_name)$ prompt is displayed.
2. Configure the WRED profile as illustrated and explained below.
3. Assign WRED profile to an internal scheduling queue (see Internal Queue
below).
Note
Using no before wred-profile (profile _name) deletes the WRED profile.
Task
Command
Comments
Defining minimum and maximum

thresholds and maximum
probability
color green [min <0100> max <0

100> [probability <0100>]
A WRED profile must include

both green and yellow packet
types
color yellow [min <0100> max <0

100> [probability <0100>]
Example
See Example at the end of the Traffic Management section
error is detected.
Message
Description
Illegal value
WRED profile is in use and cannot be

changed/deleted
The WRED profile is being used by an internal queue. Remove

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

additional WRED profiles can be added
The WRED profile name is already in use

use
Default WRED profile cannot be

changed/deleted
It is not possible to modify or delete a default WRED profile
Internal Queue
Internal queues are tier-1 scheduling elements of ETX-5300A, 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-5300A
supports up to 16K of internal queue profiles per chassis.
8-78
ETX-5300A Ver. 1.0
For a detailed explanation of ETX-5300A scheduling elements, see the Traffic

Management section in Appendix B.
Factory Defaults
By default, ETX-5300A 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.
Task
Command
Comments
Assigning a WRED profile to the

internal queue
congestion-avoidance wred profile

<wred-profile-name>
You can assign a user-defined

or default (DefaultWREDProfile)
to the internal queue.
no congestion-avoidance wred
no congestion-avoidance wred
removes a WRED profile
association.
Setting scheduling method
scheduling { strict | wfq <weight>}
The weight range is 04095
Assigning a shaper profile to the

internal queue
shaper profile <shaper-profile-name>
no shaper-profile removes a
shaper profile association
no shaper profile
Example
See Example at the end of the Traffic Management section
ETX-5300A Ver. 1.0
8-79
Queue Block
The queue block is a tier-2 scheduling element in the ETX-5300A traffic
management system. It consists of internal queues, and, in turn, serves as part of
a tier-3 element a queue group.
The Traffic Management section in Appendix B describes level-0, level-1 and
level-3 queue blocks, and details their relationships to different types of queue
groups.
Factory Defaults
ETX-5300A provides several queue block profiles, depending on the queue group
types that use them. The Traffic Management section in Appendix B describes
default the queue block profiles. The default queue block profiles are as follows:
q_block_4_WFQ_4_SP_default
q_block_8_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.
2. At the configure>qos# prompt, enter queue-block-profile followed by profile
name.
The config>qos>queue-block-profile(profile_name)$ prompt is displayed.
3. 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)$
4. Assign an internal queue profile to each internal queue within the queue
block (see internal-profile in table below).
5. 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.
8-80
ETX-5300A Ver. 1.0
Task
Command
Comments
Assigning an internal queue

profile to the queue within the
queue block
internal-profile profile
<internal_profile_name>
no internal-profile removes an
internal queue profile
association from the queue
within the queue block
no internal-profile
Example
See Example at the end of the Traffic Management section.
Queue Group
Queue group is a tier-3 scheduling element in the ETX-5300A traffic management
system. Queue groups perform pre- and post-forwarding (ingress and egress)
traffic management and are subdivided into the different types, as explained in
the Traffic Management section of Appendix B.
Factory Defaults
ETX-5300A provides several queue group profiles, depending group type. Traffic
Management section in Appendix B describes default queue group profiles. 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:
Note
queue-block 0/<1N>
queue-block 1/<1N>
queue-block 2/<1N>
The queue block number depends on the queue group type that the queue
block belongs to. Traffic Management in Appendix B 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).
ETX-5300A Ver. 1.0
8-81
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.
Task
Command
Assigning a name to the queue

block
name <block_name>
Assigning a queue block profile
profile <queue_block_profile>
Binding a queue block to a queue in

the next-level queue block
bind queue <queue_number> block

<level/number>
Assigning a shaper profile
shaper profile <shaper_profile>
Comments
Level-2 (highest)
queue block cannot
be bound to anything
Example
error is detected.
Table 8-20. Queue Configuration Error Messages
Message
Description
Illegal value
Internal queue profile is in use and

The internal queue profile is being used by a queue block.

Remove the queue block association to delete or modify an
internal queue profile.
Queue block profile is in use and cannot

be changed/deleted
The queue block profile is being used by a queue group. Remove

the queue group association to delete or modify a queue block
profile.
Only first 4 internal queues in the queue

block can be strict
The first four internal queues in a queue block must use a strict
priority mechanism
Dual shaper cannot be bound
Use single-rate shaper
The selected profile does not exist
8-82
ETX-5300A Ver. 1.0
Message
Description
Profile cannot be added, max number of

profiles has been reached
The maximum number of internal queue profiles has been

reached and no additional profiles can be added
The queue profile name is not unique

use
Default profile cannot be

changed/deleted
It is not possible to modify or delete a default queue profile
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

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

the same level
A queue block with the same name already exist in the same
level
Source group queue group profile for

inherit action does not exist
Indicates an attempt to use a non-existing queue group profile

as a source for a new queue group profile
Specified queue group profile does not

exist
Indicates an attempt to use a non-existing queue group profile
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

another queue bock
Indicates an attempt to bind an internal queue already in use to

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,

reached
The maximum number of queue group profiles has been reached

and no additional profiles can be added
Internal queue mismatch in level-0 queue

block
Invalid queue combination in a level-0 queue block
Strict internal queues cannot be

assigned to level-1 and level-2 queue
blocks
Level-1 and level-2 queue blocks can have only WFQ queues
ETX-5300A Ver. 1.0
8-83
Message
Description
WRED profiles cannot be assigned to

internal queues in level-1 and level-2
queue blocks
Internal queues in level-1 and level-2 queue blocks cannot have

WRED profiles assigned to them
Green or yellow color settings are

missing from WRED profile
No color values are defined in a WRED profile assigned to an

internal queue
Strict internal queues are missing from

level 0 queue block
Mandatory internal queues with strict priority have not been

assigned to a level-0 queue block.
WFQs are missing from level 0 queue

block
Mandatory internal queues with WFQ priority have not been

assigned to a level-0 queue block
Illegal weight value for internal queues in

level 0 queue block
The weight values entered are not valid for internal queues with
WFQ priority in a level-0 queue block
Illegal weight value for internal queues in

level 1 queue block
The weight values entered are not valid for internal queues with
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
Dual shaper cannot be bound to level 0

queue block
Dual shaper profiles cannot be assigned to a level 0 queue block

in an ingress (pre-forwarding) queue group
Dual shaper cannot be bound to level 1

queue block
Dual shaper profiles cannot be assigned to a level 1 queue block

in an ingress (pre-forwarding) queue group
Cannot be bound to internal queues in

level-1 and level-2 queue blocks
Shaper profiles cannot be assigned to internal queues in level-1

and level-2 queue blocks
CoS Mapping
User priorities must be mapped to internal Class of Service (CoS) values,
according to P-bit, DSCP, IP Precedence or per flow criteria, as detailed in
Appendix B. The newly defined CoS can then be used for:
P-bit handling during VLAN editing
Queue mapping.
In other words, each packet is first normalized to a CoS value (07), this CoS is
then used for VLAN editing (P-bit) or priority queue mapping.
Ingress Traffic
CoS Mapping
CoS to P-bit (VLAN Editing)
Profiles to map packet to CoS:
Profiles to map:
P-bit to CoS (07)
DSCP to CoS (07)
IP Precedence to CoS (07)
Flow to CoS
CoS to P-bit
Queue Mapping
Profiles to map:
CoS to priority queue (07)
The CoS Mapping section in Appendix B gives detailed description of CoS mapping
methods supported by directly- and indirectly-attached ports, according to a
classification key used for traffic classification.
8-84
ETX-5300A Ver. 1.0
Factory Defaults
ETX-5300A 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. CoS Mapping section in Appendix B describes the default
CoS mapping profiles.
Configuring CoS Mapping
To define a CoS mapping profile:

1. 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.

2. Map the user priority to a CoS value (user priority values 07 for P-bit and IP
Precedence, 063 for DSCP; CoS values 07):
map <07> to-cos <07>
map <063> to-cos <07>.
Example
error is detected.

Message
Description
Illegal value
CoS mapping profile is in use and cannot

be changed/deleted
The CoS mapping profile is being used by a flow. Remove the

flow association to delete or modify the CoS mapping profile.
Default CoS mapping profile cannot be

changed/deleted
It is not possible to modify or delete a default CoS profile
The CoS mapping profile name is not unique

use
Max number of profiles using one CoS

mapping method has been reached
The maximum number of profiles (12 or 16) using the same CoS
mapping method (P-bit to CoS, DSCP to CoS, etc.) has been
reached
ETX-5300A Ver. 1.0
8-85
Color Mapping
ETX-5300A supports an ingress color mapping mechanism as part of its traffic
policing features. The mechanism inspects incoming packets and assigns a green
or yellow color value according to the 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).
ETX-5300A supports up to 36 ingress color mapping profiles (12 of each type).

Packet color is also used by WRED mechanism for preventing congestion and for
setting DEI value during VLAN editing.
The ingress color mapping method for both directly- and indirectly-attached ports
depends on the classification key used for the port. See Ingress Color Mapping in
Appendix B for details.
Note
For directly-attached ports, color and CoS mapping methods, applied to the same
flow, must belong to the same color-CoS-mapping combination, as detailed in the
CoS Mapping section of Appendix B.
Factory Defaults
By default, ETX-5300A marks all incoming packets as green.
Configuring Color Mapping
To define a color mapping profile:

1. 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.
2. Map the user priority to a color value (user priority values 07 for P-bit and IP
Precedence, 063 for DSCP, or DEI 01; color values: green and yellow):
Note
map <07> to green or yellow
map <063> to green or yellow
DEI to color mapping is fixed: 0 to green and 1 to yellow.
Example
8-86
ETX-5300A Ver. 1.0
error is detected.
Message
Description
Illegal value
Color mapping profile is in use and

The color mapping profile is being used by a flow. Remove the

flow association to delete or modify the color mapping profile.
Color mapping profile cannot be added,

reached

additional color mapping profiles can be added
The color mapping profile name is not unique

use
Max number of profiles using one color

mapping method has been reached
The maximum number of profiles (12) using the same color

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 indirectly-attached ports to regulate traffic according to
the contracted CIR, EIR, CBS and EBS bandwidth profiles. 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.
Policing is implemented by defining policer bandwidth profiles and assigning them
to one or more (up to 16) flows (aggregate policer profile) .
ETX-5300A supports up to 128 policer bandwidth profiles (regular and aggregate)
with up to:
Note
2K policer instances per each Ethernet I/O card
Flows from different I/O port groups (110, 1120) 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-5300A does not have policer profiles.
ETX-5300A Ver. 1.0
8-87
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.
Task
Command
Defining bandwidth profile, using

CIR/CBS and EIR/EBS rates
bandwidth [cir <cir-kbit-sec>] [cbs <cbsbytes>] [eir <eir-kbit-sec>] [ebs <ebs-bytes>]
Configuring color awareness of the

policer
color-aware
Compensating for Layer-1 overhead

and additional VLAN tag (in bytes)
compensation <063>
Enabling coupling flag to control

the volume of yellow packets
coupling-flag
no color-aware
no coupling-flag
Comments
no color-aware enables
the color blind mode of
the policer
no coupling-flag
disables 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.
Task
Command
Assigning policer profile
policer profile <policer_profile_name>
Specifying rate sampling

window (minutes)
rate-sampling-window <130>
Displaying the associated

flows
show flows
Displaying statistics for

the associated flows
show statistics running
Clearing the statistics for

the associated flows
clear-statistics
8-88
Comments
ETX-5300A Ver. 1.0
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 (1114).
Table 8-23 lists the messages generated by ETX-5300A when a policer
configuration error is detected. Table 8-24 lists the messages generated by
ETX-5300A when a policer aggregate configuration error is detected.
Table 8-23. Policer Configuration Error Messages
Message
Description
Illegal value
Shaper/policer profile is in use and

The shaper profile is being used by a queue or queue block; or

the 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,

reached

no additional shaper/policer profiles can be added
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 8-24. Policer Aggregate Configuration Error Messages

Message
Description
Illegal value
Policer aggregate profile is in use and

The policer aggregate profile is being used by a flow. Remove

the association to delete or modify a policer aggregate profile.
Policer aggregate profile cannot be

added, max number of profiles has been
reached

no additional policer aggregate profiles can be added
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
ETX-5300A Ver. 1.0
8-89
optionally the Drop Eligible Indicator (DEI) bit is specified in the frame header.
ETX-5300A supports up to 16 color-aware and color-blind marking profiles.
Note
A color-aware profile translates CoS (07) and packet color (all, green,
yellow) into P-bit (07) and DEI (yellow, green) values
A color-blind profile translates CoS (07) into P-bit (07) and DEI (yellow,
green) values.
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-5300A does not have any marking profiles.
Configuring Color-Blind Marking Profile

When a color-blind marking profile is used, ETX-5300A 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 <07>
to <07> dei <green | yellow>.
Configuring Color-Aware Marking Profile

When a color-aware marking profile is used, ETX-5300A 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 alwaysgreen 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 <07>
<green | yellow> to <07> 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.
8-90
ETX-5300A Ver. 1.0
error is detected.
Message
Description
Illegal value
Color mapping profile is in use and

The color mapping profile is being used by a flow. Remove the

flow association to delete or modify color mapping profile.
Marking profile cannot be added, max


additional marking profiles can be added
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

range
The selected mark valuemust be within the range 07
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 8-26. CoS to Priority Queue Mapping

CoS
0
Queue
1
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 Figure 8-20.
ETX-5300A Ver. 1.0
8-91
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 highpriority queues. The rest of the queues use the default WRED profile, or do
not provide congestion avoidance, such as level-1 and level-2 queue blocks.
3. Define internal queue profiles, specifying their scheduling types, shaping and
WRED profiles (where applicable).
4. Configure level-0, level-1 and level -2 queue block profiles with queues, using
internal queue profiles.
5. 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.
6. Assign the queue group to the main card ports.
7. Select classification keys for the main card ports.
9. Configure 12 VLAN-type classifier profiles.
values.
11. Configure the color mapping profile to map user color to internal color values.
12. Configure 12 flows from port 1 to port 2 on the main card and direct them to
the relevant level-0 queue blocks.
8-92
ETX-5300A Ver. 1.0
Level-0 SEs
q_block_4_WFQ_4_SP_10_40
CIR
Shapers
Flow 1
Flow 2
Flow 3
Flow 4
Flow 5
Flow 6
Flow 7
WR.1
SP 1
Sh. 7
WR.1
SP 2
Sh. 7
WR.1
SP 3
Sh. 7
WR.1
SP4
Sh. 7
Def. WR.
WFQ 10
Def. WR.
WFQ 20
Def. WR.
WFQ 30
Def. WR.
WFQ 40
0/1
CIR/EIR
Shapers
Sh. 7
Sh. 1
CIR
Shapers
Flow 10
Level-1 SEs
0/2
q_block_11_queue_WFQ_10_20_30
1/1
WR.1
SP 1
Sh. 7
WR.1
SP 2
Sh. 7
WR.1
SP 3
Sh. 7
WFQ 20
WR.1
SP4
Sh. 7
WFQ 30
Def. WR.
WFQ 10
Def. WR.
WFQ 20
Def. WR.
WFQ 30
Def. WR.
WFQ 40
CIR/EIR
Shapers
WFQ 10
Sh. 7
CIR/EIR
Shapers
Sh. 2
Sh. 4
CIR
Shapers
Flow 20
WR.1
SP 1
Sh. 7
WR.1
SP 2
Sh. 7
WR.1
SP 3
Sh. 7
WR.1
SP4
Sh. 7
0/3
CIR/EIR
Shapers
Level-2 SE
q_block_21_queue_WFQ_10_20
2/1
Def. WR.
WFQ 40
WFQ 10
Def. WR.
WFQ 30
WFQ 20
Def. WR.
WFQ 20
Def. WR.
WFQ 10
Sh. 3
Sh. 6
Sh. 7
CIR
Shapers
Flow 30
WR.1
SP 1
Sh. 7
WR.1
SP 2
Sh. 7
WR.1
SP 3
Sh. 7
WR.1
SP4
Sh. 7
Def. WR.
WFQ 10
Def. WR.
WFQ 20
Def. WR.
WFQ 30
Def. WR.
WFQ 40
0/4
CIR/EIR
Shapers
Sh. 7
Sh. 3
q_block_11_queue_WFQ_10_20
1/2
CIR/EIR
Shapers
WFQ 10
CIR
Shapers
WR.1
Flow 40
WFQ 20
0/5
Sh. 5
SP 1
Sh. 7
WR.1
SP 2
Sh. 7
WR.1
SP 3
Sh. 7
WR.1
SP4
Sh. 7
Def. WR.
WFQ 10
Def. WR.
WFQ 20
Def. WR.
WFQ 30
Def. WR.
WFQ 40
CIR/EIR
Shapers
Sh. 7
Sh. 1
Figure 8-20. Traffic Management Example

ETX-5300A Ver. 1.0
CIR
Shaper
8-93
************************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
8-94
ETX-5300A Ver. 1.0
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"
ETX-5300A Ver. 1.0
8-95

exit all
#*********************************End****************************************
#********************* Configuring_Queue_Group_Profile1**********************
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
8-96
ETX-5300A Ver. 1.0
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
ETX-5300A Ver. 1.0
8-97

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
cos-mapping profile cos7_0
0/1
no shutdown
exit all
classifier class101
0/1
8-98
ETX-5300A Ver. 1.0
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
ETX-5300A Ver. 1.0
8-99

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************************************
8-100
ETX-5300A Ver. 1.0
8.10 Ethernet OAM

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-5300A also supports performance monitoring per Y.1731.
Standards
IEEE 802.1ag-D8, ITU-T Y.1731
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).
ETX-5300A Ver. 1.0
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 Point (MIP) Created in the middle of the domain.

Unlike MEPs, MIPs are passive points, responding only when triggered by CFM
Ethernet OAM
8-101
trace route and loopback messages. A MIP consists of two MIP Half Functions
(MHFs).
OAM Functions
RADs carrier Ethernet aggregation and demarcation devices feature a
comprehensive hardware-based Ethernet OAM and performance monitoring for
SLA assurance:
Note
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).
Loss measurement is supported only if the MEP-connected flows have their

statistic counters enabled (PM-enabled).
OAM Connectivity
Figure 8-21 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:
8-102
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-5300A devices act as MIPs.
Segment OAM session (operator service ME) between ETX-2xxA and the
network side of ETX-5300A.
Transport OAM session (tunnel ME) between network ports of two

ETX-5300A devices.
Ethernet OAM
ETX-5300A Ver. 1.0

Subscriber
Equipment
Operator A NEs
Service Provider
Subscriber
Equipment
Operator B NEs
5
Subscriber ME
EVC ME
Ethernet
Operator A Service ME
Operator B Service ME
UNI ME
UNI ME
Transport
Tunnel ME
ETX-2xxA
ETX-2xxA
ETX-5300A
Router
Router
ETX-5300A
Legend:
Triangle MEP (Maintenance End Point)
Circle MIP (Maintenance Intermediary Point)
Figure 8-21. Multi-Domain Ethernet Service OAM
MEPs and Services

ETX-5300A Ethernet main cards support Ethernet OAM functionality and host
MEPs as illustrated in Figure 8-22. A MEP can be either Down or Up, depending on
its position and port association, as explained below.
SAP
GbE
10 GbE
MEP
I/O Ethernet Card
10 GbE
MEP
BP
Bridge BP
10 GbE
MEP
10 GbE
MEP
10 GbE
Main Ethernet Card
Figure 8-22. Ethernet Main Card MEPs

ETX-5300A Ver. 1.0
Ethernet OAM
8-103
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 or multipoint services. Different MEP locations are
illustrated below.
Figure 8-23 illustrates a point-to-point service between two main card ports with
the MEP bound to port A. Tx flow in the service is directed to a queue block.
Tx Flow
MEP
Rx Flow
Main Card
Port A
Main Card
Port B
Figure 8-23. PtP Service with Down MEP Bound to Main Card Port A
Figure 8-24 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
I/O Card
Port B
Figure 8-24. PtP Service with Down MEP Bound to I/O Card Port B
Figure 8-25 illustrates a point-to-point service between main and I/O card ports
with MEP bound to port A. Tx flow in the service is directed to a queue block.
Rx Flow
MEP
SAP
Tx Flow
I/O Card
Port B
Main Card
Port A
Figure 8-25. PtP Service with Down MEP Bound to Main Card Port A
Figure 8-26 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
I/O Card
Port A
8-104
Ethernet OAM
Rx Flow
I/O Card
Port B
ETX-5300A Ver. 1.0
Figure 8-26. PtP Service between Two I/O Card Ports with Down MEP Bound to Port B
Figure 8-27 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 8-27. 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 reside at bridge ingress and are bound to bridge ports. These MEPs
receive and send CFM PDU from and to the bridge entity. Up MEPs are supported
for multipoint services only. The Up MEPs inherit their MAC addresses from the
corresponding physical ports (egress ports of Tx flows). Different MEP locations
are illustrated below.
Figure 8-28 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 8-28. Multipoint Service with Up MEP Bound to I/O Card Port A
Figure 8-29 illustrates a multipoint service between main card and bridge ports
with the Up MEP bound to the bridge port. Tx flow in this service is directed to
the BP SVI.
ETX-5300A Ver. 1.0
Ethernet OAM
8-105
Rx Flow
BP
Bridge BP
SVI
MEP
Tx Flow
Main Card
Port A
Figure 8-29. Multipoint Service with Up MEP Bound to Main Card Port A
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). MIP responds to link trace messages (LTMs) and loopback messages
(LBMs), whose MD level is equal to the MIP MD level. ETX-5300A supports up to
512 MIPs.
MIP
LBM/LTM
LBM/LTM
Flow X
Flow X
LBR/LTR
MHF MHF
LBR/LTR
Figure 8-30. 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 bridge port.
MIP locations are similar to those of MEP.

The MIPs are defined under MD level and are characterized by the following:
8-106
The physical port to which they are bound, inheriting the ports 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
Single VLAN+P-bit
Single outer + single inner VLAN
Single outer VLAN + P-bit + single inner VLAN
Ethernet OAM
ETX-5300A Ver. 1.0
Rx classification, when Rx flow originates from SA with the Match All

classification profile
Tx flow, originating from the physical port facing MHF 2
Optional egress queue for the Tx flow.
Figure 8-31 and Figure 8-32 illustrate MIPs in point-to-point and multipoint
services.
Rx Flow
Tx Flow
Main Card
Port A
Rx Flow
Tx Flow
Main Card
Port A
MIP
(bound to port B)
MHF 1
MHF 1
Main Card
Port B
MIP
(bound to port B)
SAP
MHF 1
MIP
(bound to port A)
Main Card
Port A
MHF 2
MHF 2
MHF 2
Tx Flow
I/O Card
Port B
SAP
Rx Flow
I/O Card
Port B
Figure 8-31. MIPs in Point-to-Point Service
Rx Flow
BP
Bridge BP
MIP
(bound to port B)
SVI
Tx Flow
MHF 1
MHF 2
Main Card
Port B
Figure 8-32. MIP in Multipoint Service
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
ETX-5300A Ver. 1.0
Ethernet OAM
8-107
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 (07) configuration.
AIS, LCK, LOC
Rx Flow
Tx Flow
Port A
MEP
AIS
(with client MD level)
Port B
Figure 8-33. 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
Table 8-27.
8-108
Ethernet OAM
ETX-5300A Ver. 1.0
Table 8-27. CCM Group Destination MAC

01-80-C2-00-00-3y
CCM MD Level
Four Address Bits y
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-bitto-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 Figure 8-34, 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.
ETX-5300A Ver. 1.0
Ethernet OAM
8-109

LTM
MEP
LTR
Main Card
Port A
Main Card
Port B
Figure 8-34. MEP with LTM Sent from the Card Port in Point-to-Point Service
In Figure 8-35, 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
BP
Bridge BP
SVI
MEP
Main Card
Port A
LTR
Figure 8-35. MEP with LTM Sent from the Bridge Port in Multipoint Service
In Figure 8-36, the MIP always responds with LTR and relays the LTM.
LTM
LTM
LTR
MIP
Main Card
Port A
Main Card
Port B
Figure 8-36. MIP with LTM Sent from the Card Port in Point-to-Point Service
In Figure 8-37, 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 8-37. MIP with LTM Sent from the Bridge Port in Multipoint Service
In Figure 8-38, the MIP responds with LTR if the target MAC address of the
received LTM has been learned on another bridge port. The MIP relays the LTM to
the bridge port with the target MAC address. If the target MAC is unknown, the
MIP floods the LTM.
8-110
Ethernet OAM
ETX-5300A Ver. 1.0
LTM
BP
Bridge BP
LTM
SVI
LTR
MIP
Main Card
Port A
Figure 8-38. MIP with LTM Sent from the Card Port in Multipoint Service
Performance Monitoring
ETX-5300A Ethernet service OAM PM functionality complies with the Y.1731
requirements. ETX-5300A provides per-service loss and delay measurement and
event reporting.
Note
Loss measurement is supported only if the MEP-connected flows have their

statistic counters enabled (PM-enabled).
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-5300A supports single-ended loss measurement (LM) with on-demand
LMM transmission and automatic LM response (up to 128 simultaneous LM
sessions per chassis). OAM MEPs measure frame loss only if statistic counters
have been enabled on the incoming and outgoing flows. LM is not supported
over tunnels.
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 frames destination node.
ETX-5300A supports dual-ended delay measurement (DM) with on-demand
DMM transmission and automatic DM response (up to 128 simultaneous DM
sessions per chassis). Measurement is performed for delays of up to 1
second with full DM over tunnels.
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-5300A elements, such as ERP.
1. Configure maintenance domains (MDs)
2. Define maintenance associations (MAs)
3. Add maintenance endpoints (MEPs)
ETX-5300A Ver. 1.0
Ethernet OAM
8-111
4. Add maintenance intermediary points (MIPs)

5. Define endpoint services
6. Add destination network elements (NEs)
7. Configuring counter thresholds.
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 14095.
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
Task
Command
Comments
Configuring maintenance
association for the MD
maintenance -association <maid>
Refer to Configuring Maintenance

Associations.
no maintenance association <maid>
no maintenance association <maid>

deletes the MA
Specifying the maintenance
domain level
md-level <md-level>
Defining MIPs
mip <mip id>
The allowed range for md-level is 07
Note: If the pre-standard OAM protocol

is used, the only value allowed for the
maintenance domain level is 3.
no mip <mip id>

Intermediary Points.
no mip <mip id> deletes the MIP.
8-112
Ethernet OAM
ETX-5300A Ver. 1.0
Task
Command
Comments
Displaying information on
configured MAs
show maintenance-association <maid>
Displaying information on
configured MIPs
show mip <mip id>
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 14095.
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 maintenanceassociation <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
Task
Command
Specifying MA name in UINT

(unsigned integer) format
ma-name <065535>
Specifying the interval

between continuity check
messages
ccm-interval {3.33ms | 10ms |

100ms | 1s | 10s | 1min | 10min}
Configuring MEP for the MA
mep <mepid>
Comments
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,
ETX-5300A Ver. 1.0
Ethernet OAM
8-113
localize, and diagnose connectivity problems. ETX-5300A 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 14098.
The MEP is created and the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)$ is displayed.
To delete a maintenance endpoint:
At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:

no mep <mepid>
The maintenance endpoint is deleted.
Note
You can remove a maintenance endpoint regardless of whether it contains

services.
To configure a maintenance endpoint:
maintenance-association <maid> mep <mepid>to select the maintenance
endpoint to configure.
The prompt config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
is displayed.
Task
Command
Comments
Enabling AIS sending and

defining interval
ais [ interval { 1s | 1min }]

[priority <priority>]
To disable AIS sending, enter no ais
Binding the MEP to an

Ethernet port, LAG or SVI
bind ethernet <slot/port>
To remove the MEP from an Ethernet port,

LAG or SVI, enter no bind
bind lag <port_number>

bind svi <port_number>
no bind
Enabling initiation of
continuity check messages
(CCM)
ccm-initiate
To disable initiating continuity check

messages, enter no ccm-initiate
Specifying the priority of

CCMs, LBMs and LTMs
transmitted by the MEP
ccm-priority <priority>
The allowed range for <priority> is 07
Associating the MEP with a

classifier profile
classification profile <profile_name>
Classifier profile is needed when the MEP

Rx flow has the SAP ingress port (in this
case the flow classifier profile is Match
All).
no classification profile
To delete classifier profile assignment,

enter no classification profile.
8-114
Ethernet OAM
ETX-5300A Ver. 1.0
Task
Command
Comments
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 profile
cos-mapping profile <profile_name>
The CoS mapping profile must be

P-bit-to-CoS to assign the class of service
to the packets transmitted by the MEP
(CCMs, LBTs etc).
no cos-mapping profile
To delete CoS mapping profile assignment,

enter no cos-mapping profile.
Defining the MEP direction
direction {up | down}
Assigning unidirectional Rx
and Tx flows to the MEP
flow uni-direction rx <rx_flow_name> [tx

<tx-name>]
To delete flow assignment, enter no flow

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

MEP
queue queue-mapping
<queue_mapping_profile_name>
[block <level_id>/<queue_id>]
To delete queue assignment, enter no

queue queue-mapping
no queue queue-mapping
Defining remote MEP with
which the MEP
communicates
remote-mep <remote_mep_id>
Allowed range for remote MEP is 18191
no remote-mep <remote_mep_id>
The MEP ID and the remote MEP ID must

be different. You can define up to 511
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

MEP
service <service_id>
Displaying MEP status
show status
Displaying remote MEP

status
show remote-mep <remote-mep-id>

status
Displaying MEP service

status
show service <service_id>
Administratively enabling
MEP
no shutdown
Endpoint Services
To deactivate the MEP, enter shutdown
Configuring Maintenance Intermediary Points

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-5300A supports up to 512 MIPs.
ETX-5300A Ver. 1.0
Ethernet OAM
8-115
To add a maintenance intermediary 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:

1. 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
Task
Command
Comments
Binding the MIP to an

Ethernet port, LAG or SVI
bind ethernet <slot/port>
To remove the MIP from an Ethernet port,

LAG or SVI, enter no bind
bind lag <port_number>

bind svi <port_number>
no bind
Assigning unidirectional Rx
and Tx flows to the MIP
flow uni-direction rx <rx_flow_name> [tx

<tx-name>]
To delete flow assignment, enter no flow

uni-direction
no flow uni-direction
Configuring MIP half
functions (MHF)
mhf 1
MIP
no shutdown
Displaying MIP status
show status
See table below
mhf 2
To deactivate the MIP, enter shutdown
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.
Task
Command
Comments
Associating the MHF with a

classifier profile
classification profile <profile_name>
Classifier profile is needed when the MHF

Rx flow has the SAP ingress port (in this
case the flow classifier profile is Match
All).
no classification profile
To delete classifier profile assignment,

enter no classification profile.
Associating the MHF with a
CoS profile
cos-mapping profile <profile_name>

no cos-mapping profile
The CoS mapping profile must be

P-bit-to-CoS to assign the class of service
to the packets transmitted by the MHF
(CCMs, LBTs etc).
To delete CoS mapping profile assignment,
enter no cos-mapping profile.
8-116
Ethernet OAM
ETX-5300A Ver. 1.0
Task
Command
Comments
Defining the queue for the

MHF
queue queue-mapping
<queue_mapping_profile_name>
[block <level_id>/<queue_id>]
To delete queue assignment, enter no

queue queue-mapping
no queue queue-mapping
Configuring Maintenance Endpoint Services

You can configure a single service on a MEP. The service configures performance
monitoring (Y.1731) functionality for loss and delay measurements.
To add a MEP service:
At the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,

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

maintenance-association <maid> mep <mepid> service <serviceid> to select
the service to configure (<serviceid> is 18).
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#
is displayed.
Task
Command
Comments
Associating this service with a

priority for LMMs and DMMs
classification priority-bit <p-bit>
The allowed range is 07
Specifying delay threshold in

microseconds
delay-threshold <delay-thresh>
The allowed range for delay

threshold is: 15,000,000. If the
threshold is exceeded, the
service is declared as degraded.
Specifying delay variation

threshold in microseconds
delay-var-threshold <delay-var-thresh>
The allowed range for delay

variation threshold is:
15,000,000. If the threshold is
exceeded, the service is
declared as degraded.
Specifying the interval for

delay measurement messages,
to be used by all remote NEs
defined for service
dmm-interval {100ms | 1s | 10s}
ETX-5300A Ver. 1.0
Ethernet OAM
8-117
Task
Command
Specifying the interval for loss

measurement messages, to be
used by all remote NEs defined
for service
lmm-interval {100ms | 1s | 10s}
Configuring destination NE for

service
dest-ne <dest-ne-index>
Comments
See Configuring Destination NEs

below. The value range is
1255. One NE per service is
allowed.
To delete a destination NE,
enter no dest-ne.
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-5300A 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 1255.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)$ is displayed.
To configure a destination NE:

maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index> to select the destination NE to configure.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)
>dest-ne(<dest-ne-index>)# is displayed.
Task
Command
Defining the MAC address of

the destination NE
remote mac-address <mac>
8-118
Ethernet OAM
Comments
ETX-5300A Ver. 1.0
Task
Command
Enabling two-way delay

measurement method
delay two-way
Enabling loss measurement

method
loss { single-ended }
Displaying statistics data
show statistics
Clearing statistics
clear-statistics
Comments
no delay
no loss
Displaying OAM Statistics

You can display end-to-end performance monitoring data for the destination NEs.
ETX-5300A 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>).
The following prompt is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>
service(<serviceid>)>dest-ne(<dest-ne-index>)#.
Task
Command
Comments
Viewing running statistics
The statistics are displayed

as listed in Table 8-28
ETX-5300A Ver. 1.0
Ethernet OAM
8-119
Task
Command
Comments
Viewing statistics for the current

interval
show statistics current
The statistics for the current

interval are displayed as
listed in Table 8-28
Viewing the statistics for a

selected interval
show statistics interval <interval-num>
Allowed values for

interval-num: 196
The statistics for the
selected interval are
displayed as listed in
Table 8-28
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-28
Viewing statistics for previous day
show statistics previous-day
The statistics for the

previous day, as listed in
Table 8-28
Viewing running statistics,
statistics for the current interval,
statistics for all intervals, and day
statistics
show statistics all
All available performance

measurement counters, as
listed in Table 8-28
Viewing statistics for all intervals
show statistics all-intervals
Performance measurement
counters for all available
Intervals, as listed in
Table 8-28
Clearing the statistics for the
destination NE
clear-statistics
All statistical data for the

service are cleared, including
the stored interval data,
except for the time elapsed
since the start of the current
interval
Table 8-28. 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
8-120
Ethernet OAM
ETX-5300A Ver. 1.0
Parameter
Description
Far End Unavailable Seconds

(sec)
Total number of unavailable seconds in the remote MEP since the service
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
since the service was activated
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

(sec)
Total number of unavailable seconds in the local MEP since the service
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

Threshold
Number of frames that exceeded the delay variation threshold
Elapsed Time (sec)
Time (in seconds) elapsed since the service was activated
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.
Task
Command
Specifying remote MEP by

MAC address
lbm address <mac_address> [repeat <1

50>] [data-tlv-length <01900>]
Sending LBMs to default

multicast MAC address
lbm multicast [repeat <150>]
Checking OAM loopback

results
show lbm-results
Comments
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified by MAC
address.
To run an OAM link trace:
ETX-5300A Ver. 1.0

enter all necessary commands according to the tasks listed below.
Ethernet OAM
8-121
Task
Command
Comments
Specifying remote the MEP by

MAC address
linktrace address <mac-address>

[ttl <164>]
The TTL parameter specifies

the number of hops. Each unit
in the link trace decrements
the TTL until it reaches 0,
which terminates the link trace.
Destnation MAC address LTM
cannot be multicast.
Checking the OAM link trace

results
show linktrace-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 Figure 8-39).
To configure a Down MEP between main card ports:

1. Assign default queue groups to 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. Define a Down MEP bound to port 1 with CCM sent over P-bit 0.
9. Configure MEP service with LMMs and DMMs sent over P-bit 1.
10. Configure OAM event reporting thresholds for:
Delay and delay variation
Loss ratio
Unavailability ratio.
CCMs
EVC1_ing
EVC1_eg
Main Card B
Port 2
MEP
PSN
LMMs
LMRs
Main Card B
Port 1
MEP
DMMs
DMRs
Remote NE
Figure 8-39. Down MEP between Main Card Ports
8-122
Ethernet OAM
ETX-5300A Ver. 1.0
**********************Assigning_Default_Queue_Group_Profiles*********************
exit all
#*********************************End********************************************
**********************Assigning_Classification_Keys******************************
exit all
#*********************************End********************************************
************************Enabling_Main_Card_Ports*********************************
exit all
#*********************************End********************************************
************************Defining_Classifier_Profile******************************
match vlan 20
exit all
#*********************************End****************************************
************************Defining_Policer_Profiles********************************
exit all
#*********************************End********************************************
************************Defining_CoS_Mapping_Profile*****************************
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
egress-port ethernet main-b/2 queue-map-profile QueueMapDefaultProfile block 0/1
ingress-color profile color1
no shutdown
exit all
configure flows flow EVC1_ing
classifier class20
ETX-5300A Ver. 1.0
Ethernet OAM
8-123

no shutdown
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
direction down
flow uni-direction rx EVC1_ing tx EVC1_eg
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 Figure 8-40).
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.
8-124
Ethernet OAM
ETX-5300A Ver. 1.0
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 100 + P-bit 5
VLAN 300 + inner VLAN 100.
5. Configure two policer profiles.

7. Configure the following flows:
From I/O card port 1 to SAP (classification VLAN 100 + P-bit 6)

From I/O card port 1 to SAP (classification VLAN 100 + P-bit 5)
From SAP to main card port 1
From main card port 1 to I/O card port 1.
8. Define a Down MEP bound to port 1 with CCM sent over P-bit 0.
Loss ratio
SAG
SAP
CCMs
ECV2COS1
Port 1
ECV2COS2
SAP 1
EVC2_eg
Port 1
MEP
PSN
LMMs
LMRs
EVC2_ing
MEP
DMMs
DMRs
Remote NE
SAP
I/O Ethernet Card
Main Ethernet Card
Figure 8-40. Down MEP between Main and I/O Card Ports
ETX-5300A Ver. 1.0
Ethernet OAM
8-125
exit all
#*********************************End********************************************
config port ethernet main-b/1 classification-key vlan inner-vlan p-bit
exit all
#*********************************End********************************************
************************Enabling_Main_and_I/O_Card_Ports*************************
exit all
#*********************************End********************************************
************************Defining_Classifier_Profiles*****************************
exit all
match vlan 300 inner-vlan 100
exit all
#*********************************End****************************************
************************Defining_Policer_Profiles********************************
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
8-126
Ethernet OAM
ETX-5300A Ver. 1.0
no shutdown
exit all
configure flows flow EVC2COS2

cos-mapping fixed 1
ingress-color green
policer profile 2
no shutdown
exit all
configure flows flow EVC2_eg

classifier match-all
vlan-tag push vlan 300 p-bit copy
no shutdown
exit all
configure flows flow EVC2_ing

vlan-tag pop vlan
no shutdown
exit all
#*********************************End********************************************
config oam cfm
name uint 22
mep 2
direction down
flow uni-direction rx EVC2_ing tx EVC2_eg
queue queue-mapping QueueMapDefaultProfile block 0/1
ccm-initiate
ccm-priority 0
remote-mep 110
no shutdown
service 1
dest-ne 1
ETX-5300A Ver. 1.0
Ethernet OAM
8-127
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 Figure 8-40).
To configure a Up MEP between main card and bridge ports:

1. Assign default queue groups to the main card 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.
8. Define an Up MEP bound to port 1 with CCM sent over P-bit 0.
8-128
Loss ratio
Ethernet OAM
ETX-5300A Ver. 1.0
SVI
1
Flow 1
BP 1
MEP
Port 1
Flow 2
Flow 3
SVI
2
BP 2
Port 2
Flow 4
Flow 5
SVI
3
BP 3
Port 3
Flow 6
Bridge
Main Ethernet Card
Figure 8-41. Up MEP between Main Card and Bridge Ports

exit all
#*********************************End********************************************
exit all
#*********************************End********************************************
************************Enabling_Main_and_I/O_Card_Ports*************************
exit all
#*********************************End********************************************
************************Defining_Classifier_Profiles*****************************
exit all
#*********************************End****************************************
map 0 to-cos 0
map 1 to-cos 1
ETX-5300A Ver. 1.0
Ethernet OAM
8-129
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
egress-port ethernet main-a/1 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all
8-130
Ethernet OAM
ETX-5300A Ver. 1.0
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********************************************
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********************************************
ETX-5300A Ver. 1.0
Ethernet OAM
8-131

exit all
#*********************************End********************************************
error is detected.
Message
Description
Mismatch between flow and MIP

classification profiles
The classification profile bound to the MIP and the classification

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

with the flow has been reached
A single flow can be bound to up to eight MEPs
Different MEPs/MIPs, using the same

flow, must have different MD levels
When the same flow is bound to different MEPs/MIPs, the flow

must have different MD levels
MIP bound to Ethernet port or LAG must

have classification profile
When a MIP is bound to an Ethernet port or LAG, the MIP must

have a classification profile assigned to it
MIP-bound bridge port is not a member

of the MHFs classification profile VLAN
The bridge port of the SVI to which the MIP is bound is not a
member of the VLAN defined in the VLAN-based classification
profile used by the MIPs 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

MEP bound to an Ethernet port or LAG
The CoS profile cannot be bound to a MEP bound to an Ethernet

port or LAG
Cannot bind queue mapping profile to a

MEP bound to an Ethernet port or LAG
The queue mapping profile cannot be bound to a MEP bound to

an Ethernet port or LAG
Up MEPs are bound to SVI (B), Down

MEPs are bound to Ethernet port or LAG
The Up MEP must be bound to a bridge-type SVI. The Down MEP

must be bound to an Ethernet port or LAG
MA number is out of range
The MA number is out of range (12048)
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
8-132
Ethernet OAM
ETX-5300A Ver. 1.0
Message
Description
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 (06535)
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

been reached
Only one Down MEP is allowed per MA
Max number of Up MEPs per MA has

been reached
Up to 88 Up MEPs are allowed per MA
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 (04094)
VLAN ID can be changed in MEP/MIP

shutdown
The VLAN ID can be changed only when the MEP/MIP is

Classification profile can be changed in

MEP/MIP shutdown
Assigned classification profile can be changed only when the

MEP/MIP is administratively disabled
Invalid classification profile
The classification profile bound to the MEP/MIP is not valid.
A non-existing classification or CoS mapping profile has been

bound to MEP/MIP
CoS mapping profile must be P-bit-toCoS
Only a P-bit-to-CoS CoS mapping profile can be bound to

MEP/MIP
Only default queue mapping profile is

allowed
Only a default queue mapping profile (QueueMapDefaultProfile)

can be bound to MEP/MIP
Port can be changed, when MEP/MIP is in

shutdown
The port to which a MEP/MIP is bound can be changed only

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

destination NE exists
The OAM service can be administratively enabled only if a

destination NE has been defined for it
Cannot enable OAM service if no
The OAM service can be administratively enabled only if a
ETX-5300A Ver. 1.0
Ethernet OAM
8-133
Message
Description
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 SAP as ingress port
For Rx flow with ingress port defined as SAP, there must be a

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

MEP/MIP, if Rx flow uses Match All
classification
If Rx flow uses the Match All classification mode, a separate

classification profile must be bound to the MEP/MIP
Classification profile must be bound to

MEP/MIP, if Tx flow uses Match All
classification
If Tx flow uses the Match All classification mode, a separate

classification profile must be bound to the MEP/MIP
Classification profile cannot be bound to

MEP/MIP, if Rx flow uses other than
Match All classification
If Rx flow does not use the Match All classification mode, a

separate classification profile cannot be bound to the MEP/MIP
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 (12048)
Cannot delete MD with MA or MIP under

it
An MD with existing MAs or MIPs cannot be deleted
Illegal MD level
The MD level value is out of allowed range (07)
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
8-134
Ethernet OAM
ETX-5300A Ver. 1.0
Chapter 9
Timing and
Synchronization
ETX-5300A 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-5300A clock
capabilities:
Clock Selection
1588v2 Timing.
9.1
Clock Selection
This section discusses clock selection mechanism provided by ETX-5300A,

synchronization sources supported by the chassis and their configuration
methods.
Standards and MIBs

ETX-5300A timing functionality complies with following standards: G.703, G.704,
G.706, G.707, G.783, G.803, G.810813, 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.
Domain Parameter
Default Value
sync-network-type
quality min-level-station
Network type 1 SEC

Network type 2 ST3
max-frequency-deviation
ETX-5300A Ver. 1.0
1200 100 ppm
Clock Selection
9-1
Chapter 9 Timing and Synchronization
Domain Parameter
Default Value
mode
auto
force-t4-as-t0
Enabled
Source Parameter
Default Value
priority
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
tx-clock-source
domain 1
ssm-channel
sa4
tx-ssm
no tx-ssm
The figure below is a diagram of the ETX-5300A timing mechanism.
9-2
Clock Selection
ETX-5300A Ver. 1.0
Main Card
System
Clock
10GbE
Ports
I/O
Clock 1
I/O
Clock 2
1588v2
(master)
T0
Mux
SEC
1588v2
(slave)
Station Clock
(BITS/GPS)
Station Clock
Output (T4)
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
Clock Domain
The timing system in ETX-5300A 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/GPS10 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:
ETX-5300A Ver. 1.0
Option I (Europe)
Option II (USA), default.
Clock Selection
9-3
Clock Quality Levels

You can define the timing quality level of the source (which can be fixed or SSMbased) 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

G.811
Highest
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

Quality Level
Description
Rank
PRS
Timing source is Primary Reference Source clock, as defined in

Recommendation G.811
Highest
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
9-4
Clock Selection
Lowest
ETX-5300A Ver. 1.0
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-5300A 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:
Note
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.
QL in free-run mode is SEC/ST3.

By default, ETX-5300A 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:
Note
ETX-5300A Ver. 1.0
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.
By default, the ETX-5300A system clock is in free-run state, until a valid clock
source is selected.
Clock Selection
9-5
Station clock output:
Note
Locked Locked to a valid clock input
Unlocked Not locked to a valid clock input.
By default, ETX-5300A 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)
System
Clock
SEC
T0
Source Clock 1
Source Clock 2
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:
9-6
Clock Selection
ETX-5300A Ver. 1.0
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:

ETX-5300A Ver. 1.0
Clock Selection
9-7
Note
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.
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.
System
Clock
Bus
Main Card
Source Clock 1
SEC
Source Clock 2
T0
System
Clock
I/O Card 1
I/O Card 2
I/O Card 3
Source Clock 3
T4
Source Clock 4
I/O Card4
Main card Ethernet ports
Station
Clock
Output
1588v2 master entity
Figure 9-3. SEC Output
Input Sources
The four clock sources (SEC inputs) are based on:
9-8
Station clock (BITS or GPS-10 MHz)
Clock Selection
ETX-5300A Ver. 1.0
Note
IEEE 1588v2 clock.
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-5300A clock domain can be configured to use timing information derived
from an STM-1, OC-3 or GbE/10GbE port located on an I/O card or a main card.
Ethernet Ports
Ethernet ports located on E5-MC-4, E5-10GbE-2 or E5-GbE-20 support
Synchronous Ethernet (Sync-E) master and slave modes according to ITU-T
G.8261G.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.
STM-1/OC-3 Ports
The Rx clock of any STM-1/OC-3 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, clock is used from a selected interface and not from an APS
group.
The Tx clock of an STM-1/OC-3 port can be locked to:
Rx clock of the port (loopback timing).
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:
ETX-5300A Ver. 1.0
System clock
Rx clock of the port
Adaptive clock recovered from pseudowire stream.
Clock Selection
9-9
Station Clock
The station clock interface has two functions:
Input for station clock signal (BITS and GPS clocks)
Output for the ETX-5300A nodal clock. This output provides a convenient
means for distributing the ETX-5300A nodal clock signal to other equipment
(BITS clock only).
BITS Clock
ETX-5300A recovers Building-Integrated Timing Supply (BITS) clock via the station
clock interface ports on E5-MC-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 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-5300A receives/transmits (1588v2 master/slave) GPS-based frequency and
phase reference signal from GPS units, using the following interfaces on the E5MC-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-5300A 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.
9-10
Clock Selection
ETX-5300A Ver. 1.0
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
Clock
Primary
SEC
Station Clock
Mux
Secondary
From backup card
To backup card
Backup Main Card
Secondary
System
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:
ETX-5300A Ver. 1.0
Domain configuration
Timing source configuration
Station clock configuration (if needed)
Recovered clock configuration (if needed).
Clock Selection
9-11
Configuring the Clock Domain

By default, ETX-5300A 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.
Task
Command
Comments
Setting the type of

synchronization network
sync-network-type { 1 | 2 }
Type 1 Europe
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

outgoing station clock
quality min-level-station { prc | ssu-a |

ssu-b | sec | dnu }
quality min-level-station { prs | stu |
st2 | tnc | st3e | st3 | smc | st4 | dus |
prov }
Minimum clock quality definition is needed to

prevent outputting low-quality clock via external
clock interface.
no quality removes the quality parameter. If no
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-t0holdover }
auto Clock selection mechanism functions

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
frequency deviation
9-12
max-frequency-deviation <value>
Clock Selection
3816096 100 ppm

When a frequency deviation of an input clock
source exceeds defined value, this clock source is
declared invalid
ETX-5300A Ver. 1.0
Task
Command
Comments
Forcing T4 timing
generator to use the same
clock source as the T0
generator
force-t4-as-t0
no force-t4-as-t0 prevents T4 timing generator

from using the same clock source as the T0
generator
Forcing a selection of a
particular clock source
when the sources have
different quality levels
force <source-id>
Manually selecting a
particular clock source in
the following conditions:
manual <source-id>
No quality is defined
for the clock domain
The sources have the

same qualities
The sources have

different priorities.
Canceling a previously
issued force or manual
command
clear
Adding clock source (refer

to Configuring the Clock
Sources)
Configuring clock source
(refer to Configuring the
Clock Sources)
Displaying status
no source <src-id> deletes the source
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
ETX-5300A Ver. 1.0
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
Clock Selection
9-13
ETX-5300A>config>system>clock>domain(1)# show status

System Clock Source
Station Out Clock Source
Force Switch
Manual Switch
:
:
:
:
0
0
InActive
InActive
State
State
: Freerun
: Unlocked
Quality
: ST3
Configuring the Clock Sources

You can define up to four clock sources for the domain. The sources can be:
Note
Ethernet port on main card or I/O Ethernet card
SDH/SONET port on a TDM I/O card
Station clock
Recovered clock (1588v2).
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 <14> 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:
Untagged classification
Ingress port Ethernet port/LAG, serving as the SSM source (Sync-E port
Egress port according to application requirements.
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
9-14
Clock Selection
ETX-5300A Ver. 1.0
For SDH/SONET port: clock source <14> rx-port sdh-sonet <slot/port>
For station clock: clock source <14> station <main-a/1 or main-b/1>
For recovered clock: clock source <14> 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 <14> to select the source to configure.
The config>system>clock>domain(1)>source(<14>)# prompt is
displayed.
Task
Command
Comments
Setting the priority to be taken

into account during the clock
selection process
priority <num>
14
Setting quality level of the

clock source
quality-level { prc | ssu-a | ssu-b | sec |

dnu | ssm-based }
Clock source quality, as well as source priority are

taken into account during clock selection process.
quality-level { prs | stu | st2 | tnc | st3e |

st3 | smc | st4 | dus | ssm-based | prov }
If no quality is defined for the domain, this

command is not available.
Priority 1 is the highest.

no priority disables clock source priority
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
that a previously failed
synchronization source must
be fault free in order to be
considered available
wait-to-restore <seconds>
0720
Defining the amount of time

that signal failure must be
active before it is transmitted
hold-off <milliseconds>
3001800
Canceling the wait-to-restore

timer of a clock source
clear-wait-to-restore
This is useful if a timing source fault is cleared

and you want the source to be available
immediately
Displaying status
show status
show statistics
ETX-5300A Ver. 1.0
Clock Selection
9-15
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-5300A>config>system>clock>domain(1)>source(1)#
ETX-5300A>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.
9-16
Clock Selection
ETX-5300A Ver. 1.0
The ESMC statistics are displayed.

ETX-5300A>config>system>clock>domain(1)>source(1)#
ETX-5300A>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
ETX-5300A Ver. 1.0
Clock Selection
9-17
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-5300A system clock can also use a signal received from a station
(external) source as reference.
The station clock interface has two functions:
oNote
Input for external clock signal
Output for the ETX-5300A clock. This output provides a convenient means for
distributing the ETX-5300A clock signal to other equipment or loop it back.
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.
9-18
Clock Selection
ETX-5300A Ver. 1.0

Task
Command
Comments
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

and 2-MHz interfaces
impedance {balanced | unbalanced}
Setting line type for E1, T1

or 64 kHz interfaces
line-type {g732n | g732n-crc}

line-type {sf | esf}
line-type {8khz | 8khz-400hz}
Assigning a name to a
station clock source
name <string>
no name removes the station

clock source name
Setting receiver sensitivity

for E1 and 2-MHz
interfaces.
rx-sensitivity {short-haul | long-haul}
Used to adjust the signals

capability to reach destinations
close by or farther away
Defining transmit (output)

clock type
tx-clock-source {station-rclk | domain <domain-number>}
The output station clock can be

locked to station Rx clock
(loopback) or to domain (T4) clock
Defining E1 G.732NCRC
bits to carry SSM
information
ssm-channel {sa4 | sa5 | sa6 | sa7 | sa8}
For T1 ESF interface, SSM

information is carried over FD.
Enabling SSM transmission

for E1 G.732NCRC and T1
ESF interfaces
tx-ssm
Enabling SSM transmission allows

using station clock as a SSM
based input clock for domain.
no tx-ssm disables SSM
transmission
station clock
no shutdown
Displaying station clock

status
show status
shutdown disables the station

clock
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.
ETX-5300A Ver. 1.0
Clock Selection
9-19
The config>system>clock>station(main-a/1 or main-b/1)# prompt is

displayed.
The station clock status is displayed.
ETX-5300A>config>system>clock>station(main-a/1)# show status
Name
: Station Clk-5-1
: Down
Operational Status
: Down
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-5300A# configure system clock station main-a/1

ETX-5300A>config>system>clock>station(main-a/1)# shutdown
ETX-5300A>config>system>clock>station(main-a/1)# interface-type e1
ETX-5300A>config>system>clock>station(main-a/1)# line-type g732n-crc
ETX-5300A>config>system>clock>station(main-a/1)# name E1_Station_Clock_1
ETX-5300A>config>system>clock>station(main-a/1)# tx-clock-source domain 1
ETX-5300A>config>system>clock>station(main-a/1)# tx-ssm
ETX-5300A>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.
9-20
Clock Selection
ETX-5300A Ver. 1.0
Main Card A
Input 1
SEC
Station Clock
Input 2
Y-Cable
Main Card B
Clock Source
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-5300A# configure port sdh-sonet 1/1
ETX-5300A>config>port>sdh-sonet(1/1)# no shutdown
ETX-5300A>config>port>sdh-sonet(1/1)# exit all
#*********************************END****************************************
#*************************Configuring_Station_Clock**************************
ETX-5300A# configure system clock station main-a/1
ETX-5300A>config>system>clock>station(main-a/1)# shutdown
ETX-5300A>config>system>clock>station(main-a/1)# interface-type e1
ETX-5300A Ver. 1.0
Clock Selection
9-21
ETX-5300A>config>system>clock>station(main-a/1)# no shutdown
ETX-5300A>config>system>clock>station(main-a/1)# show status
Name
: Station Clk-5-1
: Up
Operational Status
: Up
Detailed Status
:
Received SSM
: PRC
#*********************************END****************************************
#*************************Configuring_Clock_Domain***************************
ETX-5300A# configure system clock domain 1
ETX-5300A>config>system>clock>domain(1)# sync-network-type 1
#*********************************END****************************************
#**********************Configuring_Station_Clock_as_Source_1*****************
ETX-5300A>config>system>clock>domain(1)# source 1 station main-a/1
ETX-5300A>config>system>clock>domain(1)>source(1)$ wait-to-restore 10
ETX-5300A>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-5300A>config>system>clock>domain(1)>source(1)$ clear-wait-to-restore
Status
Tx Quality
Rx Quality
ESMC State
WTR State
:
:
:
:
:
OK
DNU
PRC
Unlocked
Inactive
ETX-5300A>config>system>clock>domain(1)>source(1)$ exit
System Clock Source
: 1
State
: Locked
Quality
: PRC
Station Out Clock Source : 0

InActive
State
: Unlocked
Force Switch:
Manual Switch
: InActive
#*********************************END****************************************
#**********************Configuring_SDH_SONET_Port_as_Source_2****************
ETX-5300A>config>system>clock>domain(1)# source 2 rx-port sdh-sonet 1/1
ETX-5300A>config>system>clock>domain(1)>source(2)$ quality-level ssu-a
ETX-5300A>config>system>clock>domain(1)>source(2)$ wait-to-restore 10
Status
: OK
Tx Quality : PRC
9-22
Clock Selection
ETX-5300A Ver. 1.0
Rx Quality : SSU-A
WTR State : Inactive
System Clock Source
: 1
State
: Locked
Quality
: PRC
Station Out Clock Source : 2

InActive
State
: Locked
Force Switch:
Manual Switch
: InActive
#*********************************END****************************************
is 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 (3001800)
Invalid Priority
Clock priority number is out of allowed range (14)
Invalid Source ID
Selected source ID is invalid
Invalid Source Number
Clock source number is not within range (14)
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 (0720)
Source is not Configured
Selected clock source has not yet been configured
Interface is in conflict with domain

network type
Interface and domain do not have the same network type
9.2
1588v2 Timing
ETX-5300A 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-5300A Ver. 1.0
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
maximum-slaves
256
mode
time-frequency
sync-rate
64pps
tx-clock
domain 1
Slave Parameter
Default Value
ip-address
ptp-domain
BMCA
revertive
wait-to-restore
300
recovery-mode
time-frequency
priority
network-type
Automatic
peer
sync
rate 128pps
grant-period 300
announce
rate 2sec
grant-period 300
delay-respond
rate 128pps
grant-period 300
9-24
1588v2 Timing
ETX-5300A Ver. 1.0
Slave Parameter
Default Value
quality-level
type2SsmBased
When implementing the 1588v2 PTP, ETX-5300A 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-5300A 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-5300A 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-5300A supports one or two redundant 1588v2 master entities (one per main
card) with a total of up to:
Note
512 slaves at 64 PPS rate
256 slaves at 128 PPS rate.
Currently, ETX-5300A supports up to 128 slaves per main card.

ETX-5300A 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-5300A 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.
ETX-5300A Ver. 1.0
1588v2 Timing
9-25
Main Card A
Loopback RIF
1588v2
Slave
ETH
1588v2
Master
I/O Card
RIF
Router RIF
ETH
1588v2
Slave
RIF
ETH
1588v2
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):
9-26
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.
1588v2 Timing
ETX-5300A Ver. 1.0
Active Main Card

Time of Day
Phase
1588v2
Master
Frequency
RS-422
Mini
BNC
Clock
Inputs
SEC
ToD
and
1PPS
1PPS
10 MHz
Backup Main Card
1588v2
Master
Frequency
Clock
Inputs
SEC
GPS
Source
ToD
and
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-5300A 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-5300A supports two 1588v2 protection topologies, illustrated in Figure 9-8
and Figure 9-9:
ETX-5300A Ver. 1.0
Redundant main cards 1588v2 slave operates opposite a single ETX-5300A

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-5300As with a

single 1588v2 master entity each.
1588v2 Timing
9-27
ETX-5300A
Main Card A
1588v2
Master
1588v2
Slave
Main Card B
1588v2
Master
Legend:
Active
Backup
Figure 9-8. Card Redundancy

ETX-5300A
Main Card A
1588v2
Master
1588v2
Slave
ETX-5300A
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.
9-28
1588v2 Timing
ETX-5300A Ver. 1.0
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-5300A 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-5300A 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.
ETX-5300A Ver. 1.0
1588v2 Timing
9-29
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.
Task
Command
Comments
Activating the 1588v2

master entity
no shutdown
shutdown deactivates the 1588v2 master entity
Defining IP address of
1588v2 master entity
ip-address <value>
The IP address of 1588v2 master entity must be

the same as the IP address of the router loopback
interface
Creating a PTP domain
ptp-domain <423>
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
number of slaves
maximum-slaves <1512 >
The total number of slaves supported by 1588v2

master entities residing on both main cards is 512
Defining the 1588v2

message exchange mode
mode {frequency | time-frequency}
In frequency mode the master transmits sync and

announce messages to slaves
In time-frequency mode the master transmits sync,
announce and delay response messages to slaves
Defining the
synchronization message
rate
sync-rate { 16pps | 32pps | 64pps |

128pps }
All slaves within the domain must use the same

message rate
Selecting Tx clock domain
tx-clock {domain <1>}
Displaying 1588v2 master

status
show status
Displaying 1588v2 slave

status
slave <value > show status
The slave is identified by its IP address
Enable statistic collection
pm-collection
no pm-collection resets statistic counters and

stops further collection of performance monitoring
data
Clearing statistics
clear statistics
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.
9-30
1588v2 Timing
ETX-5300A Ver. 1.0
ETX-5300A>config>system>clock>master(main-a/1)# show status

Administrative Status: Up
Operational Status
: Up
Detailed Status
: OK
Slave IP Address
Oper
Clock Identity
Announce
Mode
Rate
(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
Delay Rs
Rate
(pps)
-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-5300A>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:
ETX-5300A Ver. 1.0
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
1588v2 Timing
9-31
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-5300A>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-5300A>config>system>clock>master(main-a/1)>slave(1.1.1.1)#show statistics
running
Running
-----------------------------------------------------------------------------Tx Sync Packets
: 1
: 1
: 1
TX Announce Packets
: 1
: 1
: 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
9-32
1588v2 Timing
ETX-5300A Ver. 1.0
Counter
Description
Number of Follow-up packets transmitted by 1588v2 master
Number of Delay Response packets transmitted by 1588v2 master or

slave
TX Announce Packets
Number of Announce packets transmitted by 1588v2 master or slave
Number of Signaling packets transmitted by 1588v2 master or slave
Rx Packets
Number of all packets received by 1588v2 master
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
is 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

address
The defined IP address must be the router loopback interface

address
Maximum number of slaves per shelf

must be less than 512
The maximum number of allowed 1588v2 slaves per chassis has

been exceeded
Maximum slave is out of range
The number of 1588v2 slaves is not within range (1512 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 (423)
Sync rate is out of range
The synchronization message rate value is not within range
Configuring 1588v2 Slave Clock Configuration

Configuration of the ETX-5300A 1588v2 entity to slave mode requires:
ETX-5300A Ver. 1.0
Defining 1588v2 slave entity
Configuring a peer 1588v2 master entity for the slave.
1588v2 Timing
9-33
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.
Task
Command
Comments
Activating 1588v2 slave

entity
no shutdown
shutdown deactivates 1588v2 slave entity
Defining IP address of
1588v2 slave entity
ip-address <value>
The IP address of the 1588v2 slave entity must be

the same as the IP address of the router loopback
interface
Creating a PTP domain
ptp-domain <423>
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

Master Clock Algorithm)
mode
revertive
nonRevertive
Revertive mode if a higher priority master

becomes available, the 1588v2 slave uses it as its
active master
Non-revertive if a higher priority master becomes
available, the 1588v2 slave remains with its current
active master
Defining amount of time

that previously failed clock
must be fault free in order
to be considered available
9-34
wait-to-restore <0720>
1588v2 Timing
ETX-5300A Ver. 1.0
Task
Command
Comments
Defining the 1588v2 mode
recovery-mode {frequency | timefrequency}
frequency the 1588v2 slave entity reconstructs

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

status
show status
Clearing statistics
clear statistics
Displaying 1588v2 slave status
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.
Task
Command
Comments
Activating peer 1588v2

master
no shutdown
shutdown deactivates peer 1588v2 master
Defining peer master

source port ID
master-identity {clock-id<value> port

<value>}
Default clock ID value (0xFFFFFFFFFFFFFFFFFFFF)

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.
ETX-5300A Ver. 1.0
1588v2 Timing
9-35
Task
Command
Comments
Defining peer master

priority
priority { 1 | 2}
When a 1588v2 slave operates opposite two

1588v2 masters with the same quality level, it
selects a clock source with the highest priority
(priority 1)
Specifying the peer device

that transmits the clock
signal
peer <peer-number>
Defining synchronization
message rate requested by
the slave and duration of
sync message transmission
sync {rate [16pps |32pps | 64pps |

128pps] [grant-period <601000>}
All slaves within a domain must use the same sync

message rate parameters
Defining Announce
Announce message
transmission
announce {rate [16sec |8sec |4sec

|2sec |1sec | 500msec | 250msec |
125msec] [grant-period <601000>}
All slaves within a domain must use the same

Announce message rate parameters
Defining Delay Response

Delay Response message
transmission
delay-respond {rate [16pps |32pps |

64pps | 128pps] [grant-period <60
1000>}
All slaves within a domain must use the same Delay

Response message rate parameters
Setting quality level
quality-level { prc | ssu-a | ssu-b |

type1-sec | type1-dnu |
type1-ssm-based }
The quality level values are according to the

network type
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.
9-36
1588v2 Timing
ETX-5300A Ver. 1.0
ETX-5300A>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
IP
PTSF
Clock Identity
Received QL
Granted Sync Rate (pps)
Granted Sync Period (sec)
Granted Announce Rate (pps)
Granted Announce Period (sec)
Granted Delay Respond Rate (pps)
Granted Delay Respond Period (sec)
:
:
:
:
:
:
:
:
:
:
:
1
30.30.30.30
ACT
Type-1 DNU
64
0
2
0
64
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-5300A Ver. 1.0
1588v2 Timing
9-37
ETX-5300A>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
Rx
Rx
Rx
Delay Respond Elapsed Time

Sync Packets
Sync Lost
Delay Respond Packets
:
:
:
:
0
9595
0
9467
Figure 9-10. 1588v2 Slave Running Statistics

ETX-5300A>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
9-38
1588v2 Timing
ETX-5300A Ver. 1.0
Counter
Description
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

Time
Total time in seconds during which delay respond messages were not
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.
ETX-5300A Ver. 1.0
1588v2 Timing
9-39

Message
Description
All Masters within slave module must be

deleted
A 1588v2 slave cannot be disabled while it still has peer 1588v2

masters attached to it
Configuration fail. Grant-period out of

range
The grant period value is not within range (601000 sec)
Configuration fail. The minimumexpected value cannot be higher than

the rate value
The selected minimum expected value for Synchronization,

Announce or Delay Response messages is higher than the
configured message rate
Invalid IP Address
The defined IP address is not valid
IP must be configured as a router LB

address
The defined IP address is different from the router loopback

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 (423)
Recovered must be defined as none
The PTP WTR value is not within range (0720)
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

must be equal or lower that the sync
rate
A 1588v2 slave cannot be modified while it is active
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.
9-40
1588v2 Timing
ETX-5300A Ver. 1.0
Task
Command
Comments
Activating ToD clock
no shutdown
shutdown deactivates the ToD clock
Defining ToD clock baud

rate
baudrate {2400bps | 4800bps |

9600bps | 14400bps | 19200bps |
38400bps | 57600bps | 115200bps}
Assigning name to ToD

clock
name <tod_name >
no name removes the ToD clock name
Defining input interface for

1PPS phase stream
interface-type {rj-45 | mini-bnc}
rj-45 1PPS is supplied via RJ-45 TOD connector
Displaying ToD status
show status
mini-bnc 1PPS is supplied via mini BNC 1PPS

connector
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 tody-cable to disable the ToD Y-cable redundancy.

detected.

Message
Description
TOD Y-cable must be disabled before

changing TOD
ToD clock cannot be modified, when Y-cable redundancy is

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

have the same parameters
To enable ToD Y-cable redundancy, configure both ToD clock to

the same parameters
Both PTP 1588 must be the same: slave

or master
To use ToD Y-cable redundancy,1588v2 entities residing on two

main cards must be the same type: both master or both slave
Example
This example illustrates configuration of 1588v2 slave and master entities.
ETX-5300A Ver. 1.0
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

1588v2 Timing
9-41
ETX-5300A
Port 1
Port 2
1588v2
Slave
Entity
Peer Master
Clock Source
LB
RIF 1
15.15.15.15/32
PSN
15.15.15.15
Port 3
Router
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
9-42
1588v2 Timing
ETX-5300A Ver. 1.0
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****************************************
ETX-5300A Ver. 1.0
1588v2 Timing
9-43
9-44
1588v2 Timing
ETX-5300A Ver. 1.0
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-5300A 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.
Task
Command
Comments
Assigning device name
name <device-name>
The length of the device name is unlimited, but if

you enter a name containing 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-5300A# config sys name ETX-5300A12345
results in this prompt that shows the first
20 characters, followed by 0:
ETXETXETXETXETX-5300A0#
no name removes user-assigned device name
Specifying location
location
<device-location>
no location removes user-assigned location
Specifying contact person
contact <contact-person>
no contact removes user-assigned contact

information
Displaying device
information, MAC
address, and amount of
time device has been
running
ETX-5300A Ver. 1.0
Administrative Information
10-1
Chapter 10 Administration
To configure device information:
Device name ETX-5300A-HQ
Location floor-8
Contact Engineer-1.
ETX-5300A# configure system

ETX-5300A>config>system# name
ETX-5300A-HAC >config>system#
Description
Name
Location
Contact
MAC Address
Engine Time
:
:
:
:
:
:
ETX-5300A-HQ
location floor-8
contact Engineer-1
ETH NTU: Boot; 1.10, Hw: 0.0, Main Sw: 3.0, Back-up Sw: 3.0
ETX-5300A-HQ
floor-8
Engineer-1
00-20-D2-30-CC-9D
000:00:04:10
10.2 Date and Time

You can set the date and time for the ETX-5300A internal real-time clock or use
the NTP server clock signal as a time/date reference. ETX-5300A 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-5300A sends NTP requests to the preferred server. If there is no preferred
server or if the preferred server does not answer, then ETX-5300A 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.
10-2
Date and Time
ETX-5300A Ver. 1.0
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-5300A) sets its
system date and time by retrieving this information from an SNTP server. The
information 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
Reference
Time Source
est
ETX-5300A
Resp
PSN
onse
est
Requ
Request
Response
se
spon
Re
SNTP
Server
ETX-5300A
Figure 10-1. 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.
ETX-5300A Ver. 1.0
Date and Time
10-3

Task
Command
Comments
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 Coordinated Universal Time
(UTC)
zone utc [<[{+|-}]hh[:mm]>]
Allowed range of values:

-12:00 to +12:00, in 30-minute increments
Defining the time
time <hh:mm[:ss]>
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 = UTC4 hours and 30 minutes.
ETX-5300A#configure system date-and-time

ETX-5300A>config>system>date-time# date-format mm-dd-yyyy
ETX-5300A>config>system>date-time# date 05-17-2011
ETX-5300A>config>system>date-time# time 17:40
ETX-5300A>config>system>date-time# zone utc -04:30
ETX-5300A>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.
Task
Command
Comments
Enabling ETX-5300A to listen to

NTP broadcast messages to
obtain accurate timestamps
broadcast
no broadcast disables
broadcast mode.
10-4
Date and Time
ETX-5300A Ver. 1.0
Task
Command
Comments
Setting the polling interval (in

minutes) for SNTP requests
poll-interval interval <minutes>
Allowed range is 11440
Defining and configuring SNTP

servers (refer to Defining SNTP
Servers and Configuring SNTP
Server Parameters)
server <server-id>
Displaying SNTP status
show status
Defining SNTP Servers
To define an SNTP server:

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>)#.
Task
Command
Setting the IP address of the

server
address <IP-address>
Setting SNTP server as the

preferred server
prefer
Setting UDP port for NTP

requests, to a specific UDP port
or to default UDP port (123)
udp port <udp-port>
no shutdown
Sending query to server and

displaying result
query-server
ETX-5300A Ver. 1.0
Comments
no prefer removes preference
Note: Only one server can be

preferred.
Allowed range is 165535
udp default
shutdown disables the server
Date and Time
10-5
Example
To define SNTP server:
Server ID = 1
IP address = 192.1.1.1
Preferred
ETX-5300A# configure system date-and-time sntp

ETX-5300A>config>system>date-time>sntp# server 1
ETX-5300A>config>system>date-time>sntp>server(1)# address 192.1.1.1
ETX-5300A>config>system>date-time>sntp>server(1)# prefer
ETX-5300A>config>system>date-time>sntp>server(1)# no shutdown
ETX-5300A>config>system>date-time>sntp>server(1)# query-server
Query Server Replay
----------------------------------------------------------------------------Server : 192.1.1.1
UDP
: 123
Date
: 00-00-0000
Time : 00:00:00
Stratum : 0
ETX-5300A>config>system>date-time>sntp>server(1)# exit
ETX-5300A>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
NTP Server
Type
127.0.0.1
UDP Port Tstap Date Time
Strat Received
192.1.1.1
Prefer
123
00-00-0000 00:00:00 0
ETX-5300A>config>system>date-time>sntp#
--
10.3 Inventory
The ETX-5300A inventory table displays the units 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-5300A inventory table displays the units 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).
10-6
Inventory
ETX-5300A Ver. 1.0
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
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-1 for information on the parameters).
Table 10-1. Inventory Parameters

Parameter
Description
Description
Description of component type, in the form:

Device_name.< Physical Class>, e.g. ETX-5300A.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.
ETX-5300A Ver. 1.0
Inventory
10-7
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-5300A# configure chassis

ETX-5300A>config>chassis# show manufacture-info slot 1
Slot
Type
Serial Number HW Ver
Main-A
Main 10GEx4
Shelf Type
Serial Number
HW Version
FW Version
Number of MACs
:
:
:
:
:
0.0
FW Ver
2.0
N/A
0.0
2.0
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.
Task
Command
Comments
Assigning user-defined alias to

component
alias <string>
no alias removes the alias.
Assigning user-specific asset identifier

to the component (usually for
removable physical components)
asset-id <id>
no asset-id removes the asset

ID
Assigning vendor-specific serial

number to the component
serial-number <string>
no serial-number removes the

serial number
10-8
Inventory
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.
ETX-5300A Ver. 1.0
Example
To display the following inventory information:
Inventory table
Inventory information for the ETX-5300A chassis.

ETX-5300A# config>chassis# show inventory-summary
Index Physical Class Name
HW Ver SW Ver
FW Ver
----------------------------------------------------------------------------1001 Chassis
AC-chassi
N/A
N/A
N/A
2001 Backplane
Backplane
0.0
N/A
N/A
3001 Container
1
N/A
N/A
N/A
3002 Container
2
N/A
N/A
N/A
3003 Container
3
N/A
N/A
N/A
3004 Container
4
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
3008 Container
Slot 5 Port 2
N/A
N/A
N/A
3009 Container
Slot 5 Port 3
N/A
N/A
N/A
3010 Container
Slot 5 Port 4
N/A
N/A
N/A
3011 Container
Slot 6 Port 1
N/A
N/A
N/A
3012 Container
Slot 6 Port 2
N/A
N/A
N/A
3013 Container
Slot 6 Port 3
N/A
N/A
N/A
3014 Container
Slot 6 Port 4
N/A
N/A
N/A
3035 Container
Slot 2 Port 1
N/A
N/A
N/A
3036 Container
Slot 2 Port 2
N/A
N/A
N/A
3095 Container
AC Slot
N/A
N/A
N/A
3096 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
Etherent port main-b/1
N/A
N/A
N/A
7006 Port
N/A
N/A
N/A
7007 Port
N/A
N/A
N/A
7008 Port
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
7016 Port
RS_232 Control Port
N/A
N/A
N/A
7017 Port
Clock RJ45 Port
N/A
N/A
N/A
7018 Port
Clock BNC Port
N/A
N/A
N/A
7019 Port
N/A
N/A
N/A
7020 Port
N/A
N/A
N/A
7041 Port
Ethernet Port 2/1
N/A
N/A
N/A
7042 Port
Ethernet Port 2/2
N/A
N/A
N/A
ETX-5300A Ver. 1.0
Inventory
10-9

ETX-5300A# config>chassis# inventory 1001
ETX-5300A# config>chassis>inventory(1001)# show status
Description
Contained In
Physical Class
Relative Position
Name
HW Ver
SW Ver
FW Ver
Serial Number
MFG Name
Module Name
Alias
Asset ID
FRU
:
:
:
:
:
:
:
:
:
:
:
:
:
:
ETX-5300A.AC-chassis
0
Chassis
0
AC-chassi
N/A
N/A
N/A
RAD
ETX-5300A-AC
True
10.4 Downloading/Uploading Files

You can download or upload files to the ETX-5300A 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 1100 characters
Port 165535.
The SFTP protocol is used to provide secure file transfers via the devices
Ethernet interface. SFTP is a version of FTP that encrypts commands and data
transfers, keeping your data secure and your session private. For SFTP file
transfers, an SFTP server application must be installed on the local or remote
10-10
Downloading/Uploading Files
ETX-5300A Ver. 1.0
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-5300A
Ethernet
PC with an Active
SFTP Server and
Application File
ETX-5300
Figure 10-2. Downloading a Software Application File via SFTP
Example Download via SFTP
SFTP server address 192.20.20.20
SFTP user name admin
SFTP password 1234
Source file name ETX-5300A.img
Destination file name sw-pack-1.
ETX-5300A# file
ETX-5300A>file# copy sftp://<admin>:<1234>@192.20.20.20/ETX-5300A.img swpack-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-5300A# file
ETX-5300A>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.5 Copying Files within ETX-5300A

You can copy files within the ETX-5300A unit with the copy command.
Figure 10-3 shows the commands that can copy configuration files in a visual
diagram.
ETX-5300A Ver. 1.0
Copying Files within ETX-5300A
10-11
Figure 10-3. Commands that Copy Configuration Files

File Names in the Unit

ETX-5300A uses the following reserved file names:
factory-default Contains the factory default settings
running-config Contains full configuration (default and user)
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-2.
10-12
ETX-5300A Ver. 1.0
Table 10-2. Commands That Copy Files

Command
Level
Copies
Manual Section
factory-default
admin
factory-default-config to startup-config
and resets device
Error! Reference source not

found.
Resetting to Factory Defaults

user-default
admin
user-default-config to startup-config and

resets device
Resetting to User Defaults
save
global
running-config to startup-config
Saving the Configuration
software-confirmrequired
admin
running-config or any other userspecified configuration file to rollbackconfig
Confirmation of Configuration
File in Chapter 3
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-5300A# file
ETX-5300A>file# copy running-config startup-config
To display the last copy command result:
At the file# prompt, enter: show copy.
ETX-5300A# 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-5300A>file# show copy summary
Direction
Source
Destination
End Time
1
Local
running-config
user-default-conf 13-3-2011
14:6:51
2
Local
running-config
startup-config
13-3-2011
14:7:35
3
Dev to Net startup-config
DB
13-3-2011
14:7:40
Status
Ended OK
Ended OK
Ended OK
Displaying Files within ETX-5300A

The dir command is used to display the files within the device.
ETX-5300A Ver. 1.0
10-13
To display the files:
At the file# prompt, enter dir.

A list of the file names and types is displayed.
For example:
ETX-5300A>file# dir
Codes
C - Configuration S - Software
Name
LO - Log
O - Other
Type Size(Bytes) Creation Date Status
mac-table
--
sw-pack-1
70250901
startup-config
508671
rollback-config
509453
factory-default-config C
34
running-config
--
log
LO
26598
Total Bytes : 817209344 Free Bytes
2012-01-02
09:25:01
2011-12-10
05:58:01
2012-01-01
16:08:11
2012-01-01
19:58:30
2012-01-02
09:25:01
2012-01-02
11:19:24
2011-12-27
15:48:10
Read Only
valid
File In Use
valid
valid
valid
valid
valid
Read Only
valid
File In Use
valid
Read Only
valid
: 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.
Task
Command
Displaying the list of

configuration files
show configuration-files
Displaying the factory-defaultconfig file contents
show factory-default-config
Displaying the rollback-config

file contents
show rollback-config
Displaying the startup-config

file contents
show startup-config
Displaying the contents of all

application files saved in the
system
show sw-pack
10-14
Comments
Application files contain

information on application
software running on main and
I/O cards installed in the
chassis
ETX-5300A Ver. 1.0
Task
Command
Displaying the user-defaultconfig file contents
show user-default-config
Comments
Example Displaying the List of Configuration Files

ETX-5300A>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 startupconfig
Example Displaying the Contents of startup-config File

ETX-5300A>file# show startup-config
# configuration file
exit all
configure
#
Terminal Configuration
terminal
timeout forever
exit
#
System Configuration
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-5300A>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)
Type
Name
: 70250901
Version
H/W Ver
Size
(Bytes)
-----------------------------------------------------ETX-5300A Ver. 1.0
10-15
main
eth1g
stm1ch
eth2X10g
main.bin
eth1g.bin
stm1ch.bin
eth2X10g.bin
1.00A9
1.00A9
1.00A9
1.00A9
1.1
1.1
1.1
1.1
29194087
9353713
15768873
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-5300A# file
ETX-5300A>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
10-16
At the file# prompt, enter copy running-config startup-config.
ETX-5300A Ver. 1.0
10.6 Resetting ETX-5300A

ETX-5300A supports the following types of reset:
Reset to factory defaults
Reset to user defaults
Overall reset (restart, reboot) of the device.
Resetting to Factory Defaults
To reset ETX-5300A to factory defaults:

1. At 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 User Defaults
To reset ETX-5300A to user defaults:

1. At the device prompt, enter admin.
The admin> prompt appears.
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-5300A Chassis
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] _
ETX-5300A Ver. 1.0
Resetting ETX-5300A
10-17
2. Enter yes to confirm the reset.

The chassis restarts.
Rebooting the Module

Use the following procedure to reboot a module installed in a specified slot.
Note
Resetting a module will temporarily disrupt services supported by that module.

To reboot a module:
1. Navigate to configure slot <slot>.
The config>slot<slot># prompt is displayed.
2. Enter reset.
Card will reset. Are you sure?? [yes/no]
3. Enter yes to confirm the reset.
The module restarts.
10-18
Resetting ETX-5300A
ETX-5300A Ver. 1.0
Chapter 11
Monitoring and
Diagnostics
This chapter explains fault management procedures supported by ETX-5300A. It
presents the following information:
Monitoring and Diagnostics
Handling Events
Running Diagnostic Tests
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-5300A cards and the ETX-5300A 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-5300A 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-5300A 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-5300A 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
ETX-5300A Ver. 1.0
Detecting Problems
11-1
Chapter 11 Monitoring and Diagnostics
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-5300A includes an extensive subsystem that checks the validity of the users
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
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.
11-2
Handling Events
ETX-5300A Ver. 1.0
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-5300A. 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-5300A 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-5300A generates time-stamped alarm messages.
These messages are explained below.
Internally, the ETX-5300A 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, a Web browser, 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-5300A 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-5300A 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.
ETX-5300A Ver. 1.0
Handling Events
11-3
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.
Task
Command
Comments
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

specific source, defining
alarm severity and masking
reporting methods
Note: Severity and LEDRelay apply only to alarms.
alarm-source-attribute <source-type>
Use the no form to mask
[<source-id>] alarm <alarm-list> [severity
alarms/events. The following
{critical | major | minor}] [log] [snmp-trap] [led- apply:
relay]
If a trap is masked according
to alarm/event attribute, it is
alarm-source-attribute<source-type>
not sent to any management
[<source-id>] event <alarm-list> [log]
[snmp-trap]
station, regardless of whether
it is masked in the SNMP
manager configuration
11-4
Handling Events
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.
ETX-5300A Ver. 1.0
Task
Command
Comments
Masking alarm/event from a

specific source type,
defining alarm severity and
masking reporting methods
alarm-source-type-attribute <source-type>
alarm <alarm-list> [severity {critical | major |
minor}] [log] [snmp-trap] [led-relay]
Use the no form to mask

alarms/events. The following
apply:
alarm-source-type-attribute <source-type>
If a trap is masked according

to alarm/event attribute, it is
not sent to any management
station, regardless of whether
it is masked in the SNMP
manager configuration
If a trap is unmasked
according to alarm/event
attribute, it is sent only to
management station for
which it is not masked in the
SNMP manager configuration.
Note: Severity, LED and LED- event <alarm-list> [log] [snmp-trap]

Relay apply only to alarms.
Masking alarm per severity
mask-minimum-severity [log {critical | major |

minor}] [snmp-trap {critical | major | minor}]
[led-relay {critical | major | minor}]
Masking a minimum severity

means that lower severities are
also masked
no mask-minimum-severity [log] [snmp-trap

[led-relay]
Rebuilding active alarm table active-alarm-rebuild [send-traps]
from scratch, and, optionally
resending traps for all open
alarms
To ensure that no active alarms

are lost due to a system failure,
the user can rebuild the active
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}
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
ETX-5300A Ver. 1.0
To mask alarm for a specific source type:
Source type All E1s
Alarm excessive-bpv
Reporting methods log
Handling Events
11-5
ETX-5300A>config# reporting
ETX-5300A>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-5300A>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-5300A>config>reporting# mask-minimum-severity led-relay
major
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

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

added to active alarms.
alarm-information
Detailed information about the alarm type. For example, if

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

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

default view of the alarm log (i.e., alarm history) shows
one line per raised alarm and one for cleared alarm.
11-6
Handling Events
ETX-5300A Ver. 1.0
Display Option
Meaning
Example
Number
alarm-list
[<source ID> [severity
{critical|major|minor}]]
List of all ETX-5300A alarms for a specific source ID and

severity value, or for all the alarms in the system
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

brief log is cleared at reboot.
event-information
Detailed information about event type (similar to alarminformation).
event-list
List of all ETX-5300A 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-5300A>config>reporting# show active-alarms
Total :
Critical : 2
Major : 1
1
2
3
Domain Clock
Card
FAN
1
1
1
Minor
station_clock_unlock
card_provision_failure
fan_failure
: 0
Maj
Crt
Crt
Unmasked
Unmasked
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-5300A>config>reporting# show active-alarms-details
Total :
Critical : 0
Major : 3
Minor
ETX-5300A Ver. 1.0
: 0
Handling Events
11-7
Domain station clock state changed to unlocked
2011-12-20
20:55:23.00
2
Domain Clock
1
Major
Unmasked
Provisioning failure
2011-12-22
01:52:05.00
3
Fan
2011-12-20
20:56:11.00
Card
1
Critical
Unmasked
failure
FAN
1
fan_failure
Critical
Unmasked
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 types 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-5300A>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 removal: resolved, user-initiated, alarm suppression, not applicable.
ETX-5300A>config>reporting# show alarm-log
Last Acknowledge On : 64-149-1203 00:206:27.
11-8
Handling Events
ETX-5300A Ver. 1.0
Loss of signal (LOS)
2011-12-18
Ethernet
02:17:00.00
main-a/0
los
Cleared
Suppression
2011-12-18
Ethernet
02:16:58.00
main-a/0
los
Major
Example 5. Alarm List

This command displays the list of all ETX-5300A 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-5300A>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.
ETX-5300A Ver. 1.0
Handling Events
11-9
Example 7. Displaying Brief Log

This command displays a brief log of active and cleared alarms and events.
ETX-5300A>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
Severity
Last Raised
System
sw_install_end
Event
alternate_configuration_loaded
Event
2011-12-22
02:50:14.00
2011-12-22
02:51:05.00
System
Last Cleared
-----
Total Times
Since Ack
1
1
1
1
Clearing Alarms
To clear a log:
At the config>reporting# prompt, enter clear followed by log, brief-log or alllogs to clear the full log, brief log or all alarm/event logs in ETX-5300A.
The log is cleared.
Alarm List
Table 11-1 lists and explains the alarm messages generated by the ETX-5300A.
The alarm messages are listed alphabetically in order of the following:
Source type: system, card, port/entity
Alarm name (inside each source)
For each alarm, Table 11-1 also specifies the alarm description, the
corresponding trap, and the alarm ID (unique number that identifies the alarm).
Alarm names are not case-sensitive.
For an alphabetical list of traps, see Table 11-3.
Table 11-1. Alarms List

Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
alarm-input
alarm_relay_input
Alarm input
alarmInput
20401
card
hardware_failure
Card hardware failure
cardHwFailure
40001
card
card_mismatch
Card is not supported or

misconfigured
cardMismatch
40002
card
card_provision
failure
Provisioning failure
cardProvisionFailure
40003
card
card_improper
removal
Improper card removal
cardImproperRemoval
40006
11-10
Handling Events
ETX-5300A Ver. 1.0
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
card
card_temperature
ora
Card temperature is out of

range
cardTemperatureOra
40007
card
card_no_response
Loss of communication with

card
cardNoResponse
40008
card
card_initialization_
failure
Card software download has

failed
cardInitFailure
40009
clock-domain
system_clock_
unlock
Domain system clock state

changed to freerun, holdover or
locked
clockDomainStation
ClockUnlock
30301
clock-domain
domain_clock_ql_
low
Domain clock quality level is

below minimum
clockDomainQlLow
30302
clock-domain
station_clock_
unlock
Domain station clock state has

changed to unlocked
clockDomainStation
ClockUnlock
30303
e1t1
ais
Alarm indication signal (AIS)
e1t1Ais
110105
e1t1
lof
Loss of frame (LOF)
e1t1Lof
110106
e1t1
rai
Remote alarm indication (RAI)
e1t1Rai
110107
erp
erp_state_protected
ERP ring state changed to

protected
erpStateProtected
290301
eth
sfp_no_response
Loss of communication with SFP
sfpNoResponse
50001
eth
sfp_mismatch
SFP mismatch
sfpMismatch
50002
eth
los
ethLos
50003
eth
sfp_removed
SFP not installed
sfpRemoved
50004
eth
sfp_temperature_
ora
Laser temperature is out of

range
sfpTemperatureOra
50005
eth
sfp_opr_ora
Optical power received (OPR) is

out of range
sfpOprOra
50006
eth
auto_negotiation_
failure
Autonegotiation with remote

device failed
ethAutoNegotiation
Failure
50008
fan
fan_failure
Fan failure
fanFailure
20101
lag
lacp_down
Ethernet port active but LACP

out-of-sync
lagLacpDown
250001
lag
lacp_loop_detection
LACP detected loop between

LAG ports
lagLacpLoopDetection
250002
lag
lacp_churn
LACP is unable to synchronize

with partner
lagLacpChurn
250003
oam-cfmmep
ais
Alarm Indication Signal (AIS)
oamCfmMepAis
270201
oam-cfmmep
lck
Lock Signal (LCK)
oamCfmMepLck
270202
ETX-5300A Ver. 1.0
Handling Events
11-11
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
oam-cfmmep
mismatch
Mismatch due to mismerge,

unexpected MEP, unexpected
MEG level, unexpected period
oamCfmMepMismatch
270203
oam-cfmmep
loc
Loss of Continuity (LOC)
oamCfmRmepLoc
270601
oam-cfmmep
rdi
Remote Defect Indication (RDI)
oamCfmRmepRdi
270602
path
ais-path
pathAis
100201
path
lomf-path
Loss of Multiframe (LOMF)
pathLomf
100202
path
uneq-path
Unequipped payload
pathUneq
100203
path
tim-path
Path Trace ID mismatch (TIM)
pathTim
100204
path
plm-path
Payload Label Mismatch (PLM)
pathPlm
100205
path
lop-path
Loss of Pointer (LOP)
pathLop
100206
path
sd-path
BER above signal degradation

threshold
pathSd
100207
path
eed-path
BER above excessive error

threshold
pathEed
100208
path
rfi-path
Remote Failure Indication (RFI)
pathRfi
100209
power-supply
power_delivery_
failure
Power supply failure
powerDeliveryFailure
20201
power-supply
power_in_ora
Input power out-of-range
powerInOra
20202
power-supply
power_in_low
Input power near minimum
powerInLow
20203
ptp-master
unavailable_tod
Unavailable Time of Day (ToD)
ptpMasterUnavailable
Tod
30601
ptp-master
unavailable_1pps
Unavailable 1PPS
ptpMasterUnavailable
1pps
30602
ptp-master
slaves_limit_reached
Slaves limit reached
ptpMasterSlavesLimit
Reached
30603
ptprecovered
no_ptp_master
No PTP master can be reached
ptpRecoveredNoPtpM
aster
30201
ptprecovered
invalid_frequency_
accuracy
Unacceptable frequency
accuracy
ptpRecoveredInvalid
FreqAccuracy
30202
ptprecovered
invalid_time_
accuracy
Unacceptable time accuracy
ptpRecoveredInvalid
TimeAccuracy
30203
ptprecovered
disqualified_master
Master disqualification
ptpRecoveredDisquali
fiedMaster
30204
ptprecoveredmaster
sync_failure
Rx sync messages timeout

expiration
ptpRecoveredMaster
SyncFail
30401
11-12
Handling Events
ETX-5300A Ver. 1.0
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
ptprecoveredmaster
announce_failure
Rx announce messages timeout

expiration
ptpRecoveredMaster
AnnounceFail
30402
ptprecoveredmaster
delay_response_
failure
Rx delay response messages

timeout expiration
ptpRecoveredMaster
DelayRespFail
30403
pw
configuration
mismatch
Configuration mismatch
pwConfigMismatch
310001
pw
pw_oam_failure
PW OAM disconnected
pwOamFailure
310002
pw
rdi
Remote defect indication (RDI)
pwRdi
310003
pw
rx_failure
Ethernet frames not received by

PW
pwRxFailure
310004
pw
rx_failure_fe
Ethernet frames not received by

PW at far end
pwFeRxFailure
310008
pw
rdi_fe
Remote defect indication (RDI)

at the far end
pwFeRdi
310009
routerinterface
dhcp_client_no_
lease
DHCP lease not obtained
routerIfDhcpClientNo
Lease
300101
sdh-sonet
sfp_no_response
Loss of communication with SFP
sfpNoResponse
100001
sdh-sonet
sfp_mismatch
SFP mismatch
sfpMismatch
100002
sdh-sonet
lof
Loss of frame (LOF)
sdhSonetLof
100003
sdh-sonet
rfi-line
Remote failure indication (RFI)
sdhSonetRfi
100004
sdh-sonet
los
sdhSonetLos
100005
sdh-sonet
sfp_removed
SFP is not installed
sfpRemoved
100006
sdh-sonet
sfp_temperature_
ora
Laser temperature is out of

range
sfpTemperatureOra
100007
sdh-sonet
sfp_opr_ora
Optical power received (OPR) is

out of range
sfpOprOra
100008
sdh-sonet
ais-line
sdhSonetAis
100009
sdh-sonet
tim
Section trace ID mismatch (TIM)
sdhSonetTim
100010
sdh-sonet
sd-line

threshold
sdhSonetSd
100011
sdh-sonet
eed-line

threshold
sdhSonetEed
100012
station-clock
ais
stationClockAis
30102
station-clock
lof
Loss of Frame (LOF)
stationClockLof
30103
station-clock
los
Loss of Signal (LOS)
stationClockLos
30104
ETX-5300A Ver. 1.0
Handling Events
11-13
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
system
device_temperature
_ora
Device temperature is out of

range
systemDevice
TemperatureOra
20002
system
hardware_failure
Hardware failure
systemHardware
Failure
20005
system
sw_pack_corrupted
Application software file is

corrupted
systemSwPack
Corrupted
20008
vc-vt
ais-vcvt
vcVtAis
100101
vc-vt
uneq-vcvt
Unequipped payload
vcVtUneq
100103
vc-vt
tim-vcvt
Path trace ID mismatch (TIM)
vcVtTim
100104
vc-vt
plm-vcvt
Payload label mismatch (PLM)
vcVtPlm
100105
vc-vt
lop-vcvt
Loss of pointer (LOP)
vcVtLop
100106
vc-vt
sd-vcvt

threshold
vcVtSd
100107
vc-vt
eed-vcvt

threshold
vcVtEed
100108
vc-vt
rfi-vcvt
Remote failure indication (RFI)
vcVtRfi
100109
Event List
Table 11-2 lists the event messages generated by the ETX-5300A and explains
their interpretation. The event messages are listed alphabetically in order of the
following:
Source type: system, card, port/entity
Alarm name (inside each source)
For each alarm, Table 11-2 also specifies the alarm description, the
corresponding trap and the event ID (unique number that identifies the event
type). Event names are not case-sensitive.
For an alphabetical list of traps, see Table 11-3.
Table 11-2. Event List

Source
Type
Event Name
Event Description
Trap Name
Event ID
card
card_reset
Card reset
cardReset
1040001
card
card_switchover
Card switchover
cardSwitchover
1040002
card
card_plugged_in
Card plugged in
cardPluggedIn
1040004
card
card_plugged_out
Card removed from slot
cardPluggedOut
1040005
clockdomain
system_source_
clock_change
Domain system source clock changed
clockDomainSystem
SrcClockChange
1030301
11-14
Handling Events
ETX-5300A Ver. 1.0
Source
Type
Event Name
Event Description
Trap Name
Event ID
clockdomain
station_source_
clock_change
Domain station source clock changed
clockDomainStation
SrcClockChange
1030302
e1t1
loopback
Loopback started
e1t1Loopback
1110104
e1t1
loopback_off
Loopback ended
e1t1LoopbackOff
1110105
e1t1
es_line_tca
Errored Seconds (ES) threshold

crossing alert
e1t1EsLineTca
1110106
e1t1
cv_path_tca
Coding Violation (CV) threshold

crossing alert
e1t1CvPathTca
1110107
e1t1
es_path_tca
Errored seconds (ES) threshold

crossing alert
e1t1EsPathTca
1110108
e1t1
ses_path_tca
Severely Errored Seconds (SES)

threshold crossing alert
e1t1SesPathTca
1110109
e1t1
sefs_path_tca
Severely Errored Framing Seconds

(SEFS) threshold crossing alert
e1t1SefsPathTca
1110110
e1t1
css_path_tca
Controlled Slip Seconds (CSS)

e1t1CssPathTca
1110111
e1t1
uas_path_tca
Unavailable Seconds (UAS) threshold

crossing alert
e1t1UasPathTca
1110112
erp-port
erp_port_state_
change
ERP port state changed
erpPortState
Change
1291101
eth
sfp_opt_ora
Optical power transmitted (OPT) out

of range
sfpOptOra
1050001
eth
sfp_opt_ora_off
Optical power transmitted (OPT) in

permitted range
sfpOptOraOff
1050002
eth
sfp_lbc_ora
Laser bias current (LBC) out of range
sfpLbcOra
1050003
eth
sfp_lbc_ora_off
Laser bias current (LBC) in permitted

range
sfpLbcOraOff
1050004
lag
sub_group_
switchover
Switchover between sub-groups of

inter-card LAG
lagSubGroup
Switchover
1250001
lag
lag_failure
All LAG member ports are down
lagFailure
1250002
oam-cfmdest-ne
delay_tca
Delay threshold crossing alert
oamCfmDestNe
DelayTca
1270401
oam-cfmdest-ne
delay_tca_off
Delay in permitted range
oamCfmDestNe
DelayTcaOff
1270402
oam-cfmdest-ne
delay_var_tca
Delay variance threshold crossing

alert
oamCfmDestNe
DelayVarTca
1270403
oam-cfmdest-ne
delay_var_tca_off
Delay variance in permitted range
oamCfmDestNe
DelayVarTcaOff
1270404
ETX-5300A Ver. 1.0
Handling Events
11-15
Source
Type
Event Name
Event Description
Trap Name
Event ID
oam-cfmdest-ne
loss_ratio_tca
Loss ratio threshold crossing alert
oamCfmDestNe
LossRatioTca
1270405
oam-cfmdest-ne
loss_ratio_tca_off
Loss ratio in permitted range
oamCfmDestNe
LossRatioTcaOff
1270406
oam-cfmdest-ne
loss_ratio_tca_fe
Loss ratio threshold crossing alert at

far-end
oamCfmDestNe
LossRatioTcaFe
1270407
oam-cfmdest-ne
loss_ratio_tca_fe_
off
Loss ratio in permitted range at

far-end
oamCfmDestNe
LossRatioTcaFeOff
1270408
oam-cfmdest-ne
unavailable_ratio_
tca
Unavailable ratio threshold crossing

alert
oamCfmDestNe
UnavailRatioTca
1270409
oam-cfmdest-ne
unavailable_ratio_
tca_off
Unavailable ratio in permitted range
oamCfmDestNe
UnavailRatioTcaOff
1270410
oam-cfmdest-ne
unavailable_ratio_
tca_fe
Unavailable ratio threshold crossing

alert at far-end
oamCfmDestNeUna
vailRatioTcaFe
1270411
oam-cfmdest-ne
unavailable_ratio_
tca_fe_off
Unavailable ratio in permitted range

at far-end
oamCfmDestNeUna
vailRatioTcaFeOff
1270412
path
es_path_tca

crossing alert
pathEsTca
1100201
path
ses_path_tca
Severely errored seconds (SES)

pathSesTca
1100202
path
cv_path_tca
Coding violation (CV) threshold

crossing alert
pathCvTca
1100203
path
uas_path_tca

crossing alert
pathUasTca
1100204
path
es_path_tca_fe

crossing alert at far end
pathFeEsTca
1100205
path
ses_path_tca_fe

threshold crossing alert at far end
pathFeSesTca
1100206
path
cv_path_tca_fe

pathFeCvTca
1100207
path
uas_path_tca_fe

pathFeUasTca
1100208
ptpmaster
granted_service_
aborted
Granted service aborted
ptpMasterGranted
ServiceAborted
1030601
ptpmaster
slave_request_
denied
Slave request denied
ptpMasterSlave
RequestDenied
1030602
ptprecovered
ptp_state_change
PTP state changed to freerun/

holdover/acquiring/locked
ptpRecoveredPtp
StateChange
1030201
11-16
Handling Events
ETX-5300A Ver. 1.0
Source
Type
Event Name
Event Description
Trap Name
Event ID
ptprecovered
severe_frequency_
condition
Network conditions might cause

frequency recovery degradation
ptpRecovered
SevereFreq
Condition
1030202
ptprecovered
severe_time_
condition
Network conditions might cause time

recovery degradation
ptpRecovered
SevereTime
Condition
1030203
ptprecovered
master_switchover
Switchover to master (ID)
ptpRecovered
MasterSwitchover
1030204
ptprecovered
-master
unicast_
negotiation_failure
Unicast negotiation failure
ptpRecovered
MasterUnicastNeg
Fail
1030401
pw
pw_switchover
PW switchover
pwSwitchover
1310001
pw
jitter_buffer_
overflow
Jitter buffer overflow
pwJitterBuffer
Overflow
1310002
pw
jitter_buffer_
underflow
Jitter buffer underflow
pwJitterBuffer
Underflow
1310003
sdh-sonet
sfp_opt_ora
Optical power transmitted (OPT) out

of range
sfpOptOra
1100001
sdh-sonet
sfp_opt_ora_off
Optical power transmitted (OPT) in

permitted range
sfpOptOraOff
1100017
sdh-sonet
sfp_lbc_ora
Laser bias current (LBC) out of range
sfpLbcOra
1100002
sdh-sonet
sfp_lbc_ora_off
Laser bias current (LBC) in permitted

range
sfpLbcOraOff
1100018
sdh-sonet
es_section_tca

crossing alert
sdhSonetEsSecTca
1100003
sdh-sonet
ses_section_tca

sdhSonetSesSecTca
1100004
sdh-sonet
sefs_section_tca
Severely Errored Framing Seconds

(SEFS) threshold crossing alert
sdhSonetSefsSecTc
a
1100005
sdh-sonet
cv_section_tca

crossing alert
sdhSonetCvSecTca
1100006
sdh-sonet
es_line_tca

crossing alert
sdhSonetEsLineTca
1100007
sdh-sonet
ses_line_tca

sdhSonetSesLineTc
a
1100008
sdh-sonet
cv_line_tca

crossing alert
sdhSonetCvLineTca
1100009
sdh-sonet
uas_line_tca

crossing alert
sdhSonetUasLineTc
a
1100010
ETX-5300A Ver. 1.0
Handling Events
11-17
Source
Type
Event Name
Event Description
Trap Name
Event ID
sdh-sonet
es_line_tca_fe

sdhSonetFeEsLineT
ca
1100011
sdh-sonet
ses_line_tca_fe

sdhSonetFeSesLine
Tca
1100012
sdh-sonet
cv_line_tca_fe

sdhSonetFeCvLine
Tca
1100013
sdh-sonet
uas_line_tca_fe

sdhSonetFeUasLine
Tca
1100014
sdh-sonet
port_switchover
Port switchover
sdhSonetPort
Switchover
1100015
sdh-sonet
loopback
Loopback started
sdhSonetLoopback
1100019
sdh-sonet
loopback_off
Loopback ended
sdhSonetLoopback
Off
1100020
system
sw_install_start
Software file_name installation

started
systemSoftware
InstallStart
1020001
system
sw_install_end
Software file_name installation ended
systemSoftware
InstallEnd
1020002
system
download_end
file_name download
systemDownload
End
1020003
system
user_reset
Device reset by user
systemUserReset
1020004
system
alternate_
configuration_
loaded
file_name loaded as running-config
systemAlternate
ConfigLoaded
1020005
system
configuration_
migration
file_name conversion file_name after

software upgrade
System
Configuration
Migration
1020006
system
configuration_
sanity
Configuration sanity in file_name:

configuration file_name
System
ConfigurationSanity
1020007
system
trap_hard_sync_
start
Trap synchronization hard sync

process started
systemTrapHard
SyncStart
1020008
system
trap_hard_sync_
end
Trap synchronization hard sync

process ended
systemTrapHard
SyncEnd
1020009
system
configuration_
change_mask
Configuration change traps masked
System
Configuration
ChangeMask
system
configuration_
change_unmask
Configuration change traps unmasked
System
Configuration
ChangeUnmask
11-18
Handling Events
ETX-5300A Ver. 1.0
Source
Type
Event Name
Event Description
Trap Name
Event ID
system
backup_
configuration_
loaded
Device configuration loaded from

backup database
systemBackup
Configuration
Loaded
1020017
system
device_startup
Device startup
systemDevice
Startup
1020018
system
active_software_
changed
Active software changed from last

reboot
systemActive
SoftwareChanged
1020029
system
running_config_
saved
Running configuration saved to

startup configuration
systemRunning
ConfigSaved
1020030
system
successful_login
user_name login from
systemSuccessful
Login
1020022
system
failed_login
user_name failed to logon from due

to
systemFailedLogin
1020023
system
logout
user_name logout from
systemLogout
1020024
system
sw_unconfirmed
Installed software not confirmed
systemSw
Unconfirmed
system
startup_config_
unconfirmed
New startup-config not confirmed
systemStartup
ConfigUnconfirmed
1020028
vc-vt
es_vcvt_tca

crossing alert
vcVtEsTca
1100101
vc-vt
ses_vcvt_tca

vcVtSesTca
1100102
vc-vt
cv_vcvt_tca

crossing alert
vcVtCvTca
1100103
vc-vt
uas_vcvt_tca

crossing alert
vcVtUasTca
1100104
vc-vt
es_vcvt_tca_fe

vcVtFeEsTca
1100105
vc-vt
ses_vcvt_tca_fe

vcVtFeSesTca
1100106
vc-vt
cv_vcvt_tca_fe

vcVtFeCvTca
1100107
vc-vt
uas_vcvt_tca_fe

vcVtFeUasTca
1100108
Trap List
The traps are listed in the table below.
ETX-5300A Ver. 1.0
Handling Events
11-19
Table 11-3. Trap List

Associated to
Source Type
Trap
Description
Notification OID
Alarm
alarm-input
alarmInput
alarm_input
1.3.6.1.4.1.164.6.5.0.1
Alarm
card
cardHwFailure
card_hardware_failure
1.3.6.1.4.1.164.3.3.2.1.0.1
Alarm
card
cardMismatch
card_mismatch
1.3.6.1.4.1.164.3.3.2.1.0.2
Alarm
card
cardProvisionFailure
1.3.6.1.4.1.164.3.3.2.1.0.3
Alarm
card
cardImproperRemoval
card_improper_removal
1.3.6.1.4.1.164.3.3.2.1.0.6
Alarm
card
cardTemperatureOra
card_temperature_ora
1.3.6.1.4.1.164.3.3.2.1.0.7
Alarm
card
cardNoResponse
card_no_response
1.3.6.1.4.1.164.3.3.2.1.0.8
Alarm
card
cardInitFailure
card_initialization_failure
1.3.6.1.4.1.164.3.3.2.1.0.9
Alarm
clock-domain
clockDomainStationClock
Unlock
1.3.6.1.4.1.164.6.2.52.0.8
Alarm
clock-domain
clockDomainSystemClock
Unlock
system_clock_unlock
1.3.6.1.4.1.164.6.2.52.0.1
Alarm
clock-domain
clockDomainStationClock
Unlock
1.3.6.1.4.1.164.6.2.52.0.8
Alarm
clock-domain
clockDomainQlLow
domain_clock_ql_low
1.3.6.1.4.1.164.6.2.52.0.2
Alarm
e1t1
e1t1Ais
ais
1.3.6.1.4.1.164.3.1.6.4.0.25
Alarm
e1t1
e1t1Lof
lof
1.3.6.1.4.1.164.3.1.6.4.0.26
Alarm
e1t1
e1t1Rai
rai
1.3.6.1.4.1.164.3.1.6.4.0.27
Alarm
erp
erpStateProtected
erp_state_protected
1.3.6.1.4.1.164.3.1.6.1.0.4
Alarm
eth
sdh-sonet
sfpNoResponse
sfp_no_response
1.3.6.1.4.1.164.40.3.4.0.1
Alarm
eth
sdh-sonet
sfpMismatch
sfp_mismatch
1.3.6.1.4.1.164.40.3.4.0.2
Alarm
eth
ethLos
los
1.3.6.1.4.1.164.3.1.6.1.0.1
Alarm
eth
sdh-sonet
sfpRemoved
sfp_removed
1.3.6.1.4.1.164.40.3.4.0.3
Alarm
eth
sdh-sonet
sfpTemperatureOra
sfp_temperature_ora
1.3.6.1.4.1.164.40.3.4.0.4
Alarm
eth
sdh-sonet
sfpOprOra
sfp_opr_ora
1.3.6.1.4.1.164.40.3.4.0.5
Alarm
eth
ethAutoNegotiationFailure
auto_negotiation_failure
1.3.6.1.4.1.164.3.1.6.1.0.6
Alarm
fan
fanFailure
fan_failure
1.3.6.1.4.1.164.6.1.0.64
Alarm
lag
lagLacpDown
lacp_down
1.3.6.1.4.1.164.6.2.54.0.1
Alarm
lag
lagLacpLoopDetection
lacp_loop_detection
1.3.6.1.4.1.164.6.2.54.0.2
11-20
Handling Events
ETX-5300A Ver. 1.0
Associated to
Source Type
Trap
Description
Notification OID
Alarm
lag
lagLacpChurn
lacp_churn
1.3.6.1.4.1.164.6.2.54.0.3
Alarm
oam-cfm-mep
oamCfmMepAis
ais
1.3.6.1.4.1.164.3.1.6.1.3.0.4
Alarm
oam-cfm-mep
oamCfmMepLck
lck
1.3.6.1.4.1.164.3.1.6.1.3.0.5
Alarm
oam-cfm-mep
oamCfmMepMismatch
mismatch
1.3.6.1.4.1.164.3.1.6.1.3.0.6
Alarm
oam-cfm-mep
oamCfmRmepLoc
loc
1.3.6.1.4.1.164.3.1.6.1.3.0.7
Alarm
oam-cfm-mep
oamCfmRmepRdi
rdi
1.3.6.1.4.1.164.3.1.6.1.3.0.8
Alarm
path
pathAis
ais-path
1.3.6.1.4.1.164.3.1.6.2.0.50
Alarm
path
pathLomf
lomf-path
1.3.6.1.4.1.164.3.1.6.2.0.51
Alarm
path
pathUneq
uneq-path
1.3.6.1.4.1.164.3.1.6.2.0.52
Alarm
path
pathTim
tim-path
1.3.6.1.4.1.164.3.1.6.2.0.53
Alarm
path
pathPlm
plm-path
1.3.6.1.4.1.164.3.1.6.2.0.54
Alarm
path
pathLop
lop-path
1.3.6.1.4.1.164.3.1.6.2.0.55
Alarm
path
pathSd
sd-path
1.3.6.1.4.1.164.3.1.6.2.0.56
Alarm
path
pathEed
eed-path
1.3.6.1.4.1.164.3.1.6.2.0.57
Alarm
path
pathRfi
rfi-path
1.3.6.1.4.1.164.3.1.6.2.0.58
Alarm
power-supply
powerDeliveryFailure
power_delivery_failure
1.3.6.1.4.1.164.6.1.0.73
Alarm
power-supply
powerInOra
power_in_ora
1.3.6.1.4.1.164.6.1.0.74
Alarm
power-supply
powerInLow
power_in_low
1.3.6.1.4.1.164.6.1.0.75
Alarm
ptp-master
ptpMasterUnavailableTod
unavailable_tod
1.3.6.1.4.1.164.6.2.52.0.24
Alarm
ptp-master
ptpMasterUnavailable1pps
unavailable_1pps
1.3.6.1.4.1.164.6.2.52.0.25
Alarm
ptp-master
ptpMasterSlavesLimitReached
slaves_limit_reached
1.3.6.1.4.1.164.6.2.52.0.26
Alarm
ptp-recovered
ptpRecoveredNoPtpMaster
no_ptp_master
1.3.6.1.4.1.164.6.2.52.0.10
Alarm
ptp-recovered
ptpRecoveredInvalidFreq
Accuracy
invalid_frequency_accuracy
1.3.6.1.4.1.164.6.2.52.0.11
Alarm
ptp-recovered
ptpRecoveredInvalidTime
Accuracy
invalid_time_accuracy
1.3.6.1.4.1.164.6.2.52.0.12
Alarm
ptp-recovered
ptpRecoveredDisqualified
Master
disqualified_master
1.3.6.1.4.1.164.6.2.52.0.13
Alarm
ptprecoveredmaster
ptpRecoveredMasterSyncFail
sync_failure
1.3.6.1.4.1.164.6.2.52.0.14
Alarm
ptprecoveredmaster
ptpRecoveredMasterAnnounce
Fail
announce_failure
1.3.6.1.4.1.164.6.2.52.0.15
ETX-5300A Ver. 1.0
Handling Events
11-21
Associated to
Source Type
Trap
Description
Notification OID
Alarm
ptprecoveredmaster
ptpRecoveredMasterDelay
RespFail
delay_response_failure
1.3.6.1.4.1.164.6.2.52.0.16
Alarm
pw
pwConfigMismatch
configuration_mismatch
1.3.6.1.4.1.164.14.0.1
Alarm
pw
pwOamFailure
pw_oam_failure
1.3.6.1.4.1.164.14.0.2
Alarm
pw
pwRdi
rdi
1.3.6.1.4.1.164.14.0.3
Alarm
pw
pwRxFailure
rx_failure
1.3.6.1.4.1.164.14.0.4
Alarm
pw
pwFeRxFailure
rx_failure_fe
1.3.6.1.4.1.164.14.0.6
Alarm
pw
pwFeRdi
rdi_fe
1.3.6.1.4.1.164.14.0.7
Alarm
routerinterface
routerIfDhcpClientNoLease
dhcp_client_no_lease
1.3.6.1.4.1.164.11.7.2.2.1.0.1
Alarm
sdh-sonet
sdhSonetLof
lof
1.3.6.1.4.1.164.3.1.6.2.0.22
Alarm
sdh-sonet
sdhSonetRfi
rfi-line
1.3.6.1.4.1.164.3.1.6.2.0.23
Alarm
sdh-sonet
sdhSonetLos
los
1.3.6.1.4.1.164.3.1.6.2.0.24
Alarm
sdh-sonet
sdhSonetAis
ais-line
1.3.6.1.4.1.164.3.1.6.2.0.25
Alarm
sdh-sonet
sdhSonetTim
tim
1.3.6.1.4.1.164.3.1.6.2.0.26
Alarm
sdh-sonet
sdhSonetSd
sd-line
1.3.6.1.4.1.164.3.1.6.2.0.27
Alarm
sdh-sonet
sdhSonetEed
eed-line
1.3.6.1.4.1.164.3.1.6.2.0.28
Alarm
station-clock
stationClockAis
ais
1.3.6.1.4.1.164.6.2.52.0.5
Alarm
station-clock
stationClockLof
lof
1.3.6.1.4.1.164.6.2.52.0.6
Alarm
station-clock
stationClockLos
los
1.3.6.1.4.1.164.6.2.52.0.7
Alarm
system
systemDeviceTemperatureOra
device_temperature_ora
1.3.6.1.4.1.164.6.1.0.41
Alarm
system
systemSwPackCorrupted
sw_pack_corrupted
1.3.6.1.4.1.164.6.1.0.61
Alarm
system
systemFeHardwareFailure
hardware_failure_fe
1.3.6.1.4.1.164.6.1.0.66
Alarm
vc-vt
vcVtAis
ais-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.67
Alarm
vc-vt
vcVtUneq
uneq-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.69
Alarm
vc-vt
vcVtTim
tim-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.70
Alarm
vc-vt
vcVtPlm
plm-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.71
Alarm
vc-vt
vcVtLop
lop-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.72
Alarm
vc-vt
vcVtSd
sd-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.73
Alarm
vc-vt
vcVtEed
eed-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.74
Alarm
vc-vt
vcVtRfi
rfi-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.75
Event
card
cardReset
card_reset
1.3.6.1.4.1.164.3.3.2.1.0.10
Event
card
cardSwitchover
card_switchover
1.3.6.1.4.1.164.3.3.2.1.0.13
11-22
Handling Events
ETX-5300A Ver. 1.0
Associated to
Source Type
Trap
Description
Notification OID
Event
card
cardPluggedIn
card_plugged_in
1.3.6.1.4.1.164.3.3.2.1.0.11
Event
card
cardPluggedOut
card_plugged_out
1.3.6.1.4.1.164.3.3.2.1.0.12
Event
clock-domain
clockDomainSystemSrcClock
Change
system_source_clock_change
1.3.6.1.4.1.164.6.2.52.0.3
Event
clock-domain
clockDomainStationSrcClock
Change
station_source_clock_change
1.3.6.1.4.1.164.6.2.52.0.9
Event
e1t1
e1t1Loopback
loopback
1.3.6.1.4.1.164.3.1.6.4.0.36
Event
e1t1
e1t1LoopbackOff
loopback_off
1.3.6.1.4.1.164.3.1.6.4.0.37
Event
e1t1
e1t1EsLineTca
es_line_tca
1.3.6.1.4.1.164.3.1.6.4.0.38
Event
e1t1
e1t1CvPathTca
cv_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.39
Event
e1t1
e1t1EsPathTca
es_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.40
Event
e1t1
e1t1SesPathTca
ses_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.41
Event
e1t1
e1t1SefsPathTca
sefs_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.42
Event
e1t1
e1t1CssPathTca
css_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.43
Event
e1t1
e1t1UasPathTca
uas_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.44
Event
erp-port
erpPortStateChange
erp_port_state_change
1.3.6.1.4.1.164.3.1.6.1.0.5
Event
eth
sdh-sonet
sfpOptOra
sfp_opt_ora
1.3.6.1.4.1.164.40.3.4.0.6
Event
eth
sdh-sonet
sfpOptOraOff
sfp_opt_ora_off
1.3.6.1.4.1.164.40.3.4.0.7
Event
eth
sdh-sonet
sfpLbcOra
sfp_lbc_ora
1.3.6.1.4.1.164.40.3.4.0.8
Event
eth
sdh-sonet
sfpLbcOraOff
sfp_lbc_ora_off
1.3.6.1.4.1.164.40.3.4.0.9
Event
lag
lagSubGroupSwitchover
sub_group_switchover
1.3.6.1.4.1.164.6.2.54.0.4
Event
lag
lagFailure
lag_failure
1.3.6.1.4.1.164.6.2.54.0.5
Event
oam-cfmdest-ne
oamCfmDestNeDelayTca
delay_tca
1.3.6.1.4.1.164.3.1.6.1.3.0.9
Event
oam-cfmdest-ne
oamCfmDestNeDelayTcaOff
delay_tca_off
1.3.6.1.4.1.164.3.1.6.1.3.0.10
Event
oam-cfmdest-ne
oamCfmDestNeDelayVarTca
delay_var_tca
1.3.6.1.4.1.164.3.1.6.1.3.0.11
Event
oam-cfmdest-ne
oamCfmDestNeDelayVarTca
Off
delay_var_tca_off
1.3.6.1.4.1.164.3.1.6.1.3.0.12
Event
oam-cfmdest-ne
oamCfmDestNeLossRatioTca
loss_ratio_tca
1.3.6.1.4.1.164.3.1.6.1.3.0.13
ETX-5300A Ver. 1.0
Handling Events
11-23
Associated to
Source Type
Trap
Description
Notification OID
Event
oam-cfmdest-ne
Off
loss_ratio_tca_off
1.3.6.1.4.1.164.3.1.6.1.3.0.14
Event
oam-cfmdest-ne
Fe
loss_ratio_tca_fe
1.3.6.1.4.1.164.3.1.6.1.3.0.15
Event
oam-cfmdest-ne
FeOff
loss_ratio_tca_fe_off
1.3.6.1.4.1.164.3.1.6.1.3.0.16
Event
oam-cfmdest-ne
oamCfmDestNeUnavailRatio
Tca
unavailable_ratio_tca
1.3.6.1.4.1.164.3.1.6.1.3.0.17
Event
oam-cfmdest-ne
TcaOff
unavailable_ratio_tca_off
1.3.6.1.4.1.164.3.1.6.1.3.0.18
Event
oam-cfmdest-ne
TcaFe
unavailable_ratio_tca_fe
1.3.6.1.4.1.164.3.1.6.1.3.0.19
Event
oam-cfmdest-ne
TcaFeOff
unavailable_ratio_tca_fe_off
1.3.6.1.4.1.164.3.1.6.1.3.0.20
Event
path
pathEsTca
es_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.59
Event
path
pathSesTca
ses_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.60
Event
path
pathCvTca
cv_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.61
Event
path
pathUasTca
uas_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.62
Event
path
pathFeEsTca
es_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.63
Event
path
pathFeSesTca
ses_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.64
Event
path
pathFeCvTca
cv_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.65
Event
path
pathFeUasTca
uas_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.66
Event
ptp-master
ptpMasterGrantedService
Aborted
granted_service_aborted
1.3.6.1.4.1.164.6.2.52.0.27
Event
ptp-master
ptpMasterSlaveRequestDenied
slave_request_denied
1.3.6.1.4.1.164.6.2.52.0.28
Event
ptp-recovered
ptpRecoveredPtpStateChange
ptp_state_change
1.3.6.1.4.1.164.6.2.52.0.17
Event
ptp-recovered
ptpRecoveredSevereFreq
Condition
severe_frequency_condition
1.3.6.1.4.1.164.6.2.52.0.18
Event
ptp-recovered
ptpRecoveredSevereTime
Condition
severe_time_condition
1.3.6.1.4.1.164.6.2.52.0.19
Event
ptp-recovered
ptpRecoveredMaster
Switchover
master_switchover
1.3.6.1.4.1.164.6.2.52.0.20
Event
ptprecoveredmaster
ptpRecoveredMasterUnicast
NegFail
unicast_negotiation_failure
1.3.6.1.4.1.164.6.2.52.0.21
Event
pw
pwSwitchover
pw_switchover
1.3.6.1.4.1.164.14.0.6
Event
pw
pwJitterBufferOverflow
jitter_buffer_overflow
1.3.6.1.4.1.164.14.0.9
11-24
Handling Events
ETX-5300A Ver. 1.0
Associated to
Source Type
Trap
Description
Notification OID
Event
pw
pwJitterBufferUnderflow
jitter_buffer_underflow
1.3.6.1.4.1.164.14.0.10
Event
sdh-sonet
sdhSonetEsSecTca
es_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.30
Event
sdh-sonet
sdhSonetSesSecTca
ses_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.31
Event
sdh-sonet
sdhSonetSefsSecTca
sefs_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.32
Event
sdh-sonet
sdhSonetCvSecTca
cv_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.33
Event
sdh-sonet
sdhSonetEsLineTca
es_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.34
Event
sdh-sonet
sdhSonetSesLineTca
ses_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.35
Event
sdh-sonet
sdhSonetCvLineTca
cv_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.36
Event
sdh-sonet
sdhSonetUasLineTca
uas_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.37
Event
sdh-sonet
sdhSonetFeEsLineTca
es_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.38
Event
sdh-sonet
sdhSonetFeSesLineTca
ses_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.39
Event
sdh-sonet
sdhSonetFeCvLineTca
cv_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.40
Event
sdh-sonet
sdhSonetFeUasLineTca
uas_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.41
Event
sdh-sonet
sdhSonetPortSwitchover
port_switchover
1.3.6.1.4.1.164.3.1.6.2.0.88
Event
sdh-sonet
sdhSonetLoopback
loopback
1.3.6.1.4.1.164.3.1.6.2.0.89
Event
sdh-sonet
sdhSonetLoopbackOff
loopback_off
1.3.6.1.4.1.164.3.1.6.2.0.90
Event
system
systemSoftwareInstallStart
sw_install_start
1.3.6.1.4.1.164.6.1.0.42
Event
system
systemSoftwareInstallEnd
sw_install_end
1.3.6.1.4.1.164.6.1.0.43
Event
system
systemDownloadEnd
download_end
1.3.6.1.4.1.164.6.2.12.18.0.2
Event
system
systemUserReset
user_reset
1.3.6.1.4.1.164.6.1.0.82
Event
system
systemAlternateConfigLoaded
alternate_configuration_
loaded
1.3.6.1.4.1.164.6.1.0.45
Event
system
systemConfigurationMigration
configuration_migration
1.3.6.1.4.1.164.6.1.0.46
Event
system
systemConfigurationSanity
configuration_sanity
1.3.6.1.4.1.164.6.1.0.47
Event
system
systemTrapHardSyncStart
trap_hard_sync_start
1.3.6.1.4.1.164.6.1.0.77
Event
system
systemTrapHardSyncEnd
trap_hard_sync_end
1.3.6.1.4.1.164.6.1.0.78
Event
system
systemConfigurationChange
Mask
configuration_change_mask
Event
system
systemConfigurationChange
Unmask
configuration_change_
unmask
Event
system
systemBackupConfiguration
Loaded
backup_configuration_loaded
1.3.6.1.4.1.164.6.1.0.54
Event
system
systemDeviceStartup
device_startup
1.3.6.1.4.1.164.6.1.0.55
Event
system
systemActiveSoftware
Changed
active_software_changed
1.3.6.1.4.1.164.6.1.0.83
ETX-5300A Ver. 1.0
Handling Events
11-25
Associated to
Source Type
Trap
Description
Notification OID
Event
system
systemRunningConfigSaved
running_config_saved
1.3.6.1.4.1.164.6.1.0.84
Event
system
systemSuccessfulLogin
successful_login
1.3.6.1.4.1.164.6.1.0.70
Event
system
systemFailedLogin
failed_login
1.3.6.1.4.1.164.6.1.0.71
Event
system
systemLogout
logout
1.3.6.1.4.1.164.6.1.0.72
Event
system
systemSwUnconfirmed
sw_unconfirmed
Event
system
systemStartupConfig
Unconfirmed
startup_config_unconfirmed
1.3.6.1.4.1.164.6.1.0.63
Event
vc-vt
vcVtEsTca
es_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.76
Event
vc-vt
vcVtSesTca
ses_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.77
Event
vc-vt
vcVtCvTca
cv_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.78
Event
vc-vt
vcVtUasTca
uas_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.79
Event
vc-vt
vcVtFeEsTca
es_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.80
Event
vc-vt
vcVtFeSesTca
ses_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.81
Event
vc-vt
vcVtFeCvTca
cv_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.82
Event
vc-vt
vcVtFeUasTca
uas_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.83
11.3 Running Diagnostic Tests

System-level diagnostic capabilities of ETX-5300A include ping and trace route
utilities.
Running a Ping Test

You can ping a remote IP host to check the ETX-5300A 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.1255.255.255.255> [number-of-packets <110000>] [payloadsize <321450 bytes>]
2. To stop the ping test, enter no ping.
Tracing the Route

This diagnostic utility traces the route through the network from ETX-5300A to
the destination host. The trace route utility supports up to 30 hops.
11-26
Running Diagnostic Tests
ETX-5300A Ver. 1.0
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.1255.255.255.255>
11.4 Technical Support

Technical support for this product can be obtained from the local partner from
whom it was purchased.
RADcare Global Professional Services offers a wide variety of service, support and
training options, including expert consulting and troubleshooting assistance,
online tools, regular training programs, and various equipment coverage options.
For further information, please contact the RAD partner nearest you or one of
RAD's offices worldwide.
RAD Data Communications would like your help in improving its product
documentation. Please send us an e-mail with your comments.
Thank you for your assistance!
ETX-5300A Ver. 1.0
Technical Support
11-27
11-28
Technical Support
ETX-5300A Ver. 1.0
Chapter 12
Software Upgrade
This chapter explains how to upgrade the ETX-5300A 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-5300A.
ETX-5300A 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
Impact
The software upgrade process is designed to minimize service disruption, as long

as following criteria are met:
Note
Two main cards are installed in the chassis
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 APS.
12.2 Software Upgrade Options

Application software can be downloaded to ETX-5300A via CLI (using SFTP) or via
the boot menu (using FTP).
12.3 Prerequisites
This section details the software file names and outlines system requirements
needed for the upgrade procedure.
ETX-5300A Ver. 1.0
Prerequisites
12-1
Chapter 12 Software Upgrade
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 version 1.0 software pack consists of three internal image files for the
E5-MC-4, E5-GBE-20/E5-1-GBE-2 and E5-cTDM-4 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-5300A 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
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:
The application software is downloaded from a PC to the ETX-5300A 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-5300A units in the network from a
central location. A central SFTP server application is installed on a PC on the
network.
12-2
ETX-5300A Ver. 1.0

Application file is
transferred to
ETX-5300A
Ethernet
PC with an Active
SFTP Server and
Application File
ETX-5300
Figure 12-1. Downloading a Software Application File to ETX-5300A via SFTP

Use the following procedure to download the software release to ETX-5300A
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-5300A 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-5300A Flash Disk.
Note
Configuration values shown in this chapter are examples only.
Pinging the PC
Check the integrity of the communication link between ETX-5300A and the PC by
pinging the ETX-5300A 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-5300A Flash Disk

Use this procedure to download the new software release to the ETX-5300A
flash disk.
To download an application file to the ETX-5300A 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.
ETX-5300A Ver. 1.0
12-3
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-5300A>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-5300A>file# dir
Codes
C - Configuration S - Software
LO Log
Name
Type Size(Bytes) Creation Date Status
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
Total Bytes : 101367808
Free Bytes : 63442944
To monitor the copy progress:
At the file# prompt, enter the show copy command, for example:
ETX-5300A# 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-5300A>file# sw-pack.bin copied to sw-pack-4 successfully
12-4
ETX-5300A Ver. 1.0
To display the partition contents:
At the file# prompt, enter the show sw-pack command, for example:
ETX-5300A>file# show sw-pack

Name
Version
Creation Time
Actual
---------------------------------------------------------------------------sw-pack-1 1.0.0(1.39) 2012-08-06
00:00:00 ready
sw-pack-1 Size (Bytes)
Type
Name
: 77140261
Version
H/W Ver
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-5300A 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-5300A 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-5300A includes redundant main cards, the software installation
process is slightly different, resulting in the main card flip.
Caution ETX-5300A 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-5300A# admin
ETX-5300A>admin# software
ETX-5300A>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-5300A displays confirmation request:
! Device will install file and reboot. Are you sure? [yes/no] _
2. For ETX-5300A with a single main card:
Confirm the install.

The previous software pack is deleted from the active partition:
ETX-5300A Ver. 1.0
12-5
deleting
deleting
deleting
deleting
file
file
file
file
/tffs0/Sw-Pack/Active/main.bin
/tffs0/Sw-Pack/Active/eth1g.bin
/tffs0/Sw-Pack/Active/eth2X10g.bin
/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-5300A performs reboot automatically and is now ready for
operation with new software version.
ETX-5300A is upgraded and starts with the new software version.
or
3. For ETX-5300A 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-5300A 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-5300A copies the previous application software from the restore-pointconfig file, reboots, and runs the previous application software version.
Note
For ETX-5300A 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.
Task
Command
Comments
Enabling or disabling
confiramation of application
software file after reboot
software-confirm-required [time-toconfirm <51440>]
Default time-to-confirm
5 min.
12-6
no software-confirm-required
to disable application software
confirmation
ETX-5300A Ver. 1.0
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-5300A 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-5300A waits for reset of at least one I/O card
Software Installed From Boot ETX-5300A detected a new software release

installed via the Boot menu
Unconfirmed Software Used in Lack Of Valid Software ETX-5300A uses

unconfirmed software due to the lack of confirmed file
The slot software installation statuses are as follows:

ETX-5300A Ver. 1.0
12-7
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.5 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-5300A 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-5300A 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-5300A 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-5300A.
Note
All the screens shown in this section are for illustration purposes only. Your
ETX-5300A may display different software versions and port profiles.
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.
12-8
Upgrading Software via the Boot Menu
ETX-5300A Ver. 1.0
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-5300A.
To start VXWORKS Boot Manager:

1. Verify that the *.bin file is stored on the PC with the terminal application.
2. 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.
3. Turn off ETX-5300A.
4. Activate the terminal application.
5. Turn on ETX-5300A.
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....
6. Press any key to stop the auto-boot and get a boot prompt.
The boot prompt is displayed:
[boot]:
7. 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

8. 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.
ETX-5300A Ver. 1.0
12-9
[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-5300A
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-5300A
device mask
dm
The IP subnet mask of ETX-5300A
server IP
sip
The FTP server IP address
gateway ip
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-5300A IP address.
Note: If no default gateway is needed, for example,
because the FTP server is attached to the same LAN as
ETX-5300A being upgraded, enter 0.0.0.0.
user
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.
Note
device name
dn
ETX-5300A
quick autoboot
Enabling or disabling the quick autoboot feature
protocol
The file transfer protocol in use: FTP only
baud rate
Transmission bit rate (in kbps): 9600, 19200, 115200
The CLI commands are case insensitive.

9. Press <C> to change the boot parameters and type valid values in each field.
12-10
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).
ETX-5300A Ver. 1.0
'.' = 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-5300A
quick autoboot [y/n] : y
protocol [tftp/ftp] : ftp
baud rate [9600/19200/115200]: 9600
10. 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-5300A via FTP.
To download software file(s) from the Boot menu to ETX-5300A via FTP:
1. Verify that the *.bin file is stored on the PC with the FTP server application.
2. 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.
3. Turn on ETX-5300A and enter the Boot menu. Set FTP protocol.
4. 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-5300A 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]:
5. Using dir command, check which partition is currently active. In this example it
is sw-pack-1.
ETX-5300A Ver. 1.0
12-11
[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
Total Bytes : 101367808
Free Bytes
: 69701632
6. 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.
7. 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:
12-12
ETX-5300A Ver. 1.0

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.
8. Press <Enter> to start working with the new SW release downloaded.
Note
The new parameters take effect only after the reset is completed.
12.6
Verifying the Upgrade Results
To verify that the upgrade was successful, log on to ETX-5300A to view the
Inventory summary.
To verify the upgrade result:
ETX-5300A Ver. 1.0
At the config# prompt, enter show inventory-summary and verify the active
software version in the SW Ver column.
12-13

ETX-5300A# config>chassis# show inventory-summary
Index Physical Class Name
HW Ver
SW Ver
FW Ver
----------------------------------------------------------------------------1001 Chassis
AC-chassi
N/A
1.0.0(1.39)
N/A
2001
Backplane
Backplane
0.0/A
N/A
N/A
3001
Container
N/A
N/A
N/A
3002
Container
N/A
N/A
N/A
3003
Container
N/A
N/A
N/A
3004
Container
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
3008
Container
Slot 5 Port 2
N/A
N/A
N/A
3009
Container
Slot 5 Port 3
N/A
N/A
N/A
3010
Container
Slot 5 Port 4
N/A
N/A
N/A
3011
Container
Slot 6 Port 1
N/A
N/A
N/A
3012
Container
Slot 6 Port 2
N/A
N/A
N/A
3013
Container
Slot 6 Port 3
N/A
N/A
N/A
3014
Container
Slot 6 Port 4
N/A
N/A
N/A
3015
Container
Slot 1 Port 1
N/A
N/A
N/A
3016
Container
Slot 1 Port 2
N/A
N/A
N/A
3017
Container
Slot 1 Port 3
N/A
N/A
N/A
3018
Container
Slot 1 Port 4
N/A
N/A
N/A
3019
Container
Slot 1 Port 5
N/A
N/A
N/A
3020
Container
Slot 1 Port 6
N/A
N/A
N/A
3021
Container
Slot 1 Port 7
N/A
N/A
N/A
3022
Container
Slot 1 Port 8
N/A
N/A
N/A
3023
Container
Slot 1 Port 9
N/A
N/A
N/A
12-14
ETX-5300A Ver. 1.0
3024
Container
Slot 1 Port 10
N/A
N/A
N/A
3025
Container
Slot 1 Port 11
N/A
N/A
N/A
3026
Container
Slot 1 Port 12
N/A
N/A
N/A
3027
Container
Slot 1 Port 13
N/A
N/A
N/A
3028
Container
Slot 1 Port 14
N/A
N/A
N/A
3029
Container
Slot 1 Port 15
N/A
N/A
N/A
3030
Container
Slot 1 Port 16
N/A
N/A
N/A
3031
Container
Slot 1 Port 17
N/A
N/A
N/A
3032
Container
Slot 1 Port 18
N/A
N/A
N/A
3033
Container
Slot 1 Port 19
N/A
N/A
N/A
3034
Container
Slot 1 Port 20
N/A
N/A
N/A
3075
Container
Slot 4 Port 1
N/A
N/A
N/A
3076
Container
Slot 4 Port 2
N/A
N/A
N/A
3077
Container
Slot 4 Port 3
N/A
N/A
N/A
3078
Container
Slot 4 Port 4
N/A
N/A
N/A
3079
Container
Slot 4 Port 5
N/A
N/A
N/A
3080
Container
Slot 4 Port 6
N/A
N/A
N/A
3081
Container
Slot 4 Port 7
N/A
N/A
N/A
3082
Container
Slot 4 Port 8
N/A
N/A
N/A
3083
Container
Slot 4 Port 9
N/A
N/A
N/A
3084
Container
Slot 4 Port 10
N/A
N/A
N/A
3085
Container
Slot 4 Port 11
N/A
N/A
N/A
3086
Container
Slot 4 Port 12
N/A
N/A
N/A
3087
Container
Slot 4 Port 13
N/A
N/A
N/A
3088
Container
Slot 4 Port 14
N/A
N/A
N/A
3089
Container
Slot 4 Port 15
N/A
N/A
N/A
3090
Container
Slot 4 Port 16
N/A
N/A
N/A
3091
Container
Slot 4 Port 17
N/A
N/A
N/A
ETX-5300A Ver. 1.0
12-15
3092
Container
Slot 4 Port 18
N/A
N/A
N/A
3093
Container
Slot 4 Port 19
N/A
N/A
N/A
3094
Container
Slot 4 Port 20
N/A
N/A
N/A
3095
Container
AC Slot
N/A
N/A
N/A
3096
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
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
7002
Port
N/A
N/A
N/A
7003
Port
N/A
N/A
N/A
7004
Port
N/A
N/A
N/A
7009
Port
MNG Port
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
N/A
N/A
N/A
7014
Port
N/A
N/A
N/A
7016
Port
RS_232 Control Port
N/A
N/A
N/A
7017
Port
Clock RJ45 Port
N/A
N/A
N/A
7018
Port
Clock BNC Port
N/A
N/A
N/A
7019
Port
N/A
N/A
N/A
12-16
ETX-5300A Ver. 1.0
7020
Port
N/A
N/A
N/A
7021
Port
Ethernet Port 1/1
N/A
N/A
N/A
7022
Port
Ethernet Port 1/2
N/A
N/A
N/A
7023
Port
Ethernet Port 1/3
N/A
N/A
N/A
7024
Port
Ethernet Port 1/4
N/A
N/A
N/A
7025
Port
Ethernet Port 1/5
N/A
N/A
N/A
7026
Port
Ethernet Port 1/6
N/A
N/A
N/A
7027
Port
Ethernet Port 1/7
N/A
N/A
N/A
7028
Port
Ethernet Port 1/8
N/A
N/A
N/A
7029
Port
Ethernet Port 1/9
N/A
N/A
N/A
7030
Port
Ethernet Port 1/10
N/A
N/A
N/A
7031
Port
Ethernet Port 1/11
N/A
N/A
N/A
7032
Port
Ethernet Port 1/12
N/A
N/A
N/A
7033
Port
Ethernet Port 1/13
N/A
N/A
N/A
7034
Port
Ethernet Port 1/14
N/A
N/A
N/A
7035
Port
Ethernet Port 1/15
N/A
N/A
N/A
7036
Port
Ethernet Port 1/16
N/A
N/A
N/A
7037
Port
Ethernet Port 1/17
N/A
N/A
N/A
7038
Port
Ethernet Port 1/18
N/A
N/A
N/A
7039
Port
Ethernet Port 1/19
N/A
N/A
N/A
7040
Port
Ethernet Port 1/20
N/A
N/A
N/A
7082
Port
Ethernet Port 4/2
N/A
N/A
N/A
7083
Port
Ethernet Port 4/3
N/A
N/A
N/A
7084
Port
Ethernet Port 4/4
N/A
N/A
N/A
7085
Port
Ethernet Port 4/5
N/A
N/A
N/A
7086
Port
Ethernet Port 4/6
N/A
N/A
N/A
7087
Port
Ethernet Port 4/7
N/A
N/A
N/A
7088
Port
Ethernet Port 4/8
N/A
N/A
N/A
ETX-5300A Ver. 1.0
12-17
7089
Port
Ethernet Port 4/9
N/A
N/A
N/A
7090
Port
Ethernet Port 4/10
N/A
N/A
N/A
7091
Port
Ethernet Port 4/11
N/A
N/A
N/A
7092
Port
Ethernet Port 4/12
N/A
N/A
N/A
7093
Port
Ethernet Port 4/13
N/A
N/A
N/A
7094
Port
Ethernet Port 4/14
N/A
N/A
N/A
7095
Port
Ethernet Port 4/15
N/A
N/A
N/A
7096
Port
Ethernet Port 4/16
N/A
N/A
N/A
7097
Port
Ethernet Port 4/17
N/A
N/A
N/A
7098
Port
Ethernet Port 4/18
N/A
N/A
N/A
7099
Port
Ethernet Port 4/19
N/A
N/A
N/A
7100
Port
Ethernet Port 4/20
N/A
N/A
N/A
Note
If downloading failed, repeat the entire procedure.
12.7 Restoring the Previous Software Version

ETX-5300A 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:

1. At the admin>software# prompt, enter the undo-install command.
ETX-5300A displays confirmation request:
! This action will revert system to restore point. Are you sure? [yes/no] _
2. Confirm the install.
ETX-5300A reverts to the previous software version and _reboots.
12-18
Restoring the Previous Software Version
ETX-5300A Ver. 1.0
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
A.2
Pin
Designation
Function
1, 4, 6, 7, 8, 9
Not connected
Tx +
Transmit
Rx
Receive
MNG ETH Connector
Each ETX-5300A 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
ETX-5300A Ver. 1.0
Pin
Designation
Function
TxD+
Transmit data output, + wire
TxD
Transmit data output, wire
RxD+
Receive data input, + wire
4, 5
Not connected
RxD
Receive data input, wire
7, 8
Not connected
MNG ETH Connector
A-1
Appendix A Connection Data
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
A.4
Pin
Signal
Function
BI_DA+
Bi-directional pair +A
BI_DA-
Bi-directional pair -A
BI_DB+
Bi-directional pair +B
BI_DC+
Bi-directional pair +C
BI_DC-
Bi-directional pair -C
BI_DB-
Bi-directional pair -B
BI_DD+
Bi-directional pair +D
BI_DD-
Bi-directional pair -D
EXT CLK Connector
The balanced external clock interface on the E5-MC-4 card terminates in an RJ-45
connector, wired in accordance with Table A-4.
Table A-4. EXT CLK Interface Connector, Pin Functions
A.5
Pin
Designation
Function
RRING
Receive data input
RTIP
Receive data input
TRING
Transmit data output
TTIP
Transmit data output
3, 6
Not connected
7, 8
Not connected
TOD Connector
The RS-422 GPS-based ToD clock interface on the E5-MC-4 card terminates in an
RJ-45 connector, wired in accordance with Table A-5.
A-2
TOD Connector
ETX-5300A Ver. 1.0
Table A-5. TOD Interface Connector, Pin Functions
A.6
Pin
Designation
Function
TOD Rx
Receive data input, wire
TOD Rx +
Receive data input, + wire
1 pps Tx/Rx
Transmit/receive 1 pps, wire
1 pps Tx/RX+
Transmit/receive 1 pps, + wire
4, 5
GND
GND
TOD Tx/Rx
Transmit/receive TOD, wire
TOD Tx/Rx +
Transmit/receive TOD, + wire
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 60 W). The maximum
voltage across the open contacts is 60 VDC/30 VAC.
Table A-6. ALARM Connector, Pin Functions
ETX-5300A Ver. 1.0
Pin
Function
Minor Alarm Normally Open
Minor Alarm Normally Close
GND
Major Alarm Normally Open
Major Alarm Normally Close
12V output
Critical Alarm Normally Open
Critical Alarm Normally Close
Minor Alarm common
10
Input Alarm 0
ALARM Connector
A-3
A-4
ALARM Connector

Pin
Function
11
Input Alarm 1
12
Major Alarm common
13
Input Alarm 2
14
Input Alarm 3
15
Critical Alarm common
ETX-5300A Ver. 1.0
Appendix B
Data Flow and Traffic
Management
This appendix describes service creation and traffic management performed by
ETX-5300A. It discusses the following topics:
Data Path Model
Ingress Processing
Classification
CoS Mapping
Ingress Color Mapping
Policing
VLAN Editing
Traffic Management.
B.1
Data Path Model
Figure B-1 illustrates the high-level structure of an ETX-5300A system, in which:
ETX-5300A Ver. 1.0
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 the 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 traffic 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.
Data Path Model
B-1
Appendix B Data Flow and Traffic Management
4 x 10GbE
4 x 10GbE
Main Card
Main Card
Timing
Timing
Packet
Processor
Power
Packet
Processor
Common
Logic
Common
Logic
GbE, 10GbE or
SDH/SONET
I/O Card
Fans
ETX-5300A
Figure B-1. High-Level Architecture of ETX-5300A
I/O-to-Main and Main-toI/O Traffic Path

Figure B-2 illustrates the data flow and main traffic management functions
performed by I/O and main Ethernet cards.
Main and I/O cards are interconnected via two 10GbE internal ports, which
provide 20 GbE bandwidth path with a non-blocking arch.
B-2
Data Path Model
ETX-5300A Ver. 1.0
I/O to Main Card Direction
Classify
20 x GbE
or
2 x 10GbE
Map CoS
and Color
Police
Ethernet I/O Card
Pre-Forwarding
Scheduling
and Shaping
2 x 10GbE
Forward
Post-Forwarding
Scheduling and
Shaping
Edit
Ethernet Main Card
Post-Forwarding
Scheduling and
Shaping
Edit
Forward
4 x 10GbE
Map CoS
and Color
Classify
Main to I/O Card Direction
Figure B-2. 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-5300A 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.
ETX-5300A Ver. 1.0
Data Path Model
B-3
Data Path
Figure B-3 illustrates the general traffic path within the ETX-5300A system in the
ingress-to-egress direction.
Ingress
Egress
Ethernet I/O or
Main Card Ingress
Bridge
Pseudowire
Aggregation
TDM Pseudowire
Processing
I/O Card STM-1/

OC-3 Port
TDM I/O Card Ingress
Shaping
Queuing
Shaping
Queuing
Flow
Aggregation
Policing
CoS & Color

Mapping
Classification
Ingress Processing
(L2CP)
I/O Card
Ethernet Port
Main Card
Ethernet Port
Tunnel
I/O or Main Card Ethernet Ports
VLAN
Editing
SAG
Router
UDP/IP or
MEF-8
Pseudowires
Ingress Processing
Forwarding
Egress Traffic Managemnt
Figure B-3. Data Path

Note
SAG (Service Aggregation Group) is a logical port (management entity) that

represents a physical connection between I/O and main Ethernet cards. Preforwarding 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).
B-4
Data Path Model
ETX-5300A Ver. 1.0
Pre-forwarding
Processing
(VLAN/Ethertype
recognition and
admission)
Per Port L2CP

Handling
Ingress Scheduling
and Shaping (using
traffic classes and
drop precedence)
Policing
Classification
to Flows
Per Flow L2CP

Handling
First-Level VLAN
Editing (using traffic
classes and drop
precedence)
Traffic Class
(CoS) Mapping
Forwarding (bridge,
router or VLAN
cross-connect)
Ethernet I/O
Cards only
Drop Precedence
(Color) Ingress
Mapping
Second-Level VLAN
Editing (using traffic
classes and drop
precedence)
Post-forwarding
Scheduling and
Shaping (using
traffic classes and
drop precedence)
Figure B-4. Detailed Ingress-to-Egress Packet-Processing Flow
I/O Card Schematics

As mentioned in the Note above, GbE and 10GbE cards introduce logical ports
that serve as management entities (SAG) and flow aggregation points (SAP).
Figure B-5 illustrates Ethernet I/O card schematics.
Each I/O Ethernet card has two SAGs, serving ports 110 and 1120, 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 512 SAPs, which aggregate ingress flows
from I/O card ports.
Flow
SAP

SAG
Flow
Flow

SAP
SAP
SAG
Flow
SAP
Figure B-5. I/O Ethernet Card

ETX-5300A Ver. 1.0
Data Path Model
B-5
B.2
Ingress Processing
This section describes ingress processing of traffic performed by directly- and

indirectly-attached ports.
Frame Format
ETX-5300A supports Ethernet II frames. It does not support IEEE 802.3 LLC
packets.
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 instructing 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 its transmission. If that timer
expires or is cleared by getting a PAUSE frame with the timer value 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.
Ethertype
Ethertype configured per port is used for the identification of VLAN-tagged
frames at ingress and VLAN editing at egress. This refers to outer VLAN only. The
outer VLAN of the incoming 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-5300A 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.
B-6
Ingress Processing
ETX-5300A Ver. 1.0
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:
Note
Indirectly-attached ports inner VID (if exists) is 8100
Directly-attached ports inner VID is either the same as outer VID Ethertype
or 8100.
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 B-1. Indirectly-Attached Ports with Port TPID 8100

Outer TPID
Inner TPID
Admit/Drop
Recognized Tag Levels
8100
None
Admit
8100
8100
Admit
8100
X (other than 8100)
Admit
X (other than 8100)
Dont care
Admit
Untagged
None
Admit
Untagged
Table B-2. Indirectly-Attached Ports with Port TPID Y (other than 8100)
Outer TPID
Inner TPID
Admit/Drop
None
Admit
8100
Admit
X (other than 8100)
Admit
Z (other than Y)
Dont care
Admit
Untagged
None
Admit
Untagged
Table B-3. Directly-Attached Ports with Port TPID 8100
ETX-5300A Ver. 1.0
Outer TPID
Inner TPID
Admit/Drop
8100
None
Admit
8100
8100 or Y
Admit
8100
X (other than 8100)
Admit
X (other than 8100)
Dont care
Admit
Untagged
None
Admit
Untagged
Ingress Processing
B-7
Table B-4. Directly-Attached Ports with Port TPID Y (other than 8100)
Outer TPID
Inner TPID
Admit/Drop
None
Admit
8100 or Y
Admit
B (other than 8100 or Y)
Admit
8100
Dont care
Drop
B (other than 8100 or Y)
Dont care
Admit
Untagged
None
Admit
Untagged
Note
TPID is also used to indicate the Ethertype tag used in VLAN stacking.
L2CP Handling
ETX-5300A handles Layer-2 control protocol traffic on a per-port and/or a perflow 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-5300A 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-5300A can tunnel, discard or peer (trap to host for protocol processing) L2CP
packets. These actions are defined by L2CP profiles, which also provide different
L2CP addresses. The following MAC addresses are supported by L2CP profiles: 0180-C2-00-00-00, 01-80-C2-00-00-02 10 and 01-80-C2-00-00-20 2F.
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 a port, and, optionally, at a flow level. The
following section describes functionality of port- and flow-level L2CP profiles.
According to per-port L2CP profiles, ETX-5300A performs the following:
B-8
Ingress Processing
ETX-5300A Ver. 1.0
Note
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-5300A 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.
ETX-5300A does not support peer action at port level.

According to per-flow L2CP profiles, ETX-5300A performs the following:
Note
Discards L2CP traffic
Tunnels L2CP traffic. ETX-5300A forwards the traffic according to its

configuration (flows, etc).
Peers L2CP traffic. ETX-5300A forwards the traffic to the CPU.
L2CP traffic can be peered only at the flow level. Therefore, for full LACP support,
the user must define an untagged flow with per-flow L2CP profile to peer the
LACP traffic.
Default L2CP Profile

By default, a tunnel all profile is attached to every port. However, no default
L2CP profile is attached to a newly created flow. Thus, by default the flow traffic
behaves according to the port profile.
L2CP Profiles and Traffic Classification Keys

L2CP profiles can be attached only to flows created using the classification types
detailed in Table B-5.
Table B-5. 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 +

Inner VID
VLAN (outer)
Outer VLAN + P-bit + Inner VLAN
Unclassified (indirectly-attached ports only)
VLAN + Src MAC
VLAN + IP-P or
VLAN + DSCP
LAN + Non IP
P-bit
P-bit

Unclassified
Unclassified
ETX-5300A Ver. 1.0
Ingress Processing
B-9
Classification Key
Flow Classification Type
IP-P,
DSCP
Non IP (used for per-port L2CP profiles as well)
B.3
Unclassified
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 B-6 and Table B-7 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 B-8,
Table B-9, Table B-10, Table B-11, Table B-12, Table B-13, Table B-14,
Table B-15, Table B-16.
Table B-6. 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 B-7. Classification Keys for Directly-Attached Ports

Classification Key (Port + )
CoS 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 B-8.
B-10
Classification
ETX-5300A Ver. 1.0
Table B-8. Indirectly-Attached Ports with VLAN+P-Bit Classifier Key

Classifier Profile Type
Range (per Flow)
Priority
VLAN (see note 1 below)
VLAN + P-bit
Single VLAN range, single P-bit

range
VLAN + Src MAC (see Note 1 below)
Single VLAN, single MAC
Single VLAN, single IP
Single MAC
Single IP
Single Ethertype
VLAN + Dst MAC (see note 1 below)

VLAN + Src IP (see Note 1 below)
VLAN + Dst IP (see Note 1 below)
Src MAC
Dst MAC
Src IP
Dst IP
Ethertype
Untagged
Match All (Unclassified), default
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 (07).
ETX-5300A 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 B-8, 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 17.
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:
ETX-5300A Ver. 1.0
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.
Classification
B-11
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 1120 of the E5-GbE-20 card, or on ports 1 or 2 of the E5-10GbE-2 card.
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 B-9.
Table B-9. Indirectly-Attached Ports with VLAN + IP Precedence Classifier Key

Range (per Flow)
Priority
VLAN (see Note 1 below)
VLAN + IP Precedence
Single VLAN range, single IP-P

range
Single MAC
Single IP
Single Ethertype
VLAN + Dst MAC (see Note 1 below)

Src MAC
Dst MAC
Src IP
Dst IP
Ethertype
Untagged
Non-IP
VLAN + Non-IP
Note
Single VLAN range
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 (07). Packets with VLANs, but
without IP Precedence (non-IP) will not match these classifier profiles.
ETX-5300A recognizes only one level of VLAN tagging on the flows created
detected.
A packet with an Ethertype tag that does not match the port Ethertype tag is
considered to be untagged.
B-12
Classification
ETX-5300A Ver. 1.0
Priority
Flow priority, shown in Table B-9, 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 17.
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).

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 1120 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 B-10. Indirectly-Attached Ports with VLAN + DSCP Classifier Key

Range (per Flow)
Priority
VLAN (see Note 1 below)
VLAN + DSCP
Single VLAN range, single DSCP

range
Single MAC
Single IP
Single Ethertype

Src MAC
Dst MAC
Src IP
Dst IP
Ethertype
Untagged
ETX-5300A Ver. 1.0
2
Classification
B-13

Range (per Flow)

Priority
Non-IP
VLAN + Non-IP
Note
Single VLAN range
(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 (063). Packets with VLANs, but without
DSCP (non-IP) will not match these classifier profiles.
(2) ETX-5300A recognizes only one level of VLAN tagging on the flows created
detected.
Priority
Flow priority, shown in Table B-10, is a hard-coded attribute of a flow that
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 163.
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 B-11.
B-14
Classification
ETX-5300A Ver. 1.0
Table B-11. Indirectly-Attached Ports with P-Bit Classifier Key

Range (per Flow)
Priority
P-bit
Single P-bit range
Src MAC
Single MAC
Single IP
Single Ethertype
Dst MAC
Src IP
Dst IP
Ethertype
Untagged
Note
ETX-5300A 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.
Priority
For example, if a flow with P-bit 07 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 02, P-bit 3 and P-bit 47.

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 110 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 B-12. Indirectly-Attached Ports with IP Precedence Classifier Key

Range (per Flow)
Priority
IP Precedence
Single IP-P range
ETX-5300A Ver. 1.0
Classification
B-15
Range (per Flow)
Priority
Src MAC
Single MAC
Single IP
Single Ethertype
Dst MAC
Src IP
Dst IP
Ethertype
Non-IP
Priority
cannot be changed. Two flows with the same priority cannot overlap.
For example, if a flow with IP-P 07 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 02, IP-P 3
and IP-P 47.

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 B-13.
Table B-13. Indirectly-Attached Ports with DSCP Classifier Key

Range (per Flow)
Priority
DSCP
Single P-bit range
Src MAC
Single MAC
Single IP
Single Ethertype
Dst MAC
Src IP
Dst IP
Ethertype
Untagged
B-16
Classification
ETX-5300A Ver. 1.0
Priority
For example, if a flow with DSCP 063 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 02, 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.
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 B-14.
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 B-14. Indirectly-Attached Ports with Outer VLAN + P-bit + Inner VLAN Classifier Key
Range (per Flow)
Priority
Single outer VLAN, single P-bit

range, single inner VLAN range
Single VLAN, single P-bit range
Single IP
Single Ethertype
Outer VLAN + Inner VLAN

(see Note 1 below)
VLAN (see notes 1 and 2 below)
VLAN + P-bit (see Notes 1 and 2 below)
VLAN + Src MAC (see note 1 below)
Src IP
Dst IP
Ethertype
ETX-5300A Ver. 1.0
Classification
B-17

Range (per Flow)

Priority
Untagged
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 (07).
(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 B-14, 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).

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 B-15.
Table B-15. Directly-Attached Ports with VLAN+P-bit Classifier Key

Range (per Flow)
Priority
VLAN (see note 1 below)
Single VLAN range, Single P-bit

range
VLAN + P-bit
Untagged
B-18
Classification
ETX-5300A Ver. 1.0
Note
(1) VLAN classifier profile type is supported without explicit P-bit indication,
but it actually implies a full P-bit range (07).

(2) When a two-level VLAN frame is received, this classification refers to the
outer VLAN.
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 B-16.
Note
A packet with an outer Ethertype tag that does not match the port Ethertype tag
is considered untagged.
Table B-16. Directly-Attached Ports with Outer VLAN + P-bit + Inner VLAN Classifier Key
Range (per Flow)
Priority
Single outer VLAN, single P-bit

range, single inner VLAN range
Single VLAN, single P-bit range
Outer VLAN + Inner VLAN

(see note 1 below)
VLAN (see notes 1 and 2 below)
VLAN + P-bit (see note 2 below)
Untagged
Note
(1) VLAN classifier profile type is supported without explicit P-bit indication,
but it actually implies a full P-bit range (07).

(2) VLAN and VLAN + P-bit classification profile type relate to packets with
single VLAN level only.

ETX-5300A Ver. 1.0
Classification
B-19
B.4
CoS Mapping
User priorities must be 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 (07), then this
CoS is used for VLAN editing (P-bit) or priority queue mapping.
Ingress Traffic
CoS Mapping
CoS to P-bit (VLAN Editing)
Profiles to map packet to CoS:
Profiles to map:
P-bit to CoS (07)
DSCP to CoS (07)
IP Precedence to CoS (07)
Flow to CoS
CoS to P-bit
Queue Mapping
Profiles to map:
CoS to priority queue (07)
Table B-6 and Table B-7 give detailed description 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-5300A 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 B-17. P-Bit to CoS Default Mapping Profile

P-bit
0
B-20
CoS Mapping
CoS
7
ETX-5300A Ver. 1.0
Table B-18. IP Precedence to CoS Default Mapping Profile

IP-P
0
CoS
7
Table B-19. DSCP to CoS Default Mapping Profile

DSCP
0
CoS
7
763
Indirectly-attached ports support up to 12 profiles. The CoS mapping method for

indirectly-attached ports depends on the selected classification key (see
Table B-6). 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 B-7).
ETX-5300A Ver. 1.0
CoS Mapping
B-21
Table B-20. Possible Combinations of CoS and Ingress Color Mapping Methods for
Directly-Attached Ports
Note
CoS 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)
See Ingress 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.
Table B-21. CoS to Priority Queue Mapping

CoS
0
B-22
CoS Mapping
Queue
1
ETX-5300A Ver. 1.0
B.5
ETX-5300A 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-5300A 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 B-6 and Table B-7 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
ETX-5300A Ver. 1.0
The ingress color mapping method for directly-attached ports depends on

selected CoS mapping for a flow. See Table B-20 for possible combinations of
CoS mapping and color mapping profiles.
B-23
B.6
Policing
When the flows are established, a metering and policing function can be applied
for each ingress flow on indirectly-attached ports to regulate traffic according to
the contracted CIR, EIR, CBS and EBS bandwidth profiles.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).
ETX-5300A supports up to 128 policer bandwidth profiles (regular and aggregate)
with up to:
2K policer instances per each Ethernet I/O 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
, 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 (see Ingress Color
Mapping section above).
B-24
Policing
ETX-5300A Ver. 1.0
The color-aware policing mechanism conforms to MEF 10.1 requirements and is

illustrated below:
Arriving packet is
green and CIR bucket
is not exceeded
Yes
Packet is green
No
Packets are admitted

to network
EIR bucket is not

exceeded
(see Note below)
Yes
Packet is yellow
No
Packet is red and it is

dropped
Figure B-6. 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 form 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.
B.7
VLAN Editing
The VLAN tag editing mechanism allows service providers to carry customertagged traffic on its network using its own VLANs. You can configure tag editing
ETX-5300A Ver. 1.0
VLAN Editing
B-25
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-5300A 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
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 B-22 details VLAN editing options available for E-Line (point-to-point)
services.
Table B-22. 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

according to CoS marking
profile)
None
vlan-tag push vlan <vid> p-bit profile <profile name>
Swap (copy P-bit and DEI)
None
mark all
vlan <vid>
Swap (set P-bit and DEI

profile)
None

profile)
mark all
vlan <vid>
marking-profile <profile name>
mark all
vlan <vid>
exit
B-26
VLAN Editing
ETX-5300A Ver. 1.0
Action 1
Action 2
CLI Command
mark all
vlan <vid>
exit
vlan-tag push vlan <vid> p-bit copy
vlan-tag push vlan <vid> p-bit copy inner-vlan <vid> pbit copy

profile)

inner-vlan <vid> p-bit copy

profile), see Note below

profile), see Note below

inner-vlan <vid> p-bit profile <profile name>
Pop
mark all
inner-vlan <vid>
exit
vlan-tag pop vlan
Pop
Swap (set P-bit and DEI

profile)
mark all
vlan <vid>
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:
ETX-5300A Ver. 1.0
Pop: Not relevant
Swap: TPID of the egress port
Pop-pop: Not relevant.

VLAN Editing
B-27
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 B-23. VLAN Editing Options at Bridge Port Ingress

Action
CLI Command
None
Pop (outer)
vlan-tag-pop vlan
vlan-tag push vlan <sp-vlan> p-bit copy

[tag-ether-type <tag-ether-type>]
Push (set P-bit to a user-configured

value, set DEI to 0)
vlan-tag push vlan <sp-vlan>p-bit fixed

<fixed-p-bit>[tag-ether-type <tag-ethertype>]
mark all vlan <vlan-value> p-bit copy [tagether-type <tag-ether-type>]
Table B-24. VLAN Editing Options at Bridge Port Egress
Note
Action
CLI Command
None
Pop (outer)
vlan-tag-pop vlan
vlan-tag push vlan <sp-vlan> p-bit copy
Push (set P-bit and DEI according to CoS

marking profile)
vlan-tag push vlan <sp-vlan> p-bit profile

<inner-marking-profile-name>
mark all vlan <vlan-value> p-bit copy
Swap (set P-bit and DEI according to CoS

marking profile)
mark all vlan <vlan-value> p-bit profile

<inner-marking-profile-name>
The VLAN editing options allowed at bridge port ingress also depend on the
configured flow classification method. Valid combinations are listed in

Table B-25 and Table B-26.
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 B-25 details allowed combinations of flow classification method, ingress

VLAN editing action and flow VID for flows originating at directly-attached ports.
B-28
VLAN Editing
ETX-5300A Ver. 1.0
Table B-25. Flows Originating at Directly-Attached Port

Untagged
Push X
VLAN X
None
VLAN X
Push Y
VLAN Y
Swap (mark) Y
VLAN Y
None
VLAN X
Pop
VLAN Y
Push Z
VLAN Z
Swap (mark) Z
VLAN Z
VLAN X
Outer VLAN X +
Inner VLAN Y
Table B-26 details allowed combinations of flow classification method, ingress

VLAN editing action and flow VID for flows originating at indirectly-attached
ports.
Table B-26. Flows Originating at Indirectly-Attached Ports (via SAP)

Swap (mark) X
VLAN X
Push X
VLAN X
Outer VLAN X
None
VLAN X
Outer VLAN X +
Inner VLAN Y
Pop
VLAN Y
Match All
Router VLAN Editing

Router-type SVIs are considered to be untagged entities, inheriting their VLAN
properties from attached flows. Table B-27 and Table B-28 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 B-27. VLAN Editing Options at Ingress Router Interface

Type
Action 1
Action 2
CLI Command
Remarks
None
None
Untagged packets only
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.
ETX-5300A Ver. 1.0
VLAN Editing
B-29
Type
Action 1
Action 2
CLI Command
Remarks
Pop (outer)
Pop (inner)
vlan-tag-pop vlan vlantag-pop inner-vlan
Double-tagged packets only. This

action is not available, when a router
port.
Table B-28. VLAN Editing Options at Egress Router Interface

Type
Action 1
Action 2
CLI Command
None
None
Push (set P-bit

and DEI
according to
CoS marking
profile)
None
vlan-tag push vlan

<sp-vlan> p-bit profile
<inner-markingprofile-name>
Push (set P-bit

and DEI
according to
CoS marking
profile)
Push (set Pbit and DEI

according to
CoS marking
profile)
vlan-tag push vlan

<inner-markingprofile-name> inner
vlan <inner-sp-vlan>
p-bit profile <innermarking-profile-name>
Note
Remarks
Tagged packets only. This is the only

allowed action, when a router
port.
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.
The TPID Editing

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 userconfigured. 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 B-29 and Table B-30 detail VLAN editing
B-30
VLAN Editing
ETX-5300A Ver. 1.0
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 B-29. VLAN Editing Options at Ingress PW-Type SVI

Type
Action 1
Action 2
CLI Command
Remarks
None
None
Untagged packets only
Pop (outer)
None
vlan-tag pop vlan
Single-tagged packets only
Pop (outer)
Pop (inner)
vlan-tag-pop vlan vlantag-pop inner-vlan
Double-tagged packets only
Table B-30. VLAN Editing Options at Egress PW-Type SVI

Type
Action 1
Action 2
CLI Command
Remarks
None
None
Push (set P-bit

and DEI according
to CoS marking
profile)
None
vlan-tag push vlan

<inner-marking-profilename>
PtP flows
Push (set P-bit

and DEI according
to CoS marking
profile)
Push (set P-bit

and DEI according
to CoS marking
profile)
vlan-tag push vlan

<inner-marking-profilename> inner vlan <innersp-vlan> p-bit profile
<inner-marking-profilename>
PtP flows
Push (set P-bit to

a fixed value and
DEI=0)
None
vlan-tag push vlan

<sp-vlan> p-bit fixed
<fixed-p-bit>
Multipoint flows
PtP flows
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-5300A supports up to 16
color-aware and color-blind marking profiles:
Note
ETX-5300A Ver. 1.0
The color-aware profile translates CoS (07) and packet color (all, green,
yellow) into P-bit (07) and DEI (yellow, green) values
The color-blind profile translates CoS (07) into P-bit (07) and DEI (yellow,
green 1) values.
If the DEI value is omitted during configuration, it is automatically set to 0.
VLAN Editing
B-31
B.8
Traffic Management
ETX-5300A employs enhanced traffic engineering techniques for efficient

handling of multi-priority traffic on a per-flow basis. It provides pre- and/or
post-forwarding traffic management (TM), using advanced queuing and shaping
mechanisms.
As illustrated in the data flow diagram (Figure B-3), 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.
Overview
ETX-5300A 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 and Type-3 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 tunnels CIR and sharing the remaining port bandwidth
between tunnels 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
bandwidth with the EVCs EIR. The same procedure can be performed for tunnels
at the port level.
Figure B-7 illustrates the hierarchical TM concept and the dual shaper
functionality. The magnified portion of the diagram details functionality of a
level-1 SE.
B-32
Traffic Management
ETX-5300A Ver. 1.0
WFQ 1
WFQ 2
CIR/EIR
Shaper
WFQ 383
SP 1
WFQ 384
WFQ 1
SP 2
WFQ 2
CIR/EIR
Shaper
WFQ 383
WFQ 384
Level-0 SEs
CIR
Shapers
SP 1
SP 2
Level-1 SEs
CIR/EIR
Shaper
WFQ 1
WFQ 2
SP 3
CIR/EIR
Shaper
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 383
WFQ 4
WFQ 384
WFQ 2
CIR
Shaper
CIR
Shapers
WFQ 1
SP 1
SP 2
CIR/EIR
Shaper
WFQ 2
SP 3
CIR/EIR
Shaper
WFQ 63
WFQ 64
SP4
WFQ 1
WFQ 2
WFQ 383
WFQ 3
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 B-7. Traffic Management Hierarchy and Dual Shaper Functionality

ETX-5300A Ver. 1.0
Traffic Management
B-33
For WFQs belonging to the queue groups defined for physical ports (not for
SAGs)
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 packets 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
Packets mapped to queue
according to their CoS
WFQ 1
CIR/EIR
Shapers
SP 2
SP 3
Flow mapped to SE (queue block)
Level-1 SEs
SP 1
WFQ 2
CIR/EIR
Shapers
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 383
WFQ 4
WFQ 384
Up to 384
CIR
Shapers
Up to 384
Up to 64
WFQ 2
CIR
Shaper
Up to 64
WFQ 1
WFQ 2
WFQ 63
SP 1
WFQ 64
SP 2
SP 3
SP4
WFQ 1
WFQ 383
WFQ 2
WFQ 384
WFQ 3
WFQ 4
Figure B-8. Packet Queuing

ETX-5300A 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.
B-34
Traffic Management
ETX-5300A Ver. 1.0
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-5300A 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-5300A 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-5300A
supports up to eight WRED profiles.
Each WRED profile includes the following parameters:
ETX-5300A Ver. 1.0
Minimum threshold: a percentage of maximum queue depth. If a packet is

queued and the queue size is 0 minus the minimum threshold, the packet is
admitted.
Maximum threshold: a percentage of maximum queue depth. If a packet is

queued and the queue size is the minimum threshold minus the maximum
threshold, the packet is dropped at the drop probability of the particular
queue size.
Maximum drop probability: a drop probability of the maximum threshold

queue size, measured in percentages.
Traffic Management
B-35
Drop
Probability
100%
Max Drop
Probability
Min
Threshold
Max
Threshold
100%
Queue
Depth
Figure B-9. WRED Profile
Default WRED Profile

By default, ETX-5300A has one WRED profile with the following settings:
Green packets
Maximum probability 100%
Yellow packets:
Maximum probability 100%.
Traffic Management Entities

ETX-5300A 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-5300A 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.
B-36
Traffic Management
ETX-5300A Ver. 1.0
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.
Type 1 Queue Group

The type 1 queue group is a two-level TM entity with single and dual leaky bucket
shapers. ETX-5300A supports up to 88 type-1 queue group instances per device.
Level-0 SEs
CIR
Shapers
SP 1
SP 2
CIR/EIR
Shapers
SP 3
SP4
WFQ 1
Level-1 SE
WFQ 2
WFQ 1
WFQ 3
CIR
Shaper
WFQ 2
WFQ 4
WFQ 3
Up to 8
CIR
Shapers
Up to 8
WFQ 4
WFQ 5
WFQ 6
SP 1
SP 2
WFQ 7
WFQ 8
SP 3
SP4
WFQ 1
WFQ 2
WFQ 3
WFQ 4
Figure B-10. Type 1 Queue Group

The type 1 queue group consists of:
ETX-5300A Ver. 1.0
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 (163) 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 (163).
Shaping elements:
Single leaky bucket shaper per internal queue in level-0 SE
Dual leaky bucket shaper per level-0 SE queue block
Single leaky bucket shaper at level-1 SE egress.
Traffic Management
B-37
Default Queue Group Profile

By default, ETX-5300A 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-5300A 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-5300A 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).
B-38
Traffic Management
ETX-5300A Ver. 1.0
Type 2 Queue Group

The type 2 queue group is a three-level TM entity with single and dual leaky
bucket shapers. ETX-5300A supports up to 88 type 2 queue group instances per
device.
Level-0 SEs
CIR
Shapers
SP 1
SP 2
Level-1 SEs
CIR/EIR
Shapers
WFQ 1
WFQ 2
CIR/EIR
Shapers
SP 3
SP4
WFQ 1
Level-2 SE
WFQ 2
WFQ 1
WFQ 3
WFQ 383
WFQ 4
WFQ 384
Up to 384
CIR
Shapers
Up to 64
Up to 384
WFQ 2
CIR
Shaper
Up to 64
WFQ 1
WFQ 2
WFQ 63
SP 1
WFQ 64
SP 2
SP 3
SP4
WFQ 1
WFQ 383
WFQ 2
WFQ 384
WFQ 3
WFQ 4

The type 2 queue group consists of:
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 (163) 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 (163).
One level-2 scheduling element consisting of 64 WFQs with each queue userconfigurable to a different weight (14096).
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-5300A rounds it to 4096.
ETX-5300A Ver. 1.0
Traffic Management
B-39
11
21
31
41
51
61
71
87
110
151
240
585
12
22
32
42
52
62
73
89
113
157
256
682
13
23
33
43
53
63
74
91
117
163
273
819
14
24
34
44
54
64
75
93
120
170
292
1024
15
25
35
45
55
65
77
95
124
178
315
1365
16
26
36
46
56
66
78
97
128
186
341
2048
17
27
37
47
57
67
80
99
132
195
372
4096
18
28
38
48
58
68
81
102
136
204
409
19
29
39
49
59
69
83
105
141
215
455
10
20
30
40
50
60
71
85
107
146
227
512
Shaping elements:
Single leaky bucket shaper per internal queue in level-0 SE
Dual leaky bucket shaper per level-0 SE queue block (see Egress Shaping
below)
Dual leaky 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
No shaper profiles.
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
B-40
Traffic Management
ETX-5300A Ver. 1.0

attributes:
No shaper profile.
The default queue block profile can be used as is, or as a basis for a new queue
block (copy, rename, edit), and bound to a queue group.
ETX-5300A supports up to 128 different weight combinations for level-0 queue
block.
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 leaky
bucket shapers. ETX-5300A supports up to four type-3 queue group instances
per main card.
Level-1 SEs
WFQ 1
Level-0 SEs
SP 1
WFQ 2
CIR/EIR
Shapers
CIR/EIR
Shapers
SP 2
Level-2 SE
SP 3
WFQ 1
SP4
WFQ 2
WFQ 383
CIR
Shaper
WFQ 384
Up to 768
Up to 768
Up to 64
Up to 64
WFQ 1
WFQ 63
WFQ 2
SP 1
WFQ 64
SP 2
SP 3
SP4
WFQ 383
WFQ 384

Type 3 queue group consists of:
ETX-5300A Ver. 1.0
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 (163).
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 (14096).
Traffic Management
B-41
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-5300A rounds it to 4096.
11
21
31
41
51
61
71
87
110
151
240
585
12
22
32
42
52
62
73
89
113
157
256
682
13
23
33
43
53
63
74
91
117
163
273
819
14
24
34
44
54
64
75
93
120
170
292
1024
15
25
35
45
55
65
77
95
124
178
315
1365
16
26
36
46
56
66
78
97
128
186
341
2048
17
27
37
47
57
67
80
99
132
195
372
4096
18
28
38
48
58
68
81
102
136
204
409
19
29
39
49
59
69
83
105
141
215
455
10
20
30
40
50
60
71
85
107
146
227
512
Shaping elements:
Dual leaky bucket shaper per level-0 SE queue block (see Egress Shaping
below)
Dual leaky 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
No shaper profiles.
allowed:
B-42

Traffic Management
ETX-5300A Ver. 1.0
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).
No shaper profile.
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).
Egress Shaping
As described above, ETX-5300A provides the following post-forwarding shaping
elements:
Single leaky bucket shaper (CIR/CBS) per each level-0 SE queue
Dual leaky bucket shaper per each level-0 SE queue block
Dual leaky bucket shaper per each level-1 SE queue block
Single leaky bucket shaper per level-2 SE queue block.
In total, ETX-5300A supports up to 256 shaper profiles with the following

configuration ranges:
Note
CIR/EIR: 0, 256 kbps10 Gbps (configured in kbps)
CBS/EBS: 0, 10512 kBytes (configured in bytes).
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.
ETX-5300A Ver. 1.0
Traffic Management
B-43

Level-0 SEs
SP 1
SP 2
SP 3
CIR
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 B-13. 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 (3110) 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 leaky bucket shaper per
each level-0 queue block.
The ingress CIR/CBS shaper has the following configuration ranges:
CIR: 01 Gbps (configured in kbps)
CBS: 064 kBytes (configured in bytes)
Compensation: 063 bytes.

By default, ETX-5300A 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.
No shaper profiles.
allowed:
B-44
Traffic Management
ETX-5300A Ver. 1.0

no flows are attached to it, delete it and bind a new one.

attributes:
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 bind to a queue group.
The default level-1 queue block profile uses queues with default WFQ queue
profile (weight fair queues, weight = 10, no shaper).
Default Queue Profiles

By default, ETX-5300A provides two queue profiles one for strict, and one for
weight fair queue:
ETX-5300A Ver. 1.0
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.
Traffic Management
B-45
B-46
Traffic Management
ETX-5300A Ver. 1.0
Publication No. 570-200-03/13
Order this publication by Catalog No. 805010
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-5300A: Ethernet Service Aggregation Platform

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-5300A: Ethernet Service Aggregation Platform

Uploaded by

Copyright:

Available Formats

INSTALLATION AND

Installation and Operation Manual

North America Headquarters

24 Raoul Wallenberg Street

900 Corporate Drive

20082013 RAD Data Communications Ltd.

Publication No. 570-200-03/13

Installation and Operation Manual

ETX-5300A Ver. 1.0

Installation and Operation Manual

General Safety Instructions

This symbol may appear on the equipment or in the text. It indicates

Protective ground: the marked lug or terminal should be connected to the

Do not attempt to adjust the laser drive current.

Do not use broken or unterminated fiber-optic cables/connectors or look

Use of controls, adjustments or performing procedures other than those

ETX-5300A Ver. 1.0

Installation and Operation Manual

Handling Energized Products

Laite on liitettv suojamaadoituskoskettimilla varustettuun pistorasiaan

Apparatet m tilkoples jordet stikkontakt

Apparaten skall anslutas till jordat uttag

ETX-5300A Ver. 1.0

Installation and Operation Manual

Connecting Data and Telecommunications Cables

V.11, V.28, V.35, V.36, RS-530, X.21,

xDSL (without feeding voltage),

TNV-1 Telecommunication Network Voltage-1:

FXS (Foreign Exchange Subscriber)

TNV-2 Telecommunication Network Voltage-2:

FXO (Foreign Exchange Office), xDSL

TNV-3 Telecommunication Network Voltage-3:

ETX-5300A Ver. 1.0

Safety Extra Low Voltage:

Ports whose normal operating voltage is within the

Ports whose normal operating voltage exceeds the

Installation and Operation Manual

Pour rduire les risques sincendie, utiliser seulement des conducteurs de

Electromagnetic Compatibility (EMC)

ETX-5300A Ver. 1.0

Installation and Operation Manual

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

This is a class A product. In a domestic environment, this product may cause

Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel,

Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In

ETX-5300A Ver. 1.0

Installation and Operation Manual

Mise au rebut du produit

Instructions gnrales de scurit

Danger de choc lectrique ! Evitez tout contact avec la surface marque

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

ETX-5300A Ver. 1.0

Avant la mise en marche de l'quipement, assurez-vous que le cble de

Ne tentez pas d'ajuster le courant de la commande laser.

N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans

L'usage de priphriques optiques avec l'quipement augmentera le

L'usage de contrles, ajustages ou procdures autres que celles

Manipuler des produits sous tension

ETX-5300A Ver. 1.0

Installation and Operation Manual

Installation and Operation Manual