Manual-RIC-LC-RAD
Manual-RIC-LC-RAD
INSTALLATION AND
RIC-LC
Ethernet Converter for Bonded PDH Circuits
Version 2.0
RIC-LC
Ethernet Converter for Bonded PDH Circuits
Version 2.0
Installation and Operation Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD").
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the RIC-LC 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 RIC-LC 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
RIC-LC. 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 RIC-LC, based
on or derived in any way from the RIC-LC. Your undertaking in this paragraph shall survive the
termination of this Agreement.
This Agreement is effective upon your opening of the RIC-LC 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 RIC-LC and all copies and
portions thereof.
For further information contact RAD at the address below or contact your local distributor.
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the RIC-LC 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 RIC-LC, and in no event shall
RAD's liability exceed the purchase price of the RIC-LC.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to RIC-LC and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the RIC-LC 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 RIC-LC shall not
exceed the sum paid to RAD for the purchase of the RIC-LC. 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.
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.
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.
Connecting AC Mains
Make sure that the electrical installation complies with local codes.
Always connect the AC plug to a wall socket with a protective ground.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Always connect the power cord first to the equipment and then to the wall socket. If a power
switch is provided in the equipment, set it to the OFF position. If the power cord cannot be
readily disconnected in case of emergency, make sure that a readily accessible circuit breaker or
emergency switch is installed in the building installation.
In cases when the power distribution system is IT type, the switch must disconnect both poles
simultaneously.
Connecting DC Power
Unless otherwise specified in the manual, the DC input to the equipment is floating in reference
to the ground. Any single pole can be externally grounded.
Due to the high current capability of DC power systems, care should be taken when connecting
the DC supply to avoid short-circuits and fire hazards.
Make sure that the DC power supply is electrically isolated from any AC source and that the
installation complies with the local codes.
The maximum permissible current capability of the branch distribution circuit that supplies power
to the product is 16A (20A for USA and Canada). The circuit breaker in the building installation
should have high breaking capacity and must operate at short-circuit current exceeding 35A (40A
for USA and Canada).
Before connecting the DC supply wires, ensure that power is removed from the DC circuit. Locate
the circuit breaker of the panel board that services the equipment and switch it to the OFF
position. When connecting the DC supply wires, first connect the ground wire to the
corresponding terminal, then the positive pole and last the negative pole. Switch the circuit
breaker back to the ON position.
A readily accessible disconnect device that is suitably rated and approved should be incorporated
in the building installation.
If the DC power supply is floating, the switch must disconnect both poles simultaneously.
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.
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
Certains produits peuvent être équipés d'une diode laser. Dans de tels cas,
Français
une étiquette indiquant la classe laser ainsi que d'autres avertissements, le
cas échéant, sera jointe près du transmetteur optique. Le symbole
d'avertissement laser peut aussi être joint.
Avertissement
Veuillez observer les précautions suivantes :
• Avant la mise en marche de l'équipement, assurez-vous que le câble de
fibre optique est intact et qu'il est connecté au transmetteur.
• Ne tentez pas d'ajuster le courant de la commande laser.
• N'utilisez pas des câbles ou connecteurs de fibre optique cassés ou sans
terminaison et n'observez pas directement un rayon laser.
• L'usage de périphériques optiques avec l'équipement augmentera le
risque pour les yeux.
• L'usage de contrôles, ajustages ou procédures autres que celles
spécifiées ici pourrait résulter en une dangereuse exposition aux
radiations.
ATTENTION : Le rayon laser peut être invisible !
Les utilisateurs pourront, dans certains cas, insérer leurs propres émetteurs-récepteurs Laser SFP
dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas être tenue responsable de
tout dommage pouvant résulter de l'utilisation d'émetteurs-récepteurs non conformes. Plus
particulièrement, les utilisateurs sont avertis de n'utiliser que des produits approuvés par
l'agence et conformes à la réglementation locale de sécurité laser pour les produits laser de
classe 1.
Respectez toujours les précautions standards de sécurité durant l'installation, l'opération et la
maintenance de ce produit. Seul le personnel de service qualifié et autorisé devrait effectuer
l'ajustage, la maintenance ou les réparations de ce produit. Aucune opération d'installation,
d'ajustage, de maintenance ou de réparation ne devrait être effectuée par l'opérateur ou
l'utilisateur.
Connexion d'alimentation CC
Sauf s'il en est autrement spécifié dans le manuel, l'entrée CC de l'équipement est flottante par
rapport à la mise à la terre. Tout pôle doit être mis à la terre en externe.
A cause de la capacité de courant des systèmes à alimentation CC, des précautions devraient
être prises lors de la connexion de l'alimentation CC pour éviter des courts-circuits et des risques
d'incendie.
Assurez-vous que l'alimentation CC est isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation locale.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de
court-circuit dépassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des câbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'équipement et fixez-le
en position OFF. Lors de la connexion de câbles d'alimentation CC, connectez d'abord le
conducteur de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le
pôle négatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
Declaration of Conformity
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 2004/108/EC, the
Low Voltage Directive 2006/95/EC and the R&TTE Directive 99/5/EC for wired equipment. The
product was tested in a typical configuration.
Nathaniel Shomroni
Approvals Coordinator
Glossary
Address A coded representation of the origin or destination of data.
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.
Bridge A device interconnecting local area networks at the OSI data link layer,
filtering and forwarding frames according to media access control
(MAC) addresses.
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.
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.
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.
Half Duplex A circuit or device capable of transmitting in two directions, but not at
the same time.
Master Clock The source of timing signals (or the signals themselves) that all
network stations use for synchronization.
Parameters Parameters are often called arguments, and the two words are used
interchangeably. However, some computer languages such as C define
argument to mean actual parameter (i.e., the value), and parameter
to mean formal parameter. In RAD CLI, parameter means formal
parameter, not value.
Payload The 48-byte segment of the ATM cell containing user data. Any
adaptation of user data via the AAL will take place within the payload.
Physical Layer Layer 1 of the OSI model. The layer concerned with electrical,
mechanical, and handshaking procedures over the interface
connecting a device to the transmission medium.
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.
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.
1. Installing RIC-LC
2. Configuring RIC-LC
Configure RIC-LC to the desired operation mode via an ASCII terminal connected
to the rear 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 port.
Note The RIC-LC default user name is USER or SU (case insensitive). The default
password is 1234.
Factory-Set Configuration
2 Ethernet port 1
3 Ethernet port 2
4 Ethernet port 3
5 Ethernet port 4
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.
Chapter 3. Operation
3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-1
3.3 Default Settings ................................................................................................................... 3-3
3.4 Configuration and Management Alternatives ........................................................................ 3-6
Working with Terminal ....................................................................................................... 3-6
Logging In ..................................................................................................................... 3-7
Choosing Options .......................................................................................................... 3-7
Screen Example ............................................................................................................. 3-8
Navigating Tables .......................................................................................................... 3-8
Working with Telnet ........................................................................................................... 3-9
Configuring Host IP Address .......................................................................................... 3-9
Working with the Web Terminal ......................................................................................... 3-9
Logging In ................................................................................................................... 3-10
Navigating the Web Terminal Menus ........................................................................... 3-10
Working with RADview-EMS ............................................................................................. 3-10
Working with 3rd Party Network Management Systems ................................................... 3-11
3.5 Menu Maps ........................................................................................................................ 3-11
Configuration Menu ......................................................................................................... 3-13
Monitoring Menu ............................................................................................................. 3-16
Diagnostics Menu ............................................................................................................ 3-17
Utilities Menu ................................................................................................................... 3-18
3.6 Turning Off the Unit ........................................................................................................... 3-18
Chapter 4. Configuration
4.1 Services ................................................................................................................................ 4-1
Ethernet Management Traffic ............................................................................................ 4-1
Ethernet Traffic Services .................................................................................................... 4-4
4.2 Configuring for Management ................................................................................................ 4-5
Entering Device Information............................................................................................... 4-5
Configuring Host IP Parameters ......................................................................................... 4-6
Configuring Management Access Permissions and Methods ............................................... 4-6
Defining Management Access Permissions .................................................................... 4-7
Configuring Management Access ................................................................................... 4-8
Configuring Authentication and Community ....................................................................... 4-9
Configuring Network Managers ........................................................................................ 4-10
Configuring Alarm Trap Mask ........................................................................................... 4-11
Configuring Control Port Parameters ................................................................................ 4-12
4.3 Configuring for Operation .................................................................................................. 4-13
Setting System-Level Parameters ..................................................................................... 4-13
Selecting the Clock Source .......................................................................................... 4-13
Configuring the Date and Time .................................................................................... 4-15
Configuring Fault Propagation ..................................................................................... 4-17
Configuring Physical-Layer Parameters ............................................................................. 4-18
Configuring the Fast Ethernet Ports ............................................................................ 4-18
1.1 Overview
RIC-LC is a Fast Ethernet over E1 converter that provides simple, efficient and
cost-effective Fast Ethernet connectivity over one, four, eight or sixteen bonded
E1 circuits. The device enables service providers to supply high-capacity Ethernet
services to remote locations and transparently connect corporate LANs over
existing E1 links.
RIC-LC supports standard Ethernet over NG-PDH protocols including GFP ITU-T
G.8040, VCAT ITU-T G.7043 and LCAS ITU-T G.7042. These protocols allow service
providers to dynamically allocate bandwidth to their customers by mere changing
the number of links bonded to the virtual group, without stopping the service.
The following standard bonding and encapsulation protocols make RIC-LC
interoperable with third-party devices:
• Generic Framing Procedure (GFP –ITU-T G.7041)
• Virtual Concatenation (VCAT - ITU-T G.7043)
• Link Capacity Adjustment Scheme (LCAS - ITU-T G.7042).
RIC-LC supports Telnet, Web terminal, and SNMP v1&v2 applications for inband
configuration and management, as well as an ASCII terminal for out-of-band
management.
Product Options
Uplink Options
RIC-LC can be ordered with 1, 4, 8, 16 E1 interfaces.
Applications
Typical applications include Ethernet VPN services over E1 lines; aggregation of
enterprise LANs over E1 circuits; and IP DSLAM, cellular IP, and WiMAX base
station backhauling.
4 x 10/100BaseT n x E1 n x E1 4 x 10/100BaseT
Packet
Switched SDH/SONET
Network RIC-LC RIC-LC
ADM ADM LAN
NMS ADM
Customer Premises
Central Office
n x E1/T1 4 x 10/100BaseT
E1/T1 10/100BaseT
NMS
RIC_LC
LAN
Features
The main features of RIC-LC are described below.
Ethernet Interfaces
The Fast Ethernet interfaces (10/100BaseT) operate in full or half duplex, with
auto-negotiation and flow control.
WAN Interfaces
The unit supports the following interfaces:
• Framed E1 circuits (G.732N with CRC), up to 16. The E1 interfaces are G.703
and G.704 compliant.
• 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 ports are bundled together producing a less rigid, more
robust transfer method.
VCAT breaks the bundled payload into individual bytes that are transported over
the E1 lines in the bundle. 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. LCAS provides
a mechanism to remove links that are not carrying traffic due to failures or user
configuration. The link is detected and automatically removed from the VCG.
Bridge
RIC-LC 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.
The VLAN-aware bridge mode allows you to create a subgroup of bridge ports
within the bridge. Each subgroup is associated with a unique VLAN Identifier
(VID). Frames can be forwarded only between bridge ports that are members of
the same VLAN, enabling a total separation between different VLAN users within
the same bridge.
In VLAN-Unaware bridge mode, the bridge ignores VLAN tags and forwards
frames only according to their source and destination MAC addresses.
Management
Setup, control, and monitoring of status and diagnostics information can be
performed using the following methods:
• Local management via an ASCII terminal connected to the V.24 (RS-232) DCE
control port
• Remote inband and out-of-band management via the Ethernet network or
GFP logical port
• Web terminal: A Web-based element management system for remote device
configuration and maintenance. Web terminal is embedded in the units and
can be accessed from any standard Web browser.
• RADview: RAD’s SNMP-based element management software, providing SNMP
traps, status polling, and configuration download. RIC-LC supports the SNMP
v1&v2.
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 pings
• Downloading/uploading remote software and configuration files (TFTP)
• Upgrading software.
Timing
RIC-LC has a clock domain with master and fallback sources for timing. The clock
source can be an internal oscillator or a recovered clock signal from one of the
links.
Diagnostics
RIC-LC supports remote loopbacks for the E1 ports.
Statistics
RIC-LC provides statistics and counter capabilities for the physical Ethernet, E1
levels, and logical GFP statistics.
Fault Propagation
The unit features a user-configurable TDM-to-Ethernet 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.
LEDs are located on the front panel. Interfaces and control connectors are
located on the rear panel. For additional information, refer to Chapter 3.
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 Features
• Full VLAN-aware bridge in accordance with 802.1q
• Learning and forwarding according to MAC address and VID
• Learning of up to 960 MAC table entries (MAC + VID pairs) and 64 static
addresses
• Configuration of the aging time
• MAC table viewing (learned MACs).
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:
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.
Disable All VLAN tagged frames pass. Untagged/priority-only
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 RIC-LC 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, which 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 960 MAC table entries and 64 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 is updated.
• If the MAC already exists, but for a different bridge port, (dynamic entry) the
new entry overrides 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.
Transmission Process
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
at egress (regardless of whether it already has an existing VLAN tag), and
removal of a tag at ingress when the frame leaves through this port.
Encapsulation
RIC-LC supports one GFP VCAT LCAS group (VCG).
Note GFP VCAT LCAS maps Ethernet over framed E1 links. For E1 the LCAS information
is aligned to the E1 multiframe. Therefore E1 carrying Ethernet over GFP VCAT
LCAS must be transported transparently over the PDH/SDH network, to avoid
damaging the multiframe alignment.
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 XOR-ing 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.
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 + x43 scrambler; this
scrambler is always activated.
The Payload Area contains between 4 and 64 bytes, according to the following:
• PTI - Payload Type Identifier - indicates the content of the GFP frame: user
frame or management frame (RIC-LC does not generate management frames
in the Tx direction)
• PFI - indicates whether the packet includes PFCS
• EXI - indicates the type of extension header encapsulated in the frame.
RIC-LC supports transmission of a Null extension header (i.e., no extension
header is added)
• UPI - indicates the type of user data encapsulated in the GFP format.
RIC-LC 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, RIC-LC
generates idle frames.
Idle packets – The GFP idle frame is a special four-octet GFP control frame
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 ITU-T G-8040
standard.
• The PDH signal works in multiframe mode: CRC-4 multiframe mode for E1 (31
timeslots) is 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 ITU-T G.7041 (as described above).
The VCAT header information is the LCAS CONTROL packet, as described in the
ITU-T G.7043 standard. One control packet is transmitted in a period of 16
multiframes.
RIC-LC can work as a non-LCAS transmitter if all the fields such as MST, RSACK,
SQ, GID, CONTROL & CRC & MFI2 MSB are set to zero. The MFI 1 parameter is
incremented in a round-robin manner.
Rx Traffic Path
RIC-LC assumes that the traffic received from TDM ports is traffic arriving from a
non-LCAS GFP transmitter. RIC-LC treats this data according to the following:
• VCAT header extraction: The VCAT header is extracted from the first timeslot
of each multiframe.
• Frame Delineation: The frame border is recognized by synchronization on the
core header which contains the frame length & CRC16 on the length (see
Figure 1-6). 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
RIC-LC generates idle frames, with the Delta parameter equal to 2.
• Single-bit error correction: The GFP receiver has the ability to correct a
single-bit error in tHEC or cHEC. 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.
• 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.048 Mbs – 64 Kbps – 64/16 k) = 1.98 Mbs
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):
• E1 links: PPS =1.98 Mbs/ 8/ ( P_SIZE + Chec_O + Thec_O + Ehec_O + P_FCS )
In RIC-LC:
• Ehec_O is 0
• P_FCS is user-configurable.
Quality of Service
RIC-LC maps QoS to priority queues (4 PQ, strict priority or strict priority and
WFQ) according to one of the following:
• Port
• VLAN priority (802.1p)
• DSCP (bits 0-5 in IP ToS byte).
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
SOURCE ADDRESS
DESTINATION ADDRESS
OPTIONS PADDING
Timing
E1 Uplink
The Tx clock for the E1 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 links.
ADM
n x E1 n x E1
FE FE
SDH/SONET
RIC-LC RIC-LC
ADM ADM
E1 timing: E1 timing:
Internal clock Rx clock E1 link
ADM
ADM
STM-1/
n x E1
FE OC-3 FE
SDH/SONET
Egate-100 RIC-LC
E1 master clock: ADM ADM
E1 timing:
Internal clock Rx clock E1 link
or
Rx clock STM-1/OC-3 link
ADM
Management
RIC-LC’s performance can be locally monitored from an ASCII terminal, or from a
remote site using Telnet or the Web-based application. RAD’s SNMP network
management application RADview is supported as well.
Local Management
RIC-LC allows full configuration and diagnostics via an ASCII terminal. The ASCII
terminal is connected to the control port on the rear 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.
Remote Management
RIC-LC supports inband management, using dedicated VLAN running over the PDH
links. Out-of-band management link can be established via one of its Ethernet
interfaces, configured as out-of-band management port.
Management application options include Telnet, SNMP, and Web terminal.
Configuration, monitoring, and statistic counters are available.
Security
ASCII terminal, Telnet, and Web access are password protected. After 15 minutes
(default value) of inactivity, the system exits and you have to log in again.
Telnet, Web, and SNMP access can be individually disabled or restricted to
stations in the manager list.
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, RIC-LC 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-12 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.
Customer Premises Customer Premises
VLAN B VLAN B
n × E1 (Host) (User)
VLAN A
(User) ETX-202A
RIC-LC LAN
LAN
Central Office
Customer Premises Customer Premises
VLAN A VLAN C
n × E1 (Host) (User)
VLAN C
(User) ETX-202A
RIC-LC LAN
LAN
NMS
Central
Management Site
Diagnostics
RIC-LC offers several types of diagnostic and troubleshooting procedures:
• Ping test
• Remote loopbacks on the E1 ports
• Bit Error Rate Test (BERT) on the E1 ports
• Ethernet cable test
For additional information on diagnostics, refer to Chapter 5.
Auto-negotiation Supported
Connector Mini-USB
ACT (yellow) for On – Ethernet frame received or sent within the last
each Ethernet port second
Off – No frame received or sent within the last second
Power 5W
Consumption
DC Voltage 5VDC
Power 4.5W
Consumption
Interface Cable/Connector
Note When connecting Ethernet and/or Gigabit Ethernet cables longer than 30m, it is
recommended to use shielded cables.
To connect E1 equipment:
• Connect an E1 line (RJ-45, 8-pin connector) to the RJ-45 connector
designated E1.
• For unbalanced E1 connections, use BNC coax connector.
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-6. ASCII Terminal Connector (single-E1 external power supply enclosure)
Connecting to AC Power
The device supplies AC power for K-33 PL.BOX type only.
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 RIC-LC rear
panel.
2. Connect the power cable plug to outlet.
The unit turns on automatically upon connection to the outlet.
Connecting to DC Power
A special IEC 60320 adapter for 48(36)/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.
3.2 Indicators
The unit's LEDs are located on the front panel. Table 3-1 lists the functions of
the LED indicators.
Host ID 1
Host Priority 0
Stratum 0
Direction Unidirectional
Administrative Status Up
Administrative Status Up
Port VID 1
DSCP DSCP48, 56 – 3
others – 0
CIR Disable
CIR Disable
Note RIC-LC supports auto baud functionality. You can connect the serial cable and
press “Enter” when device powers up, RIC-LC can auto adjust the Baud Rate to
“PC configured”. After log in, you can configure the Baud Rate and save it as a
persistent rate.
Logging In
To log in:
1. Use SU (case insensitive) as user name with read/write permission.
2. Use 1234 as the (default) password for the first login.
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.
RIC-LC 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)?
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> toggles between the available values.
Screen Example
Figure 3-3 illustrates a typical screen, displaying the main items.
Product Title (RIC-LC)
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
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 for table navigation:
• Up Arrow: scroll up
Note
You can display these navigation keys by typing <?> from a table.
The following figure illustrates the static MAC table. MAC address, Port and VLAN
Id are the columns of the parameters to be defined.
RIC-LC
Static MAC Table
MAC Address | VID | Received Bridge Port
>
ESC-prev menu; !-main menu; CTRL+X-exit; ?-Help <1 Mngr>
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 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.
RIC-LC
Main Menu
1. Inventory >
2. Configuration >
3. Monitoring >
4. Diagnostics >
5. Utilities >
>
Configuration (2) Set and configure all parameters required for the operation
of RIC-LC
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 product option you purchased.
Configuration Menu
The following figures summarize the paths available for the configuration options:
Main Menu
1. Inventory
2. Configuration Configuration
3. Monitoring 1. System System System Clock
4. Diagnostics 2. Physical Layer
5. Utilities 1. System Clock Current Clock
3. Logical Layer Master/Fallback Clock
2. Management 1. Master Clock
4. Applications 1. Source
3. Terminal 2. Fallback Clock
4. Date and Time 2. Port
5. Fault Propagation Management
6. Factory Default 1. Device Info
2. Host Device Info
3. Management Access Description
4. Authentication and 1. System Name
Community 2. System Location
5. Manager List 3. Contact Person
6. Alarm Trap Mask
Host
1. IP Address
2. IP Mask
3. Default gateway
4. Host Tagging
5. Host ID
6. Host Priority
Management Access
1. User Access
2. Session Timeout
3. Telnet Access
4. Web Access
5. SNMP Access
User Access
User ID
1. User Name
Authentication and Community 2. Permission
1. SNMP Authentication Failure Trap 3. Access
2. SNMP Trap Community 4. ‘SU’Password
3. SNMP Read Community 5. New Password
4. SNMP Write Community 6. Confirmation
Telnet/Web Access
Manager List 1. Enable
Manager ID 2. Disable
1. Manager IP Address 3. Managers
2. Manager Trap Mask
SNMP Access
1. Enable
Alarm Trap Mask 2. Disable
1. LOS 3. Managers
2. LOF 4. Read Only
3. AIS 5. Managers Read Only
4. RDI
5. FEBE
Terminal
Data Bits
Parity Baud Rate
Stop Bits 1. 9600 bps
1. Baud Rate 2. 19200 bps
3. 38400 bps
4. 57600 bps
5. 115200 bps
Date and Time
System up Time
1. Set Time
2. Set Date NTP Servers
3. NTP Mode Server ID
4. GMT Region 1. IP Address
5. Update Interval 2. Admin Status
6. NTP Servers 3. Server UDP Port
4. Stratum
5. Time Since Last Rx Message
Fault Propagation 6. Send Update Request Once
1. Fault Propagation
2. Faulty Interfaces
3. Affected Interfaces
4. Direction
*. Fault
*. Action
Factory Default
1. Full
2. Except Management
Configuration
1. System
2. Physical Layer Physical Layer Ethernet
3. Logical Layer 1. Port Id
1. Ethernet
4. Applications 2. Admin Status
2. E1
3. Auto Negotiation
4. Flow Control Max Capability Advertised
5. Max Capability Advertised Speed and Duplex
5. Speed and Duplex 1. 10M half duplex
6. Loop Detection 2. 10M full duplex
7. Loop Detection VLAN 3. 100M half duplex
4. 100M full duplex
Setting
Tx Clock Source
Line Type
1. Port
2. Administrative Status
*. Interface Type
*. Line Code
*. Rx Sensitivity
Configuration
1. System GFP
2. Physical Layer Interface Type
3. Logical Layer Bind to
4. Applications 1. Port
2. Administrative Status
3. Port Name
4. Payload FCS
VCG
Interface Type
Max differential delay
1. Port
2. Administrative Status
3. Port Name
4. Bind to Physical Ports
5. Loop Detect
6. VCAT Header
Configuration
1. System
2. Physical Layer
3. Logical Layer
4. Applications Applications
1. Bridge Bridge
2. QoS 1. Vlan Mode
Vlan Mode
2. Forwarding Mode
1. Unaware
3. Aging Time
2. Aware
4. Clear Dynamic MAC
5. Static MAC Table
6. Bridge Port Forwarding Mode
7. VLAN Membership (Aware 1. Filter
bridge only) 2. Transparent
Bridge Port
1. Port Id
*. Bind To
2. Ingress filtering
3. Accepted Frame Type
4. Port VID
5. Default Priority Tag
6. Egress Tag Handling
7. Egress Tag Ether Type
VLAN Membership
1. VLAN ID
2. Egress Tagged Bridge Ports
3. Egress Untagged Bridge Ports
QoS
1. Scheduler Mode
2. Priority
3. Rate Limitation Priority
1. Classification Classification
2. Mapping 1. Port Id
2. Classification Selection
Mapping
1. 802.1p
2. DSCP
3. Port Default Priority
Rate Limitation
1. Egress
2. Ingress Egress
1. Port Id
2. CIR
Ingress
1. Port Id
2. CIR
3. Counted Packet Types
Monitoring Menu
The following figures summarize the paths available for the Monitoring options:
Main Menu
1. Inventory
2. Configuration
3. Monitoring Monitoring
4. Diagnostics 1. System
5. Utilities 2. Physical Layer System
3. Logical Layer MAC Address
System Up Time Interface Status
4. Application
Time Description
Date Type
1. Interface Status Administrative
2. Current Alarm Operation
3. Event Log Speed
Current Alarm
1. System Alarm
2. Port Alarm System Alarm
Index Alarm Entry
Port Alarm
Index
Port
Alarm Entry
Event Log
Show Log
1. Show Log
Source
2. Clear Log
Description
Information
Status
Date
Time
1. Jump to log
Main Menu
1. Inventory
2. Configuration
3. Monitoring Monitoring
4. Diagnostics 1. System
5. Utilities 2. Physical Layer
Physical Layer
3. Logical Layer
1. Ethernet Status
4. Applications
2. E1 Ethernet Port Type
1. Status Administrative Status
2. Port Statistics Operational Status SFP Information
Auto Negotiation Connector Type
Speed and Duplex Manufacturer Name
Loop Detection Status Manufacturer PN
1. Port Id Typical Max. Range
2. SFP Information (Device with Wave Length
fiber ports only) Fiber Type
Statistics
ES
SES
UAS
BES
Time Elapsed
1. Port
2. Interval
Main Menu
1. Inventory
2. Configuration
3. Monitoring Monitoring
4. Diagnostics 1. System
5. Utilities 2. Physical Layer
3. Logical Layer Logical Layer
4. Applications 1. Status Status
2. Statistics Interface Type
Port Name
Differential delay
1. Port
2. LCAS member status (VCG only)
Main Menu
1. Inventory
2. Configuration
3. Monitoring Monitoring
4. Diagnostics 1. System
5. Utilities 2. Physical Layer
3. Logical Layer
4. Applications
Application
1. Bridge Bridge
1. View MAC Table View MAC Table
VID
MAC Address
Received Bridge Port
Status
Diagnostics Menu
The following figure summarizes the paths available for the Diagnostics options:
Main Menu
1. Inventory
2. Configuration
Diagnostics
3. Monitoring
1. Loopback
4. Diagnostics
2. BERT
5. Utilities
3. Virtual Cable Test
4. Led Test Loopback
5. Ping 1. E1 E1
6. Port Mirror 1. Port
2. Loopback State Loopback State
1. Remote
2. Disable
BERT
Sync State
Bit Error Count
Bit Error Seconds
BERT Runtime
1. Port
*. Pattern
2. Send BERT
3. Inject Error
Ping
1. Destination IP Address
2. Timeout
3. Number of Send
Port Mirror
1. Port Name
2. Mirror Action
3. Target Port
Utilities Menu
The following figure summarizes the paths available for the Additional Tasks
options:
Main Menu
1. Inventory
2. Configuration
3. Monitoring
4. Diagnostics
5. Utilities
Utilities
1. File Utilities
2. Reset File Utilities
1. Download by Xmodem/Ymodem Download by Xmodem/Ymodem
2. Download/Upload by TFTP 1. Transfer Protocol Command
2. Command 1. SW Download & Reboot
*. Transfer Status 2. Config. Download & Reboot
Download/Upload by TFTP
1. File Name Command
2. Command 1. SW Download & Reboot
3. Server IP 2. SW Upload
4. Retry Timeout 3. Config. Download & Reboot
5. Total Timeout 4. Config. Upload
*. Transfer Status
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.
4.1 Services
This section shows the data flow and configuration steps for services.
RIC-LC
E1
Logical Ports
Ports
2 5 3
Add the bridge ports Associate Ethernet
Configure the
associated with the ports to corresponding
bridge logical ports to the bridge ports
Configure the Management VLAN
bridge port
Host parameters
Configure Host IP
Define Host ID
1 Configuring Host IP Configuration > System > This assigns the IP address, IP
Parameters Management > Host mask and default gateway to
the RIC-LC unit.
Defining a Host ID, available Configuration > System > This assigns the management
under Configuring Host IP Management > Host VLAN to the host.
Parameters Host Tagging must be
enabled.
Configuring the bridge port Configuration > Applications > This assigns the host bridge
parameters, available under Bridge > Bridge Port port parameters. You can
Configuring the Bridge Ports configure Ingress filtering,
Acceptable frame type and
Port VID, etc.
4 Defining logical ports, Configuration > Logical Layer Logical ports define groups of
available under Configuring E1 ports and parameters
the Logical Layer (GFP).
This and the following steps
are required to include the
remote units into the
Management VLAN.
5 Adding the bridge ports Configuration > Applications > Adds the Management VLAN
associated with the logical Bridge > VLAN Membership ID to the bridge port.
ports to the Management
VLAN, available under
Configuring VLAN
Membership
RIC-LC
3 2
E1 Ethernet
Logical Ports Bridge
Ports Ports
3 Defining logical ports, Configuration > Logical Layer Logical ports define groups of
available under Configuring E1 ports and parameters
the Logical Layer (GFP).
4 Adding the bridge ports Configuration > Applications > Adds the Ethernet traffic
associated with the logical Bridge > VLAN Membership VLAN ID to the bridge port.
ports to the Ethernet traffic
VLAN, available under
Configuring VLAN
Membership
RIC-LC
System>Management>Device Info
>
2. Select System Name, and type a name for the unit. The default name is
System name.
3. Select System Location, and type a location name/description.
4. Select Contact Person, and type the name of a contact person for this unit.
5. Select S to save the changes.
1. IP Address (192.168.99.198)
2. IP Mask (255.255.255.0)
3. Default gateway (192.168.99.250)
4. Host Tagging (Enable)
5. Host ID[1 - 4094] (1)
6. Host Priority[0 - 7] (0)
>
RIC-LC
Management>Management Access>User Access
User ID:1
1. User Name (SU)
2. Permission (Full control)
3. Access (All)
4. 'SU' Password ()
5. New Password ()
6. Confirmation ()
>
>
Note Available access permission settings depend on the access level selected in the
Management Access menu
4. Select S to save.
RIC-LC
System>Management>Authentication and Community
>
3. Select SNMP Authentication Failure Trap and toggle between Disable and
Enable.
Disable – Disable the Event of SNMP Authentication Failure.
Enable – Enable the Event of SNMP Authentication Failure.
4. Select SNMP Trap Community and type the name of a community to which
the unit should send SNMP traps (up to 16 alphanumeric characters,
case-sensitive).
5. Select SNMP Read Community and type the name of a community with SNMP
read-only authorization (up to 16 alphanumeric characters, case-sensitive).
6. Select SNMP Write Community and type the name of a community with write
authorization (up to 16 alphanumeric characters, case-sensitive).
7. Select S to save new settings.
RIC-LC
System>Management>Manager List
Manager ID:1
1. Manager IP Address (0.0.0.0)
2. Manager Trap Mask (Unmask)
>
Table 4-4 describes the IP address and the Trap mask fields in the Managers List
menu as illustrated below.
RIC-LC
Configuration>System>Management/Alarm Trap Mask
1.LOS
2.LOF
3.AIS
4.RDI
5.FEBE
Current selection:
>
2. Select the alarm traps that need to be masked, up to five types of alarm
traps can be masked simultaneously. The selected ones are displayed after
the Current selection.
3. To delete a selected alarm trap, select the type of alarm trap that needs to
be unmasked, the deleted ones are not displayed after the Current selection.
4. Click <Enter>, return to the Management menu and select S to save.
>
3. Select the desired baud rate (9600, 19200, 38400, 57600, 115200).
4. The default baud rate is 9600.
5. Select S to save.
Note Descriptions of this section are about the device with multi-E1 ports.
Transmitted data can be clocked either from an internal clock within the RIC-LC
unit, or from an external clock via the E1 ports.
The unit can be assigned two sources for timing:
• Fallback Source: activated when the master source fails (for example, when
the E1 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.
• Internal: for setting the internal clock as the master clock source
• Rxclk: for setting an external clock (from E1 link) for the master
clock source.
• Rxclk: for setting an external clock (from E1 link) for the fallback
clock source
1. Source (Internal)
>
Figure 4-11. Master Clock Menu, Internal for the Master Source
RIC-LC
System>System Clock>Master Clock
1. Source (Rxclk)
2. Port (E1-1)
>
Figure 4-12. Master Clock Menu, Rx Clock (External) for the Master Source
RIC-LC
System>System Clock>Fallback Clock
1. Source (None)
>
RIC-LC
System>System Clock>Fallback Clock
1. Source (Rxclk)
2. Port (E1-1)
>
Figure 4-14. Fallback Clock Menu, Rx Clock (external) for the Master Source
RIC-LC
Configuration>System>Date and Time
>
RIC-LC
Configuration>System>Date and Time>NTP Servers
Server ID (Primary)
1. IP Address (0.0.0.0)
2. Admin Status (Disable)
3. Server UDP Port(123)[1 - 65535] (123)
4. Stratum <0>
5. Time Since Last Rx Message <N/A>
6. Send Update Request Once
>
RIC-LC
Configuration>System>Fault Propagation
>
2. Set the fault propagation parameters according to Figure 4-17 and Table 4-5.
RIC-LC
Configuration>Physical Layer>Ethernet
1. Port Id (Eth1)
2. Admin Status (Enable)
3. Auto Negotiation (Enable)
4. Flow Control (Disable)
5. Max Capability Advertised (100M full duplex)
6. Loop Detection (Disable)
7. Loop Detection VLAN[1 - 4094] (4094)
>
2. From the Ethernet menu, type <F> Forward or <B> Backwards to select the
desired Fast Ethernet port.
3. Set the physical layer parameters of the selected port according to Figure 4-
18 and Table 4-6.
4. Select S to save the changes.
5. Repeat for all ports in use.
Max Capability Set of capabilities advertised by the local 10M Half Duplex
Advertised auto-negotiation entity 10M Full Duplex
Default: 100M full duplex 100M Half Duplex
100M Full Duplex
Note: This parameter only appears when
auto-negotiation is enabled
Speed and Status speed and duplex that the port uses 10M Half Duplex
Duplex when the auto-negotiation is disabled 10M Full Duplex
Default: 100M Full Duplex 100M Half Duplex
100M Full Duplex
Note: This parameter only appears when
aout-negotiation is disabled
Configuring E1 Ports
>
2. Select Signal Degrade BER Threshold, defining the signal degrade threshold
parameters. If the bit error on the E1 line exceeds the defined signal degrade
threshold, the E1 link is removed from the LCAS. The default value is 0 –
disable the signal degrade detecting of the port, possible values are 1E-5, 1E-
6, 1E-7, 1E-8, 1E-9.
3. Select Setting.
The Setting menu appears as illustrated in Figure 4-20.
RIC-LC
Physical Layer>E1>Setting
>
4. From the Setting menu, type <F> Forward or <B> Backwards to select the
desired E1 port.
5. Configure E1 port parameters for each E1 port according to Figure 4-20 and
Table 4-7.
6. Select S to save the changes.
You can map multiple E1 ports to a VCAT VCG group via the Logical Layer menu.
To ease configuration and save time, the RIC-LC unit is supplied with the logical
ports preconfigured (see the table below).
A logical port in RIC-LC is either a VCG logical port bound to physical E1 ports, or a
GFP logical port that is bound to a VCG logical port. When you create a VCG logical
port, RIC-LC 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 only create one VCG logical port.
Note A physical port can be bound to only one logical VCG port.
>
RIC-LC
Main Menu>Configuration>Logical Layer
>
2. Configure the logical parameters for each port. Parameter descriptions and
possible values are provided in Table 4-9.
Type <F> or <B> to scroll through the ports.
Interface Type Type of interface set for the port. This parameter is VCG
read-only GFP
Bind to Physical Ports VCAT VCG Logical Port: E1 links that are members of 1–16
the VCG
Loop Detect 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
3. Select S to save.
>
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.
RIC-LC
Applications>Bridge>Static MAC Table
*Total 1 Addresses
>
2. In the Static MAC Table, press <A> to add a static MAC address.
The Static MAC Table switches to the Add MAC Table mode as illustrated
in Figure 4-25.
RIC-LC
Bridge>Static MAC Table>Add MAC Table
>
Note The available numbers of MAC Addresses depend on the VLAN ID in VLAN
membership. The default value of VLAN ID is 1. Please configure the VLAN ID to
add more than one MAC addresses and vise versa.
The unit is shipped with default bridge port bindings preconfigured for basic use.
The factory defaults are listed below. You cannot delete bridge port bindings to
the host port, logical port and Ethernet ports.
2 Eth1
3 Eth2
4 Eth3
5 Eth4
>
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 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: 1
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 Stacking: Adds the PVID to every frame None
transmitted from the port (push). Stacking
Default: None
(1 4094)
*Total 2 VLANs
>
2. Select VLAN ID, or type <F> Forward or <B> Backwards to select the VLAN ID
you wish to configure.
3. Select Egress Tagged Bridge Ports. Define the set of ports to transmit packets
for this VLAN as tagged.
4. Select Egress Untagged Bridge Ports. Define the set of ports to transmit
packets for this VLAN as untagged.
5. Select S to save.
To delete a VLAN:
1. To delete a VLAN ID, type <F> Forward or <B> Backwards to select the VLAN
ID you wish to delete, press <D>.
The following message appears:
Do you want to remove this vlan (Y/N)?
2. To confirm your request, press <Y>.
RIC-LC
Configuration>Applications>QoS
>
2. Select Scheduler Mode and toggle between Strict Priority and Weighted
according to Figure 4-28.
Scheduler Mode Defines the bridge scheduling method. Strict Priority– High-priority queues that
are always serviced first. If a lower-
priority queue is being serviced and a
packet enters a higher queue, that queue
is serviced immediately.
Weighted – Priority queue are round-robin
scheduled according to 8-4-2-1 weight.
Default: Strict Priority
3. Select S to save.
1. Classification >
2. Mapping >
>
2. Select Classification.
The associated Classification menu appears as illustrated in Figure 4-30.
RIC-LC
QoS>Priority>Classification
>
3. From the Classification menu, type <F> Forward or <B> Backwards to select
the desired port from Bridge Port 1 to 6.
4. Select Classification Selection.
The associated Classification Selection menu appears as illustrated in
Figure 4-31.
RIC-LC
QoS>Priority>Classification/Classification Selection
1.802.1p
2.DSCP
3.port default priority
Current selection:802.1p
>
RIC-LC
QoS>Priority>Mapping
1. 802.1p >
2. DSCP >
3. Port Default Priority >
>
2. Select 802.1p.
3. The associated 802.1p menu appears as illustrated in Figure 4-33.
RIC-LC
Priority>Mapping>802.1p
>
4. In the 802.1p menu, select the desired user priority (0–7) and enter the
assigned traffic class number (0–3). Each traffic class can be assigned to
more than one priority.
5. Repeat the above step for all user priorities.
6. Select S to save.
RIC-LC
Priority>Mapping>DSCP
1. Traffic Class 0
2. Traffic Class 1
3. Traffic Class 2
4. Traffic Class 3
>
3. Type <Up Arrow>, <Down Arrow>, <Left Arrow> or <Right Arrow> to scroll
through the available cells, select the desired DSCP priority and enter the
assigned traffic class number (0–3). Each traffic class can be assigned to
more than one DSCP priority.
4. Press <ESC> to complete the DSCP mapping and return to the Mapping menu.
>
You can use the Rate Limitation menu for configuration of the Egress
bridge ports and Ingress bridge ports.
5. The Rate Limitation menu appears as illustrated in Figure 4-36.
RIC-LC
Applications>QoS>Rate Limitation
1. Egress >
2. Ingress >
>
>
2. Press <F> or <B> to select a bridge port (2–6) that you intend to configure.
3. Select CIR and choose the desired parameters according to Table 4-14.
CIR Defines the Committed Information Rate (CIR) for the Disable
current profile. The CIR specifies a bandwidth with 256Kbps
committed service guarantee.
512Kbps
Default: Disable
1Mbps
2Mbps
3Mbps
3.5Mbps
4Mbps
4.5Mbps
5Mbps
8Mbps
10Mbps
16Mbps
20Mbps
25Mbps
40Mbps
50Mbps
64Mbps
4. Select S to save.
5. Repeat this procedure for all bridge ports in use.
>
2. Press <F> or <B> to select a bridge port (2–6) that you intend to configure.
3. In the Ingress menu, configure the parameters according to Figure 4-38 and
Table 4-15.
CIR Defines the Committed Information Rate (CIR) for the Disable
current profile. The CIR specifies a bandwidth with 256Kbps
committed service guarantee.
512Kbps
Default: Disable
1Mbps
2Mbps
3Mbps
3.5Mbps
4Mbps
4.5Mbps
5Mbps
8Mbps
10Mbps
16Mbps
20Mbps
25Mbps
32Mbps
40Mbps
50Mbps
64Mbps
4. Select S to save.
5. Repeat this procedure for all bridge ports in use.
>
>
Note If an RIC-LC Fast Ethernet port includes an SFP transceiver, the SFP status
information is available via the SFP Information screen.
RIC-LC
Physical Layer>Ethernet>Status
>
RIC-LC
Ethernet>Status>SFP Information
Connector Type (LC)
Manufacturer Name (Gigalight )
Manufacturer PN (GP-3103-L1CD )
Typical Max. Range [m] (15000)
Wave Length [nm] (1300)
Fiber Type (SM)
(Current Min Max )
TX Optical Power [dBm] (-7.3 -7.3 -7.2)
LASER Bias [mA] (21.8 21.2 21.8)
LASER Temp [C/F] (49/119 42/107 49/119)
RX Optical Power [dBm] (-34.0 -34.0 -34.0)
Supply Voltage [V] (3.25 3.25 3.25)
>
Viewing E1 Status
Physical Layer>E1>Status
>
RIC-LC
Monitoring>Logical Layer>Status
>
RIC-LC
Monitoring>Logical Layer>Status
>
>
Parameter Description
>
R - Refresh
ESC - prev menu; ! - main menu; CTRL+X - exit <1 Mngr>
Viewing Inventory
The inventory displays a description of the unit including its hardware revision
and software revision.
Note The inventory is a wide table with 132 characters. It is best viewed by setting
your terminal to 132 character wide display.
RIC-LC
Main Menu>Inventory
>
ESC - prev menu; ! - main menu; CTRL+X - exit; ? - help <1 Mngr>
1 su 1234
Note User Access Parameters can only be changed by a user with full control
permission, eg. SU.
RIC-LC
Management>Management Access>User Access
User ID:1
1. User Name (SU)
2. Permission (Full control)
3. Access (All)
4. 'SU' Password ()
5. New Password ()
6. Confirmation ()
>
2. In the User Access menu, press <F> to select the desired User ID. If you need
to change the user name, select User Name and enter a new user name. The
user name can be up to seven characters.
3. Select Permission and toggle between Full Control and Read Only.
4. Select Access and define the desired access authority. The following access
authorities are available:
Terminal
Telnet
Web
Telnet & Web
All
5. Select ‘SU’ Password, and enter the current password of ‘SU’ (default is
1234).
Note Any configuration change in the User Access requests step 5. If you did not type
the ‘SU’ password correctly, the following system message appears.
SU password error!
compressed format. The active version is decompressed and loaded into the
RIC-LC 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, RIC-LC ships active software only.
New software releases are distributed as image files (*.img) downloaded to
RIC-LC. 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 RIC-LC using the Boot Manager, using Xmodem/Ymodem or
TFTP, as explained in Appendix B.
RIC-LC
Utilities>File Utilities>Download/Upload by TFTP
>
Resetting RIC-LC
RIC-LC lets you reset the unit while preserving customized parameters or
resetting all customized parameters to the factory defaults.
To reset RIC-LC:
1. From the Main menu, navigate to Utilities > Reset.
You are asked to confirm your request:
Do you want to reboot (Y/N)?
2. Press <Y> to confirm your request.
RIC-LC resets, preserving the last-saved settings.
RIC-LC
Physical Layer>Ethernet>Port Statistics
1. Port (Eth1)
Counter ---RX--- ---TX---
Total Correct Frames 8028 6
Total Correct Octets 4142576 384
FCS Errors 0 --
Jabber Errors 0 --
Fragments Errors 0 --
Undersized Frames 0 --
Oversized Frames 0 --
Collisions -- 0
Unicast Frames 4021 0
Multicast Frames 878 0
Broadcast Frames 3129 6
Pause Frames 0 0
Discard Frames 0 --
>
Parameter Description
Frames Received
Total Correct The total number of correct frames received. When a valid connection is established the
Frames number should increase steadily.
Total Correct The total number of octets (bytes) received. When a valid connection is established the
Octets number should increase steadily.
Jabber Errors The number of frames that are too long and have an invalid CRC.
A jabber is transmission by a data station beyond the time interval allowed by the
protocol, usually affecting the rest of the network. In an Ethernet network, devices
compete for use of the line, attempting to send a signal and then retrying in the event
that someone else tried at the same time. A jabber can look like a device that is always
sending, effectively bringing the network to a halt.
Recommendations
Check network interface card or any other transmitting devices and external electrical
interference.
Fragments Errors The number of frames that are shorter than 64 bytes and have an invalid CRC
Undersize Frames Number of frames received that were less than 64 octets long, but are otherwise valid
Ethernet frames (good CRC)
Oversize Frames Number of frames exceeding the maximum allowed frame size, but are otherwise valid
Ethernet frames (good CRC)
Parameter Description
Frames Transmitted
Total Correct The number of frames successfully transmitted. When a valid connection is established
Frames the number should increase steadily.
Total Correct The number of octets successfully transmitted. When a valid connection is established
Octets the number should increase steadily.
Displaying E1 Statistics
To view E1 port statistics:
1. In the Main menu, navigate to Monitoring > Physical Layer > E1 > Statistics.
2. Type F or B to navigate through port numbers.
The E1 Statistics screen appears as illustrated in Figure 5-2. The statistics
are described in Table 5-2.
To clear statistics:
• In the Statistics menu, type C to clear all E1 statistics.
RIC-LC
Physical Layer>E1>Statistics
ES: ( 0)
SES: ( 0)
UAS: (437)
BES: ( 0)
Time Elapsed (Sec) (438)
1. Port[1-16] (1)
2. Interval[0-96] ... (0)
>
Parameter Description
ES Number of seconds where errored seconds (ES) are detected. For ESF
and E1-CRC links an Errored Second is a second with one of:
• One or more Path Code Violation
• One or more Out of Frame defects
• One or more Controlled Slip events
• 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.
Parameter Description
Time elapsed For interval 0 displays number of seconds passed from the start time of
the interval
RIC-LC
Monitoring>Logical Layer>Statistics
Port[1-2] (2)
Interface Type (GFP)
Port Name (GFP 1)
>
C - Clear Results
ESC - prev menu; ! - main menu; CTRL+X - exit <1 Mngr>
Parameter Description
Displaying Events
To access the event log:
1. In the Main menu, navigate to Monitoring > System > Event Log > Show Log.
The Show Log screen appears as illustrated in Figure 5-4.
2. In the Show Log screen, use Cursor Up to page up and Cursor Down to page
down in the Events list.
RIC-LC
System>Event Log>Show log
>
ESC - prev menu; ! - main menu; CTRL+X - exit; ? - help <1 Mngr>
Table 5-4 presents some of the event types that appear in the show log.
101 Buffer overflow Event log buffer has exceeded its maximum size and new events are
written over the old ones.
103 Invalid login Login to the device with wrong user name or password
Clearing Events
To clear the event log:
1. Return to the Event Log menu and select Clear Log.
You are asked to confirm your request:
Log data will be cleared. Continue (Y/N)?
2. Press <Y> to confirm your request.
RIC-LC
System>Current Alarm>System Alarm
>
RIC-LC
System>Current Alarm>Port Alarm
>
5.4 Troubleshooting
Use the chart shown in Table 5-6 to identify and remedy problems in unit
operation.
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 RIC-LC’s
switch and RIC-LC do not match. Ethernet port configuration
(negotiation, rate, duplex mode).
• Use the event log to check events.
E1 local or remote Sync No E1 Link detected at the local or • Check whether the cable is
Loss LED on remote site. connected and correctly wired.
• Check the E1 physical connection
(use loopbacks).
• Check the configuration of the E1
lines at local and remote sites.
• Use the event log to check events.
No traffic flow between two Configuration or logical layer • Use the Event log file to check
units problems. events.
• Check RIC-LC’s configuration and, if
necessary, other RIC-LC
parameters.
Partial Traffic Flow Timing configuration is not properly • Check timing settings.
set.
To ping an IP host:
1. In the Main menu, navigate to Diagnostics > Ping.
The Ping menu appears as illustrated in Figure 5-7.
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 to Send. Select 1-20 to send a specified number of frames.
3. To start sending pings, type <P>.
The results are displayed in the lower scrolling message window.
4. To stop sending pings, press CTRL+C.
RIC-LC
Main Menu>Diagnostics>Ping
>
>
>
Bit Error Count Number of bit errors occurred in test. This 0-Number of bit errors
parameter is read-only and cannot be configured
RIC-LC
Diagnostics>Loopback>E1
1. Port (1)
2. Loopback State (Disable)
>
>
6.2 Impact
RIC-LC reboots itself immediately after software upgrade.
6.3 Prerequisites
This section details the RIC-LC software and versions compatible with the new
version. It also lists the software file names and outlines system requirements
needed for the upgrade procedure.
Software Files
The latest version releases are distributed as software files named RIC-LC.img.
The files can be obtained from the local RAD business partner from whom the
device was purchased.
System Requirements
Before starting the upgrade, verify that you have the following:
• For upgrade via TFTP:
Operational RIC-LC unit with valid IP parameters configured for the host
Connection to a PC with a TFTP server application (such as 3Cdaemon or
PumpKIN), and a valid IP address
Software image file stored on the PC
• For upgrade via Xmodem/Ymodem:
Operational RIC-LC unit
Connection to a PC via HyperTerminal
Software image file stored on the PC
6-2 Upgrading RIC-LC via the File Utilities Menu RIC-LC Ver. 2.0
Installation and Operation Manual Chapter 6 Software Upgrade
Using TFTP
To download the new software release to RIC-LC via the File Utilities menu:
1. Verify that the image file is stored on the PC with the TFTP server application.
2. Verify that the RIC-LC host has valid IP parameters.
3. Ping the PC to verify the connection.
4. Activate the TFTP server application.
5. Download the image file from the PC to RIC-LC.
Pinging the PC
Check the integrity of the communication link between RIC-LC and the PC by
pinging the PC from the RIC-LC.
RIC-LC Ver. 2.0 Upgrading RIC-LC via the File Utilities Menu 6-3
Chapter 6 Software Upgrade Installation and Operation Manual
Caution The Boot menu procedures are recommended only for use by authorized
personnel, because this menu provides many additional options that are intended
for use only by technical support personnel.
6-4 Upgrading RIC-LC Software via the Boot Menu RIC-LC Ver. 2.0
Installation and Operation Manual Chapter 6 Software Upgrade
• Downloading using the Ymodem protocol. This uses a different protocol and
the procedures are same.
Note If you miss the timing, RIC-LC performs a regular reboot process (this process
starts with Loading and ends with the log in screen).
0 - Exit Boot
1 - Dir
2 - Delete or Recover Software Copy
3 - Download an Application or Boot by Xmodem
4 - Download an Application or Boot by Ymodem
5 - Format Flash
6 - Format Database
7 - Basic Hardware Diagnostics
8 - Reset Board
9 - Enter Debug Shell
Select:
Using Xmodem/Ymodem
Use the following procedure to download new software release to RIC-LC via
Xmodem/Ymodem.
RIC-LC Ver. 2.0 Upgrading RIC-LC Software via the Boot Menu 6-5
Chapter 6 Software Upgrade Installation and Operation Manual
2. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
The Send File window is displayed:
Select the prescribed RIC-LC software file name (you can use the
Browse function to find it).
In the Protocol field, select Xmodem or Ymodem according to your
choice.
When ready, press Send in the Send File window.
You can now monitor the progress of the downloading in the Send File
window.
Backup system.......ok
3. At this stage, select Reset Board to reset the unit and activate the new
software.
4. Restore system from backup zone by selecting the Recover System from Back
Up Application option.
RIC-LC starts copying the file in backup zone to the system zone
immediately.
4 x 10/100BaseT n x E1 n x E1 4 x 10/100BaseT
Packet
Switched SDH/SONET
Network RIC-LC RIC-LC
ADM ADM LAN
NMS ADM
RIC-LC Ver. 2.0 Application with Ethernet Cellular Backhauling over PDH/SDH 7-1
Chapter 7 Application Tutorial Installation and Operation Manual
1. IP Address (192.188.10.12)
2. IP Mask (255.255.255.0)
3. Default gateway (192.188.10.1)
4. Host Tagging (Disable)
>
7-2 Application with Ethernet Cellular Backhauling over PDH/SDH RIC-LC Ver. 2.0
Installation and Operation Manual Chapter 7 Application Tutorial
RIC-LC
Configuration>System>System Clock
>
1. Source (Internal)
>
RIC-LC
Configuration>System>System Clock
>
RIC-LC Ver. 2.0 Application with Ethernet Cellular Backhauling over PDH/SDH 7-3
Chapter 7 Application Tutorial Installation and Operation Manual
RIC-LC
System>System Clock>Master Clock
1. Source (Rxclk)
2. Port (E1-1)
>
>
7-4 Application with Ethernet Cellular Backhauling over PDH/SDH RIC-LC Ver. 2.0
Installation and Operation Manual Chapter 7 Application Tutorial
RIC-LC
Main Menu>Configuration>Logical Layer
>
8 x E1 4 x 10/100BaseT
RIC-LC (A)
LAN
192.188.10.12
Central Office
NMS
Customer Premises
n x E1 4 x 10/100BaseT
RICi-4/8E1
LAN
RIC-LC
System>Management>Host
1. IP Address (192.188.10.12)
2. IP Mask (255.255.255.0)
3. Default gateway (192.188.10.1)
4. Host Tagging (Disable)
>
RIC-LC
Configuration>System>System Clock
>
1. Source (Rxclk)
2. Port (E1-8)
>
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.
RIC-LC
Physical Layer>E1>Setting
>
RIC-LC
Main Menu>Configuration>Logical Layer
>
RIC-LC
Main Menu>Configuration>Logical Layer
>
Pin Function
1 Tx+
2 Tx–
3 Rx+
4, 5 –
6 Rx–
7, 8 –
A.2 E1 Connector
The E1 electrical interface is an 8-pin RJ-45 connector, wired according to Table A-2.
Pin Function
1 Rx+
2 Rx–
3 NC
4 Tx+
5 Tx–
6 NC
7 NC
8 NC
Pin Function
2 Txd (TD)
3 Rxd (RD)
5 Ground (GND)
B-2 Transferring the Software and Configuration Files RIC-LC Ver. 2.0
Supplement
AC/DC Adapter
(AD) Plug
for DC Power Supply Connection
Caution
Prepare all connections to the AD plug before inserting it into the unit’s power
connector.
• 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
Publication No. 411-200-07/13
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail [email protected]
www.rad.com