RICi-16E1T1 2.5 MN

OPERATION MANUAL
INSTALLATION AND
RICi-16
Advanced Ethernet Services over Multiple
PDH Links NTU
Version 2.5
The Access Company

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

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

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

Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the RICi-16 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 RICi-16, and in no event shall
RAD's liability exceed the purchase price of the RICi-16.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to RICi-16 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the RICi-16 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 RICi-16 shall not
exceed the sum paid to RAD for the purchase of the RICi-16. In no event shall RAD be liable for
any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if RAD
has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal
waste at the end of its life cycle. Upon termination of the unit’s use,
customers should provide for its collection for reuse, recycling or other form
of environmentally conscientious disposal.
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or service
personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the
product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building
protective ground bus.
Some products may be equipped with a laser diode. In such cases, a label with the
laser class and other warnings as applicable will be attached near the optical
transmitter. The laser warning symbol may be also attached.
Warning Please observe the following precautions:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the transmitter.
• Do not attempt to adjust the laser drive current.
• Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
• The use of optical devices with the equipment will increase eye hazard.
• Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
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. The circuit breaker in the building installation should have high breaking
capacity and must operate at short-circuit current exceeding 35A.
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.
DC units should be installed in a restricted access area, i.e. an area where access is authorized
only to qualified service and maintenance personnel.
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. The circuit breaker in the building installation should have high breaking
capacity and must operate at short-circuit current exceeding 35A.
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF
position. When connecting the DC supply wires, first connect the ground wire to the
corresponding terminal, then the positive pole and last the negative pole. Switch the circuit
breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
Connecting Data and Telecommunications Cables

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

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

The equipment is designed and approved to comply with the electromagnetic regulations of
major regulatory bodies. The following instructions may enhance the performance of the
equipment and will provide better protection against excessive emission and better immunity
against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables. 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.
FCC-15 User Information
This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Canadian Emission Requirements

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

Warning This is a class A product. In a domestic environment, this product may cause radio
interference, in which case the user will be required to take adequate measures.
Avertissement Cet appareil est un appareil de Classe A. Dans un environnement résidentiel, cet
appareil peut provoquer des brouillages radioélectriques. Dans ces cas, il peut être
demandé à l’utilisateur de prendre les mesures appropriées.
Achtung Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In Wohngebieten

können beim Betrieb dieses Gerätes Rundfunkströrungen auftreten, für deren
Behebung der Benutzer verantwortlich ist.
Mise au rebut du produit
Français
Afin de faciliter la réutilisation, le recyclage ainsi que d'autres formes de

récupération d'équipement mis au rebut dans le cadre de la protection de
l'environnement, il est demandé au propriétaire de ce produit RAD de ne pas
mettre ce dernier au rebut en tant que déchet municipal non trié, une fois
que le produit est arrivé en fin de cycle de vie. Le client devrait proposer des
solutions de réutilisation, de recyclage ou toute autre forme de mise au rebut
de cette unité dans un esprit de protection de l'environnement, lorsqu'il aura
fini de l'utiliser.
Instructions générales de sécurité

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

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

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

Branchez toujours la fiche de secteur à une prise murale équipée d'une borne protectrice de mise
à la terre.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du bâtiment devrait avoir une capacité
élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A.
Branchez toujours le câble d'alimentation en premier à l'équipement puis à la prise murale. Si un
commutateur est fourni avec l'équipement, fixez-le en position OFF. Si le câble d'alimentation ne
peut pas être facilement débranché en cas d'urgence, assurez-vous qu'un coupe-circuit ou un
disjoncteur d'urgence facilement accessible est installé dans l'installation du bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si le système de distribution de
courant est de type IT.
Connexion d'alimentation CC
Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par
rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.
A cause de la capacité de courant des systèmes à alimentation CC, des précautions devraient
être prises lors de la connexion de l'alimentation CC pour éviter des courts-circuits et des risques
d'incendie.
Les unités CC devraient être installées dans une zone à accès restreint, une zone où l'accès n'est
autorisé qu'au personnel qualifié de service et de maintenance.
Assurez-vous que l'alimentation CC est isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation locale.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A. Le coupe-circuit dans l'installation du bâtiment devrait avoir une capacité
élevée de rupture et devrait fonctionner sur courant de court-circuit dépassant 35A.
Avant la connexion des câbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'équipement et fixez-le
en position OFF. Lors de la connexion de câbles d'alimentation CC, connectez d'abord le
conducteur de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le
pôle négatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
Declaration of Conformity
Manufacturer's Name: RAD Data Communications Ltd.
Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 69719, Israel
declares that the product:
Product Name: RICi-16
Product Options: All
conforms to the following standard(s) or other normative

document(s):
EMC EN 55022:2010 Information technology equipment; Radio disturbance

characteristics; Limits and methods of measurement.
EN 55024:2010 Information technology equipment; Immunity characteristics;

Limits and methods of measurement.
EN 61000-3-2:2006 Electromagnetic compatibility (EMC); Section 3-2: Limits for

harmonic current emissions (equipment input current 16A per
phase)
EN 61000-3-3:2008 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
Supplementary Information: The product herewith complies with the requirements of the EMC
Directive 2004/108/EC, the Low Voltage Directive 2006/95/EC, the
R&TTE Directive 99/5/EC for wired equipment and the sROHS
Directive 2011/65/EU.
The product was tested in a typical configuration.
Tel Aviv, 1 January 2013
Nathaniel Shomroni
Homologation Team Leader
European Contact: RAD Data Communications GmbH

Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
Glossary
Address A coded representation of the origin or destination of data.
Agent In SNMP, this refers to the managed system.
Analog A continuous wave or signal (such as human voice).
ANSI American National Standards Institute.
Attenuation Signal power loss through equipment, lines or other transmission

devices. Measured in decibels.
AWG The American Wire Gauge System, which specifies wire width.
Balanced A transmission line in which voltages on the two conductors are

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

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

conditions or events per second. If each signal event represents
only one bit condition, baud rate equals bps (bits per second).
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”).
bps (Bits Per Second) A measure of data transmission rate in serial transmission.
Bridge A device interconnecting local area networks at the OSI data link
layer, filtering and forwarding frames according to media access
control (MAC) addresses.
Bus A transmission path or channel. A bus is typically an electrical

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

modulated with a second (information carrying) signal.
Cell The 53-byte basic information unit within an ATM network. The
user traffic is segmented into cells at the source and reassembled
at the destination. An ATM cell consists of a 5-byte ATM header
and a 48-byte ATM payload, which contains the user data.
Channel A path for electrical transmission between two or more points.

Also called a link, line, circuit or facility.
Clock A term for the source(s) of timing signals used in synchronous

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

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

facsimile and video.
Data Link Layer Layer 2 of the OSI model. The entity, which establishes, maintains,
and releases data-link connections between elements in a
network. Layer 2 is concerned with the transmission of units of
information, or frames, and associated error checking.
Diagnostics The detection and isolation of a malfunction or mistake in a

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

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

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

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

which a low level protocol accepts a message from a higher level
protocol, then places it in the data portion of the lower-level
frame. The logistics of encapsulation require that packets traveling
over a physical network contain a sequence of headers.
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.
Flow Control A congestion control mechanism that results in an ATM system

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

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

(sending and receiving) at the same time.
FXO (Foreign Exchange A voice interface, emulating a PBX extension, as it appears to the
Office) CO (Central Office) for connecting a PBX extension to a
multiplexer.
FXS (Foreign Exchange A voice interface, emulating the extension interface of a PBX (or
Subscriber) subscriber interface of a CO) for connecting a regular telephone
set to a multiplexer.
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.
Half Duplex A circuit or device capable of transmitting in two directions, but

not at the same time.
Impedance The combined effect of resistance, inductance and capacitance on

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

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

that identifies a computer or device on a TCP/IP network. The
format of an IP address is a 32-bit numeric address written as four
numbers from 0 to 255, separated by periods (for example,
1.0.255.123).
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.
Loopback A type of diagnostic test in which the transmitted signal is
returned to the sending device after passing through all or part of
a communications link or network.
Manager An application that receives Simple Network Management Protocol

(SNMP) information from an agent. An agent and manager share a
database of information, called the Management Information Base
(MIB). An agent can use a message called a traps-PDU to send
unsolicited information to the manager. A manager that uses the
RADview MIB can query the RAD device, set parameters, sound
alarms when certain conditions appear, and perform other
administrative tasks.
Master Clock The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Multiplexer At one end of a communications link, a device that combines

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

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

a network, as a subset of a larger message.
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.
Polling See Multidrop.
Port The physical interface to a computer or multiplexer, for connection

of terminals and modems.
Protocol A formal set of conventions governing the formatting and relative

timing of message exchange between two communicating
systems.
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.
Serial Transmission A common mode of transmission, where the character bits are
sent sequentially one at a time instead of in parallel.
Single Mode Describing an optical wave-guide or fiber that is designed to

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

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

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

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

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

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

a single channel. In E1 and T1, one timeslot typically represents
one 64 kbps channel.
VLAN-Aware A device that is doing the Layer 2 bridging according to the VLAN
tag in addition to the standard bridging parameters. A VLAN-aware
device will not strip or add any VLAN header.
VLAN Stacking A technique that lets carriers offer multiple virtual LANs over a
single circuit. In essence, the carrier creates an Ethernet virtual
private network to tunnel customer VLANs across its WAN; this
helps avoid name conflicts among customers of service providers
who connect to the carrier. Stacking works by assigning two VLAN
IDs to each frame header. One is a "backbone" VLAN ID used by
the service provider; the other one has up to 4,096 unique 802.1Q
VLAN tags.
Quick Start Guide
Only an experienced technician should install RICi-16. If you are familiar with
RICi-16, use this guide to prepare the unit for operation.
1. Installing RICi-16
Connecting the Interfaces

1. Connect the network to the RJ-45 connectors designated E1 or T1.
2. Connect the user LAN to the RJ-45 connectors designated 10/100 BaseT (up
to four connectors).
3. Connect the control terminal to the front panel CONTROL connector
OR
Connect a Telnet host, a PC running a Web browsing application, or an SNMP
management station to the Ethernet port.
Connecting the Power

• Connect the power cable to the power socket on the RICi-16 front panel and
the other end to the power outlet.
The unit has no power switch. Operation starts when the power is
applied to the power connector(s).
2. Configuring RICi-16
Configure RICi-16 to the desired operation mode via an ASCII terminal connected
to the front panel CONTROL port. After configuring, you can manage the unit
over Telnet, a PC that runs a Web browser, or SNMP via either Ethernet or an
E1/T1 port.
Note Remote management requires configuring an IP address.
RICi-16 Ver. 2.5 Configuring RICi-16 1

Quick Start Guide Installation and Operation Manual
Starting a Terminal Session

³ To start a terminal session:
1. Turn on the control terminal PC and set its default port parameters to the
following:
Baud rate: 9600 bps
Data bits: 8
Stop bits: 1
Parity: None
Flow control: None.
2. To optimize the view of the system menus, do the following:
Set the terminal emulator to VT100.
If you are using HyperTerminal, set the terminal mode to the 132-column
mode.
3. Enter your user name and password and proceed with the management
session.
Note The RICi-16 default user name is su (lower case). The default password is 1234.
Configuring Basic Parameters

³ To configure RICi-16 for management:
• From the Host menu (Main > Configuration > System > Management > Host),
configure the following parameters:
Host IP address
Host IP mask
Default gateway
• From the Encapsulation menu (Main > Configuration > System > Management
> Host > Encapsulation), configure Host tagging (untagged/tagged). If you
select Tagged, additional parameters that need to be defined appear:
Host VLAN ID
Host VLAN Priority
2 Configuring RICi-16 RICi-16 Ver. 2.5

Installation and Operation Manual Quick Start Guide
Configuring RICi-16 Bridge Ports

The unit ships with a factory-set configuration, as defined below. To reconfigure,
you have to delete and reconfigure every bridge port parameter. You cannot
delete bridge port bindings to the host port and Ethernet ports.
Factory-Set Configuration
Bridge Port Configured to
1 Reserved for management
2 Ethernet port 1
3 Ethernet port 2
4 Ethernet port 3
5 Ethernet port 4
6 GFP 1 (logical port 2)
If you reconfigure the unit for a minimum working configuration, define at least
two bridge ports (BP) and bind them to either a physical or logical port.
One BP bound to a GFP interface
One BP bound to a Fast Ethernet interface.
Configuring RICi-16 3
Quick Start Guide Installation and Operation Manual
4 Configuring RICi-16 RICi-16 Ver. 2.5

Contents
Chapter 1. Introduction
1.1 Overview.................................................................................................................... 1-1
Product Options...................................................................................................... 1-2
Applications ............................................................................................................ 1-2
Features ................................................................................................................. 1-2
1.2 Physical Description ................................................................................................... 1-8
1.3 Functional Description................................................................................................ 1-8
Interfacing with User Traffic .................................................................................... 1-8
WAN Interfaces ....................................................................................................... 1-8
Ethernet Access (Bridge Mode) ............................................................................... 1-9
GFP, VCAT, and LCAS ............................................................................................. 1-14
Operating in Flow Mode ........................................................................................ 1-17
Prioritizing Traffic Using QoS ................................................................................. 1-19
Timing .................................................................................................................. 1-20
Management ........................................................................................................ 1-21
1.4 Technical Specifications............................................................................................ 1-23
Chapter 2. Installation and Setup

2.1 Site Requirements and Prerequisites .......................................................................... 2-1
2.2 Package Contents ...................................................................................................... 2-2
2.3 Required Equipment ................................................................................................... 2-2
2.4 Mounting the Unit ...................................................................................................... 2-3
2.5 Connecting to Ethernet Equipment ............................................................................. 2-3
2.6 Connecting to E1/T1 Equipment ................................................................................. 2-3
2.7 Connecting to T3 Equipment ...................................................................................... 2-4
2.8 Connecting to the Terminal ........................................................................................ 2-4
2.9 Connecting to Power .................................................................................................. 2-4
Connecting to AC Power.......................................................................................... 2-5
Connecting to DC Power ......................................................................................... 2-5
Removing/Installing the Hot-Swappable Power Supply Units .................................... 2-6
Chapter 3. Operation
3.1 Turning On the Unit ................................................................................................... 3-1
3.2 Indicators .................................................................................................................. 3-2
3.3 Default Settings ......................................................................................................... 3-3
3.4 Configuration and Management Alternatives .............................................................. 3-5
Working with Terminal ............................................................................................ 3-5
Working with the Web Browser ............................................................................... 3-8
Working with RADview ............................................................................................ 3-9
3.5 Menu Maps .............................................................................................................. 3-10
Configuration Menu .............................................................................................. 3-11
Monitoring Menu .................................................................................................. 3-16
Diagnostics Menu ................................................................................................. 3-18
Utilities Menu ....................................................................................................... 3-19
3.6 Turning Off the Unit ................................................................................................. 3-19
RICi-16 Ver. 2.5 i

Table of Contents Installation and Operation Manual
Chapter 4. Configuration
4.1 Configuring RICi-16 for Management .......................................................................... 4-1
Entering Device Information .................................................................................... 4-1
Configuring Host IP Parameters ............................................................................... 4-2
Configuring SNMPv3 ................................................................................................ 4-4
Configuring Management Access ........................................................................... 4-11
4.2 Configuring RICi-16 for Operation............................................................................. 4-16
Setting System-Level Parameters .......................................................................... 4-17
Configuring Physical-Layer Parameters .................................................................. 4-26
Configuring the Logical Layer ................................................................................ 4-38
Configuring the Application Layer Parameters........................................................ 4-42
Configuring the OAM............................................................................................. 4-61
4.3 Performing Additional Tasks ..................................................................................... 4-63
Viewing Inventory ................................................................................................. 4-63
Viewing the License Information ........................................................................... 4-64
Configuring Control Port Parameters ..................................................................... 4-65
Changing User Access Parameters ......................................................................... 4-65
Transferring Software and Configuration Files ....................................................... 4-66
Resetting RICi-16 .................................................................................................. 4-68
Chapter 5. Configuring Typical Applications

5.1 Application with Ethernet Cellular Backhauling over PDH/SONET/SDH .......................... 5-1
Configuring System Parameters............................................................................... 5-2
Configuring the Physical Layer ................................................................................. 5-4
Configuring the Logical Layer .................................................................................. 5-7
5.2 Ethernet Services over PDH/SONET/SDH ..................................................................... 5-8
Configuring System Parameters............................................................................... 5-8
Configuring the Physical Layer ............................................................................... 5-10
Configuring the Logical Layer ................................................................................ 5-11
5.3 Multiple Customer Premises Supported by Channelized DS-3 .................................... 5-15
Configuring System Parameters............................................................................. 5-17
Chapter 6. Diagnostics and Troubleshooting

6.1 Monitoring Performance ............................................................................................. 6-1
Viewing Device Status ............................................................................................. 6-1
Displaying Interface Statistics ............................................................................... 6-13
6.2 Handling Alarms and Traps ....................................................................................... 6-19
Displaying Events .................................................................................................. 6-19
Displaying Syslog Statistics ................................................................................... 6-20
6.3 Testing the RICi-16 Unit ........................................................................................... 6-21
Running a Ping Test .............................................................................................. 6-21
Tracing the Route ................................................................................................. 6-22
Running a Cable Test ............................................................................................ 6-22
Running Loopback Tests ....................................................................................... 6-23
Performing Bit Error Rate Test (BERT).................................................................... 6-24
Running OAM Tests............................................................................................... 6-27
6.4 Troubleshooting ....................................................................................................... 6-28
6.5 Technical Support .................................................................................................... 6-29
ii RICi-16 Ver. 2.5

Installation and Operation Manual Table of Contents
Appendix A. Connector Wiring

Appendix B. Boot Sequence and Downloading Software
Appendix C. Operation, Administration and Maintenance (OAM)
RICi-16 Ver. 2.5 iii

Table of Contents Installation and Operation Manual
iv RICi-16 Ver. 2.5

Chapter 1
Introduction
1.1 Overview
RICi-16 is a Network Termination Unit (NTU) that connects Fast Ethernet LANs
over 16 bonded E1 or T1 circuits, or over up to two bonded clear T3 circuits, or
over a channelized T3 interface. The bonded circuits create a scalable, virtual pipe
for transferring Ethernet traffic.
The unit enables service providers to supply high capacity Ethernet services to
remote locations. The units can also transparently connect corporate LANs
utilizing existing E1 or T1 lines.
RICi-16 uses the Ethernet over NG PDH standards and applies the Generic
Framing Procedure (GFP) to encapsulate the packet data for bandwidth utilization
and improving the latency for delay-sensitive applications. Virtual Concatenations
(VCAT) bond the required PDH connections for transmitting data, providing
flexible bandwidth for different applications. Link Capacity Adjustment Scheme
(LCAS) ensures seamless PDH capacity changes without affecting traffic and error
handling on individual E1/T1 links.
RICi-16 supports up to 16 GFP VCAT groups (VCG), for connecting of up to 16
different customers per site.
The following standard bonding and encapsulation protocols make RICi-16
interoperable with third-party devices:
• Generic Framing Procedure (GFP – G.8040)
• Virtual Concatenation (VCAT - G.7043)
• Link Capacity Adjustment Scheme (LCAS - G.7042).
End-to-end OAM, based on IEEE 802.1ag and ITU-T Y.1731 enables Ethernet
service providers to monitor their services proactively, measure end-to-end
performance and guarantee that the customers receive the contracted SLA. Fault
monitoring and performance measurement include Frame Delay, Frame Delay
Variation, Frame Loss and Availability. RICi-16 features single segment (link) OAM
according to IEEE 802.3ah fault indication, including remote loopback.
In both Bridge-based and Flow-based operation modes, incoming customer traffic
is classified (in Flow mode only) and mapped according to port-based (all-in-one)
bundling or by user port and CE VLAN-ID, VLAN priority, DSCP and IP precedence.
Operators can differentiate services using classification methods, police the
traffic and enforce SLA per service.
RICi-16 Ver. 2.5 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
RICi-16 supports Telnet, Web-based, and SNMP applications for inband

configuration and management, as well as an ASCII terminal for out-of-band
management.
Product Options
Uplink Options
RICi-16 is available with E1/T1/T3 interfaces as follows:
E1/T1: 4, 8, or 16 ports, which can be balanced or unbalanced
T3: Two bonded clear channel links or a single channelized link
Ethernet Port Options

The Ethernet ports are available as four 10/100BaseTx interfaces or one SFP
interface and two 10/100BaseTx interfaces.
The Fast Ethernet interfaces (10/100BaseTx) operate in full or half duplex, with
auto-negotiation and flow control.
Temperature-hardened Version
A temperature hardened version is available, significantly extending the permitted
operating temperature range.
Applications
Typical applications include Ethernet VPN services over E1 or T1 lines; aggregation
of enterprise LANs over E1 or T1 circuits; and IP DSLAM, cellular IP, and WiMAX
base station backhauling.
Figure 1-1 illustrates a typical application in which RICi-16 connects remote LANs
to the packet-switched network over 16 E1/T1 circuits using an SDH/SONET
connection.
Figure 1-1. RICi-16 Extends Ethernet Services over Multiple E1/T1 Circuits
Features
GFP VCAT LCAS

Ethernet over GFP VCAT encapsulation is supported as defined in ITU-T G.8040.
The links are grouped using VCAT as defined in ITU T G.7043. The LCAS protocol is
supported as defined in ITU T G.7042.
1-2 Overview RICi-16 Ver. 2.5

Installation and Operation Manual Chapter 1 Introduction
The RICi-16 GFP VCAT LCAS features are:

• Up to 16 Virtual Concatenation Groups (VCGs) are supported
• LCAS mechanisms:
Ensure that traffic flow recovers quickly from E1/T1 link failures
Allow on-the-fly addition/deletion of group members.
• Up to 250 ms differential delay for E1/T1
• Up to 217 ms differential delay for T3.
Note GFP VCAT LCAS maps Ethernet over framed E1/T1/T3 links. For E1/T1 the LCAS
information is aligned to the E1/T1 multiframe. Therefore E1/T1 carrying Ethernet
over GFP VCAT LCAS must be transported transparently over the PDH/SDH
network, to avoid damaging the multiframe alignment.
Encapsulation
RICi-16 supports 16 GFP VCAT LCAS groups with up to 16 E1/T1s per group (VCG).
Bridge Mode
RICi-16 provides a bridging function between its bridge ports:
• Fast Ethernet ports
• GFP logical ports (Ethernet over PDH)
• Internal host.
The internal bridge operates in VLAN-Unaware or VLAN-Aware modes.
VLAN-Unaware
In the VLAN-unaware mode all ports share the same broadcast domain (broadcast
frames are forwarded to all ports). When filtering is enabled, each port learns
MAC addresses of the connected devices and forwards traffic according to them.
When filtering is disabled (transparent mode), the switch operates as a simple
hub; it does not build a MAC table, and sends each frame to all its ports.
VLAN-Aware
In the VLAN-aware mode connections between the switch ports are determined
by their VLAN membership. This means that the traffic can be forwarded from
one port to another only if they are members of the same VLAN. For example, in
the figure below (see Figure 1-2) bridge ports 2 and 3 are members of VLAN 3,
serving the user traffic and completely separating it from the other traffic flows.
The management traffic running on VLAN 4 has to arrive to all ports, including the
device host. To achieve this, all bridge ports must be configured as VLAN 4
members.

VLAN 3
BP3
VLAN 3
User
Equipment
Bridge BP4
BP2
VLAN 4 BP5
VLAN 4
NMS
BP6
BP1
Host
Figure 1-2. Separating User and Management Traffic via VLANs
VLAN Membership
Bridge ports can be configured as egress tagged or egress untagged VLAN
members:
• Egress tagged ports add the tag of its VLAN to all untagged frames at the
bridge egress. Frames arriving with the tag of the VLAN the port belongs
remain intact.
• Egress untagged ports remove the tag of its VLAN from all arriving frames at
the bridge egress.
Tag Handling and PVID

Before being processed by the VLAN membership mechanism frames are handled
at the ingress (and egress) of each bridge port. These actions are called:
• Stacking – Adding PVID (port VID or default VLAN tag) to all arriving (ingress)
or outgoing (egress) frames, both untagged and tagged. In case of the
tagged frames, the PVID is stacked over the existing VLAN tag. When stacking
is disabled (set to None), PVID is added to the untagged frames only.
• Stripping – Removing the outer VLAN tags at the egress or ingress of the
bridge ports.
Flow Mode
RICi-16 provides traffic flow classification between the traffic source and its final
destination. RICi-16 supports up to 64 unidirectional flows. Each flow is defined
by a classification profile.
In Flow-based operation mode, incoming customer traffic is classified and
mapped according to port-based (all-in-one) bundling or by user port and CE
VLAN-ID, VLAN priority, DSCP and IP precedence. Operators can differentiate
services using classification methods, police the traffic and enforce SLA per
service

Classification
The RICi-16 classifier uses the following classification fields/ rules per port. The
following classification combinations are possible:
• Unclassified
• 802.1p
• VLAN
• DSCP
• IP Precedence
• VLAN + 802.1p
• VLAN + DSCP
• VLAN + IP Precedence
• Untagged
• No IP
• No IP + VLAN
Up to 64 classification profiles/instances are supported.
For more information about flow classification, refer to Functional Description.
Tagging and Marking

RICi-16 supports several options for per flow VLAN tagging, including adding and
removing of VLAN tags and VLAN marking. RICi-16 also marks P-bits.
Traffic Prioritization Using QoS

Different service types require different levels of QoS to be provided end-to-end.
QoS can be defined per subscriber as well as per service. QoS has three aspects;
rate limitation (policing), traffic prioritization and traffic shaping.
Policing and Bandwidth profiles

Policers are applied per flow and operate according to the dual bucket mechanism
(CIR + CBS, EIR + EBS). RICi-16 supports up to 32 policers.
Traffic Prioritization and Queue Mapping

The queue mapping functionality associates the user priorities with queue
numbers.
Once traffic has been associated with a flow, it can be mapped to network
ingress queues that can be defined to be strict (Strict Priority) queues, WFQ
(Weighted Fair Queues) or mix of both.
Priority queues can be mapped according to user priority (P-bit, DSCP, IP
Precedence).
Traffic Shaping
RICi-16 performs shaping at the network egress and port level.

L2CP Handling
RICi-16 can be configured to pass through the Layer-2 control frames across the
network to peer supported protocols (OAM.ah), or to discard the L2CP frames.
Management
Setup, control, and monitoring of status and diagnostics information can be
performed using the following methods:
• Local and remote inband management via the Ethernet network or GFP logical
port using Telnet SSH.
• Out-of-band management via one of the user data ports that can be
configured as a management port
• Local management via an ASCII terminal connected to the V.24 (RS-232) DCE
control port.
• RADview: RAD’s SNMP-based element management software, providing SNMP
traps, status polling, and configuration download. RICi-16 now supports the
SNMP version 3, providing secure access to the device by authenticating the
encrypted packets transmitted over the network.
The following tasks are performed by the internal management software:
• Viewing system information
• Modifying configuration and mode of operation, including setting system
default values and resetting the unit
• Monitoring performance
• Initiating connectivity tests
• Defining ping and trace routes
• Downloading/uploading remote software and configuration files (TFTP)
• Upgrading software.
Security
The following security protocols are provided by RICi-16 to ensure client-server
communication privacy and correct user authentication:
• RADIUS (client authentication only)
• SSLv3 for Web-based management application
• SSHv2 for Secure Shell communication session
• SNMPv3 (SNMPv1 is used if SNMPv3 is not enabled).
Ethernet OAM
RICi-16 provides two types of Ethernet OAM:
• CFM (End-to-end OAM) based on IEEE 802.1ag and ITU T Y.1731 enable
Ethernet service providers to monitor their services proactively, measure end-
to-end performance and guarantee that the customers receive the
contracted SLA. Fault monitoring and performance measurement include
Frame Delay, Frame Delay Variation, Frame Loss and Availability

• EFM OAM (link OAM) according to IEEE 802.3ah for fault indication, including
remote loopback and MIB parameters.
For additional information on OAM, refer to Appendix C.
Timing
RICi-16 has a two-clock domain with master and fallback sources for timing, one
clock for T3 timing and one for T1s mapped to VCGs. The clock source can be an
internal oscillator or a recovered clock signal from one of the links.
Diagnostics
RICi-16 offers several types of diagnostic and troubleshooting procedures:
• Remote loopbacks on the E1/T1/T3 ports
• Ping tests
• Trace Route
• Ethernet cable test
• Bit Error Rate Test (BERT) on the E1/T1/T3 ports
• OAM test
• Events/Traps – Traps can be masked, per manager IP address, upon user
configuration.
Statistics
RICi-16 provides statistics and counter capabilities for the physical Ethernet,
E1/T1 levels, and logical GFP statistics.
Event Log File

The Log File includes entries at the system, Ethernet, GFP, VCG, and E1/T1/T3
levels.
Fault Propagation
The unit features a user-configurable bidirectional fault propagation mechanism
that notifies local and remote equipment of faulty conditions. This enables
routers and switches on both ends of the link to reroute traffic.
Power Supply Redundancy

Two redundant load-sharing power supply modules provide AC or DC power to
the device. In case any single power supply module fails or loses its input power,
the remaining power supply module continues to supply power to the chassis,
without disruptions.

1.2 Physical Description

RICi-16 is a 1U high standalone or rack mountable device.
Figure 1-3 illustrates a three-dimensional view of RICi-16/T3 with T1 interfaces
and Ethernet SFP port, over RICi-16/E1 with E1 interfaces.
Figure 1-3. RICi-16/E1 and RICi-16/T3 Front Views
LEDs, interfaces, and control connectors are located on the front panel. For
additional information, refer to Chapter 3.
1.3 Functional Description

This section describes key functions of RICi-16.
Interfacing with User Traffic

RICi-16 provides one or four half-/full-duplex, 10/100 Mbps Fast Ethernet ports,
with flow control and autonegotiation support. All ports are used for user traffic.
WAN Interfaces
The unit supports the following WAN interfaces:
• Framed E1 circuits (G732N with CRC), up to 16. The E1 interfaces are G.704,
G.703 compliant.
• Framed T1 (ESF) circuits, up to 16. The T1 interfaces are ANSI T1.403
compliant. Network should be transparent for framed T1.
• Channelized or clear T3 circuits (T1oT3 {TDM} and ETHoT1oT3) to facilitate
cellular backhauling. The T3 interfaces support M23 (channelized only) or C-
bit parity framing. Up to 16 T1 circuits can be mapped over a channelized T3
interface, and the rest of the 28 channels or all of them can be mapped to up
1-8 Functional Description RICi-16 Ver. 2.5

to 16 VCGs. Multi VCG enables supporting multiple service providers per site.
Two clear T3 circuits facilitate up to 100 Mbps uplink.
Note The network should be transparent for framed E1, T1 and T3 interfaces.
T3 Port Protection
RICi-16 supports 1+1 link protection on the T3 links, if the unit is operating with a
channelized T3 network interface.
Ethernet Access (Bridge Mode)

RICi-16 has a multi-port bridging capability handling up to 6 bridge ports. The
Bridge supports two modes of operation:
• VLAN-Aware
• VLAN-Unaware.
The mechanism of each mode can be described as five different processes:
Ingress: Checks each frame entering the bridge to decide if and how
this frame should be passed on to the forwarding process
Learning: Learns new MAC table entries (MAC only or MAC VID pairs)
Term Checks the forwarding MAC table periodically
Forwarding: Decides to which bridge port/ports to forward the frame
Transmission Selects the format of the transmitted frame at the output

(VLAN-Aware mode only): port with VLAN ID (tagged) or without VLAN ID (untagged).
Bridge features and these five processes are described below for each mode.
VLAN-Aware Mode
This mode enables creating sub-groups of bridge ports within the bridge. Each
sub-group is defined per VLAN and is associated with a unique VLAN ID (VID).
Frames containing a VID can be forwarded only between bridge ports that are
members of this specific VLAN, enabling a total separation between different
VLAN users within the same bridge.
Bridge
• Full VLAN-aware bridge in accordance with 802.1q
• Learning and forwarding according to MAC address and VID
• Learning of up to 2,018 MAC table entries (MAC + VID pairs) and 30 static
addresses
• Configuration of the aging time
• MAC table viewing (all learned and static MACs).
RICi-16 Ver. 2.5 Functional Description 1-9

Ingress Process
The ingress process is composed of the following three steps:
• Frame Admission: Has two modes of operation (configured per bridge port):
Admit All Frames: All frames arriving from the port are admitted and
proceed to the ingress filtering process. PVID is assigned to untagged or
priority-only tagged frames.
Admit Only VLAN Tagged Frames: Only VLAN tagged frames are admitted
and allowed to proceed to the ingress filtering process. Untagged or
priority-only tagged frames are discarded.
• Ingress Filtering: Available for one of the following modes (configured per
bridge port):
Enable: Performs ingress filtering according to VIDs. Only frames that
share a VID assigned to this bridge port are admitted
Disable: All frames are forwarded.
Only admitted frames that pass filtering are submitted to learning and
forwarding processes.
• PVID Assignment: Is per bridge port configuration:
In VLAN-aware mode, every received frame entering the bridge is
associated with a single VID. If the received frame does not contain a
VLAN ID (untagged or priority only tagged frames), a specific PVID is
assigned to these frames before they pass to the forwarding process.
Accordingly, the untagged/priority tagged frames that have passed the
admission/ingress filtering, are tagged with PVID and proceed to the
forwarding process. Tagged frames will be double tagged with the PVID
only if Tag Stacking is enabled.
For untagged frames that were tagged during this process to VID=PVID,
the priority tag is assigned at the VLAN priority field, according to the
default priority configuration.
Table 1-1 summarizes the behavior of the ingress process:
Table 1-1. Ingress Process
Frame Ingress Bridge Behavior

Admission Filtering
Mode Mode
Admit all frames Enable VLAN tagged frames with a VID (or PVID for
untagged/priority tagged frames) that do not include
the bridge port in their VLAN member set are
dropped.
Disable All frames pass.
Admit VLAN Enable VLAN tagged frames with a VID that do not include
tagged frames the bridge port in their member set are dropped.
Untagged/priority-only tagged frames are dropped.
All VLAN tagged frames pass. Untagged/priority-only
Disable tagged frames are dropped.

Frames that pass this stage are submitted to the forwarding and learning
processes.
Learning Process
The learning process observes the source MAC address (SA) and the VID of the
received frame, and updates the database with the MAC VID pair and with the
bridge port that the frame was received from. The Forwarding Data Base (FDB) is
also referred to as a MAC table.
Entries in the MAC table can be dynamic (inserted by the learning process) or
static (inserted by configuration). A dynamic entry has an aging time associated
with it.
The RICi-16 VLAN–Aware bridge is an Independent VLAN Learning (IVL) bridge.
The learning process inserts a new dynamic entry into the MAC table. This entry
consists of a MAC-VID pair and bridge port.
If the MAC-VID pair already exists for the same port, the aging time is updated.
If the MAC-VID pair already exists but for a different bridge port (dynamic entry),
the new entry overrides the existing one.
If the MAC-VID pair already exists for a different bridge port (static entry), the
static entry prevails.
Aging Process
The aging process checks the forwarding MAC table periodically. Each dynamic
entry-aging period that has exceeded the configured Aging Time Limit is deleted.
The aging period represents the time passed since the last frame for this entry
entered the bridge. The periodic check of the MAC table (aging time intervals)
results in the actual aging time that can reach up to twice the value that was
configured by the user.
Forwarding Process
The forwarding process is performed based on the frame destination MAC VID
pair. The frame is forwarded to the bridge port specified in the MAC table for this
MAC VID pair.
Untagged frames are forwarded according to the PVID attached to them during
the ingress process.
Frames are forwarded, dropped, or flooded according to the following guidelines:
• Forwarded: If the bridge port of the pair entry (DA, VID) in the MAC table is
both an active bridge port and a member of the VLAN, the frame is forwarded
to that bridge port only.
• Dropped:
If the bridge port for the pair entry (DA, VID) in the MAC table is the port
on which the frame was received, the frame is dropped.
If there are no active ports associated with the frame’s VID, or if the VID
is not defined at all, the frame is dropped.
• Flooded:

If the pair (DA, VID) is not learned and does not exist in the MAC table,
the frame is transmitted to all bridge ports that are associated with the
frame’s VLAN ID.
Multicasts and broadcasts are flooded only through the bridge ports
whose VLAN ID is identical to the frame’s VLAN ID.
Frames that pass this stage are submitted to the forwarding and learning
processes.
Transmission Process
After the forwarding process identifies the destination bridge port/ports to which
the frames must be transmitted, the frames are transmitted in the appropriate
format.
The frame format can be configured for each VLAN and port:
• VLAN-tagged: In this mode:
VLAN-tagged frames are transmitted unchanged
Untagged frames are transmitted tagged with VID=PVID of the entry port.
Priority-tagged frames are transmitted tagged with original priority and
VID = PVID.
• Untagged: In this mode, all frames are transmitted as untagged.
VLAN-Unaware Mode
In this mode the bridge forwarding ignores the VLAN ID of VLAN-tagged frames.
Each Ethernet frame received from each bridge port (Ethernet or E1s) is
forwarded according to its destination MAC address.
Bridge Features
Bridge features include:
• Learning and forwarding according to MAC address only
• Learning of up to 2,018 MAC table entries and 30 static addresses
• Configuration of the aging time
• VLAN tagged frames transparency (forwarding according to MAC only)
• MAC table viewing (All MACs).
Ingress Process
All frames are accepted in this mode: untagged, priority-tagged, or VLAN tagged.
Learning and forwarding is based on the MAC addresses, with no regard to the
VLAN.
Learning Process
The learning process observes the source MAC address (SA) of the received frame
and updates the forwarding database (FDB) with the MAC address and the bridge
port that the frame was received from. (FDB is also referred to as MAC table).

The learning process inserts a new entry into the MAC table. This entry consists
of the MAC and bridge port.
• If the MAC already exists for the same bridge port, the aging time will be
updated.
• If the MAC already exists, but for a different bridge port, (dynamic entry) the
new entry will override the existing one.
Aging Process
The aging process checks the forwarding MAC table periodically. Each dynamic
entry aging time period that has exceeded the configured Aging Time Limit is
deleted. The aging time period is the period of time since the last frame for this
entry entered the bridge. The periodic check of the MAC table (aging time
intervals), results in an actual aging time that can reach up to twice the user-
configured value.
Forwarding Process
The forwarding process is performed based on the frame MAC Destination
Address (MDA). The frame is forwarded to the bridge/port specified in the MAC
table for this MAC.
Frames are forwarded, dropped, or flooded at this stage:
• Forwarded: The frame is forwarded according to DA, to the bridge port where
the DA was learned.
• Dropped: If the port for the DA entry in the MAC table is the port for which
the frame was received, the frame is dropped.
• Flooded:
If there is no information regarding the DA in the MAC table, the frame is
flooded to all ports.
Frames with multicast or broadcast addresses are flooded to all ports.
In this bridge mode (VLAN-Unaware), the frames are transmitted unchanged, that
is no tags are added or removed.
VLAN Stacking
VLAN Stacking mode for a bridge port refers to the addition of a tag to a frame
either at ingress or egress (regardless of whether it already has an existing VLAN
tag), and removal of a tag at ingress or egress when the frame leaves through
this port.
This setting is independent of the bridge activity.
VLAN Stripping
VLAN Stripping mode for a bridge port refers to the removal of a tag at ingress or
egress when the frame leaves from this port.
This setting is independent of the bridge activity.

GFP, VCAT, and LCAS

Using Generic Framing Procedure (GFP) for encapsulation, together with the
virtual concatenation (VCAT) and Link Capacity Adjustment Scheme (LCAS)
protocols, the 16 E1/T1 or 2 T3 ports are bundled together providing a less rigid,
more robust transfer method.
VCAT breaks the bundled payload into individual bytes that are transported over
the E1/T1/T3 lines. Since each byte may use a different physical route (different
E1) through a network, VCAT supports the buffering of the information to
account for delays.
LCAS is a signaling protocol for sizing virtually concatenated paths. It provides
removes links that are not carrying traffic, due to failures or user configuration.
The link is detected and automatically removed from the VCG.
GFP Technical Overview
TX Traffic Path
In this direction, the ETHERNET packet with the CRC32 is encapsulated into GFP.
The encapsulation can be divided into two main sections: a Core Header and a
Payload Area.
The Core Header contains the packet length and a CRC16 result of the length. It
is used by the frame-delineation procedure (as explained in the RX path
description below) to detect the boundaries of the frame. The Core Header is
scrambled by xoring the 32 bits (length and CRC16) with the 32 bits B6AB31E0.
The scrambling of the GFP Core Header improves the robustness of the frame-
delineation procedure, and provides a sufficient number of 0 1 and 1 0
transitions during idle transmission periods.
Figure 1-4. GFP Encapsulation
The Payload Area is divided into three subsections: the Payload header, the User
data (Ethernet packet), and an optional FCS (CRC 32) that is calculated on all

payload information filed. For encapsulation of Ethernet frames, this CRC appears
to be unnecessary. The PFCS addition is user configurable.
All octets in the GFP Payload Area are scrambled using a 1 + x^43 scrambler; this
scrambler is always activated.
The Payload Area contains between 4 and 64 bytes, according to the following:
Figure 1-5. GFP Encapsulation – Payload Area
The PTI (Payload Type Identifier) indicates the content of the GFP frame: user
frame or management frame (RICi-16 does not generate management frames in
the TX direction).
The PFI indicates whether the packet includes PFCS.
The EXI indicates the type of extension header encapsulated in the frame.
RICi-16 supports transmission of a Null extension header (i.e., no extension
header is added).
The UPI indicates the type of user data encapsulated in the GFP format.
RICi-16 transmits an Ethernet-over-GFP payload identifier when the GFP frames
are user frames. When there is no user packet to be transmitted over GFP,
RICi-16 generates idle frames.
Special four-octet GFP control frames consisting of only a GFP Core Header with
the PLI and cHEC fields set to 0. These frames are generated by the transmitter in
order to keep the frame-delineation mechanism in the far-end receiver in a sync
state.
The GFP signal is mapped into TDM according to the following. The procedure of
mapping the GFP packets over the PDH signals is described in the G-8040
standard.
The PDH signal works in multiframe mode: CRC-4 multiframe mode for E1 (31
timeslots) and ESF framing mode for T1 (24 timeslots) are supported
The first timeslot in each multiframe is used for transferring the VCAT header
information
In all other timeslots there is user data after the encapsulation of GFP according
to G.7041 (as described above).
The VCAT header information is the LCAS CONTROL packet, as described in the
G.7043 standard. One control packet is transmitted in a period of
16 multiframes.

RX Traffic Path
RICi-16 assumes that the traffic received from TDM ports is traffic arriving from a
non-LCAS GFP transmitter. RICi-16 treats this data according to the following:
• RICi-16 extracts the VCAT header from the first timeslot of each multiframe.
• RICi-16 recognizes the frame border by synchronization on the core header
which contains the frame length & CRC16 on the length (see Error! Reference
source not found.). The GFP LINK is kept in sync state if the cHEC is correct
per frame. To ensure that the GFP LINK is always synchronized, the
transmitter in RICi-16 generates idle frames, with the Delta parameter equal
to 2.
• The GFP receiver has the ability to correct a single-bit error in tHEC or cHEC or
tHEC. This function is always active. The single-bit error correction on Chec is
not active when the GFP signal is in Presync or hunt state.
The data is also descrambled (during sync state) before the packets are
transferred to the bridge.
Payload FCS / CRC 32 of Ethernet packet check: The GFP receiver checks that the
payload FCS (if enabled) or the CRC32 of Ethernet is correct. If incorrect, it
discards the packet.
GFP over PDH actual bandwidth: GFP mapping over a PDH signal involves the
following overhead:
• The PDH signal works in multiframe mode. For E1, TS0 is used for frame
synchronization, and for T1, the F bit is used.
• Space is also reserved for a VCAT header every multiframe.
From this it can be determined that the actual PDH rate for GFP frames is as
follows:
E1 links: (2.048Mbs –64Kbps – 64/16 k) = 1.98Mbs
T1 links: (1.544Mbs –8Kbps – 64/24 k) ~1.533Mbs. The overall calculation must

also take into account the following overhead for GFP encapsulation:
• Chec_O (Core header encapsulation) – four bytes (always added to the
packet)
• Thec_O (Type header encapsulation) – four bytes (always added to the
packet)
• Ehec_O (Linear extension header encapsulation) – four bytes (optional;
user-configurable)
• P_FCS (Payload FCS -CRC32) – four bytes (optional; user-configurable).
The maximum PPS (packets per second) that can be generated on the PDH is thus
determined as follows (where P_SIZE is the packet size, and other parameters are
as described above):
• for E1 links: PPS =1.98Mbs/ 8/ ( P_SIZE + Chec_O + Thec_O + Ehec_O + P_FCS )
• for T1 links: PPS ~1.533Mbs / 8/ ( P_SIZE + Chec_O + Thec_O + Ehec_O +
P_FCS).
In RICi-16:
• Ehec_O is 0

• P_FCS is user-configurable.
Operating in Flow Mode

RICi-16 supports up to 64 unidirectional flows. Flows are defined by ingress and
egress ports, a classification profile and a priority.
The flow traffic can be passed, dropped or policed. It can be subject to packet
editing (VLAN tag, p-bit marking) and mapped to a priority queue.
Figure 1-6. Data Flow – User Interface to Network Interface
Figure 1-7. Data Flow – Network Interface to User Interface

Classification
The ingress user traffic is mapped to the Ethernet flows using classification types.
RICi-16 allows two of the following combinations per port (port + …)
• VLAN (Range)
• P-bit (Range)
• IP Precedence (Range)
• DSCP (Range)
• VLAN (Range) + P-bit (Range)
• VLAN (Range) + IP Precedence (Range): Only for User to Network
• VLAN (Range) + DSCP (Range): Only for User to Network
In addition to the selected combination above the following classification are
supported per port:
• Untagged
• Non-IP
• VLAN (Range) + Non-IP
• Unclassified
Policing and Bandwidth Profiles

RICi-16 supports 32 policer profiles and instances.
Policers can be applied per flow. The policers operate according to the dual token
bucket mechanism with the following configurable parameters:
• CIR
• CBS
• EIR
• EBS
RICi-16 does not support policer for Network to User flows.
Tag Editing
RICi-16 supports several options for VLAN tagging and p-bit tagging/mapping
actions including adding/removing VLAN tags and setting P-bit for the VLAN tag
(as per a mapping function). The following options are available.
• Push VLAN tag/stack (push)
• Pop VLAN tag/stack (pop)
• Mark VLAN tags/stack (mark)
• Add two levels of VLAN tag/stack
• Remove two levels of VLAN tag/stack
• None (no action)
P-bit actions (for pushed VLANs)
• Set to a fixed value

• Copy from C-VLAN tag

• Mark according to a defined mapping profile according to the user priority (P-
bit, IP Precedence or DSCP)
Queue Management
The following sections explain how queues are managed.
Priority Queues
RICi-16 supports five queues at the egress network port. The first queue (#0) is
dedicated to host (management, OAM) traffic and user traffic cannot be assigned
to this queue.
The scheduling method can be configured by the user, per queue, to be strict or
WFQ, according to the scheduling method.
Strict. The data flow set to the highest priority is transmitted first. If this data
flow stops, all tasks at lower priorities move up by one priority level. For example,
the data flow set to the second-highest priority is then transmitted at the
highest priority.
WFQ. Allows different scheduling priorities to statistically multiplex data flows
with different shares on the service. Each data flow has a separate FIFO queue. A
link transmitting at a data rate R, N non-empty data flows are served
simultaneously according to the assigned share w, each at an average rate of
R/(w1 + w2 + w3 + … +wN). If one data flow stops, the remaining data flows each
receive a larger share w.
Congestion Control
Each queue employs an early discard mechanism to ensure CIR traffic (green
packets). Early discard of yellow packets (EIR), upon crossing a predefined fill
level threshold ensures CIR traffic over EIR traffic.
Prioritizing Traffic Using QoS

RICi-16 maps QoS to priority queues (4 PQ, strict priority or WFQ or both)
according to one of the following:
• VLAN priority (802.1p)
• DSCP (bits 0-5 in IP TOS byte)
• IP Precedence
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
VERSION IHL TOS TOTAL LENGTH
IDENTIFICATION FLAGS FRAGMENT OFFSET
HEADER
TIME TO LIVE PROTOCOL HEADER CHECKSUM

IP
SOURCE ADDRESS
DESTINATION ADDRESS
OPTIONS PADDING
Figure 1-8. IP Header

Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
DS5 DS4 DS3 DS2 DS1 DS0 XX XX
DSCP: six bits (DS5–DS0)
Figure 1-9. ToS Byte DSCP Field
Timing
E1/T1 Uplink
The Tx clock for the E1/T1 links is determined by the system clock, which can be
derived from the internal oscillator or the recovered clock signal from one of the
Rx links. You can configure the master and fallback source for the system clock.
The following figures show typical clock configurations for the E1/T1 links.
Figure 1-10. E1/T1 Clock Configuration for RICi-16 Working Opposite RICi-16
Figure 1-11. E1/T1 Clock Configuration for RICi-16 Working Opposite Egate-100
T3 Uplink
In T3 mode, RICi-16 supports two system clocks:
• E1/T1 clock, for E1/T1s mapped to VCGs, in the case of channelized T3. The
E1/T1 clock source options are:
Internal oscillator
Recovered clock signal from one of the E1/T1 links.
• T3 clock. The T3 clock sources options are:
Internal oscillator
Recovered clock signal from one of the T3 links.

Note Clock timing is not required for TDM T1s mapped over DS-3 (M13), as they are
transparently mapped over DS-3.
The following figures show typical clock configurations for the T3 links.
Figure 1-12. T3 Clock Configuration for RICi-16 Working Opposite RICi-16
Figure 1-13. T3 Clock Configuration for RICi-16 Working Opposite Egate-100
Management
RICi-16’s performance can be locally monitored from an ASCII terminal, or from a
remote site using Telnet or the ConfiguRAD Web-based application. RAD’s SNMP
network management application RADview is supported as well.
Inband Management
RICi-16 supports inband management via Telnet, SNMP, and Web (ConfiguRAD).
Configuration, monitoring, and statistics are available.
Out-of-Band Management
RICi-16 allows full configuration and diagnostics via an ASCII terminal. The ASCII
terminal is connected to the control port on the front panel.
Chapter 3 explains how to activate the ASCII terminal and provides general
instructions for navigating through the system menus and windows to view and
modify data.
Security
ASCII terminal, Telnet SSH, and Web access are password protected. After 15
minutes of inactivity, the system exits and you will have to log in again.

Telnet, Web, and SNMP access can be individually disabled or restricted to

stations in the manager list.
RICi-16 supports the following access authorization levels:
• Superuser mode for configuration and monitoring
• User mode for monitoring and configuration view only.
Management Access
The unit’s architecture allows access from every bridge port to the host devices.
In certain configuration modes, a total separation of management traffic from
user traffic can be achieved.
In VLAN-aware mode, RICi-16 forwards the management traffic to the
management station in the Ethernet network. Because a different VLAN is used,
total separation between user traffic and management traffic is maintained.
In the scenario illustrated by Figure 1-15, traffic coming from the remote CPE
uses separate VLANs for user and management traffic. Each remote unit uses two
VLANs, one for user traffic and one for management.
Figure 1-14. Management Traffic in a VLAN-Aware Application
1-22 Technical Specifications RICi-16 Ver. 2.5

1.4 Technical Specifications
E1 Interface Number of Ports 4, 8, or 16
Compliance G.703, G.704
Framing Framed (G732N with CRC)
Data Rate 2.048 Mbps
Impedance 120Ω, balanced

75Ω, unbalanced (via adapter cable)
Line Coding HDB3, AMI
Connector Electrical, RJ-45
T1 Interface Number of Ports 4, 8, or 16
Compliance ANSI T1.403
Framing ESF
Impedance 100Ω, balanced
Line Coding B8ZS, AMI
Connector Electrical, RJ-45
T3 Interface Number of Ports 1 (channelized)

2 (clear channel)
Compliance GR-499-CORE
ANSI T1.107
ANSI T1.102
Framing C-bit parity, M23 (channelized only)
Impedance 75Ω, unbalanced
Line Coding B3ZS
Connector Coaxial BNC
Fast Ethernet Number of Ports 3 or 4
RICi-16 Ver. 2.5 Technical Specifications 1-23

10/100BaseT
Interfaces
Interface 4 10/100BaseTx interfaces or

2 10/100BaseTx interfaces and 1 SFP interface
Standards Ethernet, Relevant sections of IEEE 802.3, 802.3u
Maximum Frame 1,700

Size
Data Rate 100 Mbps
Interface type, Electrical, RJ-45

connector
SFP
Range 100 meters/328 feet on UTP category 5 cables
Autonegotiation Supported
Flow control PAUSE
Duplex modes Full/half duplex
Encapsulation ETH over • Compliance: G.7042, G.7043, G.8040

GFP VCAT LCAS
• Up to 16 E1/T1 links per VCG
• Up to 16 VCGs
• Differential delay: Up to 250 ms for E1/T1
Up to 217 ms for T3
Internal Bridge Ports • Fast Ethernet (up to 4)

• For local host (1)
• GFP
LAN Table Learning of up to 2,018 MAC table entries and 30 static

addresses
Operation Mode VLAN–Aware, VLAN-Unaware
Filtering and Transparent or filter

forwarding
Control Port Interface RS-232/V.24 (DTE asynchronous)
Data Rate 9.6, 19.2, 115.2 kbps
Connector DB-9, female
Monitoring Statistics System and physical layer Alarms

ETH o E1 frame counters
Ethernet physical layer statistics and frame counters
Indicators PWR (green) On – RICi-16 is powered on

Off – RICi-16 is off
TST (yellow) On – Loop is set on one of the interfaces

Off – No loop is set on one of the interfaces
ALM (red) On – System or interface alarm is active

Off – No Alarm
LINK (green) for On – Ethernet link is active

each Ethernet port
Off – Ethernet link is inactive
ACT (blinking Blinking – Ethernet frame received or sent within the

green) for each last second
Ethernet port
Off – No frame received or sent within the last second
LOC (red) for each On – Local sync loss for E1

port (E1 only)
Off – No loss
REM (red) for each On – Remote sync loss for E1

port (E1 only)
Off – No loss
RED (red) for each On – Local sync loss

port (T1)
Off – No loss
Indicators (cont.) YEL (yellow) for On – Remote sync loss

each port (T1)
Off – No loss
Power AC or DC Voltage 100–240 VAC, 50/60 Hz or 48/60 VDC nominal (40–72

VDC)
Power 13W
Consumption
Physical Height 43.7 mm (1.7 in) (1U)
Width 440.0 mm (17.3 in)
Depth 240.0 mm (9.4 in)
Weight 2.2 kg (4.7 lb)
RICi-16 Ver. 2.5 Technical Specifications 1-25

Environment Temperature Regular option:

0 to 50°C (32 to 122°F)
Temperature-hardened option:
-22° to 65°C (-7.6° to 149°F)
Humidity Up to 90%, non-condensing

Chapter 2
Installation and Setup
This chapter includes the following topics:
• Site Requirements and Prerequisites
• Package Contents
• Equipment Needed
• Installation and Setup.
The RICi-16 unit ships completely assembled with factory defaults set for basic
operation. It is designed for installation as a desktop unit or mounting in a
19-inch rack. For rack installation instructions, refer to the Rack Mounting Kit for
19-inch Racks guide that comes with the RM kit.
After installing the unit, use an ASCII terminal connected to the CONTROL port to
perform any configuration necessary. The configuration procedures are described
in Chapter 3 and Chapter 4.
If problems are encountered, refer to Chapter 6.
No internal settings, adjustment, maintenance and repairs should be performed

by either the operator or the user. Such activities must be performed only by
skilled personnel who are aware of the hazards involved.
Warning
Always observe standard safety precautions during installation, operation and
maintenance of this product.
2.1 Site Requirements and Prerequisites

AC-powered units should be installed within 1.5 meters (5 feet) of an easily
accessible grounded AC outlet capable of furnishing the required supply voltage,
in the range of 100 to 240 VAC, 50/60 Hz. DC-powered units require a 48 VDC or
60 VDC nominal standard DC supply. Refer to the Connecting DC Power section at
the front of the manual.
Allow at least 90 cm (36 in) of frontal clearance for operator access. For
continuous product operation allow at least 10 cm of frontal clearance and at
least 15 cm at rear of the unit, for cable connections and ventilation. For proper
ventilation, keep at least 2.5 cm clearance from the sides and top of the product.
The ambient operating temperature of RICi-16 is 0 to 50° C (32 to 122°F), at a
relative humidity of up to 90%, non-condensing.
RICi-16 Ver. 2.5 Site Requirements and Prerequisites 2-1

Chapter 2 Installation and Setup RICi-16 Installation and Operation Manual
2.2 Package Contents

The package contains the following items:
• One RICi-16 with E1/T1/T3 ports
• AC power cord
• DC connector kit
• RM-34 kit for mounting in a 19” rack
• CBL-RJ45/2BNC/E1 RJ-45 to BNC adapter cable, if an unbalanced E1 interface
was ordered.
2.3 Required Equipment

RICi-16 needs no special tools for installation. You need a screwdriver for
mounting the unit in a 19-inch rack.
RICi-16 ships with the appropriate country- or region-specific power cord equipped
with a DC adapter to allow connecting DC power. The power cord connects
RICi-16 to the mains using the power socket on the rear panel.
Refer to the following table to determine which cables are required for
installation. Appendix A specifies all connector pin-outs.
Table 2-1. Required Connection Media
Equipment/Port Cable
Control port Straight RS-232/V.24 cable
Fast Ethernet interface RJ-45 cable

SFP
E1/T1 interface RJ-45 cable

For an unbalanced E1 interface, use the adapter cable
provided
T3 Interface BNC coax cable
2-2 Required Equipment RICi-16 Ver. 2.5

RICi-16 Installation and Operation Manual Chapter 2 Installation and Setup
2.4 Mounting the Unit

For rack installation instructions, refer to the Rack Mounting Kit for 19-inch Racks
guide that comes with the RM kit. A wall-mounting (WM) kit is available upon
request. For wall installations, refer to the Wall Mounting Kit for Installation of
8.5-inch Units.
2.5 Connecting to Ethernet Equipment

The RICi-16 Fast Ethernet interface terminates in an 8-pin RJ-45 connector.
Note When connecting Ethernet and/or Gigabit Ethernet cables longer than 30m, it is
recommended to use shielded cables.
³ To connect RICi-16 to Ethernet equipment:

• Connect the LAN line (RJ-45, 8-pin connector or SFP) to the RJ-45 connector
labeled 10/100BaseT.
Figure 2-1. Ethernet Ports
2.6 Connecting to E1/T1 Equipment

The E1/T1 interfaces terminate in an 8-pin RJ-45 connector.
³ To connect E1 or T1 equipment:
• Connect an E1 or T1 line (RJ-45, 8-pin connector) to the RJ-45 connector
designated E1 or T1 (1-16).
• For unbalanced E1 connections, use the RAD-supplied adaptor.
Figure 2-2. E1/T1 Ports
RICi-16 Ver. 2.5 Connecting to E1/T1 Equipment 2-3

2.7 Connecting to T3 Equipment

The T3 interfaces terminate in BNC coax connectors.
³ To connect T3 equipment:
1. Connect the Rx cable (BNC coax connector) to the BNC labeled Rx.
2. Connect the Tx cable (BNC coax connector) to the associated BNC labeled Tx.
Figure 2-3. T3 Ports
2.8 Connecting to the Terminal

³ To connect the ASCII terminal:
Connect the RS-232 cable (straight RS-232/V.24 connector) to the ASCII terminal
or an out-of-band management station.
Connect the RS-232 cable (DB-9 female connector) to the unit’s CONTROL port
Caution Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to supervisory
terminal port.
Figure 2-4. ASCII Terminal
2.9 Connecting to Power

RICi-16 can accept either AC power or DC power.
Before connecting or disconnecting any communication cable, the unit must be

grounded by connecting its power cord to a power outlet with a ground terminal,
Warning and by connecting the ground terminal on the panel (if provided) to protective
ground.
Any interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal may render this unit
dangerous. Intentional interruption is prohibited.
2-4 Connecting to Power RICi-16 Ver. 2.5

RICi-16 Installation and Operation Manual Chapter 2 Installation and Setup
Connecting to AC Power
AC power is supplied via a standard 3-prong inlet with an integral fuse holder.
AC power should be supplied through the 1.5m (5 ft) standard power cable
terminated by a 3-prong socket. The cable is provided with the unit.
³ To connect AC power:
1. Connect the power cable socket to the power connector on the RICi-16 rear
panel.
2. Connect the power cable plug to mains outlet.
The unit turns on automatically upon connection to the mains.
Figure 2-5. Power Connector
Connecting to DC Power
A special IEC 60320 adapter for 48/60 VDC power connection is supplied with the
unit.
³ To connect to DC power:
For instructions on wiring the DC adapter, refer to the DC power supply
connection supplement located at the end of this manual.
For safety instructions, refer to the Handling Energized Products section at the
beginning of this manual.
RICi-16 Ver. 2.5 Connecting to Power 2-5

Removing/Installing the Hot-Swappable Power Supply Units

You can replace RICi-16’s power supply units in the field whenever necessary.
³ To remove a hot-swappable power supply unit:
To prevent electrocution, DISCONNECT THE POWER SUPPLY CABLE FROM THE

POWER SUPPLY UNIT before removing the power supply unit.
Warning
1. Using a flathead screwdriver, unscrew the two tightening screws that secure
the unit to the chassis.
2. Carefully pull and remove the power supply unit from the chassis.
³ To install the hot-swappable power supply unit:
To prevent electrocution, KEEP THE POWER SUPPLY CABLE DISCONNECTED FROM

THE POWER SUPPLY UNIT until it has been fully installed.
Warning
Caution Do not install the RICi-16 power supply units in other products. The power supply
units are intended solely for RICi-16.
3. Carefully slide the new power supply into its slot until the unit's rear
connector engages the mating connector on the backplane, and the power
supply unit fits into place.
4. Using a flathead screwdriver, secure the power supply unit with the two
tightening screws.
2-6 Connecting to Power RICi-16 Ver. 2.5

Chapter 3
Operation
This chapter:
• Explains how to power RICi-16 up and down.
• Provides a detailed description of the front panel controls and indicators and
their functions.
• Provides instructions for using a terminal connected to the RICi-16 control
port.
• Describes how to navigate menus.
• Defines the configuration alternatives.
For a detailed explanation of parameters in the menus, see Chapter 4.
3.1 Turning On the Unit

 To turn on the unit:
• Connect the power cord to the mains.
The PWR indicator turns on and remains on as long as RICi-16 receives
power.
Once installed, RICi-16 requires no operator attention, except for occasionally
monitoring the front panel indicators. Intervention is only required when the unit
must be configured to its operational requirements, or when diagnostic tests are
performed.
RICi-16 Ver. 2.5 Turning On the Unit 3-1

Chapter 3 Operation RICi-16 Installation and Operation Manual
3.2 Indicators
The unit's LEDs are located on the front panel. Table 3-1 lists the functions of
the LED indicators.
Figure 3-1. RICi-16 Front Panel with T3 Connectors
Table 3-1. RICi-16 LEDs and Controls
Name Color Function
POWER Green On – Unit is powered

Off – Unit is off
TST Yellow On – Self test or diagnostics underway

Off – no test running
ALM Red On – interface alarm detected

Off – no alarm currently detected
LOC for each E1 port Red On – Local sync loss

Off – No loss
REM for each E1 port Red On – Remote sync loss

Off – No loss
RED for each T1 port Red On – Local sync loss

Off – No loss
YEL for each T1 port Yellow On – Remote sync loss

Off – No loss
LINK for each Ethernet Green On – Ethernet link is up

port Off – Ethernet link is down
ACT for each Yellow Blinking – Ethernet frame received or sent within
Ethernet port the last second
Off – No frame received or sent within the last
second
3-2 Indicators RICi-16 Ver. 2.5

RICi-16 Installation and Operation Manual Chapter 3 Operation
3.3 Default Settings

Configuration parameters in RICi-16 may or may not have default values.
Configuration parameters that have default values fall into one of two categories:
• Set/configured defaults – For example, terminal bit rate, which is auto-detect
and set on power up. These defaults are presented on the screen.
• Not set/configured defaults – These defaults are not visible when entering
the screen and are presented by a blank field. They show up after a ‘Save’
operation is done in the particular screen. For example, the ingress filtering
parameter shows the default value after changes in the bridge configuration
screen are saved.
Configuration parameters that do not have default values must have values
entered in their respective fields, or the Save operation will fail.
Table 3-2 lists the default settings of the RICi-16 configuration parameters.
Table 3-2. Default System Settings
Type Parameter Default Value
System
Host Default gateway 0.0.0.0
Default IP 0.0.0.0
DHCP Disable
IP address 0.0.0.0
IP mask 255.255.255.0
Read community Public
Trap community Public
Write community Private
Device Info Contact Person Name of the contact person
Description Fast Ethernet over 16 NTU

HW Ver: 0.0, SW 2.10
Location The Location of the device
Name RICi-16
Management Access SNMP access Enable
Telnet/ SSH access Enable
Web access Enable
User Access User name for superuser su (full control)
User name for guest user user (read-only)
RICi-16 Ver. 2.5 Default Settings 3-3

Encapsulation Host Tagging Untagged
Host VLAN ID 1
Host VLAN Priority 0
Alarm Trap Mask Alarm ID 1
Trap Status Active
Control Port Baud Rate 9600 bps
Set Scrolling Window Size 4
Security Timeout 10
Network Interface Network Operation Mode T3

Note: Applicable only for unit
with T3 ports
Physical Ports
Ethernet User Administrative Status Up
Autonegotiation Enable
Flow Control Enable
Max Capability Advertised 100base – TX Full Duplex
MDIX Auto Cross Over Enable
E1 Administrative Status Up
Interface Type Balanced
Line Code HDB3
Line Type G732N-CRC
Receiver Sensitivity Long haul
Restoration Time Immediate
Transmit Clock Source System
T1 Administrative Status Up
Line Type ESF
Line Interface CSU
Line BuildOut 0 dB
Line Code B8ZS
Receiver Sensitivity Long haul
Restoration Time 1 Sec
Transmit Clock Source System
T3 Administrative Status Up
Clock System
3-4 Default Settings RICi-16 Ver. 2.5

Line type M23
Line length Up to 225ft
Structure Channelized
Application Layer
Bridge Aging Time 300
Bridge Ports 1 = Reserved for management host

2 = Ethernet 1
3 = Ethernet 2
4 = Ethernet 3
5 = Ethernet 4
6 = GFP1
Forwarding Mode Filter
VLAN Mode Unaware
Bridge Port Activation Enable
Accept Frame Type All
Copy Original Priority Disable
Default Priority Tag --
Egress Tag Handling None
Ingress Filtering Disable
Ingress Tag Handling
Bridge Port Copy Origin Priority Disable
Default Priority 0
Port VID/Stacking VID 2
VLAN Tag Stacking Disable
3.4 Configuration and Management Alternatives

Configuration and monitoring operations are performed locally from an ASCII
terminal connected to the control port or from a PC running a Web browser.
Working with Terminal

RICi-16 includes a V.24/RS-232 asynchronous DTE port designated CONTROL that
utilizes a 9-pin D-type female connector. The control port continuously monitors
the incoming data stream and immediately responds to any input string received.
The control port can be configured to communicate at 9.6, 19.2 or 115.2 kbps.
RICi-16 Ver. 2.5 Configuration and Management Alternatives 3-5

 To start a terminal control session:

1. Make sure all relevant communication cables and connectors are properly
connected. Refer to Chapter 2 for installation and setup procedures.
2. Connect the RS-232 cable (straight RS-232/V.24 connector) to the ASCII
terminal emulation application on the PC.
3. Connect the RS-232 cable (DB-9 female connector) to the RICi-16 unit’s
CONTROL port. The default settings are as follows:
Baud Rate: 9600 bps

Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None
4. To optimize the view of the system menus:
 Set the terminal emulator to VT100.
 If you are using HyperTerminal, set the terminal mode to the 132-column
mode.
5. After the initialization and the self-test passed successfully, a menu appears
displaying initialization and self-test results.
Logging In
 To log in:
1. Use su as user name with read/write permission.
2. Use 1234 as the (default) password for the first login.
Note It is recommended to change default passwords to prevent unauthorized access

to the unit.
Choosing Options
This section explains how to select options and save changes.
 To select an option:
1. Type the number corresponding to the option and press <Enter>.
2. If you performed a change, Save appears as the last option in the menu.
3. Type the number corresponding to the Save option in the current menu, and
press <Enter> to save your change.
RICi-16 updates its database with the new value or displays a new menu
for the selected option.
4. To exit the menu, press <ESC>.
The following message appears:
Do you want to save changes (Y/N/C)?
3-6 Configuration and Management Alternatives RICi-16 Ver. 2.5

Type the appropriate letter for Yes, No, or Cancel.
Note When a menu option has only two values, typing the option number and pressing
<Enter> will toggle between the available values.
Screen Example
Figure 3-2 illustrates a typical screen, displaying the main items.
Product Title (RICi-16)
Menu Path
1. Sub Menu>
2. Sub Menu>
3. Parameter X [Range] …… (value)
4. Parameter Y> (Select value from the list)
5. Table Z []
prompt>
Help line message
Help line of keyboard shortcuts, such as “Esc-prev” for
returning to the previous menu
-----------Division screen line ------------------
Scroll messages
Figure 3-2. Sample Screen
Navigating Tables
Some of the management screens, such as the Inventory table and Manager
table, exceed the size of regular menu screens and require scrolling to navigate
between parameters. These screens are best viewed when your terminal screen is
set to 132 character width.
Use the following keys (case-sensitive) for table navigation:
<Ctrl+L>: scroll left, Left Arrow – move left

<Ctrl+R>: scroll right, Right Arrow – move right
<Ctrl+U>: scroll up, Up Arrow – move up
<Ctrl+D>: scroll down, Down Arrow – move down
<Tab>: select the next changeable cell
G<row number>, go to the specified cell
<col number>:
Note
You can display these navigation keys by typing <?> from a table.
The following figure illustrates an empty VLAN table. VIDs and Names are the
columns of the parameters to be defined.

RICi-16
VLAN Table
1. VID | NAME |
>
ESC-prev. menu; !-main menu; &-exit; ?-Help 1 user (s)
Figure 3-3. Sample Table Screen (VLAN)
Working with the Web Browser

RAD’s Web-based remote access terminal management software provides a user-
friendly interface for configuring, collecting statistics and performing diagnostic
tests on the unit.
The management software supports the following browsers:
• Internet Explorer 6.0 and up, running on Windows™
Note In order to work with Internet Explorer 8 and Internet Explorer 9, you must enable
the “work in compatibility” mode.
 Before you start using a Web browser for remote management or monitoring:
• Enable scripts.
• Configure the firewall that might be installed on your PC to allow access to
the destination IP address.
• Disable pop-up blocking software, such as Google Popup Blocker. You may
also have to configure spyware and adware protecting software to accept
traffic from/to the destination IP address.
• To prevent configuration errors, you must clear out the files stored in your
browser cache whenever you return to the same screen.
Logging In
 To log in from a Web browser:
1. Connect the Ethernet port to the LAN. Refer to Chapter 2 for information
about connecting to Ethernet equipment.
2. Verify that an IP address has been assigned to the relevant unit, using an
ASCII terminal (see Working with Terminal)
3. Open the Web browser.
4. Disable any pop-up blocking software, such as Google Popup Blocker.
5. In the address field, enter the IP address of RICi-16 and then press <Enter>.
The address line reads something like http://172.16.100.253.
The Opening window appears.
6. Click LOGIN; you are asked for the user name and the password.
3-8 Configuration and Management Alternatives RICi-16 Ver. 2.5

7. Enter your user name and the password. The default user name for
read/write permission is su and the default password is 1234.
The Web browsers Main menu appears.
Notes • It is recommended to change default passwords to prevent unauthorized

access to the unit.
• RICi-16 allows six management sessions to be active simultaneously: five
network sessions (Telnet, Web, RADview-Lite) and one ASCII terminal session.
• If no user input is detected for 5 minutes during a Web session,
RICi-16 automatically disconnects from the management station.
Navigating the Web Browser Menus

At the left-hand bottom corner, the Web browser provides auxiliary management
tools:
Status: displays the number of users currently managing the unit

Trace: opens an additional pane for system messages, progress
indicators (ping, software and configuration file downloads) and
alarms
Refresh All: refreshes the data currently displayed
 To choose an option:
1. Click a link in the Web screen to display the next menu.
2. Once the target screen is displayed, select a value from the drop-down box or
enter it in a text box.
Working with RADview

RADview-EMS is a user-friendly and powerful SNMP-based element management
system (EMS), used for planning, provisioning, and managing heterogeneous
networks. RADview-EMS provides a graphical user interface for monitoring RAD
products via their SNMP agents.
RADview-EMS for RICi-16 is bundled in the RADview-EMS/NGN package for PC
(Windows-based) or UNIX.
For more details about this network management software, and for detailed
instructions on how to install, set up, and use RADview, contact your local
distributor or refer to the RADview-EMS User's Manual, located on the Technical
Documentation CD

3.5 Menu Maps

Once you have logged into RICi-16 via an ASCII terminal or Web Terminal, navigate
the hierarchical menus to set and view the unit’s configuration parameters, and
perform other essential operations.
Figure 3-4 shows the actual main menu in an ASCII terminal screen. All system
configuration and control functions are access via this menu.
RICi-16 – RAD Data Communications
Main Menu
1. Inventory >
2. Configuration >
3. Monitoring >
4. Diagnostics >
5. Utilities >
>
Please select item <1 to 5>
ESC-Previous menu; !-Main menu; &-Exit
Figure 3-4. Main Menu for RICi-16 (Terminal Screen)

The main menu options are:
Inventory (type 1) View system information, HW/SW versions and HW
configuration
Configuration (type 2) Set and configure all parameters required for the
operation of RICi-16
Monitoring (type 3) Monitor system performance and statistics
Diagnostics (type 4) Perform diagnostics
Utilities (type 5) Upload/download application files, configuration files
and backup files
The figures on the following pages summarize the menus available in the menu
map.
Note Not all menus illustrated in the menu map are actually available. Available menus
depend on the configuration you purchased.
3-10 Menu Maps RICi-16 Ver. 2.5

Configuration Menu
The following figures summarize the paths available for the configuration options:
Figure 3-5. Main Menu > Configuration >System 1
RICi-16 Ver. 2.5 Menu Maps 3-11

Figure 3-6. Main Menu > Configuration >System 2

Figure 3-7. Configuration > Physical Layer
Figure 3-8. Configuration > Logical Layer

Figure 3-9. Configuration > Applications 1

Figure 3-10. Configuration > Applications 2

Monitoring Menu
The following figures summarize the paths available for the monitoring options:
Figure 3-11. Main Menu > Monitoring > System

Figure 3-12. Main Menu > Monitoring > Physical Port
Figure 3-13. Main Menu > Monitoring > Logical Layer

Figure 3-14. Main Menu > Monitoring > Applications
Diagnostics Menu
The following figure summarizes the paths available for the diagnostics options:
Figure 3-15. Main Menu > Diagnostics

Utilities Menu
The following figure summarizes the paths available for the additional tasks
options:
Figure 3-16. Main Menu > Utilities
3.6 Turning Off the Unit

 To turn off the unit:
• Remove the power cord from the power source.
RICi-16 Ver. 2.5 Turning Off the Unit 3-19

3-20 Turning Off the Unit RICi-16 Ver. 2.5

Chapter 4
Configuration
This chapter describes how to configure RICi-16 for management and operation.
Configuration screens are illustrated and configuration parameters explained.
Note The configuration screens illustrated in this chapter are taken from a terminal
screen, but most of the menus are similar to those viewed in Telnet and the
Web-based management application.
This chapter includes the following sections:

• Configuring RICi-16 for Management
• Configuring RICi-16 for Operation
• Performing Additional Tasks.
For instructions on accessing and navigating the screens, and a complete list of
all menu items, see Chapter 3.
4.1 Configuring RICi-16 for Management
Entering Device Information

The RICi-16 management software allows you to assign a name to the unit and
specify its location to distinguish it from other units installed in your system. A
contact person can also be assigned.
³ To enter device information:

1. From the Main menu, navigate to Configuration > System > Management >
Device Information.
The Device Information menu appears as illustrated in Figure 4-1
Note The description of the unit is factory-set and cannot be changed.
RICi-16 Ver. 2.5 Configuring RICi-16 for Management 4-1

Chapter 4 Configuration Installation and Operation Manual
RICi-16
Configuration > System > Management > Device Information
Description (Ethernet over Bonded PDH Network Termination Unit)

(HW Ver: x.x, SW Ver: x.xx)
1. Name ... (RICi-16)

2. Location ... (The Location of the Device)
3. Contact ... (Name of Contact Person)
>
s - Save
ESC-Previous menu; !-Main menu; &-Exit;
Figure 4-1. Typical Device Information Menu
2. Select Name, and type a name for the unit. The default name is
RICi-16.
3. Select Location, and type a location name/description.
4. Select Contact, and type the name of a contact person for this unit.
5. Select Save.
Configuring Host IP Parameters

You can manage RICi-16 via a network management station connected to one of
the unit’s ports. To establish a proper connection, it is necessary to configure the
Host parameters such as the IP address. In addition, by selecting a forwarding
mode and VLAN parameters, it is possible to create a separate management
VLAN.
³ To define the Host parameters:

Host.
The Host menu appears as illustrated in Figure 4-2.
RICi-16
Configuration > System > Management > Host
1. IP Address ... (0.0.0.0)

2. Mask ... (255.255.255.0)
3. Default gateway ... (0.0.0.0)
4. Read community ... (public)
5. Write community ... (private)
6. Trap community ... (public)
7. Encapsulation >
>
s - Save
ESC-Previous menu; !-Main menu; &-Exit; 1 user(s)
Figure 4-2. Host Menu
4-2 Configuring RICi-16 for Management RICi-16 Ver. 2.5

Installation and Operation Manual Chapter 4 Configuration
2. Select IP Address and enter the IP address of the IP host.

3. Select Mask and enter the host IP subnet mask.
4. Select Default Gateway and enter the default gateway IP address.
5. Select Read Community and type the name of a community with read-only
authorization.
6. Select Write Community and type the name of a community with write
authorization.
7. Select Trap Community and type the name of a community to which the unit
should send traps.
8. Select Encapsulation to define VLAN tagging performed by the host.
The Encapsulation menu appears as illustrated in Figure 4-3.
RICi-16
Configuration > System > Management > Host > Encapsulation
1. Host tagging (Tagged)

2. Host VLAN ID [1-4094] ... (2)
3. Host Priority Tag [0-7] ... (0)
>
s - Save
Figure 4-3. Encapsulation Menu
9. Select Host Tagging and toggle between Untagged and Tagged.

Untagged – The host sends and receives frames with no VLAN tag
to/from the bridge.
Tagged – The host receives frames only if they are tagged with the host’s
VLAN ID, and it sends frames to the bridge with this tag.
Note When Host Tagging is set to Tagged, two parameters are added to the menu:
Host VLAN ID and Host Priority Tag.
10. Select Host VLAN ID to specify the host VLAN ID (1–4094).

11. Select Host Priority Tag to specify the priority level for the host VLAN (0–7).
12. Select Save.
13. Return to the Host menu and select Save again.

Configuring SNMPv3
RICi-16 supports SNMP version 3 entity, providing secure SNMP access to the
device by authenticating and encrypting packets transmitted over the network.
Follow these steps to configure the SNMPv3 entity:
1. Configuring the SNMP Engine ID
2. Enable SNMPv3.
3. Define SNMP engine ID
4. Add a new user.
5. Add a new notification entry.
6. Assign traps to notification entries.
7. Configure target (NMS) parameters.
8. Specify target address, define its parameter set and assign notification tags.
9. Map SNMPv3 setting to SNMPv1 settings (if necessary).
Configuring the SNMP Engine ID

Engine ID is an alphanumeric string used for identification of the RICi-16 agent in
the SNMPv3 environment. The engine ID must be unique to allow the user to
query the SNMP engine. It must be defined prior to enabling SNMPv3
functionality. The length of the string is up to 27 characters.
³ To define the SNMP engine ID:
1. Navigate to the SNMP Engine ID menu (Configuration > System >
Management > SNMP Engine ID),
2. Select Remaining Bytes and define the value of the engine ID section reserved
for user SNMP engine identification.
The value is automatically translated in hexadecimal format and displayed
in the read-only Engine ID field.
RICi-16
Configuration > System > Management>SNMP Engine ID
Engine ID, ... (800000a40400000000)

Engine ID Config Type > (Text)
1. Remaining Bytes ... (2)
>
S - Save
Figure 4-4. SNMP Engine ID Menu
3. Select Save.

Enabling SNMPv3
³ To enable SNMPv3:
1. From the Management menu (Configuration > System > Management), select
SNMPv3 and then select Save.
A warning message is displayed advising that the current configuration of
SNMP agent will be deleted.
2. Select Y to continue or N to cancel.
Once enabled, the SNMPv3 Settings line is added to the Management
menu as illustrated in Figure 4-5.
RICi-16
Configuration > System > Management
1. Device Information >

2. SNMPv3 (Enabled)
3. Host >
4. Managers List []>
5. SNMP Engine ID >
6. SNMPv3 Setting >
7. Management Access >
>
s - Save
Figure 4-5. Management Menu
3. From the Management menu, select SNMPv3 Settings.

The SNMPv3 Settings menu is displayed as illustrated in Figure 4-6.
RICi-16
Configuration > System > Management>SNMPv3 Setting
Engine Boots (2)

Engine Time (276)
SNMP Message Size ... (1500)
1. Users >
2. Targets & Notify >
3. SNMPv1/v3 Mapping >
4. SNMPv3 Factory Defaults
5. Summary User Table []
6. Summary Target Table []
>
Figure 4-6. SNMPV3 Settings Menu

Adding SNMPv3 Users

RICi-16 supports up to ten SNMPv3 managers with different authorization and
privacy attributes.
Note Access control policy is defined via the vacmSecurityToGroupTable and

vacmAccessTable tables, which can be accessed via an SNMP browser only.
³ To add an SNMPv3 user:

1. From the SNMPv3 Settings menu (Configuration > System > Management >
SNMPv3 Settings), select Users.
The SNMPv3 Settings menu appears.
2. Select Security Name and enter security name for a new user (up to 32
alphanumeric characters).
The Privacy Protocol, Authentication Password and Privacy Password lines are
added to the SNMPv3 Users menu as illustrated in Figure 4-7.
RICi-16
Configuration > System > Management>SNMPv3 Settings>Users
1. Security Name ... (1)

2. Authentication Protocol > (usmHMACM5AuthProtocol)
3. Privacy Protocol > (usmDESPrivProtocol)
4. Authentication Password ... []
5. Privacy Password ... []
>
F–Forward; B–Back; R–Remove; S-Save
Figure 4-7. SNMPv3 Users Menu
3. Select Authentication Protocol and define the authentication protocol to be

used for authenticating the user:
usmNoAuthProtocol (No authentication is performed)
usmHMACMD5AuthProtocol (MD5 protocol)
usmHMACSHAAuthProtocol (SHA protocol)
4. Select Privacy Protocol and define the type of privacy protocol to be used for
encryption:
usmNoPrivProtocol (Privacy protocol is not used)
usmDESPrivProtocol (DES protocol)
5. Select Authentication Password and define the authentication password of
the user. This is not available if authentication has been disabled.
6. Select Privacy Password and define the private key used for encryption. This is
not available if privacy has been disabled.
Note Minimum password length is at least 8 characters long.

7. Select Save.
³ To view the summary of the SNMPv3 user configuration:

• From the SNMPv3 Settings menu (Configuration > System > Management >
SNMPv3 Settings), select Summary User Table.
³ To delete an SNMPv3 user:

• From the Users menu (Configuration > System > Management > SNMPv3
Settings > Users), perform the following:
Type F (Forward) or B (Back) to select an SNMPv3 user.
Type R (Remove) to delete the selected user.
Adding SNMPv3 Notification Entries

You can define which types of notification will be sent to the target management
stations (the target stations are defined separately, as explained in Configuring
Target Parameters).
³ To define a notification entry:

SNMPv3 Settings), select Targets & Notify.
2. Select Notify.
The Notify menu is displayed as illustrated in Figure 4-8.
3. From the Notify menu, define the following:
Name – up to 60 characters (ASCII string identifying the notification
entry)
Tag – 0-255 (A tag value to be associated with the current notification
entry. This tag is used to identify the current notification entry when
configuring the target address).
RICi-16
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Notify
Type > (Trap)
1. Name ...()
2. Tag ...()
>
F-Forward B-Backwards R- Remove
ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
Figure 4-8. Notify Menu
4. Select Save.
³ To delete a notification entry:

• From the Targets & Notify menu (Configuration > System > Management >
SNMPv3 Settings > Targets & Notify), select Notify.

Type F (Forward) or B (Back) to select a notification entry.

Type R (Remove) to delete the selected entry.
Assigning Traps
One or more traps must be assigned to each notification entry.
³ To assign traps to notification entries:

1. From the Target & Notify menu (Configuration > System > Management >
SNMPv3 Settings > Targets & Notify), select Trap.
The Trap menu is displayed as illustrated in Figure 4-9.
2. From the Trap menu, define the following:
Tag Name (A tag from the list of previously defined notification tags)
Trap (A trap to be assigned to the selected tag).
RICi-16
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Trap
1. Tag Name > (Power Failure)

2. Trap > (1)
>
F-Forward B-Backwards R-Remove
Figure 4-9. Trap Menu
³ To delete a trap:
SNMPv3 Settings > Targets & Notify), select Trap.
Configuring Target Parameters

Target is an SNMPv3 network management station to which RICi-16 is going to
send trap notifications. A set of parameters has to be configured and assigned to
each target.
³ To configure target parameters:

1. From the Targets & Notify menu (Configuration > System > Management >
SNMPv3 Settings > Targets & Notify), select Target Params.
The Target Params menu is displayed as illustrated in Figure 4-10.
2. From the Target Params menu, configure the following:
Name (An ASCII string identifying current set of target parameters)
Message Processing Model (The Message Processing Model to be used
when generating SNMP messages using this entry):

SNMPv1
SNMPv2c
SNMPv2u
SNMPv3
Security Model (The Security Model to be used when generating SNMP
messages using this entry):
Any
SNMPv1
SNMPv2c
User-Based Security Model (USM)
Not defined
Security Name (Identification of the principal on whose behalf SNMP
messages are to be generated using this entry. This can be either
SNMPv3 user or SNMPv1/SNMPv2 community string.)
Security Level (The level of security to be used when generating SNMP
messages using this entry):
noAuthNoPriv (Authorization and privacy are disabled)
authNoPriv (Authorization is enabled, privacy is disabled)
authPriv (Authorization and privacy are enabled)
RICi-16
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Params
1. Name ... (11)

2. Message Processing Model > (SNMPv1)
3. Security Model > (Any)
4. Security Name ... ()
5. Security Level > (noAuthNoPriv)
>
Figure 4-10. Target Params Menu
3. Select Save.
³ To delete a target parameter:

SNMPv3 Settings > Targets & Notify), select Target Parameters.

Configuring Target Address

Each target must have a valid IP address, IP mask. In addition, a previously
configured parameter set and notification tags must be assigned to the target.
³ To configure the target address:

1. From the Targets & Notify menu (Configuration > System > Management >
SNMPv3 Settings > Targets & Notify), select Target Address.
The Target Address menu is displayed as illustrated in Figure 4-11.
2. From the Target Address menu, configure the following:
Name (ASCII string identifying the target)
IP Address (Valid IP address of the NMS. Must be in the
xxx.xxx.xxx.xxx:162 format, where 162 is a standard SNMP port used for
sending traps)
Params Name (List of previously defined target parameter names)
Address Mask (An IP mask of the NMS)
Tag List (List of previously defined notification tags).
3. Select Save.
³ To view the summary of the SNMPv3 target configuration:

• From the SNMPv3 Settings menu (Configuration > System > Management >
SNMPv3 Settings), select Summary Target Table.
RICi-16
Configuration>System>Management> SNMPv3 Settings> Target & Notify > Target Address
1. Name ... (11)

2. IP Address ... (0.0.0.0)
3. Params Name ... (param1)
4. Tag List ... (traps)
>
F-Forward B-Backwards R-Remove>
Figure 4-11. Target Address Menu
³ To delete a target address:

SNMPv3 Settings > Targets & Notify), select Target Address.
Mapping SNMPv1 to SNMPv3

RICi-16 supports coexistence of different SNMP versions by mapping
SNMPv1/SNMPv2 community name to the SNMPv3 security name value. The
mapping is performed according to the RFC 3584 requirements.

³ To map SNMPv1 to SNMPv3:

SNMPv3 Settings), select SNMPv1/v3 Mapping.
The SNMPv1/v3 Mapping menu is displayed as illustrated in Figure 4-12.
2. From the SNMPv1/v3 Mapping menu, define the following:
Community Index (SNMP community index)
Community Name (SNMPv2/SNMPv2 community name)
Security Name (SNMPv3 security name to be mapped to the
SNMPv2/SNMPv2 community name)
Transport Tag (Specifies a set of the transport endpoints that are used,
in either of the following methods:
Specifying the transport endpoints from which an SNMP entity
accepts management requests
Specifying the transport endpoints to which a notification may be
sent, using the community string matching the corresponding
instance of community name.
RICi-16
Configuration>System>Management>SNMPv3 Settings>SNMPv1/v3 Mapping
1. Community Index ... ()

2. Community Name ... ()
3. Security Name ... ()
4. Transport Tag ... ()
>
Figure 4-12. SNMPv1/v3 Mapping Menu
3. Select Save.
Configuring Management Access

RICi-16 allows you to enable or disable remote access via an SNMP, Telnet and
Web to the I2C management system. By disabling remote management access,
you prevent unauthorized access to the system when security of the unit's IP
address has been compromised. You can allow users to be defined on a Radius
server, which is an easily accessible and centralized server from which RICi-16
units (as well as other units that support Radius) can authenticate individual
users and their passwords. You can set the availability and priority of both the
Radius and local (terminal) login methods via the unit's general access policy.
In addition, you can limit access to the device to only those stations defined in
the managers list. The Managers List menu details management access
implementation, depending on whether the network managers are defined or not
as illustrated in Figure 4-16

Note When remote management access is disabled, RICi-16 can be managed via a
direct ASCII-based terminal connection only.
³ To configure management access:

Management Access.
The Management Access menu appears as illustrated in Figure 4-13.
RICi-16
Configuration > System > Management > Management Access
1. User Access >

2. RADIUS Parameters >
3. Telnet > (Enable)
4. SSH Access > (Enable)
5. SNMP Access > (Enable)
6. WEB Access > (Enable)
7. Access Policy >
>
S – Save
ESC-Previous menu; !-Main menu; &-Exit 1 M/ 1 C
Figure 4-13. Management Access Menu
2. From the Management Access menu, select the access level you wish to
change and then select the access permission setting for the selected access
level (see
Table 4-1. Management Access Options
Parameter Description Possible Value
Telnet Access using Telnet Enable - Telnet access is enabled

Disable - Telnet access is disabled
Managers Only - Access is enabled
only for the management stations
SSH Access Access using Secure Shell Enable - Secure Shell access is
enabled
Disable - Secure Shell access is
disabled
SNMP Access Access using an SNMP Enable - SNMP access is enabled

client such as RADview Disable - SNMP access is disabled

WEB Access Access via Web based Enable - Web access is enabled
interface using a Web Disable - Web access is disabled
browser
listed in the manager list
Enable Secure - Secure access
enabled via Secure Shell (SSH) or
Secure Socket Layer (SSL) for
anybody
Manager Only Secure - Secure access
enabled via Secure Shell (SSH) or
Secure Socket Layer (SSL) for
management stations listed in the
manager list
Note
Available access permission settings depend on the access level selected in the
Management Access menu
3. Select Save.
Configuring the Radius Server Parameters

RICi-16 provides connectivity to up to four Radius authentication servers. If
RICi-16 is required to authenticate users via a centralized Radius server in any
given application, the required parameters must be configured.
³ To configure the Radius server parameters:

1. From the Management Access menu (Configuration > System > Management >
Management Access), select Radius parameters.
The Radius Parameters menu is displayed as illustrated in Figure 4-14.
RICi-16
Configuration> System> Management> Management Access> Radius parameters
Server sequence number (1)

Server status > (Not Connected)
1. Server access (Disable)
2. Server IP address ... (100.150.200.50)
3. Key string ... (****)
4. Number of retries [0-10] ... (2)
5. Timout (in seconds) [1-5] ... (2)
6. Authentication port [1-65535] ... (1812)
>
F-Forward B-Backwards
ESC–previous menu; !–main menu; &-exit
Figure 4-14. Radius Parameters Menu
2. Define the following Radius parameters:

Table 4-2. Radius Parameters
Server Access Enable or disable the specific Radius Enable

server which details are displayed Disable
Server IP Address IP address of this Radius server 0.0.0.0
Key String Non-disclosed string used to encrypt

the user password
Number of Retries Maximum number of times an 0-10

authentication request should be re-
sent to the server in case of no
response
Timeout (secs) Period in seconds during which RICi- 1-5

16 waits for a response from the
Radius server
Authentication Port UDP port number used for the 1-65535

authentication channel
3. Select Save
4. To switch to additional Radius servers, select <F> Forward or Backward
respectively.
Defining the Access Policy

Access policy allows configuration of multiple authentication protocols. User
authentication is performed in the order the methods are selected. If the first
authentication method is not available or the user is not found, the next selected
method is used.
³ To define the access policy:

1. From the Management Access menu (Configuration > System > Management >
Management Access), select Access Policy.
The Access Policy menu is displayed as illustrated in Figure 4-15.
RICi-16
Configuration> System> Management> Management Access> Access policy
1. 1st level > (Radius)

2. 2nd level > (Local)
>
S-Save
Figure 4-15. Access Policy Menu
2. Configure the following:

1st Level (First level of authentication):

RADIUS (RICi-16 uses authentication database stored on the RADIUS

server)
Local (RICi-16 uses locally stored authentication database)
2nd Level (Second level of authentication. Available only when the 1st
level authentication is set to RADIUS):
None (Second authentication level is disabled; access to RICi-16 is
allowed using the 1st level method only)
Local (RICi-16 uses locally stored authentication database)
3. Select Save.
Configuring Network Managers

You can define or modify the network management stations to which the SNMP
agent of the RICi-16 sends traps. Up to ten managers can be defined. Entering
the IP address defines each management station. The manager list defines the
network management stations that will receive these traps. In addition, you can
temporarily prevent a manager station from receiving traps by masking the
network manager.
Note This option is only available if SNMPv3 is disabled.
³ To define the manager list:

1. From the Management menu (Configuration > System > Management), select
Managers List.
The Managers List menu is displayed as illustrated in Figure 4-16.
RICi-16
Configuration>System>Management>Managers List
Manager ID Manager IP Manager Trap Mask

1 0.0.0.0 Unmasked
2 0.0.0.0 Unmasked
3 0.0.0.0 Unmasked
4 0.0.0.0 Unmasked
5 0.0.0.0 Unmasked
6 0.0.0.0 Unmasked
7 0.0.0.0 Unmasked
8 0.0.0.0 Unmasked
9 0.0.0.0 Unmasked
10 0.0.0.0 Unmasked
1. Change cell ... (0.0.0.0)
>
ESC-prev.menu; !-main menu; &-exit 1 user(s)
Figure 4-16. Managers List Menu
Table 4-3 describes the IP address and the Trap mask fields in the Managers List
menu as illustrated in Figure 4-16.

Table 4-3. Managers List Values
IP Address The manager’s IP address

Default: 0.0.0.0
Trap Mask Masks and unmasks traps to the Masked

Manager. Trap Mask is always on but Unmasked
access is only possible when the IP
address is provided
Default: Unmasked
2. The list contains 10 entries. Use the Tab key to select the next changeable
cell.
3. To change the IP value of a cell, select the field (it will appear highlighted),
then choose Change Cell and enter the new IP value.
4. To change the Trap Mask value of a cell, select the field (it will appear
highlighted), then choose Change Cell for Masked, or choose Change Cell again
for Unmasked.
4.2 Configuring RICi-16 for Operation

Configuring RICi-16 for operation entails setting the following parameters:
• System level parameters:
Clock source
Date and time
Interface groups
Syslog
Fault propagation
Application mode, selecting the Bridge or Flows mode
Operational mode, select the E1/T1 or T3 mode
• Physical layer parameters:
Fast Ethernet interfaces
• Application layer parameters:
Bridge
QoS
Flows
OAM.
4-16 Configuring RICi-16 for Operation RICi-16 Ver. 2.5

Setting System-Level Parameters

This section includes procedures for setting the clock source, setting date and
time, defining interface groups, viewing syslog information, configuring fault
propagation and selecting the network application and operation mode.
Selecting the Clock Source

Transmitted data can be clocked either from an internal clock within the RICi-16
unit, or from an external clock via the E1/T1/T3 ports.
In channelized T3 network mode the device has two system clocks, one for the
T1 ports and one for the T3 ports. In unchannelized T3 mode, only the T3 clock is
active. In T1 network mode, only the T1 clock is active.
The unit can be assigned two sources for timing:
Master Source: main clock source

Fallback Source: activated when the master source fails (for example, when
the E1/T1 link supplying the timing fails).
It is recommended to assign different clock types for the master and fallback
clock sources, for example: Rx Clock (external) for the master source and Internal
for the fallback source.
If the fallback source fails, the internal source takes over.
³ To select the master clock source:

1. Navigate to Configuration > System > Source Clock > Master Clock.
The Master Clock menu appears (see Figure 4-17 and Figure 4-18). If the
unit has T3 network mode and channelized T3 structure, the menu
indicates it is the T1 clock.
2. Select Source and choose the master clock source:
Internal: for setting the internal clock as the master clock source
Rx Clock: for setting an external clock (from E1/T1/T3 link) for the
master clock source.
3. If you chose Rx Clock, specify the port to be used:
E1/T1 Port 1–16: for configuring the E1/T1 master clock source
T3 Port 1–2: for configuring the T3 master clock source.
Note
For T1 clock in channelized T3 mode, RX sources are the internal T1 channels
1-28
4. Select Save to save the clock source settings.

5. If the unit starts in T3 network mode and channelized T3 structure, type f to
advance to the T3 master clock source, and repeat steps 2 through 4 to
configure the T3 master clock source.
RICi-16 Ver. 2.5 Configuring RICi-16 for Operation 4-17

³ To select the fallback clock source:

1. Navigate to Configuration > System > Source Clock > Fallback Clock.
The Fallback Clock menu appears (see Figure 4-19 and Figure 4-20). If the
unit has T3 network mode and channelized T3 structure, the menu
indicates it is the T1 clock.
2. Select Source and choose the fallback clock source:
Internal: for setting the internal clock as the fallback clock source
Rx Clock: for setting an external clock (from E1/T1/T3 link) for the
fallback clock source
3. If you chose Rx Clock, specify the port to be used:
E1/T1 Port 1–16: for configuring the E1/T1 fallback clock source
T3 Port 1–2: for configuring the T3 fallback clock source
4. Select Save to save the clock source settings.

5. If the unit starts in T3 network mode and channelized T3 structure, type f to
advance to the T3 fallback clock source, and repeat steps 2 through 4 to
configure the T3 fallback clock source.
RICi-16
Configuration > System > Source Clock > Master Clock
System Clock (T1)

1. Source (Internal)
>
f - Forward
Figure 4-17. Master Clock Menu, T3 Network Mode and Channelized T3 Structure
RICi-16
Configuration > System > Source Clock > Master Clock
>
Figure 4-18. Master Clock Menu, E1 Interface or T1 Network Mode or

Unchannelized T3 Structure

RICi-16
Configuration > System > Source Clock > Fallback Clock
System Clock (T1)

>
f - Forward
Figure 4-19. Fallback Clock Menu, T3 Network Mode and Channelized T3

Structure
RICi-16
Configuration > System > Source Clock > Fallback Clock
>
Figure 4-20. Fallback Clock Menu, E1 Interface or T1 Network Mode or

Unchannelized T3 Structure
Configuring the Date and Time

The Date and Time menu is used to configure the SNTP client parameters. The
SNTP client is used as a means to receive the date and time from the network.
When the SNTP server is properly configured and accessible, the device displays
the real date and time as was received from the SNTP server, instead of the
system uptime, which is the default state.
³ To set the SNTP client parameters:

• From the Date and Time menu (Configuration > System > Date and Time) set
the SNTP client parameters according to Figure 4-21 and Table 4-4.
RICi-16
Configuration> System> Date and Time
1. Date [YYYY-MM-DD] ... (2008-31-01)

2. Time [HH-MM-SS] ... (02:34:45)
3. SNTP mode > (Unicast client)
4. GMT > (0)
5. SNTP server IP address ... (255.255.255.1)
6. SNTP update interval (sec) ... (5)
7. Send initiated SNTP request
>
Figure 4-21. Date and Time Menu

Table 4-4. Date and Time Menu Parameters
Parameter Description Possible Values
Date Date in format of: [YYYY-MM-DD] 2000-01-01 to

2099-12-31
Time Time in format of: [HH:MM:SS] 00:00:00 to 23:59:59
SNTP mode Availability and type of the SNTP time Disable

retrieval: Unicast client
• Disable – the SNTP service is disabled. Default: Unicast client
• Unicast client – RICi-16 works in SNTP
mode as a Unicast client.
GMT The Greenwich Mean Time (GMT) offset of -12 to +12, in jumps of
the manually entered time (not relevant in 1 (integers only)
SNTP mode). Default: 0
SNTP server IP address of the SNTP server. Valid only 0.0.0.0 –

IP address when the SNTP mode is 'Unicast client'. 255.255.255.255
SNTP update The required delay in minutes between 1–1440

interval (min) automatic SNTP request initiations. Default: 60
You can manually initiate an SNTP request by selecting the Send initiated
SNTP request option. An SNTP request is immediately sent to the specified SNTP
server address upon selecting this option. Valid only when the SNTP mode is
'Unicast client'.
Defining Interface Groups

Each port can be allocated to an interface group. Once an interface group had
been defined you can then add specific ports to that group.
³ To define an interface group:

1. Navigate to the Interface Groups menu (Configuration >System >Interface
Groups).
The Interface Groups menu appears as illustrated in Figure 4-22.
RICi-16
Configuration> System> Interface Groups
Group Id [1-10] (0)

1. Ethernet Interfaces > (-)
2. GFP Interfaces > (-)
>
a-Add; f-Forward; b-Backward
Figure 4-22. Interface Groups Menu
2. Type <a> to add an interface group.

3. Type <s> to save the interface group.
Note The maximum number of interface groups that can be defined is 10.
³ To add a port to an interface group:

1. Navigate to the Interface Groups menu (Configuration >System >Interface
Groups).
The Interface Groups menu appears as illustrated in Figure 4-22.
2. Type <f> Forward or Backwards to select the desired interface group.
3. Select the relevant interface type and add the desired port to the interface
group.
Note You can add a single port (1) as well as a range of ports (1-4 for Ethernet and 1-
16 For GFP) to an interface group.
4. Select Save.
5. Repeat this procedure for all interface groups in use.
Selecting the Application Mode

You can set the application operation mode to Bridge Mode or Flows Mode,
according to your application requirements.
³ To set the application operation mode:

1. From the Main menu, navigate to Configuration > System.
The System Configuration menu appears as illustrated in Figure 4-23.
2. Select Application Mode and set to either Bridge Mode or Flows Mode.
3. Select Save.
Selecting the Network Operation Mode

Note This section is relevant only for RICi-16/T3.
You can select the network operation mode to be E1/T1 or T3, according to your
application requirements.
³ To set the network operation mode:

1. From the Main menu, navigate to Configuration > System.
The System Configuration menu appears as illustrated in Figure 4-23.
2. Select Network Operation Mode and set it to E1/T1 or T3.
3. Select Save.

Note Changing the network operation mode is a time-consuming operation. It may

take 10 to 30 seconds for RICi-16 to complete the transition.
When you change the network operation mode, all VCG and VLAN configurations
are lost. The device reverts to default VCG and VLAN configuration.
RICi-16
Configuration > System
1. Source Clock >

2. Management >
3. Terminal >
4. Date and Time >
5. Interface Groups >
6. Syslog >
7. Fault Propagation >
8. Application Mode (Bridge Mode)
9. Network Operation Mode (T3)
10. Protection >
11. Factory Defaults >
>
Figure 4-23. System Configuration Menu
If the T3 network mode is defined, the T3 port protection parameters option

appears in the System menu, see Configuring T3 Port Protection.
Setting the Syslog Parameters

Once the date and time are set, system events are logged accordingly. To allow
logging/sharing of system events on a server instead of internally, you need to
configure the Syslog parameters.
³ To set the Syslog parameters:

1. From the System menu (Configuration > System), select Syslog.
The Syslog menu is displayed.
2. Configure the Syslog parameters according to Figure 4-24 and Table 4-5.
3. Select Save.

RICi-16
Configuration> System> Syslog
1. Device Logging Status > (Enabled)

2. Device UDP Port [1-65535] ... (514)
3. Facility > (Local 1)
4. Severity Level > (Minor)
5. Server Parameters >
>
S-Save
Figure 4-24. Syslog Menu
Table 4-5. Syslog Parameters
Device logging Determines whether logging to Enabled

status the Syslog server is enabled or Disabled
disabled. When disabled, RICi-16
logs the events internally.
Default: Disabled
Device UDP The local UDP port from which the 1–65535
port Syslog messages are sent.
Default: 514
Note: The port cannot be changed
when the logging status is
enabled.
Facility Identifies the software module, Local 1 – Local 7

task or function from which the
Syslog messages are sent.
Default: Local 1
Severity level Only events that their severity Critical – corresponds to the
equals or exceeds the selected Emergency (0) severity level of
severity level are sent. The Syslog
severity levels are: Major – corresponds to the Alert
Default: Minor (1) and Critical (2) severity levels
of Syslog
Minor – corresponds to the Error
(3) severity level of Syslog
Warning – corresponds to the
Warning (4) severity level of
Syslog
Event – corresponds to the Notice
(5) severity level of Syslog
Info – corresponds to the
Informational (6) severity level of


Syslog
Debug – corresponds to the
Debug (7) severity level of Syslog
³ To set the Syslog server parameters:

1. From the Syslog menu (Configuration > System > Syslog), select Server
Parameters.
The Server Parameters menu is displayed.
2. Set the Server parameters according to Figure 4-25 and Table 4-6.
3. Select Save.
RICi-16
Configuration> System> Syslog >Server Parameters
Server Sequence ... (1)

Server Access > (Disable)
1. Server IP Address ... (190.72.140.100)
2. Server UDP Port ... (514)
>
S-Save
Figure 4-25. Syslog Server Parameters Menu
Table 4-6. Syslog Server Parameters
Server Server sequence number 1–5

Sequence
Server Access Whether to enable or disable syslog server Enabled

access Disabled
Default: Disabled
Server IP IP address of the Syslog server to which the 0.0.0.0 –

Address event logs are sent 255.255.255.255
Server UDP Port The UDP port of the Syslog server. 1–65535
Default: 514
Note: The port cannot be changed when the
logging status is enabled

Configuring Fault Propagation

When fault propagation is enabled, the fault propagation mechanism notifies
local and remote equipment whenever there is a faulty condition between
interface groups. This enables routers and switches on both ends of the link to
reroute traffic. Each port can be allocated to an interface group, see Defining
Interface Groups. You can configure each interface group to perform a specific
action according to the activated fault.
You can also specify the wait to restore (WTR) time for each interface. WTR is the
time period RICi-16 waits before enabling the interface group once the network is
restored.
³ To configure fault propagation:

1. From the Main menu, navigate to Configuration > System > Fault Propagation.
The Fault Propagation menu appears as illustrated in Figure 4-26.
RICi-16
Configuration > System > Fault Propagation
Faulty Interface > ()

Affected Interface > ()
1. Fault ()
2. Action ()
3. Wait to Restore [0-3600] ()
>
a - Add
Figure 4-26. Fault Propagation Menu
2. Type <a> to add a fault propagation definition.

3. Select Save.
A new fault propagation definition has been added to the Fault
Propagation screen.
4. Set the fault propagation definitions and parameters according to Figure 4-26
and Table 4-7.
Table 4-7. Fault Propagation Parameters
Faulty Interface Interface group that initiated the Group 1-10

the fault alarm
Affected Interface Interface group to which the fault Group 1-10

alarm should be forwarded
Fault Fault on which the action should be Interface Down

taken OAM Signaling
Default: OAM Signaling

Action Action taken on affected interface Interface Down

Default: OAM Signaling OAM Signaling
Wait to Restore Time period RICi-16 waits before 0-3600

enabling the interface once the (0 disables the WTR)
network is restored
Default: 0
5. Select Save.
6. Repeat this procedure for all fault propagation definitions in use.
Configuring Physical-Layer Parameters

RICi-16 is equipped with 16 E1/T1 ports and four fast Ethernet interfaces. The
Ethernet and E1 or T1 (depending on your unit) configuration menus are available
from the Physical Layer menu.
Configuring the Fast Ethernet Ports

The following parameters can be configured for the Ethernet ports at the physical
level:
• Administration status
• Auto negotiation
• Flow control
• Maximum advertised capability for the Auto Negotiation procedure
• Data rate and duplex mode (only when Auto Negotiation is disabled)
• MDIX Auto Cross-over
• OAM (EFM)
• Policer Profile
• VLAN Tag Ether Type (hex)
• MAC Access Control – You can specify that the port accepts traffic only from
the first MAC address(es) from which it receives traffic.
• L2CP Filtering Profile.
³ To configure the Fast Ethernet port at the physical level:

1. From the Main menu, navigate to Configuration > Physical Layer > Ethernet.
The Ethernet menu appears as illustrated in Figure 4-27.

RICi-16
Configuration > Physical Layer > Ethernet
Port (1)
Interface (RJ45)
OAM EFM Mode (Passive)
1. Administrative Status (Up)
2. Auto-Negotiation (Enable)
3. Flow Control (Enable)
4. Max Capability Advertised > (100base – TX Full Duplex)
5. MDIX Cross Over (Enable)
6. OAM EFM (Enable)
7. Policer Profile > (None)
8. VLAN Tag Ether Type (hex) ...(8100)
9. MAC Access Control >
10.L2CP Filtering Profile > (default 2cpProfile)
>
S – Save; F – forward; B – backward
Figure 4-27. Ethernet Menu
2. From the Ethernet menu, type <F> Forward or Backwards to select the
desired Fast Ethernet port.
3. Type <N> or accordingly to scroll up and down through the available
Ethernet parameters.
4. Set the physical layer parameters of the selected port according to
Figure 4-27 and Table 4-8,
5. Select Save.
6. Repeat for all ports in use.
Table 4-8. Ethernet Parameters
Parameter Decription Possible Values
Port Fast Ethernet port number. This parameter is 1–4

read-only
Default: 1
Interface Interface type. This parmeter is read-only
OAM EFM Mode OAM mode type. This parmeter is read-only Passive
Default: Passive Active
Administrative Fast Ethernet mode of operation Up

Status Default: Up Down
Auto-Negotiation Auto negotiation signaling over the Ethernet Enable

Default: Enable Disable
Flow Control Administrative PAUSE mode for this interface Enable

Default: Enable Disable

Max Capability Set of capabilities advertised by the local 10baseT Half Duplex
Advertised auto-negotiation entity 10baseT Full Duplex
Default: 100base TX Full Duplex 100baseTX Half Duplex
100base TX Full Duplex
Note: This parameter only appears when
aout-negotiation is enabled
Speed & Duplex Status speed and duplex that the port uses 10baseT Half Duplex
when the auto-negotiation is disabled 10baseT Full Duplex
Default: 100base TX Full Duplex 100baseTX Half Duplex
100base TX Full Duplex
Note: This parameter only appears when
aout-negotiation is disabled
MDIX Auto Cross Auto Cross Over functionality Enable
Over Default: Enable Disable
OAM EFM OAM Ethernet in the First Mile (IEEE 802.3ah) Enable
functionality Disable
Default: Disable
Policer Profile Sets a profile that performs traffic policing

for the port
VLAN Tag Ether VLAN Tag identifier 0-FFFF

Type Default: 8100
MAC Access MAC access control for the port. Defines the Enable
Control number of allowed MAC access addresses. Disable
Also defines whether the port accepts traffic
only from the first MAC address(es) from
which it receives traffic
Default: Disable
L2CP Filtering Sets a L2CP filtering profile that performs

Profile traffic filtering for the port
Configuring MAC Access Control Parameters

You can add up to 10 static MAC addresses to every Ethernet port. You may
define up to 10 static MAC addresses for every port. If this number is exceeded
and you want to add an additional MAC address, you must delete an existing MAC
address before the new one can be added.
³ To set the MAC access control parameters:

1. From the Ethernet menu (Configuration > Physical Layer > Ethernet) select
MAC Access Control.
The MAC Access Control parameters menu is displayed.
2. Configure MAC Access Control parameters according to Figure 4-28 and
Table 4-9.
3. Select Save.
4. Repeat this procedure for all ports in use.

RICi-16
Configuration>Physical Layer>Ethernet>MAC Access Control
Port ...(1)
Current Number of Permitted MAC Addresses ...(1)
1. MAC Access Control Administrative Status > (Enable)
2. Maximum Number of Permitted MAC Addresses [0-10]...(0)
3. Permitted Static MAC Addresses []>
>
s-Save; f-Forward; b-Backward
Figure 4-28. MAC Access Control Menu
Table 4-9. MAC Access Control parameters
Port Fast Ethernet port number. 1–4

This parameter is read-only
Default: 1
Current Number of Current number of learned 0-10

Permitted MAC Addresses MAC Addresses being
protected. This parameter
is read-only
Default: 0
MAC Access Control Current status of the MAC Enable

Administrative Status access control Disable
Default: Disable
Maximum Number of Specifies the maximum 0-10

Permitted MAC Addresses number of source MAC
addresses from which the
port is allowed to receive
traffic
Default: 0
Once you have defined the maximum number of permitted MAC addresses
parameter (see Table 4-9) you can start to define static MAC addresses.
³ To define static MAC addresses

1. From the MAC Access Control menu (Configuration > Physical Layer > Ethernet
> MAC Access Control) select Permitted Static MAC Addresses.
The Permitted Static MAC Addresses menu is displayed.

2. Select <A> to add a new MAC address.

A new MAC address appears as illustrated in Figure 4-29.
3. Select the desired MAC Address and define the address.
4. Select Save.
5. Repeat this procedure for all MAC addresses in use.
RICi-16
Configuration > Physical Layer >Ethernet > MAC Access Control >
Permitted Static MAC Addresses
1. MAC Address ... (000000000000)
>
S-Save
Figure 4-29. Permitted Static MAC Addresses Menu
Configuring the L2CP Filtering Profile

L2CP (Layer 2 Device Control Protocol) can be used to access and manage RICi-
16. L2CP filtering can be defined in order to assign an action based on the
address assigned to the profile. The following parameters can be configured for
the L2CP filtering profile at the physical level:
• Profile Name
• Profile Addresses.
³ To configure the L2CP Filtering Profile:

1. From the Main menu, navigate to Configuration > Physical Layer > L2CP
Filtering Profile.
The L2CP Filtering Profile menu appears as illustrated in Figure 4-30
RICi-16
Configuration > Physical Layer > L2CP Filtering Profile
Profile [1-4] (1)

1. Profile Name ... (Default Profile 1)
2. Addresses >
>
a–Add; f–Forward; b–Backward; d-Delete
Figure 4-30. L2CP Filtering Profile Menu
2. Configure the L2CP filtering profile parameters (see Figure 4-30).

3. Press <A> to add a L2CP filtering profile.
4. Press <F> to switch to a different L2CP filtering profile.

³ To configure the Profile Address:

1. Navigate to the Profile Address menu (Configuration >Physical Layer >L2CP
Filtering Profile >Addresses).
The Profile Addresses menu appears.
RICi-16
Configuration>Physical Layer>L2CP Filtering Profile > Addresses
Profile (Default Profile 1)

Address Index [1-32] (1)
Address (000000000000)
1. Action > (Tunnel)
>
a–add; f–forward; b–backward; d-Delete
Figure 4-31. Profile Address Menu
2. Configure the Profile Address parameters. Parameter descriptions and possible

values are provided in Table 4-10 and Figure 4-31.
3. Press <A> to add a new profile address.
4. Press <F> to switch to a different profile address.
Table 4-10. Profile Address Parameters
Profile Name Name of the profile DefaultProfile1
Address Index [1-32] Index number allocated to the 1-32

profile address
Default: 1
Address L2CP address 000000000000
Action Action that should be taken Discard

when destination address is Tunnel
received
Default: Tunnel
5. Select Save.
6. Repeat this procedure for all address profiles in use.
Configuring the E1 Ports

Note This section is relevant only for RICi-16 equipped with E1 ports.
³ To configure E1 ports:
1. From the Physical Layer menu (Configuration >Physical Layer), select E1.
The E1 menu appears as illustrated in Figure 4-32.

RICi-16
Configuration > Physical Layer > E1
Port [1 – 16] (1)

TX Clock Source > (System)
Line type > (G.732N-CRC)
Restoration Time (Immediate)

2. Interface Type (Balanced)
3. Line Code > (HDB3)
4. Rx Sensitivity (Long Haul)
>
S–Save; f–forward; b–backward;
Figure 4-32. E1 Port Configuration Menu
2. Configure E1 port parameters for each E1 port. Parameter descriptions and

possible values are provided in Table 4-11.
Press <F> to switch to a different E1 port.
Table 4-11. E1 Port Parameters
Port number Index of E1 ports. This parameter is read-only. 1-16
TX Clock Source Transmit clock source of the E1 port System
Line Type Type of E1 line in this circuit. The type of circuit G.732N-CRC
affects the number of bits per second that the
circuit can reasonably carry, as well as the
interpretation of the usage and error statistics.
This parameter is read-only.
Restoration Time Used to change the synchronization algorithms Immediate

to reduce the time required for the port to
return to normal operation after local loss of
synchronization (LOF event). This parameter is
read-only.
Administrative Administrative status of E1 port Up

Status Default: Up Down
Interface Type E1 interface type Balanced

Default: Balanced Unbalanced
Line Code Transmission line code. HDB3

Default: HDB3 AMI

Rx Sensitivity Maximum attenuation of the receive signal that Long Haul

can be compensated for by the interface receive Short Haul
path
Default: Long Haul
3. Select Save.
4. Repeat this procedure for all E1 ports in use.
Note If two CPEs such as RICi-16 communicate via VCG (VCAT) interfaces using a
16-frame multi-frame protocol (G.732N), network devices along the path must be
set to forward E1 frames transparently.
Configuring the T1 Ports
Note This section is relevant only for RICi-16 with T1 network ports, or channelized T3
network interface.
³ To configure T1 ports:
1. From the Physical Layer menu (Configuration >Physical Layer), select T1.
The T1 menu appears as illustrated in Figure 4-33.
RICi-16
Configuration > Physical Layer > T1
Port [1 – 16] (1)

TX clock Source > (System)
Line Type > (ESF)
Restoration Time (1 sec)

2. Line Code > (B8ZS)
3. Line Interface (DSU)
4. Line Length > (0–133 ft)
5. Line Build Out (db) (0)
>
s-Save; f–Forward; b–Backward;
Figure 4-33. T1 Port Configuration Menu
2. Configure the T1 port parameters for each T1 port. Table 4-12 lists
explanations and possible values for the listed parameters.
Press <F> to switch to a different T1 port.

Table 4-12. T1 Port Parameters
Port Index of T1 ports. This parameter is read- 1 - 16

only
Line Type Type of T1 line implementing this circuit. ESF

The type of circuit affects the number of
bits per second that the circuit can
reasonably carry, as well as the
interpretation of the usage and error
statistics. This parameter is read-only
TX clock source Transmit clock source of the T1 port System
Restoration Time Reduces the time required for the T1 port 1 sec.
to return to normal after loss of
synchronization (LOF)
Default: 1 sec.
Administrative Status Administrative status of the T1 port Up

Down
Default: Up
Line Code Transmission line code B8ZS

Default: B8ZS AMI
Line Interface Type of line interface of the T1 port DSU

Default: CSU CSU
Line Length The length of the DSL line (only visible if the 0-133 ft
Line Interface parameter is set to DSU) 133-266 ft
Default: 0-133 ft 266-399 ft
399-533 ft
533-655 ft
Line Build Out (dB) The TX gain of the DSL line (only visible if 0 dB
the Line Interface parameter is set to CSU) -7.5 dB
Default: 0 dB -15 dB
Rx Sensitivity Maximum attenuation of the receive signal Short Haul

that can be compensated for by the Long Haul
interface receive path
Default: Long Haul
3. Select Save.
4. Repeat this procedure for all T1 ports in use.
24-frame multi-frame protocol (ESF), network devices along the path must be set
to forward T1 frames transparently.

Configuring the T3 Ports
This section describes the configuration of the T3 port parameters. To configure

the T3 channel mapping, refer to Configuring the T3 Channel Mapping.
³ To configure the T3 port:

1. From the Physical Layer menu (Configuration >Physical Layer), select T3.
The T3 menu appears as illustrated in Figure 4-34.
RICi-16
Port [1-2] (1)


2. Structure (Channelized)
3. Line Type (M23)
4. Line Length (Up to 225ft)
5. Mapping []>
>
s–Save; f–Forward; b–Backward
2. Configure the T3 port parameters. Table 4-13 lists explanations and possible
values for the parameters.
Table 4-13. T3 Port Parameters
Port Index of T3 port. This parameter is read-only 1–2
TX Clock Source Transmit clock source of the T3 port System
Administrative Status Administrative status of the T3 port Up

Down
Default: Up
Structure Channelized: Aggregated T3 up to 28 T1 channels. Channelized

Unchannelized: Native T3 channel Unchannelized
Default: Channelized
Note: Changing the T3 structure is a
time-consuming operation and may take as long as
30 seconds to complete. All VCG and VLAN
configurations are lost when you change the T3
structure. The device reverts to default VCG and
VLAN configurations

Line Type Type of T3 line implementing this circuit. The type M23
of circuit affects the number of bits per second C-bit Parity
that the circuit can reasonably carry, as well as the
interpretation of the usage and error statistics
Default: M23
Note: The Line Type parameter changes if you
change the T3 structure: M23 for channelized
structure, C-bit Parity for unchannelized structure
Line Length The length of the DSL line Up to 225ft
Default: Up to 225ft Over 225ft
3. Select Save.
4. Repeat this procedure for both T3 ports if T3 structure is unchannelized. Only
the first T3 ports are available to be configured if T3 structure is channelized.
24-frame multi-frame protocol (ESF), network devices along the path must be set
to forward T1 frames transparently.
Configuring T3 Port Protection

RICi-16 enables you to configure port protection for T3 ports in cases where an
active port fails another is automatically assigned to take over the extra
workload.
This section describes the configuration of T3 port protection.
³ To configure the T3 port protection:

1. From the System menu (Configuration > System > Protection), select
Protection and perform the following:
2. Select the port protection method:
1+1: Load sharing, with both ports in the pair active, sharing the overall
traffic load. When one of the ports fails, the other port takes over.
None: No protection, in this case, each port operates independently
3. Select a working port (1–2).

4. Select Save.
5. Repeat this procedure for both T3 ports.
Configuring the T3 Channel Mapping
Note This section is relevant only for RICi-16/T3. Mapping capabilities for RICi-16/T3
depend on the user license (1-4, 1-8, 1-12, 1-16) that you currently hold

The T3 channel map offers a bird's eye view of which channel is mapped to which
port. You can map up to 28 T3 channels to up to 16 physical T1 ports and up to
16 VCGs. A physical T1 port can be mapped only once to a T3 channel. A VCG
logical port can be mapped to up to 16 T3 channels. The default T3 channel
mapping configuration is:
• T3 channels 1–16 mapped to T1 ports 1–16 respectively
• T3 channels 17–28 mapped to logical port 1 (VCG 1).
Note If you want to map a T3 channel to a VCG other than VCG 1, you must first create
the VCG logical port. Refer to Configuring the Logical Layer for details.
³ To view the T3 channel mapping:

• From the T3 menu (Configuration > Physical Layer > T3), select Mapping.
The T3 Mapping menu appears as illustrated in Figure 4-35. The default
mapping configuration is shown. When the mapping menu appears, the
cursor is positioned at the connection for channel 1.
RICi-16
Configuration > Physical Layer > T3 > Mapping
Channel Connection Channel Connection Channel Connection

1 T1-1 11 T1-11 21 LP1
2 T1-2 12 T1-12 22 LP1
3 T1-3 13 T1-13 23 LP1
4 T1-4 14 T1-14 24 LP1
5 T1-5 15 T1-15 25 LP1
6 T1-6 16 T1-16 26 LP1
7 T1-7 17 LP1 27 LP1
8 T1-8 18 LP1 28 LP1
9 T1-9 19 LP1
10 T1-10 20 LP1
1. T1-1 4. T1-4 7. T1-7 10. T1-10 13. T1-13 16. T1-16

2. T1-2 5. T1-5 8. T1-8 11. T1-11 14. T1-14 17. LP1
3. T1-3 6. T1-6 9. T1-9 12. T1-12 15. T1-15 18. N/C
>
Figure 4-35. T3 Mapping Menu, Default Configuration
The rows at the bottom of the screen show the values corresponding to potential
connections, to use when changing the channel mapping. Use the N/C value to
set a channel to unmapped. Setting a channel to unmapped causes an AIS signal
to propagate over the T3 connection on that channel.
³ To change a T3 channel mapping:

1. Use the arrow keys to position the cursor at the channel for which you want
to change the mapping.

2. Type the value corresponding to the connection that you want to map to the
channel, and click <Enter>. For example, type 1 to map to T1 port 1, or 16 to
map to logical port 1. If the list of potential connections is too large to fit on
the screen, type <n> to display the next part of the list, and to display the
previous part of the list.
Configuring the Logical Layer

You can map multiple E1/T1 ports or T3 clear channels to a VCAT VCG group, via
the Logical Layer menu. If the RICi-16 unit has a T3 channelized interface, then
you map the logical ports to T3 channels via the T3 mapping menu, not via the
Logical Layer menu.
To ease configuration effort and save time, the RICi-16 unit is supplied with the
logical ports preconfigured, according to the network interface (see Table 4-14
through Table 4-16). When you change the network interface, the corresponding
default configuration is automatically created.
A logical port in RICi-16 is either a VCG logical port bound to physical E1/T1/T3
ports or T1 channels, or a GFP logical port that is bound to a VCG logical port.
When you create a VCG logical port, RICi-16 automatically creates a GFP logical
port that is bound to the VCG logical port, and configures a bridge port bound to
the GFP logical port. Therefore, you only need to add/delete VCG logical ports.
You do not manually add/delete GFP logical ports.
You can create up to 16 VCG logical ports if the network interface is E1/T1 or
channelized T3. You can create only two VCG logical ports if the network interface
is unchannelized T3.
Note A physical port can be bound to only one logical VCG port.
Table 4-14. Default Logical Port Settings for T3 Network Interface, Channelized
Logical Interface Port Name Bound to

Port Type
1 VCG VCG 1 Internal ports (T3 channels) 17–28
2 GFP GFP 1 Logical port VCG 1
Table 4-15. Default Logical Port Settings for T3 Network Interface,

Not Channelized

Port Type
1 VCG VCG 1 Physical (T3) ports 1–2

Table 4-16. Default Logical Port Settings for E1/T1 Network Interface

Port Type
1 VCG VCG 1 Physical (E1/T1) ports 1–16
³ To configure the Logical Layer:

1. From the Main menu, navigate to Configuration > Logical Layer.
The Logical Layer menu appears. Depending on the interface type and
logical port type, the screen appears as shown in Figure 4-36 through
Figure 4-38.
RICi-16
Configuration > Logical Layer
Port (1)
Interface Type > (VCG)

Bind To Internal Ports > (13-28)
Max differential delay (msec)[0 - 256] (256)
2. Port Name ... (VCG 1)
3. Loop Detection (Enable)
4. Signal Degrade > (10ˆ-6)
>
a–add; f–forward; b–backward
Figure 4-36. Logical Layer Menu (VCG) – T3 Interface, Channelized
RICi-16
Port (1)

3. Bind to Physical Ports > (1-2)
4. Loop Detection (Enable)
5. Signal Degrade (10ˆ-6)
>
a–add; f–forward; b–backward
Figure 4-37. Logical Layer Menu (VCG) – E1/T1 or T3 Interface, Not Channelized

RICi-16
Port (2)
Interface Type > (GFP)

Bind To (VCG 1)
2. Port Name ... (GFP 1)
3. Payload FCS (Absent)
4. Mac Parameters >
>
a–Add; f–Forward; b-Backward
Figure 4-38. Logical Layer Menu (GFP)
2. Configure the logical parameters for each port. Parameter descriptions and
possible values are provided in Table 4-17.
Type <F> to scroll through the ports.
Table 4-17. Logical Layer Parameters
Port The logical port being configured 1–16
Interface Type Type of interface set for the port VCG

GFP
Bind to Internal Ports VCAT VCG Logical Port: Links to T3 channels. 1–28
This parameter is read-only and applies only when (Single number or range)
the T3 interface is configured as channelized
Bind to Physical Ports VCAT VCG Logical Port: E1/T1 links or T3 clear E1/T1: 1–16
channels that are members of the VCG T3: 1–2
This parameter applies only when RICi-16 is (Single number or range)
configured for T1 network mode or
T3 unchannelized interface
Bind to GFP Logical Port: Links to VCG. This parameter is VCG <n>
read-only
Administrative Status Administrative state of the logical port Up

Default: Up down
Port Name Free text to assign a name to the logical port VCG 1
Default: GFP 1 GFP 1
Max Differential Delay Maximum allowed delay variation in milliseconds. 256

(msec) This parameter is read-only
Default: 256

Payload FCS GFP payload FCS Present

Default: Absent Absent
Loop Detection Looped members are automatically detected and not Enable
added to the LCAS when loop detection is enabled.. Disable
The VCG restarts after enabling or disabling the loop
detection
Default: Enable
Signal Degrade Enables defining the signal degrade threshold 10ˆ-6

parameters. If the bit error on the E1/T1/T3 line
exceeds the defined signal degrade threshold, the
VCG member is temporally removed from the VCAT
group.
Configuring MAC Parameters for a GFP Logical Port

When you create a VCG logical port, RICi-16 automatically creates a GFP logical
port that is bound to the VCG logical port. RICi-16 allows you to define MAC
parameters for each GFP logical port.
³ To define MAC parameters for a GFP logical port:

1. From the Logical Layer menu (Configuration > Logical Layer), press <f> until
the desired GFP logical port is displayed (see Figure 4-38).
2. Select MAC Parameters and press Enter.
The MAC Parameters menu is displayed as illustrated in Figure 4-39.
RICi-16
Configuration > Logical Layer > MAC Parameters
Port (2)
OAM EFM Mode (Passive)

1. Port Name ... (GFP 1)
2. VLAN Tag Ether Type (hex) [0-ffff] ... (8100)
3. OAM EFM (Disable)
4. Queue Profile (QDefaultProfile1)
>
a–Add; f–Forward; b-Backward
Figure 4-39. MAC Parameters Menu
3. Configure the MAC parameters for each GFP logical port according to the
parameter descriptions and possible values in Table 4-18.

Table 4-18. MAC Parameters
Port Logical port number. This parameter is 1–2

read-only.
OAM EFM Mode OAM EFM mode type. This parmeter is Passive (default)
read-only Active
Port Name User defined name allocated to the port

(e.g. GFP 1)
VLAN Tag Ether Type (hex) [0- The VLAN TAG identifier 0-FFFF
ffff] Default: 8100
OAM EFM OAM Ethernet in the First Mile (IEEE Enable

802.3ah) functionality Disable
Default: Disable
Queue Profile Queue default profile Profile name
4. Select Save.
Configuring the Application Layer Parameters
Configuring the Internal Bridge

The internal bridge connects the unit’s ports. You need to configure the internal
bridge for it to process the VLAN tags correctly and maintain the priority of the
data flows.
Note If the application mode is set to Flows, the bridge parameters do not show
³ To set the application mode to Bridge:

• From the System menu (Configuration > System), select Application Mode
and press Enter.
The application mode is set to Bridge. The Bridge menu is available in the
Applications menu (Configuration > Applications).
³ To configure the internal bridge:

1. From the Main menu, navigate to Configuration > Applications > Bridge.
The Bridge menu appears.
2. In the Bridge menu, configure the parameters according to Figure 4-40 and
Table 4-19

RICi-16
Configuration > Applications > Bridge
1. VLAN Mode > (Aware)

2. Forwarding Mode > (Filter)
3. Aging Time (sec) [300 - 4080] ... (300)
4. Static MAC Table []>
5. Bridge Port >
6. VLAN Membership >
>
s–Save
Figure 4-40. Bridge Menu
Table 4-19. Internal Bridge screen
VLAN Mode Determines whether packet Aware –Bridge operates according to 802.1q,
forwarding is based on MAC forwarding packets based on VLAN+MAC
address only or on VLAN+MAC address
Unaware – Bridge operates according to
802.1d, forwarding packets based on MAC
address only
Forwarding Mode Determines whether the bridge Filter – Learning and filtering are enabled
learns MAC addresses Transparent – No learning is performed. Each
packet received is forwarded to all other ports
automatically, unless static MAC is used.
Aging Time Aging time for entries in the 300-4080 secs

MAC table. If the aging time
elapses, and no frame has
been received with the MAC
address, it is erased from the
MAC table
3. To configure the Static MAC Table, refer to Configuring the MAC Table.
4. To configure the Bridge Port, refer to Configuring the Bridge Ports.
5. To configure the VLAN Membership (in Aware bridge only), refer to Configuring
VLAN Membership.
Configuring the MAC Table

Static MAC addresses are stored in the MAC table.
³ To add a static MAC address:

1. From the Main menu, navigate to Configuration > Applications > Bridge >
Static MAC Table.

The Static MAC Table appears as illustrated in Figure 4-41, with VLAN ID
entries for a VLAN-aware bridge only.
RICi-16
Configuration > Applications > Bridge > Static MAC Table
VLAN ID MAC Address Bridge Port

1 111111111111 1
| 2 222222222222 2
v 3 333333333333 3
4 444444444444 4
5 555555555555 5
>
s–Save; a–Add; r–Remove; c-Clear
ESC-prev menu; !-main menu; &-exit; ?-help 1 M/ 2C
Figure 4-41. Static MAC Table
2. In the Static MAC Table, press <A> to add a static MAC address.
The Static MAC Table switches to the MAC Table Handling mode as
illustrated in Figure 4-42.
RICi-16
MAC Table Handling
1. VLAN ID [1-4094] ... (0)

2. MAC Address ... (000000000000)
3. Bridge Port [1-21] ... (0)
>
s - Save
ESC-Previous menu; !-Main menu; &-Exit; ?-Help 1 M/ 2 C
Figure 4-42. Static MAC Table, Add Mode
3. In the MAC Table Add mode, perform the following:

Select MAC Address, and enter a new MAC address.
Select VLAN ID, and choose a VLAN ID for the MAC address between
1 and 4094.
Select Bridge Port, and choose the interface this MAC address should be
attached to.
Select Save to save the MAC address.
Press <ESC> to return to the Static MAC Table screen.
³ To remove a static address from the table:

• In the Static MAC Table (Figure 4-41), select the desired MAC address and
press <R>.
The MAC address is deleted from the table.

³ To clear the MAC table:

1. In the Static MAC Table screen (Figure 4-41), press <X>.
The following message appears:
Are you sure (Y/N)?
2. To confirm your request, press <Y>.
All MAC addresses are deleted from the table.
Configuring the Bridge Ports

You can use the Bridge Port menu for configuration of the bridge port
parameters, other than binding to logical ports.
The unit ships with default bridge port bindings preconfigured for basic use. The
factory defaults are listed in Table 4-20. You cannot delete bridge port bindings
to the host port and Ethernet ports. You can create or delete bridge port
bindings to GFP logical ports only indirectly, by adding or deleting the
corresponding VCG logical port, via the Logical Layer menu.
Table 4-20. Default Bridge Port Bindings
Bridge Port Bound to
1 Reserved for management host
2 Ethernet port 1
3 Ethernet port 2
4 Ethernet port 3
5 Ethernet port 4
6 GFP 1 (logical port 2)
³ To configure a bridge port:

1. From the Main menu, navigate to Configuration > Applications > Bridge >
Bridge Ports.
The Bridge Port menu appears as illustrated in Figure 4-43.
2. In the Bridge Port menu, configure the bridge port parameters according to
Figure 4-43 and Table 4-21.
3. Select Save.

RICi-16
Configuration > Applications > Bridge > Bridge Ports
Bridge port [1 – 16] (2)

Bind To (Fast Ethernet 1)
1. Activation (Enable)
2. Ingress Filtering (Disable)
3. Accept Frame Type (All)
4. Port VID\Stacking VID [1 – 4094] ... (3)
5. Copy Origin Priority (Disable)
6. Default Priority Tag [0-7] ... (4)
7. Egress Tag Handling (Stacking)
8. Ingress Tag Handling (Stripping)
9. Queue Mapping Profile > (QMDefaultProfile1)
>
f-Forward ; b-Backward; g-Go To ; d-Delete s–Save
Figure 4-43. Bridge Port Menu
Table 4-21. Bridge Port Parameters
Parameter Possible Values Possible Values
Bridge Port Remarks 1–120
Bind to Number that identifies the bridge port Fast Ethenet

displayed Logical Port
Bridge port 1 is reserved for the host bridge Host
port
Press <F> to navigate between ports
Activation Fast Ethernat, GFP Logical Port and Host Enable

bridge ports. This parameter is read-only Disable
Default: Enable
Ingress Filtering Specifies if this port is available or not Enable

Default: Disable Disable
Accept Frame Type When enabled, the device discards incoming All
frames for VLANs of which the port is not a Tag Only
member
When disabled, the port accepts all incoming
frames
Default: All
Port VID \ Stacking VID Tag Only specifies that the device discards 1–4094
untagged frames. All specifies that untagged
frames received on this port are accepted
and assigned to the PVID for this port
Default: 2

Parameter Possible Values Possible Values
Copy Origin Priority This is the PVID, the VLAN ID assigned to Enable
untagged frames or priority-tagged frames Disable (default)
received on this port. If Stacking is enabled,
this is the tag to be added
Default: Disable
Default Priority Tag Enable: The priority tag of the original VLAN is 0–7
copied if a frame arrives with a stacked VLAN
tag, otherwise the default priority is used
Disable: The default priority is used
Default: 0
Egress Tag Handling Default VLAN frame priority, applies to Stacking

untagged frames Stripping
Default: None None
Ingress Tag Handling Stacking: Adds the PVID to every frame Stacking
transmitted from the port (push). Stripping
Stripping: Removes the first VLAN tag from
every transmitted frame, on the egress of the
port (pop)
Default: None
Queue Mapping Profile Stacking: Adds the PVID to every frame Profile name
received on the ingress of the port (push).
Stripping: Removes the first VLAN tag from
every received frame, on the ingress of the
port (pop)
Configuring VLAN Membership
³ To configure VLAN membership:

1. From the Main menu, navigate to Configuration > Applications > Bridge > VLAN
Membership.
The VLAN Membership menu appears as illustrated in Figure 4-44.
RICi-16
Configuration > Applications > Bridge > VLAN Membership
1. VLAN ID [1-4094] ... (1)

2. Egress Tagged Ports > (1-10,12)
3. Egress UnTagged Ports > (6,9,120)
>
>
s–Save; f–Forward; b–Back; g–Go; d–Delete;
Figure 4-44. VLAN Membership Menu

2. Select VLAN ID, and type the VLAN ID you wish to configure.
3. Select Egress Tagged Ports. Define the set of ports to transmit packets for
this VLAN as tagged.
4. Select Egress UnTagged Ports. Define the set of ports to transmit packets for
this VLAN as untagged.
5. Select Save.
Configuring Quality of Service (QoS)

RICi-16 supports Quality of Service (QoS) with priority methods according to
various QoS profiles. The following QoS profiles are supported:
• Queue Mapping profiles
• Marking profiles
• Policer profiles
• Shaper profiles
• Queue profiles.
Profiles can be applied to the traffic flows to ensure the desired flow
classification and prioritization.
Defining the Queue Mapping Profile

Queue mapping profiles can be applied to traffic flows to ensure the desired flow
classification and prioritization. Queue mapping classification and prioritization
can be defined using the Queue Mapping Profiles menu.
³ To configure the queue mapping for the 802.1p method:

1. Navigate to Configuration > Application > QoS.
The QoS Profiles menu appears as illustrated in Figure 4-45.
RICi-16
Configuration > Application > QoS
1. Queue Mapping Profiles >

2. Marking Profiles >
3. Policer Profiles >
4. Shaper Profiles >
5. Queues Profiles >
>
ESC-prev.menu; !-main menu; &-exit
Figure 4-45. QoS Profiles Menu
2. From the QoS menu, select Queue Mapping Profiles.

The Queue Mapping Profiles menu appears as illustrated in Figure 4-46.

RICi-16
Configuration > Application > QoS > Queue Mapping Profiles
Profile [1-32] (1)

1. Name ... ()
2. Ingress Priority Method > (802.1p)
3. Mapping []>
>
a-Add; f-Forward; b-Backward; d-delete
Figure 4-46. Queue Mapping Profiles Menu
3. Press <A> to add a new profile.

The new profile appears under the Profile ID.
4. Select Name and define a new profile name.
5. Select Ingress Priority Method and choose the 802.1p method.
6. Select Save.
7. Select Mapping.
The associated Mapping menu appears as illustrated in Figure 4-47.
8. From the Mapping menu, select a priority tag value 0–7 and map it to a
priority queue (1–4).
RICi-16
Configuration>Application>QoS>Queue Mapping Profiles>Mapping
802.1p Queue
Tag Value 0 1
Tag Value 1 1
Tag Value 2 2
Tag Value 3 2
Tag Value 4 3
Tag Value 5 3
Tag Value 6 4
Tag Value 7 4
1. Change cell [1-4] ... (1)
>
Figure 4-47. Mapping Menu (802.1p Method)
³ To configure the queue mapping for the DSCP method:

1. From the QoS menu (Configuration > Application > QoS), select Queue
Mapping Profiles.


4. Select Ingress Priority Method and choose the DSCP method.
5. Select Save.
6. Select Mapping.
³ To add or delete a tag value for the DSCP method:

• Press <A> to add a tag value and then define the tag value (0-63).
• Press to delete a tag value and then define the tag value to be deleted.
RICi-16
1. Tag Value 0 [1-4] ... (1)

2. Tag Value 1 [1-4] ... (1)
3. Tag Value 2 [1-4] ... (2)
4. Tag Value 3 [1-4] ... (2)
5. Tag Value 4 [1-4] ... (3)
6. Tag Value 5 [1-4] ... (3)
7. Tag Value 6 [1-4] ... (4)
8. Tag Value 7 [1-4] ... (4)
>
a-Add; d-Delete
Figure 4-48. Mapping Menu (DSCP Method)
³ To configure the queue mapping for the IP Precedence method:

1. From the QoS menu (Configuration > Application > QoS), select Queue
Mapping Profiles.
4. Select Ingress Priority Method and choose the IP Precedence method.
5. Select Save.
6. Select Mapping.

RICi-16
IP Precedence Queue
Tag Value 0 1
Tag Value 1 1
Tag Value 2 2
Tag Value 3 2
Tag Value 4 3
Tag Value 5 3
Tag Value 6 4
Tag Value 7 4
1. Change cell [1-4] ... (1)
>
Figure 4-49. Mapping Menu (IP Precedence Method)
Defining Marking Profiles

Marking profiles can be applied to the traffic flows to ensure the desired flow
classification and prioritization. Marking classification and prioritization can be
defined using the Marking Profiles
³ To configure marking for the 802.1p method:

2. From the QoS menu, select Marking Profiles.
The Marking Profiles menu appears as illustrated in Figure 4-50.
RICi-16
Configuration > Application > QoS > Marking Profiles
Profile [1-32] (1)

1. Name ... ()
2. Ingress Priority Method > (802.1p)
3. Mapping []>
>
a-Add, f-Forward, b-Backward
Figure 4-50. Marking Profiles Menu

5. Select Ingress Priority Method and choose the 802.1p method.
6. Select Save.

7. Select Mapping.
RICi-16
Configuration > Application > QoS > Marking Profiles > Mapping
802.1p Marking
Tag Value 0 0
Tag Value 1 1
Tag Value 2 2
Tag Value 3 3
Tag Value 4 4
Tag Value 5 5
Tag Value 6 6
Tag Value 7 7
1. Change cell [0-7] ... (1)
>
Figure 4-51. Mapping Menu (802.1p Method)
³ To configure marking for the DSCP method:

1. From the QoS menu (Configuration > Application > QoS), select Marking
Profiles.
4. Select Ingress Priority Method and choose the DSCP method.
5. Select Save.
6. Select Mapping.
³ To add or delete a tag value for the DSCP method:

• Press <A> to add a tag value and then define the tag value (0-63).
• Press to delete a tag value and then define the tag value to be deleted.

RICi-16
Configuration > Application > QoS> Marking Profiles > Mapping
1. Tag Value 0 [0-7] ... (0)

2. Tag Value 1 [0-7] ... (1)
3. Tag Value 2 [0-7] ... (2)
4. Tag Value 3 [0-7] ... (3)
5. Tag Value 4 [0-7] ... (4)
6. Tag Value 5 [0-7] ... (5)
7. Tag Value 6 [0-7] ... (6)
8. Tag Value 7 [0-7] ... (7)
>
a-Add; d-Delete
Figure 4-52. Mapping Menu (DSCP Method)
³ To configure marking for the IP Precedence method:

1. From the QoS menu (Configuration > Application > QoS), select Marking
Profiles.
4. Select Ingress Priority Method and choose the IP Precedence method.
5. Select Save.
6. Select Mapping.
RICi-16
Configuration > Application > QoS > Marking Profiles > Mapping
IP Precedence Marking
Tag Value 0 0
Tag Value 1 1
Tag Value 2 2
Tag Value 3 3
Tag Value 4 4
Tag Value 5 5
Tag Value 6 6
Tag Value 7 7
1. Change cell [0-7] ... (1)

>
Figure 4-53. Mapping Menu (IP Precedence Method)

Defining Policer Profiles

Policer profiles can be applied to the traffic flows to ensure the desired flow
classification and prioritization. Policer configuration can be defined using the
Policer Profiles menu.
³ To configure policer profiles:

2. From the QoS menu, select Policer Profiles.
The Policer Profiles menu appears as illustrated in Figure 4-54.
RICi-16
Configuration > Application > QoS > Policer Profiles
Policer [1-32] (1)

1. Name ... (DefaultPolicer1)
2. CIR [0-100000] ... (0)
3. CBS [0-12176] ... (0)
4. EIR [0-100000] ... (100000)
5. EBS [0-12176] ... (12176)
>
Figure 4-54. Policer Profiles Menu

5. Define the associated policer parameters according to Table 4-22.
6. Select Save.
Table 4-22. Policer Profiles Parameters
CIR Defines the Committed Information Rate (CIR) for the 0,64–100,000 kbps
current profile. The CIR specifies a bandwidth with
committed service guarantee (“green bucket” rate).
Granularity: 64 Kbps up to 130 Mbps and
512 Kbps up to 1 Gbps
Default: 0
CBS Defines the Committed Burst Size (CBS) for the 0,64–12,176 kbps
current profile. The CBS specifies the maximum
guaranteed burst size (“green bucket” size).
1 x Byte granularity
Default: 0

EIR Defines the Excess Information Rate (EIR). The EIR 0,64–100,000 kbps
specifies an extra bandwidth with no service
guarantee (“yellow bucket” rate).
Default: 100,000
EBS Defines the Excess Burst Size (EBS). The EBS specifies 0,64-12,176 kbps
the extra burst with no service guarantee (“yellow
bucket” size).
1 x Byte granularity
Default: 12,176
Defining Shaper Profiles

Shaper profiles can be applied to the traffic flows to ensure the desired flow
classification and prioritization. Shaper configuration can be defined using the
Shaper Profiles menu.
³ To configure shaper profiles:

2. From the QoS menu, select Shaper Profiles.
The Shaper Profiles menu appears as illustrated in Figure 4-55.
RICi-16
Configuration > Application > QoS > Shaper Profiles
Shaper [1-21] ... (1)

1. Name ... (DefaultShaper1)
2. CIR [0-100000] ... (100000)
>
a-Add; f-Forward; b-Backward
Figure 4-55. Shaper Profiles Menu

5. Define the associated shaper parameters according to Table 4-23.
6. Select Save.

Table 4-23. Shaper Profiles Parameters
CIR Defines the Committed Information Rate (CIR) for the 0,64–100,000 kbps
current profile. The CIR specifies a bandwidth with
committed service guarantee (“green bucket” rate).
Default: 0
Defining Queue Profiles

Queue profiles can be applied to the traffic flows to ensure the desired flow
classification and prioritization. Queue configuration can be defined using the
Queue Profiles menu.
³ To configure queue profiles:

2. From the QoS menu, select Queue Profiles.
The Queue Profiles menu appears as illustrated in Figure 4-56.
RICi-16
Configuration > Application > QoS > Queue Profiles
1. Name ... (QDefaultProfile1)

2. Shaper Profile > (DefaultShaper1)
3. Internal Queues >
>
Figure 4-56. Queue Profiles Menu

The new profile appears.
5. Select Shaper Profile and choose a shaper profile from the available list.
6. Select Save.
Once you have saved the queue profile, the Internal Queues option appears.
³ To configure internal queues:

1. From the Queue Profiles menu (Configuration>Application>QoS> Queue
Profiles), select Internal Queues.
The Internal Queues menu appears as illustrated in Figure 4-57.

RICi-16
Configuration>Application>QoS>Queue Profiles>Internal Queues
1. ID [1-5] ... (1)

2. Scheduling ... (WFQ)
3. Weight [1-100] ... (50)
4. Shaper Profile ... (DefualtShaper1)
>
f-Forward; b-Backward
Figure 4-57. Internal Queues Menu
2. Press <F> to select an internal queue (1–5) that you intend to configure.
3. Configure the internal queue according to Table 4-24.
4. Select Save.
Table 4-24. Internal Queue Parameters
Scheduling Defines the queue scheduling method. If Strict – High-priority queues that are
one of the internal queues is configured to always serviced first. If a lower-priority
the WFQ mode, the queues with the lower queue is being serviced and a packet
priority cannot be configured to the strict enters a higher queue, that queue is
mode. serviced immediately.
Note: In configurations with Strict and WFQ WFQ – Weighted Fair Queuing, if one port
queues, the WFQ frames are transmitted does not transmit, its unused bandwidth
only after the transmission of packets is shared by the ‘transmitting’ queues
associated with the Strict queues is according to the assigned weight.
completed. Default: WFQ
Weight Determines the weight of an internal queue 1–50

when the scheduling weight is configured to Default: 50
WFQ.
Shaper Profile Defines the shaper profile to use for the Default Shaper Profile
internal queue.
Configuring Flows
RICi-16 provides traffic flow classification between the traffic source and its final
destination. RICi-16 supports up to 64 unidirectional flows. Each flow is defined
by a classification profile.
In Flow-based operation mode, incoming customer traffic is classified and
mapped according to port-based (all-in-one) bundling or by user port and CE
VLAN-ID, VLAN priority, DSCP and IP precedence. Operators can differentiate
services using classification methods, police the traffic and enforce SLA per
service
This section explains how to define flows and add packets to the flows according
to specific criteria.

Note If RICi-16’s application mode is set to Bridge, the Flows parameter does not
show.
The following flow related options are available:

• Classification profiles
• Flow definitions.
³ To set the application mode to Flows:

1. From the System menu (Configuration > System), select Application Mode and
press Enter.
The application mode is set to Flows. The Flows menu is available in the
Applications menu (Configuration > Applications).
2. Select Save.
Defining Flows
³ To define the flow:

1. From the Flows menu (Configuration > Applications > Flows), select Flow
Definition.
The Flow Definition menu appears as illustrated in Figure 4-58.
2. To add a flow, press <a>.
A new flow is added and a Flow ID is assigned (1-64).
3. Specify the desired Flow Name before you press <S> for Save.
The remaining interface parameters are displayed once you have saved
for the first time.
4. Configure the remaining parameters as detailed in Figure 4-58 and Table 4-25.
To navigate to a different flow ID, press <f> or to browse the Flow
IDs forward or backward respectively.

RICi-16
Configuration > Applications > Flows > Flow Definition
Flow [1-64] (1)

Ingress Port (ETH1)
1. Name ... (Flow 1)
2. Administrative Status (Enable)
3. Priority [1-256] ... (1)
4. Classifier Profile > (DefaultUnclassified)
5. Policer Profile > (DefaultPolicer1)
6. Egress Port > (GFP1)
7. Queue Mapping Method (Fixed)
8. Queue [1-4] > (1)
9. Drop Frames (Disable)
10.Looopback Action (Disable)
11.VLAN Actions >
>
a-Add; f-Forward; b-Backward; d-Delete
Figure 4-58. Flows Definitions Screen
Table 4-25. Flow Definitions
Flow ID Flow ID, automatically assigned when adding a 1 – 32

flow.
Name Assign a name to a specific flow

Default: Flow-<ID#>
Administrative Status Defines the administartive staus of the flow. Enable

Ingress Port Defines which port the flow starts Host

Default: None ETH1-4
GFP1-16
Priority Priority of the port 1-256
Classifier Profile Defines which classification profile to use ClassificationDefaultProfile1

Default: None
Policer Profile Ingress brandwidth profile index DefaultPolicer1

Default: None
Egress Port To which port the flow is forwarded Host

Default: None ETH1-4
GFP-1
Queue Mapping Method Method to use when classifying frames into Fixed
queues Profile
Default: Fixed

Queue Fixed queue protocol 0–4

Default: 0
Drop Frames Defines whether to allow dropped frames or not Enable

Disable
Loopback Action Defines whether to allow loopback actions or Enable

not Disable
VLAN Actions VLAN action for the current flow
Defining VLAN Actions for Flows
³ To define VLAN actions for flows:

1. From the Flow Definition menu (Configuration > Applications > Flows > Flow
Definition), select VLAN Actions.
The VLAN Actions menu appears as illustrated in Figure 4-59.
RICi-16
Configuration > Applications > Flows > Flow Definition > VLAN
Actions
1. Outer VLAN Action > (Push)

2. Outer VLAN[0-4094] ... (1)
3. Outer Pbit Method (Profile)
5. Outer Pbit Profile > (MarkingDefault1)
6. Outer Mark (Enable)
7. Outer Mark VLAN[0-4094] ... (0)
8. Inner VLAN Action > (Push)
9. Inner VLAN [0-4094] ... (0)
10. Inner Pbit Method (Fixed)
11. Inner Pbit Value[0-7] ... (0)
13. Inner Mark (Disable)
>
s-Save
Figure 4-59. Flows Definition - Classification Screen
Table 4-26. Flows Definition (Classification)
Outer VLAN Action Defines the Outer VLAN action for the current flow Push
Default: None Pop
None
Outer VLAN Defines the VLAN to be added to the frame. Only visible 0 – 4094
when Outer VLAN Action parameter is set to Push
Default: 0

Outer Pbit Method Defines the Pbit method used for marking. Only visible Profile
when Outer VLAN Action parameter is set to Push Fixed
Default: Fixed
Outer Pbit Profile Defines an index to the marking profile. Only visible Valid marking profile
when Outer VLAN Action parameter is set to Push and
Outer Pbit Method is set to Profile
Default: DefaultMarkingProfile1
Outer Mark Defines the Outer VLAN MARK action Enable

Outer Mark VLAN Defines the Outer VLAN value for Mark 0 - 4094
Default: 0
Inner VLAN Action Defines the Inner VLAN action for the curent flow Push
Default: None Pop
None
Inner VLAN Defines the Inner VLAN that is added to the frame 0 - 4094
Default: 0
Inner Pbit Method Defines the Inner Pbit method used for marking. Only Profile
visible when Inner VLAN Action parameter is set to Push Copy
Default: Fixed Fixed
Inner Pbit Value Defines the Inner Pbit value when the Pbit method is 0-7
defined as fixed. Only visible when Outer VLAN Action
parameter is set to Push and Outer Pbit Method is set to
Fixed
Default: 0
Inner Mark Defines the Inner VLAN MARK action Enable

Configuring the OAM

RICi-16 provides OAM -CFM (End-to-end OAM) based on IEEE 802.1ag and ITU T
Y.1731. This provides operation, administration, and maintenance capabilities in
packet switched networks.
³ To configure the OAM:

1. From the OAM (Configuration > Applications > OAM) menu, select CFM.
The OAM options appear listed as illustrated in Figure 4-60.

RICi-16
Configuration > Applications > OAM > CFM
1. Maintenance Domains >

2. Standard OAM MAC Address ... (0180C2000030)
3. Standard OAM EtherType [0-ffff] ... (8902)
>
Figure 4-60. OAM-CFM Menu
Table 4-27. OAM-CFM Menu
Standard OAM MAC Specifies the MAC Address for Operation and
Address Maintenance.
Default: 0180C2000030
Standard OAM Specifies the Operation and Maintenance EtherType. 0 - ffff

EtherType Default: 8902
2. If necessary, modify the OAM MAC Address and/or the Standard OAM Ether
Type as defined in Table 4-27.
3. Click Save.
Configuring a Maintenance Domain

RICi-16 lets you add or remove Maintenance Domains (MD). MDs are configured
with different level values to keep them separate. Each domain provides enough
information in order to perform management end-to-end monitoring.
³ To view and edit existing maintenance domain:

1. To view configured Maintenance Domains, press <f> or to scroll forward
or backward respectively.
The associated MD ID, the protocol type, the MD format, the MD name
and the MD level appear.
2. Modify the Protocol type, MD format, MD name and MD level as defined in
Table 4-28.
3. Select Save.
³ To add a maintenance domain:

1. From the CFM menu, select Maintenance Domains.
2. Press <a>.
The new MD ID appears as illustrated in Figure 4-61 .
3. Modify the Protocol type, MD format, MD name and MD level as defined in
Table 4-28.
4. Select Save.

RICi-16
Configuration > Applications > OAM > CFM > Maintenance Domains
MD ID ... (000000000102)
1. Protocol Type (Standard)

2. MD Name Format > (String)
3. MD Name ... ()
4. MD Level [0-7] ... (3)
5. Maintenance Associations >
>
a-Add New MD; f-Forward; b-Backward; d-Delete
Figure 4-61. MD Names Menu
Table 4-28. MD Names Menu
MD ID The maintenance domain’s ID
Protocol Type Indicates the maintenance domain’s protocol type Pre-Standard

Default: Standard Standard
MD Format Indicates maintenance group entity ID’s (MEG ID) domain None
name format. String
Default: String DNS Like
MAC + UINT
MD Name Indicates maintenance group entity ID’s (MEG ID) domain

name. One MD name (None) remains by default.
Default: The latest configured name or none
MD Level Indicates the maintenance domain’s level. 0-7

Default: 0
³ To delete a maintenance domain:

• Press <d>.
4.3 Performing Additional Tasks
Viewing Inventory
The inventory displays a description of the unit including its hardware revision
and power supply type.
Note The inventory is a wide table with 132 characters. It is best viewed by setting
your terminal to 132 character wide display.
RICi-16 Ver. 2.5 Performing Additional Tasks 4-63

³ To display the inventory:

• From the Main menu, select Inventory.
Hardware and software appear listed as illustrated in Figure 4-62.
• To navigate in the inventory list, use the arrow keys.
RICi-16
Inventory
ID Description Vendor type Class Entity name HWRev

1001 RICi-16 Device Chassis RICi-16 1.00
| 7001 Fast Eth Port 1 Port FAST 1
v 7002 Fast Eth Port 2 Port FAST 2
7003 Fast Eth Port 3 Port FAST 3
7004 Fast Eth Port 4 Port FAST 4
7005 E1 Port 1 Port E 1
- > >
>
Figure 4-62. Typical Inventory Screen
Note Power supply can be PS 1 or PS 2.
Viewing the License Information

RICi-16 is delivered with a prefixed software license pack, which lists the
functional features available. You can view which features are defined in the
unit's license file.
³ To view the license information:

• From the Main Menu, navigate to Utilities > License Management > Feature
Status.
The Feature Status information is displayed.
RICi-16
Utilities> License Management> Feature Status
Enable 4 E1/T1 Ports ... (Enabled)

Enable 8 E1/T1 Ports ... (Disable)
>
Figure 4-63. Feature Status Menu
4-64 Performing Additional Tasks RICi-16 Ver. 2.5

Configuring Control Port Parameters

You can manage RICi-16 using an ASCII terminal connected to the Control Port.
The management software allows you to configure the terminal baud rate.
Note The Baud Rate parameter is masked during a Telnet session.
³ To configure the control port parameters:

1. From the Main menu, navigate to Configuration > System > Terminal.
The Terminal menu appears as illustrated in Figure 4-64.
RICi-16
Configuration > System > Terminal
1. Baud Rate > (9600 bps)
>
s - Save
Figure 4-64. Control Port Menu
2. From the Terminal menu, select Baud Rate.

3. Select the desired baud rate (9600, 19200, 115200).
The default baud rate is 9600.
4. Select Save.
Changing User Access Parameters

From the User Access menu you can change the current user name and
password. RICi-16 supports two user names and passwords. The unit is supplied
with the following default user settings:
User User Name Password
1 su 1234
2 user 1234
³ To change the current user name and password:

Management Access > User Access.
The User Access menu appears.

RICi-16
Configuration > System > Management > Management Access > User Access
1. User Name ... (su)

2. Old Password ... (********)
3. New Password ... (********)
4. Confirm New Password ... (********)
>
s - Save
Figure 4-65. User Access Menu
2. In the User Access menu, select User Name, and enter a new user name. The
user name can be up to twenty characters.
3. Select Old Password, and enter the current password (default is 1234).
4. Select New password and assign a new password of up to eight characters to
the new or existing user name.
Note The password is case sensitive.
5. Select Confirm New Password to confirm the new password.

If the new password is invalid, an error message appears indicating that the
password is illegal. Assign a different password.
6. Select Save.
The new password is saved.
Transferring Software and Configuration Files

This section instructs you on installing new software releases on
RICi-16 units and transferring configuration files.
RICi-16 stores two software versions, each of them in one of the two partitions
of its flash memory, which also contains a boot program. The software is stored
in compressed format. The active version is decompressed and loaded into the
RICi-16 RAM upon power-up. The passive software is kept for backup purposes. If
the active software becomes corrupted, you can swap it with the backup. By
default, RICi-16 ships active software only.
New software releases are distributed as image files (*.img) downloaded to
RICi-16. Once downloading starts, the current backup is erased and the new
software release is placed in the backup partition instead. When downloading is
completed, the unit checks the integrity of the new software file. If approved, the
new software release becomes active and the previously active software
becomes the backup. If a failure occurs while downloading, the new version is
erased and only the previous version remains on the flash memory.
Configuration files can be uploaded for storage and backup.

Management software allows file transfer via TFTP only. You may also download
the software files to RICi-16 using the Boot Manager, using XMODEM or TFTP, as
explained in Appendix B.
³ To transfer files via TFTP:

1. From the Main menu navigate to Utilities > File Transfer > TFTP.
The File Transfer menu appears as illustrated in Figure 4-66.
RICi-16
Utilities > File Transfer > TFTP
1. Server IP Address ... (0.0.0.0)

2. Remote File Name ... ()
3. File Type (Configuration)
4. Command >
>
s - Save
Figure 4-66. TFTP Menu
2. From the File Transfer menu, perform the following:

Select Server IP Address, and enter the IP address of the TFTP server.
Select Remote File Name, and enter a file name as explained below.
For downloading, assign a name to the file that is about to be
downloaded to RICi-16.
For uploading, assign a name to the file that will be saved on the
remote server.
Select File Type, and choose whether you intend to transfer software
(IMG) or configuration (Configuration) file.
Select Save to save the changes.
Select Command to start the desired procedure:
Upload – saving software or a configuration file on a remote server.
Download – transferring software or a configuration file to
RICi-16.
RICi-16 starts the file transfer.
The TFTP file transfer process is logged by the system messages listed below,
which are stored in the log file:
TFTP – Starting Upload
TFTP – Starting Download
TFTP – Upload Failed
TFTP – Download Failed.

Resetting RICi-16
RICi-16 lets you reset the unit while preserving customized parameters or
resetting all customized parameters to the factory defaults.
Resetting to Factory Defaults
³ To reset to the default settings:

1. From the System menu, select Factory Defaults.
You are asked to confirm your request:
The device will restart. Do you want to proceed? (Y/N)
2. Press <Y> to confirm your request.
RICi-16 resets all parameters to their default settings.
Resetting the Unit

You can restart RICi-16 while preserving the parameters you configured.
³ To reset RICi-16:
1. From the Utilities menu, select Reset Device.
You are asked to confirm your request:
The device will restart. Do you want to proceed? (Y/N)
2. Press <Y> to confirm your request.
RICi-16 resets, preserving the last-saved settings.

Chapter 5
Configuring Typical
Applications
This chapter provides instructions for configuring RICi-16 for typical applications.
5.1 Application with Ethernet Cellular Backhauling

over PDH/SONET/SDH
Figure 5-1 illustrates an application where three RICi-16 units provide Ethernet
cellular backhauling, working opposite a third-party Ethernet device. Each unit has
a different interface option: channelized DS-3, 16 E1 ports, and unchannelized
T3.
Figure 5-1. Ethernet Cellular Backhauling over PDH/SONET/SDH

This application has the following requirements:
• Channelized DS-3 links to the SDH/SONET network
• E1 links to the SDH/SONET network
• T3 links to the SDH/SONET network
• Third-party Ethernet device that can work opposite all the RICi-16 interface
options.
RICi-16 Ver. 2.5 Application with Ethernet Cellular Backhauling over PDH/SONET/SDH 5-1
Chapter 5 Configuring Typical Applications Installation and Operation Manual
The configuration procedure is divided into the following stages:

1. Configuring host IP parameters
2. Configuring physical port parameters
3. Configuring the logical layer.
Table 5-1. Host IP Parameters
Device Host IP IP mask Default Gateway
RICi-16 (A) 192.188.10.12 255.255.255.0 192.188.10.1
RICi-16 (B) 192.188.10.14 255.255.255.0 192.188.10.1
RICi-16 (C) 192.188.10.16 255.255.255.0 192.188.10.1
Configuring System Parameters
Configuring the Host Parameters for RICi-16

The configuration procedure for host parameters is similar for all three RICi-16
units, except for defining different host IP addresses.
³ To define the host parameters:
1. For RICi-16 (A), navigate to the Host menu (Configuration> System >
Management> Host), and configure the host parameters as shown in
Table 5-1.
2. For RICi-16 (B) and RICi-16 (C), perform the same procedure, using the host
parameters as shown in Table 5-1 for each respective unit.
RICi-16
1. IP Address ... (192.188.10.12)

2. IP Mask ... (255.255.255.0)
3. Default gateway ... (192.188.10.1)
7. Encapsulation >
>
s - Save
Figure 5-2. Host Menu, RICi-16 (A
5-2 Application with Ethernet Cellular Backhauling over PDH/SONET/SDH RICi-16 Ver. 2.5
Installation and Operation Manual Chapter 5 Configuring Typical Applications
Configuring the System Clock Source for RICi-16

The configuration procedure for system clock parameters is similar for all three
RICi-16 units.
³ To configuring the system clock source:
1. For RICi-16 (A), navigate to the System Clock menu (Configuration> System >
System Clock).
RICi-16
Configuration > System > System Clock
1. Master Clock >

2. Fallback Clock >
>
s - Save
ESC-Previous menu; !-Main menu; &-Exit; 1M/ 1C

2. Select Master Clock.
RICi-16
1. Source > (Rx Clock)

2. Port > (T1 Port)
>
s - Save

3. Select Source and choose Rx Clock.
4. Select Port and specify the port to be used.
5. Select Save.
6. For RICi-16 (B) and RICi-16 (C), perform the same procedure, using the
system clock parameters as shown in Figure 5-4 for each respective unit.
Note For this type of configuration the network must provide the internal clock.
Configuring the Physical Layer
Configuring the Physical Layer for RICi-16 (A)

In the RICi-16 (A), you need to configure the T1 ports and the T3 channels.
Configuring the T1 Physical Layer

³ To configure the T1 physical layer:
• For the RICi-16 (A) unit, you can use the default T1 port configurations. Use
the T1 Physical Layer menu to check that the default configuration is in place
for T1 ports 1–16.
RICi-16
Configuration > Physical Ports > T1
Port (1)
TX clock Source > (System)
Line Type > (ESF)
Restoration Time (1 Sec)

2. Line Code > (B8ZS)
3. Line Interface (DSU)
4. Line Length > (0–133 ft)
>
f – forward b – backward
Configuring the T3 Interface

³ To configure the T3 interface:
• Use the T3 Physical Layer menu to ensure that the T3 interface is
channelized.
RICi-16
Port (1)

2. Line Type (M23)
3. Mapping []>
>
f – forward; b – backward
Figure 5-6. T3 Channelized

You can use the default configuration T3 channel mapping (T3 channels 1–16
mapped to T1 ports 1–16). Use the T3 mapping menu to check that the default
configuration is in place.
RICi-16
1 T1-1 11 T1-11 21 LP1
2 T1-2 12 T1-12 22 LP1
3 T1-3 13 T1-13 23 LP1
4 T1-4 14 T1-14 24 LP1
5 T1-5 15 T1-15 25 LP1
6 T1-6 16 T1-16 26 LP1
7 T1-7 17 LP1 27 LP1
8 T1-8 18 LP1 28 LP1
9 T1-9 19 LP1
10 T1-10 20 LP1
1. T1-1 4. T1-4 7. T1-7 10. T1-10 13. T1-13 16. T1-16

2. T1-2 5. T1-5 8. T1-8 11. T1-11 14. T1-14 17. LP1
3. T1-3 6. T1-6 9. T1-9 12. T1-12 15. T1-15 18. N/C
>
Figure 5-7. T3 Mapping Menu, Default Configuration
Configuring the Physical Layer for RICi-16 (B)

³ To configure the E1 physical layer:
• For the RICi-16 (B) unit, you can use the default E1 port configurations. Use
the E1 Physical Layer menu to check that the default configuration is in place
for E1 ports 1–16.
RICi-16
Port (1)
TX Clock Source (System)
Line type (G.732N-CRC)

3. Line Code (HDB3)
>
s – Save; f – forward; b – backward
Figure 5-8. E1 Port Configuration Menu
Configuring the Physical Layer for RICi-16 (C)
Configuring the T3 Interface

• Use the T3 Physical Layer menu to ensure that the T3 interface is not
channelized.
RICi-16
Port (1)
1. Structure (Unchannelized)
2. Line Type (M23)
>
s – Save; f – forward
Configuring the Logical Layer for RICi-16 (B)

For the RICi-16 (B) unit, you can use the default logical layer configuration (logical
port VCG 1 bound to E1 ports 1–16). Use the Logical Layer menu to check that
the default configuration is in place.
RICi-16
Port (1)
3. Bind to Physical Ports (1-16)
4. E1/T1 Loop Detection Enable
>
a – add; f – forward; b – backward; d – delete
Figure 5-10. Logical Layer Menu (VCG) – E1 Interface
Configuring the Logical Layer for RICi-16 (C)

For the RICi-16 (C) unit, you can use the default logical layer configuration (logical
port VCG 1 bound to T3 ports 1–2). Use the Logical Layer menu to check that the
default configuration is in place.
RICi-16
Port (1)
>
Figure 5-11. Logical Layer Menu (VCG) – T3 Interface, Not Channelized
5.2 Ethernet Services over PDH/SONET/SDH

Figure 5-1 illustrates an application where two RICi-16 units, with eight and four
E1 ports respectively, extend Ethernet services over PDH/SONET/SDH, working
opposite RAD’s Egate-100.
Figure 5-12. Ethernet Services over PDH/SONET/SDH

• E1 links to the SDH/SONET network
• Egate-100 with STM-1/OC-3 or channelized DS-3 links to the SDH/SONET
network.

3. Configuring the logical layer.
Table 5-2. Host IP Parameters
Device Host IP IP mask Default Gateway
RICi-16 (A) 192.188.10.12 255.255.255.0 192.188.10.1
RICi-16 (B) 192.188.10.14 255.255.255.0 192.188.10.1

The configuration procedure for host parameters is similar for both RICi-16 units,
except for defining different host IP addresses.
5-8 Ethernet Services over PDH/SONET/SDH RICi-16 Ver. 2.5


1. For RICi-16 (A), navigate to the Host menu (Configuration> System >
Management> Host), and configure the host parameters as shown in
Table 5-2.
2. For RICi-16 (B), perform the same procedure, using the host parameters as
shown in Table 5-2.
RICi-16
1. IP Address ... (192.188.10.12)

2. IP Mask ... (255.255.255.0)
3. Default gateway ... (192.188.10.1)
7. Encapsulation >
>
s - Save

The configuration procedure for system clock parameters is similar for both RICi-
16 units.
System Clock).
RICi-16
1. Master Clock >

2. Fallback Clock >
>
s - Save

RICi-16 Ver. 2.5 Ethernet Services over PDH/SONET/SDH 5-9

RICi-16

2. Port > (T1 Port)
>
s - Save

5. Select Save.
6. For RICi-16 (B), perform the same procedure, using the system clock
parameters as shown in Figure 5-15 for each respective unit.
Note For this type of configuration, either the Egate-100 (located in the Central Office)
should be configured for internal clock, or the network must provide the internal
clock.
Configuring the Physical Layer for RICi-16 (A)

• For the RICi-16 (A) unit, you can use the default E1 port configurations. Use
for E1 ports 1–8.
RICi-16
Port [1 – 16] (1)


3. Line Code (HDB3)
>
Figure 5-16. E1 Port Configuration Menu, RICi-16 (A)

Configuring the Physical Layer for RICi-16 (B)

• For the RICi-16 (B) unit, you can use the default E1 port configurations. Use
for E1 ports 1–4.
RICi-16
Port [1 – 16] (1)


3. Line Code (HDB3)
>
Figure 5-17. E1 Port Configuration Menu, RICi-16 (B)
Configuring the Logical Layer for RICi-16 (A)

For the RICi-16 (A) unit, you need a logical port bound to E1 ports 1-8. The
instructions in this section describe how to change the default configuration of
logical port VCG 1 from bound to E1 ports 1–16, to bound to E1 ports 1-8.
³ To configure the logical port:
1. Navigate to Configuration > Logical Layer.
The Logical Layer menu appears as illustrated in Figure 5-18.
2. Select Bind to Physical Ports
The Bind to Physical Ports menu appears as illustrated in Figure 5-19.
3. Type 2 to delete range.
You are prompted to provide a range of values to remove from the list.
4. Type 9–16.
5. Type s to save your changes.
6. Click <ESC> to return to the previous menu. The logical port is now bound to
to E1 ports 1-8, as illustrated in Figure 5-20.

RICi-16
Port (1)
>
Figure 5-18. Logical Layer Menu (VCG) – Bound to E1 Ports 1–16, RICi-16 (A)
RICi-16
Configuration > Logical Layer > Bind To Physical Ports (1–16)
1. [1-16]... (1–8)
2. Delete Range...
>
ESC-Previous menu; !-Main menu; &-Exit; A-add 1 M/ 2 C
Figure 5-19. Bind to Physical Ports, RICi-16 (A)
RICi-16
Port (1)
>
s – Save; f – forward; b - backward
Figure 5-20. Logical Layer Menu (VCG) – Bound to E1 Ports 1–8, RICi-16 (A)

Configuring the Logical Layer for RICi-16 (B)

For the RICi-16 (B) unit, you need a logical port bound to E1 ports 1-4. The
instructions in this section describe how to change the default configuration of
logical port VCG 1 from bound to E1 ports 1–16, to bound to E1 ports 1-4.
³ To configure the logical port:
2. Select Bind to Physical Ports
The Bind to Physical Ports menu appears as illustrated in Figure 5-22.
3. Type 2 to delete range.
You are prompted to provide a range of values to remove from the list.
4. Type 5–16.
5. Type s to save your changes.
6. Click <ESC> to return to the previous menu. The logical port is now bound to
to E1 ports 1-4, as illustrated in Figure 5-23.
RICi-16
Port (1)
>
Figure 5-21. Logical Layer Menu (VCG) – Bound to E1 Ports 1–16, RICi-16 (B)
RICi-16
Configuration > Logical Layer > Bind To Physical Ports (1–16)
1. [1-16]... (1–4)
2. Delete Range...
>
ESC-Previous menu; !-Main menu; &-Exit; A-add 1 M/ 2 C
Figure 5-22. Bind to Physical Ports, RICi-16 (B)

RICi-16
Port (1)
>
S – Save; f – forward; b - backward
Figure 5-23. Logical Layer Menu (VCG) – Bound to E1 Ports 1–8, RICi-16 (B)
5-14 Multiple Customer Premises Supported by Channelized DS-3 RICi-16 Ver. 2.5
5.3 Multiple Customer Premises Supported by

Channelized DS-3
Figure 5-1 illustrates an application where a RICi-16 unit with channelized DS-3
interface supports four customer premises with RICi-16T1 units and one
customer premises with RICi T1 unit.
Figure 5-24. RICi-16 with Channelized DS-3 Supporting Multiple Customer Premises
• Channelized DS-3 links to the SDH/SONET network
• RICi-16T1 units with T1 links to the SDH/SONET network.
• RICi-T1 unit with T1 links to the SDH/SONET network.

3. Configuring logical layer
4. Configuring T3 channel mapping.
RICi-16 Ver. 2.5 Multiple Customer Premises Supported by Channelized DS-3 5-15
The required channel mapping and logical ports for this application are shown in
the following table.
Table 5-3. Channel Mapping and Logical Ports
T3 channel Logical port number Logical port name Corresponding Unit
1 1 VCG 1 RICi-16T1 (A)
2 1 VCG 1 RICi-16T1 (A)
3 1 VCG 1 RICi-16T1 (A)
4 1 VCG 1 RICi-16T1 (A)
5 3 VCG 2 RICi-16T1 (B)
6 3 VCG 2 RICi-16T1 (B)
7 3 VCG 2 RICi-16T1 (B)
8 3 VCG 2 RICi-16T1 (B)
9 3 VCG 2 RICi-16T1 (B)
10 3 VCG 2 RICi-16T1 (B)
11 3 VCG 2 RICi-16T1 (B)
12 3 VCG 2 RICi-16T1 (B)
13 5 VCG 3 RICi-16T1 (C)
14 5 VCG 3 RICi-16T1 (C)
15 5 VCG 3 RICi-16T1 (C)
16 5 VCG 3 RICi-16T1 (C)
17 5 VCG 3 RICi-16T1 (C)
18 5 VCG 3 RICi-16T1 (C)
19 5 VCG 3 RICi-16T1 (C)
20 5 VCG 3 RICi-16T1 (C)
21 7 VCG 4 RICi-16T1 (D)
22 7 VCG 4 RICi-16T1 (D)
23 7 VCG 4 RICi-16T1 (D)
24 7 VCG 4 RICi-16T1 (D)
25 9 VCG 5 RICi-T1 (E)

The configuration procedure for host parameters is similar for both RICi-16 units,
except for defining different host IP addresses.
• Navigate to the Host menu (Configuration> System > Management> Host),
and configure the host parameters as illustrated in Figure 5-25.
RICi-16
1. IP Address ... (192.188.10.12)

2. IP Mask ... (255.255.255.0)
3. Default gateway ... (192.188.10.1)
7. Encapsulation >
>
s - Save
Figure 5-25. Host Menu

The configuration procedure for system clock parameters is similar for all RICi-16
units.
System Clock).
RICi-16
1. Master Clock >

2. Fallback Clock >
>
s - Save

RICi-16

2. Port > (T1 Port)
>
s - Save

5. Select Save.
6. For RICi-16 (B), (C), (D) perform the same procedure, using the system clock
parameters as shown in Figure 5-27 for each respective unit.
Note For this type of configuration, either the RICi-16 (located at the Central Office)
should be configured for internal clock, or the network must provide the internal
clock.

• Use the T3 Physical Layer menu to ensure that the T3 interface is
channelized.
RICi-16
Port (1)
2. Line Type (M23)
3. Mapping >
>

You must create logical ports for VCGs 2–5 for this application, as illustrated in
Table 5-3. You do not need to create VCG 1, which is automatically created by
RICi-16.
³ To create the VCG logical ports:
RICi-16
Port (1)
Bind To Internal Ports (17-28)
>
Figure 5-29. Logical Layer Menu (VCG), Logical Port 1

2. Type a to add a logical port.
A screen appears showing the new logical port, with all parameters empty
except the port number, and a message at the bottom prompting you to
save the VCG.
RICi-16
Port (3)
Interface Type > ()
Bind To Internal Ports (-)
Max differential delay (msec)[0 - 256] ()
1. Administrative Status ()
2. Port Name ... ()
3. E1/T1 Loop Detection
>
s – save; a – add; f – forward; b – backward; d – delete
--------------------------------------------------------
Press ‘s’ to save new VCG
Figure 5-30. Logical Layer Menu (VCG), New Logical Port
3. Type s to save the logical port.

The logical port is saved as VCG 2 (logical port 3).
RICi-16
Port (3)
Interface Type > (VCG 2)
Bind To Internal Ports (-)
>
Figure 5-31. Logical Layer Menu (VCG), Logical Port 3

4. Repeat the same procedure to create the following:
VCG 3 (logical port 5)
VCG 4 (logical port 7)
VCG 5 (logical port 9).
Note The corresponding GFP logical port is created automatically by RICi-16 for each
new VCG logical port.

You must set up the T3 channel mapping as specified in Table 5-3:
• Map channels 1–4 to logical port 1
• Map channels 25–28 to logical port 9.
³ To configure the T3 channel mapping:
1. Navigate to Configuration > Physical Layer > T3 > Mapping.
The T3 Mapping menu appears as illustrated in Figure 5-7, with the cursor
is positioned at the connection for channel 1. The list of connections at
the bottom only shows the T1 ports.
2. Type n to see the next set of connection values.
The T3 Mapping menu appears as illustrated in Figure 5-33, with the

connection values shown for the logical ports.
RICi-16
1 T1-1 11 T1-11 21 LP1
2 T1-2 12 T1-12 22 LP1
3 T1-3 13 T1-13 23 LP1
4 T1-4 14 T1-14 24 LP1
5 T1-5 15 T1-15 25 LP1
6 T1-6 16 T1-16 26 LP1
7 T1-7 17 LP1 27 LP1
8 T1-8 18 LP1 28 LP1
9 T1-9 19 LP1
10 T1-10 20 LP1
1. T1-1 3. T1-3 5. T1-5 7. T1-7 9. T1-9 11. T1-11 13. T1-13

2. T1-2 4. T1-4 6. T1-6 8. T1-8 10. T1-10 12. T1-12 14. T1-14
...(N)
>
Figure 5-32. T3 Mapping Menu, First Set of Connections
RICi-16
1 T1-1 11 T1-11 21 LP1
2 T1-2 12 T1-12 22 LP1
3 T1-3 13 T1-13 23 LP1
4 T1-4 14 T1-14 24 LP1
5 T1-5 15 T1-15 25 LP1
6 T1-6 16 T1-16 26 LP1
7 T1-7 17 LP1 27 LP1
8 T1-8 18 LP1 28 LP1
9 T1-9 19 LP1
10 T1-10 20 LP1
...(P)
15. T1-15 17. LP1 19. LP5 21. LP9
16. T1-16 18. LP3 20. LP7 22. N/C
>
Figure 5-33. T3 Mapping Menu, Second Set of Connections
3. Type 17 and then click <Enter>.

T3 channel 1 is mapped to logical port 1.
4. Follow the same procedure for T3 channels 2–4, using the arrow keys to
position the cursor.
T3 channels 2–4 are mapped to logical port 1.
5. Position the cursor at T3 channel 5, and type 18 and then click <Enter>.
7. Position the cursor at T3 channel 13, and type 19 and then click <Enter.
T3 channel 21 to is mapped logical port 7.
Figure 5-34 Illustrates the mapping after the above steps have been performed.
RICi-16
1 LP1 11 LP3 21 LP7
2 LP1 12 LP3 22 LP7
3 LP1 13 LP5 23 LP7
4 LP1 14 LP5 24 LP7
5 LP3 15 LP5 25 LP9
6 LP3 16 LP5 26 LP9
7 LP3 17 LP5 27 LP9
8 LP3 18 LP5 28 LP9
9 LP3 19 LP5
10 LP3 20 LP5
1. T1-1 3. T1-3 5. T1-5 7. T1-7 9. T1-9 11. T1-11 13. T1-13

2. T1-2 4. T1-4 6. T1-6 8. T1-8 10. T1-10 12. T1-12 14. T1-14
...(N)
>
Figure 5-34. T3 Mapping Menu, First Set of Connections
Chapter 6
Monitoring and
Diagnostics
This section describes how to:
• Monitor the system performance
• Display statistics
• Display system messages
• Detect errors
• Troubleshoot the device
• Perform connectivity tests.
6.1 Monitoring Performance
Viewing Device Status

The software provides access to the following status information:
• Device level – MAC address, connection status, connected managers and
event log file
• Physical level – Ethernet and E1/T1, T3 port status
• Logical level –VCG and GFP ports status
• Application level – MAC table and flow status.
The status information is available via the Monitoring menu.
Displaying Device Status Information

The System menu shows the interface connection status, connected managers,
Syslog and Event Log file. For a description of system messages displayed via the
Event Log file, refer to Displaying Events.
 To display system status information:
1. Navigate to Main Menu > Monitoring > System.
The Monitoring System screen appears as illustrated in Figure 6-1.
RICi-16 Ver. 2.5 Monitoring Performance 6-1

Chapter 6 Monitoring and Diagnostics Installation and Operation Manual
RICi-16
Main Menu > Monitoring > System
MAC address (00-D2-20-10-20-30)

System Up Time (12:09:12)
Date (2007-03-01)
Time (21:06:57)
Security Key (SSL + SSH)
1. Interface Status []
2. Event log []
3. Radius Statistics []
4. Syslog Statistics >
5. Connected Managers []
6. Current Clock Source >
7. Power Supply Status []
>
ESC-Previous menu; !-Main menu; &-Exit; ?-Help
Figure 6-1. Monitoring System Screen
 To display interface connection information:

• Navigate to Main Menu > Monitoring > System > Interface Status.
The Interface Status screen appears as illustrated in Figure 6-2.
RICi-16
Main Menu > Monitoring > System > Interface Status
Description Type Activation Operation Speed

ETH Port 1 Fast Eth Up Down 100000000
I ETH Port 2 Fast Eth Up Down 100000000
I ETH Port 3 Fast Eth Up Down 100000000
V ETH Port 4 Fast Eth Up Down 100000000
T1 Port 1 T1 Up Up 1544000
T1 Port 2 T1 Up Down 1544000
T1 Port 3 T1 Up Up 1544000
>
Figure 6-2. Interface Status Screen
Displaying Protection Status and Statistics

The Connected Managers menu details management access implementation,
connection type and status, depending on how the network managers are
defined.
The Radius server checks whether access authentication information is correct
(user name and password) before network access is authorized. The Radius
Statistics menu details the network access’s accept/reject statistics for each
server in use.
6-2 Monitoring Performance RICi-16 Ver. 2.5

Installation and Operation Manual Chapter 6 Monitoring and Diagnostics
Displaying the Connected Managers Status

 To display connected managers status:
• From the System menu (Monitoring >System), select Connected Managers.
The Connected Managers screen appears as illustrated in Figure 6-3.
RICi-16
Main Menu > Monitoring > System > Connected Managers
Index IP Address Connection Type User Name

1 172.18.187.60 SSH su
2 172.18.187.60 SSL su
3 172.18.187.166 TELNET su
4 172.18.187.166 TELNET su
>
Figure 6-3. Connected Managers Screen
Displaying Radius Statistics

 To display radius statistics:
1. From the System menu (Monitoring > System), select Radius Statistics.
The Radius Statistics screen appears as illustrated in Figure 6-4. The
parameters are described in Table 6-1.
RICi-16
Main Menu > Monitoring > System > Radius Statistics
Server 1 Server 2 Server 3 Server 4

Access Requests 0 0 0 0
Access Retransmits 0 0 0 0
Access Accepts 0 0 0 0
Access Rejects 0 0 0 0
Access Challenges 0 0 0 0
Malformed Responses 0 0 0 0
Bad Authenticators 0 0 0 0
Pending Requests 0 0 0 0
Timeouts 0 0 0 0
Unknown Types 0 0 0 0
Packets Dropped 0 0 0 0
>
c-Clear Counters
Figure 6-4. Radius Statistics Screen

Table 6-1. Radius Statistics Parameters
Parameter Description
Access Requests The number of Radius access requests sent to the server
excluding retransmissions.
Access Retransmits The number of Radius access requests retransmitted to the

server.
Access Accepts The number of Radius access acceptances (valid and invalid)
received from the server.
Access Rejects The number of Radius access rejects (valid and invalid)
Access Challenges The number of Radius access challenges (valid and invalid)
Malformed Responses The number of malformed Radius access responses received

from the server. This does not include invalid authenticators
or signature attributes.
Bad Authenticators The number of Radius access responses containing invalid

authenticators or signatures received from the server.
Pending Requests The number of Radius access requests sent to the server
that are still pending.
Timeouts The number of Radius access requests sent to the server

that have a timeout status.
Unknown Types The number of Radius access requests received from the
server that have an unknown type status.
Packets Dropped The number of Radius access responses received from the
server that have been dropped.

Displaying the Physical Layer Status

You can view the status of the unit’s physical ports.
Displaying the Ethernet Port Status

 To display the Ethernet port status:
1. From the Ethernet menu (Monitoring > Physical Ports > Ethernet), select
Status.
The Fast Ethernet Status screen appears as illustrated in Figure 6-5. The
2. Press <f> to select the port number.
RICi-16
Main Menu > Monitoring > Physical Ports > Ethernet > Status
Port (1)
Port Type (SFP 1310nm 15km LC SM)

Administrative Status (Enable)
Operation Status (Up)
Speed & Duplex > (100Mbps – TX Full Duplex)
Flow Control (Enable)
1. SFP Information >
>
f - Forward; b - Backward
Figure 6-5. Ethernet Status Screen
Table 6-2. Ethernet Status Parameters
Port The port slot number to be handled.
Port Type The interface used for the port
Admistrative Status Whether the interface is enabled or disabled.
Operation Status The actual operational status of the link (Up or Down).
Speed & Duplex The current data rate and duplex mode of the link
(100 – full, 100 –half, 10 – full, or 10 - half).
Flow Control Whether flow control is enabled or disabled.

 To display the SFP information:

1. From the Ethernet Starus menu (Monitoring > Physical Ports > Ethernet >
Status), select SFP Information.
The SFP Information screen appears as illustrated in Figure 6-6.
RICi-16
Monitoring >Physical Ports >Ethernet >Status >SFP Information
Connector Type (LC)

Manufacturer Name (FIBERXON INC.)
Manufacturer PN (FTM-3001C-SL15G)
Typical Max. Range [m/km] (15)
Wave Length [nm] (1310)
Fiber Type (SM)
>
Displaying the E1/T1 Port Status

 To display the E1/T1 port status:
1. From the T1 menu (Monitoring > Physical Ports > T1), select Status.
The E1/T1 Status screen appears as illustrated in Figure 6-7.
RICi-16
Main Menu > Monitoring > Physical Ports > T1 > Status
1. Port [1-16] (1)
Connector Type (RJ45)

Administrative Status (Up)
Operation Status (Up)
>
F - Forward; B - Backward
Figure 6-7. E1/T1 Status Screen

Displaying the T3 Port Status

 To display the T3 port status:
1. From the T3 menu (Monitoring > Physical Ports > T3), select Status.
The T3 Status screen appears as illustrated in Figure 6-8.
RICi-16
Main Menu > Monitoring > Physical Ports > T3 > Status
1. Port [1-16] (1)
Connector Type (BNC)

Administrative Status (Up)
Operation Status (Down)
>
Figure 6-8. T3 Status Screen
Displaying Logical Layer Status

You can view the status of the GFP and VCG logical ports.
For a description of the logical layer statistics, refer to Displaying Logical Layer
Statistics.
Displaying the GFP and VCG Logical Ports Status

 To display the GFP and VCG logical port status:
1. From the Logical Layer menu (Monitoring > Logical Layer), select Status.
The GFP and VCG Logical Ports Status screen appears as illustrated in
Figure 6-9 and Figure 6-10.
RICi-16
Monitoring > logical Layer > Status
Port (1)
Interface Type (GFP)

Port Name (GFP 1)
GFP Frame Delineation (Not Delineated)
>
Figure 6-9. GFP Logical Port Status Screen

RICi-16
Monitoring > logical Layer > Status
Port (1)

Port Name (VCG 1)
1. L-CAS Member Status []
>
Figure 6-10. VCG Logical Port Status Screen
 To display L-CAS member status:

1. From the Logical Port Status menu (Monitoring > Logical Layer > Status),
select L-CAS Member Status.
The L-CAS Status screen appears as illustrated in Figure 6-11.
RICi-16
Monitoring >Logical Layer >Status >L-CAS Member Status
Link Source Status Sink Status

1 OK OK
2 OK OK
3 OK OK
I 4 OK OK
I 5 OK OK
V 6 Fail Fail
7 OK OK
8 OK OK
9 OK OK
10 OK OK
11 OK OK
12 OK OK
>

Displaying Application-Level Status

The RICi-16 can operate in Bridge or Flow mode, which can be configured by the
user.
Displaying Bridge Information

In Bridge mode, the unit provides information on the MAC addresses (static and
learned) and their bridge port assignments, as well as VLAN IDs and their bridge
port assignments.
 To display the MAC table:
• From the Bridge menu (Monitoring > Application > Bridge), select View MAC
Table.
The MAC Table screen appears as illustrated in Figure 6-12 and
Figure 6-13. The parameters are described in Table 6-3.
RICi-16
Main Menu > Monitoring > Application > Bridge > View MAC Table
VLAN ID MAC address Bridge port Status
1 1 111111111111 1 Static
| 2 2 222222222222 2 Dynamic
v 3 3 333333333333 3 Static
4 4 444444444444 3 Dynamic
5 5 555555555555 5 Dynamic
>
x-Clear Table
Figure 6-12. View MAC Table (VLAN-Aware)
RICi-16
Main Menu > Monitoring > Application > Bridge > View MAC Table
MAC address Bridge port Status
1 11-11-11-11-11-11 1 Static
| 2 22-22-22-22-22-22 2 Dynamic
V 3 33-33-33-33-33-33 3 Static
4 44-44-44-44-44-44 3 Dynamic
5 55-55-55-55-55-55 5 Dynamic
>
Figure 6-13. View MAC Table (VLAN-Unaware)

Table 6-3. View MAC Table Parameters
VLAN ID The VLAN ID corresponding to the MAC address (1 – 4094).

(VLAN aware mode only)
MAC Address The destination MAC address in a frame to which this

entry's filtering information applies.
Bridge Port The port number of the port from which a frame must be
received in order for this entry's filtering information to
apply.
Status The status of the entry (Static or Dynamic).
Displaying Flow Information

In flow mode the unit provides information on incoming customer traffic. This
traffic is mapped to the Ethernet flows according to user defined per-port
criteria.
 To display flow information:
• From the Application menu (Monitoring > Application), select Flows.
The Flow screen appears as illustrated in Figure 6-14. The parameters are
described in Table 6-4.
RICi-16
Main Menu > Monitoring > Application > Flows
Flow [1-64] (2)

Name (Flow1)
Fwd Green Packets (0)
Fwd Green Bytes (0)
Fwd Yellow Packets (0)
Fwd Yellow Bytes (0)
Dscrd Green Packets (0)
Dscrd Green Bytes (0)
Dscrd Yellow Packets (0)
Dscrd Yellow Bytes (0)
Dscrd Red Packets (0)
Dscrd Red Bytes (0)
>
f-Forward b-Backward c-Clear Statistics
Figure 6-14. View Flow Screen

Table 6-4. View Flow Parameters
Flow [1-64] Flow ID
Name Flow name corresponding to the flow ID.
Fwd Green Packets Number of forwarded packets that were marked as green
by the policer located on the flow.
Fwd Green Bytes Number of forwarded bytes that were marked as green by
the policer located on the flow.
Fwd Yellow Packets Number of forwarded packets that were marked as yellow
by the policer located on the flow.
Fwd Yellow Bytes Number of forwarded bytes that were marked as yellow by
the policer located on the flow.
Dscrd Green Packets Number of discarded packets that were marked as green by
the policer located on the flow, due to lack of egress buffer
space.
Dscrd Green Bytes Number of discarded bytes that were marked as green by
space.
Dscrd Yellow Packets Number of discarded packets that were marked as yellow
by the policer located on the flow, due to lack of egress
buffer space.
Dscrd Yellow Bytes Number of discarded bytes that were marked as yellow by
space.
Dscrd Red Packets Number of discarded packets that were marked as red by
space.
Dscrd Red Bytes Number of discarded bytes that were marked as red by the
policer located on the flow, due to lack of egress buffer
space.

Displaying OAM Information

 To display the OAM status:
• From the OAM.CFM menu (Monitoring > Application > OAM.CFM), select
Status.
The OAM.CFM Status screen appears as illustrated in Figure 6-15). The
RICi-16
Monitoring > Application > OAM.CFM > Status
1. MD ID ... (0)
2. MA ID ... (0)
3. MEP ID [1-8191] ... (0)
4. Remote MEP ID [1-8191] ... (0)
>
Figure 6-15. OAM.CFM Status Screen
Table 6-5. OAM.CFM Status
MD ID ID of the Maintenance group
MA ID ID of the MAC address
MEP ID[1-8191] ID of the Maintenance entity group
Remote Mep ID[1 – 8191] Remote ID of the Maintenance entity group

Displaying Interface Statistics

You can display statistical data for the Ethernet, E1/T1, T3 ports, and the logical
layer.
Displaying Ethernet Statistics
 To view Ethernet statistics:

1. In the Main menu, navigate to Monitoring > Physical Ports > Ethernet.
2. Select Statistics.
3. Type f to navigate through port numbers.
The Ethernet Statistics screen appears as illustrated in Figure 6-16.
 To clear Ethernet statistics:

• In the Ethernet Statistics menu, type c to clear port statistics.
RICi-16
Monitoring > Physical Ports > Ethernet > Statistics
Port (1)
Rx Correct Frames (709073132)

Rx Correct Octets (533197630)
Rx FCS Errors (0)
Tx Correct Frames (21532)
Tx Correct Octets (2139845)
Tx Single Collision (0)
Tx Collision (0)
Tx Multiple Collision) (0)
Tx Deferred Transmissions (0)
Tx Late Collisions (0)
Tx Congestion Dropped Frames (0)
>
f-Forward; b-Backwards; c-Clear statistics
ESC-Previous menu; !-Main menu; &-Exit; 1 M/ 1 C
Figure 6-16. Ethernet Statistics
Displaying E1/T1 Statistics

E1/T1 statistics can be displayed for 15-minute intervals or 1-day periods.
 To view E1/T1 port statistics:

1. In the Main menu, navigate to Monitoring > Physical Ports > E1/T1 >
Statistics.
2. Select one of the following:
 15 Min. Intervals – To view statistics for current and previous 15-minute
intervals.

 1 Day Interval – To view statistics for current one-day intervals.

The E1/T1 Statistics screen appears as illustrated in Figure 6-17. The
statistics are described in Table 6-6.
 To clear statistics:
• In the Statistics menu, select Clear Statistics to clear all E1/T1 statistics.
RICi-16
Monitoring > Physical Ports > E1/T1 > Statistics>15 Min
Intervals
1. Port [1 – 16] ... (1)

2. Interval [0-96] ... (0)
Time Elapsed (10)

ES (0)
SES (0)
UAS (0)
BES (0)
>
f-Forward; c-Clear Statistics: ˆF-Frw(Int; ˆB-Bkw(Int)
Figure 6-17. E1/T1 Statistics
Table 6-6. E1/T1 Statistics Parameters
Port number Statistics regarding selectable port number
Interval number Selectable interval (interval 0 displays the current interval)
Time elapsed For interval 0 displays number of seconds passed from the start
time of the interval
ES Number of seconds where errored seconds (ES) are detected. For

ESF and E1-CRC links an Errored Second is a second with:
One or more Path Code Violation
or,
One or more Out of Frame defects
or
One or more Controlled Slip events
or
A detected AIS defect.
For D4 and E1-noCRC links, the presence of Bipolar Violations also
triggers an Errored Second. This is not incremented during an
Unavailable Second.

SES Number of seconds where SES is detected.

A Severely Errored Second for ESF signals is a second with:
320 or more Path Code Violation Error Events
or
or
A detected AIS defect.
For E1-CRC signals, a Severely Errored Second is a second with:
832 or more Path Code Violation error events
or
One or more Out of Frame defects.
For E1-noCRC signals, a Severely Errored Second is a 2048 LCVs or
more.
For D4 signals, a Severely Errored Second is:
A count of one- second intervals with Framing Error events
or
An OOF defect
or
1544 LCVs or more.
Controlled slips are not included in this parameter. This is not
incremented during an Unavailable Second.
UAS Number of seconds where SES is detected as Unavailable Seconds

(UAS). Calculated by counting the number of seconds for which the
interface is unavailable. The DS1 interface is said to be unavailable
from the onset of 10 contiguous SESs, or the onset of the
condition leading to a failure.
BES Number of seconds where BES is detected. A Bursty Errored

Second is a second with fewer than 320 and more than 1 Path
Coding Violation error events, no Severely Errored Frame defects
and no detected incoming AIS defects. Controlled slips are not
included in this parameter. This is not incremented during an
Unavailable Second. It applies to ESF signals only. Valid only for E1-
CRCon and T1-ESF
Displaying T3 Statistics
T3 statistics can be displayed for 15-minute intervals or 1-day periods.
 To view T3 port statistics:

1. In the Main menu, navigate to Monitoring > Physical Ports > T3 > Statistics.
2. Select one of the following:
 15 Min. Intervals – To view statistics for current and previous 15-minute
intervals.
 1 Day Interval – To view statistics for current one-day intervals.

The T3 Statistics screen appears as illustrated in Figure 6-18. The

statistics are described in Table 6-7.
 To clear statistics:
• In the Statistics menu, select Clear Statistics to clear all E1/T1 statistics.
RICi-16
Monitoring > Physical Ports > T3> Statistics>15 Min Intervals
Port [1 - 2] (1)
1. Interval [0 - 96] (0)
Time Elapsed (sec) (10)

LES (0)
PES (0)
PSESS (0)
CES (0)
CSES (0)
SEFS (0)
UAS (0)
>
f-Forward; c-Clear Statistics; ^F-Frw (Int); ^B-Bkw (Int)
Figure 6-18. T3 Statistics
Table 6-7. T3 Statistics Parameters
Port number Statistics regarding selected port number
Interval number Selectable interval (interval 0 displays the current interval)
Time elapsed For interval 0 displays number of seconds passed from the start time
of the interval
LES Number of seconds where Line Errored Seconds are detected. A Line
Errored Second is a second with:
One or more Code Violations
or,
One or more Loss of Signal defects
PES Number of seconds where P-bit Errored Seconds are detected.

A P-bit Errored Second is a second with:
One or more Path Code Violation Error Events
or
or
A detected incoming AIS defect.
This counter is not incremented when Unavailable Seconds (UAS) are
counted.

PSES Number of seconds where P-bit Severely Errored Seconds are

detected.
A P-bit Errored Second is a second with:
44 or more Path Code Violation Error Events
or
or
counted.
CES Number of seconds where C-bit Errored Seconds are detected.

A C-bit Errored Second is a second with:
One or more CCV Error Events
or
or
counted.
Note: This count is only for the SYNTRAN and C-bit Parity DS3
applications.
CSES Number of seconds where C-bit Severely Errored Seconds are

detected.
A C-bit Severely Errored Second is a second with:
44 or more CCV Error Events
or
or
counted.
Note: This count is only for the SYNTRAN and C-bit Parity DS3
applications.
SEFS Number of seconds where Severely Errored Framing Seconds are

detected.
A Severely Errored Framing Second is a second with:
or
This counter is not incremented during unavailable seconds
UAS Number of seconds where the interface is unavailable. The DS3

interface is said to be unavailable from the onset of 10 contiguous
LESs, or the onset of the condition leading to a failure.

Displaying Logical Layer Statistics

You can display the statistics for the GFP logical ports. There are no statistics for
VCG logical ports.
 To view the Logical Layer statistics:

• In the Main menu, navigate to Monitoring > Logical Layer > Statistics.
The Logical Layer Statistics screen appears as illustrated in Figure 6-19.
The statistics are explained in Table 6-8.
 To clear Logical Layer statistics:

• In the Logical Layer Statistics menu, type c to clear port statistics.
RICi-16
Monitoring > Logical Layer > Statistics
Port (2)
Interface Type > (GFP)

Port name (GFP 1)
Rx Correct Frames (0)

Rx Correct Octets (0)
Rx cHEC Errors (0)
Rx tHEC Errors (0)
Rx FCS Errors (0)
TX Frames (453160)
TX Octets (45609507)
Tx congestion Dropped Frames (0)
>
f-Forward; b-Backward; c-Clear Statistics
ESC-Previous menu; !-Main menu; &-Exit; 1 M/ 1 C
Figure 6-19. Logical Layer Statistics (GFP)
Table 6-8. Logical Layer Statistics
Port Logical port being monitored
Interface Type Interface type
Port Name Given name to logical port
RX Correct Frames Total number of frames received
RX Correct Octets Total number of octets received
RX cHEC Errors Total number of frames received with errors in the cHEC
field of the header
RX tHEC Errors Total number of frames received with errors in the tHEC
field of the header

RX FCS Errors Total number of frames received with frame checksum

errors
TX Frames Total number of frames transmitted
TX Octets Total number of octets transmitted
TX Congestion Dropped Total number of frames dropped because of congestion

Frames
6.2 Handling Alarms and Traps

RICi-16 maintains a log file, which can hold up to 1000 system messages. All
events are time-stamped. In addition, RICi-16 allows logging and sharing of
system events on a server instead of internally. The statistical information of
logging and sharing system events is displayed in the Syslog menu.
Displaying Events
 To access the event log:
1. In the Main menu, navigate to Monitoring > System > Event Log.
The Event Log screen appears as illustrated in Figure 6-20.
2. In the Event Log screen, use <Ctrl-u> to scroll up, <Ctrl-d> to scroll down,
<Ctrl-r> to move right and <Ctrl-l> to move left in the Events list.
RICi-16
Monitoring > System > Event Log Current time: 03:07:59
Source Description Information Severity

E1 Port 2 LINK_DOWN E1 port Major
E1 Port 6 LINK_UP E1 port Minor
I Eth Port 1 LINK_DOWN Eth port Major
I T1 Port 4 LINK_DOWN T1 Port Major
V T1 Port 3 LINK_DOWN T1 Port Major
T1 Port 2 LINK_DOWN T1 Port Major
T1 Port 1 LINK_UP T1 Port Major
->>
>
x - Clear Table
ESC-Previous menu; !-Main menu; &-Exit; ?-help
Figure 6-20. Typical Log File
Table 6-9 presents some of the event types that appear in the event log.
RICi-16 Ver. 2.5 Handling Alarms and Traps 6-19

Table 6-9. Event List
Code Event Description
System Events
10 LINK_UP A port has been connected
20 LINK_DOWN A port has been disconnected
30 HW_FAILURE Hardware failure has been detected
32 PS_FAILED_ON (Dual power supply only) One of the power supplies has failed
33 PS_FAILED_OFF (Dual power supply only) The power supply has been turned back
on after a failure
40 SNMP_AUTH_FAIL SNMP Authentication Failure trap has been received
50 WEB_START Web session has been initiated
51 WEB_FINISH Web session has been finished
70 TFTP_START TFTP session has been initiated
71 TFTP_FINISH TFTP session has been finished
72 TFTP_FAILURE TFTP session has failed
90 TELNET_ACCESS_DENIED Access via Telnet was denied, either because the current IP address
does not appear in the manager list, or because Telnet access was
disabled via user configuration.
91 WEB_ACCESS_DENIED Access via Web was denied, either because the current IP address
does not appear in the manager list, or because web access was
92 SNMP_ACCESS_DENIED Access via SNMP was denied, either because the current IP address
does not appear in the manager list, or because SNMP access was
100 E1/T1 Major An E1/T1 event that has the severity “major”.
101 E1/T1 Minor An E1/T1 event that has the severity “minor”.
102 E1/T1 Event There is a momentary even on the E1/T1.
105 T1 FDL Remove LLB An event occurs for removal of a local loopback.
108 T1 FDL LLB Message sent to begin a local loopback.
111 SFP Event Indicates whether SFP is present, not present, or of incompatible
type.
112 Signal Degrade On The number of PDH E1/T1/T3 errors were above the threshold; the
line was disconnected.
113 Signal Degrade Off Traffic was renewed after the number of errors dropped beneath
the threshold.
160 MAC Protection Violation Violation occurred either because a frame was received with an
incorrect MAC.
180 Loop Detected A loop was detected on Ethernet and GFP.
6-20 Handling Alarms and Traps RICi-16 Ver. 2.5

181 Loop Recovery The loop on Ethernet and GFP has stopped.
182 Cold Start The device has been powered up.
183 Login Login has succeeded.
184 Failed Login Login has failed.
OAM Ag Events
0x1001 CC OK OAM connectivity check (CC) with remote MEP has been confirmed
0x1002 CC Mismerge A MEP receives a CCM frame with correct MEG Level but incorrect
MEG ID.
0x1003 Unexpected MEP On A MEP receives a CCM frame with correct MEG Level, correct MEG ID
but with unexpected MEP ID.
0x1004 Unexpected MEP Off During an interval equal to 3.5 times the CCM transmission periods,
the MEP does not receive CCM frames with an unexpected MEP ID.
0x1005 Unexpected Period On A MEP receives a CCM frame with correct MEG Level, correct MEG ID,
correct MEP ID, but with a Period field value different than its own
CCM transmission period.
0x1006 CC Failure On A MEP receives no CCM frames from a peer MEP (MEP ID = i) during
an interval equal to 3.5 times the CCM transmission period.
0x1007 RDI Detected On A MEP receives a CCM frame with the RDI field set.
0x1008 Unexpected MD Level On A MEP receives a CCM frame with incorrect MEG Level.
0x1009 Unexpected MD Level Off During an interval equal to 3.5 times the CCM transmission period,
the MEP does not receive CCM frames with incorrect MEG Level.
0x100A Frame Loss Ratio On The number of service frames not delivered divided by the total
number of service frames during time interval T, where the number
of service frames not delivered is the difference between the
number of service frames arriving at the ingress ETH flow point and
the number of service frames delivered at the egress ETH flow point
in a point-to-point ETH connection.
0x100C Frames Above Delay On Frame Delay can be specified as round-trip delay for a frame, where
Frame Delay is defined as the time elapsed since the start of
transmission of the first bit of the frame by a source node until the
reception of the last bit of the loop backed frame by the same
source node, when the loopback is performed at the frame's
destination node.
0x100 Frames Above Delay Off Frame Loss Ratio Threshold has been reached (exceeded / dropped
D below)
0x100E Frames Above Delay Var On Frame Delay Variation is a measure of the variations in the Frame
Delay between a pair of service frames, where the service frames
belong to the same CoS instance on a point-to-point ETH
connection.
0x1010 Unavailability Ratio The total number of unavailable seconds divided by the elapsed
Dropped On time, and the defect is on if the unavailability ratio threshold is
RICi-16 Ver. 2.5 Handling Alarms and Traps 6-21


exceeded.
0x1011 Unavailability Ratio The exit criteria of the above, i.e. when the ratio is below threshold.
Dropped Off
Refer to Table 6-10 for the list of traps sent by RICi-16
Table 6-10. Traps List
Trap Description OID
coldStart The unit has been restarted 1.3.6.1.6.3.1.1.5.1

authenticationFailure User authentication has failed 1.3.6.1.6.3.1.1.5.5
linkDown Interface has been disconnected 1.3.6.1.6.3.1.1.5.3
linkUp Interface has been connected 1.3.6.1.6.3.1.1.5.4
risingAlarm User-set threshold for OAM ag 1.3.6.1.2.1.16.0.1
alarm has been exceeded
fallingAlarm User-set threshold for OAM ag 1.3.6.1.2.1.16.0.2
alarm is no longer exceeded
dsx1LineStatusChange Status change of E1/T1 ports 1.3.6.1.2.1.10.18.15.0.1
tftpStatusChangeTrap TFTP operation has successfully 1.3.6.1.4.1.164.6.1.0.1
completed or has failed
agnStatusChangeTrap The device status has changed 1.3.6.1.4.1.164.6.1.0.2

prtStatusChangeTrap SFP module is removed or inserted 1.3.6.1.4.1.164.6.1.0.3
agnPowerFailureTrap Power failure occurred 1.3.6.1.4.1.164.6.1.0.13
ethOamCfmDefectCondition Status change of OAM ag MEP 1.3.6.1.4.1.164.3.1.6.1.3.0.1
dsx3LineStatusChange Status change of T3 ports 1.3.6.1.2.1.10.30.15.0.1
prtLoopDetectTrap Loop detected/cleared on Ethernet 1.3.6.1.4.1.164.6.1.0.32
or GFP port
 To clear the event log:

• In the Event Log screen, press <x>.
6-22 Handling Alarms and Traps RICi-16 Ver. 2.5

Displaying Syslog Statistics

 To access the Syslog Statistics:
1. In the Main menu, navigate to Monitoring > System > Syslog Statistics.
The Syslog Statistics screen appears as illustrated in Figure 6-21.
RICi-16
Monitoring > System > Syslog Statistics
Total Tx Messages (0)

Unqueued Dropped Messages (4)
>
c - Clear
ESC-Previous menu; !-Main menu; &-Exit; ?-help
Figure 6-21. Typical Log File
 To clear the Syslog:

• In the Syslog Statistics screen, press <c>.
6.3 Testing the RICi-16 Unit

RICi-16 checks network integrity by running a number of tests. All RICi-16
network integrity testing can be performed from the Diagnostics menu.
You can perform the following diagnostics tests:
• Ping
• Trace route
• Cable test
• T1 loopback
• T3 loopback
• BERT
• OAM test
RICi-16 Ver. 2.5 Testing the RICi-16 Unit 6-23

Running a Ping Test

You can ping the remote IP host to check the IP connectivity.
 To ping an IP host:
1. In the Main menu, navigate to Diagnostics > Ping.
The Ping menu appears as illustrated in Figure 6-22.
2. In the Ping menu, configure the following:
 Destination IP Address. This is the IP address of the host that you intend
to ping. Use values between 0.0.0.0 and 255. 255. 255. 255.
 Number of Frames to Send. Select 0 to send a continuous stream of
frames, or 1-50 to send a specified number of frames.
3. To start sending pings, select Send Ping.
The results are displayed in the lower scrolling message window.
4. To stop sending pings, select Stop Ping.
RICi-16
Diagnostics > Ping
1. Destination IP Address ... (0.0.0.0)
2. Number of Frames to Send [0-50] ... (10)
3. Send Ping
4. Stop Ping
>
Figure 6-22. Ping Menu
Tracing the Route

This diagnostic utility traces the route through the network from RICi-16 to the
destination host.
 To trace a route:
1. In the Main menu, navigate to Diagnostics > Trace Route.
The Trace Route menu appears as illustrated in Figure 6-23.
2. In the Trace Route menu, select Destination IP Address and enter the IP
address of the host to which you intend to trace the route.
3. To start tracing, select Display Trace Route.
RICi-16 starts tracing the route, displaying the IP addresses of all hop
nodes.
4. To stop the tracing, select Stop Trace Route.
6-24 Testing the RICi-16 Unit RICi-16 Ver. 2.5

RICi-16
Diagnostics > Trace Route
1. Destination IP Address ... (0.0.0.0)

2. Display Trace Route
3. Stop Trace Route
>
Figure 6-23. Trace Route Menu
Running a Cable Test

This diagnostic can be used to check the quality of the Tx/Rx cables, connectors
and terminations by running a cable test.
 To run the cable test:

1. In the Main menu, navigate to Diagnostics > Cable Test.
The Cable Test menu appears as illustrated in Figure 6-24.
2. From the Cable Test menu, type F to select the RICi-16 user port for the cable
that you intend to test.
3. Select the Start Test command to initiate the virtual cable test on the
selected port.
The virtual cable test results are displayed for receive and transmit wires:
 Tx/Rx test results:
Fail: Tx/Rx cable has a non-compliant termination i.e. less than

85 or greater than 115
Normal: Tx/Rx cable is normal and has a termination between the
IEEE specified limits of 85 to 115
Open: Tx/Rx cable is not terminated
Short: Tx/Rx cable is shorted
 Rx/Tx distance of reflection: Approximate distance to the location of a

cable break or short in meters.

RICi-16
Diagnostics > Cable Test
Port > (3)
Tx Test Result > (Normal)

Tx Distance of Reflection ... (2m)
Rx Test Result > (Normal)
Rx Distance of Reflection ... (2m)
1. Command > (Start Test)
>
f – Forward; b-Backwards
>ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
Figure 6-24. Virtual Cable Test Menu
Running Loopback Tests
Testing E1/T1 Links

This diagnostic utility performs remote loopback tests on the E1/T1 links in order
to determine the source of a break in the data flow. These loopbacks are
performed on the device toward the TDM network.
 To execute a loopback test on an E1/T1 link:

1. In the Main menu, navigate to Diagnostics > E1/T1 Loopback.
The E1/T1 Loopback menu appears as illustrated in Figure 6-25.
2. Navigate to the E1/T1 link to test, by using f and b.
3. Select the Loopback State and specify Remote to perform remote loopback
or Disable to disable loopback testing.
4. Select Duration and enter a value between 0 and 3600 to specify how many
seconds to run the loopback test.
RICi-16
Diagnostics > E1/T1 Loopback
Port [1 – 4] (1)
1. Loopback State (Disable)

2. Duration (sec)[0 – 3600] ... (60)
>
f-Forwards; b-Backwards
Figure 6-25. E1/T1 Loopback Menu

Testing T3 Links
This diagnostic utility performs remote loopback tests on the T3 links in order to
determine the source of a break in the data flow. These loopbacks are performed
on the device toward the TDM network.
 To execute a loopback test on a T3 link:

1. In the Main menu, navigate to Diagnostics > T3 Loopback.
The T3 Loopback menu appears as illustrated in Figure 6-26.
2. Navigate to the T3 link to test, by using f and b.
3. Select the Loopback State and specify Remote to perform remote loopback
or Disable to disable loopback testing.
4. Select Duration and enter a value between 0 and 3600 to specify how many
seconds to run the loopback test.
RICi-16
Diagnostics> T3 Loopback
Port (1)
1. Loopback State (Disable)

2. Duration (sec)[0 – 3600] ... (60)
>
f-Forward; b-Backwards
Figure 6-26. T3 Loopback Menu
Local Loopback
RICi-16 supports FDL (facility data link)-activated local loopback (LLB) code only.
This means that when RICi-16 receives a loop up/down pattern it is configured on
the receiving port towards the TDM network.
Performing Bit Error Rate Test (BERT)
Testing E1/T1 Physical Layers

This diagnostics utility performs a Bit Error Rate Test (BERT) to check that the
E1/T1 physical layer is free of errors.
 To perform a Bit Error Rate Test on the E1/T1 physical layer:

1. In the Main menu, navigate to Diagnostics > BERT
2. Select E1/T1.
The BERT E1/T1 menu appears as illustrated in Figure 6-27.
3. Navigate to the E1/T1 port to test, by using <f> and .

4. Define the pattern according to your testing requirements as illustrated in

Figure 6-26.
5. Select Send BERT and set it to On to start the test.
6. Select Save.
The test starts. If errors occur, Bit Error Count indicates how many errors.
7. If desired, select Inject Error to inject an error.
Indication of inject error is shown in the lower scrolling message window,
as illustrated in Figure 6-28.
RICi-16
Main Menu > Diagnostics > BERT > T1
Port [1-4] (1)
1. Pattern > (2ˆ15-1)

2. Send BERT (OFF)
>
f-Forward b-Backward
Figure 6-27. BERT Menu
RICi-16
Main Menu > Diagnostics > BERT
Port (1)
Sync State > (Not Sync)
Bit Error Count (0)
1. Pattern > (2ˆ15-1)
2. Send BERT (ON)
3. Inject Error
>
---------------------------------------------------------
Inject Error
Inject Error
Figure 6-28. BERT Menu with Inject Error

Table 6-11. BERT Parameters
Port Index of E1/T1 port 1–Number of E1/T1 ports

(4 or 8)
Sync State E1/T1 port synchronization status. This parameter is Not Sync
read-only and cannot be configured. Sync
Note: The BERT is executed only if Sync State is
Sync.
Bit Error Count Number of bit errors occurred in test. This 0-Number of bit errors
parameter is read-only and cannot be configured
Pattern Bit pattern to send 2^11-1

QRSS
2^15-1
Send BERT Set to On to start the test On

Set to Off to stop the test. Off
Inject Error Select this to inject an error into the test .
Testing T3 Physical Layers

This diagnostics utility performs a Bit Error Rate Test (BERT) to check that the T3
physical layer is free of errors.
 To perform a Bit Error Rate Test on the T3 physical layer:

1. In the Main menu, navigate to Diagnostics > BERT
2. Select T3.
3. The BERT T3 menu appears as illustrated in Figure 6-29.
4. Navigate to the T3 port to test, by using <f> and .
5. Define the pattern according to your testing requirements as illustrated in
Table 6-12.
6. Select Send BERT and set it to On to start the test.
7. Select Save.
The test starts. If errors occur, Bit Error Count indicates how many errors.
RICi-16
Main Menu > Diagnostics > BERT > T3
Port (1)
Sync State > (Not Sync)
Bit Error Count (0)
1. Pattern > (2ˆ15-1)
2. Send BERT (Off)
>ESC-Previous menu; !-Main menu; &-Exit; ?-Help
Figure 6-29. BERT Menu

Table 6-12. BERT Parameters
Port Index of T3 port 1–Number of T3 ports (4)
Sync State T3 port synchronization status. This Not Sync

parameter is read-only and cannot be Sync
configured.
Note: The BERT is executed only if Sync
State is Sync.
Bit Error Count Number of bit errors occurred in test. 0-Number of bit errors
This parameter is read-only and cannot
be configured
Pattern Bit pattern to send 2^11-1

QRSS
2^15-1
Send BERT Set to On to start the test On

Set to Off to stop the test. Off
Running OAM Tests

This diagnostic utility traces the OAM monitoring statistics on selected virtual
Ethernet connections (flows). You can initiate a loopback and trace the OAM
monitoring statistics according to the selected maintenance end point (MEP).
 To perform a loopback:
1. From the OAM Tests menu (Diagnostics > OAM Tests), select Loopback.
The Loopback menu appears as illustrated in Figure 6-30.
2. Define the test parameters according to Table 6-13.
RICi-16
Main Menu > Diagnostics > OAM Tests > Loopback
1. MD ID ... (1)
2. MA ID ... (1)
3. MEP ID [1-8191] ... (255)
>
Figure 6-30. Loopback Menu

Table 6-13. Loopback Menu
MD ID The ID of the maintanance domain 1–8
MA ID The ID of the MAC address
MEP ID ID of the maintenance endpoint, terminating the 1-8191

maintenance entity. If set to 0, no maintenance end
point (MEP) is assigned.
Default: 0
 To trace OAM monitoring statistics:

1. From the OAM Tests menu (Diagnostics > OAM Tests), select Link Trace.
The Link Trace menu appears as illustrated in Figure 6-31.
2. Define the test parameters according to Table 6-14.
3. Select Results to view the OAM monitoring statistics.
RICi-16
Main Menu > Diagnostics > OAM Tests > Link Trace
1. MD ID ... (1)
2. MA ID ... (1)
3. MEP ID [1-8191] ... (255)
4. Results []
>
Figure 6-31. Link Trace Menu
Table 6-14. Link Trace Menu
MD ID The ID of the maintanance domain 1–8
MA ID The ID of the MAC address
MEP ID ID of the maintenance endpoint, terminating the 1 – 65535

maintenance entity. If set to 0, no maintenance end
point (MEP) is assigned.
Default: 0

6.4 Troubleshooting
Use the chart shown in Table 6-15 to identify and remedy problems in unit
operation.
Table 6-15. Troubleshooting Chart
Fault Probable Cause Remedial Action
Power LED off No power supplied to unit. • Check the power source.
• Check whether the power cable is
connected and correctly wired.
Ethernet Link LED off • No Ethernet Link detected. • Check whether the cable is
• The rate or the duplex mode of connected and correctly wired.
the Ethernet ports on the • Check the switch and RICi-16’s
switch and RICi-16 do not Ethernet port configuration
match. (negotiation, rate, duplex mode).
• Use the event log to check events.
E1/T1 local or remote Sync No E1/T1 Link detected at the local • Check whether the cable is
Loss LED on or remote site. connected and correctly wired.
• Check the E1/T1 physical
connection (use loopbacks).
• Check the configuration of the
E1/T1 lines at local and remote
sites.
• Use the event log to check events.
No traffic flow between two Configuration or logical layer • Use the System Interface Status
units problems. screen for assistance. All active
ports that show Activation–Up,
should show Operation–Up.
• Use the log file to check events.
• Check RICi-16’s configuration and,
if necessary, other RICi-16
parameters.
Partial Traffic Flow Timing configuration is not • Check timing settings.

properly set.
6.5 Technical Support

Technical support for this product can be obtained from the local distributor from
whom it was purchased.
For further information, please contact the RAD distributor nearest you or one of
RAD's offices worldwide. This information can be found at www.rad.com. (Offices
– About RAD > Worldwide Offices; Distributors – Where to Buy > End Users).
6-32 Technical Support RICi-16 Ver. 2.5

Appendix B
Boot Sequence and
Downloading Software
RICi-16 allows you to download software. In order to do so, you have to connect
an ASCII terminal to RICi-16’s Control port.
Software is stored in the in two separate sectors on the flash memory, in the
boot sector and in the file system. The boot sector includes a boot program that
calls the rest of the program from the file system.
The file system can hold two compressed copies of the RICi-16 code. One copy is
called the operating file, and the other one is called the backup file. The
operating file is the default-executable RICi-16 code. The backup file is used
whenever the operating file is absent or corrupted.
B.1 Booting RICi-16

RICi-16 boots automatically. Once powered up, no further user intervention is
required, except when the user wants to access the file system to modify or
update the software or the RICi-16 configuration.
Accessing the Boot Manager

The Boot Manager menu is an option that allows the user to perform basic file
transfer operations. These operations are all optional.
³ To access the Boot Manager menu:
• Press <Enter> several times immediately after powering RICi-16 up.
The Boot Manager menu appears as illustrated in Figure B-1.
RICi-16 Ver. 2.5 Booting RICi-16 B-1

Appendix B Boot Sequence and Downloading Software RICi-16 Installation and Operation Manual
RICi-XN Boot Version 1.10 (Dec 31 2007)

Boot manager version 10.07 (Dec 31 2007)
0 - Exit boot-manager
1 - Dir
2 - Set active software copy
3 - Delete software Copy
4 – Download boot manager or an application by XMODEM
5 - Format flash
6 - Show basic hardware information
7 - Reset board
8 - System configuration.
9 – Download boot manager or an application by TFTP
Select:
Figure B-1. Typical Boot Manager Menu

From the Boot Manager menu, you can:
• List all files stored in the flash memory
• Exchange the operating and backup files
• Delete the operating file; the backup file becomes the operating file
• Download a new operating file via XMODEM; the previous operating file is
saved as the backup file
• Delete all software and configuration files
• Display basic hardware information such as RAM, ROM size etc.
• Reset RICi-16
• Configure the IP address, the IP mask and the default gateway for the
consecutively downloading via TFTP.
If you choose to exchange or delete a file, you are prompted for confirmation.
B.2 Transferring the Software and Configuration

Files
New software releases are distributed as separate files, which are downloaded to
RICi-16 using the XMODEM protocol or TFTP from the Boot Manager menu.
Alternatively, you can download a new software release via TFTP, when the
RICi-16 management software is already running (Main menu > Utilities > File
Transfer).
The TFTP protocol can also be used for uploading configuration files that contain
the RICi-16 database to the management station. When RICi-16 is running,
administrators can use this capability to distribute verified configuration files to
all other units that use the similar configuration.
B-2 Transferring the Software and Configuration Files RICi-16 Ver. 2.5
RICi-16 Installation and Operation Manual Appendix B Boot Sequence and Downloading Software
Downloading Application Files via XMODEM

Use the XMODEM protocol to download applications from the Boot Manager
menu.
³ To download application file via XMODEM:
1. Configure your ASCII terminal or terminal emulation utility running on your PC
to a data rate of 115.2 kbps.
2. Enter the Boot Manager menu.
The Boot Manager menu appears as illustrated in Figure B-1.
3. From the Boot Manager menu, select Download Files or an Application by
XMODEM.
RICi-16 displays the following message:
Select Copy number for download (0)
4. Enter the number associated with the backup partition, 0 or 1.
RICi-16 responds with the following string:
Please start the XMODEM download.
5. Start sending the application file to RICi-16 using the XMODEM utility of your
terminal application.
Once completed, RICi-16 saves the new release as an active partition, the
previously active partition becomes the backup partition and the boot
sequence continues normally.
In case downloading fails, the partially downloaded file is erased and only the
active software file remains in the flash memory.
Downloading Application Files via TFTP

³ To download application file via TFTP
1. From the Boot Manager menu, select System Configuration.
2. Configure the IIP address, the IP mask and the default gateway. These
parameters are only valid for the TFTP file transfer via the Boot Manager.
3. Start a TFTP application and configure the TFTP communication parameters as
follows:
Connection timeout – more than 30 seconds to prevent an automatic
disconnection during the backup partition deletion (about 25 seconds)
Block size – 512 bytes
UDP port – 69.
4. Select a local software release file to download.
5. Enter the TFTP server IP address.
6. Start downloading.
RICi-16 erases the backup partition. Once completed, RICi-16 saves the
new release as an active partition. The previously active partition
becomes the backup partition.
RICi-16 Ver. 2.5 Transferring the Software and Configuration Files B-3
Appendix B Boot Sequence and Downloading Software RICi-16 Installation and Operation Manual
B-4 Transferring the Software and Configuration Files RICi-16 Ver. 2.5
Appendix C
Operation, Administration
and Maintenance (OAM)
This appendix describes the Ethernet OAM functionality of RICi-16.
C.1 Introduction
Currently RICi-16 support pre-standard implementation of Ethernet OAM based
on Y.1731 and standard implementation based on Y.1731 and IEEE P802.1ag. The
pre-standard implementation is only used for performance measurements when
using two RAD units working opposite each other or when working against a RAD
that runs an older version of RAD’s Ethernet OAM software. This appendix
describes the pre-standard implementation. The standard implementation can be
found in the standards Y.1731 and IEEE P802.1ag documents.
RICi-16 has the following capabilities for providing operation, administration, and
maintenance (OAM) in the packet-switched networks:
• Continuity check
• Non-intrusive loopback which used to detect loss of bidirectional continuity
• Performance measurements (per service).
Table C-1 lists the Ethernet OAM-related terms used in the appendix.
Table C-1. Ethernet OAM Terminology
Term Description
UNI User Network Interface. The physical demarcation point

between the responsibility of the Service Provider and the
responsibility of the Subscriber
UNI_C Customer side of a UNI link
UNI_N Network side of a UNI link
Service frame An Ethernet frame transmitted across the UNI toward the
Service Provider or an Ethernet frame transmitted across the
UNI toward the Subscriber.
Flow Ethernet Virtual Connection : An association of two or more

UNIs that limits the exchange of Service Frames to UNIs in the
Ethernet Virtual Connection
Point-to-point Flow Flow connecting exactly two UNIs
RICi-16 Ver. 2.5 Introduction C-1

Appendix C Operation, Administration and Maintenance (OAM) Installation and Operation Manual
Term Description
Multipoint-to-Multipoint Flow connecting two or more UNIs

Flow
Service Instance / Class A set of Service Frames that have a commitment from the
of service (CoS) Service Provider to receive a particular level of performance
Service Instance Service Frame delivery performance is specified for all Service
Identifier (CoS ID) Frames transported within a flow with a particular Class of
Service instance. The Class of Service instance is identified by a
Class of Service Identifier associated with each Service Frame
(Class of service can be identified by more than one
parameter/frame attribute)
MEP Proactive OAM reference point which is capable to initiate and

terminate proactive OAM frames. MEP is also capable to initiate
and react to diagnostics OAM frames.
MIP A provisioned OAM reference point which is capable to respond

to diagnostics OAM frames initiated by the MEP.
MEP Service Instance The receiver of OAM frames in each Service Instance
Source
MEP Service Instance The transmitter of OAM frames in each Service Instance
Destination
C.2 Reference Architecture

Figure C-1 illustrates two OAM flows:
• OAM flow originating from the CPE
The CPE-to-CPE OAM flow is transferred transparently by RICi-16 and treated
as data.
• OAM flow originating from the RICi-16 devices.
The RICi-16 OAM flow runs on a data flow on the same VLAN.
The RICi-16 units terminate the OAM flow and can be referred as a
Maintenance Entity (ME). Each device supports up to 8 such MEs. In this case,
the RICi-16 units act as MEPs (Maintenance End-Points) and not as a MIP
(Maintenance Intermediate Points) and all measurements are performed on
the UNI_N to UNI_N segment.
C-2 Reference Architecture RICi-16 Ver. 2.5

Installation and Operation Manual Appendix C Operation, Administration and Maintenance (OAM)
Figure C-1. OAM Architecture
Handling of OAM Levels
UNI_C to UNI_N Direction

In the UNI_C to UNI_N direction RICi-16 blocks all OAM messages with OAM level
greater than 2. Messages with other OAM levels are passed transparently.
Network Ingress to UNI_N Direction

All OAM messages coming from the network ingress with the ETX MAC address or
with the special OAM multicast address are sent to the CPU. All other OAM
messages are passed transparently to the user ports as per the respective flow
definition.
C.3 OAM Entities

This section describes the OAM entities hierarchy. Figure C-2 illustrates the
relationship between UNI, flow and Service Instance (COS ID), when one or more
service instances belong to one flow and one or more flow belong to a UNI. From
the OAM perspective, the continuity messages and defects are activated per flow,
and the PM is activated per service instance.
Note A flow can belong only to one UNI in the same RICi-16.
Figure C-2. UNI, Flow and Service Instance (COS ID)
Figure C-3, Figure C-4 and Figure C-5 illustrate different combinations of UNIs,
flows and service instances. Each UNI contains at least one flow, which contain at
least one service instance.
• In the one flow per UNI case (Figure C-3), the PM and CC are transmitted
once.
RICi-16 Ver. 2.5 OAM Entities C-3

Figure C-3. One Flow per UNI
• In case of multiple flows per UNI (Figure C-4), PM and CC are transmitted
three times.
Figure C-4. Multiple Flows per UNI
• In case of one flow and multiple CoS (Service Instances) per UNI (Figure C-5),
the PM is transmitted three times and the CC – once.
Figure C-5. One Flow and Multiple CoS (Service Instances) per UNI
C.4 OAM Flows

Figure C-6 illustrates a typical OAM traffic flow. The OAM message is transmitted
from the source MEP 1 to the destination MEP 2 and the reply is transmitted back
The source is also a destination for messages from the other direction.
The OAM interval is one second, so each NTU transmits one request and one
reply and receive one request and one reply. Total of four messages are
transmitted per second per service instance.
OAM Message
Request
MEP 1 MEP 2
OAM Message
Reply
Source Destination
Figure C-6. OAM Flow
C-4 OAM Flows RICi-16 Ver. 2.5

OAM Messages Addressing

The OAM defines two modes of addressing, unicast and multicast. Unicast
addressing is used for point-to-point connections, while multicast addressing is
used in cases where the MAC address of the destination MEP is not known.
OAM Message Association

On the receiver side the OAM frame is associated with a flow and a service.
Flow Association
When an OAM frame is associated with a flow, the following steps are performed:
• Request message reception
When a request message is received, the VLAN is extracted to find the Flow
ID. The Flow ID found at the receiver is compared against the Flow ID in the
frame. If the IDs are equal, further service association is made. If it is not
found, the “Flow ID no match” notification is returned in the reply message.
• Reply message reception
When a reply message is received, the VLAN is extracted to find the Flow ID.
The Flow ID found at the receiver is compared against the Flow ID in the
frame. If the IDs are equal, further service association is made. If it is not
found, the frame is discarded and connectivity alarm is issued.
Service Association
When an OAM frame is associated with a service, the following steps are
performed:
• Request message reception
The class of service characteristics are extracted from the frame and must be
matched to an entry in the flows <-> services table at the receiver. If they are
matched, the frame is processed. If not, the service ID is returned with the
“Not Found” notification.
• Reply message reception
The class of service characteristics are extracted from the frame and must be
matched to an entry in the flow <-> services table at the receiver. If they are
matched, the frame is processed. If not, the frame is discarded.
Ethernet Loopback (ETH-LB)

The ETH-LB can be used to verify connectivity. The ETH-LB is performed by
sending a request ETH-LB message to the remote unit and expecting an ETH-LB
reply message back to verify connectivity. When the insertion rate of ETH-LB
messages is much slower compared to data rate between the flow points, ETH-LB
is suitable to perform in-service connectivity verification and to measure round
trip delays.
The message is initiated by the local device and runs periodically making it
suitable for fault detection.
RICi-16 Ver. 2.5 OAM Flows C-5

Unicast ETH-LB request message is sent from a MEP to a specific MEP (remote
device). The DA of the request message is a unicast MAC address of destination
device. Upon receipt of the request message, the MEP responds with unicast ETH-
LB reply message. The DA of the reply message is a unicast MAC address of
requesting device, learned from request message.
Continuity Check (ETH-CC)

Ethernet Continuity Check (ETH-CC) can be used to detect continuity failures
across flows between a given pair of edge service point on a flow. Continuity
failures are caused by:
• Major failures (link failure, device failure, network path failure etc)
• Minor failures (software failure, memory corruption, incorrect configuration
etc).
The ETH-CC signal is generated by one MEP. Upon receipt of the first ETH-CC
signal from a sending MEP, the receiving MEP detects continuity with sending MEP
and expects to receive further periodic ETH-CC signals. Once the receiving MEP
stops receiving periodic ETH-CC signals from sending MEP, it declares continuity
failure. The MEP that detects the continuity failure notifies the operator by
sending an alarm or a trap.
OAM Procedures
This section discusses the continuity check (CC) and the performance
measurement (PM) procedures.
Continuity Check Procedure

The loopback message and the ETH-CC messages are used for continuity check. In
case the services are defined and PM collection is enabled, they are also used to
carry PM messages. If PM collection is disabled, the messages are used for
continuity check only.
If the RX CC mode of the receiver is configured to CC-based, the continuity
detection is based on ETH-CC. If the mode is set to LB-based, the continuity
detection is based on ETH-LB. If the mode is disabled, the continuity detection is
not performed.
ETH-LB Method
The ETH-LB method includes the following elements:
• Unicast ETH-LB transmission
Unicast ETH-LB request message is transmitted by a MEP (RICi-16) every
1 second. The transmitted Transaction Identifier is retained for at least
5 seconds after the unicast ETH-LB signal is transmitted. The Transaction
Identifier must be changed for every unicast ETH-LB message, and no
Transaction Identifier from the same MEP is allowed to be repeated within
1 minute.
• Unicast ETH-LB reception and reply transmission

Whenever a valid unicast ETH-LB request message is received by MEP

(RICi-16), a unicast ETH-LB reply message is generated and transmitted to the
requesting MEP. Every field in the unicast ETH-LB request message is copied
to the unicast ETH-LB reply message with the following exceptions:
The source and destination MAC addresses are swapped.
The OpCode field is vendor-specific oxFE.
The Flow and MEP ID are processed as follows: if the Flow/MEP ID do not
exist in the device, it changes them to No Match” otherwise they are left
intact.
• Unicast ETH-LB reply receipt
When a unicast ETH-LB reply message is received by a MEP (RICi-16)
diagnostic flow termination function, it examines the TLVs returned in the
unicast ETH-LB reply message. The signal is declared invalid if the TLVs do not
match those sent in the corresponding unicast ETH-LB request signal,
including MEP ID and Flow ID.
• Continuity declarations
Loss of Continuity and Connectivity Mismatch states are declared by the
ETH-LB mechanism.
Loss of continuity declaration
After the source device sends an ETH-LB message a timer is set with a
3.52 second timeout. If the destination device does send reply within the
timeout, the source enters the loss of continuity state. Upon reply from
the destination, the source resets the timer to 23.5 seconds. Regarding
the continuity check message, the source checks only the Flow ID with
the MEP ID. When the source enters the loss of continuity state, it adds
24 to Unavailable Seconds counter. The 23.5 second period is calculated
as a sliding window.
Loss of continuity state is cleared after 3.52 seconds with at least
21 reply messages from the destination. In this case the Unavailable
Seconds counter decreased by 24.
Connectivity mismatch declaration
If the source Flow ID is not equal to the destination Flow ID as recorded
in the reply message for 10 consecutive times, the source enters in to
misconnection state.
Misconnection state is cleared after 10 consecutive reply messages with
the correct flow name from the destination.
The Unavailable counter is maintained by the service according to the
number of PM messages that did not receive replies. If a mismatch
notification is received to the LB request, the frame is dropped and reply
message is not sent. This is why the service becomes unavailable (no
reply) in case of mismatch and the unavailable counter is raised.
RICi-16 Ver. 2.5 OAM Flows C-7

ETH-CC Method
The ETH-CC method includes the following elements:
• ETH-CC transmission
Unicast ETH-CC request message is transmitted by a MEP (RICi-16) every
1 second (depending on the configuration). The transmitted Transaction
Identifier is retained for at least 5 seconds after the unicast ETH-CC signal is
transmitted. The Transaction Identifier must be changed for every Unicast
ETH-CC message, and no Transaction Identifier from the same MEP is allowed
to be repeated within 1 minute.
• Unicast ETH-CC reply receipt
When a unicast ETH-CC message is received by a MEP (RICi-16) diagnostic
flow termination function, it examines the TLVs returned in the unicast
ETH-CC message, and declares the signal invalid if the TLVs do not match
those sent in the corresponding exiting MEP ID and Flow ID.
• Continuity declarations
Loss of Continuity and Connectivity Mismatch states are declared by the
ETH-CC mechanism.
Loss of continuity declaration
When the MEP receives the ETH-CC message a timer is set with a
3.5 seconds timeout. If the source does send another message during
this period, the destination enters the loss of continuity state. Upon
receipt of the ETH-CC message, the destination resets the timer to
3.5 seconds. Regarding the continuity check message, the destination
check the Flow ID and the MEP ID. When the destination enters the loss
of continuity state, it adds 4 to the Unavailable Seconds counter. The
3.5 second period is calculated as a sliding window.
Loss of continuity state is cleared after 3.5 seconds with at least
2 messages from the source. In this case the Unavailable Seconds counter
is decreased by 4.
Connectivity mismatch declaration
If the source Flow ID is not equal to the destination Flow ID for
10 consecutive times, the destination enters in to misconnection state.
Misconnection state is cleared after 10 consecutive reply messages with
the correct flow name from the source.
The Unavailable counter is maintained by the service according to the
number of PM messages that did not receive replies. If a mismatch
notification is received to the LB request, the frame is dropped and reply
message is not sent. This is why the service becomes unavailable (no
reply) in case of mismatch and the unavailable counter is raised.

Performance Measurement
RICi-16 measures performance during 15-minute intervals. It also stores
performance history data of nthe last 24 hours (96 intervals). Table C-2 lists the
PM counters supported by RICi-16.
Table C-2. PM Counters
Frames Above Delay Obj. Number of frames that exceeded delay objective
Frames Below Delay Obj. Number of frames below or equal delay objective
Frames Above DV Obj. Number of frames that exceeded delay variation objective
Frames Below DV Obj. Number of frames below or equal delay variation objective
Frames Transmitted Total number of OAM frames transmitted in the current interval
Frames Lost Number of frames lost in the current interval
Unavailable Seconds Number of seconds during which the service was unavailable in the current
interval
Elapsed Time Time (in seconds) elapsed from beginning of the interval 0–900
Min. RT Delay Minimum round trip delay (in mseconds) calculated in the interval (or up to
elapsed time in current interval)
Avg. RT Delay Average round trip delay (in mseconds) calculated in the interval (or up to
Max. RT Delay Maximum round trip delay (in mseconds) calculated in the interval (or up
to elapsed time in current interval)
Avg. DV Average delay variation (in mseconds) calculated in the interval (or up to
Max. DV Maximum delay variation (in mseconds) calculated in the interval (or up to
OAM Transmitted Frames Total number of OAM frames transmitted since the service was enabled
Counter
OAM Frames Loss Counter Total number of OAM frames lost since the service was enabled
OAM Frame Loss Ratio Total number of lost OAM frames divided by total number of transmitted
OAM frames since the service was enabled
Elapsed Time Time (in seconds) elapsed since the service was enabled
Unavailable Seconds Total number of unavailable seconds since the service was enabled
Unavailability Ratio Total number of unavailable seconds divided by elapsed time
RICi-16 Ver. 2.5 RMON Statistics C-9

C.5 RMON Statistics

In addition to the regular statistics collection, RICi-16 supports proactive SLA
measurements per RICi-16 port, as per RMON-based RFC 2819. The device sends
reports when one of the available counters (physical layer or OAM) rise above or
drop 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 be written to the event log.
The following counters can be monitored:
• Dropped Frames
• Undersize Frames
• Oversize Frames
• Fragmented Frames
• Jabbers
• Frame Loss Ratio
• Frames Above Delay
• Frames Above Delay Variation
• Unavailability Ratio.
C-10 RMON Statistics RICi-16 Ver. 2.5

Index
E1/T1 port, 2-3

—A— terminal, 2-4
AC power, connecting, 2-5 Connectivity tests, 6-21
Aging, 1-9 Connectors, 2-2
Aging Process Control interface
VLAN–Aware bridge, 1-11 pinouts, A-2
VLAN–Unaware bridge, 1-13 Control Port, 3-5, See Terminal
Application, 1-2 specifications, 1-24
Ethernet cellular backhauling, 5-1, 5-15
Ethernet services, 5-8 —D—
Application-level status
displaying, 6-9 Date and time, 4-19
Date and Time
configuring, 4-19
—B— DC power, connecting, 2-5
BERT, 6-24, 6-26 Default settings, 3-3
Bit Error Rate Test, 6-24, 6-26 Device information, 4-1
Boot Manager, B-1 Diagnostics, 6-1
Bridge, 1-3, 1-9 connectivity tests, 6-21
Ethernet access, 1-9 loopback, E1/T1, 6-23
specifications, 1-24 loopback, T3, 6-24
VLAN Stripping mode, 1-13 ping, 6-21
VLAN–Aware, 1-9 trace route, 6-22
Bridge, internal VCT, 6-22
configuring, 4-42 Dimensions, 1-25
—C— —E—
Cables, 2-2 E1 interface, 1-23
Choosing options connecting the port, 2-3
ConfiguRAD, 3-9 default settings, 3-3
ConfiguRAD, 3-8 pinouts, A-2
configuring access, 4-11 E1 Interface
Configuration configuring, 4-31
ASCII terminal, 3-5 E1/T1 status, 6-7
manager list, 4-15 Environmental specifications, 1-26
Configuring Equipment
defining flows, 4-58 cables, 2-2
device information, 4-1 connectors, 2-2
E1 ports, 4-31 hand tools, 2-2
Ethernet port, 4-26 power cable, 2-2
fault propagation, 4-25 Ethernet. See Ethernet
Flows, 4-57 access, 1-9
IP host parameters, 4-2 Ethernet interface
L2CP Filtering Profile, 4-30 default settings, 3-3
MAC Access Control, 4-28 pinouts, A-1
ports, 4-26 statistics, 6-13
QoS priorities, 4-48 Ethernet Interface, 1-2, 1-8
T1 ports, 4-33, 4-35 Ethernet Port, 4-26
terminal parameters, 4-65 Ethernet status, 6-5
user priorities, 4-48
Connecting
AC power, 2-5
DC power, 2-5
I-1
Index Installation and Operation Manual
terminal, 3-6
—F— Web browser, 3-9
Loopback
Fault Propagation, 4-25
E1/T1, 6-23
File downloading, B-2
T3, 6-24
File transfer, 4-66, B-2
Flow, 1-4, 4-57
Flows, 4-57 —M—
defining, 4-58 MAC Access Control, 4-28
Forwarding, 1-9 MAC port protection, 4-26
Forwarding Process MAC table, 4-43
VLAN–Aware bridge, 1-11 Management, 1-6, 1-21
VLAN–Unaware bridge, 1-13 access method, 4-11
Front panel functions, 1-6
LEDs, 3-2 SNMPv3, 4-4
via terminal port, 3-5
—G— via Web browser, 3-8
Menu tree, 3-10
GFP, 1-2
Menus
RX traffic, 1-16
Management, 4-5
Tx traffic, 1-14
navigating, 3-9
GFP and VCG port status, 6-8
Notification Entries, 4-7
reference, 3-10
—H— SNMP Engine ID, 4-4
Host, 4-2 SNMPv1/v3 Mapping, 4-11
Host tagging SNMPv3 Settings, 4-5
tagged, 4-3 SNMPv3 Users, 4-6
untagged, 4-3 Target Address, 4-10
Target Params, 4-9
—I— Trap, 4-8
Virtual Cable Test, 6-23
Indicators, 1-25 Monitoring, 6-1
Ingress, 1-9 connected managers status, 6-3
Ingress process Ethernet statistics, 6-13
VLAN–Aware bridge, 1-10 log file, 6-19
VLAN–Unaware bridge, 1-12 MAC table, 6-9
Installation, 2-1 port status, 6-5, 6-7
Interfaces ports status, 6-8
pinouts statistics, 6-13
control, A-2 Status, 6-1
E1, A-2 system messages, 6-19
Ethernet, A-1 Monitoring statistics, 1-24
statistics, 6-13
Internal bridge
configuring, 4-42 —N—
Inventory, 4-63 Network Application Mode
configuring, 4-21
—L— Network interface
default settings, 3-3
L2CP Filtering Profile, 4-30 Network Operation Mode
LCAS, 1-2 configuring, 4-21
Learning, 1-9
Learning Process
VLAN–Aware bridge, 1-11 —O—
VLAN–Unaware bridge, 1-12 OAM, 4-61
LEDs, 3-2 Operation, 3-1
License pack
viewing details, 4-64 —P—
Log file, 6-19
Package contents, 2-2
Logical layer
Password, 4-65
Default configuration, 4-38
default, 3-6
Logical ports
Physical Ports, 4-26
Configuration, 4-38
Physical specifications, 1-25
Logical-level status
Physical-level status
displaying, 6-8
displaying, 6-5
Login
Ping, 6-21
I-2 RICi-16 Ver. 2.5

Installation and Operation Manual Index
Pinouts, A-1 System messages, 6-19

Pop-ups
blocking, 3-8 —T—
Port
T1 interface, 1-23
protection, 4-36
connecting the port, 2-3
Ports
E1/T1 port, 2-3
pinouts, A-2
Power
T1 Interface
installing hot-swappable unit, 2-6
configuring, 4-33, 4-35
Power cable, 2-2
T3 interface, 1-23
Power supply
AC, 2-5
T3 status, 6-7
DC, 2-5
Tables
Powering down, 3-19
navigating, 3-7
Powering up, 3-1
technical specifications
Protection status, 6-3
power, 1-25
Technical Specifications, 1-24
—Q— Telnet, 4-11
Quality of service, 4-48 Terminal, 3-5
Quality of Service, 1-19 baud rate, 4-65
configuring, 3-5
—R— connecting, 2-4
login, 3-6
Resetting
parameters, 4-65
device, 4-68
TFTP, 4-67, B-2
to factory defaults, 4-68
Trace route, 6-22
RS-232 port, 3-5
Transmission, 1-9
—S— VLAN–Aware bridge, 1-12
Screens VLAN–Unaware bridge, 1-13
reset device, 4-68 Troubleshooting, 6-1
Security, 1-21
Security Protocols, 1-6 —U—
Setting up, 2-1
User interface
Site requirements, 2-1
SNMP
User name, 4-65
configuring access, 4-11
Utilities
SNMPv3, 4-4
File transfer, 4-67
Software
reset device, 4-68
files, B-1
in flash memory, B-1
new releases, 4-66 —V—
updates, 4-66, B-2 VCAS, 1-2
versions, 4-66 VCT, 6-22
Software license Virtual cable test, 6-22
viewing details, 4-64 VLAN–Aware mode, 1-9
Source clock, 4-17 VLAN–Unaware mode, 1-12
Specifications
bridge, 1-24 —W—
control port, 1-24
WAN Interface, 1-8
dimensions, 1-25
Web browser, 3-8
environmental, 1-25
login, 3-9
Statistics
E1/T1, 6-13
T3, 6-15 —X—
Statistics, 6-13 XMODEM, B-3
Ethernet, 6-13
RICi-16 Ver. 2.5 I-3

Index Installation and Operation Manual
I-4 RICi-16 Ver. 2.5

Supplement
AC/DC Adapter
(AD) Plug
for DC Power Supply Connection
Note Ignore this supplement if the unit is AC-powered.
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 or
90-degree AC/DC Adapter (AD) plug for attaching Figure 1. Straight AD Plug
to your DC power supply cable is supplied with
your RAD product (see Figure 1 and Figure 2).
Connect the wires of your DC power supply cable
to the AD plug, according to the voltage polarity
and assembly instructions provided on page 2.
Figure 2. 90-Degree AD Plug
Caution
Prepare all connections to the AD plug before inserting it into the unit’s power
connector.
Publication No. SUP-930-07/08 The Access Company

AC/DC Adapter (AD) Plug
³ 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 3).
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
Figure 3. AD Plug Details
plug and tighten the cover screw.
6. Connect the assembled power supply
cable to the unit.
Note: You have to flip over the
non-90-degree AD plug type by
180 degrees to insert it into the unit.
After inserting it, verify that the blue
(negative) wire is connected to the
POWER and the brown (positive) wire is
connected to the RETURN.
• Reversing the wire voltage polarity will not cause damage to the unit, but the
internal protection fuse will not function.
Warning • Always connect a ground wire to the AD plug’s chassis (frame) ground
terminal. Connecting the unit without a protective ground, or interrupting the
grounding (for example, by using an extension power cord without a
grounding conductor) can damage the unit or the equipment connected to it!
• The AD adapter is not intended for field wiring.
2
Supplement
Terminal Block
Connector
for DC Power Supply Connection
Note Ignore this supplement if the unit is AC-powered.
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 1. All
0
are functionally identical.

Supplied with such units is a kit
including a mating Terminal Block (TB)
type connector plug for attaching to
your power supply cable.
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. Figure 1. TB DC Input Connector Types
Appearing on Unit Panels
Caution
Prepare all connections to the TB plug before inserting it into the unit’s VDC-IN
connector.
Publication No. SUP-220-06/08 The Access Company

Terminal Block Connector
³ To prepare and connect the power

supply cable with the TB Plug:
Note: Refer to Figure 2 for assistance.
1
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 3. (If a terminal is not already
2
open, loosen its screw.) Afterwards,

tighten the three terminal screws to
close them.
Figure 2. TB Plug Assembly
3. Pull a nylon cable tie (supplied) around
the power supply cable to secure it
firmly to the TB plug grip, passing the
tie through the holes on the grip.
4. Isolate the exposed terminal
screws/wire leads using a plastic
sleeve or insulating tape to avoid a
short-circuit.
5. Connect the assembled power supply
cable to the unit by inserting the
TB plug into the unit’s VDC-IN
connector until it snaps into place. Figure 3. Mapping of the Power Supply Wire
Leads to the TB Plug Terminals
• Reversing the wire voltage polarity can cause damage to the unit!
• Always connect a ground wire to the TB plug’s chassis (frame) ground
Warning terminal. Connecting the unit without a protective ground, or interruption of
the grounding (for example, by using an extension power cord without a
grounding conductor) can cause harm to the unit or to the equipment
connected to it!
2
Note: Certain TB plugs are equipped with

captive screws for securing the assembled
cable’s TB plug to the unit’s VDC-IN
connector (C and E types only). To secure
the plug, tighten the two screws on the
plug into the corresponding holes on the
sides of the input connector as shown in
Figure 4.
3
Figure 4. 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 4).
4
2. If the unit’s VDC-IN connector is type B, lift the locking latch (see Figure 1).
5
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.
3
4
24 Raoul Wallenberg Street, Tel Aviv 69719, Israel
Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250
E-mail: erika_y@rad.com, Web site: http://www.rad.com
Customer Response Form

RAD Data Communications would like your help in improving its product documentation.
Please complete and return this form by mail or by fax or send us an e-mail with your
comments.
Thank you for your assistance!
Manual Name: RICi-16 Version 2.5
Publication Number: 506-200-05/14
Please grade the manual according to the following factors:
Excellent Good Fair Poor Very Poor
Installation instructions     
Operating instructions     
Manual organization     
Illustrations     
The manual as a whole     
What did you like about the manual?

Error Report
Type of error(s) or  Incompatibility with product
problem(s):  Difficulty in understanding text
 Regulatory information (Safety, Compliance, Warnings, etc.)
 Difficulty in finding needed information
 Missing information
 Illogical flow of information
 Style (spelling, grammar, references, etc.)
 Appearance
 Other
Please list the exact page numbers with the error(s), detail the errors you found (information missing,
unclear or inadequately explained, etc.) and attach the page to your fax, if necessary.
Please add any comments or suggestions you may have.
You are:  Distributor

 End user
 VAR
 Other
Who is your distributor?
Your name and company:
Job title:
Address:
Direct telephone number and extension:
Fax number:
E-mail:
Publication No. 506-200-05/14
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North America Headquarters

900 Corporate Drive
Mahwah, NJ 07430, USA
Tel. 201-5291100
Toll free 1-800-4447234
Fax 201-5295777
E-mail market@radusa.com
www.rad.com

RICi-16E1T1 2.5 MN

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RICi-16E1T1 2.5 MN

Загружено:

Авторское право:

Доступные форматы

OPERATION MANUAL

The Access Company

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

© 2006 –2009 RAD Data Communications Ltd. Publication No. 506-200-05/14

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Achtung Das vorliegende Gerät fällt unter die Funkstörgrenzwertklasse A. In Wohngebieten

Afin de faciliter la réutilisation, le recyclage ainsi que d'autres formes de

Instructions générales de sécurité

Mise à la terre de protection : la cosse ou la borne marquée devrait être connectée

Manipuler des produits sous tension

Règles générales de sécurité

Assurez-vous que l'installation électrique est conforme à la réglementation locale.

Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 69719, Israel

declares that the product:

Product Name: RICi-16

Product Options: All

conforms to the following standard(s) or other normative

EMC EN 55022:2010 Information technology equipment; Radio disturbance

EN 55024:2010 Information technology equipment; Immunity characteristics;

EN 61000-3-2:2006 Electromagnetic compatibility (EMC); Section 3-2: Limits for

EN 61000-3-3:2008 Electromagnetic compatibility (EMC); Section 3-3: Limits -

Safety EN 60950-1:2006 + Information technology equipment; Safety – Part 1:

European Contact: RAD Data Communications GmbH

Address A coded representation of the origin or destination of data.

Agent In SNMP, this refers to the managed system.

Analog A continuous wave or signal (such as human voice).

ANSI American National Standards Institute.

Attenuation Signal power loss through equipment, lines or other transmission

Balanced A transmission line in which voltages on the two conductors are

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

Bus A transmission path or channel. A bus is typically an electrical

Byte A group of bits (normally 8 bits in length).

Carrier A continuous signal at a fixed frequency that is capable of being

Channel A path for electrical transmission between two or more points.

Clock A term for the source(s) of timing signals used in synchronous

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

Data Information represented in digital form, including voice, text,

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

Digital The binary (“1” or “0”) output of a computer or terminal. In data

E1 Line A 2.048 Mbps line, common in Europe, that supports thirty-two 64

E3 The European standard for high speed digital transmission,

Encapsulation Encapsulating data is a technique used by layered protocols in

Flow Control A congestion control mechanism that results in an ATM system

Frame A logical grouping of information sent as a link-layer unit over a

Full Duplex A circuit or device permitting transmission in two directions

G.703 An ITU standard for the physical and electrical characteristics of

Gateway Gateways are points of entrance and exit from a communications

Half Duplex A circuit or device capable of transmitting in two directions, but

Impedance The combined effect of resistance, inductance and capacitance on

Interface A shared boundary, defined by common physical interconnection

IP Address Also known as an Internet address. A unique string of numbers

Laser A device that transmits an extremely narrow and coherent beam

Manager An application that receives Simple Network Management Protocol

Multiplexer At one end of a communications link, a device that combines