ETX-2i

OPERATION MANUAL
INSTALLATION AND
ETX-2i
IP & Carrier Ethernet Demarcation with
D-NFV
Version 6.4
ETX-2i
Carrier Ethernet Demarcation
Version 6.4
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-2i 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-2i product name is owned by RAD. The ETX-2i product name is owned by RAD. No right,
license, or interest to such trademark is granted hereunder, and you agree that no such right,
license, or interest shall be asserted by you with respect to such trademark. RAD
products/technologies are protected by registered patents. To review specifically which product is
covered by which patent, please see ipr.rad.com. The RAD name, logo, logotype, and the product
names MiNID, Optimux, Airmux, IPmux, and MiCLK are registered trademarks of RAD Data
Communications Ltd. All other trademarks are the property of their respective holders.
You shall not copy, reverse compile or reverse assemble all or any portion of the Manual or the
ETX-2i. 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-2i, based on
or derived in any way from the ETX-2i. Your undertaking in this paragraph shall survive the
termination of this Agreement.
This Agreement is effective upon your opening of the ETX-2i 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-2i and all copies and portions
thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters North American Headquarters

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

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

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

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

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

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

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

The equipment is designed and approved to comply with the electromagnetic regulations of major
regulatory bodies. The following instructions may enhance the performance of the equipment and
will provide better protection against excessive emission and better immunity against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables with the exception of 1000BaseT ports that must always use shielded
twisted pair cables of good quality (CAT 5E or higher). However, the use of shielded wires is always
recommended, especially for high-rate data. In some cases, when unshielded wires are used,
ferrite cores should be installed on certain cables. In such cases, special instructions are provided
in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines is
dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal conversion
loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with plastic
connectors (without a grounded metal hood, such as flat cables) to sensitive data lines. Before
connecting such cables, discharge yourself by touching ground or wear an ESD preventive wrist
strap.
vi ETX-2i
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 B digital apparatus meets all the requirements of the Canadian Interference-Causing
Equipment Regulation.
Cet appareil numrique de la classe B respecte toutes les exigences du Rglement sur le matriel
brouilleur du Canada.
ETX-2i vii
Mise au rebut du produit

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

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

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

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

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

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

Branchez toujours la fiche de secteur une prise murale quipe d'une borne protectrice de mise
la terre.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de court-
circuit dpassant 35A (40A aux Etats-Unis et Canada).
Branchez toujours le cble d'alimentation en premier l'quipement puis la prise murale. Si un
commutateur est fourni avec l'quipement, fixez-le en position OFF. Si le cble d'alimentation ne
peut pas tre facilement dbranch en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est install dans l'installation du btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si le systme de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spcifi dans le manuel, l'entre CC de l'quipement est flottante par
rapport la mise la terre. Tout ple doit tre mis la terre en externe.
A cause de la capacit de courant des systmes alimentation CC, des prcautions devraient tre
prises lors de la connexion de l'alimentation CC pour viter des courts-circuits et des risques
d'incendie.
Assurez-vous que l'alimentation CC est isole de toute source de courant CA (secteur) et que
l'installation est conforme la rglementation locale.
La capacit maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
btiment devrait avoir une capacit leve de rupture et devrait fonctionner sur courant de court-
circuit dpassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des cbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'quipement et fixez-le en
position OFF. Lors de la connexion de cbles d'alimentation CC, connectez d'abord le conducteur
de mise la terre la borne correspondante, puis le ple positif et en dernier, le ple ngatif.
Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapt et approuv devrait tre intgr l'installation du
btiment.
Le disjoncteur devrait dconnecter simultanment les deux ples si l'alimentation en courant CC
est flottante.
x ETX-2i
Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
ANSI American National Standards Institute.
APS (Automatic An automatic service restoration function by which a network

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

devices. Measured in decibels.
Azimuth The horizontal direction from the GPS satellite, measured clockwise
with reference to north as the base direction. For example, a
coordinate due north has an azimuth of 0, one due east has an
azimuth of 90, one due south has an azimuth of 180, etc.
Bandwidth The range of frequencies passing through a given circuit. The

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

conditions or events per second. If each signal event represents
only one bit condition, baud rate equals bps (bits per second).
Best Effort A QoS class in which no specific traffic parameters and no absolute
guarantees are provided.
Bipolar Signaling method in E1/T1 representing a binary 1 by alternating

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

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

data rates or event timing when transmitting from one device to
another. Also used to remove jitter.
Byte A group of bits (normally 8 bits in length).
Carrier A continuous signal at a fixed frequency that is capable of being

modulated with a second (information carrying) signal.
Cell The 53-byte basic information unit within an ATM network. The user
traffic is segmented into cells at the source and reassembled at the
destination. An ATM cell consists of a 5-byte ATM header and a 48-
byte ATM payload, which contains the user data.
ETX-2i xi
Channel A path for electrical transmission between two or more points. Also
called a link, line, circuit or facility.
CLI Command Line Interface (CLI) is a mechanism for interacting with a

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

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

user data (frames, cells or packets).
Data Information represented in digital form, including voice, text,

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

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

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

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

operating at 34 Mbps.
ERP Ethernet Ring Protection. A G.8032 Layer-2 Ethernet ring is a logical

ring that protects against link and node failures.
Ethernet A local area network (LAN) technology which has extended into the
wide area networks. Ethernet operates at many speeds, including
data rates of 10 Mbps (Ethernet), 100 Mbps (Fast Ethernet), 1,000
Mbps (Gigabit Ethernet), 10 Gbps, 40 Gbps, and 100 Gbps.
Ethernet OAM Ethernet operation, administration and maintenance (OAM) are a

set of standardized protocols for measuring and controlling network
performance. There are two layers of Ethernet OAM: Service OAM
(provides end-to-end connectivity fault management per customer
service instance, even in multi-operator networks) and Link or
Segment OAM (detailed monitoring and troubleshooting of an
individual physical or emulated link).
EVC An Ethernet Virtual Connection is an association between two or

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

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

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

encapsulated in a packet, which is encapsulated in the frame.
Full Duplex A circuit or device permitting transmission in two directions

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

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

network. Viewed as a physical entity, a gateway is that node that
translates between two otherwise incompatible networks or
network segments. Gateways perform code and protocol conversion
to facilitate traffic between data highways of differing architecture.
GFP (Generic Framing Defined by ITU-T G.7041, generic framing procedure allows efficient
Procedure) mapping of variable length, higher-layer client signals, such as
Ethernet, over a transport network like SDH/SONET. Recently, GFP
has been extended to lower speed PDH networks.
Interface A shared boundary, defined by common physical interconnection

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

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

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

electromagnetic energy in the visible light spectrum. Used as a light
source for fiber optic transmission (generally more expensive,
shorter lived, single mode only, for greater distances than LED).
Latency The time between initiating a request for data and the beginning of
the actual data transfer. Network latency is the delay introduced
when a packet is momentarily stored, analyzed and then forwarded.
Link The definition of a physical connection on the RV-SC/TDM map
Loading The addition of inductance to a line in order to minimize amplitude

distortion. Used commonly on public telephone lines to improve
voice quality, it can make the lines impassable to high speed data,
and baseband modems.
Logical MAC A concept used to describe and map the Ethernet traffic passing over
different media (E1/T1, SDH/SONET, etc). Logical MAC represents the
MAC layer of the entity. It should be bound to a GFP, HDLC or MLPPP
port, which, in its turn, should be bound to the physical layer.
Loopback A type of diagnostic test in which the transmitted signal is returned

to the sending device after passing through all or part of a
communications link or network.
MA (Maintenance See MEG (Maintenance Entity Group).
ETX-2i xiii
Association)
ME (Maintenance An ME is a maintenance entity as defined by ITU-T Y.1731 that

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

Entity Group Ethernet path. It can respond to OAM messages, but cannot
Intermediate Point) originate them.
Manager An application that receives Simple Network Management Protocol

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

is equivalent to a binary 1. A mark is the opposite of a space (0).
Master Clock The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Metering This feature is intended for support of payphones, and therefore

includes dedicated circuits for the detection of polarity and of 16
kHz or 12 kHz metering pulses.
Multiplexer At one end of a communications link, a device that combines

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

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

network, as a subset of a larger message.
Parameters Parameters are often called arguments, and the two words are used
interchangeably. However, some computer languages such as C
define argument to mean actual parameter (i.e., the value), and
parameter to mean formal parameter. In RAD CLI, parameter means
formal parameter, not value.
xiv ETX-2i
Path A service defined over network links is referred to as path in RV-

SC/TDM.
Payload The 48-byte segment of the ATM cell containing user data. Any
adaptation of user data via the AAL will take place within the
payload.
Physical Layer Layer 1 of the OSI model. The layer concerned with electrical,
mechanical, and handshaking procedures over the interface
connecting a device to the transmission medium.
Policing A method for verifying that the incoming VC complies with the
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.
RADIUS (Remote An authentication, authorization and accounting protocol for

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

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

conditions. For example, a scalable network can be expanded from a
few nodes to thousands of nodes.
SNR Signal to Noise Ratio is the ratio of signal strength to the level of
background noise, usually expressed in decibels (dB)
SONET (Synchronous A North American standard for using optical media as the physical
Optical Network) transport for high speed long-haul networks. SONET basic speeds
start at 51.84 Mbps and go up to 2.5 Gbps.
ETX-2i xv
Space In telecommunications, the absence of a signal. Equivalent to a

binary 0.
SSH (Secure Shell) A network protocol that allows data to be exchanged over a secure
channel between two computers. Encryption provides confidentiality
and integrity of data.
Sync See Synchronous Transmission.
T1 A digital transmission link with a capacity of 1.544 Mbps used in

North America. Typically channelized into 24 DS0s, each capable of
carrying a single voice conversation or data stream. Uses two pairs
of twisted pair wires.
T3 A digital transmission link with a capacity of 45 Mbps, or 28 T1

lines.
Telnet The virtual terminal protocol in the Internet suite of protocols. It

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

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

single channel. In E1 and T1, one timeslot typically represents one
64 kbps channel.
Traffic Shaping A method for smoothing the bursty traffic rate that might arrive on
an access virtual circuit so as to present a more uniform traffic rate
on the network.
Trunk A single circuit between two points, both of which are switching
centers or individual distribution points. A trunk usually handles
many channels simultaneously.
TWAMP Two-Way Active Measurement Protocol. Mechanism for measuring

metrics between network elements by sending test packets from
generators to responders.
Zero suppression Technique used to ensure a minimum density of marks.
xvi ETX-2i
EU Declaration of Conformity
Manufacturer's Name: RAD Data Communications Ltd.
Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 6971920, Israel
declares under its sole responsibility that the product:
Product Name: ETX-2i
Product Options: All options (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative document(s) in

accordance with the relevant European Union harmonization legislation:
EMC EN 55032: 2012+ Electromagnetic Compatibility of multimedia equipment Emissions

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

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

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

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

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

Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
ETX-2i xvii
Product Name: ETX-2i-B
Product Options: All options (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative document(s) in

accordance with the relevant European Union harmonization legislation:
EMC EN 55032: 2012+ Electromagnetic Compatibility of multimedia equipment Emissions

AC/2013 requirements.

EN 61000-4-
2/3/4/5/6/11)
EN 61000-3-2:2014 Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic

current emissions (equipment input current 16A per phase)

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.

A12:2011, A2:2013
Supplementary Information: The product herewith complies with the requirements of the EMC Directive
2014/30/EU, the Low Voltage Directive 2014/35/EU and the ROHS Directive
2011/65/EU.
Zohar Zosmanovich

xviii ETX-2i
Product Name: ETX-2i-B
Product Options: ETX-2i-B/WR (may be followed by several suffixes separated by slashes)
conforms to the following standard(s) or other normative document(s) in accordance

with the relevant European Union harmonization legislation:
EMC EN Electromagnetic Compatibility of multimedia equipment Emissions requirements.

55032:2012+AC/2013
EN 55022:2010 Information technology equipment; Radio disturbance characteristics; Limits and

methods of measurement.

EN 61000-4-
2/3/4/5/6/11)
EN 61000-3-2:2014 Electromagnetic compatibility (EMC); Section 3-2: Limits for harmonic current
emissions (equipment input current 16A per phase)

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.

A12:2011, A2:2013
Supplementary Information: The product herewith complies with the requirements of the EMC Directive
2014/30/EU, the Low Voltage Directive 2014/35/EU and the ROHS Directive
2011/65/EU.
Zohar Zosmanovich

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

Perform the following steps to install the unit:
1. Determine the required configuration of ETX-2i according to your application.
2. Connect the ASCII terminal to the CONTROL port.
3. Connect power to the unit.
Connecting to Terminal
To connect the unit to a terminal:
1. Connect the male mini USB connector of the mini USB terminal cable to the
units 5-pin female connector, designated CONTROL.
2. Connect the other end of the mini USB terminal cable to the ASCII terminal
equipment.
Connecting to Power
Regular units are available with single or dual AC or DC power supply, depending
on the ordering option. There is also a dual DC inlet option for the
8.5 enclosure; the dual DC inlet is a single DC power supply, with two DC inlets
for redundancy at the DC source level. The ETX-2i-B branch-office device is
offered with a wide-range power supply.
AC/DC plugs or terminal block connectors are available for DC power supplies.
Before connecting or disconnecting any cable, the protective ground terminals of

this unit must be connected to the protective ground conductor of the mains (AC
or DC) power cord. If you are using an extension cord (power cable) make sure it
Warning is grounded as well.
Any interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting of the protective ground terminal can make this unit
dangerous. Intentional interruption is prohibited.
Connecting to AC Power
For indoor installations, a standard K.21 power cable is supplied to provide AC
power to the unit.
ETX-2i Installing the Unit 1

Quick Start Guide Installation and Operation Manual
For connection to unprotected AC power networks, devices that do not have

built-in AC surge protection are provided with an Enhanced AC power cable per
ITU-T K.21E enhanced mode.
To connect to AC power:
1. Connect the relevant AC power cable to the power connector on ETX-2i.
2. Connect the power cable to the mains outlet.
The unit turns on automatically once connected to the mains.
Connecting to DC Power
For indoor installations, a standard K.21 power cable is supplied to provide AC
power to the unit.
All DC options support NEBS level 3 on port type 8b (DC inlet).
To connect to DC power:
1. Connect the standard power cable to the power connector on ETX-2i.
The unit turns on automatically once connected to the mains.
Refer to the relevant DC Power Supply Connection section at the end of Chapter
2 in this manual for instructions on wiring the DC connection.
2. Configuring the Unit for Management

Configure ETX-2i 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-2i cables and connectors are properly connected.
2. Connect ETX-2i to a PC equipped with an ASCII terminal emulation application.
Refer to the Installation and Setup chapter for details on connecting to the
control port.
3. Start the PC terminal emulation program and create a new terminal
connection.
4. Configure the PC communication port parameters to a baud rate of 9.6 kbps,
8 bits/character, 1 stop bit, no parity and no flow control.
5. Power-up the unit.
The boot manager of ETX-2i starts, and displays a message that you can
stop the auto-boot and enter the boot manager by pressing any key. A
running countdown of the number of seconds remaining until auto-boot
is displayed. If it reaches 0 before you press a key, then after a few
2 Configuring the Unit for Management ETX-2i

Installation and Operation Manual Quick Start Guide
seconds a message is displayed showing that the active software pack is

being loaded.
After a few more seconds, the login prompt is displayed.
6. Log in with your user name (default: su for full configuration and monitoring
access) and password (default: 1234).
The device prompt appears:
ETX-2i#
7. Type the necessary CLI commands.
8. Continue with product configuration.
Configuring Management Flows

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

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

Quick Start Guide Installation and Operation Manual
flow mng_out
classifier all
ingress-port svi 1
egress-port ethernet 101 queue 0 block 0/1
no shutdown
exit all
#*********************Configuring_Router_Interface***************************
configure router 1
interface 1
bind svi 1
address 172.18.141.39/24
no shutdown
exit
static-route 172.17.0.0/16 address 172.18.141.1
exit all
save
3. Saving Management Configuration
Saving Configuration
Type save in any level to save your configuration in startup-config.
Copying User Configuration to Default Configuration

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

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

Contents
Chapter 1. Introduction
1.1 Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-2
ETX2i ........................................................................................................................... 1-2
ETX-2i-B ........................................................................................................................ 1-3
ETX-2i-10G .................................................................................................................... 1-3
Router Options .................................................................................................................. 1-4
Timing Options .................................................................................................................. 1-4
Applications ....................................................................................................................... 1-4
Ethernet Demarcation for Retail and Wholesale Services............................................... 1-4
Mobile Demarcation Device for Mobile Backhauling Applications ................................... 1-5
Features ............................................................................................................................ 1-6
Traffic Processing .......................................................................................................... 1-6
Resiliency and Optimization .......................................................................................... 1-8
Timing and Synchronization .......................................................................................... 1-8
Integrated x86 Processor and Distributed Network Functions Virtualization (D-NFV)..... 1-9
Management and Security ........................................................................................... 1-10
Monitoring and Diagnostics ......................................................................................... 1-11
1.2 New in This Version ............................................................................................................ 1-13
1.3 Physical Description ........................................................................................................... 1-13
1.4 Functional Description ........................................................................................................ 1-14
1.5 Technical Specifications...................................................................................................... 1-16
Chapter 2. Installation and Setup

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

2.18 Connecting to a Network Management Station .................................................................. 2-26
2.19 Basic Connectivity Tests ..................................................................................................... 2-26
Chapter 3. Operation and Maintenance

3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-1
ETX2i ................................................................................................................................ 3-1
ETX-2i-B ............................................................................................................................. 3-2
ETX-2i-10G ........................................................................................................................ 3-4
3.3 Startup ................................................................................................................................. 3-5
Applicable Products............................................................................................................ 3-5
Configuration and Software Files ....................................................................................... 3-5
Loading Sequence .............................................................................................................. 3-6
3.4 Working with Custom Configuration Files ............................................................................. 3-6
Saving Configuration Changes ............................................................................................ 3-7
Zero Touch......................................................................................................................... 3-7
Show Me Demo ............................................................................................................. 3-8
Zero Touch via DHCP/DHCPv6 ........................................................................................ 3-8
Zero Touch via Trap ..................................................................................................... 3-12
3.5 Configuration and Management ......................................................................................... 3-12
3.6 CLI-Based Configuration ..................................................................................................... 3-13
Working with Terminal ..................................................................................................... 3-13
Accessing a Remote Terminal ...................................................................................... 3-16
Working with Telnet and SSH ........................................................................................... 3-16
Adding a Telnet Client Session .................................................................................... 3-17
Login ............................................................................................................................... 3-19
Changing Password ..................................................................................................... 3-20
Lost Superuser Password ............................................................................................ 3-20
Using the CLI .................................................................................................................... 3-20
CLI Prompt .................................................................................................................. 3-20
Navigating ................................................................................................................... 3-21
Command Tree ............................................................................................................ 3-22
Command Structure .................................................................................................... 3-23
Special Keys ................................................................................................................ 3-23
Getting Help ................................................................................................................ 3-24
Scheduling CLI Commands ........................................................................................... 3-30
Viewing the Device Configuration ................................................................................ 3-34
Refreshing Output ...................................................................................................... 3-34
Filtering Output ........................................................................................................... 3-35
Enabling Entities.......................................................................................................... 3-37
Using Scripts .................................................................................................................... 3-37
Examples ......................................................................................................................... 3-38
3.7 Management Access Methods ............................................................................................ 3-38
Applicable Products.......................................................................................................... 3-39
Functional Description ..................................................................................................... 3-39
Factory Defaults .............................................................................................................. 3-39
Configuring Management Access...................................................................................... 3-40
3.8 Resetting Unit to Default ................................................................................................... 3-41
3.9 Turning Off the Unit ........................................................................................................... 3-41
3.10 SNMP-Based Network Management ................................................................................... 3-41
ii ETX-2i
Installation and Operation Manual Table of Contents
Standards ........................................................................................................................ 3-41

Benefits ........................................................................................................................... 3-42
Configuring SNMPv3 Parameters ...................................................................................... 3-43
Examples ......................................................................................................................... 3-51
Preconfiguring ETX2i for SNMP Management .................................................................. 3-55
Working with RADview ..................................................................................................... 3-57
Overview ..................................................................................................................... 3-57
Preconfiguration for Service Discovery ........................................................................ 3-57
Working with Shelf View .................................................................................................. 3-58
Working with Third-Party Network Management Systems ................................................ 3-58
Chapter 4. Service Provisioning

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

5.1 Cards.................................................................................................................................... 5-1
Benefits ............................................................................................................................. 5-1
Functional Description ....................................................................................................... 5-1
Factory Defaults ................................................................................................................ 5-1
Configuring Module ............................................................................................................ 5-2
5.2 Ethertype ............................................................................................................................. 5-2
Standards .......................................................................................................................... 5-3
Benefits ............................................................................................................................. 5-3
Configuring Ethertype ........................................................................................................ 5-4
Example ............................................................................................................................. 5-4
Configuration Errors ........................................................................................................... 5-4
ETX-2i iii
5.3 GFP Ports ............................................................................................................................. 5-5

Standards .......................................................................................................................... 5-5
Benefits ............................................................................................................................. 5-5
Configuring GFP Ports ........................................................................................................ 5-6
Examples ........................................................................................................................... 5-7
5.4 Internal Ports for x86 Interconnection.................................................................................. 5-8
Benefits ............................................................................................................................. 5-8
Configuring the Internal Port Parameters ........................................................................... 5-9
5.5 Logical MAC Ports ................................................................................................................. 5-9
Benefits ............................................................................................................................. 5-9
Configuring Logical MAC ports .......................................................................................... 5-10
Examples ......................................................................................................................... 5-13
5.6 PCS Ports ........................................................................................................................... 5-13
Standards ........................................................................................................................ 5-13
Benefits ........................................................................................................................... 5-13
Configuring the PCS Port Parameters ............................................................................... 5-14
Viewing PCS Port Statistics ............................................................................................... 5-16
5.7 Peers .................................................................................................................................. 5-18
Configuring Peers............................................................................................................. 5-18
5.8 Service Virtual Interfaces .................................................................................................... 5-18
Benefits ........................................................................................................................... 5-18
Configuring Service Virtual Interfaces ............................................................................... 5-18
5.9 VCGs .................................................................................................................................. 5-19
Standards ........................................................................................................................ 5-19
Benefits ........................................................................................................................... 5-19
Configuring VCG Ports ...................................................................................................... 5-20
Examples ......................................................................................................................... 5-21
5.10 DS1 (E1/T1) Ports .............................................................................................................. 5-22
Benefits ........................................................................................................................... 5-22
Configuring E1/T1 Ports ................................................................................................... 5-22
5.11 E1 Ports ............................................................................................................................. 5-23
Standards ........................................................................................................................ 5-23
Benefits ........................................................................................................................... 5-23
Configuring E1 Ports ........................................................................................................ 5-24
Configuring Built-in E1 Ports ....................................................................................... 5-24
iv ETX-2i
Configuring Modular E1 Ports ...................................................................................... 5-27

Configuring Smart SFP E1 Ports ................................................................................... 5-29
5.12 E3 Ports ............................................................................................................................. 5-32
Standards ........................................................................................................................ 5-32
Benefits ........................................................................................................................... 5-32
Configuring E3 Ports ........................................................................................................ 5-33
5.13 Ethernet Ports .................................................................................................................... 5-35
Options ....................................................................................................................... 5-35
Numbering .................................................................................................................. 5-35
MAC Addresses ........................................................................................................... 5-38
Ethertype .................................................................................................................... 5-38
Fat Pipe Detection and Rate Limiting .......................................................................... 5-38
Silent Start .................................................................................................................. 5-38
Configuring Ethernet Port Parameters .............................................................................. 5-41
Setting Functional Mode to Network or User Port ............................................................ 5-46
Viewing Ethernet Port Status ........................................................................................... 5-47
Testing Ethernet Ports ..................................................................................................... 5-48
Example ...................................................................................................................... 5-49
Viewing Ethernet Port Statistics ....................................................................................... 5-49
Setting Sampling Interval for Port Statistics ................................................................ 5-49
Displaying Port Statistics ............................................................................................. 5-49
Example ...................................................................................................................... 5-50
Displaying Fat Pipe Information ................................................................................... 5-52
Example ...................................................................................................................... 5-52
Displaying Layer-2 Control Processing Statistics .......................................................... 5-53
Example ...................................................................................................................... 5-54
Clearing Statistics ........................................................................................................ 5-54
Viewing Ethernet Port Data Rate and Line Rate ............................................................... 5-54
Example ...................................................................................................................... 5-55
5.14 SDH/SONET Ports ............................................................................................................... 5-55
Standards ........................................................................................................................ 5-55
Benefits ........................................................................................................................... 5-55
Configuring SDH/SONET Ports .......................................................................................... 5-56
5.15 SHDSL Ports ....................................................................................................................... 5-57
Standards ........................................................................................................................ 5-58
Benefits ........................................................................................................................... 5-58
Configuring the SHDSL Port Parameters ........................................................................... 5-58
Viewing SHDSL Port Status............................................................................................... 5-58
Example ........................................................................................................................... 5-59
5.16 VDSL2 Ports ....................................................................................................................... 5-59
Standards ........................................................................................................................ 5-59
Benefits ........................................................................................................................... 5-59
Configuring the VDSL2 Port Parameters ........................................................................... 5-60
Viewing VDSL2 Port Status ............................................................................................... 5-61
ETX-2i v
Viewing VDSL2 Port Statistics........................................................................................... 5-62

Example ...................................................................................................................... 5-62
5.17 T1 Ports ............................................................................................................................. 5-63
Standards ........................................................................................................................ 5-63
Benefits ........................................................................................................................... 5-63
Configuring T1 Ports ........................................................................................................ 5-64
Configuring Built-in T1 Ports ....................................................................................... 5-64
Configuring Modular T1 Ports ...................................................................................... 5-67
Configuring Smart SFP T1 Ports ................................................................................... 5-69
5.18 T3 Ports ............................................................................................................................. 5-71
Standards ........................................................................................................................ 5-72
Benefits ........................................................................................................................... 5-72
Configuring T3 Ports ........................................................................................................ 5-72
Configuring Modular T3 Ports ...................................................................................... 5-72
Configuring Smart SFP T3 Ports ................................................................................... 5-74
5.19 SFPs ................................................................................................................................... 5-76
5.20 Smart SFPs ......................................................................................................................... 5-76
Benefits ........................................................................................................................... 5-76
Configuring Smart SFPs .................................................................................................... 5-77
Examples ......................................................................................................................... 5-78
Chapter 6. Management and Security

6.1 Access Control List (ACL) ...................................................................................................... 6-1
Standards .......................................................................................................................... 6-1
Benefits ............................................................................................................................. 6-1
Binding Access Control Lists .......................................................................................... 6-2
Filtering and Marking ..................................................................................................... 6-2
Show Me Demo ............................................................................................................. 6-3
Statistics ....................................................................................................................... 6-3
Configuring ACL ................................................................................................................. 6-4
Access-Control-Level Tasks ........................................................................................... 6-4
Router-Level Tasks ........................................................................................................ 6-6
Management-Level Tasks .............................................................................................. 6-7
Examples ....................................................................................................................... 6-8
Configuration Errors .................................................................................................... 6-10
Displaying Status......................................................................................................... 6-10
Displaying Statistics .................................................................................................... 6-11
6.2 GUI-Based Configuration .................................................................................................... 6-12
Preconfiguring ETX2i for SNMP Management .................................................................. 6-12
Working with RADview ..................................................................................................... 6-13
Overview ..................................................................................................................... 6-13
Preconfiguration for Service Discovery ........................................................................ 6-13
Working with Shelf View .................................................................................................. 6-14
Working with Third-Party Network Management Systems ................................................ 6-14
vi ETX-2i
6.3 Access Policy ...................................................................................................................... 6-15

Configuring Access Policy ................................................................................................. 6-15
6.4 Authentication via RADIUS Server ....................................................................................... 6-16
Standards ........................................................................................................................ 6-16
Benefits ........................................................................................................................... 6-17
Configuring RADIUS Parameters ....................................................................................... 6-18
Viewing RADIUS Statistics ................................................................................................ 6-19
6.5 Authentication via TACACS+ Server..................................................................................... 6-20
Standards ........................................................................................................................ 6-20
Benefits ........................................................................................................................... 6-20
Components................................................................................................................ 6-21
Accounting .................................................................................................................. 6-22
Mapping Privilege Levels .............................................................................................. 6-22
Configuring TACACS+ Server ............................................................................................. 6-23
Configuring Accounting Groups ........................................................................................ 6-24
Mapping CLI Levels to TACACS+ Privilege Levels................................................................ 6-24
Example Defining Server ............................................................................................... 6-24
Example Defining Accounting Group .............................................................................. 6-25
Example Mapping CLI Level to Privilege Level ................................................................. 6-26
Configuration Errors ......................................................................................................... 6-26
Viewing TACACS+ Statistics .............................................................................................. 6-26
6.6 Control Port ....................................................................................................................... 6-27
Configuring Control Port Parameters ................................................................................ 6-27
6.7 DHCP Relay ........................................................................................................................ 6-28
Standards ........................................................................................................................ 6-28
Benefits ........................................................................................................................... 6-29
DHCP Messages ........................................................................................................... 6-29
DHCP Snooping ........................................................................................................... 6-30
DHCP Option 82 .......................................................................................................... 6-30
Configuring DHCP Relay ................................................................................................... 6-31
System Parameters ..................................................................................................... 6-31
6.8 DHCP Server ....................................................................................................................... 6-33
Standards ........................................................................................................................ 6-33
Benefits ........................................................................................................................... 6-33
DHCP Options ............................................................................................................. 6-35
Manual Bindings .......................................................................................................... 6-35
DHCP Lease Offer Message ......................................................................................... 6-36
Configuring DHCP Server .................................................................................................. 6-37
Configuring DHCP Server Pool ..................................................................................... 6-39
ETX-2i vii
Viewing DHCP Server Binding....................................................................................... 6-43

Viewing DHCP Server Conflict ...................................................................................... 6-44
Viewing DHCP Server Statistics .................................................................................... 6-45
6.9 NETCONF/YANG Management ............................................................................................. 6-47
Standards ........................................................................................................................ 6-47
Benefits ........................................................................................................................... 6-48
Configuring NETCONF Parameters .................................................................................... 6-49
Examples ......................................................................................................................... 6-49
6.10 Point-to-Point Protocol over Ethernet (PPPoE) ................................................................... 6-49
Standards ........................................................................................................................ 6-49
Benefits ........................................................................................................................... 6-50
Discovery .................................................................................................................... 6-50
PPP Session ................................................................................................................. 6-50
Configuring PPPoE and PPP Entities ............................................................................. 6-51
Configuring PPP Port ........................................................................................................ 6-52
Example ........................................................................................................................... 6-53
Viewing PPP and PPPoE Status ......................................................................................... 6-54
6.11 SNMP Management ............................................................................................................ 6-55
Standards ........................................................................................................................ 6-56
Benefits ........................................................................................................................... 6-56
Configuring SNMPv3 Parameters ...................................................................................... 6-57
Examples ......................................................................................................................... 6-65
6.12 User Access ........................................................................................................................ 6-69
Password Hashing ....................................................................................................... 6-70
SSH Authentication ..................................................................................................... 6-70
Configuring Users ............................................................................................................ 6-70
Example Defining Users ............................................................................................ 6-71
Example Displaying Users ......................................................................................... 6-73
Viewing User Information ................................................................................................. 6-73
Viewing SSH Server Information ....................................................................................... 6-73
Chapter 7. Resiliency and Optimization

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

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

Benefits ........................................................................................................................... 7-46
Configuring Link Protection .............................................................................................. 7-47
Example ........................................................................................................................... 7-48
Chapter 8. Traffic Processing

8.1 Bridge .................................................................................................................................. 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-2
Admission to Bridge ...................................................................................................... 8-3
Packet Editing on Reverse Flows ................................................................................... 8-3
L2PT Over Bridge ........................................................................................................... 8-4
Management via Bridge ................................................................................................. 8-5
Spanning Tree Protocol ................................................................................................. 8-5
Configuring the Bridge ....................................................................................................... 8-9
Configuring Bridge Ports ............................................................................................. 8-11
Configuring VLAN ........................................................................................................ 8-11
Configuring RSTP/MSTP ............................................................................................... 8-12
Examples ......................................................................................................................... 8-18
VLAN-Aware Bridge ..................................................................................................... 8-18
Displaying VLAN Information ....................................................................................... 8-20
VLAN-Unaware Bridge ................................................................................................. 8-21
Creating Static MAC Address ....................................................................................... 8-22
Displaying MAC Table .................................................................................................. 8-22
8.2 Classification by Port/Flow ................................................................................................. 8-23
Standards ........................................................................................................................ 8-24
Benefits ........................................................................................................................... 8-24
Flow Classification ....................................................................................................... 8-24
Port Classification ....................................................................................................... 8-35
Ethertype .................................................................................................................... 8-36
Configuring a Classifier Profile ......................................................................................... 8-36
Configuring Flows ............................................................................................................ 8-37
Configuring Port Classification ......................................................................................... 8-44
Examples ......................................................................................................................... 8-45
Classifier Profiles ......................................................................................................... 8-45
Traffic Flows ............................................................................................................... 8-46
ETP Flows .................................................................................................................... 8-47
Unidirectional Hub....................................................................................................... 8-47
Multi-CoS Flow ............................................................................................................ 8-49
Testing Flows and Flow Diagnostics Loopback ................................................................. 8-52
Use Case 1 Application Layer Loopback .................................................................... 8-52
Example ...................................................................................................................... 8-53
Method 2 Flow Diagnostics Loopback ...................................................................... 8-54
Example Flow Diagnostics Loop ................................................................................ 8-54
Viewing Flow Statistics ..................................................................................................... 8-55
x ETX-2i
Examples ..................................................................................................................... 8-55

Viewing Flow Status ......................................................................................................... 8-59
Example ...................................................................................................................... 8-59
Viewing Flow Data Rate and Line Rate ............................................................................. 8-59
Example ........................................................................................................................... 8-60
8.3 Distributed Network Functions Virtualization (D-NFV) ........................................................ 8-60
Overview .......................................................................................................................... 8-60
D-NFV Module ............................................................................................................. 8-61
Benefits ........................................................................................................................... 8-62
D-NFV Module ............................................................................................................. 8-62
ETX2i Device .............................................................................................................. 8-62
Application Management ............................................................................................. 8-63
Configuring Service Function Chain (SFC) for D-NFV ......................................................... 8-64
Configuring Compute Node .............................................................................................. 8-64
Accessing the x86 Terminal ......................................................................................... 8-65
Configuring Compute Node Parameters ....................................................................... 8-65
Setting the OpenStack Networking Mechanism Driver ................................................. 8-66
Configuring Fault Propagation ..................................................................................... 8-67
Viewing Compute Node Information ............................................................................ 8-69
Rebooting/Shutting Down Compute Node ................................................................... 8-69
Resetting/Waking the D-NFV Module ........................................................................... 8-69
Exiting the x86 Terminal .............................................................................................. 8-69
Examples ..................................................................................................................... 8-70
Configuring Controller ...................................................................................................... 8-73
Controller Installation .................................................................................................. 8-73
Logging into Controller ................................................................................................ 8-76
Configuring Controller Parameters ............................................................................... 8-76
Controller Verification ................................................................................................. 8-77
Viewing Controller Information .................................................................................... 8-77
Examples ..................................................................................................................... 8-77
Maintenance .................................................................................................................... 8-78
Upgrade ...................................................................................................................... 8-78
Backup ........................................................................................................................ 8-80
Restore ....................................................................................................................... 8-81
Examples ..................................................................................................................... 8-83
8.4 Ethernet over GRE (ETHoGRE) Tunnel ................................................................................. 8-83
Standards ........................................................................................................................ 8-84
Benefits ........................................................................................................................... 8-84
ETHoIP/GRE Encapsulation ........................................................................................... 8-84
Forwarding Model ....................................................................................................... 8-86
Configuring GRE Tunneling ............................................................................................... 8-87
Deleting a GRE Tunnel ...................................................................................................... 8-89
Viewing GRE Status .......................................................................................................... 8-89
Examples ......................................................................................................................... 8-92
GRE-ETH Tunnels at Router ......................................................................................... 8-92
OAM above GRE Tunnel ............................................................................................... 8-93
8.5 Fat Pipe Detection and Rate Limiting ................................................................................. 8-94
ETX-2i xi
Standards ........................................................................................................................ 8-95

Benefits ........................................................................................................................... 8-95
Configuring Fat Pipe Detection ........................................................................................ 8-96
Deleting a Fat pipe Detection Profile ............................................................................... 8-97
Example ........................................................................................................................... 8-97
8.6 Layer-2 Control Processing ................................................................................................. 8-97
Standards ........................................................................................................................ 8-98
Benefits ........................................................................................................................... 8-98
Configuring Layer 2 Control Processing ............................................................................ 8-98
Adding Layer 2 Control Processing Profiles .................................................................. 8-98
Deleting Layer 2 Control Processing Profiles ............................................................... 8-99
Configuring Layer 2 Control Processing Profile Parameters .......................................... 8-99
Examples ....................................................................................................................... 8-101
8.7 Link Layer Discovery Protocol (LLDP) ................................................................................ 8-103
Applicable Products........................................................................................................ 8-103
Standards ...................................................................................................................... 8-103
Benefits ......................................................................................................................... 8-103
Functional Description ................................................................................................... 8-103
LLDP Bridge Types ..................................................................................................... 8-103
LLDP Packets ............................................................................................................. 8-104
Factory Defaults ............................................................................................................ 8-106
Configuring LLDP............................................................................................................ 8-106
System Parameters ................................................................................................... 8-106
Port Parameters ........................................................................................................ 8-106
Example ......................................................................................................................... 8-108
Viewing LLDP Neighbor Information ............................................................................... 8-109
8.8 MLDv2 Snooping .............................................................................................................. 8-110
Standards ...................................................................................................................... 8-110
Benefits ......................................................................................................................... 8-111
MAC-based Forwarding Addresses............................................................................. 8-112
Port Aging ................................................................................................................. 8-113
Source-Specific Multicast .......................................................................................... 8-114
MLD Snooping and Ethernet Ring Protection ............................................................. 8-114
Configuring MLD Snooping ............................................................................................. 8-114
Displaying MLD Snooping Status .................................................................................... 8-115
8.9 Pseudowire Connections .................................................................................................. 8-116
Standards ...................................................................................................................... 8-117
Pseudowire Packet Structure ..................................................................................... 8-117
TDM Service Encapsulation ........................................................................................ 8-117
Encapsulation over Different PSN Types .................................................................... 8-119
Jitter Buffer ............................................................................................................... 8-119
Configuring Pseudowire Bundles .................................................................................... 8-120
Adding Pseudowire Bundles ...................................................................................... 8-121
xii ETX-2i
Configuring Pseudowire Bundle Parameters .............................................................. 8-122

Deleting Pseudowire Bundles .................................................................................... 8-125
Viewing Pseudowire Configuration ................................................................................. 8-125
Viewing PW Statistics ..................................................................................................... 8-126
Viewing PW Connectivity Statistics ................................................................................. 8-127
Examples ....................................................................................................................... 8-128
8.10 PW Cross Connects........................................................................................................... 8-130
Configuring PW Cross Connects...................................................................................... 8-131
Examples ....................................................................................................................... 8-131
8.11 Router .............................................................................................................................. 8-132
Standards ...................................................................................................................... 8-132
Benefits ......................................................................................................................... 8-132
Overview ................................................................................................................... 8-133
Embedded Router ..................................................................................................... 8-133
Routing Preferences .................................................................................................. 8-134
Router Interface Forwarding ..................................................................................... 8-135
DHCPv6 Option Request ............................................................................................ 8-135
DHCP Relay ............................................................................................................... 8-135
Network Address Translator (NAT) ............................................................................ 8-136
Configuring the Router .................................................................................................. 8-140
Configuring Router Interfaces ................................................................................... 8-143
Configuring Network Address Translator (NAT) ......................................................... 8-146
Configuring the Management Source IP Address ....................................................... 8-148
Deleting a Router ...................................................................................................... 8-148
Deleting a Router Interface ....................................................................................... 8-149
Viewing Router Interface Information ............................................................................ 8-149
Viewing IPv6 Neighbors .................................................................................................. 8-150
Viewing Routing Information .......................................................................................... 8-151
Viewing RIB .................................................................................................................... 8-152
Viewing Router Interface Status..................................................................................... 8-153
Viewing NAT Translation Table ....................................................................................... 8-155
Viewing NAT Statistics ................................................................................................... 8-156
Configuration Errors ....................................................................................................... 8-157
8.12 Routing Protocol BGP ....................................................................................................... 8-161
Standards and MIBs ....................................................................................................... 8-161
Benefits ......................................................................................................................... 8-161
Show Me Demo ......................................................................................................... 8-161
Dynamic Routing Protocols ....................................................................................... 8-162
BGP: Path-Vector Routing .......................................................................................... 8-162
BGP Neighbors .......................................................................................................... 8-162
AS-Internal Destination Injection ............................................................................... 8-163
AS Numbers (ASN) .................................................................................................... 8-163
Limiting Received Routes .......................................................................................... 8-163
BGP Session Timers ................................................................................................... 8-163
BGP Path Attributes .................................................................................................. 8-164
BGP Policies............................................................................................................... 8-164
Maintained Information ............................................................................................. 8-165
ETX-2i xiii

Router....................................................................................................................... 8-166
IPv4 and IPv6 Unicast Address Family ........................................................................ 8-166
Neighbor ................................................................................................................... 8-166
Configuring BGP ............................................................................................................. 8-167
Configuring BGP at Router Level ................................................................................ 8-168
Configuring BGP Neighbors........................................................................................ 8-169
Configuring IPv4/IPv6 Unicast Address Families ......................................................... 8-170
Configuring BGP Policy Profiles .................................................................................. 8-172
Configuration Example ................................................................................................... 8-177
Viewing BGP Status ........................................................................................................ 8-181
Viewing the Current Configuration ............................................................................ 8-181
Viewing Neighbor Connection Status ......................................................................... 8-182
Viewing Received Routes........................................................................................... 8-182
Viewing Advertised Routes ........................................................................................ 8-183
Viewing BGP Policy Profiles ........................................................................................ 8-184
Viewing BGP Communities ......................................................................................... 8-186
Viewing BGP RIB ........................................................................................................ 8-187
Viewing BGP Summary ............................................................................................... 8-188
Testing BGP ................................................................................................................... 8-189
8.13 Routing Protocol OSPF ..................................................................................................... 8-190
Benefits ......................................................................................................................... 8-190
Show Me Demo ......................................................................................................... 8-191
Dynamic Routing Protocols ....................................................................................... 8-191
Link-State Routing .................................................................................................... 8-191
OSPF Network Architecture ....................................................................................... 8-192
AS-External Information ............................................................................................ 8-192
Link-State Summarization ......................................................................................... 8-193
Designated Routers .................................................................................................. 8-193
Authentication .......................................................................................................... 8-193
Explicit Range Aggregation ........................................................................................ 8-193
Maintained Information ............................................................................................. 8-193
Parameters and Factory Defaults ................................................................................... 8-194
Router OSPF Parameters ........................................................................................... 8-194
Area OSPF Parameters .............................................................................................. 8-194
Interface OSPF Parameters ........................................................................................ 8-195
Configuring OSPF ........................................................................................................... 8-196
Configuring OSPF at the Router Level ........................................................................ 8-197
Configuring OSPF at the Area Level ........................................................................... 8-199
Configuring OSPF at the Interface Level .................................................................... 8-200
Configuration Example ................................................................................................... 8-201
Viewing OSPF Status ...................................................................................................... 8-204
Viewing the Current Configuration ............................................................................ 8-204
Viewing the Link-State Database ............................................................................... 8-204
Viewing OSPF Interface States .................................................................................. 8-205
Viewing OSPF Neighbors ........................................................................................... 8-206
Viewing OSPF Statistics .................................................................................................. 8-207
Testing OSPF.................................................................................................................. 8-207
8.14 Routing Protocol VRRP ..................................................................................................... 8-208
xiv ETX-2i

Benefits ......................................................................................................................... 8-208
VRRP Group ............................................................................................................... 8-208
Master Router ........................................................................................................... 8-209
Preemption ............................................................................................................... 8-209
Fault Propagation ...................................................................................................... 8-209
Load Balancing .......................................................................................................... 8-209
Configuring VRRP ........................................................................................................... 8-210
Configuring VRRP Version .......................................................................................... 8-210
Configuring VRRP Group Parameters ......................................................................... 8-210
Viewing VRRP Status ...................................................................................................... 8-212
Viewing VRRP Summary .................................................................................................. 8-213
Chapter 9. Timing and Synchronization

9.1 1588v2 Timing ..................................................................................................................... 9-1
Standards .......................................................................................................................... 9-1
Benefits ............................................................................................................................. 9-2
PTP Protocols ................................................................................................................ 9-2
1588v2 Entities ............................................................................................................. 9-2
PTP Port ........................................................................................................................ 9-2
Slave Clock .................................................................................................................... 9-3
Boundary Clock ............................................................................................................. 9-3
Forwarding .................................................................................................................... 9-4
Configuring PTP Ports ........................................................................................................ 9-5
Configuring the Slave Clock ................................................................................................ 9-5
Configuring the Master Clock ............................................................................................. 9-8
Viewing Clock Recovery Metrics.......................................................................................... 9-9
Examples ......................................................................................................................... 9-11
Configuring Slave Clock ............................................................................................... 9-11
Configuring Boundary Clock ......................................................................................... 9-16
Configuring Master Clock ............................................................................................. 9-24
Viewing Current Metrics .............................................................................................. 9-26
Viewing Metrics for Selected Interval ........................................................................... 9-28
9.2 Clock Selection ................................................................................................................... 9-29
Standards ........................................................................................................................ 9-29
Benefits ........................................................................................................................... 9-29
Clock Domain ................................................................................................................... 9-30
Factory Defaults .......................................................................................................... 9-31
Configuring the Clock Domain ..................................................................................... 9-31
Clock Sources ................................................................................................................... 9-33
Configuring the Clock Sources ..................................................................................... 9-34
Viewing Clock Source Statistics.................................................................................... 9-35
Configuring the Station Clock ........................................................................................... 9-36
Examples ......................................................................................................................... 9-37
ETX-2i xv
9.3 Date and Time.................................................................................................................... 9-38

Standards and MIBs ......................................................................................................... 9-38
Benefits ........................................................................................................................... 9-38
Setting the Date and Time ............................................................................................... 9-39
Viewing the Date and Time .............................................................................................. 9-40
Working with SNTP........................................................................................................... 9-40
Configuring SNTP Parameters ...................................................................................... 9-40
Defining SNTP Servers ................................................................................................. 9-41
Configuring SNTP Server Parameters ........................................................................... 9-41
Working with NTP ............................................................................................................ 9-42
Configuring NTP Parameters ........................................................................................ 9-42
Defining NTP Servers ................................................................................................... 9-42
Configuring NTP Server Parameters ............................................................................. 9-43
Examples ......................................................................................................................... 9-43
Setting Date and Time ................................................................................................ 9-43
Defining SNTP Server .................................................................................................. 9-43
Viewing SNTP Server Information ................................................................................ 9-44
Defining NTP Server .................................................................................................... 9-44
9.4 Daylight Saving Time .......................................................................................................... 9-45
Configuring Daylight Saving Time Scheduling.................................................................... 9-46
Viewing Scheduling Information ....................................................................................... 9-46
Examples ......................................................................................................................... 9-46
Chapter 10. Administration

10.1 Confirming Startup Configuration ....................................................................................... 10-1
Configuring Startup Configuration Confirmation............................................................... 10-1
10.2 CPU and Memory Utilization ............................................................................................... 10-2
Viewing CPU Utilization .................................................................................................... 10-2
Viewing Memory Pool Utilization ...................................................................................... 10-2
10.3 Device Information ............................................................................................................. 10-3
Standards ........................................................................................................................ 10-3
Configuring Parameters ................................................................................................... 10-3
Example ........................................................................................................................... 10-4
10.4 Environment ....................................................................................................................... 10-4
Device Temperature .................................................................................................... 10-4
Device Fan .................................................................................................................. 10-5
Configuring the Temperature Threshold ........................................................................... 10-5
Viewing Environment Information .................................................................................... 10-5
Examples ......................................................................................................................... 10-6
10.5 File Operations ................................................................................................................... 10-6
Using SFTP or TFTP........................................................................................................... 10-7
SFTP Application .......................................................................................................... 10-7
xvi ETX-2i
TFTP Application .......................................................................................................... 10-7

Copying Files .................................................................................................................... 10-8
Examples ..................................................................................................................... 10-9
Viewing Copy Status ...................................................................................................... 10-10
Viewing Information on Files .......................................................................................... 10-10
Example .................................................................................................................... 10-11
Example .................................................................................................................... 10-12
Example .................................................................................................................... 10-13
Deleting Files ................................................................................................................. 10-13
Example .................................................................................................................... 10-14
10.6 Inventory.......................................................................................................................... 10-14
Standards ...................................................................................................................... 10-14
Benefits ......................................................................................................................... 10-14
Viewing Inventory Information ....................................................................................... 10-14
Setting Administrative Inventory Information ................................................................. 10-16
Examples ....................................................................................................................... 10-17
10.7 Licensing .......................................................................................................................... 10-19
Benefits ......................................................................................................................... 10-20
Fault Propagation Event Manager License ................................................................. 10-20
SFP+ 10GbE Rate License .......................................................................................... 10-20
Configuring Licenses ...................................................................................................... 10-21
Viewing License Status Summary ................................................................................... 10-22
Example ......................................................................................................................... 10-22
10.8 Login Banner .................................................................................................................... 10-23
Defining Login Banners .................................................................................................. 10-23
Defining Login Banners via CLI Commands ................................................................ 10-24
Defining Pre-Login Banner Using a Banner File .......................................................... 10-25
10.9 Reset ............................................................................................................................... 10-26
Resetting to Factory Defaults ........................................................................................ 10-26
Resetting to User Defaults ............................................................................................. 10-27
Restarting the Unit ........................................................................................................ 10-28
Resetting the x86 Card .................................................................................................. 10-28
10.10 Tech-Support Commands .......................................................................................... 10-29
Benefits ......................................................................................................................... 10-29
Showing the Tech-Support Commands........................................................................... 10-30
Chapter 11. Monitoring and Diagnostics

11.1 In-Service ICMP Echo Ping Test ........................................................................................... 11-1
Benefits ........................................................................................................................... 11-2
PtP E-line Service ........................................................................................................ 11-2
MP to MP E-LAN (bridge) Services ............................................................................... 11-3
ETX-2i xvii
MP to MP (or P to MP) E-Tree Services ........................................................................ 11-3

Configuring the In-Service ICMP Echo Ping Test ................................................................ 11-3
Configuring In-Service ICMP Echo Ping Response ......................................................... 11-4
Configuring In-Service ICMP Echo Ping Request ........................................................... 11-4
In-Service ICMP Echo Ping Test Results ........................................................................ 11-6
Examples ......................................................................................................................... 11-6
11.2 OAM CFM (Connectivity Fault Management) ....................................................................... 11-9
Standards ........................................................................................................................ 11-9
Benefits ........................................................................................................................... 11-9
OAM Elements........................................................................................................... 11-10
OAM Performance Monitoring ................................................................................... 11-11
OAM Packet Handling ................................................................................................ 11-12
Automatic SLM and LMM Responders ........................................................................ 11-14
MEF46 Latching Loopback ......................................................................................... 11-15
Configuring OAM CFM .................................................................................................... 11-17
Configuring General Parameters ................................................................................ 11-17
Configuring Maintenance Domains ............................................................................ 11-19
Configuring Maintenance Associations ...................................................................... 11-20
Configuring Maintenance Endpoints .......................................................................... 11-22
Viewing MEF46 Latching Loopback Status ................................................................. 11-26
Configuring Maintenance Intermediate Points ........................................................... 11-27
Configuring Maintenance Endpoint Services .............................................................. 11-28
Configuring Destination NEs ...................................................................................... 11-30
Configuring OAM CFM Service Event Reporting .......................................................... 11-33
Viewing OAM CFM Statistics ...................................................................................... 11-35
Performing OAM Loopback ............................................................................................. 11-41
Performing OAM Link Trace ............................................................................................ 11-41
Examples ....................................................................................................................... 11-42
Configuring MD, MA, and MEP ................................................................................... 11-42
Configuring Service for Discovery .............................................................................. 11-43
Viewing MEP Status and Remote MEP ........................................................................ 11-44
Configuring Service and Destination NE ..................................................................... 11-45
Configuring Service Event Reporting .......................................................................... 11-46
Viewing Running Statistics ........................................................................................ 11-48
Viewing Current Statistics.......................................................................................... 11-49
Viewing Interval Statistics.......................................................................................... 11-50
Configuring and Viewing Delay Measurement Bins..................................................... 11-53
11.3 OAM EFM.......................................................................................................................... 11-61
Standards ...................................................................................................................... 11-62
Benefits ......................................................................................................................... 11-62
Configuring OAM EFM .................................................................................................... 11-63
Examples ....................................................................................................................... 11-64
11.4 TWAMP ............................................................................................................................. 11-64
Standards ...................................................................................................................... 11-65
Benefits ......................................................................................................................... 11-65
xviii ETX-2i

TWAMP Tests ............................................................................................................ 11-67
Configuring TWAMP ........................................................................................................ 11-71
Configuring Controllers .............................................................................................. 11-72
Running Test Sessions Via Controller Peers ............................................................... 11-73
Configuring Test Profiles ........................................................................................... 11-76
Configuring Responders ............................................................................................ 11-77
Viewing TWAMP Status................................................................................................... 11-78
Viewing TWAMP Reports ................................................................................................ 11-78
Examples ....................................................................................................................... 11-81
Example Configuring TWAMP in Layer-2 E-Line Service Mode .................................. 11-81
Example Configuring TWAMP in Layer-2 E-LAN Service Mode .................................. 11-84
Example Configuring TWAMP in Layer-3 Mode ........................................................ 11-88
Example Viewing TWAMP Status ............................................................................. 11-91
Example Viewing TWAMP Reports ........................................................................... 11-92
11.5 Quality of Service (QoS) ................................................................................................... 11-97
Standards ...................................................................................................................... 11-98
Benefits ......................................................................................................................... 11-98
Traffic Management .................................................................................................. 11-98
Scheduling ................................................................................................................ 11-98
Queue Mapping Profiles ................................................................................................. 11-99
Factory Defaults ...................................................................................................... 11-100
Adding Queue Mapping Profiles............................................................................... 11-101
Configuring Queue Mappings .................................................................................. 11-101
Examples ................................................................................................................. 11-102
CoS Mapping Profiles ................................................................................................... 11-103
Configuring CoS Mapping Profiles ............................................................................ 11-104
Examples ................................................................................................................. 11-105
Color Mapping Profiles ................................................................................................. 11-105
Configuring Color Mapping Profiles .......................................................................... 11-106
Example .................................................................................................................. 11-106
Marking Profiles ........................................................................................................... 11-106
Configuring Marking Profiles .................................................................................... 11-107
Bandwidth Profiles ....................................................................................................... 11-108
Envelope Bandwidth Profiles ................................................................................... 11-110
Configuring Granularity Rounding ............................................................................ 11-112
Configuring Shaper Profiles ..................................................................................... 11-112
Configuring Policer Profiles...................................................................................... 11-114
Configuring Policer Aggregates ................................................................................ 11-117
Configuring Envelope Profiles .................................................................................. 11-119
Queue Block Profiles .................................................................................................... 11-120
Adding Queue Block Profiles.................................................................................... 11-121
Configuring Queue Block Profile Parameters............................................................ 11-121
Examples ................................................................................................................. 11-122
Queue Group Profiles ................................................................................................... 11-123
ETX-2i xix

Adding Queue Group Profiles .................................................................................. 11-124
Configuring Queue Group Parameters ..................................................................... 11-124
Examples ................................................................................................................. 11-124
WRED Profiles .............................................................................................................. 11-125
Applicable Products ................................................................................................. 11-125
Functional Description............................................................................................. 11-125
Configuring WRED Profiles ....................................................................................... 11-126
Example .................................................................................................................. 11-127
11.6 Layer-3 Service Activation Test ...................................................................................... 11-127
Standards .................................................................................................................... 11-127
Benefits ....................................................................................................................... 11-127
Functional Description ................................................................................................. 11-129
Test Phases ............................................................................................................. 11-129
Test Elements ......................................................................................................... 11-131
Configuring L3 SAT Entities .......................................................................................... 11-132
Configuring Generators ........................................................................................... 11-133
Configuring Peers .................................................................................................... 11-134
Configuring Peer Profiles ......................................................................................... 11-134
Configuring Session Profiles .................................................................................... 11-136
Configuring Responders .......................................................................................... 11-136
Viewing L3 SAT Test Status .......................................................................................... 11-137
Viewing L3 SAT Test Reports ........................................................................................ 11-138
Examples ..................................................................................................................... 11-145
11.7 RFC-2544 Testing ........................................................................................................... 11-151
Applicable Products...................................................................................................... 11-151
Standards .................................................................................................................... 11-151
Benefits ....................................................................................................................... 11-151
Performing Tests ......................................................................................................... 11-153
Examples ..................................................................................................................... 11-156
Running RFC-2544 Test ........................................................................................... 11-156
Viewing Test Report ................................................................................................ 11-157
Viewing Test Status ................................................................................................. 11-161
Viewing Lost Frames Per Test Attempt .................................................................... 11-162
Viewing Test Results ............................................................................................... 11-162
11.8 Syslog ............................................................................................................................ 11-163
Standards .................................................................................................................... 11-163
Benefits ....................................................................................................................... 11-163
Elements ................................................................................................................. 11-163
Transport Protocol .................................................................................................. 11-164
Message Format...................................................................................................... 11-164
Facilities and Severities ........................................................................................... 11-164
Configuring Syslog Parameters ..................................................................................... 11-165
Viewing Syslog Statistics .............................................................................................. 11-166
Clearing Syslog Statistics.............................................................................................. 11-166
Configuration Errors ..................................................................................................... 11-167
Example ....................................................................................................................... 11-167
xx ETX-2i
11.9 Y.1564 Ethernet Service Activation Test ......................................................................... 11-167

Standards .................................................................................................................... 11-168
Benefits ....................................................................................................................... 11-168
SLAs ........................................................................................................................ 11-169
Policing ................................................................................................................... 11-169
Blocking User Traffic ............................................................................................... 11-169
Y.1564 over LAG ..................................................................................................... 11-169
Y.1564 Standard ..................................................................................................... 11-170
Test Elements ......................................................................................................... 11-172
Capacity .................................................................................................................. 11-173
Test Cases............................................................................................................... 11-173
Operation Internal MEP Case ................................................................................ 11-173
Operation Service MEP Case ................................................................................. 11-175
Running Test on MEP with No Configured Services .................................................. 11-178
Test Procedures ...................................................................................................... 11-178
Configuring Y.1564 Test .............................................................................................. 11-183
Adding Y.1564 Test Profile ...................................................................................... 11-183
Adding Y.1564 Responder ....................................................................................... 11-188
Viewing Test Status (Responder Side) ..................................................................... 11-190
Adding Y.1564 Generator ........................................................................................ 11-191
Viewing MEF46 Latching Loopback Generator Status............................................... 11-194
Viewing Test Status (Generator Side) ...................................................................... 11-195
Viewing Test Results ............................................................................................... 11-197
Examples ..................................................................................................................... 11-203
11.10 Port Mirroring .......................................................................................................... 11-209
Standards .................................................................................................................... 11-210
Benefits ....................................................................................................................... 11-210
Configuring Port Mirroring ............................................................................................ 11-210
Examples ..................................................................................................................... 11-212
11.11 Performance Management ...................................................................................... 11-212
Benefits ....................................................................................................................... 11-213
Configuring Performance Management ........................................................................ 11-215
Viewing Performance Management Configuration ........................................................ 11-217
Examples ..................................................................................................................... 11-218
11.12 Detecting Problems ................................................................................................. 11-219
LEDs ............................................................................................................................ 11-219
Alarms and Traps ......................................................................................................... 11-219
Statistic Counters ........................................................................................................ 11-220
11.13 Handling Alarms and Events .................................................................................... 11-220
Alarm Soaking .............................................................................................................. 11-221
Configuring Alarm and Event Properties ....................................................................... 11-222
Controlling Popup Behavior .......................................................................................... 11-225
ETX-2i xxi
Working with Alarm and Event Logs ............................................................................. 11-226

Alarms and Events ....................................................................................................... 11-227
11.14 Troubleshooting ...................................................................................................... 11-228
11.15 Performing Diagnostic Tests.................................................................................... 11-230
Running a Ping Test ..................................................................................................... 11-230
Example .................................................................................................................. 11-231
Tracing the Route ........................................................................................................ 11-231
11.16 Frequently Asked Questions .................................................................................... 11-231
11.17 Technical Support.................................................................................................... 11-231
Chapter 12. Software Upgrade

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

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

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

Chapter 1 Introduction Installation and Operation Manual
L3 SAT generators and analyzers for service-oriented SLA validation and service
birth certificate reports.
Furthermore, incorporating RADs SyncToP platform of synchronization and timing
over packet feature set, ETX2i utilizes standard technologies such as
IEEE 1588v2 transparent clock (TC), slave clock, and boundary clock, as well as
synchronous Ethernet to ensure highly accurate timing delivery in packet-based
mobile backhaul networks.
With the D-NFV optional module, ETX2i can host virtual machines providing
virtual network functions (VFs), or value added service capabilities. This enables
service providers to quickly and easily provide new services and implement new
network capabilities, with the benefit of function localization at the customer
premises.
Product Options
Several product options of the unit are available, offering different combinations
of ports, enclosures, and functionalities. Available product options in the ETX2i
family are ETX2i, ETX-2i-B, and ETX-2i-10G. The following SW licenses are
available:
FE Provides Fast Ethernet of 100 Mbps (default)
GE Stronger than FE (default SW license option); 1 Gbps per

port; also provides Ethernet service
ETX2i
ETX2i is available with the following options:
Four or eight fixed Ethernet SFP/copper combo ports, available in 19 or
8.5 enclosure
Modular option, in 19 or 8.5 enclosure, available with the following port
types:
GbE two SFP/copper combo ports.
SHDSL two or four ports
VDSL bonding four ports (eight-wire)
EoPDH:
Four or eight E1/T1 ports
One or two T3 ports
USB port (for future use)
D-NFV slot for x86 module, available in 19 enclosure
D-NFV option:
Network ports up to two SFP/copper combo ports. Port 2 can be
configured as a network or user port.
1-2 Overview ETX2i

Installation and Operation Manual Chapter 1 Introduction
User ports up to two SFP/copper combo ports, or up to three if

port 2 is configured as a user port. An additional user port appears
on the panel but is not usable.
Internal x86 card and hard drive
No E1/T1 ports or timing options
Single AC power supply
NEBS-compliant enclosures and SyncE/PTP options are available (with ports
specified in Timing Options). The device has an AC or DC power supply.
ETX-2i-B
The ETX-2i-B device has up to ten 1GbE interfaces in an 8.5 metal enclosure,
and is available in the following options:
Network ports two 1GbE SFP
User ports two 1GbE SFP/copper combo ports, four 1Gbe copper UTP ports,
four SFP ports, or eight SFP ports (2U hardened option)
Single AC, Dual DC inlet, or wide-range AC/DC with auto detection
No E1/T1 ports, AIO modules (SHDSL, VDSL), or timing options
USB port (for future use)
D-NFV slot that serves virtualization.
ETX-2i-B can be ordered with SyncE/PTP options, in which case the device
provides the ports specified in Timing Options.
ETX-2i-10G
The ETX-2i-10G device supports up to four 10GbE interfaces and eight 1GbE
interfaces in a half 8.5 or full 19 metal enclosure, and is available in the
following options:
10GbE interface two or four (provided license is activated) SFP+ (1/10 GbE)
ports with the following characteristics:
Autonegotiation and max capability relevant for 1GbE SFP+ only
DDM support
Flow control supported for Rx only
1GbE interface four to 24 SFP and UTP ports:
Eight 1GbE SFP ports
Four 1GbE SFP and four 1GbE UTP ports
12 1GbE SFP and 12 1GbE UTP ports (full 19 only)
USB port
Supports timing
No AIO modules (SHDSL, VDSL) or x86 module
Single AC, dual AC, or dual DC power supply
ETX2i Overview 1-3

Dual AC or DC inlet
No GNNS receiver or router
Router Options
ETX2i and ETX-2i-B are offered with two software licenses per ordering option:
Dynamic Router:
L-3 HW forwarding
Supports OSPF and BGP routing protocols
Static Router:
Same as Dynamic Router, but routing protocols are not supported.
A change to Dynamic Router from Static Router software license is supported;
however, a change to Static Router from Dynamic Router software license is
supported only when the device is set to default.
Timing Options
If ETX2i, ETX-2i-B, or ETX-2i-10G are ordered with the timing option (PTP), the
following features are supported:
Clock selection mechanism to select and distribute the device system clock,
including the holdover mechanism
SyncE
1588 slave
1588 BC
In this option, the device also provides these additional timing ports:
Station clock port (RJ-45)
ToD/1PPS RS-422 port (RJ-45)
SMA port supplying external clock
SMA port supplying 1 pps
Applications
Ethernet Demarcation for Retail and Wholesale Services

ETX2i can function as an Ethernet demarcation device, separating the service
provider network, the access provider network, and the customer network.
Figure 1-1 illustrates a complete access solution with full service visibility. ETX2i,
placed at connection points in the network, greatly contributes to monitoring and
troubleshooting the network, using its enhanced Ethernet OAM and performance
monitoring capabilities.
1-4 Overview ETX2i

Core Services Metro/Core Access Aggregation Access Network First Mile
Internet
FE/GbE
Access
Management MiNID
1/10 GbE
ETX-2/2i
Cell-Site
ETX-5 PDH/
Cloud/Data Center SDH
SDH/
SONET ETX-2/2i
10 GbE
IP/MPLS
Ring
ETX-5 ETX-5 GbE DSL

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

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

Mobile Network Transport Network Mobile Network

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

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

G.8032 v2
1/10 GbE
ETX-2/2i Ring Node B
ETX-2/2i TDM
BTS
ETX-2/2i
Timing (1588PTP/SyncE)
Figure 1-2. Mobile Demarcation Device
Features
Traffic Processing
ETX2i incorporates a complete set of CE 2.0-certified Ethernet service tools that
allow the service provider to distinguish between high- and low-priority traffic,
and to optimize TCP sessions.
Forwarding
Traffic forwarding is performed via point-to-point, bridge, or L3 forwarding
(router) mechanisms.
The ETX2i bridge operates in VLAN-aware or VLAN-unaware mode.
The ingress user traffic is mapped to Ethernet flows using flexible per-port
classification criteria. VLAN editing can be performed on the flows such as
overwriting the VLAN, adding a new VLAN (push), or removing a VLAN (pop).
TDM Pseudowire
Note This feature is applicable to devices that support smart SFP MiTOP functionality.
Devices that have integrated MiTOPs allow TDM over packet pseudowire services.
Each TDM pseudowire (PW) carries a single bundle (group of timeslots) to a
predefined far-end bundle.
The following standard payload encapsulation methods are supported:
CESoPSN (with or CES (Circuit Emulation Services) over PSN, for framed
without CAS) traffic, according to IETF RFC 5086
1-6 Overview ETX2i

SAToP Structure-Agnostic TDM over Packet, for unframed traffic,

according to IETF RFC 4553
The pseudowire connections can be encapsulated by the device for the following
types of PSN transport networks:
MEF 8 (Ethernet)
UDP over IP
Fat Pipe Detection and Rate Limiting

The Fat pipe mechanism detects high bandwidth sessions going over limited
bandwidth paths, thus allowing the operator to rate limit these sessions. This
reduces congestion and drops for all traffic going over these paths.
Ethernet over GRE (ETHoGRE) Tunnel

ETX2i and ETX-2i-B devices with an embedded router support Ethernet over GRE
(ETHoGRE), a Layer-2 tunneling technology that allows transport of Layer-2
frames and services over an IP/MPLS network using IP/GRE encapsulation.
Layer-2 Control Processing (L2CP)

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

LLDP packets are sent periodically between ETX2i and neighboring devices on
the same physical LAN, advertising information about itself and obtaining
neighbor information. This automated discovery of devices simplifies
management and network maintenance, reducing general setup costs of new
equipment.
MLDv2 Snooping
ETX2i IPv6 routers support Multicast Listener Discovery Version 2 (MLDv2)
protocol to discover multicast listeners on attached links and addresses that are
of interest to them. Bridges use MLDv2 Snooping to reduce multicast traffic by
analyzing MLDv2 messages and limiting multicast traffic to ports interested in it.
Routing
ETX2i and ETX-2i-B support a high-performance, dual-stack, IPv4/IPv6 embedded
router. The embedded router is supported with routing protocols (OSPFv2 and
BGPv4 license ordering options), as well as BFD for fast forwarding path failure
detection, IPv4/IPv6 ACLs, and VRRPv2/v3.
Device management, as well as other L3 modules, such as 1588 (8265.1), TDM
PW (UDP/IP), and TWAMP, use the ETX2i routing scheme.
When the dynamic router or TWAMP license is enabled, ETX2i supports multiple
VRFs (up to 10); management is supported over VRF1 only.
ETX2i Overview 1-7

Resiliency and Optimization

ETX2i provides the following to ensure five nines (99.999%) availability and
sub-50 ms restoration in the event of network outages:
Link redundancy in a LAG architecture that supports the LACP protocol
according to 802.3-2005
LAG delivery of link protection and link redundancy between two network
ports or two user ports
Dual homing technology in a 1:1 architecture allows ETX2i to be connected
to two different upstream devices
Ethernet protection switching in the following modes for network ports per
ITU-T G.8031:
1:1 bidirectional with APS protocol Endpoints negotiate using APS
protocol.
1:1 unidirectional without APS protocol Endpoints act independently
and do not negotiate with each other. Unidirectional mode is suitable for
EVC level dual homing applications.
Ethernet Ring Protection per G.8032v2 Layer-2 to protect against link and
node failures. This supports ring topology, and delivers low-cost traffic
protection and rapid service restoration, with SDH/SONET type resilience.
Fault Propagation
The ETX2i fault propagation mechanism enables propagating user port failures to
the network and the remote end, as well as propagating network failures back to
the user port. The mechanism has a set of triggers and actions that are based on
the physical layer (e.g. port failure), ETH OAM (AIS, RDI, LOC, etc.), or VRRP
group.
A Traffic Management Fault Propagation (TMFP) license can be enabled to provide
the Fault Propagation mechanism with a set of triggers and actions for queue
block shaper and flow policer (Event Manager).
The additional fault propagation actions are:
Change policer rate
Change shaper rate
Configuration of these actions enables you to implement network/application
level redundancy schemes while controlling the bandwidth of the different
redundant paths.
Timing and Synchronization
Note This section is relevant only when ETX2i, ETX-2i-B, or ETX-2i-10G are ordered
with the appropriate timing options.
The units SyncToP suite includes clock recovery using IEEE 1588v2 Precision
Timing Protocol, Synchronous Ethernet (SyncE), and a built-in input/output clock
interface.
1-8 Overview ETX2i

The ETX2i domain (system) clock is selected from up to two user-configurable

sources. Each source can be an Ethernet port (recovered SyncE clock), the station
clock, or the recovered 1588v2 clock (i.e. 1588v2 slave clock; relevant only for
devices without GNSS).
The clock selection mechanism (CSM) selects the best clock according to its
quality level (by SSM) and configured priority. The selected domain clock and its
quality level are distributed to all Ethernet ports (Tx SyncE and SSM) and is the
reference clock for the 1588v2 master.
A dedicated IEEE 1588v2 clock recovery module allows ETX2i to recover the clock
from a remote 1588v2 master clock. Furthermore, ETX2i supports a 1588v2
master clock that can function in a boundary clock application.
The Network Time Protocol (NTP) provides the means of synchronizing all
managed elements across the network to a reliable clock source provided by
multiple servers. ETX2i supports the client side of NTP v.3 (RFC 1305).
Integrated x86 Processor and Distributed Network Functions

Virtualization (D-NFV)
Note This section is relevant only for ETX2i and ETX-2i-B.
ETX2i can be ordered with an integrated Intel x86 core, as follows:

Intel i7 for ETX2i
ETX-2i-B
In an ETX-2i-B x86-enabled device, the x86 Rangeley card is supported as an
optional drawer; hot insertion of the x86 module is not supported.
The available x86 module ordering options are described in the following table.
Table 1-1. x86 Module Ordering Options
Device Processor Cores Hard Drive RAM
ETX-2i-B Intel Atom 4@2.4GHz SSD M2.0/2.5 8 GByte

Rangeley format
C2558 128 GByte
With or without
PLP
Intel Atom 8@2.4GHz SSD M2.0/2.5 8 GByte

Rangeley format
C2758 128 GByte
With or without
PLP
ETX2i Intel Core 4@2.4GHz SSD 4/8/16

i7-4700EQ 128 GByte GByte
The Intel x86 core can work in the following operation mode:
D-NFV general infrastructure x86 processor with a cloud computing
software platform that enables hosting virtual machines providing virtual
ETX2i Overview 1-9

network functions (VFs). This option provides rapid deployment and

upgrading of network and service functionalities, and enables you to flexibly
locate network functionality wherever it is most effective and/or least
expensive.
The ETX2i NID and x86 card are interconnected via internal Ethernet ports 7 and
8; you configure flows over these ports in order to route data to the x86 card.
The D-NFV option is not available with the following:
Timing options
NEBS-compliant enclosure
Power supply redundancy
Temperature-hardened option
Management and Security

ETX2i access control lists (ACLs) are used to flexibly filter and mark incoming and
management traffic.
ETX2i can be managed as follows:
Local management via ASCII terminal, connected to the V.24/RS-232 DCE
control port
Local management via dedicated out-of-band management port
Remote management via an Ethernet port using Telnet, SSH, NETCONF, or
RADview, RADs SNMP-based management system
Remote management using Point-to-Point Protocol over Ethernet (PPPoE) -
establishes a management channel that a remote management system can
use to send software and configuration files and manage ETX2i.
ETX2i supports a variety of access protocols including CLI over Telnet, SNMP,
NETCONF, and TFTP/SFTP. You can create databases and scripts of commonly
used commands and easily apply them to multiple units in your infrastructure.
To ensure client-server communication privacy and correct user authentication,
ETX2i supports the security protocols listed below:
SNMPv3 (provides secure access to the device by authenticating and
encrypting packets transmitted over the network)
RADIUS (client authentication)
TACACS+ (client authentication)
SSH for Secure Shell communication session
The ETX2i DHCP client enables plug-and-play zero touch provisioning via
standard TFTP functionality. This includes downloading the latest SW version and
configuration files.
1-10 Overview ETX2i

Smart SFPs
ETX2i provides integrated management for RADs smart SFP devices, allowing
TDM over packet pseudowire services (using MiTOP devices), and Ethernet over
TDM (using MiRICi devices). The following devices are supported:
MiRICi-E1/T1/E3/T3
MiRICi-155
MiTOP-E1/T1/E3/T3
Monitoring and Diagnostics

ETX2i offers several types of diagnostic procedures:
Ping test checks IP connectivity by pinging remote IP hosts
In-service ICMP Echo ping test checks the connectivity across Layer-2
service paths
Trace route quickly traces a route from ETX2i to any other network device
Loopback tests:
Layer-1 loopback performed at the PHY of the physical ports. When the
loopback is active, the data forwarded to a port is looped from the Tx
path to the Rx path, disrupting the traffic. This loopback cannot pass
through Ethernet bridges.
Layer-2/Layer-3 loopback on flows, with optional MAC and/or IP address
swapping. When the loopback is active, ETX2i can exchange the source
and destination MAC/IP addresses of the incoming packets. This loopback
passes through Ethernet bridges and routers, and does not disrupt traffic
flows that are not being tested.
Service activation tests:
RFC-2544 traffic generator and analyzer
L3 SAT for Layer-3 testing
ITU-T Y.1564 traffic generator and analyzer for Layer-2 testing
Syslog protocol that generates and transports event notification messages
from the device to servers across IP networks
Port mirroring duplicates port traffic to a single destination port, where a
traffic analyzer receives, records, and analyzes the traffic.
Hardware-Based Ethernet OAM and Performance Monitoring

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

Quality of Service (H-QoS)

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

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

1.2 New in This Version

The following features have been added for Version 6.4:
Enhanced ETP statistics
Continuous ping (device with router)
PW support for DSCP configuration
HW based GRE Tunneling for L2 services (ETX2i and ETX-2i-B with router)
New ETX-2i-10G ordering options
ETX-2i-10G 10GbE speed license
1.3 Physical Description

The following figure shows the ETX2i devices:
Top row ETX-2i-10G (half 19)
Middle row ETX-2i-B branch office device
Bottom row ETX2i
Figure 1-3. ETX2i

The following figure shows the ETX-2i-10G device with four SFP+, 12 SFP, 12 UTP,
PTP, and two DC power supplies.
ETX2i Physical Description 1-13

Figure 1-4. ETX-2i-10G Full 19 with four SFP+, 12 SFP, 12 UTP, PTP, and two DC PS
Refer to the Installation and Setup chapter for a detailed description of the
ETX2i interface connections.
1.4 Functional Description

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

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

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

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

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

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

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

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

1.5 Technical Specifications
Ethernet Interfaces Number of Ports Eight on-board combo ports (fixed port ordering
(ETX2i) option)
Four on-board combo ports (modular and D-NFV
options)
Type SFP/copper combo

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

Specifications and
Ranges
Electrical Operation 10/100/1000 Mbps

Mode
Connector SFP slot or RJ-45
Modular GbE Number of Ports Two

(ETX2i)
Type SFP/copper combo


Specifications and
Ranges
Electrical Operation 10/100 Mbps or 10/100/1000 Mbps

Mode
Connector RJ-45 or SFP
Modular EoPDH Number of Ports Four or eight

E1/T1 Interface,
Compliance G.703, G.823, G.704, G.7041, G.8040, G.7043,
E1 mode
G.7042
(ETX2i)
Framing Framed (G.732N with CRC)
Data Rate 2.048 Mbps
Impedance 120, balanced

75, unbalanced (via adapter cable)
Line Coding HDB3
1-16 Technical Specifications ETX2i

Connector Electrical, four RJ-45 connectors:

Four E1 ports one E1 interface per RJ-45
Eight E1 ports two E1 interfaces per RJ-45, with
adapter cable
Modular EoPDH Number of Ports Four or eight

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

Four T1 ports one T1 interface per RJ-45
Eight T1 ports two T1 interfaces per RJ-45, with
adapter cable
Modular EoPDH T3 Number of Ports One or two

Interface (ETX2i)
Compliance G.703, G.7041, G.8040, G.7043, G.7042
Framing C-bit parity
Impedance 75, unbalanced
Line Coding B3ZS
Connector Coaxial BNC (one pair per port)
Modular SHDSL Number of Ports Two or four (4-wire or 8-wire)

Interface (ETX2i)
Type 2-wire unconditioned dedicated line (twisted pair)
Operation Mode STU-R (remote customer premises equipment)
Line Coding 16 or 32 TC-PAM
Line Rate 192 kbps5696 kbps with steps of n 64 kbps per

2-wire
Impedance 135
ETX2i Technical Specifications 1-17

Connector 4-wire ordering option: one RJ-45

8-wire ordering option: two RJ-45s
Standard ITU-T G.991.2, ITU-T G.994.1
Modular Network Number of Ports Four (8-wire) on slot 1

VDSL Bonding Card
Type 2-wire unconditioned dedicated line (twisted pair)
(ETX2i)
Operation Mode STU-R (remote customer premises equipment)
Line Coding 16 or 32 TC-PAM
Payload Rate 100Mbps DL/50Mbps UL per line
Impedance VDSL2 over POTS: 100

VDSL2 over ISDN: 135
Connectors Two RJ-45s (UTP)
Standard ITU-T G.993.2, G.997.1, G.998.2, IEEE 802.3
Temperature Operates in non-hardened device of up to 35C

(90F). Above this temperature, requires hardened
device.
Modular x86 and Processor Intel Core i7-4700EQ

D-NFV Interface
Cores Four
(ETX2i)
Core Frequency 2.4 GHz
Hard Drive Type: SSD

Volume: 128 GByte
RAM 4/8/16 GByte
Connectors USB: USB 2.0 type A port, master architecture

Console: RS-232 terminal interface
Station Clock (when Mode Input and output

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

75 unbalanced (via adapter cable)
Connector RJ-45 shielded

ToD/1PPS (when Mode Output

applicable) (ETX2i)
Line/connector RS-422 over RJ-45 (NMEA 0183)
EXT-CLK (when Mode Output

applicable)
(ETX2i)
Signal type Square wave
Amplitude 2.0 Vpp
Nominal Impedance 50 unbalanced
Connector SMA
1PPS (when Mode Output

applicable)
(ETX2i)
Amplitude 2.0 Vpp
Connector SMA
Alarm Inputs Type Dry relay contact with one relay

(hardware ready)
Number of Inputs Three
(ETX2i)
Connector Terminal block, 9-pin
USB Interface Type USB2

(ETX2i)
Rating 5v/500 ma
Protection Thermal shutdown
Short circuit protection
Power (ETX2i) AC 100240 VAC (10%), 0.7A-0.4A, 50/60 Hz
DC 19 enclosure: 24/48 VDC (20-60 VDC)

19 enclosure: Dual DC feed of 24/48 VDC
(20-60 VDC) (relevant for Fixed Ports and Modular
Uplink)

Power Consumption Fixed ports:

Non-modular product base (8GbE): 35W max
Modular and D-NFV:
Modular base: 30W
Modular uplink: 5W max
VDSL: 10W max
D-NFV module: 30W max
Physical (ETX2i) Size (19 enclosure) Fixed option:

H: 43.7 mm (1.7 in)
W: 440 mm (17.4 in)
D: 240 mm (9.5 in)
Modular option:
H: 43.7 mm (1.7 in)
W: 440 mm (17.4 in)
D: 300 mm (11.8 in)
D-NFV option:
H: 43.7 mm (1.7 in)
W: 440 mm (17.4 in)
D: 350 mm (13.78 in)
Size (8.5 Fixed option:

enclosure) H: 43.7 mm (1.7 in)
W: 215.9 mm (8.5 in)
D: 300 mm (11.8 in)
Modular option:
H: 43.7 mm (1.7 in)
W: 215.9 mm (8.5 in)
D: 300 mm (11.8 in)
Environment Storage -40 to 85C (-40 to 185F)

(ETX2i) Temperature
Operating Regular:
Temperature 0 to 50C (32 to 122F)
Temperature-hardened (fixed and modular options):
-40 to 65C (-40 to 149F)
Humidity 5% to 90%, non-condensing
Ethernet Interfaces Number of Ports Network: Two

(ETX-2i-B)
User: Two, four, or eight

Type SFP/copper (combo), SFP, copper

Notes:
With 6xSFP6, up to 50C commercial SFP6 or 55C
industrial SFP6 is required.
With 4xSFP6 and 2xSFP-30, up to 45C commercial
SFP-30 or 50C industrial SFP-30 is required.
In regular ETX-2i-B (not 2U), use only one copper
or SFP due to power restrictions.

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

Mode autonegotiation, MDI/MDIX
1PPS (when Mode Output

applicable)
(ETX-2i-B)
Amplitude 2.0 Vpp
Connector SMA
Alarm Inputs Type Dry relay contact with one relay

(hardware ready)
Number of Inputs Three
(ETX-2i-B)
Connector Terminal block, 9-pin

(ETX-2i-B)
Rating 5v/500 ma
Modular x86 and Processor Intel Atom Rangeley

D-NFV Interface C2558; Intel Atom Rangeley
(ETX-2i-B) C2758
Cores
4, 8 respectively

Hard Drive Type: SSD M2.0/2.5 format

Volume: 128 GByte with or without PLP
RAM 8 GByte
Connectors USB: USB 2.0 type A port, master architecture

Console: RS-232 terminal interface
Power (ETX-2i-B) AC/DC AC/DC inlet connector with auto detection

Wide-range AC: 100-240 VAC (10%), 50/60 Hz;
DC: 48 VDC (40-60 VDC)
D-NFV option:
AC: 100-240 VAC (10%), 50/60 Hz
DC: Dual DC feed of 24/48 VDC (20-60 VDC)
Power Consumption 23W max
D-NFV:
Modular base: 23W
D-NFV: 30W
Physical (ETX-2i-B) Height 1U box: 43.7 mm (1.7 in)

(Metal Enclosure) 2U box: 88.2 mm (3.5 in)
Width Type 4 metal: 220 mm (8.7 in)
D-NFV: 215.5 mm (8.5 in)
Depth 170.0 mm (6.7 in)

D-NFV: 280 mm (11 in)
Weight 1U box: 0.7 kg (1.54 lb)

(ETX-2i-B) Temperature
Operating -5 to 55C (23 to 131F)

Temperature -20 to 65C (-4 to 149F) for ETX-2i-B with ten ports
Note: In ETX-2i-B with ten ports (2U), a single
SFP-30H is supported at temperature up to 62C.
D-NFV: 0 to 50C (32 to 122F)

10GbE Interfaces Number of Ports Four SFP+ (1GbE or 10GbE). Two or four 1GbE
(ETX-2i-10G) capable ports require a license (two or four-port
speed, respectively) to make them 10GbE capable.
The following Ethernet configurations can be ordered
for half 19 model:
4 SFP+ and 8 1GbE SFP
4 SFP+, 4 1GbE SFP, and 4 1GbE UTP
The following Ethernet configurations can be ordered
for full 19 model:
4 SFP+, 12 1GbE SFP, and 12 1GbE UTP
4 SFP+ and 24 1GbE SFP
Note: Depending on the ordering option, all, some, or
none of the four SFP+ ports are 10G capable; the
remaining SFP+ ports are 1G capable, provided they
are available to users. In the case that all SFP+ ports
are 10G capable, the speed license is not relevant.
You can use the two or four-port speed license to
upgrade available 1G SFP+ ports to 10G.
Type Fiber optic (SFP-based)

10-Gigabit Ethernet
Connector SFP+ LC
Transceiver Types 10GBaseSR, 10GBaseER, 10GBaseLR, 10GBaseZR

1000BaseSx, 1000BaseLx
1GbE Interfaces Number of Ports Eight (half 19 model) or 24 (full 19 model)

(ETX-2i-10G)
Refer to the 1/10GbE specification for the Ethernet
configurations.
Type Copper (UTP) or fiber optic (SFP-based)

Gigabit Ethernet

Specifications and
Ranges
Transceiver Types 1000BaseSx, 1000BaseLx, 100Base FX (full duplex

only)
10/100/1000 BaseT (full duplex only)
Station Clock Mode Input and output

(ETX-2i-10G)

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

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

(ETX-2i-10G)
Line/connector RS-422 RJ-45 (NMEA 0183)
EXT-CLK Mode Output

(ETX-2i-10G)
Bit Rate 2.048 MHz
Amplitude 2.0 Vpp (5.0 unloaded)
Connector SMA (mini BNC)
1PPS (ETX-2i-10G) Mode Output
Amplitude 2.0 Vpp (5.0 unloaded)
Connector SMA (mini BNC)

(ETX-2i-10G)
Rating 5v/500 ma
Power (ETX-2i-10G) AC 100240 VAC nominal (10%) 50/60 Hz
DC 48 VDC (40-60 VDC)
Power Consumption 19 enclosure: 90W max

8.5 enclosure: 120W max
Power Supply 19 enclosure: hot swappable, redundant PS (AC and

DC)
8.5 enclosure: DC PS with dual inlet

Physical Size (8.5 Height: 43.7 mm (1.7 in)

(ETX-2i-10G) enclosure) Width: 215.5 mm (6.5 in)
Depth: 301 mm (11.8 in)
Weight: 2.3 kg (5.1 lb)
Size (19 enclosure) Height: 43.7 mm (1.7 in)

Width: 440 mm (17.4 in)
Depth: 240 mm (9.5 in)
Weight: 3.1 kg (6.8 lb)

(ETX-2i-10G) Temperature
Operating Regular: 0 to 50C (32 to 122F)

Temperature Temperature hardened: -40 to 65C (-40 to 149F)
Flows and Max. Number Flows ETX2i: 1,000

Classification
ETX-2i-B, ETX-2i-10G (half 19): 256
ETX-2i-10G (full 19): 1,860 (can include up to
1,000 multi-CoS flows)
Note: In ETX-2i-10G (full 19), classification matches
may also be a scaling factor.
Max. Number ETX2i, ETX-2i-B, ETX-2i-10G (half 19): 1,000

Classification
ETX-2i-10G (full 19): 930 matches for ports 3-16;
Matches per Device
930 matches for ports 1-2, 17-28
Max. Number Flow 256

Classification ACLs
Max. Number Port ETX2i: 768

Classification
ETX-2i-B, ETX-2i-10G (half 19, full 19): 300
Matches
Max. Number Flows 5

in a Unidirectional
Hub
Max. Number 7
Unidirectional Hubs
per Device
Bridge Mode VLAN-aware, VLAN-unaware
Max. Number Bridge ETX2i: 44

Ports
ETX-2i-B, ETX-2i-10G: 32

Max. Number MAC ETX2i: 32K

Table Entries
ETX-2i-B, ETX-2i-10G (half 19): 8K; ETX-2i-10G (full
19): 16K
Max. Number ETX2i: 128

Broadcast Domains
ETX-2i-B, ETX-2i-10G (half 19): 40
(VLANs)
ETX-2i-10G (full 19): 300
Router General IPv4, IPv6, static and dynamic router
Routing Protocols OSPFv2, BGPv4
Other Protocols BFD, VRRPv2, VRRPv3
Number of VRFs ETX2i: 10

ETX-2i-B: 5
Number of Router ETX2i: 31

Interfaces
ETX-2i-B:15
Notes:
Only one router interface is supported when
working with PWs.
Only two router interfaces can be configured for
management.

IPv4 Routing Table ETX2i: 4,000

Entries
ETX-2i-B: 2,000
IPv6 Routing Table ETX2i: 3,500

Entries
ETX-2i-B: 2,000
Router ACLs ETX2i: 128

ETX-2i-B: 64
ARP table entries 256

(IPv4 and IPv6)
OAM CFM 8021.1ag, Y.1731
Max. Number MDs ETX2i, ETX-2i-B, ETX-2i-10G (half 19): 127

per Device
ETX-2i-10G (full 19): 255
Max. Number MAs ETX2i, ETX-2i-B ETX-2i-10G (half 19): 127

per Device
ETX-2i-10G (full 19): 255

Max. Number MEPs Up to 8 (configuration on EVC.cos)

per MA
Max. Number MEPs ETX2i, ETX-2i-B , ETX-2i-10G (half 19): 127

per Device
ETX-2i-10G (full 19): 255

Max. Number ETX-2i-B, ETX-2i-10G (half 19): 512

Remote MEPs per
ETX2i, ETX-2i-10G (full 19): 1,024
Device
Max. Number Eight

Services per MEP
Max. Number ETX2i, ETX-2i-B, ETX-2i-10G (half 19): 255

Services per Device
ETX-2i-10G (full 19): 511
Max. Number Dest ETX2i, ETX-2i-B, ETX-2i-10G (half 19): 255

NEs (PM sessions
ETX-2i-10G (full 19): 511
LM/DM pairs) per
Device Notes:
Loss Measurement (LM) can be LMM or SLM.
Single SLM session per Dest NE is supported.
Single Test ID per EVC.CoS and RMEP is supported.
OAM TWAMP Max. Number Layer-2 E-Line service: 3

TWAMP Entities
Layer-2 E-LAN service over bridge: 7
(Controllers or
Responders) Layer-3: 15
Max. Number 150

Sessions Per Device
Max. Rate 150 pps

Supported For
TWAMP Sessions
Per Device
Max. Number Peers 15

Supported for
TWAMP Controllers
Max. Rate Per 10 pps

Session
Quality of Service Policer Dual Token Bucket mechanism (two rates, three
(Traffic colors)
Management)
CIR, CBS, EIR, EBS

Color Mode Color blind, color aware with coupling flag support
Standard MEF 10.3
Max. Number Policer 256

Profiles
Max. Number Policer 160

Aggregates
Max. Number Ranks 4 or 8 (selectable at the device level)

in Envelope Policer
Max. Number ETX2i:

Envelope Instances
4-rank mode: 250
8-rank mode: 125
ETX-2i-B, ETX-2i-10G (half 19):
4-rank mode: 64
8-rank mode: 32
ETX-2i-10G (full 19):
4-rank mode: 1,000
8-rank mode: 500
Max. Number 128

Shaper Profiles
Max. Number Queue ETX2i, ETX-2i-10G (half 19): 128

Blocks in Device
ETX-2i-10G (full 19): 256
Max Number Queue Network ports ETX2i, ETX-2i-10G (half 19): 64;
Blocks per Port User ports Eight
ETX-2i-10G (full 19): Network port 1 239; Network

port 2 90; all other ports 8
Max. Queue Size 16k frame buffers, 32 Mbytes
Total Frame Buffers ETX2i, ETX-2i-10G (full 19): 128k, 256 Mbytes
ETX-2i-B, ETX-2i-10G (half 19): 64k, 128 Mbytes
Max. Number 12
Marking Profiles
Max. Number Queue 12

Mapping Profiles

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

ordering options) Domains
Standards Normal operation (locked to upstream clock source):

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

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

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

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

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

Data rates: 9.6, 19.2, 115.2 kbps; Mini USB
connector


Chapter 2
Installation and Setup
This chapter describes installation and setup procedures for the ETX2i unit.
After installing the unit, refer to the Operation chapter for operating instructions
and the Management and Security chapter for management instructions.
If you encounter a problem, refer to the Monitoring and Diagnostics chapter for
test and diagnostic instructions.
Internal settings, adjustment, maintenance, and repairs may be performed only

by a skilled technician who is aware of the hazards involved.
Always observe standard safety precautions during installation, operation, and
Warning
maintenance of this product.
2.1 Safety
ETX2i devices are provided with the following types of grounding lugs:
ETX2i NEBS-compliant enclosures for central office or cell-sites have a
UL-recognized dual grounding lug.
Figure 2-1. Dual Grounding Lug

ETX2i enclosures that are not NEBS-compliant are provided with a single ring
tongue grounding lug.
ETX2i Safety 2-1

Chapter 2 Installation and Setup Installation and Operation Manual
Figure 2-2. Single Ring Tongue Grounding Lug

Screws are provided for attaching the grounding lug to ETX2i, as well as star or
spring washers that ensure proper contact and preclude loosening of the screws.
To connect a grounded wire to the grounding lug:

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

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

It is advisable to install AC-powered units within 1.5m (5 ft) of an
easily-accessible grounded AC outlet capable of furnishing the voltage in
accordance with the nominal supply voltage.
DC-powered units require a -48 VDC power source. Adequately isolate the units
from the main supply.
In order to protect equipment from surges on AC lines that exceed 2000V, install
a suitable surge protection device (SPD) at the AC power service entrance. The
SPD should be an approved component according to local regulations and codes,
and be capable of handling 6000V/3000A surges.
You should ground ETX2i equipment installed in a Central Office (CO) to a
common bonding network. This is the grounding system where all metal parts
and constructional materials of the building and installation are deliberately
bonded together and to the structures ground electrodes.
Seek the help of professionals to design the complex grounding system of cell-
sites. A poor grounding system may cause very high voltages between various
types of site equipment, due to ground potential rise.
2-2 Site Requirements and Prerequisites ETX2i

Installation and Operation Manual Chapter 2 Installation and Setup
Note Refer also to the Connecting AC Mains and Connecting DC Power sections in the
Front Matter of this manual.
Allow at least 90 cm (36 in) of frontal clearance for operating and maintenance
accessibility. Allow at least 10 cm (4 in) clearance at the rear of the unit for signal
lines and interface cables.
The following table displays the ambient operating temperature of ETX2i
products:
Table 2-1. Ambient Operating Temperature
Device Connectors
ETX2i Regular enclosure: 0 to 50C (32 to 122F)

Temperature-hardened enclosure (fixed and modular options
only): -40 to 65C (-40 to 149F)
ETX-2i-B Metal enclosure: -5 to 55C (23 to 131F).

Device with 10 ports: -20 to 65C (-4 to 149F)
ETX-2i-10G -40 to 65C (-40 to 149F)
The ambient operating temperature of ETX2i is at a relative humidity of 5% to

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

In addition to the general bonding and grounding instructions given in various
parts of this manual, this section presents procedures that are needed for
network telecommunication equipment that is installed in large
telecommunication centers (central offices) and cell-sites. These requirements
are an integral part of Telcordia GR-1089-CORE, but are applicable to all such
systems.
The main goals of adequate bonding and grounding are as follows:
Equalize the potential between several telecommunication units and reduce
voltage differences that might damage the equipment or present safety
hazards.
Ensure that overcurrent devices such as fuses and circuit breakers operate
properly during a fault.
Divert as much as possible of unwanted energy from lightning strikes or
transient phenomena on the mains supply to ground, by means of surge and
transient absorbers.
Improve electromagnetic compatibility.
Use the following methods in order to achieve proper bonding and grounding:
Connect the mains plug to a socket outlet with a ground connection; this
method protects the user from electrical shock but is not sufficient to
achieve adequate grounding and bonding.
ETX2i Site Requirements and Prerequisites 2-3

Connect the ground lug on the front or rear panel of the equipment to a
ground bus bar by means of a short grounding wire (see Safety).
Install the equipment in an adequately grounded rack by means of the
mounting brackets provided with the equipment, to improve the ground
connection of the ETX2i equipment. To mount ETX2i, connect the provided
mounting adapters to ETX2i using star and spring washers. Remove any
paint that may interfere with the connection.
Plan carefully the grounding system for the central office or cell-site.
2.3 Package Contents

The ETX2i package includes the following items:
ETX2i unit
Matching SFP/SFP+ module(s) (for relevant ordering option)
RM-34 rack-mount kit for mounting ETX2i unit with 19 enclosure in a 19"
rack (ETX2i, ETX-2i-10G)
Standard CBL-K21 AC external power cable (per ITU-K.21) supplied if AC
power supply is ordered
DC connection kit (supplied if DC power supply was ordered)
Manual download form
The ETX2i package also includes the following optional accessories, if ordered:
Cables:
CBL-RJ45/D9/F/6FT control port cable (ETX-2i-B)
CBL-MUSB-DB9F mini-USB cable to connect device to a serial port (ETX2i,
ETX-2i-B 2U with 10 ports, ETX-2i-10G)
Enhanced CBL-K21E AC external power cable (per ITU-K.21 Enhanced
mode)
Mounting kits:
RM-35 rack-mount kit for mounting one or two units with 8.5 enclosure
in a 19" rack (ETX2i, ETX-2i-B, ETX-2i-B DNFV, and ETX-2i-10G). RM-
35/P1 includes all accessories required for installing one unit; RM-35/P2
includes all elements accessories required for installing two units.
RM-42 rack-mount kit for mounting ETX-2i-B 2U unit
WM-35 wall-mount kit for ETX2i unit with 8.5 enclosure, ETX-2i-B DNFV,
and ETX-2i-10G
WM-35-TYPE4 for ETX-2i-B unit
Network interface and D-NFV modules for modular and D-NFV ordering
options
AC/DC adapter
Power supply according to ordering options:
Single AC power supply: ETX2i
2-4 Package Contents ETX2i

High power AC power supply (ETX2i with D-NFV)

High power DC power supply (ETX2i with D-NFV)
2.4 Required Equipment

Prior to installing the unit, prepare the following, as required:
Phillips screwdriver to mount the ETX2i unit in a rack or on the wall.
Standard CBL-K21 AC external power cable (per ITU-K.21) to connect the
unit to a socket indoors.
Enhanced CBL-K21E AC external power cable (per ITU-K.21 Enhanced mode)
to connect the unit to a socket in an unprotected power network (such as AC
cell site, AC street cabinet, AC pole, or rural area).
CBL-RJ45/D9/F/6FT control port cable to connect the unit (ETX-2i-B) to the
ASCII supervision terminal.
CBL-MUSB-DB9F mini-USB cable to connect the unit (ETX2i, ETX-2i-B 2U with
10 ports, ETX-2i-10G) to the ASCII supervision terminal.
Any other cables required to connect the unit to remote equipment as per
the specific application.
2.5 Mounting the Unit

ETX2i is designed for installation as a desktop unit in horizontal orientation only.
It can also be mounted in a 19" rack or on a wall, depending on the enclosure
size.
ETX2i units are intended for use in horizontal orientation only.

In case of vertical mounting orientation, install the unit on top of concrete or
Warning other non-combustible surface, such as an external baffle or tray, due to safety
considerations.
For rack mounting instructions, refer to the associated installation kit manual.
For wall mounting instructions for 8.5 enclosures, refer to the associated
installation kit. There is no wall mounting option for 19 enclosures.
If you are using ETX2i as a desktop unit, place and secure the unit on a stable,
non-movable surface.
Refer to the clearance and temperature requirements in Site Requirements and
Prerequisites.
ETX2i Mounting the Unit 2-5

2.6 Installing SFP Modules

You can install into an ETX2i Ethernet SFP port, a recognized SFP module with LC
fiber optic connector.
You can install into an ETX-2i-10G Ethernet SFP+ port, a recognized SFP of the
same speed as the SFP+ port (1GbE or 10GbE, depending on the ordering option
of the unit, and whether or not the port has been upgraded using the port speed
license (refer to Licensing section in Chapter 10)).
You can also install a recognized dual rate SFP (1GbE/10GbE) into the SFP+ port.
In this case, the SFP speed is adjusted to the speed of the SFP+ port
(1GbE/10GbE).
In the case that you insert into an SFP+ port, a recognized SFP of a different
speed than the SFP+ port, the device generates a Port rate mismatch event and
raises a Speed mismatch alarm, as in the following cases:
You inserted a recognized 10GbE SFP into an SFP+ port with speed-duplex
configured to 1GbE.
You inserted a recognized 1GbE SFP into an SFP+ port with speed-duplex
configured to 10GbE.
You can clear the alarm by either extracting the SFP from the port, or by changing
speed-duplex to match the SFP port (refer to Ethernet Ports section in Chapter
5).
If you insert an unrecognized SFP into an SFP or SFP+ port, even if it is the same
speed as the port, the SFP does not work, but does not raise an alarm or
generate a message.
Third-party SFP optical transceivers must be agency-approved, complying with the

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

1. Lock the wire latch of each SFP module by lifting it up until it clicks into place,
as illustrated in Figure 2-3 for SFPs.
Note Some SFP models have a plastic door instead of a wire latch.
2-6 Installing SFP Modules ETX2i

Figure 2-3. Locking the SFP Wire Latch

2. Carefully remove the dust covers from the SFP slot.
3. Insert the rear end of the SFP into the socket, and push slowly backwards to
mate the connectors until the SFP clicks into place. If you feel resistance
before the connectors are fully mated, retract the SFP using the wire latch as
a pulling handle, and then repeat the procedure.
Caution Insert the SFP gently. Using force can damage the connecting pins.
4. Remove the protective rubber caps from the SFP modules.
To remove the SFP module:

1. Disconnect the fiber optic cables from the SFP module.
2. Unlock the wire latch by lowering it downwards (as opposed to locking).
3. Hold the wire latch and pull the SFP module out of the Ethernet port.
Caution Do not remove the SFP while the fiber optic cables are still connected. This may
result in physical damage (such as a chipped SFP module clip or socket), or cause
malfunction (e.g., the network port redundancy switching may be interrupted).
2.7 Installing the D-NFV Module
Note This section is relevant for ETX2i only.
You can insert into the rear of the ETX2i unit, a D-NFV module with an
integrated Intel x86 core, to enable hosting virtual machines providing virtual
network functions (VFs).
ETX2i supports hot swapping of the D-NFV module (card), meaning you can
insert and extract the D-NFV module into the ETX2i device without interrupting
the devices operation (i.e. powering it down).
ETX2i Installing the D-NFV Module 2-7

Note The following procedures are relevant for ETX2i with a hot-swappable D-NFV
module, indicated by a screw and latch at the top right edge on the rear of the
ETX2i unit.
If you are using an ETX2i unit that does not support hot swapping, you must
power down the ETX2i unit, insert or remove the D-NFV module, and then power
up the ETX2i unit again.
Inserting the D-NFV Module (Hot Swapping)

To install the D-NFV module:
1. For safe insertion of the D-NFV module, disable D-NFV operation by entering
configure> cn> shutdown.
2. Release the lock knob screw, open the latch, and remove the dummy module.
Figure 2-4. Unit with Dummy Module Latch Closed (left) and Open (right)
3. Insert the D-NFV module into the now empty device slot.
Figure 2-5. D-NFV Module Partially Inserted

4. Push the D-NFV module into the device until it clicks into place.
2-8 Installing the D-NFV Module ETX2i

Figure 2-6. D-NFV Module in Device Latch Open

5. Close all the D-NFV holding screws, close the latch, and secure it with the lock
screw.
Figure 2-7. D-NFV Module in Device Latch Closed
Note Only after the lock is secured in place, the device recognizes that the D-NFV card
has been inserted.
6. Enable D-NFV operation by entering configure> cn> no shutdown.

The D-NFV LED turns green, indicating that D-NFV is operational.
Extracting the D-NFV Module (Hot Swapping)

To remove the D-NFV module:
1. If the D-NFV module is powered down (D-NFV Active LED is not green), skip
to step 8.
2. Enter configure> chassis> ve-module> remote-terminal to get to the D-NFV
card serial port.
Wait a few moments while Linux uploads.
3. When output has completed, at the login prompt, enter rad, and at the
Password prompt, enter rad123 (invisible)
4. Enter sudo poweroff p to close Linux.
5. Re-enter password: rad123
ETX2i Installing the D-NFV Module 2-9

Linux powers down.

6. Once Linux finishes the shutdown process, press CTL .
The ETX2i command line is displayed.
7. In the ETX2i command line, enter configure> cn> shutdown.
Wait for the D-NFV green LED to turn off. D-NFV operation is disabled.
8. Release the screw and open the latch holding the module in place (see
Figure 2-6).
9. Pull the D-NFV module out of the slot (see Figure 2-5).
10. Insert the dummy module into the slot (see Figure 2-4, rightmost figure).
11. Close all screws, close the latch, and secure it with the lock screw (see
Figure 2-4, leftmost figure).
2.8 Connecting to Power

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

ETX2i, ETX-2i-B D-NFV, and ETX-2i-10G half 19 hardened devices have a built-in
AC Surge Protection Unit, and therefore, in unprotected power networks, can use
the standard CBL-K21 AC external power cable (per ITU-K.21) to provide AC
power to the unit.
ETX-2i-B (Type 4) and ETX-2i-10G 19 hardened devices do not have a built-in AC
Surge Protection unit, and therefore require an Enhanced CBL-K21E AC external
power cable (per ITU-K.21E).
Under standard conditions, ETX-2i-B (2U) can use a standard CBL-K21 AC external
power cable for AC power. However, in unprotected power networks, it cannot
use the Enhanced CBL-K21E AC external power cable. In this case, the device
requires a special ordering option that supports K21E.
The following table summarizes K.21E support in the ETX2i family:
Table 2-2. K.21E support in ETX2i family
Device K.21E Support
ETX220A Enhanced CBL-K21E AC external power cable
ETX2i No additional support required; has built-in K.21E AC surge

protection unit.
ETX-2i-B (2U) Not supported in regular device. Requires a special ordering

option that supports K.21E.
ETX-2i-B (Type 4) Enhanced CBL-K21E AC external power cable
ETX-2i-B D-NFV No additional support required; has built-in K.21E AC surge

protection unit.
ETX-2i-10G half 19 No additional support required; has built-in K.21E AC surge

protection unit.
ETX-2i-10G 19 Enhanced CBL-K21E AC external power cable
To connect to AC power:
1. Connect the relevant power cable to the power connector on ETX2i.
For indoor installation standard CBL-K21 AC power cable
For connection of hardened units to an unprotected power network:
For ETX-2i-B (Type 4) and ETX-2i-10G 19 Enhanced CBL-K21E AC
external power cable
For ETX2i, ETX-2i-B D-NFV, and ETX-2i-10G half 19 (with built-in AC
Surge Protection Unit) Standard CBL-K21 AC external power cable
For ETX-2i-B (2U) Regular unit cannot be used. Use special ordering
option that supports K21E.
The unit turns on automatically.
ETX2i Connecting to Power 2-11

Connecting to DC Power
AC/DC plugs or terminal block connectors are available for wiring the DC
connection to the power cable (see AC/DC Adapter (AD) Plug for DC Power Supply
Connection and Terminal Block Connector for DC Power Supply Connection).
All DC options support NEBS level 3 on port type 8b (DC inlet).
To connect to DC power:
1. Wire the DC connection to the power cable, and connect it to the unit.
See the relevant DC Power Supply Connection section below for instructions
on wiring the DC connection AC/DC Adapter (AD) Plug for DC Power Supply
Connection or Terminal Block Connector for DC Power Supply Connection.
The unit turns on automatically.
AC/DC Adapter (AD) Plug for DC Power Supply Connection

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

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

To prepare the AD plug and connect it to the DC power supply cable:

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

Certain DC-powered units are equipped with a plastic 3-pin VDC-IN power input
connector, located on the unit rear panel. Different variations of the connector
are shown in Figure 2-11. All are functionally identical.

Figure 2-11. TB DC Input Connector Types Appearing on Unit Panels

Supplied with such units is a kit including a mating Terminal Block (TB) type
connector plug for attaching to your power supply cable.
The DC power supply cable wiring requirements are as follows:
Solid or stranded wires
Wire gauge AWG 12-18 according to products current consumption
Connect the wires of your power supply cable to the TB plug, according to the
voltage polarity and assembly instructions provided on the following pages.
Caution Prepare all connections to the TB plug before inserting it into the units VDC-IN
connector.
To prepare and connect the power supply cable with the TB Plug:
Note Refer to Figure 2-12 for assistance.
1. Strip the insulation of your power supply wires according to the dimensions
shown.
2. Place each wire lead into the appropriate TB plug terminal according to the
voltage polarity mapping shown in Figure 2-13. (If a terminal is not already
open, loosen its screw.) Afterwards, tighten the three terminal screws to
close them.
3. Pull a nylon cable tie (supplied) around the power supply cable to secure it
firmly to the TB plug grip, passing the tie through the holes on the grip.
4. Isolate the exposed terminal screws/wire leads using a plastic sleeve or
insulating tape to avoid a short-circuit.
5. Connect the assembled power supply cable to the unit by inserting the
TB plug into the units VDC-IN connector until it snaps into place.

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

Figure 2-14. TB Plug with Captive Screws (optional)
To disconnect the TB plug:

1. If the TB plug is equipped with captive screws, loosen the captive screws
(see Figure 2-14).
2. If the units VDC-IN connector is type B, lift the locking latch
(see Figure 2-11).
3. Pull out the TB plug carefully.
Caution Always lift the locking latch of type B connectors before disconnecting the
TB plug, to avoid damaging the TB plug.
2.9 Connecting to Alarm Equipment

The alarm port is terminated in a 9-pin flat connector, designated ALARM. This
port includes:
Floating change-over dry-contact outputs for the major and minor alarm relays.
The alarm relay contacts are rated at maximum 30 VDC across open contacts,
and maximum 2 ADC through closed contacts or 125 VAC across open contacts,
and maximum 0.5 AAC through closed contacts (total load switching capacity of
60 W).
Caution Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
+12V auxiliary voltage output (through a 1600 W series resistor)
2-16 Connecting to Alarm Equipment ETX2i

External alarm sense input. The input accepts an RS-232 input signal; it can
also be connected by means of a dry-contact relay to the auxiliary voltage
output.
To connect to the ALARM connector:

Connect a cable that meets the specific requirements of the site to the
ALARM connector. Refer to Appendix A for connector pin functions.
Caution
To prevent damage to the internal alarm relay contacts, it is necessary to limit, by
external means, the maximum current that may flow through the contacts
(maximum allowed current through closed contacts is 2A). The maximum voltage
across the open contacts must not exceed 30 VDC.
Figure 2-15. Alarm Connector ETX2i
Figure 2-16. Alarm Connector ETX-2i-B (2 SFP + 2 Combo)
Figure 2-17. Alarm Connector ETX-2i-10G Full 19 (4 SFP+, 12 SFP, and 12 UTP)
2.10 Connecting to Ethernet Equipment

You can connect ETX2i to Ethernet equipment via the connectors described in
the following table, according to the relevant option:
Table 2-3. Device Connectors
Device Connectors
ETX2i Fiber optic LC connector designated GbE/100Fx (combo

port)
8-pin RJ-45 electrical port designated 10/100/1000BT
(combo port)
ETX2i Connecting to Ethernet Equipment 2-17

Device Connectors
ETX-2i-B Fiber optic LC connector designated GbE/100Fx (standard

port, combo port)
(combo port)
ETX-2i-10G Fiber optic LC connector designated GbE/100Fx (standard

port, combo port)
Fiber optic LC connector designated 10GbE
The instructions below are illustrated with sample configurations.
To connect to the Ethernet equipment with fiber optic interface:

Connect ETX2i to the Ethernet equipment using a standard fiber optic cable
terminated with an LC connector.
Note Use shielded cables when connecting to the Ethernet ports.
Figure 2-18. GbE Fiber Optic Connectors ETX2i
Figure 2-19. GbE Fiber Optic Connectors ETX-2i-B (2 SFP + 2 Combo)
Figure 2-20. GbE Fiber Optic Connectors ETX-2i-B (2 SFP + 4 UTP)
2-18 Connecting to Ethernet Equipment ETX2i

Figure 2-21. GbE Fiber Optic Connectors ETX-2i-B 2U with ten SFP
Figure 2-22. GbE Fiber Optic Connectors Half 19 (4 SFP+, four SFP, and four UTP)
Figure 2-23. GbE Fiber Optic Connectors ETX-2i-10G Full 19 (4 SFP+, 12 SFP, and 12 UTP)
To connect to the Ethernet equipment with a copper interface:

Connect ETX2i to the Ethernet network equipment using a standard straight
STP cable terminated with an RJ-45 connector. Refer to the Connection Data
appendix for the RJ-45 connector pinout.
The following applies to all intra-building Ethernet ports with a copper interface
(RJ-45):
Warning The ports are suitable for connection to intra-building or unexposed wiring or
cabling only. The intra-building port(s) of the equipment or subassembly MUST
NOT be metallically connected to interfaces that connect to the OSP or its
wiring. These interfaces are designed for use as intra-building interfaces only
(Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation
from the exposed OSP cabling. The addition of primary protectors is not
sufficient protection in order to connect these interfaces metallically to OSP
wiring.
The ports must use shielded intra-building cabling/wiring that is grounded at
both ends. The ground connection must be stable and with low impedance, in
order to ensure that surge currents, which can develop due to ground
ETX2i Connecting to Ethernet Equipment 2-19

potential rise, do not cause very high voltages to develop on the ETH isolation
transformer.
Note In order to comply with electromagnetic compatibility requirements, it is

recommended to use Category 6E shielded twisted pairs (STP) cables.
Figure 2-24. Ethernet Electrical Connectors ETX2i
Figure 2-25. Ethernet Electrical Connectors ETX-2i-B (2 SFP + 2 Combo)
Figure 2-26. Ethernet Electrical Connectors ETX-2i-10G Half 19 (4 SFP+, 4 SFP, and 4 UTP)
Figure 2-27. Ethernet Electrical Connectors ETX-2i-10G Full 19 (4 SFP+, 12 SFP, and 12 UTP)
2.11 Connecting to SHDSL Equipment
Note This section is relevant for the ETX2i modular option with SHDSL network
module.
You can connect ETX2i to SHDSL equipment via one or two RJ-45 connectors
designated SHDSL; one RJ-45 connector for the 4-wire option and two RJ-45
connectors for the 8-wire option.
2-20 Connecting to SHDSL Equipment ETX2i

Figure 2-28. SHDSL Connectors ETX2i (eight-wire ordering option)
To connect to SHDSL equipment:

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

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

Connect ETX2i to the VDSL equipment using standard straight UTP cables
terminated with RJ-45 connectors. Refer to the Connection Data appendix for
the RJ-45 connector pinout.
Note Use unshielded cables when connecting to the VDSL ports.
2.13 Connecting to E1/T1 Equipment
Note
This section is relevant only for the ETX2i modular option with E1/T1 network
module.
ETX2i Connecting to E1/T1 Equipment 2-21

You can connect ETX2i to E1 or T1 equipment via the RJ-45 connectors

designated E1/T1.
To connect to E1 or T1 equipment:
Connect an E1 or T1 line to the RJ-45 connector designated E1/T1 (14/8).
Refer to the Connection Data appendix for the RJ-45 connector pinout.
Figure 2-30. E1/T1 Ports ETX2i
2.14 Connecting to T3 Equipment
Note This section is relevant only for the modular option with T3 network module.
You can connect ETX2i to T3 equipment via the BNC coaxial connectors on the
network module.
Note You must configure the module with the correct module type. Refer to the Cards
and Ports chapter for details.
To connect to T3 equipment:
1. Connect the Rx cable to the BNC connector labeled Rx.
2. Connect the Tx cable to the BNC connector labeled Tx.
Figure 2-31. T3 Ports ETX2i
2.15 Connecting to Station Clock
Note This section is relevant only for ETX2i or ETX-2i-10G ordered with a timing option
that includes a station clock port.
You can connect ETX2i to an external clock source via a dedicated station clock
port, an RJ-45 connector designated EXT-CLK. Refer to the Connection Data
appendix for the connector pinout.
2-22 Connecting to Station Clock ETX2i

Figure 2-32. EXT-CLK Connector ETX2i
Figure 2-33. EXT-CLK Connector ETX-2i-10G

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

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

Connecting to equipment with an unbalanced interface requires you to convert
the RJ-45 connector to a pair of BNC female connectors, in order to receive the
clock signal via one of the connectors and transmit the signal via the other.
To connect ETX2i to an unbalanced clock source:

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

2.16 Connecting to Synchronization Equipment
Note This section is relevant only for ETX2i, ETX-2i-B, or ETX-2i-10G ordered with a
timing option that includes the EXT-CLK/1PPS ports and/or the ToD/1PPS port.
ETX2i can transmit a 1PPS signal for synchronization, as well as connect to an

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

Connect ETX2i to the synchronization equipment using standard SMA cables
terminated with SMA connectors.
To connect to ToD/1PPS:
Connect ETX2i to the synchronization equipment using a proprietary RAD
cable terminated with a male RS-422 RJ-45 connector.
Figure 2-34. EXT-CLK and 1PPS Connector ETX2i
Figure 2-35. ToD/1PPS Connector ETX2i
Figure 2-36. EXT-CLK and 1PPS Connector ETX-2i-10G
2-24 Connecting to Synchronization Equipment ETX2i

Figure 2-37. ToD/1PPS Connector ETX-2i-10G
2.17 Connecting to a Terminal

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

1. Connect the mini USB CBL-MUSB-DB9F cable to the CONTROL connector.
2. Connect the other end of the mini USB cable to a computer equipped with an
ASCII terminal emulation application.
Figure 2-38. CONTROL Connector ETX2i
Figure 2-39. CONTROL Connector ETX-2i-B
Figure 2-40. CONTROL Connector ETX-2i-10G
ETX2i Connecting to a Terminal 2-25

2.18 Connecting to a Network Management Station

You can connect ETX2i to remote network management stations via the
dedicated Ethernet management port, an 8-pin RJ-45 connector designated
MNG-ETH. Refer to the Connection Data appendix for the connector pinout.
To connect to an NMS:
Connect ETX2i to an Ethernet switch.
Figure 2-41: Ethernet Management Connector ETX2i
Figure 2-42: Ethernet Management Connector ETX-2i-B
Figure 2-43: Ethernet Management Connector ETX-2i-10G
2.19 Basic Connectivity Tests
Caution Before leaving the installation site, it is highly recommended that you test
network connectivity between the device and the remote network management
station (for example, by sending a ping).
2-26 Basic Connectivity Tests ETX2i

Chapter 3
Operation and
Maintenance
This chapter:
Explains power-on and power-off procedures
Provides a detailed description of the front panel controls and indicators and
their functions
Describes the startup sequence of ETX2i
3.1 Turning On the Unit

To turn on ETX2i:
Connect the power cord to the mains.
The PWR indicator lights up and remains lit as long as ETX2i receives
power.
ETX2i requires no operator attention once installed, with the exception of
occasional monitoring of front panel indicators. Intervention is only required
when ETX2i must be configured to its operational requirements, or diagnostic
tests are performed.
3.2 Indicators
The following sections describe the functions of the ETX2i LED indicators.
ETX2i
Figure 3-1. ETX2i Front Panel
ETX2i Indicators 3-1

Chapter 3 Operation Installation and Operation Manual
Table 3-1. ETX2i Front Panel Controls and Indicators
Name Color State
PWR Green ON Power is ON.

TST/ALM Red ON There is at least one active alarm.
Flashing Diagnostic loopback is active.
FD Contains push button for setting unit to default configuration
LINK Green ON Ethernet interface is synchronized.

Ethernet port
(User/Network/MNG)
ACT Yellow ON Data is being transmitted/received at the Ethernet link.

Ethernet port
(User/Network/MNG)
SHDSL SYNC Green/red ON (green) SHDSL line is synchronized.

SHDSL ports on ON (red) SHDSL line is not synchronized.
modular uplink
Flashing (red/green): SHDSL line is activating, after exchanging
connection parameters (handshaking) with remote side.
LOC Red ON Local synchronization loss (LOS, LOF, or AIS occurred)

E1/T1 ports on OFF No local synchronization alarm
modular uplink
AIS Yellow ON AIS (Alarm Indication Signal) occurred.

T3 port(s) on modular OFF No AIS alarm
uplink
LOS Red ON Local synchronization loss (LOS)

T3 port(s) on modular OFF No local synchronization alarm
uplink
SD Green ON Station clock port is synchronized.

EXT-CLK
ETX-2i-B
Figure 3-2. ETX-2i-B Metal 2+4 Front Panel
3-2 Indicators ETX2i

Installation and Operation Manual Chapter 3 Operation
Figure 3-3. ETX-2i-B Metal 2+2 Combo Front Panel
Figure 3-4. ETX-2i-B-DNFV Front Panel
Figure 3-5. ETX-2i-B-DNFV Back Panel
Figure 3-6. ETX-2i-B 2U Front Panel
Table 3-2. ETX-2i-B Controls and Indicators
Name Color State

ETX2i Indicators 3-3

Name Color State
LINK Green ON Ethernet link is synchronized.

Ethernet port
(User/Network/MNG)

Ethernet port
(User/Network/MNG)
Active Green ON LINUX is up and running.

Relevant for ETX-2i-B-DNFV (back panel)
ETX-2i-10G
Figure 3-7. ETX-2i-10G Half 19 Front Panel (4 SFP+, 4 SFP, and 4 UTP)
Figure 3-8. ETX-2i-10G Full 19 Front Panel (4 SFP+, 12 SFP, and 12 UTP)
Figure 3-9. ETX-2i-10G Full 19 Front Panel (4 SFP+ and 24 SFP)
Table 3-3. ETX-2i-10G Front Panel Controls and Indicators
Name Color State

LINK Green ON Ethernet interface is synchronized.

Ethernet port
(User/Network/MNG)
3-4 Indicators ETX2i

Name Color State

Ethernet port
(User/Network/MNG)
3.3 Startup
Applicable Products
All configuration and software files, as well as the loading sequence, are
applicable to all ETX2i products.
Configuration and Software Files

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

factory-default-config contains the manufacturer default settings. At
startup, factory-default-config is loaded if startup-config, rollback-config, and
user-default-config are missing or invalid.
rollback-config serves as a backup for startup-config. At startup,
rollback-config is loaded if it exists and is valid, and if startup-config is
missing or invalid.
restore-point-config created by ETX2i when software is installed with
restore point option. Refer to the Software Upgrade chapter for more details.
running-config contains the current configuration that the device is
running. This file is deleted and rebuilt at device reboot.
startup-config contains saved non-default user configuration. This file is
not automatically created. You can use the save or copy command to create
it. At startup, startup-config is loaded if it exists and is valid.
user-default-config contains default user configuration. This file is not
automatically created. You can use the copy command to create it. At
startup, user-default-config is loaded if startup-config and rollback-config,
are missing or invalid.
Note Configuration files should contain only printable ASCII characters (0x200x7E),
<Enter> (0x0D), <Line Feed> (0x0A), and <Tab> (0x09).
Refer to the File Operations section in the Administration chapter for details on
file operations.
ETX2i Startup 3-5

Loading Sequence
At startup, the device attempts to load configuration files in the following
sequence until a valid one is found:
startup-config
rollback-config
user-default-config
factory-default-config
If an error is encountered while loading a file, the default is to ignore the error
and continue loading. You can use the on-configuration-error command to
change this behavior, to either stop loading the file when the first error is
encountered, or reject the file and reboot; after rebooting, the next file in the
loading sequence is loaded).
To display the parameter values after startup, use the info [detail]
command.
3.4 Working with Custom Configuration Files

In large deployments, often a central network administrator sends configuration
files to the remote locations and all that remains for the local technician to do is
replace the IP address in the file or other similar minor changes, and then
download the file to the device. Alternatively, the technician can download the
file as is to the device, log in to the device and make the required changes, and
then save the configuration.
To download the configuration file, use the copy command (refer to the
Administration chapter). 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.
To ease deployment of large numbers of devices, you can automatically distribute
software and configuration files in the following ways:
Use Zero Touch provisioning to enable units to automatically receive an IP
address and software and configuration files (see Zero Touch for details).
Use PPPoE (Point-to-Point Protocol over Ethernet) to establish a management
channel through which an IP address can be acquired (refer to Point-to-Point
Protocol over Ethernet (PPPoE) for details). For instance, the IP address can
be acquired from a broadband remote access server (BRAS), which notifies a
Radius server, which reports to a management system that a new device is
up. The management system then sends software and configuration files to
the device.
Applicable Products
These file operations are applicable to all ETX2i products.
3-6 Working with Custom Configuration Files ETX2i

Saving Configuration Changes

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

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

At the file# prompt, enter: copy running-config user-default-config.
Zero Touch
The Zero Touch feature allows ETX2i to receive software and configuration files
automatically, eliminating the need to manually log into ETX2i in order to
transfer the required files to it.
The following zero touch mechanisms enable automatic provisioning of ETX2i:
Zero Touch via DHCP ETX2i retrieves configuration information from the
DHCP server (see Zero Touch via DHCP/DHCPv6).
Zero Touch via DHCPv6 ETX2i retrieves configuration information from the
DHCPv6 server (see Zero Touch via DHCP/DHCPv6).
ETX2i Working with Custom Configuration Files 3-7

Zero Touch via trap ETX2i sends a notification trap to the management
system (see Zero Touch via Trap), so that the management system can
perform the appropriate provisioning.
Show Me Demo
To view a video describing Zero Touch via DHCP:

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

This section describes Zero Touch provisioning via DHCP (for IPv4) or DHCPv6 (for
IPv6).
Prerequisites
A Zero Touch configuration (ZTC) XML file, containing directives for the
software and configuration files. See ZTC File Structure for details on how to
prepare this file.
A DHCP or DHCPv6 server for providing the TFTP server address, in addition to
the usual IP address, default gateway, etc.
A TFTP server from which to download the following:
ZTC file
Software image file, if required by the directives
Configuration file, if required by the directives
Sequence
1. At reboot, ETX2i obtains a DHCP lease from the DHCP server and/or a
DHCPv6 lease from the DHCPv6 server. If ETX2i receives more than one lease
that contains ZTC directives (from multiple interfaces), it processes them one
by one. After the first one is finished, either successfully or not (e.g. reaching
a timeout during file download), the device proceeds with the directives
received in the second lease.
2. For DHCP: The lease provides the TFTP server address, either via option 150,
or as a string via option 66 (the string is interpreted as an IP address rather
than a device name). Option 66 is valid only if the string is formatted as

(xxx.xxx.xxx.xxx). Optionally, the DHCP lease provides the path and/or the file
name of the ZTC file via DHCP option 67.
3. For DHCPv6: The lease provides the TFTP server address via CableLabs
vendor-specific (17) sub-option 32, provided that ETX2i supports it. If
multiple TFTP server addresses are received, only the first one is used.
Optionally, the DHCPv6 lease provides the path and/or the file name of the
ZTC file via DHCPv6 sub-option 33.
4. If neither a valid TFTP address nor the path and/or file name of the ZTC file is
obtained, the ZTC process finishes unsuccessfully.
5. ETX2i loads the ZTC file from the TFTP server, according to the information
received in the lease. If not specified in the lease, the default path is rad/,
and the default file name is rad.xml.
6. If the ZTC file is loaded successfully, ETX2i sends the event download_end
(with success indication) to any configured network managers, and saves the
ZTC file as zero-touch-config-xml.
7. If zero-touch-config-xml contains directives for a software file, ETX2i does
one of the following, according to the action specified in the directives:
upgrade-only Load software file if it is newer than the active software
image.
downgrade-only Load software file if it is older than the active software
image.
replace Load software file if different from the active software image.
8. If zero-touch-config-xml contains directives for a configuration file, then if
the action specified in the directives is replace-cfg, ETX2i loads the specified
configuration file if it is different than the last configuration file loaded via
the ZTC mechanism, and saves it as specified by cfg-dst-file.
9. If a software file was downloaded, ETX2i installs it as the active software
pack.
10. If a software file and/or configuration file was downloaded, ETX2i reboots.
After startup, the normal startup loading sequence is performed, so that if
startup-config is loaded in the sequence, ETX2i executes the CLI commands
in the file.
11. If no reboot was needed, ETX2i performs the normal startup loading
sequence.
If the ZTC process ends successfully, ETX2i sends the event download_end (with
success indication) to any configured network managers.
If an error occurs in the ZTC process, ETX2i does the following:
Sends the event download_end (with failed indication) to any configured
network managers
Starts a 10-minute timer
Performs the normal startup loading sequence
When the timer expires, ETX2i again attempts the ZTC process.

ZTC File Structure

This section describes the ZTC directives in the ZTC file, which is written in
standard XML, based on the Netconf schema. The file can contain directives for
one or more devices. This flexibility enables the use of one ZTC file per device, or
one ZTC file for all devices. ZTC File Example shows a ZTC file containing directives
for ETX-100, ETX-200, and ETX-300.
The directives are enclosed in the element pair <zero-touch-configuration>
</zero-touch-configuration>. The ZTC directives for a particular device are
enclosed by an element pair such as <ETX-100></ETX-100>. The element
contents are according to the chassis name in the inventory display (refer to the
Inventory section). The file can contain software-related directives and/or
configuration-related directives for each device.
Software Directives
The following directives supply information about the software file to download:
sw-version version of the software to download; must be formatted in the
same way as the chassis software revision displayed in the inventory display
(refer to the Inventory section).
sw-action software installation to perform:
upgrade-only Load software file if sw-version specifies a newer version
than the chassis software revision.
downgrade-only Load software file if sw-version specifies an older
version than the chassis software revision.
replace Load software file if sw-version specifies a version that is
different from the chassis software revision.
sw-src-file path and name of the software to download
sw-dst-file file name for saving the downloaded software:
sw-pack-<n> File is saved as the specified name, if it is not the active
software.
auto File is saved as follows:
If there is an unused software pack number, and there is enough
space in the file system, then the file is saved as sw-pack-<n>, where
<n>is the smallest unused software pack number.
If all software packs numbers are in use, or if there is not enough
space to save the software, then the file is saved as sw-pack-<n>,
where <n>is the software pack number of the oldest version.
Configuration Directives
The following directives supply information about the configuration file to
download:
cfg-version version of configuration to download
cfg-action action to take regarding configuration:

replace-cfg Load configuration file if cfg-version is different than the

last ZTC configuration version.
cfg-src-file path and name of the configuration file to download.
cfg-dst-file specifies the name under which to save the downloaded
configuration file; must contain startup-config
ZTC File Example

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

<sw-version>4.3.50</sw-version>
<sw-action>upgrade-only</sw-action>
</ETX-200>
<ETX-300>
<sw-version>4.3.10</sw-version>
<sw-action>downgrade-only</sw-action>
</ETX-300>
</zero-touch-configuration>
</config>
</edit-config>
</rpc>
Zero Touch via Trap

You can specify that ETX2i send a trap periodically to the management system
to notify it of its existence in the network (by default, this trap is not sent).
To enable sending the trap:

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

Usually, initial configuration of the management parameters is performed via an
ASCII terminal. Once the management flows and corresponding router interface
have been configured, it is possible to access ETX2i via Telnet (IPv4 only),
NETCONF, or SNMP for operation configuration. See Preconfiguring ETX2i for
SNMP Management for an example of management configuration. For details on
configuring the router, refer to the Networking chapter.
3-12 Configuration and Management ETX2i

Table 3-4 summarizes management options for ETX2i.
Table 3-4. Management Alternatives
Port Manager Transport Method Management Application

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

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

only), SSH (see Working with Telnet and SSH
below)
SNMP RADview (see Working with

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

with Third-Party Network
Management Systems below)
NETCONF Third-party NETCONF client
Note
By default, the terminal, Telnet (SSH), NETCONF, and SNMP management access
methods are enabled. See Management Access Methods for details on
enabling/disabling a particular method.
3.6 CLI-Based Configuration
Working with Terminal

ETX2i has a V.24/RS-232 asynchronous DCE port, designated CONTROL, and
terminated in a Mini USB. The control port continuously monitors the incoming
data stream and immediately responds to any input string received through this
port. You can use any terminal emulation program (such as HyperTerminal or
PuTTY) to manage ETX2i via the control port. The following procedure shows
how to start a terminal control session using HyperTerminal.
ETX2i CLI-Based Configuration 3-13

To start a terminal control session:

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

In the Connect To window that opens, in Connect using, select COM1, and
then click OK.
The Com Properties window opens.
In the Com Properties window, configure the following laptop communication
port parameters, and then click OK.
Bits per second (speed) baud rate of 9.6 kbps (9600)
Data bits 8 bits/character
Parity no parity
Stop bits 1 stop bit
Flow control no flow control
3-14 CLI-Based Configuration ETX2i

Figure 3-12. Configuring Laptop Communication Port Parameters

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

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

Figure 3-14. Powering Up Device
Accessing a Remote Terminal

You can access the terminal for the x86 card of D-NFV enabled devices, from the
ETX2i CLI, without the need for a separate terminal.
Characters typed at the ETX2i CLI prompt are redirected to and from either the
local terminal (if managing ETX2i via the control port) or the Telnet/SSH session
(if managing ETX2i remotely) to the x86 host, via the RS-232 connection
between the ETX2i NTU and the x86 card.
Note You can also run a Telnet (IPv4 only) or SSH session directly to the x86 processor.
To access an x86 terminal:

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

Typically, the Telnet/SSH host is a PC or Unix station with the appropriate suite of
TCP/IP protocols. Telnet is supported in IPv4 only.

To enable the Telnet/SSH host to communicate with ETX2i, it is necessary to

configure the ETX2i IP address settings (refer to the Router section for details).
This is usually done via a terminal emulation program (see Working with
Terminal). After this preliminary configuration, you can use a Telnet/SSH host
connected directly or via a local area network.
The following procedure describes how to connect to ETX2i via Telnet. You can
connect to ETX2i via SSH (more secure) using a program, such as PuTTY.
To connect to ETX2i via Telnet:

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

2. Log into the device as explained in Login. See the Using the CLI section for
details on using the CLI commands.
Adding a Telnet Client Session

The ETX2i management system allows you to open an additional Telnet session
(terminal, Telnet, or SSH) to a remote device while you are in an active CLI
management session (Standard IETF RFC 854).
The Telnet client allows you to manage a remote unit without IP connectivity to
the host device. Moreover, the remote unit usually treats the Telnet client traffic
as originating from a secure source (ETX2i). This traffic is unlikely to be filtered
out by an ACL rule of the remote unit, in contrast to non-secure PC traffic.
Network
Telnet RS-232
Remote RAD
Device RAD Device
PC
Figure 3-16. Managing Remote Device, Using Telnet Client Functionality

Source IP Address
The source IP address depends on the location in the CLI tree from which the
Telnet client command is activated:
If the Telnet client command is activated from the router context, the routing
table of the current router defines the IP address that the packets are sent
from.
If the Telnet client command is activated outside the router context, the
routing table of Router 1 defines the IP address that the packets are sent
from.
If the destination IP address is not a valid unicast IP address, ETX2i rejects the
command.
Special Characters
When the client session is open, its parent session passes all special characters
(such as <Ctrl> + <any key>) without parsing or acting upon them. The only
exception is the <Ctrl> + <_> key combination, which closes the client Telnet
session. This allows you to terminate the connection and return to the parent
session if the client session becomes unresponsive, rather than waiting for the
inactivity timeout to end the connection.
Inactivity Timeout
When a Telnet client is used, the inactivity timer of the parent session rearms.
This ensures that as long as the client session is active, its parent session is not
terminated due to an inactivity timeout. Likewise, when the inactivity timer of the
parent session expires, it is terminated together with its client session.
Termination
The client session is terminated if one of the following occurs:
You quit the client session by using the <Ctrl> + <_> key combination. When
this key combination is entered, ETX2i terminates the client session and
returns to the parent session prompt. This is useful when the remote device
stops responding or the connection to it is lost.
You quit the parent session.
The parent session is terminated due to inactivity timeout.
Configuring Telnet Client

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

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

At any level, enter:
<Ctrl> + <_>

ETX2i terminates the client Telnet session and returns to the parent
session prompt.
Viewing Telnet Client Session Information

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

In the configure>management# prompt, enter:
show users-details
The result of the command show users-details is displayed.
The Connected To and the For (sec) fields in the third line for user 123456 detail
the destination IP/ protocol type and duration of the active client Telnet session.
ETX2i# configure management
ETX2i>config>mngmnt# show users-details
User:1234 Level:su Popup:Disabled
From:1.1.1.1/SSH For(sec):120
User:123456 Level:oper Popup:Disabled
From:100.100.100.100/Telnet For(sec):120
Connected To:1111:2222:3333:4444:5555:6666:7777:8888/Telnet For(sec):100
Figure 3-17. Output of users-details
Login
To prevent unauthorized modification of the operating parameters, ETX2i
supports various access levels. Refer to User Access for more information on the
access levels, as well as a list of the default users defined in the device and
information on configuring additional users.
Note The superuser (su) can perform all the activities supported by the ETX2i
management facility.
To log in to ETX2i:
1. At the user prompt (user>), enter the user name and press <Enter>.
The password prompt (password>) appears.
2. Enter the password (default is 1234) and press <Enter>.
The base prompt ETX2i# appears.
Note You can display a banner at login. Refer to the Administration chapter for details.

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

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

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

Note The examples in this manual use # as the last character of the prompt, unless the
creation of a new dynamic entity is being illustrated.
After you type a command at the CLI prompt and press <Enter>, ETX2i responds
according to the command entered.
Navigating
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location. To navigate up, use the global command exit. To
navigate all the way up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed (or not) by a command. If only level names are typed, navigation is
performed and the prompt changes to reflect the current location in the tree. If
the level names are followed by a command, the command is executed, but no
navigation is performed and the prompt remains unchanged.
Note To use show commands without navigating, type show followed by the level
name(s) followed by the rest of the show command.
In the following example, the levels and command were typed together and
therefore no navigation was performed, so the prompt did not change.
ETX2i# configure system date-and-time date-format yyyy-mm-dd
ETX2i# show configure system system-date
2013-06-10 15:08:20 UTC +00:00
ETX2i#
In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
ETX2i# configure
ETX2i>config# system
ETX2i>config>system# date-and-time
ETX2i>config>system>date-time# date-format yyyy-mm-dd
ETX2i>config>system>date-time# exit
ETX2i>config>system# show system-date
2013-06-10 15:13:23 UTC +00:00
ETX2i>config>system#
Full-Path Command
Full-path command allows you to enter a CLI command anywhere in the tree as if
the current level was the CLI root, by preceding the command or level change
with a backslash character. The device executes the command as if it were
invoked from the CLI root.
If you enter a level change (preceded by \) without a command, the CLI does not
return to the prompt of the level that the command was invoked from, but
remains at the changed level. For example, the \configure system command,
when invoked from any level in the CLI tree, returns the
ETX2i>config>system# prompt. However, if you enter a level change followed
by a command, the system performs the command and then returns the prompt

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

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

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

ETX2i>config# tree detail

configure
|
+---access-control
| |
| +---access-list [{ipv4|ipv6}] <acl-name>
| | no access-list <acl-name>
| | |
| | +---delete <sequence-number>
| | |
| | +---deny udp <src-address> [<src-port-range>] <dst-address>
[<dst-port-range>] [dscp <dscp-value>] [log] [sequence
<sequence>]
| | | deny tcp <src-address> [<src-port-range>] <dst-address>
[<dst-port-range>] [dscp <dscp-value>] [log] [sequence
<sequence>]
| | | deny icmp <src-address> <dst-address> [icmp-type <icmp-type-
number>]
[icmp-code <icmp-code-number>] [dscp <dscp-value>] [log]
[sequence <sequence>]
| | | deny ip [protocol <ip-protocol-number>] <src-address> <dst-
address>
Press <Enter> to see more or <CTRL-C> to return to the prompt.
Command Structure
CLI commands have the following basic format:
command [parameter]{ value1 | value2 | | valuen } [ optional-parameter
<value> ]
where:
{} Indicates that one of the values must be selected

[] Indicates an optional parameter
<> Indicates a value to be typed by the user according to
parameter requirements
You can type only as many letters of the level, command, or parameter as
required by the system to identify it. For example, you can enter config manag to
navigate to the management level.
Special Keys
The following keys are available at any time:
? List all commands and levels available at the current level.

<Tab> Command-line completion; complete the unambiguous
characters of the command, and display a list of available
commands beginning with those characters (as when
pressing ?).
Display the previous command (history forward).

Display the next command (history backward).

<Backspace> Delete character before cursor.
<Delete> Delete character before cursor.
<- Move cursor one character left.
-> Move cursor one character right.
<Alt>+B, <Esc>+B Move cursor left one word (or go to start of word).
<Alt>+D, <Esc>+D Delete until end of word starting from the cursor.
<Alt>+F, <Esc>+F Move cursor right one word (or go to end of word).
<Ctrl>+<_> Exit CLI.
or
<Ctrl>+<Shift>+<->
<Ctrl>+A Move cursor to start of line.

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

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

<Ctrl>+U Delete text up to cursor.
<Ctrl>+W Delete word to the left of cursor.
<Ctrl>+Y Paste text last deleted by a shortcut.
<Ctrl>+Z Navigate to base level.
Getting Help
You can get help in the following ways:
Type help to display general help (see General Help).
Type help <command> to display information on a command and its
parameters (see Command Help).
Type ? to display the commands available in the level (see Level Help).
Use <Tab> while typing commands and parameters, for string completion
(see Command-Line Completion).

Use ? after typing a command or parameter, for interactive help (see

Interactive Help).
General Help
Enter help at any level to display general CLI help, including:
Short description of CLI interactive help
Commands and levels available at the current level
Globally available commands
CLI special keys (hotkeys)
Output modifiers for filtering output
URLs for device manual and shelf view manual
Example of help command output from the root level:

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

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

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

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

ETX-2 Shelf View User's Manual : http://goo.gl/RJTLDc
Command Help
Enter help <command> to display command and parameter information.
ETX2i>config>system# help name
- name <name-of-device>
- no name
<name-of-device> : Adds free text to specify the device name [0..255 chars]
Level Help
Enter ? at the command prompt to display the commands available in the current
level.
ETX2i>file# ?
delete - Delete file
dir - Display file directory
show banner-text - Display banner

show configuration-files - Display configuration files
properties
show copy - Display Copy progress
show factory-default-config - Display factory-default-config
show rollback-config - Display rollback-config
show schedule-log - Display schedule-log
show startup-config - Display startup-config
show sw-pack - Display SW packs
show user-default-config - Display user-default-config
Command-Line Completion
Command-line completion saves you command-line entry time and reminds you
the syntax of command-line entities (levels, commands, parameters, flows, and
profiles).
In a command-line, ETX2i completes command-line entities, when you press
<Tab> immediately following a string (one or more characters).
Some user-defined entity names, such as flow names or profile names, can be
completed as well. If you enter an entity name (flow, profile, or similar) that does
not exist in the database, ETX2i creates this entity with the selected name.

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

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

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

This is a new flow, as my-flow-3
did not exist before.
Interactive Help
To get interactive help, type ?.
In general, typing a ? directly after a string displays possibilities for string
completion, while typing <space> and then a ? displays possibilities of the next
argument.
When a <CR> appears in a ? list, the string you entered is itself a valid command
needing no further additions. Pressing <Enter> executes the command or
navigates to the indicated level.

Typing ? immediately after a command or partial command with no space before

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

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

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

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

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

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

When executing scheduled commands, ETX2i assumes a Yes answer for any
confirmation questions. When a scheduled command is executed, it is sent to
TACACS+ and Syslog accounting, as if it were executed by a CLI user.

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

You can view the following scheduled information:
Commands, with or without details of the commands
Daylight saving time (For an explanation on the configuration of daylight
saving time, refer to the Daylight Saving Time section in Chapter 9.)
Note You can also enter the info command from the root of the device to view all
commands of the device, including scheduled commands (see Viewing the Device
Configuration section below).

To view scheduling without command details:

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

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

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

Type : Once (In)
Permanent : No
Finished : No
Activation In(Seconds) : 207 days 12:45:00
Command: copy log tftp://1.1.1.1
Summer Time
Start (Recurring): Last Sunday of May, 02:00
End (Recurring): Last Thursday of October, 02:00
Offset : 60 minutes
Start : 31 May 2015 12:21
End : 29 October 2015 12:21
Table 3-6. Scheduling Display Parameters
Parameter Description
Current date Current date and time, and current offset from UTC

Schedule Name Name of schedule
Type Type of schedule:

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

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

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

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

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

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

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

Auto Negotiation : Other

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

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

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

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

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

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

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

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

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

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

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

command):
ETX2i# info
.
Bridge Configuration
bridge 1
name "BRIDGE 1"
echo "Bridge Port Configuration"
# Bridge Port Configuration
port 1
spanning-tree
cost 10
no shutdown
exit
no shutdown
exit
port 2
spanning-tree
cost 20
no shutdown
exit
no shutdown
exit
.
schedule "sched1" in 5 "configure flows flow v100in shutdown"
ETX2i#
3.7 Management Access Methods

You can enable or disable access to the ETX2i management system via Telnet
(IPv4 only), SSH, NETCONF, or SNMP applications. By disabling Telnet, SSH,
NETCONF, or SNMP, you prevent unauthorized access to the system when security
of the ETX2i IP address has been compromised. When Telnet, SSH, NETCONF, and
SNMP are disabled, ETX2i can be managed via an ASCII terminal only. Additionally,
you can enable or disable file transfer via SFTP/TFTP.
3-38 Management Access Methods ETX2i

Applicable Products
This feature is applicable to all ETX2i products.
Functional Description
Two types of ETX management access are supported:
Inband ETX host (management RI) resides directly over one or two VLANs in
a specific port or over a Bridge port (for example, to allow management
access in a Ring topology).
MNG RI
(ETX Host)
Router NNI
Figure 3-18. ETX Host over VLANs
Ring Port East
NNI
MNG RI
(ETX Host)
Router Bridge Bridge Port
Ring Port West
NNI
Figure 3-19. ETX Host over Bridge Port

Out-of-band (OOB) MNG access via OOB port is supported to access the device
host only, and not the management VLAN Bridge domain.
Factory Defaults
By default, access is enabled for all the applications.
In the default factory configuration, ETX2i allows management from the OOB
management port.
The default factory configuration includes the following:
Allows untagged management access from the OOB port
Default IP address of the Router Interface is 169.254.1.1/16
No default Gateway configuration
Allows local management access using a PC to an out of the box ETX2i
device:
ETX2i Management Access Methods 3-39

When PC uses DHCP, access to ETX2i device is automatically established

(PC address defaults to 169.254.x.y as no DHCP server Microsoft
protocol).
Default configuration includes flows to and from an SVI Router and a Router
Interface with a fixed and set IP address
SVI, RI, and flow are assigned with indexes at the end of the device range and
reserved flow names (to coexist with existing scripts).
SVI #: 100
RI #: 100
Flows: mng_access_default_in, mng_access_default_out
Not backward compatible to user configuration CLI scripts that configure OOB
port
Figure 3-20. Untagged Management Access from OOB MNG Port

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

This section describes how to configure general management parameters.
Note There is no explicit configuration for inband and outband management access.
To configure management access:

At the configure management access prompt enter the necessary commands
according to the tasks listed below.
Task Command Comments
Allowing SFTP access sftp Typing no sftp blocks access by SFTP.
3-40 Management Access Methods ETX2i

Allowing SSH (Secure Shell) access ssh Typing no ssh blocks access by SSH.
Allowing SNMP access snmp Typing no snmp blocks access by SNMP.
Allowing Telnet access (for IPv4 only) telnet Typing no telnet blocks access by Telnet.
Allowing TFTP access tftp Typing no tftp blocks access by TFTP.
3.8 Resetting Unit to Default

ETX2i has an external push button for setting the units software to its default.
The unit is restored to its factory default.
If the user default has been configured, the unit boots up with the user-
default-config file.
To reset the unit to its default configuration:

While the unit is up and running, press and hold the push button for five
seconds.
3.9 Turning Off the Unit

To power off the unit:
Remove the power cord from the power source.
3.10 SNMP-Based Network Management

Simple Network Management Protocol (SNMP) is an application layer protocol
that provides a message format for communication between managers and
agents.
ETX2i supports SNMPv3, the latest SNMP version to date. SNMPv3 provides
secure access to devices in the network by using authentication and data
encryption.
Applicable Products
Standards
The supported SNMP versions are based on the following standards:
ETX2i SNMP-Based Network Management 3-41

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
RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework. SNMPv2 Working Group
RFC 2104, Keyed Hashing for Message Authentication
RFC 2271, Architecture for Describing SNMP Management Frameworks
RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP)
RFC 2273, SNMPv3 Applications
RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3)
RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
RFC 3412, Version 3 Message Processing and Dispatching
RFC 3414, User-based Security Model for SNMPv3
RFC 3416, Update for RFC 1904
Benefits
SNMP allows you to remotely manage multiple units from a central workstation
using a network management system.
SNMPv3 allows data to be collected securely from SNMP devices. Confidential
information such as SNMP commands can thus be encrypted to prevent
unauthorized parties from being able to access them.
In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which reports information via SNMP back to the
managing workstations.
3-42 SNMP-Based Network Management ETX2i

Factory Defaults
The following is the default configuration of the SNMP parameters (see
Configuring SNMPv3 Parameters for explanations of the parameters):
SNMP engine ID set to device MAC address
View named internet providing access to IETF MIBs and IEEE MIBs
User named "initial", with security level no authentication and no privacy
Group for SNMPv3 named "initial":
Security levels no authentication and no privacy, authentication and no
privacy, authentication and privacy
User initial
Views for read/write/notify "internet"
Notifications with tag unmasked for the device traps
Configuring SNMPv3 Parameters

SNMP version 3, provides secure SNMP access to the device by authenticating and
encrypting packets transmitted over the network.
The SNMPv3 manager application in RADview-EMS provides a user-friendly GUI
interface to configure SNMPv3 parameters. If you intend to use it, you must first
use the device CLI to create users with the required encryption method and
security level, as the application can create users based only on existing users;
the new user has the same encryption method, and the same security level or
lower. The ETX2i default configuration provides one standard user named
initial with no encryption and the lowest security level (see Factory Defaults for
details).
A Network Management Station (NMS) relies on traps in order to display device
alarms. As traps are not reliable, the NMS needs to be aware which traps got lost
and be able to ask a device to resend them. This mechanism is called trap
synchronization.
NMSs (targets; such as RADview or third party) may be organized into trap sync
groups in order to provide redundancy between these NMSs. You can define the
tags and target parameters in each trap sync group for example, you can define
one trap sync group for critical alarms such as linkDown and coldStart, and
another group for all other traps.
Each trap is sent to all targets attached to the group, and therefore it is
recommended to set identical traps masking for all group members.
Notes ETX2i supports up to two trap synchronization groups.

A single trap synchronization group can support multiple NMS.
If you would like all NMS to receive all traps, there is no need to configure trap
synchronization groups.
Follow this procedure to configure SNMPv3:

1. Set SNMP engine ID if necessary.
2. Add users, specifying authentication protocol and privacy protocol.

3. Add groups, specifying security level, protocol, and views.

4. Connect users to groups.
5. Add notification entries with assigned traps and tags.
6. Configure target parameter sets to be used for targets.
7. Configure targets (SNMPv3 network management stations to which ETX2i
should send trap notifications), specifying target parameter sets, notification
tags, and trap synchronization groups if applicable.
To configure SNMPv3 parameters:
2. Enter all necessary commands according to the tasks listed below.
Note When you enter password parameters, they should contain at least eight
characters.
Task Command Level Comments
Configuring access-group <group-name> { snmpv2c | usm } snmp Using no access-group

group { no-auth-no-priv | auth-no-priv | auth-priv } deletes the group.
Defining how to context-match {exact | prefix} snmp>access-group exact Match the

match the entire context.
context sent in prefix Match the first
frames by the part of the context.
NMS
Note: ETX2i
automatically identifies
the NMS context,
therefore you can
configure exact match.
Normally prefix is used
for devices with
multiple instances.
Setting view for notify-view <name> snmp>access-group See the description of

traps the view command for
information on how to
Setting view read-view <name> snmp>access-group
limit the parts of the
with read-only
MIB hierarchy that the
access
view can access.
Setting view write-view <name> snmp>access-group
with write
access
Administratively no shutdown snmp>access-group Using shutdown

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

community
Configuring name <community-string> snmp>community

name

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

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

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

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

notification
Assigning trap bind <trap-name> snmp>notify You can assign more

to notification than one trap to a
notification, in
separate commands.
Assigning tag to tag <tag-value> snmp>notify

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

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

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

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

Defining type {included | excluded} snmp>notify-filter included Traps

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

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

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

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

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

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

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

enabling disables the
security-to-grou security-to-group
p entity entity.

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

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

target address address oam-domain <oam-port>
as IP address or
OAM port
Assigning tag(s) tag-list <tag> snmp>target If you specify more

to target (the tag-list [ <tag> ] than one tag, you must
tag(s) must be enclose the list in
tag-list [ <tag1> <tag2><tagn> ]
defined in quotes; however, if you
notification are specifying just one
entries) tag, the quotes are
optional.
Specifying set target-params <params-name> snmp>target

of target
parameters for
target

Specifying the trap-sync-group <group-id> snmp>target If the group does

trap not exist, it is
synchronization created.
group to be Enter no
associated with trap-sync-group
the SNMP <group-id> to
target (NMS) remove the
manager (NMS)
from the group. If
the removed
manager was the
last to be
associated with the
trap-sync-group,
the group is
automatically
deleted.
ETX2i supports up
to two trap
synchronization
groups.
Administratively no shutdown snmp>target Using shutdown

enabling target disables the target.
Configuring set target-params <target-param-name> snmp Using no target-params

of target removes target
parameters, to parameters.
be assigned to
target
Specifying message-processing-model { snmpv2c | snmpv3 } snmp>target

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

on whose [ level { no-auth-no-priv | auth-no-priv | auth-priv } ]
behalf SNMP
messages are
to be generated
for the set of
target
parameters

Specifying version { snmpv2c | usm } snmp>target Use usm for SNMPv3

SNMP version to version.
be used when
generating
SNMP messages
for the set of
target
parameters

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

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

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

of target target parameters,
parameters in enter: no
trap-sync-group target-params
<params-name>.
Configuring user user <security-name> snmp If you dont specify the

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

authentication [ key <key-change> ] no authentication
password and disables the
optional key for authentication
changes protocol.

Setting user privacy [ password <password> ] [ key <key-change> ] snmp>user Using no privacy
privacy disables privacy
password and protocol
optional key for Note: Password
changes minimum length is 10
for AES128 and 8 for
DES.
Administratively no shutdown snmp>user You must define the

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

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

specify a mask if
Defining type {included | excluded} snmp>view included Allow access

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

enabling view

Displaying trap show trap-sync snmp

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

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

exit all
configure management snmp
#********* Configure user MD5_priv with authentication method MD5 with DES privacy protocol
user MD5_priv md5-auth des
privacy password MD654321
authentication password MD654321
no shutdown
exit
#******** Configure access group MD5Group with various authentication and privacy options
access-group MD5Group usm no-auth-no-priv
context-match exact
read-view internet
write-view internet
notify-view internet
no shutdown
exit
access-group MD5Group usm auth-no-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit
access-group MD5Group usm auth-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit
#******** Connect user MD5_priv to group MD5Group

security-to-group usm sec-name MD5_priv
group-name MD5Group
no shutdown
exit all
save
To create notifications:
Notification named TrapPort:
Tag=Port
Bound to ethLos, sfpRemoved
Notification named TrapPower:
Tag=Power
Bound to powerDeliveryFailure, systemDeviceStartup
exit all
#******** Configure notification TrapPort
notify TrapPort
tag Port
bind ethLos
bind sfpRemoved
no shutdown

exit
#******** Configure notification TrapPower

notify TrapPower
tag Power
bind powerDeliveryFailure
bind systemDeviceStartup
no shutdown
exit all
save
To create target parameters and target:

Target parameters named TargParam1:
Message processing model SNMPv3
version USM
User MD5_priv
Security level authentication and privacy
Target named TargNMS1:
Target parameters TargParam1
Tag list=Port, Power
IP address 192.5.4.3
exit all
#******** Configure target parameters TargParam1
target-params TargParam1
message-processing-model snmpv3
version usm
security name MD5_priv level auth-priv
no shutdown
exit
#******** Configure target TargNMS1

target TargNMS1
tag-list port power
address udp-domain 192.5.4.3
no shutdown
exit
To create communities, target parameters, and target for network devices that
are working with SNMPv1:
Community read:
Name: public
Security name: v1_read (defined in default configuration)
Community write:
Name: private
Security name: v1_write (defined in default configuration)
Community trap:

Name: public
Security name: v1_trap (defined in default configuration)
Target parameters named snv1:
Version SNMPv1
Security name: v1_trap
Security level: no authentication and no privacy
Target named NMSsnmpv1:
Target parameters snv1
Tag list=unmasked
exit all
#******** Configure communities
snmpv3
community read
name public
sec-name v1_read
no shutdown
exit
community write
name private
sec-name v1_write
no shutdown
exit
community trap
name public
sec-name v1_trap
no shutdown
exit
#******** Configure target parameters

target-params snv1
version snmpv1
security name v1_trap level no-auth-no-priv
no shutdown
exit
#******** Configure target

target NMSsnmpv1
target-params snv1
tag-list unmasked
no shutdown
exit all
save
To display SNMPv3 information:

ETX2i# configure management snmp

ETX2i> config>mngmnt>snmp# show snmpv3 information

SNMPv3 : enable
Boots : 2
Boots Time (sec) : 102
EngineID : 800000a4030020d2202416
To configure trap synchronization:

Trap synchronization group 1:
Members NMS1 and NMS2
Target parameters TargParam1 (from previous example)
Tag list=Port, Power (from previous example)
exit all
#******** Configure targets and trap synchronization group
target NMS1
trap-sync-group 1
exit
target NMS2
trap-sync-group 1
exit
target NMS3
trap-sync-group 2
exit
target NMS4
trap-sync-group 2
exit
trap-sync-group 1
tag-list port power
exit all
save
To display trap synchronization configured in above example:

ETX2i>config>mngmnt>snmp# show trap-sync
Group ID Member
---------------------------------------------------------------
1 NMS1
1 NMS2
2 NMS3
2 NMS4
Preconfiguring ETX2i for SNMP Management

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

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

parameters using a supervision terminal connected to the ETX2i CONTROL DCE
port.
To configure ETX2i for management access:

Add an SVI port.
Create classifier profiles for matching all traffic and matching untagged
traffic.
Add two flows (incoming and outgoing) connecting the out-of-band Ethernet
Add a router interface, bind it to the SVI, and add a static route to the next
hop.
The following script provides the necessary configuration steps for ETX2i, ETX-2i-
B, and ETX-2i-10G. Replace IP addresses and entity names with values suitable
for your network environment.
#*******************************Adding_SVI*********************
config port
svi 99
no shutdown
exit all
#***************************Adding Classifier_Profiles*********
config flows
#***************************Configuring_Flows******************
flow mng_in
classifier untagged
no policer
ingress-port ethernet 0/101
egress-port svi 99
no shutdown
exit
flow mng_out
classifier all
ingress-port svi 99
egress-port ethernet 0/101 queue 0 block 0/1
no shutdown
exit all
#*********************Configuring_Router_Interface*************
configure router 1
interface 1
bind svi 99
address 172.18.141.39/24
no shutdown
exit
exit all
save

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

You can discover services via RADview, and view statistics for services and ports
in the RADview Performance Monitoring portal. This also allows you to ensure
that SLAs are being met. In order to do so, you need to perform the following:
Configure service with parameters that enable RADview to recognize the
flows that correspond to the service, as follows:
Configure Rx and Tx traffic flows with the same service ID.
Assign the above Rx and Tx flows to the MEP corresponding to the
service.
Note The service name configuration is necessary only in the endpoint devices.
Enable PM collection for the Rx and Tx flows, as well as for the corresponding
destination NE.
All flows belonging to the same service End Point must use the same port.
Only one S-tag should be used for the service.

Run the RADview Discovery Service function (refer to the RADview online
help).
Discovery can be performed only on the user port (UNI). For more information,
refer to the Performance Management section.
Note Multi-port E-Line services can't be discovered and statistics can't be collected on
the flows.
Working with Shelf View

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

ETX2i can be integrated into third-party network management systems at the
following levels:
Viewing device inventory and receiving traps (refer to the Monitoring and
Diagnostics chapter for trap list)
Managing device, including configuration, statistics collection, and
diagnostics, using the following standard and private MIBs:
CFM MIB (IEEE8021-CFM-MIB)
IANAifType-MIB
IETF Syslog Device MIB
IEEE8023-LAG-MIB
MEF-R MIB
RAD private MIB
RFC 2819 (RMON-MIB)
RFC 2863 (IF-MIB)
RFC 3273 (Remote Network Monitoring MIB)
RFC 3411 (SNMP-FRAMEWORK-MIB)
RFC 3413 (SNMP-TARGET-MIB)
RFC 3414 (SNMP-USER-BASED-SM-MIB)
RFC 3415 (SNMP-VIEW-BASED-ACM-MIB)
RFC 3418 (SNMPv2-MIB)
RFC 3433 (ENTITY-SENSOR-MIB)
RFC 3636 (MAU-MIB)
RFC 4133 (ENTITY-MIB)

RFC 4668 (RADIUS-AUTH-CLIENT-MIB)

RFC 4836.MIB (MAU-MIB)
RFC 4878.MIB (DOT3-OAM-MIB)


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

This section describes the managed elements that need to be configured during
service provisioning.
Service provisioning elements are as follows:
Profiles
Scheduling and shaping entities
Physical ports (E1/T1/T3 (depending on product), Ethernet)
Logical ports (LAG, logical MAC, PCS (for ETX2i with an SHDSL or VDSL2
module), and SVI)
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 4-1. Profile Types
Profile Type Applied to Description
L2CP Ethernet/logical MAC port, Defines actions for L2CP processing (drop, peer,
PCS flow tunnel, and tunnel with MAC swap)
Classifier Flow Defines criteria for flow classification
CoS mapping ETP/bridge flow/MultiCoS Defines method and values for mapping packet
flow (10.3 policer) attributes (P-bit, DSCP, IP precedence) to internal
CoS values
Color mapping Flow Defines method and values for mapping packet
attributes (P-bit, DSCP, IP precedence) to internal
color values
ETX-2i Service Entities 4-1

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

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

probabilities
Scheduling and Shaping Entities

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

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

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

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

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

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

Interface (SVI)
Forwarding Entities
Several internal entities carry traffic and make forwarding and switching
decisions. These are:
Flows Traffic-forwarding interconnection elements
Bridge
Router
Flows
Flows are entities that interconnect two physical or logical ports. Flow processing
is performed as follows:
Ingress traffic is mapped in flows using classification match criteria defined
via a classification profile.
L2CP frames are handled per flow according to L2CP profile settings.
User priority (P-bit, IP Precedence, DSCP) is mapped into internal queue
according to a queue mapping profile or assignment per flow.
ETX-2i Service Entities 4-3

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

Ingress Egress bridge

Classification Flow
Ethernet port port
5) Ethernet ports 2) Classification 3) Marking 1) Bridge ports
4) CoS mapping
6) Flows
Figure 4-1. E-LAN Traffic Data Flow Ethernet to Bridge
Table 4-2. E-LAN Traffic Configuration Ethernet to Bridge
Sequence Step Commands Comments
1 Configuring the Bridge port

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

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

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

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

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

Ingress bridge Queueing Queueing Egress

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

shutdown

Profile match criteria for the flow.

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

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

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

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

color non-default WRED configuration for
the queue blocks

ingress or egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
4-6 E-LAN Service ETX-2i

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

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

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

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

compensation
incoming traffic of the
ETX-2i E-Line Service 4-7


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

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

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

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

ingress or egress port
classifier-key
max-capability
speed-duplex
queue-group
egress-mtu
tag-ethernet-type
shutdown
ingress-port traffic from the user port to the
network port.
egress-port
policer
mark
vlan-tag
shutdown
Network to User
In Figure 4-4, the rectangles illustrate the data flow for Ethernet user traffic from
a network port to a user port. The rounded rectangles indicate the features that
4-8 E-Line Service ETX-2i

Queueing
Ingress NNI Classification Flow Policing Shaping Egress UNI
level 0
9) Ethernet ports 1) Classification 2) Marking 4) Policing 6) Queue blocks 5) Shaping 8) Queue groups
3) Queue mapping 7) WRED 9) Ethernet ports
10) Flows
Figure 4-4. E-Line Traffic Data Flow Network to User
Table 4-5. E-Line Traffic Configuration Network to User

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

for the network-to-user flow

network-to-user flow

compensation

compensation
network-to-user flow (via attaching

the network-to-user flow
scheduling
depth

the queue blocks

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


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

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

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

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

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

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

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

for the network-to-user flow


compensation

the network-to-user flow
scheduling
depth

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

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

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

name
profile
shaper

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

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

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

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

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

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

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

for the user-to-network flow


compensation

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

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

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

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

name
profile
shaper

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

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

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

To view the service information:

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

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

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

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

Test Status : Off

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

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

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

Chapter 5
Cards and Ports
This chapter describes card and port-related features:
Note
Ports are referenced generally as [<slot>/]<port>[/<tributary>]:
<slot> = 1 for modular ports
<slot> = 0 for non-modular ports
<tributary> is required only for smart SFP E1/T1/E3/T3/SDH/SONET ports,
and is always set to 1.
5.1 Cards
This section describes how to configure the module type (card type) for the
modular option.
Benefits
The ability to preprovision the module type before actually inserting the module
provides more flexibility.
The ETX-2i module can contain ports of type GbE, E1, T1, T3, VDSL2, or SHDSL; or
it can contain an optional embedded router. You can preprovision the module
type before physically inserting the module. The configured module type must
match the actual module installed, for correct operation.
When ETX-2i starts up, it verifies that the configured module type matches the
module that is installed. If they do not match, the card_mismatch alarm is sent.
The ETX-2i module is defined as slot 1, therefore the ports on the module are
referenced with slot 1. The device ports that are not on the module are
referenced with slot 0.
Note The ETX-2i module is not hot swappable; it can be removed/replaced only when
ETX-2i is powered off.
Factory Defaults
By default, the module type is set according to the module type that is actually
installed.
ETX-2i Cards 5-1

Chapter 5 Cards and Ports Installation and Operation Manual
Configuring Module
Note You can display the module type from the device level by typing
show cards-summary.
To configure the module:

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

interfaces the module interfaces.
Resetting module SW reset Supported for VDSL only
Displaying module status show status
5.2 Ethertype
Ethertype tag configuration of a packet allows identification of incoming and
outgoing VLAN-tagged packets.
Ethertype (tag protocol ID, or TPID) configured per port is used for:
5-2 Ethertype ETX-2i

Installation and Operation Manual Chapter 5 Cards and Ports
Identification of (outer) VLAN-tagged packets at ingress

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

Table 5-1. Ports with Configured Port TPID Y (Tag Ethertype port configuration)
Outer TPID Inner TPID Admit/Drop Recognized Tag Levels
Y None Admit 1
Y Any one of the four Admit 2
device-level global
TPIDs
Y None of the four Admit 1

device-level global
TPIDs
Z (other than Y) Dont care Admit Untagged
None Admit Untagged
Configuring Ethertype
ETX-2i comes preconfigured with two global Ethertype tag values 8100 and
88a8. These Ethernet tag values cannot be modified or deleted.
You can configure an additional two global Ethertype tags so that they can be
used in Ethertype tag configuration of a packet or port.
If additional tag values are not defined, the port and packet can only use the
default global values 88a8 and 8100.
To configure the Ethertype tag at the device level:

1. Navigate to config>port.
2. Enter tag-ethernet-type <0x0000-0xFFFF>.
You can use no before tag-ethernet-type to remove the two additional user-
configurable Ethertype tag values. You cannot remove the fixed 8100 and 88a8
Note
values.
Example
To configure a port with global Ethertype tag 0x88a8:
ETX-2i>config>port>tag-ethertype 0x88a8
To configure a port with global Ethertype tag 0x88a4:

ETX-2i>config>port>tag-ethertype 0x88a4
The following table lists the messages generated by ETX-2i when a configuration
error is detected.
5-4 Ethertype ETX-2i

Message Description
Modify failed: Ethertype tag value is in The Ethertype tag value cannot be changed because it is
use currently used by a port of a flow.
Invalid port Ethertype tag value The Ethertype tag value for a port cannot be configured to the
default value (0x8100), and cannot be different from the one
configured at system level.
Cannot delete default Ethertype tag The default Ethertype tag value (0x8100) cannot be deleted.
value
Delete failed: Ethertype tag value is in The Ethertype tag value cannot be deleted because it is
use currently being used by a port of a flow.
Setting failed: Ethertype tag value is The Ethertype tag value for a port or a flow is different from the
unknown one configured at system level.
Ethertype tag cannot be modified for a The Ethertype tag value is in use by the LAG.
port attached to LAG
5.3 GFP Ports
Standards
G.7041
Benefits
GFP logical ports provide a logical link to smart SFP E1/T1/T3/SDH/SONET ports or
modular E1/T1/T3 ports.
ETX-2i uses GFP (Generic Framing Procedure) ports to provide a logical link to the
TDM ports that become available when smart SFPs are inserted (see Smart SFPs),
or an E1/T1/T3 module is installed.
ETX-2i supports up to four GFP ports when inserting up to four Smart SFPs
(MiRICs) into the device ports.
When using the GFP module (ETX2i), up to eight E1/T1 or two T3 can be
supported in a single GFP VCAToPDH group.
Notes If a module with multiple E1/T1/T3 ports is installed, the GFP port is bound to
the VCG port that is bound to the E1/T1/T3 ports.
If a module with a single T3 port is installed, the GFP port is bound directly to
the T3 port.
ETX-2i GFP Ports 5-5

Factory Defaults
By default, no GFP ports exist. When a GFP port is created, it is configured as
shown below.
Parameter Default Remarks
name GFP <port>
scrambler-payload rx-tx Scrambling on the GFP packet payload in

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

is disabled.
Configuring GFP Ports

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

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

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

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

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

Enabling/disabling VLI byte vcat-header Note: Not relevant to GFP port bound
insertion on VCAT trunk or PDH to SDH/SONET port, modular T3 port,
or VCG port.
Displaying a list of interfaces show bind Lower level binds to E1.

bound to the port Higher level binds to VCG.
Displaying GFP port statistics show statistics
Clearing port statistics clear-statistics
Displaying GFP port status show status Operation Status:

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

To display the status of GFP logical port 3:

ETX-2i# config port gfp 3
ETX-2i>config>port>gfp(3)# show status
Name : GFP 3
5.4 Internal Ports for x86 Interconnection

Two predefined internal Ethernet ports are used for interconnection between the
ETX-2i NID and x86 processor, if applicable.
Ethernet 1, interconnected to ETX-2i internal Ethernet port 8
Ethernet 2, interconnected to ETX-2i internal Ethernet port 7
Note
For ETX2i with D-NFV option, regular user ports 7 and 8 are not available.
Applicable Products
This feature is applicable to ETX2i with the D-NFV option.
Benefits
The internal ports enable interconnection with the x86 processor.
Factory Defaults
By default, the internal Ethernet ports have the following configuration.
Parameter Description Default Value
dhcp-trust Trust server DHCP packets Disabled (trust client DHCP

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

Bridge port
Ethernet port
ETP Subscriber port
LAG
You cannot configure flows between the internal Ethernet ports and the
following types of ports:
ETP subscriber port
SVI assigned to router interface
Configuring the Internal Port Parameters

The internal ports are referred to in the CLI as int-ethernet <port-num>, where
<port-num> is 7 or 8.
To configure the internal port parameters:
1. Navigate to configure port int-ethernet <port-num> to select the internal
port to configure.
The config>port>int-eth(<port-num>)# prompt is displayed.
Configuring port to trust DHCP packets dhcp-trust Client ports must always be untrusted
sent from server (no dhcp-trust); otherwise, the DHCP relay
discards the discovery messages sent from
the client port to the server.
Relevant only if DHCP snooping is enabled.
Assigning description to port name <string> Entering no name removes the name.
Associating a queue group profile with queue-group profile

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

Logical MAC ports are used to connect E1/T1/T3 ports to flows.
Benefits
The logical MAC ports connect between flows and GFP ports.
ETX-2i Logical MAC Ports 5-9

ETX-2i uses logical MAC ports to connect flows to GFP (Generic Framing
Procedure) ports that provide a logical link to modular E1/T1/T3 ports, or to the
TDM ports that become available when smart SFPs are inserted (see Smart SFPs).
In the case of modular E1/T1/T3 ports, the logical MAC port can operate as a
network or user port (user configurable).
Factory Defaults
By default, no logical MAC ports exist. When a logical MAC port is created, it is
configured as shown below.
Description Default Value
Port name LOGICAL MAC <logical-mac-port-number>
Administrative status Disabled
Trust server DHCP packets Disabled
Port to which the logical MAC is bound GFP 5
Ethernet tag protocol identifier 08100
Egress MTU 1790
Functional mode Network
Queue group profile DefaultQueueGroup
L2CP profile L2cpDefaultProfile
Configuring Logical MAC ports

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

Specifying classification key per port classification-key [legacy] legacy No classification key is
[vlan] [inner-vlan] used.
vlan Classification key
according to VLAN
inner-vlan Classification key
according to VLAN + Inner
VLAN
Valid for flow classifier only.
You can change the port
classification key only if all
flows using this port are
administratively disabled.
See the relevant table In the
Classification Keys section
below to see the queue/priority
mapping methods for the
selected classification key, as
well as the flows / flow
parameters that can be
configured for the key.
Configuring port classification classifier See Configuring Port

Classification.
Configuring port to trust DHCP packets dhcp-trust Client ports must always be
sent from server untrusted (no dhcp-trust);
otherwise, the DHCP relay
discards the discovery
messages sent from the client
port to the server.
Relevant only if DHCP snooping
is enabled.
Configuring OAM EFM descriptor efm descriptor See Configuring OAM EFM.
<efm-descriptor-index>
Setting maximum frame size to transmit egress-mtu <size> Maximum size is 12,288.
(frames above the specified size are
discarded)
Configuring the functional mode functional-mode {user |

network}
Associating a Layer-2 control processing l2cp profile

profile with the port <l2cp-profile-name>
Configuring LLDP parameters lldp See Link Layer Discovery

Protocol (LLDP) for details.
Running loopback test on port loopback {local|remote} Use the no loopback command
[duration <seconds>] to stop the test.
ETX-2i Logical MAC Ports 5-11

Associating a policer profile with the policer profile

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

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

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

port.
Displaying the interfaces that are bound show bind

to the port
Displaying link OAM (EFM) parameters show oam-efm
Displaying OAM EFM statistics show oam-efm-statistics
Displaying L2CP statistics show l2cp-statistics
Clearing OAM EFM statistics clear-efm-statistics
Clearing L2CP statistics clear-l2cp-statistics
Clearing port statistics clear-statistics
To change the logical MAC port back to ETH:

no logical-mac <port>
The port mode changes from Logical MAC to ETH.
The config>port>eth([<slot>/]<port-num>)# prompt is displayed.
2. Type shutdown and then no shutdown.
The ETH port hardware is disabled and then enabled, synchronizing the
ETH port, provided that line/cable/fiber is connected.
5-12 Logical MAC Ports ETX-2i

Examples
To configure logical MAC port 3:
Bind to GFP port 3.
exit all
logical-mac 3
bind gfp 3
no shutdown
exit all
To display information on logical MAC port 3:
ETX-2i>config>port# logical-mac 3
ETX-2i>config>port>log-mac(3)# info detail
name "LOGICAL MAC 3"
no shutdown
bind gfp 3
tag-ethernet-type 0x8100
egress-mtu 1790
queue-group profile "DefaultQueueGroup"
l2cp profile "L2cpDefaultProfile
ETX-2i>config>port>log-mac(3)# show status

Name : LOGICAL MAC 3
Operational Status : Up
5.6 PCS Ports

The PCS port is the logical link to modular SHDSL or VDSL2 ports.
Applicable Products
This feature is applicable to ETX2i with an SHDSL or VDSL2 module.
Standards
ITU-T G.991.2
ETSI TS 101524
Benefits
You can create flows over the PCS port.
The PCS (physical coding sublayer) port represents the bundling of the modular
SHDSL/VDSL2 interfaces. By default, all SHDSL/VDSL2 lines are bound to a single
PCS port. The PCS port can operate as a network or user port (user configurable).
ETX-2i PCS Ports 5-13

Factory Defaults
The PCS port default configuration is shown below.
Port name PCS 1
Administrative status Enabled
Classification key Legacy
DHCP trust no dhcp-trust
Ethernet tag protocol identifier 08100
Egress MTU 1790
Functional mode Network
OAM EFM Disabled
Queue group profile DefaultQueueGroup
L2CP profile L2cpDefaultProfile
Policer profile None
Configuring the PCS Port Parameters

To configure the PCS port parameters:
1. Navigate to configure port pcs <port> to select the PCS port to configure.
The config>port>pcs(<port>)# prompt is displayed.
Specifying classification key per port classification-key [legacy] [vlan] [inner- legacy No classification key is used.
vlan] vlan Classification key according to VLAN
inner-vlan Classification key according to
VLAN + Inner VLAN
You can change the port classification key
only if all flows using this port are
See the relevant table In the Classification
Keys section below to see the
queue/priority mapping methods for the
selected classification key, as well as the
flows / flow parameters that can be
configured for the key.
5-14 PCS Ports ETX-2i

Configuring OAM EFM descriptor efm descriptor <efm-descriptor-index> See Configuring OAM EFM.
Setting maximum frame size to egress-mtu <size> Possible values: 641580

transmit (egress MTU)
Configuring the functional mode functional-mode {user | network}
Associating a Layer-2 control l2cp profile <l2cp-profile-name>

processing profile with the port
Running loopback test on port loopback {local|remote} [duration Use the no loopback command to stop the
<seconds>] test.
Assigning description to port name <string>
Configuring collection of performance pm-collection interval <seconds> Note: In addition to enabling PM statistics
management statistics for the port, collection for the ports, it must be enabled
that are presented via the RADview for the device. Refer to the Performance
Performance Management portal Management section in the Monitoring and
Associating a policer profile with the policer profile <policer-profile-name> Typing no policer removes any policer
port profile from the port.
Associating a queue group profile with queue-group profile Typing no queue-group removes any queue
the port <queue-group-profile-name> group profile from the port.
Setting the VLAN tag Ethertype tag-ethernet-type <0x0000-0xFFFF>
Displaying the interfaces that are show bind

bound to the port
Displaying link OAM (EFM) parameters show oam-efm
Displaying L2CP statistics show l2cp-statistics
Displaying port statistics show statistics running See Viewing PCS Port Statistics.
Clearing L2CP statistics clear-l2cp-statistics
Clearing statistics clear-statistics
Administratively enabling port no shutdown Using shutdown disables the port.

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

Viewing PCS Port Statistics

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

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

ETX-2i# configure port pcs 1
ETX-2i>config>port>pcs(1)# show statistics running
Rates Sampling Window
---------------------------------------------------------------
Window Size [Min.] : 15
Window Remain Time [Min.] : 14
Running
---------------------------------------------------------------
Counter Rx Tx
Total Frames 0 0
Total Octets 0 0
Total Frames/Sec 0 0
Total Bits/Sec 0 0
Minimum Bits/Sec 0 0
Maximum Bits/Sec 0 0
Unicast Frames 0 0
Multicast Frames 0 0
Broadcast Frames 0 0
CRC Errors 0
Error Frames 0 --
L2CP Discarded 0 --
CFM Discarded 0 --
MTU Discarded 0 56
Unknown Protocol Discarded 0 --
CRC Errors/Sec 0
Jabber Errors 0 --
Oversize Frames 0 0
64 Octets 0 0
65-127 Octets 0 0
128-255 Octets 0 0
256-511 Octets 0 0
512-1023 Octets 0 0
1024-1518 Octets 0 0
1519-2047 Octets 0 0
2048-Max Octets 0 0
MTU Discarded Flow : --/EVC1-TLV
5-16 PCS Ports ETX-2i

Table 5-3. PCS Statistics Counters
Window Size [Min.] Interval for sampling statistics, user-configurable (see Setting Sampling
Interval for Port Statistics)
Window Remain Time [Min.] Amount of time remaining in statistics sampling window
Total Frames Total number of frames received/transmitted
Total Octets Total number of bytes received/transmitted
Total Frames/Sec Number of frames received/transmitted per second
Total Bits/Sec Number of bits received/transmitted per second
Minimum Bits/Sec Minimum number of bits received/transmitted per second
Maximum Bits/Sec Maximum number of bits received/transmitted per second
Unicast Frames Total number of unicast frames received/transmitted
Multicast Frames Total number of multicast frames received/transmitted
Broadcast Frames Total number of broadcast frames received/transmitted
CRC Errors Total number of frames received that are an integral number of octets in
length, but do not pass the Frame Check Sequence (FCS) check. This count
excludes frames received with Frame-Too-Long or Frame-Too-Short error.
Error Frames Total number of frames with errors received
L2CP Discarded Total number of L2CP frames discarded
CFM Discarded Total number of CFM frames discarded. See OAM Packet Handling for all
cases when OAM packet is discarded.
MTU Discarded Total number of packets dropped due to exceeding the egress-mtu limit
configured over the port
Unknown Protocol Discarded Total number of frames with unknown protocol discarded
CRC Errors/Sec Number of frames per second received that are an integral number of octets
in length, but do not pass the Frame Check Sequence (FCS) check. This count
Jabber Errors Total number of frames received with jabber errors
Oversize Frames Total number of oversized frames received/transmitted
64 Octets Total number of received/transmitted 64-byte packets
65127 Octets Total number of received/transmitted 65 to 127-byte packets
2048Max Octets Total number of received/transmitted packets with 2048 bytes and up to
maximum
MTU Discarded Flow The last flow from which MTU packets were discarded

5.7 Peers
Configuring peers provides access to remote devices.
Peers are remote devices operating opposite router interfaces that can be linked
in order to access the 1588v2 master clock.
Factory Defaults
By default, no peers are defined in ETX-2i.
Configuring Peers
You can define up to 64 peers as explained below.
To define a peer:
At the config# prompt, do one of the following:
To define the peer according to IP address, type:
peer <number> ip <ip-address> [name <name>]
To define the peer according to MAC address, type:
peer <number> mac <mac-address> [name <name>]
5.8 Service Virtual Interfaces

SVIs are virtual ports used in routers.
Benefits
SVIs are used as ingress and egress ports for flows, serving as intermediaries for
routers.
Service virtual interfaces (SVIs) are logical ports used to link router interfaces with
Ethernet ports (via Layer-2 flows) or TWAMP controllers/responders.
Note ETX-2i supports up to eight SVIs.
Factory Defaults
By default, no SVIs exist in ETX-2i.
Configuring Service Virtual Interfaces

You can enable and operate service virtual interfaces as explained below.
5-18 Service Virtual Interfaces ETX-2i

To configure the SVI parameters:

1. Navigate to configure port svi <port-num> to select the SVI to configure.
Note If the SVI port is intended for use with TWAMP, type port svi <port-num> twamp
when creating it.
The config>port>svi(<port-num>)# prompt is displayed.

Setting the port name name <string>
Administratively enabling SVI no shutdown Using shutdown disables the SVI.
5.9 VCGs
VCG ports provide a logical link to modular E1/T1/T3 ports, if applicable.
Standards
ITU-T G.7042
ITU-T G.7043
Benefits
The VCG port provides a logical link to modular E1/T1/T3 ports.
A VCG (Virtual Concatenation Group) logical port is used to group the E1/T1/T3
ports that are available if the appropriate type of module has been provisioned
and inserted.
By default, the Tx clock of the E1/T1/T3 ports in the module is the internal clock
provided by the internal oscillator of the module. You have the option of
selecting instead the loopback clock retrieved from the port's incoming (Rx) data,
as the Tx clock of the E1/T1/T3 ports. For the ETX2i EoPDH AIO module, you
have yet another option of selecting the domain clock provided by the ETX2i
CSM system clock as the Tx clock of the E1s.
Note The Rx clock of an E1 in an ETX2i EoPDH AIO module can also be provided as a
source clock to ETX2i CSM, provided the E1 port is bound to VCG 5. For further
information, refer to the Clock Selection section in Chapter 9.
ETX-2i VCGs 5-19

Note The VCG logical port is used only if the module contains multiple E1/T1/T3 ports,
and a GFP port is then bound to the VCG port. If a module with a single T3 port is
installed, the GFP port is bound directly to the T3 port.
Factory Defaults
By default, no VCG ports exist. When a VCG port is created, it is configured as
shown below.
Parameter Value Remarks
lcas lcas LCAS enabled
minimum-number-of-links 1 Minimum number of links

when working with LCAS
name VCG <port>
shutdown no shutdown Administratively enabled
tx-clock-source internal Clock source for transmitted

data
Configuring VCG Ports
Note One VCG port is available in ETX-2i.
To configure VCG ports:

vcg <port>
config>port>vcg(<port>)# prompt is displayed.
Binding VCG port to E1 port bind e1 <slot>/<port> Note: Successful only if the
no bind e1 <slot>/<port> E1/T1 module is installed.
Binding VCG port to T1 port bind t1 <slot>/<port> Note: Successful only if the
no bind t1 <slot>/<port> E1/T1 module is installed.
Binding VCG port to T3 port bind t3 <slot>/<port> Note: Successful only if the T3
no bind t3 <slot>/<port> module is installed.
Enabling link capacity adjustment lcas

scheme (LCAS) no lcas
Enabling loop detection loop-detection Note: Relevant only in the case

no loop-detection of modular E1 ports.
Specifying minimum number of links minimum-number-of-links

when working with LCAS <links>
5-20 VCGs ETX-2i


no name
Selecting the transmit clock source tx-clock-source {loopback | loopback clock retrieved
internal | domain <number>} from the port's incoming
(Rx) data
internal clock provided by
internal oscillator of the
E1/T1/T3 module
domain clock provided by
ETX2i CSM system clock.
This option is available only
for modular E1 ports of
ETX2i EoPDH AIO module.
Administratively enabling port no shutdown Using shutdown disables the

port.
Displaying list of interfaces bound to show bind

the port
Displaying the VCG port status show status
Examples
To configure VCG port 5 with module containing two E1 ports, and with system
clock from ETX2i CSM:
#*****ports E1 configuration***************************
configure port
e1 1/1
no shutdown
exit
e1 1/2
no shutdown
exit all
#*****ports GFP bind MAC configuration******************
configure port
vcg 5
bind e1 1/1
bind e1
tx-clock-source domain 1
exit
gfp 5
bind vcg 5
exit
logical-mac 5
bind gfp 5
no shutdown
exit all
To configure VCG port 5 with module containing two T3 ports:
ETX-2i>config>port# vcg 5
ETX-2i VCGs 5-21

ETX-2i>config>port>vcg(5)$ bind t3 1/1

ETX-2i>config>port>vcg(5)$ bind t3 1/2
ETX-2i>config>port>vcg(5)$ no shutdown
ETX-2i>config>port>vcg(5)$ info detail
Name "VCG 5 "
no shutdown
bind t3 1/1
bind t3 1/2
tx-clock-source internal
lcas
minimum-number-of-links 1
ETX-2i>config>port>vcg(5)$ show bind
Higher Layer
---------------------------------------------------------------
Lower Layer
---------------------------------------------------------------
T3 1
T3 2
5.10 DS1 (E1/T1) Ports

The E1/T1 ports can be configured to work as E1 ports or T1 ports if there is an
E1/T1 module, in the ds1 (digital signal) level. The E1/T1 ports are bound to VCGs
via GFP ports and logical MAC ports.
Benefits
There is no need to choose E1 or T1 when ordering the unit.
All ports must work in the same mode, therefore configuring any port sets all
ports to the same mode.
Before changing the E1/T1 port mode, any corresponding GFP ports/VCGs/logical
MAC ports/pseudowires/PW cross connects must be deleted. After changing the
mode, ETX-2i must be restarted.
Factory Defaults
By default, the E1/T1 ports are set to E1 mode.
Configuring E1/T1 Ports

To configure E1/T1 ports:
ds1 [<slot>/]<port>
5-22 DS1 (E1/T1) Ports ETX-2i

The config>port>ds1([<slot>/]<port>)# prompt is displayed.

2. To configure the E1/T1 port to E1 or T1 mode, type:
frame-type { e1 | t1 }
5.11 E1 Ports
The European Conference of Postal and Telecommunications Administrations
(CEPT) standardized the E-Carrier system, which was then adopted by the
International Union Telecommunication Standardization sector (ITU-T), and is
used in almost all countries outside the USA, Canada, and Japan.
The most commonly used versions are E1 and E3. E1 circuits are very common in
most telephone exchanges and used to connect medium and large companies to
remote exchanges. In many cases, E1 connects exchanges with each other.
E1 ports are applicable to ETX-2i as follows:
Smart SFP E1 ports:
Smart SFP E1 ports are available for ETX2i and ETX-2i-B when smart SFPs
such as MiRICi-E1 or MiTOP-E1 are provisioned; for ETX-2i-10G in
standalone mode only (see Smart SFPs).
Smart SFP E1 ports do not support encapsulation via VCG.
Smart SFP E1 ports are referenced as [<slot>/]<port>/<tributary>:
<slot> is relevant to modular ports.
<tributary> is always set to 1.
E1/T1 module:
Modular E1/T1 ports can be configured to E1 mode (see DS1 (E1/T1)
Ports). The default mode is E1.
Modular E1 ports support encapsulation via VCG (see VCGs).
Modular E1 ports are referenced as <slot>/<port>.
Standards
CCITT G.732
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
E1 lines are high-speed dedicated lines that enable large volume usage.
ETX-2i E1 Ports 5-23

An E1 link operates over a twisted pair of cables. A nominal 3-volt peak signal is
encoded with pulses using a method that avoids long periods without polarity
changes. The line data rate is 2.048 Mbps at full duplex, which means 2.048 Mbps
downstream and 2.048 Mbps upstream. The E1 signal splits into 32 timeslots
each of which is allocated 8 bits. Each timeslot sends and receives an 8-bit
sample 8000 times per second (8 x 8000 x 32 = 2,048,000), which is ideal for
voice telephone calls where the voice is sampled into an 8-bit number at that
data rate and restored at the other end. The timeslots are numbered from 0 to
31.
Factory Defaults
By default, no smart SFP E1 ports exist.
By default, modular E1/T1 ports are set to E1 mode and have the following
configuration.
interface-type balanced Line impedance type
line-code hdb3 Transmission line code
line-type Unframed Port framing mode
name E1 <slot>/<port> DS1 <port>
pm-enable no pm-enable Performance monitoring is

disabled
rx-sensitivity short-haul Attenuation level of

received signal
shutdown shutdown Administratively disabled
Configuring E1 Ports
Configuring Built-in E1 Ports
To configure E1 ports:
1. Navigate to configure port e1 <port>.
e1 <port>/<tributary>
The prompt config>port>e1(<port>/<tributary>)# is displayed.
5-24 E1 Ports ETX-2i

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

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

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

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

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

code High Density Bipolar of
order 3 code, it is a
telecommunication line
code based on AMI and
used in E1 lines. It is
similar to B8ZS used in T1
lines.
AMI Referred to as
Alternate Mark Inversion
because a 1 is referred to
as a mark and a 0 as a
space.

Specifying the framing mode of line-type { unframed | g732n | g732n-crc | unframed no framing;
the port g732s | g732s-crc } relevant only for built-in
E1 ports
g732n G.732N framing
with CRC disabled
g732n-crc G.732N
framing with CRC enabled
g732s G.732S framing
(CAS) with CRC disabled
g732s-crc G.732S
framing (CAS) with CRC
enabled.
Running loopback test on E1 port loopback {local | remote} local returns the
[duration <seconds>] transmitted data at the
physical layer to the
receiving path
remote returns the
received data at the
transmitting path
Click here to enter text.
duration specifies the
duration of the loopback
(in seconds).
Possible values: 1 to 3600
If duration is not
specified, the loopback
test runs forever, until
stopped.
Use no loopback to disable
the loopback test.
Defining the value to be out-of-service <oos> Possible values: 0x000xFF

transmitted if the corresponding (default 0xFF)
PW is out of service If the corresponding PW is out
of service, ETX-2i transmits
the configured value on a
time slot that is assigned to
the PW toward the TDM side
(relevant only for framed E1
ports).
Specifying if performance pm-enable

reporting is enabled for the port

Specifying the attenuation level rx-sensitivity {short-haul | long-haul} short-haul low

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

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

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

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

balanced or unbalanced

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

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

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

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

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

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

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

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

1. Provision a smart SFP port with type MiRICi-E1 or MiTOP-E1 (see Smart SFPs).

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

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

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

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

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

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

attenuation level of the long-haul} long-haul high sensitivity
received signal,
compensated for by the
interface receive path
Specifying the port source-clock-quality {stratum1 | Clock quality used in adaptive clock
clock quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
stratum4} specified:
stratum1 PRC G.811
stratum2 Type II G.812
stratum3 Type IV G.812
stratum3e Type III G.812
stratum4 Free running
Selecting the transmit tx-clock-source {loopback | loopback Rx clock; clock retrieved

clock source internal | domain <number> | from the port's incoming (Rx) data
pw <number>} internal clock provided by internal
oscillator
domain clock provided by clock
domain, if device has timing option.
pw clock provided by PW bundle
Note: The domain and pw options are
available only for MiTOP.

Administratively shutdown Type no shutdown to administratively

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

interfaces bound to
port
Displaying loopback test show loopback

status
Displaying the port show status

status
Displaying the port show statistics current

statistics show statistics interval
<interval-num>
show statistics all
5.12 E3 Ports
Groups of E1 circuits are bundled into higher-capacity E3 links, which are mainly
used between exchanges, operators, and/or countries, and have a transmission
speed of 34.368 Mbps.
E3 ports are available when smart SFPs such as MiRICi-E3 or MiTOP-E3 are
provisioned (see Smart SFPs).
Smart SFP E3 ports are referenced as [<slot>/]<port>/<tributary>:
Standards
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
E3 lines provide high-capacity circuits.

Each E3 signal has 16 E1 channels, and each channel transmits at 2.048 Mbps. E3
links use all eight bits of a channel.
Factory Defaults
By default, no E3 ports exist.
Configuring E3 Ports
1. Provision a smart SFP such as MiRICi-E3 or MiTOP-E3 and insert it into an
Ethernet port (see Smart SFPs).

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

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

the port

Specifying the port source-clock-quality {stratum1 | Clock quality used in adaptive clock
clock quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
stratum1 PRC G.811
Selecting the transmit tx-clock-source {loopback | internal | loopback clock retrieved from
clock source pw <number>} the port's incoming (Rx) data
internal oscillator
Note: The pw option is available only
for MiTOP.

the port

interfaces bound to
port
Displaying loopback show loopback

test status

status

statistics show statistics interval
<interval-num>
show statistics all

5.13 Ethernet Ports
Options
ETX-2i has four or eight fixed SFP/copper combo ports. If ordered with the
modular GbE option, it has four fixed SFP/copper combo ports, and two fiber
optic/copper (combo) Gigabit Ethernet ports on the module.
ETX-2i-B has four or six fixed SFP/copper combo ports (two Network ports and
two or four User ports, depending on the ordering option).
ETX-2i-10G half 19 has four ETH SFP+ ports, four UTP ports, and four combo or
SFP ports.
ETX-2i-10G full 19 has four ETH SFP+ ports, 12 UTP ports, and 12 SFP ports.
Numbering
The following table shows how to refer to the ports when configuring them with
CLI commands.
Table 5-4. Ethernet Port Reference
Port Unit CLI
Port Number [Slot/]Port Number
ETX2i
Fixed Ethernet port 1 1 0/1
Fixed Ethernet port 5 (if applicable) 5 0/5
Modular port 1 (if applicable) 1 1/1
Modular port 2 (if applicable) 2 1/2
MNG-ETH 0/101
ETX-2i-B
ETX-2i Ethernet Ports 5-35

Port Unit CLI
Fixed Ethernet port 10 (if 8 0/10

applicable)
MNG-ETH 0/101
ETX-2i-10G Half 19
Fixed Ethernet port 1 (SFP+) 1 0/1
Fixed Ethernet port 5 (SFP) 5 0/5

applicable)

applicable)

applicable)
MNG-ETH 0/101
ETX-2i-10G Full 19
5-36 Ethernet Ports ETX-2i

Port Unit CLI

Port Unit CLI
MNG-ETH 0/101
Note For ETX2i with D-NFVoption, user ports 7 and 8 are not available.
MAC Addresses
ETX-2i has multiple MAC addresses. Each Ethernet port is assigned a different
MAC address.
You can view the MAC address assigned to an Ethernet port via show status (see
Viewing Ethernet Port Status). For information on which MAC address is used by a
particular feature, refer to the relevant section in this manual.
Ethertype
Ethertype configured per-port is used for identification of VLAN-tagged frames at
ingress and Ethertype stacking at egress. This refers to the outer VLAN only. The
outer VLAN of an incoming packet must match the configured Ethertype of the
port in order to be considered a VLAN-tagged frame (otherwise frame is
considered untagged or dropped). See the Ethertype section in Chapter 6 for
details.

ETX-2i-10G half 19 supports Fat pipe detection, a mechanism that detects
exceptionally high BW sessions (micro flows) according to a search key, and binds
a preconfigured BW policer to the session, thus limiting its BW. You can bind up
to two ports to a Fat pipe detection profile.
Refer to the Fat Pipe Detection and Rate Limiting section in Chapter 8 for a
detailed overview and configuration instructions.
Silent Start
Network operators use both point-to-point and point-to-multipoint Optical
Access Networks (OANs), depending on the application. For example, a Passive
Optical Network (PON) is a point-to-multipoint OAN. One of the major challenges
to operating and maintaining such OANs securely is that misconnecting a point-
to-point Optical Network Terminal (ONT) or Ethernet equipment to a branch of a
PON can cause a service outage in the PON system. In order to address this issue,
a Silent Start function is introduced in all types of ONTs, which inhibits an ONT
transmitter's power at startup until the receiver recognizes consistent incoming
data. On recovery of "understandable" data by the receiver, the transmitter is
enabled to enter a handshaking process with the Optical Line Terminal (OLT).
Optical Network Units (ONUs) transmit in assigned time slots to avoid disturbing
each other over the shard fiber, as a non-GPON device transmitting continuously
is likely to bring down a GPON segment.

Ethernet equipment can also be connected by mistake to a PON network and

bring down the PON segment, to address this the ETX also supports a silent start
functionality which once enabled would allow optical Tx only once a valid Ethernet
signal is received.
Figure 5-1. Passive Optical Network (PON)
ETX-2i supports Silent Start functionality for the following ports:

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

Figure 5-2. Silent Start
Factory Defaults
By default, the non-management Ethernet ports have the following configuration.
auto-negotiation Enable or disable auto-negotiation auto-negotiation
classification-key Classification key legacy
dhcp-trust Trust server DHCP packets no dhcp-trust (i.e. trust client

DHCP packets)
efm Enable or disable OAM EFM no efm
egress-mtu Packet size 1790
no fat-pipe-detection Bind a fat pipe detection profile no fat-pipe-detection

to a port.
functional-mode Note: Relevant to port 0/2 network
l2cp L2CP profile L2cpDefaultProfile
lldp 802.1-management-vlan-id LLDP: no transmission of IEEE no

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

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

source

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

1. Navigate to configure port ethernet [<slot>/]<port-num> to select the
Ethernet port to configure.
Note The only parameter that can be configured for the management Ethernet port is
PM collection. To configure the management Ethernet port, navigate to configure
port mng-ethernet.
Enabling autonegotiation for FE/GbE auto-negotiation Autonegotiation is not applicable for SFP+
port ports with speed-duplex configured to 10g-r
(ETX-2i-10G).
Entering no auto-negotiation disables
autonegotiation.
auto-negotiation can be enabled only if
silent-start is disabled (sanity check).

Specifying classification key per port classification-key [legacy] [vlan] [inner- legacy No classification key is used.
vlan] vlan classification key according to VLAN
inner-vlan classification key according to
VLAN + Inner VLAN
You can change the port classification key
only if all flows using this port are
See the relevant table In the Classification
Keys section below to see the queue/priority
mapping methods for the selected
classification key, as well as the flows / flow
parameters that can be configured for the
key.
Configuring port classification classifier See Configuring Port Classification.
Clearing L2CP statistics clear-l2cp-statistics See Clearing Statistics.
Clearing port statistics clear-statistics See Clearing Statistics.
Configuring OAM EFM descriptor efm descriptor <efm-descriptor-index> See OAM EFM.
Setting maximum frame size (in bytes) egress-mtu <6412288>

to transmit (frames above the
specified size are discarded)
Binding a Fat pipe detection profile to fat-pipe-detection profile <profile-name> Profile-name name of the fat pipe
a port detection profile bound to the port
Type no fat-pipe-detection to unbind fat
pipe detection profile from the port.
Relevant for ETX-2i-10G half 19 only.
You can define a single Fat-pipe detection
profile.
Setting port to function as network or functional-mode {network | user} Note: Relevant to port 0/2
user See Table 5-5 for further information.

Associating a Layer-2 control l2cp profile <l2cp-profile-name> Be sure to assign the same L2CP profile to
processing profile with the port both network ports.
The associated L2CP profile must specify
peer action for MAC 0x02 in the following
cases:
The port needs to receive clock
signals (i.e. is defined as clock source).
LACP (LAG) is enabled for the port.
Link OAM (EFM) is enabled for port.
Configuring LLDP parameters lldp See Link Layer Discovery Protocol (LLDP) for
details.
Executing loopback test loopback {local | remote} See Testing Ethernet Ports.
[duration <seconds>]
Setting maximum advertised capability max-capability {10-full-duplex | 10-full-duplex 10baseT full duplex
(highest traffic handling capability to 100-full-duplex | 1000-full-duplex | 100-full-duplex 100baseT full duplex
be advertised during the 1000-x-full-duplex } [{sfp | rj45}]
1000-full-duplex 1000base T full duplex
autonegotiation process) for FE/GbE
port if autonegotiation is enabled 1000-x-full-duplex 1000 BaseX,
1000 BaseLX, 1000 BaseSX, or 1000 BaseCX
full duplex
Note: Use sfp or rj45 for combo ports to
configure different values for the SFP and
RJ-45 modes. If neither sfp nor rj45 is
specified, the command applies to both
modes. The device works with the values
that apply according to whether an SFP is
inserted.
Defining maximum quality level of max-ql {prc | ssu-a | ssu-b | sec | dnu | The quality level of the SyncE transmitted
clock source, if SyncE is transmitted ssm-based | prs | stu | st2 | tnc | st3e | st3 over this port is the minimum of the quality
over the port | smc | st4 | dus | ssm-based | prov | unk | level set by this command, and the system
sec | dnu | ssm-based} quality level set by clock selection.
Note: Refer to the Clock Selection section in
the Timing and Synchronization chapter for
an explanation of the quality levels.
Assigning description to port name <string> Entering no name removes the name.
Configuring collection of performance pm-collection interval <seconds> Note: You can enable PM statistics collection
management statistics for the port, for all Ethernet ports rather than enabling it
that are presented via the RADview for individual ports. In addition to enabling
Performance Management portal PM statistics collection for the ports, it must
be enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.

Associating a policer profile for policer profile <policer-profile-name> Typing no policer removes any policer profile
broadcast/multicast traffic with the from the port.
port

the port <queue-group-profile-name>
Measuring port data rate and line rate rate-measure interval <seconds> Possible values: 10300
See Viewing Ethernet Port Data Rate and
Line Rate for details.
Enabling/disabling Silent Start [no] silent-start This parameter is visible for optical ports
only.
silent-start can be configured only if auto-
negotiation is disabled (no uto-negotiation).
Setting data rate and duplex mode of speed-duplex {10-full-duplex | 10-full-duplex 10baseT full duplex
FE/GbE port and SFP+ (1GbE) port 100-full-duplex | 1000-full-duplex | 100-full-duplex 100baseT full duplex
1000-x-full-duplex [{sfp | rj45}]
1000-full-duplex 1000base T full duplex
1000-x-full-duplex 1000 BaseX,
1000 BaseLX, 1000 BaseSX, or 1000 BaseCX
full duplex
Notes:
The values 10-full-duplex,
100-full-duplex, 1000-full-duplex, and
1000-x-full-duplex are relevant only when
auto-negotation is disabled.
Use sfp or rj45 for combo ports to
configure different values for the SFP and
RJ-45 modes. If neither sfp nor rj45 is
specified, the command applies to both
modes. The device works with the values
that apply according to whether an SFP is
inserted.
It is not possible to downgrade SFP+
ports that are set to 10G by the ordering
option.
Downgrading an SFP+ port from 10GbE to
1GbE returns the port configuration to its
default values.

Setting data rate and duplex mode of speed-duplex 10g-r Relevant for ETX-2i-10G SFP+ ports, only if
SFP+ port (10GbE) license exists.
10g-r Sets SFP+ port speed to 10GbE
(relevant for ETX-2i-10G SFP+ ports that are
1GbE capable).
Notes:
Autonegotiation is not applicable for
SFP+ ports with speed-duplex configured
to 10g-r.
Upgrading an SFP+ port from 1GbE to
10GbE returns the port configuration to
its default values.
Setting the VLAN tagged frame ETH II tag-ethernet-type <0x0000-0xFFFF> Port Ethertype can be set to one of the
frame Ethertype (tag protocol following values, provided it has been
identifier) defined at the device (chassis) level:
0x8100 (default)
0x88a8
A user configurable Ethertype (two can
be configured)
Note: If you do not configure an Ethertype
for the port, the port uses the default
setting (8100).
Enabling transmitting of clock tx-ssm You should enable this for Ethernet ports
availability and quality via SSM that transmit clock signals. The MAC address
of the transmitting port is used in the SSM
message.
Entering no tx-ssm disables sending SSM
messages.
Displaying information on active and show fat-pipe-list { active | history | all } all option shows both Active and History
history (closed) Fat pipes entries.
See Displaying Fat Pipe Information.
Relevant for ETX-2i-10G half 19 only.
Displaying L2CP statistics show l2cp-statistics See Displaying Layer-2 Control Processing
Statistics.
Displaying OAM EFM status show oam-efm
Displaying measured port data rate show rate See Viewing Ethernet Port Data Rate and
and line rate Line Rate for details.
Displaying the port statistics show statistics See Viewing Ethernet Port Statistics.
Displaying the port status show status See Viewing Ethernet Port Status.

Table 5-5. Classification Key Priority Map Scheme
Classification Key Queue Mapping Method
Legacy (current key) NA

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

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

You can set the ETX2i Ethernet port 0/2 to function as network or user.
Notes When you change the functional mode, all flows related to the port are
deleted.
The port must be administratively disabled before you can change the
functional mode.
To change the functional mode of the Ethernet interface:

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

exit all
configure port ethernet 0/2
shutdown
functional-mode user
no shutdown
save

Viewing Ethernet Port Status

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

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

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

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

At the prompt config>port>eth(<port-num>)#, enter:
show status
The Ethernet port status parameters are displayed, including SFP
information if applicable.
Notes The SFP/XFP wavelength values display the exact values from the SFP/XFP
registers.
In case of DDM SFP/XFP, 1/100 nano meter resolution is supported
(e.g 1536.61).

To display the status of all Ethernet ports:

ETX-2i# configure port
ETX-2i>config>port# show summary
Port Number Name Admin Oper Speed
--------------------------------------------------------------
Ethernet 0/1 ETH-0/1 Up Down 1000000000
Ethernet 0/4 ETH-0/4 Testing Down 1000000000
Ethernet 0/5 ETH-0/5 Up Up 1000000000
Ethernet 0/101 MNG-ETH Up Up 100000000
To display the status of Ethernet port 0/3 if an SFP is inserted:

ETX-2i# configure port ethernet 0/3
ETX-2i>config>port>eth(0/3)# show status
Connector Type : Combo RJ45+SFP In - SFP Active
Auto Negotiation (SFP) : Other
MAC Address : 00-20-D2-E4-A2-66
SFP
---------------------------------------------------------------
Connector Type : LC
Manufacturer Name : RAD data comm.
Manufacturer Part Number : MiRICi-155
Typical Maximum Range (Meter) : 15000
Wave Length (nm) : 1310.00
Fiber Type : Not Applicable
To display the status of Ethernet port 1 with Silent Start enabled:

ETX2i# show con port eth 1 status
Name Eth-1
Operational Status : Up
Connector Type : SFP
Auto Negotiation .. : Disabled
Speed And Duplex .. : 1000 Full Duplex
MAC Address : 00-20-D2-51-0C-50
Silent Start : In progress
Testing Ethernet Ports

The physical layer runs at the PHY of the ports. When the loopback is active the
data forwarded to a port is looped from the Tx path to the Rx path.
The loopback can be one of the following types:
Local Loopback is closed toward the user interface.

Remote Loopback is closed toward the network interface.
To run a physical layer loopback test:

1. Navigate to configure port ethernet [<slot>/]<port-num> to select the
Ethernet port to test.
2. Enter:
loopback {local | remote} [duration <seconds>]
The duration is in seconds, with range 086400. Entering 0 or not specifying
the duration disables the timer, e.g. the loopback runs forever until you
disable it.
While the test is running, entering show summary at the port level displays
the ports operational status as Testing (see Viewing Ethernet Port Status).
3. To end the loopback test, enter:
no loopback
Example
To run loopback on Ethernet port 0/3:

exit all
loopback remote duration 30
To display loopback status:

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

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

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

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

At the prompt config>port>eth([<slot>/]<port-num>)#, enter:
show statistics

Ethernet port statistics are displayed. The counters are described in the
following table.
Example
To display the statistics for Ethernet port 0/2:

ETX-2i>config>port>eth(0/2)# show statistics
--------------------------------------------------------------
Running
--------------------------------------------------------------
Rx Tx
Total Frames : 0 5257039970304
Total Octets : 0 0
Total Frames/Sec : 0 0
Total Bits/Sec (L1) : 0 0
Minimum Bits/Sec (L1) : 0 0
Maximum Bits/Sec (L1) : 0 0
Unicast Frames : 0 0
Multicast Frames : 0 1224
Broadcast Frames : 0 0
CRC Errors : 0 --
Error Frames : 0 --
L2CP Discarded : 0 --
OAM Discarded : 0 --
MTU Discarded : 0 56
Unknown Protocol Discarded : 0 --
CRC Errors/Sec : 0 --
Jabber Errors : 0 --
Oversize Frames : 0 0
64 Octets : 0 0
65-127 Octets : 0 0
128-255 Octets : 0 0
256-511 Octets : 0 0
512-1023 Octets : 0 0
1024-1528 Octets : 0 0
1519-2047 Octets : 0 0
2048-Max Octets : 0 0
Table 5-6. Ethernet Statistics Counters
Window Size [Min.] Interval for sampling statistics, user-configurable (see Setting Sampling
Interval for Port Statistics)
Window Remain Time [Min.] Amount of time remaining in statistics sampling window

Total Frames Total number of frames received/transmitted
Total Octets Total number of bytes received/transmitted
Total Frames/Sec Number of frames received/transmitted per second
Total Bits/Sec (L1) Number of bits received/transmitted per second in Layer 1, using the line
rate: [Total number of bytes + (number of packets x 20 bytes of line
overhead)] divided by the time interval
Minimum Bits/Sec (L1) Minimum number of bits received/transmitted per second in Layer 1, using
the line rate: [Total number of bytes + (number of packets x 20 bytes of line
Maximum Bits/Sec (L1) Maximum number of bits received/transmitted per second in Layer 1, using
the line rate: [Total number of bytes + (number of packets x 20 bytes of line
Total Bits/Sec (L2) Number of bits received/transmitted per second in Layer 2, using the data
rate: [Total number of bytes (not including line overhead) divided by the
time interval
Minimum Bits/Sec (L2) Minimum number of bits received/transmitted per second in Layer 2, using
the data rate: [Total number of bytes (not including line overhead) divided
by the time interval
Maximum Bits/Sec (L2) Maximum number of bits received/transmitted per second in Layer 2, using
the data rate: [Total number of bytes (not including line overhead) divided
by the time interval
Unicast Frames Total number of unicast frames received/transmitted
Multicast Frames Total number of multicast frames received/transmitted
Broadcast Frames Total number of broadcast frames received/transmitted
Error Frames Total number of frames with errors received
L2CP Discarded Total number of L2CP frames discarded
OAM Discarded Total number of OAM frames discarded. See OAM Packet Handling for all
cases when OAM packet is discarded.
MTU Discarded Total number of packets dropped due to exceeding the egress-mtu limit
configured over the port. Relevant to Ethernet, PCS, and Logical MAC ports.
Unknown Protocol Discarded Total number of frames with unknown protocol, which are discarded. This
includes:
Packets dropped as they were not matched by a classifier profile
Packets dropped by the L2PT mechanism as a result of a non-existant
forwarding path
CRC Errors Total number of frames received that are an integral number of octets in
length, but do not pass the Frame Check Sequence (FCS) check. This count
CRC Errors/Sec Number of frames per second received that are an integral number of octets
in length, but do not pass the Frame Check Sequence (FCS) check. This count
Jabber Errors Total number of frames received with jabber errors

Oversize Frames Total number of oversized frames received/transmitted
64 Octets Total number of received/transmitted 64-byte packets
2048Max Octets Total number of received/transmitted packets with 2048 bytes and up to
maximum
MTU Discarded Flow The last flow from which MTU packets were discarded. Relevant to Ethernet,
PCS, and Logical MAC ports.
Displaying Fat Pipe Information
To display the Ethernet port Fat pipe information:

show fat-pipe-list { active | history | all }
where
active shows only the active entries
history shows only the history entries
all shows both active and history entries
Ethernet Fat pipe information is displayed. Only those L2-L4 packet attributes (up
to five) that you configured in the Fat pipe detection profile (refer to Configuring
Fat Pipe Detection) are displayed in the report. The parameters are described in
the following table.
Example
To display the information of active Ethernet port 0/1 Fat pipes:

ETX-2I-10G-LC>config>port>eth(0/1)# show fat-pipe-list all
Entity : e2000
Entity : 1 Detection Time : 1970-01-01 00:02:18

Duration (Sec) : 107 Detected Rate (Mbps) : 1662
Current Rate (Mbps): 1475
Src MAC Address : AA-10-94-00-00-03
To display the information of history (closed) Ethernet port 0/1 Fat pipes:
Entity : e2000


Src MAC Address : AA-10-94-00-00-02
Entity : e2000

Src MAC Address : EE-10-94-00-00-02
Table 5-7. Fat Pipe Parameters
Entity Fat pipe profile name

Entity Entry number
Possible values: 1-10 for active list; 1-32 for history list
Detection Time The time of day that the Fat pipe was detected
Duration (Sec) Duration of Fat pipe since detection (in seconds)
Detected Rate (Mbps) The Fat pipe rate measured at the time of Fat pipe detection.
Possible values: 0-10,000
Current Rate (Mbps) The current ingress Fat pipe rate
Src MAC Address Source MAC address of packet
Dst MAC Address Destination MAC address of packet
Ethertype Ethertype of packet
VLAN Packet Vlan
P-bit P-bit of packet
Inner Ethertype Packets Inner Ethertype
Inner VLAN Packets Inner VLAN
Inner p-bit Packets Inner p-bit
DSCP Packets DSCP value
IP Precedence IP Precedence of packet
ToS ToS of packet
Protocol Packet protocol
Src IP Address Packet source IP address
Dst IP Address Packet destination IP address
L4 Src Port Layer-4 source port
L4 Dst Port Layer-4 destination port
Displaying Layer-2 Control Processing Statistics

The following procedure describes how to generate L2CP statistics. The counters
displayed relate to L2CP MAC swap functionality.

To display the Layer-2 control processing statistics for an Ethernet port:

show l2cp-statistics
L2CP statistics are displayed for the specified port, showing the number
of encapsulated and decapsulated packets for each protocol.
Example
To display the L2CP statistics for Ethernet port 0/3:

ETX-2i>config>port>eth (0/3)# show l2cp-statistics
Protocol Encapsulated Decapsulated
-----------------------------------------------------------
LACP 0 0
STP 0 0
CDP 0 0
VTP 0 0
LLDP 0 0
PVSTP 0 0
PAGP 0 0
UDLD 0 0
DTP 0 0
Total 0 0
Clearing Statistics
To clear the statistics for an Ethernet port:

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

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

You can measure the data rate and line rate at which Ethernet ports transmit and
receive, for a configurable time interval of 10300 seconds. After you enter the
command to measure the rates, ETX-2i automatically displays the results when
the specified time interval ends. The data rate is calculated by dividing the total
number of bytes (not including line overhead) by the time interval. The line rate is
calculated by dividing (total number of bytes + (number of packets x 20 bytes of
line overhead)) by the time interval.

To start data rate and line rate measurements for an Ethernet port:
rate-measure interval <seconds>
The rate measurement starts. You can use show rate to monitor how
much of the time interval has elapsed. The result is automatically
displayed, without the need to enter show rate, after the specified time
interval ends.
Example
To display the data rate and line rate for Ethernet port 1/2:
ETX-2i>config>port>eth(1/2)# rate-measure interval 30
ETX-2i>config>port>eth(1/2)# show rate

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

SDH/SONET ports are available when smart SFPs such as MiRICi-155 are
provisioned (see Smart SFPs).
SDH (Synchronous Digital Hierarchy) and SONET (Synchronous Optical Network)
are standardized transport protocols that transfer multiple digital bit streams
over optical fiber using lasers or light-emitting diodes (LEDs). SONET is the United
States version and SDH is the international version.
Standards
SDH is defined by ITU-T G.707, G.781, G.782, G.783, and G.803. SONET is an ANSI
standard defined in T1.105 and T1.119.
Benefits
SDH and SONET allow many different circuits from different sources to be
transported simultaneously within one single framing protocol.
ETX-2i SDH/SONET Ports 5-55

SDH is based on STM-1 which has a data rate of 155.52 Mbps, equivalent to
STS-3. SONET is based on transmission at speeds of multiples of 51.840 Mbps, or
STS-1.
Factory Defaults
By default, no SDH/SONET ports exist.
Configuring SDH/SONET Ports

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

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

the port
5-56 SDH/SONET Ports ETX-2i

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

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

clock source internal oscillator
loopback clock retrieved from the
port's incoming (Rx) data

interfaces bound to
port

status

statistics show statistics interval <interval-num>
show statistics all
5.15 SHDSL Ports

ETX-2i is optionally equipped with a module with two or four SHDSL ports (4-wire
or 8-wire). The SHDSL interfaces are bundled into one PCS (physical coding
sublayer) port. See PCS Ports for commands related to the PCS port.
Applicable Products
This feature is applicable to ETX2i with an SHDSL module.
ETX-2i SHDSL Ports 5-57

Standards
ITU-T G.991.2 (SHDSL.bis)
ITU-T G.994.1 (DSL Handshake)
Benefits
ETX-2i can aggregate traffic over the SHDSL.bis links.
SHDSL stands for Single Pair High-speed Digital Subscriber Line. It is a data
communications technology that enables faster data transmission over copper
telephone lines than a conventional voice band modem can provide. Compared to
ADSL, SHDSL employs frequencies that include those used by traditional POTS
telephone services to provide equal data rates to transmit and receive. As such, a
telephone line cannot be used by both an SHDSL service and a POTS service at
the same time. Support of symmetric data rates has made SHDSL a popular
choice by businesses for PBX, VPN, web hosting and other data services.
Configuring the SHDSL Port Parameters

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

1. Navigate to configure port shdsl 1/<port> to select the SHDSL port to
configure.
The config>port>shdsl(1/<port>)# prompt is displayed.
Clearing the port statistics clear-statistics
Assigning port name name
Viewing SHDSL Port Status

To display the SHDSL port status:
At the config>port>shdsl(1/<port>)# prompt, enter show status.
Relevant SHDSL status parameters are displayed.
5-58 SHDSL Ports ETX-2i

Example
To display the status of SHDSL port 1:
ETX-2i# config port shdsl 1/1
ETX-2i>config>port>shdsl(1/1)# show status
Name : SHDSL-1/1
Operation Status : Down
Wires : 2
Transmission Mode : B-G
Payload Rate (Kbps) : 0
Wires
-----------------------------------------------------------------------------
State SNR Loop Tx PSD Power
Margin Attenuation Power Mask Backoff
(db) (db) (dBm)
-----------------------------------------------------------------------------
Pre Activation 0 0 0.0 Symmetric 6
5.16 VDSL2 Ports

ETX-2i is optionally equipped with a module having four VDSL2 ports (8-wire). The
VDSL2 interfaces are bundled into one PCS (physical coding sublayer) port. See
PCS Ports for commands related to the PCS port.
Applicable Products
This feature is applicable to ETX2i with a VDSL2 module; operates in CPE mode
only.
Standards
ITU-T G.993.2, G.997.1, G.998.2
IEEE 802.3
Benefits
ETX-2i can aggregate traffic over the VDSL.bis links.
VDSL2 (Very High Speed Digital Subscriber Line Transceivers 2) is an access
technology that enables delivery of very high-speed internet access over copper
telephone lines much higher than a conventional voice band modem can
provide.
VDSL2 main features include:
ETX-2i VDSL2 Ports 5-59

Four VDSL2 ports

One bonding group; supports up to four VDSL port(s)
Payload rate 100Mbps DL/ 50Mbps UL per line
G.998.2 VDSL2 PTM (64/65-octet encapsulation) bonding
Bonding payload rate up to 400Mbps DL/ 200Mbps UL, with packet
forwarding throughput 380Mbps DL/180Mbps UL
Supports VDSL2 profiles 8a, 8b, 8c, 8d, 12a, 12b and 17a
Operation frequency scope up to 17.7MHz
Supports ADSL2/ADSL2+ fall back in PTM mode
Comply ITU-T Rec. G.993.2 Annex A and Annex B power spectrum mask
Supports two HW SKUs - one for POTS overlay, the other for ISDN overlay
Supports Trellis coding and reed-Solomon code
SRA (Seamless Rate Adaptation)
Bit Swap
Upstream power backoff (UPBO)
Downstream power backoff (DPBO)
RFI notch
DMT as line coding
G.INP (impulse noise protection)
G.993.2 DELT
G.993.5 vectoring system for NEXT and FEXT
G.993.2 Amd 7, timing synchronization
Dying Gasp
Configuring the VDSL2 Port Parameters

This section explains how to configure the VDSL2 port.
To configure the VDSL2 port parameters

1. Navigate to configure port vdsl2 1/<port> to select the VDSL2port to
configure.
The config>port>vdsl2(1/<port>)# prompt is displayed.
Displaying port status show status See Viewing VDSL2 Port Status.
Displaying port statistics show statistics See Viewing VDSL2 Port Statistics.
Clearing the port statistics clear-statistics
Assigning port name name <string> Typing no name removes the port name.
5-60 VDSL2 Ports ETX-2i

Viewing VDSL2 Port Status

To display the VDSL2 port status:
At the config>port>vdsl2(1/<port>)# prompt, enter show status.
Relevant VDSL2 status parameters are displayed.
Example
To display the status of VDSL2 port 1:

ETX-2i# config port vdsl2 1/1
ETX-2i>config>port>vdsl2(1/1)# show status
Name : VDSL2-1/1
Transmission System : g9932AnnexB
Attainable Line Rate Downstream (Kbps) : 143439
Attainable Line Rate Upstream (Kbps) : 62592
Loop Attenuation (dB) : 0.2dB
SNR Margin (dB) : 9.2dB
Far-End Vendor ID : 26 00 52 41 44 00 00
00
Table 5-8. VDSL2 Status Information
Name Port name

Administrative Status VDSL2 line administrative status
Up or Down
Operation Status VDSL2 line operational status
Up or Down
Attainable Line Rate The maximum downstream net data-rate currently attainable on the
Downstream [Kbps] VDSL2 line, in Kbps
Valid only during VDSL2 line showtime
Attainable Line Rate Upstream The maximum upstream net data-rate currently attainable on the VDSL2
[Kbps] line, in Kbps
Valid only during VDSL2 line showtime
SNR Margin [dB] The average SNR margin
Far-end Vendor ID VTU-C vendor ID
ETX-2i VDSL2 Ports 5-61

Viewing VDSL2 Port Statistics

To display the VDSL2 port statistics:
At the config>port>vdsl2(1/<port>)# prompt, enter show statistics [{current |
interval |current-day | day} {interval-num<interval-num> | day-num<day-
num>}].
Relevant VDSL2 statistic parameters are displayed.
Example
To display the VDSL2 current interval statistics for port 1:

ETX-2i# config port vdsl2 1/1
ETX-2i>config>port>vdsl2(1/1)# show statistics current
Current
---------------------------------------------------------------
Time Elapsed (Sec) : 895
Valid Intervals : 6 Invalid Intervals : 90
ES : 0 SES : 0
UAS : 0 FEC : 2
LOSS : 0
Table 5-9. VDSL2 Statistics Counters
Time Elapsed Total elapsed seconds for current interval/day

Monitored Time Total seconds for this historical interval
Interval Validity Indicates if the data for this historical interval is valid
Valid Intervals The number of 15-minute PM intervals for which data was collected. The
value is typically equal to the maximum number of 15-minute intervals
the implementation is planned to store, unless the measurement was
(re-)started recently, in which case the value is the number of complete
15-minute intervals for which the agent has at least some data. In
certain cases (e.g., in the case where the agent is a proxy), it is possible
that some intervals are unavailable, in which case, this interval is the
maximum interval number for which data is available.
Invalid Intervals The number of 15-minute PM intervals for which no data is available. The
value is typically zero, except in cases where the data for some intervals
are not available (for example, in proxy situations).
ES Number of errored seconds during this interval
SES Number of severely errored seconds during this interval
UAS Number of seconds in Unavailability State during this interval
FEC Number of seconds with at least one FEC correction during this interval
5-62 VDSL2 Ports ETX-2i

5.17 T1 Ports
The T-carrier signaling scheme was devised by Bell Labs and is a widely used
standard in telecommunications in the USA, Canada, and Japan to transmit voice
and data between devices. T1, also referred to as DS-1, is a dedicated data line
that transmits information at the speed of 1.544 Mbps.
T1 ports are applicable to ETX-2i as follows:
Smart SFP T1 ports:
Smart SFP T1 ports are available when smart SFPs such as MiRICi-T1 or
MiTOP-T1 are provisioned (see Smart SFPs)
Smart SFP T1 ports do not support encapsulation via VCG
Smart SFP T1 ports are referenced as [<slot>/]<port>/<tributary>:
E1/T1 module:
Modular E1/T1 ports can be configured to T1 mode (see DS1 (E1/T1)
Ports). The default mode is E1.
Modular T1 ports support encapsulation via VCG (see VCGs)
Modular T1 ports are referenced as <slot>/<port>.
Standards
ITU-T G.703
ITU-T G.704
ITU-T G.823
Benefits
T1 lines are high-speed dedicated lines that enable large volume usage.
A T1 link operates over a twisted pair of cables. A nominal 3-volt peak signal is
encoded with pulses using a method that avoids long periods without polarity
changes. The line data rate is 1.544 Mbps at full duplex, which means 1.544 Mbps
for downstream and 1.544 Mbps for upstream. The T1 signal splits into 24
timeslots each which is allocated 8 bits. Each timeslot sends and receives an 8-bit
sample 8000 times per second (8 x 8000 x 24 = 1,544,000), which is ideal for
voice telephone calls where the voice is sampled into an 8-bit number at that
data rate and restored at the other end. The timeslots are numbered from 0 to
24.
ETX-2i T1 Ports 5-63

Factory Defaults
By default, no smart SFP T1 ports exist.
By default, modular E1/T1 ports are set to E1 mode. When they are configured to
T1 mode, they have the following configuration.
line-code b8zs Zero code suppression
line-length 0-133
line-type ESF
name T1 <slot>/<port>
rx-sensitivity Short-haul Attenuation level of received

signal
Configuring T1 Ports
Configuring Built-in T1 Ports
To configure T1 ports:
1. Configure the port to T1 mode (see Configuring E1/T1 Ports)
t1 <port>/<tributary>
The prompt config>port>t1(<port>/<tributary>)# is displayed.
Specifying out-of-service cas-oos-codes space Space signaling code allowed

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

Specifying inband loopback inband-loopback {local | remote}

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

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

of the T1 line, in DSU mode 267-399 | 400-533 | 534-655}
Specifying the T1 line type line-type { unframed | esf | sf } unframed No framing (this type
is relevant only for built-in T1
ports)
sf (D4) Super Frame (12 T1
frames)
esf Extended Super Frame (24
T1 frames, with on-line
performance monitoring and
4 Kbps control data link)

Running loopback test on T1 loopback {local | remote } local returns the transmitted
port [duration <seconds>] data at the physical layer to the
receiving path
remote returns the received
data at the physical layer to the
transmitting path
seconds) until the loopback
starts. Possible values: 1 to 3600
stopped.
loopback test.

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

the receive signal that is long-haul }
Specifying the port clock source-clock-quality {stratum1 | Clock quality used in adaptive clock
quality stratum2 | stratum3 | stratum3e | recovery set according to parameter
stratum1 PRC G.811
Administratively disabling or shutdown Type no shutdown to administratively

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

bound to port

status


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

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

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

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

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

the receive signal that is long-haul } long-haul indicates CSU mode.

Displaying list of interfaces show bind

bound to port

status


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

1. Provision a smart SFP port with type MiRICi-T1 or MiTOP-T1 (see Smart SFPs).
2. Insert the MiRICi-T1/ MiTOP-T1 into the Ethernet port.

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

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

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

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

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

receive signal that is compensated long-haul }
for by the interface receive path
Specifying the port clock quality source-clock-quality {stratum1 Clock quality used in adaptive clock
| stratum2 | stratum3 | recovery set according to parameter
stratum3e | stratum4} specified:
stratum1 PRC G.811

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

Displaying list of interfaces bound show bind

to port

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

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

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

Specifying the length line-length { up-to-225ft | over-225ft }

(in feet) of the T3 line
Specifying type of T3 line-type { c-bit-parity } c-bit-parity The c-bit parity

line framing format is an enhancement
of the M13 application, providing
greater management and
performance functions.
Running loopback test loopback {local | remote } [start local returns the transmitted
on T3 port <seconds> ] [duration <seconds>] data at the physical layer to the
receiving path
transmitting path
seconds) until the loopback starts.
duration specifies the duration of
the loopback (in seconds).
stopped.
loopback test.
Assigning a name to the name <string>

port
Selecting the transmit tx-clock-source {loopback | internal } loopback clock retrieved from the
clock source port's incoming (Rx) data
internal oscillator
Note: This command is relevant only if
the module has a single T3 port. In the
case of a module with two T3 ports,
the Tx clock source is configured at
the VCG port level (see Configuring
VCG Ports).

the port


interfaces bound to
port

status

status

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

1. Provision a smart SFP port with type MiRICi-T3 or MiTOP-T3 (see Smart SFPs).
2. Insert the MiRICi-T3/ MiTOP-T3 into the Ethernet port.

type of smart SFP.
Specifying the line-length { up-to-225ft |

length (in feet) over-225ft }
of the T3 line
Specifying type line-type {m23 | c-bit-parity | m23 Four DS1 signals are are
of T3 line unframed } multiplexed into one DS2 signal, then
seven DS2 signals are multiplexed into one
DS3 signal.
c-bit-parity The c-bit parity framing
format is an enhancement of the M13
application, providing greater management
and performance functions.
unframed No framing (relevant only for
MiTOP).

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

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

disabling or the port.
enabling the port

interfaces bound
to port
Displaying show loopback

loopback test
status

Displaying the show status

port status
Displaying the show statistics current

port statistics show statistics interval
<interval-num>
show statistics all
Clearing the clear-statistics

statistics
5.19 SFPs
The Ethernet ports are combo ports that have an RJ-45 connector and SFP slot,
and the port can function as a copper port or SFP slot.
The Ethernet ports that are combo ports functioning as SFP slots, are configured
as shown in Ethernet Ports. When you display the port status, the SFP
information is shown if applicable (see Viewing Ethernet Port Status). You can
insert regular SFPs into the SFP slots, or you can insert smart SFPs that provide
integrated configuration and management (see Smart SFPs).
5.20 Smart SFPs

ETX-2i supports integrated configuration and management of smart SFPs (such as
MiRICi/MiTOP devices) to provide TDM port functionality. The following are
supported:
MiRICi-E1/T1/E3/T3
MiRICi-155
MiTOP-E1/T1/E3/T3
ETX-2i supports up to four smart SFPs per device.For ETX-2i-10G, smart SFPs are
supported in standalone mode only.
Benefits
ETX-2i offers the use of a wide variety of TDM E1/T1/E3/T3 OC-3/STM-1 ports via
the smart SFP feature.
The smart SFP is provisioned in the specific Ethernet port where the SFP shall be
inserted. After this provisioning, the Ethernet port is no longer available for
5-76 Smart SFPs ETX-2i

normal Ethernet port functioning. If the smart SFP is provisioned in a combo

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

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

Administratively enabling no shutdown You cannot administratively

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

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

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

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

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

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

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


Chapter 6
Management and Security
This chapter describes the following:
Access Control List (ACL)
Management and configuration options
Working with a terminal connected to the ETX2i control port
Management-related features
6.1 Access Control List (ACL)

Access control lists are used to flexibly filter and mark incoming and management
traffic.
Applicable Products
This feature is applicable to all ETX2i products, with the following condition:
ETX2i and ETX-2i-B ACL can be applied to management packets and router
interfaces.
Standards
Relevant sections of RFC 1812
Benefits
Service providers use ACLs to maintain network security by preventing malicious
traffic from entering the device. ACLs can be used to save network resources by
dropping unwanted packets.
When user or management data is marked via ACLs, service providers can apply
various traffic management techniques to the marked packets, such as allocating
more bandwidth to a certain traffic type.
Devices featuring ACLs can flexibly filter user or management traffic, by denying
or permitting IP packets to enter the host, according to the packets
source/destination address, protocol type, or other criteria.
ACL entries are sequentially numbered rules containing statements (Deny, Permit,
or Remark) and conditions. Remarks are free-text ACL entries used for
ETX2i Access Control List (ACL) 6-1

Chapter 6 Management and Security Installation and Operation Manual
commenting and visually organizing ACLs.

Packets are permitted or denied access, based on the following conditions:
IP source and destination address or address range
IP protocol
TCP port TCP/23 (TELNET), TCP/22 (SSH), TCP/830 (NETCONF)
UDP port UDP/161 (SNMP)
ICMP type and code
The ACL structure is illustrated in the Example section.
If there is a need to add a rule between already existing rules with consecutive
numbers, the rules can be interspaced to accommodate additional rules between
them. For example, if you apply resequencing to an ACL including rules 1, 2, and
3, with an interspacing value of 30, the rule numbers will change to 30, 60 and
90. Sequence numbers can also be set at the rule level.
Binding Access Control Lists

Once created, ACLs are applied (bound) to router interfaces for filtering user
traffic, or to the virtual management entity for filtering management traffic. For
the management entity and router interfaces, ACLs can be used in the inbound
direction only. If a router interface is deleted, all associated ACLs are
automatically detached.
Only one IPv4 ACL is supported per router interface / management entity. An
additional IPv6 ACL may coexist with one IPv4 access list on the same interface /
management entity.
Filtering and Marking

Packets attempting to enter an entity to which the ACL is bound are checked
against the access list rules, one by one. Access of matching packets is denied
(packets are dropped) or permitted (packets are forwarded and possibly marked),
as directed by the ACL statement.
Packets matching a Deny statement (rule) are dropped unless permitted by a
previous rule.
Packets matching a Permit statement (rule) are permitted to access an entity
unless denied by a previous statement. Permit statements may also set the ToS
byte or Layer-2 priority of packets matching them.
When a rule match occurs, an entry is added to the event log if logging is
enabled. To prevent log overflow, it is possible to disable logging (per rule or
device) or define the minimal logging interval of packets matching ACL entries
(per device).
Note By default, logging is disabled. If you choose to enable it, the default logging
interval is five minutes.
Two packets matching the same rule on the same entity in the same direction are
logged only if the time between them exceeds the logging interval.
6-2 Access Control List (ACL) ETX2i

Installation and Operation Manual Chapter 6 Management and Security
After a match, the rest of the rules are ignored. Packets not matching any rule
are dropped. Empty ACLs deny access of all packets matched to them.
Show Me Demo
Reader.
Statistics
The device collects ACL statistics per router, router interface, and management
entity. The statistic counters include the number of rule matches that occurred
since the counters were last cleared. The statistic counters are cleared upon
device reboot. The user may also clear ACL statistics of any entity.
Factory Defaults
Parameter defaults are alphabetically listed in the tables below.
Topic Parameter Default Value
Access Control logging minimum interval 300 (seconds)
Access List access-list type ipv4
All ACL Rules ACL statement sequence Highest number in use in the ACL plus 10
Management access-list direction in
Deny/Permit Rule dscp-value All values are filtered.
dst-port-range All values are filtered.
icmp-code All values are filtered.
icmp-type-number All values are filtered.
ip-precedence-value All values are filtered.
ip-protocol-number All values are filtered.
log Disable
sequence-number
src-port-range All values are filtered.
Router clear-statistics access-list direction in
icmp rate-limit unreachable 500

Topic Parameter Default Value
show access-list statistics direction in
Router Interface access-list direction in
clear-statistics access-list direction in
icmp unreachable Enable
show access-list statistics direction in
Management access-list direction in
Configuring ACL
The ACL configuration tasks are performed at the access control, router interface,
and management levels.
To configure ACL:
1. Create an access control list.
2. Add deny and permit rules to the ACL.
3. Bind the ACL to a router interface or management entity.
4. Configure additional ACL parameters (logging interval, ICMP Unreachable
messages etc), if necessary.
Access-Control-Level Tasks
The following commands are available in the CLI access-control context:
config>access-control#. The exception to this are the deny, permit and remark
commands, which are performed in the access-list(acl_name) context:
configure>access-control>access-list(acl_name)#.
Table 6-1. Access-Control-Level Commands
Creating and access-list [{ipv4 | ipv6}] <acl_name> Creating an ACL is performed by assigning
deleting an ACL no access-list <acl_name> a name and specifying the ACL IP type.
The ACL names must be unique.
The ACL name contains up to
252 alphanumeric characters.

Adding deny deny {tcp | udp} {any | <src-address> [/<src- The arguments of the deny rule vary
rules to an ACL prefix-length>]} [<src-port-range>] {any | depending on the protocol (TCP, UDP,
<dst-address>[/<dst-prefix-length>]} [<dst- ICMP, IP).
port-range>] [dscp <dscp-value> | DSCP and IP Precedence cannot be used
precedence <ip-precedence-value>] [log] together.
[sequence <sequence-number>]
Management-bound ACLs have the
deny icmp {any | <src-address> [/<src- following configuration limitations:
prefix-length>]} {any|<dstaddress>
Only TCP- or UDP-based rules can be
[/<dstprefix-length>]} [icmp-type <icmp-
defined.
type-number> [icmpcode <icmp-code-
number>]] [dscp <dscp-value> | precedence The destination IP address must be
<ipprecedencevalue>] [log] [sequence any.
<sequence-number>] For TCP/UDP, the destination port must
deny ip [protocol <ip-protocol-number>] be tcp/23 (Telnet), tcp/22 (SSH),
{any | <src-address> [/<src-prefix-length>]} tcp/830 (NETCONF), , udp/161 (SNMP),
{any |<dstaddress>[/<dstprefix-length>]} or any..
[dscp <dscp-value> | precedence The source port must remain any (i.e.
<ipprecedence-value>] [log] [sequence optional src-port-range field should not
<sequencenumber>] be configured).
DSCP and IP Precedence are not
supported.
log enables logging match events of the
rule into the event log and sending SNMP
traps.
Possible values for sequence:
12147483648.
Note: If the ACL already has a statement
with the same sequence number, the old
statement is replaced with the new one.

Adding permit permit {tcp | udp} {any | <src- The arguments of the permit rule vary
rules to an ACL address>[/<src-prefix-length>]} [<src-port- depending on the protocol (TCP, UDP,
range>] {any|<dst-address>[/<dst-prefix- ICMP, IP).
length>]} [<dst-port-range>] [dscp <dscp- DSCP and IP Precedence cannot be used
value> | precedence <ip-precedence-value>] together.
[set {dscp < dscp-marking-value> |
Management-bound ACLs have the
precedence <ip-precedence-marking-value>
following configuration limitations:
| pbit <pbit-marking-value>}] [log]
[sequence <sequence-number>] Only TCP- or UDP-based rules can be
defined.
permit icmp {any | <src-address>[/<src-
prefix-length>]} {any | The destination IP address must be
<dstaddress>[/<dstprefix-length>]} [icmp- any.
type <icmp-type-number> [icmpcode For TCP/UDP, the destination port must
<icmp-code-number>]] [dscp <dscp-value> be tcp/23 (Telnet), tcp/22 (SSH),
| precedence <ipprecedencevalue>] [set tcp/830 (NETCONF), udp/161 (SNMP) ,
{dscp < dscp-marking-value> | precedence or any..
<ipprecedence-marking-value> | pbit <pbit- The source port must remain any (i.e.
marking-value>}] [log] [sequence optional src-port-range field should not
<sequence-number>] be configured).
permit ip [protocol <ip-protocol-number>] DSCP and IP Precedence are not
{any | <src-address>[/<src-prefix-length>]} supported.
{any |<dstaddress>[/<dstprefix-length>]}
log enables logging match events of the
[dscp <dscp-value> | precedence
rule into the event log and sending SNMP
<ipprecedence-value>] [set {dscp < dscp-
traps.
marking-value> | precedence <ip-
Possible values for sequence:
precedence-marking-value> | pbit <pbit-
12147483648.
marking-value>}] [log] [sequence
<sequencenumber>] Note: If the ACL already has a statement
with the same sequence number, the old
statement is replaced with the new one.
Adding remarks remark <description> [sequence <sequence- The description contains up to 255
to an ACL number>] characters.
Reseqencing the resequence access-list <acl-name> Possible values for value: 1100000
rules in an ACL [<value>]
Removing rules delete <sequence-number> Possible values for sequence-number:

from an ACL 12147483648.
Setting the logging access-list <value> Enable logging at the maximum rate of the
logging interval no logging access-list value set at Access Control level. <0> is
of all ACLs equivalent to no logging access-list
command.
no logging access-list disables event
logging for all rules in the ACL.
Router-Level Tasks
The following commands are available in the CLI router-interface context:
router(number)> interface(number)#. The exception to this are the show access-

list summary and show access-list statistics commands, which can be used in the
router(number) context as well.
Table 6-2. Router-Interface-Level Commands
Binding the ACL access-group <acl-name> in

to a router no access-group in{ipv4 | ipv6}
interface and
defining the ACL
direction
Sending/stop unreachables
sending ICMP no unreachables
Unreachable
messages
Displaying ACL show access-list statistics See Displaying Statistics below.

statistics
Clearing ACL clear-statistics access-list Router interface level

statistics clear-statistics access-list [interface Router level
<router-interface>
Displaying the show access-list summary Displays ACL status at the current level
summary of ACLs See Displaying Status below.
bound to router
interface
Management-Level Tasks
The following commands are available in the CLI management context:
configure>management>access#.

Table 6-3. Management-Level Commands
Binding the ACL access-group <acl-name> in The management entity supports the ACLs
to a no access-group in {ipv4 | ipv6} only in the in direction.
management When binding the ACL to the management
entity and entity, or when adding/editing rules in an
defining the ACL ACL that is bound to the management
direction entity, the rules must conform to the
following limitations:
The protocol rules must be of TCP/UDP
type.
The destination address must be set to
any.
The source port must be set to any.
The destination port must be tcp/830
(NETCONF), tcp/23 (Telnet), tcp/22
(SSH), udp/161 (SNMP), or any.
DSCP, IP precedence, and P-bit cannot
be used.
Displaying ACL show access-list statistics See Displaying Statistics below.

statistics
Clearing ACL clear-statistics access-list

statistics
Displaying the show access-list summary Displays ACL status at the current level
summary of ACLs See Displaying Status below.
bound to a
management
entity
Examples
Management ACL
To create management ACL:

The example below illustrates a typical ACL applied to the incoming management
traffic:
Allows SSH (TCP port 22) traffic from any source
Denies and logs incoming Telnet (TCP port 23) connections from any source,
except for 192.168.1.0 subnet
access-control>access-list(mng)#
remark Allow incoming SSH traffic
permit tcp any any 22
remark Allow Telnet traffic coming from 192.168.1.0 subnet
permit tcp 192.168.1.0/24 any 23
remark Deny and log incoming Telnet traffic
deny tcp any any 23 log

The table below summarizes the rules configured for the ACL. Items in red are
either implied or unavailable for the current parameter or serve as system
settings that cannot be changed. The deny rule appearing in the bottom row is a
system rule that is used to deny all non-compliant data.
Sequence Action Protocol Source IP TCP/UDP Dest. IP TCP/UDP Dest. Port Log
Number Source Port
10 Permit TCP Any Any Any 22 No
20 Permit TCP 192.168.1.0/24 Any Any 23 No
30 Deny TCP Any Any Any 23 Yes
40 Deny IP Any N/A Any N/A No
Router ACL
To create router ACLs:

The example below illustrates two typical ACLs applied to the incoming and
outgoing traffic.
Incoming traffic ACL:
Allows TCP traffic from ports 1024 or higher
Allows and logs incoming SMTP connections to 192.168.1.100
Allows incoming pings
access-control>access-list(permit_incoming)#
remark Allow incoming TCP traffic from ports 1024 or higher
permit tcp any 192.168.1.0/24 1024..65535
remark Allow and log incoming SMTP connection to 192.168.1.100
permit tcp any 192.168.1.100 25 log
remark Allow incoming pings
permit icmp any 192.168.1.0/24
Sequence Action Protocol IP Source IP TCP/UDP Dest. IP TCP/UDP ICMP ICMP ToS Mark Log
Number Protocol Source Port Dest. Port Type Code
10 Permit TCP N/A Any Any 192.168.1.0/24 1024..65535 N/A N/A Any No
20 Permit TCP N/A Any Any 192.168.1.100 25 N/A N/A Any Yes
30 Permit ICMP N/A Any N/A 192.168.1.0/24 N/A Any Any Any No
40 Deny IP Any Any N/A Any N/A N/A N/A Any N/A No
Outgoing traffic ACL:

Denies Web access from 192.168.1.10, allows other traffic
Permits Web access for the other stations on the 192.168.1.0 subnet
access-control>access-list(outgoing_rules)#
remark Deny 192.168.1.10 web access; allow other traffic

deny tcp 192.168.1.10/32 any 80

permit ip 192.168.1.10/32 any
remark Permit others on the 192.168.1.0 subnet web access
permit tcp 192.168.1.0/24 any 80
Sequence Action Protocol IP Source IP TCP/UDP Dest. IP TCP/UDP ICMP ICMP ToS Mark Log
Number Protocol Source Port Dest. Port Type Code
10 Deny TCP N/A 192.168.1.10 Any Any 80 N/A N/A Any N/A No
20 Permit IP Any 192.168.1.10 N/A Any Any N/A N/A Any No
30 Permit TCP N/A 192.168.1.0/24 Any Any 80 N/A N/A Any No
40 Deny IP Any Any N/A Any N/A N/A N/A Any N/A No
Table 6-4 lists the messages generated by the device when a configuration error
is detected.
Message Description
Cannot execute; invalid statement Invalid matching rule. For example, binding the ACL with a rule,
using a protocol other than TCP or UDP to the management
entity.
Cannot add statement; sequence Invalid sequence number of the rule. Allowed sequence number
number out of range range is 12147483648.
Cannot resequence; sequence number Resequencing has failed because the ACL interspace value is
out of range invalid.
Cannot clear; no such router interface Statistic counters cannot be cleared on the non-existing router
interface.
Cannot bind; no such access list A non-existing ACL cannot be bound to the router interface or
the management entity.
Cannot show; no such router interface Statistic counters cannot be displayed on the non-existing
router interface.
Cannot bind; invalid statement An access list with statements, which are not supported by the
management ACL, cannot be attached to the management
entity.
Displaying Status
The ACL status displays information on the ACL name, type (IPv4 or IPv6), and the
entity that the ACL is bound to. The status information is available for the ACLs at
the router, router interface, and management access levels.

To display the ACL status (router):

1. Navigate to the required prompt (router(number)#, router(number)>
interface(number)#).
2. Enter the show access-list summary command.
The following status information is displayed:
ACL Name|Type|Bound to |Direction
--------|----|----------|---------
my-acl |IPv4|RI 2 |In
To display the ACL status (management):

In the config>mngmnt>access# prompt, enter the show access-list summary
command.
The following status information is displayed:
ACL Name Type Bound to Direction
---------------------------------------------------------------
MNG_port_1 IPv4 management inbound
Displaying Statistics
The ACL statistic counters gather information on the number of rule matches
registered on the ACL since the last reboot or counter clearing.
Note All ACLs have an implied last rule that denies all packets. The device does not
provide statistic counters for this rule. If you intend to collect statistics on the
number of packets discarded by the default ACL mechanism, you must add the
deny ip any any rule at the end of the ACL.
To display the ACL statistics (router):

1. Navigate to the required prompt (router(number)#, router(number)>
interface(number)#).
2. Enter the show access-list statistics command as explained in the tables
above.
The following statistic information is displayed:
IPv4 access list: block-invalid-traffic-in (in)
Bound to:
Router: 1, Interface: 2
Matches counted for: 7 seconds
10 deny tcp any any dscp 17 (5 matches)
To display the ACL statistics (management):

In the config>mngmnt>access# prompt, enter the show access-list statistics
command.
The following statistic information is displayed:
IPv4 access list: MNG_port_1 (in)
Bound to: Management
Matches counted for: 0 days 0 hours 2 minutes 33 seconds
---------------------------------------------------------------

10 permit tcp 172.17.154.154/24 any 22 log (0 matches)

20 permit tcp 172.17.154.154/24 any 23 log (0 matches)
30 permit udp 172.17.154.154/24 any 161 log (0 matches)
6.2 GUI-Based Configuration
Preconfiguring ETX2i for SNMP Management

ETX2i can be managed by any SNMP-based network management station, such
as via the RADview family of network management stations, provided IP
communications is possible with the management station, as well as by the
standalone RADview stations.
To manage ETX2i from a remote NMS, it is necessary to preconfigure the basic
parameters using a supervision terminal connected to the ETX2i CONTROL DCE
port.
To configure ETX2i for management access:

Add an SVI port.
Create classifier profiles for matching all traffic and matching untagged
traffic.
Add two flows (incoming and outgoing) connecting the out-of-band Ethernet
Add a router interface, bind it to the SVI, and add a static route to the next
hop.
The following script provides the necessary configuration steps for ETX2i, ETX-2i-
B, and ETX-2i-10G. Replace IP addresses and entity names with values suitable
for your network environment.
#*******************************Adding_SVI*********************
config port
svi 99
no shutdown
exit all
#***************************Adding Classifier_Profiles*********
config flows
#***************************Configuring_Flows******************
flow mng_in
classifier untagged
no policer
egress-port svi 99
no shutdown
exit
flow mng_out
6-12 GUI-Based Configuration ETX2i

classifier all
ingress-port svi 99
no shutdown
exit all
#*********************Configuring_Router_Interface*************
configure router 1
interface 1
bind svi 99
address 172.18.141.39/24
no shutdown
exit
exit all
save
Working with RADview
Overview
RADview is a Windows-based modular, client-server, scalable management
system that can be used in a distributed network topology or a single-station
configuration. RADview consists of the system and the following optional
modules:
D-NFV Orchestrator D-NFV Orchestrator creates, configures and manages
virtual machines on the X.86 D-NFV module within RADs customer edge
devices. D-NFV Orchestrator accommodates the Network Planning
functionality, which is part of RADview-Service Manager and enables offline
planning of networks with RAD products.
Service Manager (SM) end-to-end Carrier Ethernet service provisioning for
Ethernet Access products. This module includes the Service Center (SC)
module, which is an end-to-end Carrier Ethernet and TDM service provisioning
for AXCESS+ products.
Performance Monitor (PM) portal for service SLA monitoring for both
carriers and their customers
The ETX2i element and network management systems include a CORBA
northbound interface, enabling easy integration into the customers umbrella
NMS. CORBA enables interconnectivity and communication across heterogeneous
operating systems and telecommunications networks. CORBA effectively supplies
a software interface that defines data models used between various
management layers. It supports multi-vendor distributed network management
applications, providing the data interface between clients and servers.
For more details about the RADview network management software, and for
detailed instructions on how to install, set up, and use RADview, contact your
local RAD partner.
Preconfiguration for Service Discovery

You can discover services via RADview, and view statistics for services and ports
in the RADview Performance Monitoring portal. This also allows you to ensure
that SLAs are being met. In order to do so, you need to perform the following:
ETX2i GUI-Based Configuration 6-13

Configure service with parameters that enable RADview to recognize the

flows that correspond to the service, as follows:
Configure Rx and Tx traffic flows with the same service ID.
Assign the above Rx and Tx flows to the MEP corresponding to the
service.
Note The service name configuration is necessary only in the endpoint devices.
Enable PM collection for the Rx and Tx flows, as well as for the corresponding
destination NE.
All flows belonging to the same service End Point must use the same port.
Only one S-tag should be used for the service.
Run the RADview Discovery Service function (refer to the RADview online
help).
Discovery can be performed only on the user port (UNI). For more information,
refer to the Performance Management section.
Note Multi-port E-Line services can't be discovered and statistics can't be collected on
the flows.
Working with Shelf View

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

ETX2i can be integrated into third-party network management systems at the
following levels:
Viewing device inventory and receiving traps (refer to the Monitoring and
Diagnostics chapter for trap list)
Managing device, including configuration, statistics collection, and
diagnostics, using the following standard and private MIBs:
CFM MIB (IEEE8021-CFM-MIB)
IANAifType-MIB
IETF Syslog Device MIB
IEEE8023-LAG-MIB
MEF-R MIB
RAD private MIB
RFC 2819 (RMON-MIB)
6-14 GUI-Based Configuration ETX2i

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)
6.3 Access Policy

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

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

stored database
ETX2i Access Policy 6-15

Specifying authentication method auth-policy 1st-level tacacs+ [2nd-level { If 2nd-level is set to local, authentication is
preferably via TACACS+, then local | none } ] performed via the TACACS server. If the
optionally local TACACS server does not answer the
authentication request, then ETX2i
authenticates via the local database. .If the
TACACS server rejects the authentication
request, ETX2i ends the authentication
process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
Specifying authentication method auth-policy 1st-level radius [2nd-level ETX2i first attempts authentication via the
preferably via RADIUS/ TACACS+, then tacacs+ [3rd-level {local | none}]] server specified by 1st-level. If the server
optionally TACACS+/ RADIUS, then auth-policy 1st-level tacacs+ [2nd-level does not answer the authentication
optionally local radius [3rd-level {local | none}]] request, then ETX2i attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then ETX2i
attempts to authenticate according to
3rd-level:
local ETX2i 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, ETX2i ends the
authentication process and does not
attempt authentication at the next level.
6.4 Authentication via RADIUS Server

RADIUS (Remote Authentication Dial-In User Service) is an AAA (authentication,
authorization and accounting) client/server protocol that secures networks
against unauthorized access. It is used to authenticate users and authorize their
access to the requested system or service. The RADIUS client communicates with
the RADIUS server using a defined authentication sequence.
Applicable Products
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS)
6-16 Authentication via RADIUS Server ETX2i

RFC 2618, RADIUS Authentication Client MIB
Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device in the
network.
Due to its generic nature, the RADIUS protocol can easily be used by service
providers and enterprises to manage access to the Internet, internal networks,
wireless networks, and integrated email services. These networks may
incorporate DSL, access points, VPNs, network ports, and more.
RADIUS servers have built-in mapping of users to service-types (Table 6-5). Note
that each user has the rights of all users above it. All users have default password
1234. It is highly recommended to change the default password when setting up
your device (Refer to Changing Password on how to change a password).
Table 6-5. RADIUS Service-Types
Name Prompt RADIUS Service-Type (User Access Level)
user ETX2i% 1 (login)
tech ETX2i% 7 (NAS prompt)
oper ETX2i# 8 (authenticate only)
su ETX2i# 6 (administrative)
When a user attempts to log in to ETX2i, the following occurs:

User is prompted to enter their username and password.
RADIUS client submits an authentication request to the RADIUS server. The
username and encrypted password is transmitted over the network. (A hash
code is generated over the entered password and a previously defined shared
secret (string of free text) is transmitted between the RADIUS server and
ETX2i unit.)
The RADIUS server verifies the user information against a database stored at
the RADIUS server, and sends one of the following responses:
Access Rejected User is not authenticated and access to all resources is
denied. User is prompted to reenter their username and password.
Access Accepted User is authenticated. Access to the requested
network resources is granted. The RADIUS service type is sent, indicating
what services the user can access.
ETX2i Authentication via RADIUS Server 6-17

Verifying credentials and privileges via RADIUS data base
Logon request to ETX-2i
Network
Logging on to ETX-2i or
returning authentication error ETX-2i
RADIUS Server
Management Work Station Access accepted or denied
Shared Secret
Figure 6-1. RADIUS Server Operation Scheme
Factory Defaults
By default, no RADIUS servers are defined. When the RADIUS server is first
defined, it is configured as shown below.
IP address of server 0.0.0.0
Key Empty string
Max number of authentication attempts 3
Time interval between two authentication attempts 3 seconds
UDP port used for authentication 1812
Configuring RADIUS Parameters

ETX2i provides connectivity to up to four RADIUS authentication servers. You
have to specify access parameters such as Radius server ID, associated server IP
address, the number of allowed authentication request attempts, etc.
To define a RADIUS server:

At the config>mngmnt>radius# prompt, type server <1..4> to specify which
server to configure.
The config>mngmnt>radius>server(<1..4>)# prompt is displayed.
Enter the necessary commands according to the tasks listed below.
Assigning an IP address to the server address <ip-address> A valid unicast IP address
6-18 Authentication via RADIUS Server ETX2i

Defining a non-disclosed string (shared key <string> [hash] The shared secret is a secret key
secret) used to encrypt the user consisting of free text known to
password. the client and the server for
encryption.
The hash keyword denotes that
the string is hashed, rather than
clear text; usually it is added by
the device after hashing the clear
text that the user enters, before
saving it in the database.
If you enter the password as a
text string, do not use the hash
parameter. Use it only if you are
specifying the password as a
hashed value (obtained by using
the info command to display
RADIUS data).
Defining the number of authentication retry <number-of-retries> Possible values: 010

request attempts
Defining timeout (in seconds) for timeout <seconds> Possible values: 15

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

administratively disable the
server.
Displaying status show status
Viewing RADIUS Statistics

To display RADIUS statistics:
At the config>mngmnt>radius# prompt, enter:
show statistics
RADIUS statistics appear as shown below.
ETX2i>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
ETX2i Authentication via RADIUS Server 6-19

Timeouts :0 0 0 0
Unknown Types :0 0 0 0
Packets Dropped :0 0 0 0
To clear the statistics for RADIUS:

At the config>mngmnt>radius# prompt, enter:
clear-statistics
The RADIUS statistics are cleared.
6.5 Authentication via TACACS+ Server

TACACS+ (Terminal Access Controller Access Control System Plus) is a security
application that provides access control for routers, network access servers, and
other networked computing devices via one or more centralized servers. TACACS+
provides separate authentication, authorization, and accounting services. It is
used to communicate between the switch and an authentication database. As
TACACS+ is based on TCP, implementations are typically resilient against packet
loss.
Applicable Products
Standards
TACACS+ Protocol Version 1.78 (IETF draft-grant-tacacs-02)
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet, but leaves a
standard TACACS+ header.
Customers do not have to adapt their TACACS+ server privilege levels to RAD CLI
default values; CLI levels can be remapped in accordance with the customers
TACACS+ levels.
Factory Defaults
By default, no TACACS+ servers are defined. When the TACACS+ server is first
defined, it is configured as shown below.
Parameter Default Value
key Empty string
retry 1
6-20 Authentication via TACACS+ Server ETX2i

timeout 5 seconds
authentication-port 49
accounting-port 49
Administrative status shutdown
Accounting group membership None
TACACS+ is a protocol that provides access control for routers, network access
servers, and other networked computing devices via one or more centralized
servers. TACACS+ is based on the AAA model:
Authentication The action of determining identity of a user
Authorization The action of determining what a user is allowed to do. It can
be used to customize the service for the particular user.
Accounting The action of recording what a user is doing, and/or has done
The TACACS+ client can be configured to use authentication/authorization with or
without accounting functionality.
When configuring users on external TACACS+ servers, see Table 6-6 to define
authorization levels for ETX2i standard users. Note that each user has the rights
of all users below it, in addition to those explained in its description.
Table 6-6. TACACS+ Authorization Levels
Level User Allowed Actions Description
3 user Monitoring Commands that do not affect

services, traffic, or configuration
6 tech Diagnostics Commands that may affect services

and traffic, but are not saved in the
database
9 oper Configuration Commands that change

configuration parameters
permanently
12, 15 su User management Commands that manage users in the

database
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
The access client is an entity which seeks the services offered by the
network.
ETX2i Authentication via TACACS+ Server 6-21

TACACS+ client, running on ETX2i, processes the requests from the access
client and passes this data to TACACS+ server for authentication.
TACACS+ server authenticates the request, and authorizes services over the
connection. The TACACS+ server does this by matching data from the
TACACS+ client`s request with entries in a trusted database.
TACACS+ server decides whether to accept or reject the user's authentication or
authorization. Based on this response from the TACACS+ server, the TACACS+
client decides whether to establish the user's connection or terminate the user's
connection attempt. The TACACS+ client also sends accounting data to the
TACACS+ server to record in a trusted database.
TACACS+ uses TCP for its transport and encrypts the body of each packet.
TACACS+ client and server can agree to use any port for authentication and
accounting. TACACS+ supports authentication by using a user name and a fixed
password.
Accounting
ETX2i supports up to five accounting groups, with up to five TACACS+ servers per
group. However, each TACACS+ server can be bound to a single accounting group
only.
A group can be defined with its own accounting level:
Shell accounting, which logs the following events:
Successful logon
Logon failure
Logoff
ETX2i - 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 ETX2i
Any level that was successfully changed in a shell
Mapping Privilege Levels

ETX2i supports software configuration of mapping CLI levels to TACACS+ privilege
levels.
There are 16 TACACS+ privilege levels.
You can map a CLI level to multiple TACACS+ levels.
You cannot map a TACACS+ level to multiple CLI levels. If the command is
repeated for a TACACS+ level, the new mapping replaces the old one.
You can unmap both TACACS+ and CLI levels, with the exception of su, which
must be mapped to at least one TACACS+ level.

Configuring TACACS+ Server

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

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.
Enter the necessary commands according to the tasks listed below.
Defining the TCP port to be used for accounting-port <port-number> Possible values: 165535
accounting
Defining the TCP port to be used for authentication-port <port-number> Possible values: 165535
authentication
Binding accounting group to TACACS+ group <string> no group detaches accounting

server group from server.
Defining a non-disclosed string (shared key <string> [hash] The shared secret is a secret
secret) used to encrypt the user key consisting of free text
password known to the client and the
server for encryption.
The hash keyword denotes
that the string is hashed,
rather than clear text; usually
it is added by the device after
hashing the clear text that
the user enters, before saving
it in the database.
If you enter the password as
a text string, do not use the
hash parameter. Use it only if
you are specifying the
password as a hashed value
(obtained by using the info
command to display TACACS+
data).
Defining the number of authentication retry <number-of-retries> Permanently set to 1

request attempts
Defining timeout (in seconds) for timeout <seconds> Possible values: 130
response from TACACS+ server

Administratively enabling server no shutdown shutdown administratively

disables the server.
Displaying statistics show statistics
Configuring Accounting Groups

To configure accounting groups:
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.
To define the accounting for the group, enter:
accounting [shell] [system] [commands]
Notes You can enter any combination of the parameters shell, system, or commands,
but you must enter at least one of them
Type no accounting to disable TACACS+ accounting for the group.
Type exit to return to the TACACS+ level.

The config>mngmnt>tacacsplus# prompt is displayed.
Type server <ip-address> to select the TACACS+ server to which to bind the
group.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, enter
group < group-name> to bind the previously defined accounting group to the
TACACS+ server.
Mapping CLI Levels to TACACS+ Privilege Levels

To map a CLI level to a TACACS+ privilege level:
At the config>mngmnt>tacacsplus# prompt, type
privilege-level <tacacs-privilege-level> {su|oper|tech|user}.
The tacacs-privilege-level value can be 0-15.
Note Type no privilege-level <tacacs-privilege-level> to remove TACACS+ privilege level

mapping.
Example Defining Server

The example below illustrates the procedure for defining a TACACS+ server.

Server IP address: 175.18.172.150

Key: TAC_server1
exit all
configure management tacacsplus
server 175.18.172.150
key TAC_server1
no shutdown
exit all
save
To display the configuration from the above example:

ETX2i# configure management tacacsplus server 175.18.172.150
ETX2i>config>mngmnt>tacacsplus>server(175.18.172.150)# information detail
key "244055BF667B8F89225048C6571135EF" hash
retry 1
timeout 5
accounting-port 49
no group
no shutdown
Example Defining Accounting Group

The example below illustrates the procedure for defining an accounting group.
Group name: TAC1
Accounting: Shell, system, and commands
Bound to server defined in Example Defining Server
exit all
configure management tacacsplus
group TAC1
accounting shell system commands
exit
server 175.18.172.150
group TAC1
exit all
To display the configuration from the above example:

ETX2i# configure management tacacsplus server 175.18.172.150
ETX2i>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89829AB8AB0FE50885" hash
retry 1
timeout 5
accounting-port 49
group "TAC1"
no shutdown

Example Mapping CLI Level to Privilege Level

To map TACACS+ level 7 to the CLI user level:
ETX2i# configure management tacacsplus privilege-level 7 user
To delete the mapping of TACACS+ level 7 to the CLI user level:

ETX2i# configure management tacacsplus no privilege-level 7
The following table lists the messages generated by ETX2i when a configuration
error is detected.
su level must be mapped to a You tried removing the last Leave at least one mapping of su.
TACACS+ level mapping of su, but su must be
mapped to at least one
TACACS+ level.
Viewing TACACS+ Statistics

To display TACACS+ statistics:
At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, type:
show statistics.
The TACACS+ statistic counters are displayed.
ETX2i>config>mngmnt>tacacsplus>server(175.18.172.150)$ show statistics
Requests 0
Request Timeouts 0
Unexpected Responses 0
Server Error Responses 0
Incorrect Responses 0
Transaction Successes 0
Transaction Failures 0
Pending Requests 0
Table 6-8. TACACS+ Statistic Counters
Counter Description
Requests Number of authentications performed toward a specific TACACS+ server
Request Timeouts Number of transaction timeouts that occurred between the client and
server
Unexpected Responses Number of times the TACACS+ client receives a TACACS+ packet that is
not expected at that time. Usually, this occurs due to a delayed response
to a request that has already timed out

Counter Description
Server Error Responses Number of errors received from the TACACS+ server
Incorrect Responses Number of times the TACACS+ client:

Fails to decrypt the packet
Detects an invalid field in the TACACS+ packet
Receives a response that is not valid according to the initial request
Transaction Successes Number of successful transactions between the client and TACACS+
server
Transaction Failures Number of times the TACACS+ 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.
6.6 Control Port

You can configure the serial port parameters, which include specifying the data rate,
security timeout, and screen size from which you are accessing the device. You can also
disable management via the console serial port.
Applicable Products
Factory Defaults
By default, data rate is set to 9600 bps.
Configuring Control Port Parameters

To define the control port parameters:
At the config>terminal# prompt, enter the necessary commands according to
the tasks listed below.
Specifying the desired data rate baud-rate { 9600bps | 19200bps | The default data rate is 9,600 bps.
38400bps | 57800bps | 115200bps
ETX2i Control Port 6-27

Defining whether in case of inactivity, timeout forever If you define a timeout, the timeout value
device remains connected or timeout limited <minutes> can be 060. The default is 10 minutes.
disconnects after a specified time
period
Disabling the control port serial-port-disable Once this command is issued, console
no serial-port-enable (default) access is denied for normal operation.
Access is allowed only during boot process.
Management connectivity can be resumed in
one of the following ways:
Entering no serial-port-enable command
via remote access (Inband or OOB via
Telnet, SNMP).
Setting to default configuration, by
pressing the external push button on the
front panel.
Specifying the number of rows to length <number-of-rows> The number of rows can be 0, to indicate
display no limit on the number of lines displayed, or
20.
6.7 DHCP Relay

A device can function as DHCP client and relay at the same time.
This section describes the DHCP relay component, including how it receives,
intercepts, and forwards DHCP requests and replies not destined to the device
itself.
Note Packets sent from or to the device itself are not related to the DHCP relay
functionality.
You can enable the following Layer-2 DHCP Relay agent features on your device
or on specific services of your device:
DHCP Snooping Configuration of servers and relay ports as trusted, and
client ports as untrusted.
DHCP Option 82 Add additional information to the DHCP request, including
Remote ID and Circuit ID.
Note DHCP Relay applies to DHCPv4 only.
Standards
[RFC 1542] Clarifications and Extensions for the Bootstrap Protocol
[RFC 2131] Dynamic Host Configuration Protocol
6-28 DHCP Relay ETX2i

[RFC 2132] DHCP Options and BOOTP Vendor Extensions

[RFC 3046] DHCP Relay Agent Information Option
Benefits
Layer-2 DHCP Snooping verifies DHCP transactions and protects against rogue
DHCP servers and clients.
The DHCP server uses the Remote ID and Circuit ID information provided by
DHCP option 82 for the address allocation scheme.
A DHCP relay agent at Layer-2 forwards requests and replies between clients and
servers that are on the same Layer-2 subnet but not on the same physical
subnet. Unlike normal Layer-2 forwarding, in which IP datagrams are switched
transparently, a relay agent receives DHCP messages and generates new ones to
send on output interfaces.
DHCP servers are assumed to reside in trusted locations, usually beyond network
ports, while DHCP clients reside in untrusted locations, usually behind user ports.
Each port is configured as either DHCP trusted or untrusted.
The device can be configured with two DHCP functionalities:
DHCP Snooping
DHCP Option 82
DHCP Messages
The following table [per RFC 2131] describes the various DHCP client and server
messages:
Table 6-9. DHCP Messages
Message Use Sent By
DHCPDISCOVER Locate available servers. Client
DHCPOFFER Offer configuration parameters in response to DHCPDISCOVER. Server
DHCPREQUEST Accept, confirm, or extend an offer, implicitly declining others. Client
DHCPACK Commit client request. Server
DHCPNAK Decline client request. Server
DHCPDECLINE Indicate that the committed address is already in use. Client
DHCPRELEASE Relinquish address and cancel remaining lease. Client
DHCPINFORM Ask for configuration; address has been externally configured. Client
ETX2i DHCP Relay 6-29

DHCP Snooping
DHCP relay supports DHCP snooping on the device (or specific services), for
added security. Servers and relay ports should be configured as trusted, and
client ports as untrusted.
In addition to verifying the validity of incoming DHCP messages, when enabled,
the DHCP relay does the following:
Blocks server DHCP messages (DHCPOFFER, DHCPACK, and DHCPNACK)
arriving from untrusted ports; allows from trusted ports.
Blocks client DHCP messages (DHCPDISCOVER, DHCPREQUEST, DHCPDECLINE,
DHCPRELEASE and DHCPINFORM) when they arrive from trusted ports; allows
from untrusted ports.
Forwards DHCP server packets only to untrusted ports and DHCP client
packets only to trusted ports.
DHCP snooping over a specific EVC is indicated by its Service ID (configured
over all EVC flows).
DHCP Option 82
The device (or specific services) can also be configured to enable DHCP option 82
(the relay agent information option). If enabled, upon intercepting a client DHCP
packet the relay agent adds option 82 to the DHCP request before forwarding the
packet to the DHCP server.
The following information is added to the DHCP request:
Remote ID the agent identification; usually agent MAC address
Circuit ID usually identification of the port and VLAN of the switch from
which the request was received.
Note The format of the Remote ID and Circuit ID suboptions is configurable.
The reply from the server is forwarded back to the client after removing option
82.
Figure 6-2 describes the flow of DHCP packets through a relay when option 82 is
enabled.
1. The DHCP client broadcasts a DHCP request.
2. The DHCP relay agent intercepts the request, and performs a sanity check on
the packet.
3. If it is not valid, it discards the message.
4. Otherwise, if it is valid, inserts option 82 in the packet and broadcasts it
towards the DHCP server. Option 82 information includes the two configured
suboptions: Circuit ID and Remote ID.
5. The DHCP server assigns an IP address based on the option 82 suboptions
and sends a lease back to the client.
6. The relay agent performs a sanity check on the packet and strips option 82
(Remote ID and Circuit ID fields) off the packet before forwarding the packet
to the client.

Figure 6-2. DHCP Relay Agent Process
Factory Defaults
By default, no DHCP relay parameters are configured for ports. The system DHCP
relay parameters have the default values shown in the following table.
dhcp-option-82 no dhcp-option-82
dhcp-snooping no dhcp-snooping
Configuring DHCP Relay

DHCP relay is configured as follows:
System level DHCP relay features (Option 82 and snooping) must be
enabled or disabled for the entire device or a specific service.
Port level For each port through which DHCP packets can be received and
sent (Ethernet, internal Ethernet, LAG, Logical MAC, and PCS), the device
supports configuration of the port as DHCP trusted or untrusted.
The snooping functionality can be enabled for all ingress traffic from the
ports or to traffic of specific services as configured in dhcp-snooping (see
table below).
Refer to port configuration sections in Chapter 6 to set port
dhcp-trust/untrust.
System Parameters
This section explains how to enable or disable DHCP Option 82 and DHCP
Snooping for the device.
You can enable DHCP Option 82 and DHCP Snooping globally for the entire device
(i.e. all services) or for a specific service. You can repeat the command for each
service on which to enable the feature.
Note
If a feature is enabled for all services, the feature applies to all services,
regardless of service-specific configuration. If it is not enabled for all services, it
applies only to those services for which it was explicitly enabled.
ETX2i DHCP Relay 6-31

It is possible to enable DHCP option 82 for the entire device, but set the format
of its sub-options (Circuit ID and Remote ID) either globally or per service.
You can disable these features on all services using the no form of the command.
To configure DHCP relay system parameters:
1. Navigate to configure system dhcp-relay.
The config>system>dhcp-relay# prompt is displayed.
Enabling DHCP option 82 dhcp-option-82 {all | service <service-name>} service the service on which to
[circuit-id {vlan-card-port | string <circuit-id- enable option 82
string>}] [remote-id {mac | hostname | string Possible values: all, service name (1-
<remote-id-string>} 31 characters)
no dhcp-option-82 {all | service <service-name>} circuit-id circuit ID format
Possible values: vlan-card-port
(default) , string (0-253 characters)
remote-id remote ID format
Possible values: mac (default),
hostname (SNMP sysName), or
string (0-253 characters)
Notes:
If hostname is chosen, if SNMP
sysName is > 253 characters, or
if SNMP sysName > 253
characters is configured while it
is in use by option 82, the
following message is displayed:
Only first 253 characters of
hostname are used in DHCP
option 82 remote ID.
Option 82 suboptions format
can be configured for a specific
service to be different from the
global configuration; however,
option 82 cannot be disabled on
a specific service if it is globally
enabled.
Both circuit-ID and remote-ID
suboptions are always sent if
option 82 is enabled.
Enabling DHCP snooping [no] dhcp-snooping {all | service <service-name>} service the service on which to
enable snooping.
Possible values: all, service name (1-
31 characters)
all All ports traffic is subjected to
snooping functionality.

6.8 DHCP Server

ETX2i supports Dynamic Host Configuration Protocol (DHCP) server functionality
for IPv4 clients. Based on the Bootstrap Protocol (BOOTP), DHCP server assigns to
DHCP clients IPv4 addresses from configured pools, as well as various
configuration parameters (DHCP options), in response to the broadcast requests
of DHCP clients. In addition, DHCP relays can negotiate DHCP information on
behalf of a client, if the client and server are not directly connected. This
functionality eliminates the need to manually assign an IP address for each
potential client.
Notes DHCP server, relay, and client applications are independent. You can configure
neither or any combination of them.
DHCP server is not supported on tunnel interfaces.
Applicable Products
This feature is applicable to ETX2i with an embedded router.
Standards
[RFC 951] Bootstrap Protocol
[RFC 1542] Clarifications and Extensions for the Bootstrap Protocol (relay agent
requirements)
[RFC 2131] Dynamic Host Configuration Protocol
[RFC 2132] DHCP Options and BOOTP Vendor Extensions (basic DHCP options)
[RFC 3046] DHCP Relay Agent Information Option (DHCP option 82)
Benefits
The main benefits of DHCP servers are:
Reduced costs of IP addresses There is no need to buy and manage an IP
address for each potential client. For example, there is no need to manually
assign an address for each machine that is connected to the network, even
briefly or rarely.
Reduced access costs Dynamic addresses are cheaper than static
addresses.
Reduced client configuration costs DHCP ease of configuration leads to fast
deployment and less operational overhead. There is no need to manually
configure connectivity parameters on each client, except for very basic
configuration (and sometimes not even this). The DHCP server can even start
a zero touch configuration process, which completely configures the client
without network manager intervention.
Centralized management Network managers only need to configure a single
central server. If a global parameter, e.g. DNS server, is changed, there is no
need to manually configure all the clients in the network.
ETX2i DHCP Server 6-33

The following describes the DHCP flow, from the time the client sends a
broadcast DHCP request and until the IP addresses are distributed.
The DHCP client sends to the DHCP server a broadcast DHCP request. If the
client and server are not directly connected to each other, the DHCP
messages can be forwarded by a DHCP Layer 2 or Layer 3 relay agent.
The DHCP relay agent (if one exists) intercepts the request, optionally inserts
the relay agent information option (option 82) into the packet, and
broadcasts it toward the DHCP server.
Any listening DHCP server can assign an IP address to the DHCP client (based
on information sent by the client or relay agent), as well as other options.
Before assigning an IP address, the server pings it. If a reply is received, this
means the address is a conflict, meaning it is an address that is already
occupied. The conflict enters the conflicts table.
DHCP server sends back to the client a lease offer, containing an IP address
and possibly other parameters. It sends its IP address in option 54 (server
identifier) to the client.
Note If the DHCP server offers a lease and the client then sends a DHCP request with
an IP address of a different server (in option 54), the server assumes that the
request is no longer relevant, and return the offered address to the pool of
available addresses.
The relay agent (if one exists) strips Option 82 from the packet (if one
exists), and then forwards the lease offer to the client.
The DHCP client accepts the offer. If the DHCP client received more than one
lease offer, it chooses a lease; usually the first one it received.
Before accepting a lease, a typical client sends a gratuitous ARP to the IP
address it is about to use. If two replies are received, the client should
decline the lease, and the server places the IP address into the conflicts table.
The server acknowledges the lease.
ETX2i saves the lease in a database that includes all active and inactive leases.
The lease database with address binding (IP address to client hardware address)
resides in permanent memory that withstands reboot. If possible, ETX2i assigns
to clients the same IP addresses they previously had.
The lease is usually granted for a limited time; therefore, the DHCP client should
renew it before it expires. A DHCP client may also release a lease once is no
longer needed.
The server does not delete a binding from the database when a lease expires.
However, if a new client asks for an address and the server does not have a free
address, then one of the unused addresses from the database may be used.
The server also saves a table of conflicts. A conflict is an IP address that the
server tried to assign but found out it is already occupied. The server does not
assign an address from the conflicts table unless all non-conflicting addresses
belong to active leases.
6-34 DHCP Server ETX2i

If you change the configuration so that it renders active leases invalid (such as
changing a pools range of addresses or network, excluding an address), the
server removes the leases from the binding database. Addresses in the conflict
database, which are no longer valid, are also removed.
The device may function as DHCP client, relay, or server at the same time.
DHCP Options
The following Tx options (i.e. sent from server to client) are supported by RAD
DHCP server and RAD clients:
Default routers (3) one or two
Lease time (51) offered lease time
Server identifier (54) IP address of the server offering the lease; not
configurable
The following Tx options are supported by RAD DHCP server, but unsupported by
RAD clients:
Domain name system (DNS) servers (6) one or two
Domain name (15)
NetBIOS name server (44)
NetBIOS node type [b, p, m, or h] (46)
The following Rx options (i.e. sent from client to server) are supported by RAD
DHCP server and RAD clients:
Lease time (51) requested lease time
Server identifier (54) IP address of the server whose offer is accepted (also
used by clients to send unicast messages to the server)
Client identifier (61) client unique identifier (typically MAC address)
The following Rx options are supported by RAD clients, but ignored by RAD DHCP
server:
Host name (12) client host name
Vendor class identifier (60) client vendor identifier
Note Options 66 (TFTP server name), 67 (boot file name), and 150 (TFTP server
address) are not supported by RAD DHCP server although RAD clients use
them for the zero touch configuration process.
Unsupported received DHCP options are ignored. They do not invalidate a
request.
Manual Bindings
In cases when it is important that a client, usually a router or server, not change
its address, it is possible to configure manual bindings, i.e. IP addresses that are
manually mapped to clients. This directs the server to grant fixed addresses to
specific clients (usually recognized by their MAC address).

DHCP Lease Offer Message

When offering a lease, the server builds a DHCPOFFER message, locates the
assigned IP address, and adds the following options:
DHCP message type (53) 2, in case of a DHCP offer
Subnet mask (1) The subnet mask of the client, taken from the host or
network command of the pool configuration.
Lease time (51) Time the lease is valid
Renewal (T1) time value (58) time (in seconds) at which the client should
transition to the renewing state.
If the offered lease time is infinite, this option is not sent. Otherwise it is
set to the default, which is 0.5 of the lease time.
Rebinding (T1) time value (59) Time (in seconds) at which the client should
transition to the rebinding state.
If the offered lease time is infinite, this option is not sent. Otherwise, it is
set to the default, which is 0.875 of the lease time.
Server identifier (54) IP address of the server,
Any of the following options, if configured:
Default router (3) one or two IP addresses
DNS server (6) one or two IP addresses
Domain name (15) a string
NetBIOS name server (14) one or two IP addresses.
NetBIOS node type (46) b, p, m, or h
Relay agent information option (82).
If the relay information option was received from the client, the server
sends it back.
The end option (255) Marks the end of valid information in the vendor
field.
Factory Defaults
By default, no DHCP server or DHCP server pool is defined. When a DHCP server
or DHCP server pool is first defined, it is configured as shown below.
DHCP server
number 1
clear --
bind router 1
exclude-address --
shutdown no shutdown
pool No pool

DHCP server pool
address-range no address-range
client-identifier no client-identifier
default-router no default-router
dns-server no dns-server
domain-name no domain-name
hardware-address no hardware-address
host no host
lease-default no lease-default
netbios-name-server no netbios-name-server
netbios-node type no netbios-node type
network no network
relay-information no relay-information
Configuring DHCP Server

You can configure the DHCP server as follows:
Globally enable DHCP server functionality (the default).
By default, no DHCP server exists. Create a single instance of DHCP server
over one of the n VRFs supported in the ETX2i embedded router.
Exclude addresses that should never be assigned to clients; typically
addresses that are statically configured on servers or routers.
Configure DHCP pools containing:
Range of addresses (or a single address) to assign to clients
Various DHCP options to send to clients
Definitions of clients eligible to get lease from the pool
Host and subnetwork inherit options from larger networks (simplifying the
configuration):
For example, a global pool (e.g. 192.168.0.0) can contain global options,
such as domain name.
Additional pools are set for subnets (e.g. 192.168.1.0 and 192.168.2.0),
each with its own default gateway.
To configure the DHCP server:

Navigate to configure system [no] dhcp-server [<number>}.
The config>system>dhcp-server# prompt is displayed.

Note <number> is the number of the dhcp-server, which can only be 1.

Type no dhcp-server to remove the DHCP server from the router.
At the config>system>dhcp-server# prompt, enter the necessary

commands according to the tasks listed below.
Binding DHCP server to router bind router <number> number router number
Note: The DHCP server works only on the
router to which it is bound. If the bound
router does not exist, the DHCP server is
idle.
Clearing DHCP server bindings, clear {binding {address <ipv4-address> | You can clear the entire DHCP server
conflicts, or statistics all} | conflict {address <ipv4-address> | binding database, or binding of a specific
all}} address.
When clearing a specific address, if ipv4-
address does not exist in the database,
an error message is generated:
No such address.
You can clear the entire conflicts
database, or a specific conflicting
address.
Clearing all conflicts clears both
abandoned (declined by clients) and
blocked (already in use) addresses.
Configuring the IP address that is not [no] exclude-address <ipv4-address> A single address to be excluded can be
to be offered to a client configured per command.
Repeating this command adds new excluded
addresses; it does not replace previous
excluded addresses.
Note: Excluded addresses are typically
addresses that are statically configured on
servers or routers.
Configuring DHCP server pool [no] pool See Configuring DHCP Server Pool.
Typing no pool removes the DHCP server
pool and the configuration related to it (IP
address ranges and DHCP options).
Displaying DHCP server bindings show binding See Viewing DHCP Server Binding.
Displaying DHCP server conflicts show conflict See Viewing DHCP Server Conflict.
Displaying DHCP server statistics show statistics See Viewing DHCP Server Statistics.

Disabling/enabling DHCP server [no] shutdown DHCP server functionality is enabled by

functionality default.
Notes:
The DHCP relay and client functions are
not affected by this command.
When disabled, the rest of the server
configuration is ignored.
Configuring DHCP Server Pool

By default, no DHCP server pool exists. The following procedure describes how to
create a DHCP server pool. Each pool must be assigned a unique name.
The DHCP server offers leases based on the pools configurations.
To configure the DHCP server pool:

Navigate to configure system [no] dhcp-server pool [name].
The config>system>dhcp-server>pool# prompt is displayed.
At the config>system>dhcp-server>pool# prompt, enter the necessary
Note Typing no pool removes the DHCP server pool, as well as the configuration
related to it.
You must assign a unique pool name of 1 to 80 characters.
Configuring range of IP addresses that [no] address-range <start-ip> <end-ip> start-ip lowest IPv4 address of the range
server can assign to clients end-ip highest IPv4 address of the range
(relevant only for pool bound to Notes:
network)
An address range can be configured only
if the pool is bound to a network. It is
irrelevant if the pool is bound to a host.
The address range must be inside the
pools subnet (configured with the
network command).
If no range is configured, the default
value is the entire subnet of the pool.
A single range can be configured per
pool.
Typing no address-range <start-ip>
<end-ip> deletes an existing range. If
the specified range is not exactly the
one configured by the command, range
is not deleted.

Configuring client identifier (DHCP client-identifier <unique-identifier> Client identifier (option 61) is used for
option 61) no client-identifier manual binding, i.e. assigning a
preconfigured IP address to a specific client.
unique-identifier client identifier; 1-255
character string
Notes:
Client identifier can be configured only if
the pool is bound to a host (using host
command).
If the command is repeated, it replaces
the previous one.
Either client identifier or hardware
address can be configured; not both.
You cannot configure a client identifier
already configured on another pool.
Typing no client-identifier removes the
client identifier from the pool.
Configuring default router (DHCP default-router <address> [<address-2>] address default router IPv4 address
option 3) no default-router address-2 second default router IPv4
address
Notes:
Repeating this command replaces the
previous one.
address-2 must be different than
address-1.
Configuring DNS server (DHCP option dns-server <address> [<address-2>] address DNS server IPv4 address
6) no dns-server (mandatory)
address-2 second DNS server IPv4 address
(optional)
Notes:
previous one.
address-2 must be different than
address-1.
Configuring domain name (DHCP domain-name <domain> Domain domain name; 1-255 character
option 15) no domain-name string
Note: Repeating this command replaces the
previous one.

Configuring client hardware address hardware-address <mac-address> MAC address is used for manual binding, i.e.
(MAC address) no hardware-address assigning a preconfigured IP address to a
specific client.
mac-address client MAC address
Notes:
The hardware address can be configured
only if the pool is bound to a host
(configured with the host command).
previous one.
Either client identifier or hardware
address can be configured; not both.
You cannot configure a hardware
address already configured on another
pool.
Configuring client IP address and prefix host <ipv4-address>/<prefix-length> Ipv4-address client IPv4 address
length no host Prefix-length client IP prefix length
Possible values: 1-32
Notes:
If no host is invoked while client
identifier or hardware address is
configured, the device deletes the
configured client identifier or hardware
address.
previous one.
Either the host or network command can
be configured; not both.
The address (while taking into account
the prefix length) must be a unicast
address.
The same pair of address and prefix
length may not be configured on more
than one pool.
The mask (reflecting the prefix length) is
passed to the client in option 1.

Configuring lease default validity time lease-default {time <days> [<hours> Possible values: 60-8640000 seconds (100
(DHCP option 51) [<minutes>]] | infinite} days); infinite (lease never expires, unless
no lease-default the client releases it.)
Notes:
If you configure lease validity time to
between 60 and 8640000 (100 days)
seconds, the server grants it.
If you configure less than 60 seconds,
the server offers 60 seconds.
If you configure more than 8640000
seconds, the server offers 8640000
seconds.
If the client does not send option 51, i.e.
it does not state for how much time it
requires the lease, the server offers the
default lease time (one day, unless
otherwise configured).
previous one.
Configuring NetBIOS name server netbios-name-server <address> address NetBIOS name server IPv4
(DHCP option 44) [<address-2>] address
no netbios-name-server address-2 Second NetBIOS name server
IPv4 address
previous one.
Configuring NetBIOS node type (DHCP netbios-node-type <type> Type NetBIOS node type
option 46) no netbios-node-type Possible values: b, p, m, h
previous one.

Configuring client network IPv4 network <ipv4-address>/<prefix-length> Ipv4-address client IP address

address and mask no network Prefix-length client IP prefix length
Notes:
If the network is deleted or changed in
such a way that the configured ranges
are not in it, the device deletes the
ranges that are out of the newly
configured network.
previous one.
Either the host or network command can
be configured; not both.
The IP address (while taking into account
the prefix length) must be a subnet
address.
length cannot be configured on more
than one pool.
Configure relay agent information relay-information circuit-id <circuit-id> Matching the received option 82 with the
(DHCP option 82) relay-information remote-id <remote-id> configuration determines the clients that
can receive offers of the pool.
no relay-information
Notes:
previous one.
Either circuit-id or remote-id can be
specified, as only one of them can be
matched with received option 82.
Option 82 cannot be matched with a hex
pattern.
The relay agent information option can
be configured only if the pool is bound
to a network.
length cannot be configured on more
than one pool.
Viewing DHCP Server Binding

You can display the DHCP server binding database, which includes all IP addresses
that have already been assigned, lease expiration time and date, and the
hardware addresses of the clients.
To display the DHCP server binding information:

At the config>system>dhcp-server# prompt, enter show binding.
The DHCP server binding information is displayed.

IP Address : 192.168.1.1
Binding State: active
Bound to :
MAC : 11:22:33:44:55:66
ID : 0x01 rad111
Lease Time : 864000 seconds
Expires At : 1949/10/01 01:11:12
Table 6-10. DHCP Server Binding Parameters
Counter Description
IP Address Lease IPv4 address
Binding State Binding state.

Possible values: free, offered, active, expired, released, abandoned,
permanent, bootp, blocked
Bound to MAC Client MAC address

Possible values: MAC address, formatted xx:xx:xx:xx:xx:xx
Bound to ID Client ID
Possible values: Hex string. Readable characters are printed as is; for
non-readable, the hex value is printed preceded by 0x; for example: 0x01
rad111.
Lease Time Lease time in seconds
Expires At Lease expiration date and time, formatted as other date and time
parameters in the device
Viewing DHCP Server Conflict

You can display the DHCP server conflict information, which includes all address
conflicts that have been recorded by the DHCP server, including:
Abandoned addresses addresses that clients have declined (they expire
after a timeout)
Blocked addresses addresses that were in use without the server assigning
them.
To display the DHCP server conflict information:

At the config>system>dhcp-server# prompt, enter show conflict.
The DHCP server conflict information is displayed.
IP Address Expires in
---------------------------
1.1.1.1 -- seconds
100.100.100.100 390 seconds
Table 6-11. DHCP Server Conflict Parameters
Counter Description
IP Address Conflict IPv4 address

Counter Description
Expires in Time (in seconds) remaining before the conflict expires

Possible values:
-- if there is no expiration time, such as for blocked addresses
number if there is an expiration time, such as for abandoned
addresses
Viewing DHCP Server Statistics

You can display the DHCP server statistics.
To display the DHCP server statistics:

At the config>system>dhcp-server# prompt, enter show statistics.
The DHCP server statistics are displayed.
Address Type Total
-------------------
Free 10
Offered 1
Active 100
Expired 2
Released --
Abandoned --
Permanent --
Bootp --
Blocked 1
Table 6-12. DHCP Server Statistics Counters
Counter Description
Free Total number of free addresses
Offered Total number of offered addresses
Active Total number of active addresses
Expired Total number of expired addresses
Released Total number of released addresses
Abandoned Total number of abandoned addresses
Permanent Total number of permanent addresses
Bootp Total number of bootp addresses
Blocked Total number of blocked addresses
The following table lists the messages generated by ETX2i when a configuration
error is detected.

No such address You tried clearing an IPv4 Make sure the address is in the
address that does not exist in database.
the database.
The pool is not bound to You tried to configure a range Bind the pool to a network using the
network of addresses for a pool that network command.
has not been bound to a
network.
You tried to configure the

relay agent information option
for a pool that has not been
bound to a network.
Range is not inside the pools You tried to configure a range Configure a range inside the pools
network that is not in the pools subnet, using the network command.
subnet.
Range is already configured You can only configure a single Delete the existing address range, and
range per pool. You already then configure a new range.
configured a range for the
pool.
Range does not exist You tried to delete an address Delete the exact address range that
range that is not exactly the you configured.
same as the one configured.
The pool is not bound to host You tried to configure a Unbind the pool from the network, and
network while a host is bind it to a host using the host
configured. command.
You tried to configure a client Bind the pool to a host using the host
identifier (option 61) or command.
hardware address (MAC) for a
pool that is not bound to a
host.
Cannot have both client- You configured a client Remove the client identifier or
identifier and hardware-address identifier when a hardware hardware address configuration.
address is already configured,
or vice versa.
Client identifier configured on You tried to configure a client Configure a unique client identifier.
different pool identifier that has already
been configured on another
pool.
Hardware address configured on You tried to configure a Configure a unique hardware address.
different pools. hardware address that has
already been configured on
another pool.

The pool is bound to network You tried configuring a host Unbind the pool from the network.
while pool was bound to a
network.
Invalid address or prefix length You entered a non-unicast Enter a valid unicast address (taking
address. into account the prefix length).
Address and prefix configured You configured the same pair Configure a unique address and prefix
on another pool of address and prefix length length pair.
on another pool.
The pool is bound to host You tried configuring a Unbind the pool from the host.
network while pool was bound
to a host.
Invalid address or prefix length In case of a host: You entered Enter a valid unicast IP address (taking
a non-unicast address. into account the prefix length).
In case of a network: You Enter a valid subnet IP address (while

entered a non-subnet address. taking into account the prefix length).
6.9 NETCONF/YANG Management

NETCONF/YANG, a management interface equivalent to SNMP/MIB, enables the
remote manager to configure and monitor the device.
Network Configuration Protocol (NETCONF) 1.1 a protocol that provides
mechanisms to install, manipulate, and delete the configuration of network
devices. NETCONF carries configuration data and operations as requests and
replies using RPCs encoded in XML over a connection-oriented transport
(SSH).
YANG a data modeling language used to model configuration and state data
manipulated by the NETCONF, NETCONF RPCs, and NETCONF notifications.
Applicable Products
Standards
The supported NETCONF versions are based on the following standards:
RFC 6241 (06/2011), Network Configuration Protocol (NETCONF) 1.1
RFC 6020 (10/2010), YANG 1.0 - A Data Modeling Language for the Network
Configuration Protocol (NETCONF)
ETX2i NETCONF/YANG Management 6-47

Benefits
Based on transactions, NETCONF reduces the burden on the network
management station.
Error recovery and sequencing tasks are removed from the management side.
YANG enables writing automatic scripts on the management side. YANG
models are richer than MIB, in that you can formally specify capability
options, i.e. what is allowed and not allowed on the device. In MIB, you can
only write a description.
Enhanced capabilities, in comparison to SNMP.
NETCONF is a session-based network management protocol that uses XML-
encoded remote procedure calls (RPCs) and configuration data to manage
network devices.
The mandatory transport protocol for NETCONF is SSH. The default TCP port
assigned for this mapping is 830. A NETCONF server implementation listens for
connections to the NETCONF subsystem on this port. Use of a dedicated port
makes it easier for the NETCONF server to identify and filter NETCONF traffic.
The following are characteristics of transactions:
Transactions are indivisible; all-or-nothing.
There is no internal order inside a transaction. It is a set of all-at-once
changes; not a sequence.
Parallel transactions do not interfere with each other; no-crosstalk.
Committed data always-sticks, i.e. it remains in the system even if fail-over,
power failure, restart, or more occurs; done-is-done.
The following deployment model shows the communication between the device
(NETCONF server; equivalent to SNMP agent) and management station (NETCONF
client; equivalent to SNMP manager).
Figure 6-3. NETCONF/YANG Deployment Model
6-48 NETCONF/YANG Management ETX2i

Factory Defaults
The following is the default configuration of NETCONF.
Parameter Description or value
inactivity-timeout time 10 (ten minutes)
no shutdown NETCONF is enabled.
Configuring NETCONF Parameters

To configure NETCONF parameters:
1. Navigate to configure management netconf.
The config>mngmnt>netconf# prompt is displayed.
Defining NETCONF session inactivity inactivity-timeout {time <minutes> | infinite} minutes: 1-60
timeout
Disabling NETCONF [no] shutdown
Examples
To configure NETCONF session inactivity timeout to 15 minutes:
ETX2i>config>mngmnt>netconf# inactivity-timeout time 15
ETX2i>config>mngmnt>netconf#
To configure NETCONF session inactivity timeout to be infinite:

ETX2i>config>mngmnt>netconf# inactivity-timeout infinite
To disable NETCONF:
ETX2i>config>mngmnt>netconf# shutdown
6.10 Point-to-Point Protocol over Ethernet (PPPoE)

The Point-to-Point Protocol (PPP) provides a standard method for transporting
multi-protocol packets over point-to-point links. PPP over Ethernet (PPPoE) is
used to encapsulate PPP packets over Ethernet. It allows ETX2i to connect to a
remote access concentrator to establish a PPPoE session, and then build a PPP
link to the peer at the other end of the PPP link.
Standards
RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)
ETX2i Point-to-Point Protocol over Ethernet (PPPoE) 6-49

RFC 1334 PPP Authentication Protocols

RFC 1661 The Point-to-Point Protocol (PPP)
RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP)
RFC 2516 A Method for Transmitting PPP Over Ethernet (PPPoE)
RFC 5072 IP Version 6 over PPP
Benefits
PPPoE in ETX2i is used to establish a management channel through which an IP
address can be acquired and the unit can be managed. You can connect ETX2i to
a central server for authentication and to acquire an IP address, and establish a
management channel that a remote management system can use to send
software and configuration files and manage ETX2i.
PPPoE consists of the following stages:
Discovery
PPP Session
Discovery
ETX2i locates a remote access concentrator by broadcasting a request to initiate
a PPPoE session. The request can contain a user-configurable service name (sent
as empty string if service name has not been configured). When an access
concentrator answers the request and the PPPoE initiation message sequence is
performed successfully, the PPPoE session can be established.
If ETX2i cannot establish the session due to timeout (after a set number of
retries), or if the session is terminated or rejected by the access concentrator,
ETX2i restarts the session initiation process.
PPP Session
After discovering the access concentrator, ETX2i builds a PPP link with the
remote peer, in the following stages:
Link Control Protocol (LCP) Negotiation
Authentication
Internet Protocol Control Protocol (IPCP) Negotiation
Link Control Protocol (LCP) Negotiation

The LCP negotiation is used to establish with the peer the link encapsulation
options, packet size, error detection, termination options, etc.
If timeout occurs during LCP negotiation (after a set number of retries), or if LCP
negotiation is terminated or rejected, ETX2i restarts the LCP negotiation process.
6-50 Point-to-Point Protocol over Ethernet (PPPoE) ETX2i

Authentication
ETX2i does not attempt to authenticate the PPP peer, but does respond to a
peer that requires authenticating ETX2i.
The following authentication methods are supported (you can specify whether to
refuse a particular method if it is offered by the peer):
Challenge Handshake Authentication Protocol (CHAP) This is the
recommended authentication method if authentication is being performed, as
the username and password are not sent in clear text.
If CHAP authentication is performed, ETX2i receives a challenge from the
peer, and authenticates as follows:
If the user name in the challenge matches a configured user, ETX2i uses
the login-user and its password.
If the user name in the challenge does not match any of the configured
users, ETX2i uses the default CHAP password. If no default CHAP
password has been configured, the CHAP authentication fails.
Password Authentication Protocol (PAP) This authentication method is less
secure, as the username and password are sent in clear text. If the PAP
username and password have not been configured, ETX2i cannot perform
PAP authentication.
No authentication
If authentication should be performed, ETX2i sends an authentication request to
the peer according to the method being performed, and the peer responds
accordingly.
If timeout occurs during authentication, ETX2i retries the authentication. After a
set number of retries, ETX2i terminates the PPPoE session, and then restarts the
session initiation process as described in Discovery.
If the peer rejects the authentication request, ETX2i terminates the PPPoE
session, and then restarts the session initiation process as described in
Discovery.
Internet Protocol Control Protocol (IPCP) Negotiation

Before it can send IP packets over the PPP connection, ETX2i has to negotiate
IPCP with the peer.
If timeout occurs during IPCP negotiation or the negotiation is rejected, ETX2i
retries the negotiation for a set number of retries; if the retries fail, then ETX2i
restarts the IPCP negotiation process. If IPCP negotiation is terminated, ETX2i
restarts the IPCP negotiation process.
Configuring PPPoE and PPP Entities

In order for PPPoE and PPP to function, you configure a PPP port bound to an SVI
port, to bind to a router interface; additionally you configure incoming and
outgoing flows over the SVI port. You can bind one ETX2i router interface to a
PPP port. See Example for a PPPoE configuration example.

Factory Defaults
By default, no PPP port exists. When a PPP port is created, it is configured as
shown below.
Parameter Description or value
name PPP <ppp-port-num>, e.g. PPP 1 for PPP port 1
no refuse-chap Do not refuse CHAP authentication.
refuse-no-auth Refuse skipping authentication.
refuse-pap Refuse PAP authentication.
no service-name Service name is not configured.
Configuring PPP Port

To configure the PPP port:
Navigate to configure port ppp <ppp-port-num> to select the PPP port to
configure.
The config>port>ppp(<ppp-port-num>)# prompt is displayed.
Enter all necessary commands according to the tasks listed below.
Binding PPP port to SVI bind svi <port-number>
Defining host name to send to PPP chap-hostname <name> If the CHAP host name is not configured,
peer if CHAP authentication is used ETX2i identifies itself by its device name
(assigned via the name command in the
system level).
Defining default password for CHAP chap-password <password> [hash] The default CHAP password is used for
authentication authentication if the username in a
received CHAP challenge does not match
any of the defined users.
The hash keyword denotes that the
string is hashed, rather than clear text;
usually it is added by the device after
hashing the clear text that the user
enters, before saving it in the database.
If you enter the password as a text
string, do not use the hash parameter.
Use it only if you are specifying the
password as a hashed value (obtained
by using the info command to display
PPP data).
Defining name of PPP port name <string>
Defining user name and password for pap-username <name> password <password> See above comments about the hash
PAP authentication [hash] parameter.

Specifying whether to refuse CHAP refuse-chap If you do not want ETX2i to use
authentication if it is offered by the CHAP authentication for the PPP
peer session, enter refuse-chap.
If you do want ETX2i to use CHAP
authentication if offered by the peer,
enter no refuse-chap.
Specifying whether to refuse not using refuse-no-auth If you do not want ETX2i to skip
authentication (i.e. whether to refuse authentication for the PPP session,
skipping authentication), if that is enter refuse-no-auth.
offered by the peer If you do want ETX2i to skip
enter no refuse-no-auth.
Specifying whether to refuse PAP refuse-pap If you do not want ETX2i to use PAP
authentication if it is offered by the authentication for the PPP session,
peer enter refuse-pap.
If you do want ETX2i to use PAP
enter no refuse-pap.
Displaying PPP port status show status See Viewing PPP and PPPoE Status.
Entering PPPoE level pppoe
Commands in pppoe level
Defining service name for PPPoE service-name <string> If the service name is configured, ETX2i
session accepts PPPoE offers only if the service
name in the offer matches.
Displaying PPPoE status show status See Viewing PPP and PPPoE Status.
Example
To configure for PPPoE:
Bind to SVI 1, router interface 1.
Authentication CHAP or PAP must be used.
CHAP hostname=ETXCHAP, default password=ppp1
PAP username=ETXPAP, password=ppp1
Incoming flow: Untagged, ingress ETH 6, egress SVI 1
Outgoing flow: Untagged, ingress SVI 1, egress ETH 6
exit all
configure
port
# Configure SVI 1
svi 1
no shutdown
exit
# Configure PPP port

ppp 1
bind svi 1
chap-hostname ETXCHAP
chap-password ppp1
pap-username ETXPAP password ppp1
no refuse-chap
no refuse-pap
refuse-no-auth
exit
exit
flows
# Configure classifier to match untagged packets
classifier-profile untagged match-any
match untagged
exit
# Configure incoming flow
flow ppp_in
classifier untagged
egress-port svi 1
no shutdown
exit
# Configure outgoing flow
flow ppp_out
classifier untagged
ingress-port svi 1
no shutdown
exit
exit
# Configure router interface bound to PPP port
router 1
interface 1
bind ppp 1
ipv6-autoconfig
no shutdown
exit
exit
# Save configuration
save
exit all
Viewing PPP and PPPoE Status

To view the PPP port status:
At the config>port>ppp(<ppp-port-num>)# prompt, type:
show status
The PPP port status is displayed as shown below (based on the
configuration from Example).
ETX2i# configure port ppp 1
ETX2i>config>port>ppp(1)# show status

Name : PPP 1
Router Interface : Router 1/If 1

Physical Port : svi 1
LCP
-----------------------------------------------------------------------------
state : Opened
MRU Local : 1500 Peer : 1500
Authentication
-----------------------------------------------------------------------------
Of Us : CHAP State : Completed Identity : admin
IPCP
-----------------------------------------------------------------------------
State : Opened
Local IPv4 address : 22.22.22.22 Negotiated
Peer IPv4 address : 10.0.0.1
IPV6CP
-----------------------------------------------------------------------------
State : Opened
Local IPv6 address : fe80::d31:494c:56c:71b0 Negotiated
Peer IPv6 address : fe80::8828:1bab:8cf5:2477

Global IPv6 address : 2001:db8::284d:3190:e15a:e814
To view the PPPoE status:

At the config>port>ppp(<ppp-port-num>)>pppoe # prompt, type:
show status
The PPPoE status is displayed as shown below (based on the
configuration from Example).
ETX2i>config>port>ppp(1)# pppoe
ETX2i>config>port>ppp(1)>pppoe# show status
Router Interface : Router 1/If 1
Physical Port : svi 1
State : Up
Service Name Requested :
6.11 SNMP Management

Simple Network Management Protocol (SNMP) is an application layer protocol
that provides a message format for communication between managers and
agents.
ETX2i supports SNMPv3, the latest SNMP version to date. SNMPv3 provides
secure access to devices in the network by using authentication and data
encryption.
ETX2i SNMP Management 6-55

Applicable Products
Standards
The supported SNMP versions are based on the following standards:
RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working Group
RFC 1902, Structure of Management Information for Version 2 of the Simple
RFC 1903, Textual Conventions for Version 2 of the Simple Network
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
RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework. SNMPv2 Working Group
RFC 2104, Keyed Hashing for Message Authentication
RFC 2271, Architecture for Describing SNMP Management Frameworks
RFC 2272, message processing and dispatching for the Simple Network
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
RFC 3412, Version 3 Message Processing and Dispatching
RFC 3414, User-based Security Model for SNMPv3
RFC 3416, Update for RFC 1904
Benefits
SNMP allows you to remotely manage multiple units from a central workstation
using a network management system.
SNMPv3 allows data to be collected securely from SNMP devices. Confidential
information such as SNMP commands can thus be encrypted to prevent
unauthorized parties from being able to access them.
6-56 SNMP Management ETX2i

In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which reports information via SNMP back to the
managing workstations.
Factory Defaults
The following is the default configuration of the SNMP parameters (see
Configuring SNMPv3 Parameters for explanations of the parameters):
SNMP engine ID set to device MAC address
View named internet providing access to IETF MIBs and IEEE MIBs
User named "initial", with security level no authentication and no privacy
Group for SNMPv3 named "initial":
Security levels no authentication and no privacy, authentication and no
privacy, authentication and privacy
User initial
Views for read/write/notify "internet"
Notifications with tag unmasked for the device traps
Configuring SNMPv3 Parameters

SNMP version 3, provides secure SNMP access to the device by authenticating and
encrypting packets transmitted over the network.
The SNMPv3 manager application in RADview-EMS provides a user-friendly GUI
interface to configure SNMPv3 parameters. If you intend to use it, you must first
use the device CLI to create users with the required encryption method and
security level, as the application can create users based only on existing users;
the new user has the same encryption method, and the same security level or
lower. The ETX2i default configuration provides one standard user named
initial with no encryption and the lowest security level (see Factory Defaults for
details).
A Network Management Station (NMS) relies on traps in order to display device
alarms. As traps are not reliable, the NMS needs to be aware which traps got lost
and be able to ask a device to resend them. This mechanism is called trap
synchronization.
NMSs (targets; such as RADview or third party) may be organized into trap sync
groups in order to provide redundancy between these NMSs. You can define the
tags and target parameters in each trap sync group for example, you can define
one trap sync group for critical alarms such as linkDown and coldStart, and
another group for all other traps.
Each trap is sent to all targets attached to the group, and therefore it is
recommended to set identical traps masking for all group members.

Notes ETX2i supports up to two trap synchronization groups.

A single trap synchronization group can support multiple NMS.
If you would like all NMS to receive all traps, there is no need to configure trap
synchronization groups.
Follow this procedure to configure SNMPv3:

1. Set SNMP engine ID if necessary.
2. Add users, specifying authentication protocol and privacy protocol.
3. Add groups, specifying security level, protocol, and views.
4. Connect users to groups.
5. Add notification entries with assigned traps and tags.
6. Configure target parameter sets to be used for targets.
7. Configure targets (SNMPv3 network management stations to which ETX2i
should send trap notifications), specifying target parameter sets, notification
tags, and trap synchronization groups if applicable.
To configure SNMPv3 parameters:
Note When you enter password parameters, they should contain at least eight
characters.
Configuring access-group <group-name> { snmpv2c | usm } snmp Using no access-group

group { no-auth-no-priv | auth-no-priv | auth-priv } deletes the group.
Defining how to context-match {exact | prefix} snmp>access-group exact Match the

match the entire context.
context sent in prefix Match the first
frames by the part of the context.
NMS
Note: ETX2i
automatically identifies
the NMS context,
therefore you can
configure exact match.
Normally prefix is used
for devices with
multiple instances.
Setting view for notify-view <name> snmp>access-group See the description of

traps the view command for
information on how to
Setting view read-view <name> snmp>access-group
limit the parts of the
with read-only
access

Setting view write-view <name> snmp>access-group MIB hierarchy that the

with write view can access.
access
Administratively no shutdown snmp>access-group Using shutdown

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

community
Configuring name <community-string> snmp>community

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

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

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

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

notification
Assigning trap bind <trap-name> snmp>notify You can assign more

to notification than one trap to a
notification, in
separate commands.
Assigning tag to tag <tag-value> snmp>notify

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

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

notification filter
filter to define sub-tree-oid OID
access to a that defines the MIB
particular part subtree
of the MIB
hierarchy for
trap variables

Specifying the mask [<mask>] snmp>notify-filter The mask is comprised

specify a mask if
Defining type {included | excluded} snmp>notify-filter included Traps

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

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

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

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

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

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

Specifying group-name <group-name> snmp>security-to-group

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

enabling disables the
security-to-grou security-to-group
p entity entity.
Setting SNMP snmp-engine-id mac [ <mac-address> ] snmp If you use the mac
engine ID, as snmp-engine-id ipv4 [ <ip-address> ] option and dont
MAC address or specify the MAC
snmp-engine-id text <string>
IP address or address, the SNMP
string engine ID is set to the
device MAC address.
If you use the ipv4
option and dont
specify the IP address,
the SNMP engine ID is
set to the device IP
address.
Configuring target <target-name> snmp Using no target

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

target address address oam-domain <oam-port>
as IP address or
OAM port
Assigning tag(s) tag-list <tag> snmp>target If you specify more

to target (the tag-list [ <tag> ] than one tag, you must
tag(s) must be enclose the list in
tag-list [ <tag1> <tag2><tagn> ]
defined in quotes; however, if you
notification are specifying just one
entries) tag, the quotes are
optional.
Specifying set target-params <params-name> snmp>target

of target
parameters for
target

Specifying the trap-sync-group <group-id> snmp>target If the group does

trap not exist, it is
synchronization created.
group to be Enter no
associated with trap-sync-group
the SNMP <group-id> to
target (NMS) remove the
manager (NMS)
from the group. If
the removed
manager was the
last to be
associated with the
trap-sync-group,
the group is
automatically
deleted.
ETX2i supports up
to two trap
synchronization
groups.

enabling target disables the target.
Configuring set target-params <target-param-name> snmp Using no target-params

of target removes target
parameters, to parameters.
be assigned to
target
Specifying message-processing-model { snmpv2c | snmpv3 } snmp>target

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

on whose [ level { no-auth-no-priv | auth-no-priv | auth-priv } ]
behalf SNMP
messages are
to be generated
for the set of
target
parameters

Specifying version { snmpv2c | usm } snmp>target Use usm for SNMPv3

SNMP version to version.
be used when
generating
SNMP messages
for the set of
target
parameters

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

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

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

of target target parameters,
parameters in enter: no
trap-sync-group target-params
<params-name>.
Configuring user user <security-name> snmp If you dont specify the

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

authentication [ key <key-change> ] no authentication
password and disables the
optional key for authentication
changes protocol.

Setting user privacy [ password <password> ] [ key <key-change> ] snmp>user Using no privacy
privacy disables privacy
password and protocol
optional key for Note: Password
changes minimum length is 10
for AES128 and 8 for
DES.
Administratively no shutdown snmp>user You must define the

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

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

specify a mask if
Defining type {included | excluded} snmp>view included Allow access

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

enabling view

Displaying trap show trap-sync snmp

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

SNMPv3
information,
such as the
number of
times the
SNMPv3 engine
has booted, and
how long since
the last boot
Examples
To create an SNMPv3 user and connect it to group:
User named MD5_priv:
Security level MD5 authentication, DES privacy
Group named "MD5Group":
All security levels
Contains set of views named "internet" (from default configuration)
exit all
#********* Configure user MD5_priv with authentication method MD5 with DES privacy protocol
user MD5_priv md5-auth des
privacy password MD654321
authentication password MD654321
no shutdown
exit
#******** Configure access group MD5Group with various authentication and privacy options
access-group MD5Group usm no-auth-no-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit
access-group MD5Group usm auth-no-priv
context-match exact
read-view internet
write-view internet
no shutdown
exit

access-group MD5Group usm auth-priv

context-match exact
read-view internet
write-view internet
no shutdown
exit
#******** Connect user MD5_priv to group MD5Group

security-to-group usm sec-name MD5_priv
group-name MD5Group
no shutdown
exit all
save
To create notifications:
Notification named TrapPort:
Tag=Port
Bound to ethLos, sfpRemoved
Notification named TrapPower:
Tag=Power
Bound to powerDeliveryFailure, systemDeviceStartup
exit all
#******** Configure notification TrapPort
notify TrapPort
tag Port
bind ethLos
bind sfpRemoved
no shutdown
exit
#******** Configure notification TrapPower

notify TrapPower
tag Power
bind powerDeliveryFailure
bind systemDeviceStartup
no shutdown
exit all
save
To create target parameters and target:

Target parameters named TargParam1:
version USM
User MD5_priv
Security level authentication and privacy
Target named TargNMS1:
Target parameters TargParam1

Tag list=Port, Power

exit all
#******** Configure target parameters TargParam1
version usm
security name MD5_priv level auth-priv
no shutdown
exit
#******** Configure target TargNMS1

target TargNMS1
tag-list port power
no shutdown
exit
To create communities, target parameters, and target for network devices that
are working with SNMPv1:
Community read:
Name: public
Security name: v1_read (defined in default configuration)
Community write:
Name: private
Security name: v1_write (defined in default configuration)
Community trap:
Name: public
Security name: v1_trap (defined in default configuration)
Target parameters named snv1:
Version SNMPv1
Security name: v1_trap
Security level: no authentication and no privacy
Target named NMSsnmpv1:
Target parameters snv1
Tag list=unmasked
exit all
#******** Configure communities
snmpv3
community read
name public
sec-name v1_read

no shutdown
exit
community write
name private
sec-name v1_write
no shutdown
exit
community trap
name public
sec-name v1_trap
no shutdown
exit
#******** Configure target parameters

target-params snv1
version snmpv1
security name v1_trap level no-auth-no-priv
no shutdown
exit
#******** Configure target

target NMSsnmpv1
target-params snv1
tag-list unmasked
no shutdown
exit all
save
To display SNMPv3 information:

ETX2i# configure management snmp
ETX2i> config>mngmnt>snmp# show snmpv3 information
SNMPv3 : enable
Boots : 2
Boots Time (sec) : 102
EngineID : 800000a4030020d2202416
To configure trap synchronization:

Target parameters TargParam1 (from previous example)
Tag list=Port, Power (from previous example)
exit all
#******** Configure targets and trap synchronization group
target NMS1
trap-sync-group 1
exit

target NMS2
trap-sync-group 1
exit
target NMS3
trap-sync-group 2
exit
target NMS4
trap-sync-group 2
exit
trap-sync-group 1
tag-list port power
exit all
save
To display trap synchronization configured in above example:

ETX2i>config>mngmnt>snmp# show trap-sync
Group ID Member
---------------------------------------------------------------
1 NMS1
1 NMS2
2 NMS3
2 NMS4
6.12 User Access

ETX2i management software allows you to define new users, and their
management and access rights.
Applicable Products
Factory Defaults
By default, the following users exist, with default password 1234:
su
oper
tech
user
The default users cannot be deleted, but can be disabled (shut down).
ETX2i supports the following four user access levels:
ETX2i User Access 6-69

Superuser (su) can perform all the activities supported by the system,
including creating new users, changing its and other user access levels and
passwords, deleting and disabling other users.
Operator (oper) can perform all the activities, except for defining, deleting or
disabling other users.
Technician (tech) can monitor the device (info, show status, show statistics).
User (user) can monitor the device (info, show status, show statistics).
The regular users (oper, tech, user) cannot define, delete or disable other users,
or change their own access levels. They are allowed to change their current
passwords. All users can view all CLI levels.
Password Hashing
You can specify a 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.
SSH Authentication
In addition to password, ETX2i can be configured to use more robust and secure
public key user authentication method for SSH sessions.
Configuring Users
To add a new user:
1. Verify that you are logged on as superuser (su).
2. Navigate to the management context (config>mngmnt).
3. Enter login-user, followed by a new user name if you intend to create a new
user, or an existing name, if you intend to change previously defined user.
Note Maximum user name length is 20 characters.
4. The prompt changes to config>mngmnt>login-user<user-name>#.

5. Enter the necessary commands according to the tasks listed in the table
below.
To delete an existing user:

1. Verify that you are logged on as superuser (su).
6-70 User Access ETX2i

2. Navigate to the management context (config>mngmnt).

3. Enter no login-user, followed by the name of the user that you intend to
delete.
Specifying user authentication-method The default user authentication method is

authentication method {password | public-key} password
If you change the authentication method of a
user with access level su to public key, and no
public key has been defined, you are warned
that the super user is going to be disabled,
and prompted to confirm the operation.
Defining a user access level { su | oper | tech | user }

level
Specifying user password password <password> [hash] Maximum password length is as follows:
Non-hashed 20 characters
Hashed 40 characters
The use of hash function is illustrated in the
example below.
Setting user public key for public-key <public-key> no public-key deletes the public key.
authentication Public key configuration is relevant only for the
public key authentication method.
Use the Base64 encoding (ASCII A to Z, a
to z, 0 to 9, +, / and space) for the
public key configuration.
Set the key string using the following format:
Begin and end with
Include: ssh-rsa, space, public key string,
space, comment
Enabling/disabling a user shutdown Default users (su, oper, tech, user) can be
no shutdown disabled, but cannot be deleted.
Example Defining Users
To define a new user:

User name staff
Access level su
Password 1234
exit all
configure management
login-user staff
level su
password 1234
no shutdown
exit

To add a new user with a hashed password:

1. Define a new user with a text password.
2. Use info detail to display the password hash value.
3. Define another user with the hashed password from the info detail
output.
The second user can log in with the text password defined in step 1.
For example, to add the following users:
User name staff1
User password 4222
User name staff2
User password hash of 4222 (user staff2 can log in with password 4222)
exit all
login-user staff1
level su
password 4222
no shutdown
exit
exit all
configure management login-user staff1 info detail
level su
password "3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
no shutdown
exit all
login-user staff2
level su
no shutdown
exit
exit all
configure management login-user staff2 info detail
level su
no shutdown
To delete an existing user:

At the config>mngmnt# prompt, enter no login-user <user_name>.
The specified user is deleted.
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

ETX2i>config>mngmnt# show users
Num User Access Level Source IP Address
-----------------------------------------------------------------------------
1. su Su Terminal 0.0.0.0
2. su Su Netconf 172.17.160.69
Viewing User Information

The details of the currently logged-in users are available in the show users-details
screen.
The screen for show users-details provides the following information:
User User name
Level User access level
Popup Alarm/event popup status (enabled or disabled)
From Source IP address of the management session, followed by

protocol type (serial, Telnet, SSH, NETCONF)
For (sec) Duration of the current management session in seconds
Connected To Destination IP/ protocol type of the active client Telnet

session (to a remote device)
For (sec) Duration of the active client Telnet session (to a remote
device) in seconds
To display the user information:

In the configure>management# prompt, enter show users-details.
ETX2i>config>mngmnt# show users-details
From:1.1.1.1/SSH For(sec):120
User:123456 Level:oper Popup:Disabled
From:100.100.100.100/Telnet For(sec):120
Connected To:1111:2222:3333:4444:5555:6666:7777:8888/Telnet For(sec):100
User:su Level:su Popup:Enabled
From:Serial For(sec):94
User:su Level:su Popup:Enabled
From:172.17.160.69/Netconf For(sec):77
Viewing SSH Server Information

You can display the fingerprint of the SSH server public key.
To display the SSH server information:

At the config>mngmnt# prompt, enter show ssh-server fingerprint.
The SSH fingerprint information stored on the SSH server is displayed.


ETX2i>config>mngmnt# show ssh-server fingerprint
RSA key fingerprint is ef:ab:28:81:53:c2:a3:8d:77:0d:06:e7:89:2b:81:9c

Chapter 7
Resiliency and
Optimization
This chapter describes features related to resiliency and optimization:
Ethernet Linear Protection
Ethernet Ring Protection (ERP)
Fault Propagation
Link Aggregation
Link Protection
7.1 Ethernet Linear Protection

ETX-2i provides bidirectional and unidirectional protection switching for network
ports per ITU-T G.8031, optionally using APS protocol.
The triggers are:
Port signal loss
CCM LOC, RDI, or interface status TLV indicating interface down
ETH-AIS
The protection time is as follows:
One EVC pair 50ms protection
Four EVC pairs 200ms protection
Applicable Products
This feature is applicable to all ETX-2i products, with the following conditions:
PCS port is relevant to ETX2i with an SHDSL or VDSL2 module.
Standards
ITU-T G.8031
ETX-2i Ethernet Linear Protection 7-1

Chapter 7 Resiliency and Optimization Installation and Operation Manual
Benefits
The Ethernet linear protection provides a way to protect the flows belonging to
an EVC.
The protection is based on an EVC Termination Point (ETP). An ETP has one
subscriber port and one or more transport ports. Multiple transport ports are
used for protection only. There are two kinds of flows connected to the ETP
ports, subscriber flows and transport flows.
Subscriber flows run between UNIs and ETP subscriber port. You can define
classification and policing on subscriber flows, as well as marking.
Transport flows run between ETP transport ports and NNIs. You can define
actions such as push, pop, and marking on transport flows.
Note You can define transport flows between ETP transport ports and logical MAC
ports corresponding to MiRICi-155 smart SFPs.
Flows entering the ETP assign an internal CoS value to every frame using mapping
profiles (priority-to-CoS) or by setting fixed CoS values.
Flows exiting the ETP perform queuing based on the internal CoS value using
mapping profiles (CoS-to-queue).
ETP Flow Attributes

The following table shows which attributes you can configure for ETP flows.
Table 7-1. ETP Flow Attributes
Attribute Subscriber Subscriber Transport Transport

(UNI to ETP) (ETP to UNI) (NNI to ETP) (ETP to NNI)
Ingress port Required Required Required Required
Egress port Required Required Required Required
Classifier profile Required, with any type of Required, with Required, with Required, with
criteria criteria: criteria: criteria:
Unclassified or SP VLAN Unclassified
VLAN
Policer profile Optional Optional Not allowed Not allowed
Queue / block Not allowed Required, with Not allowed Required, with
queue mapping queue mapping
profile classified by profile classified
CoS by CoS
CoS Required, with CoS Not allowed Required, with Not allowed
mapping profile CoS mapping
profile
VLAN tag (push) Optional Not allowed Not allowed
7-2 Ethernet Linear Protection ETX-2i

Installation and Operation Manual Chapter 7 Resiliency and Optimization
Attribute Subscriber Subscriber Transport Transport

(UNI to ETP) (ETP to UNI) (NNI to ETP) (ETP to NNI)
Mark Required, with marking Required, with CoS For at least one For at least one of
profile classified by CoS mapping profile of the actions, the actions,
CoS mapping marking profile
profile classified by CoS
VLAN tag (pop) Not allowed Optional Not allowed
Drop Optional Optional Optional Optional
EVC Protection Switching

EVC protection (1:1) is based on the ETP model. One of the transport ports is the
working transport entity and the other port serves as the protection transport
entity.
Monitoring both working and protection transport entity is done via MEPs
exchanging CCMs. In addition, the protection transport optionally runs APS
protocol.
When working without APS, switchover is affected by local events only (signal
failure trigger, switch back to port after failure ends, manual switchover due to
command). In one-to-one bidirectional mode, upon switchover both the EVC Rx
and Tx flows move to the second path.
Master and Slave ETPs

You can define one master ETP and several slave ETPs. The master ETP must have
all the configuration of the protection, same as single ETP. The slave ETPs point
to the master ETP via master command and bind each port ID to
working/protection.
The master ETP index MUST be lower than the index of the slave ETPs. You must
create the master ETP before creating the slave ETPs.
Management over ETP

ETX-2i can be managed via a router interface connected to the ETP subscriber
port.
EVC and OAM

On each transport entity you must define a MEP to use as the signal failure
trigger if working in APS mode, in order to monitor the connection using CCM.
The MEPs must be activated so that the protection switching mechanism can
monitor both working and protection transport entities. The monitoring is
accomplished by exchanging CCMs as defined in ITU-T Rec. Y.1731. In non-APS
mode, the signal failure trigger can be a MEP or port status.
In addition, the MEP can be defined to perform other Y.1731 services such as
measuring delay and loss on the specific EVC. If an Up MEP associated with the
transport is associated with an untagged classifier profile, services can still be
defined for it; the Up MEP is transparent to the CVLAN, and the OAM transmitted
from the ETP transport ports can be edited according to the SVLAN.

EVC Fault Propagation

You can define fault propagation based on EVC failure detection (ETP operation
status) to shut down the UNIs that connect to it. The fault trigger can be one of
the following:
In case of protection the signal failure trigger MEP for ETP transport ports
In other cases the NNI operation status
EVC Loopback
A loopback can be activated on any of the transport ports toward the network
and on the subscriber port toward the user or network.
In most cases you would activate a loop on the subscriber port toward the
network, thus you can loop the EVC traffic without affecting protection.
If you wish to run a loop on a specific EVC path when you activate the loop on
the transport ports, you have two options:
Loopback on a transport port affects OAM, as any traffic EVC path
redundancy is triggered if present.
Loopback only data without affecting redundancy.
Factory Defaults
By default, no ETPs are configured.
When you create an ETP port, by default it is configured as follows:
Name = ETP <etp-name> Subscriber Port <port-index> or
ETP <etp-name> Transport Port <port-index>, according to whether port is
subscriber or transport
Administratively enabled
When you first enter the ETP protection level, by default the protection is
configured as follows:
ETX-2i#configure etps etp ETP1 protection
ETX-2i>config>etps>etp(ETP1)>protection$ info detail
shutdown
no master-etp
mode bi-directional-1-to-1
no aps-protocol
revertive
wait-to-restore 300
ETX-2i>config>etps>etp(ETP1)>protection$
Configuring ETPs
This section describes how to configure ETPs.
To configure ETPs:
1. Navigate to configure etps etp <name> to select the ETP to configure.

The ETP is created if it does not already exist, and the

config>etps>etp(<name>)# prompt is displayed.
Configuring ETP port port {subscriber | transport} <port-id> Use the no form to remove the port.
The port-id range is 12.
See the procedure below for more
information on configuring ETP ports.
Configuring ETP protection protection See Configuring ETP Protection for more
information.
Displaying ETP status show status
Displaying ETP statistics show statistics running
Displaying flows show flows-summary

corresponding to ETP
Clearing ETP statistics clear-statistics
To configure ETP ports:

1. Navigate to configure etps etp <name> to select the ETP to configure.
The config>etps>etp(<name>)# prompt is displayed.
2. Type the following command to configure a port, where port-index can be 1
for subscriber ports, or 12 for transport ports:
port {subscriber | transport} <port-index>
The prompt is displayed according to whether you typed subscriber or
transport:
config>etps>etp(<name>)>port(subscriber/<port-index>)#
config>etps>etp(<name>)>port(transport/<port-index>)#
Activating loopback loopback [local | remote] [duration <seconds>]
Assigning name to ETP port name <string>
Displaying loopback status show loopback
Administratively enabling no shutdown Using shutdown disables the port.

ETP port Note: When the port is created, it is
enabled by default.
Configuring ETP Protection

To configure ETP protection, you define the working and protection ports, as well
as other protection parameters.

To configure ETP protection:

1. Navigate to configure etps etp <name> protection to configure protection for
the selected ETP.
The config>etps>etp(<name>)>protection# prompt is displayed.
Defining APS protocol for ETP aps-protocol
Defining transport port ID for bind {protection | working} transport

protection or working port <protection-port>
Clearing the active near end clear

lockout of Protection, Forced
Switch, Manual Switch, WTR
state, or Exercise command
Forcing normal traffic signal to force-switch

be selected from the
protection transport entity,
meaning jump to next port
even if it is down
Preventing a working signal lockout

from being selected from the
protection transport entity,
effectively disabling the
protection group
Forcing normal traffic signal to manual-switch

be selected from the
protection transport entity in
the absence of failure of
working or protection transport
entity, meaning jump to next
port only if it is not down
Defining master ETP master-etp <etp-name>
Configuring protection mode mode {uni-directional-1-plus-1 | uni-directional-1-plus-1 provides 1:1

bi-directional-1-plus-1 | bi-directional-1-to-1} unidirectional protection
bi-directional-1-plus-1 not supported
bi-directional-1-to-1 provides 1:1
bidirectional protection
Indicating if mode is revertive revertive

Defining signal failure trigger sf-trigger { protection | working } port You can use MEPs from flows other
ethernet [<slot>/]<port-index> than the ETP transport flows.
sf-trigger { protection | working } port
logical-mac <port-number>
sf-trigger { protection | working } mep
<md-id> <ma-id> <mep-id>
sf-trigger { protection | working } port pcs
<port-number>
Defining time between wait-to-restore <seconds>

recovery and resumption of
transmission
Displaying protection status show status
Administratively enabling ETP shutdown

protection
Examples
To configure an ETP:
Name = ETP1
Port members = subscriber 1, transport 1, transport 2
exit all
configure etps etp ETP1
port subscriber 1
exit
port transport 1
exit
port transport 2
exit all
To configure ETP protection:

ETP name = ETP1, port members = subscriber 1, transport 1, transport2
Protection mode = bidirectional 1:1
APS protocol used for protection
Working port = transport 1
Protection port = transport 2
Signal failure triggers = working MEP: MD 3 MA 2 MEP 1, protection MEP:
MD 4 MA 2 MEP 1
Note The MEPs must be active.
Revertive mode
Time to wait before restoring transmission = 300 seconds
exit all

configure etps etp ETP1 protection

mode bi-directional-1-to-1
aps-protocol
bind working transport 1
bind protection transport 2
sf-trigger working mep 3 2 1
sf-trigger protection mep 4 2 1
revertive
wait-to-restore 300
no shutdown
exit all
7.2 Ethernet Ring Protection (ERP)

A G.8032 Layer-2 Ethernet ring is a logical ring that protects against link and
node failures. ETX-2i supports multiple rings (up to eight; including sub-rings)
over a single bridge.
Applicable Products
ETX2i and ETX-2i-B support up to six ring instances on the same port.
ETX-2i-10G supports up to eight ring instances on the same port.
Standards
ITU-T G.8032v2, Y.1731
Benefits
G.8032 rings provide sub 50 ms protection for Ethernet traffic.
Ethernet Ring Protection (ERP) technology provides a scalable solution for
low-cost traffic protection and rapid service restoration, with SDH/SONET-type
resilience. It is built on traditional Ethernet MAC (IEEE 802.3) and bridging (IEEE
802.1) functionality. It is independent of any physical layer technologies and can
be utilized in any carrier network.
A ring can be configured on network or user ports. If a ring is configured, LAG or
protection on the network ports is not allowed.
7-8 Ethernet Ring Protection (ERP) ETX-2i

Note Rings are color-aware via the setting of the DEI bit:
Set to 0 maps to green
Set to 1 maps to yellow
No additional configuration is needed for the color-aware functionality.
You can also define the color-aware functionality of the ring by associating the
ring with a predefined color mapping profile (see Color Mapping).This is an
alternative method to using the DEI bit setting.
Ring Topology
ETX-2i supports the following topologies:
Multi-ring
Figure 7-1. Multi-Ring
Major ring with multiple sub-rings
Figure 7-2. Major Ring with Multiple Sub-rings
Multiple rings with a common link are usually referred to as ladder network (see
Figure 7-3).
The following terms are commonly used for describing ladder ring topology:
Interconnection nodes ring nodes that are common to both interconnected
rings (nodes C and G in Figure 7-3)
Major ring an Ethernet ring that controls a full physical ring and is
connected to the interconnection nodes on two ports (ring A-H-G-C-B in
Figure 7-3)
Sub-ring an Ethernet ring that is connected to a major ring at the
interconnection nodes. By itself, the sub-ring does not constitute a closed
physical ring. A sub-ring is connected to the interconnection nodes on only
one port (ring C-D-E-F-G in Figure 7-3). Link CG is not a part of the sub-ring;
ETX-2i Ethernet Ring Protection (ERP) 7-9

it is controlled by the major ring.

G.8032 supports two operation modes of sub-rings:
Sub-ring with an R-APS virtual channel A virtual R-APS channel
connection is established between two interconnection nodes of the sub-
ring over a network or other ring, to tunnel R-APS messages. In this
mode, R-APS of the sub-ring is configured as a data VLAN in the Major
ring.
Sub-ring without an R-APS virtual channel The R-APS channel is
terminated at the interconnection nodes and its R-APS messages are not
tunnelled between the interconnection nodes. In this mode, R-APS of the
sub-ring is not configured as a data VLAN in the Major ring.
H G F
Virtual Channel
A Major Ring Sub-Ring E
B C D
Figure 7-3. Physical Ladder Topology for Sub-Ring with R-APS Virtual Channel
Note Sub-rings without R-APS virtual channel do not have a Virtual Channel between G
and C.
H G G F
A Major Ring Sub-Ring E
B C C D
Figure 7-4. Major Ring and Sub-Ring
In ladder networks, a common VLAN is shared on more than one physical ring. For
example, in Figure 7-3, a user connected to node E communicates with a user
connected to node A over the same VLAN. Ring topology includes a physical link
between nodes G and C. It belongs to the major ring and is used by the sub-ring
as its R-APS channel. Note that a sub-ring without a virtual channel would not
have an R-APS virtual channel between nodes G and C.

Ring Protection Links

An Ethernet ring consists of multiple Ethernet nodes, each connected to adjacent
Ethernet nodes using two independent ring links. In order to prevent loops, the
ring uses a specific link to protect the ring, designated as the Ring Protection Link
(RPL). When there are no failures in the ring, the RPL is blocked. When a failure is
detected, the RPL is unblocked.
R-APS Control Messages

Nodes on the ring use Ring Automatic Protection Switching (R-APS) messages to
coordinate ring protection switching. R-APS messages are transmitted over a
VLAN designated as the R-APS VLAN.
ETX-2i supports the configuration of a Ring ID parameter per ring instance (both
major and sub). The configured Ring ID parameter is used as the suffix of the
R-APS DA MAC address, so that R-APS messages are sent to 01-19-A7-00-00-
<Ring ID>. For example, if you configure Ring ID of ring 3 as 03, R-APS messages
will be sent to 01-19-A7-00-00-03.
Note A single R-APS session is supported per VLAN.
Multiple Ring Instances on a Single Port

ETX-2i with Virtual Ring support enables multiple ring instances to reside over the
same physical port, allowing better bandwidth utilization of the ring in Idle state.
, ETX203AM, ETX205A four ring instances per physical port
ETX-2i-10G eight ring instances per physical port
ETX2i, ETX-2i-B six ring instances per physical port
Each ring instance resides on a different set of bridge ports, and supports R-APS
on a different VLAN.
It is not possible to allocate the same VLANs to ring instances residing on the
same physical port; this results in a sanity error.
The same MEP can be used as an sf-trigger to multiple rings residing on the same
physical link.
Figure 7-5. Multiple Rings on Single Physical Port

Passthrough VLANs
Passthrough VLANs over the ring are those VLANs that are not added/dropped to
the ring at the local ring node (ETX), but only traverse via the ring node (East to
West or vice versa).
By default, added/dropped VLANs at the local ring node, as well as passthrough
VLANs, must be configured as data VLANs, and each one is assigned a bridge
broadcast domain (device resource).
ETX-2i ring configuration supports a passthrough attribute, which automatically
assigns a ring/bridge bypass (East to West, West to East) for all passthrough
traffic (i.e. all traffic other than the local added/dropped VLANs that are
configured as data VLANs and use bridge broadcast domains). Passthrough traffic
can be configured for either the full VLAN range other than the VLANs defined as
data VLANs, or for a specific range of VLANs (again excluding the in-range
added/dropped VLANs configured as data VLANs).
As they do not go through the bridge and use its resources, ETX-2i allows an
unlimited number of passthrough VLANS to enter the ring, and does not require
configuring them as data VLANs. Added/dropped VLANs at the local ring node still
need to be configured as data VLANs. The number of added/dropped VLANs is
limited, because they go through the bridge and use up its resources (bridge
broadcast domains).
Use of passthrough VLANs upscales the ring capacity an unlimited number of
passthrough services can travel through the ring; there is only a limit to the
number of ring services added/dropped at the local ring node (maximum number
of broadcast domains per local node). Without using the passthrough attribute,
the maximum broadcast domain supported in a single local node limits the
number of VLANs at the entire ring to this number.
Protection Switching Functionality

In idle state, traffic flows over all the ring links except the RPL. The RPL is
controlled by a node called the RPL owner, which blocks the RPL when in idle
state, in order to to prevent loops. Each link is monitored by its two adjacent
nodes (east and west ports) using standard ETH CC OAM messages per Y.1731
(optional), or port physical status.
When a node detects link failure, it transmits an R-APS Signal Fail (SF) message
periodically, until link recovery is detected. Upon receiving the R-APS (SF), the RPL
owner unblocks the RPL port.
When a node detects link recovery, it sends R-APS No Request (NR) periodically
until R-APS No Request, RPL Blocked (NR, RB) is received from the RPL owner.
R-APS (NR, RB) is sent by the RPL owner to indicate that the ring has no failure
and the RPL has been blocked. Nodes receiving R-APS (NR, RB) flush their MAC
learning table, unblock their ports, and return to idle state.
After link recovery is detected, the adjacent nodes (to the initial failure) start to
send R-APS with (NR,NB). When these packets get to the RPL owner, it starts a
WTR (Wait To Restore) timer. If during the predefined value of this timer, no
additional link failure is detected, the RPL Owner starts to send R-APS with
(NR,RB) (RB = RPL Blocked) and blocks the RPL. Nodes receiving R APS (NR, RB)
flush their MAC learning table, unblock their ports, and return to idle state.

ERP Timers
The following timers are used in ERP operation:
Wait to Restore Period of time used by RPL owner to verify that the ring
(WTR) has stabilized before blocking the RPL after signal recovery.
Non-configurable; permanently set to 300 seconds.
Guard Period of time during which all received R-APS messages

are ignored by the ERP mechanism. This prevents the ring
nodes from receiving outdated R-APS messages.
Holdoff Period of time during which the Ethernet layer does not
report link faults to the ERP mechanism. This filters out
intermittent link faults.
Ring Commands
In addition to failure detection, protection switching can be initiated by the
following commands:
Force switch Forcefully blocks a particular ring port. It can be issued

even if an SF condition exists on the ring, with multiple
force switch commands allowed in the ring.
Manual switch Manually blocks a particular ring port. It can be overridden

by SF condition or a force switch command. Only one
manual switch command is allowed in the ring.
Clear Clears all existing force and manual switch commands in

the ERP.
Color Mapping
ETX-2i supports color mapping configuration at ring nodes, in order to manage
ring QoS.
A ring can be configured with color mapping, according to either of the following
methods:
DEI the default; DEI value is not configurable; its default color aware
functionality is as follows:
DEI = 0 maps to green.
DEI = 1 maps to yellow.
Color mapping profile associating ring with a predefined color mapping
profile (p-bit to color). See Color Mapping Profiles section on how to define a
color mapping profile.
By default, a ring is configured with DEI color mapping.
CoS Mapping
ETX-2i supports CoS mapping configuration at ring nodes, in order to manage ring
QoS.

By default, the ring is associated with a default one-to-one p-bit to CoS profile,
where CoS 0 maps to the highest p-bit 7.
Figure 7-6. Default P-bit to CoS Profile
You can associate a predefined CoS mapping profile to the ring. Refer to CoS
Mapping Profiles section on how to define a CoS mapping profile.
Factory Defaults
By default, there is no Ethernet protection ring created in the ETX-2i system.
When the ring is created, it has the following default configuration.
backward-compatibility no backward-compatibility Backward compatibility to G.8032v1
bridge 0
color-mapping dei
cos-mapping no-cos-mapping Associates the ring with the default one-to-

one p-bit to CoS profile, where CoS 0 maps
to the highest p-bit 7
east-port 0
interconnection-node no interconnection-node
passthrough-vlan no passthrough vlan Default is No Passthrough VLAN mode, i.e.

added/dropped VLANs at the local ring node,
as well as passthrough VLANs, must be
configured as data VLANs, and each one is
assigned a bridge broadcast domain (device
resource).
port-type east node-port

west node-port
r-aps vlan 0 vlan-priority 0 mel 255
shutdown shutdown
timers guard 500 holdoff 0 wtr 300

west-port 0
Configuring Ethernet Ring Protection

The ring configuration sequence is as follows:
1. Configure the bridge (see Configuring the Bridge).
2. Configure the ring.
3. Configure flows (see Configuring Flows).
4. Configure the router (see Configuring the Router).
To configure ERP:
1. At the config>protection# prompt, enter:
erp <ring-number> [{major | sub}]
An ERP instance of the specified type is created if it does not already
exist, and the config>protection>erp(<ring-number>)# prompt is
displayed.
Making the ring compatible with backward-compatibility

previous ERP implementations no backward-compatibility
Assigning ring to bridge bridge 1
Clearing any existing clear

force-switch or manual-switch
command
Clearing ERP statistics clear-statistics [{east | west}]
Defining color mapping type for color-mapping {dei | profile <profile- Packet at ring ingress and at any
ring name>} node mapped to color according
to one of the following:
dei DEI (default)
profile predefined p-bit color
mapping profile (p-bit to color);
string 1-32 characters
Associating CoS profile with ring cos-mapping profile <cos-mapping- profile predefined p-bit color
profile-name> mapping profile (p-bit to color);
no cos-mapping string 1-32 characters
no cos-mapping associates the
ring with a default one-to-one
p-bit to CoS profile, where CoS 0
maps to the highest p-bit.
Defining description text for ring description <string>

Defining the east port of a ring east-port <bridge-port-number>

node ethernet [<slot>/]<port-index>
east-port <bridge-port-number>
east-port <bridge-port-number>
pcs <port-number>
Blocking the east or west port of force-switch {east | west} The force switch can be applied
a ring node, regardless of any to any number of nodes in the
failure conditions ring.
Defining ERP node as an interconnection-node

interconnection node, sharing
more than one ring
Blocking the east or west port of manual-switch {east | west} The manual switch command can
a ring node manually be applied to a single ring node
only.
Defining description text for port port-description {east | west} <string>
Defining ring port type port-type { east | west } { node-port | node-port Port is not
rpl | neighbor | next-neighbor } connected to RPL.
rpl Port is designated as RPL.
neighbor Port is directly
connected to RPL owner.
next-neighbor Port is
connected to RPL owner via
neighbor.
Configuring dedicated VLAN for r-aps [vlan <vlan-id>] Range for vlan-id: 14094
R-APS messages [vlan-priority <vlan-priority>] Range for vlan-priority: 07
[mel <level>]
Range for level: 07.
The mel parameter specifies the
maintenance entity group (MEG)
level (MEL) of the R-APS
messages.
Defining whether ring reverts revertive Enter no revertive to specify

back to original RPL when failure non-revertive operation.
is cleared
Configuring the ring ID ring-id <number> Used to configure destination of

no ring-id R-APS messages. ring-id is
appended to the R-APS DA MAC
address as follows:
01-19-A7-00-00-<Ring ID>
Possible values: 1-255 (00-FF)
Enabling propagation of Signal sf-trigger {east | west} mep <md-id> Before enabling SF propagation,
Failure (SF) condition from the <ma-id> <mep-id> verify that the relevant CFM
Ethernet OAM service layer no sf-trigger {east | west} parameters have been
configured.

Connecting previously defined sub-ring <sub-ring-number> Note: This is available for major
sub-ring to a major ring rings only. The sub-ring number
must be lower than the number
of the major ring it is assigned
to.
Defining ring timers timers [guard <guard-msec>] guard While the guard timer is
[holdoff <holdoff-msec>] active, all received R-APS
messages are ignored by the
node; thus preventing the
receipt of outdated R-APS
messages. The range is 10 ms to
2 seconds in 10 ms steps.
holdoff specifies the amount
of time an ERP-enabled node
waits from the point it
recognizes a local failure until it
reacts to the failure, i.e. it blocks
the port adjacent to the failed
link and send R-APS (SF) to the
RPL owner. The range is 0 to
10 seconds in 100 ms steps.
Defining data VLANs for user vlan <vlan-id> If using No Passthrough VLAN
traffic mode (the default), configure
both added/dropped and
passthrough VLANs as data
VLANs. If configuring
passthrough VLANs, configure
dropped VLANs only.
Note: In Passthrough VLAN
mode, if you configure a
passthrough VLAN as a data
VLAN, it will behave as an added/
dropped VLAN, and go through
the bridge, instead of bypassing
it.
To remove the VLAN assignment,
enter: no vlan <vlan-id>.
Before removing the VLAN
assignment, verify that all flows
using this VLAN have been
disabled.

Enabling passthrough VLANs passthrough-vlan [<vlan-range>] Configure all VLANs or an explicit

[queue-block east <qb-east> west range of VLANs, excluding those
<qb-west>] defined as data VLANs, as
no passthrough-vlan passthrough VLANs.
East and west queue blocks can
optionally be configured.
Enter no passthrough-vlan (the
default) to use the regular mode,
where both added/dropped
VLANs at the local ring node and
passthrough VLANs must be
configured as data VLANs and
are each assigned a bridge
broadcast domain (device
resource).
Commands in vlan level
Defining the queue blocks for queue-block east <east-block>

the VLAN west <west-block>
Assigning service name to VLAN service-name <name>
Administratively enabling the no shutdown Type shutdown to disable the

VLAN VLAN.
Defining amount of time for RPL wait-to-restore <seconds> This timer specifies how long the
owner to wait before blocking RPL owner waits to verify that
RPL after failure recovery ring failures have been cleared,
before blocking the RPL. The
range is 1 min (60 sec) to 12
min (720 sec).
Defining the west port of a ring west-port <bridge-port-number>

node ethernet [<slot>/]<port-index>
west-port <bridge-port-number>
west-port <bridge-port-number>
pcs <port-number>
Administratively enabling the no shutdown Type shutdown to disable the

ERP ERP.
Displaying ERP status show status See Viewing ERP Status.
Displaying ERP statistics show statistics See Viewing ERP Statistics.
Examples
This section illustrates the following configuration:
VLAN-aware bridge, with bridge ports 14
Ring:

East port Bridge port 1, Ethernet port 0/1

West port Bridge port 2, Ethernet port 0/2
R-APS VLAN 57
User traffic VLANs 100, 4000
Management flows (unidirectional) between SVI 1 and bridge port 4, over
VLAN 4000
Traffic flow (bidirectional) between Ethernet port 0/3 and bridge port 3, with
classification VLAN 100
#*******Configure SVI
exit all
configure port svi 1
no shutdown
exit all
# *******Configure bridge and bridge ports

configure bridge 1
port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
no shutdown
exit
port 4
no shutdown
exit all
# *******Configure Ethernet Ring Protection

configure protection
erp 1 major
bridge 1
east-port 1 ethernet 0/1
west-port 2 ethernet 0/2
r-aps vlan 57 vlan-priority 0 mel 3
port-type east node-port
port-type west node-port
color-mapping dei
cos-mapping my-p-bit
vlan 100
queue-block east 0/1 west 0/1
no shutdown
exit
vlan 4000
queue-block east 0/2 west 0/2
no shutdown
exit
timers holdoff 0
no shutdown

exit all
#*******Configure classifier profiles

configure flows
classifier-profile v100 match-any
match vlan 100
exit
match vlan 4000
exit
classifier-profile all match-any
match all
exit
#*******Configure flows
flow data
classifier v100
egress-port bridge-port 1 3
reverse-direction block 0/1
no shutdown
exit
flow mng_in
classifier v4000
no policer
vlan-tag pop vlan
ingress-port bridge-port 1 4
egress-port svi 1
no shutdown
exit
flow mng_out
classifier all
no policer
vlan-tag push vlan 4000 p-bit fixed 0
ingress-port svi 1
no shutdown
exit all
#*******Configure router
interface
configure router 1
interface 1
address 172.18.141.11/24
bind svi 1
no shutdown
exit
exit all
save

Viewing ERP Status

You can display the current status of an ERP entity.
To display ERP status:

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

RPL Link : Not Owner
Ring State : Init
East Port Status : Block R-APS and Data Local SF Source

West Port Status : Block R-APS and Data Local SF Source
ERP status provides information on:
Bridge number
Bridge ports assigned to be East and West ring ports
RPL link role:
Not owner All other nodes on the ring (that is, those that are not
the RPL owner node) operate as normal nodes and have no special
role on the ring.
RPL owner This node owns the RPL and blocks or unblocks the RPL
as conditions require. This node initiates the R-APS message.
Ring state:
Init The node is disabled (in shutdown).
Idle The node is performing normally (there is no link failure on the
ring). In this state, traffic is unblocked on both ring ports, except for
the RPL owner node, which blocks the RPL port (the other RPL owner
port is unblocked) and the RPL neighbors port.
Pending transition state between Protected and Idle (only in this
direction). This state means that the device detected that a signal
failure state was cleared, and started the WTR timer. After the WTR
timer consumes itself, the state changes to Idle.
Protected A failure occurred on the ring. A non owner node has
traffic blocked on the ring port that connects to the failed link. The
RPL owner, if it is not at one end of the failed link, unblocks the RPL
port so both ports are active.
East/West Port Status:
Forward Port is forwarding data.
Block R-APS and Data Port is blocked.

East/West Port Local SF Source Local Signal Failure source:

OK Port forwarding
CFM CC OAM failure
Server Layer Port down failure
Viewing ERP Statistics

You can view statistics on R-APS messages sent and received by the East and West
ports.
To display ERP statistics:

At the config>protection>erp(<erp-number>)# prompt, enter
show statistics
The ERP statistic counters are displayed.
ETX-2i>config>protection>erp(1)$ show statistics
East Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 0 0
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
West Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 0 0
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
Table 7-2. ERP Statistic Counters
Counter Description
R-APS SF Message Tx/Rx Total number of R-APS Signal Fail (SF) messages received or transmitted
by East/West port.
Received R-APS Signal Fail message indicates a failed port in the ring.
Transmitted R-APS Signal Fail message indicates a failed port in the
node.
R-APS NR Message Tx/Rx Total number of R-APS No Request (NR) messages received or
transmitted by East/West port.
Received R-APS No Request message indicates absence of failed ports in
the ring.
Transmitted R-APS No Request message indicates that the node fixed its
failed port.

Counter Description
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
7.3 Fault Propagation

Fault propagation enables you to specify which entities to shut down if link
failure occurs.
Applicable Products
VRRP group is relevant to ETX-2i.
Standards
IEEE 802.1ag-D8
ITU-T Y.1731
Benefits
You can ensure that you are sending packets via links that have not failed.
Failures are propagated end-to-end via actions such as OAM CFM messages and
entity deactivation, as well as VRRP priority decrement.
In the network-to-user or user-to-network direction, if a link fails for which fault
propagation is enabled, the corresponding port shuts down or OAM CFM message
indicating failure is sent, thus signaling the connected CPE to stop forwarding
frames through the link.
You can enable fault propagation to be triggered by failure detection on a
network/user interface or entity, which causes a user-configurable action (such
as deactivation or OAM CFM message indicating failure sent or lowering VRRP
priority) to be performed on a user/network interface or entity. You can enable
ETX-2i Fault Propagation 7-23

fault propagation in the network-to-user or user-to-network direction, for a pair

of entities such as PCS port, Ethernet ports, MEPs, VRRP group, queue block
shaper, flow policer, card (VDSL), TWAMP sessions, and ETPs.
You can define the following when you enable fault propagation for a pair of
entities:
Trigger:
Failure detected on a router interface.
Failure detected on port or MEP:
LOS link down detected
Failure detected on MEP:
OAM CFM AIS alarm indication signal detected
OAM CFM LOC loss of continuity detected
OAM CFM RDI remote defect indication detected
OAM CFM Interface status TLV remote port failure detected
OAM CFM E-LAN failure LOC has occurred for all the remote MEPs of
the MEP.
Failure detected in Bidirectional Forwarding Detection (BFD)
Failure detected in VDSL card connection (relevant for ETX2i with VDSL
card). This is detected via ping to a remote station using ICMP Echo. 75%
lost pings in one minute (i.e. unavailable minute) indicates an ICMP Echo
fail event.
Action to take when fault propagation is triggered:
Action performed on port:
Deactivate interface.
Action performed on VRRP group:
Decrease VRRP priority.
Action performed on MEP:
Send OAM CFM alarm indication signal to indicate failure.
Or
Send OAM CFM interface status TLV to indicate failure.
Action performed on queue block shaper:
Change shaper rate according to specified shaper-profile.
Action performed on flow policer:
Change policer rate according to specified policer-profile.
Action performed on VDSL card (relevant for ETX2i with VDSL card):
Reset VDSL card.
Wait-to-restore time the time period before enabling the shut-down entity
or ceasing to send OAM CFM interface status once the failed entity has been
restored
7-24 Fault Propagation ETX-2i

Holdoff timer Action is triggered only if detected fault propagation persists

for the amount of time configured in the holdoff timer. Holdoff timer enables
timing the fault propagation action and synchronizing with other network
redundancy mechansims.
Factory Defaults
By default, no fault propagation is configured. When you configure fault
propagation for a particular entity pair, the default configuration is as follows:
No trigger is defined for fault detection.
No action is defined to be performed when a fault is detected.
No holdoff is defined. Trigger activates fault propagation as soon as it is
detected.
Wait-to-restore time = 0
Configuring Fault Propagation

Follow this procedure to configure fault propagation:
1. Add a fault propagation entry for a pair of entities.
2. Configure the fault propagation parameters for the entry:
a. Specify the trigger(s).
b. Specify the action.
c. Define the holdoff timer.
d. For applicable actions, specify the wait-to-restore time if you do not want
the default value 0.
Adding Fault Propagation Entry

To add fault propagation for a pair of entities:
1. Navigate to configure fault.
2. Type the command:
fault-propagation <from-entity> to <to-entity> and enter the desired
entities, as shown in Table 7-3.
A prompt is displayed:
config>fault>fault-propogation(<from-entity>/to/<to-entity>)$
3. Configure the fault propagation parameters as needed (see Configuring Fault
Propagation Parameters).
Table 7-3. Fault Propagation Command Options
From Entity To Entity Command
BFD VRRP group fault-propagation bfd <router>/<interface>ip<ip-address>

to vrrp <vrid> {ipv4|ipv6} router-interface
<router>/<interface>

ETP Ethernet port fault-propagation etp <etp-name> to

port ethernet [<slot>/]<port>
ETP PCS fault-propagation etp <etp-name> to port pcs <port>
ETP Logical MAC fault-propagation etp <etp-name> to port logical-

mac <port>
ETP MEP fault-propagation etp <etp-name> to

mep <to-mdid> <to-maid> <to-mepid>
Ethernet port Ethernet port fault-propagation port ethernet [<slot>/]port> to

Ethernet port Logical MAC fault-propagation port ethernet [<slot>/]port> to

port logical-mac <port>
Ethernet port MEP fault-propagation port ethernet [<slot>/]port> to

Ethernet port PCS fault-propagation port ethernet [<slot>/]port> to

port pcs <port>
Ethernet port Queue block fault-propagation port ethernet [<slot>/]port> to shaper

shaper port <eth-port> queue-block <level>/<queue-block>
Ethernet port Policer instance fault-propagation port ethernet [<slot>/]port> to policer

flow <flow-name>
LAG port Ethernet port fault-propagation port lag <port> to port

ethernet [<slot>/]<port>
LAG port Logical MAC fault-propagation port lag <port> to port logical-
mac <port>
LAG port MEP fault-propagation port lag <port> to

LAG port PCS port fault-propagation port lag <port> to port pcs <port>
Logical MAC Ethernet port fault-propagation port logical-mac <port> to port

ethernet [<slot>/]<port>
Logical MAC Logical MAC fault-propagation port logical-mac <port> to port logical-
mac <port>
Logical MAC MEP fault-propagation port logical-mac <port> to

Logical MAC PCS port fault-propagation port logical-mac <port> to port pcs
<port>
MEP Ethernet port fault-propagation mep <md-id> <ma-id> <mep-id> to

MEP Logical MAC fault-propagation mep <md-id> <ma-id> <mep-id> to

port logical-mac <port>
MEP MEP fault-propagation mep <md-id> <ma-id> <mep-id> to


MEP PCS fault-propagation mep <md-id> <ma-id> <mep-id> to

port pcs <port>
MEP Queue block fault-propagation mep <md-id> <ma-id> <mep-id> to

shaper shaper port <eth-port> queue-block <level>/<queue-
block>
MEP Policer instance fault-propagation port mep <md-id> <ma-id> <mep-id> to

policer flow <flow-name>
PCS port (only Ethernet port fault-propagation port pcs <port> to port
with SHSDL ethernet [<slot>/]<port>
module)
PCS port (only Logical MAC fault-propagation port pcs <port> to port logical-
with SHSDL mac <port>
module)
PCS port (only MEP fault-propagation port pcs <port> to

with SHSDL mep <to-mdid> <to-maid> <to-mepid>
module)
Router interface VRRP group fault-propagation router-interface <router>/<interface> to

vrrp <vrid> {ipv4|ipv6} router-interface
<router>/<interface>
TWAMP session Card (VDSL) fault-propagation twamp-session controller <name> peer

<ip-address> session-id <number> to slot <number>
Configuring Fault Propagation Parameters

To configure fault propagation parameters:
1. Navigate to configure fault fault-propagation <from-entity> to <to-entity> to
select the fault propagation entry to configure.
A prompt is displayed:
config>fault>fault-propagation(<from-entity>/to/<to-entity>)#

Specifying the action to take when action-on-group { interface-deactivation | The following actions are supported:
fault propagation is triggered oam-cfm-if-status-tlv | oam-cfm-ais| interface-deactivation Deactivate
shaper-swap <shaper-profile> | policer- interface.
swap <policer-profile> | reset |
oam-cfm-if-status-tlv Send OAM CFM
vrrp-priority-decrement <number> }
interface status TLV to indicate failure.
oam-cfm-ais Send OAM CFM alarm
indication signal to indicate failure.
shaper-swap Change shaper rate
according to shaper-profile.
policer-swap Change policer rate
according to policer-profile.
reset Reset the card. Relevant for
ETX2i with VDSL card.
vrrp-priority-decrement Decrease VRRP
priority.
Typing no action-on-group removes the
action.
Notes:
The interface-deactivation action is
allowed only if the to-entity is an
Ethernet port.
The oam-cfm-if-status-tlv or
oam-cfm-ais action is allowed only if
the to-entity is a MEP.
The vrrp-priority-decrement
action is allowed only if the
to-entity is a VRRP group.
The shaper-swap action is relevant
only for the Queue Block Shaper
destination.
The policer-swap action is relevant
only for the Flow Policer destination.
shaper-swap and policer-swap
actions are enabled only if you have
activated the tmfp license for
enhanced fault propagation features.
Defining the number of milliseconds to holdoff <milliseconds> Possible values:

wait before a trigger activates fault no holdoff 0 default; no holdoff; trigger activates
propagation. fault propagation as soon as it is detected.
>0 number of milliseconds

Specifying the trigger(s) trigger { los | oam-cfm-loc | oam-cfm-rdi | The following triggers are supported:
oam-cfm-if-status-tlv | oam-cfm-ais | los link down
oam-cfm-all-rmep-fail | oam-cfm-cfs-clos |
oam-cfm-loc LOC detected
router-interface-down | bfd-session-down
| unavailable } oam-cfm-rdi RDI detected
oam-cfm-if-status-tlv
oam-cfm-ais AIS detected
oam-cfm-all-rmep-fail All remote MEPs
failed.
oam-cfm-csf-clos
router-interface-down specified RI is
operationally down.
bfd-session-down BFD session is
down.
unavailable VDSL connection to remote
station is down.
Typing no before the command removes the
specified trigger.
Note: The los trigger is allowed only if the
from-entity is an Ethernet port or ETP. The
OAM CFM triggers are allowed only if the
from-entity is a MEP.
Specifying the wait-to-restore time wait-to-restore <seconds> Possible values: 03600
Disabling Fault Propagation

To disable fault propagation for a pair of entities:
1. Navigate to configure fault.
2. Type the command:
no fault-propagation <from-entity> to <to-entity> to select the entities for
which to disable fault propagation.
The specified fault propagation is disabled.
Examples
To enable fault propagation:
From Ethernet port 0/3
To MEP 3 in maintenance association 3 in maintenance domain 2 (this
example assumes the MEP has been created)
Trigger: LOS
Action: Send OAM CFM interface status TLV.
Wait-to-restore time = 120 seconds
Holdoff timer = 150 milliseconds

exit all
config fault
fault-propagation port ethernet 0/3 to mep 2 3 3
trigger los
action-on-group oam-cfm-if-stat
wait-to-restore 120
holdoff 150
exit all
To display information on the fault propagation configured above:

ETX-2i# config fault fault-propagation port eth 0/3 to mep 2 3 3
ETX-2i>config>fault>fault-propagation(port/ethernet/0/3/to/mep/2/3/3)$ info
detail
action-on-group oam-cfm-if-status-tlv
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-if-status-tlv
no trigger oam-cfm-rdi
wait-to-restore 120
holdoff 150

To Ethernet port 0/3
Trigger: LOS
Action: Shut down Ethernet port.
Holdoff time = 320 milliseconds
exit all
config fault fault-prop port ethernet 0/1 to port ethernet 0/3
trigger los
action interface-deact
wait-to-restore 90
holdoff 320
exit all

ETX-2i# config fault fault-prop port eth 0/1 to port eth 0/3
ETX-2i>config>fault>fault-
propagation(port/ethernet/0/1/to/port/ethernet/0/3)# info detail
action-on-group interface-deactivation
trigger los
no trigger oam-cfm-loc
no trigger oam-cfm-if-status-tlv
no trigger oam-cfm-rdi
wait-to-restore 90
holdoff 320


From MEP 1 in maintenance association 1 in maintenance domain 1 (this
To MEP 2 in maintenance association 2 in maintenance domain 1 (this
Trigger: Any OAM CFM error
Action: Send OAM CFM interface status TLV
exit all
config fault
fault-propagation mep 1 1 1 to mep 1 2 2
trigger oam-cfm-loc
trigger oam-cfm-rdi
trigger oam-cfm-if-status-tl
action-on-g oam-cfm-if-stat
wait-to-restore 300
exit all

ETX-2i# config fault fault-propagation mep 1 1 1 to mep 1 2 2
ETX-2i>config>fault>fault-propagation(mep/1/1/1/to/mep/1/2/2)# info detail
action-on-group oam-cfm-if-status-tlv
no trigger los
trigger oam-cfm-loc
trigger oam-cfm-if-status-tlv
trigger oam-cfm-rdi
wait-to-restore 300

To Shaper port 0/3
Trigger: LOS
Action: Change shaper rate to 100M.
exit all
config fault fault-prop port ethernet 0/1 to shaper port ethernet 0/3 queue-
block 0/2
wait-to-restore 100
trigger los
action-on-group shaper-swap rate_100M
exit all

To policer flow tlv1
Trigger: LOS

Action: Change policer rate to 70M.

config fault fault-propagation port ethernet 0/1 to policer flow tlv1
wait-to-restore 100
trigger los
action-on-group policer-swap rate_70M
exit all
The following table lists the messages generated by the device when a
configuration error is detected.
Cannot delete entity while it You tried to delete an entity

participates in fault propagation used in fault propagation
existent configuration.
Fault propagation source does You tried to configure fault

not exist propagation with a non-
existent source.
Fault propagation destination You tried to configure fault

does not exist propagation with an existent
source but non-existent
destination.
Priority decrement fault You tried to configure a VRRP Either configure the to-element with a
propagation banned on VRRP group address owner as a different IP address that is not a virtual
address owner to-element. IP address, or use a virtual address that
is not a real address of the to-element.
VRRP priority preemption must You tried to configure a VRRP Enable preemption for the VRRP group.
be enabled for fault propagation group whose preemption is
disabled as a to-element.
7.4 Link Aggregation

In link aggregation (LAG) mode according to IEEE 802.3ad, Ethernet interfaces can
be aggregated into a single logical link for protection or load balancing.
Applicable Products
Ethernet 10GbE ports are relevant only to ETX-2i-10G half and full 19.
LAG is supported with or without LACP (user-configurable), with 50ms LAG
switchover time.
7-32 Link Aggregation ETX-2i

Protection LAG groups can have up to two members, and load-balancing LAG
goups can have up to four members.
A protection LAG group can be made up of one or two adjacent network
ports or user ports; not both types.
A LAG group can include ports of the same speed only (1G or 10G).
A LAG group can function in protection or load-balancing mode.
A load-balancing LAG group can be made up of up to four members from
specified ports. The ports do not have to be adjacent.
ETX2i You can configure up to four LAG groups (protection and load-
balancing).
ETX-2i-B You can configure up to three LAG groups (protection and load-
balancing).
ETX-2i-10G half 19 You can configure up to six LAG groups (protection and
load-balancing).
Members in a protection LAG group can be: 1 and 2, 3 and 4, 5 and 6, 7
and 8, 9 and 10, or 11 and 12.
Members in a load-balancing LAG group can include ports from one of the
following groups: (A single LAG group cannot contain some ports from
one group and other ports from another group.)
1, 2
3-8 (if 3,4 are 10GbE, LAG can be supported only between the two.)
9-12
ETX-2i-10G full 19 You can configure up to 14 LAG groups (protection and
load-balancing):
Members in a protection LAG group can be: 1 and 2, 3 and 4, 5 and 6, 7
and 8, 9 and 10, 11 and 12, , or 27 and 28.
Members in a load-balancing LAG group can include ports from one of the
following groups: (A single LAG group cannot contain some ports from
one group and other ports from another group.)
1, 2
3-16
17-28
Standards
IEEE 802.3ad
Benefits
ETX-2i can continue to route traffic even if one of the links fails.
ETX-2i Link Aggregation 7-33

All LAG ports receive traffic at the same time and one port transmits. The LAG
members can be network or user interfaces, and must be connected to the same
switch/router. If LACP is activated, then LACP control frames are periodically
transmitted in order to locate failures as they occur.
You can configure an anchor port for a LAG group, which you can use to
configure flows to/from the LAG group. The default anchor port is the first port
bound to the LAG group. The MAC address of the anchor port is used for logical
port level entities (router interface over the LAG, OAM MEP over the LAG, etc.).
Protection
If the transmitting port fails, ETX-2i switches to a standby link. The equipment
connected to the Ethernet ports must use compatible switching criteria for
redundancy to be available:
For networks using Layer 2 switching The criterion is signal loss.
For networks using Layer-3 routing The router must support IEEE 802.3ad
or other link aggregation protocol that views the aggregated link as a single
logical interface.
Using link aggregation inherently provides redundancy, because if a port fails,
another port can continue transferring traffic. Failure of a link is detected by
sensing the loss of valid signals, or receiving a failure report via Link Aggregation
Control Protocol (LACP) if applicable, in which case all traffic is sent through the
other link.
Load Balancing
In a load balancing LAG group, traffic is distributed to the different ports
according to the configured distribution method. You can configure the following
distribution methods:
MAC source address
MAC destination address
MAC source address and MAC destination address
IP source address
IP destination address
IP source address and IP destination address
MAC source/destination address and IP source/destination address
For distribution method based on IP address, all non IP packets are forwarded on
the same port. For distribution method based on MAC source/destination address
+ IP source/destination address, fallback for non IP packets is based on MAC
address info.
Note All load balancing LAG groups in the device must use the same distribution
method.
The load balancing and distribution is performed after the queuing mechanism.
The port policer is supported at the port level, not on LAG aggregate ingress

traffic. Aggregate LAG egress traffic can be shaped at the LAG level up to a
maximum of 10 Gbps (level 1 shaper supported for rates up to 10 Gbps).
You can configure the minimum number of active ports in the LAG for it to be
considered operationally active. A port is considered as active if it has no physical
layer failure and LACP is synched (if LACP is enabled).
If there are flows over the anchor port when the LAG group is created and
enabled, the flows are inherited by the LAG group. The LAG group can be
administratively enabled if flows exist over the anchor port, but not if flows exist
over a non-anchor port. If the LAG group is deleted or administratively disabled,
the flows and traffic remain on the anchor port; they are not distributed to other
ports.
Factory Defaults
By default, no LAG groups are configured. When a LAG group is created, it has
the following default configuration.
admin-key giga-ethernet LAG admin key is GbE port
lacp no lacp LACP not enabled
mode redundancy LAG is protection LAG
If the mode is changed to load-balance, the default configuration is as shown

below.
admin-key giga-ethernet LAG admin key is GbE port
distribution-method src-ip Packets distributed according to source IP address
lacp no lacp LACP not enabled
minimum-link-number 1 One LAG port must be active
mode load-balance LAG is load balancing LAG
Configuring LAG
This section explains how to define a link aggregation group (LAG) and enable link
aggregation control protocol (LACP).
Notes In order to enable LACP for the LAG, the ports bound to the LAG must be
associated with an L2CP profile that specifies peer action for MAC 0x02.
In a load-balancing LAG, all non-anchor ports bound to the LAG must not be
associated with a queue group profile (use command no queue-group).

To configure the LAG:

1. Navigate to configure port lag <num>.
The config>port>lag(<num>)# prompt is displayed.
Assigning an admin key to the admin-key {giga-ethernet | You must define admin key
LAG to indicate the port speed fast-ethernet | ten-giga-ethernet} before binding ports to the
LAG.
Defining the LAG anchor port anchor-port ethernet <port-index>

anchor-port logical-mac <port-number>
Adding a port to the LAG bind ethernet [<slot>/]<port-num> Entering no bind removes a link
bind logical-mac <port-num> from the LAG.

Assigning method of distribution-method {src-mac | dest-mac src-mac Packets are

distributing traffic within LAG | src-or-dest-mac | src-and-dest-mac | distributed according to their
src-ip | dest-ip | src-dest-mac-ip | source MAC addresses.
round-robin | source-port | one-to-one | dest-mac Packets are
src-dest-ip} distributed according to their
destination MAC addresses.
src-or-dest-mac not
supported
src-and-dest-mac Packets are
distributed according to their
source and destination MAC
addresses.
src-ip Packets are distributed
according to their source IP
addresses.
dest-ip Packets are
destination IP addresses
src-dest-mac-ip Packets are
source and destination MAC
and IP addresses.
round-robin not supported
source-port not supported
one-to-one Packets are
distributed one to one.
src-dest-ip Packets are
source and destination IP
addresses.
Note: The one-to-one
parameter is relevant only for
redundancy LAG; the other
parameters are relevant only
for load balancing LAG.

Enabling LACP and setting lacp [tx-activity {active | passive}] tx-activity Defines operation
LACP parameters [tx-speed { slow | fast }] [sys-priority mode:
<sys-priority>] active LAG interface
periodically transmits LACP
frames (LACPDUs) to all
links with LACP enabled.
passive LAG interface
does not initiate the LACP
exchange, but replies to
received LACPDUs.
tx-speed Defines time to wait
before sending LACP frames:
fast three seconds
slow 90 seconds
sys-priority determines
aggregation precedence. If
there are two partner devices
competing for the same LAG,
LACP compares the priorities
for each grouping of ports. The
LAG with the lower priority is
given precedence.
Defaults:
If you type lacp without
specifying tx-activity, it is
set to active.
If you type lacp without
specifying tx-speed, it is set
to fast.
Typing no lacp disables LACP
protocol.
Configuring LLDP parameters lldp See Link Layer Discovery

Protocol (LLDP) for details.
Defining the minimum number minimum-link-number <number> Range is 1 to maximum number
of links required for load of LAG members.
balancing LAG If less than the minimum
number of links function
properly, LAG failure is
reported.
Specifying if LAG is for mode {redundancy | load-balance}

redundancy or load balancing
Administratively enabling LAG no shutdown Using shutdown disables the

LAG.
Displaying bind status show bind

Displaying LACP statistics show lacp-statistics ethernet

[<slot>/]<port-id>
Displaying LACP status show lacp-status ethernet

[<slot>/]<port-id>
Displaying LAG statistics show statistics running
Clearing LAG statistics clear-statistics
Displaying LAG status show status See Viewing LAG Status.
Examples
Protection LAG
To define LAG:
L2CP profile mac2peer, with mac0x02 set to peer action
LAG members Ethernet ports 1 and 2
LACP operation mode active
Distribution method one to one
System priority 32768
#****************Create L2CP profile mac2peer
exit all
configure port l2cp-profile mac2peer
mac 0x02 peer
exit
#****************Assign L2CP profile mac2peer to network ports

eth 1 l2cp profile mac2peer
eth 2 l2cp profile mac2peer
#****************Configure LAG 1
lag 1
bind ethernet 1
bind ethernet 2
lacp tx-activity active tx-speed slow sys-priority 32768
distribution-method one-to-one
no shutdown
exit all
To display LACP status:

ETX-2i#configure port lag 1
ETX-2i>config>port>lag(1)# show lacp-status eth 1
Ports
-----------------------------------------------------------
Actor Partner
Port Number : 1 1
Port Priority : 32768 0
System ID : 0020D250E70A 0020D2F5AD58

System Priority : 32768 32768

Operational Key : 2 32
Activity : Active Active
Timeout : Long Long
Synchronized : Yes No
Collecting : No No
Distributing : No No
To display LACP statistics:

ETX-2i>config>port>lag(1)# show lacp-statistics ethernet 1
LACP
---------------------------------------------------------------
Rx LACP Frames : 3221
Rx Marker Frames : 0
Rx Unknown Frames : 0
Rx Illegal Frames : 0
Tx LACP Frames : 5783
Tx Marker response Frames : 0
Load Balancing LAG
To define load balancing LAGs:

L2CP profile mac2peer, with mac0x02 set to peer action
LAG members:
LAG 1: GbE ports 3 to 6
LAG 2: GbE ports 7 to 8.
LACP operation mode active
Distribution method Destination MAC address
Flows:
Flows for LAG 1 between GbE 1 and 3, VLAN 100
Flows for LAG 2 between GbE 1 and 7, VLAN 200
exit all
#***********Configure L2CP profile
mac 0x02 peer
exit
#***********Associate ports with the L2CP profile

#***********Specify no queue group profile for non-anchor ports
ethernet 3
l2cp profile mac2peer
no shutdown
exit
ethernet 4
no queue-group
no shutdown

exit
ethernet 5
no queue-group
no shutdown
exit
ethernet 6
no queue-group
no shutdown
exit
ethernet 7
no shutdown
exit
ethernet 8
no queue-group
no shutdown
exit
#***********Configure LAGs
lag 1
mode load-balance
distribution-method dest-mac
admin-key giga-ethernet
bind ethernet 3
bind ethernet 4
bind ethernet 5
bind ethernet 6
lacp tx-activity active tx-speed fast
anchor-port ethernet 3
no shutdown
exit
lag 2
mode load-balance
distribution-method dest-mac
admin-key giga-ethernet
bind ethernet 7
bind ethernet 8
lacp tx-activity active tx-speed fast
anchor-port ethernet 7
no shutdown
exit
#***********Configure classification profiles for flows

exit
flows
classifier-profile vlan100 match-any match vlan 100
classifier-profile vlan200 match-any match vlan 200

exit
#***********Configure flow for LAG 1

flow lag1_1_to_3
classifier vlan100
no policer
no shutdown
exit
flow lag1_3_to_1
classifier vlan100
no policer
no shutdown
exit
#***********Configure flow for LAG 2

flow lag2_1_to_7
classifier vlan200
no policer
no shutdown
exit
flow lag2_7_to_1
classifier vlan200
no policer
no shutdown
exit all
save
To display LACP status:

ETX-2i>config>port>lag(1)# show lacp-status ethernet 3
Ports
-----------------------------------------------------------
Actor Partner
Port Number : 3 3
Port Priority : 32768 0
System ID : 0020D2EE5ED8 0020D2EE62E1
System Priority : 32768 0
Operational Key : 2 31
Activity : Active Active
Timeout : Short Short
Synchronized : Yes Yes
Collecting : Yes Yes
Distributing : Yes Yes

To display LACP statistics:

ETX-2i>config>port>lag(1)# show lacp-statistics ethernet 3
LACP
---------------------------------------------------------------
Rx LACP Frames : 386
Rx Marker Frames : 0
Rx Unknown Frames : 0
Rx Illegal Frames : 0
Tx LACP Frames : 386
Tx Marker response Frames : 0
To display LAG status:

ETX-2i>config>port>lag(1)# show status
Group
---------------------------------------------------------------
Administrative Status: Up
MAC Address : 00-20-D2-EE-5E-D8
Links
---------------------------------------------------------------
Port Admin Oper LACP Redundancy
---------------------------------------------------------------
1/3 Up Up Sync Active
To display LAG statistics:

ETX-2i>config>port>lag(1)# show statistics running
Rate of Total
---------------------------------------------------------------
Port Rx Total Frames Tx Total Frames
(%) (%)
---------------------------------------------------------------
1/3 25.00 25.00
1/4 25.00 25.00
1/5 25.00 25.00
1/6 25.00 25.00
Viewing LAG Status

You can display the LAG status, including the information specified in Table 7-5.
To display the LAG status:

At the prompt config>port>lag(<num>)#, enter:
show status
ETX-2i# configure port lag 1

Group
---------------------------------------------------------------
Name : LAG 1
Group
---------------------------------------------------------------
Mode : Redundancy
Speed : 1Gbps
MAC Address : 00-20-D2-50-C0-D3
Links
---------------------------------------------------------------
---------------------------------------------------------------
1 Up Up Sync Active
2 Up Up Sync Active
Table 7-5. LAG Status
Group
Name Displays name assigned to LAG
Administrative Status Indicates if LAG is administratively enabled or disabled: Up

or Down
Operational Status Indicates if LAG is operational:

Up LAG is operational.
Down LAG is not operational, for reason such as being
administratively disabled or link shut down for Fault
propagation.
LLD (all links down) Both protection LAG ports are down,
in case of protection LAG).
LLD (minimum links down) Minimum links are down, in
case of load balancing LAG.
Mode Displays LAG mode: Redundancy or Load Balance
Speed Indicates LAG speed as one of the following, according to

X (port speed in case of protection LAG, or number of
active links link rate in case of load balancing LAG):
X >=1 Gbps Speed indicated as X Gbps
0 < X < 1 Gbps Speed indicated as X Mbps
X = 0 Speed indicated as Not Applicable
MAC Address Displays MAC address of LAG
Links
Port Displays port number of link

Admin Indicates if link is administratively enabled or disabled: Up

or Down
Oper Indicates if link is operational: Up or Down
LACP Indicates if LACP is synchronized
Redundancy Indicates if redundancy is active
Examples
To display the status of a protection LAG with all links down:
Group
---------------------------------------------------------------
Name : LAG 1
Group
---------------------------------------------------------------
Operational Status : LLD (all links down)
Mode : Redundancy
Speed : Not Applicable
MAC Address : 00-20-D2-50-C0-D3
Links
---------------------------------------------------------------
---------------------------------------------------------------
1 Up Down Not Sync Active
2 Up Down Not Sync Active
To display the status of a load balancing LAG with minimum links down:
Group
---------------------------------------------------------------
Operational Status : LLD (minimum links down)
Mode : Load Balance
Speed : Not Applicable
MAC Address : 00-20-D2-EE-41-C1
Links
---------------------------------------------------------------
---------------------------------------------------------------
1/1 Up Down Not Sync Active
1/2 Up Down Not Sync Active

7.5 Link Protection

Two Ethernet network interfaces can operate in 1:1 bidirectional protection
(redundancy) mode. In this mode, only one port is active at a time to carry
traffic. If it fails, the second port takes over. The recovery mode (revertive or
non-revertive) and the restoration time in revertive mode can be selected
according to the application requirements.
Standards
IEEE 802.3ad
Benefits
ETX-2i can continue to route traffic even if one of the links fails.
Link protection offers an alternative to link aggregation, if protection without
LACP is acceptable. You can configure parameters such as revertive/non-revertive
mode, the restoration time in revertive mode, forcing active link, etc., however
the switchover time to the standby link is longer than for LAG.
In 1:1 bidirectional mode mode, the following topologies can be used:
Connection of both ports to the same switch/router
Connection of the ports to different switch/routers. The main advantage of
this topology is its higher availability, because each port can be routed along
a different path through the network. This topology is also referred to as
dual homing.
With 1:1 bidirectional redundancy mode, at any time only one of the ports is
actively carrying traffic, and the other port serves as the backup port. A RAD
proprietary redundancy algorithm, based on loss of Ethernet signal, is used to
detect line failure. The protection switching (flipping) time is less than 1 second.
It also depends on the network relearning time or aging.
The recovery mode after protection switching can be selected in accordance with
the application requirements:
Non-revertive mode ETX-2i does not automatically flip back after the failed
port returns to normal operation, but only when the currently used port fails,
or after a manual flip command.
Revertive mode ETX-2i flips back to the original port when it returns to
normal operation. Flipping back can be delayed by specifying a restoration
time, during which alarms are ignored. As a result, ETX-2i starts evaluating
the criteria for protection switching (flipping) only after the restoration time
expires, thereby ensuring that another flip cannot occur before the specified
time expires.
7-46 Link Protection ETX-2i

Factory Defaults
By default, bidirectional redundancy is not enabled.
Configuring Link Protection

Configuring a 1:1 protection requires defining an Ethernet group.
To define an Ethernet group:

At the Protection context (config>protection), enter:
ethernet-group <group-id>
The system switches to the context of the specified Ethernet group
(config>protection>eth-group(<group-id>)).
To add/remove protection and working ports in manual mode:

At the Ethernet Group context (config>protection>eth-group(<group id>)),
enter
bind ethernet primary [<slot>/]<port>
To remove protection and working ports, enter:
no bind ethernet primary
To add/remove protection and working ports in 1to1 mode:

enter:
bind ethernet [primary [<slot>/]<port>] [secondary [<slot>/]<port>]
To remove protection and working ports, enter:
no bind ethernet primary
no bind ethernet secondary
To define the operation mode:

enter:
oper-mode { 1-to-1 | manual }
To define the port recovery mode as revertive:

enter:
revertive
Traffic is switched back to the primary port after it recovers.
To define the port recovery mode as non-revertive:

At the Ethernet Group context config>protection>eth-group(<group id>)),
enter:
no revertive
Traffic continues being transmitted over the secondary port after the primary
port recovers.
ETX-2i Link Protection 7-47

To define the time between recovery and resumption of transmission

enter
wait-to-restore <seconds>
The primary port resumes transmitting traffic once the specified time has
been restored and the specified time has elapsed. You can choose between 1
and 720 seconds.
To define the period of time that the failed link stops transmitting to report the
failure:
enter
tx-down-duration-upon-flip <seconds>
The secondary port resumes transmitting after the specified reporting time.
You may specify a time in the range between 0 and 30 seconds. This function
is useful if there is no autonegotiation between the link end points.
To force a port to transmit:

At the EthernetGroup context (config>protection>eth-group(<group id>)),
enter:
force-active-port ethernet [<slot>/]<port>
The specified port is set to be active. You can choose the primary port (1) or
the secondary port (2).
Port 1. Port 1 is configured as a permanently active link. Even if port 1
fails, the traffic is not switched to the standby port.
Port 2. Port 2 is configured as a permanently active link. Even if port 2
fails, the traffic is not switched to the standby port.
To specify that neither of the ports is forced to remain active, enter:
no force-active-port
To display the Ethernet group status:

At the EthernetGroup context (config>protection>eth-group(<group id>)),
enter:
show status
The Ethernet group status parameters are displayed.
Example
To define link protection:
Ethernet group 1
Protection port Ethernet port 1/1
Working port Ethernet port 1/2
Operation mode One-to-one
exit all
configure protection ethernet-group 1

bind eth primary 1/1 secondary 1/2

oper-mode 1-to-1
exit all
To display configuration information for the link protection:
ETX-2i#configure protection ethernet-group 1
ETX-2i>config>protection>eth-group(1)# info detail
bind ethernet primary 1/1 secondary 1/2
oper-mode 1-to-1
revertive
wait-to-restore 0
tx-down-duration-upon-flip 0
no shutdown
ETX-2i Link Protection 7-49


Chapter 8
Traffic Processing
This chapter describes traffic processing features:
Bridge
Classification by Port/Flow
Distributed Network Functions Virtualization (D-NFV)
Ethernet over GRE (ETHoGRE) Tunnel
Layer-2 Control Processing
Link Layer Discovery Protocol (LLDP)
MLDv2 Snooping
Pseudowire Connections
PW Cross Connects
Router
Routing Protocol BGP
Routing Protocol OSPF
Virtual Router Redundancy Protocol - VRRP
8.1 Bridge
The ETX-2i bridge is a Layer-2 forwarding entity that can be VLAN-aware or
VLAN-unaware.
Applicable Products
Standards
IEEE 802.1D
IEEE 802.1Q
ETX-2i Bridge 8-1

Chapter 8 Traffic Processing Installation and Operation Manual
Benefits
The bridge delivers E-LAN and E-Tree services.
The bridge operates in VLAN-aware or VLAN-unaware mode.
When the bridge is working in VLAN-aware mode:
Bidirectional flows are supported.
Each VLAN can work in E-LAN or E-Tree mode.
When the bridge is working in VLAN-unaware mode:
Bidirectional flows are not supported.
Only one egress flow per bridge port can be configured.
The bridge can work in E-LAN or E-Tree mode.
Traffic through the bridge is configured via flows between non-bridge ports (e.g.
Ethernet, ETP, logical MAC, PCS, SVI) and bridge ports, allowing editing action at
the bridge ports.
Notes Flow classifications source/destination MAC address or source/destination IP

address are not supported via bridge.
If flows use the same queue before relevant MAC addresses are learned, the
policing does not function properly.
Different flows from the same port can be mapped to different bridge ports (see
Figure 8-1). However, different flows from one bridge port cannot be mapped to
different ports (see Figure 8-2).
Figure 8-1. Flows Mapped from Same Port to Different Bridge Ports Allowed
Figure 8-2. Flows Mapped from Same Bridge Port to Different Ports Not Allowed
8-2 Bridge ETX-2i

Installation and Operation Manual Chapter 8 Traffic Processing
Admission to Bridge
In order for a frame to be admitted to the bridge, its classification must match
the flow classification configured for the bridge port.
In VLAN-aware mode, VLAN membership is read-only and automatically learned
from the VLAN classification used in bridge port flows. Additionally, flows with
untagged classification must have a push editing action.
In VLAN-unaware mode, any packet may be admitted according to the configured
flow classifications.
Packet Editing on Reverse Flows

In the case of a bidirectional flow, the editing action can be specified for the flow
to the bridge port, but not for the reverse direction. ETX-2i performs editing on
the reverse direction according to the flow classification and specified editing
actions. The following table shows the editing action on the reverse flow, as well
as the VLAN learned from the flow.
Classification Editing of Flow with Editing of Reverse VLAN Value

Bridge Port as Egress Directional Flow
Port
VLAN X + any None None X
VLAN X..Y None Not allowed Not allowed
Untagged None None Not supported; use

push action
VLAN X None None X

Inner VLAN Y
Any classification Push X Pop X

(including untagged) p-bit fixed/copy/profile
Any classification Push X push inner Y Pop twice X

(including untagged and p-bit and inner p-bit
all) fixed/copy/profile
VLAN X Pop Push X Y

Inner vlan Y
VLAN X Pop Not allowed Not allowed

Inner vlan Y..Z
VLAN X Pop Not allowed Not allowed
VLAN X + any Swap VLAN Y Swap VLAN X Y

p-bit fixed/copy/profile
VLAN X Swap VLAN Z Swap VLAN X Z

Inner VLAN Y p-bit fixed/copy/profile
VLAN Y..Z Swap VLAN Y Not allowed Not allowed

VLAN X Push VLAN Y, swap VLAN Z Pop, swap X Y

ETX-2i Bridge 8-3

Classification Editing of Flow with Editing of Reverse VLAN Value

Bridge Port as Egress Directional Flow
Port
VLAN Y..Z Push VLAN X, swap VLAN Z Not allowed Not allowed
VLAN X Pop, swap VLAN Z Push X Z

Inner VLAN Y p-bit fixed/copy/profile Inner swap to Y
VLAN X Pop, swap 200 Not allowed Not allowed

Inner VLAN Y..Z p-bit fixed/copy/profile
VLAN X Swap VLAN Z, Swap X, inner swap Y Z

Inner VLAN Y inner swap VLAN K
VLAN X Swap VLAN Z, Not allowed Not allowed

Inner VLAN Y..Z inner swap VLAN K
L2PT Over Bridge

L2PT over the bridge is implemented by configuring a protocol and MAC swap in
the L2CP profiles of the ports corresponding to egress bridge flows. When
packets are transmitted across the bridge, the MAC swap actions are determined
according to the L2CP profiles. If an ingress port has an L2CP profile specifying
protocol and MAC swap:
If the egress port is a user port with L2CP profile specifying protocol and MAC
swap, the MAC swap is not performed.
If the egress port is a network port or does not have an L2CP profile
specifying protocol and MAC swap, the MAC swap is performed.
For example, given the configuration in Figure 8-3, if P1 and P3 are both user
ports with L2CP profiles specifying protocol and MAC swap, and P2 is a network
port:
MAC swap is performed for packets transmitted from or to P1 (P1 to P2 or
P3, P2 to P1, and P3 to P1).
MAC swap is not performed for packets transmitted between P2 and P3 (P2
to P3, P3 to P2).
8-4 Bridge ETX-2i

Figure 8-3. Bridge Flows and Ports
Management via Bridge

In order to manage via the bridge, you need to configure the following (see
VLAN-Aware Bridge for an example of configuring the bridge for management):
Router interface for management, bound to SVI
Flow between SVI and bridge port (only one SVI<->bridge port flow can be
created per bridge port)
Flow between Ethernet port and bridge port
Note It is recommended to manage ETX-2i via the bridge only if the bridge is
VLAN-aware.
Spanning Tree Protocol

Spanning Tree Protocol (STP) (802.1Q; previously 802.1D) is a Layer-2 loop
avoidance technique used in Ethernet networks. Loops are created in bridge-
based networks with more than one path between two endpoints. STP is used to
identify the best path to the destination, and block all other paths. The blocked
links are connected and kept inactive, creating automatic backup links.
Figure 8-4 illustrates STP operation. Bridge 3 is directly connected to Bridge 1 and
Bridge 2. Another physical link directly connects Bridge 1 to Bridge 2. Under
normal conditions, there is looping of data, causing broadcast congestion on the
network. When an STP is applied, Link A is blocked from transmitting any data,
but it remains on standby and listens to the network. If Link B or Link C fails, Link
A is activated, providing link and switch redundancy in the network.
ETX-2i Bridge 8-5

Link A Link A
Bridge 1 Bridge 2 Bridge 1 Bridge 2
Link B Link C Link B Link C
Bridge 3 Bridge 3
Physical Topology Logical Topology
Figure 8-4. STP Operation
ETX-2i supports a single STP instance per chassis.
STP Bridge Types

The root bridge is the central reference bridge in the STP. It serves as a reference
for other bridges to determine their best cost path. Bridge 3 in Figure 8-4 serves
as a root in the application.
The root bridge is elected by automatically selecting the bridge in the network
with the lowest bridge ID. If the root bridge fails, the other bridges select a new
root device.
Link Cost
Each link in the network is allocated a certain cost. Usually, higher-bandwidth
links that are adjacent to the root bridge are assigned a lower cost. Lower-
bandwidth links that are multiple hops away from the root bridge are assigned a
higher cost. Once link costs are estimated, STP determines the lowest cost
connections from each bridge to the root bridge to determine the lowest-cost
path. It also blocks all the other higher cost links to prevent loops in the network.
Bridge Protocol Data Units

The bridges use Bridge Protocol Data Units (BPDUs) to exchange information
about network topology, bridge IDs, link costs etc. BPDUs help establish the best
route (least cost path) to the root bridge.
When there is a change in the network, relevant BPDUs are sent to all the
bridges/bridge ports by the root bridge. The bridges adjust their tables to
determine the new routes to the terminals.
Rapid Spanning Tree Protocol and Multiple Spanning Tree Protocol

Rapid Spanning Tree Protocol (RSTP) (802.1Q; previously 802.1W) is an evolution
of STP with some protocol enhancements, providing significantly faster spanning
tree convergence following a topology change. In RSTP, the link status of each
port is monitored proactively (instead of waiting for the BPDU messages) to
detect changes in network topology.
ETX-2i supports a single instance of RSTP over a VLAN aware or VLAN unaware
bridge (ETX-2i supports only one bridge).
8-6 Bridge ETX-2i

Multiple Spanning Tree Protocol (MSTP) (802.1Q; previously 802.1S) supports

several instances of forwarding topology on the same physical topology for load
balancing purposes (per a group of VLANs).
MSTP is supported over a VLAN-aware bridge only. MSTP maps a group of VLANs
(that have been configured at the bridge ports) into a single Multiple Spanning
Tree instance (MSTI). This means that the Spanning Tree Protocol is applied
separately for a set of VLANs instead of every VLAN in the whole network.
Different root bridges and different STP parameters can be individually configured
for each MSTI. So, one link can be active for one MSTI and the other link active
for the second MSTI. This enables some degree of load-balancing and generally
two MSTIs are used in the network for easier implementation. ETX-2i supports up
to 16 MSTIs per chassis, excluding MSTI0 (IST). All VLANs in the bridge that are
not configured to a specific MSTI, belong to MSTI0 (IST).
Figure 8-5 illustrates MSTP operation. MSTI 1 is used for forwarding traffic
marked with VLANs 10 and 20; MSTI 2 is used for VLANs 30 and 40; MSTI 0 for
the remaining VLANs in the network.
Bridge 1 Bridge 2
Bridge 3
Physical Topology
Root Root
Bridge 1 Bridge 2 Bridge 1 Bridge 2 Bridge 1 Bridge 2
Root
Bridge 3 Bridge 3 Bridge 3

MSTI 1 Logical Topology MSTI 2 Logical Topology MSTI 0 Logical Topology
Figure 8-5. MSTP Operation
RSTP and MSTP uses OOB MNG MAC as the Bridge Identifier.
Note Before using RSTP or MSTP, you are required to configure trapping of
01-80-C2-00-00 using an L2CP profile with a peer action for 01-80-C2-00-00.
ETX-2i supports RSTP and MSTP per 802.1Q over a bridge with the following port
types:
User
Network
PCS
ETX-2i Bridge 8-7

Logical MAC
Note ETX-2i does not support RSTP and MSTP over a bridge with the following port
types:
OOB
LAG group
Ports configured with ETH protection
Ports configured as G.8032 ring nodes
Ports not connected to a physical port (such as a router interface or MEF 8
PW)
STP interoperability is supported per bridge port; when the RSTP/MSTP bridge
identifies STP messages on a port, it reverts to STP mode on that port.
Factory Defaults
By default, the bridge is not created in ETX-2i. When the bridge is created, its
default configuration is VLAN-aware, filtering enabled, and with no bridge ports
or VLANs. When VLANs are created, the default configuration is E-LAN mode.
ETX-2i>config# bridge 1
ETX-2i>config>bridge(1)$ info detail
name "BRIDGE 1"
vlan-aware
filtering
aging-time 300
ETX-2i>config>bridge(1)$ vlan 333
ETX-2i>config>bridge(1)>vlan(333)$ info detail
maximum-mac-addresses 0
mode e-lan
The default STP parameters are as follows:
admin-edge Disable
auto-edge Enable
cost (bridge port) 0
forward-time 15 sec
hello-time 2 sec
max-age 20 sec
max-hops 20
mcheck Disable
mode rstp
name empty string
priority (bridge port) 128
priority (bridge) 32768
8-8 Bridge ETX-2i

restricted-role Disable
restricted-tcn Disable
revision 0
tx-hold-count 6
Configuring the Bridge

To configure the bridge, perform the following steps:
1. Configure the bridge.
2. Configure the bridge ports.
3. If working in VLAN-unaware mode:
For E-Tree service, configure bridge mode to E-Tree and configure root.
4. If working in VLAN-aware mode:
Configure VLANs. For E-Tree service in a VLAN, configure VLAN mode to
E-Tree and configure root.
5. Configure flows between non-bridge ports and bridge ports.
6. Configure RSTP/MSTP (optional).
7. Configure spanning tree L2CP profile.
Note In Bridge configuration, different bridge ports that egress to the same ETH port
with different VLAN editing cannot share the same queue block.
To configure the bridge:

1. At the config# prompt, enter:
bridge 1
The config> bridge(1)# prompt is displayed.
Defining aging time for MAC aging-time <seconds> Possible values: 603000
table entries (seconds)
Clearing addresses in MAC table clear-mac-table
Enabling or disabling filtering filtering To disable filtering forwarding

mode, type no filtering.
Configuring VLAN-unaware mode {e-tree | e-lan} Changing to E-Tree mode

bridge to E-Tree or E-LAN mode requires you to define a bridge
port as root.
Note: This command is
available only if the bridge is
VLAN-unaware.
ETX-2i Bridge 8-9

Assigning a name to the bridge name To delete the bridge name,

type no name.
Configuring bridge ports (see port <port-number> ETX2i: Range is 144

Configuring Bridge Ports) ETX-2i-B, ETX-2i-10G: Range is
1-32
To delete a bridge port, enter
no port <port-number>.
Configuring bridge port as root root <bridge-port> Notes:

port in E-Tree mode This command is available
only if the bridge is
VLAN-unaware and the
mode is E-Tree.
Supports more than one
root; the number of roots
supported is equivalent to
the number of bridge ports.

Configuring static MAC address static-mac <vlan-id> <mac-address> Note: Before creating the static
<bridge-port> MAC, you must create a flow
with the bridge port, and VLAN
(if applicable).
Defining VLANs (see below) vlan <vlan-id> Possible values: 14094

To delete a VLAN, enter
no vlan <vlan-id>
Note: This command is
available only if the bridge is
VLAN-aware.
Setting mode to VLAN-aware or vlan-aware To set mode to VLAN-unaware,

VLAN-unaware enter no vlan-aware.
Note: The VLAN aware mode
cannot be changed if bridge
port flows exist.
Displaying MAC address table show mac-address-table static

(static addresses, dynamic show mac-address-table dynamic
addresses, or all addresses)
show mac-address-table all
See Displaying MAC Table.
Searching MAC address table for show mac-table [vlan <vlan>] Vlan VLAN to search for
specific MAC address [mac-address <mac-address>] mac-address MAC address
to search for
Displaying VLAN information, show vlans Note: This command is

including which bridge ports available only if the bridge is
have been automatically added VLAN-aware.
as tagged VLAN members
8-10 Bridge ETX-2i

Configuring STP parameters at spanning-tree See Configuring Bridge-Level

the bridge level RSTP Parameters.
Configuring multicast snooping mld-snooping See MLD Snooping.

at the bridge level
Configuring Bridge Ports

The following commands are available in the port level, at the
config>bridge(1)>port(<port-number>)# prompt.
Assigning a name to the bridge name <port-name> To delete the bridge port
port name, enter no name.
Administratively enabling the no shutdown To administratively disable the

bridge port bridge port, enter shutdown.
Configuring STP parameters at spanning-tree See Configuring Bridge-Port-

the bridge port level Level RSTP Parameters.
Configuring VLAN
The following commands are available in the vlan level, at the
config>bridge(1)>vlan(<vlan-id>)# prompt.
Defining maximum MAC table maximum-mac-addresses <max-mac> Possible values: 032000

size supported by the VLAN When using the bridge VLAN
MAC table limitation
(maximum-mac-addresses
limit), the first packet of each
learned MAC address is
dropped.
Configuring VLAN to work in mode {e-tree | e-lan} If you change to E-Tree, you
E-Tree or E-LAN mode need to define a bridge port as
root.
ETX-2i Bridge 8-11

Configuring bridge port as root root <bridge-port number> Possible values: 116.
port in E-Tree mode no root < bridge-port_number> no root defines a bridge port
as a leaf in E-Tree mode.
Notes:
This command is available
only if the VLAN mode is
E-Tree.
Supports one root per VLAN
Supports more than one
root per VLAN; the number
of roots supported is
equivalent to the number of
bridge ports.

Configuring RSTP/MSTP
RSTP and MSTP are configured at the bridge and bridge-port levels.
Configuring Bridge-Level RSTP/MSTP Parameters
To configure the bridge-level RSTP/MSTP parameters:

In the config>bridge(bridge_number)# prompt, enter spanning-tree and
configure the bridge-level RSTP/MSTP parameters as illustrated and explained
below.
Configuring the amount of time forward-time <430> sec When configuring forwarding
a port remains in the listening time, follow this rule:
and learning states before 2 (forwarding time - 1) =>
entering the forwarding state maximum aging time
Defining how often ETX-2i hello-time <110> sec Limitation: Define hello-time
broadcasts hello messages to must be configured so that
other devices to indicate that 2 (hello-time - 1) <= max-
the bridge is alive age.
Defining maximum aging time for max-age <640> sec

spanning tree operation
Defining the number of hops in max-hops <640>

an MST region before the BDPU
is discarded and the port
information is aged out
Selecting spanning tree mode {rstp | mstp} MSTP-related parameters are

operation mode masked, when the bridge
operates in RSTP mode.
8-12 Bridge ETX-2i

Configuring bridge-level MST mst <14094> no mst (msti_number) deletes

instance level no mst MST instance.
See configuration instructions
below.
Specifying spanning tree priority priority <0, 4096, 8192, 12288, This is the value of the first
of the bridge 16384, 20480, 24576, 28672, 32768, two octets of the bridge ID. It
36864, 40960, 45056, 49152, 53248, is used to make the bridge
57344, 61440> more (or less) likely to be
chosen as the root bridge.
The lower the number, the
more likely the bridge will be
chosen as the root bridge.
Defining MSTP configuration name <string> For two or more bridges to be

name in the same MST region, they
must have the same
Defining MSTP configuration revision <065535>
configuration revision number
revision number
and name.
Displaying bridge-level spanning show status See Displaying Spanning Tree

tree status Status below.
Selecting the maximum number tx-hold-count <110> BPDUs per sec

of BPDUs that can be
transmitted to a port in one
second
To configure bridge-level MST instance:

In the config>bridge(bridge_number)>spanning-tree # prompt, enter mst
(msti_number) and configure the bridge-level MSTI parameters as illustrated
and explained below.
Specifying MSTI priority priority<0, 4096, 8192, 12288,

16384, 20480, 24576, 28672, 32768,
36864, 40960, 45056, 49152, 53248,
57344, 61440>
Mapping VLANs to MST instance vlan <14094> Map list of VLANS to MST
no vlan instance.
no vlan (vlan_lsit) removes
VLAN mapping from the MSTI.
This command can be repeated
to configure additional VLAN
mappings.
For two or more bridges to be
in the same MST region, they
must have the same VLAN-to-
MSTI mapping.
ETX-2i Bridge 8-13

Displaying bridge-level MSTI show status See Displaying Spanning Tree

status Status below.
Configuring Bridge-Port-Level RSTP/MSTP Parameters
To configure the bridge-port-level RSTP/MSTP parameters:

In the config>bridge(bridge_number)>port(port_number)# prompt, enter
spanning-tree and configure the bridge-port-level RSTP/MSTP parameters as
illustrated and explained below.
Defining bridge port as an edge admin-edge no admin-edge disables edge

port no admin-edge port functionality.
An edge port is put into the
forwarding state upon linkup,
for faster convergence.
An edge port connected to a
bridge could prevent the
spanning tree from detecting
and disabling loops.
Enabling/disabling automatic auto-edge no auto-edge disables

identification of edge ports no auto-edge automatic edge port
identification.
The edge status of an auto
edge port is automatically
disabled upon receiving a BPDU
(regardless of the configured
admin-edge value).
Defining port path cost cost <0200000000> If a loop occurs, the path cost
is used to select an interface
to place into the forwarding
state.
A lower path cost represents
higher speed links. It is
recommended to use the
default cost value (0) to let
ETX-2i to compute the best
possible cost according to the
link bandwidth (Table 8-44).
8-14 Bridge ETX-2i

Activating migration check by mcheck If a port connects to a bridge

the port running STP, this port
automatically migrates to the
STP-compatible mode, and
does not revert automatically
back to MSTP/RSTP mode.
mcheck forces protocol
renegotiation with neighboring
devices, to check if they are
MSTP/RSTP-compatible.
Configuring bridge-port-level mst <14094> no mst (msti_number) deletes

MSTI no mst MST instance.
See configuration instructions
below.
Defining bridge port priority port-priority <0, 16, 32, 48, 64, 80, This is the value of the first
96, 112, 128, 144, 160, 176, 192, octet of the bridge port ID. If a
208, 224, 240> loop occurs, the MSTP uses the
port priority, when selecting an
interface to put into the
forwarding state.
The lower the number, the
higher the port priority (the
lowest numbered port is
selected if a tie breaker is
needed).
Preventing/allowing bridge port restricted-role no restricted-role removes

to become a root port no restricted-role bridge port restriction.
Restricted port cannot become
a root port, even it is the most
likely candidate.
Enabling/disabling propagation restricted-tcn no restricted-tcn enables

of topology changes by the port no restricted-tcn propagation of topology
changes by the port.
A restricted-tcn port does not
propagate received topology
change notifications and
topology changes to other
ports.
Restricting propagation of
topology changes can be used
to prevent bridges external to a
network core influencing the
active spanning tree topology.
Usually, it is applied to bridges
which are not under the full
control of the network
administrator.
ETX-2i Bridge 8-15

Displaying bridge port spanning show status See Displaying Spanning Tree
tree status Status below.
Activating spanning tree on the shutdown shutdown disables spanning

bridge port no shutdown tree on bridge port.
Table 8-1. Bandwidth Values for Bridge Port Path Cost
Link Bandwidth Cost
<= 100 kbps 200 000 000
1 Mbps 20 000 000
10 Mbps 2 000 000
100 Mbps 200 000
1 Gbps 20 000
10 Gbps 2 000
100 Gbps 200
1 Tbps 20
10 Tbps 2
To configure bridge-port-level MST instance:

In the config>bridge(bridge_number)>port(port_number)>spanning-tree #
prompt, enter mst (msti_number) and configure the bridge-level MSTI
parameters as illustrated and explained below.
Defining MSTI port path cost cost <0200000000>
Specifying MSTI port priority port-priority <0, 16, 32, 48, 64, 80,
96, 112, 128, 144, 160, 176, 192,
208, 224, 240>
Displaying bridge-port-level MSTI show status See Displaying Spanning Tree

status Status below.
Displaying Spanning Tree Status

You can display spanning tree status at the following levels:
Bridge
Bridge MSTI
Bridge port
Bridge port MSTI
8-16 Bridge ETX-2i

To display spanning tree status:

At the relevant prompt (bridge, bridge MSTI, bridge port, bridge port MSTI),
type show status.
One of the following status screens is displayed.
Mode MSTP, Root, Regional Root
Bridge: Priority 32768, Address 00:11:22:33:44:55
Root: Priority 32768, Address 00:11:22:33:44:55,
Cost 012, Port 1 (Eth 1/2)
Regional Root: Priority 32768, Address 00:11:22:33:44:55, cost
012
Configured Times:
Max Age 01, Hello 01, Forward Delay 01
Actual Times:
Max Age 01, Hello 01, Forward Delay 01, Hold 01
Topology Change Total 012, Since Last 2 days 00:11:22
Figure 8-6. Spanning Tree Status, Bridge Level
MST Instance 1, Root

VLANs Mapped 1-10, 20
Bridge: Priority 32768, Address 00:11:22:33:44:55, Root
Root: Priority 32768, Address 00:11:22:33:44:55
Cost 32768, Port 1 (Eth1/1)
Topology Change: Total 1234, Since Last 2 days 22:11:00
BP Interface Role State

-- --------- ---------- ----------
01 Eth1/1 Backup Blocking
02 Eth1/2 Designated Forwarding
Figure 8-7. Spanning Tree Status, Bridge MSTI Level
Port 1 (Eth1/1), Root, Forwarding, Edge (default)

Path Cost 200000000, Priority 128, Up 2 days 00:11:22
Designated Root: Priority 32768, Address 00:11:22:33:44:55
Designated Bridge: Priority 32768, Address 00:11:22:33:44:55
Port 1, Port Priority 128, Cost 200000000
Regional Root: Priority 32768, Address 00:11:22:33:44:55, Cost 200000000
Hello Timer 10
Forward Transitions: 11
Figure 8-8. Spanning Tree Status, Bridge Port Level
Port 1 (Eth1/1), MSTI 1000, Root, Forwarding, Edge (default)

Up 2 days 22:11:00
VLANs mapped 1-20, 100
Designated Root: Priority 32768, Address 00:11:22:33:44:55, Port 10
Regional Root: Priority 32768, Address 00:11:22:33:44:55, Cost 200000000
Figure 8-9. Spanning Tree Status, Bridge Port MSTI Level
Configuring BPDU Peers

When configuring RSTP/MSTP, attach L2CP profile directly to the physical port,
with MAC 0x00 and action set to peer.
The following example shows the necessary configuration.
ETX-2i Bridge 8-17

To configure an L2CP profile for MAC 0x00 with peer action:

ETX-2i >config>port# l2cp-profile RSTP
ETX-2i >config>port>l2cp-profile RSTP# mac 0x00 peer
exit
Examples
VLAN-Aware Bridge
VLAN-aware bridge, with bridge ports 14
VLAN 51 used for management, in E-LAN mode
VLAN 100 used for traffic, in E-Tree mode, with root bridge port 2
VLAN 200 used for traffic, in E-LAN mode
Management flows (unidirectional) between SVI 1 and bridge port 1
Traffic flows (bidirectional) between:
Ethernet port 1/1 and bridge port 2, with classification VLAN 100 and
VLAN 200
Ethernet port 0/3 and bridge port 3, with classification VLAN 100
Ethernet port 0/4 and bridge port 4, with classification VLAN 100
#*******Configure SVI
no shutdown
exit all
#*******Configure bridge
configure bridge 1
vlan-aware
#*******Configure bridge ports

port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
no shutdown
exit
port 4
no shutdown
exit
#*******Configure VLANs
vlan 51
exit
vlan 100
mode e-tree
8-18 Bridge ETX-2i

root 2
exit
vlan 200
exit all
#*******Configure classifier profiles

configure flows
classifier-profile 51 match-any
match vlan 51
exit
match vlan 100
exit
match vlan 200
exit
classifier-profile unt match-any
match untagged
exit
#*******Configure management flows

flow mng_in
classifier 51
egress-port svi 1 queue 0
no policer
no shutdown
exit
flow mng_out
classifier unt
ingress-port svi 1
no shutdown
exit
#*******Configure management flow to physical port

flow 1toBP2_51
classifier 51
no shutdown
exit
#*******Configure bidirectional traffic flows

flow 1toBP2_100
classifier 100
no shutdown
exit
ETX-2i Bridge 8-19

flow 1toBP2_200
classifier 200
no shutdown
exit
flow 3toBP3_100
classifier 100
no shutdown
exit
flow 4toBP4_100
classifier 100
no shutdown
exit all
#*******Configure router interface

configure router 1
interface 1
address 10.10.10.20/24
bind svi 1
dhcp-client
client-id mac
exit
no shutdown
exit all
save
Displaying VLAN Information

This section illustrates displaying VLAN information after performing the
configuration specified in VLAN-Aware Bridge. The VLAN information shows the
following:
VLAN 51 Bridge ports 12 were automatically added as tagged

ports.
VLAN 100 Bridge ports 24 were automatically added as tagged

ports.
VLAN 200 Bridge port 2 was automatically added as a tagged port.

ETX-2i# configure bridge 1
ETX-2i>config>bridge(1)# show vlans
VLAN ID : 51
Tagged Ports : 1..2

Untagged Ports : 0
8-20 Bridge ETX-2i

VLAN ID : 100
Tagged Ports : 2..4

Untagged Ports : 0
VLAN ID : 200
Tagged Ports : 2
Untagged Ports : 0
VLAN-Unaware Bridge
VLAN-unaware bridge, with bridge ports 14
Traffic flows (unidirectional), with classification to match all, between:
Ethernet port 0/1 and bridge port 2
configure bridge 1
no vlan-aware

port 1
no shutdown
exit
port 2
no shutdown
exit
port 3
no shutdown
exit
port 4
no shutdown
exit all
#*******Configure classifier profile

configure flows
match all
exit
#*******Configure unidirectional traffic flows

flow 1toBP2
class all
no shutdown
exit
ETX-2i Bridge 8-21

flow BP2to1
class all
egress-port ethernet 0/1 block 0/1
no policer
no shutdown
exit
flow 3toBP3
class all
no shutdown
exit
flow BP3to3
class all
no policer
no shutdown
exit
flow 4toBP4
class all
no shutdown
exit
flow BP4to4
class all
no policer
no shutdown
exit
Creating Static MAC Address

This section illustrates creating a static MAC address after performing the
configuration specified in VLAN-Aware Bridge.
exit all
configure bridge 1
static-mac 100 01-02-03-04-05-06 2
exit all
Displaying MAC Table

You can display an ETX-2i MAC table, which provides information on static and
dynamic addresses, and the bridge ports and VLANs associated with them.
8-22 Bridge ETX-2i

To display MAC address table:

At the config>bridge(bridge_number)# prompt, enter show mac-address-table
{static | dynamic | all}.
The MAC address table is displayed.
Note ETX-2i displays only the first 1000 entries. To view the entire MAC table,
download it to your PC, using SFTP. See File Operations in Chapter 10.
ETX-2i# configure bridge 1

ETX-2i>config>bridge(1)# show mac-address-table all
Total MAC Addresses : 22
Static MAC Addresses : 12
Dynamic MAC Addresses : 10
VLAN MAC Address Port Status

---------------------------------------------------------------
20 00-00-00-00-00-01 2 Static
40 00-00-00-00-00-01 2 Static
50 00-00-00-00-00-01 2 Static
60 00-00-00-00-00-01 2 Static
60 00-00-00-00-00-E1 7 Dynamic
100 00-00-00-00-00-E1 7 Dynamic
100 01-02-03-04-05-06 2 Static
130 00-00-00-00-00-E1 7 Dynamic
150 00-00-00-00-00-E1 7 Dynamic
160 00-00-00-00-00-E1 7 Dynamic
170 00-00-00-00-00-01 2 Static
180 00-00-00-00-00-01 2 Static
190 00-00-00-00-00-01 2 Static
200 00-00-00-00-00-01 2 Static
200 00-00-00-00-00-E1 7 Dynamic
230 00-00-00-00-00-E1 7 Dynamic
250 00-00-00-00-00-E1 7 Dynamic
260 00-00-00-00-00-E1 7 Dynamic
270 00-00-00-00-00-01 2 Static
280 00-00-00-00-00-01 2 Static
290 00-00-00-00-00-01 2 Static
290 00-00-00-00-00-E1 7 Dynamic
8.2 Classification by Port/Flow

Traffic is classified into flows, which are unidirectional or bidirectional entities
that connect two physical or logical ports. ETX-2i supports the following port-
level classification mechanisms:
Flow classification (see Flow Classification)
Port Classification (see Port Classification)
ETX-2i Classification by Port/Flow 8-23

If flow classification and port classification are configured for a port, the port
classification takes precedence over the flow classification.
Applicable Products
Pseudowire (PW) is relevant to devices that support smart SFP MiTOP
functionality.
D-NFV is relevant only for ETX2i with a D-NFV option.
Standards
IEEE 802.1ad, IEEE 802.1Q
Benefits
User traffic can be classified into different Ethernet flows (EVC.CoS) to provide
services in a flexible manner. With port classification, you can maintain network
security by preventing malicious traffic from being forwarded by the port, as well
as save network resources by dropping unwanted packets.
Ethernet flows are unidirectional, or bidirectional in the case of bridge flows. For
unidirectional flows, you have to define two flows between the two ports, one
for each direction. For bidirectional flows, you only need to define one flow from
a port to a bridge port, and specify the reverse-direction command.
Flow Classification
The ingress traffic is first classified into flows according to classification profiles.
The classification is per port and is applied to the ingress port of the flow.
Packets can be classified by means of their VLAN IDs and other criteria, fully
specified in Configuring a Classifier Profile.
In the following descriptions, VLAN refers to the service provider (outer) VLAN,
sometimes referred to as SP-VLAN, while inner VLAN refers to the Customer
Entity VLAN, sometimes referred to as CE-VLAN or C-VLAN.
Flow classifications that apply to the same port are allowed in the combinations
shown in Table 8-7. The priority shown is used to determine which classification
is used if incoming packets for the port fit the criteria of more than one
classification. Priority 4 is the lowest, priority 1 is the highest. NNI indicates
ingress network port, UNI indicates ingress user port.
8-24 Classification by Port/Flow ETX-2i

Table 8-2. Flow Classification Combinations
Classification Other Classifications Allowed On Range Max Number Priority NNI/UNI

Same Ingress Port Ranges
Unclassified VLAN 1 4 Both

(all-to-one VLAN + IP precedence
bundling) VLAN + DSCP
VLAN + VLAN priority
VLAN + Non-IP
VLAN priority
IP precedence
DSCP
Source MAC address
Destination MAC address
My-MAC
Source IP address
Destination IP address
My-IP
Non-IP
Untagged
VLAN VLAN + VLAN priority 04094 30 2 Both
See Note 1 VLAN + IP precedence
VLAN + DSCP
VLAN + source MAC address
VLAN + destination MAC address
VLAN + source IP address
VLAN + destination IP address
VLAN + inner VLAN
VLAN + VLAN priority + inner VLAN
Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Untagged
VLAN + VLAN VLAN 04094 + 07 30 2 Both

priority VLAN + source MAC address
See Note 1 VLAN + destination MAC address
VLAN + inner VLAN
Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Untagged


VLAN + IP VLAN 04094 + 07 30 2 Both

precedence Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Non-IP
Untagged
VLAN + DSCP VLAN 04094 + 063 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Unclassified
Non-IP
Untagged
VLAN + source MAC VLAN 04094 + One VLAN value 1 Both

address VLAN + VLAN priority MAC address + one MAC
VLAN + inner VLAN address range
VLAN + destination VLAN 04094 + One VLAN value 1 Both

MAC address VLAN + VLAN priority MAC address + one MAC
VLAN + inner VLAN address range
VLAN + source VLAN 04094 + 10 VLAN 2 Both

IP address VLAN + VLAN priority IP address value + IP
VLAN + inner VLAN address/range
VLAN + inner VLAN + VLAN priority
VLAN + destination VLAN 04094 + 10 VLAN 2 Both

IP address VLAN + VLAN priority IP address value + IP
VLAN + inner VLAN address/range
VLAN + inner VLAN + VLAN priority
VLAN + inner VLAN VLAN Single value for 30 (for inner 3 Both
VLAN + VLAN priority VLAN and range range)
VLAN + VLAN priority + inner VLAN for inner VLAN
VLAN + source MAC address


VLAN + inner VLAN VLAN Single value for 30 (for inner 3 Both
+ VLAN priority VLAN + inner VLAN VLAN and range range)
VLAN + source MAC address for inner VLAN
VLAN + inner VLAN VLAN + inner VLAN Single value for 10 for inner 2 Both
+ DSCP VLAN +inner VLAN + non IP VLAN and range VLAN
VLAN + DSCP for inner VLAN 1 for DSCP
VLAN + non IP and DSCP
Untagged
VLAN + inner VLAN VLAN + inner VLAN Single value for 10 (for inner 1 Both
+ non IP VLAN +inner VLAN + DSCP VLAN and range range)
VLAN + DSCP for inner VLAN
VLAN + non IP
Untagged
VLAN + non-IP Unclassified 04094 30 1 Both

VLAN
VLAN + IP precedence
VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP
Untagged
VLAN priority Unclassified 07 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Untagged
IP precedence Unclassified 07 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Non-IP


DSCP Unclassified 063 30 2 Both

Source MAC address
My-MAC
Source IP address
My-IP
Non-IP
Source MAC address VLAN MAC address 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Destination MAC VLAN MAC address 1 1 Both

address VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
My-MAC
Unclassified
Non-IP
Untagged
My-MAC VLAN 1 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged


Source IP address VLAN IP address 10 1 Both

See Note 2 VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Destination VLAN IP address 10 1 Both

IP address VLAN priority
See Note 2 VLAN + VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
My-IP
Unclassified
Non-IP
Untagged
My-IP VLAN 1 1 1 Both

VLAN priority
VLAN + DSCP
VLAN + Non-IP
IP precedence
DSCP
Unclassified
Non-IP
Untagged
Non-IP Unclassified 1 1 Both

VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP


Untagged Unclassified 1 2 Both

VLAN
VLAN priority
VLAN + DSCP
Source MAC address
My-MAC
Source IP address
My-IP
Note 1
If you combine the classifications VLAN and VLAN + VLAN priority, the VLANs must
be different.
For example, the following combination is not allowed:
VLAN 100
VLAN 100 + p-bit 5
The following combination is allowed:
VLAN 100
VLAN 200 + p-bit 5
You can achieve the combination VLAN 100 and VLAN 100 + p-bit 5 via the
following:
VLAN 100 + p-bit 04, 67
VLAN 100 + p-bit 5
You cannot create flows with VLAN classification overlap.
For example, the following combination is not allowed:
VLAN 100..300 + p-bit 3
VLAN 200 + p-bit 4
A sanity check detects that VLAN 200 is in the range 100-300 (i.e. VLAN
overlap), and does not allow this configuration.
Note 2 If you apply two classification profiles with IP address ranges to a port, the
profiles must have the same mask.
For example:
The following is valid (mask1 equal to mask2):
Classification #1: 10.10.0.0 10.10.0.255 -> mask1 = 255.255.255.0
The following is invalid (mask1 not equal to mask2):
Classification #1: 10.10.0.00.10.0.255 -> mask1 = 255.255.255.0
Classification Keys
The following classification keys are supported per port:

Legacy
VLAN
VLAN Inner VLAN
Table 8-9 and Table 8-10 show for the VLAN and VLAN Inner VLAN classification
keys, respectively, the queue mapping method and the parameters that can be
configured in a flow, the range per classification rule, maximum number of rules
per flow, and the internal flow priority. See Table 8-7 for the combinations of
flow classifications that are allowed per port.
Table 8-3. Queue Mapping Method and Configurable Flow Classification Parameters VLAN
Classification Key
Queue/Priority Classification Profile Parameter Range (per defined Max. # of Internal

Mapping Method classification rule) Rules per Flow Flow
priority
1. Flow Untagged NA 1 3
2. DSCP Unclassified NA 1 2
3. P-bit
VLAN VLAN range [0..4094] 30 2
VLAN+P-bit VLAN range [0..4094]; 30 2
P-bit range [0..7]
VLAN+DSCP VLAN range [0..4094]; 30 2A
DSCP range [0..63]
VLAN+IP-P VLAN range [0..4094]; 30 2A
IP-P range [0..7]
VLAN+MAC SA Single VLAN value 1 1
SA MAC range
VLAN+MAC DA Single VLAN value 1 1
DA MAC range
VLAN+IP SA VLAN range [0..4094], 10 1
SRC IP
VLAN+IP DA VLAN range [0..4094], 10 1
Dest IP
VLAN+Ethertype Single VLAN value and 1 1
single Ethertype value
VLAN+Non IP VLAN Range [0..4094] 30 2
MAC SA SA MAC Range 1 1
MAC DA DA MAC Range 1 1
IP SA SRC IP Range 1 1
IP DA DST IP Range 1 1
Ethertype Single VLAN value 1 1
Non IP NA 1 2

Table 8-4. Queue Mapping Method and Configurable Flow Classification Parameters VLAN Inner
VLAN Classification Key
Queue/Priority Classification Profile Range (per defined Max. # of Internal

Mapping Method Parameter classification rule) Rules per Flow Flow
priority
4. Flow Untagged NA 1 3
5. DSCP Unclassified NA 1 2
6. P-bit
VLAN, Inner VLAN Single Outer value 30 2
Inner VLAN range
[0..4094]
VLAN, Inner VLAN, p-bit Single Outer value 30 2
Inner VLAN range
[0..4094]
P-bit range [0..7]
VLAN, Inner VLAN, DSCP Single Outer value 30 2
Inner VLAN range
[0..4094]
DSCP range [0..63]
VLAN, Inner VLAN, non IP VLAN range [0..4094] 30 2
VLAN (one tag level only) VLAN range [0..4094] 30 2
MAC SA SA MAC range 1 1
MAC DA DA MAC range 1 1
IP SA SRC IP range 1 1
IP DA DST IP range 1 1
Ethertype Single VLAN value 1 1
Non IP NA 1 2
VLAN Actions
You can perform marking and tagging actions on the outer and inner VLAN such
as adding, replacing, or removing, as well as marking with p-bit. Only certain
combinations of actions on the outer and inner VLAN are allowed. If no action is
performed for the outer VLAN, then for the inner VLAN there must be no action
performed. Table 8-11 shows valid action combinations on ingress frame tags
and the resulting egress frame tags and p-bits, according to whether the ingress
frame is untagged, contains one VLAN, or is double-tagged. Any combination not
shown in the table is not supported.
In the ETX-2i bridge, if one of the bridge ports is configured with VLAN
classification, and another bridge port with VLAN + p-bit classification, in order to
mark the p-bit of the inner VLAN, you must mark the required p-bit at the VLAN +
p-bit bridge port.

Table 8-5. Valid VLAN Action Combinations
Action on: Egress VLAN(s) and P-bit(s) for Ingress Frame Types:
Outer VLAN Inner VLAN Untagged One VLAN (X) Double VLANs
(X and Y)
None None Untagged X X, Y

Pop None Not applicable Untagged Y
unsupported
Pop Mark with VLAN A Not applicable Not applicable A
unsupported unsupported
Pop Pop Not applicable Not applicable Untagged
unsupported unsupported
Push VLAN A None A A, X A, X, Y
Push VLAN A Mark with VLAN B A A, B A, B, Y
Push VLAN A Mark with p-bit D A A A,
X + p-bit D X + p-bit D,
Y
Push VLAN A Mark with profile F A A, A,
See Note 1 X + p-bit according X + p-bit according
to F to F,
Y
Push VLAN A. Push VLAN B, A + p-bit 7 A + p-bit according A + p-bit according
mark with profile E mark with p-bit D according to E, to E, to E,
B + p-bit D B + p-bit D, B + p-bit D,
X X,
Y
Push VLAN A. Push VLAN B, A + p-bit C, A + p-bit C, A + p-bit C,
mark with p-bit C mark with p-bit D B + p-bit D B + p-bit D, B + p-bit D,
X X,
Y
Push VLAN A. Push VLAN B. A + p-bit 7 A + p-bit according A + p-bit according
mark with profile E mark with profile F according to E, to E, to E,
See Note 1 B + p-bit 7 B + p-bit according B + p-bit according
according to F to F, to F,
X X,
Y
Push VLAN A. Push VLAN B. A + p-bit C, A + p-bit C, A + p-bit C,
mark with p-bit C mark with profile F B + p-bit 7 B + p-bit according B + p-bit according
according to F to F, to F,
X X,
Y
Mark with VLAN A None Untagged A A, Y
Mark with VLAN A Mark with p-bit D Not applicable Not applicable A,
unsupported unsupported Y + p-bit D

Action on: Egress VLAN(s) and P-bit(s) for Ingress Frame Types:
Outer VLAN Inner VLAN Untagged One VLAN (X) Double VLANs
(X and Y)
Mark with p-bit C Mark with p-bit D Not applicable Not applicable X+ p-bit C,
unsupported unsupported Y + p-bit D
Mark with VLAN A Mark with p-bit D Not applicable Not applicable A + p-bit,
+ p-bit unsupported unsupported Y + p-bit D
Mark with VLAN A Mark with VLAN B Not applicable Not applicable A + p-bit according
+ profile E +p-bit D unsupported unsupported to E,
B +p-bit D
Permanent Flow Loopbacks

You can set up a permanent flow loopback by specifying MAC and IP address
swap for flow traffic in the marking context, and saving it as part of the
configuration.
Unidirectional Hubs
You can configure a unidirectional hub (UDH) by defining a group of flows with
the same ingress port, classifier profile, and policer aggregate, and different
egress ports. The egress ports must be physical Ethernet ports, not virtual ports
such as SVI, ETP, etc. Only one queue-mapping profile and one marking profile
can be used for the flows in a UDH group, however VLAN tag editing can be
different in the different flows.
In unidirectional hub mode, the rate of each flow that is part of the group cannot
exceed the rate of the queue with the lowest rate, therefore it is not possible to
use different rates for different p-bits.
Multi-CoS Flows
A multi-CoS flow per MEF 10.3 contains multiple classes of service. It can be
assigned an envelope policer (see Envelope Bandwidth Profiles) to enable sharing
bandwidth between the CoSs, where each CoS is assigned a rank. Alternatively, if
bandwidth policing is not required but per-CoS counters are required.you can
specify that a multi-CoS flow has per-CoS counters.
Figure 8-10. Multi-CoS Flow
The CoS-to-rank mapping is done automatically by the device, according to the

CoSs that are configured in the assigned envelope policer. CoS 0 is mapped to
the highest rank needed for the number of configured CoSs, then CoS 1 is

mapped to the next highest rank, ending with mapping the last configured CoS to
1. For example, if CoS 1, CoS 5, and CoS 6 are configured, then three ranks are
used, and the mappings are:
CoS 1 to rank 3
CoS 5 to rank 2
CoS 6 to rank 1
Traffic that is mapped to a CoS that does not correspond to a CoS configured in
the envelope profile is dropped (the port-level counter Unmapped CoS Frames
indicates how many frames were dropped for this reason).
Multi-CoS flows must be assigned a CoS mapping profile, which can be used to
specify the mapping of untagged traffic to CoS in case of p-bit method, or non IP
to CoS in the case of DSCP.
Multi-CoS flows support only the following ingress/egress ports:
Ingress and egress port are Ethernet or logical MAC.
Egress port is bridge port (unidirectional and reverse flows supported).
Egress port is ETP subscriber or transport port.
The queue block mapping for the egress port in a multi-CoS flow is done as CoS
to queue mapping as follows: Cos 0 to queue 0, Cos 1 to queue 1, CoS 2 to
queue 2, etc. There is a predefined queue map profile with this mapping, with the
reserved name q-map-for-cos. This profile cannot be modified.
If a marking profile is assigned to a multi-CoS flow, it must be type CoS to p-bit.
Port Classification
You can define port classification to flexibly filter packet forwarding for ports.
Port classification consists of a set of sequentially numbered rules (similar to
ACLs), with the following rule types:
Comment Text used for commenting and visually organizing the rules.
Match Specifies the criteria for forwarding packets, as well as a flow
attribute and optional CoS (required for Multi-CoS MEF 10.3 flows)
Drop Specifies the criteria for dropping packets
The following table specifies the criteria.
Table 8-6. Port Classification Criteria
Rule Criterion Rule Value/Range Comments
Any - Allows match any or drop any rules
Destination MAC address Value
Source MAC address Value
Ethertype Value
VLAN Range [04094]
P-bit Value [07]

Rule Criterion Rule Value/Range Comments
DEI 0 or 1
Inner Ethertype Value
Inner VLAN Range [04094]
Inner p-bit Value [07]
IP DSCP Range [063]
IP precedence Range [07]
ToS Range [0255]
IP protocol Value
Source IP address IP address/length IPv4 or IPv6
Destination IP address IP address/length IPv4 or IPv6
TCP Source Port Range IP Layer 4
TCP Destination Port Range IP Layer 4
UDP Source Port Range IP Layer 4
UDP Destination Port Range IP Layer 4
Ethertype
Ingress packets are identified as outer VLAN-tagged packets if the packet outer
tag Ethertype equals the port configured Ethertype 0x811, 0x88a8, or one of
the two user-configurable global Ethertype values.
Ingress packets are identified as outer VLAN-tagged packets if the packet inner
tag Ethertype equals 0x811, 0x88a8, or one of the two user-configurable global
Ethertype values.
If the packet inner and outer tag Ethertypes do not meet these criteria, the
packet is treated as untagged.
Factory Defaults
By default, no flows or port classifiers are configured.
Configuring a Classifier Profile

You can define classifier profiles to apply to flows for flow classification.
Note Classifier profiles are not used for flows that are defined with the port
classification attribute.

Note When a classification profile is assigned to a flow, each match in the profile is
allocated one of the available internal classification match entries, according to
the flow ingress port.
For example, if a classification profile is defined with matches to two different
VLANS, then if the profile is assigned to two flows that use different ingress
ports, the result is that four internal classification match entries are allocated. If
the profile is assigned to two flows that use the same ingress port, the result is
that two internal classification match entries are used.
To define a classifier profile:

1. Navigate to the flows context (config>flows).
2. Define a classifier profile and assign a name to it:
classifier-profile <profile-name> match-any
The system switches to the context of the classifier profile
(config>flows>classifier-profile(<profile-name>)).
3. Specify the criteria for the classifier profile:
[no] match [vlan <vlan-range>] [inner-vlan <inner-vlan-range>]
[p-bit <p-bit-range>] [ip-precedence <ip-precedence-range>]
[ip-dscp <ip-dscp-range>] [src-mac <src-mac-low>]
[to-src-mac <src-mac-high>] [dst-mac <dst-mac-low>]
[to-dst-mac <dst-mac-high>] [src-ip <src-ip-low>] [to-src-ip <src-ip-high>]
[dst-ip <dst-ip-low>] [to-dst-ip <dst-ip-high>] [ether-type <ether-type>]
[untagged] [non-ip] [my-mac] [my-ip] [all]
Note Using the matching type my-mac or my-ip is equivalent to using the matching
type dest-mac <device-MAC-address> or dest-ip <host-IP-address>.
4. When you have completed specifying the criteria, enter exit to exit the
classifier profile context.
Configuring Flows
Note If the flow is being used for port classification (see Port Classification), it inherits
the ingress port from the port classification, and does not use a classifier profile.
To configure flows:
1. Navigate to config>flows.
2. Enter:
flow <flow-name> [port-classifier]
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.
If port-classifier is specified, this flow is used for port classification, and
the commands ingress-port, classifier, reverse-direction, and
cos-mapping are not used.

Associating the flow with a classifier <classifier-profile-name> If the flow is multi-CoS, the
classifier profile classification must be one of the
following:
VLAN, VLAN + inner VLAN, VLAN
range
Match all
Untagged
This command cannot be used if
port-classifier was specified for the
flow.
Associating multi-CoS flow with cos-mapping-profile <cos-mapping-profile-name> This command cannot be used if
CoS mapping profile port-classifier was specified for the
flow.
Discarding traffic transmitted via drop

the flow
Specifying the ingress packet ingress-color green You can set the packet color to
color ingress-color yellow green or yellow, or use a color
mapping profile (see Color Mapping
ingress-color profile <color-mapping-profile-name>
Profiles).
Specifying the ingress port ingress-port ethernet [<slot>/]<port> This command cannot be used if
ingress-port bridge-port <bridge-number> port-classifier was specified for the
<bridge-port-number> flow.
ingress-port etp <etp-name> {subscriber | transport} Note: If working with PW, packets
<port-number> forwarded to the SVI must be
ingress-port logical-mac <port> untagged, and pop any VLAN.
ingress-port pcs <port>

ingress-port svi <port>

Specifying the egress port, and egress-port ethernet [<slot>/]<port> [queue If a queue mapping profile is used,
defining queue <queue-id> block <level-id/queue-id>] it must be compatible with the
egress-port ethernet [<slot>/]<port> classification criteria of the flow,
[queue-map-profile <queue-map-profile-name> e.g. if the classification is according
block <level-id/queue-id>] to DSCP then the queue mapping
should not be according to p-bit.
egress-port ethernet <port> [block <level-id/queue-id>]
egress-port bridge-port <bridge-number> For multi-CoS flows, the predefined
<bridge-port-number> [cos <cos-id>] q-map-for-cos queue mapping
profile should be used.
egress-port bridge-port <bridge-number>
<bridge-port-number> [cos-map-profile Note: If working with PW, packets
<cos-map-profile-name>] forwarded from the SVI must be
untagged or match all, and push
egress-port etp <etp-name> {subscriber | transport}
any necessary VLAN.
<port-number> [cos <cos-id>]
egress-port etp <etp-name> {subscriber | transport}
<port-number> [cos-map-profile
<cos-map-profile-name>]
egress-port logical-mac <port> [queue <queue-id>
block <level-id/queue-id>]
egress-port logical-mac <port> [queue-map-profile
<queue-map-profile-name> block <level-id/queue-id>]
egress-port logical-mac <port>
[block <level-id/queue-id>]
egress-port pcs <port> [queue <queue-id>
block <level-id/queue-id>]
egress-port pcs <port> [queue-map-profile
<queue-map-profile-name> block <level-id/queue-id>]
egress-port pcs <port> [block <level-id/queue-id>]
egress-port svi <port> [queue <queue-id>]
egress-port svi <port> [queue-map-profile
<queue-map-profile-name>]
Associating a Layer-2 control l2cp profile <l2cp-profile-name> L2CP profile can be attached only
processing profile with the flow to flows with the following
classification types:
VLAN/VLAN+P-bit
Outer+Inner VLAN / Outer +P-bit
+ Inner VLAN
P-bits
VLAN+Non IP
Untagged
Defining marking actions for the mark all See the following table for the
flow such as overwriting the VLAN marking actions.
ID or inner VLAN ID or setting the
priority, or specifying MAC and IP
address swap

Specifying that the flow is a multi-cos-counters <cos-list> <cos-list> is the list of CoS values
multi-CoS flow with counters for for the flow; the list can be a range
the multiple CoSs such as 1..3 or a list of values such
as 2,4,5
You can assign either multiple CoS
counters or an envelope policer to
a multi-CoS flow; you cannot assign
both.
Configuring collection of pm-collection interval <seconds> Note: In addition to enabling PM

performance management statistics collection for the flow, it
statistics for the flow, that are must be enabled for the device.
presented via the RADview Refer to the Performance
Performance Management portal Management section in the
Monitoring and Diagnostics chapter
for details.
Associating regular flow with a policer profile <policer-profile-name> Note: You cannot assign a policer
non-envelope policer profile or policer aggregate <policer-aggregate-name> profile to a flow with a bridge port
policer aggregate as ingress port.
Associating multi-CoS flow with policer envelope <policer-profile-name> You can assign either an envelope
envelope policer policer or multiple CoS counters to
a multi-CoS flow; you cannot assign
both.
Measuring data rate and line rate rate-measure interval <seconds> Possible values: 10300
of flow See Viewing Flow Data Rate and
Line Rate for details.
Defining flow to bridge port as reverse-direction block <queue-block-id> Note: This command is allowed only
bidirectional, if bridge is if port classifier was not specified
VLAN-aware for the flow, the bridge is
VLAN-aware, and the egress port is
a bridge port.
Assigning service name to flow for service-name <name> The flows that belong to the same
its subsequent discovery by service must be tagged in both
RADview directions.
Displaying measured flow data show rate See Viewing Flow Data Rate and
rate and line rate Line Rate for details.
Displaying flow status show status Fault propagation actions are
visible only for flows configured
with fault propagation and
activated fault propagation license.
See Viewing Flow Status.

Specifying whether transmitted statistics-count-oam Enter no statistics-count-oam if

and received OAM packets are you do not want to include
included in the statistics counters transmitted and received OAM
for Rx and Tx statistics packets in the statistics; this
applies to the following OAM
packets:
AIS
CCMs
DMM/DMRs
LMM/LMRs
LBM/LBRs
LTM/LTRs
Port status TLV
Adding VLAN ID with p-bit set to vlan-tag push vlan <sp-vlan> p-bit fixed <fixed-p-bit> Inner-ether-type can be configured
specific value, and optionally [inner-vlan <inner-sp-vlan>[inner-ether-type to one of the four global device
adding inner VLAN ID with <inner-ether-type>] p-bit fixed <inner-fixed-p-bit>] level Ethertypes (see Ethertype
Ethertype (optional) and with section in Chapter 6).
p-bit set to specific value If not configured, the inner
Ethertype is set to 0x8100.
specific value, and optionally [inner-vlan <inner-sp-vlan> [inner-ether-type to one of the four global device
adding inner VLAN ID with <inner-ether-type>] level Ethertypes (see Ethertype
Ethertype (optional) and with p-bit profile <inner-marking-profile-name>] section in Chapter 6).
p-bit set via marking profile If not configured, the inner
specific value, and optionally [inner-vlan <inner-sp-vlan> [inner-ether-type to one of the four global device
adding inner VLAN ID with <inner-ether-type>] p-bit copy] level Ethertypes (see Ethertype
Ethertype (optional) and with section in Chapter 6).
p-bit set by copying from the If not configured, the inner
incoming frame Ethertype is set to 0x8100.
Adding VLAN ID with p-bit set via vlan-tag push vlan <sp-vlan> Inner-ether-type can be configured
marking profile, and optionally p-bit profile <marking-profile-name> to one of the four global device
adding inner VLAN ID with [inner-vlan <inner-sp-vlan> [inner-ether-type level Ethertypes (see Ethertype
Ethertype (optional) and with <inner-ether-type>] p-bit fixed <inner-fixed-p-bit>] section in Chapter 6).
p-bit set to specific value If not configured, the inner
Ethertype (optional) and with <inner-ether-type>] section in Chapter 6).
p-bit set via marking profile p-bit profile <inner-marking-profile-name>] If not configured, the inner

Ethertype (optional) and with <inner-ether-type>] p-bit copy] section in Chapter 6).
p-bit set by copying from the If not configured, the inner
Adding VLAN ID with p-bit set by vlan-tag push vlan <sp-vlan> p-bit copy Inner-ether-type can be configured
copying from the incoming frame, [inner-vlan <inner-sp-vlan> [inner-ether-type to one of the four global device
and optionally adding inner VLAN <inner-ether-type>] p-bit fixed <inner-fixed-p-bit>] level Ethertypes (see Ethertype
ID with Ethertype (optional) and section in Chapter 6).
with p-bit set to specific value: If not configured, the inner
and optionally adding inner VLAN <inner-ether-type>] level Ethertypes (see Ethertype
ID with Ethertype (optional) and p-bit profile <inner-marking-profile-name>] section in Chapter 6).
with p-bit set via marking profile If not configured, the inner
and optionally adding inner VLAN <inner-ether-type>] p-bit copy] level Ethertypes (see Ethertype
ID with Ethertype (optional) and section in Chapter 6).
with p-bit set by copying from the If not configured, the inner
Removing VLAN ID, and optionally vlan-tag pop vlan [inner-vlan]

removing inner VLAN ID
Removing pushing of inner VLAN no vlan-tag [push inner-vlan]
Displaying the flow statistics show statistics running See Viewing Flow Statistics.
Administratively enabling the flow no shutdown You can activate a flow only if it
is associated with at least a
classifier profile, ingress port,
and egress port.
A flow from a bridge port to a
physical port cannot be
activated if another flow from
the same bridge port, in the
same VPN, exits to a different
egress cluster (physical port and
queue block). This applies to
unidirectional flows and to the
reverse direction of bidirectional
flows.
Type shutdown to disable the
flow.

The following marking actions can be performed in the mark level, at the
config>flows>flow(<flow-name>)>mark# prompt.
Specifying permanent flow ip swap

loopback with IP address swap
Specifying permanent flow mac swap

loopback with MAC address swap
Overwriting p-bit according to marking-profile <marking-profile-name> If a marking profile is used, it must
marking profile be compatible with the classification
criteria of the flow, e.g. if the flow
classification is according to DSCP
then the marking classification
should not be according to p-bit.
If the flow is multi-CoS, the marking
profile must be of type CoS to p-bit.
If a color-aware marking profile is
applied for the outer VLAN of a flow,
then if marking is applied to the
inner VLAN, either the same
color-aware marking profile must be
used for the inner VLAN, or a
non-color-aware marking profile
must be used for the inner VLAN.
Typing no marking-profile or
no inner-marking-profile removes
the overwriting of marking profile
or inner marking profile
respectively.
Overwriting inner p-bit according inner-marking-profile <inner-marking-profile-name> See comments for marking-profile.
to marking profile
Overwriting p-bit with a new value p-bit <p-bit-value> Typing no p-bit removes the
overwriting of p-bit.
Overwriting inner p-bit with a new inner-p-bit <inner-p-bit-value> Typing no inner-p-bit removes the
value overwriting of inner p-bit.
Overwriting VLAN ID with a new vlan <vlan-value> Typing no vlan removes the
value overwriting of VLAN ID.
Overwriting inner VLAN ID with a inner-vlan <inner-vlan-value> [inner-ether-type Inner-ether-type can be configured
new value and optional Ethertype <inner-ether-type>] to one of the four global device level
value Ethertypes (see Ethertype section in
Chapter 6).
If not configured, the inner
Typing no inner-vlan removes the
overwriting of inner VLAN ID.
Exiting the marking context and exit

returning to the flow context

Configuring Port Classification

Port classification can be configured for the following ports:
Ethernet ports
Redundancy LAG ports (the port classifier rules must be configured for the
anchor port)
Logical MAC
PCS port
To configure port classification for Ethernet/LAG/logical MAC/PCS port:

1. Navigate to configure port ethernet [<slot>/]<port> classifier,
configure port lag <port> classifier, configure port logical-mac <port>
classifier, or configure port pcs <port> classifier, respectively.
The prompt config>port>eth([<slot>/]<port>)>classifier#,
config>port>lag(<port>)>classifier#,
config>port>log-mac(<port>)>classifier#, or
config>port>pcs(<port>)>classifier# is displayed.
Note In the case of LAG port, the port classifier rules must be configured for the
anchor port.
Adding comment rule comment <description> description text description

[sequence <sequence-number>] sequence-number sequence
number for comment
Removing rule delete <sequence-number>
Adding drop rule drop [dst-mac <dst-mac-address>] Up to five criteria can be

[src-mac <src-mac-address>] specified; they must be in the
[ether-type <ether-type>] [vlan <vlan>] same order in which they
[p-bit <p-bit>] [dei {0 | 1}] appear in the command syntax
[inner-ether-type <inner-ether-type>]
[inner-vlan <inner-vlan>]
[inner-p-bit <inner-p-bit>] [ip-dscp <ip-dscp>]
[ip-precedence <ip-precedence>] [tos <tos>]
[protocol <protocol>] [src-ip <src-ip-address>]
[dst-ip <dst-ip-address>]
[tcp-src-port <tcp-src-port>]
[tcp-dst-port <tcp-dst-port>]
[udp-src-port udp-src-port>]
[udp-dst-port <udp-dst-port>] [any]

Adding match rule match [dst-mac <dst-mac-address>] Up to five criteria can be

[src-mac <src-mac-address>] specified; they must be in
[ether-type <ether-type>] [vlan <vlan>] the same order in which
[p-bit <p-bit>] [dei {0 | 1}] they appear in the
[inner-ether-type <inner-ether-type>] command syntax
[inner-vlan <inner-vlan>] The flow specified by
[inner-p-bit <inner-p-bit>] [ip-dscp <ip-dscp>] to-flow <flow-name> has
[ip-precedence <ip-precedence>] [tos <tos>] to be defined as a flow
[protocol <protocol>] [src-ip <src-ip-address>] with parameter
[dst-ip <dst-ip-address>] port-classifier.
[tcp-src-port <tcp-src-port>]
CoS is optional; it can be
[tcp-dst-port <tcp-dst-port>]
specified via to-cos-fixed
[udp-src-port udp-src-port>]
as a fixed value or via
[udp-dst-port <udp-dst-port>] [any]
to-cos-profile as a profile.
to-flow <flow-name>
{[to-cos-fixed <fixed-cos>] |
[to-cos-profile <profile-cos>]}
Reseqencing the rules resequence [<step>] If you need to add a rule

between existing rules with
consecutive sequence
numbers, use this command to
add space between the rule
sequence numbers.
The <step> parameter
specifies the interspacing
value. For example, if you
apply resequence 30 to a port
classification that contains
rules 1, 2, and 3, the rule
sequence numbers change to
30, 60, and 90.
Displaying port classifier show status

status
Examples
Classifier Profiles
To create classifier profile with criteria VLAN 100 to VLAN 150:

exit all
configure flows classifier-profile v100_150 match-any
match vlan 100..150
exit all
To create classifier profile with criteria VLAN 20 and inner VLAN 30:
exit all
configure flows classifier-profile v20_inner_30 match-any

match vlan 20 inner-vlan 30

exit all
To create classifier profile that matches all criteria:

exit all
configure flows classifier-profile all match-any
match all
exit all
Traffic Flows
This section provides an example of configuring the following flows:
Outgoing traffic from port ETH 0/3 to port ETH 0/1:
Accept only traffic tagged with VLAN 10.
Add VLAN 100 with p-bit 5 (this causes VLAN 100 to be the outer VLAN
and VLAN 10 to be the inner VLAN).
Incoming traffic from port ETH 0/1 to port ETH 0/3:
Accept only traffic tagged with VLAN 100 and inner VLAN 10.
Remove the outer VLAN (VLAN 100).
To configure the flows:

#*******Configure v10 classifier profile for outgoing flow
exit all
configure flows
match vlan 10
exit
#*******Configure outgoing flow with v10 classifier profile,

#********* with ingress at ETH 1/3, egress at ETH 0/1,
#********* and pushing VLAN 100 with p-bit 5
flow f10_out
classifier v10
service-name v10
pm-collection interval 900
no shutdown
exit
#*******Configure v100_inner_v10 classifier profile for incoming flow

classifier-profile v100_inner_v10 match-any
match vlan 100 inner-vlan 10
exit
#*******Configure flow with v100_inner_v10 classifier profile,

#********* ingress at ETH 0/1, egress at ETH 0/3, and popping the outer VLAN
flow f100_in
classifier v100_inner_v10


vlan-tag pop vlan
service-name v10
no shutdown
exit all
ETP Flows
This section provides an example of configuring the following flows:
Flow sub1:
Ingress = ethernet 0/3
Egress = etp ETP1 subscriber 1, CoS mapping profile my-p-bit (see CoS
Mapping Profiles for details on CoS mapping profiles)
Flow trans1:
Ingress = etp ETP1 transport 1
Egress = ethernet 0/1, queue 0, block 0/1
To configure ETP flows:

#**************Configure flow sub1
exit all
configure flows
flow sub1
egress-port etp ETP1 subscriber 1 cos-mapping my-p-bit
exit
#**************Configure flow trans1

flow trans1
ingress-port etp ETP1 transport 1
exit all
Unidirectional Hub
This section provides an example of configuring a unidirectional hub with five
flows:
Ingress port = ETH 0/1
Egress ports:
ETH 0/3, queue 0, block 0/1
Criteria = VLAN 100
Policer profile bandwidth limits = CIR 10000, CBS 5000, EIR 0, EBS 0

To configure the hub:

#**************** Configure policer profile and aggregate for UDH
exit all
configure qos
policer-profile udh_pol bandwidth cir 10000 cbs 5000 eir 0 ebs 0
policer-aggregate udh_agg policer profile udh_pol
exit all
#*************** Configure classifier profile for UDH

configure flows
classifier-profile udh_class match-any match vlan 100
exit
#*************** Configure flow udh1

flow udh1
classifier udh_class
policer aggregate udh_agg
no shutdown
exit

flow udh2
no shutdown
exit

flow udh3
no shutdown
exit

flow udh4
ingress-port ethernet ethernet 0/1
egress-port e ethernet 0/5 queue 1 block 0/2
no shutdown
exit

flow udh5


no shutdown
exit all
Multi-CoS Flow
This section provides an example of configuring multi-CoS flows per MEF 10.3:
Flow with multi-CoS counters:
Egress port: ETH 1/1
Criteria = VLAN 10
Flow with envelope policer:
Egress port: ETH 0/1
Criteria = VLAN 10
Envelope profile bandwidth limits:
CIR 1000; maximum CIR 10,000; CBS 2000; EIR 0; EBS 0; maximum EIR 0
To configure the multi-CoS flows:

#**************** Configure CoS mapping profile
exit all
configure
qos
cos-map-profile cos-pbit classification p-bit
untagged-map to-cos 0
exit
#**************** Configure envelope profile

envelope-profile env1
cf-policy uncoupled-BW-sharing
cos 0 bandwidth cir 1000 cir-max 10000 cbs 2000 eir 0 eir-max 0 ebs 0
cos 1 bandwidth cir 2000 cir-max 10000 cbs 2000 eir 0 ebs 0
exit
exit
#*************** Configure classifier profile

flows
exit
#*************** Configure multi-cos-counters flow

flow multi2

classifier v10
cos-mapping profile cos-pbit
no policer
multi-cos-counters 0..3
egress-port ethernet 1/1 queue-map-profile q-map-for-cos block 0/1
no shutdown
exit
#*************** Configure flow with envelope policer

flow env2
classifier v10
policer envelope env1
cos-mapping profile cos-pbit
egress-port ethernet 0/1 queue-map-profile q-map-for-cos block 0/1
no shutdown
exit all
save
Port Classification
The following illustrates configuring port classification for Ethernet
port 0/1.
exit all
#************Outer VLAN************
configure port ethernet 0/1 classifier
match vlan 100 sequence 1 to-flow 1
exit all
configure flows flow 1 port-classifier

no shutdown
exit all
#************Outer p-bit************
match p-bit 2 sequence 2 to-flow 2
exit all

no shutdown
exit all
#************Dest MAC************
match dst-mac 00-11-22-33-44-55 sequence 3 to-flow 3
exit all

no shutdown
exit all
#************Dest IP address IPv4************


match dst-ip 172.17.160.173/32 sequence 4 to-flow 4

exit all

no shutdown
exit all
#************Dst IP address IPv6************

match dst-ip 1234:1235:1236:1237:1238::1239/128 sequence 5 to-flow 5
exit all

no shutdown
exit all
#************Dest TCP port************

match tcp-dst-port 0070 sequence 6 to-flow 6
exit all

no shutdown
exit all
#************Dest UDP port************

match udp-dst-port 0070 sequence 7 to-flow 7
exit all

no shutdown
exit all
#************ToS************
match tos 8 sequence 8 to-flow 8
exit all

no shutdown
exit all
#************Protocol************
match protocol 5 sequence 9 to-flow 9
exit all


no shutdown
exit all
#************ IP DSCP************
match ip-dscp 4..6 sequence 10 to-flow 10
exit all

no shutdown
exit all
#************IP Precedence************
match ip-dscp 4..6 sequence 11 to-flow 11
exit all

no shutdown
exit all
Testing Flows and Flow Diagnostics Loopback

MAC swap loopback tests support two different use cases:
Use Case 1: Application layer loopback MAC swap loopback of traffic with
certain characteristics (e.g MAC address, VLAN+MAC, etc.) by configuring a
dedicated flow for this purpose
Use Case 2: Flow diagnostics loopback performs MAC swap loopback over
an existing configured flow
Note MAC swap is not performed if the flow is part of a unidirectional hub.
Use Case 1 Application Layer Loopback

In this use case, an application layer loopback test is applied over a dedicated
configured flow with a test mac-swap attribute. In this case, the egress port must
be configured to be equal to the ingress port.
You can run application layer loopbacks on a flow, with exchange of source and
destination MAC addresses or IP addresses of incoming packets. This applies to all
the data associated with the flow.
Note Regardless of whether the mac-swap or ip-swap option is specified, if there is an

IP header in the frames, then both MAC and IP addresses are swapped; otherwise
only the MAC address is swapped.
The following procedure shows how to run an application layer loopback test
using a flow.

To run an application layer flow loopback test:

1. Navigate to configure flows flow <flow-name> to select the above flow.
The config>flows>flow(<flow-name>)# prompt is displayed.
2. Create a flow with the ingress port equal to the egress port with a test mac-
swap attribute.
test [{mac-swap | ip-swap}] [duration <seconds>] [ttl-force <ttl>]
The flow is activated upon flow no-shutdown, and the TEST LED is
turned on. The test runs for the duration specified. If 0 is specified for
the duration, the test runs until it is stopped manually, and the loop
remains after reset (including MAC/IP swap).
To end the test:

Delete the flow
OR
1. Navigate to configure flows flow <flow-name> to select the flow being
tested.
2. Enter:
no test
Example
Note This example uses the classifier profile da mac aa, created in the classifier
profile examples.
To configure the mac-swap loopback:

exit all
configure flows flow Tflow
classifier da_mac_aa
test mac-swap duration 50
no shutdown
exit all
ETH1
Figure 8-11. Application Layer Loopback Test on Flow with Three Attributes
To display flow test status:

ETX-2i>config>flows>flow(Tflow)# show test
Test : MAC Swap Duration (Sec) : 50 Remain (sec) : 40
No TTL

Method 2 Flow Diagnostics Loopback

This method, supported over a point to point service, performs the loopback test
using only one flow attribute test mac-swap. No other changes are required to
the flow; there is no need to configure egress port = ingress port, or to shut
down the flow and associated MEPs. The loop command is cleared after reset.
To run flow diagnostic loopback:

1. Navigate to configure flows flow <flow-name> to select an existing flow.
2. Enter:
test [{mac-swap|] [duration <seconds>]
The TEST LED is turned on. The test runs for the duration specified. If 0 is
specified for the duration, the test runs until it is stopped manually.
To end the test:

1. Navigate to configure flows flow <flow-name> to select the flow being
tested.
2. Enter:
no test
Example Flow Diagnostics Loop

In the following example, two flows of an EVC are configured. The diagnostics
loop is performed over evc1_in the flow (back to the network).
Note This example uses the classifier profile all, created in the classifier profile
examples.
To configure the mac-swap loopback:

exit all
ETX-2x configure flows flow (evc1_in)# test mac-swap duration
50
To display flow test status:

ETX-2i>config>flows>flow(evc1_in)# show test
Test : MAC Swap Duration (Sec) : 50 Remain (sec) : 40
No TTL
ETH 3 ETH 1
Loop performed on this flow (evc1_in)
Figure 8-12. Application Layer Loopback Test on Flow with a Single Attribute

Viewing Flow Statistics

You can display the number of forwarded and discarded packets and bytes for a
flow.
The statistics do not include transmitted and received OAM packets if no
statistics-count-oam was specified for the flow. The counters are displayed per
CoS in the case of multi-CoS flow.
ETP subscriber flow statistics include:
Red dropped counters at policer, as the logical flow extends to the ETP and
not to the Egress port.
Green and yellow dropped counters, reflecting the statistic of the flow up to
the Egress port.
Note See Configuring Policer Aggregate Parameters for information on displaying

statistics for flows associated with policer aggregates.
To display the statistics for a flow:

At the relevant flow context (config>flows>flow(<flow-id>)), enter:
show statistics running
Flow statistics are displayed.
To clear the statistics for a flow:

At the relevant flow context (config>flows>flow(<flow-id>)), enter:
clear-statistics
The statistics for the flow are cleared.
Examples
ETP Subscriber Flow Statistics

This example displays statistics of ETP subscriber flow sub1 (see configuration in
ETP Flows example).
To display flow statistics (ETP):

ETX-2i# configure flows flow sub1
ETX-2i>config>flows>flow(sub1)# show statistics running
Rate Sampling Window
-----------------------------------------------------------------------------
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 20000
Bytes : 20000000
Drop Statistics
-----------------------------------------------------------------------------

Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
pps L1 (bps) L2(bps)
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Yellow(Rate) : 0 0 0
Red(Rate) : 0 0 0
Yellow/Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
L1 Min. L2 Min L1 Max L2 Max.
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
Multi-CoS Flow Statistics

This example displays statistics of multi-cos flow multi2 (see configuration in
Multi-CoS Flow example).
To display multi-CoS flow statistics:

ETX-2i# configure flows flow multi2
ETX-2i>config>flows>flow(multi2)# show statistics running
-----------------------------------------------------------------------------
Cos Number : 2
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics

-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 0 0
Drop Bit Rate [bps]: 0 0 0 0
Cos Number : 3
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000

Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
Cos Number : 5
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 0 0 0
Green(Rate) : 0 0 0

Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 0 0
Drop Bit Rate [bps]: 0 0 0 0
Viewing Flow Status

You can display the operational status and reverse operational status of a flow,
as well as the service name for flows configured with a service. Fault propagation
actions are visible only for flows configured with fault propagation and fault
propagation license activated.
Example
To display flow status:

ETX-2i# configure flows flow a1
ETX-2i>config>flows>flow(a1)# show status
Reverse Operational Status : Up
Service Name :
Fault propagation actions:

Policer changed : policer profile
Shaper changed
Status Details
-----------------------------------------------------------------------------
: Ingress Port Oper Status: Down
Viewing Flow Data Rate and Line Rate

You can measure the data rate and line rate at which flows transmit and receive,
for a configurable time interval of 10300 seconds. After you enter the command
to measure the rates, ETX-2i automatically displays the results when the specified
time interval ends. The data rate is calculated by dividing the number of total
bytes (not including line overhead) by the time interval. The line rate is calculated
by dividing (number of total bytes + (number of packets x 20 bytes of line
overhead)) by the time interval.
To start data rate and line rate measurements for flow:

At the prompt config>flows>flow(<name>)#, enter:
rate-measure interval <seconds>
The rate measurement starts. You can use show rate to monitor how
much of the time interval has elapsed. The result is automatically
displayed, without the need to enter show rate, after the specified time
interval ends.

Example
To display data rate and line rate for flow:
ETX-2i# configure flows flow f10_out
ETX-2i>config>flows>flow(f10_out)# rate-measure interval 30
ETX-2i>config>flows>flow(f10_out)# show rate

Name : f10_out
Time Left to Elapse (Sec) : 18
ETX-2i>config>flows>flow(f10_out)#
Name : f10_out
Status : Passed
Start Time : 2014-11-13 12:24:36 UTC +00:00
Duration (Sec) : 30
Cos : 255
L1 L2
Rx Rate (bps) : 1000 950
Tx Rate (bps) : 1500 1400
Green Drop (bps) : 100 95
Yellow Drop (bps) : 100 95
Red Drop (bps) : 100 90
8.3 Distributed Network Functions Virtualization

(D-NFV)
Overview
Network functions virtualization (NFV) is a network architecture concept that uses
IT virtualization technologies to virtualize entire classes of network node
functions into building blocks that connect or chain together to create
communication services.
NFV uses IT virtualization technologies to replace dedicated network devices with
software running on common off-the-shelf servers. NFV relies upon, but differs
from, traditional server-virtualization techniques, such as those used in enterprise
IT.
A virtualized network function (VNF) can consist of one or more virtual machines
running different software and processes on top of standard high-volume
servers, switches, and storage, or even cloud computing infrastructure, instead of
allocating custom hardware appliances for each network function.
The original approach to NFV advocates placement of VNFs not only in data
centers, but throughout the network, wherever they are most effective and least
expensive.
Distributed Network Functions Virtualization (D-NFV) is a solution for distributed
NFV at the customer edge. According to this concept, some network functions
8-60 Distributed Network Functions Virtualization (D-NFV) ETX-2i

are located in the cloud while others are distributed geographically to locations
out of the cloud, at customer premises.
D-NFV Orchestrator, a GUI network management application described in the
RADview Manual, manages D-NFV applications.
Orchestrator
Controller
ETX-2i ETX-2i
D-NFV Module D-NFV Module

UNI Port X.86 NNI Port NNI Port X.86 UNI Port
Compute Host Network Host
Compute
Figure 8-13. D-NFV Application Architecture
D-NFV Module
The D-NFV module resides on an x86 card connected to the ETX-2i NID, which
uses a cloud computing software platform to enable hosting virtual machines
providing virtual functions (VFs).
D-NFV Module software is based on a Linux machine that runs OpenStack services
and DNFV-OS software that provides an operation and maintenance environment.
D-NFV module has the following general features:
General
Based on x86 hardware and Linux Ubuntu distribution version 14.04.3
Supports D-NFV HW cards inserted into ETX2i
Supports IPv4
Supported by RADview
Supports DPDK acceleration.
DNFV-OS
OpenStack
Supports OpenStack Juno version 2014.2.3
Supports Compute Node functionalities
Supports Controller functionalities
Supports OVS and Linux Bridge
Applicable Products
This feature is applicable to ETX2i with D-NFV option.
ETX-2i Distributed Network Functions Virtualization (D-NFV) 8-61

Benefits
Rapid rollout of new services, network capabilities, and functions
Integration of higher-level applications (firewall, encryption, WINDOWS server,
and more) with a communication platform in a single device
Reduced number of physical network devices for better reliability and simpler
operation
Reduced customer site equipment footprint and less power consumption
D-NFV Module
D-NFV infrastructure is based on OpenStack, a software platform that controls
large pools of compute, storage, and networking resources and is managed via
the OpenStack API.
Related to D-NFV context, OpenStack provides two main functions:
Controller
Compute Node
The D-NFV module includes the following components:
Linux OS Release Ubuntu 14.04
KVM Hypervisor Enables running multiple virtual machines; QEMU KVM

V 2.0.0; on ACC (accelerated version), V 2.5.0
Open Virtual Enables the connection between the x86 processor

Switch (OVS) physical ports and the VM ports; V 2.0.1; on ACC
(accelerated version), V 2.4.0
Linux Bridge Standard Linux bridge that provides a connection between

the x86 processor physical ports and VM ports
Controller OpenStack Controller
Compute Node OpenStack Compute Node
Controller
Located in the cloud, Controller manages the edge devices VNF resources, such
as compute, storage, and network capabilities. Controller is also responsible for
controlling the deployment of VNF instances.
Compute Node
Compute Node is located in the customer edge device, where D-NFV modules
reside on a standard Intel x86 core that enables hosting virtual machines. These
VMs host VNFs. Compute Node is controlled by Controller.
ETX2i Device
The D-NFV module resides on an x86 card connected to the ETX-2i NID.

The following diagram shows the ETX2i internal structure.
ETX
VNF2 VNF1
X86
Controller
Hypervisor (KVM)
OVS (Open VSwitch)

Compute
OS Node
HW Resources
P7 P8
UNI ETX NNI

Host
NID
Figure 8-14 ETX2i Internal Structure
The ETX2i NID elements requiring configuration are:

Flow engine
Physical external ports NNI and UNI
Physical internal ports Internal ports 0/7 and 0/8
ETX2i host
Application Management
Application management includes both planning and deployment and is
performed via D-NFV Orchestrator, a module designed specifically for NFV
management.
D-NFV Orchestrator provides the following configuration capabilities:
Device configuration (except D-NFV module) Configuration to connect a
devices physical or logical ports to D-NFV module ports (using internal flows,
bridges) and provide the needed functionality (QoS, protocols).
VNF deployment (D-NFV module) Configuration to create connectivity,
allocate resources, and deploy the VNF instance.
D-NFV Orchestrator communicates with the device to set device configuration,
and with Controller to set VNF deployment. Controller communicates with
Compute Node.
D-NFV Orchestrator receives status and statistics events from the device and
Controller.

Configuring Service Function Chain (SFC) for D-NFV

Perform the following steps to provide SFC:
1. Configure ETX2i for basic management (refer to ETX2i Installation and
Operation Manual).
For example: Connect management VLAN from NNI port via bridge to ETX2i
host and internal port 0/8.
2. Configure D-NFV module x86 host (see Configuring Compute Node):
IP address, mask, default gateway, host name, and Controller IP address
3. Configure SFC flows on ETX2i device (refer to ETX2i Installation and
Operation Manual):
Between NNI (user traffic VLAN) and Internal port 0/8
Between UNI and Internal port 0/7
4. Create OpenStack SFC using D-NFV Orchestrator or OpenStack dashboard
(Horizon).
Figure 8-15. Simple Service Function Chain (SFC)
Configuring Compute Node

The D-NFV module resides on a standard Intel x86 core with a Compute Node
instance on top of it. There is no need for installation.
Perform the following steps to configure the Compute Node:
1. Access the x86 terminal from the ETX-2i CLI (see Accessing the x86 Terminal).
2. Configure the Compute Nodes basic parameters (see Configuring Compute
Node Parameters).
3. Set the OpenStack Network Mechanism to Open vSwitch or Linux Bridge (see
Setting the OpenStack Networking Mechanism Driver).
4. Configure Fault Propagation on the device and Compute Node, if required
(see Configuring Fault Propagation).

Accessing the x86 Terminal

You can access the x86 terminal from the device CLI, without the need for a
separate terminal.
Characters typed at the CLI prompt are redirected to and from either the local
terminal (if managing the device via the control port) or the Telnet/SSH session
(if managing the device remotely) to the x86 host, via the RS-232 connection
between the device NTU and the x86 card.
Note You can also run a Telnet/SSH session directly to the x86 processor.
To access the x86 terminal:

1. Access the ETX-2i devices CLI, and log in to the device using the following
identification parameters:
Username: su
Password: 1234
3. Switch access from the ETX-2i terminal to the x86 terminal, by typing:
remote-terminal
The x86 terminal login prompt is displayed.
The first time, etx2i-x86-acc login: prompt is displayed.
4. At login as: prompt, type the x86 terminal username: rad.
password prompt is displayed.
5. At password prompt, type rad123.
The displayed prompt is rad@hostname.
(At first login, rad@etx2i-x86-acc:~$.)
6. You are now in rad user context, and are allowed to use DNFV-OS commands.
Proceed to configure Compute Node.
Configuring Compute Node Parameters

Once you have logged into the x86 terminal, you must configure Compute Nodes
networking behavior by setting its basic parameters. This includes setting the IP
information of the management interface, and setting the host name and
Controller hosts IP address.
To configure Compute Node:

At the rad@hostname:~$ prompt, type dnfv-conf, followed by the necessary
configuration options, according to the tasks listed below.
Task Option Comments
Getting command help --help Shows DNFV-OS commands that you can
use to configure Compute Node.

Setting Compute Node IP --ip= <IP address> Valid IP address

address
Setting Compute Node --mask= <IP mask> Valid IP mask

network mask
Setting Compute Node --gw= <IP address> Valid IP address

default gateway IP address
Setting Compute Node --hostname= <host name> Prompt upon login is

host name rad@hostname: ~$
Notes:
The hostname at first login is
etx2i-x86-acc. It must be changed at
dnfv-conf first run.
After you set the hostname, it is not
recommended to change it again, as it
can cause problems with the existing
running VMs.
Setting Controllers IP --ip-ctrl= <IP address> Valid IP address

address
Setting MTU size --mtu= <size> Maximum transmission unit; the largest size
packet (in octets), which can be sent in the
network
Removing verification --no-verif By default, Compute Node configuration is

process verified.
Selecting this option indicates not to
perform the verification process.
Removing reboot option --no-reboot By default, the machine reboots following

configuration and is ready to use.
Selecting this option means that the
machine does not reboot following
configuration.
Setting the OpenStack Networking Mechanism Driver

You can set the OpenStack Networking Mechanism Driver on Compute Node only.
To configure the OpenStack networking mechanism driver:

At the rad@hostname:~$ prompt, type dnfv-set-12 followed by the necessary
Getting command help -- Shows DNFV-OS commands that you can

help use to configure OpenStack networking
mechanism driver

Defining networking (L2) --mechanism = {open-vswitch | Sets OpenStack networking mechanism to

mechanism drivers linux-bridge} one of the following implementations:
Open vSwitch
Linux Bridge

configuration.
Configuring Fault Propagation

DNFV-OS supports Fault Propagation, reflecting a physical ports status onto a
VMs vNIC. When a physical port link goes down, the related vNIC link goes down.
The Fault Propagation process is as follows:
The ETX-2i device generates an SNMP trap toward the x86 host upon physical
Ethernet port link status change.
DNFV-OS, using its built-in correlation map between ETX-2i ports and the
Linux network interface, correlates to the appropriate VMs vNIC(s).
Table 8-7. DNFV-OS Correlation Map Between ETX-2i Ports and x86 Interface
ETX-2i Physical Port X86 Interface
Ethernet 0/1 P4p2
Ethernet 0/2 p4p1.200
Note
You can view the current map configuration by typing
cat /home/rad/work/code/mgmt/fault-propagation/dnfv-fp-ifs-map.conf.
When the DNFV-OS receives such a trap, it changes the appropriate VMs
vNIC(s) link status according to the trap content.
Fault Propagation configuration requires configuring both the ETX-2i device and
DNFV-OS (Compute Node).
Configuring the ETX-2i Device

You must configure the ETX-2i device as follows:
Set SNMP trap target to DNFV-OS.
Configure the SNMP target tag-list as both unmasked and masked, so
that the following occurs:
The ETX2i device sends the VM all notifications (traps), which by default
have the tag unmasked.

The ETX2i devices sends the VM the internal trap adminDown, which by
default has the tag masked. This trap notifies the VM that a device port
has gone down, enabling synchronization between the VM and device
ports.
Enable SNMP trap-sync mechanism. For configuration details, refer to the
Configuring SNMPv3 Parameters section in Chapter 4 of the ETX2i Installation
and Operation Manual.
Configuring Fault Propagation on Compute Node

You must configure the DNFV-OS (Compute Node) as follows:
Set the ETX-2i host IP address and communities (trap and set).
Define ETX-2i physical ports mapping to x86 interfaces and segment ID.
Enable/disable fault propagation.
To configure Fault Propagation:

At the rad@hostname:~$ prompt, type dnfv-fp-conf, followed by the
necessary configuration options, according to the tasks listed below.
Getting command help --help Shows DNFV-OS commands that can be

used to configure fault propagation
Setting SNMP trap --snmp-trap-

community community=community
Setting SNMP set --snmp-set-

community community=community
Setting SNMP trap source --snmp-trap-src-ip=ip

IP address
Mapping ETX-2i physical --ifs-map-entry=etx-port,x86- etx-port must match the SourceName field
port to x86 interface if within the ethLos trap (format: Ethernet
[slot/]port). See default table: Table 8-13
Skipping the reboot post- --no-restart Default: False

execution step
Enabling/Disabling Fault Propagation

You can control the operational state of Fault Propagation. The default is that
Fault Propagation is disabled.
To enable Fault Propagation:

At the rad@hostname:~$ prompt, type dnfv-fp-ctrl on.
To disable Fault Propagation:

At the rad@hostname:~$ prompt, type dnfv-fp-ctrl off.

Viewing Compute Node Information

You can view Compute Node basic information or enhanced information.
To display Compute Node basic information:

At the rad@hostname:~$ prompt, type dnfv-info.
To display Compute Node enhanced information:

At the rad@hostname:~$ prompt, type dnfv-info-max.
Rebooting/Shutting Down Compute Node

You can reboot or shut down Compute Node, using the dnfv-ctrl-pwr command.
Note You can view the available host power command options, by entering
dnfv-ctrl-pwr--help.
To reboot Compute Node:

At the rad@hostname:~$ prompt, type dnfv-ctrl-pwr --reboot.
To shut down Compute Node:

At the rad@hostname:~$ prompt, type dnfv-ctrl-pwr --shutdown.
Resetting/Waking the D-NFV Module

You can reset a running D-NFV module or wake a sleeping D-NFV module, using
the device CLI.
To reset/wake the D-NFV module:

1. Access the ETX-2i devices CLI, and log in to the device using the following
identification parameters:
Username: su
Password: 1234
3. Type reset-wake.
The D-NFV module is reset.
Exiting the x86 Terminal

When you are finished configuring Compute Node, you can exit the x86 terminal,
and return to your device CLI.
To exit the x86 terminal:

Exit the x86 terminal by entering:
<ctrl>+<shift> + <->.
The device CLI screen is displayed.

Examples
Example 1 x86 Terminal Access

The following example shows how to access the x86 terminal.
user>su
password>****
CPE#CPE# configure chassis ve-module

CPE>config>chassis>ve-module# remote-terminal
CPE>config>chassis>ve-module#
Ubuntu 14.04.2 LTS etx2i-x86-acc ttyS0
etx2i-x86-acc login:
etx2i-x86-acc login: rad
Password:
Last login: Mon May 30 20:26:34 IDT 2016 on ttyS0
rad@etx2i-x86-acc:~$
Example 2 Compute Node Configuration

The following is an example of Compute Node configuration.
rad@etx2i-x86-acc:~$ dnfv-conf --ip=10.20.30.40
--mask=255.255.255.0 --gw=10.20.30.254 --ip-ctrl=1.2.3.4
--hostname=compute1
[sudo] password for rad:
D-NFV host configuration utility
Copyright (c) RAD Data Communications, 2015
..
Done.
Rebooting...
Example 3 Compute Node Reboot/Shutdown

The following example shows how to reboot and shut down Compute Node.
rad@compute1:~$ dnfv-ctrl-pwr reboot
D-NFV power control utility

Rebooting...
rad@0020d2535094:~$ dnfv-ctrl-pwr shutdown
D-NFV power control utility

Shutting down...
Example 4 Open vSwitch Configuration

The following example shows how to set open-vswitch.
rad@compute1:~$ dnfv-set-l2 --mechanism=open-vswitch
D-NFV L2 set-up utility


Done.
Rebooting...
Example 5 OpenStack Networking Mechanism Configuration

The following example shows how to set the Linux-bridge.
rad@compute1:~$ dnfv-set-l2 --mechanism=linux-bridge
D-NFV L2 set-up utility
Done.
Rebooting...
Example 6 Fault Propagation Configuration

The following example shows how to configure the ETX-2i device, correlation
map, and DNFV-OS (Compute Node), for fault propagation.
The following shows how to configure ETX-2i to:
Generate SNMP traps and transmit them to the x86 host.
Operate trap-sync mechanism.
configure
management
snmp
security-to-group snmpv2c sec-name "v2c_trap"
group-name "v2_trap"
no shutdown
exit
community "read"
name "public"
sec-name "v2_read"
no shutdown
exit
community "trap"
name "public"
sec-name "v2c_trap"
no shutdown
exit
community "write"
name "private"
sec-name "v2_write"
no shutdown
exit
target-params "x86_fp_trap"
message-processing-model snmpv2c
version snmpv2c
security name "v2c_trap" level no-auth-no-priv
no shutdown
exit
target "x86_fp_trap"

target-params "x86_fp_trap"
address udp-domain <TRAP DESTINATION IP>
no shutdown
tag-list unmasked masked
trap-sync-group 1
exit
exit
exit
exit
save
The following shows how to configure the correlation map:
rad@compute1:~$
dnfv-fp-conf --ifs-map-entry="Ethernet 0/1,p4p2"
dnfv-fp-conf --ifs-map-entry="Ethernet 0/2,p4p1.200"
dnfv-fp-conf --ifs-map-entry="Ethernet 0/3,p4p1.201"
dnfv-fp-conf --ifs-map-entry="Ethernet 0/4,p4p1.202
The following shows how to configure DNFV-OS (Compute Node) with fault
propagation as follows:
SNMP trap community set to public
SNMP set community set to private
SNMP trap source IP address set to 172.17.231.238
Skipping the reboot post-execution step
rad@compute1:~$
dnfv-fp-conf --snmp-trap-community=public --snmp-set-
community=private --snmp-trap-src-ip=172.17.231.238 --no-
restart
Example 7 Display of Compute Node Information

The following example shows how to display Compute Node basic information.
rad@compute1:~$ dnfv-info
Version: dnfv-1.1.0.015
Host: Compute
Name: compute1
Platform: ETX-2I
OS: Linux - Ubuntu 14.04.2 LTS
Cloud management: OpenStack - 2014.2.3
L2 mechanism: Open vSwitch
Add-on functionality:
aux-tools
tcpping
core-pinning
dp-acceleration
fault-propagation

rad@compute1:~$
The following example shows how to display Compute Node enhanced
information.
rad@compute1:~$ dnfv-info-max
Host: Compute
Name: compute1
Platform: ETX-2I
aux-tools
tcpping
core-pinning
---
Packages:
...
---
Configuration files:
...
Configuring Controller
Perform the following steps to configure the Controller:
1. Install Controller (see Controller Installation).
2. Log into the Controller (see Logging into Controller).
3. Configure the Controller basic settings (see Configuring Controller
Parameters).
Controller Installation
DNFV-OS provides installation of a Controller image for the VMware virtualization
environment.
Controller can be installed during the D-NFV Orchestrator installation on the same
server or separately on another server.
For installation during D-NFV Orchestrator installation, see the relevant topic in
the RADview online help.
For installation on another server, use the installation image.
For example, dnfv-os-1.2.0.010-ctrl-vmware.ova.
VMware server system requirements are:
ESXi server version 5.0 or later
2GB RAM memory available
60GB hard drive
To install Controller (1.2.0.010 or later) on VMware:

1. Open vSphere client, and select File> Deploy OVF Template.

2. Choose relevant OVA/OVF file:
3. Click Next.
4. Select the Name and Location tab, and type a Name for the virtual machine.

5. Select the Disk Format tab, and select Thin Provision.
Note You can also select Thick Provision: however, this uses more disk space.
6. Select the Ready to Complete tab, and click Finish.

The virtual machine is created. The following prompt is displayed:

controller login:
Logging into Controller

Once you have installed Controller, you can log into it.
To log into Controller:

1. In Controller login, type rad.
2. In password, type rad123.
The following prompt is displayed:
rad@controller:~$
Configuring Controller Parameters

Once you have logged into Controller, you must configure it for use.
To configure Controller:
At the rad@controller:~$ prompt, type dnfv-conf, followed by the necessary

used to configure Controller
Setting the Controller IP --ip= <IP address> Valid IP address

address

Setting the Controller --mask= <IP mask> Valid IP mask

network mask
Setting the Controller --gw= <IP address> Valid IP address

default gateway IP address
Setting interfaces MTU --mtu= <size>
Removing verification --no-verif By default, Controller configuration is

process verified.

configuration.
Controller Verification
To verify that Controller is up:

Connect to controllers dashboard.
Viewing Controller Information

You can view Controller basic information or enhanced information.
To display Controller basic information:

At the rad@controller:~$ prompt, type dnfv-info.
To display Controller enhanced information:

At the rad@controller:~$ prompt, type dnfv-info-max.
Examples
Example 1 Controller Configuration

The following is an example of Controller configuration.
rad@controller:~$ dnfv-conf --ip=100.100.100.100
--mask=255.255.255.0 --gw=100.100.100.1
D-NFV host configuration utility
..
Done.
Rebooting...
Example 2 Display of Controller Information

The following example shows how to display Controller basic information.
rad@controller:~$ dnfv-info

Host: Controller
Name: controller
Platform: VM
L2 mechanism: Open vSwitch
aux-tools
rad@controller:~$
Maintenance
Upgrade
This section describes the Upgrade process for Controller and Compute Node. The
Upgrade process supports installation of x86 software above a previous
upgradeable version (from V. 1.2.0.10).
The Upgrade Apply process is automatic (remotely triggered).
You can update x86 software using either of the following two methods:
Upgrade Download full version installation.

Update those elements that are related to the previous
version (packages, text files).
Patch Update text files.
Upgrade Process
The Upgrade process is composed of two stages:
Download Downloading the Upgrade file.
Apply Applying the Upgrade file in the remote host.
Apply does the following:

Sets running D-NFV services down
Backs up Compute Node / Controller required configuration
Installs upgrade services, packages, and text files
Restores the required configuration
Sets D-NFV services up
You can perform both Download and Apply in one CLI command, or in two
separate commands. As D-NFV services stop running during Upgrade, it is

recommended to apply Upgrade (Apply stage) at night, when services are not
running.
The following are not supported:
Downgrade (related to packages)
Update of external packages (add-ons)
To perform the Upgrade process on Controller:

At the rad@controller:~$ prompt, type dnfv-upgrade, followed by the
necessary Upgrade options, according to the tasks listed below.

used to perform the upgrade process
Downloading upgrade file download arch-url [--apply [-- arch-url <transfer-protocol> ://
and optionally, applying no-reboot]] <username>:<password>@<ip-address> /
the upgrade with or <file-name>
without reboot apply Use this command option to apply
the upgrade immediately after downloading
the file. If you do not want to upgrade
immediately following download, enter the
apply command option `at a later time (see
following task).
Applying the upgrade file in apply arch [--no-reboot] Use this command option in the case that
the remote host with or you did not apply the upgrade in the same
without reboot command as the download (see previous
task). In this case, you need to specify the
name of the upgrade file to apply.
arch file-name to apply
To perform the Upgrade process on Compute Node:

At the rad@hostname:~$ prompt, type dnfv-upgrade, followed by the
necessary Upgrade options, according to the tasks listed in the above table.
Patch Process
DNFV-OS supports a command to perform the x86 software patch update.
To perform the Patch process on Controller:

At the rad@controller:~$ prompt, type dnfv-patch, followed by the necessary
Patch options, according to the tasks listed below.

used to perform the patch process

Downloading and patching patches-arch-url [--no-reboot] Patches-arch-url <transfer-protocol> ://

the upgrade file in the <username>:<password>@<ip-address> /
remote host with or <file-name>
without reboot
To perform the Patch process on Compute Node:

At the rad@hostname:~$ prompt, type dnfv-patch, followed by the necessary
Patch options, according to the tasks listed in the above table.
Backup
You should perform periodic backup of the DNFV Compute Node and Controller.
Then, if a problem occurs with the DNFV Compute Node or Controller, you can
replace it with a backed up version.
The Backup process saves the following components:
Compute Node
Compute Node configuration the configuration performed by DNFV-OS
commands
VNF instances the instances that OpenStack downloaded from the
Controller
VNF configuration the configuration performed by the user
VNF license the license that the user inserted
Controller
Controller configuration the configuration performed by DNFV-OS
commands
Controller information OpenStack file system
Controller Backup
The Controller backup process does the following:
Creates a text file (controller-config) with all historical controller
configuration commands (dnfv-conf and more)
Creates a tar file (controller-info) with all controller info (OpenStack file
system)
Backs up compute tokens
Packs all files into one backup file
Copies the backup file to the SFTP server
To back up the controller:

At the rad@controller:~$ prompt, type dnfv-backup, followed by the
necessary option, according to the tasks listed below.

Getting command help --help Shows DNFV-OS command that can be used
to perform the backup process.
Specifying the URL of the arch-url arch-url <transfer-protocol> ://

backup file <username>:<password>@<ip-address> /
<file-name>
Compute Node Backup

The Compute Node backup process does the following:
Creates a text file (compute-config) with all historical compute configuration
commands (dnfv-conf, dnfv-set-12, and more)
Creates a tar file (instance-info) with VNF instances information for each VNF,
configuration, and license
Packs all files into one backup file
Copies the backup file to the SFTP server
To back up the compute-node:

At the rad@compute-node:~$ prompt, type dnfv-backup, followed by the
to perform the backup process.
Specifying the URL of the arch-url arch-url <transfer-protocol> ://

<file-name>
Restore
You can restore Compute Node or Controller, if you previously created a backup
file.
Compute Node Restore

The Compute Node restore process requires access and login into the Compute
Node machine (x86). When the DNFV card is in factory setup, an access via host
device remote terminal is required.
The Compute Node restore process is remotely triggered using a single
dnfv-restore command.
The Restore command performs the following:
Unpacks the relevant backup file
Runs a script on the ETX-2i device, which includes:
Login to the device
Entry into the remote terminal

Login to Compute Node (x86)

Running commands from the compute-config text file and reboot
Running the Restore command that does the following:
Copies from the SFTP server the relevant backup file
Unpacks the backup file
Opens the instance-info tar file
Restarts the OpenStack nova service
To restore Compute Node:

At the rad@compute-node:~$ prompt, type dnfv-restore, followed by the
to perform the restore process.
Specifying the URL of the arch-url [--no-reboot] arch-url <transfer-protocol> ://

<file-name>
no-reboot Do not perform reboot after
command set.
Controller Restore
The Controller Restore process requires access and login into the Controller
machine (x86).
The Compute Node restore process is automated by a single dnfv-restore
command.
The Restore command performs the following:
Enables access to the Controllers VM prompt
Login to Controllers VM
Unpacks the relevant backup file
Runs a script on Controller, which includes:
Running commands from the text file controller-config, and performing
reboot
Running the actual Restore command that does the following:
Copies from the SFTP server the relevant backup file
Unpacks the backup file
Opens the controller-info tar file
Restarts the compute tokens

To restore Controller:
At the rad@controller:~$ prompt, type dnfv-restore, followed by the
to perform the restore process
Specifying the URL of the arch-url [--no-reboot] arch-url <transfer-protocol> ://

<file-name>
no-reboot Do not perform reboot after
command set.
Examples
Example 1 Compute Node Upgrade

This example downloads and applies the Upgrade file in a single step, and then
reboots.
rad@compute1:~$
dnfv-upgrade download sftp://admin:admin@1.1.1.1/FileA --apply
Example 2 Controller Backup

This example backs up the Controller with the file in URL
sftp://admin:admin@1.1.2.2/FileB , without rebooting.
rad@controller:~$ dnfv-backup sftp://admin:admin@1.1.2.2/FileB
--no-reboot
Example 3 Controller Restore

This example restores the Controller with the file in URL
sftp://admin:admin@1.1.2.2/FileB , with rebooting.
rad@controller:~$ dnfv-restore sftp://admin:admin@1.1.2.2/FileB
Total Drop (bps) : 100 95
8.4 Ethernet over GRE (ETHoGRE) Tunnel

ETX-2i devices with an embedded router support Ethernet over GRE (ETHoGRE), a
Layer-2 tunneling technology that allows transport of Layer-2 frames and
services over an IP/MPLS network using IP/GRE Encapsulation.
Layer-2 tunneling technology allows Service Providers to have a single
infrastructure for both IP and Ethernet services or to allow Layer-2 services in
cases where only an IP network is available for transport.
ETX-2i supports up to 32 IPv4 or IPv6 GRE tunnels.
ETX-2i Ethernet over GRE (ETHoGRE) Tunnel 8-83

Figure 8-16. Tunneling Layer-2 MEF Services over an IP/MPLS Network
Applicable Products
This feature is applicable to ETX2i and ETX-2i-B.
Standards
RFC 2784: Generic Routing Encapsulation (GRE)
RFC 4087: IP Tunnel MIB
RFC 2890
Benefits
Allows transport of Layer-2 frames over an IP infrastructure.
ETHoIP/GRE Encapsulation
ETHoIP/GRE encapsulation is illustrated in the following diagram.
8-84 Ethernet over GRE (ETHoGRE) Tunnel ETX-2i

Figure 8-17. ETHoIP/GRE Encapsulation
The original Ethernet frame header and payload are encapsulated with a GRE
header, as described in RFC 2890, and a Tunnel IP header.
Figure 8-18. GRE Encapsulation
Figure 8-19. GRE Header
The Tunnel Identifier can be defined using one of the following two methods:
SRC IP (Key flag in GRE header is cleared)
SRC IP + key (If key is configured and k flag is set in GRE header)
Configured key is symmetrical (both Tx and Rx use the same key)
Both methods can coexist.
The following configuration is supported on the user side (Ethernet).

ETX-2
GRE1 (Dest IP, Key1)

ETH
Port SVI

ETH Bind
Port Bridge SVI

ETH
Port ETP SVI
Figure 8-20. Supported Configuration
The Layer-2 attachment to a GRE tunnel is supported with:

n Rx flows
A single Tx flow
Figure 8-21. Layer-2 Attachment to a GRE Tunnel
The Tunnel Tx flows can have the Match all classification profiles:
The Layer-2 GRE Tunnel interface supports configuration of the IP Tunnel DSCP to
one of the following:
A fixed value (0-63)
A previously defined p-bit to DSCP profile (refer to Configuring Marking
Profiles in the Quality of Service (QoS) section in Chapter 11).
Forwarding Model
The diagram below describes the ETHoGRE forwarding model.
Once encapsulated with IP/GRE, forwarding is done by the Router.

ETX-2
ETH IP GRE ETH

Forward by Router
ETH
GRE Tunnel
Port
Identify My Tunnel
ETH
Router Port
Figure 8-22. ETHoGRE Forwarding Model
GRE packets that exceed the GRE interface (Tunnel) MTU are discarded. There is
no support for fragmentation/reassembly.
Tunnel source IP should match one of the Router interface IP addresses.
Note When creating a GRE tunnel, it is recommended to configure OAM above the GRE
tunnel. See the example below.
Factory Defaults
Table 8-8. Tunnel Parameter Default Values
number DSCP number 0
key-number GRE key no key
name Tunnel name Tunnel-# (no name)
shutdown Enable/disable GRE tunnel. no shutdown
gre-ip/gre-eth Tunnel type gre-ip
Configuring GRE Tunneling

The following section describes how to configure a GRE tunnel.
To configure a GRE tunnel:
1. Navigate to configure router <number> to select the router interface on
which to configure GRE tunneling.
The config>router(number)# prompt is displayed.
2. Type tunnel-interface <number> gre-eth
Tunnel number can be 1-32.

3. In the config>router(<number>)>tunnel-interface (<number>)# prompt that

is displayed, enter all necessary commands according to the tasks listed
below.
Binding tunnel to a Layer-2 bind svi <svi-port-number> svi-port-number layer-2 port

attachment circuit no bind number
Possible values: 1-n (user-
defined per SVI index range in
the device)
SVI type must be GRE.
Clearing tunnel statistics clear-statistics
Configuring tunnel DSCP values dscp {fixed <number> | profile <profile-name>} number fixed DSCP value
Possible values:
0-63
255 means that the ETHoGRE
will use the DSCP profile.
profile-name name of profile
that maps p-bit to DSCP (refer
to Configuring Marking Profiles
in the Quality of Service (QoS)
section in Chapter 11).
Possible values: 1-32 character
string
Configuring tunnel GRE key key <key-number> Possible values:

no key 0 (no key)
1 to 4,294,967,295
no key means the GRE header
does not include the key field.
Defining tunnel name name <tunnel-name> Tunnel-name 0-64 character

no name string
Entering no name returns the
tunnel name to Tunnel-# (# is
the tunnel index).
Displaying tunnel status show status See Viewing GRE Status.
Disabling tunnel interface shutdown Tunnel interface shutdown

no shutdown stops traffic.
Notes:
Tunnel parameters can be
changed on the fly, even if
Tunnel is no shutdown.
If no shutdown, Tunnel is
operational if a valid source
and destination IP are
configured.

Defining tunnel destination IP tunnel-destination <ip-address> ip-address must be a valid

address no tunnel-destination unicast IPv4 or non-link-local
IPv6 address.
Source and destination
addresses must both be IPv4 or
both IPv6.
Defining source IP address or router tunnel-source [<ip-address>] [router-interface Either router-interface number
interface number used to bind the <number>] of IP address must be defined;
tunnel to a router interface no tunnel-source not both.
ip-address must be a valid
unicast IPv4 or non-link-local
IPv6 address
The router interface anchoring
the tunnel may not be a
loopback interface.
Source and destination
addresses must both be IPv4 or
both IPv6.
Deleting a GRE Tunnel

The following section describes how to delete a GRE tunnel.
To delete a GRE tunnel:
1. Navigate to configure router <number> to select the router interface from
which to delete a GRE tunnel.
The config>router(number)# prompt is displayed.
2. Enter no tunnel-interface <number>.
The tunnel of the specified number is removed from the router interface.
Viewing GRE Status

You can display the current GRE tunnel status.
To display GRE tunnel status:

At the config>router(<number>)>tunnel-interface(<number>)# prompt,
enter:
show status
The GRE tunnel status is displayed.
The following displays the status of a GRE-ETH tunnel.
ETX-2I>config>router(2)>tunnel-interface(2)$ show status
Tunnel : 2
Type : GRE-ETH
Status : Up
Tunnel Source

Interface : Router Interface 2/1 (SVI 1)

Address : 20.20.20.20
Tunnel destination : 20.20.20.40
Up For : 0 Day(s), 0:0:21
Packets
Tunnel Encapsulated 1532
Tunnel Decapsulated 9800
Table 7-9. ETHoGRE Status Parameters
Tunnel Tunnel number

Type Tunnel type
Possible values: GRE-IP, GRE-ETH
Status Tunnel status
Possible values:
Up
Down: and one of the following:
Reason: Configuration Missing
Reason: Lower Layer Down
Reason: No Route To Destination
Tunnel Source Interface Router interface anchoring the tunnel

Possible values:
-- (No interface is configured.)
Router Interface <router number>/<interface number>
Tunnel Physical Interface Physical interface bound to the router interface anchoring the tunnel
Possible values:
Empty string
(<port-type> <port-number>)
Tunnel Source Address Tunnel source IP address
Possible values:
-- (Tunnel address is not configured.)
<IPv4 or IPv6 unicast address>/<prefix length>
Tunnel Destination Tunnel destination IP address

Possible values:
-- (Tunnel destination IP address is not configured.)
IPv4 or IPv6 unicast address
Up For (seconds) Tunnel uptime

Possible values: Time in seconds; Display hint: ddd Days, hh:mm:ss
Tunnel Encapsulated Packets Number of Rx packets since tunnel uptime
Tunnel Decapstulated Packets Number of Tx packets since tunnel uptime

error is detected.
Tunnel already exists with a You tried changing the type of Delete the tunnel and then create a
different type an existing tunnel from gre-ip new tunnel (same index as deleted
to gre-eth, or vice versa. tunnel) with the new type.
Create a new tunnel (new index) of the
new type.
SVI type must be GRE SVI type is not GRE. Bind to SVI of type GRE.
Profile type must be p-bit to Profile type is not p-bit to

DSCP DSCP.
The address is assigned to You tried to configure the Assign a unique address to the tunnel.
another interface tunnel with an address of an
already existing tunnel or
router interface.
Tunnel may not be anchored to You assigned to the router Assign another IP address.
loopback interface interface anchoring the tunnel
an address of a loopback
interface.
Tunnel source may not be

anchored to loopback interface
Configure either source address You tried to configure the Remove one of the configurations:
or interface, not both router interface anchoring the either the address or interface.
tunnel with both an address
and interface.
Source and destination must be You tried to configure tunnel Define destination and source with
both IPv4 or both IPv6 destination with an IPv4 same type of IP address both IPv4 or
address while the tunnel both IPv6.
source is an IPv6 address.
You tried to configure tunnel
source with an IPv4 address
while the tunnel destination is
an IPv6 address.
Too many mappings You tried configuring more

than one mapping per tunnel.
No such mapping You tried to delete a

nonexistent mapping.
Too many NHS You tried configuring more han

one NHS for the tunnel.
No such NHS You tried to delete a

nonexistent NHS.

Examples
GRE-ETH Tunnels at Router

The following example shows:
A router configured with a router interface facing the IP transport network.
Two GRE-ETH tunnels configured using two GRE interfaces at the router and
bound to the Ethernet attachment circuit (flows) using SVI of type GRE.
exit all
config
port
svi 1
no shutdown
exit
svi 2 gre
no shutdown
exit
svi 3 gre
no shutdown
exit
exit
flows
classifier-profile "v100" match-any
match vlan 100
exit
match vlan 200
exit
flow "user_in"
classifier "untagged"
egress-port svi 1
no shutdown
exit
flow "user_out"
classifier "all"
ingress-port svi 1
no shutdown
exit
flow "tunnel1_in"
classifier "v100"
egress-port svi 2
no shutdown
exit
flow "tunnel1_out"
classifier "v100"
ingress-port svi 2
no shutdown
exit
flow "tunnel2_in"

classifier "v200"
egress-port svi 3
no shutdown
exit
flow "tunnel2_out"
classifier "v200"
ingress-port svi 3
no shutdown
exit
exit
router 1
interface 1
address 20.20.20.20/24
bind svi 1
no shutdown
exit
tunnel-interface 1 gre-eth
no shutdown
tunnel-source router-interface 1
tunnel-destination 30.30.30.30
bind svi 2
exit
no shutdown
bind svi 3
exit
exit
exit
OAM above GRE Tunnel

The following example shows how to configure OAM above a GRE tunnel. This is
recommended when configuring a GRE tunnel.
Create a policer profile zero configured with zero values (EIR, EBS).
Configure a GRE tunnel.
Configure a MEP bound to a physical port, where the flow to the GRE tunnel
starts from (in our case Ethernet 0/3) with the relevant VLAN.
Configure a Fault Propagation rule that stops GRE data transmission if the
MEP is in fail status (LOC). This is done by changing the flow policer to policer
with zero values. (Flow 3 from UNI toward SVI GRE tunnel)
configure
echo "QoS - Configuration"
# QoS - Configuration
qos
policer-profile "zero"
bandwidth eir 0 ebs 0
exit
exit

no shutdown
bind svi 2
exit
exit
exit
configure
oam
echo "OAM CFM Configuration"
# OAM CFM Configuration
cfm
maintenance-domain 1
name string "MD1"
maintenance-association 1
name string "MA1"
ccm-interval 3.33ms
classification vlan 100
mep 1
bind ethernet 0/3
remote-mep 10
ccm-priority 7
direction up
client-md-level 4
no shutdown
exit
exit
exit
exit
exit
fault
echo "Fault Propagation Configuration"
# Fault Propagation Configuration
fault-propagation mep 1 1 1 to policer flow "3"
action-on-group policer-swap "zero"
trigger oam-cfm-loc
exit
exit
exit
8.5 Fat Pipe Detection and Rate Limiting

In some applications, a 10G data pipe is distributed by ECMP over several paths,
to load balance the traffic. Some of the paths may have a limited BW (low-rate
links), posing a problem if the ECMP distribution results in high BW sessions going
over the same limited path congestion and drops for all traffic going over this
path.
The Fat pipe mechanism allows detection and rate limiting of these sessions to
avoid such congestion. It allows the operator to detect such sessions according
8-94 Fat Pipe Detection and Rate Limiting ETX-2i

to predefined attributes and BW thresholds, and once detected, rate limits these
sessions per user configuration.
Rate limiting is released, once the session rate drops below a configured value.
Fat pipe detection supports up to ten simultaneous detected and policed sessions
(micro flows).
Applicable Products
This feature is applicable to ETX-2i-10G half 19 only.
Standards
N/A
Benefits
Minimizes traffic congestion and dropped packets in network
Activation of Fat pipe detection requires you to create and configure a Fat pipe
detection profile, and then bind it to an Ethernet port (see Configuring Ethernet
Port Parameters).
You can bind up to two Ethernet ports to a Fat pipe detection profile.
You must configure the following in the Fat pipe detection profile:
Search key used for Fat pipe differentiation; can include up to five of the
following L2-L4 packet attributes: dst-mac, src-mac, vlan, p-bit, inner-vlan,
inner-p-bit, dscp, ip-precedence, tos, protocol, src-ip-address, dst-ip-address,
l4-src-port, l4-dst-port
Note Only IPv4 is supported.
Policer BW profile a preconfigured two-rate three-color policer BW profile:

Used to rate limit a Fat pipe session
Its CIR+EIR rate is used as the criteria to declare Fat pipe found and issue
the policer.
When traffic goes below the defined CIR rate for a defined amount of
time (see next parameter), the Fat pipe policer is released.
Release hold time the amount of time that the Fat pipe policer must stay
below the defined CIR rate, in order to release the policer.
Once you have bound the created Fat pipe detection profile to an Ethernet port,
it begins identifying and rate limiting up to ten high BW sessions simultaneously.
Fat pipe detection works as follows:
1. The Fat pipe search algorithm looks for exceptionally high BW sessions (up to
ten simultaneous sessions; not including IPv6 packets) differentiated by the
search key defined in the Fat pipe detection profile. The criteria to declare
ETX-2i Fat Pipe Detection and Rate Limiting 8-95

that a Fat pipe has been detected is the CIR+EIR (PIR) rate in the policer BW
profile.
It takes the algorithm one second to detect the first high-BW session, and
1+n seconds to detect the following n high-BW sessions.
2. Once the exceptionally high-BW sessions are found, the Fat pipe detection
procedure binds its defined two-rate three-color policer to the sessions, in
order to rate limit the BW of these sessions.
3. The sessions are monitored; once their BW drops below the CIR defined in
the policer for the defined release hold time, the policer is released and
alarms are cleared. Simultaneously, the search for additional high BW
sessions is resumed (Step 1).
At any time, you can display the information of active and history (closed) Fat
pipes of an Ethernet port (refer to Displaying Fat Pipe Information).
Factory Defaults
By default, ETX-2i-10G half 19 does not have a Fat pipe detection profile.
The default release-hold-time of a newly created Fat pipe detection profile is 60
seconds.
Configuring Fat Pipe Detection

The following section describes how to create a profile with Fat pipe detection
mechanism attributes. A single profile is supported.
To add a fat pipe detection profile:
1. Navigate to configure port.
The config>port# prompt is displayed.
2. Type fat-pipe-detection-profile <profile-name>
A Fat pipe detection profile with the specified name is created and the
config>port>fat-pipe-detection-profile(<profile-name>)$ prompt is
displayed.
Configuring a search key for Fat pipe search-key [dst-mac] [src-mac] [vlan] [p-bit] [inner- The search key used for Fat
differentiation vlan] [inner-p-bit] [dscp] [ip-precedence] [tos] pipe differentiation can include
[protocol] [src-ip-address] [dst-ip-address] [l4-src-port] up to five L2-L4 packet
[l4-dst-port] attributes.
Notes:
The order of the attributes
is significant.
The search does not
recognize L3-L4 fields of
IPv6 packets.
8-96 Fat Pipe Detection and Rate Limiting ETX-2i

Configuring Policer BW profile policer profile <bw_profile> bw_profile policer BW profile

name to be used for Fat pipe
rate limiting and for find and
clear criteria
T
Configuring time that session BW release-hold-time <time> time Time that session BW is
must remain below defined CIR in required to remain below CIR in
order to release policer. order to release the policer
from the session, and release
Fat pipe from active Fat pipe
list.
seconds
Deleting a Fat pipe Detection Profile

You can delete a fat pipe detection profile only if it is not bound to any port.
To delete a fat pipe detection profile:
2. Type no fat-pipe-detection-profile <profile-name>.
The fat-pipe-detection-profile of the specified name is deleted if it is not
bound to any port.
Example
The following example describes how to define a fat pipe detection profile named
e2000, with regular policer 2000M, and searching according to source MAC
address.
To configure regular policer 2000M:
config qos policer-profile "2000M" bandwidth cir 500000 cbs
32000 eir 500000 ebs 32000
To define Fat pipe detection profile named e2000:
con port fat-pipe-detection-profile e2000
policer profile 2000M release-hold-time 30
search-key src-mac
exit all
8.6 Layer-2 Control Processing

ETX-2i 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.
ETX-2i Layer-2 Control Processing 8-97

Applicable Products
This feature is applicable to all ETX-2i products.
Standards
IEEE 802.3
Benefits
Layer 2 Control Protocol can be passed or filtered to Ethernet virtual connections.
ETX-2i can be configured to pass through Layer-2 control frames (including other
vendors L2CP frames) across the network, to peer supported protocols, or to
discard the L2CP frames. You can perform protocol tunneling with MAC address
swap, and discard the Loopback packets (Ethertype 0x9000).
You can create profiles to define the handling of Layer-2 Control Protocol traffic.
You then assign the required profile to an Ethernet port or to a flow (see
Configuring Ethernet Port Parameters and Configuring Flows, respectively), and
display the Layer-2 control processing statistics for an Ethernet port (see
Displaying Layer-2 Control Processing Statistics).
Factory Defaults
ETX-2i provides a default L2CP profile named L2cpDefaultProfile, configured as
follows:
For MAC hex byte 0x00 through 0x2f, action = tunnel
Default action = tunnel
When a new L2CP profile is created, it has the same configuration as
L2cpDefaultProfile.
Configuring Layer 2 Control Processing
Adding Layer 2 Control Processing Profiles

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

3. Configure the L2CP profile as needed (see Configuring Layer 2 Control

Processing Profile Parameters).
Deleting Layer 2 Control Processing Profiles

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

To configure an L2CP profile:
1. Navigate to configure port l2cp-profile <l2cp-profile-name> to select the
L2CP profile to configure.
The config>port>l2cp-profile(<l2cp-profile-name>)# prompt is displayed.
Specifying the default action for default {discard | tunnel}

undefined control protocols

Specifying the L2CP action for MAC mac <mac-addr-last-byte-value-list><mac-addr> mac-addr can be either of the
addresses (discard, tunnel, or peer) {discard | tunnel | peer} following:
Long MAC address, i.e. full
valid MAC adress [xx-xx-xx-
xx-xx-xx]
For example:
01-80-c2-00-00-02
Possible values:
01-80-c2-00-00-xx, where
xx= 0H-10H, 20H-2FH;
01-cc-cc-cc-cc-cc
01-cc-cc-cc-cc-cd
Short MAC address, i.e. last
byte of the control protocol
MAC address
[0x00..0x10,0x20..0x2F]
For example: 0x02 is the
short MAC address of
01-80-c2-00-00-02.
Possible values: 0H-10H,
20H-2FH
discard L2CP frames are
discarded.
tunnel L2CP frames are
forwarded across the network
as ordinary data.
peer ETX-2i peers with the
user equipment to run the
protocol. L2CP frames are
forwarded to the ETX-2i CPU.
Unidentified L2CP frames are
forwarded across the network
as ordinary data.
Note: Peer action cannot be
used with the MAC addresses
01-cc-cc-cc-cc-cc and 01-cc-cc-
cc-cc-cd.
Typing no mac
<mac-addr-last-byte-value-list>
<mac-addr> removes the
action for the specified MAC
address.
Defining a Loopback protocol for protocol loopback discard Typing no protocol loopback
discarding removes the action for the
Loopback protocol.

Choosing a protocol for tunneling protocol { lacp | stp | vtp | cdp | lldp | pvstp| pagp | udld | Typing no protocol { lacp | stp |
and specifying MAC swap if desired dtp } tunnel mac-change [<mac-address>] vtp | cdp | lldp | pvstp| pvstp |
pagp | udld | dtp } removes the
action for the specified
protocol.
Examples
To add L2CP profile named layer2ctrl1 with discard action for hex byte 0x01 and
0x03 (short MAC format):
exit all
ETX-2i#configure port
l2cp-profile layer2ctrl1
ETX-2i>config>port>l2cp-profile (layer2ctrl1)#mac 0x01 discard
mac 0x03 discard
exit all
To add L2CP profile named layer2ctrl2 with tunnel action for long MAC addresses
01-80-c2-00-00-00 and 01-80-c2-00-00-01 (long MAC format):
exit all
ETX-2i#configure port
l2cp-profile layer2ctrl2
ETX-2i>config>port>l2cp-profile(layer2ctrl2)#
mac 01-80-c2-00-00-00 tunnel
mac 01-80-c2-00-00-01 tunnel
exit all
To add L2CP profile 1 that uses LACP protocol for tunneling with L2CP MAC swap:
ETX-2i#configure port l2cp-profile 1
ETX-2i>config>port>l2cp-profile(1)#
protocol lacp tunnel mac-change 01-23-45-67-89-DD
exit all
To display the layer2ctrl1 L2CP profile:
ETX-2i#configure port l2cp-profile layer2ctrl1
ETX-2i>config>port>l2cp-profile(layer2ctrl1)# info detail
mac 0x00 tunnel
mac 0x01 discard
mac 0x02 tunnel
mac 0x03 discard
mac 0x04 tunnel
mac 0x05 tunnel
mac 0x06 tunnel
mac 0x07 tunnel
mac 0x08 tunnel
mac 0x09 tunnel
mac 0x0a tunnel
mac 0x0b tunnel
mac 0x0c tunnel
mac 0x0d tunnel
mac 0x0e tunnel
mac 0x0f tunnel

mac 0x10 tunnel

mac 0x20 tunnel
mac 0x21 tunnel
mac 0x22 tunnel
mac 0x23 tunnel
mac 0x24 tunnel
mac 0x25 tunnel
mac 0x26 tunnel
mac 0x27 tunnel
mac 0x28 tunnel
mac 0x29 tunnel
mac 0x2a tunnel
mac 0x2b tunnel
mac 0x2c tunnel
mac 0x2d tunnel
mac 0x2e tunnel
mac 0x2f tunnel
default tunnel
mac "01-80-c2-00-00-00" tunnel
mac "01-80-c2-00-00-01" tunnel
mac "01-80-c2-00-00-02" tunnel
mac "01-80-c2-00-00-03" tunnel
mac "01-80-c2-00-00-04" tunnel
mac "01-80-c2-00-00-05" discard
mac "01-80-c2-00-00-06" tunnel
mac "01-80-c2-00-00-07" tunnel
mac "01-80-c2-00-00-08" tunnel
mac "01-80-c2-00-00-09" tunnel
mac "01-80-c2-00-00-0a" tunnel
mac "01-80-c2-00-00-0b" tunnel
mac "01-80-c2-00-00-0c" tunnel
mac "01-80-c2-00-00-0d" tunnel
mac "01-80-c2-00-00-0e" tunnel
mac "01-80-c2-00-00-0f" tunnel
mac "01-80-c2-00-00-10" tunnel
mac "01-80-c2-00-00-20" tunnel
mac "01-80-c2-00-00-21" tunnel
mac "01-80-c2-00-00-22" discard
mac "01-80-c2-00-00-23" tunnel
mac "01-80-c2-00-00-24" tunnel
mac "01-80-c2-00-00-25" tunnel
mac "01-80-c2-00-00-26" tunnel
mac "01-80-c2-00-00-27" tunnel
mac "01-80-c2-00-00-28" tunnel
mac "01-80-c2-00-00-29" tunnel
mac "01-80-c2-00-00-2a" tunnel
mac "01-80-c2-00-00-2b" tunnel
mac "01-80-c2-00-00-2c" tunnel
mac "01-80-c2-00-00-2d" tunnel
mac "01-80-c2-00-00-2e" tunnel
mac "01-80-c2-00-00-2f" tunnel
mac "01-00-0c-cc-cc-cc" tunnel
mac "01-00-0c-cc-cc-cd" discard
default tunnel
ETX-2i#configure port l2cp-profile layer2ctrl1

ETX-2i>config>port>l2cp-profile(layer2ctrl1)# info
mac "01-80-c2-00-00-05" discard
mac "01-80-c2-00-00-22" discard
mac "01-00-0c-cc-cc-cd" discard
Note
The info detail command displays all actions (including the default action (in
above example, tunnel). The info command only displays non-default actions.
To delete L2CP profile layer2ctrl1:

no l2cp-profile layer2ctrl1
8.7 Link Layer Discovery Protocol (LLDP)

LLDP is a standard layer-2 protocol that allows Ethernet network devices to
advertise information about themselves, and receive information from other
Ethernet network devices. The devices store this information in local MIB
databases accessible via SNMP; therefore the information can be accessed by a
network management system.
Applicable Products
Standards
IEEE 802.1AB-2009
IEEE 802.3az-2010
Benefits
Automated discovery of devices simplifies management and network
maintenance, and reduces general setup costs of new equipment.
LLDP is a neighbor discovery protocol that enables network devices to advertise
information to peer devices on the same physical LAN and store information
about the network. LLDP is supported for all Ethernet ports, including the
management port and Ethernet ports that are bound to LAG. LLDP information is
exchanged by means of LLDP packets.
Note LLDP runs on physical links and is configured on each individual physical port; it
neither runs nor is configured over the LAG logical layer.
LLDP Bridge Types

LLDP works according to the following bridge types:
ETX-2i Link Layer Discovery Protocol (LLDP) 8-103

Nearest bridge The propagation of LLDP packets is limited to a single

physical link, and is stopped by any type of bridge.
Nearest customer The propagation of LLDP packets is limited by customer

bridge bridges.
Nearest non-TPMR The propagation of LLDP packets is limited by non-TPMR

bridge bridges. Typically this mode is used in provider bridged
networks.
TPMR (Two-port MAC Relay) indicates a bridge that has only two
externally-accessible bridge ports, and supports a subset of the regular functions
of a MAC bridge. A TPMR bridge is transparent to all frame-based
media-independent protocols except for packets with destinations that terminate
at the bridge, or packets with destinations that are reserved MAC addresses that
are not defined for forwarding by the relay function of the TPMR bridge.
LLDP Packets
LLDP packets are sent periodically between ETX-2i and neighboring devices, in
order to obtain neighbor information. The information from the LLDP packets is
stored for a period of time, determined by the time-to-live (TTL) value in the
received packet. When the TTL expires, the LLDP information is discarded.
LLDP packets contain the following information:
Destination MAC Set to 01-80-C2-00-00-00 (nearest customer bridge),

address 01-80-C2-00-00-03 (nearest non-TPMR bridge) or
01-80-C2-00-00-0E (nearest bridge), depending on
configuration
Source MAC Set to port MAC address

address
EtherType Set to 0x88CC
LLDP Protocol Contains a variable number of information units called

Data Unit TLVs: mandatory TLVs, optional TLVs, and an EndOfLLDPDU
(LLDPDU) TLV. LLDPDUs are always sent untagged. TLVs consist of
basic management TLVs and organizationally specific TLVs.
The organizationally specific TLVs are differentiated by
IEEE 802.1, IEEE 802.3, and more.
Table 8-11. Basic Management TLVs
TLV Name Description TLV Appears in

LLDPDU
Chassis ID Management MAC address Mandatory
Port ID Interface name per RFC 2863 Mandatory
Time To Live Time in seconds that specifies the validity Mandatory

period of the information
Port Description ifDescr per RFC 2863, which is port name Optional
8-104 Link Layer Discovery Protocol (LLDP) ETX-2i

TLV Name Description TLV Appears in

LLDPDU
System Name Device name as configured by CLI (per Optional

RFC 3418 )
System Description sysDescr per RFC 3418 includes: Optional

Device name
HW version
SW version
System Capabilities Includes indications for the following: Optional

MAC bridge
Router
C-VLAN component of VLAN bridge
S-VLAN component of VLAN bridge
Two-port MAC relay (TPMR)
Management Address Management IP address Optional
End Of LLDPDU N/A; indicates end of LLDPDU Mandatory
Table 8-12. Organization-Specific IEEE 802.1 TLVs
TLV Name Description
Protocol Identity Protocols configured on the port. The following protocols

are supported:
LLDP
EFM if configured
CFM
LAG-LACP if the port is in a LAG group
ESMC if tx-ssm is enabled for the port)
ERP-v2 if G.8032 ring is configured on the port
Table 8-13. Organization-Specific IEEE 802.3 TLVs
TLV Name Description
MAC/PHY Configuration/Status Autonegotiation support/status

Autonegotiation advertised capability
MAU type (data rate and duplex mode)
Maximum Frame Size Egress MTU

Factory Defaults
By default, no LLDP parameters are configured for ports. The system LLDP
parameters have the default values shown in the following table.
hold-multiplier 4
shutdown shutdown LLDP is administratively enabled for

all relevant interfaces.
tx-interval 30 Value is in seconds.
Configuring LLDP
LLDP parameters are configured at the following levels:
Global LLDP parameters that apply to the entire device are configured at the
system level.
Port LLDP parameters are configured at the Ethernet port level, to specify
which TLVs to send for the port.
Note In order for LLDP to function properly for the port, an L2CP profile must be
associated with it that specifies peer action for MAC address 01-80-C2-00-00-00,
01-80-C2-00-00-03 or 01-80-C2-00-00-0E, depending on the LLDPDUs
destination addresses configured.
System Parameters
This section explains how to configure global parameters such as bridge type, as
well as enable or disable LLDP for the device.
To configure LLDP system parameters:
1. Navigate to configure system lldp.
The config>system>lldp# prompt is displayed.
Specifying how long device should hold hold-multiplier

received information before discarding
it
Specifying the amount of time between tx-interval <seconds>

LLDP transmissions
Enabling or disabling LLDP for device shutdown Enter no shutdown to enable LLDP.
Port Parameters
This section explains how to configure which TLVs to transmit for the port for the
different LLDP bridge types (see Table 8-14 to Table 8-16 for details on TLVs).

To configure LLDP parameters for Ethernet port:

1. Navigate to configure port ethernet [<slot>/]<port>.
The prompt config>port>eth([<slot>/]<port>)# is displayed.
Enabling or disabling 802.1-protocol-identity {lldp | efm |

transmission of the specified cfm | lag-lacp | rstp-mstp | esmc
protocol in the IEEE 802.1 |erp-v2}
protocol identity TLV (see
Table 8-15)
Enabling or disabling customer-bridge-802.3 mac-phy-configuration

transmission of IEEE 802.3 TLVs [mac-phy-configuration] MAC/PHY
(see Table 8-16) in customer [power-via-mdi] [max-frame-size] Configuration/Status TLV
bridge mode power-via-mdi not
supported
max-frame-size maximum
Frame Size TLV
Enabling or disabling customer-bridge-basic-management port-description port

transmission of basic [port-description] [sys-name] description TLV
management TLVs (see [sys-description] [sys-capabilities] sys-name system name
Table 8-14) in customer bridge [management-address] TLV
mode
sys-description system
description TLV
sys-capabilities system
capabilities TLV
management-address
management address TLV
Specifying transmission mode in customer-bridge-mode {tx | rx | tx Transmit LLDP packets

customer bridge mode tx-rx} rx Receive LLDP packets
tx-rx Transmit and Receive
LLDP packets
Enabling or disabling nearest-bridge-802.3 mac-phy-configuration

(see Table 8-16) in nearest [max-frame-size] Configuration/Status TLV
bridge mode max-frame-size maximum
Frame Size TLV

Enabling or disabling nearest-bridge-basic-management port-description port

management TLVs (see [sys-description] [sys-capabilities] sys-name system name TLV
Table 8-14) in nearest bridge [management-address]
mode
description TLV
capabilities TLV
management-address
management address TLV
Specifying transmission mode in nearest-bridge-mode {tx | rx | tx-rx} tx Transmit LLDP packets

nearest bridge mode rx Receive LLDP packets
tx-rx: Transmit and Receive
LLDP packets
Enabling or disabling non-tpmr-802.3 mac-phy-configuration

(see Table 8-16) in non-TPMR [max-frame-size] Configuration/Status TLV
bridge mode max-frame-size Maximum
Frame Size TLV
Enabling or disabling non-tpmr-basic-management port-description port

management TLVs (see [sys-description] [sys-capabilities] sys-name system name TLV
Table 8-14) in non-TPMR bridge [management-address]
mode
description TLV
capabilities TLV
management-address
Management address TLV
Specifying transmission mode in non-tpmr-bridge-mode {tx | rx | tx Transmit LLDP packets

non-TPMR bridge mode tx-rx} rx Receive LLDP packets
tx-rx Transmit and Receive
LLDP packets
Viewing detailed information show neighbors-details

about neighboring devices
Viewing brief summary of show neighbors-summary

neighboring devices
Viewing LLDP statistics show statistics
Clearing LLDP statistics clear-statistics
Example
The following example illustrates how to configure LLDP in the system.

#*********************************Configuring_LLDP in
system*****************
conf system lldp
tx-interval 10
hold-time 2
bridge-type nearest-bridge
no shutdown
exit all
#***************************Configuring_L2CP_Profile***********
**************
configure port
l2cp-profile lldp
mac 0x0e peer
exit all
configure port eth 1

l2cp profile lldp
no shutdown
exit all
#*****************************Configuring_LLDP in
port***********************
configure port ethernet 1 lldp
nearest-bridge-mode tx-rx
nearest-bridge-basic-management sys-description
nearest-bridge-basic-management sys-name
nearest-bridge-basic-management sys-capabilities
nearest-bridge-basic-management management-
address
nearest-bridge-basic-management port-description
nearest-bridge-802.3 mac-phy-configuration max-
frame-size
Viewing LLDP Neighbor Information

You can display detailed information about neighboring devices or display a brief
summary of neighboring devices.
To display detailed information about neighboring devices:

1. Navigate to configure port ethernet [<slot>/]<port> lldp.
The prompt config>port>eth([<slot>/]<port>)>lldp# is displayed.
2. Enter show neighbors-details.
For example:
ETX-2i# configure port ethernet 1 lldp
ETX-2i>config>port>eth(1)>lldp# show neighbors-details
Name : RAD-ETX-2i ID : 00 01 00 00 00 03 02
Basic-Management Info
Bridge-Type : NEAREST
Chassis-type : MAC_ADDRESS
Chassis-id : 00:01:00:00:00:03
Port-Type : Locally Assigned
Port-id : eth-0/1

Port-Descr : Ethernet Port

System-name : RAD-ETX-205
System-Descr : RAD SWITCH
System Capabilities : REPEATER, MAC_BRIDGE
Enabled Capabilities : REPEATER, MAC_BRIDGE
Remote Management Address
Type : IPV4
Address : 192.168.200.10
802.1
Port-vlanId : 10
Port-protocol Vlan-id : --
Vlan Name : --
Protocol Identity : Link-aggregation, OAM, ELMI
VID Usage : --
Management VID : --
Link-Aggregation
Link Aggregation Status : Enabled
Lag-portId : 100
802.3
MAC/PHY configuration
Auto Negotiation Support Status : Supported
Auto Negotiation Current Status : Enabled
Auto-negotiation-advertised Capability : --
Operational MAU Type : --
POWER/MDI configuration
Port-class : --
MDI Support Status : --
MDI Current Status : Disabled
PSE Pair Control Ability : --
Power Class : --
Max Frame Size : 1500
8.8 MLDv2 Snooping

Multicast Listener Discovery Version 2, or MLDv2, is a protocol used by IPv6
routers to discover multicast listeners on attached links and addresses that are of
interest to them.
Multicast Listener Discovery Version 2 Snooping, or MLDv2 Snooping, is a practice
employed by IPv6 bridges to reduce multicast traffic by analyzing MLDv2
messages and limiting multicast traffic to ports interested in it.
Applicable Products
This feature is applicable to ETX2i and ETX-2i-B 2u with 10 SFP.
Standards
ETX-2i and ETX-2i-B 2u with 10 SFP support MLD Snooping version 2.
8-110 MLDv2 Snooping ETX-2i

Note MLDv1 is not supported.
Benefits
Enables reduction in traffic by reducing the number of unneeded packets on the
network.
Factory Defaults
By default, MLD Snooping is disabled.
Table 8-14. MLD Snooping Factory Defaults
router port aging timer 260 seconds
member port aging timer 260 seconds
ETX-2i supports MLD Snooping for both VLAN-unaware and VLAN-aware bridges.
MLDv2 snooping can be enabled and disabled per bridge. In VLAN-aware bridges
it can also be enabled and disabled per VLAN. If snooping is disabled at the bridge
level, the per-VLAN configuration is ignored. This allows MLDv2 snooping to be
disabled on the entire bridge, without changing the per-VLAN configuration (e.g.
for troubleshooting).
When MLDv2 snooping is enabled, the bridge keeps two lists, per port (in VLAN-
unaware bridges) or per port and VLAN (in VLAN-aware bridges).
Router port list Ports from which MLDv2 router traffic is received
Member port list Pairs of port and multicast group address, to which
multicast traffic is to be forwarded
The bridge listens to messages on all MLDv2-snooping-enabled ports and

dynamically adds and removes ports to the router and member port lists.
The router-port list is maintained per port in VLAN-unaware bridges and per port
and VLAN in VLAN-aware bridges.
ETX-2i can receive multicast traffic from all ports and VLANs. MLDv2 snooping
builds a multicast forwarding database, rather than always forwarding multicast
traffic to all ports (in VLAN-unaware bridges) or all ports of a VLAN (in VLAN-
aware bridges).
ETX-2i supports MLDv2 Snooping on up to 16 VPNs.
Note Snooping is only enabled on a VLAN if it is enabled at both bridge and VLAN
levels. A command at either level does not change configuration of other levels.
ETX-2i MLDv2 Snooping 8-111

MAC-based Forwarding Addresses

MLDv2 snooping supports forwarding databases that are either IPv6-based or
MAC-based. The ETX-2i has a MAC-based forwarding database. However, there
are some limitations when using MAC-based address forwarding.
When using a MAC-based forwarding database, IPv6 addresses are mapped to
MAC addresses by ANDing their last 32 bits with 0xffffffff, and adding a prefix of
0x3333. The IPv6 multicast address group ID, however, is 112 bits long. Since the
higher 80 bits of the group ID are omitted when mapping IPv6 addresses to MAC
addresses, then if the bits left of the right-most 32 bits are used in a group ID,
then multiple multicast IP addresses could be mapped to the same MAC address.
Since multiple IPv6 addresses could be mapped to single MAC addresses, the
following limitations apply:
An IPv6 multicast address has the following format:
ffxx.xxxx.xxxx.xxxx.xxxx.xxxx.zzxx.xxxx. If the bridge receives a multicast IPv6
address with zz = 0xff or 0x00, MLDv2 snooping is not performed on the
packet, and it is forwarded to all ports in the VLAN except the port it was
received from. These address scopes contain special addresses, e.g. all
MLDv2-capable routers, which must be forwarded to all ports.
To avoid one MAC address affecting multiple IPv6 addresses, make use of
only the lower 32 bits when choosing IPv6 multicast addresses.
If the ETX-2i bridge receives a report asking to join a multicast group with an
address of ffxx.xxxx.xxxx.xxxx.xxxx.xxxx.zzxx.xxxx, where zz = 0xff or 0x00, the
mld_snooping_unsupported_ip event is generated.
Note Data for unsupported addresses is forwarded to all ports, including ones behind
which there is no host interested in the address. To avoid this, use addresses out
of the unsupported ranges.
ETX-2i maintains a table of learned multicast IPv6 addresses. When it receives a

report asking to join a group that maps to the same MAC address as a different
group in that table, the new address ignored and the mld_snooping_duplicate_ip
event is generated.
Note Data for the duplicate address will be forwarded to the ports used by the one
already in the forwarding database. Duplicate addresses should either be
changed or configured statically.
Note
ETX-2i does not analyze group-specific and group-and-source-specific queries.
These queries are sent to group addresses, (unlike general queries, which are
sent to a fixed address). Information that could be learned from these queries
will eventually be learned from the periodic general queries, but it will take more
time for MLDv2 Snooping to adjust to that information.

Port Aging
Router port is the ETX-2i port facing the multicast router. Router port is learned
from receiving general queries and can age out. ETX-2x sets the router port aging
timer when a port is added to the router port list.
The timer is rearmed when receiving an MLDv2 general query or an IPv6 PIM
hello message with source address different from 0::0.
If the timer expires, the port is removed from the router port list.
The router port list is maintained per bridge port in VLAN-unaware bridges, or
per VLAN and bridge port in VLAN-aware bridges.
A member port is the ETX-2i port facing a multicast client. Member port is learned
from report messages and is subjected to agin. The ETX-2i sets the member port
aging timer when a port joins an IPv6 multicast group.
The timer is rearmed when receiving an MLDv2 report message.
If the timer expires, the port is removed from the multicast group forwarding
table.
The member port list is maintained per bridge port and multicast group in
VLAN-unaware bridges, or per VLAN, bridge port and multicast group in VLAN-
aware bridges.
ETX-2i must listen to MLDv2 general queries, sent to the link-scope all-nodes
multicast address (FF02::1), on all ports and all VLANs. General queries are sent
periodically by MLDv2 queries, to find the ports on which group members reside.
If a general query is received the bridge must:
Forward the query to all ports (VLAN-unaware bridges) of all ports in the
VLAN (VLAN-aware bridges) except the receiving port.
If the receiving port is not on the router-port list, add it to the list and set
the aging timer.
If the receiving port is on the router-port list, rearm its aging timer.
ETX-2i must listen to MLDv2 reports, sent to FF02::16, to which all MLDv2
multicast routers listen, on all ports and all VLANs. Reports are sent by listeners
as responses to router queriers or when asking to join or leave a multicast group.
If MLDv2 report is received the bridge must:
Peruse the report and update the member port list accordingly; that is, if a
host asks to join a group, add the receiving port to the member port list of
the group. Conversely, if a host is leaving a group the receiving port is not
immediately removed from the member list, since there may be other hosts
interested in the group on the port. Ports are only removed from the member
port list if the aging timer expires.
Forward it to all router ports (in VLAN-unaware bridges) or all router ports in
the VLAN (in VLAN-aware bridges).
If the receiving port is not on the member port list, add it to the list and set
the aging timer.
If the receiving port is on the member port list, rearm the aging timer.
ETX-2i must receive all multicast traffic from all ports and VLANs. If multicast
packet that is not MLDv2 protocol traffic is received, the device must:

In case of an unregistered multicast packet, i.e. a packet for a group with no

current members, forward it to all router ports (in VLAN-unaware bridges) or
all ports in the VLAN (in VLAN-aware bridges).
In case of a registered multicast packet, forward it to:
All router ports (in VLAN-unaware bridges) or all router ports in the VLAN
(in VLAN-aware bridges).
All member ports (in VLAN-unaware bridges) or all member ports in the
VLAN (in VLAN-aware bridges) that are members of the multicast group.
Note A static router port is always on the router port list; it is not subjected to timer
aging.
A static member port is always on the member port list; it is not subjected to
timer aging.
Source-Specific Multicast
Source-Specific Multicast, or SSM, is a multicast service allowing hosts to
subscribe to specific multicast sources, and thus further reducing multicast traffic
in the network.
In addition to subscribing to a multicast group, hosts may ask to receive traffic
from a specific host. ETX-2i, however, does not maintain a per-source database.
This means that multicast traffic sent to a specific group will be forwarded to all
members of that group, regardless of whether or not they are interested in the
traffic source.
MLD Snooping and Ethernet Ring Protection

When an ERP ring port changes state, all nodes in the ring receive a Signal Failure
(SF) message. If such a signal is received from a port on which MLDv2 snooping is
enabled, ETX-2i removes from the multicast forwarding database all the
addresses that are forwarded to either ring port (the addresses are removed
from all ports, including ones that are not ring members). This causes multicast
traffic to be forwarded to both ring ports until the new topology is learned from
subsequent reports and queries.
Configuring MLD Snooping

MLD Snooping must be enabled globally. VLAN related commands and arguments
apply only to VLAN-aware bridges.
To configure MLD Snooping:

1. At the config>bridge <x> prompt, enter mld-snooping.
Where x is the bridge on which you want to configure MLD Snooping.
The config> bridge(x)> mld-snooping# prompt is displayed.

Enable/disable MLD snooping [no]shutdown [no] shutdown enables/disables

MLD Snooping globally on the
bridge. In addition, if the bridge is
VLAN aware you can enable and
disable MLD snooping on specific
VLANs, using the vlan command.
Configure host aging interval host-aging-interval<seconds> Possible values: 311264

Default: 260
Configure router aging interval router-aging-interval Possible values: 311264

Default: 260
Display MLD snooping status show status See Displaying MLD Snooping
Status.
Configure static multicast group static-group static-group <group-address> vlan

<vid> port <port-number-list>
no static-group <group-address>
[vlan <vid>]
Configure static router port static-router-port static-router-port vlan <vid> port

<port-number-list>
no static-router-port vlan <vid>
Configure MLD snooping VLANs vlan [no] vlan <vid-list>

If the command is repeated, it
does not replace the current
configuration; vid-list is either
added to the current configuration
or removed from it (using the no
option).
Displaying MLD Snooping Status

To display MLD Snooping status:
At the config>bridge x>mld-snooping# prompt, enter show status.
The MLD Snooping status is displayed.
Status output is displayed in the following format:
MLD Snooping Is Globally admin-state
MLD Snooping Is Enabled for VLAN snooping-vlans
Aging Interval
Host Ports (seconds): host-aging
Router Ports (seconds): router-aging
Router Ports:
VLAN Type Ports
------------------
r-v r-type r-ports

Host Ports:
VLAN IP Address Type Ports
----------------------------------------------------------
h-v h-ip h-type h-ports
Note
Port member tables are sorted by VLAN, then (the host port list) IP address, and
then type (static first).
MLD Snooping Status Example

MLD snooping is globally enabled
MLD Snooping Is Enabled for VLAN 1-100, 200
Aging Interval (seconds)
Host Ports : 260
Router Ports: 260
Router Ports:
VLAN Type Ports
------------------
1 static 1-5, 7
2000 learned 2, 7-10
Host Ports:
VLAN Group IP Address Type Ports
----------------------------------------------------------
100 ff00:1111:2222:3333:4444:5555:6666:7777 static 1-5, 7
2000 ff11:1111:1111:1111:1111:1111:1111:1111 learned 2, 7-10
Table 8-15. MLD Snooping Status Fields
admin-state MLD snooping admin state at bridge level; possible values: enabled,
disabled.
snooping-vlans VLANs for which MLD snooping is enabled
host-aging Aging time of host ports (in seconds)
router-aging Aging time of router ports (in seconds)
r-v VLAN the router ports of this entry are on; possible values: 1-4094.
r-type Type of this entry; possible values: static, learned
r-ports List of router ports
h-v VLAN the host ports of this entry are on; possible values: 1-4094.
h-ip Multicast IPv6 address this entry is on
h-type Type of this entry; possible values: static, learned
h-ports List of host ports
8.9 Pseudowire Connections

A pseudowire (PW) bundle provides emulation of Layer-2 point-to-point
connection-oriented services over packet-switching networks (PSN). The PW
8-116 Pseudowire Connections ETX-2i

parameters define the way a payload is transported via the E1/T1 ports through
the PSN network. You can configure up to 64 PW bundles.
Note If you have performed shutdown and then no shutdown of a PW cross connect or
smart SFP port, you must perform shutdown and then no shutdown of the PW.
Applicable Products
This feature is applicable to devices that support smart SFP MiTOP functionality.
Standards
IETF RFC 5086 (CESoPSN)
IETF RFC 4553 (SAToP)
ITU-T Y.1413 (CESoPSN, SAToP)
ITU-T Y.1453 (CESoPSN, SAToP)
The device supports the CESoPSN and SAToP network encapsulation methods,
transmitting E1/T1 traffic over Ethernet (MEF 8) or UDP/IP packet-switched
networks. TDM PW is supported over G.8032 rings, for MEF 8 and UDP/IP.
Pseudowire Packet Structure

A PW packet comprises the following data components (see Figure 8-16):
Ethernet Header Contains the DA (destination MAC address), SA (local MAC

address), and Ethernet network type
PSN Header Defines the PSN transport type: Ethernet or UDP/IP
Control Word Data control as defined in the relevant IETF RFCs and drafts
Payload TDM service payload containing the actual traffic data
Figure 8-23. Basic PW Structure
Note The source MAC address is the egress port MAC address for MEF 8 (Ethernet)
PWs, or the MAC address of the egress router interface for UDP/IP PWs.
TDM Service Encapsulation

TDM traffic can be encapsulated over PSN in two modes:
ETX-2i Pseudowire Connections 8-117

CESoPSN CES (Circuit Emulation Services) over PSN, for framed E1/T1
traffic with or without CAS
SAToP Structure-Agnostic TDM over Packet, for unframed E1/T1

traffic
CESoPSN
The CESoPSN method is a structure-aware format for framed E1/T1 services. It
converts structured E1/T1 data flows into IP packets and vice versa with static
assignment of timeslots inside a bundle according to IETF RFC 5086 and
ITU-T Y.1413. The CESoPSN packet size is a multiple of TDM frame size.
Figure 8-17 illustrates CESoPSN encapsulation without CAS.
TDM Payload
L2/L3 Control
4 25 4 25 4 25 CRC Ethernet Packet
Header Word
FRG bits = 00 Frame Frame Frame

(no fragmentation) 1 2 N
4 25 4 25 4 25
Frame 1 Frame 2 Frame N
Figure 8-24. CESoPSN Encapsulation E1 without CAS, Bundle with Timeslots 4

and 25
CESoPSN with CAS is configurable in the following case only:

The corresponding E1 is configured to framed mode with CAS (with or
without CRC).
SAToP
The SAToP encapsulation method is used to convert unframed E1/T1 data flows
into Ethernet or IP packets and vice versa according to ITU-T Y.1413 and
IETF RFC 4553. It provides flexible packet size configuration and low end-to-end
delay.
L2/L3 Control Ethernet

TDM Payload CRC
Header Word Packet
FRG bits = 00
(no fragmentation)
TDM
Bitstream
N TDM Bytes
Figure 8-25. SAToP Encapsulation

Encapsulation over Different PSN Types

The pseudowire connections can be encapsulated by ETX-2i for the following
types of PSN transport networks:
UDP/IP (UDP over IP)
MEF 8 (Ethernet)
When the PSN type is UDP over IP, ETX-2i enables you to select the mode of
configuring the IP priority of the IP/UDP packet: DSCP or ToS. Once you select the
mode, you can configure the DSCP or ToS value.
Jitter Buffer
The packets of each pseudowire are transmitted by ETX-2i at essentially fixed
intervals toward the PSN. The packets are transported by the PSN and arrive to
the far end after some delay. Ideally, the PSN transport delay should be constant,
meaning the packets arrive at regular intervals (equivalent to the intervals at
which they were transmitted). However, in reality, packets arrive at irregular
intervals, because of variations in the network transmission delay. The term
Packet Delay Variation (PDV) is used to designate the maximum expected
deviation from the nominal arrival time of the packets at the far end device.
Note
The deviations from the nominal transmission delay experienced by packets are
referred to as jitter, and the PDV is equal to the expected peak value of the jitter.
However, nothing prevents the actual delay from exceeding the selected PDV
value.
To compensate for deviations from the expected packet arrival time, ETX-2i uses
jitter buffers that temporarily store the packets arriving from the PSN (that is,
from the far end equipment) before being transmitted to the local TDM
equipment, to ensure that the TDM traffic is sent to the TDM side at a constant
rate.
For each pseudowire, the jitter buffer must be configured to compensate for the
jitter level expected to be introduced by the PSN; that is, the jitter buffer size
determines the Packet Delay Variation Tolerance (PDVT).
Two conflicting requirements apply:
As packets arriving from the PSN are first stored in the jitter buffer before
being transmitted to the TDM side, TDM traffic suffers an additional delay.
The added delay time is equal to the jitter buffer size configured by the user.
The jitter buffer is filled by the incoming packets and emptied to fill the TDM
stream. If the PSN jitter exceeds the configured jitter buffer size,
underflow/overflow conditions occur, resulting in errors at the TDM side:
A jitter buffer overrun occurs when it receives a burst of packets that
exceeds the configured jitter buffer size + packetization delay. When an
overrun is detected, ETX-2i clears the jitter buffer, causing an underrun.
A jitter buffer underrun occurs when no packets are received for more
than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is
automatically filled with a conditioning pattern up to the PDVT level in order to

compensate for the underrun. Then, ETX-2i starts processing the packets and
emptying the jitter buffer toward the TDM side.
To minimize the possibility of buffer overflow/underflow events, two conditions
must be fulfilled:
The buffer must have sufficient capacity. For this purpose, the buffer size can
be selected by the user in accordance with the expected jitter characteristics,
separately for each pseudowire, in the range of 1 to 180 ms.
TDM clocks at both ends should be synchronized so that the read-out rate
shall be equal to the average rate at which frames are received from the
network. One way to achieve this is by adaptive clock recovery, which
continuously adapts the recovered clock to the packet rate. Other ways may
be by distributing the same clock to ETXs by SyncE, 1588, or External clock
input.
Factory Defaults
No PWs are included in the ETX-2i factory defaults. You must define the
necessary PWs in accordance with your application requirements.
When you create a PW, it is configured by default, as shown below.
ETX2i>config>pwe>pw(1)# inf d
shutdown
name "Put your string here"
description "Put your string here"
no peer
label in 0 out 0
no oam
vlan priority 0
ip-priority-type tos
tos 184
tdm-payload size 0 rate 0
jitter-buffer 2000
psn-oos stop-tx
udp-mux-method dst-port
pm-enable
Configuring Pseudowire Bundles

The configuration of a PW bundle comprises the following steps:
1. Verify that all the necessary ports have been configured as needed and are
administratively enabled.
2. Verify that the peer to be used for the PW has been defined.
3. Verify that Layer-2 and Layer-3 entities have been defined (e.g. flows, router,
etc.).
4. If you are configuring PW encapsulation for PSN UDP over IP (see step 6),
configure the router interface for PWE, making sure to set the router
interface to no management-access (mandatory). You are not required to
configure the router interface for PSN MEF 8 (Ethernet).
Only one router interface can be configured for PWE.

5. Select the PW connection type: CESoPSN for framed E1/T1 packets, SAToP for
unframed E1/T1 packets.
6. Select the PSN type: UDP over IP or Ethernet.
Note All PWs must have the same PSN type.
7. Configure the PW parameters in accordance with the selected connection

type and PSN type.
See Examples below on how to create a CES PW with UDP encapsulation and a
SaTOP PW with Ethernet encapsulation.
Adding Pseudowire Bundles

You can create one pseudowire per MiToP, and link to each one a predefined
peer.
You create a new pseudowire bundle in the level configure pwe. When you define
the PW bundle, you define its number (164), connection type, and PSN type.
You can configure up to eight PW bundles per E1/T1 port, with the exception that
you can create up 16 PW bundles for an E1 port working in CAS mode.
To add a PW:
At the config>pwe# prompt, enter:
pw <pw> [type {ces-psn-data|e1satop|t1satop }] [psn {ethernet | udp-over-ip
}] [manually].
Table 8-16. PW Parameters
type Specifies connection type

ces-psn-data PW bundle using the CESoPSN protocol, for carrying framed data
streams
e1satop PW bundle using the SAToP protocol, for carrying an unframed E1 data
stream
t1satop PW bundle using the SAToP protocol, for carrying an unframed T1 data
stream
psn Specifies packet-switched network type

ethernet MEF 8 packet structure
udp-over-ip UDP over IP with standard packet structure
provisioning Specifies the provisoning mode

manually The pseudowire labels are manually established.
As manually is the only setting for the PW provisioning, it is not necessary to type
the manually parameter.
Note
When the PW encapsulation type is SAToP and the PSN type is Ethernet, alarms
are forwarded toward E1 ports only if the E1 port trail mode is configured to
extended (see Configuring E1 Ports).

Configuring Pseudowire Bundle Parameters

ETX-2i presents configuration parameters relevant only to the PW type and PSN
type. The table of tasks below specifies if a parameter is relevant only for a
certain PW type/PSN type.
To configure a PW bundle:
1. Add a PW bundle as explained in Adding Pseudowire Bundle above.
2. At the config>pwe>pw(<pw-number>)# prompt, enter all necessary
Clearing PW statistics clear statistics The current and running counters are cleared;
the interval counters are not cleared.
Configuring the value of dscp <number> number the value of the IP DSCP field in egress
the IP header DSCP field packets.
Note: Relevant only when IP priority type is
DSCP, and PSN type is UDP over IP.
Providing pseudowire description <pw-descr> For identification of the PW customer
description no description
Defining the egress port egress-port svi Relevant only if the PSN type is ethernet
for PW with Ethernet <port-number> Note: If you need to change the egress SVI port
encapsulation for an active PW configured over a built-in E1/T1
port, you need to do the following:
Administratively disable the PW.
Change the egress SVI.
Delete the relevant cross connect entry.
Administratively re-enable the PW.
Configure the cross connect.
Selecting the IP priority ip-priority-type {tos | dscp} Note: Relevant only when PSN type is UDP over
field used to configure the IP.
IP priority of the IP/UDP If you select IP priority type ToS, configure the
packet: ToS or DSCP tos value (see command in this table).
Otherwise, if you select IP priority type DCSP,
configure the dscp value (see command in this
table).
Defining the jitter buffer Jitter-buffer <jitter-size> Possible values: 1000180000

size in sec. It is recommended to use the shortest feasible
buffer, to minimize connection latency.

Selecting source and label [in <in-pw-label>] in-pw-label the PW label used in the inbound
destination circuit bundle [out <out-pw-label>] direction
identifiers (CBID), also out-pw-label the PW label used in the
referred to as PW labels outbound direction
Possible values for labels: 18191
Each PW bundle must have a unique in (source)
label.
It is not recommended to reuse the same out
(destination) value on PW bundles terminating at
the same peer.
Assigning a name to the name <pw-name> For identification of the PW service

pseudowire no name
Enabling OAM for the PW, oam [rising-threshold The delay threshold is set as follows:
and specifying rate in ms <rising>] [falling-threshold rising-threshold 1180 ms
<falling>]
falling-threshold 1180 ms
no oam
The falling threshold must be less than or equal
to the rising threshold.
Defining the peer for the peer <peer-number> peer-number the number of the remote peer
PW no peer which terminated this PW
The peer type must be according to the PSN
type:
IP address for UDP/IP
MAC address for Ethernet
Specifying if PM collection pm-enable Entering no pm-enable disables PM collection.

is enabled for the PW
Selecting the response to psn-oos {l-bit | stop-tx} Out-of-service conditions are responded to by
out-of-service conditions transmitting PW frames filled with all ones, or by
detected at the local E1/T1 stopping transmission.
physical port

Specifying TDM payload tdm-payload size <size> Note: TDM payload size can be configured for
size in bytes and rate rate <rate> CESoPSN only if the associated E1 port is not in
(number of time slots for CAS mode.
each frame in the packet) if Size according to PW type:
applicable e1satop N32; range 321440
t1satop N24; range 241440
ces-psn-data N number of time slots in a
bundle; range 41440
Rate: 131 for E1; 124 for T1
Note: Rate is relevant only for PW type
ces-psn-data.
It is recommended to specify the parameter
values such that the ratio size/rate is between 2
and 256.
A larger size increases the bandwidth utilization
efficiency, but also increases the connection
intrinsic latency, in particular when the PW
bundle is configured to carry a small number of
timeslots.
Specifying the Layer-3 tos <tos> tos the value of the IP TOS byte in egress
priority assigned to the packets
traffic generated by the PW Possible values: 0255
In accordance with RFC 2474, it is recommended
to use only values that are multiples of 4.
Note: Relevant only when IP priority type is TOS,
and PSN type is UDP over IP.
Specifying the UDP port udp-mux-method dst-port dst-port Standard multiplexing method:
multiplexing method UDP destination port = 0xC000 + <out-PW-label>
UDP source port is 0xC000 + <in-PW-label>
Note: Relevant only for PSN type UDP over IP
Enabling the VLAN tag on vlan priority <vlan-priority> vlan-priority the VLAN priority on every
every transmitting packet no vlan transmitted packet for this PW
for the PW and specifying Possible values: 0-7
the VLAN priority.
Entering no vlan disables the VLAN tag on the
transmitting packets for the PW.

Displaying PW statistics show statistics { current | current displays PW statistic counters for
interval <interval-num> | all- the current interval
intervals | all } interval displays PW statistics for the
selected interval
all-intervals displays PW statistics for all
intervals since the PW statistics collection has
been enabled
all displays PW statistics for current
interval and all intervals
Note: The statistics are visible only when
performance management is enabled for the
corresponding E1/T1 port.
See Viewing PW Statistics.
Displaying PW connectivity show connectivity-statistics Note: The statistics are visible only when
statistics performance management is enabled for the
corresponding E1/T1 port.
See Viewing PW Connectivity Statistics.
Displaying PW status show status
Administratively enabling no shutdown Type shutdown to administratively disable the

the PW bundle PW.
Deleting Pseudowire Bundles
To delete a PW:
1. At the config>pwe>pw(<pw-number>)# prompt, enter:
shutdown
The PW is administratively disabled.
2. At the config>pwe# prompt, enter:
no pw <pw-number>.
The PW is removed.
Viewing Pseudowire Configuration

You can display information about the PW configuration.
To display PW information:
At the prompt config>pwe#, enter show summary.
For example,
ETX-2i>config>pwe# show summary
PW : 1 PW Type : CES PSN Data

PSN Type : UDP Over IP Oper : Not present

Out Label : 0 In Label : 0

Peer : 0 Port : Unknown port 0
Jitter Buffer : 2000 Payload Size : 0

See above table for field descriptions.
Viewing PW Statistics
ETX-2i PWs feature the collection of statistical diagnostics, thereby allowing the
carrier to monitor the transmission performance of the links.
The pseudowire transmission statistics enable analysis of pseudowire traffic
volume, and evaluation of the end-to-end transmission quality (as indicated by
sequence errors) and jitter buffer performance. By resetting the status data at
the desired instant, it is possible to ensure that only current, valid data is taken
into consideration.
To display the PW statistics:

At the prompt config>slot>pwe>pw(<pw_number>)#, enter show statistics
followed by current | interval <interval-num> | all-intervals | all.
For example, show current statistics:
ETX-2i>config>pwe>pw(1)# show statistics current

PW : 1
Port : Unknown port 0
Current
---------------------------------------------------------------
Time Elapsed (Sec) : 0
Valid Intervals : 0
Rx Packets : 354994
Tx Packets : 354995
Missing Packets : 0
Mis-order Dropped Packets : 0
Reordered Packets : 0
Malformed Packets : 0
Jitter Buffer Underrun : 0
The fields are:
Table 8-17. TDM PW Statistic Counters
Rx Packets Number of packets received on the PW from the PSN
Tx Packets Number of packets transmitted on the PW toward the PSN
Missing Packets Number of missing packets as detected via CW sequence number gaps. This
count does not include misordered dropped packets.
Misordered Dropped Number of packets detected via CW sequence number to be out of sequence,
Packets and could not be re-ordered, or could not fit in the jitter buffer. This count
includes duplicated packets.

Reordered Packets Number of packets detected via CW sequence number to be out of sequence,
but successfully reordered
Malformed Packets Number of packets with mismatch between the expected packet and the actual
packet sizes
Jitter Buffer Underrun Number of times jitter buffer was in underrun state
Viewing PW Connectivity Statistics

ETX-2i PWs feature the collection of connectivity statistics for the current,
running, previous, or all intervals. These statistics display the jitter buffer level
(average/current, minimum, and maximum), and round trip delay
(average/current, minimum, and maximum) for a specific interval or for all
intervals.
To display the PW connectivity statistics:

At the prompt config>slot>pwe>pw(<pw_number>)#, enter show
connectivity-statistics followed by current | interval <interval-num> | all-
intervals | running.
For example, show connectivity statistics for interval 1:
ETX-2i# config pwe pw 1 show connectivity-statistics interval 1
Interval Number : 1
Valid Data : Valid
Start Time : 23-06-2015 13:15:10 UTC +00:00
Duration (Sec) : 901
Minimum Average Maximum

Jitter Buffer Level (msec): 1.500 2.097 2.500
Round Trip Delay (msec) : 0.200 0.230 0.261
The fields are:
Table 8-18. TDM PW Connectivity Statistic Counters
Jitter Buffer Level Minimum displays the minimum level of the jitter buffer since the last reset (in
msec)
Average/Current for current and previous intervals, displays the average level
of the jitter buffer; for running interval, displays the current level of the jitter
buffer (in msec)
Maximum Units displays the maximum level of the jitter buffer since the last
reset (in msec)
Round Trip delay Minimum displays the minimum round trip delay since the last reset (in msec)
Average/Current for current and previous intervals, displays the average round
trip delay; for running interval, displays the current round trip delay (in msec)

Maximum Units displays the maximum round trip delay since the last reset (in
msec)
Examples
To create and activate a CES PW with UDP encapsulation:
Note The E1 port must be configured for framed traffic.
exit all
config flow
classifier-profile mng_untagged match-any
match untagged
exit
flow 1
classifier "mng_untagged"
no shutdown
exit
flow 2
classifier mng_untagged
ingress-port svi 1
no shutdown
exit all
config router 1 interface 1

address 10.10.10.10/24
bind svi 1
no management-access
no shutdown
exit all
config peer 1 ip 10.10.10.11
configure pw
pw 1 type ces-psn-data psn udp-over-ip
peer 1
label in 100 out 100
tdm-payload size 40 rate 10
no shutdown
exit all
configure cross-connect
pw-tdm pw 1 e1 1 time-slots 1..10
exit all
To create and activate a SaTOP PW with Ethernet encapsulation:
Note The E1 port must be configured for unframed traffic.
config flow
classifier-profile mng_untagged match-any

match untagged
exit
flow 1
no shutdown
exit
flow 2
ingress-port svi 1
no shutdown
exit all
config peer 1 mac 00-00-00-00-00-01

configure pw
pw 1 type e1satop psn ethernet
egress-port svi 1
peer 1
label in 100 out 100
tdm-payload size 34
no shutdown
exit all
configure cross-connect
pw-tdm pw 1 e1 1
To create and activate a CESoPSN with CAS PW with UDP encapsulation:
Note The E1 port must be configured for framed traffic with signaling.
configure
peer 1 ip 10.10.20.100
port
svi 1
no shutdown
exit
e1 1
tx-clock-source pw 1
line-type g732s
pm-enable
no shutdown
exit
exit
flows
classifier-profile "all" match-any
match all
exit
classifier-profile "unt" match-any
match untagged
exit
flow "in"
classifier "unt"
no policer

no shutdown
exit
flow "out"
classifier "all"
no policer
ingress-port svi 1
no shutdown
exit
exit
router 1
interface 1
address 10.10.20.200/24
bind svi 1
dhcp-client
client-id mac
exit
no shutdown
exit
exit
pwe
pw 1 type ces-psn-cas psn udp-over-ip
peer 1
label in 20 out 20
no vlan
jitter-buffer 10000
psn-oos 1-bit
pm-enable
cas-frames-per-packet 16
no shutdown
exit
exit
cross-connect
exit
exit
8.10 PW Cross Connects
Applicable Products
This feature is applicable to devices that support smart SFP MiTOP functionality.
PW cross-connects are used to connect E1/T1 ports to pseudowire bundles.
8-130 PW Cross Connects ETX-2i

Factory Defaults
No PW cross-connects are included in the ETX-2i factory defaults.
Configuring PW Cross Connects

To configure PW cross-connects for E1/T1 ports:
At the config>cross-connect# prompt, enter the pw-tdm command as
follows:
pw-tdm pw <pw> {e1|t1} <port> [time-slots <list>]
where:
<pw> specifies number of pseudowire bundle that must already exist
and be active
<port> specifies E1/T1 port number
<list> list of timeslots to assign to the PW bundle. Note that time-slots
<list> option can be used only if the PW type is CESoPSN. The list can be
a single value or range (in the form <ts1..ts2>). The specified timeslots
must be compatible with the payload size and rate specified for the PW
via the tdm-payload command.
The E1/T1 port line-type must be compatible with the PW type, as follows:
If the PW type is ces-psn-data, the E1/T1 port line-type must be g723n or
g723n-crc for E1; esf for T1.
If the PW type is e1satop or t1satop, the E1/T1 port line-type must be
unframed.
Examples
In these examples, PW 1 must be active; see Examples in Pseudowire Connections
for instructions on configuring and enabling PWs.
To assign E1 port timeslots 131:
exit all
config cross-connect
exit all
To remove the E1 port timeslot assignment for PW 1:

exit all
config cross-connect
no pw-tdm pw 1 e1
exit all
ETX-2i PW Cross Connects 8-131

8.11 Router
The router provides an IP forwarding plane for IPv4 and IPv6 packets, and also
interconnects internal Layer-3 support modules, such as management and
1588v2 (recovered clock). Any flow related to IP forwarding, management traffic,
or timing must be via an SVI or PPP that is bound to a router interface. The ETX-2i
dynamic router option provides up to 8 Gbps Layer-3 forwarding, with multiple
Virtual Routing and Forwarding instances (VRFs).
Standards
RFC 1812 Requirements for IP Version 4 Routers
RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
RFC 2464 Transmission of IPv6 Packets over Ethernet Networks
RFC 4291 IP Version 6 Addressing Architecture
RFC 4294 IPv6 Node Requirements
RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol
Version 6 (IPv6) Specification
RFC 4862 IPv6 Stateless Address Autoconfiguration
RFC 5880 Bidirectional Forwarding Detection general protocol
RFC 5881 Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single
Hop) protocol
RFC 5882 Generic Application of Bidirectional Forwarding Detection (BFD)
RFC 2663 IP Network Translator (NAT) Terminology and considerations
RFC 2766 Traditional IP Address Translator
RFC 3489 Simple Traversal of User Datagram Protocol through Network Address
Translator (STUN)
RFC 7857 Traditional IP Address Translator
Benefits
The router provides IP Routing and Forwarding for IPv4 and IPv6 packets.
Notes A router supports up to 31 router interfaces; however, only one router

interface is supported when working with PWs, and only two router interfaces
can be configured for management access.
In order to enable management, you must configure a router interface
enabled for management access, assign it an IP address, and bind it to an SVI
for which management flows have been defined.
8-132 Router ETX-2i

Overview
Any flow into/out of the device, which is related to management/timing, must be
via an SVI that is bound to a router interface. A router interface can be
associated via binding to only one SVI. If a flow is used for management
purposes, the router interface corresponding to the SVI should be enabled for
management access.
Figure 8-26. Router and SVIs
The router maintains a table of IPv6 neighbors, via discovery of neighboring IPv6
nodes. It is recommended to manage ETX-2i via a router interface defined as a
loopback interface, as this router interface remains active. To ensure that packets
generated by the router are transmitted with the loopback IP address, you need
to define the management source IP address for IPv4 and IPv6 (see Configuring
the Management Source IP Address).
The MAC addresses used by router interfaces are as follows:
Router interface that resides directly on a port uses that ports MAC address
Router interface that resides on a bridge port uses the Ethernet management
port MAC address
Router interface connected to an ETP subscriber port uses the Ethernet
management port MAC address.
The management and control packets transmitted by the router have a
configurable IP DSCP value, so that each router entity can control its traffic
priority by setting its DSCP value for its protocols (see Configuring the Router on
how to configure the DSCP).
Embedded Router
The following ETX-2i features are not supported with the embedded router
option:
Timing ports (do not appear on the front panel)
Bridge functionality
Smart SFP MiTOP functionality
ETX-2i Router 8-133

Protocols
The embedded router uses the BFD protocol to trigger reroute for static routes
when faults are detected in the route to BFD neighbors with local addresses
(single hop). The router maintains a table of BFD neighbors for this purpose. ACLs
can be bound to ingress router interfaces of the embedded router; they cannot
be bound to router interfaces of the regular router.
In addition, the embedded router supports the following:
Border Gateway Protocol (BGP) See the Routing Protocol BGP section.
Open Shortest Path First (OSPF) See the Routing Protocol OSPF section.
Virtual Router Redundancy Protocol (VRRP) See the Virtual Router
Redundancy Protocol - VRRP section.
Routing Preferences
When there are conflicts between routes received from different sources, such as
static routes, OSPF routes, and BGP routes, the routers Routing Table Manager
(RTM) chooses among the sources according to configurable source preference
indices.
Capacity
The following table shows the limits applicable to the router.
Table 8-19. Embedded Router Capacity
Parameter Capacity
VRFs 10 for ETX2i; 5 for ETX-2i-B
Router Interfaces 31 for ETX2i; 15 for ETX-2i-B
Routing table per VRF Two (one for IPv4, one for IPv6)
Total IPv4 routing table entries 4K for ETX2i; 2K for ETX-2i-B
Total IPv6 routing table entries 3.5K for ETX2i; 2K for ETX-2i-B
ARP table per VRF Two (one for IPv4, one for IPv6)
Total IPv4 ARP table entries 128
Total IPv6 ARP table entries 128
Maximum IPv4 addresses per device 64
Maximum IPv6 addresses per device 128
Maximum IPv4 addresses per router interface 10
Maximum IPv6 addresses per router interface 10
Maximum ACLs per device 64
Maximum ACLs per router interface Two (one for IPv4 inbound, one for
IPv6 inbound)
Maximum ACL rules per device 128 for ETX2i; 64 for ETX-2i-B
8-134 Router ETX-2i

Parameter Capacity
Maximum IPv4 BFD sessions 20
Maximum IPv6 BFD sessions 20
Router Interface Forwarding

The following tables specify the classification, editing, and queue/CoS mapping
for flows to and from a router interface.
Table 8-20. Flows to Router Interface
Classification VLAN editing CoS mapping Comments
Untagged None None Mapped to CoS = 0
VLAN Pop DSCP mapping profile

(DSCP to CoS) or none
Outer VLAN, inner VLAN Pop,pop DSCP mapping profile

(DSCP to CoS) or none
Outer VLAN, Pop,pop DSCP mapping profile

inner VLAN + DSCP (DSCP to CoS) or none
Outer VLAN, Pop,pop None

inner VLAN + non IP
Table 8-21. Flows from Router Interface
Classification VLAN editing CoS mapping Comments
Untagged None, push single VLAN, push VLAN DSCP to queue or fixed DSCP to p-bit or fixed
and inner VLAN
DSCP None, push single VLAN, push VLAN DSCP to queue or fixed DSCP to p-bit or fixed
and inner VLAN
DHCPv6 Option Request

In the ETX-2i-B 10 ports device, you can configure the DHCP client to request the
DHCPv6 server for vendor-specific option 17 (using the dhcpv6-option-request
command). The DHCPv6 server offers this option only if you configure the
devices DHCP client to request it.
Vendor-specific option (17) is used to pass data needed to run the Zero Touch
process (refer to Chapter 3 for a description). This data includes TFTP server IP
and the name of the file to download (optional).
DHCP Relay
DCHP relay uses a DHCP relay agent (either an Internet host or router) to pass
DHCP messages between DHCP clients and DHCP servers. One DHCP relay agent is
ETX-2i Router 8-135

supported per device, and one DHCP server is supported to serve the DHCP relay
agent.
Figure 8-27. DHCP Relay Application
Note DHCP is designed to use the relay agent behavior specified in the BOOTP protocol
specification.
The DHCP Relay application requirements include:

The device supports operation of one DHCP relay agent, which in turn, is
associated with one router entity.
The DHCP relay agent supports IPv4 only.
The DHCP Relay Agent supports the definition of one DHCP server with which
it can communicate.
The DHCP relay agent, when enabled on the router entity, is able to provide
DHCP Relay functionality for all router interfaces at this router entity.
The DHCP relay agent enables you to create a DHCP relay server and set its IP
address on router level (see dhcp-relay-server table entry in Configuring the
Router). The DHCP relay agent also provides configuration to enable/disable DHCP
relay per router interface on the router entity where the DHCP relay server was
defined (see dhcp-relay-server table entry in Configuring Router Interfaces).
Network Address Translator (NAT)

Network Address Translation is a method that maps IP addresses (IPv4 only) from
one IP domain to another in an attempt to provide transparent routing to hosts.
Traditionally, NAT devices connect networks and hosts having private
unregistered addresses to a global public network with globally unique registered
addresses.
8-136 Router ETX-2i

IP Address translation is required for the following reasons:

The network's internal IP addresses cannot be used outside the network,
either because they are invalid for use outside, or because the internal
addressing must be kept private from the external network.
Lack of public IP addresses and the need to represent as many hosts as
possible (using private IP addresses) via a single public address. NAT uses the
IP address resource in an efficient way.
NAT Terminology
The following NAT terminology is used:
Inside network the private network side of the NAT function
Outside network the public network side of the NAT function
Inside local address the IP address assigned to a host on the inside
network. This is the address configured as a parameter of the computer OS
or received via dynamic address allocation protocols, such as DHCP. The
address is not likely a legitimate IP address assigned by the Network
Information Center (NIC) or service provider.
Inside global address a legitimate IP address assigned by the NIC or service
provider; represents one or more inside local IP addresses to the outside
world.
Outside local address the IP address of an outside host as it appears to the
inside network. Not necessarily a legitimate address, it is allocated from an
address space routable on the inside.
Outside global address the IP address assigned to a host on the outside
network by the host owner. The address is allocated from a globally routable
address or network space.
NAT Functionality: Address Translation

NAT translates in the following ways:
NAT translations:
Inside to Outside: Inside (private) IP SA (Inside local) Outside (public) IP
SA (Inside global)
Outside to Inside: Outside (public) IP DA (Inside global) Inside (private)
IP DA (Inside local)
NAPT translations TCP and UDP sessions are translated with port number, in
addition to the IP address:
Inside to Outside: Inside (private) IP SA:Port (inside local) Outside
(public) IP SA:Port (Inside global)
Outside to Inside: Outside (public) IP DA:Port (Inside global) Inside
(private) IP DA:Port (Inside local)
Traffic that does not match NAT entries, is forwarded per router regular path.
ETX-2i Router 8-137

Outside Network Inside Network
DA SA DA SA
Outside Global Inside Global Outside Local Inside Local
Outside Inside
NAT Host
Host
SA DA SA DA
Outside Global Inside Global Outside Local Inside Local
Translate
NAT Address Translation
Supported NAT Types

ETX-2i supports the following NAT types:
Static (One to One) NAT with the following properties:
One to One Translates a single private IPSA to a single public IPSA; does
not translate port
Bidirectional Sessions can be initiated both from the Inside and
Outside.
NAPT/PAT: In this mode, many hosts on the private (Inside) network are
represented by a single public (Outside) IP, using the TCP or UDP port number
to differentiate between the different sessions.
In this mode, many different IPs (IP:Port) are translated into a single IP:Port,
while the translated port is used to differentiate between the sessions ( as
translated IP uses the same IP).
Many to One Translate IP and Port for TCP/UDP sessions.
Unidirectional Sessions can be initiated only from the Inside
TCP/UDP Port mapping functionality valid for TCP/UDP sessions only.
Outside destination to Inside hole punching (Static Port configuration):
One to One Translates IP DA:Port from the Outside to the Inside
Unidirectional Sessions can be initiated only from the Outside.
NAT supports symmetric operation, meaning that NAT sessions are identified by
both IPSA (:Port) and IP DA (:Port).
ALG
Some applications use IP addresses and port numbers inside their data payloads.
To extend the capabilities of NAT and enable it to operate with such applications,
ALGs can modify such information within data payloads. As different applications
employ different protocols or data formats, ALGs must be customized for each
application.
ETX-2i NAT supports the following ALGs:
8-138 Router ETX-2i

ICMP
FTP for both active and passive FTP
SIP
ALG is always on and requires no configuration.
Mapping Table Entries Timeout

In general, mapping table (NAT translation table) entries are deleted upon
expiration of a timeout (configurable; default is 60 seconds). The expiration time
of an entry is refreshed each time a translation (hit) occurs.
NAT TCP entries are removed from the mapping table in the following cases:
After TCP FIN is detected from both peers and Other Timer expires.
If TCP FIN is not detected, TCP entries are removed after TCP timer expires.
Configurable TCP Timer - Timer per entry is supported and refreshed by entry
hit (occurrence of translation).
NAT UDP entries are removed by an aging mechanism (refreshed by traffic hit):
Configurable UDP timer
Timer per entry is supported and refreshed by entry hit (occurrence of
translation).
NAT entries, which are not TCP (excluding the TCP FIN case) or UDP, aree
removed by an aging mechanism (refreshed by traffic hit):
Configurable Other timer
Timer per entry is supported and refreshed by entry hit (occurrence of
translation)
An alarm is issued when the mapping table reaches its full capacity (1000
entries). The alarm clears when the mapping table goes below 95% full capacity.
NAT Instances
ETX2i supports a single instance of NAT, which may be configured over each one
of the ETX2i VRFs.
Scale
20000 entries in the mapping table
Up to 32 NAT rules of static NAT, NAPT and Outside to Inside (Static IP:Port)
Factory Defaults
By default, no router interfaces exist. The other router parameters are configured
as shown in the following table.
By default, the source management IP address for IPv4/IPv6 is not configured.
name "Router#1
ETX-2i Router 8-139

dhcp-client host-name sys-name In the DHCP client, the device name is used
as the host name.
dhcp-client vendor-class-id ent-physical-name In the DHCP client, the entity physical name
is used as the vendor class ID.
Configuring the Router

The router functionality allows ETX-2i to establish links to Ethernet ports via SVIs,
or to peers that provide the 1588v2 master clock, or to establish PPPoE sessions
via PPP ports.
To configure the router:

1. At the config# prompt, enter:
router <number>
The config>router(<number>)# prompt is displayed.
Starting session with BFD bfd-neighbor <ip-address> {associated |

neighbor non-associated}
Deleting dynamic ARP entities clear-arp-table [<address>] Specify the IP address to clear only
the entries corresponding to it.
Clearing BFD statistics clear-bfd-statistics <ip-address>
Clearing IPv6 neighbor table clear-neighbor-table
Clearing router statistics clear-statistics all Router statistics include:

clear-statistics ipv4 {access-list | traffic} IPv4 and IPv6 router system
clear-statistics ipv6 {access-list | traffic} statistics
IPv4 and IPv6 router interface
statistics
Statistics of all (either IPv4 or
IPv6) access lists bound to the
router
Creating a router interface interface <interface-num> [{loopback } ] interface-num a unique number

assigned to the router interface
loopback configures interface as a
loopback interface
Type no interface <interface-num>
to delete a router interface.
See the Configuring Router
Interfaces section for a list of tasks
that can be configured on a router
interface.
8-140 Router ETX-2i

Assigning name to router name <string> Alphanumeric string
Enabling, or disabling and nat Typing no nat disables and deletes

deleting Network Address no nat the existing NAT configuration,
Translator (NAT) including. all mapping table entries.
Note: You can configure a single
instance of NAT over each one of the
supported VRFs.
See Configuring Network Address
Translator (NAT).
Setting the priority of static static-preference {ipv4 | ipv6} <priority> Possible values for number: 0255
routes for IPv4 and IPv6 RTM Default: 1
Enabling the static route and static-route The next hop must be a subnet of
the next gateway (next hop) <ip-address/ip-mask-of-static-route> address one of the router interfaces.
using the next hops IP address <ip-address-of-next-hop> [metric <metric>][ To set the default-gateway,
install | no-install ] configure the static route of address
no static-route <ip-address/prefix-length> 0.0.0.0/0 to next hop default
address address gateway address.
no static-route deletes static route
entry.
metric specifies the priority of the
static route
Default: 1
install option forwards a specific
route entry into the FIB.
no-install option does not forward a
specific route entry into the FIB.
Enabling the static route and static-route no static-route deletes static route
the router interface number <ip-address/ip-mask-of-static-route> entry.
toward which the destination interface <router-interface-num> [metric metric specifies the priority of the
subnet is to be routed <metric>][ install | no-install ] static route: 1255 (default: 1).
no static-route <ip-address/prefix-length> install option forwards a specific
interface <router-interface-num> route entry into the FIB.
no-install option does not forward a
specific route entry into the FIB.
Displaying the summary of show access-list summary Refer to the Access Control List
ACLs bound to router interface (ACL) section for further information.
Displaying the address show arp-table [ address <ip-address> ]

resolution protocol (ARP) table,
which lists the original MAC
addresses and the associated
(resolved) IP addresses
Displaying BFD neighbor table show bfd-neighbors

show bfd-neighbors-details
ETX-2i Router 8-141

Displaying the interface table show summary-interface See Viewing Router Interface
Information.
Displaying IPv6 neighbors table show neighbor-table [address <ip-address>] See Viewing IPv6 Neighbors.
Displaying the routing table show routing-table [ address ip-address/ip-mask View routing
<ip-address/ip-mask> ] information for a specific IP address
[ protocol { dynamic | static } ] of a specified prefix length.
protocol { dynamic | static } View
information on only dynamic or
static routes.
See Viewing Routing Information.
Displaying the IPv4 or IPv6 RIB show rib { ipv4 | ipv6 } See Viewing RIB.
(Routing Information Base)
table
Displaying router statistics show statistics ipv4 access-list {in | out}

show statistics ipv4 traffic
show statistics ipv6 access-list {in | out}
Configuring DHCP client for the dhcp-client

router interface
Commands in level dhcp-client
Configuring DHCP client to dhcpv6-option-request [vendor-specific- Vendor specific option 17 is used

request DHCPv6 server for information-17] to pass data needed for the Zero
option 17 no dhcpv6-option-request Touch process.
Notes:
The command behaves the
same regardless of whether you
specify vendor-specific-
information-17 optional
keyword.
Entering no dhcpv6-option-
request results in DHCP client
not explicitly requesting option
17.
Providing host name to DHCP host-name name <string> You can specify a name, or specify
server host-name sys-name sys-name to indicate that the
system name should be used as
no host-name
the host name.
Providing vendor ID to DHCP vendor-class-id name <string> You can specify an ID, or specify
server vendor-class-id ent-physical-name ent-physical-name to indicate that
the device name should be used as
the vendor ID.
8-142 Router ETX-2i

Configuring DHCP relay servers dhcp-relay-server <ip-address> You can add only one DHCP relay
no dhcp-relay-server <ip-address> server per device.
ip-address legal IPv4 server
address
no dhcp-relay-server <ip-address>
deletes the DHCP relay server.
You can delete the relay server
only when all router interfaces
associated with the router are
configured to DHCP Relay disable.
Configuring DSCP value for dscp <number> Possible values: 063

router entity traffic Default: 0
Configuring Router Interfaces

You can configure up to 31 router interfaces for ETX2i; 15 for ETX-2i-B.
However, only one routing interface is supported when working with PWs, and
only two routing interfaces can be configured for management.
To configure router interfaces:

1. At the config>router(<number>)# prompt, enter:
interface <interface-num> [loopback]
The config>router(<number>)>interface(<interface-num>)# prompt is
displayed.
Binding ACL to router interface access-group Refer to the Access Control List
(ACL) section for further
information.
Assigning an IP address and address The IP address can be IPv4 (e.g.

prefix length to the router <ip-address/prefix-length> 10.10.10.1) or IPv6 format (e.g.
interface no address 10:10:10:10:10:10:10:10)
<ip-address/prefix-length> Prefix length: IPv4 132;
IPv6 1128
You cannot define an IP address
if the router interface is bound
to a PPP port.
ETX-2i Router 8-143

Specifying parameters for BFD bfd min-tx {100ms | 1s | 10s} min-tx minimum time interval
sessions min-rx {100ms | 1s | 10s} for periodic transmission of BFD
multiplier <multiplier-val> control packets
min-rx minimum interval for
periodic reception of BFD
control packets
multiplier detection time
multiplier: BFD session
detection time is calculated by
multiplying the negotiated
transmit interval by this value.
Binding router interface to SVI bind svi <port-number> You can bind one SVI to a
logical port router interface.
Enter no bind to unbind the
router interface.
Note: This command is available
only if the interface is not
loopback.
Binding router interface to PPP bind ppp <port-number> Only one router interface can
port for PPPoE be bound to a PPP port.
Enter no bind to unbind the
router interface.
Clearing router interface clear-statistics all

statistics clear-statistics ipv4 access-list
{in | out}
clear-statistics ipv4 traffic
clear-statistics ipv6 access-list
{in | out}
clear-statistics ipv6 traffic
Enabling/disabling DHCP client dhcp You cannot enable DHCP (for IPv4)
no dhcp in the following cases:
Router interface is bound to a
PPP port.
IPv4 address is configured.
Router interface is not
unnumbered.
DHCPv6 is enabled.
DHCP relay is enabled.
Configuring DHCP client for the dhcp-client

router interface
Commands in level dhcp-client
8-144 Router ETX-2i

Providing client ID to DHCP server client-id id <string> You can specify an ID, or specify
client-id mac mac to indicate that the device
MAC address should be used as the
client ID.
Enabling or disabling DHCP relay dhcp-relay You can enable DHCP relay if DHCP
for the router interface no dhcp-relay client is disabled and a DHCP relay
server is defined in the Router
level.
Enabling or disabling DHCPv6 dhcpv6-client You can enable DHCPv6 client

client for the router interface no dhcpv6-client provided that the following
conditions exist:
Router entity is Router # 1.
There is no other DHCPv6 client
defined in the device.
DHCPv4 is not enabled.
The router interface is not
defined as loopback.
The router interface is not
bound to a PPP port.
VRRP is not configured on the
router interface.
Enabling or disabling IPv6 ipv6-autoconfig Enter no ipv6-autoconfig to disable

autoconfiguration on router no ipv6-autoconfig IPv6 autoconfiguration.
interface
Configuring interface management-access {allow-all | You can set management

management access allow-ping} access to allow-all for up to two
router interfaces.
Enter no management-access
to remove management access
from router interface.
Configuring maximum allowed mtu <bytes> Possible values: 128012,288

length of transmitted unit (in Default: 1500
bytes) Note: This command is available
loopback.
Assigning a name to the router name <interface-name>

interface no name
Displaying the summary of ACLs show access-list summary Refer to the Access Control List
bound to router interface (ACL) section for further
information.
ETX-2i Router 8-145

Displaying router interface show statistics ipv4 access-list

statistic show statistics ipv4 traffic
show statistics ipv6 access-list
Displaying router interface status show status See Viewing Router Interface
Status.
Enabling or disabling sending of unreachables

ICMP unreachable messages, to no unreachables
notify that the destination
unicast address is unreachable
Removing VLAN assignment no vlan VLAN can be removed, only when

router interface is in non-active
state.
Note: This command is available
loopback.
Administratively enabling or no shutdown You can administratively enable the

disabling the router interface shutdown router interface only if one of the
following is true:
The router interface is bound to
an administratively enabled SVI,
and the following are true:
An IP address was assigned
via the address command.
Flows have been defined to
and from the SVI, and are
administratively enabled.
The router interface is bound to
a PPP port that is bound to an
administratively enabled SVI,
and the following are true:
No IP address has been
assigned via the address
command.
DHCP has not been enabled.
Using shutdown disables the
interface.
Configuring Network Address Translator (NAT)

You can configure a single instance of NAT over one of the device VRFs.
To configure NAT:
1. At the config>router(<number>)# prompt, enter:
nat
8-146 Router ETX-2i

The config>router(<number>)>nat# prompt is displayed.

Configuring, modifying, or nat-inside-source-static <inside- inside-ip IPv4 address of Inside IP

deleting a NAT rule from the ip> { ip <outside-ip> | interface station
inside to outside <rif-id> } ip Ipv4 address for translation
no nat-inside-source-static interface number of outside
<inside-ip> facing router interace whose IP
address is used for IP translation.
Notes:
The static NAT configuration must
be unique, i.e. no other static NAT
entry can use the same inside local
IP (source IP) or inside global IP
(translated IP).
A NAT rule that is missing info
(yet to be configured) is saved
and applied once you configure
the missing info. There is no
sanity reject.
Configuring, modifying, or nat-inside-source-static-port source source address

deleting a NAPT rule from the {tcp | udp} <inside-ip> <port> { translation
inside to outside ip <outside-ip> <port>|interface <inside ip/prefix> - IP subnet of
<rif-id> <port>} inside Inside network
no nat-inside-source-static-port ip IPv4 address for translation
tcp <inside-ip> <port>
interface number of outside
no nat-inside-source-static-port facing router interface whose IP
udp <inside-ip> <port> address is used for IP translation
tcp - range of IP ports to be used
for TCP port translations
udp - range of IP ports to be used
for UDP port translations
Possible values:
start-port : 1024 (default) 65535
size : 1 64511 (default)
Configuring, modifying, or nat-inside-overload source

deleting a NAPT rule from the <inside ip/prefix> { ip <outside-
inside to outside ip> | interface <RI number> } [
tcp < start-port> <size> ] [udp <
start-port> <size> ]
no nat-inside-overload source
<inside ip/prefix> <outside-ip>
no nat-inside-overload source
<inside ip/prefix> interface <RI
number>
ETX-2i Router 8-147

Configuring or modifying NAT nat-timeout [ tcp < tcp- tcp - expiration timeout of TCP
translation table entry timeout timeout>] [ udp <udp-timeout> ] entries in NAT translation table
[ other <other-timeout> ] udp - expiration timeout of UDP
entries in NAT translation table
other - expiration timeout of other
protocol entries in NAT translation
table
Default: 60
Displaying NAT translation table show nat-translations See Viewing NAT Translation Table
Clearing NAT translation table clear nat-translations
Displaying NAT statistics counters show nat-statistics See Viewing NAT Statistics,
Clearing NAT statistics counters clear nat-statistics
Configuring the Management Source IP Address

The management source IP address provides a single point of contact for
management applications that interface with ETX-2i.
When a router interface responds to management packets, the responding
packet source IP address is set to the router interface IP address. If the router
interface sends a management packet that is not a response, the packet source
IP address is set to the ETX-2i management source IP address. If the management
source IP address is not configured or the corresponding router interface is
down, the packet source IP address set to the router interface IP address. You
can configure a single management source address for IPv4 and IPv6 to be used
in all client management applications, including: SNMPv3 (for trap), Radius,
Tacacs+. Syslog, SNTP, TFTP, and SFTP.
To configure the management source IP address:

1. Navigate to configure management.
The config> mngmnt# prompt is displayed.
2. Type:
management-address <ip-address>
Note According to the format of the IP address (IPv4 or IPv6), it is saved as the IPv4 or
IPv6 management source IP address.
The management source IP address is set to the specified IP address.

3. To delete the IPv4 or IPv6 management address, type:
no management-address {ipv4 | ipv6}
Deleting a Router
You can delete a router if there are no router interfaces or OSPF entities
associated with it.
8-148 Router ETX-2i

To delete a router:
At the config# prompt, enter:
no router <number>
Deleting a Router Interface

You can delete a router interface if there is no OSPF interface associated with it.
To delete a router interface:

At the config>router(<number>)# prompt, enter:
no interface <interface-num>
Viewing Router Interface Information

You can view information on each router interface by using the show summary-
interface command:
config>router(<number>)>show summary-interface
To display the interface summary:

ETX-2i>config>router(1)# show summary-interface
Router Interface: 1
Name: RI001
Admin:Up Oper: Up Bound to: svi 1
3.3.3.2/24 (manual) (preferred)
Router Interface: 3
Name: RI003
Admin:Up Oper: Up Bound to: svi 31
4.4.4.3/24 (manual) (preferred)

The above fields are:
Table 8-22. Router Interface Parameters
Field Description
number Unique number assigned to the router interface
Name Name of the router interface (alphanumeric string)
Admin Administrative status:

up ready to pass packets
down
Oper Operational status:

down
LLD Lower Layer Down; down due to state of lower-layer
interface(s)
Bound to The port that the router interface is bound to
ETX-2i Router 8-149

Field Description
IP Addresses
IP Address/prefix IPv4 or IPv6 address and prefix length

length Note: Supported for DHCPv6
origin Origin of the IP address.

Possible origins are:
other for example, link local address
manual indicates that the address was manually configured to a
specified address
dhcp indicates an address that was assigned to this system by a
DHCP server
link layer indicates an address created by IPv6 stateless auto-
configuration
random indicates an address chosen by the system at random
status Status of the IP address.

Available statuses (from the IPv6 Stateless Address Autoconfiguration
protocol) are:
preferred (default)
deprecated
invalid
inaccessible
unknown
tentative
duplicate
optimistic
Viewing IPv6 Neighbors

You can view information on each each IPv6 neighbor by using the show
neighbor-table command:
config>router(<number>)>show neighbor-table
To display the neighbor table:

ETX-2i>config>router(1)# show neighbor-table
IPv6 Address MAC address State Interface
=============================================================================
1234:1234:1234:1234:1234:1234:1234:1234 01-01-01-01-01-01 reachable 1
1234:1234:1234:1234:1234:1234:1234:1234 01-01-01-01-01-01 incomplete 28
FE80::200:E8FF:FE00:2A2B 00-00-e8-00-2a-2b stale 2
8-150 Router ETX-2i

Table 8-23. IPv6 Neighbor Parameters
Field Description
IPv6 address
MAC address
State The Neighbor Unreachability Detection state for the interface when
the address mapping in this entry is used:
reachable confirmed reachability
stale unconfirmed reachability
delay waiting for reachability confirmation before entering
probe state
probe actively probing
invalid invalidated mapping
unknown state cannot be determined for some reason
incomplete address resolution is being performed
interface Router interface number
Viewing Routing Information

You can view all routing information or only information on dynamic or static
routes, for all IP addresses or for a specific IP address and prefix length of a
dynamic or static by using the show routing-table command:
config>router(<number>)>show routing-table [ address <IP-address/IP-mask> ]
[ protocol { dynamic | static } ]
To display the routing table:

ETX-2i>config>router(1)# show routing-table
IP address/prefix Next Hop interface Protocol Metric
====================================================================
172.17.175.0/24 172.177.170.100 1 Static 250
172.17.176.0/24 0.0.0.0 3 Local 0
1.1.1.1/32 0.0.0.0 4 Local 0
Table 8-24. Routing Parameters
Field Description
IP address/prefix IPv4 or IPv6 address and prefix length
Next Hop Route entry next hop IP address
Interface Router interface number
ETX-2i Router 8-151

Field Description
Protocol Source protocol:

other
local
mngmnt
icmp
egp
ggp
hello
rip
isis
esis
ciscoigrp
bbnspflgp
ospf
bgp
idpr
cisco-eigrp
dvmrp
Metric Route entry metric

When protocol is BGP, this is blank.
Viewing RIB
You can view the RIB (Routing Information Base) by using the command show rib.
This command is available in the CLI contexts for IPv4 or IPv6, at the router level:
config>router(<number>)#.
To display the IPv4 RIB:

ETX-2i>config>router(1)# show rib ipv4
* = Active Route
Network > Next Hop RI Proto Metric
=============================================================================
* 0.0.0.0/0 > 172.17.171.1 2 Static 1
* 2.2.2.0/24 > 172.17.171.205 2 BGP
* 3.3.3.0/24 > 0.0.0.0 1 Local 0
3.3.3.0/24 > 172.17.171.205 2 BGP
* 111.222.111.0/24 > 0.0.0.0 2 Local 0
111.222.111.0/24 > 172.17.171.205 2 BGP
To display the IPv6 RIB:

ETX-2i>config>router(1)# show rib ipv6
* = Active Route
Network > Next Hop RI Proto Metric
=============================================================================
* ::/0 > 11:11:11:11::1 1 Static 1
8-152 Router ETX-2i

* 11:11:11:11::/64 > :: 1 Local 0

* abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd/126
> abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 1 Static 1
* fe80::/64 > :: 1 Local 0
Table 8-25. RIB Field Descriptions
Field Description
Status Marks with a * an Active Route, i.e. route entry is forwarded to the
(Active FIB (Forwarding Information Base)
Route)
Network IPv4 or IPv6 network address (prefix and prefix length)

IPv4 prefix length can be 032; IPv6 prefix length can be 0128.
Next hop Route entry next hop IP address
RI Local interface through which the next hop of this route should be
reached
Protocol Source protocol
Metric Route entry metric
Viewing Router Interface Status

You can view the router interface status by using the show status command:
config>router(<number>)>interface(<interface-num>)>show status
To display the router interface status:

ETX-2i>config>router(1>interface# show status
Admin: up Oper: down
IP Addresses:
101.101.101.1/24 (DHCP) (preferred)
1234:1234:1234:1234:1234:1234:1234:1234/126 (manual) (preferred)
1234:1234:1234:1234:1234:1234:1234:1234/126 (link layer) (preferred)
IPv4 Default Router: 1.1.1.254
DHCP Client Information /*section appears if DHCP is enabled*/

Status: Holding Lease
Server: 10.110.110.110
Lease Obtained: 01-01-2010 00:00:01
Lease Expires: 10-01-2010 00:00:01
Lease Renewal: 05-01-2010 00:00:01
Lease Rebinding: 07-01-2010 00:00:01
Router: 101.201.1.111, 101.201.1.222
Static Routes: IP: 2.2.2.2 NH: 1.1.1.7
IP: 10.10.10.10 NH 1.1.1.8
TFTP Server: 2.2.2.2
Bootfile Name: path/filename
Host Name: Mao-Ze-Dong
ETX-2i Router 8-153

DHCPv6 Client Information /*section appears if DHCPv6 is enabled*/

Server: 1234:1234:1234:1234:1234:1234:1234:1234
TFTP Server: 1234:1234:1234:1234:1234:1234:1234:1234
Filename: path/filename
Table 8-26. Router Interface Status Parameters
Field Description
Admin Administrative status:

down
Oper Operational status:

down
IP Addresses
IP Address/prefix IPv4 or IPv6 address and prefix length

length Note: Supported for DHCPv6
origin Origin of the IP address.

Possible origins are:
other
manual
DHCP
link layer
random
status Status of the IP address.

Available statuses (from the IPv6 Stateless Address Autoconfiguration
protocol) are:
preferred (default)
deprecated
invalid
inaccessible
unknown
tentative
duplicate
optimistic
IPv4 Default Router IP address of the IPv4 default router
DHCP Client Information (Section appears only when DHCP is enabled.)
8-154 Router ETX-2i

Field Description
Status DHCP client operational status. Available options are:

Holding Lease
Not Holding Lease
Failed to Obtain Lease
Waiting for Lease
Initializing
No Lease Address In Use
Server Displays client servers address
Lease Obtained Date and time when the DHCP lease was obtained
Lease Expires Date and time when the DHCP lease will expire, if not renewed
Lease Renewal Date and time when the device will try to renew the DHCP lease.
renewal time = (expired - obtained) * 0.5
If the lease last chance for renewal time passes, -- is displayed.
Otherwise, the next renewal time is displayed, as follows:
Date and time, formatted like other date and time values in the
device (by default as dd mm-yyyy hh:mm:ss)
If real time clock is not available, time in seconds since startup.
Lease Rebinding Date and time when the device will try to rebind the DHCP lease
Router List of default routers, in order of preference

If the first router is in use, (active) is displayed following its address.
The first router is not in use if:
There is a different static default router.
The DHCP default router is invalid, i.e., not on the devices
networks.
Static Routes File to obtain from TFTP server, received by DHCP
TFTP Server IP address of TFTP server, received by DHCP
Bootfile Name File to obtain from TFTP server, received by DHCP
Host Name Host name, received by DHCP
DHCPv6 Client Information (Section appears only if DHCPv6 is enabled.)
Server (IPv6) Displays DHCPv6 servers IP address
TFTP Server IP address of TFTP server, received by DHCPv6
Filename File to obtain from TFTP server, received by DHCPv6
Viewing NAT Translation Table

You can display the NAT translation table.
ETX-2i Router 8-155

To display the NAT translation table:

At the config>router(<number>)>nat # prompt, enter:
show nat-translations
The NAT translation table is displayed.
ETX-2IB-x86# config router 1 nat
ETX-2IB-x86>config>router(1)>nat# show nat-translations
Number of entries : 1
Entry Protocol Inside Local Inside Global Outside Local/Global

Expire in
-----------------------------------------------------------------------------
1 ICMP 30.30.30.30:1 20.20.20.30:1 10.10.10.1:0
47
Table 8-27. NAT Translation Table
Field Description
Number of Entries Total number of entries in the translation table

Entry Entry number

Protocol The associated router interface ID

Possible values: TCP, UDP, ICMP, Other
Inside Local Inside local address or address/port

Possible Values: IP address: port, where port=1-65535
Note: For Other protocol, only IP address is displayed.
Inside Global Translated inside global address or address/port

Note: For Other protocol, only IP address is displayed.
Outside Local/Global Outside global/local address or address/port

Note: For Other and ICMP protocols, only IP address is displayed
Expire in Time left for the entry to expire

Viewing NAT Statistics

You can display NAT statistics counters.
To display NAT statistics:

At the config>router(<number>)>nat # prompt, enter:
show nat-statistics
The NAT statistics are displayed.
ETX-2IB-x86>config>router(1)>nat# show nat-statistics
Translated packets Inside to Outside : 62
8-156 Router ETX-2i

Translated packets Outside to Inside : 69

Entries Created : 7
Entries Expired : 6
Dropped Packets : 0
Failed Mapping : 0
ETX-2IB-x86>config>router(1)>nat#
Table 8-28. NAT Statistics Counters
Field Description
Translated packets Number of packets translated by NAT at the Inside to Outside

Inside to Outside direction
Translated packets Number of packets translated by NAT at the Outside to Inside

Outside to Inside direction
Entries Created Number of entries created in the translation table
Entries Expired Number of entries expired and deleted in the translation table
Dropped Packets Number of packets dropped by NAT
Failed Mapping Number of entries that failed to be created in the translation table
due to table full or lack of UDP/TCP ports for allocation
Cannot delete; interface You tried to delete a router Disassociate router interfaces from
associated with the router entity that has router router.
interfaces associated with it.
Cannot delete; OSPF entity You tried to delete a router Disassociate the OSPF entity from the
associated with the router entity that has an OSPF entity router.
associated with it.
Cannot add; DHCP relay server You tried adding a dhcp-relay- Remove the already existing dhcp-
already exists server to a device that already relay-server.
has one, but only one dhcp-
relay-server is allowed per
device.
Cannot delete; DHCP relay is You tried deleting a DHCP relay Disable DHCP Relay in all router
enabled in router interface server in a router entity that is interfaces associated with the router
associated with one or more entity.
router interfaces configured to
DHCP Relay disable.
ETX-2i Router 8-157

Cannot add; IP address not legal You tried adding a DHCP relay
server with an illegal IP
address (0.0.0.0 , non-unicast,
not IPv4).
Cannot delete; OSPF Interface You tried deleting a router Disassociate the OSPF interface from
associated with the router interface associated with an the router interface.
interface OSPF interface.
Cannot set address; DHCP You tried adding an IPv4 Disable DHCP.
enabled address when DHCP is
enabled.
Cannot set address; too many You tried adding an IP address, Delete one of the associated addresses
addresses already configured but the amount of IP before associating a new IP address.
addresses already reached its
limit.
Cannot set address; invalid You tried adding a multicast IP

address or an interface IPv4
address with prefix length 32
(, which is only allowed for
loopback interface).
When configuring static-route,
you tried to do one of the
following:
Add a multicast IP network
address.
Add an IP network address
when it was not allowed.
Use /31 prefix-length on non You tried adding anIPv4

point-to-point interface interface address with prefix
cautiously length 31.
Cannot set address; Router You tried adding an IP address Unbind the router interface from the
Interface bound to PPP port when the router interface is PPP port.
bound to a PPP port.
Cannot modify; activated router You tried modifying or Shut down the router interface and try
interface removing a bound port while again.
the router interface was
activated (no shutdown).
You tried adding, modifying, or
removing a VLAN while the
router interface was activated
(no shutdown).
Cannot enable; IPv4 address You tried enabling DHCP even

exists though manual IPv4 address
exists.
Cannot enable; DHCPv6 is You tried enabling DHCP even Disable DHCPv6.
enabled though DHCPv6 is enabled.
8-158 Router ETX-2i

Cannot set; Router Interface You tried enabling DHCP while Unbind the router interface from the
bound to PPP port the router interface is bound PPP port.
to a PPP port.
OR
You tried enabling DHCPv6
client while router interface is
bound to PPP port.
Cannot enable; DHCP relay is You tried enabling DHCP client Disable DHCP relay.
enabled while DHCP relay is enabled.
Cannot enable; DHCP client is You tried enabling DHCP relay Disable DHCP client.
enabled while DHCP client is enabled.
Cannot set; DHCP relay server You tried enabling DHCP relay, Define DHCP relay server at Router
definition not exist but DHCP relay server is not level.
defined at Router level.
Cannot set; DHCPv6 client is You tried enabling DHCPv6 Remove existing DHCPv6 client.
already defined client when there is already
one defined in the device.
Cannot enable; DHCP (v4) is You tried enabling DHCPv6 Disable DHCPv4.
enabled while DHCPv4 is enabled.
Cannot set; Router Interface is You tried enabling DHCPv6 Associate DHCPv6 client with a router
loopback interface client while router interface is interface that is not defined as a
defined as loopback interface. loopback interface.
Cannot set; VRRP is enabled on You tried enabling DHCPv6 Disable VRRP on the router interface.
Router Interface client while VRRP is enabled on
the router interface.
VRRP and DHCP not allowed on You tried to enable DHCP for a Create the VRRP group for a different
the same interface router interface for which a router interface, or disable DHCP for
VRRP group is configured. the interface.
VRRP cannot be configured on You tried to bind a router Bind a different router interface to the
PPP interface for which a VRRP PPP port.
group is configured, to a PPP
port.
Cannot activate; must be bound You tried activating a router Bind the router interface to a loopback
to port interface, which is neither a interface or a port.
loopback interface nor bound
to a port.
Cannot activate; bound port in You tried activating the router

use by another router interface interface, while the bound
port is already in use by
another router interface.
ETX-2i Router 8-159

Cannot activate; bound You tried activating the router

port+vlan in use by another interface that is bound to port
router interface + vlan, while bound pair
port+vlan is already in use by
another router interface.
Cannot activate; ip address is You tried activating the router

set interface bound to PPP port,
when IP address was set.
Cannot activate; dhcp is enable You tried activating the router

interface bound to PPP port,
when DHCP is enabled.
Cannot activate; PPP lower layer You tried activating the router
is not bound interface bound to PPP port,
when PPP lower layer port is
not bound.
NAT already enabled for another You tried enabling NAT on a Disable NAT from the other router
router router instance while it was instance.
already enabled on another
router instance.
Address is not IPv4 address. You configured the IP address Configure the IP address of Inside IP
of Inside IP station with a non- station with an IPv4 address.
IPv4 address.
NAT rule with the same inside You configured the static NAT
global address already exists with the same inside global IP
(translated IP) as another
static NAT.
NAT rule with the same inside You configured the static NAT
local address already exists with the same inside local IP
(source IP) as another static
NAT.
Port static NAT rule with the You configured a hole

same inside global address and punching static NAT (port
port already exists static NAT) with the same
inside global IP (translated |IP)
as another port static NAT.
Port static NAT rule with the You configured a hole

same inside local address and punching static NAT (port
port already exists static NAT) with the same
inside local IP (source |IP) as
another port static NAT.
Timeout is out of range Expiration timeout of

TCP/UDP/other protocol
entries in NAT translation table
is out of the allowed range
(60-43200).
8-160 Router ETX-2i

8.12 Routing Protocol BGP

BGP (Border Gateway Protocol) is a path-vector protocol for dynamic routing,
used for route distribution between Autonomous Systems (AS) across the
internet and other large networks.
Standards and MIBs

The BGP feature adheres to the following standards:
Table 8-30. Standards and MIBs
Reference Title
RFC 4271 A Border Gateway Protocol 4 (BGP-4)
RFC 4893 BGP Support for Four-octet AS Number Space
RFC 5396 Textual Representation of Autonomous System (AS) Numbers
RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature Option
RFC 2545 Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
The following BGP features are not supported:

Graceful restart (RFC 4724)
Interaction with ECMP
Benefits
Dynamic routing protocols enable routing tables to automatically adapt to
changing networks. BGP is the de-facto standard in the internet for
communicating routing information between Autonomous Systems (AS), making
it the only option for AS boundary routers (ASBR) to enable route communication
with other ASes.
In the context of RAD devices, BGP is intended for use on customer-premises
equipment (CPE) at the boundary of a large customer network that is an
independent stub AS connected to only one other AS (the service provider
network).
BGP functionality is explained in the following sections.
Show Me Demo
The following video gives an overview of BGP.
ETX-2i Routing Protocol BGP 8-161

Reader.
Dynamic Routing Protocols

Routers direct packets through their various interfaces according to their routing
tables, which specify an exit interface for each destination IP network. While
routing tables can include static, manually configured routes, an optimized
routing table requires knowledge of remote network topology and complex path
calculations. Dynamic routing protocols define how routers communicate network
topology with each other and how they accordingly calculate optimized network
paths and create their routing tables.
The internet is divided into Autonomous Systems (AS). An AS is usually the
network of an Internet Service Provider (ISP) or another large organization that
administers the AS-internal routing policy. Routing information inside each AS is
communicated and determined by an Interior Gateway Protocol (IGP) such as
OSPF; routing information between ASes is communicated by the Border Gateway
Protocol (BGP).
BGP: Path-Vector Routing

BGP is a path-vector routing protocol. As opposed to link-state protocols, in
which network topology is communicated throughout a network, and as opposed
to distance-vector protocols, in which routers communicate destination
distances, routers using a path-vector protocol communicate actual paths, or
routes, to destinations.
In BGP, communicated paths for each destination contain the IP address of the
first hop, and the list of ASes, by AS numbers (ASN), which need to be traversed
to reach the destination. BGP aggregates routes, and, to prevent loops and to
choose among the path alternatives, each BGP router decides which actual routes
to adopt among BGP updates received from its neighbors and which of its known
routes to advertise to its neighbors. BGP makes these decisions using
optimization algorithms and (in other BGP implementations) additional criteria
from a locally configurable policy.
BGP Neighbors
BGP is configured only on AS Boundary Routers (ASBR). Each BGP router
recognizes a limited list of BGP neighbors from which it receives route updates
and to which it advertises route updates. A BGP neighbor relationship needs to
be manually defined on both BGP routers. BGP routers identify neighbors by their
IP addresses and AS numbers.
BGP neighbors always belong to the IPv4 unicast address family, and can
optionally belong to the IPv6 unicast address family.
8-162 Routing Protocol BGP ETX-2i

AS-Internal Destination Injection

To be able to advertise its local AS-internal destinations to the rest of the
internet, BGP needs to know what destination networks are included in its local
AS. BGP can become aware of these networks in several configurable ways:
BGP can be configured to redistribute static routes from the routers routing
table.
BGP can be configured to redistribute connected networks.
BGP can be configured to redistribute routes from the AS IGP (OSPF).
Supported only for IPv4 address family.
Specified network addresses can be manually configured in BGP. These
destinations are advertised only if they are found in the local routing table.
AS Numbers (ASN)
BGP communicates paths as a list of numbers of the ASes that need to be
traversed to reach destinations. Generally, ASNs uniquely define the AS, and are
allocated for the individual AS by the Internet Assigned Numbers Authority
(IANA); however, ISPs can define private ASes for their customer networks with
ASNs in the range 6451265534.
Limiting Received Routes

The number of routes received can be limited for each neighbor. When the
number of received routes reaches 90% of the configured value, the device
generates an alarm and sends an SNMP trap. When the configured value is
exceeded, the session goes down for five minutes.
BGP Session Timers

BGP neighbors send each other keep-alive messages to confirm the connections
health. Two parameters are defined:
keepalive is the interval, in seconds, between messages confirming connection
health to the neighbor. If the value is 0, these messages are disabled.
holdtime is the interval, in seconds, after which the connection with the neighbor
is considered down if no keep-alive messages have been received from the
neighbor. If the value is 0, the neighbor is never considered down.
Upon session initiation, the neighbors negotiate for each of these two
parameters and then both use the lower of their values. Negotiated values can be
viewed (see Viewing Neighbor Connection Status).
Either both parameters must be non-zero or both must be zero.
Routing Preferences
static routes, connected networks, OSPF routes, and BGP routes, the routers
Routing Table Manager (RTM) chooses among the sources according to
configurable source preference indices (lowest number indicates highest priority).
Separate preference indices are defined for BGP routes received from BGP
neighbors in the same AS (Internal BGP) and for BGP routes received from BGP
neighbors in other ASes (External BGP).

BGP Path Attributes

Path attributes are contained in BGP update packets. The path attributes of
advertised routes are used to select the route from multiple routes, and to
propagate policy.
BGP path attributes have the following types:
Well-known Must be supported and propagated

mandatory
Well-known Must be supported; propagation optional

discretionary
Optional transitive Marked as partial if unsupported by neighbor
Optional Deleted if unsupported by neighbor

nontransitive
The following table lists the path attributes.
Table 8-31. BGP Path Attributes
Name Description Path Type
1 Origin Origin type (IGP, EGP, or unknown) Well-known mandatory
2 AS Path List of autonomous systems which the Well-known mandatory

advertisement has traversed
3 Next Hop External peer in neighboring AS Well-known mandatory
5 Local Preference Metric for internal neighbors to reach external Well-known discretionary
destinations (default 100)
6 Atomic Aggregate Includes ASes that have been dropped due to Well-known discretionary
route aggregation
7 Aggregator ID and AS of summarizing router Well-known discretionary
8 Community Route tag Well-known discretionary
4 Multiple Exit Metric for external neighbors to reach the local AS Optional nontransitive
Discriminator (MED) (default 0)
9 Originator ID The originator of a reflected route Optional nontransitive
10 Cluster List List of cluster IDs Optional nontransitive
13 Cluster ID Originating cluster Optional nontransitive
-- Weight Cisco proprietary, not communicated to peers Optional nontransitive

(default 0)
BGP Policies
The BGP functionality provides a flexible filtering mechanism to ensure that the
router processes only relevant BGP update packets. The filtering is done by
means of defining BGP policy profiles of the following types:

Prefix lists Filter by prefix and prefix length, where prefix is specified
by IP address and mask, with prefix length between 24 and
26
Route maps Permit/deny if packet matches community in the form x:y.

The community is a BGP path attribute (see Table 8-32)
that is usually set by each network.
BGP policy profiles are assigned per IPv4/IPv6 unicast address family per neighbor.
One of each policy profile type can be assigned in the inbound direction (to be
applied to received packets) and outbound direction (to be applied to advertised
packets), per IPv4/IPv6 unicast address family per neighbor.
BGP policy profiles comprise sequentially numbered rules, each of which can be
one of the following:
Permit action Specifies criteria for permitting packet, and optionally sets
action in case of route map profile
Deny action Specifies criteria for dropping a packet
Remark Used for commenting and visually organizing rules
If there is a need to add a rule between already existing rules with consecutive
sequence numbers, the rules can be interspaced to accommodate additional rules
between them.
The packet filtering is done as follows: Each BGP update packet is checked
according to the associated prefix list policy (if exists), and then the
associated route map policy (if exists), starting with the first rule.
If the packet doesnt match a rule, the next rule according to the sequence
number is checked.
If the packet matches a deny rule, it is dropped, and the filtering ends.
If the packet matches a permit rule, the packet is permitted. Any set
operation in the rule is performed, in the case of route map profile.
If the packet doesnt match any rule, it is dropped.
Maintained Information
BGP maintains the following network information, all of which can be viewed (see
Viewing BGP Status):
Neighbor connectivity details
Per-neighbor received routes
Per-neighbor advertised routes
Per-neighbor policy profiles
Per-neigbor communities
Per-neighbor RIB
Per neighbor summary

Factory Defaults
By default, BGP is not configured on RAD routers. The following tables show the
default values when it is configured.
Router
The following parameters determine BGP behavior for the whole router, for all
interfaces:
Table 8-32. Router BGP Parameters
bgp Whether BGP is defined (but not necessarily enabled) no bgp

on this router, and the local ASN
router-id ID for router in BGP communications, in IP address --

format (mandatory configuration)
shutdown Enable (no shutdown) / disable (shutdown) BGP on the shutdown

router
IPv4 and IPv6 Unicast Address Family

The following parameters characterize behavior for the IPv4/IPv6 unicast address
families, for all BGP neighbors. The parameters for IPv4 and IPv6 have the same
names but are defined in separate levels.
Table 8-33. IPv4/IPv6 Unicast Address Family Parameters
external-preference Preference index for external BGP routes. See Routing 20

Preferences.
internal-preference Preference index for internal BGP routes. See Routing 200
Preferences.
network AS-internal networks that should be advertised to BGP no network

neighbors. See AS-Internal Destination Injection.
redistribute Sources other than BGP of routes that should be advertised no redistribute
to BGP neighbors. See AS-Internal Destination Injection.
Neighbor
The following parameters determine BGP behavior per neighbor:
Table 8-34. Neighbor BGP Parameters
active Whether IPv6 is enabled (active) or disabled (no active) no active

for the neighbor

local-address The local IP address from which to advertise BGP --

updates to the neighbor (Uses closest interface to
neighbor)
max-prefixes The maximum number of destination networks to 0

receive from the neighbor (=no limit)
password Secret key for authentication of and to the neighbor no password
remote-as The neighbors ASN --

(mandatory configuration)
shutdown Whether the neighbor is administratively enabled (no shutdown

shutdown) or disabled (shutdown) for
keepalive Interval, in seconds, between messages confirming 30

connection health to the neighbor
holdtime Interval, in seconds, after which the connection with 90

the neighbor is considered down if no keepalive
messages have been received from the neighbor
Configuring BGP
You can configure BGP on a RAD router that is at the boundary of an AS, after
the router itself has been properly configured. To configure BGP properly, you
need to know your network BGP design, including the routers IP address and
ASN, designated BGP neighbors IP addresses and ASNs, whether IPv6 is required,
and the desired method of passing AS-internal destinations to BGP.
When multiple VPN routers are configured on a device, each router should be
configured with its own instance of BGP. All of these BGP instances must share
the same ASN.
BGP parameters are configured at the following levels:
Configuring BGP at Router Level: Parameters that determine BGP behavior for
the whole router, for all IP families and neighbors
Configuring BGP Neighbors: Per-neighbor parameters
Configuring IPv4/IPv6 Unicast Address Families: Parameters that characterize
BGP behavior for IPv4/IPv6 unicast address families.
Follow these steps to configure BGP:
1. Define the BGP router IP address and ASN (see Configuring BGP at Router
Level).
2. Administratively enable BGP.
3. Define any necessary BGP neighbors, along with the remote AS to which the
neighbor belongs (see Configuring BGP Neighbors).
4. Administratively enable the BGP neighbors.
5. If it is necessary for BGP to be aware of AS-internal destinations that need to
be advertised, configure redistribution (of OSPF routes, static routes, and/or

connected networks) or explicit networks, for IPv4 and IPV6 unicast address
families (see Configuring IPv4/IPv6 Unicast Address Families).
6. For each BGP neighbor, if network design requires any non-default values for
IPv4 and IPV6 unicast address families, configure the parameters (see
Configuring Neighbor Parameters).
Configuring BGP at Router Level
To configure BGP:
1. At the config>router(<number>)# prompt, type:
[no] bgp <ASN>
The config>router(<number>)>bgp(<ASN>)# prompt is displayed.
Notes <ASN> is the number of the local AS where the router is located
Type no bgp <ASN> to remove BGP from the router (if no neighbors are
defined).
Enabling BGP on the [no] bgp <ASN> <ASN> is the number of the local AS where the
router router is located.
Restarting BGP session clear-neighbor <IP-address> <IP-address> is the neighbors IP address (IPv4 or
with neighbor and [soft] IPv6).
reloading BGP policy If you specify soft, the link with the neighbor is
profiles not reset, but the BGP policy profiles are
reloaded.
Configuring BGP ipv4-unicast-af See Configuring IPv4/IPv6 Unicast Address

parameters for IPv4 or ipv6-unicast-af Families.
IPv6 unicast address
family
Configuring BGP neighbor <IP-address> <IP-address> is the neighbors IP address (IPv4 or

neighbor IPv6). See Configuring BGP Neighbors.
no neighbor <IP-address> removes the neighbor
from BGP configuration.
Defining IP address for router-id <IP-address> To simplify management, the IP address can be
the router in BGP the actual IP address of one of the routers
communications interfaces, or there may be some other
organizational convention.
Defining or changing the router IP address
requires BGP to be administratively disabled
(shutdown).
Displaying the IPv4 or show community { ipv4 | ipv6 } See Viewing BGP Communities.
IPv6 community table
Displaying the IPv4 or show rib { ipv4 | ipv6 } See Viewing BGP RIB.
IPv6 RIB (Routing
Information Base) table

Displaying summary of show summary See Viewing BGP Summary.

neighbor connections
information
Administratively [no] shutdown To disable: shutdown;to enable: no shutdown

enabling or disabling When BGP is disabled, operational status of BGP
BGP on the router neighbors moves down.
Configuring BGP Neighbors

You can define BGP neighbors to represent neighboring routers from which the
BGP router entity receives route updates and to which it advertises route
updates.
To configure BGP neighbors:

1. At the config>router(<number>)>bgp(<ASN>)# prompt, type:
neighbor <IP-address>
The config>router(<number>)>bgp(<ASN>)> neighbor(<IP-address>)#
prompt is displayed.
Defining the local IP [no] local-address local-address <IP-address> sets a parameter

address from which to [<IP-address>] value; no local-address clears the parameter.
advertise BGP updates When no local address is set (default), BGP
to the neighbor uses the closest interface to the neighbor.
The change takes effect only after
clear-neighbor or shutdown.
Setting the maximum max-prefixes <prefixes> <prefixes> is a number in range:

number of routes to 02147483647. 0 means no limit.
accept from the See Limiting Received Routes.
neighbor
Change takes effect only after clear-neighbor
or shutdown.
Setting password for [no] password <password> The <password> can be up to 80 characters.
neighbor session [hash] hash specifies that the password should be
encrypted.
no password deletes the password.
Change takes effect only after clear-neighbor
or shutdown.
Defining neighbors ASN remote-as <ASN> Available only when communication with the
neighbor is disabled (shutdown).
Setting keepalive and timers <keepalive> See BGP Session Timers.

holdtime timers <holdtime> Change takes effect only after clear-neighbor
or shutdown.

Viewing connectivity show neighbor-connection See Viewing Neighbor Connection Status.

details
Enabling or disabling BGP [no] shutdown To enable: no shutdown (requires remote-as

communication with the to have been configured)
neighbor To disable: shutdown .
Configuring IPv4/IPv6 Unicast Address Families

The parameters for IPv4/IPv6 unicast address families are configured in the levels
configure router <number> bgp <ASN> ipv4-unicast-af and configure router
<number> bgp <ASN> ipv6-unicast-af, respectively. You can configure general
parameters for the unicast address families, or neighbor parameters.
Configuring Unicast Address Family Parameters
To configure IPv4/IPv6 unicast address families:

1. At the config>router(<number>)>bgp(<ASN>)# prompt, type one of the
following, according to whether you wish to configure BGP parameters for
IPv4 or IPv6 unicast address families:
ipv4-unicast-af
ipv6-unicast-af
The prompt config>router(<number>)>bgp(<ASN>)>ipv4-unicast-af# or
config>router(<number>)>bgp(<ASN>)>ipv6-unicast-af# is displayed.
Defining the preference external-preference <priority> <priority> should be an integer in range 0255.
index for external BGP See Routing Preferences.
routes
Priority can be changed at any time.
Defining the preference internal-preference <priority>
index for internal BGP
routes
Specifying a neighbor neighbor <IP-address> See Configuring Neighbor Parameters.

router
Defining an explicit network <IP-address> is the networks IP address, and

network that should be <IP-address>/<netmask> <netmask> is the length of the network part
advertised to BGP (CIDR notation).
neighbors as a Each added network requires a separate
destination in this AS command.
To delete the network entity: no network
<IP-address>/<netmask See AS-Internal
Destination Injection.

Defining non-BGP [no] redistribute {connected | To disable distribution: no redistribute {

sources of routes that static | ospf} connected | static | ospf}.
should be advertised to Each source protocol (connected, static, ospf)
BGP neighbors requires a separate command.
For IPv6, only the connected and static options
are supported.
See AS-Internal Destination Injection.
Configuring Neighbor Parameters
To configure BGP neighbor parameters under IPv4/IPv6 unicast address families:

1. At the prompt config>router(<number>)>bgp(<ASN>)> ipv4-unicast-af# or
config>router(<number>)>bgp(<ASN>)> ipv6-unicast-af#, type:
neighbor <IP-address>
The prompt config>router(<number>)>bgp(<ASN>)>ipv4-unicast-af>
neighbor(<IP-address>)# or config>router(<number>)>bgp(<ASN>)>
ipv6-unicast-af neighbor>(<IP-address>)# is displayed.
Enabling or disabling [no] active Enable active

IPv4 or IPv6 BGP for Disable no active
the neighbor
You cannot type no active for IPv4, as the address family
IPv4 unicast is always enabled for all neighbors.
Associating prefix list prefix-list-bind Type no before the command to remove the association with
BGP policy with the <name> {in | out} the prefix list.
neighbor unicast
address family for
incoming or outgoing
direction
Associating route route-map-bind Type no before the command to remove the association with
map BGP policy to the <name>{in | out} the route map.
neighbor unicast
address family for
incoming or outgoing
direction
Viewing routes show See Viewing Advertised Routes.

advertised to the advertised-route
neighbor
Displaying any show prefix-list See Viewing BGP Policy Profiles.

associated prefix list
policy profiles and
rules related to a BGP
neighbor per AF

Viewing routes show See Viewing Received Routes.

received from the received-route
neighbor
Displaying any show route-map See Viewing BGP Policy Profiles.

associated route map
policy profiles and
rules related to a BGP
neighbor per AF
Configuring BGP Policy Profiles

BGP policy profiles are configured at the router level. They can be prefix list or
route map policy profiles (see BGP Policies for more information). After changing
a policy profile, you should use the command clear-neighbor with the soft
parameter, to ensure that the change is applied to the neighbor BGP policies.
To configure BGP policy profiles:

1. Navigate to configure router <number>.
2. Enter the necessary commands according to the table below.
3. See Configuring Prefix List Rules or Configuring Route Map Rules respectively,
for commands to configure the rules in a prefix list policy profile or route map
policy profile
Configuring prefix list policy prefix-list <name> {ipv4 | ipv6} Type no prefix-list <name> to delete the
profile, for IPv4/IPv6 prefix list.
Configuring route map policy route-map <name> Type no before the command to delete
profile the route map.
Reseqencing the rules in a resequence <name> This command can be used when you
policy profile [<number>] need to insert rules in the middle of a
policy profile.
<name> name of the policy profile
<number> steps to insert between the
rule sequence numbers. For instance, if
you specify 10, the rule sequence
numbers are changed to 10, 20, 30, etc.
Range for <number>: 1100000.
Configuring Prefix List Rules
To configure the rules in a prefix list policy profile:

1. Navigate to configure router prefix-list <name> {ipv4 | ipv6}.
2. Enter the necessary commands according to the tasks listed below.

Removing a rule delete <sequence> <sequence> sequence number of the

rule to delete
Adding a deny deny <prefix>/<length> [ge <ge-value>] <prefix>/<length> prefix and length
rule [le <le-value>] [sequence <sequence>] identifying the network that this rule
matches, in the following form
according to IPv4 or IPv6:
(IPv4) <IPv4 address>/<132>
(IPv6) <IPv6 address>/<1128>
ge Rule matches packets with prefix
length greater than or equal to
<ge-value>.
le Rule matches packets with prefix
length less than or equal to <le-value>.
sequence assigns <sequence> as the
sequence number of the rule.
Sequence number range:
12147483648
The ge and le parameters are validated as
follows:
(IPv4) Prefix length <ge < le <= 32
(IPv6) Prefix length <ge < le <= 128
Adding a permit permit <prefix>/<length> [ge <ge-value>] For an explanation of the parameters, see
rule [le <le-value>] [sequence <sequence>] the comments above for the deny rule.
Adding a remark remark [<description>] [sequence The description can contain up to

<sequence>] 252 characters.
Configuring Route Map Rules
To configure the rules in a route map policy profile:

1. Navigate to configure router route-map <name>.
Removing a rule delete <sequence> <sequence> sequence number of the rule

to delete

Adding a deny deny [match [as-path string] [community as-path BGP AS Path that this rule uses
rule string] [ prefix-list string] ][sequence to match to a route in ASCII format; in
sequence>] regular expression format (permitted
length 0127 characters).
Note: AS numbers are matched as decimal
numbers. For example, the AS number
'0x0123' should be represented in the
regular expression string as '291'. A NULL
string indicates that the field is not in use.
community BGP community that this
rule matches, in the form aa:nn
(permitted length 0127 characters). If
community is not specified, this rule
matches all packets.
Note: Community has the new-format
decimal notation. For example, the
community '0x00120101' should be
represented in the string as '18:257'.
prefix-list - BGP policy prefix-list profile
name that this rule matches; permitted
length 080 characters
sequence Assigns <sequence> as the
Sequence number range: 12147483648

Adding a permit permit[match [as-path string] [community as-path BGP AS Path that this rule uses
rule, and string] [ prefix-list string] ][set [as2-path- to match to a route in ASCII format; in
optionally prepend string] [as4-path-prepend string] regular expression format (permitted
specifying set [community string] [local-preference length 0127 characters).
actions number] [med number] ][sequence Note: AS numbers are matched as decimal
sequence>] numbers. For example, the AS number
'0x0123' should be represented in the
regular expression string as '291'. A NULL
string indicates that the field is not in use.
community BGP community that this
rule matches, in the form aa:nn
(permitted length 0127 characters). If
community is not specified, this rule
matches all packets.
Note: Community has the new-format
decimal notation. For example, the
community '0x00120101' should be
represented in the string as '18:257'.
prefix-list - BGP policy prefix-list profile
name that this rule matches; permitted
length 080 characters
set Specify set actions for BGP path
attributes (see Table 8-32).
as2-path-prepend/as4-path-prepend
Set AS prepend (for 2/4 octets AS size)
to <string>; permitted length 0127
characters
Note: You can define only one as-path-
prepend statement - as2-path-prepend or
as4-path-prepend.
community Set community to a string
in the form aa:nn (permitted length 0
127 characters.
local-preference Set local preference to
<number>.
med Set Multiple Exit Discriminator
(MED) to <number>.
sequence Assigns <sequence> as the
Sequence number range:
12147483648
Adding a remark remark [<description>] The description can contain up to

[sequence <sequence>] 255 characters.

Examples
This section illustrates configuring BGP policy profiles.
To configure prefix list (IPv4):

BGP AS = 65530
Neighbor IP address = 120.120.120.120
Permit routes with prefix 100.102.0.0/11, and prefix length 2426
exit all
#****** Configure the prefix list
configure router 1
prefix-list subnetsIN ipv4
permit 100.102.0.0/11 ge 24 le 26 sequence 10
remark "permit 100.102.0.0/11 with prefix length 24 to 26" sequence 10000
exit
#****** Bind the prefix list

bgp 65530 ipv4-unicast-af neighbor 120.120.120.120
prefix-list-bind subnetsIN in
exit all
#****** Reload BGP policy profiles for the neighbor

configure router 1 bgp 65530
clear-neighbor 120.120.120.120 soft
save
To configure the prefix list (IPv6):

BGP AS = 65530
Neighbor IP address = 78:78:78::78
Permit routes with prefix 123a:bbb1::/28 and prefix length 5066
exit all
#****** Configure the prefix list
configure router 1
prefix-list subnetsIN ipv6
permit 123a:bbb1::/28 ge 50 le 66 sequence 10
remark "permit 123a:bbb1::/28 with prefix length 50 to 66" sequence 10000
exit
#****** Bind the prefix list

bgp 65530 ipv6-unicast-af neighbor 78:78:78::78
prefix-list-bind subnetsIN in
exit all

clear-neighbor 78:78:78::78 soft
save
To configure the route map (IPv4):

BGP AS = 65530

Neighbor IP address = 120.120.120.120

Deny subnets with community 1:10
exit all
#****** Configure the route map
configure router 1
route-map commIN
deny match community 1:10 sequence 10
remark "deny subnets with community 1:10" sequence 10000
exit
#****** Bind the route map

bgp 65530 ipv4-unicast-af neighbor 120.120.120.120
route-map-bind commIN in
exit all

clear-neighbor 120.120.120.120 soft
save
To configure the route map (IPv6):

BGP AS = 65530
Neighbor IP address = 78:78:78::78
Permit subnets with community 1:10
exit all
#****** Configure the route map
configure router 1
route-map commIN
permit match community 1:10 sequence 10
remark "permit subnets with community 1:10" sequence 10000
exit
#****** Bind the route map

bgp 65530 ipv6-unicast-af neighbor 78:78:78::78
route-map-bind commIN in
exit all

clear-neighbor 78:78:78::78 soft
save
Configuration Example
In this example, a customer-premises RAD device has been placed at the
boundary of an organizations network, which is an independent AS. The RAD
device needs to be configured for BGP.
The only BGP neighbor is the Provider Edge (PE) router. Since this is a stub AS, it
has been decided that AS-internal destinations should be aggregated and
manually defined (with the network command) rather than enabling automatic
redistribution. IPv6 is required for this network.

Device IP ASN
CPE ASBR (the device being configured for BGP) 10.10.1.1 64515
PE (BGP neighbor) 10.10.10.1 613
The configuration process for this example is:

#***** Configure BGP on router
configure router 1
bgp 64515
router-id 10.10.1.1
no shutdown
#***** define AS-internal networks for advertisement
ipv4-unicast-af
network 10.10.1.0/24
exit
ipv6-unicast-af
network fc00:1234:a1b1:0000:0000:0000:0000:0000/48
exit
#***** configure neighbor
neighbor 10.10.10.1
remote-as 613
no shutdown
exit all
save
Cannot delete; BGP neighbor You tried to run no bgp, but Delete all neighbors and try again.
exist there are configured BGP
neighbors.
Cannot create; AS number must You tried to define BGP with Use the same ASN for BGP on all the
be equal for all BGP entities an ASN different from the BGP devices routers.
ASN configured for another
router on this device.
Cannot clear; unknown neighbor You tried to run clear-neighbor Use the correct IP address configured
on an IP address that is not for the neighbor.
configured for any defined
BGP neighbor.
Cannot set; AS number change You tried changing the BGP Delete all BGP entities, and then
requires deletion of all BGP ASN before deleting all BGP change the ASN.
entities entities.
Cannot set; change requires bgp You tried to set the router-id Run shutdown and then try again.
shutdown with BGP running.

Cannot activate; router-id You tried to enable BGP (no Set the router-id and try again.
number must be set shutdown) without having set
the router-id.
Cannot set; No such neighbor You tried to enter an IP / Use the correct IP address configured
neighbor context, but you for the neighbor.
specified an IP address that is
not configured for any
neighbor.
Cannot set; ipv4 unicast address You tried using the active IPv4 cannot be disabled for any
family always enable command in the IPv4 neighbor neighbors. If you meant to enable or
CLI context. disable IPv6, navigate to
config>router(<number>)>bgp(<ASN>)
>ipv6-unicast-af>neighbor(<IP-address
>)# and try again.
Cannot activate; remote IP You tried to run no shutdown Set the neighbors ASN (with the
address and AS number must be for a BGP neighbor, but this remote-as command) and then try
set neighbor does not yet have an again.
ASN.
Cannot set; Hold time should be You tried to run the timers Run the command again with hold time
greater than the keepalive time command with hold time less greater than keepalive time.
than or equal to keepalive
time.
Cannot bind; policy profile type You tried to bind a policy Change policy type to prefix-list-ipv4 or
does not match profile that does not match prefix-list-ipv6).
the required policy type
(prefix-list-ipv4 or prefix-list-
ipv6).
Cannot bind; prefix-list profile You tried to bind prefix-list Unbind route-map profile with match
already in use in match profile when route-map profile prefix-list statement from the BGP
statement with match prefix-list connection.
statement is already bound to
the same BGP connection.
Cannot bind; no such policy You tried to bind a policy Create the policy profile that you want
profile profile that does not exist. to bind.
Cannot bind; policy profile type You tried to bind a policy Bind the policy profile to route-map.
does not match profile that does not match
the required type (route-map)
Cannot bind; address-family You tried to bind a route-map Create a prefix-list address-family that
mismatch with match statement profile with match prefix-list is identical to bound connection
statement with a prefix-list address-family.
address-family that is not
identical to bound connection
address-family.

Cannot bind; prefix-list profile You tried to bind a route-map Unbind prefix-list profile from the BGP
already bound profile with match prefix-list connection.
statement when prefix-list
profile is bound to the same
BGP connection.
Cannot delete; prefix list is You tried to delete a prefix Unbind the policy profile from all
matched in a route-map list that is matched in a route- entities bound to it.
map.
Cannot create; name already in You tried creating a prefix-list Choose a unique name for the newly
use policy profile with a name that created prefix-list policy profile.
already exists in the system.
Cannot add statement; wrong You tried adding a rule with an Use the appropriate address type.
prefix address type address type (ipv4 or ipv6)
that is not related to the
profile type.
Cannot add statement; wrong You tried adding a rule with Correct the length paremeters so that
length parameters incorrect length parameters. length < ge-value <= le-value <=
address length of family (32 or 128).
Cannot add statement; regular The regular expression that Enter a new regular expression for the
expression is incorrect you entered does not translate AS path.
into a valid AS path.
Cannot add statement; no such You tried adding a statement Create the prefix-list profile or use an
policy profile with a prefix-list profile that existing prefix-list profile.
does not exist.
Cannot add statement; prefix- You tried adding a statement Use a prefix-list profile address-family
list address-family mismatch with a prefix-list profile that is similar to previous statements.
address-family that is different
than similar previous
statements.
Cannot add statement; the You tried adding a statement, Unbind the route map from the bgp
route-map is bound to bgp but the route-map profile connection.
connection with bound prefix- (with the new match prefix-
list list statement) is bound to a
connection with a bound
prefix-list profile.
Warning: prefix list profile You used a prefix-list profile Use another prefix-list profile or
contains permit statement that contains at least one remove all permit statements from
permit statement. the current prefix-list profile.
Set timer to 0 requires You tried to run the timers Run the command again with either
holdtime = keepalive = 0 command with one 0 value. both or neither parameter being 0.
Either both or neither must be
0.

Viewing BGP Status

You can view the current configuration (see Viewing the Current Configuration),
status of the connection with each configured neighbor (see Viewing Neighbor
Connection Status), and routes received from and advertised to each neighbor
(see Viewing Received Routes and Viewing Advertised Routes). This information
can be used for testing (see Testing BGP) and debugging.
Viewing the Current Configuration

To view the configuration, use the commands info (to include only non-default
configuration) and info detail (to include default configuration).
You can view this info at any of the following configuration levels:
Level Context Prompt
Router config>router(<number>)>bgp(<ASN>)#
IPv4/IPv6 unicast config>router(<number>)>bgp(<ASN>)>ipv4-unicast-af#

address family config>router(<number>)>bgp(<ASN>)>ipv6-unicast-af#
Neighbor config>router(<number>)>bgp(<ASN>)>neighbor(<IP-address>)#
IPv6 neighbor config>router(<number>)>bgp(<ASN>)>ipv6-unicast-af>neighbor

(<IP-address>)#
For example:
ETX-2i>config>router(1)>bgp(64515)# info detail
router-id 10.10.1.1
no shutdown
echo "BGP Neighbor Configuration"#
# BGP Neighbor Configuration
neighbor 10.10.10.1
local-address 0.0.0.0
max-prefixes 0
password "" hash
remote-as 613
no shutdown
timers keepalive 30 holdtime 90
exit
echo "IPv4 Unicast Address Family Configuration"
# IPv4 Unicast Address Family Configuration
ipv4-unicast-af
external-preference 20
internal-preference 200
redistribute ospf
echo "IPv4 Unicast Address Family - Neighbor Configuration"
# IPv4 Unicast Address Family - Neighbor Configuration
neighbor 10.10.10.1
active
exit
exit
echo "IPv6 Unicast Address Family Configuration"
# IPv6 Unicast Address Family Configuration
ipv6-unicast-af

echo "IPv6 Unicast Address Family - Neighbor Configuration"
# IPv6 Unicast Address Family - Neighbor Configuration
neighbor 10.10.10.1
no active
exit
exit
Viewing Neighbor Connection Status

You can view connectivity details with any configured BGP neighbor by using the
show neighbor-connection command. This command is available in the BGP
neighbor CLI context:
config>router(<number>)>bgp(<ASN>)>neighbor(<IP-address>)#. You can use
this information for troubleshooting and testing.
For example:
ETX-2i>config>router(1)>bgp(64515)>neighbor(10.10.10.1)# show neighbor-connection
Remote Host: 10.10.10.1
Remote Port: 179
Local Host : 0.0.0.0
Local Port : 36586
Remote AS : 613
BGP State: Active Up for 12d 06:23:53

Hold Time (seconds) : 180 Keepalive Interval (seconds): 60
Last Error : None
Neighbor Advertised Capabilities

---------------------------------------------------------------------------
Address Family IPv4 Unicast : Advertised and received
Address Family IPv6 Unicast : Advertised and received
Route refresh : Advertised and received
Graceful Restart : None
Four Octet AS : Received
Viewing Received Routes

You can view the database of routes received from a particular neighbor by using
the show received-route command. This command is available in the CLI contexts
for IPv4 or IPv6 unicast address families, at the neighbor level:
config>router(<number>)>bgp(<ASN>)>ipv4-unicast-af>neighbor(<IP-address>)#
or config>router(<number>)>bgp(<ASN>)>ipv6-unicast-af>
neighbor(<IP-address>)#.
To display the received routes for IPv4 unicast address families:
ETX-2i>config>router(1)>bgp(1)>ipv4-unicast-af>neighbor(2.2.2.2)# show
received-route
Network > Next Hop MED LocPrf Path
=============================================================================
===
0.0.0.0/0 > 172.17.171.1 1000 2000 3000 1000 100 2333
111.222.111.220/30 > 111.222.111.223 65200 65200 4000 800 65500

To display the received routes for IPv6 unicast address families:

ETX-2i>config>router(1)>bgp(1)>ipv6-unicast-af>neighbor(1:1:1:1::2)# show
received-route
=============================================================================
===
::/0 > 11:11:11:11::1 1000 2000 3000 1000 100 2333
11:11:11:11::/64 > :: 1000 2000 3000 1000 100
abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd/126
> abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 65200 65200 4000 80 65500
Table 8-36. BGP Received Routes Field Descriptions
Field Description

Next Hop Neighbor IPv4 or IPv6 address
MED Number of Multi-exit Discriminators (in decimal value)

LocPrf Local preference

Path
Viewing Advertised Routes

You can view the database of routes that are advertised to a particular neighbor
by using the show advertised-route command. This command is available in the
CLI contexts for IPv4 or IPv6 unicast address families, at the neighbor level:
To display the advertised routes for IPv4 unicast address families:

advertised-route
A = advertised, S = suppressed, E = endingWithdrawal W = withdrawn
=============================================================================
===
A 0.0.0.0/0 > 172.17.171.1 1000 2000 3000 1000 100 2333
A 111.222.111.220/30 > 111.222.111.223 65200 65200 4000 800 65500
To display the advertised routes for IPv6 unicast address families:

ETX-2i>config>router(1)>bgp(1)>ipv6-unicast-af>neighbor(1:1:1:1::2)# show
advertised-route
A = advertised, S = suppressed, E = endingWithdrawal W = withdrawn
=============================================================================
===

A ::/0 > 11:11:11:11::1 1000 2000 3000 1000 100

2333
S 11:11:11:11::/64 > :: 1000 2000 3000 1000 100
A abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd/126
Table 8-37. BGP Advertised Routes Field Descriptions
Field Description
Status Status of route

Possible values are:
A advertised
S suppressed
E endingWithdrawal
W withdrawn
Neighbor IPv4 or IPv6 network address (prefix and prefix length)

Next hop Neighbor IPv4 or IPv6 address


Path
Viewing BGP Policy Profiles

You can view the BGP policy profiles assigned to a particular neighbor by using
the command show prefix-list or show route-map. These commands are available
in the CLI contexts for IPv4 or IPv6 unicast address families, at the neighbor level:
To display the prefix list policy profiles assigned to the neighbor 1.1.1.1 IPv4
unicast family:
prefix-list
Name: aaaaaAAAAAbbbbbBBBBBcccccCCCCCdddddDDDDD (In)

10 deny 10.10.10.0/24 (hit count: 2)
20 permit 3.3.3.0/24 ge 25 le 27 (hit count: 35)
Name: XXXX (Out)
100000 permit 2.2.2.0/24 10 (hit count: 35)

To display the prefix list policy profiles assigned to the neighbor 10:10:10::10
IPv6 unicast family:
ETX-2i>config>router(1)>bgp(64515)>ipv6-unicast-af>neighbor(10:10:10::10)#
show prefix-list

100000 permit 1234:1234:1234:1234:1234:1234:1234:1234/100 ge 110 le 120
(hit count: 4294967295)
Name: XXXX (Out)
20 permit 2:2:2::0/64 (hit count: 15)
To display the route map policy profiles assigned to the neighbor 1.1.1.1 IPv4
unicast family:
route-map
10 permit (hit count: 0)
match community 1:2
set community 2:3 med 456799 local-pref 123456
20 deny (hit count: 2)
match community 1000:2000
Name: XXXX (Out)
set community 1000:2000 local-pref 110
match as-path _150$ prefix-list AAAA community 10:20
set as2-path-prepend 100 100 community 30:40
To display the route map policy profiles assigned to the neighbor 10:10:10::10
IPv6 unicast family:
ETX-2i>config>router(1)>bgp(64515)>ipv6-unicast-af>neighbor(10:10:10::10)#
show route-map
match community 1:2
set community 2:3 med 456799 local-pref 123456
20 deny (hit count: 2)
Name: XXXX (Out)
set community 1000:2000 local-pref 110
match as-path _150$ prefix-list AAAA community 10:20
set as2-path-prepend 100 100 community 30:40

Table 8-38. BGP Route Map Field Descriptions
Field Description
Name Profile name
(In)/(Out) Policy direction: inbound or outbound
sequence Policy rule sequence number

number
type Policy rule type

Possible options are:
Deny
Permit
route map
rule
information
Viewing BGP Communities

You can view the received communities of all neighbors by using the command
show community. This command is available in the CLI contexts for IPv4 or IPv6,
at the BGP level: config>router(<number>)>bgp(<ASN>) #.
To display the IPv4 BGP communities received by all neighbors:

ETX-2i>config>router(1)>bgp(1)# show community ipv4
Network Community
===============================================================
Neighbor 2.2.2.2
0.0.0.0/0 65000:65000
111.222.111.220/30 20:20
Neighbor 33.33.33.33
0.0.0.0/0 1000:2000
111.222.111.220/30 100:100 200:200 300:300 400:400
To display the IPv6 BGP communities received by all neighbors:

ETX-2i>config>router(1)> bgp(1)# show community ipv6
Network Community
=============================================================================
Neighbor 2:2:2:2::2
::/0 > 11:11:11:11::1 65000:65000 1000:2000 3000:1000
11:11:11:11::/64 > :: 1000:2000
> abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 65200:65200
Neighbor 33:33:33:33::33
::/0 > 11:11:11:11::1 20:30
11:11:11:11::/64 > :: 400:400
> abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 65200:65200 4000:65500

Table 8-39. BGP Communities Field Descriptions
Field Description
Neighbor Neighbor IPv4 or IPv6 address

Community Decimal value, in format xxxx:yyyy

Possible values: 00000:0000065535:65535
Viewing BGP RIB

You can view the BGP RIB (Routing Information Base) for each neighbor by using
the command show rib. This command is available in the CLI contexts for IPv4 or
IPv6, at the BGP level: config>router(<number>)>bgp(<ASN>) #.
To display the IPv4 BGP RIB:

ETX-2i>config>router(1)>bgp(1)# show rib ipv4
* = Best Route
=============================================================================
Neighbor 2.2.2.2
* 0.0.0.0/0 > 172.17.171.1 1000 2000 3000 1000 100 2333
* 111.222.111.220/30 > 111.222.111.223 65200 65200 4000 800 65500
Neighbor 33.33.33.33
0.0.0.0/0 > 172.17.171.1 1000 2000 3000 1000 100 2333
111.222.111.220/30 > 111.222.111.223 65200 65200 4000 800 65500
To display the IPv6 BGP RIB:

ETX-2i>config>router(1)> bgp(1)# show rib ipv6
* = Best Route
=============================================================================
Neighbor 2:2:2:2::2
* ::/0 > 11:11:11:11::1 1000 2000 3000 1000 100
2333
11:11:11:11::/64 > :: 1000 2000 3000 1000 100
* abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd/126
Neighbor 33:33:33:33::33
::/0 > 11:11:11:11::1 1000 2000 3000 1000 100
2333
* 11:11:11:11::/64 > :: 1000 2000 3000 1000 100

Table 8-40. BGP RIB Field Descriptions
Field Description
Status (Best Marks with a * the Best Route, i.e. the route entry forwarded to the
Route) Routers RIB (Routing Information Base)

Next hop Network prefix and prefix length


Path
Viewing BGP Summary

You can view the summary of neighbor connections information by using the
command show summary. This command is available in the CLI contexts for IPv4
and IPv6, at the BGP level: config>router(<number>)>bgp(<ASN>) #.
IPv4 AF connections appear on top, followed by IPv6 AF connections.
To display the BGP summary:

ETX-2i>config>router(1)>bgp(1)# show summary
Neighbor AS Up/Down State
=============================================================================
11:11:11:11::205 209 never Active
3.3.3.2 3000 never Idle
172.17.171.205 209 12d 06:23:53 Established
2
172.17.171.218 209 12d 06:23:53 Active
abcd:abcd:abcd:abcd:abcd:abcd:abcd:abcd 65200 never Active
Table 8-41. BGP Summary Field Descriptions
Field Description
AS Remote AS number
Possible values: 0..35655 or 0..4294967295

Field Description
Up/Down Amount of time that the underlying TCP connection has been in
existence, i.e. how long this peer has been in the Established state.
Note: Up/Down time is set to zero when a new peer is configured or the
router is booted.
Possible values: 0 - 4294967295 seconds
When up/down time = 0, displays never.
Otherwise displays in format number of days, hours, minutes, and
seconds, for example: 12d 06:23:53
State BGP session state

Possible values are:
Idle
Connect
Active
Opensent
Openconfirm
Established
Testing BGP
After configuring BGP on a router in an existing BGP environment, you should test
that BGP is working properly.
To test BGP:
1. Wait a few seconds after configuration for BGP communications to take
place.
2. For each configured BGP neighbor:
a. Navigate to the BGP neighbor CLI context
(config>router(<number>)>bgp(<ASN>)>neighbor(<IP-address>)#).
b. Enter show neighbor-connection and check that communication has been
successfully established.
c. Navigate to the IPv4 unicast address family neighbor context
(config>router(<number>)>bgp(<ASN>)>ipv4-unicast-af>
neighbor(<IP-address>)#).
d. Enter show advertised-route and check that the correct destination
routes are being advertised.
e. Enter show received-route and check that BGP routes are being received.
3. If IPv6 has been configured for this neighbor:
a. Navigate to the IPv6 unicast address family neighbor context
(config>router(<number>)>bgp(<ASN>)>ipv6-unicast-af>
neighbor(<IP-address>)#).
b. Enter show advertised-route and check that the correct destination
routes are being advertised.
c. Enter show received-route and check that BGP routes are being received.

4. Navigate out of the BGP context, to the router CLI context.

5. Enter show routing-table and check that there are new routes marked as
originating in BGP.
8.13 Routing Protocol OSPF

OSPF (Open Shortest Path First) is a link-state interior-gateway protocol for
dynamic routing. The current implementation is OSPF v.2 (handles IPv4 only).
Standards and MIBs

The current implementation of OSPF adheres to the following standards:
Table 8-42. Standards and MIBs
Reference Title Unsupported Features
RFC 2328 OSPF Version 2 IPv6 (supported only in OSPF

v.3)
Multiple OSPF instances on a
router
Non-Broadcast Multiple Access
(NBMA) networks
Area-to-backbone virtual links
RFC 3101 The OSPF Not-So-Stubby Area

(NSSA) Option
RFC 3509 Alternative Implementations of

OSPF Area Border Routers
RFC 4750 OSPF Version 2 Management

Information Base
RFC 4940 IANA Considerations for OSPF
Note
OSPF does not support the BFD protocol.
Benefits
Dynamic routing protocols enable routing tables to automatically adapt to
changing networks. Link-state dynamic routing protocols such as OSPF quickly
adapt to network changes, enable intelligent decisions for best routing paths,
and are highly scalable.
All the routers in an Autonomous System (AS) must use the same Interior
Gateway Protocol (IGP).
8-190 Routing Protocol OSPF ETX-2i

OSPF functionality is explained in the following sections.
Show Me Demo
The following video gives an overview of OSPF.
Reader.
Dynamic Routing Protocols

Routers direct packets through their various interfaces according to their routing
tables, which specify an exit interface for each destination IP network. While
routing tables can include static, manually configured routes, an optimized
routing table requires knowledge of remote network topology and complex path
calculations. Dynamic routing protocols define how routers communicate network
topology with each other and how they accordingly calculate optimized network
paths and create their routing tables.
The internet is divided into Autonomous Systems (AS). An AS is usually the
network of an Internet Service Provider (ISP) or another large organization that
administers the AS-internal routing policy. Routing information inside each AS is
communicated and determined by an Interior Gateway Protocol (IGP) such as
OSPF; Routing information between ASes is communicated by the Border
Gateway Protocol (BGP).
Link-State Routing
Link-state routing is one of the two main types of IGPs, along with distance-
vector routing. OSPF is a link-state routing protocol.
In link-state protocols, each router creates and maintains a relatively full map of
network connectivity. The connectivity map, called the Link-State Database
(LSDB), includes information on which routers are connected to which other
routers, and each connections cost metric, which takes into account things like
round-trip time, throughput, and link availability. The maps completeness enables
the router to intelligently calculate the optimal path from itself to any network
destination, without having to rely on partial path calculations made in other
parts of the network. These optimal paths are used to dynamically create a
routing table.
To supply information for LSDBs, each router in the network notifies the network
about its own immediate neighboring routers and the costs of its connections
with them. Routers collect this link-state information and issue Link-State
Advertisements (LSAs) to their neighbors. Upon receiving an LSA, each router
updates its LSDB.
ETX-2i Routing Protocol OSPF 8-191

To inform their neighbors of their existence, routers send periodical HELLO

messages. When HELLO messages stop coming from a router, the connection
with that router is considered to have failed, and an LSA is generated to inform
the network of the lost connection.
OSPF Network Architecture

To reduce routing traffic and LSDB size, an AS that uses OSPF is divided into OSPF
areas. Each area is a group of contiguous networks which appears to OSPF
externally as a single unit with an invisible internal topology.
The AS must have a single designated backbone area so that each other area is
directly connected to the backbone. A router that connects an area to the
backbone (that is, it has an interface in the backbone and an interface in another
area) is called an Area Border Router (ABR). An ABR summarizes its areas
topology for external distribution, and maintains an LSDB for all areas to which it
is connected.
Figure 8-28. OSPF Network Architecture
AS-External Information
To enable routing to destinations outside the AS, designated Autonomous
System Boundary Routers (ASBRs) receive topology information about other ASs,
and distribute it to internal routers. ASBRs can be configured whether to
distribute topology from specified external sources (static routes or from BGP).
However, to reduce traffic, LSDB size, and routing table size, areas can be
configured so that only the area ABR is aware of the AS-external topology, and
the internal routers route traffic with destinations outside the AS through the
ABR. Two types of such areas can be configured:
Stub Area Cannot originate nor import AS-external topology. Internal

routers in this area route through the ABR.

Not So Stubby Cannot originate but can import AS-external topology

Area (NSSA)
An area which is neither stub nor NSSA is called a transit area. The backbone area
must always be a transit area.
Link-State Summarization
For AS-internal topology information, there is by default no difference between
the different types of non-backbone areas: ABRs of stub, NSSA and transit
(except for backbone) areas summarize AS-internal, area-external link-state
information for distribution to area-internal routers. However, a stub or NSSA
ABR can be optionally configured to suppress summary-LSAs, instead becoming
the areas single default gateway.
Designated Routers
To reduce network traffic, each network selects a Designated Router (DR) to
send LSAs outside of the network. A Backup Designated Router (BDR) is also
selected in case of DR failure. Routers are selected according to configurable
router priority indexes (lowest number indicates highest priority).
Authentication
OSPF can be configured to perform authentication, in which case OSPF
information is accepted only from password-authenticated routers.
Routing Preferences
static routes, OSPF AS-internal routes, and OSPF AS-external routes, the Routing
Table Manager (RTM) chooses among the sources according to configurable
source preference indices (lowest number indicates highest priority).
Explicit Range Aggregation

To reduce route lists, explicit ranges can be configured to replace included
subnets. Specifically, internal IP address ranges can be configured to be
summarized by a transit area ABR, or external IP address ranges can be
aggregated by an NSSA ABR. For a transit area ABR, an internal range can also be
configured to be hidden from other areas.
Maintained Information
OSPF maintains the following network information, all of which can be viewed
(see Viewing OSPF Status):
Neighbor list
Interface information
LSDB
LSA counters (see Viewing OSPF Statistics)

Parameters and Factory Defaults

OSPF parameters are configured at these levels:
Configuring OSPF at the Router Level: Parameters that determine OSPF
behavior for the whole router, for all interfaces
Configuring OSPF at the Area Level: Parameters that characterize an area, for
all interfaces that are configured as belonging in this area
Configuring OSPF at the Interface Level: Per-interface parameters
Router OSPF Parameters

The following parameters determine OSPF behavior for the whole router, for all
interfaces:
Table 8-43. Router OSPF Parameters
asbr Whether the router should be an ASBR (distribute AS- no asbr

external routes). See AS-External Information.
external-preference Preference index for OSPF AS-external routes. See 110

Routing Preferences.
internal-preference Preference index for OSPF AS-internal routes. See 10

Routing Preferences.
ospf Whether OSPF configuration is defined (but not no ospf

necessarily enabled) on this router
redistribute If an ASBR, whether to distribute routes from specified no redistribute

external sources (static or BGP) to the rest of the AS.
See AS-External Information.
router-id ID for router in OSPF communications, in format like IP --

address. Must be unique in AS (mandatory configuration)
shutdown Enable (no shutdown) / disable (shutdown) OSPF on the shutdown

router.
Area OSPF Parameters

The following parameters characterize an area (see OSPF Network Architecture),
for all interfaces that are configured as belonging in this area:
Table 8-44. Area OSPF Parameters
area-id ID for area in OSPF communications. Must be unique in AS. --

Format is like IP address. Can be same as IP address of a
network in the area. Backbone area must have ID 0.0.0.0
default-cost Cost metric of default route, for stub area ABR to advertise 1
into the area. See Link-State Routing.

nssa Whether area is NSSA, and whether the area ABR will no nssa, no-summary
provide area routers with summary LSAs (or just rely on its
default route). See AS-External Information and Link-State
Summarization.
range Internal IP address range(s) to be summarized or hidden by --

a transit area ABR, or external IP address range(s) to be
aggregated by an NSSA ABR. See Explicit Range
Aggregation.
shutdown Enable (no shutdown) / disable (shutdown) the area shutdown
stub Whether area is a stub area, and whether the area ABR will no stub, no-summary
provide area routers with summary LSAs (rather than just
rely on its default route). See AS-External Information and
Link-State Summarization.
Interface OSPF Parameters

The following parameters determine OSPF behavior per-interface:
Table 8-45. Interface OSPF Parameters
area ID of area to which interface belongs. See OSPF Network no area

Architecture.
authentication-key Password for OSPF authentication. See Authentication. --
authentication-type Whether OSPF information should be password- no authentication

authenticated. See Authentication.
dead-interval Time after which the connection with a silent neighbor is 40

considered failed. See Link-State Routing.
hello-interval Time, in seconds, between sending HELLO packets. See 10

Link-State Routing.
metric Explicit network cost of the interface for OSPF path 1

calculation. See Link-State Routing.
ospf Whether OSPF configuration is defined (but not necessarily no ospf

enabled) on this interface
passive Whether OSPF packets can (no passive) or cannot (passive) no passive
be sent through this interface
priority Priority index for becoming DR or BDR. See Designated 128

Routers.
retransmit-interval Time, in seconds, between retransmissions of 5

unacknowledged adjacency LSAs and of other network
advertisements. See Link-State Routing.
shutdown Enable (no shutdown) / disable (shutdown) OSPF on the shutdown

interface

transit-delay Time, in seconds, to be added to the LSAs age before 1

transmission. Should be the estimated time of LSA
transmission over the interface including propagation
delays
Configuring OSPF
OSPF is not configured by default on RAD routers. On a router that does not have
OSPF defined, once the router itself and its interfaces have been properly
configured, you can configure OSPF. To configure OSPF properly, you will need to
know your network OSPF design.
To configure OSPF on a fresh router:

1. Define OSPF on the router by entering the following commands in the device
CLI:
configure
router <number>
ospf
OSPF is defined on the router, and the CLI ospf context is provided.
2. In the router ospf context, define the router ID:
router-id <id>
where <id> is an ID for the router in OSPF communications, in IP address
format (<0-255>.<0-255>.<0-255>.<0-255>). The ID must be unique in the
AS. To simplify management, the ID can be the actual IP address of one of
the routers interfaces, or there may be some other organizational
convention.
3. Where network design requires that this router have non-default values (see
Parameters and Factory Defaults) for any router-level OSPF parameters,
configure them (see Configuring OSPF at the Router Level).
4. Still in the router ospf context, enable OSPF on the router by entering:
no shutdown
5. Configure each OSPF area (see OSPF Network Architecture) that the router
should be in according to network design:
a. In the router OSPF context (config>router(<router_number>)>ospf#),
define the are ID:
area <area-id>
where <area-id> is an ID for the area in OSPF communications, in IP
address format (<0-255>.<0-255>.<0-255>.<0-255>). The ID must be
unique in the AS. To simplify management, the ID can be the actual IP
address of a network in the area, or there may be some other
organizational convention. The backbone area ID must be 0.0.0.0 .
The area is defined, and the CLI area context is provided.

b. In the area context (config>router(<router_number>)>ospf>area(<area-

id>)#):
If according to network design the area should be a stub area, enter:
stub
If according to network design the area should be an NSSA area,
enter:
nssa
c. Where network design requires that this router have non-default values
(see Parameters and Factory Defaults) for any area-level OSPF
parameters, configure them (see Configuring OSPF at the Area Level).
d. Still in the area context, enable the area by entering:
no shutdown
An enabled area means that OSPF interfaces connected to it can be
enabled, and that the areas type (stub / NSSA / transit) cannot be
changed.
e. Exit the area context.
6. Exit the router OSPF context to return to the router CLI context.
7. Configure OSPF on each interface:
a. Go into the interface CLI context (config>router(<router_number>)>
interface(<interface_number>)#), and define OSPF on the interface:
ospf
OSPF is defined on the interface, and the CLI interface ospf context is
provided.
b. In the interface OSPF context, set the area with which to associate the
interface:
area <area-id>
where <area-id> is the areas ID, according to network design.
c. Where network design requires that this interface have non-default
values (see Parameters and Factory Defaults) for any interface-level OSPF
parameters, configure them (see Configuring OSPF at the Interface Level).
d. Still in the interface OSPF context, activate OSPF on the interface by
entering:
no shutdown
e. Exit the interface OSPF context, and exit the interface context.
Configuring OSPF at the Router Level

The following commands are available in the CLI router OSPF context:
config>router(<router_number>)>ospf# . The exception to this is the ospf
command itself, which is performed in the router context:
config>router(<router_number>)# .

Table 8-46. Router-Level Configuration Tasks
Define OSPF on the [no] ospf After defining OSPF on the router, OSPF still
router (if not yet needs to be enabled (after setting router-id) with
defined), and provide no shutdown.
the router CLI ospf no ospf removes OSPF from the router (if no
context areas are defined).
Define ID for the router router-id <id> <id> is in IP address format: <0-255>.<0-
in OSPF 255>.<0-255>.<0-255> . The ID must be unique
communications in the AS. To simplify management, the ID can be
the actual IP address of one of the routers
interfaces, or there may be some other
organizational convention.
Enable / disable OSPF [no] shutdown To disable: shutdown . To enable: no shutdown

on the router
Define / remove OSPF [no] area <area-id> <area-id> is in IP address format: <0-255>.<0-
area, with an ID for the 255>.<0-255>.<0-255>. The ID must be unique
area in OSPF in the AS. To simplify management, the ID can be
communications the actual IP address of a network in the area, or
there may be some other organizational
convention. The backbone area ID must be
0.0.0.0 .
no area <area-id> removes the area from router
OSPF configuration (if the area is not associated
with any interfaces).
To further configure the area, see Configuring
OSPF at the Area Level
Make router an ASBR [no] asbr OSPF must be disabled to run this command.
(=distribute AS-external See AS-External Information.
routes)
Set ASBR to distribute [no] redistribute {static | bgp} To disable distribution: no redistribute .
routes from specified See AS-External Information.
external sources (static
or BGP) to the rest of
the AS, or disable
distribution
Set preference index external-preference <priority> <priority> should be an integer in range 0-255.
for OSPF AS-external See Routing Preferences.
routes
Set preference index internal-preference <priority> <priority> should be an integer in range 0-255.
for OSPF AS-internal See Routing Preferences.
routes
View counters of LSAs show statistics See Viewing OSPF Statistics.
View Link-State show database See Viewing OSPF Status.

Database (LSDB)

View OSPF interface show interface-table

information
View OSPF neighbors show neighbor-table
Configuring OSPF at the Area Level

The following commands are available in the CLI OSPF area context:
config>router(<router_number>)>ospf>area(<area-id>)# . Note that the area
command, which is performed in the router OSPF context:
config>router(<router_number>)>ospf#, appears under Configuring OSPF at the
Router Level.
Table 8-47. Area-Level Configuration Tasks
Make area a stub area, [no] stub [summary | All routers in a stub area must be configured as
or change a stub area no-summary] such. See AS-External Information.
back to a transit area This command is effective regardless of the areas
current type (transit or NSSA).
For the area ABR to just rely on its default route
rather than provide area routers with summary
LSAs, use stub no-summary . For it to go back to
providing summary LSAs, use stub summary. See
To change a stub area back to a transit area, use
no stub
Make area an NSSA [no] nssa [summary | All routers in an NSSA area must be configured as
area, or change an no-summary] such. See AS-External Information.
NSSA area back to a This command is effective regardless of the areas
transit area current type (transit or stub).
For the area ABR to just rely on its default route
rather than provide area routers with summary
LSAs, use nssa no-summary . For it to go back to
providing summary LSAs, use nssa summary. See
To change an NSSA area back to a transit area, use
no nssa
Set cost metric of default-cost <metric> Use only on stub area ABR.
default route, for stub Possible values: 116777215 (24-bit)
area ABR to advertise
See Link-State Routing.
into the area

Set internal IP address [no] range <ip-address>/ To set internal transit area summarization, on the
range(s) to be <mask-length> [advertise | transit ABR use: range <ip-address>/<mask-
summarized or hidden not-advertise] [nssa] length> advertise .
by a transit area ABR, To set internal transit area hiding, on the transit
or external IP address ABR use: range <ip-address>/<mask-length> not-
range(s) to be advertise .
aggregated by an NSSA
To set external NSSA aggregation, on the NSSA
ABR
ABR use range <ip-address>/<mask-length>
advertise nssa .
<ip-address> should represent an IP range, in IP
address format. <mask-length> should be an
integer in range 132, representing the number of
first bits in <ip-address> that are the network
mask.
To delete a configured range, use: no range <ip-
address>/<mask-length>.
See Explicit Range Aggregation.
Enable / disable the [no] shutdown To disable: shutdown . To enable: no shutdown

area
Configuring OSPF at the Interface Level

The following commands are available in the CLI interface OSPF context:
config>router(<router_number>)>interface(<interface_number>)>ospf# . The
exception to this is the interface ospf command, which is performed in the
interface OSPF context: config>router(<router_number>)>interface(<
interface_number>)# .
Table 8-48. Interface-Level Configuration Tasks
Define OSPF on the ospf After defining OSPF on the interface, OSPF
interface (if not yet still needs to be enabled (after associating
defined), and provide the the interface with an area) with no shutdown.
interface CLI ospf context no ospf removes OSPF from the interface (if
no areas are defined)
Associate interface with an [no] area <area-id> Specify the area with its <area-id>.
area To disassociate the interface from any area,
use no area <area-id>.
Enable / disable OSPF on [no] shutdown To disable: shutdown . To enable: no

the interface shutdown
Set the time between hello-interval <seconds> <seconds> should be in range 165535.
sending HELLO packets See Link-State Routing.

Set the time after which dead-interval <seconds> Possible values: 12147483647.
the connection with a See Link-State Routing.
silent neighbor is
considered failed
Set the priority index for priority <priority> Possible values: 0255.
becoming DR or BDR See Designated Routers
Set the time to be added transit-delay <seconds> The estimated time of LSA transmission over
to the LSAs age before the interface including propagation delays
transmission Possible values: 03600
Set the time between retransmit-interval <seconds> Possible values: 03600.

retransmissions of See Link-State Routing.
unacknowledged adjacency
LSAs and of other network
advertisements
Prevent OSPF packets from [no] passive A passive interface is still advertised as an
being sent through the OSPF interface, but doesnt itself run the
interface OSPF protocol.
To re-enable sending OSPF packets, use no
passive
Set password [no] authentication-type To set authentication, use: authentication-

authentication for OSPF [simple-password] type password . To disable authentication,
communications use: no authentication.
See Authentication.
Set password for OSPF authentication-key <authentication-key> can be any combination

authentication, if enabled <authentication-key> [hash] of up to 8 ASCII characters. Use the hash
option to specify that the provided key should
be encrypted, in which case the key can be up
to 22 characters.
See Authentication.
Explicitly set the network metric <number> Possible values: 165535

cost of the interface for See Link-State Routing.
OSPF path calculation
Configuration Example
In this example, a router needs to be configured for OSPF. According to network
design, this router is a stub area ABR with two interfaces, one in the backbone
and one in a stub area. Authentication is used in both areas, but each area uses a
different password.
The relevant part of the network design is:

Router ID Interface Area Password
10.10.1.1 Interface 1 0.0.0.0 12345672
Interface 2 10.10.0.0 abcdefgh
The actual configuration process for this example is:

configure
router 1
remark Configure OSPF on router
ospf
router-id 10.10.1.1
no shutdown
remark Configure OSPF Areas
area 0.0.0.0
no shutdown
exit
area 10.10.0.0
stub no-summary
no shutdown
exit
exit
remark Configure OSPF with authentication on interfaces
interface 1
ospf
area 0.0.0.0
authentication-type simple-password
authentication-key 12345678
no shutdown
exit
exit
interface 2
ospf
area 10.10.0.0
authentication-type simple-password
authentication-key abcdefgh
no shutdown
exit
exit
Table 8-50 lists the messages generated by the device when a configuration error
is detected.
Cannot be modified; OSPF You tried to associate an Enter shutdown and try again.
interface is administratively interface with an area, but the
enabled interface is OSPF-enabled

Cannot create OSPF interface; IP You tried to run ospf in the Set a fixed IP address for the
address wasnt configured interface context, but the interface.
interface itself has no fixed IP
address (it is possibly DHCP)
Cannot create OSPF interface; You tried to run ospf in the Remove interface IP addresses to
more than one IP address is interface context, but the leave only one, and try again.
configured interface itself has multiple IPv4
addresses
Cannot delete area; There is an You tried to run no area (router Go to the relevant interface OSPF
OSPF interface associated with OSPF context) on an area context and enter no area <area-id>.
the Area associated with an interface
Cannot delete ospf; ospf area or You tried to run no ospf (router Remove OSPF from all interfaces,
OSPF interface exist context) with existing areas or delete all areas, and try again.
OSPF interfaces
cannot enable OSPF interface; You tried to enable OSPF on an Set an area for the interface and try
area-id is not defined interface without an associated again.
area
Cannot enable OSPF; router-id is You tried to run no shutdown Set router-id and try again.
not configured (router OSPF context) with no
OSPF router ID
Cannot enable redistribute; You tried to run the redistribute If by network design this router
ASBR disabled command on a non-ASBR router should be an ASBR, enter asbr and
try again.
Cannot execute, license required You tried to run ospf (router Contact your RAD sales
context) without an OSPF representative to obtain a license.
license
Cannot modify area parameter; You tried to make an enabled Enter shutdown and try again.
area is administratively enable area into a stub or NSSA
Cannot modify; OSPF is enabled You tried to change router-id or Enter shutdown and try again.
asbr with OSPF enabled
Cannot set area as nssa; area-id You tried to make the backbone If this is not the backbone, change
0.0.0.0 cannot be nssa a stub or NSSA the area ID and try again.
Cannot set metric; Area is a You tried to run the default-cost If this area should be a stub area,
Transit command on a transit area enter stub and try again.
Cannot set ranges for external You tried to run the range If this area shouldnt be an NSSA,
routes for non NSSA command with the nssa option, enter no nssa and try again.
on a non-NSSA area
OSPF entity shall be initiated You tried to run ospf in the Exit to the router context and enter
before interfaces configuration interface context, but OSPF ospf. Then try again.
hasnt been defined on the
router

Viewing OSPF Status

You can view the current configuration (see Viewing the Current Configuration),
and you can also view several types of dynamic and traffic-based OSPF
information (see sections below). This information can be used for testing (see
Testing OSPF) and debugging.
Viewing the Current Configuration

To view the current configuration, use the standard RAD commands: info (to view
only non-default configuration) and info detail (to include default configuration).
You can view this info at any of the following configuration levels:
Level Context Prompt
Router config>router(<router_number>)>ospf#
Area config>router(<router_number>)>ospf>area(<area-id>)#
Interface config>router(<router_number>)>interface(<interface_number>)>ospf#
For example:
rad_os_p# configure
rad_os_p>config# router 1
rad_os_p>config>router(1)# ospf
rad_os_p>config>router(1)>ospf# info detail
router-id 1.2.3.4
no asbr
no graceful-restart
restart-interval 120
strict-lsa-checking
shutdown
echo "OSPF AREA Configuration"
# OSPF AREA Configuration
area 0.0.0.0
no nssa
no stub
no shutdown
exit
rad_os_p>config>router(1)>ospf#
Viewing the Link-State Database

You can view the current Link-State Database by using the show database
command. This command is available in the CLI router OSPF context:
(config>router(<router_number>)>ospf#), and can be used for testing (see
For example:
Area ID Type LS ID Router ID Sequence Age Checksum
--------------------------------------------------------------------------------
100.100.100.100 1 000.000.010.010 000.000.010.010 0x80000096 938 0x609b
100.100.100.100 1 050.050.050.020 050.050.050.020 0x80000006 839 0x49d4

000.000.000.000 2 020.020.020.020 020.020.020.030 0x80000008 946 0x3c3a

000.000.000.000 3 050.050.050.000 000.000.010.010 0x8000000d 764 0xcbd9
000.000.000.000 4 000.000.010.010 050.050.050.020 0x80000002 840 0x83f7
Table 8-50. LSDB Field Descriptions
Field Description
Area ID <area-id> of an OSPF area
Type One of the following LSA types:

1 Router-LSA: Describes collected states of router's interfaces
2 Network-LSA: Describes routers attached to network
3 Network summary-LSA: Describes inter-area routes to networks,

summarized by ABR
4 ASBR summary-LSA: Describes inter-area routes to ASBRs, summarized by
ABR
5 AS-external-LSA: Originated by ASBR, describes routes to AS-
external destinations or a default route for the AS
7 NSSA-external-LSA: Describes external route information within an
NSSA
LS ID Router ID or IP address (depending on Type) of domain described by the

LSA
Router ID ID of originating router
Sequence Signed 32-bit integer, incremented each time the router originates a new
instance of the LSA. Used to detect old and duplicate LSAs
Age LSA age in seconds
Checksum Checksum of complete LSA contents except for Age field
Viewing OSPF Interface States

You can view current interface states by using the show interface-table
For example:
IP Address Area ID Type Priority DR BDR State
-------------------------------------------------------------------------------------
000.000.000.000 000.000.000.001 P-T-P 0001
000.000.000.000 000.000.000.000 Down
192.168.001.001 000.000.000.003 BRDCST 0001
192.168.001.007 192.168.001.002 Up
Table 8-51. Interface Field Descriptions
Field Description
IP Address Interface IP address

Field Description
Area ID ID of area with which the interface is associated
Type Broadcast or point-to-point
Priority Priority index for becoming DR or BDR
DR Designated Router in this network
BDR Backup Designated Router in this network
State UP if all of the following are true: OSPF is enabled (no

shutdown), the IP interfaces operational status is UP, and
the OSPF interface is enabled (no shutdown)
Viewing OSPF Neighbors

You can view the current OSPF neighbors by using the show neighbor-table
For example:
Neighbor Neighbor ID Priority State Interface Port
----------------------------------------------------------------------------
192.168.001.003 192.168.001.009 0001 Full 192.168.001.002 Ethernet 0
192.168.001.007 000.000.000.004 0004 Full 192.168.001.002 Ethernet 0
10.10.001.001 000.000.000.005 0005 Full 10.10.001.002 Ethernet 1
Table 8-52. Neighbor Field Descriptions
Field Description
Neighbor IP address used by this neighbor as its source address
Neighbor ID The neighbors OSPF router-id
Priority The neighbors priority index for becoming DR or BDR
State The state of the connection with this neighbor. One of:
Down
Attempt
Init
Twoway
Exchangestart
Exchange
Loading
Full
Interface IP address of the neighbors interface with which a connection is

established
Port Name of the neighbors interface with which a connection is established

Viewing OSPF Statistics

You can view LSA counters by using the show statistics command. This command
is available in the CLI router OSPF context:
(config>router(<router_number>)>ospf#).
For example:
Count Checksum
--------------------------------------
External LSA 50 0x3245
AS LSA 1059 0x7843
New LSAs Originated 45 -
New LSAs Received 1024 -
Table 8-53. Statistics Field Descriptions
Field Description
Count The number of LSAs of this type
Checksum 32-bit sum of the checksums of the LSAs of this type. Can be used to
check if an LSDB has changed or to compare LSDBs.
Testing OSPF
After configuring OSPF on a router in an existing OSPF environment, you should
test that OSPF is working properly.
To test OSPF:
1. Wait a few seconds after configuration for OSPF communications to take
place.
2. Navigate to the CLI router OSPF context (config>router(<router_number>)>
ospf#).
3. Enter show interface-table and check that a DR and a BDR have been
successfully elected.
4. Enter show neighbor-table and check that connections have been established
with all neighbors.
5. Enter show routing-table and check that expected routes have been learned
from OSPF neighbors.
6. Exit the OSPF context, to the router CLI context.
7. Enter show routing-table and check that there are new routes marked as
originating in OSPF.

8.14 Routing Protocol VRRP

VRRP (Virtual Router Redundancy Protocol) enables a group of routers to act as a
virtual router with a virtual IP address that can be configured as the default
gateway for access devices in a LAN.
Standards and MIBs

The VRRP feature complies with the following standards.
Table 8-54. Standards
Standard Title
RFC 1071 Computing the Internet Checksum
RFC 2460 Internet Protocol, Version 6 (IPv6) Specification
RFC 3768 Virtual Router Redundancy Protocol (VRRP)
RFC 5798 Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6
RFC 6527 Definitions of Managed Objects for the Virtual Router Redundancy Protocol
Version 3 (VRRPv3)
ETX-2i can support either of the following VRRP versions at any time:
VRRPv2 (RFC 3768) supports only IPv4
VRRPv3 (RFC 5798) supports IPv4 and IPv6
The two versions cannot interwork together.
Benefits
A static default gateway router is a potential single point of failure, which is
eliminated by VRRP; it increases the availability and reliability of routing paths
without the need for dynamic routing or router discovery protocols on every
access device.
VRRP Group
A VRRP group is defined as a group of routers that share one or more virtual IP
addresses. If a routers physical IP address matches a virtual IP address, it is
referred to as the address owner. The routers in the group are assigned priorities
ranging from 1255, with 255 being the highest priority, however only priorities
1254 are configurable. Priority 255 is automatically assigned to the address
owner regardless of the configured priority. Up to 20 VRRP groups are supported
per device.
8-208 Routing Protocol VRRP ETX-2i

Master Router
At any time, one of the routers is the master (active) and the others are backups.
The router with the highest priority is selected as the master, therefore the
address owner is the master unless it has failed. If more than one router has the
highest priority, the one with the highest primary IP address is selected as
master. The primary IP address is one of the router interfaces real (IPv4) or
link-local (IPv6) IP addresses. It is used as the source address in VRRP
advertisements
The master router forwards upstream traffic packets destined for the virtual IP
address(es), and sends periodic advertisements to the backup routers at a
user-configurable interval. If a backup router does not receive an advertisement
for a set period, the backup router with the next highest priority takes over as
master.
Preemption
If preemption is enabled, then when a new router is added to a VRRP group and
its priority is higher than any of the routers in the group, it preempts the master
role. When a router with priority 255 (address owner) is added to a VRRP group
or becomes active, it preempts all lower-priority routers, even if preemption is
disabled. If no router has priority 255 and preemption is disabled, then no
preemption occurs.
Fault Propagation
If the VRRP master routers uplink toward the network fails, it does not affect the
VRRP state if VRRP is running on an Ethernet port connected to the user network;
however, the master might not be able to forward packets, or might delay the
packet forwarding by using an alternative route.
To solve this, the status of an interface can be used as a fault propagation
trigger, with the configured action of lowering the VRRP priority, in order to cause
a backup router to become the master. This VRRP redundancy is supported within
50 ms from the start of switchover. When the interface recovers, the original
priority is restored.
Note In order for fault propagation to interact properly with a VRRP group, preemption
must be enabled on all VRFs belonging to that group, and all the VRFs must not
be address owners.
Load Balancing
The VRRP backup virtual routers do not forward traffic incoming from the LAN
unless they become the master router. It would be advantageous to have multiple
routers forwarding the traffic instead of one being the active master, and the
rest idle backups. To achieve this, multiple VRRP groups (up to , 2) can be
configured for a router interface, with each router acting as the master of a
different virtual IP address.
Each virtual address can then be configured as default gateway for some of the
devices on the LAN, and each router handles the traffic of the devices for which
it is the default gateway. If a router fails, one of the other routers transitions to
master, and handles the failed routers traffic.
ETX-2i Routing Protocol VRRP 8-209

Factory Defaults
The default device VRRP version is 2.
By default, no VRRP groups exist. When a VRRP group is created, its default
configuration is the following:
description virtual router <ip-ver> group <id> <ip-ver> is either IPv4 or IPv6.
<id> is the group VRID.
preempt Preempt Preemption is enabled by default.
priority 100
shutdown shutdown VRRP is disabled by default; at least one

virtual IP address must be associated with
the group before the group can be enabled.
timer-advertise VRRP v2: 1 second

VRRP v3: 100 centiseconds
Configuring VRRP
VRRP is configured at the following levels:
System> router Configure device VRRP version.
Router interface Configure VRRP group parameters.
Configuring VRRP Version

You can configure the VRRP version at the system > router level.
To configure the device VRRP version:

At the config>system>router# prompt, enter the following command to
specify VRRP version 2 or 3:
vrrp-version {2 | 3}
Note See Viewing VRRP Summary for details on displaying VRRP group summary
information at various levels.
Configuring VRRP Group Parameters

You configure VRRP group parameters at the router interface level.
Notes A VRRP group cannot be associated with a router interface for which any of the
following is true:
DHCP is enabled for the router interface.
The router interface is bound to a PPP port.
The router interface is a loopback interface.

To configure VRRP group parameters:

1. At the config>router(<number>)>interface(<interface-num>)# prompt, enter
the following, specifying the VRRP group ID (1255) and IP version:
vrrp <vrid> [{ipv4 | ipv6}]
One of the following prompts is displayed, depending on the IP version
entered:
config>router(<number>)>interface(<interface-num>)>vrrp(<vrid>,ipv4)#
Note The commands ip and no shutdown are mandatory for VRRP group configuration.
The other commands are optional; if they are not specified, then default values
are used (see Factory Defaults).
Configuring VRRP group description <string> Type no description to use an

description empty (NULL) string.
Associating a virtual IP address ip <ip-address> Type no ip <ip-address> to

with the VRRP group delete the association with the
IP address.
The IP address must be in the
correct form for the configured
IP version.
Enabling preemption Preempt Type no preempt to disable

preemption.
Configuring VRRP priority priority <number> 1254

Configuring interval for VRRP timer-advertise <number> If centiseconds is not entered,

master router advertisements [centiseconds] the range for <number> is 140
seconds.
If centiseconds is entered, the
range for <number> is 104000
centiseconds.
If the centiseconds parameter
is entered when ETX-2i is
working in VRRPv2, then the
entered value is stored, but if it
is not a multiple of 100, then
ETX-2i uses a value that is
rounded up to the next multiple
of 100, e.g. for timer-advertise
201 centiseconds, ETX-2i uses
3 seconds for the timer.
When the configuration is
displayed via the info
command, the centiseconds
keyword is displayed only if the
device is working in VRRPv3 and
the configured interval value in
centiseconds is not a multiple
of 100.
Viewing VRRP status show status
Administratively enabling or no shutdown Type shutdown to

disabling VRRP for router administratively disable VRRP.
interface VRRP can be enabled only if at
least one virtual IP address has
been associated.
Viewing VRRP Status

You can view VRRP status by using the show status command. This command is
available in one of the following CLI contexts, depending on the IP version of the
VRRP group:
For example:
ETX-2i# configure router(1)>interface(7)>vrrp(1,ipv4)# show status
Router/Interface : 1/7
Physical Port : Ethernet 1/2
VRRP Group : 1 (IPv4)
Administrative Status : Enabled
Operational Status : Master
Uptime (seconds) : 1111
Primary IP Address : 10.20.0.01/24

Protected IP Address : 10.20.0.01/24

: 10.20.0.10/24
Virtual MAC Address : 00:00:5e:00:01:01
Advertisement Interval (seconds) : 1
Preemption : Enabled
Priority : 254
Reduced By Fault Propagation to: 253
From Interface : Router Interface 1/2
Table 8-55. VRRP Status Parameters
Field Description
Router/Interface Router and interface where the VRRP group is configured
Physical Port Physical interface that is bound to the router interface
VRRP Group VRRP group ID
Administrative Status VRRP group administrative status Disabled or Enabled
Operational Status VRRP role:

Backup Router interface is acting as backup.
Master Router interface is acting as master.
Init Router interface VRRP group parameters are being
initialized.
Lower Layer Down The interface with which the group is
associated is non-operational.
Uptime (seconds) Time since VRRP role changed from Init to Backup or Master
Primary IP Address Primary IP address and mask of the VRRP group
Protected IP Address One or more virtual IP address(es) protected by the VRRP group; one
output line is displayed for each protected IP address.
Virtual MAC Address Virtual MAC address of the VRRP group
Advertisement Interval Interval between VRRP advertisements (if the router is acting as
(seconds) master)
Preemption Preemption state Disabled or Enabled
Priority Router VRRP priority (0255)
Reduced By Fault Router VRRP actual priority, after being reduced by fault propagation
Propagation to if applicable
From Interface Faulted interface that triggered priority decrease
Viewing VRRP Summary

You can view a VRRP group summary by using the show vrrp-summary command
for router, or show summary-vrrp command for router interface. This command is
available in the following CLI contexts:
config>system>router displays information for all VRRP groups in the device

config>router(<number>) displays information for all VRRP groups

configured for any router interfaces belonging to the router
config>router(<number>)>interface displays information for all VRRP
groups configured for the router interface
For example:
ETX-2i# configure router(1)>interface(1)# show summary-vrrp
Rtr If Phys If Group Pri Own Pre State Primary Address
1/1 Ethernet 1/2 111(IPv4) 100 Yes Ena Master 10.10.10.10
1/1 Ethernet 1/2 222(IPv6) 200 -- Dis Backup FE80::1234
Table 8-56. VRRP Group Summary Parameters
Field Description
Rtr Router and interface where the VRRP group is configured
Phys If Physical interface that is bound to the router interface
Group VRRP group ID
Pri Router VRRP priority (0255)
Own Indicates if VRRP group is address owner: Yes or --
Pre Preemption state Dis or Ena
State VRRP role:

Backup Router interface is acting as backup.
Master Router interface is acting as master.
Init Router interface VRRP group parameters are being
initialized.
LLD The router interface where the VRRP group is configured, is
not operational.
Primary Address Primary IP address of the VRRP group
Too many VRRP groups on this You tried to create a VRRP Delete one of the VRRP groups from
interface group for a router interface the interface.
for which the maximum
number of groups already
exists.
VRRP and DHCP not allowed on You tried to create a VRRP Disable DHCP for the interface.
the same interface group for a router interface
for which DHCP is enabled.

VRRP cannot be configured on You tried to create a VRRP Remove the PPP port association from
PPP group for a router interface the interface.
that is bound to a PPP port.
VRRP cannot be configured on a You tried to create a VRRP Create the VRRP group for a different
loopback router interface group for a router interface router interface.
that is a loopback router
interface.
Too many addresses associated You tried to associate an IP Delete one of the associated addresses
with VRRP group address with a VRRP group for before associating a new IP address
which the maximum number of with the group.
supported addresses is already
associated.
Incorrect IP version You tried to associate an IPv4 Associate an IPv4 address with an IPv4
address with an IPv6 group or group, or an IPv6 address with an IPv6
an IPv6 address with an IPv4 group.
group.
Active VRRP group must have You tried to dissociate the last Associate a virtual IP address with the
virtual IP IP address from an enabled VRRP group or disable the group.
VRRP group.
Cannot activate VRRP group You tried to administratively Associate a virtual IP address with the
without virtual IP address enable a VRRP group that does VRRP group.
not have at least one
associated virtual IP address.
VRRP priority preemption must You tried to disable Remove the fault propagation
be enabled for fault propagation preemption on a VRRP group configuration.
that is defined in fault
propagation as a to-element.
Priority decrement fault You tried to configure one of Either configure the to-element with a
propagation banned on VRRP the following: different IP address that is not a virtual
address owner Fault propagation IP address, or use a virtual address that
to-element virtual IP is not a real address of the to-element.
address as the to-element
IP address
Fault propagation
to-element IP address as
the to-element virtual IP
address.


Chapter 9
Timing and
Synchronization
This chapter describes timing and synchronization features:
1588v2 Timing
Clock Selection
Date and Time
Daylight Saving Time
9.1 1588v2 Timing

ETX2i supports IEEE 1588v2 Precision Time Protocol for distribution of
synchronization signals over packet-switched networks.
Applicable Products
This feature is applicable to ETX2i, ETX-2i-B, and ETX-2i-10G with PTP options,
with the following conditions:
The following 1588v2 entities are supported by ETX2i and ETX-2i-10G:
Standalone slave clock
Boundary clock
For G.8275.1, the PTP port limits are as follows:
PTP ports with master role per device: Up to 7
PTP ports with slave role per device: Up to 2
<slot> is relevant for modular ports.
Standards
IEEE 1588 Precision Time Protocol
ITU-T G.8265.1 Precision Time Protocol Telecom Profile
ITU-T G.8275.1 Precision Time Protocol Telecom Profile
ITU-T G.8273.2 Telecom Boundary Clock (T-BC) Specification
ETX2i 1588v2 Timing 9-1

Chapter 9 Timing and Synchronization Installation and Operation Manual
Benefits
The Precision Time Protocol (PTP), defined in the IEEE 1588 standard, is a
high-precision time protocol for synchronization of clocks over a PSN. PTP is
beneficial for applications that recover or distribute timing information.
PTP Protocols
G.8265.1 is an end-to-end protocol based on IP packets. The synchronization
message rate and announce rate are negotiated between the slave and master.
The G.8265.1 protocol is used to obtain frequency and time.
G.8275.1 is a point-to-point protocol based on Layer-2 multicast messages. There
is no signaling phase; the message rate is always 16 PPS and the announce rate is
8 PPS. The G.8275.1 protocol is used to obtain time rather than frequency. It
obtains frequency from SyncE to get a more accurate time. The reference time is
taken from the CSM source if it is PRC; otherwise from the 1588v2 frequency.
1588v2 Entities
ETX2i supports the following 1588v2 entities:
Standalone slave Recovers the clock signal from master clocks
Boundary clock Transfers time of day (ToD) and frequency from a remote
master clock to one or more slave clocks. The boundary
clock is implemented as a back-to-back master and slave
clock.
Note
Only IPv4 addresses are supported in the timing/synchronization messaging.
PTP Port
When a 1588v2 entity acts according to G.8275.1, you need to configure a PTP
port entity for each clock entity. The PTP port has a provisioned state that you
configure, as well as an actual state. The provisioned state can be one of the
following:
Slave Acts as the time source of ETX2i
Master Provides the distribution path for the device time
The actual state can be one of the following:

Slave (one per device)
Master
Passive neither master nor slave
ETX2i uses the best master clock algorithm (BMCA) to select the best clock from
the ports that are provisioned as slave. The selection is done according to quality
level received in announce messages and port priority.
9-2 1588v2 Timing ETX2i

Installation and Operation Manual Chapter 9 Timing and Synchronization
The actual state of the provisioned slave port that is selected as the best clock is
set to slave. The actual state of the provisioned slave ports that are not selected is
set to passive.
Slave Clock
The standalone slave clock complies with G.8265.1 or G.8275.1. The slave clock
complies with the standard G.8265.1 Telecom Profile 1 (E2E), as well as
Symmetricom Telecom-2008, when working according to G.8265.1.
G.8265.1
The G.8265.1 slave clock can work in one-way mode, where it receives only
frequency from up to two IEEE 1588 master clocks, or in two-way mode (full
synchronization), where it receives frequency and time. When the master clock
grants signal transmission it notifies the slave clock of the master clock quality
level and source port identification, then periodically transmits synchronization
signals.
The slave clock works in the following recovery modes:
Time (also The slave uses its regenerated frequency to reconstruct

referred to as the remote clock, or uses a high-quality clock (PRC/PRS)
Hybrid) from the clock domain. Therefore, the time accuracy
depends on the quality of the reconstructed frequency;
noise in the frequency generation impacts the time
accuracy.
Frequency The slave reconstructs the remote clock using Sync

messages and delay request/response sent from master to
slave. Time-related status and alarms, as well as time
indication over the ToD interface, are not supported.
Frequency and The slave provides frequency information and time

Time information as described above. As the slave uses the
frequency for time recovery, a high-quality reference clock
usually improves the time recovery, except in the case of
network asymmetry.
1588v2 traffic is transmitted only via Ethernet port 0/1.
G.8275.1
The G.8275.1 slave clock receives frequency from one or more IEEE 1588 master
clocks that periodically transmit synchronization signals.
The slave clock works in time (also referred to as hybrid) recovery mode. The slave
uses both Sync and Delay messages to reconstruct the remote clock, and takes
the reference frequency is taken from the clock domain (same the G.8265.1 slave
in hybrid mode).
G.8273.2 clock specification supports G.8275.1.
Boundary Clock
The boundary clock is defined in ETX2i as a back-to-back master and slave clock
sharing the same IP address and PTP domain. The slave can be a G.8265.1 or

G.8275.1 entity, and the master can be a G.8265.1 or G.8275.1 entity, or it can be
a dual mode master that supports both G.8265.1 and G.8275.1.
The boundary clock performs the following tasks:
The local slave recovers reference ToD and frequency from a remote master.
The local master uses the local slave recovered ToD as its reference ToD.
The local master uses the local slave recovered frequency as its reference
frequency.
Forwarding
G.8265.1
You need to configure the following for the G.8265.1 clock entities to function
correctly:
Corresponding SVI
Corresponding flows
Corresponding router interface. For the G.8265.1 boundary clock, the SVI
corresponding to the router interface must be connected via flow to a bridge
port.
In order to communicate with the remote master of the G.8265.1 boundary clock,
a peer must be defined with the remote master IP address; additionally, if the
remote master is not in the same subnet as ETX2i, a static route must be
configured to define how to reach the remote master.
G.8275.1
1588v2 traffic for PTP ports is transmitted and received by the 1588 entity
to/from an Ethernet port. You need to configure the following for the G.8275.1
clock entities to function correctly:
Corresponding SVI
Corresponding PTP port
Corresponding flows. The traffic from the Ethernet port to the SVI port should
be classified as untagged. The traffic from the SVI port to the Ethernet port
should be classified to match all packets.
Dual Mode Master

You configure a dual mode master, also called a Distributed PTP Grandmaster
(DISTRIBUTED GM), by configuring a G.8265.1 master entity and a G.8275.1
master entity:
Any configuration change to the dual mode master (Grandmaster) requires
that you first remove and then add the G.8265.1 master entity.
The two masters must be configured with different PTP clock domains.
Each master can support different 1588 message rates. A G.8265.1 master
supports message rates per slave negotiation, and a G.8275.1 master supports
the standard sync rate of 16 PPS.

Factory Defaults
By default, there is no configured master or slave clock.
Configuring PTP Ports

You need to configure a PTP port entity for each G.8275.1 clock entity.
To configure a PTP port:

1. Navigate to configure system clock ptp-port 0/1 g.8275-1 port <port>.
The config>system>clock>ptp-port(0/1)>port(<port>)# prompt is
displayed.
Configuring asymmetry asymmetry-correction

correction to compensate <nano-sec>
for possible network
asymmetry
Binding SVI to port bind svi <port-number>
Specifying which mac {01-1b-19-00-00-00 | Layer-2 IEEE 1588 packets have destination
destination MAC address to 01-80-c2-00-00-0e} MAC address 01-1B-19-00-00-00 or
use 01-80-C2-00-00-0E
Setting port priority priority <value> Priority is used when selecting the best
source from the PTP ports that are
provisioned as slaves.
Provisioning PTP port state state {master | slave | auto | master distributes time
auto-no-slave} slave provides time source
auto reserved for future use
auto-no-slave reserved for future use
See Configuring PTP Ports for more details
on the PTP port state.
Viewing PTP port status show status
Viewing PTP port statistics show statistics running
Administratively enabling no shutdown Using shutdown disables the port.

port
Configuring the Slave Clock

The slave clock is configured in the clock recovered 0/1 ptp level, specifying
g.8275-1 if you are configuring a G.8275.1 slave clock. Additionally, for G.8275.1
you need to configure PTP ports. For examples of configuring G.8265.1 and
G.8275.1 slave clocks, see Configuring Slave Clock and Configuring Boundary Clock.

To configure the recovered clock:

3. Navigate to configure system clock recovered 0/1 ptp [g.8275-1].
The config>system>clock>recovered(0/1)# prompt is displayed.
Configuring clock quality clock-quality log-variance

<value>
Configuring IP address ip-address <ip-address>
Defining master recovered master <id> Possible values: 12

clock See the commands in the master level
below.
Configuring multicast multicast <ip-address>

IP address
Specifying the peer device peer <peer-number>

that transmits the clock
signal
Defining Telecom Profile profile-type

{telecom-end-to-end |
telecom-peer-to-peer}
Setting precision time ptp-domain <number> Possible values: 023

protocol (PTP) domain
Setting clock recovery recovery-mode { frequency | frequency frequency only

mode time-frequency | time } time-frequency time and frequency
(allowed only in two-way mode; see
description of delay-respond in master
level.)
time Hybrid mode (allowed only in
two-way mode; see description of
delay-respond in master level.)
Defining whether revertive

recovered clock is revertive
Defining amount of time wait-to-restore <seconds> Possible values: 0720

that previously failed clock
must be fault free in order
to be considered available
Clearing network metrics clear-network-metrics See Viewing Clock Recovery Metrics.

{master-to-slave |
slave-to-master | all}
Viewing network metrics show network-metrics See Viewing Clock Recovery Metrics.
Displaying status show status Displays the recovered clock status,

including master/slave

Administratively enabling no shutdown Using shutdown disables the recovered

recovered clock clock.
Commands in level master
Specifying the requested announce [rate { 16sec | 8sec | The allowed range for grant-period is:
rate for announce 4sec | 2sec | 1sec | 500msec | 601000 (default 300)
messages 250msec | 125msec }
[minimum-expected { 16sec |
8sec | 4sec | 2sec | 1sec |
500msec | 250msec |
125msec }]
[grant-period <grant-period>
Configuring asymmetry asymmetry-correction

correction to compensate <nano-seconds>
for possible asymmetry
between the slave and the
grandmaster
Configuring port associated clock-identity clock-id <id> If this is not configured, by default a
with clock port [<slot>/]<number> standard clock ID is generated.
Specifying if recovered delay-respond [rate {16pps | The recovered clock works in one-way mode
clock works in one-way or 32pps | 64pps | 128pps }] if no delay-respond is entered. It works in
two-way mode, and [minimum-expected { 16pps | two-way mode if delay-respond is entered
desired rate if applicable 32pps | 64pps | 128pps }] with parameters.
[grant-period <grant-period>] The allowed range for grant-period is:
601000 (default 300).
Configuring network type network-type { automatic |

dsl }
Specifying the peer device peer <peer-number>

that transmits the clock
signal
Setting priority priority <value>
Setting quality level quality-level { prc | ssu-a | The quality level values are according to the
ssu-b | type1-sec | type1-dnu | network type.
type1-ssm-based }
quality-level { prs | stu | st2 |
tnc | st3e | st3 | smc | st4 | dus
| type2-ssm-based | prov }
Specifying the requested sync [rate { 16pps | 32pps | The allowed range for grant-period is:
rate for synchronization 64pps | 128pps }] 601000 (default 300).
messages [minimum-expected { 16pps |
32pps | 64pps | 128pps }]
[grant-period <grant-period>]

Clearing measured clear-measured-statistics

statistics
Displaying statistics show statistics running Displaying the 1588v2 statistic counters
Displaying measured show measured-statistics Displaying the measured rates of the

statistics received 1588v2 messages
Administratively enabling no shutdown Using shutdown disables the master clock.

master
Configuring the Master Clock

The master clock is configured in the clock master 0/1 ptp level, specifying
g.8275-1 if you are configuring a G.8275.1 master clock. Additionally, for G.8275.1
you need to configure PTP ports. For examples of configuring G.8265.1 and
G.8275.1 master clocks, see Configuring Boundary Clock and Configuring Master
Clock.
Note When configuring a boundary clock, the slave clock must be configured before the
master clock.
To configure the master clock:

5. Navigate to configure system clock master 0/1 ptp [g.8275-1].
The config>system>clock>master(0/1)# prompt is displayed.
Defining the 1588v2 distributed-mode {frequency | In frequency mode, the master transmits sync and
message exchange mode time-frequency} announce messages to slaves.
In time-frequency mode, the master transmits
sync, announce, and delay response messages to
slaves.
Defining the PTP domain domain-number <number> Possible values: 0, or 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 the master IP ip-address <address> The IP address must be the same as the IP address
address of the dedicated router interface.
Defining remote slave slave <ip> See the commands in the slave level below.
Defining maximum number maximum-slaves <number> Possible values: 164

of slaves

Enabling statistic collection pm-collection no pm-collection resets statistic counters and

stops further collection of performance monitoring
data.
Defining Telecom Profile profile-type {telecom-end-to-end |

telecom-peer-to-peer}
Defining the sync-rate { 16pps | 32pps | 64pps | All slaves within the domain must use the same
synchronization message 128pps } message rate.
rate
Selecting Tx clock domain tx-clock {domain <1>}
Displaying status of master show status

clock
Enabling the master clock no shutdown shutdown disables the master clock.
Displaying statistics for show statistics running

master clock
Clearing statistics for clear-statistics

master clock
Commands in level slave
Displaying slave status show status
Displaying statistics for show statistics running

slave clock
Viewing Clock Recovery Metrics

You can display the network performance metrics of the recovered timing. The
metrics apply to the network packet delay variation (PDV) sequence and are useful
for projecting the required system bandwidth. The metrics are displayed for the
slave clock for the following directions:
Master to slave (based on Sync messages)
Slave to master (based on Delay Request messages)
You can display current metrics, metrics for a selected interval of one hour, or for
all intervals.
To display the clock recovery metrics:

7. Navigate to configure system clock recovered 0/1 ptp [g.8275-1].
The config>system>clock>recovered(0/1)# prompt is displayed.

Viewing current metrics show network-metrics current The metrics for the current
interval are displayed as
shown in Viewing Current
Metrics; see Table 9-1.
Viewing the metrics for a selected show network-metrics interval Allowed values for
interval <interval-number> interval-num: 124
The metrics for the

selected interval are
displayed as shown in
Viewing Metrics for
Selected Interval; see
Table 9-1.
Viewing all metrics show network-metrics all The metrics are displayed as
shown in Viewing Current
Metrics and Viewing Metrics
for Selected Interval; see
Table 9-1.
Viewing metrics for all intervals show network-metrics all-intervals The metrics for all intervals
are displayed as shown in
Viewing Metrics for Selected
Interval; see Table 9-1.
Clearing the metrics clear-network-metrics {master-to-slave master-to-slave Clear

| slave-to-master | all} the metrics for the
direction master->slave.
slave-to-master Clear
the metrics for the
direction slave -> master.
all Clear all metrics.
Table 9-1. Network Metrics
Master ID Master clock identification

Id Index of metric observation window (122)
Tau (Sec) Metric observation window
Tdev (ns) Time Deviation PDV metric that characterizes PDV spectral noise, as
defined in ITU-T G.8260
Note: The Tdev values displayed in the network metrics are squares
of the actual Tdev values; therefore, you must compute the square
roots to obtain the correct values.
minTdev (ns) Minimum Time Deviation PDV metric that characterizes floor delay
PDV spectral noise, as defined in ITU-T G.8260
Note: The minTdev values displayed in the network metrics are
squares of the actual minTdev values; therefore, you must compute
the square roots to obtain the correct values.

Elapsed Time This time counter, in seconds, shows the statistics total information
gathering time and indicates the statistics reliability (tightness).
Sampling Time Time of sample
Sampling Date Date of sample
Examples
Configuring Slave Clock
G.8265.1
To configure a G.8265.1 slave clock:

exit all
config port
svi 1
no shutdown
exit all
configure qos policer-profile policer1

bandwidth cir 1000 cbs 32000 eir 0 ebs 0
exit all
config flows
classifier-profile "Router_All" match-any
match all
exit
classifier-profile "Router_Untagged" match-any
match untagged
exit
flow "Router_In"
classifier "Router_Untagged"
policer profile policer1
no shutdown
exit
flow "Router_Out"
classifier "Router_All"
policer profile policer1
ingress-port svi 1
no shutdown
exit all

config router 1
interface 1
address 172.18.141.15/24
bind svi 1
no shutdown
exit
static-route 172.17.171.0/24 address 172.18.141.1 metric 1
exit
peer 1 ip 172.17.171.158
exit all
configure
system
clock
domain 1
source 1 recovered 0/1
priority 1
quality-level ssm-based
wait-to-restore 0
clear-wait-to-restore
exit
exit
recovered 0/1 ptp

wait-to-restore 0
master 1
peer 1
priority 1
sync grant-period 60
announce grant-period 60
delay-respond grant-period 60
quality-level type1-ssm-based
no shutdown
exit
no shutdown
exit

To display recovered clock information:

ETX2i# configure system clock recovered 0/1 ptp
ETX2i>config>system>clock>recovered(0/1/ptp)# info d
multicast 0.0.0.0
no revertive
wait-to-restore 0
no ip-address
ptp-domain 4
recovery-mode time-frequency
master 1
clock-identity clock-id ffffffffffffffff port ffff
priority 1
network-type automatic
peer 1
sync rate 64pps minimum-expected 64pps grant-period 300
announce rate 2sec minimum-expected 2sec grant-period 300
delay-respond rate 64pps minimum-expected 64pps grant-period 300
quality-level type1-ssm-based
no shutdown
exit
no shutdown
To display recovered clock status:

ETX2i# configure system clock recovered 0/1 ptp
ETX2i>config>system>clock>recovered(0/1/ptp)# show status
Clock State: Time-Frequency : Acquisition
Indicated QL : Type-1 SSU-A
Clock Identity : 1
Active Master : 2 Ip Address : 222.18.159.59
Master Num : 1
IP : 222.17.171.158
PTSF : NACT
Clock Identity : 00B0AEFFFE011BC10001
Received QL : Type-1 SEC
Granted Sync Rate (pps) : 64
Granted Sync Period (sec) : 60
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 60
Granted Delay Respond Rate (pps) : 64
Granted Delay Respond Period (sec) : 60
Master Num : 2
IP : 222.18.159.59
PTSF : NACT
Clock Identity : 00B0AEFFFE011BC10001
Received QL : Type-1 SEC
Granted Sync Rate (pps) : 64
Granted Sync Period (sec) : 60
Granted Announce Rate (pps) : 2
Granted Announce Period (sec) : 60
Granted Delay Respond Rate (pps) : 64
Granted Delay Respond Period (sec) : 60

G.8275.1
To configure a G.8275.1 slave clock

Clock sources: Ethernet port 0/1 and Ethernet port 0/4
Flows between:
Ethernet port 0/1 and SVI 1
PTP ports:
Port 1 bound to SVI 1

#****************Configure SVIs
exit all
no shutdown
exit
svi 4
no shutdown
exit
#**************Configure L2CP profile for SSM and Ethernet ports

l2cp-profile SSM
mac 0x02 peer
exit
ethernet 0/1
l2cp profile SSM
tx-ssm
exit
ethernet 0/4
l2cp profile SSM
tx-ssm
exit
exit
#****************Configure classifier profiles

flows
#****************Configure flows
flow eth1_svi1
classifier untagged
egress-port svi 1
no shutdown
exit
flow svi1_eth1
classifier all
ingress-port svi 1
no shutdown
exit
flow eth4_svi4
classifier untagged
egress-port svi 4
no shutdown
exit
flow svi4_eth4
classifier all
ingress-port svi 4
no shutdown
exit

exit
#****************Configure PTP ports
system clock ptp-port 0/1 g.8275-1
port 1
bind svi 1
no shutdown
exit
port 4
bind svi 4
no shutdown
exit
exit
#****************Configure slave clock

recovered 0/1 ptp g.8275-1
no shutdown
exit
#**************** Configure clock sources

domain 1
source 1 rx-port ethernet 0/1
priority 1
wait-to-restore 0
clear
exit

priority 2
wait-to-restore 0
clear
exit all
save
Configuring Boundary Clock
G.8265.1
To configure a boundary clock with G.8265.1 slave and master:

#**************************** Configure slave clock ************
exit all
configure
system
clock
recovered 0/1 ptp
no ptp-domain
master 1
priority 0
peer 1
sync-rate 128pps
delay-respond 128pps
no shutdown
exit

no shutdown
exit
#************************* Configure master clock **************

master 0/1 ptp
ip-address 172.17.163.140
domain-number 0
sync-rate 128pps
no shutdown
exit all
#************************* Save configuration ******************

save
G.8275.1
To configure a boundary clock with G.8275.1 slave and master:

Clock source: Ethernet port 0/1
Flows between:
PTP ports:

#****************Configure SVIs
exit all
no shutdown
exit
svi 4
no shutdown
exit
svi 6
no shutdown
exit
#**************Configure L2CP profile for SSM and Ethernet ports

l2cp-profile SSM
mac 0x02 peer
exit
ethernet 0/1
l2cp profile SSM
tx-ssm
exit
ethernet 0/3
tx-ssm
exit
ethernet 0/5
tx-ssm
exit
exit

flows
flow eth1_svi2
classifier untagged
egress-port svi 2
no shutdown
exit
flow svi2_eth1
classifier all
ingress-port svi 2
no shutdown
exit
flow eth3_svi4
classifier untagged
egress-port svi 4
no shutdown
exit
flow svi4_eth3
classifier all

ingress-port svi 4
no shutdown
exit
flow eth5_svi6
classifier untagged
egress-port svi 6
no shutdown
exit
flow svi6_eth5
classifier all
ingress-port svi 6
no shutdown
exit
exit
#****************Configure PTP ports

port 3
bind svi 2
no shutdown
exit
port 5
bind svi 4
state master
no shutdown
exit
port 7
bind svi 6
state master
no shutdown
exit
exit
#****************Configure slave clock

recovered 0/1 ptp g.8275-1
no shutdown
exit
#****************Configure master clock

master 0/1 ptp g.8275-1
no shutdown
exit
#**************** Configure clock source

domain 1
priority 1
wait-to-restore 0
clear
exit all

save
Dual Mode
To configure a boundary clock with G.8265.1 slave, and dual mode master:
G8265.1 slave:
PTP domain 4
SVI port 1
VLAN 2385
Flows between Ethernet port 0/1 and bridge port 1
Flows between SVI port 1 and bridge port 2
Remote master IP address 172.19.171.100
G8265.1 master:
PTP domain 4
IP address 172.19.171.101
Flows between Ethernet ports 0/2, 0/4, 0/6 and bridge ports 3, 5, 7
Router interface 1 (used for both G8265.1 slave and G8265.1 master):
IP address 172.19.171.101
SVI port 1
G8275.1 master:
PTP domain 5
Flows between Ethernet ports 0/30/5 and SVI ports 35
PTP ports 35 bound to SVI ports 35

#**************** Configure SVI ports

exit all
config port
svi 1
no shutdown
exit
svi 3
no shutdown
exit
svi 4
no shutdown
exit
svi 5
no shutdown
exit
exit
#**************** Configure classifier profiles

flows
#**************** Configure flows for G.8265.1 slave

flow 8265_in
classifier v2385
no shutdown
exit
flow 8265_out
classifier all
ingress-port svi 1
reverse-direction
no shutdown
exit
#**************** Configure flows for G.8265.1 master

flow "in1"
classifier "v2385"
no shutdown
exit
flow "in4"
classifier "v2385"
no shutdown
exit
flow "in6"
classifier "v2385"


no shutdown
exit
#**************** Configure flows for G.8275.1 master

flow "eth3_svi3"
egress-port svi 3
no shutdown
exit
flow "svi3_eth3"
classifier "all"
ingress-port svi 3
no shutdown
exit
flow "eth4_svi4"
ingress-color green
egress-port svi 4
no shutdown
exit
flow "svi4_eth4"
classifier "all"
ingress-port svi 4
no shutdown
exit
flow "eth5_svi5"
egress-port svi 5
no shutdown
exit
flow "svi5_eth5"
classifier "all"
ingress-port svi 5
no shutdown
exit
#******* Configure router interface for G8265.1 slave and master

config router 1
interface 1
address 172.19.171.101/24
bind svi 1
no shutdown
exit
exit

#*********** Configure peer for remote master, for G8265.1 slave

peer 1 172.19.171.100
exit
#**************** Configure clock source

system clock domain 1
source 1 recovered 0/1
priority 1
wait-to-restore 0
exit
exit
#**************** Configure PTP ports

ptp-port 0/1 g.8275-1
port 3
bind svi 3
state master
no shutdown
exit
port 4
bind svi 4
state master
no shutdown
exit
port 5
bind svi 5
state master
no shutdown
exit
exit
#**************** Configure G8265.1 slave

recovered 0/1 ptp
ptp-domain 4
wait-to-restore 0
no shutdown
master 1
peer 1
priority 1
network-type automatic
no shutdown
exit
exit
#**************** Configure G8265.1 master
master 0/1 ptp
ip-address 172.19.171.101
domain-number 4
tx-clock domain 1
no shutdown
exit
#**************** Configure G8275.1 master

domain-number 5

no shutdown
exit all
save
Configuring Master Clock
To configure a dual mode master clock:

G.8265.1 master:
PTP domain 4
IP address 172.20.171.200
SVI port 10
VLAN 1637
G.8275.1 master:
PTP domain 5
Flows between Ethernet ports 0/10/3 and SVI ports 13
PTP port 1 bound to SVI ports 13

#****************Configure SVI ports

exit all
no shutdown
exit
no shutdown
exit
no shutdown
exit
no shutdown
exit

flows
flow eth1_svi1
classifier untagged
egress-port svi 1
no shutdown
exit
flow svi1_eth1
classifier all
ingress-port svi 1
no shutdown
exit
flow eth2_svi2
classifier untagged
egress-port svi 2
no shutdown
exit
flow svi2_eth2
classifier all
ingress-port svi 2
no shutdown
exit
flow eth3_svi3
classifier untagged
egress-port svi 3
no shutdown
exit
flow svi3_eth3
classifier all
ingress-port svi 3


no shutdown
exit
flow G8265_in
classifier v1637
vlan-tag pop vlan
no shutdown
exit
flow G8265_out
classifier all
ingress-port svi 10
no shutdown
exit
#****************Configure PTP port

port 1
bind svi 1
state master
no shutdown
exit
port 2
bind svi 2
state master
no shutdown
exit
port 3
bind svi 3
state master
no shutdown
exit
exit
#****************Configure G.8265.1 master clock

master 0/1 ptp
ip-address 172.20.171.200
domain-number 4
tx-clock domain 1
profile-type telecom-end-to-end
no shutdown
exit
#****************Configure G.8275.1 master clock
domain-number 5
no shutdown
exit
save
Viewing Current Metrics

ETX2i>config>system>clock>recovered(0/1/ptp)# show network-metrics current

Current
-----------------------------------------------------------------------------
Master ID : 1
Master To Slave
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elasped Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 100 501 00:33:29
2 2 55 452 00:33:28
3 4 41 400 00:33:28
4 8 39 400 00:33:29
5 12 71 400 00:33:25
6 16 121 438 00:33:21
7 24 171 411 00:33:14
8 32 231 520 00:33:06
9 48 180 484 00:32:51
10 64 162 593 00:33:07
11 96 63 674 00:32:06
12 128 115 402 00:32:07
13 196 146 547 00:32:41
14 256 138 673 00:29:57
15 384 132 879 00:32:07
16 512 96 400 00:25:46
17 768 172 400 01:04:00
18 1024 116 400 00:51:14
19 2048 1 1 00:34:14
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
Slave To Master
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elasped Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 128 449 00:33:30
2 2 63 400 00:33:30
3 4 45 400 00:33:28
4 8 54 406 00:33:29
5 12 75 400 00:33:25
6 16 122 420 00:33:21
7 24 187 406 00:33:14
8 32 233 428 00:33:06
9 48 189 477 00:32:51
10 64 158 400 00:33:07
11 96 64 400 00:32:06
12 128 122 400 00:32:07
13 196 135 400 00:32:41
14 256 130 569 00:29:57
15 384 129 400 00:32:07
16 512 107 400 00:25:46
17 768 103 400 00:51:13
18 1024 25 400 00:51:13
19 2048 1 1 00:34:09

20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
Viewing Metrics for Selected Interval

ETX2i>config>system>clock>recovered(0/1/ptp)# show network-metrics interval 1
Interval Number : 1
Master ID : 1
Sampling Time : 08:00:00
Sampling Date : 26-07-2012
Master To Slave
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elapsed Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 41448968 58527396 00:05:49
2 2 18079422 28993502 00:05:48
3 4 5276496 15718937 00:05:48
4 8 1201367 12813626 00:05:45
5 12 691645 12206705 00:05:49
6 16 506413 8053903 00:05:38
7 24 622610 3623477 00:05:39
8 32 347378 4017002 00:05:22
9 48 78378 9761690 00:05:39
10 64 139133 6660025 00:05:23
11 96 606 139842 00:04:53
12 128 1 1 00:04:19
13 196 1 1 00:03:19
14 256 1 1 00:04:21
15 384 1 1 00:00:11
16 512 1 1 00:00:13
17 768 1 1 00:00:14
18 1024 1 1 00:00:15
19 2048 1 1 00:00:15
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19

Slave To Master
-----------------------------------------------------------------------------
Id Tau Tdev minTdev Elapsed Time
(Sec) (ns) (ns)
-----------------------------------------------------------------------------
1 1 617756 400 00:30:44
2 2 770042 400 00:30:44
3 4 344708 400 00:30:44
4 8 246177 2935 00:30:41
5 12 226724 65673 00:30:37
6 16 159360 316373 00:30:41
7 24 218542 1682603 00:30:27
8 32 231636 3483920 00:30:27
9 48 203230 6556856 00:30:29
10 64 166905 9179698 00:29:55
11 96 103179 14061712 00:30:29
12 128 88556 19896568 00:29:55
13 196 79678 34140880 00:29:25
14 256 50201 47704072 00:29:57
15 384 60187 119676112 00:25:45
16 512 60686 237447312 00:25:46
17 768 1 1 00:25:47
18 1024 1 1 00:17:10
19 2048 1 1 00:00:15
20 4096 1 1 00:00:18
21 8192 1 1 00:00:19
22 32768 1 1 00:00:19
9.2 Clock Selection

This section discusses the clock selection mechanism provided by ETX2i.
Applicable Products
This feature is applicable to ETX2i and ETX-2i-10G with timing options. It is not
applicable to ETX-2i-B.
Standards
ITU-T G.8261/G.8262-G.8264
Benefits
The clock selection provides synchronization over packet transport networks.
You can configure a slave (recovered) clock that complies with the IEEE-1588
Precision Time Protocol (PTP). You need to configure the clock domain before
configuring the recovered clock.
ETX2i Clock Selection 9-29

ETX2i supports one clock domain with up to two clock sources. The sources can
be network/user Ethernet ports, or the station clock. For ETX2i with EoPDH AIO
module, an Rx clock of a single E1 (bound to VCG 5) can also be provided as a
source clock to ETX2i CSM.
The timing subsystem automatically selects the best timing source to use for
synchronization.
Note
For ETX2i with EoPDH AIO module, the ETX2i CSM system clock can be provided
to module E1s (provided the E1s are bound to VCG 5). For further information,
refer to the VCGs section in Chapter 6.
Clock Domain
The domain parameters include the synchronization network type and the timing
quality level.
The synchronization network type identifies the type of synchronization network
connections and the synchronization level. Each synchronization network
connection is provided by one or more synchronization link connections, each
supported by a synchronized PDH trail, SDH multiplex section trail, or 802.3
physical media trail.
The synchronization network types are:
i. Option I (Europe)
ii. Option II (USA)
You can define the timing quality level of the domain and source, or work without
quality level. The supported quality levels are according to the synchronization
network type, as shown in the following tables. The quality levels are shown in
order of highest quality level to lowest quality level.
Table 9-2. Option I Quality Levels
Quality Description Rank

Level
PRC Timing source is Primary Reference Clock as defined in Recommendation Highest

G.811
SSU-A Timing source is Type I or V Synchronization Supply Unit (SSU) clock as |

defined in Recommendation G.812
SSU-B Timing source is Type VI Synchronization Supply Unit (SSU)clock as defined |

in Recommendation G.812
SEC Timing source is Synchronous Equipment Clock as defined in |

Recommendation G.813 or G.8262, Option I
DNU Do Not Use This signal should not be used for synchronization. Lowest
9-30 Clock Selection ETX2i

Table 9-3. Option II Quality Levels
Quality Description Rank

Level
PRS Timing source is Primary Reference Source clock as defined in Highest

Recommendation G.811
STU Synchronization Traceability Unknown Timing signal does not carry a |

quality level indication of the source.
ST2 Timing source is Stratum 2 clock as defined in Recommendation G.812, |

Type II.
TNC Timing source is Transit Node Clock as defined in Recommendation G.812, |

Type V.
ST3E Timing source is Stratum 3E clock as defined in Recommendation G.812, |

Type III.
ST3 Timing source is Stratum 3 clock as defined in Recommendation G.812, |

Type IV.
SMC Timing source is SONET/Ethernet self-timed clock as defined in |

Recommendation G.813 or G.8262, Option II.
ST4 Timing source is Stratum 4 free-running clock (applicable only to 1.5 |

Mbit/s signals).
PROV Provisionable by the network operator |
DUS Don't Use for Sync This signal should not be used for synchronization. Lowest
Factory Defaults
By default, if a timing card is installed in the unit a clock domain entry is created
with the following configuration:
Synchronization network type 1
Minimum quality DNU
Mode auto (clock selection mechanism functions normally)
Configuring the Clock Domain
To configure the clock domain:

1. Navigate to configure system clock domain 1.
The config>system>clock>domain(1)# prompt is displayed.
Canceling previously issued clear

force or manual command
Clearing statistics for clock clear-statistics

sources

Forcing selection of a force <source-id>

particular clock source
when the sources have
different quality levels
Forcing T4 (station clock) force-t4-as-t0 Use no-force-t4-as-t0 to

timing generator to use prevent T4 timing generator
the same clock source as from using the same clock
the T0 (system clock) source as the T0 generator.
generator
Manually selecting a manual <source-id> This command in the following

particular clock source conditions:
No quality is defined for the
clock domain.
The sources have the same
qualities.
The sources have different
priorities.
Setting maximum max-frequency-deviation <value> Range is 3816096, in units of

frequency deviation PPM*100 (e.g. specifying 381
sets maximum frequency
deviation to 3.81).
When frequency deviation of
an input clock source exceeds
the defined maximum
frequency deviation, the clock
source is declared invalid.
Setting clock mode mode { auto | free-run | force-t0-holdover } auto Clock selection
mechanism functions normally,
e.g. the best available clock
source is selected for
synchronization.
free-run Internal oscillator is
used for synchronization.
force-t0-holdover Clock is no
longer synchronized to
reference clock source.

Setting minimum quality of quality min-level-station { prc | ssu-a | ssu-b | sec | dnu } Typing no quality removes the
clock quality min-level-station { prs | stu | st2 | tnc | st3e | st3 | minimum quality parameter. If
smc | st4 | dus | prov } no minimum quality is defined
for the domain you cannot
quality min-level-station { unk | sec | dnu }
configure quality level for the
sources. A clock source with
quality level lower than the
defined minimum quality is
ignored by the clock selection
mechanism.
Note: The quality values are
according to the
synchronization network type
defined for the domain (see
Table 9-2 and Table 9-3).
Displaying domain status show status
Configuring clock source source <src-id> Typing no source <src-id>

deletes the source.
See Clock Sources.
Adding clock source source <src-id> recovered [<slot>/]<port> See Clock Sources.
source <src-id> rx-port {ethernet [<slot>/]<port>|e1 Notes:
<slot>/<port>} Only an E1 port bound to
source <src-id> station [<slot>/]<port> VCG 5 can be used as an Rx
port in CSM.
Only one E1 from the
EoPDH AIO module can be
used as a source. However,
if the selected E1 is
inactive, the system
automatically finds the next
active E1 in VCG 5, and uses
it as a source (redundancy).
Setting synchronization sync-network-type { 1 | 2} Type 1 Europe

network type Type 2 USA
Note: When you change the
synchronization network type,
you have to redefine the clock
sources.
Clock Sources
You can define up to two clock sources for the domain. The sources can be:
Ethernet ports
Recovered clock
Station clock

E1 Rx clock (for ETX2i with EoPDH AIO module)
Note If an Ethernet port is defined as a clock source, it must be associated with an

L2CP profile that specifies peer action for MAC 0x02. It is also recommended to
enable the transmitting of SSM messages by the port (via tx-ssm), as it may
need to transfer clock signals.
In ETX2i with EoPDH AIO module, only an E1 port bound to VCG 5 can be
defined as a clock source. This feature provides redundancy; if the selected E1
is inactive, another E1 (active with a valid clock) within VCG 5 is automatically
selected as the source.
Factory Defaults
When a clock source is created, its default configuration is the following (see the
task list below for explanations of the parameters):
Priority = 2
Wait-to-restore = five minutes (300 seconds)
Hold-off = 300 milliseconds
Configuring the Clock Sources
To add a clock source:

Type one of the following, according to the type of clock source:
source <12> rx-port ethernet [<slot>/]<port>
source <12> rx-port e1 <slot>/<port>
source 1 recovered [<slot>/]<port>
source <12> station [<slot>/]<port>
The clock source is created and the
config>system>clock>domain(1)>source(<12>)$ prompt is displayed.
2. Enter all necessary commands according to the tasks listed below the following
procedure.
To configure a clock source that has already been created:

2. Type source <12> to select the source to configure.
The config>system>clock>domain(1)>source(<12>)# prompt is displayed.

Canceling the wait-to-restore clear-wait-to-restore

timer of a clock source. This is
useful if a timing source fault is
cleared and you want the
source to be immediately
available.
Defining amount of time (in hold-off <milliseconds> Possible values: 3001800

milliseconds) that signal failure
must be active before it is
transmitted
Setting priority priority <num> Possible values: 12

Note: Priority 1 is the highest.
Setting quality level quality-level { prc | ssu-a | ssu-b | sec | dnu | ssm-based } Notes:
quality-level { prs | stu | st2 | tnc | st3e | st3 | smc | st4 | If no minimum quality is
dus | ssm-based | prov } defined for the domain, this
command is not available.
The quality level values are
according to the
synchronization network
type defined for the domain
(see Table 9-2 and
Table 9-3)
The quality level ssm-based
indicates the quality level is
based on SSM messages.
This option requires that if
an Ethernet port is being
used as the clock source,
the port is associated with
an L2CP profile that
specifies peer action for
MAC 0x02.
Defining amount of time (in wait-to-restore <seconds> Possible values: 0720

seconds) that a previously
failed synchronization source
must be fault free in order to
be considered available
Displaying statistics show statistics
Viewing Clock Source Statistics

You can display the Ethernet Synchronization Messaging Channel (ESMC) statistics
for the clock sources.

To display the ESMC statistics for a clock source:

1. Navigate to configure system clock domain 1 source <src-id>.
config>system>clock>domain(1)>source(<src-id>)#.
2. Enter:
show statistics
The ESMC statistics are displayed.
Configuring the Station Clock

The station clock is an E1/2MHz port that can be used for synchronization.
To configure the station clock:

3. Navigate to configure system clock station 0/1.
The config>system>clock>station(0/1)# prompt is displayed.
Setting interface type interface-type e1 [{balanced | unbalanced}] If you specify e1 or 2mhz and
Note: You can configure interface-type 2mhz [{balanced | unbalanced}] do not specify balanced or
the interface type only if unbalanced, by default the
the station clock is interface is set as balanced.
administratively disabled
(shutdown).
Setting line code line-code { ami | hdb3 } ami Referred to as Alternate

Note: You can configure Mark Inversion because a 1 is
the line code only if the referred to as a mark and a 0
interface type is E1 and as a space.
the station clock is hdb3 Referred to as High
administratively disabled Density Bipolar of order 3, this
(shutdown). code is a telecommunication
line code based on AMI and
used in E1 lines.
Setting receiver sensitivity rx-sensitivity {short-haul | long-haul}

to adjust the signals
capability to reach
destinations close by or
farther away
Setting clock timing to be tx-clock-source {system | loopback-timing} system timing based on

based on internal system internal system
or external source loopback-timing timing based
on E1/2MHz external source
Administratively enabling no shutdown Using shutdown disables the

station clock station clock.

Examples
To configure clock selection
Domain 1:
Synchronization network type 2
Quality level: Timing source is Stratum 3E clock
Source 1: Ethernet port 0/3 (which is configured with L2CP profile with
peer for MAC 0x02, and transmitting of clock SSM messages)
exit all
configure port l2cp-profile ssm
mac 0x02 peer
exit
ethernet 0/3
l2cp profile ssm
tx-ssm
exit all
configure system clock domain 1

sync-network-type 2
quality min-level-station st3e
exit all
To display the clock source statistics:

ETX2i# configure system clock domain 1 source 1
ETX2i>config>system>clock>domain(1)>source(1)# show statistics
ESMC Failure Counter : 0
Rx Tx
ESMC Events : 1 2
ESMC Information : 1 255
ETX2i>config>system>clock>domain(1)>source(1)$ exit
ETX2i>config>system>clock>domain(1)# info detail
sync-network-type 2
quality min-level-station st3e
max-frequency-deviation 1200
mode auto
force-t4-as-t0
echo "Clock Source Configuration"
# Clock Source Configuration
priority 2
wait-to-restore 300
hold-off 300
exit

To configure AIO E1 1/1 port as rx-clock-source 1 under domain 1:

ETX2i# configure system clock domain 1 source 1
ETX2i>config>system>clock>domain(1)# source 1 rx-port e1 1/1
9.3 Date and Time

You can configure the ETX2i internal real-time clock as free running or with Simple
Network Time Protocol (SNTP).
For ETX2i with DNFV, you can configure its integrated x86 processor internal real-
time clock as free running or with Network Time Protocol (NTP).
Applicable Products
This feature is applicable to all ETX2i products, and to the integrated x86
processor, with the following restrictions:
Manual configuration of the date and time is relevant for ETX2i products, as
well as the integrated x86 processor.
SNTP configuration is relevant for ETX2i products.
NTP configuration is relevant for integrated x86 processors (in ETX2i with
DNFV).
Standards and MIBs

DISMAN-SCHEDULE-MIB, RFC 3231
IF-MIB, RFC 2863
SNMPv2-MIB, RFC 3418
RFC 4330
Benefits
SNTP and NTP synchronize the internal clocks of network devices to a single time
reference source. SNTP and NTP provide comprehensive mechanisms to access
national time dissemination services, organize the NTP subnet of servers and
clients, and adjust the system clock in each participant. It improves the
timekeeping quality of the network by using redundant reference sources and
diverse paths for time distribution.
Network Time Protocol (NTP) is a networking protocol for clock synchronization
between computer systems over packet-switched, variable-latency data networks.
It is a large and very complex application for the synchronization of computers and
computer networks, incorporating complex statistical algorithms that filter out
small discrepancies in time and makes time adjustments. It synchronizes all
9-38 Date and Time ETX2i

participating computers to within a few milliseconds of Coordinated Universal Time

(UTC).
Simple Network Time Protocol (SNTP), a less complex implementation of NTP, uses
the same protocol without requiring the storage of state over extended periods of
time. It synchronizes the internal clocks of network devices to a single time
reference source.
The SNTP client operates in one of the following modes:
Unicast Sends requests to configured server addresses
Broadcast Listens to an unsolicited broadcast address and learns

timestamps from any broadcast server sending messages
to this address
Note
SNTP is not supported on OOB ports.
Factory Defaults
The default configuration of the SNTP/NTP parameters is:
No SNTP/NTP servers are defined.
Polling interval is set to 15 minutes (relevant for SNTP only).
When an SNTP/NTP server is defined, its default configuration is:
IP address is set to 0.0.0.0
Not preferred
Administratively disabled (shutdown)
Setting the Date and Time

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

format mm-dd-yyyy | yyyy-dd-mm}
Defining the date date <date> Date is according to the configured date
format.
Configuring NTP ntp For configuration of internal clock in

integrated x86 processor (relevant for
ETX2i with DNFV).
See Working with NTP.
ETX2i Date and Time 9-39

Configuring SNTP sntp For configuration of ETX2i device internal

clock.
See Working with SNTP.
Scheduling adjustment of device summer-time See Configuring Daylight Saving Time

time for daylight saving time Scheduling.
start and stop
Displaying daylight saving time show summer-time See Viewing Scheduling Information.
scheduling information
Defining the time zone relative zone utc [<[{+|-}]hh[:mm]>] Possible values:
to Universal Time Coordinated -12:00 to +12:00, in 30-minute increments
(UTC)
Defining the time time <hh:mm[:ss]>
Viewing the Date and Time

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

You can configure the time on the internal clock of the ETX2i device, with the
time on an SNTP server.
This section explains how to receive the clock signal from NTP servers in the
network. ETX2i can synchronize with up to ten servers, sending NTP requests to
the servers at user-defined intervals.
You can set one of the active SNTP servers as the preferred server, so that ETX2i
sends NTP requests to the preferred server. If there is no preferred server or if the
preferred server does not answer, then ETX2i sends NTP requests to any enabled
servers.
Configuring SNTP Parameters

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

broadcast messages to obtain broadcast mode.
accurate timestamps

Setting polling interval for SNTP poll-interval interval <minutes> If interval parameter is
requests poll-interval fast-mode specified, the allowed
range of minutes is:
11440
If fast-mode parameter is
specified, the interval is set
to 4 seconds (for accuracy
of TWAMP one-way
metrics).
Defining and configuring SNTP server <server-id>

servers (see Defining SNTP
Servers and Configuring SNTP
Server Parameters)
Displaying SNTP status show status
Defining SNTP Servers

To define an SNTP server:
1. Navigate to config system date-and-time sntp.
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:
1. Navigate to config system date-and-time sntp.
2. Type server <server-id> to select the SNTP server to configure.
config>system>date-time>sntp>server(<server-id>)#
Setting the IP address of the address <IP-address>

server
Set SNTP server as preferred prefer Type no prefer to remove

server. preference.
Note: Only one server can be
preferred.

Setting UDP port for NTP udp port <udp-port> Possible values: 165535
requests, to a specific UDP port udp default
or to default UDP port (123)
Administratively enabling server no shutdown Using shutdown disables the

server.
Sending query to server and query-server

displaying result
Working with NTP

You can configure the time on the internal clock of the integrated x86 processor in
ETX2i with DNFV, with the time on an NTP server.
This section explains how to receive the clock signal from NTP servers in the
network. One of the active NTP servers can be designated the preferred server, so
that NTP requests are sent to the preferred server. If there is no preferred server
or if the preferred server does not answer, then NTP requests are sent to any
enabled servers.
Configuring NTP Parameters

To configure NTP parameters:
1. Navigate to configure system date-and-time ntp.
The config>system>date-time>ntp# prompt is displayed.
Defining and configuring NTP server <server-id>

servers (see Defining NTP
Servers and Configuring NTP
Server Parameters)
Displaying NTP status show status
Defining NTP Servers

To define an NTP server:
1. Navigate to config system date-and-time ntp.
2. Type server <server-id> to define an NTP server with ID <server-id>.
config>system>date-time>ntp>server(<server-id>)$.
3. Configure the NTP server parameters as needed, as described in Configuring
NTP Server Parameters.

Configuring NTP Server Parameters

To configure NTP server parameters:
1. Navigate to config system date-and-time ntp.
2. Type server <server-id> to select the NTP server to configure.
config>system>date-time>ntp>server(<server-id>)#
Setting the IP address of the address <IP-address>

server
Set NTP server as preferred prefer Type no prefer to remove

server. preference.
Note: Only one server can be
preferred.
Administratively enabling server no shutdown Using shutdown disables the

server.
Sending an NTP polling request query-server

to check server status
Examples
Setting Date and Time
To set the date and time:

Format = mm-dd-yyyy
Date = May 17, 2012
Time = 5:40pm
Zone = UTC 4 hours and 30 minutes
exit all
configure system date-and-time
date-format mm-dd-yyyy
date 05-17-2012
time 17:40
zone utc -04:30
Defining SNTP Server
To define SNTP server:

Server ID = 1
IP address = 192.1.1.1
Preferred

exit all
configure system date-and-time sntp
server 1
address 192.1.1.1
prefer
no shutdown
Viewing SNTP Server Information
To display server information:

ETX2i# configure system date-and-time sntp server 1
ETX2i>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
ETX2i>config>system>date-time>sntp>server(1)# exit
ETX2i>config>system>date-time>sntp# show status
System Uptime : 000 Days 00:19:55
System Time : 2009-09-14 13:01:09
Current Source : 1 127.0.0.1
NTP Server Type UDP Port Tstap Date Time Strat Received
192.1.1.1 Prefer 123 00-00-0000 00:00:00 0 --
Defining NTP Server
To define NTP server:

Server ID = 1
IP address = 172.17.171.141
Preferred

exit all
configure system
date-and-time
zone utc +03:00
ntp
server 1
address 172.17.171.141
prefer
no shutdown
exit
9.4 Daylight Saving Time

You can schedule your device to change its system time to daylight saving time
(also known as summer time), at a specific date and time.
Applicable Products
Factory Defaults
By default, no scheduling is configured.
The default value for daylight saving time offset is 60 minutes.
You can specify when the device local system time should reflect the start of
daylight saving time by adding an offset, and when it should reflect the end of
daylight saving time by subtracting the offset.
Daylight saving time can be scheduled in one of the following ways:
One shot Daylight saving time starts and ends once, at a specified
date and time (e.g. November 6 2016).
Recurring Daylight saving time starts and ends every year at a

specified time, and a date specified according to the
weekday and month (e.g. first Sunday in October).
The daylight saving time schedule is saved in nonvolatile (permanent) memory, in

order to be available after device reboot.
Note ETX2i logs the start and end of daylight saving time with the events
summer_time_started and summer_time_ended, respectively. Each event is also
sent as an SNMP notification to management stations.
ETX2i Daylight Saving Time 9-45

Configuring Daylight Saving Time Scheduling

When you configure daylight saving time scheduling, the first set of parameters in
the commands specifies when daylight saving time starts, and the second set of
parameters specifies when daylight saving time ends.
To configure daylight saving time:

Navigate to the config>system>date-time level and enter the summer-time
command according to the type of schedule:
One shot Enter:
summer-time date {january | february | march | april | may | june | july |
august | september | october | november | december} <dd> <yyyy>
<hh>:<mm> {january | february | march | april | may | june | july | august |
september | october | november | december} <dd> <yyyy> <hh>:<mm>
[<offset>]
Recurring Enter:
summer-time recurring { 1 | 2 | 3 | 4 | last} {sunday | monday | tuesday |
wednesday | thursday | friday | saturday} {january | february | march | april |
may | june | july | august | september | october | november | december}
<hh>:<mm> { 1 | 2 | 3 | 4 | last} {sunday | monday | tuesday | wednesday |
thursday | friday | saturday} {january | february | march | april | may | june |
july | august | september | october | november | december}
<hh>:<mm>[<offset>]
The parameter {1 | 2 | 3 | 4 | last} specifies the week of the month.
For both schedule types, <offset> specifies (in minutes) the time to add at
daylight saving time start, or subtract at daylight saving time end. Its range is 1
1440.
To delete daylight saving time scheduling:

Navigate to the config>system>date-time level and enter:
no summer-time
Viewing Scheduling Information

For details and an example on how to view scheduled daylight saving time in your
device, refer to the Viewing Scheduling Information section in Chapter 4.
Examples
To schedule daylight saving time starting March 27 2016 at 1:00 and ending
October 27 2016 at 2:00:
exit all
summer-time date march 27 2016 01:00 october 27 02:00
save
9-46 Daylight Saving Time ETX2i

To schedule daylight saving time starting on the first Friday in March at 2:00 and
ending on the last Sunday in October at 3:00:
exit all
summer-time recurring 1 friday march 02:00 last sunday october
03:00
save
Schedule with this name You tried to create a new schedule with Specify a name that is not being used
already configured a name that is used by an existing by an existing schedule.
schedule.
Summer-time already You entered the summer-time command Delete the existing summer-time
configured to configure daylight saving time, but configuration; and then re-enter the
the scheduling of summer-time has summer-time command.
already been configured.
Recurring summer-time You tried to configure summer-time start Enter the summer-time command
start and end must be and end in the same month. with summer-time start and end in
on different months different months.
Summer-time cannot You entered the summer-time command Enter the summer-time command
end before it starts (with one-shot schedule type) with with summer-time start time earlier
summer-time end time earlier than than the end time.
summer-time start.
ETX2i Daylight Saving Time 9-47

9-48 Daylight Saving Time ETX2i

Chapter 10
Administration
This chapter describes administrative features:
Confirming Startup Configuration
CPU and Memory Utilization
Device Information
Environment
File Operations
Inventory
Licensing
Login Banner
Reset
Tech-Support Commands
10.1 Confirming Startup Configuration
Applicable Products
Configuring Startup Configuration Confirmation

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

At the admin# prompt enter:
startup-confirm-required [time-to-confirm <minutes>] [rollback
{startup-config | user-default-config | factory-default-config |
running-config}]
The <minutes> parameter defines the confirmation timeout, range 165535
(default 5). If rollback <config-file> is specified, the specified configuration
file is copied to rollback-config.
ETX2i Confirming Startup Configuration 10-1

Chapter 10 Administration Installation and Operation Manual
To confirm confirmation of startup-config after reboot;

In any level, enter:
startup-config-confirm
10.2 CPU and Memory Utilization

You can view the CPU and memory pool usage.
Applicable Products
Viewing CPU Utilization

To display CPU usage:
From the system context (config>system), enter:
show cpu-utilization
The CPU usage is displayed.
ETX-2i>config>system# show cpu-utilization
CPU Utilization
---------------------------------------------------------------
Min (%) : 2
Cur (%) : 2
Max (%) : 65
Average (%) : 10
Viewing Memory Pool Utilization

To display memory pool usage:
1. From the system context (config>system), enter the following to display
memory pool usage:
show memory
The memory pool usage is displayed, showing the total amount allocated
to the pool, as well as the amount that is free.
ETX-2i>config>system# show memory
Kernel Kernel
Total (KB) Free (KB)
---------------------------------------------------------------
Memory 3166141899 1051027919
2. From the system context (config>system), enter the following to display
details of memory pool usage:
show memorydetails
ETX-2i>config>system# show memory-details
Kernel Total(KB) : 3166141899 Free : 1051027919
10-2 CPU and Memory Utilization ETX2i

Installation and Operation Manual Chapter 10 Administration
10.3 Device Information

The ETX2i management software allows you to assign a name and description to
the unit, specify its location to distinguish it from the other devices installed in
your system, and assign a contact person.
Standards
The commands below are based on RFC 3841.
Configuring Parameters
To configure device information:
1. Navigate to configure system.
The config>system# prompt is displayed.
Specifying contact person contact <contact-person> Typing no contact removes contact person.
Assigning device name name <device-name> The device name can be 0-255 characters; however, the device
prompt displays only up to 20 characters, therefore if you enter a
name with more than 20 characters, the prompt displays the first
19 characters followed by *.
For example, a command that defines a device with a name
longer than 20 characters:
ETX2i# config sys name 12345678901234567ETX2i
results in the prompt:
12345678901234567ET*#
You can view the complete device name by typing
show device-information.
Typing no name removes the name entirely.
Specifying location location <device-location>
Displaying device show device-information The command output indicates after sw version number (sw:) if
information, MAC address, the device is using Static Router license (SR). No indication
and amount of time device means Dynamic Router license is being used (the default).
has been running
ETX2i Device Information 10-3

Example
To configure device information for ETX2i:
Device name ETX2i
Location floor-8
Contact Engineer-1
exit all
configure system
name ETX-2i
location floor-8
contact Engineer-1
exit all
To display device informationETX2i:

ETX-2i>config>system# show device-information
Description : ETX-2i Hw: 0.1/6xGbE SFP, Sw: 6.4

Name : ETX-2i
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-30-CC-9D
Engine Time : 05:13:31
10.4 Environment
You can define the temperature threshold of a chassis and display information
about chassis components.
Device Temperature
You can define minimum and maximum temperature thresholds, as well as
temperature unit (Celsius or Fahrenheit), in order to receive trap notification that
the device temperature has left the allowed range or returned to the allowed
range.
You can optionally use a hysteresis mechanism to avoid sending an excessive
amount of traps when a threshold is repeatedly crossed. The hysteresis defines
the margin around the temperature thresholds for sending trap notification of
temperature threshold crossed:
Sends trap notification of temperature too high when the temperature rises
above <maximum temperature + hysteresis value>.
After sending a trap notification of temperature too high, it sends a trap
notification of temperature OK when the temperature falls below <maximum
temperature - hysteresis value>.
10-4 Environment ETX2i

Sends trap notification of temperature too low when the temperature falls
below <minimum temperature - hysteresis value>.
After sending a trap notification of temperature too low, it sends the trap
notification of temperature OK when the temperature rises above <minimum
temperature + hysteresis value>.
Device Fan
The device fan is activated when the temperature of the device exceeds a certain
limit (defined by RAD HW engineers; non-configurable). When the device
temperature once again drops below that limit, the fan stops.
A Fan Failure alarm is issued if the device fan stops working or its speed drops
below 100RPM.
Configuring the Temperature Threshold

To configure the temperature threshold:
1. Navigate to configure chassis.
The config>chassis# prompt is displayed.
2. Type:
temperature-threshold { celsius | fahrenheit } min <min-value>
max <max-value> [ hysteresis <hysteresis-value> ]
The temperature thresholds are set as specified.
Viewing Environment Information

You can display information about the following:
Type and status of the power supplies
Status of the fans
Temperature sensor
To display the information:

1. Navigate to configure chassis.
The config>chassis# prompt is displayed.
2. Enter:
show environment
The information is displayed as shown in the examples below.
The power supply type is indicated as AC, DC, or -- (if it is absent or has
failed).
The status for the power supplies and fans indicates whether the
component is present and functioning properly, or is absent (does not
exist), or has failed.
The temperature sensor status indicates the temperature, and whether
the sensor is functioning correctly.
ETX2i Environment 10-5

Examples
To define temperature thresholds:
Minimum temperature = -20 degrees Celsius
Maximum temperature = 50 degrees Celsius
Hysteresis = 4
exit all
ETX-2i>configure chassis
ETX-2i>config chassis#
temperature-threshold celsius min -20 max 50 hysteresis 4
exit all
save
To view environment information:

ETX-2i# configure chassis
ETX-2i>config>chassis# show environment
Power Supply Type Status
---------------------------------------------------------------
1 AC OK
FAN Status
---------------------------------------------------------------
1 OK
Sensor Value Status

---------------------------------------------------------------
1. 32 Celsius OK
10.5 File Operations

You can perform the following operations:
Transfer files via SFTP/TFTP
Copy files within the ETX2i unit
Display files
Delete files
You can copy or transfer files via the copy command, or via the commands shown
in Table 10-2. As shown in the table, some commands that reset the device also
erase the saved user configuration by copying another file to it before the reset.
Table 10-1. Commands That Copy Files
Command Level Copies Additional Manual Section

Actions
save Global running-config to startup-config None Saving Configuration

Changes (in Operation
chapter)
10-6 File Operations ETX2i

Command Level Copies Additional Manual Section

Actions
factory-default Admin factory-default to startup-config Unit resets Resetting to Factory

after copying Defaults
user-default Admin user-default-config to startup-config Unit resets Resetting to User

after copying Defaults
Applicable Products
Using SFTP or TFTP

You can download or upload files to the ETX2i unit via SFTP/TFTP. Normally the
types of files copied are configuration files and software files.
The software files can also be downloaded to ETX2i via the Boot Manager, using
XMODEM, FTP, or TFTP. For details on upgrading the device software, refer to the
Software Upgrade chapter.
SFTP Application
The SFTP protocol is used to provide secure file transfers via the product's
Ethernet interface. SFTP is a version of FTP that encrypts commands and data
transfers, keeping your data secure and your session private. For SFTP file
transfers, an SFTP server application must be installed on the local or remote
computer.
A variety of third-party applications offer SFTP server software. For more
information, refer to the documentation of these applications.
Setting up SFTP Server

If you use a local laptop and SFTP is the preferred transfer method, a SFTP server
application must be installed on it.
As mentioned above, third-party applications are available and you should refer
to their setup documentation.
Note SFTP file transfers are carried out through TCP port 22. You should check that the
firewalls you are using on the server and Windows allow communication through
this port. If not, configure the firewall settings to open TCP port 22.
TFTP Application
The TFTP protocol is typically used for remote IP-to-IP file transfers via the
product's Ethernet interface. It can be used, however, for local file transfer as
well, as the transfer rate of the Ethernet interface is much faster than that of the
RS-232 interface.
For TFTP file transfers, a TFTP server application must be installed on the local or
remote computer. As it runs in the background, the TFTP server waits for any
ETX2i File Operations 10-7

TFTP file transfer request originating from the product, and carries out the
received request automatically.
A variety of third-party TFTP applications are available that allow the instant
creation of a TFTP server on a client computer. For more information, refer to the
documentation of these applications.
Setting up a TFTP Server

If you use a local laptop and TFTP is the preferred transfer method, a TFTP server
application must be installed on it.
As mentioned above, third-party applications are available and you should refer
to their setup documentation.
Note TFTP file transfers are carried out through UDP port 69. You should check that
the firewalls you are using on the server and Windows allow communication
through this port. If not, configure the firewall settings to open UDP port 69.
Copying Files
You can use the copy command to copy files within the ETX2i unit, or
download/upload files to the ETX2i unit via SFTP/TFTP.
To copy files:
At any prompt, enter:
copy <source-file-url> <destination-file-url>
Where:
<file-url> = <url-prefix> <file>
<url-prefix> can be empty, or one of the following:
tftp://<ipv4-address>/
tftp://[<ipv6-address>]/
sftp://<username>:<password>
@<ipv4-address>[:<port>]/
sftp://<username>:<password>@[<ipv6-address>][:<port>]/
xmodem:
Note It is not necessary to specify <port> when using the well-known SFTP port.
<file> can be empty, or one of the following files, or the file name on a
remote computer if applicable. If <file> is on a remote computer it can
contain a path and file name, or just a file name.
startup-config
restore-point-config
rollback-config
running-config

user-default-config
factory-default-config
log
sw-pack-1
sw-pack-2
sw-pack-3
sw-pack-4
zero-touch-config-xml
banner-text
pm-0
db-schema
mac-table
db-config
1tm_1
1tm_2
1tm_9
schedule-log
sniffer-file
user-script
script-result
cn-backup-file
The maximum length/range is:
<username> 160 characters
<password> 160 characters
<file> 196 characters
<port> 165535
Examples
Copying Files Within Device

Source file name running-config
Destination file name startup-config
copy running-config startup-config
Downloading via TFTP

TFTP server address 192.10.10.10
Source file name d:/img/ETX2i.img
Destination file name sw-pack-2

copy tftp://192.10.10.10/d:/img/ETX-2i.img sw-pack-2
Uploading via TFTP

TFTP server address 192.10.10.10
Source file name startup-config
Destination file name c:/etx/config/db1conf.cfg
copy startup-config tftp://192.10.10.10/c:/etx/config/db1conf.cfg
Downloading via SFTP

SFTP server address 192.20.20.20
SFTP user name admin
SFTP password 1234
Source file name bin/ETX2i.img
Destination file name sw-pack-2
copy sftp://admin:1234@192.20.20.20/bin/ETX-2i.img sw-pack-2
Uploading via SFTP

SFTP server address 192.20.20.20
SFTP user name admin
SFTP password 1234
Source file name startup-config
Destination file name config/db1conf.cfg
copy startup-config sftp://admin:1234@192.20.20.20/config/db1conf.cfg
Viewing Copy Status

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

At the file# prompt, enter:
show copy [summary]
Viewing Information on Files

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

To display the files within the device:

dir
A list of the file names and types is displayed.
Example
ETX-2i# file
ETX-2i>file# dir
Codes CConfiguration S-Software LO-Log OOther B-Banner
Name Type Size(Bytes) Creation Date Status
mac-table O -- 2012-07-15 Read Only

03:39:48
sw-pack-1 S 3366481 2012-04-10
0:0:6
sw-pack-2 S 3366780 2012-07-18 File In Use
20:53:12
startup-config C 23269 2012-08-02
18:19:7
factory-default-config C 12404 2012-08-13 Read Only
17:18:7
running-config C -- 2012-04-10 File In Use
0:0:6
log LO 105840 2012-04-10 Read Only
0:0:6
ltm_1 LO 102400 2012-04-10 Read Only
0:0:6
Total Bytes : 27359280 Free Bytes : 13413376
Bytes Available for PM: 4990142
To display information on the configuration files:

show configuration-files
Information on the configuration files is displayed.

Example
ETX-2i# file
ETX-2i>file# show configuration-files
Configuration Last Modified Valid
-----------------------------------------------------------------------------
startup-config 2012-08-02 18:19:07 Yes
factory-default-config 2012-08-13 17:18:07 Yes
running-config 2012-04-10 00:00:06 Yes
Device loaded from : startup-config
running-config has been modified since last time it was equal to startup-config
To display the contents of configuration text files:

At the file# prompt, enter one of the following:
show factory-default-config
show rollback-config
show startup-config
show user-default-config
The contents of the specified configuration file are displayed.
To display information on the software files:

show sw-pack [refresh [<sec>]]
where sec represents the refresh timeout, with range 3100.
Information on the software files is displayed.

Example
ETX-2i# file
ETX-2i>file# show sw-pack
Name Version Creation Time Actual
---------------------------------------------------------------
sw-pack-1 6.4 2014-11-14 14:28:44 ready
sw-pack-2 6.4 2014-11-14 14:28:44 active
sw-pack-1 Size (Bytes) : 3366481
Type Name Version H/W Ver

Size
(Bytes)
---------------------------------------------------------------
main main.bin 6.4 0.0 3366241
sw-pack-2 Size (Bytes) : 3366780
Type Name Version H/W Ver

Size
(Bytes)
---------------------------------------------------------------
main main.bin 6.4 0.0 3366241
Deleting Files
You can delete the following files:
restore-point-config
script-result
sw-pack-<n>
rollback-config
startup-config
user-default-config
user-script
zero-touch-config-xml
Note Use caution in deleting files.
To delete a file:
1. At the file# prompt, enter:
delete <file-name>
You are prompted to confirm the deletion.
2. Confirm the deletion.

Example
ETX-2i# file
ETX-2i>file# delete startup-config
! The file will be erased. Are you sure? [yes/no] _yes
10.6 Inventory
The ETX2i inventory table displays the units components, hardware and
software revisions, and power supply types. You can display an inventory table
that shows all installed components, and you can display more detailed
information for each component. You can configure an alias name, asset ID, and
serial number for inventory components.
Applicable Products
This feature is applicable to all ETX2i products; however, the inventory display
differs for each product according to the different chassis components and port
configurations.
Standards
The inventory feature is implemented according to RFC 4133 Entity MIB
(RFC 2737 was made obsolete by RFC 4133 version 3).
Benefits
You can monitor the installed components and hardware/software revisions.
Viewing Inventory Information

To display the inventory table:
At the config>system# prompt, enter:
show summary-inventory
The inventory table is displayed (see Example for a typical inventory table
output).
You can display more information for each installed inventory component. To do
so, you need to enter the inventory level with the corresponding inventory
component index, which is displayed in the Index column in the output of
show summary-inventory.
To display the inventory component information:

1. Navigate to configure system inventory <index>.
2. Enter:
show status
10-14 Inventory ETX2i

Information for the corresponding inventory component is displayed (see

Table 10-3 for information on the parameters).
Table 10-2. Inventory Parameters
Description Description of component type, in the form:
RAD.<device-name>.< Physical Class>, e.g. RAD.ETX2i.Port
Contained In Index of the component that contains the component for which
information is being displayed. This is 0 for the chassis, as it is not
contained in any component, and 1001 for all other components, as they
are all contained in the chassis.
Physical Class Class of component
Possible values: Chassis, CPU, Power Supply, Fan, Sensor, Port, Container,
Module
Relative Position Contains the relative position of this component among other components
in the same index range (e.g. index 40014002, etc.)
Name Name of component

Possible values (according to component type):
<device-name> Chassis
CPU
PS-AC/DC <n>
PS-AC <n>
PS-DC <n>
Fan <n>
Temperature Sensor <n>
External Clock
ETH Port [<slot>/]<n>
MNG Port
RS-232 Control Port
Time of Day Port
Mini BNC
External Clock Port
HW Rev Hardware version (relevant only for chassis)
SW Rev Software version (relevant only for chassis)
FW Rev Firmware version (relevant only for chassis)
Serial No. Serial number (blank if unknown for component)
MFG Name Manufacturer name (blank if unknown for component)
Model Name Model name (blank if unknown for component)
Alias Alias name for component
Asset ID Identification information for component
FRU Indicates whether this component is a field replaceable unit that can be
replaced on site.
For ETX2i this is normally true only for the chassis, and for the dual power
supplies.
ETX2i Inventory 10-15

Processor Processor name
Possible processors:
Intel Atom Rangeley C2558
Intel Atom Rangeley C2758
Cores Core size
Possible values:
4 Quad
8 Octal
RAM RAM volume

8 GByte
HD Type Hard Drive type

SSD M2.0 format
HD Volume 128 GByte
Setting Administrative Inventory Information

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

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

component the alias.
Note: Configuring the alias is
meaningful only for the chassis
component. It can be used by a
network manager as a
non-volatile identifier for the
device.
Assigning user-specific asset identifier asset-id <id> Using no before asset-id

to the component (usually for removes the asset ID.
removable physical components)
Assigning vendor-specific serial serial-number <string> Using no before serial-number

number to the component removes the serial number.

Examples
To display inventory summary for ETX2i:
ETX-2i# configure system
ETX-2i# config>system# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW Ver
-----------------------------------------------------------------------------
1001 Chassis ETX-2i 0.1/ 6.4 5.0.0.0.0.36
4001 Fan Fan 1
4002 Sensor Temperature Sensor 1
4003 Power Supply PS 1
7001 Port Time of Day Port
7002 Port Mini BNC
7003 Port External Clock Port
7004 Port RS-232 Control Port
7005 Port MNG Port
7006 Port ETH Port 0/1
To display inventory information for ETX2i port 0/1:

ETX-2i>config>system# inventory 7006
ETX-2i>config>system>inventory(7006)# show status
Description : ETX-2i Ethernet Port
Contained In : 1001
Physical Class : Port
Relative Position : 6
Name : ETH Port 0/1
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : False
To display inventory summary for ETX2i with VDSL module:

ETX-2I>config>system# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW
Ver
-----------------------------------------------------------------------------
1001 Chassis ETX-
2I 0.1/ 5.9.1(0.22) 5.0.0.0.0.62
3001 Container Slot 1
3002 Container Slot 2
4001 Fan Fan 1
ETX2i Inventory 10-17


4003 Power Supply PS-AC 1
5001 Module VDSL-MODULE ACB 1.00(UHZ.0)b10 1.2
5006 Port PCS PORT 1
7001 Port External Clock Port
7003 Port MNG Port
8001 CPU CPU
To display inventory information for ETX2i VDSL module:

ETX-2I>config>system# inventory 5001
ETX-2I>config>system>inventory(5001)# show status
Description : VDSL-MODULE
Contained In : 0
Physical Class : Module
Name : VDSL-MODULE
HW Ver : ACB
SW Ver : 1.00(UHZ.0)b10
FW Ver : 1.2
Serial Number : 1505250004
MFG Name :
Model Name : ETX-M/VDSL-ISDN
Alias :
Asset ID : Put your string here
FRU :
To display inventory summary for ETX-2i-B with x86 Rangeley card:

ETX-2i-B# configure system
ETX-2i-B>config>system# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW
Ver
-----------------------------------------------------------------------------
1001 Chassis ETX-2IB-
10x1G 0.0/A 5.8.0(0.29) 5.2.B.
0.0.6
4001 Fan Fan 1
4003 Power Supply PS 1
7002 Port MNG Port
8001 CPU CPU

To display inventory information for chassis:

ETX-2i>config>system# inventory 1001
ETX-2i>config>system>inventory(1001)# show status
Description : ETX-2i Ethernet Port
Contained In : 1001
Physical Class : Port
Name : ETH Port 0/1
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Model Name :
Alias :
Asset ID :
FRU : False
TBD
Intel Atom : C2558/2758
Quad/Octal Core
Core Frequency : 2.4GHz
Volume : 8 GByte
HD Type : SSD M2.0/2.5
HD volume : 128 GByte w/wo PLP
10.7 Licensing
Some features require a license to be enabled before the feature can be
configured.
The following licenses are available:
TWAMP
Traffic Management Fault Propagation (TMFP)
SFP+ 10GbE Rate (ETX-2i-10G) licenses:
sfp-plus-factory-10g-rate activated by RAD operations only (not by
users), in order to set SFP+ ports as 10GbE, according to the ordering
option
sfp-plus-10g-rate (two or four-port) license that users can purchase
from RAD to upgrade two or four SFP+ 1GbE ports to 10GbE.
Applicable Products
SFP+ 10GbE rate licenses are relevant for ETX-2i-10G only.
ETX2i Licensing 10-19

Benefits
The license mechanism enables fewer software version variants to be produced.
Also, it can be used to track licensed feature usage.
Factory Defaults
By default, feature licenses are disabled.
A feature that requires a license can be configured only if the feature license is
enabled.
For backward compatibility, in the event that a feature was defined as requiring a
license after having already been released without a license in a previous
software release, the feature configuration is allowed if it was done in a release
that did not require a license. In this case, a command enabling the license is
automatically added to the running-config file.
If ETX2i loads a configuration file that configures a feature requiring a license
when the license is not enabled, the device rejects that features configuration if
the configuration file was created by a software version that requires a license.
Fault Propagation Event Manager License

Use of standard fault propagation features does not require a license. However,
use of enhanced Fault Propagation Event Manager actions, such as shaper-swap
(for changing queue block shaper rate) and policer-swap (for changing flow
policer rate), as well as use of enhanced triggers, requires an enabled Traffic
Management Fault Propagation (TMFP) license.
SFP+ 10GbE Rate License

ETX-2i-10G devices have up to four SFP+ ports with each ports rate
preconfigured to 1GbE or 10GbE, according to the specific ordering option. RAD
operations activates the sfp-plus-factory-10g-rate license to upgrade the SFP+
ports defined as 10GbE in the ordering option.
In the case that the ordering option specifies four 10GbE SFP+ ports, sfp-plus-
factory-10g-rate sets all SFP+ Ethernet ports to 10GbE, and sfp-plus-10g-rate
license is not available.
In the case that the ordering option specifies two 10GbE SFP+ ports,
sfp-plus-factory-10g-rate sets SFP+ Ethernet ports 1 and 2 to 10GbE.
The set sfp-plus-factory-10g-rate license is saved in the Statuses file (and not in
the Configuration file).
It is possible to upgrade the SFP+ ports (two or four) that are not set to 10GbE
by the ordering option, using the two-port or four-port license provided by RAD.
If two SFP+ ports are set to 10GbE rate according to the ordering option, only
SFP+ ports 3 and 4 can be configured to the 10GbE rate using the two-port
license.
10-20 Licensing ETX2i

If no SFP+ ports are set to 10GbE rate according to the ordering option, any
two SFP+ ports can be configured to the 10GbE rate using the two-port
license.
It is not possible to downgrade to 1GbE, a port that is set to 10GbE according to
the ordering option.
If at any stage, a device returns to its factory default settings, the
sfp-plus-factory-10g-rate license remains (as it is saved in the Statuses file).
However, the user-configurable sfp-plus-10g-rate license is deleted.
Configuring Licenses
The ETX2i TWAMP, enhanced Fault Propagation Event Manager features, as well
as the SFP+ Ethernet port rate upgrade to 10GbE, require a license.
Traffic Management Fault Propagation (TMFP) license and TWAMP license in a VNF
(not in a device) are protected by a hardcoded password only known to you.
Configuration of the enhanced FP Event Manager or TWAMP (in VNF) features
requires you to enable the respective password-protected licenses.
The SFP+ Factory 10G Rate license is set in the factory. You cannot enable or
disable it, but can view its status and whether it is in use.
To enable licenses:
1. Navigate to admin license.
The admin>license# prompt is displayed.
Enabling TWAMP license in license-enable twamp

device
Enabling TWAMP license in license-enable twamp password hardcoded password assigned to the device
VNF <password> [hashed] hashed If this option is specified, the device assumes the
Enabling Traffic license-enable tmfp <password> entered password is hashed. If not specified, the device assumes
Management Fault [hashed] the password is plain text (non-ecrypted), and if correct, hashes
Propagation (TMFP) license the password, and saves the hashed result in the license hard
password feature.
Enabling SFP Plus 10g rate license-enable sfp-plus-10g-rate amount number of SFP+ ports that can be upgraded to 10GbE
license <amount> Possible values: 2, 4
ETX2i Licensing 10-21

Disabling license no license-enable <feature> feature licensed feature

Possible values:
sfp-plus-10g-rate
tmfp
twamp
Notes:
You can disable a license, provided running-config does not
contain a configuration that is prohibited without a license.
You can disable the TMFP license, provided enhanced Fault
Propagation Event Manager actions have not been configured.
You can disable the TWAMP license, provided TWAMP entities
have not been configured.
Viewing License Status Summary

You can generate a summary of all the feature licenses in the device.
Example
This example displays the license summary.
ETX-2i-10G>admin>license# show summary
Feature Status Amount In Use
-----------------------------------------------
SFP+ 10G Rate Enabled 2 1
SFP+ Factory 10G Rate Enabled 2 2
TWAMP Disabled -- --
TMFP Enabled -- Yes
Table 10-3. License Summary Parameters
Feature Feature name
Possible values:
SFP+ 10G Rate
SFP+ Factory 10G Rate
TMFP (Traffic Management Fault Propagation)
TWAMP
Status License status
Possible values: Enabled, Disabled
Amount License amount
Possible values:
-- : not applicable (for TMFP and TWAMP)
<1-4>: number of 10GbE licensed SFP+ ports
10-22 Licensing ETX2i

In Use Indicates whether or not the license is in use.
Possible values:
-- : not applicable (for disabled license)
Yes/No: indicates whether or not enabled TMFP or TWAMP license is in use
<1-4>: number of 10GbE licensed SFP+ ports in use. The feature is
considered in use if the port is configured as 10GbE and enabled in
running-config.
The following table lists messages generated by ETX2i when a configuration
error is detected.
Message Description
License needed by running configuration You attempted to disable the license for a feature that is
configured in the device running configuration.
License required You attempted to configure a feature that requires a license,

and the license is disabled.
Wrong password You failed to set the correct password for the device.
10.8 Login Banner
Applicable Products
Defining Login Banners

You can define a banner to be displayed before the login prompt for user name,
as well as a banner to be displayed following successful login. You can define the
pre-login banner using the CLI command login-message, and the post-login
banner using the CLI command announcement. A banner file can also be used to
define a pre-login banner, provided it is supported in the device. Although the
banner file is maintained for backward compatibility, it is recommended to use a
CLI command to define the pre-login banner. Note that a device cannot
simultaneously support a banner file and banner command.
Note If you are accessing ETX2i via SSH, the banner is printed between the user name
prompt and the password prompt.
ETX2i Login Banner 10-23

Defining Login Banners via CLI Commands

You can define a banner to be displayed before login, as well as another banner
to be displayed following login.
Pre-login and post-login banner messages must satisfy the following:
Message must be enclosed in single quotation marks.
Pressing <Enter> before entering a closing quotation mark, results in the
device displaying the warning message:
Enter message. End with the single quotation character ().
A message that spans multiple lines is interpreted as if it were written in one
line; <cr> and <lf> between lines in the configuration file or command are
ignored.
A message can contain printable characters, as well as the following special
characters (only relevant for CLI; from SNMP, these characters should be
entered normally):
\n new line
\t horizontal tab
\ single quotation mark
\\ backslash
Usage of special characters reduces the maximum number of printable
characters that the banner can contain. For example, if the banner contains
\n, up to 1998 additional printable characters can be used.
The banner can be up to 2000 characters (including the escape / characters).
If you try to configure a longer banner, the device prints the following CLI
error: Banner may not exceed 2000 characters.
To configure a pre-login banner:

2. Type login-message <message>, enclosing the message in quotes.
At the next login, this pre-login banner is displayed.
If a bannertext file already exists in the device, the device rejects the
command and displays the CLI error message:
Cannot configure banner while bannertext file exists
Note Type no login-message to remove a previously configured pre-login banner.
To configure a post-login banner:

2. Type announcement <message>, enclosing the message in quotes.
After the next login, this post-login banner is displayed.
10-24 Login Banner ETX2i

Note Type no announcement to remove a previously configured post-login banner.
You can display the banners configured for ETX2i by navigating to the device
level and entering info. For example:
ETX-2i# info
version "3.01A14" sw "5.9.1(0.08)"
configure
echo "System Configuration"
# System Configuration
system
login-message 'Authorized Users Only'
announcement 'Successful Login!'
exit
The configured banners are displayed before and after login, as shown below.
Authorized Users Only
user>su
password>****
Successful Login!
ETX-2i#
Defining Pre-Login Banner Using a Banner File
To define the banner using a banner file:

1. Create a text file called banner-text that contains the banner to display.
Notes The banner must contain only printable ASCII characters (0x200x7E), <Enter>
(0x0D), <Line Feed> (0x0A), and <Tab> (0x09)
The banner can contain up to 2,000 characters.
2. Transfer the file banner-text to ETX2i.

At the next login, the banner is displayed.
If the device already contains the pre-login CLI command login-message,
the device rejects the banner-text file download and displays the CLI
error: Cannot load bannertext file while login-message is configured.
You can display the banner defined for ETX2i by navigating to the file level and
entering show banner-text, as shown in the example below.
ETX-2i# file
ETX-2i>file# show banner-text
******* Authorized users only *******
Given the above banner file, the banner is displayed before login, as shown
below.
******* Authorized users only *******
user>
ETX2i Login Banner 10-25

10.9 Reset
Note
This section describes how to reset using CLI commands. You can also reset the
device to its factory defaults or user configured defaults by pressing the push
button on the front panel. For details, refer to the description on resetting the
device in the Operation chapter.
ETX2i supports the following types of reset:

Reset to factory defaults
Reset to user defaults
Overall reset (restart) of the device
Reset x86 card of D-NFV-enabled devices
Note You can request that the active software pack be confirmed after the next reboot
of ETX2i. Refer to the description of installing software in the Software Upgrade
chapter for details.
Applicable Products
This feature is applicable to all ETX2i products, with the exception that reset of
the x86 card is applicable only to ETX2i with D-NFV option.
Resetting to Factory Defaults

ETX2i can be reset to its factory defaults using either of the following
commands:
factory-default for customer use
factory-default-all for use by RAD Operations personnel prior to releasing
the device for shipment, in order to revert the device to its prior-to-shipment
state
The ETX-2i-10G Four SFP+ Ethernet Ports license is not affected by the device
reset to factory defaults.
The factory-default and factory-default-all commands have the following
differences:
factory-default always reloads the device with factory-default-config.
factory-default-all reloads the device with user-default-config, if it exists;
otherwise, with factory-default-config.
factory-default only deletes startup-config.
factory-default-all clears the log files and deletes most files, with the
exception of factory-default-config, user-default-config, licenses, banner,
software, mac-table, pm (including the legacy statistics collection file),
db-schema, and db-config. It also resets file creation times in the file system.
10-26 Reset ETX2i

factory-default-all resets the snmpEngineBoots parameter to 1. This

parameter counts the number of times the SNMP engine was restarted, and
is maintained throughout reboots to prevent replay attacks.
Note It is not recommended for customers to use the factory-default-all command, as

it resets the SNMP object (snmpEngineBoots), which could lead the management
station to assume that the original device was replaced by another impersonating
device, and therefore refusing to communicate with it. In such cases, the
manager must manually delete the device from the map and then redraw it.
Therefore, to avoid issues resulting from the resetting of snmpEngineBoots, it is
recommended to use instead user-default or factory-default and then manually
delete unneeded files and clear logs, as required.
To reset ETX2i to factory defaults:

1. At the admin# prompt enter:
factory-default
A confirmation message is displayed:
Current configuration will be erased and device will
reboot with factory default configuration. Are you sure?
[yes/no]
2. Enter yes to confirm the reset to factory defaults.
The factory-default-config file is copied to the startup-config file. The
unit resets, and after it completes its startup the factory defaults are
loaded. If a startup-config confirm request was active, it is canceled.
To reset ETX2i to factory defaults and revert the device to its prior-to-shipment
state:
factory-default-all
The device will delete its entire database and reboot.
Are you sure? [yes/no]
2. Enter yes to confirm the reset to factory defaults with configuration and
counter reset.
The configuration and counter reset explained above is performed, the
unit resets, and after it completes its startup the factory defaults are
loaded. If a startup-config confirm request was active, it is canceled.
Resetting to User Defaults

You can use the user-default command to reset ETX2i to the configuration
stored in user-default-config, a file which contains user default parameters that
are usually different from RADs factory default parameters.
To reset ETX2i to user defaults:

user-default
ETX2i Reset 10-27


Current configuration will be erased and device will
reboot with user default configuration. Are you sure?
[yes/no]
2. Enter yes to confirm the reset to user defaults.
The user-default-config file is copied to the startup-config file. The unit
resets, and after it completes its startup the user defaults are loaded. If a
startup-config confirm request was active, it is canceled.
Restarting the Unit

If necessary, you can restart ETX2i without interrupting the power supply.
Note Rebooting the ETX2i device does not reset the x86 card.
To restart ETX2i:
reboot
Device will reboot. Are you sure? [yes/no]
2. Enter yes to confirm the reset.
The unit restarts.
Resetting the x86 Card

When restarting the ETX2i unit using admin reboot, the x86 card does not
reset. This section describes how to reset the x86 card only.
Note You can reset the x86 card from the x86 screen only (chassis ve-module).
To reset the x86 card:

2. Enter:
reset
If the x86 card is up and running, it resets.
10-28 Reset ETX2i

10.10 Tech-Support Commands

ETX2i supports a show tech-support command, which you can use to display on
the terminal or store in a script file a predefined series of CLI commands, such as
general device status and statistics.
Applicable Products
Benefits
You can view or save in a file general device status and statistics.
Factory Defaults
By default, the show tech-support command is predefined with the following
commands in order:
show configure system system-date
show configure system device-information
show configure system memory-details
show configure system buffers
show configure system summary-inventory
show file sw-pack
show file copy
show configure port summary
show configure service
show configure flows summary details
show configure oam cfm summary
show configure pwe summary
show configure system clock domain1 status
show configure protection erp-summary
show configure router 1 arp-table
show configure router 1 routing-table
show configure management users-details
show configure reporting active-alarms
ETX2i Tech-Support Commands 10-29

When the tech-support command is invoked, its output is displayed on your
terminal or stored in a script file called script-result (, which can afterwards be
displayed or downloaded).
For each command, the following is displayed:
A timestamp formatted <date> <time> UTC {+|-}<hours>:<minutes>; for
example: 2015-05-35 11:10:09 UTC +02:00
The executed command
The command output, including errors and other messages, provided that the
command was invoked with the terminal argument (If the file argument is
invoked, the command output is stored in a file instead of being displayed on
the CLI terminal.)
Unlike other commands, the output is sent to the screen continuously, without
pausing after each page.
The CLI prompt does not return until all commands included in the script are
executed, or you stop the execution.
The terminal inactivity timer does not decrease while the script is being executed,
so the terminal remains open even if it takes a long time.
The script-result file is automatically cleared each time the show tech-support
command is invoked.
Showing the Tech-Support Commands

To show the tech support commands:
2. At the config>system# prompt, enter show tech-support [file|terminal].
The commands and their output are displayed.
10-30 Tech-Support Commands ETX2i

Chapter 11
Monitoring and
Diagnostics
The following are described in this chapter:
In-Service ICMP Echo Ping Test
OAM CFM (Connectivity Fault Management)
OAM EFM
TWAMP
Quality of Service (QoS)
Layer-3 Service Activation Test
RFC-2544 Testing
Syslog
Y.1564 Ethernet Service Activation Test
Port Mirroring
Performance Management
Detecting Problems
Handling Alarms and Events
Troubleshooting
Performing Diagnostic Tests
Frequently Asked Questions
Technical Support
11.1 In-Service ICMP Echo Ping Test

In many cases, users want to be able to ping the Layer-2 EVC at the device for
diagnostic purposes. The in-service ICMP Echo ping test provided by ETX-2i
enables you to activate a simple command to send a ping and check the
connectivity across Layer-2 service paths for diagnostic purposes.
Applicable Products
ETX-2i In-Service ICMP Echo Ping Test 11-1

Chapter 11 Monitoring and Diagnostics Installation and Operation Manual
Benefits
This test requires a single CLI command to perform a simple connectivity check
across Layer-2 service paths, without the need for configuration of a full TWAMP
controller and responder.
Layer-2 Ether-Access devices have the ability to initiate a connectivity test, and
also respond to in-service ping requests sent over Layer-2 services to a
configured IP address.
The in-service ICMP Echo ping test pings the Layer-2 EVC of the device from the
flow level. The in-service ping includes a mechanism to enable performing a
connectivity test across the flow inside the device, by configuring ICMP packets
entry-point to the flow, either at the flow ingress or egress. The in-service ping
runs independently of working routers.
The in-service test requires that the devices be activated in two modes:
Generator Device sends ping messages.
Responder Device receives ping messages and sends a reply.
A single ICMP Echo instance is supported Generator or Responder.

In-service ICMP Echo is supported in the following topologies:
PtP E-line service
MP to MP E-LAN (bridge) services
MP to MP (or P to MP) E-Tree services
PtP E-line Service

IPv4 only
Two configurable probing scopes:
Up In-service ping request/response packets are injected at

the ingress port of the service and mimic frame traverse of
the UNI/NNI flow chain.
Down In-service ping request/response packets are injected

directly at the egress port of the service using the highest
priority queue.
11-2 In-Service ICMP Echo Ping Test ETX-2i

Installation and Operation Manual Chapter 11 Monitoring and Diagnostics
ETX-2
Ping VRF
TWAMP
Router
Inte rfa ce
Ping
ETH Policer ETH

Port Port
Figure 11-1. ICMP Echo PtP E-Line Services
MP to MP E-LAN (bridge) Services

IPv4 only
Where bridge is used, in-service ping probing-scope is injected to the bridge
only, and generated towards any port connected to the specific VPN.
ETX-2
Ping VRF
Router
Inte rfa ce
Bridge
Port
Ping
ETH ETH
Port Bridge Port
Figure 11-2. ICMP Echo Bridge Services
MP to MP (or P to MP) E-Tree Services

IPv4 only
Where bridge is used, in-service ping probing-scope is injected to the bridge
only, and generated towards any port connected to the specific VPN.
The internal bridge port from which the in-service ping-request is sent must
be configured as root for the given Layer-2 VPN. The responder listens to in-
service ping-requests received from the root bridge port on the specified
VPN and replies with an in-service ping response on the same root bridge
port.
Configuring the In-Service ICMP Echo Ping Test

To configure the in-service ICMP Echo ping test:

1. Configure the in-service ping response at the device that responds to the
ping-request packets with ping-response packets. You can configure the IP
stack to start and listen to ping-requests being sent over a particular flow,
targeted to a provisioned IP address.
2. Configure the in-service ping request at the device generating the ping
test.
It is not possible to save the in-service ping responder configuration. It is erased
on reset, and does not appear in the info command.
When you invoke the commands, a temporary IP interface is created on the
device, as well as a routing entry in the static-route table. When the test has
completed, all IP context on the generator side that is related to the test is
cleared; the IP context on the responder side must be cleared manually.
Configuring In-Service ICMP Echo Ping Response
Note In PtP mode, a service (flows) with corresponding classification must exist on the
requested ingress port prior to in-service ping-response commands generation;
it is optional to configure an opposite matching flow. In the case that an
opposite matching flow does not exist, the service ping works in down scope
(default) without any warning.
To configure an in-service ping response:

1. Navigate to ETX-2i configure flows.
The ETX-2i>config>flows# prompt is displayed.
2. Type the following command, using the parameters described in Table 11-1:
service-ping-response {local-ip <local_ip_addr_and_subnetmask>} {next-hop
<next_hop_ip_address>} {egress-port <egress_port>|bridge <bridge_id>} [vlan
< vlan_id>] [inner-vlan <inner_vlan_id>] [p-bit < p_bit_id] [inner-p-bit
<inner_p_bit_id>][probe-scope <up|down>]
At any time, you can configure the device to cease listening to in-ping-requests,
by typing the command:
no service-ping-response
The device clears any generated command context (the local IP address and
routing entry).
Note Invoking no service-ping-response terminates the command that was initiated in

the same data-base session or in a different database session (same user or
different user).
Configuring In-Service ICMP Echo Ping Request
Note In PtP mode, a service (flows) with corresponding classification must exist on the
requested ingress port prior to in-service ping commands generation; it is
optional to configure an opposite matching flow. In the case that an opposite
matching flow does not exist, the service ping works in down scope (default)
without any warning.

To configure an in-service ping request:

1. Navigate to ETX-2i configure flows.
The ETX-2i>config>flows# prompt is displayed.
2. Type the following command, using the parameters described in Table 11-1:
service-ping {local-ip <local_ip_addr_and_subnetmask>} {dst-ip
<destination_ip_addr>} {next-hop|<next_hop_ip_address>} {egress-
port<egress_port>|bridge<bridge_id>} [vlan < vlan_id] [inner-vlan
<inner_vlan_id>] [p-bit< p_bit_id] [inner-p-bit <inner_p_bit_id>] [probe-scope
<up|down>] [number-of-packets<number_of_packets>] [payload-
size<number_of_bytes>]
The next in-service ping request is transmitted after at least one second (hard-
coded) has elapsed from the transmission of the previous in-service ping
request, provided the previous in-service ping response packet has been
received. If the in-service ping response packet has not been received within
two seconds since it was sent (hard-coded timeout), the ping-packet is declared
lost, a message is echoed back to your-screen, and the next in-service ping
request is immediately transmitted.
The in-service ping test is automatically terminated after the transmission of the
number-of-packets in the in-service ping request and the reception of the
corresponding echoes.
You can terminate the in-service ping test before the number-of-packets have
been exhausted by clicking Ctrl-C or by typing the command:
no service-ping
The initiator interrupts the current in-service ping test and returns the following
termination message and test summary:
Ping is terminated by user:
<num_packet_tx> packets transmitted. < num_packet_rx> packets
received, <loss_percentage>% packet loss
round-trip (ms) min/avg/max = <rt_min>/<rt_avg>/<rt_max>
Note
Invoking no service-ping terminates the command that was initiated in the same
data-base session or in a different database session (same user or different
user).
Table 11-1. In-Service Ping Parameters
Parameter Description Value
local-ip The temporary IP address provisioned on the Valid IP address and subnet
sender/responder for the duration of the test, mask
combined with subnet-mask [0.0.0.0/32|0:0:0:0::0/128]
dst-ip The IP address to which in-service ping request packets Valid IP address
are destined [0.0.0.0|0:0:0:0::0]
next-hop Next hop to use when destination IP is out of the Valid IP address
source subnet [0.0.0.0|0:0:0:0::0]

egress-port Egress port for PtP services (E-Line). The physical (e.g. ethernet, pcs, or logical-
Ethernet port) or logical (e.g. bridge ID) interface from mac
which the ping request/response exits. Valid attribute
only when bridge parameter is not introduced.
bridge Bridge ID for bridged services (E-LAN/E-Tree service Valid bridge ID

probing). Valid attribute only when egress-port
parameter is not introduced.
vlan Together with egress-interface, defines the flow Possible values: 04094
Default: -1 (untagged)
inner-vlan Together with egress-interface, defines the flow Possible values: 04094
Default: -1 (untagged)
p-bit The service VLAN priority bit used when encapsulating Possible values: 07
the ping packet Default: 0 (untagged)
inner-p-bit The inner-VLAN priority bit used when encapsulating the Possible values: 07
ping packet Default: 0 (untagged)
probe-scope The in-service ping request/response probing mode. up/down

Applicable only for E-Line services, when egress-port is Default: up
selected. Not applicable when user selects bridge.
number-of-packets Number of in-service ping request packets for the test Possible values: 110000
Default: 5
payload-size Payload size of the in-service ping request packets Possible values: 321450
Default: 32
In-Service ICMP Echo Ping Test Results

Echo results (including RTT) are echoed back to the user terminal in a format
similar to the existing ping format.
For example, pinging IP address 172.17.155.83 with number-of-packets = 6 and
payload-size = 32:
Reply from 172.17.155.83: bytes = 32, packet number = 0, time < 10 ms
5 packets transmitted. 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
Examples
The following example illustrates configuring in-service ping test over Eth
services. Layer-2 E-Line service is provisioned between device UNI and NNI.
To configure the responder with an in-service ping response:

exit all

#********* Configure classifier for VLAN 100

configure
flows
match vlan 100
exit
#********* Configure Service between ETH 3 & 4
flow ping_E3toE4
classifier v100
no policer
no shutdown
exit
flow ping_E4toE3
classifier v100
no policer
no shutdown
exit
#*********In-Service Ping ********************************
service-ping-response local-ip 10.10.10.30/24 next-hop

10.10.10.20 egress-port ethernet 4 vlan 100
To configure the generator with an in-service ping request:

exit all
configure
flows
match vlan 100
exit
#********* Configure Service between ETH 3 & 4
flow ping_E3toE4
classifier v100
no policer
no shutdown
exit
flow ping_E4toE3
classifier v100
no policer
no shutdown
exit
#*********In-Service Ping ********************************

service-ping local-ip 10.10.10.20/24 dst-ip 10.10.10.30 next-

hop 10.10.10.30 egress-port ethernet 4 vlan 100 probe-scope
down number-of-packets 5 payload-size 64
The following example illustrates configuring an in-service ping test over bridge
services. Layer 2 E-LAN service is provisioned between device UNI and an
internal bridge port.
exit all
configure bridge 1
vlan-aware
port 1
no shutdown
exit all
configure
flows
match vlan 100
exit
#********* Configure flows between ETH 3 & BP11

flow ping_E03_BP11
classifier v100
no policer
no shutdown
exit
service-ping-response local-ip 10.10.10.30/24 next-hop

10.10.10.20 bridge 1 vlan 100
#*********In-Service Ping ********************************
#*********In-Service Ping ********************************#
Parameter or keyword missing The entered service (outer) Configure a service (outer) VLAN that
or wrong VLAN, does not also populate also populates the customer (inner)
the customer (inner) VLAN in VLAN in the command.
the command.

Invalid parameter value; local-ip The next-hop address does Choose local IP and next-hop IP
and next-hop must belong to not belong to the same addresses in the same network.
the same network network as the sender address
(local IP address).
Invalid parameter value; local-ip The destination IP address Make next hop address equal to the
and next-hop must be equal as belongs to the same network local IP address.
dst-ip belongs to the same as the sender, but the next-
network hop address is not equal to
the local IP address.
11.2 OAM CFM (Connectivity Fault Management)

Ethernet OAM (Operation, Administration, and Maintenance) functions provide
end-to-end connectivity checks and performance monitoring.
Ethernet Connectivity Fault Management (CFM) is a service-level OAM protocol
that provides tools for monitoring and troubleshooting end-to-end Ethernet
services. This includes proactive connectivity monitoring, fault verification, and
fault isolation. CFM uses standard Ethernet frames and can be run on any
physical media that is capable of transporting Ethernet service frames. ETX-2i
also supports performance monitoring per Y.1731.
ETX-2i can act as a Maintenance Entity Group Intermediate Point (MIP) or
Maintenance Entity Group End Point (MEP). If ETX-2i is acting as a MIP, it
forwards OAM CFM messages transparently, responding only to OAM link trace
(LTM) and unicast OAM loopback (LBM).
Applicable Products
Standards
IEEE 802.1ag-D8
ITU-T Y.1731
MEF 36
Benefits
Ethernet service providers can monitor their services proactively and guarantee
that customers receive the contracted SLA. Fault monitoring and end-to-end
performance measurement provide tools for monitoring frame delay, frame
delay variation, and frame loss and availability.
ETX-2i OAM CFM (Connectivity Fault Management) 11-9

OAM enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM
functionality ensures that network operators comply with QoS guarantees,
detect anomalies before they escalate, and isolate and bypass network defects.
As a result, the operators can offer binding service-level agreements.
ETX-2i provides the OAM (CFM) functions listed below in packet-switched
networks:
End-to-end Connectivity Fault Management (CFM) per IEEE 802.1ag:
Continuity check (CC)
Non-intrusive loopback, used to detect loss of bidirectional continuity
Link Trace for fault localization
End-to-end service and performance monitoring per ITU-T Y.1731:
Loss measurement
Delay measurement
OAM Elements
Maintenance entities (ME) that require management are grouped into ME groups
(MEGs, referred to as Maintenance Associations or MAs). The Ethernet OAM
mechanism monitors connectivity in MAs. 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). The following entities are used for monitoring:
Maintenance End Point (MEP) A MEP is both an endpoint of a single MA,
and an endpoint of a separate Maintenance Entity for each of the other
MEPs in the same MA. A MEP generates and receives CFM connectivity
messages and tracks responses.
MEPs are referred to as up MEPs or down MEPs, depending on their location
in the device. Up MEPs reside at bridge ingress and are bound to bridge
ports. These MEPs receive and send CFM PDUs from and to the bridge. Down
MEPs reside at port egress and are bound to physical ports. These MEPs
receive and send CFM PDUs from and to the network.
You can enable or disable (the default) Latching Loopback Function (LLF) for
a down or up MEP, which is configured with Rx and Tx flows (and not
Classification). This enables the MEP to perform simultaneous loopbacks for
different source MAC addresses. When LLF is enabled at the MEP level, the
MEP level responder can work with a third party generator. For example, the
Y.1564 test generator can work with the MEP-level responder having LLF
enabled, eliminating the need to add a Y.1564 test responder.
The OAM packets transmitted by MEPs usually contain a service VLAN ID
(S-tag) and customer VLAN ID (C-tag). However, there are cases where the
user side C-tag is unknown. To handle this case, you can specify for E-line
up MEPs that customer tags are excluded. Maintenance Intermediate Points
(MIPs) are intermediate entities unlike MEPs, which are directional entities
acting as service termination points. There are two types of intermediate
11-10 OAM CFM (Connectivity Fault Management) ETX-2i

entities: service-level and MD-level MIPs. These MIP modes cannot be

activated simultaneously:
Service-level MIPs are defined under the MD level. This type of MIP
inherits its source MAC address from the directly or indirectly attached
physical port. Service-level MIPs respond to link trace messages (LTMs)
and loopback messages (LBMs) whose MD level is equal to the MIP MD
level.
MD-level MIPs are activated per device per MD level (or several MD
levels). When MD-level MIP mode is activated, ETX-2i automatically
creates a MIP for each flow at each physical port, bridge port, and ring
port. This includes the flows that already exist in the system, and the
flows that are created after MD-level MIP mode is activated. Each MIP
inherits its source MAC address from the adjacent port. MD-level MIPs
respond to link trace messages (LTMs) whose MD level is equal to the
MIP MD level.
Services used for performance monitoring of the relevant MEP
Destination Network Elements (Dest NEs) provide performance monitoring
for the relevant service
The following limitations apply to MD-level MIPs:
If an MD-level MIP is configured and a MEP with an equal or higher MD level
is added on a specific flow, the MIP is removed from the flow.
If a MEP with an equal or higher MD level is configured on a flow, an
MD-level MIP cannot be provisioned for the flow.
MD-level MIPs are not provisioned for flows connected to an MEF-8 PW SVI,
ETP subscriber/transport port, or router interface.
MD-level MIPs can be defined only over flows with the classification: Single
VLAN, or Single outer + single inner VLAN.
MD-level MIPS do not reply to loopback messages (LBMs).
MEPs that are created at the same MD level as the MIPs do not support
multicast loopbacks.
The MAC addresses used in the OAM CFM entities are as follows:
Down MEPs use the MAC address assigned to the port bound to the MEP.
Up MEPs use the MAC address assigned to the port to which the relevant
bridge port connects.
MIPs use the MAC address assigned to the port they are bound to.
OAM Performance Monitoring

The OAM PM functionality complies with ITU-T Y.1731 and MEF 36. ETX-2i
provides loss and delay measurements, as well as event reporting. ETX-2i
supports the following measurement methods:
User data This method measures user data and CCM messages. You can
specify that this method measure only green packets (color-aware loss
measurement); additionally you can specify that it does not measure CCM
messages.

In the case of color-aware loss measurement, the following statistic

counters are based on green packets only:
Forward/backward Tx/Rx frames
Forward/backward Frame Loss Ratio (FLR)
Forward/backward Availability/Unavailability
Synthetic This method measures DM frames. It is recommended when
working with devices that do not count user data frames.
LMM synthetic This method measures synthetic frames as well. It is
recommended for working with ETX-201A/202A.
SLM synthetic This method measures synthetic SLM/SLR frames.
Note OAM SLM is handled in the hardware.
While working in a Bridge application, not learned user data packets, and
multicast and broadcast transmitted frames are counted several times.
OAM Packet Handling

This section describes how an OAM packet is handled in the following:
MEP CCM
MEP LB/LT
MEP LM/DM
MIP
For each of these modes, a description is provided as to how packets are
discarded and counted in the port counters, per port, under the OAM Discarded
counter, at the following levels:
Low MD level Packets OAM level is lower than the defined MEPs level.
Equal MD level Packets OAM level is equal to the defined MEPs level.
High MD level Packets OAM level is higher than the defined MEPs level.
MEP CCM
Lower MD-Level:
Multicast / unicast My-MAC / unicast different MAC
Packet received from Active side > MEP defect
Cross Connected CCM (mismatch; unexpected MD level): On
Packet received from Passive side > OAM discarded on port.
Equal MD-Level:
Multicast / unicast My-MAC
Packet received from Active side > OK
Packet received from Passive side > OAM discarded on port
Unicast different MAC (not My-MAC DA)

Packet received from Active side > DA MAC is not analyzed. No discard,
no alarm MEP in OK status.
Higher MD-Level:
Multicast /unicast different MAC
Packet received from both sides > considered as user data
Unicast My-MAC
Packet received from both sides > OAM discarded on port
MEP LB/LT
Lower MD-Level:
LB/LT multicast / unicast My-MAC / unicast different MAC
Equal MD-Level:
Multicast / Unicast My-MAC (LB/LT)
LB
LT
Packet received from Active side > discarded by CPU; no indication
Higher MD-Level:
Unicast My-MAC (relevant to LB only)
MEP LM/DM
Lower MD-Level:
Multicast / unicast My-MAC / unicast different MAC
Equal MD-Level:
Multicast / unicast My-MAC


Higher MD-Level:
Unicast My-MAC
MIP
Note Not relevant to global MIP.
Lower MD-Level received packet:

Multicast / unicast different MAC > considered as user data
Unicast My-MAC > OAM discarded on port
Equal MD-Level received packet:
Linktrace (LT) (always MC DA)
Answer LTR. Forward LTM, if not HIT
Loopback (LB)
MC -> considered as user data
Unicast My-MAC> answer LBR
Unicast different MAC -> considered as user data
Other OAM packet
MC -> considered as user data
Unicast My-MAC > OAM discarded on port
Unicast different MAC -> considered as user data
Higher MD-Level received packet:
Unicast My-MAC
Automatic SLM and LMM Responders

As soon as a MEP becomes active (no shutdown), the ETX2i family supports
automatic SLM and LMM responders. This is the default; no configuration is
required to activate the auto SLM or auto LMM mode.
A MEP answers SLM packets with SLR even if the service (p-bit) and session
(dest-ne) are not configured.
A MEP answers LMM packets with LMR even if this session (dest-ne) is not
configured.

SLM and LMM learned sessions are supported up to the scale supported in
the specific ETX-2i device. The sum of the learned session and configured
session cannot exceed the device session limit.
Preconfigured and learned sessions can coexist on the same MEP or on the
same device.
A sessions aging time is 10 minutes, meaning that when there is no SLM or
LMM received for a learned session for 10 minutes, the session is deleted.
MEP LOC deletes all learned sessions.
MEF46 Latching Loopback

MEF46 enables associating a Latching Loopback State Machine (LLSM) with a
MEP. You can enable or disable the Latching Loopback functionality (LLF) per
MEP, which is configured with Rx and Tx flows (and not Classification). By
default, LLF is disabled. LLF is supported in either a service down or up MEP that
is connected to a physical or LAG port. When LLF is enabled, the operational
status of the MEP is set to mef46Loop. Latching Loopback is supported in all
network topologies that support Y.1564, i.e. E-Line, E-LAN, and E-Tree.
Factory Defaults
By default, there are no MDs, MAs, or MEPs.
The OAM CFM general parameters have the following default configuration.
alarm-type legacy
availability delta-t 1 n 10 forward-thr 50 Forward threshold and backward threshold

backward-thr 50 default values are 50% (unit is %).
multicast-addr 01-80-C2-00-00-30
When a maintenance domain is created, it has the following default

configuration.
proprietary-cc no proprietary-cc Standard OAM protocol
md-level 3
name string "MD<mdid>" For example, the default name for

maintenance domain 1 is MD1.
When a maintenance association is created, it has the following default

configuration.
ccm-interval 1s Continuity check interval is 1 second.
interface-status-tlv interface-status-tlv

name string "MA<maid>" For example, the default name for

maintenance association 1 is MA1.
When a maintenance endpoint is created, it has the following default

configuration.
ais no ais
bind no bind
ccm-initiate ccm-initiate Initiate continuity check messages.
ccm-priority 0
client-md-level 4
customer-tags-excluded no customer-tags-excluded
dest-addr-type ccm multicast Destination address type for CCM

pm unicast messages multicast
Destination address type for performance
measurement messages unicast
direction down
mef46-ll no mef46-ll
queue fixed 0 block 0/0
When a service is created, it has the following default configuration.
delay-threshold 1000
delay-var-threshold 1000
classification priority-bit 0
dmm-interval 1s
lmm-interval 1s
When a destination NE is created, it has the following default configuration.
delay two-way data-tlv-length 0
delay-measurement-bin no delay-measurement-bin
delay-var-measurement-bin no delay-var-measurement-bin
loss single-ended user-data

remote mac-address
00-00-00-00-00-00
Configuring OAM CFM

To configure the service OAM:
1. Configure general OAM parameters.
2. Add and configure maintenance domain(s) (MD).
3. Configure maintenance associations for the added MDs.
4. If ETX-2i is acting as a MIP, then configure the necessary MIPs.
5. If ETX-2i is acting as a MEP:
a. Configure MA endpoints, referred to as MEPs.
b. Configure MEP services.
c. Configure Destination NEs.
Configuring General Parameters

You can define general OAM CFM parameters, as well as displaying OAM CFM
information.
To define general OAM CFM parameters:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
Defining whether legacy alarm-type { legacy | soam } legacy OAM alarm names remain the same
alarms or newer alarms as in previous versions.
are used soam OAM alarm names change as
follows:
defErrorCCM MEP level alarm: invalid
CCM received with CCM Interval that has
not yet timed out; replaces mismatch
defMACstatus RMEP level alarm: Defect
reported by interface or port status TLV
defRDICCM RMEP level alarm: RDI
(remote defect); replaces rdi
defRemoteCCM RMEP level alarm: Loss
of continuity (LOC); replaces loc
defXconCCM MEP level alarm:
Unexpected CCM received from MAID or
lower MD level; replaces mismatch

Defining parameters for availability [delta-t {1 | 2 | 3 | 4 | 5 | 6 | 10 These parameters define availability

availability calculations | 12 | 15 | 20}] [n <n>] performance measurement, based on frame
[forward-thr <forward-thr-percents>] loss during a sequence of consecutive small
[backward-thr <backward-thr-percents>] time intervals:
delta-t time interval (in seconds)
n number of consecutive small time
intervals over which to measure
availability
forward-thr Forward frame loss ratio
threshold, for which unavailability occurs
if exceeded (%)
forward-thr = 0 recommended for
measuring low levels of loss
backward-thr Backward frame loss
ratio threshold, for which unavailability
occurs if exceeded (%)
forward-thr = 0 recommended for
measuring low levels of loss.
Configuring device-level md-level-mip <md-level-list>

MIP
Configuring measurement-bin-profile <name> See Configuring Measurement Bin Profiles

measurement bin for more details.
profiles
Configuring the MAC multicast-addr <mac-address>

address used in
multicasts
Displaying information show mips

on MIPs
Displaying OAM CFM show summary See Viewing OAM CFM Information for more
information such as details.
MDs, MAs, MEPs, etc.
Configuring Measurement Bin Profiles

You can define measurement bin profiles to define sets of threshold ranges (in
microseconds (s)) for displaying delay measurements in destination NEs. See
Configuring and Viewing Delay Measurement Bins for a configuration example.
To define measurement bin profiles:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
Enter the measurement bin profile level by typing the following:
measurement-bin-profile <name>

The prompt config>oam>cfm>measurement-bin-prof(<name>)# is

displayed.
2. Specify the thresholds (single value, or values separated by commas) in
microseconds (s).
thresholds <thresholds-list>
Each value is used as the upper range of a set of thresholds, up to
5,000,000. For instance, entering thresholds 500,1000,15000 results in this
set of threshold ranges:
0500
5011,000
1,00115,000
15,0015,000,000
Viewing OAM CFM Information

You can display OAM CFM information by typing show summary, as shown in the
following.
ETX-2i# configure oam cfm
ETX-2i# config>oam>cfm# show summary
md slot/ classifi admin mep
ok/total
md/ma/mepid md/ma name lvl port cation status def r.meps
001/001/001 MD1/MA1 3 eth1 100 enable off 1/1

002/002/8191 1234567890123456789012 3 eth1 0 disable
34567890/1234567801234
002/005/123 1234567890123456789012 3 eth1 100/ enable off 0/2
34567890/155 200
002/006/101 1234567890123456789012 3 eth3 untagged enable off 0/3
003/001/001 /iccname 4 eth1 100.1 enable off 0/1
004/001/001 20-64-32-AB-CD-64 120/ 0 eth1 4000 enable off 0/1
MA1
004/002/001 20-64-32-AB-CD-64 120/ 0 eth1 3000/ enable off 0/3
12345678901234567890123
Configuring Maintenance Domains

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

To delete a maintenance domain:

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

association for the MD Associations
Specifying the maintenance md-level <md-level> The allowed range for md-level is 07.
domain level Note: If prestandard OAM protocol is
being used, the only allowed value for
the maintenance domain level is 3.
Note: When md-level is set to 7, client
md-level, even if configured, becomes
meaningless, as it must have a higher
value than md-level but cannot exceed 7.
Specifying the name format name string <md-name-string> Maximum length of md-name-string is
and name of the name dns <md-name-string> 43 characters.
maintenance domain Maximum combined length of
name mac-and-uint <md-name-mac>
<md-name-uint> md-name-string and ma-name-string
(maintenance association name) is
no name
48 characters.
Format mac-and-uint Specify
md-name-mac as xx-xx-xx-xx-xx-xx,
and md-name-uint as an unsigned
integer decimal number (065535).
If prestandard OAM protocol is being
used, the maintenance domain must
have no name (use command no
name).
Specifying the OAM no proprietary-cc Use no proprietary-cc for standard

protocol type proprietary-cc OAM protocol.
Use proprietary-cc for prestandard
OAM protocol.
Note: The MD must have no name (via
no name) and the level must be 3 before
you can set the protocol to prestandard.
Configuring Maintenance Associations

A maintenance domain contains maintenance associations.

To add a maintenance association (MA):

At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance- association <maid>
where <maid> is 1128
The maintenance association is created and the
config>oam>cfm>md(<mdid>)>ma(<maid>)$ prompt is displayed.
To delete a maintenance association:

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

1. Navigate to configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> to select the maintenance association to
configure.
The config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt is displayed.
Specifying the interval ccm-interval {3.33ms | 10ms | Note: When ccm-interval is set to 3.33ms, then
between continuity check 100ms | 1s | 10s | 1min | 10min} if you have defined the maximum number of
messages MEPs (255), the interval is not enough time to
activate them with all the corresponding
remote MEPs.
Associating the MA with a classification vlan <vlan-id> Verify that the VLAN is the same as the VLAN
VLAN associated with the MEP.
Note: If a classifier profile is associated with
the MEP, the VLAN should be set to 0.
Specifying if Interface Status interface-status-tlv

TLV is in continuity check
messages
Configuring MEP for the MA mep <mepid> See Configuring Maintenance Endpoints.

Specifying the name format name string <ma-name-string> Maximum length of ma-name-string is
and name of the name primary-vid 45 characters.
maintenance association <ma-name-vid> Maximum combined length of md name
name uint <ma-name-uint> string and ma name string is 48 characters.
name icc <ma-name-icc> Format primary-vid Specify ma-name-vid

as 14094.
Format uint Specify ma-name-uint as an
unsigned integer decimal number
(065535).
Format icc Specify ma-name-icc as the ITU
carrier code that is assigned to the relevant
network operator/service provider. The
codes are maintained by ITU-T as defined in
ITU-T Rec. M.1400.
Note: If the icc option is selected or
prestandard OAM protocol is being used, the
maintenance domain must have no name (use
command no name).
Configuring Maintenance Endpoints

Maintenance endpoints reside at the edge of a maintenance domain. They
initiate and respond to CCMs, linktrace requests, and loopbacks to detect,
localize, and diagnose connectivity problems.
Note For every MEP, a flow must be configured with the same classification as the
MEP, in the direction UNI to NNI. This can be achieved using either of the
following methods:
Classification method Configure the MEP classification; the SW automatically
finds and matches the corresponding flows to the MEP according to the
MEPs configured classification.
Rx, Tx flows method Explicitly bind flows on a MEP. The MEP derives its
classification from its bound flows.
To add a maintenance endpoint (MEP):

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

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

Note You can remove a maintenance endpoint regardless of whether it contains

services.
To configure a maintenance endpoint:

maintenance-association <maid> mep <mepid>to select the maintenance
endpoint to configure.
The prompt config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
is displayed.
Note When changing the MEP classification method, you must delete the MEP and
then create a new MEP.
Defining sending of AIS ais [ interval { 1s | 1min }] When md-level is set to 7, client-md-level,
[priority <priority>] even if configured, becomes meaningless.
In this case, the MEP cannot be defined to
AIS transmission and must be set to no-
ais.
Binding the MEP to an bind ethernet [<slot>/]<port> To unbind the MEP, enter no bind.
Ethernet port
Binding the MEP to an ETP bind etp <etp-name> To unbind the MEP, enter no bind.
port if ETP is used {subscriber | transport} <port-id>
Binding the MEP to a logical bind logical-mac <port-number> To unbind the MEP, enter no bind.
MAC port
Binding the MEP to PCS bind pcs <port-number> To unbind the MEP, enter no bind.
port Note: Relevant only for the SHSDL module
option.
Binding the MEP to bridge bind bridge-port <bridge-number> The bridge port must not be used by a
port <port-number> flow.
Enabling initiation of ccm-initiate To disable initiating continuity check

continuity check messages messages, enter no ccm-initiate.
(CCM)
Specifying the priority of ccm-priority <priority> Possible values: 07

CCMs and LTMs transmitted
by the MEP
Associating the MEP with a classification vlan <vlan-id> You can associate more than one MEP to
classifier profile or VLAN classification profile <profile-name> the same VLAN if the MEPs belong to MDs
with different levels.
Verify that the VLAN is the same as the
VLAN associated with the MA.
If using a classifier profile, it must be
EVC.cos or VLAN+inner-VLAN.

Defining client MD level client-md-level <md-level> Possible values: 07

Client MD level must be higher than MD
level.
Note: When md-level is set to 7,
client- md-level, even if configured,
becomes meaningless, as it must have a
higher value than md-level but cannot
exceed 7.
Specifying continuity continuity-verification <cc-based | This parameter is visible only in
verification method lb-based> prestandard mode and can be configured
only if ccm-initiate is enabled as explained
above. Use lb-based only for RAD
proprietary OAM functionality.
Specifying that MEP customer-tags-excluded This parameter is visible only for up MEPs,
transmits OAM PDUs with and is relevant to E-line only; it is not
only S-tag, and no C-tag applicable for up MEPs over bridge or ETP.
Defining the MAC address dest-addr-type [ccm {unicast|multicast}] If more than one remote MEP ID has been
type sent in OAM [pm {unicast|multicast}] defined for the MEP and you change the
continuity check messages CCM destination address type from
(CCM) and performance multicast to unicast, all remote MEP IDs
measurement messages are deleted except for the lowest remote
(PM) MEP ID.
If the MAC address type for PM messages
is unicast, then the MAC address for the
transmission of PM messages is
determined by the configuration of the
destination NE. If a remote MAC address is
configured for the destination NE, that
MAC is used. Otherwise if a remote MEP ID
is configured for the destination NE, the
remote MAC address is learned from CCM
messages. See Configuring Destination
NEs for details.
Defining a unicast MAC dest-mac-addr <mac-addr> MAC address is in format xx-xx-xx-xx-xx-xx
address if you defined
unicast MAC address type
for CCM messages with the
dest-addr-type command
Defining direction direction { up | down } If the MEP is bound to a bridge or ETP

port, the direction must be up.

Assigning unidirectional or flow uni-direction rx <rx-name> [ Rx flow: Flow with ingress port that is the
bidirectional Rx or Tx flow tx <tx-name>] MEP facing port
to the MEP flow bi-direction <name> Tx flow: Flow with egress port that is MEP
facing port
Up to eight Tx flows and eight Rx flows
can be assigned to the MEP.
Rx/Tx flows cannot be assigned if one of
the following is true:
VLAN is configured at the MA level.
VLAN or profile is configured at the
MEP level for the Rx classification.
To delete flow assignment, enter no flow
uni-direction or no flow bi-direction,
respectively.
Defining forwarding forwarding-method { e-line | e-lan }

method
Enabling/disabling Latching mef46-ll Note: MEF-46 can only be enabled on MEP

Loopback Function (LLF) on no mef46-ll configured with Rx and Tx flows. It cannot
MEP be enabled on MEP configured with
classification.
Defining the queue for the queue fixed <queue-id> Note: The block parameter is not allowed
MEP [block <level-id>/<queue-id>] for up MEPs.
queue queue-mapping
<queue-map-profile-name>
[block <level-id>/<queue-id>]
Defining remote MEP with remote-mep[<rmep1>..<rmep2>,<rmep3> Possible values for remote MEP IDs:
which the MEP ] 18191
communicates You can define multiple remote MEP IDs in
one remote-mep command by specifying a
list of values separated by commas (with
no spaces between the values), using .. to
indicate ranges. You can end the
command line with <CR> and then input
another list. Up to 10 elements (where
each element is either a single remote
MEP or a range of multiple remote MEPs
having consecutively numbered IDs) can be
configured in a list.
The MEP ID must be different than the
remote MEP ID(s). You can use multiple
remote-mep commands to define up to
100 remote MEPs for the local MEP (up to
1024 total remote MEPS in device) if
standard OAM protocol is being used for
the MD and the destination address type
is multicast, otherwise you can define only
one remote MEP.

Configuring service for the service <serviceid> See Configuring Maintenance Endpoint
MEP Services.
Displaying MEF46 Latching show mef46-ll-status See Viewing MEF46 Latching Loopback
Loopback status Status.
Displaying MEP status show status
Displaying remote MEP show remote-mep <remote-mep-id> If a remote MEP was never learned, its
status status status is NEW. As a result, the following
takes place:
Dest NE that is configured under this
MEPs services cannot learn the remote
MAC address and therefore, does not
transmit LMM and DMM.
unavailability is not indicated and
therefore the unavailability counters
are not incremented.
Available counter increments, as it is
ready for use as soon as the remote
MEP is configured.
Administratively enabling no shutdown To deactivate the MEP, enter shutdown.

MEP Note: Following no shutdown of MEP, the
following warning message appears to
notify you to activate relevant MEP
services: Warning: Relevant MEP services
must be activated following MEP
reactivation.
Viewing MEF46 Latching Loopback Status
To display the MEF46 LL status:

In the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,
enter show mef46-ll-status.
The status screen appears. For information on the MEF46 LL status
values, see Table 11-3.
ETX2i>config>oam>cfm>md(1)>ma(1)>mep(2)# show mef46-ll-status
Rx Unicast LLMs : 2
Rx Multicast LLMs : 0
Rx Discarded LLMs : 0
Tx LLRs : 2
Tx Autonomous LLRs : 0
Num First Source MAC Address Last Source MAC Address Time Remaining

-----------------------------------------------------------------------------
1 00-20-D2-54-11-92 00:06:43
ETX2i config>oam>cfm>md(1)>ma(1)>mep(2)#
Table 11-3. MEF46 Latching Loopback Status
Displayed
Administrative Status Current status of the LLF

Possible values: Up, Down
Note: The parameters of this report are only displayed when
Administrative Status is Up.
Rx Unicast LLMs Number of unicast LLM PDUs received by the LLF
Rx Multicast LLMs Number of multicast LLM PDUs received by the LLF
Rx Discarded LLMs Number of invalid LLM PDUs discarded by the LLF
Tx LLRs Number of LLR PDUs sent by the LLF
Tx Autonomous LLRs Number of autonomous LLR PDUs sent by the LLF. An

autonomous LLR has a response code of Timeout or Prohibited.
First Source MAC Addre Start of a block of source MACs in incoming frames that are
looped
Last Source MAC Addre End of a block of source MACs in incoming frames that are
looped
Time Remaining Time remaining until deactivation of the loop
Configuring Maintenance Intermediate Points
MD-Level MIP
When MD-level MIP mode is activated, ETX-2i provisions a MIP for each flow at
each physical port, bridge port, and ring port, subject to the limitations specified
above in OAM Elements. The MIPs are added for each specified MD level, or MD
level range.
To add an MD-level MIP:

At the config>oam>cfm# prompt, enter md-level-mip <md-level-list>.
The MD levels in the list can be separated by a comma or given as a range,
for example: 1..3, 5.
Note Do not type a space after any commas in the list.
Typing no md-level-mip <md-level-list> removes the specified MD-level MIP.
Service-Level MIP
Service-level MIPs are intermediate entities that are defined in the maintenance
domain level.

To add a MIP:
At the config>oam>cfm>md(<mdid># prompt, enter:
mip <mipid>
The MIP is created and the prompt
config>oam>cfm>md(<mdid>)>mip(<mipid>)$ is displayed.
To delete a MIP:
At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mipid>
The maintenance intermediary point is deleted.
To configure a MIP:
1. Navigate to configure oam cfm maintenance-domain <mdid> mip <mipid> to
select the MIP to configure.
The config>oam>cfm>md(<mdid>)>mip(<mipid>)# prompt is displayed
Binding the MIP to an bind ethernet [<slot>/]<port> To unbind the MIP, enter no bind.
Ethernet port, logical MAC bind logical-mac <port-number>
port, or PCS port
bind pcs <port-number>
Assigning unidirectional Rx flow uni-direction rx <rx-name> [tx <rx-name> Rx flow name

and Tx flows to the MIP <tx-name>] <rt-name> Tx flow name
To delete flow assignment, enter no flow
uni-direction.
Administratively enabling no shutdown To deactivate the MIP, enter shutdown.

MIP
Displaying MIP status show status
Configuring Maintenance Endpoint Services

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

At the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,
enter:
service <serviceid>
where <serviceid> is 18.

The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)$
is displayed.
To configure a MEP service:

maintenance-association <maid> mep <mepid> service <serviceid> to select
the service to configure (<serviceid> is 18).
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)
# is displayed.
Associating this service with a classification priority-bit <p-bit> Possible values: 07

priority
Specifying delay threshold in delay-threshold <delay-thresh> Possible values: 15,000,000

microseconds Note: The configured value is
rounded down to
100 microsecond granularity,
e.g. values 099 are rounded
to 0, values 100199 are
rounded to 100, etc.
Specifying delay variation delay-var-threshold <delay-var-thresh> Possible values: 15,000,000

threshold in microseconds Note: The configured value is
rounded down to
100 microsecond granularity.
Specifying the interval for dmm-interval {100ms | 1s | 10s}

delay measurement messages,
to be used by all remote NEs
defined for service
Specifying the interval for loss lmm-interval {100ms | 1s | 10s} When changing lmm-interval,
measurement messages, to be you must perform NO LM and
used by all remote NEs defined then LM.
for service
Configuring collection of pm-collection interval <seconds> Note: In addition to enabling

performance management PM statistics collection for the
statistics for the service, that service, it must be enabled for
are presented via the RADview the device. Refer to the
Performance Management Performance Management
portal section in the Monitoring and
Configuring destination NE for dest-ne <dest-ne-index> Possible values: 1255

service

Activating the MEP service no shutdown You can activate a service only
if the corresponding MEP is
active and you have defined at
least one destination NE.
Note: Following no shutdown
of MEP, the following warning
message appears to remind
you to activate relevant MEP
services: Warning: Relevant
MEP services must be activated
following MEP reactivation.
Configuring Destination NEs

For performance measurement, it is necessary to know the exact address of the
destination NE. You can configure the remote MAC address of the NE or ETX-2i
can learn it from the CCM messages, provided that the remote MEP of the
destination NE has been learned (its status is not NEW).
If the remote MAC address is not configured and needs to be learned,
performance measurement messages (lmm and dmm) are sent only after the
address is learned.
To add a destination NE:

At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<service
id>)#, enter:
dest-ne <dest-ne-index>
where <dest-ne-index> is 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.
Assigning the delay variation bck-delay-var-bin-profile profile <name>

measurement bin profile for
backward delay variation
measurement

Specifying delay measurement delay {one-way | two-way}

method and length of DMM [data-tlv-length <length-val>]
data TLV
Assigning the delay delay-measurement-bin profile <name> The delay measurement bin profiles
measurement bin profile are defined in the conf>oam>cfm
level.
Assigning the delay variation delay-var-measurement-bin The delay measurement bin profiles
measurement bin profile profile <name> are defined in the conf>oam>cfm
level.
Configuring description string description <string>
Assigning the delay variation fwd-delay-var-bin-profile profile

measurement bin profile for <name>
forward delay variation
measurement

Defining single-ended/dual- loss {single-ended |dual-ended} user-data measures user data

ended loss measurement [user-data [green-only] [no-ccm] and CCM messages. Do not use
method [lm-mode {rx | tx-rx}]] user-data on up MEPs in the
loss {single-ended |dual-ended} Bridge application.
[user-data [lm-mode {rx | tx-rx}]] green-only measures green
loss {single-ended |dual-ended} packets only, for user data
[user-data-green [lm-mode {rx | tx-rx}]] single-ended/dual-ended loss
loss single-ended [synthetic measurement
[lm-mode {rx | tx-rx}]] no-ccm does not include CCMs
loss single-ended [lmm-synthetic in user data single-ended/dual-
[lm-mode {rx | tx-rx}]] ended loss measurement
loss single-ended [slm user-data-green measures green

[slm-data-tlv-length <slm-length-val>] packets only, for user data
[lm-mode {rx | tx-rx}] single-ended/dual-ended loss
measurement
Note: Green and yellow frames are
identified by DEI (0=green, 1=yellow).
Therefore in order for color-aware
loss measurement to function
properly, you need to do the
following:
Mark green/yellow frames by
DEI in the Tx flow.
Configure ingress-color by DEI.
Specify no_policer for the flow.
synthetic measures DM frames;
recommended when working with
devices that do not count user
data frames
lmm-synthetic measures
synthetic frames as well;
recommended for working with
ETX-201A/202A
slm measures synthetic SLM/SLR
frames
lm-mode specifies loss
measurement message mode:
rx indicates to respond with
LMR/SLR when LMM/SLM is
received.
tx-rx indicates to transmit
LMMs/SLMs, and respond with
LMR/SLR when LMM/SLM is
received.
slm-data-tlv-length specifies
length of SLM data TLV.
Possible values: 01800 (default:
0)

Configuring collection of pm-collection interval <seconds> Note: In addition to enabling PM

performance management statistics collection for the
statistics for the destination destination NE, it must be enabled
NE, that are presented via the for the device. Refer to the
RADview Performance Performance Management section in
Management portal the Monitoring and Diagnostics
chapter for details.
Defining the MAC address of remote mac-address <mac> If the MAC address is
the destination NE 00-00-00-00-00-00, the statistic
counters for the destination NE do
not increment.
Defining the remote MEP ID of remote mep-id <remote-mep-id>

the destination NE
Displaying the delay show delay-measurement-bins {rt-delay Relevant only if profiles were
measurement bins for delay | rt-delay-var | fw-delay-var | bw-delay- assigned via delay-measurement-bin,
measurements via DMRs var } current delay-var-measurement-bin.
show delay-measurement-bins {rt-delay rt-delay Round trip delay
| rt-delay-var | fw-delay-var | bw-delay- <rt-delay-var> Round trip delay
var } interval <interval-num> variation
show delay-measurement-bins {rt-delay <fw-delay-var> Forward delay
| rt-delay-var | fw-delay-var | bw-delay- variation
var } all
<bw-delay-var> Backward delay
variation
<current> Current statistics
<interval> Interval statistics
interval-num> Interval number
[number]
all all statistics
Clearing statistics clear-statistics The destination network element

running counters are cleared; the
interval and current counters are not
cleared.
Configuring OAM CFM Service Event Reporting

You can define dedicated event reporting counters to track OAM SLA threshold
crossing violations (for information on configuring the OAM service thresholds,
see Configuring Maintenance Endpoint Services).
In addition to the regular OAM statistics collection, ETX-2i supports proactive
SLA measurements per OAM service, as per RMON-based RFC 2819. The device
sends reports when one of the counters rises above or drops below the set
thresholds within the specified sampling period of time. These reports can be
sent as SNMP traps to the defined network management stations, or written to
the event log. If an event is generated, this action also sends a syslog
notification packet, if syslog reporting is active (refer to the Syslog section for
more details).

The following counters can be monitored:
Far End Frame Total number of OAM frames lost from local MEP to remote
Loss Ratio MEP, divided by total number of transmitted OAM frames
since the service was activated
Near End Frame Total number of OAM frames lost from remote MEP to local
Loss Ratio MEP, divided by total number of transmitted OAM frames
since the service was activated
Frames Above Number of frames that exceeded delay threshold

Delay
Frames Above Number of frames below or equal delay variation threshold

Delay Variation
(Jitter)
Far End Total number of far end unavailable seconds divided by

Unavailability Ratio elapsed time since service was activated
Near End Total number of near end unavailable seconds divided by

Unavailability Ratio elapsed time since service was activated
For non ratio-based counters (Frames Above Delay and Frames Above Delay
Variation), you have to define a sampling interval in addition to the rising and
falling thresholds. The purpose of the interval is to define a timeline, in seconds,
in which the service OAM data is sampled and compared with the pre-defined
service thresholds. For the ratio-based counters, defining a sampling interval is
not required.
To configure the event reporting for a service:

1. Navigate to configure fault cfm.
2. Specify the service and counter for which you wish to configure event
reporting:
service md <mdid> ma <maid> mep <mepid> service <serviceid>
{above-delay | above-delay-var | far-end-loss-ratio | near-end-loss-ratio |
far-end-unavailability-ratio | near-end-unavailability-ratio}
The prompt
config>fault>cfm>service(<mdid>/<maid>/<mepid>/<serviceid>)# is
displayed.
3. Specify the type of event reporting for the counter (see Table 11-4):
For counters above-delay and above-delay-var:
frames-report [event {none | log | trap | logandtrap}] [rising-threshold
<rising-threshold>] [falling-threshold <falling-threshold>]
[sampling-interval <value>]
For counters near-end-loss-ratio or far-end-loss-ratio:
{1e-3 | 1e-4 | 1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 | 1e-10}] [falling-threshold
{1e-3 | 1e-4 | 1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 | 1e-10}]
For counters near-end-unavailability-ratio or far-end-unavailability-ratio:

<rising-threshold-thousandth>] [falling-threshold
<falling-threshold-thousandth>]
4. Type no shutdown to activate the event reporting for the counter.
Table 11-4. Service Event Reporting Parameters
Parameter Description Possible Values
event Specifies the type of event reporting none The event is not reported.
log The event is reported via the
event log.
trap An SNMP trap is sent to
report the event.
logandtrap The event is reported
via the event log and an SNMP trap.
rising-threshold A value above rising-threshold within the For counters above-delay or

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

the data is sampled and compared with the Relevant only for counters
rising and falling thresholds above-delay or above-delay-var
Sampling interval value must be
at least double rising threshold.
Viewing OAM CFM Statistics

You can display end-to-end performance monitoring data for the MEPs, OAM
services, and destination NEs. The statistics for a service are calculated from the
statistics for its destination NEs.
ETX-2i measures performance in fixed intervals (the interval length can be
configured by the interval-duration command).

You can view the following types of statistics for MEPs, services, and destination
NEs:
Running OAM statistics collected since the corresponding service

was activated
Current OAM statistics for the current interval
Interval OAM statistics for a selected interval. You can select an

interval only if it has already ended since the
corresponding service was activated.
When a service is first activated, you can view statistics for only the current
interval. The statistics data is shown for the time elapsed since the beginning of
the interval. When the current interval ends, it becomes interval 1 and you can
select it for viewing interval statistics. After each interval ends, you can select it
for viewing interval statistics.
OAM CFM supports checking Availability status within an interval as well as
across intervals. In the case that there are less than n consecutive delta-t small
time intervals at the end of an interval that have changed Availability status
(become Available or Unavailable), the delta-t small time intervals at the
beginning of the next interval are checked to see if there is a total of n
consecutive delta-t small time intervals across the intervals (the end of the
current interval and the beginning of the next interval). If so, the delta-t small
time intervals at the end of the current interval are all considered to have a
changed Availability status (Available or Unavailable).
For example, when Availability is defined for ten one-second intervals, and there
are three SES seconds at the end of the current interval, those seconds are
considered Unavailable only if the first seven seconds of the next interval are
also SES, i.e. ten consecutive SES.
An interval is closed only after the following Availability and Unavailability
counters are updated accordingly, taking into consideration the Availabilty status
change of Delta-ts in the current interval that are affected by the Availability
status of Delta-ts in the new interval (see Table 11-5 for a description of the
counters):
Tx Frames [Forward]
Tx Frames [Backward]
Rx Frames [Forward]
Rx Frames [Backward]
Unavailable Seconds [Forward]
Unavailable Seconds [Backward]
Frame Loss Ratio (%) [Forward]
Frame Loss Ratio (%) [Backward]
Also, the statistics of the last History interval (i.e. the interval before the
current) can only be viewed n * Delta_t seconds after the current interval has
commenced.

To configure the OAM CFM statistics interval in minutes:

At the config>system prompt, use the interval-duration command as
specified :
interval-duration { 5 | 10 | 15 }
Notes If RADview is being used to manage ETX-2i, then when the interval duration is
changed, it is recommended to clear the statistics of all relevant Dest NEs, in
order to avoid any inconsistencies.
interval-duration must be configured to a larger value than availability (delta_t
* n) calculation; otherwise, a sanity error occurs.
To display the OAM CFM statistics for a MEP, service, or destination NE:
1. Navigate to the level corresponding to the OAM MEP, service, or destination
NE for which you wish to view the statistics
configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> mep <mepid>
or
maintenance-association <maid> mep <mepid> service <serviceid>
or
maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index>).
The prompt for MEP, service, or destination NE is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<ser
viceid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<ser
viceid>)>
dest-ne(<dest-ne-index>)#
Note The service for which you wish to view the statistics must be active. If the
service is not active, the commands to view statistics are not recognized.
Viewing show statistics The statistics are displayed as shown in Viewing Running Statistics; see
running running Table 11-5 and Table 11-6.
statistics
Viewing show statistics The statistics for the current interval are displayed as shown in Viewing
statistics current Current Statistics; see Table 11-5 and Table 11-6.
for the
current
interval

Viewing show statistics Allowed values for interval-num: 148

the interval The statistics for the selected interval are displayed as shown in
statistics <interval-num> Viewing Interval Statistics; see Table 11-5 and Table 11-6.
for a
If you specified an interval that has not yet ended since the service
selected
was activated, a message is displayed that the interval doesnt exist.
interval
Viewing show statistics The statistics are displayed as shown in Viewing Running Statistics,
running all Viewing Current Statistics, Viewing Interval Statistics; see Table 11-5 and
statistics, Table 11-6.
statistics
for the
current
interval,
and
statistics
for all
intervals
Viewing show statistics The statistics for all intervals are displayed as shown in Viewing Interval
statistics all-intervals Statistics; see Table 11-5 and Table 11-6.
for all
intervals
Clearing clear-statistics The running statistics for the MEP, service, or destination NE are cleared
the (the interval and current counters are not cleared).
statistics
for the
service or
destination
NE
Table 11-5. OAM Statistic Counters
Tx Frames [Forward] Total number of frames transmitted from local destination NE to

remote destination NE since the service was activated
Note: Counts Tx frames during Available time only.
Tx Frames [Backward] Total number of frames transmitted from remote destination NE to
local destination NE since the service was activated
Note: Counts Tx frames during Available time only.
Rx Frames [Forward] Total number of frames received by remote destination NE since the
service was activated
Note: Counts Rx frames during Available time only.
Rx Frames [Backward] Total number of frames received by local destination NE since the
service was activated
Note: Counts Rx frames during Available time only.

Lost Frames [Forward] (in service Total number of frames lost from local destination NE to remote
statistics) destination NE since the service was activated
Frames Loss[Forward] (in dest-ne Note: This counter is called Lost Frames for Services, and Frames Loss
statistics) for dest NEs.
Lost Frames [Backward] (in service Total number of frames lost from remote destination NE to local
statistics) destination NE since the service was activated
Frames Loss[Backward] (in dest-ne Note: This counter is called Lost Frames for Services, and Frames Loss
statistics) for dest NEs.
Frame Loss Ratio (%) [Forward] Lost Frames [Forward] divided by Tx Frames [Forward]
Note: Counts FLR during Available time only.
Frame Loss Ratio (%) [Backward] Lost Frames [Backward] divided by Tx Frames [Backward]
Note: Counts FLR during Available time only.
Unavailable Seconds [Forward] Number of seconds the remote destination NE is considered
unavailable
Note: This counter is displayed only for dest NEs.
Unavailable Seconds [Backward] Number of seconds the local destination NE is considered unavailable
Available Seconds [Forward] Number of seconds the remote destination NE is considered available
Two Way Unavailable Seconds Number of seconds that either the remote destination NE (forward)
and/or local destination NE (backward) are unavailable.
Note: This counter is displayed only for dest NEs current and interval
statistics.
Available Seconds [Backward] Number of seconds the local destination NE is considered available
Two Way Available Seconds Number of seconds that both the remote destination NE (forward)
and local destination NE (backward) are available.
Note: This counter is displayed only for dest NEs current and interval
statistics.
Two Way Delay (mSec) Round trip frame delay
Two Way IFDV (mSec) Round trip frame delay variation
Current Forward IFDV (mSec) Difference between the current delay value and the previous current
delay value, for forward direction
Current Backward IFDV (mSec) Difference between the current delay value and the previous current
delay value, for backward direction
Frames Above Delay Threshold Number of DM frames whose delay value exceeded the configured
delay threshold
Frames Above IFDV Threshold Number of DM frames whose delay variation exceeded the configured
delay variation threshold
Two Way Delay (msec) [Min] Minimum frame delay value received in DM frame
Two Way Delay (mSec) [Average] Average of all frame delay values received in DM frames

Two Way Delay (msec) [Max] Maximum frame delay value received in DM frame
Two Way IFDV (msec) [Min] Minimum difference between the frame delay values received in DM
frames
Two Way IFDV (mSec) [Average] Average difference between the frame delay values received in DM
frames
Two Way IFDV (msec) [Max] Maximum difference between the frame delay values received in DM
frames
Forward IFDV [Min] Minimum difference between the frame delay values received in DM
frames for forward direction
Forward IFDV [Average] Average difference between the frame delay values received in DM
Forward IFDV [Max] Maximum difference between the frame delay values received in DM
Backward IFDV [Min] Minimum difference between the frame delay values received in DM
frames for backward direction
Backward IFDV [Average] Average difference between the frame delay values received in DM
Backward IFDV [Max] Maximum difference between the frame delay values received in DM
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated.
Exception: Following shutdown and then no shutdown of a service,
current statistics of the first interval display in Elapsed Time the time
that is aligned to the wall clock, and not the elapsed time since the
service was activated. Hence, all current statistics calculated using
Elapsed Time are not valid for the first interval following shutdown
and no shutdown.
CCM P-bit P-bit where CCM resides
MD Level MD level munber where CCM resides
CCM Tx frames Number of CCM Tx frames per MEP
RMEP ID The ID of the remote MEP associated with the MEP
CCM Rx frames Number of CCM Rx frames per remote MEP
Table 11-6. OAM Delay and Loss Measurement Counters
Tx LMMs Number of transmitted loss measurement messages

Tx DMMs Number of transmitted delay measurement messages
Rx LMRs Number of received loss measurement replies
Rx DMRs Number of received delay measurement replies

Performing OAM Loopback

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

enter all necessary commands according to the tasks listed below.
Specifying remote MEP by lbm address <mac-address> [repeat MAC address is in the
MAC address <repeat-num>] [data-tlv-length format <xx-xx-xx-xx-xx-xx>.
<length-val>] Allowed range of
Specifying remote MEP by lbm remote-mep <mep-id> [repeat repeat-num is 1500.
MEP ID <repeat-num>] [data-tlv-length Allowed range of
<length-val>] data-tlv-length is 01900.
Sending LBM messages to lbm multicast [repeat <repeat-num>] The only allowed value for
default multicast MAC repeat-num is 1.
address
Checking OAM loopback show lbm-results

results
Performing OAM Link Trace

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

enter all necessary commands according to the tasks listed below.
Specifying remote MEP by MAC linktrace address <mac-address> MAC address is in the
address [ttl <ttl-value>] format <xx-xx-xx-xx-xx-xx>.
Specifying remote MEP by ID linktrace remote-mep <mep-id> Allowed range for ttl-value
[ttl <ttl-value>] is 164. This parameter
specifies number of hops.
Each unit in the link trace
decrements the TTL until it
reaches 0, which terminates
the link trace.

Checking the OAM link trace show linktrace-results

results
Examples
Configuring MD, MA, and MEP

This example illustrates configuring the following:
MD ID 1
MA ID 1
MEP ID 1:
Remote MEP ID 2
Classification VLAN 100
To configure MD, MA, and MEP:

#**************************Configure MD
exit all
configure oam cfm
#**************************Configure MA
#**************************Configure MEP
mep 1
bind ethernet 0/1
remote-mep 1..5,7,15..25,54,68,73..75,80,88..99,100,102,120
remote-mep 150,160..164,180
no shutdown
exit all
To display the configured MD, MA, and MEP:

ETX-2i# configure oam cfm maintenance-domain 1
ETX-2i>config>oam>cfm>md(1)# info detail
no proprietary-cc
md-level 3
name string "MD1"
name string "MA1"
ccm-interval 1s
mep 1
bind ethernet 0/1
remote-mep 1..5,7,15..25,54,68,73..75,80,88..99,100,102,120,150,160..164,180

dest-addr-type ccm multicast pm unicast

ccm-initiate
ccm-priority 0
forwarding-method e-line
direction down
client-md-level 4
no ais
no shutdown
exit
exit
Configuring Service for Discovery

This example illustrates configuring a service with MEP and Rx/Tx flows, with the
flow and OAM parameters configured for service discovery by RADview, and with
PM statistics collection enabled for the service components, for the RADview PM
portal.
Rx flow parameters:
Ingress port=Ethernet port 0/1, egress port=Ethernet port 0/3
Classification=VLAN 21
Service name=gold
Tx flow parameters:
Ingress port=Ethernet port 0/3, egress port=Ethernet port 0/1
Classification=VLAN 1
Service name=gold
MEP parameters:
MD ID=10
MA ID=10
MEP ID=101
Note VLAN classification must not be configured for the MEP, in order to facilitate the
service discovery.
Remote MEP ID=20

Service ID=1
Dest NE ID=1
#**************************Enable PM in device
exit all
configure
reporting
pm
exit
#**************************Configure classifiers
flows
match vlan 1

exit
match vlan 21
exit
#**************************Configure Rx flow
flow v21_v1
classifier v21
service-name gold
no shutdown
exit
#**************************Configure Tx flow
flow v1_v21
classifier v1
service-name gold
no shutdown
exit all
#**************************Configure MEP, service, and dest NE

configure oam cfm
mep 101
bind ethernet 0/1
flow uni-direction rx v21_v1
flow uni-direction tx v1_v21
remote-mep 20
no shutdown
service 1
dest-ne 1
loss single-ended lmm-synthetic lm-mode tx-rx
remote mep-id 20
exit
no shutdown
exit all
Viewing MEP Status and Remote MEP

The following illustrates displaying MEP status and remote MEP.
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)# show status
Ingress Port : Ethernet 0/1
Direction : Down
Classification Profile : Class_A
CCM Priority : 7

MD Name : MD1
MA Name : MA1
Test Status : Off
MEP Defect : Status

Rx LCK : Off
Rx AIS : Off
Cross Connected CCM (Mismatch; Unexpected MD Level) : Off
Invalid CCM (Unexpected MEP; Unexpected CCM Period) : Off
Remote MEP Remote MEP Address Operational Status

-----------------------------------------------------------------------------
4 00-20-D2-2C-97-A9 OK
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)# show remote-mep 4 status

Remote MEP Address : 00-20-D2-2C-97-A9
Operational Status : OK
Configuring Service and Destination NE

This section illustrates configuring the following service and destination NE:
MD ID 1, MA ID 1, MEP ID 1 (from example in Configuring MD, MA, and MEP)
Service 1
Destination NE 3
To configure service and destination NE:

exit all
configure oam cfm ma 1 ma 1 mep 1
service 1
dest-ne 3
exit
no shutdown
exit all
To display the configured service and destination NE:

ETX-2i# configure oam cfm ma 1 ma 1 mep 1 service 1
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)#info detail
lmm-interval 1s
dmm-interval 1s
dest-ne 3
remote mac-address 00-00-00-00-00-00
delay two-way data-tlv-length 0
loss single-ended user-data
no delay-measurement-bin
no delay-var-measurement-bin
exit


no shutdown
Configuring Service Event Reporting

This section illustrates configuring OAM CFM event reporting as follows:
Configure counters for the following service, as shown in the table below:
Maintenance domain 5
Maintenance association 8
MEP 3
Service 4
The delay and delay variation (jitter) threshold for this service are set to 10 and
5 milliseconds respectively. The reporting counters for this service are set as
shown in the table below.
Counter Event Type Rising Threshold Falling Threshold Sampling Interval
Frames Above Delay Log and trap 4 2 8
Frames Above Delay Variation Log 10 5 30
Far End Frame Loss Ratio Trap 1e-4 1e-8
Near End Frame Loss Ratio Log and trap 1e-9 1e-10
Far End Unavailability Ratio Trap 40 20
Near End Unavailability Ratio Log 50 25
In this example, an SNMP trap and an event are generated as notification of the
rising threshold if during an 8-second sample interval, four DMM packets or
more exceed the 10-milliseconds delay threshold of this service. The alarm is
cleared (falling threshold) if ETX-2i detects an 8-second sample interval in which
two or fewer packets cross the thresholds.
A rising or falling threshold event is generated if a specific ratio is exceeded. For
example, an SNMP trap is sent if the far end Frame Loss Ratio (from ETX-2i to
the network) exceed 10^-4, i.e. more than one frame out of 10,000 LMMs sent
for this service are lost.
To configure OAM CFM event reporting:

#************** Define the service delay thresholds
exit all
configure oam cfm ma 5 ma 8 mep 3 service 4
delay-threshold 10
exit all
#************** Define the service event reporting counters

#****************** Counter: Frames Above Delay
configure fault cfm
service md 5 ma 8 mep 3 service 4 above-delay
frames-report event logandtrap rising-threshold 4 falling-threshold 2
sampling-interval 8
no shutdown

exit
#****************** Counter: Frames Above Delay Variation

service md 5 ma 8 mep 3 service 4 above-delay-var
frames-report event log rising-threshold 10 falling-threshold 5 sampling-
interval 30
no shutdown
exit
#****************** Counter: Far End Frame Loss Ratio

service md 5 ma 8 mep 3 service 4 far-end-loss-ratio
frames-report event trap rising-threshold 1e-4 falling-threshold 1e-8
no shutdown
exit
#****************** Counter: Near End Frame Loss Ratio

service md 5 ma 8 mep 3 service 4 near-end-loss-ratio
frames-report event logandtrap rising-threshold 1e-9 falling-threshold 1e-10
no shutdown
exit
#****************** Counter: Far End Unavailability Ratio

service md 5 ma 8 mep 3 service 4 far-end-unavailability-ratio
frames-report event trap rising-threshold 40 falling-threshold 20
no shutdown
exit
#****************** Counter: Near End Unavailability Ratio

service md 5 ma 8 mep 3 service 4 near-end-unavailability-ratio
frames-report event log rising-threshold 50 falling-threshold 25
no shutdown
exit all
To display the defined service event reporting counters:

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

frames-report event trap rising-threshold 40 falling-threshold 20

no shutdown
exit
service md 5 ma 8 mep 3 service 4 near-end-unavailability-ratio
frames-report event log rising-threshold 50 falling-threshold 25
no shutdown
exit
Viewing Running Statistics

ETX-2i>config>oam>cfm>md(1)>ma(100)# mep 100
ETX-2i>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics running
Running
-----------------------------------------------------------------------------
CCM P-bit : 2 MD Level : 3

CCM Tx frames : 1286
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames
-----------------------------------------------------------------------------
101 1286
102 0
103 0
ETX-2i>config>oam>cfm# ma 1 ma 1 mep 1 serv 1
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
TX Frames : 1548 1548
RX Frames : 1548 1548
Lost Frames : 0 0
Two Way Delay (mSec) : 0.062

Two Way IFDV (mSec) : 0.004
Frames Above Delay Threshold : 0
Frames Above IFDV Threshold : 0
Elapsed Time (sec) : 31271
Loss and Delay Measurements Messages

-----------------------------------------------------------------------------
Tx Rx
LMMs : 31271 LMRs : 0
DMMs : 31278 DMRs : 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# dest-ne 3
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statistics running
Running Counters
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 1759 1759
Rx Frames : 1759 1759
Frames Loss : 0 0
Unavailable Seconds : 0 0
Available S

Two Way Delay (mSec) : 0.062

Two Way IFDV (mSec) : 0.004
Current Forward IFDV (mSec) : 0.002
Current Backward IFDV (mSec) : 0.002

-----------------------------------------------------------------------------
Tx Rx
LMMs : 1759 LMRs : 1759
DMMs : 1759 DMRs : 1760
Viewing Current Statistics

ETX-2i>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics current
Current
-----------------------------------------------------------------------------

Elapsed Time : 135
CCM Tx frames: 137
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames
-----------------------------------------------------------------------------
101 136
102 0
103 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 1863 1863
Rx Frames : 1863 1863
Lost Frames : 0 0
Frame Loss Ratio (%) : 0.0000 0.0000
Min Average Max

(mSec) (mSec) (mSec)
Two Way Delay : 0.037 0.059 0.084
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018



-----------------------------------------------------------------------------
Tx Rx
LMMs : 722 LMRs : 0
DMMs : 722 DMRs : 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statistics current
Current
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 739 739
Rx Frames : 739 739
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Available Seconds : 739 739
Two Way Unavailable Seconds : 0

Two Way Available Seconds : 739
Min Average Max

Two Way Delay : 0.037 0.059 0.084
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018


-----------------------------------------------------------------------------
Tx Rx
LMMs : 740 LMRs : 740
DMMs : 739 DMRs : 739
Viewing Interval Statistics

ETX-2i>config>oam>cfm>md(1)>ma(100)>mep(100)># show statistics interval 1
Interval
-----------------------------------------------------------------------------

Interval : 1
Time Stamp : 28-10-2015 11:09:59
Valid Data : Valid
CCM Tx frames : 303
R-MEP
-----------------------------------------------------------------------------
ID CCM Rx frames

-----------------------------------------------------------------------------
101 303
102 0
103 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)# show statist interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Forward Backward
Tx Frames : 1541 1541
Rx Frames : 1541 1541
Lost Frames : 0 0
Frame Loss Ratio (%) : 0.0000 0.0000
Min Average Max

Two Way Delay : 0.039 0.059 0.083
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018

-----------------------------------------------------------------------------
Tx Rx
LMMs : 900 LMRs : 0
DMMs : 900 DMRs : 0
ETX-205A>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)#
ETX-205A>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)# show statistics total-intervals
Total Intervals
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Lost Frames : 0 0
Min Average Max

Two Way Delay : 0.000 0.000 0.000
Two Way IFDV : 0.000 0.000 0.000

-----------------------------------------------------------------------------
Tx Rx
LMMs : 0 LMRs : 0
DMMs : 0 DMRs : 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show statist interval 1
Interval
-----------------------------------------------------------------------------
Interval : 1
Valid Data : Valid
Time Stamp : 19-05-2014 10:25:06

Forward Backward
Tx Frames : 899 899
Rx Frames : 899 899
Frames Loss : 0 0
Frame Loss Ratio (%) : 0.0000% 0.0000%
Two Way Unavailable Seconds : 0

Two Way Available Seconds : 1195
Min Average Max

Two Way Delay : 0.039 0.059 0.083
Two Way IFDV : 0.001 0.008 0.036
Forward IFDV : 0.000 0.004 0.018
Backward IFDV : 0.000 0.004 0.018

-----------------------------------------------------------------------------
Tx Rx
LMMs : 899 LMRs : 899
DMMs : 900 DMRs : 900
ETX-2i>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)>dest-ne(1)#
ETX-2i>config>oam>cfm>md(1)>ma(2)>mep(1)>service(2)>dest-ne(1)# show statistics total-
intervals
Total Intervals
-----------------------------------------------------------------------------
Forward Backward
Tx Frames : 0 0
Rx Frames : 0 0
Frames Loss : 0 0
Frame Loss Ration (%) : 0.0000% 0.0000%
Min Average Max

Two Way Delay : 0.000 0.000 0.000
Two Way IFDV : 0.000 0.000 0.000
Forward IFDV : 0.000 0.000 0.000
Backward IFDV : 0.000 0.000 0.000

-----------------------------------------------------------------------------
Tx Rx
LMMs : 0 LMRs : 0
DMMs : 0 DMRs : 0

Configuring and Viewing Delay Measurement Bins

This section illustrates configuring delay measurement bins as follows:
Bin1 used for round trip delay measurements, with threshold ranges (in
microseconds (s)):
015,000
15,00149,000
49,00155,000
55,001250,000
250,0015,000,000
Bin2 used for round trip delay variation measurements, with threshold
ranges (in microseconds (s)):
015,000
15,00155,000
55,001105,000
105,001205,000
205,0015,000,000
To configure delay measurement bins:

#*****************Configure delay measurement bin: bin1
exit all
config oam cfm
measurement-bin-profile bin1
thresholds 15000,49000,55000,250000
exit
#*****************Configure delay measurement bin: bin2

measurement-bin-profile bin2
thresholds 15000,55000,105000,205000
exit
#*****************Configure dest NE 3 with the delay

measurement bins
ma 1 ma 1 mep 1 serv 1 dest-ne 3
delay-measurement-bin profile bin1
delay-var-measurement-bin profile bin2
exit all
To display delay measurement bins:

ETX-2i# config oam cfm ma 1 ma 1 mep 1 service 1 dest-ne 3#
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-
ne(3)#show delay-measurement-bins rt-delay all
Type : rt Delay
Current
Bin range Rx DMR

(us)
---------------------------------------------------------------

1 0..15000 0
2 15001..49000 0
3 49001..55000 0
4 55001..250000 0
5 250001..5000000 0
Type : rt Delay
Interval Bin
range Rx DMR
(us)
---------------------------------------------------------------
1 1 0..15000 36
1 2 15001..49000 0
1 3 49001..55000 0
1 4 55001..250000 0
1 5 250001..5000000 0
2 1 0..15000 753
2 2 15001..49000 0
2 3 49001..55000 0
2 4 55001..250000 0
2 5 250001..5000000 0
3 1 0..15000 713
3 2 15001..49000 0
3 3 49001..55000 0
3 4 55001..250000 0
3 5 250001..5000000 0
ETX-2i>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)#
show delay-measurement-bins rt-delay-var all
Type : rt Delay Var
Current
---------------------------------------------------------------
Bin range Rx DMR
(us)
---------------------------------------------------------------
1 0..15000 0
2 15001..55000 0
3 55001..105000 0
4 105001..205000 0
5 205001..5000000 0
Type : rt Delay Var
Interval Bin
range Rx DMR
(us)
---------------------------------------------------------------
1 1 0..15000 36
1 2 15001..55000 0
1 3 55001..105000 0
1 4 105001..205000 0
1 5 205001..5000000 0
2 1 0..15000 753
2 2 15001..55000 0
2 3 55001..105000 0
2 4 105001..205000 0

2 5 205001..5000000 0
3 1 0..15000 713
3 2 15001..55000 0
3 3 55001..105000 0
3 4 105001..205000 0
3 5 205001..5000000 0
OAM CFM: A service with the You tried to configure more Check the priority bit classification and
same priority already exists than one service on the same verify that there is no other configured
priority bit. service on it.
OAM CFM: A Maintenance You previously configured Configure the MA with another name
Association with this format and another MA with the same or format.
name already exists configuration.
OAM CFM: A Maintenance You previously configured Configure the MD with another format,
Domain with this format name another MD with the same name, or level.
and level already exists configuration.
OAM CFM: Active MEP cannot You tried to delete or shut Disassociate the flow from the MEP,
work without a flow down a flow that is being used and then delete or shut down the flow.
by a MEP.
OAM CFM: Active MEP requires You did not configure a single Configure at least one remote MEP.
at least 1 remote MEP remote ID on the MEP.
OAM CFM: Active MIP cannot You did not configure a TX or Configure a TX or Rx flow on the
work without a flow Rx flow on the manual manual MIP that you configured.
MIP that you configured.
OAM CFM: Active MIP cannot The Tx or RX flow that you Configure the MIP with an active Tx or
work without an active flow configured on the MIP is not Rx flow.
active.
OAM CFM: AIS cannot be You configured MEP on a Configure MEP on a maintenance
enabled when MD level equals maintenance Domain with Domain other than Level 7.
seven (7) Level 7, and therefore AIS
could not be enabled on it.
OAM CFM: Cannot activate a You tried to activate a Service Configure a Dest NE under Service.
service without a dest-NE that has no Dest NE
configured under it.
OAM CFM: Cannot activate MIP You did not configure a bound Configure a bound port on the manual
without a bound port port on a manual MIP. MIP.
OAM CFM: Cannot change You tried to change Disable Fault CFM entity, and then
parameters when active parameters on an active Fault change parameters.
CFM entity.

OAM CFM: Cannot change pm to You tried to configure a Configure a multicast destination
multicast because there is a multicast destination address address on a Dest NE that does not
destne that counts loss on a Dest NE that has user have user data loss measurements.
data loss measurements.
OAM CFM: Cannot configure You configured a MEP to work Configure only one remote MEP per
destination address type unicast with unicast destination MEP.
and more than one remote MEP address, but also assigned to
it more than one remote MEP.
OAM CFM: Cannot configure ICC It is not legal to configure MD Change MA name to format other ICC.
with MD name name when MA name format
is ICC.
OAM CFM: Cannot delete a You tried to delete a remote Disassociate the remote MEP from the
remote MEP that is being used MEP from MEP configuration, Dest NE and then delete it.
by a dest-ne while this remote MEP is being
used in one of the MEPs Dest
NEs as remote peer address.
OAM CFM: Cannot delete destne; You tried to delete or shut Wait until RFC2544 test has completed,
it is bound to rfc2544 test. down a Dest NE that is used and then delete or shut down the Dest
on an active RFC2544 test. NE.
OAM CFM: Cannot delete MEP; You tried to delete a MEP Finish using the MEP under the Y.1564
MEP is under Y.1564 test. which is being used in a test, and then delete it.
Y.1564 test.
OAM CFM: Cannot delete or You tried to modify or delete a Remove the Bin profile from the Dest
change measurement profile used Bin profile. NE, and then modify or delete it.
first remove from dest-NE
OAM CFM: Cannot enable loss You tried to configure user Configure Dest NE without a multicast
measurement because pm is in data loss measurements on a address or use another loss
multicast Dest NE with multicast measurement method.
destination address.
OAM CFM: Cannot enable service You are trying to enable (no Enable the MEP (no shutdown).
while the MEP is not active shutdown) a service of one of
the MEPs priority bits, while
the MEP is not enabled
(shutdown).
OAM CFM: Cannot have a dest- You tried to configure remote Activate MEPs CCM or use remote-mac.
NE remote MEP-ID when CCM is MEP Id on the Dest NE while
disabled MEPs CCM is not active.
OAM CFM: Cannot modify a You tried to change remote Shut down the service, delete the Dest
remote MEP while it is being MEP parameters in MEP NE that uses this remote MEP or
used configuration while the change its configuration to remote
Remote MEP is being. used MAC.

OAM CFM: Cannot resolve this You are using remote MEP ID Use a remote MEP ID only of remote
remote MEP MAC address for loopback or linktrace MEP MAC address that was learned by
transmission, but the remote the CCM.
MEP MAC address was not
learned by the CCM yet.
OAM CFM: Cannot send more You sent more than one Send only one LB message to multicast
than one LB to multicast loopback message to the same address.
address multicast destination address
of the MEP. All relevant remote
MEPs should answer one LBR
from every remote MEP.
OAM CFM: Cannot shutdown You tried to disable a MEP Finish using the MEP under the Y.1564
MEP; MEP is under Y.1564 test. which is being used in a test, and then disable it.
Y.1564 test.
OAM CFM: Classification: Conflict You previoulsy configured Configure the MEP with a different
with another MEP classification another MEP with the same classification.
parameters.
OAM CFM: Classification: Inner You tried to configure a MEP Configure the MEP with a supported
VLAN range is not supported with a non-supported flow flow classification.
classification.
OAM CFM: Classification: You tried to configure a MEP Configure the MEP with a supported
Unsupported criteria with a non-supported flow flow classification.
classification.
OAM CFM: Classification: VID=0 You configured an Illegal VLAN Configure a VLAN with ID other than 0
is invalid on a MEP. on the MEP.
OAM CFM: Client MD level must You tried to configure a client Configure client MD level higher than
be higher than MD level Maintenance Domain Level MD level.
(MDL) lower than or equal to
the MDL.
OAM CFM: Conflict between You configured a destination Select a valid destination MAC address.
OAM destination MAC address MAC address that conflicts
and device MAC address with the devices MAC address.
OAM CFM: Deactivate service You did not deactivate service Deactivate service, and then erase last
before erasing last dest-NE before erasing last active Dest active Dest NE under it.
NE under it.
OAM CFM: dest-NE out of range You configured Dest NE ID out Confiugre a Dest NE ID between 1 and
the range 1..255. 255.
OAM CFM: EVC.COS: Illegal You did not configure Local Configure Local MEP Id.
remote MEP configuration MEP Id (can only occur via
SNMP).
OAM CFM: EVC.COS: More than 1 You tried to configure two Configure only one MEP on the same
MEP on the same MA is only MEPs on the same MA. MA or use vlan.p_bit classification for
allowed when all classifications all MEPs on MA.
are VLAN + pBit

OAM CFM: EVC.COS: Priority bit You did not configure EVC.cos Configure the EVC.cos MEPs flow
doesn't match classifier MEPs flow classification to classification to match the MEPs
match the MEPs configured configured priority.
priority.
OAM CFM: EVC.COS: Two MEPs You tried to configure two Configure two MEPs on the same MA
on the same MA must use MEPs on the same MA with with different priorities.
classifiers with same VLAN and same priority.
different priorities
OAM CFM: Event type must be You tried to configure for Configure an event for the Fault CFM
different than none unavailability, a Fault CFM frame report entity.
frame report entity that has
no event.
OAM CFM: Exceeded number of You tried to define more than Define only up to 100 fault CFM
entries in alarmTable 100 fault CFM entities. entities.
OAM CFM: Falling On Fault CFM entity, you Configure a lower limit for alarm falling,
alarm_threshold must be less configured a lower limit for which is lower than the higher limit of
than rising alarm_threshold alarm falling, which is higher alarm rising.
than the higher limit of alarm
rising.
OAM CFM: FPGA supports up to You tried to configure Bin Configure Bin profile limit which is up
1000000 uSec (1 second) profile limit which is higher to 1 second.
threshold than 1 second.
OAM CFM: Illegal change of You tried to change the

bounded port bounded port from a Bridge
Port to a regular port or vice
versa.
OAM CFM: Illegal MAC address You configured the MAC Configure a valid MAC address.
address with all zeroes or all
ones.
OAM CFM: Illegal queue block You did not configure a queue Configure a queue block on the MEP.
block on the MEP.
OAM CFM: Illegal value CFM entity was configured Configure CFM entity with legal indices.
with illegal or out of range
indices (for example, loopback
on an active CFM loopback).
OAM CFM: Invalid falling You configured the falling Configure the falling threshold
threshold threshold to less than one-of- between one-of-thousand and 1000
thousand or higher than 1000 one-of-thousand. Make sure that the
one-of-thousand. Or you falling threshold value is lower than the
configured the falling rising threshold.
threshold to a higher value
than the rising threshold.
OAM CFM: Invalid forwarding You configured E-LAN Configure another forwarding method.
method for MEP with direction forwarding method on a Down
set to down MEP.

OAM CFM: Invalid rising You configured the rising Configure the rising threshold between
threshold threshold to less than one-of- one-of-thousand and 1000 one-of-
thousand or higher than 1000 thousand. Make sure that the rising
one-of-thousand. Or you threshold value is higher than the
configured the rising threshold falling threshold.
to a lower value than the
falling threshold.
OAM CFM: Invalid time interval You tried to configure a fault Configure an interval between 1 and
CFM interval which is shorter 60 seconds.
than 1 second or longer than
60 seconds.
OAM CFM: Lmm and dmm You configured lmm-synthetic Configure one second on both lmm and
intervals must be equal if lmm- while in the service level, but dmm.
synthetic was selected you also set lmm or dmm
intervals to be different than 1
second.
OAM CFM: Local MEP-ID and You assigned the same ID to a Configure the remote MEP and local
remote MEP-ID are equal remote MEP and local MEP. MEP with different IDs.
OAM CFM: MA and MEP VLAN You configured a classification Configure a classification VLAN on the
don't match VLAN on MA level that does MA level to match the configured
not match the configured classification VLAN on the MEP level.
classification VLAN on the MEP
level.
OAM CFM: MA name max length You configured an MA name in Configure an MA name in ICC format up
is 13 characters when format is ICC format more than 13 to 13 characters long.
ICC characters long.
OAM CFM: MA-ID size exceeds You defined an MD or MA Define an MD or MA name that is not
limit name length that is longer longer than the maximum allowed
than the maximum allowed length.
length.
OAM CFM: Max allowed dest-NEs You tried to add more than Configure up to the allowed number of
in active services already allowed maximum Dest NEs. Dest NEs.
reached
OAM CFM: Max allowed number You already configured the Configure up to the allowed number
of remote MEPs reached maximum allowed number of remote MEPs per device.
remote MEPs on the device.
OAM CFM: MD level out of range You configured an MD level Configure an MD level between 0 and
that is smaller than 0 or bigger 7.
than 7 (can happen only via
SNMP).
OAM CFM: MEP direction is not You bound the MEP to the Bind a MEP of the correct direction to a
correct for port type wrong port. For example: You port.
bound a Down MEP to a Bridge
port or an UP MEP to an SVI.

OAM CFM: MEP must be active You tried to send LBM or LTM Activate MEP, and then send LBm or
for this action on a non-active MEP. LTM.
OAM CFM: MEP out of range You configured a MEP ID Configure a MEP ID between 1 and
outside the range 1..8191 8191.
OAM CFM: Name cannot be You did not configure an MD Configure a name for MD or MA.
empty or MA name.
OAM CFM: Name length too long You configured an illegal MD or Configure an MD/MA name up to 43
MA name length (more than characters.
43 characters).
OAM CFM: NE remote MEP-ID or You tried to define Dest NE Define a Dest NE that has different
MAC address conflicts with that has same indices as an indices than an existing Dest NE.
another NE on the current existing Dest NE.
service
OAM CFM: No port is bound to You tried to activate a MEP Bind a port to the MEP.
MEP with no bounded port.
OAM CFM: Only 10 TX flows per You tried to configure more Configure up to 10 Tx flows.
MEP are allowed than 10 Tx flows on a MEP.
OAM CFM: Only one destne can You tried to configure more Configure only one Dest NE on a
be configured if loss user data than one Dest NE on a service service with User Data Loss
was selected with User Data Loss measurement method.
measurement method.
OAM CFM: Only one RX flow per You tried to configure more Configure only one Rx flow on the MEP.
MEP is allowed than one Rx flow on a MEP.
OAM CFM: Please make sure you You configured a MEP to work When MEP is shutdown, configure a
configure a unicast type and with unicast destination valid unicast address as destination
MAC address when MEP is address, but did not configure address.
shutdown a valid unicast address as
destination address.
OAM CFM: Port is occupied with You tried to send loopback or Send loopback or linktrace only when
another action linktrace while there is another no other loopback or linktrace
active loopback or linktrace respectively, is active.
respectively.
OAM CFM: Port level MEP: Only You tried to configure more Configure only one MEP on an
one allowed per port than one MEP on an untagged untagged port.
port.
OAM CFM: Priority out of range You configured a Priority that Configure a Priority between 0 and 7.
is smaller than 0 or bigger
than 7 (can happen only via
SNMP).
OAM CFM: Profile must have You tried to use a flow with Use a flow with only one VLAN
only one entry multiple VLANs matching matching classification.
classification.
OAM CFM: Profile was not found You used a wrong or non- Use a correct or existing profile.
existing profile.

OAM CFM: Remote MEP doesn't You tried to configure a Configure the remote MEP ID at the
exist remote MEP Id at the Dest NE, MEP as Remote.
as remote peer address, but
this Remote MEP Id is not
configured at the MEP as
Remote.
OAM CFM: Remote MEP ID You tried to configure a Configure the remote MEP with an ID
cannot be equal to local MEP ID remote MEP with the same ID that is different than the MEP ID.
as the MEP itself.
OAM CFM: rfc2544 test is in You tried to change the status Wait until RFC2544 test terminates,
progress; cannot enable service of a service that one of its and then change the services status.
Dest NEs is used on an active
RFC2544 test.
OAM CFM: Service out of range You configured a service ID Configure a service ID between 1 and
OAM CFM: The Rx and Tx flows You configured Rx and Tx Configure Rx and Tx flows to start and
must be in opposite directions. flows so that they do not start end on opposite Ingress and Egress
and end on opposite Ingress ports.
and Egress ports.
OAM CFM: The Rx flow must You configured manual MIP, so Configure the Rx flows Ingress port to
originate from the bound port. that Rx flows Ingress port is be equal to the MIPs bound port.
not equal to the MIPs bound
port.
OAM CFM: There is no MEP with You tried to create an entry in Connect the flow to a MEP that already
those indices the MepFlow table and to exists.
connect between a flow and a
MEP that does not exist (can
only occur via SNMP).
OAM CFM: VID out of range You configured a VLAN ID Configure a VLAN ID between 1 and
OAM CFM: When using untagged You tried to configure a MEP Configure a MEP with EVC.cos
or EVC.COS MEP classification with EVC.cos classification and classification and Service Id equal to 1.
only service index 1 is permitted Service Id other than 1.
OAM CFM: MEF-46 should have You tried to configure MEF-46 Configure MEF-46 on a MEP that is
Tx/Rx flow classification on a MEP that is configured configured with Rx and Tx flows.
with a classifier profile or
VLAN.
11.3 OAM EFM

Ethernet OAM (Operation, Administration, and Maintenance) functions provide
end-to-end connectivity checks and performance monitoring.
ETX-2i OAM EFM 11-61

Ethernet in the First Mile (EFM) is a link-layer OAM protocol that operates at the
level of the single link for remote management and fault indication. ETX-2i can
act as the active or passive side in an IEEE 802.3ah application.
The term last mile is often used by core network engineers to refer to access
links from an operators central office to the customers locations. The opposite
term first mile refers to the same access links but from the customers
perspective.
This section covers the monitoring of the Ethernet links using OAM EFM (OAM
Ethernet at the First Mile). ETX-2i can act as the active or passive side in an IEEE
802.3-2005 application.
Applicable Products
Standards
IEEE 802.3-2005
Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
The OAM (EFM) discovery process allows a local data terminating entity (DTE) to
detect Ethernet OAM capabilities on a remote DTE. Once Ethernet OAM support
is detected, both ends of the link exchange state and configuration information,
such as mode, PDU size, loopback support, etc. If both DTEs are satisfied with
the settings, OAM is enabled on the link. However, the loss of a link or a failure
to receive OAMPDUs for five seconds may cause the discovery process to
restart.
DTEs may either be in active or passive mode. DTEs in active mode initiate the
ETH-OAM (EFM) communications and can issue queries and commands to a
remote device. DTEs in passive mode generally wait for the peer device to
initiate OAM communications and respond to commands and queries, but do not
initiate them.
A flag in the OAMPDU allows an OAM entity to convey the failure condition Link
Fault to its peer. Link Fault refers to the loss of signal detected by the receiver;
A Link Fault report is sent once per second with the Information OAMPDU.
Factory Defaults
By default, OAM EFM is not enabled for Ethernet/logical MAC/PCS ports.
11-62 OAM EFM ETX-2i

Configuring OAM EFM

There are two available OAM EFM descriptors. Each can be configured to indicate
active or passive OAM EFM. When you enable OAM EFM for a port, you assign a
descriptor to the port.
You can configure OAM EFM for Ethernet/logical MAC/PCS ports. When link OAM
(EFM) is enabled for a port, you can view its status by displaying the port status
(show status). You can also display the OAM (EFM) parameters and OAM (EFM)
statistics.
To configure OAM EFM descriptor:

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

1. Navigate to configure port ethernet [<slot>/]<port> or
configure port logical-mac <port> or configure port pcs <port>, respectively.
The prompt config>port>eth([<slot>/]<port-num>)# or
config>port>log-mac(<port>)# or config>port>pcs(<port>)# is
displayed.
Enabling link OAM (EFM) efm descriptor <12> The EFM descriptor must exist
before you can assign it to a port
Note: In order for link OAM (EFM)
to function properly, the relevant
Ethernet port must be associated
with an L2CP profile that
specifies peer action for MAC
0x02.
Disabling link OAM (EFM) no efm
Displaying link OAM (EFM) show oam-efm Note: Relevant only for
parameters Ethernet/PCS ports, if link OAM
(EFM) is enabled.
Displaying link OAM (EFM) show oam-efm-statistics Note: Relevant only for
statistics Ethernet/PCS ports, if link OAM
(EFM) is enabled.
Commands in level efm
Enabling loopback loopback Type no loopback to disable

loopback.
Enabling SNMP tunneling for OAM snmp-tunneling Type no snmp-tunneling to

EFM disable snmp tunneling.
ETX-2i OAM EFM 11-63

Examples
To enable active link OAM (EFM) Ethernet port 1/1:
#************** Configure L2CP profile for OAM EFM
exit all
mac 0x02 peer
exit all
#************** Configure OAM EFM descriptor

configure oam efm
descriptor 2 active
exit all
#************** Configure Ethernet port 1/1:

#************** Associate L2CP profile and OAM EFM descriptor
efm descriptor 2
exit all
To display the link OAM (EFM) status for Ethernet port 1/1
ETX-2i>config>port>eth(1/1)# show oam-efm
Administrative Status : Enabled
Operational Status : Link Fault
Loopback Status : Off
Information
---------------------------------------------------------------
Local Remote
Mode : Active --
MAC Address : 00-20-D2-30-CC-9D --
Unidirectional : Not Supported --
Vars Retrieval : Supported --
Link Events : Supported --
Loopback : Supported --
PDU Size : 1518 --
Vendor OUI : 0x0020D2 --
11.4 TWAMP
The full Two-Way Active Measurement Protocol (TWAMP) consists of two parts:
TWAMP Control Layered over TCP; used to initiate, start, and stop
measurement sessions
TWAMP Test Layered over UDP; used to exchange test packets between
two measurement nodes. The TWAMP Test includes three
tests: TWAMP Light, ICMP Echo, and UDP Echo.
11-64 TWAMP ETX-2i

ETX-2i provides a low-scale (150 sessions) TWAMP Light mechanism over

VxWorks for measurement of one-way and two-way metrics between network
elements.
Applicable Products
Standards
RFC 5357 A Two-Way Active Measurement Protocol (TWAMP)
RFC 2330 Framework for IP Performance Metrics
RFC 2681 A Round-trip Delay Metric for IPPM
RFC 4656 A One-way Active Measurement Protocol (OWAMP)
RFC 5481 Packet Delay Variation Applicability Statement
RFC 4737 Packet Reordering Metrics
RFC 5560 A One-Way Packet Duplication Metric
ITU-T Y.1540 Internet protocol data communication service IP packet
transfer and availability performance parameters
ITU-T Y.1541 Network performance objectives for IP-based services
ITU-T Y.1543 Measurements in IP networks for inter-domain performance
assessment
Benefits
TWAMP measures the IP performance of Layer-2 or 3 networks at all locations,
without the need for a special performance management system. Its ICMP Echo
service is useful for probing and general debugging, such as path continuity and
integrity verification.
ETX205A with PMC provides the full TWAMP feature: TWAMP Control and
TWAMP Test.
Full TWAMP supports the following:
IPv4 and IPv6, tagged and untagged, TWAMP frame format
PCP, DSCP, and TC (IPv6) for TWAMP generated traffic
Up to 64 TWAMP controllers and eight responders. Each controller and
responder is associated with a router interface within the configured router
entity, with the same IP address as the controller/responder. Controllers and
responders can reside on the same VRF or on different VRFs (up to four).
TWAMP controller supports up to 3,000 peers and up to 3,000 test sessions.
ETX-2i TWAMP 11-65

Maximum rate per session: 10 pps for TWAMP peers.

PMC controllers and responders each support timestamp accuracy of at least
50 usec; 80 usec for one-way and 2 msec for RADM.
Status and statistics
Responder functionality, at a different IP address than the controller.
Up to eight responders that together handle a total of 100 test sessions,
simultaneously with the 3000 sessions initiated by the controllers residing
on the same device.
PMC supports Responder Agnostic Delay Measurement (RADM), which
enables one-way delay and delay variation measurements without requiring
the controller or responder to be ToD locked.
Multiple VRFs up to 4
Setting Up a Connection on the Client Side

A connection is established between a TWAMP Controller and Responder on the
Client side, as follows:
1. You request (via CLI or SNMP) to create a peer between a TWAMP Controller
and a TWAMP Responder.
2. You optionally configure the TCP port on which the control connection
(peer) to the server is to be established. Default is 862.
3. The agent validates that the TCP port value that you selected is < 49151. If
not, it rejects your configuration attempt.
4. The control-client connection to the TWAMP server takes place on the TCP
port (default or configured), via the TWAMP connection setup procedure.
5. The client automatically selects the source TCP port for the control
connection in the range of 4915265535. This TCP port number shall be
used for all control connection to different responders, and client shall
distinguish received control traffic based on source IP address of the
responders. Note that you cannot configure the source TCP port.
6. The client supportsonly unauthenticated, unencrypted mode ( open mode).
7. When the connection is established with the server, the client timestamps
its local time, and uses it when you request peer-information (peer-level
show status command).
Setting Up Connection on Server Side

A connection between a TWAMP Controller and Responder is established on the
Server side, as follows:
1. You enable Control protocol at the server side by configuring the Responder
without an IPPM type.
2. You optionally configure the TCP port on which the server is to listen for
connection attempts from the client. Default is 862.
3. The agent validates that the TCP port value that you selected is < 49151. If
not, it rejects the configuration attempt.
4. The server supports multiple peers, initiated from different clients.
11-66 TWAMP ETX-2i

5. The server accepts or rejects client attempt for connection.

After a connection has been made between the client and zerver, the client
must send to the server a request for each test session it wants to open on the
peer, as described below.
TWAMP Session Request on Client Side

1. The client sends a single request for each test session it wishes to open on
the peer.
2. The source and destination UDP port of the outgoing TWAMP test packets
for the requested sessions are conveyed to the server.
3. The client monitors whether the test session has been accepted by the
server. If it has been rejected, the client raises an event.
TWAMP Session Request on Server Side

1. The server listens to TWAMP control messages from the client. If the request
is not valid, the server rejects it and raises an event.
2. If the request is valid, the server sends the client the UDP port value, so that
the client is aware that the UDP port is available at the reflector, and the
sender can commence test session on this UDP port. This UDP port is used
by the session sender as the destination UDP port for the transmitted test
packets.
3. If this UDP port is not available at the responder side, server sends an
alternate UDP port value.
4. Server configures the reflector to listen on this UDP port.
Starting Test Session Client Side

1. The client sends a request to initiate all test sessions provisioned with the
servers endpoint.
2. If the start session request is accepted by the TWAMP server, it must
commence as soon as possible. Otherwise, if it is rejected, the client
terminates the TCP connection with the server, and raises an event.
3. When you send a no activate command on the selected peer, or the peers
configured test duration expires, all test sessions on the peer are
terminated.
Starting Test Session Server Side

If the server decides to acknowledge starting the test session request from
the client, it configures the reflector to start processing the test packets to
be received from all peers test sessions. It then sends to the client the
acknowledgement to initiate test sessions.
You can configure the PMC to run full TWAMP, as described in Configuring PMC.
TWAMP Tests
TWAMP tests, a part of the Full TWAMP protocol, is layered over UDP; it is used
to exchange test packets between two measurement nodes.
ETX-2i TWAMP 11-67

The ETX-2i TWAMP controller supports the following TWAMP test protocols:
TWAMP Light (one-way or round-trip)
ICMP Echo (only round-trip)
The test protocol type (TWAMP Light or ICMP Echo) is defined per peer towards
specific responder. It is possible to operate mixed protocols (TWAMP Light and
ICMP Echo) per peer in the same TWAMP controller.
When the TWAMP responder receives a test packet, it reflects the test packet
after it adds an Rx stamp, a Tx stamp, and the following (if configured
accordingly):
Independent sequence number (tx-seq-num enabled)
Indication of forward fragmentation (tx-extended-info enabled)
Indication of responder ToD synchronization status (tx-extended-info
enabled)
When the TWAMP controller receives a test packet from the responder, it
calculates the following:
Delay Responder Rx stamp Controller Tx stamp + Controller Rx

stamp - Responder Tx stamp
Forward Delay Responder Rx stamp Controller Tx stamp
Backward Delay Controller Rx stamp Responder Tx stamp
Packet Validity Determined by checking if the delay is less than the value
configured by command loss-timeout. If so, the Rx valid
count is incremented, otherwise the packet is dropped.
ToD Controller Derived from the controller local NTP client:

Status notApplicable NTP client is not active.
unknown NTP client is acquiring clock sources.
sync NTP client accuracy is within the limits.
out-of-sync NTP client accuracy is not within the limits.
ToD Peer Status Calculated only for a peer with one-way calculation mode:
unknown tx-extended-info is disabled.
sync tx-extended-info enabled and responder ToD is
synchronized.
out-of-sync tx-extended-info enabled and responder ToD
is not synchronized.
TWAMP Light Test
Note This test can be run on any ETX-2i device.
The TWAMP Light mechanism provides for monitoring sessions where

information is exchanged between TWAMP controllers and responders. The
controller establishes the test session with the responder. After the TWAMP test
session is established, the controller transmits test packets to the responder,
11-68 TWAMP ETX-2i

which reflects the test packets to the controller. The controller processes the
resulting measurements and calculates metrics that can be displayed in test
reports (see Viewing TWAMP Reports).
In addition to viewing the metrics in the test reports, you can also view them via
the RADview Performance Management portal, if collection of PM statistics for
the OAM TWAMP component is enabled (via pm-collection command in the
reporting level). Refer to the Performance Management section in the
Monitoring and Diagnostics chapter for details.
TWAMP controllers and responders can operate in the following modes:
Layer-2 E-Line (pont-to-point) service L2 probe configuration; The TWAMP
controller/responder is associated with a router interface and bound to an
Ethernet/logical MAC/PCS port and flow.
IPv6 test sessions are not supported in this mode.
Up to a total of three controllers and responders are supported.
Figure 11-3. TWAMP Controller over L2 E-Line Service
Layer-2 E-LAN service over bridge The TWAMP controller/responder is

associated with a router interface that is connected to a bridge port via an
SVI.
Figure 11-4. TWAMP Controller over Bridge (E-LAN Service)
ETX-2i TWAMP 11-69

Layer-3 The TWAMP controller/responder is associated with a router

interface that is connected to an Ethernet port via an SVI.
This configuration is relevant to embedded router only
A Layer-3 router interface ACL can be configured on the router interface.
Figure 11-5. TWAMP Controller over Router Interface

TWAMP can be configured on an independent VRF. A total of seven
controllers/responders can be configured (for example, three controllers and
four responders).
The TWAMP controller/responder and router interface must be configured with
the same IP address. The TWAMP controller/responder is defined to have IP
connectivity when the following conditions are met:
Controller/responder local IP address is configured.
Associated router interface is configured and administratively enabled.
Controller/responder is bound to a port (if TWAMP mode is layer-2 E-Line).
Related SVI and flows are configured (TWAMP in ETX-2i)
ICMP Echo Test
Note This test can be run on any ETX-2i device.
ETX-2i supports the two-way (round trip) ICMP Echo test, a member of the
TWAMP tests. It is a useful tool for testing and debugging path continuity and
integrity verification.
The test, supported for both IPv4 and IPv6, is based on ICMP/ICMPv6 Echo
request/reply packets. The ICMP Echo test is defined per peer towards a specific
responder, which can be any device or workstation with standard IPv4/IPv6 stack
that responds to standard ICMP/ICMPv6 Echo request packets. The ICMP peer can
generate multiple ICMP Echo test sessions to the same responder; these tests
differ in ICMP identifier, and possibly in packet length and DSCP. The ICMP peer
can generate ICMP Echo tests in continuous and non-continuous modes.
Prior to running the ICMP Echo test, you are required to configure the following
parameters:
Test packet definition:
Destination IP (peer level)
DSCP
11-70 TWAMP ETX-2i

Packet length
Transmit rate (pps)
Report/event/ alarm definition:
Loss timeout
Loss threshold
Delay threshold
Delay variation threshold
You do not configure peer parameters for the ICMP Echo test. The calculation
mode is not configurable; it is automatically set to default (round-trip). The
responder sequence number is also set to its default (off).
ICMP Echo test is performed as follows:
1. ICMP Echo IPv4/IPv6 test generates test packets based on IPv4/IPv6 ICMP
Echo request standard packets.
2. ICMP Echo builds test packets with:
Test session identifier
Controllers transmit sequence number
Controllers transmit timestamp
3. Controller identifies received packet according to ICMP identifier (represents
test session).
4. Packets round trip delay is calculated according to received and transmitted
timestamps.
5. Loss, duplicate, and reorder are calculated according to sequence number.
6. Metrics are calculated for roll-up window, current interval, and report interval
(as defined for TWAMP).
7. Metrics are collected, according to PM collection mechanism (as defined for
TWAMP).
8. ICMP Echo test events and alarms are generated as TWAMP events and
alarms with the same definitions.
Delay result (na / pass / fail)
DV result (na / pass / fail)
Loss result (na / pass / fail)
Factory Defaults
By default, no controllers or responders are configured.
Configuring TWAMP
You can configure low-scale (150 sessions) TWAMP in an ETX-2i device.
To configure TWAMP in an ETX-2i device, perform the following steps:
1. In the responder device:
ETX-2i TWAMP 11-71

a. Configure relevant SVI port (relevant for ETX-2i TWAMP; not in PMC
TWAMP in ETX205A) , router interface, and flows.
b. Configure relevant SNTP server(s).
c. Configure and activate TWAMP responder and relevant test session(s).
2. In the controller device:
a. Configure relevant SVI port, router interface, and flows.
b. Configure relevant SNTP server(s).
c. Configure TWAMP profile(s).
d. Configure and activate TWAMP controller, relevant peers, and test
sessions.
Configuring Controllers
To configure a TWAMP Light controller of an ETX-2i device:
1. Navigate to configure oam twamp.
The config>oam>twamp# prompt is displayed.
2. To configure the TWAMP controller, enter:
controller <name> [<number>] [light] [l2-probe]
Note The parameter l2-probe specifies that the controller is working in mode Layer-2
E-Line service (see Functional Description).
The config>oam>twamp>controller(<name>/light)# prompt is displayed.

3. Enter all necessary commands according to the tasks listed in the table
below.
Binding controller to a port bind ethernet <port-index> Can bind controller to a port, only if
bind logical-mac <port-number> controller is in layer-2 probe mode.
bind pcs <port-number> Typing no bind deletes definition of
TWAMP ingress and egress port.
Configuring controller local IP local-ip-address <ip-address> Possible values:

address 0 (default) no IP address
IPv4 or IPv6 network address
Defining peer entity peer <ip-address> twamp-light | See Running Test Sessions Via
(corresponding to responder), icmp-echo Controller Peers.
to run TWAMP test sessions
Associating controller with a router-entity <number> The parameter <number> is the

router that contains a suitable router number, in which a router
router interface interface must be configured with the
same IP address as local-ip-address.
Possible values:
0 (default) no router entity
1-Maximum number of router entities
11-72 TWAMP ETX-2i

Associating controller with vlan-tag vlan <vlan> [p-bit <p-bit>] Can associate controller with VLAN
VLAN [inner-vlan <inner-vlan>] only if controller is in layer-2 probe
[inner-p-bit <inner-p-bit>] mode.
Possible values for vlan, inner-vlan:
0-4095, 0xFFFFFFFF (i.e. not
applicable)
Possible values for p-bit, inner p-bit:
0-7
Typing no vlan deletes VLANs for L2
service definition in L2 probe mode.
Administratively enabling or no shutdown Type shutdown to administratively

disabling the controller shutdown disable the controller.
You should enable the controller only
after the responder has been
configured and enabled.
Viewing controller status show status
Running Test Sessions Via Controller Peers

On an ETX-2i device, you can configure up to 150 test sessions of TWAMP Light
(default) and/or ICMP Echo protocols on each peer of a controller.
This section describes how to define the peer entity for a group of TWAMP test
sessions.
To configure TWAMP test sessions in ETX-2i:

1. Navigate to configure oam twamp controller <name> [<number>] light
[l2-probe] peer <ip-address> [twamp-light | icmp-echo].
The config>oam>twamp>controller (<name>/light)> peer(<ip-address>)
[twamp-light | icmp-echo]# prompt is displayed.
below.
Activating all configured test activate duration <minutes> The tests run for the specified amount
sessions in one-time mode of time.
Type no activate to deactivate the
one-time (non-continuous) command.
Possible values for minures: 1-10080
(default: 1 minute)
Activating all configured test activate continuous The tests run until they are stopped.
sessions in continuous mode Type no activate to deactivate the
continuous command.
ETX-2i TWAMP 11-73

Defining the type of calculation-mode { round-trip | one-way round-trip: TWAMP controller peer
calculation for the TWAMP } calculates standard TWAMP metrics
metrics and partial one-way metrics:
Two-way metrics availability, loss,
delay, PDV (packet delay variation),
IPDV (inter-packet delay variation)
Partial one-way metrics IPDV,
duplicate packets, reordered
packets, fragmented packets (no
one-way delay or PDV metrics)
One-way loss and availability
one-way: TWAMP controller peer
calculates one-way metrics:
One-way metrics delay, PDV,
IPDV, duplicate packets, reordered
packets, fragmented packets
One-way loss and availability
11-74 TWAMP ETX-2i

Notes:
This parameter is masked when
using ICMP Echo protocol, as its
value is always round-trip (the
default).
This parameter can be changed
only if there is no active test
session.
You can set one-way mode only if
both the controller and responder
are ToD locked.
One-way loss and availability is
available only if responder is
configured to transmit an
independent sequence number
(tx-seq-num enabled), and
controller is configured accordingly
(responder-seq-num enabled).
One-way delay and PDV metrics are
available only if tx-extended-info
has been enabled in responder, and
it sent indication that its ToD (Time
of Day) is synchronized; the metrics
are accurate only if the controller
ToD is also synchronized.
The fragmented packet count in
the forward direction (controller to
responder) is available only if if tx-
extended-info has been enabled in
the responder, and it sent
indication of fragmentation.
Specifying whether the responder-seq-num Notes:

responder transmits an no responder-seq-num The controller calculates one-way
independent sequence loss and availability only if this is
number enabled.
The corresponding responder must
be configured to transmit the
responder sequence number (via
command tx-seq-num).
This parameter is masked when
using ICMP Echo protocol, as its
value is always off (the default).
ETX-2i TWAMP 11-75

Configuring test session test-session <number> The UDP and DSCP can be used to
[name <name-string>] distinguish between test sessions.
[udp-port <udp-port-number>] UDP port number: 165535
[test-profile <profile-name>]
Test profile name: Up to 32 characters
[dscp <dscp-number>]
DSCP number: 063 (default: 0)
Notes:
The udp-port parameter is masked
when using the ICMP Echo protocol.
iewing test report show report <name> all See Viewing TWAMP Reports.
show report <name> current
show report <name> interval
<interval-num>
Viewing summary of test show summary-report See Viewing TWAMP Reports.

reports
Viewing test status show status See Viewing TWAMP Status.
Configuring Test Profiles

You can configure test profiles to associate with a test session.
To configure TWAMP test profiles:
2. To configure a test profile, enter:
profile <name> [<number>]
The config>oam>twamp>profile(<name>) prompt# is displayed.
Defining delay threshold in delay-threshold <s>

microseconds
Configuring delay variation delay-variation-event-type {pdv | ipdv} pdv Packet delay variation metric
event type to define whether ipdv Inter-packet delay variation
the PDV or IPDV metric is metric
used for the delay threshold
See RFC 5481 for details on these
metrics.
Defining delay variation delay-variation-threshold <s>

threshold in microseconds
Defining test packet loss loss-timeout <msec>

timeout in microseconds
Defining test packet payload payload-length <bytes> Possible values: 371472

length in bytes
11-76 TWAMP ETX-2i

Defining test profile packet transmit-rate <pps> Note: In layer-2 probe mode, 150 pps
transmit rate in PPS is possible only if the test packet
payload length is not greater than 170.
Configuring Responders
This section describes how to create a TWAMP responder entity.
To configure a TWAMP Light responder of an ETX-2i device:
2. To configure the TWAMP Light responder, enter:
responder <name> [<number>] [light] [l2-probe]
Note The parameter l2-probe specifies that the responder is working in mode Layer-2
E-Line service (see Functional Description).
The config>oam>twamp>responder(<name>/light)# prompt is displayed.

below.
Binding responder to a port bind ethernet <port-index> Can bind responder to a port, only if
bind logical-mac <port-number> responder is in layer-2 probe mode.
bind pcs <port-number> Typing no bind deletes definition of
TWAMP ingress and egress port.
Defining whether to provide tx-extended-info

indication of fragmentation no tx-extended-info
in forward path, and status
of ToD (Time Of Day)
synchronization
Configuring responder local local-ip-address <ip-address> Possible values:

IP address 0 (default) no IP address
IPv4 or IPv6 network address
Associating responder with a router-entity <number> The parameter <number> is the router
router that contains a number, in which a router interface
suitable router interface must be configured with the same IP
address as local-ip-address.
Possible values:
0 (default) no router entity
1-Maximum number of router entities
ETX-2i TWAMP 11-77

Associating responder with a test-session <number> Typing no test-session <number>

test session [name <name-string>] [name <name-string>] deletes the test
[udp-port <udp-port-number>] session entity.
Note:
For TWAMP Light only
Defining whether responder tx-seq-num Notes:

transmits an independent no tx-seq-num The responder independent
sequence number, rather sequence number can be used by
than copying the received the controller to calculate one-way
sequence number into the loss and availability.
transmitted packet
The corresponding controller must
be configured to indicate that the
responder sequence number is
being transmitted (via command
responder-seq-num).
Associating responder with vlan-tag vlan <vlan> [p-bit <p-bit>] Can associate responder with VLAN<
VLAN [inner-vlan <inner-vlan>] only if responder is in layer-2 probe
[inner-p-bit <inner-p-bit>] mode.
Possible values for vlan, inner-vlan:
0-4095, 0xFFFFFFFF (i.e. not
applicable)
Possible values for p-bit, inner p-bit: 0-
7
Typing no vlan deletes VLANs for L2
service definition in L2 probe mode.

disabling the responder shutdown disable the responder.
Viewing responder status show status See Viewing TWAMP Status.
Viewing TWAMP Status

You can view the status of the controller, responder, or peer test sessions, in
any device, as well as in the PMC of ETX205A with PMC, using the show status
command in the following levels.
Controller status show status in level config oam twamp controller
Responder status show status in level config oam twamp responder
Peer test sessions show status in level config oam twamp controller peer
status
Viewing TWAMP Reports

After you configure round-trip or one-way metrics calculation for each peer via
command calculation-mode (see Running Test Sessions Via Controller Peers) you
can generate the TWAMP report.
11-78 TWAMP ETX-2i

The TWAMP controller calculates performance measurement metrics according to

the received test packets for each peer and its active test sessions. The metrics
are recalculated every minute. In the TWAMP report, you can view the metrics
for the current interval, selected interval, or all intervals. You can also view the
metrics via the RADview Performance Management portal if TWAMP PM
collection is enabled (see the Performance Management section for details).
To view a summary report of all peer test sessions:

1. Navigate to configure oam twamp controller peer.
The config>oam>twamp>controller>peer# prompt is displayed.
2. Type show summary-report.
To view a report of all intervals in a specific peer test session:

2. Type show report <name> all.
To view a report of the current interval in a specific peer test session:

2. Type show report <name> current.
To view a report of a specific interval in a specific peer test session:

2. Type show report <name> interval <interval-num>.
The following table lists the metrics that are displayed in the TWAMP reports,
subject to the restrictions specified above for the calculation modes. See
Example Viewing TWAMP Reports for examples of TWAMP reports.
Table 11-8. TWAMP Report Metrics
Counter Description
Tx Packets Fwd Number of packets transmitted in forward direction (controller to responder)
Tx Packets Back Number of packets transmitted in backward direction (responder to controller)
Loss Packets Fwd Number of packets lost in forward direction, calculated by Tx Packets Fwd
Rx valid count
Loss Packets Back Number of packets lost in backward direction, calculated by Tx Packets Back
Rx valid count
Loss Ratio Fwd Loss Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Loss Ratio Back Loss Packets Back divided by Tx Packets Back, converted to a percentage
ETX-2i TWAMP 11-79

Counter Description
Availability Count Fwd (sec) Number of available seconds in forward direction. A (forward) minute is declared
as unavailable if it has more than 75% packet loss in forward direction,
therefore it is available if packet loss in forward direction is 25% or less. When a
minute is declared unavailable, the delay, delay variation, loss measurements,
and their derived metrics are ignored for that minute.
Availability Count Back (sec) Number of available seconds in backward direction. A (backward) minute is
declared as unavailable if it has more than 75% packet loss in backward
direction therefore it is available if packet loss in backward direction is 25% or
less. When a minute is declared unavailable, the delay, delay variation, loss
measurements, and their derived metrics are ignored for that minute.
Duplicate Packets Fwd Number of duplicate packets in forward direction. A packet is considered
duplicate (forward) if its controller sequence number or controller Tx timestamp
matches that of a previously received packet in forward direction.
Duplicate Packets Back Number of duplicate packets in backward direction. A packet is considered
duplicate (backward) if its responder Tx timestamp matches that of a previously
received packet in backward direction.
Duplicate Ratio Fwd Duplicate Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Duplicate Ratio Back Duplicate Packets Back divided by Tx Packets Back, converted to a percentage
Reordered Packets Fwd Number of reordered packets in forward direction. A packet is considered
reordered (forward) if its controller sequence number or controller Tx timestamp
is smaller than that of a previously received packet in forward direction.
Reordered Packets Back Number of reordered packets in backward direction. A packet is considered
reordered (backward) if its responder sequence number is smaller than that of a
previously received packet in backward direction.
Reordered Ratio Fwd Reordered Packets Fwd divided by Tx Packets Fwd, converted to a percentage
Reordered Ratio Back Reordered Packets Back divided by Tx Packets Back, converted to a percentage
Fragmented Packets Fwd Number of fragmented packets in forward direction. When the TWAMP
responder receives a fragmented packet, when it reflects it to the controller, the
responder sends indication of fragmentation, if tx-extended-info was enabled.
When this indication is received, the controller increments the Fragmented
Packets Fwd counter.
Fragmented Packets Back Number of fragmented packets in backward direction. When the TWAMP
controller recognizes a fragmented packet, it increments the Fragmented
Packets Back counter.
Delay-Fwd Threshold Crossing Number of packets in forward direction with delay larger than the delay
Count threshold configured for the corresponding test profile
Delay-Back Threshold Number of packets in backward direction with delay larger than the delay
Crossing Count threshold configured for the corresponding test profile
Delay-Fwd Min (ms) Minimum of packet delay values in forward direction
Delay-Fwd Max (ms) Maximum of packet delay values in forward direction
Delay-Fwd Average (ms) Average of packet delay values in forward direction
Delay-Back Min (ms) Minimum of packet delay values in backward direction
11-80 TWAMP ETX-2i

Counter Description
Delay-Back Max (ms) Maximum of packet delay values in backward direction
Delay-Back Average (ms) Average of packet delay values in backward direction
PDV-Fwd Max (ms) Maximum of PDV (Packet Delay Variation) values in forward direction. Packet
Delay Variation is calculated according to ITU-T Y.1540, by subtracting the
minimum delay from the 99.9% percentile of the delay values
PDV-Fwd Average (ms) Average of PDV (Packet Delay Variation) values in forward direction, calculated
by subtracting Delay-Fwd Min from Delay-Fwd Average
PDV-Back Max (ms) Maximum of PDV (Packet Delay Variation) values in backward direction
PDV-Back Average (ms) Average of PDV (Packet Delay Variation) values in backward direction
IPDV-Fwd Max (ms) Maximum of IPDV (Inter Packet Delay Variation) values in forward direction. Inter
Packet Delay Variation is calculated according to RFC 5481, from the variations
of the delays between valid packets.
IPDV-Fwd Average (ms) Average of IPDV (Inter Packet Delay Variation) values in forward direction
IPDV-Back Max (ms) Maximum of IPDV (Inter Packet Delay Variation) values in backward direction
IPDV-Back Average (ms) Average of IPDV (Inter Packet Delay Variation) values in backward direction
Examples
Example Configuring TWAMP in Layer-2 E-Line Service Mode

This example illustrates configuring TWAMP in mode Layer-2 E-Line service:
Controller with IP address = 11.11.11.1
Responder with IP address = 11.11.11.2
To configure the responder:

Router: Associate Interface 2 with SVI 2.
Flows between Ethernet ports 0/1 and 0/3:
VLAN 100
No policer
Test session:
UDP port 999
exit all
#*********Configure SVI for TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit

flows
ETX-2i TWAMP 11-81

match vlan 100

exit
#********* Configure flows between ETH 0/1 & 0/3

flow E1toE3
classifier v100
no policer
no shutdown
exit
flow E3toE1
classifier v100
no policer
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for TWAMP

router 1
interface 2
address 11.11.11.2/24
address 11:11:11::2/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP responder

oam
twamp
responder 1 light l2-prob
bind ethernet 0/1
vlan-tag vlan 100
router-entity 1
local-ip-address 11.11.11.2
test-session 1 udp-port 999
tx-extended-info
tx-seq-num
no shutdown
exit all
save
To configure the controller:

Flows between Ethernet ports 0/1 and 0/3:
VLAN 100
No policer
11-82 TWAMP ETX-2i

Test session:
Profile with payload length 150, and loss timeout 1 second
UDP port 999
DSCP 0
exit all
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit

flow E1toE3
classifier v100
no policer
no shutdown
exit
flow E3toE1
classifier v100
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.11.1/24
address 11:11:11::1/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile

oam
twamp
profile twp1
payload-length 150
loss-timeout 1000000
exit
ETX-2i TWAMP 11-83

#*********Configure TWAMP controller

controller 1 light l2-probe
bind ethernet 0/1
vlan-tag vlan 100
router-entity 1
peer 11.11.11.2
test-session 1 name twamp1 udp-port 999 test-profile twp1 dscp 0
calculation-mode round-trip
responder-seq-num
exit
no shutdown
exit all
save
Example Configuring TWAMP in Layer-2 E-LAN Service Mode

This example illustrates configuring TWAMP in mode Layer-2 E-LAN service:
Controller with IP address = 11.11.101.6

Bridge Activate ports 1, 2, and 3; associate VLAN 1.
Router Associate Interface 2 with SVI 2.
Flows between Ethernet port 1/1 and bridge port 1, and Ethernet port 0/1
and bridge port 2:
Match VLAN 1
No policer
Flows between bridge port 3 and SVI 2:
Bridge port to SVI Match VLAN 1, and pop VLAN.
SVI to bridge port Match all traffic, and push VLAN 1.
No policer
Test session:
UDP port 900
exit all
configure
port svi 2 twamp
no shutdown
exit
exit
#*********Configure bridge ports

configure bridge 1
port 1 no shutdown
port 2 no shutdown
port 3 no shutdown
11-84 TWAMP ETX-2i

vlan 1
exit all
#*********Configure classifier for VLAN 1

configure
flows
match vlan 1
exit
#*********Configure flows between Ethernet port 1/1 and bridge port 1

flow E1_1toBP1
classifier v1
no policer
no shutdown
exit
flow BP1to E1_1

classifier v1
no policer
no shutdown
exit
#*********Configure flows between Ethernet port 0/1 and bridge port 2

flow E0_1toBP2
classifier v1
no policer
no shutdown
exit
flow BP2toE0_1
classifier v1
no policer
no shutdown
exit
#*********Configure flows between bridge port 3 and SVI 2

flow BP3toSVI2
classifier v1
egress-port svi 2
vlan-tag pop vlan
no policer
no shutdown
exit
flow SVI2toBP3
classifier all
ETX-2i TWAMP 11-85

ingress-port svi 2
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.101.116/24
address 11:11:101::116/64
bind svi 2
no shutdown
exit
exit

oam
twamp
responder 1 light
router-entity 1
test-session 1 udp-port 900
tx-extended-info
tx-seq-num
no shutdown
exit all
save

Bridge Activate ports 1, 2, and 3; associate VLAN 1.
Router Associate Interface 2 with SVI 2.
Flows between Ethernet port 1 and bridge port 1, and Ethernet port 3 and
bridge port 2:
Match VLAN 1
No policer
Flows between bridge port 3 and SVI 2:
Bridge port to SVI: Match VLAN 1, and pop VLAN.
SVI to bridge port: Match all traffic, and push VLAN 1.
No policer
Test session:
Profile with default values
UDP port 900
DSCP 22
exit all
11-86 TWAMP ETX-2i

configure
port svi 2 twamp
no shutdown
exit
exit
#*********Configure bridge ports

configure bridge 1
port 1 no shutdown
port 2 no shutdown
port 3 no shutdown
vlan 1
exit all
#*********Configure classifier for VLAN 1

configure
flows
match vlan 1
exit
#*********Configure flows between Ethernet port 1 and bridge port 1

flow E1toBP1
classifier v1
no policer
no shutdown
exit
flow BP1to E1
classifier v1
egress-port ethernet 1 block 0/1
no policer
no shutdown
exit
#*********Configure flows between Ethernet port 3 and bridge port 2

flow E3toBP2
classifier v1
no policer
no shutdown
exit
flow BP2to E3
classifier v1
egress-port ethernet 3 block 0/1
no policer
no shutdown
exit
#*********Configure flows between bridge port 3 and SVI 2
ETX-2i TWAMP 11-87

flow BP3toSVI2
classifier v1
egress-port svi 2
vlan-tag pop vlan
no policer
no shutdown
exit
flow SVI2toBP3
classifier all
ingress-port svi 2
no policer
no shutdown
exit
exit

router 1
interface 2
address 11.11.101.6/24
address 11:11:101::6/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile with default values

oam
twamp
profile twp1
exit

controller 1 light
router-entity 1
peer 11.11.101.116
calculation-mode round-trip
responder-seq-num
exit
no shutdown
exit all
save
Example Configuring TWAMP in Layer-3 Mode

This example illustrates configuring TWAMP in Layer-3 mode:
Controller with IP address=12.12.12.1
Responder with IP address=22.22.22.1
11-88 TWAMP ETX-2i

Note This example assumes for the routers in the controller and responder:
In the controller, the next hop to reach the 22.22.22.0/24 subnet is
12.12.12.2
In the responder, the next hop to reach the 12.12.12.0/24 subnet is
22.22.22.2

Flows between Ethernet port 0/1 and SVI 2:
Untagged traffic from Ethernet port 0/1 to SVI 2
Untagged traffic from SVI 2 to Ethernet port 0/1
No policer
Test session:
UDP port 999
exit all
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifier for untagged traffic

flows
match untagged
exit
#********* Configure flows between Eth port 0/1 & SVI 2

flow E1toSVI2
classifier untagged
no policer
no shutdown
exit
flow SVI2toE1
classifier untagged
ingress-port svi 2
no policer
no shutdown
exit
exit
#*********Configure router with interface 2 for TWAMP

router 1
interface 2
ETX-2i TWAMP 11-89

address 22.22.22.1/24
address 22:22:22::1/64
bind svi 2
no shutdown
exit
exit

oam
twamp
responder 1 light
router-entity 1
test-session 1 name "twamp1" udp-port 999
tx-extended-info
tx-seq-num
no shutdown
exit all
save

Untagged traffic from Ethernet port 0/1 to SVI 2
Untagged traffic from SVI 2 to Ethernet port 0/1
No policer
Test session:
Profile with payload length 150, and loss timeout 1 second
UDP port 999
DSCP 0
exit all
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifier for untagged traffic

flows
match untagged
exit

flow E1toSVI2
classifier untagged
11-90 TWAMP ETX-2i


no policer
no shutdown
exit
flow SVI2toE1
classifier untagged
ingress-port svi 2
no policer
no shutdown
exit
exit
#*********Configure router with interface 2 for TWAMP

router 1
interface 2
address 12.12.12.1/24
address 12:12:12::1/64
bind svi 2
no shutdown
exit
exit
#*********Configure TWAMP profile

oam
twamp
profile twp1
payload-length 150
loss-timeout 1000000
exit

controller 1 light
router-entity 1
peer 22.22.22.1
calculation-mode one-way
responder-seq-num
exit
no shutdown
exit all
save
Example Viewing TWAMP Status
To view controller status:

ETX-2i>config>oam>twamp>controller(1/light)# show status
IPPM Type : TWAMP Light
Router Entity : 1
Router Interface : 2
Router Interface oper status : UP
Controller Status : In Progress
ETX-2i TWAMP 11-91

To view responder status:

ETX-2i>config>oam>twamp>responder(1/light)# show status
Router Entity : 1
Responder Status : Ready
Responder Test Name UDP Port Tx Packets Rx Packets

---------------------------------------------------------------
TwampResponderSession 900 1107 1107
To view peer test status for TWAMP Light continuous test:

ETX-2i>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show status
Activation Mode : Continuous
Start Time : 2013-11-24 14:13:28
Controller Test Name Peer UDP Status Tx Packets Rx Packets

-----------------------------------------------------------------------------
twamp1 900 In Progress 600 599
To view peer test status for TWAMP Light non-continuous test:

ETX-2i>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show status
IPPM type : TWAMP Light
Activation mode : non-continuous
Calculation Mode : round-trip
Start time : 2013-05-30 15:29:45
Duration [ min ] : 120
Elapsed Time [ min ] : 20
Controller test name Peer UDP Status Tx packets Rx packets

-----------------------------------------------------------------------------
XXXX 30000 In progress 2000 1900
YYYY 35000 Ready 2000 1900
ABCD 40000 In progress 42000000 600000
To view peer test status for ICMP Echo continuous test:

ETX-2i>config>oam>twamp>controller(1)>peer(33.33.116.6)# show status
IPPM type : ICMP Echo
Activation mode : continuous
Start time : 2013-05-30 15:29:45
Controller test name Status Tx packets Rx packets

-----------------------------------------------------------------------------
XXXX In progress 2000 1900
YYYY Ready 2000 1900
ABCD In progress 42000000 600000
Example Viewing TWAMP Reports
To view a TWAMP Light test summary report (one-way calculation mode):

ETX-2i>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show summary-report
11-92 TWAMP ETX-2i


Controller IP Address : 11.11.101.6
Responder IP Address : 33.33.116.6
Activation Mode : Off
Calculation Mode : one-way
TOD status controller/peer : Sync / Out of sync
Start / Elapsed / Duration (min) : 2014-06-01 10:36:41 / 1 / 1
Controller Test Name Dir IP Size Loss Delay PDV IPDV Result
DSCP Ratio Max Max Max
(bytes) (ms) (ms) (ms)
----------------------------------------------------------------------------
1 fwd 22 1280 2.0E-2 0.658 0.065 0.048 Fail
1 bck 22 1280 0 0.263 0.014 0.011 Pass
To view a TWAMP Light test summary report (round-trip calculation mode):

ETX-2i>config>oam>twamp>controller(2/light)>peer(33.33.117.6)# show summary-report
Controller IP Address : 11.11.102.6
Responder IP Address : 33.33.117.6
Activation Mode : Continuous
Calculation Mode : round-trip
Start Time / Elapsed Time (sec) : 2014-06-02 00:27:30 / 240
Controller Test Name IP Size Loss Delay PDV IPDV Result

DSCP Ratio Max Max Max
(bytes) (ms) (ms) (ms)
-----------------------------------------------------------------------------
6 6 512 6.9E-1 179.292 3.415 2.312 NA
7 7 512 6.7E-1 181.170 5.494 3.888 NA
8 8 512 6.9E-1 183.131 5.817 4.545 NA
9 9 512 6.7E-1 185.145 7.609 6.323 NA
10 10 512 6.7E-1 187.108 10.949 9.789 NA
To view a TWAMP Light test report:

ETX-2i>config>oam>twamp>controller(1/light)>peer(33.33.116.6)# show report 1 all
Test Name : 1
Controller IP Address : 11.11.101.6 / 56568
Responder IP Address : 33.33.116.6 / 50000
IP DSCP : 22
Payload Length (bytes) : 256
Calculation Mode : one-way
Start Time : 2014-06-01 14:13:28
Test Interval : Current

Time Stamp : 2014-06-01 16:14:53
TOD Sync Count (sec) : 0
Tx Packets Fwd / Back : 5400 5360

Loss Packets Fwd / Back : 40 17
Loss Ratio Fwd / Back : 7.4E-3 3.2E-3
Availability Count Fwd / Back (sec) : 540 540
ETX-2i TWAMP 11-93

Duplicate Packets Fwd / Back : 0 0

Duplicate Ratio Fwd / Back : 0 0
Reordered Packets Fwd / Back : 0 0
Reordered Ratio Fwd / Back : 0 0
Fragmented Packets Fwd / Back : 0 0
Delay-Fwd Threshold Crossing Count : 0

Delay-Back Threshold Crossing Count : 8
Delay-Fwd Min / Max / Average (ms) : 0.530 0.892 0.615
Delay-Back Min / Max / Average (ms) : 0.226 775.498 0.899
PDV-Fwd Max / Average (ms) : 0.351 0.085
PDV-Back Max / Average (ms) : 377.482 0.673
IPDV-Fwd Max / Average (ms) : 0.306 0.010
IPDV-Back Max / Average (ms) : 775.263 0.293
Loss Result : Pass

Delay Result : Pass
DV Result : Pass
To view an ICMP Echo test summary report (continuous, round-trip calculation

mode):
ETX-2i>config>oam>twamp>controller(1)>peer(234.234.56.100)icmp-echo# show
summary-report
IPPM : ICMP Echo
Controller ip address : 1.1.1.1
Responder ip address : 234.234.56.100
Activation mode : continuous
Start time / Elapsed time [sec] : 2013-05-30 15:29:45 / 500
Controller test name DSCP Size Loss

Delay PDV IPDV Result
[bytes] Ratio
Max Max Max
[ms] [ms] [ms]
--------------------------------------------------------------------------------
AAAAA 02 100 6.5E-5 5.000 1.000 2.000 NA
To view an ICMP Echo test report (non-countinuous, round trip calculation

mode):
ETX-2i>config>oam>twamp>controller(1)>peer(33.33.116.6)icmp-echo# show report
AABBCC current
Test Name : AABBCC

IPPM type : ICMP Echo
Controller ip address : 1.1.1.1
Responder ip address : 234.234.56.100
IP DSCP : 34
Payload length [bytes] : 1500
Start Time : 2013-05-30 15:29:45
-------------------------------------------------------------------------------
Test interval : current
Elapsed time [sec] : 180
Tx packets : 1800
Loss packets : 10
Loss Ratio : 1.2E-3
Availability count [sec] : 180
Duplicate packets : 2
11-94 TWAMP ETX-2i

Duplicate Ratio : 1.2E-3

Reordered packets : 3
Reordered Ratio : 1.2E-3
Delay threshold crossing count : 7
Delay min / max / average [ms] : 1.000 2.000 1.500
PDV max / average [ms] : 2.000 1.000
IPDV max / average [ms] : 2.000 1.000
Loss result : fail // for non-continuous
only
Delay result : pass // for non-continuous
only
DV result : pass // for non-continuous
only
Cannot modify; TWAMP Tried modifying the bound Shut down the controller and then
controller is active port definition while controller modify the bound port definition.
was active (status was not
shutdown).
Tried modifying VLAN Shut down the controller and then

definition while controller was modify the VLAN definition
active (status was not
shutdown).
Tried modifying controllers Shut down the controller and then

router entity number while modify the router entity number.
controller was active (status
was not shutdown).
Tried modifying local IP Shut down the controller and then

address while controller was modify the local IP address.
shutdown).
Cannot modify; TWAMP Tried modifying the bound Wait for the active test to terminate
controller has active test port definition while controller and then modify the bound port
had an active test. definition.
Tried modifying VLAN Wait for the active test to terminate

definition while controller had and then modify the VLAN definition.
an active test.
Tried modifying controllers Wait for the active test to terminate

router entity number while and then modify the controllers router
controller had an active test. entity number.
ETX-2i TWAMP 11-95

Tried modifying local IP Wait for the active test to terminate

address while controller had and then modify the local IP address.
an active test.
Cannot delete; TWAMP controller Tried removing the bound port Shut down the controller and then
is active while controller was active remove the bound port.
(status was not shutdown).
Tried removing the VLAN Shut down the controller and then
definition while controller was remove the VLAN definition.
shutdown).
Cannot delete; TWAMP controller Tried removing the bound port Wait for the active test to terminate
has active test while controller had an active and then remove the bound port.
test.
Tried removing the VLAN Wait for the active test to terminate
definition while controller had and then remove the VLAN definition.
an active test.
Cannot activate; router entity Tried activating controller Define router entity and local IP
and local ip address must be when router entity and/or local address, and then activate controller.
defined IP address were not defined.
Tried activating responder Define router entity and local IP

when router entity and/or local address, and then activate responder.
IP address were not defined.
Cannot activate; router entity, In l2-probe mode, tried Define router entity, local IP address,
local ip address and port must activating controller when and port, and then activate controller.
be defined router entity, local IP address,
and/or port were not defined.
In l2-probe mode, tried Define router entity, local IP address,

activating responder when and port, and then activate responder.
router entity, local IP address,
and/or port were not defined.
Cannot delete; peer has active Tried deleting peer entity, Wait for active test to terminate, and
test while there was an active test. then delete peer entity.
Cannot create; name already in Tried giving a test session a Give test session a unique name.
use name that already exists under
peer context.
Tried giving a test profile a Give test profile a unique name.

name that already exists under
TWAMP contest.
Tried giving a responder a Give responder a unique name.

TWAMP context.
Tried giving a test session a Give test session a unique name.

responder contest.
11-96 TWAMP ETX-2i

Cannot activate; controller not Tried activating peer test Wait for controller to be ready, and
ready sessions when controller then activate peer test sessions.
status was idle (not ready).
Cannot activate; peer has active Tried activating peer test Wait for active tests to terminate, and
test sessions while there were then activate peer test sessions.
active tests.
Cannot delete; TWAMP Tried removing active Shut down the responder and then
responder is active responder (status idle or delete it.
ready).
Tried deleting the bound port Shut down the responder and then
definition while responder was delete the bound port definition.
active (status idle or ready).
Tried removing VLAN definition Shut down the responderer and then
while responder was active remove the VLAN definition.
(status idle or ready).
Cannot modify; TWAMP Tried modifying the bound Shut down the responder and then
responder is active port definition while responder modify the bound port definition.
was active (status idle or
ready).
Tried modifying VLAN Shut down the responder and then

definition while responder was modify the VLAN definition.
active (status idle or ready).
Tried modifying responders Shut down the responder and then

router entity number while modify the router entity number.
responder was active (status
idle or ready).
Tried modifying responders Shut down the responder and then

local IP address while modify the local IP address.
responder was active (status
idle or ready).
Tried deleting a test profile

that is in use by a test session.
11.5 Quality of Service (QoS)

The ETX-2i Quality of Service (QoS) parameters include the following profiles:
Queue map profiles
CoS map profiles
Color mapping profiles
Marking profiles
Bandwidth profiles
ETX-2i Quality of Service (QoS) 11-97

Queue block profiles

Queue group profiles
These profiles can be applied to the traffic flows to ensure the desired flow
prioritization.
Standards
The following standards are supported:
IEEE 802.1p
IEEE 802.1Q
MEF 10.3
Benefits
QoS allows you to optimize bandwidth, avoiding the need to allocate excessive
bandwidth to facilitate the necessary bandwidth for traffic at different
requirements of speed and quality.
Traffic Management
ETX-2i traffic management entities are called queue groups. They are configured
over physical ports. The queue groups consist of 2-level scheduling elements
(queue blocks) per port. The queue blocks consist of internal queues.
Additionally, shapers operate at per-scheduling-element level to shape traffic
into a required traffic profile (CIR, CBS or CIR/EIR, CBS/EBS).
Each flow is assigned to a queue block as its destination. Each queue block
includes scheduling queues in accordance with CoS delivery priorities. Flow
packets are mapped in the following ways to queues:
Mapped explicitly to a specific queue
Mapped to a queue according a queue mapping profile (p-bit or DSCP to
queue)
Mapped according to the packets CoS, in case of bridge or ETP (set by CoS
mapping profile at the ingress), whereby CoS 7 is mapped to the lower
priority queue, and CoS 0 to the highest
Scheduling
ETX-2i supports a combination of traffic scheduling techniques, whereby
applications requiring low latency and jitter are mapped to Strict priority queues,
while other services are mapped to the remaining slots using weighted fair
queuing (WFQ) and best effort (BE):
The Strict priority queues ensure minimal latency and jitter for the RT traffic,
even when a large amount of bursty data traffic is sent over the same
uplink. Strict priority traffic is always processed first, while flows mapped to
the WFQ slots are buffered until the strict priority queues are empty.
11-98 Quality of Service (QoS) ETX-2i

The WFQ technique avoids scheduling starvation of lower priority queues

and ensures relatively fair allocation of bandwidth by sharing it among all
flows. In this manner, packets belonging to lower classes of service are not
penalized when higher priority queues are not empty and may still receive
transmission time. QoS-conformant scheduling is handled by assigning
different weights to the various queues instead of equally dividing overall
bandwidth among all active flows.
BE (best-effort) queues transmit packets only if there are no packets in
higher level queues.
Congestion avoidance is provided by WRED profiles (see WRED Profiles).
Factory Defaults
See the following sections for each QoS types specific defaults.
Queue Mapping Profiles

To differentiate traffic, the IEEE 802.1p standard specifies eight classes of
service per user-defined queue map profile. These classes of service are
associated with priority values between 0 and 7, using the 3-bit user priority
field in an IEEE 802.1Q header added to VLAN-tagged frames within an Ethernet
frame header. The way traffic is treated when assigned to a specific priority
value is only generally defined and left to implementation. The general
definitions are as follows:
Table 11-10. User Priorities
User Priority Traffic Type
0 Best effort
1 Background
2 Spare
3 Excellent effort
4 Controlled load
5 Video
6 Voice
7 Network control
Queue mapping profiles are used to convert the following user priorities into
internal priority queues.
p-bit When ingress traffic is prioritized according to the 802.1p

requirements
Ip-dscp When ingress traffic is prioritized according to DSCP; for

both IPv4 and IPv6
Ip-precedence When ingress traffic is prioritized according to

IP precedence; for both IPv4 and IPv6

Class of Service When ingress traffic is mapped to an internal CoS (e.g p-bit
(CoS) or DSCP to CoS) at the Bridge port ingress, ETP subscriber
ingress, and flow that uses an envelope policer
For each profile, you have to define the queue mapping to map the user priority
values to the internal queue values. The internal queues are combined into a
queue profile, which can be assigned to a queue block.
Factory Defaults
Default Queue Mapping Profile

ETX-2i provides a default queue mapping profile named CosProfile1, which can
be used when the ingress traffic is prioritized according to the 802.1p
requirements. It is defined with classification p-bit, and the following mappings:
Map p-bit 0 to queue 7.
There is also a predefined queue mapping profile named q-map-for-cos, which
can be used for multi-Cos flows when you wish to map CoS 0 to queue 0, CoS 1
to queue 1, etc.
Default Configuration for IP Precedence Classification

When a new queue mapping profile is created with classification IP precedence,
it contains the following mappings:
Default Configuration for DSCP Classification

When a new queue mapping profile is created with classification DSCP, it
contains the following mappings:


Map p-bit 7 through 63 to queue 0.
Adding Queue Mapping Profiles

When you create a queue mapping profile, you specify the name and the
classification method (p-bit, IP precedence, or DSCP).
To add a queue mapping profile:

1. Navigate to configure qos.
The config>qos# prompt is displayed.
2. Type:
queue-map-profile <queue-map-profile-name> classification
{p-bit|ip-precedence|ip-dscp|cos}
A queue mapping profile with the specified name and classification
method is created and the following prompt is displayed:
config>qos>queue-map-profile(<queue-map-profile-name>)$.
The mappings for the new profile are configured by default as described
in Factory Defaults.
3. Configure the queue profile mappings as described in Configuring Queue
Mappings.
Configuring Queue Mappings

1. To configure queue mappings:Navigate to config qos queue-map-profile
<queue-map-profile-name> to select the queue mapping profile to
configure.
config>qos>queue-map-profile(<queue-map-profile-name>)#
2. Map the user priorities to queue IDs as necessary:
Classification p-bit or IP precedence:
map <0-7> to-queue <0-7>
Classification DSCP:
Classification CoS:

Examples
To create and configure a queue mapping profile named QMapPbit with

classification p-bit:
Map priority 0 to queue 3.
Map priority 4 and 6 to queue 2.
exit all
configure qos queue-map-profile QMapPbit classification p-bit
map 0 to 3
map 4 to 2
map 6 to 2
exit all
To display the configuration information for queue mapping profile QMapPbit:

ETX-2i# configure qos queue-map-profile QMapPbit
ETX-2i>config>qos>queue-map-profile(QMapPbit)# info detail
map 0 to-queue 3
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4..6 to-queue 2
map 7 to-queue 0
To create and configure a queue mapping profile named QMapIPprec with

classification IP precedence:
Map priority 2 and 3 to queue 3.
exit all
configure qos queue-map-profile QMapIPprec classif ip-precedence
map 2 to 3
map 3 to 3
exit all
To display the configuration information for queue mapping profile QMapIPprec:

ETX-2i# configure qos queue-map-profile QMapIPprec
ETX-2i>config>qos>queue-map-profile(QMapIPprec)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2..4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0
To create and configure a queue mapping profile named QMapDSCP with

classification DSCP:
exit all
configure qos queue-map-profile QMapDSCP classif ip-dscp
map 7 to 6

map 55 to 4
map 63 to 5
exit all
To display the configuration information for queue mapping profile QMapDSCP:

ETX-2i# configure qos queue-map-profile QMapDSCP
ETX-2i>config>qos>queue-map-profile(QMapDSCP)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 6
map 8..54 to-queue 0
map 55 to-queue
4
map 56..62 to-queue 0
map 63 to-queue 5
To create and configure a queue mapping profile named QMapCoS with

classification CoS:
Map CoS 67 to-queue 0.
exit all
configure qos queue-map-profile QMapCoS classification cos
map 6..7 to-queue 0
map 3..5 to-queue 1
map 0..2 to-queue 2
exit all
CoS Mapping Profiles

CoS mapping profiles can be used at the following levels:
Flow level ingress Bridge port flows, ETP subscriber flows, and flows using
envelope policer (MEF 10.3 BW profiles)
Ring level
Class of Service (CoS) mapping profiles map the following user priorities to
internal CoS values:
p-bit Relevant at flow and ring levels; when ingress traffic is

prioritized according to 802.1p requirements
ip-dscp Only relevant at flow level; when ingress traffic is

prioritized according to DSCP
ip-precedence Only relevant at flow level; when ingress traffic is

prioritized according to IP precedence

Note If the flow from UNI to NNI is classified with one of the above classifications
(p-bit only, ip-dscp, or ip-precedence), Up MEP and customer-tag-excluded MEP
do not work and it is therefore recommended not to use them.
Internal CoS is used:

To map a packet to a specific egress queue (fixed mapping: CoS 0 maps to
queue 0, CoS 1 maps to queue 1, etc.)
By marking profiles to set p-bits of remarked packets (CoS to p-bit marking
profiles)
By flows with MEF 10.3 envelope BW profiles to map traffic to the different
envelope ranks identified by CoS
Factory Defaults
By default, there are no CoS mapping profiles. When you create a CoS mapping
profile, it is configured as follows:
Classification p-bit
Mappings:
Map 0 to CoS 7.
Map 1 to CoS 6.
Map 2 to CoS 5.
Map 3 to CoS 4.
Map 4 to CoS 3.
Map 5 to CoS 2.
Map 6 to CoS 1.
Map 7 to CoS 0.
Untagged to CoS 7, for profile assigned to multi-Cos flow in case of p-bit
mapping
Non-IP to CoS 7, for profile assigned to multi-Cos flow in case of DSCP
mapping
Configuring CoS Mapping Profiles
To define a CoS mapping profile:

1. Navigate to the qos context (config>qos).
2. Define a CoS profile and assign a classification to it:
cos-map-profile <cos-mapping-profile-name> [classification {p-bit |
ip-precedence | ip-dscp }]
Note that you can only configure classification p-bit for a CoS mapping
profile to be associated with a ring.
3. Map the user priority to a CoS value (user priority values 07 for p-bit and IP
precedence, 063 for the other priority types; CoS values 07):
map <0-7> to <0-7>
map <0-63> to <0-7>

4. If the CoS mapping profile is intended for use with a multi-Cos flow:
a. Define the mapping of untagged traffic in case of p-bit mapping:
map untagged to <0-7>
b. Define the mapping of non IP traffic in case of DSCP mapping:
map non-ip to <0-7>
Examples
To create and configure a CoS mapping profile (for a flow or ring):

Profile name: my-p-bit
Classification: p-bit
Map priority 67 to CoS 0.
exit all
configure qos cos-map-profile my-p-bit classification p-bit
map 6..7 to-cos 0
map 3..5 to-cos 1
map 0..2 to-cos 2
exit all
To create and configure a CoS mapping profile for a multi-CoS flow:

Profile name: p-bit-multi
Classification: p-bit
.
.
Map untagged traffic to CoS 0.
exit all
configure qos cos-map-profile p-bit-multi classification p-bit
untagged-map to-cos 0
exit all
Color Mapping Profiles

Color mapping profiles map p-bits or the drop eligible indicator (DEI) bit to
packet color:
Color mapping profiles with classification type p-bit are used to map p-bit
values to green or yellow.
Color mapping profiles with classification type DEI are used to map the DEI
bit to green or yellow as follows:
DEI=0: Maps to green
DEI=1: Maps to yellow

Color mapping profiles with classification type p-bit are configurable, whereas
color mapping profiles with classification type DEI are not configurable.
Color mapping profiles can be assigned to flows and rings.
Factory Defaults
By default, there is no color mapping profile. When a color mapping profile with
classification type p-bit is created, all the p-bit values are mapped to green.
Configuring Color Mapping Profiles
To define a color mapping profile:

2. Define a color mapping profile according to classification type:
P-bit classification:
a. Enter:
color-map-profile <color-mapping-profile-name> classification p-bit
b. Map the p-bits to a color as needed:
map <class-value> to {green|yellow}
DEI classification:
color-map-profile <color-mapping-profile-name> classification dei
Example
To create a color mapping profile kcolpb to map odd p-bit values to green, and
even to yellow:
exit all
configure qos
color-map-profile kcolpb classification p-bit
map 0 to yellow
map 2 to yellow
map 4 to yellow
map 6 to yellow
exit all
save
Marking Profiles
Marking profiles map the p-bit, IP precedence, DSCP, or CoS classifications to the
egress priority tags (p-bit) or DSCP values (ip-dscp). The marking can also be
done per color (green and/or yellow), to support color re-marking, optionally
specifying the Drop Eligible Indicator (DEI) bit in the frame header.
In the case that you configure the ETHoGRE tunnel DSCP value using a DSCP
marking profile (refer to Ethernet over GRE (EoGRE) Tunnel section in Chapter

8), you must first configure the DSCP marking profile with classification p-bit and
method ip-dscp (see below).
Factory Defaults
ETX-2i provides a default non color-aware marking profile named
MarkingProfile1, which can be used when the ingress traffic is prioritized
according to the 802.1p requirements. It is defined with classification p-bit and
method p-bit, and the following markings:
P-bit 0 => priority 0
P-bit 1 =>priority 1
When a non color-aware marking profile is created, it has the same
configuration as MarkingProfile1.
Configuring Marking Profiles
To define a marking profile and assign a priority mark to it:

2. Define the marking profile and assign a classification and method to it:
marking-profile <marking-profile-name>
[classification {p-bit | ip-precedence | ip-dscp |cos}] [method {p-bit | ip-
dscp} ] [color-aware {none | green-yellow} [dei {always-green |
always-yellow | by-policer}]
To define a color-aware profile, specify color-aware green-yellow.
Note You must specify cos if the marking profile is intended for use with a multi-CoS
flow.
Note While working with ETP, marking profile on Transport flows must be mapped by
cos (marking-profile 1 classification cos) and not p-bit (marking-profile 1
classification p-bit).
The dei parameter affects the Drop Eligible Indicator (DEI) bit in transmitted
frames as follows:
always-green Frames transmitted from the device are marked via the
DEI bit as not eligible to be dropped. In this case, the color-aware
parameter can be none or green-yellow.
always-yellow Frames transmitted from the device are marked via the
DEI bit as eligible to be dropped. In this case, the color-aware parameter
must be green-yellow.

by-policer Yellow frames transmitted from ETX-2i are marked via the
DEI bit as eligible to be dropped, and green frames transmitted from
ETX-2i are marked as not eligible to be dropped. In this case, the
color-aware parameter can be none or green-yellow.
3. Map the user priority (and packet color, if it is a color-aware marking profile)
to a priority marking value according to the specific profile parameters
(classification and method), as follows.
At the config>qos>marking-profile(<profile-name>)$ prompt, enter:
Non color-aware profile:
mark <user-priority> to <priority-marking>
Color-aware profile:
mark <user-priority> {all|green|yellow} to <priority-marking>
Where user-priority value can be set to:
0-7 for marking profile configured with classification p-bit, ip-
precedence, or cos
0-63 for marking profile configured with classification ip-dscp
And priority-marking value can be set to:
0-7 for marking profile configured with method p-bit
0-63 for marking profile configured with method ip-dscp
Bandwidth Profiles
ETX-2i supports the following bandwidth profiles:
Shaper profile Applied to queue group blocks
Policer profile Applied to flows to limit flow traffic, or to Ethernet ports

(non-envelope) to limit broadcast/multicast traffic
Envelope policer Specifies set of bandwidth profiles to apply to multi-CoS

profile flows
Policer aggregate Specifies non-envelope policer profile to apply to a group

of flows
You can control the egress bandwidth utilization by defining the committed
information rate (CIR) and committed burst size (CBS) in shaper and policer
profiles. You can also define the excessive information rate (EIR), excessive burst
size (EBS), and compensation in policer profiles.
CIR Defines the Committed Information Rate (CIR) for the

current profile. The CIR specifies a bandwidth with
committed service guarantee (green bucket rate).
CBS Defines the Committed Burst Size (CBS) for the current
profile. The CBS specifies the maximum guaranteed burst
size (green bucket size).

EIR Defines the Excess Information Rate (EIR). The EIR specifies
an extra bandwidth with no service guarantee (yellow
bucket rate).
EBS Defines the Excess Burst Size (EBS). The EBS specifies the
extra burst with no service guarantee (yellow bucket
size).
Compensation Defines the amount of bytes that the shaper or policer can
compensate for Layer-1 overhead (preamble and IFG) and
the overhead for the additional VLAN header in case of
stacking.
Color Aware You can specify the policer profile as color aware.
If the policer profile is specified as color aware, you can set the packet color as
follows:
1. If the arriving packet is marked green and and the CIR bucket complies, the
packet color is set to green.
2. If the result of the preceding test is not true, then ETX-2i checks if the EIR
bucket complies (if the coupling flag is set, the CIR+EIR bucket is used):
If the test result is true, the packet color is set to yellow.
If the test result is false, the packet color is set to red (packet is
dropped).
Factory Defaults
The default for bandwidth-round-up is no bandwidth-round-up. The default
value for envelope-ranks (maximum number of ranks in envelope profiles) is 4.
ETX-2i provides default bandwidth profiles, as specified in the following table.
Table 11-11. Default Bandwidth Profiles
Profile Type Shaper Policer (non-envelope)
Profile Name Shaper1 Policer1
cir 0
9999872
cbs 0
16000000
eir [not applicable]

10000000
ebs [not applicable] 32767
color-aware [not applicable] no color-aware
compensation 0 0
coupling-flag [not applicable] no coupling-flag
traffic-type [not applicable] all

When an envelope profile is created, it has the default values shown in the
following table.
Table 11-12. Default Envelope Profile
Parameter Value
compensation 0
cf-policy sharing-excess-bw
color-aware no color-aware
cos <n> bandwidth cir 0 cir-max 10000000 cbs 0 eir 0 eir-max 10000000 ebs 0
Envelope Bandwidth Profiles

An envelope profile as defined in MEF 10.3 contains a set of bandwidth profiles,
each of which has been assigned a unique rank from 1 (lowest) to 4 or 8
(highest). Excess bandwidth from a higher rank can overflow to a lower rank to
be shared, either to the committed or to the excess bucket. In ETX-2i, each
profile corresponds to a separate CoS. Figure 11-6 illustrates an envelope profile
with three CoSs. The coupling flags specify the path of overflow bandwidth. For
the CoS coupling flags (CFi), 0 = committed token bucket of the next lower rank,
and 1 = excess token bucket of the same rank. For coupling flag 0, 0 = discard,
and 1 = excess token bucket of the highest rank.
CIR3
EIR3
1
Rank #3 CBS 3 CF3
0
EBS3
CIR2
EIR2
1
Rank #2 CBS 2
CF 2
0
EBS2 Envelope
CIR2
EIR1
1
1
1
Rank #1 CBS CF
0
EBS1
0 1
CF0
Figure 11-6. MEF 10.3 Bandwidth Profiles
When the envelope profile is assigned to a multi-CoS flow (see Multi-CoS Flows),
it enables the flow to share excess bandwidth. The bandwidth sharing can be
overflowed to the excess bucket (see Figure 11-7) or independent from the
excess bucket (see Figure 11-8).

CIR3
EIR3
1
3 3
CBS CF
EBS3
CIR2
EIR2
2
1
2
CBS CF
EBS2
2
CIR
EIR1
1
CBS1 CF1
EBS1
Figure 11-7. Sharing Excess Bandwidth
CIRenv
EIRenv
CBS3 CF3
0
EBS3
CBS2 CF2
0
EBS2
CBS1 CF1
0
EBS1
Figure 11-8. Sharing Excess Bandwidth, Uncoupled from EIR/EBS
ETX-2i can work with up to four or eight ranks (user configurable).
To change the maximum number of ranks:
Note The following must be true in order to change the maximum number of ranks
from 4 to 8:
No more than 125 active envelope policer instances exist in the device.
No more than 32 envelope profiles are configured.
The following must be true in order to change the maximum number of ranks
from 8 to 4:
No envelope policer profile is configured with more than 4 ranks.


2. Enter:
envelope-ranks {4|8}
A message is displayed recommending that you reset the device in order
to save the configuration and for changes to go into effect.
Configuring Granularity Rounding

When policer or shaper profiles are configured, the configured values are
rounded either up or down for granularity, according to whether the command
bandwidth-round-up has enabled rounding up or has disabled it. The rounded
value is stored in the device database, and is displayed when you display
information on the profile.
To configure granularity rounding:
2. To enable rounding up to the higher granular value, type:
bandwidth-round-up
When policer or shaper profiles are configured, the configured value is
rounded to the higher granular value.
3. To enable rounding down to the lower granular value, type:
no bandwidth-round-up
When policer or shaper profiles are configured, the configured value is
rounded to the lower granular value.
If you change the behavior from rounding up to rounding down, then after
device reset, the rates that were actually configured are rounded up to the
higher granularity values.
Configuring Shaper Profiles

You can configure shaper profiles and apply them to queue group blocks as
needed.
Adding Shaper Profiles

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

Configuring Shaper Profile Parameters

To configure shaper profiles:
1. Navigate to configure qos shaper-profile <shaper-profile-name> to select
the shaper profile to configure.
The config>qos>shaper-profile(<shaper-profile-name>)# prompt is
displayed.
Specifying the CIR (Kbps) and CBS bandwidth [cir <cir-kbit-sec>] [cbs <cbs-bytes>] Notes:
(bytes) bandwidth limits CIR allowed values:
010,000,000
(see Table 11-13 for the
shaper CIR granularity)
CBS allowed values:
0, or 6416777215
Compensating for Layer-1 overhead compensation <063> For pre-forwarding (ingress)
and additional VLAN tag (in bytes) traffic management, the
compensation is configurable in
the 0-63 range.
For post-forwarding (egress),
traffic management, the
compation is applied to level-0
shapers only. It can be set to 0
(data rate) or 20 (line rate).
Table 11-13. Shaper CIR Granularity
Device CIR > 130 Mbps (fast) CIR <= 130 Mbps
(slow)
ETX2i, ETX-2i-B, 256 Kbps 64 Kbps

ETX-2i-10G 1G ports
ETX-2i-10G 512 Kbps 512 Kbps

10G ports
Note: Although the CLI enables you to configure
the shaper profile with either 64 Kbps or 256 Kbps
granularity, when applied to ETX-2i-10G 10G ports,
this value is rounded up to 512 Kbps.
This behaviour is due to HW limitations and due to
the fact that the shaper profile is not bound to any
port when configured, but in actuality, can be
bound to both 1G and 10G ports.

Examples
To create and configure a shaper profile named Shap2:

CIR = 99,840 Kbps
CBS = 32,000 bytes
Compensation = 48
exit all
configure qos shaper-profile Shap2
bandwidth cir 99840 cbs 32000
compensation 48
exit all
Configuring Policer Profiles

This section explains functionality and configuration of non-envelope policer
profiles for traffic policing and rate limit. Policer profiles can be applied to flows
or Ethernet ports.
A port policer profile (also known as BUM filter (Broadcast, Unknown Unicast,
Multicast filter)), is supported by binding a policer BW profile to the Ethernet
port. This BW profile can only be configured with CIR and CBS bandwidth
parameters.
Whereas a policer BW profile bound to a flow relates to the entire traffic over
this flow, a policer BW profile bound to an Ethernet port can be configured to
limit Broadcast, Multicast, Unknown Unicast, and their combinations (see below).
You can configure the policer BW prile bound to Ethernet port to rate limit the
following traffic types:
Broadcast Broadcast traffic from the port is limited per the

configured CIR and CBS bandwidth limits..
Multicast Multicast traffic from the port is limited per the configured
CIR and CBS bandwidth limits.
Unknown Unicast Unknown Unicast traffic from the port is limited per the
configured CIR and CBS bandwidth limits. This is relevant
only for traffic into a bridge.
Broadcast + Aggregate traffic of Broadcast + Multicast from the port is

Multicast limited per the configured CIR and CBS bandwidth limits.
Broadcast + Aggregate traffic of Broadcast + Multicast + Unknown

Multicast + Unicast from the port is limited per the configured CIR and
Unknown Unicast CBS bandwidth limits.
Adding Policer Profiles


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

1. Navigate to configure qos policer-profile <policer-profile-name> to select
the policer profile to configure.
The config>qos>policer-profile(<policer-profile-name>)# prompt is
displayed.

Specifying the CIR (Kbps), CBS bandwidth [cir <cir-kbit-sec>] [cbs <cbs-bytes>] Notes:
(bytes), EIR (Kbps), and EBS (bytes) [eir <eir-kbit-sec>] [ebs <ebs-bytes>] CIR & EIR allowed values:
bandwidth limits
010000000
CBS & EBS allowed values:
0, or 642097151
CIR can be set to zero only if
CBS is set to zero.
EIR can be set to zero only if
EBS is set to zero.
CIR + EIR must not exceed the
maximum available bandwidth.
CBS should be greater than the
maximum frame size.
For policer profiles that will be
attached to Ethernet ports to
limit broadcast/multicast
traffic, only the CIR and CBS
parameters are relevant (EIR
and EBS should be set to 0).
A high-speed policer (CIR or
EIR >= 100,000 Kbps) cannot
be associated with more than
64 flows.
The CIR and EIR granularity
depend on the configured
values, as described in
Table 11-14.
The actual rate is rounded
down or up according to the
setting of
bandwidth-round-up.
The CBS must be greater than
or equal to the CIR divided by
policer granularity.
Specifying if the policer profile is color-aware

color aware
Compensating for Layer-1 overhead compensation <063>

and additional VLAN tag (in bytes)
Specifying whether to check CIR+EIR coupling-flag

when determining packet color
Specifying the traffic type traffic-type {all | broadcast | multicast | Note:

unknown-unicast | broadcast-and-multicast | Traffic types other than all are
broadcast-and-multicast-and-unknown-unicast} relevant only for policer
profiles attached to ports.

Table 11-14. Granularity Rounding of Policer CIR/EIR
IR (CIR, EIR) CBS < 2 MB <= CBS 4 MB <= CBS 8 MB <= CBS 16 MB <= CBS
2 MB < 4 MB < 8 MB < 16 MB < 32 MB
IR < 10,000 Kbps 10 Kbps 20 Kbps 40 Kbps 80 Kbps 160 Kbps
10,000 Kbps <= IR 100 Kbps 200 Kbps 400 Kbps 800 Kbps 1600 Kbps
< 100,000 Kbps
100,000 Kbps <= IR 1 Mbps 2 Mbps 4 Mbps 8 Mbps 16 Mbps

< 1,000,000 Kbps
Examples
To create and configure a policer profile named Policer4:

CIR = 50,000 Kbps
CBS = 28,000 bytes
EIR = 30,000 Kbps
EBS = 20,000 bytes
Compensation = 56
Note CIR and EIR are rounded down to 64K granularity, as this is a low-speed policer
with burst size < 64,000 bytes.
exit all
configure qos policer-profile Policer4
compensation 56
exit all
To display the configuration information for policer profile Policer4:

ETX-2i# configure qos policer-profile Policer4
ETX-2i>config>qos>policer-profile(Policer4)# info detail
traffic-type all
compensation 56
Configuring Policer Aggregates

You can define a policer aggregate that specifies a non-envelope policer profile
to apply to a group of flows. This is useful if you want to set bandwidth limits
that are divided among more than one flow.
Factory Defaults
By default, no policer aggregates exist. When a policer aggregate is created, it
has the following configuration:
No assigned policer profile
No assigned flows

Rate sampling window (interval for sampling the associated flow statistics)
set to 15 minutes
Adding Policer Aggregates

2. Type:
policer-aggregate <policer-aggregate-name>
A policer aggregate with the specified name is created and the
config>qos>policer-aggregate(<policer-aggregate-name>)$ prompt is
displayed. The new policer aggregate parameters are configured by
default as described in Factory Default.
3. Configure the policer aggregate as described in Configuring Policer Aggregate
Parameters.
Configuring Policer Aggregate Parameters

1. Navigate to configure qos policer-aggregate <policer-aggregate-name> to
select the policer aggregate to configure.
config>qos>policer-aggregate(<policer-aggregate-name>)#
Note You assign flows to the policer aggregate in the flow level (see Configuring
Flows for details).
Assigning policer profile policer profile <policer-profile-name>
Specifying rate sampling window rate-sampling-window <130>

(minutes)
Displaying the associated flows show flows
Displaying statistics for the show statistics running

associated flows
Clearing the statistics for the clear-statistics

associated flows
Examples
To create and configure a policer aggregate named Aggr1:

Policer profile: Policer4 (created in policer profile example).
exit all
configure qos
policer-aggregate Aggr1
policer profile Policer4
exit all

Configuring Envelope Profiles

This section explains how to configure envelope profiles, to apply to multi-Cos
flows per MEF 10.3.
Adding Envelope Policer Profiles

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

1. Navigate to configure qos envelope-profile <envelope-profile-name> to
select the envelope profile to configure.
The config>qos>policer-profile(<envelope-profile-name>)# prompt is
displayed.
Defining policy for excess cf-policy {sharing-excess-bw | uncoupled-bw-sharing} sharing-excess-bw Excess

bandwidth sharing bandwidth is shared to excess
token bucket (see Figure 11-7).
Selecting this parameter
automatically sets coupling-flag-0
to 0, and sets each CoS coupling
flag to 1.
uncoupled-bw-sharing Excess
bandwidth is shared independently
from EIR/EBS (see Figure 11-8).
Selecting this parameter
automatically sets coupling-flag-0
to 0, and sets each CoS coupling
flag to 0.
If you enter no cf-policy, you can
configure coupling-flag-0; each CoS
coupling flag determines the
bandwidth sharing.
Specifying if the envelope color-aware

profile is color aware

Specifying the compensation compensation <value> Possible values: 063

(bytes)
Specifying the CIR (Kbps), CBS cos <value> bandwidth [cir <cir-kbit-sec>] Range for cos value is 07; you can
(bytes), EIR (Kbps), and EBS [cir-max <cir-max-kbit-sec>] [cbs <cbs-bytes>] define up to four or eight cos
(bytes) bandwidth limits, for a [eir <eir-kbit-sec>] [eir-max <eir-max-kbit-sec>] values in an envelope profile.
particular CoS [ebs <ebs-bytes>] [coupling-flag <coupling-flag>] Range for <cir-kbit-sec>,
<cir-max-kbit-sec>, <eir-kbit-sec>,
and <eir-max-kbit-sec>:
010000000 (010 Gbps)
Range for <cbs-bytes>,
<ebs-bytes>:
02000000 (02Mbytes)
<cir-max-kbit-sec> must be greater
than or equal to <cir-kbit-sec>.
<eir-max-kbit-sec> must be greater
than or equal to <eir-kbit-sec>.
coupling-flag controls the path of
overflow tokens: 0=overflow to
committed token bucket, 1=
overflow to excess token bucket.
Specifying path of overflow coupling-flag-0 <value> <value> is 01:

bandwidth (see CF0 in 0=discard, and 1=excess token bucket
Figure 11-6) of the highest rank
Queue Block Profiles

In order to facilitate congestion management, you can sort traffic by applying
queue block profiles to queue block entities. A queue block profile contains
entries for queues 07, with the following parameters:
Scheduling method:
Strict high-priority queues that are always serviced first. If a
lower-priority queue is being serviced and a packet enters a higher
queue, that queue is serviced immediately.
WFQ (weighted fair queuing) If one port does not transmit, its unused
bandwidth is shared by the transmitting queues according to the
assigned weight. WFQ frames are transmitted only after transmission of
any frames associated with Strict queues is completed.
BE (best effort) lowest priority queue(s). One or both of the lowest
queues (Queue 6 and/or Queue 7) in a level 0 queue block can be
configured as BE. Packets in BE queues are transmitted only if there are
no packets in the WFQ or Strict queues.
Strict BE When a BE queue is defined, it is strict in relation to the
queues beneath it.
Number of frame buffers Each frame buffer holds one queued packet,
therefore the number of frame buffers determines how many packets the

queue can hold at one time. For example, if you configure 16384 frame
buffers, then the queue can tolerate bursts of up to 16384 packets (if the
queue size allows it).
Depth (queue size), in bytes.
Factory Defaults
ETX-2i provides a default queue block profile named DefaultQueue1, which
defines queues 07 as follows:
Congestion avoidance WRED profile corresponding to queue
Scheduling method WFQ, with weight set to 100
Number of frame buffers 511
Depth 49,152
Adding Queue Block Profiles

This section explains how to define queue block profiles.
To add a queue block profile:

2. Type:
queue-block-profile <queue-block-profile-name> [number-of-queues
<number>]
A queue block profile with the specified name, and number of queues, is
created, and the following prompt is displayed:
config>qos>queue-block-profile(<queue-block-profile-name>)$
The queues for the new profile are configured by default as described in
Factory Defaults.
3. Configure the queue block profile as described in Configuring Queue Block
Profile Parameters.
Configuring Queue Block Profile Parameters

To configure a queue block profile:
1. Navigate to config qos queue-block-profile <queue-block-profile-name> to
select the queue block profile to configure.
The config>qos>queue-block-profile(<queue-block-profile-name>)#
2. Perform the following for each queue that you wish to configure:
a. To configure a queue, enter:
queue <queue-ID>
config>qos>queue-block-profile(<queue-block-profile-name>)>queue(<queue-ID>)#.
b. Enter all necessary commands according to the tasks listed below.
c. Type exit to return to the queue block profile context.

Specifying queue depth (in bytes) depth <value> Possible values: 642097152
Notes:
If queue depth is confgured to below 64, it is
automatically rounded up to 64 bytes.
The queue depth that you configure might be
changed by ETX-2i due to granularity . After you
configure the queue depth, it is recommended to
use info detail to see the actual value
If a queue contains a relatively small amount of
frame buffers such as the default value 511, it is
possible for the queue to be full when every
buffer is in use, even if the queue size has not
reached the maximum. This is more likely to
happen in the case of relatively small frame sizes.
Specifying maximum frame buffers frame-buffers <number> Possible values: 016384
Setting scheduling method scheduling { strict | wfq <weight>| The WFQ weight range is 31000
best-effort} Strict queues must have queue indices lower than
WFQ or best-effort queues, and WFQ queues must
have queue indices lower than best-effort queues.
Table 11-15. Queue Depth Granularity
Entered Via CLI Granularity
065535 64
65536131071 128
131072262143 256
262144524287 512
5242881048575 1024
10485762097151 2048
2097152 4194303 4096
4194304 8380416 8192
Examples
To create and configure a queue block profile named QBlockProf1:

Queue 0 set to strict scheduling and depth 524,288
Queue 1 set to strict scheduling and depth 212,992
Queues 2 and 3 set to WFQ scheduling with weight 75
Queues 6 and 7 set to Best Effort and depth 49,152
exit all
configure qos queue-block-profile QBlockProf1

queue 0
scheduling strict
depth 524288
exit
queue 1
scheduling strict
depth 212992
exit
queue 2
scheduling wfq 75
exit
queue 3
scheduling wfq 75
exit
queue 6
scheduling best-effort
depth 49152
exit
queue 7
scheduling best-effort
depth 49152
exit all
Queue Group Profiles

In order to facilitate congestion management, you can sort traffic by applying
queue group profiles.
Factory Defaults
ETX-2i provides a default queue group profile named DefaultQueueGroup,
configured as shown:
ETX-2i# configure qos queue-group-profile DefaultQueueGroup
ETX-2i> config>qos>queue-group-profile(DefaultQueueGroup)# info
detail
queue-block 1/1
name "Level1QueueBlock"
profile "Scheduling1"
no shaper
exit
queue-block 0/1
profile "DefaultQueue1"
bind queue 0 queue-block 1/1
shaper profile "Shaper1"
exit
queue-block 0/2
exit

Adding Queue Group Profiles
To add a queue group profile:

2. Type:
queue-group-profile <queue-group-profile-name>.
A queue group profile with the specified name is created and the
following prompt is displayed:
config>qos>queue-group-profile(<queue-group-profile-name>)$
The queue group profile parameters are configured by default as
described in Factory Defaults.
3. Configure the queue group profile as described in Configuring Queue Group .
Configuring Queue Group Parameters

To configure a queue group profile:
1. Navigate to config qos queue-group-profile <queue-group-profile-name> to
select the queue group profile to configure.
The config>qos>queue-group-profile(<queue-group-profile-name>)#
2. Select a queue block in level 0 or 1 to configure:
queue-block 0/<131>
queue-block 1/1
config>qos>queue-group-profile(<q-grp-profile-name>)>queue-block(<level/ID>)#
4. If you wish to configure another queue block, type exit to return to the
queue group profile context, and start again at step 2.
Assigning a name to the queue block name <block-name>
Assigning a queue block profile profile <queue-block-profile-name>
Assigning a shaper profile shaper profile <shaper-profile-name>
Note
Normally there is no need for you to enter the bind command. When you add a
queue block in level 0 to the profile, bind is done automatically.
You cannot use the bind command if the queue group contains a single
queue block in level 0.
Examples
Note This example uses the shaper profile and queue block profile created in the
examples in the preceding sections.

To create and configure a queue group profile named QGroupProf1:

Queue block 0/1:
Queue block profile: QBlockProf1
Shaper profile: Shap2
Note Queue blocks 1/1 and 0/2 are automatically created.
exit all
configure qos queue-group-profile QGroupProf1
queue-block 0/1
profile QBlockProf1
shaper profile Shap2
exit all
To display the configuration information for queue group profile QGroupProf1

ETX-2i# configure qos queue-group-profile QGroupProf1
ETX-2i>config>qos>queue-group-profile(QGroupProf1)# info detail
queue-block 1/1
name "Level1QueueBlock"
profile "Scheduling2"
exit
queue-block 0/1
profile "QBlockProf1"
shaper profile "Shap2"
exit
queue-block 0/2
exit
WRED Profiles
The ETX-2i traffic management engine employs a weighted random early discard
(WRED) mechanism for intelligent queue management and congestion
avoidance. The WRED algorithm monitors the fill level of each queue and
determines whether an incoming packet should be queued or dropped, based on
statistical probabilities.
Applicable Products
Congestion control policy is defined by:
Tail drop for green packets Packets are queued if there is room in the
queue, and are dropped if the queue is full.
WRED profile for yellow packets

WRED profiles include the following parameters:
Maximum drop A percentage of the maximum threshold queue size that

probability defines the drop probability
Minimum Set to a percentage of the maximum queue depth. If a

threshold packet is queued and the queue size is between 0 and the
minimum threshold, the packet is admitted.
Maximum Set to a percentage of the maximum queue depth. If a

threshold packet is queued and the queue size is between the
minimum threshold and the maximum threshold, the
packet is dropped according to the drop probability of the
particular queue size.
Probability Set to a percentage of the maximum threshold queue size

that defines the drop probability
The following graph illustrates congestion control in ETX-2i.

WRED profile for
Drop yellow packets
probability (%)
100%
Tail drop for
green packets
Queue depth
Min Max 100% (% of maximum)
threshold threshold
Figure 11-9. Congestion Control
There are eight WRED profiles available, named WREDProfile0 through

WREDProfile7. They are bound to the internal queues automatically:
WREDProfile0 is bound to queue 0, WREDProfile1 is bound to queue 1, etc. You
cannot delete the WRED profiles, and you cannot add more WRED profiles. The
binding of the profiles to the queues is set and cannot be changed, but you can
change the profile parameters. You can view the assignment of WRED profiles to
queues via the info command in the queue block profile level.
Factory Defaults
There are eight WRED profiles available, named WREDProfile0 through
WREDProfile7, bound to the corresponding queues.
Configuring WRED Profiles
To configure WRED profiles:

1. Navigate to configure qos and type wred-profile WREDProfile<n> where n is
0 through 7.

The config>qos>wred-profile(WREDProfile<n>)# prompt is displayed.

2. Enter:
color yellow min <min-threshold> max <max-threshold> [probability
<max-probability>]
min-threshold queue usage minimum threshold in percentage, 0100
max-threshold queue usage maximum threshold in percentage, 0100
max-probability percentage of packets to be dropped when the queue
usage reaches the maximimum limit
Note You can configure the parameters for the color yellow only.
Example
To configure WRED profile 4:

Minimum threshold 64
Maximum threshold 100
Probability 50
exit all
configure qos wred-profile WREDProfile4
color yellow min 64 max 100 probability 50
exit all
save
To display the configuration information for WRED profile 4:

ETX-2i # configure qos wred-profile WREDProfile4
ETX-2i >config>qos>wred-profile(WREDProfile4)# info detail
color yellow min 64 max 100 probability 50
11.6 Layer-3 Service Activation Test

The Layer-3 service activation test (L3 SAT) provides an out-of-service (intrusive)
IP/UDP test to assess the proper configuration and performance of an IP
transport service prior to customer notification and delivery.
Standards
ITU-T Y.1564
Benefits
The Y.1564 testing methodology allows service providers to have a standard way
of measuring the performance of IP transport services. The tests are performed
per multiple traffic streams simultaneously, confirming policing per EVC or
EVC.CoS.
ETX-2i Layer-3 Service Activation Test 11-127

Factory Defaults
By default, there are no L3 SAT entities configured in ETX-2i.
When a peer profile is created, it has the following default configuration.
bw-steps 25 50 75 100
configuration-duration 100
performance-duration 120
policing-test policing-test
report-type no-clock-sync
scope configuration performance
udp-port 53248
When a session profile is created, it has the following default configuration.
availability-threshold 9990
delay-variation-threshold 100000
ip-size 256
loss-ratio-threshold 1000
When a peer is created, there is no default configuration.

When a test session is created, it has the following default configuration.
<name> <Not applicable> <name> must be specified when the test

session is created.
session-profile <Not applicable> <profile-name> must be specified when the

test session is created.
bw <Not applicable> <kbps> must be specified when the test

session is created.
dscp 0
When a generator is created, it has the following default configuration.
bind <not applicable> This parameter has no default configuration.
local-ip-address <not applicable> This parameter has no default configuration.
router-entity 1
vlan-tag <not applicable> This parameter has no default configuration.
11-128 Layer-3 Service Activation Test ETX-2i

When a responder is created, it has the following default configuration.
bind <not applicable> This parameter has no default configuration.
local-ip-address <not applicable> This parameter has no default configuration.
router-entity 1
udp-port 53248
vlan-tag <not applicable> This parameter has no default configuration.
L3 SAT testing has the following objectives:
Validate that the IP transport service is correctly configured.
Validate the quality of the services as delivered to the end user.
L3 SAT tests can be performed over Layer-3 networks, or as a Layer-3 service
over a Layer-2 network.
Test Phases
The methodology has a service configuration test phase followed by a service
performance test phase; the service configuration test is short in order to
prevent wasted time caused by failed service performance tests. The test
flowchart below illustrates the two phases.

Enter test
parameters
Start test
Service Fail Troubleshoot

configuration service
test configuration
Pass
Service
performance
test
Pass
Test completed
Figure 11-10. L3 SAT Test Flowchart
Configuration Test
The configuration test validates that services are configured as intended before
proceeding to the service performance test. The following are performed:
Preliminary (common for all test sessions):
Verify connectivity If the connectivity subtest fails, the configuration
test fails and the L3 SAT to the relevant peer is stopped. Otherwise, the
detected responder type is recorded and shown in the test report.
Determine the path MTU If the MTU subtest fails, the configuration
test fails and the L3 SAT to the relevant peer is stopped. Otherwise, the
discovered MTU is recorded and shown in the test report.
Note The preliminary tests are always performed, even if the configuration phase is
not included in the scope of the test.
Bandwidth subtests (one test session at a time):

Step load
Policing
The bandwidth subtests are performed for the packet sizes configured for the
test session. They are performed in increasing order of packet size, one packet

size at a time. The bandwidth subtest is successful if the subtest results are
within the configured Service Acceptance Criteria (SAC) limits.
If a bandwidth subtest fails for a particular packet size, the testing for that
packet size continues and all remaining bandwidth subtests are performed.
If packet sizes larger than the discovered MTU were configured for the test
session, the bandwidth subtest is considered failed for these packet sizes; it is
not performed for packet sizes larger than the MTU.
A test session is declared successful only if the results for all tested packet sizes
are within SAC limits.
Note When the report-type parameter is clock-sync (report includes parameters

requiring synchronization) and the responder type is loop and timestamp, an
additional requirement for a test session to be declared successful is that there
were no out-of-sync seconds during the test.
The configuration test is declared successful if the results for all the test
sessions are successful.
Performance Test
The performance test validates the quality of the services over a
user-configurable period of time, as follows:
Traffic is generated for all services at the configured bandwidth level.
For all the test sessions, test packets are sent simultaneously at 100% of
the bandwidth configured per test session.
Per test session, the duration of the performance test is evenly divided
between the different packet sizes, e.g. per test session, each packet size is
transmitted for an equal amount of time.
The performance test is declared successful if the results are within SAC limits.
Note When the report-type parameter is clock-sync (report includes parameters

requiring synchronization) and the responder type is loop and timestamp, an
additional requirement for the performance test to be declared successful is
that during the test, at least one minute was not excluded due to unavailability
or out-of-sync.
Test Elements
L3 SAT includes the following elements:
Generators Initiate multiple test sessions for multiple responders, send

out the test and OAM frames, receive responses from the
responder(s), process the resulting measurements, and
display test reports. Generators can support mixed
responder types.
Peers Used to run TWAMP test sessions. One or more peers can
be configured per generator with IP address(es)
corresponding to responder(s).
Test Sessions One or more test sessions can be configured per peer.

Responders Receive test and OAM frames from generator, and transmit
responses to generator. Responders can be the following
types:
IP loop filters incoming traffic by destination IP address,
and loops it back while performing MAC address swap and
IP address swap
UDP loop filters incoming traffic by destination IP address
and UDP port, and loops it back while performing MAC
address swap, IP address , and UDP port swap
Loop and timestamp filters incoming traffic by
destination IP address and UDP port and performs IP loop
for loss measurement packets, UDP loop with timestamp
for delay measurement packets
Note
Responders can be ETX-2i devices or third-party devices. Third-party responders
can be only IP loop or UDP loop types. Only ETX-2i can be a loop and timestamp
responder, and only an ETX-2i responder can provide one-way metrics.
Figure 11-11. L3 SAT Generators and Responders
Configuring L3 SAT Entities

To configure L3 SAT, perform the following steps:
1. In the responder device:
b. Configure and activate L3 SAT responder.
2. In the generator device:
b. Configure L3 SAT peer and session profile(s).

c. Configure and activate L3 SAT generator and relevant peers and test
sessions.
Configuring Generators
To configure L3 SAT generators:
1. Navigate to configure test l3sat.
The config>test>l3sat# prompt is displayed.
2. Enter:
generator <name> [l2-probe]
Note The optional parameter l2-probe is used to specify Layer-3 over Layer-2
operation. The default without the parameter is Layer-3 service.
The config>test>l3sat>generator(<name>)# prompt is displayed.

Binding generator to the port bind ethernet <port-index>

over which to test the service, bind logical-mac <port-number>
if the generator is working in bind pcs <port-number>
layer-2 probe mode
Configuring generator IP local-ip-address <ip-address>

address
Defining peer entity peer <ip-address> See Configuring Peers.

(corresponding to responder)
Associating generator with a router-entity <number> The parameter <number> is the

router that contains a suitable router number, in which a router
router interface interface must be configured with the
same IP address as local-ip-address.
Associating generator with vlan-tag <vlan> p-bit fixed <p-bit> <vlan> Outer VLAN tag of test
VLAN, if the generator is [inner-vlan <inner-vlan>] packets
working in layer-2 probe mode [inner-p-bit <inner-p-bit>] <p-bit> Outer VLAN priority of
vlan-tag <vlan> p-bit marking test packets
<dscp-to-pbit-profile> [inner-vlan <inner-vlan> Inner VLAN tag of
<inner-vlan>] [inner-p-bit <inner-p-bit>] test packets
<inner-p-bit> Inner VLAN priority
of test packets
<dscp-to-pbit-profile> Marking
profile used to mark outer VLAN
priority of test packets

disabling the generator disable the generator.
You should enable the generator only
after at least one responder has been
configured and enabled.
Viewing generator status show status

Configuring Peers
To configure L3 SAT peers:
1. Navigate to configure test l3sat generator <name>.
The config>test>l3sat>generator(<name>)# prompt is displayed.
2. Enter:
peer <ip-address>
The prompt config>test>l3sat>generator(<name>)> peer(<ip-address>)#
is displayed.
Activating or deactivating the activate You can activate a peer only if

peer test sessions no activate at least one test session has
been configured.
Assigning a peer profile to use peer-profile <profile-name>

for the peer parameters
Assigning a test session test-session <name> session-profile Multiple test sessions can be
<profile-name> bw <kbps> defined in the peer.
[dscp <number>] bw rate of the test session
traffic in Kbps
dscp priority value for the
test session traffic
Displaying results and show report <test-name> Available only if peer was
measurements for a specific test activated
Displaying summary of test show summary-report Available only if peer was

results and measurements activated
Displaying the peer status show status
Configuring Peer Profiles

To configure L3 SAT peer profiles:
2. Enter:
peer-profile <name>
The prompt config>test>l3sat> peer-profile(<name>)# is displayed.

Setting the number of steps and bw-steps <s1-percent> <s1-percent> transmission

their transmission rate in the bw-steps <s1-percent> <s2-percent> rate, as percentage of
bandwidth subtest configured bandwidth, at the
bw-steps <s1-percent>
first step of the step load
<s2-percent><s3-percent>
subtest (1100)
bw-steps <s1-percent> <s2-percent>
<s2-percent> transmission
<s3-percent><s4-percent>
rate, as percentage of
configured bandwidth, at the
second step of the step load
subtest (1100)
third step of the step load
subtest (1100)
fourth step of the step load
subtest (1100)
Note: You can define fewer than
four steps as long as the last
step is 100%.
Defining the duration of the configuration-duration <seconds> Possible values: 60300 seconds
configuration phase for each
test session
Defining the duration in minutes performance-duration <minutes> Possible values: 457200

of the performance phase minutes
Specifying whether to include or policing-test

exclude the traffic policing no policing-test
subtest from the configuration
phase
Defining which parameters are report-type {clock-sync | clock-sync Include

included in the test report no-clock-sync} parameters requiring
synchronization.
no-clock-sync Do not
include parameters requiring
synchronization.
See Viewing L3 SAT Test Reports
for details on which parameters
are included in the test report.
Setting the scope of the test: scope [configuration] [performance] You can enter the command
configuration test, performance with one or both parameters.
test, or both

Specifying start of the range of udp-port <port> Possible values: 065504

UDP ports that are used in the
tests
Configuring Session Profiles

To configure L3 SAT session profiles:
2. Enter:
session-profile <name>
The prompt config>test>l3sat>session-profile(<name>)# is displayed.
Defining Availability service availability-threshold <availability> Availability is measured in

acceptance criteria hundredths of percent units
(for example, use value 8930 in
order to define 89.3%).
Defining Packet Transfer Delay delay-threshold <s> Possible values: 01000000

service acceptance criteria, in
microseconds
Defining Packet Delay Variation delay-variation-threshold <s> Possible values: 01000000

microseconds
Defining test packet size ip-size [64] [128] [256] [512] [1024] You can specify up to four
[1280] [1500] [mtu] [custom <size>] packet sizes.
Range for custom <size>:
522094
Defining Packet Loss Ratio loss-ratio-threshold <ppm> Possible values: 01000000

ppm (1E-6 units)
Configuring Responders
To configure L3 SAT responders:
2. Enter:
responder <name> [l2-probe]
Note The optional parameter l2-probe s used to specify Layer-3 over Layer-2
operation. The default without the parameter is Layer-3 service.

The config>test>l3sat>responder(<name>)# prompt is displayed.

Binding responder to the bind ethernet <port-index>

port over which to test the bind logical-mac <port-number>
service, if the responder is bind pcs <port-number>
working in layer-2 probe
mode
Configuring responder IP local-ip-address <ip-address>

address
Associating responder with a router-entity <number> The parameter <number> is the router
router that contains a number, in which a router interface
suitable router interface must be configured with the same IP
address as local-ip-address.
Specifying start of the range udp-port <port> Possible values: 5324865520

of UDP ports that are used in
the tests
Associating responder with vlan-tag <vlan> p-bit fixed <p-bit> <vlan> Outer VLAN tag of test
VLAN, if the responder is [inner-vlan <inner-vlan>] packets
working in layer-2 probe [inner-p-bit <inner-p-bit>] <p-bit> Outer VLAN priority of
mode vlan-tag <vlan> p-bit marking test packets
<dscp-to-pbit-profile> [inner-vlan <inner-vlan> Inner VLAN tag of
<inner-vlan>] [inner-p-bit <inner-p-bit>] test packets
<inner-p-bit> Inner VLAN priority
of test packets
<dscp-to-pbit-profile> Marking
profile used to mark outer VLAN
priority of test packets

disabling the responder disable the responder.
Viewing responder status show status
Viewing L3 SAT Test Status

You can view the status of the test as it is running.
To display the test status (generator side):

At the
config>test>l3sat>generator(<generator-name>)>peer(<IP-address>)#
prompt, enter:
show status
ETX-2i>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show status
Last Connectivity Sub-test : Passed
Last MTU Sub-test : Not Applicable
Responder Type : Loop & Timestamp

Elapsed Time : 00:00:02

Time Remaining : 00:13:26
Current Phase :
TOD Status : Unknown
Test Name LM UDP Ports DM UDP Ports Status

-----------------------------------------------------------------------------
test1 53249, 53249 53248, 53248 In Progress
test2 53251, 53251 53250, 53250 In Progress
test3 53253, 53253 53252, 53252 In Progress
test4 53255, 53255 53254, 53254 In Progress
test5 53257, 53257 53256, 53256 In Progress
test6 53259, 53259 53258, 53258 In Progress
test7 53261, 53261 53260, 53260 In Progress
test8 53263, 53263 53262, 53262 In Progress
Note
Elapsed Time includes the time it has so far taken to perform the steps,
including the inter-step wait time.
To display the test status (responder side):

At the config>test>l3sat>responder(<responder-name>)# prompt, enter:
show status
ETX-2i>config>test>l3sat>responder(1)# show status
Application Type : L3 Over L2
Router Entity : 1
Responder Status : Ready
Total LM / DM Rx. Packets : 312164 / 1007
Viewing L3 SAT Test Reports

The generator calculates performance parameters according to the received test
packets, for each peer and its active test sessions. The performance parameters
are recalculated every minute. The performance parameters are presented in
test reports that can be viewed per peer and test session.
Note Unavailable and out-of-sync time affect parameter evaluation as follows:

A minute is considered as unavailable if it has more than 75% packet loss,
therefore is considered as available if it has packet loss less than or equal to
25%. Unavailable time is not used for performance parameter evaluation and
comparison with test objectives.
A minute is considered as out-of-sync if during the minute there was not
accurate TOD synchronization between the generator device and the
responder device. Out-of-sync time is not used for forward and backward
packet transfer delay (PTD) evaluation and comparison with test objectives.
To display summary test results:

At the

prompt, enter:
show summary-report
ETX-2i>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show summary-
report
End Points
Generator Address : 50.50.50.100
Responder Address : 50.50.50.101
MTU (bytes) : 1500
Test
Scope : Configuration + Performance
Peer Profile Name : peer1
Start Date & Time : 2014-12-04 13:28:10
End Date & Time : 2014-12-04 13:31:23
Total Duration : 193
Overall Result : Failed
Test Name BW DSCP Conf. Result Perf. Result

(Mbps)
-----------------------------------------------------------------------------
test1 2.000 3 Failed Not Applicable
test2 1.000 3 Failed Not Applicable
To display detailed test results:

At the
prompt, enter:
show report <test-name>
The detailed report is displayed. For information on the detailed test
report counters, see Table 11-16.
ETX-2i>config>test>l3sat>generator(gen3)>peer(50.50.50.101)# show report test1
End Points
Generator Address : 50.50.50.100
Responder Address : 50.50.50.101
LM UDP Ports : 53248, 53248
DM UDP Ports : 53249, 53249
MTU (bytes) : 1500
Test
Scope : Configuration + Performance
Peer Profile Name : peer1
Report Type : No Clock Sync
BW (Mbps) : 1.000
DSCP : 3
IP Sizes (bytes) : 128, 512, 750
Session Profile Name : session3
Start Date & Time : 2014-12-04 13:33:55
End Date & Time : 2014-12-04 13:42:08
Total Duration : 493

Configuration Phase
-----------------------------------------------------------------------------
Duration (sec) : 100
Configuration Result : Passed
IP Size (bytes) : 128
Step Load
-----------------------------------------------------------------------------
Parameter Step#1 Step#2 Step#3 Step#4 Thr
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.249 0.500 0.749 1.001
IR - mean (Mbps) 0.249 0.499 0.750 1.001
PL - count 1 0 0 1
PLR 6.0E-4 0 0 1.0E-4 1.000E-3
PTD - min (ms) 4.075 4.073 4.062 4.077
PTD - mean (ms) 4.142 4.137 4.132 4.132 200.000
PTD - max (ms) 4.248 4.268 4.267 4.265
PTD - std (ms) 0.032 0.040 0.041 0.042
PDV - mean (ms) 0.067 0.064 0.070 0.070 0.150
PDV - max (ms) 0.173 0.195 0.205 0.188
IPDV-Fwd - mean (ms) 0.023 0.039 0.032 0.030
IPDV-Fwd - max (ms) 0.139 0.087 0.103 0.102
IPDV-Bck - mean (ms) 0.020 0.023 0.017 0.020
IPDV-Bck - max (ms) 0.057 0.075 0.063 0.112
---------------- -------- -------- -------- -------- --------
Result Passed Passed Passed Passed
Policing
-----------------------------------------------------------------------------
Parameter Policing Thr
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - mean (ms) 0.150
PDV - max (ms)
IPDV-Fwd - mean (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - mean (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Step Load
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.250 0.498 0.749 0.997

IR - mean (Mbps) 0.250 0.497 0.750 0.997

PL - count 0 0 0 0
PLR 0 0 0 0 1.000E-3
PTD - min (ms) 4.780 4.753 4.764 4.769
PTD - mean (ms) 4.864 4.856 4.872 4.872 200.000
PTD - max (ms) 5.190 5.225 5.164 5.250
PTD - std (ms) 0.060 0.080 0.093 0.077
PDV - mean (ms) 0.084 0.103 0.108 0.108 0.150
PDV - max (ms) 0.410 0.472 0.400 0.481
IPDV-Fwd - mean (ms) 0.038 0.031 0.051 0.050
IPDV-Fwd - max (ms) 0.296 0.133 0.330 0.295
IPDV-Bck - mean (ms) 0.032 0.057 0.067 0.039
IPDV-Bck - max (ms) 0.314 0.394 0.315 0.138
---------------- -------- -------- -------- -------- --------
Policing
-----------------------------------------------------------------------------
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - max (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Step Load
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.250 0.498 0.748 0.999
IR - mean (Mbps) 0.250 0.498 0.748 0.998
PL - count 0 0 0 1
PLR 0 0 0 9.0E-4 1.000E-3
PTD - min (ms) 5.233 5.249 5.198 5.233
PTD - mean (ms) 5.296 5.297 5.318 5.318 200.000
PTD - max (ms) 5.577 5.357 5.731 5.757
PTD - std (ms) 0.052 0.025 0.099 0.102
PDV - mean (ms) 0.063 0.048 0.120 0.120 0.150
PDV - max (ms) 0.344 0.108 0.533 0.524
IPDV-Fwd - mean (ms) 0.028 0.021 0.064 0.058
IPDV-Fwd - max (ms) 0.079 0.064 0.470 0.488
IPDV-Bck - mean (ms) 0.024 0.013 0.039 0.046

IPDV-Bck - max (ms) 0.313 0.048 0.224 0.416

---------------- -------- -------- -------- -------- --------
Policing
-----------------------------------------------------------------------------
---------------- -------- --------
Tx Rate (Mbps)
IR - mean (Mbps)
PL - count
PLR 0 1.000E-3
PTD - min (ms)
PTD - mean (ms) 200.000
PTD - max (ms)
PTD - std (ms)
PDV - max (ms)
IPDV-Fwd - max (ms)
IPDV-Bck - max (ms)
---------------- -------- --------
Result
Performance Phase
-----------------------------------------------------------------------------
Duration (min) : 5
Configuration Result : Failed
Parameter IP Size #1 IP Size #2 IP Size #3 IP Size #4 Thr
128 bytes 512 bytes 750 bytes 0 bytes
---------------- -------- -------- -------- -------- --------
Tx Rate (Mbps) 0.999 0.997 0.998
IR - mean (Mbps) 0.999 0.997 0.998
PL - count 0 0 0
PLR 0 0 0 0 1.000E-3
UAS - count 0 0 0
Availability (%) 100.00 100.00 100.00 99.90
PTD - min (ms) 4.046 4.764 5.187
PTD - mean (ms) 4.171 4.899 5.401 5.401 200.000
PTD - max (ms) 4.444 5.337 5.875
PTD - std (ms) 0.064 0.112 0.158
PDV - mean (ms) 0.125 0.135 0.214 0.214 0.150
PDV - max (ms) 0.398 0.573 0.688
IPDV-Fwd - mean (ms) 0.049 0.077 0.110
IPDV-Fwd - max (ms) 0.234 0.399 0.593
IPDV-Bck - mean (ms) 0.037 0.047 0.097
IPDV-Bck - max (ms) 0.165 0.358 0.543
PD-Fwd - count 0 0 0
PDR-Fwd 0 0 0 0
PD-Bck - count 0 0 0
PDR-Bck 0 0 0 0
PR-Fwd - count 0 0 0
PRR-Fwd 0 0 0 0
PR-Bck - count 0 0 0
PRR-Bck 0 0 0 0

---------------- -------- -------- -------- -------- --------

Result Passed Passed Failed
The following table shows the test report parameters. The columns CS and NCS
indicate if the parameter is presented for report type clock-sync and
no-clock-sync, respectively. The forward direction refers to generator to
responder, and backward direction refers to responder to generator.
Table 11-16. L3 SAT Report Parameters
Counter Description CS NCS
Information Rate (IR) Number of received test packets times test packet Ethernet frame
length (in bits), divided by the elapsed time (in seconds)
Note: The test packet Ethernet frame length starts with the first
MAC address bit, and ends with the last FCS bit.
Packet loss (PL) Number of lost test packets. A test packet is considered lost in the
following cases:
Test packet was not received back at the generator, or was
received with a round-trip delay of over two seconds.
Report type parameter is clock-sync and the responder type is
loop and timestamp, and test packet was received with a
forward and/or backward delay over one second.
Packet loss ratio (PLR) Number of lost packets divided by the number of transmitted
packets
Unavailable seconds Total number of unavailable seconds.
Available seconds (%) Percentage of available seconds
Round-trip packet transfer Minimum round-trip PTD. The round-trip PTD is calculated from the
delay (PTD) min test packet embedded timestamps. A round-trip PTD over two
seconds is ignored, as the packet is considered lost.
Round-trip PTD mean Average round-trip PTD
Round-trip PTD max Maximum round-trip PTD
Round-trip PTD std Standard deviation round-trip PTD
One-way packet transfer delay Minimum forward PTD. The forward PTD is calculated from the test
(PTD), forward min packet embedded timestamps. A forward PTD over one second is
ignored, as the packet is considered lost.
Note: The one-way PTD measurements are valid only when there is
TOD synchronization between the generator device and the
responder device, and accurate TOD synchronization is feasible only
with a responder of type loop and timestamp.
One-way packet transfer delay Average forward PTD

(PTD), forward mean
One-way packet transfer delay Maximum forward PTD

(PTD), forward max
One-way packet transfer delay Standard deviation forward PTD

(PTD), forward std

One-way packet transfer delay Minimum backward PTD. The backward PTD is calculated from the
(PTD), backward min test packet embedded timestamps. A backward PTD over one
second is ignored, as the packet is considered lost.
One-way packet transfer delay Average backward PTD

(PTD), backward mean
One-way packet transfer delay Maximum backward PTD

(PTD), backward max
One-way packet transfer delay Standard deviation backward PTD

(PTD), backward std
Round-trip delay variation (PDV) Average round-trip PDV. The round-trip PDV is calculated according
mean to ITU-T Y.1540, by subtracting the minimum PTD from the 99.9%
percentile of the PTD values.
Round-trip delay variation (PDV) Maximum round-trip PDV

max
One-way packet transfer delay Average forward PDV

variation (PDV), forward mean
One-way packet transfer delay Maximum forward PDV

variation (PDV), forward max
One-way packet transfer delay Average backward PDV

variation (PDV), backward
mean
One-way packet transfer delay Maximum backward PDV

variation (PDV), backward max
One-way inter-packet delay Average forward IPDV. IPDV is calculated according to RFC 3393,
variation (IPDV) ), forward from the variations of the delays between valid packets.
mean Note: Appears in report only if responder type is loop and
timestamp.
One-way inter-packet delay Maximum forward IPDV

variation (IPDV) ), forward Note: Appears in report only if responder type is loop and
max timestamp.
One-way inter-packet delay Average backward IPDV. IPDV is calculated according to RFC 3393,
variation (IPDV) ), backward from the variations of the delays between valid packets.
mean Note: Appears in report only if responder type is loop and
timestamp.
One-way inter-packet delay Maximum backward IPDV

variation (IPDV) ), backward Note: Appears in report only if responder type is loop and
max timestamp.

One-way Packet Duplication Number of duplicate packets in forward direction. A packet is

(PD), forward considered duplicate (forward) if its generator Tx timestamp
matches that of a previously received packet, and the responder Tx
timestamps are different.
Note: Appears in report only if responder type is loop and
timestamp.
One-way Packet Duplication Number of duplicate packets in backward direction. A packet is

(PD), backward considered duplicate (backward) if its responder Tx timestamp
matches that of a previously received packet.
timestamp.
One-way Packet Duplication PDR (forward) is calculated as PD (forward) divided by the number
Ratio (PDR), forward of received valid packets, converted to a percentage.
One-way Packet Duplication PDR (backward) is calculated as PD (backward) divided by the

Ratio (PDR), backward number of received valid packets, converted to a percentage.
One-way Packets Reordered Number of reordered packets in forward direction. A packet is

(PR), forward considered reordered (forward) if its generatorTx timestamp is
smaller than that of a previously received packet in forward
direction. Duplicated and lost packets are not included in the
calculation.
timestamp.
One-way Packets Reordered Number of reordered packets in backward direction. A packet is

(PR), backward considered reordered (backward) if its responder Tx timestamp is
smaller than that of a previously received packet in backward
direction. Duplicated and lost packets are not included in the
calculation.
timestamp.
One-way Packets Reordered PRR (forward) is calculated as PR (forward) divided by the number
Ratio (PRR), forward of received valid packets, converted to a percentage.
One-way Packets Reordered PRR (backward) is calculated as PR (backward) divided by the

Ratio (PRR), backward number of received valid packets, converted to a percentage.
Examples
Layer-2 Probe Mode

This example illustrates configuring L3 SAT in layer-2 probe mode:
Generator with IP address = 20.20.20.101

Router: Associate Interface 2 with SVI 2 (type TWAMP).

Flows between Ethernet ports 0/1 and 0/3, classified to VLAN 100
exit all
#*********Configure SVI type TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit
flow E1toE3
classifier v100
no shutdown
exit
flow E3toE1
classifier v100
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.20/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT responder

test
l3sat
responder res1 l2-probe
bind ethernet 0/3
router-entity 1
vlan-tag vlan 100 pbit fixed 3
no shutdown
exit all
save
To configure the generator:

Router: Associate Interface 2 with SVI 2 (type TWAMP).
Flows between Ethernet ports 0/1 and 0/3, classified to VLAN 100

Test sessions:
Session1:
Packet sizes 128, 512, and 750
Bandwidth 10000
DSCP 11
Session2:
Default packet size (256)
Bandwidth 5000
DSCP 12
exit all
#*********Configure SVI type TWAMP
configure
port svi 2 twamp
no shutdown
exit
exit

flows
match vlan 100
exit

flow E1toE3
classifier v100
no shutdown
exit
flow E3toE1
classifier v100
no shutdown
exit
exit
#*********Configure router 1 with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.101/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT peer profile

test
l3sat

peer-profile peer1
performance-duration custom 5
exit
#*********Configure L3 SAT session profiles

session-profile session1
ip-size 128 512 custom 750
exit
exit
#*********Configure L3 SAT generator
generator gen1 l2-probe
bind ethernet 0/3
router-entity 1
vlan-tag vlan 100 pbit fixed 3
no shutdown
peer 20.20.20.20
peer-profile peer1
test-session test1 session-profile session1 bw 10000
dscp 11
dscp 12
activate
exit
exit all
save
Layer-3
This example illustrates configuring L3 SAT in Layer-3 mode:
Generator with IP address = 20.20.20.101

Ethernet port 0/3 to SVI 2: Traffic tagged with VLAN 12, VLAN popped
SVI 2 to Ethernet port 0/3: All traffic, VLAN 12 pushed
exit all
#*********Configure SVI for L3 SAT
configure
port
svi 2
no shutdown
exit
exit
#********* Configure classifiers for VLAN 12 & all traffic

flows
match vlan 12

exit
match all
exit
flow E3toSVI2
classifier v12
vlan-tag pop vlan
no shutdown
exit
flow SVI2toE3
ingress-port svi 2
classifier all
no shutdown
exit
exit
#*********Configure router with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.20/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT responder

test
l3sat
responder res1
router-entity 1
no shutdown
exit all
save
To configure the generator:

Ethernet port 0/3 to SVI 2: Traffic tagged with VLAN 12, VLAN popped
SVI 2 to Ethernet port 0/3: All traffic, VLAN 12 pushed
Test sessions:
Session1:
Packet sizes 512, 700
Bandwidth 10000
DSCP 11

Session2:
Default packet size (256)
Bandwidth 5000
DSCP 12
exit all
#*********Configure SVI for L3 SAT
configure
port
svi 2 twamp
no shutdown
exit
exit
#********* Configure classifiers for VLAN 12 & all traffic

flows
match vlan 12
exit
match all
exit

flow E3toSVI2
classifier v12
vlan-tag pop vlan
no shutdown
exit
flow SVI2toE3
ingress-port svi 2
classifier all
no shutdown
exit
exit
#*********Configure router with interface 2 for L3 SAT

router 1
interface 2
address 20.20.20.101/24
bind svi 2
no shutdown
exit
exit
#*********Configure L3 SAT peer profile

test
l3sat
peer-profile peer1

exit
#*********Configure L3 SAT session profiles
ip-size 512 custom 700
exit
exit
#*********Configure L3 SAT generator

generator gen1
router-entity 1
no shutdown
peer 20.20.20.20
peer-profile peer1
dscp 11
dscp 12
activate
exit all
save
11.7 RFC-2544 Testing

You can perform BERT testing based on RFC-2544:
Throughput test Detect the maximum frame rate without lost frames.
Packet loss test Detect the point at which frame loss does not occur.
Latency test Determine average frame roundtrip time.
Note
You can run the RFC-2544 tests up to 1 GbE at a time.
Applicable Products
Standards
RFC-2544, Benchmarking Methodology for Carrier Ethernet Networks
Benefits
You can evaluate the performance of network devices to provide performance
metrics of the Ethernet network and validate the SLA.
ETX-2i RFC-2544 Testing 11-151

RFC-2544 testing uses OAM CFM messages such as Loopback (LB), Loss
Measurements (LM), and Delay Measurements (DM) frames. Therefore,
end-to-end OAM CFM is necessary for the testing. User data cant be
transmitted via associated OAM service data/flows while an RFC-2544 test is
running.
In a bidirectional throughput test, the local ETX-2i generates LBM + data TLV
messages towards the far-end device, which responds with LBR messages. The
local ETX-2i calculates the round trip throughput.
In a unidirectional throughput test, the local ETX-2i generates 1DM messages
towards the far-end device, which verifies the frames and calculates
unidirectional throughput. The convergence algorithm is based on a binary
search using LMM and LMR messages.
The packet loss test is performed as follows for all selected frame sizes:
Transmit x frames at a rate of 100% throughput.
Calculate frame loss with the formula: (tx - rx) / 100 * tx
Decrease rate by 10% and repeat the test until two trials result in no frame
loss.
The latency test is performed as follows:
Transmit DMM frames at throughput rate for 10 seconds.
Calculate the latency using DMM and DMR frames that are transmitted after
1 second.
The test result is the average of the number of iterations per frame size (up
to 5 minutes per frame size).
Applicable for round-trip mode
Note If the remote MEP status is NEW, ETX-2i does not launch the RFC-2544 test,
unless the relevant dest NE is configured with the remote MAC address.
Factory Defaults
By default, no profiles or tests are defined.
When you create a test profile, it is configured by default as shown below.
ETX-2i# config test rfc2544
ETX-2i>config>test>rfc2544# profile-name Testprf
ETX-2i>config>test>rfc2544>profile-nam(Testprf)$ inf d
frame-size 64
pattern all-ones
tlv-type data
test-direction bidirectional
frames-number-in-attempt 200000
frame-loss-tolerance 20
throughput-measurement-accuracy 100000
number-of-trials 1
no learning-frames
11-152 RFC-2544 Testing ETX-2i

When you create a test, it is configured by default as shown below.

ETX-2i# config test rfc2544
ETX-2i>config>test>rfc2544# test 1
ETX-2i>config>test>rfc2544>test(1)$ inf d
no bind
max-rate 0 convention data-rate compensation 0
type throughput
no max-test-duration
no associated-flow
Performing Tests
In order to perform RFC-2544 tests, you must configure:
Bidirectional data flows that are administratively enabled. If one of the flows
is associated with the test, its egress port and queue block must be identical
to the associated port and queue block of the MEP to which the test is
bound.
MEP and Destination NE
RFC-2544 profile Template to create test runs. You can configure up to
eight test profiles.
RFC-2544 test Associated with RFC-2544 profile. Up to eight tests can use
the same test profile. In one RFC-2544 test, you can perform one or more of
the three test types.
Note Up to eight RFC-2544 tests can run concurrently.
If you are performing more than one type of test, they are performed in the
following order:
Throughput
Packet loss
Latency Up to 20 latency test attempts are performed in the remaining
time, according to the configured maximum test duration (each attempt
requires 15 seconds).
To configure RFC-2544 test profiles:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
profile-name <name>
A test profile with the specified name is created if it does not already
exist, and the config>test>RFC2544> profile-nam(<name>)# prompt is
displayed.

Configuring frame loss tolerance 1/1 frame-loss-tolerance <frames> Defines the success criteria for
(one to one) the throughput test.
Each throughput attempt is
defined as a success only if the
amount of lost packets is less
than or equal to the number of
frames configured for frame-
loss-tolerance.
Success in a throughput
attempt sets the next attempt
to a higher rate, while a failure
in an attempt sets the next
attempt to a lower rate.
Configuring frame sizes for the test frame-size [64] [128] [256] [512] [1024] [1280] You can specify one or more
[1518] [1700] [1900] [2000] [custom <custom>] standard frame sizes, as well as
a custom frame size (642000).
Configuring how many frames in frames-number-in-attempt The maximum number of frames

attempt (transmitted packets) is the
maximal value of unsigned long
(4294967295 (0xffffffff)).
Configuring amount and frequency of learning-frames number <value> frequency { once |

learning frames once-per-trial }
no learning-frames
Configuring the number of trials for number-of-trials <value> Possible values: 13

the test
Configuring pattern of test frame pattern { all-ones | all-zeros-without-crc |

payload all-zeros-with-crc | alternate | prbs-with-crc |
prbs-without-crc }
Configuring direction of test test-direction { unidirectional | bidirectional }

(unidirectional or bidirectional)
Configuring accuracy of throughput throughput-measurement-accuracy <bps>

measurement
Disabling ETH-LCK frame when no eth-lck By default, ETH-LCK is enabled.

activating RFC-2544 test
Configuring TLV type as test or data tlv-type { test | data }
To configure RFC-2544 tests:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
test <id>
The config>test>rfc2544> test(<id>)# prompt is displayed.

Activating the test activate date <dd-mm-yyyy> <hh:mm:ss> Type no activate to stop the
activate recurring <hours> test.
Associating test with flow in order to associated-flow <name> Flow must be active and its
retrieve bandwidth profile and QoS egress port and queue block
information. must be identical to the
associated port and queue
block of the MEP to which the
test is bound.
Binding to destination NE bind oam-cfm md <md-id> ma <ma-id> mep <mep-id> There must be bidirectional
service <service-id> dest-ne <dest-ne-id> flows using the same
classification and port
associated with the MEP.
Configuring maximum rate for test max-rate <bps> [convention {line-rate | data-rate}] max-rate The maximum rate
[compensation <compensation>] applies to throughput and loss
tests.
convention Determines
whether the interpacket gap is
included in test result
calculations:
line-rate Interpacket gap is
included.
data-rate Interpacket gap is
not included.
compensation Allowed range
is 063. The compensation
value is added to frame size, to
allow for Layer-1 overhead in
the network.
Note: It is not necessary to
configure the maximum rate if
associated-flow is used to
associate the test with a flow
that has a policer profile, as in
that case the maximum rate is
derived from the flow policer
profile.
Configuring maximum duration of max-test-duration <minutes> Possible values: 0, or 260
test The value 0 indicates no limit;
the test runs until it completes.
If a value from 260 is
configured, the test is stopped
when the configured maximum
duration has elapsed, whether
or not all the configured test
types have completed.

Associating a test profile with the test-profile <name>

test
Defining the type(s) of benchmark type [throughput] [latency] [frame-loss]

test to perform on this run
Clearing test report clear-reports
Displaying number of lost frames for show attempt-lost-frames See Viewing Lost Frames Per
each test attempt Test Attempt.
Displaying test report show report all See Viewing Test Report.
show report iteration <iteration-number>
Displaying test status show status See Viewing Test Status.
Displaying test summary show summary See Viewing Test Results.
Examples
Running RFC-2544 Test

To run RFC-2544 test:
Test direction bidirectional
Number of trials 2
Frame sizes 64, 256, 1400 [custom]
Test types throughput, frame loss, latency
Bound to MD 1 MA 1 service 1 MEP 1 Destination NE 1
Associated to flow test_flow1, that has associated policer profile
test_policer with CIR=9984, EIR = 0, and is associated with classification,
port, and queue block of the above MEP
Maximum test duration 1 hour
ETX-2i# configure test rfc2544
ETX-2i>config>test>rfc2544# profile-name p1
ETX-2i>config>test>rfc2544>profile-nam(p1)$
ETX-2i>config>test>rfc2544>profile-nam(p1)$ frame-size 64 256 custom 1400
ETX-2i>config>test>rfc2544>profile-nam(p1)$ pattern all-ones
ETX-2i>config>test>rfc2544>profile-nam(p1)$ tlv-type data
ETX-2i>config>test>rfc2544>profile-nam(p1)$ test-direction bidirectional
ETX-2i>config>test>rfc2544>profile-nam(p1)$ frames-number-in-attempt 5000
ETX-2i>config>test>rfc2544>profile-nam(p1)$ frame-loss-tolerance 10
ETX-2i>config>test>rfc2544>profile-nam(p1)$ number-of-trials 2
ETX-2i>config>test>rfc2544>profile-nam(p1)$ no learning-frames
ETX-2i>config>test>rfc2544>profile-nam(p1)$ no eth-lck
ETX2x>config>test>rfc2544>profile-nam(p1)$ exit
ETX-2i>config>test>rfc2544# test 1
ETX-2i>config>test>rfc2544>test(1)$ test-profile p1
ETX-2i>config>test>rfc2544>test(1)$ type throughput latency frame-loss
ETX-2i>config>test>rfc2544>test(1)$ bind oam-cfm md 1 ma 1 mep 1 service 1
dest-ne 1

ETX-2i>config>test>rfc2544>test(1)$ associated-flow test_flow1

ETX-2i>config>test>rfc2544>test(1)$ max-test-duration 60
ETX-2i>config>test>rfc2544>test(1)$ activate
ETX-2i>config>test>rfc2544>test(1)$ show status
Activity Status : In Progress
Elapsed Time <dd:hh:mm:ss> : <00:00:15:24>
ETX-2i>config>test>rfc2544>test(1)$ show status
Activity Status : Completed
ETX-2i>config>test>rfc2544>test(1)$ show summary

Iteration Start Start Duration Duration
Date Time Days Time
-----------------------------------------------------------------------------
1 08-01-2012 11:31:43 0 <00:38:25>
Viewing Test Report

You can display the test report for all iterations, or for a specific iteration.
The following illustrates displaying the test report for the test from the above
section (all iterations).
To display the complete test report:

In the config>test>rfc2544>test<test number># prompt, enter show report
all.
The complete report screen is displayed. For information on the test
report counters, see Table 11-17.
ETX-2i>config>test>rfc2544>test(1)$ show report all
Test ID : 1
Iteration Number : 1
Date & Time : 08-01-2012 11:31:43
Profile Name : p1
Number of Trials : 2
Duration <dd:hh:mm:ss> : <00:00:38:25>
Test Parameters
-----------------------------------------------------------------------------
Bind: MD : 1 MA : 1
MEP : 1
P-Bit : 0 VLAN : 200
Max Rate (bps) : 1000000000
Convention : Data Rate Compensation : 0
Frames in Burst : 200000
Pattern : All Ones
Frame Type : Data
Search Resolution : 1 Tolerance : 5
Learning Frames: : 0 Frequency :
Direction : Bidirectional
Flow Parameters
-----------------------------------------------------------------------------
Flow Name : test_flow1
Fixed Queue : 0 Mapping Profile :
Policer Name : test_policer
CIR (Kbps) : 9984 EIR (Kbps) : 0

Throughput Report
-----------------------------------------------------------------------------
Trial : 1
Status : Success Duration : <00:00:00:49>
Frame Size Theoretical Max Throughput Throughput Success
(FPS) (FPS) (Mbps) (%)
-----------------------------------------------------------------------------
64 1953125 1490312 763.040 76
256 488281 453309 928.379 92
1400 97656 96173 984.812 98
Throughput Report
-----------------------------------------------------------------------------
Trial : 2
Frame Size Theoretical Max Throughput Throughput Success
(FPS) (FPS) (Mbps) (%)
-----------------------------------------------------------------------------
64 1953125 1490312 763.040 76
256 488281 453309 928.379 92
1400 97656 96173 984.812 98
Loss Report
-----------------------------------------------------------------------------
Trial : 1
Frame Size : 64
Theoretical Max (FPS) : 1953125
Throughput of Max Success

(%) (%)
-----------------------------------------------------------------------------
100 76
90 84
80 95
70 100
60 100
Frame Size : 256


(%) (%)
-----------------------------------------------------------------------------
100 92
90 100
80 100
Frame Size : 1400


(%) (%)

-----------------------------------------------------------------------------
100 98
90 100
80 100
Loss Report
-----------------------------------------------------------------------------
Trial : 2
Frame Size : 64

(%) (%)
-----------------------------------------------------------------------------
100 76
90 84
80 95
70 100
60 100
Frame Size : 256

(%) (%)
-----------------------------------------------------------------------------
100 92
90 100
80 100
Frame Size : 1400


(%) (%)
-----------------------------------------------------------------------------
100 98
90 100
80 100
Latency Report
-----------------------------------------------------------------------------
Trial : 1

Num of Attempts : 20
Frame Size Latency

(micro-sec)
-----------------------------------------------------------------------------
64 1

256 1
1400 1
Latency Report
-----------------------------------------------------------------------------
Trial : 2

Num of Attempts : 20
Frame Size Latency

(micro-sec)
-----------------------------------------------------------------------------
64 0
256 0
1400 0
ETX-2i>config>test>rfc2544>test(1)$
To display the test report for a specific iteration:

In the config>test>rfc2544>test<test number># prompt, enter show report
iteration <iteration number>.
The report screen is displayed for the requested iteration. For
information on the test report counters, see Table 11-17..
ETX-2i>config>test>rfc2544>test(1)# show report iteration 1
Test ID : 1
Iteration Number : 1
Date & Time
Profile Name : p1
Number of Trials : 1
Duration <dd:hh:mm:ss>
Test Parameters
-----------------------------------------------------------------------------
Bind: MD : 1 MA : 1 MEP
: 1
P-Bit : 0 VLAN : 100
Max Rate (bps) : 100000
Convention : Data Rate Compensation : 0
Frames in Burst : 100000 Pattern : All
Ones Frame Type : Data
Search Resolution : 10000 Tolerance : 50
Learning Frames : 0 Frequency :
Direction : Bidirectional
Table 11-17. RFC-2544 Test Parameters
Counter Description
Bind The MEP parameters that the RFC-2544 test is running on
P-Bit The P-Bit of the tested service

Counter Description
VLAN The VLAN on which test is performed
Max Rate (bps) The maximum rate at which the test starts
Convention Convention used for this test:

Line Rate or Data Rate
Compensation Indicates whether compensation due to editing will be performed in

the test and the number of bytes that will be compensated
Frames in Burst The number of frames transmitted in each attempt
Pattern The data pattern in the transmitted packets
Frame Type The frame type (TLV) used in the transmitted packets:
Data or Test
Search Size of the smallest search resolution step

Resolution
Tolerance The number of packets that can be lost without declaring Fail
Learning Frames Indicates whether some frames are transmitted before the test
starts, in order to enable the network learning
Frequency Indicates whether learning frames are transmitted once per test or
once per trial
Direction Bidirectional or Unidirectional
Viewing Test Status
To display the test status:

In the config>test>rfc2544>test<test number># prompt, enter show status.
The status screen appears. For information on the test status values,
see Table 11-18.
ETX-2i>config>test>rfc2544>test(1)# show status
Activity Status : In Progress
Elapsed Time <dd:hh:mm:ss> : <00:00:16:39>
Current Test Type : Throughput Current Frame Size : 64

Trial No. : 1 Attempt No. : 1
Remote MEP Status : OK
Table 11-18. RFC-2544 Test Status
Displayed
Current Test Type Test type can be:

Throughput
Packet Loss
Latency
Current Frame Size Current tested frame size

Displayed
Trial No. Current trial number. 13
Attempt No. Current performed attempt number
Remote MEP Peer OAM status

Status
Viewing Lost Frames Per Test Attempt

The following illustrates displaying the number of lost frames for each test
attempt.
ETX-2i>config>test>rfc2544>test(1)$ show attempt-lost-frames
Test ID : 4
Number of Frames in Attempt : 700000
Trial : 1
Frame Size : 128
Attempt Throughput Loss Frames

---------------------------------------------------------------
1 999999488 559210
2 499999744 419391
3 249999872 139756
4 124999936 0
5 187499904 0
6 218749888 59908
7 203124896 10805
8 195312400 0
9 199218648 0
10 201171772 4070
11 200195210 650
Viewing Test Results

You can display a summary of the RFC-2544 test results.
To display the summary test results:

In the config>test>rfc2544>test<test number># prompt, enter show
summary.
The summary report screen is displayed. For information on the test
report summary counters, see the following table.
ETX-2i>config>test>rfc2544>test(5)# show summary
Iteration Start Start Duration Duration
Date Time Days Time
---------------------------------------------------------------
1 10-08-2015 15:16:40 0 <04:17:04>

Table 11-19. RFC-2544 Test Counters (Summary)
Counter Description
Iteration The iteration number of the test
Start Date The date that the test started (dd-mm-yyyy)
Start Time The time of day that the test started (hh:mm:ss)
Duration Days The duration of the test in days
Duration Time The duration of the test (hh:mm:ss)
11.8 Syslog
ETX-2i uses the Syslog protocol to generate and transport event notification
messages over IP networks to Syslog servers.
Applicable Products
Standards
RFC 3164, RFC 5674
Benefits
Syslog protocol collects heterogeneous data into a single data repository. It
provides system administrators with a single point of management for collecting,
distributing, and processing audit data. Syslog standardizes log file formats,
making it easier to examine log data with various standard tools. Data logging
can be used for:
Long-term auditing
Intrusion detection
Tracking user and administrator activity
Product operation management
The Syslog protocol provides an instrument for generating and transporting
event notification messages from ETX-2i to servers across IP networks.
Elements
Typical Syslog topology includes message senders (clients) and message
receivers (servers). ETX-2i supports Syslog client functionality. It can send
messages to up to five Syslog servers. The receiver displays, stores, or forwards
logged information. The standard designates two types of receivers:
ETX-2i Syslog 11-163

Relay Forwards messages
Collector Displays and stores messages
Transport Protocol
Usually, Syslog uses UDP port 514 for its transport, but devices and servers can
be defined to use any port for communication.
Message Format
The length of a Syslog message is 1024 bytes or less. It contains the following
information:
Facility and severity (see below)
Host name or IP address of the device
Timestamp
Message content
A typical Syslog message looks like this:
<145>Jan 15 13:24:07 172.17.160.69 Eth 1: Loss of signal (LOS)
Facilities and Severities

Facility designates a device or application that sends a message. The standard
includes some predefined facilities in the 015 range. For originator
identification, ETX-2i can be configured to use facilities local1 local7; local1 is
the default facility.
Severity is assigned to a message to specify its importance. ETX-2i uses the
following severity designations:
Table 11-20. Syslog Severities
Code Syslog Type Description
0 Emergency Emergency message, not in use
1 Alert Critical alarm
2 Critical Major alarm
3 Error Minor alarm
4 Warning Event
5 Notice Cleared alarm and accounting message
6 Informational Informational message, not in use
7 Debug Debug-level messages, not in use
Factory Defaults
By default, Syslog operation is disabled. When enabled, the default parameters
are as follows:
11-164 Syslog ETX-2i

facility local1
port 514
severity-level informational
Configuring Syslog Parameters

When configuring Syslog parameters, it is necessary to enable Syslog device
(client) and define Syslog servers. The remaining configuration is optional.
To configure Syslog device:

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

messages are sent local4 | local5 | local6 | local7}
Defining Syslog device UDP port for port <udp-port-number> Possible values: 165535
communication Port configuration is allowed
only if a Syslog device is
Defining severity level severity-level { emergency | alert | The log messages that contain
critical | error | warning | notice | severity level above or equal to
informational | debug} the specified level are
transmitted.
emergency emergency
messages
alert critical alarms
critical major alarms
error minor alarms
warning events
notice cleared alarms,
accounting messages
informational
informational messages
debug debug messages
Administratively enabling Syslog device no shutdown shutdown administratively

disables the Syslog device.
Displaying Syslog statistics show statistics See Viewing Syslog Statistics.
Clearing Syslog statistics clear-statistics See Clearing Syslog Statistics.
ETX-2i Syslog 11-165

To configure a Syslog server:

2. At the config>system# prompt, enter syslog server <server-ID> to specify
the server to receive Syslog messages, where <server-ID> is 1 to 5.
The config>system>syslog(server/<server-ID>)# prompt is displayed.
Enabling logging of command entries accounting commands To disable command logging,

enter no accounting.
Defining Syslog server IP address address <ip-address> Possible values:

0.0.0.0255.255.255.255
Defining Syslog server UDP port for port <udp-port-number> Possible values: 165535
communication
Administratively enabling Syslog server no shutdown shutdown administratively

disables Syslog server.
Viewing Syslog Statistics

To display Syslog statistics:
2. At the config>system>syslog(device)#, enter show statistics.
Syslog statistics appear as shown below. The counters are described in
the following table.
ETX-2i>config>system>syslog(device)# show statistics
Total Tx Messages : 356
Non-queued Dropped Messages : 265
Table 11-21. Syslog Statistic Parameters
Total Tx Messages The total number of Syslog messages transmitted
Non-queued Dropped The total number of Syslog messages that were

Messages dropped before being queued
Clearing Syslog Statistics

To clear Syslog statistics:
11-166 Syslog ETX-2i

2. At the config>system>syslog(device)# prompt, enter clear-statistics.

The Syslog statistic counters are set to 0.
The following table lists messages generated by ETX-2i when a configuration
error is detected.
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 Selected UDP port is already in use.
use
Parameter cannot be changed if Logging Device/server UDP port or server IP address cannot be changed
Status/Server Access is enabled while Syslog server is enabled.
Illegal Severity Invalid severity value
Illegal Facility Invalid facility value
Illegal Server IP Address Invalid server IP address
Example
Server IP address: 178.16.173.152
UDP port: 155
exit all
configure system
syslog device
no shutdown
exit
syslog server 1
address 178.16.173.152
port 155
no shutdown
save
exit all
11.9 Y.1564 Ethernet Service Activation Test

The Ethernet service activation test provides out-of-service test methodology to
assess the proper configuration and performance of an Ethernet service prior to
customer notification and delivery.
ETX-2i Y.1564 Ethernet Service Activation Test 11-167

Applicable Products
This feature is applicable to all ETX-2i products, except for capacity differences
between products that are specified where relevant.
Standards
ITU-T Y.1564
Benefits
The Y.1564 testing methodology allows service providers to have a standard way
of measuring the performance of Ethernet-based services. The tests are
performed per multiple traffic streams simultaneously, confirming policing per
EVC or EVC.CoS.
Factory Defaults
By default, Ethernet service activation testing functionality is disabled.
When a Y.1564 test profile is added, it has the following default settings:
Parameter Default Value Units
auto-cos-completion no auto-cos-completion
ethernet-type 0x22e8
frame-size 512 Bytes
round-trip-thresholds flr 200 PPM (1E-6)

ftd 26000 Microseconds
fdv 11000 Microseconds
availability 9990 Hundredths of percent
direction bidirectional
color-aware color-aware
traffic-policing traffic-policing
cir-steps s1-percent 25
s2-percent 50
s3-percent 75
s4-percent 100
configuration-duration 60 Seconds
performance-duration 120 Minutes
rate-convention data-rate
responder-type y1564
user-traffic-blocked user-traffic-blocked
11-168 Y.1564 Ethernet Service Activation Test ETX-2i

To assure quality of service (QoS), providers must properly configure their
networks to define how the traffic is prioritized in the network. This is
accomplished by assigning different levels of priority to each type of service and
accurately configuring network prioritization algorithms. QoS enforcement refers
to the method used to differentiate the traffic of various services via specific
fields in the frames, thus providing better service to some frames over other
ones.
SLAs
The service-level agreement (SLA) is a binding contract between a service
provider and a customer, which guarantees the minimum performance that is
assured for the services provided.
Customer traffic is classified into three traffic classes, and each is assigned a
specific color: green for committed traffic, yellow for excess traffic, and red for
discarded traffic.
Policing
ETX-2i can set different traffic policing parameters. When a policer is activated,
it monitors the incoming frames and determines their color mode (CM). If CM is
set to color aware, ETX-2i monitors incoming frames and assigns them the
relative color (green or yellow) based on the frame header matching the policer
setting and current information rate.
Notes When the Y.1564 test is configured as bidirectional, it may fail if the policer
profiles for the directions generator->responder and responder->generator
are different. For instance, the test could fail if a policer profile is defined for
the Rx and Tx flows in the generator, and the bandwidth of the ingress
policer is lower than that of the egress policer.
You should configure a non-default policer profile for the Tx flow, and
configure no profile for the Rx flow.
If multiple Tx flows are attached to the same MEP in the responder, any
policer profile attached to the Tx flows is not used in the responder egress
direction (back towards the generator).
The Y.1564 generator discovers the test rate per service or service.CoS
policer, even when the policer is not an aggregate policer.
Blocking User Traffic

By default, user traffic on the flows associated with the test is automatically
blocked by the device from the time a test is activated until it is completed. You
can leave this default or configure the test to allow user traffic on the flows
associated to the test.
Y.1564 over LAG

When LAG exists on the network path, Y.1564 is limited in its ability to test the
full path SLA of the EVC. To overcome this limitation, ETX-2i supports changing
the source MAC address (SA) in each transmitted frame (instead of the default,
where the SA of the test frame is automatically inherited from the port that the

associated MEP is bound to), so that the frames pass through all the links in the
network LAG.
In the Y.1564 test profile, you can select this operation mode, by setting a block
of 32 consecutive MACs as SA. The SAs of generated test frames are then
cyclically selected from the block of 32 consecutive MAC addresses. By default,
0x0020D2000100 is the first MAC address in the block of MACs used as SA in
test frames. However, you have the option of setting another first address,
provided it is a multiple of 32.
When the hashing function of the network LAG is set to SA+DA MAC, the Y.1564
frames pass through all the links of the LAG, enabling testing the SLA of the
different links.
LAG (SA+DA MAC HASH) Y.1564 Gen
L2
Network ETX-2i
Router
Figure 11-12. Y.1564 over LAG
Y.1564 Standard
The ITU-T Y.1564 testing methodology ensures that quality is maintained across
networks with multiple streams and different policing parameters. Service
providers use the SAC (Service Acceptance Criteria) information which is normally
based on a subset of the users SLA to set pass/fail parameters.
There are two main objectives:
To validate that each Ethernet-based service is correctly configured
To validate the quality of the services as delivered to the end user
The test flowchart below illustrates the test phases.

Enter test
parameters
Start test
Service Fail Troubleshoot

configuration service
test configuration
Pass
Service
performance
test
Pass
Test completed
Figure 11-13. Y.1564 Test Flowchart
Configuration Test
The configuration test validates that services are configured as intended before
proceeding to the service performance test. Each service is tested individually
and the information rate (IR), Frame Transfer Delay (FTD), Frame Delay Variation
(FDV), and Frame Loss Ratio (FLR) are measured simultaneously. The test is
declared successful if the information rate and frame counters are within the
Service Acceptance Criteria (SAC).
The configuration test consists of the following procedures (mandatory to
implement and optional to perform):
CIR (simple or stepped)
EIR (color-blind)
Traffic policing (color-blind); can be disabled
In addition, the configuration test consists of the following burst test
procedures (optional to implement):
CBS (color-aware or color-blind)
EBS (color-aware or color-blind)

The CBS and EBS burst sub-tests can be disabled (the default) or enabled. These
tests cannot coexist with another configuration test; if they do, a sanity error
occurs. However, they can coexist with other running performance tests.
A burst sub-test (CBS, EBS) consists of at least one transmission cycle. If
needed, the actual duration of a burst sub-test is automatically extended i.e. by
increasing the total duration of the configuration test.
Performance Test
The performance test validates the quality of the services over a
user-configurable period of time (one minute to five days). Traffic is generated
for all services at configured CIR levels; all Ethernet performance parameters are
measured simultaneously. The bandwidth test is performed according to the
bandwidth profile of a policer assigned to the associated flow, or a policer
assigned to the test.
Note If there are two bandwidth profiles (flow and test), the test bandwidth
profile is used.
OAM relevant packets are calculated as part of the test bandwidth.
Test Elements
The Y.1564 test is an intrusive procedure that includes two main elements:
Generator an entity that initiates the test, sends out the test and OAM
frames, receives responses from the responder, processes the resulting
measurements and displays test reports. In the case of a MEF46 LL
responder, the generator executes the Latching Loopback (LL) controller
functionality.
Responder an entity that receives the test and OAM frames from the
generator, and transmits a response to the generator. The responder can be
of the following types:
Regular responder adds time stamps to the OAM frames that it returns
to the generator
MAC swap responder does not add time stamps to the OAM frames
that it returns to the generator
MEF46 Latching Loopback responder Upon receiving LLM from the
generator, replies with LLRs. OAM frames are not looped back.
While performing/running the Y.1564 test, the responder does not transmit
PM packets.
The test operation can be configured as unidirectional or bidirectional (the
default). When bidirectional, service performance is measured on the frames
that make a round trip (generator > receiver > generator).
PSN
Forward
Backward
Generator Responder
Figure 11-14. Y.1564 Test Elements

Capacity
ETX-2i supports up to 8 simultaneous Y.1564 tests, with:
Up to eight generators; one MEP per generator
Up to 20 responders for ETX2i and up to eight for ETX-2i-B and ETX-2i-10G
The 8 generators and 8/20 responders can be activated over EVC, EVC.CoS, or a
combination of EVC and EVC.CoS. The Y.1564 generator is limited to two VLANs.
The rate of the Y.1564 traffic for a single generator/responder or several
generators/responders running in parallel, cannot exceed 1 Gbps for ETX2i or
ETX-2i-B; 10 Gbps for ETX-2i-10G.
The test requires that the corresponding ingress and egress flows (or a
bidirectional flow) be preconfigured at both ends.
Test Cases
The Y.1564 test supports two cases:
Internal MEP case Supported for E-Line, E-LAN, and E-Tree services over PTP
or Bridge, in which MEPs are not preconfigured
Service MEP case Full support over point-to-point and E-LAN services, where
Down or Up MEPs are preconfigured
Operation Internal MEP Case

The test traffic flow for Y.1564 tests Internal MEP case is illustrated and
explained below.
In Internal MEP case, if a service MEP does not already exist, an Up MEP is
automatically created at the generator side under the first unused MA number at
MD level 7. An ACL is also automatically created on the receive side of the
generator. The ACL forwards to the internal MEP only frames having source MAC
address equal to the configured destination MAC address.
This automatically created MEP is automatically deleted at the end of the test.
In Internal MEP case, the Y.1564 test is associated with only one of the
following options:
A single multi-CoS flow with an optional list of CoS values (default is all
CoS)
One or more single CoS flows
A service (identified by service name) with an egress port ID and an optional
list of CoS values (default is all CoS). In this case, the flows on which the
test is performed are automatically found.
If the EVC is classified by VLAN, the test is performed using P-bit value 5.
Note This P-bit value often represents high priority data.

Key=crs_mac
Generator Responder
Test
ETH Internal ETH ETH Automatic ETH
Frames
Port Up MEP ACL Port Port Block of User Port
Service Traffic
MAC Swap
Loopback
ETX-2 ETX-2
Figure 11-15. Y.1546 Test - Internal MEP Case (E-Line Services over PTP)
On all Flows to a
Bridge-port
Generator Responder
Test
ETH Internal ETH ETH Automatic ETH
Frames B
Port Up MEP ACL Port Port Block of User Port
Service Traffic
MAC Swap
Loopback
ETX-2 ETX-2
Figure 11-16. Y.1546 Test - Internal MEP Case (E-Line Services over Bridge)
Note When running the Y.1564 test in a device, without configuring the OAM (Internal
MEP case), configure the destination MAC address on the generator to the
responder NNI MAC, as per the device used.
The Y.1564 test for the Internal MEP case is performed as follows:
1. At the generator side, a unique MAC is configured.
2. At the generator side, an internal up MEP is automatically created.
3. At the generator side, the source transmits test frames at data rate
(different rates are used during different steps of the test) toward the
configured MAC.
4. DMM and LMM frames, transmitted periodically by the MEP at the generator
side, are interleaved with the test data.
5. At the responder side, the same unique MAC as used in the generator is
configured.
6. The responder loops back only frames with a destination MAC equal to the
configured MAC. If egress-port is a bridge-port, loop and ACL on all ingress
flows to a bridge-port.
7. At the generator receive side, an ACL forwards only frames whose source
MAC equals to the configured MAC.
8. When the generator receives the looped DMM and LMM frames, it
responds by sending DMR and LMR frames, respectively.
9. The responder loops back also the DMRs and LMRs.
10. Round-trip loss is measured by the sum of the LMR frame count and the
local count at the generator ingress.

11. Round-trip delay is measured by the DMR frame timestamps divided by two.
Operation Service MEP Case

Generators and responders are supported over the following:
Down MEPs for E-Line and E-LAN services:
Down MEP facing network ports
Down MEP facing PCS port
Down MEP facing EoPDH (logical MAC)
Up MEPs for E-Line and E-LAN services over bridge/ring:
Up MEP facing bridge port
Up MEP facing ETP
Up MEP facing port (E-Line up MEP)
Note If a Y.1564 test is running over an ERP or ETP, any protection switchover causes
the test to fail.
Y.1564 test is supported over E-LAN in the presence of user traffic in the
following cases:
E-LAN service is newly installed.
E-LAN service is already installed and running on E-LAN nodes, and you add
a new node to the service. In this case, you can run the non-intrusive
Y.1564 test on the new node without disrupting (blocking) the traffic on the
other nodes.
For the Service MEP case, the MA of the service MEPs used by the test, must be
manually configured. The CoS on which the test is performed can optionally be
configured with a single value or several values from 0 to 7; the default all CoS
indicates that all the preconfigured EVC.CoS will be tested. The MEPs and flows
on which the test is performed are automatically learned from the configured
MA and CoS.
Regular Y.1564 Test

The test traffic flow for regular Y.1564 tests is illustrated and explained below.
The Y.1564 testing is disruptive; user traffic is blocked on the tested EVC during
diagnostic procedure.

Generator Responder
Test
Frames Test Frames,
DMMs, LMMs
Policer
PSN
Policer
Ethernet Down Ethernet Ethernet Down Ethernet
Looped Test Frames,
Port MEP Port Port MEP Port
DMRs, LMRs
Figure 11-17. Full Y.1564 Traffic Path for EVC with Single CoS (Down MEP)
Generator Responder
Test Test
ETH Down ETH ETH Down ETH
Frames B B Frames
Port MEP Port Port MEP Port
Service Service
ETX-2 ETX-2
Figure 11-18. Full Y.1564 Traffic Path
Note The responder can be configured to inject the test frames into the policer or
bypass it.
The regular Y.1564 test is performed as follows:

1. At the generator side, the source transmits test frames at specified data
rate (different rates are used during the different steps of the test).
2. The test frames are counted by the MEP LMM counters as they exit the
generator.
3. The test frames are counted again as they enter the responder by the MEP
LMM counters.
4. At the responder, the sink either drops the test frames or loops them back
(unidirectional or bidirectional test configuration).
5. LMR frames, returned by the MEP at the responder, plus local count at the
generator ingress, provide the round-trip loss measurements (looped test
frames are also counted by the LMR counters).
6. DMM frames, transmitted periodically by the MEP at the generator side, are
interleaved with the test data. The DMR frames, returned by the MEP at the
responder side with two additional timestamps, provide the one-way and/or
round-trip delay measurements.
Y.1564 MAC Swap Loopback Test

When the responder device has limited capabilities i.e. no service MEP is defined
or the test frames cannot be identified and/or counted by the MEP, there is an

alternative form of the responder MAC swap loopback. Only bidirectional

(round-trip) measurements are supported in this case.
This test is supported over point-to-point services where MEPs are
preconfigured at the generator side and a MAC swap loopback is activated at the
responder side.
Generator Responder
Test MAC Swap

Frames Test Frames, Loopback
DMMs, LMMs, DMRs, LMRs
Policer
PSN
Policer
Ethernet Down Ethernet Ethernet Ethernet
Port MEP Port Port Port
Figure 11-19. Y.1564 Test with MAC Swap
The Y.1564 MAC swap loopback test is performed as follows:

1. At the generator side, the source transmits test frames at specified data
rate (different rates are used during different steps of the test).
2. DMM and LMM frames, transmitted periodically by the MEP at the generator
side, are interleaved with the test data.
3. The responder loops back all the frames (the test frames as well as the OAM
frames).
4. When the generator receives the looped DMM and LMM frames it responds
by sending DMR and LMR frames, respectively.
5. The responder loops back the DMRs and LMRs received from the generator.
6. Round-trip loss is measured by the sum of the LMR frame count and the
local count at the generator ingress.
7. Round-trip delay is measured by the DMR frame timestamps divided by two.
Note In the case of a MAC swap loopback responder, the DMR timestamps include the
time spent by the packet in the responder, therefore the round-trip delay
measurements are less accurate.
Y.1564 Launching Loopback Test

When Launching Loopback functionality (LLF) is enabled on a MEP, the
responder at the MEP level is used in the Y.1564 test. There is no need to define
a Y.1564 responder especially for the Y.1564 test.
The Y.1564 Launching Loopback test is performed as follows:
1. Enable the responder at MEP level.
2. A generator having profile with responder type MEF4622, sends LLMs to
responder. Some LMMs request status of LL; others request to activate or
deactivate loopback.

3. Upon receiving the LLM, the responder identifies the port, VLAN tags, and
source MAC address of the generator.
4. The Responder returns an LLR.
5. If a reply is received, the Generator sends an LL Activate Request.
Down MEP
Depending on the specific implementation, a single MEP per EVC, or a separate
MEP per single or multiple EVC.CoS is required to provision the test. In all cases,
the service is supported with regular and aggregate policer. In case of a single
MEP, the Rx flow classification can be VLAN or Outer VLAN. In case of multiple
MEPs, all the MEPs must belong to the same MA, and the Rx flow classification
can only be VLAN + p-bit.
Up MEP
For multipoint-to-multipoint (E-LAN) services, the Y.1564 testing is performed
over an Up MEP, for either a single Cos (EVC) or multi CoS (EVC) service. The
testing frames are transmitted into the bridge, and the VLAN tag value of the
test traffic is defined by the Rx flow classification. In both cases, the service is
supported with regular and aggregate policer.
Generator
Test
Frames
BP
Tx Flow
Policer
BP Bridge BP
Rx Flow
Ethernet
Up MEP SVI
Port
Figure 11-20. EVC: Single CoS and Single Up MEP
Running Test on MEP with No Configured Services

The Y.1564 profile supports the auto-cos-completion option, which enables
running the Y.1564 test on a MEP without preconfiguration of services on some
or all of the CoS p-bits of the MEP. Use of this option requires you to explicitly
configure the p-bit in the MEP on which the test is to be run.
The auto-cos-completion and p-bit options should be configured in both the
generator and responder.
Test Procedures
This section describes Y.1564 test procedures and success criteria.
Stepped CIR Test

Transmission rate is according to the configured steps in percentage of CIR. For
example, 25% of CIR, 50% of CIR, 75% of CIR and CIR.
Success criteria FLR, FTD, and FDV are within SAC limits.

Color-Blind EIR Test

Transmission rate is equal to CIR + EIR.
Success criteria 0.99 CIR (1-FLR) IR 1.01 (CIR + EIR)
Color-Blind Traffic Policing Test

Transmission rate is set as follows:
If EIR 20% of CIR, Tx rate is set to: CIR + 125% of EIR
If EIR < 20% of CIR, Tx rate is set to: 125% of CIR + EIR
Success criteria 0.99 CIR (1-FLR) IR 1.01 (CIR + EIR)
Color-Aware and Color-Blind CBS Test

Based on test case 36 in MEF 19.
Objective: To form the transmission pattern shown in the following diagram for
the duration of the test.
rate
1.1CBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-21. Transmission Pattern (CBS Test)
This can be realized by utilizing two generators:

First generator (G1) should transmit at CIR for ~200 msec, turn off for
100 msec, and start over.
Note If (8 CBS/CIR) > 90 msec, the transmission off period should be floor(9
CBS/CIR) instead of 100 msec.
Second generator (G2) should inject a burst of length 110% CBS at maximum
rate every 300 msec.
Note If (8f CBS/CIR) > 90 msec, the burst should be transmitted every floor (9
CBS/CIR) + 200 msec instead of every 300 msec.
Preparation:
Set EIR = 0 and EBS = 0 for the duration of the test.
Stop DMM transmission for the duration of the test.

Transmit LMM once at the beginning of the test (when the generators are
off) and once at the end of the test (when the generators are off).
Procedure:
G1 transmits green C frames at CIR.
C = ceiling (200 msec CIR/bitsInFrame)
where
bitsInFrame = the size of the test frame in bits
G2 transmits green B frames at maximum rate (1G or 10G).
B = ceiling (1.1 CBS/frameLength)
where
frameLength = the size of the test frame in bytes
The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
For color-aware test 0.99 number of cycles (C + N) (1-FLR) number
of green frames
For color-blind test 0.99 number of cycles (C + N) (1-FLR) total
number of frames
C = number of frames at CIR per cycle, defined above
N = number of frames in CBS w/o excess = floor (CBS/frameLength)
Where:
Color-Aware EBS Test

rate
1.1EBS
PHY
CIR
100 200 300 400 500 600 700 time [ms]
Figure 11-22. Transmission Pattern (Color-Aware EBS Test)

First generator (G1) should transmit at CIR for ~200 msec, turn off for
Note If (8 EBS/EIR) > 270 msec, the transmission off period should be floor (9
EBS/EIR) 200 msec instead of 100 msec.
Second generator (G2) should inject a burst of length 110% (EBS) at

maximum rate every 300 msec.
Note If (8 EBS/EIR) > 270 msec, the burst should be transmitted every floor(9
EBS/EIR) instead of every 300 msec.
Preparation:
Procedure:
G1 transmits green C frames at CIR.
where
bitsInFrame = test frame size in bits
G2 transmits yellow B frames at maximum rate (1G or 10G).
B = ceiling (1.1 EBS/frameLength)
where
frameLength = test frame size in bytes
The number of CIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 number of cycles C (1-FLR) total number of frames
Color-Blind EBS Test


rate
1.1(CBS+EBS)
PHY
CIR+EIR
100 200 300 400 500 600 700 time [ms]
Figure 11-23. Transmission Pattern (Color-Blind EBS Test)

First generator (G1) should transmit at CIR+EIR for ~200 msec, turn off for
Note T = max(CBS/CIR, EBS/EIR); If (8 T) > 90 msec, the transmission off period

should be floor(9 T) instead of 100 msec.
Second generator (G2) should inject a burst of length 110% (CBS+EBS) at

maximum rate every 300 msec.
Note T = max(CBS/CIR, EBS/EIR); If (8 T) > 90 msec, the burst is transmitted every

floor(9 T) + 200 msec instead of every 300 msec.
Preparation:
Procedure:
G1 transmits E frames at (CIR+EIR).
E = ceiling (200 msec (CIR+EIR)/bitsInFrame)
where
bitsInFrame = test frame size in bits
G2 transmits B frames at maximum rate (1G or 10G).
B = ceiling (1.1 (CBS+EBS)/frameLength)
where
frameLength = test frame size in bytes
The number of EIR/burst cycles actually performed during the test, are
counted.
Success criteria:
0.99 number of cycles (C + N) (1-FLR) total number of frames


Where:
Performance Test
Transmission rate is equal to CIR.
Success criteria FLR, FTD, FDV, and Availability are within SAC limits.
Configuring Y.1564 Test

Y.1564 test configuration procedure includes the following steps, detailed in this
section:
1. Add and configure a Y.1564 test profile in the generator and responder
devices.
2. Add, configure, and activate a Y.1564 test responder.
3. Add, configure, and activate a Y.1564 test generator.
Note For the Y.1564 test Service MEP case, in devices with OAM MEP configured
with MEF46 Latching Loopback, there is no need to add a Y.1564 responder.
Adding Y.1564 Test Profile

You can define up to 16 Y.1564 test profiles to be applied to generator and
responder to ensure the desired test functionality.
The test profiles are defined at the EVC level, and can also contain profiles at
the EVC.Cos (P-bit) level with frame size and threshold definitions. Any EVC.Cos
configuration overrides the EVC configuration. This enables the definition of
different frame sizes and thresholds according to P-bit.
Note The DMM frame size in the Y.1564 test is set according to the frame size
configured for the test profile, rather than according to the dest NE
data-tlv-length configuration.
To add and configure a Y.1564 test profile:

1. Navigate to config>test>y1564.
2. Define a Y.1564 test profile and assign a name to it: profile <profile-name>
The system switches to the context of the profile
(config>test>y1564>profile<profile-name>).
Note no profile <profile-name> deletes the Y.1564 test profile.

Specifying whether OAM CFM auto-cos-completion Use of auto-cos-completion

services should be automatically no auto-cos-completion requires you to explicitly
created for tested p-bit values configure the p-bit command
for the test (see parameter
description below).
Specifying whether to include or burst-tests [cbs] [ebs] You can enter the command
exclude the CBS and EBS sub- with one or both parameters.
tests (burst tests) in the To specify not to include any
configuration phase burst tests in the configuration
phase, enter: no burst-tests.
Setting the number of steps and cir-steps s1 <s1-percent> <s1-percent> transmission

their transmission rate in the CIR [s2 <s2-percent>] [s3 <s3-percent>] rate, as percentage of CIR, at
subtest [s4 <s4-percent>] the first step of the CIR subtest
(1100)
rate, as percentage of CIR, at
the second step of the CIR
subtest (1100)
the third step of the CIR
subtest (1100)
the fourth step of the CIR
subtest (1100)
Note: You can define fewer
than four steps as long as the
last step is 100%.
Setting the color mode used for color-aware

the test no color-aware
Defining the duration of the configuration-duration <seconds> Possible values: 18360

configuration test for each P-bit seconds
Setting the direction in which direction {unidirectional | Default: bidirectional

the test is performed bidirectional}
Defining Ethertype of the test ethernet-type <hex-number>

frames
Defining test frame size frame-size {64 | 128 | 256 | 512 | Range for custom bytes:
1024 | 1280 | 1518 | custom <bytes>}
642000

Setting the source MAC address multiple-sa-mac The source MAC addresses of
in test frames multiple-sa-mac base generated test frames are
<first-mac-address> cyclically selected from a block
of 32 consecutive MAC
no multiple-sa-mac
addresses beginning at default
address 0x0020D2000100 or
at configured base address.
base - the start of a block of
MACs to be used as the source
address in test frames.
Must be a multiple of 32.
Example: multiple-sa-mac base
0x000012345600
Setting the one-way service one-way-thresholds flr <ppm> ftd flr unidirectional Frame Loss
acceptance criteria <s> fdv <s> availability Ratio, measured in 1E-6 units
<percent/100> ftd unidirectional Frame
Transfer Delay, measured in
microseconds
fdv unidirectional Frame
Delay Variation, measured in
microseconds
availability unidirectional
availability, measured in
hundredths of percent units
order to define 89.3%)
Creating, modifying, or deleting p-bit <0..7> The P-bit test profile allows
a Y.1564 test P-bit profile configuring separate frame
sizes and thresholds for
specific P-bits. The rest of the
P-bits are tested using the
general profile.
See P-bit configuration details
below.
Type no p-bit <0..7> to delete
a specific test P-bit profile.
Defining the duration of the performance-duration minutes Possible values: 17200

performance test, in minutes minutes

Defining the convention of the rate-convention <data-rate | The convention of the rate
rate measurements in the line-rate> measurements section in the
Y.1564 test report Y.1564 test report is
determined by the option that
you select:
data rate section title is IR
[Mbps].
line rate section title is
ULR [Mbps].
Note: Configuring
rate-convention only changes
the title in the generated
Y.1564 test report according to
your selection (IR for data-rate;
ULR for line-rate). It does not
change the values of the
measurements in the report.
Therefore, after changing
rate-convention in the profile,
you must run the Y.1564 test
again to display the
measurements in the newly
selected rate-convention.
Defining the type of responder responder-type {y1564 | mac-swap | See Operation section.
that receives the test and OAM mef46-ll}
frames from the generator in
the Y.1564 test: regular
responder, MEF46 Latching
Loopback responder, or MAC
swap responder.
Setting the round-trip service round-trip-thresholds flr <ppm> ftd flr bidirectional Frame Loss
acceptance criteria <s> fdv <s> availability <availability> Ratio, measured in 1E-6 units
ftd bidirectional Frame
microseconds
fdv bidirectional Frame Delay
Variation, measured in
microseconds
availability bidirectional
Setting the scope of the test: scope [configuration] [performance] You can enter the command
configuration test, performance with one or both parameters
test, or both To specify with no scope
parameters, enter: no scope

Specifying whether to apply traffic-policing This command affects the

traffic policing no traffic-policing following, according to which
side:
Generator side including
or excluding the traffic
policing subtest from the
configuration phase
Responder side passing or
not passing the data
through the responder
policer
Specifying whether user traffic is user-traffic-blocked

to be blocked/allowed during the no user-traffic-blocked
test
The following P-bit test profile parameters can be configured at the p-bit level in
the config>test>y1564>profile(profile-name)>p-bit<value># prompt.
Defining test frame size frame-size {64 | 128 | 256 | 512 | Range for custom bytes:
1024 | 1280 | 1518 | custom <bytes>}
642000
Setting the one-way service one-way-thresholds flr <ppm> ftd flr service acceptance criteria
acceptance criteria <s> fdv <s> availability <availability> for unidirectional Frame Loss
Ratio, measured in 1E-6 units
ftd service acceptance
criteria for unidirectional Frame
microseconds
fdv service acceptance
criteria for unidirectional Frame
microseconds
availability service acceptance
criteria for unidirectional

Setting the round-trip service round-trip-thresholds flr <ppm> ftd flr service acceptance criteria
acceptance criteria <s> fdv <s> availability <availability> for bidirectional Frame Loss
Ratio, measured in 1E-6 units
ftd service acceptance
criteria for bidirectional Frame
microseconds
fdv service acceptance
criteria for bidirectional Frame
microseconds
availability service acceptance
criteria for bidirectional
Adding Y.1564 Responder
Note For the Y.1564 test - Service MEP case, in devices with OAM MEP configured with
MEF46 Latching Loopback, there is no need to add a Y.1564 responder.
You can define up to 20 Y.1564 test responders for ETX2i and ETX-2i-B, when
each OAM MA includes eight services (p-bits). These 20 responders can be all
EVC, all EVC.CoS, or any combination of EVCs and EVC.CoSs. All the responders
can be activated simultaneously.
To add and configure Y.1564 responder:

2. Define a Y.1564 test responder and assign a name to it:
responder<responder-name>
The system switches to the context of the responder
(config>test>y1564>responder<responder-name>).
Note no responder <responder-name> deletes the Y.1564 responder.
Activating or deactivating the activate

test at the responder side no activate

Defining the service to be tested bind <md <id> ma <id> [p-bit <0..7>] md the maintenance domain
no bind <md <id> ma <id> to which the service belongs
(165535)
ma the maintenance
association to which the
service belongs (165535)
p-bit the specific P-bits to be
tested, or all preconfigured
P-bits if none are specified
no bind md <id> ma <id>
removes responder association
with the service.
When enabling
auto-cos-completion, it is
mandatory to explicitly
configure the normally optional
p-bit command.
Defining the service to be tested bind flow <flow-name> Mutual exclusion with the other
no bind flow <flow-name> bind formats.
flow the multi-CoS flow that
carries the service OR a single-
CoS flow that is part of the
service.
Possible values: Variable length
string, up to 32 characters.
A corresponding flow must
already exist in the RAD flow
table.
no bind removes responder
association with the service.
Defining the service to be tested bind service <service-name> Mutual exclusion with the other
{ethernet} <port-index> bind formats
bind service <service-name> {lag | pcs service the name of the
| logical-mac | svi} <port-number> tested service. A flow
bind service <service-name> corresponding to service name,
bridge-port <bridge-number> port must already exist in the
<port-number> RAD flow table.
bind service <service-name> Possible values: Variable length

etp <etp-name> string, up to 32 characters
{subscriber|transport} <port- ethernet, lag, pcs, logical-mac,
number> svi, bridge-port, etp subscriber,
no bind service <service-name> etp transport the port over
which the service is tested
no bind removes responder

Setting the local MAC address local-mac mac <mac-address> Note: Command available only
used for the multipoint test no local-mac when responder is bound to a
flow.
mac the MAC address that
the responder uses for E-LAN
and E-Tree tests
Default value: 0x000000
Setting the destination MAC destination mac <mac-address> mac a configurable MAC
address or remote MEP number destination remote-mep <rmep-id> address that identifies the
generator side
Note: When there is more than
one generator on a certain
E-LAN service, each generator
has a unique remote MAC.
remote-mep identifier of a
remote MEP at the generator
side, towards which the test is
conducted.
Note: You can disassociate the
destination remote MEP from
the responder by entering
destination remote-mep 0 (and
not no destination).
Assigning a test profile to the test-profile <profile-name>

responder
Displaying the Y.1564 test show status See Viewing Test Status
status (Responder Side)
Viewing Test Status (Responder Side)
To display the test status (responder side):

In the config>test>y1564>responder<responder-name># prompt, enter
show status.
see Table 11-23.
ETX-2i>config>test>y1564>responder(1)# show status
MEP Service P-BIT

21 1 1
22 1 3
23 1 5

Table 11-23. Y.1564 Test Status (Responder Side)
Status Current status of the test (responder):

Idle Test has been configured and has not yet been run.
Ready Test is ready to run.
In progress Test is currently running.
MEP Identifier of the MEP that is associated with the responder and
specific P-bit
Service Identifier of the service that is associated with the responder and
specific P-bit
Possible values: 18 or
P-BIT P-bit that is included in the tested service

Possible values: 07
Adding Y.1564 Generator

You can define up to eight Y.1564 test generators, each with up to eight p-bits.
These eight generators can be all EVC, all EVC.CoS, or any combination of EVCs
and EVC.CoSs. All the generators can be activated simultaneously. You can
activate generators on up to eight p-bits simultaneously (a p-bit is equivalent to
an OAM MEP service).
To add and configure Y.1564 generator:

2. Define a Y.1564 test generator and assign a name to it:
generator<generator-name>
The system switches to the context of the generator
(config>test>y1564>generator<generator-name>).
Note no generator<generator-name> deletes the Y.1564 generator.
Activating or deactivating the activate

test at the generator side no activate

Defining the service to be tested bind md <id> ma <id> [p-bit <0..7>] md maintenance domain to
no bind md <id> ma <id> which the service belongs (1
65535)
ma maintenance association
to which the service belongs
(165535)
p-bit specific P-bits to be
no bind md <id> ma <id>
removes generator association
with the service.
When enabling
auto-cos-completion, it is
mandatory to explicitly
configure the normally optional
p-bit command.
Defining the service to be tested bind flow <flow-name> [multi-cos] Mutual exclusion with the other
[p-bit <0..7>] bind formats; if the optional
no bind flow <flow-name> multi-cos attribute does not
exist, several bind commands
with different flow names can
be configured.
flow the multi-CoS flow that
carries the service OR a single-
CoS flow that is part of the
service. A corresponding flow
must already exist in the RAD
flow table.
Possible values: Variable length
string, up to 32 characters
multi-cos indicates that the
specified flow name is a
multi-CoS flow
p-bit specific P-bits to be
Valid only together with the
optional multi-cos attribute.
For each specified P-bit, a
corresponding CoS (rank) must
already exist in the envelope
policer of the multi-CoS flow.
no bind removes generator

Defining the service to be tested bind service <service-name> Mutual exclusion with the other
{ethernet} <port-index> bind formats
[p-bit [<0..7>]] service the name of the
bind service <service-name> {lag | pcs tested service. A flow
| logical-mac | svi} <port-number> corresponding to service name,
[p-bit [<0..7>]] port must already exist in the
bind service <service-name> RAD flow table.
bridge-port <bridge-number> Possible values: Variable length
<port-number> [p-bit [<0..7>]] string, up to 32 characters
bind service <service-name> ethernet, lag, pcs, logical-mac,
etp <etp-name> {subscriber|transport} svi, bridge-port, etp subscriber,
<port-number> [p-bit <p-bit>] etp transport the port over
no bind service <service-name> which the service is tested
p-bit the specific P-bits to be
P-bits if none are specified.
For each specified P-bit, a
corresponding flow must
already exist in the RAD flow
table.
no bind removes generator
Setting the destination MAC destination mac <mac-address> mac a configurable MAC
address or remote MEP number destination remote-mep <rmep-id> address that identifies the
responder side
Note: When there is more than
one responder on a certain E-
LAN service, each reponder has
a unique remote MAC.
remote-mep identifier of a
remote MEP at the responder
side, towards which the test is
conducted
Note: Destination remote MEP
can be disassociated from the
generator by entering
destination remote-mep 0 (and
not no destination).

Assigning policer to test policer <p-bit> bandwidth If a policer is defined for the
[cir <cir-value>] [cbs <cbs-value>] test, then the test is
[eir <eir-value>] [ebs <ebs-value>] performed according to the
[compensation <compensation-value>] test policer, rather than
policer <p-bit> profile according to the associated
<policer-profile-name> flow policer.
p-bit CoS to which the
configuration applies
Possible values: 0..7
cir committed information
rate
cbs committed burst size
eir excessive information rate
ebs excessive burst size
compensation extra bytes
added to frame size to take
into account Layer-1 overhead
(preamble and IFG) in the
network and the overhead for
the added VLAN header.
Possible values: 0..63
profile an optional
predefined policer profile to be
used in the test
Note: The option to define a
test policer is useful if there is
no flow policer, or the flow
policer has different limits than
you wish to use for the test.
Assigning a test profile to the test-profile <profile-name>

generator
Displaying the status of the show mef46-ll-status See Viewing MEF46 Latching
MEF46 Latching Loopback Loopback Generator Status..
generator
Displaying the Y.1564 test show status See Viewing Test Status
status (Generator Side).
Displaying the test results and show report <summary | detailed> See Viewing Test Results.
measurements
Viewing MEF46 Latching Loopback Generator Status
To display the MEF46 LL generator status:

In the config>test>y1564>generator<generator-name># prompt, enter show
mef46-ll-status.

see Table 11-25.
ETX2i>config>test>y1564>generator(1)# show mef46-ll-status
Tx LLMs : 3
Rx LLRs : 3
Rx Autonomous LLRs : 0
Last Received LLR

---------------------------------------------------------------
--------------
Flags : Status : Inactive Direction :
NA Unrecognized TLV : No
Response Code : No Error
ETX2i >config>test>y1564>generator(1)#
Table 11-24. MEF46 Latching Loopback Generator Status
Displayed
Tx LLMs Number of LLM PDUs sent by the LL controller
Rx LLRs Number of LLR PDUs received by the LL controller
Rx Autonomous LLRs Number of autonomous LLR PDUs received by the LL controller
Status Latching Loopback status:

Possible values: Inactive, Active
Direction Latching Loopback direction:

Possible values: NA, Internal, External
Unrecognized TLV Indicates whether one or more of the included TLVs were not
recognized
Possible values: No, Yes
Response Code Response code in the last received LLR PDU

Possible values: No Error, Malformed Request, Max Session
Exceeded, Resource Unavailable, Already Active, Already Inactive,
Unsupported, Wrong MP, Timeout, Prohibited, Unknown
Message Type, Unknown Error
Viewing Test Status (Generator Side)
To display the test status (generator side):

status.
see Table 11-25.
ETX-2i>config>test>y1564>generator(1)# show status
Time Remaining : 00:00:24

Test Phase : Performance
Associated EVC
---------------------------------------------------------------
Inner VLAN : --- Outer VLAN : 20
MEP Service P-BIT Tx Flow Rx Flow

---------------------------------------------------------------
1 2 1 flow2_3to1
flow2_1to3
MEP Service P-BITCIR EIR BWP In Use

(Mbps) (Mbps)
---------------------------------------------------------------
--------------
1 2 1 37.5 75.0 Flow
Table 11-25. Y.1564 Test Status (Generator Side)
Displayed
Status Current Test status (generator):

Idle Test has been configured and has not yet been run.
In Progress Test is currently running.
Passed Test has been completed successfully.
Failed Test has failed.
User Aborted Test has been stopped by the operator.
Time Remaining Time remaining until the end of the test

Displayed when Status is In Progress
Test Phase Current phase of the test

Possible values: Configuration, Performance
Displayed when Status is In Progress
Inner VLAN Value of the inner VLAN (usually C-Tag)

If there is no inner tag, the string is displayed.
Displayed when Status is other than Idle
Outer VLAN Value of the outer VLAN (usually S-Tag)

If there is no outer tag, the string is displayed.
Displayed when Status is other than Idle.
MEP Identifier of the MEP that is associated with the P-bit


Displayed
Service Identifier of the service that is associated with the P-bit

Possible values: 18 or
Displayed when Status is other than Idle.
P-BIT P-bit that corresponds to the tested service

Displayed when Status is other than Idle and when EVC is untagged
Tx Flow Egress flow corresponding to the MEP and P-bit

Rx Flow Ingress flow corresponding to the MEP and P-bit

CIR (Mbps) Provisioned CIR of the egress flow

EIR (Mbps) Provisioned EIR of the egress flow

BWP in use Origin of the associated bandwidth profile for the EVc.CoS
Possible values: Test, Flow
Viewing Test Results

When displaying the Y.1564 test results, you can choose to generate a test
summary or a detailed test report.
Note In detailed test report, in case a step is Not Applicable, all step parameters
display value --- and not 0.
To display the summary test results:

report summary.
The summary report screen is displayed. For information on the test
report summary counters, see the following table.
ETX-220A>config>test>y1564>generator(1)# show report summary
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-20-D2-54-11-92
Source MAC Address : 00-20-d2-f1-d1-66
Inner Tag : --- Outer Tag : 1
P-bit/s : 0
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance
Profile Name : 1

Start Date & Time : 2016-07-24 13:04:44

End Date & Time : 2016-07-24 13:05:05
Total Duration : 00:00:21
Configuration Test Report

-----------------------------------------------------------------------------
P-bit : 0
Duration (Sec) : 20
Result : Failed CIR,EIR,Policing
Test Result Tx Rate IR FLR FTD FDV

(Mbps) (Mbps) (ms)
(ms)
CIR Test
-----------------------------------------------------------------------------
Step#1 Failed FLR 25.0 0.0 1.0E+00 0.004 0.0
Step#2 Failed FLR 50.0 0.0 1.0E+00 0.004 0.0
Step#3 Failed FLR 75.0 0.0 1.0E+00 0.004 0.0
Step#4 Failed FLR 100.0 0.0 1.0E+00 0.004 0.0
EIR Test
-----------------------------------------------------------------------------
Failed IR 101.0 0.0 1.0E+00 0.004 0.0
Traffic Policing Test

-----------------------------------------------------------------------------
Failed IR 126.0 0.0 0.0E+00 0.0 0.0
CBS Test
-----------------------------------------------------------------------------
Passed
EBS Test
-----------------------------------------------------------------------------
Passed
Performance Test Report

-----------------------------------------------------------------------------
Duration (Min) : 1
Result : Failed P-bit/s 0
P-bit Result Tx Rate

-----------------------------------------------------------------------------
0 Failed IR,Avail. 100.0
IR (Mbps)
-----------------------------------------------------------------------------
P-bit IR FLR FTD FDV Avail
(ms) (ms) (%)
-----------------------------------------------------------------------------
0 0.0 0.0E+00 0.0 0.0 1.66

Table 11-26. Y.1564 Header and Test Counters (Summary)
Counter Description
Name Name of the tested service
Destination MAC Address MAC address of the remote MEP
Source MAC Address MAC address of the local MEP
Inner Tag Value of the inner VLAN
Outer Tag Value of the outer VLAN
P-bit/s List of the P-bit values that were actually tested
Scope Scope of the test: configuration test, performance test, or both

phases
Possible values: Configuration, Performance, Configuration +
Performance
Profile Name Profile used in the test
Start Date & Time Date and time at the last test activation
End Date & Time Date and time when the last test ended (regardless of the end
result passed/failed/aborted)
Total Duration Duration of the last test
Overall Result Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Configuration Test report (summary)
P-bit
Duration Duration of the configuration test (in seconds)
Result Result of the last configuration test for the specific P-bit and if it
failed, the reason for failure
Possible Result values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Possible reasons for failure: CIR, EIR, Policing, and/or CBS test
Test Name of the sub-test: CIR Test, EIR Test, Traffic Policing Test, CBS
Test, EBS Test
Result Result of the sub-test

Possible Result values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Reason for failure If sub-test failed, shows the reason(s) for failure.
Possible reasons for failure:
CIR Test FLR, FTD, or FDV
EIR Test IR
Traffic Policing Test IR
CBS Test Burst size
EBS Test Burst size

Counter Description
Tx Rate (Mbps) Transmission rate to which the generator is configured in the

subtest
IR (Mbps) Average calculated Information Rate
FLR Calculated Frame Loss Ratio
FTD (ms) Average calculated Frame Transfer Delay
FDV (ms) Average calculated Frame Delay Variation
Performance test report (summary)
Duration Duration of the performance test (in minutes)
Result Performance test result summary for all CoS (p-bits)

Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
If test failed, displays the failed CoS (p-bit(s))
P-bit P-bit (sub-test) that is included in the tested service
Result Result of the sub-test for the CoS (p-bit)

Possible values: Not Applicable, Passed, Failed, User Aborted,
System Aborted
Reason for failure If sub-test failed, displays the reason for failure: FLR, FTD, or FDV
Tx Rate (Mbps) Transmission rate to which the generator is configured in the

subtest
IR (Mbps) Average calculated Information Rate
FLR Calculated Frame Loss Ratio
FTD (ms) Average calculated Frame Transfer Delay
FDV (ms) Average calculated Frame Delay Variation
Avail (%) Percentage of available time
To display the detailed test results:

report detailed.
The detailed report screen is displayed. For information on the detailed
test report counters, see Table 11-5.
ETX-2i>config>test>y1564>generator(1)# show report detailed
Services
-----------------------------------------------------------------------------
Destination MAC Address : 00-20-D2-50-95-A3
Source MAC Address : 00-20-D2-54-EF-EB
Inner Tag : --- Outer Tag : 20
P-bit/s : 1
Summary
-----------------------------------------------------------------------------
Scope : Configuration+Performance

Profile Name : 1
Start Date & Time : 2017-05-21 13:04:44
End Date & Time : 2017-05-21 13:05:05
Total Duration : 00:00:21
Configuration Test Report

-----------------------------------------------------------------------------
P-bit : 0
Duration (Sec) : 20
Result : Failed CIR,EIR,Policing
CIR Test
-----------------------------------------------------------------------------
---------------- -------- -------- -------- -------- ----
Tx Rate (Mbps) 25.0 --- 75.0 100.0
IR - Min (Mbps) 0.0 --- 0.0 0.0
IR - Mean (Mbps) 0.0 --- 0.0 0.0
IR - Max (Mbps) 0.0 --- 0.0 0.0
Tx Count 6101 --- 18301 24391
Rx Count 0 --- 0 0
FL Count 6101 --- 18301 24391
FLR 1.0E+00 --- 1.0E+00 1.0E+00 3.0E-04
FTD - Min (ms) 0.004 --- 0.004 0.004
FTD - Mean (ms) 0.004 --- 0.004 0.004 26.000
FTD - Max (ms) 0.004 --- 0.004 0.004
FTD - Std (ms) 0.0 --- 0.0 0.0
FDV - Mean (ms) 0.0 --- 0.0 0.0 11.000
FDV - Max (ms) 0.0 --- 0.0 0.0
---------------- -------- -------- -------- -------- ----
Result Failed Not Applicable Failed Failed
EIR Test & Traffic Policing Test
-----------------------------------------------------------------------------
EIR Policing Thr
---------------- -------- -------- --------
Tx Rate (Mbps) 101.0 126.0
IR - Min (Mbps) 0.0 0.0
IR - Mean (Mbps) 0.0 0.0 0.0 - 10.128
IR - Max (Mbps) 0.0 0.0
Tx Count 24633 0
Rx Count 0 0
FL Count 24633 0
FLR 1.0E+00 0.0E+00
FTD - Min (ms) 0.004 0.0
FTD - Mean (ms) 0.004 0.0
FTD - Max (ms) 0.004 0.0
FTD - Std (ms) 0.0 0.0
FDV - Mean (ms) 0.0 0.0
FDV - Max (ms) 0.0 0.0
---------------- -------- -------- --------
Result Failed Failed
Burst Tests
-----------------------------------------------------------------------------
Parameter CBS EBS
--------------------------------- -------- --------
Number of Cycles 24 24
Frames per Cycle 70 140
Minimum Expected Frames 105881 105730
Actual Received Frames 106733 159260
--------------------------------- -------- --------
Result Passed Passed

Performance Test Report

-----------------------------------------------------------------------------
Duration (Min) : 1
Result : Failed P-bit/s 0
P-bit Result Tx Rate

-----------------------------------------------------------------------------
0 Failed IR,Avail. 100.0
IR (Mbps)
-----------------------------------------------------------------------------
P-bit Min Mean Max
-----------------------------------------------------------------------------
0 0.0 0.0 0.0
FL
-----------------------------------------------------------------------------
P-bit Count FLR Thr
-----------------------------------------------------------------------------
0 0 0.0E+00 3.0E-04
FTD (ms)
-----------------------------------------------------------------------------
P-bit Min Max Std Mean Thr
(ms) (ms) (ms) (ms)
-----------------------------------------------------------------------------
0 0.0 0.0 0.0 0.0 26.000
FDV (ms)
-----------------------------------------------------------------------------
P-bit Max Mean Thr
(ms) (ms)
-----------------------------------------------------------------------------
0 0.0 0.0 11.000
Availability
-----------------------------------------------------------------------------
P-bit UAS % Thr (%)
-----------------------------------------------------------------------------
0 59 1.66 99.90
Table 11-27. Y.1564 Test Counters (Detailed)
Counter Description
Tx Rate (Mbps) The transmission rate to which the generator is configured in the
subtest
IR Min (Mbps) The minimum measured Information Rate
IR Mean (Mbps) The average calculated Information Rate

Note: For EIR and Traffic Policing tests, displays under Thr column,
the service acceptance criteria (SAC).
IR Max (Mbps) The maximum measured Information Rate
Tx Count Number of transmitted frames
Rx Count Number of received frames
FL Count The number of lost frames
FLR The calculated Frame Loss Ratio

Counter Description
FTD Min (ms) The minimum measured Frame Transfer Delay
FTD Mean (ms) The average calculated Frame Transfer Delay
FTD Max (ms) The maximum measured Frame Transfer Delay
FTD Std (ms) The calculated standard deviation of the Frame Transfer Delay
FDV Mean (ms) The average calculated Frame Delay Variation
FDV Max (ms) The maximum calculated Frame Delay Variation
UAS The number of unavailable seconds
% The percentage of available time
Availability Thr The Availability service acceptance criteria for the reported P-bit
Burst Tests
Number of Cycles The number of burst transmission cycles
Frames per Cycle The number of frames in a single burst transmission cycle
Minimum The minimum total number of frames expected to be received in the

Expected Frames sub-test
Actual Received The actual total number of frames received during the sub-test
Frames
Examples
This example shows how to create a Y.1564 test generator over a MEP located
between two Ethernet ports and bound to one of them. The Y.1564 test
(Service MEP case) is run over an OAM (CFM) service defined on P-bit 0. The test
in this example is run on a network port, but Y.1564 tests can also be run on
user ports.
To configure Y.1564 test generator over a MEP:

1. Configure a policer profile.
2. Configure a VLAN-type classifier profile.
3. Configure two flows from Ethernet port 0/1 to port 0/4 and vice versa.
4. Define a MEP bound to port 1.
5. Configure MEP service with LMMs and DMMs sent over P-bit 0.
6. Configure a Y.1564 test profile.
7. Add a Y.1564 generator, bind it to the relevant MD, MA, P-bit, and test
profile.

Generator
Test
Frames
Flow 1 P-bit 0
Policer
Flow 2
Ethernet MEP Ethernet

Port 1 Port 4
Figure 11-24. Y.1564 Test Generator over Down MEP
************************Defining_Policer_Profile*****************************
exit all
config qos policer-profile v10 bandwidth cir 100000 cbs 10000 eir 10000 ebs
5000
#*********************************End****************************************
************************Defining_Classifier_Profile**************************
config flows classifier-profile vlan10 match-any
match vlan 10
exit all
#*********************************End****************************************
******************************Adding_Flows***********************************
configure flows flow v10_1to4
classifier vlan10
no policer
no shutdown
exit all
configure flows flow v10_4to1

classifier vlan10
policer profile v10
no shutdown
exit all
#*********************************End****************************************
ff
#**************************Defining_MEP_and_MEP_Service**********************
configure oam cfm
ccm-interval 1s
mep 1
flow uni-direction rx v10_1to4 tx v10_4to1
bind ethernet 0/1
remote-mep 2

dest-addr-type ccm multicast

client-md-level 6
ais
no shutdown
service 1
lmm-interval 100ms
dmm-interval 100ms
dest-ne 1
remote mep 2
loss single-ended
delay two-way
exit
no shutdown
exit all
#*********************************End****************************************
#*******************Configuring_Y.1564_Test_Profile_and_Generator************
config test y1564
profile 1
ethernet-type 0x22e8
frame-size 512
one-way-thresholds flr 100 ftd 13000 fdv 8000 availability 9990
round-trip-thresholds flr 200 ftd 26000 fdv 11000 availability 9990
direction bidirectional
color-blind
traffic-policing
cir-steps s1 25 s2 50 s3 75 s4 100
configuration-duration 60
rate-convention data-rate
exit
generator 1
test-profile 1
bind md 1 ma 1 p-bit 0
activate
exit all
save
#*********************************End****************************************
The following example shows the configuration of the Y.1564 test (Service MEP
case) over E-LAN service. Note that the node in the target device must be
explicitly configured with the remote MEP number.
To run the Y.1564 test on an E-LAN service:

generator "1"
test-profile "1"
bind md 1 ma 1
destination remote-mep 1
responder "1"
test-profile "1"

bind md 1 ma 1
destination remote-mep 1
The following example shows the configuration of both the generator and
responder when the Y.1564 test is run in a device without configuring the OAM
(Internal MEP case). In this case, both generator and responder are bound to a
flow (and not to an MA or MD). Also, the destination MAC address on the
generator is configured to the responder NNI MAC.
#generator :
configure
qos
policer-profile "CIR10M-EIR20M"
bandwidth cir 9984 cbs 64000 eir 19968 ebs
64000
exit
exit
flows
match vlan 100
exit
classifier-profile "v1502-p3" match-any
match vlan 1502 p-bit 3
exit
flow "gd-dn"
classifier "v1502-p3"
no policer
vlan-tag pop vlan
no shutdown
exit
flow "gd-up"
classifier "v100"
policer profile "CIR10M-EIR20M"
no shutdown
exit
exit
exit
configure
test
echo "Configure Y1564"
# Configure Y1564
y1564
echo "Y1564 - Profile Configuration"
# Y1564 - Profile Configuration
profile "2"
exit
echo "Y1564 - Generator Configuration"
# Y1564 - Generator Configuration
generator "Generator1"
test-profile "2"
bind flow "gd-up"

Destination 00-20-D2-EE-1B-B7
exit
exit
exit
exit
#responder
configure
qos
policer-profile "CIR10M-EIR20M"
bandwidth cir 9984 cbs 64000 eir 19968 ebs
64000
exit
exit
flows
match vlan 100
exit
classifier-profile "v1502-p3" match-any
match vlan 1502 p-bit 3
exit
flow "gd-dn"
classifier "v1502-p3"
no policer
vlan-tag pop vlan
no shutdown
exit
flow "gd-up"
classifier "v100"
policer profile "CIR10M-EIR20M"
no shutdown
exit
exit
exit
configure
test
echo "Configure Y1564"
# Configure Y1564
y1564
echo "Y1564 - Profile Configuration"
# Y1564 - Profile Configuration
profile "2"
exit
echo "Y1564 - Responder Configuration"
# Y1564 - Responder Configuration
responder "Responder1"
test-profile "2"
bind flow "gd-up"
exit
exit

exit
The following example shows the configuration of the policer under the Y.1564
generator.
To configure the policer under the Y.1564 generator:

ETX2i>config>test>y1564>generator(1)$ policer 5 bandwidth cir
10000 cbs 32767 eir 5000 ebs 32767 compensation 20
Table 11-28 lists the messages generated by ETX-2i when a configuration error
is detected.
Message Description
Illegal frame size value Invalid test frame size for Y.1564 profile
Unidirectional measurement is not Only bidirectional measurement is supported.

supported
Illegal threshold value Invalid round-trip service acceptance criteria for Y.1564 profile
Illegal color value Invalid color mode for Y.1564 profile
Illegal traffic policing value Invalid traffic policer for Y.1564 profile
Illegal CIR step value Invalid CIR step for Y.1564 profile
Illegal configuration duration value Invalid duration of the configuration test for Y.1564 profile
Illegal performance duration value Invalid duration of the performance test for Y.1564 profile
Illegal rate convention value Invalid rate measurement convention for Y.1564 profile
Illegal P-bit value Invalid P-bit value for Y.1564 profile or generator
MD does not exist Maintenance domain selected for Y.1564 generator or

responder has not been configured yet.
MA does not exist Maintenance association selected for Y.1564 generator or

responder has not been configured yet.
Y.1564 profile does not exist (SNMP only) The configured Y.1564 test profile does not exist.
Illegal command value Invalid value for the parameter
Max number of active generators has The maximum number of Y.1564 generators (eight) has been
been exceeded reached and no additional generators can be added.
Max number of active responders has The maximum number of Y.1564 responders (20) has been
been exceeded reached and no additional responders can be added.
Y.1564 profile is in use Y.1564 profile is in use and cannot be modified.
Y.1564 profile has not been attached No Y.1564 profile has been attached to generator or responder.
Active generator cannot be changed Active Y.1564 generators cannot be modified.
Active responder cannot be changed Active Y.1564 responders cannot be modified.

Message Description
MEP or service have not been found MEP or OAM service within selected MD/MA does not exist.
MEPs have different destination MAC Y.1564 Generator works opposite one remote only. In EVC.cos,
address the MEPs under the MA are opposite several remotes, and
therefore the test does not work.
The device didn't learn the remote's No CCM was received from the remote MEP and its MAC address
mac-address. was not learned. This is relevant only if remote-mep is
configured on the DestNE.
MEPs have different source MAC All MEPs under the same MA must be bound to the same port.
addresses
MEPs have different classification types MEPs within selected MD/MA have different classification types.
MEPs have different VLANs MEPs within selected MD/MA have different VLANs.
MEPs have different inner VLANs MEPs within selected MD/MA have different inner VLANs.
MEP or service are not active MEP or OAM service within selected MD/MA has not been
activated yet.
OAM CFM: Max number of remote MEP The maximum number of remote MEP elements in a line has
elements in a line has been exceeded. been reached and no additional MEP elements can be added.
OAM CFM: Max allowed number of Adding MEPs to previously configured MEPs exceeds the allowed
<512/1024> remote MEPs has been maximum number of remote MEP elements that can be
reached. configured (512/1024).
Policer profile is missing No Policer is configured on the relevant Tx flow.
I/O flow with matching CoS has not been The Y.1564 test mechanism failed to identify a MEP Tx flow with a
found P-bit, matching testing criteria.
Generator can test only one P-bit If there is only one Tx flow with the non-envelope Policer, only
one P-bit can be tested.
MEP is already under test A test is already running on this MEP.
11.10 Port Mirroring

You can monitor and diagnose network traffic passing through ports using port
mirroring. Port mirroring duplicates port traffic from one or more source ports to
a single destination port, where a traffic analyzer receives, records, and
analyzes the traffic.
ETX-2i supports both inbound Tx mirroring of port ingress traffic and outbound
Rx mirroring of port egress traffic.
Applicable Products
ETX-2i Port Mirroring 11-209

Standards
N/A
Benefits
Port mirroring enables recording and analyzing inbound and outbound port
traffic, without disrupting traffic. Port mirroring allows constant monitoring of
network performance, sending an alert when a problem or error occurs.
You can configure port mirroring by defining a mirroring session, which
comprises one or two sources, the traffic direction of each source (one Rx, one
Tx, or one Rx-Tx), and a single destination.
Port mirroring supports the following interfaces as mirroring session sources and
destination for mirrored traffic:
ETH user or network ports
PCS
Logical MAC
LAG (Load balancing, Protection) is not supported.
At any time, you can monitor in your device inbound (Tx) traffic to one port
and/or outbound (Rx) traffic from another port, or both inbound and outbound
traffic of a single port. You can configure mirroring of Rx and Tx traffic either in
one mirroring session to the same destination port or in two mirroring sessions
to two separate destination ports.
Inbound traffic includes all traffic admitted into the source port following
physical layer tests, FCS, and more, but before filtering by L2CP, vlan-edit,
policing, and more. Outboumd traffic qualified for mirroring includes all packets
of the source that were actually transmitted, such as after the dequeue process
and filtering (e,g egress MTU).
The mirror port (destination port) can be a 1GbE or 10GbE user or network port.
The mirror port is dedicated solely for mirroring, and does not support
forwarding of inbound traffic.
A mirroring session source can be added while the session is running.
Configuration of a new mirror destination overrides the existing one; there is no
need to delete the existing destination.
Factory Defaults
By default, port mirroring is disabled.
Configuring Port Mirroring

To configure port mirroring:
1. Navigate to configure mirroring-session <num>.
11-210 Port Mirroring ETX-2i

The config> mirroring-session (num)# prompt is displayed.
Note <num> is the number of the mirroring session.

Type no mirroring-session (num) to disable the mirroring session.
Adding or removing source port from the [no] source {port <port-type> port type source port type
mirroring session <port-index>} {tx | rx | tx-rx} Possible values: ethernet, pcs,
or logical-mac
tx enable inbound mirroring.
rx enable outbound mirroring.
tx-rx enable both inbound
and outbound mirroring.
Adding or removing destination port [no] destination <port-type> port type destination port
from the mirroring session <port-index> type
Possible values: ethernet, pcs,
or logical-mac
Note: A destination port can be
used in one mirroring session
only.
Administratively enabling port mirroring no shutdown Type shutdown to

administratively disable the
mirroring session.
This command enables you to
keep the mirror configuration
and activate it only when
needed.
error is detected.
Message Possible Cause Corrective Action
Maximum number of Rx You attempted to open a Remove the existing

mirroring sessions has new Rx mirroring session mirroring session in order
already been configured. even though the maximum to create a new mirroring
number (one) of supported session.
Rx mirroring sessions was
already configured..
ETX-2i Port Mirroring 11-211

Message Possible Cause Corrective Action
Maximum number of Tx You attempted to open a Remove the existing Tx

mirroring sessions has new Tx mirroring session mirroring session in order
already been configured. even though the maximum to create a new Tx
number (one) of supported mirroring session.
Tx mirroring sessions was
already configured..
The same destination You used the same Define a different

cannot be defined for destination for more than destination for each
different sessions. one session. The same session.
destination may not be
defined for more than one
session at a time.
Examples
In the following example, all the outbound traffic from port 0/3 and inbound
traffic into port 0/4, is mirrored to Ethernet port 0/1.
ETX2i>configure mirroring-session 1
ETX2i>config>mirroring-session(1)# source port ethernet 0/3 rx
ETX2i>config>mirroring-session(1)# source port ethernet 0/4 tx
ETX2i>config>mirroring-session(1)# destination ethernet 0/1
ETX2i>config>mirroring-session(1)# no shutdown
exit
In the following example, all the inbound traffic to and outbound traffic from
port 0/4, is mirrored to Ethernet port 0/2.
ETX2i>configure mirroring-session 2
ETX2i>config>mirroring-session(2)# source port ethernet 0/4 tx-rx
ETX2i>config>mirroring-session(2)# destination ethernet 0/2
ETX2i>config>mirroring-session(2)# no shutdown
exit
11.11 Performance Management

ETX-2i maintains performance management (PM) statistics for selected entities
in the device. The PM statistics are collected into a file periodically, for retrieval
by RADview, for display in the RADview PM portal (refer to the RADview System
Users Manual for further details on the PM portal). The PM file includes the
following information: buffer (kernel) memory utilization and TCA, CPU
utilization, memory utilization, flash memory utilization, and device uptime. The
PM collection process can be globally enabled or disabled for the entire device.
In addition, the statistics collection can be enabled for all entities of a specific
type, or for specific entities.
11-212 Performance Management ETX-2i

Applicable Products
This feature is applicable to all ETX-2i products, with the following condition:
Scripts containing port numbers may have to be edited according to the
product port numbering.
Benefits
The PM data is useful for analyzing ETX-2i service quality. The flexible statistics
collection allows only the necessary data to be collected.
PM statistics collection is configured for the device, entity type, and specific
entities. PM statistics are collected for the following types of entities:
Ethernet ports
Flows
OAM TWAMP sessions
OAM CFM services
OAM CFM destination NEs
System parameters: memory usage and CPU utilization
Notes PM statistics collection is performed only if it is enabled for the entire device,
regardless of whether it is enabled for any entity
PM statistics are not collected for entities that are administratively disabled.
If PM statistics collection is disabled for a particular entity type, then no PM

statistics collection is done for any entity of that type, except those for which
PM statistics collection is enabled.
When PM statistics collection is enabled for all entities of the same type, then
when a new entity of that type is added the device automatically starts
collecting PM statistics for it, as soon as PM statistics maintenance (if applicable)
is enabled for the entity.
Note
If you are using the RADview PM Portal, it is recommended to enable PM
statistics collection for all relevant entities. See Examples for a script that you
can use for this purpose.
PM statistics collection is performed at user-configurable intervals of one second

to 15 minutes. A different interval can be configured for each entity type, and
for specific entities.
If different intervals are scheduled for collection at the same time, ETX-2i
collects the PM statistics starting with the interval that has the highest
frequency, and ending with the interval that has the lowest frequency. If ETX-2i
has not finished collecting the statistics for an interval when the scheduled time
for another interval arrives, the following action is taken according to whether
the new interval is the next interval, or an interval with higher frequency:
ETX-2i Performance Management 11-213

If it is the next interval, then the next interval is canceled, and a PM record
indicating the cancellation is inserted in the PM data.
If it is an interval with higher frequency, then ETX-2i collects the higher
frequency interval statistics and then resumes collecting the lower frequency
interval statistics. The PM data is retrieved from ETX-2i by RADview via TFTP
or SFTP. After PM data is retrieved, ETX-2i deletes the file and opens a new
one for further data.
Factory Defaults
Command Level under config Default Remarks
pm reporting pm PM statistics collection in device

is globally enabled by default.
pm-collection Specific entity level Disabled PM statistics collection for

specific entities is not explicitly
configured by default;
therefore, it is disabled until
statistics collection is enabled
for the entity type or entity.
pm-collection dest- reporting Disabled PM statistics collection for OAM

ne CFM destination NEs is not
explicitly configured by default;
therefore, it is disabled.
pm-collection eth reporting Disabled PM statistics collection for

Ethernet ports is not explicitly
pm-collection flow reporting Disabled PM statistics collection for

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

oam-cfm-service CFM services is not explicitly
pm-collection reporting Disabled PM statistics collection for

system memory usage and CPU
utilization is not explicitly
pm-collection twamp reporting Disabled PM statistics collection for

TWAMP is not explicitly

Configuring Performance Management

You can configure PM statistics collection for the entire device via the pm
command, and for entity types via the pm-collection command, in the reporting
level. For specific entities, you can configure PM statistics collection via
pm-collection, in the specific entity level.
You can configure the device to record statistics at fixed intervals using the
pm-collection interval <seconds> command or at the close of an interval using
the pm-collection on-interval-close command. For parameters that are not
zeroed regularly, it is recommended to record statistics at fixed intervals. For
parameters zeroed at fixed intervals (interval statistics), it is recommended to
record statistics whenever an interval is about to expire, i.e. right before the
parameters are zeroed, in order to avoid losing data. This option is available for
interval statistics only.The interval parameter for the pm-collection command
can range from 1 to 900 seconds (15 minutes); however, the value must divide
evenly into 3600. Different intervals can be specified for an entity type and for
specific entities of that type, up to a supported maximum number of intervals.
For example, if the PM statistics collection interval for all flows is configured to
15 minutes, and the PM statistics collection interval for flow-1 is configured to
1 minute, the data displayed in the RADview PM portal shows flow data for
every 15 minutes, and flow-1 data for every minute. You can also collect PM
statistics on interval close.
The following shows the PM statistics collection configuration tasks, and their
corresponding commands, as well as the level of each command.
Task Level under config Command Comments
Enabling PM statistics flows > flow(<flow-name>) pm-collection PM collection can be

collection for a specific { interval <seconds> | enabled at a defined
flow on-interval-close } interval or before an
interval expires.
Type no pm-collection to
disable PM statistics
collection for the flow.
Enabling PM statistics oam > cfm > md(<md-id>) > pm-collection PM collection can be
collection for a specific ma(<ma-id>) > mep(<mep- { interval <seconds> | enabled at a defined
OAM CFM service id>) > service(<service-id>) on-interval-close } interval or before an
interval expires.
collection for the service.
Enabling PM statistics oam > cfm > md(<md-id>) > pm-collection PM collection can be
collection for a specific ma(<ma-id>) > mep(<mep- { interval <seconds> | enabled at a defined
OAM CFM destination id>) > service(<service-id>) > on-interval-close } interval or before an
NE dest-ne(<dest-ne-index>) interval expires.
collection for the
destination NE.

Enabling PM statistics port > pm-collection PM collection can be

collection for a specific ethernet(<slot>/<port-num>) { interval <seconds> | enabled at a defined
Ethernet port (other on-interval-close } interval or before an
than the management interval expires.
port) Type no pm-collection to
collection for the Ethernet
port.
Enabling PM statistics port > mng-eth pm-collection PM collection can be

collection for the { interval <seconds> | enabled at a defined
Ethernet management on-interval-close } interval or before an
port interval expires.
collection for the Ethernet
management port.
Globally enabling PM reporting pm Type no pm to disable all

statistics collection for PM statistics collection in
device ETX-2i.
Note: no pm stops all PM
collection regardless of
other PM configuration;
however, it does not
change other
configurations.
It deletes any collected PM
data and PM files, as well.
Enabling PM statistics reporting pm-collection dest-ne PM collection can be

collection for OAM CFM { interval <seconds> | enabled at a defined
destination NEs on-interval-close } interval or before an
interval expires.
Type no pm-collection
dest-ne to disable PM
statistics collection for all
OAM CFM destination NEs.
Enabling PM statistics reporting pm-collection eth PM collection can be

collection for Ethernet { interval <seconds> | enabled at a defined
ports on-interval-close } interval or before an
interval expires.
Type no pm-collection eth
to disable PM statistics
collection for Ethernet
ports.

Enabling PM statistics reporting pm-collection flow PM collection can be

collection for flows { interval <seconds> | enabled at a defined
on-interval-close } interval or before an
interval expires.
Type no pm-collection flow
to disable PM statistics
collection for flows.
Enabling PM statistics reporting pm-collection PM collection can be

collection for OAM CFM oam-cfm-service enabled at a defined
services { interval <seconds> | interval or before an
on-interval-close } interval expires.
oam-cfm-service to disable
PM statistics collection for
OAM CFM services.
Enabling PM statistics reporting pm-collection system PM collection can be

collection for system { interval <seconds> | enabled at a defined
parameters on-interval-close } interval or before an
interval expires.
system to disable PM
statistics collection for
system parameters.
Enabling PM statistics reporting pm-collection twamp PM collection can be

collection for OAM { interval <seconds> | enabled at a defined
TWAMP component on-interval-close } interval or before an
interval expires.
twamp to disable PM
statistics collection for
OAM TWAMP component.
Note
PM statistics are collected for entities for which PM statistics collection is
specifically enabled in the entity level via pm-collection, even if PM statistics
collection for the entity type is disabled.
Viewing Performance Management Configuration

You can use the info detail command to view the performance management
configuration.
To view the performance management configuration for the device and for
entity types:
1. Navigate to configure reporting.
2. Enter info detail | include pm to view PM-related commands in the
configuration.

To view the performance management configuration for specific entities:

1. Navigate to the specific entity level.
2. Enter info detail | include pm to view PM-related commands in the
configuration.
Examples
To enable PM for all relevant entities in ETX-2i:
PM statistics collection enabled for device
PM statistics collection enabled for all relevant entities, every five minutes.
exit all
configure reporting
#**** Enable PM in device
pm
#**** Enable PM for Eth ports, collection interval=5 min
pm-collection eth interval 300
#**** Enable PM for flows, collection interval=5 min
pm-collection flow interval 300
#**** Enable PM for OAM CFM services, collection interval=5 min
pm-collection oam-cfm-service interval 300
#**** Enable PM for OAM CFM dest NEs, collection interval=5 min
pm-collection dest-ne interval 300
exit all
save
To configure the following PM:

PM statistics collection enabled for device.
PM statistics collection enabled for Ethernet ports, every two minutes.
PM statistics collection enabled for flows, every five minutes.
PM statistics collection for Ethernet port 0/3 configured to every minute.
PM statistics collection enabled for OAM CFM services, every 15 minutes.
PM statistics collection enabled for OAM CFM dest NEs, every 15 minutes.
exit all
configure reporting
#**** Enable PM in device
pm
#**** Enable PM for Eth ports, collection interval=2 min
#**** Enable PM for flows, collection interval=5 min
#**** Enable PM for OAM CFM services, collection interval=15 min
#**** Enable PM for OAM CFM dest NEs, collection interval=15 min
exit all
#**** Configure PM statistics collection interval for Eth port 0/3, to 1 min

exit all
save
To display PM configuration from above example:

ETX-2i# configure reporting
ETX-2i>config>reporting# info detail | include pm
pm
ETX-2i>config>reporting# exit all

ETX-2i>config>port>eth(0/3)# info detail | include pm
Table 11-30 lists the messages displayed by ETX-2i when a configuration error is
detected.
Message Description
Invalid interval; must divide evenly into The pm-collection command was entered with an interval value
3600 that does not divide evenly into 3600.
Cannot execute; too many different Attempt was made to configure more intervals than the
intervals supported maximum.
11.12 Detecting Problems

The LED indicators indicate errors on the hardware level.
LEDs
A red LED is usually an indication of a problem. Check the port that is associated
with the LED to further investigate the problem. Refer to the Operation chapter
for a description of the unit LEDs.
Alarms and Traps

Alarms serve as notification of a fault in the device, and are indicated by an
entry in the alarm and event history log, and/or an SNMP trap to a management
station. See Handling Alarms and Events for further details on alarms, events,
and traps.
ETX-2i Detecting Problems 11-219

Statistic Counters
Statistic counters provide information on possible abnormal behavior and
failures. You can collect statistics on the following:
Ethernet ports
E1/T1 ports, if applicable
SHDSL ports, if applicable
VDSL ports, if applicable
Flows
RADIUS server
OAM CFM
For further information, refer to the relevant sections in Chapter 6 10 and the
relevant sections in the troubleshooting chart.
You can clear the statistics for Ethernet ports, flows, and OAM services.
Statistics clearing is globally enabled by default. Once statistics are cleared from
an interval, the interval becomes not valid.
To clear the statistics:

At the device prompt, enter:
clear-statistics
The statistics for Ethernet ports, flows, and OAM services (running
counters only; not current counters) are cleared. The OAM interval
statistics are not cleared.
Note PW and E1 do not support running-statistics; therefore, clear-statistics clears

only the current statistics.
11.13 Handling Alarms and Events

An alarm is an indication of a fault in the device. An event is an occurrence in
the device that may be a fault or may be a user login, change in port status, etc.
Alarms and events can be written to the alarm and event history log. In addition
to the history log containing alarms and events, the device maintains statistics
for alarms and events in a brief log. Alarms can also be written to the active
alarm table. An SNMP trap can be sent to management stations as the result of
an alarm/event. Additionally, you can configure alarms and events to pop up on
the serial CLI terminal.
Alarms and events have the following properties:
11-220 Handling Alarms and Events ETX-2i

Source An entity for which alarms and events can be generated.

The source consists of a source ID, source type, and source
name.
Alarms and events can be generated for any of the
following source types: system, fan, power-supply, station-
clock, recovered-clock, g82751-recovered*, g82751-
master-cl*, gnss, card, ethernet, vdsl, shdsl, pcs, sdh-
sonet, e1, t1, e3, t3, vcg, bridge, logical-mac, etp, gfp, lag,
oam-efm, oam-cfm-mep, oam-cfm-destne, eps, erp, eth-
protection, router-interface, pw, bgp, domain-clock
recovered-clock-*, domain-clock-sou*, master-clock,
smart-sfp, oam-cfm-r-mep, erp-port, ospf, ospf-neighbor,
ospf-interface, twamp-session, twamp-peer, all
ID Unique numeric identification of the alarm/event
Name Unique alphanumeric identification of the alarm/event, up

to 32 characters
Description Alphanumeric description that provides details on the

alarm/event
Severity Alarms only; Critical, Major, or Minor
Alarms and events can be masked per source type, source ID, or minimum
severity. When an alarm/event is masked, it is not written to the history log, and
any corresponding traps are not sent to management stations, regardless of
masking in the SNMP manager configuration. When an alarm/event is not
masked, any corresponding traps are sent only to management stations for
which the traps are not masked in the SNMP manager configuration.
Alarm Soaking
ETX-2i supports alarm soaking. This means that the device does not raise an
alarm immediately upon detecting an abnormal condition (i.e. defect); only after
the abnormal condition has occurred uninterrupted for a certain amount of time
(called the rising soaking time). Similarly, the alarm is cleared only after the
abnormal condition is resolved and remains resolved for a certain amount of
time (called the falling soaking time or clear time). In this way, alarm soaking
prevents fleeting alarms, i.e. alarms that rise and fall multiple times in a short
period. Instead of sending a flood of alarms to RADview, only one initial alarm is
sent, and the final clear alarm is sent only upon stabilization of the link.
The device supports alarm soaking, provided the following requirements are met:
The device supports configurable alarm rising and falling soaking times, as
follows:
Rising and falling soaking times may be configured to different values.
The configurable soaking time range is 0 (i.e. no soaking time) to 10,000
milliseconds.
The default rising soaking time is 2,500 milliseconds (2 seconds);
default falling soaking time is 10,000 milliseconds (10 seconds).
ETX-2i Handling Alarms and Events 11-221

The actual soaking time may deviate by up to second from the

configured value.
The configured soaking times apply only for those entities that do have
a standard dictating a different behavior. If there is such a standard,
such as SDH/SONET and DS1, the standard is followed.
When a defect occurs, the device must wait the rising soaking time (either
configured or dictated by a standard) before raising the alarm. An alarm is
raised only if the defect exists for the entire soaking time. If the defect is
cleared and reoccurs, the rising soaking timer must be rearmed.
When a condition that caused an alarm is resolved, the device must wait the
falling soaking time (either configured or dictated by a standard) before
clearing the alarm. Only if the condition stays resolved for the entire soaking
time, the alarm is cleared. If the defect reoccurs, the soaking timer must be
rearmed.
Configuring Alarm and Event Properties

This section explains how to configure alarm/event properties.
Note In the commands alarm-source-attribute, alarm-source-type-attribute, and

mask-minimum-severity, the popup parameter controls popup behavior in serial
management sessions, and the vtypopup parameter controls popup behavior in
Telnet/SSH management sessions.
Note All traps are maskable, by masking the corresponding alarm/event via the
alarm-source-attribute / alarm-source-typeattribute commands, or by masking
the corresponding alarm per severity via the mask-minimum-severity command.
To configure alarm/event properties:

The config>reporting# prompt is displayed.

Configuring alarm input alarm-input <port-number> [active {high | low | Three input alarms are
off}] [description <description>] supported over the Alarm
connector ( 9-pin Terminal
Block).
If you set alarm-input to active
state, configure alarm inputs
activation mode to one of the
following:
high active alarm input
indicated by high voltage
low active alarm input
indicated by low voltage
off active alarm input
disabled
In description, enter a
description of the alarm
generated by the alarm-input.
This description is saved in the
log and sent with snmp traps
when the alarm occurs.
Configuring alarm/event alarm-source-attribute <source-name> Use the no form to mask

severity and masking per [<source-id>] alarm {<alarm-list> | all} [severity alarms/events. The following
source {critical | major | minor}] [log] [snmp-trap] [led] apply:
Note: Severity applies [popup] [vtypopup] If a trap is masked according
only to alarms. alarm-source-attribute <source-name> to alarm/event attribute, it
[<source-id>] event {<alarm-list> | all} [log] is not sent to any
[snmp-trap] [popup] [vtypopup] management station,
regardless of whether it is
masked in the SNMP
manager configuration.
If a trap is unmasked
according to alarm/event
attribute, it is sent only to
management station for
which it is not masked in
the SNMP manager
configuration.

Configuring alarm/event alarm-source-type-attribute <source-type> Use the no form to mask

severity and masking per [<source-id>] alarm {<alarm-list> | all} [severity alarms/events. The following
source type {critical | major | minor}] [log] [snmp-trap] [led] apply:
Note: Severity applies [popup] [vtypopup] If a trap is masked according
only to alarms. alarm-source-type-attribute <source-type> to alarm/event attribute, it
[<source-id>] event {<alarm-list> | all} [log] is not sent to any
[snmp-trap] [popup] [vtypopup] management station,
regardless of whether it is
masked in the SNMP
manager configuration.
If a trap is unmasked
according to alarm/event
attribute, it is sent only to
management station for
which it is not masked in
the SNMP manager
configuration.
Configuring alarm mask-minimum-severity [log {critical | major |

masking and popup minor}] [snmp-trap {critical | major | minor}] [led
behavior per severity {critical | major | minor}] [popup {critical | major |
minor}] [vtypopup {critical | major | minor}]
Configuring alarm rising soaking-time interval [rising rising-msec] clear rising, falling: 010,000 ms
and falling soaking times [falling falling-msec] Default:
rising 2500 ms
falling 10000 ms
Note: The configured soaking
times apply only for entities for
which there is no standard
dictating a different behavior. If
there is such a standard (e.g.
for SDH/SONET and DS1), the
standard must be followed.
Displaying information on show alarm-information <source-type> show alarm-information

specified alarms and {<alarm-list> | all} <source-type> all indicates to
source type display information on all
alarms of the specified source
type.

Displaying information on show alarm-inputs [all] show alarm-input all indicates

alarm inputs to display information on all
alarm inputs of the device (up
to three).
The following is displayed for
each alarm-input:
Port port number
Status active or inactive
Voltage high, low, or off
Description
Displaying list of show alarm-list

supported alarms, show alarm-list [<source-type> [<source-id>]
optionally for specified [severity {critical | major | minor}]]
source/severity
Displaying information on show event-information <source-type>

specified event and [<event-list>]
source type
Displaying list of show event-list

supported events show event-list <source-type> [<event-list>]
Controlling Popup Behavior

Alarms and events are displayed (pop up) on active CLI terminals as soon as they
occur. You can disable the popups per management session, without saving this
setting in the configuration. It is relevant only for a management session (serial
or Telnet/SSH) for which it is configured, and does not affect any other active
session.
If the popups are disabled for the current management session, they are not
displayed, no matter how they are configured for a specific alarm or event (see
Configuring Alarm and Event Properties).
The current alarm/event popup status is available in the show users-details
screen (see below).
To disable or enable alarm/event popups:

At any level, enter popup-suspend to disable alarm/event popups.
Enter no popup-suspend to enable alarm/event popups.
To display the user information:

In the configure>management# prompt, enter show users-details.
ETX-2i# configure management show users-details
From:Serial For(sec):281744
User:123456 Level:su Popup: Enabled
From:100.100.100.100/SSH For(sec):4510

Working with Alarm and Event Logs

This section explains how to work with the log files to display or acknowledge
alarm/events,
To work with alarm/event log files:

The config>reporting# prompt is displayed.
Acknowledging alarms acknowledge {log | brief-log | activity-log | all-logs}
Rebuilding active alarm active-alarm-rebuild [send-traps]

database
Clearing alarms from log clear-alarm-log {log | brief-log | activity-log | all-logs}

file(s)
Displaying active alarms, show active-alarms

optionally according to show active-alarms {<source-type> [<source-id>] |
specified criteria all} [minimum-severity {critical | major | minor}]
[masked-included] [instance <instance-number>]]
Displaying active alarms show active-alarms-details

with details, optionally show active-alarms-details {<source-type>
according to specified [<source-id>] | all} [minimum-severity {critical |
criteria major | minor}] [time-zone-utc] [masked-included]
[instance <instance-number>]]
Displaying alarms in alarm show alarm-log

and event history log, show alarm-log {<source-type> [<source-id>] | all}
optionally according to [minimum-severity {critical | major | minor | cleared}]
specified criteria [order-ascending] [time-zone-utc]
[acknowledged-included] [start <yyyy-mm-dd>
[<hh:mm[:ss]>] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]
show alarm-log {<source-type> [<source-id>] | all}
[minimum-severity {critical | major | minor | cleared}]
[order-ascending] [time-zone-utc]
[acknowledged-included] {[last-seconds <seconds>]
| [last-entries <entries>]}

Displaying alarms in brief show brief-alarm-log

alarm and event history show brief-alarm-log {<source-type> [<source-id>] |
log, optionally according all} [minimum-severity {critical | major | minor |
to specified criteria cleared}] [order-ascending] [time-zone-utc]
[<hh:mm[:ss]>]] [end <yyyy-mm-dd>
[<hh:mm[:ss]>]]
show brief-alarm-log {<source-type> [<source-id>] |
all} [minimum-severity {critical | major | minor |
cleared}] [order-ascending] [time-zone-utc]
Displaying brief alarm and show brief-log

event history log, show brief-log {<source-type> [<source-id>] | all}
[<hh:mm[:ss]>]]
show brief-log {<source-type> [<source-id>] | all}
Displaying alarm and show log

event history log, show log {<source-type> [<source-id>] | all}
[<hh:mm[:ss]>]]
show log {<source-type> [<source-id>] | all}
Alarms and Events

You can view the full lists of alarms and events supported by ETX2x.
To view the alarms table:
Double-click the paper clip image on the following line.

To view the events table:
Double-click the paper clip image on the following line.
Notes Entries with source type card are relevant only for ETX2i modular option with
SHDSL or VDSL module.
Entries with source type pcs or shdsl are relevant only for ETX2i modular
option with SHDSL or VDSL module.
Entries with source type e1t1 are relevant only for ETX2i modular option
with E1/T1 module.
Entries with source type ptp-recovered or ptp-recovered-master are relevant
only for PTP ordering options.
Entries with source type clock-domain, clock-domain-source, or station-clock
are relevant only for timing ordering options.
11.14 Troubleshooting
This section contains a general troubleshooting chart that lists possible failures
and provides workarounds.
Use this chart to identify the cause of a problem that may arise during
operation. For detailed description of the LED indicators functions, refer to the
Operation chapter.
To correct the reported problem, perform the suggested corrective actions. If a
problem cannot be resolved by performing the suggested action, please contact
your RAD distributor.
Table 11-31. Troubleshooting Chart
Fault/Problem Probable Cause Corrective Action
The unit is dead No power Verify that both ends of the power
(POWER LED is off) cable are properly connected.
Blown fuse Disconnect the power cable from both

ends and replace the fuse with another
fuse of proper rating.
The event log reports a View the inventory file by entering

fan or power supply show inventory at the config>system
error. prompt.
Restart the unit.
In case of failure, replace the entire
unit.
11-228 Troubleshooting ETX-2i

Fault/Problem Probable Cause Corrective Action
The unit is unreachable Incorrect management settings Using a local serial connection, enable
the relevant management access type
by entering telnet, snmp, and/or ssh at
the config>mngmnt>access prompt.
View the list of enabled management
access types and settings by entering
info detail at the config>mngmnt
prompt
Verify that a router interface has been
configured with management access
set to allow all, assigned an IP address,
and bound to an administratively
enabled SVI.
Verify that management flows have
been set up to/from the SVI, and that
the flows are enabled.
Management path disconnected In case of remote management,

analyze this issue using a local serial
connection.
At the current prompt, check whether
the desired unit responds by entering
ping <IP address>.
Check network connectivity issues and
firewall settings.
Verify that the management flows have
been configured correctly.
Physical link fails to Link may be administratively Administratively enable the link.
respond disabled. In case of Ethernet links, make sure
that the autonegotiation, speed, and
duplex modes match the configured
values on the access switch/router.
Ethernet LINK LED Ethernet cable problem Check the Ethernet cable to see
is off whether a cross or straight cable is
needed.
Check/replace Ethernet cable.
Verify that the range is within the
limits.
Check the port by connecting the
remote end of the cable to a different
switch.
Send the unit for repair.
ETX-2i Troubleshooting 11-229

11.15 Performing Diagnostic Tests
Running a Ping Test

You can ping a remote IPv4 or IPv6 host to check the ETX-2i IP connectivity with
that host. You can define the number of pings (packets) to generate, or
configure a continuous ping (infinite). The ping generator continues to generate
ping requests according to the number of configured pings, or until you manually
disrupt it (by pressing Ctrl+C).
To ping an IP host:
In any level, start pinging the host, specifying its IP address (IPv4 or IPv6)
and optionally the number of packets to send, payload size (in bytes), and
router entity number:
ping <ip-address> [number-of-packets <packets>] [payload-size <bytes>]
[router-entity <number>]
Table 11-32. Ping Parameters
<ip-address> Destination IP address Valid IPv4 or IPv6 address

1.1.1.1255.255.255.255
Note: Multicast address is not
allowed.
number-of-packets Number of pings Possible values:

0 (forever), 1-10000
Default: 5
payload-size Packet size Possible values:

32-1450 bytes
router-entity Related router-entity Possible values: 1-max-vrf-number

If the remote host answers, ETX-2i displays the ping results including the
round trip delay, rounded as in the following table.
Table 11-33. Ping Round Trip Results
Round Trip Delay Displayed in Ping Results
<= 10 msec time < 10 ms
>= 11 msec and <= 20 msec time < 20 ms
: :
: :
11-230 Performing Diagnostic Tests ETX-2i

Example
ETX-2i# ping 10.10.10.10

Reply from 10.10.10.10.44: bytes = 32, packet number = 2, time < 10 ms
Tracing the Route

This diagnostic utility traces the route through the network from ETX-2i to the
destination host. The trace route utility supports up to 30 hops.
To trace a route:
In any level, start the trace route and specify the IP address (IPv4 or IPv6) of
the host to which you intend to trace route:
trace-route <1.1.1.1255.255.255.255>
11.16 Frequently Asked Questions
Q How should ETX-2i be configured for management?

A You need to configure a router interface for management by assigning it an
IP address, and binding it to an SVI for which management flows have been
configured. Additionally, you need to configure the default gateway address
in the router.
Q If I change the functional mode of a network Ethernet port to user, what

happens to the associated flows?
A When you change the functional mode, all flows related to the port are
deleted.
11.17 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-2i Technical Support 11-231

11-232 Technical Support ETX-2i

Chapter 12
Software Upgrade
This chapter explains how to upgrade ETX2i for software version 6.4.
Software upgrade is required to fix product limitations, enable new features, or
make the unit compatible with other devices that are already running the new
software version.
The device can store up to two software images, referred to as software packs. It
is recommended to name these software packs sw-pack-1 and sw-pack-2.
Note You can define only two software packs simultaneously. Although the CLI allows
you to name the SW packs sw-pack-1 through sw-pack-4, it is recommended to
name them sw-pack-1 and sw-pack-2.
You can designate any of the software packs as active. The non-active software
pack serves as a backup that can be used if the active software becomes
corrupted.
The information in this chapter includes the following:
Software packs that can be loaded into each device
Detailed conditions required for the upgrade
Any impact the upgrade may have on the system
Description of downloading options
Application software can be downloaded to ETX2i via SFTP/TFTP with the copy
command, or via XMODEM, FTP, or TFTP, from the Boot screen.
The downloaded software pack can be installed as the active software via the
admin software install command, or from the Boot screen.
Note Software upgrade relates to upgrading from the products previous version to
current version. To upgrade from an older version, you may not be able to
upgrade directly to the latest version, but may be required to upgrade one
version at a time. Refer to the relevant User Manual for upgrade instructions.
12.1 Compatibility Requirements

Following are the software releases that can be upgraded to version 6.4, as well
as the hardware revisions that can accept the software version 6.4.
Software Ver. 5.8x, 5.9x, 6.0x, 6.2x, 6.3x
Hardware 1.0 and above
ETX2i Compatibility Requirements 12-1

Chapter 12 Software Upgrade Installation and Operation Manual
12.2 Impact
During the software upgrade process, service is disrupted.
12.3 Prerequisites
SFTP/FTP/TFTP Prerequisites
Prior to upgrading via SFTP/FTP/TFTP, verify that you have the following:
Operational ETX2i unit with valid IP parameters configured
Connection to a PC with an SFTP/FTP/TFTP server application and a valid IP
address
Software image file stored on the PC. The image file (and exact name) can be
obtained from the local RAD business partner from whom the device was
purchased.
XMODEM Prerequisites
Prior to upgrading via XMODEM, verify that you have the following:
Operational ETX2i unit
Connection to a PC via a terminal emulation program
Software image file stored on the PC. The image file (and exact name) can be
obtained from the local RAD business partner from whom the device was
purchased.
Software Packs
Each ETX2i software download can contain two sw-packs from the available
options listed in the following table.
Table 12-1. Software Packs per Device
Device File Name Description
ETX2i ETX2_x.x.x(x.x)_sw-pack_2i.bin Device with capabilities of full router, i.e. includes

dynamic routing protocols (OSPF and BGP)
ETX2_x.x.x(x.x)_sw-pack_2i_sr.bin Device with capabilities of static router, i.e. without

dynamic routing protocols
dnfv-os_1.x.x.xxx OPT Compute node optimized
dnfv-os_1.x.x.xxx ACC Compute node with accelerator
ETX-2i-B ETX2_x.x.x(x.x)_sw-pack_2iB.bin Device with capabilities of full router
ETX2_x.x.x(x.x)_sw-pack_2iB_sr.bin Device with capabilities of static router
12-2 Prerequisites ETX2i

Installation and Operation Manual Chapter 12 Software Upgrade
Device File Name Description
ETX-2i-B-x86 ETX2_x.x.x(x.x)_sw-pack_2iB_10x1G.bin Device with capabilities of full router

ETX-2i-B 10 ports
ETX2_x.x.x(x.x)_sw-pack_2iB_10x1G_sr.bin Device with capabilities of static router
ETX-2i-10G ETX2_x.x.x(x.x)_sw-pack_2i_10g.bin
ETX-2i-10G-LC ETX2_x.x.x(x.x)_sw-pack_2i_10g_lc.bin
12.4 Upgrading Software via CLI

You can upgrade ETX2i software using CLI commands.
The recommended software downloading method is to use the copy command.

Network administrators can use this procedure to distribute new software
releases to all the managed ETX2i units in the network from a central location.
Use the following procedure to download software release 6.4 to ETX2x via CLI.
1. Verify that the image file is stored on the PC with the SFTP/TFTP server
application.
2. Verify that the ETX2i router has been configured with valid IP parameters.
3. Ping the PC to verify the connection.
4. Activate the SFTP/TFTP server application.
5. Download the image file from the PC to ETX2i.
6. Install the image as the active software.
Note Configuration values shown in this chapter are examples only.
Verifying the Host Parameters

In order to be able to establish communication with the SFTP/TFTP server, the
ETX2i router must have IP parameters configured according to your network
requirements. Refer to the following manual sections for additional information:
Connecting to a Terminal in the Installation and Setup chapter
Working with Terminal in the Management and Security chapter
Router in the Networking chapter
Pinging the PC
Check the integrity of the communication link between ETX2i and the PC by
pinging the PC from ETX2i.
ETX2i Upgrading Software via CLI 12-3

To ping the PC:

1. In any level, start pinging the PC specifying its IP address and optionally the
number of packets to send:
ping <ip-address> [number-of-packets <num-packets>]
num-packets can be 1-10,000 or 0 (forever) for a continuous ping.
Default is 5.
A reply from the PC indicates a proper communication link.
2. If the ping request times out, check the link between ETX2i and the PC
(physical path, configuration parameters, etc.).
Activating the SFTP Server

Once the SFTP server is activated on the PC, it waits for any SFTP file transfer
request originating from the product, and carries out the received request
automatically.
SFTP file transfers are carried out through TCP port 22. Make sure that the
firewall you are using on the server allows communication through this port (refer
to the Administration chapter for details).
Activating the TFTP Server

Once the TFTP server is activated on the PC, it waits for any TFTP file transfer
request originating from the product, and carries out the received request
automatically.
TFTP file transfers are carried out through port 69. Make sure that the firewall
you are using on the server allows communication through this port (refer to the
Administration chapter for details).
Note Configure the connection timeout of the TFTP server to be more than 30 seconds
to prevent an automatic disconnection during the backup partition deletion
(about 25 seconds).
Downloading the New Software Release File

This procedure is used to download a new software version.
To copy the image file to the ETX2i unit:

In any level, enter:
copy sftp://<username>:<password>@<ip-address>/<image-file-name>
<sw-pack-n>
Where <ip-address> is the IP address of the PC where the SFTP server is
installed and <n> is the index of the software pack.
Or
copy tftp://<tftp-ip-address>/<image-file-name> <sw-pack-n>
Where tftp-ip-address is the IP address of the PC where the TFTP server is
installed and <n> is the index of the software pack.
12-4 Upgrading Software via CLI ETX2i

Note Choose an index that is not being used by the active software, or by a software
pack that you do not want to overwrite.
The software download is performed. See Activating the Software for

instructions on installing the downloaded software as the active
software.
Activating the Software

After software is downloaded to ETX2i, it has to be installed via the install
command as the active software. When you install software, by default ETX2i
creates a restore point, so that if there is a problem with the new software pack,
you can perform a rollback to the previous software pack and startup-config file.
This ensures that if you changed the startup-config file before noticing that
something was wrong with the newly installed software, you can restore the
startup-config that was running before the last installation.
Note The file startup-config must exist before you can install software with creation of
a restore point.
Prior to installing the software, you can request (via command

software-confirm-required) that the user confirm the next installed software (via
command software-confirm) following the next ETX2i reboot. This software
confirmation command verifies that the user has regained connection to the
device following installation. If confirmation is requested, but the user does not
confirm the software (via command software-confirm) within the configured
timeout period, ETX2i automatically falls back to its previous software. This
precaution prevents a permanent loss of connection to the remote device
following installation.
To request software confirmation:

At the admin>software# prompt, enter:
software-confirm-required [time-to-confirm <minutes>]
The confirmation timeout can be from five minutes to 24 hours. If you do not
specify it, the default is five minutes.
Note You can cancel the software confirmation request by entering

no software-confirm-required.
Next time ETX2i reboots and loads new software, it starts a confirmation
timer. See the following procedure for more details on the confirmation.
To install a software pack as active:
Notes If startup-config does not exist, you must install the software pack without
creating a restore point.
As a defective startup-config can cause a loss of connection, it is not
recommended to install software and change startup-config at the same time.
However, if you must do both at the same time, first install the software and
only after verifying it, make the needed configuration changes (or vice versa).
ETX2i Upgrading Software via CLI 12-5

1. At the admin>software# prompt, enter:

install <filename> [no-restore-point]
The parameter <filename> can be any of the non-active software packs
(sw-pack-1 through sw-pack-4). If you specify no-restore-point, then after
the software is installed, it is not possible to roll back to the previous
software.
You are prompted to confirm the operation.
!Device will install file and reboot. Are you sure? [yes/no] _
2. Type yes to confirm.

If a restore point is being created, then startup-config is copied to
restore-point-config. ETX2i designates the specified software pack as
active, then reboots.
3. If a software confirmation request is active, ETX2i starts a timer with the
specified timeout period.
Note While the confirmation timer is running, ETX2i does not allow any commands
that change its configuration.
4. If the software-confirm command is entered before the timer expires, the

software is considered to be confirmed.
5. If the software-confirm command is not entered before the timer expires,
then restore-point-config is deleted, ETX2i designates the previously active
software pack as active, then reboots.
12.5 Upgrading ETX2i Software via the Boot Screen

Software downloading can also be performed from the Boot screen. The Boot
screen can be reached while ETX2i performs initialization, such as after
power-up.
You may need to start the loading from the Boot screen if you are unable to use
the copy command (for example, because the ETX2i software has not yet been
downloaded or is corrupted).
Caution The Boot screen procedures are recommended only for use by authorized
personnel, because it provides many additional options that are intended for use
only by technical support personnel.
The following software downloading options are available from the Boot screen:
Downloading using the XMODEM protocol. This is usually performed by
downloading from a PC directly connected to the CONTROL DCE port of the
unit.
Downloading using FTP/TFTP. This is usually performed by downloading from
a remote location that provides an IP communication path to an Ethernet port
of ETX2i.
12-6 Upgrading ETX2i Software via the Boot Screen ETX2i

Accessing the Boot Screen

The Boot screen can be accessed when the device is powered up, before logging
in.
To access the Boot screen:

1. Connect the ASCII terminal or PC with terminal emulation to the ETX2i
CONTROL port.
2. Configure the communication parameters of the selected PC serial port for
asynchronous communication with 9,600 bps, no parity, one start bit, eight
data bits, and one stop bit. Turn all types of flow control off.
3. Power off ETX2i.
4. Activate the terminal application.
5. Power on ETX2i and immediately start pressing the <Enter> key several
times in sequence until you see the prompt to press any key to stop the
autoboot.
6. Press any key.
The Boot screen appears. A typical Boot screen is shown below (the exact
version and date displayed by your ETX2i unit may be different).
Note If you miss the timing, ETX2i performs a regular reboot process (this process
starts with Loading/un-compressing sw-pack-<n> and ends with the login
screen).
System Boot
Copyright 1984-2008 RAD Data Communications, Ltd.
Boot version: 1.05 [May 26 2015]
CPU : Freescale P1015E - Security Engine

OS version : VxWorks 6.9
BSP version: 1.0/3
Boot-Manager version: 3.02 [Oct 19 2014]
Use '?'/help to view available commands
Press any key to stop auto-boot...

1
[boot]:
Figure 12-1. Boot Screen
7. Enter ? to display a list of boot commands.

Commands:
?/help - print this list
p - print boot parameters
ETX2i Upgrading ETX2i Software via the Boot Screen 12-7

c [param] - change boot parameter(s)

v - print boot logo with versions information
run - load active sw pack and execute
delete <FileName> - delete a file
dir - show list of files
show <index> - show sw pack info
download <index> [,<FileName|x>] - download a sw pack to specific index (x - by Xmodem)
set-active <index> - Set a sw pack index to be the active application
control-x/reset - reboot/reset
8. Enter p to display all boot parameters.
The boot parameters appear. A typical boot parameter list is shown
below (see Table 12-2 for details on the boot parameters).
[boot]: p
file name (fn) : vxWorks

device IP (ip) : 10.10.10.101
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.2
gateway IP (g) : 10.10.10.2
user (u) : vxworks
ftp password (pw) : *******
device name (dn) : ETX2i
quick autoboot (q) : no
protocol (p) : ftp
baud rate (b) : 9600
Figure 12-2. Typical Boot Parameters Screen
Table 12-2. Boot Parameters
Parameter Command Description
file name fn The binary software pack file (*.bin) name to be

downloaded via FTP/TFTP
device ip ip ETX2i IP address
device mask dm ETX2i IP subnet mask
server IP sip FTP/TFTP server IP address
gateway ip g FTP/TFTP server default gateway IP address
user u User name for FTP server

Note: Displayed only when using FTP protocol.
ftp password pw User password for FTP server

Note: Displayed only when using FTP protocol.
device name dn ETX2i
quick autoboot q Enables or disables the quick autoboot feature
protocol p File transfer protocol to use: FTP or TFTP
baud rate b Transmission bit rate (in kbps): 9600, 19200, or 115200
9. Enter c to configure the boot parameters.

The boot parameters are displayed line by line. For each parameter, you
can type a different value, or click <Enter> to go to the next parameter.
The example below illustrates changing the file name to ETX2i.bin, and
the protocol to TFTP.
'.' = clear field; '-' = go to previous field; ^D = quit
file name (fn) : vxworks ETX2i.bin

device IP (ip) : 10.10.10.101
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.2
gateway IP (g) : 10.10.10.2
user (u) : vxworks
ftp password (pw) (blank = use rsh): *******
device name (dn) : ETX2i
quick autoboot [y/n] : n
protocol [tftp/ftp] : ftp tftp
baud rate [9600/19200/115200]: 9600
10. See the following sections for instructions on downloading via XMODEM, FTP,
or TFTP.
Using FTP
Use the following procedure to download software release 6.4 to ETX2i via FTP.
To download software release via FTP:

1. Verify that the image file is stored on the PC with the FTP server application.
2. Enter the Boot screen and set the boot parameters as needed (see Accessing
the Boot Screen). For example, set the FTP user and password, and set
protocol to FTP.
3. At the boot prompt, enter:
download <index>[, <FileName>]
If no errors are detected, the downloading process starts, and the file is
downloaded via FTP.
Notes The <index> parameter corresponds to the software pack number to which to
copy the image file.
If you have set the file name in the boot parameters, you do not need to
specify <FileName>.
For example, to download the file name configured in the boot

parameters to sw-pack-2, enter:
download 2
4. See Activating the Software for instructions on activating the downloaded
software.
Using TFTP
Use the following procedure to download software release 6.4 to ETX2i via TFTP.
ETX2i Upgrading ETX2i Software via the Boot Screen 12-9

To download software release via TFTP:

1. Verify that the image file is stored on the PC with the TFTP server application.
the Boot Screen). For example, set protocol to TFTP.
download <index>[, <FileName>]
If no errors are detected, the downloading process starts, and the file is
downloaded via TFTP.
Notes The <index> parameter corresponds to the software pack number to which to
copy the image file
If you have set the file name in the boot parameters, you do not need to
specify <FileName>.
For example, to download the file name configured in the boot

parameters to sw-pack-2, enter:
download 2
software.
Using XMODEM
Use the following procedure to download software release 6.4 to ETX2i via
XMODEM.
To download software release via XMODEM:

1. Verify that the image file is stored on the PC with the terminal application.
the Boot Screen).
download <index>, x
Note The <index> parameter corresponds to the software pack number to which to
copy the image file.
The process starts, and the following is displayed:

The terminal will become disabled !!!
Please send the file in XMODEM
4. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
The Send File window is displayed:
Select the prescribed ETX2i software file name (you may use the
Browse function to find it).

In the Protocol field, select Xmodem.

When ready, press Send in the Send File window.
You can now monitor the progress of the downloading in the Send File
window.
When the downloading process has successfully completed, a sequence
of messages similar to the following is displayed:
File writing to flash: - 4030KB
File downloaded successfully to :2

software.
Activating the Software

To activate a software pack, you need to designate it as active and load it.
To activate a software pack:

1. To set the software as active, enter:
set-active <index>.
A confirmation similar to the following is displayed:
SW set active 2 completed successfully.
2. To load the active software, type: run.

A sequence of messages similar to the following is displayed:
Loading/un-compressing sw-pack-2...
Starting the APPLICATION off address 0x10000...
After a few more seconds, the login prompt is displayed.
12.6 Verifying Upgrade Results

To verify that the upgrade was successful, log on to ETX2i via a terminal
emulation program to view the Inventory table (show summary-inventory at
prompt config>system#), and verify the active software version in the SW Rev
column.
12.7 Restoring the Previous Version

If the installed software malfunctions and was installed with a restore point
(restore-point-config must exist on device), you can perform rollback to the
previous active software.
ETX2i Restoring the Previous Version 12-11

To roll back to the previous active software pack:

1. At the admin>software# prompt, enter:
undo-install
You are prompted to confirm the operation.
! Falling back to restore point ! Are you sure? [yes/no] _
2. Type yes to confirm.

The file restore-point-config is renamed to startup-config. ETX2i
designates the previously active software pack as active, then reboots.
12-12 Restoring the Previous Version ETX2i

Chapter 13
Application Tutorial
This chapter provides configuration guidelines for setting up a typical E-Line
service.
The configuration activities presented in this chapter assume that ETX2i is
configured using a standard ASCII terminal, and that you are familiar with ETX2i
management as described in Chapter 6.
Figure 13-1 illustrates the application layout. Table 13-1 details a summary of
port connections.
Figure 13-1. E-Line Application
Ethernet Private Line (EPL) is implemented using a point-to-point EVC. All service
frames at the UNI are mapped to a single EVC.
The data traffic flow in the application behaves as follows (from left to the right):
1. PC transmits untagged packets, traffic enters ETX2i (1) User port #3.
2. ETX2i (1) adds VLAN ID 10 towards the network.
3. ETX-5 accepts only traffic with VLAN 10 in port 1/10 and forwards the
packets to port 1/20 in the same I/O card.
4. ETX2i (2) accepts only traffic tagged with VLAN 10, removes the VLAN, and
forwards the untagged packets to PC.
Table 13-1. Connection Summary
From Device/Port To Device/Port
ETX2i (1), port 3 PC network interface #2
ETX2i (1), port 1 ETX-5, port 1/10
ETX-5, port 1/20 ETX2i (2), port 1
ETX2i (2), port 3 PC network interface #3
ETX2i Equipment List 13-1

Chapter 13 Application Tutorial Installation and Operation Manual
13.1 Equipment List

Table 13-2 lists the devices required for the application.
Table 13-2. Required Equipment
Device Quantity
ETX2i (1) 1
ETX2i (2) 1
ETX-5 1
PC with application such as Ostinato that can 1
simulate traffic, and three network cards for
following:
Management (one network card)
Connect to simulate traffic (two network
cards)
13.2 Installing the Units

Before starting configuration, install the units as follows:
1. Configure PC network interface #1 with static IP address 172.17.192.10.
2. Connect PC network interface #2 to ETX2i (1) port 3.
3. Connect ETX2i (1) port 1 to ETX-5 port 1/10.
4. Connect ETX-5 port 1/20 to ETX2i (2) port 1.
5. Connect ETX2i (2) port 3 to PC network interface #3.
13.3 Configuring the E-Line Service

This section describes how to configure the E-Line service.
Configuring E-Line for ETX2i (1)

You need to create the following:
Outgoing data traffic from user to network:
Classifier profile that accepts traffic untagged (data traffic entering
ETX2i (1) from user port #3)
Flow named 3t1 from user port #3 to network port #1, using the above
profile, and adding VLAN 10 (with P-bit 0)
Incoming data traffic from network to user:
13-2 Configuring the E-Line Service ETX2i

Installation and Operation Manual Chapter 13 Application Tutorial
Classifier profile that accepts only traffic tagged with VLAN ID 10 (data
traffic entering ETX2i (1) from the network)
Flow named 1t3 from network port #1 to user port #3, using the above
profile, and removing the SP-VLAN
exit all
#*********** Create classifier profiles
configure flows
match untagged
exit

match vlan 10
exit
#*********** Create flows

flow 3t1
classifier untagged
no shutdown
exit
flow 1t3
classifier v10
vlan-tag pop vlan
no shutdown
exit all
save
Configuring E-Line ETX2i (2)

As the ETX2i units have the same configuration in this application, either repeat
the same commands listed in Configuring E-Line for, or copy the commands to a
script, transfer it to ETX2i (2), and run it.
Configuring E-Line for ETX-5

You need to create the following:
Queue group profile assigned to ports 1/10 and 1/20, and the ports enabled
SAG (service aggregation group) queue group profiles
Data traffic from port 1/10 to port 1/20:
Flow from port 1/10 to SAP
Flow from SAP to port 1/20
Data traffic from port 1/20 to port 1/10:
Flow from port 1/20 to SAP
ETX2i Configuring the E-Line Service 13-3

Flow from SAP to port 1/10

exit all
#*********** Configure Ethernet port queue groups
config port
ethernet 1/10
queue-group profile q_group_2_level_default
no shutdown
exit
ethernet 1/20
queue-group profile q_group_2_level_default
no shutdown
exit
#*********** Configure SAG queue group profiles

sag 1/1
queue-group profile q_group_SAG_2_level_default
exit
sag 1/2
queue-group profile q_group_SAG_2_level_default
exit all
#*********** Configure classifier profiles

configure flows
match vlan 10
exit

match all
exit
#*********** Configure flows

flow 10_sap
classifier v10
egress-port sap 1/1/2 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
flow sap_20
classifier all
ingress-port sap 1/1/2
egress-port eth 1/20 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
flow 20_sap
classifier v10
egress-port sap 1/2/2 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit
13-4 Configuring the E-Line Service ETX2i

configure flows flow sap_10

classifier all
ingress-port sap 1/2/2
egress-port eth 1/10 queue-map-profile QueueMapDefaultProfile block 0/1
no shutdown
exit all
save
13.4 Testing the Application
Checking E-Line Connectivity

To check the E-Line application, use the data traffic application on the PC to
verify the following:
Only untagged packets pass between CPEs.
Traffic passes from end to end between CPEs.
Checking Port/Flow Statistics

To check the statistics:
1. Connect ETX2i (0/3), and view user port #3 statistics.
2. Verify that counters are as expected according to the generated traffic rate
and type. The following shows an example of the statistics:
ETX2i Testing the Application 13-5

ETX2i# configure port ethernet 0/3

ETX2i>config>port>eth(0/3)# show statistics
--------------------------------------------------------------
Running
--------------------------------------------------------------
Rx Tx
Total Frames : 120368 40674
Total Octets : 182716280 61743132
Total Frames/Sec : 192 65
Total Bits/Sec (L2) : 2342512 791576

Unicast Frames : 120366 40674
Multicast Frames : 0 0
Broadcast Frames : 2 0
CRC Errors : 0 --
Error Frames : 0 --
L2CP Discarded : 0 --
OAM Discarded : 0 --
MTU Discarded : 0 56
Unknown Protocol Discarded : 0 --
CRC Errors/Sec : 0 --
Jabber Errors : 0 --
Oversize Frames : 0 0
64 Octets : 0 0
65-127 Octets : 0 0
128-255 Octets : 0 0
256-511 Octets : 0 0
512-1023 Octets : 0 0
1024-1528 Octets : 121575 41084
1519-2047 Octets : 0 0
2048-Max Octets : 0 0
3. View statistics for flow 3t1, and verify that counters are as expected
according to the generated traffic rate and type. The following shows an
example of the statistics:
13-6 Testing the Application ETX2i

ETX2i# configure flows flow 3t1

ETX2i>config>flows>flow(3t1)# show statistics running
-----------------------------------------------------------------------------
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 20000
Bytes : 20000000
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Red : 0 0
Yellow/Red : 0 0
Drop Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Red(Rate) : 0 0 0
Tx Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 197941 197941000
Green : 197941 197941000
Yellow : 0 0
Tx Rate
-----------------------------------------------------------------------------
Total(Rate) : 243 1947758 1800000
Green(Rate) : 243 1947758 1800000
Peak Measurement
-----------------------------------------------------------------------------
Tx Bit Rate [bps] : 0 0 1300 1252
Drop Bit Rate [bps]: 0 0 13000 121203
ETX2i Testing the Application 13-7

13-8 Testing the Application ETX2i

Appendix A
Connection Data
A.1 Alarm Relay Connector

The alarm relay dry contact interface terminates in a 9-pin Molex flat female
connector.
The following table lists the alarm relay pin assignments.
Table A-1. Alarm Relay Pinout
Pin Function
1 External alarm input
2 Major alarm relay

normally-open (NO) contact
3 Major alarm relay center

contact
4 Major alarm relay

normally-closed (NC) contact
5 +12V auxiliary output (through

1600 W series resistor)
6 Minor alarm relay

normally-open (NO) contact
7 Minor alarm relay center

contact
8 Minor alarm relay

normally- closed (NC) contact
9 Ground
A.2 Ethernet Connector

The Ethernet electrical interfaces terminate in 8-pin RJ-45 connectors, of type
10/100BaseT or 10/100/1000BaseT, wired in accordance with Table A-2. The
connector supports both MDI and MDIX modes.
ETX2i Ethernet Connector A-1

Appendix A Connection Data Installation and Operation Manual
Table A-2. 10/100/1000BaseT Connector Pinout
Pin MDI MDIX
1 A+ B+
2 A- B-
3 B+ A+
4 C+ D+
5 C- D-
6 B- A-
7 D+ C+
8 D- C-
A.3 E1/T1 Connector
Note This section is relevant only if an E1/T1 module was ordered.
The E1/T1 connectors terminate in four RJ-45 connectors. If four E1/T1 ports
were ordered, each connector provides one port; if eight E1/T1 ports were
ordered, each connector provides two ports. Table A-3 and Table A-4 list the pin
assignments.
Table A-3. E1/T1 Connector Pinout Four E1/T1 Ports
PIN Function Direction
1 RX Ring Input
2 RX Tip Input
3 NC NC
4 TX Ring Output
5 TX Tip Output
6 NC NC
7 NC NC
8 NC NC
Table A-4. E1/T1 Connector Pinout Eight E1/T1 Ports
Channels 14 Channels 58
PIN Function Direction Function Direction
1 RX Ring Input NC NC
2 RX Tip Input NC NC
A-2 E1/T1 Connector ETX2i

Installation and Operation Manual Appendix A Connection Data
Channels 14 Channels 58
PIN Function Direction Function Direction
3 NC NC TX Ring Output
4 TX Ring Output NC NC
5 TX Tip Output NC NC
6 NC NC TX Tip Output
7 NC NC RX Ring Input
8 NC NC RX Tip Input
Note
Do not connect wires to the NC pins.
A.4 CONTROL Connector

The CONTROL connector is a mini USB. The following table lists the CONTROL
connector pin assignments.
Table A-5. CONTROL Connector Pinout
Pin Name Function
1 N.A. -
2 TXD Transmit data
3 RXD Receive data
4 N.A. -
5 GND Ground
A.5 EXT CLK Connector
Note This section is relevant only if a timing option was ordered.
The station clock port terminates in an 8-pin RJ-45 connector, wired in

accordance with Table A-6.
Table A-6. EXT CLK Connector Pinout
Pin Direction Function
1,2 Input T3 (Input)
3 Not connected
ETX2i EXT CLK Connector A-3

Pin Direction Function
4,5 Output T4 (Output)
6, 7, 8 Not connected
A.6 MNG Connector

The ETX2i Ethernet management port terminates in an RJ-45, 8-pin connector
that supports MDI and MDIX modes. Table A-7 lists the pin assignments.
Table A-7. MNG Pinout
Pin Designation Function
1 RxD+ Receive Data output, + wire
2 RxD Receive Data output, wire
3 TxD+ Transmit Data input, + wire
4,5 Not connected
6 TxD- Transmit Data input, wire
7,8 Not connected
A.7 SHDSL Connector
Note This section is relevant only if an SHDSL module was ordered. One 8-pin RJ-45
connector is used for the 4-wire ordering option, and two 8-pin RJ-45 connectors
are used for the 8-wire ordering option. Each pin is wired as in the table below.
The SHDSL electrical interface is an 8-pin RJ-45 connector, wired in accordance

with Table A-8.
Table A-8. SHDSL Connector Pinouts
Pin Function
1 NC
2 NC
3 Loop 2
4 Loop 1
5 Loop 1
6 Loop 2
7 NC
A-4 SHDSL Connector ETX2i

Installation and Operation Manual Appendix A Connection Data
Pin Function
8 NC
Note Do not connect wires to the NC pins.
A.8 VDSL Connector
Note This section is relevant only for ETX2i with VDSL module.
The VDSL AIO electrical interface is made up of two 8-pin RJ-45 connectors one
connector for Loop 1 and Loop 2; the other for Loop 3 and Loop 4. Each
connector is wired in accordance with Table A-9.
Table A-9. VDSL Connector Pinout
Pin Function
1 NC
2 NC
3 Loop 2 / Loop 4
4 Loop 1 / Loop 3
5 Loop 1 / Loop 3
6 Loop 2 / Loop 4
7 NC
8 NC
Note Do not connect wires to the NC pins.
A.9 ToD/1PPS Connector
Note This section is relevant only for ETX2i if a PTP option was ordered.
The ToD/1PPS interface terminates in an RS-422 (half duplex) 8-pin RJ-45

connector. Table A-10 lists the pin assignments.
Table A-10. ToD/1PPS Connector Pinout
Pin Function
1 Option, NC
ETX2i ToD/1PPS Connector A-5

Pin Function
2 Option, NC
3 Tx/Rx 1PPS -
4 GND
5 GND
6 Tx/Rx 1PPS +
7 Tx/Rx TOD -
8 Tx/Rx TOD +
A-6 ToD/1PPS Connector ETX2i

Appendix C
Clock Selection and
Management (CSM)
Contents
Clock Selection and Management (CSM).................................................................................... C-1
C.1 Overview ..................................................................................................................... C-2
C.2 Terms and Definitions.................................................................................................. C-2
Timing loop .............................................................................................................. C-2
QL_minimum ............................................................................................................. C-2
Clock-Source Quality-Level ....................................................................................... C-2
Station Clock ............................................................................................................ C-3
Squelch .................................................................................................................... C-3
Synchronous Equipment Clock .................................................................................. C-3
C.3 Abbreviations .............................................................................................................. C-4
C.4 Standards Compliance ................................................................................................. C-6
C.5 CSM Features ............................................................................................................... C-7
C.6 CSM Structure Overview ............................................................................................... C-8
C.7 Detailed Description .................................................................................................... C-9
Clock Domains .......................................................................................................... C-9
Supported Physical Synchronization Interfaces ......................................................... C-9
Clock-Source Quality Levels (QL) Supported ........................................................... C-11
Synchronization Status Messages (SSM) ................................................................. C-15
CSM Selection Process ............................................................................................ C-21
Signal Fail ............................................................................................................... C-22
Hold-Off and Wait-to-Restore Delay Support ......................................................... C-23
Synchronization Source Priorities ........................................................................... C-24
External Commands ................................................................................................ C-25
Automatic Reference Selection Process .................................................................. C-26
Timing Loop Prevention .......................................................................................... C-27
Delay Times ............................................................................................................ C-30
ESMC Support ......................................................................................................... C-31
CSM State Machine ................................................................................................. C-33
C.8 CSM CLI Commands .................................................................................................... C-35
Clock Selection Module Commands ......................................................................... C-35
Clock Client Commands........................................................................................... C-36
Status and Statistics Commands............................................................................. C-36
ETX-2i Contents C-1

Appendix C Clock Selection and Management (CSM) Installation and Operation Manual
C.1 Overview
Note This appendix is applicable only to devices that contain an SEC/EEC clock module.
This appendix describes RADs clock selection and management SW module

version 1.55. The detailed functionality of this module is described as well as the
specific CLI commands that control it.
The specifications in this appendix apply to three regional standards bodies.
When different processing within a single function is required to support the
specific regional processing, this is identified by means of Options I, II and III
processing. "Option I" applies to networks optimized for the 2048 kbit/s
hierarchy. "Option II" applies to networks optimized for the 1544 kbit/s hierarchy.
"Option III" applies to networks optimized for the 1544 kbit/s hierarchy.
The SSM based clock selection algorithm specified in this appendix is only
generally applicable to SEC/EEC (Recommendation G.813 and G.8262) clock
equipment.
C.2 Terms and Definitions
Timing loop
This is a network condition where a slave clock providing synchronization
becomes locked to its own timing signal. It is generally created when the slave
clock timing information is looped back to its own input, either directly or via
other network equipments. Timing loops should be prevented in networks by
careful network design.
QL_minimum
QL_minimum is a user configurable parameter used in the squelching of clock
output signals. If the QL of the signal used to derive the output falls below
QL_minimum then the output is squelched (cut-off or set to AIS).
Clock-Source Quality-Level
The clock-source quality-level of a SEC or SASE is defined as the grade of clock to
which it is ultimately traceable; i.e. the grade-of-clock to which it is synchronized
directly or indirectly via a chain of SECs, and SASEs however long this chain of
clocks is. For example, the clock-source quality-level may be a Primary Reference
Clock complying with Recommendation G.811, or it may be a Slave Clock in
holdover-mode, complying with Recommendation G.812, or a Recommendation
G.813 or G.8262 Clock in holdover or free-run.
The clock-source quality-level is essentially, therefore, an indication only of the
long-term accuracy of the NE Clock.
C-2 Overview ETX-2i

Installation and Operation Manual Appendix C Clock Selection and Management (CSM)
Station Clock
This is a node clock as defined in Recommendation G.810.
The functional definitions are given in Recommendation G.783.
The symbols and diagrammatic conventions are given in Recommendation G.783.
Squelch
An action that cuts-off (i.e. shuts down) an output signal. For some signals
(e.g. 2 Mbit/s) squelching may be realized by means of inserting AIS, instead of
shutting down the signal.
Synchronous Equipment Clock

A generic term representing both the SDH Equipment Clock (G.813) and the
Ethernet Equipment Clock (G.8262).
ETX-2i Terms and Definitions C-3

C.3 Abbreviations
This appendix uses the following abbreviations:
AIS Alarm Indication Signal
BITS Building Integrated Timing Supply
CI Characteristic Information
CK Clock signal (Timing information)
CLR Clear
CS Clock Source (Timing information)
CSid Clock Source identifier
DNU Do Not Use
DUS Don't Use for Sync
ESF Extended Super Frame
ESMC Ethernet Synchronization messaging Channel
ESSM Ethernet Synchronization Status Messages
FSw Forced Switch
HO Hold Off time
HO HoldOver mode
ID IDentifier
LO Lockout
LO Locked mode
LOS Loss Of Signal
LSB Least Significant Bit
MSB Most Significant Bit
MSw Manual Switch
NE Network Element
NSUPP Not supported
PDH Plesiochronous Digital Hierarchy
PRC Primary Reference Clock
PRS Primary Reference Source
QL Quality Level
SASE Stand Alone Synchronization Equipment
SDH Synchronous Digital Hierarchy
SEC Synchronous Equipment Clock
SF Signal Fail
SMC SONET Minimum Clock
SQLCH Squelch
SSF Server Signal Fail
C-4 Abbreviations ETX-2i

SSM Synchronization Status Message

SSU Synchronization Supply Unit
SSU-A primary level SSU
SSU-B second level SSU
ST2 Stratum 2
ST3 Stratum 3
ST3E Stratum 3 Enhanced
ST4 Stratum 4
STM-N Synchronous Transport Module, level N
STU Synchronization Traceability Unknown
UNC UNConnected
UNK Unknown
WTR Wait to Restore
ETX-2i Abbreviations C-5

C.4 Standards Compliance

[1] ITU-T Recommendation G.703 (1998), Physical/electrical characteristics of hierarchical digital
interfaces
[2] ITU-T Recommendation G.704 (1998), Synchronous frame structures used at 1544, 6312,
2048, 8448 and 44 736 kbit/s hierarchical levels
[3] CCITT Recommendation G.706 (1991), Frame alignment and cyclic redundancy check (CRC)
procedures relating to basic frame structures defined in Recommendation G.704
[4] ITU-T Recommendation G.707 (1996), Network node interface for the synchronous digital
hierarchy (SDH)
[5] ITU-T Recommendation G.783 (1997), Characteristics of synchronous digital hierarchy (SDH)
equipment functional blocks
[6] ITU-T Recommendation G.803 (1997), Architecture of transport networks based on the
synchronous digital hierarchy (SDH)
[7] ITU-T Recommendation G.810 (1996), Definitions and terminology for synchronization
networks
[8] ITU-T Recommendation G.811 (1997), Timing characteristics of primary reference clocks
[9] ITU-T Recommendation G.812 (1998), Timing requirements of slave clocks suitable for use
as node clocks in synchronization networks
[10] ITU-T Recommendation G.813 (1996), Timing characteristics of SDH equipment slave
clocks (SEC)
[11] ITU-T Recommendation G.8261 (2006), Timing and synchronization aspects in packet
networks
[12] ITU-T Recommendation G.8262 (2007), Timing characteristics of Synchronous Ethernet
Equipment slave clock (EEC)
[13] ITU-T Recommendation G.8264 (2008), Distribution of timing through packet networks
[14] IEEE Standard 802.3 TM -2005, Part3, CSMA/CD access method and physical layer
specifications
[15] DS3102 Stratum 3 Timing Card IC with Synchronous Ethernet Support data sheet
C-6 Standards Compliance ETX-2i

C.5 CSM Features

The clock selection & management SW module described in this appendix is
integrated in every RAD device that comprises an SEC/EEC clock module and
constitutes the upper SW control and management plane for such modules. It is
largely based on the ITU-T G.781 standard and presents the following features:
(1) Selects the best synchronization reference for the equipment system clock
among a group of assigned synchronization sources (physical or higher-layer
ports).
(2) Accepts legitimate user preferences and acts accordingly.
(3) Controls the different clock routing HW modules such as the assigned
synchronization references HW MUXs and the main clock processing HW
(central timing module).
(4) Supports input clock synchronization frequency and activity monitoring.
(5) Only one clock domain is supported per SW module.
(6) Manages all SSM processing in the equipment (QL interception and
generation).
(7) Supports timing loop prevention.
(8) Supports QL-enabled and QL-disabled modes of operation.
(9) Supports option I, II, and III regional requirements (only one option is
supported at a time according to user configuration).
(10) Supports CLI and SNMP management.
ETX-2i CSM Features C-7

C.6 CSM Structure Overview

RAD CSM general block diagram is shown in Figure C-1. RAD CSM General Block
Diagram
RAD CSM is basically comprised of five major components:
A SEC/EEC clock module implemented in HW.
Data ports HW based on the specific product attributes. The data ports can
be legacy TDM/SDH or more modern Synchronous Ethernet capable Ethernet
ports (FE/GE).
Logical higher layers clock distribution scheme ports (e.g. PTP) that can be
used either as a synchronization source to the CSM (e.g. output of a PTP
slave) or as an outgoing synchronization source from the CSM (e.g. input to a
PTP master). (Not shown in the figure below).
A dedicated external clock input/output port HW. This port can be either a
standard E1/T1 port (dedicated for sync) or an analog 2.048MHz port (T12).
A CSM control SW that controls the various HW components and the clock
selection process based on ITU-T Recommendation G.781
Figure C-1. RAD CSM General Block Diagram
RAD CSM can support up to eight synchronization sources (including the T3

external input clock interface) simultaneously supplied to the SEC/EEC input clock
interfaces. Based on the control CSM SW configuration the SEC/EEC performs the
physical clock selection, hitless switching, filtering and holdover. The SEC/EEC HW
comprises two internal DPLL blocks (not shown in the figure) dedicated for the
T0 (system clock) and T4 (external clock) output interfaces. The T0 output
interface is used to frequency lock the outgoing data links and possibly a higher-
layer clock distribution function (e.g. PTP master), while the T4 output interface is
used to frequency lock the external clock output port.
C-8 CSM Structure Overview ETX-2i

The CSM control SW runs all the G.781 based attributes such as the clock
selection algorithms, external user commands etc. It receives and transmits
Quality Level (QL) and Server Signal Fail (SSF) information from/to the relevant
data and external clock ports. It is also responsible for correctly configuring the
SEC/EEC according to the relevant standards and user preferences (e.g. G.8262
option I).
C.7 Detailed Description
Clock Domains
The CSM module supports one clock domain (one primary long-term frequency
source) only. In products that require to support multiple clock domains (e.g. to
support multiple service providers, each having its own primary long-term
frequency source), multiple instances of the CSM module are required.
The clock domain ID shall be configured by the user using the following CLI
command:
configure >system>clock> domain <id> // <id> - domain number
Supported Physical Synchronization Interfaces

Synchronization trails can be carried through the network by a number of
interfaces. The following physical synchronization interfaces are supported:
Option I Synchronization Networking

Traffic interfaces:
2048 kHz (T12) 1;
2048 kbit/s (E12+P12s)
Dedicated sync interfaces:
155 520 kbit/s (OS1 (or ES1)+RS1+MS1);
2048 kbit/s (E12+P12s)
100 000 kbit/s (ETY2[+ETH])
1 000 000 kbit/s (ETY3[+ETH])
10 000 000 kbit/s (ETY4[+ETH])
Note
ETYn synchronization interfaces are full duplex with continuous bit stream, as
specified in G.8262.
Option II Synchronization Networking

Traffic interfaces:
1
For more information regarding the terms in brackets see ITU-T
G.703/G.704/G.781.
ETX-2i Detailed Description C-9

1544 kbit/s (E11+P11s);

155 520 kbit/s (OS1 (or ES1)+RS1+MS1);
1544 kbit/s (E11+P11s)
1 000 000 kbit/s (ETY3[+ETH])
10 000 000 kbit/s (ETY4[+ETH])
Note
specified in G.8262.
Option III Synchronization Networking

Traffic interfaces:
155 520 kbit/s (OS1 (or ES1)+RS1+MS1)
1 000 000 kbit/s (ETY3[+ETH])
10 000 000 kbit/s (ETY4[+ETH])
Note
specified in G.8262
STM-N
The STM-N transport signals carry (in addition to the payload) reference timing
information and an indication of the quality level of the source generating this
timing information, via the Synchronization Status Message (SSM) as defined in
Recommendation G.707.
2 Mbit/s (E1)
The 2 Mbit/s transport signals may carry (in addition to the payload) reference
timing information.
The 2 Mbit/s timing reference signals (without payload) carry reference timing
information to specific synchronization ports.
Both signals can carry an indication of the quality level of the source generating
the timing information via the SSM as specified in Recommendation G.704.
2 MHz (T12)
Synchronization can be carried through 2 MHz signals to specific synchronization
ports (so called station clock ports). This signal does not carry an indication of
the quality level of the source generating the timing information.
1.5 Mbit/s (T1)

The 1.5 Mbit/s transport signals may carry (in addition to the payload) reference
timing information.
The 1.5 Mbit/s timing reference signals (without payload) carry reference timing
information to specific synchronization ports.
C-10 Detailed Description ETX-2i

Both signals can carry an indication of the quality level of the source generating
the timing information via the SSM transported within the 1544 kbit/s signal's
Extended Super Frame (ESF) Data Link (DL) as specified in Recommendation
G.704.
100 Mbit/s, 1 Gbit/s, 10 Gbit/s

The 802.3 transport signals may carry (in addition to the payload) reference
timing information and an indication of the quality level of the source generating
this timing information, via the Synchronization Status Message (SSM) as defined
in ITU-T Recommendation G.8264.
Notes Equipment developed prior to this first revision of the Recommendation may
not be able to carry reference timing information and/or support SSM via its
802.3 interfaces
The equipment can have both nonsynchronous and synchronous 802.3
interfaces as defined in G.8264. Nonsynchronous 802.3 interfaces are
excluded from the synchronization distribution process
The relevant synchronization input/output ports (type and ID) that are to take
part in the clock selection process are user configured using the following CLI
command:
configure >system>clock>domain (id)#[no] source <src-id> {type}
[<id>] [{port type} <port-index>]
// type - {domain <domain-id>| rx-port {port-type}
<port-index>| station <station-id> | recovered
<recovered-id>}.
// rx-port {port-type} - E1, T1, Ethernet, SDH/SONET.
Note
For further details regarding the specific CLI structure, refer to Chapter 4
Clock-Source Quality Levels (QL) Supported
Clock-Source Quality-Level Definitions

SDH and packet transport networks throughout the world are based on different
synchronization philosophies. Those differences are identified as three Options: I,
II, and III in the relevant standards and are all supported by the CSM SW module.
The relevant network option shall be configured by the user using the following
CLI command:
configure >system>clock>domain (id)# sync-network { type-1 | type-2 | type-3 }
// default type-2A change in the sync-network Type configuration can only take
place if no clock sources are configured. An attempt to change the sync-network
Type when one or more clock sources are configured in the system result in the
following error message:
Existing sources should be removed first
Thus, before changing the sync-network Type, the user must delete all configured
clock sources.


The following clock source quality levels are defined in the CSM synchronization
process of Option I network corresponding to 4 levels of synchronization quality
(based in ITU-T Recommendation G.803).
QL-PRC This synchronization trail transports a timing quality

generated by a Primary Reference Clock that is
defined in Recommendation G.811.
QL-SSU-A This synchronization trail transports a timing quality
generated by Types I or V slave clock that is defined
in Recommendation G.812.
QL-SSU-B This synchronization trail transports a timing quality
generated by a Type VI slave clock that is defined in
QL-SEC This synchronization trail transports a timing quality
generated by a Synchronous Equipment Clock (SEC)
that is defined in Recommendation G.813 or G.8262,
Option I.
QL-DNU This signal should not be used for synchronization.

Clock source quality levels of Option II networks have been expanded from 7
levels to 9 levels. The 7 quality level set is referred to as First generation and the
new 9 quality level set is referred to as Second generation. First generation
quality levels are a subset of Second generation.
Note RAD equipment is always defined as second generation equipment.
The following clock source quality levels are defined in the CSM synchronization
selection process of Option II network corresponding to Second generation.
QL-PRS PRS traceable (Recommendation G.811)
QL-STU Synchronized Traceability Unknown
QL-ST2 Traceable to Stratum 2 (Recommendation G.812, Type II)
QL-TNC Traceable to Transit Node Clock (Recommendation G.812, Type V)
QL-ST3E Traceable to Stratum 3E (Recommendation G.812, Type III)
QL-ST3 Traceable to Stratum 3 (Recommendation G.812, Type IV)
QL-SMC Traceable to SONET Clock Self Timed (Recommendation G.813 or
G.8262, Option II)
QL-ST4 Traceable to Stratum 4 Freerun (only applicable to 1.5 Mbit/s
signals)
QL-PROV Provisionable by the Network Operator
QL-DUS This signal should not be used for synchronization.

The following clock source quality levels are defined in the synchronization
process of Option III SDH network corresponding to 2 levels of synchronization
quality.

QL-UNK This synchronization trail transports a timing quality

generated by an unknown clock source. It is at least of
quality SSU.
QL-SEC This synchronization trail transports a timing quality
generated by a Synchronous Equipment Clock (SEC) that is
defined in ITU-T Recommendation G.813 or G.8262, Option I.
External Synchronization Interface Output (T4) Squelching

The CSM module supports squelching of the external synchronization interface
output. The first purpose of the "squelch" function is to prevent transmission of
a timing signal with a quality that is lower than the quality of the clock in the
receiving network element or SASE. It is also used for the prevention of timing
loops.
Squelching is done according to the user configured QL_minimum value, by
comparing this user configured value to the reported quality level of the current
selected synchronization source.
Note Squelching (signal cutoff) is applicable only for 2.048 MHz (T12) clock interfaces.
In case 2.048 Kb/s (E1) or 1.544 Kb/s (T1) are used, upon a squelching event
the interface would start transmitting AIS.
Supported Hierarchy of Clock-Sources Quality Levels (QL)

The following tables define the QL hierarchy.
Table C-1. Hierarchy of quality levels in Option I
Quality Level Order
QL-PRC highest
QL-SSU-A |
QL-SSU-B |
QL-SEC |
QL-DNU |
QL-INVx, -FAILED, -UNC, -NSUPP lowest
Note
The quality levels QL-INVx, QL-FAILED, QL-UNC and QL-NSUPP are internal QLs
inside the NE and are never generated at an output port.

Table C-2. Hierarchy of quality levels in Option II
Quality Level Order
QL-PRS highest
QL-STU |
QL-ST2 |
QL-TNC (See note) |
QL-ST3E (See note) |
QL-ST3 |
QL-SMC |
QL-ST4 |
QL-PROV (default position) |
QL-DUS |
Note
The quality level QL-PROV is provisionable by the network operator and may take
different order positions. The default position for QL-PROV is as shown in
Table C-2.
Note The implementation in RAD CSM always assumes this default position for
QL-PROV.
Table C-3. Hierarchy of quality levels in Option III
Quality Level Order
QL-UNK highest
QL-SEC |
Note
Forcing and Defaulting Clock-Source Quality-Levels

For synchronization source signals/interfaces not supporting SSM
transport/processing, it is possible to force the quality level to a fixed provisioned

value. This allows using these signals/interfaces as synchronization sources in an

automatic reference selection process operating in QL-enabled mode.
Forcing of quality levels is used for new equipment operating in QL-enabled mode
in order to:
Interwork with old equipment not supporting SSM generation
Interwork with new equipment operating in QL-disabled mode
Select interfaces not supporting SSM processing
Select signals for which SSM is not defined (e.g. 2 MHz)
Note Valid SSM synchronization sources can also be overwritten using the Force QL
procedure.
In RAD CSM, when working in QL-enabled mode, the user must configure (force)
a specific QL level for all the ingress synchronization interfaces (assigned sync
sources) that does not support SSM (outputting the default QL-NSUPP).
A synchronization source issuing signal fail (SSF) cannot be QL overwritten by
user configuration (QL_FAILED is always distributed to the selection algorithm).

The quality level of the input signal (STM-N, 2 Mbit/s, 2 MHz) can be forced to
either QL-PRC, QL-SSU-A, QL-SSU-B or QL-SEC.

The quality level of the input signal can be forced to either QL-PRS, QL-STU,
QL-ST2, QL-TNC, QL-ST3E, QL-ST3, QL-SMC, QL-ST4, QL-PROV or QL-DUS.

The quality level of the input signal can be forced to either QL-UNK or QL-SEC.
Synchronization Status Messages (SSM)

The following supported signals have a four-bit SSM channel defined:
STM-N (N = 1, 4, 16) bits 5 to 8 of the byte S1 (called SSMB,
Synchronization Status Message Byte) of the multiplex section overhead as
defined in Recommendation G.707
2 Mbit/s octet structured according to Recommendation G.704: bits Sax1 to

Sax4 (x = 4, 5, 6, 7, or 8) of TS0
1.5 Mbit/s octet structured according to 2.1/G.704
100 Mbit/s, 1 Gbit/s, 10 Gbit/s as defined in IEEE Std. 802.3: 4-bit SSM field in
the SSM PDU as defined in Recommendation G.8264
SSM Message Sets

Five SSM codes are defined to represent clock source QL as listed below:

Code 0010 (Quality PRC) means that the source of the trail is a PRC clock
(Recommendation G.811).
Code 0100 (Quality SSU-A), means that the source of the trail is a Type I or V
SSU clock as defined in Recommendation G.812.
Code 1000 (Quality SSU-B), means that the source of the trail is a Type VI
SSU clock (Recommendation G.812).
Code 1011 (Quality SEC), means that the source of the trail is a SEC clock
(Recommendation G.813 or G.8262, Option I).
Code 1111 (quality DNU), means that the signal carrying this SSM shall not be
used for synchronization because a timing loop situation could result if it is
used.

Nine SSM codes are defined to represent clock source QL as listed below on STM-
N signals:
Code 0001 (Quality PRS) means that the source of the trail is a PRS clock
Code 0000 (Quality STU) means that the signal does not carry the QL
message of the source of the trail.
Code 0111 (Quality ST2), means that the source of the trail is a Stratum 2
clock (Recommendation G.812, Type II).
Code 0100 (Quality TNC), means that the source of the trail is a Transit Node
Clock (Recommendation G.812, Type V).
Code 1101 (Quality ST3E), means that the source of the trail is a stratum 3E
clock (Recommendation G.812, Type III).
Code 1010 (Quality ST3), means that the source of the trail is a stratum 3
clock (Recommendation G.812, Type IV).
Code 1100 (Quality SMC), means that the source of the trail is a
SONET/Ethernet self timed clock (Recommendation G.813 or G.8262, Option
II).
Code 1110 (Quality PROV), is provisionable by the network operator.
Code 1111 (Quality DUS), means that the signal carrying this SSM shall not be
used.
Ten SSM codes are defined to represent clock source QL as listed below on
1544 kbit/s signals:
Code 04FFH (Quality PRS) means that the source of the trail is a PRS clock
Code 08FFH (Quality Unknown) means that the source of the trail is unknown.
Code 0CFFH (Quality ST2) means that the source of the trail is a Stratum 2
clock (Recommendation G.812, Type II).
Code 78FFH (Quality TNC) means that the source of the trail is a Transit Node
Clock (Recommendation G.812, Type V).

Code 7CFFH (Quality ST3E) means that the source of the trail is a Stratum 3E
clock (Recommendation G.812, Type III).
Code 10FFH (Quality ST3) means that the source of the trail is a Stratum 3
clock (Recommendation G.812, Type IV).
Code 22FFH (Quality SMC) means that the source of the trail is a
SONET/Ethernet self-timed clock (Recommendation G.813 or G.8262, Option
II).
Code 28FFH (Quality ST4) means that the source of the trail is a Stratum 4
clock.
Code 40FFH (Quality PROV) is provisionable by the network operator.
Code 30FFH (Quality DUS) means that the signal carrying this SSM shall not be
used.

Two SSM codes are defined to represent clock source QL as listed below:
Code 0000 (Quality Unknown) means that the source of the trail is unknown.
Code 1011 (Quality SEC) means that the source of the trail is a SEC clock
(Recommendation G.813 or G.8262, Option I).
SSM Code Word Generation (SSM Tx Function)

The SSM can be viewed as an application specific data communication channel
with a limited message set. The message is generated and inserted depending on
the applied selected reference quality level indication. The following tables
present the relation between the existing set of QLs and SSM codes generation
for the three options.
In the CSM module it is possible to disable the SSM Tx function , generation and
inserting "1111", independently for each interface. An application for this could
be e.g. at network boundaries where timing information should not be forwarded
to the other network.
Note SSM disable for an Ethernet port causes it to stop transmitting ESMC frames.
Table C-4. Quality Level Set and Coding in Synchronization Status Message in Option I
Synchronization Networks
Quality Level (QL) SSM usage SSM coding [MSB..LSB]
QL-PRC enabled 0010
QL-SSU-A enabled 0100
QL-SSU-B enabled 1000
QL-SEC enabled 1011
QL-DNU enabled 1111

disabled 1111
Table C-5. Quality Level Set and Coding in Synchronization Status Message in Option II
Quality SSM usage Second Generation SSM

Level (QL)
SSM SSM
coding [MSB..LS coding [MSB..LS
B] in STM-N B] in 1544
signal kbit/s signal
(BINARY) with ESF (HEX)
QL-PRS enabled 0001 04FF
QL-STU enabled 0000 08FF
QL-ST2 enabled 0111 0CFF
QL-TNC enabled 0100 78FF
QL-ST3E enabled 1101 7CFF
QL-ST3 enabled 1010 10FF
QL-SIC enabled 1100 22FF
QL-ST4 enabled 28FF
QL-PROV enabled 1110 40FF
QL-DUS enabled 1111 30FF
disabled 1111 08FF
Table C-6. Quality Level Set and Coding in Synchronization Status Message in Option III
Quality Level (QL) SSM coding [MSB..LSB]
QL-UNK 0000
QL-SEC 1011
SSM Code Word Interpretation (SSM Rx Function)

At the receive side, the received SSM bits are to be validated by a persistency
check and then interpreted to determine the QL.

Table C-7. Interpretation of Synchronization Status Message Codes in Option I Synchronization

Networks
SSM code [MSB..LSB] QL interpretation
0000 QL-INV0
0001 QL-INV1
0010 QL-PRC
0011 QL-INV3
0100 QL-SSU-A
0101 QL-INV5
0110 QL-INV6
0111 QL-INV7
1000 QL-SSU-B
1001 QL-INV9
1010 QL-INV10
1011 QL-SEC
1100 QL-INV12
1101 QL-INV13
1110 QL-INV14
1111 QL-DNU
Table C-8. Interpretation of Synchronization Status Message Codes in STM N Signals in Option II
SSM code [MSB..LSB] in STM-N signals QL interpretation
0000 QL-STU
0001 QL-PRS
0010 QL-INV2
0011 QL-INV3
0100 QL-TNC
0101 QL-INV5
0110 QL-INV6
0111 QL-ST2
1000 QL-INV8

SSM code [MSB..LSB] in STM-N signals QL interpretation
1001 QL-INV9
1010 QL-ST3
1011 QL-INV11
1100 QL-SMC
1101 QL-ST3E
1110 QL-PROV
1111 QL-DUS
Table C-9. Interpretation of Synchronization Status Message Codes in 1544 kbit/s Signals in Option
II Synchronization Networks
SSM code in 1544 kbit/s signals QL interpretation
0xxx xxx0 1111 1111 HEX --
000 010 04FF QL-PRS
000 100 08FF QL-STU
000 110 0CFF QL-ST2
111 100 78FF QL-TNC
111 110 7CFF QL-ST3E
001 000 10FF QL-ST3
010 001 22FF QL-SMC
010 100 28FF QL-ST4
011 000 30FF QL-DUS
100 000 40FF QL-PROV
other (see Note 1) other (see Note 1) QL-INV
Table C-10. Interpretation of Synchronization Status Message Codes in Option III Synchronization
Networks
0000 QL-UNK
0001 QL-INV1
0010 QL-INV2
0011 QL-INV3
0100 QL-INV4
0101 QL-INV5

0110 QL-INV6
0111 QL-INV7
1000 QL-INV8
1001 QL-INV9
1010 QL-INV10
1011 QL-SEC
1100 QL-INV12
1101 QL-INV13
1110 QL-INV14
1111s QL-INV15
Note
Interworking between Option I and II, Option I and III and Option II and III
synchronization networks is not defined.
CSM Selection Process

The process of selecting a synchronization source from the set of physical ports
is performed in three steps plus one for use of the station clock output:
Figure C-2. Visualization of the Synchronization Source Selection Process(Es)
1. Assignment of a physical port to be a synchronization source: Select a

(limited) set of interface signals (from the total set of interfaces) to act as
synchronization sources. This is performed by means of adding a fixed (not
changing during runtime) physical mapping between a group of inputs
(connected to the transport layer) and outputs (connected to the SEC/EEC
device). This functionality is usually realized by HW MUXs that are SW

managed according to user preferences. Generally speaking, only the

assigned synchronization sources take part in the automatic selection
process. In other words, a synchronization source that has not been mapped
into the assigned group of sources, cannot be used as a synchronization
reference.
2. Nomination of a synchronization source for an automatic selection process:
Select a subset of the synchronization sources to contribute to a selection
process. This is performed in the CSM by means of assigning a priority to the
synchronization source. Under any circumstance, the T3 synchronization
source cannot be nominated for T4 selection process.
3. Automatic Selection Process: Selects the "best" synchronization source of the
set from nominated sources according to the selection algorithm. Two
independently selection process for T0 and T4 are being carried.
Signal Fail
RAD CSM supports three levels (or sources) of signal fail triggering:
1. Signal fail for a synchronization source is activated in case of defects
detected in the transport layers. In addition an unconnected synchronization
signal has also signal fail active in order to allow correct processing in the QL
disabled mode.
2. Inclusion of specific synchronization failures conditions based on dedicated
detection mechanism embedded within the SEC/EEC device are also
supported. More specifically, RADs SEC/EEC implementation is capable of
detecting a large frequency deviation, beyond a pre-configured threshold, as
well as lack of activity on each one of the assigned synchronization sources.
Those alarm indications are also used to issue a Server Signal Fail (SSF) signal
towards the CSM.
An SSF signal is issued by the SEC/EEC HW in the following cases:
Activity alarm (leaky bucket mechanism). The configuration of the activity
detector is fixed and preconfigured for all RAD products.
10,000 ppm coarse frequency monitoring (fixed for all RAD products).
User configured HARD limit frequency monitoring. The user can configure
a HARD frequency limit within the range of 3.81 ppm to 60.96 ppm in
0.01 ppm steps using the following CLI command:
configure >system>clock>domain (id)># max-frequency-deviation
<value>
3. Synchronous Ethernet ports that fail to receive a valid ESMC message
immediately for a period of 5 seconds, issue a signal fail indication.
In order to avoid reactions on short pulses or intermittent signal fail information,
the signal fail information is passed through a hold-off and wait-to-restore
processes before it is considered by the selection process.
In QL enabled mode the QL of a synchronization source with active signal fail is
set to QL-FAILED. The selection process reacted to this QL value instead of the
signal fail signal in this mode.

When it comes to the user failure indications for a specific clock source, the
priority of presenting the specific SSF event cause is as follows:
1. A problem reported by the PHY (physical-fail)
2. Violation of the HARD frequency limit (monitoring-fail)
3. Lack of ESMC messages reception (if the interface is an Ethernet one) (esmc-
fail)
In other words, a violation of the HARD frequency limit would mask a concurrent
ESMC messages timeout indication. A problem reported from the PHY would mask
both concurrent HARD frequency violation and ESMC messages timeout
indications.
It should be stressed again that only the user indication would be masked, not
the actual failure signal (SSF). Moreover, new versions of CSM support
dedicated/independent user indications for each cause.
Hold-Off and Wait-to-Restore Delay Support
Hold-Off Time
The hold-off time ensures that short activation of signal fail is not passed to the
selection process.
In QL-disabled mode signal fail is active for the hold-off time before it is passed
to the selection process.
In QL-enabled mode a QL value of QL-FAILED exists for the hold-off time before it
is passed to the selection process. In the mean time the previous QL value is
passed to the selection process.
Note Other QL values than QL-FAILED are passed to the selection process immediately.
Separate hold-off timers are used for each input to a selection process
(nominated source). The hold-off time is user configured within the range of 300
ms to 1800 ms using the following CLI command:
configure >system>clock>domain (id)> source (src-id)# hold-off
<seconds>
Wait-to-Restore Time
The wait to restore time ensures that a previous failed synchronization source is
only again considered as available by the selection process if it is fault free for a
certain time.
In QL-disabled mode after deactivation of signal fail, it remains false for the wait
to restore time before signal fail false is passed to the selection process. In the
meantime, signal fail true is passed to the selection process.
In QL-enabled mode after a change of the quality level from QL-FAILED to any
other value, the quality value QL-FAILED is maintained for the wait to restore
time before the new QL value is passed to the selection process. In the
meantime, the quality level QL-FAILED is passed to the selection process.

Separate wait to restore timers are used for each input to a selection process
(nominated source).
The wait to restore time is user configurable (user configuration) in the range of
0 to 12 minutes in steps of 1 minute for all inputs of the selection process in
common using the following CLI command. The default value is 5 minutes.
configure >system>clock>domain (id)> source (src-id)#
wait-to-restore <seconds>
Each wait to restore timer can be cleared with a separate (user) Clear command
using the CLI command shown below. If a wait to restore timer is cleared the new
QL value (in QL-enabled mode), or signal fail value (in QL-disabled mode), is
immediately passed to the selection process.
configure >system>clock>domain (id)> source (src-id)#
wait-to-restore-clear //command
A new WTR state status was added to the source/show status command to
give the user more clarity regarding the current WTR state of each
synchronization source.
configure >system>clock>domain (id)> source (src-id)# show status
.
.
.
WTR State : { Inactive | Running }
Synchronization Source Priorities

In order to define a preferred network synchronization flow, priority values are
allocated to assigned synchronization sources within a network element (see
Table C-11).
Different priorities reflect a preference of one synchronization source over the
other. Equal synchronization source priorities reflect that no preference exists
between the synchronization sources.
Within the group of synchronization sources with equal priorities, the selection
process has a non-revertive behavior.
Table C-11. Priority Order
Priority value Order
1 highest
2 |
3 |
: |
K lowest
Disable (no priority) Cannot be used for

clock selection T0/T4

Notes The priority value is not ordered numerically. The following relation is present:
"1" > "2" > "3" > .. >"K"
The assigning of equal priorities to synchronization sources, in order to allow
for non-revertive operation, does not allow for a predefined initialization state
of known synchronization configuration following failure of a higher priority
source.
The CSM synchronization source ports priority is configured by the user using the
following CLI command:
configure >system>clock>domain (id)> source (src-id)#no
priority <num> ock-
// If no option is chosen, then this source is not taken to the
selection process
External Commands
Several external commands are available to the user via the products
management level (e.g. for maintenance purposes). These commands are
independent and have different impact on the selection processes.
The activation and deactivation of external commands associated with the
synchronization selection process are defined below. Furthermore, only one of
these external commands is active at a time as per the selection process.
Clear Command
A clear (CLR) command clears the forced switch and manual switch commands.
Forced Switch #p Command

A forced switch (FSw) to #p command can be used to override the currently
selected synchronization source, assuming the synchronization source #p is
enabled.
The forced switch overrides the manual switch and a subsequent forced switch
pre-empts the previous forced switch.
If the source selected by the forced switch command (#p) is disabled (using the
no priority command), the forced switch command is automatically rejected. The
forced switch command can be cleared by the "clear" command.
Note A forced switch command to a synchronization source #p, which is in the SF state
or has a QL of DNU in QL enabled mode, results in the network element entering
holdover.
A new Force switch state status was added to the domain/show status
command to give the user more clarity regarding the current Force switch state
of the clock domain.
configure >system>clock>domain (id) # show status
.
.
.
Force Switch: {InActive | Active}

Manual Switch #p Command

A manual switch (MSw) to #p command selects the synchronization source #p,
assuming it is enabled, not in signal fail condition, and has a QL better than DNU
in QL enabled mode. Furthermore, in the QL enabled mode, a manual switch can
be performed only to a source which has the highest available QL. As such, these
conditions have the effect that manual switching can only be used to override the
assigned synchronization source priorities.
A manual switch request overrides a previous manual switch request.
If the source selected by the manual switch command (#p) is in signal fail, or has
a QL of DNU or lower than one of the other source signals, the manual switch
command is automatically rejected.
The manual switch command can be cleared by the "clear" command.
The following CLI commands allow the user to impose external commands on the
CSM:
configure >system>clock>domain (id)# force < source-id >
configure >system>clock>domain (id)# manual < source-id >
configure >system>clock>domain (id)# clear
The Manual switch state status is available under the domain/show status
command to give the user more clarity regarding the current Manual switch
state of the clock domain.
.
.
.
Manual Switch: {InActive | Active}
Force T4=T0 Set Command

Activating the Force T4 to T0 command deactivates the T4 DPLL and uses the T0
DPLL to feed both the T0 and T4 output clock paths.
configure >system>clock>domain (id)# [no] force-t4-as-
t0 //project dependent
Automatic Reference Selection Process

One or more reference selection processes operate independently to select the
reference signal for the internal (system) clock (T0) and, where present, the
station clock output(s) (T4).
The selection process(es) can work in two distinct modes: QL-enabled or
QL-disabled. If multiple selection processes are present in a network element, all
processes work in the same mode.
The following is a brief description of the automatic reference selection process.
The relevant QL mode shall be configured by the user using dedicated CLI
commands. To switch the CSM into QL-disabled mode the following CLI command
shall be used:
configure >system>clock>domain (id)# no quality

To switch the CSM back into QL-enabled mode the following CLI command should
be used. Through this CLI command the user also configures the QL_minimum
level used for the T4 squelching mechanism.
configure >system>clock>domain (id)# quality min-level {level}
QL-enabled Mode
In QL-enabled mode the following parameters contribute to the selection
process:
Quality Level
Signal fail via QL_FAILED
Priority
External commands
If no overriding external commands are active, the algorithm selects the reference
with the highest quality level, which is not experiencing a signal fail condition. If
multiple inputs have the same highest quality level, the input with the highest
priority is selected. For the case that multiple inputs have the same highest
priority and quality level, the current existing selected reference is maintained if it
belongs to this group, otherwise an arbitrary reference from this group is
selected.
If no input could be selected, the CSM moves the SEC/EEC to holdover state while
distributing the internal oscillator QL level towards the output synchronization
interfaces (T4 immediately moves to squelch mode).
QL-disabled Mode
In QL-disabled mode the following parameters contribute to the selection
process:
Signal fail
Priority
External commands
If no overriding external commands are active, the algorithm selects the reference
with the highest priority which is not experiencing a signal fail condition. For the
case that multiple inputs have the same highest priority, the current existing
selected reference is maintained if it belongs to this group, otherwise an arbitrary
reference from this group is selected.
If no input could be selected, the CSM moves the SEC/EEC to holdover state (T4
immediately moves to squelch mode).
Timing Loop Prevention

Timing loops are formed when a clock is traceable to itself. Such a situation can
develop when the synchronization distribution flow in the network losses its pure
tree-like topology, due to an erroneous distribution configuration, and a timing
circle is formed.
Synchronization network architectures should be designed such that timing loops
do not occur under fault free or failure conditions. Special timing loop prevention

techniques should be used within network elements and SASEs that might open
the potential loop. Some of these are described hereafter that affect the
synchronization distribution functionality within a product.
Between RAD CSM and Network Elements with SEC/EEC Type

Clock
The master-slave synchronization over several NEs with multiple possible
synchronization inputs for protection of synchronization as defined in ITU-T
Recommendation G.803 could lead to timing loops between NEs. To avoid timing
loops the CSM module would insert a SSM value of DNU in direction of the NE
which is used as actual synchronization source for the CSM.
NEx NEy NEz

MI_CSid=1 MI_CSid=3
SSM=0010 input CI_CS=1 CI_CS=3 input
RI_CS=1 RI_CS=3
do not use as SSM=1111 CI_CS=1 CI_CS=1 SSM=0010 can be used as
synchronization output output synchronization
source source
transport MI_CSid=2 MI_CSid=4 transport
ports ports
input input
RI_CS=2 RI_CS=4
SSM=0010 CI_CS=1 CI_CS=1 SSM=0010
output output
T1530620-99
Figure C-3. RAD CSM Automatic DNU Generation Towards NE with SEC/EEC Timing
The clock source identifier CSid has been introduced to support the above feature
as shown in Figure C-3. To each transport and station clock input port a unique
CSid is assigned. This ID is processed in the CSM together with the clock and
quality level of the port. The CSid of the selected source for the SEC/EEC is
distributed to all output ports. If a transport output port receives the same CSid
as its associated input port the outgoing is set to DNU.
Between RAD CSM and NE or SASE/BITS with a SSU/ST2 Clock

RADs product can be interconnected with SASE/BITS via its (2 MHz, 2 Mbit/s,
1.5 Mbit/s) station clock input and output ports (unidirectional). If the SASE/BITS
is used as the actual synchronization source for RAD CSM, the mechanism
defined above has to be extended to support automatic DNU insertion also for
this case.
It is not possible to detect that the SASE/BITS has selected the station clock
output port of the NE as actual clock source, but several conditions exist that
indicate that the station clock output port is not used as clock source by the
SASE/BITS.
If a RAD CSM is connected to a SASE/BITS that does not process QL/SSM
information, a squelched/AIS station clock output port is the only criteria that
indicates that the output port is not used as clock source by the SASE/BITS. As
long as the station clock output is not squelched (for 2 MHz station clock ports)
or set to AIS (for 2 Mbit/s station clock ports), it is assumed that the SASE/BITS
selects the station clock output of RAD CSM as reference clock. The station clock

input port uses, in this case, the remote CSid (from the station clock output) as
CSid for the clock signal to the selection process (RI_CS = CI_CS) instead of its
own CSid (MI_CSid). This results in DNU insertion in the traffic output port
associated with the traffic input port used as source for the station clock (see
Figure C-4). If the station clock output is squelched or set to AIS, the remote CSid
is replaced by the own CSid (MI_CSid) and the automatic DNU insertion in the
traffic output port associated with the traffic input port used as source for the
station clock is removed (see Figure C-5).
SASE
station clock
active ports
RI_CS=1
output
MI_CSid=5
input
NEy
NEx NEz
CI_CS=1 CI_CS=1
MI_CSid=1 MI_CSid=3
SSM=0010 CI_CS=1 CI_CS=3
input input
SSM=1111 RI_CS=1 CI_CS=1 CI_CS=1 RI_CS=3 SSM=0010

do not use as output output can be used as
synchronization synchronization
source transport MI_CSid=2 MI_CSid=4 transport source
ports ports
input input

output output
T1530660-99
Figure C-4. Automatic DNU Generation in RAD CSM with SASE/BITS Timing (SSM/QL not Supported)

SASE
station clock
squelched/AIS ports
RI_CS=none
output
MI_CSid=5
input
NEy
NEx NEz
CI_CS=1 CI_CS=5
MI_CSid=1 MI_CSid=3
SSM=1011 CI_CS=1 CI_CS=3
input input

can be used as output output can be used as
synchronization synchronization
source transport MI_CSid=2 MI_CSid=4 transport source
ports ports
input input

output output
T1530670-99
Figure C-5. Removal of Automatic DNU Generation in RAD CSM with SASE/BITS Timing (SSM/QL not
Supported)
Delay Times
The following delay times are respected by the CSM module:
1. Holdover message delay THM This delay applies when the CSM (SEC/EEC)
switches to holdover because of loss of signal of the input reference and lack
of any other available reference. When this event occurs, the CSM (and
SEC/EEC) goes immediately into holdover but changes the output SSM to the
holdover code after a delay which has been defined to be between 500 ms
and 2000 ms.
2. Non-switching message delay TNSM This delay applies when the QL of the
selected synchronization source changes but no switchover to another source
is performed by the CSM. The outgoing SSM follows this change at the input
within a time defined to be less than 200 ms.
3. Switching message delay TSM This delay applies when a new synchronization
source is selected by the CSM. The output SSM change, if any, is done after a
delay that has been defined to be between 180 ms and 500 ms.

ESMC Support
If the interface type of the clock is Ethernet, that the CSM supports ESSM
(Ethernet SSM) messages transmission and reception for this port as per ITU-T
ESMC Operational Mode Overview

The protocol is related to the slow protocols group defined in [15]. The slow
protocol should transmit not more than 10 frames per second. The protocol PDUs
carry the characteristic of the clock quality as defined in ITU-T Recommendation
G.8264. The quality parameter is encoded as the QL TLV, where the informative
quality element is the SSM code. The SSM codes values for the Ethernet SSM are
defined in ITU-T Recommendation G.8264.
RAD CSM ESMC process transmits a periodic ESMC message each 1 sec and an
immediate event ESMC message per selected synchronization source quality level
change event. The quality information that is encoded in the transmitted ESMC
frames is enquired from the T0 selection process.
At the receiving end, RAD CSM ESMC process supports reception of ESMC frames
as well as informing the clock selection process about the received clock source
quality level. In addition, it maintains the continuity of the ESMC process; that is if
no ESMC message is received during 5 sec time interval the quality level of that
clock source is declared as QL-FAILED (SSF is issued).
ESMC PDU Format
Table C-12. ESMC PDU Format
Octet number Size/bits Field
1-6 6 octets Destination Address =01-80-C2-00-00-02 (hex)
7-12 6 octets Source Address
13-14 2 octets Slow Protocol Ethertype = 88-09 (hex)
15 1 octets Slow Protocol Subtype =0A (hex)
16-18 3 octets ITU-OUI = 00-19-A7 (hex)
19-20 2 octets ITU Subtype
21 bits 7:4 (see Note 1) Version
bit 3 Event flag
bits 2:0 (see Note 2) Reserved
22-24 3 octets Reserved
25-1532 36-1490 octets Data and Padding (See point J)

Last 4 4 octets FCS
Note 1: Bit 7 is the most significant bit of Byte 21. Bit7 to bit 4 (bits 7:4) represent the four bit version
number for the ESMC.
Note 2: The three least significant bits (bits 2:0) are reserved.
ESSM is sent with the slow protocol multicast MAC address (01 80 C2 00 00 02),
slow protocol Ethernet type (8809) and a specific sub type (0x0A). The OUI, ITU
subtype and version field values are shown in Table C-12. The E bit designates
the event that is the QL value changed. The R symbol designates the reserved
field.
The payload of the PDU contains one TLV 2 defined by the standard QL TLV. The
format of this TLV is given in Table C-13.
Table C-13. ESSM TLV Format
1 8 bits Type:0x01
2-3 16 bits Length: 0x0004
4 bits 7:4 0 (unused)
bits 3:0 SSM code
Note 1: Bit 7 of Octet 4is the most significant bit. The least significant nibble, bit 3 to bit 0
(bits 3:0) contain the four bit SSM code.
The codes to be used for Synchronous Ethernet SSM are: EEC1=1011 and
EEC2=1010 as defined in ITU-T Recommendation G.8264.
ESMC Process Functional Requirements

The implementation of the ESMC is fully compliant with ITU-T Recommendation
G.8264. The ESMC process maintains independent receive and transmit state
machines.
The receive state machine is comprised of two states: LOCKED and UNLOCKED.
The state machine enters the LOCKED state once it receives valid ESMC messages.
The state machine enters UNLOCKED state if it doesnt receive ESMC message
during 5 consecutive seconds. Upon such an event, the ESMC client would send
QL-FAILED quality level towards the selection process. While in LOCKED state, the
last received QL value is maintained. Upon a detection of a QL level change in the
incoming messages, the new QL level is immediately propagated to the selection
process (after going through the required Holdoff delay).
The ESMC client transmits state machine supports periodic transmission of ESMC
frames. The transmitting state machine sends an ESMC message every 1 sec in a
periodic manner. The QL code used in those ESMC messages is enquired from the
T0 clock selection process. The ESMC client sends DNU to the port, whose clock is
currently selected by the T0 selection process (timing loop prevention). The ESMC
2
Future ESMC applications may require additional TLVs.

transmit state machine also supports transmission per demand. This

transmission is performed immediately upon request from selection process.
Such request may happen if the selection process selects a new reference
clocked with a different QL value (or alternatively its current selected sync source
has altered its quality level).
The transmission of ESMC frames on a specific port can be enabled/disabled by
user configuration. In QL-disbaled mode, ESMC frames are being transmitted on
the relevant ports (unless they have been disabled by the user) with QL value set
to QL_DNU.
CSM State Machine

This CSM SW module is controlling a clock selection HW (SEC/EEC) that is
responsible for physical clocks selection, jitter attenuation and holdover according
to ITU-T Recommendation G.813/G.8262.
Three operational modes are supported:
Normal (Auto) operational mode, working in the Locked or Holdover states
depending on the input signals
Forced Freerun operational mode, working in the Freerun state
Forced Holdover operational mode, working in the Holdover state
These three types of operational modes are toggled by user configuration.
Figure C-6 shows the relationship between the different operational modes.
Figure C-6. SEC/EEC Operational Modes and Clock States

While in Freerun operational mode, the internal oscillator clock signal is

propagated to the relevant output clock synchronization ports, and the quality
level of the internal oscillator is being distributed on those ports (sent by the CSM
module).
The Auto (normal) operational mode is comprised of two clock states: Locked and
Holdover (an additional Unlocked clock state also exists but this is only an
intermediate ghost state and therefore does not have any significance):
Locked This is the steady-state of the system. The CSM is locking

to a synchronization clock source.
Holdover Upon losing its synchronization references, the system
immediately transits to Holdover state where the holdover
information, gathered so far, is being used to steer the
output frequency. At this state, holdover memory is no
longer updated by the incoming reference clock (holdover
memory freeze). When a new synchronization source
becomes valid, the system returns to the Locked state.
In Auto operational mode, the selection between the clock states is done
automatically depending on the quality and availability of the incoming reference
signal and the selected QL mode.
When in Auto operational mode, a forced holdover command would force the
CSM to move into the Holdover operational mode (Holdover state) regardless of
the current clock state.
In QL-enabled mode, the Locked state is automatically selected if the incoming
reference is not in the signal fail state (SSF = false) and the quality level of the
incoming reference is better or equal to the configured QL_minimum level.
The Holdover state is automatically selected without delay when the incoming
reference goes into the signal fail state (SSF = true) or the quality level of the
incoming signal is lower than the configured QL_minimum level. The Holdover
state is left when both the signal fail clears (SSF = false) and the quality level of
the incoming signal is equal or better than the configured QL_minimum level.
In QL-disabled mode the Locked state is automatically selected if the incoming
reference is not in the signal fail state (SSF = false). The Holdover state is
automatically selected when the incoming reference goes into the signal fail state
(SSF = true).
The CSM state can be forced by the user using the following CLI command:
configure >system>clock>domain (id)# mode { auto | free-run |
holdover } //default auto

C.8 CSM CLI Commands
Note For detailed information regarding the CSM CLI, refer to Chapter 4.
configure
system
clock
domain
- master
- fallback
-source
station
The Master and Fallback Clocks are kept for the backward compatibility with the
existing old projects, in order to have just one Clock XML file. TBD
Clock Selection Module Commands

Clock Domain definition:
configure >system>clock> domain <id> // <id> - domain number
Synchronization Network Type:
configure >system>clock>domain (id)# sync-network { type-1 | type-2 | type-3 }
// default type-2
Note
This parameter can be changed if no clock sources are configured. Upon attempt
to change it when there are existing sources the following error message is
displayed: Existing sources should be removed first.
QL Minimum:
configure >system>clock>domain (id)# no quality
configure >system>clock>domain (id)# quality min-level {level}
// level {lprc, ssu-a, ssu-b, sec, dnu } // option I
// {prs, stu, st2, tnc, st3e, st3, smc, st4, dus} // option II
// {unk, sec} // option III.
HW inputs monitoring:
configure >system>clock>domain (id)># max-frequency-deviation <value>
// value in units of 0.01 ppm in the range of 381-6096 (3.81 ppm to 60.96 ppm).
// the value configured here is effective for all HW inputs.
// the default value is 1524.
Operational mode:
ETX-2i CSM CLI Commands C-35

configure >system>clock>domain (id)# mode { auto | free-run | holdover

} //default auto
Note
Mode holdover is relevant only for T0 and once is selected forces T0 to go and
stay in Holdover state. This mode is also applicable for system maintenance and
troubleshooting
Synchronization of T4 on T0:
configure >system>clock>domain (id)# [no] force-t4-as-t0 //project dependent
Note
This command causes T4 clock output to be fed by DPLL T0 and to be locked on
the same source as T0.
External commands:
configure >system>clock>domain (id)# force < source-id >
configure >system>clock>domain (id)# manual < source-id >
configure >system>clock>domain (id)# clear
Notes
Command force never becomes inactive; even if the input is in SSF state only
clear deactivates it
Command manual becomes inactive if the input is SSF or QL changed
Command clear deactivates all commands; it returns to auto mode and cancels
force and manual.
Clock Client Commands

configure >system>clock>domain (id)#[no] source <src-id> {type} [<id>] [{port
type} <port-index>]
// type {domain <domain-id>| rx-port {port-type} <port-index>| station <station-id> |
recovered <recovered-id>}.
// rx-port {port-type} E1, T1, Ethernet, SDH/SONET.
configure >system>clock>domain (id)> source (src-id)# no priority <num> // If no
option is selected , then this source is not taken to the corresponding selection
process (for T0 or T4)
configure >system>clock>domain (id)> source (src-id)# wait-to-restore
<seconds>
configure >system>clock>domain (id)> source (src-id)# hold-off <milliseconds>
configure >system>clock>domain (id)>source (src-id) # quality-level <ql>
// ql can be {prc, ssu-a, ssu-b, sec, dnu} // option I
{prs, stu, st2, tnc, st3e, st3, smc, st4, dus} // option II
{unk, sec} // option III.
configure >system>clock>domain (id)> source (src-id)# wtr-clear //command
Status and Statistics Commands

C-36 CSM CLI Commands ETX-2i

System Clock: {source id} {quality} {state} // state has values: holdover, free-run
and locked.
Station-out Clock: {source id} {state} // state has values locked or unlocked
Force Switch: {InActive | Active}
Manual Switch: {InActive | Active}
configure >system>clock>domain (id)> source (src-id)# show status
Status: { ok, physical-fail, monitoring-fail, esmc-fail }
Tx quality: {ql }
Rx quality: {ql }
ESMC state: { locked | unlocked } // masked if disabled
WTR State : { Inactive | Running }
Notes
Tx and Rx quality and ESMC state are visible only for quality enabled mode.
ESMC state is visible only for Ethernet port type.
Tx quality is visible only if Tx SSM is enabled for this port.
configure >system>clock>domain (id)> source (src-id) # show statistics

ESMC Failure Counter:
ESMC frames: Tx Rx
configure >system>clock>domain (id)> source (src-id) # clear statistics
ETX-2i CSM CLI Commands C-37

C-38 CSM CLI Commands ETX-2i

Publication No. 547-200-10/17
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North American Headquarters

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

ETX-2i

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-2i

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

International Headquarters North American Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

19882017 RAD Data Communications Ltd. Publication No. 547-200-10/17

General Safety Instructions

Protective ground: the marked lug or terminal should be connected to the

Handling Energized Products

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Mise au rebut du produit

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

Instructions gnrales de scurit

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

Manipuler des produits sous tension

Rgles gnrales de scurit

Connexion au courant du secteur

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

Agent In SNMP, this refers to the managed system.

ANSI American National Standards Institute.

APS (Automatic An automatic service restoration function by which a network

Attenuation Signal power loss through equipment, lines or other transmission

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

Baud Unit of signaling speed equivalent to the number of discrete

Bipolar Signaling method in E1/T1 representing a binary 1 by alternating

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

Buffer A storage device. Commonly used to compensate for differences in

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

Carrier A continuous signal at a fixed frequency that is capable of being

CLI Command Line Interface (CLI) is a mechanism for interacting with a

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

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

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

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

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

E1 Line A 2.048 Mbps line, common in Europe, which supports thirty-two 64

E3 The European standard for high speed digital transmission,

ERP Ethernet Ring Protection. A G.8032 Layer-2 Ethernet ring is a logical

Ethernet OAM Ethernet operation, administration and maintenance (OAM) are a

EVC An Ethernet Virtual Connection is an association between two or

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

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

such as network protocols and the actual payload of data, is

Full Duplex A circuit or device permitting transmission in two directions

G.703 An ITU standard for the physical and electrical characteristics of

Gateway Gateways are points of entrance and exit from a communications

Interface A shared boundary, defined by common physical interconnection

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

Jitter The deviation of a transmission signal in time or phase. It can

Laser A device that transmits an extremely narrow and coherent beam of

Loading The addition of inductance to a line in order to minimize amplitude

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

MA (Maintenance See MEG (Maintenance Entity Group).

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

MIP (Maintenance A MIP is located at an intermediate point along the end-to-end

Manager An application that receives Simple Network Management Protocol

Mark In telecommunications, this means the presence of a signal. A mark

Metering This feature is intended for support of payphones, and therefore

Multiplexer At one end of a communications link, a device that combines

Network (1) An interconnected group of nodes. (2) A series of points, nodes,