Megaplex-4100 Manual Sheet New PDF

INSTALLATION AND
OPERATION MANUAL
Megaplex-4100
Next Generation Multiservice Access Node
Version 3.06
The Access Company
Megaplex-4100
Next Generation Multiservice Access Node
Version 3.06
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 Megaplex-4100
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 Megaplex-4100 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
Megaplex-4100. 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
Megaplex-4100, based on or derived in any way from the Megaplex-4100. Your undertaking in
this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the Megaplex-4100 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 Megaplex-4100 and all copies
and portions thereof.
For further information contact RAD at the address below or contact your local distributor.
International Headquarters
RAD Data Communications Ltd.
North America Headquarters

RAD Data Communications Inc.
24 Raoul Wallenberg Street

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

Mahwah, NJ 07430, USA
Tel: (201) 5291100, Toll free: 1-800-4447234
Fax: (201) 5295777
E-mail: market@radusa.com
19882012 RAD Data Communications Ltd.
Publication No. 464-201-09/12
Limited Warranty
RAD warrants to DISTRIBUTOR that the hardware in the Megaplex-4100 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 Megaplex-4100, and in no event
shall RAD's liability exceed the purchase price of the Megaplex-4100.
DISTRIBUTOR shall be responsible to its customers for any and all warranties which it makes
relating to Megaplex-4100 and for ensuring that replacements and other adjustments required in
connection with the said warranties are satisfactory.
Software components in the Megaplex-4100 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 Megaplex-4100
shall not exceed the sum paid to RAD for the purchase of the Megaplex-4100. In no event shall
RAD be liable for any indirect, incidental, consequential, special, or exemplary damages or lost
profits, even if RAD has been advised of the possibility of such damages.
This Agreement shall be construed and governed in accordance with the laws of the State of
Israel.
Product Disposal
To facilitate the reuse, recycling and other forms of recovery of waste
equipment in protecting the environment, the owner of this RAD product is
required to refrain from disposing of this product as unsorted municipal
waste at the end of its life cycle. Upon termination of the units use,
customers should provide for its collection for reuse, recycling or other form
of environmentally conscientious disposal.
General Safety Instructions

The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
Warning
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or service
personnel.
Danger of electric shock! Avoid any contact with the marked surface while the
product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building
protective ground bus.
Warning
Some products may be equipped with a laser diode. In such cases, a label with the
laser class and other warnings as applicable will be attached near the optical
transmitter. The laser warning symbol may be also attached.
Please observe the following precautions:
Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the transmitter.
Do not attempt to adjust the laser drive current.
Do not use broken or unterminated fiber-optic cables/connectors or look

straight at the laser beam.
The use of optical devices with the equipment will increase eye hazard.
Use of controls, adjustments or performing procedures other than those

specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP 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,

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

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

Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are not possible. These
ports are not permitted to be directly connected to
external telephone and data lines.
FXO (Foreign Exchange Office), xDSL

(with feeding voltage), U-Interface
ISDN

Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are possible.
Safety Extra Low Voltage:

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

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

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

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

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

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

Warning
Avertissement
Achtung
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.
Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel, cet
appareil peut provoquer des brouillages radiolectriques. Dans ces cas, il peut tre
demand lutilisateur de prendre les mesures appropries.
Das vorliegende Gert fllt unter die Funkstrgrenzwertklasse A. In Wohngebieten
knnen beim Betrieb dieses Gertes Rundfunkstrrungen auftreten, fr deren
Behebung der Benutzer verantwortlich ist.
Franais
Mise au rebut du produit

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

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

la prise de terre de protection du btiment.
Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre

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

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

les yeux.
L'usage de contrles, ajustages ou procdures autres que celles spcifies ici

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

Rgles gnrales de scurit
Ne pas toucher ou altrer l'alimentation en courant lorsque le cble d'alimentation est branch.
Des tensions de lignes peuvent tre prsentes dans certains produits, mme lorsque le
commutateur (s'il est install) est en position OFF ou si le fusible est rompu. Pour les produits
aliments par CC, les niveaux de tension ne sont gnralement pas dangereux mais des risques
de courant peuvent toujours exister.
Avant de travailler sur un quipement connect aux lignes de tension ou de tlcommunications,
retirez vos bijoux ou tout autre objet mtallique pouvant venir en contact avec les pices sous
tension.
Sauf s'il en est autrement indiqu, tous les produits sont destins tre mis la terre durant
l'usage normal. La mise la terre est fournie par la connexion de la fiche principale une prise
murale quipe d'une borne protectrice de mise la terre. Si une cosse de mise la terre est
fournie avec le produit, elle devrait tre connecte tout moment une mise la terre de
protection par un conducteur de diamtre 18 AWG ou plus. L'quipement mont en chssis ne
devrait tre mont que sur des chssis et dans des armoires mises la terre.
Branchez toujours la mise la terre en premier et dbranchez-la en dernier. Ne branchez pas des
cbles de tlcommunications un quipement qui n'est pas mis la terre. Assurez-vous que
tous les autres cbles sont dbranchs avant de dconnecter la mise la terre.
Franais
Certains produits peuvent tre quips d'une diode laser. Dans de tels cas, une
tiquette indiquant la classe laser ainsi que d'autres avertissements, le cas chant,
sera jointe prs du transmetteur optique. Le symbole d'avertissement laser peut
aussi tre joint.
Avertissement
Veuillez observer les prcautions suivantes :
Franais
Connexion au courant du secteur

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

Signal)
One of the OAM function types used for fault management (see
also CC).
Analog
A continuous wave or signal (such as human voice).
ANSI
American National Standards Institute.
APS (Automatic
protection switching)
An automatic service restoration function by which a network

senses a circuit or node failure and automatically switches traffic
over an alternate path.
Async
See Asynchronous Transmission.
Asynchronous
Transmission
A transmission method that sends units of data one character at a

time. Characters are preceded by start bits and followed by stop
bits, which provide synchronization at the receive terminal. Also
called start-stop transmission.
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.
Balanced Line
A circuit in which neither side of the line is grounded. This

minimizes crosstalk or noise pickup between pairs in the same
cable.
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.
Baseband
Refers to transmission of a digital or analog signal at its original

frequency, as an unmodulated signal.
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).
Bit
Interleaving/Multiplexing
A process used in time division multiplexing where individual bits

from different lower speed channel sources are combined (one bit
from one channel at a time) into one continuous higher speed bit
stream.
bps (Bits Per Second)
A measure of data transmission rate in serial transmission.
Bridge
A device interconnecting local area networks at the OSI data link

layer, filtering and forwarding frames according to media access
control (MAC) addresses.
Broadband
Wideband technology capable of supporting voice, video and data,

possibly using multiple channels.
Buffer
A storage device. Commonly used to compensate for differences

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

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

modulated with a second (information carrying) signal.
Cell
The 53-byte basic information unit within an ATM network. The

user traffic is segmented into cells at the source and reassembled
at the destination. An ATM cell consists of a 5-byte ATM header
and a 48-byte ATM payload, which contains the user data.
Central Office (CO)
Telephone company switching office. This is where you would find

the local telco switch that connects to your telephone.
Channel
A path for electrical transmission between two or more points.

Also called a link, line, circuit or facility.
Circuit Emulation
In ATM, a connection over a virtual circuit-based network providing

service to the end users that is indistinguishable from a real pointto point, fixed-bandwidth circuit.
CLI
Command Line Interface (CLI) is a mechanism for interacting with a

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

transmission.
Compression
Any of several techniques that reduce the number of bits required

to represent information in data transmission or storage, thereby
conserving bandwidth and/or memory.
Concentrator
Device that serves as a wiring hub in a star-topology network.

Sometimes refers to a device containing multiple modules of
network equipment.
Congestion
A state in which the network is overloaded and starts to discard

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

prevent excessive situations (buffer overflow, insufficient
bandwidth) that can cause the network to collapse. In ATM
networks, congestion control schemes may be based on fields
within the ATM cell header (CLP, EFCI within the PTI) or may be
based on a more sophisticated mechanism between the ATM endsystem and ATM switches. The ATM Forum has developed a
mechanism based on rate control for ABR-type traffic. In Frame
Relay networks, congestion is handled by the FECN, BECN and DE
bits.
Control Signals
Signals passing between one part of a communications system

and another (such as RTS, DTR, or DCD), as part of a mechanism
for controlling the system.
CORBA
The acronym for Common Object Request Broker Architecture,

OMG's open, vendor-independent architecture and infrastructure
that computer applications use to work together over networks.
One of its most important uses is in servers that must handle large
number of clients, at high hit rates, with high reliability, such as
network management systems.
Crosstalk
An undesirable condition that happens when a communication

from one line can be heard on another independent line. This is
usually caused by inductive or capacitive coupling, or by an
electrical short circuit between adjacent lines.
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.
dBm
A measure of power in communications: the decibel in reference

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

communications device, network or system.
Differential Delay
Differential delay is caused when traffic is split over different lines

that may traverse shorter and longer paths. Products like the RAD
IMX-2T1/E1 inverse multiplexer compensate for any differential
delay (up to 64 msec) between the T1 lines, to properly
reconstruct the original stream.
Digital
The binary (1 or 0) output of a computer or terminal. In data

communications, an alternating, non-continuous (pulsating) signal.
Digital Loopback
A technique for testing the digital processing of a communications

device. The loopback is toward the line side of a modem, but tests
most of the circuitry in the modem under test.
Distortion
The unwanted change in a signals waveform occurring between

two points in a transmission system.
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.
E&M Signaling
Voice transmission system that uses separate paths for signaling

and voice. The M lead (mouth) transmits signals to the remote
end of the circuit while the E lead (ear) receives incoming
signals.
Echo Cancellation
Echo cancellation improves the quality of voice transmissions. It

eliminates the echo that results from the reflection of the
telephony signal back to the caller, which can occur in a 4-wire to
2-wire hybrid connection between the VFRAD and the telephones
or PBX. The longer it takes the signals to return to the caller, the
more perceptible the echo.
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.
Ethernet OAM
Ethernet operation, administration and maintenance (OAM) are a

set of standardized protocols for measuring and controlling
network performance. There are two layers of Ethernet OAM:
Service OAM (provides end-to-end connectivity fault management
per customer service instance, even in multi-operator networks)
and Link or Segment OAM (detailed monitoring and
troubleshooting of an individual physical or emulated link).
Flow Control
A congestion control mechanism that results in an ATM system

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

transmission medium. The terms packet, datagram, segment, and
message are also used to describe logical information groupings.
Frame Relay
An efficient packet switching technology providing high speed

frame or packet transmission with minimum delay and efficient
bandwidth utilization over virtual circuits. The link layer handles
much of the network layer functionality. It has less protocol

overhead than X.25.
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

Office)
A voice interface, emulating a PBX extension, as it appears to the

CO (Central Office) for connecting a PBX extension to a
multiplexer.
FXS (Foreign Exchange

Subscriber)
A voice interface, emulating the extension interface of a PBX (or

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.
GFP (Generic Framing

Procedure)
Defined by ITU-T G.7041, generic framing procedure allows

efficient mapping of variable length, higher-layer client signals,
such as Ethernet, over a transport network like SDH/SONET.
Recently, GFP has been extended to lower speed PDH networks.
Grooming
In telecommunications, the process of separating and segregating

channels by combing, such that the broadest channel possible can
be assembled and sent across the longest practical link. The aim is
to minimize de-multiplexing traffic and reshuffling it electrically.
Half Duplex
A circuit or device capable of transmitting in two directions, but

not at the same time.
IEEE C37.94
A standard providing plug-and-play transparent communications

between different manufacturers Teleprotection and multiplexer
devices using multimode optical fiber. The standard defines clock
recovery, jitter tolerances, physical connection method, and the
equipment-failure actions for all communications link failures.
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.
Inverse Multiplexing
A method in which the inverse multiplexer slices the data stream

into equal portions and transmits each portion over an available
circuit. The receiving end adjusts for network-induced delay and
reassembles the data packets into their proper order. Therefore,
an inverse multiplexer allows lower speed channels across a
network to be combined into a single, higher speed data stream.
IP Address
Also known as an Internet address. A unique string of numbers

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

introduce errors and loss of synchronization in high speed
synchronous communications.
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.
LCAS (Link Capacity

Adjustment Scheme)
A method to dynamically increase or decrease the bandwidth of

virtual concatenated containers in SDH. The LCAS protocol is
specified in ITU-T G.7042. It allows on-demand increase or
decrease of the bandwidth of the virtual concatenated group in a
hitless manner. This brings bandwidth-on-demand capability for
data clients like Ethernet when mapped into SDH containers.
Leased Line
A permanent telephone connection between two points that is

rented for exclusive use from a telecommunications common
carrier. In contrast to a normal dial-up connection, a leased line is
always active. Typically, the highest speed data connections
require a leased line connection. For example, a T1 channel is a
type of leased line that provides a maximum transmission speed of
1.544 Mbps.
Line Driver
A signal converter which conditions a digital signal to ensure

reliable transmission over an extended distance.
Loading
The addition of inductance to a line in order to minimize amplitude

distortion. Used commonly on public telephone lines to improve
voice quality, it can make the lines impassable to high speed data,
and baseband modems.
Logical MAC
A concept used to describe and map the Ethernet traffic passing over
different media (E1/T1, SDH/SONET, etc). Logical MAC represents the
MAC layer of the entity. It should be bound to a GFP, HDLC or MLPPP
port, which, in its turn, should be bound to the physical layer.
Loop Start
The most commonly used method of signaling an off-hook

condition between an analog phone set and a switch, where
picking up the receiver closes a wire loop, allowing DC current to
flow, which is detected by a PBX or local exchange and interpreted
as a request for service.
Loopback
A type of diagnostic test in which the transmitted signal is

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

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

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

includes dedicated circuits for the detection of polarity and of 16
kHz or 12 kHz metering pulses.
MIB (Management
Information Base)
A directory listing the logical names of all information resources

residing in a network and pertinent to the networks management.
A key element of SNMP management systems.
Modular
Modular interfaces enable field-changeable conversion.
Modulation
The alteration of a carrier wave in relation to the value or samples

of the data being transferred.
Multidrop
A communications configuration in which multiple devices share a

common transmission facility (or multipoint line), although
generally only one may transmit at a time. Usually used with some
kind of polling mechanism to address each connected terminal
with a unique address code.
Multimode Fiber
A fiber with a large core diameter; 50-200 microns compared with

the wavelength of light. It therefore propagates more than one
mode. With multimode fiber, light traverses multiple paths, some
longer than others. This leads to dispersion, which reduces optical
range.
Multiplexer
At one end of a communications link, a device that combines

several lower speed transmission channels into a single high speed
channel. A multiplexer at the other end reverses the process.
Sometimes called a mux. See Bit Interleaving/Multiplexing.
Multipoint Line
See Multidrop.
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.
Network Layer
A layer in the OSI reference model. The network layer provides

address resolution and routing protocols. Address resolution
enables the network layer to determine a unique network address
for a node. Routing protocols allow data to flow between
networks and reach their proper destination. Examples of network
layer protocols are Address Resolution Protocol (ARP), Datagram
Delivery Protocol (DDP), Internet Control Message Protocol (ICMP),
Interior Gateway Protocol (IGP), Internet Protocol (IP),
Internetwork Packet Exchange (IPX) and Packet Layer Protocol
(PLP).
NMS (Network
Management System)
The system that controls the network configuration, fault and

performance management, and diagnostic analysis.
Node
A point of interconnection to a network.
Off-Hook
A state that results when you lift a telephone receiver, producing a

busy signal.
Omnibus
Instant multi-party voice communications between distant

operators in a non-service-intrusive fashion.
On-Hook
A state that results when the telephone receiver is in place. No

loop current flows and the switch recognizes that the telephone is
available for incoming calls.
Out-of-Band
Connection
A remote link, or a link outside connected networks, established

over a modem. It is useful when network communications are not
available.
Packet
An ordered group of data and control signals transmitted through

a network, as a subset of a larger message.
Packet Switching
A data transmission technique, which divides user information into

discrete data envelopes called packets, and sends the information
packet by packet.
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.
Parity Bit
An additional non-information bit added to a group of bits to

ensure that the total number of 1 bits in the character is even or
odd.
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.
PCM Bus
The term used to indicate that traffic passing over this bus is
structured and locked to the system timing.
PCS (Physical Coding

Sublayer)
Part of the Ethernet PHY layer which performs rate matching (in
case of an Ethernet port with auto-negotiotion)
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.
Prioritization
Also called CoS (class of service), classifies traffic into categories

such as high, medium, and low. The lower the priority, the more
drop eligible is a packet. When the network gets busy,
prioritization ensures critical or high-rated traffic is passed first,
and packets from the lowest categories may be dropped.
prompt
One or more characters in a command line interface to indicate

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

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

native services like ATM, Frame Relay, Ethernet, TDM, or
SONET/SDH over an underlying common packet-switched network
(Ethernet, MPLS or IP) core. Pseudowires are defined by the IETF
PWE3 (pseudowire emulation edge-to-edge) working group.
Repeater
A device which automatically amplifies, restores or reshapes

signals to compensate for distortion and/or attenuation prior to
retransmission.
Reverse Polarity
Signaling call answer and disconnect status is often a problem on

analog voice circuits (FXO). When circuits supporting reverse
polarity are available, the signaling problem can be solved by
sensing reverse polarity and toggling the status of the signaling
bits appropriately.
Router
An interconnection device that connects individual LANs. Unlike

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

message.
Satellite Link
A microwave link that uses a satellite to receive and retransmit

signals. Uses a geosynchronous orbit to keep a satellite above a
fixed position on the equator.

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).
SAToP
Structure-Agnostic Time Division Multiplexing (TDM) over Packet. A

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

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

binary 0.
Sync
See Synchronous Transmission.
Synchronous
Transmission
Transmission in which data bits are sent at a fixed rate, with the
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.
Teleprotection
Transmission of protection commands in high voltage grids of

electricity. IEEE C37.94 is a standard for interfacing between
Teleprotection equipment and communications devices.
Telnet
The virtual terminal protocol in the Internet suite of protocols. It

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

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

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

guarantee the operability of the network, exercised in the form of
traffic control and flow control.

Trunk
A single circuit between two points, both of which are switching

centers or individual distribution points. A trunk usually handles
many channels simultaneously.
VLAN-Aware
A device that is doing the Layer 2 bridging according to the VLAN

tag in addition to the standard bridging parameters. A VLAN-aware
device will not strip or add any VLAN header.
Voice Compression
Newer voice compression algorithms try to model 64 kpbs PCM

(G.711) more efficiently using fewer bits to reduce the bandwidth
required, while preserving the quality or audibility of the voice
transmission. Vendors such as RAD support low bit rate voice
compression algorithms such as ITU G.723.1 and G.729A to permit
the greatest number of simultaneous multiple calls while
maintaining high quality voice. In this way, compressed voice
systems can offer greater bandwidth savings, reduced network
congestion and high quality voice transmissions.
Zero suppression
Technique used to ensure a minimum density of marks.
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:
Megaplex-4100
conforms to the following standard(s) or other normative document(s):

EMC:
Safety:
EN 55022:1998 +
A1:2000, A2:2003
Information technology equipment Radio

disturbance characteristics Limits and
methods of measurement.
EN 50024:1998 +
A1:2000, A2:2003
Information technology equipment Immunity

characteristics Limits and methods of
measurement.
EN 60950: 2000
Information technology equipment Safety

Part 1: General requirements
Supplementary Information:
The product herewith complies with the requirements of the EMC Directive 89/336/EEC, 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.
Tel Aviv, 7 August, 2007
Haim Karshen
VP Quality
European Contact: RAD Data

Ottobrunn-Riemerling, Germany
Communications
GmbH,
Otto-Hahn-Str.
28-30,
85521
Quick Start Guide

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

1. Determine the required configuration of Megaplex-4100, according to your
application.
2. Install the Megaplex-4100 enclosure.
3. Install the modules in accordance with the site installation plan.
4. Connect the ASCII terminal to the RS-232 control port.
5. Connect power to the unit.
Connecting the Interfaces
To connect the interfaces:

1. Insert the SFP modules (if applicable) into the relevant SFP-based Ethernet
ports.
2. Refer to the site installation plan, and connect the prescribed cables to the
Megaplex-4100 modules.
Connecting to a Terminal
To connect the unit to a terminal:

1. Connect the male RJ-45 connector of the cable supplied by RAD to the unit's
8-pin connector, designated CONTROL DCE.
2. Connect the other side of the cable to the ASCII terminal equipment.
Connecting the Power

Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Megaplex-4100 Ver. 3.06
Installing the Unit
Quick Start Guide
2.
Configuring the Unit for Management
Configure Megaplex-4100 for management, using a local ASCII-based terminal.
Starting a Terminal Session for the First Time
To start the terminal session:

1. Connect an ASCII terminal to the CONTROL DCE connector of the active CL
module (use a straight cable).
2. Configure the ASCII terminal to the settings listed below and then set the
terminal emulator to VT100 emulation for optimal view of system menus.
Data Rate:
9,600 bps
Data bits:
Parity:
None
Stop bits:
Flow control:
None.
3. If you are using HyperTerminal, set the terminal mode to 132-column mode
for optimal view of system menus (Properties> Settings> Terminal Setup>
132 column mode).
4. Turn the power on.
Note
The Megaplex-4100 PS modules do not include a power switch. Use an external

power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
5. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
After a few seconds, Megaplex-4100 starts decompressing its software.
After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4100
performs its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4100.
6. When the startup process is completed, you are prompted to press <ENTER>
to receive the login prompt.
7. Press <ENTER> until you receive the login prompt.
8. If the Megaplex-4100 default user name and password have not yet been
changed, log in as administrator using su as the user name (su for full
configuration and monitoring access) and 1234 for password.
9. The device prompt appears:
mp4100#
Configuring the Unit for Management
Quick Start Guide
You can now type the necessary CLI commands.
Configuring the Router

To enable a Telnet host to communicate, it is necessary to assign its IP address
to the management router (1) interface 9999. This interface is configured by
default and connected to the out-of-band Ethernet management port (CONTROL
ETH).
To configure router interface #9999 for management:

1. Define IP address of the management interface (#9999).
2. Define the default gateway (static-route 0.0.0.0/0).
mp4100# configure
mp4100>config# router 1
mp4100>config>router(1)# interface 9999
mp4100>config>router(1)>interface(9999)# address 172.18.170.77/24
mp4100>config>router(1)>interface(9999)#exit
mp4100>config>router(1)# static-route 0.0.0.0/0 address 172.18.170.1
mp4100>config>router(1)#commit
3.
Saving Management Configuration
Saving Configuration
Type save in any level to save your configuration in startup-config.
Copying User Configuration to Default Configuration

In addition to saving your configuration in startup-config, you may also wish to
save your configuration as a user default configuration.
To save user default configuration:
Enter the following commands:
exit all
file copy startup-config user-default-config
y
4.
Verifying Connectivity
At the ASCII terminal, ping the IP address assigned to Megaplex-4100 and verify
that replies are received. If there is no reply to the ping, check your configuration
and make the necessary corrections.
Quick Start Guide
Contents
Chapter 1. Introduction
1.1
1.2
1.3
1.4
Overview ..................................................................................................................... 1-1

Product Options ....................................................................................................... 1-1
SDH/SONET Interface ........................................................................................... 1-1
GbE Interface ....................................................................................................... 1-2
Power Supply ....................................................................................................... 1-2
Applications.............................................................................................................. 1-2
Central Solution for RAD CPE Devices .................................................................. 1-2
TDM and Ethernet Multiservice Access ................................................................. 1-3
Smooth Migration from TDM to PSN .................................................................... 1-4
Features ................................................................................................................... 1-5
DS0 Cross-Connect .............................................................................................. 1-6
Protection ........................................................................................................... 1-7
Diversity of Rings................................................................................................. 1-7
Modularity and Flexibility ..................................................................................... 1-7
Next-Generation ADM/Terminal ........................................................................... 1-8
Timing ................................................................................................................. 1-8
Management ....................................................................................................... 1-9
Diagnostics ........................................................................................................ 1-10
Alarm Collection and Reporting .......................................................................... 1-10
Performance Monitoring .................................................................................... 1-11
Security ............................................................................................................. 1-11
New in this Version .................................................................................................... 1-11
Major Version Update ............................................................................................. 1-11
Minor Version Update ............................................................................................. 1-12
Physical Description ................................................................................................... 1-12
System Structure .................................................................................................... 1-12
Equipment Description ........................................................................................... 1-13
I/O Modules ............................................................................................................ 1-15
Common Logic (CL.2) Modules................................................................................ 1-18
Power Supply (PS) Modules .................................................................................... 1-19
PS Modules ........................................................................................................ 1-19
Feed and Ring Voltage Sources .......................................................................... 1-20
Functional Description ............................................................................................... 1-20
Megaplex-4100 Architecture .................................................................................. 1-20
TDM Engine ............................................................................................................ 1-22
DS0 Cross-Connect Matrix ................................................................................. 1-22
DS1 Cross-Connect Matrix ................................................................................. 1-24
E1/T1 Framers and Mappers .............................................................................. 1-24
SDH/SONET Engine ................................................................................................. 1-25
SDH/SONET Network Port Interfaces ................................................................. 1-25
SDH/SONET Framer and LO/HO Cross-Connect Matrix ........................................ 1-25
Packet Engine ......................................................................................................... 1-25
Packet Processor ............................................................................................... 1-26
VCAT Engine....................................................................................................... 1-27
HO/LO Mapper ................................................................................................... 1-27
Ethernet over SDH/SONET and E1/T1 - General Concept .................................... 1-27
Ethernet over E1/T1 .......................................................................................... 1-28
Ethernet over SDH/SONET ................................................................................. 1-29
Table of Contents
1.5
I/O Modules ............................................................................................................ 1-31

Megaplex-4100 Architecture Entities ...................................................................... 1-31
Technical Specifications ............................................................................................. 1-34
Chapter 2. Installation
2.1
2.2
2.3
2.4
2.5
ii
Site Requirements and Prerequisites ........................................................................... 2-1

General Safety Precautions ...................................................................................... 2-1
Grounding ................................................................................................................ 2-2
Laser Safety ............................................................................................................. 2-3
Protection against ESD ............................................................................................. 2-3
AC Power Requirements ........................................................................................... 2-4
DC Power Requirements ........................................................................................... 2-4
Front and Rear Panel Clearance ................................................................................ 2-5
Ambient Requirements ............................................................................................. 2-5
Electromagnetic Compatibility Considerations .......................................................... 2-5
Package Contents ........................................................................................................ 2-6
Required Equipment .................................................................................................... 2-6
Mounting the Megaplex-4100 Unit .............................................................................. 2-6
Familiarization with Megaplex-4100 ......................................................................... 2-7
Rear View ............................................................................................................ 2-7
Front Panel .......................................................................................................... 2-8
Installing PS Modules ................................................................................................ 2-9
Module Panels ..................................................................................................... 2-9
Internal Jumpers ................................................................................................ 2-10
Installing a PS Module ........................................................................................ 2-11
Removing a PS Module....................................................................................... 2-11
Installing CL Modules .............................................................................................. 2-11
Module Panels ................................................................................................... 2-11
Preparing CL Modules for Installation ................................................................. 2-13
Installing a CL Module ........................................................................................ 2-14
Removing a CL Module ....................................................................................... 2-15
Replacing a CL Module during Equipment Operation Megaplex-4100 Chassis with
two CL Modules ................................................................................................. 2-15
Replacing a CL Module during Equipment Operation Megaplex-4100 Chassis with
Single CL Module ............................................................................................... 2-16
Installing I/O Modules ............................................................................................. 2-16
Installing Blank Panels ............................................................................................ 2-16
Installing the Megaplex-4100 Enclosure.................................................................. 2-17
Installing in a 19 Rack ...................................................................................... 2-17
Installing in 23 Rack ......................................................................................... 2-18
Connecting the Megaplex-4100 Unit .......................................................................... 2-18
Grounding Megaplex-4100 ..................................................................................... 2-18
Connecting to Power .............................................................................................. 2-19
Connecting to External Feed and Ring Voltages ...................................................... 2-19
Connecting to a Terminal........................................................................................ 2-19
Connecting to a Management Station or Telnet Host ............................................. 2-20
Connecting the Station Clock Port .......................................................................... 2-20
Connecting the Alarm Port ..................................................................................... 2-21
Connecting to SDH/SONET Equipment .................................................................... 2-22
Connecting Optical Cables to the SDH/SONET Links ........................................... 2-22
Connecting Coaxial Cables to SDH/SONET Links ................................................. 2-23
Connecting I/O Modules to Remote Equipment ...................................................... 2-23
Connections to E1 and T1 Ports ......................................................................... 2-23
Table of Contents
Connections to Ethernet Ports ........................................................................... 2-23

Optical Cable Requirements ............................................................................... 2-24
Chapter 3. Operation
3.1
3.2
3.3
3.4
3.5
Turning On the Unit ..................................................................................................... 3-1

Indicators .................................................................................................................... 3-2
CL.2 Front Panel Indicators ....................................................................................... 3-3
Megaplex-4100 Front Panel Indicators ..................................................................... 3-5
Startup ........................................................................................................................ 3-6
Configuration Files ................................................................................................... 3-6
Loading Sequence .................................................................................................... 3-7
Using a Custom Configuration File ............................................................................... 3-8
Turning Off the Unit .................................................................................................... 3-8
Chapter 4. Management
4.1
4.2
4.3
4.4
4.5
Management Access Methods...................................................................................... 4-1

Working with Terminal ................................................................................................. 4-2
Connecting a Terminal to the Control Port ................................................................ 4-2
Login ........................................................................................................................ 4-5
Using the CLI ............................................................................................................ 4-5
Command Tree ......................................................................................................... 4-8
Working with Telnet and SSH ..................................................................................... 4-26
Working with Telnet ............................................................................................... 4-26
Using SSH ............................................................................................................... 4-27
Working with RADview ............................................................................................... 4-28
Working with 3rd Party Network Management Systems ............................................. 4-28
Chapter 5. Configuration
5.1
5.2
5.3
5.4
5.5
5.6
Services ....................................................................................................................... 5-1

Terminal Control .......................................................................................................... 5-2
Standards ................................................................................................................. 5-2
Functional Description .............................................................................................. 5-2
Factory Defaults ....................................................................................................... 5-2
Configuring Control Port Parameters ........................................................................ 5-3
Programming Modules in the Chassis ........................................................................... 5-3
Configuring Modules in the Chassis .......................................................................... 5-3
Example .................................................................................................................... 5-5
Displaying Modules in the Chassis ............................................................................ 5-5
Management Ethernet Ports ...................................................................................... 5-17
User Ethernet Ports ................................................................................................... 5-18
Standards ............................................................................................................... 5-18
Functional Description ............................................................................................ 5-18
GbE Port Interfaces ............................................................................................ 5-18
Fast Ethernet Port Interfaces ............................................................................. 5-18
Flow Control ...................................................................................................... 5-19
Factory Defaults ..................................................................................................... 5-20
Configuring User Ethernet Port Parameters ............................................................ 5-20
Displaying Ethernet Port Status .............................................................................. 5-21
Testing Ethernet Ports............................................................................................ 5-22
Displaying Ethernet Port Statistics .......................................................................... 5-22
Clearing Statistics ................................................................................................... 5-24
Flows ......................................................................................................................... 5-24
iii
Table of Contents

Ethernet Entities ................................................................................................ 5-25
Aware and Unaware Traffic................................................................................ 5-26
Classifier Profiles ............................................................................................... 5-26
Tagging and Marking .......................................................................................... 5-27
Defining Classifier Profiles ...................................................................................... 5-27
Configuring Flows ................................................................................................... 5-28
Example .................................................................................................................. 5-29
Viewing the Flow Summary ..................................................................................... 5-30
Testing the Flows ................................................................................................... 5-31
5.7 Quality of Service (QoS) ............................................................................................ 5-31
Configuring Policer Profiles ..................................................................................... 5-32
Adding Policer Profiles ....................................................................................... 5-32
Configuring Policer Profiles ................................................................................ 5-32
Example 1............................................................................................................... 5-32
Example 2............................................................................................................... 5-33
5.8 SHDSL Ports............................................................................................................... 5-34
Standards ............................................................................................................... 5-35
Benefits ................................................................................................................. 5-35
SHDSL Transmission Subsystem Structure ......................................................... 5-36
SHDSL Modulation Method ................................................................................ 5-36
SHDSL Transport ................................................................................................ 5-36
Handling of Timeslot 0....................................................................................... 5-37
Management via Embedded Operational Channel (EOC)..................................... 5-37
Single IP Management ....................................................................................... 5-37
Configuring SHDSL Port Parameters........................................................................ 5-38
Testing SHDSL Ports ............................................................................................... 5-43
Local Port Loopback (M8SL only) ....................................................................... 5-43
Remote Port Loopback (M8SL only) ................................................................... 5-44
Remote Loopback on Remote Unit .................................................................... 5-45
Activating SHDSL Loopbacks .............................................................................. 5-45
Displaying SHDSL Port Status ................................................................................. 5-46
Displaying SHDSL Port Statistics ............................................................................. 5-47
Displaying SHDSL Repeater Statistics ..................................................................... 5-50
5.9 PCS Ports ................................................................................................................... 5-52
Standards ............................................................................................................... 5-52
Configuring a PCS Port ............................................................................................ 5-53
Displaying PCS Port Status ...................................................................................... 5-54
Displaying PCS Statistics ......................................................................................... 5-54
5.10 E1 Ports ..................................................................................................................... 5-56
Standards ............................................................................................................... 5-57
Framing ............................................................................................................. 5-57
Interface Type ................................................................................................... 5-58
Receive Signal Attenuation (M8E1 only) ............................................................ 5-58
E1 Payload Processing ....................................................................................... 5-58
Handling E1 Alarm Conditions ............................................................................ 5-59
iv
5.11
5.12
5.13
5.14
Table of Contents
OOS Signaling .................................................................................................... 5-59

Inband Management .......................................................................................... 5-59
Configuring E1 Port Parameters .............................................................................. 5-60
Configuring Internal E1 Port Parameters ................................................................. 5-62
Example 1............................................................................................................... 5-64
Example 2............................................................................................................... 5-65
Example 3............................................................................................................... 5-65
Testing E1 Ports ..................................................................................................... 5-66
CL Modules ........................................................................................................ 5-67
I/O Modules ....................................................................................................... 5-69
Loopback Duration ............................................................................................ 5-76
Activating Loopbacks and BER Tests .................................................................. 5-76
Viewing an E1 Port Status ...................................................................................... 5-78
Displaying E1 Port Statistics ................................................................................... 5-78
T1 Ports ..................................................................................................................... 5-82
Standards ............................................................................................................... 5-83
Framing ............................................................................................................. 5-83
Line Interface (M8T1 only) ................................................................................. 5-83
Line Length........................................................................................................ 5-84
Zero Suppression ............................................................................................... 5-84
Interface Type ................................................................................................... 5-84
Handling of T1 Alarm Conditions ........................................................................ 5-84
T1 Payload Processing ....................................................................................... 5-85
OOS Signaling .................................................................................................... 5-85
Inband Management .......................................................................................... 5-86
Configuring T1 Port Parameters .............................................................................. 5-87
Configuring Internal T1 Port Parameters ................................................................. 5-88
Example 1............................................................................................................... 5-89
Example 2............................................................................................................... 5-90
Example 3............................................................................................................... 5-90
Testing T1 Ports ..................................................................................................... 5-91
CL Modules ........................................................................................................ 5-92
I/O Modules ....................................................................................................... 5-94
Loopback Duration ............................................................................................ 5-96
Activating Loopbacks ......................................................................................... 5-97
Viewing a T1 Port Status ........................................................................................ 5-97
Displaying T1 Port Statistics ................................................................................... 5-97
Signaling Profiles ..................................................................................................... 5-101
Functional Description .......................................................................................... 5-101
Factory Defaults ................................................................................................... 5-102
Configuring CAS Signaling Profiles ........................................................................ 5-102
Example ................................................................................................................ 5-104
HDLC Ports (I/O Modules) ........................................................................................ 5-105
Standards ............................................................................................................. 5-105
Configuring HDLC Ports ........................................................................................ 5-105
MLPPP Ports............................................................................................................. 5-106
Standards ............................................................................................................. 5-106
Configuring MLPPP Ports....................................................................................... 5-107
Table of Contents
Example ................................................................................................................ 5-107

5.15 PPP Ports ................................................................................................................. 5-108
Standards ............................................................................................................. 5-108
Configuring PPP Ports ........................................................................................... 5-109
Example ................................................................................................................ 5-109
5.16 Voice Ports .............................................................................................................. 5-110
Standards ............................................................................................................. 5-111
Configuring External Voice Port Parameters .......................................................... 5-113
Example ................................................................................................................ 5-115
Configuring Internal Voice Port Parameters .......................................................... 5-116
Testing Voice Ports ............................................................................................... 5-116
Local Digital Loopback (Local Loop) ................................................................. 5-116
Remote Digital Loopback (Remote Loop) ......................................................... 5-117
Forward Tone Injection .................................................................................... 5-118
Backward Tone Injection .................................................................................. 5-119
Loopback Duration .......................................................................................... 5-120
Activating Loopbacks and Tone-Inject Tests..................................................... 5-120
Viewing a Voice Port Status .................................................................................. 5-121
5.17 Serial Ports .............................................................................................................. 5-121
Standards ............................................................................................................. 5-123
Configuring Serial Port Parameters ....................................................................... 5-124
Example ................................................................................................................ 5-127
Testing Serial Ports............................................................................................... 5-127
Local Digital Loopback (Local Loop) ................................................................. 5-127
Remote Digital Loopback (Remote Loop) ......................................................... 5-128
Activating the Loopbacks ................................................................................. 5-129
5.18 BRI Ports.................................................................................................................. 5-130
Standards ............................................................................................................. 5-130
Configuring BRI (ISDN) Port Parameters ................................................................ 5-131
Example ................................................................................................................ 5-131
5.19 Serial Bundle Ports................................................................................................... 5-132
Configuring Serial Bundle Port Parameters............................................................ 5-132
Example ................................................................................................................ 5-133
Testing Serial-Bundle Ports ................................................................................... 5-133
Composite Data Stream Remote Digital Loopback ........................................... 5-134
5.20 Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)..................................... 5-135
Standards ............................................................................................................. 5-136
Configuring Optical Link Parameters and Accessing the Remote Unit .................... 5-138
Configuring the Local Optical Link .................................................................... 5-138
Configuring the Remote Optimux ..................................................................... 5-139
vi
5.21
5.22
5.23
5.24
Table of Contents
Example ................................................................................................................ 5-141

Testing Optical Links ............................................................................................ 5-142
Local Loopback on Local Optical Link ............................................................... 5-142
Remote Loopback on Local Optical Link ........................................................... 5-143
Link Local Loopback on Remote Optimux ......................................................... 5-143
Link Remote Loopback on Remote Optimux..................................................... 5-144
Viewing Optical Link SFP Status Information ......................................................... 5-146
SDH/SONET Ports..................................................................................................... 5-147
Standards ............................................................................................................. 5-147
SDH Implementation Principles ........................................................................ 5-148
Direct Multiplexing Approach ........................................................................... 5-148
General Structure of SDH Signals ..................................................................... 5-149
SDH Frame Organization .................................................................................. 5-149
VC Assembly/Disassembly Process ................................................................... 5-150
STM-1 Frame Structure .................................................................................... 5-151
Pointers ........................................................................................................... 5-152
SDH Overhead Data ......................................................................................... 5-153
SDH Tributary Units ......................................................................................... 5-157
SDH Maintenance Signals and Response to Abnormal Conditions .................... 5-160
SONET Environment ......................................................................................... 5-163
SDH/SONET Interfaces ..................................................................................... 5-164
Automatic Laser Shutdown .............................................................................. 5-164
Inband Management Access through SDH/SONET Networks ............................ 5-164
SDH/SONET Hierarchy and Allowed Activities ................................................... 5-166
Factory Defaults (SDH/SONET Parameters) ........................................................... 5-166
Configuring SDH/SONET Link Parameters .............................................................. 5-167
Assigning VC Profiles to AUG/OC-3 ....................................................................... 5-169
Testing SDH/SONET Ports ..................................................................................... 5-170
Remote Loopback on SDH/SONET Link............................................................. 5-171
Local Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5 .............................. 5-171
Remote Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5 .......................... 5-171
Activating Loopbacks ....................................................................................... 5-172
Viewing SDH/SONET Status Information ............................................................... 5-174
Displaying SDH/SONET Statistics........................................................................... 5-176
Clearing Statistics ................................................................................................. 5-181
VC Profiles ............................................................................................................... 5-181
Configuring VC Profiles ......................................................................................... 5-183
Logical MAC Ports .................................................................................................... 5-184
Configuring Logical MAC Ports .............................................................................. 5-185
VCG Ports ................................................................................................................ 5-186
Standards ............................................................................................................. 5-186
Benefits ............................................................................................................... 5-186
Ethernet over SDH/SONET ............................................................................... 5-186
Encapsulation Modes ....................................................................................... 5-187
Link Bandwidth Utilization ............................................................................... 5-187
Support for LCAS ............................................................................................. 5-188
vii
Table of Contents
5.25
5.26
5.27
5.28
5.29
5.30
5.31
5.32
5.33
viii
Configuring VCG Ports .......................................................................................... 5-188

Viewing LCAS Status Information .......................................................................... 5-189
Displaying LCAS Statistics ..................................................................................... 5-191
GFP Ports ................................................................................................................. 5-193
Standards ............................................................................................................. 5-193
Configuring GFP Ports ........................................................................................... 5-193
Displaying GFP Statistics ....................................................................................... 5-194
HDLC Ports (CL.2 Modules) ...................................................................................... 5-196
Standards ............................................................................................................. 5-197
Configuring HDLC Ports ........................................................................................ 5-197
Displaying HDLC Statistics .................................................................................... 5-197
Managers ................................................................................................................. 5-200
Configuring a Manager ......................................................................................... 5-200
Management Access ................................................................................................ 5-200
Configuring Access ............................................................................................... 5-201
SNMP Management .................................................................................................. 5-202
Standards ............................................................................................................. 5-202
Benefits ............................................................................................................... 5-203
SNMP Message Formats ................................................................................... 5-204
The SNMPv3 Mechanism .................................................................................. 5-208
Configuring for SNMP Management ...................................................................... 5-209
Specifying an SNMPv3 Engine .......................................................................... 5-209
Enabling SNMPv3 ............................................................................................. 5-210
Specifying an SNMPv3 User.............................................................................. 5-210
Defining User (Access) Groups ......................................................................... 5-211
Setting up a View ............................................................................................ 5-212
Mapping SNMPv1 to SNMPv3 ........................................................................... 5-213
Configuring Targets ......................................................................................... 5-214
Configuring SNMP Communities for SNMPv1 .................................................... 5-215
Adding SNMPv3 Notification Entries ................................................................. 5-216
Configuring a Notification Filter ....................................................................... 5-217
Configuring a Notification Filter Profile ............................................................ 5-217
Linking User (Access) Groups to an Access Control Policy ................................ 5-218
Authentication via RADIUS Server ............................................................................ 5-218
Standards ............................................................................................................. 5-218
Benefits ............................................................................................................... 5-218
Configuring the RADIUS Server ............................................................................. 5-219
Viewing the RADIUS Server Profile Status ............................................................. 5-220
Viewing RADIUS Statistics ..................................................................................... 5-220
Out-Of-Band Ethernet Control ................................................................................. 5-221
Benefits ............................................................................................................... 5-221
Configuring the Out-Of-Band Management Port ................................................... 5-221
Switched Virtual Interface ........................................................................................ 5-221
Management Bridge ................................................................................................. 5-222
Configuring the Management Bridge .................................................................... 5-224
Table of Contents
Example ................................................................................................................ 5-225

5.34 Management Router ................................................................................................ 5-227
Adding and Configuring Router Interfaces ............................................................ 5-227
Adding a Router Interface ................................................................................ 5-227
Configuring the Router Interface ..................................................................... 5-228
Displaying the Routing Table ................................................................................ 5-229
Configuring Static Routes and Default Gateway ................................................... 5-230
Example ................................................................................................................ 5-231
5.35 Pseudowire Router .................................................................................................. 5-234
Adding and Configuring Router Interfaces ............................................................ 5-236
Adding a Router Interface ................................................................................ 5-236
Configuring the Router Interface ..................................................................... 5-237
Adding and Configuring Remote Peers.................................................................. 5-238
Displaying the Routing Table ................................................................................ 5-239
Configuring Static Routes and Default Gateway ................................................... 5-240
Example 1. Establishing PW Connectivity between HS-12N Module and MPW-1 Fast
Ethernet Port ....................................................................................................... 5-241
Example 2. Establishing PW Connectivity between HS-12N Module and VCG ......... 5-242
5.36 Internal DS1 Ports ................................................................................................... 5-244
Configuring Internal DS1 Port Parameters ............................................................ 5-245
Example ................................................................................................................ 5-245
Testing DS1 Ports ................................................................................................. 5-245
Local Loopback on Selected Internal DS1 Port Timeslots ................................. 5-246
Remote Loopback on Selected Internal DS1 Port Timeslots ............................. 5-246
Activating Loopbacks ....................................................................................... 5-248
5.37 Pseudowires ............................................................................................................ 5-248
Standards ............................................................................................................. 5-249
Pseudowire Packet Processing Subsystem ....................................................... 5-250
PSN Configuration Parameters ......................................................................... 5-253
Pseudowire QoS/CoS ....................................................................................... 5-253
ToS .................................................................................................................. 5-254
Jitter Buffer ..................................................................................................... 5-254
Adaptive Timing ............................................................................................... 5-255
OAM Protocol .................................................................................................. 5-256
Configuring Pseudowires ...................................................................................... 5-257
Examples .............................................................................................................. 5-263
Displaying PW Statistics ........................................................................................ 5-263
Viewing the Pseudowire Status and Summary ...................................................... 5-268
5.38 Cross-Connections ................................................................................................... 5-269
Cross-Connect Types ....................................................................................... 5-271
Timeslot Types ................................................................................................ 5-271
Full Timeslot versus Split Timeslot Assignment (Split Timeslot Cross-Connect) . 5-272
Bidirectional Transfer Mode ............................................................................. 5-272
Unidirectional Broadcast Function ................................................................... 5-272
Configuring a DS0 Cross-Connection .................................................................... 5-273
Examples .............................................................................................................. 5-275
ix
Table of Contents
5.39
5.40
5.41
5.42
5.43
Example 1. Bidirectional DS0 Cross-Connect: CL <-> I/O Modules, Single Timeslot . 5275
Example 2. Consecutive Timeslot Assignment: E1/T1/E1-i/T1-i Port <-> Serial
Module Port ..................................................................................................... 5-276
Example 3. Consecutive Timeslot Assignment: Two E1/T1/E1-i/T1-i I/0 Module Ports
........................................................................................................................ 5-276
Example 4. Unidirectional Broadcast: M8E1 Port is Sending Data to three M8E1
ports using UniRx............................................................................................. 5-276
Example 5. Unidirectional Broadcast: Voice Port is Sending Data to M8E1 Port using
UniTx ............................................................................................................... 5-276
Example 6. Unidirectional Broadcast: Serial Port is Sending Data to M8E1 Port using
UniTx ............................................................................................................... 5-277
Configuring a TDM Cross-Connection .................................................................... 5-277
Examples .............................................................................................................. 5-277
Example 1 ........................................................................................................ 5-277
Example 2 ........................................................................................................ 5-278
Configuring a Split Timeslot Cross-Connection ...................................................... 5-278
Example ................................................................................................................ 5-279
Configuring an SDH/SONET Cross-Connection....................................................... 5-280
Examples .............................................................................................................. 5-281
Example 1. Direct Transparent Mapping of E1 Links over SDH .......................... 5-281
Example 2. Mapping Framed E1 Link Payload to VC-12 Container..................... 5-282
Configuring a PW-TDM Cross Connection .............................................................. 5-282
Example ................................................................................................................ 5-283
Fault Propagation .................................................................................................... 5-283
Configuring Fault Propagation .............................................................................. 5-285
APS Protection ......................................................................................................... 5-286
Standards ............................................................................................................. 5-287
Configuring Automatic Protection Switching ......................................................... 5-288
Adding and Removing an APS Group ................................................................ 5-288
Binding Ports to an APS Group ......................................................................... 5-289
Viewing the Status of an APS Group ..................................................................... 5-291
Example ................................................................................................................ 5-292
Path Protection for SDH/SONET Payload .................................................................. 5-292
Configuring VC Path Protection ............................................................................. 5-293
Adding and Removing a VC Path Protection Group ........................................... 5-293
Binding Ports to a VC path Protection Group ................................................... 5-293
Viewing the Status of a VC Path Protection Group ................................................ 5-294
Example ................................................................................................................ 5-294
LAG Protection......................................................................................................... 5-295
LAGs Benefits ....................................................................................................... 5-295
Configuring the LAG ............................................................................................. 5-296
Displaying the LAG Status..................................................................................... 5-297
Displaying the LAG Statistics ................................................................................ 5-298
Ethernet Group Protection ....................................................................................... 5-298
Standards ............................................................................................................. 5-298
Configuring Ethernet Protection Group ................................................................. 5-300
Adding and Removing an Ethernet Protection Group ....................................... 5-300
5.44
5.45
5.46
5.47
5.48
5.49
Table of Contents
Binding Ports to an Ethernet Protection Group ................................................ 5-301

Example ................................................................................................................ 5-301
Viewing the Status of an Ethernet Protection Group ............................................ 5-303
TDM Group Protection ............................................................................................. 5-303
Benefits ............................................................................................................... 5-304
Standards ............................................................................................................. 5-304
Dual Cable (Parallel TX) Protection ................................................................... 5-305
Y-Cable Protection ........................................................................................... 5-306
Working and Protection Port Parameters ......................................................... 5-307
Protection Mode .............................................................................................. 5-307
Configuring TDM Group Protection ....................................................................... 5-307
Example 1............................................................................................................. 5-308
Example 2............................................................................................................. 5-308
Example 3............................................................................................................. 5-309
TDM Ring Protection ................................................................................................ 5-310
Benefits ............................................................................................................... 5-310
Standards ............................................................................................................. 5-310
Configuring TDM Ring Protection .......................................................................... 5-313
Example ................................................................................................................ 5-314
Clock Selection ........................................................................................................ 5-314
Standards ............................................................................................................. 5-314
Clock Synchronization ...................................................................................... 5-315
System Timing Modes ...................................................................................... 5-316
Configuring the Clock Domain............................................................................... 5-319
Displaying the Clock Domain Status ...................................................................... 5-320
Configuring the Clock Sources .............................................................................. 5-320
Displaying the Clock Source Status ....................................................................... 5-322
Configuring the Station Clock ............................................................................... 5-322
Displaying the Station Clock Status ...................................................................... 5-323
Configuring the Recovered Clock .......................................................................... 5-323
Displaying the Recovered Clock Status ................................................................. 5-324
Date and Time ......................................................................................................... 5-325
Setting the Date and Time ................................................................................... 5-325
Example ................................................................................................................ 5-326
Displaying the Date and Time ............................................................................... 5-326
User Access Levels ................................................................................................... 5-326
Defining Users and Passwords.............................................................................. 5-326
Example ................................................................................................................ 5-327
Viewing Connected Users ..................................................................................... 5-328
Administration ......................................................................................................... 5-328
Specifying Administrative Information .................................................................. 5-328
Managing the SONET/SDH Link Rate Selection License ......................................... 5-329
Checking the License Availability ...................................................................... 5-329
Ordering the License ....................................................................................... 5-330
Downloading the License File Using TFTP ......................................................... 5-331
Downloading the License File Using XModem .................................................. 5-332
Installing the License for Redundant CL Modules ............................................. 5-332
File Operations ..................................................................................................... 5-332
xi
Table of Contents
File Names in the Unit ..................................................................................... 5-332

Copying Files within Megaplex-4100 ................................................................ 5-333
Displaying Files within Megaplex-4100 ............................................................. 5-335
Deleting Files ................................................................................................... 5-335
Saving the Configuration ................................................................................. 5-336
Resetting Megaplex-4100 ..................................................................................... 5-336
Resetting to Factory Defaults .......................................................................... 5-336
Resetting to User Defaults .............................................................................. 5-336
Rebooting the Megaplex-4100 Chassis ............................................................ 5-337
Rebooting the Module ..................................................................................... 5-337
Chapter 6. Monitoring and Diagnostics
6.1
6.2
6.3
6.4
6.5
Detecting Problems ..................................................................................................... 6-1

Indicators ................................................................................................................. 6-1
Alarms and Traps ...................................................................................................... 6-2
Statistic Counters ..................................................................................................... 6-2
Configuration Error Messages ................................................................................... 6-2
Handling Events ......................................................................................................... 6-20
Alarm Buffer ........................................................................................................... 6-20
Alarm Relays........................................................................................................... 6-21
Working with the Alarm and Event Logs ................................................................. 6-21
Example 1: Displaying Active Alarms .................................................................. 6-22
Example 2. Displaying Active Alarms Details ....................................................... 6-22
Example 3: Displaying Information of LOF alarm on SDH/SONET port................. 6-23
Example 4. Alarm Log ........................................................................................ 6-23
Example 5. Alarm List ......................................................................................... 6-24
Alarm, Event and Trap Lists .................................................................................... 6-25
Alarm List .......................................................................................................... 6-25
Event List........................................................................................................... 6-29
Trap List ............................................................................................................ 6-31
Troubleshooting ........................................................................................................ 6-37
Preliminary Checks.................................................................................................. 6-37
Troubleshooting Procedure .................................................................................... 6-38
Performing Diagnostics Tests..................................................................................... 6-40
Performing a Ping Test ........................................................................................... 6-40
Running Diagnostic Loopbacks ............................................................................... 6-40
Technical Support ...................................................................................................... 6-45
Appendix A. Connection Data

Appendix B. I/O Modules
xii
Chapter 1
Introduction
1.1
Overview
RADs Megaplex-4100 multiservice, next generation access node, a high-capacity,

carrier-class multiservice concentrator, transports traffic over fiber or copper and
provides multiple Legacy and next-generation services on PDH/SDH/SONET or
packet-switched networks (PSN) for large enterprises, including utilities,
transportation and campuses, as well as for carriers and service providers.
The Megaplex-4100 multiservice access node is an efficient and cost-effective
device for integrating various data interfaces, rates and user services. These
include Fast Ethernet and Gigabit Ethernet as well as low speed sub-64 kbps
data, serial n x 64 kbps data, high speed data (up to 2 x STM-4/OC-12 per CL.2),
digital voice, analog voice, ISDN and additional industry specific interfaces.
When deployed as a carrier-class TDM and Ethernet aggregator, Megaplex-4100
can terminate Ethernet traffic carried over E1/T1/SHDSL/SHDSL.bis/fiber links or
native Ethernet copper and fiber, as well as through a VCG in the SDH/SONET
circuits. This traffic can then be switched either to a different PDH/TDM trunk or
to the Fast Ethernet or Gigabit Ethernet ports. The next-generation concentrator
also features an internal TDM cross-connect matrix of up to 8384 DS0 and 1504
DS1, enabling it to cross-connect traffic directly from one channel to another.
As a high-capacity multiservice concentrator, Megaplex-4100 provides access over
PDH/SDH/SONET transport networks. This functionality can be used by large
organizations with SDH/SONET backbones that require an efficient way to
transport and provision multiple legacy and next generation services over their
high capacity pipes.
Handling a broad range of Ethernet, data and voice services and various network
technologies in a single compact managed node, makes Megaplex-4100 a
versatile and cost-effective next-generation multiservice access node solution.
Product Options
SDH/SONET Interface
Two SDH/SONET ports located on the CL.2 modules can be ordered in two
versions:
STM-1/OC-3 only, with software key license upgrade if required
Software-configurable to STM-4/OC-12 or STM-1/OC-3, with software key

license built-in.
Overview
1-1
Chapter 1 Introduction
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical.
GbE Interface
The GbE ports can be ordered with one of the following interfaces:
10/100/1000BASE-T (UTP) copper ports. This type of ports support autonegotiation, with user-specified advertised data rate (10, 100 or 1000 Mbps)
and operating mode (half- or full-duplex).
SFP sockets, for installing SFP plug-in modules.
Power Supply
Megaplex-4100 can be ordered with AC (115 or 230 VAC nominal) or DC (24 or
-48 VDC nominal) power supply modules. It can also be ordered with one power
supply module, or with two power supply modules, for redundancy. The DC
modules can be ordered with selectable ground reference or floating ground.
Applications
Central Solution for RAD CPE Devices
Megaplex-4100 offers a complete, end-to-end solution as a central aggregation
platform for diverse CPE devices managed together under RADview.
Megaplex-4100 is interoperable with DXC, MP-2100/2104, FCD, ASMi, Optimux, as
well as ETX, RICi and IPMUX family devices.
Figure 1-1 illustrates Megaplex-4100 as a central site solution, Ethernet and TDM
aggregator for SDH/SONET and PSN networks.
1-2
Overview
Figure 1-1. Megaplex-4100 as a Central Site Solution, Ethernet and TDM

Aggregator for SDH/SONET and PSN Networks
TDM and Ethernet Multiservice Access

Enterprises, campuses and utility companies can deploy Megaplex-4100 as a core
or an edge device to create a diversity of STM-1/STM-4/OC-3/OC-12 rings,
multiplexing voice, fax, data, and other low speed traffic. Megaplex-4100 can also
groom and cross-connect between channels and terminate Ethernet traffic.
Megaplex-4100 can work with industry-specific devices, such as Teleprotection
and Omnibus units (see Figure 1-2).
Overview
1-3
Figure 1-2. Megaplex-4100 as Multiservice Platform for Transportation and Power Utilities
Smooth Migration from TDM to PSN

Megaplex-4100 equipped with the MPW-1 module provides legacy services over
packet-switched networks (PSN). The MPW-1 module converts the data stream
from other modules in the MP-4100 chassis (E1/T1, SHDSL, data or voice ports)
delivered by the internal Megaplex backplane via MPW-1s internal DS1 ports into
IP or MPLS packets for transmission over Ethernet, IP or MPLS networks. The
ASIC-based architecture provides a robust and high performance pseudowire
solution with minimal processing delay. MPW-1 supports various legacy services
over packet transport types, including TDMoIP, CESoPSN, SAToP, HDLCoPSN (see
Figure 1-3).
1-4
Overview
Figure 1-3. Migrating TDM and Ethernet Services from SDH/SONET to PSN
Features
PDH Access
Megaplex-4100 delivers PDH Access at E1/T1 and fractional E1/T1 level with up to
160 E1/T1 ports per chassis over copper or fiber, including access over
2-wire/4-wire SHDSL, with up to 80 SHDSL ports per chassis.
Data Services
Megaplex-4100 provides up to 120 multichannel sub-DS0 low speed data,
64-kbps codirectional G.703 channels, teleprotection channels, multichannel ISDN
access (up to 120 ISDN U and/or S type ports per chassis), and n64 kbps
high speed data (up to 2.048 Mbps for E1 environments, or up to 1.544 Mbps for
T1 environments).
Voice Services
Voice services are provided by analog and digital voice modules (up to 4800 voice
channels per chassis for E1 ports, up to 3840 voice channels for T1 ports), with
support for special services such as omnibus and party lines. Voice channel
processing can include user-defined signaling translations.
SDH/SONET Services
SDH/SONET services are provided by up to 4 separately configurable STM-1/STM4 or OC-3/OC-12 links per node, with support for APS (Automatic Protection
Switching) for line redundancy.
Overview
1-5
Ethernet Layer 2 Services

Ethernet Layer 2 services are supported by up to 30 10/100 Mbps Ethernet ports
on I/O modules, and 4 GbE ports on CL modules. Up to three separately
configurable Ethernet ports are available per I/O module; each CL module has two
GbE ports, for up to four separately configurable GbE ports per chassis.
Megaplex-4100 can provide Ethernet traffic termination for transport over E1, T1,
SHDSL uplinks, virtually concatenated group uplinks and high and low-order
SDH/SONET VC-12/VC1.5 virtual containers. It can also serve as Ethernet access
concentrator with GbE uplinks.
Flexible Ethernet Transport

Flexible Ethernet transport options over TDM links provide full support for
Ethernet services over existing TDM infrastructures with efficient bandwidth
utilization for each type of application, and also enable cost-effective migration
to packet switched transport. The available Ethernet transport options include:
HDLC bundles with selectable number of timeslots over individual external E1

and T1 links, and internal PDH ports of the SDH/SONET subsystem
Wideband, multilink MLPPP bundles over E1 links, with a bandwidth of up to

16.384 Mbps (the equivalent of eight E1 links)
Virtually concatenated groups over SDH/SONET links, with selectable

granularity down to VC-12/VT1.5/VC-3/VC-4/STS-1/STS-3C, Megaplex-4100
performs low-order and high-order virtual concatenation, including GFP
encapsulation per ITU-T Rec. G.7041 or LAPS per ITU-T Rec. X.85/X.86. For
reliable transmission, Megaplex-4100 also supports LCAS per ITU-T Rec.
G.7042.
TDM pseudowire (PW) circuit emulation for E1 and T1 over IP and MPLS
packet-switched networks. Megaplex-4100 complies with the emerging
pseudowire edge-to edge emulation (PWE3) standards, including TDMoPSN,
HDLCoPSN, CES and SAToP, and therefore it is compatible with other
pseudowire equipment offered by RAD, such as Gmux-2000 Pseudowire
Gateways, the IPmux family of TDM Pseudowire Access Gateways, as well as
with previous generations of Megaplex equipment with IP main link modules.
Fiber Multiplexing
Megaplex-4100 also features multiport fiber multiplexing modules, for
transporting 4 or 16 E1 or T1 streams, together with Ethernet traffic of up to
100 Mbps, over proprietary fiber optic links to compatible standalone units
offered by RAD for use at customers premises.
DS0 Cross-Connect
Megaplex-4100 features an internal DS0 cross connect matrix of up to 8384
channels. Traffic from any channel can be cross-connected directly to any other
channel.
These capabilities enable Megaplex-4100 to function as a service differentiation
point at the headquarters, handing off traditional voice and data services to the
transport network.
1-6
Overview
At the remote offices or customer premises, Megaplex-4100 may also be

deployed to effectively fan out multiple voice and data services.
Protection
The modular, distributed architecture of Megaplex-4100 enables redundancy at
different levels of the network and provides a resilient system with no single
point of failure. Hardware redundancy is provided through an optional redundant
power supply and CL modules, with switchover to the backup CL links within
50 msec.
Each combined common logic, cross-connect matrix and broadband link module
(CL) provide automatic switchover between each two STM-1/STM-4/OC-3/OC-12
links within 50 msec, for 1+1 protection against hardware, network or cable
failure. The SDH/SONET employs APS 1+1 protection as well as Subnetwork
connection protection (SNCP for SDH and UPSR for SONET) for path protection.
The Ethernet GbE ports feature LAG- and VCG-based link protection mechanism
over SDH/SONET. In addition, any E1/T1 stream can be protected using various
mechanisms over any interface.
Selected I/O modules can also be configured for redundancy and can be
hot-swapped, allowing for continuous service.
For more detailed information about different redundancy types, refer to the
following:
CL redundancy Common Logic (CL.2) Modules in this chapter
PS redundancy Power Supply (PS) Modules in this chapter
APS Automatic Protection Switching section in Chapter 5
Path protection Path Protection for SDH/SONET Payload section in

Chapter 5
I/O module redundancy TDM Ring Protection and TDM Group Protection
sections in Chapter 5
Ethernet protection Configuring the LAG section in Chapter 5
Ethernet group (VCG-based) protection Ethernet Group Protection section

in Chapter 5.
Diversity of Rings
In addition to supporting standard SDH/SONET rings, Megaplex-4100 can be used
to create E1, T1, TDM over SHDSL, TDM over fiber, or a mix of ring topologies. For
more detailed information, refer to TDM Ring Protection section in Chapter 5.
Megaplex-4100 provides a perfect solution in combining low-rate service
provisioning and ring protection.
Modularity and Flexibility

Megaplex-4100 is available as a 4U-high chassis providing slots for up to 2 AC or
DC power supplies, 2 common logic and 10 I/O modules. This allows for a pay as
you grow approach and enables Capex optimization.
Overview
1-7
Next-Generation ADM/Terminal
STM-1/STM-4/OC-3/OC-12 network owners can extend the use of existing ADM
equipment or terminal multiplexers, saving replacement or expansion costs, by
implementing VCAT protocols to carry the Ethernet traffic in a more efficient way
and minimize wasted bandwidth.
Megaplex-4100 performs STM-1/STM-4/OC-3/OC-12 add/drop multiplexing for
grooming LAN and TDM traffic over SDH/SONET networks. Ethernet traffic can be
mapped into n x VC-12/VC-3/VC-4 or n x VT1.5/STS-1/STS-3C virtual containers.
Megaplex-4100 brings Ethernet economics and packet-switching efficiency to
existing SDH/ SONET/TDM infrastructures. It thereby enables utilities and other
private fiber network owners to reduce both Opex and Capex as they use their
optical bandwidth for reselling revenue generating Ethernet services. New
business opportunities can be created by leveraging existing equipment to
support clear channel data streams and the latest high bandwidth services.
Megaplex-4100 eliminates the need for two separate units (ADM and multiplexer)
for private networks where voice, Ethernet and data services are required. As
shown in Figure 1-5, the Megaplex-4100 chassis has 14 slots (2 for PS modules,
2 for CL modules, and 10 for I/O modules). These slots are interconnected by
means of a bus subsystem located on the backplane.
Timing
Flexible timing options enable reliable distribution of timing together with flexible
selection of timing sources, including external station clock for daisy-chaining the
clock signals to other equipment. Megaplex-4100 also provides traceable timing
quality and supports automatic selection of best-quality timing reference.
Megaplex-4100 timing is fully redundant, i.e., each CL module has its own timing
subsystem, and can supply all the clock signals required by the system via the
chassis timing bus. However, at each time, only one CL module (the active
module) actually drives the timing bus, while the other (standby) module is
disconnected from the bus, but continuously monitors the state of the main
module timing subsystem. If a problem is detected in the active timing
subsystem, the standby subsystem hitlessly takes over.
The user can define the following clock sources:
Recovered from the STM-1/STM-4/OC-3/OC-12 interface, including automatic

selection, based on SSM (Synchronization Status Messaging)
Internal crystal free-running oscillator-based clock
Derived from the receive clock of a specified module user port
ACR Adaptive clock recovered from a pseudowire circuit
External station clock.
Multiple clock sources can be set and assigned corresponding quality and priority.
Megaplex-4100 uses the highest quality stratum available, determined by
monitoring the synchronization status messages (SSM) of the configured
SDH/SONET clock sources.
1-8
Overview
For detailed information about the different system timing modes, refer to the
following sources:
Clock Selection in Chapter 5
Relevant I/O module section in Appendix B.
Management
Megaplex-4100 offers carrier-class service provisioning features, including
end-to-end path management, to ensure continuous service availability.
Advanced SNMP management capabilities provide control and monitoring of all
network elements: SDH/SONET access and ring units as well as remote POP and
Last Mile broadband access feeders and CPEs.
Complete control over the Megaplex-4100 functions can be attained via the
following applications:
CLI-driven terminal utility for management via a local ASCII-based terminal

connection (see Working with Terminal in Chapter 4 and Terminal Control in
Chapter 5). Telnet access is supported via IP-based connection.
RADview-EMS RADs CORBA-based element management system, providing

a dedicated PC/Unix-based GUI for controlling and monitoring the unit from a
network management station. It also includes northbound CORBA interface
for integration into any third-party NMS (network management system). For
more information, refer to the RADview-EMS User's Manual.
For more information about configuration alternatives, refer to Management
Alternatives in Chapter 4.
The unit can be managed by and report to up to 10 different users
simultaneously. Accounts of existing and new users can be defined/changed
remotely, using a dedicated RADIUS server as explained under Authentication via
RADIUS Server in Chapter 5.
A wide range of inband and out-of-band management options provide
organizations with the means needed to integrate the equipment within the
organizational management network, as well as transfer their management traffic
seamlessly through the Megaplex-4100-based network.
Remote units can be managed in the following ways:
Out-of-band, using the 10/100 Ethernet management port (for more

information, see Out-Of-Band Ethernet Control in Chapter 5)
Inband, using IP/PPP or IP/HDLC over DCC, via the STM-1/STM-4/OC-3/OC-12

links (for more information, see SDH/SONET Ports in Chapter 5)
Inband, using the IP/PPP or IP/FR over a dedicated timeslot in any E1/T1 or
SHDSL link (for more information, see the description of a relevant port in
Chapter 5, for example, Configuring E1 Ports).
Inband, via any of the user Ethernet ports (see Configuring Flows in
Chapter 5)
Via a network management station running RADview, RADs SNMP element

management application.
Overview
1-9
Databases and scripts of commonly used commands can be easily created and
applied to multiple units using command line interface.
Software upgrades can be downloaded to CL and selected I/O modules. Preset
configuration files can be downloaded/uploaded to/from Megaplex-4100 via TFTP.
For more information and instructions, refer to Chapter 6.
Diagnostics
When a problem occurs, Megaplex-4100 offers a set of diagnostic functions that
efficiently locate the problem (in the Megaplex-4100 chassis, one of I/O modules,
a connecting cable, or external equipment) and rapidly restore full service.
The diagnostic functions are based on the activation of loopbacks at various
ports. These loopbacks enable identifying whether a malfunction is caused by
Megaplex-4100 or by an external system component (for example, equipment,
cable, or transmission path connected to the Megaplex-4100). A detailed
description of the test and loopback functions is given in Chapter 6, under the
corresponding section (for example, E1 Ports, SHDSL Ports).
Comprehensive diagnostic capabilities include:
Local and remote loopbacks
Real-time alarms to alert the user on fault conditions
SDH/SONET link monitoring
Ethernet traffic counters
E1/T1, SHDSL and Optical interface status monitoring.
Alarm Collection and Reporting

Megaplex-4100 continuously monitors critical signals and signal processing
functions. If a problem is detected, the Megaplex-4100 generates time-stamped
alarm messages. The time stamp is provided by an internal real-time clock.
For continuous system monitoring, the user can monitor alarm messages through
the supervisory port. Alarm messages can also be automatically sent as traps to
user-specified network management stations.
The alarms can be read on-line by the network administrator using a Telnet host, an
SNMP-based network management station, or a supervision terminal.
Note
Megaplex-4100 can also monitor one external sense input, and will report its
activation as any other internally-detected alarm.
In addition to the alarm collection and reporting facility, the Megaplex-4100 has
two alarm relays with floating change-over contacts: one relay for indicating the
presence of major alarms and the other for minor alarms. Each relay changes
state whenever the first alarm is detected, and returns to its normal state when
all the alarms of the corresponding severity disappear. The relay contacts can be
used to report internal system alarms to outside indicators, e.g., lights, buzzers,
bells, etc., located on an alarm bay or remote monitoring panel.
1-10
Overview
Performance Monitoring
Megaplex-4100 collects statistics per physical port and per connection for
15-minute intervals, which enables the network operator to monitor the
transmission performance and thus the quality of service provided to users, as
well as identify transmission problems. Performance parameters for all the active
entities are continuously collected during equipment operation.
Statistics for the last 24 hours are stored in the device and can be retrieved by
the network management station. For additional information, refer to the
Statistics section for the relevant port (for example Viewing Ethernet Port
Statistics under Ethernet Ports).
Megaplex-4100 maintains a cyclic event log file that stores up to 256
time-stamped events. In addition, an internal system log agent can send all
reported events to a centralized repository or remote server. For additional
information, refer to Alarms and Traps in Chapter 6.
Security
User access to Megaplex-4100 is restricted via user name and password. For
more information, refer to Management Access Methods in Chapter 4.
Telnet-like management can be secured using a Secure Shell (SSH) client/server
program. Instead of sending plain-text ASCII-based commands and login requests
over the network, SSH provides a secure communication channel.
In addition, Megaplex-4100 supports SNMP version 3, providing secure access to
the device by authenticating and encrypting packets transmitted over the
network. For more information, refer to The SNMPv3 Mechanism in Chapter 5.
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network. For more information, refer to Authentication via RADIUS Server
Mechanism in Chapter 5.
1.2
New in this Version
Major Version Update

The following new functionalities have been added to version 3.0 since version
2.1:
STM-4/OC-12: configurable SDH/SONET ports for up to STM-4/OC-12
Transparent E1/T1 over SDH/SONET: mapping up to 160 E1/T1 streams over

SDH/SONET in a transparent mode including timing
Increased Ethernet over SDH/SONET capacity: encapsulating up to

2*622 Mbps of Ethernet over SDH/SONET using 32 VCG per CL.2
Command Line Interface: redesigned control interface that allows

configuration file text editing, scripting and automation
New in this Version
1-11
ASMi-54C/N module: Transmission of Ethernet and E1 over SHDSL.bis module

working with ASMi-52, ASMi-52L, ASMi-54 or ASMi-54L standalone modules
ACM module: support for MP-2100/2104 alarm relay module adding

4 outbound switches and 8 inbound sensors to Megaplex-4100 alarm control.
Minor Version Update

The following new functionalities have been added to version 3.06 since version
3.00:
TDM ring functionality: Low-capacity resilience E1/T1 ring for mission-critical

services such as Tetra backhauling
SDH/SONET license: license-based STM-4/OC-12 port activation
SHDSL repeaters: Remote management of SHDSL repeaters (S-RPT) via

ASMi-54C/N module
Remote power feeding for SHDSL lines: Remote power feeding control
(phantom) of 4-wire SHDSL lines via the ASMi-54C/ETH/E1/UTP/N module
(from the new MPF standalone power feeding device)
Enhanced ASMi-54C/N diagnostics: Enhanced local and remote loopbacks and

BER tests on the ASMi-54C/N module for improved service monitoring and
fault detection.
1.3
Physical Description
System Structure
Megaplex-4100 units use a modular chassis. The chassis has physical slots in
which modules are installed by the user to obtain the desired equipment
configuration.
Megaplex-4100 configuration includes the following main subsystems:
I/O subsystem, provides interfaces to the users equipment. The number of

user interfacing modules that can be installed in a chassis is up to 10
Multiplexing, timing and control subsystem, located on the common logic and
cross-connect (CL.2) modules.
Power supply subsystem, located on the power supply (PS) modules
Chassis. The main function of the chassis is to provide interconnections

between the various modules, and in particular to connect between the user
interfacing (I/O) modules, and the CL modules that provide the multiplexing
function and the optional connections to SDH/SONET and/or Ethernet
networks.
CL and PS modules are always installed in their dedicated chassis slots, whereas
the user interfacing modules can be installed in any of the other chassis slots
(called I/O slots).
1-12
Any operational Megaplex-4100 system must include at least one CL module and
one PS module. These modules are thus referred to as system modules. User
interfacing modules, called I/O modules, are added to this basic configuration.
Megaplex-4100 system modules are critical components, because a failure in any
one of these modules could disable the whole system, whereas a failure in an I/O
module affects only a small part of the system, and can be generally overcome by
using alternate routes, putting unused capacity into service, etc. Therefore, in
most applications Megaplex-4100 units should be equipped with an additional
redundant system module of each type. Redundancy is also available for the
network interfacing subsystems.
The Megaplex-4100 system is designed to automatically put a redundant module
or subsystem in service in case the corresponding system component fails,
thereby ensuring continuous system operation in the event of any single module
failure. Moreover, redundant modules may be inserted or removed even while the
system operates.
Equipment Description
Figure 1-4 shows a general view of the Megaplex-4100 enclosure.
Megaplex-4100 is built in a 4U-high enclosure that is intended for installation in
19 and 23 racks, using brackets attached to the sides of the enclosure, near the
front or rear panel. Thus, a Megaplex-4100 can be installed in accordance with the
specific requirements of each site, either with the Megaplex-4100 front panel
toward the front of the rack (per ETSI practice), or with the module panels
toward the front (per ANSI practice).
System status indicators are located on both the front panels and on the CL
module panels. Additional indicators are located on the module panels. The cable
connections are made directly to the module panels.
1-13

10 I/O Modules
2 CL Modules
2 PS Modules
Figure 1-4. Typical Megaplex-4100 Enclosure, General View

Figure 1-5 shows a typical rear view of the Megaplex-4100 enclosure that
identifies the slots and their utilization. The enclosure has 14 slots:
Slot
Two slots are reserved for power supply (PS) modules
Two slots are reserved for CL modules
The other 10 slots, arranged in two groups of 5 each, are intended for I/O
modules. Each I/O slot can accept any type of I/O module.
PS-A
PS-B
PS-A
IO-1 IO-2
PS-B
I/O 1
PS/AC
PS/DC
PS/DC
PS/DC
L
I
N
K
I/O 3
I/O 4
CL-A
HS-R/N
CH.
LOC
E
CH-1 CH-1
M
REM
LOC
E
CH-2 CH-2
CH
4-6
CH
1-3
TST
LINK
1-8
LASER
CLASS
1
24V
+72V
RTN
ON
-48V
100-120VAC
S
D
H 1
/
S
O
N
E 2
T
CH.
1-2
200-240VAC
ACT
LINK
E
T
H
1
Rx
ACT
Rx
LINK
LINK
Tx
ACT
Tx
ON
PS Slots
E
T
H
2
E
T
H
3
CH-6
CH
10-12
CH
7-9
ON
LINE
ACT
G
b
E
2
C
O
N D
T C
R E
O
L
REM
LOC
LINK
E
T
H
C
O
N D
T C
R E
O
L
CH.
3-4
CH-8
REM
I/O Slots
IO-9 IO-10
I/O 9
I/O 10
ASMi-54C
OP-34C
OP-106C
A
L
A
R
M
C
L
O
C
K
LINK
ON/LOS
A
L
A
R
M
S
H
D
S
L
.
b
I
s
T
HO
LINK/
ACT
E
T
H
LINK
1-8
LINK/
ACT
O
P
E A
P
B
100
100
ACT
1
LASER
CLASS
1
LASER
CLASS
1
LINK
ACT
L
I
N
K
ACT
ETH2
ON
LINE
ACT
E
T
H
CH-7
REM
LOC
LINK
ETH1
2
LINK
ACT
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
G
b
E
REM
LOC
LASER
CLASS
1
Rx
72V
Tx
ON LINE
ALM
LOS
CH-5
IO-8
I/O 8
M8E1
LASER
CLASS
1
ON LINE
LOC
MPW-1
IO-7
I/O 7
STATUS
REM
VDC-IN
I/O 6
CL-2
CL-2
CH-4 CH-4
IO-6
CL-B
LOS
CH-3 CH-3
REM
LOC
CL-B
CL-A
REM
LOC
VDC-IN
I/O 5
VC-4/Omni
E&M
VC-8/RJ
FXS
HS-12/N
RS-232
M8E1
STATUS
IO-4 IO-5
IO-3
I/O 2
C
L
O
C
K
ON/LOS
E
T
H
1
E
T
H
2
E
T
H
3
LOSS
L
I AIS
N
LOSS
LINK K
ACT
E
T
H
2
LASER
CLASS
1
ACT
E
T
H
1
O
P
A
2
LASER
CLASS
1
ACT
1
E
T
B H
O
P
B
L
I
N
3 K
AIS
LOSS
LINK
LINK
ACT
E
T
H
3
LINK
CL Slots
I/O Slots
Figure 1-5. Megaplex-4100 Enclosure, Typical Rear View
1-14
I/O Modules
Table 1-1 lists the I/O modules currently offered for the Megaplex-4100 in the
alphabetical order of their names. Contact RAD Marketing for information on
additional modules that may be available for your specific application
requirements.
Table 1-1. Megaplex-4100 I/O Modules

Megaplex2100/2104
Compatible
Module
Description
ACM
Alarm and diagnostics module with four outbound relays for reporting
internal alarms to outside indicators such as bells, buzzers, etc. Eight
inbound sensors enable external alarms or conditions to be reported to
the Megaplex system.
ASMi-54C
No
Eight-port SHDSL.bis module with two Ethernet ports, for transporting
digital data to customer premises over the existing copper infrastructure
of the distribution network while eliminating the need for repeaters. It
multiplexes Ethernet over 1, 2, and 4 pairs of SHDSL.bis copper lines. Each
SHDSL port can operate in a link with an ASMi-54/ASMi-54L standalone
unit offered by RAD.
Yes
Has eight independently configurable SHDSL.bis external ports for SHDSL

services, and two 10/100 Mbps Ethernet ports, for packet-based services.
Can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R) SHDSL.bis
Terminal Unit for up to 8 ASMi-54 standalone devices or another ASMi54C module.
ASMi-54C/N
No
Eight-port SHDSL.bis modules with eight E1 and two optional Ethernet
ports, for transporting digital data to customer premises over the existing
copper infrastructure of the distribution network, while eliminating the
need for repeaters. Transparently forward E1 data and optionally
Ethernet, over 1 or 2 pairs of SHDSL.bis/SHDSL copper lines to
ASMi-54/ASMi-54L (SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone
modems on the remote site.
Have eight independently configurable SHDSL.bis external ports for SHDSL
services, eight E1 ports for E1 services and two optional 10/100 Mbps
Ethernet ports, for packet-based services.
HS-6N,
HS-12N
High-speed data module, providing 6, respectively 12, high-speed V.35 or

RS-530/V.11 data channels. Channel data rates are user-selectable in the
range of n56 kbps or n64 kbps, where n is up to 24 for T1 operation,
and up to 31 for E1 operation (maximum 1984 kbps).
Yes
Supports enhanced clock modes. Any channel can be directed to any E1

or T1 link or internal PDH port.
HS-703
High-speed data sub-channel module, providing four 64-kbps

codirectional ITU-T Rec. G.703 data channels.
Yes
1-15

Megaplex2100/2104
Compatible
Module
Description
HS-RN
Low-speed data module, providing 4 synchronous or asynchronous data

Yes
channels with ITU-T Rec. V.24/EIA RS-232 interfaces, each operating at an
independently selectable data rate in the range of 0.6 kbps up to
38.4 kbps in the asynchronous mode, and up to 64 kbps in the
synchronous mode. End-to-end control signals are also supported.
Available in two models:
HS-RN: employing proprietary, HDLC-based, rate adaptation for

performance optimization with respect to either bandwidth or latency,
in accordance with user configuration
HS-RN/V.110: employing V.110 rate adaptation, fully compatible with

the old HS-R module. Enables optimum rate utilization of uplink
bandwidth and minimum end-to-end data latency
Supports unidirectional broadcast applications.

HS-S
ISDN basic rate access module with four type S interfaces. Performs
submultiplexing and data rate adaptation on B channels in accordance with
ITU-T Rec. I.460.
Yes
This module is intended for extension of ISDN lines over Megaplex-4100 links,
and can provide phantom feed to user equipment
HS-U-6,
HS-U-12
ISDN basic rate access module with 6, respectively 12, type U interfaces.
Performs submultiplexing and data rate adaptation on B channels per ITU-T
Rec. I.460. The module supports two operation modes:
/I: intended for extension of ISDN lines, can provide phantom feed to user
equipment. Supports 2B + D channels, and the channel data rates are
user-selectable (16, 32, and 64 kbps for each B channel, and 16 kbps for
the D channel).
/1: intended for use over leased lines, and can be used as dedicated
line termination units for the ASM-31 and ASMi-31 short-range
modems offered by RAD. Supports user channel data rates of 4.8, 9.6,
19.2, 48, 56, and 64 kbps over each B channel, and 128 kbps by
combining the two B channels. The D channel is ignored.
Yes
HSF-2
Interface module for teleprotection equipment, complying with IEEE C37.94

requirements. Provides two ports with 850 nm multimode fiber interfaces,
with a capacity of up to 10 64 kbps per port.
Yes
LS-6N,
LS-12
Data sub-multiplexer modules, providing 6, respectively 12, synchronous

or asynchronous data channels with ITU-T Rec. V.24/EIA RS-232
interfaces, each operating at independently selectable data rate in the
range of 2.4 to 64 kbps. Support end-to-end transmission of control line
per channel. LS-12 channels can be bundled into two groups, each
independently routed to a different destination.
Yes
M16E1
Module with 16 E1 DSU interfaces, providing up to 160 E1 ports per

chassis and transparent E1 transfer to SDH.
No
M16T1
Module with 16 T1 DSU interfaces providing up to 160 T1 ports per

chassis and transparent T1 transfer to SONET.
No
1-16
Megaplex2100/2104
Compatible
Module
Description
M8E1
Module with eight E1 interfaces and user-selectable DSU or LTU mode,

and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
No
M8T1
Module with eight T1 interfaces and user-selectable DSU or CSU mode,

and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
No
M8SL
Module with eight SHDSL interfaces, for transporting E1 and fractional E1

payloads, and three 10/100 Mbps Ethernet ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The
three Ethernet ports are connected to an internal Ethernet switch, and
share a 100 Mbps Fast Ethernet connection to the CL module.
No
Each port features an independent multi-rate SHDSL modem, transmitting

at user-selectable data rates in the range of 192 kbps to 2048 kbps. Has
internal non-blocking full cross-connect matrix similar to M8E1 and M8T1
modules.
SHDSL interface type (STU-C or STU-R) is user-selectable.
Compatible with other RAD equipment having STU-R SHDSL interfaces,
such as the ASMi-52 SHDSL Modems. M8SL modules will also operate in a
link with 991.2-compatible STU-R units from other vendors.
MPW-1
No
Pseudowire server I/O module that provides TDM pseudowire access
gateway services over packet-switched networks (Ethernet, IP, and MPLS)
for TDM traffic (E1, T1, SHDSL, ISDN, high-speed and low-speed data,
voice) received via the Megaplex-4100 TDM buses from other modules.
Has eight independently-configurable internal DS1 ports, each capable of
handling 32 timeslots, for a total processing capacity of 256 timeslots
(the equivalent of 8 E1, or 2.048 Mbps streams).
OP-108C
Dual E1 and Ethernet multiplexer, where each multiplexer operates

independently and can operate in a link with the Optimux-108 and
Optimux-108L, 4 E1 and Ethernet Multiplexer standalone units offered by
RAD.
No
Each multiplexer transparently transports four independent E1 data

streams and one 100BASE-TX Ethernet channel over one optical link. Each
link has two optical ports, with user-configurable redundancy between
the two ports.
The optical ports can be equipped with field-replaceable SFPs. Support for
standard SFP optical transceivers link interfaces enables selecting the
optimal interface for each application. High-performance SFPs available
from RAD can achieve ranges of up to 120 km (75 miles).
1-17

Megaplex2100/2104
Compatible
Module
Description
OP-34C
16-channel E1 and Ethernet multiplexer, transporting 16 independent E1

data streams and optionally Ethernet data from a 100BASE-TX Ethernet
channel over one link operating at the E3 (34.386 Mbps) rate. Is primarily
intended to operate in a link with the Optimux-34 standalone fiber-optic
multiplexer offered by RAD. However, it can also operate in a link with
another OP-34C module.
No
The link has two ports, with user-configurable redundancy between the
two ports. The ports can be equipped with field-replaceable SFPs with
optical or copper (ITU-T Rec. G.703) interfaces. Using SFP optical
transceivers enables selecting the optimal interface for each application.
High-performance SFPs available from RAD can achieve ranges of up to
110 km (68.3 miles).
Ringer-2100R
DC power supply module for DC feed and up to 32 voice channel ring

voltages
Yes
VC-16,
VC-8,
VC-4,
VC-8A,
VC-4A
Analog voice modules VC-16, VC-8 and VC-4 provide 16, 8 or 4

PCM-encoded toll-quality voice channels.
Yes
The modules are available in three models:
E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464 Types
I, II, III and V, and BT SSDC5
FXS: 2-wire interfaces for direct connection to telephone sets
FXO: 2-wire interfaces for direct connection to PBX extension lines.
VC-8A and VC-4A are similar to VC-8 and VC-4 modules, except that they
also support ADPCM.
VC-4/ OMNI
Note
Omnibus E&M voice module providing four toll-quality voice channels.

Intended for broadcast applications, in which a master site needs to
communicate with multiple remote stations simultaneously (such as to
broadcast an important message). Also provides party-line service.
Yes
Some of the modules behave different ly in the Megaplex-4100 and

Megaplex-2100/2104 chassis.
Common Logic (CL.2) Modules

The Common Logic (CL.2) module controls the Megaplex operation and is the
interface for its configuration and management.
CL.2 houses the TDM and Packet processing engines, as well as the GbE and
SDH/SONET uplinks.
For direct connection to the SDH/SONET network, CL.2 features two standard
network ports with a software-configurable STM-1/STM-4 or OC-3/OC-12
interface. The dual ports on the CL.2 module can be used either for operation in
parallel or for redundancy.
1-18
For direct connection to packet-based networks, CL.2 has two UTP or SFP-based
GbE ports. The UTP interface features autonegotiaton speed detection
capabilities.
Megaplex-4100 allows the installation of two CL.2 modules of the same type, to
ensure continuous operation when one module is reset, restarted, or stops
operating for any reason. In such a case, the redundant main module immediately
takes over the unit, using its own pre-configured settings. The switch-over to the
off-line module occurs automatically upon detection of failure in the online
module, or upon removing the online module from the chassis. The SDH/SONET
and/or Ethernet traffic subsystems located on the CL modules operate
independently of the management subsystems. This means that if protection
switching has occurred between two external links, the standby module still
controls the SDH/SONET and/or Ethernet traffic assigned to it. For instructions on
extracting and inserting a CL module, refer to Removing/Installing the CL Module
in Chapter 2.
Power Supply (PS) Modules

Megaplex-4100 can be powered from AC and/or DC sources. When ISDN and/or
analog voice modules are installed in the chassis, it may be necessary to supply feed
and ring generation voltage: for this purpose, the power supply modules connect to
an external ringer, for example, a Ringer-2200N/ISDN standalone unit offered by
RAD.
PS Modules
Two PS modules can be installed in the chassis. Only one PS module is required to
provide power to a fully equipped Megaplex-4100, and therefore installing a
second module provides redundancy. While both modules operate normally, they
share the load; in case one fails or does not receive power, the other module
continues to provide power alone. Switch-over is thus automatic and does not
disturb normal operation. For instructions on extracting and inserting a power
supply, refer to Removing/Installing the PS Module in Chapter 2.
Megaplex-4100 can be ordered with either AC or DC power supply modules. The
current PS module versions are listed below:
DC-powered modules: PS/48 and PS/24. These 250W power supply modules
operate on -48 VDC and 24 VDC, respectively (nominal voltage is marked on
the module panel), and can provide line feed and ring voltages (-48 or
24 VDC) to the I/O modules installed in the chassis, through an internal bus.
These voltages are sufficient for most types of voice modules. However,
higher voltages required (for example, for ISDN modules) must be provided by
an external source.
AC-powered module, PS/AC: 250W power supply module, operates on

110 VAC and 230 VAC, 50/60Hz (nominal voltage is marked on the module
panel). Phantom feed voltages must be supplied by an external voltage
source.
1-19
Feed and Ring Voltage Sources

Megaplex-4100 PS modules connect to an external feed and ring generation voltage
source, for example the Ringer-2200N standalone unit offered by RAD. The
connection is made as follows:
AC-powered PS modules have a separate connector for feed and ring voltage.
DC-powered modules derive the -48 VDC or +24 VDC feed voltage from the
DC input voltage (in accordance with the nominal input voltage of the
module). In addition, the power input connector also includes a +72 VDC
input for ISDN modules, and for the ring voltage needed by some types of
voice interface modules.
RAD offers the standalone Ringer-2200N unit, intended for installation in 19 racks,
for providing the required feed voltages. For additional details, refer to the
Ringer-2200N Installation and Operation Manual.
1.4
Functional Description
Megaplex-4100 Architecture
Megaplex-4100 unique dual star topology architecture (see Figure 1-6) connects
the common logic processing engines to any of the 10 I/O slots independently. In
addition each of the I/O slots is connected by a TDM path, as well as an Ethernet
path, allowing true native TDM and Ethernet traffic handling with minimal
encapsulation delays, no overhead and dual TDM-Ethernet mode modules.
1-20
Figure 1-6. Megaplex-4100 as a Central Site Solution, Ethernet and TDM Aggregator for SDH/SONET
and PSN Networks
The Megaplex-4100 architecture includes the following main subsystems:
I/O subsystem: provides interfaces to the users equipment. For description,

see I/O Modules section below.
TDM engine:
DS0 cross-connect matrix: handles the TDM traffic. The matrix also
handles the signaling information associated with TDM traffic.
PDH mapper and framer: handle the TDM traffic directed to the network,
and enable mapping any E1 or T1 port to any VC-12, respectively VT1.5.
SDH/SONET engine: includes the circuits needed to interface to an

SDH/SONET network:
Low-order/high-order (LO/HO) cross-connect matrix: controls the routing

of VCs/VTs at all the levels among the PDH mapper, and the SDH/SONET
links. Also provides automatic protection switching (APS) for the network
links, and path protection.
SDH/SONET interfaces: provide the physical interfaces for the SDH/SONET

links.
Ethernet (packet) engine: includes the circuits needed to interface to a

packet-switched network. The Ethernet traffic handling subsystem includes:
Packet processor: controls the forwarding of Ethernet traffic within the

Megaplex-4100 (including forwarding from internal ports, Ethernet-overTDM and virtually concatenated groups) to external Ethernet ports
HO/LO mapper and VCAT engine: handle the Ethernet traffic directed for
transport over the SDH/SONET network by means of virtually
concatenated groups.
GbE interfaces: provide the physical interfaces for the packet switched
network links.
Timing subsystem: provides timing signals to all the Megaplex-4100 circuits,

and external (station) clock interfaces. For redundancy, two independent
subsystems, each located in a CL module, are used. For more information,
see Clock Selection in Chapter 5.
Management subsystem: controls Megaplex-4100 operation, stores its

software and configuration, and provides interfaces for local and remote
management, and for alarm reporting. The management subsystem is also
redundant: two independent subsystems, each located in a CL module, are
used. For more information, see Management Access Methods in Chapter 4,
Management Bridge and Management Router in Chapter 5, as well as
Chapter 7, Software Upgrade.
Power supply subsystem: includes power supply modules that provide power
to the internal circuits, and an interface for external line feed. For
redundancy, two power supply modules can be installed in the chassis. For
more information, see Power Supply (PS) Modules in this chapter and
Installing PS Modules in Chapter 2.
1-21
Figure 1-7 illustrates the position and the contents of the TDM, SDH/SONET and
Packet engines in the Megaplex-4100 Data Flow Block Diagram.
SDH/SONET
Framers and
HO/LO VC/VT
Cross-Connect
Matrix
VCAT
Engine
E1/T1
Mapper
TDM Engine
Packet Engine
Packet
Processor
HO/LO
and VCAT
Mapper
SDH/SONET
Engine
SDH/SONET Ports
GbE Ports
DS1
Cross-Connect
Matrix
E1/T1
Framer
DS0
Cross-Connect
Matrix
ETH
DS0
DS1
Figure 1-7. Data Flow Block Diagram
TDM Engine
TDM traffic can be switched between any of the following entities on the specific
level:
DS0 (analog and digital interfaces: voice, serial, framed E1/T1, E1 over DSL,
E1/T1 over PW or multiplexed fiber, E1/T1 coming from VC-12/VT1.5)
DS1 (unframed E1/T1 coming from M16E1/M16T1, Optimux modules or

ASMi-54C/N): transparent and clock independent DS1 processing towards
SONET/SDH or other I/O ports
SDH/SONET (high and low level cross connect between SDH/SONET ports).
The cross-connect level can be selected to DS1 or DS0 operation mode per port.
DS0 Cross-Connect Matrix

The DS0 cross-connect matrix located on CL modules provides fully non-blocking
1/0 cross-connect among I/O modules and PDH ports of the CL.2 modules. This
matrix operates in coordination with the cross-connect matrices located on most
types of I/O modules.
The DS0 cross-connect matrix provides full control over the routing of individual
timeslots. This is needed for handling the payload of E1 ports with G.704
1-22
framing, T1 ports with SF or ESF framing, and for the inband management
timeslot. The traffic associated with sub-E1 ports (such as ISDN, voice or serial
interfaces} is always handled in the DS0 mode. Accordingly, Megaplex-4100
distinguishes among three main types of payload per timeslot:
Voice: timeslots carrying PCM-encoded payload.

Channel-associated signaling (CAS) information is always associated with
voice timeslots, and therefore it must also be converted when
cross-connecting timeslots from ports using different standards.
Data: data timeslots are transparently transferred from port to port. In

general, it is assumed that no CAS is associated with data timeslots.
Management: one timeslot can be assigned in any E1 or T1 port to carry

inband management traffic to the end users equipment. Such timeslots are
always directed to the CL management subsystem, for processing.
The flow of payload carried by data and voice timeslots is normally bidirectional
(full duplex connection). However, for individual timeslots, it is also possible to
define unidirectional flows, called unidirectional broadcasts, from one source (a
timeslot of a source port) to multiple destinations (each destination being a
selected timeslot of another port). For more information, see the Unidirectional
Broadcast Function section under Cross-Connections in Chapter 5.
The following diagram and table illustrate the DS0 matrix capacity. The maximum
capacity on the I/O side is achieved with the following module combination: 8
M16E1/M16T1 modules + 2 M8E1/M8T1 modules.
1-23
Table 1-2. DS0 Matrix Maximum Capacity

Modules
SDH
SONET
CL.2 side
2 CL.2 modules
4032 (2 x 63 32) DS0
4032 (2 x 84 24) DS0
I/O side
8 M16E1/M16T1
modules
3840 (120* 32) DS0
2880 (120* 24) DS0
2 M8E1/M8T1 modules
512 (2 x 8 32) DS0
384 (2 x 8 24) DS0
Total
8384
7296
*8 x 16 =128 the closest number to the 120 E1/T1 restriction.

The resulting I/O + CL.2 capacity is up to 8384 DS0 for and 7296 DS0 for SONET.
DS1 Cross-Connect Matrix

The DS1 cross-connect matrix provides direct timing-independent cross-connect
of E1/T1 streams directly to any selected VC-12/VT1.5. The E1/T1 traffic from
selected modules (M16E1/M16T1, ASMi-54C/N, Optimux) can be mapped directly
to SONET/SDH without passing the DS0 matrix, thus maintaining independent
timing of the E1/T1 links.
Using the DS1 cross-connect, up to 160 E1/T1 links can be added and dropped at
each Megaplex-4100 node when connected over STM-4/OC-12. The DS1
cross-connect matrix has a capacity of 160 DS1 for the I/O side. On the CL.2
side, the matrix capacity is 252 2 DS1 for SDH (2 x STM-4) and 336 2 DS1 for
SONET (2 x OC-12) for each CL module. The resulting I/O + CL.2 capacity for the
entire system is up to 1168 DS1 for SDH and up to 1504 DS1 for SONET.
E1/T1 Framers and Mappers

The TDM payload directed to the network is structured by the DS0 cross-connect
matrix and applied to the E1/T1 framers. Each framer behaves as a logical E1/T1
port, with user-selectable framing: each CL.2 module can have up to 63 E1 ports,
or up to 84 T1 ports, in accordance with the SDH/SONET framing mode.
The operation mode of each framer can be configured by the user:
For SDH network interfaces, E1 ports are supported
For SONET network interfaces, T1 ports are supported.
The frame type is also selectable, separately for each port:
For E1 ports, either basic G.704 framing (identified as G732N) or G.704

multiframe (G.732S) can be selected.
For T1 ports, the selections are SF (D4) and ESF.
Each framer adds the appropriate overhead and creates the frame structure. The
data stream provided by each framer is applied to the E1/T1 mappers:
1-24
For E1 ports, the mapper enables mapping the port data stream to any of the
63/252 VC-12 in the STM-1/STM-4 signal.
For T1 ports, the mapper enables mapping the port data stream to any of the
84/336 VT1.5 in the OC-3/OC-12 signal.
SDH/SONET Engine
The SDH/SONET engine includes the following parts:
Network port interfaces
SDH/SONET framers and high-order (HO STS-1/VC-4) cross-connect matrix.
The SDH/SONET subsystem is integrated with the Ethernet over SDH/SONET

engine.
SDH/SONET Network Port Interfaces

Each CL.2 module has two STM-1/OC-3/STM-4/OC-12 ports. The ports can be
ordered either with the following interfaces:
STM-1/OC-3:155.52 Mbps 4.6 ppm
STM-4/OC-12: 622.08 Mbps 4.6 ppm.
Each port has an SFP socket that provides the physical interface. For more
information, see SDH/SONET Ports in Chapter 5.
SDH/SONET Framer and LO/HO Cross-Connect Matrix

The SDH/SONET framer subsystem provides the frame assembly/disassembly
services and SDH/SONET overhead processing for the link to the network. The
framer operating modes (SDH or SONET, STM-1/OC-3 or STM-4/OC-12) are
selected by software configuration.
The low-order/high-order (LO/HO) cross-connect matrix controls the routing of
VCs/VTs at all the levels between the E1/T1 mapper, VCAT mapper, and the
SDH/SONET links. It also provides automatic protection switching (APS) for the
network links, and path protection.
The LO part supports low-order cross-connections (VC-12 and VC-3 for SDH links,
VT1.5 for SONET links), while the HO part enables the routing of the high-order
payload (VC-4 for SDH links and STS-1 for SONET links) in the SDH/SONET mode.
Packet Engine
The Packet (Ethernet) Engine is a state-of-the-art, multi-port GbE switching and
aggregating block, which enables hardware-based Ethernet capabilities, such as
traffic management and performance monitoring, between any of the Ethernet
entities.
This Ethernet flow-based traffic can be terminated by any of the following
entities:
Fast Ethernet ports located on I/O modules
Internal Ethernet ports of I/O modules carrying traffic generated by CPE

devices and transferred over E1, T1, voice, multiplexed fiber or SHDSL circuits
Two Gigabit Ethernet ports located on CL.2 modules
SDH/SONET ports by using Virtual or Contiguous concatenation (up to 32 VCG

per CL.2) with GFP or LAPS and optional LCAS support.
1-25
The Ethernet engine flow classification mechanism is based on port (unaware

mode) or VLAN (aware mode with pop/push or preserve capabilities).
Packet Processor
The GbE packet processor is a high-capacity Ethernet processor with classifier,
capable of handling a wide range of VLAN and port-based flows.
The processor includes GbE and Fast Ethernet ports, which are used as follows:
Two external GbE ports, one connected to the GbE 1 interface and the other
to the GbE 2 interface. The two ports can be configured to operate as a
redundancy pair, using hardware-based path and link failure for rapid
switching to the backup link.
10 Fast Ethernet ports are used for Ethernet traffic from I/O modules, one
from each I/O slot.
Two GbE ports are internally connected to the Ethernet processor of the
other CL module installed in the Megaplex-4100.
Each Ethernet port is supported by an independent MAC controller that

performs all the functions required by the IEEE 802.3 protocol. The maximum
frame size supported by the basic Ethernet switch is 9600 bytes. For
maximum frame sizes supported by different I/O modules, see Appendix B.
The frames passed by the MAC controllers are analyzed by the ingress rate
policy controller of the corresponding port before being transferred, through
the switch fabric, to an internal port controller, which controls the frame
egress priorities and inserts them in separate queues. The switch supports up
to four transmission classes for the Fast Ethernet ports, and up to four
transmission classes for the GbE ports. The queues are connected to the
ports through port egress policy controllers. This approach provides full
control over traffic flow, and ensures that congestion at one port does not
affect other ports.
The processor includes a flow classification engine categorizing packets into

flows in accordance with user-defined classification rules. Classification takes
place at full wire speed. The processor recognizes standard frame types.
In addition to the Ethernet traffic handling subsystem components located on
the CL.2 modules, I/O modules with Ethernet ports (M8E1, M8T1, M8SL,
OP-34C, OP-108C, ASMi-54C, ASMi-54C/N, MPW-1) also include a local
Ethernet handling subsystem). This subsystem includes:
Ethernet port interfaces: provide 10/100 Mbps physical interfaces for

external Ethernet links.
Layer 2 Ethernet switch: provides the local Ethernet VLAN classification.
Fast Ethernet data ports: each port connects to the Ethernet traffic
handling subsystem of one CL module.
Ethernet termination and processing: provides the interface between the

Layer 2 Ethernet switch and the TDM-based interface.
1-26
For M8E1, M8T1, and M8SL modules, this function terminates

Ethernet frames in the direction from the switch to the local
cross-connect matrix and processes them for transmission through
the appropriate bundles, that is, over TDM media. In the inverse
direction, the payload received from TDM media is packetized and
inserted in Ethernet frames for transmission to the appropriate
Ethernet port
Note
For MPW-1 modules, this function provides the interfaces for

pseudowire packet traffic
For the Optimux modules, this function terminates Ethernet frames
over the fiber-optic TDM interface
For the ASMi-54C/N and ASMi-54C modules, this function terminates
the Ethernet frames over SHDSL.
The Ethernet termination and processing function can also serve Ethernet traffic
carried through E1-i/T1-i ports of CL.2 modules.
For a detailed description of I/O module Ethernet traffic handling subsystem,
refer to the corresponding I/O module Installation and Operation Manual.
VCAT Engine
The VCAT Engine handles all the functions related to the use of virtual
concatenation, and the preparation of Ethernet traffic for efficient transport over
the SDH/SONET network.
The Ethernet mapper subsystem includes the following functions:
LAPS encapsulation
GFP encapsulation
Virtually concatenated group mapper.
To increase the available number of virtually concatenated groups as Ethernet

transport links, you can configure redundancy for pairs of selected VCGs.
HO/LO Mapper
The HO/LO mapper maps the Ethernet traffic for transmission over the
SDH/SONET network, and creates the virtually concatenated groups (VCGs) that
enable the user to control the utilization of the bandwidth available on the link to
the SDH/SONET network.
The routing of the VCG payload is defined by means of cross-connections, which
means selection of specific VCs/VTs to be used to carry each VCG, in the number
needed to provide the required bandwidth. This operation creates the trails that
are needed to connect the local users to remote locations through the
SDH/SONET network.
Ethernet over SDH/SONET and E1/T1 - General Concept

To describe and map the Ethernet traffic passing over different media (E1/T1,
SDH/SONET, etc), the Megaplex-4100 architecture uses a concept of Logical MAC
ports. Logical MAC represents the Ethernet part of the entity. It should be bound
to a gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical
layer.
1-27
The meaning of the gfp, hdlc or mlppp ports and their further mapping depends
on the Ethernet traffic media:
GFP ports exist only on CL.2 modules and represent VCGs (Virtual
Concatenation Groups) with GFP encapsulation. They can be mapped either
directly to the physical layer or to VCG. In the latter case the binding is done
in two stages and this VCG should be further bound to the physical layer
HDLC ports exist in two flavors:
HDLC ports defined on CL.2 modules represent VCGs (Virtual

Concatenation Groups) with LAPS encapsulation. They can be mapped
either directly to the physical layer or to another VCG. In the latter case
the binding is done in two stages and this VCG should be further bound
to the physical layer
HDLC ports defined on M8E1, M8T1 and M8SL modules represent HDLC
bundles which can be bound to the physical layer representing E1/T1
ports or specific timeslots.
MLPPP ports exist only on M8E1 and M8SL modules and are mapped to the
PPP port. The binding is done in two stages and this PPP port should be
further bound to the physical layer.
Ethernet over E1/T1

The Ethernet services supported by M8E1, M8T1 and M8SL modules are
configured by defining flows within the Megaplex-4100. The flows are defined by
means of Ethernet virtual connection that interconnects two or more ports
(called Logical MAC ports).
Megaplex-4100 uses a special protocol to support the flow of Ethernet traffic. In
M8T1 it is HDLC protocol, in M8E1 and M8SL two types of protocols can be used:
HDLC and MLPPP.
Figure 1-8 shows the relationship between the entities involved in the Ethernet
over E1/T1 functionality.
Logical MAC
1..32
MLPPP
1
HDLC
1..32
XC
1-28
Unframed
E1
1
1:
1:n
Bind
1:1
PPP
1..8
Framed
E1/T 1
Figure 1-8. Logical Entities Representing Ethernet Traffic over E1/T1 Media
The maximum number of HDLC ports that can be defined on an M8E1/M8T1/M8SL
module is 32, and together with the three Ethernet ports, an M8E1/M8T1/M8SL
module supports up to 35 ports. Each of these ports can be connected to any
other Ethernet port within the Megaplex-4100, for example, to another HDLC or
external Ethernet port on any module (including GbE ports on CL modules), to a
Logical MAC port, etc.
Note
It is possible to open only 8 E1-i/T1-i links per module and assign up to 4 HDLC
ports to each of them so that the total capacity is 32 HDLC ports per module.
Moreover, each used E1-i/T1-i link reduces the number of external E1/T1 links
that can be connected to E1/T1 equipment.
In the HDLC Mode, two or more timeslots are cross-connected to the HDLC
entity. The bound HDLC port can be defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1/T1 port. As seen from the diagram, the
timeslot mapping between the framed E1/T1 and HDLC ports should be done via
cross-connect.
The MLPPP protocol is an extension of the PPP protocol that uses the PPP Link
Control Protocol (LCP) and Bridge Control Protocol (BCP) to bind two or more PPP
links to provide increased bandwidth. Each PPP port binds an E1 port. The MLPPP
bundle can be defined only on unframed ports, and its maximum bandwidth is a
multiple of 2048kbps.
The binding of HDLC/MLPPP to flow is done by the intermediate Logical MAC
entity.
Ethernet over SDH/SONET

To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4100 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
1.
At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
2.
The resulting streams are mapped to the desired VCs/SPEs, also configured by
management. The Path Overhead (POH) byte carried by all the group
members is used to transfer to the far endpoint the information needed to
identify:
The relative time difference between arriving members of the virtual

group.
The sequence number of each arriving member.
1-29
3.
Each member of the virtual group is independently transmitted through the

network. The network need not be aware of the type of payload carried by
the virtual members of the group.
4.
At the receiving end, the phase of the incoming VCs/SPEs is aligned and then
the original payload data stream is rebuilt. This requires using a memory of
appropriate size for buffering all the arriving members of the group at the
receiving end. The memory size depends on the maximum expected delay,
therefore to minimize latency the maximum delay to be compensated can be
defined by management.
Figure 1-9 shows the relationship between the entities involved in the Ethernet
over SDH/SONET functionality. Ethernet is mapped to SDH/SONET in the following
steps.
1. Bind VC/VT/STS containers to GFP or HDLC ports. This can be done in two
ways:
Directly 1:1 without using virtual concatenation ( no VCAT)
Using virtual concatenation (VCAT). In this case VC/VT/STS should be first

bound n:1 to a VCG port and then this VCG should be bound to a GFP/
HDLC port.
2. Bind a GFP/HDLC port to a Logical MAC port (1 to 32).

3. Create ingress/egress flows.
Note
The maximum total number of GFP and HDLC ports per CL.2 is 32.
Flow
Egress/ Ingress Port
Logical MAC
1
Ethernet Group
Logical MAC
32
Bind1:1
GFP1..32
HDLC1..32
OR
Bind1:1
Bind1:1
VCG1..32
Bind1:n
VC4-4C/ STS-12C
VCAT No
VC4/ STS-3C
VC3/ STS-1
VC12/VT1.5
Figure 1-9. Logical Entities Representing Ethernet Traffic over SDH/SONET Media
1-30
I/O Modules
Figure 1-10 illustrates Architectural Entities involved in the Megaplex-4100 I/O
FE
24*E1
DS0
DS0
PPP
1..8
Voice
1,2,3,4.1..1
,2,3,4..4
Serial
Bundle
1..2
DS0
DS0
(D)
BRI 1..4
DS0
ETH
1..3
Line 1..8
ETH
1..3
ETH
1..3
Voice
1..4
Serial
1..12
VC-4/OMNI
LS-6N/
LS-12
Voice
1..4/8/16
T1/E1 1..16
Swit
ch
DS1 Mux
DS1 Mux
T1/E1
1..8
T1/E1
1.1..1.4
3.1..3.4
Fast-ethernet
1,2
DS1 Mux
Ethernet
1.1,3.1
PCS
1..8
E1-I
1..8
E1 1..8
SHDSL
1..8
VC-4/8/16
Applicable only for

the LRS module
OP-108C
Switch
DS1 Mux
T1/E1
1..16
T1/E1
1.1..1.16
ETH 1
HS-6N/
HS-12N
HS-703
PCS
1..8
ETH
1.1
SHDSL
1..8
mux_eth_tdm
1
mux_eth_tdm
1..2
M16E1/T1
HSU-6,12/HS-S
FE
FE
16E1/T1
Applicable only for

the LRS module
M8E1/M8T1
FE
16E1/T1
16E1/T1
MPW-1
16E1/T1
640 PWs per

chassis, numbered
per system (1..640)
Serial
1..4/6/12
Serial
1..4
T1/E1 1..8
M8SL
8*E1
HDLC
1..32
PW (32)
B1,B2
BRI
1.1,2..4.1,2
FE
FE
8*E1
L.
MAC
1*E1
HDLC
1..32
L. MAC
MLPPP
1
DS0
ds1 1..8
PPP
1..8
E1-I
1..8
1*E1
Swit
ch
1*E1
DS0
Switch
8*E1
8*E1
MLPPP
1
FE
Modules. Each entity is described in detail in Chapter 5 under the section for
corresponding type of ports: E1, T1, Ethernet, Serial, Logical Mac, etc. For
possible values and hierarchy of the entities, see also Table 1-3.
OP-34C
ASMi-54C/N
ASMi-54C
Figure 1-10. I/O Modules and their Architectural Entities
Megaplex-4100 Architecture Entities

Table 1-3 lists the possible values and hierarchy of different Megaplex-4100
architecture entities.
Table 1-3. Megaplex-4100 Architecture Entities and their Hierarchy
Modules
Port Type
Hierarchy
Possible Values
CL.2
sdh-sonet
slot: port
1..2
aug
slot: au4
speed 155 - 1
speed 622 - 1..4
vc-12
slot:port:au4:tug3:tug2:
tributary
1..63
(port = sdh-sonet)
(tributary = vc12)
vc3-sts1
slot:port:au4:tug3
1..3
1-31
Modules

Port Type
Hierarchy
Possible Values
vt1.5
slot:port:au4:tug3:tug2:
tributary
1..84
(port = sdh-sonet)
(tributary = vt1.5)
oc-3
slot: oc-3
speed 155 - 1
speed 622 - 1..4
e1-i
slot:port:tributary
1..63
(tributary = e1-i)
t1-i
slot:port:tributary
1..84
(tributary = t1-i)
M8E1, M8T1
M8SL
OP-108C
1-32
hdlc
slot:hdlc
1..32
gfp
slot:gfp
1..32
vcg
slot:vcg
1..32
logical-mac
slot: logical-mac
1..32
ethernet
slot:port
1..2
mngethernet
slot:port
station
id
1- cl-a; 2-cl-b
e1/t1
slot: port
1..8
hdlc
slot: hdlc
1..32
ppp
slot: ppp
1..8
mlppp
slot: mlppp
logical-mac
slot: logical-mac
1..32
ethernet
slot: port
1..3
shdsl
slot: port
1..8
e1-i
slot: port
1..8
hdlc
slot: hdlc
1..32
ppp
slot: ppp
1..8
mlppp
slot: mlppp
logical-mac
slot: logical-mac
1..32
ethernet
slot:port
1..3
e1
slot:mux eth tdm:port
1/1..1/4, 3/1..3/4
mux-eth-tdm
slot: port
1..2
ethernet
slot:port
1..2
ethernet
slot:mux_eth_tdm: ethernet
1/1, 3/1
Modules
Port Type
Hierarchy
Possible Values
OP-108C/E1
e1
slot: port
1..8
mux-eth-tdm
slot: port
1..2
ethernet
slot:port
1..2
int-eth
slot:port:tributary
1/1, 3/1
(port = mux_eth_tdm)
(tributary = int-eth)
OP-34C
e1
slot: mux_eth_tdm:port
1..16
mux-eth-tdm
slot: port
ethernet
slot:port
int-eth
slot:port:tributary
1/1
ASMi-54C
shdsl
slot:port
1..8
pcs
slot:pcs
1..8
ethernet
slot:port
1..2
shdsl
slot: port
1..8
e1
slot: port
1..8
e1-i
slot: port
1..8
pcs
slot: pcs
1..8
ethernet
slot:port
1..2
M16E1/M16T1
e1/t1
slot: port
1..16
HSU-6, HSU-12, HSS
serial
slot:port
1..6/1..12/1..4
bri
slot: port
(port=d-channel)
1..6/1..12/1..4
bri
slot:port:tributary
(port=serial,
tributary = b1,b2)
1..2
HS-6N, HS-12,
HS-703
serial
slot:port
1..4/1..6/1..12
HSF-2
serial
slot: port
1..2
LS-6N, LS-12N
serial
slot:port
1..6/1..12
serial-bundle
slot:port
1..2
VC-4/4A/8/8A/16
voice
slot:port
1..4/1..8/1..16
VC-4/OMNI
voice
slot:port
1..4
ASMi-54C/N
1-33
Modules
Port Type
voice
1.5
Note
Hierarchy
Possible Values
slot:port:tributary
(port = voice) (tributary =
internal)
1.1 4.4
Technical Specifications
For module technical specifications, refer to the corresponding section in

Appendix B.
STM-1/STM-4/
OC-3/OC-12 Ports
Number of Ports
2 per CL module
4 per chassis
Bit Rate
STM-1/OC-3:155.52 Mbps 4.6 ppm

STM-4/OC-12: 622.08 Mbps 4.6 ppm
Timing
Internal clock
Clock recovered from the SDH/SONET
interface
External clock recovered from TDM interfaces
Compliance
SDH: ITU-T G.957, G.783, G.798

SONET: GR-253-CORE
Line Code
NRZ
Framing
SDH: ITU-T Rec. G.707, G.708, G.709, G.783

SONET: ANSI T1.105-1995, GR-253-CORE
Ethernet over SDH/SONET GFP (Generic Framing Procedure): ITU-T

G.7041, ANSI T1-105.02, framed mode
LAPS (Links Access Procedure); X.86

LCAS (Link Capacity Adjustment Scheme):
ITU-T G.7042
Protection
1+1 unidirectional APS (G.842)

1+1 bidirectional APS (G.841, Clause 7.1).
1+1 bidirectional optimized APS (G.841 Annex
B. Linear Multiplex Section (MSP); compatible
with 1:1 bidirectional switching)
Path Protection (Telecordia UPSR standard
and ITU-T SNCP recommendation)
Connectors
1-34
SFP-based in accordance with Table 1-4 and

Table 1-5.
Note: For detailed specifications of SFP transceivers,

see the RAD SFP Transceivers data sheet.
Table 1-4. SFP Connector Modules for STM-1/OC-3 Interfaces
Transceiver Wavelength
Fiber Type
Type
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
(min)
(max)
(min)
(max)
(km)
(miles)
LC
-30
-14
-20
-14
1.2
Laser
LC
-28
-8
-15
-8
15
9.3
Laser
LC
-34
-10
-5
40
24.8
Laser
LC
-34
-10
-5
80
49.7
Mini-BNC
0.135
0.08
62.5/125 m, VCSEL
SFP-1
Input power
Transmitter Connector
multi-mode
SFP-2
9/125 m,
1310 nm
single mode
9/125 m,
SFP-3
single mode
SFP-4
9/125 m,
1550 nm
single mode
SFP-11
Copper Link
75 coaxial
cable
over RG-59B/U
Table 1-5. SFP Connector Modules for STM-4/OC-12 Interfaces
Fiber Type
Input power
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
Type
(min)
SFP-15
1310
9/125 single
(max)
(min)
(max)
(km)
(miles)
Laser
LC
-28
-8
-15
-8
15
9.3
Laser
LC
-28
-8
-3
+2
80
49.7
mode
SFP-16
1550
9/125 single
mode
GbE Ports
Number of Ports
2 per CL module
4 per chassis
External Ports
In accordance with order:

Two GbE ports with SFP modules
Two GbE ports with copper (RJ-45) interfaces
Copper GbE Ports
Maximum Frame Size
9600 bytes (for max. frame sizes supported by

different I/O modules, see Appendix B)
Interface Type
10/100/1000BASE-T port, full-duplex, with

autonegotiation
Connectors (per port)
RJ-45, shielded
1-35
Optical GbE Ports
Interface Type
1000 Mbps full-duplex port
Link Connectors
SFP-based in accordance with Table 1-6
Table 1-6. SFP Connector Modules for GbE Interfaces
SFP-5
850 nm
Fiber Type
50/125 m,
Input power
Output Power
Typical Max.
(dBm)
(dBm)
Range
Type
Type
(min)
(max)
(min)
(max)
(km)
(miles)
VCSEL
LC
-17
-9.5
0.55
0.3
Laser
LC
-20
-3
-9.5
-3
10
6.2
Laser
LC
-22
-3
+5
80
49.7
Laser
LC
-21
-3
-4
40
24.8
multi-mode
SFP-6
1310 nm
9/125 m,
single mode
SFP-7
1550 nm
9/125 m,
single mode
SFP-8d
1310 nm
9/125 m,
single mode
Serial Control Port

(CONTROL DCE)
Interface
RS-232/V.24 (DCE)
Data Rate
9.6, 19.2, 38.4, 57.6, 115.2 kbps asynchronous
Ethernet
Management Port
(CONTROL ETH)
Interface
10/100BaseT with autonegotiation
Connector
RJ-45
Station Clock
Interface
Rate
2.048 MHz
2.048 Mbps
1.544 Mbps
Interface
Software-selectable:
RS-422 squarewave
ITU-T Rec. G.703, HDB3 coding for 2.048 MHz
and 2.048 Mbps
ITU-T Rec. G.703, B8ZS coding for 1.544 Mbps
Diagnostics
1-36
Connector
RJ-45
Tests
Local and remote loopbacks per link
Alarms
Time and date stamped
Performance Statistics
Ethernet, SDH/SONET, E1/T1, SHDSL, VCG, PCS,

GFP, HDLC and PW ports
Indicators
Front Panel
POWER SUPPLY A, B
(green)
On: the corresponding PS module is on (and

one of the CL modules is active)
Off: Power supply is off
SYSTEM TEST (yellow)
On: a test (or loopback) is being performed in

the Megaplex-4100
Off: No active tests
SYSTEM ALARM (red)
Blinking: a major and/or critical alarm has

been detected in Megaplex-4100
On: a minor alarm has been detected in
Megaplex-4100
Off: No active alarms
CL.2 module
ON LINE (green/yellow)
On (green): CL module is active or software

decompression
Blinking slowly (green): CL module is on
standby
On (yellow): a test is being performed (active
module only)
ALM (red)
On: alarms have been detected in the

Megaplex-4100, but the highest alarm
severity is minor or warning.
SDH/SONET Ports
ON LINE (green/yellow)
On (green): the corresponding port is active

(carries SDH/SONET traffic, and there is no major
alarm condition, nor any test on this port)
Blinking (green) the port is in protection mode
On (yellow): a test is active on the port
Off: no traffic or test on the port
LOS (red)
On: loss-of-signal at the corresponding port

Off: no loss-of-signal
GbE Ports
1-37
LINK (green)
On: the port is connected to an active Ethernet

hub or switch
Off: Ethernet link is not detected
ACT (yellow)
On or Blinking (in accordance with the traffic):

ETH frames are received or transmitted
Off: ETH frames are not received and
transmitted
Management Ethernet
Ports
LINK (green)

hub or switch
ACT (yellow)

transmitted
Station CLOCK Port

ON (green)
On: the station clock port is configured as no

shutdown
LOS (red)
On: loss-of-signal (when station clock port

configured as connected)
Alarm Relay Port
Port Functions
1 inbound RS-232 alarm input

2 outbound (dry contact) relays triggered by
any user-selected Megaplex-4100 alarm
1-38
Operation
Normally open, normally closed, using different

pins
Connector
9-pin, D-type, female
Power Supply
PS/AC
110/115 VAC (allowed range: 85 to 150 VAC),

50/60Hz
220/230 VAC (allowed range: 150 to 264
VAC), 50/60Hz
Maximum AC input power: 315W + power
supplied for ring and feed voltage purposes
Total output power: 250W + power supplied
for ring and feed voltage purposes (drawn
directly from external source)
PS/DC
-48 VDC (allowed range: -36 to -57 VDC)

24 VDC (allowed range: 18 to 40 VDC)
Maximum input power: 315W + power
supplied for ring and feed voltage purposes
Total output power: 250W + power supplied
for ring and feed voltage purposes (drawn
directly from external source)
Selectable ground reference or floating
ground
Caution
The DC input is primarily designed for negative input voltage (grounded positive
pole). However, the DC input voltage can be floated with respect to
Megaplex-4100 ground by means of field-selectable jumpers. Internal jumpers
can also be set to match operational requirements that need either the +
(positive) or (negative) terminal of the power source to be grounded. Contact
your nearest RAD Partner for detailed information.
Maximum Power Supply Output Currents
Regulated Output Voltage

All PS models
Power Consumption
Physical
+3.3V
+5V
-5V
+12V
-12V
30A
40A
6.5A
2A
2A
27.75 W (per CL, max)
Height
18 cm (7 in), 4U
Width
44 cm (17 in)
Depth
33 cm (12 in)
Weight (fully equipped

chassis)
15.3 kg (33.8 lb) max
1-39
1-40
Chapter 2
Installation
This chapter provides installation instructions for the Megaplex-4100.
The chapter presents the following information:
General description of equipment enclosure and its panels.
Mechanical and electrical installation instructions for the enclosure itself and
for system modules, that is, PS and CL modules.
After installing the system, it is necessary to configure it in accordance with the

specific user's requirements:
The preliminary system configuration is always performed by means of a

supervision terminal (procedures for using the terminal are given in
Chapter 4). The software necessary for using the terminal is stored in the CL
module: if the CL module is not yet loaded with the required software, refer
to Chapter 7 for detailed software installation instructions.
After the preliminary configuration, the system can also be managed by

means of Telnet hosts and/or SNMP-based network management stations,
e.g., RADview. Refer to the User's Manual of the network management
station for operating instructions.
2.1
Site Requirements and Prerequisites
General Safety Precautions
Warning
No internal settings, adjustment, maintenance, and repairs may be performed by

either the operator or the user; such activities may be performed only by a skilled
technician who is aware of the hazards involved. Always observe standard safety
precautions during installation, operation, and maintenance of this product.
2-1
Chapter 2 Installation
Megaplex-4100 modules contain components sensitive to electrostatic discharge

(ESD). To prevent ESD damage, always hold the module by its sides, and do not
touch the module components or connectors.
Cautions
Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the Megaplex-4100 modules. To prevent physical damage:
Always keep modules in their protective packaging until installed in the
Megaplex-4100 chassis, and return them to the packaging as soon as they are
removed from the enclosure.
Do not stack modules one above the other, and do not lay any objects on
PCBs.
When inserting a module into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the module PCB does not touch
the adjacent module, nor any part of the chassis. If resistance is felt before the
module fully engages the mating backplane connector, retract the module, realign
it with the slot guides and then insert again.
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
Warning
Grounding
Grounding
For your protection and to prevent possible damage to equipment when a fault
condition, e.g., a lightning stroke or contact with high-voltage power lines, occurs
on the lines connected to the equipment, the Megaplex-4100 case must be
properly grounded (earthed) at any time. Any interruption of the protective
(grounding) connection inside or outside the equipment, or the disconnection of
the protective ground terminal can make this equipment dangerous. Intentional
interruption is prohibited.
Dangerous voltages may be present on the electrical cables connected to the

Megaplex-4100 and its modules.
Warning
Never connect cables to Megaplex-4100 if not properly installed and

grounded.
Disconnect all the cables connected to the electrical connectors of the
Megaplex-4100 before disconnecting its grounding connection.
Before connecting any other cable and before applying power to this equipment,
the protective ground (earth) terminal of the equipment must be connected to
protective ground. Megaplex-4100 grounding terminals are located on the
Megaplex-4100 PS module panels.
Whenever Megaplex-4100 units are installed in a rack, make sure that the rack is
properly grounded and connected to a reliable, low-resistance grounding system,
because the rack can also provide a connection to ground.
2-2
In addition, the grounding connection is also made through each one of the AC
power cables. Therefore, the AC power cable plug must always be inserted in a
socket outlet provided with a protective ground.
Laser Safety
Warning
Megaplex-4100 modules may be equipped with a laser diode. In such cases, a

label with the laser class and other warnings as applicable will be attached near
the optical transmitter. The laser warning symbol may also be attached.
For your safety:
and is connected to the optical transmitter.
Do not use broken or unterminated fiber-optic cables/connectors.
Do not look straight at the laser beam and into the optical connectors while
the unit is operating.
The use of optical instruments with this product will increase eye hazard.
Laser power up to 1 mW at 1300 nm and 1550 nm could be collected by an
optical instrument.
Use of controls or adjustment or performing procedures other than those
specified herein may result in hazardous radiation exposure.
Megaplex-4100 modules equipped with laser devices provided by RAD comply with
laser product performance standards set by governmental agencies for Class 1 laser
products. The modules do not emit hazardous light, and the beam is totally enclosed
during all operating modes of customer operation and maintenance.
In some cases, the users may insert their own SFP laser transceivers into
Megaplex-4100 modules. Users are alerted that RAD cannot be held responsible
for any damage that may result if non-compliant transceivers are used. In
particular, users are warned to use only agency approved products that comply
with the local laser safety regulations for Class 1 laser products.
Wherever applicable, Megaplex-4100 modules are shipped with protective covers
installed on all the optical connectors. Do not remove these covers until you are
ready to connect optical cables to the connectors. Keep the covers for reuse, to
reinstall the cover over the optical connector as soon as the optical cable is
disconnected.
Protection against ESD

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

(ESD). To prevent ESD damage, always hold a module by its sides, and do not
touch the module components or connectors. If you are not using a wrist strap,
before touching a module, it is recommended to discharge the electrostatic
charge of your body by touching the frame of a grounded equipment unit.
Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistance,
yet are not insulators.
AC Power Requirements
AC-powered Megaplex-4100 units should be installed within 1.5m (5 feet) of an
easily-accessible grounded AC outlet capable of furnishing 110/115 or 230 VAC,
(nominal), 50/60 Hz.
DC Power Requirements
DC-powered Megaplex-4100 units require a -48 VDC (36 to -72 VDC) or 24 VDC
(20 to 40 VDC) power source (in accordance with the nominal mains voltage of the
ordered PS module).
Cautions
Megaplex-4100 PS modules have no power switch and start operating as soon

as power is applied. Therefore, an external power ON/OFF switch is required
(for example, the circuit breaker that protects the power line can also serve as
an ON/OFF switch).
It is not allowed to install DC-powered PS modules operating on different
voltages (i.e., 24 VDC and -48 VDC) in the same Megaplex-4100 chassis.
Internal jumpers on the DC PS modules can be set to match operational
requirements that need either the + (positive) or (negative) terminal of the
power source to be grounded. The normal factory setting is for a power
source with the +(positive) terminal grounded (the power supply module
jumpers are installed in the BGND=FGND and GND=FGND positions). When it is
necessary to use a power source with the (negative) terminal grounded, or a
floating power source, the jumpers must be disconnected (set to NO).
Check the position of jumpers in the Megaplex-4100 power supply module
(see Figure 2-5) before connecting the DC supply voltage.
Certain I/O modules may still cause BGND to be connected to FGND or GND,
even after setting the jumpers to NO. Refer to the Installation and Operation
Manuals of the modules installed in the chassis for proper setting of their
ground-control jumpers.
2-4
If the Megaplex-4100 chassis must be operated with floating ground, it may

also be necessary to disconnect the ground reference on the power supply
modules, and check the ground and shield wiring on the cables connected to
the chassis. This may require replacing the cables with cables suitable to your
specific application.
Megaplex-4100 chassis must always be connected to FGND (protective
ground).
Special ordering options with preconfigured floating ground settings are available.
Contact your local RAD Partner for more information. When working with FXS
voice modules, see also the VC-4/4A/8/8A/16 section in Appendix B.
Front and Rear Panel Clearance

Allow at least 90 cm (36 inches) of frontal clearance for operator access. Allow
the same clearance at the rear of the unit for interface cable connections and
module replacement.
Ambient Requirements
The ambient operating temperature range of the Megaplex-4100 is 0 to +45C (32
to 113F), at a relative humidity of up to 90%, non-condensing.
Most of the Megaplex-4100 modules are cooled by free air convection: air intake
vents are located on the bottom and exhaust vents are located on the top. The
PS power supply modules have a miniature cooling fan installed on their front
panels: this fan operates only when the temperature is high. Cooling vents are
located in the bottom and upper covers. Do not obstruct these vents. When the
Megaplex-4100 is installed in a 19" rack, allow at least 1U of space below and
above the unit.
Electromagnetic Compatibility Considerations

The Megaplex-4100 is designed to comply with the electromagnetic compatibility
(EMC) requirements of Sub-Part J of FCC Rules, Part 15, for Class A electronic
equipment, and additional applicable standards such as EN55022 and EN55024.
Megaplex-4100 also complies with all the requirements of the CE mark.
To meet these standards, it is necessary to perform the following actions:
Note
Connect the Megaplex-4100 case to a low-resistance grounding system.
Install blank panels to cover all empty slots. Appropriate blank panels can be
ordered from RAD.
Whenever possible, use shielded telecommunication cables. In particular, it is

recommended to use a shielded RS-232 to connect to the CL module serial
control port.
The serial control port is normally used only during preliminary configuration, and
for maintenance purposes. If you cannot obtain a shielded control cable, connect
the cable only for the minimum time required for performing the task.
2-5
In certain cases, the use of shielded cables or twisted pairs, or use of ferrite
cores, is recommended. Refer to the individual module Installation and
Operation Manual for details.
Covering all empty slots is also required for reasons of personal safety.
Warning
2.2
Package Contents
The Megaplex-4100 package includes the following items:
Megaplex-4100 chassis, including CL and PS modules in accordance with order
Power cables in accordance with order (for the DC power cable, also includes
a DC plug)
Supervision terminal cable, CBL-DB9F-DB9M-STR
Dual DB-9 to single DB-9 control cable, CBL-SP-9/SH (if ordered)
Rack installation kit in accordance with order:
RM-MP-MX-23/19: hardware kit for installing one Megaplex-4100 in either

a 19-inch or 23-inch rack
MP-4100-RM-ETSI/19: hardware kit for installing one Megaplex-4100 in a

23-inch ETSI rack (can also be used for installation in 19-inch rack)
Technical documentation CD.
I/O modules are shipped either separately, or preinstalled in the chassis, in

accordance with your order.
2.3
Required Equipment
The additional cables you may need to connect to the Megaplex-4100 device
depend on the Megaplex-4100 application.
You can use standard cables or prepare the appropriate cables yourself in
accordance with the information given in Appendix A, and in the Installation and
Operation Manuals of the installed modules.
2.4
Mounting the Megaplex-4100 Unit
This section presents instructions for installing Megaplex-4100 units. To help you
familiarize with the equipment, it also presents a physical description of the
Megaplex-4100 versions.
2-6
Do not connect any cables to the Megaplex-4100 before it is installed in the

designated position.
Warning
Familiarization with Megaplex-4100

Figure 2-1 shows a general view of the Megaplex-4100 enclosure.
10 I/O Modules
2 CL Modules
2 PS Modules
Figure 2-1. Megaplex-4100 Enclosure, General View

The enclosure has 14 module slots: two of them are reserved for PS modules,
and two for CL modules. The other 10 slots are intended for I/O modules. Each
I/O slot can accept any type of I/O module. The modules are inserted from the
rear side.
The Megaplex-4100 enclosure can be ordered with brackets for installation in racks.
The brackets are attached to the sides of the enclosure, near the front or rear panel.
Rear View
Figure 2-2 shows a typical rear view of the Megaplex-4100 enclosure and
identifies the slots and their use. Note the labels which designate the type of
module that can be installed in each slot:
Slots labeled PS-A and PS-B (identified as ps-a and ps-b on supervision
terminal screens): power supply modules
Slots labeled I/O-1 to I/O-10 (identified as slot 1 to slot 10 on supervision

terminal screens): I/O modules
Slots labeled CLX-A and CLX-B (identified as cl-a and cl-b on supervision
terminal screens): CL modules.
2-7
In addition, each slot is keyed, therefore it is not possible to install a wrong

module type.
Caution
Slot
To prevent physical damage to the electronic components assembled on the two

sides of the module printed circuit boards (PCB) while it is inserted into its
chassis slot, support the module while sliding it into position and make sure that
its components do not touch the chassis structure, nor other modules.
PS-A
PS-B
I/O 2
I/O 1
PS-B
PS-A
PS/DC
PS/AC
PS/DC
PS/DC
IO-3
IO-1 IO-2
L
I
N
K
I/O 3
I/O 4
TST
CL-2
LOC
E
CH-1 CH-1
REM
LOC
M
E
CH-2 CH-2
CH
4-6
CH
1-3
LINK
1-8
ON LINE
S
D
H 1
/
S
O
N
E 2
T
CH.
1-2
72V
24V
RTN
+72V
ON
-48V
ACT
200-240VAC
LINK
E
T
H
1
Rx
Tx
ACT
LINK
Tx
LINK
Rx
ON
ACT
C
O
N D
T C
R E
O
L
REM
LOC
LASER
CLASS
1
100-120VAC
Rx
Tx
E
T
H
2
CH-6
CH
10-12
E
T
H
3
PS Slots
CH
7-9
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
G
b
E
CH-5
REM
LOC
LINK
E
T
H
C
O
N D
T C
R E
O
L
CH.
3-4
CH-8
REM
I/O Slots
ASMi-54C
OP-34C
A
L
A
R
M
C
L
O
C
K
LINK
ON/LOS
A
L
A
R
M
OP-106C
S
H
D
S
L
.
b
I
s
LINK/
ACT
E
T
H
LINK
1-8
LINK/
ACT
O
P
E A
T
HO
P
B
100
100
ACT
1
LASER
CLASS
1
LASER
CLASS
1
LINK
ACT
L
I
N
K
ACT
ETH2
ON
LINE
ACT
E
T
H
CH-7
REM
LOC
LINK
ETH1
2
LINK
ACT
ALM
LOS
G
b
E
LOC
ON LINE
ALM
LOS
I/O 10
I/O 9
I/O 8
M8E1
LASER
CLASS
1
REM
VDC-IN
IO-9 IO-10
IO-8
STATUS
LASER
CLASS
1
CH-3 CH-3
CH-4 CH-4
MPW-1
CL-2
LOS
REM
LOC
IO-7
I/O 7
I/O 6
CL-B
CL-A
HS-R/N
CH.
1
REM
LOC
VDC-IN
I/O 5
VC-4/Omni
E&M
VC-8/RJ
FXS
HS-12/N
RS-232
M8E1
STATUS
IO-6
CL-B
CL-A
IO-4 IO-5
C
L
O
C
K
ON/LOS
E
T
H
1
E
T
H
2
E
T
H
3
LOSS
ACT
E
T
H
1
L
I AIS
N
LOSS
LINK K
LASER
CLASS
1
ACT
1
E
T
B H
ACT
E
T
H
2
O
P
A
LASER
CLASS
1
O
P
B
2
L
I
N
3 K
AIS
LOSS
LINK
LINK
ACT
E
T
H
3
LINK
CL Slots
I/O Slots
Figure 2-2. Megaplex-4100 Enclosure, Typical Rear View
Front Panel
The front panel of the Megaplex-4100 enclosure is shown in Figure 2-3. For
description of LED indicators, see Chapter 3.
POWER SUPPLY
A
B
SYSTEM
ALARM
TEST
MEGAPLEX-4100
Figure 2-3. Megaplex-4100 Enclosure, Front Panel
2-8
Installing PS Modules
Warning
High
Voltage
Dangerous voltages are present inside the PS module when it is connected to

power. Do not connect the PS module to power before it is properly installed
within the Megaplex-4100 enclosure. Always disconnect the input power from
the PS module before removing it from the enclosure. The installation and
preparation of the module shall be done by a qualified person who is aware of
the hazards involved.
Module Panels
The following PS versions are offered for Megaplex-4100:
DC-powered modules, PS/24 and PS/48: 250W modules, operating on 24 VDC

and -48 VDC (nominal), respectively
AC-powered module, PS/AC: 250W module, operates on 110 VAC or 230 VAC,
50/60Hz (nominal voltage is marked on the module panel).
Typical PS panels are shown in Figure 2-4. PS modules do not include a power
on/off switch and start operating as soon as power is applied. It is recommended
to use an external power on/off switch, for example, the circuit breaker used to
protect the supply line to the Megaplex-4100 may also serve as the on/off
switch.
AC-Powered Module
24 VDC-Powered Module
-48 VDC-Powered Module
Figure 2-4. Typical Megaplex-4100 PS Module Panels
2-9
The PS modules connect to an external feed and ring voltage source, e.g., a
Ringer-2200N standalone unit offered by RAD:
The AC-powered PS versions have a separate connector, designated VDC-IN,

for the external -48 VDC and +72 VDC voltages.
The connection of the +72 VDC voltage to the DC-powered PS versions is

made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
The PS modules have a miniature cooling fan on the front panel. Make sure to
keep the fan opening free of obstructions.
Internal Jumpers
The PS modules include two internal jumpers that control the connection of
frame ground to the internal ground lines.
Caution
If the Megaplex-4100 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local RAD Partner for more information.
The jumpers of a typical PS module (PS/DC or PS/AC) are identified in Figure 2-5.
BGND = FGND
YES
48/24 VDC Positive

Line Connected
to Frame Ground
48/24 VDC Positive
Line not Connected
to Frame Ground
NO
GND = FGND
YES
NO
NO
YES
NO
YES
Signal Ground
Connected
to Frame Ground
Signal Ground not
Connected
to Frame Ground
Figure 2-5. Typical PS Module, Location of Internal Jumpers
2-10
The jumper designated GND=FGND controls the connection between the

internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
Note
The jumper designated BGND=FGND controls the connection between the

positive (+) line of the external 24/48 VDC voltage and the frame (enclosure)
ground. The module is normally delivered with the jumper set to YES. If
necessary, you can set the jumper to NO to float the external 24/48 VDC
positive line with respect to the frame ground. This is usually necessary when
the DC voltage is used to feed or ring voltages.
PS/DC and PS/AC modules can also use a positive supply voltage. In this case,
always disconnect BGND from FGND (set the jumper to NO).
If two power supply modules are installed, make sure that the internal
jumpers are set to the same position on both modules.
Caution Certain I/O modules may still cause BGND to be connected to FGND or GND, even
after setting the jumpers to NO. Refer to the appropriate sections of Appendix B
describing the modules installed in the chassis for proper setting of their groundcontrol jumpers.
Installing a PS Module
Warning
Do not connect the power and/or ring and feed voltage cable(s) to a PS module
before it is inserted in the Megaplex-4100 chassis. Disconnect the cable(s) from
the module before it is removed from the chassis.
1. Insert the PS module in the PS-A slot, and fasten it with the two screws.
2. Connect the power cable according to the voltages indicated on the panel.
3. If an additional redundant module is used, install it in the PS-B slot.
Note
You can install a redundant module in an operating enclosure without turning the
Megaplex-4100 power off. In this case:
First insert the module in its slot
Connect its power cable.
Removing a PS Module
1. Disconnect the power cable(s) connected to the module.
2. Release the two module screws
3. Pull the PS module out.
Installing CL Modules
Module Panels
The Megaplex-4100 chassis can be equipped with two CL modules. At any time,
only one module is active, and the other serves as hot standby.
The modules include the chassis management and timing subsystem, and a
cross-connect matrix for TDM traffic, two SDH/SONET ports (with STM-1/OC-3 or
2-11
STM-4/OC-12 interfaces, in accordance with order) and two GbE ports (with SFPs
or with copper interfaces, in accordance with order). The panels for the
STM-1/OC-3 or STM-4/OC-12 versions are identical.
Figure 2-6 shows typical CL module panels. Table 2-1 describes the functions of
the panel switches. For description of LED indicators, see Chapter 3.
CL-2
CL-2
LASER
CLASS
1
LASER
CLASS
1
ON LINE
ON LINE
ALM
S
D
H 1
/
S
O
N
E 2
T
ALM
LOS
LOS
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ON
LINE
ACT
ACT
1
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
G
b
E
G
b
E
E
T
H
C
L
O
C
K
ON/LOS
CL.2 with Copper

GbE Interfaces
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
LINK
E
T
H
C
L
O
C
K
ON/LOS
CL.2 with Optical

GbE Interfaces
Figure 2-6. CL.2 Module Panels

Table 2-1. Module CL.2, Panel Components
Item
Function
CLOCK Connector
RJ-45 connector for the station clock input and output signals
ETH Connector
RJ-45 connector for the CL 10/100BASE-T Ethernet management port
CONTROL DCE Connector
9-pin D-type female connector with RS-232 DCE interface, for connection to
system management. Connector pin allocation is given in Appendix A
ALARM Connector
9-pin D-type female connector, for connection to the Megaplex-4100 alarm

relay outputs, and an external alarm input. Connector pin allocation is given in
Appendix A
LINK 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding SDH/SONET ports
GbE 1, 2 Connectors
Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors
2-12
Preparing CL Modules for Installation

Before installing a CL module, you may have to install the prescribed types of
SFPs.
Installing an SFP
When installing an optical SFP in an operating module, be aware that it may

immediately start generating laser radiation.
Warning
Caution
During the installation of an SFP with optical interfaces, make sure that all optical
connectors are closed by protective caps.
Do not remove the covers until you are ready to connect optical fibers to the
connectors. Be aware that when inserting an SFP into a working module, the SFP
transmitter may start transmitting as soon as it is inserted.
Note
All the following procedures are illustrated for typical SFPs with optical interfaces.
However, the same procedures apply for SFPs with electrical (copper) interfaces.
Third-party SFP optical transceivers must be agency-approved, complying with the
local laser safety regulations for Class 1 laser equipment.
Warning
To install the SFP module:

1. Lock the wire latch of the SFP module by lifting it up until it clicks into place,
as illustrated in Figure 2-7.
Note
Some SFP models have a plastic door instead of a wire latch.
Figure 2-7. Locking the Wire latch of a Typical SFP

2. Carefully remove the dust covers from the corresponding SFP socket of the CL
module, and from the SFP electrical connector.
3. Orient the SFP as shown in Figure 2-7, and then insert the rear end of the
SFP into the module socket.
2-13
4. Push SFP slowly backwards to mate the connectors, until the SFP clicks into
place. If you feel resistance before the connectors are fully mated, retract the
SFP using the wire latch as a pulling handle, and then repeat the procedure.
5. If necessary, repeat the procedure for the other SFP.
Caution Insert the SFP gently. Using force can damage the connecting pins.
6. Remove the protective rubber caps from the SFP modules.
To remove the SFP module:

Disconnect the fiber optic cables from the SFP module.
1. Unlock the wire latch by lowering it downwards (as opposed to locking).
2. Hold the wire latch and pull the SFP module out of the port.
Caution Do not remove the SFP while the fiber optic cables are still connected. This may
result in physical damage (such as a chipped SFP module clip or socket) or cause
malfunction (e.g., the network port redundancy switching may be interrupted).
Replacing an SFP
SFPs can be hot-swapped. It is always recommended to coordinate SFP
replacement with the system administrator. During the replacement of SFPs with
optical interfaces, only the traffic on the affected link is disrupted (the other link
can continue to carry traffic).
To replace an SFP:
1. If necessary, disconnect any cables connected to the SFP connectors.
2. Push down the SFP locking wire, and then pull the SFP out.
3. Reinstall protective covers on the SFP electrical and optical connectors.
4. Install the replacement SFP in accordance with the Installing an SFP section.
Installing a CL Module
CL modules are installed in the CLX-A and/or CLX-B slots. When two CL modules
are installed, redundancy is available. In this case, the module installed in slot
CLX-A will be automatically selected as the master module, provided that it
operates normally and stores all the required configuration parameters.
To install a CL module:
1. Check that the two fastening screws of the module are free to move.
2. Insert the CL module in its chassis slot and slide it backward as far as it goes.
3. Simultaneously press the extractor handles toward the center of the module
to fully insert its rear connector into the mating connector on the backplane.
4. Secure the CL module by tightening its two screws.
2-14
To interconnect the expansion ports of CL modules:
Connect the expansion cable between the EX LINK connectors of the two
modules.
Removing a CL Module
To remove a CL module:
1. Fully release the two screws fastening the module to the chassis.
2. Simultaneously push the extractor handles outward, to disengage the rear
connector.
3. Pull the module out.
Replacing a CL Module during Equipment Operation

Megaplex-4100 Chassis with two CL Modules
In a Megaplex-4100 equipped with two functional CL modules, the standby
module can be removed/replaced with minimal disruption of Megaplex-4100
services: when you replace the on-line CL module, Megaplex-4100 will
automatically switch to the standby module, provided that module is operational.
The expected disruptions can be minimized in the following ways:
An active CL module also provides routing services and clock signals to other
Megaplex-4100 subsystems, as well as an out-of-band connection to
management. Simply removing the active CL module will therefore cause a
disruption, however short, in all the services provided by the Megaplex-4100
chassis. It is therefore important to prevent this type of disruption, and this
can be achieved by first switching (flipping) to the standby CL module before
replacing the on-line CL module.
Removing a module always disconnects the traffic carried by the active

payload interfaces (GbE and/or SDH/SONET) located on the replaced module.
Note that these traffic interfaces can be active even on the standby CL
module, and therefore the only way to avoid traffic disconnections is to use
automatic protection for these interfaces: for example, APS can be used to
protect SDH/SONET traffic, and LAG protection can be used to protect
Ethernet traffic.
You can identify the active and standby modules by their ON LINE indicators.
Caution
To prevent service disruption, check that the ON LINE indicator of the CL module
you want to remove is flashing. If not, use the supervisory terminal (or any other
management facility) to reset the module to be replaced, and wait for execution
of this command before continuing: this will cause the Megaplex-4100 to flip to
the other CL module within 50 msec.
To flip to the other CL module using the supervision terminal:
1. Identify the on-line CL module: this is the module with the lit ON LINE
indicator.
2-15
2. Whenever possible, connect the supervision terminal directly to the CONTROL

DCE connector of the on-line CL module, and log in as administrator.
3. At the mp4100>admin# prompt, type reboot active to send a reset command
to the module to be replaced.
4. Wait for the flipping to be executed. After it is executed, the ON LINE
indicator of the CL module the supervision terminal is connected to starts
flashing, while that of the other module stops flashing and lights steadily.
5. You can now disconnect the supervision terminal, and remove the module.
6. When installing a CL module in the slot of the removed module, you may
cause flipping to the original module by resetting the current on-line CL
module.
Replacing a CL Module during Equipment Operation

Megaplex-4100 Chassis with Single CL Module
In a Megaplex-4100 equipped with a single CL module, before replacing the CL
module it is recommended that a functional CL module of the same type be
installed in the free CL slot. The replacement can be temporary.
After inserting the additional CL module, it is necessary to let it update its
database from the information provided by the existing CL module:
1. If necessary, program the additional module in the Megaplex-4100 database.
2. Enter commit to update the databases, and then wait until the CL DB
CHECKSUM IS DIFFERENT alarm is off.
3. At this stage, continue in accordance with the steps listed above for a
Megaplex-4100 with two CL modules.
If the only CL module in the chassis is replaced, Megaplex-4100 services will
always be disrupted to some extent while no CL module is present. Therefore, be
prepared and perform the replacement as rapidly as possible.
Among other steps, make sure to upload the existing configuration database to a
host, using TFTP. After replacement is completed, download the database to the
new CL module, to continue normal operation in accordance with the previous
configuration.
Installing I/O Modules

Install each I/O module in the prescribed I/O slot, in accordance with the
installation plan.
For installation instructions, refer to the corresponding section of Appendix B.
Installing Blank Panels

Install blank panels in all the chassis slots that are not occupied by modules.
2-16
Installing the Megaplex-4100 Enclosure

The Megaplex-4100 is intended for installation on shelves and racks. Do not
connect power to the enclosure before it is installed in the designated position.
Installing in a 19 Rack
For rack installation, it is necessary to install two brackets to the sides of the
unit. As illustrated in Figure 2-8, you may install the brackets in two ways, to
orient the unit in accordance with your requirements (either with the
Megaplex-4100 front panel toward the front of the rack, or the module panels
toward the front).
Install Brackets Here if

You Want the Front Panel
toward the Front of the Rack
Figure 2-8. Attachment of Brackets to Megaplex-4100 Case for Installing in 19 Rack
2-17
Installing in 23 Rack
The same set of brackets can also be used to install the Megaplex-4100 unit in a
23 rack. Figure 2-9 shows how to attach the brackets for installation in 23
racks (only front installation is shown in this figure).
Figure 2-9. Attachment of Brackets for Installation of Megaplex-4100 Unit in 23 Rack

After attaching the brackets, fasten the enclosure to the rack by four screws
(two on each side).
After installing the enclosure, check and install the required modules, in
accordance with the installation plan.
2.5
Connecting the Megaplex-4100 Unit
Grounding Megaplex-4100
Warning
2-18
Before connecting any cables and before switching on this instrument, the
protective ground terminals of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Make sure that only fuses of the required rating are used for replacement. Use of
repaired fuses and the short-circuiting of fuse holders is forbidden.
Whenever it is likely that the protection offered by fuses has been impaired, the
instrument must be made inoperative and be secured against any unintended
operation.
Connect a short, thick copper braid between the grounding screw on each PS
module panel and a nearby grounding point.
Connecting to Power
Caution Megaplex-4100 does not have a power on/off switch. Therefore, when
Megaplex-4100 is equipped with PS modules without power on/off switch, it will

start operating as soon as power is applied to at least one of its PS modules. It is
recommended to use an external power on/off switch to control the connection
of power to Megaplex-4100. For example, the circuit breaker used to protect the
supply line to Megaplex-4100 may also serve as the on/off switch.
Power should be connected only after completing cable connections.
Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Note
When redundant power supply modules are used, it is recommended to connect

the power cables to outlets powered by different circuits.
Connecting to External Feed and Ring Voltages

External feed and ring voltages are required by voice modules and by ISDN
interface modules.
The recommended source for external voltages is Ringer-2200N offered by RAD.
Ringer-2200N is a standalone unit intended for rack mounting, capable of
providing power for up to twenty voice channels. Refer to the Ringer-2200N
Installation and Operation Manual for connection instructions.
Caution
Turn on the Ringer-2200N external voltage source, or connect the external

voltages, only after Megaplex-4100 is turned on.
Turn off the Ringer-2200N external voltage source, or disconnect the external
voltages, only after Megaplex-4100 is turned off.
Connecting to a Terminal
The CL supervisory port has a serial RS-232 asynchronous DCE interface
terminated in a 9-pin D-type female connector, designated CONTROL DCE.
This port can be directly connected to terminals using a cable wired
point-to-point. A cross cable is required to use the DTE mode, for example, for
connection through modems or digital multiplexer channels.
Note
When using redundant CL modules, you can connect the terminal, respectively the
modem, in parallel to the corresponding serial port connectors of the two modules
by means of a simple Y-cable, because at any time only one serial port (that of the
active module) is active. An optional CBL-SP-9/SH cable can be ordered from RAD
for this purpose.
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.
2-19
To connect to the CONTROL DCE port:

The connections to the CONTROL DCE connector are made as follows:
Connection to a supervision terminal with 9-pin connector: by means of a

straight cable (a cable wired point-to-point).
Connection to modem with 9-pin connector (for communication with remote

supervision terminal): by means of a crossed cable.
Additional connection options are presented in Appendix A.
To connect to an ASCII terminal:

1. Connect the male 9-pin D-type connector of CBL-DB9F-DB9M-STR straight
cable available from RAD to the CONTROL DCE connector.
2. Connect the other connector of the CBL-DB9F-DB9M-STR cable to an ASCII
terminal.
Caution
Terminal cables must have a frame ground connection. Use ungrounded cables
when connecting a supervisory terminal to a DC-powered unit with floating
ground. Using improper terminal cable may result in damage to supervisory
terminal port.
Connecting to a Management Station or Telnet Host

The CL modules have 10BASE-T/100BASE-TX Ethernet interfaces terminated in
RJ-45 connectors, designated CONTROL ETH.
These interfaces support MDI/MDIX crossover and therefore the ports can always
be connected through a straight (point-to-point) cable to any other type of
10/100BASE-T Ethernet port (hub or station).
To connect to a management station or Telnet host:

The link to network management stations using SNMP, and/or Telnet hosts is
made to the RJ-45 connector designated CONTROL ETH.
You can use any standard cable (straight or crossed) to connect to any type of
Ethernet port (hub or station).
Connecting the Station Clock Port

The station clock ports located on the CL modules can accept 2.048 MHz or
1.544 MHz signals (framed 2.048 Mbps or 1.544 Mbps signals are also accepted).
The port can also output the clock signal: this output provides a convenient
means for distributing clock signals, including the Megaplex-4100 nodal clock
signal, to other equipment.
The station clock port is terminated in one RJ-45 connector, designated CLOCK,
which supports two interfaces:
2-20
100 /120 balanced interface for operation over two twisted pairs
75 unbalanced interface for operation over coaxial cables. This interface

can be used only for 2.048 MHz or 2.048 Mbps clock signals.
At any time, only one interface is active. The selection of the active interface is
made by the user. In addition, provisions are made to sense the type cable
connected to the port:
Note
One of the contacts in the station clock connector is used to sense the
connection of the unbalanced adapter cable (see Appendix A). Do not connect
cables with more than two pairs when you want to use the balanced interface.
Note
The cable used for connecting to equipment with balanced interface should
include only two twisted pairs, one for the clock output and the other for the
clock input.
To connect to equipment with unbalanced interface, it is necessary to convert

the CL RJ-45 connector to the standard pair of BNC female connectors used
for unbalanced ITU-T Rec. G.703 interfaces. For this purpose, RAD offers a
15-cm long adapter cable, CBL-RJ45/2BNC/E1/X. This cable has one RJ-45 plug
for connection to CL station clock connector, and two BNC female connectors
at the other end.
When using redundant CL modules, only one of the two station clock ports must be
connected to a station clock source. For best protection, it is recommended to
connect the two station ports to two separate station clock sources.
When only one clock source is available, you can have better protection by
connecting the station clock inputs in parallel, by means of a simple Y-cable. In this
case, configure the CL module to use a Y-cable: this configuration ensures that at
any time only one station clock interface (that of the active module) is active.
Connecting the Alarm Port

The alarm port is terminated in a 9-pin D-type female connector located on the
CL module, designated ALARM. This port includes:
Caution
Floating change-over dry-contact outputs for the major and minor alarm
relays. The alarm relay contacts are rated at maximum 60 VDC/30 VAC across
open contacts, and maximum 1 ADC through closed contacts (total load
switching capacity of 60 W).
Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
+5V auxiliary voltage output (through a 330 series resistor).
External alarm sense input. The input accepts an RS-232 input signal; it can
also be connected by means of a dry-contact relay to the auxiliary voltage
output.
2-21
To connect to the ALARM connector:

The connection to the ALARM connector is made by means of a cable provided by
the customer, in accordance with the specific requirements of each site. Refer to
Appendix A for connector pin functions.
Caution
To prevent damage to the internal alarm relay contacts, it is necessary to limit, by

external means, the maximum current that may flow through the contacts
(maximum allowed current through closed contacts is 1A). The maximum voltage
across the open contacts must not exceed 60 VDC.
Connecting to SDH/SONET Equipment

Note
SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends to order modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Connecting Optical Cables to the SDH/SONET Links

The optical fibers intended for connection to equipment installed in a rack should
pass through fiber spoolers, located at the top or bottom of the rack, in
accordance with the site routing arrangements (overhead or under-the-floor
routing). The spoolers must contain enough fiber for routing within the rack up to
the CL optical connectors, and for fiber replacement in case of damage (splicing
repairs).
From the spoolers, the optical fibers should be routed through cable guides
running along the sides of the rack frame to the level of the equipment to which
they connect.
When connecting optical cables, make sure to prevent cable twisting and avoid
sharp bends (unless otherwise specified by the optical cable manufacturer, the
minimum fiber bending radius is 35 mm). Always leave some slack, to prevent
stress. RAD recommends installing plastic supports on each cable connector:
these supports determine the fiber bending radius at the connector entry point
and also prevent stress at this point.
Caution
Make sure all the optical connectors are closed at all times by the appropriate
protective caps, or by the mating cable connector.
Do not remove the protective cap until an optical fiber is connected to the
corresponding connector, and immediately install a protective cap after a cable is
disconnected.
Before installing optical cables, it is recommended to clean thoroughly their
connectors using an approved cleaning kit.
To connect optical cables to the SDH/SONET links:

1. For each optical interface, refer to the site installation plan and identify the
cables intended for connection to the SFP serving the corresponding
interface.
2-22
2. Where two fibers are used, pay attention to TX and RX connections, and
leave enough slack to prevent strain:
Connect the prescribed transmit fiber (connected to the receive input of

the remote equipment) to the TX connector of the SFP.
Connect the prescribed receive fiber (connected to the transmit output of

the remote equipment) to the RX connector of the SFP serving the same
interface.
Connecting Coaxial Cables to SDH/SONET Links

The SFPs offered by RAD for the electrical SDH/SONET links are equipped with
two mini-BNC connectors, one identified as TX (transmit output) and the other as
RX (receive input).
To convert to BNC connectors, RAD offers the CBL-MINIBNC-BNC adapter cable,
terminated in two BNC connectors.
To connect coaxial cables to the SDH/SONET links:

1. For each electrical interface, identify the cables intended for connection to
this interface in accordance with the site installation plan.
Note
If you are using the CBL-MINIBNC-BNC adapter cable, first connect its mini-BNC
connectors to the corresponding connectors of the SDH links (note TX and RX
designations), and then proceed with the connection of the external cables.
2. Connect the prescribed coaxial transmit cable (connected to the receive input
of the remote equipment) to the TX connector of the interface.
3. Connect the prescribed coaxial receive cable (connected to the transmit
output of the remote equipment) to the RX connector of the same interface.
Connecting I/O Modules to Remote Equipment

For information regarding connections to port types not covered below, refer to
the corresponding module section in Appendix B.
Connections to E1 and T1 Ports

The maximum allowable line attenuation between a Megaplex-4100 E1/T1
external port and the network interface depends on the type of port interface,
and therefore it is given in the Installation and Operation Manual of each specific
module.
The electrical E1 and T1 interfaces of Megaplex-4100 systems must not be
connected directly to unprotected public telecommunication networks. Use
primary protectors in the MDF or IDF for additional protection.
Connections to Ethernet Ports

SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends ordering modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
2-23
Optical Cable Requirements

The cables connected to Megaplex-4100 optical ports should use 2-mm optical
fibers terminated in the corresponding type of connectors. When routing fibers,
make sure to observe the minimum bending radius (35 mm). RAD recommends
installing plastic supports on each cable connector: these supports determine the
fiber bending radius at the connector entry point and also prevent stress at this
point.
2-24
Chapter 3
Operation
This chapter:
Explains power-on and power-off procedures.
Describes the Megaplex-4100 LED indicators and their function.
3.1
Turning On the Unit
When turning Megaplex-4100 on, it is useful to monitor the power-up sequence.

You can monitor the power-up sequence using any standard ASCII terminal (dumb
terminal or personal computer emulating an ASCII terminal) equipped with an
RS-232 communication interface (same terminal that can be used to control the
Megaplex-4100 operation).
To monitor Megaplex-4100:
1. Configure the terminal for 115.2 kbps, one start bit, eight data bits, no
parity, and one stop bit.
2. Select the full-duplex mode, echo off, and disable any type of flow control.
Make sure to use VT-100 terminal emulation: using a different terminal type
will cause display problems, for example, the cursor will not be located at the
proper location, text may appear jumbled, etc.
To prepare Megaplex-4100 for first-time turn-on:

1. Before first-time turn-on, inspect Megaplex-4100 installation and check that
the required cable connections have been correctly performed in accordance
with Chapter 2.
2. To monitor the Megaplex-4100 during power up and to perform preliminary
configuration procedures, connect a terminal to the CONTROL DCE connector
of the CL module installed in Megaplex-4100 slot CLX-A (this module will be,
by default, the active CL module). Use a straight (point-to-point) cable.
Notes
On the supervision terminal screens, the slots assigned to CL modules are
identified as CL-A, and CL-B.

You can also connect the terminal in parallel to the CONTROL DCE connectors
of both CL modules installed in Megaplex-4100, using a Y-cable.
Turning On the Unit
3-1
Chapter 3 Operation
Caution
To turn the Megaplex-4100 on:

When an external feed and ring voltage source is connected to the PS modules
installed in Megaplex-4100, always turn that source on only after the PS
module(s) have been turned on.
Note
The Megaplex-4100 PS modules do not include a power switch. Use an external

power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
2. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
After a few seconds, Megaplex-4100 starts decompressing its software.
After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4100
performs its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4100.
3. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active CL module lights in green and that of the
other CL module flashes slowly in green. At this stage, the indicators display
the actual Megaplex-4100 status.
3.2
Indicators
The following tables summarize the function of all LED indicators in

Megaplex-4100. The normal indications on power-up (provided the corresponding
port is connected) are marked in bold.
3-2
Indicators
Chapter 3 Operation
CL.2 Front Panel Indicators

The figure below shows typical CL.2 module panels. Table 3-1 to Table 3-6
describe the functions of the panel components.
CL-2
CL-2
LASER
CLASS
1
LASER
CLASS
1
ON LINE
ALM
ON LINE
LOS
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
1
A
L
A
R
M
G
b
E
G
b
E
2
C
O
N D
T C
R E
O
L
LINK
ACT
E
T
H
LINK
C
L
O
C
K
ON/LOS
Copper GbE
Interfaces
ALM
LOS
S
D
H 1
/
S
O
N
E 2
T
ON
LINE
ACT
2
C
O
N D
T C
R E
O
L
A
L
A
R
M
LINK
ACT
E
T
H
LINK
C
L
O
C
K
ON/LOS
Optical GbE
Interfaces
Figure 3-1. CL.2 Module Panels

Table 3-1. CL.2 System LED Indicators
Name
LED Color
Function
ON LINE
Yellow/green
On (green): CL module is active or software

decompression
Blinking slowly (green): CL module is on

standby
On (yellow): a test is being performed

(active module only)
Indicators
3-3
Chapter 3 Operation
Name
LED Color
Function
ALM
Red
On: alarms have been detected in the

Megaplex-4100, but the highest alarm
severity is minor or warning.

Note: On the standby CL module, this indicator

is always off, even while an alarm condition is
present
Table 3-2. SDH/SONET Link LED Indicators

Name
LED Color
Function
ON LINE
Green/Yellow
On (green): the corresponding port is active

(carries SDH/SONET traffic, and there is no
major alarm condition, nor any test on this
port)
Blinking (green) the port is in protection
mode
On (yellow): a test is active on the port
Red
LOS
On: loss-of-signal at the corresponding port

Note: Any other alarm condition related to

SDH/SONET traffic handled by the port is
indicated only by the CL general alarm (ALM)
indicator
Note
Status indicators for SDH/SONET ports are active only when the corresponding
port is equipped with an SFP and configured as no shutdown.
Table 3-3. Gigabit Ethernet Port LED Indicators
Name
LED Color
Function
LINK (per port)
Green

hub or switch
ACT (per port)
Yellow

transmitted
Note
3-4
Indicators
GbE Status indicators are active only when the corresponding port is configured
as no shutdown, and for optical ports when the port is equipped with an SFP
Chapter 3 Operation
Table 3-4. Management Ethernet Port LED Indicators

Name
LED Color
Function
LINK (per port)
Green
On: the port is connected to an active Ethernet hub or

switch
ACT (per port)
Yellow
On or Blinking (in accordance with the traffic): ETH

frames are received or transmitted
Off: ETH frames are not received and transmitted
Table 3-5. Clock LED Indicators

Name
LED Color
Function
ON
Green
On: the station clock port is configured as no shutdown

Red
LOS
On: loss-of-signal (when station clock port configured as

connected)
Megaplex-4100 Front Panel Indicators

The front panel of the Megaplex-4100 chassis includes additional system status
indicators. Figure 3-2 identifies the front panel indicators, and Table 3-6
describes indicator functions.
POWER SUPPLY
A
B
SYSTEM
ALARM
TEST
MEGAPLEX-4100
Figure 3-2. Megaplex-4100 Chassis, Front Panel

Table 3-6. System LED Indicators (on Megaplex-4100 Front Panel)
Name
Color
Function
POWER SUPPLY
A, B
Green
On: the corresponding PS module is on (and one of

the CL modules is active)
Off: Power supply is off
Indicators
3-5
Chapter 3 Operation

Name
Color
Function
SYSTEM TEST
Yellow
On: a test (or loopback) is being performed in the

Megaplex-4100
Off: No active tests
Blinking: a major and/or critical alarm has been

detected in Megaplex-4100
On: a minor alarm has been detected in Megaplex4100
SYSTEM ALARM
3.3
Red
Startup
Configuration Files
The following files contain configuration settings:
factory-default contains the manufacturer default settings
running-config contains the current configuration that is different from the

default configuration
startup-config contains the saved non-default user configuration. This file is

not automatically created. You can use the save or copy command to create
it.
user-default-config contains default user configuration. This file is not

automatically created. You can use the copy command to create it.
candidate stores any configuration before it is copied to running-config via

commit command.
main-sw contains the active software image.
Figure 3-3 shows the commands that can copy configuration files in a visual
diagram. For details on file operations, refer to File Operations in Chapter 5.
3-6
Startup
Chapter 3 Operation
Admin user-default
Sanity
check
Copy
Copy
Configuration
Session
(Candidate DB)
User-Default Config
Startup-Config
TFTP
Running-config
Save
Factory-Default
TFTP
Commit
Copy
Admin factory-default
Figure 3-3. Commands that Copy Configuration Files
Loading Sequence
At startup, the device boots from the startup-config file, the user-default file, or
the factory-default file, in the sequence shown in Figure 3-4 . If none of these
files exist, the device boots using hard-coded defaults.
Start
Pass
Boot from
Startup-config
Sanity
Check
Yes
Startup-config exist?
Fail
Boot from
User-default-config
Pass
Sanity
Check
No
Yes
User-default-config
exist?
Fail
No
Boot from
Factory-default-config
End
Figure 3-4. Loading Sequence
Startup
3-7
Chapter 3 Operation
If the loading of startup-config or the user-default file fails, the loading failure
event is registered in the event log.
To display the parameter values after startup, use the info [detail] command.
3.4
Using a Custom Configuration File
In large deployments, often a central network administrator sends configuration

scripts to the remote locations and all that remains for the local technician to do
is to replace the IP address in the script or other similar minor changes (using any
text editor), and then download the file to the device.
To download the configuration file, use the copy command. It is recommended to
copy the file to both startup-config and the user-default file.
After downloading the configuration file to startup-config, you have to execute
the file. This can be done in two ways:
Reset the unit. After the unit completes its startup, the custom configuration
is complete.
Instead of resetting the unit, you can simply copy the configuration file to the
running-config file (see File Operations in Chapter 5).
3.5
To turn the Megaplex-4100 unit off:
3-8
Turning Off the Unit
Disconnect the power cord from the power source.
Chapter 4
Management
This chapter describes alternative methods of product management for
Megaplex-4100. Detailed configuration procedures are given in Chapter 5.
4.1
Management Access Methods
Once installed, there are no special operating procedures for Megaplex-4100. The
unit operates automatically after it has started up. The units operational status
can be constantly monitored. If required, Megaplex-4100 can be reconfigured.
Table 4-1 summarizes management alternatives for Megaplex-4100.

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

(HyperTerminal, Procomm, Putty).
See Working with Terminal below.
CONTROL ETH, any

user ETH port on CL
or I/O modules
Local,
remote
Out-of-band
(via CONTROL
ETH only),
Inband
Telnet, SSH over

Ethernet
Procomm, Putty (see Working with

Telnet and SSH below)
SNMP over
Ethernet
RADview (see Working with

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

Systems below)
STM-1/STM-4/
OC-3/OC-12 links
Remote
Inband
Telnet, SSH over

DCC (IP/PPP or
IP/HDLC)

SNMP over DCC

(IP/PPP or
IP/HDLC)

RADview below)

Systems below)
Any E1/T1 or SHDSL
link
Remote
Inband
Telnet, SSH over

a dedicated
timeslot (IP/PPP
or IP/FR)

Management Access Methods
4-1
Chapter 4 Management
Port

Manager
Location
Transport
Method
Management
Protocol
Application
SNMP over a
dedicated
timeslot (IP/PPP
or IP/FR)

RADview below)

Systems below)
Optical (mux-ethtdm) link of OP

modules
Local,
remote
Inband
RAD proprietary
HyperTerminal, Procomm, Putty,

any NMS
SHDSL ports of
ASMi-54C/E1/ETH/N
and ASMi-54/ETH
modules
Local,
remote
Inband
EOC
HyperTerminal, Procomm, Putty,

any NMS
Note
By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled. Refer to the Management Access section in Chapter 5 for details on
enabling/disabling a particular method.
Detailed configuration procedures are given in Chapter 5.
The following functions are supported by the Megaplex-4100 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
Uploading and downloading software and configuration files.
4.2
Working with Terminal
Megaplex-4100 has a V.24/RS-232 asynchronous DCE port, designated CONTROL

DCE and terminated in a 9-pin D-type female connector. The control port
continuously monitors the incoming data stream and immediately responds to
any input string received through this port.
Connecting a Terminal to the Control Port
To set up terminal control:

1. Verify that all the cables are properly connected. For more information, refer
to Chapter 2.
4-2
2. Connect Megaplex-4100 to a PC equipped with HyperTerminal. Refer to

Connecting to a Terminal in Chapter 2 for additional information on
connecting to the control port.
3. Turn on the control terminal or start the PC terminal emulation. To do so, go
to Start> All Programs> Accessories> Communications>HyperTerminal to
create a new terminal connection.
The HyperTerminal application opens, and the Connection Description
dialog box is displayed.
Figure 4-1. HyperTerminal, Connection Description Dialog Box

4. Enter a name for the terminal connection.
5. Select an icon to represent the terminal connection, or leave the default icon
selected.
6. Click <OK>.
The Connect To dialog appears.
Figure 4-2. Connect To Dialog Box

7. Select a PC COM port to be used to communicate with Megaplex-4100 and
click <OK>.
The COM Properties dialog appears.
4-3
Figure 4-3. Properties Dialog Box

8. Configure the communication port parameters as follows:
Bits per second: 9,600
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None.
9. Click <OK>.
HyperTerminal is now ready for communication with the unit.
10. Power-up the unit by connecting the power cable(s).
Megaplex-4100 boots up and self-test results appear on the terminal
screen. Once the test has been completed successfully, the ON LINE LED
becomes green and a login prompt appears.
Figure 4-4. HyperTerminal Window

11. Refer to the next section for details on logging on.
4-4
Login
To access the unit's management/configuration/monitoring options, you must
log in.
Megaplex-4100 supports the following access levels:
Superuser (su) can perform all the activities supported by the Megaplex-4100
management facility, including defining new users of any level and changing
their passwords.
Operator (oper) can perform all the activities except defining new users and
changing passwords.
User (user) can only monitor the device or change his/her own password
Technician (tech) can monitor the device, perform diagnostics and clear
alarms)
To enter the Megaplex-4100 CLI:

1. At the User prompt (user>), enter the access level (su | oper | tech | user) and
press <Enter>.
2. The Password prompt (password>) appears.
3. Enter 1234 as password and press <Enter>.
The base prompt mp4100# appears.
Note
It is recommended to change default passwords to prevent unauthorized access

to the unit.
A special option (chngpass) is provided for the case when the user has forgotten
his/her password.
To change/restore the password:

1. At the User prompt (mp4100>config>mngmnt# user>), enter chngpass and
press <Enter>.
2. Enter user as user name and press <Enter> to receive a temporary password.
With this password you can enter as user and change the password to your
own.
Using the CLI

The CLI consists of commands organized in a tree structure, starting at the base
prompt mp4100#. The base prompt is the device name, which can be configured
at the system level (refer to Specifying Administrative Information in Chapter 5).
By default the device name is mp4100.
Commands that are not global are available only at their specific tree location,
while global commands can be typed at any level. To find out what commands are
available at the current location, type ?.
4-5
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location, followed by #. To navigate up, use the global command
exit. To navigate all the way up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed (or not) by a command. If only level names are typed, navigation is
performed and the prompt changes to reflect the current location in the tree.
If the level names are followed by a command, the command is executed, but no
navigation is performed and the prompt remains unchanged.
Note
To use show commands without navigating, type show followed by the level
name(s) followed by the rest of the show command.
In the example below the levels and command were typed together and therefore
no navigation was performed, so the prompt has not changed.
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
configure
configure
configure
configure
configure
configure
configure
configure
port
port
port
port
port
port
port
port
ppp
ppp
ppp
ppp
ppp
ppp
ppp
ppp
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
bind
bind
bind
bind
bind
bind
bind
bind
e1
e1
e1
e1
e1
e1
e1
e1
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
Figure 4-5. Commands without Level Navigation

In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
mp4100#
mp4100# configure
mp4100>config# port
mp4100>config>port# ppp 5/1
mp4100>config>port# ppp(5/1)# bind e1 5/1
mp4100>config>port# ppp(5/1)#
Figure 3-6. Commands with Level Navigation

Note
Level names are abbreviated in the prompt.

You can type only as many letters of the level or command as required by the
system to identify the level or command, for example you can enter config manag
to navigate to the management level.
In addition to being the default prompt, the # symbol also indicates a static or
already configured entity. The $ symbol indicates a new dynamic entity that takes
several commands to configure. The dynamic entity is created as inactive. After
the configuration is completed, it is activated by using the no shutdown
command, as shown in the following example.
mp4100# configure port logical-mac 5/1
mp4100>config>port>log-mac(5/1)$ bind mlppp 5/1
mp4100>config>port>log-mac(5/1)$ no shutdown
mp4100>config>port>log-mac(5/1)$ commit
Figure 3-7. Creating and Activating Dynamic Entity
4-6
The shutdown command disables a hardware element (such as a port), while no

shutdown enables/activates it.
CLI commands have the following basic format:
command [parameter]{value1 | value2 | | valuen} [optional parameter <value>]
where:
{}
Indicates that one of the values must be selected
[]
Indicates an optional parameter
<>
Indicates a value to be replaced by user text
The following keys are available at any time:

?
Lists all commands available at the current level
<Tab>
Command autocomplete
<Ctrl-E>
Logs out
<Ctrl-U>
Erases the line
Displays the previous command
Displays the next command
<Backspace>
Deletes character
<Ctrl-C>
Interrupts current command
<Ctrl-Z>
Returns to the device prompt (root)
The following commands are available at any time and at any level:
echo [<text-to-echo>]
Echoes the specified text
exec <file-name> [echo]
Executes a file, optionally echoing the commands
help [hotkeys] [globals]
Displays general help, or optionally just the

hotkeys and/or global commands
history
Displays the command history for the current

session (by default the history contains the last
10 commands)
info [detail]
Displays information on the current configuration
tree [detail]
Displays all lower command levels and commands

accessible from the current context level
CLI commands can be gathered into text files called scripts. They can be created
using a text editor, by recording the user commands or by saving the current
configuration. The scripts can be imported from and exported to RAD devices via
copy/paste commands.
Note
Although scripts can be created using a text editor, it is recommended to save

the configuration file and then edit it rather than write a script from scratch. The
sequence of the commands is very important and if a script fails during startup at
a certain command, the entire configuration file is discarded.
4-7
Command Tree
At the CLI root, the following categories are available:
version
configure
file
admin
Each category is detailed in the tables below.
Table 4-2. Global Commands

Command
Description
change-mode
Switch to Menus
commit
Update the candidate database to the running

database
discard-changes
Resets to last-saved parameter profile
echo
Echo the text that is typed in
exec
Execute a file
exit
Return to previous level in the commands hierarchy
help
Display help
history
Display commands history
info
print configuration info
logout
Log out this system
sanity-check
Initiates a self test of the device
save
Saves current settings
tree
Display commands hierarchy from current context
virtual-terminal
Table 4-3. Commands in the Admin Category

Command
Description
factory-default
Loads factory default configuration
reboot
Reboots the card
software
Software installed vectors
install
Instructs the device to run from another sw-pack

(upgrade)
show status
Status of upgrade process
user-default
4-8
Loads user default configuration
Table 4-4. Commands in the Configure Category

Command
Description
bridge
Defines bridge parameters.
port
Defines the behavior and attributes of bridge ports.
bind
Binds Bridge to a device (physical/logical) port.
show bind
Displays a list of interfaces bound to the bridge port.
name
Port name.
shutdown
Administratively enable/disable the bridge port.
chassis
|
show manufacture-info
Displaying MAC address of a CL module
cross-connect
Defines cross connects
ds0
DS0 (TimeSlot Assignment) Cross Connect Command
pw-tdm
TDM virtual circuit cross connect
sdh-sonet
SDH/Sonet Cross Connect Command
split-ts
DS0 (TimeSlot Assignment) Cross Connect Command
tdm
TDM (DS1) Cross Connect Command
fault
|
fault-propagation
Enter the fault propagation level
flows
|
classifier-profile
flow
classifier
Map the previously configured classifier profile to the flow
egress-port
Specify the egress port
ingress-port
Specify the ingress port
shutdown
vlan-tag
match
management
Configure management parameters
access
auth-policy
Assign policy of authentication
snmp
Configure SNMP access
ssh
Configure SSH access
telnet
Configure telnet access
radius
Specifies RADIUS parameters
4-9
Command
Description
clear-statistics
Clears the RADIUS statistics
server
Defines the RADIUS server
address
Specifies the RADIUS server's IP address
auth-port
Specifies the RADIUS server authentication port
key
Specifies the shared secret between client and RADIUS

server
retry
Number of authentication attempts at RADIUS server
shutdown
Administratively enables/disables RADIUS server
timeout
Specifies the timeout
show statistics
Displays the RADIUS server statistics
show status
Displays the RADIUS server status
snmp
Configure SNMP parameters
access-group
Configure SNMPv3 access group
shutdown
Activate or deactivate SNMPv3 access group
context-match
Configure context match
notify-view
Configure notify view
read-view
Configure read view
write-view
Configure write view
community
Configure SNMPv3 community
shutdown
Activate or deactivate
name
Configure SNMPv3 community name
sec-name
Configure SNMPv3 community security name
tag
Configure SNMPv3 community tag
notify
Configure SNMPv3 notification
shutdown
Activate or deactivate SNMPv3 notification
tag
Configure SNMPv3 notification tag
bind
Configure SNMPv3 notification bind
notify-filter
Configure SNMPv3 notification filter
shutdown
Activate or deactivate SNMPv3 notification filter
type
Configure SNMPv3 notification filter type
mask
Configure SNMPv3 notification filter mask
notify-filter-profile
Configure SNMPv3 notification filter profile
profile-name
Specify SNMPv3 notification filter profile name
shutdown
Activate or deactivate SNMPv3 notification filter profile
4-10
Command
Description
security-to-group
Configure security for access group
group-name
Specify access group
shutdown
Activate or deactivate security for access group
snmp-engine-id
snmp-engine-id-string
Text, administratively assigned. Maximum remaining

length 27
snmpv3
Enable or disable SNMPv3
Display SNMPv3 information
show snmpv3
target
Configure SNMPv3 target
Activate or deactivate SNMPv3 target
address
Configure SNMPv3 target address
tag-list
Configure SNMPv3 target tag list
target-params
Configure SNMPv3 target parameters
target-params
Configure SNMPv3 target parameters
message-processing-model
Configure SNMPv3 target parameters security message

processing model
security
Configure SNMPv3 target parameters security
shutdown
Activate or deactivate SNMPv3 target parameters
version
Configure SNMPv3 target parameters version
user
Configure SNMPv3 user
shutdown
Activate or deactivate SNMPv3 user
authentication
Configure authentication for SNMPv3 user
privacy
Configure privacy for SNMPv3 user
view
Configure SNMPv3 view
shutdown
Activate or deactivate
mask
Configure SNMPv3 view mask
type
Configure SNMPv3 view type
user
Create/delete user and assign user password
show users
Displays a table of specified users
show information
shutdown
peer
Create/delete peer
port
Enables, disables and defines ports
bri
Define BRI (B1,B2,D ISDN ports) paramters
name
Port name
4-11
Command
Description
rate-bits
Specifies the number of bits for the corresponding

channel
shutdown
This command administratively disables a port. The no

form of this command administratively enables the port
ds1
Specifies the port's frame and line types
line-type
Specifies the line type for the associated channel
loopback
name
Assigns/removes a port name
shutdown
Administratively disables/enables the port
signaling
Enables transmitting an out-of-service signal (OOS) on PW

failure
e1
bert
Activates BER test
Injects single error
clear-bert-counters
Clears BERT counters
clear-statistics
Clears the displayed statistics
idle-code
Code transm. to fill unused timeslots in E1 frames
inband-management
Enables/disables inband management
interface-type
Specifies the port's impedance setting
line-type
Specifies the E1 framing mode
loopback
Enables/disables loopback mode for the port
name
out-of-service
Transmits an out of service signal (oos)
restoration-time
Time req. by port to resume normal oper. after LOF
rx-sensitivity
Sets the attenuation level of the receive signal
shutdown
signaling-profile
Specifies the signaling profile
show bert
Shows BER test parameters
show statistics
Displays the E1 port statistics
show status
Displays the E1 port status
timeslots-signaling-profile
Specifies the signaling profile per timeslot
vc
Adds/vc a virtual connection
e1-i
Specifies internal E1 parameters
Activates BER test
4-12
Specifies E1 parameters
bert inject-error single
bert
Command
Description
Injects single error
clear-bert-counters
Clears BERT counters
clear-statistics
idle-code
Code transm. to fill unused timeslots in E1 frames
inband-management
line-type
Specifies the E1 framing mode
loopback
name
out-of-service
remote-crc
E1 in remote device with/without CRC
restoration-time
Time req. for port to resume normal oper after LOF
shutdown
show bert
Shows BER test parameters
show statistics
show status
Displays the E1 port status
ts0-over-dsl
vc
ethernet
Specifies Ethernet parameters
auto-negotiation
auto negotiation ability
clear-statistics
flow-control
flow control
max-capability
maximum advertizing
name
Port name
policer
Activates/deactivates a policer profile with single queue
shutdown

form of this command administratively enables the port
speed-duplex
Configures the speed and duplex of a Giga Ethernet port

when autonegotiation is disabled
show statistics
Displays the Ethernet port statistics
show status
gfp
Specifies GFP port parameters
bind
Bind port to lower layer port
show bind
clear-statistics
bert inject-error single
Adds/removes a virtual connection
4-13
Command
Description
fcs-payload
Enables/disables CRC-32 sequence of GFP packet payload
name
Port name
scrambler-payload
Enables/disables Scrambling on the GFP packet payload
shutdown
show statistics
Displays the GFP port statistics
vc
hdlc
Specifies HDLC parameters
bind
show bind
name
Port name
shutdown
show statistics
Displays the HDLC port statistics
vc
lag
admin-key
Defines LAG capability
bind
Bind a port to the LAG
show bind
distribution-method
Defines load sharing between LAG ports
name
Name of the LAG
shutdown
shutdown the LAG
show statistics
Displays the LAG statistics
show status
logical-mac
bind
show bind
name
Port name
shutdown
Disables/enables the port
mlppp
bind
show bind
mtu
name
Port name
shutdown
Disables/enables the port
4-14
Command
Description
show statistics
Displays the MLPPP port statistics
show status
Displays the MLPPP port status
mng-ethernet
Specifies management Ethernet parameters
show bind
Displays a list of interfaces bound to the bridge
name
shutdown
mux-eth-tdm
Link use to transport TDM/ETH services
far-end-name
far-end-type
Define far end type of the connected device
loopback
name
remote
Access to remote device connected to the uplink
show sfp-status
Displays the Ethernet port SFP status
shutdown
pcs
bind
show bind-summary
clear-statistics
clear-statistics
name
Port name
shutdown
Enable/disable the port
show statistics
Displays the Ethernet port statistics
show status
ppp
bind
show bind
name
Port name
shutdown
Enable/disable the port
show statistics
Displays the PPP port statistics
show status
sdh-sonet
Defines SDH/SONET port parameters
aug
Defines the administrative unit group (AUG)
clear-statistics
Clears the statistics
loopback
Bind ports to PCS bundle
4-15
Command
Description
show statistics
Displays the specified SDH/SONET statistics
show status
Displays the SDH-SONET of the port
tug3
Defines TUG and enters TUG3 controller
clear-statistics
loopback
show statistics
show status
vc12
Defines VC-12 parameters
clear-statistics
loopback
show statistics
show status
vc
automatic-laser-shutdown
Enable/disable automatic laser shutdown
show bind
Displays a list of interfaces bound to the bridge
clear-statistics
dcc
Enables/disables DCC inband management
frame-type
Specifies the cell frame type
j0-pathtrace
Sets section trace bytes in the section header
loopback
name
oc3
Defines an OC-3 (STM-1) connection
loopback
sts1
Number in the range from 1 to 3.
clear-statistics
loopback
show statistics
show status
vc
vt1-5
Specifies VT-1.5 as Sonet Channelized format
clear-statistics
loopback
show statistics
4-16

Command
Description
show status
vc
rdi-on-failure
Enables/disables triggering RDI on failure
shutdown
speed
Selects the port speed
show statistics
show status
Displays the status of SDH-SONET port
threshold
Bit error rate above which an alarm is triggered
tim-response
Enables/disables triggering RDI on path trace error
tx-ssm
serial
Define serial paramters
activation-type
Define the ISDN activation mode of a port configured for

operation in the NT-I mode
clock-mode
Define the clock mode in the synchronous mode
cts-rts
Selects the state of the local CTS line
data-bits
Define the number of data bits
encapsulation-mode
Define the encapsulation mode according to the user

application in the HDLC model
end-to-end-control
Define the end-to-end transmission of the local DTR and

RTS lines
fifo-size
Selects the size of the FIFO buffer used by the channel
interface
Define the ISDN function of the port
llb
Define the activation of a local loopback
loopback
mode
Selects the protocol used by the data channel
name
Port name
parity
Define the end-to-end transfer of the parity bit
rate
Define the channel data rate for HSN cards
rate-adaptive
Define multiplexing and rate adaptation method
rlb
Define the activation of a remote loopback
shutdown

form of this command administratively enables a port
stop-bits
Define the number of stop bits
serial-bundle

Define serial bundle
4-17
Command
Description
bind
Bind HSU D-channels or LS-6N/12 external channels to

this port
loopback
name
Port name
rate
Define the rate
shutdown

form of this command administratively enables this port
shdsl
Defines an SHDSL port
clear-statistics
clock-mode
current-margin
Enables/disables up-/downstream curr. cond. SNR
data-rate
Specifies the data rate range
far-end-type
line-prob
Enables/disables Power Measurement Modulation Session
loop-attenuation-threshold
Specifies the loop attenuation threshold in db
loopback
name
power-backoff
Time of reduced power to counter magnetic fields
remote-ch1-ts-num
repeater
| |
loopback
Activates remote loopback on a selected SHDSL repeater
| |
show statistics running
Displays the statistics on a selected SHDSL repeater
| show status
Displays the status of a selected SHDSL repeater
snr-margin-threshold
Sets the current signal-to-noise margin
show statistics
Displays the statistics of an SHDSL interface
show status
Displays the status of an SHDSL interface
stu
Indicates whether the unit is a CPE or a CO unit
tc
Specifies the TC layer and functional mode
ts-compaction-mode
wires
Specifies number of wires for M-pair group or IMA
worst-margin
Enables/disables up-/downstream worst case SNR
signaling-profile
a-bit-code
b-bit-code
4-18
Defines Signaling profile

Command
Description
c-bit-code
d-bit-code
busy-code
idle-code
show summary
Displays a summary of a port and its parameters
svi
Create/delete service virtual interface
name
Assign name to the SVI port
shutdown
Administrtavly enable/disable the SVI port
t1
clear-statistics
idle-code
Code transm. to fill unused timeslots in T1 frames
inband-management
line-buildout
Specifies the line build out
line-code
Line code and zero suppression used by port
line-interface
Specifies the T1 operation mode
line-length
Specifies the length of the T1 line in DSU mode
line-type
Specifies the T1 framing mode
loopback
name
out-of-service
restoration-time
Time req. for port to resume normal oper after LOF
shutdown
signaling-profile
Specifies the signaling profile
show statistics
Displays the T1 port statistics
show status
Displays the T1 port's status
Specifies the signaling profile per timeslot
vc
Assigning VC profile to the port
t1-i
Specifies internal T1 parameters
clear-statistics
idle-code
Code transm to fill unused timeslots in T1 frames
inband-management
line-type
Specifies the T1 framing mode
loopback
Specifies T1 parameters
4-19
Command
Description
name
out-of-service
restoration-time
Time needed for port to resume oper after LOF
shutdown
show statistics
show status
Displays the E1 port's status
vc
Adds/removes a virtual connection
vcg
Specifies VCG parameters
bind
show bind
lcas
Enable/Disable LCAS
minimum-number-of-links
minimum number of links when working in LCAS
name
Port name
shutdown
show statistics
Displays the VCG port statistics
show status
Displays the VCG port's status
vc-profile
day-threshold
interval-threshold
pathtrace
payload-label
plm-response
rate-threshold
tim-response
voice
analog-signaling
Define the signaling method used for all channels
coding
Define the companding law to be used by the voice

channels
compression
Define the compression method used in the ADPCM

encoding
echo-canceler
Enables/disables the built-in adaptive echo canceller
e-m-type
Define the E&M signaling standard, available only for E&M
impedance-standard
Define Impendance standard
4-20
Defines SDH/Sonet VC profile
The J-path-trace that identifies the circuit is inserted

continuously at source.
sending RDI upon Signal Label Mismatch
sending RDI upon Path Trace

Command
Description
loopback
meter-rate
Define the pulse metering frequency (supported only on

FXS and FXO modules in PCM mode
name
Port name
omni-signaling
Define the end-to-end signaling transfer method for the

OMNI BUS card
operation-mode
Define the operating mode of the OMNI BUS channel
signaling-feedback
Define the use of signaling feedback, available only for

FXO modules
rx-sensitivity
Define the nominal output level of the receive path
shutdown

form of this command administratively enables
signaling
Define the end-to-end signaling transfer method
tx-gain
Define the nominal input level of the transmit path
wires
Define the interface to be used by the voice channels
protection
Defines protection mechanisms
aps
Enables/disables port protection
bind
Adds/removes ports to/from the APS
clear (1+1 optimized bi-directional mode)
Clears the current command (Force Switch or Lockout)
clear (compatible 1+1, unidirectional modes)
Clears all externally initiated switch commands and the

WTR time
flip-upon-sd
Enables/disables the flip of the two ports upon signal

degradation
force-switch
Switches traffic from the active link to the next one (in
1+1 Bi-Optimized Bidirectional mode)
force-switch-to-protection
Switches traffic to the protection port (in Compatible 1+1

or Unidirection mode)
force-switch-to-working
Switches traffic to the working port (in Compatible 1+1 or

Unidirection mode)
lockout
Prevents a possible switch over (in 1+1 Bi-Optimized

Bidirectional mode)
lockout-of-protection
Denies access of traffic to the protection port (in

Comaptible 1+1 mode)
manual-switch
Switches manually traffic from the active link to the next

one
manual-switch-to-protection
Switches traffic to the protection port (in Compatible 1+1

or Unidirection mode)
4-21
Command
Description
manual-switch-to-working
Switches traffic to the working port (in Compatible 1+1 or

Unidirection mode)
oper-mode
Specifies the APS operation mode
revertive
Enables/disables reverting working port and protection

port
shutdown
Switches the APS to standby or re-activates the APS
show status
Displays the APS status
wait-to-restore
Specifies the time to elapse after the link recovers and

before traffic switches back
ethernet-group
Enables/disables ethernet port protection
bind
Add protection and working ports to Eth group.
shutdown
Switches the ethernet group to standby or re-activates it
show status
Display the ethernet group status
wait-to-restore
Specify wait to restore timeout in seconds.
tdm-group
Define tdm protection group
bind
Bind the working/protection port.
oper-mode
Controls the use of port redundancy.
show status
wait-to-restore
tdm-ring
Define tdm protection ring
bind
Bind the working/protection port.
shutdown
Administratively disables/enables the tdm-ring.
show status
wait-to-restore
vc-path
Input/Output card protection group configuration
bind
Bind a card to an IO card group.
name
revertive
Indicates if the mode is revertive or not.
shutdown
Enables/disables an IO card protection group
show status
Display status of Input/Output card protection group.
Specifies the time following the last redundancy switching

(flipping) during which alarms are ignore
Specifies the time following the last redundancy switching

(flipping) during which alarms are ignore
pwe
Create/delete Psaudo-wire
pw
Create/delete Pseudo-wire
4-22
exp-bits
Indicate the MPLS EXP bits for this PW

Command
Description
far-end-type
jitter-buffer
Jitter buffer size
label
The PW label used in the inbound /outbound direction
name
Create/delete PW name
oam
Enable/disable OAM protocol for this PW
peer
The number of the remote peer which terminated this PW
sensitivity
shutdown
Administrativly enable/disable the current PW
show statistics
Display PW statistics counters
show status
Display PW status parameters
tdm-oos
tdm-payload
TDM payload configuration
tos
TOS byte value in the outgoing traffic
tunnel-index
Index of the ingress/egress tunnel definitions for this PW
vlan
Enable/disable VLAN tag on every transmitted packet for

this PW
show pw-summary
qos
Display PWs summary

Quality of service
policer-profile
bandwidth
reporting
|
show active-alarms
show active-alarms-details
Show the active alarms table with time stamp added to

active alarms
show alarm-information
Show detailed information about alarm type
show alarm-list
List all Megaplex-4100 alarms for a specific source IDs and

severity value or of all the alarms available in the system
show alarm-log
Show the log of active and cleared alarms (without

events)
clear-log
Clear any alarm log
show event-information
Show detailed information about event type
show event-list
Show list of all Megaplex-4100 events for a specific

source IDs or of all the events available in the system
show log
Show log of active alarms, cleared alarms and events
router
Configures router parameters
4-23
Command
Description
interface
Create/delete router interface
address
Router interface IP and mask
bind
Binds router interface to physical/logical port
name
Router interface name
shutdown
Administrtavly enable/disable the router interface
show routing-table
Displays the routing table
static-route
Create/delete static route entities
slot
Provision slots card types in the chassis database
card-type
Provision the expected card type in the slot
show card-type
Status of card
reset
Reset the card
system
Configures system parameters
clock
Clock configuration
domain
Clock domain number
clear
Clear the Forced or Manual selection
clear-statistics
Clear statistics for all Clock Sources
force
Forced selection of any configured Clock Source
manual
Manual selection of any configured Clock Source
max-frequency-deviation
Max. allowed frequency error compared to PRC
mode
Auto or Free Run
quality
Clock Quality Level (QL)
source
Clock Source parameters
clear-wait-to-restore
One-time reset of running WTR
hold-off
De-bouncing timeout for Clock Source failure
priority
Clock Source priority
quality-level
QL of the Clock Source
show statistics
Display statistics counters
show status
Display status parameters
wait-to-restore
De-bouncing timeout for Clock Source failure recovery
show status
sync-network-type
The synchronous digital hierarchy type
recovered
Create/delete recovered clock
Network type of the recovered clock
4-24
network-type
Command
Description
pw
Associate PW number to recovered clock
shutdown
Enable/disable recovered clock
show status
station
Enable/disable station clock
interface-type
Assign station clock interface type
line-code
Assign station clock line code
rx-sensitivity
Station clock received sensitivity
shutdown
Administrtavly enable/disable station clock
show status
tx-clock-source
tx-ssm
contact
Specifies/removes a contact person
date-and-time
Date and time parameters
date
System date
date-format
System date format
time
System time
show date-and-time
Displays current system data and time
show device-information
Displays device information
location
Specifies/removes the location of a device
name
Assigns/removes a name to the device
license
Controls the STM-4/OC-12 functionality
Assign station transmitted clock source
terminal
Defines the Terminal access
baud-rate
Defines the data rate for communication
length
Sets the legth of the terminal screen (in number of rows)
timeout
Specifies the time of inactivity after which the device

disconnects
show cards-summary
Displays installed module summary
Table 4-5. Commands in the File Category

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

to/from remote locations
delete
Deletes a file from the device
dir
Lists all files in the device
4-25
Command
Description
show sw-pack
Displays the upload/download status
show copy
Displays the upload/download status
Table 4-6. Commands in the Version Category

Command
Description
version
Displays software and configuration version numbers
4.3
Working with Telnet and SSH
Typically, the Telnet host is a PC or a Unix station with the appropriate suite of
TCP/IP protocols.
To enable a Telnet host to communicate, it is necessary to assign its IP address
to the management router (1) interface 9999. This interface is configured by
default and connected to the out-of-band Ethernet management port (CONTROL
ETH). After this preliminary configuration, you can use a Telnet host connected to
it directly or via a local area network.
Working with Telnet

Telnet uses the terminal utility screens for configuration. The only difference is
that Telnet management access is possible only after performing a preliminary
configuration of the Megaplex-4100.
To configure router interface #9999 for management:

1. Define IP address of the management interface (#9999).
2. Define the default gateway (static-route 0.0.0.0/0).
mp4100# configure
mp4100>config# router 1
mp4100>config>router(1)>interface(9999)# address 172.18.170.77/24
mp4100>config>router(1)>interface(9999)#exit
mp4100>config>router(1)#commit
3. Enable Telnet access if it is disabled. By default, Megaplex-4100 has Telnet

access enabled.
To enable or disable access via Telnet:

1. At the config>mngmnt# prompt, enter access.
The config>mngmnt>access# prompt appears.
4-26
2.
Type telnet to enable or no telnet to disable Telnet access. The access is

enabled by default.
Using SSH
To prepare for using SSH:

1. If your Megaplex-4100 is not yet configured for management, configure
router interface #9999 as shown above for Telnet (if you already have Telnet
configured, no need to do this).
2. Enable SSH access if it is disabled. By default, Megaplex-4100 has SSH access
enabled.
To enable or disable access via SSH:

2.
Type ssh to enable or no ssh to disable Telnet access. The access is enabled
by default.
3. Connect the Ethernet port of the PC to the CONTROL ETH port of the active
CL module, or to the same LAN the CONTROL ETH port is attached to.
4. Start the SSH client program, and select the following parameters:
Connection type: SSH
IP address: use the preconfigured host IP address
Port: 22 (the default SSH port)
5. Click Open to open the SSH session with the Megaplex-4100.
4-27
6. You will see the log-in prompt: type the prescribed user name, for example,
su, and then press <Enter>.
7. You will see a request for password: enter the prescribed password, for
example, 1234, and then press <Enter>.
8. If login is successful, you will see the main menu.
4.4
Working with RADview
RADview-EMS is a user-friendly and powerful SNMP-based element management

system (EMS), used for planning, provisioning and managing heterogeneous
networks. RADview-EMS provides a dedicated graphical user interface (GUI) for
monitoring RAD products via their SNMP agents. RADview-EMS for Megaplex-4100
is bundled in the RADview-EMS package for PC (Windows-based) or Unix.
For more details about this network management software, and for detailed
instructions on how to install, set up, and use RADview, contact your local RAD
partner or refer to the RADview-EMS User's Manual at the RAD website.
Megaplex-4100 can be also managed by the RV-SC/TDM service management
application.
4.5
Working with 3rd Party Network Management

Systems
Megaplex-4100 can be integrated into 3rd-party management systems at

different levels:
4-28
Viewing device inventory and receiving traps (see Chapter 6 for trap list)
Managing device, including configuration, statistics collection, diagnostics,

using standard and private MIBs:
IANAifType-MIB
IEEE8023-LAG-MIB
MEF-R MIB
RAD private MIB
RFC 2819 (RMON-MIB)
RFC 2863 (IF-MIB)
RFC 3273 (Remote Network Monitoring MIB)
RFC 3411 (SNMP-FRAMEWORK-MIB)
RFC 3413 (SNMP-TARGET-MIB)
RFC 3414 (SNMP-USER-BASED-SM-MIB)
RFC 3415 (SNMP-VIEW-BASED-ACM-MIB)
RFC 3418 (SNMPv2-MIB)
Working with 3rd Party Network Management Systems
RFC 3636 (MAU-MIB)
RFC 4668 (RADIUS-AUTH-CLIENT-MIB)
RFC 4836.MIB (MAU-MIB)
RFC 3592 SONET MIB
RFC 4319 SHDSL2-SHDSL-LINE-MIB
RFC 4805 DS1-MIB.
4-29
4-30
Chapter 5
Configuration
This chapter lists the commands used to configure Megaplex-4100 and explains
their parameters.
For a list of commands and their context, refer to Chapter 3.
5.1
Services
Both carriers and transportation and utility services providers can benefit from
Megaplex-4100 capabilities.
The services for carriers and service providers (TDM and/or ETH grooming) are as
follows:
Aggregation Services:
TDM (E1/T1) service aggregation over copper/fiber lines into SDH/SONET

backbone
TDM (E1/T1) service aggregation over copper/fiber lines into PSN

backbone
TDM (E1/T1) and Ethernet service aggregation over copper/fiber lines into
SDH/SONET backbone
SDH/SONET and PSN backbone (TDM to TDM, Ethernet to PSN)
PSN backbone
Ethernet-service aggregation over copper/fiber lines into PSN.
Cross-connect services:
Legacy (Voice, serial, ISDN) services cross-connect for interbranch

connectivity
Multiplexing any traffic (Legacy/TDM/Ethernet) for cross-connect services.
Transportation and utility services provided by Megaplex-4100 include:
Legacy and new Ethernet-based service aggregation to SDH/SONET

backbones
Legacy and new Ethernet-based service aggregation to SDH/SONET and PSN

backbones (keeping mission-critical services towards the TDM backbone)
Legacy and new Ethernet-based service aggregation to PSN backbones
Resilient ring topology for legacy and Ethernet services with minimal
downtime.
Services
5-1
Chapter 5 Configuration
5.2
Terminal Control
All the Megaplex-4100 supervision and configuration functions, and in particular

the preliminary configuration activities, can be performed using a dumb ASCII
terminal (or a PC running a terminal emulation program) directly connected to the
Megaplex-4100 serial RS-232 asynchronous supervisory port, located on its front
panel. The terminal is controlled by the program stored in the Megaplex-4100. No
information has to be stored in the terminal.
Standards
The control port complies with the EIA RS-232/ITU-T V.24 standards.
The supervisory port enables the preliminary configuration of the Megaplex-4100.
After the preliminary configuration is completed, Megaplex-4100 can also be
managed by the other means, for example, Telnet hosts and SNMP network
management stations.
The supervisory port has a DCE interface, and supports data rates in the range of
9.6 to 115.2 kbps.
The terminal control parameters determine the control port's baud rate,
password used for each control session, and availability of the fixed security
timeout.
The following parameters can be configured for the control ports:
Note
Data rate
Security timeout
Length of the screen from which you are accessing the device.
Terminal parameters can only be configured when using a terminal connection.
Factory Defaults
Megaplex-4100 is supplied with the control port enabled. Other parameter
defaults are listed in the table below.
Parameter
Default Value
baud-rate
9600 bps
timeout
10
Configuring Control Port Parameters
To configure the terminal parameters:
5-2
At the config>terminal# prompt, enter the necessary parameters according to

the table below.
Terminal Control
Task
Command
Comments
Setting the baud rate (bps)
baud-rate {9600bps | 19200bps |

38400bps | 57800bps | 115200bps}
Enabling and defining a security

timeout (in minutes)
timeout limited <timeout in minutes>
Possible values are 0 to 60.
To specify the number of rows to

display
length <number-of-rows>
The number of rows can be 0,

to indicate no limit on the
number of lines displayed, or
20.
Disabling the security timeout
timeout forever
For example:
To set up a terminal connection at 19200 kbps with timeout after 10 minutes:
Set up the baud rate to 19200 kbps and make sure that the same rate is
selected in HyperTerminal for any future HyperTerminal connections.
Set the security timeout to 10 minutes.
mp4100>config>terminal# baud-rate 19200bps

mp4100>config>terminal# timeout-limited 10
5.3
Programming Modules in the Chassis
To operate properly, each module should be programmed in the MP-4100 chassis.

You can program modules even if they are not installed in the chassis. Use the
following procedure to program modules in the Megaplex-4100 chassis.
Configuring Modules in the Chassis
To program modules in the Megaplex-4100 chassis:

Navigate to configure slot <slot>.
The config>slot<slot># prompt is displayed.
Use the card-type command to perform the tasks listed below.
Use the no card-type command to delete a module from the Megaplex-4100
database.
Task
Command
Comments
Defining power supply modules
card-type power-supply ps
Slots: ps-a, ps-b

Using no card-type removes the
selection
5-3
Task
Command
Comments
Defining common logic modules
card-type cl {cl2-622gbe | cl2622gbea }
Slots: cl-a, cl-b

cl2-622gbe CL.2 module with 2 GbE
ports and 2 STM-1/OC-3 or
STM-4/OC-12 links
cl2-622gbe/a CL.2 module with 2

GbE ports (possibility of upgrade to
advances Ethernet capabilities) and 2
STM-1/OC-3 or STM-4/OC-12 links

selection
Defining M8E1/M8T1/M16E1/M16T1
modules
card-type e1-t1 {m8e1 | m8t1

| m16e1 | m16t1}
Defining high speed modules
card-type high-speed {hs12n |

hs6n | hsf2 | hs703}
Defining ISDN modules
Defining low speed modules
Defining voice modules
Defining Optimux modules
Defining SHDSL modules
Defining pseudowire modules
card-type isdn {hsu12 | hsu6 |

hss}
card-type low-speed {ls6n |

ls12 | hsr-n}
card-type voice {vc4fxs | vc4fxo

| vc4e-m | vc8fxs | vc8fxo |
vc8e-m | vc16fxs | vc16fxo |
vc16e-m | vc4-omni}
card-type optimux {op108c |
op108c-e1 | op34c }
card-type dsl {m8sl | asmi54c |

asmi54c-e1eth}
card-type pw mpw1
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Slots: 1 to 10
selection
Note
The Megaplex-4100 chassis is supplied with a power supply in slot PS-A and a
CL.2 module in slot CL-A configured as factory defaults:
(slot ps-a card-type power-supply ps
slot cl-a card-type cl cl2-622gbe).
5-4
Example
To configure a chassis with:
Two power supply modules
Two CL.2 modules
One ASMi-54C/N module in slot 6
Five M8E1 modules in slots 15.
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
config
config
config
config
config
config
config
config
config
config
slot
slot
slot
slot
slot
slot
slot
slot
slot
slot
ps-a card-type ps-a power-supply ps

ps-b card-type ps-b power-supply ps
cl-a card-type cl cl2-622gbe
cl-b card-type cl cl2-622gbe
1 card-type e1-t1 m8e1
6 card-type dsl asmi54c-e1eth
To delete the ASMi-54C/N module in slot 6 from the database:

mp4100>config# slot 6 no card-type
Displaying Modules in the Chassis

You can display information on the following:
Modules installed in the chassis: show cards-summary command
Module programmed in the specific slot: info or show card-type command
All the parameters configured in the database (per chassis): info detail
command.
To display the modules installed in the chassis:
At the config# prompt, enter the show cards-summary command.
5-5
mp4100>config# show cards-summary

Slot Family
Type
HW Ver
SW Ver
---------------------------------------------------------------------------PS-A Power Supply ps
Undefined Undefined
PS-B Not Installed-Undefined Undefined
CL-A CL
CL2 622GbE
0.0/ 0.0 3.00P14/ 0
CL-B Not Installed-Undefined Undefined
1
Optimux
OP-34C
1
1.50A0
2
Optimux
OP-34C
1
1.50A0
3
Optimux
OP-34C Eth E1
1
1.50A0
4
E1-T1
M8 E1
1
1.69
5
E1-T1
M16 E1
1
1.50
6
E1-T1
M8 T1
1
1.69
7
Optimux
OP-108C
2
2.UNDEF
8
Optimux
OP-108C
2
2.UNDEF
9
E1-T1
M16 T1
1
1.50
10
High Speed
HS6N
2
6.00
To display information on the module programmed in the slot:
At the slot# prompt, enter the info command.
MP4100>config>slot(1)# info
card-type e1-t1 m8t1
OR
At the slot# prompt, enter the show card-type command.
MP4100>config>slot(1)# show card-type

Family : E1-T1
Type
: M8 E1
HW Ver : 1
SW Ver : 1.73
To display information on all the parameters configured in the database (per

chassis):
5-6
At the config# prompt, enter the info detail command.
mp4100# configure info detail

echo "Management configuration"
#
Management configuration
management
echo "SNMP Configuration"
#
SNMP Configuration
snmp
snmp-engine-id mac 00-00-00-00-00-00
no snmpv3
exit
more..
echo "RADIUS"
#
RADIUS
radius
server 1
exit
server 2
exit
server 3
exit
server 4
exit
exit
exit
echo "Slot Configuration"
#
Slot Configuration
slot ps-a
card-type power-supply ps
exit
#
Slot Configuration
more..
slot ps-b
exit
#
Slot Configuration
slot cl-a
card-type cl cl2-622gbe
exit
#
Slot Configuration
slot cl-b
exit
#
Slot Configuration
slot 1
card-type voice vc4e-m
exit
#
Slot Configuration
slot 2
exit
#
Slot Configuration
slot 3
more..
exit
#
Slot Configuration
slot 4
exit
#
Slot Configuration
slot 5
5-7
exit
Slot Configuration
slot 6
exit
#
Slot Configuration
slot 7
exit
#
Slot Configuration
slot 8
exit
more..
#
Slot Configuration
slot 9
exit
#
Slot Configuration
slot 10
exit
echo "System Configuration"
#
System Configuration
system
echo "Clock Configuration"
#
Clock Configuration
clock
echo "Station Clock Configuration"
#
Station Clock Configuration
station 1
exit
exit
exit
more..
echo "QoS - Configuration"
#
QoS - Configuration
qos
echo "Policer Profile configuration"
#
Policer Profile configuration
policer-profile "Policer1"
exit
exit
echo "Port Configuration"
#
Port Configuration
port
echo "Signaling Profile Configuration"
#
Signaling Profile Configuration
signaling-profile ""
exit
#
exit
#
exit
#
exit
#
#
5-8
exit
echo "Ethernet - Port Configuration"
Ethernet - Port Configuration
ethernet cl-a/1
no policer
exit
Ethernet - Port Configuration
ethernet cl-a/2
no policer
exit
echo "Managment Ethernet - Port Configuration"
Managment Ethernet - Port Configuration
mng-ethernet cl-a/1
exit
echo "E1 Internal - Port Configuration"
E1 Internal - Port Configuration
e1-i cl-a/1
exit
e1-i cl-a/2
exit
e1-i cl-a/3
#
exit
#

e1-i cl-a/4
exit
e1-i cl-a/5
exit
e1-i cl-a/6
no shutdown
more..
#
more..
#
#
exit
E1 Internal - Port
e1-i cl-a/7
no shutdown
exit
E1 Internal - Port
e1-i cl-a/8
exit
E1 Internal - Port
e1-i cl-a/9
exit
E1 Internal - Port
e1-i cl-a/10
exit
E1 Internal - Port
e1-i cl-a/11
exit
E1 Internal - Port
e1-i cl-a/12
exit
Configuration
Configuration
Configuration
Configuration
Configuration
Configuration

e1-i cl-a/13
exit
5-9
more..
#
#
more..
more..
#
5-10
e1-i cl-a/14
exit
E1 Internal e1-i cl-a/15
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
more..
#
e1-i cl-a/33
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
exit
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
Port Configuration
more..
no shutdown
exit
E1 Internal - Port
e1-i cl-a/47
no shutdown
exit
E1 Internal - Port
e1-i cl-a/48
exit
E1 Internal - Port
e1-i cl-a/49
exit
E1 Internal - Port
e1-i cl-a/50
exit
E1 Internal - Port
e1-i cl-a/51
exit
Configuration
Configuration
Configuration
Configuration
Configuration
5-11
#
more..
5-12

e1-i cl-a/52
exit
e1-i cl-a/53
exit
e1-i cl-a/54
exit
e1-i cl-a/55
exit
e1-i cl-a/56
exit
e1-i cl-a/57
exit
e1-i cl-a/58
exit
e1-i cl-a/59
exit
e1-i cl-a/60
exit
e1-i cl-a/61
exit
e1-i cl-a/62
exit
e1-i cl-a/63
exit
echo "Voice - Port Configuration"
Voice - Port Configuration
voice 1/1
no shutdown
signaling cas
exit
voice 1/2
no shutdown
signaling cas
exit
voice 1/3
no shutdown
signaling cas
no shutdown
signaling cas
exit
voice 1/4
no shutdown
signaling cas
exit

voice 2/1
no shutdown
signaling cas
more..
#
exit
voice 2/2
no shutdown
signaling cas
exit
voice 2/3
no shutdown
signaling cas
exit
voice 2/4
no shutdown
signaling cas
exit
voice 3/1
no shutdown
signaling cas
more..
#
exit
voice 3/2
no shutdown
signaling cas
exit
voice 3/3
no shutdown
signaling cas
exit
voice 3/4
no shutdown
signaling cas
exit
voice 4/1
no shutdown
signaling cas
more..
#
exit
voice 4/2
no shutdown
signaling cas
exit
voice 4/3
no shutdown
signaling cas
exit
voice 4/4
5-13
no shutdown
signaling cas
#
exit
voice 5/1
no shutdown
signaling cas
more..
#
exit
voice 5/2
no shutdown
signaling cas
exit
voice 5/3
no shutdown
signaling cas
exit
voice 5/4
no shutdown
signaling cas
exit
voice 6/1
no shutdown
signaling cas
more..
#
exit
voice 6/2
no shutdown
signaling cas
exit
voice 6/3
no shutdown
signaling cas
exit
voice 6/4
no shutdown
signaling cas
exit
voice 7/1
no shutdown
signaling cas
more..
#
5-14
exit
voice 7/2
no shutdown
signaling cas
exit
voice 7/3
no shutdown
signaling cas
exit
voice 7/4
no shutdown
signaling cas
exit
voice 8/1
no shutdown
signaling cas
more..
#
exit
voice 8/2
no shutdown
signaling cas
exit
voice 8/3
no shutdown
signaling cas
exit
voice 8/4
no shutdown
signaling cas
exit
voice 9/1
no shutdown
signaling cas
more..
#
exit
voice 9/2
no shutdown
signaling cas
exit
voice 9/3
no shutdown
signaling cas
exit
voice 9/4
no shutdown
signaling cas
exit
voice 10/1
no shutdown
signaling cas
exit
voice 10/2
no shutdown
signaling cas
exit
voice 10/3
5-15
no shutdown
signaling cas
#
exit
voice 10/4
no shutdown
signaling cas
exit
echo "SDH/Sonet - Port Configuration"
SDH/Sonet - Port Configuration
sdh-sonet cl-a/1
exit
SDH/Sonet - Port Configuration
sdh-sonet cl-a/2
exit
exit
echo "Cross Connect"
#
Cross Connect
cross-connect
ds0 e1-i cl-a/6 ts
ds0 e1-i cl-a/6 ts
ds0 e1-i cl-a/6 ts
ds0 e1-i cl-a/6 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
more..
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/7 ts
ds0 e1-i cl-a/46 ts
ds0 e1-i cl-a/46 ts
ds0 e1-i cl-a/46 ts
ds0 e1-i cl-a/46 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
more..
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
ds0 e1-i cl-a/47 ts
5-16
3
4
7
8
1
2
5
6
9
10
13
14
18
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
9/2
9/4
10/2
10/4
1/2
1/4
2/2
2/4
3/2
3/4
4/2
4/4
5/2
19
22
23
26
27
30
31
3
4
7
8
1
2
5
6
9
10
13
14
18
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
voice
5/4
6/2
6/4
7/2
7/4
8/2
8/4
9/1
9/3
10/1
10/3
1/1
1/3
2/1
2/3
3/1
3/3
4/1
4/3
5/1
19
22
23
26
27
30
voice
voice
voice
voice
voice
voice
5/3
6/1
6/3
7/1
7/3
8/1
ds0 e1-i
sdh-sonet
sdh-sonet
sdh-sonet
sdh-sonet
cl-a/47 ts 31 voice 8/3

vc12-vt2 cl-a/1/1/2/1/1 e1-i
vc12-vt2 cl-a/1/1/1/7/2 e1-i
vc12-vt2 cl-a/2/1/2/1/1 e1-i
vc12-vt2 cl-a/2/1/1/7/2 e1-i
cl-a/46
cl-a/47
cl-a/6
cl-a/7
exit
router 1
exit
router 2
exit
echo "Port Configuration"
Port Configuration
port
echo "SDH/Sonet VC Profile Configuration"
SDH/Sonet VC Profile Configuration
vc-profile "tug-structure"
exit
vc-profile "hvc-laps"
payload-label 0x18
exit
vc-profile "hvc-gfp"
payload-label 0x1b
exit
vc-profile "lvc-eos"
payload-label 0x05
exit
exit
5.4
Management Ethernet Ports
Megaplex-4100 has one management Ethernet port (CONTROL ETH) located on

each CL.2 module panel and used for connection to a management station or
Telnet host.
The following parameters can be configured for the management Ethernet port:
Port name
Administrative status.
To configure the Management Ethernet port parameters:

1. Navigate to configure port mng-ethernet <slot>/<port> to select the
Ethernet port to configure.
The config>port>mng-ethernet>(<slot>/<port>)# prompt is displayed.
Enter all necessary commands according to the tasks listed below.
Task
Command
Comments
Assigning short description to port
name <string>
Using no before name removes the name
Administratively enabling port
no shutdown
Using shutdown disables the port
Management Ethernet Ports
5-17
5.5
User Ethernet Ports
Megaplex-4100 has two fiber optic or copper Gigabit Ethernet network ports on
each CL.2 module and various fiber-optic/copper external Fast Ethernet user ports
on several I/O modules. Optimux modules, in addition to external Ethernet ports,
also have internal Ethernet ports, serving to increase the total payload and
management bandwidth transferred to the optical link.
Standards
The GbE ports comply with 10/100/1000BASE-T, 100BASE-FX, 1000BASE-X
standards. Fast Ethernet ports comply with 10/100BaseT (copper) and 100BaseFx
(fiber) standards.
GbE Port Interfaces
The GbE ports provide the physical connection to the packet switched network.
These ports can be ordered with one of the following interfaces:
10/100/1000BASE-T copper ports. This type of ports support

auto-negotiation, with user-specified advertised data rate (10, 100 or
1000 Mbps) and operating mode (half- or full-duplex).
The ports also support automatic polarity and crossover detection, and
polarity correction, for connection through any type of cable to any type of
Ethernet port (hub or station).
Alternatively, auto-negotiation can be disabled and the rate and operating
mode be directly specified.
SFP sockets, for installing SFP plug-in modules. Support for standard SFP
optical transceivers for the GbE link interfaces enables selecting the optimal
interface for each application. This type of ports should be configured to
operate without autonegotiation, in the 1000 Mbps full duplex mode.
Fast Ethernet Port Interfaces

The external Ethernet ports have 10/100 Mbps interfaces capable of
auto-negotiation. The user can configure the advertised data rate (10 or
100 Mbps) and operating mode (half-duplex or full-duplex). Alternatively,
auto-negotiation can be disabled, and the rate and operating mode be directly
specified.
The Ethernet ports can be ordered with one of the following types of interfaces:
5-18
Sockets for SFP Fast Ethernet transceivers. RAD offers several types of SFPs
with optical interfaces, for meeting a wide range of operational requirements
(SFPs with copper interfaces are also available). The SFPs are hot-swappable.
10/100BASE-TX interfaces terminated in RJ-45 connectors. In addition to

auto-negotiation, MDI/MDIX polarity and cross-over detection and automatic
cross-over correction are also supported. Therefore, these ports can always
User Ethernet Ports
be connected through a straight (point-to-point) cable to any other type of

10/100BASE-T Ethernet port (hub or station).
The ordering options depend on the specific I/O module.
The following table shows the number of Ethernet ports on each Megaplex-4100
module, their CLI denomination, hierarchy and possible values. The hierarchical
position of external Ethernet ports is slot:port for all the modules. The internal
Ethernet ports of the Optimux modules are designed as slot:port:tributary (in
these modules port=mux_eth_tdm).
Table 5-1. Ethernet Ports on I/O Modules

Modules
CLI Name
Hierarchy
Possible Values
M8E1, M8T1, M8SL
ethernet
slot: port
1..3
OP-108C, OP-108C/E1,
ethernet
slot:port
1..2
int-eth
slot:port:tributary
1/1, 3/1
OP-34C
ethernet
slot:port
int-eth
slot:port:tributary
1/1
ASMi-54C,
ASMi-54C/N
ethernet
slot:port
1..2
For more information, see the respective module section in Appendix B.
Flow Control
The user can enable flow control for the Ethernet ports. When flow control is
enabled, it is always activated only on the port (or ports) involved in congestion:
other ports are not affected.
Flow control is available in both the half-duplex and full-duplex modes:
In half-duplex mode, flow control uses a collision-based scheme to throttle

the connected stations when the free buffer space of the corresponding port
is too low, to avoid discarding frames during network congestion (this
approach is called back pressure). When the buffer space of a port is almost
full, its MAC controller forces a collision in the input port when an incoming
frame is sensed (the alternative, without flow control, is to discard the
incoming frame).
In full-duplex mode, the standard flow control method defined in IEEE 802.3x
is used, which is based on pause frames and enables stopping and restoring
the transmission from the remote node. However, this method can only be
used when auto-negotiation is enabled on the port, and the node attached
to the port supports pause frames.
User Ethernet Ports
5-19
The Ethernet switch internal MAC controllers discard all the received IEEE 802.3x
pause frames, even when full-duplex flow control is disabled or the port is in the
half-duplex mode.
Factory Defaults
Megaplex-4100 is supplied with all Ethernet ports disabled. Other parameter
Parameter
Default Value
max-capability
100-full-duplex
speed-duplex
100-full-duplex
flow-control
Disabled
auto-negotiation
Enabled
Configuring User Ethernet Port Parameters
To configure the user Ethernet port parameters (any module with Ethernet ports):
1. Navigate to configure port ethernet <slot>/<port> to select the Ethernet port
to configure.
The config>port>eth>(<slot>/<port>)# prompt is displayed.
Enter all necessary commands according to the tasks listed in the table below.
Task
Command
Comments
Assigning short description to

port
name <string>
Using no name removes the name
no shutdown
Enabling autonegotiation
auto-negotiation
Using no auto-negotiation disables

autonegotiation
Setting maximum advertised

capability (highest traffic handling
capability to be advertised during
the autonegotiation process)
max-capability {10-full-duplex |
100-full-duplex | 1000-full-duplex
| 10-half-duplex |
100-half-duplex}
10-full-duplex 10baseT full duplex

1000-full-duplex 1000base T full duplex
(GbE ports only)
10-half-duplex 10baseT half duplex
For fiber optic ports, permanently set to
1000-x-full-duplex
This parameter applies only if
autonegotiation is enabled.
5-20
User Ethernet Ports
Task
Command
Comments
Setting data rate and duplex

mode of the Ethernet port, when
autonegotiation is disabled
speed-duplex {10-full-duplex |
100-full-duplex |1000-full-duplex |
10-half-duplex |100-half-duplex |
1000-x-full-duplex}

1000-full-duplex 1000base T full duplex
(GbE ports only)
For fiber optic ports, permanently set to
1000-x-full-duplex
This parameter applies only to RJ-45 copper
ports.
Setting flow control for the

selected port (when operating in
the full duplex mode), or back
pressure (when operating in the
half-duplex mode)
flow-control
Using no flow-control disables flow control
Activating/deactivating a policer
profile
policer-profile <name>
The policer profile is defined under

Configuring Policer Profiles.
Using no policer <name> deactivates this
policer profile
To configure the internal Ethernet port parameters (Optimux cards only):

1. Navigate to configure port ethernet <slot>/<port>/<tributary> to select the
internal Ethernet port to configure.
The config>port>eth>(<slot>/<port>/<tributary>)# prompt is displayed.
Enter all necessary commands according to the tasks listed in the below.
Task
Command
Comments
name <string>
Using no name removes the

name
no shutdown
Displaying Ethernet Port Status

You can display the status and configuration of an individual external Ethernet
port. Status of internal Ethernet ports of Optimux modules cannot be displayed.
To display status of an Ethernet port:
At the prompt config>port>eth>(<slot>/<port>#, enter show status.

The Ethernet port status parameters are displayed.
For example: Module M8E1, Slot 6, Ethernet port 1, copper SFP-9F

connector.
User Ethernet Ports
5-21
mp4100>config>port>eth(6/1)# show status

Name
:
Administrative Status : Up
Operation Status
: Up
Connector Type
: SFP In
Auto Negotiation
: Enabled
Speed And Duplex
: 100 Half Duplex
MAC Address
: 0020D2501AA3
SFP
--------------------------------------------------------Connector Type
: Copper
Manufacturer Name
: RAD data comm.
Manufacturer Part Number
: SFP-9F
Typical Maximum Range (Meter) : 100
Wave Length (nm)
: Not Applicable
Fiber Type
: Not Applicable
Testing Ethernet Ports

No testing is available.
Displaying Ethernet Port Statistics

The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819. The statistics are available both on external Ethernet ports and
internal Ethernet ports of Optimux modules.
To display the internal Ethernet port statistics on Optimux modules:
At the prompt config>slot>port>eth(<slot>/<port>/<tributary>)#, enter show

statistics:
OP-108C section OP A, OP-34C: <port>/<tributary> = 1/1
OP-108C section OP B: <port>/<tributary> = 3/1
To display the external Ethernet port statistics:
At the prompt config>slot>port>eth(<slot>/<port>)#, enter show statistics.

Ethernet port statistics are displayed. The counters are described in the
table below.
Screens and counters are different for Fast Ethernet ports of I/O modules
and GbE ports of CL.2 modules.
5-22
User Ethernet Ports
M8E1 Module:
mp4100>config>port>eth(8/1)# show statistics
Running
--------------------------------------------------------------Counter
Rx
Tx
Total Frames
0
0
Total Octets
0
0
Unicast Frames
0
0
Multicast Frames 0
0
Broadcast Frames 0
0
Paused Frames
FCS Errors
Filtered Frames
Jabber Errors
Undersize Frames
Oversize Frames
0
0
0
0
0
0
0
------
64 Octets
65-127 Octets
128-255 Octets
256-511 Octets
512-1023 Octets
1024-1528 Octets
0
0
0
0
0
0
-------
CL.2 Module:
mp4100>config>port>eth(cl-a/1)# show statistics
Running
--------------------------------------------------------------Counter
Rx
Tx
Total Frames
0
0
Total Octets
0
0
Unicast Frames
0
0
Multicast Frames
0
0
Broadcast Frames
0
0
Single Collision
Paused Frames
FCS Errors
-0
0
0
0
--
Table 5-2. Ethernet Statistics Parameters

Parameter
Description
Total Frames
Total number of frames received/transmitted
Total Octets
Total number of bytes received/transmitted
Unicast Frames
Total number of unicast frames received/transmitted
Multicast Frames
Total number of multicast frames received/transmitted
Broadcast Frames
Total number of broadcast frames received/transmitted
Note
User Ethernet Ports
5-23
Parameter
Description
Note
Single Collision
The number of successfully transmitted frames on this

interface for which transmission is inhibited by exactly one
collision.
GbE ports only
Paused Frames
Total number of pause frames (used for flow control)

received/transmitted through the corresponding Ethernet port
FCS Errors
The number of frames received on this interface that are an

integral number of octets in length but do not pass the FCS
check
Filtered Frames
Total number of filtered frames received/transmitted
I/O Ethernet ports only
Jabber Errors
Total number of frames received with jabber errors
Oversize Frames
Total number of oversized frames received/transmitted
Undersize Frames
Total number of undersized frames received/transmitted
64 Octets
Total number of received/transmitted 64-byte packets
65127 Octets
128255 Octets
256511 Octets
5121023 Octets
10241528
Octets
Total number of received/transmitted 10241528-byte

packets
Clearing Statistics
To clear the statistics for an Ethernet port:
At the prompt config>port>eth<slot>/<port>)#, enter clear-statistics.

The statistics for the specified port are cleared.
5.6
Flows
The forwarding of Ethernet traffic is controlled by configuring flows that function

as virtual bridges. Megaplex-4100 supports up to 240 unidirectional Ethernet
flows, to provide E-line service delivery over Metro Ethernet networks. Each
Ethernet flow is unidirectional and interconnects two ports.
Traffic and management flows are configured according to the same procedure,
which is described in this section.
5-24
Flows
Ethernet Entities
Ethernet services are provided by means of the Megaplex-4100 I/O modules with
traffic Ethernet ports, which can serve as customers edge network interfaces,
and by means of the CL.2 modules, which provide GbE ports that can serve as
service providers edge interfaces.
The customers edge traffic accepted by Ethernet ports on I/O modules is
directed to other interfaces that can transfer the traffic to the transport
network. These interfaces are as follows:
GbE ports located on the Megaplex-4100 CL.2 modules (ethernet or lag in

the CLI language).
Ethernet ports on other I/O modules (M8E1, M8T1, M8SL, OP-34C, OP-108C,
ASMi-54C, MPW-1) (ethernet in the CLI language)
Logical MAC ports (logical-mac). A Logical MAC port is bound to a gfp, hdlc or
mlppp port, which, in its turn, should be bound to the physical layer. The
meaning of the gfp, hdlc or mlppp ports and their further mapping depends
on the Ethernet traffic media:
GFP ports exist only on CL.2 modules and represent VCGs (Virtual
Concatenation Groups) with GFP encapsulation. They can be mapped
either directly to the physical layer or to VCG. In the latter case the
binding is done in two stages and this VCG should be further bound to
the physical layer
HDLC ports exist in two flavors:
HDLC ports defined on CL.2 modules represent VCGs (Virtual

Concatenation Groups) with LAPS encapsulation. They can be mapped
either directly to the physical layer or to another VCG. In the latter case
the binding is done in two stages and this VCG should be further bound
to the physical layer
HDLC ports defined on M8E1, M8T1 and M8SL modules represent HDLC
bundles which can be bound to the physical layer representing E1/T1
ports or specific timeslots
MLPPP ports exist only on M8E1 and M8SL modules and are mapped to
the PPP port. The binding is done in two stages and this PPP port should
be further bound to the physical layer.
The maximum number of HDLC ports that may be defined on an I/O module
(M8E1, M8T1, or M8SL) is 32.
PCS (Physical Coding Sublayer) ports available on the ASMi-54C/N and

ASMI-54C modules, which determine the Ethernet (packet) physical layer
transmission capabilities over SHDSL lines.
SVI ports intermediate Ethernet entities between the Bridge/Router and

another Ethernet port (bound one-to-one). An SVI port also serves as an
ingress or egress port for terminating management flows. The management
flows are configured between the physical port which is the management
source and the corresponding SVI port bound to the bridge port of the
Flows
5-25
Unaware Management Bridge (see Figure 5-35). For more information on the
bridge connections and configuration see the Management Bridge section.
Each of the above-mentioned interfaces (either customers edge or intranetwork
or service provider interface) is generically referred to as a bridge port. The
Ethernet traffic is forwarded (or flows) among the desired bridge ports in
accordance with user-configured rules that define Ethernet Virtual Connections
(flows). A flow functions as a virtual bridge.
Aware and Unaware Traffic

In general, a given bridge port can serve as the termination point of several flows
(the maximum number of traffic flows that can be defined on a Megaplex-4100 is
250). Therefore, each flow must discriminate among the Ethernet frames (be
aware of the frame VLANs) reaching an associated bridge port in order to
determine how to handle customers edge traffic. In general, this action is based
on the users VLAN identifier (VLAN ID) received in each frame. For untagged or
priority-tagged traffic, a special VLAN ID is automatically assigned by the
Megaplex-4100 for handling the Ethernet traffic.
The range of specific VLAN IDs that can be used for Ethernet traffic with IEEE
802.Q tags is 1 to 4094 (for the management flow, only the range of 1 to 3999
is allowed).
Notes
All incoming VLANs must be with non-repeating ID. The Ingress VLAN ID must
be unique per I/O module (when using ASMi-54C, the ingress VLAN ID must be
unique per system).
Ingress VLAN ID within the 3800-4095 VLAN ID range may not be filtered.
The internal Ethernet switch of the module can also handle other types of
frames, such as untagged frames, and priority-tagged frames (frames with IEEE
802.Q tags with 0 as the VLAN ID). M8E1/M8T1 modules also enable the user to
configure flows to handle traffic with or without IEEE 802.Q tags: this traffic is
forwarded only between the bridge ports mapped to a given flow. This
forwarding mode is usually referred to as VLAN-unaware. In order to transmit
unclassified frames, its classification should be set to match-all.
The following list summarizes the configuration restrictions applying to the types
of flows to which any given bridge port can be mapped:
A bridge port can terminate only one flow classified as unaware (i.e., which
does not discriminate Ethernet traffic in accordance with VLANs).
When a bridge port is mapped to more than one flow, the bridge port can
terminate several flows with specific VLAN IDs, but only one flow classified as
unaware.
A bridge port can terminate flows with different VLAN IDs (aware flow mode).
VLAN tagging, stacking and striping options enable transporting users traffic
transparently, thereby keeping all the users VLAN settings intact.
Classifier Profiles
You can use classifier profiles to specify the criteria for flows. The classification is
per port and is applied to the ingress port of the flow.
5-26
Flows
The ingress user traffic is mapped to the Ethernet flows using the following
per-port classification criteria:
Port-based (All to one bundling)
VLAN.
You have to first configure a classifier profile and then associate it with the
relevant flow in order to distinguish user traffic from traffic that is part of the
flow. Once the classifier profile is configured, you can configure the flow itself.
Once you have finished configuring the classifier profile, you must configure
egress and ingress flows to allow traffic to in both directions.
Tagging and Marking

Megaplex-4100 supports the following tagging and marking actions:
Remove (pop) outer VLAN. When you remove a VLAN, the inner VLAN
becomes the outer VLAN.
Add (push) outer VLAN, with fixed p-bit value.
You can perform tagging actions on the outer and inner VLAN such as adding or
removing, as well as marking with p-bit.
In the descriptions, VLAN refers to the service provider (outer) VLAN, previously
referred to as SP-VLAN, while inner VLAN refers to the Customer Entity VLAN,
previously referred to as CE-VLAN.
Defining Classifier Profiles

You can define up to 240 classifier profiles to apply to flows to ensure the
desired flow classification.
To define a classifier profile:

1. Navigate to the flows context (config>flows).
Define a classifier profile and assign a name to it:
classifier-profile <profile-name> match-any.
The system switches to the context of the classifier profile
(config>flows>classifier-profile(<profile-name>)).
Specify the criteria for the classifier profile:
Flows
5-27
Task
Command
Comments
Specifying a VLAN
classifier profile
match [vlan <vlan number 1.. 4094>]

[inner-vlan <inner-vlan number 1.. 4094>]
Packets belonging to the defined

(outer) VLAN and/or inner VLAN will be
mapped to the flow.
The most common command is match
vlan. match inner-vlan command is
used for vcg ports only. match vlan
inner-vlan command is used for gbe
ports only.
Using no before the command removes
the criterion.
Specifying a classifier
profile that maps all
packets to the flow
match all
All packets will be mapped to the flow.

Using no classifier-profile
<profile-name> removes the criterion.
When you have completed specifying the criteria, enter exit to exit the classifier
profile context.
To remove a classifier profile:
At the config>flows# prompt, enter no classifier-profile < profile-name>.

The relevant classifier profile is removed.
Configuring Flows
To create and configure a flow:

1. Navigate to the flows context (config>flows).
Define a flow and assign a name to it:
flow <flow-name>
The system switches to the respective flow context
(config>flows>flow(<flow-name>))
Specify the flow as explained in the table below.
Task
Command
Comments
Administratively enabling the

flow (the flow is created as
inactive by default)
no shutdown
You can activate a flow only if it is

associated with at least a classifier
profile, ingress port, and egress port.
Using no shutdown disables the flow
Mapping the previously

configured classifier profile to
the flow
classifier <classifier-profile name>
Using no before classifier removes the

mapping
Specifying the egress port

(ethernet, lag, logical-mac, pcs,
svi)
egress-port {ethernet | lag | logicalmac | pcs}<slot><port>
Using no egress-port removes egress

port assignment
5-28
Flows
egress-port svi <port number>
Task
Command
Comments
Specifying the internal

Ethernet egress port for
Optimux modules
egress-port ethernet
<slot><port><tributary>
Optimux cards only
Adding VLAN ID to the flow

with p-bit set to specific value
(related to egress port)
vlan-tag push vlan <sp-vlan> p-bit

fixed <fixed-p-bit>
Using no vlan-tag disables the

pushing
Removing VLANs (related to

egress port)
Using no egress-port removes egress

port assignment
When a flow is established between a

PCS port of ASM-54C/ETH module and
any other port, the VLAN/classifiers
configured at the egress and ingress
ports must be identical.
vlan-tag pop vlan
Using no vlan-tag pop cancels the

VLAN removal
Specifying the ingress port

(ethernet, lag, logical-mac, pcs,
svi)
ingress-port {ethernet | lag |

logical-mac | pcs}<slot><port>
Using no ingress-port removes ingress

port assignment
Specifying the internal

Ethernet ingress port for
Optimux modules
ingress-port ethernet
ingress-port svi <svi port

number>
Optimux cards only
Using no ingress-port removes ingress
port assignment
Example
This section provides an example of creating two management flows between
PCS ports of an ASMi-54C module installed in slot 3. The procedure is as follows:
1. Create two flow classifiers:
Create an ingress flow 1 between PCS port 1 of the ASMi-54C module and SVI
port 2 using the following parameters:
Flow 1
Classifier named mng_flow_bridge_side
Tagging of the management traffic with VLAN 100, priority bit 7
Set SVI 2 as ingress port.
Set PCS 3/1 as egress port.
Create an egress flow 2 between PCS port 1 of an ASMi-54C module and SVI port
2 using the following parameters:
Flow 2.
Classifier named mng_flow_port_side
Removing VLAN before entering management bridge (management bridge

is unaware bridge)
Set SVI 2 as egress port.
Set PCS 3/1 as ingress port.
Flows
5-29
#Step 1
mp4100>config>flows# classifier-profile mng_flow_port_side matchany match vlan 100
mp4100>config>flows# classifier-profile mng_flow_bridge_side
match-any match all
#Step 2
mp4100>config>flows#
flow
flow
flow
flow
1
1
1
1
classifier mng_flow_bridge_side
vlan-tag push vlan 100 p-bit fixed 7
ingress-port svi 2
egress-port pcs 3/1
#Step 3
flow
flow
flow
flow
2
2
2
2
classifier mng_flow_port_side
vlan-tag pop vlan
ingress-port pcs 3/1
egress-port svi 2
Viewing the Flow Summary

You can view a summary of the flows you just configured.
To view the flows summary:
At the config>flows# prompt, enter info detail.

The summary of all configured flows appears.
5-30
Flows
mp4100>config>flows# info detail

echo "Classifier Profile Configuration"
#
Classifier Profile Configuration
classifier-profile "mng" match-any
match vlan 100
exit
#
Classifier Profile Configuration
classifier-profile "all" match-any
match all
exit
echo "Flow Configuration"
#
Flow Configuration
flow "241"
classifier "mng"
vlan-tag pop vlan
ingress-port ethernet 1/1
egress-port svi 2
no shutdown
exit
#
Flow Configuration
flow "242"
classifier "all"
vlan-tag push vlan 100 p-bit fixed
ingress-port svi 2
egress-port ethernet 1/1
no shutdown
Testing the Flows

Flow testing and statistics are not supported.
5.7
Quality of Service (QoS)
The Megaplex-4100 Quality of Service (QoS) includes bandwidth policer profiles.

These profiles can be applied to the traffic flows to ensure the desired flow
prioritization. You can define up to 30 policer profiles.
The main use of policer profiles in Megaplex-4100 is for Optimux modules to
control the rate of the ingress frames from the remote device. This is done by
defining the committed information rate (CIR) in policer profiles. The CIR specifies
the highest bandwidth (rate) of the ingress frames from the remote device.
Possible values are 0 to 100 000 kbps (100 Mbps). Frames that are over the
ingress rate limit are dropped.
Factory Defaults
Megaplex-4100 provides a default bandwidth profile Policer 1, with
CIR=1000 kbps.
5-31
Configuring Policer Profiles

Adding Policer Profiles
1. Navigate to configure qos.
The config>qos# prompt is displayed.
Type policer-profile <policer-profile-name>.
A policer profile with the specified name is created and the following
prompt is displayed: config>qos>policer-profile(<policer-profile-name>)#.
The new policer profile parameters (except for name) are configured by
default as described in Factory Defaults.
Configure the policer profile as described below.
Configuring Policer Profiles

1. Navigate to configure qos policer-profile <policer-profile-name> to select the
policer profile to configure.
The config>qos>policer-profile(<policer-profile-name>)# prompt is
displayed.
2. Enter the bandwidth [cir <value in kbps>] command to specify the CIR (kbps)
bandwidth. Typing no bandwidth removes the bandwidth limits. The CIR
granularity is 1, 2, .. 10, 20, 30, up to 100,000 kbps.
Note
CIR values of 70,000 kbps and 90,000 kbps are not available for OP-108C
modules. Use 60,000 kbps or 80,000 kbps if these bandwidth limits are needed.
Example 1
The procedure is as follows:
1. Create and configure a policer profile named policer4, setting a rate limitation
of 12 Mbps
2. Assign the created policer profile to:
5-32
ASMi-54C/ETH module installed in slot 2
Ethernet port 1
#Creating the policer profile (Step 1)

mp4100>config>qos# policer-profile policer4 bandwidth cir 12000
#Displaying the policer profile
mp4100>config>qos# info detail
#
policer-profile "policer4"
bandwidth cir 12000
#Assigning the policer profile (Step 2)
mp4100>config>port# eth 2/1
mp4100>config>port>eth(2/1)# policer profile policer4
#Displaying the result
mp4100>config>port>eth(2/1)# info detail
name "ASMI-54C ETH -7"
no shutdown
auto-negotiation
max-capability 100-full-duplex
no flow-control
policer profile "policer4"
Example 2
The procedure is as follows:
1. Create and configure a policer profile named 108c, setting a rate limitation of
10 Mbps (frames that are over this ingress rate limit are dropped)
2. Assign the created policer profile to:
OP-108C module installed in slot 3
Remote Optimux-108 connected to Section OP A.
#Creating the policer profile (Step 1)

mp4100>config>qos# policer-profile 108c bandwidth cir 10000
#Displaying the policer profile
mp4100>config>qos# info detail
#
policer-profile "108c"
bandwidth cir 10000
#Assigning the policer profile (Step 2)
mp4100>config>port# mux-eth-tdm 3/1 remote
mp4100>config>port> mux-eth-tdm (3/1)remote#
configure port ethernet 1 policer profile 108c
5-33
5.8
SHDSL Ports
The SHDSL ports are available on the M8SL and ASMi-54C family I/O modules. The
ASMi-54C includes three main modules:
ASMi-54C/ETH Ethernet over SHDSL.bis 8-port module with EFM support
ASMi-54C/E1/N - E1 over SHDSL 8-Port module
ASMi-54C/E1/ETH/N E1 and Ethernet over SHDSL/SHDSL.bis 8-port module

(with optional remote power feeding support).
The following table shows the number of SHDSL/SHDSL.bis ports and the features
supported by each Megaplex-4100 module. The digits in brackets (1 to 5) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Note
ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules have the same features for their
SHDSL ports; in this section they are denoted as ASMi-54C/N, to distinguish from
the older ASMi-54C/ETH version. The generic term ASMi-54C is used when the
information is applicable to all of the ASMi-54C models.
Table 5-3. Features Supported by Megaplex-4100 SHDSL/SHDSL.bis Ports
Feature/Command
ASMi-54C/ETH
ASMi-54C/E1/N,
M8SL
ASMi-54C/E1/ETH/N
Number of ports
name
shutdown
far-end-type
asmi54 (ASMi-54 or ASMi-
(5)
asmi52 (ASMi-52 or ASMi-52L
54L standalone)
standalone)
asmi54-eoc (ASMi-54L
standalone)
asmi52-e1-dte (ASMi-52 standalone
standalone configurable
asmi52-e1-eth (ASMi-52
with E1 and serial ports (Mux type))
via EOC)
standalone with E1 and LAN
asmi52-e1-eth (ASMi-52 standalone
ports (Mux type))
with E1 and LAN ports (Mux type))
asmi52-eth-dte (ASMi-52 standalone
standalone)
with serial and LAN ports (Mux type))
mp-card (M8SL module installed in
standalone configurable via
MP-4100 unit)
EOC, ASMi-54C/E1/ETH/N
fcd-ip (FCD-IP device)
module only)
dxc (equipment from the
asmi52-e1-dte (ASMi-52
DXC-8R/10A/30 family of multiservice
standalone with E1 and serial
access nodes
ports (Mux type))

high-speed-mux-serial-e1
(ASMi-52 standalone with E1
and serial ports (Mux type),
4M/4W functionality)
stu
5-34
SHDSL Ports
(1)
Feature/Command
ASMi-54C/ETH
ASMi-54C/E1/N,
M8SL
ASMi-54C/E1/ETH/N
line-prob
data-rate-maximum
tc
(2)
(2)
wires
(3)
power-backoff
current-margin
worst-margin
threshold
clock-mode
remote-ch1-ts-num
ts-compaction-mode
ts0-over-dsl (4)
remote-crc (4)
loop-attenuation-
1 central only
2 HDLC only
3 2 wire only
4 these parameters are configured under e1-i ports
5 ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules cannot work with a mix of ASMi-54 and ASMi-52 modems at the far
end. At every moment, all the remote modems should be either ASMi-54/ ASMi-54L or ASMi-52/ ASMi-52L.
Standards
SHDSL and SHDSL.bis ports comply with ITU-T Rec. G.991.2 and ETSI TS 101 524.
Benefits
The SHDSL/SHDSL.bis technology is an efficient method for transmitting
full-duplex data at high rates over a single unloaded and unconditioned twisted
copper pair, of the type used in the local telephone distribution plant. Therefore,
SHDSL provides a cost-effective solution for short-range data transmission and
last-mile applications.
SHDSL Ports
5-35
SHDSL has been standardized in ITU-T Rec. G.991.2, and has been extended
beyond the original specifications, which called only for support of rates up to
2.312 Mbps per pair. The current SHDSL.bis version, as standardized in ITU-T Rec.
G.991.2, supports variable payload data rates up to 5.696 Mbps (5.7 Mbps line
rate) on a single unloaded and unconditioned twisted copper pair, of the type
used in the local telephone distribution plant. SHDSL.bis includes an extension,
referred to as M-pair, that enables to bond multiple pairs (up to four) to achieve
variable payload rates up to 22.784 Mbps (22.8 Mbps equivalent line rate).
SHDSL Transmission Subsystem Structure

The basic SHDSL transmission subsystem includes two units interconnected by a
single pair of wires, usually a regular unloaded twisted pair. The pair is used for
duplex transmission.
Two different types of SHDSL units are defined by ITU-T Rec. G.991.2:
SHDSL central unit (STU-C), usually located at the network side, at the central
office (CO), which controls the operation of the whole subsystem, supervises
the link setup process and provides the timing reference.
SHDSL remote unit (STU-R), which terminates the line at the user side, on the
customer premises (CPE).
This feature is supported by M8SL and ASMi-54C/ETH modules. ASMi-54C/N

modules operate as central devices only (STU-C).
Note
When the ASMi-54C/ETH module is operating in the STU-R mode, the maximum
number of remote units is two. These units are served by PCS 1 and PCS 5.
SHDSL Modulation Method

SHDSL uses multi-level pulse-amplitude modulation (PAM) together with trellis
coding. Advanced digital signal processing (DSP) techniques enable symmetric
data transmission at rates of 192 to 2304 kbps (3 to 36 x 64 kbps timeslots), or
5.696 Mbps (up to 89 timeslots) for SHDSL.bis, which corresponds to lines rates
of 200 to 2312 kbps, respectively 5.7 Mbps. The modulation method is spectrally
compatible with other transmission technologies deployed in the access network,
including other DSL technologies.
SHDSL Transport
M8SL are I/O modules employing the single-pair high-speed digital subscriber line
(SHDSL) technology for line transmission, providing Megaplex-4100 with SHDSL
interfaces capable of carrying E1 and fractional E1 payloads.
ASMi-54C modules allow increasing available bandwidth or extending the
maximum range at a given rate. This is done by bonding together two lines
(4-wires mode). Note that when connecting an ASMi-54C/N to a standalone unit
with E1 ports, the maximum bandwidth needed for TDM services is that of a
single E1 port.
5-36
SHDSL Ports
Handling of Timeslot 0
To meet various systems requirements, the user can select the handling method
of timeslot 0 of an E1 stream by each SHDSL port of M8SL and ASMi-54C/N
modules. Two options are available:
Terminate (loop back) timeslot 0. This option is available in the basic G.704
mode only.
Transfer timeslot 0 transparently through the SHDSL link, down to the E1

port of the unit connected to the remote ASMi-52/ASMi-52L unit. This option
is available in both G.704 framing modes.
The handling method of TS0 is configured by means of ts0-over-dsl parameter.

See also ASMi-54C Modules and M8SL Modules in Appendix B for additional
configuration considerations.
Management via Embedded Operational Channel (EOC)

ASMi-54C/ETH and ASMi-54C/E1/ETH/N modules provide an inband management
channel (EOC) for end-to-end system management and supervision of ASMi-54
family of SHDSL/SHDSL.bis modems. This management channel uses SHDSL
overhead bits and operates without interfering with data transmission.
EOC management can be used to configure unaware flows between the GbE
ports of CL modules and PCS ports of ASMi-54C modules without configuring the
module itself.
Note
Configuring aware flows requires dedicated VLAN management.

To activate eoc management, the far-end equipment (ASMi-54L modem) must be
defined as asmi-54eoc.
Single IP Management
The ASMi-54L modems (starting from version 2.6 and higher) can be fully
managed via ASMi-54C/ETH or ASMi-54C/E1/ETH/N modules installed in the
Megaplex-4100 chassis, using RADview-EMS with the Single IP solution.
The Single IP solution uses one legal IP address (the Megaplex-4100 CL module IP
address) to manage up to 96 standalone units via the chassis. The remote
standalone ASMi-54L is assigned a private IP address derived from the CL.2 IP by
an internal algorithm. This solution saves IP addresses on the Megaplex-4100
working with a remote standalone ASMi-54L modem.
This IP address is assigned to all the system which includes the Megaplex-4100
(from version 3.0) with all its CL.2 and ASMi-54C modules and the remote
standalone ASMi-54L units.
If dedicated VLAN management is not configured on an ASMi-54C PCS port, single
IP management is automatically established.
When working in Single IP mode, RADview-EMS sends packets to the ASMi-54L
using the Megaplex-4100 IP address. The Megaplex-4100 CL.2 module works as
NAPT router and routes the management packets to the appropriate entity.
SHDSL Ports
5-37
Factory Defaults
Megaplex-4100 is supplied with all SHDSL ports disabled. Other parameter
Parameter
Default Value
wires
tc
64-65-octets
stu
central
far-end-type
none
power-backoff
line-prob
line-prob (enabled)
ts-compaction-mode
no-mapping
data-rate [kbps]
192
clock-mode {plesiochronous1 |
plesiochronous2 | synchronous3a }
plesiochronous1
current-margin
worst-margin
no worst-margin (disabled)
remote-ch1-ts-num
power-feeding
no power-feeding (disabled)
Configuring SHDSL Port Parameters
To configure the SHDSL port parameters:

1. Navigate to configure port shdsl <slot>/<port> to select the SHDSL port to
configure.
The config>port>shdsl>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short description name < name>

to port
Administratively enabling
port
no shutdown
Specifying number of wires wires {2 | 4 | 8}

for an M-pair group or IMA
In ASMi-54C/ETH, the available selections depend on

the tc parameter
ASMi-54C/N supports only 2- or 4-wire operation
M8SL supports only 2-wire operation
5-38
SHDSL Ports
Task
Command
Comments
Specifying TC layer and

functional mode
(ASMi-54/ETH only)
tc {64-65-octets | hdlc}
All the module ports use the same Transmission

Convergence layer (the last selection is automatically
applied to all the ports)
Setting the port operation

mode: CO or CPE
stu {central | remote}
This option is available only for M8SL or

ASMi-54C/ETH modules when the equipment
connected to the far end of the line is another M8SL
or ASMi-54C/ETH module installed in a
Megaplex-4100
Specifying the far end

equipment connected to
this SHDSL port
far-end-type {none | asmi52 |

asmi52-e1-dte |
high-speed-mux-serial-e1 |
asmi52-e1-eth | asmi52-ethdte | asmi54 | asmi54-eoc |
fcd-ip | dxc | mp-card}
To specify far-end equipment for specific SHDSL

modules, consult Table 5-3.
Enabling the transmit

power-backoff <value in dbm>
power backoff and setting
its value (for ASMi-54C/ETH
and M8SL only)
For working with far-end-type=high-speed-muxserial-e1, see 4M Functionality in ASMi-54C/N

working opposite ASMi-52/52L in Mux Mode in
Appendix B.
Possible values are 0 to 31 dbm.
Power backoff is used to reduce the transmit power
below the nominal value specified in the standards:
this reduces interference caused by your signal to
other equipment using pairs in the same cable,
without degrading the link transmission quality.
Values set for STU-C are copied automatically to
STU-R.
Using no power-backoff disables the power backoff
Controlling the use of line

probing per ITU-T Rec.
G.991.2 for the
corresponding line (to
automatically select the
maximum data rate
supported by the line)
line-prob
This parameter is relevant for ASMi-54C/ETH only.

Using no line-prob disables line probing
When line probing is enabled, either the
current-margin or worst-margin parameter must be
enabled and set
SHDSL Ports
5-39
Task

Command
Controlling the mapping of ts-compaction-mode {nothe connected E1 port

mapping | low-ts-mapping}
timeslots into the SHDSL
frames
Comments
This parameter is relevant only for M8SL when far
end device is MP card, FCD-IP, or DXC.
no-mapping The connected timeslots of the E1
frame are placed in the SHDSL frame in consecutive
timeslots, in ascending order.
when a new E1 timeslot, lower than the timeslots
already connected, is added, the timeslots with
higher numbers must be moved (reassigned): this
results in a brief interruption of data transfer for the
moved timeslots.
low-ts-mapping The first two timeslots of the
SHDSL frame are reserved for the signaling timeslot
(timeslot 16) and the dedicated management
timeslot. The payload starts from the third timeslot,
and is inserted in consecutive timeslots according to
the E1 frame order.
This ensures that the signaling and dedicated
timeslots will continue to function even when new
timeslots are connected in the E1 frame. Service
interruption might still occur when timeslots are
moved, but in this case only data timeslots are
moved.
When the far end device is an ASMi-52/ASMi-52L,
no-mapping is automatically used.
Setting the SHDSL port

data rate (line payload
rate)
data-rate maximum [rate in

kbps]
Selecting the loop

attenuation threshold in
db
<value in dbm>
In ASMi-54C/ETH, this parameter is relevant only

when line probing is disabled (no line-prob).
For available selections, see Table 5-4.
The range is 0 to 127 (the number specifies the
maximum value, in dB).
If the attenuation measured on the SHDSL link
exceeds the threshold value, an alarm is generated.
Selecting clock
clock-mode {plesiochronous1 |
synchronization mode in
plesiochronous2 |
accordance with the SHDSL synchronous3a}
bit rates available in
remote devices
Selecting the SNR margin
threshold in db
snr-margin-threshold <value in The range is 0 to 15 (the number specifies the

db>
maximum value, in dB).
If the attenuation measured on the SHDSL link
exceeds the specified value, an alarm is generated.
5-40
SHDSL Ports
Task
Command
Comments
Specifying the target

margin for the measured
signal-to-noise ratio
relative to the current
noise level (ASMi-54C/ETH
current-margin <value in db>
This parameter is relevant only when line probing is

enabled.
The range is -10 db to +21 dB).
STU-R.
only)
Using no current-margin disables the use of the

signal-to-noise ratio measured relative to the
current noise level.
Alternatively, line activation may be performed in
accordance with the Worst Margin value.
Specifying the target

worst-margin <value in db>
margin for the measured
signal-to-noise ratio
relative to the reference
worst-case near-end
crosstalk noise specified in
ITU-T Rec. G.991.2
This parameter is relevant for ASMi-54C/ETH only,

when line probing is enabled.
The range is -10 db to +21 dB.
STU-R.
Using no worst-margin disables the use of the
signal-to-noise ratio measured measured relative to
crosstalk.
Alternatively, line activation may be performed in
accordance with the Current Margin value.
Setting the number of

timeslots connected to
CH1 (E1) on the remote
modem
remote-ch1-ts-num <value>
Activating power feeding

to this SHDSL line
power-feeding
The available selections are 0 to 31.

This parameter is relevant only for ASMi-54C/ETH
and when the remote modem is ASMi-52/ASMi-52L
MUX type
Using no power-feeding disables the power feeding
of this line
See also Appendix B, ASMi-54C Modules, Working
with Power Feeding.
To verify the SHDSL port parameters:
At the config>port>shdsl>(<slot>/<port>)# prompt, type info detail.

The configured SHDSL port parameters are displayed.
SHDSL Ports
5-41
For example:
mp4100>config>port>shdsl(2/1)# info detail
name "IO-2 shdsl 01"
far-end-type asmi54-eoc
wires 4
stu central
power-backoff default 0
power-feeding
data-rate maximum 5632
loop-attenuation-threshold 0
snr-margin-threshold 0
clock-mode plesiochronous1
no shutdown
Table 5-4. SHDSL Data Rates

Module
ASMi-54C/ETH
ASMi-54C/N
5-42
Wires/Mode/TC
Layer
Far-End Device
ASMi-54
ASMi-54L
ASMi-52/ASMi-52L
2W, HDLC
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 12544 kbps

(n 64 kbps, n= 3 to
196)
N/A
2W, 64/65-Octets
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 15296 kbps

(n 64 kbps, n= 3 to
239)
N/A
4W, HDLC
384 to 11392 kbps

(n 64 kbps, n = 6 to
178)
384 to 30592 kbps

(n 64 kbps, n= 6 to
478)**
N/A
4W, 64/65-Octets
384 to 11392 kbps

178)
384 to 30592 kbps

(n 64 kbps, n= 6 to
478)
N/A
8W, HDLC
768 to 22784 kbps

(n 64 kbps, n= 12 to
356)
N/A
N/A
8W, 64/65-Octets
768 to 22784 kbps

356)
N/A
N/A
2W
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 2048 kbps

32)
*4W,
high-speed-muxserial-e1 mode
N/A
N/A
384 to 4096 kbps

64)
4W, other modes
384 to 11392 kbps

178)
384 to 11392 kbps

178)
384 to 2048 kbps

32)
SHDSL Ports

Module
Wires/Mode/TC
Layer
8W
Far-End Device
ASMi-54
ASMi-54L
ASMi-52/ASMi-52L
768 to 22784 kbps

356)
N/A
N/A
*ASMi-52 only
**The following rates are unavailable for 4W/HDLC operation:
17024 to 18432 kbps
24570 to 25088 kbps
27520 to 30592 kbps.
Testing SHDSL Ports

The SHDSL ports of the M8SL modules feature the following loopbacks, which can
be independently activated for each port:
Local loopback
Remote loopback.
In addition, the M8SL module features a remote loopback on remote ASMi-52

or ASMi-52L unit.
The SHDSL ports of the ASMi-54C/N modules feature the remote loopback on
remote unit, which can be independently activated for each port.
The ASMi-54C/ETH module does not support loopbacks on its SHDSL ports.
Local Port Loopback (M8SL only)

The local port loopback is used to test the path of the signals intended for
transmission through a selected SHDSL port: this path starts at the other port(s)
within the same Megaplex-4100 chassis that are connected to the selected port,
passes through the CL module, and continues up to the SHDSL modem serving
the port. Within the tested I/O module, the path includes most of the SHDSL
modem circuits serving the selected port, and the operation of the routing
circuits that handle the port signals within the module.
A typical local port loopback signal path is shown in Figure 5-1.
As shown in Figure 5-1, when a local loopback is activated on one of the module
ports, the transmit signal is returned to the input of the same port receive path,
at a point just before the line interface. The local port must receive its own
signal, and thus it must be frame-synchronized.
SHDSL Ports
5-43
Note
During local port loopback, the remote equipment does not receive a valid SHDSL
signal, and therefore it loses synchronization. This is normal, and does not
indicate a problem.
After the local loopback is deactivated, the SHDSL subsystem must synchronize
again, and therefore you will see the sequence of port synchronization
indications at both the local and the remote ports.
In addition, each I/O module connected to the corresponding port must also
receive its own signal: in general, the result is that these modules are
synchronized and do not generate alarm indications. However modules that
cannot receive their own signal (for example modules with Ethernet interfaces)
enter an alarm state while a local loopback is activated.
Megaplex-4100
CL
M8SL
Port 1
Other Port
Interface
Routing
Matrix
..
..
.
Bus
Interface
..
..
..
.
Port 8
Figure 5-1. Local Port Loopback Signal Path
Remote Port Loopback (M8SL only)

The remote port loopback is used to test the SHDSL modem circuits of a selected
SHDSL external port. This test also checks the transmission plant connecting the
remote equipment to the corresponding port of the I/O module.
A typical remote port loopback signal path is shown in Figure 5-2.
Megaplex-4100
CL
M8SL
Port 1
Other Port
Interface
Routing
Matrix
Bus
Interface
..
..
.
..
..
..
.
Port 8
Figure 5-2. Remote Port Loopback Signal Path

When a remote loopback is activated on one of the SHDSL ports, the SHDSL
modem serving that port returns the received signal toward the remote unit, via
the transmit path. The received signal remains connected as usual to the receive
path of the corresponding port. To correct transmission distortions, the returned
signal is fully regenerated by the SHDSL modem circuits.
5-44
SHDSL Ports
The remote loopback should be activated only after checking that the remote unit
operates normally with local port loopback. In this case, the remote unit must
receive its own signal, and thus it must be frame-synchronized. The effect on the
individual modules is mixed, as explained above for the local loopback.
If the local Megaplex-4100 unit operates normally with the local port loopback,
then while the remote loopback is connected the local unit should receive a valid
signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the two
Megaplex-4100 connected in a link, otherwise an unstable situation occurs.
Remote Loopback on Remote Unit

The remote loopback on remote unit is relevant for M8SL and ASMi-54C/N SHDSL
ports connected to remote modems. This loopback is used to test all the circuits
of the corresponding module port, the line to the remote unit, and the operation
of the remote unit.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
The loopback is activated within the user interface of the remote modem, which
returns the received data through the transmit path.
Figure 5-3 shows the signal paths of a typical remote loopback on the remote
ASMi-52/ASMi-52L.
Megaplex-4100
CL
M8SL
Routing
Matrix
Port 1
..
..
.
Bus
Interface
Other Port
Interface
ASMi-52
..
..
..
..
Remote
Loopback
Port 8
Figure 5-3. Remote Loopback on Remote Unit, Signal Paths
Activating SHDSL Loopbacks

You can activate a loopback on an SHDSL port or on one of the repeaters
operating on its line. Repeaters feature only remote loopbacks with infinite
duration.
To perform a loopback on the SHDSL port:

1. Navigate to configure port shdsl <slot>/<port> to select the SHDSL port to
configure.
The config>port>shdsl>(<slot>/<port>)# prompt is displayed.
SHDSL Ports
5-45
Task
Command
Setting loopback duration

and activating the
corresponding loopback on
this port
loopback {local | remote | remote-on- Local and remote loopbacks are available
remote } [ duration <duration in
for M8SL modules only.
minutes 1..30> ]
Using no loopback disables the loopback
Comments
To perform a loopback on an SHDSL repeater:

1. Navigate to configure port shdsl <slot>/<port>)repeater (repeater ID)#, to
select the repeater.
The config>port>shdsl (<slot>/<port>)repeater (repeater ID)# prompt is
displayed.
Task
Command
Comments
Activating the remote

loopback on the repeater
loopback remote
Using no loopback remote disables the

loopback
Displaying SHDSL Port Status

You can display the status and configuration of an individual SHDSL port. If
relevant, the display also shows the number and parameters of SHDSL repeaters
installed in the line. For each repeater and wire, the values of SNR Margin (db)
and Loop Attenuation (db) are displayed on the Network and Customer sides.
To display status of an SHDSL port:
At the prompt config>port>shdsl(<slot/port)#, enter show status.

The SHDSL port status parameters are displayed.
Note
5-46
The possible status values are interpreted as follows:
ON Power feeding is connected
OFF Power feeding is disconnected
Failure Current overload or failure on the line
N/A Power feeding is not relevant for this module
SHDSL Ports
mp4100>config>port>shdsl(8/1)# show status

Operation Status
: Up
Loopback Type
: None
Wires
: 4
Transmission Mode
: B-G
Line Rate (Kbps)
: 1552
Number Of repeaters
: 1
Wires
---------------------------------------------------------------------State
SNR
Loop
Power
Power
Margin
Attenuation
Backoff
Feeding
(db)
(db)
---------------------------------------------------------------------Data
23
0
6
ON
Repeater Number
: 1
Repeater Side
:
Wire Num
:
SNR Margin (db)
:
Loop Attenuation (db) :
Loopback Type
:
Customer
1
23
0
Remote
2
23
0
Network
1
24
0
2
24
0
Displaying SHDSL Port Statistics

You can display statistics for the SHDSL ports of all kinds of ASMi-54C and M8SL
modules.
To display the SHDSL port statistics:

At the prompt config>slot>port>shdsl (<slot>/<port>)#, enter show statistics
followed by parameters listed below. <wire-num> specifies the number of the
SHDSL interface wire for which the statistics is displayed.
Note
Day statistics (all types) are supported only for ASMi-54C/ETH, other statistic
types are supported by all SHDSL modules.
SHDSL Ports
5-47
Task
Command
Comments
Displaying statistics
show statistics <wire-num> {all | all-intervals |

all-days-interval | current | current-day}
All SHDSL modules:
current - current statistics (up to

15 min)
all-intervals - all intervals during

the last 24 hours
Additional statistics ( ASM-54C/ETH

only):
current-day - current today's

statistics
all-days-interval - all intervals

during the last 7 days
all - current, all-intervals,

current-day, all-days-interval
for a specific 15-min
interval
show statistics <wire-num> interval

<interval-num 1..96>
All SHDSL modules
for a selected day
show statistics <wire-num> day <day-num

1..7>
ASMi-54C/ETH only
SHDSL port statistics are displayed. For example:

Current Statistics for Wire 1 (all modules):
mp4100>config>port>shdsl(4/2)# show statistics 1 current
Wire Num : 1
Current
--------------------------------------------------------------Time Elapsed (Sec) : 388
Valid Intervals
: 0
ES
: 0
LOSWS
: 0
SES
: 0
CRC Anomalies : 0
UAS
: 0
Statistics for Interval 1, Wire 1 (all modules):
mp4100>config>port>shdsl(4/2)# show statistics 1 interval 1
Wire Num : 1
Interval
--------------------------------------------------------------Interval Number : 1
ES
: 0
LOSWS
: 1
SES
: 395
CRC Anomalies : 0
UAS
: 395
Current Day Statistics for Wire 1 (ASMi-54C/ETH):
5-48
SHDSL Ports
mp4100>config>port>shdsl(4/2)# show statistics 1 current-day

Wire Num : 1
Current Day
--------------------------------------------------------------Time Elapsed (Sec) : 3115
Valid Days
: 0
ES
: 0
LOSWS
: 11
SES
: 1163
CRC Anomalies : 0
UAS
: 1163
Statistics for Day 1, Wire 1 (ASMi-54C/ETH):
mp4100>config>port>shdsl(4/2)# show statistics 1 day 1
Wire Num : 1
Day Interval
--------------------------------------------------------------Day Number : 1
ES
: 0
LOSWS
: 1
SES
: 395
CRC Anomalies : 0
UAS
: 395
The counters are described in the table below.
Table 5-5. SHDSL Statistics Parameters

Parameter
Description
Time elapsed (for current

interval)
The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds
Time elapsed (for current

day, ASMi-54C/ETH only)
The elapsed time (in seconds) since the beginning of the current day, in
Interval number
Number of interval for which statistics are displayed
Note: The sequence of intervals is different for the SHDSL ports of different
modules:
For the M8SL and ASMi-54C/N modules, Interval #1 is the latest in time
For the ASMi-54C/ETH modules, Interval #1 is the earliest in time.
Day number
Number of day for which statistics are displayed (ASMi-54C/ETH only)
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics can be
displayed, in addition to the current (not finished) interval (up to 96)
Valid days
The number of elapsed finished days (24 hours) for which statistics can be
displayed, in addition to the current (not finished) day (up to 7)
(ASMi-54C/ETH only)
ES
The number of errored SHDSL seconds (ES) in the current/selected

interval/day/week.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared
SHDSL Ports
5-49
Parameter
Description
UAS
The number of unavailable SHDSL seconds (UAS) in the current/selected

interval/day/week.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The
SHDSL line becomes unavailable at the onset of 10 contiguous SESs (the 10
SESs are included in the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10
contiguous seconds with no SESs (the 10 seconds with no SESs are excluded
from the unavailable time)
SES
The number of severely errored SHDSL seconds (SES) in the current/selected

interval/day/week.
The SHDSL SES is any second which is not declared a UAS, during which at
least 50 CRC anomalies are declared, or one or more LOSW defects are
declared
CRC Anomalies
The number of CRC anomalies in the current/selected interval/day/week.

A CRC anomaly is declared when the CRC bits generated locally on the data in
the received SHDSL frame do not match the CRC bits (crc1 - crc6) received
from the transmitter. A CRC anomaly only pertains to the frame over which it
was declared.
LOSWS
Displays the number of SHDSL LOSW seconds (LOSWS) in the

current/selected interval/day/week.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW
defects are declared
Displaying SHDSL Repeater Statistics

You can display statistics for the SHDSL repeaters working in line with
ASMi-54C/N modules.
To display the SHDSL repeater statistics:

At the prompt config>port>shdsl (<slot>/<port>) repeater (repeater ID)#, enter
show statistics running.
SHDSL statistics are displayed separately for each repeater and each wire
on the customer and the network side. The number of columns depends
on number of wire-pairs configured in the line menu. The statistics are
accumulated since the corresponding SHDSL port of the ASMi-54C/N
module is on.
For example:
5-50
SHDSL Ports
mp4100>config>port>shdsl(2/5)# repeater 1
mp4100>config>port>shdsl(2/5)>repeater(1)# show statistics
Repeater Side : Customer
Network
Wire Num
: 1
2
1
ES
: 4
4
0
SES
: 0
0
0
UAS
: 248
248
47
LOSWS
: 248
248
47
CRC Anomalies : 19
19
0
running
2
0
0
47
47
0
The counters are described in the table below.
Table 5-6. SHDSL Repeater Statistics Parameters

Parameter
Description
ES
The number of errored SHDSL seconds (ES) accumulated since the module is
on.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared
UAS
The number of unavailable SHDSL seconds (UAS) accumulated since the

module is on.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The
SHDSL line becomes unavailable at the onset of 10 contiguous SESs (the 10
SESs are included in the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10
contiguous seconds with no SESs (the 10 seconds with no SESs are excluded
from the unavailable time)
SES
The number of severely errored SHDSL seconds (SES) accumulated since the
module is on.
The SHDSL SES is any second which is not declared a UAS, during which at
least 50 CRC anomalies are declared, or one or more LOSW defects are
declared
CRC Anomalies
The number of CRC anomalies accumulated since the module is on.

A CRC anomaly is declared when the CRC bits generated locally on the data in
the received SHDSL frame do not match the CRC bits (crc1 - crc6) received
from the transmitter. A CRC anomaly only pertains to the frame over which it
was declared.
LOSWS
Displays the number of SHDSL LOSW seconds (LOSWS) accumulated since

the module is on.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW
defects are declared
Clearing Statistics
To clear the statistics for an SHDSL port:
At the prompt config>port>shdsl<slot>/<port>)#, enter clear-statistics.

You cannot clear repeater statistics.

SHDSL Ports
5-51
Note
If the SHDSL cable is removed, the repeater statistics is cleared. However, do not
use this as a method to clear repeater statistics.
5.9
PCS Ports
PCS (Physical Coding Sublayer) ports are available on the ASMi-54C/N and
ASMI-54C modules and determine the Ethernet (packet) physical layer
transmission capabilities over SHDSL lines. The number of PCS ports on each
module is 8.
The following can be configured for the PCS ports:
Assigning PCS port name
Setting port administrative status
Binding an SHDSL port to a PCS port
Standards
PCS ports comply with IEEE 802.3-2005.
In Megaplex-4100, PCS ports are used to transport Ethernet traffic from a local
Ethernet port over SHDSL.
The ASMi-54C internal SHDSL processing subsystem enables configuring the
desired Physical Coding Sublayer parameters for each SHDSL line (actually for
each SHDSL port). Therefore, ASMi-54C supports 8 PCS entities, one for each
associated SHDSL port, and on the supervision terminal screens, the PCS index
number is the same as the associated SHDSL port.
As for SHDSL ports, PCS ports are processed in two groups of four (one group
includes PCS ports 1 to 4, and the other 5 to 8).
Note
ASMi-54/54L/52/52L standalone units can connect to up to four PCS ports, which

must be in the same group (either 1 to 4, or 5 to 8).
In IEEE 802.3-2005 terminology, each PCS port is associated with a PME (Physical
Medium Entity): for ASMi-54C modules, it is the SHDSL master line port. When
using the M-pair mode (4-wire operation), the PME is the SHDSL master port.
PCS ports are independently configurable.
In ASMi-54C/ETH modules, the available bandwidth is the payload rate of the
associated line. In ASMi-54C/N, the available PCS bandwidth is the payload rate of
the associated line, less any bandwidth assigned to the associated E1 port of the
same line.
Even when all eight SHDSL lines of the ASMi-54C module operate in 2-wire mode,
the PCS transport bandwidth can be increased using PAF (PME Aggregation
Function), also defined in IEEE 802.3-2005. PAF creates PCS groups. The PCS
5-52
PCS Ports
groups that can be configured on the ASMi-54C modules are listed in Table 5-7
for ASMi-54C/N models and in Table 5-8 for ASMi-54C/ETH.
The main functions performed for each PCS port include:
Ethernet payload data rate matching: the average payload rate accepted by
each PCS port is matched to the physical rate supported by the
corresponding PME.
As for M-pair bonding, one of the PCS ports (the PCS with the lowest index in
the group) is automatically selected as the master PCS port, from which all
the other PCS ports copy their parameters.
Each active PCS port can serve as a bridge port that can terminate Ethernet flows
configured within the Megaplex-4100.
Table 5-7. Supported PCS Groups versus Lines Parameter, ASMi-54C/N module
Maximum Number of
PCS Groups
Number of SHDSL
Ports in PCS Group
2 (4 wires)
4
2 (4 wires)
8
1 (2 wires)
SHDSL Ports in
PCS Group
Master PCS in the

Group
1, 2
3, 4
5, 6
7, 8
1 to 8
N/A
Table 5-8. Supported PCS Groups versus Lines Parameter for ASMi-54C/ETH
Maximum
Number of PCS
Groups
Number of SHDSL
Ports (Lines) in PCS
Group
SHDSL Lines in
PCS Group
Master PCS in the

Group
1, 2, 3, 4
5, 6, 7, 8
1, 2
3, 4
5, 6
7, 8
2
4
2
Factory Defaults
Megaplex-4100 is supplied with all PCS ports disabled.
Configuring a PCS Port
To configure a PCS port:

1. Navigate to configure port pcs <slot>/<port> to select the port to configure.
The config>port>pcs>(<slot>/<port># prompt is displayed.
PCS Ports
5-53

Task
Command
Comments
Assigning short description to a name <string>

PCS port
Administratively enabling the

port
no shutdown
Using shutdown disables the PCS
bind shdsl <slot><port>
Using no before bind removes the binding
Binding a SHDSL port to a PCS

port
Displaying PCS Port Status

You can display the status and configuration of an individual PCS port.
To display the status of a PCS port:
At the prompt config>port>pcs(<slot/port)#, enter show status.

The PCS port status parameters are displayed.
For example:
To display the status of PCS port 1 of an ASM-54C/ETH module installed in slot 2:

mp4100>config>port>pcs(2/1)# show status
Name
: IO-2 Pcs 01
Operation Status
: Up
Displaying PCS Statistics

You can display statistics for the PCS ports of all kinds of ASMi-54C modules.
To display the PCS statistics:

At the prompt config>slot>port>pcs (<slot>/<port>)#, enter show statistics
followed by parameters listed below.
PCS statistics are displayed. The counters are described in Table 5-9. For
example:
5-54
PCS Ports
mp4100>config>port>pcs(2/1)# show statistics

Running
--------------------------------------------------------------Total Frames Rx
: 0
Total Frames Tx
: 0
Total Octets Rx
: 0
Total Octets Tx
: 0
Unicast Frames Tx
: 0
Multicast Frames Rx : 0
Broadcast Frames Rx : 0
FCS Errors
: 0
Jabber Errors
: 0
Undersize Frames
: 0
Oversize Frames
: 0
Paused Frames
: 0
64 Octets
: 0
65-127 Octets
: 0
128-255 Octets
: 0
256-511 Octets
: 0
512-1023 Octets
: 0
1024-1528 Octets
: 0
Table 5-9. PCS Statistics Parameters

Parameter
Description
Total Frames Rx/Tx
Total Octets Rx/Tx
Unicast Frames Tx
Total number of unicast frames transmitted
Multicast Frames Rx
Total number of multicast frames received
Broadcast Frames Rx
Total number of broadcast frames received
FCS Errors
Total number of frames received on this PCS that are an integral number of
octets in length but do not pass the FCS check
Jabber Errors
Total number of frames received with jabber errors
Undersize Frames
Oversize Frames
Paused Frames
Total number of pause frames (used for flow control) received/transmitted

through the corresponding PCS
64 Octets
65127 Octets
128255 Octets
256511 Octets
5121023 Octets
10241528 Octets
PCS Ports
5-55
Clearing Statistics
To clear the statistics for a PCS:
At the prompt config>port>pcs<slot>/<port>)#, enter clear-statistics.
5.10 E1 Ports
The following table shows the number of E1 and E1-i ports and their features
supported by each Megaplex-4100 module. The hierarchical position of e1 and
e1-i ports is slot:port for all the modules, with the exception of Megaplex cards
OP-108C and OP-34C, where it is slot:port:tributary (in these modules
slot:port=mux_eth_tdm). The digits in brackets (1 to 4) denote restrictions or
other special remarks regarding implementation of this feature in specific
modules.
Table 5-10. Features Supported by Megaplex-4100 E1 and Internal E1 Ports

Feature/
Command
E1 Ports (e1)
Internal E1 Ports (e1-i)
M8E1
M16E1
OP-108C
OP-108C/E1
OP-34C
OP-34C/E1
ASMi-54C/N
CL.2
M8SL
ASMi-54C/N
ports
16
16
16
63
name
shutdown
inband-
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
interface-type
line-type
(6)
out-of-service
(voice, data)
(2)(1)
(2)(1)
(2)(1)
(2)(1)
(2)(1)
(2)(1)
(2)(1)
restoration-
rx-sensitivity
signaling-
profile
(1)(4)
timeslots-
signaling-
(1)(4)
Number of
management
(2)(1)
time
(1)(4)
(1)(4)
profile
idle-code
(1)
ts0-over-dsl
5-56
E1 Ports
(1)
(1)
(1)
(1)
(1)
(1)
(1)
Feature/
Command
E1 Ports (e1)
M8E1
M16E1
OP-108C
OP-108C/E1
OP-34C
OP-34C/E1
ASMi-54C/N
CL.2
remote-crc
vc-profile
(7)
(7)
(7)
(7)
M8SL
ASMi-54C/N
(5)
(7)
1 - N/A for Unframed

2 - OOS voice and signaling N/A for line-type=g732n/g732n-crc
3 Unframed not supported
4 - N/A for line-type=g732n/g732n-crc
5 Applicable if ts0-over-dsl is looped and line-type is g732n
6 - N/A for line-type=g732n-crc/g732n-crc
7 - Applicable if line type is Unframed and the link is directly mapped to SDH-SONET vc12-vt2
Note
OP-108C/E1 and OP-34C/E1 are LRS-102 modules with E1 physical ports, which
can also be installed and operate in Megaplex-4100.
Standards
The E1 link interfaces meet the applicable requirements of ITU-T Rec. G.703,
G.704, G.706, G.732, and G.823.
External E1 Link Interfaces are available in M8E1, M16E1, OP-108C/E1, OP-34C/E1
and ASMi-54C/N I/O modules. Internal E1 ports are available in CL.2, M8SL and
ASMi-54C/N I/O modules.
The Megaplex-4100 Optimux modules (OP-108C and OP-34C) also have internal
ports but of other type than E1-i. These ports are designed and configured as
E1 but hierarchically they hold tributary positions, such as
<slot>/<port>/<tributary>.
The parameters configurable for each module can be chosen from Table 5-10 . E1
port parameters are described in the following sections.
Framing
The external and internal E1 ports can be independently configured in accordance
with the desired ITU-T framing mode and signaling formats:
Basic G.704 framing (identified as G.732N) for applications that require CCS.
G.704 framing with timeslot 16 multiframe (identified as G.732S and referred

to as G.704 multiframe mode) for applications that require CAS.
Unframed mode for transparent transfer of 2.048 Mbps streams, including

streams with proprietary framing. Also enables transferring framed E1
streams without terminating timeslot 0, and timeslot 16.
E1 Ports
5-57
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode can be independently selected for each extermal or internal E1
port of the I/O module. It is configured by means of the line-type parameter.
Interface Type
The external ports support two line interfaces:
120 balanced line interface. The nominal balanced interface transmit level is
3V.
75 unbalanced interface. The nominal unbalanced interface transmit level is

2.37V.
Only one of these interfaces can be active at any time. The active interface can
be selected by the user, separately for each port.
Receive Signal Attenuation (M8E1 only)

The E1 line interfaces have integral LTUs, which enable long-haul operation with
line attenuation of up to 33 dB. The line interface can also emulate a DSU
interface, for short-haul applications: in this case, the maximum line attenuation
is 10 dB. The receive signal attenuation level is configured by means of the
rx-sensitivity parameter.
E1 Payload Processing
Megaplex-4100 E1 modules support three main types of payload per timeslot:
Data timeslots: timeslots which are transparently transferred from port to

port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
Voice timeslots: timeslots carrying PCM-encoded payload, with A-law

companding for M8E1 ports and -law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
standards. The user can specify translation rules for the signaling information
by defining signaling profiles see details in the Signaling Profiles section
below.
Management timeslots: with framed signals, one timeslot per port can be
assigned to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). However, it is also possible to define unidirectional flows, called
unidirectional broadcasts, from one source (a timeslot of a source port) to
multiple destinations (each destination being a selected timeslot of another
port).
5-58
E1 Ports
In case of data timeslots, the flow of payload is normally unidirectional. If the

application requires bidirectional flows, cross-coneect must be configured
symmetrically for both directions.
Handling E1 Alarm Conditions

External and internal E1 ports using framed mode support two types of indications
in the individual timeslots:
Idle Timeslot Indication. A special code can be transmitted in empty timeslots

(timeslots which do not carry payload).
OOS Indications. The OOS code is inserted in individual timeslots to signal the
equipment routed to one of the E1 ports of the module that the link
connected to the external port is out-of-service (e.g., because of loss of
frame synchronization).
For ports using a G.704 timeslot 16 multiframe mode, the CAS information
can also be replaced by a selectable OOS indication.
The idle code and OOS indications can be independently configured for each port.
Moreover, separate OOS codes can be transmitted in the timeslots, in accordance
with the type of payload carried by each timeslot (voice or data).
OOS Signaling
If the communication between modules located in different Megaplex units fails,
e.g., because loss of main link synchronization, etc., it is necessary to control the
state of the signaling information at the two ends of the link. This activity, called
out-of-service (OOS) signaling, is performed by the E1 interfaces and can be
selected in accordance with the specific application requirements, on a per-link
basis.
The OOS signaling options supported by the E1 module ports are as follows:
Signaling forced to idle state for the duration of the out-of-service condition
(force-idle). This option is suitable for use with all the VC module types.
Signaling forced to busy state for the duration of the out-of-service condition
(force-busy). This option is suitable for use with E&M and FXO modules, but
not with FXS modules.
Signaling forced to idle state for 2.5 seconds, and then changed to busy
state for the remaining duration of the out-of-service condition (idle-busy).
This option is suitable for use with E&M and FXO modules, but not with FXS
modules.
Signaling forced to busy state for 2.5 seconds, and then changed to idle
state for the remaining duration of the out-of-service condition (busy-idle).
This option is suitable for use with all the VC module types.
Inband Management
E1 and internal E1 ports of Megaplex-4100 using a framed mode feature inband
management access to the end users equipment provided by configuring a
dedicated management timeslot.
E1 Ports
5-59
The transfer of inband management traffic is controlled by using synchronous

PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
RIP2 routing tablesare transmitted as follows:
Proprietary RIP Management traffic is routed using RAD proprietary routing

protocol
RIP2 In addition to the RAD proprietary routing protocol, RIP2 routing is

also supported.
Factory Defaults
Megaplex-4100 is supplied with all e1/e1-i ports disabled. Other parameter
Parameter
Default Value
line-type
g732s
restoration-time
immediate
rx-sensitivity
short-haul
interface-type
balanced
idle-code
7F
inband-management
no inband-management (disabled)
inband-management routing-protocol
none
out-of-service - voice
00
out-of-service - data
00
out-of-service - signaling
force-idle
signaling-profile
no signaling-profile
vc profile
no vc
Configuring E1 Port Parameters
To configure the E1 port parameters of OP-108C, OP-34C modules:

1. Navigate to configure port e1 <slot>/< mux-eth-tdm port>/<tributary> to
select the E1 port to configure.
The config>port>e1>(<slot>/<mux-eth-tdm port>/<tributary>)# prompt is
displayed.
Note
Tributary e1 ports of Megaplex Optimux modules are actually internal ports but of
type other than e1-i.
For OP-108C, <port>/<tributary> is 1/1 to 1/4 and 3/1 to 3/4. Tributaries 2/x
and 4/x do not exist.
5-60
E1 Ports
For OP-34C, <port>/<tributary> is 1/1 to 1/16. Tributaries 2/x do not exist.
To configure the E1 port parameters of other modules:

Navigate to configure port e1 <slot>/<port> to select the E1 port to configure.
The config>port>e1>(<slot>/<port>)# prompt is displayed.
Enter all necessary commands according to the tasks listed below (see Table 4-5
for parameters supported in each module).
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specifying E1 framing
mode
line-type {unframed | g732n

| g732n-crc | g732s | g732s-crc}
Setting attenuation level

of the receive signal
rx-sensitivity {short-haul | long-haul}
Specifying port
impedance
interface-type {balanced | unbalanced}
Specifying the code

transmitted to fill unused
timeslots in E1 frames
idle-code { 00 to FF (hexa) }
The available selections are [0x01 to 0xFF]

with the following values that are illegal:
0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92
Enabling inband
management and setting
its parameters
inband-management <timeslot> protocol

{ppp | fr} [routing-protocol {none | proprip | rip2} ]
ppp synchronous PPP over HDLC

encapsulation
fr Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
The RIP2 network is limited to 14 nodes.
Using no inband management <timeslot>
disables inband management through this
timeslot
Transmitting an
out-of-service signal
(OOS)
out-of-service [voice <00 to FF (hexa)>] [

data <00 to FF (hexa)>] [signaling
{force-idle | force-busy | idle-busy |
busy-idle}]
The hexadecimal number is in the range of 0

to FF (two digits)
The selected out-of-service data code is
also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
E1 Ports
5-61
Task
Command
Comments
Specifying the signaling

profile (M8E1 only)
signaling-profile {1 | 2 | 3 | 4 | 5 | per-ts}
1 to 5 All the voice timeslots of the port

being configured use the same signaling
profile, and the number specifies the signaling
profile to be used, in the range of 1 to 5.
per-ts The signaling profile can be
individually selected for each voice timeslot of
the port being configured.
This parameter is relevant only when using a
framing mode that supports CAS (line-type
= g732s)
Using no signaling-profile cancels signaling
profile setting (signaling information is
transparently transferred)
For creating and configuring signaling
profiles, see Signaling Profiles.

profile per a single
timeslot or per timeslot
range
timeslots-signaling-profile [tsx] {1 | 2 | 3 |
4 | 5}
timeslots-signaling-profile [tsx..tsy] {1 | 2 |
3 | 4 | 5}
This command is available for voice

timeslots only, if you selected per-ts under
signaling-profile
This command is not available for TS #16.
This command is possible for multiple
timeslots only if they are consecutive
Setting the time required

for a port to resume
normal operation after
loss of frame
restoration-time {1-sec | immediate |

10-sec}
Used to change the frame synchronization

algorithm, to reduce the time required for
the port to return to normal operation after
local loss of synchronization.
1-sec After 1 second.
10-sec Similar to the requirements of
AT&T TR-62411 (after 10 seconds).
Immediate Immediate, complies with ITU-T
Rec. G.732.
This parameter cannot be changed when
using the Unframed mode.
Assigning VC profile to
the port
vc profile <profile name>
For creating VC profiles, see VC Profiles.

Relevant for M16E1, Optimux modules (in
Megaplex chassis only) and ASMi-54C/N.
M8E1 does not support this feature.
Using no vc removes the profile
Configuring Internal E1 Port Parameters
To configure the internal E1 port parameters:

1. Navigate to configure port e1-i <slot>/<port> to select the internal E1 port to
configure.
The config>port>e1-i>(<slot>/<port>)# prompt is displayed.
5-62
E1 Ports

Task
Command
Comments
Assigning short
description to the port
name <string>
the port
no shutdown
Specifying E1 framing
mode
line-type { unframed | g732n | g732n-crc |

g732s | g732s-crc }
g732n-crc and g732s-crc options are not

relevant for the M8SL module.
For even e1-i ports representing the serial
ASMi-52 interface (far-end-type=highspeed-mux-serial-e1), the only possible
selection is g732n.
Specifying the code

timeslots in E1 frames
idle-code <00 to FF (hexa)>
The available selections are [0x01 to 0xFF]

with the following values that are illegal:
0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92
Enabling inband
its parameters

{ppp | fr} [routing-protocol {none | proprip | rip2} ]

encapsulation
timeslot
Inband management is not available for
even e1-i ports representing the serial
ASMi-52 interface (far-end-type=highspeed-mux-serial-e1).
Transmitting an
(OOS)
out-of-service [voice <00 to FF (hexa)>] [

data <00 to FF (hexa)>] [signaling
busy-idle}]
The hexadecimal number is in the range of 0

to FF (two digits)
The selected out-of-service data code is
also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
ASMi-52/52L interface (far-end-type=highspeed-mux-serial-e1), the only possible
selection is data.
E1 Ports
5-63
Task
Command
Comments
Selecting the handling of

timeslot 0 for M8SL,
ASMi-54C/N and CL.2
internal E1 ports
ts0-over-dsl
Timeslot 0 is transparently transferred

through the SHDSL link and terminated by
the remote equipment). When selecting the
port bandwidth, make sure to assign an
additional timeslot for transferring timeslot
0. This is the only option when using the
G.732S mode.
This option is not available for even e1-i
ports representing the serial ASMi-52/52L
interface (far-end-type=high-speed-muxserial-e1).
Using no ts0-over-dsl means local
termination of timeslot 0. This option is
relevant only when the framing mode
(line-type) of the internal (virtual) port is
G.732N.
Enabling CRC-4 error

detection at the remote
ASMi-52/52L unit (M8SL
only)
remote-crc

loss of frame
restoration-time {1-sec | immediate |

10-sec}
Used for performance monitoring, and is

available only when the ASMi-52/52L
includes an E1 user port
Using no remote-crc disables the remote
CRC-4 error detection
Immediate Immediate, complies with ITU-T
Rec. G.732.
This parameter cannot be changed in
unframed mode.
ASMi-52/52L interface (far-end-type=highspeed-mux-serial-e1), the only possible
selection is immediate.
the port

Example 1
The following section illustrates how to configure the E1 port labeled 1 on the
M8E1 module installed in slot 9:
5-64
E1 Ports
Set the E1 framing mode to G.732N with CRC.
Set the line interface to unbalanced.
Set the attenuation level of the receive signal to long-haul.
Set the idle code to 8E.
Administratively enable the port.
Leave all other parameters disabled or at their defaults.
mp4100>config>port>e1(9/1)#
interface-type unbalanced
line-type g732n-crc
rx-sensitivity long-haul
idle-code 0x8E
no shutdown
Example 2
This section illustrates how to configure inband management via a dedicated
timeslot on M8E1 Module.
1. Define an M8E1 module in Slot 1 and configure inband management via E1
port 1 with the following parameters:
Dedicated timeslot - #31
Inband management protocol: synchronous PPP over HDLC encapsulation
Routing protocol: RAD proprietary RIP.
mp4100>config>slot# 4 card-type e1-t1 m8e1

mp4100>config>port# e1 1/1 no shutdown
mp4100>config>port# e1 1/1 line-type g732n
mp4100>config>port# e1 1/1 inband-management 31 protocol ppp
routing-protocol prop-rip
Configure router interface 5.
mp4100>config>router# 1 interface 5 address 17.17.17.17/24
Bind E1 port 1/1 to router interface 5.
mp4100>config>router# 1 interface 5 bind e1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate E1 port 2 of M8E1 module in Slot 9.
Configure signaling profile per ts:
TS-10 to profile 2
TS-1 to 9 to profile 3
Result : OK
no shutdown
signaling-profile per-ts
timeslots-signaling-profile 10 2
timeslots-signaling-profile [1..9] 3
commit
E1 Ports
5-65
Displaying signaling profile per ts:

mp4100>config>port>e1(9/2)# info detail
name "IO-9 e1 02"
no shutdown
line-type g732s
line-code hdb3
interface-type balanced
idle-code 0x7f
restoration-time immediate
out-of-service voice 0x00 data 0x00 signaling
rx-sensitivity short-haul
force-idle
Testing E1 Ports
Megaplex-4100 E1 ports feature test and loopback functions at the port and
timeslot levels. The available loopbacks depend on the port type (E1, E1-i) and
specific module. The following table shows the loopbacks supported by E1 and
E1-i ports on each Megaplex-4100 module. The hierarchical position of e1 and
e1-i ports is slot:port for all the modules, with the exception of Megaplex cards
OP-108C and OP-34C, where the e1 port is found at slot:port:tributary (in these
modules slot:port=mux_eth_tdm). The digits in brackets (1 to 3) denote
restrictions or other special remarks regarding implementation of this loopback in
specific modules.
Table 5-11. Loopbacks Supported by Megaplex-4100 E1 and E1-i Ports

E1 Ports (e1)
Lopback Type
M8E1
M16E1
OP-108C
OP-108C/E1
OP-34C
ASMi-54C/N
CL.2
M8SL
ASMi-54C/N
Local Loop
(1)
(1)
Remote Loop
(2)
(2)
(2)
(2)
Loop per TS
Local
Loop per TS
Remote
Local on
remote
Remote on
remote
5-66
E1 Ports
1 - Loopback on local and remote devices

2 - Only for local internal e1 ports.
CL Modules
The following sections briefly describe each type of loopback on E1-i ports of CL
modules. Table 5-12 shows the paths of the signals when each loopback is
activated.
Table 5-12. Loopbacks on E1-i Ports of CL.2 Modules
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
I/O Port
..
..
..
..
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
E1-i port
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on E1-i port
..
..
..
E1 Ports
5-67
Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
Framers
CL
1
2
I/O Port
.
.
.
..
.
.
.
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
timeslots of
E1-i port
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on timeslots of
E1-i port
..
..
..
Local Loopback on E1-i Port

The local E1-i port loopback is used to test the intra-Megaplex-4100 paths of the
signals intended for transmission through a selected E1-i port: these paths start
at the other Megaplex-4100 port(s) connected to the tested E1-i port, pass
through the DS1 cross-connect matrix in the CL module, and continue up to the
framer of the E1-i port within the SDH/SONET link interface. Therefore, these
paths include all of the Megaplex-4100 local ports connected to the tested E1-i
port, and in the particular the operation of the DS1 cross-connect matrix circuits
that handle the signals directed to the tested E1-i port within the CL module.
As shown in Table 5-12, the local E1-i port loopback is activated within the E1-i
framer of a selected CL E1-i port.
Remote Loopback on E1-i Port

As shown in Table 5-12, the E1-i port remote loopback is activated on the framer
serving the port within the SDH/SONET link interface.
5-68
E1 Ports
Local Loopback on E1-i Port Timeslots

The local loopback on selected timeslots of an E1-i port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.
This test is recommended for testing the signal paths between the E1-i port and
an I/O port of another module that uses only a fraction of the available E1-i port
bandwidth.
As shown in Table 5-12, the loopback is activated only on the timeslots specified
by the user during the activation of the loopback. As a result, there is no
disturbance to services provided by means of the other timeslots of the same
E1-i port, only the flow of payload carried by the specified timeslots is disrupted.
The user can activate the loopback on any individual timeslot, or on several
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
cross-connected with HDLC ports.
Remote Loopback on E1-i Port Timeslots

The remote loopback on selected timeslots of an E1-i port is used to return the
receive payload carried by the selected timeslots through the same timeslots of
the transmit path. The corresponding timeslots received from the local equipment
are disconnected.
This test is recommended for testing signal paths from a remote equipment unit,
through the selected timeslots of the E1-i port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
As shown in Table 5-12, the loopback is activated only on the timeslots specified
by the user during the activation of the loopback. As a result, there is no
E1-i port: only the flow of payload carried by the specified timeslots is disrupted.
It is not allowed to activate loopbacks on timeslots assigned to HDLC ports.
I/O Modules
The following sections briefly describe each type of loopback on E1 and E1-i ports
of I/O modules. Table 5-13 shows the paths of the signals when each loopback is
activated.
Table 5-13. Loopbacks on E1 and E1-i Ports of I/O Modules

I/O
Local loopback on E1
port (M8E1, M16E1,
ASMi-54C/N, OP-108C/E1,
OP-108C, OP-34C/E1,
OP-34C modules)
Port
Interface
CL
DS1
Cross-Connect
Matrix
"1 "
E1 Ports
5-69

I/O
Remote loopback on E1
port (M8E1, M16E1,
ASMi-54C/N, OP-108C/E1,
OP-108C, OP-34C/E1,
OP-34C modules)
Port
Interface
CL
DS1
Cross-Connect
Matrix
I/O Interface
Local loopback on E1/E1-i

timeslots (M8E1, M16E1,
ASMi-54C/N, OP-108C,
OP-34C modules)
Remote loopback on
E1/E1-i timeslots (M8E1,
M16E1, ASMi-54C/N,
OP-108C, OP-34C
modules)
1
2
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
1
2
..
..
.
DS1
Cross-Connect
Matrix
Local Loopback on E1 Port of I/O Module

transmission through a selected E1 port: this path starts at the other Megaplex4100 port(s) connected to the selected port, passes through the cross-connect
matrix in the CL module, and continues up to the port line interface. Within the
tested module, the path includes most of the line interface circuits serving the
selected port, and the operation of the routing circuits that handle the port
signals within the module.
As shown in Table 5-13, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed all-ones signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on E1 Port of I/O Module

The remote port loopback is used to test the line interface circuits of a selected
E1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
5-70
E1 Ports
As shown in Table 5-13, when a remote loopback is activated on an E1 port, that

port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
operates normally with the local port loopback. In this case, the remote unit must
If the local Megaplex-4100 unit also operated normally when the local port
loopback was activated, then while the remote loopback is connected the local
unit should receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of E1 I/O Module Port

The local loopback on selected timeslots of an E1 port is used to return the
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the E1 port.
As shown in Table 5-13, the loopback is activated within the I/O module routing
matrix, and only on the timeslots specified by the user during the activation of
the loopback. As a result, there is no disturbance to services provided by means
of the other timeslots of the same port: only the flow of payload carried by the
specified timeslots is disrupted.
You can activate the loopback on any individual timeslot, or on several arbitrarily
selected timeslots. You cannot activate loopbacks on timeslots assigned to HDLC
ports.
This convenience feature is also available for loopback deactivation. The
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
Remote Loopback on Timeslots of E1 I/O Module Port

The remote loopback on selected timeslots of an E1 port is used to return the
the transmit path. This loopback is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the E1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
of the other timeslots of the same port. Only the flow of payload carried by the
You cannot activate loopbacks on timeslots assigned to HDLC ports.
The other features related to loopback activation/deactivation described above
for the local loopback on timeslots are also applicable to the remote loopback.
E1 Ports
5-71
E1 Port Loopbacks on Remote Optimux Devices

Megaplex-4100 features local and remote E1 loopbacks on the remote Optimux
devices connected to optical links of its OP-108C and OP-34C modules.
A typical signal flow for a local loopback on an E1 port of a remote Optimux is
shown in Figure 4-9. The remote Optimux device can be one of the following:
Optimux-108/108L connected to OP-108C module (Section A or B)
Optimux-34 connected to OP-34C module.
The number of E1 ports is 4 for Optimux-108/108L and 16 for Optimux-34.

Remote Optimux
Megaplex-4100
"1"
CL
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
E1 Payload
Mux/Demux
E1
Port 1
..
.
..
..
.
LIU 4
E1
Port
4(16)
Figure 4-9. Typical Signal Flow for E1 Port Local Loopback on Remote Optimux Device
When a local loopback on an E1 port of the connected Optimux is activated by an
OP module command, the E1 port transmit signal is returned to the input of the
port receive path (the E1 port signal is disconnected from the transmit path and
is replaced by an AIS signal).
While the loopback is activated, the tested Optimux port will receive its own
signal, and therefore must operate normally. In addition, the user equipment
connected to the tested E1 port must also receive its own signal and thus it must
be synchronized.
This test checks the operation of the far end Optimux E1 port interface, and the
connections to the E1 equipment attached to the far end E1 port.
A typical signal flow for a remote loopback on an E1 port of a remote Optimux is
shown in Figure 4-10.
Megaplex-4100
Local OP-34C or
OP-108C Section
Remote Optimux
"1"
CL
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
E1 Payload
Mux/Demux
..
.
LIU 4
(16)
E1
Port 1
..
.
..
E1
Port 4
(16)
Figure 4-10. Typical Signal Flow for E1 Port Remote Loopback on Remote Optimux
When a remote loopback on an E1 port of the connected Optimux is activated by
an OP module command, the received E1 signal is returned to the input of the
port transmit path after being processed by the internal E1 port, and is
5-72
E1 Ports
transmitted back to the OP module (the E1 port signal is disconnected from the
receive path and is replaced by an AIS signal).
Therefore, the corresponding internal E1 port of the OP module receives its own
signal, and it must operate normally. In addition, the OP module user equipment
connected via the tested E1 port must also receive its own signal and thus it
must be synchronized.
This test checks the connections between the users E1 equipment connected via
the tested internal E1 port of the local OP module, the operation of the OP
module link (section) and of the remote Optimux, and the network connections
between the local OP module and the remote Optimux.
Note
The same loopback can be activated/deactivated by a supervision terminal

connected to the far end Optimux.
Local and Remote Loopbacks on Remote ASMi Modems from E1-i

Ports of ASMi-54C/N Module
E1-i ports of ASMi-54C/N module feature additional local and remote loopbacks
on remote ASMi modems. Availability of loopbacks and their activation command
depend on the remote modem flavor (far-end-type). The following table lists the
loopbacks available on e1-i ports of ASMi-54C/N module for each far end type.
Table 5-14. Local and Remote Loopbacks on Remote ASMi Modems from E1-i Ports of ASMi-54C/N
Module
Far-end-type
Loopback
Far-end Device Ports

Tested
Figure
asmi52 (ASMi-52 or
ASMi-52L standalone)
remote-on-remote
E1
Figure 5-6
asmi52-e1-eth (ASMi-52
standalone with E1 and
LAN ports (Mux type))
remote-on-remote
asmi52-e1-dte (ASMi-52
standalone with E1 and
serial ports (Mux type))
remote-on-remote serial
Serial
Figure 5-6
local-on-remote serial
Serial
Figure 5-7
remote-on-remote e1
E1
Figure 5-6
local-on-remote e1
E1
Figure 5-7
(ASMi-52 standalone with
E1 and serial ports (Mux
type), 4M/4W
functionality)
remote-on-remote
Odd e1-i ports of

ASMi-54C/N module =
loopback on E1 ports of
remote modem
Figure 5-6
asmi54 (ASMi-54 or
ASMi-54L standalone)
remote-on-remote
E1 ports
Figure 5-6
local-on-remote
E1 ports
Figure 5-7
Figure 5-7
local-on-remote
E1
Figure 5-7
local-on-remote
local-on-remote
Figure 5-6
Figure 5-7
Even e1-i ports =

loopback on Serial ports
of remote modem
E1 Ports
5-73
Far-end-type
Loopback
Far-end Device Ports

Tested
Figure
standalone configurable
via EOC)
remote-on-remote
E1 ports
Figure 5-6
local-on-remote
E1 ports
Figure 5-7
Note
Only one loopback at a time can be activated from Megaplex-4100. At any

moment the last loopback command is valid and overrides the previous loopback
command.
Figure 5-6 shows the signal paths of a typical remote loopback on the remote
ASMi modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
Megaplex-4100/4104
CL
Remote
Loopback
ASMi-54C/N
ASMi-52/54
E1 or DTE
Routing
Matrix
Port e1-i 1
..
..
.
Bus
Interface
Other Port
Interface
Port e1-i 8
..
E1 or Serial
..
Port*
.. *When far-end-type=high-speed.. mux-serial-e1, loops on ASMi E1
ports are activated from odd e1-i
ports and loops on ASMi serial
ports - from even e1-i ports
Figure 5-6. Remote Loopback on Remote Unit, Signal Paths
Local Loopback on Remote Unit

Figure 5-7 shows the signal paths of a typical local loopback on the remote ASMi
modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a local loopback request
to the remote modem connected to that channel. The command is sent through
the inband eoc channel configured on the remote modem.
5-74
E1 Ports
Megaplex-4100/4104
CL
Local
Loopback
ASMi-54C/N
ASMi-52/54
E1 or DTE
Routing
Matrix
Port e1-i 1
Bus
Interface
Other Port
Interface
..
..
.
Port e1-i 8
..
E1 or Serial
..
Port*
. *When far-end-type=high-speed..
. mux-serial-e1, loops on ASMi E1
ports are activated from odd e1-i
ports and loops on ASMi serial
ports - from even e1-i ports
Figure 5-7. Local Loopback on Remote Unit, Signal Paths
BER TEST on the E1 and E1-i Ports of ASMi-54C/N Module

The BER test, activated by the command bert, is used to evaluate data
transmission through selected timeslots of the link connected to a selected E1 or
E1-i port of the ASMi-54C/N module without using external test equipment.
Data transmission is checked by applying a test sequence generated by an
internal test sequence generator towards the remote equipment. The timeslots in
which the sequence is transmitted, are defined by means of the bert command.
The test sequence is 2E-15.
To check that the line is alive or verify the BER detection calibration, the user can
also inject single errors into the transmitted pattern.
The BER Test on unframed ports is performed per port, while on framed ports it
is performed also per individual timeslot.
The timeslot on which BERT is performed must be cross-connected.
The transmitted data is returned by means of a loop, somewhere along the data
path, to the test sequence evaluator. The evaluator compares the received data,
bit by bit, to the original data and detects any difference (bit error). The output
of the evaluator is sampled during module polling, to check whether errors were
detected in the interval between consecutive pollings.
The number of errors is accumulated from the activation of the BER test.
The test results are displayed on a supervision terminal as a number in the range
of 0 (no errors detected during the current measurement interval) through
63535. The meaning of the displayed parameters is given in the table below.
The BER test duration is infinite (to stop the test manually, use no bert
command).
Table 5-15. Bert Performance Parameters

Parameter
Description
Status
Displays the BERT status: Not Active, In Sync or Out of Sync
Run Time (Sec)
Displays the total time the test is running in seconds
Sync Loss (Sec)
Displays the number of times Sync Loss was detected since BERT
started to run
Bert Error Count
Displays the total number of bit errors detected
E1 Ports
5-75
Parameter
Description
Pattern
Displays the BERT pattern (always 2e-15)
ES (Sec)
Displays the total number of seconds in which errors have been

detected
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the Megaplex-4100. Therefore, when you initiate a loopback, you have the
option to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated
without operator intervention. However, you can always deactivate a loopback
activated on the local Megaplex-4100 before this timeout expires. When using
inband management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).
Activating Loopbacks and BER Tests
To perform a loopback or BER test on the E1 port:

1. Navigate to configure port e1 <slot>/<port>/<tributary> to select the E1 port
to be tested.
The config>port>e1>(<slot>/<port>/<tributary>)# prompt is displayed.
Note
<tributary> relates to OP modules only:

For OP-108C, <port>/<tributary> is 1/1 to 1/4, 3/1 to 3/4.
For OP-34C, <port>/<tributary> is 1/1 to 1/16.
To perform a loopback or BER test on the internal E1 port:

1. Navigate to configure port e1-i <slot>/<port> to select the internal E1 port to
be tested.
The config>port>e1-i>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Activating and configuring

the direction of the
loopback
loopback {local | remote | remoteon-remote } [time-slot <1..31>]
local local loopback
Stopping the loopback
no loopback
5-76
E1 Ports
remote remote loopback

remote-on-remote remote loopback on
remote ASMi modem (e1-i ports of
ASMi-54C/N only)
Task
Command
Comments
Activating the BER test and

configuring its parameters
bert [ts <ts number 1..31>]

[inject-error single]
The [ts <ts number in the range from 1

to 31>] command is used only for
framed ports and is mandatory for these
ports.
The timeslot on which BERT is performed
must be cross-connected.
CL flip stops the BERT session.
Stopping the BER test
no bert
Displaying the BER test

results
show bert
Clearing the BER test

counters
clear-bert-counters
A typical display:
Status
:
Bit Error Count:
Pattern
:
Run Time (Sec) :
ES (Sec)
:
Sync Loss (Sec):
Not Active
1
2e-15
1
1
1
To perform a loopback on the E1 port of the remote Optimux:

1. Navigate to configure port mux-eth-tdm <slot>/<port> to select the optical
link connected to the device being tested.
Note
The number of <port> is:

1 or 3 for OP-108C
1 for OP-34C
Remote devices connected to protection ports 2 and 4 cannot be configured.

The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.
Type remote.
Type configure port e1 <port> to select the E1 port of the remote device to be
tested.
Note

1 to 4 for Optimux-108/108L
1 to 16 for Optimux-34.
Task
Command
Comments
Activating and configuring the

direction of the loopback and
the duration of it (in minutes)
loopback {local | remote}

[duration <duration in minutes
1..30> ]
local local loopback:
no loopback
E1 Ports
5-77
Viewing an E1 Port Status

Follow the instructions below for viewing the status of the E1 port 5/1 as an
example.
To view the E1 port status:
At the config>port>e1(<slot>/<port>/<tributary>)# prompt, enter show

status.
The status information appears as illustrated below.
Note

mp4100>config>port>e1(5/1)# show status
Name
:
Administrative Status : Down
Operation Status
: Up
Connector Type
: DB44
Displaying E1 Port Statistics

E1 and E1-i ports of Megaplex-4100 feature the collection of statistical
diagnostics per relevant parts of ITU-T G.826, thereby allowing the carrier to
monitor the transmission performance of the links.
To display the E1 port statistics:
Note
At the prompt config>slot>port>e1(<slot><port>[<tributary>])#, enter show

statistics followed by the parameters listed below.

To display the E1-i port statistics:
At the prompt config>slot>port>e1-i(<slot><port>)#, enter show statistics

followed by the parameters listed below.
Task
Command
Comments
show statistics {total | all | current}
total total statistics of last 96

intervals
current current statistics
all all statistics: first current

statistics, then statistics for all
valid intervals, and finally total
statistics
5-78
E1 Ports

Task
Command
for a specific
interval
show statistics interval <interval-num 1..96>
Comments
E1 port statistics are displayed.
Note
BES, LOFC and Rx Frames Slip are displayed for framed formats only.
For example:
Current statistics:
mp4100>config>port>e1(1/2)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 191
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Statistics for interval 67:
mp4100>config>port>e1(3/1)# show statistics interval 67
Interval Number : 67
Interval
--------------------------------------------------------------ES
: 16
SES
: 1
UAS
: 589
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total statistics:
mp4100>config>port>e1(1/2)# show statistics total
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
All statistics:
mp4100>config>port>e1(1/2)# show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 171
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
E1 Ports
5-79
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 1
Interval
--------------------------------------------------------------ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 2
Interval
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
The counters are described in Table 5-16, Table 5-17 and Table 5-18.
Table 5-16. E1 Port Statistics Parameters Current 15-Minute Interval

Parameter
Description
ES
Displays the number of errored seconds in the current 15-minute interval.

An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
UAS
Displays the number of unavailable seconds (UAS) in the current interval.

An unavailable second is one of the following:
SES
Any second following 10 consecutive SES seconds
A second for which any of the previous 10 consecutive seconds was also a UAS
and any of the previous 10 consecutive seconds was a SES.
Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES
Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
5-80
E1 Ports

Parameter
Description
LOFC
Displays the number of LOFC in the current interval.
The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip
Displays the number of Rx Frames Slips in the current 15-minute interval.

A CSS is a second with one or more controlled slip events.
Time elapsed
The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
Valid Intervals
The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96).
Table 5-17. E1 Port Statistics Parameters Selected 15-Minute Interval

Parameter
Description
ES
Displays the total number of errored seconds (ES) in the selected interval
UAS
Displays the total number of unavailable seconds (UAS) in the selected interval
SES
Displays the total number of severely errored seconds (SES) in the selected interval
BES
Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC
Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number
The number of interval for which statistics is displayed.
Note: The sequence of intervals is different for the E1 ports of different module
families:
For the M8E1 modules, Interval #1 is the latest in time
For the M16E1, ASMi-54C/N, OP-108C and OP-34C modules, Interval #1 is the
earliest in time.
Table 5-18. E1 Port Statistics Parameters Total Statistics

Parameter
Description
ES
Displays the total number of errored seconds (ES) since statistics are available
UAS
Displays the total number of unavailable seconds (UAS) since statistics are available
SES
Displays the total number of severely errored seconds since statistics are available
BES
Displays the total number of bursty errored seconds (BES) since statistics are available
LOFC
Displays the total number of loss of frame alignment events since statistics are available
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events since statistics are
available
E1 Ports
5-81
Clearing Statistics
To clear the statistics for an E1 port:
At the prompt config>port>e1<slot>/<port>)#, enter clear-statistics.

To clear the statistics for an E1-i port:
At the prompt config>port>e1-i<slot>/<port>)#, enter clear-statistics.

5.11 T1 Ports
The following table shows the number of t1 and t1-i ports and the features
supported by each Megaplex-4100 module. The hierarchical position of t1 and
t1-i ports is slot:port for all the modules. The digits in brackets (1 to 3) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Table 5-19. Megaplex-4100 T1 and Internal T1 Ports

T1 Ports (t1)
Internal T1 Ports (t1-
Feature/
Command
i)
M8T1
M16T1
CL.2
Number of ports
16
84
name
shutdown
inband-management
(1)
(1)
(1)
line-interface
line-type
(2)
line-length (DSU only)
line-code
line-buildout (CSU only)
signaling)
(1)
(1)
(1)
restoration-time
signaling- profile
(1)
(1)
out-of-service (voice, data,
5-82
T1 Ports
T1 Ports (t1)
Internal T1 Ports (t1-
Feature/
Command
i)
M8T1
M16T1
CL.2
idle-code
(1)
(1)
(1)
vc-profile
(3)
1 - N/A for Unframed

2 Unframed is not supported
3 Applicable if line type is unframed and the link is directly mapped to SDH-SONET vc12-vt2
Note
OP-108C/E1 are LRS-102 modules with E1 physical ports, which can also be
installed and operated in Megaplex-4100.
Standards
The T1 interface complies with ANSI T1.403-1989, AT&T Pub. 54016, AT&T
TR-62411 and ANSI T1.107.4 standards.
External T1 Link Interfaces are available in M8T1 and M16T1 modules. Internal T1
ports are available in CL.2 modules. The parameters configurable for each module
can be chosen from Table 5-10 . General description of T1 port parameters is
given in the following sections.
Framing
The external and internal T1 ports can be independently configured in accordance
with the desired ITU-T framing mode and signaling formats:
D4 (SF) framing (12 frames per multiframe)
ESF framing (24 frames per multiframe)
Unframed mode: enables transparent transfer of 1.544 Mbps streams,

including streams with proprietary framing.
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode can be independently selected for each extermal or internal T1
port of the I/O module. It is configured by means of line-type parameter.
Line Interface (M8T1 only)

Each T1 line interface has an integral CSU, which enables operation with line
attenuations up to 34 dB. The nominal transmit level is 3V.
The CSU transmit level must be adjusted to ensure reliable operation of the
network. It can be attenuated by 7.5, 15, or 22.5 dB, for compliance with FCC
T1 Ports
5-83
Rules Part 68A. This adjustment minimizes the interference your transmit signal
causes to other users that transmit their signals on other pairs of the same cable.
The required setting depends mainly on the length of the cable that connects the
T1 port and the first repeater down the line.
Repeaters are usually spaced a mile apart. They are therefore designed to
optimally handle signals attenuated by one mile length of cable. If the T1 port
were closer, the repeater would receive your signal at a higher level. This will not
significantly improve the handling of your signal, but will certainly increase the
interference coupled from your pair to repeaters that serve other pairs in the
cable. To prevent this, you can select an attenuation value that will bring your
signal level closer to the expected repeater signal level. This is achieved by
connecting, as required, one, two, or three artificial line sections in series with
your T1 transmit signal. Each line section introduces a nominal attenuation of
7.5 dB (equivalent to the attenuation of approximately 1000 feet of cable). Your
system administrator or data carrier will give you the proper setting for each
port.
The line interface can also emulate a DSU interface. The selection CSU/DSU is
defined by the line-interface parameter. The relative output transmit level of the
port is selected by means of the line-buildout parameter.
Line Length
When configured for DSU emulation, the line transmit signal is user-adjustable for
line lengths of 0 to 655 feet in accordance with AT&T CB-119. The transmit signal
mask is selected in accordance with the transmit line length, to meet DSX-1
requirements, as specified by AT&T CB-119. The following selections are
available:
0 133 Ft
133 266 Ft
266 399 Ft
399 533 Ft
533 655 Ft.
These values define the length of the cable (in feet) connected between the port
connector and the network access point.
Zero Suppression
Zero suppression is user-selectable, separately for each port: transparent (AMI)
coding, B7ZS, or B8ZS. It is configured by means of line-code parameter.
Interface Type
The external T1 links have 100 balanced interfaces.
Handling of T1 Alarm Conditions

The external and internal T1 ports support two types of indications in the individual
timeslots: idle timeslots and out-of-service (OOS) indications.
5-84
T1 Ports
Idle Timeslot Indication. A special code can be transmitted in empty timeslots

(timeslots which do not carry payload).
OOS Indications. The OOS code is inserted in individual timeslots to signal the
equipment routed to one of the module ports that the link connected to the
external port is out-of-service (e.g., because of a loss of frame
synchronization).
The idle code and OOS indications can be independently configured for each
module port. Moreover, separate OOS codes can be transmitted in the timeslots,
in accordance with the type of payload carried by each timeslot (voice or data).
T1 Payload Processing
The Megaplex-4100 T1 modules support three main types of payload per
timeslot:
Data timeslots: timeslots which are transparently transferred from port to

port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
Voice timeslots: timeslots carrying PCM-encoded payload, with A-law

companding for M8E1 ports and -law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
standards. The user can specify translation rules for the signaling
information, called signaling profiles see details in the Signaling Profiles
section below.
Management timeslots: with framed signals, one timeslot can be assigned in

any port to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). It is also possible to define unidirectional flows, called unidirectional
broadcasts, from one source (a timeslot of a source port) to multiple destinations
(each destination being a selected timeslot of another port).
In case of data timeslots, the flow of payload is normally unidirectional. If the
application requires bidirectional flows, cross-connect must be configured
symmetrically for both directions.
OOS Signaling
If communication between modules located in different Megaplex units fails, e.g.,
because loss of main link synchronization, it is necessary to control the state of
the signaling information at each end of the link. This activity, called
out-of-service (OOS) signaling, is performed by the M8T1 modules and can be
selected in accordance with the specific application requirements, on a per-link
basis.
The OOS signaling options supported by the M8T1 modules are as follows:
Signaling forced to the idle state for the duration of the out-of-service
condition (force-idle). This option is suitable for use with all the VC module
types.
T1 Ports
5-85
Signaling forced to the busy state for the duration of the out-of-service
condition (force-busy). This option is suitable for use with E&M and FXO
modules, but not with FXS modules.
Signaling forced to the idle state for 2.5 seconds, and then changed to the
busy state for the remaining duration of the out-of-service condition
(idle-busy). This option is suitable for use with E&M and FXO modules, but
not with FXS modules.
Signaling forced to the busy state for 2.5 seconds, and then changed to the
idle state for the remaining duration of the out-of-service condition
(busy-idle). This option is suitable for use with all the VC module types.
Inband Management
T1 and internal T1 ports of Megaplex-4100 using a framed mode feature inband
management access to the end users equipment provided by configuring a
dedicated management timeslot.
The transfer of inband management traffic is controlled by using synchronous
PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
Transmission of RIP2 routing tables is done via the following options:
Proprietary RIP Management traffic is routed using RAD proprietary routing

protocol
RIP2 In addition to the RAD proprietary routing protocol, RIP2 routing is

also supported.
Factory Defaults
Megaplex-4100 is supplied with all t1/t1-i ports disabled. Other parameter
5-86
T1 Ports
Parameter
Default Value
line-type
esf
restoration-time
10-sec
line-interface
csu
idle-code
7F
inband-management
no inband-management (disabled)
inband-management routing-protocol
none
out-of-service - voice
00
out-of-service - data
00
out-of-service - signaling
force-idle
signaling-profile
line-code
b8zs
line-length
0-133
Parameter
Default Value
line-buildout
0db
duration
infinite
Configuring T1 Port Parameters
To configure the T1 port parameters:

1. Navigate to configure port t1 <slot>/<port> to select the T1 port to
configure.
The config>port>t1>(<slot>/<port>)# prompt is displayed.
Enter all necessary commands according to the tasks listed below (see Table 5-19
for parameters supported in each module).
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specifying T1 framing
mode
line-type {unframed | esf | sf}
Setting the line code

used by the port, and the
zero suppression method
line-code {ami | b8zs | b7zs}
Specifying T1 operation
mode
line-interface {dsu | csu}
Specifying the length of

the T1 line in DSU mode
line-length {0-133 | 134-266 | 267-399 |

400-533 | 534-655}
Specifying the code

timeslots in T1 frames
The available selections are [0x40 to 0x7F]

and [0xC0 to 0xFF]
Enabling inband
its parameters

{ppp | fr} [routing-protocol {none |
prop-rip | rip2} ]

encapsulation
For guaranteed clear channel capability, use

B8ZS; do not use B7ZS for ports carrying
inband management

timeslot
T1 Ports
5-87
Task
Command
Transmitting an
(OOS)
out-of-service [ voice <00 to FF (hexa)>]

[data <00 to FF (hexa)>] [signaling
busy-idle} ]

profile
signaling-profile { 1 | 2 | 3 | 4 | 5 | per-ts}
Comments
Using no signaling-profile cancels signaling

profile setting
For creating and configuring signaling
profiles, see Signaling Profiles.

profile per a single
timeslot or per timeslot
range
timeslots-signaling-profile [tsx] {1 | 2 | 3 |
4 | 5}

loss of frame
restoration-time {1-sec | 10-sec}
timeslots-signaling-profile [tsx..tsy] {1 | 2 |
3 | 4 | 5}
This command is available for voice

timeslots only, if you selected per-ts under
signaling-profile
This command is possible for multiple
timeslots only if they are consecutive
Specifying the line buildout (relative output

transmit level of the port)
line-buildout {0db | -7dot5db | -15db |

-22dot5db}
CSU mode (M8T1 module) only
the port
Relevant for M16T1 and Megaplex Optimux

modules. M8T1 does not support this
feature.
Using no vc removes the profile.
Configuring Internal T1 Port Parameters
To configure the internal T1 port parameters:

1. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
configure.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short
description to port
name <string>
5-88
T1 Ports
Task
Command
Comments
port
no shutdown
Specifying T1 framing
mode
line-type {unframed | esf | sf}
Specifying the code

timeslots in T1 frames
The available selections are [0x40 to 0x7F]

and [0xC0 to 0xFF]
Enabling inband
its parameters

{ppp | fr} [routing-protocol {none |
prop-rip | rip2} ]

encapsulation
timeslot

loss of frame
restoration-time {1-sec | 10-sec}

the port
Example 1
The following example illustrates how to configure the T1 port labeled 1 on the
M8T1 module installed in slot 9 as follows:
Set the T1 framing mode to SF.
Set the restoration time to 10 sec.
Set the line code to AMI.
Set the idle code to 8E.
T1 Ports
5-89
mp4100>config>port>t1(9/1)#
line-type sf
line-code ami
restoration-time 10-sec
idle-code 0x8E
no shutdown
Example 2
This section illustrates how to configure inband management via a dedicated
timeslot on M8T1 Module.
1. Program an M8T1 module in Slot 1 and configure inband management via T1
port 1 with the following parameters:
Dedicated timeslot - #24
Inband management protocol: synchronous PPP over HDLC encapsulation
mp4100>config>slot# 4 card-type e1-t1 m8t1

mp4100>config>port# t1 1/1 no shutdown
mp4100>config>port# t1 1/1 line-type sf
mp4100>config>port# e1 1/1 inband-management 24 protocol ppp
routing-protocol prop-rip
Configure router interface 5.
mp4100>config>router# 1 interface 5 address 17.17.17.17/24
Bind T1 port 1/1 to router interface 5.
mp4100>config>router# 1 interface 5 bind t1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate T1 port 2 of M8T1 module in Slot 9.
Configure signaling profile per ts:
TS-10 to profile 2
TS-1 to 9 to profile 3
Result : OK
no shutdown
timeslots-signaling-profile [1..9] 3
commit
Displaying signaling profile per ts:
5-90
T1 Ports
mp4100>config>port>t1(9/2)# info detail

name "IO-9 e1 02"
no shutdown
line-type sf
line-code ami
interface-type balanced
idle-code 0x7f
restoration-time 10-sec
out-of-service voice 0x00 data 0x00 signaling
rx-sensitivity short-haul
force-idle
Testing T1 Ports
The Megaplex-4100 T1 ports feature test and loopback functions at the port and
timeslot levels. The available loopbacks depend on the port type (T1, T1-i) and
the specific module. The following table shows the loopbacks supported by T1
and T1-i ports on each Megaplex-4100 module. In addition, M8T1 modules
support network line loopback (LLB) and network payload loopback (PLB). T1
ports of other I/O modules do not support network-controlled loopbacks.
The hierarchical position of t1 and t1-i ports is slot:port for all the modules. The
digits in brackets (1,2) denote restrictions or other special remarks regarding
implementation of this loopback in specific modules.
Table 5-20. Loopbacks Supported by Megaplex-4100 T1 and T1-i Ports
T1 Ports (t1)
Lopback Type
Internal T1 Ports (t1-i)
M8T1
M16T1
CL.2
Local Loop
Remote Loop
Loop per TS Local
Loop per TS Remote
Local On Remote
Remote Loop On Remote
1 - Loopback on local and remote devices
T1 Ports
5-91
2 - Only for local internal t1 ports.
CL Modules
The following sections briefly describe each type of loopback on T1-i ports of CL
modules. Table 5-21 shows the paths of the signals when each or loopback is
activated.
Table 5-21. Loopbacks on T1-i ports of CL.2 Modules
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
I/O Port
..
..
..
..
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
T1-i port
..
..
..
E1-i/T1-i Framers
1
Remote loopback
on T1-i port
..
..
..
E1-i/T1-i Framers
1
Local loopback on
timeslots of
T1-i port
5-92
T1 Ports
..
..
..
Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
Framers
CL
1
2
I/O Port
.
.
.
..
.
.
.
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Remote loopback
on timeslots of
T1-i port
..
..
..
Local Loopback on T1-i Port

The local T1-i port loopback is used to test the intra-Megaplex-4100 paths of the
signals intended for transmission through a selected T1-i port. These paths start
at the other Megaplex-4100 port(s) connected to the tested T1-i port, pass
through the DS1 cross-connect matrix in the CL module, and continues up to the
framer of the T1-i port within the SDH/SONET link interface. These paths include
all of the Megaplex-4100 local ports connected to the tested T1-i port, and in the
particular the operation of the DS1 cross-connect matrix circuits that handle the
signals directed to the tested T1-i port within the CL module.
The local T1-i port loopback is activated within the T1-i framer of a selected CL
T1-i port, as shown in Table 5-21.
Remote Loopback on T1-i Port

The T1-i port remote loopback is activated on the framer serving the port within
the SDH/SONET link interface, as shown in Table 5-21.
Local Loopback on T1-i Port Timeslots

The local loopback on selected timeslots of a T1-i port is used to return the
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.
T1 Ports
5-93
This test is recommended for testing the signal paths between the T1-i port and
an I/O port of another module that uses only a fraction of the available T1-i port
bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 5-21. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
You can activate the loopback on any individual timeslot, or on several arbitrarily
selected timeslots. You cannot activate loopbacks on timeslots cross-connected
with HDLC ports.
Remote Loopback on T1-i Port Timeslots

The remote loopback on selected timeslots of a T1-i port is used to return the
the transmit path. The corresponding timeslots received from the local equipment
are disconnected.
through the selected timeslots of the T1-i port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 5-21. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
specified timeslots is disrupted. You cannot to activate loopbacks on timeslots
assigned to HDLC ports.
I/O Modules
The following sections briefly describe each type of loopback on T1 and T1-i ports
of I/O modules. Table 5-13 shows the paths of the signals when each or loopback
is activated.
Table 5-22. Loopbacks on T1 and T1-i Ports of I/O Modules

I/O
Local loopback on T1 port (M8T1,

M16T1 modules)
Port
Interface
CL
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on T1 port (M8T1,

M16T1 modules)
5-94
T1 Ports
Port
Interface
DS1
Cross-Connect
Matrix
I/O
CL
I/O Interface
1
Local loopback on T1 timeslots

(M8T1, M16T1 modules)
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
1
Remote loopback on T1 timeslots

(M8T1, M16T1 modules)
..
..
.
DS1
Cross-Connect
Matrix
Local Loopback on T1 Port of I/O Module

transmission through a selected T1 port: this path starts at the other
Megaplex-4100 port(s) connected to the selected port, passes through the
cross-connect matrix in the CL module, and continues up to the port line
interface. Within the tested module, the path includes most of the line interface
circuits serving the selected port, and the operation of the routing circuits that
handle the port signals within the module.
As shown in Table 5-13, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed all-ones signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on T1 Port of I/O Module

The remote port loopback is used to test the line interface circuits of a selected
T1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in Table 5-13, when a remote loopback is activated on a T1 port, that
port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.
operates normally with the local port loopback. In this case, the remote unit must
T1 Ports
5-95
If the local Megaplex-4100 unit also operated normally when the local port
loopback was activated, then while the remote loopback is connected the local
unit should receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of T1 I/O Module Port

The local loopback on selected timeslots of a T1 port is used to return the
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the T1 port.
of the other timeslots of the same port: only the flow of payload carried by the
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
assigned to HDLC ports.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
Remote Loopback on Timeslots of T1 I/O Module Port

The remote loopback on selected timeslots of a T1 port is used to return the
the transmit path. This test is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the T1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
matrix, and only on the timeslots specified by the user. As a result, there is no
port: only the flow of payload carried by the specified timeslots is disrupted.
It is not allowed to activate loopbacks on timeslots assigned to HDLC ports.
Loopback Duration
5-96
T1 Ports
Activating Loopbacks
To perform a loopback on the T1 port:

1. Navigate to configure port t1 <slot>/<port> to select the T1 port to be
tested.
The config>port>t1>(<slot>/<port># prompt is displayed.
To perform a loopback on the internal T1 port:

1. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
be tested.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments

loopback and the duration
of it (in minutes)
loopback {local | remote} [time-slot

<1..24>] [duration <duration in
minutes 1..30> ]
no loopback
Viewing a T1 Port Status

Follow the instructions below for viewing the status of a T1 port.
To view the T1 port status:
At the config>port>t1(<slot>/<port># prompt, enter show status.

mp4100>config>port>t1(3/1)# show status

Name
:
Operation Status
: Up
Connector Type
: DB44
Displaying T1 Port Statistics

T1 and T1-i ports of Megaplex-4100 feature the collection of statistical
diagnostics per ANSI T1.403, thereby allowing the carrier to monitor the
transmission performance of the links.
T1 Ports
5-97
To display the T1 port statistics:
At the prompt config>slot>port>t1(<slot><port>)#, enter show statistics

To display the T1-i port statistics:
At the prompt config>slot>port>t1-i(<slot><port>)#, enter show statistics

Task
Command
Comments
total - Total statistics of last 96

intervals
current - Current statistics
all All statistics: first current

statistics, then statistics for all
valid intervals, and finally total
statistics
for a specific
interval
T1 port statistics are displayed. The counters are described in

Table 5-23, Table 5-24 and Table 5-25. For example:
Note
BES, LOFC and Rx Frames Slip are displayed for framed formats only.
For example:
Current statistics:
mp4100>config>port>t1(1/2)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 191
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
mp4100>config>port>t1(3/1)# show statistics interval 67
Interval Number : 67
Interval
--------------------------------------------------------------ES
: 16
SES
: 1
UAS
: 589
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total statistics:
5-98
T1 Ports
mp4100>config>port>t1(1/2)# show statistics total

Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
All statistics:
mp4100>config>port>t1(1/2)# show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 171
Valid Intervals
: 2
ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 1
Interval
--------------------------------------------------------------ES
: 0
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Interval Number : 2
Interval
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
Total
--------------------------------------------------------------ES
: 2
SES
: 0
UAS
: 0
BES
: 0
Rx Frames Slip : 0
LOFC
: 0
T1 Ports
5-99
Table 5-26. T1 Port Statistics Parameters Current 15-Minute Interval

Parameter
Description
ES

An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
UAS
Displays the number of unavailable seconds (UAS) in the current interval.

An unavailable second is one of the following:
SES
Any second following 10 consecutive SES seconds
A second for which any of the previous 10 consecutive seconds was also a UAS
and any of the previous 10 consecutive seconds was a SES.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES
Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
LOFC
Displays the number of LOFC in the current interval.

The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip
Displays the number of Rx Frames Slips in the current 15-minute interval.

A CSS is a second with one or more controlled slip events.
Time elapsed
The range is 1 to 900 seconds.
Valid Intervals
displayed, in addition to the current (not finished) interval (up to 96).
Table 5-27. T1 Port Statistics Parameters Selected 15-Minute Interval

Parameter
Description
ES
UAS
Displays the total number of unavailable seconds (UAS) in the selected interval
SES
BES
Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC
Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number
Displays the number of interval for which statistics is displayed
Note: The sequence of intervals is different for the T1 ports of different module
families:
5-100
T1 Ports
For the M8T1 modules, Interval #1 is the latest in time
For the M16T1 modules, Interval #1 is the earliest in time.
Table 5-28. T1 Port Statistics Parameters Total Statistics

Parameter
Description
ES
Displays the total number of errored seconds (ES) since statistics is available
UAS
Displays the total number of unavailable seconds (UAS) since statistics is available
SES
Displays the total number of severely errored seconds since statistics is available
BES
Displays the total number of bursty errored seconds (BES) since statistics is available
LOFC
Displays the total number of loss of frame alignment events since statistics is available
Rx Frames Slip
Displays the total number of loss of of Rx Frames Slip events since statistics is available
To clear the statistics for a T1 port:
At the prompt config>port>t1<slot>/<port>)#, enter clear-statistics.

5.12 Signaling Profiles

This feature is available for the E1/T1 ports on the M8E1/M8T1 modules.
When CAS is used (always in an M8T1 module, and in an M8E1 module when the
E1 port uses G.732S framing, with or without CRC-4 support), the signaling
information of each voice channel is carried by means of up to four bits (signaling
bits), designated by the applicable standards as bits A, B, C, and D.
The number of bits actually available for carrying signaling information and the
data rate at which signaling information can be transferred, depend on the port
(E1 or T1) and the framing mode being used, which are determined by the
applicable international standards.
The information appearing in the signaling bits can be provided either by voice
interface modules installed in the Megaplex-4100, or by digital PBXs or local
exchange trunks connected to one of the E1 or T1 Megaplex-4100 ports.
Digital PBXs and local exchanges often use dedicated signaling protocols to
exchange the signaling information through the E1 or T1 trunk bits assigned to
CAS, and therefore may interpret the state of CAS bits in proprietary ways. The
CL module can perform signaling protocol conversions, for example to enable
the termination of PBX timeslots by a voice module installed in an I/O slot, to
connect a PBX to PSTN lines, etc.
The format of the signaling information is defined by specifying a profile. A profile
enables the user to specify translation rules for each individual signaling bit. The
available selections are A, B, C, D (value copied from the corresponding incoming
bit), ~A, ~B, ~C, ~D (inverted value of corresponding incoming bit), 0 (always 0),
and 1 (always 1).
Signaling Profiles
5-101
In addition to the translation of individual bits, the receive path conversion

section also defines the signaling bit patterns that indicate the busy and idle
states.
The user can assign a separate profile to each TDM (E1 or T1) port. Each port,
and even individual timeslots of a port, can therefore use different receive and
transmit translation rules. Up to 5 different profiles, each covering a different set
of interoperability requirements, can be defined and stored in the Megaplex-4100
configuration databases.
See also VC-4, VC-4A, VC-8, VC-8A and VC-16 Modules section in Appendix B for
specific considerations regarding voice ports.
Factory Defaults
The default signaling profiles (profile1 to profile5) are provided with no signaling
translation.
Parameter
Default Value
idle-code
0x00
busy-code
0x0f
Each default signaling profile looks as follows.

busy-code
idle-code
a-bit-code
b-bit-code
c-bit-code
d-bit-code
0x0f
0x00
tx a
tx b
tx c
tx d
rx
rx
rx
rx
a
b
c
d
You can change the contents but not the names of each of the 5 profiles.
Configuring CAS Signaling Profiles

Use the following procedure to modify the signaling translation rules contained in
the five signaling profiles supported by Megaplex-4100, in accordance with your
specific application requirements. You can specify different rules for the receive
and transmit directions.
Receive direction: defines the interpretation of the incoming signaling

information, that is, the signaling information received from the external
port. This section enables the user to select the translation of each incoming
bit to the corresponding internal signaling bit (the signaling bit actually sent
to each module which needs the signaling information received by a main
link).
Transmit direction: defines the translation of the internal signaling bits to the
signaling bits transmitted through the external port.
To add a signaling profile:

1. Navigate to configure port.
The config>port# prompt is displayed.
5-102
Signaling Profiles
Type signaling-profile <signaling-profile-name>. Signaling profile name has the

fixed format: profile1 to profile5.
A signaling profile with the specified name is created and the following
prompt is displayed, for example:
config>port>signaling-profile(<profile2>)#.
Configure the signaling profile as described below.
To configure a signaling profile:

1. Navigate to configure port signaling-profile < signaling-profile-name> to
select the signaling profile to configure.
The config>port>signaling-profile(<signaling-profile-name>)# prompt is
displayed.
Task
Command
Comments
Specifying translation rules

for signaling bit A (receive
and transmit directions)
a-bit-code tx {0 | 1 | a | b
| c | d | inverse-a | inverse-b
| inverse-c | inverse-d}
rx {0 | 1 | a | b | c | d | inverse-a
| inverse-b | inverse-c | inverse-d}
0 bit value is always 0
b-bit-code tx {0 | 1 | a | b
rx {0 | 1 | a | b | c | d | inverse-a
c-bit-code tx {0 | 1 | a | b
rx {0 | 1 | a | b | c | d | inverse-a
d-bit-code tx {0 | 1 | a | b
rx {0 | 1 | a | b | c | d | inverse-a

for signaling bit B (receive

for signaling bit C (receive

for signaling bit D (receive

a, b, c, d bit value copied from the
corresponding incoming bit
inverse-a, inverse-b, inverse-c, inverse-d
inverted bit value, related to the



Signaling Profiles
5-103
Task
Command
Comments
Specifying the signaling bit

pattern indicating the busy
state
busy-code {00 to 0F (hexa)}
Hexadecimal number in the range of 0 to

0F (two digits)
The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which, when
converted to binary format, yields the
desired ABCD sequence.
Example: if the busy state is indicated by
the incoming sequence 1000, select 8.
Specifying the signaling bit

pattern indicating the idle
state
idle-code {00 to 0F (hexa)}

0F (two digits)
The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which when
converted to binary format yields the
desired ABCD sequence.
Example
To create and configure signaling profile 1:
mp4100>config#
inverse-a
mp4100>config#
mp4100>config#
mp4100>config#
a-bit-code rx and tx translated to inverse-a
b-bit-code rx and tx b
c-bit-code rx and tx translated to 1
d-bit-code rx and tx d
port signaling-profile profile1 a-bit-code tx inverse-a rx
port signaling-profile profile1 b-bit-code tx b rx b
port signaling-profile profile1 c-bit-code tx 1 rx 1
port signaling-profile profile1 d-bit-code tx d rx d
To display the resulting signaling profile:
mp4100>config>port>signaling-profile(profile1)# info detail

busy-code 0x0f
idle-code 0x00
a-bit-code tx inverse-a rx inverse-a
b-bit-code tx b rx b
c-bit-code tx 1 rx 1
d-bit-code tx d rx d
The screen lists the four signaling bits, A to D, together with their current
translations. In this case, the busy and idle codes are left at their
defaults.
5-104
Signaling Profiles
To assign profile 1 to an E1 port:

mp4100>config>port>e1(9/1)# signaling-profile 1
Note
Pay attention to the syntax:

When configuring the profile n (n=1,2,3,4,5), use profile<n> number
When assigning the configured profile to an E1/T1 port, use simply <n>, not
profile<n>)
5.13 HDLC Ports (I/O Modules)

This section describes HDLC ports defined on M8E1, M8T1 and M8SL module.
These ports can be bound to the physical layer representing E1/T1 ports or
specific timeslots. For HDLC ports defined on CL.2 modules, see HDLC Ports (CL.2
Modules).
Standards
HDLC ports in E1/T1 I/O modules comply with IETF RFC 1990.
Factory Defaults
Megaplex-4100 is supplied with all HDLC ports disabled.
Configuring HDLC Ports
To configure an HDLC port:

1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short
description to the
port
name <string>
Administratively
enabling the port
no shutdown
HDLC Ports (I/O Modules)
5-105
Task
Command
Comments
Binding the
corresponding
E1/T1 port to the
HDLC port
bind e1
<slot>/<port>/[<tributary>]
For the allowed ranges, seeTable 5-44.
bind t1 <slot>/<port>/
bind e1-i <slot>/<port>
bind t1-i <slot>/<port>
When binding e1 ports, optional <tributary> index

relates to Megaplex Optimux cards (OP-34C, OP-108C)
only and denotes their internal E1 ports.
Binding the HDLC port to specific timeslots of E1/T1
physical port is done via the xc command.
Using no before the corresponding command removes
the binding
Assigning VC
profile to the port
Note
It is possible to open only 8 E1/E1-i/T1 links per M8E1/M8SL/M8T1 module and

assign up to 4 HDLC ports to each of them so that the total capacity is 32 HDLC
ports per module. Moreover, every E1/E1-i/T1 used reduces the number of
external E1/T1 links that can be connected to E1/T1 equipment.
5.14 MLPPP Ports

MLPPP ports exist only on M8E1 and M8SL modules and are mapped to a PPP
port. The binding is done in two stages and the PPP port should be further bound
to the physical layer (see Figure 1-8 in Chapter 1).
M8E1 and M8SL modules have one MLPPP port per module.
The MLPPP bundle can use any number of the links supported by the module, that
is, from 1 to 8. All the links (ports) used by the MLPPP bundle must have identical
physical layer parameters and their line-type parameter must be configured as
unframed. Therefore, each bonded link adds 2048 kbps to the available
bandwidth.
Management traffic is carried inband, as part of the Ethernet traffic, using the
dedicated management VLAN configured for the Megaplex-4100 host.
Note that ports bound to MLPPP ports cannot be part of a protection group.
However, some redundancy is inherent in the MLPPP protocol, because if one of
the bonded links is out-of-service, the result is only a reduction in the available
transmission bandwidth.
Standards
The MLPPP ports conform to the IETF RFC 1990 standard.
Factory Defaults
Megaplex-4100 is supplied with all MLPPP ports disabled. The MTU default value is
250.
5-106
MLPPP Ports
Configuring MLPPP Ports
To configure an MLPPP port (bundle):

1. Navigate to configure port mlppp <slot>/<port> to select the MLPPP port
(bundle) to configure.
The config>port>mlppp>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short description to the

port
name <string>
Administratively enabling the port
no shutdown
Using shutdown disables the bundle
Binding the PPP port to the MLPPP

port
bind ppp <slot>/<port>
Selecting the MTU (maximum

transmission unit) for fragmented
packet
mtu <value in bytes>
Slot: 1 to 10, Port: 1 to 8

Using no bind ppp<slot>/<port>
removes the binding
The supported range is 80 to 1600
bytes.
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
To map E1 port 1 to Ethernet Port 2:
Bind corresponding E1 streams to each PPP port
Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
Configure Logical Mac port 5/1 and bind to it the MLPPP port
Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.
MLPPP Ports
5-107
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
configure
configure
configure
configure
configure
configure
configure
configure
port
port
port
port
port
port
port
port
ppp
ppp
ppp
ppp
ppp
ppp
ppp
ppp
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
exit all
configure
configure
configure
configure
configure
configure
configure
configure
configure
port
port
port
port
port
port
port
port
port
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
bind
bind
bind
bind
bind
bind
bind
bind
5/1
5/1
5/1
5/1
5/1
5/1
5/1
5/1
5/1
e1
e1
e1
e1
e1
e1
e1
e1
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
no shutdown
bind ppp 5/1
bind ppp 5/2
bind ppp 5/3
bind ppp 5/4
bind ppp 5/5
bind ppp 5/6
bind ppp 5/7
bind ppp 5/8

mp4100# configure flows classifier-profile unw match-any match
all
mp4100>config>flows>flow(01)$ classifier unw
mp4100>config>flows>flow(01)$ egress-port eth 5/2
mp4100>config>flows>flow(01)$ ingress-port logical-mac 5/1
mp4100>config>flows>flow(01)$ commit
mp4100>config>flows>flow(01)$ no shutdown
mp4100>config>flows>flow(02)$
classifier unw
egress-port logical-mac 5/1
ingress-port eth 5/2
commit
no shutdown
5.15 PPP Ports

PPP is the intermediate layer between the MLPPP and the physical (E1) layer.
Dividing the Ethernet traffic between several PPP ports grouped by a single
MLPPP entity provides increased bandwidth over several physical connections.
Standards
The PPP ports conform to the IETF RFC 1990 standard.
5-108
PPP Ports
Factory Defaults
Megaplex-4100 is supplied with all PPP ports disabled.
Configuring PPP Ports
To configure a PPP port:

1. Navigate to configure port ppp <slot>/<port> to select the PPP port to
configure.
The config>port>ppp>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
name <string>
no shutdown
Binding the PPP port (logical entity) to

the E1 physical port of a M8E1/M8SL
module
bind e1 <slot>/<port>
Slot: 1 to 10; Port: 1 to 8

Using no bind e1 <slot>/<port>
removes the binding
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
Note
To map E1 port 1 to Ethernet Port 2:
Bind corresponding E1 streams to each PPP port
Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
Configure Logical Mac port 5/1 and bind to it the MLPPP port
Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.
The PPP ports are administratively enabled by default so there is no need for the
no shutdown command.
PPP Ports
5-109
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
configure
configure
configure
configure
configure
configure
configure
configure
port
port
port
port
port
port
port
port
ppp
ppp
ppp
ppp
ppp
ppp
ppp
ppp
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
exit all
configure
configure
configure
configure
configure
configure
configure
configure
configure
port
port
port
port
port
port
port
port
port
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
mlppp
bind
bind
bind
bind
bind
bind
bind
bind
5/1
5/1
5/1
5/1
5/1
5/1
5/1
5/1
5/1
e1
e1
e1
e1
e1
e1
e1
e1
5/1
5/2
5/3
5/4
5/5
5/6
5/7
5/8
no shutdown
bind ppp 5/1
bind ppp 5/2
bind ppp 5/3
bind ppp 5/4
bind ppp 5/5
bind ppp 5/6
bind ppp 5/7
bind ppp 5/8

mp4100# configure flows classifier-profile unw match-any match
all
mp4100>config>flows>flow(01)$ classifier unw
mp4100>config>flows>flow(01)$ egress-port eth 5/2
mp4100>config>flows>flow(01)$ ingress-port logical-mac 5/1
mp4100>config>flows>flow(01)$ commit
classifier unw
egress-port logical-mac 5/1
commit
no shutdown
5.16 Voice Ports

Voice ports are available on the VC-4, VC-8 and VC-16, VC-4A, VC-8A and
VC-4/OMNI I/O modules. The following table shows the number of voice ports on
each Megaplex-4100 I/O module.
5-110
Voice Ports
Table 5-29. Megaplex-4100 Voice Ports

Module
Number of Ports
VC-4/OMNI
VC-4A/8A
4/8
VC-4/8/16
4/8/16
Analog voice interface modules, VC-4, VC-8 and VC-16, provide 4, 8 or 16

PCM-encoded toll-quality voice channels (ports). The modules are available in
three models:
E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464 Types I, II, III
and V, and BT SSDC5.
FXS: 2-wire interfaces for direct connection to telephone sets.
FXO: 2-wire interfaces for direct connection to PBX extension lines
VC-4A and VC-8A modules are analog voice interface module similar to VC-4 and
VC-8, except that they also support ADPCM.
A special omnibus VC-4/OMNI module provides four toll-quality voice channels
for applications where a master site needs to communicate with multiple remote
stations simultaneously (such as to broadcast an important message).
The following parameters can be configured for the voice ports:
Port name
Administrative status
End-to-end signaling transfer method
Pulse metering frequency for FXO/FXS channels
Number of wires for E&M channels
Specifying the compression method used in the ADPCM encoding.
Analog signaling method for FXO/FXS channels
E&M signaling standard
Enabling the built-in adaptive echo canceller
Operating mode of the channel
Nominal input level of the transmit and receive path.
Standards
The Megaplex-4100 voice ports comply with following standards:
Modulation Technique
PCM: per ITU-T Rec. G.711 and AT&T Pub. 43801

ADPCM: per ITU-T G.726 and G.727
Echo Cancellation
ITU-T G.168
Analog Interface
ITU-T Rec. G.712
Voice Ports
5-111
E&M Signaling Method
EIA RS-464 Type I

EIA RS-464 Type II, III and V (British Telecom
SSDC5) using internal -12 VDC in place of -48 VDC
FXS/FXO Signaling Modes EIA RS-464 loop-start and wink-start

End-to-End Signaling for
E1 Uplinks
User-selectable as per ITU-T Rec. G.704, para. 3.3.32
All the VC modules provide high-quality voice channels. The functional difference
between the various modules is in the signaling interface and mode. The analog
interface for the E&M modules is user-selectable for 2-wire or 4-wire; for the
other versions, a 2-wire interface is always used.
Voice encoding method for all VC-4A and VC-8A module versions is
user-selectable for either toll-quality 64 kbps PCM or 32/24 kbps ADPCM. The
VC-4, VC-8 and VC-16 modules feature only PCM encoding.
The user can select the companding law, -law or A-law, in accordance with
system requirements. In accordance with ITU-T Rec. G.711, the A-law should be
used on E1 trunks and the -law should be used on T1 trunks. However, the user
can select the desired companding law, -law or A-law, in accordance with the
specific system requirements.
To increase application flexibility, the nominal audio transmit and receive levels of
all the module versions can be adjusted over a wide range (see Table 5-30).
Table 5-30. Transmit and Receive Levels for Various Interfaces

Module Interface
Transmit
[dbm]
min
Receive
[dbm]
max
min
max
E&M regular
-10
+5
-17
+2
E&M 4W enhanced
-17
+5
-17
+9
FXS
-5
+5
-17
+1
FXO
-3.5
+5
-17
+1
Due to the high quality audio reproduction, DTMF signaling is transparently

transferred, inband. Therefore, the user can use DTMF signaling as usual, e.g.,
can operate the telephone set keypad to access voice mail systems, interactive
systems, etc.
The VC-4A and VC-8A modules use G.168 standard for echo cancellation (up to
4 ms per channel).
For more information, see also the VC-4/VC-4A/VC-8/VC-8A/VC-16 and VC-4/OMNI
sections in Appendix B.
5-112
Voice Ports
Factory Defaults
Megaplex-4100 is supplied with all voice ports disabled. Other parameter defaults
are listed in the table below.
Parameter
Default Value
coding
a-law
signaling
no signaling (disabled)
meter-rate
12khz
wires
compression
no compression (disabled)
analog-signaling
loop-start
e-m-type
ssdc5
echo-canceler
no echo-canceler (disabled)
operation-mode
ptp
signaling-feedback
no signaling-feedback (disabled)
tx-gain
0 dbm
rx-sensitivity
0 dbm
duration
infinite
omni-signaling
legacy
Configuring External Voice Port Parameters
To configure the external voice port parameters:

1. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specifying the
companding law to be
used by the voice
channels
coding {a-law | u-law}
a-law - A-law coding, intended for use on

E1 links
u-law --law coding, intended for use on T1

links
Voice Ports
5-113
Task
Command
Comments
Specifying the
end-to-end signaling
transfer method for voice
modules
signaling {rbmf | cas | rbf}
The signaling transfer options depend on

the type of link module installed in the
Megaplex chassis:
with T1 link modules, RBMF and RBF is

used
with E1 link modules, CAS and RBF is

used
Using no signaling means that channel

signaling is not transferred
RBF is a proprietary robbed bit signaling
method that does not require multiframe
synchronization, used as follows:
7-bit PCM with channel signaling carried

by the 8th bit of each channel
3-bit ADPCM with channel signaling

carried by the 4th bit of each channel
when using G.727
This option is used for VC-4A/VC-8A

modules only.
Specifying the
transfer method for
VC-4/OMNI modules
omni-signaling {legacy | abcd}
Using no omni-signaling means that channel

signaling is not transferred
Specifying the pulse

metering frequency
meter-rate { 16khz | 12khz }
This feature is supported only on FXS and

FXO modules in PCM mode
Specifying the interface

to be used by the voice
channels
wires {2 | 4}
Selection between 2-wire and 4-wire

interface is available only for the VC-4/8/16
E&M modules. Can be independently
selected for each pair of channels (1, 2; 3,
4; etc.).
Specifying the
compression method
used in the ADPCM
encoding
compression {g726 | g727}
Always use G.727 when working with RBF or

RBMF signaling.
If PCM encoding is used, a sanity error is
sent.
Using no compression disables compression
Specifying the analog

signaling method used
for all FXO/FXS channels
5-114
Voice Ports
analog-signaling {loop-start | wink-start}
Can be selected only for FXO and FXS

modules operated in PCM mode.
For VC-4, VC-4A, VC-8 and VC-8A modules,
the selection is made for the entire group
of all the module channels. For VC-16
modules, the selection can be separately
made for each group of eight channels: 1 to
8 and 9 to 16.
Task
Command
Comments
Specifying the E&M

signaling standard
e-m-type {1 | 2 | 3 | ssdc5}
This selection is available only for E&M

modules. The E&M signaling type can be
independently selected for each group of
four channels 1, 2, 3, 4; 5, 6, 7, 8; etc.).
Note: For the E&M/POS module, select 2

only.
Enabling the built-in
adaptive echo canceller,
supporting up to a 4
msec delay
echo-canceler
This option is relevant only for VC-4A and

VC-8A modules.
Setting the operating

mode of the channel for
VC-4/OMNI modules
operation-mode {ptp | omni-bus |

p2mp-dst | p2mp-src}
This parameter is valid only for

VC-4/OMNI modules.
Controls the use of

signaling feedback for
FXO modules
signaling-feedback
Available only for FXO modules.
Using no before echo-canceler disables

echo canceling
For VC-4, VC-4A, VC-8 and VC-8A, the

selection should be the same for all the
module channels. For VC-16 modules, the
selection can be separately made for each
group of eight channels: 1 to 8 and 9 to 16.
This is done by forcing the last choice
(signaling-feedback/no signaling-feedback)
to all the module/group ports.
Using no before signaling-feedback disables
the signaling feedback.
Selecting the nominal

input level of the
transmit path
tx-gain <value in dbm>
The input level can be set in 0.5 dB steps in

the range of +5 dBm to -17 dBm, depending
on the module type (see Table 5-30).
Selects the nominal input

level of the receive path
rx-sensitivity <value in dbm>
The input level can be set in 0.5 dB steps in

the range of +9 dBm to -17 dBm, depending
on the module type (see Table 5-30).
Example
The following section illustrates how to configure the voice FXS port 1 on the
VC-8 module installed in slot 9:
Set --law coding
Set CAS signaling
Administratively enable the port
Voice Ports
5-115
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
#----------vc8fxs----------------port voice 9/1 no shutdown

port voice 9/1 coding u-law
port voice 9/1 signaling cas
Configuring Internal Voice Port Parameters
To configure the internal voice port parameters (VC-4/OMNI only):

1. Navigate to configure port voice <slot>/<port>/<tributary> to select the
internal voice port to configure.
The config>port>voice>(<slot>/<port>/<tributary>)# prompt is displayed.
Task
Command
Comments
name <string>
no shutdown
Specifying the end-to-end signaling

transfer method for VC-4/OMNI
modules
omni-signaling {legacy | abcd}
Using no before omni-signaling means that

channel signaling is not transferred
Testing Voice Ports

The test and diagnostics functions available on each voice channel are:
Local digital loopback
Remote digital loopback
Forward tone injection
Backward tone injection.
Local Digital Loopback (Local Loop)

The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
While the loopback is connected, the local voice channel should receive its own
signal, e.g., a strong sidetone should be heard in the earpiece if the channel is
connected to a telephone set.
The loopback signal path is shown in Figure 5-8.
5-116
Voice Ports
Channel 1
User or
Test
Equipment
..
...
.
..
..
.
..
..
.
..
..
.
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-8. Local Loopback, Signal Path

Note
When working in the ADPCM mode, the local digital loopback towards the local
user equipment is performed for each pair of consecutive channels (1-2, 3-4,
etc.)
Remote Digital Loopback (Remote Loop)

The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote voice channel should receive its own
The loopback signal path is shown in Figure 5-9.
Voice Ports
5-117
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-9. Remote Loopback, Signal Path
Forward Tone Injection

The test tone is a data sequence repeating at a rate of 1 kHz. This data sequence
is identical to the data sequence that would have been generated if a 1-kHz
signal having a nominal level of 1 mW (0 dBm0) were applied to the input of the
channel codec.
The tone is injected to the local transmit path multiplexer, instead of the transmit
signal of the channel. The signal received from the other end remains connected
to the local subscriber.
While the forward tone injection is activated, the remote user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 5-10 shows the signal path.
5-118
Voice Ports
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
Test
~ Tone
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-10. Forward Test Tone Injection Path
Backward Tone Injection

When the backward test tone injection is enabled, the test tone (a data sequence
repeating at a rate of 1 kHz) is injected to the local receive input of the channel
decoder, instead of the received signal of the channel, and the resulting analog
signal is supplied to the local subscriber. The signal received from the other end is
disconnected from the local subscriber.
While the backward tone injection is activated, the local user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 5-11 shows the signal path.
Voice Ports
5-119
..
..
.
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
Test
Tone
VC-16
VC-16
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-11. Backward Test Tone Injection Path
Loopback Duration
After the selected interval expires, the loopback is automatically deactivated,
Activating Loopbacks and Tone-Inject Tests
To perform a loopback on the voice port:

1. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
5-120
Voice Ports
Task
Command
Comments
Activating and
configuring the
direction of the
loopback and the
duration of it (in
seconds)
loopback {local | remote} [tone-inject]

[duration <duration in minutes 1..30> ]
no loopback

local tone-inject backward tone
injection
remote tone-inject forward tone
injection
Viewing a Voice Port Status

Follow the instructions below for viewing the status of a voice port.
To view the voice port status:
At the config>port>voice(<slot>/<port>/<tributary>)# prompt, enter show

status.
Note
<tributary> relates to VC-4/OMNI modules only.

mp4100>config>port>voice(3/1)# show status
Name
: IO-3 voice 01
Administrative Status
: Up
Operation Status
: Up
Loopback Type
: None
5.17 Serial Ports

The following table shows the type and number of serial ports available on each
Megaplex-4100 serial I/O module.
Table 5-31. Megaplex-4100 Serial Ports

Module
Type of Module
Number of Ports
HS-6N, HS-12N
n x 64 kbps high speed
6/12
HSU-6, HSU-12
ISDN U
6/12
HS-S
ISDN S
HS-703
Codirectional data
HS-RN
sub-DSO low speed
HSF-2
fiber optic teleprotection
LS-6N, LS-12
low speed
6/12
The following parameters can be configured for the serial ports:
Serial Ports
5-121
Port name
Clock mode
Port data rate
Size of the FIFO buffer used by the channel
Port transmission mode
Setting CTS line to track the state of the local RTS line
Selecting the number of data bits/ stop bits and controlling the
end-to-end transfer of the parity bit in the asynchronous word format
Selecting other parameters for specific kind of modules.
Table 5-32 summarizes the features available for serial ports of different I/O
modules. To configure a specific module, select its supported parameters in
Table 5-32 and then refer to Configuring Serial Port Parameters for configuration
instructions. In addition, consult the corresponding module section in Appendix B
for specific configuration considerations.
Table 5-32. Features Supported by Megaplex-4100 Serial Ports

Feature/Command
HS-RN
HS-6N/12N
HS-S
HS-U-6/12
HS-U-6/12
I Mode
1 Mode
LS-6N, LS-12
HSF-2
Number of ports
6/12
6/12
6/12
6/12
Additional ports
bri
bri
serial-bundle
(for serial ports)
name
shutdown
clock-mode
cts-rts
rate
fifo-size
mode
encapsulation-mode
end-to-end-control
data-bits
parity
stop-bits
rate-adaptive
interface
activation-type
Split TS cross-connect
5-122
Serial Ports
Standards
The Megaplex-4100 serial ports comply with following standards:
HS-703: ITU-T G.703, Codirectional interface
LS-6N/LS-12 channel interface: ITU-T Rec. V.24/EIA RS-232, user-selectable

DCE or DTE
LS-6N/LS-12 async-to-sync conversion method compatible with ITU-T Rec.

V.14
HS-RN channel interface: ITU-T Rec. V.24/V.28, EIA RS-232
HS-RN HDLC protocol based or ITU-T Rec. V.110
HSF-2: IEEE PC37.94 standard draft
See corresponding section in Appendix B for each module.
Factory Defaults
Megaplex-4100 is supplied with all serial ports disabled. Other parameter defaults
Parameter
clock-mode
Default Value
dce
HSF-2: 1x64
HSU-6/12: 1.2
rate
HS-RN: 0.6
LS-6N/LS-12: 9.6
HS-6N/12N: T1: 1 x 56kbps, E1: 1 x 64kbps
fifo-size
auto
mode
sync
encapsulation-mode
bandwidth
cts-rts
no cts-rts (disabled)
end-to-end-control
no end-to-end-control (disabled)
data-bits
8 (HSU-6/12 modules:7)
parity
no parity (disabled)
stop-bits
rate-adaptive
proprietary
interface
nt
activation-type
Serial Ports
5-123
Configuring Serial Port Parameters
To configure the serial port parameters:

1. Navigate to configure port serial <slot>/<port> to select the voice port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short description

to port
name <string>
port
no shutdown
Configuring the clock mode

in synchronous mode
HS-RN, HSU-6/12 (lt1 mode

only): clock-mode
{dce|external-dce}
dce The port provides transmit and

receive clocks to the DTE
external-dce The port provides the

receive clock to the DTE, and accepts the
transmit clock from the DTE
dte The channel interface requires

transmit and receive clock signals from
the users equipment
HS-6N/12N, LS-6N/LS-12:
clock-mode {dce | externaldce | dte }
In modules with sync/async operation this

selection is relevant only for synchronous
mode
Setting the data rate of this
port in kbps. The selection
depends on the module
type.
HS-6N/12N: rate {1 | 2 | 3 | 4 |
5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 14 | 15 | 16 | 17 | 18 | 19
| 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31} x
{56kbps | 64kbps}
The allowed range is n56 kbps or n64 kbps,

where n is 1 through 24 for a T1 link, and 1
through 31 for an E1 link.
In HS-6N/12N modules with V.24/RS-232
interface, the data rate for all channels is
64 kbps only.
HSF-2: rate {1x64 | 2x64 |

3x64 | 4x64 | 5x64 | 6x64 |
7x64 | 8x64 | 9x64 | 10x64}
HSU-6/12 (lt1 mode only):
rate {1.2 | 2.4 | 4.8 | 9.6 | 16 |
19.2 | 32 | 38.4 | 48 | 56 |
57.6 | 64 | 115.2 | 128}
5-124
Serial Ports
The available data rates depend on the port

transmission mode:
Synchronous mode: 1.2, 2.4, 4.8, 9.6, 16,

19.2, 32, 38.4, 48, 56 (supported only
when connected to an ASMi-31 using
V.110 rate adaptation), 64 or 128 kbps.
Asynchronous mode: 1.2, 2.4, 4.8, 9.6,

19.2, 38.4, 48, 57.6 or 115.2 kbps.

Task
Command
Comments
HS-RN: rate {0.6 | 1.2 | 2.4 |

4.8 | 7.2 | 9.6 | 14.4 | 19.2 |
28.8 | 38.4 | 48 | 56 | 64}
The supported range is as follows:

ASYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
14.4*, 19.2, 28.8*, or 38.4 kbps.
SYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
14.4*, 19.2, 28.8*, 38.4, 56, or 64 kbps.
The rates marked by an asterisk (*) are
supported only by the HDLC-based model
When the encapsulation-mode=latency, only
rates up to 19.2 kbps are supported, and the
required uplink bandwidth is always one full
timeslot. In sync mode, also 56 kbps and
64 kbps are supported.
LS-6N/LS-12: rate {2.4 | 4.8 |

7.2 | 8 | 9.6 | 14.4 | 16 | 19.2 |
24 | 28.8 | 32 | 38.4 | 48 | 56 |
57.6 | 64}
Determines the channel data rate, in kbps.

Group 1: 2.4, 4.8, 9.6, 19.2, 38.4
Group 2: 7.2, 14.4, 28.8, 57.6
Group 3: 8.0, 16.0, 24.0, 32.0, 48.0, 56.0,
64.0
Note: Both channels of a given pair must

operate at rates belonging to the same group.
Group 3 rates can be selected only on
channels using the synchronous protocol.
Selecting the size of the
FIFO buffer used by the
channel
fifo-size {auto | 16bit | 30bit |

52bit | 72bit}
In general, you should select auto. The

automatically selected value depends on the
channel data rate:
16 bits for 64 kbps
30 bits for 128 and 192 kbps
52 bits for 256 through 320 kbps
16 bits for 1984 kbps.
For special applications that require longer

buffers, you may want to manually select one
of the supported FIFO sizes (16 bits, 30
bits, 52 bits, or 72 bits)
Selecting the port
transmission mode (HS-RN,
HSU-6/12, LS-6N/LS-12)
mode {sync | async}
Selecting the encapsulation

mode for the HS-RN module
(using HDLC-based rate
adaptation)
encapsulation-mode {latency |
bandwidth}
In the HS-RN/V.110 module version the only

possible selection is bandwidth.
All the HS-RN ports use the same
encapsulation mode (as determined by the
last selection).
Serial Ports
5-125
Task
Command
Comments
Setting CTS line to track the

state of the local RTS line
cts-rts
HS-RN, HS-6N/12N, LS-6N/LS-12 modules

only
Using no cts-rts sets the CTS line continously
to on.
Configuring end-to-end
control (HS-RN, HSU-6/12,
lt1 mode)
end-to-end-control
When configured, the state of the local RTS

and DTR lines are reflected by the remote
DCD and DSR line, respectively. For HS-RN, do
not use this selection for data rates
exceeding 38.4 kbps.
Using no end-to-end-control disables end-toend control. For HS-RN, always use this
selection for data rates exceeding 38.4 kbps.
Configuring end-to-end
control (LS-6N/LS-12)
end-to-end-control {rts | rtsdtr}
rts the state of the local RTS line is

reflected by the remote DCD line
rts-dtr the state of the local RTS and DTR
lines are reflected by the remote DCD and
DSR line, respectively
Using no end-to-end-control disables end-toend control (only local support is enabled)
Both channels of a given pair must be
assigned to support the matching control
signals.
Selecting the number of

data bits in the
asynchronous word format
HS-RN, HSU-6/12, HS-S:

data-bits {5 | 6 | 7 | 8}
LS-6N/LS-12: data-bits {6 | 7 |
8 | 9}
Controlling the
end-to-end transfer of the
parity bit in the
HS-RN: parity
Selecting the number of

stop bits in the
(HS-RN, HSU-6/12, lt1 mode
only)
stop-bits {1 | 2}
Selecting the multiplexing

and rate adaptation method
supported by the
corresponding HS-U-6/12
port (lt1 mode only)
rate-adaptive {proprietary |
v110}
5-126
Serial Ports
HSU-6/12 (lt1 mode only),

HS-S: parity {odd | even}
HSU-6/12: 5 or 6 data bits are supported only

when the remote equipment is an ASMi-31
using V.110 rate adaptation.
LS-6N/12: The number is equal to the total
number of data and parity bits
Using no parity means that the parity bit is
not transferred
LS-6N/12: Parity is transparently transferred
proprietary RAD proprietary method

based on ITU-T Rec. I.460
v110 Multiplexing and rate adaptation in

accordance with ITU-T Rec. V.110
Task
Command
Comments
Selecting the function and

mode of the HS-U-6/12/
HS-S external port
interface {lt | nt | te | lt1}
Selections for HS-U-6/12 are:
nt port operates as a network

termination unit in the I mode.
lt port operates as a line termination

unit in the I mode.
lt1 port operates as a line termination

unit in the 1 mode (used for connection
to NT equipment, such as ASMi-31).
Selections for HS-S are:
Selects the ISDN activation

mode of an HS-U-6/12 port
configured for operation in
the nt mode
te terminal mode.
nt network termination mode.
activation-type {1 | 2 | 3}
Example
The following section illustrates how to configure serial port 1 on the HS-6N
module installed in slot 5:
Data rate 128 kbps.
Set CTS line to track the state of the local RTS line
mp4100>config>port>serial(5/1)# rate 2 x 64
mp4100>config>port>serial(5/1)# cts-rts
mp4100>config>port>serial(5/1)# no shutdown
Testing Serial Ports

The following test and diagnostics functions available on each serial port:
Some additional tests and loopbacks are available for HS-U-6/12 modules working
in 1 Mode in conjuction with remote ASMi-31 modems. For their description,
see HS-U-6 and HS-U-12 Modules section in Appendix B.
Local Digital Loopback (Local Loop)

The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
Serial Ports
5-127
While the loopback is connected, the local voice channel should receive its own
The loopback signal path is shown below.
Channel 1
User or
Test
Equipment
..
...
.
..
..
.
..
..
.
..
..
.
HS-703
HS-703
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-12. Local Loopback, Signal Path
Remote Digital Loopback (Remote Loop)

The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote voice channel should receive its own
The loopback signal path is shown below.
5-128
Serial Ports
Channel 1
User or
Test
Equipment
..
..
..
.
..
..
.
..
..
.
..
..
.
HS-703 C
HS-703
I/O Modules
I/O Modules
Local
Unit
User or
Test
Equipment
Remote
Unit
System
Management
Figure 5-13. Remote Loopback, Signal Path
Loopback Duration
Activating the Loopbacks
To perform a loopback on the serial port:

1. Navigate to configure port serial <slot>/<port> to select the serial port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.
Serial Ports
5-129
Task
Command
Comments

direction of the loopback
local. Returns the transmitted data

at the physical layer to the receiving
path. The local physical loopback
includes a configurable timeout
mechanism that ends the loopback
operation after a user-defined
duration.
remote. Returns the received data

at the physical layer to the
transmitting path.
Using no loopback stops the loopback.
5.18 BRI Ports

The following table shows the number of BRI ports on the HSU-6, HSU-12 and
HS-S I/O modules.
Table 5-33. BRI Ports

Module
Type of Module
Number of Ports
HSU-6, HSU-12
ISDN U
6/12
HS-S
ISDN S
The following parameters can be configured for the BRI ports:
Port name
Number of bits that must be allocated to each internal port (B-channel)
Standards
The BRI ports comply with the ANSI T1.601 and ITU-T Rec. G.961 standards.
See the corresponding module section in Appendix B.
Factory Defaults
Megaplex-4100 is supplied with all BRI ports disabled. Other parameter defaults
Parameter
rate-bits
5-130
BRI Ports
Default Value
2
Configuring BRI (ISDN) Port Parameters
To configure the BRI port parameters:

1. Navigate to configure port bri <slot>/<port>[tributary] to select the BRI port
to configure:
To configure Channel B1, use configure port bri <slot>/<port>/1
To configure Channel B2, use configure port bri <slot>/<port>/2
To configure Channel D, use configure port bri <slot>/<port>

The config>port>bri>(<slot>/<port>/[tributary>]# prompt is displayed.

Task
Command
Comments

to port
name <string>
port
no shutdown
Specifying the number of

bits that must be allocated
to each internal port
(B-channel), in accordance
with the payload data rate
rate-bits {2 | 4 | 8}
The data rates supported by each

B-channel are as follows:
2
Used for payload data rates up to 16

kbps.

kbps.

kbps.
For the D-Channel rate-bits is constantly

set to 2 (16 kbps).
Example
The following section illustrates how to configure the bri ports 3 and 4 (B1, B2
and D-channels) on the HS-U-6 module installed in slot 5:
Data rate 8 kbps on each B-channel (total 32 kbps).
Data rate 2 kbps on each D-channel (total 4 kbps).
Administratively enable the ports.
BRI Ports
5-131
------------hs-U6---------------mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
port
port
port
port
bri
bri
bri
bri
5/3/1 no shutdown
5/3/1 rate-bits 8
5/3/2 no shutdown
5/3/2 rate-bits 8
port
port
port
port
bri
bri
bri
bri
5/4/1
5/4/1
5/4/2
5/4/2
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
#------------d-channel-----port bri 5/3 no shutdown

port bri 5/3 rate-bits 2
port bri 5/4
port bri 5/4
no shutdown
rate-bits 8
no shutdown
rate-bits 8
no shutdown
rate-bits 2
5.19 Serial Bundle Ports

The serial bundle ports are available only on LS-6N, LS-12 modules. The following
parameters can be configured for the serial bundle ports:
Port name
Setting the port data rate.
See the LS-6N, LS-12 Modules section in Appendix B.
Factory Defaults
Megaplex-4100 is supplied with all serial bundle ports disabled. Other parameter
Parameter
rate
Default Value
64kbps
Configuring Serial Bundle Port Parameters
To configure the serial bundle port parameters:

1. Navigate to configure port serial-bundle <slot>/<port> to select the port to
configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.
5-132
Serial Bundle Ports
Task
Command
Comments

to port
name <string>
port
no shutdown
Specifying the bandwidth

allocated to the
corresponding composite
channel on the Megaplex
uplink
rate {14.4kbps | 32kbps | 56kbps |

64kbps | 128kbps | 192kbps | 256kbps |
384kbps | 512kbps | 768kbps}
Binding external serial ports

that will be carried over this
serial bundle port
(composite channel)
bind serial <slot>
To remove the binding, you must bind this

serial-bundle port to another serial port
Example
The following section illustrates how to configure the serial bundle (internal) port
1 on the LS-12 module installed in slot 6:
Data rate 32 kbps.
Bind external serial ports 1 and 2 to be carried over this serial bundle port
mp4100>config# port serial-bundle 6/1

mp4100>config>port>serial-bundle(6/1)#
mp4100>config>port# exit
no shutdown
bind serial 1
bind serial 2
rate 32
exit
Testing Serial-Bundle Ports

The LS-6N and LS-12 modules feature the test loopbacks on each composite data
stream (serial-bundle port). The test and diagnostics functions available on each
serial-bundle port are:
Composite Data Stream Local Digital Loopback

When a local loop is activated on the Megaplex-4100 composite data stream, the
module composite transmit signal is returned to its receive path. As a result, each
individual channel receives its own signal.
Serial Bundle Ports
5-133
The composite transmit signal is still connected to the transmit path and reaches
the LS-6N/12 module installed in the remote Megaplex unit, therefore the remote
equipment does not lose synchronization.
While the loop is connected, all the local users connected to the module must
receive their own signals, and the S.LOSS indicators of the local module must be
off. This loopback provides a quick operational check of the local module. The
loopback signal path is shown in Figure 5-14.
Composite Data Stream Remote Digital Loopback

When a remote composite data stream loopback is activated, the LS-6N/12
module loops back the receive signal toward the remote equipment. The received
signal remains connected as usual to the receive path of the local module, and
therefore the local S.LOSS indicates must be off. The loopback signal path is
shown in Figure 5-15.
While the loop is connected, and the link to the remote equipment operates
normally, all the users connected to the remote module must receive their own
signals, and the S.LOSS indicators of the modules must be off.
This loop allows the user to perform a quick operational check of the end-to-end
transmission via this module.
Figure 5-14. Composite Local Loopback, Signal Path
Figure 5-15. Composite Remote Loopback, Signal Path
Loopback Duration
option to limit its duration to a selectable interval in the range of 1 through 30
minutes.
To perform a loopback on the serial-bundle port:

1. Navigate to configure port serial-bundle <slot>/<port> to select the serial
port to configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.
5-134
Serial Bundle Ports
Task
Command
Comments
Activating and
configuring the
direction of the
loopback
local. Returns the transmitted data

at the physical layer to the receiving
path. The local physical loopback
includes a configurable timeout
mechanism that ends the loopback
operation after a user-defined
duration.
remote. Returns the received data

at the physical layer to the
transmitting path.
no loopback
5.20 Mux-Eth-Tdm Ports (Fiber Optic Links of

Optimux Modules)
Mux-eth-tdm ports denote fiber optic links of Optimux modules.
Each Optimux module link has two optical ports, which can be operated as a
protection group, to enhance service availability to critical users. The service
provider can control each standalone unit through the link connecting the unit to
the Optimux module, and therefore can manage a large number of standalone
units from a central location.
OP-108C comprises two identical independently-operating sections, identified as
OP A and OP B, each of which is capable of multiplexing four independent internal
E1 data streams and up to 100 Mbps of Ethernet payload for transport over a
fiber-optic link. OP-34C has a single section capable of multiplexing 16
independent internal E1 data streams and up to 32 Mbps of Ethernet payload for
transport over a fiber-optic link.
In addition to its own OP modules, Megaplex-4100 can also operate with similar
modules initially designed for operation in the LRS-102 chassis. The difference
between the Megaplex and LRS modules is in the type of E1/T1 ports:
Megaplex modules have internal E1/T1 ports, and can be connected to other
ports within Megaplex-4100 via the chassis TDM buses
LRS modules have external E1/T1 ports which can be connected only to
external users, but cannot be connected to other ports within Megaplex-4100
via the chassis TDM buses.
In the CLI, LRS-102 modules are identified by -e1 at the end of the module
name: for example, the LRS-102 OP-108C (OP-108C/E1) module is identifiled as
op108c-e1.
The following table shows the number of mux-eth-tdm ports on Megaplex-4100
and LRS-102 I/O modules.
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
5-135
Table 5-34. Mux-Eth-Tdm Ports

Module
Number of Ports
OP-108C, OP-108C/E1
4:
OP-34C
2 for Section OP A (mux-eth-tdm 1 main,

mux-eth-tdm 2 redundant)
2 for Section OP B (mux-eth-tdm 3 main,

mux-eth-tdm 4 redundant)
2 (mux-eth-tdm 1 main, mux-eth-tdm 2 redundant)
Standards
Fiber optic links of Optimux modules are RAD proprietary technology.
The link interface subsystem of each Optimux module section includes a link
redundancy switch, and two independent link interfaces (one for each link port)
with SFP sockets.
The link redundancy switch operates as follows:
When only one SFP is installed, only one link port is active. The link
redundancy switch then connects the link mux/demux to this port.
When both SFP are installed, but redundancy is disabled, the link redundancy
switch connects the link mux/demux to the first port (LINK 1 or LINK 3 in OP108C, OP-108C/E1, LINK 1 in OP-34C).
When both SFP are installed, and redundancy is enabled, the link redundancy
switch connects the link mux/demux to the port selected as the primary port
of the corresponding link. When signal loss is detected by the primary port,
the switch transfers the traffic to the other (secondary) port.
Each link interface performs the following functions:
The transmit path converts the link data and the associated clock signal
provided by the link mux/demux to the signals needed to drive the SFP that
provides the physical interface of each port, for transmission to the far end
equipment.
The receive path recovers the link data stream received from the far end
equipment, and the associated clock, and provides the data and clock to the
link mux/demux.
The link interfaces accept a wide range of SFPs, and therefore the performance
depends on the installed SFP model. RAD offers a wide range of SFPs to meet a
wide range of system requirements. The fiber-optic interfaces can operate over
62.5/125 micron multi-mode, or 9/125 micron single-mode fibers (typical
attenuation of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm). The offered SFPs include models that need a single fiber instead of the
customary two fibers; for example, WDM models SF1 and SF2 operating at two
different wavelengths, or the SF3 model with SC/APC (angled polished connector)
that operates at a single wavelength.
5-136
Note
It is strongly recommended to order OP modules with RAD SFPs installed: this will
ensure that prior to shipping RAD has performed comprehensive functional
testing on the assembled module, including SFPs. Although users can install their
own SFPs into OP modules, RAD cannot guarantee full compliance to product
specifications when using non-RAD SFPs, and 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 SFPs that comply with the local
laser safety regulations for Class 1 laser products.
Table 5-35 provides information on the characteristics of the SFPs offered by
RAD, together with typical maximum ranges (calculated assuming typical fiber
attenuations of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm, and a 3-dB margin).
All the fiber-optic interface options offer high performance and have a wide
dynamic range, which ensures that the receiver will not saturate even when using
short fiber-optic cables. (Saturation is caused when the optical power applied to
the receiver exceeds its maximum allowed input power, and results in very high
bit error rates.)
Table 5-35. Link Port Interface Characteristics

Module Transmitter
Name
Type and
Wavelength
[nm]
Connector Fiber Type

Type
Typical
Output
Power
Receiver
Sensitivity
Typical Range
[dBm]
[km]
[miles]
[dBm]
SFP-1
LED, 1310
LC
62.5/125 Multimode
-18
-31
6.5
SFP-2
Laser, 1310
LC
9/125 Single mode
-12
-31
38
23.6
SFP-3
Long haul
laser, 1310
LC
9/125 Single mode
-2
-34
70
43.4
SFP-4
Long haul
laser, 1550
LC
9/125 Single mode
-2
-34
120
74.5
SFP-10a Laser WDM,

LC
Tx 1310, Rx
1550
9/125 Single mode

(single fiber)
-12
-30
40
24.8
SFP-10b Laser WDM,

LC
Tx 1550, Rx
1310
9/125 Single mode

(single fiber)
-12
-30
40
24.8
SFP-18A Tx 1310, Rx LC
1550
9/125 single mode

(single fiber)
-2
-30
60
37.3
SFP-18B Tx 1550, Rx LC
1310
9/125 single mode

(single fiber)
-2
-30
60
37.3
SFP-24
62.5/125 Multimode
-7
-31
6.5
VCSEL
LC
4.0
4.0
The OP-34C and OP-108C modules (MP-4100) and the OP-34C/E1 modules (LRS102) can be connected to remote standalone Optimux units, or to other modules
installed in the MP-4100 or LRS-102 chassis via fiber optic links.
5-137
Factory Defaults
Megaplex-4100 is supplied with all mux-eth-tdm ports disabled. The default
far-end-type value is no far-end-type.
Configuring Optical Link Parameters and Accessing the Remote Unit

Configuring the Local Optical Link
To configure the optical link parameters:

1. Navigate to configure port mux-eth-tdm <slot>/<port> to select the port to
configure.
Note

1 or 3 for OP-108C
1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively. To use links 2
and 4 as protection links they must be set manually to no shutdown.
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specify the type of far

end equipment
connected to this port
far-end-type {op-108 | op-108-eth | mplrs-card | op-34 | op-34-v35 | op-xle1 | op-xl-t1 | op-xl-e1-16 | other | op108l | op-108l-eth}
Assigning short
description to the remote
port connected to this
link
far-end-name <string>
Accessing
the remote device
connected to the uplink
See Table 5-36 for device definitions

and possible interconnections.
Using no far-end-type removes the
name
Using no far-end-name removes the

name
Once the remote device has been

accessed by this command, you can
activates loopbacks and configure
parameters of the remote device
remote
Table 5-36. Far End Devices

Local Device
Remote Device
Description
OP-108C, OP-108C/E1
no far-end-type
No far end equipment is connected
5-138

Local Device
For OP-34C
Remote Device
Description
op-108
Optimux-108 or Optimux-108L standalone unit without

Ethernet ports
op-108-eth
Optimux-108 or Optimux-108L standalone unit with

Ethernet ports
op-108l
Optimux-108L/BM standalone unit without Ethernet

ports
op-108l-eth
Optimux-108L/BM standalone unit with Ethernet ports
mp-lrs-card
OP-108C card installed in another Megaplex-4100 or

OP-108C/E1 card installed in an LRS-102 or in another
Megaplex-4100
other
Other type of equipment compatible with OP-108C.
no far-end-type
No far end equipment is connected
op-34
Optimux-34 standalone unit with 16 E1 ports and one

user Ethernet port with configurable throughput rate
op-xl-e1
Optimux-XLE1 standalone unit with 12 E1 ports and one

user Ethernet port providing a fixed throughput rate of
8 Mbps
op-xl-e1-16
Optimux-XLE1/16 standalone unit
op-34-v35
Optimux-34 standalone unit with 16 E1 ports, one V.35

port, and one user Ethernet port with configurable
Ethernet throughput rate
mp-lrs-card
OP-34C card installed in another Megaplex-4100
other
Other type of equipment compatible with OP-34C.
Configuring the Remote Optimux

To configure the remote Optimux ports, you must first access the remote unit.
To access the remote unit:

Note

1 or 3 for OP-108C
1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively, and cannot be
configured.
Type remote.
Now you are at the remote Optimux context and can configure the
followings ports:
5-139
Management Ethernet port
User Ethernet port
Optical link
E1/T1 ports.
To configure the remote Optimux management Ethernet port parameters:

1. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type
configure port mng-eth 1. (There is only one management Ethernet port on
any Optimux standalone device.)
To configure the remote Optimux user Ethernet port parameters:

configure port eth 1. (There is only one management Ethernet port on any
Optimux standalone device.)
Task
Command
Comments

port
name <string>
no shutdown
Enabling autonegotiation
auto-negotiation
Using no auto-negotiation disables

autonegotiation
Setting maximum advertised

capability (highest traffic
handling capability to be
advertised during the
autonegotiation process)
max-capability {100-full-duplex }

This parameter applies only if
autonegotiation is enabled and is
always 100-full-duplex. When
autonegotiation is disabled, this
parameter is replaced by speed-duplex.
This parameter is not relevant for the
Ethernet management port.
Setting data rate and duplex

mode of the Ethernet port,
when autonegotiation is
disabled
speed-duplex {10-full-duplex |
100-full-duplex |10-half-duplex
|100-half-duplex }

100-half-duplex 100baseT half
duplex.
When autonegotiation is enabled, this
parameter is replaced by max-capability.
Setting flow control for the

selected port (when operating
in the full duplex mode), or
back pressure (when operating
in the half-duplex mode)
5-140
flow-control
Using no flow-control disables flow

control
Task
Command
Comments
Activating/deactivating a
policer profile to set ingress
rate limitation (user port only)
policer-profile <name>
The policer profile for ingress rate

limitation is defined under Configuring
Policer Profiles.
Using no policer <name> deactivates
this policer profile
To configure the remote Optimux optical link parameters:

configure port mux-eth-tdm <port 1..2> to select the optical link of the
remote device to be tested.
Task
Command
Comments

to port
name <string>
port
no shutdown
To configure the remote Optimux E1 parameters:
Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type:

configure port e1 <port>.
Note

1 to 4 for each section for Optimux-108/108L
1 to 16 for Optimux-34.
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specifying port
impedance used by the
E1 port
interface-type {balanced | unbalanced}
Example
The following section illustrates how to configure the remote Optimux-108
connected to port 3 of local OP-108C module installed in slot 1:
Administratively enable the optical links, Ethernet port and all E1 ports.
Leave their parameters at their defaults.
5-141
configure port
configure port
configure port
configure port
configure port
configure port
configure port
configure port
exit-remote
exit all
mux-eth-tdm 1/3 remote

mux-eth-tdm 1 no shutdown
mux-eth-tdm 2 no shutdown
ethernet 1 no shutdown
e1 1 no shutdown
e1 2 no shutdown
e1 3 no shutdown
e1 4 no shutdown
Testing Optical Links

The test and diagnostics functions available on each optical link are:
Local loopback on local OP module link
Remote loopback on local OP module link
Local loopback on remote Optimux unit (OP module only, with limited
duration)
Remote loopback on remote Optimux unit
Local Loopback on Local Optical Link

A typical signal flow for a local loopback on the local OP module link is shown in
Figure 5-16. Note that AIS is sent to the link as shown in Figure 5-16 only when
the far end device configured for the tested section is a basic Optimux unit (with
E1 ports only); when the far end device includes an Ethernet port, a special
pattern is sent, and the Ethernet ports (both on the tested section of the local
OP module, and on the remote Optimux) are shut down for the duration of the
test.
Megaplex-4100
CL
OP-108C Section
or OP-34C
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Link
Mux/Demux
Uplink
Interface
Figure 5-16. Signal Flow for Link Local Loopback on Local OP Module
When a link local loopback is activated on an OP module, the link transmit signal
is returned to the input of the link receive path at a point just before the uplink
interface. The local link receive path will receive its own signal, and therefore
must operate normally.
In addition, user equipment connected via each E1 internal port served by the
corresponding link must also receive its own signal and thus it must be
synchronized.
5-142
This test checks the operation of the local OP link (section), and the connections
to the E1 equipment attached via local internal E1 ports.
Remote Loopback on Local Optical Link

A typical signal flow for a remote loopback on the local OP-108C link is shown in
the figure below.
Megaplex-4100
CL
Routing
Matrix
Other Port
Interface
OP-108C - OP-A Section
E1 Payload
Mux/Demux
Link
Mux/Demux
Uplink
Interface
Figure 5-17. Signal Flow for Link Remote Loopback on Local

OP Link
When a link remote loopback is activated on an OP module, the received link
signal is processed by the uplink interface, returned to the input of the link
transmit path at a point just before the uplink interface, and transmitted back to
the far end device. Therefore, the far end device receives its own TDM signal, and
its TDM paths must operate normally.
During the test, the local link receive path supplies AIS signals to each local
internal E1 port.
This test checks the connections between the user E1 equipment attached to the
E1 ports of the far end device, the operation of the far end device, the uplink
interface of the local OP module (module section), and the network connections
between the local OP module and the far end device.
Link Local Loopback on Remote Optimux

A typical signal flow for a local link loopback on the remote Optimux-108/108L is
shown in Figure 5-18. Note that AIS is sent to the link as shown in Figure 5-18
only when the far end device connected to the tested section is a basic Optimux
(with E1 ports only).
The link local loopback signal path on the remote Optimux is shown in
Figure 5-18.
5-143
Megaplex-4100
Local OP-108C Section
Remote Optimux
CL
LIU 1
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
.
..
.
.
.
..
E1/ Payload
Mux/Demux
"1"
E1
Port 1
LIU 4
(16)
E1
Port 4
(16)
Figure 5-18. Typical Signal Flow for Link Local Loopback on Remote Optimux
When a link local loopback is activated by an OP module command on the
connected Optimux, the Optimux link transmit signal is returned to the input of
its link receive path within the uplink interface. The Optimux link receive path will
receive its own signal, and therefore must operate normally.
In addition, user equipment connected to each OP module E1 port served by the
link must receive an AIS signal.
Ethernet traffic will not be disrupted while the loopback is activated.
This test checks the operation of the far end Optimux, and the connections to
the E1 equipment attached to the far end E1 ports.
This test is possible for OP-108C only with limited (not infinite) duration and not
available for OP-34C.
Link Remote Loopback on Remote Optimux

A typical signal flow for a link remote loopback is shown in Figure 5-19. Note that
AIS is applied only when the far end device connected to the tested section is a
basic Optimux (with E1 ports only). Ethernet traffic will not be disrupted while the
loopback is activated.
Remote Optimux
Megaplex-4100
CL
LIU 1
"1"
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux
Uplink
Interface
Uplink
Interface
E1 Payload
Mux/Demux
..
.
LIU 4
(16)
E1
Port 1
..
.
..
E1
Port 4
(16)
Figure 5-19. Typical Signal Flow for Link Remote Loopback on Remote Optimux
When a link remote loopback is activated on an Optimux, the received link signal
is processed by the uplink interface, returned to the input of the link transmit
path, and transmitted back to the local OP module. Therefore, the local OP
module receives its own TDM signal, and its TDM paths must operate normally.
In addition, user equipment connected via each local OP module internal E1 port
served by the corresponding link must also receive its own signal and thus it must
be synchronized.
5-144
This test checks the connections between the user E1 equipment attached to the
internal E1 ports of the local OP module, the operation of the local OP module,
the uplink interface of the far end device, and the network connections between
the local OP module and the far end device.
Loopback Duration
by the OP module. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
activated on the local module before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
To perform a loopback on the local optical link:

link to be tested.
Note

1 or 3 for OP-108C
1 for OP-34C
Loopbacks on protection ports 2 and 4 (of the same kind as on links 1 and 3) are
activated automatically, provided the protection links are at no shutdown.
2. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments


1..30> ]
no loopback
To perform a loopback on the remote optical link:

Note

1 or 3 for OP-108C
1 for OP-34C
Remote devices connected to protection ports 2 and 4 cannot be configured.
5-145

2. Type remote.
3. Navigate to configure port mux-eth-tdm <port 1..2> to select the optical link
of the remote device to be tested.
4. Enter all necessary commands according to the tasks listed below.
Task
Command
Comments


1..30> ]
local local loopback:
not available for OP-34C
for OP-108C available only when

the duration is not infinite

no loopback
Viewing Optical Link SFP Status Information

For viewing the status of the optical link SFP, follow the instructions below.
To view the status of a local optical link SFP:

1. Navigate to mux-eth-tdm (<slot>/<port>)#
Type show sfp-status.
The status is displayed, for example as follows:
mp4100>config>port>mux-eth-tdm(11/3)# show sfp-status
SFP
--------------------------------------------------------------Connector Type
: LC
Manufacturer Name
: WTD
: RTXM139-BG-RAD
Wave Length (nm)
: 1310
Fiber Type
: SM
SFP
--------------------------------------------------------------Current
Minimum
Maximum
RX Power (dBm)
: 0.0 dBm
TX Power (dBm)
: 0.0 dBm
Laser Bias (mA)
: 0.0 mA
Laser Temperature (Celsius) : 0.0 C
Power Supply (V)
: 3.3 V
The performance monitoring data for the OP module link physical layer includes
status data for each link port, and SFP data for the installed SFPs. Table 4-4
explains the parameters of the SFP installed for selected link port.
5-146
Table 4-4. Link SFP Parameters

Parameter
Description
Connector Type
Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name
Displays the original manufacturers name
Vendor PN
Displays the original vendors part number
Typical Max. Range

(Meter)
Displays the maximum range expected to be achieved over typical optical fibers, in
meters
Wave Length (nm)
Displays the nominal operating wavelength of the SFP, in nm
Fiber Type
Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm)
Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm)
Displays the current optical power, in dBm, received by the SFP
Laser Bias (mA)
Displays the measured laser bias current, in mA
Laser Temperature
(Celcius)
Displays the measured laser temperature, in C
Power Supply (V)
Displays the SFP power supply voltage
For displaying protection status, see Viewing the Status of an Ethernet Protection
Group section later in this chapter.
5.21 SDH/SONET Ports

Megaplex-4100 features four SDH/SONET ports (two ports located on each of the
two CL.2 modules). The ports can be ordered either with STM-1/OC-3 or
STM-4/OC-12 interfaces (see Ordering in Megaplex-4100 data sheet). The panels
and terminal identification for the STM-1/OC-3 and STM-4/OC-12 versions are
identical.
Standards
The SDH/SONET ports comply with the following standards:
SDH: ITU-T G.957, G.783, G.798
SONET: GR-253-core.
In particular, framing complies with the following:
SDH: ITU-T G.707, G.708, G.709
SONET: GR-253-core.
SDH/SONET Ports
5-147
SDH Implementation Principles
This section describes the implementation principles for the Synchronous Digital
Hierarchy (SDH), as a background for the detailed presentation of the SDH signal
structures. In the following explanations, the following terms are used to describe
SDH networks:
Network node. The SDH network node is a facility at which signals built in
accordance with the SDH frame structure are generated and/or terminated.
Therefore, a network node provides a convenient access point to add or drop
payload signals, e.g., PDH tributary signals, for transmission over the SDH
network.
SDH transport system. An SDH transport system provides the technical means
to transfer SDH signals between two network nodes.
SDH network. An SDH network is formed by interconnecting the required

number of network nodes by means of SDH transport systems.
The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two

principles:
1. Direct synchronous multiplexing of individual tributary signals within the
structure of the higher-rate multiplexed signal.
Transparent transporting of each individual tributary signal through the network,
without any disassembly except at the two network nodes that exchange
information through that particular signal.
To enable synchronous multiplexing, SDH equipment is designed to permit
efficient and reliable synchronization of the whole network to a single timing
reference.
Direct Multiplexing Approach

Direct multiplexing means that individual tributary signals can be inserted and
removed into the SDH multiplexed signal without intermediate multiplexing and
demultiplexing steps. This capability results in the following characteristics:
Efficient signal transport, as the same SDH transport system can carry various
types of payloads (tributary signals).
Flexible routing, because any tributary can be inserted and removed into the
SDH signal as a single unit, without affecting in any way the other tributary
signals carried by the same SDH signal. This permits the user to build
cost-effective add/drop multiplexers, the key component of flexible networks,
instead of implementing digital cross-connect systems as entities separated
from multiplexing equipment.
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore provides the network operator full
control over all the operational aspects of SDH networks and equipment units.
This overhead permits the integration of the network management and
maintenance functions within the transport network itself.
5-148
SDH/SONET Ports
General Structure of SDH Signals

The SDH signal is a serial signal stream with a frame structure. Figure 5-20 shows
the general structure of SDH signals.
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure. Each SDH frame starts with framing bytes, which enable
equipment receiving the SDH data stream to identify the beginning of each
frame. The location of the other bytes within this frame structure is determined
by its position relative to the framing byte.
The organization of the frame can be easily understood by representing the
frame structure as a rectangle comprising boxes arranged in N rows and M
columns, where each box carries one byte. In accordance with this
representation, the framing byte appears in the top left-hand box (the byte
located in row 1, column 1), which by convention is referred to as byte 1 of the
SDH frame.
N x M Bytes
Order of
Transmission
F B
B B
B
B
N x M Bytes
N Rows
1
2
Order of
Transmission
B B
B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure 5-20. General Structure of SDH Signals

The frame bytes are transmitted bit by bit, sequentially, starting with those in the
first row (see arrow in Figure 5-20). After the transmission of a row is completed,
the bits in the next lower row are transmitted. The order of transmission within
each row is from left to right. After transmission of the last byte in the frame
(the byte located in row N, column M), the whole sequence repeats - starting
with the framing byte of the following frame.
SDH Frame Organization

As shown in Figure 5-21, an SDH frame comprises two distinct parts:
Section Overhead (SOH)
Virtual Container (VC).
SDH/SONET Ports
5-149
N Rows
Section
Overhead
Path Overhead (One Column)
Virtual Container
(VC)
M Columns
Figure 5-21. SDH Frame Organization
Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type.
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
Virtual Container (VC)

The VC is an envelope (i.e., a special type of signal structure, or frame) that is
used to transport a tributary signal across the SDH network.
The path followed by a VC within the network may include any number of nodes,
therefore the VC may be transferred from one SDH transport system to another,
many times on its path through the network. Nevertheless, in most cases the VC
is assembled at the point of entry to the SDH network and disassembled only at
the point of exit.
Since the VC is handled as an envelope that is opened only at the path end
points, some of its signal carrying capacity is dedicated to path overhead. The
path overhead provides the facilities (e.g., alarm and performance monitoring),
required to support and maintain the transportation of the VC between the end
points.
VC Assembly/Disassembly Process
The concept of a tributary signal being inserted into a virtual container, to be
transported end-to-end across a SDH network, is fundamental to the operation
5-150
SDH/SONET Ports
of SDH networks. This process of inserting the tributary signal into the proper
locations of a VC is referred to as mapping.
In all the SDH signal structures, the carrying capacity provided for each individual
tributary signal is always slightly greater than that required by the tributary rate.
Thus, the mapping process must compensate for this difference. This is achieved
by adding stuffing bytes, e.g., path overhead bytes, to the signal stream as part
of the mapping process. This increases the bit rate of the composite signal to the
rate provided for tributary transport in the SDH structure.
At the point of exit from the SDH network, the tributary signal must be recovered
from the virtual container, by removing the path overhead and stuffing bits. This
process is referred to as demapping. After demapping, it is necessary to
restore the original data rate of the recovered tributary data stream.
STM-1 Frame Structure

Figure 5-22 shows the STM-1 frame structure.
2430 Bytes/Frame
155.52 Mbps
9 Rows
Section
Overhead
Path Overhead (9 Bytes)
Serial Signal
Stream
STM-1 Virtual Container (VC-4)
Container Capacity = 150.34 Mbps

Payload Capacity = 149.76 Mbps
9 Columns
260 Columns
1 Column
2430 Bytes/Frame x 8 Bits/Byte x 8000 Frames/sec = 155.52 Mbps
Figure 5-22. STM-1 Frame Structure

STM-1 frames are transmitted at a fixed rate of 8000 frames per second.
Note
At a transmission rate of 8000 frames per second, each byte supports a data rate
of 64 kbps.
The STM-1 signal frame comprises 9 rows by 270 columns, resulting in a total
signal capacity of 2430 bytes (19440 bits per frame). Considering the STM-1
frame repetition rate, 8000 frames per second, this yields a bit rate of
155.520 Mbps.
The STM-1 frame comprises the following parts:
Section Overhead. The STM-1 section overhead occupies the first nine
columns of the STM-1 frame, for total of 81 bytes.
Virtual Container. The remaining 261 columns of the STM-1 frame, which
contain a total of 2349 bytes, are allocated to the virtual container. The
virtual container itself comprises a container for the payload signal (260
SDH/SONET Ports
5-151
columns), preceded by one column of path overhead. The virtual container

carried in an STM-1 frame is referred to as a Virtual Container Level 4, or
VC-4. VC-4, which is transported unchanged across the SDH network,
provides a channel capacity of 150.34 Mbps.
The VC-4 structure includes one column (9 bytes) for the VC-4 path overhead,
leaving 260 columns of signal carrying capacity (149.76 Mbps). This carrying
capacity is sufficient for transporting a 139.264 Mbps tributary signal (the
fourth level in the PDH signal hierarchy). The VC-4 signal carrying capacity can
also be subdivided, to permit the transport of multiple lower-level PDH
signals.
Pointers
In Figure 5-22, the VC-4 appears to start immediately after the section overhead
part of the STM-1 frame.
Actually, to facilitate efficient multiplexing and cross-connection of signals in the
SDH network, VC-4 structures are allowed to float within the payload part of
STM-1 frames. This means that the VC-4 may begin anywhere within the STM-1
payload part. The result is that in most cases, a given VC-4 begins in one STM-1
frame and ends in the next.
Were the VC-4 not allowed to float, buffers would be required to store the VC-4
data up to the instant it can be inserted in the STM-1 frame. These buffers
(called slip buffers), which are often used in PDH multiplex equipment, introduce
long delays. Moreover, they also cause disruptions in case a slip occurs.
Identifying VC-4 Beginning in the STM-1 Frame

When a VC-4 is assembled into the STM-1 frame, a pointer (byte) located in the
section overhead of the STM-1 frame indicates the location of the first byte (J1)
of the VC-4 that starts in that STM-1 frame.
Using Pointers to Correct Timing Differences

SDH network are intended to operate as synchronous networks. Ideally, this
means that all SDH network nodes should derive their timing signals from a single
master network clock. However, in practical applications, network implementation
must accommodate timing differences (clock offsets). These may be the result of
an SDH node losing network timing reference and operating on its standby clock,
or it may be caused by timing differences at the boundary between two separate
SDH networks.
The VC-4 is allowed to float freely within the space made available for it in the
STM-1 frame, therefore phase adjustments can be made as required between the
VC-4 and the STM-1 frame.
To accommodate timing differences, the VC-4 can be moved (justified), positively
or negatively three bytes at time, with respect to the STM-1 frame. This is
achieved by simply recalculating and updating the pointer value at each SDH
network node. In addition to clock offsets, updating the pointer will also
accommodate any other adjustment required between the input SDH signal rate
and the timing reference of the SDH mode.
Pointer adjustments introduce jitter. Excessive jitter on a tributary signal degrades
signal quality and may cause errors. Therefore, SDH networks must be designed
5-152
SDH/SONET Ports
to permit reliable distribution of timing to minimize the number of pointer

adjustments.
SDH Overhead Data

SDH Overhead Data Types
In SDH networks, a transmission path can include three equipment functions:
SDH terminal multiplexer which performs the insertion/removal of tributary

signals into SDH frames
SDH cross-connect switch permits to change the routing of tributary signals

carried in SDH frames
Regenerator used to increase the physical range of the transmission path.
The resulting structure of an SDH transmission path is shown in Figure 5-23.

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

As shown in Figure 5-23, a transmission path can comprise three types of
segments:
Multiplexer section a part of a transmission path located between a

terminal multiplexer and an adjacent SDH cross-connect equipment, or
between two adjacent SDH terminal multiplexers.
Regenerator section a part of a transmission path located between a

terminal multiplexer or SDH cross-connect equipment and the adjacent
regenerator, or between two adjacent regenerators. A multiplexer section can
include up to three regenerator sections.
Path the logical connection between the point at which a tributary signal is
assembled into its virtual container, and the point at which it is disassembled
from the virtual container.
To provide the support and maintenance signals associated with transmission

across each segment, each of these segments is provided with its own overhead
data, hence three types of overhead data:
Section overhead, carried in the first nine columns of the STM-1 frame:
Multiplexer section (MS) overhead carried in overhead rows 5 to 9
Regenerator section (RS) overhead carried in overhead rows 1 to 3
AU pointers carried in overhead row 4.
SDH/SONET Ports
5-153
Path overhead, carried in the first column of a VC-4. The path overhead
carried in the VC-4 is called high-order path overhead; see the SDH Tributary
Units section for a description of the low-order path overhead.
Figure 5-24 shows the detailed structure of the overhead data in STM-1 frames.
Path
Overhead
Section Overhead
Framing
A1
Regenerator
Section
Overhead
(Rows 1 - 3)
AU Pointers
(Row 4)
Framing
A1
Framing
A1
Framing
A2
Framing
A2
Framing
A2
ID
C1
Path Trace
J1
BIP-8
B1
Orderwire
E1
User
F1
BIP-8
B3
DCC
D1
DCC
D2
DCC
D3
Signal Label
C2
Pointer
H1
Pointer
H2
Pointer
H3
APS
APS
K1
K2
User Channel
F2
DCC
D4
DCC
D5
DCC
D6
Multiframe
H4
DCC
D7
DCC
D8
DCC
D9
Z3
DCC
D10
DCC
D11
DCC
D12
Z4
Orderwire
E2
Z5
BIP-24
B2
Multiplex
Section
Overhead
(Rows 5 - 9)
Z1
B2
Z1
B2
Z1
Z2
Z2
Z2
Pointer
H3
Pointer
H3
Path Status
G1
Bytes reserved for future use
Figure 5-24. Organization of STM-1 Overhead Data
Regenerator Section Overhead (RSOH)

A regenerator section of an SDH network comprises the transmission medium
and associated equipment between a network element and the adjacent
regenerator, or between two adjacent regenerators. The associated equipment
includes the aggregate interfaces and SDH processing equipment which either
originates or terminates the regenerator section overhead.
The functions of the various bytes carried in the STM-1 regenerator section
overhead are described below.
Framing (A1, A2 Bytes)
The six framing bytes carry the framing pattern, and are used to indicate the start
of an STM-1 frame.
Channel Identifier (C1 Byte)
The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
5-154
SDH/SONET Ports
Parity Check (B1 Byte)

A 8-bit wide bit-interleaved parity (BIP-8) checksum is calculated over all the bits
in the STM-1 frame, to permit error monitoring over the regenerator section. The
computed even-parity checksum is placed in the RSOH of the following STM-1
frame.
Data Communication Channel (D1, D2, D3 Bytes)
The 192 kbps Data Communication Channel (DCC) provides the capability to
transfer network management and maintenance information between
regenerator section terminating equipment.
Orderwire Channel (E1 Byte)
The E1 byte is used to provide a local orderwire channel for voice
communications between regenerators and remote terminal locations.
User Communication Channel (F1 byte)
The F1 byte is intended to provide the network operator with a channel that is
terminated at each regenerator location, and can carry proprietary
communications.
The information transmitted on this channel can be passed unmodified through a
regenerator, or can be overwritten by data generated by the regenerator.
AU Pointers (H1, H2, H3 bytes)

The AU (Administration Unit) pointer bytes are used to enable the transfer of
STM-1 frames within STM-N frames, and therefore are processed by multiplexer
section terminating equipment. Separate pointers are provided for each STM-1
frame in an STM-N frame.
AU pointer function is to link between the section overhead and the associated
virtual container(s).
Multiplexer Section Overhead (MSOH)

A multiplexer section of an SDH network comprises the transmission medium,
together with the associated equipment (including regenerators) that provide the
means of transporting information between two consecutive network nodes
(e.g., SDH multiplexers). One of the network nodes originates the multiplexer
section overhead (MSOH) and the other terminates this overhead.
The functions of the various bytes carried in the STM-1 multiplexer section
overhead are described below.
Parity Check (B2 Bytes)
A 24-bit wide bit-interleaved parity (BIP) checksum is calculated over all the bits
in the STM-1 frame (except those in the regenerator section overhead). The
computed checksum is placed in the MSOH of the following STM-1 frame.
Protection Switching (K1, K2 Bytes)
The K1 and K2 bytes carry the information needed to activate/deactivate the
switching between the main and protection paths on a multiplexer section.
SDH/SONET Ports
5-155
Data Communication Channel (D4 to D12 Bytes)

Bytes D4 to D12 provide a 576 kbps data communication channel (DCC) between
multiplexer section termination equipment. This channel is used to carry network
administration and maintenance information.
Orderwire Channel (E2 Byte)
The E2 byte is used to provide a local orderwire channel for voice
communications between multiplexer section terminating equipment.
Alarm Signals
Alarm information is included as part of the MSOH. These functions are explained
in the SDH Maintenance Signals and Response to Abnormal Conditions section
below.
VC-4 Path Overhead Functions

The path overhead (POH) is contained within the virtual container portion of the
STM-1 frame. The POH data of the VC-4 occupies all the 9 bytes of the first
column. The functions of the various bytes carried in the VC-4 path overhead are
described below.
Path Trace Message (J1 Byte)
The J1 byte is used to repetitively transmit a 64-byte string (message). The
message is transmitted one byte per VC-4 frame.
A unique message is assigned to each path in an SDH network. Therefore, the
path trace message can be used to check continuity between any location on a
transmission path and the path source.
Parity Check (B3 Byte)
An 8-bit wide bit-interleaved parity even checksum, used for error performance
monitoring on the path, is calculated over all the bits of the previous VC-4. The
computed value is placed in the B3 byte.
Signal Label (C2 Byte)
The signal label byte, C2, indicates the structure of the VC-4 container. The signal
label can assume 256 values, however two of these values are of particular
importance:
The all 0s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)
The code 00000001 represents the VC-4 equipped state.
Path Status (G1 Byte)

The G1 byte is used to send status and performance monitoring information from
the receive side of the path terminating equipment to the path originating
equipment. This allows the status and performance of a path to be monitored
from either end, or at any point along the path.
5-156
SDH/SONET Ports
Multiframe Indication (H4 byte)

The H4 byte is used as a payload multiframe indicator, to provide support for
complex payload structures, for example payload structures carrying multiple
tributary units (TUs see the SDH Tributary Units section). If, for example, the TU
overhead is distributed over four TU frames, these four frames form a TU
multiframe structure. The H4 byte then indicates which frame of the TU
multiframe is present in the current VC-4.
User Communication Channel (F2 Byte)
The F2 byte supports a user channel that enables proprietary network operator
communications between path terminating equipment.
Alarm Signals
Alarm and performance information is included as part of the path overhead.
These functions are explained in SDH Maintenance Signals and Response to
Abnormal Conditions section below.
SDH Tributary Units

The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the
transport of a fourth level (139.264 Mbps) PDH multiplex signal.
To enable the transport and switching of lower-rate tributary signals within the
VC-4, several special structures, called Tributary Units (TUs), have been defined.
The characteristics of each TU type have been specifically selected to carry one of
the standardized PDH signal rates. In addition, a fixed number of whole TUs may
be mapped within the container area of a VC-4.
Tributary Unit Frame Structure

The structure of the tributary unit frame is rather similar to the SDH frame
structure. With reference to Figure 5-21, the tributary unit frame also includes a
section overhead part and a virtual container part, which comprises a container
and path overhead.
In general, the tributary unit frame is generated in three steps:
A low rate tributary signal is mapped into the TU container
Low-path path overhead is added before the container, to form the

corresponding virtual container (VC-11, VC-12, VC-2 or VC-3, depending on
the TU type)
A TU pointer is added to indicate the beginning of the VC within the TU

frame. This is the only element of TU section overhead.
The TU frame is then multiplexed into a fixed location within the VC-4.
Because of the byte interleaving method, a TU frame structure is distributed over
four consecutive VC-4 frames. It is therefore more accurate to refer to the
structure as a TU multiframe. The phase of the multiframe structure is indicated
by the H4 byte contained in the VC-4 path overhead.
SDH/SONET Ports
5-157
Tributary Unit Types

As mentioned above, specific containers (C), virtual containers (VC) and
associated TU structures have been defined for each standard PDH multiplex
signal level. These structures are explained below:
TU-11: Each TU-11 frame consists of 27 bytes, structured as 3 columns of 9

bytes. At a frame rate of 8000 Hz, these bytes provide a transport capacity
of 1.728 Mbps and will accommodate the mapping of a North American DS1
signal (1.544 Mbps). 84 TU-11s may be multiplexed into the STM-1 VC-4.

of 2.304 Mbps and will accommodate the mapping of a CEPT 2.048 Mbps
signal. 63 TU-12s may be multiplexed into the STM-1 VC-4.

of 6.912 Mbps and will accommodate the mapping of a North American DS2
signal. 21 TU-2s may be multiplexed into the STM-1 VC-4.

of 49.54 Mbps and will accommodate the mapping of a CEPT 34.368 Mbps
signal or a North American 44.768 DS3 signal. Three TU-3s may be
multiplexed into the STM-1 VC-4.
Figure 5-25 illustrates the assembly (multiplexing) of TUs in the VC-4 structure,
for the specific case of the TU-12. For other multiplexing options, see
Figure 5-26.
2430 Bytes/Frame
155.52 Mbps
9 Rows
Section
Overhead
VC-4 Path Overhead
Serial Signal
Stream
9 Columns
TU-12
No. 1
TU-12 No.2
to
TU-12 No.62
TU-12
No. 63
260 Columns
1 Column
Figure 5-25. VC-4 Carrying TU-12 Payload

As shown in Figure 5-25, 63 TU-12s can be packed into the 260 columns of
payload capacity (i.e., the C-4 container) provided by a VC-4. This leaves 8
columns in the C-4 container unused. These unused columns result from
intermediate stages in the TU-12 to VC-4 multiplexing process, and are filled by
fixed stuffing bytes.
5-158
SDH/SONET Ports
SDH Multiplexing Hierarchy

Figure 5-26 shows a general view of the SDH multiplexing hierarchy. The
hierarchy illustrates both the European and North American PDH multiplex levels.
Figure 5-26 also shows the utilization of additional SDH signal structures:
Note
STM-1
(155.520 Mbps)
TUG: tributary unit group, is the structure generated by combining several

lower level tributaries into the next higher level tributary. For example, TUG-2
is generated by combining 3 TU-12 or 4 TU-11, and TUG-3 is generated by
combining 7 TUG-2.
AU: administrative unit, is a structure that includes a VC and a pointer to the

beginning of the VC. For example, AU-3 contains one VC-3 and includes a
pointer to the beginning of the VC.
AUG: administrative unit group, is the structure generated by combining

several lower level administrative units into the next higher level
administrative unit. For example, AUG for the STM-1 level is generated by
combining 3 AU-3 (several AUG can be combined for generating STM-N (N =
4, 16, etc.) structures).
For simplicity, reference is made only to VCs (the actual structure needed to
transport a VC can be found from the SDH or SONET multiplexing hierarchy).
1
1
AU-4
VC-4
AU-3
VC-3
AUG
C-4
139.264 Mbps
(E4)
1
3
44.736 Mbps
(DS3)
3
VC-3
TU-3
C-3
34.368 Mbps
(E3)
TUG3
TU-2
1
7
2
TUG2
Legend
VC-2
C-2
3.152 Mbps
(DS1C)
VT3
TU-11
VC-11
C-11
1.544 Mbps
(DS1)
TU-12
VC-12
C-12
2.048 Mbps
(E1)
Pointer Processing
3
Mapping
6.312 Mbps
(DS2)
Figure 5-26. SDH Multiplexing Hierarchy

The flexibility of the SDH multiplexing approach is illustrated by the many paths
that can be used to build the various signal structures. For example, Figure 5-26
shows that the STM-1 signal can be generated by the following multiplexing
paths:
Each E1 signal is mapped into a VC-12, which is then encapsulated in a TU-12.
Each group of 3 TU-12 is combined to obtain a TUG-2 (3 E1 signals per TUG-2.)
SDH/SONET Ports
5-159
Seven TUG-2 are combined to obtain one TUG-3 (21 E1 signals per TUG-3).
TUG-3 is carried in a VC-3.
Three VC-3 are combined to generate one VC-4 (63 E1 signals per VC-4). The
STM-1 signal carries one VC-4.
SDH Maintenance Signals and Response to Abnormal

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

Signal
Description
Loss of Signal (LOS)
LOS state entered when received signal level drops below the value at which an
error ratio of 10 is predicted.
-3
LOS state exited when 2 consecutive valid framing patterns are received,
provided that during this time no new LOS condition has been detected
Out of Frame (OOF)
OOF state entered when 4 or 5 consecutive SDH frames are received with invalid
(errored) framing patterns. Maximum OOF detection time is therefore 625 s.
OOF state exited when 2 consecutive SDH frames are received with valid framing
patterns
Loss of Frame (LOF)
LOF state entered when OOF state exists for up to 3 ms. If OOFs are
intermittent, the timer is not reset to zero until an in-frame state persists
continuously for 0.25 ms.
LOF state exited when an in-frame state exists continuously for 1 to 3 ms
Loss of Pointer (LOP)
LOP state entered when N consecutive invalid pointers are received where N = 8,
9 or 10.
LOP state exited when 3 equal valid pointers or 3 consecutive AIS indications are
received.
Note
Multiplexer Section AIS
The AIS indication is an all 1s pattern in pointer bytes.
Sent by regenerator section terminating equipment (RSTE) to alert downstream

MSTE of detected LOS or LOF state. Indicated by STM signal containing valid
RSOH and a scrambled all 1s pattern in the rest of the frame.
Detected by MSTE when bits 6 to 8 of the received K2 byte are set to 111 for
3 consecutive frames. Removal is detected by MSTE when 3 consecutive frames
are received with a pattern other than 111 in bits 6 to 8 of K2.
Far End Receive Failure

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

250 s of detecting LOS, LOF or MS-AIS on incoming signal. Optionally
transmitted upon detection of excessive BER defect (equivalent BER, based on B2
bytes, exceeds 10 ). Indicated by setting bits 6 to 8 of transmitted K2 byte to
110.
-3
Detected by MSTE when bits 6 to 8 of received K2 byte are set to 110 for 3
consecutive frames. Removal is detected by MSTE when 3 consecutive frames are
received with a pattern other than 110 in bits 6 to 8 of K2.
Transmission of MS-AIS overrides MS-FERF
5-160
SDH/SONET Ports
Signal
Description
AU Path AIS
Sent by MSTE to alert downstream high order path terminating equipment (HO
PTE) of detected LOP state or received AU Path AIS. Indicated by transmitting all
1s pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when all 1s pattern is received in bytes H1 and H2 for 3
consecutive frames. Removal is detected when 3 consecutive valid AU pointers
are received
High Order Path Remote

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

received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
POH G1 byte to 1.
TU Path AIS
Sent downstream to alert low order path terminating equipment (LO PTE) of
detected TU LOP state or received TU path AIS. Indicated by transmitting all 1s
pattern in entire TU-1, TU-2 and TU-3 (i.e., pointer bytes V1-V3, V4 byte, plus all
bytes of associated VC-1, VC-2 and VC-3 loaded by all 1s pattern).
Detected by peer HO PTE when bit 5 of received G1 byte is set to 1 for 10

consecutive frames. Removal detected when peer HO PTE receives 10
consecutive frames with bit 5 of G1 byte set to 0
Detected by LO PTE when all 1s pattern received in bytes V1 and V2 for 3

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

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

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

received TU Path AIS. Sent upstream to peer LO PTE.
Indicated by setting bit 8 of LO POH V5 byte to 1.
Detected by peer LO PTE when bit 8 of received V5 byte is set to 1 or 10
consecutive multiframes. Removal detected when peer LO PTE receives 10
consecutive multiframes with bit 8 of V5 byte set to 0.
Note
LO Path RAI is only available when generating and/or receiving floating

mode tributary unit payload structures.
This section describes the response to the wide range of conditions that can be
detected by the maintenance means built into the SDH frames, and the flow of
alarm and indication signals.
Figure 5-27 provides a graphical representation of the flow of alarm and

indication signals through an SDH transmission path.
SDH/SONET Ports
5-161

Low Order Path
High Order Path

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

Regenerator Section Terminating Equipment
Multiplexer Section Terminating Equipment
Figure 5-27. Flow of Alarm and Indication Signals through an SDH Transmission Path
Flow of Alarm and Response Signals

The major alarm conditions such as Loss of Signal (LOS), Loss of Frame (LOF),
and Loss of Pointer (LOP) cause various types of Alarm Indication Signals (AIS) to
be transmitted downstream.
In response to the detection of an AIS signals, and detection of major receiver
alarm conditions, other alarm signals are sent upstream to warn of trouble
downstream:
5-162
Far End Receive Failure (FERF) is sent upstream in the multiplexer overhead
after multiplexer section AIS, or LOS, or LOF has been detected by equipment
terminating in a multiplexer section span;
A Remote Alarm Indication (RAI) for a high order path is sent upstream after
a path AIS or LOP condition has been detected by equipment terminating a
path
SDH/SONET Ports
A Remote Alarm Indication (RAI) for a low order path is sent upstream after
low order path AIS or LOP condition has been detected by equipment
terminating a low order path.
Performance Monitoring
Performance monitoring at each level in the maintenance hierarchy is based on
the use of the byte interleaved parity (BIP) checksums calculated on a frame by
frame basis. These BIP checksums are sent downstream in the overhead
associated with the regenerator section, multiplexer section and path
maintenance spans.
In response to the detection of errors using the BIP checksums, the equipment
terminating the corresponding path sends upstream Far End Block Error (FEBE)
signals.
SONET Environment
SONET (Synchronous Optical Network) is an alternative standard to SDH, widely
used in North America and other parts of the world. SONET uses similar
implementation principles, and even the frame structures are quite similar to
those used by SDH. Therefore, the following description is based on the
information already presented for SDH.
Figure 5-28 shows the SONET multiplexing hierarchy.

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

The designations of the main signal structures in the SONET hierarchy are as
follows:
Containers are replaced by Synchronous Payload Envelopes (SPE) for the

various virtual tributaries (VTs)
Virtual containers (VCs) are replaced by virtual tributaries (VTs), however the
rates are similar to those used in the SDH hierarchy
SDH/SONET Ports
5-163
Tributary unit groups (TUGs) are replaced by virtual tributary groups
The VC-3 level is replaced by the Synchronous Transport Signal level 1

(STS-1), and has the same rate (51.840 Mbps).
3 STS-1 can be combined to obtain one Synchronous Transport Signal level 3

(STS-3) at the same rate as STM-1 (155.520 Mbps). The corresponding
optical line signal is designated OC-3.
SDH/SONET Interfaces
Each CL.2 module has two STM-1/OC-3/STM-4/OC-12 ports. The ports can be
ordered with the following interfaces:
STM-1/OC-3:155.52 Mbps 20 ppm
STM-4/OC-12: 622.08 Mbps 20 ppm
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical. The bit rate for the STM-4/OC-12 version is set by means
of the speed parameter.
The framer operating mode, SDH or SONET, is selected by software configuration.
The two modules must always use the same mode, and therefore selecting the
mode for one module automatically switches the other to the same mode.
Each port has an SFP socket that provides the physical interface. RAD offers a
wide range of SFPs covering requirements from short-range low-cost optical
interfaces to long-range, high-performance interfaces. Optical SFPs are
terminated in LC connectors. RAD also offers SFPs with electrical interfaces for
intra-office applications.
The port interfaces support the enhanced digital diagnostic monitoring interface
per SFF-8472, which enables collecting status and performance data from the
SFPs, as well as alerting if abnormal conditions might cause damage or
performance degradation.
SFPs are hot-swappable, and can be replaced in the field. This enables upgrading
the network port interface characteristics as network topology changes.
Automatic Laser Shutdown

For safety, Megaplex-4100 uses automatic laser shutdown (ALS), which protects
against accidental exposure to laser radiation in case of fiber breaks or
disconnections. This is achieved by automatically switching off the transmitter of
an SDH/SONET interface when the receiver of the same interface reports loss of
the optical signal. To enable automatic recovery, the transmitter is periodically
turned back on, for a short time. If the receive signal does not reappear, the
transmitter is turned back off; if the receive signal reappears, the transmitter
remains on (normal operation).
Inband Management Access through SDH/SONET Networks

Figure 5-29 illustrates the inband management access through SDH/SONET
networks. The inband management is done via the Data Communication Channel
(DCC) carried in the SDH/SONET overhead. Each SDH/SONET link can have its DCC
used for management. DCC ports use the host IP address of the Megaplex-4100
management subsystem.
5-164
SDH/SONET Ports
Note
Inband management can also support more complex topologies, such as rings.
However, this is possible only if the carriers SDH/SONET network provides access
to the DCC and enables transparent transfer of user data through the DCC. In this
case, a Telnet host or an SNMP-based network management station connected to
one of the Megaplex-4100 units in the network can manage all the other units,
inband.
Typically, the Telnet host or management station is connected to a CL Ethernet
port of the local Megaplex-4100 unit. To enable remote management, the
management traffic not addressed to the internal management subsystem of the
Megaplex-4100 is also connected by this subsystem to the DCCs carried by the
other SDH/SONET links connected to the Megaplex-4100.
At the remote Megaplex-4100 units, the management traffic is extracted from
the DCC and connected to the local unit management subsystem. This
arrangement enables the management station to manage each remote
Megaplex-4100 unit.
Figure 5-29. Inband Management Access through SDH/SONET Networks

As mentioned above, the inband management traffic is carried in the DCC bytes,
as part of the SDH/SONET overhead. The user can select the DCC bytes to carry
the traffic, which are named differently for SDH and SONET environments.
SDH:
Regenerator DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
Multiplex DCC bytes (D4 to D12), which provide a 576 kbps channel
terminated at SDH multiplex section terminating equipment.
SDH/SONET Ports
5-165
SONET:
Section DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
Line DCC bytes (D4 to D12), which provide a 576 kbps channel terminated at
SDH multiplex section terminating equipment.
You can also select the encapsulation and routing protocols used for inband
management parameters:
Two encapsulation options are available: HDLC, or PPP over HDLC in

accordance with RFC1661 and RFC1662.
For compatibility with particular implementations of the HDLC encapsulation
protocol for management purposes, you can select the Type 1 flavor (for this
flavor, the LCP (Link Control Protocol) packets do not include address and
control fields in their overhead).
Two options are also available for the management traffic routing protocol:
RAD proprietary protocol. This protocol is sufficient for managing any RAD
equipment and should always be used with HDLC encapsulation.
RIP2: the Megaplex-4100 transmits RIP2 routing tables. This permits
standard RIP routers to reach the Megaplex-4100 SNMP agent through the
inband (DCC) channel. The RIP2 network is limited to 14 nodes.
SDH/SONET Hierarchy and Allowed Activities

The Megaplex-4100 CLI architecture follows the SDH/SONET hierarchy. The kinds
of activities available on each SDH/SONET hierarchical level are listed below:
Activities
SDH/SONET
AUG/OC-3
TUG-3/STS-1
VC-12/VT-1.5
Configuring Port Parameters
Assigning VC Profile
Displaying Status
Displaying Statistics
The following sections explain how these activities are performed.
Factory Defaults (SDH/SONET Parameters)

Megaplex-4100 is supplied with all SDH/SONET ports enabled. Other parameter
5-166
Parameter
Default Value
frame-type
sdh
speed
155mbps
dcc
disabled
dcc mode
d1-to-d3
SDH/SONET Ports
Parameter
Default Value
dcc routing-protocol
none
dcc deviation
standard
threshold eed
1e-3
threshold sd
1e-6
j0-pathtrace direction
tx
j0-pathtrace padding
nulls
j0-pathtrace string
www.rad.com
rdi-on-failure
enabled
tim-response
enabled
disabled
loopback
disabled
Tx-ssm
enabled
Configuring SDH/SONET Link Parameters
To configure external SDH/SONET parameters:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
Task
Command
Comments

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

accordance with the SDH or
SONET standards
frame-type {sdh | sonet}
Selecting the SDH/SONET port

speed and operating mode
speed {155mbps | 622mbps}
Enabling DCC inband

management and configuring
DCC parameters: encapsulation
protocol and the DCC bytes used
to carry inband management
traffic
dcc [encapsulation {hdlc |

ppp-o-hdlc | type1}] [mode
{d1-to-d3 | d4-to-d12}]
[routing-protocol
{ none | prop-rip | rip2}]
[deviation {standard | type1}
See Functional Description above for

parameter explanation. Using no dcc
disables inband management
Selecting EED (error rate

degradation) and SD (signal
degrade) thresholds
threshold [eed {1e-3 | 1e-4 |

1e-5}] [sd {1e-6 | 1e-7 | 1e8 | 1e-9}]
If the selected BER value is exceeded,

Megaplex-4100 generates the relevant
(EED or SD) alarm
155mbps: STM-1 (SDH)/OC-3 (SONET)

622mbps: STM-4 (SDH)/OC-12 (SONET)
SDH/SONET Ports
5-167
Task
Command
Comments
Enabling the checking of the

receive/transmit path trace label
by the port and configuring the
optional path trace direction and
padding (when the path label is
shorter than the required length
of 15 characters)
j0-pathtrace [direction { tx |
rx-tx }] [string <path-tracestring> ] [padding {spaces |
nulls }]
Using no j0-pathtrace disables the

checking
Enabling RDI (remote defect

indication) sending in case of
failure
rdi-on-failure
The SDH fault conditions are:
LOS (loss of SDH signal)
LOF (loss of SDH frame)
AIS (alarm indication signal)
Using no rdi-on-failure disables RDI

sending
Enabling the sending of RDI
indications by the port, in case
the received path trace label
(carried in SDH overhead byte
J0) is different from the
expected path trace label
tim-response
Using no tim-response disables sending

of RDI indications
Enabling automatic laser

shutdown of optical laser link on
sync loss
Using no automatic-laser-shutdown
disables automatic shutdown
Defines the administrative unit

group (AUG)
aug <aug number>
This option is valid only when

frame-type=sdh.
Possible values:
for speed=155mbps: 1
for speed=622mbps: 1 to 4
See also Assigning VC Profiles to

AUG/OC-3 below
Enabling SSM transmission
tx-ssm
Defines an OC-3 connection
oc3 <oc3 number>
This option is valid only when

frame-type=sonet.
Possible values:
for speed=155mbps: 1
for speed=622mbps: 1 to 4
See also Assigning VC Profiles to

AUG/OC-3 below
Example
This example illustrates how to configure an SDH Port with management via DCC
(Dedicated Communication Channel).
1. Program SDH Port 1 in Slot CL-A and configure DCC management with the
following parameters:
5-168
SDH/SONET Ports
Speed: 155 Mbps
DCC encapsulation protocol: HDLC
DCC bytes used to carry inband management traffic: D1 D3
mp4100>config>slot#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
cl-a card-type cl cl2-622gbe

sdh-sonet cl-a/1 no shutdown
sdh-sonet cl-a/1 frame-type sdh
sdh-sonet cl-a/1 speed 155mbps
sdh-sonet cl-a/1 dcc encapsulation hdlc mode d1-to-d3
Configure router interface 3, address 10.10.10.9, subnet mask 24

mp4100>config>router 1 interface 3 address 10.10.10.9/24
Bind SDH port 1 on CL-A to router interface 2
mp4100>config>router# 1 interface 3 bind sdh-sonet cl-a/1
The inband management connectivity via DCC is established.
Assigning VC Profiles to AUG/OC-3
To assign a VC profile to AUG:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH port
to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
Set frame-type to sdh.
Enter the aug command followed by the desired aug number (1 for 155 Mbps, 1
to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> aug(number)# prompt is
displayed.

Task
Command
Comments
Assigning user-defined VC profile

to the port

Before you assign the user-defined
profile, you must use the no vc command
to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement
To assign a VC Profile to OC-3:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SONET port
to configure.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.
Set frame-type to sonet.
SDH/SONET Ports
5-169
Enter the oc3 command followed by the desired OC-3 number (1 for 155 Mbps, 1
to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> oc3(number)# prompt is
displayed.
Task
Command
Comments

to the port

to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement
Testing SDH/SONET Ports

Megaplex-4100 features remote loopbacks on the SDH/SONET ports of the CL.2
modules and local and remote loopbacks on AUG/OC-3, TUG-3/STS-1, and
VC-12/VT-1.5. The following sections briefly describe each type of loopback. Table
5-39 shows the paths of the signals when each loopback is activated.
Table 5-39. SDH/SONET Loopbacks
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
Diagnostic
Function
2
I/O Port
DS1
Cross-Connect
Matrix
..
..
..
..
E1/T1
Mapper
VC/VT
Matrix
Framer
Remote
loopback on
SDH/SONET link
Local loopbacks
on AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
ports
5-170
SDH/SONET Ports
SDH/
SONET
Framer
VC/VT
Matrix
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
Diagnostic
Function
2
I/O Port
DS1
Cross-Connect
Matrix
.
.
.
..
.
.
.
E1/T1
Mapper
Remote
loopbacks on
AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
ports
VC/VT
Matrix
SDH/
SONET
Framer
VC/VT
Matrix
Remote Loopback on SDH/SONET Link

As shown in Table 5-39, the remote loopback is activated within the network side
circuits of the SDH/SONET framer, and therefore the loopback signal paths
includes all the circuits of the local Megaplex-4100 SDH/SONET interface but very
few of the framer circuits.
When the remote loopback is activated, the received SDH/SONET signal is
processed by the receive path of the local Megaplex-4100 SDH/SONET interface
and then returned to the input of the transmit path through the framer.
Therefore, when the remote loopback is activated on the external port, the
receive signal is returned to the remote unit. To correct transmission distortions,
the returned signal is regenerated by the SDH/SONET interface circuits.
The remote loopback should be activated at only one of the two units
interconnected by the SDH/SONET link, otherwise an unstable situation occurs.
Local Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5

As shown in Table 5-39, the local loopback is activated within the SDH/SONET VC
cross-connect matrix. When the local loopback is activated, the transmit signal is
returned to the receive path before the output to the SDH/SONET framer, at
different points for each entity.
While the loopback is activated, the equipment mapped to the corresponding
E1-i/T1-i port of the local Megaplex-4100 must receive its own signal, and thus it
must be frame-synchronized.
Remote Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5

As shown in Table 5-39, the remote loopback on AUG/OC-3, TUG-3/STS-1, or
VC-12/VT-1.5 is activated within the network side circuits of the VC/VT
cross-connect matrix. Therefore, the loopback signal path includes all the circuits
SDH/SONET Ports
5-171
of the local Megaplex-4100 SDH/SONET interface and framer, but very few of the
other circuits.
When the remote loopback is activated, the received SDH/SONET signal is
processed by the receive path of the local Megaplex-4100 SDH/SONET interface
and then returned to the input of the transmit path through the framer.
Therefore, when the remote loopback is activated on the external port, the
receive signal is returned to the remote unit.
The remote loopback should be activated only after checking that the equipment
connected at the remote side to the tested unit operates normally during a local
loopback. In this case, the remote unit must receive its own signal, and thus it
must be frame-synchronized. The effect on the ports of the remote unit is mixed,
as explained above for the local loopback.
Loopback Duration
option to limit its duration to a selectable interval in the range of 1 through 60
minutes.
To perform a loopback on the SDH/SONET port:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to be tested.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Activating the remote

loopback and setting its
duration (in minutes)
loopback {remote} [duration

<duration in minutes 1..60> ]
Using no loopback remote disables the

loopback
To perform a loopback on the AUG/OC-3 port:
5-172
Default (without duration parameter) is

infinite loopback
From the config>port>sdh-sonet> (<slot>/<port 1..2>)

aug (<aug number 1..4>) or config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>) # context, activate the loopback as follows:
SDH/SONET Ports
Task
Command
Comments
Activating the local or

remote loopback on this
aug/oc3 port
loopback { remote | local}
Using no loopback followed by the

corresponding command disables the
loopback
To perform a loopback on the TUG-3/STS-1 port:

1. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4>)
tug3 (<tug3 number 1..3>)#
SONET:
oc3 (<oc3 number 1..4>)
sts1 (<sts1 number 1..3>) #
Activate the loopback as follows:
Task
Command
Comments

tug3/sts1
loopback {remote | local}

loopback
To perform a loopback on the VC-12/VT-1.5:

1. Navigate to:
SDH:
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
sts1 (<sts1 number 1..3>)
vt1-5 (<tug2 number 1..7>)/ <tributary number 1..4>)#.
Activate the loopback as follows:
Task
vc12/vc1-5
Command
Comments
loopback {remote | local}

loopback
SDH/SONET Ports
5-173
Viewing SDH/SONET Status Information

For viewing the status of the SDH/SONET hierarchical entities, follow the
instructions below.
To view the status of an SDH/SONET port:

1. Navigate to config>port>sdh-sonet> (<slot>/<port>)#
Type show status.
mp4100>config>port>sdh-sonet(cl-a/1)# show status
General
--------------------------------------------------------------Name
: CL-A sdh-sonet 01
Administrative Status
: Up
Operational Status
: Up
Loopback Type
: None
Connector Type
: SFP In
Expected Trace Message (J0) : www.rad.com
Received Trace Message (J0) :
Rx Quality
: SEC
Tx Quality
: SEC
SFP
--------------------------------------------------------------Connector Type
: LC
Manufacturer Name
: CORETEK
: CT-0155TSP-MB5L
Wave Length (nm)
: 1310
Fiber Type
: SM
RX Power (dBm)
: -50.0 dBm
TX Power (dBm)
:
Laser Bias (mA)
:
Laser Temperature (Celsius) :
Power Supply (V)
:
Note
-12.0 dBm
14.0 mA
47.0 C
3.3 V
The last 5 rows are displayed only for SFPs with built-in DDM functionality.
The performance monitoring data for the SDH/SONET link physical layer includes
status data for each link port, and SFP data for the installed SFPs. The table
below explains the parameters of the SFP installed for selected port.
Table 5-40. Link SFP Parameters

Parameter
Description
Connector Type
Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name
Displays the original manufacturers name
5-174
SDH/SONET Ports
Parameter
Description
Vendor PN
Displays the original vendors part number
Typical Max. Range

(Meter)
Displays the maximum range expected to be achieved over typical optical fibers, in
meters
Wave Length (nm)
Displays the nominal operating wavelength of the SFP, in nm
Fiber Type
Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm)
Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm)
Displays the current optical power, in dBm, received by the SFP
Laser Bias (mA)
Displays the measured laser bias current, in mA
Laser Temperature
(Celcius)
Displays the measured laser temperature, in C
Power Supply (V)
Displays the SFP power supply voltage
To view the status of an AUG-3/OC-3:

1. Navigate to:
SDH:
aug (<aug number 1..4> )#
SONET:
oc3 (<oc3 number 1..4>#
Type show status.
mp4100>config>port>sdh-sonet(cl-a/1)>aug(1)# show status
General
--------------------------------------------------------------Expected Trace Message (J1) : www.rad.com
Received Trace Message (J1) : www.rad.com
Expected Signal Label
: 0x1B
Received Signal Label
: 0x1B
Loopback Type
: None
To view the status of a TUG-3/STS-1:

1. Navigate to:
SDH:
aug (<aug number 1..4> )
SDH/SONET Ports
5-175
SONET:
oc3 (<oc3 number 1..4>
Type show status.
mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)# show status
General
: 0x02
: 0x02
Loopback Type
: None
To view the status of a VC-12/VT-1.5:

1. Navigate to:
SDH:
aug (<aug number 1..4> )
tug3 (<tug3 number 1..3>)
vc12 (<tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
oc3 <oc3 number 1..4>)
sts1 <sts1 number 1..3>)
vt1-5 <tug2 number 1..7>)/ <tributary number 1..4>)#.
Type show status.
mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)# show status

General
: 0x05
: 0x05
Loopback Type
: None
Displaying SDH/SONET Statistics

SDH/SONET ports of Megaplex-4100 feature the collection of statistical
diagnostics at different hierarchical levels, per ANSI T1.403.
Note
5-176
Only locally-terminated entities (AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5) are

monitored by Megaplex-4100.
SDH/SONET Ports
To display the SDH/SONET port statistics:
At the prompt config>slot>port>sdh-sonet (<slot><port>)#, enter show

statistics followed by parameters listed below.
To display the AUG/OC-3 statistics:

1. Navigate to:
SDH:
aug (<aug number 1..4> )#
SONET:
oc3 (<oc3 number 1..4> )#
Enter show statistics followed by parameters listed in the table below.
To display the TUG-3/STS-1 statistics:

1. Navigate to:
SDH:
aug (<aug number 1..4>)
SONET:
To display the VC-12/VT-1.5 statistics:

1. Navigate to:
SDH:
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
sts1 (<sts1 number 1..3>)
vt1-5 (<tug2 number 1..7>)/ (<tributary number 1..4>)#.
SDH/SONET Ports
5-177
Task
Command
Comments
show statistics {all | current}
current Displays the current

statistics
all Displays all statistics: first

current interval statistics, then
statistics for all valid intervals
for a specific interval
SDH/SONET statistics are displayed. The counters are described in

Table 5-41 and Table 5-42. For example:
Current statistics:
mp4100>config>port>sdh-sonet(cl-a/1)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 222
Valid Intervals
: 2
ES
: 0
SES
: 0
SEFS
: 0
CV
: 0
5-178
SDH/SONET Ports

mp4100>config>port>sdh-sonet(cl-a/1)# show statistics interval 67
Interval
--------------------------------------------------------------Interval Number : 67
Section ES
: 0
Section SES
: 0
Section SEFS
: 31
Section CV
: 0
All statistics:
mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)#
show statistics all
Current
--------------------------------------------------------------Time Elapsed (Sec) : 712
Valid Intervals
: 1
ES
: 0
SES
: 0
UAS
: 0
CV
: 0
Interval
-------------------------------------------------------------Interval Number : 1
ES
: 3
SES
: 2
UAS
: 57
CV
: 0
SDH/SONET Ports
5-179
Table 5-41. SDH/SONET Port Statistics Parameters Current 15-Minute Interval

Parameter
Description
ES

An errored second is any second containing one or more of the following types of
errors:
SEFS (UAS)
Severely Errored Frame (SEF) defect (also called Out-of-Frame (OOF) event):
A SEF defect is declared after detection of four contiguous errored frame

alignment words.
The SEF defect is terminated when two contiguous error-free frame words are
detected.
Loss of Signal (LOS) defect:
A LOS defect is declared after no transitions are detected in the incoming line
signal (before descrambling) in an interval of 2.3 to 100 microseconds.
The LOS defect is terminated after a 125-microsecond interval (one frame) in

which no LOS defect is detected.
Loss of Pointer (LOP) defect:
A LOP defect is declared after no valid pointer is detected in eight consecutive

frames. The LOP defect will not be reported while an AIS signal is present.
The LOP defect is terminated after a valid pointer is detected.
Alarm Indication Signal (AIS) received in the SDH overhead.
Coding Violation (CV): a coding violation is declared when a Bit Interleaved Parity
(BIP) error is detected in the incoming signal. The BIP information is collected using
the B1 byte in the Section Overhead.
Displays the number of unavailable seconds (UAS (SEFS)) in the current interval.
An unavailable second is any second in which one or more SEF defects have been
detected.
SES
A SES is any second in which multiple error events of the types taken into
consideration for an ES have occurred.
CV
Displays the number of coding violations (CV) in the current interval.
Time elapsed
The range is 1 to 900 seconds
Valid Intervals
displayed, in addition to the current (not finished) interval (up to 96)
Table 5-42. SDH/SONET Port Statistics Parameters Selected 15-Minute Interval

Parameter
Description
Section ES
Section SES
Section SEFS
Displays the total number of unavailable seconds (SEFS/UAS) in the selected interval
Section CV
Displays the total number of code violations (CV) in the selected interval
Interval number
Number of interval for which statistics is displayed
5-180
SDH/SONET Ports
Clearing Statistics
There are two options for clearing SDH/SONET statistics data:
Clearing current interval statistics
Clearing all statistics, except for the current interval.
To clear the current interval statistics:

1. Navigate to the corresponding entity as described above.
Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
To clear all statistics data except for from the current interval:
Enter clear-statistics current-all.
5.22 VC Profiles
In the Megaplex-4100 architecture, any SDH/SONET unit of order lower than
SDH/SONET port is configured by creating VC profiles and binding it to the
corresponding unit. You can create up to 64 profiles to define the handling of
SDH/SONET (VC/VT/STS) traffic. You can then assign the required profile to a gfp,
hdlc, e1, e1-i, aug, t1, t1-i or oc-3 port.
Four pre-defined default VC profiles are available in the system. They are bound
automatically to VC-12/VT-1.5/ VC-3/VC-4/STS-1/STS-3C or E1/T1 ports when
certain configurations take place in the system. Table 5-43 lists these profiles
together with their names and corresponding configurations.
Table 5-43. Default VC Profiles

Name
VC Profile
Matches Configuration
lvc-eos
payload-label 0x05
VC-12/VT-1.5 bound to VCG
pathtrace direction tx length 15plus-crc string

"www.rad.com" padding nulls
Note: When this profile is
no plm-response
no tim-response
rate-threshold eed e-3 sd e-6
assigned to GFP ports (which

is done automatically), the
pathtrace parameters define
the J2 pathtrace
interval-threshold cv 25 es 20 ses 3 uas 10

day-threshold cv 250 es 200 ses 7 uas 10
VC Profiles
5-181
Name
VC Profile
Matches Configuration
tug-structure
payload-label 0x02
VC-12/VT1.5 bound to VCG on

the overhead (POH) level or
E1/T1 is cross-connected to
SDH/SONET ports directly

no plm-response
no tim-response
assigned to AUG/OC-3 ports

(which is done automatically),
the pathtrace parameters
define the J1 pathtrace
When this profile is assigned
to E1/T1 ports (which is done
automatically), the pathtrace
parameters define the J2
pathtrace
hvc-laps
payload-label 0x18
VC-3/VC-4/STS-1/STS-3C
bound to VCG with LAPS
encapsulation (hdlc)
no plm-response
no tim-response
assigned to HDLC ports (which

the J1 pathtrace

hvc-gfp
payload-label 0x1b
no plm-response
no tim-response
VC-3/VC-4/STS-1/STS-3C
bound to VCG with GFP
encapsulation (gfp)

assigned to GFP ports (which
the J1 pathtrace
Factory Defaults
The VC profile parameter defaults are listed in the table below.
5-182
VC Profiles
Parameter
Default Value
payload-label
0x02 (default values for pre-defined profiles are listed in

Table 5-43)
pathtrace direction
tx
pathtrace padding
nulls
pathtrace length
15plus-crc
plm-response
disable
Parameter
Default Value
tim-response
disable
rate-threshold eed
e-3
rate-threshold sd
e-6
interval-threshold cv
25
interval-threshold es
20
interval-threshold ses
interval-threshold uas
10
day-threshold cv
250
day-threshold es
200
day-threshold ses
day-threshold uas
10
Configuring VC Profiles
Usually the four predefined VC profiles assigned to the corresponding units by
default should satify the user needs. However, if it is necessary to add and
configure a new user-defined profile, you must first disconnect the respective
predefined profile and only then configure and assign the new one.
To add a user-defined VC profile:

Type vc profile <vc-profile-name>.
A VC profile with the specified name is created and the following prompt
is displayed: config>port>vc-profile(<vc-profile-name>)$.
Configure the VC profile as described below.
To configure a VC profile:
1. Navigate to configure port vc-profile <vc-profile-name> to select the VC
profile to configure.
The config>port>vc-profile(<vc-profile-name>)# prompt is displayed.
Task
Command
Comments
Specifying the expected payload

label (one byte)
payload-label { 00 to FF
(hexa) }

FF (two digits)
VC Profiles
5-183
Task

Command
Comments
Using no pathtrace disables the checking
Enabling the checking of the

receive/transmit path trace label
by the port and configuring the
optional path trace direction and
padding
pathtrace [direction { tx | rxtx}] [length {64 | 15pluscrc}] [string <path-tracestring>] [padding {spaces |
nulls}]
When the VC profile is assigned to

au-4/oc-3 ports, this string defines the J1
pathtrace.
Enables the sending of RDI

the received signal label (SDH
overhead byte C2 or V5) is
different from the expected
signal label
plm-response rdi
Using no plm-response disables RDI

indications
Enables the sending of RDI

the received path trace label
(carried in SDH overhead byte J1
or J2) is different from the
expected path trace label
tim-response rdi
Using no tim-response disables RDI

indications
Selecting EED (error rate

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

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

Megaplex-4100 generates the relevant
(EED or SD) alarm
Setting CV, ES, SES and/or UAS

counter value during a 15-min
interval starting from which a
trap will be sent
interval-threshold [cv
<cv-value 0-900>] [es <esvalue 0-900>] [ses <sesvalue 0-900>] [uas
<uas-value 0-900>]
Setting CV, ES, SES and/or UAS

counter value during 24-hours
interval starting from which a
trap will be sent
day-threshold [cv <cv-value

0-86400>] [es <es-value 086400>] [ses <ses-value 086400>] [uas <uas-value 086400>]
When the VC profile is assigned to

gfp/hdlc/e1/t1 ports, this string defines
the J2 pathtrace.
5.23 Logical MAC Ports

To describe and map the Ethernet traffic passing over different media (E1/T1,
SDH/SONET, etc), the Megaplex-4100 architecture uses a concept of Logical MAC
ports. Logical MAC represents the MAC layer of the entity. It should be bound to a
gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical layer.
Table 5-44 lists the possible entities that can be bound to the Logical MAC, with
their corresponding media, protocols and possible values.
5-184
Logical MAC Ports
Table 5-44. Entities Bound to Logical MAC

Entities
Media
Protocol
Module
Possible
Values
gfp
Ethernet over
SDH/SONET
GFP encapsulation
protocol
CL.2
1 to 32
hdlc
Ethernet over
SDH/SONET
LAPS encapsulation
protocol
CL.2
1 to 32
hdlc
Ethernet over
E1/T1
HDLC Layer 2 protocol
M8E1/M8T1, M8SL
1 to 32
mlppp
Ethernet over E1
MLPPP, PPP Layer 2

protocols
M8E1, M8SL
Factory Defaults
Megaplex-4100 is supplied with all Logical MAC ports disabled.
Configuring Logical MAC Ports
To configure the Logical MAC port:

1. Navigate to configure port logical-mac <slot>/<port> to select the Logical Mac
entity to configure.
The config>port>logical-mac>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments

Logical MAC
name <string>
Administratively enabling Logical

MAC
no shutdown
Using shutdown disables the Logical MAC
Binding HDLC port to Logical MAC
bind hdlc <slot>/<port>
Ethernet over E1/T1: port=HDLC bundle

Ethernet over SDH/SONET: port=VCG using
LAPS encapsulation protocol
Binding GFP port to Logical MAC
bind gfp <slot>/<port>
GFP port=VCG using GFP encapsulation

protocol
Binding MLPPP port to Logical

MAC
bind mlppp <slot>/<port>
To bind a flow to a Logical MAC port, see ingress-port logical-mac command

under config>flows>flow.
Logical MAC Ports
5-185
5.24 VCG Ports

Virtually concatenated groups (VCGs) can be configured on SDH/SONET links.
To prepare Ethernet traffic for efficient transport over the SDH/SONET network,
the traffic is encapsulated using LAPS or GFP encapsulation, before being
transmitted over a virtually concatenated group. Megaplex-4100 also supports
the Link Capacity Adjustment Scheme (LCAS), covered by ITU-T Rec. G.7042.
In Megaplex-4100, VCGs are protected by the Ethernet group redundancy. For
description and instructions, refer to Ethernet Group Protection.
Standards
Two types of supported encapsulation comply with the following standards:
LAPS (Link Access Protocol SDH) encapsulation in accordance with ITU-T

Rec. X.86
GFP (Generic Framing Procedure) encapsulation in accordance with ITU-T Rec.

G.7041, using the framed mode.
Benefits
Virtual concatenation has the following main advantages:
Scalability: allows bandwidth to be selected in relatively small increments, as

required to match the desired payload data rate.
Efficiency: the resulting signals are easily routed through a SDH/SONET

network, without wasting bandwidth, and therefore allows for more efficient
utilization of the bandwidth available on existing networks.
Compatibility: virtual concatenation requires only the end nodes to be aware

of the containers being virtually concatenated, and therefore is transparent
to the core network elements.
Resiliency: individual members of a virtually concatenated group can be freely

routed across the network.
Ethernet over SDH/SONET
To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4100 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
5-186
VCG Ports
The processing is as follows:

1. At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
The resulting streams are mapped to the desired VCs/SPEs, also configured by
management. The Path Overhead (POH) byte carried by all the group
members is used to transfer to the far endpoint the information needed to
identify:
The relative time difference between arriving members of the virtual

group
The sequence number of each arriving member.
Each member of the virtual group is independently transmitted through the

network. The network need not be aware of the type of payload carried by
the virtual members of the group.
At the receiving end, the phase of the incoming VCs/SPEs is aligned and then the
original payload data stream is rebuilt. This requires using a memory of
appropriate size for buffering all the arriving members of the group at the
receiving end. The memory size depends on the maximum expected delay,
therefore to minimize latency the maximum delay to be compensated can be
defined by management.
Encapsulation Modes
Ethernet frames must be encapsulated before transport over the SDH/SONET
network. You can select the desired encapsulation mode, independently, for each
virtually concatenated group. This can be done by binding VCG ports to the
corresponding entity:
For LAPS encapsulation, see Configuring HDLC Ports.
For GFP encapsulation, see Configuring GFP Ports.
Link Bandwidth Utilization

Link bandwidth utilization is configured by selecting the type and number of
VCs/VTs allocated to each group. Following are several examples of bandwidth
allocation enabled by virtual concatenation:
When using VC-3: maximum of two virtually concatenated groups per

Megaplex-4100. For example, assuming that it is necessary to support
streaming payload over full duplex Ethernet, a virtually concatenated group
using two VC-3 can be used to carry the full traffic load of one 100BASE-TX
Ethernet port.
When using VC-12: the 63 VC-12s can be divided as required to create up to

32 virtually concatenated groups. For example, for streaming payload, a
group using 5 VC-12 can be used to carry the full traffic load of a 10BASE-T
Ethernet port over SDH; 50 VC-12 are needed to carry the full traffic load of a
100BASE-TX Ethernet port.
VCG Ports
5-187
For other types of payload, the statistical distribution of the traffic and the
optional use of flow control, reduce the bandwidth requirements in
accordance with the long-term average data rate.
When using VT1.5: the 84 VT1.5s can be divided as required to create up to

32 groups. For example, a group using 7 VT1.5 can be used to carry the full
traffic load of a 10BASE-T Ethernet port over SONET. However, the maximum
number of VT1.5s in any group cannot exceed 64 (this number is sufficient
for carrying the full traffic load of a 100BASE-TX Ethernet port).
When virtual concatenation is not used, one group can be assigned the full VC-4
bandwidth.
It is possible to build several virtually concatenated groups using different types
of VCs/VTs: for example, when using VC-12 to carry E1-i/T1-i traffic, one or two
groups can use VC-3s, and the remaining bandwidth (17 VC-12) can be assigned
to one or two additional virtually concatenated groups.
The routing of the VCG payload is defined by means of mapping (mapping is the
selection of specific VCs/VTs to be used to carry each virtually concatenated
group, in the number needed to provide the required bandwidth). This operation
creates the trails that are needed to connect the local users to remote locations
through the SDH/SONET network.
Support for LCAS

Each virtually concatenated group with two or more VCs/VTs can be configured to
support LCAS.
With LCAS, the capacity of a virtually concatenated group can be hitlessly
decreased when one of the VCs/VTs fails; when the failure is no longer present,
the group will automatically and hitlessly recover to return to the normal capacity.
Another LCAS advantage is that it allows setting up a link even when the number
of VCs/VTs at the two endpoints, or anywhere along the trail followed by the VCG,
is not equal.
The user can specify a minimum number of VCs/VTs for the group capacity: if the
number of VCs/VTs decreases below this minimum, an alarm will be generated.
Factory Defaults
Megaplex-4100 is supplied with all VCG ports disabled.
Configuring VCG Ports
To configure a VCG:
At the config>port>vcg (slot/port)# prompt, enter all necessary commands

according to the tasks listed below:
Task
Command
Comments
Assigning short description to a

VCG port
name <string>
5-188
VCG Ports
Task
Command
Comments
Administratively enabling a VCG

port
no shutdown
Using shutdown disables the VCG port
Binding the corresponding

VC/VT/STS-1 to the VCG port
bind vc4-sts3c
<slot>/<port>/<tributary>
bind vc3-sts1
<slot>/<port>/<au4>/
<tributary>
bind vc-vt <slot>/<port>/
<au4>/<tug_3>/<tug_2>
[/<tributary>]
Enabling the use of the Link

Capacity Adjustment Scheme
(LCAS) on the corresponding
group
lcas
The connection to a VC or VT/STS

depends on the frame selection
(frame=sdh or frame=sonet)
Using no before the corresponding
command removes the binding
LCAS is relevant only when the group

includes 2 or more VCs, and therefore it
is relevant for VC-4 (STS-3c) binding only
when STM-4/OC-12 ports are configured
Using no lcas disables the use of LCAS
Selecting the minimum allowed

number of operational
VC/VT/STSs that must remain in
operation. If the number
decreases below the selected
value, an alarm is generated.
minimum-number-of-links
<value>
This parameter is relevant only when

LCAS is enabled.
Viewing LCAS Status Information

For viewing the LCAS status information, follow the instructions below.
To view the LCAS status information:

1. Navigate to config>port>vcg> (<slot>/<port>)#
Type show status.
VCG Ports
5-189
mp4100>config>port>vcg(cl-a/2)# show status

Name
: CL-A vcg 02
Operation Status
: Up
LCAS Status
: All Normal
Members
--------------------------------------------------------------Link
: cl-a/2/1/1/1/2
Source Status : Norm
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/1/1/3
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/2/2/3
Sink Status
: Norm
Status
: OK
Link
: cl-a/2/1/3/5/1
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/1/2/1
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/2/3/1
Sink Status
: Norm
Status
: OK
Link
: cl-a/1/2/2/5/1
Source Status : EOS
Sink Status
: EOS
Status
: OK
The parameters displayed in the screen are as follows:
Link
Identifies the position of the corresponding VC or VT within the

STM-1/STM-4 or OC-3/OC-12 frame, using the vc4-sts3c/
tug-3/tug-2/tu format.
The Link number also includes the identification of the link,
cl-a/1, cl-a/2, cl-b/1 or cl-b/2.
5-190
VCG Ports
Source
Status
Displays the state of the corresponding VC or VT on the local end

of the path serving the selected virtually concatenated group
(that is, the end located on the Megaplex-4100 to which the
supervisory terminal is connected):
Fixed the end uses the fixed bandwidth (not LCAS)
Add the corresponding VC or VT is about to be added to the
virtually concatenated group
Norm normal transmission state
EOS end-of-sequence indication
Idle the corresponding VC or VT is not part of the virtually
concatenated group, or is about to be removed from the
group
DNU do not use the corresponding VC or VT, for example,
because the sink side reported a failure.
The state is correct at the time the command to display this
screen has been received by the Megaplex-4100.
Sink Status
Same as above for the sink side (remote end of the path).
Status
Displays the member status of the corresponding VC or VT: OK or

Failed
Displaying LCAS Statistics

VCG ports feature the collection of LCAS statistical diagnostics.
To display the LCAS statistics:
At the prompt config>slot>port>vcg (<slot><port>)#, enter show statistics

Task
Command
Comments

statistics

LCAS statistics are displayed. The counters are described in Table 5-46.
For example:
Current Statistics:
VCG Ports
5-191
mp4100>config>port>vcg(cl-a/2)# show statistics current

Current
----------------------------------------------------------------Time Elapsed (Sec)
: 644
Valid Intervals
: 3
Number of Active VCs/VTs
: 4
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0
mp4100>config>port>vcg(cl-a/2)# show statistics interval 2
Interval
----------------------------------------------------------------Interval Number
: 2
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0
Under Minimum Limit Time
: 0
Table 5-45. LCAS Statistics Parameters

Parameter
Description
Time elapsed (Current

statistics only)
Valid Intervals (Current

statistics only)
The number of elapsed finished 15-min intervals for which statistics data can
be displayed, in addition to the current (not finished) interval (up to 96)
Interval number (Selected

interval statistics only)
Number of Active VCs/VTs

(Current statistics only)
Displays the current number of active VCs/VTs reported for the

corresponding VCG
Maximum Number of Active

VCs/VTs
Displays the maximum number of active VCs/VTs reported for the

corresponding VCG during the selected interval.
Minimum Number of Active

VCs/VTs
Displays the minimum number of active VCs/VTs reported for the
Under Minimum Limit Time

(Selected interval statistics
only)
Displays the accumulated time, in seconds, during which the number of

active VCs/VTs for the corresponding VCG has been less than the configured
minimum allowed number.
corresponding VCG during the selected interval.
Clearing Statistics
There are two options for clearing LCAS statistics data:

5-192
VCG Ports
5.25 GFP Ports

To describe Ethernet transport over the SDH/SONET network using GFP
encapsulation, Megaplex-4100 architecture uses an entity named GFP port. GFP
ports exist only on CL.2 modules and represent VCGs (Virtual Concatenation
Groups) with GFP encapsulation. They can be mapped either directly to the
physical layer or to VCG. In the latter case, the binding is done in two stages and
the VCG is further bound to the physical layer.
Standards
GFP Ports comply with ITU-T Rec. G.7041, using the framed mode.
Factory Defaults
Megaplex-4100 is supplied with all GFP ports disabled.
Configuring GFP Ports
To configure a GFP port:

1. Navigate to configure port gfp <slot>/<port> to select the gfp port to
configure.
The config>port>gfp>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
`

port
name <string>
no shutdown
GFP Ports
5-193
Task
Command
Comments
`
Binding the corresponding

VC/VT/STS-1/VCG to the GFP port
bind vc4-sts3c
bind vc3-sts1
<tributary>
<au4>/<tug_3>/<tug_2>
[/<tributary>]
bind vcg <slot>/<port>
The connection to a VC or VT/STS

depends on the frame selection
(frame=sdh or frame=sonet)
You cannot bind both a VCG and a
VC/VT/STS-1 to a GFP port
Enabling payload error detection:

in this case, a frame checksum is
calculated, using the 32-bit
polynomial recommended by
ITU-T, and added to the GFP
frame structure
fcs-payload
Using no fcs-payload disables payload

error detection
Enabling the use of payload data

scrambling in the transmit and
receive directions, before
insertion in frames
scrambler-payload { rx | tx |
rx-tx }
Using no scrambler-payload disables

payload scrambling for both the transmit
and receive directions

to the port

to remove the automatical lvc-eos or
hvc-gfp profile assignement
Displaying GFP Statistics

GFP ports feature the collection of statistical diagnostics.
To display the GFP port statistics:
At the prompt config>slot>port>gfp (<slot><port>)#, enter show statistics

Task
Command
Comments

statistics

5-194
GFP Ports
GFP statistics are displayed. The counters are described in Table 5-46.
For example:
Current Statistics:
mp4100>config>port>gfp(cl-b/6)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec) : 299
Valid Intervals
: 96
Total RX Frames
: 475682
Total RX Frames
: 475681
Idle Frames Error : 237726
cHEC Errors
: 0
tHEC Errros
: 0
eHEC Errors
: 0
FCS Errors
: 0
PTI Mismatch
: 0
EXI Mismatch
: 0
mp4100>config>port>gfp(cl-a/1)# show statistics interval 67
Interval
--------------------------------------------------------------Interval Number
: 67
Total RX Frames
: 1192393
Total RX Frames
: 1192403
Idle Frames Error : 0
cHEC Errors
: 0
tHEC Errros
: 0
eHEC Errors
: 0
FCS Errors
: 0
PTI Mismatch
: 0
EXI Mismatch
: 0
Table 5-46. GFP Statistics Parameters

Parameter
Description

statistics only)

statistics only)

Total Rx Frames
Total number of frames received
Total Tx Frames
Total number of frames transmitted
GFP Ports
5-195
Parameter
Description
Idle Frames Error
Number of idle frames errors.

Idle frame is a special four-octet GFP control frame consisting of only a GFP
Core Header with the PLI and cHEC fields (see 6.1.1 in G.7041) set to 0, and
no Payload Area. The Idle frame is intended for use as a filler frame for the
GFP transmitter to facilitate the adaptation of the GFP octet stream to any
given transport medium where the transport medium channel has a higher
capacity than required by the client signal
Number of cHEC errors.
cHEC Errors
GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Core Header Error Check (cHEC).
Number of tHEC errors.
tHEC Errors
GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Type Header Error Check (tHEC).
FCS Errors
The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
PTI Mismatch
Number of payload Headers with incorrect PTI values
EXI Mismatch
Number of payload Headers with incorrect EXI values
Clearing Statistics
There are two options for clearing GFP statistics data:

5.26 HDLC Ports (CL.2 Modules)

HDLC ports defined on CL.2 modules represent VCGs (Virtual Concatenation
Groups) with LAPS encapsulation. They can be mapped either directly to the
physical layer or to a VCG. In the latter case, the binding is done in two stages
and the VCG is further bound to the physical layer. The maximum total number of
GFP and HDLC ports that can be configured per slot is 32.
5-196
HDLC Ports (CL.2 Modules)
For HDLC ports defined on M8E1, M8T1 and M8SL modules, see HDLC Ports (I/O
Modules).
Standards
HDLC ports in CL.2 modules comply with ITU-T Rec. X.86.
Factory Defaults
Megaplex-4100 is supplied with all HDLC ports disabled.
To configure an HDLC port:

1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short
description to the port
name <string>
the port
no shutdown
Binding the
corresponding
VC/VT/STS-1/VCG to the
HDLC port
bind vc4-sts3c <slot>/<port>/<tributary>

bind vc3-sts1 <slot>/<port>/<au4>/
<tributary>
<au4>/<tug_3>/<tug_2>/
[<tributary>]
bind vcg <slot>/<port>
Assigning user-defined VC
profile to the port
The connection to a VC or VT/STS depends

on the frame selection (frame=sdh or
frame=sonet)
You cannot bind both a VCG and a
VC/VT/STS-1 to a GFP port
Before you assign the user-defined profile,
you must use the no vc command to
remove the automatical hvc-laps or lvc-eos
profile assignement
Displaying HDLC Statistics

HDLC ports of CL.2 modules feature the collection of statistical diagnostics.
5-197
To display the HDLC port statistics:
At the prompt config>slot>port>hdlc (<slot><port>)#, enter show statistics

Task
Command
Comments

statistics

HDLC statistics are displayed. The counters are described in Table 5-47.
For example:
Current Statistics:
mp4100>config>port>hdlc(cl-b/6)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec)
: 430
Valid Intervals
: 96
Total RX Frames
: 569704
Total TX Frames
: 569703
Address Mismatch
: 0
Control Mismatch
: 0
LAPS Sapi Mismatch
: 0
FCS Errors
: 0
Abort Frames
: 0
Minimum Length Violation : 0
Maximum Length Violation : 0
5-198
mp4100>config>port>sdh-sonet(cl-a/1)# show statistics interval

67
Interval
--------------------------------------------------------------Interval Number
: 67
Total RX Frames
: 1192393
Total RX Frames
: 1192403
Address Mismatch
: 0
Control Mismatch
: 0
LAPS Sapi Mismatch
: 0
FCS Errors
: 0
Abort Frames
: 0
Minimum Length Violation : 0
Maximum Length Violation : 0
Table 5-47. HDLC Statistics Parameters

Parameter
Description

statistics only)

statistics only)

Total Rx Frames
Total number of frames received
Total Tx Frames
Total number of frames transmitted
Address Mismatch
The number of frames with wrong address value (the correct value of
Address byte in LAPS Overhead is 0x4)
Control Mismatch
The number of frames with wrong control value (the correct value of Control
byte in LAPS Overhead is 0x3)
LAPS Sapi Mismatch
The number of frames with wrong SAPI value (the correct value of SAPI byte
in LAPS Overhead is 0xF0E1)
FCS Errors
The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
Abort Frames
The number of abort frames received (a packet can be aborted by inserting

the abort sequence, 0x7d7e. Reception of this code at the far end will cause
the receiver to discard this frame)
Minimum Length Violation
Maximum Length Violation
Clearing Statistics
There are two options for clearing HDLC statistics data:
5-199

5.27 Managers
This section explains how to add and remove managers.
Configuring a Manager
This section explains how to add and remove managers. You can add up to 10
managers.
To add a manager:
1. At the config# prompt, enter manager.
The config>mngmnt# prompt appears.
At the config>mngmnt# prompt, enter manager <0.0.0.0..255.255.255.255>.
The specified manager has been added and the
config>mngmnt>manager <0.0.0.0..255.255.255.255> prompt appears
displaying the IP address of the manager you just added.
To remove a network manager:
To delete a manager, in the management context (config>mngmnt), enter no

manager <ip-address>/<ip-mask>
To delete all managers, enter no manager.
5.28 Management Access

You can enable or disable access to the Megaplex-4100 management system via
Telnet, SSH, or SNMP applications for a specific router interface. By disabling
Telnet, SSH, or SNMP, you prevent unauthorized access to the system when
security of the associated IP address has been compromised. When Telnet, SSH,
and SNMP are disabled, Megaplex-4100 cannot be managed using the relevant
router interface. If Telnet, SSH and SNMP are disabled for all router interfaces,
5-200
Management Access
the unit can be managed via an ASCII terminal only. In addition, you can limit
access to the device to only the defined management stations.
In addition, Megaplex-4100 can use up to four RADIUS servers to facilitate
remote authentication. Introducing a RADIUS server allows configuring up to two
authentication protocols according to a user-configured order. If the first
authentication method is unavailable or the user is not found, the next method is
used.
The table below lists management access implementation, according to the
defined management access and whether network managers are defined.
Access Method
Mode
Telnet Access
SSH Access (Secure Shell)
SNMP Access
Allowed to Access Megaplex-4100

Network Manager(s)
Defined
Network Manager(s)
not Defined
Enable
Anybody
Anybody
Disable
Nobody
Nobody
Enable
Anybody
Anybody
Disable
Nobody
Nobody
Enable
Anybody
Anybody
Disable
Nobody
Nobody
Configuring Access
Follow the instructions below to enable/disable access via Telnet, SSH or SNMP. In
addition, you have to configure the access policy
To enable or disable access via management protocols:

Configure as illustrated and explained in the table below.
Task
Command
Enabling access via Telnet
telnet
Disabling acess via Telnet
no telnet
Enabling access via Secure Shell (SSH)
ssh
Disabling access via SSH
no ssh
Enabling access via SNMP
snmp
Disabling access via SNMP
no snmp
Comments
To define the access policy:
At the config>mngmnt>access# prompt, configure the access levels as

illustrated and explained in the table below.
Management Access
5-201
Task
Command
Comments
Specifying authentication
preferably via database
stored on RADIUS server,
then optionally local
auth-policy 1st-level radius [2nd-level

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

authentication is performed via the
RADIUS server. If the RADIUS server
does not answer the authentication
request, then Megaplex-4100
authenticates via the local database. If
the RADIUS server rejects the
authentication request, Megaplex-4100
ends the authentication process.
If 2nd-level is set to none,
authentication is performed via the
RADIUS server only
5.29 SNMP Management

SNMP stands for Simple Network Management Protocol and is an application
layer protocol that provides a message format for the communication between
managers and agents. SNMP systems consist of an SNMP manager, an SNMP
agent and a MIB. The NMS can be part of a management network system. To
configure SNMP, you have to define the relationship between the manager and
the agent. Megaplex-4100 supports SNMPv3, the latest SNMP version to date.
SNMPv3 provides secure access to devices in the network such as Megaplex units
by using authentication and data encryption.
Standards
This section states the standards that the supported SNMP versions are based
on.
5-202
RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working

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

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

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

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

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

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

Network Management Protocol (SNMPv2). SNMPv2 Working Group.
SNMP Management
RFC 1908, Coexistence between Version 1 and Version 2 of the Internetstandard Network Management Framework. SNMPv2 Working Group.
RFC 2104, Keyed Hashing for Message Authentication.
RFC 2271, Architecture for Describing SNMP Management Frameworks.
RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP).
RFC 2273, SNMPv3 Applications.
RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3).
RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP).
RFC 3412, Version 3 Message Processing and Dispatching.
RFC 3414, User-based Security Model for SNMPv3
RFC 3416, Update for RFC 1904.
Benefits
The SNMP protocol allows you to remotely manage multiple units from a central
work station using RADview EMS. RADview EMS offers a graphical user interface
that resembles the front panel of your unit with its interfaces and LEDs.
Megaplex-4100 supports SNMPv3, which allows data to be collected securely
from SNMP devices. Confidential information such as SNMP commands can thus
be encrypted to prevent unauthorized parties from being able to access them.
In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which reports information via SNMP back to the
managing systems.
get_request
get_response
get_next_request
get_response
set_request
Work Station with
RADview
(SNMP Manager)
Megaplex Unit
(MIB, SNMP Agent)
get_response
traps
Figure 5-30. SNMP Network Scheme
SNMP Management
5-203
The SNMP agent contains MIB variables whose values the SNMP manager can
request or change. A manager receives/transmits a value from/to an agent. The
agent gathers data from the MIB (Management Information Base). A MIB module
is actually the store for data on network and device parameters. In addition, the
agent may set or get data according to manager commands. Commands are used
to send and receive data as follows:
get. Retrieving specific management information.
get-next. Retrieving management information via traversal
set. Manipulating management information.
get-response. Sent by an agent to respond to any of the above.
trap. Messages on events such as improper authentication, link status,

loss/restoration of connections etc, sent by the agent to notify the manager
of the current conditions.
SNMP Message Formats

Megaplex-4100 supports SNMPv1, SNMPv2c and SNMPv3. The SNMP message
formats of those three standards are illustrated below. Additional SNMPv2
formats exist, but are not supported by Megaplex-4100.
SNMPv1 Message Format

The SNMP general message format was originally used to define the format of
messages in the original SNMP Protocol (SNMPv1), and was therefore relatively
straight-forward.
The general message format in SNMPv1 is a wrapper that consists of a small
header and an encapsulated PDU as illustrated and explained below.
There are not many header fields needed in SNMPv1 because of the simple
nature of the community-based security method in SNMPv1.
Table 5-48. SNMPv1 Header Fields

Field Name
Syntax
Size (Bytes)
Description
Version
Integer
Version Number. Describes the SNMP version number of

this message; used for ensuring compatibility between
versions. For SNMPv1, this value is 0.
Community
Octet string
Variable
Community String. Identifies the SNMP community in which

the sender and recipient of this message are located. This
is used to implement the simple SNMP community-based
security mechanism.
PDU
--
Variable
Protocol Data Unit. The PDU is communicated at the body

of the message.
5-204
SNMP Management
16
32
Version Number = 0
Community String
PDU Control Fields
Message Body (PDU)

PDU Variable Bindings
Figure 5-31. SNMPv1 General Message Format
SNMPv2c Message Format

Amongst various approaches to introduce SNMPv2, SNMPv2c was the most
accepted one. Its architecture is identical to SNMPv1 except for the version
number, which is 1 instead of 0. 0 is the version number for SNMPv1.
SNMPv3 Message Format

SNMPv3 adds security methods and parameters and completes the respective
approach that has been started with SNMPv2, but did not lead to a common
standard. This standard has been established with SNMPv3.
The significant changes made in SNMPv3 include a more flexible way of defining
security methods and parameters, to allow the coexistence of multiple security
techniques.
The general message format for SNMPv3 still follows the idea of an overall
message wrapper that contains a header and an encapsulated PDU, but it has
been significantly refined. The fields in the header have been divided into those
dealing with security and those not dealing with security. The non-security fields
are common to all SNMPv3 implementations, while the use of the security fields
can be tailored by each SNMPv3 security model, and processed by the module in
an SNMP entity that deals with security. The entire processing in SNMPv3 is
described in RFC 3412.
For a detailed illustration and explanation, refer to the figure and the table
below.
SNMP Management
5-205
16
32
Message Version Number = 3

Message Identifier
Maximum Message Size
Message Security Model
(bytes 1 to 3)
Message Flags
Message Security
Model (byte 4)
Message Security Parameters
Context Engine ID
Context Name
Scoped PDU
PDU Control Fields
Message Body (PDU)
PDU Variable Bindings
Reserved
Reportable
Flag
Privacy
Flag
(Priv)
Authentication
Flag
(Auth)
Figure 5-32. SNMPv3 General Message Format
5-206
SNMP Management
Table 5-49. SNMPv3 General Message Format

Field Name
Syntax
Size (Bytes)
Description
Msg Version
Integer
Message Version Number. Describes the SNMP version

number of this message; used for ensuring compatibility
between versions. For SNMPv3, this value is 3.
Msg ID
Integer
Message Identifier. A number used to identify an SNMPv3

message and to match response messages to request
messages. This field was created to allow the matching at
the message processing level to protect against certain
security attacks regardless of the PDU content. Thus, Msg
ID and Request ID are used independently.
Msg Max Size
Integer
Maximum Message Size. The maximum size of message that

the sender of this message can receive. Minimum value of
this field is 484.
Msg Flags
Octet String
Message Flags. A set of flags tcontrols processing the

message. the substructure of this field is illustrated in
Table 5-50.
Msg Security
Model
Integer
Message Security Model. An integer value indicating which

security model was used for this message. For the userbased security model (default), this value is 3.
Msg Security
Parameter
--
Variable
Message Security Parameters. A set of fields that contain

parameters required to implement the respective security
model for this message. The contents of this field are
specified in every document that describes an SNMPv3
security model. For example, the parameters for the userbased model are defined in RFC 3414.
Scoped PDU
--
Variable
Scoped PDU. Contains the PDU to be transmitted along

with parameters that identify an SNMP context, which
describes a set of management information accessible by a
particular entity. The PDU is referred to as scoped
because it is applied within the scope of this context. This
field may or may not be encrypted, depending on the value
of the Private Flag. The structure of the PDU field is
illustrated in Table 5-51.
Table 5-50. SNMPv3 Message Flag Substructure

Field Name
Size (Bytes)
Reserved
5/8 (5 bits)
Reserved. For future use
Reportable Flag
1/8 (1 bit)
Reportable Flag. If set to 1, a device receiving this message has

to return a Report-PDU whenever conditions arise that require
such a PDU to be generated.
Priv Flag
1/8 (1 bit)
Privacy Flag. If set to 1, it indicates that the message was

encrypted to ensure its privacy.
SNMP Management
5-207
Field Name
Size (Bytes)
Auth Flag
1/8 (1 bit)
Authentication Flag. If set to 1, it indicates that authentication

was used to protect the authenticity of this message.
Table 5-51. Structure of the PDU Field

Field Name
Syntax
Size (Bytes)
Description
Context Engine ID
Octet String
Variable
Context Engine ID. Used to identify to which

application the PDU will be sent for processing.
Context Name
Octet String
Variable
Context Name. An object identifier specifying the

particular context associated with this PDU.
PDU
--
Variable
PDU. The protocol data unit being transmitted.
The SNMPv3 Mechanism

SNMPv3 uses the basic SNMP protocol and adds the following security
functionalities:
Message integrity. Ensuring that the package has not been tempered with
during transmission.
Authentication. Verifying that the message comes from a valid source.
Encryption. Preventing snooping by unauthorized sources.
SNMPv3 does not refer to managers and agents, but to SNMP entities. Each
entity consists of an SNMP engine and one or more SNMP components. The new
concepts define an architecture that separates different components of the
SNMP system in order to make a secure implementation possible. The SNMPv3
components are explained in the following sections.
The SNMPv3 Engine

The SNMPv3 engine consists of four subsystems that address authentication and
access authorization.
5-208
Dispatcher. Sending and receiving messages. It tries to determine the SNMP

version of each message (SNMPv1, SNMPv2c or SNMPv3) once it is handed
over to the message processing subsystem.
Message processing subsystem. Prepares messages to be sent and extracts

data from received messages.
Security subsystem. Provides authentication and privacy services. The

authentication uses either community strings to support SNMP Versions 1 and
2, or user-based authentication for SNMPv3. SNMPv3 user-based
authentication uses the MD5 or SHA algorithms to authenticate users without
sending a clear password. The privacy service uses the DES algorithm to
encrypt and decrypt SNMP messages. Currently, DES is the only algorithm
used, though others may be added in the future.
Access control system. Managing the access control to MIB objects. You can
define objects that a user can access as well as operations that a user is
allowed to perform on those objects. For example, you may grant read-write
SNMP Management
access to certain parts of the MIB-2 tree, while allowing read-only access to
the remaining parts of the tree.
SNMPv3 Components
SNMPv3 consists of components that deal with receiving/issuing requests,
generating traps etc. These commands are listed and explained below.
Command generator. Generates the Get, Get-Next, Get-Bulk requests, Set

requests, and processes the responses. This application is implemented by an
NMS to issue queries and set requests against entities on routers, switches,
Unix hosts etc.
Command responder. Responds to Get, Get-Next, Get-Bulk requests. The

command responder is implemented by the SNMP agent.
Notification originator. Generates SNMP traps and notifications. This

application is implemented by an entity on a router or host.
Proxy forwarder. Facilitates the passing of messages between entities.
RFC 2571 allows additional applications to be defined over time, which is a

significant advantage over the older SNMP versions. The figure below illustrates
how the components fit together creating an entity.
SNMP Entity
SNMP Engine (idntified by SnmpEngineID)
Message
Processing
Subsystem
Dispatcher
Security
Subsystem
Access
Control
Subsystem
SNMPv3 Components
Command Generator
Notification Receiver
Proxy Forwarder
Command Responder
Notification Originator
Other
Figure 5-33. SNMPv3 Entity
Factory Defaults
By default, SNMPv1 is enabled. SNMPv2c and SNMPv3 are disabled.
Configuring for SNMP Management

Before configuring SNMPv3, you should specify an SNMPv3 engine.
Specifying an SNMPv3 Engine

By default, the SNMPv3 engine ID config type is set to MAC-address. To use a
different ID config type, refer to the instructions below.
SNMP Management
5-209
To specify the SNMP engine ID config type:

1. At the config>mngmnt# prompt, enter snmp.
The config>mngmnt>snmp# prompt appears.
At the config>mngmnt>snmp# prompt, enter snmp-engine-id {mac<MAC
address>|ip4 <IP address>|text <string>}.
The SNMP engine ID config type ID is specified.
Note
If you use the CL.2 protection, the SNMP engine ID must be identical for both the
working card and the protection card, which means that you have to assign the
same MAC address or IP address etc. to both cards.
To enter the SNMP engine ID string:
At the config>mngmnt>snmp# prompt, enter snmp-engine-id-string <string

of up to 27 alphanumeric characters>.
The SNMP engine ID is specified and SNMPv3 can be enabled and
configured.
Enabling SNMPv3
To enable/disable SNMPv3:
To enable the SNMPv3 engine, at the config>mngmnt>snmp# prompt, enter

snmpv3.
The SNMPv3 engine is enabled.
To disable the SNMPv3 engine, at the config>mngmnt>snmp# prompt, enter

no snmpv3.
The SNMPv3 engine is disabled.
Specifying an SNMPv3 User
To specify an SNMPv3 user:
After SNMPv3 has been enabled, at the config>mngmnt>snmp# prompt,

enter the following, depending on the SNMPv3 authentication protocol used:
Task
Command
Comments
Adding a user who

authenticates using the
MD5 protocol.
user <security-name>
[md5-auth [{des|none}]]
security name. The user specific security

name, consisting of up to 32 alphanumeric
characters.
md5-auth. MD5 authentication protocol.
des. Using the DES privacy protocol.
none. No privacy protocol used.
sha-auth. SHA authentication protocol.
Adding a user who

authenticates using the
SHA protocol.
5-210
SNMP Management
[sha-auth [{des|none}]]
Task
Command
Comments
Adding a user who does

not authenticate.
[none-auth]
Removing a user
no user <security-name>
none-auth. No authentication performed.
To deactivate a user:
1. At the config>mngmnt>snmp# prompt, enter user <security name>.
The config>mngmnt>snmp>user(<security name>)# prompt appears.
Enter shutdown.
The user is deactivated but remains available.
Defining User (Access) Groups

Megaplex-4100 supports up to 10 SNMPv3 managers with different authorization
and privacy tributes.
To define and remove an SNMP access group:
At the config>mngmnt>snmp# prompt, enter the following:

access-group <group-name> {snmpv1 |snmpv2c | usm} {no-auth-no-priv |
auth-no-priv | auth-priv}
The config>mngmnt>snmp>access-group(<group name>/<snmpv1 |
snmpv2c | usm>/<no-auth-no-priv|auth-no-priv|auth-priv>)# prompt
appears.
Task
Command
Comments
Defining an access
group
access-group <group-name> {snmpv1

|snmpv2c | usm} {no-auth-no-priv |
auth-no-priv | auth-priv}
group name. Identifies the access

group.
snmpv1, snmpv2c, usm. Security

model for the SNMP messages.
usm. User based security model
no-auth-no-priv. Authorization and

privacy are disabled, lowest level of
security for generating SNMP
messages.
auth-no-priv. Authorization enabled,

privacy disabled.
auth- priv. Authorization and privacy

disabled, highest level of security for
generating SNMP messages.
Removing an access
group
no access-group <group-name>
{snmpv1 |snmpv2c | usm}
{no-auth-no-priv | auth-no-priv | authpriv}
SNMP Management
5-211
To configure the access criteria for the SNMP access group:
At the config>mngmnt>snmp>access-group(<group
name>/<snmpv1|snmpv2c|usm>/<no-auth-no-priv|auth-no-priv|auth-priv>)#
prompt, enter the following;
Task
Command
Comments
context-match {exact|prefix}
exact. In order to gain access rights,

the group name must match exactly
the value of the instance of this
project.
prefix. The group name must match

partially the value of the instance of
this project.
Specifying the read view of the

access group
read-view <name>
Specifying the write view of the

access group
write-view <name>
Specifying the notify view of the

access group
notify-view <name>
To define the access control policy for users:
At the config>mngmnt>snmp# prompt, enter the following:
Task
Command
Comments
Linking a user to a security

model
security-to-group {any | snmpv1 | snmpv2c |

usm} sec-name {security-name}
security name. The user

specific security name.
snmpv1, snmpv2c, usm.

Security model for the
SNMP messages as
explained previously.
any. Any security model is

allowed for the relevant
access group.
Removing the link of a user

to a security model
no security-to-group {any | snmpv1 |

snmpv2c | usm} sec-name {security-name}
Setting up a View
To define a view:
At the config>mngmnt>snmp# prompt, enter parameters as illustrated and

explained below.
The mngmnt>snmp>view(<view name>/<subtree OID>)# prompt appears.
Task
Command
Assigning a name and an

object ID to the view
view <view name> <subtree OID>
5-212
SNMP Management
Comments
Task
Command
Removing the view
no view <view name> <subtree OID>
Comments
To configure the view you previously defined:
At the config>mngmnt>snmp>view(<view name>/<subtree OID>)# prompt,

enter parameters as illustrated and explained below.
Task
Command
Comments
Enabling the view
no shutdown
Disabling the view
shutdown
Masking a view
mask <mask name>
Including, excluding the

view.
type {included | excluded}
The view is disabled, but remains

available.
Mapping SNMPv1 to SNMPv3

Megaplex-4100 supports coexistence of different SNMP versions by mapping
SNMPv1/SNMPv2 community names to the SNMPv3 security name values. The
mapping is performed according to the RFC 3584 requirements.
To set up an SNMPv3 community:
At the config>mngmnt>snmp# prompt, enter parameters as illustrated and

explained below.
The config>mngmnt>snmp>community(<community-index>)# prompt
appears.
Task
Command
Comments
Defining a community
community <community-index>
community-index. Free text, consisting

of up to 32 alphanumeric characters.
Removing a community
no community <community-index>
To map an SNMPv1/SNMPv2 community to SNMPv3:
At the config>mngmnt>snmp>community(<community-index>)# prompt,

enter parameters as illustrated and explained below.
Task
Command
Comments
Specifying the SNMPv1/SNMPv2

community name for which the
information is presented.
name <community-string>
community-string. Free text,

consisting of up to 32 alphanumeric
characters.
Specifying the SNMPv3 security name

to be mapped to the SNMPv1/SNMPv2
community name
sec-name <sec-name>
sec-name. Free text, consisting of

up to 32 alphanumeric characters
Activating the community
no shutdown
SNMP Management
5-213
Task
Command
Comments
De-activating the community
shutdown
The community is de-activated, but

remains available.
Specifying a set of the transport

endpoints that are used in either of
the following methods:
tag <transport-tag>
As defined for each target
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.
Configuring Targets
A target is a network management station to which Megaplex-4100 should send
trap notifications over SNMPv3. A set of parameters must be configured and
assigned to each target. Then, each target must have a valid IP address and IP
mask. In addition, a previously configured parameter set and notification tags
must be assigned to the target.
To configure a target, you have to first configure a parameter set that you will
have to attach to the relevant target when it is being configured.
To configure a target parameter set:
At the config>mngmnt>snmp# prompt, enter target-params <params-name>.

The config>mngmnt>snmp>target(<params-name>)# prompt appears and
the target parameters can be set as illustrated and explained below.
The target parameter set you configure must be attached to the relevant
target as explained on the next page.
Task
Command
Defining the message

preprocessing model to be used
when generating SNMP
messages.
message-processing-model {snmpv1 |
snmpv2 | snmpv3}
5-214
SNMP Management
Comments
Task
Command
Comments
Specifying the security level to

be used when generating SNMP
messages.
security [name <security-name>][level

{no-auth-no-priv|auth-no-priv | auth-priv}]
security-name. Free
text, consisting of up to
32 alphanumeric
characters.
no-auth-no-priv. No
authentication, no
privacy
auth-no-priv.
Authentication, no
privacy
auth-priv.
Authentication and
privacy
usm. User based

security model
Specifying the SNMP version

(security model)
version { snmpv1 | snmpv2c | usm}
To configure the target:
At the config>mngmnt>snmp# prompt, enter target <name>.

The config>mngmnt>snmp>target(<name>)# prompt appears and the
target parameters can be set as illustrated and explained below.
Task
Command
Comments
Identifying the
target NMS
address udp-domain <0.0.0.0..255.255.255.255>
You have to enter the domain

and the IP address or the OAM
port, depending on whether
the target NMS belongs to a
UDP domain or an OAM
domain.
address oam-domain <oam-port>
Activating the
transmission of
SNMP message to
the target NMS
no shutdown address
Deactivating the
transmission of
SNMP message to
the target NMS
shutdown address
Selecting a tag from

the list of previously
defined notification
tags.
tag-list <list>
Configuring SNMP Communities for SNMPv1

This section instructs you on setting up read-, write-, and trap communities for
SNMPv1.
SNMP Management
5-215
To set up communities:
Make sure that SNMPv3 is disabled and at the

Megaplex-4100>config>mngmnt>snmp# prompt, define the desired
community as illustrated and explained below.
Task
Command
Comments
Defining a read community
community read <name>
Assign a name consisting of up to 20

alphanumerical characters.
Defining a write community
community write <name>

Defining a trap community
community trap <name>

Note
The names you assign to the communities are case sensitive.
Adding SNMPv3 Notification Entries

You can define which types of notification will be sent to previously configured
target management stations as explained under Configuring Targets.
To define and enable a notification entry:

1. At the config>mngmnt>snmp# prompt, enter notify <notify_name>.
The config>mngmnt>snmp>notify(<notify_name>)# prompt appears.
Configure the notification entries as illustrated and explained in the table below.
Task
Command
Assigning a single tag

value to the notification
used to identify the
notification entry when
configuring the target
tag <name>
Associating traps with the

notification entry
bind {<trap name> or <list of traps names>}
Activating the notification

entry
no shutdown
De-activating the
notification entry
shutdown
Comments
You can associate

one or more traps to
the notification
entry
To disable notification:
At the config>mngmnt>snmp# prompt, enter no notify <notify_name>.

The notification is disabled.
5-216
SNMP Management
Configuring a Notification Filter

You can customize a notification filter view as explained below.
To set up a notification filter:

1. At the config>mngmnt>snmp# prompt, define a notification filter and assign
a name and an object ID (sub-tree-oid) to it by entering
notify-filter <name> <sub-tree-oid>.
The config>mngmnt>snmp>notify-filter(<name>/<sub-tree-oid>) prompt
appears.
name. Refers to the name of the notify filter.
sub-tree-oid. Refers to the MIB subtree, which defines a family of

subtrees included in or excluded from the filter profile, if combined with
the corresponding instance of snmpNotifyFilterMask.
Configure the notification filter as illustrated and explained in the table below.
Task
Command
Activating the notification filter
no shutdown
De-activating the notification filter
shutdown
Defining if the notification filter includes

or excludes specific notifications.
type {included|excluded}
Masking the notification filter
Comments
included. The subtrees defined by

sub-tree-oid are included in the
notification profile.
excluded. The listed subtrees by

sub-tree-oid excluded from the
notification profile.
mask
Configuring a Notification Filter Profile

You can customize the notification view as explained below.
To define a notification filter profile:

1. At the config>mngmnt>snmp# prompt, enter
notify-filter-profile <params-name>.
The config>mngmnt>snmp>filter-profile# prompt appears. params-name.
refers to the name of the profile notification parameter set.
Configure the notification filter profile as illustrated and explained in the table
below.
Task
Command
Comments
Assigning a name to the notification

profile
profile-name <name>
Refers to the name of the profile

itself
Enabling the notification filter profile
no shutdown
Disabling the notification filter profile
shutdown
SNMP Management
5-217
Linking User (Access) Groups to an Access Control Policy
To create a user group linked to a specific access control policy:

1. At the config>mngmnt>snmp# prompt, enter security-to-group <any | snmpv1
| snmpv2c | usm> sec-name <security name>.
The config>mngmnt>snmp>security-togroup(<any|snmpv1|snmpv2c|usm>/<security name>)# prompt appears.
Enter group-name <group name>.
The current user is linked to the group.
Repeat steps 1 and 2 for another user with the same security-to-group setting.
A user group consisting of two users linked to the same security model
has been created.
To disable a user group:
At the config>mngmnt>snmp>security-to-group(<any|snmpv1|snmpv2c|usm>/
<security name>)# prompt, enter shutdown.
The user group is disabled.
To enable a user group again:
At the config>mngmnt>snmp>security-to-group(<any|snmpv1|snmpv2c|usm>/
<security name>)# prompt, enter no shutdown.
The user group is enabled.
5.30 Authentication via RADIUS Server

Megaplex-4100 provides connectivity to up to four Radius authentication servers.
You have to specify access parameters such as assigning Radius server IDs,
specifying the associated server IP addresses and the number of retries.
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS).
RFC 2618, RADIUS Authentication Client MIB.
Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network.
Because of its generic nature, the RADIUS protocol can easily be used by service
providers and enterprises to manage access to the Internet, internal networks,
wireless networks, and integrated e-mail services. These networks may
incorporate DSL, access points, VPNs, network ports etc.
5-218
Authentication via RADIUS Server
A work station attempts to log on to a Megaplex unit, which in turn submits an
authentication request to the RADIUS server.
The password is not transmitted over the network. A hash code is generated over
it instead and a previously defined shared secret (string of free text) between the
RADIUS server and the Megaplex unit is transmitted.
Verifying credentials and privileges via RADIUS data base
Logon request to MP-4100
Network
Logging on to MP-4100 or
returning authentication error
MP-4100
Management Work Station
Access accepted or denied
RADIUS Server
Shared Secret
Figure 5-34. RADIUS Server Operation Scheme

The RADIUS server verifies the user information against a database stored at the
RADIUS server. The RADIUS server replies in one of the following ways:
Access Rejected. Access to all resources denied.
Access Accepted. Access to the requested network resources granted.
Factory Defaults
Description
Default Value
The max number of authentication attempts.
Time interval between two authentication attempts.
2 seconds
UDP port used for the authentication channel
1812
Configuring the RADIUS Server

Megaplex-4100 provides connectivity to up to four Radius authentication servers.
You have to specify access parameters such as assigning Radius server IDs,
specifying the associated server IP addresses and the number of retries.
This section explains how to define and configure a RADIUS server, activate and
de-activate it.
To define a Radius server:

1. At the config>mngmnt# prompt, enter radius.
The config>mngmnt>radius# prompt appears.
Enter server <1..4>.
The config>mngmnt>radius>server <1..4># prompt appears.
Define the parameters for the relevant Radius server as illustrated and explained
in the table below.
5-219
Task
Command
Assigning an IP address to the server
address <1.1.1.1..255.255.255.255>
Defining a non-disclosed string (shared

secret) used to encrypt the user password.
key <string of free text>
Defining the number of authentication

request attempts
retry <0..10>
Defining the period of time during which

Megaplex-4100 waits for a response from the
RADIUS server.
timeout <1..5>
Specifying the UDP port used for the

authentication channel
auth-port <1..65535>
Viewing the RADIUS Server Profile Status

This section explains how to display the status of the RADIUS servers.
To display the RADIUS server profile status:
At the config>mngmnt>radius# prompt, enter show status.

The status of the four RADIUS server entries appears regardless if they
are configured and enabled or not.
mp4100>config>mngmnt>radius# show status

Server
IP Address
Access Status
----------------------------------------------------------------------------1.
172.17.143.3
Enable Connected
2.
0.0.0.0
Disable
Not connected
3.
0.0.0.0
Disable
Not connected
4.
0.0.0.0
Disable
Not connected
mp4100>config>mngmnt>radius#
Viewing RADIUS Statistics

This section explains how to display RADIUS sever statistics.
To display RADIUS statistics:
At the config>mngmnt>radius# prompt, enter show statistics.

RADIUS statistics appear as illustrated below.
5-220
mp4100>config>mngmnt>radius# show statistics

Server1
Server2 Server3 Server4
--------------------------------------------------------------Access Requests
: 0
0 0
0
Access Retransmits : 0
0 0
0
Access Accepts
: 0
0 0
0
Access Rejects
: 0
0 0
0
Access Challenges : 0
0 0
0
Malformed Response : 0
0 0
0
Bad Authenticators : 0
0 0
0
Pending Requests
: 0
0 0
0
Timeouts
: 0
0
0 0
Unknown Types
: 0
0 0
0
Packets Dropped
: 0
0 0
0
5.31 Out-Of-Band Ethernet Control

The out-of-band Ethernet port is an Ethernet port dedicated to management
traffic.
All the CL.2 modules have a CONTROL ETH port with a 10BASE-T/100BASE-TX
Ethernet interface. This interface supports MDI/MDIX crossover, and therefore the
port can always be connected through a straight (point-to-point) cable to any
other type of 10/100BASE-T Ethernet port (hub or station).
The CL.2 Ethernet management port supports IP communications, using the host
IP address of the Megaplex-4100 management subsystem.
The CONTROL ETH ports of both CL modules can be simultaneously connected to
the same LAN, through standard Ethernet hubs or switches.
To support out-of-band management, management stations, Telnet hosts, etc.
can be attached to the same LAN, or to any LAN from which IP communication
with the CL.2 module Ethernet ports is possible.
Benefits
Configuring a dedicated management port eliminates the possibility of
management traffic reducing bandwidth and/or causing interruptions in the
traffic flow caused by the management.
Configuring the Out-Of-Band Management Port

Follow the instructions in Management Ethernet Ports.
5.32 Switched Virtual Interface

A switched virtual interface (SVI) is a VLAN of switch ports represented by one
interface to a routing or bridging system. There is no physical interface for the
Switched Virtual Interface
5-221
VLAN, and the SVI provides the Layer 3 processing for packets from all switch
ports associated with the VLAN.
There is one-to-one mapping between a VLAN and SVI, thus only a single SVI can
be mapped to a VLAN.
In Megaplex-4100, an SVI port is an intermediate Ethernet entity between the
Bridge/Router and another Ethernet port (bound one-to-one). It also serves as an
ingress or egress port for terminating management flows. The flow is configured
between the physical port, which is the management source, and the
corresponding SVI port bound to the bridge port. This flow will classify the
management traffic to be forwarded to the bridge port. For illustration, see
Example under Management Bridge.
You can enable and operate a switched virtual interface (SVI port) as explained
below.
To define an SVI port:
At the config>port# prompt, enter svi <port number>.

The config>port>svi <port number># prompt appears and the relevant SVI
port is defined.
To administratively enable an SVI port:
At the config>port>svi<port number># prompt, enter no shutdown.

The SVI port is administratively enabled.
To administratively disable an SVI port:
At the config>port>svi<port number># prompt, enter shutdown.

The SVI port is administratively disabled.
5.33 Management Bridge

Megaplex-4100 management tasks are organized as shown in Figure 5-35. The
diagram shows the unaware management bridge, the management router and
their interconnections with management flows.
Router 1 basic functionality is in connecting to control management stations
(such as PC) and accessing the Common Logic.
Note
5-222
There are two routers in the MP-4100 architecture: Router 1 is used for inband
management, while Router 2 is used for pseudowire routing. Router 2 is
explained in the Pseudowire Router section.
Management Bridge
mng-ethernet cl-b/1
Bind ETH to BP
Bind SVI to BP
Int
Int
BP#9999
PPP
DCC
BP
BP
Logical
MAC
SVI
Logical
MAC
GFP
SVI
GFP
VCG
Part of Factory default
PPP
DTS
SVI#9999
BP
SVI
ETH
VCG
User Flows
PPP
DTS
BP#1
SVI#2
PCS 3/1
(Host)
Router #1
Unaware
Bridge
MNG Flows
Int
Host
BP#9997
Int
BP#9998
flow #2
(tag with mng VLAN)
mng-ethernet cl-a/1
RI#9999
flow #1
(untag mng VLAN)
ETH
Ethernet port physical or logical
ETH
Ethernet Control port
DTS
P2P IP connection
(DCC or DTS)
Unnumbered Router interface
Logical MNG data flow
Figure 5-35. Management Connectivity Diagram

Megaplex-4100 features one unaware bridge that is used for management. The
entities encircled with a dotted line in the diagram are created automatically by
the system and are in no shutdown state by default. These entities include the
control ports of both CL.2 modules that must be permanently bound to the
Management Bridge. For this purpose, Bridge ports #9997 and #9998 are created
and included into the default configuration file. A chain connecting the
management bridge to the management router must also be permanently
connected. For this purpose BP#9999, SVI#9999 and RI#9999 are also created
and included into the default configuration file.
The following table summarizes the default configuration file entities and their
automatically assigned ID numbers, which you can change later, if needed.
Table 5-52. Default Configuration File Entities

Entity
Number
Router 1 interface
9999
Bridge port connecting the management bridge to

the management router
9999
SVI port connecting the router interface to the

bridge
9999
Management Bridge
5-223
Entity
Number
Bridge port connecting the Bridge to the

Management Ethernet port 1 of CL-A module
9997
Bridge port connecting the Bridge to the

Management Ethernet port 1 of CL-B module
9998
The default configuration file looks as follows:

port svi 9999 no shutdown
port mng-ethernet cl-a/1 no shutdown
bridge 1 port 9999 no shutdown
bridge 1 port 9999 bind svi 9999
bridge 1 port 9997 bind mng-ethernet cl-a/1
bridge 1 port 9998 bind mng-ethernet cl-b/1
router 1 interface 9999 bind svi 9999
Other entities should be created by binding the Logical Mac/user Ethernet ports
of all types to the bridge ports via the SVI ports.
Management traffic flowing through Ethernet connections is normally assigned a
dedicated VLAN. Within the Megaplex-4100, inband management traffic can reach
the management subsystem on the CL modules through Ethernet ports, PCS, GFP,
MLPPP port or virtually concatenated groups carrying Ethernet traffic.
To add each of these ports to the bridge, an associated SVI port should be added
and bound to these ports on one side and to the bridge (via corresponding
bridge ports used for Layer 2 management) on the other. A flow should be
configured between the physical port which is the management source and the
corresponding SVI port bound to the bridge port. This flow will classify the
management traffic to be forwarded to the bridge port.
The total number of bridge ports for management is 96. Accordingly, the
maximum number of SVI ports that can be configured is also 96.
Note
Router 2 (pseudowire) has 100 additional SVI ports.

Ethernet and PCS ports are directly bound to the SVI ports, while all the other
entities (GFP, MLPPP, VCG) are bound via Logical MAC ports.
Configuring the Management Bridge

This section explains how to configure the management bridge.
To define and configure a bridge:

1. At the config# prompt, enter bridge 1.
The new bridge is defined and the config>bridge(1)# prompt appears.
To define and configure a bridge port:

At the config>bridge(1)# prompt, enter port <1..250>.
5-224
Management Bridge
The config>bridge(1)>port(<1..250>)# prompt appears.

Configure the new bridge port and bind it to the bridge as illustrated and
explained in the table below.
Task
Command
Comments
Assigning short
description to the bridge
port
name <string>
Using no name removes the

name
the bridge port
no shutdown
Using shutdown disables the

bridge port
Binding a mng-ethernet
port to the bridge
bind mng-ethernet <slot>/1
Using no before bind removes

the port from the bridge
Binding an SVI port to the

bridge
bind svi <port-number>
Using no before bind removes

the port from the bridge
Example
The following example illustrates configuring management connectivity with
Management VLAN via ASMi-54C module.
1. Make sure that the Default Router Bridge Connectivity is established:
SVI port 9999 connects the router interface 9999 to the bridge port
9999(default configuration).
Management Ethernet port 1 of CL-A module is up and bound to bridge

port 9997
Management Ethernet port 1 of CL-B module is up and bound to bridge

port 9998.
Add router 1 interface:

mp4100# config router 1
Configure router 9999 interface address 172.17.171.217, subnet mask 24, and
default-gateway 172.17.171.1 (see below).
mp4100>config>router(1)# interface 9999 address 172.17.171.217/24
The router bridge connectivity is established.
Program an ASMi-54C module in Slot 3 and configure SHDSL ports 1 and 2 named
Line1 and Line2.
Management Bridge
5-225
mp4100>config>slot#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
mp4100>config>port#
3 card-type dsl asmi54c

shdsl 3/1 name Line1
shdsl 3/1 line-prob
shdsl 3/1 stu central
shdsl 3/1 no shutdown
shdsl 3/2 name Line2
shdsl 3/2 line-prob
shdsl 3/2 stu central
shdsl 3/1 no shutdown
Configure PCS port on the ASMi-54C module named PCS1 and bind ports Line1
and Line2 to this PCS port.
mp4100>config>port# pcs 3/1 name PCS1
mp4100>config>port# pcs 3/1 bind shdsl 3/1
mp4100>config>port# pcs 3/1 bind shdsl 3/2
Define a classifier named mng flow port side with profile match-any match vlan
100.
mp4100>config>flows# classifier-profile mng match-any match vlan 100
Define a classifier named mng flow bridge side with profile match-any match
all.
mp4100>config>flows# classifier-profile mng match-any match all
Add and configure an SVI port 2 named MNG2 to connect the ASMi-54C module
to the bridge.
mp4100>config>port# svi 2 name MNG2
Bind SVI port 2 to bridge port 4.
mp4100>config>bridge# 1 port 4 bind svi 2
Create an ingress flow 1 between PCS port 1 of the ASMi-54C module and SVI
port 2 using the following parameters:
Flow 1
Classifier named mng_flow_bridge_side
Tagging of the management traffic with VLAN 100, priority bit 7
Set SVI 2 as ingress port.
Set PCS 3/1 as egress port.
flow
flow
flow
flow
1
1
1
1
classifier mng_flow_bridge_side
vlan-tag push vlan 100 p-bit fixed 7
ingress-port svi 2
egress-port pcs 3/1
Create an egress flow 2 between PCS port 1 of an ASMi-54C module and SVI port
2 using the following parameters:
5-226
Flow 2.
Classifier named mng_flow_port_side
Removing VLAN before entering management bridge (management bridge

is unaware bridge)
Set SVI 2 as egress port.
Management Bridge
Set PCS 3/1 as ingress port.
flow
flow
flow
flow
2
2
2
2
classifier mng_flow_port_side
vlan-tag pop vlan
ingress-port pcs 3/1
egress-port svi 2
The management connectivity is established.
5.34 Management Router

The Megaplex-4100 router is an internal interworking device that forwards
management traffic between its interfaces. Each router interface is assigned an
IP address and can be bound to one of the Megaplex-4100 ports. The router
supports up to 128 interfaces for binding TDM (E1, T1, E1-i, T1-i) ports and up to
4 interfaces for binding SDH/SONET ports.
Management Router is configured at the router(1) level.
Note
There are two routers in the Megaplex-4100 architerchure: Router 1 is used for
inband management, while Router 2 is used for pseudowire routing. Router 2 is
explained in the Pseudowire Router section.
Follow this procedure to configure the Megaplex-4100 router:
1. If needed, configure the default gateway (static route 0.0.0.0/0) and other
static routes.
Add a router interface and define its IP address and subnet mask.
Define inband management through the relevant port with its parameters (dcc
encapsulation, mode and routing-protocol for sdh-sonet ports), protocol and
routing-protocol for e1, t1, e1-i, t1-i ports).
Bind the router interface to this sdh-sonet, e1, t1, e1-i, or t1-i port.
Adding and Configuring Router Interfaces

Each router interface is assigned an IP address and can be bound to one of the
Megaplex-4100 ports.
Adding a Router Interface
To add a router interface:

1.
Navigate to configure router 1.

The config>router(1)# prompt is displayed.
Type the interface command and enter an interface number in the 1132 range.
An interface is added and the config>router(1)>interface(number)#
prompt is displayed.
For example:
Management Router
5-227
To add router interface 5:

mp4100>config>router 1 interface 5 bind e1 5/1
To delete router interface 5:

mp4100>config router 1 no interface 5
Configuring the Router Interface

After adding a router interface, you have to configure it. Once configuration is
completed, you can display the routing table (see below).
To configure a router interface:
At the config>router(1)>interface(number)# prompt, enter all necessary

commands according to the tasks listed below:
Task
Command
Comments
Assigning a short name to

the router interface
name <string>
no shutdown
Using shutdown administratively

disables the router interface
Assigning IP address and

subnet mask to the router
interface
address <valid IP address with mask

in the address/mask format>
For creating subnets, RAD

recommends using an IP subnet
calculator, for example
http://www.wildpackets.com/. Use the
following guidelines:
When designing a ring, assign to

each interface a small subnet which
contains a minimum of IP
addresses (2 -3).
Subnets inside the ring should not

overlap, that is the ring no two
addresses inside the ring should be
identical.
Binding the router

interface to an sdh-sonet,
e1, t1, e1-i, or t1-i port
bind { sdh-sonet | e1 | t1 | e1-i | t1-i }

<slot/port>
To remove the binding, you must

delete the router interface (use no
interface command)
Binding the router

interface to an E1
Optimux module port
bind e1
Megaplex Optimux cards (OP-34C,

OP-108C) only
Binding the router

interface to an SVI port
bind svi <port-number>
Displaying a routing table
show routing-table
5-228
Management Router
<slot/port>
To remove the binding, you must

delete the router interface (use no
interface command)
Using no before bind removes the
binding
Note
The following IP addresses cannot be used for router interfaces:
255.255.255.255 limited broadcast
127.x.x.x loopback network
0.0.0.0 this host
224.x.x.x classes D and E
x.y.z.255 directed broadcast for net
0.0.0.x or zero mask.
For example:
To configure a router interface 5:
IP address 172.17.171.217, subnet mask 24
Bound to E1 port 5/1

mp4100>config>router(1)# address 172.17.171.217/24
mp4100>config>router 1 interface 5 bind e1 5/1

Displaying the Routing Table

The routing table displays the following entries:
Interfaces configured by the user provided they are synchronized (#27, #28,
#29 in our example). These interfaces are marked with Protocol Local.
Static routes configured by the user, including the default gateway, or static
route 0.0.0.0/0 (in our example #1). These interfaces are marked with
Protocol Static.
Interfaces learned from different protocols (in the example, the rest of the
interfaces have been learned from the RIP protocol).
For each interface the routing table includes the following:
IP Address/Mask
IP Address of the next hop
Routing protocol
Distance between this interface and the router IP addresses in hops

(Metric-1). In the case of a static route Metric-1 denotes priority.
Management Router
5-229
To display a routing table:

mp4100>config>router(1)# show routing-table
Num IP Address/Mask
Next Hop
Protocol
Metric-1
--------------------------------------------------------------1. 0.0.0.0/0
172.17.173.1
Static
1
2. 172.17.173.0/24
172.18.197.49 RIP
5
3. 172.17.173.2/32
172.18.197.49 RIP
5
4. 172.18.197.4/30
172.18.197.49 RIP
4
5. 172.18.197.5/32
172.18.197.49 RIP
5
6. 172.18.197.6/32
172.18.197.49 RIP
4
7. 172.18.197.8/30
172.18.197.49 RIP
5
8. 172.18.197.9/32
172.18.197.49 RIP
5
9. 172.18.197.10/32
172.18.197.49 RIP
6
10. 172.18.197.12/30
172.18.197.49 RIP
3
11. 172.18.197.13/32
172.18.197.49 RIP
4
12. 172.18.197.14/32
172.18.197.49 RIP
3
13. 172.18.197.16/30
172.18.197.58 RIP
5
14. 172.18.197.17/32
172.18.197.58 RIP
5
15. 172.18.197.18/32
172.18.197.49 RIP
6
16. 172.18.197.24/30
172.18.197.49 RIP
4
17. 172.18.197.25/32
172.18.197.49 RIP
4
18. 172.18.197.28/30
172.18.197.58 RIP
5
19. 172.18.197.29/32
172.18.197.58 RIP
5
20. 172.18.197.32/30
172.18.197.49 RIP
6
21. 172.18.197.33/32
172.18.197.49 RIP
6
22. 172.18.197.36/30
172.18.197.49 RIP
3
23. 172.18.197.37/32
172.18.197.49 RIP
3
24. 172.18.197.40/30
172.18.197.49 RIP
2
25. 172.18.197.41/32
172.18.197.49 RIP
3
26. 172.18.197.42/32
172.18.197.49 RIP
2
27. 172.18.197.50/30
0.0.0.0
Local
0
28. 172.18.197.53/30
0.0.0.0
Local
0
29. 172.18.197.57/30
0.0.0.0
Local
0
30. 172.18.197.58/32
172.18.197.58 RIP
2
Configuring Static Routes and Default Gateway

You can add fixed (static) routes to the Megaplex-4100 routing table. A particular
case of a static route is default gateway, which is defined in Megaplex-4100 by
configuring a static route 0.0.0.0/0.
To configure a static route:
At the config>router(1) # prompt, enter the static-route command as follows:
static-route <IP address/mask> address <IP address of a next hop host>

priority <priority 1 to 255>
Example.
5-230
IP address 10.10.10.10
Mask 24
Next hop address 172.17.144.1
Management Router
Priority 5.
mp4100>configure router 1 static-route 10.10.10.10/24 address 172.17.144.1

priority 5
To delete a static route:
mp4100>configure router 1 no static-route 10.10.10.10/24 address 172.17.144.1
To configure a default gateway at the host with IP address 172.17.173.1:

1. Navigate to configure router 1.
To remove a default gateway:
mp4100>config router 1 no static-route 0.0.0.0/0 address 172.17.173.1
Example
Figure 5-35 shows an application with four Megaplex-4100 nodes (MP1, MP2,
MP3, MP4) connected by an SDH ring. The central node (MP1) is connected via its
control port to the Management router which manages the entire network. The
nodes are connected via small subnets, and four different colors designate IP
addresses from the same subnet (for example, the yellow line from MP1 CL.A link
1 to MP2 CL.B link 1 connects two addresses from the same subnet:
172.17.197.5/30 and 172.17.197.6/30).
In each Megaplex the configuration procedure is as follows:
Configure 2 SDH ports with DCC management
Configure 2 router interfaces with subnets and bind them to SDH ports
Note
Router interface 9999 and SVI port 9999 are present in the Megaplex-4100
configuration as part of the factory default file and need not be created. By
default, SVI port 9999 is bound to Router interface 9999.
In addition, for the central Megaplex-4100 MP1 (IP address 172.17.173.1) you
must configure the default gateway (static-route 0.0.0.0/0) and the next hop
(static route).
Management Router
5-231
1 2 1 2
CL.B
CL.A
MP 2
1 2 1 2
1 2 1 2
CL.B
172.17.174.1
1 2 1 2
CL.A
MP 1
172.17.173.1
CL.B
CL.A
CL.B
CL.A
PC
172.17.174.54
MP 3
MP 4
Figure 5-36. Four Megaplex-4100 Nodes in an SDH Ring
Router (not part of the MP configuration)

Next hop 172.17.197.0 172.17.173.2
172.17.179.1/24
MP 1
CL A
172.17.173.2/24
SVI
CL A
CL B
Control 172.17.173.2/24
L1
172.17.197.5/30
L1
172.17.197.9/30
Static Route*
0.0.0.0/0
172.17.173.1
MP 2
SVI
CL A
CL B
L1
L1
172.17.197.25/30
172.17.197.13/30
172.17.197.6/30
SVI
CL A
CL B
L1
L1
172.17.197.29/30
172.17.197.17/30
172.17.197.14/30
L1
L1
172.17.197.33/30
172.17.197.10/30
172.17.197.18/30
MP 3
MP 4
SVI
CL A
CL B
* A static-route is needed on the router to subnet 172.17.197.X

5-232
Management Router
#MP 1
exit all
configure slot cl-b card-type cl cl2-622gbe
configure router 1 interface 9999 address 172.17.173.2/24
configure router 1 static-route 0.0.0.0/0 address 172.17.173.1
configure port sdh-sonet cl-a/1 no shutdown
configure port sdh-sonet cl-a/1 dcc encapsulation hdlc mode d1-to-d3 routingprotocol rip2
configure router 1 interface 1 bind sdh-sonet cl-a/1
configure router 1 interface 1 no shutdown
configure port sdh-sonet cl-b/1 no shutdown
configure port sdh-sonet cl-b/1 dcc encapsulation hdlc mode d1-to-d3 routingprotocol rip2
configure router 1 interface 2 bind sdh-sonet cl-b/1
commit
save
#MP 2
exit all
commit
save
Management Router
5-233
#MP 3
exit all
commit
save
#MP 4
exit all
commit
save
5.35 Pseudowire Router

The Megaplex-4100 Router 2 function is used to route pseudowire packets
generated by the MPW-1 modules installed in the chassis to their destination
(peers).
5-234
Pseudowire Router
The terms and parameters needed by the Megaplex-4100 router function to
support pseudowire routing are explained below:
Router interfaces: the Megaplex-4100 Router 2 function supports up to 100

router interfaces, each assigned a unique index number. Each router interface
has its own IP address; you must also specify an IP subnet mask, and the
module and port on which interface is located.
For each router interface, you can also enable the use of VLAN tagging and
specify a VLAN ID, to enable differentiating the traffic carried by this router.
Note that when the router interface is connected (via SVI) to a GbE port or a
VCG, VLAN tagging is always enabled.
Each MPW-1 supports up to 6 different router interfaces; additional
interfaces can be configured on any bridge port in the Megaplex-4100. The IP
address of the appropriate interface is automatically inserted as the
pseudowire source IP address.
Pseudowire peers: the pseudowire destination is referred to as the

pseudowire peer. Megaplex-4100 supports up to 100 peers, each assigned a
unique index number. The index number is then used to specify the
pseudowire destination, instead of directly providing the necessary
destination information. To configure a peer, it is necessary to provide its IP
address, and as an option the next hop IP address. The peers (the
pseudowire destinations) and the associated routing information are defined
under configure peer context.
Static routes: to control the paths used to reach the pseudowire

destinations, the Megaplex-4100 router function supports the definition of
up to 100 static routes, in addition to a default gateway.
Within the Megaplex-4100, pseudowires are forwarded to the appropriate exit

port (always a router interface) by internal E-line Ethernet flows (an E-line flow is
a type of Ethernet logical connection that interconnects two bridge ports).
Each router interface serves as a bridge port for the pseudowires using it (in
addition, each Megaplex-4100 Ethernet port also serves as a bridge port).
To help you design the routing information, Figure 5-37 summarizes the process
used to select the router interface for each pseudowire peer. The priority of the
various router interfaces, as determined by the routing process, is as follows:
1. If the peer IP address is in the subnet of a router interface, that interface will
always be used.
If the peer IP address is not within a router interface subnet, then the router
checks if the specified peer next hop address is within the subnet of a router
interface. If such a router interface is found, it is selected to serve as the
pseudowire exit port.
If neither of the previous conditions is fulfilled, the router checks if the specified
peer next hop address is specified in a static route that is within the subnet
of a router interface.
The last priority is to use the router interface that is within the default gateway
subnet.
Pseudowire Router
5-235
DB Update
Peer IP address
in the subnet
of one of the
router interfaces
No
No
Look in static routes

table, for peer Next Hop in
the subnet of one
of the router interfaces
No
Peer Next Hop

in the subnet
of one of the
router interfaces
Yes
Yes
Yes
Find a router interface in

the default gateway
subnet
Select as the router interface in use
Figure 5-37. Selecting the Active Router Interface for an Ethernet Flow Serving a Pseudowire
The PW Router is configured at the router(2) level.
Adding and Configuring Router Interfaces

Each router interface is assigned an IP address and can be bound to one of the
Megaplex-4100 ports.
Adding a Router Interface
To add a router interface:

1.

Type the interface command and enter an interface number in the 1100 range.
An interface is added and the config>router(2)>interface(number)#
prompt is displayed.
For example:
5-236
Pseudowire Router
To add router interface 5:

mp4100>config>router 2 interface 5 bind svi 4

Configuring the Router Interface

After adding a router interface, you have to configure it. Once configuration is
completed, you can display the routing table (see below).
To configure a router interface:
At the config>router(2)>interface(number)# prompt, enter all necessary

Task
Command
Comments
Assigning a short name to

name <string>
no shutdown
Using shutdown administratively

disables the router interface
Assigning IP address and

subnet mask to the router
interface
address <valid IP address with mask

in the address/mask format>
For creating subnets, RAD

recommends using an IP subnet
calculator, for example
http://www.wildpackets.com/. Use the
following guidelines:
Binding the PW router

interface to an SVI port
bind svi <port>
Router interfaces must be on

different subnets
When designing a ring, assign to

each interface a small subnet which
contains a minimum of IP
addresses (2 -3)
Subnets inside the ring should not

overlap, that is no two addresses
inside the ring should be identical.
This SVI port will be further bound to

an ethernet or logical mac port.
Using no before svi removes the
binding.
Note
The following IP addresses cannot be used for router interfaces:
Pseudowire Router
5-237
255.255.255.255 limited broadcast
127.x.x.x loopback network
0.0.0.0 this host
224.x.x.x classes D and E
x.y.z.255 directed broadcast for net
1.1.1. x or zero mask.
For example:
To configure a router interface 5:
IP address 172.17.171.217, subnet mask 24
Bound to SVI port 2

mp4100>config>router 2 interface 5 bind svi 2

Adding and Configuring Remote Peers

Peers are remote devices operating opposite router interfaces. These devices
serve as destinations for pseudowire connections for transporting a TDM payload
over packet-switched networks. You can define up to 100 peers.
To add a remote peer:
At the config>peer # prompt, type the peer number in the range of 1 to 100.
To configure a remote peer:
At the config>peer (peer number) # prompt, enter all necessary commands

Task
Command
Defining IP address of a remote

peer in IP and MPLS networks
ip <valid IP address>
Assigning a name to a remote

peer
name <alphanumeric string >
Specifying the IP address of the

next port to which packets
directed to the selected peer will
be sent
next-hop-ip <valid IP address>
Comments
You need to specify a next hop

IP address only when the peer
IP address is not within the IP
subnet of the router interface
that will be used to send
packets to this peer.
The default value, 0.0.0.0,
means that no next hop IP
address is defined
5-238
Pseudowire Router
To remove a remote peer:
Note
At the config>peer (peer number) # prompt, type no peer (peer number).
Setting remote peers as destinations is done under configure pwe context.

To display the remote peer table:
At the config# prompt, type info and scroll to the corresponding section.
mp4100>config# info
peer 1 ip 6.6.6.7 next-hop-ip
peer 2 ip 172.17.153.191 name
peer 3 ip 172.17.154.192 name
0.0.0.0
"peer_2" next-hop-ip
"peer_3" next-hop-ip
172.18.170.1
172.18.170.1
For example:
To configure remote peer 1:
IP address: 9.9.9.9
Next hop IP address: 0.0.0.0
Name: peer1.
mp4100>configure peer 1 ip 9.9.9.9 name peer1 next-hop-ip 0.0.0.0
To delete remote peer 1:
mp4100>config# no peer 1
Displaying the Routing Table

The routing table displays the following entries:
Interfaces configured by the user on condition that they are synchronized (in
our example #2, #3, #4). These interfaces are marked with Protocol Local.
Static routes configured by the user, including the default gateway, or static
route 0.0.0.0/0 (in our example #1). These interfaces are marked with
Protocol Static.
For each interface the routing table includes the following:
IP Address/Mask
IP Address of the next hop
Routing protocol
Distance between this interface and the router IP addresses in hops

(Metric-1). In the case of a static route Metric-1 denotes priority.
Pseudowire Router
5-239
To display a routing table:

mp4100>config>router(2)# show routing-table
Num IP Address/Mask
Next Hop
Protocol
Metric-1
----------------------------------------------------------1. 0.0.0.0/0
172.18.170.1
Static
1
2. 172.18.170.75/24
0.0.0.0
Local
0
3. 172.17.151.55/24
0.0.0.0
Local
0
Configuring Static Routes and Default Gateway

To control the paths used to reach the pseudowire destinations, the PW router
supports the definition of up to 100 static routes, in addition to a default
gateway.
You can add fixed (static) routes to the Megaplex-4100 routing table. A particular
case of a static route is default gateway, which is defined in Megaplex-4100 by
configuring a static route 0.0.0.0/0.
At the config>router(2) # prompt, enter the static-route command as follows:
static-route <IP address/mask> address <IP address of a next hop host>

priority <priority 1 to 255>
For example:
IP address 10.10.10.10
Mask 24
Next hop address 172.17.144.1
Priority 5.

priority 5
To delete a static route:
mp4100>configure router 2 no static-route 10.10.10.10/24 address 172.17.144.1
To configure a default gateway at the host with IP address 172.17.173.1:

5-240
Pseudowire Router
To remove a default gateway:
mp4100>config router 2 no static-route 0.0.0.0/0 address 172.17.173.1
Example 1. Establishing PW Connectivity between HS-12N Module and

MPW-1 Fast Ethernet Port
1. Configuring an HS-12N module in slot 10:
configure slot 10 card-type high-speed hs12n
configure port serial 10/1 no shutdown
Configuring a MPW-1 module in slot 2:
configure
configure
configure
configure
slot
port
port
port
2 card-type pw mpw1
ethernet 2/1 no shutdown
ds1 2/1 no shutdown
ds1 2/1 signaling
Configuring PW 1:
configure pwe pw 1 type tdmoip-v2 psn udp-over-ip
oam
peer 1
exit all
Configuring the PW destination:
configure peer 1 ip 10.10.10.3
Creating a TDM pseudowire cross-connection between PW 1 and serial HS-12N
port:
DS0 cross-connect between:
HS-12N module installed in slot 10, port 1.
MPW-1 module installed in slot 2, DS1 port 1, TS 1.
PW-TDM cross-connect between:
Pseudowire (pw) 1.
configure cross-connect ds0 ds1 2/1 ts 1 serial 10/1

configure cross-connect pw-tdm pw 1 ds1 2/1 time-slots 1
Configuring the default gateway and interface 1 on PW router:
configure router 2
static-route 0.0.0.0/0 address 10.10.10.1
interface 1 address 10.10.10.2/24
Configuring SVI port and binding it to router interface 1:
configure port svi 1 no shutdown
interface 1 bind svi 1
exit all
Creating two symmetric flows between Ethernet port 2/1 on MPW-1 module and
SVI 1 port, classifier match-all named C1:
Pseudowire Router
5-241
configure flows
classifier-profile c1 match-all
match all
exit
flow 1
no shutdown
classifier c1
egress-port svi 1
exit
flow 2
no shutdown
classifier c1
ingress-port svi 1
egress-port eth 2/1
exit all
Now the traffic from HS-12N serial port is forwarded to Ethernet port, which
serves as a pseudowire exit port toward the PSN.
Example 2. Establishing PW Connectivity between HS-12N Module and

VCG
1. Configuring an HS-12N module in slot 10:
configure slot 10 card-type high-speed hs12n
configure port serial 10/1 no shutdown
Configuring a MPW-1 module in slot 4
configure slot 4 card-type pw mpw1
configure port ds1 4/1 no shutdown
Adding and configuring the remote peer:
config peer 1 ip 9.9.9.9 name peer1 next-hop-ip 0.0.0.0
Configuring PW 1 and setting its destination peer:
configure pwe
pw 1 type tdmoip-v2 psn udp-over-ip
peer 1
exit all
Creating a TDM pseudowire cross-connection between PW 1 and serial HS-12N
port:
5-242
Pseudowire (pw) 1.
Pseudowire Router
configure cr ds0 ds1 2/1 ts 1 serial 10/1

configure cr pw-tdm pw 1 ds1 4/1 time-slots 1
Configuring the default gateway and interface 1 on PW router:
configure router 2
static-route 0.0.0.0/0 address 2.2.2.1
interface 1 address 2.2.2.2/24
exit all
Configuring SVI port and binding it to router interface 1:
configure port svi 1 no shutdown
interface 1 bind svi 1
exit all
Defining VCG 1 and mapping it to SDH:
configure port vcg cl-a/1 no shutdown
configure port vcg cl-a/1 bind vc-vt cl-a/1/1/1/1/1
Defining gfp encapsulation for VCG 1:
configure port gfp cl-a/1
no shutdown
bind vcg cl-a/1
exit all
Defining logical-mac (logical Ethernet port for creating the flow):
configure port logical-mac cl-a/1
no shutdown
bind gfp cl-a/1
exit all
Creating two symmetric flows (Flow 1 and Flow 2) between Logical-mac 1 on CLA module and SVI 1 port, classifier profile named vlan-10:
configure flows
classifier-profile vlan-10 match-all
match vlan 10
exit all
configure flows
flow 1
no shutdown
classifier vlan-10
egress-port svi 1
ingress-port logical-mac cl-a/1
exit
flow 2
no shutdown
classifier vlan-1
egress-port logical-mac cl-a/1
ingress-port svi 1
exit all
Now the traffic from HS-12N serial port is forwarded to a VCG, which serves as a
pseudowire exit port toward the PSN.
Pseudowire Router
5-243
5.36 Internal DS1 Ports

The MPW-1 module has eight independently-configurable internal DS1 ports, each
capable of handling 32 timeslots, for a total processing capacity of 256 timeslots
(the equivalent of 8 E1, or 2.048 Mbps, streams).
The following parameters can be configured for the internal DS1 ports:
Port name
Framing type
Signaling.
The internal DS1 ports are logical ports that provide the linkage between the
packet processing subsystem and the TDM subsystem:
On the TDM side, a DS1 port serves as an endpoint for traffic from the TDM
and signaling buses. Each I/O or E1-i/T1-i port in the Megaplex-4100 that will
use pseudowires on MPW-1 must be assigned bandwidth (timeslots) on the
internal DS1 port, using the standard Megaplex-4100 timeslot assignment
procedures.
On the pseudowire side, a DS1 port serves as the collection point for
timeslots to be carried by each pseudowire. Thus, to carry traffic from a
specific TDM port by means of a pseudowire, it is necessary to assign the
same timeslots on the TDM side and on the pseudowire side. The pseudowire
timeslot assignment is made as part of the pseudowire configuration
procedure, and it determines the cross-connect operations performed by the
pseudowire cross-connect matrix (see Configuring a PW-TDM Cross
Connection below).
MPW-1 has a total of eight internal DS1 ports, each capable of handling 32
64-kbps timeslots. The user can independently configure each internal DS1 port
in accordance with the desired operation mode:
Framed mode, which enables individual handling of each port timeslot, or

unframed (all the 32 timeslots of the port handled as a whole, and
cross-connected to the same destination port)
Signaling transfer: enabled or disabled. The MPW-1 module itself does not
process signaling information: all the necessary processing is performed
under the control of the CL module, either at the source TDM port or within
the CL module itself. Therefore, all the Megaplex-4100 signaling processing
features, including use of signaling profiles, are also effective for traffic
transferred over pseudowires by means of MPW-1 modules.
Factory Defaults
Megaplex-4100 is supplied with all DS1 ports disabled. Other parameter defaults
5-244
Internal DS1 Ports
Parameter
Default Value
line-type
framed
signaling
disabled
Configuring Internal DS1 Port Parameters
To configure the internal DS1 port parameters:

1. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to configure.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments
Assigning short
description to port
name <string>
port
no shutdown
Specifying the framing

mode of the internal DS1
port
line-type {unframed | framed}
Make sure to select the same value at both

end points.
Enabling transmitting an
(OOS) on PW failure
signaling
no signaling disables transmitting an OOS

signal
Example
The following section illustrates how to configure the internal DS1 port 1 on the
MPW-1 module installed in slot 9:
Set the line type to unframed.
mp4100>config>port>ds1(9/1)# line-type unframed

mp4100>config>port>ds1(9/1)# no shutdown
Testing DS1 Ports

The Megaplex-4100 DS1 ports feature test and loopback functions at the
timeslot level.
Internal DS1 Ports
5-245
Local Loopback on Selected Internal DS1 Port Timeslots

The local loopback on timeslots of an MPW-1 internal DS1 port is used to return
the transmit payload carried by selected timeslots of the tested port through the
same timeslots of the receive path. The timeslots looped back remain connected
to the transmit path of the port, but the corresponding timeslots received from
the remote end are disconnected.
This test is recommended for testing signal paths between the I/O port of the
other local module which uses the pseudowire, and the MPW-1 port.
The loopback is activated within the CL module routing matrix, and only on the
timeslots specified by the user during the activation of the loopback. As a result,
there is no disturbance to services provided by means of the other timeslots
(pseudowires) of the same port: only the flow of payload carried by the specified
timeslots is disrupted.
The signal paths for a local loopback on timeslots are shown in Figure 5-38.
arbitrarily selected timeslots.
When the loopback is activated on timeslots of a port which is part of a
redundancy pair, the CL module automatically activates the loopback on the same
timeslots of the other port of the pair. The same is true for timeslots assigned to
the same pseudowire.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the
redundancy pair (even if it has been activated by a command to the other port).
Int DS1 Port n

TS n
Megaplex-4100
MPW-1 Module
CL
MPW-1
Int DS1 Port 1
TS n
Other
Ports
Routing
Matrix
Bus
Interface
..
.
..
.
..
.
.
..
TDM CrossConnect
Matrix
Pseudowire
CrossConnect
Matrix
Packet
Processor
Ethernet
Switch
To PSN
Int DS1 Port 8
Figure 5-38. Local Loopback on Selected Internal DS1 Port Timeslots, Signal Paths
Remote Loopback on Selected Internal DS1 Port Timeslots

The signal paths for a remote loopback on timeslots are shown in Figure 5-39.
5-246
Internal DS1 Ports
Int DS1 Port n

TS n
Megaplex-4100
MPW-1 Module
CL
MPW-1
Int DS1 Port 1
TS n
Other
Ports
Routing
Matrix
Bus
Interface
..
..
.
..
..
..
.
TDM CrossConnect
Matrix
Pseudowire
CrossConnect
Matrix
Packet
Processor
Ethernet
Switch
To PSN
Int DS1 Port 8
Figure 5-39. Remote Loopback on Selected Internal DS1 Port Timeslots, Signal Paths
The remote loopback on timeslots of an MPW-1 port is used to return the receive
payload carried by selected timeslots of the tested port through the same
timeslots of the transmit path. The corresponding timeslots received from the
local equipment are disconnected.
through a selected pseudowire served by the corresponding MPW-1 port.
The loopback is activated within the CL module routing matrix, and only on the
timeslots specified by the user during the activation of the loopback. As a result,
there is no disturbance to services provided by means of the other timeslots
(pseudowires) of the same port: only the flow of payload carried by the specified
timeslots is disrupted.
Loopback Duration
by the MPW-1. Therefore, when you initiate a loopback, you have the option to
limit its duration to a selectable interval in the range of 1 through 30 minutes.
Internal DS1 Ports
5-247
To perform a loopback on the internal DS1 port:

1. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to be tested.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
Task
Command
Comments

loopback and the duration
of it (in minutes)
loopback {local | remote} time-slot

<1..31>] [duration <duration in
minutes 1..30> ]
no loopback
5.37 Pseudowires
Pseudowires are an emulation of Layer-2 point-to-point connection-oriented
services over packet-switching networks (PSN).
Packet formats can be selected on a per-bundle basis for optimal transmission
over UDP/IP- or MPLS- based networks (UDP/IP and MPLS, respectively). Each
bundle can be independently routed to any destination.
The following user-configurable protocols are supported, independently for each
pseudowire:
TDMoIP (TDM over IP) in accordance with RFC5087, and TDMoMPLS in

accordance with RFC5087 and ITU-T Rec. Y.1413 (the term TDMoPSN is used
when information is applicable to both protocols)
HDLCoPSN (HDLC over PSN) in accordance with RFC5087 and RFC4618

(except Clause 5.3 PPP)
CESoPSN (structure-aware TDM circuit emulation over PSN) in accordance

with RFC5086.
SAToPSN (structure-agnostic TDM over PSN) in accordance with RFC4553.
The maximum number of PW (connection) configurations that may be stored in

the Megaplex-4100 is 640, where each pseudowire is assigned a unique index
number in the range of 1 to 640. The actual maximum number, however,
depends on the number and type of modules installed in the chassis.
Note
5-248
When the PSN type is UDP/IP, the user-specified labels are in the range of 1 to
8063.
Pseudowires
Standards
The MPW-1 PW ports provide pseudowire emulation services over
packet-switched networks using the following user-configurable protocols:

accordance with RFC5087 and ITU-T Rec. Y.1413


with RFC5086
In addition, MPW-1 meets the requirements for edge-to-edge simulation of TDM

circuits over PSN in accordance with RFC4197, including high-performance
adaptive timing recovery capabilities.
The pseudowire services enable converting TDM payload to packets and
transferring these packets through router interfaces defined in the
Megaplex-4100.
The pseudowire subsystem is located on the MPW-1 modules. Each MPW-1
module has eight independently-configurable internal DS1 ports, each capable of
handling 32 timeslots, for a total processing capacity of 256 timeslots (the
equivalent of 8 E1, or 2.048 Mbps, streams). The traffic to the internal DS1 ports
is directed by means of a pseudowire cross-connect matrix (a timeslot
cross-connect matrix similar to the TDM cross-connect matrix), which routes
traffic from the internal DS1 ports to the pseudowire packet processors.
Multiple MPW-1 modules can be installed in the Megaplex-4100 chassis, in
accordance with the required pseudowire transport capacity.
Note
For additional information on the Megaplex-4100 pseudowire system, see also

the following sections:
Pseudowire Router
Internal DS1 Ports
Configuring a PW-TDM Cross Connection
Fault Propagation
MPW-1 modules (in Appendix B of this manual)
Each pseudowire terminated on the MPW-1 can be independently configured to
handle the desired type of traffic:
Transparent transfer of data (unframed E1 streams) using TDMoPSN, or

SAToPSN.
Transfer of framed E1 and T1 streams, using TDMoPSN and CESoPSN.

To support voice payload, the signaling information can also be transported.
Note that when using CESoPSN, any timeslots carrying signaling information
(either channel-associated signaling (CAS), or common-channel signaling
Pseudowires
5-249
(CCS) such as Signaling Scheme 7 (SS7), ISDN PRI signaling, etc.) can be
transparently transferred within the pseudowire, as regular data timeslots.
Fractional E1 and T1 services, with or without CAS, are supported by means

of TDMoPSN. Without CAS, CESoPSN can also be used.
HDLC traffic can be carried over framed and unframed E1 and T1 using
HDLCoPSN. This enables efficient and transparent transfer of Frame Relay
traffic.
Packet structure is independently selectable for each pseudowire, for

compatibility with the various pseudowire protocols (TDMoPSN, CESoPSN,
HDLCoPSN, SAToPSN) and the PSN type (UDP/IP or MPLS/ETH). For maximum
flexibility in system applications, the framing format of the pseudowire device at
the destination (referred to as a pseudowire peer) can also be taken into
account, thus in many cases traffic using the E1 standards can be directed at
destinations using the T1 standards, and vice versa.
The pseudowire exit port toward the PSN is also selectable: either via one of the
MPW-1 Ethernet ports, or via any other bridge port (GbE, Fast Ethernet, or VCG)
of any module installed in the chassis. The selectable exit ports are bound (via SVI
ports) to router interfaces, where each router interface has its own IP source
address, and optionally its own VLAN. Each MPW-1 module supports up to 6
interfaces, CL.2 modules support unlimited number of interfaces. However, the
maximum number of router interfaces per Megaplex-4100 is limited to 100. The
user can also specify static routes to control the IP routing.
Pseudowire Packet Processing Subsystem

The packet processors in the MPW-1 packet processing subsystem perform the
functions necessary to convert TDM traffic directed to the MPW-1 internal DS1
ports to packetized traffic for transmission over pseudowires.
The maximum number of pseudowires that can be processed for each DS1 port,
provided the port uses the DS0 cross-connect mode, is 16 (only one pseudowire
is supported when the port uses the DS1 cross-connect mode).
A pseudowire can process traffic from only one internal DS1 port.
Each pseudowire has a header whose structure depends on the selected PSN
type, and includes labels that specify the uniquely specify the pseudowire source
and destination, in accordance with the following rules:
Notes
When the PSN type is UDP/IP, the user-specified labels are in the range of 1
to 8063. The pseudowire labels determine the UDP port numbers, as
explained in the Determining UDP Port Numbers Used by Pseudowires section
in Appendix B
When the PSN type is MPLS/ETH, the user-specified labels are used as MPLS
labels (these labels are always located at the bottom of the MPLS label
stack). The allowed range for pseudowire labels is then 16 to 1048575.
Different source and destination labels can be used. In this case, it is
necessary to ensure that the source (inbound) label selected at one

pseudowire endpoint is configured as the destination (outbound) label at the
other pseudowire endpoint, and vice versa.
The inbound Input PW label must be unique.
5-250
Pseudowires
Each pseudowire is handled in accordance with the user-configured PSN

parameters, considering the user-selected pseudowire parameters, and the
framing and signaling mode of the associated internal DS1 port. The processing
details for each pseudowire protocol are presented below.
TDMoPSN Processing
The main functions performed by the packet processor when using the TDMoPSN
mode are as follows:
In the transmit-to-network direction:
Processes the data stream received through the internal DS1 port to
generate pseudowires, as specified by the user. When using a framed
mode, the user can specify the timeslots to be transported end-to-end.
To prepare a pseudowire, the packet processor extracts segments from
the continuous data stream for insertion into the pseudowire payload
section.
The size of the pseudowire payload section is specified by the user
(n 48 bytes, where n is 1 to 30):
When operating in a framed mode, the slices are formed by collecting the
appropriate timeslots from consecutive frames until the TDM payload
section of the packet is filled. Timeslot 0 is never included; timeslot 16 is
processed in accordance with the signaling mode.
When operating in the unframed mode, the slices are formed by collecting
consecutive bytes from the received DS1 stream until the TDM payload
section of the packet is filled.
Adds the overhead necessary to transmit each slice over the packet
switched network (either UDP/IP or MPLS/ETH), and builds TDMoIP,
respectively TDMoMPLS, packets for transmission to the desired
destination. The resulting packets are encapsulated as TDMoPSN over
Ethernet, and then sent to the Ethernet switching subsystem of the
module.
When signaling transport is enabled and the pseudowire timeslots are

defined as voice timeslots, the signaling information associated with the
timeslots transported by the pseudowire is also inserted in the packet.
In the receive-from-network direction:
The TDMoPSN packets retrieved from the received Ethernet frames are
stored in a packet buffer. Each pseudowire has its own buffer.
The function of this buffer is to enable the packet processor to read the
received packets at the rate of the original data stream of each
pseudowire, and thus eliminate jitter in their arrival times. Therefore, this
buffer is called jitter buffer.
The packet processor recovers the payload carried by the packets and
restores the original data stream of the pseudowire, in accordance with
the selected framing mode.
When the pseudowire carries only selected timeslots, the payload is
reinserted in the appropriate timeslots. Therefore, when several
pseudowires carry payloads destined to the same internal DS1 port, all
Pseudowires
5-251
the useful payload is reinserted in the original timeslots, and only the
remaining empty timeslots in the internal port frame are filled with a
user-selectable idle code.
In a similar way, the signaling information related to the voice timeslots
transported by each pseudowire is reinserted in the positions
corresponding to the pseudowire timeslots.
Since the TDMoPSN packet structure for framed ports does not depend
on the port frame structure, a pseudowire carrying traffic from an E1 port
can be directed to a T1 port at the far end, as long as the total number
of timeslots does not exceed 24, and the payload type is data (signaling
cannot be transferred between E1 and T1 ports).
HDLCoPSN Processing
HDLCoPSN packet processing is similar to the processing of TDMoPSN packets
described above, except that the HDLCoPSN protocol is intended to provide
port-to-port transport of HDLC-encapsulated traffic, in accordance with RFC4618,
for example, Frame Relay or CCS protocols.
For framed ports, the HDLC traffic is carried in specific timeslots (these timeslots
are specified during the configuration of a HDLCoPSN pseudowire and are always
considered data timeslots).
Note
For HDLCoPSN, it is not necessary to configure the same number of timeslots at

the pseudowire end points. The pseudowire bandwidth will be determined by the
endpoint with the smaller number of assigned timeslots.
The HDLCoPSN protocol can also handle whole (unframed) E1 streams.
When assembling packets for a HDLC pseudowire, HDLC idle flags are removed,
and only the contents of HDLC packets with useful payload are inserted in
packets. This results in better bandwidth utilization efficiency. At the receive end,
HDLC packet structure is restored and inserted in the restored port data stream.
Therefore, HDLC pseudowires can connect only ports with the same framing
mode.
SAToPSN Processing
SAToPSN is different from the TDMoPSN and HDLCoPSN protocols, in that it is
used to transfer transparently a bit stream at the nominal port rate
(2.048 Mbps). Therefore, SAToPSN can be used only when the port uses the
unframed mode, and thus only one pseudowire can be configured per port.
SAToPSN packet payload consists of a user-specified number of raw TDM bytes (4
to 1440 bytes), and is treated as data payload.
Note
The SAToPSN packet overhead is large, and therefore, for efficient bandwidth
utilization, the number of raw TDM bytes per packet should be as large as
possible.
The receiving end restores the original bit stream, and therefore a SAToPSN
pseudowire can only be directed to another unframed E1 port, or to an
n64 kbps protocol (where n must be 32, that is, to a high-speed serial port
operating at a rate of 2048 kbps).
5-252
Pseudowires
CESoPSN Processing
CESoPSN transports raw TDM data, that is, packets are formed by inserting a
user-specified number of complete TDM frames (4 to 360 frames) in the packet
payload area. Therefore, CESoPSN pseudowires can only be configured on framed
ports.
The TDM frames are considered as serial data, even if they carry voice and CAS.
Since a CESoPSN pseudowire transports raw TDM frames, a CESoPSN pseudowire
can only be directed to another E1 framed port.
PSN Configuration Parameters

MPW-1 enables the user to select the PSN type (UDP/IP or MPLS/ETH), and
configure the PSN transport parameters.
The PSN parameters, which are reflected in the pseudowire header structure,
enable specifying the requested priority or quality of service for pseudowire
traffic generated by the MPW-1. The applicable parameters depend on PSN type:
When the PSN is based on Layer 2 forwarding, the user can specify the VLAN
priority (per IEEE 802.1p) for the Ethernet frames carrying pseudowire
packets. The priority is always selectable for traffic forwarded through the
Megaplex-4100 GbE ports, because for these ports VLAN tagging is always
enabled; when using other bridge ports as pseudowire exit ports, it is
necessary to enable VLAN tagging in order to request a specific priority.
When the PSN uses IP routing, the user can specify the Type of Service (ToS)
per RFC791; if the PSN supports RFC2474, ToS is interpreted as a DiffServ
codepoint per RFC2474.
When the PSN uses MPLS, the user can specify the EXP bits. In addition, the
user can also add ingress and egress tunnel labels, which enable network
operators to plan preferential forwarding of pseudowire traffic using the
specified tunnel labels.
Another parameter that may be used, for compatibility with older TDMoIP
implementations, is the packet payload version, V1 or V2.
Pseudowire QoS/CoS
To enable optimal handling of pseudowire traffic within the PSN, the following
parameters can be configured:
For Ethernet transport networks: outgoing pseudowire packets are assigned

to a dedicated VLAN ID according to 802.1Q and marked for priority using
802.1p bits.
For IP transport networks: outgoing pseudowire packets are marked for

priority using DSCP, ToS, or Diffserv bits. This allows TDMoIP packets to be
given the highest priority in IP networks.
For MPLS transport networks: outgoing pseudowire packets are assigned to a

specific MPLS tunnel, and marked for priority using the EXP bits.
The proper balance between the PSN throughput and delay is achieved via
configurable packet size. A jitter buffer with selectable size compensates for
packet delay variation (jitter) of up to 200 msec in the network.
Pseudowires
5-253
ToS
The ToS specifies the Layer 3 priority assigned to the traffic generated by this
pseudowire.
For IP networks, this priority is indicated by the IP type-of-service parameter for
this pseudowire. The specified value is inserted in the IP TOS field of the
pseudowire IP packets.
When supported by an IP network, the type-of-service parameter is interpreted,
in accordance with RFC791 or RFC2474, as a set of qualitative parameters for the
precedence, delay, throughput and delivery reliability to be provided to the IP
traffic generated by this pseudowire.
These qualitative parameters may be used by each network that transfers the
pseudowire IP traffic to select specific values for the actual service parameters of
the network, to achieve the desired quality of service.
You can also specify a Layer 2 priority by means of the vlan priority command.
Jitter Buffer
The packets of each pseudowire are transmitted by MPW-1 at essentially fixed
intervals towards the PSN. The packets are transported by the PSN and arrive to
the far end after some delay. Ideally, the PSN transport delay should be constant:
in this case, the packets arrive at regular intervals (these intervals are equal to
the intervals at which they had been transmitted). However, in reality packets
arrive at irregular intervals, because of variations in the network transmission
delay. The term Packet Delay Variation (PDV) is used to designate the maximum
expected deviation from the nominal arrival time of the packets at the far end
device.
Note
The deviations from the nominal transmission delay experienced by packets are
referred to as jitter, and the PDV is equal to the expected peak value of the jitter.
Note however that nothing prevents the actual delay from exceeding the selected
PDV value.
To compensate for deviations from the expected packet arrival time, MPW-1 uses
jitter buffers that temporarily store the packets arriving from the PSN (that is,
from the far end equipment) before being transmitted to the local TDM
equipment, to ensure that the TDM traffic is sent to the TDM side at a constant
rate.
For each pseudowire, the jitter buffer must be configured to compensate for the
jitter level expected to be introduced by the PSN, that is, the jitter buffer size
determines the Packet Delay Variation Tolerance (PDVT).
Two conflicting requirements apply:
5-254
Since packets arriving from the PSN are first stored in the jitter buffer before
being transmitted to the TDM side, TDM traffic suffers an additional delay.
The added delay time is equal to the jitter buffer size configured by the user.
The jitter buffer is filled by the incoming packets and emptied out to fill the
TDM stream. If the PSN jitter exceeds the configured jitter buffer size,
underflow/overflow conditions occur, resulting in errors at the TDM side:
Pseudowires
A jitter buffer overrun occurs when it receives a burst of packets that

exceeds the configured jitter buffer size + packetization delay. When an
overrun is detected, MPW-1 clears the jitter buffer, causing an underrun.
A jitter buffer underrun occurs when no packets are received for more
than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is
automatically filled with a conditioning pattern up to the PDVT level in order to
compensate for the underrun. Then, MPW-1 starts processing the packets and
empty out the jitter buffer toward the TDM side.
To minimize the possibility of buffer overflow/underflow events, two conditions
must be fulfilled:
The buffer must have sufficient capacity. For this purpose, the buffer size can
be selected by the user in accordance with the expected jitter characteristics,
separately for each pseudowire, in the range of 2.5 to 200 msec.
The read-out rate must be equal to the average rate at which frames are
received from the network. For this purpose, the read-out rate must be
continuously adapted to the packet rate, a function performed by the
adaptive clock recovery mechanism of each packet processor.
Adaptive Timing
MPW-1 modules have independent adaptive clock recovery mechanisms for each
pseudowire, which recover the original timing (clock rate) of the far-end source
of each pseudowire. The clock recovery mechanisms can provide recovered clock
signals to serve as timing references for the Megaplex-4100 nodal timing
subsystem.
The receive path of each pseudowire must use a clock recovery mechanism to
recover a clock signal at the original payload transmit rate used at the far end.
This mechanism is referred to as adaptive clock recovery mechanism.
Each pseudowire has its own adaptive timing recovery mechanism, in accordance
with the options listed in RFC4197. The recovered pseudowire clocks can be used
as timing reference signals for the nodal Megaplex-4100 timing subsystem, and
therefore MPW-1 allows flexible timing distribution.
The adaptive clock recovery mechanism estimates the average rate of the
payload data received in the frames arriving from the packet-switched network.
Assuming that the packet-switched network does not lose data, the average rate
at which payload arrives will be equal to the rate at which payload is transmitted
by the source.
Note
Generally, lost packets, as well as packets that did not arrive in the correct order,
are replaced by special dummy packets. However, for CESoPSN and SAToPSN,
packets can be reordered.
The method used to recover the payload clock of a pseudowire is based on
monitoring the fill level of the selected pseudowire jitter buffer: the clock
recovery mechanism monitors the buffer fill level, and generates a read-out clock
signal with adjustable frequency. The frequency of this clock signal is adjusted so
as to read frames out of the buffer at a rate that keeps the jitter buffer as near
as possible to the half-full mark. This condition can be maintained only when the
Pseudowires
5-255
rate at which frames are loaded into the buffer is equal to the rate at which
frames are removed. Therefore, the adaptive clock recovery mechanism actually
recovers the original payload transmit clock.
The performance of the clock recovery mechanism can be optimized for the
operating environment, by specifying the following parameters:
The accuracy of the original timing source, in accordance with the standard
SDH/SONET terminology (Stratum 1, 2, 3, 3E, or 4/unknown)
The type of PSN that transports the traffic: router-based network (for
example, UDP/IP) versus switch-based network (for example, MPLS/Ethernet).
Handling of transient conditions: even after the adaptive clock recovery

mechanism reaches a stable state, there may still be temporary changes in
the network delay, which may occur on a timescale that does not allow for
the mechanism to fully readjust. To provide the best possible user experience,
the user can specify how to handle such transient conditions (a capability
referred to as delay sensitivity):
By disabling delay sensitivity, performance is optimized for accurate clock

recovery. This selection is optimal for data transmission applications.
By enabling delay sensitivity, performance is optimized for constant delay.

This selection is optimal for voice transmission applications.
You can select a total of 10 pseudowire recovered clocks per Megaplex-4100.

For HDLCoPSN pseudowires, it is not necessary to restore the original data rate,
because only useful HDLC payload (extracted from some of the HDLC frames
reaching each endpoint) is transferred through the pseudowire, as explained in
the HDLCoPSN Processing section. Therefore, the payload, which requires only a
fraction of the available bandwidth, can be reinserted in timeslots at the receiving
endpoint rate, without requiring any clock adaptation mechanism.
OAM Protocol
The RAD proprietary implementation of the OAM connectivity protocol enables
detecting loss of communication with the pseudowire destination and taking
steps that prevent the resulting flooding. The protocol also enables checking that
the destination uses a compatible configuration.
The OAM protocol is used to check for a valid pseudowire connection: this
includes checks for compatible configuration parameters at the packet processors
at the two endpoints of a pseudowire, and detection of inactive pseudowire
status.
The information regarding the pseudowire state is collected by the continuous,
periodic handshake between the two endpoints of a pseudowire, which
generates little traffic, but ensures that each endpoint recognizes the
connection, and that it is enabled. In case no response is received to OAM
packets within a predefined interval (a few tens of seconds), the pseudowire is
declared inactive.
When the use of the OAM protocol is enabled, little traffic flows until the
connection between the two pseudowire endpoints is established: only after the
connection is confirmed by the OAM exchange is transmission at the normal (full)
rate started, and the pseudowire starts carrying traffic. In case the connection is
lost, the transmitted traffic is again significantly decreased (several packets per
5-256
Pseudowires
second per connection). Therefore, the OAM connectivity check also prevents
network flooding in case the connection is lost.
OAM packets sent by MPW-1 are identified in accordance with the source port:
the OAM packets run over a UDP port number (see the Determining UDP Port
Numbers Used by Pseudowires section) that is assigned only to OAM traffic, but
use the VLAN ID and ToS of the originating connection.
Factory Defaults
By default, no pseudowires are configured: you must define your own in
accordance with your application requirements. Other parameter defaults are
listed in the table below.
Parameter
Default Value
psn
udp-over-ip
type
tdmoip-v2
exp-bits
tos
tunnel-index
0 (for ingress and egress)
Jitter-buffer [sec}
2500
tdm-payload
sensitivity
disabled
oam
enabled
vlan priority
label
For udp-over-ip: same as the PW index

number
For mpls: PW index number + 15
oos parameters:
far-end-type
signaling
e1
force-idle
data
00
voice
00
Configuring Pseudowires
New pseudowire bundles are added by defining their number (1640), type
(connection mode) and a PSN type.
Pseudowires
5-257
Note
If you need to know the number of the source UDP port of a bundle, you can find
it as follows (unless noted otherwise, all numbers are in hexadecimal notation):
For TDMoIP (CE) bundles using packet payload Version V1:
During normal operation, the source UDP port is given by:
UDP Source Port = 1 + Destination PW Number
This means that during normal operation, the UDP ports numbers are in the
range of 0 to 8191 decimal.
While the bundle is in the local fail state, the source UDP port changes to:
This means that in the local fail state, the UDP ports numbers are higher than
8000 hexa (32768 decimal).
For TDMoIP (CE) bundles using packet payload Version V2:
This means that all the UDP ports numbers are higher than 2000 hexa (8192
decimal).
For CESoPSN and SAToPSN bundles using packet payload Version V2:
UDP Source Port = C000 + Destination PW Number
This means that all the UDP ports numbers are higher than C000 hexa (49152
decimal).
To define and configure a pseudowire:

1. At the config>pwe# prompt, enter the syntax illustrated in the table below.
The config>pwe>pw(<pw-number>)# prompt appears.
5-258
Pseudowires
Task
Command
Comments
Assigning the
pseudowire number,
selecting the
encapsulation protocol
for the selected
pseudowire and
specifying the PSN
type (selecting the
type of PSN header)
pw <pw-number> [type {cespsn-data | e1satop | hdlc |

tdmoip-v1 | tdmoip-v2]
[psn {mpls | udp-over-ip}]
PW number: 1..640
PW type (must be configured for the first time):
hdlc: carrying HDLC traffic using the HDLCoPSN

protocol
tdmoip-v1: TDMoPSN circuit emulation for

carrying data and voice timeslots, old packet
payload format, can only be used for TDMoIP CE
pseudowires (for example, when working with
MP-2100 ML-IP module and old IPmux devices).
This version requires two UDP sockets per
pseudowire.
tdmoip-v2: TDMoPSN circuit emulation for

carrying data and voice timeslots, current packet
payload format. This version requires a single
UDP socket per pseudowire.
e1satop: SAToPSN protocol, for carrying

unframed E1 data streams
ces-psn-data: CESoPSN protocol, for carrying

framed data streams
psn (must be configured for the first time):
udp-over-ip UDP over IP
mpls MPLS over Ethernet with standard packet

structure. In this case, only TDMoIP Version V2 is
used
Using no before pw <number> deletes the bundle
At the config>pwe>pw(<pw-number>)# prompt, enter the parameters specified

in the table below.
Task
Command
Assigning a name to the

pseudowire
name <up to 32
characters>
Comments
Pseudowires
5-259
Task
Command
Comments
Specifying the PW label used

in the inbound and
outbound directions
label [in <number>]

[out < number>]
Out PW label:
For udp-over-ip: Specifies the UDP source port

number used by the pseudowire
For mpls: Specifies the outer (tunnel) MPLS label

used by the pseudowire.
In PW label:
For udp-over-ip: Specifies the UDP destination

port number used by the pseudowire
For mpls: Specifies the inbound MPLS label used

by the pseudowire.
Each PW must have a unique in (source) label.

Do not reuse the same out (destination) value on
bundles terminating at the same peer, and/or using
the same VLAN ID (when VLAN tagging is enabled).
For udp-over-ip, the allowed range is 1 to 8063.
For mpls, the allowed range is 16 to 1048575.
Specifying the type of
framing used by the
equipment at the
destination endpoint. The
selected value also
determines the encoding
law used on PCM voice
channels
far-end-type {e1 | t1esf | t1-sf | unframed}
e1 E1 stream with G.704 framing. The PCM signals

are processed assuming that they are encoded in
accordance with the A-law. You can use this
selection when the port line-type is a framed
version.
t1-esf T1 stream with ESF framing. The PCM signals
are processed assuming that they are encoded in
accordance with the -law. You can use this
selection when the port line-type is a framed
version.
t1-sf T1 stream with SF (D4) framing. The PCM
signals are processed assuming that they are
encoded in accordance with the -law. You can use
this selection when the port line-type is a framed
version.
unframed unframed data stream, transparently
transferred. You can use this selection when the
port line-type is unframed. This is the only selection
for SAToPSN pseudowires, but it is not allowed for
CESoPSN pseudowires.
For the PWs on the same module, make sure to
select the same value at both end points.
The selected value must also match the line-type
configured for the physical port of the pseudowire
local endpoint
This parameter is not relevant for HDLCoPSN
pseudowires
5-260
Pseudowires
Task
Command
Comments
Optimizing the clock

recovery mechanism of the
selected pseudowire for
constant delay. This
selection is optimal for voice
transmission applications
sensitivity
Use no sensitivity to optimize the clock mechanism

for accurate clock recovery. This selection is optimal
for data transmission applications.
Transmitting an
out-of-service signal (OOS)
on PW failure and selecting
the code transmitted by the
port during out-of-service
periods on the timeslots
defined as data and voice
timeslots.
tdm-oos [voice <00 to

FF (hexa)>] [data <00
to FF (hexa)>]
[signaling {force-idle |
force-busy} ]

pseudowires
tdm-oos voice and data are hexadecimal numbers in
the range of 00 to FF (two digits).
The selected code for data is also sent during
out-of-service periods instead of the external data
stream when the unframed mode is used
The voice OOS parameter is relevant neither for
HDLCoPSN pseudowires, nor when the port uses the
unframed mode.
signaling - Determines the state of the signaling bits
sent to the internal DS1 port connected to the
selected pseudowire during out-of-service periods
(relevant only when the attached internal DS1 port is
configured with signaling enabled):
Defining the jitter buffer

size in msec
jitter-buffer <value in
sec>
force-idle The signaling bits are forced to the

idle state (05 hexa) during out-of-service periods.
force-busy The signaling bits are forced to the

busy state (0F hexa) during out-of-service
periods.
Use the shortest feasible buffer, to minimize

connection latency
The allowed range depends on the framing mode:
framed: 2500 to 200000 sec, in 1-sec steps.
unframed: 500 to 200000 sec, in 1-sec steps.

pseudowires
Enabling/disabling the OAM
connectivity protocol for this
PW
oam
Defining a remote peer

terminating this PW
peer <peer number>
The selection must be compatible with the

equipment at the far end of the connection
For pseudowires defined on redundant internal DS1
ports, make sure to select the same OAM mode.
Using no oam disables the OAM protocol
Range: from 1 to 100.
Using no peer removes the remote peer
Pseudowires
5-261
Task
Command
Comments
Specifying the number of

TDM payload bytes to be
inserted in each packet
tdm-payload <130>
A larger value increases the bandwidth utilization

efficiency, but also increases the connection intrinsic
latency, in particular when the bundle is configured
to carry a small number of timeslots.
Refer to the Selection Guidelines for TDM Payload
Bytes per Frame section in Appendix B for selection
consideration.
The number is specified as a multiple of 48 bytes, for
example, 1 means 48 bytes, and 30 means 1440
bytes.
The available selections for TDMoIP are 1 to 30 (48
to 1440 bytes, respectively), and the values for
CESoPSN are 4 to 360.
pseudowires.
Specifying the value for the

TOS byte used on outbound
traffic
tos <tos number>
This parameter is relevant only when psn is

udp-over-ip.
Range: from 1 to 255.
In accordance with RFC 2474, it is recommended to
use only values which are multiples of 4.
Eabling and configuring

VLAN tagging and priority on
every transmitted packet
vlan [id <0..4094>]

[priority <0..7>]
VLAN ID: The allowed range is 1 to 4094. 0 means

that no VLAN ID has been selected.
The selected VLAN ID must be unique per router
interface, but can be reused on different interfaces.
VLAN priority: The allowed range in accordance with
IEEE 802.1p is 7 (highest priority) to 0 (lowest
priority).
Specifying the value of the

outbound EXP bits that
indicate the requested
quality of service in the
MPLS header of the
pseudowire
exp-bits <exp-bit
number>
Enabling and specifying the

ingress and egress MLPS
tunnel indices
tunnel-index [ingress
<ingress-label>]
[egress <egresslabel>]
The allowed range is 7 (highest priority) to 0 (lowest

priority).
Applies only to MPLS PSN.
Relevant for MPLS PSN only

Configuring an inbound label for each pseudowire is
mandatory. When no outbound label is configured,
the inbound label is also used as the outbound label.
The supported range is 16 to 1048575. 0 means
that no label has been defined
Adding no before the command removes the labels
5-262
Pseudowires
Examples
To configure a TDMoIP PW with UDP/IP network encapsulation:
PW number 1
PW type TDMoIP (v2)
PSN type UDP/IP
Out (destination) label 3
In (source) label 2
Far end type E1
Jitter buffer 10 000
OAM enabled
Peer 1
TDM payload size 10 (480 bytes).
mp4100>config>pwe# pw 1
mp4100>config>pwe>pw(1)
type tdmoip-v2 psn udp-over-ip

label out 3 in 2
far-end-type e1
jitter-buffer 10000
oam
peer 1
tdm-payload 10
To configure a SAToP PW with UDP/IP network encapsulation:
PW number 1
PW type SAToP
PSN type UDP/IP
Out (destination) label 3
In (source) label 2
Jitter buffer 10 000
Peer 1 (further configuration under configure>peer)
TDM payload size 30.
type e1satop psn udp-over-ip

label out 3 in 2
far-end-type unframed
jitter-buffer 10000
peer 1
tdm-payload 30
Displaying PW Statistics
PW ports of Megaplex-4100 feature the collection of statistical diagnostics,
thereby allowing the carrier to monitor the transmission performance of the links.
The pseudowire transmission statistics enable analyzing pseudowire traffic
volume, evaluate the end-to-end transmission quality (as indicated by sequence
Pseudowires
5-263
errors), and jitter buffer performance. By resetting the status data at the desired
instant, it is possible to ensure that only current, valid data is taken into
consideration.
To display the PW statistics:
At the prompt config>slot>pwe>pw(<PW number>)#, enter show statistics

Task
Command
Comments
Displaying
statistics
current - Displays the current statistics
all-intervals Displays statistics for all

valid intervals (without current statistics)
total-counters - Displays total statistics of

last 96 intervals
PW statistics are displayed. The counters are described in Table 5-23,

Table 5-24 and Table 5-25. For example:
Current Statistics:
mp4100>config>pwe>pw(1)# show statistics current
Current
--------------------------------------------------------------Time Elapsed (Sec)
: 412
Sequence Errors Seconds
: 0
Jitter Buffer Underflows Seconds
: 1
Jitter Buffer Overflows Seconds
: 2
Min Jitter Buffer Level (uSec)
: 2000
Max Jitter Buffer Level (uSec)
: 12000
Max Jitter Buffer Deviation (uSec) : 9500
All Intervals Statistics:
mp4100>config>pwe>pw(1)# show statistics all-intervals
All
--------------------------------------------------------------Valid Intervals
: 10
: 0
Jitter Buffer Underflows Seconds
: 1
Jitter Buffer Overflows Seconds
: 2
Min Jitter Buffer Level (uSec)
: 2000
Max Jitter Buffer Level (uSec)
: 12000
Max Jitter Buffer Deviation (uSec) : 12000
Total Counters Statistics:
5-264
Pseudowires
mp4100>config>pwe>pw(1)# show statistics total-counters

Total
--------------------------------------------------------------Tx Frames
: 291225
Rx Frames
: 288995
: 0
Jitter Buffer Underflows Seconds : 1
Jitter Buffer Overflows Seconds : 0
Table 5-53. PWE Statistics Parameters Current 15-Minute Interval

Parameter
Description
Time Elapsed (Sec)
The range is 1 to 900 seconds
Sequence Errors
Seconds
Displays the number of seconds during which sequence errors have been detected.
In accordance with the applicable standards, the transmitted packets carry a sequence
number that is automatically assigned, such that consecutive packets are
automatically consecutive sequence numbers. At the receive side, these numbers are
checked by the receive mechanism, which expects each new incoming packet to carry
the next number in the sequence, relative to the previous one (i.e., packet 5 must be
received after packet 4). Any deviation from the this rule indicates a problem with
packet flow integrity (and hence with the pseudowire payload (data or voice)
integrity), and in this case the sequence errors count is incremented by 1.
There are two main reasons for a sequence error event:
Jitter Buffer
Underflows
Seconds
One or more packets have been lost somewhere in the network.
Packets have been reordered within the network. Packet reordering may occur due
to queuing mechanisms, rerouting by the network, or when the router updates
include very large routing tables
Displays the number of seconds during which at least one jitter buffer underflow
event has been detected (not relevant for HDLC pseudowires).
MPW-1 is equipped with a Packet Delay Variation Tolerance buffer, also called a jitter
buffer, which is used to automatically compensate for packet network delay variation
(jitter). Each pseudowire has its own jitter buffer. Although packets leave the
transmitting MPW-1 at a constant rate, they will usually reach the far end at a rate
which is not constant, because in practice the network transmission delay varies (due
to factors such as congestion, rerouting, queuing mechanisms, transport over
wireless or half-duplex media, etc.).
TDM equipment at both ends of a pseudowire require a constant flow of data, and
cannot tolerate delay variation. Therefore, the receive side jitter buffer is required to
provide the TDM equipment with a synchronous and constant flow.
For this purpose, when a pseudowire is set up (and at any time after communication
is restored), the jitter buffer is loaded with packets up to its middle point: only after
this point it starts outputting TDM data towards the connected TDM equipment. The
stored packets assure that the TDM equipment will continue receiving data even if the
network delay momentarily increases. Obviously, if packets are delayed too long, the
buffer is gradually emptied out until it underflows (this situation is called buffer
starvation, and it affects the end-to-end voice/data integrity).
Each underflow event increases the jitter buffer underflow counter by 1.
Pseudowires
5-265
Parameter
Description
Jitter Buffer
Overflows Seconds
Displays the number of seconds during which at least one jitter buffer overflow event
has been detected (not relevant for HDLC pseudowires).
As explained above, during steady state, the jitter buffer is filled up to its middle
point, which means that it has space to hold additional packets. An overflow will occur
when the network delay suddently decreases, for example, when a large burst of
packets reaches the MPW-1. If the burst includes more packets than the jitter buffer
can store at that instant, the buffer will be filled up to its top. In this case, an
unknown number of excess packets are dropped. To correct the situation, Megaplex4100 initiates a forced underflow by flushing (emptying) the buffer. Therefore, an
overflow always results in an immediate underflow. After the buffer is flushed, the
process of filling up the buffer is started again
Min Jitter Buffer

Level (usec)
Actual minimum size of the jitter buffer recorded for this pseudowire in the selected
interval, in sec (not relevant for HDLC pseudowires).
Max Jitter Buffer

Level (usec)
Actual maximum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer

Deviation (usec)
The maximum jitter buffer deviation (variation of delay, in sec) reported during the
selected interval (not relevant for HDLC pseudowires). This is the maximum jitter level
that had to be compensated for in the selected interval
Table 5-54. PWE Statistics Parameters All Intervals Statistics

Parameter
Description
Valid Intervals
displayed, not including the current (not finished) interval (up to 96)
Sequence Errors
Seconds
Displays the number of seconds during which sequence errors have been detected.
In accordance with the applicable standards, the transmitted packets carry a sequence
number that is automatically assigned, such that consecutive packets are
automatically consecutive sequence numbers. At the receive side, these numbers are
checked by the receive mechanism, which expects each new incoming packet to carry
the next number in the sequence, relative to the previous one (i.e., packet 5 must be
received after packet 4). Any deviation from the this rule indicates a problem with
packet flow integrity (and hence with the pseudowire payload (data or voice)
integrity), and in this case the sequence errors count is incremented by 1.
There are two main reasons for a sequence error event:
5-266
Pseudowires
One or more packets have been lost somewhere in the network.
Packets have been reordered within the network. Packet reordering may occur due
to queuing mechanisms, rerouting by the network, or when the router updates
include very large routing tables
Parameter
Description
Jitter Buffer
Underflows
Seconds
Displays the number of seconds during which at least one jitter buffer underflow
event has been detected (not relevant for HDLC pseudowires).
MPW-1 is equipped with a Packet Delay Variation Tolerance buffer, also called a jitter
buffer, which is used to automatically compensate for packet network delay variation
(jitter). Each pseudowire has its own jitter buffer. Although packets leave the
transmitting MPW-1 at a constant rate, they will usually reach the far end at a rate
which is not constant, because in practice the network transmission delay varies (due
to factors such as congestion, rerouting, queuing mechanisms, transport over
wireless or half-duplex media, etc.).
TDM equipment at both ends of a pseudowire require a constant flow of data, and
cannot tolerate delay variation. Therefore, the receive side jitter buffer is required to
provide the TDM equipment with a synchronous and constant flow.
For this purpose, when a pseudowire is set up (and at any time after communication
is restored), the jitter buffer is loaded with packets up to its middle point: only after
this point it starts outputting TDM data towards the connected TDM equipment. The
stored packets assure that the TDM equipment will continue receiving data even if the
network delay momentarily increases. Obviously, if packets are delayed too long, the
buffer is gradually emptied out until it underflows (this situation is called buffer
starvation, and it affects the end-to-end voice/data integrity).
Each underflow event increases the jitter buffer underflow counter by 1.
Jitter Buffer
Overflows Seconds
Displays the number of seconds during which at least one jitter buffer overflow event
has been detected (not relevant for HDLC pseudowires).
As explained above, during steady state, the jitter buffer is filled up to its middle
point, which means that it has space to hold additional packets. An overflow will occur
when the network delay suddently decreases, for example, when a large burst of
packets reaches the MPW-1. If the burst includes more packets than the jitter buffer
can store at that instant, the buffer will be filled up to its top. In this case, an
unknown number of excess packets are dropped. To correct the situation, Megaplex4100 initiates a forced underflow by flushing (emptying) the buffer. Therefore, an
overflow always results in an immediate underflow. After the buffer is flushed, the
process of filling up the buffer is started again
Min Jitter Buffer

Level (usec)
Actual minimum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer

Level (usec)
Actual maximum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer

Deviation (usec)
The maximum jitter buffer deviation (variation of delay, in sec) reported during the
selected interval (not relevant for HDLC pseudowires). This is the maximum jitter level
that had to be compensated for in the selected interval
Table 5-55. PWE Statistics Parameters Total Counters

Parameter
Description
Tx Frames
Total number of frames transmitted toward the PSN
Rx Frames
Total number of frames received from the PSN
Total number of seconds during which sequence errors have been detected.
Pseudowires
5-267
Parameter
Description
Jitter Buffer Underflows

Seconds
Total number of jitter buffer underflow events (not relevant for HDLC
pseudowires).
Jitter Buffer Overflows

Seconds
Total number of jitter buffer overflow events (not relevant for HDLC
pseudowires).
Clearing Statistics
To clear the PW statistics:
At the prompt config>pwe>pw<PW number>)#, enter clear-statistics.

The statistics for the specified PW are cleared.
Viewing the Pseudowire Status and Summary
To display a single PW status:

1. At the config#pwe prompt, enter the desired pseudowire (pw <number>).
The config>pwe>pw(<number>)$ prompt appears.
Enter show status.
The status screen appears. For information on the connectivity status
values, refer to the table below.
mp4100>config# pwe
mp4100>config>pwe>pw(1)# show status
PW : 1
Name
PW Type
PSN Type
Connectivity Status
Out Label
In Label
Peer IP Address
Next Hop MAC Address
:
:
:
:
:
:
:
:
pw-1
CES PSN Data
UDP Over IP
Up
1
1
0.0.0.0
00-00-00-00-00-00
Table 4-43 explains the connectivity status values of the selected pseudowire.
Table 4-43. Pseudowire Connectivity Status Values
5-268
Pseudowires
Parameter
Displayed
Description
Disable
The pseudowire is disabled
Up
The pseudowire carries traffic, and both the remote and the local
pseudowire endpoints receive Ethernet frames. However, there
may be problems such as sequence errors, underflows, overflows,
etc., which may be displayed using the Statistics function.
Parameter
Displayed
Description
Unavailable
The pseudowire reports loss of connectivity (it did not receive

neither OAM, nor data packets for 10 seconds or more (OAM link
then reports loss of synchronization). This is often caused by
network problems, or configuration errors.
Down
The pseudowire is waiting for timeslot assignment
Local Fail
A failure has been detected at the local pseudowire endpoint.
Remote Fail
A failure is reported by the remote pseudowire endpoint.
Validation Fail
The remote pseudowire endpoint replied to OAM packets, but

there is a configuration mismatch (the configuration parameters
used at two endpoints of the pseudowire are different).
To display PW configuration summary:
At the config>pwe# prompt, enter the show pw-summary command.
For example:
mp4100>config>pwe# show pw-summary
PW
PSN Type
Out Label
Peer
Peer IP Address
Jitter Buffer
:
:
:
:
:
:
1
UDP Over IP
1
1
10.10.10.200
2500
PW Type
Status
In Label
Next Hop MAC
Payload Size
: CES PSN Data

: Up
: 1
Address: 00-00-00-00-00-00
: 5
5.38 Cross-Connections
The matrix in the figure below describes all possible cross-connections you can
perform in the Megaplex-4100.
Cross-Connections
5-269
Figure 5-40. Cross-Connections in Megaplex-4100

The matrix cells are color-coded to indicate which option (command) to choose
for the various modules/ports/timeslots/entities at both ends, as follows:
Color
Command
Meaning
ds0, tdm, split-ts
cross-connect on the DS0 or DS1 level and/or split timeslot cross-connect
ds0
cross-connect on the DS0 level (no split timeslot cross-connect)
ds0, tdm
cross-connect on the DS0 level and/or split timeslot cross-connect
LRS-102 Optimux modules only, fixed local cross-connect
bind
cross-connect for Ethernet-over-TDM traffic
sdh-sonet
SDH/SONET cross-connect
pw-tdm
Pseudowire cross-connect on DS1 level

A number inside the cell refers to a special note regarding this type of
cross-connect.
5-270
Cross-Connections
Examples of using the table:
To cross-connect an e1-i port of an M8SL module to an e1-i port on the CL.2

module you have to use ds0 cross-connect.
To cross-connect a t1-i port to vt1.5 virtual tributary or e1-i to sdh, you have
to use sdh-sonet cross-connect
To cross-connect the entire e1 port traffic of an M16E1 module transparently

to vc-12, you have to use sdh-sonet mapping
To cross-connect the entire e1 port traffic of an M16E1 module transparently

to vc-12, you have to use sdh-sonet mapping
To map the entire e1 port to an e1-i port, you can use either ds1 or ds0
cross-connect
To cross-connect an hdlc port to e1, you have to use the bind command
To cross-connect unframed stream, you have to use the ds1 command.
Split timeslot cross-connect is possible for the same ports where ds0
cross-connect is used, when working with the following modules: HSU-6/HSU-12,
HS-S, HS-RN, VC-4A, VC-8A, LS-6N/LS-12. HS-6N/12N, HS-703, HSF-2 and
VC-4/OMNI modules do not support split timeslot cross-connect.
Cross-Connect Types
The DS0 cross-connect matrix supports two cross-connect types, selectable at
the level of the individual E1 and T1 port:
DS0 cross-connect mode used when it is necessary to control the routing of

individual timeslots, and therefore it is relevant only when using a framed
mode. This cross-connect mode is also needed for handling the inband
management timeslot (see E1 Ports and T1 Ports sections for description). In
the DS0 cross-connect mode, Megaplex-4100 enables connecting payload
and signaling between all kinds of E1, T1, E1-I, T1-i, voice, serial or HDLC
ports.
DS1 (TDM) cross-connect mode this cross-connect mode is used when it is

necessary to transparently transfer entire E1 or T1 streams on external and
internal ports. This is needed for unframed streams. In the DS1 cross-connect
mode, E1 ports can be mapped only to other E1 ports (including SDH E1-i
ports), and T1 ports can be mapped only to other T1 ports (including SONET
E1-i ports).
Timeslot Types
When configuring the cross-connect, it is necessary to instruct each port how to
handle the traffic flow and signaling information. This is performed by defining
the timeslot type.
The selections are as follows:
data: the timeslot is handled as a data channel. This means that any signaling
information associated with the channel is ignored.
Cross-Connections
5-271
voice: the timeslot is handled as a voice channel. This means two things:
It is necessary to select a link framing mode that supports channel

associated signaling, e.g., G.704 multiframe (G.732S) for E1, SF (D4) or
ESF for T1.
The signaling information of the channel is routed (automatically) in

parallel with the channel payload.
Full Timeslot versus Split Timeslot Assignment (Split Timeslot

Cross-Connect)
For user ports that do not require a full timeslot (eight bits, equivalent to a
bandwidth of 64 kbps), Megaplex-4100 also permits split timeslot assignment,
that is, assignment of individual bits in a selected timeslot.
Split timeslot assignment increases the bandwidth utilization efficiency for TDM
modules or channels, because it enables the allocation of link bandwidth in
smaller (sub-DS0) units: the split timeslot assignment unit is 16 kbps (a pair of
consecutive bits in a timeslot).
Split timeslot assignment is supported by voice modules (ADPCM encoding), lowspeed data modules, and ISDN modules.
The split timeslot assignment is performed in coordination with the modules
having sub-DS0 ports. It is not possible to mix bits from different modules in the
same DS0 timeslot.
Bidirectional Transfer Mode

The bidirectional transfer mode is used to transfer data/voice simultaneously in
both receive and transmit directions.
Unidirectional Broadcast Function

The unidirectional broadcast mode enables a user at a central location to send
data or voice to multiple users connected to remote ports via the Megaplex-4100
links (simplex communication). In this mode, any message is simultaneously
received by all the remote unidirectional users, but none of them can send back
data to the originator.
This capability is achieved by separating the handling of the receive and transmit
paths for timeslots assigned to unidirectional channels.
You can specify the operating mode of each unidirectional channel or E1/T1
timeslot either as unidirectional transmit, or unidirectional receive:
Unidirectional transmit: the channel/timeslot transmits, but cannot receive

(its receive path is disconnected). The information transmitted by the channel
can be routed to any number of E1/T1/E1-i/T1-i ports for distribution to
multiple remote Megaplex-4100 units.
Unidirectional receive: the channel/timeslot receives, but cannot transmit (its

transmit path is disconnected). The user can select the source port
(E1/T1/E1-i/T1-i or compatible I/O port) from which the channel receives, and
the specific timeslot. The same source port or a range of timeslots can be
connected to several channels operating in the unidirectional receive mode.
The unidirectional broadcast function is available only for ds0 cross-connect.

5-272
Cross-Connections
The unidirectional broadcast capabilities depend on the module type:
Modules with internal or external E1 and T1 ports (see Table 5-56): the
payload received by a unidirectional broadcast timeslot is distributed in
parallel to multiple destination timeslots of other E1 or T1 links, or to
modules with unidirectional receive capabilities.
Voice and data I/O modules (see Table 5-57): not all the modules support
unidirectional capabilities, but only modules which require a single timeslot
per channel, and that do not require handshaking for setting up a link.
Therefore, unidirectional broadcast is supported by VC-4/4A/8/8A/16 voice
modules with E&M and FXS interfaces, HS-6N/12N or HS-RN data modules, as
well as LS-6N/LS-12 (internal ports). ISDN interface modules cannot support
this capability.
Table 5-56. Unidirectional Broadcast for E1/T1 Ports

I/O Modules
Ports
unidirection-tx
unidirection-rx
CL.2
Internal E1/T1
M8E1/M8T1
M16E1/M16T1
External E1/T1
ASMi-54C/N
M8SL
Internal E1
ASMi-54C/N
External E1/T1
OP-34C/OP-108C
Internal E1
Table 5-57. Unidirectional Broadcast in Voice and Data I/O Modules

I/O Modules
Ports
unidirection-tx
unidirection-rx
VC-4/4A/8/8A/16
FXS & E&M
VC-4/4A/8/8A/16
FXO
HS-U-6, HS-U-12,
HS-S
serial
HS-RN
serial
LS-6N/LS-12
serial
LS-6N/LS-12
serial-bundle
HS-6N/HS-12N
serial
Configuring a DS0 Cross-Connection
To configure a DS0 cross-connection:

1. At the config# prompt, enter cross-connect or cr.
The config>xc# prompt appears.
Configure the cross-connection as illustrated and explained below for the various
interfaces.
Cross-Connections
5-273
Task
Command
Comments
Cross-connecting timeslot x (or

range of sequential timeslots
x1..x2) of the e1/t1/e1-i/t1i/ds1 port to timeslot y (or
starting from y1) on the e1
port and setting its/their type
and direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/[<tributary>] ts
{<x> | <[x1..x2]>} e1
{ts <y> | start-ts <y1>} {data |
voice} [bi-direction | unidirectionrx | unidirection-tx]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/[<tributary>] ts {<x> |
<[x1..x2]>} e1 <slot>/<port>/
[<tributary>] {ts <y> | start-ts <y1>}
removes cross-connection

starting from y1) on the t1
and direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

{<x> | <[x1..x2]>} t1
{ts <y> | start-ts <y1>} {data |
voice} [bi-direction | unidirectionrx | unidirection-tx]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/[<tributary>] ts {<x> |
<]x1..x2]>} t1 <slot>/<port>/
[<tributary>] {ts <y> | start-ts <y1>}
Cross-connecting timeslot x of
the e1/t1/e1-i/t1-i/ds1 port to
a voice port and setting its
direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port> ts <x> voice
<slot>/<port> [bi-direction |
unidirection-rx | unidirection-tx ]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port> ts <x> voice
<slot>/<port> removes
cross-connection
See Examples 3,4
See Examples 3,4
see Examples 1, 5
x1..x2) of the e1/t1/e1-i/t1i/ds1 port to a serial port and
setting its direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port> ts <x> serial
<slot>/<port> [bi-direction |
unidirection-rx | unidirection-tx}

x1..x2) of the e1/t1/e1-i/t1-i
port to an hdlc port (M8E1,
M8T1 modules)
ds0 {e1 | t1 | e1-i | t1-i}

<slot>/<port>/[<tributary>] ts <x>
hdlc <slot>/<port>
no ds0 {e1 | t1 | e1-i | t1-i}

hdlc <slot>/<port> removes
cross-connection

starting from y1) on the e1-i
and direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

{<x> | <[x1..x2]>} e1-i
<slot>/<port>/[<tributary>] {ts
<y> | start-ts <y1>} {data | voice}
[bi-direction | unidirection-rx |
unidirection-tx]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/
[<tributary>] ts {<x> | <[x1..x2]>}
e1-i <slot>/<port>/ [<tributary>] {ts
<y> | start-ts <y1>} removes crossconnection
5-274
Cross-Connections
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port> ts <x> serial
cross-connection
see Examples 1, 2, 6
See Examples 3,4
Task
Command
Comments

starting from y1) on the t1-i
and direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

{<x> | <[x1..x2]>} t1-i
unidirection-tx]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/
t1-i <slot>/<port>/ [<tributary>] {ts
<y> | start-ts <y1>} removes crossconnection

starting from y1) on the ds1
and direction
ds0 {e1 | t1 | e1-i | t1-i | ds1}

{<x> | <[x1..x2]>} ds1
unidirection-tx]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/
ds1 <slot>/<port>/ [<tributary>]
{ts <y> | start-ts <y1>} removes
cross-connection
bri port (HS-S, HS-U-6,
HS-U-12 modules)
ds0 {e1 | t1 | e1-i | t1-i | ds1}

bri <slot>/<port>/[<tributary>]
Using no before ds0 {e1 | t1 | e1-i |

t1-i | ds1} <slot>/<port>/
[<tributary>] ts <x> bri
<slot>/<port> /[<tributary> removes
cross-connection
serial-bundle port (LS-6N,
LS-12 modules)
ds0 {e1 | t1 | e1-i | t1-i | ds1}

serial-bundle <slot>/<port> [bidirection | unidirection-rx |
unidirection-tx ]
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/
[<tributary>] ts <x> serial-bundle
cross-connection
See Examples 3,4
Note: The optional <tributary> index relates to different cards and denotes different entities, depending on
the ports if follows:
When following {e1 | t1 | e1-i | t1-i | ds1} options, the index relates to Megaplex Optimux cards (OP-34C,
OP-108C) only and denotes their internal E1 ports. Therefore, the cross-connect side involving these
tributary ports is relevant only for e1 port options, not for t1, e1-i, t1-i, or ds1.
When following bri port, the index relates to B1 and B2 channels.
Examples
Below are some examples of using DS0 cross-connect function for different
applications.
Example 1. Bidirectional DS0 Cross-Connect: CL <-> I/O

Modules, Single Timeslot
CL-A, port E1-i port 1/1, timeslot 1 to voice port 8/1
CL-A, port E1-i port 1/1, timeslot 2 to serial port 9/1
Cross-Connections
5-275
config
cr
ds0 e1-i cl-a/1 ts 1 voice 8/1 bi-direction
ds0 e1-i cl-a/1 ts 2 serial 9/1 bi-direction
Example 2. Consecutive Timeslot Assignment: E1/T1/E1-i/T1-i

Port <-> Serial Module Port
In this example the entire traffic from the E1 port 1/1 (M8E1 module) is
transferred to HS-12N port 10/1 and vice versa. The ds0 cross-connect must be
used here since the M8E1 port is configured as framed.
config
cr
ds0 e1 1/1 ts [1..31] serial 10/1 bi-direction
Example 3. Consecutive Timeslot Assignment: Two

E1/T1/E1-i/T1-i I/0 Module Ports
In this example the entire traffic from the E1 port 1/2 (M8E1 module) is
transferred to E1-i port 9/1 (M8SL module) and vice versa. The ds0 cross-connect
must be used here since both ports are configured as framed. Note that in this
case the command must be repeated in both directions.
config
cr
ds0 e1 1/2 ts [1..31] e1-i 9/1 start-ts 1 data bi-direction
ds0 e1-i 9/1 ts [1..31] e1 1/2 start-ts 1 data bi-direction
Example 4. Unidirectional Broadcast: M8E1 Port is Sending

Data to three M8E1 ports using UniRx
Source port (sending data):
M8E1, port 1/1, timeslot 1
Destination ports (receiving data):
M8E1, port 3/1, timeslot 1.
config
cr
ds0 e1 1/2 ts 1 e1 1/1 ts 1 data unidirection-rx
Example 5. Unidirectional Broadcast: Voice Port is Sending

Data to M8E1 Port using UniTx
Sending from:
5-276
VC-16, port 8/1,
Sending to:
Cross-Connections
config
cr
ds0 e1 1/1 ts 1 voice 8/1
unidirection-tx
Example 6. Unidirectional Broadcast: Serial Port is Sending

Data to M8E1 Port using UniTx
Sending from:
HS-6N, port 9/1,
Sending to:
config
cr
ds0 e1 1/2 ts 1 serial 9/1
unidirection-tx
Configuring a TDM Cross-Connection
To configure a TDM cross-connection:

Configure the cross connection as illustrated and explained below for the various
interfaces.
Task
Command
Comments
Cross-connecting the
full payload from this
e1/t1/e1-i/t1-i/serial
port with another port
of the same type and
configuration
tdm {e1 | t1 | e1-i | t1-i } <slot>/<port>

{e1 | t1 | e1-i | t1-i } <slot>/<port>
no tdm {e1 | t1 | e1-i | t1-i }

<slot>/<port> command disables
the cross-connection
full e1 payload from
this tributary port with
another port of the
same type and
configuration
tdm e1 <slot>/<port>/<tributary>
e1 <slot>/<port>/<tributary>
Megaplex Optimux cards (OP-34C,

OP-108C) only
no tdm e1 <slot>/<port>/
<tributary> command disables the
cross-connection
Examples
Example 1
Cross-connecting the full E1 payload
M16E1 module installed in slot 3
E1 port 3 with E1 port 2
Cross-Connections
5-277
mp4100>config>xc# tdm e1 3/2 e1 3/3
Example 2
Port 2, line type G.732S
mp4100>config>port>e1(1/2)# line-type g732s
Cross-connecting E1 port 2 with internal E1 port 1 on CL-A module
mp4100>config>xc# tdm e1 1/2 e1-i cl-a/1
Cross-connecting (mapping) internal E1 port 1 to the SDH:
VC-12 = 2
TUG-3 = 1
TUG-2 = 1
AUG 1 = 1
SDH port 1 on the CL-A module.
mp4100>config# cr sdh-sonet vc12-vt2 cl-a/1/1/1/1/2 e1-i cl-a/1
Configuring a Split Timeslot Cross-Connection
To configure a split timeslot cross-connection:

interfaces.
Task
Command
Comments
timeslot bits of the
e1/t1/e1-i/t1-i/ds1 port
with this voice port
(defining the selected data
rate on the voice port)
split-ts {e1 | t1 | e1-i | t1-i | ds1}

<slot>/<port>/[<tributary>] ts <ts
x> bits <bit y> voice voice
<slot/port[/tributary]>}
Used for VC-4A/VC-8A modules working

in ADPCM mode
no ds0 {e1 | t1 | e1-i | t1-i | ds1}
<slot>/<port>/[<tributary>] ts <ts x>
bits <bit y> voice <slot>/<port>
The entire number of cross-connected
timeslot bits should match the selected
data rate
with this serial port
rate on the serial port)
5-278
Cross-Connections

<slot>/<port>[<tributary>] ts <ts x>
bits <bit y> serial
<slot/port[/tributary]>}
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

bits <bit y> serial <slot>/<port>
data rate
Task
Command
Comments
with this serial-bundle port
rate on the serial-bundle
port)

bits <bit y> serial-bundle
<slot>/<port>}
no ds0 {e1 | t1 | e1-i | t1-i | ds1}

bits <bit y> serial-bundle <slot>/<port>
with this bri port (defining
the selected data rate on
the bri port)

rate-bits <bit y> bri <slot>/<port>
[<tributary>]

data rate
no ds0 {e1 | t1 | e1-i | t1-i | ds1}
rate-bits <bit y> bri <slot>/<port>
[<tributary>] removes cross-connection
data rate
Note: The optional <tributary> index relates to different cards and denotes different entities, depending on
the ports if follows:
When following {e1 | t1 | e1-i | t1-i | ds1} options, the index relates to Megaplex Optimux cards (OP-34C,
OP-108C) only and denotes their internal E1 ports. Therefore, the cross-connect side involving these
tributary ports is relevant only for e1 port options, not for t1, e1-i, t1-i, or ds1.
When following bri port, the index relates to B1 and B2 channels.
Example
The following section illustrates how to configure the HS-RN module installed in
slot 8 and cross-connect its serial ports with timeslot bits of the M8E1 module
installed in slot 1:
Data rate 9.6 kbps on ports 1 and 2.
Cross-connect serial port 1 with bits 1 and 2 of timeslot 1 of E1 port 2 of

M8E1 module installed in slot 1 (total data rate 9.6 kbps on serial port 1)
Cross-connect serial port 2 with bits 1 and 2 of timeslot 1 of E1 port 3 of

the same M8E1 module (total data rate 9.6 kbps on serial port 2)
Cross-connect serial port 3 with bits 1,2,3,4 of timeslot 1 of E1 port 4 of the

same M8E1 module (total data rate 19.2 kbps on serial port 3)
Cross-connect serial port 4 with bits 1,2,3,4 of timeslot 1 of E1 port 5 of the

same M8E1 module (total data rate 19.2 kbps on serial port 4)
The total data rate transferred on the HS-RN module is 57.6 kbps.
Cross-Connections
5-279
mp4100>config# #------------hsr-n---------------mp4100>config# port serial 8/1 no shutdown

mp4100>config# port serial 8/1
mp4100>config>port>serial(8/1)# rate 9.6
mp4100>config>port>serial(8/1)# exit
mp4100>config#
mp4100>config# port serial 8/2 no shutdown
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config# cr
mp4100>config>xc# split-ts e1 1/2 ts 1 bits 1 serial
mp4100>config>xc#
mp4100>config>xc#
mp4100>config>xc#
8/1
8/1
8/2
8/2
8/3
8/3
8/3
8/3
8/4
8/4
8/4
8/4
See more examples in the LS-6N/12 and HSU-6/12 sections of Appendix B.
Configuring an SDH/SONET Cross-Connection
To configure an SDH/SONET cross-connection:

1. At the config# prompt, enter cross-connect.
interfaces.
5-280
Cross-Connections
Task
Command
Comments
Cross-connecting the E1 port

of an I/O module with a
vc12-vt2 from an SDH port
(transparent clocking)
sdh-sonet vc12-vt2 <slot>/<port>/<au4>/

<tug3>/ <tug2>/<vc12-vt2>
e1<slot>/<port> [/tributary]
[/tributary] refers to Megaplex Optimux

cards (OP-34C, OP-108C) only
Adding no before the full command
disables the cross-connection
This command is available only for
unframed E1 links in ASMi-54C/N OP-34C,
OP-108C and M16E1 modules
Cross-connecting the vc12-vt2

from an SDH port with an e1-i
port of an I/O module
sdh-sonet vc12-vt2
<slot>/<port>/<au4>/<tug3>/
<tug2>/<vc12-vt2> e1-i <slot>/<port>

Cross-connecting two vc12-vt2

containers
sdh-sonet vc12-vt2 <slot>/<port>/<au4>/

<tug3>/ <tug2>/<vc12-vt2> vc12-vt2
<slot>/<port>/<au4>/ <tug3>/<tug2>/
<vc12-vt2>

Cross-connecting the T1 port

of an I/O module with a
vc11-vt1.5 from a SONET port
(transparent clocking,
available only for M16T1
modules)
sdh-sonet vc11-vt1.5
<tug2>/<vc11-vt5> t1 <slot>/<port>
vc11-vt1.5 from a SONET port
with a t1-i port of an I/O
module
<tug2>/<vc11-vt1.5> t1-i} <slot>/<port>
Cross-connecting two
vc11-vt1.5 containers
<tug2>/<vc12-vt2> vc11-vt1.5
<tug3>/<tug2>/<vc11-vt1.5>
Cross-connecting two vc3-sts1
sdh-sonet vc3-sts1
<slot>/<port>/<au4>/<tug3> vc3-sts1
<slot>/<port>/<au4>/<tug3>
Cross-connecting two
vc4-sts3c
sdh-sonet vc4-sts3c <slot>/<port>/<au4>

vc4-sts3c <slot>/<port>/<au4>
Examples
Example 1. Direct Transparent Mapping of E1 Links over SDH
M16E1 modules allow direct mapping of E1 links over SDH/SONET in a transparent
mode (this feature is also called transparent clocking).
M16E1 module:
I/O slot 1
Cross-Connections
5-281
E1 port 2
Mapping E1 port 2 to the following VC-12 container:
VC-12 = 1
TUG-3 = 7
TUG-2 = 1
AUG 1 = 1

cr sdh-sonet vc12-vt2 cl-a/1/1/1/7/1
e1 1/2
Example 2. Mapping Framed E1 Link Payload to VC-12

Container
Framed E1 links do not allow direct mapping to SDH. In this case the mapping is
done in two stages: first the E1 port is mapped to an internal E1 port on the CL.2
module and then the internal E1 port is mapped to the SDH.
VC-12 = 2
TUG-3 = 1
TUG-2 = 1
AUG 1 = 1
Configuring a PW-TDM Cross Connection
To configure a pw-tdm cross connection:

interfaces.
5-282
Cross-Connections
Task
Command
Comments
Establishing crossconnection
between this
pseudowire and
timeslots on the
ds1 port
pw-tdm pw <pw number> ds1 <slot>/<port>

[time-slots <ts list>]
The ds1 port should be populated by

using additional ds0 cross-connect
command between ds1 and other
ports in MP-4100 (see example
below)
Timeslots in a list can be separated
by a comma or given as a range, for
example: 1..3, 5.
Using no before the command
removes the cross-connection
Example
This section provides an example on creating a TDM pseudowire cross-connection
between PW 1 and serial HS-12N port:
Pseudowire (PW) 1.
configure cross-connect pw-tdm pw 1 ds1 2/1 time-slots 1

configure cross-connect ds0 ds1 2/1 ts 1 serial 10/1
5.39 Fault Propagation

The fault propagation function can be used to notify equipment at a far end port
that a fault condition has been detected at a local port connected to it.
Fault propagation is supported for compatible types of ports, for example:
Between interconnected external E1/T1, internal E1-i/T1-i or PW ports
Between the Ethernet, PCS, GFP or MLPPP ports.
For each port type, Table 5-58 lists the following:
Failure or alarm conditions at this (failed) port used to initiate a response at

another (affected) port
Response (action) at this port when it is affected (to port in CLI).
Fault Propagation
5-283
Table 5-58. Fault Propagation Response

Port Type
Detected Failure or Alarm Condition
Action at the Port when it is

Affected
GbE
eth los alarm
Disconnecting GbE port
card card_mismatch alarm (module

removed)
eth los alarm

removed)
External Fast
Ethernet (I/O
modules)
Internal Ethernet
(MP Optimux
modules)
mux-eth-tdm los alarm

removed)
GFP
With LCAS: vcg minimum members tca

alarm
Without LCAS: gfp rx_trail_failure

alarm
gfp csf alarm

removed)
ppp bcp_failure alarm

removed)
shdsl lof alarm
shdsl losw alarm

removed)
pw pw_configuration_mismatch alarm
pw pw_oam_failure alarm
pw fe_rdi alarm
pw rx_failure alarm
pw fe_rx_failure alarm

removed)
e1t1 ais alarm
e1t1 lof alarm
e1t1 rai alarm
e1t1 lomf alarm
e1t1 lomf_fe alarm
e1t1 los alarm

removed)
MLPPP
PCS
PW
E1-i/T1-i
(CL.2 module)
5-284
Fault Propagation
Disconnecting the Ethernet port
Disconnecting user Ethernet port of the

remote standalone device
CSF(Client Signal Failure) frame will be

sent instead of idle GFP frames on the
associated VCGs
MLPPP port is down (BCP down)
N/A (can only affect other ports)
Sending of OAM packets with Local Fail

indication (L-bit set) to remote PW
Note: OAM must be enabled.
Sending of AIS
Port Type
Detected Failure or Alarm Condition
Action at the Port when it is

Affected
E1-i (M8SL
module)
e1t1 ais alarm
N/A (can only affect other ports)
e1t1 lof alarm
e1t1 rai alarm
e1t1 lomf alarm
e1t1 lomf_fe alarm
e1t1 los alarm

removed)
e1t1 ais alarm
e1t1 lof alarm
e1t1 rai alarm
e1t1 lomf alarm
e1t1 lomf_fe alarm
e1t1 los alarm

removed)
e1t1 ais alarm
e1t1 lof alarm
e1t1 rai alarm
e1t1 lomf alarm
e1t1 lomf_fe alarm
mux-eth-tdm los alarm

removed)
E1/T1 ports
(M8E1/M8T1,
M16E1/M16T1)
Internal E1/T1
ports (MP Optimux
modules)
Sending of AIS
Sending of AIS by the associated E1

port of the remote standalone device
Factory Defaults
By default, fault propagation is not configured.
Configuring Fault Propagation

Follow this procedure to configure fault propagation:
To add fault propagation for a pair of interfaces:

1. Navigate to configure fault.
Type the command:
fault-propagation <from-interface> to <to-interface>, as shown in
Table 5-59.
The fault propagation in the to direction is established.
Fault Propagation
5-285
Table 5-59. Fault Propagation

Task
Command
Comments
Configuring fault
propagation for
external and internal
e1 and t1 ports
fault-propagation port {e1 | t1 | e1i | t1-i | pw}

to port {e1 | t1 | e1-i | t1-i | pw}
Optional <tributary> index refers only to

e1 ports of Megaplex Optimux cards
(OP-34C, OP-108C)
In the case of a PW participating in the

fault propagation, <slot>/<port>/
[<tributary>] on the corresponding side
must be replaced by <pw number>.
Using no before fault-propagation disables
the command.
Configuring fault
propagation for
ethernet type ports
and pseudowires
fault-propagation port {ethernet |

pcs | gfp | mlppp}
to port {ethernet | gfp | mlppp}
Optional <tributary> index refers only to

ethernet ports of Megaplex Optimux cards
(OP-34C, OP-108C)
The PCS port can be on the from side
only.
Using no before the full command disables
the command.
When configuring fault propagation, the following must be taken into account:
The maximum number of affected ports defined per one failed port is 10
In bidirectional fault propagation, one failed port corresponds to one affected

port and vice versa
The maximum number of fault propagation entries defined in the system is

200
Neither failed nor affected E1/T1/E1-i/T1-i port can be configured

as unframed
An E1/T1/E1-i/T1-i port defined as protection in a TDM protection group

cannot be selected by the user as failed or affected.
If a working port in a TDM protection group is selected as failed or affected,

the protection port is internally added to the fault propagation configuration.
In particular:
If a working port of a TDM group is selected as failed, the port selected

as affected responds only if both working and protection ports fail
If a working port of a TDM group is selected as affected, both working

and protection ports will be affected by the failed port.
5.40 APS Protection

Two SDH/SONET ports can work in APS (Automatic Protection Switching) mode.
The APS configuration allows you to specify the two working ports and their
operational mode, which can comply with one of the standards quoted below.
5-286
APS Protection
Standards
Automatic Protection Switching complies with the following standards:
1+1 unidirectional APS (G.842, Clause 7.1.4.4)
1+1 bidirectional compatible APS (G.841, Clause 7.1).
1+1 bidirectional optimized APS (G.841 Annex B. Linear Multiplex Section

(MSP); compatible with 1:1 bidirectional switching)
Automatic protection switching (APS) is a link-level protection mechanism for
ensuring service continuity in the case of interface failure/error.
In Megaplex-4100, the APS can be configured with the following operating
modes:
1+1 optimized bi-directional mode. You specify two working ports, 1 and 2,
and bind one of the four ports available on CL.2 module (sdh-sonet cl-a/1,
cl-a/2, cl-b/1, cl-b/2) to working port 1 and another one to working port 2
respectively. The protocol used to handle the switching is carried out using
K1 and K2 bytes from the line header of the SONET/SDH frame.
1+1 compatible bi-directional mode. You specify a working port and a

protection port. Bind one of the four ports available on CL.2 module (sdhsonet cl-a/1, cl-a/2, cl-b/1, cl-b/2) to the working port and another one to
the protection port respectively. The protocol used to handle the switching is
carried out using K1 and K2 bytes from the line header of the SONET/SDH
frame.
1+1 unidirectional mode. You specify a working port and a protection port.
Bind one of the four ports available on CL.2 module (sdh-sonet cl-a/1, cl-a/2,
cl-b/1, cl-b/2) to the working port and another one to the protection port
respectively. The protocol used to handle the switching is carried out using
SDH/SONET alarms.
The alarm criteria taken into consideration for protection switching are grouped
into two categories: major alarm and minor alarm.
The major alarms are caused by any of the following:
An SFP is removed from the socket
Loss of SDH/SONET line signal is detected
Loss of SDH/SONET frame is reported
AIS signal is received on the line
OOS condition is reported.
The minor alarms are caused by the following:
EED (excessive error degradation). The EED threshold can be selected by the
user.
SD (signal degraded) condition, where the threshold can be selected by the

user. However, the user can configure APS parameters to ignore the SD
criterion.
APS Protection
5-287
Forced-flip command.
The working port always carries the traffic, as long as its total alarm weight does
not exceed that of the protection. The user can force switching (flipping) to the
other port by a manual flip command.
The two ports in an APS group can be assigned priorities. Megaplex-4100 will
generate alarm messages to notify managers (supervision terminal, Telnet hosts,
management stations, etc.) that protection switching from the high priority port to
the low priority port, or vice versa, occurred.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
Non-revertive mode the CL module will not automatically flip back after the
failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
However, as explained above, the user can always initiate flipping back by a
manual flip command.
Revertive mode the CL module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
To prevent switching under marginal conditions, the user can specify a

restoration time (wait-to-restore). This is the minimum interval before flipping
back to the original port. During the restoration time, alarms with the same
weight, or with lower weights, are ignored. As a result, the module starts
evaluating the criteria for protection switching (flipping) only after the
restoration time expires, thereby ensuring that another flip cannot occur before
the specified time expires.
However, if an alarm with a weight exceeding that of the alarm which caused
flipping appears, immediate flipping will occur, even if the restoration time has
not yet expired.
Factory Defaults
In Revertive mode, the wait-to-restore time is 300 sec.
Configuring Automatic Protection Switching

Adding and Removing an APS Group
To add and define an APS group:

1. At the config> prompt, enter protection.
The config>protection# prompt appears.
Enter aps <group name>. The group name may consist of up to 80 alphanumeric
characters.
The APS group is defined and enabled and the
config>protection>aps(<group name>)# prompt appears.
5-288
APS Protection
To remove an APS group:
At the config>protection# prompt, enter no aps <group name>.

The APS group is removed.
Binding Ports to an APS Group

Before you can bind ports to the APS group, you have to first specify the desired
operation mode.
To specify the operation mode:
At the config>protection>aps(<group name>)# prompt, enter

oper-mode {uni-directional | optimized-1-plus-1 | compatible-1-plus-1}.
You are now able to bind a port to the APS group.
To define the working ports for the APS group if optimized-1-plus-1 is selected:
1. At the config>protection>aps <group name># prompt, enter
bind working 1 sdh-sonet <slot><port>.
Working port 1 is bound to the APS group.
bind working 2 sdh-sonet <slot><port>.
Working port 2 is bound to the APS group.
To bind the working and protecting ports to the APS group if compatible-1-plus-1
or uni-directional is selected:
bind working sdh-sonet <slot><port>.
The working port is bound to the APS group.
At the config>protection>aps <group name># prompt, enter
bind protection sdh-sonet <slot><port>.
The protection port is bound to the APS group.
To configure the SDH/SONET APS:
At the config>protection>aps(group name)# prompt, enter all necessary

Task
Command
Comments
Activating the APS group
no shutdown
Using shutdown switches the

APS to standby mode
Defining operation mode of the

APS
oper-mode {unidirectional | optimized1-plus-1 | compatible-1plus-1}
APS Protection
5-289
Task
Command
Comments
Adding a working port to the APS

group (compatible 1+1 and
unidirectional modes)
bind { working |
protection } sdh-sonet
<slot/port>
Available for the compatible 1+1 and

unidirectional modes
Adding a working port to the APS

group (1+1 optimized bidirectional
mode)
bind working {1 | 2} sdh

-sonet <slot/port>
Available for the 1+1 optimized bidirectional mode.
Enabling the reverting of the

working and protection ports (not
available in 1+1 optimized mode)
revertive
Using no revertive disables the reverting
Defining the wait-to-restore

period for the revertive recovery
mode (the time to elapse
after the link recovery
before traffic switches back)
wait-to-restore <1
720>
The unit of time is seconds
Enabling the flip of the two

SDH/SONET ports upon signal
degradation
flip-upon-sd
Using no flip-upon-sd disables the flip
Forced switching of traffic

from the working link to
protection link
force-switch
Manual switching of traffic

from the working link to
protection link
manual-switch
Freezing the transmitted K-bytes

and the selector's position.
lockout
Using no bind { working | protection }

removes a port from APS group
Using no bind { working | protection }

removes a port from APS group
The switchover will stay active disregarding

the physical status of the link

The switchover is temporary (one-time) and
the traffic will be switched back according
to the physical status of the link
Available only for the 1+1 optimized
bidirectional mode.
In this case, the traffic is retrieved from the
port which is currently the working port
until the lockout is cleared. Lockout is
considered a local request that is not
signaled over the K-bytes.
Denying access of all traffic

signals to the protection port by
issuing a "Lockout of protection"
request, unless an equal
protection switch command is in
effect
5-290
APS Protection
lockout-of-protection
Available only in compatible 1+1 and

Task
Command
Comments
Clearing the current command

(Force Switch or Lockout).
clear
Available only for the 1+1 optimized bidirectional mode.
If you clear the 'Lockout' command, the

selector and the transmitted K-bytes
return to their previous state.
If you clear the 'Force Switch' command,

the working line returns to be the
currently active line, and the local
request for lockout is cleared.
Clears all externally initiated

switch commands and the WTR
time
clear

Forced switching of traffic from

the protection port to the working
port (unless an equal or higher
priority request has been issued)
force-switch-to-working


the working port to the protection
port, unless an equal or higher
priority switch command is in
effect, or if an SF condition exists
on the protection port.
force-switch-toprotection

Manual switching of traffic from

the protection port back to the
working port, unless an equal or
higher priority request is in effect
manual-switch-toworking


the working port to the protection
port, unless a failure condition
exists on the protection port or
an equal/higher priority switch
command is in effect
manual-switch-toprotection
Since a forced switch has a higher priority

than SF or SD on a working port, this
command is carried out regardless of the
current condition of the working port
Since a manual switch has lower priority

than SF or SD on a working port, this
command is carried out only if the working
port is not in SF or SD condition.
Viewing the Status of an APS Group

This section illustrates the status display of an APS group created in
1+1 Optimized Bi-directional mode.
To view the APS groups status:
At the config>protection>aps(<group name>)# prompt, enter show status.

The APS groups status appears.
APS Protection
5-291
In this example, the APS group name is test.
mp4100>config>protection>aps(test)# show status

Group
--------------------------------------------------------------Mode
: Uni Directional
Current Working
: cl-b/1
Rx K1K2
: 0x0010
Tx K1K2
: 0x0010
Ports
--------------------------------------------------------------Port
Admin
Status
Active
cl-a/1
cl-b/1
Up
Up
Up
Up
No
Yes
Example
To add and configure an APS group:
APS group name test
Working port Port 2 of the module installed in slot cl-a
Protection port Port 1 of the module installed in slot cl-a
Recovery mode revertive
Wait-to-restore period 200 seconds.
mp4100#configure protection aps test bind working sdh-sonet cl-a/2

mp4100>config>protection>aps(test)#bind protection sdh-sonet cl-a/1
mp4100>config>protection>aps(test)#revertive
mp4100>config>protection>aps(test)#wait-to-restore 200
To delete APS group named test:

mp4100#configure protection no aps test
5.41 Path Protection for SDH/SONET Payload

Path (trail) protection is available for user-specified payload units (VC-12 for SDH
links, or VT1.5 for SONET links) mapped to VCG. Up to 252 VC path protection
groups can be defined by the user.
When path protection is enabled, the protected payload unit is assigned
bandwidth on both network links:
5-292
The same payload is transmitted on both links.
Path Protection for SDH/SONET Payload
The receive interfaces of the two links continuously evaluate the received
signals. As long as the working path operates satisfactorily, its signal is
selected for processing. When the working path signal fails, or is degraded,
the receive side rapidly selects the other signal for processing.
Provisioning appropriate alternative paths through the network ensures that in

case of a fault anywhere along the active path, the traffic is automatically
switched to the standby path.
The recovery mode after a protection switching can be selected in accordance
with the application requirements:
Non-revertive mode the CL module will not automatically flip back after the
failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
Revertive mode the CL module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
Configuring VC Path Protection

Adding and Removing a VC Path Protection Group
To add and define a VC path protection group:

Enter vc-path <path name>. The path name may consist of up to 80
alphanumeric characters.
The VC path protection group is defined and enabled and the
config>protection>vc-path(<path name>)# prompt appears.
To remove a VC path protection group:
At the config>protection# prompt, enter no vc-path <path name>.

The VC path protection group is removed.
Binding Ports to a VC path Protection Group
To configure the SDH/SONET path protection:
At the config>protection>vc-path(group name)# prompt, enter all necessary

Task
Command
Assigning a name to the VC

path protection group
name <up to 80 characters>
Activating the VC path

protection group
no shutdown
Comments
Using shutdown switches the VC path

protection group to standby mode
5-293
Task
Command
Comments
Adding a working/protection
port to the VC path protection
group
bind vc-vt {working | protection}

<slot>/<port>/<au4>/<tug_3>/
<tug_2>/<tributary>
The number and type of working and

protection ports must be identical.
Enabling the reverting of the

working and protection ports
revertive
In case reverting is selected, the waitto-restore time is constantly set to 6

sec
Using no before bind removes a port

from VC path protection group
Using no revertive disables the reverting
Viewing the Status of a VC Path Protection Group

This section illustrates the status display of a VC path protection group.
To view the VC path protection group status:
At the config>protection>vc-path(<group name>)# prompt, enter show

status.
The VC path protection group status appears.
In this example, the VC path protection group name is test.
mp4100>config>protection>vc-path(test)# show status

Group
----------------------------------------------------------------------------Mode
: 1+1
Cards
----------------------------------------------------------------------------Working
VC
Admin
Oper
Active
----------------------------------------------------------------------------Protection
Sdh-Sonet cl-a/1/1/1/1/1
Up
Up
-Working
Sdh-Sonet cl-a/2/1/1/1/1
Up
Up
Yes
Example
5-294
To add and configure an VC path protection group:
VC-path protection group name test
Working port: slot=cl-a, sdh port=2, aug=1, tug3=1, vc12=1, tributary=1
Protection port: slot=cl-a, sdh port=1, aug=1, tug3=1, vc12=1, tributary=1
Reverting is enabled.
mp4100#configure protection vc-path(test)#bind working sdh-sonet cl-a/2/1/1/1/1

mp4100>config>protection> vc-path(test)#bind protection sdh-sonet cl-a/1/1/1/1/1
mp4100>config>protection> vc-path(test)#revertive
To delete VC path protection group named test:

mp4100#configure protection no vc-path test
5.42 LAG Protection

Megaplex-4100 features LAG creation on the Gigabit Ethernet ports of its CL
modules. Link aggregation is a method of setting up a high-speed Ethernet link
that transfers more data than any one single port of the device can deliver. It
also provides inherent, automatic redundancy on point-to-point links. In other
words, if one of the ports used in a link fails, network traffic is dynamically
redirected to flow across the remaining good port in the link.
Link Aggregation Groups (LAGs) are created by combining several interfaces into
one logical link to increase bandwidth and improve reliability while saving the cost
of upgrading the hardware.
By increasing the link speed beyond limits of any one single port, LAGs offer
network channels tailored to need, filling the gaps between 10 Mbps, 100 Mbps
and 1 Gbps with intermediate bandwidth values. This allows networks to grow
incrementally as demand on the network increases, without having to replace
everything and buy new hardware.
1 Gbps
1 Gbps
2 x 1 Gbps
100 Mbps
Megaplex-4100
100 Mbps
100 Mbps
Megaplex-4100
100 Mbps
Figure 5-41. Two Gigabit Ethernet Ports Combined into a LAG

The load sharing is automatically readjusted if a failure or recovery from failure
occurs in any of the links that participate in a LAG.
The CL modules support port aggregation on the same or different modules.
For a LAG aggregating two GbE of the same CL module, up to two LAGs can be
configured each time in the system. When LAG members belong to different CL
modules, only one LAG can be defined per system.
LAGs Benefits
Static LAGs provide the following benefits:
Increased bandwidth
LAG Protection
5-295
The capacity of multiple interfaces is combined into one logical link. Besides
increasing bandwidth, link aggregation also provides intermediate data rate
levels between the standard data rates of 10 Mbps, 100 Mbps, 1000 Mbps.
Increased availability
If a link within a LAG fails or is replaced, the traffic is not disrupted and
communication is maintained (even though the available capacity is reduced).
Load sharing
Traffic is distributed across multiple links, minimizing the probability that a
single link could be overwhelmed.
Use of existing hardware

Software replaces the need to upgrade the hardware to higher bandwidth
capacity.
Link aggregation always provides revertive recovery, because that as soon as the
down port returns to normal, the full bandwidth is again available.
Configuring the LAG

LAG configuration includes the following steps:
1. Assigning a number to a LAG.
Binding ports to the LAG
Assigning a name to the LAG
Storing the LAG.
To add a LAG:
Type lag and enter a LAG number (1 or 2).
The config>port>lag(number)# prompt is displayed.
Note
LAGs must be added in consecutive order. This means LAG 2 must be added after
LAG 1.
To configure the LAG:
At the config>port>lag(number)# prompt, enter all necessary commands

Task
Command
Comments
Adding a GBE port to the

LAG
bind ethernet <slot/port>
Using no before bind removes a link from LAG
Assigning a name to the

LAG
name <Alphanumeric string>
Maximum name length is 64 characters
5-296
LAG Protection
Task
Command
Comments
Selecting the type of

ports protected by LAG
admin-key giga-ethernet
The only possible option for the current

version is giga-ethernet: GbE ports
Assigning method of
distributing traffic within
LAG
distribution-method dest-mac
<slot/port>
The only possible option is dest-mac: packets

are distrubuted according to their destination
MAC addresses
Disabling the LAG
shutdown
Using no shutdown enables the LAG
For example:
To create a LAG with packets distrubuted according to their destination MAC

addresses:
LAG number 1
LAG members GbE Port 1 and GbE port 2of a CL.2 module installed in slot
CL-A.
configure slot cl-a card-type cl cl2-622gbe

config port lag 1 bind ethernet cl-a/1
config port lag 1 bind ethernet cl-a/2
config port lag 1 admin-key giga-ethernet
config port lag 1 distribution-method dest-mac
config port lag 1 no shutdown
To create a flow between this LAG and a fast Ethernet port of an ASMi-54C/N
module installed in I/O slot 1:
config flows classifier-profile 1000 match-all match vlan 1000
config
config
config
config
flows
flows
flows
flows
flow
flow
flow
flow
5
5
5
5
classifier 1000
ingress-port ethernet 1/1
egress-port lag 1
no shutdown
config
config
config
config
commit
flows
flows
flows
flows
flow
flow
flow
flow
6
6
6
6
classifier 1000
ingress-port lag 1
egress-port ethernet 1/1
no shutdown
To delete a LAG:
mp4100#configure port no lag 1
Displaying the LAG Status
To display the status of a specific LAG:
LAG Protection
5-297
mp4100>config>port>lag(1)$ show status

Name
: lag 01
Operation Status
: Up
Displaying the LAG Statistics
To display LAG statistics:

mp4100>config>port>lag(1)# show statistics
Running
--------------------------------------------------------------Counter
Rx
Tx
Total Frames
21241092
7431095
Total Octets
4948371714
0
Unicast
12010124
0
Multicast
0
0
Broadcast
9230656
7431095
Paused Frames
FCS Errors
0
0
0
--
Table 5-60. LAG Statistics Parameters

Parameter
Description
Total Frames
Total Octets
Unicast
Total number of unicast frames received/transmitted
Multicast
Total number of multicast frames received/transmitted
Broadcast
Total number of broadcast frames received/transmitted
Paused Frames
Total number of pause frames (used for flow control) received/transmitted through
the corresponding Ethernet port
FCS Errors
The number of frames received on this interface that are an integral number of octets
in length but do not pass the FCS check
5.43 Ethernet Group Protection

Megaplex-4100 supports 1+1 protection (redundancy) for Ethernet groups,
protecting Ethernet and packet traffic against transmission failures on the
SDH/SONET links. Up to 16 Ethernet protection groups can be configured per one
CL.2 module.
Standards
Ethernet group protection is RAD proprietary technology.
5-298
Ethernet Group Protection
Any pair of logical MACs can be configured as an Ethernet protection group, even
if the entities bound to them have different capacity, different encapsulation
methods, and/or different parameters. Only the wait-to-restore delay must be
the same.
To use Ethernet group protection, both the primary (working) logical MAC and the
secondary (protection) logical MAC must be assigned bandwidth (mapped) on the
particular links. In other words, the lower-hierarchy entities on these desired links
must be bound to this logical MAC. Provisioning appropriate trails through the
network ensures that in case of a fault anywhere along the primary group path,
its traffic will be automatically switched to the standby group and will follow a
different path through the SDH/SONET network, thereby ensuring that the
payload can still be transported end-to-end.
Depending on the desired protection level, the protection partners can be
mapped to the same link, to different links on the same CL module, or to a link
on the other (adjacent) CL module.
The Ethernet group protection mode is always 1+1 and operates as follows:
Note
During normal operation, the payload is directed to the primary logical MAC,
and transmitted only over the bandwidth assigned to this group.
Only the primary (working) logical MAC can be included in a flow. The protection
logical MAC will not appear in the list of available bridge ports.
If an alarm condition is detected on the entities bound to the working logical

MAC, the payload is directed to the protection logical MAC, and transmitted
over its bandwidth. The alarm criteria taken into consideration for protection
switching include physical port failures and VCG failures. When using LCAS,
this also includes a decrease in available bandwidth below the specified
minimum.
The recovery mode after a redundancy switching is always revertive which

means that the traffic will be automatically redirected back to the original group
when it returns to normal operation.
To prevent switching under marginal conditions, the user can specify a wait-torestore time, which is the minimum interval before flipping back to the original
port. However, if a more severe alarm appears, immediate flipping will take place,
even if the wait-to-restore time has not yet expired.
Figure 5-42 illustates various entities that can be protected via Ethernet group
redundancy. Any SDH entity in the diagram can be protected by any other SDH
entity via their logical MACs. The same holds for SONET entities. The only
restriction is that each VCG is bound to the CL on which it has been defined.
5-299
Flow
Egress/Ingress Port
Logical MAC
32
Logical MAC
1
Ethernet Group
OR
Bind 1:1
GFP 1..32
HDLC 1..32
OR
Bind 1:1
Bind 1:1
VCG 1..32
Bind 1:n
VC4-4C/STS-12C
VCAT No
VC4/STS-3C
VC3/STS-1
VC12/VT1.5
Figure 5-42. Ethernet Group Protection
Configuring Ethernet Protection Group

Adding and Removing an Ethernet Protection Group
To add and define an Ethernet protection group:

Enter ethernet-group <group number 1..32>.
The Ethernet protection group is defined and enabled and the
config>protection>ethernet-group( <group number>)# prompt appears.
To remove an Ethernet protection group:
At the config>protection prompt, enter no ethernet-group <group number>.

The Ethernet protection group is removed.
5-300
Binding Ports to an Ethernet Protection Group
To configure the Ethernet group protection:
At the config>protection>Ethernet-group(group number)# prompt, enter all

necessary commands according to the tasks listed below:
Task
Command
Comments
Activating the Ethernet protection

group
no shutdown
Using shutdown switches the

Ethernet protection group
to standby mode
Adding a working/protection port

to the Ethernet protection group
bind logical-mac {working |

protection} <slot>/<port 1..32>
Using no bind logical-mac

<slot>/<port> removes a port
from Ethernet protection group
Specifying a wait-to-restore
timeout in seconds
wait-to-restore <time in seconds>
1..300..720
Example
To add and configure an Ethernet protection group 2:
M8E1 modules installed in slot 5
Ethernet protection group number 2
Configure SDH ports cl-a/2 and cl-b/2
Configure vcg cl-a/2 and bind vc-vt cl-a/2/1/1/1/1 to it
Configure gfp cl-a/2 and bind vcg cl-a/2 to it (GFP encapsulation of this VCG)
Configuring logical-mac cl-a/2 and bind gfp cl-a/2 to it
Same on cl-b/2
Configure flows (13) and (14) between logical-mac cl-a/2 and Ethernet port
5/2
Set ethernet group 2 with logical-mac cl-b/2 as protection port for logicalmac cl-a/2. Now flows (13 and (14) are protected
Wait-to-restore time = 2 sec
5-301
mp4100# config slot cl-a card-type cl cl2-622gbe

mp4100# config slot cl-b card-type cl cl2-622gbe
mp4100# config slot 5 card e1-t1 m8e1
mp4100# config port eth 5/2 no shutdown
mp4100#
mp4100# exit all
mp4100# configure
mp4100>config# port
mp4100>config>port# sdh-sonet cl-a/2
mp4100>config>port>sdh-sonet(cl-a/2)# no shutdown
mp4100>config>port>sdh-sonet(cl-a/2)# speed 622mbps
mp4100>config>port>sdh-sonet(cl-a/2)# exit
mp4100>config>port#
mp4100>config>port# sdh-sonet cl-b/2
mp4100>config>port>sdh-sonet(cl-b/2)# no shutdown
mp4100>config>port>sdh-sonet(cl-b/2)# speed 622mbps
mp4100>config>port>sdh-sonet(cl-b/2)# exit
mp4100>config>port#
mp4100>config>port# vcg cl-a/2
mp4100>config>port>vcg(cl-a/2)$ bind vc-vt cl-a/2/1/1/1/1
mp4100>config>port>vcg(cl-a/2)$ no shutdown
mp4100>config>port>vcg(cl-a/2)$ exit
mp4100>config>port#
mp4100>config>port# gfp cl-a/2
mp4100>config>port>gfp(cl-a/2)$ bind vcg cl-a/2
mp4100>config>port>gfp(cl-a/2)$ no shutdown
mp4100>config>port>gfp(cl-a/2)$ exit
mp4100>config>port#
mp4100>config>port# logical-mac cl-a/2
mp4100>config>port>log-mac(cl-a/2)$ bind gfp cl-a/2
mp4100>config>port>log-mac(cl-a/2)$ no shutdown
mp4100>config>port>log-mac(cl-a/2)$
mp4100>config>port>log-mac(cl-a/2)$ exit all
mp4100# configure
mp4100>config# port
mp4100>config>port# vcg cl-b/2
mp4100>config>port>vcg(cl-b/2)$ bind vc-vt cl-b/2/1/1/1/1
mp4100>config>port>vcg(cl-b/2)$ no shutdown
mp4100>config>port>vcg(cl-b/2)$ exit
mp4100>config>port# gfp cl-b/2
mp4100>config>port>gfp(cl-b/2)$ bind vcg cl-b/2
mp4100>config>port>gfp(cl-b/2)$ no shutdown
mp4100>config>port>gfp(cl-b/2)$ exit
mp4100>config>port# logical-mac cl-b/2
mp4100>config>port>log-mac(cl-b/2)$ bind gfp cl-b/2
mp4100>config>port>log-mac(cl-b/2)$ no shutdown
mp4100>config>port>log-mac(cl-b/2)$
mp4100>config>port>log-mac(cl-b/2)$
mp4100>config>port>log-mac(cl-b/2)$ exit all
mp4100# configure flows classifier-profile vlan600 match-all match vlan 600
mp4100#
mp4100# config
mp4100>config# flows
mp4100>config>flows# flow 13
mp4100>config>flows>flow(13)$ ingress-port ethernet 5/2
5-302
mp4100>config>flows>flow(13)$ egress-port logical-mac cl-a/2

mp4100>config>flows>flow(13)$ classifier vlan600
mp4100>config>flows>flow(13)$ exit
mp4100>config>flows# flow 14
mp4100>config>flows>flow(14)$ ingress-port logical-mac cl-a/2
mp4100>config>flows>flow(14)$ egress-port ethernet 5/2
mp4100>config>flows>flow(14)$ classifier vlan600
mp4100>config>flows>flow(14)$ exit all
mp4100#
mp4100# ################
mp4100# # eth-group 2 #
mp4100# ################
mp4100#
mp4100# config prot eth 2
mp4100>config>protection>eth-group(2)# bind logical-mac working cl-a/2
mp4100>config>protection>eth-group(2)# bind logical-mac protection cl-b/2
mp4100>config>protection>eth-group(2)# wait-to-restore 2
mp4100>config>protection>eth-group(2)# commit
To delete Ethernet protection group 2:

mp4100#configure protection no ethernet-group 2
Viewing the Status of an Ethernet Protection Group

This section illustrates the status display of an Ethernet protection group.
To view the Ethernet protection group status:
At the config>protection>ethernet-group (<group number>)# prompt, enter

show status.
The Ethernet protection group status appears. In this example, the
Ethernet protection group number is 1.
mp4100>config>protection# ethernet-group 1
mp4100>config>protection>eth-group(1)# show status
Ports
--------------------------------------------------------------Port
Admin
Oper
Active
Working
Logical MAC cl-a/1
Up
Up
-Protection Logical MAC cl-a/2
Up
Down
Yes
5.44 TDM Group Protection

One of the simplest methods to protect against link and hardware failure is to
use the TDM group protection (redundancy for E1/T1/DS1 ports and optical links).
For E1/T1/DS1 ports, the protection partner ports can be located on either the
TDM Group Protection
5-303
same module, or another module, and can be of any of the following depending
on the interface type:
For external/internal E1 ports: external E1 ports, internal E1 ports of OP

modules, internal E1 ports of CL modules, or internal E1 ports of M8SL and
ASMi-54C/N modules, or DS1 ports of MPW-1 modules.
For external/internal T1 ports: external T1 ports, internal T1 ports of OP

modules, internal T1 ports of CL modules, or DS1 ports of MPW-1 modules
For optical links (mux-eth-tdm ports) of OP modules, the protection partner port
is located on the same module and must be the following:
mux-eth-tdm 2 is always a protection partner for mux-eth-tdm 1 (OP-34C,

OP A section of OP-108C)
mux-eth-tdm 4 is always a protection partner for mux-eth-tdm 3 (OP B

section of OP-108C)
The maximum total number of TDM groups that can be configured for
Megaplex-4100 is 144.
Benefits
The TDM group protection provides two main advantages:
Automatically restores service within a short time without user intervention
In case of technical failure, allows service to continue while technical staff

finds the source of the failure and corrects it.
Moreover, when protection is used, tasks such as planned maintenance, updating

software versions, or installing modules with enhanced capabilities, can also be
performed without disrupting service, provided a few precautions are taken (see
below).
Standards
TDM Group Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4100 is supplied with TDM protection disabled. Other parameter
Parameter
Default Value
oper-mode
dual-cable-tx
wait-to-restore
300 sec
Two different E1/T1 link protection approaches are supported: dual-cable
protection and Y-cable protection. An additional TDM ring protection mode is
described below, in the next section.
5-304
The following tables show the protection features supported by each I/O module.
The hierarchical position of e1/t1 and e1-i/t1-i ports is slot:port for all the
modules, with the exception of the OP-108C and OP-34C Megaplex cards, where
it is slot:port:tributary (in these modules slot:port=mux_eth_tdm).
In addition, Optimux modules support dual-cable protection on their mux-eth-tdm
ports.
Table 5-61. TDM Protection on E1/T1 Ports

E1/T1 Ports (e1/t1)
Protection
M8E1
M16E1
M8T1
M16T1
dual-cable-tx
(1)
(1)
(1)
(1)
y-cable
tdm-ring
type
OP-108C
OP-108C/E1
OP-34C
ASMi-54C/N
(E1 only)
1 Not available for Transparent E1/T1 over SDH/SONET
Table 5-62. TDM Protection on E1-i/T1-i and DS1 Ports

Internal E1/T1 Ports (e1-i/t1-i)
Protection type
Internal DS1 Ports (ds1)
CL.2
M8SL (E1 only)
ASMi-54C/N (E1 only)
MPW-1
dual-cable-tx
(1)
y-cable
tdm-ring
(2)
1 - Not available for Transparent E1/T1 over SDH/SONET

2 Ring section between the SHDSL port at end of the chain and the SHDSL port beginning the chain (on the first
Megaplex-4100)
Dual Cable (Parallel TX) Protection

The dual-cable configuration provides protection against both transmission path
failure and technical failure in the module hardware.
For this type of protection, two ports of the same type (either e1/e1-i/ds1 or
t1/t1-i/ds1 or mux-eth-tdm) are connected to the remote unit via two parallel
links. Defining these two links as a TDM protection group ensures that traffic
carrying capacity is available even if one of the links fails.
Figure 5-43 shows a typical system configuration using dual-cable protection. The
user can select the module ports operating as a TDM group. Both ports process as
usual the transmit and receive signals, but the receive output of the protection
port is disconnected.
During normal operation, the operational state of the protection port is
continuously monitored to ensure that it is operating properly. If the working link
fails, the corresponding port is disconnected, and the protection port takes over.
5-305
The maximum switching time between main and backup ports is 50 msec.
Therefore protection switching will ensure essentially uninterrupted service for all
the types of applications; in particular, it will not cause the disconnection of voice
calls.
Note
50 msec protection switching is not available on modules with SHDSL interfaces,

because of the long times needed to detect failure and put a standby port in
service . This is caused by the SHDSL link setup protocols specified by the
standards.
I/O Module with
E1 or T1 Ports
I/O Module with

E1 or T1 Ports
Working (Active) Link

Protection (Standby) Link
Megaplex-4100
Megaplex-4100
Figure 5-43. E1/T1 Link Protection Using Dual Cables
Y-Cable Protection
For Y-cable protection, two module ports with the same type of physical and
electrical interfaces are connected to the same communication link by a single
Y-cable. For this type of protection to be effective, the two ports must be located
on different modules because it provides protection mainly for technical failures
in the module hardware. A typical configuration is shown in Figure 5-44.
During normal operation, the transmit output of the protection module is
electrically disconnected from the link. Nevertheless, its operational state is
continuously monitored to ensure that it is operating properly. If the working
module fails, it is disconnected from the link and from the internal buses, and the
protection module takes over.
I/O Module with
E1 or T1 Ports
I/O Module with

E1 or T1 Ports
Transmission Link
Megaplex-4100
Megaplex-4100
Figure 5-44. E1/T1 Link Protection Using Y-Cable

When protection is used, tasks as planned maintenance, updating software
versions, or installing modules with enhanced capabilities, can also be performed
without disrupting service, provided a few precautions are taken:
5-306
To minimize disruptions to traffic, do not simply pull module out but first
check that the module does not serve as the working port. If one of the
module ports serves as the working port, first force protection flipping by
means of a RESET command.
After removing a module, wait at least 10 seconds before inserting a module

in the same slot.
Working and Protection Port Parameters

When two ports are configured to TDM group protection, the following
parameters must be same for both ports:
Admin Status
line-type
line-code
inband-management>timeslot
inband-management>protocol
inband-management>routing-protocol.
Protection Mode
The protection mode for TDM group redundancy is always revertive.
Configuring TDM Group Protection

The TDM Group Protection is configured as follows.
To add a TDM protection group:

1. Navigate to configure protection.
Type tdm-group and enter a group number.
The config>protection>tdm-group(group number)# prompt is displayed.
To configure the TDM protection group:
At the config>protection>tdm-group(group number)# prompt, enter all

necessary commands according to the tasks listed below:
Task
Command
Comments
Administratively
enabling TDM group
no shutdown
Using shutdown disables the group
Defining operation
mode of the TDM group
oper-mode {y-cable | dual-cable-tx}
Y-cable protection is available in

M8E1/M8T1 modules only
Adding working and pro

tection e1/e1-i/ds-1
ports to the TDM group
bind e1 {working | protection}

bind e1-i {working | protection}
<slot>/<port>
bind ds1 {working | protection}
<slot>/<port>
Using no bind (e1/e1-i/ds-1) protection

removes the protection port from the
group. There is no need to remove the
working port from the group.
[<tributary>] relates to Megaplex Optimux

cards (OP-34C, OP-108C) as protection
ports (for internal E1 port numbering in
Optimux modules, see relevant section of
Appendix B).
5-307
Task
Command
Comments

tection t1/t1-i/ds-1
bind t1 {working | protection}

<slot>/<port>
bind t1-i {working | protection}
<slot>/<port>
Using no bind (t1/t1-i/ds-1) protection

bind ds1 {working | protection}

<slot>/<port>
tection
mux-eth-tdm
bind mux-eth-tdm {working |

protection} <slot>/<port>
Using no bind mux-eth-tdm protection

Defining the wait-torestore period

(the time to elapse
before traffic
switches back)
wait-to-restore <0720>
The unit of time is seconds. For

mux-eth-tdm ports, the wait-to-restore
time is always 0.
Example 1
To add and configure an E1/T1 protection group:
Protection group number 2
Working link Port 1 of the module installed in slot 6
Protection link Port 2 of the module installed in slot 5
Operation mode dual cable protection
mp4100#configure protection tdm-group 2 bind e1 working 6/1

mp4100#configure protection tdm-group 2
mp4100>config>protection>tdm-group (2)#bind e1 protection 5/2
mp4100>config>protection>tdm-group (2)#wait-to-restore 200
To delete protection group 2:

mp4100#configure protection no tdm-group 2
Example 2
5-308
To add and configure an optical link protection group:
Operation mode dual cable protection (this is the only option so the 3rd
string is optional)
mp4100#configure
mp4100#configure
mp4100#configure
mp4100#configure
port mux-eth-tdm 1/2

protection tdm-group 1 bind working mux-eth-tdm 1/1
protection tdm-group 1 bind protection mux-eth-tdm 1/2
protection tdm-group 1 oper-mode dual-cable-tx
To display the protection status:

mp4100>config>protection>tdm-group(1)# show status
Group
--------------------------------------------------------------Mode
:
Cards
--------------------------------------------------------------Port
Admin
Oper
Active
Working
Mux Eth TDM 1/1
Up
Up
Yes
Protection Mux Eth TDM 1/2
Up
Down
--

mp4100#configure protection no tdm-group 1
Example 3
To add and configure an internal E1 protection group on OP-108C:
Working link Port 1 of Section OP A of the module installed in slot 1
Protection link Port 4 of Section OP B of the module installed in slot 2
Operation mode dual cable protection (this is the only option so the 3rd
string is optional)
mp4100#configure protection tdm-group 3 bind working e1 1/1/1

mp4100#configure protection tdm-group 3 bind protection e1 2/3/4
mp4100#configure protection tdm-group 3 oper-mode dual-cable-tx
To display the protection status:

mp4100>config>protection>tdm-group(3)# show status
Group
--------------------------------------------------------------Mode
:
Cards
--------------------------------------------------------------Port
Admin
Oper
Active
Working
E1 1/1/1
Up
Up
Yes
Protection E1 2/3/4
Up
Down
--
5-309
5.45 TDM Ring Protection

The TDM ring protection (E1/T1 ring redundancy) is a RAD proprietary topology
suitable for Megaplex-4100 equipment. It provides higher availability for critical
applications at the E1 and T1 level, with fast protection switching time.
The maximum total number of TDM rings that can be configured for
Megaplex-4100 is 16.
Benefits
E1/T1 ring protection can use the same cabling infrastructure as regular
point-to-point links, and provides several significant advantages:
There is no single point of failure
Rapid switching time in case of failure
Does not require additional hardware. Any daisy chain topology can be
converted to an E1/T1 ring topology by connecting two additional pairs
between the E1, T1 or SHDSL port on the Megaplex-4100 at the end of the
chain to the E1/T1/SHDSL port beginning the chain (on the first Megaplex4100)
Flexible solution (any Megaplex-4100 unit in the ring can connect to

additional rings)
Simple to configure: requires the same timeslot assignment as a chain

topology, except that at each node it is necessary to bypass timeslots that
are not used for local payload between the working and protection E1/T1
ports.
Standards
TDM Ring Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4100 is supplied with TDM ring protection disabled. The default
wait-to-restore time is 300 sec.
Figure 5-45 illustrates TDM Ring Protection topology. The links comprising the
ring can include E1 and T1 physical links, as well as E1 links implemented over
SHDSL. The different types of links can be intermixed along the same ring,
without requiring any media converters or modems.
5-310
TDM Ring Protection
Protection Ring
(SHDSL)
MP- 4100 B
MP- 4100 A
MP- 4100 C
Working Ring
(E1 or T1)
Protection Ring
(E1 or T1)
MP- 4100 D
Figure 5-45. TDM (E1/T1) Ring Topology

TDM (E1/T1) ring protection is based on the use of two transmission paths, each
requiring a single twisted pair: one pair, called the working, is used instead of the
legacy transmit pair, and the other, called the protection, is used instead of the
legacy receive pair. Therefore, E1/T1 ring protection can use the same cabling
infrastructure as regular point-to-point links.
The E1/T1 ring protection topology can be efficiently implemented by any pair of
physical or internal (logical) E1 or T1 ports, as available on M8E1, M8T1, M8SL,
etc. Any pair of ports, even ports located on different modules, can be configured
as a protection group.
Any port participating in the TDM ring can automatically choose an appropriate
timing reference or data flow direction in accordance with internal mesaages
and/or alarms in the system.
Note
When using inband management carried over a dedicated timeslot, you need to
add a Proprietary RIP or RIP2 routing protocol (inband-management <timeslot>
protocol {ppp | fr} routing-protocol {prop-rip | rip2}. It is highly recommended to
use RIP2 protocol rather than Proprietary RIP.
Figure 5-46 shows a typical application that uses the ring protection topology.
TDM Ring Protection
5-311

Working Ring
Protection Ring
TS 13 MNG
TS 1-3 Local (3 TS)
TS 4-12 Bypass
TS 13 MNG
TS 1-12 Local
Working
Working
TX
Port 1
RX
Port 2
TX
RX
Central
RX
Port 2
TX
TS 13
MNG
TS 4-6
Local (3 TS)
TS 1-3, 7-12 Bypass
RX
RX
Port 2
TX
TX
Port 1
RX
RX
Port 2
TX
TS 13
MNG
TS 10-12 Local (3 TS)
TS 1-9
Bypass
Working
Working
Working
TX
Port 1
TS 13
MNG
TS 7-9
Local (3 TS)
TS 1-6, 10-12 Bypass
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
HS-6N
HS-6N
HS-6N
HS-6N
A B C D
User's Equipment
User's Equipment
User's Equipment
User's Equipment
User's Equipment
Figure 5-46. E1/T1 Ring Protection Signal Flow during Normal Operation
In each Megaplex-4100 unit on the ring, two E1 or T1 ports (identified as port 1
and port 2 in Figure 5-46) are defined as a protection group pair. One port of
each unit (in this example, port 2) is configured as working port: under normal
conditions, each Megaplex-4100 transmits data to the next node through the
working port, and receives through the protection port. Timeslots not connected
to local channels are bypassed.
The payload is handled as follows:
Working ring: at each unit, timeslots used at the local unit are dropped from
the receive side of the protection port, and added to the transmit side of the
working port. Timeslots used by the other Megaplex-4100 units are bypassed
directly between these two ports.
Protection ring: all the timeslots received by port 2 are bypassed to the
transmit side of port 1.
If one of the segments in the ring fails (see Figure 5-47), the CL modules of the
two Megaplex-4100 units adjacent to the failure point detect the loss of signal
and change the signal routing within the corresponding units. Therefore, each
unit now receives and transmits only through the synchronized port. Timeslots
previously bypassed between the ports are now transferred between the receive
and transmit sides of the active port by a connection similar to the remote
loopback, thereby preserving transmission path continuity.
5-312
TDM Ring Protection
Working Ring
Protection Ring
TS 13 MNG
TS 1-3 Local
TS 4-12 Bypass
TS 13 MNG
TS 1-12 Local
Working
TS 13
MNG
TS 4-6
Local
TS 1-3, 7-12 Remote Loop
TS 13
MNG
TS 7-9
Local
TS 1-6, 10-12 Remote Loop
Working
Working
Working
RX
TX
Port 1
RX
Port 2
TX
Port 2
TX
RX
Central
TX
Port 1
RX
Port 2
RX
TX
HS-6N
TX
Port 1
RX
RX
Port 2
TX
TS 13
MNG
TS 10-12 Local
TS 1-9 Bypass
Working
TX
Port 1
RX
RX
Port 2
TX
TX
Port 1
RX
HS-6N
HS-6N
HS-6N
HS-6N
User's Equipment
User's Equipment
User's Equipment
User's Equipment
A B C D
User's Equipment
Figure 5-47. E1/T1 Ring Protection Signal Flow after Segment Failure
Note that all the other Megaplex-4100 units do not change their operating
configuration: only the units that are connected to the failed segment take action
in response to the failure.
Notes
To prevent unnecessary switching to the protection path, do not activate
remote loopbacks, or loopbacks on timeslots, on ports connected to the ring.

When it is necessary to perform local bypassing (on the same module) from
another port to one of the ports participating in ring protection, you can do
that only for the working port; for the protection port, you get an error
message.
To save duplication of configuration parameters, all the E1/T1 port parameters
are selectable only for the working port. The parameters of the other
(protection) port are automatically copied from the working port after the
configuration of the working port has been completed and the database has
been updated. However, you can select different interface-type for the working
and protection ports, where this parameter is applicable.
Configuring TDM Ring Protection
To add a TDM protection ring:

1. Navigate to configure>protection#.
Type tdm-ring and enter a ring number.
The config>protection>tdm-ring(ring number)# prompt is displayed.
To configure the TDM ring protection:
At the config>protection>tdm-ring(ring number)# prompt, enter all necessary

Task
Command
Comments
TDM ring
no shutdown
Using shutdown disables the ring
TDM Ring Protection
5-313
Task
Command
Comments
Adding working and

protection e1/e1-i
bind e1 {working | protection}

bind e1-i {working | protection}
<slot>/<port>
Using no bind (e1/e1-i) protection

[<tributary>] relates to Megaplex
Optimux cards (OP-34C, OP-108C) as
protection ports (for internal E1 port
numbering in Optimux modules, see
relevant section of Appendix B).
Adding working and

protection t1/t1-i
bind t1 {working | protection}

<slot>/<port>
bind t1-i {working | protection}
<slot>/<port>
Using no bind (t1/t1-i/ds-1) protection

Defining the wait-to-restore

period (the time to elapse
before traffic switches back)
wait-to-restore <time in seconds>
1..300..720
Example
To add and configure a TDM Ring protection group:
mp4100#configure protection tdm-ring 2 bind e1 working 6/1

mp4100>config>protection> tdm-ring(2)#bind e1 protection 5/2
mp4100>config>protection> tdm-ring(2)#wait-to-restore 200

mp4100#configure protection no tdm-ring 2
5.46 Clock Selection

Megaplex-4100 flexible timing options enable reliable distribution of timing
together with flexible selections of timing sources, including support for an
external station clock interface that enables daisy-chaining the clock signals to
other equipment. Megaplex-4100 also provides traceable timing quality and
supports automatic selection of best-quality timing reference.
Standards
The CSM module complies with the ITU-T G.781 standard.
5-314
Clock Selection
Megaplex-4100 supports one clock domain with up to 10 clock sources. The
timing subsystem automatically selects the best timing source to use for
synchronization.
The user can define the following clock sources:
Recovered from the STM-1/STM-4/OC-3/OC-12 interface, including automatic

selection based on SSM (Synchronization Status Messaging)
Internal crystal free-running oscillator-based clock
Clock derived from the receive clock of a specified module user port
Adaptive clock recovered from a pseudowire circuit (ACR)
External station clock.
Multiple clock sources can be set and assigned a corresponding clock source
quality and priority.
If SDH/SONET clock sources are configured as SSM-based, their quality can be
determined by monitoring the synchronization status messages.
Clock Synchronization
The synchronization network type identifies the type of synchronization network
connections and the synchronization level. Each synchronization network
connection is provided by one or more synchronization link connections, each link
connection supported by an SDH multiplex section trail.
The synchronization network types are:
1. Option I (Europe, Table 5-63)
Option II (USA, Table 5-64).
You can define the timing quality level of the source, or work without quality
level. The supported quality levels are according to the synchronization network
type, as shown in the following tables. The quality levels are shown in order of
highest quality level to lowest quality level.
Table 5-63. Option I Quality Levels

Quality
Level
Description
Rank
PRC
Timing source is Primary Reference Clock as defined in Recommendation

G.811
Highest
SSU-A
Timing source is Type I or V Synchronization Supply Unit (SSU) clock as

defined in Recommendation G.812
SSU-B
Timing source is Type VI Synchronization Supply Unit (SSU)clock as defined

in Recommendation G.812
SEC
Timing source is Synchronous Equipment Clock as defined in

Recommendation G.813 or G.8262, Option I
DNU
Do Not Use This signal should not be used for synchronization
Clock Selection
Lowest
5-315
Table 5-64. Option II Quality Levels

Quality
Level
Description
Rank
PRS
Timing source is Primary Reference Source clock as defined in

Recommendation G.811
Highest
STU
Synchronization Traceability Unknown Timing signal does not carry a

quality level indication of the source
ST2
Timing source is Stratum 2 clock as defined in Recommendation G.812,

Type II
TNC
Timing source is Transit Node Clock as defined in Recommendation G.812,

Type V
ST3E
Timing source is Stratum 3E clock as defined in Recommendation G.812,

Type III
ST3
Timing source is Stratum 3 clock as defined in Recommendation G.812,

Type IV
SMC
Timing source is SONET/Ethernet self-timed clock as defined in

Recommendation G.813 or G.8262, Option II
ST4
Timing source is Stratum 4 free-running clock (applicable only to 1.5

Mbit/s signals)
PROV
Provisionable by the network operator
DUS
Don't Use for Sync This signal should not be used for synchronization
Lowest
System Timing Modes

The Megaplex-4100 timing subsystem can use the following types of reference
sources:
Internal Megaplex-4100 oscillator
Clock signal derived from the E1/T1/SHDSL receive clock (Rx timing mode),
SDH/SONET port, or pseudowire
Station clock, a special case of Rx timing, which uses an external clock signal
supplied to the CL module CLOCK connector.
Table 5-65 lists the reference clock sources that can be configured, together with
the types of Megaplex-4100 modules that can provide a timing reference signal.
For each module, the table also lists the type of ports and, when applicable, the
operating mode that must be selected for a port to provide a timing reference
signal.
Table 5-65. Clock Reference Sources

Source Type
Module Type
Selectable Ports
Specific Operating Mode
Internal
Not applicable
Not applicable
Not applicable
Station (external)
CL
Station clock
Not applicable
5-316
Clock Selection

Source Type
RX Clock from
Local User Port
Module Type
Selectable Ports
Specific Operating Mode
M8E1, M16E1,
M8T1, M16T1
External E1 or T1 ports
Not applicable
M8SL
External SHDSL ports
STU-R mode
MPW-1
Pseudowire recovered
clock
Not for HDLC pseudowires
OP-108C/OP-34C
Internal E1-i
Not applicable
HS-6N, HS-12N
External ports
DTE timing
HS-U-6, HS-U-12
External ports
NT mode
HS-S
External ports
TE mode
HS-703
External ports
Not applicable
LS-6N, LS-12
External ports
DTE timing mode, provided

the channel data rate is a
multiple of 8 kbps
Link port
Not applicable
Line (STM-1/OC-3/STM-4/OC- CL.2

12) Signal from SDH/SONET
Subsystem
A timing source is defined by specifying the slot and the port to be used. The
source slot can be any I/O slot with a module having ports capable of recovering
a clock signal, or a CL slot.
Internal Timing Mode

In most Megaplex-4100 applications, an external clock source is used. The
internal oscillator is used as a last recourse timing source: it is automatically
selected when no source is capable of providing a good timing reference.
Rx Timing Mode
In the Rx timing mode, the reference signal is derived from the receive (RX) clock
of a specified user port, or a clock recovered from a user-specified pseudowire:
Megaplex-4100 always permits locking the system (nodal) timing to a local

user (that is, a user directly connected to a port of an I/O module installed in
the chassis) from which a stable clock signal can be obtained. See Table 5-65.
For Megaplex-4100 equipped with MPW-1 modules, it is also possible to

configure certain pseudowires to provide recovered clock signals to serve as
timing references. Any type of pseudowires, except HDLC, can provide
recovered clock signals.
The algorithm that selects the Megaplex-4100 timing reference source is based
on the user-defined priorities, and works to automatically select the operational
port as the nodal timing reference: first according to the highest quality, and
then according to the highest priority. If the quality level is not selected,
Megaplex-4100 selects the operational port with the highest available priority
from the source list.
Clock Selection
5-317
If no operational port can be found in the source list, the Megaplex-4100

switches to the holdover mode. In this mode, the timing subsystem selects the
frequency used 26 msec before the fault condition that caused the switching to
the next clock source mode (this is assumed to be a safe selection, at which the
subsystem operated normally at the correct frequency). This frequency is
maintained until one of the user-specified sources can again be selected as a
reference. If time limit expires without any of the user-specified clock sources
returning to normal, Megaplex-4100 switches to the internal oscillator.
Station Timing
When the station timing mode is used as one of the 10 clock sources, the
Megaplex-4100 system (nodal) timing is synchronized to an external clock signal
delivered to the dedicated station clock interface located on each CL module. This
signal is usually provided by a highly-accurate clock source, configured with the
highest priority, which is often available in communication facilities (for example,
a signal provided by a GPS-based timing source, an independent primary clock
source, clock signals provided by an SDH/SONET ADM, or other suitable clock
source). The clock signal frequency is user-selectable: 2.048 MHz, 2048 Mbps, or
1.544 Mbps.
The station clock quality can be set by the user.
Each CL module can be connected to a separate station clock source, so that
both station ports can serve as a clock source.
The station clock has software-selectable interfaces:
ITU-T Rec. G.703 interface. The clock interface (balanced/unbalanced) and

sensitivity (long or short range) are also user-selectable
RS-422 interface for squarewave signals, which is the recommended interface

when timing quality is critical. Note that this interface is suitable for short
cable runs, interconnecting equipment units located in close proximity.
The station clock interface also provides an output clock signal, for chaining
applications. The source of the output clock is selectable:
The external clock signal applied to the station clock interface.
The external clock signal, after regeneration and filtering by a jitter

attenuator
When using the internal clock as the system timing reference, the transmitted SSM
message is SEC (SDH) or SMC (SONET).
Factory Defaults
The table below lists the parameter defaults for the Clock Domain, Clock Source
and Station Clock configuration.
Parameter
Default Value
domain
sync-network-type
5-318
Clock Selection
Parameter
Default Value
quality
sdh-sonet: ssm-based
other ports, Type 1: dnu
other ports, Type 2: dus
mode
auto
clock-source
priority
10
wait-to-restore
300 (s)
hold-off
300 (ms)
station
tx-clock-source
system
interface-type
e1, balanced
rx-sensitivity
short-haul
line-code
hdb3
recovered
network-type
type-b
Configuring the Clock Domain
To configure the clock domain:

1. Navigate to configure system clock domain 1.
The config>system>clock>domain(1)# prompt is displayed.
Task
Command
Comments
Setting
synchronization
network type
sync-network-type {1 | 2}
Type 1 Europe
Setting quality of
clock
quality
Type 2 USA
When you change the synchronization network
type, you must redefine the clock sources.
Typing no quality removes the quality parameter. If
no quality is defined for the domain you cannot
configure quality level for the sources.
The quality value is PRC for Type 1 and PRS for
Type 2
Setting clock mode
mode {auto | free-run}
auto Clock selection mechanism functions

normally, e.g. the best available clock source is
selected for synchronization
free-run Internal oscillator is used for
synchronization
Clock Selection
5-319
Task
Command
Comments
Forcing selection of a
particular clock
source when the
sources have
different quality
levels
force <source-id>
The range of source-id is 1 to 10.
Manually selecting a
particular clock
source
manual <source-id>
The selection is performed in the following

conditions:
Canceling previously
issued force or
manual command
clear
Adding clock source
source <src-id> rx-port {e1| t1

| sdh-sonet | shdsl | station |
recovered} <slot><port>
No quality is defined for the clock domain
The sources have the same qualities
The sources have different priorities.
Refer to Configuring the Clock Sources.
source <src-id> station

<slot>/1
Configuring clock
source
source <src-id>
Typing no source <src-id> deletes the source

Refer to Configuring the Clock Sources.
Displaying the Clock Domain Status
To view the clock domain status:
At the system>clock> domain(1)#, enter show status.

The clock source status is displayed.
The possible clock states are explained in the following table.

Parameter
Displayed
Description
Free Run
Indicates that the nodal timing system is locked to the internal oscillator
Note: When using the internal clock as the system timing reference, the transmitted
SSM message is SEC (SDH) or SMC (SONET).
Holdover
Indicates whether the nodal timing system is in the holdover state (yes) or not (no).
The nodal timing system enters the holdover state when all the configured sources
fail. In the holdover mode, the clock maintains the incoming reference frequency at
the last value acquired before the failure. This situation persists until at least one of
the configured sources returns to normal operation, and thus is selected again as
reference.
Note 1: This field is not relevant for DS0 only CL option

Note 2: The transmitted quality level is SEC (SDH) or SMC (SONET).
5-320
Clock Selection
Parameter
Displayed
Description
Locked
Indicates that the nodal timeing is locked on one of the clock references.
Example 1: Megaplex-4100 clock is locked to Source 2, with PRC quality.

mp4100>config>system>clock>domain(1)# show status
System Clock Source
: 2
State : Locked
Quality
: PRC
Example 2: The nodal timing system entered the holdover state after all the
configured sources failed.
System Clock Source
: 0
State : Holdover
Quality
: SEC
Example 3: Clock Domain Mode is configured to free-run and no clock selection

is performed.
System Clock Source
: 0
State : Freerun
Quality
: SEC
Configuring the Clock Sources

You can define up to 10 clock sources. The sources can be E1, T1, SHDSL,
SDH/SONET ports, PW, or the station clock.
To add a clock source:

Type one of the following, according to the source port type:
source <src-id>
source <src-id>
source <src-id>
source <src-id>
source <src-id>
source <src-id>
source <src-id>
no source
Note
rx-port e1 <slot>/<port>
rx-port t1 <slot>/<port>
rx-port sdh-sonet <slot>/<port>
rx-port shdsl <slot>/<port>
rx-port serial <slot>/<port>
station <slot>/1
recovered <recovered ID>
Recovered ID range is 1 to 99.

The clock source is created and the
config>system>clock>domain(1)>source(<110>)# prompt is displayed.
Enter all necessary commands according to the tasks listed below the following
procedure.
To configure a clock source for which the port has been defined:
Type source <110> to select the source to configure.
Clock Selection
5-321
The config>system>clock>domain(1)>source(<110>)# prompt is

displayed.
Task
Command
Comments
Setting priority
priority <110>
Priority 1 is the highest.
Setting quality level
For Type 1: quality-level

{prc | ssu-a | ssu-b | sec |
dnu | ssm-based}
If no quality is defined for the domain, this

command is not available
For Type 2: quality-level {

prs | stu | st2 | tnc | st3e |
st3 | smc | st4 | dus |
ssm-based | prov }
The quality level ssm-based indicates that the

quality level is based on SSM messages
Using no quality cancels the quality hierarchy
and the clock becomes priority-based only
Defining the time that a

previously failed
synchronization source must
be fault-free in order to be
considered available
wait-to-restore <0720>
The time is defined in seconds.
Defining the time that

signal failure must be active
before it is transmitted
hold-off <3001800>
The time is defined in milliseconds.
Canceling the
wait-to-restore timer of a
clock source
clear-wait-to-restore
This option is useful if a timing source fault is

cleared and you want to souce to be
immediately available.
Displaying the Clock Source Status
To view the clock source status:
At the system>clock> domain(1)>source(<110>)#, enter show status.

The clock source status is displayed.
mp4100>config>system>clock>domain(1)>source(1)# show status

Status
: Physical Fail
Tx Quality : DNU
Rx Quality : PRC
Configuring the Station Clock

The station clock is an E1/2MHz or T1/1.5MHz port that can be used for
synchronization. You can set the station clock timing to be based on the system
clock or recovered from the received signal of the station clock (with or without
jitter attenuator).
To configure the station clock:

1. Navigate to configure system clock station <slot>/1 (<slot> is cl-a or cl-b).
The config>system>clock>station(<slot>/1)# prompt is displayed.
5-322
Clock Selection

Task
Command
Comments
Selecting the source of the

clock output signal provided
in the station clock
connector, for connection to
other equipment
tx-clock-source {system | stationrclk-plus-ja}
system The output (transmit) clock is

derived from the Megaplex-4100 nodal
timing
Selecting the rate and type

of signal accepted and
transmitted via the station
clock port
interface-type {e1 | 2mhz | t1}
station rclk after ja The external clock

signal applied to the station clock
receive input is regenerated and filtered
by a jitter attenuator, before being
returned through the transmit output
e1 2.048 Mbps signal per ITU-T Rec.
G.703 Para. 9
2mhz 2.048 MHz signal per ITU-T Rec.
G.703 Para. 13
t1 1.544 Mbps signal per ITU-T Rec.
G.703 Para. 5.
Selecting the impedance of

signal accepted and
transmitted via the station
clock port
impedance {balanced | unbalanced}
For e1 and 2mhz options only. If you

specify e1 or 2mhz and do not specify
balanced or unbalanced, by default the
interface is set as balanced
Setting line code
line-code {b8zs | ami | hdb3}
hdb3 High Density Bipolar coding of

order 3, used for e1 and 2mhz options
ami Alternate Mark Inversion coding,
used for t1 and 1.5mhz options
b8zs Binary-8 zero suppression
coding, used for t1 and 1.5mhz options
Specifying E1 framing mode
line-type { g732n | g732n-crc }
Specifying T1 framing mode
line-type { sf | esf}
Setting receiver sensitivity

to adjust the signal
capability to reach
destinations close by or
farther away
rx-sensitivity {short-haul |
long-haul}
Enabling SSM transmission
tx-ssm
Specifying bits in TS0 for

transfering clock quality via
SSM (E1 only)
ssm-channel { sa4 | sa5 | sa6 | sa7

| sa8 }
station clock
no shutdown
short-haul maximum allowable

attenuation of 10 dB, relative to the
nominal transmit level
long-haul maximum allowable
attenuation of 34 dB, relative to the
nominal transmit level
Using no tx-ssm disables SSM
transmission
Using shutdown disables the station

clock
Clock Selection
5-323
Displaying the Station Clock Status
To view the station clock status:
At the system>clock>recovered (<slot><1>)# prompt, enter show status.

The station clock status is displayed.
mp4100>config>system>clock>station(cl-a/1)# show status

Name
: CL-A station 01
Administrative Status : Down
Operational Status
: Down
Configuring the Recovered Clock

MPW-1 pseudowires of all types, except HDLCoPSN, can be selected as timing
sources for the Megaplex-4100 nodal timing subsystem.
To configure the recovered clock:

1. Navigate to configure system clock recovered <ID 1..99>.
The config>system>clock>recovered (<ID>)# prompt is displayed.
Task
Command
Comments
Associating the PW number

to recovered clock
pw <PW number>
The possible PW number range is 1 to 640.
Specifies the type of packet

switched network used to
transport the pseudowire
recovered clock
network-type {type-a | type-b}
no shutdown
type-a Switch-based network, for example,

an MPLS/ETH network
type-b Router-based network, for example,
an UDP/IP network
Using shutdown disables the recovered clock
Displaying the Recovered Clock Status

You can display the recovered clock status and the current status of the
pseudowire adaptive clock recovery mechanism.
To view the recovered clock status and pseudowire adaptive clock recovery
mechanism state:
At the system>clock>recovered (<PW number)# prompt, enter show status.

The recovered clock status is displayed.
mp4100>config>system>clock>recovered(1)# show status

Clock State : Frequency Acquisition
The possible clock states are explained in the following table.
5-324
Clock Selection
Parameter
Displayed
Description
Idle
Indicates that the clock recovery mechanism is not locked to any clock.
Holdover
Indicates whether the nodal timing subsystem is in the holdover state (yes) or not
(no).
The nodal timing subsystem enters the holdover state when all the configured
sources fail. In the holdover mode, the maintains the internal reference frequency at
the last value acquired before the failure. This situation persists until at least one of
the configured reference source returns to normal, and thus is selected again as
reference
Frequency
Acquisition
Indicates that the clock recovery mechanism is learning the frequency of the
selected reference.
Rapid Phase Lock
Indicates that the clock recovery mechanism is in the training process
Fine Phase Lock
Indicates that the clock recovery mechanism successfully completed the training
process, and is now locked. At this stage, the clock recovery mechanism provides a
stable clock of good quality.
Not Applicable
The adaptive clock recovery status is not relevant.
You can also display the number of the PW the recovered clock is locked to, and
the network type by means of the following command.
To display the network type and the PW number:

mp4100>config>system>clock>recovered(1)# info detail
pw 1
network-type type-b
no shutdown
5.47 Date and Time

You can set the date and time for the Megaplex-4100 internal real-time clock.
Note
The internal real-time clock is used to time-stamp various messages, alarms, etc.
The previously attached time stamps are not changed when the time-of-day is
changed as a result of updates.
Setting the Date and Time

You can adjust the time and the date, or link the system clock to a network time
server to receive the network time.
To specify the system date and time:

1. At the config>system# prompt, enter date-and-time.
The config>system>date-time# prompt appears.
Date and Time
5-325
Specify the date and time and associated parameters as illustrated and explained
below.
Task
Command
Comments
Specifying the system date
date <selected format>
Default: yyyy-mm-dd
Selecting the date format
date-format {yyyy-mm-dd | dd-mmyyyy | mm-dd-yyyy | yyyy-dd-mm}
yyyy-mm-dd ISO format

dd-mm-yyyy European
format
mm-dd-yyyy US format
yyyy-dd-mm Japanese format
dd stands for day, mm for
month and yyyy for year
Specifying the system time
time <hh:mm[:ss]>
Seconds are optional.

It is recommended to set the
time about one minute beyond
the desired time, and then
save at the correct instant.
Example
To define dd-mm-yyyy as a date format:

mp4100>config>system>date-and-time# date-format dd-mm-yyyy
To define January 2, 2011 as the Megaplex-4100 date:

mp4100>config>system>date-and-time# date 02-01-2011
To define 18:23 as the Megaplex-4100 time:

mp4100>config>system>date-and-time# time 18:23
Displaying the Date and Time
To view the date and time settings:
At the config>system# prompt, enter show date-and-time.

The date, time and the time zone are displayed.
mp4100>config>system# show date-and-time

2011-03-04
19:52:23
5.48 User Access Levels

Megaplex-4100 allows you to define new users, their management and access
rights. Only superusers (su) can create new users. Regular users are limited to
changing their current passwords, even if they were given full management and
access rights.
5-326
User Access Levels
You can specify a user password as a text string. You can add a second user with
the same password using the hash function as explained below.
Defining Users and Passwords

Follow the instructions below to add users and assign passwords.
Notes
User passwords are stored in a database so that the system can perform
password verification when a user attempts to log in. To preserve

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

1. Make sure that you are logged on as superuser (su).
At the user prompt config>mngmnt>, enter
user <name> [level <debug | su | oper | tech | user>] [password <password of
up to 40 characters>].
The user name, the associated user level and the password are defined.
To add another user with the same password using the hash function:
1. At the user prompt config>mngmnt> prompt, enter info.
The first users passwords hash value appears as illustrated below.
mp4100>config>mngmnt# info
user "staff1" level user password
"3fda26f8cff4123ddcad0c1bc89ed1e79977acef"
hash
Define another user with the hashed password obtained from the info output.
The second user is added and can log on with the text password defined
in step 1.
To delete an existing user:
At the config>mngmnt# prompt, enter no user <name>.

The specified user is deleted.
Example
To add a super user with a text password and access to all possible ways of
management:
Specify the user name staff for the user level su.
Assign the password 1234.
User Access Levels
5-327
mp4100>config>mngmnt# user staff level su password 1234

# Password is encrypted successfully
Megaplex-4100>config>mngmnt#
To add two new users with identical passwords using the hash function:
Assign the user name staff1.
Assign the password 4222.
Assign the user name staff2.
Assign the same password 4222 to staff2 by linking the hash output to
staff2.
mp4100>config>mngmnt# user staff1 level user password 4222

# Password is encrypted successfully
Megaplex-4100>config>mngmnt# info
"3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
user "su"
mp4100>config>mngmnt# user staff2 level user password

3fda26f8cff4123ddcad0c1bc89ed1e79977acef hash
mp4100>config>mngmnt# info
user "su"
mp4100>config>mngmnt# logout
CLI session is closed
user>staff2
password>4222
mp4100#
Viewing Connected Users

This section explains how to view users currently logged on to the unit.
To view all connected users:
At the config>mngmnt# prompt, enter show users.

A list of all connected users is displayed, showing their access level, the
type of connection, and the IP address from which they are connected.
5-328
User Access Levels
mp4100# configure management

mp4100>config>mngmnt# show users
User
Access Level
Source
IP-address
----------------------------------------------------------------------------su
SU
Terminal
172.4.3.3
Megaplex-4100>config>mngmnt#
5.49 Administration
This section covers administrative tasks such as entering contact info, file
management, etc. In addition, this section instructs you on resetting the unit.
For description of software upgrade procedures, refer to Chapter 6.
Specifying Administrative Information

You can assign a name to Megaplex-4100, specify information on its location and
whom to contact if necessary. In addition, you can modify the timeout and
number of retries for file transfers to the unit.
To enter information and set administrative parameters:
At the config>system# prompt, specify the units details as illustrated and

explained in the table below.
Task
Command
Assigning a name to the unit
name <free text>
Removing the name from the unit
no name
Specifying a contact person in

charge for this unit
contact <free text>
Removing the contact person
no contact
Specifying the location of this unit
location <free text>
Removing the location
no location
Note
Comments
For configuring the system clock and date&time, refer to Clock Selection and
Date and Time sections, respectively.
To display device information:
At the config>system# prompt, enter show device-information.
For example:
Administration
5-329
mp4100>config>system# show device-information

Name
: MP-4100_ph_3.0
Location : Ziv_Towers
Contact : Yaniv
Managing the SONET/SDH Link Rate Selection License

By default, the CL.2 modules are supplied with STM-1/OC-3 ports. To enable the
STM-4/OC-12 functionality, a software license key MP-4100-LIC/622SK is
required. You can order it together with the product or later, when the upgrade is
needed. The license is based on the module MAC address and must be ordered
separately for each CL.2 module.
Once the license is downloaded, the SDH/SONET ports are software-configurable
to STM-4/OC-12 or STM-1/OC-3.
Checking the License Availability

If you do not know whether your device features the STM-4/OC-12 functionality,
follow the procedure below:
1. Try to configure the port to 622 Mbps speed. In this example we want to
configure all 4 SDH/SONET ports for STM-1/OC-4 operation.
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
configure port sdh-sonet cl-a/1 speed 622mbps

configure port sdh-sonet cl-a/2 speed 622mbps
configure port sdh-sonet cl-b/1 speed 622mbps
configure port sdh-sonet cl-b/2 speed 622mbps
commit
If there is no valid license is available, the ON LINE LEDs of the SDH/SONET ports
on the corresponding CL module go off and the following sanity is displayed:
Sdh
Cl-A/01 (W310)NO LICENSE FOR STM-4/OC-12
You can also see the corresponding alarms notifying of license mismatch.
5-330
Administration
mp4100#
mp4100# show configure reporting active-alarms
Total :
Critical : 0
Major : 4
1
Maj
2
Maj
3
Maj
4
Maj
SDH-SONET
unmasked
SDH-SONET
unmasked
SDH-SONET
unmasked
SDH-SONET
unmasked
Minor
: 0
cl-a/1
LICENSE_MISMATCH
cl-a/2
LICENSE_MISMATCH
cl-b/1
LICENSE_MISMATCH
cl-b/2
LICENSE_MISMATCH
---------------------------------------------------------------
Ordering the License

In order to activate the STM-4/OC-12 functionality, the license file must be
downloaded and activated. Once purchased, the license is permanent and does
not expire.
The licenses are based on the CL.2 module MAC address and distributed as
software files named *.txt, for example LIC_0020D2500C48.txt. The files can be
obtained from the local RAD Partner from whom the device was purchased. Each
license is ordered per CL module.
To display the MAC Address of CL-A/CL-B:
Use configure>chassis>show manufacture-info command as illustrated in the

following example.
mp4100# configure
mp4100>config# chassis
mp4100>config>chassis#
mp4100>config>chassis# show manufacture-info slot cl-a
First MAC Address : 00-20-D2-50-0E-93
Number of MACs
: 1
mp4100>config>chassis#
mp4100>config>chassis# show manufacture-info slot cl-b
First MAC Address : 00-20-D2-50-05-B0
Number of MACs
: 1
You can also use the following syntax:
mp4100# show configure chassis manufacture-info slot cl-a
First MAC Address : 00-20-D2-50-0C-48
Number of MACs
: 1
mp4100#
mp4100# show configure chassis manufacture-info slot cl-b
First MAC Address : 00-20-D2-50-05-B0
Number of MACs
: 1
The Number of MACs field value in the case of Megaplex-4100 is always 1.
The software upgrade utility includes four partitions called license-1, license -2,
license -3, license -4 for downloading and storing the licenses.
Administration
5-331
You can download the license file to Megaplex-4100 via CLI in either of two ways:
TFTP when downloading over a network
XMODEM when downloading over a dumb terminal connected to the

Megaplex-4100 control port.
Downloading the License File Using TFTP
To download the license file using TFTP:

1. Assign the IP address to the Megaplex-4100 device as described in
Management Router section.
Download the valid license obtained from RAD using file>copy command as
follows.
For example:
Host IP (PC) address is 172.17.170.38.
License file for CL-A is LIC_0020D2500C48.txt
License file for CL-B is LIC_0020D25005B0.txt.
mp4100# file copy tftp://172.17.170.38/LIC_0020D2500C48.txt license-1

Are you sure? [yes/no] _ y
mp4100#
File copy command was completed.
tftp://172.17.170.38/LIC_0020D2500C48.txt copied to license-1 successfully
139 bytes copied in 2 secs (69 bytes/sec)
mp4100#
mp4100# file copy tftp://172.17.170.38/LIC_0020D25005B0.txt license-2
mp4100#
tftp://172.17.170.38/LIC_0020D25005B0.txt copied to license-2 successfully
Type commit.
Now the license file is downloaded to the device.
Downloading the License File Using XModem
To download the License File using XMODEM:

1. Type the following command (in our example we are downloading the license
to license-4 partition):
mp4100>file# copy xmodem: license-4
mp4100>file#
*****The terminal will become disable !!!
Please send the file
*****
Using the terminal application, select the license file and click the send button.
5-332
Administration
*****
File copy command was completed.*****
*****xmodem: copied to license-4 successfully*****
*****256 bytes copied in 10 secs (25 bytes/sec)*****
Now the license file is downloaded to the device.
Installing the License for Redundant CL Modules

If two redundant modules (CL-A and CL-B) are installed in the chassis, the license
must be installed both in the working and protection CL modules.
To ensure this, proceed as follows:
1. Install both CL modules in the chassis.
2. Download the license file to CL-A.
3. Reset the CL-A module.
Now the CL-B module become active (working) and you can download the
license to it.
4. Download the license file to CL-B.
5. Reset the CL-B module.
Now the modules can operate at STM-4/OC-12 rates as a redundant pair.
File Operations
You can perform the following operations:
Copy files within the Megaplex-4100 unit
Display files within the Megaplex-4100 unit
Delete files.
File Names in the Unit

Megaplex-4100 uses the following reserved file names:
factory-default Contains the factory default settings
running-config Contains the current user configuration that is different

from the default configuration.
startup-config Contains saved user configuration. You must save the file
startup-config; it is not automatically created. Refer to Saving the
Configuration for details on how to save the user configuration.
user-default-config Contains default user configuration. Refer to Saving the

Configuration for details on how to save the default user configuration.
candidate Stores any configuration before it is copied to running-config via

commit command.
main-sw Contains the active software image.
You can copy files via the copy command, or via the commands shown in
Table 5-66.
Administration
5-333
Table 5-66. Commands That Copy Files

Command
Level
Copies
Manual Section
factory-default
admin
factory-default to candidate
(then use commit to copy factory-default
to running-config and then save to copy
it to startup-config)
Resetting to Factory
Defaults
user-default-config
admin
user-default-config to candidate
(then use commit to copy
user-default-config to running-config and
then save to copy it to startup-config)
Resetting to User
Defaults
save
global
running-config to startup-config
Saving the Configuration
Copying Files within Megaplex-4100

You can copy files within the Megaplex-4100 unit with the copy command.
Figure 5-48 shows the commands that can copy configuration files in a visual
diagram.
Admin user-default
Sanity
check
Running-config
User-Default Config
Startup-Config
Save
TFTP
Configuration
Session
(Candidate DB)
Copy
Copy
Factory-Default
TFTP
Commit
Copy
Admin factory-default
Figure 5-48. Commands that Copy Configuration Files
To copy files within the device:
At the file# prompt, enter:

copy <source-file> <dest-file>.
For example:
5-334
Source file name running-config
Destination file name startup-config.
Administration
mp4100# file
mp4100>file# copy running-config startup-config
To display the last copy command result:
At the file# prompt, enter: show copy.
mp4100# show file copy

Network to Device, Transferring Data
Src: tftp://172.17.174.56/mp4cl2_03_00b06.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Transferred : 665600 Bytes in: 16 seconds (41600 Bytes/Second)
To view the copy command history:
At the file# prompt, enter: show copy summary.
For example:
mp4100>file# show copy summary
Direction
Source
1
Local
running-config
2
Local
running-config
Dev to Net startup-config
Destination
End Time
user-default-conf 13-3-2011
14:6:51
startup-config
13-3-2011
14:7:35
DB
13-3-2011
14:7:40
Status
Ended OK
Ended OK
Ended OK
Displaying Files within Megaplex-4100

The dir command is used to display the files within the device.
To display the files:
At the file# prompt, enter dir.

A list of the file names and types is displayed.
For example:
mp4100>file# dir
Codes
C - Configuration S - Software
LO Log
Name
Type Size(Bytes) Creation Date Status
sw-pack-1
S
6306207
21-12-2010
valid
13:44:58
sw-pack-2
S
6305847
21-2-2011
valid
7:48:0
sw-pack-3
S
6278526
21-2-2011
valid
9:57:47
sw-pack-4
S
6289552
6-1-2011
valid
10:23:13
startup-config
C
95872
13-3-2011
valid
14:7:35
user-default-config C
95872
13-3-2011
valid
14:6:51
factory-default-conf C
796
1-1-1970
Read Only
0:0:9
running-config
C
0
1-1-1970
Read Only
0:0:9
Administration
5-335
Total Bytes : 101367808
Free Bytes
: 69701632
Deleting Files
You can delete files. Before deleting the file, make sure the file is not in use. For
additional information on configuration files and the consequences of deleting,
refer to Configuration Files and Loading Sequence in Chapter 3.
To delete a file:
1. At the file# prompt, enter: delete <file-name>.
You are prompted to confirm the deletion.
For example:
mp4100# file
mp4100>file# delete sw-pack-1
File will be erased. Are you sure?? [yes/no] _yes
Confirm the deletion.
The unit reverts to the factory default.
Saving the Configuration

You must save your configuration if you wish to have it available, as it is not
saved automatically. You can save your configuration as outlined below.
Additional information on config files is available under Configuration Files in
Chapter 3.
To save your current configuration in the startup-config file:
At any level, enter save.
At the file# prompt enter:

copy running-config startup-config.
Resetting Megaplex-4100
Megaplex-4100 supports the following types of reset:
Reset to factory defaults
Reset to user defaults
Overall reset (restart, reboot) of the device.
Resetting to Factory Defaults
To reset Megaplex-4100 to factory defaults:

1. At the device prompt, enter admin.
The admin> prompt appears.
Enter factory-default.
A confirmation message is displayed:
Current configuration will be erased with factory default configuration.
Are you sure?? [yes/no]
5-336
Administration
Enter yes to confirm resetting to factory defaults.

The factory-default file is copied to the candidate file.
Enter commit to complete the operation.
The factory-default file via Candidate DB is copied to the running-config
file. Now at the device startup, the factory defaults are loaded.
Resetting to User Defaults
To reset Megaplex-4100 to user defaults:

1. At the device prompt, enter admin.
The admin> prompt appears.
Enter user-default.
Current configuration will be erased with user default configuration. Are
you sure?? [yes/no]
Enter yes to confirm resetting to user defaults.
The user-default-config file is copied to the candidate file.
Enter commit to complete the operation.
The user-default config file via Candidate DB is copied to the
running-config file. Now at the device startup, the user defaults are
loaded.
Rebooting the Megaplex-4100 Chassis
To reboot the chassis:

1. At the admin# prompt, enter the reboot command.
Chassis will reboot. Are you sure?? [yes/no]
Enter yes to confirm the reset.
The chassis restarts.
Rebooting the Module

Use the following procedure to reboot a module installed in a specified slot.
Note
Resetting a module will temporarily disrupt services supported by that module.

To reboot a module:
1. Navigate to configure slot <slot>.
The config>slot<slot># prompt is displayed.
Enter reset.
Card will reset. Are you sure?? [yes/no]
Administration
5-337
Enter yes to confirm the reset.

The module restarts.
5-338
Administration
Chapter 6
Monitoring and
Diagnostics
The Megaplex-4100 monitoring and diagnostic functions can be used to identify
problems in the network incorporating Megaplex-4100 units, test the proper
operation of each Megaplex-4100 unit, and rapidly locate the cause of the fault
within the Megaplex-4100 itself, in its connections to the network or to user
equipment, or in another network component.
In addition to the general Megaplex-4100 functions described in this Chapter, you
can find information on the module-specific diagnostic functions in Appendix B.
If you need additional support for this product, see Section 6.5 for technical
support information.
The available functions include:
Detection of configuration (sanity) errors
Alarm and event collection, and reporting of relevant alarms
Configuration error (sanity) messages
Collection of performance monitoring data
Ping test
Diagnostic tests for checking transmission paths.
6.1
Detecting Problems
Problems can be detected on the hardware level, for example by running the
self-test and monitoring the LED behavior.
On the software level, you can follow statistical counters and events and errors
returned by the system.
Indicators
Megaplex-4100 modules and the Megaplex-4100 chassis itself have various status
indicators that can be used to identify problems.
Refer to Chapter 2 of this manual for details regarding the functions and
indications of each system indicator and to Chapter 3 of this manual for normal
indications after power-up. Also refer to Appendix B for details regarding the
functions and indications of each module indicator.
Detecting Problems
6-1
Chapter 6 Monitoring and Diagnostics
Alarms and Traps

Megaplex-4100 generates various alarms that can be displayed by means of a
supervision terminal, and sends alarm traps to management stations that enable
the operators to identify problems.
Megaplex-4100 maintains a cyclic event log file that stores up to 200
time-stamped events. In addition, an internal system log agent can send all
reported events to a centralized repository or remote server.
Statistic Counters
Megaplex-4100 collects statistics per physical and logical ports (see the list
below) for 15-minute intervals. This enables the network operator to monitor the
transmission performance, and thus the quality of service provided to users, as
well as identify transmission problems. Performance parameters for all the active
entities are continuously collected during equipment operation.
Statistics for the last 24 hours are stored in the device and can be retrieved at
the network management station.
Statistic counters provide information on possible abnormal behavior and failures.
You can display statistics of the following:
RADIUS server
Ethernet, SDH/SONET, E1/T1, SHDSL, VCG, PCS, GFP, HDLC and PW ports.
For further information, refer to the relevant sections in Chapter 4 and the
relevant sections in the troubleshooting chart.
Configuration Error Messages

Megaplex-4100 includes an extensive subsystem that checks the validity of the
users configuration activities and reports any conflicts and errors.
The tables below list and explain the error messages generated by
Megaplex-4100. Such messages are referred to as sanity errors, because they
are detected by the so-called sanity check automatically performed to confirm
correct configuration of the equipment.
Two types of messages are generated:
Warning
Minor errors that do not prevent using the Megaplex-4100;

for example, an installed module is not programmed in the
chassis.
Error
Errors that prevent proper operation of the Megaplex-4100

in its intended application; for example, an invalid timeslot
assignment).
The messages are listed in ascending order of their codes.
6-2
Detecting Problems
Table 6-1. Global Sanity Messages

Code
Type
Syntax
Meaning
100
Error
AT LEAST ONE PS CARD MUST

BE DEFINED
At least one power supply module must be defined in the

system configuration
101
Error
AT LEAST ONE CL CARD MUST

BE DEFINED
At least one CL module must be defined in the system

configuration
102
Warning
MODULE TYPE MISMATCH
The modules actually installed in the equipment and the

modules programmed in the database are not the same
103
Warning
INTERFACE HW/SW MISMATCH
The interface type configured by the management system

is different from the interface selected by means of
jumpers
Table 6-2. Clock Sanity Messages

Code
Type
Syntax
Meaning
110
Error
ILLEGAL CLOCK SOURCE
The selected clock source is invalid for one of the

following reasons:
The configured module port cannot supply a reference

clock
The port rate is not suitable for use as clock source

(e.g., LS-12 channel operating at a rate of 14.4 kbps)
The I/O module port is selected as clock source, but its

interface type is not DTE
The interface of the ISDN channel selected as a clock

reference cannot provide a reference clock. For
HSU-6/HSU-12 modules, the channel must be
configured as NT
112
Error
CLOCK SOURCE IS IN
SHUTDOWN STATE
When configuring the clock source to be locked to the

receive clock of a module/channel, the source
module/channel must be connected
114
Error
CLOCK SOURCE CAN'T BE

UNFRAMED
Unframed (transparent) E1/T1 ports from M16E1/16T1,

ASMi-54C/N, or OP modules cannot serve as clock source
(only M8E1/M8T1 ports can)
115
Error
RECOVERED CLOCK - PW DOES You are trying to configure a recovered clock source but
NOT EXIST
the PW associated to it does not exist.
116
Error
DOMAIN NET TYPE DOES NOT

MATCH SDH/SONET
Domain network type 1 and 2 must match sdh and sonet

frame-type, respectively.
Table 6-3. Module Sanity Messages

Code
Type
Syntax
Meaning
130
Error
CLOCK MODE/CLOCK SOURCE

MISMATCH
The EXT-DCE clock mode cannot be selected when the

port interface is configured as LT-1 (applicable only for
HS-U-6 and HS-U-12 modules)
Detecting Problems
6-3
Code
Type
Syntax
Meaning
131
Warning
RESTORATION TIME DOES NOT For T1 links, the restoration time must be 10 seconds,
MATCH THE STD
according to the standard.
For E1 links, the restoration time must be in accordance
with ITU-T recommendations
132
Error
FRAME TYPE / PROFILE

MISMATCH
One of the following:
The selected framing mode does not support signaling

profiles
When the station clock is configured to interface-type=

e1 with tx-ssm enabled, line-type must be g732n-crc
Table 6-4. E1/T1 Sanity Messages

Code
Type
Syntax
Meaning
140
Error
ILLEGAL TDM PROTECTION

ASSIGNMENT
The protection assignment of one port does not point to

another port
141
Error
ROUTING PROTOCOL/
MNG TYPE MISMATCH
The rip2 protocol on an I/O module port can be enabled

only when the inband management method is configured
to ppp or fr
142
Error
PORT CAN PARTICIPATE ONLY

IN ONE TDM GROUP
An E1/T1 port cannot be member of several TDM

protection groups.
143
Error
Y-CABLE CANT BE FOR PORTS

ON SAME CARD
Y-cable protection can be configured only for ports on

different I/O modules
144
Error
ILLEGAL IDLE CODE SELECTION
Code transmitted in idle timeslots is illegal.
145
146
Error
Error
The available selections for E1/E1-i ports are [0x01 to

0xFF] with the following values that are illegal: 0x00,
0x08, 0x10, 0x12, 0x21, 0x24, 0x42, 0x49, 0x84, 0x92
The available selections for T1/T1-i ports are [0x40 to

0x7F] and [0xC0 to 0xFF]
Y-CABLE PROTECTION ONLY

BETWEEN I/O CARDS
Y-cable protection can be configured only between ports

on I/O modules (E1-i/T1-i ports of CL modules cannot be
Y-cable protection group members)
NUM OF E1/T1 PORTS

EXCEEDS 120
The maximum number of framed E1/T1 ports opened on

the M16E1/M16T1, ASMi-54C/N or OP modules must not
exceed 120.
Table 6-5. HS-12N/HS-6N Sanity Messages

Code
150
6-4
Type
Error
Syntax
Meaning
FIFO SIZE TOO SMALL
The manually-selected FIFO size must be equal or larger

than the minimum FIFO size required for the selected rate
and link type (E1 or T1)
Detecting Problems

Code
151
152
Type
Error
Error
Syntax
Meaning
ILLEGAL CHANNELS RATE

COMBINATION
All channels are configured for operation in multiples of

64 kbps or 56 kbps. This error may be caused by:
Selection of 64K in an odd-numbered channel (e.g.,

channel 1) and 56K in an adjacent channel (e.g.,
channel 2) is not allowed.
The total rate of 2 adjacent channels must not require

more than 31 timeslots
CTS SHOULD BE SAME FOR ALL All the channels of the specified module must be
CHANNELS
configured with the same CTS mode
Table 6-6. VC Modules Sanity Messages

Code
170
Type
Error
Syntax
Meaning
ILLEGAL SIGNALING METHOD
You can select the channel associated signaling method

only when an E1 module port with G.732S framing is used.
You can select the robbed bit multiframe signaling transfer
method only for E1 links with G.732S framing, or on T1
links.
171
Warning VOICE CODING LAW (E1/T1)

MISMATCH
The selected voice companding law differs from the

companding law specified by the standards: the A-law is
generally used for E1 links, and the -law is generally used
on T1 links
172
Error
TX GAIN VALUE OUT OF RANGE The transmit gain selected for the specified channel is not
within the supported range
173
Error
RX SENSITIVITY VALUE OUT OF

RANGE
The receive sensitivity (gain) selected for the specified

channel is not within the supported range
174
Error
OOS/INTERFACE MISMATCH
The selected OOS mode cannot be used on this type of

interface
175
Error
SIGNALING PROFILE/INTERFACE The selected profile cannot be used on this type of

MISMATCH
interface
176
Error
ILLEGAL NUMBER OF WIRES
Voice modules with /FXO and /FXS interfaces support only

the two-wire interface.
For voice modules with /E&M interface only, it is possible
to select two-wire or four-wire interfaces. In addition, for
VC-4/4A/8A/16 modules with /E&M interface, the same
interface type must be selected for consecutive pairs of
channels (for example, 1, 2 or 15, 16)
177
Error
NO SIGNALING IS ILLEGAL FOR

THIS INTERFACE
The selected interface cannot be used with no signaling

the signaling option must be specified
Detecting Problems
6-5

Code
Type
Syntax
Meaning
179
Error
ILLEGAL ANALOG SIG

COMBINATION
For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of

analog-signaling parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
180
Error
ILLEGAL FXO SIG FEEDBACK

COMBINATION
For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of

signaling-feedback parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
Table 6-7. ADPCM Voice Modules Sanity Messages

Code
181
Type
Syntax
Meaning
Error
ILLEGAL TS SPLIT CONFIG FOR

ADPCM MODE
Split timeslot cross-connect must be peformed on a pair

of ports (1,2 or 3,4..)
Table 6-8. Timeslot Sanity Messages

Code
190
Type
Syntax
Meaning
Error
ILLEGAL DEST SLOT/PORT

CONNECTION
One of the following conditions has been detected:
One or more module channels are connected to a

disabled port (that is, a port configured to shutdown).
One or more module channels are connected to a port

that cannot provide the required connection (for
example, the port is connected to another I/O port).
For a tdm cross-connection: the port definitions are

not symmetrical
191
Error
ILLEGAL TIMESLOT
ASSIGNMENT
The required number of timeslots must be exactly the

same as the number of timeslots assigned on the relevant
module port
192
Error
ILLEGAL CROSS CONNECT
The number of timeslots routed between two module

ports must be the same for both modules
193
Error
TS-16 IS RESERVED FOR CAS

SIGNALING
To bypass signaling information between E1 ports on

different modules, timeslot 16 of one module must be
bound to timeslot 16 on the other module. Both ports
must use G732S framing, with or without CRC-4 (G732S,
G723S-CRC4).
194
Error
ILLEGAL POSITION OF TS BIT

ASSIGNMENT
When using split timeslot assignment:
2-bit assignments must start at bit 1, 3, 5 and/or 7.
4-bit assignments must start at bit 1 and/or 5.
Consecutive bits must be assigned to the same channel

195
6-6
Error
TS ASSIGNMENT/TS REQUEST
MISMATCH
Detecting Problems
The timeslot bit assignment does not match the

requirements for such timeslots

Code
196
Type
Syntax
Meaning
Error
INCORRECT TS TYPE
The definition of the timeslot must correspond to the type

of information generated by the module using the
timeslot:
Timeslot cross-connected to serial port: the type must

be data (this also applies to timeslots cross-connected
to HSF modules).
Timeslot cross-connected to voice I/O module: the type

must be voice.
In addition, the types of timeslots cross-connected

between links must be identical.
197
Warning
TS DATA TYPE DOESNT MATCH For T1 links, do not use the B7ZS line code when one or
B7ZS LINE CODE
more timeslots are defined as data timeslots
198
Error
ILLEGAL BROADCAST
DEFINITION
The ds0 cross-connect for the specified channel is not

correct.
199
Error
NOT COMPLETE BROADCAST

DEFINITION
The timeslot assignment for the specified port is not

complete.
202
Error
UNFRAMED TYPE CROSS-CONNECT
TDM cross-connect is not supported between the

following modules:
MISMATCH
OP-108C/34C (E1 ports), M16E1/M16T1 (E1/T1 ports),

ASMi-54C/N modules (E1, E1-i ports) on one side
M8E1/M8T1 modules (E1/T1 ports), M8SL (E1-i ports),

or MPW-1 (DS1 ports) on the other side
Table 6-9. Timeslot LS-6N/LS-12 Sanity Messages

Code
210
Type
Syntax
Meaning
Error
BANDWIDTH OVERFLOW
The bandwidth allocated to the internal port of the

LS-6N/LS-12 module must be greater than, or equal to the
sum of the following:
The bandwidths allocated to the external ports
Management channel, if the remote unit is a KM

working in slave mode
Frame synchronization
Channel end-to-end control signals (one per pair)
211
Error
SERIAL PORTS NOT IN SAME

RATE GROUP
212
Error
SERIAL PORTS NOT BOUND TO The two adjacent serial ports (1/2, 11/12) of an LS-12
SAME SERIAL BUNDLE PORT
module must be bound to same serial bundle port.
213
Error
SERIAL PORT/SERIAL-BUNDLE
PORT RATE MISMATCH
The two adjacent serial ports (1/2, 11/12) of an LS-12

module must operate in the same rate group.
The external port rate is not compatible with the data rate
allocated on the link to the corresponding internal port
Detecting Problems
6-7

Code
214
Type
Syntax
Meaning
Error
NO EXTERNAL CHANNEL IS
CONNECTED
The internal port is connected to the link, but no external

port is connected to the internal port
Table 6-10. M8SL Sanity Messages

Code
Type
Syntax
Meaning
220
Error
RATE/TS ASSIGNMENT
MISMATCH
The line rate configured for the M8SL port must match the
number of timeslots assigned
221
Error
CLOCK REFERENCE PORT

SHOULD BE SET STU-R
The M8SL port configured as clock reference must be

configured as STU-R
222
Error
MAX BANDWIDTH MISMATCH
Maximum bandwidth configured on the SHDSL line must

match the number of timeslots assigned
Table 6-11. VC-4/OMNI Sanity Messages

Code
Type
Syntax
Meaning
241
Error
ONLY FIRST TRIBUTARY CAN

BE CONNECTED
If operation-mode is ptp, only the first tributary channel

of this voice port can be connected. All the other tributary
channels must be set to shutdown.
242
Error
FIRST TRIBITURY MUST BE

CONNECTED
If the operation-mode is p2mp-dst, and the first internal

channel is not connected, the other internals can be
connected and can carry traffic
Table 6-12. SDH/SONET Sanity Messages

Code
Type
Syntax
Meaning
300
Error
TOO MUCH VCS/VTS
The maximum number of virtual containers that can be

used by one virtually concatenated group cannot exceed
63 for VC-12, or 64 for VT1.5
301
Error
MINIMUM NUMBER OF VCs/VTs The minimum number of virtual containers (VC-12 or

IS 2
VT-1.5) in a group is 2
302
Error
VC GROUP IS NOT CONNECTED The virtually concatenated group is not bound to any
other entity. Check and correct
303
Error
DIFFERENT CLS FRAME

STRUCTURE
The two CL modules installed in the Megaplex-4100 must

use the same link standards (either SDH or SONET)
305
Error
MISSING E1-I/T1-I SDH-SONET

CROSS CONNECT
An E1-i/T1-i port is opened on CL.2 but not crossconnected to VC/VT on SDH/SONET.
307
Error
ILLEGAL VCG MAPPING
The virtually concatenated group mapping is not correct
309
Error
E1-I/T1-I PORT IS AT
SHUTDOWN
e1-i/t1-i port cannot be cross-connected when it is in

shutdown state. Set the port to no shutdown
6-8
Detecting Problems

Code
Type
Syntax
Meaning
310
Warning
NO LICENSE FOR STM-4/OC-12 The port is configured to 622mbps but the CL does not
have an appropriate license.
311
Error
ILLEGAL BINDING
Pay attention to the following:
A VCG and a VC-VT container bound to it must belong

to the same CL module (A or B).
A Logical MAC and a GFP/HDLC port bound to it must

belong to the same CL module (A or B).
A GFP/HDLC port and a VCG bound to it must belong to

the same CL module (A or B).
A GFP/HDLC port defined as no shutdown must be

bound to a Logical MAC
A VCG port defined as no shutdown must be bound

to a GFP/HDLC port.
312
Error
ILLEGAL SDH/SONET CROSS

CONNECT
An E1-i/T1-i port and a VC-VT container cross-connected

with it must belong to the same CL module (A or B).
313
Error
NUMBER OF LIMITED VC-VT XCONNECTS EXCEEDED
Pay attention to the following:
314
Error
ASSIGNMENT/NUMBER OF VC
MISMATCH
Number of vc-vt containers per CL module is limited to

252.
Number of vc-vt containers for EoS per CL module is

limited to 128.
One of the following:
Mismatch between the link speed

(155mbps/622mbps) and the number of virtual
containers defined. The numbers should not exceed
the following ranges:
SDH:
<port 1..2>
aug <aug number 1..4> (1 for STM-1)
tug3 <tug3 number 1..3>
vc12 <tug2 number 1..7>
<tributary number 1..3>
SONET:
<port 1..2>
oc3 (<oc3 number 1..4> (1 for OC-3)
sts1 (<sts1 number 1..3>
vt1-5 (<tug2 number 1..7>
<tributary number 1..4>).
315
Error
A VC cannot be bound/cross-connected simultaneously

to multiple sources (VCG port, E1-i/T1-i port,
etc).
VCAT NUMBER OF VCs LIMITED The maximum number of virtual containers (VC-12 or VTTO 64
1.5) that can be bound to one VCG cannot exceed 64
Detecting Problems
6-9

Code
Type
Syntax
Meaning
316
Error
GFP/HDLC PORT CAN BE

BOUND TO SINGLE VC-VT
ONLY
A GFP or HDLC port of the CL module can be bound only

to a single vc-vt container.
317
Error
VC-PROFILE DOES NOT MATCH The VC profile content does not match the port type.
PORT TYPE
318
Error
WRONG LCAS PARAMETER
One of the LCAS parameters does not match one of the

VCG parameters.
Table 6-13. System Sanity Messages

Code
Type
Syntax
Meaning
400
Error
DIFFERENT CL CARDS FOR

REDUNDANCY
Different CL module types are installed in slots CL-A and

CL-B; CL redundancy is not available
404
Error
PORT ASSIGNED IS IN
SHUTDOWN STATE
One of the two ports connected via flow, cross-connect or

bind command is in shutdown state. Set this port to no
shutdown.
Table 6-14. HDLC/PPP/MLPPP Port Sanity Messages

Code
Type
Syntax
Meaning
420
Error
MLPPP PORT CAN'T BE BOUND E1 port bound to MLPPP port cannot be a member of
TO TDM GROUP
protection group
422
Error
MLPPP PORT SHOULD BE

BOUND TO UNFRAMED E1
MLPPP port cannot be bound to a framed port
423
Error
HDLC/PPP PORT OR
ASSOCIATED E1/T1 PORT
DOWN
Whenever the HDLC/PPP port is connected, the associated

ports should be at no shutdown, and vice-versa.
424
Error
HDLC/PPP ILLEGAL SLOT

ASSOCIATION
The I/O slot specified for an HDLC port and the slot of its
associated E1/E1-i/T1/T1-i port cannot be another I/O
slot. It must be either the same I/O slot or CL-A/CL-B.
The I/O slot specified for a PPP port and the slot of its
associated E1 port must be the same I/O slot.
426
Error
MORE THAN ONE MLPPP PORT Only one MLPPP port can be active on any given I/O
PER SLOT
module
427
Error
ONLY ONE E1/T1 PORT CAN BE Only one E1/T1 port can be bound to a single HDLC port
BOUND TO HDLC PORT
429
Error
EVEN TS NUM MUST BE

DEFINED PER HDLC PORT
HDLC rate must be a multiple of 128 kbps (even number

of timeslots).
430
Error
LINKS ASSIGNED FOR MLPPP

PORT EXCEEDED
The maximum number of E1 ports that can be bound to

MLPPP port is 8.
431
Error
ILLEGAL NUMBER OF
TIMESLOTS
Illegal number of timeslots has been selected
6-10
Detecting Problems

Code
Type
Syntax
Meaning
432
Error
ILLEGAL HDLC SLOT

ASSIGNMENT
All 4 HDLC ports bound to a specific E1-i/T1-i port must be

assigned (for processing) to the same I/O module.
433
Error
MAX 4 HDLC PORTS MAY BE

DEFINED PER LINK
The maximum number of HDLC ports defined per

E1/E1-i/T1/T1-i port is 4
434
Error
PORT LINE TYPE MISMATCH
TDM cross conect can be done only for unframed E1/T1

ports
437
Error
SAME E1 BOUND TO
DIFFERENT PPP PORTS
E1 port cant be bound to more than one PPP port
Table 6-15. MPW-1 Sanity Messages

Code
460
Type
Syntax
Meaning
Error
SAME IP FOR ROUTER INTERF

& D.GATEWAY
The same IP address has been defined for both the

default gateway and for one of the router interfaces. This
is not allowed.
Note however that this error may also appear because the
default IP address (0.0.0.0) have not yet been changed.
461
Error
NOT SAME SUBNET FOR

At least one of the IP addresses assigned to router
ROUTER INTERF & D.GATEWAY interfaces must be in the IP subnet of the Megaplex-4100
router default gateway.
463
Error
IN PW LABEL IS NOT UNIQUE
This message, which is generated only after the specified

pseudowire is switched to the no shutdown state,
indicates that two or more pseudowires have the same
source UDP port number (the check is made irrespective
of the pseudowire PSN type, UDP/IP or MPLS/ETH). This is
not allowed.
464
Error
IP & NEXT HOP ARE THE SAME

FOR STATIC ROUTE
This message is generated after the specified static route

is updated, and indicates that the next hop IP address and
the destination IP address of the route are the same.
This is not allowed the addresses must be different. If
the next hop IP address is not needed, leave the default
value, 0.0.0.0.
default IP addresses (0.0.0.0) have not yet been changed.
465
Error
STATIC ROUTE IP IS NOT

UNIQUE
This message, which is generated only after the specified

static route is updated, indicates that the route
destination IP address is already used in another static
route.
This is not allowed only one static route may be defined
for any specific destination IP address.
default IP addresses (0.0.0.0) have not yet been changed
Detecting Problems
6-11

Code
466
Type
Error
Syntax
Meaning
ROUTER INTERF CAN'T BE ON

THE SAME SUBNET
The IP addresses assigned to the router interfaces must

be in different IP subnets.
467
Error
MORE THAN 16 PWS FOR DS1

PORT
You are trying to connect too many pseudowires to the

same ds1 port (the maximum is 16 pseudowires per port).
468
Error
ILLEGAL FAR END TYPE

FRAMING
The pseudowire far-end-type-mp parameter must match

the framing mode of the ds1 port supporting the
pseudowire:
Framed mode: select e1, t1-esf, or t1-sf
Unframed mode: select unframed.
469
Error
DS1 PORT OF PW IS DOWN
The ds1 port assigned to a pseudowire is set to

shutdown. Change its setting to no shutdown.
470
Error
TOO MANY ROUTER

INTERFACES
You are trying to configure more than 6 router interfaces

on a MPW-1 module (MPW-1 supports a maximum of 6
router interfaces). Check and remove unused interfaces.
471
Error
NUMBER OF BYTES IN FRAME

EXCEEDS 1440
In CESoPSN the number of TDM payload bytes is equal to

{tdm-payload value <4360> * (number of timeslots
cross-connected between the PW and DS1 port).
This number must not exceed 1440 bytes.
472
Warning
CHANGE MAY CAUSE DATA

INTERFERENCE
As a result of the last configuration actions, during the

database update you are initiating, the internal MPW-1
pseudowire processing assignments will be recalculated.
You are warned that this may this cause a short traffic
disruption (errors) for the other pseudowires served by
the same MPW-1 module. If this is not acceptable,
postpone the update and perform it while traffic load is
light
473
Error
WRONG TIMESLOT
ASSIGNMENT
When the redundancy partner of a DS1 port of the MPW-1

is a T1 port, it is not allowed to assign more than 24
timeslots on the DS1 port.
474
Error
WRONG SATOP PARAMETERS
When using the SAToP protocol, make sure that DS1 port
is cross-connected via ds1 command and not ds0.
far-end-type-mp should be set to unframed.
475
Error
PWS FROM DIFF SLOTS

DEMANDS DIFF PEERS
Pseudowires configured on different MPW-1 modules

must be configured with different peers, even if the
destination address is the same.
Using different peer numbers will result in the creation of
different internal flows, each directed to the relevant
router interface
476
Error
PROTECTED PORTS HAVE

ASSYMETRIC PARAMETERS
When TDM protection is configured between two DS1

ports, all their physical layer parameters must be identical
PEER DOESN'T EXIST
You have specified a peer index during the creation of a

pseudowire, but the peer has not yet been created.
477
Error
6-12
Detecting Problems

Code
478
Type
Error
Syntax
Meaning
PEER NEEDS ROUTER

INTERFACE
It is not possible to configure peers before at least one

router interface has been configured.
479
Error
V1/V2 PW LABEL DUPLICATED
After assigning a label to a pseudowire using payload

format V1, do not assign the next label in sequence to a
pseudowire using payload format V2 (skip that label).
480
Error
PEER NOT ATTACHED TO PW
You have created a PEER without attaching it to any

pseudowire.
481
Error
SLOT/PORT OF RI IS NOT
CONNECTED
You must configure a flow between the router interface

and the Ethernet entity
482
Error
ASSYMETRIC FAR END TYPE

FOR PROTECTED PORTS
When TDM protection is configured between two DS1

ports, all their far-end-type parameters must be identical
483
Error
PW FAR END TYPE PER SLOT

MUST BE FRAMED
When signaling is enabled on the DS1 port attached to a

pseudowire, the far-end-type-mp for all the pseudowires
terminated on the corresponding module must be set to
framed mode (either E1 or T1).
484
Error
PEER PARAMETERS ARE

DUPLICATED
Different peers must not have the same destination IP

address and the same Next Hop IP address (at least one
of these parameters must be different). Therefore, if it
necessary for several pseudowires to reach the same IP
address, create separate router interfaces.
486
Warning
TS NOT ASSIGNED TO ANY PW
The specified MPW-1 DS1 port is connected to local

module ports, but no pseudowire has been assigned
timeslots on the same port.
You must specify timeslots to be connected to the DS1
port
487
Error
PW CREATED BUT NOT

ASSIGNED
A PW was created but not cross-connected to DS1 port.
488
Error
PW CANT SERVE AS
RECOVERED CLK
A pseudowire using the HDLCoPSN protocol cannot serve

as recovered clock source
489
Warning
TS 16 IS RESERVED FOR CAS

SIGNALING
It is not allowed to assign timeslot 16 to a pseudowire

configured with signaling enabled and far-end-type=e1
490
Error
FAULT PROPAGATION OF PW
MUST USE OAM
To use fault propagation for pseudowires, you must

enable the use of OAM
491
Error
SAME IP CONFIGURED IN
ANOTHER INTERFACE
More than one router interfaces are configured with the

same IP address
493
Error
STATIC ROUTE ADDRESS DOES

NOT MATCH
Next hop address of static route is invalid
Detecting Problems
6-13
Table 6-16. OP-108C/OP-34C Sanity Messages

Code
Type
Syntax
Meaning
500
Warning
FAR-END CHANGED, DEVICE

WILL RESTART
The type of far-end device connected to the OP-108C

module is different from the one configured. The module
will perform a reset.
501
Error
NOT IDENTICAL FAR-END

DEVICE TYPE
When two far end devices are connected to the OP-108C

module, they must be identical.
502
Error
PORT ASSIGNED TO
DISCONNECTED LINK
The optical link (mux-eth-tdm port) status is set to

shutdown, while the corresponding E1 or Ethernet ports
are configured as no shutdown.
503
Error
ETH RATE & E1/T1/TRIBUTARY

RATE MISMATCH
The far-end user Ethernet port rate exceeds the available

link bandwidth. Increase the bandwidth by reducing the
number of active E1 ports
Table 6-17. ASMi-54C Sanity Messages

Code
Type
Syntax
Meaning
510
Error
INCORRECT SHDSL LINES IN

PCS
When the configured TC Layer is 64/65-Octets, the wrong

combination of SHDSL lines is used in a PCS
511
Error
SHDSL ADMIN IS NOT

CONNECTED
One of the SHDSL lines is in shutdown state
512
Error
ILLEGAL SHDSL RATE
The selected SHDSL rate is not compatible with the

selected operating mode
513
Error
NOT IDENTICAL SHDSL

DEFINITION
When the Wire parameter of an SHDSL line is configured

to 4W or 8W, all the parameters of the corresponding
SHDSL wire pairs must be identical
514
Error
ILLEGAL PCS DEFINITION FOR

STU-R
When the STU side is configured as the Remote, and the

TC Layer is 64/65 Octets, the only PCS and SHDSL line
combinations allowed are as follows:
PCS 1 can bound to SHDSL lines 1, or 1,2, or 1,2,3,4
PCS 5 can bound to SHDSL lines 5, or 5,6, or 5,6,7,8
515
Error
NOT IDENTICAL LINE PROBE

DEFINITION
When the STU side is configured as the Remote, Line

Probe (line-prob) must be enabled
516
Error
NOT IDENTICAL WIRE NUMBER

DEFINITION
When the TC Layer is 64/65-Octets, the wires parameter

must be set to 2W
517
Error
AT LEAST ONE MARGIN MUST

BE SET
When line probing is enabled, either the current-margin or

worst-margin parameter must be enabled and set
518
Error
ILLEGAL SHDSL DEFINITION

FOR STU-R
When the STU side is configured as the Remote, and the

TC Layer is HDLC, only SHDSL lines 1 and 5 can be set to
4W or 8W.
6-14
Detecting Problems

Code
Type
Syntax
Meaning
519
Error
ILLEGAL NUMBER OF WIRE

COMBINATION
When the TC Layer is HDLC, the wires parameter of the

SHDSL lines must be configured according to Supported
Lines versus Wires Parameter table in ASMi-54C module
section of Appendix B.
520
Error
ILLEGAL E1-i DEFINITION
When the TC Layer is HDLC, the E1-i port is configured to

no shutdown and the corresponding SHDSL line to
shutdown (make sure that only the allowed e1-i ports
are set to no shutdown).
When the TC Layer is 64/65 Octets, one of the e1-i ports
is set to no shutdown
521
Error
STU-MODE MUST BE THE SAME The STU parameter of all the SHDSL lines in a module
IN ALL LINES
must be set to same value
522
Error
TC-LAYER MUST BE THE SAME

IN ALL LINES
The TC Layer parameter of all the SHDSL lines in a module

must be set to same value
524
Error
TS0 MODE DOESN'T FIT TO

LINE TYPE
Contradiction between TS0 mode and line type
525
Error
FE TYPE MUST BE THE SAME IN Far-end-type parameter must be set to the same value for
ALL LINES
all SHDSL ports
526
Error
ILLEGAL PCS BINDING
When working in 4W/8W mode, some PCS ports cannot be

bound to some SHDSL ports. For allowed binding, see
Supported Ports versus Wires Parameter table in
Appendix B.
527
Error
ILLEGAL PARAM VALUE FOR

E1-I PORT
When far-end-type=high-speed-mux-serial-e1, the

corresponding e1-i port must be configured to no
inband-management
528
Error
UNUSED E1-I PORT IS

CONNECTED
Even E1-i ports cannot be connected when working in 4W

mode
529
Warning
FAR-END CHANGED, DEVICE

WILL RESTART
When far-end-type=high-speed-mux-serial-e1 is selected

instead of another far-end-type setting, both the module
and the remote modem will be automatically restarted.
530
Error
DATA RATE EXCEEDS MAXIMAL The data rate configured for ASMi-54C SHDSL port
RATE
exceeds the maximum rate
531
Error
DATA RATE NOT SUPPORTED
For 4W/HDLC operation, rates 17024 to 18432 kbps are

unavailable
532
Error
ILLEGAL REMOTE CH1 TS

NUM
The number of timeslots connected to CH1 (E1) on the

remote modem (remote-ch1-ts-num) exceeds the number
of open timeslots.
Table 6-18. Bridge Sanity Messages

Code
540
Type
Syntax
Meaning
Error
BRIDGE PORT IS SHUTDOWN
Bridge port must be bound to SVI
Detecting Problems
6-15

Code
Type
Syntax
Meaning
541
Error
MORE THAN ONE SVI BOUND

TO BRIDGE PORT
Bridge port should be bound to a single SVI
542
Error
SVI PORT IS NOT CONNECTED
SVI is enabled (no shutdown) but not bound
543
Error
SAME SVI BOUND TO

DIFFERENT BRIDGE PORTS
SVI must be bound to bridge port 1:1
544
Error
BRIDGE PORT NOT BOUND TO

PORT
A bridge port is defined but not bound to any other port.
Table 6-19. LAG Protection Messages

Code
Type
Syntax
Meaning
553
Error
ILLEGAL NUMBER OF LAGs

BETWEEN CL CARDS
Only a single LAG can be configured between two CL cards
554
Error
ILLEGAL NUMBER OF LAG

MEMBERS
At least two members must be define in a LAG
555
Error
LAG MEMBER IS SHUTDOWN
A LAG member should be in no shutdown state
Table 6-20. Flow Sanity Messages

Code
Type
Syntax
Meaning
560
Error
UP TO 240 FLOWS FOR DATA
The maximum number of unidirectional flows for data is

240. This does not include management flows (which
contain an SVI Port bound to BP).
561
Error
UP TO 192 FLOWS FOR

MANAGENENT
The maximum number of management flows is 192.
562
Error
FLOW MUST CONSIST OF TWO

PORTS
Flow must connect 2 ports.
563
Error
SAME INGRESS AND EGRESS

PORTS
Ingress and egress ports must be different.
564
Error
FLOW MUST HAVE A

CLASSIFIER
A classifier profile must be bound to the flow.
565
Error
FLOW BETWEEN TWO SVIS

NOT ALLOWED
A flow cannot connect between 2 SVI ports.
566
Error
CL L. MAC CANT BE MEMBER

IN MNG FLOW
A Logical MAC with a VCG bound to it cannot be a member

in a management flow
567
Error
ILLEGAL FLOW BETWEEN ETH

PORTS
A flow between external or internal Ethernet ports on the

same I/O slot is not allowed.
568
Error
CLASSIFIER PROFILE MUST BE

MATCH ALL
If an ingress port is SVI bound to BP (management flow),

the classifier must be match all.
6-16
Detecting Problems
Code
Type
Syntax
Meaning
569
Error
MNG VLAN MUST BE LESS

THAN 4000
Management flow VLAN ID must be less than 4000.
570
Error
ILLEGAL CLASSIFIER FOR PORT
The selected classification is not supported by this port.

Correction required according to the following:
571
572
573
Error
Error
Error
VLAN TAG ACTION PUSH NOT

ALLOWED
VLAN TAG ACTION POP NOT

ALLOWED
VLAN TAG ACTION MUST BE

POP
Command match vlan inner-vlan is valid only for flows

between GbE and/or LAG ports defined on CL modules
Commands match vlan inner-vlan or match vlan are

obligatory for flows between GbE and/or LAG ports
defined on CL modules, no other classifier can be used
on these ports
I/O port classifier can be only match vlan or match all.
VLAN tag push action is not allowed in the following

cases:
At egress port of flows between GbE and/or LAG ports

defined on CL modules
On ports of I/O modules participating in nonmanagement (data) flows.
VLAN tag pop action is not allowed in the following cases:
At egress ports of flows using classifier match all
At egress port residing on an ASMi-54C/ETH module

when its ingress port classifier is different from match
vlan inner-vlan or match vlan
When both ends of the flow reside on the same I/O

slot
When both ends of the flow reside on GbE or LAG

ports defined on CL modules
Pop action is obligatory in the following cases:
Egress port is SVI bound to a bridge port (management

flow)
Ingress port has inner VLAN as classifier (used only in

Logical macs defined on CL), and egress port is GBE or
LAG
Ingress port has inner VLAN as classifier (match vlan

inner-vlan or match inner-vlan), and egress port is
defined on ASMi-54C/ETH module
If one of these cases is yours, define VLAN pop action.

574
Error
VLAN TAG ACTION MUST BE

PUSH
Push action is obligatory in the following cases:
Ingress port is SVI bound to a bridge port

(management flow).
I/O or CL Logical-mac classifier is match all (push

VLAN must be added at the egress GBE/LAG port).
If one of these cases is yours, define VLAN push action.
Detecting Problems
6-17
Code
Type
Syntax
Meaning
575
Error
CLASSIFIER/PUSHED
VLAN/P-BIT MUST BE THE
SAME
Pay attention to one of the following:
All the flows where egress port is SVI bound to bridge

port (management flow) must have the same VLAN
number in classifier
All the flows where ingress port is SVI bound to bridge

port (management flow) must have the same push
vlan number and p-bit value.
The VLAN number in classifier must be identical to the

push vlan number.
If the mentioned numbers/values are not the same,

correct according to the above.
576
Error
MANAGEMENT FLOW MUST BE

BI-DIRECTIONAL
When a management flow is configured and SVI bound to

a bridge port is its egress port, another flow (with SVI
bound to the bridge port as ingress port) must be
configured and vice versa. In addition, this SVI cannot
participate in another flow.
577
Error
VLAN CAN'T BE REPEATED BTW Pay attention to the following:

CL ETH/LAG PORTS
For non-management (data) flows the classifier profile
VLAN of each GbE/LAG port defined on CL module
must be unique. (Note: This is not relevant in case
when both flow ends reside on GbE/LAG ports defined
on CL module).
For the flows with classifier based on outer&inner

VLAN, the inner VLAN cant be repeated on GbE/LAG
ports defined on CL module
Push SP-VLAN cannot be repeated on GbE/LAG ports

defined on the same CL module
If your case is different, correct according to the above.

578
Error
FLOWS BETWEEN PORTS CANT If ingress port of several flows is the same I/O port, the
BE SPLIT
egress ports of these flows cannot be different.
579
Error
VLAN ID IS UNIQUE PER SLOT
VLAN ID (number) must be unique per slot (except for the

management flows)
580
Error
ONLY SINGLE FLOW IS

ALLOWED FOR MATCH ALL
If the classifier is 'match all', only a single flow is allowed

for the port.
581
Error
CLASSIFIERES CONFLICT ON
SLOT
For any flow terminated on an ASMi-54C/ETH, the

classifier should be either match all or match vlan per
entire module
582
Error
CLASSIFIERES CONFLICT ON
PORT
All flows terminating on a specific port must use the same

classifier criteria.
583
Error
VLAN ID CANT BE REPEATED

PER SYSTEM
An ASMi-54C/ETH port classifier VLAN ID (number) is

unique per system (both at ingress and egress ports) and
cannot be repeated in other ASMi-54C/ETH ports.
6-18
Detecting Problems
Code
Type
Syntax
Meaning
584
Error
NUMBER OF OUTER VLANS ON When the classifier on a GBE or LAG port is match vlan
PORT OUT OF RANGE
inner-vlan, only up to 4 different VLANs (outer VLANs) can
be configured per port. In addition, the inner VLAN IDs
should be different from (outer) VLAN IDs.
585
Error
FLOW CONNECTED TO PORT IN Flow can be connected to ports only in no shutdown

SHUTDOWN STATE
state.
Table 6-21. Protection Messages

Code
Type
Syntax
Meaning
601
Error
WORKING & PROTECTION ARE

ON THE SAME PORT
The same port cannot be defined as both working and

protection port
602
Error
UNFRAMED TYPE CAN'T BE A

MEMBER OF TDM GROUP
Unframed E1/T1 ports of OP-108C/34C, M16E1/M16T1,

ASMi-54C/N modules cannot be selected as members of
TDM group
603
Error
PORT PARAMETERS OF TDM

GROUP ARE ASSYMETRIC
For two ports configured to TDM group protection, the

following parameters must be the same for both ports:
604
Error
PROTECTION PORT IS IN
SHUTDOWN STATE
Admin Status
line-type
line-code
inband-management > timeslot
inband-management > protocol
inband-management > routing-protocol.
One of the ports in tdm protection group is in shutdown

state
Table 6-22. Fault Propagation Sanity Messages

Code
Type
Syntax
Meaning
631
Error
FP PORT IS IN SHUTDOWN
STATE
The port configured for fault propagation is in shutdown

state and the other one is set to no shutdown. Both ports
must be set either to shutdown or to no shutdown.
632
Error
FP PORT CAN'T AFFECT ITSELF
The same port cannot be failed and affected at the same

time.
633
Error
UNFRAMED PORT CAN'T

PARTICIPATE IN FP
Neither failed nor affected E1/T1/E1-i/T1-i/DS-1 port can

be configured as unframed.
634
Error
UP TO 200 FP ENTRIES CAN BE The maximum number of fault propagation entries has
CONFIGURED
been exceeded
635
Error
FP AFFECTED PORT IS USED

MORE THAN ONCE
A port cannot be defined as affected by more than one

failed port
636
Error
FAILED PORT CAN AFFECT UP

TO 10 PORTS
The maximum number of affected ports per one failed

port has been exceeded
Detecting Problems
6-19
637
Error
ASYMMETRIC BI DIR FP
CONFIGURATION
In bidirectional fault propagation, one failed port must

correspond to one affected port, and vice versa
638
Error
PROTECTED PORT CAN'T BE

CONFIGURED IN FP
A port defined as protection in a protection group cannot

be selected by user as failed or affected. If a working port
is selected as failed or affected, the protection port is
internally added to the fault propagation configuration.
639
Error
FP FAILED PORT IS NOT

SUPPORTED
The failed port configured is not supported by Fault

Propagation process
640
Error
FP AFFECTED PORT IS NOT

SUPPORTED
The affected port configured is not supported by Fault

Propagation process
6.2
Handling Events
Reported events can be events, traps and alarms. The difference between them
is as follows:
Alarm. A message that reports a failure. An alarm is a persistent indication of

a fault of an entity, which may be the device itself or any of its components.
Event. Any change of status in a managed object in the network. SNMP

equipment can generate traps for many different kinds of events, not all of
which are important for telemetry. The ability to filter unimportant events is
essential for high-quality SNMP alarm management. An event is something
that may be of interest, such as a fault, a change in status, crossing a
threshold, or an external input to the system.
Trap. An SNMP message issued by an agent that reports an event. The term
trap is used as abbreviation to SNMPv1 or SNMPv3 notification. The SNMP
version is usually omitted, unless it is important to specify it. Traps may be
generated and sent as a result of event or alarm.
Megaplex-4100 includes a configurable mechanism of detecting and reporting

alarms. Once an alarm is triggered, Megaplex-4100 sends an alarm trap to the
relevant network manager, depending on whether the relevant trap has been
masked or activated. In the current Megaplex-4100 version, all traps are
activated.
Alarm Buffer
Megaplex-4100 continuously monitors critical signals and signal processing
functions. In addition, it can also monitor an external alarm line, connected to the
ALARM connector.
If a problem is detected, Megaplex-4100 generates time-stamped alarm
messages. The time stamp is provided by an internal real-time clock.
The alarm messages generated by the Megaplex-4100 are explained below.
Internally, the Megaplex-4100 stores alarms in an alarm buffer. This alarm buffer
can store up to 200 alarm messages, together with their time stamps. The alarm
6-20
Handling Events
history buffer is organized as a FIFO queue; after 200 alarms are written into the
buffer, new alarms overwrite the oldest alarms.
Alarm messages can also be sent automatically as traps to the user-specified
network management stations.
The alarms can be read on-line by the network administrator using the network
management station, a Telnet host, a Web browser or a supervision terminal. The
network administrator can then use the various diagnostic tests to determine the
causes of the alarm messages and to return the system to normal operation.
When Megaplex-4100 is powered down, the alarm messages are erased; old
alarms will not reappear after the Megaplex-4100 is powered up again. When
using the terminal, a Web browser or a Telnet host, the user also can clear
(delete) the alarms stored in this buffer, after reading them.
Alarm Relays
In addition to the alarm reporting facility, Megaplex-4100 has two alarm relays
with floating change-over contacts: one relay for indicating the presence of major
alarms and the other for minor alarms. Each relay changes state whenever the
first alarm is detected, and returns to its normal state when all the alarms of the
corresponding severity disappear.
The relay contacts can be used to report internal system alarms to outside
indicators (e.g., lights, buzzers, bells), located on a bay alarm or remote
monitoring panel.
See also ACM Module section in Appendix B for description of alarm relays
available on this module.
Working with the Alarm and Event Logs

This section explains how to display and clear the alarm and event logs.
Instructions on viewing alarms and events can be found below. Lists of possible
alarms and events can be found under Alarm List and Event List sections,
respectively.
To display the alarm/event log:

1. Navigate to configure>reporting# context.
2. Type show followed by the display option parameter listed in the following
table.
Display Option
Meaning
Example no
active-alarms
Shows the active alarms table. Counters of active alarms in

the output, in order of severity, appear at top of the
screen
active-alarms-details
Same as above but with time stamp added to active alarms
Handling Events
6-21
Display Option
Meaning
Example no
alarm-information
Detailed information about alarm type. For example, if you

need to know what is LOF alarm on SDH/SONET in
Examples 1 or 2, see Example 3.
alarm-log
Log of active and cleared alarms (without events). The

default view of the alarm log (i.e., history of alarms) shows
one line per raised alarm and one for cleared alarm
alarm-list
[<source ID> [severity
{critical|major|minor}]]
List of all Megaplex-4100 alarms for a specific source IDs

and severity value or of all the alarms available in the
system
event-information
Detailed information about event type (similar to alarminformation)
event-list
List of all Megaplex-4100 events for a specific source IDs

or of all the events available in the system
log
Log of active alarms, cleared alarms and events
To scroll up and down in the list, use the arrow keys.
Example 1: Displaying Active Alarms

This command shows the table of active alarms. On top of the screen appear counters of active alarms in the
output, by severity: critical, major and minor.
mp4100>config>reporting# show active-alarms

Total :
Critical : 0
Major : 3
1
2
3
SDH-SONET
Ethernet
SDH-SONET
cl-a/2
MNG cl-b/1
cl-b/2
LOF
LOS
LOS
Minor
Maj
Maj
Maj
: 0
unmasked
unmasked
unmasked
Example 2. Displaying Active Alarms Details

This command shows the table of active alarms with their time stamp. On top of the screen appear counters
of active alarms in the output, by severity: critical, major and minor.
mp4100>config>reporting# show active-alarms-details

Total :
Critical : 0
Major : 3
1
SDH-SONET
cl-a/2
LOF
Major
Unmasked
Loss of signal (LOS)
15-05-2015
03:38:53
6-22
: 0
Loss of frame (LOF)
15-05-2015
02:10:52
Minor
Ethernet
MNG cl-b/1
Handling Events
LOS
Major
Unmasked
15-05-2015
03:38:48
SDH-SONET
cl-b/2
LOS
Major
Unmasked
Example 3: Displaying Information of LOF alarm on

SDH/SONET port
This command displays detailed information about a specific alarm. The output
shows configuration of the source type, followed by a table of sources whose
configuration divert from the source types configuration.
For example, use this command if you need to know what is LOF alarm on
SDH/SONET in Examples 1 or 2. In this example the table of sources is empty
since all the sources are configured the same as their type.
mp4100>config>reporting# show alarm-information sdh-sonet lof
Source
: SDH-SONET
Name
: LOF
Description
: Loss of frame (LOF)
Alarm ID
: 100003
Severity
: Major
LED
: Yes
LED Relay
: Yes
Logged
: Yes
SNMP Trap
: Yes
SNMP trap OID : 1.3.6.1.4.1.164.3.1.6.2.0.22
Source
Source ID
Severity LED
Logged SNMP Trap
-----------------------------------------------------------------------------
Example 4. Alarm Log

This command displays the log of active and cleared alarms (without events). The
default view of the alarm log (i.e. history alarms) shows one line per raised alarm
and one for cleared alarm. The alarm severity is shown on the left. Its possible
values are critical, major, minor, or cleared. The field on the left shows the reason
of alarm removal: resolved, user-initiated, alarm suppression, not applicable.
mp4100>config>reporting# show alarm-log
Last Acknowledge On : 64-149-1203 00:206:27.
1
Alarm indication signal (AIS)
17-05-2015
Major
20:19:36
2
SDH-SONET
AIS-LINE
cl-a/2
17-05-2015
Cleared
20:19:38
SDH-SONET
cl-a/2
AIS-LINE
Resolved
Handling Events
6-23
17-05-2015
Major
20:19:40
SDH-SONET
AIS-LINE
cl-a/2
17-05-2015
Cleared
20:19:46
SDH-SONET
AIS-LINE
cl-a/2
Resolved
Example 5. Alarm List

This command displays the list of all Megaplex-4100 alarms for a specific source
IDs and severity value. The table also shows whether the alarm appears in the log
and whether these parameters are set to default or modified by the user. This
specific example displays the beginning of the list of all the alarms available in the
system.
mp4100>config>reporting# show alarm-list

Source
Name
ID
Severity
Logged
System
SYSTEM_TEMPERATURE_ORA
20002
Major
Yes
(Default)
---------------------------------------------------------------------------System
hardware_failure_fe
20012
Yes
(Default)
----------------------------------------------------------------------------System
configuration_mismatch_fe
20013
Yes
(Default)
----------------------------------------------------------------------------System
INTERFACE_MISMATCH_FE
20014
Major
Yes
(Default)
----------------------------------------------------------------------------System
NO_INTERFACE_FE
20015
Yes
(Default)
----------------------------------------------------------------------------Power Supply
POWER_DELIVERY_FAILURE
20201
Major
Yes
(Default)
----------------------------------------------------------------------------Alarm Input
Alarm_Relay_Input
20401
Major
Yes
(Default)
----------------------------------------------------------------------------Card
HARDWARE_FAILURE
40001
Major
Yes
(Default)
----------------------------------------------------------------------------Card
CARD_MISMATCH
40002
Major
Yes
(Default)
6-24
Handling Events
----------------------------------------------------------------------------To scroll up and down in the list, use the arrow keys.
To clear any log:
At the config>reporting# context, enter clear-log.

The log is cleared.
Alarm, Event and Trap Lists

Alarm List
Table 6-23 lists the alarm messages generated by the Megaplex-4100. The alarms
are listed in the ascending order of the following:
Source type: system, card, port/entity
Alarm name (inside each source)
For each alarm, Table 6-23 also specifies the alarm description, the
corresponding trap and the alarm ID (unique numbers, which identify the alarms).
Alarm names are not case-sensitive.
For an alphabetical list of traps, see Table 6-25.
Table 6-23. Alarms List

Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
alarm-input
alarm_relay_input
Alarm input
alarmInput
20401
card
hardware_failure
Hardware failure
cardHwFailure
40001
card
card_mismatch
Card not supported or misconfigured
cardMismatch
40002
card
card_provision
failure
Provisioning failure
cardProvisionFailure
40003
card
unsupported
software
Module software not supported
cardUnsupportedSw
40004
card
unsupported
hardware
Module hardware not supported
cardUnsupportedHw
40005
card
card_improper
removal
Improper card removal
cardImproperRemoval
40006
card_temperature
ora
Card temperature <current card

temperature> out of range
cardTemperatureOra
40007
card
card_no_response
Loss of communication with card
cardNoResponse
40008
domain-clock
system_clock_
holdover
Domain system clock state changed

to holdover
clockDomainSystemCl
ockHoldover
30301
domainclock-source
source_clock_failure
Source clock failure
sourceClockFailure
30501
card
Handling Events
6-25
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
e1t1
management_link
down
Management link with far end is

down
e1t1ManagementLink
Down
110102
e1t1
excessive_bpv
Excessive bipolar violation (BPV)
e1t1ExcessiveBpv
110103
e1t1
excessive_error
ratio
Excessive error ratio
e1t1ExcessiveErrorRat
io
110104
e1t1
ais
e1t1Ais
110105
e1t1
lof
Loss of frame (LOF)
e1t1Lof
110106
e1t1
rai
Remote alarm indication (RAI)
e1t1Rai
110107
e1t1
lomf
Loss of multiframe (LOMF)
e1t1Lomf
110108
e1t1
lomf_fe
Loss of multiframe at far end

(LOMF-FE)
e1t1LomfFe
110109
e1t1
los_fe
e1t1LosFe
110116
e1t1
ais_fe
e1t1AisFe
110117
e1t1
los
e1t1Los
110110
e1t1
ds1_ring_clock_
failure
Ring clock failure
e1t1Ds1RingClockFail
ure
110111
e1t1
ds1_ring_direction_
mismatch
Ring working and protection ports

mismatch
e1t1Ds1RingDirection
Mismatch
110112
e1t1
fault_propagation
Fault propagation
faultPropagation
110113
eth
sfp_no_response
Loss of communication with SFP
sfpNoResponse
50001
eth
sfp_mismatch
SFP mismatch
sfpMismatch
50002
eth
los
ethLos
50003
eth
sfp_removed
SFP not installed
sfpRemoved
50004
eth
fault_propagation
Fault propagation
faultPropagation
50007
gfp
lof
Loss of frame (LOF)
gfpLof
230001
gfp
csf
Client signal fail (CSF)
gfpCsf
230002
gfp
rx_trail_failure
Rx trail failure
gfpRxTrailFailure
230003
gfp
fault_propagation
Fault propagation
faultPropagation
230004
hdlc
rx_trail_failure
Rx trail failure
hdlcRxTrailFailure
240001
mux-eth-tdm
lof
Loss of frame (LOF)
muxEthTdmLof
60001
mux-eth-tdm
los
muxEthTdmLos
60002
mux-eth-tdm
fault_propagation
Fault propagation
faultPropagation
60003
mux-eth-tdm
remote_connection_
failure
Control protocol to far-end device

failed
muxEthTdmRemoteCo
nnectionFailure
60005
6-26
Handling Events
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
mux-eth-tdm
loop_detection
Loop detected
muxEthTdmLoopDete
ction
60006
mux-eth-tdm
ais
muxEthTdmAis
60007
mux-eth-tdm
sfp_mismatch
SFP mismatch
sfpMismatch
60008
mux-eth-tdm
sfp_removed
SFP not installed
sfpRemoved
60009
mux-eth-tdm
lof_fe
Far-End Loss of frame
muxEthTdmLofFe
60012
mux-eth-tdm
los_fe
Far-End Loss of signal
muxEthTdmLosFe
60013
mux-eth-tdm
Ais_fe
Far-End Alarm indication signal
muxEthTdmAisFe
60014
path
ais-path
pathAis
100201
path
lomf-path
pathLomf
100202
path
uneq-path
Unequipped payload
pathUneq
100203
path
tim-path
Path trace ID mismatch (TIM)
pathTim
100204
path
plm-path
Payload label mismatch (PLM)
pathPlm
100205
path
lop-path
Loss of pointer (LOP)
pathLop
100206
path
sd-path
BER above signal degradation

threshold
pathSd
100207
path
eed-path
BER above excessive error threshold
pathEed
100208
path
rfi-path
Remote failure indication (RFI)
pathRfi
100209
ppp
lcp_failure
Link control protocol (LCP) failure
pppLcpFailure
280001
ppp
bcp_failure
Bridge control protocol (BCP) failure
pppBcpFailure
280002
pw
configuration
mismatch
Configuration mismatch
pwConfigMismatch
310001
pw
pw_oam_failure
PW OAM disconnected
pwOamFailure
310002
pw
fe_rdi
Remote defect indication (RDI)
pwRdi
310003
pw
rx_failure
Ethernet frames not received by PW
pwRxFailure
310004
pw
rx_failure_fe
Ethernet frames not received by PW

at far end
pwFeRxFailure
310008
pw
fault_propagation
Fault propagation
faultPropagation
310006
pw
jitter_buffer
overrun
Jitter buffer overrun
pwJitterBufferOverrun
310007
sdh-sonet
sfp_no_response
Loss of communication with SFP
sfpNoResponse
100001
sdh-sonet
sfp_mismatch
SFP mismatch
sfpMismatch
100002
sdh-sonet
lof
Loss of frame (LOF)
sdhSonetLof
100003
sdh-sonet
rfi-line
sdhSonetRfi
100004
Handling Events
6-27
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
sdh-sonet
los
sdhSonetLos
100005
sdh-sonet
sfp_removed
SFP not installed
sfpRemoved
100006
sdh-sonet
ais-line
sdhSonetAis
100009
sdh-sonet
tim
Section trace ID mismatch (TIM)
sdhSonetTim
100010
sdh-sonet
sd-line

threshold
sdhSonetSd
100011
sdh-sonet
eed-line
sdhSonetEed
100012
sdh-sonet
fault_propagation
Fault propagation
faultPropagation
100013
sdh-sonet
management_link_d
own

down
sdhSonetManagemen
tLinkDown
100014
sdh-sonet
aps_protection_byte
_failure
APS protection switching byte failure
sdhSonetApsProtectio
nByteFailure
100016
sdh-sonet
aps_channel
mismatch
APS channel mismatch
sdhSonetApsChannel
Mismatch
100017
sdh-sonet
aps_mode
mismatch
APS mode mismatch
sdhSonetApsModeMis
match
100018
sdh-sonet
aps_fe_protection
line failure
APS far-end protection line failure
sdhSonetApsFeProtec
tionLineFailure
100019
serial
hardware_failure
Hardware failure
serialHardwareFailure
150001
serial
lof
Loss of frame (LOF)
serialLof
150002
serial
rai
serialRai
150003
serial
rts_off
No RTS
serialNoRts
150004
serial
fe_rts_off
No RTS at far-end
serialFeNoRts
150008
serial
rs232_rate
mismatch
Rate mismatch
serialRs232RateMism
atch
150006
serial-bundle
lof
Loss of frame (LOF)
serialBundleLof
150101
serial-bundle
rai
serialBundleRai
150102
shdsl
Configuration
mismatch
Configuration mismatch
shdslConfigurationMis
match
70203
shdsl
management_link
down

down
shdslManagementLink
Down
70204
shdsl
loop_attenuation
tca
Loop attenuation exceeded

threshold
shdslLoopAttenuation
Ora
70214
shdsl
snr_margin_tca
Signal-to-noise ratio (SNR) margin

below threshold
shdslSnrMarginOra
70216
shdsl
losw
Loss of sync word (LOSW)
shdslLosw
70218
6-28
Handling Events
Source Type
Alarm Name
Alarm Description
Trap Name
Alarm ID
system
device_temperature
_ora
Device temperature out of range
systemDeviceTemper
atureOra
20002
vc-vt
ais-vcvt
vcVtAis
100101
vc-vt
lomf-vcvt
vcVtLomf
100102
vc-vt
uneq-vcvt
Unequipped payload
vcVtUneq
100103
vc-vt
tim-vcvt
Path trace ID mismatch (TIM)
vcVtTim
100104
vc-vt
plm-vcvt
Payload label mismatch (PLM)
vcVtPlm
100105
vc-vt
lop-vcvt
Loss of pointer (LOP)
vcVtLop
100106
vc-vt
sd-vcvt

threshold
vcVtSd
100107
vc-vt
eed-vcvt
vcVtEed
100108
vc-vt
rfi-vcvt
vcVtRfi
100109
vcg
minimum_members
_tca
Number of members below the

minimum
vcgMinimumMembers
130001
vcg
fault_propagation
Fault propagation
faultPropagation
130002
voice
hardware_failure
Hardware failure
voiceHardwareFailure
90001
Event List
Table 6-23 describes the event messages generated by the Megaplex-4100 and
explains their interpretation. The events are listed in the ascending order of the
following:
Source type: system, card, port/entity
Alarm name (inside each source)
For each alarm, Table 6-23 also specifies the alarm description, the
corresponding trap and the event ID (unique number, which identifies the event
type). Event names are not case-sensitive.
For alphabetical list of traps, see Table 6-25.
Table 6-24. Event List

Source
Type
Event Name
Event Description
Trap Name
Event ID
bri
loopback
Loopback started
briLoopback
1080001
bri
loopback_off
Loopback ended
briLoopbackOff
1080002
card
card_reset
Card reset
cardReset
1040001
card
card_plugged_in
Card plugged in
cardPluggedIn
1040004
card
card_plugged_out
Card removed from slot
cardPluggedOut
1040005
Handling Events
6-29
Source
Type
Event Name
Event Description
Trap Name
Event ID
domainclock
system_source
clock_changed
Domain system source clock changed
csmSourceStatus
Change
1030301
e1t1
frame_slip
Frame slip
e1t1FrameSlip
1110101
e1t1
bpv
Bipolar violation (BPV)
e1t1Bpv
1110102
e1t1
crc_error
CRC error
e1t1CrcError
1110103
path
es_path_tca
Errored seconds (ES) threshold

crossing alert
pathEsTca
1100201
path
ses_path_tca
Severely errored seconds (SES)

threshold crossing alert
pathSesTca
1100202
path
cv_path_tca
Coding violation (CV) threshold

crossing alert
pathCvTca
1100203
path
uas_path_tca
Unavailable Seconds (UAS) threshold

crossing alert
pathUasTca
1100204
path
es_path_tca_fe

crossing alert at far end
pathFeEsTca
1100205
path
ses_path_tca_fe

threshold crossing alert at far end
pathFeSesTca
1100206
path
cv_path_tca_fe

pathFeCvTca
1100207
path
uas_path_tca_fe

pathFeUasTca
1100208
sdh-sonet
es_section_tca

crossing alert
sdhSonetEsSecTca
1100003
sdh-sonet
ses_section_tca

sdhSonetSesSecTca
1100004
sdh-sonet
sefs_section_tca
Severely Errored Framing Seconds

(SEFS) threshold crossing alert
sdhSonetSefsSecTc
a
1100005
sdh-sonet
cv_section_tca

crossing alert
sdhSonetCvSecTca
1100006
sdh-sonet
es_line_tca

crossing alert
sdhSonetEsLineTca
1100007
sdh-sonet
ses_line_tca

sdhSonetSesLineTc
a
1100008
sdh-sonet
cv_line_tca

crossing alert
sdhSonetCvLineTca
1100009
sdh-sonet
uas_line_tca

crossing alert
sdhSonetUasLineTc
a
1100010
sdh-sonet
es_line_tca_fe

sdhSonetFeEsLineT
ca
1100011
6-30
Handling Events
Source
Type
Event Name
Event Description
Trap Name
Event ID
sdh-sonet
ses_line_tca_fe

sdhSonetFeSesLine
Tca
1100012
sdh-sonet
cv_line_tca_fe

sdhSonetFeCvLineT
ca
1100013
sdh-sonet
uas_line_tca_fe

sdhSonetFeUasLine
Tca
1100014
sdh-sonet
port_switchover
Port switchover
sdhSonetPortSwitc
hover
1100015
serial
buffer_slip
Buffer overflow or underflow
serialBufferSlip
1150001
shdsl
loopback
Loopback started
shdslLoopback
1070204
shdsl
loopback_off
Loopback ended
shdslLoopbackOff
1070205
vc-vt
es_vcvt_tca

crossing alert
vcVtEsTca
1100101
vc-vt
ses_vcvt_tca

vcVtSesTca
1100102
vc-vt
cv_vcvt_tca

crossing alert
vcVtCvTca
1100103
vc-vt
uas_vcvt_tca

crossing alert
vcVtUasTca
1100104
vc-vt
es_vcvt_tca_fe

vcVtFeEsTca
1100105
vc-vt
ses_vcvt_tca_fe

vcVtFeSesTca
1100106
vc-vt
cv_vcvt_tca_fe

vcVtFeCvTca
1100107
vc-vt
uas_vcvt_tca_fe

vcVtFeUasTca
1100108
Trap List
The traps are listed in the table below.
Table 6-25. Trap List

Associated to
Source Type
Trap
Description
Notification OID
Alarm
alarm-input
alarmInput
alarm_input
1.3.6.1.4.1.164.6.5.0.1
Alarm
card
cardHwFailure
card_hardware_failure
1.3.6.1.4.1.164.3.3.2.1.0.1
Alarm
card
cardMismatch
card_mismatch
1.3.6.1.4.1.164.3.3.2.1.0.2
Handling Events
6-31
Associated to
Source Type
Trap
Description
Notification OID
Alarm
card
cardProvisionFailure
card_provision_failure
1.3.6.1.4.1.164.3.3.2.1.0.3
Alarm
card
cardUnsupportedSw
card_unsupported_software
1.3.6.1.4.1.164.3.3.2.1.0.4
Alarm
card
cardUnsupportedHw
card_unsupported_hardware
1.3.6.1.4.1.164.3.3.2.1.0.5
Alarm
card
cardImproperRemoval
card_improper_removal
1.3.6.1.4.1.164.3.3.2.1.0.6
Alarm
card
cardTemperatureOra
card_temperature_ora
1.3.6.1.4.1.164.3.3.2.1.0.7
Alarm
card
cardNoResponse
card_no_response
1.3.6.1.4.1.164.3.3.2.1.0.8
Alarm
card
cardInitFailure
card_initialization_failure
1.3.6.1.4.1.164.3.3.2.1.0.9
Alarm
card
cardConfigurationMismatch
card_configuration_mismatch
1.3.6.1.4.1.164.3.3.2.1.0.14
Alarm
e1t1
e1t1ManagementLinkDown
management_link_down
1.3.6.1.4.1.164.3.1.6.4.0.22
Alarm
e1t1
e1t1ExcessiveBpv
excessive_bpv
1.3.6.1.4.1.164.3.1.6.4.0.23
Alarm
e1t1
e1t1ExcessiveErrorRatio
excessive_error_ratio
1.3.6.1.4.1.164.3.1.6.4.0.24
Alarm
e1t1
e1t1Ais
ais
1.3.6.1.4.1.164.3.1.6.4.0.25
Alarm
e1t1
e1t1Lof
lof
1.3.6.1.4.1.164.3.1.6.4.0.26
Alarm
e1t1
e1t1Rai
rai
1.3.6.1.4.1.164.3.1.6.4.0.27
Alarm
e1t1
e1t1Lomf
lomf
1.3.6.1.4.1.164.3.1.6.4.0.28
Alarm
e1t1
e1t1LomfFe
lomf_fe
1.3.6.1.4.1.164.3.1.6.4.0.29
Alarm
e1t1
e1t1Los
los
1.3.6.1.4.1.164.3.1.6.4.0.30
Alarm
e1t1
e1t1Ds1RingClockFailure
ds1_ring_clock_failure
1.3.6.1.4.1.164.3.1.6.4.0.31
Alarm
e1t1
e1t1Ds1RingDirectionMismatc
h
ds1_ring_direction_mismatch
1.3.6.1.4.1.164.3.1.6.4.0.32
Alarm
e1t1
eth
gfp
hdlc
mux-eth-tdm
pw
sdh-sonet
serial
serial-bundle
vcg
faultPropagation
fault_propagation
1.3.6.1.4.1.164.6.5.0.2
Alarm
e1t1
e1t1FeExcessiveBpv
excessive_bpv_fe
1.3.6.1.4.1.164.3.1.6.4.0.45
Alarm
eth
feFaultPropagation
fault_propagation_fe
1.3.6.1.4.1.164.6.5.0.3
Alarm
e1t1
e1t1FeExcessiveErrorRatio
excessive_error_ratio_fe
1.3.6.1.4.1.164.3.1.6.4.0.46
Alarm
e1t1
e1t1FeAis
ais_fe
1.3.6.1.4.1.164.3.1.6.4.0.47
Alarm
e1t1
e1t1FeLos
los_fe
1.3.6.1.4.1.164.3.1.6.4.0.48
Alarm
eth
ethLos
los
1.3.6.1.4.1.164.3.1.6.1.0.1
6-32
Handling Events
Associated to
Source Type
Trap
Description
Notification OID
Alarm
eth
ethFeLos
los_fe
1.3.6.1.4.1.164.3.1.6.1.0.16
Alarm
fan
fanFailure
fan_failure
1.3.6.1.4.1.164.6.1.0.64
Alarm
gfp
gfpLof
lof
1.3.6.1.4.1.164.6.2.55.0.1
Alarm
gfp
gfpCsf
csf
1.3.6.1.4.1.164.6.2.55.0.2
Alarm
gfp
gfpRxTrailFailure
rx_trail_failure
1.3.6.1.4.1.164.6.2.55.0.3
Alarm
hdlc
hdlcRxTrailFailure
rx_trail_failure
1.3.6.1.4.1.164.3.1.6.5.0.1
Alarm
mux-eth-tdm
muxEthTdmLof
lof
1.3.6.1.4.1.164.3.1.6.1.0.2
Alarm
mux-eth-tdm
muxEthTdmLos
los
1.3.6.1.4.1.164.3.1.6.1.0.3
Alarm
mux-eth-tdm
muxEthTdmRemoteConnection
Failure
remote_connection_failure
1.3.6.1.4.1.164.3.1.6.1.0.7
Alarm
mux-eth-tdm
muxEthTdmLoopDetection
loop_detection
1.3.6.1.4.1.164.3.1.6.1.0.8
Alarm
mux-eth-tdm
muxEthTdmAis
ais
1.3.6.1.4.1.164.3.1.6.1.0.9
Alarm
mux-eth-tdm
muxEthTdmFeLof
lof_fe
1.3.6.1.4.1.164.3.1.6.1.0.13
Alarm
mux-eth-tdm
muxEthTdmFeLos
los_fe
1.3.6.1.4.1.164.3.1.6.1.0.14
Alarm
mux-eth-tdm
muxEthTdmFeAis
ais_fe
1.3.6.1.4.1.164.3.1.6.1.0.15
Alarm
path
pathAis
ais-path
1.3.6.1.4.1.164.3.1.6.2.0.50
Alarm
path
pathLomf
lomf-path
1.3.6.1.4.1.164.3.1.6.2.0.51
Alarm
path
pathUneq
uneq-path
1.3.6.1.4.1.164.3.1.6.2.0.52
Alarm
path
pathTim
tim-path
1.3.6.1.4.1.164.3.1.6.2.0.53
Alarm
path
pathPlm
plm-path
1.3.6.1.4.1.164.3.1.6.2.0.54
Alarm
path
pathLop
lop-path
1.3.6.1.4.1.164.3.1.6.2.0.55
Alarm
path
pathSd
sd-path
1.3.6.1.4.1.164.3.1.6.2.0.56
Alarm
path
pathEed
eed-path
1.3.6.1.4.1.164.3.1.6.2.0.57
Alarm
path
pathRfi
rfi-path
1.3.6.1.4.1.164.3.1.6.2.0.58
Alarm
power-supply
powerDeliveryFailure
power_delivery_failure
1.3.6.1.4.1.164.6.1.0.73
Alarm
power-supply
powerInOra
power_in_ora
1.3.6.1.4.1.164.6.1.0.74
Alarm
power-supply
powerInLow
power_in_low
1.3.6.1.4.1.164.6.1.0.75
Alarm
ppp
pppLcpFailure
lcp_failure
1.3.6.1.4.1.164.4.2.0.5
Alarm
ppp
pppBcpFailure
bcp_failure
1.3.6.1.4.1.164.4.2.0.6
Alarm
ppp
pppLoopDetection
loop_detection
1.3.6.1.4.1.164.4.2.0.7
Alarm
pw
pwConfigMismatch
configuration_mismatch
1.3.6.1.4.1.164.14.0.1
Alarm
pw
pwOamFailure
pw_oam_failure
1.3.6.1.4.1.164.14.0.2
Alarm
pw
pwRdi
rdi
1.3.6.1.4.1.164.14.0.3
Handling Events
6-33
Associated to
Source Type
Trap
Description
Notification OID
Alarm
pw
pwRxFailure
rx_failure
1.3.6.1.4.1.164.14.0.4
Alarm
pw
pwJitterBufferOverrun
jitter_buffer_overrun
1.3.6.1.4.1.164.14.0.5
Alarm
pw
pwFeRxFailure
rx_failure_fe
1.3.6.1.4.1.164.14.0.6
Alarm
pw
pwFeRdi
rdi_fe
1.3.6.1.4.1.164.14.0.7
Alarm
sdh-sonet
sdhSonetLof
lof
1.3.6.1.4.1.164.3.1.6.2.0.22
Alarm
sdh-sonet
sdhSonetRfi
rfi-line
1.3.6.1.4.1.164.3.1.6.2.0.23
Alarm
sdh-sonet
sdhSonetLos
los
1.3.6.1.4.1.164.3.1.6.2.0.24
Alarm
sdh-sonet
sdhSonetAis
ais-line
1.3.6.1.4.1.164.3.1.6.2.0.25
Alarm
sdh-sonet
sdhSonetTim
tim
1.3.6.1.4.1.164.3.1.6.2.0.26
Alarm
sdh-sonet
sdhSonetSd
sd-line
1.3.6.1.4.1.164.3.1.6.2.0.27
Alarm
sdh-sonet
sdhSonetEed
eed-line
1.3.6.1.4.1.164.3.1.6.2.0.28
Alarm
sdh-sonet
sdhSonetManagementLinkDo
wn
1.3.6.1.4.1.164.3.1.6.2.0.29
Alarm
serial
serialHardwareFailure
hardware_failure
1.3.6.1.4.1.164.3.1.6.18.0.1
Alarm
serial
serialLof
lof
1.3.6.1.4.1.164.3.1.6.18.0.2
Alarm
serial
serialRai
rai
1.3.6.1.4.1.164.3.1.6.18.0.3
Alarm
serial
serialNoRts
no_rts
1.3.6.1.4.1.164.3.1.6.18.0.4
Alarm
serial
serialFeNoRts
no_rts_fe
1.3.6.1.4.1.164.3.1.6.18.0.5
Alarm
serial
serialRs232RateMismatch
rs232_rate_mismatch
1.3.6.1.4.1.164.3.1.6.18.0.6
Alarm
serial-bundle
serialBundleLof
lof
1.3.6.1.4.1.164.3.1.6.18.0.7
Alarm
serial-bundle
serialBundleRai
rai
1.3.6.1.4.1.164.3.1.6.18.0.8
Alarm
eth
sdh-sonet
sfpNoResponse
sfp_no_response
1.3.6.1.4.1.164.40.3.4.0.1
Alarm
eth
sdh-sonet
mux-eth-tdm
sfpMismatch
sfp_mismatch
1.3.6.1.4.1.164.40.3.4.0.2
Alarm
eth
sdh-sonet
mux-eth-tdm
sfpRemoved
sfp_removed
1.3.6.1.4.1.164.40.3.4.0.3
Alarm
shdsl
shdslConfigurationMismatch
configuration_mismatch
1.3.6.1.4.1.164.3.1.6.12.0.4
Alarm
shdsl
shdslManagementLinkDown
1.3.6.1.4.1.164.3.1.6.12.0.5
Alarm
shdsl
shdslLoopAttenuationOra
loop_attenuation_ora
1.3.6.1.4.1.164.3.1.6.12.0.9
Alarm
shdsl
shdslSnrMarginOra
snr_margin_ora
1.3.6.1.4.1.164.3.1.6.12.0.11
Alarm
shdsl
shdslLosw
losw
1.3.6.1.4.1.164.3.1.6.12.0.13
Alarm
shdsl
shdslExcessiveCrcError
excessive_crc_error
1.3.6.1.4.1.164.3.1.6.12.0.15
6-34
Handling Events
Associated to
Source Type
Trap
Description
Notification OID
Alarm
shdsl
shdslFeConfigurationMismatch
1.3.6.1.4.1.164.3.1.6.12.0.22
Alarm
shdsl
shdslLinkDown
link_down
1.3.6.1.4.1.164.3.1.6.12.0.23
Alarm
shdsl
shdslFeLoopAttenuationOra
loop_attenuation_ora_fe
1.3.6.1.4.1.164.3.1.6.12.0.24
Alarm
shdsl
shdslFeSnrMarginOra
snr_margin_ora_fe
1.3.6.1.4.1.164.3.1.6.12.0.25
Alarm
shdsl
shdslFeLosw
losw_fe
1.3.6.1.4.1.164.3.1.6.12.0.26
Alarm
smart-sfp
smartSfpMismatch
smart_sfp_mismatch
1.3.6.1.4.1.164.40.2.0.1
Alarm
station-clock
stationClockAis
ais
1.3.6.1.4.1.164.6.2.52.0.5
Alarm
station-clock
stationClockLof
lof
1.3.6.1.4.1.164.6.2.52.0.6
Alarm
station-clock
stationClockLos
los
1.3.6.1.4.1.164.6.2.52.0.7
Alarm
system
systemDeviceTemperatureOra
device_temperature_ora
1.3.6.1.4.1.164.6.1.0.41
Alarm
system
systemSwPackCorrupted
sw_pack_corrupted
1.3.6.1.4.1.164.6.1.0.61
Alarm
system
systemFeHardwareFailure
hardware_failure_fe
1.3.6.1.4.1.164.6.1.0.66
Alarm
system
systemFeConfigurationMismat
ch
1.3.6.1.4.1.164.6.1.0.67
Alarm
system
systemFeInterfaceMismatch
interface_mismatch_fe
1.3.6.1.4.1.164.6.1.0.68
Alarm
system
systemFeNoInterface
no_interface_fe
1.3.6.1.4.1.164.6.1.0.69
Alarm
vc-vt
vcVtAis
ais-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.67
Alarm
vc-vt
vcVtLomf
lomf-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.68
Alarm
vc-vt
vcVtUneq
uneq-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.69
Alarm
vc-vt
vcVtTim
tim-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.70
Alarm
vc-vt
vcVtPlm
plm-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.71
Alarm
vc-vt
vcVtLop
lop-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.72
Alarm
vc-vt
vcVtSd
sd-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.73
Alarm
vc-vt
vcVtEed
eed-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.74
Alarm
vc-vt
vcVtRfi
rfi-vcvt
1.3.6.1.4.1.164.3.1.6.2.0.75
Alarm
vcg
vcgMinimumMembers
minimum_members
1.3.6.1.4.1.164.3.1.6.2.0.21
Alarm
voice
voiceHardwareFailure
hardware_failure
1.3.6.1.4.1.164.3.1.6.13.0.1
Event
bri
briLoopback
loopback
1.3.6.1.4.1.164.3.2.3.0.4
Event
bri
briLoopbackOff
loopback_off
1.3.6.1.4.1.164.3.2.3.0.5
Event
bri
briFeLoopback
loopback_fe
1.3.6.1.4.1.164.3.2.3.0.6
Event
bri
briFeLoopbackOff
loopback_off_fe
1.3.6.1.4.1.164.3.2.3.0.7
Event
card
cardReset
card_reset
1.3.6.1.4.1.164.3.3.2.1.0.10
Event
card
cardPluggedIn
card_plugged_in
1.3.6.1.4.1.164.3.3.2.1.0.11
Handling Events
6-35
Associated to
Source Type
Trap
Description
Notification OID
Event
card
cardPluggedOut
card_plugged_out
1.3.6.1.4.1.164.3.3.2.1.0.12
Event
e1t1
e1t1FrameSlip
frame_slip
1.3.6.1.4.1.164.3.1.6.4.0.33
Event
e1t1
e1t1Bpv
bpv
1.3.6.1.4.1.164.3.1.6.4.0.34
Event
e1t1
e1t1CrcError
crc_error
1.3.6.1.4.1.164.3.1.6.4.0.35
Event
e1t1
e1t1Loopback
loopback
1.3.6.1.4.1.164.3.1.6.4.0.36
Event
e1t1
e1t1LoopbackOff
loopback_off
1.3.6.1.4.1.164.3.1.6.4.0.37
Event
e1t1
e1t1EsLineTca
es_line_tca
1.3.6.1.4.1.164.3.1.6.4.0.38
Event
e1t1
e1t1CvPathTca
cv_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.39
Event
e1t1
e1t1EsPathTca
es_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.40
Event
e1t1
e1t1SesPathTca
ses_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.41
Event
e1t1
e1t1SefsPathTca
sefs_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.42
Event
e1t1
e1t1CssPathTca
css_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.43
Event
e1t1
e1t1UasPathTca
uas_path_tca
1.3.6.1.4.1.164.3.1.6.4.0.44
Event
path
pathEsTca
es_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.59
Event
path
pathSesTca
ses_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.60
Event
path
pathCvTca
cv_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.61
Event
path
pathUasTca
uas_path_tca
1.3.6.1.4.1.164.3.1.6.2.0.62
Event
path
pathFeEsTca
es_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.63
Event
path
pathFeSesTca
ses_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.64
Event
path
pathFeCvTca
cv_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.65
Event
path
pathFeUasTca
uas_path_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.66
Event
sdh-sonet
sdhSonetEsSecTca
es_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.30
Event
sdh-sonet
sdhSonetSesSecTca
ses_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.31
Event
sdh-sonet
sdhSonetSefsSecTca
sefs_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.32
Event
sdh-sonet
sdhSonetCvSecTca
cv_section_tca
1.3.6.1.4.1.164.3.1.6.2.0.33
Event
sdh-sonet
sdhSonetEsLineTca
es_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.34
Event
sdh-sonet
sdhSonetSesLineTca
ses_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.35
Event
sdh-sonet
sdhSonetCvLineTca
cv_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.36
Event
sdh-sonet
sdhSonetUasLineTca
uas_line_tca
1.3.6.1.4.1.164.3.1.6.2.0.37
Event
sdh-sonet
sdhSonetFeEsLineTca
es_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.38
Event
sdh-sonet
sdhSonetFeSesLineTca
ses_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.39
Event
sdh-sonet
sdhSonetFeCvLineTca
cv_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.40
Event
sdh-sonet
sdhSonetFeUasLineTca
uas_line_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.41
6-36
Handling Events
Associated to
Source Type
Trap
Description
Notification OID
Event
serial
serialBufferSlip
buffer_slip
1.3.6.1.4.1.164.3.1.6.18.0.9
Event
shdsl
shdslLoopback
loopback
1.3.6.1.4.1.164.3.1.6.12.0.17
Event
shdsl
shdslLoopbackOff
loopback_off
1.3.6.1.4.1.164.3.1.6.12.0.18
Event
system
systemConfigurationMigration
configuration_migration
1.3.6.1.4.1.164.6.1.0.46
Event
system
systemDeviceStartup
device_startup
1.3.6.1.4.1.164.6.1.0.55
Event
system
systemSuccessfulLogin
successful_login
1.3.6.1.4.1.164.6.1.0.70
Event
system
systemFailedLogin
failed_login
1.3.6.1.4.1.164.6.1.0.71
Event
system
systemLogout
logout
1.3.6.1.4.1.164.6.1.0.72
Event
vc-vt
vcVtEsTca
es_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.76
Event
vc-vt
vcVtSesTca
ses_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.77
Event
vc-vt
vcVtCvTca
cv_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.78
Event
vc-vt
vcVtUasTca
uas_vcvt_tca
1.3.6.1.4.1.164.3.1.6.2.0.79
Event
vc-vt
vcVtFeEsTca
es_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.80
Event
vc-vt
vcVtFeSesTca
ses_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.81
Event
vc-vt
vcVtFeCvTca
cv_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.82
Event
vc-vt
vcVtFeUasTca
uas_vcvt_tca_fe
1.3.6.1.4.1.164.3.1.6.2.0.83
6.3
Troubleshooting
Preliminary Checks
If a problem occurs, perform the following preliminary checks:
If the problem is detected when Megaplex-4100 is put into operation (for the
first time), perform the following checks:
Check for proper chassis and module installation, and correct cable
connections, in accordance with the system installation plan.
Check that system and module configuration parameters are in

accordance with the specific application requirements, as provided by the
system administrator.
If the Megaplex-4100 nodal clock is to be locked to the clock recovered

from one of the ports of a module installed in the chassis, make sure a
suitable additional clock source is configured and provides a good clock
signal.
When two CL modules are installed, check the ON LINE indicators: the ON
LINE indicator of the active module must light steadily, and that of the
standby must flash. If not, check the configuration.
Troubleshooting
6-37
Check the displayed alarm messages and refer to Alarm, Event and Trap Lists
section for their meaning and corrective actions.
Troubleshooting Procedure
If the problem cannot be corrected by performing the actions listed above, refer
to Table 6-26. Identify the best-fitting trouble symptoms and perform the actions
listed under Corrective Measures in the order given, until the problem is
corrected.
Table 6-26. Troubleshooting Chart

No.
Trouble
Symptoms
Probable Cause
Megaplex-4100
1. No power
does not turn on
Corrective Measures
Check that power is available at the power outlets or power

distribution panel serving the Megaplex-4100.
Check that both ends of all the Megaplex-4100 power cables
are properly connected.
The local
Megaplex-4100
cannot be
configured
through its
CONTROL DCE
port
2. Defective PS
module
Replace the suspected PS module
3. Defective
Megaplex-4100
Replace Megaplex-4100
1. Connection made
to the inactive CL
module
Check that the connection is made to the CONTROL DCE

connector of the CL module whose ON LINE indicator lights
steadily
2. Configuration
problem
Restore the default parameters as explained in Chapter 2,

and then perform the preliminary supervision terminal
configuration instructions in accordance with Chapter 3
3. External problem
Check the equipment serving as a supervision terminal, and

the connecting cable.
If the supervision terminal is connected through a data link
to the Megaplex-4100, check the equipment providing the
data link for proper operation
6-38
The local
Megaplex-4100
cannot be
4. Software not yet

loaded into CL
module, or
corrupted
Download the appropriate Megaplex-4100 software to the CL

modules in accordance with Chapter 6
5. Defective CL
module
Replace the corresponding CL module
1. Configuration
problems
Check the CONTROL ETH port configuration.
Troubleshooting
Check that the ON LINE indicator of the CL module lights

steadily

No.
Trouble
Symptoms
Probable Cause
Corrective Measures
managed
through its
CONTROL ETH
port
2. Problem in the
connection
between the
CONTROL ETH port
and the LAN
Check that the LINK indicator of the CONTROL ETH port is lit.
Check the external equipment (for example, the default

gateway and other routers/switches) that process the traffic
coming from the local Megaplex-4100 CONTROL ETH port
4. Defective CL
module
Replace the corresponding CL module
5. Defective
Megaplex-4100
Replace Megaplex-4100
The LOS indicator 1. Cable connection

problems
of an SDH/SONET
port is on
The status
indicator of a
local I/O module
port lights in red
1. Cable connection
problems
Check for proper connections of the cables to the

SDH/SONET connector of each CL.2 port.
Repeat the check at the users equipment connected to the
port.
Activate the remote loopback at the local SDH/SONET module
port.
If the user equipment connected to the SDH/SONET

connector does not receive its own signal, check its
operation, and replace if necessary
If the problem is not in the equipment connected to the

SDH/SONET port, replace the CL.2 module
Check for proper connections of the cables to the module

connector.
Repeat the check at the user equipment connected to the
port.
2. External problem
Activate the local physical loopback on the corresponding

port. If the indicator of the corresponding local port lights in
green while the loop is connected, the problem is external.
Check cable connections, and the transmission equipment
providing the link to the remote unit.
3. Defective I/O
module
Replace the I/O module
The LOS indicator 1. Cable connection

of the CLOCK
problems
port lights in red
2. Defective CL
module
If not, check for proper connection of the cable between the

LAN and the CONTROL ETH port. Also check that at least one
node is active on the LAN, and that the hub or Ethernet
switch to which the
Megaplex-4100 CONTROL ETH port is connected is powered
3. External problem
2. External problem
Check for proper connections of the cables to the connector.

Repeat the check at the equipment providing the station
clock signal to the Megaplex-4100.
Replace the CL module
Troubleshooting
6-39
6.4
Performing Diagnostics Tests
When a problem occurs, Megaplex-4100 offers a set of diagnostic functions that

efficiently locate the problem (in the Megaplex-4100 chassis, in one of
Megaplex-4100 modules, in a connecting cable, or in external equipment) and
rapidly restore full service.
The diagnostic functions include a ping utility on the system level and loopbacks
at the various ports, which identify whether a malfunction is caused by the
Megaplex-4100 or by an external system component (for example, an equipment
unit, cable, or transmission path connected to the Megaplex-4100).
Performing a Ping Test

You can perform a ping test to check the Megaplex-4100 IP connectivity.
To perform a ping test:

1. At any level, start pinging the desired host specifying its IP address and,
optionally, the number of packets to be sent, and payload size:
ping <1.1.1.1255.255.255.255> [number-of-packets <110000>] [payloadsize <321450 bytes>]
2. To stop the ping test, enter Ctrl-C.
Example:
mp4100# ping 172.17.170.81 number-of-packets 2 payload-size 64
Pinging 172.17.170.81 with 64 bytes of data:
Reply from 172.17.170.81 bytes=64 ttl=64 time=10ms seq=1
Reply from 172.17.170.81 bytes=64 ttl=64 time=0ms seq=2
mp4100#
--- Ping Statistics --Packets: Sent = 2, Received = 2, Lost = 0 (0% loss)
Running Diagnostic Loopbacks

The available diagnostic loopbacks depend on the installed modules. For specific
instructions, refer to the corresponding section in Chapter 5: for example, Testing
E1 Ports under E1 Ports, etc.
Table 6-27 identifies the general types of test and loopback functions supported
by Megaplex-4100, and the paths of the signals when each test or loopback is
activated. Additional types of loopbacks may be supported by some I/O modules.
6-40
Table 6-27. Megaplex-4100 Test and Loopback Functions
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
Diagnostic
Function
I/O Port
Local loopback on I/O

voice, serial, serialbundle, mux-ethtdm, shdsl ports
Remote loopback on
I/O voice, serial,
serial-bundle, muxeth-tdm, shdsl ports
Local loopback on
E1 or T1 port
(M8E1/M8T1,
M16E1/M16T1,
ASMi-54C/N, all OP
modules)
I/O Port
Interface
Port
Interface
Port
Interface
DS1
Cross-Connect
Matrix
.
.
.
..
.
.
.
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
DS1
Cross-Connect
Matrix
DS1
Cross-Connect
Matrix
DS1
Cross-Connect
Matrix
"1 "
Remote loopback on
E1 or T1 port
(M8E1/M8T1,
M16E1/M16T1,
ASMi-54C/N, all OP
modules)
Port
Interface
DS1
Cross-Connect
Matrix
6-41
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
Diagnostic
Function
I/O Port
Local loopback on
E1/E1-i/T1/T1-i
timeslots
(M8E1/M8T1,
M16E1/M16T1,
ASMi-54C/N,
Megaplex OP
modules)
Remote loopback on
E1/E1-i/T1/T1-i
timeslots
(M8E1/M8T1,
M16E1/M16T1,
ASMi-54C/N,
Megaplex OP
modules)
DS1
Cross-Connect
Matrix
.
.
.
..
.
.
.
E1/T1
Mapper
VC/VT
Matrix
I/O Interface
1
2
..
..
.
DS1
Cross-Connect
Matrix
I/O Interface
1
2
..
..
.
DS1
Cross-Connect
Matrix
SDH/SONET
Framer
Remote loopback on
SDH/SONET link
Local loopbacks on
AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5 ports
Remote loopbacks
on AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5 ports
6-42
SDH/
SONET
Framer
VC/VT
Matrix
VC/VT
Matrix
Megaplex-4100
SDH/SONET Interface
CL
E1-i/T1-i
Framers
1
2
Diagnostic
Function
I/O Port
.
.
.
..
.
.
.
DS1
Cross-Connect
Matrix
E1/T1
Mapper
VC/VT
Matrix
SDH/
SONET
Framer
E1-i/T1-i Framers
1
Local loopback on
E1-i/T1-i port
..
..
..
E1-i/T1-i Framers
1
Remote loopback on
E1-i/T1-i port
..
..
..
E1-i/T1-i Framers
1
Local loopback on
timeslots of
E1-i/T1-i port
..
..
.
.
E1-i/T1-i Framers
1
Remote loopback on
timeslots of
E1-i/T1-i port
..
..
..
The Megaplex-4100 loopbacks are activated from the following context and are
described in the corresponding sections in Chapter 4.
6-43

Loopbacks

Activated from
Local and remote loopbacks on I/O voice, serial,

serial-bundle, mux-eth-tdm, shdsl ports
configure>port>voice
configure>port>serial
configure>port>serial-bundle
configure>port>mux-eth-tdm
configure>port>shdsl
Local and remote loopbacks on

E1 or T1 port
configure>port>e1
configure>port>t1
Local and remote loopbacks on E1/E1-i/T1/T1-i

timeslots
configure>port>e1
configure>port>t1
configure>port>e1-i
configure>port>t1-i
Remote loopback on SDH/SONET link
configure>port>sdh-sonet
Local and remote loopbacks on AUG ports
configure>port>sdh-sonet>aug
Local and remote loopbacks on OC-3 ports
configure>port>sdh-sonet>oc3
Local and remote loopbacks on TUG-3 ports
configure>port>sdh-sonet>aug>tug3
Local and remote loopbacks on STS-1 ports
configure>port>sdh-sonet>oc3>sts1
Local and remote loopbacks on VC-12 ports
configure>port>sdh-sonet>aug>tug3>vc12
Local and remote loopbacks on VT-1.5 ports
configure>port>sdh-sonet>oc3>sts1>vt1-5
Local and remote loopbacks on E1-i/T1-i port
configure>port>e1-i
configure>port>t1-i
Local and remote loopbacks on timeslots of

E1-i/T1-i port
configure>port>e1-i
configure>port>t1-i
6-44
6.5
Technical Support
Technical support for this product can be obtained from the local partner from
whom it was purchased.
RADcare Global Professional Services offers a wide variety of service, support and
training options, including expert consulting and troubleshooting assistance,
online tools, regular training programs, and various equipment coverage options.
For further information, please contact the RAD partner nearest you or one of
RAD's offices worldwide.
RAD Data Communications would like your help in improving its product
documentation. Please send us an e-mail with your comments.
Thank you for your assistance!
Technical Support
6-45
6-46
Technical Support
Chapter 7
Software Upgrade
This chapter explains how to upgrade Megaplex-4100.
Software upgrades may be required to fix product limitations, to enable new
features, or to make the unit compatible with other devices that are already
running the new software version. New software releases are distributed as *.bin
files, to be downloaded to Megaplex-4100.
Megaplex-4100 can store four software versions, each in one of the four
partitions of its flash memory, which also contains a boot program. The software
is stored in compressed format.
Note
If your system has two CL modules, you must upgrade both modules to the same
software version to ensure seamless redundancy after the upgrade.
7.1
Impact
Megaplex-4100 is upgraded once the unit has been reset.
7.2
Software Upgrade Options
Application software can be downloaded to Megaplex-4100 via CLI (using TFTP) or

via the boot menu (using TFTP or XMODEM). The upgrade consists of two stages.
First the application software is downloaded from a PC to Megaplex-4100 flash
disk. This can be done in the following ways:
via CLI (using TFTP) using file>copy command
via the boot commands (download, using TFTP or XMODEM).
Then the software pack is downloaded from the flash disk to the CL and I/O
modules. This can be done in the following ways:
via the CLI admin>software>install command (both for CL and I/O modules)
via the boot set-activecommand (CL modules only).
7.3
Prerequisites
This section details the software file names and outlines system requirements
needed for the upgrade procedure.
Prerequisites
7-1
Chapter 7 Software Upgrade
Software Files
New version releases are distributed as software files named *.bin, for example
sw-pack.bin. The files can be obtained from the local RAD business partner from
whom the device was purchased.
The software upgrade utility includes four partitions called sw-pack-1, sw-pack-2,
sw-pack-3, sw-pack-4 for downloading and storing the software versions. To
activate the specified software version, one of these partitions is set to active.
Each software pack consists of a set of image files for each (CL or I/O) module
with appropriate headers. The software pack can be ordered either for the entire
chassis, or for specific modules only.
System Requirements
Before starting the upgrade, verify that you have the following:
Note
For upgrade via TFTP:
Megaplex-4100 unit with a router interface bound to the management

interface used, and a static route defined to a PC with the TFTP server
application (such as 3Cdaemon or PumpKIN), and a valid IP address.
Software file stored on the PC.
Megaplex-4100 communicates with TFTP servers via Ethernet ports only.
For upgrade via XMODEM:
Operational Megaplex-4100 unit
Connection to a PC with HyperTerminal installed
Software file stored on the PC.
7.4
Upgrading Software using the CLI
The recommended software method of downloading software to the flash disk is

to use the file copy command of the CLI environment. This allows processing the
upgrade remotely and avoiding the booting. Only CL modules need to be reset
after this procedure.
Using TFTP
Network administrators use the TFTP protocol to distribute new software
releases to all the managed Megaplex-4100 units in the network from a central
location. The central application is a PC on the network with a TFTP server
application such as the PumpKIN server installed on it.
7-2

Application file is
transferred to
Megaplex-4100
Ethernet
Megaplex-4100
PC with an Active
TFTP Server and
Application File
Figure 7-1. Downloading a Software Application File to Megaplex-4100 via TFTP

Use the following procedure to download the software release to Megaplex-4100
using the copy command.
1. Verify that the required image file is stored on the PC together with the TFTP
server application.
2. Verify that Megaplex-4100 has a router interface assigned to it, as explained
in Adding and Configuring Router Interfaces in Chapter 5.
3. Verify that a static route is configured to the PC, as explained in Configuring
Static Routes and Default Gateway in Chapter 5.
4. Ping the PC to verify the connection.
5. Activate the TFTP server application, as explained in Activating the TFTP
Server.
6. Download the image file to the unit, as explained in Downloading the New
Software Release File to Megaplex-4100 Flash Disk.
Note
Configuration values shown in this chapter are examples only.
Verifying the IP Settings

Megaplex-4100 must have a router interface with IP parameters configured
according to your network requirements. In addition, a static route must be
established to the TFTP server to establish a communication session with the
TFTP server.
For example:
configure router 1 static 0.0.0.0/0 address 11.11.11.1
To verify the IP parameters:
At the router(1)# prompt, enter info detail.

The router interface configuration information is displayed.
7-3
mp4100>config>router(1)# info detail

interface 9999
address 11.11.11.29/30
name "Put your string here"
bind svi 9999
no vlan
no shutdown
exit
arp-timeout 1200
Pinging the PC
Check the integrity of the communication link between Megaplex-4100 and the
PC by pinging the Megaplex-4100 from the PC.
Activating the TFTP Server

Once the TFTP server is activated on the PC, it waits for any TFTP file transfer
request originating from the product, and carries out the received request
automatically.
To run the TFTP server:
Activate a TFTP server application, such as 3Cdaemon (available from

www.3com.com) or PumpKIN (available from http://kin.klever.net/pumpkin/).
Downloading the New Software Release File to Megaplex-4100 Flash

Disk
Use this procedure to download the new software release to the Megaplex-4100
flash disk.
To download an application file to the Megaplex-4100 flash disk via CLI:
At the file# prompt, enter the copy command, as follows:

copy tftp://<tftp-ip-address>/<image-file-name> sw-pack-<index 1..4>
where tftp-ip-address is the IP address of the PC in which the TFTP server is
installed.
For example, to download the sw-pack.bin file to sw-pack-4 partition from

the PC at 10.10.10.10:
mp4100>file# copy tftp://10.10.10.10/sw-pack.bin sw-pack-4

You are prompted to confirm the request:
The application file begins downloading.
To check the flash memory contents:
7-4
At the file# prompt, enter the dir command, for example:
mp4100>file# dir
Codes
C - Configuration S - Software
LO Log
Name
Type Size(Bytes) Creation Date Status
sw-pack-1
S
6306207
21-12-2010
valid
13:44:58
sw-pack-2
S
6305847
21-2-2011
valid
7:48:0
sw-pack-3
S
6278526
21-2-2011
valid
9:57:47
sw-pack-4
S
6289552
6-1-2011
valid
10:23:13
startup-config
C
95872
13-3-2011
valid
14:7:35
user-default-config C
95872
13-3-2011
valid
14:6:51
factory-default-conf C
796
1-1-1970
Read Only
0:0:9
running-config
C
0
1-1-1970
Read Only
0:0:9
Free Bytes
: 63442944
To monitor the copy progress:
At the file# prompt, enter the show copy command, for example:
mp4100# show file copy

Network to Device, Transferring Data
Src: tftp://172.17.174.56/mp4cl2_03_00b06.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Transferred : 665600 Bytes in: 16 seconds (41600 Bytes/Second)
Finally, the application file is downloaded and saved in partition 4 of the
flash disk.
tftp://172.17.174.56/mp4cl2_03_00b06.bin copied to sw-pack-4
successfully
Once the file is downloaded, the following message is displayed:
mp4100>file# sw-pack.bin copied to sw-pack-4 successfully
To display the partition contents:
At the file# prompt, enter the show sw-pack command, for example:
7-5
mp4100>file# show sw-pack

Name
Version
Creation Time
Status
Actual
--------------------------------------------------------------sw-pack-1 3.00B6
21-12-2010
13:44:58 Ready
Yes
sw-pack-2 3.00B5
21-2-2011
7:48:0
Ready
-sw-pack-3 3.00B4
21-2-2011
9:57:47
Ready
-sw-pack-4 3.00B6
14-3-2011
9:32:56
Ready
-sw-pack-1 Size (Bytes)
Type
Name
: 6306207
Size
(Bytes)
--------------------------------------------------------------main
main.bin
3.00B6
0.1
6305967
sw-pack-2 Size (Bytes)
Type
Name
Version
H/W Ver
: 6305847
Size
(Bytes)
--------------------------------------------------------------main
main.bin
3.00B5
0.1
6305607
Type
Name
Version
H/W Ver
: 6278526
Size
(Bytes)
--------------------------------------------------------------main
main.bin
3.00B4
0.1
6278286
Type
Name
Version
H/W Ver
: 12493650
Version
H/W Ver
Size
(Bytes)
--------------------------------------------------------------main
main.bin
3.00B6
0.1
6306207
asmi54cn asmi54cn.bin
3.4567
1.2
1625132
asmi54c
asmi54c.bin
4.5678
2.3
1898111
m8e1
m8e1.bin
7.6543
9.8
844767
op34c
op34c.bin
7.5642
8.9
683210
op108c
op108c.bin
2.9637
8.5
1053603
In the above example, partitions 1, 2 and 3 contain software release for
CL.2 modules. Partition 4 contains software release for CL.2 and five
types of I/O modules. The active partition is 1.
Downloading the New Software Release File from the Flash Disk to
CL.2 and I/O Modules
Once a file is saved on the Megaplex-4100 flash disk, it must be downloaded to
the CL.2 or I/O modules to replace the current software. The sw-pack file includes
the new software version for all the CL.2 and I/O modules, according to your
purchase order.
You can choose to download the new SW release file to all the CL.2 and I/O
modules installed in the chassis simultaneously. In this case, if the chassis
includes several modules of the same kind, the new software release will be
7-6
installed in all of them. If you do not want this to happen, you can issue a
command to install the software in one specific slot.
To download the new software release file from the flash disk to all the CL.2 and
I/O modules installed in the chassis:
At the admin>software # prompt, enter the install command. For example:
mp4100# admin
mp4100>admin# software
mp4100>admin>software# install sw-pack-3
The previous software pack is deleted from the active partition:
deleting
deleting
deleting
deleting
deleting
deleting
file
file
file
file
file
file
/tffs0/Sw-Pack/Active/main.bin
/tffs0/Sw-Pack/Active/mainHdr.bin
/tffs0/Sw-Pack/Active/op-108c.bin
/tffs0/Sw-Pack/Active/op-108cHdr.bin
/tffs0/Sw-Pack/Active/m8e1.bin
/tffs0/Sw-Pack/Active/m8e1Hdr.bin
Wait until install command completed.....

successfull install to cl-a
successfull install to cl-b
installation completed
The software pack stored in sw-pack-3 partition is transferred to the
active partition and sent to all the relevant modules that are found in the
chassis. The I/O modules perform reboot automatically and are now ready
for operation with new software version.
7. To activate the new software release for the CL modules, you must perform
reboot. Disconnect the power, wait a few seconds and then reconnect the
power.
Megaplex-4100 is upgraded and starts with the new software version.
mp4100# admin software install sw-pack-1
deleting file /tffs0:2/Sw-Pack/Active/main.bin
deleting file /tffs0:2/Sw-Pack/Active/mainHdr.bin
To download the new software release file from the flash disk to a specified CL.2
or I/O module:
At the admin>software # prompt, enter the install command and add the
specified slot number. For example:
mp4100# admin software install sw-pack-1 slot 10

deleting file /tffs0/Sw-Pack/Active/op-108c.bin
deleting file /tffs0/Sw-Pack/Active/op-108cHdr.bin
Wait until install command completed.....
successful install to op-108c
installation completed
The OP-108C module installed in slot 10 is upgraded and starts with the
new software version.
7-7
7.5
Upgrading Megaplex-4100 Software via the

Boot Menu
Software downloading may also be performed using the Boot menu. The Boot
menu can be reached while Megaplex-4100 performs initialization, for example,
after power-up.
You may need to start the loading from the Boot menu when it is not possible to
activate TFTP using the CLI because, for example, the Megaplex-4100 software
has not yet been downloaded or is corrupted.
Caution The Boot menu procedures are recommended for use only by authorized
personnel, because this menu provides many additional options that are intended
for use only by technical support personnel.
You can upgrade via the Boot menu using either the TFTP or the XMODEM
protocol. Two software downloading options are available from the Boot
Manager:
Note
Downloading using the XMODEM protocol. This is usually performed by

downloading from a PC directly connected to the CONTROL port of the unit.
Downloading using the TFTP. This is usually performed by downloading from a

remote location that provides an IP communication path to an Ethernet port
of Megaplex-4100.
All the screens shown in this section are for illustration purposes only. Your
Megaplex-4100 may display different software versions and port profiles.
The preparations needed for using the TFTP/FTP protocol via the Boot menu are
similar to the preparations needed to download software using the TFTP protocol
via the CLI. The main difference is that you need to define the IP communication
parameters associated with the corresponding Ethernet port (IP addresses and
the associated subnet mask and a default gateway IP address).
Starting Boot Manager

Prior to initiating the VXWORKS Boot Manager functionality, connect the ASCII
terminal or PC with terminal emulation to the CONTROL DCE (serial) port of
Megaplex-4100.
To start VXWORKS Boot Manager:

1. Verify that the *.bin file is stored on the PC with the terminal application.
2. Configure the communication parameters of the selected PC serial port for
asynchronous communication for 115.2 kbps, no parity, one start bit, eight
data bits and one stop bit. Turn all types of flow control off.
3. Turn off Megaplex-4100.
7-8
Upgrading Megaplex-4100 Software via the Boot Menu
4. Activate the terminal application.

5. Turn on Megaplex-4100.
Information about the System Boot, Boot version, and information about
CPU, OS-version, BSP version and Boot Manager version is displayed.
The following message appears:
Use '?'/help to view available commands.
Press any key to stop auto-boot....
6. Press any key to stop the auto-boot and get a boot prompt.
The boot prompt is displayed:
[boot]:
7. Press <?> to display the Help list.
The Help list is displayed.
Commands:
?/help
- print this list
p
- print boot parameters
c [param]
- change boot parameter(s)
v
- print boot logo with
versions information
run
- load active sw pack and
execute
delete <FileName>
- delete a file
dir
- show list of files
show <index>
- show sw pack info
download <index> [,<FileName|x>] - download a sw pack to
specific index (x - by Xmodem)
set-active <index>
- Set a sw pack index to be
the active application
control-x/reset
- reboot/reset
Figure 7-2. VXWORKS Boot Manager Help List

8. Press <P> to display all boot parameters.
The boot parameters list appears. A typical boot parameters list is shown
in Figure 7-3. The parameters are described in Table 7-1.
[boot]: p
file name
(fn) : vxworks
device IP
(ip) : 10.10.10.88
device mask
(dm) : 255.255.255.0
server IP
(sip) : 10.10.10.10
gateway IP
(g) : 10.10.10.10
user
(u) : vxworks
ftp password
(pw) : *******
device name
(dn) : MP4100
quick autoboot
(q) : yes
protocol
(p) : ftp
baud rate
(b) : 9600
Figure 7-3. Typical Boot Parameters Screen
7-9
Table 7-1. Boot Parameters

Parameter
Command
Description
file name
fn
The binary software pack file (*.bin) name
device ip
ip
The IP address of Megaplex-4100
device mask
dm
The IP subnet mask of Megaplex-4100
server IP
sip
The TFTP server IP address
gateway ip
The TFTP server default gateway IP-address if the

server is located on a different LAN.
Note: Be sure to select an IP address within the subnet

of the assigned Megaplex-4100 IP address.
Note: If no default gateway is needed, for example,
because the TFTP server is attached to the same LAN
as Megaplex-4100 being upgraded, enter 0.0.0.0.
user
The user name, as registered at the FTP server.
Note: Displayed only when using FTP Protocol.

ftp password
vx
The user password, as registered at the FTP server.
Note: Displayed only when using FTP Protocol.
Note
device name
dn
MP4100
quick autoboot
Enabling or disabling the quick autoboot feature
protocol
The file transfer protocol in use: TFTP or FTP
baud rate
Transmission bit rate (in kbps): 9600, 19200, 115200
The CLI commands are case insensitive.

9. Press <C> to change the boot parameters and type valid values in each field.
Type 'c' to modify all parameters
Type 'c [parameter]' to modify the specific parameter (for example, to

change the filename to sw-pack.bin, type: c fn vxworks sw-pack.bin).
'.' = clear field;
'-' = go to previous field;
^D = quit
file name
(fn) : vxworks sw-pack.bin
device IP
(ip) : 10.10.10.88
device mask
(dm) : 255.255.255.0
server IP
(sip) : 10.10.10.10
gateway IP
(g) : 10.10.10.10
user
(u) : vxworks
ftp password
(pw) (blank = use rsh): *******
device name
(dn) : MP4100
quick autoboot [y/n] : y
protocol [tftp/ftp] : ftp
baud rate [9600/19200/115200]: 9600
10. To complete the upgrade and log on again, follow the onscreen instructions.
7-10
Using the TFTP/FTP Protocol

Use the following procedure to download software release to Megaplex-4100 via
TFTP.
To download software file(s) from the Boot menu to Megaplex-4100 via

TFTP/FTP:
1. Verify that the *.bin file is stored on the PC with the TFTP server application.
2. Activate the TFTP server application/FTP server.
Note
When working with FTP server, the user name and password in Boot parameters
must be the same as defined in FTP server.
3. Turn on Megaplex-4100 and enter the Boot menu. Set TFTP or FTP protocol.
4. From the Boot menu, type download <index 1..4> [<FileName>] command to
start downloading the software pack file from the PC to the corresponding
partition of the Megaplex-4100 flash disk.
Note
[<FileName>] is used if you did not specify the filename in the Boot menu
earlier.
For example: Download the file to sw-pack-2
[boot]: download 2
The file is being copied to sw-pack-2 partition:
File transferring - 7580KB
226 Transfer finished successfully.
Please wait, old file is being erased and written with new one.
File writing to flash: - 7580KB
File downloaded successfully to :2
[boot]:
5. Using dir command, check which partition is currently active. In our example it
is sw-pack-1.
[boot]: dir
SIZE
FILE-NAME
796
factory-default-config
6296759
sw-pack-1
6305902
sw-pack-2
6278526
sw-pack-3
6289552
sw-pack-4
Active SW-pack is: 2
Free Bytes
: 69701632
6. Use set-active command to activate the partition to which the file has been
downloaded (in our example: sw-pack-2).
7-11
[boot]: set-active 2
set-active may take few minutes...
deleting file /tffs0/Sw-Pack/Active/main.bin
deleting file /tffs0/Sw-Pack/Active/mainHdr.bin
SW set active 2 completed successfully.
The new software release is now stored in partition 2 and will be
activated after reset.
7. Perform one of the following:
Type @ or run.
The following message is displayed and the new software release is
activated:
[boot]: run
External file header passed validation!
Loading/un-compressing main.bin...
Starting the APPLICATION off address 0x10000...
Press <Ctrl + X> to perform a cold (hard) reboot with turning power off
and then on.
Type reset to perform a warm (soft) reboot without turning off power.
The following message is displayed:
Are you sure (y/n)?

Press <Y>.
When the downloading process is successfully completed, you will see a
sequence of messages similar to the following:
7-12

Instantiating /ram as rawFs, device = 0x20001
Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x20001
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0
Root dir entries 0, sysId (null) , serial number 7d0000
Label:"
" ...
Disk with 64 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 54 clusters, 1 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 2
Root dir entries 112, sysId VXDOS12 , serial number 7d0000
Adding 71349 symbols for standalone.
8. Press <Enter> to start working with the new SW release downloaded.
Note
The new parameters take effect only after the reset is completed.
Using the XMODEM Protocol

XMODEM is used to download and upgrade from a PC connected to the CONTROL
DCE port of the Megaplex-4100 unit.
Application file is
transferred to
Megaplex-4100
RS-232
Megaplex-4100
PC with a Terminal
Emulation and
Application File
Figure 7-4. Downloading a Software Application File to Megaplex-4100 via

XMODEM
To download software release via XMODEM:

1. From the Boot menu, type download <index 1..4> [<FileName>] x command
and press <Enter> to start downloading the software pack file from the PC to
the corresponding partition of the Megaplex-4100 flash disk.
7-13
Note
[<FileName>] is used if you did not specify the filename in the Boot menu
earlier.
For example: Download the file to sw-pack-2.
[boot]: download 2, x
The following message appears:
The terminal will become disabled !!!
Please send the file in XMODEM
2. In HyperTerminals Menu bar, click on the
icon or choose the Transfer
menu of HyperTerminal, and then select Send File.
The Send File window appears.
3. In the Protocol field, select Xmodem.
4. In the Filename field, enter the prescribed Megaplex-4100 software file name
and its path, or click <Browse> to navigate to it.
The Send button becomes available.
5. When ready, click <Send>.
The Xmodem File Transfer window appears and the download starts. A
progress bar and counters let you monitor the progress as illustrated
below.
Figure 7-5. XMODEM File Send Status Window

6. Perform <dir> to verify status of the new image.
7. Use set-active command to activate the partition to which the file has been
downloaded (in our example: sw-pack-2).
7-14
[boot]: set-active 2
set-active may take few minutes...
deleting file /tffs0/Sw-Pack/Active/main.bin
deleting file /tffs0/Sw-Pack/Active/mainHdr.bin
SW set active 2 completed successfully.
The new software release is now stored in partition 2 and will be
activated after reset.
8. When the downloading process is successfully completed, press <@> to exit
the Boot Manager.
9. When the Megaplex-4100 initialization ends, the unit loads the new software.
Note
The command times out and the send file request is considered failed if you do
not initiate sending the file within approximately 3 minutes.
7.6
Verifying the Upgrade Results
To verify that the upgrade was successful, log on to Megaplex-4100 via

HyperTerminal to view the Inventory summary.
To verify the upgrade result:
Type: show cards-summary in the config context and verify the active
software version in the SW Ver column.
mp4100>config# show cards-summary

Slot Family
Type
HW Ver
SW Ver
---------------------------------------------------------------------------PS-A Power Supply ps
Undefined Undefined
PS-B Not Installed-Undefined Undefined
CL-A CL
CL2 622GbE
0.0/ 0.0 3.00B06/ 0
CL-B CL
CL2 622GbE
0.0/ 0.0 3.00B06/ 0
1
Optimux
OP-34C
1
1.50B1
2
DSL
ASMI54C
2
2.73
3
Optimux
OP-108C
4
2.51
4
DSL
m8sl
1
1.121
5
E1-T1
M8 E1
1
1.121
6
E1-T1
M8 E1
1
1.121
7
Voice
VC8 FXS
10
13.00
8
High Speed
HS12N
2
6.00
9
DSL
ASMI54C E1+Eth 1
3.00B0
10
E1-T1
M16 E1
1
1.50B1
Note
If downloading failed, repeat the entire procedure.
7-15
7-16
Appendix A
Connection Data
A.1
Connector Data
The CONTROL DCE connector is a 9-pin D-type female connector with RS-232
asynchronous DCE interface, intended for direct connection to a supervision
terminal. The connector is wired in accordance with Table A-1.
Table A-1. CONTROL DCE Connector Wiring

Pin
Function
Direction
Data Carrier Detect (DCD)
From Megaplex-4100
Receive Data (RD)
From Megaplex-4100
Transmit Data (TD)
To Megaplex-4100
Data Terminal Ready (DTR)
To Megaplex-4100
Signal Ground (SIG)
Common reference and DC power supply ground
Data Set Ready (DSR)
From Megaplex-4100
Request to Send (RTS)
To Megaplex-4100
Clear to Send (CTS)
From Megaplex-4100
Ring Indicator (RI)
To Megaplex-4100
Connection Data
The connections to the CONTROL DCE connector are made as follows:
Connection to supervision terminal with 9-pin connector: by means of a

straight cable (a cable wired point-to-point)
Connection to supervision terminal with 25-pin connector: by means of a

cable wired in accordance with Figure A-1
Connection to modem with 25-pin connector (for communication with

remote supervision terminal): by means of a cable wired in accordance with
Figure A-1
Connection to modem with 9-pin connector (for communication with remote

supervision terminal): by means of a crossed cable wired in accordance with
Figure A-2.
A-1
Appendix A Connection Data
9 Pin
Connector
To
CONTROL DCE
Connector
25 Pin
Connector
TD
RD
RTS
CTS
DSR
DCD
RI
22
DTR
20
GND
CL Side
To Terminal
Terminal Side
Figure A-1. 25-Pin Terminal Cable Wiring - Connection to CONTROL DCE

Connector
9-Pin
Connector
To
CONTROL DCE
Connector
TD
RD
RTS
CTS
DSR
DCD
RI
DTR
GND
CL Side
9-Pin
Connector
To Modem
Modem Side
Figure A-2. 9-Pin Crossed Cable Wiring - Connection to CONTROL DCE Connector
A-2
CONTROL ETH Connector
A.2
CONTROL ETH Connector
Connector Data
Each Megaplex-4100 CONTROL ETH port has a 10/100BASE-TX Ethernet station
interface terminated in an RJ-45 connector. The port supports the MDI/MDIX
crossover function, and therefore it can be connected by any type of cable
(straight or crossed) to any type of 10/100BASE-TX Ethernet port. The port also
corrects for polarity reversal in the 10BASE-T mode.
Connector pin functions for the MDI state are listed in Table A-2. In the MDIX
state, the receive and transmit pairs are interchanged.
Table A-2. CONTROL ETH Interface Connector, Pin Functions

Pin
Designation
Function
TxD+
Transmit Data output, + wire
TxD
Transmit Data output, wire
RxD+
Receive Data input, + wire
4, 5
RxD
7, 8
Not connected
Receive Data input, wire
Not connected
Connection Data
Use a standard station cable to connect the CONTROL ETH connector to any type
of 10/100BASE-TX Ethernet port.
A.3
ALARM Connector
The ALARM connector is a 9-pin D-type female connector which provides

connections to the following functions:
Major and minor alarm relay contacts
+5V auxiliary voltage output (through 330 series resistor)
External alarm sense input, accepts RS-232 levels. Can be connected to the
+5V auxiliary output by external dry contacts.
Connector pin functions are listed in Table A-3.
Caution To prevent damage to alarm relay contacts, it is necessary to limit, by external

means, the maximum current that may flow through the contacts (maximum
allowed current through closed contacts is 1 A; load switching capacity is 60 W).
The maximum voltage across the open contacts must not exceed 60 VDC/30 VAC.
ALARM Connector
A-3
Table A-3. ALARM Connector, Pin Functions

Pin
Function
Major alarm relay normally-open (NO) contact
Major alarm relay normally-closed (NC) contact
Ground
Minor alarm relay normally-open (NO) contact
Minor alarm relay normally- closed (NC) contact
Major alarm relay center contact
External alarm input
+5V auxiliary output (through 330 series resistor)
Minor alarm relay center contact
A.4
CL CLOCK Connector
Connector Data
The CLOCK interface located on CL modules has one RJ-45 eight-pin connector.
Table A-4 lists the connector pin functions.
Table A-4. CL CLOCK Connector, Pin Functions
A-4
Pin
Direction
Input
Clock In (ring)
Input
Clock In (tip)
Output
Clock Out (ring)
Output
Clock Out (tip)
Frame Ground (connection controlled by internal jumper)
Not connected
Not connected
CL CLOCK Connector
Function
Signal Ground (connection controlled by internal jumper)
Connection Cable for Unbalanced Interface, CBL-RJ45/2BNC/E1/X

To connect the CL CLOCK connector to equipment with unbalanced interface, it is
necessary to convert the RJ-45 connector to the standard pair of BNC female
connectors used for unbalanced interfaces.
For this purpose, RAD offers a 15-cm long adapter cable, CBL-RJ45/2BNC/E1/X,
which has one RJ-45 plug for connection to CL CLOCK connector and two BNC
female connectors at the other end. Cable wiring is given in Figure A-3.
Clock Input
(Green)
RJ-45
BNC
Female
CLOCK IN Ring
Clock Output
(Red)
CLOCK IN Tip
NC
CLOCK OUT Ring
CLOCK OUT Tip
NC
Cable Sense (option)
GND
..
.
Input
(Green BNC)
.
..
Output
(Red BNC)
Figure A-3. Unbalanced CLOCK Interface Adapter Cable, CBL-RJ45/2BNC/E1/X, Wiring Diagram
Connection Cable for Balanced Interface

The cable used for connecting the CL CLOCK connector to equipment with
balanced interface should include only two twisted pairs, one for the clock output
and the other for the clock input.
The cable end intended for connection to the CL must be terminated in an RJ-45
plug. Make sure that pin 7 in the RJ-45 plug is not connected.
CL CLOCK Connector
A-5
A.5
Power Connectors
AC PS Module Connections
The AC-powered PS modules have one standard IEC three-pin socket for the
connection of the AC power.
In addition, the AC-powered PS modules include a three-pin connector,
designated VDC-IN, for the connection of external phantom feed and ring
voltages. Connector wiring is listed in Table A-5.
Table A-5. VDC-IN Connector on AC-Powered Modules, Pin Functions

Pin
Function
Common reference (0V ground), BGND
+72 VDC ring and feed voltage input
-48 VDC ring and feed voltage input
RTN
+72
-48
DC PS Module Connections
The DC-powered PS modules have a single three-pin VDC-IN connector, for the
connection of the supply voltage (24 or 48 VDC), as well as a +72 VDC input for
ring and phantom feed purposes.
Connector wiring is listed in Table A-6, together with a view of the connector
itself. The nominal supply voltage appears in the table under the connector.
Table A-6. VDC IN Connector on DC-Powered Modules, Pin Functions

Pin
Function
Common reference (0V ground), BGND
+72 VDC ring and feed voltage input
-24 or -48 VDC supply voltage input
24 VDC Module
Note
72V
24V
48 VDC Module
72V
48V
RAD supplies mating connectors for the DC power connectors. Prepare the cable
using the supplied connector in accordance with the panel inscriptions and your
requirements.
Ground Connection
All PS modules are equipped with a grounding screw on the module panel for
connecting the protective ground.
A-6
Power Connectors
Appendix B
I/O Modules
This appendix describes the main features, applications and installation
procedures for the I/O modules operating in the Megaplex-4100 chassis with CLI
management. It also describes the installation and operation procedures for the
MPF device providing power feed to remote modems and repeaters in conjunction
with ASMi-54C/N modules.
For the same modules operating in the Megaplex-4100 chassis with menu
interface, or for modules operating in the Megaplex-2100/2104 chassis (modules
shared by Megaplex-4100 and Megaplex-2100/2104), refer to the corresponding
module Installation and Operation Manual.
B.1
M8E1, M8T1 Modules
The M8E1 and M8T1 modules enable direct connection of Megaplex-4100 to up

to 8 E1 or T1 lines. Up to 10 modules can be installed in a single chassis, giving
Megaplex-4100 up to 80 E1/T1 ports.
In addition to providing E1/T1 interfaces for Megaplex-4100 units, M8E1/M8T1
modules enable packet-based Fast Ethernet services.
The modules have two types of external ports:
Eight independently configurable E1/T1 external ports for E1/T1 services
Three 10/100 Mbps Ethernet ports, for packet-based services.
Product Options
The Ethernet ports are offered with the following types of interfaces:
Two 10/100BASE-TX ports terminated in RJ-45 connectors.
Two sockets for Fast Ethernet SFP optical transceivers.
Applications
Figure B-1 shows a typical application for a Megaplex-4100 equipped with
M8E1/M8T1 modules.
In this application, a Megaplex-4100 located at a point-of-presence (PoP) serves
as a multiservice access node: the ports of the I/O modules installed in the
Megaplex-4100 provide the First Mile connections over E1 and T1 lines to
customer equipment, such as dedicated FCD, ASMi, etc., offered by RAD.
The STM-1/SONET link connecting the Megaplex-4100 to the ADM (add/drop
multiplexer) at the PoP can carry all the payload that can be used by I/O modules
M8E1, M8T1 Modules
B-1
Appendix B I/O Modules
installed in the chassis (up to 63 E1/84 T1 streams), with flexible mapping. In

addition, the DS0/DS1 cross-connect matrix of the Megaplex-4100 can provide
cross-connect services among the I/O modules installed in the chassis.
The application shown in Figure B-1 also gives users connected to M8E1/M8T1
Ethernet ports access to packet switched networks (PSN), such as Internet or
metropolitan Ethernet networks, via the GbE links of the Megaplex-4100.
Figure B-1. Multiservice Access Aggregation to SDH/SONET and Packet-Switched

Networks
Features
E1/T1 Services
The E1 interface is compatible with all carrier-provided E1 services, meeting the
requirements of ITU-T Rec. G.703, G.704 and G.732. It supports both 2 (G.732N)
and 16 (G.732S) frames per multiframe formats, as well as unframed mode. It
also supports CRC-4 and E bit, in compliance with G.704 recommendations. Zero
suppression over the line is HDB3. The E1 interface is equipped with an integral
user-enabled LTU, ensuring ranges of up to 2 km (1.2 miles).
The T1 interface is compatible with ANSI requirements. Both D4 and ESF framing
formats are supported. Zero suppression is selectable for Transparent, B7ZS, or
B8ZS. The T1 interface is equipped with an integral user-enabled CSU, ensuring
ranges of up to 1.6 km (1 mile).
Internal TDM flows are handled by an internal DS0 cross-connect matrix. The
matrix supports flexible payload routing, independently configurable for each
port, at the individual timeslots (DS0) level. This enables routing individually
selected timeslots (including timeslots with split assignment) to other modules
B-2
M8E1, M8T1 Modules
installed in the Megaplex-4100 chassis, via the internal TDM buses. Timeslots can
be routed to any port with compatible properties. The signaling information
associated with voice timeslots can be translated by means of user-specified
signaling profiles.
The modules also support unidirectional broadcast applications.
The E1/T1 ports can also be connected to SDH/SONET links, which permits using
the Megaplex-4100 as an SDH/SONET terminal multiplexer (TM). Using the
Megaplex-4100 as an add/drop multiplexer (ADM), in either linear chain or ring
topologies, enables dropping part of the SDH/SONET link payload at a certain
location, and possibly inserting other payload.
Timing
M8E1/M8T1 modules recover the timing of each received E1/T1 stream, and
therefore can also provide timing reference signals derived from a selected E1/T1
stream for the nodal Megaplex-4100 timing subsystem. M8E1/M8T1 transmit
timing can be locked to the Megaplex-4100 nodal timing.
Cross-Connections
The M8E1/M8T1 modules support both DS0 and TDM cross-connection, selectable
at the level of the individual E1/T1 port:
ds0 cross-connect used when necessary to control the routing of individual

timeslots, and therefore relevant only when using a framed mode. The DS0
cross-connect enables connecting payload between E1 to T1 ports.
tdm cross-connect mode used when necessary to transparently transfer

the entire stream to a selected destination port using the unframed mode.
Ethernet Services
The Ethernet services are provided by means of an internal Layer-2 Ethernet
switch that fully complies with the IEEE 802.3/Ethernet V.2 standards, and has
full VLAN support. The total Ethernet traffic per module (from 1, 2 or 3 ports) is
up to 100 Mbps.
The interface supports autonegotiation for plug-and-play Ethernet connectivity
and complies with IEEE 802.3/Ethernet V.2 standards.
The Ethernet switch switches traffic between the module Ethernet ports and the
CL module Ethernet traffic subsystem, for connection via the CL GbE ports to a
packet-switched network, or for transmission through the SDH network via
virtually concatenated groups (VCGs). It also switches traffic between module
Ethernet ports and HDLC/MLPPP ports, and traffic between Ethernet ports of I/O
modules.
The forwarding of Ethernet payload within the Megaplex-4100 is configured by
defining flows.
The customers edge traffic accepted by M8E1/M8T1 Ethernet ports is directed to
other interfaces that can transfer the traffic to the transport network. These
interfaces are as follows:
GbE ports located on the CL.2 modules (ethernet or lag)
M8E1, M8T1 Modules
B-3
ASMi-54C, MPW-1) (ethernet)
mlppp port, which, in turn, needs to be bound to the physical layer.

SVI ports, which are intermediate Ethernet entities between the

Bridge/Router and another Ethernet port (bound one-to-one). An SVI port
also serves as an ingress or egress port for terminating management flows.
The management flows are configured between the physical port which is the
management source and the corresponding SVI port bound to the bridge port
of the Unaware Management Bridge. For more information on the bridge
connections and configuration see Management Bridge in Chapter 5.
Processing and Termination of Ethernet Traffic over TDM

This function provides the interface between the M8E1/M8T1 Ethernet switch and
the local cross-connect matrix:
In the direction from the switch to the matrix, Ethernet frames are
terminated and processed for transmission through the appropriate
HDLC/MLPPP ports, that is, over TDM media.
In the inverse direction, the payload received from TDM media is packetized
and inserted in Ethernet frames for transmission to the appropriate Ethernet
port.
The Ethernet services supported by M8E1 and M8T1 modules are configured by
defining flows within the Megaplex-4100. The flows are defined by means of
Ethernet virtual connection that interconnects two or more ports (called Logical
MAC ports).
M8T1 it is HDLC protocol, in M8E1 and M8SL two types of protocols can be used:
HDLC and MLPPP.
Figure B-2 shows the relationship between the entities involved in the Ethernet
over E1/T1 functionality.
B-4
M8E1, M8T1 Modules

Logical MAC
1..32
MLPPP
1
HDLC
1..32
XC
Unframed
E1
1
1:
1:n
Bind
1:1
PPP
1..8
Framed
E1/T 1
Figure B-2. Logical Entities Representing Ethernet Traffic over E1/T1 Media
entity. The HDLC port can be defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1/T1 port. As seen in the diagram, the
timeslot mapping between the framed E1/T1 and HDLC ports needs to be done
via cross-connect.
A maximum of 32 HDLC ports can be defined on an M8E1/M8T1 module; together
with the three Ethernet ports, an M8E1/M8T1 module supports up to 35 ports.
Each of these ports can be connected to any other Ethernet port within the
Megaplex-4100, such as another HDLC or external Ethernet port on any module
(including GbE ports on CL modules), or a Logical MAC port.
The binding of HDLC/MLPPP to a flow is done by the intermediate Logical MAC
entity.
Termination of Ethernet Traffic over E1-i/T1-i Links of

SDH/SONET
The M8E1/M8T1 Ethernet termination and processing function can also serve
Ethernet traffic carried through E1-i/T1-i links on a CL.2 module operating in the
SDH/SONET mode. This processing is done via HDLC protocol.
Inband Management
M8E1/M8T1 supports the transfer of management traffic, inband, for both TDM
and Ethernet applications:
A dedicated management timeslot can be configured on each E1/T1 port

operating in a framed mode. This enables extending the management
M8E1, M8T1 Modules
B-5
connections to other RAD equipment using inband management over

dedicate timeslots.
Inband management can be carried over Ethernet ports and HDLC/MLPPP

ports configured on M8E1/M8T1, which are included in the management flow
configured by the user (using the dedicated management VLAN configured
for the Megaplex-4100 host).
Protection for E1/T1 Links

The E1/T1 ports of M8E1/M8T1 use the TDM group protection functionality, with
two different protection modes available:
Dual-cable protection with parallel transmission
Y-cable protection.
This type of protection is available for ports both on the same module and on
different modules.
The protection group ports can be located either on the same module or on
another module, and can be any of the following types: E1/T1, internal E1/T1
ports of CL modules, or internal E1 ports of M8SL, OP or ASMi-54C/N modules.
A special TDM Ring protection functionality is used for the ports participating in a
ring. For more information, see TDM Group Protection and TDM Ring Protection in
Chapter 5.
The M8E1/M8T1 module occupies one I/O slot in the Megaplex-4100 chassis.
Typical panels are shown in Figure B-3. The module panel includes a TDM
interfacing section, and an Ethernet interfacing section.
B-6
M8E1, M8T1 Modules
L
I
N
K
M8E1
M8E1
M8T1
M8T1
STATUS
2
1
4
3
5
6
7
8
STATUS
2
1
4
3
5
6
7
8
STATUS
2
1
4
3
5
6
7
8
STATUS
2
1
4
3
5
6
7
8
L
I
N
K
LINK
1-8
L
I
N
K
L
I
N
K
LINK
1-8
LINK
1-8
LINK
1-8
TX
ACT
TX
LINK
LINK
RX
ACT
TX
LINK
RX
ACT
RX
LASER
CLASS
1
E
T
H
1
E
T
H
1
E
T
H
2
E
T
H
2
E
T
H
3
E
T
H
3
M8E1 Module with

Ethernet Ports Equipped
with SFPs
ACT
ACT
LINK
LINK
ACT
ACT
LINK
LINK
ACT
ACT
LINK
LINK
M8E1 Module with

Copper
Ethernet Ports
E
T
H
1
E
T
H
1
E
T
H
2
E
T
H
2
E
T
H
3
E
T
H
3
M8T1 Module with

Ethernet Ports Equipped
with SFPs
ACT
LINK
ACT
LINK
ACT
LINK
M8T1 Module with

Copper
Ethernet Ports
Figure B-3. Module Panels

The module panel includes the following interface sections:
The TDM interfacing section, located at the upper part of the panel, includes
8 E1/T1 LINK status indicators (one for each E1/T1 port), and one 44-pin
D-type female connector, designated LINK 1-8, for connecting to all the
E1/T1 ports.
The Ethernet interfacing section, located in the lower part of the panel,
includes three Ethernet ports, designated ETH1, ETH2 and ETH3. The ports
are either equipped with SFPs or terminated in RJ-45 connectors. Each port
has its own set of ACT and LINK status indicators.
M8E1, M8T1 Modules
B-7
LED Indicators
E1/T1 Indicators
Each port status indicator operates as follows:
Lights steadily in green when the corresponding port is operating properly

and is active (that is, it is connected, and serves as the working port when
included in a protection group).
Flashes in green when the corresponding port is operating properly, and

serves as the protection port when TDM or RING protection is enabled.
Lights in red when the corresponding port detects loss of synchronization,

loss of signal or a red alarm
Flashes in red when the corresponding port is serving as the protection port
and detects loss of synchronization
Off when the corresponding port is not connected.
Ethernet Indicators
Each port has its own set of ACT and LINK status indicators.
The functions of the ETH port status indicator are as follows:
ACT (yellow): flashes in accordance with the transmit and/or receive activity
on the corresponding port
LINK (green): lights when the link integrity signal is detected by the
corresponding port (normal operating condition).
E1 Interface
Type and Bit Rate
E1, 2.048 Mbps (per link)
Number of Links
Line Interface
4-wire, 120 balanced
Coax, 75 unbalanced
Line Code
HDB3
Compliance
ITU-T Rec. G.703, G704, G.732 (including CRC-4 and

E bit)
Framing
B-8
M8E1, M8T1 Modules
Basic G.704 framing (G732N) with or without

CRC-4 per ITU-T Rec. G.704
Timeslot 16 multiframe (G732S), with or without

No framing (unframed mode)
Transmit Level
Receive Level
T1 Interface
3V 10%, balanced
2.37V 10%, unbalanced
Software selectable:
0 through -10 dB for short haul mode
0 through -33 dB for long haul (LTU) mode
Jitter Performance
Per ITU-T Rec. G.823
Surge Protection
Per ITU-T Rec. K.21
Connector
44-pin D-type female for all ports. Adapter (splitter)

cables available from RAD
Type and Bit Rate
T1, 1.544 Mbps
Compliance
AT&T TR-62411, AT&T Pub 54016, ANSI T1.107,

ANSI T1.403
Line Interface
Line Code
Bipolar AMI
Zero Suppression
Framing
Transmit Levels
Receive Level
Transparent (no zero suppression)
B7ZS
B8ZS
SF (D4)
ESF
DSU emulation: 3V 10%, software adjustable,

measured at 0 through 655ft
CSU mode: 0, -7.5, -15, -22.5 dB

software-selectable LBOs
Software selectable:
0 through 10 dB for short-haul (DSU) mode
0 through 34 dB for long-haul (CSU) mode
Jitter Performance
Per AT&T TR-62411
Connector
44-pin D-type female for all ports. Adapter cables

available from RAD
M8E1, M8T1 Modules
B-9
Indicators
Ethernet
Interfaces
Status Indicator per Link Dual-color indicator:
Lights steadily in green when the port is

connected and carries traffic
Flashes in green when the port is connected and

is the protection port in a TDM protection pair
Lights in red during red alarm
Flashes in red for a protection port that reports

loss of synchronization
Off when not connected
Number of Ports
3 (all either fiber-optic or copper, per customer

order)
Maximum Frame Size
1600 bytes
Data Rate
10/100 Mbps (Fast Ethernet)

Autonegotiation (Copper only)
Fiber Optic Ports
Hot-swappable SFPs
Note: For detailed specifications of the SFP

transceivers, see the SFP Transceivers data sheet
Connectors: LC
Copper Ports
Interface Type:10/100Base-TX
Connectors: Shielded RJ-45
Indicators (per Ethernet

port)
Diagnostics
B-10
ACT (yellow): flashes in accordance with the

transmit and/or receive activity on the
corresponding port
LINK (green): lights when the link integrity signal

is detected by the corresponding port
Total Bandwidth per

Module
100 Mbps
CAS Signaling Monitor
Display of signaling information for selected timeslots
User-Controlled Port
Loopbacks
Local loopback on each module port
Remote loopback on each module port
Network-Controlled Port
Loopbacks (M8T1, ESF
framing only)
Network line loopback (LLB)
Network payload loopback (PLB), available with

ESF framing
Timeslot Loopbacks
Local loopback
Remote loopback
M8E1, M8T1 Modules
Performance
Monitoring
E1 Ports
As per ITU-T G.826 (relevant parts)
T1 Ports
As per ANSI T1.403
Ethernet Ports
As per RMON-RFC2819
Power
Consumption
10.8W
Configuration
Programmable via Megaplex-4100 management

system
Environment
Operating Temperature
-10C to 55C (14F to 131F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
Up to 95%, non-condensing
Preparing the Module for Installation
Warning
Caution
Caution
Before performing any internal settings, adjustment, maintenance, or repairs,

first disconnect all the cables from the module, and then remove the module
from the Megaplex-4100 enclosure.
technician who is aware of the hazards involved.
Always observe standard safety precautions during installation, operation, and
maintenance of this product.
The M8E1/M8T1 modules contain components sensitive to electrostatic discharge

M8E1/M8T1 modules may be installed in an operating chassis (hot insertion).
Note
M8E1/M8T1 software can be updated by downloading from the CL module.

Therefore, if the M8E1/M8T1 module is not yet loaded with the required software
version, refer to Chapter 7 for detailed software downloading instructions.
No preparations are required for M8E1/M8T1 modules with UTP Ethernet ports,
terminated in RJ-45 connectors.
M8E1, M8T1 Modules
B-11
For M8E1/M8T1 modules equipped with Ethernet ports having SFP sockets, it may
be necessary to install or replace SFPs. M8E1/M8T1 modules have three
installation positions for SFPs, designated ETH1, ETH2, and ETH3:
To install an SFP, use the procedure prescribed in Installing an SFP below.
SFPs may be replaced using the procedure given in Replacing an SFP below.
M8E1/M8T1 modules equipped with RAD-supplied SFP plug-in modules comply

with laser product performance standards set by government agencies for Class 1
laser products. The modules do not emit hazardous light, and the beam is totally
enclosed during all operating modes of customer operation and maintenance.
Third-party SFP optical transceivers may be also used, provided they are
approved by an internationally recognized regulatory agency, and comply with
the national laser safety regulations for Class 1 laser equipment. However, RAD
strongly recommends ordering RAD SFPs, as this permits full performance testing
Warning
of the supplied equipment.
M8E1/M8T1 modules are shipped with protective covers installed on all the
optical connectors. Keep the covers for reuse, to reinstall the cover over the
optical connector as soon as the optical cable is disconnected.
SFPs installed on M8E1/M8T1 modules may be equipped with a laser diode. In
such cases, a label with the laser class and other warnings as applicable will be
attached near the SFP socket. The laser warning symbol may be also attached.
Warning
For your safety:

Do not look straight at the laser beam, and do not look directly into the
optical connectors while the module is operating.
Laser power up to 1 mW could be collected by an optical instrument.
Installing an SFP
Warning
B-12
M8E1, M8T1 Modules
Caution During the installation of an SFP with optical interfaces, make sure that all the
optical connectors are closed by protective caps.
connectors.
Note
The following procedures all have illustrations showing typical SFPs with optical
interfaces. Your SFPs may look different.
To install the SFP:
1. Lock the latch wire of the SFP module by lifting it up until it clicks into place,
as illustrated in Figure B-30.
Note
Some SFP models have a plastic door instead of a latch wire.
Figure B-4. Locking the Latch Wire of a Typical SFP

2. Carefully remove the dust covers from the corresponding SFP socket of the
M8E1/M8T1 module, and from the SFP electrical connector.
3. Orient the SFP as shown in Figure B-30, and then insert the rear end of the
4. Slowly push in the SFP to mate the connectors, until the SFP clicks into place.
If you feel resistance before the connectors are fully mated, retract the SFP
using the latch wire as a pulling handle, and then repeat the procedure.
Replacing an SFP
replacement with the system administrator. Note that during the replacement of
SFPs, only the traffic on the affected ETH link is disrupted (the other ETH link can
continue to carry traffic).
To replace an SFP:
4. Install the replacement SFP as prescribed in Installing an SFP.
M8E1, M8T1 Modules
B-13
Installing a Module in the Chassis
The M8E1/M8T1 module starts operating as soon as it is inserted in an operating

chassis.
Warning
To install an M8E1/M8T1 module:

1. Refer to the system installation plan and identify the prescribed module slot.
2. Check that the fastening screws at the module sides are free to move.
3. Insert the M8E1/M8T1 module in its chassis slot and slide it in as far as
possible.
4. Secure the M8E1/M8T1 module by tightening its two fastening screws.
5. The module starts operating as soon as it is plugged into an operating
enclosure. At this stage, ignore the alarm indications.
Connecting to Remote Equipment

Before starting, identify the cables intended for connection to each port of this
module, in accordance with the site installation plan.
Connecting the Electrical Ethernet Ports

Each M8E1/M8T1 ETH electrical port has a 10/100BASE-TX Ethernet interface
terminated in an RJ-45 connector. The port supports the MDI/MDIX crossover
function, and therefore it can be connected by any type of cable (straight or
crossed) to any type of 10/100BASE-TX Ethernet port. The port also corrects for
polarity reversal in the 10BASE-T mode.
Connector pin functions for the MDI state are listed in Table B-19. In the MDIX
Table B-1. ETH Connector, Pin Functions

Pin
B-14
Designation
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
M8E1, M8T1 Modules
Not connected
Not connected
To connect cables to the M8E1/M8T1 electrical Ethernet ports:
Connect the prescribed cable to the corresponding connector, ETH1, ETH2 or

ETH3.
Connecting the Optical Ethernet Ports

Before starting, review the general optical cable handling instructions in
Chapter 2.
To connect cables to the M8E1/M8T1 optical Ethernet ports:
Connect each prescribed cable to the corresponding Megaplex-4100

connector, ETH1, ETH2 or ETH3.
When two fibers are used, pay attention to connector polarity: the
transmitter output is on the left side.
Connecting the E1/T1 Ports

The module E1/T1 ports are terminated in a 44-pin D-type female connector. The
module connector supports both the unbalanced (M8E1 only) and balanced
interfaces. Each type requires a different adapter cable.
RAD offers the following adapter cables:
CBL-G703-8/RJ45/ST: adapter cable terminated in RJ-45 plugs at the users

end, for use when M8E1/M8T1 modules are connected to equipment with
balanced E1/T1 interfaces using pins 1, 2 for the receive (RX) pair and pins
4,5 for the transmit (TX) pair
CBL-G703-8/RJ45/X: adapter cable terminated in RJ-45 plugs at the users

balanced E1/T1 interfaces using pins 4,5 for the receive (RX) pair and pins 1,
2 for the transmit (TX) pair
CBL-G703-8/OPEN/2M: adapter cable terminated in free leads at the users

end, for balanced E1/T1 applications
CBL-G703-8/COAX: adapter cable terminated in BNC connectors at the users

end, for use when M8E1 modules are connected to equipment with
unbalanced E1 interfaces
The following sections describe these adapter cables, the functions of the 44-pin
connector pins for each interface type, and connection instructions.
CBL-G703-8/RJ45/ST Cable
The CBL-G703-8/RJ45/ST is a 2-meter cable for M8E1/M8T1 modules using the
balanced interface.
Figure B-32 shows the cable construction.
M8E1, M8T1 Modules
B-15

Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL-G703-8/RJ45/ST
Ch. 5
Ch. 6
Ch. 7
Ch. 8
ST-CLK
Station
Clock
Figure B-5. CBL-G703-8/RJ45/ST Cable

Table B-21 presents the cable wiring and identifies the interface connector pin
assignment.
B-16
M8E1, M8T1 Modules
Table B-2. CBL-G703-8/RJ45/ST Cable Wiring
Channel
44-Pin Connector
RJ-45
Pin
Connector
CH-1
CH-2
CH-4
Connector
Channel
Pins
31
RX Ring
17
RX Tip
2
5
RJ-45
44-Pin Connector
Pin
Connector
CH-5
Function
RJ-45
Connector
Pins
37
RX Ring
23
RX Tip
22
TX Ring
16
TX Ring
TX Tip
TX Tip
33
RX Ring
38
RX Ring
32
RX Tip
39
RX Tip
TX Ring
CH-3
Function
RJ-45
TX Ring
CH-6
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
26
RX Tip
19
TX Ring
25
TX Ring
TX Tip
10
TX Tip
35
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
24
RX Ring
27
RX Tip
21
TX Ring
18
TX Tip
CH-7
CH-8
ST-CLK
CBL-G703-8/RJ45/X Cable
CBL-G703-8/RJ45/X is a 2-meter cable. Figure B-33 shows the cable construction.
assignment.
Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL- G 703-8/R J45/X
Ch. 5
Ch. 6
Ch. 7
Ch. 8
Figure B-6. CBL-G703-8/RJ45/X Cable
M8E1, M8T1 Modules
B-17
Table B-3. CBL-G703-8/RJ45/X Cable Wiring

Channel
RJ-45
Connector
CH-1
CH-2
CH-3
CH-4
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
31
RX Ring
17
RX Tip
16
TX Ring
TX Tip
Channel
RJ-45
Connector
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
37
RX Ring
23
RX Tip
22
TX Ring
TX Tip
2
4
CH-5
33
RX Ring
38
RX Ring
32
RX Tip
39
RX Tip
TX Ring
TX Ring
CH-6
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
26
RX Tip
19
TX Ring
25
TX Ring
TX Tip
10
TX Tip
35
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
CH-7
CH-8
CBL-G703-8/OPEN/2M Cable
CBL-G703-8/OPEN/2M cable is a 2-meter cable for M8E1/M8T1 modules using the
balanced E1/T1 interface, terminated in free leads that can be connected to any
terminal block or connector appropriate for your application.
Figure B-34 shows the cable construction. Table B-23 presents the cable wiring
and identifies the pair functions.
CBL-G703-8/OPEN/2M
Figure B-7. CBL-G703-8/OPEN/2M Cable
B-18
M8E1, M8T1 Modules
Table B-4. CBL-G703-8/OPEN/2M, 8M Cable Wiring

44-Pin Connector
Channel
44-Pin Connector
Pair Color
Pin
Function
31
Rx Ring
17
Rx Tip
Blue
Tx Tip
Orange
16
Tx Ring
White
33
Rx Ring
32
Rx Tip
Tx Tip
Brown
Channel
Pair Color
Pin
Function
37
Rx Ring
White
23
Rx Tip
Brown/Blue
Tx Tip
Grey/Blue
22
Tx Ring
White
White
38
Rx Ring
White
Green
39
Rx Tip
White/Orange
Tx Tip
Orange/Green
White
White
5
Tx Ring
White
Tx Ring
34
Rx Ring
White
40
Rx Ring
White
20
Rx Tip
Grey
26
Rx Tip
Orange/Brown
Tx Tip
White/Blue
10
Tx Tip
Grey/Orange
19
Tx Ring
White
25
Tx Ring
White
35
Rx Ring
White
41
Rx Ring
White
36
Rx Tip
Orange/Blue
42
Rx Tip
White/Green
Tx Tip
Green/Blue
12
Tx Tip
Green/Brown
Tx Ring
White
11
Tx Ring
White
CBL-G703-8/COAX Cable
CBL-G703-8/COAX is a 2-meter cable for M8E1 modules using the unbalanced E1
interface. Figure B-35 shows the cable construction.
RX
Ch. 1
TX
RX
Ch. 2
TX
RX
Ch. 3
TX
CBL-G703-8/COAX
RX
Ch. 7
TX
RX
Ch. 8
TX
Figure B-8. CBL-G703-8/COAX Cable

assignment. In this cable, pin 15 (cable type sensing) is wired to pin 30 (frame
ground): this enables the M8E1 module to differentiate between the connection
of this cable and the connection of the
CBL-G703-8/RJ45/ST cable.
M8E1, M8T1 Modules
B-19
Table B-5. CBL-G703-8/COAX Cable Wiring

Channel Function
RX
1
TX
RX
2
TX
RX
3
TX
RX
44-Pin Connector
Pin
Function
31
Ring
29
Frame Ground
BNC
Contact
Shield
17
Tip
Center
Tip
Center
16
Ring
14
Frame Ground
33
Ring
44
Frame Ground
Tip
Center
Tip
Center
Ring
29
Frame Ground
34
Ring
29
Frame Ground
20
Tip
Center
Tip
Center
Ring
Frame Ground
35
Ring
44
Frame Ground
RX
6
TX
Shield
RX
7
TX
Shield
Shield
Tip
Center
Tip
Center
Ring
29
Frame Ground
Cable Type Sensing
15
Sense Input,
connected to
pin 30
Signal Ground
30
Ground
Frame Ground
44
Cable Shield
TX
TX
Shield
36
Shield
14
RX
Shield
32
19
Channel Function
RX
8
Shield
TX
Function
BNC
Contact
37
Ring
Shield
29
Frame Ground
44-Pin Connector
Pin
23
Tip
Center
Tip
Center
22
Ring
14
Frame Ground
38
Ring
44
Frame Ground
Shield
Shield
39
Tip
Center
Tip
Center
Ring
14
Frame Ground
40
Ring
29
Frame Ground
Shield
Shield
26
Tip
Center
10
Tip
Center
25
Ring
14
Frame Ground
41
Ring
44
Frame Ground
Shield
Shield
42
Tip
Center
12
Tip
Center
11
Ring
14
Frame Ground
Shield
Connecting Cables to the E1/T1 Ports

Using the site installation plan, identify the cable intended for connection to the
corresponding M8E1/M8T1 connector, and connect the cable to the module as
explained below.
To connect the CBL-G703-8/RJ45/ST and CBL-G703-8/RJ45/X cables:

1. Connect the 44-pin connector of the cable to the M8E1/M8T1 front panel
connector.
2. Connect the RJ-45 plug of each port interface (the plugs are marked CH-1 to
CH-8) to the prescribed user equipment or patch panel connector. Insulate
unused connectors, to prevent accidental short-circuiting of their exposed
contacts to metallic surfaces.
B-20
M8E1, M8T1 Modules
To connect the CBL-G703-8/COAX cable:

1. Connect the 44-pin male connector of the cable to the M8E1 front panel
connector.
2. Connect the BNC plugs of each port interface (the plugs are marked with the
number of the port) to the prescribed user equipment or patch panel
connectors. Pay attention to correct connection:
TX connector: serves as the transmit output of the port
RX connector: serves as the receive input of the port.
To connect the CBL-G703-8/OPEN cable:

1. Connect the free cable ends in accordance with the prescribed termination
method.
2. When done, connect the 44-pin male connector of the cable to the
M8E1/M8T1 front panel connector.
Normal Indications
Ethernet Ports
Once the equipment connected to the M8E1/M8T1 Ethernet ports is operational,
the following indications appear for each port:
The LINK indicator lights as long as the port is connected to operational

equipment
The ACT indicator may light continuously, or flash from time to time, in
accordance with the transmit and receive activity at the corresponding port.
E1/T1 Ports
The status of each M8E1/M8T1 link is indicated by a separate indicator.
During normal operation, after communication with the remote equipment is
established, the port indicators of the M8E1/M8T1 module light steadily in green;
however, if a port is configured as the protection port in a protection group, its
indicator flashes in green.
If the other communication equipment on the link is not yet operative, the port
indicator lights in red. The indicator turns green (or flashes in green) as soon as
the link with the remote equipment is established.
The indicators of ports configured at shutdown are off.
Configuration Considerations
You can configure up to four HDLC ports for each E1/T1 port (link), where each
port can be assigned a fraction (number of timeslots) of the port bandwidth. The
maximum number of HDLC ports in an M8E1/M8T1 module is 32.
M8E1, M8T1 Modules
B-21
Moreover, you can select specific timeslots to be assigned to each port. Binding
the HDLC port to specific timeslots of E1/T1 physical port is done via the xc
command.
The nominal bandwidth assigned to the HDLC port is determined by the number
of timeslots cross-connected with itm and must be a multiple of 128 kbps.
The available range for M8E1 is 128 to 2048 kbps (2 to 32 cross-connected
timeslots); for M8T1 it is 128 to 1536 kbps (2 to 24 cross-connected timeslots).
Any given port timeslot can be assigned only one use (an HDLC bundle, TDM
traffic, or inband management). Timeslots assigned to HDLC ports are always
data timeslots.
Before setting the HDLC port to no shutdown, make sure that the source
E1/T1/E1-i/T1-i ports are also set to no shutdown and bound to this HDLC port,
and vice-versa.
When configuring Ethernet termination for E1-i/T1-i links on a CL.2 module, it is
possible to open (set to no shutdown ) only 8 E1-i/T1-i links on a CL.2 module
per each M8E1/M8T1 module and bind up to 4 HDLC ports to each of these links
so that the total capacity is 32 HDLC ports per M8E1/M8T1 module. Moreover,
each used E1-i/T1-i link cross-connected with HDLC ports of M8E1/M8T1 reduces
the number of its external E1/T1 links that can be connected to E1/T1 equipment.
Configuring MLPPP and PPP Ports

Ports using MLPPP (multilink point-to-point protocol) as the Layer 2 protocol are
called MLPPP ports. They exist only on M8E1 modules, not on M8T1 modules. In
the case of an MLPPP port, one or more unframed E1 ports are logically bonded
together as a single serial port. There is one MLPPP port per M8E1module.
The MLPPP port can be bound to any number of the links supported by the
module, that is, from 1 to 8. All the links (ports) used by the MLPPP port must
have identical physical layer parameters and their line-type parameter must be
configured as unframed. Therefore, each bonded link adds 2048 kbps to the
available bandwidth.
An MLPPP port has PPP ports bound to it. The binding is done in two stages and
this PPP port needs to be further bound to the physical layer (see Figure B-2).
E1 ports bound (via PPP) to MLPPP ports cannot be part of a protection group.
On the other hand, some redundancy is inherent in the MLPPP protocol, because
if one of the bonded links is out-of-service, the result is only a reduction in the
available transmission bandwidth.
E1 ports bound (via PPP) to MLPPP ports must be cross-connected via tdm
command and configured as unframed.
Configuring TDM Group/Ring (E1/T1 Port) Protection

To avoid duplication of configuration parameters, all the E1/T1 port parameters
are selectable only for the working port. The parameters of the other
B-22
M8E1, M8T1 Modules
been updated. However, you can select different interface-type for the working
and protection ports.
When the other port in a redundancy pair is an internal port of a CL.2 module,
only the dual-cable-tx protection mode can be used. CL.2 internal ports may also
use path protection, so this type of protection is not necessary for internal ports
included in another protection scheme.
In M8E1, when the other port in a protection group is an internal E1 port of an
M8SL or ASMi-54C/N module, only the dual-cable-tx or tdm-ring protection can be
used.
E1 ports bound to MLPPP ports cannot be included in a protection group.
To avoid configuration errors, use the following procedure:
1. Before starting the configuration of the protection parameters, make sure
that the other port does not carry traffic.
2. After completing configuration of the working port, configure the protection
port (interface-type).
When using protection, timeslot assignment can be performed only for the
working E1/T1 port: the assignment is automatically copied to the protection
partner of the working port.
Configuring TDM Cross-Connect

An unframed E1 port can be cross-connected only with another unframed E1 port
or E1-i port. The TDM cross-connect is not available on M8T1 modules since they
do not support unframed streams.
OOS Signaling
When choosing the OOS signaling option in M8E1/M8T1 modules working in one
chassis with VC modules (see E1 Ports or T1 Ports in Chapter 5 for description),
take into account the following:
force-idle and busy-idle options are suitable for use with all the VC module
types.
force-busy and idle-busy options is suitable for use with E&M and FXO
Configuration Sequence
The list of tasks that can be performed on the M8E1/M8T1modules and the
recommended configuration sequence are described in the table below. For
detailed descriptions, refer to Chapter 5. The second column indicates the
configuration context for this task, in which it can be found in Chapter 5. The
third column refers to the reference tables and relevant sections that should be
consulted when planning the module operation.
M8E1, M8T1 Modules
B-23
Task
Configuration Context
Reference
Configure an M8E1/M8T1 module

and put it into service
configure>slot>card-type
Select an E1/T1 Port as system

timing reference
config>system>clock>domain(1)
Configure the E1 port parameters

(M8E1)
configure>port>e1
E1 Ports in Chapter 5, pay attention

to Features Supported by
Megaplex-4100 E1 and Internal E1
Ports table
Configure the T1 port parameters

(M8T1)
configure>port>t1
T1 Ports in Chapter 5, pay attention

Megaplex-4100 T1 and Internal T1
Ports table
Configure inband management

through E1/T1 port
configure>port>e1
Configure the E1/T1 port CAS

signaling profile
configure>port>signaling-profile
Configure the Ethernet physical

layer parameters
configure>port>ethernet
User Ethernet Ports in Chapter 5
Configure timeslot assignment for

E1/T1 ports (DS0 cross-connect
for E1/T1 ports)
configure>cr>ds0
To find which ports on which

modules can be cross-connected
with M8E1/M8T1 ports, see CrossConnect Table in Chapter 5
Configure the split assignment of

timeslots, for each module port
configure>cr>split-ts
Used for operation with

HSU-6/HSU-12, HS-S, HS-RN,
VC-4A/VC-8A, LS-6N/LS-12
Cross-connect the full payload

from this e1 port with another
port of the same type and
configuration
configure>cr>tdm
Not available for T1 (unframed T1

not supported on M8T1)
configure>port>t1
Mapping E1 to Ethernet via MLPPP

protocol
Bind E1 streams to PPP ports
configure>port>ppp
Configure MLPPP port and bind the

PPP ports to it
configure>port>mlppp
Configure Logical Mac and bind

the MLPPP port to it
configure>port>logical-mac
B-24
M8E1, M8T1 Modules
Task
Configure ingress and egress flows

between Logical MAC and Ethernet
ports
configure>flows
Reference
Mapping E1/T1 to Ethernet port

via HDLC protocol
Configure HDLC port and bind
E1/T1 stream to it
configure>port>hdlc
Configure Logical MAC port and

bind to it the HDLC port

between Logical MAC and Ethernet
ports
configure>flows
Configure Ethernet termination for

for HDLC ports)
configure>cr>ds0

E1-i/T1-i links on a CL.2 module
(DS0 cross-connect for HDLC
ports)
configure>cr>ds0
Configuring TDM group protection
config>protection>tdm-group
Configuring TDM ring protection
config>protection>tdm-ring

with M8E1/M8T1 ports, see CrossConnect Table in Chapter 5
Monitoring and Diagnostics

Diagnostics
M8E1/M8T1 diagnostic capabilities include local and remote loopback on each
E1/T1 port (see E1 Ports and, respectively, T1 Ports in Chapter 5):
On the port level
On the timeslot level.
In addition, M8T1 modules support inband code-activated loopbacks specified in

ANSI T1E1.2/93-003, as follows:
Network line loopback
Network payload loopback
Network CSU loopback.
M8E1, M8T1 Modules
B-25
Monitoring
The M8E1 modules support the collection of performance diagnostics on E1 ports
in accordance with ITU-T G.826, relevant parts. The M8T1 modules support the
collection of performance diagnostics on T1 ports in accordance with ANSI
T1.403.
The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819.
For more information:
E1/T1 ports see E1 Ports and T1 Ports in Chapter 5
Ethernet ports - see Ethernet Ports in Chapter 5.
Troubleshooting
If a problem occurs, check the displayed alarm messages and refer to the Chapter
6 for their interpretation.
Note
If the problem is detected the first time the module is put into operation,
perform the following preliminary checks before proceeding:
Check for proper module installation and correct cable connections, in
accordance with the system installation plan.

Check that the module configuration parameters are in accordance with the
specific application requirements, as provided by the system administrator.

If, after collecting all the relevant information, the problem appears to be related
to the operation of one of the M8E1/M8T1 ports, perform the actions listed
below, until the problem is corrected:
Make sure that no test has been activated on the corresponding M8E1/M8T1
port. Use the Megaplex-4100 management system to find and deactivate the
active test or loopback.
Activate the local loopback on the corresponding port. If the indicator of the
corresponding local port lights in green while the loop is connected, the
problem is external. Check cable connections and the transmission equipment
Quickly check the link to the remote Megaplex-4100 unit by activating the
remote port loopback at the remote unit. If the link operates properly, the
indicator of the corresponding local port lights in green.
If the test fails, there is a problem with the transmission through the
network, or with the M8E1/M8T1 modules. Repeat the test after carefully
checking all the configuration parameters of the module and its ports. If the
problem persists, replace the module and check again.
B-26
M8E1, M8T1 Modules
B.2
M8SL Modules
This section describes the technical characteristics, applications, installation and

operation of the M8SL SHDSL I/O modules for the Megaplex-4100 Next
Generation Multiservice Access Node.
In addition to providing SHDSL interfaces for Megaplex-4100 units, M8SL modules
enable Megaplex-4100 units to support Ethernet services. In particular, M8SL
modules support services suitable for metropolitan Ethernet network
applications. These services are based on the Metro Ethernet Forum (MEF)
specifications, which supplement existing technical standards in order to ensure
interoperability and adequate performance of Ethernet networks in metro
applications.
Product Options
Applications
Figure B-14 shows a typical application for a Megaplex-4100 equipped with M8SL
modules.
In this application, a Megaplex-4100 located at a point-of-presence (PoP) serves
as a multiservice access node: the ports of the I/O modules installed in the
Megaplex-4100 provide the Last Mile connections over E1, T1, and SHDSL lines to
the customers equipment, such as a dedicated FCD, ASMi, etc., offered by RAD.
The STM-1 link connecting the Megaplex-4100 to the ADM at the PoP can carry all
the payload that can be used by I/O modules installed in the chassis (up to 63 E1
streams), with flexible mapping. In addition, the DS0/DS1 cross-connect matrix of
the Megaplex-4100 can also provide cross-connect services among the I/O
modules installed in the chassis.
The application shown in Figure B-14 also permits users connected to M8SL
metropolitan Ethernet networks, via the GbE links of the Megaplex-4100.
M8SL Modules
B-27
Figure B-9. M8SL Typical Application
Features
The M8SL modules have two types of external ports:
Eight SHDSL independently configurable external ports for E1 (TDM) services
Three 10/100 Mbps Ethernet ports, for packet-based services.
The main services provided by Megaplex-4100 modules are described below.
SHDSL Transport Services

M8SL are I/O modules using the single-pair high-speed digital subscriber line
(SHDSL) technology for line transmission that provide the Megaplex-4100 with
SHDSL interfaces capable of carrying E1 and fractional E1 payloads.
The type of SHDSL interfaces provided by the module STU-C (SHDSL terminal
unit CO) or STU-R (SHDSL terminal unit remote) as well as the bandwidth,
are selected by software. The module handles all the signal processing, framing
and signaling processing tasks necessary for interfacing.
The SHDSL technology, standardized in ITU-T Rec. G.991.2, is an efficient method
for transmitting full-duplex data at high rates over a single unloaded and
unconditioned twisted copper pair, of the type used in the local telephone
distribution plant. Therefore, SHDSL provides a cost-effective solution for
short-range data transmission and last-mile applications.
M8SL modules can be configured by the user to operate in accordance with either
ITU-T Rec. G.991.2 Annex A for compatibility with North American (or similar)
networks, or Annex B for compatibility with European (and similar) networks.
Each M8SL module port is supported by an independent multi-rate SHDSL
modem. Each modem supports user-selectable data rates in the range of 192 to
B-28
M8SL Modules
2048 kbps, for a maximum payload capacity of up to 256 timeslots

(16.384 Mbps) per M8SL module.
M8SL ports can operate in a link with other M8SL ports, as well as with other RAD
equipment having STU-R SHDSL interfaces, such as the ASMi-52 G.HDSL Modems
with Remote Management offered by RAD, FCD-IP, FCD-IPM, etc.
M8SL modules will also operate in a link with 991.2-compatible STU-R units from
other vendors.
Note
The M8SL ports can be operated as STU-R ports only when connected to other
M8SL ports (configured as STU-C ports).
E1 Services
M8SL E1 subsystem provides the Megaplex-4100 with internal (virtual) E1 ports,
one for each external SHDSL link. The E1 subsystem handles all the framing and
signaling processing tasks necessary for interfacing to the E1 ports, as well as the
facilities needed to support Ethernet services over these E1 ports.
Each M8SL port can transfer either basic G.704 or G.704 multiframes (2 or 16
frames per multiframe, respectively), according to user selection. Each port can
also be operated in an unframed mode, which supports transparent transmission
of unframed 2.048 Mbps signals.
be routed to any port with compatible properties. The signaling information
associated with voice timeslots can be translated by means of user-specified
signaling profiles.
The module also supports unidirectional broadcast applications.
For applications requiring transparent transfer of E1 data streams, M8SL module
ports can be configured to use the unframed mode: in this case, the internal
matrix operates as a DS1 cross-connect matrix.
The E1 ports can also be connected to SDH links, which permits using the
Megaplex-4100 as an SDH terminal multiplexer (TM). Using the Megaplex-4100 as
an add/drop multiplexer (ADM), in either linear chain or ring topologies, enables
dropping part of the SDH/SONET link payload at a certain location, and possibly
inserting other payload.
Cross-Connections
The M8SL modules support both DS0 and TDM cross-connection, selectable at
the level of the individual internal E1 port:


the entire E1 stream to a selected destination port using the unframed mode.
M8SL Modules
B-29
Ethernet Services
The total Ethernet traffic per module (from 1, 2 or 3 ports) is up to 100 Mbps.
The Ethernet services are provided by means of an internal Layer 2 Ethernet
full VLAN support. The Ethernet switch serves both traffic and management:
The traffic is supported by means of three ports, connected to the three

external Ethernet ports of the module, by an internal port connected to the
module TDM cross-connect matrix, and by an additional Fast Ethernet port
connected to the Ethernet traffic handling subsystem of the CL modules
installed in the Megaplex-4100.
The external Ethernet ports can be ordered with one of the following types of
interfaces:
10/100BASE-TX interfaces terminated in RJ-45 connectors.
Sockets for SFP Fast Ethernet transceivers. RAD offers several types of
SFPs with optical interfaces, for meeting a wide range of operational
requirements (SFPs with copper interfaces are also available).
Management is supported by a dedicated port internally connected to the

M8SL management subsystem, and by another Fast Ethernet port connected
to the management handling section of the CL modules installed in the
Megaplex-4100 (this section is available on all CL modules).

The Ethernet switch switches traffic between the module Ethernet ports, SHDSL
ports and the CL module Ethernet traffic subsystem (for connection via the CL GbE
ports to a packet-switched network, or for transmission through the SDH network
via virtually concatenated groups (VCGs)), and between module Ethernet ports and
HDLC/MLPPP ports. It also switches traffic between Ethernet ports of I/O modules.
defining flows.
The customers edge traffic accepted by M8SL Ethernet ports is directed to other
interfaces that can transfer the traffic to the transport network. These interfaces
are as follows:
B-30
GbE ports located on the CL.2 modules (ethernet or lag ).


M8SL Modules
Unaware Management Bridge. For more information on the bridge
The Ethernet switch switches traffic between the module Ethernet ports,
including ETH over SHDSL, and the CL module Ethernet traffic subsystem (for
connection via the CL GbE ports to a WAN or packet-switched network, or for
transmission through the SDH network via virtually concatenated groups (VCGs)),
and between module Ethernet ports and the module cross-connect matrix, in
accordance with the parameters (Ethernet flows) configured by the user.
Processing and Termination of Ethernet Traffic over TDM

This function provides the interface between the M8SL Ethernet switch and the
local cross-connect matrix:
In the direction from the switch to the matrix, Ethernet frames are
terminated and processed for transmission through the appropriate
HDLC/MLPPP ports, that is, over TDM media.
In the inverse direction, the payload received from TDM media is packetized
and inserted in Ethernet frames for transmission to the appropriate Ethernet
port.
The Ethernet services supported by M8SL are configured by defining flows within
the Megaplex-4100. The flows are defined by means of Ethernet virtual
connection that interconnects two or more ports (called Logical MAC ports).
M8SL two types of protocols can be used: HDLC and MLPPP.
Figure B-2 shows the relationship between the entities involved in the Ethernet
over E1 functionality.
Logical MAC
1..32
MLPPP
1
HDLC
1..32
XC
Unframed
E1
1
1:
1:n
Bind
1:1
PPP
1..8
Framed
E1
Figure B-10. Logical Entities Representing Ethernet Traffic over E1 Media
M8SL Modules
B-31
entity. The HDLC port can be defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1 port. As seen in the diagram, the
timeslot mapping between the framed E1 and HDLC ports needs to be done via
cross-connect.
A maximum of 32 HDLC ports can be defined on an M8SL module, together with
the three Ethernet ports, meaning an M8SL module supports up to 35 ports. Each
of these ports can be connected to any other Ethernet port within the
Megaplex-4100, such as another HDLC or external Ethernet port on any module
(including GbE ports on CL modules), or a Logical MAC port.
The binding of HDLC/MLPPP to a flow is done by the intermediate Logical MAC
entity.
Termination of Ethernet Traffic over E1-i/T1-i Links of

SDH/SONET
The M8SL Ethernet termination and processing function can also serve Ethernet
traffic carried through E1-i/T1-i links on a CL.2 module operating in the SDH
mode. This processing is done via HDLC protocol.
Inband Management
M8SL supports the transfer of management traffic, inband, for both TDM and
Ethernet applications:
A dedicated management timeslot can be configured on each E1 port

dedicate timeslots.
Inband management can be carried over Ethernet ports and HDLC/MLPPP

ports configured on M8SL, which are included in the management flow
configured by the user (using the dedicated management VLAN configured
for the Megaplex-4100 host).
Management
Setup, control, and diagnostics are performed in the following ways:
via a supervisory port on the Megaplex-4100 CL module using an ASCII

terminal
via a dedicated 10/100BaseT Ethernet port for connection to a management

station
using inband management with dedicated VLAN for managing remote units.
The remote ASMi-52/ASMi-52L modems can be configured and monitored from

the central M8SL card via EOC.
B-32
M8SL Modules
Timing
M8SL modules recover the timing of each received E1 stream, and therefore can
also provide timing reference signals derived from a selected E1 stream for the
nodal Megaplex-4100 timing subsystem. M8SL transmit timing can be locked to
the Megaplex-4100 nodal timing.
Redundancy for Internal E1 Ports

The internal E1 ports of Megaplex-4100 use the TDM group protection
functionality.
The protection group ports can be located either on the same module or on
another module, and can be any of the following types: E1, internal E1 ports of
CL modules, or internal E1 ports of M8SL, OP or ASMi-54C/N modules.
A special TDM Ring protection functionality is used for the ports participating in a
Chapter 5.
Monitoring
Performance statistics for the SHDSL and Ethernet ports may be obtained and
analyzed via the Megaplex-4100 management system.
M8SL modules occupy one I/O slot in the Megaplex-4100 chassis. Typical panels
are shown in Figure B-3.
M8SL Modules
B-33
L
I
N
K
M8SL
M8SL
STATUS
2
1
4
3
6
5
8
7
STATUS
2
1
4
3
6
5
8
7
L
I
N
K
ETH1
ETH2
LINK ACT
S
H
D
S
L
S
H
D
S
L
LASER
CLASS
1
E
T
H
3
TX
RX
RX
TX
E
T
H
2
E
T
H
3
TX
E
T
H
2
E
T
H
1
RX
E
T
H
1
Module with Ethernet Ports

Equipped with SFPs
ACT
LINK
ACT
LINK
ACT
LINK
Module with Copper

Ethernet Ports
The TDM interfacing section, located at the upper part of the panel, includes
8 LINK status indicators (one for each SHDSL port), and one 40-pin SCSI
female connector, designated SHDSL, for connecting to all the SHDSL ports.
The Ethernet interfacing section, located in the lower part of the panel,
includes three Ethernet ports, designated ETH1, ETH2 and ETH3. The ports
are either equipped with SFPs or terminated in RJ-45 connectors.
LED Indicators
SHDSL Indicators
Each port status indicator operates as follows:
B-34
Lights steadily in red when the M8SL port is not synchronized to the remote
unit
Flashes in red during handshaking between the M8SL port and the remote
unit
M8SL Modules
Lights in green when the M8SL port is synchronized to the remote unit
Flashes slowly in green when the corresponding port is operating properly,

but serves as the standby port when link redundancy is enabled
Flashes in red when the corresponding port serves as the standby port, and
detects loss of synchronization
Off when the corresponding port is not connected.
Ethernet Indicators
Each port has its own set of ACT and LINK status indicators, except for the ETH3
port, when equipped with SFP.
ACT (yellow): flashes in accordance with the transmit and/or receive activity
on the corresponding port
LINK (green): lights when the link integrity signal is detected by the
SHDSL Interface
Number of Ports
Interface Type
SHDSL
Compliance
ITU-T Rec. G.991.2
Port Type
Software configurable for all the ports:

STU-C default mode
STU-R selectable only when connecting to
another M8SL installed in a Megaplex-4100
unit
Line Type
Single unloaded, unconditioned copper twisted

pair, 26 AWG or thicker
Nominal Line Impedance
135
Range
See Table B-6
Line Connector
40-pin SCSI female connector convertible to 8

RJ-45 connectors via adaptor cable
M8SL Modules
B-35
Status Indicator per Link
Dual-color indicator:
Lights steadily in red when the Megaplex-4100
port is not synchronized to the remote unit
Flashes in red during handshaking between
the Megaplex-4100 port and the remote unit
Lights in green when the Megaplex-4100 port
is synchronized to the remote unit
Flashes slowly in green when the
corresponding port is operating properly, but
serves as the standby port when link
redundancy is enabled
Flashes in red for a standby port that reports
loss of synchronization
Off when the corresponding port is not
connected
Table B-6 lists typical M8SL ranges over 2-wire 26 AWG pairs versus the
payload data rate. Note that because of the widely varying characteristics of
actual twisted pairs, the actual range on any particular pair may deviate from
the data presented in the table.
Note
For full information on the ASMi-52 modem, refer to the ASMi-52 Installation and
Operation Manual.
Table B-6. Typical Megaplex-4100 Ranges on 26 AWG Pair (2-Wire)
Data Rate
[kbps]
Internal E1 Port
M8SL to M8SL
M8SL to ASMi-52
[km]
[miles]
[km]
[miles]
256
6.1
3.8
6.0
3.7
384
6.0
3.7
5.9
3.7
512
5.8
3.6
5.7
3.5
1024
5.4
3.3
5.1
3.2
1536
5.5
3.4
4.3
2.6
2048
4.9
3.0
4.2
2.6
Type and Bit Rate
E1, 2.048 Mbps
Framing
Basic G.704 framing (G732N)

G.704 framing with timeslot 16 multiframe
(G732S)
B-36
M8SL Modules
Port Timing
STU-C: locked to Megaplex-4100 nodal clock

STU-R: locked to the line signal received from the
STU-C
Ethernet Interfaces Number of Ports
3 ports (either fiber-optic or copper, per customer

order)
Maximum Frame Size
1600 bytes
Data Rate

Fiber Optic Ports
Hot-swappable SFPs

Connectors: LC
Copper Ports
Interface Type:10/100Base-TX
Connectors: Shielded RJ-45
Indicators (Ports ETH1,

ETH2)
Diagnostics
ACT (yellow): flashes in accordance with the

transmit and/or receive activity on the
corresponding port
LINK (green): lights when the link integrity

signal is detected by the corresponding port
External SHDSL Port

Loopbacks
Local loopback on each SHDSL port
Internal E1 Port
Loopbacks
Local loopback per timeslot
Remote loopback on each SHDSL port
Remote loopback per timeslot
Performance
Monitoring
Transmission performance statistics for Ethernet,

SHDSL and E1-i ports
Performance
Monitoring
In accordance with ITU-T Rec. G.991.2, G.826
Power Consumption
13.7W
Configuration

system
M8SL Modules
B-37
Warning
Caution
Caution

The M8SL modules contain components sensitive to electrostatic discharge (ESD).

To prevent ESD damage, always hold the module by its sides, and do not touch
the module components or connectors.

M8SL modules may be installed in an operating chassis (hot insertion).
Note
M8SL software can be updated by downloading from the CL module. Therefore, if

the M8SL module is not yet loaded with the required software version, refer to
Chapter 7 for detailed software downloading instructions.
No preparations are required for M8SL modules with UTP Ethernet ports,
For M8SL modules equipped with Ethernet ports having SFP sockets, it may be
necessary to install or replace SFPs. M8SL modules have three installation
positions for SFPs, designated ETH1, ETH2, and ETH3:
M8SL modules equipped with RAD-supplied SFP plug-in modules comply with laser
product performance standards set by government agencies for Class 1 laser
strongly recommends ordering the M8SL with RAD SFPs, as this permits full
Warning performance testing of the supplied equipment.
B-38
M8SL Modules
M8SL modules are shipped with protective covers installed on all the optical
connectors. Keep the covers for reuse, to reinstall the cover over the optical
connector as soon as the optical cable is disconnected.
SFPs installed on M8SL modules may be equipped with a laser diode. In such
cases, a label with the laser class and other warnings as applicable will be
Warning
For your safety:

Installing an SFP
Warning
Caution
During the installation of an SFP with optical interfaces, make sure that all the
connectors.
Note
To install the SFP:
Note
M8SL Modules
B-39

M8SL module, and from the SFP electrical connector.
Replacing an SFP
To replace an SFP:
4. Install the replacement SFP in accordance with Installing an SFP.
The M8SL module starts operating as soon as it is inserted in an operating

chassis.
Warning
To install an M8SL module:

3. Insert the M8SL module in its chassis slot and slide it in as far as possible.
4. Secure the M8SL module by tightening its two fastening screws.
B-40
M8SL Modules



Each M8SL ETH electrical port has a 10/100BASE-TX Ethernet interface terminated
in an RJ-45 connector. The port supports the MDI/MDIX crossover function, and
therefore it can be connected by any type of cable (straight or crossed) to any
type of 10/100BASE-TX Ethernet port. The port also corrects for polarity reversal
in the 10BASE-T mode.

Pin
Designation
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
Not connected
Not connected
To connect cables to the M8SL electrical Ethernet ports:

ETH3.

Chapter 2.
To connect cables to the M8SL optical Ethernet ports:

Connecting the SHDSL Ports

All the SHDSL ports of the M8SL modules are terminated in a 40-pin SCSI female
connector, designated SHDSL. A CBL-MSL8-SC40/RJ45 cable can be ordered from
M8SL Modules
B-41
RAD for connecting to the module SHDSL interfaces. CBL-MSL8-SC40/RJ45 is 2meter cable, ending in 8 RJ-45 connectors, one for each channel.
and identifies the interface connector pin assignment.
Ch. 1
Ch. 2
Ch. 3
CBL-MSL8-SC40RJ45M
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 8
Figure B-13. CBL-MSL8-SC40/RJ45 Cable

Table B-8. CBL-MSL8-SC40/RJ45 Cable Wiring
Channel
RJ-45
Connector
CH-1
CH-2
CH-3
CH-4
40-Pin SCSI
Connector
Pin
Function
RJ-45
Connector
Pins
22
RX/TX Ring
21
RX/TX Tip
40-Pin SCSI
Connector
Pin
Function
RJ-45
Connector
Pins
10
11
30
RX/TX Ring
29
RX/TX Tip
12
13
24
RX/TX Ring
32
RX/TX Ring
23
RX/TX Tip
31
RX/TX Tip
14
15
26
RX/TX Ring
34
RX/TX Ring
25
RX/TX Tip
33
RX/TX Tip
16
17
28
RX/TX Ring
37
RX/TX Ring
27
RX/TX Tip
36
RX/TX Tip
Channel
RJ-45
Connector
CH-5
CH-6
CH-7
CH-8
M8SL SHDSL connector, and connect the cable to the module as explained below.
B-42
M8SL Modules
To connect the cable to the module:

6. Connect the 26-pin connector of the CBL-MSL8-SC40/RJ45cable to the
module front panel SHDSL connector.
7. Connect the RJ-45 plug of each line (the plugs are marked CH-1 to CH-8) to
the prescribed user equipment or patch panel connector. Insulate unused
connectors, to prevent accidental short-circuiting of their exposed contacts
to metallic surfaces.
Normal Indications
Ethernet Ports
Once the equipment connected to the M8SL Ethernet ports is operational, the
following indications appear for each port:

equipment
SHDSL Ports
The status of each M8SL link is indicated by a separate indicator. During normal
operation, after communication with the remote equipment is established, the
port indicators of the M8SL module lights steadily in green (however, if a port is
configured as the standby port in a redundancy pair, its indicator flashes in
green).
indicator lights in red. The indicator turns green (or flash in green) as soon as the
link with the remote equipment is established.
The indicators of ports not configured at shutdown are off.
Configuring SHDSL Line Parameters
Timeslot 0 termination. As explained in Chapter 5, when using the basic

G.704 framing mode, you can select between local termination of timeslot 0,
and transparent transfer of timeslot 0 contents.
The recommended settings for RAD equipment that can be connected to
M8SL modules are as follows:
ASMi-52 with E1 user port: either transparent or looped back, as required
ASMi-52 without E1 user port, for example, single-channel ASMi-52 with

high-speed data user port, or with LAN port: always looped back
FCD-IP: always transparent.
Contact RAD Technical Support Department for help on other equipment.
M8SL Modules
B-43
SHDSL Modem Parameters

The user must specify the following set of SHDSL modem parameters for each
M8SL STU-C port:
Maximum bandwidth. The SHDSL modem of each port supports payload

(user) rates which are multiples of 64 kbps (n 64 kbps), where n is in the
range of 3 to 32, corresponding to bit rates of 192 to 2048 kbps. The
selected rate is automatically configured on the STU-R, except when the
STU-R is another M8SL module.
The SHDSL modems use the maximum bandwidth to setup a link that
supports the specified rate. Because of the modulation method used by
SHDSL modems, a lower rate enables operation over longer ranges. It also
reduces the power consumption of the M8SL module. The minimum payload
data rate supported by an SHDSL signal, however, is 192 kbps (corresponding
to three timeslots on the SHDSL line), which results, together with the SHDSL
overhead (8 kbps) in a minimum line rate of 200 kbps. Therefore, you cannot
select data rates lower than 192 kbps.
The maximum bandwidth specified by you is used to set up a link capable of
supporting the specified payload rate: if the number of timeslots routed to
the corresponding module port is lower than the maximum rate, any unused
timeslots in the SHDSL signal frame is filled with the idle timeslot code.
When selecting the minimum data rate, make sure to take into consideration
that timeslots may also have to be allocated for one or more of the following
purposes:
End-to-end transfer of timeslot 0 when the selected timeslot 0 mode is

transparent.
End-to-end transfer of the signaling timeslot (timeslot 16) when the

framing mode is G.732S (G.704 multiframe).
Management when inband management is desired.
Therefore, you may need to add up to three timeslots to the number of

timeslots assigned to payload data.
Table B-6 lists typical M8SL ranges over 2-wire 26 AWG pairs versus the
payload data rate. Note that because of the widely varying characteristics of
actual twisted pairs, the actual range on any particular pair may deviate from
the data presented in the table.
Note
For full information on the ASMi-52 modem, refer to the ASMi-52 Installation and
Operation Manual.
B-44
Power backoff. Because of the complex line signal transmitted by SHDSL

modems, it may be desirable to transmit at reduced power, that is, at less
than the maximum signal power allowed in accordance with the standards.
You can instruct the STU-C to use the nominal transmit level, or allow
backoff: in this case, you can select the maximum reduction in 1-dB steps, up
to -31 dB relative to the nominal transmit level.
M8SL Modules
Attenuation threshold. You can enable the generation of an alarm if the

attenuation value measured by the STU-C on the SHDSL link exceeds a certain
value (user-selectable in 1-dB steps up to 127 dB).
SNR margin threshold. You can enable the generation of an alarmif the
signal/noise ratio decreases below a certain value (user-selectable in 1-dB
steps up to 15 dB).
When operating in a link with ASMi-52 modems, the M8SL ports can control
several of the STU-R operational parameters via the eoc:
Note
Remote power backoff. The power backoff can be separately

enabled/disabled for the STU-R.
Remote attenuation threshold. A separate attenuation threshold value can be

selected for the STU-R.
Remote SNR margin threshold. The SNR margin threshold of the ASMi-52 can
be separately selected.
Remote current SNR margin. You can decide whether to specify an SNR
margin for the ASMi-52, and its value. The current SNR margin is specified
relative to the noise level measured during the SHDSL line activation process.
This margin can be set in 1-dB steps, within the range of -10 to +10 dB.
Remote worst case SNR margin. As an alternative to using the current SNR
margin during the line activation process, you can specify a worst-case SNR
margin for the ASMi-52. The worst-case SNR margin is specified relative to
the worst-case crosstalk noise specified in ITU-T Rec. G.991.2. This margin
can be set in 1-dB steps, within the range of -10 to +10 dB.
An M8SL module can operate as STU-R only if the far-end equipment is another
Megaplex (which must include an M8SL module serving as STU-C).

You can configure up to four HDLC ports for each E1-i port, where each port can
be assigned a fraction (number of timeslots) of the port bandwidth. The
maximum number of HDLC ports in an M8SL module is 32.
Moreover, you can select specific timeslots to be assigned to each port. Binding
the HDLC port to specific timeslots of E1-i port is done via the xc command.
The nominal bandwidth assigned to the HDLC port is determined by the number
of timeslots cross-connected with it and must be a multiple of 128 kbps.
The available range is 128 to 2048 kbps (2 to 32 cross-connected timeslots.
Any given port timeslot can be assigned only one use (an HDLC bundle, TDM
traffic, or inband management). Timeslots assigned to HDLC ports are always
data timeslots.
Before setting the HDLC port to no shutdown, make sure that the source E1-ii
ports are also set to no shutdown and bound to this HDLC port, and vice-versa.
When configuring Ethernet termination for E1-iT1-i links on a CL.2 module, it is
possible to open (set to no shutdown ) only 8 E1-i /T1-i links on a CL.2 module
per each M8SL module, and bind up to 4 HDLC ports to each of these links, so
that the total capacity is 32 HDLC ports per M8SL module.
M8SL Modules
B-45
Configuring MLPPP and PPP Ports

Ports using MLPPP (multilink point-to-point protocol) as the Layer 2 protocol are
called MLPPP ports. In this case, one or more unframed E1 ports are logically
bonded together as a single serial port. There is one MLPPP port per M8SL
module.
The MLPPP port can be bound to any number of the links supported by the
module, that is, from 1 to 8. All the links (ports) used by the MLPPP port must
have identical physical layer parameters and their line-type parameter must be
configured as unframed. Therefore, each bonded link adds 2048 kbps to the
available bandwidth.
An MLPPP port has PPP ports bound to it. The binding is done in two stages and
this PPP port needs to be further bound to the physical layer (see Figure B-2).
E1 ports bound (via PPP) to MLPPP ports cannot be part of a protection group.
On the other hand, some redundancy is inherent in the MLPPP protocol, because
if one of the bonded links is out-of-service, the result is only a reduction in the
available transmission bandwidth.
E1 ports bound (via PPP) to MLPPP ports must be cross-connected via tdm
command and configured as unframed.
OOS Signaling
When choosing the OOS signaling option in M8E1/M8T1 modules working in one
chassis with VC modules (see E1 Ports in Chapter 5 for description), take into
account the following:
types.
Configuring TDM Group/Ring Protection for Internal E1 Ports

The operation mode (oper-mode) of the M8SL modules is always configured to
dual-cable-tx. In this mode, each of the two ports in the redundancy pair is
connected through a separate cable to the remote equipment, and both ports
transmit in parallel the same data.
To avoid duplication of configuration parameters, all the internal E1 port
parameters are selectable only for the working port. The parameters of the other
been updated.
E1-i ports bound to MLPPP ports cannot be included in a protection group.
B-46
M8SL Modules

working E1-i port: the assignment is automatically copied to the protection
The list of tasks that can be performed on the M8SL modules and the
configuration context for this task, under which it can be found in Chapter 5. The
Task
Command
Configure an M8SL module and

put it into service
Configure the SHDSL parameters
Selecting an SHDSL Port as System

Timing Reference
config>system>clock>domain(1)#
Configure the internal E1 port

parameters
configure>port>e1-i
Reference
Features Supported by
Megaplex-4100 SHDSL Ports

Ports table
Configure the E1-i port CAS

signaling profile
configure>port>signaling-profile
Configure the Ethernet physical

layer parameters

internal E1 ports (DS0 crossconnect for E1-i ports)
configure>cr>ds0

with M8SL internal E1 ports, see
Cross-Connect Table in Chapter 5


Cross-connecting the full payload

from this e1-i port with another
configuration
configure>cr>tdm
M8SL Modules
B-47
Task
Command
Reference
Mapping E1 to Ethernet via MLPPP

protocol
Bind E1 streams to PPP ports
configure>port>ppp
Configure MLPPP port and bind the

PPP ports to it
configure>port>mlppp
Configure Logical MAC and bind

the MLPPP port to it

between Logical MAC port
Ethernet Port
configure>flows
Mapping E1 to Ethernet port via

HDLC protocol
Configure HDLC port and bind E1
stream to it
configure>port>hdlc
Configure Logical MAC port and

bind to it the HDLC port

between Logical MAC port
Ethernet Port
configure>flows

E1-i ports (DS0 cross-connect for
HDLC ports)
configure>cr>ds0

E1-i links on a CL.2 module (DS0
cross-connect for HDLC ports)
configure>cr>ds0

with M8SL ports, see Cross-Connect
Table in Chapter 5
configure>cr>tdm
Configuring TDM group protection
Configuring TDM ring protection

M8SL diagnostic capabilities include the following:
B-48
Local and remote loopback on each SHDSL port (see SHDSL Ports in Chapter
5).
Local and remote loopback per timeslot on each E1-i port (see E1 Ports in
Chapter 5).
M8SL Modules
In addition, the M8SL module features a remote loopback on remote ASMi-52 or

ASMi-52L unit.
For ports using CAS, the user can also display the CAS information received for
any desired voice timeslot. This expedites the troubleshooting of voice services.
Performance statistics may be obtained and analyzed via the Megaplex
management system:
for SHDSL ports see SHDSL Ports in Chapter 5
for Ethernet ports - see Ethernet Ports in Chapter 5.
B.3
M16E1/M16T1 Modules
The M16E1 and M16T1 modules enable direct connection of Megaplex-4100 to up

to 16 E1 or T1 lines. Up to 10 modules can be installed in a single chassis,
providing Megaplex-4100 with up to 160 E1/T1 ports.
Applications
M16E1/M16T1 modules.
Figure B-14. E1/T1 Access to SDH/SONET Networks
Features
The M16E1 module has 16 E1 (2.048 Mbps) independently configurable external
ports for E1 services. The M16T1 modules has 16 T1 (1.544 Mbps) independently
configurable external ports for T1 services.
M16E1/M16T1 Modules
B-49
E1/T1 Services
and 16 (G.732S) frames per multiframe formats, as well as unframed mode.
CRC-4 and E bit are also supported, in compliance with G.704 recommendations.
Zero suppression over the line is HDB3. The E1 interface is equipped with an
integral user-enabled LTU, ensuring ranges of up to 2 km (1.2 miles).
The T1 interface is compatible with ANSI requirements. It supports both D4 and
ESF framing formats, as well as unframed mode. Zero suppression is selectable
for Transparent, B7ZS, or B8ZS.
be routed to any port with compatible properties.
Timing
M16E1/M16T1 modules recover the timing of each received E1/T1 stream, and
therefore can also provide timing reference signals derived from a selected E1/T1
stream for the nodal Megaplex-4100 timing subsystem. M16E1/M16T1 transmit
timing can be locked to the Megaplex-4100 nodal timing.
Cross-Connections
The M16E1/M16T1 modules support both DS0 and TDM cross-connection,
selectable at the level of the individual E1/T1 port:


Mapping of E1/T1 Links over SDH/SONET

The E1/T1 ports can also be connected to SDH/SONET links, which permits using
the Megaplex-4100 as an SDH/SONET terminal multiplexer (TM). Using the
topologies, enables dropping part of the SDH/SONET link payload at a certain
location, and possibly inserting other payload.
M16E1/M16T1 modules allow direct transparent mapping of unframed E1/T1 links
over SDH/SONET; this feature is also called transparent clocking.
Framed payload can be mapped to SDH/SONET links in two stages: first via DS0
cross-connect to E1-i/T1-i ports of CL.2 modules and then to SDH/SONET
containers.
B-50
M16E1/M16T1 Modules
Inband Management
M16E1/M16T1 supports the transfer of management traffic, inband. A dedicated
management timeslot can be configured on each E1/T1 port operating in a
framed mode. This enables extending the management connections to other RAD
equipment using inband management over dedicate timeslots.
Protection for E1/T1 Links

The E1/T1 ports feature dual-cable protection with parallel transmission, for ports
both on the same module and on different modules. A special TDM ring protection
functionality is used for the ports participating in a ring. For more information,
see TDM Group Protection and TDM Ring Protection in Chapter 5.
The M16E1/M16T1 modules occupy one I/O slot in the Megaplex-4100 chassis.
Typical panels are shown in Figure B-3.
M16E1
M16T1
1-8
1-8
9-16
9-16
M16E1 Module
M16T1 Module
The panel includes two 44-pin D-type female connectors, designated 1-8 and
9-16, for connecting to E1/T1 ports 1 to 8 and 9 to 16, respectively.
M16E1/M16T1 Modules
B-51
E1 Interface
Type and Bit Rate
E1, 2.048 Mbps
Number of Links
16
Line Interface
Coax, 75 unbalanced
HDB3
Standards Compliance

E bit)
Transmit Level


Balanced: 3V (10%)
Unbalanced: 2.37V (10%)
Receive Level
0 to -12 dBm
Jitter Performance
Per ITU-T Rec. G.823
Surge Protection
Per ITU-T Rec. K.21
Connector
44-pin D-type female for each 8 ports. Adapter

(splitter) cables available from RAD
Type and Bit Rate
T1, 1.544 Mbps
Number of Links
16
Line Interface
Line Code
Bipolar AMI
Zero Suppression
Transparent, B7, B8ZS
ANSI T1.107 and T1.403
Framing
B-52
Line Code
Framing
T1 Interface
D4 (SF) per ITU-T Rec. G.704
ESF per ITU-T Rec. G.704
Transmit Level
0.6, 1.2, 1.8, 2.4, 3.0 dBm user-adjustable, measured

at 0 to 655 ft
M16E1/M16T1 Modules
Diagnostics
Receive Level
0 to -12 dBm
Jitter Performance
Per AT&T TR-62411
Surge Protection
Per ITU-T Rec. K.21
Connector
44-pin D-type female for each 8 ports. Adapter

(splitter) cables available from RAD
Loopbacks (per port and

per timeslot)
Local loopback on each module port
Remote loopback on each module port
Power
Consumption
10.4W
Configuration

system

M16E1/M16T1 modules may be installed in an operating chassis (hot insertion).
Note
Warning
Caution
M16E1/M16T1 software can be updated by downloading from the CL module.

Therefore, if the M16E1/M16T1 module is not yet loaded with the required
software version, refer to Chapter 7 for detailed software downloading
instructions.
from the Megaplex enclosure.
The M16E1/M16T1 modules contain components sensitive to electrostatic
discharge (ESD). To prevent ESD damage, always hold the module by its sides,
and do not touch the module components or connectors.
Caution To prevent physical damage to the electronic components assembled on the two
The M16E1/M16T1 module starts operating as soon as it is inserted in an
operating chassis.
Warning
M16E1/M16T1 Modules
B-53
To install a M16E1/M16T1 module:

3. Insert the M16E1/M16T1 module in its chassis slot and slide it in as far as
possible.
4. Secure the M16E1/M16T1 module by tightening its two fastening screws.

Each 8 M16E1/M16T1 ports are terminated in a 44-pin D-type female connector.

balanced E1/T1 interfaces using pins 1, 2 for the receive (RX) pair and pins
4,5 for the transmit (TX) pair

balanced E1/T1 interfaces using pins 4,5 for the receive (RX) pair and pins 1,
2 for the transmit (TX) pair

end, for balanced E1/T1 applications

end, for use when M16E1 modules are connected to equipment with
unbalanced E1 interfaces.
The following sections describe these adapter cables, the functions of the 44-pin
connector pins for each interface type and connection instructions.
The CBL-G703-8/RJ45/ST is a 2-meter cable for M16E1/M16T1 modules using the
balanced interface.
B-54
M16E1/M16T1 Modules

Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL-G703-8/RJ45/ST
Ch. 5
Ch. 6
Ch. 7
Ch. 8
Station
Clock
ST-CLK

assignment.
Channel
RJ-45
44-Pin Connector
Pin
Connector
CH-1
CH-2
CH-3
CH-4
Function
RJ-45
Connector
Channel
Pins
31
RX Ring
17
RX Tip
16
TX Ring
TX Tip
33
32
44-Pin Connector
RJ-45
Pin
Connector
37
Function
RX Ring
RJ-45
Connector
Pins
1
23
RX Tip
22
TX Ring
TX Tip
RX Ring
38
RX Ring
RX Tip
39
RX Tip
TX Ring
CH-5
CH-6
TX Ring
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
19
TX Ring
TX Tip
35
26
RX Tip
25
TX Ring
10
TX Tip
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
24
RX Ring
27
RX Tip
21
TX Ring
18
TX Tip
CH-7
CH-8
ST-CLK
M16E1/M16T1 Modules
B-55
assignment.
Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL- G 703-8/R J45/X
Ch. 5
Ch. 6
Ch. 7
Ch. 8

Channel
RJ-45
Connector
CH-1
CH-2
CH-3
CH-4
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
Channel
RJ-45
Connector
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
4
31
RX Ring
37
RX Ring
17
RX Tip
23
RX Tip
16
TX Ring
22
TX Ring
CH-5
TX Tip
TX Tip
33
RX Ring
38
RX Ring
32
RX Tip
39
RX Tip
TX Ring
TX Ring
CH-6
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
26
RX Tip
19
TX Ring
25
TX Ring
TX Tip
10
TX Tip
35
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
CH-7
CH-8
CBL-G703-8/OPEN/2M cable is a 2-meter cable for M16E1/M16T1 modules using
the balanced E1/T1 interface, terminated in free leads that can be connected to
any terminal block or connector appropriate for your application.
B-56
M16E1/M16T1 Modules
CBL-G703-8/OPEN/2M

44-Pin Connector
Channel
44-Pin Connector
Pair Color
Pin
Function
31
Rx Ring
17
Rx Tip
Tx Tip
Orange
Channel
Pair Color
Pin
Function
White
37
Rx Ring
White
Blue
23
Rx Tip
Brown/Blue
Tx Tip
Grey/Blue
White
16
Tx Ring
White
22
Tx Ring
33
Rx Ring
White
38
Rx Ring
White
32
Rx Tip
Green
39
Rx Tip
White/Orange
Tx Tip
Brown
Tx Tip
Orange/Green
Tx Ring
White
Tx Ring
White
34
Rx Ring
White
40
Rx Ring
White
20
Rx Tip
Grey
26
Rx Tip
Orange/Brown
Tx Tip
White/Blue
10
Tx Tip
Grey/Orange
19
Tx Ring
White
25
Tx Ring
White
35
Rx Ring
White
41
Rx Ring
White
36
Rx Tip
Orange/Blue
42
Rx Tip
White/Green
Tx Tip
Green/Blue
12
Tx Tip
Green/Brown
Tx Ring
White
11
Tx Ring
White
CBL-G703-8/COAX is a 2-meter cable for M16E1 modules using the unbalanced E1
interface. Figure B-35 shows the cable construction.
RX
Ch. 1
TX
RX
Ch. 2
TX
RX
Ch. 3
TX
CBL-G703-8/COAX
RX
Ch. 7
TX
RX
Ch. 8
TX
M16E1/M16T1 Modules
B-57
ground): this enables the M16E1 module to differentiate between the connection
of this cable and the connection of the

Channel Function
RX
1
TX
RX
2
TX
RX
3
TX
44-Pin Connector
BNC
Contact
Pin
Function
31
Ring
29
Frame Ground
17
Tip
Center
Center
Tip
16
Ring
14
Frame Ground
33
Ring
44
Frame Ground
Shield
Tip
Center
Tip
Center
Ring
Frame Ground
34
Ring
29
Frame Ground
Tip
Center
Tip
Center
Ring
Frame Ground
35
Ring
Frame Ground
36
Tip
Center
Tip
Center
Ring
29
Frame Ground
Cable Type Sensing
15
Sense Input,
connected to
pin 30
Signal Ground
30
Ground
Frame Ground
44
Cable Shield
4
TX
6
TX
RX
7
TX
Shield
44
RX
RX
Shield
4
14
TX
Shield
20
19
Shield
3
2
RX
Shield
32
29
Channel Function
Shield
Shield
RX
8
TX
Function
BNC
Contact
37
Ring
Shield
29
Frame Ground
23
Tip
Center
Center
44-Pin Connector
Pin
Tip
22
Ring
14
Frame Ground
38
Ring
44
Frame Ground
Shield
Shield
39
Tip
Center
Tip
Center
Ring
14
Frame Ground
40
Ring
29
Frame Ground
Shield
Shield
26
Tip
Center
10
Tip
Center
25
Ring
14
Frame Ground
Shield
41
Ring
44
Frame Ground
Shield
42
Tip
Center
12
Tip
Center
11
Ring
14
Frame Ground
Shield
Connecting Cables to the E1/T1 Ports

corresponding M16E1/M16T1 connector, and connect the cable to the module as
explained below.

1. Connect the 44-pin connector of the cable to the M16E1/M16T1 front panel
connector.
B-58
M16E1/M16T1 Modules

1. Connect the 44-pin male connector of the cable to the M16E1 front panel
connector.

method.
2. When done, connect the 44-pin male connector of the cable to the
M16E1/M16T1 front panel connector.
Configuring DS0 Cross-Connect (Timeslot Assignment)
When the port uses a framed mode, you must configure the routing of the
individual port timeslots (timeslot assignment). This is done with the help of ds0
cross-connect command. You can assign only timeslots of ports that have already
been configured to no shutdown.

An unframed E1 port can be cross-connected via tdm cross-connect only with
another unframed E1 port on an I/O module supporting transparent mapping
(M16E1, OP-108C, OP-34C, ASMi-54C/N).
An unframed T1 port can be cross-connected via tdm cross-connect only with
another unframed T1 port on an I/O module supporting transparent mapping
(M16T1).
In addition, unframed E1/T1 ports can be cross-connected with direct transparent
mapping over SDH/SONET (sdh-sonet cross-connect), as described in the next
section.
Configuring Transparent Mapping of E1/T1 Links over

SDH/SONET
To configure a direct E1/T1 to SDH/SONET connection:

2. Configure the cross connection as shown in the example below.
M16E1/M16T1 Modules
B-59
M16E1 module:
I/O slot 1
E1 port 2
Mapping E1 port 2 to the following VC-12 container:
VC-12 = 1
TUG-3 = 7
TUG-2 = 1
AUG 1 = 1

cr sdh-sonet vc12-vt2 cl-a/1/1/1/7/1
e1 1/2
Mapping Framed E1/T1 Link Payload to SDH/SONET

Framed E1/T1 links do not allow direct mapping to SDH/SONET. In this case the
mapping is done in two stages: first the E1/T1 port is mapped to an internal
E1/T1 port on the CL.2 module and then the internal E1/T1 port is mapped to the
SDH/SONET.
The following example serves as an illustration.
VC-12 = 2
TUG-3 = 1
TUG-2 = 1
AUG 1 = 1
Selecting an E1/T1 Port as System Timing Reference

After an E1/T1 port is configured and at no shutdown, its receive clock can be
selected as a timing reference for the Megaplex-4100 system.
To modify the system timing reference with the supervision terminal, use the
following commands at the config>system>clock>domain(1)# prompt:
source <src-id> rx-port e1 <slot>/<port>
source <src-id> rx-port t1 <slot>/<port>
For detailed instructions, refer to Chapter 5.
B-60
M16E1/M16T1 Modules
Configuring TDM Group (E1/T1 Port) Protection

The operation mode (oper-mode) of the M16E1/M16T1 modules is always
configured to dual-cable-tx. In this mode, each of the two ports in the protection
group is connected through a separate cable to the remote equipment, and both
ports transmit in parallel the same data.
To avoid duplication of configuration parameters, all the E1/T1 port parameters
are selectable only for the working port. The parameters of the protection port
are automatically copied from the working port after the database has been
updated. However, you can select different interface-type for the working and
protection ports.
When the other port in a redundancy pair is an internal port of a CL.2 module,
only the dual-cable-tx protection mode can be used. CL.2 internal ports may also
use path protection, so this type of protection is not necessary for internal ports
included in another redundancy scheme.
OOS Signaling
When choosing the OOS signaling option in M16E1/M16T1 modules working in
one chassis with VC modules (see E1 Ports or T1 Ports in Chapter 5 for
description), take into account the following:
types.
The list of tasks that can be performed on the M16E1/M16T1modules and the
Task
Configure an M16E1/M16T1
module and put it into service
Reference
M16E1/M16T1 Modules
B-61
Task
Reference
Select an E1/T1 port as system

timing reference

(M16E1)
configure>port>e1

Ports table
Configure the T1 port parameters

(M16T1)
configure>port>t1
T1 Ports in Chapter 5, pay attention

Megaplex-4100 T1 and Internal T1
Ports table

through E1/T1 port
configure>port>e1

for E1/T1 ports)
configure>cr>ds0

with M16E1/M16T1 ports, see


Cross-connect the full payload

from this E1/T1 port with another
configuration
configure>cr>tdm
Cross-connect the unframed E1/T1

port with a vc12-vt2/vc11-vt1.5
from an SDH/SONET port
configure>cr>sdh-sonet
Cross-connect the framed E1/T1

port with a vc12-vt2/vc11-vt1.5
from an SDH/SONET port
configure>cr>ds0
Configure TDM group protection
Configure TDM ring protection
configure>port>t1

Diagnostics
M16E1/M16T1 diagnostic capabilities include local and remote loopback on each
E1/T1 port (see E1 Ports and, respectively, T1 Ports in Chapter 5):
B-62
On the port level
On the timeslot level.
M16E1/M16T1 Modules
Monitoring
The M16E1 modules support the collection of performance diagnostics on E1
ports in accordance with ITU-T G.826, relevant parts. The M16T1 modules support
the collection of performance diagnostics on T1 ports in accordance with ANSI
T1.403. For more information, see E1 Ports and T1 Ports in Chapter 5.
Troubleshooting
Note


to the operation of one of the Megaplex-4100 ports, perform the actions listed
Make sure that no test has been activated on the corresponding

M16E1/M16T1 port. Use the Megaplex-4100 management system to find and
deactivate the active test or loopback.
Activate the local loopback on the corresponding port. If no major alarm

appears on the corresponding local port while the loop is connected, the
Quickly check the link to the remote Megaplex-4100 unit by activating the
remote port loopback at the remote unit. If the link operates properly, no
major alarm appears on the corresponding local port.
network, or with the M16E1/M16T1 modules. Repeat the test after carefully
B.4
MPW-1 Modules

operation of the MPW-1 pseudowire access gateway I/O module for the
Megaplex-4100 Next Generation Multiservice Access Node.
MPW-1 operates as a pseudowire server for TDM traffic (E1, T1, SHDSL, ISDN,
high-speed and low-speed data, voice) received via the internal Megaplex-4100
TDM buses from other I/O modules installed in the same chassis. MPW-1
performs the following tasks:
MPW-1 Modules
B-63
Interfacing to the Megaplex-4100 internal TDM buses (equivalent capacity of

256 timeslots, or eight 2.048 Mbps streams).
Conversion between TDM and pseudowire packet formats. The conversion

parameters are controlled by defining pseudowires (see Chapter 5 for
details), and can be optimized for the specific end-user equipment and the
application requirements.
Forwarding the pseudowire packet streams, either directly to a PSN (through

the MPW-1 external Fast Ethernet ports), or for forwarding over any bridge
port within the Megaplex-4100. Each pseudowire can be forwarded to the
endpoint through the packet-switched network. Both UDP/IP and MPLS/ETH
networks are supported. The user can also specify forwarding and
priority/quality of service parameters.
In addition, MPW-1 external Fast Ethernet ports can also be used to carry
Ethernet traffic, like Ethernet ports on other I/O modules (M8E1, M8T1, OP-108C,
etc.).
Installing a MPW-1 module enhances Megaplex-4100 capabilities and services by
enabling the transport of legacy TDM traffic from other modules over Ethernet,
IP, and MPLS packet-switched networks (PSNs). MPW-1 supports the TDMoIP,
CESoPSN, SAToP and HDLCoPSN pseudowire protocols.
Product Options
MPW-1 is offered in two models with similar properties, which differ only in the
type of interfaces supported by the external Fast Ethernet ports:
MPW-1/UTP: has three 10/100BASE-TX interfaces terminated in RJ-45

connectors
MPW-1/SFP: has three sockets for Fast Ethernet SFP optical transceivers. RAD
offers several types of SFPs capable of meeting a wide range of operational
requirements.
Applications
Forwarding Traffic via Local Fast Ethernet Ports
A typical basic application is shown in Figure B-20. In this application, the legacy
traffic from TDM I/O modules intended for transport over the PSN is connected to
the MPW-1 internal DS1 ports, using a cross-connect (DS0 or TDM). The traffic is
then packetized to create data streams in accordance with a pseudowire protocol
(TDMoIP, CESoPSN, SAToP, or HDLCoPSN), independently selectable for each
pseudowire. The resulting data streams are sent via the external Fast Ethernet
ports of the module, for routing to the destinations, where each stream is
converted back to the original TDM stream.
B-64
MPW-1 Modules
Figure B-20. Basic MPW-1 Application using Local Fast Ethernet Ports
Forwarding Traffic via GbE Ports

Packetized traffic can also be sent via any bridge port on any module installed in
the chassis. In a typical application shown in Figure B-14, pseudowires are routed
to the PSN through the GbE ports located on the CL.2 module (this capability is in
addition to the local Fast Ethernet ports).
Figure B-21. Basic MPW-1 Application using GbE Ports

The application shown in Figure B-14 also permits users connected to MPW-1
metropolitan Ethernet networks, via the Megaplex-4100 GbE links.
In the application shown in Figure B-22, Megaplex-4100 located at Site B does
not have direct access to the PSN; therefore, pseudowire traffic generated by
MPW-1 modules at Site B is directed, by internal flows within the Megaplex-4100,
to ASMi-54C SHDSL.bis I/O modules, which transport the traffic over SHDSL.bis
lines to a DSLAM located at the point-of-presence (PoP). The PSN provides the
connection to the GbE ports of the Megaplex-4100 at Site A, where MPW-1
modules convert the packetized traffic back to legacy TDM traffic.
Figure B-22. MPW-1 Application Using Ethernet over DSL

E1 or T1 traffic received via STM-1/STM-4/OC-3/OC-12 links can be also directed
to the MPW-1 modules for processing and transport over PSN.
Another option, illustrated at Site A in Figure B-23, is applicable for
Megaplex-4100 connected to STM-1/STM-4/OC-3/OC-12 infrastructure, but not to
MPW-1 Modules
B-65
the PSN infrastructure: TDM services are converted to packet traffic at Site A and
transferred over SDH/SONET using virtual concatenation. The bandwidth is
specified by configuring a virtually concatenated group (VCG) using the
appropriate type and number of VCs/VTs, and availability can be enhanced by
configuring LCAS. At a particular location in the SDH/SONET network, the virtually
concatenated group is terminated by a RAD Interface Converter, RICi-155GE, and
converted to Ethernet for transmission over the PSN to Site B, where another
Megaplex-4100 with MPW-1 converts the packetized traffic back to legacy TDM
traffic.
Figure B-23. Legacy and Ethernet Services over SDH/SONET and Packet Switched Networks
Features
MPW-1 is a pseudowire server I/O module that provides TDM pseudowire access
gateway services over packet-switched networks (Ethernet, IP, and MPLS) for
TDM traffic (E1, T1, SHDSL, ISDN, high-speed and low-speed data, voice) received
via the Megaplex-4100 TDM buses from other modules. The MPW-1 module has
eight independently-configurable internal DS1 ports, each capable of handling
32 timeslots, for a total processing capacity of 256 timeslots (the equivalent of 8
E1, or 2.048 Mbps, streams). Multiple MPW-1 modules can be installed in the
Megaplex-4100 chassis, in accordance with the required pseudowire transport
capacity.
Pseudowire Services
The MPW-1 module provides pseudowire emulation services over packet-switched
networks using the following user-configurable protocols:

accordance with RFC5087 and ITU-T Rec. Y.1413


with RFC5086
The pseudowire services enable converting TDM payload to packets and

transferring these packets through router interfaces defined in the
Megaplex-4100.
MPW-1 meets the requirements for edge-to-edge simulation of TDM circuits over
PSN in accordance with RFC4197, including high-performance adaptive timing
B-66
MPW-1 Modules
recovery capabilities. Pseudowires of all types, except HDLCoPSN, can be selected

as timing sources for the Megaplex-4100 nodal timing subsystem.
The number of pseudowires supported by each MPW-1 internal DS1 port depends
on the payload framing mode:
Each framed internal DS1 port can be served by up to 16 pseudowires, where

each pseudowire can be separately routed to its destination over the PSN,
for a total of 128 destinations per module. The total number of pseudowires
is up to 640 per Megaplex-4100 chassis.
The actual number of active pseudowires depends on internal DS1 port
timeslot assignment (a timeslot can be included in a single pseudowire). An
internal cross-connect matrix, similar in capabilities to the cross-connect
matrices in other I/O modules, provides full control over timeslot routing from
any TDM port within the Megaplex-4100 to a particular pseudowire,
independently for each port, using either DS0 or DS1 cross-connect mode.
An unframed E1 or T1 port is served by a single pseudowire; in this case, only

the TDM cross-connect mode can be used.
Each pseudowire terminated on the MPW-1 can be independently configured to

handle a particular type of traffic:
Transparent transfer of data (unframed E1 streams) using TDMoPSN, or

SAToPSN
Transfer of framed E1 and T1 streams, using TDMoPSN and CESoPSN.

To support voice payload, the signaling information can also be transported.
Note that when using CESoPSN, any timeslots carrying signaling information
(either channel-associated signaling (CAS) or common-channel signaling (CCS)
such as Signaling Scheme 7 (SS7), ISDN PRI signaling, etc.) can be
transparently transferred within the pseudowire, as regular data timeslots.
Fractional E1 and T1 services, with or without CAS, are supported by means

of TDMoPSN. Without CAS, CESoPSN can also be used.
HDLC traffic can be carried over framed and unframed E1 and T1 using
HDLCoPSN. This enables efficient and transparent transfer of Frame Relay
traffic.
Packet structure is independently selectable for each pseudowire, for

compatibility with the various pseudowire protocols (TDMoPSN, CESoPSN,
HDLCoPSN, SAToPSN) and the PSN type (UDP/IP or MPLS/ETH). For maximum
flexibility in system applications, the framing format of the pseudowire device at
the destination (referred to as a pseudowire peer) can also be taken into
account. Thus, in many cases traffic using the E1 standards can be directed at
destinations using the T1 standards, and vice versa.
The pseudowire exit port toward the PSN is also selectable, either via one of the
MPW-1 Ethernet ports, or via any other bridge port (GbE, Fast Ethernet, or VCG)
of any module installed in the chassis. The selectable exit ports are bound (via SVI
ports) to router interfaces, where each router interface has its own IP source
address and, optionally, its own VLAN. Each MPW-1 module supports up to 6
interfaces, CL.2 modules support unlimited number of interfaces. However, the
maximum number of router interfaces per Megaplex-4100 is 100. The user can
also specify static routes to control the IP routing.
MPW-1 Modules
B-67
Ethernet Services
full VLAN support.
The external Ethernet ports can be ordered with two types of interfaces:
10/100BaseTx interfaces terminated in RJ-45 connectors
Sockets for Fast Ethernet SFP transceivers. RAD offers several types of SFPs
(SFPs with copper interfaces are also available).
The interface supports autonegotiation for plug-and-play Ethernet connectivity.
Ethernet Termination and Processing

The Ethernet termination and processing function provides an interface between
the Ethernet switching subsystem and the local TDM cross-connect matrix. In the
transmit direction, the payload received from TDM media is packetized and
inserted in Ethernet frames for transmission to the appropriate Ethernet port.
The reverse operation is performed for the incoming Ethernet frames.
MPW-1 implements IEEE 802.1Q standards to provide VLAN-tagging with levels of
prioritization, enabling carriers to offer differentiated Ethernet services. VLAN
tagging can also be employed to separate traffic, ensuring transparency of the
customer traffic and bolstering security of management traffic.
The Ethernet switch serves both traffic and management. Traffic is supported by
means of the 3 external Ethernet ports of the module and by internal ports
connected to the pseudowire engine. Management is supported by a dedicated
port internally connected to the MPW-1 management subsystem, and by another
Fast Ethernet port connected to the management handling section of the CL
modules installed in the Megaplex-4100 (this section is available on all CL
modules).
The internal Ethernet switching subsystem enables forwarding traffic between
the MPW-1 external Ethernet ports and the pseudowire engine to any other
bridge port in the Megaplex-4100, using both the unaware and aware modes in
accordance with application requirements.
Each Ethernet physical port can also serve as a bridge port. Each of these bridge
ports can be connected to any other bridge port within the Megaplex-4100, such
as another PW or Ethernet port on any module (including GbE ports on CL
modules), or to a virtually concatenated group (VCG).
defining flows.
The customers edge traffic accepted by MPW-1 Ethernet ports is directed to
B-68
GbE ports located on the CL.2 modules (ethernet or lag )
MPW-1 Modules


Cross-Connections
The MPW-1 modules support DS0, TDM and PW-TDM cross-connections,
selectable at the level of the individual DS1 port:

cross-connect enables connecting payload between DS1 and other type of
ports.
tdm cross-connect used when necessary to transparently transfer the

entire stream to a selected destination port using the unframed mode.
pw-tdm cross-connect used when necessary to control the routing of

individual timeslots between the PW and the DS1 port.
Pseudowire QoS/CoS
To enable optimal handling of pseudowire traffic within the PSN, the following
parameters can be configured:
For Ethernet transport networks: outgoing pseudowire packets are assigned

to a dedicated VLAN ID according to 802.1Q and marked for priority using
802.1p bits.
For IP transport networks: outgoing pseudowire packets are marked for

priority using DSCP, ToS, or Diffserv bits. This allows TDMoIP packets to be
given the highest priority in IP networks.
For MPLS transport networks: outgoing pseudowire packets are assigned to a

specific MPLS tunnel, and marked for priority using the EXP bits.
The proper balance between the PSN throughput and delay is achieved via
configurable packet size. A jitter buffer with selectable size compensates for
packet delay variation (jitter) of up to 200 msec in the network.
OAM
RADs TDM PW OAM mechanism verifies connectivity and prevents pseudowire
configuration mismatch.
MPW-1 Modules
B-69
Timing
MPW-1 can operate in three timing modes:
Internal mode: The Megaplex internal oscillator is the source for the timing
used by Ethernet links and other I/O modules. MPW-1 is the sole clock source
for all the units in the network.
External mode: one of the I/O modules is the source for the system timing.
Adaptive mode (recovered clock): the MPW-1 timing clocks are regenerated
using the adaptive method, according to the monitored received packet rate
from the IP network. The timing is then also passed on to the I/O modules.
End-to-end synchronization between circuits is maintained by deploying
advanced clock recovery mechanisms.
The system clock ensures a single clock source for all TDM links. For description
of adapting timing, refer to Functional Description under Pseudowires in Chapter
5.
Management
The MPW-1 module operating parameters are determined by commands received
from the Megaplex-4100 CL module. The CL module can also download new
software to the module, when the Megaplex-4100 software is updated.
Via a supervisory port on the Megaplex-4100 CL module using an ASCII

terminal
Via a dedicated 10/100BaseT Ethernet port for connection to a management

station
Using inband management with dedicated VLAN for managing remote units.
Protection
The MPW-1 module provides redundancy protection between internal DS1 ports,
and between an internal DS1 port and a user-selected legacy TDM port (E1, T1,
SHDSL, E1-i/T1-i, etc.) with redundancy. Therefore, the pseudowire traffic is also
protected by the redundancy function. The pseudowire redundancy mode
depends on the use of OAM:
When OAM is disabled, the pseudowire redundancy mode is 1+1, meaning

that the traffic is also sent on the standby pseudowire
When OAM is enabled, the pseudowire redundancy mode is 1:1, meaning that
only OAM packets are sent on the standby pseudowire. This minimizes packet
traffic when a pseudowire it is not active due to the redundancy mechanism.
Figure B-24 shows a topology which protects TDM traffic carried over PSN against
failures in MPW-1 hardware, and in the transmission paths over PSN.
To minimize traffic when a pseudowire it is not active due to the redundancy
mechanism, the pseudowire transmits only OAM packets to ensure connectivity.
B-70
MPW-1 Modules
Note
When pseudowires are configured on redundant internal DS1 ports, the

pseudowire traffic is automatically protected as well. The pseudowire redundancy
mode depends on the use of OAM:
When OAM is disabled, the resulting pseudowire redundancy mode is 1+1,
meaning that the traffic is sent on both the working and standby pseudowires
When OAM is enabled, the resulting pseudowire redundancy mode is 1:1,
meaning that traffic is sent only on the working pseudowire, and only OAM
packets are sent on the standby pseudowire.
West
East
Figure B-24. MPW-1 Redundancy Hardware and Transmission Path Protection via PSN
Redundancy via PSN only

To illustrate the flexibility of the redundancy schemes available for the MPW-1,
hardware redundancy is used only at the West side:
Note
At the West side, two MPW-1 are used, and the redundancy is configured on
internal DS1 ports located on different MPW-1 modules
The East side uses a single MPW-1, and therefore supports only transmission
path redundancy. For this mode, redundancy is configured on internal DS1
ports located on the same MPW-1.
To enable hardware redundancy at the East side, it is necessary to install two

MPW-1 modules, same as at the West side.
When MPW-1 external Fast Ethernet ports are directly connected to the PSN, true
hardware redundancy is always possible. When MPW-1 connection to the PSN is
provided through bridge ports on other modules, true hardware redundancy is
available only when redundancy is also enabled on the other modules. For
example, when the connection is made via the GbE ports of CL .2 modules,
redundancy for the CL.2 PSN interface must also be enabled.
For each redundancy pair, you must first configure the internal DS1 port that will
serve as the primary port; the configuration prepared for the primary internal DS1
port is copied to the other port of the pair. In addition, it is necessary to
configure pseudowires from each internal DS1 port in the redundancy pair to the
desired destinations. Make sure to enable OAM, which is essential to proper
operation of the redundancy feature.
The pseudowires serving the standby (offline) internal DS1 port carry only OAM
packets, which require relatively little bandwidth. When a problem causes
MPW-1 Modules
B-71
switching to standby, the traffic is switched to the standby pseudowires, and the
offline pseudowires attempt to transmit OAM packets.
Redundancy switching (flipping) is always revertive; after the failure is corrected,
the primary port becomes again the active port.
Upon turn-on, the first port to enter normal operation is selected as the active
(online) port of the pair. Thus, if this port is not the primary port, when the
primary port starts normal operation flipping occurs and the primary port is
selected as the active port.
Redundancy via PSN and TDM (E1) Networks

The dual-cable, parallel transmission redundancy mode supported by MPW-1
enables protecting traffic over different media. Therefore, a MPW-1 internal DS1
port can be the redundancy partner of an E1 or E1-i port on another I/O,
respectively CL, module. This could be used in two ways, depending on the
application requirements:
To add protection for selected E1 links when no TDM transport capacity can
be assigned for redundancy, MPW-1 modules may be used to provide the
protection over the PSN. For this purpose, the E1 port to be protected is
configured as the primary port, and an internal DS1 port of a MPW-1 is
assigned and configured as the protection (offline) port. This ensures that
unless a fault occurs, the transmission quality is that available over TDM links,
and very little bandwidth is consumed on the PSN.
When some TDM transport capacity is available, it is possible to add

protection for critical traffic carried by means of MPW-1 modules over the
PSN, without using the same media (PSN) for protection. In this case, MPW-1
internal DS1 ports are configured as the primary ports, and E1 ports are
configured as the protection ports.
Fault Propagation
MPW-1 modules perform fault propagation for pseudowires. If a problem is
detected on a pseudowire, the attached physical port receives a fault indication
and vice versa.
Diagnostics
The module supports comprehensive diagnostics, including local and remote
loopbacks per selected timeslots on each internal DS1 port. Front-panel
indicators show at a glance the status of Ethernet module ports.
Monitoring
MPW-1 also supports a wide range of performance monitoring statistics to enable
analyzing transmission problems and optimizing PSN transmission performance.
Performance statistics for the Ethernet and PW ports may be obtained and
analyzed via the Megaplex-4100 management system. LAN and IP layer network
condition statistics, such as packet loss and packet delay variation (jitter), are
monitored and stored by the device. Performance is monitored by storing
Ethernet and IP-layer network condition statistics, such as packet sequence
errors (loss or misorder) and packet delay variation (jitter).
B-72
MPW-1 Modules
The MPW-1 module occupies one I/O slot in the Megaplex-4100 chassis. Typical
panels are shown in Figure B-3.
MPW-1
MPW-1
LINK ACT
ETH1
ETH2
LASER
CLASS
1
E
T
H
1
RX
TX
E
T
H
1
E
T
H
2
RX
TX
E
T
H
2
E
T
H
3
RX
TX
E
T
H
3
Module with Ethernet Ports Equipped with SFPs
ACT
LINK
ACT
LINK
ACT
LINK
Module with Copper Ethernet Ports
Figure B-25. Typical Module Panels

The MPW-1 panel includes three Ethernet ports, designated ETH1, ETH2 and
ETH3. The ports are either equipped with SFPs or terminated in RJ-45 connectors.
LED Indicators
Each port has its own set of ACT and LINK status indicators, except for the ETH3
port, when equipped with SFP.
ACT (yellow): On or blinking in accordance with the transmit and/or receive

activity on the corresponding port:
On for UTP ports
Blinking for SFP ports
MPW-1 Modules
B-73
LINK (green): On when the link integrity signal is detected by the

General
Function
TDM pseudowire access gateway with internal ports
Internal TDM Ports
8 internal DS1 ports, with 32 timeslots per port

(256 timeslots total, equivalent to 82.048 Mbps)
External Packet
Ports
Three 10/100 Mbps ports
Number of
Pseudowires
Pseudowire
Protocols
Packet Switched
Network Types
Jitter Buffer Size
Clock Modes
Payload Routing Packet Routing
B-74
MPW-1 Modules
Up to 16 active pseudowires per Internal DS1 port
Up to 128 pseudowires per MPW-1
Up to 640 pseudowires per Megaplex-4100
TDMoIP in accordance with RFC5087
TDMoMPLS in accordance with RFC5087 and ITU-T

Rec. Y.1413
HDLCoPSN in accordance with RFC5087 and RFC4618

CESoPSN in accordance with RFC5086
SAToPSN in accordance with RFC4553
UDP over IP
MPLS over ETH
User-configurable per pseudowire:
Unframed mode: 0.5 to 200 msec, with 1-sec

granularity
Framed modes: 2.5 to 200 msec, with 1-sec

granularity
Based on Megaplex-4100 nodal timing
Independent adaptive clock recovery mechanisms per

pseudowire, recovered clock can serve as
Megaplex-4100 nodal timing clock source
Static routing (up to 100 static routes per

Megaplex-4100)
Up to 6 router interfaces per MPW-1, and up to 100

router interfaces per Megaplex-4100 (each router
interface has its own source IP address)
Up to 100 pseudowire destinations (peers) per

Megaplex-4100
Exit Ports
Ethernet
Interfaces
User-defined internal routing (any packet processor

to any external Fast Ethernet port), and connection
parameters (each pseudowire to any destination)
In accordance with user-defined flows, to any bridge

port in Megaplex-4100
Number of Ports
Three 10/100 Mbps ports (either fiber-optic or copper, per

customer order)
Data Rate and

Mode
10 or 100 Mbps, half- or full-duplex, selected by

auto-negotiation or configured by the user
Maximum Frame
Size
1440 bytes
Fiber Optic Ports
Hot-swappable SFPs
Note: For detailed specifications of the SFP transceivers,

see RAD SFP Transceivers data sheet.
Copper Ports
10/100Base-TX
Shielded RJ-45
Note: RJ-45 copper interfaces are also available for

MPW-1 with SFP sockets (RAD SFP model SFP-9F)
Indicators (per
Ethernet port)
ACT (yellow): On or blinking in accordance with the

transmit and/or receive activity on the corresponding
port:
On for UTP ports
Blinking for SFP ports
LINK (green): On when the link integrity signal is

detected by the corresponding port (normal operating
condition)
Note: ETH3 port, when equipped with SFP, has no

indicators.
Diagnostics
User-Controlled
Port Loopbacks
Local loopback per selected timeslots on each internal

DS1 port
Remote loopback per selected timeslots on each

internal DS1 port
Power
Consumption
8.5W
Configuration
Programmable via Megaplex-4100 management system
MPW-1 Modules
B-75
Warning
Caution
Caution

The MPW-1 modules contain components sensitive to electrostatic discharge


MPW-1 modules may be installed in an operating chassis (hot insertion).
Note
MPW-1 software can be updated by downloading from the CL module. Therefore,

if the MPW-1 module is not yet loaded with the required software version, refer
to Chapter 7 for detailed software downloading instructions.
No preparations are required for MPW-1 modules with UTP Ethernet ports,
For MPW-1 modules equipped with Ethernet ports having SFP sockets, it may be
necessary to install or replace SFPs. MPW-1 modules have 3 installation positions
for SFPs, designated ETH1, ETH2 and ETH3:
MPW-1 modules equipped with RAD-supplied SFP plug-in modules comply with
laser product performance standards set by government agencies for Class 1 laser
strongly recommends ordering the MPW-1 with RAD SFPs, as this permits full
B-76
MPW-1 Modules
MPW-1 modules are shipped with protective covers installed on all the optical
SFPs installed on MPW-1 modules may be equipped with a laser diode. In such
Warning
For your safety:

Installing an SFP
Warning
Caution
connectors.
Note
To install the SFP:
Note
MPW-1 Modules
B-77

MPW-1 module, and from the SFP electrical connector.
Replacing an SFP
SFPs, only the traffic on the affected ETH link is disrupted (the other ETH links
can continue to carry traffic).
To replace an SFP:
The MPW-1 module starts operating as soon as it is inserted in an operating

chassis.
Warning
To install an MPW-1 module:

3. Insert the module in its chassis slot and slide it in as far as possible.
4. Secure the module by tightening its two fastening screws.
B-78
MPW-1 Modules



Each Megaplex-4100 electrical ETH port has a 10/100BASE-TX Ethernet interface

Pin
Designation
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
Not connected
Not connected
To connect cables to the MPW-1 electrical Ethernet ports:

ETH3.

Chapter 2 of the Megaplex-4100 Installation and Operation Manual.
To connect cables to the optical Ethernet ports:

Normal Indications
Once the equipment connected to the module Ethernet ports is operational, the
following indications appear for each active port:
MPW-1 Modules
B-79

equipment
Adding and Configuring Pseudowires
To be able to create a PW, first make sure that all the TDM external and internal
ports, as well as the network ports that will carry the pseudowire and participate
in its processing, have already been configured and defined as no shutdown.
The configuration of a PW includes the following main activities:
1. Select the PW structure: the structure is determined by the connection mode
and PSN type.
2.
Configure the PW parameters corresponding to the selected structure.
During PW configuration, you can also choose whether to activate the PW

configuration data, or just save it in the database without the PW being used by
any module (as long as it is in shutdown state).
When you try to save the PW configuration, the MPW-1 automatically checks its
parameters to verify that the PW appears to be correctly defined, without
configuration conflicts or obvious errors such as incorrect IP addresses, etc. Any
errors are reported; they must be corrected for the PW to be saved.
Note
Once a PW is active, do not change its parameters, or the parameters of the

ports and subsystems handling the PW. Delete the PW defined on a module
before that module is removed from the Megaplex-4100.
Do not delete a PW while it is active (no shutdown); first change its state to
shutdown.
Configuring Pseudowire Routing

Pay attention to the following points:
Pseudowires configured on different MPW-1 modules must be configured

with different peers, even if the destination address is the same.
Different peers must not have the same destination IP address and the same
next hop IP address (at least one of these parameters must be different).
Therefore, if it necessary for several pseudowires to reach the same IP
address, create separate router interfaces.
To help you design the routing information, Figure B-27 summarizes the process
used to select the router interface for each pseudowire peer. The priority of the
various router interfaces, as determined by the routing process, is as follows:
1. If the peer IP address is in the subnet of a router interface, that interface will
always be used.
2. If the peer IP address is not within a router interface subnet, then the router
checks if the specified peer next hop address is within the subnet of a router
B-80
MPW-1 Modules
interface. If such a router interface is found, it is selected to serve as the

pseudowire exit port.
3. If neither of the previous conditions is fulfilled, the router checks if the
specified peer next hop address is specified in a static route that is within the
subnet of a router interface.
4. The last priority is to use the router interface that is within the default
gateway subnet.
DB Update
No
No
No
Look in static routes

table, for peer Next Hop in
the subnet of one
of the router interfaces
Peer Next Hop

in the subnet
of one of the
router interfaces
Peer IP address
in the subnet
of one of the
router interfaces
Yes
Yes
Yes
Find a router interface in

the default gateway
subnet
Select as the router interface in use
Figure B-27. Selecting the Active Router Interface for an Ethernet Flow Serving a Pseudowire
Bandwidth Utilization Considerations

When selecting parameters for a new pseudowire, one of the critical parameters
is the payload size, which is determined by the number of TDM bytes per packet.
This parameter affects several important performance aspects:
Bandwidth utilization: because of the relatively short payload (especially

relevant for TDMoPSN and HDLCoPSN), the bandwidth utilization efficiency
MPW-1 Modules
B-81
depends on the overhead that must be transmitted to the network in order

to support the transmission of a certain amount of payload.
The overhead depends on the packet structure: for example, for UDP/IP
networks the overhead is 50 bytes when using VLANs, and 46 bytes
without VLANs
The payload depends on the number of TDM bytes, and varies between
48 to 1440 bytes.
For example, when using the minimum payload size (48 bytes), bandwidth
utilization efficiency is around 50%.
Packetizing delay and the associated delay variance. Bandwidth utilization

efficiency increases when using a large payload size per frame. However,
some additional aspects must be considered when selecting the size of the
packet payload:
Packetization time: the packet filling time, which is the time needed to
load the payload into an Ethernet frame, increases in direct proportion to
the number of bytes in the packet payload. This is particularly significant
for pseudowires with few timeslots; for example, a voice channel could be
carried by a single-timeslot pseudowire. Considering the nominal filling
rate (approximately one byte every 0.125 msec), the time needed to fill a
single-timeslot TDMoPSN pseudowire is as follows:
At 48 TDM bytes per frame: 5.5 msec when signaling is transferred,

and 5.9 msec without signaling
At 384 TDM bytes per frame: 44 msec when signaling is transferred,
and 47 msec without signaling
Therefore, for pseudowires with a few timeslots, it is recommended to

use the minimum payload size (48 bytes).
In general, the TDMoPSN packetization delay is calculated with the
following formula:
Packetization delay (ms) =
47 N 0.125
TS
where N is the selected multiplier, 1 to 30:

N=
TDM bytes/fram e
48
and TS is the number of assigned timeslots.

Therefore, before considering any other delays encountered along the
end-to-end transmission path, the round-trip (or echo) delay for the
voice channel example presented above is 92 msec at 384 TDM bytes per
frame (including the additional intrinsic delay of module see below).
Such long delays may also cause time-out in certain data transmission
protocols.
B-82
MPW-1 Modules
Intrinsic jitter: the transmission of packets to the network is performed at

nominally equal intervals (usually, the interval is 1 msec). This means that
every 1 msec the packet processor sends to the network all the frames
ready for transmission. As a result, the actual payload transmission
intervals vary in an apparently random way whose peak value depends on

the pseudowire size, an effect called delay variance (or jitter).
For example, a pseudowire with 6 timeslots will fill a 48-byte payload field
of an Ethernet frame every 1 msec. If the sending instants are not
perfectly synchronized with the filling instants, the sending time will
sometimes occur just in time and sometimes will be delayed by 1 msec
relative to the ideal, creating a peak delay variance of 1 msec at the
transmitting side.
The intrinsic jitter in other cases is lower, therefore the delay variance
generated by the MPW-1 modules will not exceed 2 msec.
Round-trip delay. The round-trip delay for the voice path, in milliseconds, is
calculated as follows:
2 [Packetization Delay + Jitter Buffer Size + 1] + PSN Round Trip Delay
The actual value is within 2 msec of the calculated value.
Sometimes, it is necessary to evaluate the transmission bandwidth required on

the PSN, which also depends on the number of TDM bytes. Use the following
formula:
Bandwidth (bps) = [(Frame Overhead (bytes) + TDM Bytes/Frame) 8] Frames/Second
The frame overhead and the number of TDM bytes per frame have already been
presented; the additional parameter is the number of frames per second, which
assumes the following values:
Unframed E1 stream: 5447/N, where N is the multiplier of 48 bytes specified

when selecting the number of TDM bytes per frame
Framed E1 stream: 8000 k/47N, where k is the number of timeslots

assigned to the pseudowire.
Determining UDP Port Numbers Used by Pseudowires

For UDP/IP networks, the pseudowire label determines the source UDP port of a
pseudowire (at the other endpoint of the pseudowire, this port number must
then be inserted as the destination port). The method used to assign the source
UDP port is as follows (unless explicitly stated otherwise, all the numbers are in
hexadecimal notation):
For TDMoIP CE pseudowires using packet payload Version V1:

During normal operation, the source UDP port is given by:
UDP Source Port = Pseudowire Label + 1

This means that during normal operation, the UDP ports numbers are in the
range of 0 to 8191 decimal.
While the pseudowire is in the local fail state, the source UDP port changes
to:

This means that in the local fail state, the UDP ports numbers are higher than
8000 hexa (32768 decimal).
For TDMoIP CE pseudowires using packet payload Version V2:
MPW-1 Modules
B-83

This means that for TDMoIP CE pseudowires, all the UDP ports numbers are
higher than 2000 hexa (8192 decimal). This also applies to HDLCoPSN.
When application requirements cause the MPW-1 module to send to the same
peer (destination IP address) packets using both payload version V1 and
payload version V2, there is a potential for conflict. For example:
When you assign a certain label (for example, Out PW Label is set to 100)
to a pseudowire using payload Version V1, the source UDP port is 101
Now, you cannot assign the next label (Out PW Label of 101 in this
example) to a pseudowire using payload Version V2, because the resulting
source UDP port is also 101
Thus it is always necessary to skip (never use) the pseudowire label next to
the label assigned to a pseudowire using payload Version V1, if the next
pseudowire uses payload Version V2.
For CESoPSN and SAToPSN pseudowires using packet payload Version V2:
UDP Source Port = Pseudowire Number + C000

This means that all the UDP ports numbers are higher than C000 hexa (49152
decimal).
Selection Guidelines for TDM Payload Bytes per Frame

The TDMoIP technology enables transmitting the continuous data stream
generated by TDM equipment as a stream of discrete packets, having a structure
suitable for transmission over packet-switched networks. This process is called
packetizing (see Appendix C for a concise description of this process, and of the
reverse process used to reconstruct the TDM data stream).
As part of this process, the continuous TDM data stream is sliced in accordance
with the TDM Byte per Frame parameter, and 44 bytes of overhead are added to
create a TDMoIP packet (additional overhead is latter added to form frames for
transmission over Ethernet).
The number of TDM bytes inserted in each packet affects two important
performance parameters:
B-84
Bandwidth utilization efficiency. The smaller the number of TDM bytes per
packet, the lower the efficiency. The overhead can be a significant fraction of
the total packet when the TDM Byte per Frame parameter is small. The worst
efficiency occurs at the minimum packet size, 48 bytes of payload versus 44
bytes of overhead.
Packetizing delay and the associated delay variance. Considering that any
given TDM byte is received only once in every TDM frame, the rate at which
TDM bytes are received for filling packets is 8000 bytes per timeslot per
second. Since a packet will be sent only after its payload field has been filled,
the maximum possible filling rate occurs for PWs carrying 32 timeslots
(unframed mode) and a payload of 48 bytes per frame: in this case, the filling
of the 48 bytes takes 1.5 internal TDM frames (with CAS signaling, the
maximum number of timeslots decreases to 30).
MPW-1 Modules
However, the filling time increases significantly for PWs with few timeslots;
for example, a voice channel could be carried by a single-timeslot PW.
Considering the nominal filling rate (approximately one byte every
0.125 msec), the filling time can easily become very significant. As a
worst-case example, consider the time needed to fill a single-timeslot PW:
At 48 TDM bytes per frame: approx. 5.5 msec with CAS support and
5.9 msec without CAS support
At 1440 TDM bytes per frame: approx. 165 msec with CAS support and
177 msec without CAS support.
The round-trip (or echo) delay for voice channels is at least twice the
packetizing delay; any other delays encountered along the end-to-end
transmission path only add to this minimum. Another problem introduced by
packetizing is intrinsic jitter. Because the instant a packet is filled up is usually
not synchronized with its transmission to network, but occurs after an
essentially random delay, some jitter is inherently introduced.
Selecting an Optimal Jitter Buffer Size

For reliable operation, the jitter buffer must be large enough to ensure that it is
not emptied when the transmission delay increases temporarily (an effect called
underflow, or underrun), nor fills up to the point that it can no longer accept new
frames when the transmission delay decreases temporarily (an effect called
overflow).
The minimum size of the jitter buffer depends on the intrinsic jitter, and the
maximum size is 200 msec.
The theoretically correct value for the size of the jitter buffer of any given PW is
slightly more than the maximum variation in the transmission delay through the
network, as observed on the particular link between the PW source and the
destination. For practical reasons, it is sufficient to select a value that is not
exceeded for any desired percentage of time: for example, a value of 99.93%
means that the jitter buffer will overflow or underflow for an accumulated total
of only one minute per day.
Jitter buffers are located at both ends of a link, therefore the delay added by the
buffers is twice the selected value. The resultant increase in the round-trip delay
of a connection may cause problems ranging from inconvenience because of long
echo delays on audio circuits (similar to those encountered on satellite links) to
time-out of data transmission protocols (especially polling protocols).
Therefore, the size of each jitter buffer must be minimized, to reduce the
round-trip delay of each connection in as far as possible, while still maintaining
the link availability at a level consistent with the application requirements.
Configuring Pseudowires as System Timing References

You can select up to 10 pseudowires as clock sources per Megaplex-4100. The
allowed range of PW numbers that can serve as clock sources is 1 to 640. You
cannot select HDLCoPSN pseudowires as clock sources.
MPW-1 Modules
B-85
Configuring DS0 Cross-Connect

The internal DS1 port provides a connection point between TDM traffic arriving
from other modules and the pseudowires supported by MPW-1. Each pseudowire
can be connected to only one internal DS1 port.
Only framed ports can participate in DS0 cross-connect. You can assign timeslots
only to internal DS1 ports that have been already set to no shutdown.
Timeslots can be assigned for connection to any other port of an I/O or CL
module via DS0 cross-connect (such as framed E1-i, T1-i, E1 or T1 ports), or to
an I/O channel that supports connection of individual timeslots (such as a
high-speed data module).
For E1-i/T1-i ports, make sure to map this port to the prescribed TU of the CL
STM-1/4 or OC-3/12 port (use sdh-sonet cross-connect).
The maximum number of timeslots that can be cross-connected to T1 ports
(including T1-i ports on OC-3/OC-12 links), is 24.
Note that a timeslot assignment for a connection between two ports is accepted
as valid only when it is symmetrical, that is, a suitable timeslot of the destination
is also connected to the source port timeslot.
When using redundancy, timeslot assignment needs to be performed on the
primary port, and it is automatically copied to the redundancy partner.

TDM cross-connect can be done only between the ports using the same type of
framing (either a framed mode or the unframed mode).
Note that for ports using the TDM cross-connect, the internal DS1 port
bandwidth cannot be split among multiple pseudowires, and therefore the whole
port bandwidth must be assigned to only one pseudowire.
Although the internal DS1 port bandwidth is equivalent to 32 timeslots, the
pseudowire bandwidth depends on the number of timeslots available at the other
port:
For E1 ports, or E1-i ports on STM-1/4 links: 32 timeslots when using the
Unframed mode, or 31 timeslots when using a Framed mode
For T1 ports, or T1-i ports on OC-3/12 links: 24 timeslots.
The following selections of the other port are supported:
An external or internal E1 or T1 port of another I/O module using the same

framing mode
An E1-i/T1-i port on a CL.2 module. The corresponding E1-i/T1-i port must be

configured with the appropriate framing mode, and mapped to the prescribed
TU of the STM-1/4 or OC-3/12 port (in accordance with the type of links in
use).
The list of tasks that can be performed on the MPW-1 modules and the
B-86
MPW-1 Modules
Task
Configure an MPW-1 module and

put it into service
Selecting an adaptive clock

recovered from a pseudowire
circuit as system timing reference
Add a new pseudowire on a

MPW-1 module
config>pwe>pw
Configure the Ethernet port
Configuring the physical layer

parameters for the active internal
DS1 ports
configure>port>ds1
Comments and References
Configuring pseudowire services

Routing parameters for the
Megaplex-4100 PW router
(interfaces, associated static
routes, default gateway)
configure>router (2)
Adding pseudowire peers
configure>pwe>pw>peer
Configuring the PW peer

parameters
configure>peer
Adding pseudowires terminated at

the MPW-1 internal DS1 ports
configure>pwe
Configuring the pseudowires
configure>pwe>pw
Configuring flows
Configuring ingress and egress
flows between the SVI port
(bound to Router 2 interface) and
Logical MAC port or Ethernet port
configure>flows
Configuring cross-connect
Configuring timeslot assignment
for internal DS1 ports (DS0 crossconnect for DS1 ports)
configure>cr>ds0
Cross-connecting the DS1 port

with a vc12-vt2/vc11-vt1.5 from
an SDH/SONET port

with DS1 ports, see Cross-Connect
Table in Chapter 5
MPW-1 Modules
B-87
Task

from this ds1 port with another
ds1 port of the same
configuration
configure>cr>tdm
Establishing cross-connection
between the pseudowire and
timeslots on the ds1 port
configure>cr>pw-tdm
Configuring protection
Configuring protection for internal
DS1 ports
configure>protection>tdm-group
configure>protection>tdm-ring
Configuring fault propagation

Configuring fault propagation for
PW
configure>fault
Diagnostics
The MPW-1 module has local and remote loopbacks on selected timeslots of the
internal DS1 port level that can be controlled by the operator using
Megaplex-4100 system management. For loopback description and configuration,
refer to Testing DS1 Ports in Chapter 5.
Loopbacks can be activated only on connected ports (set to no shutdown).
Monitoring
The collected data enables the system administrator to monitor the transmission
performance, and thus the quality of service provided to users, for statistical
purposes. In addition, when problems are reported by users served by MPW-1,
the collected data can be used for diagnostic purposes, because it can help
identify the source of the problem.
The performance statistics data is continuously collected, and is stored as long as
the equipment operates. The stored data is deleted when the MPW-1 is reset or
removed, and is also lost when the Megaplex-4100 is powered down.
The monitoring tasks supported on each local MPW-1 port level are listed in the
table below.
Level
Monitored Feature
Path
Reference
Ethernet port
Status data for the Ethernet

port
configure>port>
ethernet
Ethernet Ports in Chapter
Status data for each SFP
configure>port>
ethernet
B-88
MPW-1 Modules

Level
Pseudowires
terminated on
MPW-1 ports
DS1 port
Monitored Feature
Path
Reference
Transmission performance
statistics
configure>port>
ethernet
Status data for each

pseudowire
configure>pwe>pw
Pseudowires in Chapter 5
Pseudowire transmission
statistics
configure>pwe>pw
Pseudowires in Chapter 5
Protection status
configure>
protection>tdmgroup
TDM Group Protection in
Chapter 5
Troubleshooting
Preliminary Checks

For problems affecting Ethernet traffic, use the performance monitoring

statistics data to analyze the problem characteristics and act accordingly.
If after collecting all the relevant alarm information, the problem appears to be
related to the operation of one of the MPW-1 ports, perform the actions listed
Make sure that no test has been activated on the corresponding MPW-1
internal DS1 port. Use the Megaplex-4100 management system to find the
active test or loopback, and deactivate it.
Activate the local loopback on the corresponding port timeslots that carry the
corresponding pseudowire. While the loop is connected, the user equipment
served by pseudowires configured on the corresponding port should receive
its own signal; if yes, the problem is external. Check cable connections, and
any transmission equipment providing the link to the user equipment.
Quickly check the link to the remote unit by activating, at the remote unit,
the remote loopback on the corresponding timeslots of the remote internal
DS1 port. If the link operates properly, the local user equipment served by
MPW-1 Modules
B-89
pseudowires configured on the corresponding port should receive its own

signal.
network, or with the MPW-1 modules.
B.5
ASMi-54C Modules
ASMi-54C is a family of SHDSL/SHDSL.bis Ethernet and TDM modules for the

Megaplex-4100 chassis that deliver Ethernet and E1 digital data to customer
premises over existing copper cables of the distribution network while eliminating
the need for repeaters.
ASMi-54C modules operate in the Megaplex-4100 chassis, to provide a simple and
low-cost connectivity solution using High speed Digital Subscriber Line
(SHDSL/SHDSL.bis) technology, as standardized by ITU-T Rec. G.991.2.
Each SHDSL/SHDSL.bis port is a multirate SHDSL/SHDSL.bis modem transmitting
user-selectable data rates up to 5.7 Mbps on each pair. Extended rates of up to
15 Mbps per 2W / 30 Mbps for 4W are available for the ASMi-54C/ETH version
with ASMi-54L modem at the far end (EFM mode).
The E1 and Ethernet high-speed functionality is divided among different module
versions with a variety of user ports.
The following types of external ports are available:
Eight SHDSL/SHDSL.bis independently-configurable external ports for SHDSL

services
Eight independently configurable E1 ports for E1 services
Two 10/100 Mbps Ethernet ports for packet-based services, with internal
Ethernet switching subsystem.
Product Options
The ASMi-54C family includes three basic modules:
ASMi-54C/ETH Ethernet over SHDSL.bis 8-port module with EFM support
ASMi-54C/E1/N - E1 over SHDSL 8-port module
ASMi-54C/E1/ETH/N E1 and Ethernet over SHDSL/SHDSL.bis 8-port module

(with optional remote power feeding support).
Interfaces and Services

The services provided by the three basic modules are as follows:
B-90
ASMi-54C/ETH transports Ethernet over 1, 2, and 4 pairs of SHDSL.bis copper

lines. It can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R)
SHDSL.bis Termination Unit working opposite up to 8 ASMi-54/ASMi-54L
standalone devices.
ASMi-54C Modules
Note
The ASMi-54C/E1/N module transparently forwards E1 data over 1, 2, and 4

pairs of SHDSL.bis/SHDSL copper lines. These modules operate as Central
SHDSL/SHDSL.bis (STU-C) Terminal Units for up to 8 ASMi-54/ASMi-54L
(SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone modems on the remote
site.
The ASMi-54C/E1/ETH/N multiplexer module transparently forwards E1 and

Ethernet data over 1, 2, and 4 pairs of SHDSL.bis/SHDSL copper lines. These
modules operate as Central SHDSL/SHDSL.bis (STU-C) Terminal Units for up to
8 ASMi-54/ASMi-54L (SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone
modems on the remote site.
In this chapter, the generic term ASMi-54C is used when the information is
applicable to all of the ASMi-54C models. The generic term ASMi-54C/N is used
when the information is applicable to ASMi-54C/E1/N and ASMi-54C/E1/ETH/N
models. The complete module designation is used when information is applicable
only to a specific model.
Table B-14. ASMi-54C Model Comparison
ASMi-54C/ETH
ASMi-54C/E1/N
ASMi-54C/E1/ETH/N
Line type
SHDSL.bis
SHDSL/SHDSL.bis
SHDSL/SHDSL.bis
Remote CPE and

number of wires
ASMi-54 (2W/4W/8W)
ASMi-54L (2W/4W)
ASMi-54 (2W/4W/8W)
ASMi-54L (2W/4W)
ASMi-52 (2W/4W)
ASMi-52L (2W/4W)
ASMi-54 (2W/4W/8W)
ASMi-54L (2W/4W)
ASMi-52 (2W/4W)
ASMi-52L (2W/4W)
Data transfer
Ethernet data over 1,

2 or 4 pairs
E1 data over 1, 2 or 4 pairs
E1 and Ethernet data over

1, 2 or 4 pairs
EFM/M-pair
EFM/M-pair
M-pair
M-pair
Central/Remote
STU-C/ STU-R
STU-C
STU-C
Note
ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules cannot work with a mix of

ASMi-54 and ASMi-52 modems at the far end. At every moment, all the remote
modems should be either ASMi-54/ASMi-54L or ASMi-52/ASMi-52L.
Power Feed
The ASMi-54C/E1/ETH/N module has a special version to provide a remote power
feeding source that delivers power and data over 4 wires to up to 4 remote
modems or repeaters and eliminates the need for locally powered modems or
repeaters.
Ethernet Ports
ASMi-54C Modules
B-91
Applications
ASMi-54C and ASMi-54C/N modules connected to ASMi-54/ASMi-54L and
ASMi-52/ASMi-52L standalone modems.
Figure B-28. Corporate Service Sharing
Features
SHDSL Transport
ASMi-54C modules use the SHDSL.bis version of the Symmetrical High-speed
Digital Subscriber Line technology, as standardized in ITU-T Rec. G.991.2, also
supporting the older SHDSL standard. It also fully complies with ETSI TS 101 524
standard. Each group of four SHDSL/SHDSL.bis ports (1 to 4, and 5 to 8) is
handled by a separate SHDSL section.
The SHDSL transport mechanism and features depend on the specific model of
ASMi-54C:
B-92
ASMi-54C/ETH transports Ethernet over 1, 2, and 4 pairs of SHDSL.bis copper

lines. It can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R)
SHDSL.bis Termination Unit working opposite up to 8 ASMi-54/ASMi-54L
standalone devices.
The ASMi-54C/E1/N module transparently forwards E1 data over 1, 2, and 4

pairs of SHDSL.bis/SHDSL copper lines. These modules operate as Central
SHDSL/SHDSL.bis (STU-C) Terminal Units for up to 8 ASMi-54/ASMi-54L
(SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone modems on the remote
site.
ASMi-54C Modules
The ASMi-54C/E1/ETH/N multiplexer module transparently forwards E1 and

Ethernet data over 1, 2, and 4 pairs of SHDSL.bis/SHDSL copper lines. These
modules operate as Central SHDSL/SHDSL.bis (STU-C) Terminal Units for up to
8 ASMi-54/ASMi-54L (SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone
modems on the remote site. Each of the eight SHDSL/SHDSL.bis module ports
is supported by a multirate modem that operates at a data rate of up to
5696 kbps (E1+Ethernet).
To increase available bandwidth or extend the maximum range at a given rate, it

is possible to bond together two lines (4-wires mode). Note that when
connecting an ASMi-54C/N to a standalone unit with E1 ports, the maximum
bandwidth needed for TDM services is that of a single E1 port.
Ethernet Services
full VLAN support. The total Ethernet traffic per module (from 1 or 2 ports) is up
to 100 Mbps.
The external Ethernet ports can be ordered with two types of interfaces:
10/100BaseTx interfaces terminated in RJ-45 connectors.
Sockets for Fast Ethernet SFP transceivers. RAD offers several types of SFPs
(SFPs with copper interfaces are also available).
The interface supports autonegotiation for plug-and-play Ethernet connectivity.

ASMi-54C implements IEEE 802.1Q standards to provide VLAN-tagging with levels
of prioritization, enabling carriers to offer differentiated Ethernet services. VLAN
tagging can also be employed to separate traffic, ensuring transparency of the
customer traffic and bolstering security of management traffic.
The Ethernet switch serves both traffic and management. Traffic is supported by
means of the two external Ethernet ports of the module and by internal ports
connected to the SHDSL lines, and management is supported by a dedicated port
internally connected to the ASMi-54C management subsystem, and by another
Fast Ethernet port connected to the management handling section of the CL
modules installed in the Megaplex-4100 (this section is available on all CL
modules).
The internal Ethernet switching subsystem enables forwarding traffic between
the ASMi-54C external Ethernet ports and SHDSL lines to any other bridge port in
the Megaplex-4100, using both the unaware and aware modes in accordance
with application requirements.
Two types of bridge ports can be defined on an ASMi-54C module:
Each PCS configured on the module SHDSL ports.
Each Ethernet physical port can also serve as a bridge port.
A maximum of 10 bridge ports can be defined on an ASMi-54C module, together

with the two Ethernet ports.
ASMi-54C Modules
B-93
Each of these bridge ports can be connected to any other bridge port within the
Megaplex-4100, for example, to another bundle or Ethernet port on any module
(including GbE ports on CL modules), to a virtually concatenated group (VCG), etc.
defining flows.
The customers edge traffic accepted by ASMi-54C Ethernet ports is directed to


When providing Ethernet services and operating as STU-R, ASMi-54C/ETH

performs line probing according to G.991.2. When enabled, the SHDSL interface
adapts its rate to the condition of the line (noise, loop attenuation, etc.). When
disabled, the SHDSL line operates at a fixed rate selected by the user. The SHDSL
line supports TPS-TC framing 64/65-octets for EFM (IEEE 802.3) and HDLC
(G.991.2).
The processing and switching of Ethernet traffic over TDM (SHDSL) links is
configured by means of PCS using EFM or HDLC as the Layer-2 protocol.
EFM bonding on the Ethernet interface ensures that a failure or addition of a link
does not drop the traffic being transmitted over the other wires in the group.
The capacity of the group is not affected when a new link is added at a lower
rate.
Ethernet transport over SHDSL/SHDSL.bis in ASMi-54C/E1/ETH/N is provided by
means of HDLC encapsulation only.
E1 Services
E1 services are provided by /N options of the ASMi-54C module.
To increase available bandwidth, two lines (4-wires) can be bonded to operate in
the M-pair mode specified in ITU-T Rec. G.991.2. Bonding is possible only for lines
handled by the same SHDSL section (the section handling either ports 1 to 4, or
ports 5 to 8).
B-94
ASMi-54C Modules
The external line ports have user-selectable balanced (120) or unbalanced

(75) DSU interfaces. The framing mode is also user-selectable, in accordance
with the required handling of the port traffic: G.704 basic with or without CRC-4,
or unframed.
Cross-Connections
The ASMi-54C/N modules support both DS0 and TDM cross-connection, selectable
at the level of the individual E1 port:

cross-connect enables connecting payload between E1 and T1 ports.

Management
Via a supervisory port on the Megaplex-4100 CL module using an ASCII

terminal
Via a dedicated 10/100BaseT Ethernet port for connection to a management

station
Using inband management with dedicated VLAN for managing remote units.
The remote ASMi-52/ASMi-52L modems can be configured and monitored from

the central ASMi-54C/N card via EOC.
Remote Power Feeding

The ASMi-54C/E1/ETH/N module has a special remote power feeding version that
delivers power and data over 4 wires to up to 4 SHDSL/SHDSL.bis remote
modems or repeaters.
The module receives the power from the external MPF power feeder supplying
each 2-wire line with nominal DC voltage at a maximum of 70 mA with current
limit protection for each channel.
The nominal voltage is 120 VDC.
Power feeding for each individual line is connected/disconnected via a software
command. The power feeding status for each line and report of current overload
conditions is also displayed via CLI (see SHDSL ports in Chapter 5).
Monitoring
Performance statistics for the SHDSL, E1 and Ethernet ports may be obtained and
analyzed via the Megaplex-4100 management system.
ASMi-54C modules occupy one I/O slot in the Megaplex-4100 chassis.
Typical ASMi-54C module panels are shown in Figure B-29.
ASMi-54C Modules
B-95
ASMi-54C/ETH with ASMi-54C/ETH

Ethernet Ports
with Copper
Equipped with SFPs Ethernet Ports
ASMi-54C/E1/N
ASMi-54C/E1/ETH/N
with Ethernet Ports
Equipped with SFPs
ASMi-54C/E1/ETH/N
with Copper
Ethernet Ports
Figure B-29. ASMi-54C/E1/N Module Panels

B-96
The SHDSL interfacing section consists of a 26-pin D-type female connector,

designated SHDSL.bis, for connecting to all the SHDSL ports. The SHDSL
interface of /PF module version is different and consists of 8 terminal block
connectors, two for each feeding line.
E1 interfacing section (optional) consists of a 44-pin D-type female

connector, designated E1, for connecting to all the E1 ports.
Ethernet interfacing section (optional): includes two Ethernet ports,

designated ETH1 and ETH2. The ports are either equipped with SFPs or
ASMi-54C Modules
LED Indicators
The E1 section of all modules and SHDSL section of the modules do not contain
any LED indicators.
Each Ethernet port has its own set of LED indicators, which are different for the
ASMi-54C/ETH and ASMi-54C/N models.
The functions of the Ethernet port status indicators are as follows:
Table B-15. ASMi-54C/N Ethernet Indicators

Name
Function/Color
Meaning
LINK/ACT
On (green)
Link is up
Off
Link is down
Flashes:
Frames are transmitted/received
On (yellow)
100 Mbps mode
Off
10 Mbps mode
100
Table B-16. ASMi-54C/ETH Ethernet Indicators

Name
Function/Color
Meaning
LINK
On (green)
Link is up
Off
Link is down
On (yellow)
Data is being transferred
Off
No data transfer
ACT
SHDSL Interface
Number of Ports
Number of Wires
2, 4 or 8 (see Table B-17)
Interface Type
ASMi-54C/ETH: SHDSL.bis
ASMi-54C/N (all models) : SHDSL/SHDSL.bis
Line Coding
ASMi-52/52L: TC-PAM16
ASMi-54: TC-PAM16/32
ASMi-54L: TC-PAM16/32/64
Compliance
ITU-T Rec. G.991.2, ETSI TS 101524
Data Rate
Depends on the module type, number of wires and

far-end device (see Table B-17)
ASMi-54C Modules
B-97
Table B-17. SHDSL Data Rates

Module
Wires/Mode/TC Layer
ASMi-54C/ETH
ASMi-54C/N
Far-End Device
ASMi-54
ASMi-54L
ASMi-52/ASMi-52L
2W, HDLC
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 12544 kbps

(n 64 kbps, n= 3 to
196)
N/A
2W, 64/65-Octets
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 15296 kbps

(n 64 kbps, n= 3 to
239)
N/A
4W, HDLC
384 to 11392 kbps

178)
384 to 30592 kbps

(n 64 kbps, n= 6 to
478)**
N/A
4W, 64/65-Octets
384 to 11392 kbps

178)
384 to 30592 kbps

(n 64 kbps, n= 6 to
478)
N/A
8W, HDLC
768 to 22784 kbps

356)
N/A
N/A
8W, 64/65-Octets
768 to 22784 kbps

356)
N/A
N/A
2W
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 5696 kbps

(n 64 kbps, n= 3 to
89)
192 to 2048 kbps

32)
*4W,
high-speed-muxserial-e1 mode
N/A
N/A
384 to 4096 kbps

64)
4W, other modes
384 to 11392 kbps

178)
384 to 11392 kbps

178)
384 to 2048 kbps

32)
8W
768 to 22784 kbps

356)
N/A
N/A
*ASMi-52 only
**The following rates are unavailable for 4W/HDLC operation:
17024 to 18432 kbps
24570 to 25088 kbps
27520 to 30592 kbps.
B-98
ASMi-54C Modules
Port Type
(ASMi-54C/ETH
only)
Software configurable for all the ports:

Central (STU-C) default mode
Remote (STU-R)
Line Type
Single unloaded, unconditioned copper twisted pair, 26

AWG or thicker
Nominal Line
Impedance
135
Range at 26 AWG, See Table B-18.

noise-free
Port Timing
STU-C: locked to Megaplex-4100 nodal clock

STU-R (ASMi-54C/ETH only): locked to the line signal
received from the STU-C
Connectors
DB-26 convertible to 8 RJ-45 connectors via adaptor cable

(regular model)
Single-pair female 2-pin terminal block for each port
(power-feed model)
Table B-18. Typical Ranges over 2W@26 AWG Cable

Data Rate
Notes
Ranges
[kbps]
[km]
[miles]
192
6.6
4.1
1536
4.9
3.0
2048
4.5
2.8
4096
3.2
2.0
4608
3.0
1.9
5696
2.6
1.6
15296
0.70
0.43
The typical ranges are based on error-free lab tests without noise and
obtained on a 26 AWG cable line simulator (DLS-400). For ASMi-52/52L on the

far end, only ranges up to 2048 are relevant.
Using 4-wire or 8-wire devices allows achieving the same ranges at higher data
rates. For example, an 8-wire ASMi-54C/ETH module provides the range of

5.5 km/3.4 miles at the rate of 4096 kbps instead of 1024 kbps for 2 wires.
Ethernet
Interfaces
Number of Ports
2 (either fiber-optic or copper, per customer

order)
ASMi-54C Modules
B-99
Maximum Frame Size
ASMi-54C/N: 9600 bytes

ASMi-54C/ETH: 1522 bytes
Data Rate

Fiber Optic Ports
Hot-swappable SFPs

Copper Ports
Interface Type
10/100Base-TX
Connector
Shielded RJ-45
Indicators (per port)

ASMi-54C
LINK (green) LAN link integrity

ACT (yellow) LAN data activity
ASMi-54C/N
LINK/ACT (green)
On: link is up
Off: link is down
Blinking: frames are transmitted/received
100 (yellow)
On: 100 Mbps mode
Off: 10 Mbps mode
E1 Interface
Number of Ports
Type and Bit Rate
E1, 2.048 Mbps
Coding
HDB3
Line Impedance
Balanced E1: 120

Unbalanced E1: 75 (via adapter cable)
E1 Jitter Performance
As per ITU G.823
Connector
DB-44 convertible to RJ-45 or BNC connectors via

adaptor cables
Framing
Basic G.704 framing (G732N) with and without

CRC-4 option enabled
G.704 framing with timeslot 16 multiframe
(G732S)
B-100
ASMi-54C Modules
Power Feed
Diagnostics
Power Feeding Voltage
120 VDC
Power Feeding Current
Maximum 70 mA per line (2W)
For details, see Table B-27
Local and remote loopbacks on local E1 ports,

per port and per timeslot
(ASMi-54C/N only)
Local and remote loopbacks on local E1-i ports

connected to the corresponding remote SHDSL
ports, per port and per timeslot
Remote-on-remote inband loopbacks on
SHDSL ports, per port
BER Test on local framed E1 and E1-i ports,
per timeslot
BER Test on local unframed and whole framed
E1 and E1-i ports, per port
Performance
Monitoring
Power
Consumption
(max)
Transmission performance statistics for Ethernet,

SHDSL, PCS, E1 and E1-i ports
ASMi-54C/ETH
14.5W
ASMi-54C/E1/N
7.3W
ASMi-54C/E1/ETH/N
12W
ASMi-54C/E1/ETH/UTP/N/RPF 12.3W
(from Megaplex PS, regular
operation)
ASMi-54C/E1/ETH/UTP/N/RPF 3W + [P x (Cm + Cr + Cl)], where:
(from MPF, power feeding
P number of module ports used for phantom
operation)
feeding
Cm remote modem power consumption

Cr repeater power consumption
Cl power drop on the line
Configuration
Environment

system
Operating temperature
ASMi-54C/ETH: -10C to 55C (14F to 131F)

ASMi-54C/N: 0C to 45C (32F to 113F)
Storage temperature
-20C to 70C (-4F to 158F)
Humidity: up to 95%,
non-condensing
ASMi-54C Modules
B-101
Warning
Caution

The ASMi-54C modules contain components sensitive to electrostatic discharge
ASMi-54C modules may be installed in an operating chassis (hot insertion).
Note
ASMi-54C software can be updated by downloading from the CL module.

Therefore, if the ASMi-54C module is not yet loaded with the required software
No preparations are required for ASMi-54C modules with UTP Ethernet
portsterminated in RJ-45 connectors.
For ASMi-54C modules equipped with Ethernet ports having SFP sockets, it may
be necessary to install or replace SFPs. ASMi-54C modules have two installation
positions for SFPs, designated ETH1 and ETH2:
ASMi-54C modules equipped with RAD-supplied SFP plug-in modules comply with
strongly recommends ordering the ASMi-54C with RAD SFPs, as this permits full
ASMi-54C modules are shipped with protective covers installed on all the optical
B-102
ASMi-54C Modules
SFPs installed on ASMi-54C modules may be equipped with a laser diode. In such
Warning
For your safety:

Installing an SFP
Warning
Caution
connectors.
Note
To install the SFP:
Note
ASMi-54C Modules
B-103
ASMi-54C module, and from the SFP electrical connector.
Replacing an SFP
To replace an SFP:
The ASMi-54C module starts operating as soon as it is inserted in an operating

chassis.
Warning
To install an ASMi-54C module:

3. Insert the ASMi-54C module in its chassis slot and slide it in as far as
possible.
4. Secure the ASMi-54C module by tightening its two fastening screws.

B-104
ASMi-54C Modules

Each ASMi-54C ETH electrical port has a 10/100BASE-TX Ethernet interface

Pin
Designation
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
Not connected
Not connected
To connect cables to the ASMi-54C electrical Ethernet ports:
Connect the prescribed cable to the corresponding connector, ETH1 or ETH2.

To connect cables to the ASMi-54C optical Ethernet ports:

connector, ETH1 or ETH2.
Connecting the SHDSL Ports

All the SHDSL ports of the ASMi-54C modules are terminated in a 26-pin D-type
male connector, designated SHDSL.bis. RAD offers as an ordering option an
adapter cable, CBL-DB26-8SHDSL, for connecting to the module SHDSL
interfaces. CBL-DB26-8SHDSL is 2-meter cable, ending in 8 RJ-45 connectors, one
for each channel. Figure B-31 shows the cable construction. Table B-20 presents
the cable wiring and also identifies the SHDSL.bis connector pin assignment.
ASMi-54C Modules
B-105

Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL-D B26-8SHDSL
Ch. 5
Ch. 6
Ch. 7
Ch. 8
Figure B-31. CBL-DB26-8SHDSL Cable

Table B-20. CBL-DB26-8SHDSL Cable Wiring
Channel
26-Pin Connector
Pin
Function
Tip
Ring
19
Tip
20
Ring
12
Tip
13
Ring
Tip
Ring
RJ-45 Connector
Label
CH-1
Channel
Pin
5
4
5
CH-2
5
CH-3
CH-4
4
5
26-Pin Connector
Pin
Function
22
Tip
23
Ring
16
Tip
15
Ring
Tip
Ring
25
Tip
26
Ring
RJ-45 Connector
Label
CH-5
Pin
5
4
5
CH-6
4
5
CH-7
CH-8
4
5
4
ASMi-54C SHDSL.bis connector, and connect the cable to the module as explained
below.
To connect the cable to the module:

1. Connect the 26-pin connector of the CBL-DB26-8SHDSL cable to the module
front panel SHDSL.bis connector.
2. Connect the RJ-45 plug of each line (the plugs are marked CH-1 to CH-8) to
the prescribed user equipment or patch panel connector. Insulate unused
connectors, to prevent accidental short-circuiting of their exposed contacts
to metallic surfaces.
Connecting the E1 Ports

The E1 ports of ASMi-54C/N modules are terminated in a 44-pin D-type female
connector. The module connector supports both the unbalanced and balanced
interfaces. Each type requires a different adapter cable.
B-106
ASMi-54C Modules

end, for use when ASMi-54C/N modules are connected to equipment with
balanced E1 interfaces using pins 1, 2 for the receive (RX) pair and pins 4,5
for the transmit (TX) pair

balanced E1 interfaces using pins 4,5 for the receive (RX) pair and pins 1, 2
for the transmit (TX) pair

end, for use with ASMi-54C/N modules using the balanced E1 interface

unbalanced E1 interfaces
MP-PATCH-16-BNC: a low-cost adapter patch panel terminated in BNC

connectors at the users end, for use when several ASMi-54C/N modules are
connected to equipment with unbalanced E1 interfaces.
The following sections describe these adapter cables, and the functions of the
44-pin connector pins for each interface type.
The CBL-G703-8/RJ45/ST is a 2-meter cable for ASMi-54C/N modules using the
balanced interface.

Ch. 1
Ch. 2
Ch. 3
Ch. 4
CBL-G703-8/RJ45/ST
Ch. 5
Ch. 6
Ch. 7
Ch. 8
ST-CLK
Station
Clock

assignment.
ASMi-54C Modules
B-107
Channel
44-Pin Connector
RJ-45
Pin
Connector
CH-1
CH-2
CH-3
CH-4
Function
RJ-45
Connector
31
RX Ring
17
RX Tip
16
TX Ring
Channel
Pins
RJ-45
44-Pin Connector
Pin
Connector
CH-5
Function
RJ-45
Connector
Pins
37
RX Ring
23
RX Tip
22
TX Ring
TX Tip
TX Tip
33
RX Ring
38
RX Ring
32
RX Tip
39
RX Tip
TX Ring
CH-6
TX Ring
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
26
RX Tip
19
TX Ring
25
TX Ring
CH-7
TX Tip
10
TX Tip
35
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
24
RX Ring
27
RX Tip
21
TX Ring
18
TX Tip
CH-8
ST-CLK
assignment.
B-108
ASMi-54C Modules

Channel
RJ-45
Connector
CH-1
CH-2
CH-3
CH-4
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
31
RX Ring
17
RX Tip
16
TX Ring
TX Tip
Channel
RJ-45
Connector
44-Pin
Connector
Pin
Function
RJ-45
Connector
Pins
37
RX Ring
23
RX Tip
22
TX Ring
TX Tip
2
4
CH-5
33
RX Ring
38
RX Ring
32
RX Tip
39
RX Tip
TX Ring
TX Ring
CH-6
TX Tip
TX Tip
34
RX Ring
40
RX Ring
20
RX Tip
26
RX Tip
19
TX Ring
25
TX Ring
TX Tip
10
TX Tip
35
RX Ring
41
RX Ring
36
RX Tip
42
RX Tip
TX Ring
11
TX Ring
TX Tip
12
TX Tip
CH-7
CH-8
CBL-G703-8/OPEN/2M cable is a 2-meter cable for ASMi-54C/N modules using the
balanced E1 interface, terminated in free leads that can be connected to any
terminal block or connector appropriate for your application.
CBL-G703-8/OPEN/2M
ASMi-54C Modules
B-109

44-Pin Connector
Channel
44-Pin Connector
Pair Color
Pin
Function
31
Rx Ring
17
Rx Tip
Blue
Tx Tip
Orange
16
Tx Ring
White
33
Rx Ring
32
Rx Tip
Tx Tip
Brown
Channel
Pair Color
Pin
Function
37
Rx Ring
White
23
Rx Tip
Brown/Blue
Tx Tip
Grey/Blue
22
Tx Ring
White
White
38
Rx Ring
White
Green
39
Rx Tip
White/Orange
Tx Tip
Orange/Green
White
White
5
Tx Ring
White
Tx Ring
34
Rx Ring
White
40
Rx Ring
White
20
Rx Tip
Grey
26
Rx Tip
Orange/Brown
Tx Tip
White/Blue
10
Tx Tip
Grey/Orange
19
Tx Ring
White
25
Tx Ring
White
35
Rx Ring
White
41
Rx Ring
White
36
Rx Tip
Orange/Blue
42
Rx Tip
White/Green
Tx Tip
Green/Blue
12
Tx Tip
Green/Brown
Tx Ring
White
11
Tx Ring
White
CBL-G703-8/COAX is a 2-meter cable for ASMi-54C/N modules using the
unbalanced E1 interface. Figure B-35 shows the cable construction.
RX
Ch. 1
TX
RX
Ch. 2
TX
RX
Ch. 3
TX
CBL-G703-8/COAX
RX
Ch. 7
TX
RX
Ch. 8
TX

ground): this enables the ASMi-54C/N module to differentiate between the
connection of this cable and the connection of the
B-110
ASMi-54C Modules

Channel Function
RX
1
TX
RX
2
TX
RX
3
TX
RX
4
TX
44-Pin Connector
Pin
Function
31
Ring
29
Frame Ground
BNC
Contact
Shield
17
Tip
Center
Tip
Center
16
Ring
14
Frame Ground
33
Ring
44
Frame Ground
32
Tip
Center
Tip
Center
Ring
29
Frame Ground
34
Ring
29
Frame Ground
Channel Function
RX
5
TX
Shield
Shield
RX
6
TX
Shield
Shield
20
Tip
Center
Tip
Center
19
Ring
14
Frame Ground
35
Ring
44
Frame Ground
36
Tip
Center
Tip
Center
RX
7
TX
Shield
Shield
Ring
29
Frame Ground
Cable Type Sensing
15
Sense Input,
connected to
pin 30
Signal Ground
30
Ground
Frame Ground
44
Cable Shield
RX
8
Shield
TX
Function
BNC
Contact
37
Ring
Shield
29
Frame Ground
44-Pin Connector
Pin
23
Tip
Center
Tip
Center
22
Ring
14
Frame Ground
38
Ring
44
Frame Ground
Shield
Shield
39
Tip
Center
Tip
Center
Ring
14
Frame Ground
40
Ring
29
Frame Ground
Shield
Shield
26
Tip
Center
10
Tip
Center
25
Ring
14
Frame Ground
41
Ring
44
Frame Ground
Shield
Shield
42
Tip
Center
12
Tip
Center
11
Ring
14
Frame Ground
Shield
ASMi-54C/N connector, and connect the cable to the module as explained below.
BNC Patch Panel

A different solution for connecting ASMi-54C/N modules using the unbalanced E1
interface is a BNC patch panel. This low-cost alternative to CBL-G703-8/COAX
allows considerable cost savings, especially when working in 4-wire mode.
The patch panel supports up to two ASMi54-C/N modules with 8 E1 links or up to
four ASMi-54C/N modules with 4 E1 links, depending on the connection to the
panel.
The patch panel includes 16 female BNC connectors on its front panel (see
Figure B-36) and 6 DB-44 connectors on its rear panel (see Figure B-37). A
special CBL-DB44-DB44 cable can be ordered from RAD to connect each DB-44
connector of the module to the corresponding DB-44 connector of the patch
panel.
Six DB-44 connectors are used as follows:
ASMi-54C Modules
B-111
1-8 and 9-16 connectors are used for connecting up to two ASMi-54C/N
modules operating in 2-wire mode (8 E1 links for each connector)
1-4, 5-8, 9-12 and 13-16 connectors are used for connecting up to
four ASMi-54C/N modules operating in 4-wire mode (4 E1 links for each
connector).
Figure B-36. Front Panel
Figure B-37. Rear Panel
Connecting to E1 Ports
Using the site installation plan, identify the appropriate cable/patch panel
intended for connection to the ASMi-54C/N connector, and connect it to the
module as explained below.

1. Connect the 44-pin connector of the cable to the ASMi-54C/N front panel
connector.
B-112
ASMi-54C Modules

1. Connect the 44-pin male connector of the cable to the ASMi-54C/N front
panel connector.
To connect the BNC patch panel:

1. Connect the 44-pin male connector of the CBL-DB44-DB44 cable to the
ASMi-54C/N front panel connector.
2. Connect the other end of the CBL-DB44-DB44 cable to the corresponding
44-pin female connector of the Patch panel.
3. Connect the BNC plugs of the Patch panel (the plugs are marked with the
number of ports 1 to 16) to the prescribed user equipment or external patch
panel connectors. Pay attention to correct connection:

method.
2. Connect the 44-pin male connector of the cable to the ASMi-54C/N front
panel connector.
Normal Indications
ASMi-54C/ETH
Once the equipment connected to the ASMi-54C Ethernet ports is operational,
the following indications appear for each port:

equipment
ASMi-54C/N
The LINK/ACT indicator lights as long as the port is connected to operational

equipment, or flashes in accordance with the transmit and receive activity at
the corresponding port
The 100 indicator lights when the port operates at 100 Mbps.
ASMi-54C Modules
B-113
The normal indication for the P-FEED dual-color indicators of the power feed
model is steady green light. This means that the line group carries power of
180 VDC.
ASMi-54C/ETH Only
The first step in planning the configuration sequence of ASMi-54C/ETH modules is
to select the Transmission Convergence (TC) layer to be used by the module,
HDLC or 64/65 octet encapsulation:
64/65 octet encapsulation: supports only packet traffic, that is, only Ethernet
transmissions port services. Each SHDSL line then operates alone (2-wires
mode only), but the total bandwidth available for an Ethernet port can be
increased by bonding together several lines, using the PAF (PME Aggregation
Function).
For ASMi-54C/ETH modules, PAF can combine two or four lines for serving a
single PCS. The PCS can be connected by a flow to an Ethernet port (with four
lines per PCS, two PCSs can be configured, one for each ASMi-54C/ETH
Ethernet port).
HDLC encapsulation: supports both Ethernet and TDM transmissions port

services. To increase available bandwidth, it is possible to bond together two
or four lines (4-wires and 8-wires mode, respectively). Thus, the maximum
bandwidth for Ethernet services is obtained by configuring two 8-wires lines.
After selecting the TC layer, it is necessary to select the bandwidth, considering

the required range (see range data in Table B-18. When range is significant, the
use of multiple lines is recommended. This can yield the same throughput as a
single line, but a lower rate per line is used, thus increasing the range and
reducing the effects of interference and crosstalk.
Also note that when the ASMi-54C/ETH module is operating in the STU-R mode,
the maximum number of remote units is two. These units will be served by PCS 1
and PCS 5 only.
After determining the general planning parameters, other configuration
parameters can be selected in accordance with the specific application
requirements.
Configuring SHDSL Line Parameters

ASMi-54C modules have 8 independent SHDSL ports, supported by means of two
internal SHDSL processing subsystems (one subsystem handles ports 1 to 4, and
the other ports 5 to 8). Each port requires a 2-wire line.
Note
ASMi-54/54L/52/52L standalone units support the connection of up to four

SHDSL ports, which must always be in the same group: either 1 to 4, or 5 to 8.
In each group, ports can be configured to operate separately (2 wires mode), or
can be bonded together in groups of two ports (4 wires mode), or 4 (8 wires
mode).
B-114
ASMi-54C Modules
Table B-25. Supported Ports versus Wires Parameter

Line Number
Available Modes
Description
2 Wires
Port independently configurable
4 Wires
Port 1 bonded with Port 2.

Port 1 is the master port, and all its parameters will be
copied to Port 2. Port 2 and PCS 2 will not be
available to selection by the user
1
8 Wires*
Port 1 bonded with Port 2, Port 3 and Port 4.

Line 1 is the master port, and all its parameters will be
copied to Port 2, Port 3, and Port 4. Port 2, 3, 4 and
PCS 2, 3, 4 will not be available for selection by the
user
2 Wires
2 Wires
4 Wires

2 Wires
2 Wires
4 Wires

copied to Port 6. Port 6 and Port 6 will not be
5
8 Wires*
Port 5 bonded with Port 6, Port 7 and Port 8.

copied to Port 6, Port 7 and Port 8. Port 6, 7, 8 and
PCS 6, 7, 8 will not be available for selection by the
user
2 Wires
2 Wires
4 Wires

2 Wires
Handling of Timeslot 0 in ASMi-54C/N Modules

You can select the handling method of timeslot 0 of an E1 stream by each SHDSL
port of ASMi-54C/N modules as follows:
ASMi-54C Modules
B-115
Terminate (loop back) timeslot 0 (ts0-over-dsl disabled). This option is

available in the basic G.704 mode only.
Transfer timeslot 0 transparently through the SHDSL link, down to the E1

port of the equipment unit connected to the remote ASMi-52/ASMi-52L or
ASMi-54/ASMi-54L unit (ts0-over-dsl enabled). This option is available in both
G.704 framing modes.
ASMi-54C/N Module Limitation

This limitation concerns configuring an ASMi-54C/N module with an ASMi modem
on the far end having E1 and Ethernet ports. If you configure such a modem for
Ethernet traffic only, make sure to open and configure at least one of E1
timeslots.
4M Functionality in ASMi-54C/N working opposite

ASMi-52/52L in Mux Mode
The SHDSL port data rate (line payload rate) attained by any model of ASMi-54C
module working opposite ASMi-54/ASMi-54L depends only on the number of
wires: 192 to 5696 kbps for 2W and 384 to 11392 kbps for 4W. It depends
neither on the model of the remote modem nor on the working configuration.
The situation is different for ASMi-54C/N modules working opposite ASMi-52
modems with E1 and serial ports. When working in 2W mode, the available rates
are 192 to 2048 kbps for any remote modem type and any working
configuration. However, when working in 4W mode and in the E1+serial mux
mode, the available rates are not twice as higher as compared to 2W but still
remain limited in the range of 384 to 2048 kbps.
To overcome this limitation and attain the rate of 4096 kbps in a configuration
when ASMi-54C/N is working opposite ASMi-52 in the mux (E1+serial) mode, a
special procedure is required. In this procedure the far-end-type parameter is set
to high-speed-mux-serial-e1 and e1-i ports of the ASMi-54C/N module are
configured in a special way:
Odd e1-i ports (#1,3,5,7) are configured to carry E1 payload
Even e1-i ports (#2,4,6,8) are configured to carry serial payload, representing
the ASMi-52/52 serial interface.
When the far-end-type is high-speed-mux-serial-e1, each 4W line employs two

e1-i ports, the even e1-i ports representing this serial interface of the ASMi52/52L. This means that timeslot assignment shall treat all timeslot selected on
this e1-i port as one bundle (like serial interface of HS-12). This bundle cannot
be assigned to different lines or if cross connected to a high-speed serial
interface, the number of timeslots must be identical to the serial channel speed.
The table below shows the traffic distribution by e1-i ports for different
applications of ASMi-54C/N working opposite ASMi-52/52L modems.
Table B-26. Traffic Distribution by ASMi-54C/N Application

Application
B-116
Functionality
ASMi-54C Modules
Cross-connect
Comments
Application
Functionality
Cross-connect
E1 over 4W
Non-mux, working
opposite ASMi-52/52L
non-mux version with E1
interface
e1-i#1 crossconnected to E1 port
Non-mux, working
opposite ASMi-52/52L
non-mux version with
serial interface
e1-i#1 crossconnected to serial

port
Mux, working opposite

ASMi-52 mux version
with E1 and serial
interfaces
e1-i#1 cross
connected to e1 port
Serial over
4W
E1+serial
over 4W
Comments
e1-i#2 not connected

The SHDSL line rate must be identical to
number of selected timeslots
e1-i#2 not connected
e1-i#2 cross
connected to the serial
bundle
The configured SHDSL rate must be

even and equal to the (sum of timeslots
used in ei-i#1 and ei-i#2) + (1 or 2):
if (sum of timeslots used in ei-i#1

and ei-i#2) is even, then +2 must be
added
if (sum of timeslots used in ei-i#1

and ei-i#2) is odd, then +1 must be
added.
For even e1-i ports representing the

serial ASMi-52 interface (far-endtype=high-speed-mux-serial-e1), the
only possible selections are g732n and
unframed.
See also Table B-17 for the SHDSL data rate depending on the module type,
number of wires and far-end device.
An example of such configuration is given below. The procedure in this example is
as follows:
1. Configure the ASMi-54C/N module in slot 7 and HS-12N module in slot 10
2. Configure E1 payload on E1 port 7/1.
3. Configure port 1 of HS-12N to total speed of 31 x 64= 1984 kbps.
4. Configure SHDSL port 7/1 to high-speed-mux-serial-e1.
5. Configure SHDSL port 7/1 to total speed of 64 x 64= 4096 kbps.
6. Configure its Ei-i port 1 (odd) for E1 data.
7. Configure its Ei-i port 2 (even) for serial data (representing the ASMi-52 serial
interface).
8. Cross-connect (tdm) E1 payload with E1-i port 7/1 (odd).
9. Cross-connect (ds0) serial payload with E1-i port 7/2 (even).
ASMi-54C Modules
B-117
mp4100# configure
mp4100>config# slot 7 card-type dsl asmi54c-e1eth
mp4100>config# slot 10 card-type high-speed hs12n
mp4100>config#
mp4100>config# port shdsl 7/1 no shutdown
mp4100>config# port shdsl 7/1 wire 4
mp4100>config# port shdsl 7/1 far-end-type high-speed-muxserial-e1
mp4100>config# port shdsl 7/1 data-rate maximum 4096
mp4100>config#
mp4100>config# port e1-i 7/1 no shutdown
mp4100>config# port e1-i 7/1 line-type unframed
mp4100>config#
mp4100>config# port e1-i 7/2 no shutdown
mp4100>config# port e1-i 7/2 line-type g732n
mp4100>config# port e1-i 7/2 no ts0-over-dsl
mp4100>config#
mp4100>config# port serial 10/1 rate 31 x 64
mp4100>config#
mp4100>config# port e1 7/1 no shutdown
mp4100>config# port e1 7/1 line-type unframed
mp4100>config# cross-connect
mp4100>config>xc# tdm e1 7/1 e1-i 7/1
mp4100>config>xc# ds0 e1-i 7/2 ts [1..31] serial 10/1
mp4100>config>xc# commit
Result : ok
When changing the 2M operation mode to 4M and vice versa (changing far-endtype between high-speed-mux-serial-e1 and any other), a warning appears that
the module will be restarted. This means that the connected modem will be
restarted as well. At this moment it is important not to change other SHDSL port
parameters before you confirm the 2M/4M change with the commit command.
You can change other parameters later, after the module and the modem have
been restarted.
Working with Power Feeding
Warning
Before you activate remote power feeding from the CLI terminal, make sure that
all the cables are properly connected to all the relevant equipment (ASMi-54C/N
modules, PS modules, MPF etc).
When using the ASMi-54C/N module to supply power feeding for remote
modems/repeaters, use the following procedure:
1. Install the module in the chassis.
2. Connect the MPF standalone unit to the PS module, as described in the MPF
Installation and Operation Manual.
3. Connect all the module ports to the prescribed remote equipment.
4. From the CLI terminal, activate remote power feeding as described in
Chapter 5, under SHDSL Ports.
B-118
ASMi-54C Modules
Note
When activating remote power feeding from the ASMi-54C/N module to a remote
S-RPT repeater and/or ASMi-52/52L modem, be careful not to exceed the allowed
ranges (see Table B-18). If the remote equipment is installed beyond the declared
range, the following may occur:
Far-end ASMi-52/52L modem may continuously reset after connecting a
terminal to its serial port

After reconnecting an SHDSL line, SHDSL synchronization may be not stable
enough.
Warning
Before you disconnect/connect cables between ASMi-54C/N modules to remote

modems/repeaters, make sure to disconnect power feeding on the CLI terminal
(no power-feeding).
The list of tasks that can be performed on the ASMi-54C modules and the
Task
Configuring an ASMi-54C module

Selecting an E1 or SHDSL port as

system timing reference
Configuring the SHDSL port

parameters

(ASMi-54C/N)
configure>port>e1

Ports table
Configure the E1-i port

parameters (ASMi-54C/N)
configure>port>e1-i

Ports table

through E1 or E1-i port
configure>port>e1
Configuring the Ethernet port
Configuring the physical layer

parameters for the active PCSs
configure>port>psc
configure>port>e1-i
ASMi-54C Modules
B-119

Task

Configuring flows
flows between Logical MAC port
and Ethernet port
configure>flows
Configurng timeslot assignment
for external and internal E1 ports
(DS0 cross-connect for E1 ports)
configure>cr>ds0

with ASMi-54C/N E1 and E1-i ports,
see Cross-Connect Table in
Chapter 5
Configuring the split assignment

of timeslots, for each external and
internal E1 port

Cross-connecting the E1 port with

a vc12-vt2/vc11-vt1.5 from an
SDH/SONET port

from this e1/e1-i port with
another port of the same type and
configuration
configure>cr>tdm
e1 and e1-i ports are considered to

be of the same type
and external E1 ports
Diagnostics
ASMi-54C/ETH modules do not support loopbacks.
ASMi-54C/N modules have comprehensive test and diagnostics capabilities on
various levels. Availability of loopbacks on remote ASMi modems and their
activation command depend on the remote modem flavor (far-end-type).
Table B-27 lists the loopbacks available on E1, E1-i and SHDSL ports of
ASMi-54C/N module for each far end type. The figure below illustrates the table.
B-120
ASMi-54C Modules

ASMi-54
Line
PCS
5
6
MP-4100
E1
CL
Line
ASMi-52
ASMi-54C/N
Network
Line
PCS
4 E1-i 3
9 V.35
1
0
1
1 E1
1
2
asmi52-e1-dte
ASMi-52
2 E1 1
PCS
1
Line 3
1
4 E1
1
5
asmi52, asmi52-e1-eth
ASMi-52
1
1
7 V.35 8
1
Line 6
1
9 E1
2
0
Figure B-38. Loopback and BER Tests on ASMi-54C/N Module and Remote ASMi Modems
The ASMi-54C/N modules also feature BER tests on E1-i and E1 ports of the
module. On framed ports, the BER Test can be also performed per individual
timeslot.
To perform a BER test, a local loopback must be activated on the corresponding
port/timeslot. Thus BER tests are available with loops 1 and 3 of the local
module. BER tests can also check the remote E1 ports (see loopbacks 7, 12, 15
and 20 in the figure). These tests must be performed from the corresponding
e1-i port of the local module.
Table B-27. Loopback and BER Tests on ASMi-54C/N Module and Remote ASMi Modems
ASMi-54C/N Port
(from which the
loopback is
activated)
Far-end-type
Loopback
No
Loopback Command
local
Per port/
Per timeslot
Far-end Device
Ports Tested
Loopbacks/BERT on the Module

e1
any
P+TS
(+bert)
e1
remote
P+TS
e1-i
local
P+TS
P+TS
(+bert)
e1-i
remote
ASMi-54C Modules
B-121

ASMi-54C/N Port
(from which the
loopback is
activated)
Far-end-type

Loopback
No
Loopback Command
Per port/
Per timeslot
Far-end Device
Ports Tested
Loopbacks/BERT on the Remote Modems

shdsl
asmi-54,
remote-on-remote
SHDSL
e1-i
asmi54-eoc
local-on-remote
E1
remote-on-remote
E1
e1-i
(+bert)
shdsl
asmi52-e1-dte
remote-on-remote
SHDSL
e1-i
local-on-remote serial
Serial
e1-i
10
remote-on-remote serial
Serial
e1-i
11
local-on-remote e1
E1
e1-i
12
remote-on-remote e1
E1
shdsl
asmi52,
13
remote-on-remote
SHDSL
e1-i
asmi52-e1-eth
14
local-on-remote
E1
15
remote-on-remote
E1
e1-i
(+bert)
shdsl
high-speed-muxserial-e1
Odd e1-i
Odd e1-i
16
remote-on-remote
SHDSL
17
local-on-remote
E1
18
remote-on-remote
E1
(+bert)
Even e1-i
19
local-on-remote
Serial
Even e1-i
20
remote-on-remote
Serial
(+bert)
Note 1
Loopbacks can be activated only on connected (set to no shutdown) and

synchronized ports. To check the port status, use show configure port
summary command: Admin status and Oper Status of the port should
display Up.
Note 2 When activating a loopback, a following CLI error may appear: Loopback already
exists in the path. This means that the loopback cannot be activated since one
B-122
ASMi-54C Modules
of the path members is already engaged in another loopback. The path members
are as follows:
SHDSL port
E1-i port connected to this SHDSL port (one or two, depending on the far-end
device)
Repeater connected to this line
Remote modem.
Monitoring
The monitoring tasks supported on each local ASMi-54C port level are listed in the
table below.
Level
Monitored Feature
Path
SHDSL port
Status data
configure>port>
shdsl
Statistics
configure>port>
shdsl
Status data for the Ethernet

port
configure>port>
ethernet
configure>port>
ethernet
statistics
configure>port>
ethernet
Status data for the PCS port
configure>port>
pcs
PCS Ports in Chapter 5
statistics
configure>port>
pcs
PCS Ports in Chapter 5
statistics
configure>port>e1
Displaying E1 Port
Statistics in Chapter 5
Status data
configure>port>e1
Viewing E1 Port Status in
Ethernet port
PCS port
E1 port
Reference

5
Chapter 5
Protection status
E1-i port
statistics
configure>
protection>tdmgroup
configure>port>e1-i
Displaying E1 Port
Chapter 5
ASMi-54C Modules
B-123
Level
Monitored Feature
Path
Reference
Status data
configure>port>e1-i

Chapter 5
Protection status
configure>
protection>tdmgroup

Chapter 5
Troubleshooting
Preliminary Checks

Check the configuration parameters of the remote equipment units.

If after collecting all the relevant alarm information, the problem appears to be
related to the operation of one of the ASMi-54C ports, perform the actions listed
Make sure that no test has been activated on the corresponding ASMi-54C
port. Use the Megaplex-4100 management system to find and deactivate the
For problems related to an E1 port:
Check the link between the user equipment and the corresponding E1
port by activating the remote loopback on the E1 port carrying the
affected traffic.
If the test fails, repeat the test after carefully checking all the
configuration parameters of the module and its ports, and after checking
that the user equipment operates properly when its local loopback is
activated. If the test fails again:
B-124
ASMi-54C Modules
If the user equipment fails its local loopback test, request the local
operator to troubleshoot the user equipment.
If the user equipment passes its local loopback test, check the
connections between the ASMi-54C/N E1 port and the user
equipment, including all the interconnecting cables and any E1
transmission link.
If the problem persists, replace the local ASMi-54C/N module.
Activate a local loopback on the ASMi-54C/N E1 port. If the receive path

of the ASMi-54C/N E1 port synchronizes with its own signal while the
loop is connected, the problem is not within the ASMi-54C/N: however,
there can be a problem at the local equipment connected through the
Megaplex-4100 to the corresponding E1 port, or within the other
Megaplex-4100 I/O module serving that equipment. Check by activating
local loopbacks on the local equipment, and on the Megaplex-4100 I/O
module. Also check local cable connections, and the transmission
equipment providing the link between the other I/O module port and the
local user equipment.
For problems related to an SHDSL port:
Activate a local loopback on the corresponding SHDSL port. If the receive

path of the corresponding ASMi-54C local port operates while the loop is
connected, the problem is not within the ASMi-54C: however, there can
be a problem in the local equipment connected through the LRS-102 to
the SHDSL port, or within the Megaplex-4100 I/O module serving that
equipment. Check by activating local loopbacks on the local equipment,
and on the Megaplex-4100 I/O module. Also check local cable
connections, and the transmission equipment providing the link to the
local user equipment.
B.6
OP-108C Modules

operation of the OP-108C Dual Fiber Multiplexer Modules for 4E1 and Ethernet
for the Megaplex-4100 Next Generation Multiservice Access Node.
OP-108C modules provide cost-effective point-to-point E1 and Ethernet transport
services over fiber-optic links at ranges up to 120 km (74.5 miles) using a RAD
proprietary signal format.
OP-108C modules can also operate in a link with Optimux-108/ Optimux-108L
standalone units offered by RAD.
For information on Optimux-108 or Optimux-108L, refer to the Optimux-108 or
Optimux-108L Installation and Operation Manual, respectively.

In addition to providing optical and E1 links for Megaplex-4100, OP-108C modules
enable packet-based Fast Ethernet services.
Applications
Figure B-14shows a typical corporate service sharing application for OP-108C
modules.
OP-108C Modules
B-125
Figure B-39. Corporate Service Sharing
Features
OP-108C comprises two identical independently-operating sections, identified as
OP A and OP B, each of which is capable of multiplexing four independent internal
E1 data streams and up to 100 Mbps of Ethernet payload for transport over a
fiber-optic link. Each OP-108C section can be connected in a link to another
OP-108C, or to an Optimux-108/108L (the link properties are automatically
adapted to the type of far end equipment). A Megaplex-4100 chassis equipped to
its full capacity (10 modules) with OP-108C modules can thus provide links to 20
standalone units, that is, a total capacity of 80 E1 streams per chassis. The
application shown in Figure B-39 also permits users connected to OP-108C
Ethernet ports access to packet switched networks, such as Internet or
metropolitan Ethernet networks.
The OP-108C capacity is up to four E1 streams and 100 Mbps Ethernet traffic
from each remote unit.
Each OP-108Csection has two optical ports, which can be operated as a
redundant pair, to enhance service availability to critical users. The service
provider can control each standalone unit through the link connecting the unit to
the OP-108C module, and therefore can manage a large number of standalone
units from a central location.
OP-108C has the following interfaces:
B-126
One optical link interface per section (each with two redundant optical ports),
for a total of two links (four ports) per OP-108C
One 10/100 Mbps Ethernet port per section for packet-based services, for a
total of two Ethernet ports per OP-108C.
OP-108C Modules
Optical Link Interfaces

To increase link availability and protect against fiber damage, each link interface
(sections OP A and OP B) has two ports, which operate as a redundant pair with
automatic switch-over in case of a fault.
The link interface subsystem of each OP-108C section includes a link redundancy
switch, and two independent link interfaces (one for each link port) with SFP
sockets.
The link redundancy switch operates as follows:
When only one SFP is installed, only one link port is active. The link
redundancy switch then connects the link mux/demux to this port.
When both SFP are installed, but protection is disabled, the link redundancy
switch connects the link mux/demux to the first port (LINK 1 or LINK 3,
respectively).
When both SFP are installed, and protection is enabled, the link redundancy
switch connects the link mux/demux to the port selected as the primary
(working) port of the corresponding link. When signal loss is detected by the
primary (working) port, the switch transfers the traffic to the other
(secondary) port.
Each link interface performs the following functions:
The transmit path converts the link data and the associated clock signal
provided by the link mux/demux to the signals needed to drive the SFP that
provides the physical interface of each port, for transmission to the far end
equipment.
The receive path recovers the link data stream received from the far end
equipment, and the associated clock, and provides the data and clock to the
link mux/demux.
The link interfaces accept a wide range of SFPs, and the performance depends on
the installed SFP model. RAD offers a wide range of SFPs, to optimally meet a
wide range of system requirements. The fiber-optic interfaces can operate over
62.5/125 micron multi-mode, or 9/125 micron single-mode fibers (typical
attenuation of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm). The offered SFPs include models that need a single fiber instead of the
customary two fibers (for example, WDM models SF1 and SF2 operating at two
different wavelengths, or the SF3 model with SC/APC (angled polished connector)
that operates at a single wavelength).
Note
It is strongly recommended to order OP-108C with RAD SFPs installed: this will
own SFPs into OP-108C modules, RAD cannot guarantee full compliance to
product specifications when using non-RAD SFPs, and cannot be held responsible
for any damage that may result if non-compliant transceivers are used. In
particular, users are advised to use only agency approved SFPs that comply with
the local laser safety regulations for Class 1 laser products.
Table B-28 provides information on the characteristics of the SFPs offered by
RAD, together with typical maximum ranges (calculated assuming typical fiber
OP-108C Modules
B-127
attenuations of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm, and a 3-dB margin).
All the fiber-optic interface options offer high performance and have a wide
dynamic range, which ensures that the receiver will not saturate even when using
short fiber-optic cables (saturation is caused when the optical power applied to
the receiver exceeds its maximum allowed input power, and results in very high
bit error rates).
Table B-28. Link Port Interface Characteristics

Module
Name
Transmitter
Type and
Wavelength
[nm]
Connector Fiber Type

Type
Typical Output
Power
Receiver
Sensitivity
Typical Range
[dBm]
[dBm]
[km]
SFP-1
LED, 1310
LC
62.5/125
Multimode
-18
-31
6.5
SFP-2
Laser, 1310
LC
9/125 Single mode -12
-31
38
23.6
SFP-3
Long haul
laser, 1310
LC
-34
70
43.4
SFP-4
Long haul
laser, 1550
LC
-34
120
74.5
SFP-10a Laser WDM,

LC
Tx 1310, Rx
1550

(single fiber)
-30
40
24.8
SFP-10b Laser WDM,

LC
Tx 1550, Rx
1310

(single fiber)
-30
40
24.8
SFP-18A Tx 1310, Rx LC
1550
9/125 single mode -2

(single fiber)
-30
60
37.3
SFP-18B Tx 1550, Rx LC
1310
9/125 single mode -2

(single fiber)
-30
60
37.3
SFP-24
62.5/125
Multimode
-31
6.5
VCSEL
LC
-7
[miles]
4.0
4.0
E1 Services
E1 services in the OP-108C module are provided via the internal E1 ports
connected to the Megaplex-4100 TDM bus.
Zero suppression over the line is HDB3.
B-128
OP-108C Modules
Cross-Connections
The OP-108C modules support both DS0 and TDM cross-connection, selectable at
the level of the individual E1 port:

cross-connect enables connecting payload between E1 to T1 ports. When an
E1 or T1 port of the far end unit is connected to RAD equipment, it is
possible to assign a dedicated timeslot to inband management of the RAD
equipment.

External Ethernet Port Interfaces

The external Ethernet ports have 10/100Base-Tx interfaces capable of
specified. The Ethernet interfaces are terminated in RJ-45 connectors. In addition
to auto-negotiation, MDI/MDIX polarity and cross-over detection and automatic
cross-over correction are also supported. Therefore, these ports can always be
connected through a straight (point-to-point) cable to any other type of
10/100Base-T Ethernet port (hub or station).
Ethernet Services
to 100 Mbps.
The 2-port 10/100BaseT interface includes a built-in flow classification engine
that performs single VLAN tagging according to IEEE 802.1Q and 802.1p. The
interface supports autonegotiation for plug-and-play Ethernet connectivity and
complies with IEEE 802.3/Ethernet V.2 standards.
The Ethernet switch enables the forwarding of traffic between each OP-108C
Ethernet port and the corresponding OP-108C link, provided the link is connected
to another OP-108C, or to an Optimux-108/108L with Ethernet ports. Ethernet
traffic cannot be forwarded to a link connected to an Optimux-108 that does not
have Ethernet ports (refer to the corresponding Optimux Installation and
Operation Manual for details on the capabilities of the various Optimux models). In
addition, the Ethernet switch can transfer traffic from the CL or another
Megaplex-4100 module with Ethernet interface to the OP-108C link(s).
OP-108C Modules
B-129
Two types of ports can be defined on an OP-108C module external and internal
(bridge) Ethernet ports:
Each Ethernet physical interface can be defined as a bridge port.
A bridge port can be defined on each external link (actually, this bridge port is
configured on an internal Ethernet port, which supports the Ethernet traffic
to the OP-108C external link). These bridge ports are named Int-Eth1 and
Int-Eth2 and designed as <slot><port><tributary) (see Internal Ethernet Port
Numbering below).
Note that Int-Eth1 is served by the mux-eth-tdm 1 and mux-eth-tdm 2 ports,

and Int-Eth2 is served by the mux-eth-tdm 3 and mux-eth-tdm 4 ports.
Thus, each OP-108C has two bridge ports defined on Ethernet ports, and two
bridge ports defined on the external links.
defining flows.
The customers edge traffic accepted by OP-108C external and internal Ethernet
ports is directed to other interfaces that can transfer the traffic to the transport


The total maximum Ethernet traffic that can be transferred via the backplane for
aggregation (from one or two ports) is 100 Mbps for the entire OP-108C module.
Mapping of E1 Traffic over SDH

The internal E1 ports can also be connected to SDH links, which permits using the
Megaplex-4100 as an SDH terminal multiplexer (TM). Using the
topologies, enables dropping part of the SDH link payload at a certain location,
and possibly inserting other payload.
OP-108Cmodules allow direct transparent mapping of unframed E1 links over SDH
in a transparent mode (this feature is also called transparent clocking).
Framed payload can be mapped to SDH links in two stages: first via ds0 crossconnect to E1-i ports of CL.2 modules and then to desired SDH containers.
B-130
OP-108C Modules
Management
OP-108C supports the transfer of management traffic, inband, for both TDM and
A dedicated management timeslot can be configured on each internal E1 port

dedicate timeslots.
Inband management can be carried over Ethernet ports configured on

OP-108C, which are included in the management flow configured by the user
(using the dedicated management VLAN configured for the Megaplex-4100
host).
An OP-108C section connected in a link to an Optimux-108/108L enables inband

management of the attached Optimux-108 (this traffic is carried within the TDM
payload transferred through the link, in an Optimux-108-compatible format). This
enables fully automatic, plug-and-play, setting up of the attached Optimux
standalone device. Moreover, to prevent configuration conflicts, the configuration
data supplied via the OP-108C overrides the internal configuration data of the
remote Optimux unit as soon as the link to the unit is established. The remote
Optimux can however be controlled by means of a supervision terminal directly
attached to its control connector, as long as the remote Optimux is connected to
the OP-108C.
Interconnected OP-108C modules located in different Megaplex-4100 systems
must be managed separately (inband management between two OP-108C
modules is not possible).
Protection for Internal E1 Ports

The internal E1 ports of OP-108C feature dual-cable protection with parallel
transmission, for ports both on the same module and on different modules. A
special TDM ring protection functionality is used for the ports participating in a
Chapter 5.
Protection for Optical Links

In addition, OP-108C supports optical link protection. This kind of protection is
available for ports on the same module only.
Each link (section) has two ports that form a protection group. Ports mux-ethtdm 1 and mux-eth-tdm 3 serve as primary ports. Their protection partners are as
follows:
mux-eth-tdm 2 is always protection partner for mux-eth-tdm 1 (OP A section)
mux-eth-tdm 4 is always protection partner for mux-eth-tdm 3 (OP B section)
Each of the two ports in the protection group (mux-eth-tdm 1 and mux-eth-tdm
2 for OP A, mux-eth-tdm 3 and mux-eth-tdm 4 for OP B) is connected through a
separate cable to the remote equipment, and both ports transmit in parallel the
same data. Therefore, an OP-108C, or an Optimux-108/108L unit configured for
protection can independently select an active port, and does not have to flip to
synchronize its selection with those of the local OP-108C.
OP-108C Modules
B-131
The fault conditions that cause switching to backup are loss of signal, loss of
frame alignment, reception of AIS or a link fault (for example, removal or failure
of the corresponding SFP).
The link redundancy mode is revertive: the switch will automatically flip back to
the primary link immediately after it returns to normal operation.
Timing
The OP-108C internal timing subsystem generates the clock and timing signals
required by the link transmit paths of the module.
The link receive paths of the module use the clock signals recovered from the
corresponding received link signal.
The OP-108C modules can also provide timing reference signals derived from a
selected E1 stream for the nodal Megaplex-4100 timing subsystem.
OP-108C transmit timing can be locked to the Megaplex-4100 nodal timing.
Module Panels
The OP-108C module occupies one I/O slot in the Megaplex-4100 chassis. The
panels are shown in Figure B-40.
B-132
OP-108C Modules
OP-108C
LINK/
ACT
O
P
EA
T
HO
P
B
100
AIS
1
O
P
A
2
LASER
CLASS
1
O
P
B
L
I
N
3 K
LOSS
Figure B-40. OP-108C Panel

The module panels have an Ethernet interfacing section in the middle, and a link
interfacing section at the bottom.
Ethernet Interfacing Section

The Ethernet interfacing section includes two Ethernet ports, designated ETH 1
and ETH 2. Port ETH 1 serves the OP A section of the OP-108C, and port ETH 2
serves the OP B section.
Each port is terminated in an RJ-45 connector with integral status indicators.
Link Interfacing Section

The link interfacing section includes two pairs of ports:
The ports designated LINK 1 and LINK 2 serve the OP A section.
The ports designated LINK 3 and LINK 4 serve the OP B section.
The ports are equipped with SFPs. Each port has its own set of status indicators.
OP-108C Modules
B-133
LED Indicators
Link Indicators
Each LINK status indicator operates as follows:
AIS (yellow)
Lights when AIS is detected on the corresponding link.
LOSS (red)
Loss of signal indicator, is always Off when the

corresponding link port operates normally.
Lights when the corresponding link port reports loss of
signal.
Ethernet Indicators
The functions of each ETH port status indicator are as follows:
LINK/ACT (yellow)
Lights when the link integrity signal is detected by the

corresponding port (normal operating condition the port
is connected to an active LAN, and the Ethernet link is up).
Flashes in accordance with the transmit and/or receive
activity on the corresponding port.
OFF when the Ethernet link is down.
100 (green)
Lights when the port operating rate is 100 Mbps.

OFF when the port operating rate is 10 Mbps.
General
Function
Dual Fiber Multiplexer Modules for 4E1 and Ethernet
Compatibility
Each section can be connected to:

Another OP-108C section
Optimux-108/108L standalone unit with or without
an Ethernet port
Internal E1 Ports Type and Bit Rate
B-134
Number
Line Code
HDB3
Compliance

E bit)
OP-108C Modules
Framing
Optical Link
Number of Links


One link per section

2 links per slot
Number of Ports per Link 2, with user-configured redundancy

Type
Optical SFP-based, RAD proprietary
Timing
Transmit path: internal source

Receive path: recovered from received line signal
Indicators per Link

AIS (yellow)
Lights when AIS is received (only for operating

opposite Optimux-108/108L without ETH)
LOSS (red)
On: loss of incoming signal
Note: Both LEDs are on if no SFP is inserted.
Ethernet
Interfaces
Number of Ports
Maximum Frame Size
1600 bytes
Type
10/100Base-Tx with user-configurable

autonegotiation
Connectors
Shielded RJ-45
Port Throughput
100 Mbps
IEEE 802.3, IEEE 802.3ah
Indicators (per Ethernet

port)
LINK/ACT (yellow)
On (yellow): link is up
Off: link is down
Blinking: frames are transmitted/received
100 (green)
On: port operates at 100 Mbps

Off: port operates at 10 Mbps
Diagnostics
Local and remote loopbacks on the local optical link
OP-108C Modules
B-135
Local and remote loopbacks on the remote optical

link
Local and remote loopbacks on the module internal
E1 ports (per port and per timeslot)
Local and remote loopbacks on remote E1 ports (per
port)
Performance
Monitoring
E1 Ports
Ethernet Ports
As per RMON-RFC2819
Power
Consumption
8W
Configuration

system
Environment
-10C to 55C (14F to 131F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
Warning
Caution

The OP-108C modules contain components sensitive to electrostatic discharge
OP-108C modules may be installed in an operating chassis (hot insertion).
Note
B-136
OP-108C software can be updated by downloading from the CL module.

Therefore, if the OP-108C module is not yet loaded with the required software
OP-108C Modules
Before installing OP-108C modules, it may be necessary to install, or replace,

SFPs. OP-108C modules have four installation positions for SFPs, identified as
LINK 1 to LINK 4:
OP-108C modules equipped with RAD-supplied SFP plug-in modules comply with
Warning
OP-108C modules are shipped with protective covers installed on all the optical
SFPs installed on OP-108C modules may be equipped with a laser diode. In such
Warning
For your safety:

Installing an SFP
Warning
OP-108C Modules
B-137
connectors.
Note
To install the SFP:
as illustrated in the figure below.
Note

OP-108C module, and from the SFP electrical connector.
7. Orient the SFP as shown in the figure, and then insert the rear end of the SFP
into the module socket.
Replacing an SFP
SFPs, only the traffic on the affected optical link is disrupted (the other optical
link can continue to carry traffic).
To replace an SFP:
B-138
OP-108C Modules
The OP-108C module starts operating as soon as it is inserted in an operating

chassis.
Warning
To install an OP-108C module:

16. Insert the OP-108C module in its chassis slot and slide it in as far as possible.
17. Secure the OP-108C module by tightening its two fastening screws.

Connecting the Ethernet Ports

Each OP-108C ETH port has a 10/100BASE-TX Ethernet interface terminated in an
RJ-45 connector. The port supports the MDI/MDIX crossover function, and

Pin
Designation
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
Not connected
Not connected
To connect cables to the OP-108C Ethernet ports:
Connect the prescribed cable to the corresponding connector, ETH 1 or

ETH 2.
OP-108C Modules
B-139
Connecting to LINK Ports

Chapter 2.
Identify the optical fibers intended for connection to each optical port of this
Pay special attention to SFPs that require a single fiber:
SFP option SF3 uses SC/APC (SC/Angled Polished Connector). Make sure to
use only patch cords and fibers terminated in SP/APC connectors along the
whole optical transmission path (such connectors are usually green).
SFP with WDM option SF1 is intended for operation in a link with SFP with
WDM option SF2. Make sure to check before connecting fibers.
To connect cables to the OP-108C LINK ports:
Connect each prescribed fiber to the corresponding LINK connector.

transmitter output is at the left-hand side.
Normal Indications
Optical Links
The status of each OP-108C LINK port is indicated by two separate indicators.
established, both indicators of a LINK port are off.
LOSS indicator lights in red. The indicator turns off as soon as the link with the
remote equipment is established.
Ethernet Ports

Configuring the Local Links
You can configure the local links even when no far end device is connected to an
OP-108C section.
Only mux-eth-tdm 1 and mux-eth-tdm 3 need to be configured. If you want to
set protection on these ports, mux-eth-tdm 2 and mux-eth-tdm 4 ports must be
B-140
OP-108C Modules
set to no shutdown and configured for protection as described in Chapter 7,
Configuring TDM Group Protection.
Internal E1/T1 Port Numbering

Tributary E1/T1 ports of Megaplex Optimux modules are actually internal ports but
of other type than E1-i/T1-i.
OP-108C has 8 internal E1/T1 ports, 4 serving section OP A and another 4 serving
section OP B. These ports are numbered not 1 to 8, but according to the primary
mux-eth-tdm port of the section: 1 for section OP A and 3 for section OP B.
Serving section OP A: <slot>/1/1, <slot>/1/2, <slot>/1/3, <slot>/1/4
Serving section OP B: <slot>/3/1, <slot>/3/2, <slot>/3/3, <slot>/3/4
Tributaries <slot>/2/x and <slot>/4/x dont exist.
Internal Ethernet Port Numbering

OP-108C has 2 internal Ethernet ports numbered according to the primary muxeth-tdm port of the section: 1 for section OP A and 3 for section OP B.
Serving section OP A: <slot>/1/1
Serving section OP B: <slot>/3/1.
Configuring Remote Equipment Ports

You can configure the remote equipment ports when the far end device is any
standalone Optimux unit, but not an OP card.
Configuring the remote Optimux is described in Configuring the Remote Optimux
under Configuring Optical Link Parameters and Accessing the Remote Unit in
Chapter 5.
Refer also to the corresponding Optimux-108 or Optimux-108L Installation and
Operation Manual for a description of the Optimux capabilities, and for specific
configuration instructions.
You can configure a remote Ethernet port only when the corresponding OP-108C
section is connected to an Optimux-108/108L unit that has an Ethernet port.
Configuring TDM Group/Ring Protection

OP-108C feature TDM group and ring protection for E1 ports and TDM group
protection for optical links (mux-eth-tdm ports).
To save duplication of configuration parameters, all the e1/mux-eth-tdm port
been updated. However, you must set the protection port to no shutdown
before starting the configuration.
Internal E1 Ports
The protection partners for internal E1 ports of OP-108C modules can be located
either on the same module or on another module, and can be any of the
OP-108C Modules
B-141
following types: E1, internal E1 ports of CL or OP modules, or internal E1 ports of

M8SL or ASMi-54C/N modules.
When the other port in a protection group with an internal port of a CL.2 module,
only the dual-cable-tx protection mode can be used, and ring protection is
unavailable. CL.2 internal ports may also use path protection, so this type of
protection is not necessary for internal ports included in another protection
scheme.
To avoid configuration errors, before starting the configuration of the protection
parameters, make sure that the other port does not carry traffic.
Optical Links
Link protection is effective only when OP-108C is connected to a standalone
Optimux with dual links. Make sure to connect link A of the local
OP-108C to link A of the far end, and local link B to far end link B.
The protection partners of each link (mux-eth-tdm 2 for the OP A section, or
mux-eth-tdm 4 for the OP B section) are automatically configured with the same
parameters as mux-eth-tdm 1 and mux-eth-tdm 3, respectively. To activate
protection, mux-eth-tdm 2 and mux-eth-tdm 4 ports must be set to no
shutdown and configured for protection as described in Chapter 7, Configuring
TDM Group Protection.

For mux-eth-tdm ports, the wait-to-restore time is always 0.
The list of tasks that can be performed on the OP-108C modules and the
Task
Configuring an OP-108C module

Configuring the optical link
Selecting an internal E1 Port as

Configuring the internal E1 port

parameters
configure>port>e1
Comments and Reference
Ports, table, under E1 Ports in
Chapter 5
B-142
OP-108C Modules
Task
Configuring inband management

through E1 port
configure>port>e1
Configuring the external Ethernet

ports
Configuring the internal Ethernet

ports


for E1 ports (DS0 cross-connect
for E1 ports)
configure>cr>ds0

with OP-108C ports, see CrossConnect Table in Chapter 5

of timeslots, for each internal E1
port


a vc12/vc11 from an SDH port

configuration
configure>cr>tdm

<slot>/<port>

be of the same type
Configuring flows
flows between Logical MAC and
Ethernet port
configure>flows
E1/T1 ports
Configuring protection for optical

links (mux-eth-tdm ports)
Configuring the remote Optimux

Acessing the remote Optimux
remote

optical link
Configuring the Remote Optimux in
remote
Chapter 5
OP-108C Modules
B-143
Task

user Ethernet port
remote
Chapter 5
Controlling the rate of the ingress
frames from the remote Optimux
device: frames that are over the
ingress rate limit are dropped
configure>qos, then
Configuring Bandwidth Profiles in
Chapter 5
remote

management Ethernet port
remote
Chapter 5
Chapter 5
configure>port>mng-eth
E1 ports
remote
Chapter 5
configure>port>e1
Diagnostics
OP-108C modules have comprehensive test and diagnostics capabilities that
include local and remote loopbacks on each link interface, on each internal E1
port, and on selected timeslots of any E1 port.
When connected in a link with a standalone Optimux-108/108L, the management
system controlling the OP-108C modules can also activate on the standalone unit
the remote link loopback, and local and remote loopbacks on E1 ports.
The OP-108C modules support diagnostic functions at the following levels:
OP-108C link level
Remote unit link level
OP-108C Internal E1 port and timeslot levels
Remote unit E1 port level.
The loopbacks supported on each level are described in the table below.
Level
Name and Description
Optical link of
local module
B-144
Local loopback on local OP108C: this loopback returns the

OP-108C link transmit signal to
the input of the link receive
path
OP-108C Modules
Path and command
Reference
<slot>/<port 1 or 3>
Testing Optical
Links in Chapter 5
loopback local

Level
Optical link of
remote unit
Path and command
Reference
Remote loopback on local

OP-108C: this loopback returns
the OP-108C link receive signal
toward the remote equipment
(Optimux-108/108L or OP108C)
<slot>/<port 1 or 3>
Testing Optical
Links in Chapter 5
Local loopback on remote

Optimux-108: this loopback
returns the link receive signal
of the far end unit to the input
of the link receive path
<slot>/<port 1 or 3> remote
Testing Optical
Links in Chapter 5
configure port mux-eth-tdm <port

of remote unit 1 or 2> loopback
local
Only when duration

is limited (not
infinite)
<slot>/<port 1 or 3> remote
Testing Optical
Links in Chapter 5
Remote loopback on remote

of the far end unit toward the
local OP-108C
Internal E1
port of local
module: per
port and per
timeslot
E1 port of
remote unit
loopback remote

remote
Local loopback: this loopback

returns the internal E1 port
transmit signal to the input of
the port receive path
config>port>e1(<slot>/<mux-ethtdm port 1 or 3> /<e1 port

1..4>)#
Remote loopback: this loopback

receive signal toward the
remote equipment
(Optimux-108/108L)
config>port>e1(<slot>/<mux-ethtdm port 1 or 3> /<e1 port

1..4>)#

returns the E1 port transmit
signal to the input of the port
receive path
loopback local [time-slot <1..31>]
loopback remote [time-slot

<1..31>]
config>port>mux-eth-tdm
(<slot>/<port 1 or 3> remote
configure port e1 <remote unit
e1 port 1..4>
configure port t1 <remote unit t1
port 1..4>
loopback local

returns the remote Optimux E1
port receive signal toward the
corresponding OP-108C internal
E1 port.
(<slot>/<port 1 or 3> remote
e1 port 1..4>
loopback remote
OP-108C Modules
B-145
Note
A supervision terminal or other manager connected to a remote

Optimux-108/108L can also activate loopbacks on the local
OP-108C.
The Ethernet protocol does not allow looping back frames, and therefore all the
OP-108C loopbacks affect only the TDM signal paths: Ethernet payload is not
affected, and continues to flow through the link even when a link loopback is
activated.
Each OP-108C section (OP A and OP B) operates independently, and therefore
the diagnostic functions are independently activated on each section.
Monitoring
The monitoring tasks supported on each OP-108C port level are listed in the table
below.
Level
Monitored Feature
Path
Reference
Local OP-108C Link
configure>port>
mux-eth-tdm>
Viewing Optical Link

Status Information in
Chapter 5
configure>
protection>tdmgroup
Status data for the external

physical port
configure>port>
ethernet
Ethernet Ports in
statistics
configure>port>
ethernet
Ethernet Ports in
Local OP-108C
internal Ethernet
port
statistics
configure>port>
ethernet
Ethernet Ports in
Local OP-108C
internal E1 port
statistics
configure>port>e1
Displaying E1 Port
Protection status
Local OP-108C
external Ethernet
port
Chapter 5
Chapter 5 (electrical
10/100BaseT ports only)
Chapter 5
Chapter 5 (tributary)
(tributary)
Status data
configure>port>e1

Protection status
B-146
OP-108C Modules
configure>
protection>tdmgroup

Chapter 5

Level
Monitored Feature
Path
Reference
Protection status
configure>
protection>tdmgroup

Chapter 5
The remote equipment status cannot be viewed through OP-108C links.
Troubleshooting
Preliminary Checks


If, after collecting all the relevant information, the problem appears to affect all
the internal E1 ports of an OP-108C section, perform the actions listed below
until the problem is corrected:

OP-108C link. Use the Megaplex-4100 management system to find the active
test loopback and deactivate it.
Activate the local loopback on the corresponding OP-108C link. If the

indicators of the corresponding local link ports turn off while the loop is
connected and the local E1 user equipment starts operating normally, the
Quickly check the link to the remote equipment unit by activating the remote
port loopback at the remote unit. If the link operates properly, the indicators
of the corresponding local link ports turn off while the loop is connected and
the local E1 user equipment starts operating normally.
network, or with the OP-108C module. Repeat the test after carefully
to the operation of one of the OP-108C internal E1 ports, perform the actions
listed below, until the problem is corrected:
OP-108C Modules
B-147

OP-108C internal E1 port. Use the Megaplex-4100 management system to
find and deactivate the active test or loopback.
Activate the local loopback on the corresponding OP-108C internal E1 port. If

the local user E1 equipment does not synchronize while the loopback is
connected, check cable connections to the user equipment, and the user
equipment itself.
Quickly check the link to the remote equipment unit by activating the remote
E1 port loopback at the remote unit.
If the local user E1 equipment synchronizes while the loop is connected,

the problem is at the remote equipment unit: in this case, activate the
local E1 port loopback at the remote unit. If the remote user E1
equipment does not synchronize while the loopback is connected, check
cable connections to the remote user equipment, and the user equipment
itself.
network, or with the OP-108C module. Repeat the test after carefully
checking all the configuration parameters of the module and its ports,
and then perform the checks described above for link problems. If the
problem persists, replace the OP-108C module and check again.
B.7
OP-34C Modules

operation of the OP-34C 16-channel E1 and Ethernet multiplexer modules for the
Megaplex-4100 Next Generation Multiservice Access Node.
OP-34C modules provide cost-effective point-to-point E1 transport over fiberoptic links at ranges up to 110 km (68.3 miles); unused bandwidth on the links
can be assigned to Ethernet transport services.
OP-34C serves remote Optimux-134 fiber-optic standalone units, which are
configured to operate in the Optimux-34 mode.
Product Options
OP-34C can be ordered with one of the following Ethernet interfaces:
10/100BASE-TX copper (UTP) interface terminated in an RJ-45 connector
Socket for field-replaceable Fast Ethernet SFP optical transceiver.
Applications
Each OP-34C module can operate in a link with a standalone Optimux-134 fiberoptic multiplexer, available from RAD. A Megaplex-4100 chassis equipped to its
full capacity (10 modules) with OP-34C modules can thus provide links to 10
B-148
OP-34C Modules
standalone units, that is, a total capacity of 160 E1 streams per chassis. Part of
the link capacity can be assigned to Ethernet traffic.
Figure B-42 shows a typical application for OP-34C modules.
Figure B-42. Typical OP-34C Application

In this application, remote users connected via E1 links to Optimux-134
standalone units, are groomed over SDH/SONET links, with local dropping and
cross-connecting.
When not all of the link bandwidth is used for E1 traffic, Ethernet traffic can also
be carried: Ethernet traffic received from remote LANs attached to the
Optimux-134 can be switched over Ethernet flows toward the CL modules, and
groomed via a single GbE port towards a router, for access to packet switched
networks, such as Internet or metropolitan Ethernet networks.
Features
OP-34C is capable of multiplexing independent E1 data streams and Ethernet
payload for transport over a common link. OP-34C has the following interfaces:
16 internal E1 (2.048 Mbps) ports for OP-34C ports for TDM services
One 10/100 Mbps Ethernet port for packet-based services
One link interface (with two ports, for redundancy) using a RAD proprietary
format, operates at 34.386 Mbps (the E3 rate).
When not all the E1 ports are needed, the unused link bandwidth can be used to
carry Ethernet traffic (see TDM Services below for details), and vice versa if
you specify the Ethernet throughput rate, a corresponding number of E1 ports
will be automatically disabled to reserve the corresponding bandwidth for
Ethernet traffic.
OP-34C can also operate in a link with an OP-34C module installed in another
Megaplex or LRS-102 chassis.
OP-34C Modules
B-149
In addition to providing optical and E1 links for Megaplex-4100, OP-34C modules

enable packet-based Fast Ethernet services.
For information on Optimux-134 refer to the Optimux-134 Installation and
Operation Manual.
Optical Link Interfaces

The link interfaces accept a wide range of SFPs, and therefore the performance
depends on the installed SFP model. RAD offers a wide range of SFPs, to
optimally meet a wide range of system requirements. The fiber-optic interfaces
can operate over 62.5/125 micron multimode, or 9/125 micron single-mode fibers.
The offered SFPs also include models that need a single fiber instead of the
customary two fibers (for example, WDM models). Refer to the OP-34C datasheet
for a list of supported SFPs.
Note
It is strongly recommended to order OP-34C with RAD SFPs installed: this will
own SFPs into OP-34C modules, note that RAD cannot guarantee full compliance
to product specifications when using non-RAD SFPs, and 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 SFPs that
comply with the local laser safety regulations for Class 1 laser products.
TDM Services
E1 services in the OP-34C module are provided via the internal E1 ports
connected to the Megaplex-4100 TDM bus.
Zero suppression over the line is HDB3.
The OP-34C internal E1 ports provide a connection point for timeslots (or entire
data streams, depending on the cross-connection mode) that are routed to an
OP-34C module via the TDM buses of the Megaplex-4100 chassis, under the
control of the CL modules. The TDM traffic routed to each internal E1 port (an E1
data stream) is internally directed to the link interface, for transport to the far
end equipment (which can be either an Optimux-134 standalone unit with active
Ethernet user port, or an OP-34C installed in another chassis).
When connecting to an Optimux-134 with V.35 port, the E1 traffic of port 16 is
transferred transparently to the V.35 port of the standalone unit.
The user can select the number of E1 streams transported over the link, up to a
maximum of 16 streams. Link bandwidth not used for E1 transport can be
assigned to the transport of Ethernet traffic toward the far end equipment, in
accordance with the options identified in Figure B-43.
As illustrated in Figure B-43, bandwidth can be released to Ethernet traffic in
multiples of 8 Mbps for OP-34C, i.e., in chunks equivalent to the bandwidth
B-150
OP-34C Modules
occupied by 4 contiguous internal E1 ports, always starting with internal E1 port

1. For example:
If you configure the Ethernet throughput to 8 Mbps for OP-34C, the internal
E1 ports 1 to 4 will be automatically disabled
If you need 6 internal E1 ports for E1 traffic and you enable ports 11 to 16,
then ports 9 and 10 are also reserved, and the bandwidth available to
Ethernet traffic is 16, respectively 12 Mbps
If internal E1 port 3 is enabled, even if it is the only port enabled, all the
internal E1 ports are automatically reserved for E1 traffic, and no bandwidth
is available for Ethernet traffic.
Figure B-43. OP-34C Link Utilization Options

Each data stream is transparently transferred over the link (OP-34C also supports
unframed streams, and streams with proprietary framing). Moreover, the original
stream timing can also be transparently transferred, and therefore the various
streams do not need to be synchronized to a common source.
To increase link availability and protect against fiber damage, the link interface
has two ports, which operate as a redundant pair with automatic switch-over in
case of a fault.
The optical ports are equipped with hot-swappable SFPs. RAD offers SFPs that
cover a wide range of transmission requirements, for use over multimode,
single-mode, and single-mode over single fiber; OP-34C can also accept SFPs with
copper interface.
Cross-Connections
OP-34C Modules
B-151
The OP-34C modules support both DS0 and TDM cross-connection, selectable at
the level of the individual E1 port:

timeslots, and therefore relevant only when using a framed mode. When an
E1 port of the far end unit is connected to RAD equipment, it is possible to
assign a dedicated timeslot to inband management of the RAD equipment.

External Ethernet Port Interfaces

The external Ethernet port has an 10/100Base-Tx interface capable of
specified. The Ethernet interface is terminated in RJ-45 connectors. In addition to
auto-negotiation, MDI/MDIX polarity and cross-over detection and automatic
cross-over correction are also supported. Therefore, these ports can always be
connected through a straight (point-to-point) cable to any other type of
10/100Base-T Ethernet port (hub or station).
Ethernet Services
to 100 Mbps.
The single-port 10/100BaseT interface includes a built-in flow classification
engine that performs single VLAN tagging according to IEEE 802.1Q and 802.1p.
The Ethernet switch enables the forwarding of traffic between the OP-34C
Ethernet port and the OP-34C link, provided the link is connected to another OP34C, or to an Optimux-134 with Ethernet ports. Ethernet traffic cannot be
forwarded to a link connected to an Optimux-134 that does not have Ethernet
ports (refer to the corresponding Optimux Installation and Operation Manual for
details on the capabilities of the various Optimux models). In addition, the
Ethernet switch can transfer traffic from the CL or another OP-34C module with
Ethernet interface to the OP-34C link(s).
Two types of ports can be defined on an OP-34C module external and internal
(bridge) Ethernet ports:
B-152
The Ethernet physical interface can be defined as a bridge port.
A bridge port can be defined on the external link (actually, this bridge port is
configured on an internal Ethernet port, which supports the Ethernet traffic
to the OP-34C external link). This bridge port is named Int-Eth1 and designed
as <slot><port><tributary) (where port=1 and tributary=1, see Internal
Ethernet Port Numbering below).
Note that Int-Eth1 is served by the mux-eth-tdm 1 and mux-eth-tdm 2 ports.
OP-34C Modules
Thus, each OP-34C has one bridge port defined on the Ethernet port, and one
bridge ports defined on the external link.
defining flows.
The customers edge traffic accepted by OP-34C external and internal Ethernet
ports is directed to other interfaces that can transfer the traffic to the transport

ASMi-54C modules, which determine the Ethernet (packet) physical layer

The total maximum Ethernet traffic that can be transferred via the backplane for
aggregation (from one or two ports) is 100 Mbps for either the OP-34C module.
Capacity
The connection between the Ethernet switching subsystem of the OP-34C
module and the Ethernet handling subsystem of the CL modules has a bandwidth
of 100 Mbps. This bandwidth is used to carry traffic toward other modules
installed in the chassis, and traffic from other modules which is directed through
the internal Ethernet port toward the Optimux-134.
The traffic capacity toward the far end unit depends on the bandwidth reserved
for Ethernet traffic, as illustrated in Figure B-43: each group of 4 unused ports
releases, for Ethernet traffic, 8 Mbps. Therefore, the maximum link Ethernet
bandwidth available on OP-34C is 32 Mbps when no TDM traffic is transported,
and decreases to 0 (no Ethernet traffic) when 13 or more E1 ports are in use.
To protect against congestion, flow control can be independently activated for
the external and internal Ethernet port. In addition, the ingress rate of the
internal Ethernet port can be limited to a user-specified value (frames exceeding
the ingress rate limit are quietly discarded).
Mapping of E1 Traffic over SDH

The internal E1 ports can also be connected to SDH links, which permits using the
Megaplex-4100 as an SDH terminal multiplexer (TM). Using the
OP-34C Modules
B-153
topologies, enables dropping part of the SDH link payload at a certain location,
and possibly inserting other payload.
OP-34C modules allow direct transparent mapping of unframed E1 links over SDH
in a transparent mode (this feature is also called transparent clocking).
Framed payload can be mapped to SDH links in two stages: first via ds0 crossconnect to E1-i ports of CL.2 modules and then to desired SDH containers.
Management
OP-34C enable inband management of Optimux-134 through the interconnecting
links, therefore the OP-34C management system can also manage the far end
standalone units.
OP-34C supports the transfer of management traffic, inband, for both TDM and
A dedicated management timeslot can be configured on each internal E1 port

dedicate timeslots.
Inband management can be carried over Ethernet ports configured on

OP-34C, which are included in the management flow configured by the user
(using the dedicated management VLAN configured for the Megaplex-4100
host).
Moreover, to prevent configuration conflicts, the configuration data supplied via

the OP-34C overrides the internal configuration data of the remote Optimux-134
unit as soon as the link to the unit is established (the remote Optimux-134 can
however be controlled by means of a supervision terminal directly attached to its
control connector), as long as the remote Optimux is connected to the OP-34C).
Interconnected OP-34C modules located in different Megaplex-4100 systems
must be managed separately (inband management between two OP-34C modules
is not possible).
Protection for Internal E1 Ports

The internal E1 ports of OP-34C feature dual-cable protection with parallel
transmission, for ports both on the same module and on different modules. A
special TDM ring protection functionality is used for the ports participating in a
Chapter 7.
Protection for Optical Links

In addition, OP-34C supports optical link protection. This kind of protection is
available for ports on the same module only.
The two links form a protection group. Port mux-eth-tdm 1 serves as primary
ports. Its protection partner is mux-eth-tdm 2.
Each of the two ports in the protection group is connected through a separate
cable to the remote equipment, and both ports transmit in parallel the same
data. Therefore, an OP-34C, or an Optimux-134 unit configured for protection
B-154
OP-34C Modules
can independently select an active port, and does not have to flip to synchronize
its selection with those of the local OP-34C.
The fault conditions that cause switching to backup are loss of signal, loss of
frame alignment, reception of AIS or a link fault (for example, removal or failure
of the corresponding SFP).
The link redundancy mode is revertive: the switch will automatically flip back to
the primary link immediately after it returns to normal operation. The link
redundancy mode is revertive: the switch automatically flips back to the primary
port when it returns to normal operation, after a user-selectable restoration
time. When the far end unit is an Optimux-134, the restoration is immediate
(zero restoration time).
Timing
The OP-34C internal timing subsystem generates the clock and timing signals
required by the link transmit paths of the module.
The link receive paths of the module use the clock signals recovered from the
corresponding received link signal.
The OP-34C modules can also provide timing reference signals derived from a
selected E1 stream for the nodal Megaplex-4100 timing subsystem.
OP-34C transmit timing can be locked to the Megaplex-4100 nodal timing.
The OP-34C module occupies one I/O slot in the Megaplex-4100 chassis. The
panels for the various OP-34C models are shown in Figure B-3.
OP-34C Modules
B-155
OP-34C
OP-34C
LINK/ACT
10 0
E
T
H
LOSS
AIS
L
I
N LOSS
K
AIS
LIN K/
ACT
E
T
H
100
LOSS
L AIS
I
N LOSS
K
AIS
OP-34C Module with SFP Ethernet Port OP-34C Module with Copper Ethernet Port
Figure B-44. Typical OP-34C Panels
The module panels have an Ethernet interfacing section in the middle, and a link
interfacing section at the bottom.
Ethernet Interfacing Section

The Ethernet interfacing section includes an Ethernet port, designated ETH. The
port is either equipped with an SFP or terminated in an RJ-45 connector. The port
has two status indicators, LINK/ACT and 100.
Link Interfacing Section

The link interfacing section includes a pair of ports, designated LINK A and LINK B.
The ports are equipped with SFPs. Each port has its own set of status indicators.
B-156
OP-34C Modules
LED Indicators
Link Indicators
Each LINK status indicator operates as follows:
AIS (yellow)
Lights when AIS is detected on the corresponding link.
LOSS (red)
Loss of signal indicator, is always Off when the

corresponding link port operates normally.
Lights when the corresponding link port reports loss of
signal.
Ethernet Indicators
LINK/ACT (yellow)
Lights when the link integrity signal is detected by the port

(normal operating condition the port is connected to an
active LAN, and the Ethernet link is up).
Flashes in accordance with the transmit and/or receive
activity on the corresponding port.
OFF when the Ethernet link is down.
100 (green)
Lights when the port operating rate is 100 Mbps.

OFF when the port operating rate is 10 Mbps.
General
Function
Compatibility
Number of Ports
Internal E1 Ports Type and Bit Rate
16-Channel E1 and Ethernet Multiplexer module with

SFP-based link
Another OP-34C
Optimux-134 standalone unit with or without

Ethernet port
16 internal E1 ports
One external Ethernet port
One internal Ethernet port
One link with two redundant ports
Number
16
Line Code
HDB3
Compliance

E bit)
OP-34C Modules
B-157
Framing
Ethernet Port

Timeslot 16 multiframe (G732S), with or

without CRC-4 per ITU-T Rec. G.704
Type
10/100Base-TX or SFP, with user-configurable

autonegotiation
Connector
Shielded RJ-45 connector, or hot-swappable SFP

(see OP-34C datasheet for available options)

transceivers, see the SFP Transceivers datasheet
Port Throughput
100 Mbps
IEEE 802.3, IEEE 802.3ah
Maximum Frame Size
1535 bytes
IEEE 802.3
Indicators per Port

LINK/ACT (yellow)
100 (green)
Optical Link
ON (yellow): link is up
OFF: link is down
Flashes: frames are transmitted/received
ON: port operates at 100 Mbps
OFF: port operates at 10 Mbps
Number of Ports per Link
2, with user-configured redundancy
Interface Type
SFP-based (see OP-34C datasheet for available

options)
Rate and Framing
E3 (34.386 Mbps)
Timing Source
Transmit timing: Megaplex-4100 nodal clock

(when connected to another OP-34C, you can
also select loopback timing)
Receive timing: recovered from receive line

signal
Indicators per Port
B-158
AIS (yellow)
Lights when AIS is received
LOSS (red)
Lights upon loss of incoming signal
OP-34C Modules
Note: Both LEDs are on if no SFP is inserted.
Diagnostics
Local and remote loopbacks on the local optical link

Local and remote loopbacks on the remote optical
link
Local and remote loopbacks on the module internal
E1/T1 ports (per port and per timeslot)
Local and remote loopbacks on remote E1/T1 ports
(per port)
Performance
Monitoring
E1 Ports
Ethernet Ports
As per RMON-RFC2819
Power
Consumption
10.4W
Configuration

system
Environment
0C to 45C (32F to 113F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
Warning
Caution

The OP-34C modules contain components sensitive to electrostatic discharge
OP-34C modules may be installed in an operating chassis (hot insertion).
OP-34C Modules
B-159
Note
OP-34C software can be updated by downloading from the CL module. Therefore,

if the OP-34C module is not yet loaded with the required software version, refer
to Chapter 7 for detailed software downloading instructions.
Before installing OP-34C modules, it may be necessary to install, or replace, SFPs.
OP-34C modules have four installation positions for SFPs, identified as LINK 1 to
LINK 4:
OP-34C modules equipped with RAD-supplied SFP plug-in modules comply with
Warning
OP-34C modules are shipped with protective covers installed on all the optical
SFPs installed on OP-34C modules may be equipped with a laser diode. In such
Warning
For your safety:

Installing an SFP
Warning
B-160
OP-34C Modules
connectors.
Note
To install the SFP:
Note

OP-34C module, and from the SFP electrical connector.
Replacing an SFP
SFPs, only the traffic on the affected optical link is disrupted (the other optical
link can continue to carry traffic).
To replace an SFP:
If necessary, disconnect any cables connected to the SFP connectors.
Push down the SFP locking wire, and then pull the SFP out.
OP-34C Modules
B-161
The module starts operating as soon as it is inserted in an operating chassis.
Warning
To install an OP-34C module:

3. Insert the OP-34C module in its chassis slot and slide it in as far as possible.
4. Secure the OP-34C module by tightening its two fastening screws.

Connecting to OP-34C Ethernet Electrical Port

OP-34C ETH electrical port has a 10/100BASE-TX Ethernet interface terminated in
an RJ-45 connector. The port supports the MDI/MDIX crossover function, and

Pin
Function
TxD+
TxD
RxD+
4, 5
RxD
7, 8
Not connected
Not connected
To connect to the electrical (copper) Ethernet port:
B-162
Designation
Connect the prescribed cable to the ETH connector.
OP-34C Modules
Connecting to Ethernet Optical Port

To connect to OP-34C with SFP Ethernet port:
Use the procedure described above for the optical LINK ports.
Connecting to Optical Link Ports

Pay special attention to SFPs that require a single fiber:
For SFP with SC/APC (SC/Angled Polished Connector), make sure to use only
patch cords and fibers terminated in SP/APC connectors along the whole
optical transmission path (such connectors are usually green).
SFP with WDM option A is intended for operation in a link with SFP with WDM
option B. For example, always operate SFP10A at one end of a link, and
SFP10B at the other end. Make sure to check before connecting fibers.
To connect to the OP-34C link ports:
Connect each prescribed fiber to the corresponding LINK connector.

Connecting to Copper Link Ports (OP-34C only)

For short-range applications, you can equip OP-34C LINK ports with SFP-12,
available from RAD, which has an electrical ITU-T Rec. G.703 interface terminated
in two SMB connectors.
RAD also offers an SMB-to-BNC adapter cable, CBL-SMB-BNC/M, which is
terminated in two BNC male plugs.
To connect to electrical OP-34C LINK ports:

1. Connect the SMB connectors of the CBL-SMB-BNC/M cable to the SFP-12
connector. Pay attention to polarity.
2. Connect the prescribed coaxial transmit cable (connected to the receive input
of the remote equipment) to the TX BNC connector of the CBL-SMB-BNC/M
cable.
3. Connect the prescribed coaxial receive cable (connected to the transmit
output of the remote equipment) to the RX BNC connector of the
CBL-SMB-BNC/M cable.
OP-34C Modules
B-163
Normal Indications
Optical Links
The status of each OP-34C LINK port is indicated by two separate indicators.
established, both indicators of a LINK port must be off.
If the equipment at the far end of the link is not yet operative, the port LOSS
indicator will light. The indicator must turn off as soon as the link with the
remote equipment is established.
Ethernet Port
Once the equipment connected to the module Ethernet port is operational, the

Configuring the Local Link
You can configure the local link even when no far end device is connected to it.
Only mux-eth-tdm 1 has to be configured. If you want to set protection for this
port, mux-eth-tdm 2 must be set to no shutdown and configured for protection
as described in Chapter 7, Configuring TDM Group Protection.
Internal E1 Port Numbering

Tributary E1 ports of Megaplex Optimux modules are actually internal ports but of
other type than E1-i.
OP-34C has 16 internal E1 ports. These ports are numbered 1 to 16 as follows:
<slot>/1/1, <slot>/1/2, . <slot>/1/15, <slot>/1/16. Tributaries <slot>/2/x do not
exist.
Internal Ethernet Port Numbering

The OP-34C internal Ethernet port is numbered <slot>/1/1.
Configuring Remote Equipment Ports

You can configure the remote equipment ports only when the far end device is a
standalone unit, but not an OP card.
Configuring the remote Optimux is described in Configuring the Remote Optimux
under Configuring Optical Link Parameters and Accessing the Remote Unit in
Chapter 6.
B-164
OP-34C Modules
Refer also to the Optimux-134 Installation and Operation Manual for a

description of the Optimux capabilities, and for specific configuration
instructions.
Configuring the Local Internal E1 Ports

OP-34C internal E1 ports provide the connection points toward the far end unit
E1 ports, respectively. Therefore, the number of active internal E1 ports must
match the number of E1 enabled on the far end unit (which must be equal to the
number of E1, streams to be transported to the far end), and in any case must
not exceed the number of E1 ports available on the far end unit.
When selecting the number of active ports, it is also necessary to consider the
bandwidth that remains available for Ethernet traffic, or vice versa if you need
to reserve a certain bandwidth for your Ethernet traffic, you must know how
many E1 streams you can transport.
Note
If you know the number of E1 streams to be transported, refer to Table B-31

to determine the available Ethernet transport bandwidth.
If you need to reserve a certain Ethernet transport bandwidth, refer to

Table B-31 to determine the number of E1 streams that can be transported.
The values appearing in Table B-31 should be interpreted as average bandwidth.

The Ethernet bandwidth is selected using the bandwidth [cir <value in kbps>]
parameter in the configure>qos context (see Configuring Bandwidth Profiles in
Chapter 8).
OP-34C always releases bandwidth for Ethernet traffic starting with internal E1
port 1, and in increments of four contiguous ports. Thus, E1 traffic is always
carried by the uppermost E1 ports.
For example:
When connecting to an Optimux-134 with V.35 port, if you enable internal E1

port 16 to carry traffic to the V.35 port, the maximum Ethernet transport
bandwidth is 24 Mbps.
To free 8 Mbps for Ethernet traffic on an OP-34C module, you cannot enable
the internal E1 ports 1 to 4; therefore, you can enable any of the internal E1
ports 5 to 16.
To free 16 Mbps, you must disable ports 1 to 8, and any of the internal E1
ports 9 to 16 can be enabled.
For your convenience, Table B-31 also lists the internal E1 ports that can be
enabled to obtain a desired E1 transport capacity while maximizing the bandwidth
available for Ethernet traffic.
Table B-31. Number of E1 Streams versus Reserved Ethernet Traffic Bandwidth

Bandwidth Reserved for
Ethernet Traffic (Rate Limit)
Number of E1 Streams that Can be

Transported
Internal E1 Ports that can be

Enabled
32 Mbps
None
No port
24 Mbps
Up to 4 E1
Port 13 to 16
OP-34C Modules
B-165
Bandwidth Reserved for

Ethernet Traffic (Rate Limit)
Number of E1 Streams that Can be

Transported
Internal E1 Ports that can be

Enabled
16 Mbps
Up to 8 E1
Port 9 to 16
8 Mbps
Up to 12 E1
Port 5 to 16
No bandwidth
Up to 16
Port 1 to 16
Configuring TDM Group/Ring Protection

OP-34C feature TDM group and ring protection for E1 ports and TDM group
protection for optical links (mux-eth-tdm ports).
To save duplication of configuration parameters, all the e1/mux-eth-tdm port
been updated. However, you must set the protection port to no shutdown
before starting the configuration.
Internal E1 Ports
The protection partners for internal E1 ports of OP-34C modules can be located
either on the same module or on another module, and can be any of the
following types: E1, internal E1 ports of CL or OP modules, or internal E1 ports of
M8SL or ASMi-54C/N modules.
When the other port in a protection group with an internal port of a CL.2 module,
only the dual-cable-tx protection mode can be used, and ring protection is
unavailable. CL.2 internal ports may also use path protection, so this type of
protection is not necessary for internal ports included in another protection
scheme.
working E1 port: the assignment is automatically copied to the protection partner
of the working port.
To avoid configuration errors, before starting the configuration of the protection
parameters, make sure that the other port does not carry traffic.
Optical Links
Make sure to connect link A of the local OP-34C to link A of the far end, and local
link B to far end link B.
The protection partner of the link (mux-eth-tdm 2) is automatically configured
with the same parameters as mux-eth-tdm 1. To activate protection, mux-ethtdm 2 must be set to no shutdown and configured for protection as described
in Chapter 5, Configuring TDM Group Protection.
For mux-eth-tdm ports, the wait-to-restore time is always 0.
The list of tasks that can be performed on the OP-34C modules and the
B-166
OP-34C Modules
Task
Configuring an OP-34C module

Configuring the optical link
Selecting an internal E1 Port as

Configuring the internal E1 port

parameters (OP-34C)
configure>port>e1
Ports, table, under E1 Ports in
Chapter 5
Configuring inband management

through E1 port
configure>port>e1
Configuring the external Ethernet

port
Configuring the internal Ethernet

port


for E1 ports (DS0 cross-connect
for E1 ports)
configure>cr>ds0

with OP-34C ports, see CrossConnect Table in Chapter 5

of timeslots, for each internal
E1/T1 port


a vc12-vt2 from an SDH port

configuration
configure>cr>tdm

<slot>/<port>

be of the same type
Configuring flows
flows between Logical MAC and
Ethernet port
configure>flows
OP-34C Modules
B-167
Task
E1 ports
Configuring protection for optical

links (mux-eth-tdm ports)

Acessing the remote Optimux
remote

optical link
remote
Chapter 5
user Ethernet port
remote
Chapter 5
Controlling the rate of the ingress
frames from the remote Optimux
device: frames that are over the
ingress rate limit are dropped
configure>qos, then
Configuring Bandwidth Profiles in
Chapter 5
remote

management Ethernet port
remote
Chapter 5
Chapter 5
configure>port>mng-eth
E1 ports
remote
Chapter 5
configure>port>e1
Diagnostics
OP-34C modules have comprehensive test and diagnostics capabilities that
include local and remote loopbacks on each link interface, on each internal E1/T1
port, and on selected timeslots of any E1 port.
When connected in a link with a standalone Optimux-134, the management
system controlling the OP-34C modules can also activate on the standalone unit
the remote link loopback, and local and remote loopbacks on E1 ports.
The OP-34C modules support diagnostic functions at the following levels:
B-168
OP-34C link level
Remote unit link level
OP-34C Internal E1 port and timeslot levels
Remote unit E1 port level.
OP-34C Modules
The loopbacks supported on each level are described in the table below.
Level
Optical link of
local module
Optical link of
remote unit
Internal E1
port of local
module: per
port and per
timeslot
E1/T1 port of
remote unit
Path and command
Reference
Local loopback on local OP-34C:

this loopback returns the OP34C link transmit signal to the
input of the link receive path
<slot>/<port 1>
Testing Optical
Links in Chapter 5
Remote loopback on local OP34C: this loopback returns the

OP-34C link receive signal
toward the remote equipment
(Optimux-134 or OP-34C)
<slot>/<port 1>
Remote loopback on remote

of the far end unit toward the
local OP-34C
<slot>/<port 1> remote
loopback local
Testing Optical
Links in Chapter 5
loopback remote
Testing Optical
Links in Chapter 5

remote

transmit signal to the input of
the port receive path
config>port>e1(<slot>/<mux-ethtdm port 1> /<e1 port 1..16>)#

receive signal toward the
remote equipment
(Optimux-134)
config>port>e1(<slot>/<mux-ethtdm port 1> /<e1 port 1..16>)#

returns the E1 port transmit
signal to the input of the port
receive path
loopback local [time-slot <1..31>]
loopback remote [time-slot

<1..31>]
(<slot>/<port 1> remote
e1 port 1..16>
loopback local

returns the Optimux-134 E1
port receive signal toward the
corresponding OP-34C internal
E1 port.
(<slot>/<port 1> remote
e1 port 1..16>
loopback remote
Note
A supervision terminal or other manager connected to a remote Optimux-134 can

also activate loopbacks on the local OP-34C.
OP-34C Modules
B-169
The Ethernet protocol does not allow looping back frames, and therefore all the
OP-34C loopbacks affect only the TDM signal paths. Ethernet payload is not
affected, and continues to flow through the link even when a link loopback is
activated.
Monitoring
The monitoring tasks supported on each OP-34C port level are listed in the table
below.
Level
Monitored Feature
Path
Reference
Local OP-34C Link
configure>port>
mux-eth-tdm>
Viewing Optical Link

Status Information in
Chapter 5
configure>
protection>tdmgroup
Status data for the external

physical port
configure>port>
ethernet
Ethernet Ports in
statistics
configure>port>
ethernet
Ethernet Ports in
Local OP-34C
internal Ethernet
port
statistics
configure>port>
ethernet
Local OP-34C
internal E1 port
statistics
configure>port>e1
Displaying E1 Port
Protection status
Local OP-34C
external Ethernet
port
Chapter 5
Chapter 5 (electrical
10/100BaseT ports only)
Chapter 5
5 (tributary)
(tributary)
Status data
configure>port>e1

Protection status
configure>
protection>tdmgroup

Chapter 5
The remote equipment status cannot be viewed through OP-34C links.
Troubleshooting
B-170
OP-34C Modules
Preliminary Checks
Check for proper installation and correct cable connections to the far end unit
connected to OP-34C, in accordance with its installation plan. Make sure that
the far end equipment is powered and operates normally
Check the attenuation of the optical fibers connected to the OP-34C
specific application requirements, as provided by the system administrator
If the Megaplex-4100 nodal clock is to be locked to the clock recovered from

one of the internal E1 ports of the OP-34C module, make sure that a suitable
fallback clock source is configured and provides a good clock signal.
After collecting all the available information, try to determine the main service
type affected by the problem, and continue to the appropriate section below.
If the problem cannot be corrected by the following procedures, the OP-34C or
the far end equipment must be replaced.
Problems Affecting All OP-34C Services

If, after collecting all the relevant information, the problem appears to affect all
the services of an OP-34C, perform the actions listed below until the problem is
corrected:
Check the AIS indicator of the OP-34C active LINK port: if an AIS indicator
lights, the problem is at the far end equipment.
Check that the LOSS indicators of the OP-34C LINK ports are OFF: if an
indicator lights, make sure that the SFP is properly plugged into its socket,
and then check the link fibers and their connections. Repeat the checks for
the far end equipment Link ports.
Make sure that no test has been activated on the link, neither at the OP-34C,
nor at the far end unit. Use the management system or a supervision
terminal to find the active test loopback and deactivate it.
Activate the local loopback on the OP-34C link. If the alarms generated by the
user equipment connected to the OP-34C stop, the problem is external.
Check cable connections and the transmission plant providing the link to the
far end unit.
Quickly check the link to the far end equipment unit by activating the remote
link loopback at the remote unit. If the link operates properly, the LOSS
indicators of the local link ports turn off while the loop is connected and the
alarms generated by the user equipment connected to the OP-34C stop.
If the remote loopback test fails but the local loopback is functioning, there is
a problem with the fibers connecting the OP-34C with the far end equipment,
or at the far end equipment (repeat the checks at the far end).
OP-34C Modules
B-171
Problems Affecting OP-34C TDM Services

to traffic served by one of the OP-34C internal E1 ports, perform the actions
Make sure that no test has been activated on the corresponding OP-34C port.
Use the Megaplex-4100 management system to find and deactivate the
If the problem is related to only part of the traffic carried by the

corresponding OP-34C port, check the configuration of OP-34C, in particular
timeslot assignment and cross-connections, and the configuration of the
modules handling the affected traffic and its source
Quickly check the path to the far end equipment unit by activating a remote
loopback on the corresponding OP-34C internal E1 port.
If the far end user equipment operates normally while the loop is
connected, the problem is at the local side. In this case, activate the local
port loopback on the internal E1 port: If the alarms related to the port
stop, the problem is in the OP-34C.
If the test fails, there is a problem with the transmission path to the far
end unit, or with the OP-34C module. Repeat the test after carefully
checking all the configuration parameters of the module and its ports,
and then perform the checks described above for link problems. If the
problem persists, replace the OP-34C module and check again.
Activate the local loopback on the corresponding OP-34C port.
If the alarms related to the equipment served by the port stop, the
problem is in the OP-34C.
If the alarms do not stop, check the configuration of Megaplex-4100, in

particular timeslot assignment and cross-connections, and the
configuration of the modules handling the affected traffic and its source.
Also check cable connections to the user equipment, and the user
equipment itself.
Problems Affecting OP-34C Ethernet Services

For problems affecting Ethernet traffic, first check the indications provided by the
Megaplex-4100 ETH port: if the LINK/ACT indicator is off, check cable connections
to the local LAN and the LAN equipment.
If the LINK/ACT indicator flashes or appears to light continuously, use the
performance data to analyze the problem characteristics and act accordingly.
B.8
HS-6N and HS-12N Modules

operation of the HS-6N and HS-12N 6/12 high-speed data modules for use in the
B-172
Megaplex-4100 Next Generation Multiservice Access Node, ver 3.0 and higher. For
use of the modules in the Megaplex-2100, Megaplex-2104, and Megaplex-4100
ver 2.1 chassis, see their respectiveInstallation and Operation manuals.
Product Options
The HS-6N and HS-12N modules can be ordered in the following versions, which
differ with respect to the type of channel interface:
Modules with V.11/RS-422 channel interfaces. These versions support user

equipment with RS-530, V.36/RS-449, and X.21 physical interfaces.
Modules with V.35 channel interfaces, for connection to user equipment with
V.35 interfaces.
Modules with RS-232 channel interfaces, for connection to user equipment

with RS-232 interfaces.
Each version is available in two models:
Note
HS-12N: module with 12 independent channels
HS-6N: module with 6 independent channels.
In this section, the generic term HS-6N/HS-12N is used when the information is
applicable to all the interface versions. The complete designation is used only for
information applicable to a specific equipment version.
Applications
Basic Applications
Figure B-46 illustrates an HS-12N application that gives a large number of users
flexible access to an SDH/SONET network. The total number of data channels
available in one fully equipped Megaplex-4100 unit is 120, where each channel
can operate at any data rate within the range supported by HS-12N.
Server
512 kbps
37X5
HS-12N
Modules
256 kbps
SDH/SONET
Network
E1/T1
..
.
DDS
Network
Up to 120
n x 56/64 kbps
Channels
ADM
384 kbps
..
.
Kilomux
Megaplex
64 kbps
Terminal
Figure B-46. Typical HS-12N Application Connecting 120 Data Channels to SDH/SONET Network
B-173
Figure B-47 shows another application that enables users at several remote sites
(e.g., branch offices) to connect to data equipment or other users at a central
site (company headquarters) through a single HS-12N module.
HS-2
..
.
Megaplex
Up to 12
n x 56/64 kbps
Channels
HS-6N
..
.
..
..
.
E1/T1 or IP
Network
Megaplex
Megaplex
..
.
HS-QN
Megaplex
Figure B-47. HS-12N at Central Site Serving Multiple Remote Sites
Point-to-Multipoint (Unidirectional Broadcast) Applications

data to multiple users connected to remote Megaplex units (simplex
communication), while using only the number of timeslots needed to support a
particular data rate.
In this mode, any message is simultaneously received by all the unidirectional
users, but none of them can send back data to the originator. This capability is
achieved by separating the handling of the receive and transmit paths for the
timeslots assigned for the unidirectional channels, as shown by the dashed lines
within the Megaplex units in Figure B-48.
Figure B-48 shows a network that uses the unidirectional broadcast mode to
distribute data from a central location (A) to several remote locations (B, C, D,
etc.). In Figure B-48, the user at the central location (A) is connected to an
HS-12N channel configured for operation in the unidirectional transmit mode. The
channels of the remote users (at locations B, C, D) are configured for the
unidirectional receive mode.
B-174

Location D
HS-12N
(UNI-BRD RX)
Location A
HS-12N
(UNI-BRD TX)
Megaplex
Port 1
Location C
Port 2
HS-12N
(UNI-BRD RX)
Location B
Megaplex
Port 1 Port 2
Megaplex
Megaplex
HS-12N
(UNI-BRD RX)
User's Equipment
(Receive Only)
Figure B-48. Typical Unidirectional Broadcast Application

At location A, the timeslots assigned to the user are routed to two main link
ports of the Megaplex unit, and can be inserted in timeslots with different
numbers.
For simplicity, first the path to the user at location D is described:
In the forward path (from location A to D), the timeslots assigned to the
HS-12N channel configured for unidirectional transmit operation are routed
through specified timeslots of port 1 to the Megaplex unit at location D.
At location D, the timeslots are routed to the receive path of the
unidirectional receive HS-12N channel. Therefore, user D receives data sent
by user A.
In the reverse path (from location D to A), the timeslot is always

disconnected. Therefore, user D cannot transmit data to user A.
The path to the users B and C is as follows:
In the forward path (from location A to B, C, etc.), the timeslots assigned to

the HS-12N channel configured for unidirectional transmit operation are
routed through a specified timeslot of port 2 to the Megaplex at location B.
At location B, the timeslots received at port 1 are routed as follows:
To the receive path of user B, configured for unidirectional receive mode
To the specified timeslots of port 2 (bypassing), which are connected to

the Megaplex at location C.
Therefore, the transmit signal of user A is relayed to the following units, and
the users at locations B and C receive data sent by user A.
B-175
The timeslots can be connected in parallel to any number of channels.

Note
In the reverse path (to location A), the timeslots are always bypassed from
port 2 to port 1, en route to location A.
To prevent interference from the unidirectional channel, its transmit path is
always disconnected from the main link timeslots (at location B, no
information is inserted in the timeslot bypassed from port 2 to port 1), and
user B cannot transmit data to any other user. The same is true for the user
at location C.
Figure B-49 shows another network configuration, which enables regular (full
duplex, or bidirectional) communication between two users (the users at
locations A and C). It also enables monitoring of the data sent by the user A at
location B.
Location C
Location A
HS-12N
(BI-DIR)
HS-12N
(BI-DIR)
Location B
Megaplex
Megaplex
Megaplex
HS-12N
(UNI-BRD RX)
User's Equipment
(Receive Only)
Figure B-49. Typical Unidirectional Receive Application

For this configuration, the users A and C are configured as regular users, and only
the user at location B is configured for unidirectional receive operation.
Features
The HS-6N and HS-12N modules support 6 or 12 high-speed synchronous data
channels, respectively.
Each channel can be independently configured to operate at a data rate of n56
or n64 kbps, where n = 1 to 24 when the channel is routed to a T1 link, and 1
to 31 (that is, maximum 1984 kbps) when the channel is routed to an E1 link.
Note
In modules with V.24/RS-232 interface, all channels operate at a rate of 64 kbps

only.
Data rates are independently selectable for each channel. The only restrictions
are as follows:
B-176
The combined data rates of a pair of consecutive channels (1 and 2,

3 and 4, etc.) cannot exceed 1984 kbps
You can operate the two channels of a pair at rates that are multiples of the
same basic rate (56 or 64 kbps), or at multiples of different basic rates.
However, in the latter case, configure the second (even-numbered) channel
of a pair to operate at a multiple of 64 kbps, and configure the first
(odd-numbered) channel to operate at a multiple of 56 kbps.
In addition to the normal full-duplex (bidirectional) mode, Megaplex-4100

supports an additional transmission mode, which enables point-to-multipoint
communication. This mode is unidirectional (simplex) transmission, in which each
channel can be configured either to receive (unidirectional RX) or to transmit
(unidirectional TX).
Interface Characteristics
The module channels are terminated on 68-pin SCSI-4 female connectors. Each
connector contains three channels; therefore HS-6N has two connectors and
HS-12N has four connectors. Adapter cables, available upon order, are offered by
RAD to split each module connector into three separate channel interfaces with
standard connectors.
The HS-6N/HS-12N modules can be ordered with the following interface types:
V.35
RS-422/V.11, which can be converted by means of adapter cables to

V.36/RS-449, RS-530, or X.21 interfaces
RS-232.
Interface Control Signals

Each channel has local support for the CTS, RTS, DCD, and DSR lines:
The DSR line is always ON.
The CTS line can be configured to be always ON, or to track the RTS line. The
same selection must be made for all the channels.
The DCD line is constantly ON, except when communications are not possible
because of loss of frame synchronization.
TDM Mapping
The DS0 cross-connect matrix of the Megaplex-4100 chassis enables flexible
payload routing in the HS-6N, HS-12N modules, independently configurable for
each port, at the individual timeslots (DS0) level.
Management
All operating parameters of HS-6N, HS-12N are soft-selectable via the
management system. The operating mode of each channel is independently
selectable.
Timing
The HS-6N, HS-12N module has an internal timing generator that receives the
nodal timing and clock signals from the Megaplex-4100 chassis and generates the
internal timing and clock signals needed for module operation.
B-177
The timing subsystem also generates clock signals locked to the timing of
channels operating in the DTE mode, which can be selected as sources for the
Megaplex nodal timing. A channel can serve as a timing source only when its RTS
line is active, and therefore channels used in the polling mode are not suitable as
nodal clock sources.
The timing mode of each channel can be configured to DCE, external DCE, or DTE
timing modes. The external DCE mode is used for tail-end applications, whereas
the DTE mode enables using an external clock source in applications that require
connecting to a data line provided by a data carrier service (such as DDS or
Kilostream), with the external clock available as a system nodal timing source.
The channel timing modes are as follows:
DCE timing: the HS-6N, HS-12N channel provides the clock signals to the DTE
connected to it. This mode is suitable for connecting equipment with DTE
interface to the HS-12N channel.
External DCE timing: the HS-6N, HS-12N channel provides the receive clock
signal to the user's DTE, and accepts an external transmit clock. In this mode,
the user equipment must use loopback timing; that is, its transmit timing
must be locked to the receive timing. This mode is suitable for tail-end
applications.
DTE timing: the HS-6N, HS-12N channel accepts the external transmit and
receive clock signals from the user equipment. In this case, the
HS-6N, HS-12N channel can serve as the nodal timing source for the
Megaplex system. This mode is suitable for connections to a digital
transmission network, which has its own accurate timing source.
FIFO buffers are used in the receive and transmit path of each module channel,
to absorb timing variations. FIFO size can be individually configured for each
channel. The Megaplex system can automatically select the FIFO size in
accordance with the minimum necessary. When a longer buffer is desired, the
user can also manually select the FIFO size. The supported FIFO sizes are 16
bits, 30 bits, 52 bits, and 72 bits.
The HS-6N and HS-12N modules occupy one I/O slot in the Megaplex-4100
chassis.
The panels of the HS-6N and HS-12N modules include only the channel interface
connectors. Figure B-50 shows typical module panels.
B-178
CH
1-3
HS-12/N
RS-422
HS-6/N
V.35
HS-12/N
V.35
CH
4-6
CH
4-6
CH
4-6
CH
1-3
CH
4-6
HS-12/N
RS-232
CH
4-6
CH
1-3
CH
7-9
CH
7-9
HS-12N
CH
1-3
HS-6/N
RS-422
HS-6N
HS-12N
Typical Panels for Modules

with V.35 Interface
CH
1-3
HS-6/N
RS-232
CH
4-6
CH
1-3
CH
7-9
HS-6N
HS-12N

with RS-422 Interface
HS-6N

with RS-232 Interface
Figure B-50. HS-6N/HS-12N Module Panels
Number of
Channels
Channel
Characteristics
HS-6N
6 synchronous data channels
HS-12N
12 synchronous data channels
Electrical Interface
V.35
V.11/RS-422
V.24/RS-232
Physical Interface
V.35 (via adapter cable)

V.36/RS-449, RS-530, or X.21 (via adapter
cables)
RS-232 (via adapter cable)
B-179
Channel Data Rates
n56 or n64 kbps rates, independently

selectable per channel:
E1: n = 1 to 31
T1: n = 1 to 24
Note: In modules with V.24/RS-232 interface,
the data rate for all channels is limited to

64 kbps.
Timing Modes
Connectors
68-pin SCSI female connector per each 3 data

channels (2 connectors for HS-6N and 4
connectors for HS-12N)
DCE
HS-6N/HS-12N channel provides both RX and TX

clocks to the user DTE
External-DCE
HS-6N/HS-12N channel provides RX clock to user

while receiving TX clock from user. Used for tailend applications
DTE
HS-6N/HS-12N channel receives both RX and TX

clocks from the user DCE
Control Signals
CTS follows RTS or is constantly ON,

soft-selectable (same setting for all channels)
DCD constantly ON, except during sync loss
DSR always ON
Power
Consumption
HS-6N
Max. 5.5W
HS-12N
Max. 6.25W
Environment
Operating temperature
-10C to 55C (14F to 131F)
Storage temperature
-20C to +70C (-4F to +160F)
Humidity:
Configuration
Programmable via Megaplex system management
Preparing the Modules for Installation
Warning
B-180

Caution
Caution
The modules contain components sensitive to electrostatic discharge (ESD). To

prevent ESD damage, always hold the module by its sides, and do not touch the
module components or connectors.


The modules may be installed in an operating chassis (hot insertion).
Warning
To install an HS-6N/HS-12N module:


The user equipment is connected to HS-12N modules via 68-pin SCSI female
connectors designated CH. 1-3, CH. 4-6, CH. 7-9, CH. 10-12. For HS-6N modules,
only the CH. 1-3 and CH. 4-6 connectors are used.
SCSI Connector Pinout

Table B-32 lists the pin assignment of the CH connectors. Note that the pins in
actual use depend on the module version.
Table B-32. CH Connector, Pin Assignment

Channel Pin Designation
Function
Pin Designation
Function
F.G.
Frame Ground
35
S.G.
Signal Ground
1,
RD(A)
Receive Data A
36
RD(B)
Receive Data B
4,
TC(A)
Transmit Clock A
37
TC(B)
Transmit Clock B
7,
RC(A)
Receive Clock A
38
RC(B)
Receive Clock B
B-181

Channel Pin Designation
10
2,
5,
8,
11
3,
6,
9,
12

Function
Pin Designation
Function
ERC(A)
External Receive Clock A
39
ERC(B)
External Receive Clock B
ETC(A)
External Transmit Clock A
40
ETC(B)
External Transmit Clock B
TD(A)
Transmit Data A
41
TD(B)
Transmit Data B
CO(A)
Control Out A
42
CO(B)
Control Out B
DSR(A)
Data Set Ready A
43
DSR(B)
Data Set Ready B
10
DCD(A)
Data Carrier Detect A
44
DCD(B)
Data Carrier Detect B
11
CI(A)
Control In A
45
CI(B)
Control In B
12
F.G
Frame Ground
46
S.G
Signal Ground
13
RD(A)
Receive Data A
47
RD(B)
Receive Data B
14
TC(A)
Transmit Clock A
48
TC(B)
Transmit Clock B
15
RC(A)
Receive Clock A
49
RC(B)
Receive Clock B
16
ERC(A)
50
ERC(B)
17
ETC(A)
51
ETC(B)
18
TD(A)
Transmit Data A
52
TD(B)
Transmit Data B
19
CO(A)
Control Out A
53
CO(B)
Control Out B
20
DSR(A)
Data Set Ready A
54
DSR(B)
Data Set Ready B
21
DCD(A)
55
DCD(B)
22
CI(A)
Control In A
56
CI(B)
Control In B
23
F.G
Frame Ground
57
S.G
Signal Ground
24
RD(A)
Receive Data A
58
RD(B)
Receive Data B
25
TC(A)
Transmit Clock A
59
TC(B)
Transmit Clock B
26
RC(A)
Receive Clock A
60
RC(B)
Receive Clock B
27
ERC(A)
61
ERC(B)
28
ETC(A)
62
ETC(B)
29
TD(A)
Transmit Data A
63
TD(B)
Transmit Data B
30
CO(A)
Control Out A
64
CO(B)
Control Out B
31
DSR(A)
Data Set Ready A
65
DSR(B)
Data Set Ready B
32
DCD(A)
66
DCD(B)
33
CI(A)
Control In A
67
CI(B)
Control In B
34
F.G
Frame Ground
68
S.G
Signal Ground
RAD offers adapter cables for directly connecting user equipment with standard
connectors to the appropriate 68-pin SCSI connector located on the
HS-6N/12N module. Table B-33 provides information on the adapter cables
available from RAD.
B-182
Table B-33. Adapter Cables Offered by RAD

Module Version
V.35
RS-422
RS-232
Adapter Cable
Users Side Connectors
CBL-SCS68/3/V35/M
34-pin VAPL male connector
CBL-SCS68/3/530/M
25-pin D-type male connector
CBL-SCS68/3/X21/M
CBL-SCS68/3/V36/M
CBL-SCS68/3/V36/F
37-pin D-type female connector
CBL-SCS68/3/232/M
To connect the cables:

1. Identify the cables intended for connection to each module connector, and
connect them into the appropriate connectors.
2. When using any of the adapter cables, plug each channel connector at the
other end of the cable into the prescribed user equipment connector in
accordance with the site installation plan.
Adapter Cables
The user side of each cable is terminated in three connectors, designated CH-1,
CH-2, CH-3. The tables in the following sections list the pinout of each connector
on the HS-6N/HS-12N and user sides and indicate the number of HS-6N/HS-12N
channel corresponding to each pin.
CBL-SCS68/3/V35/M Cable
Figure B-51 shows a general view of the CBL-SCS68/3/V35/M cable, and Table B34 lists the cable wiring.
CH-1
CH-
-3
CH
Figure B-51. CBL-SCS68/3/V35/M Cable

Table B-34. CBL-SCS68/3/V35/M, Cable Wiring
SCSI
Connector
Function
F.G.
Not Used
1,
RD(A)
Receive Data A
4,
TC(A)
7,
RC(A)
Ch
34-Pin
SCSI
Connector Connector
Function
34-Pin
Connector
35 S.G.
Not Used
36 RD(B)
Receive Data B
Transmit Clock A
37 TC(B)
Transmit Clock B
AA
Receive Clock A
38 RC(B)
Receive Clock B
B-183
Ch
SCSI
Connector
Function

34-Pin
SCSI
Connector Connector
34-Pin
Connector
Function
10 5
ERC(A)
BB
39 ERC(B)
ETC(A)
External Transmit Clock

A
40 ETC(B)

B
TD(A)
Transmit Data A
41 TD(B)
Transmit Data B
CO
Control Out
42
Not Used
DSR
Data Set Ready
43
Not Used
10
DCD
Data Carrier Detect
44
Not Used
11
CI
Control In
45
Not Used
12
F.G
Frame Ground
46 S.G
Signal Ground
13
RD(A)
Receive Data A
47 RD(B)
Receive Data B
14
TC(A)
Transmit Clock A
48 TC(B)
Transmit Clock B
AA
15
RC(A)
Receive Clock A
49 RC(B)
Receive Clock B
16
ERC(A)
BB
50 ERC(B)
17
ETC(A)

A
51 ETC(B)

B
18
TD(A)
Transmit Data A
52 TD(B)
Transmit Data B
CO
Control Out
53
Not Used
20
DSR
Data Set Ready
54
Not Used
21
DCD
Data Carrier Detect
55
Not Used
22
CI
Control In
56
Not Used
23
F.G
Frame Ground
57 S.G
Signal Ground
24
RD(A)
Receive Data A
58 RD(B)
Receive Data B
25
TC(A)
Transmit Clock A
59 TC(B)
Transmit Clock B
AA
26
RC(A)
Receive Clock A
60 RC(B)
Receive Clock B
27
ERC(A)
BB
61 ERC(B)
28
ETC(A)

A
62 ETC(B)

B
29
TD(A)
Transmit Data A
63 TD(B)
Transmit Data B
CO
Control Out
64
Not Used
31
DSR
Data Set Ready
65
Not Used
32
DCD
Data Carrier Detect
66
Not Used
33
CI
Control In
67
Not Used
34
F.G
Frame Ground
68 S.G
Signal Ground
2,
5,
8,
11 19
3,
6,
9,
12 30
CBL-SCS68/3/530/M Cable
Figure B-52 shows a general view of the CBL-SCS68/3/530/M cable, and Table B35 lists the cable wiring.
B-184

CH-1
CH
-2
-3
CH
Figure B-52. CBL-SCS68/3/530/M Cable

Table B-35. CBL-SCS68/3/530/M Cable Wiring
SCSI
Connector
Function
F.G.
Not Used
RD(A)
Receive Data A
1,
TC(A)
4,
7,
Ch
25-Pin
SCSI
Connector Connector
Function
25-Pin
Connector
35 S.G.
Not Used
36 RD(B)
Receive Data B
16
Transmit Clock A
15
37 TC(B)
Transmit Clock B
12
RC(A)
Receive Clock A
17
38 RC(B)
Receive Clock B
ERC(A)
20
39 ERC(B)
23
ETC(A)

A
24
40 ETC(B)

B
11
TD(A)
Transmit Data A
41 TD(B)
Transmit Data B
14
CO(A)
Control Out A
42 CO(B)
Control Out B
13
DSR(A)
Data Set Ready A
43 DSR(B)
Data Set Ready B
22
10
DCD(A)
44 DCD(B)
10
11
CI(A)
Control In A
45 CI(B)
Control In B
19
12
F.G
Frame Ground
46 S.G
Signal Ground
13
RD(A)
Receive Data A
47 RD(B)
Receive Data B
16
14
TC(A)
Transmit Clock A
15
48 TC(B)
Transmit Clock B
12
15
RC(A)
Receive Clock A
17
49 RC(B)
Receive Clock B
16
ERC(A)
20
50 ERC(B)
23
17
ETC(A)

A
24
51 ETC(B)

B
11
18
TD(A)
Transmit Data A
52 TD(B)
Transmit Data B
14
11 19
CO(A)
Control Out A
53 CO(B)
Control Out B
13
20
DSR(A)
Data Set Ready A
54 DSR(B)
Data Set Ready B
22
21
DCD(A)
55 DCD(B)
10
22
CI(A)
Control In A
56 CI(B)
Control In B
19
23
F.G
Frame Ground
57 S.G
Signal Ground
3,
24
RD(A)
Receive Data A
58 RD(B)
Receive Data B
16
6,
25
TC(A)
Transmit Clock A
15
59 TC(B)
Transmit Clock B
12
10
2,
5,
8,
B-185
Ch
SCSI
Connector
Function
9,
26
RC(A)
Receive Clock A
17
60 RC(B)
Receive Clock B
27
ERC(A)
20
61 ERC(B)
23
28
ETC(A)

A
24
62 ETC(B)

B
11
29
TD(A)
Transmit Data A
63 TD(B)
Transmit Data B
14
30
CO(A)
Control Out A
64 CO(B)
Control Out B
13
31
DSR(A)
Data Set Ready A
65 DSR(B)
Data Set Ready B
22
32
DCD(A)
66 DCD(B)
10
33
CI(A)
Control In A
67 CI(B)
Control In B
19
34
F.G
Frame Ground
68 S.G
Signal Ground
12
25-Pin
SCSI
Connector Connector
25-Pin
Connector
Function
CBL-SCS68/3/X21/M Cable
Figure B-53 shows a general view of the CBL-SCS68/3/X21/M cable, and Table B36 lists the cable wiring.
CH-1
CH
-2
-3
CH
Figure B-53. CBL-SCS68/3/X21/M Cable, General View

Table B-36. CBL-SCS68/3/X21/M Cable Wiring
Ch
1,
4,
7,
10
B-186
SCSI
Connector
Function
F.G.
Not Used
RD(A)
Receive Data A
TC(A)
Transmit Clock A
Not Used
ETC(A)

A
ETC(A)
15-Pin
SCSI
Connector Connector
15-Pin
Connector
Function
35 S.G.
Not Used
36 RD(B)
Receive Data B
11
37 TC(B)
Transmit Clock B
13
38
Not Used
39 ETC(B)

B
14

A
40 ETC(B)

B
14
TD(A)
Transmit Data A
41 TD(B)
Transmit Data B
Not Used
42
Not Used
Not Used
43
Not Used
10
DCD(A)
44 DCD(B)
12
Ch
2,
5,
8,
11
3,
SCSI
Connector
Function
11
CI(A)
Control In A
45 CI(B)
Control In B
12
F.G
Frame Ground
46 S.G
Signal Ground
13
RD(A)
Receive Data A
47 RD(B)
Receive Data B
11
14
TC(A)
Transmit Clock A
48 TC(B)
Transmit Clock B
13
15
Not Used
49
Not Used
16
ETC(A)

A
50 ETC(B)

B
14
17
ETC(A)

A
51 ETC(B)

B
14
18
TD(A)
Transmit Data A
52 TD(B)
Transmit Data B
19
Not Used
53
Not Used
20
Not Used
54
Not Used
21
DCD(A)
55 DCD(B)
12
22
CI(A)
Control In A
56 CI(B)
Control In B
10
23
F.G
Frame Ground
57 S.G
Signal Ground
24
RD(A)
Receive Data A
58 RD(B)
Receive Data B
11
25
TC(A)
Transmit Clock A
59 TC(B)
Transmit Clock B
13
26
Not Used
60
Not Used
27
ETC(A)

A
61 ETC(B)

B
14
28
ETC(A)

A
62 ETC(B)

B
14
29
TD(A)
Transmit Data A
63 TD(B)
Transmit Data B
30
Not Used
64
Not Used
31
Not Used
65
Not Used
32
DCD(A)
66 DCD(B)
12
33
CI(A)
Control In A
67 CI(B)
Control In B
10
34
F.G
Frame Ground
68 S.G
Signal Ground
6,
9,
12

15-Pin
SCSI
Connector Connector
Function
15-Pin
Connector
10
CBL-SCS68/3/V36/M and CBL-SCS68/3/V36/F Cables

Figure B-54 shows general views of the CBL-SCS68/3/V36/M and
CBL-SCS68/3/V36/F cables, and Table B-37 lists the cable wiring.
B-187

CH-1
CH
-2
-3
CH
Figure B-54. CBL-SCS68/3/V36/M, CBL-SCS68/3/V36/F Cables

Table B-37. CBL-SCS68/3/V36/M, CBL-SCS68/3/V36/F Cable Wiring
Ch
SCSI
Connector
Function
F.G.
Not Used
RD(A)
Receive Data A
TC(A)
37-Pin
SCSI
Connector Connector
37-Pin
Connector
Function
35 S.G.
Not Used
36 RD(B)
Receive Data B
24
Transmit Clock A
37 TC(B)
Transmit Clock B
23
RC(A)
Receive Clock A
38 RC(B)
Receive Clock B
26
ERC(A)
12
39 ERC(B)
30
ETC(A)

A
17
40 ETC(B)

B
35
TD(A)
Transmit Data A
41 TD(B)
Transmit Data B
22
10 8
CO(A)
Control Out A
42 CO(B)
Control Out B
27
DSR(A)
Data Set Ready A
11
43 DSR(B)
Data Set Ready B
29
10
DCD(A)
13
44 DCD(B)
31
11
CI(A)
Control In A
45 CI(B)
Control In B
25
12
F.G
Frame Ground
46 S.G
Signal Ground
19, 20, 37
13
RD(A)
Receive Data A
47 RD(B)
Receive Data B
24
14
TC(A)
Transmit Clock A
48 TC(B)
Transmit Clock B
23
15
RC(A)
Receive Clock A
49 RC(B)
Receive Clock B
26
16
ERC(A)
12
50 ERC(B)
30
2, 17
ETC(A)

A
17
51 ETC(B)

B
35
18
TD(A)
Transmit Data A
52 TD(B)
Transmit Data B
22
11 19
CO(A)
Control Out A
53 CO(B)
Control Out B
27
20
DSR(A)
Data Set Ready A
11
54 DSR(B)
Data Set Ready B
29
21
DCD(A)
13
55 DCD(B)
31
22
CI(A)
Control In A
56 CI(B)
Control In B
25
23
F.G
Frame Ground
57 S.G
Signal Ground
19, 20, 37
3,
24
RD(A)
Receive Data A
58 RD(B)
Receive Data B
24
6,
25
TC(A)
Transmit Clock A
59 TC(B)
Transmit Clock B
23
9,
26
RC(A)
Receive Clock A
60 RC(B)
Receive Clock B
26
1,
4,
7,
5,
8,
B-188
Ch
SCSI
Connector

37-Pin
SCSI
Connector Connector
Function
37-Pin
Connector
Function
12 27
ERC(A)
12
61 ERC(B)
30
28
ETC(A)

A
17
62 ETC(B)

B
35
29
TD(A)
Transmit Data A
63 TD(B)
Transmit Data B
22
30
CO(A)
Control Out A
64 CO(B)
Control Out B
27
31
DSR(A)
Data Set Ready A
11
65 DSR(B)
Data Set Ready B
29
32
DCD(A)
13
66 DCD(B)
31
33
CI(A)
Control In A
67 CI(B)
Control In B
25
34
F.G
Frame Ground
68 S.G
Signal Ground
19, 20, 37
CBL-SCS68/3/232/M Cable
Figure B-55 shows a general view of the CBL-SCS68/3/232/M cable, and Table B38 lists the cable wiring.
CH-1
CH
-2
-3
CH
Figure B-55. CBL-SCS68/3/232/M Cable
B-189
Table B-38. CBL-SCS68/3/232/M Cable Wiring

Ch
1,
4,
7,
10
2,
5,
8,
11
3,
6,
9,
12
B-190
SCSI
Connector
Function
F.G.
Frame Ground
35 S.G.
Signal Ground
RD(A)
Receive Data A
36
Not Used
TC(A)
Transmit Clock A
15
37
Not Used
RC(A)
Receive Clock A
17
38
Not Used
ERC(A)
External Receive Clock
20
39
Not Used
ETC(A)
24
40
Not Used
TD(A)
Transmit Data
41
Not Used
CO(A)
Control Out
42
Not Used
DSR(A)
Data Set Ready
43
Not Used
10
DCD(A)
Data Carrier Detect
44
Not Used
11
CI(A)
Control In A
45
Not Used
12
F.G
Frame Ground
46 S.G
Signal Ground
13
RD(A)
Receive Data
47
Not Used
14
TC(A)
Transmit Clock
15
48
Not Used
15
RC(A)
Receive Clock
17
49
Not Used
16
ERC(A)
20
50
Not Used
17
ETC(A)
24
51
Not Used
18
TD(A)
Transmit Data
52
Not Used
19
CO(A)
Control Out
53
Not Used
20
DSR(A)
Data Set Ready
54
Not Used
21
DCD(A)
Data Carrier Detect
55
Not Used
22
CI(A)
Control In
56
Not Used
23
F.G
Frame Ground
57 S.G
Signal Ground
24
RD(A)
Receive Data
58
Not Used
25
TC(A)
Transmit Clock
15
59
Not Used
26
RC(A)
Receive Clock
17
60
Not Used
27
ERC(A)
20
61
Not Used
28
ETC(A)
24
62
Not Used
29
TD(A)
Transmit Data
63
Not Used
30
CO(A)
Control Out
64
Not Used
31
DSR(A)
Data Set Ready
65
Not Used
32
DCD(A)
Data Carrier Detect
66
Not Used
33
CI(A)
Control In
67
Not Used
34
F.G
Frame Ground
68 S.G
Signal Ground
25-Pin
SCSI
Connector Connector
25-Pin
Connector
Function
The routing of the individual port timeslots (timeslot assignment) is configured
via ds0 cross-connect. You can assign only timeslots of ports that have already
been configured, and are configured as no shutdown.
Timeslots can be assigned to the following ports:
External E1/T1 ports of any I/O module
Internal E1/T1 ports of any I/O or CL module
DS1 ports of the MPW-1 module
Selecting FIFO Size

In general, you should select auto. For special applications that require longer
buffers, you may want to manually select one of the supported FIFO sizes (16
bits, 30 bits, 52 bits, or 72 bits). The automatically selected value depends
on the channel data rate:
16 bits for 64 kbps
16 bits for 1984 kbps.
Make sure to select a value equal to, or exceeding, the automatically selected
value at the operating data rate.
Selecting a Serial Port as System Timing Reference

After an external serial port of HS-6N/HS-12N is configured and at no shutdown,
its receive clock can be selected as a timing reference for the Megaplex-4100
system.
source <src-id> rx-port serial <slot>/<port>
Selecting the Data Rate

When selecting the data rate, take into consideration the number of timeslots
that is used by, or must be reserved for, other channels using the same uplink.
Moreover, if an E1 link is used and the framing method is G.732S, you must also
reserve one timeslot (timeslot 16) for signaling.
The total rate assigned to a pair of consecutive channels (e.g., 1 and 2, 3 and 4)
cannot exceed 1984 kbps (31 timeslots). In addition, you cannot select a multiple
B-191
of 64 kbps for the first (odd) channel of a pair, or a multiple of 56 kbps for the
even channel. The allowed range is n56 kbps or n64 kbps, where n is 1 through
24 for a T1 link, and 1 through 31 for an E1 link.
In HS-6N/12N modules with V.24/RS-232 interface, the data rate for all channels
is 64 kbps only.
The list of tasks that can be performed on the HS-6N/HS-12N module and the
third column refers to the reference tables that should be consulted when
planning the module operation.
Task
Configure a module and put it into

service
Configure the serial port

parameters
Reference
Megaplex-4100 Serial Ports
Note: You must also configure the CL.2 or uplink module port parameters (depending on the HS-6N/12N
module application). For the uplink module configuration procedure, refer to the appropriate section of this
Appendix.
Selecting a serial port as system
timing reference
config>system>clock>
domain(1)
Configure DS0 cross-connect

(timeslot assignment)
configure>cr>ds0

with HS-6N/HS-12N serial ports,
see Cross-Connect Table in
Chapter 5

HS-6N, HS-12N diagnostic capabilities include local and remote digital loopbacks
on each serial port (see Serial Ports in Chapter 5).
Troubleshooting
The loopbacks available on the HS-6N/HS-12N module provide a rapid and
efficient way to identify the general location of a fault in either of the two
HS-6N/HS-12N modules connected in a link, in the external equipment, or in the
connections to the channels.
If a complaint is received from one of the subscribers connected to the
HS-6N/HS-12N channels, first activate the local test loop at the side where the
complaint comes from. The local subscriber must receive its own signal.
B-192
If the signal is not received, the problem is at the local end:
Check the connections to the user equipment or the user equipment itself.
Replace the cable
Replace the local HS-6N/HS-12N module.
If the local subscriber receives its own signal when the local loopback is
connected, activate the remote loopback at the remote side and repeat the
check.
If the remote loopback indicates that the link operates normally, the problem is
at the remote end. To check, repeat the procedure on the remote Megaplex unit.
No performance monitoring and statistics are available on the serial ports.
B.9
HS-RN Modules

operation of the HS-RN four-channel low-speed data modules for use in the
ver 2.1 chassis, see their respective Installation and Operation manuals.
Product Options
Two module versions are offered:
Note
HS-RN: module version using proprietary, HDLC-protocol based, rate

adaptation that supports performance optimization with respect to either
bandwidth or latency, in accordance with user configuration
HS-RN/V.110: module version using V.110 rate adaptation, fully compatible

with the old HS-R module.
In this manual, the term HS-RN is used when the information is applicable to both
the HS-RN and HS-RN/V.110 modules.
The complete designation is used only for information applicable to a specific
equipment version.
Applications
Low-Speed Data Connectivity
Figure B-56 shows a typical point-to-point low-speed data transmission
application using HS-RN modules in Megaplex-4100. , HS-RN is also supported by
Megaplex-2100/2104, and modules installed in different chassis types are
interoperable.
In this application, two HS-RN modules are used to connect remote terminals to a
server or communication controller through the Megaplex link. Each channel can
be connected to a different destination.
HS-RN Modules
B-193
The HS-RN modules enable efficient utilization of link bandwidth; for example, a
HS-RN module enables the transmission of all four 9.6 kbps channels in one
64 kbps timeslot.
0.6 kbps
HS-RN
HS-RN
MPW-1
MPW-1
Terminal
IP
MP-4100
MP-4100
64 kbps
Server
Terminal
Figure B-56. Low-Speed Data Connection

Figure B-57 shows a typical point-to-multipoint application. Like the first one,
this application is also supported by both Megaplex-2100/2104 and Megaplex4100, and modules installed in different chassis types are interoperable.
Figure B-57. Point-to-Multipoint Connectivity for Low Speed Data Transfer
Unidirectional Broadcast Mode Applications

data to multiple users connected to remote Megaplex units (simplex
communication) while using only one timeslot. This application is supported by
both Megaplex-2100/2104 and Megaplex-4100, and modules installed in different
chassis types are interoperable.
In this mode, any message is simultaneously received by all the unidirectional
users, but none of them can send back data to the originator.
This capability is achieved by separating the handling of the receive and transmit
paths in the timeslot assigned for the unidirectional channels, as shown by the
dashed lines within the Megaplex units in Figure B-58.
B-194
HS-RN Modules
Figure B-58 shows a network that uses the unidirectional broadcast mode to
distribute data from a central location (A) to several remote locations (B, C, D,
etc.). In Figure B-58, the user at the central location (A) is connected to an HSRN channel configured for operation in the unidirectional transmit mode. The
channels of the remote users (at locations B, C, D) are configured for the
unidirectional receive mode.
The timeslot assigned to user A on one of the internal TDM buses is routed to the
two main link ports of the Megaplex unit at location A, and can be inserted in
timeslots with different numbers.
For simplicity, first the path to the user at location D is described:
In the forward path (from location A to D), the timeslot assigned to the
HS-RN channel configured for unidirectional transmit operation is routed
through the desired timeslot of port 1 to the Megaplex unit at location D.
At location D, the timeslot is routed to the receive path of the unidirectional
receive HS-RN channel. Therefore, the user D receives data sent by user A.
In the reverse path (from location D to A), the timeslot is always

disconnected. Therefore, the user D cannot transmit data to user A.
Figure B-58. Typical Unidirectional Broadcast Application

The path to the users B and C is as follows:
In the forward path (from location A to B, C, etc.), the timeslot assigned to

the HS-RN channel configured for unidirectional transmit operation is routed
through the specified timeslot of port 2 to the Megaplex unit at location B.
At location B, the timeslot received at port 1 is routed as follows:
To the receive path of user B, configured for unidirectional receive

operation
HS-RN Modules
B-195
To the specified timeslot of port 2 (bypassing), which is connected to the

Megaplex at location C.
Therefore, the transmit signal of user A is relayed to the following units, and
user B receives data sent by user A.
Note
The timeslot can be connected in parallel to any number of channels.
In the reverse path (to location A), the timeslot is always bypassed from port
2 to port 1, en route to location A.
To prevent interference from the unidirectional channel, its transmit path is
always disconnected from the main link timeslots (at location B, no
information is inserted in the timeslot bypassed from port 2 to port 1), and
user B cannot transmit data to any other user. The same is true for the user
at location C.
Figure B-59 shows another network configuration, which enables regular (full
duplex, or bidirectional) communication between two users (the users at
locations A and C), and in addition enables the monitoring of the data sent by
the user at location A by the user at location B.
For this configuration, users A and C are configured as regular users, and the user
at location B is configured for unidirectional receive operation.
Figure B-59. Typical Unidirectional Receive Application
Features
The HS-RN modules provide four independent V.24/RS-232 channels with DCE
interfaces that support full duplex asynchronous and synchronous data
transmission in the range of 0.6 through 64 kbps. The supported data rates
depend on the HS-RN model and rate adaptation (encapsulation) method (see
Table B-39).
HS-RN modules perform rate adaptation using a proprietary HDLC-based
protocol, whereas HS-RN/V.110 modules perform rate adaptation in accordance
with ITU-T Rec. V.110. Multiplexing in both modes is performed in accordance
with ITU-T Rec. I.460.
Each channel has local support of RS-232 control signals. Alternately, each
channel can be configured to transmit RS-232 control signals end-to-end (at all
the rates, except for 56 and 64 kbps):
B-196
HS-RN Modules
The local DTR state determines the remote DSR state, and vice versa
The local RTS state determines the remote DCD state, and vice versa.
Basically, each HS-RN channel is assigned an individual timeslot in a user-selected

E1, T1, or SDH/SONET uplink. In low data rate, bandwidth-optimized modes, the
HS-RN modules also support split timeslot assignment, therefore improving uplink
bandwidth utilization. User-controlled timeslot assignment provides control over
the routing of the bit stream generated by each local channel to any other
compatible Megaplex channel at the remote site.
In addition to the normal (bidirectional) mode of operation, the HS-RN modules
support the unidirectional broadcast mode. For a description of this mode, refer
to Unidirectional Broadcast Function under Cross-Connections in Chapter 5.
Encapsulation Mode
For the HDLC-based module version, the module rate adaptation and
encapsulation method can be selected in accordance with the specific application
requirements as follows:
Bandwidth Optimized enables optimal uplink bandwidth utilization (by using

split timeslot assignment for all the rates up to, and including, 19.2 kbps) in
applications less sensitive to latency.
Latency Optimized enables minimum end-to-end data latency. In this mode,

split timeslot assignment is not used, and the uplink bandwidth needed by
each channel is a full timeslot (64 kbps per channel).
The Megaplex-4100/V.110 module always operates in the bandwidth optimized

mode only, but the end-to-end data latency is at minimum because of the use of
V.110 rate adaptation.
Note
HS-RN modules can operate in a link only when set to the same mode. In
addition, HS-RN/V.110 cannot be operated in a link with the HDLC-based HS-RN
module version.
Channel Data Rates

Table B-39 lists the HS-RN channel data rates available for each module version
and operating mode.
HS-RN Modules
B-197
Table B-39. HS-RN Channel Rates

HDLC - Bandwidth Optimized
HDLC - Latency Optimized
V.110
Sync
Async
Sync
Async
Sync
Async
0.6 kbps
1.2 kbps
2.4 kbps
4.8 kbps
7.2 kbps
9.6 kbps
14.4 kbps
19.2 kbps
28.8 kbps
38.4 kbps
56 kbps
64 kbps
Channel Rate
Channel Rate Adaptation Processor

Rate adaptation is needed at all the channel rates, except 56 and 64 kbps. Each
channel has its own channel rate adaptation processor, which is used to adapt
the user payload data rate to a multiple of 16 kbps (16 kbps, or two bits, is the
main link bandwidth allocation unit).
The difference between the assigned and payload bandwidth also enables
end-to-end transfer of RS-232 interface signal states, when a channel is
configured to support this service.
Table B-40 lists the supported user's payload data rates, the data rate obtained
after rate adaptation, the number of main link bits assigned by the HS-RN
channel to carry the channel payload data, and the corresponding fraction of
main link timeslot for each data rate.
Note
When a channel operates in any one of the broadcast modes or latency

optimized mode, it must be assigned a full main link timeslot, although it may not
utilize the full timeslot bandwidth.
Table B-40 also lists rates at which rate adaptation is not needed (56 and 64
kbps).
B-198
HS-RN Modules
Table B-40. Occupied Bandwidth versus Channel Rate

Channel Rate
Occupied Bandwidth
Number of Bits
0.6 kbps
16 kbps
2 (one-quarter timeslot)
1.2 kbps
16 kbps
2.4 kbps
16 kbps
4.8 kbps
16 kbps
7.2 kbps
16 kbps
9.6 kbps
16 kbps
14.4 kbps
32 kbps
4 (one-half timeslot)
19.2 kbps
32 kbps
28.8 kbps
64 kbps
8 (one timeslot)
38.4 kbps
64 kbps
8 (one timeslot)
56 kbps (Sync mode only)
64 kbps
8 (one timeslot)
64 kbps (Sync mode only)
64 kbps
8 (one timeslot)
Channel Interface
Each HS-RN module channel can be configured by the user for asynchronous or
synchronous operation. Each channel has a DCE RS-232 interface.
The channel interface provides the following functions:
Conversion of data stream received from the link to the format needed by
the user equipment, and vice versa. This conversion depends on the
operation mode (synchronous/asynchronous; for the latter, it also depends
on the selected word format.
Physical interfacing to the user equipment, including handling of RS-232

interface signals.
Asynchronous Mode
The data rates supported by the HS-RN models in the asynchronous mode are
0.6, 1.2, 2.4, 4.8, 9.6, 19.2, and 38.4 kbps. The HDLC-based HS-RN model also
supports data rates of 7.2, 14.4, and 28.8 kbps.
In the asynchronous mode, the user can specify the structure of the word format
to be processed by each channel; this structure must be identical to that used by
the user equipment. The user can select the following parameters:
Number of data bits: 5, 6, 7, or 8.
Use of parity: if the data word format received from the user equipment
includes a parity bit, the user can enable transparent end-to-end transfer of
the original parity bit. The HS-RN module itself does not check the parity of
the incoming data.
Number of stop bits: 1 or 2.
In addition to the selected parameters, the word format includes one start bit.
HS-RN Modules
B-199
Note
The range of Async Mode character lengths supported by the Megaplex-4100

modules is 8 to 11 bits. Character length is given by: data bits + parity + 1 start
bit + stop bits.
Synchronous Mode
The data rates supported by both HS-RN models in the synchronous mode are
0.6, 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 56, and 64 kbps. The HDLC-based HS-RN
model also supports data rates of 7.2, 14.4, and 28.8 kbps.
Interface Control Lines

The RS-232 interface control signals are locally supported in accordance with the
RS-232 protocol, with the following modifications:
The DSR line is continuously active (ON), except when the end-to-end
transmission of control signals is enabled.
The DCD line is ON only when both the channel framing machine and the local
Megaplex main link carrying the channel are synchronized, and is OFF when
either the channel framing machine or the main link loses synchronization.
For flexibility in application, the user can program the state of the CTS line.
The available selections are:
The CTS line is continuously active (ON).
The state of the local CTS line tracks the state of the local RTS line.
As an alternative to local support as described above, the user can enable

end-to-end transmission of the states of the local DTR and RTS lines to the
remote DSR and DCD lines, respectively. Note that end-to-end transmission of
control signals is not supported at the 56 and 64 kbps channel rates.
TDM Mapping
payload routing in the HS-RN modules, independently configurable for each port,
at the individual timeslots (DS0) level.
Each main link allocation unit generated by an HS-RN module can be
independently routed to any other compatible module that is installed in the
remote Megaplex unit and configured for the same combination of data rates.
Moreover, the HS-RN modules support split timeslot allocation.
Management
All operating parameters of HS-RN are soft-selectable via the management
system. The operating mode of each channel is independently selectable.
Timing
When operating in the synchronous mode, the timing of the HS-RN channel
interfaces is locked to the Megaplex nodal timing.
The timing mode of each HS-RN module channel can be selected by the user. Two
options are available:
B-200
HS-RN Modules
DCE timing: the interface provides transmit and receive clock signals to the
user's data equipment (DTE). The user's DTE must receive and transmit at the
rate of the clock signals provided by the HS-RN channel interface.
External DCE timing: the interface provides a receive clock signal to the user's
DTE, and accepts the transmit clock from the user's DTE. The user's DTE must
operate with loopback timing; that is, it must transmit at the rate of the
receive clock signal provided by the HS-RN channel interface. This timing
mode is suitable for tail-end applications.
The HS-RN module occupies one I/O module slot in the Megaplex-4100 chassis.
All the functional configuration parameters of the modules are determined by
software. Jumpers are used only to control the connection of ground reference to
each channel connector.
Figure B-60 shows the module panel.

HS-RN
TST LOS
CH.1
Test
Indicators
CH.2
CH.3
LOS
Indicators
CH.4
CH1 & CH2 Connector

Channels
1-2
CH.
1-2
CH3 & CH4 Connector

Channels
3-4
CH.
3-4
Figure B-60. HS-RN Module Panel

The HS-RN module panel includes two 25-pin D-type female connectors, each
serving two channels and two status indicators for each channel.
LED Indicators
The HS-RN panel includes two status indicators for each channel:
TST (yellow): lights when a test or loopback is activated on the corresponding

channel.
LOS (red): lights when the main link loses synchronization, or the
corresponding channel loses protocol synchronization to the remote end (for
rates of 64 kbps and 56 kbps)
HS-RN Modules
B-201
When a channel is not connected, its LOS indicator is always off.
General
Number of data
channels
Four
Channel interface
ITU-T Rec. V.24/V.28, EIA RS-232
Interface type
DCE
Signal format
Asynchronous or synchronous, user-selectable
Rate Adaptation Megaplex-4100

Protocol
model
Proprietary HDLC-based
Megaplex-4100/V.1 ITU-T Rec. V.110

10
Data
Transmission
Characteristics
Interface
Control Signals
Channel data rates
Refer to Table B-39
Asynchronous
character format
User-selectable
Start bits
Data bits
5, 6, 7, or 8
Parity
Enable/disable transparent end-to-end transfer of parity

bit
Stop bits
1 or 2
Support modes
Local support
End-to-end transfer (not available for rates of 56 and
64 kbps
Local support
DSR always ON when module is powered (unless

end-to-end transmission is enabled)
Local DCD is ON when the main link is synchronized
and there is no SYNC LOSS alarm on the channel
Local CTS tracks local RTS state, or is constantly ON
(user-selectable)
End-to-end transfer Local DTR line to remote DSR line

(user-selectable)
Local RTS line to remote DCD line
Timing source
B-202
HS-RN Modules
RS-232 interface timing locked to nodal timing
Timing
Timing modes
DCE: Transmit and receive clocks to DTE

External DCE: Receive clock to DTE, transmit clock from
DTE
Main Link
Bandwidth
Refer to Table B-40.
Indicators
LOS indicator (per

channel)
Lights up when the main link loses synchronization or the

corresponding channel loses protocol synchronization to
the remote end (not used for the rates of 56 and
64 kbps)
TST indicator (per

channel)
Lights when a loopback is activated on the corresponding

channel
Connectors
Diagnostics
Two 25-pin D-type female connectors (one connector for

each pair of channels)
Loopbacks
Local loopback
Remote loopback
Power
Consumption
1.8W
Configuration
Programmable by the Megaplex system management
Warning
Caution
Caution



HS-RN Modules
B-203

Warning
To install an HS-RN module:


Connector Pin Assignment
The connection of user equipment to HS-RN modules is made to the two 25-pin
D-type female connectors designated CH. 1-2 and CH. 3-4. Table B-32 lists the pin
assignment of the CH. 1-2 connector, which serves channels 1 and 2. The wiring of
the CH. 3-4 connector, which serves channels 3 and 4, is similar.
Table B-41. CH. 1-2 Connector, Pin Assignment

Pin
Designation
Function
FGND
Frame ground (connected through jumper)
TD1
IN
TX data, channel 1
RD1
OUT
RX data, channel 1
RTS1
IN
CTS1
OUT
Clear to send, channel 1
DSR1
OUT
Data set ready, channel 1
SGND
DCD1
OUT
9, 10
B-204
Direction
Request to send, channel 1
Signal ground
Carrier detect, channel 1
Not used
11
TXCLK2
OUT
TX clock, channel 2
12
DCD2
OUT
Carrier detect, channel 2
13
CTS2
OUT
Clear to send, channel 2
14
TD2
IN
TX data, channel 2
15
TXCLK1
OUT
TX clock, channel 1
HS-RN Modules

Pin
Designation
Direction
Function
16
RD2
OUT
RX data, channel 2
17
RCLK1
OUT
RX clock, channel 1
18
RCLK2
OUT
RX clock, channel 2
19
RTS2
IN
Request to send, channel 2
20
DTR1
IN
Data terminal ready, channel 1
21
DSR2
OUT
Data set ready, channel 2
22
Not used
23
TXCLK-EXT2
IN
External TX CLK, channel 2
24
TXCLK-EXT1
IN
External TX CLK, channel 1
25
DTR2
IN
Data terminal ready, channel 2
Splitter Cables
RAD offers two channel splitter cables that enable direct connection of data
equipment with RS-232 interfaces to an HS-RN channel connector:
CBL-HSR/F, which terminates in two 25-pin D-type female connectors.
CBL-HSR/M, which terminates in two 25-pin D-type male connectors.
The wiring diagram of the two cables is shown in Figure B-61.
HS-RN Modules
B-205
TD1
RD1
RTS1
CTS1
DSR1
DCD1
TXCLK1
15
15
RCLK1
17
17
DTR1
20
20
TXCLK-EXT1
24
24
GND
Channel 1
.
.
.
To HS-RN Port
Connector
TD2
14
RD2
16
RTS2
19
CTS2
13
DSR2
21
DCD2
12
TXCLK2
11
15
RCLK2
18
17
DTR2
25
20
TXCLK-EXT2
23
.
.
24
Channel 2
User's Equipment
Side
Module
Side
Figure B-61. Channel Splitter Cable Wiring
To connect the cables:

1. Identify the cables intended for connection to each module connector and
connect them into the appropriate connectors.
2. When using any of the adapter cables, plug each channel connector at the
other end of the cable into the prescribed user equipment connector in
Normal Indications
The normal indications for an operational channel are as follows:
B-206
The LOS indicator must be off.
The TST indicator must be off, but may turn on when a loopback is activated
on the corresponding channel interface.
HS-RN Modules
Configuring Encapsulation Mode
All the ports of the HS-RN module must use the same encapsulation mode. This is
done by forcing the last choice to all the module ports.
In the HS-RN/V.110 module version the only possible selection is bandwidth.

Configuring Split Timeslot Cross-Connect

When using a broadcast mode or the latency-optimized mode, split timeslot
assignment cannot be used. In this case you must assign a full timeslot to each
HS-RN channel operating in this mode.
Selecting the Async Word Format

When selecting the Async word format, pay attention to the total character
length, as calculated by the formula: Data bits + Parity + 1 Start Bit + Stop Bits.
The allowed character length is 8 to 11 bits.
Configuring End-to-End Control

When configured (end-to-end-control enabled), the state of the local RTS and
DTR lines are reflected by the remote DCD and DSR line, respectively. Do not use
this selection for data rates exceeding 38.4 kbps.
When end-to-end-control is disabled (no end-to-end-control), only local support
is available). Always use this selection for data rates exceeding 38.4 kbps.
The list of tasks that can be performed on the HS-RN module and the
Task
Configuring a module and put it

into service
Reference
HS-RN Modules
B-207
Task
Reference
Configuring the serial port

parameters
Note: you must also configure the CL.2 or uplink module port parameters (depending on the HS-RN module
application). For the uplink module configuration procedure, refer to the appropriate section of this Appendix.
Configuring DS0 cross-connect
configure>cr>ds0

with HS-RN serial ports, see CrossConnect Table in Chapter 5
Configuring split timeslot crossconnect (timeslot assignment)

with HS-RN serial ports, see CrossConnect Table in Chapter 5

HS-RN diagnostic capabilities include local and remote digital loopbacks on each
serial port (see Serial Ports in Chapter 5).
Troubleshooting
The loops available on the HS-RN module provide a rapid and efficient way to
identify the general location of a fault either of the HS-RN modules connected in
a link, in the external equipment, or in the connections to the channels.
If the LOS indicator of an HS-RN channel lights, or a complaint is received
regarding the transmission of data through one of the HS-RN channels, perform
the following procedure until the problem is located. After each step, continue to
the next step only if the previously specified test has been successfully
completed.
Note
If the problem is detected when a connection between two new users is

activated for the first time, before starting the troubleshooting procedure
described below, thoroughly check the timeslot allocation, the configuration of
the two Megaplex units that provide the new connection, and the configuration
of the user's terminal equipment.
Request the user to perform a local loopback test on the local data
equipment. If the user equipment does not receive its own signal, the
problem is in the user equipment. After correcting the problem, continue
troubleshooting as explained below.
If the signal is not received when the remote digital loopback is activated,
activate the local main link loop on the local Megaplex unit:
B-208
HS-RN Modules
If the user equipment does not receive its own signal when the main link
loop is connected, the problem is in the local unit.
If the signal is received when the main link local loopback is activated,
activate the remote main link loop.
If the user equipment does not receive its own signal, the problem is
either in the timeslot allocation or in the remote unit.
B.10 HS-U-6 and HS-U-12 Modules

operation of the HS-U-6 and HS-U-12 ISDN interface modules for use in the
ver 2.1 chassis, see the corresponding separate Installation and Operation
manual.
Product Options
Two module versions are offered:
Note
HS-U-12: provides 12 ISDN U-type basic rate access (BRI) ports, including
capability for supplying phantom feed to the subscribers equipment.
HS-U-6: similar to the HS-U-12 module, except that it has only 6 ports.
In this manual, the term HS-U-6/12 is used when the information is applicable to
both the HS-U-6 and HS-U-12 modules.
The complete designation is used only for information applicable to a specific
equipment version.
Operating Modes
HS-U-6 and HS-U-12 ports feature two operation modes:
I mode: intended for applications requiring the extension of ISDN lines. In

this mode, the user can configure each module port to operate either as a
line termination (referred to as lt in CLI) or network termination (referred to
as nt in CLI).
1 mode: the module port serves as a dedicated line termination unit for
leased lines and the ASMi-31 short-range modem (referred to as lt1 in CLI).
The operation mode of each module port is independently selectable, using the
Megaplex management system or a supervision terminal.
HS-U-6 and HS-U-12 Modules
B-209
I Mode Main Features and Applications

In the I mode, the HS-U-6/12 module enables extending ISDN lines over
non-ISDN facilities over a link provided by Megaplex equipment. In this mode,
each of the module ports operates as an independent U ISDN basic rate access
interface (port), which can be configured to operate in the lt or nt mode.
Each U interface carries two B (64 kbps) channels and one D (16 kbps) channel.
Each channel can be independently connected to the Megaplex main link,
operates independently, and its rate can be freely selected, irrespective of the
data rates selected for the other channels.
Note
In this manual, the term main link is used to denote any E1/T1/E1-i/T1-I links on
I/O or CL modules working in conjunction with the HS-U-6/12 module.
The I mode provides ISDN BRI ports whose channels can be independently
configured and connected:
Each B-channel supports synchronous data transmission at rates of 16, 32,

and 64 kbps.
The D channels support 16 kbps.
Usually, only the B channels are used to carry payload data, and the D channel carries
control and signaling information associated with the U interface.
For B channel payload rates lower than 64 kbps, the modules perform channel
multiplexing and data rate adaptation. Therefore, main link bandwidth must be
allocated only in accordance with the actual payload carried by the module channels.
The I mode enables connecting remotely located ISDN equipment to an ISDN
switch via Megaplex units interconnected by links, as shown in the typical
application shown in Figure B-62.
B-210
ISDN Switch
Megaplex
System
HS-U-12
(NT-I)
12
Transmission
Network
2-Wire Line
(Max 5.5Km)
1
HS-U-12
(LT-I)
12
.
..
..
.
..
..
User's Side
NT1 Unit
TE Unit
ISDN
Terminal
2-Wire Line
(Max 5.5Km)
Megaplex
System
Figure B-62. Typical I Mode Application

In the application shown in Figure B-62, the HS-U-12 module connected directly
to the ISDN switch is configured to operate in the nt mode, and the other module
is configured to operate in the lt mode. The module transparently transfers the
data in the 2B + D channels, and therefore operates independently of the ISDN
switch in use.
The module ports working in I mode have two operating modes, which can be
independently selected for each port:
LT Mode: The LT mode enables the connection of the external ports to

network termination (NT) units that have a U interface.
NT Mode: The NT mode enables the connection of the external ports to an

ISDN switch that operates in the LT mode.
1 Mode Main Features and Applications

In the 1 mode, each of the module ports can provide an independent ISDN U
basic rate access interface operating as an LT (line termination), a mode referred
to as lt1.
The 1 mode is intended for use with leased lines, and therefore only the
B channels of each port are supported (the D channel is ignored). Each B channel
operates independently, and its rate can be freely selected, irrespective of the
data rates selected for the other channels.
In the 1 mode, the module ports can serve as dedicated line termination units for
the ASMi-31 short-range modems, offered by RAD. Figure B-63 shows a typical
application for the 1 mode in conjunction with ASMi-31.
B-211
In the application shown in Figure B-63, each module port serves as a line
termination unit (LT) for one ASMi-31. Each ASMi-31 unit operates as a network
termination unit (NT). This configuration enables the connection of various types
of remotely located data equipment such as computer terminals or statistical
multiplexers, via the Megaplex data link.
DTE
ASMi-31
19.2k
(NT)
2-Wire Line
(Max 5.5Km)
Megaplex
System
1
DTE
HS-U-12
(LT-1)
12
ASMi-31
128k
(NT)
2-Wire Line
(Max 5.5Km)
Transmission
Network
DTE
ASMi-31
19.2k
2-Wire Line
(Max 5.5Km)
HS-U-12
(LT-1)
(NT)
1
DTE
12
ASMi-31
128k
2-Wire Line
(Max 5.5Km)
(NT)
Megaplex System
Figure B-63. Typical 1 Mode Application

When an ASMi-31 modem is connected to an HS-U-6/12 port, the module
automatically establishes control over the operation of the ASMi-31. The ASMi-31
modem supports bidirectional management communication over the D channel,
using the SFM protocol (a RAD proprietary protocol). As a result, an HS-U-6/12
port connected to an ASMi-31 can automatically download the appropriate
configuration to the ASMi-31 through the downlink path, thereby ensuring that
the ASMi-31 is always correctly configured.
The operation mode of each HS-U-6/12 port can be independently selected:
Synchronous mode: in this mode, the port can be configured for operation at
rates of 1.2, 2.4, 4.8, 9.6, 16, 19.2, 32, 38.4, 48, 56 (supported only when
connected to an ASMi-31 using V.110 rate adaptation), 64 or 128 kbps (for
128 kbps, both B channels are used).
Asynchronous mode: in this mode, the port can be configured for operation
at rates of 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 57.6 or 115.2 kbps (for 115.2 kbps,
both B channels are used).
In both the synchronous and asynchronous modes, the user can select between
multiplexing and data rate adaptation using a RAD proprietary method based on
ITU-T Rec. I.460, or multiplexing and data rate adaptation in accordance with
ITU-T Rec. V.110.
B-212
In the 1 mode, the B channels are used to provide payload transmission pipes
(leased line mode), and the D channels are ignored (that is, they are not
transmitted through the main link; however, they can be used to carry a
proprietary communication channel for the management of ASMi-31 short-range
modems connected to the local ISDN port).
The transmission mode of each port can be selected by the user:
Synchronous mode: supports data rates of 1.2, 2.4, 4.8, 9.6, 16, 19.2, 32,
38.4, 48, 56 (only when connected to an ASMi-31 using V.110 rate
adaptation), 64 and 128 kbps.
For operation at 128 kbps, the B-channels are combined, therefore it is
necessary to ensure that the two B channels of a port are always routed
along the same path and have identical delays. The two B channels are
always inserted in consecutive main link timeslots, starting with an even
timeslot.
Asynchronous mode: supports data rates of 1.2, 2.4, 4.8, 9.6, 19.2, 38.4,
57.6 and 115.2 kbps (115.2 kbps uses two B channels, as explained above
for the 128 kbps synchronous mode).
In the asynchronous mode, the user can select the word format:
Note
One start bit.
7 or 8 data bits. When using the V.110 protocol (see Handling of B

Channels section below), you can also select 5 or 6 data bits.
Parity (one even or odd parity bit), or no parity.
One or two stop bits.
When using the V.110 protocol, the maximum rate supported in the
asynchronous mode is 38.4 kbps.
When a 1 port is connected to an ASMi-31, the port configuration is
automatically downloaded through the D channel.
General Features
External and Internal Ports
The HS-U-12 module includes 12 external ports terminated in U interfaces.
Each U interface supports two 64-kbps B channels, which carry payload data,
and one 16 kbps D channel, which carries signaling information. The B- and
D-channels serve as internal (BRI) ports.
In addition, the U interface is used to connect the feed voltage to the external
line, to provide phantom feed to the equipment at the remote end of each line.
Each B and D channel is connected to the corresponding external port Table B-42
lists the internal (BRI) ports serving each external port.
B-213
Table B-42. Internal Ports Functions

External Port
Channel Internal Port
External Port
Channel Internal Port
B1
B2
D
BRI <slot>/1/1
BRI <slot>/1/2
BRI <slot>/1
B1
B2
D
BRI <slot>/7/1
BRI <slot>/7/2
BRI <slot>/7
B1
B2
D
BRI <slot>/2/1
BRI <slot>/2/2
BRI <slot>/2
B1
B2
D
BRI <slot>/8/1
BRI <slot>/8/2
BRI <slot>/8
B1
B2
D
BRI <slot>/3/1
BRI <slot>/3/2
BRI <slot>/3
B1
B2
D
BRI <slot>/9/1
BRI <slot>/9/2
BRI <slot>/9
B1
B2
D
BRI <slot>/4/1
BRI <slot>/4/2
BRI <slot>/4
10
B1
B2
D
BRI <slot>/10/1
BRI <slot>/10/2
BRI <slot>/10
B1
B2
D
BRI <slot>/5/1
BRI <slot>/5/2
BRI <slot>/5
11
B1
B2
D
BRI <slot>/11/1
BRI <slot>/11/2
BRI <slot>/11
B1
B2
D
BRI <slot>/6/1
BRI <slot>/6/2
BRI <slot>/6
12
B1
B2
D
BRI <slot>/12/1
BRI <slot>/12/2
BRI <slot>/12
Phantom Feed Function

The HS-U-6/12 modules can provide DC power to the equipment at the remote
ends of the lines that are connected to its ports, using the phantom feed
method.
The standard feed voltage is 120 VDC.
The source used by HS-U-6/12 module ports to provide phantom feed power to
the equipment connected to the remote end of each line can be a DC power
supply, an appropriate Ringer module installed in the chassis, or an external
Ringer-2000 or Ringer-2200N unit, offered by RAD (see the corresponding Ringer
Installation and Operation Manual for details).
The Ringer modules and units are available in various versions, capable of providing
various standard feed voltages (-24/-48 VDC and +48/+60/+72 VDC). To provide
the phantom feed voltage, the HS-U-6/12 module combines the various DC voltage
inputs to provide a differential voltage, which is the sum of the input DC voltages.
Therefore, to obtain the standard 120 VDC feed voltage, it is necessary to use a
ringer unit that provides -48 VDC and +72 VDC output voltages.
When the lengths of all the lines connecting the remote equipment to the
HS-U-6/12 ports are shorter than the maximum allowed by the standards, it may
be advantageous to reduce the feed voltage, to reduce power dissipation. In this
case, other combinations of input voltages can be used: for example, you can use
a ringer that provides -24 VDC and +60 VDC to obtain a feed voltage of 84 VDC.
B-214
Note
It is not recommended to use (combined) phantom feed voltages less than

60 VDC, since these will not support the minimum line requirements.
The HS-U-6/12 module includes internal jumpers, which must be set in accordance
with the input voltages used to derive the phantom feed voltage. Switches are
available to disconnect the feed voltage from each module port, when the
equipment connected to that port does not require phantom feeding.
See Setting the Internal Jumpers and Connecting the Phantom Feed Voltage
Source sections for details.
Port Interface Characteristics

Each external port interface supports full duplex transmission of 2B+D channels
over one unconditioned two-wire telephone loop (one twisted pair), using
advanced adaptive echo cancellation techniques. The line data rate is 160 kbps,
and the line coding is 2B1Q.
When using 120 V feed voltage, the typical range is 5.5 km (3.4 miles) over 26 AWG
(0.4 mm) pairs. The nominal line impedance is 135 .
All the module external ports are terminated in a common 50-pin SCI connector.
TDM Mapping
payload routing in the HS-U-6/12 modules, independently configurable for each
BRI port, at the individual timeslots (DS0) level.
Each main link allocation unit generated by an HS-U-6/12 module can be
independently routed to any other compatible module installed in the remote
Megaplex unit, configured for the same combination of data rates. Moreover, the
HS-U-6/12 modules support split timeslot allocation.
Management
All the module operating parameters, including functionality (I or 1), are
controlled by means of the Megaplex-4100 system management.
HS-U-6 and HS-U-12 occupy one I/O module slot in the Megaplex-4100 chassis.
All the functional configuration parameters of the modules are determined by
software, except for two parameters, which are selected by means of jumpers: the
phantom feed voltage and the phantom feed function of each port.
Figure B-64 shows typical HS-U-6 and HS-U-12 module panels. The module panels
include status indicators for each channel.
B-215
HSU-12
HSU-6
CH TST LOS
CH TST LOS
6
7
8
Figure B-64. HS-U-6 and HS-U-12

Front Panels
9
10
11
12
CH.
CH.
1-6
1-12
In addition to the indicators, the module has a 50-pin SCSI connector, for
connection to the individual ports. RAD offers an adapter cable, CBL-HSU12,
which is terminated in 12 RJ-45 plugs (one for each port). This cable enables
direct connection to user equipment.
Note
The HS-U-6 module has only 6 ports, therefore if you use the CBL-HSU12 cable,
the connectors of the ports 7 to 12 are not connected. You may order from RAD
an adapter cable for the HS-U-6, CBL-HSU6, terminated in 6 RJ-45 plugs.
LED Indicators
The module panel includes pairs of status indicators, one pair for each port
(channel). The functions of the status indicators are as follows:
LOS indicator: On when the corresponding module port loses synchronization

to the line signal.
TST indicator: On when a loopback is activated on the corresponding port.
Number
of Channels
(Ports)
B-216
HS-U-12
12 ISDN type U
HS-U-6
6 ISDN type U
Port
Characteristics
Compliance
ANSI T1.601, ITU-T Rec. G.961
Nominal line rate
160 kbps (ISDN basic rate access, 2B+D

channels)
Line signal format
2B1Q
Transmission format
Full duplex
Line type
2-wire unconditioned telephone loops (one

twisted pair)
Nominal line impedance
135
Transmit level
+13 dBm
Typical range
5.5 km (3.4 miles) over 26 AWG (0.4 mm) pair
Line connector
50-pin SCSI connector for all the ports (6 or 12)
Port timing
Transmit clock locked to the Megaplex nodal

timing
Receive clock recovered from line signal
Port Transmission I configuration

Mode
1 configuration
Synchronous mode
Synchronous or asynchronous mode, in
accordance with users selection
In asynchronous mode, supports
user-selectable word format (7 or 8 data bits,
transparent transmission of parity bit, one or
two stop bits). In V.110 mode, 5 or 6 data bits
are also supported
End-to-end transfer of one ASMi-31 control
signal (RTS to DTR)
Channel Payload
Rate (I Mode)
Channel Rate
Adaptation and
Multiplexing (1
Mode)
16, 32 or 64 kbps, retrieved from the

B channels, and 16 kbps from D channel
Per ITU-T Rec. I.460 or

V.110
Port Rate
After Rate
Adaptation
Occupied
Bandwidth
1.2 kbps
8 kbps
16 kbps (2 bits)
2.4 kbps
8 kbps
16 kbps (2 bits)
4.8 kbps
8 kbps
16 kbps (2 bits)
9.6 kbps
16 kbps
16 kbps (2 bits)
19.2 kbps
32 kbps
32 kbps (4 bits)
32 kbps
32 kbps
32 kbps (4 bits)
38.4 kbps
64 kbps
64 kbps (8 bits)
48 kbps
64 kbps
64 kbps (8 bits)
B-217
Indicators
Power
Consumption

57.6 kbps
64 kbps
64 kbps (8 bits)
64 kbps
64 kbps
64 kbps (8 bits)
115.2 kbps
128 kbps
128 kbps (two

timeslots)
128 kbps
128 kbps
128 kbps (two

timeslots)
LOS (red)
On upon loss of synchronization
TST (yellow)
On when a loopback is active
HSU-6
4.75W max (0.95A from +5 VAC)
HSU-12
6.5W max. (1.3A from +5 VAC)

Programmable by the Megaplex system
management
Configuration
Configuration downloading from 1 port to

ASMi-31
Full duplex management communication from
1 port to ASMi-31
Warning
Caution
Caution
B-218



Setting the Internal Jumpers

The operating mode of the HS-U-6/12 module is controlled by software. In
addition, there are several jumpers that must be set before installing an
HS-U-6/12 module in the Megaplex-4100 chassis. These jumpers control the
phantom feed voltage (see description in the Phantom Feed Function section of
Section 1.3), and enable/disable the phantom feed function for each module
port.
Note
The module includes additional jumpers that are preset by the manufacturer and
must not be moved.
The actual phantom feed voltage depends on the voltages supplied by the
source. For example:
To obtain the recommended 120 VDC feed voltage, use a source that
provides both -48 VDC and +72 VDC (for example, AC-powered
Ringer-2000/48/72).
To obtain an 84 VDC feed voltage, use a source that provides both -24 VDC
and +60 VDC (for example, -24 VDC-powered Ringer-2000).
Table B-43 lists the resulting feed voltages available from supported combinations of
standard supply voltages.
Table B-43. Chart of Supported Feed Voltages

Negative Voltage
Positive Voltage
Resulting Feed Voltage
-24 VDC
+60 VDC
84 VDC
+72 VDC
96 VDC
+48 VDC (Ringer-2200/P)
96 VDC
+60 VDC
108 VDC
+72 VDC
120 VDC
-48 VDC
Warning
Always disconnect the phantom feed voltages from a port when the equipment
connected to the corresponding port does not require phantom feed. If no port
requires phantom feeding, in addition to per-port jumpers, disconnect the feed
voltages for the whole module, using the jumpers JP15, JP16, JP18, JP19 (see
Figure B-67).
With the voltage connected, dangerous voltages may appear on the line
conductors. In addition, equipment which does not require phantom feed may
present a low DC input resistance and thus will draw unnecessary current from
the phantom feed source. A low resistance may even cause the activation of the
overload protection of the power supply, thereby disrupting the operation of all
the other modules connected to the same line.
B-219
Figure B-65 shows a general view of the HS-U-12 module. The HS-U-12 module
includes the following printed circuit boards:
Main board
IDSL-CPU board
Interface board for ports 1 to 6
Interface board for ports 7 to 12, installed above that of ports 1 to 6.
The HS-U-6 module is similar, except that it does not include the interface board
for ports 7 to 12.
Release these screws
to remove interface board
IDSL-CPU
Board
Interface Board For
Ports 7 - 12
(HS-U-12 Only)
Main Board
Interface Board for Ports 1 - 6
Figure B-65. HS-U-6 and HS-U-12 Modules, General View

For HS-U-6 modules, skip directly to Interface Board for Ports 1 to 6 section
below.
Interface Board for Ports 7 to 12 (HS-U-12 Only)

The user-selectable jumpers located on the interface board for ports 7 to 12 are
shown in Figure B-66.
Table B-44 describes the jumper functions located on this interface board and
indicates their default settings. If the factory (default) settings meet your specific
requirements, you may skip this section.
B-220
Table B-44. Jumpers Located on Interface Board for Ports 7 to 12

Jumper
Port
Port
Port
Port
Port
Port
7
8
9
10
11
12
Function
JP12, JP13
JP10, JP11
JP8, JP9
JP6, JP7
JP4, JP5
JP2, JP3
Each pair controls the connection of the phantom feed to the corresponding port,
and can be independently set as follows:
YES
Phantom feed enabled.
NO
Phantom feed disabled.
Default setting: Jumpers installed (port phantom feed enabled, but depends on the
setting of jumpers JP15, JP16, JP18, JP19 on the interface board
for ports 1 to 6)
Phantom Feed Control
for Port 12 - JP2, JP3
YES
Enabled
ON
JP2
JP3
Port 12
(JP2, JP3)
Port 11
(JP4, JP5)
JP4
JP5
Interface Board for

Ports 7 - 12
Disabled
JP6
JP7
Port 10
(JP6, JP7)
Port 7
(JP12, JP13)
JP10
JP11
JP12
Port 8
(JP10, JP11)
JP8
JP9
Port 9
(JP8, JP9)
JP13
Figure B-66. Internal Settings on Interface Board for Ports 7 to 12 (HS-U-12 Only)
Reaching Interface Board for Ports 1 to 6 (Only for HS-U-12)

For the HS-U-12 module, it is necessary to remove the interface board for ports 7
to 12, to gain access to the jumpers located on the interface board for ports 1 to
6.
Proceed as follows:
Release the four screws identified in Figure B-65.
Carefully separate the interface board for ports 7 to 12 from the other board,
by pulling straight up.
To reinstall the interface board for ports 7 to 12, proceed as follows:
Place the module main board, with the components side up, on a flat, clean
tabletop covered by a soft cloth or rubber sheet.
B-221
Align the connectors on the print side of the interface board for ports 7
to 12 with the corresponding connectors on the module, and then push
lightly to mate the connectors. Make sure that all the pins fit into the
corresponding sockets, and are not bent.
Fasten the board with its four original screws.
Interface Board for Ports 1 to 6

The user-selectable jumpers located on the interface board for ports 1 to 6 are
shown in Figure B-67.
Table B-45 describes the jumper functions located on this interface board and
indicates their default settings. If the factory (default) settings meet your specific
requirements, you may skip this section and proceed directly to installing the
module in the chassis.
for Port 6 - JP2, JP3
YES
Enabled
Disabled
ON
Phantom Feed Voltage

JP15, JP16, JP18, JP19
Port 4
(JP6, JP7)
NO PHV
No Phantom
Feed
E PHV
JP4
JP5
JP2
JP3
Port 5
(JP4, JP5)
JP6
JP7
Interface Board
for Ports 1 - 6
Port 6
(JP2, JP3)
Not Used
JP10
Port 2
(JP10, JP11)
+120V
JP8
JP9
Port 3
(JP8, JP9)
JP11
+72V
Port 1
(JP12, JP13)
JP19
-48V
JP16
JP18
JP12 JP13
JP15
NOTE 1
Actual feed voltage depends on the
voltages supplied by the source
+120V
(Note 1)
+72V
(Note 1)
-48V
(Note 1)
Not
Recommended
Figure B-67. Internal Settings on Interface Board for Ports 1 to 6

Table B-45. Jumpers Located on Interface Board for Ports 1 to 6
Jumper
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
B-222
Function
JP12, JP13
JP10, JP11
JP8, JP9
JP6, JP7
JP4, JP5
JP2, JP3
Each pair controls the connection of the phantom feed to the corresponding port, and can
be independently set as follows:
YES
Phantom feed enabled.
NO
Phantom feed disabled.
Default setting:
Jumpers installed (port phantom feed enabled, but depends on the

setting of jumpers JP15, JP16, JP18, JP19)
Jumper
Function
JP15, JP16, JP18,

JP19
Control the phantom feed voltage connected to the module ports 7 to 12:
-48V
The port provides feed voltage from the -48 VDC line of the internal power
bus of the Megaplex chassis. This option is not recommended since -48V
alone will not support the minimum line requirements.
120V
The port provides a feed voltage of 120 VDC (obtained by using both the -48
VDC and the +72 VDC voltages supplied through the internal power bus of
the Megaplex chassis.
+72V
The port provides feed voltage from the +72 VDC line of the internal power
bus of the Megaplex chassis).
E_PHV
The port provides feed voltage from the external feed voltage source
connected through the pins 1 and 2 of a port connector. This option is not
used.
NO_PHV
The ports are not connected to a phantom feed source and therefore do not
provide phantom feed, even when the port jumpers are set to YES.
Default setting:
NO_PHV (phantom feed disabled)

Warning
To install an HS-U-6/12 module:

3. Insert the module in its chassis slot and slide it backward as far as it goes.
Note
When the Megaplex-4100 is connected to an external ringer, make sure to turn

the ringer off before inserting the module in the Megaplex-4100 chassis.
Turning the ringer off will disconnect on-going voice and ISDN connections,
therefore coordinate this activity with the system administrator.

The connection of users equipment to HS-U-12 modules is made to the 50-pin
SCSI connector located on the module. Table B-46 lists the connector pin
functions. For HS-U-6 modules, only the first six ports (connected to pins 1 to
12) are used.
ISDN equipment is usually equipped with RJ-45 connectors, therefore RAD offers
an adapter cable, CBL-HSU12. This cable has a mating 50-pin SCSI connector at
B-223
one end; the other ends are terminated in 12 RJ-45 plugs, one for each port (the
port number, 1 to 12, is marked near each RJ-45 plug). Figure B-68 shows a
general view of this cable.
The HS-U-6 module has only 6 ports, therefore if you use the CBL-HSU12 cable,
the connectors of the ports 7 to 12 are not connected. You may order from RAD
an adapter cable for the HS-U-6, CBL-HSU6. The CBL-HSU6 cable is similar to the
CBL-HSU12 cable shown in Figure B-68, except that it is terminated in 6 RJ-45
plugs, designated 1 to 6.
Figure B-68. CBL-HSU12 Cable

Table B-46. Module Connector Pin Functions and CBL-HSU12 Cable Wiring
SCSI Pin
1
Port
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
B-224
Function
RJ-45 Pin
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring

SCSI Pin
Port
16
17
18
19
10
20
21
11
22
23
12
24
25
+EPHV
26 to 49
50
-EPHV
Function
RJ-45 Pin
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
External Phantom Feed Voltage - positive line (not

used)
Not connected
External Phantom Feed Voltage - negative line (not

used)
RAD also offers an open-end splitter cable, CBL-HSU12/OPEN/12M. This cable

includes one SCSI-50 and one open-ended connector. The cable is 12m (39.3 ft)
long. See its drawing and pinout in the figure and table below.
Figure B-69. CBL-HSU12/OPEN/12M Cable

Table B-47. CBL-HSU12/OPEN/12M Cable Pinout
Open-Ended
Connector Pin
1
6
7
SCSI-50
Connector Pin
Ring
White
Tip
Blue
Ring
White
Tip
Orange
Ring
White
Tip
Green
Ring
White
Tip
Brown
Ring
White
Tip
Gray
10
Ring
White
11
Tip
White/Blue
12
Ring
White
13
Notes
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
B-225

Open-Ended
Connector Pin
10
11
12
Tip
Orange/Blue
14
Ring
White
15
Tip
Green/Blue
16
Ring
White
17
Tip
Brown/Blue
18
Ring
White
19
Tip
Gray/Blue
20
Ring
White
21
Tip
White/Orange
22
Ring
White
23
Tip
Orange/Green
24
Drain Wire
SCSI-50
Connector Pin
Notes
Twisted
Twisted
Twisted
Twisted
Twisted
Shell
To connect the data channels:
Identify the cables intended for connection to each port of this module, and
connect them into the appropriate connectors, located on the interface
module panel.
When using the CBL-HSU12 cable, pay attention not to touch the exposed
contacts of RJ-45 connectors.
Connecting the Phantom Feed Voltage Source

Note
Review Phantom Feed Function above for a description of phantom feed

considerations.
The DC feed voltage used for phantom feeding can be supplied to the HS-U-6/12
module using one of the following methods (make sure to set the relevant
phantom feed control jumpers of the HS-U-6/12 module accordingly):
Internal DC voltage distribution. The HS-U-6/12 module receives the required

voltages via its internal connector to the chassis voltage distribution bus. No
external source or cable is required. This method can be used when the
chassis receives the required DC voltages from:
DC power supply installed in Megaplex-4100 chassis, provided it operates

on -48 VDC.
Note that this is sufficient for -48 VDC phantom feeding only, and
therefore can be used only on very short lines.
B-226
Ringer-2100R module installed in the Megaplex-4100 chassis.
External source connected to the chassis. The HS-U-6/12 module receives the
required voltages via its internal connector from the chassis voltage
distribution bus, as in the method described above. However, the chassis
receives the DC feed voltage from an external source (for example, from a
Ringer-2000 or Ringer-2200N unit) via a cable connected to the dedicated

VDC-IN connector on the power supply interface module.
Warning
The external voltage source must be either floating in accordance with the
applicable national safety standards, or balanced with respect to ground. The
maximum source voltage must not exceed 120 VDC.
RAD offers a variety of ringer standalone units and modules, which can provide
the required DC power for the Megaplex modules. Refer to the appropriate Ringer
Installation and Operation Manual for details.
Caution
Since an external voltage source can supply voltage even when the Megaplex is
not operating, observe the following precautions:
1. Always turn off the external source, e.g., Ringer, before the Megaplex chassis
is turned off.
2. Never connect external voltages to modules installed in a Megaplex chassis if
it is not operating.
3. Do not connect/disconnect the Ringer while it is operating.
Connecting the Ringer-2000 or Ringer-2200N

The recommended external source for phantom feed voltages is the Ringer-2000
or Ringer-2200N offered by RAD (refer to the appropriate Installation and
Operation Manual for a complete description). The Ringer-2000 and
Ringer-2200N are standalone units, intended for 19" rack mounting, and have a
height of 1U (1.75 in).
To minimize cable runs, the Ringer-2200N or Ringer-2000 should be installed
directly above the Megaplex chassis.
To connect the Megaplex to a Ringer-2000, use a CBL-RINGER-1/TB cable, to

connect between an OUTPUT connector of the Ringer-2000 and the DC input
connector on the Megaplex power supply module. Whenever possible,
connect to the Ringers OUTPUT1 connector.
This connects the phantom feed voltage to all the modules installed in the
chassis that can use such voltages, including voice modules, which use these
voltages as line feed and ring voltages.
To connect to a Ringer-2200N, use a CBL-RINGER2200N-1/TB cable.
Normal Indications
During normal operation, the LOS indicator of each connected port must be off.
The TEST (TST) indicators must be off, except when the corresponding port is
engaged in a test. During tests, the port does not carry user's traffic.
B-227
Handling of B Channels
Users payload data is carried in the B channels. Data in B channels is formatted in
8-bit groups (octets), (the same as in the Megaplex main link timeslots). To enable
efficient transfer of channels carrying data rates lower than the B-channel rate,
rate conversion (adaptation) is required.
The user can select between two multiplexing and rate adaptation methods:
RAD proprietary method, based on the guidelines of ITU-T Rec. I.460.
V.110 multiplexing, an option available only for 1 ports connected to

ASMi-31.
The sources of payload data depend on the channels connected by the user. In the
1 mode, only the payload data carried in the B channels is used (the D channel is
ignored with respect to transmission via the main link). In accordance with the
guidelines of ITU-T Rec. I.460, in the 1 mode the channel payload data is
subjected to rate adaptation to obtain one of the standard rates of 16, 32, or
64 kbps.
The resulting occupied bandwidth is given in Table B-40.
Table B-48. Occupied Bandwidth versus Channel Rate

Channel Rate
Occupied Bandwidth
Number of Bits
1.2 kbps
16 kbps
2.4 kbps
16 kbps
4.8 kbps
16 kbps
9.6 kbps
16 kbps
16 kbps
16 kbps
19.2 kbps
32 kbps
32 kbps
32 kbps
38.4 kbps
64 kbps
8 (one timeslot)
48 kbps
64 kbps
8 (one timeslot)
56 kbps
64 kbps
8 (one timeslot)
57.6 kbps
64 kbps
8 (one timeslot)
64 kbps
64 kbps
8 (one timeslot)
115.2 kbps
128 kbps
16 (two timeslots)
128 kbps
128 kbps
16 (two timeslots)
The table lists all the supported user terminal data rates, the main link bandwidth
required after rate adaptation, the number of B-channel octet bits assigned by
the HS-U-6/12 module to carry the channel payload data, and the corresponding
fraction of main link timeslots for each data rate.
B-228
As shown in Table B-40, the HS-U-6/12 module uses minimum allocations of two
bits (16 kbps). The HS-U-6/12 module multiplexes the data rates obtained after
adaptation to fill the standard main link bandwidth allocation units.
The following examples illustrate Table B-40:
When four channels operate at 4.8 kbps, the main link bandwidth allocated to
these four channels would be one timeslot.
When all four channels operate at 9.6 kbps, the main link bandwidth allocated
to these four channels would still be one timeslot.
When two channels operate at 4.8 kbps, one channel at 19.2 kbps, and one
channel at 128 kbps, the main link bandwidth allocated to these channels
would be as follows:
One-half timeslot (4 bits) for the two 4.8 kbps channels.
A second one-half timeslot (4 bits) for the third channel.
Two additional slots for the fourth channel.
Note that the two one-half timeslot units are combined in one timeslot.

After an external (serial) port of HS-U-6/12 is configured in NT mode and at no
shutdown, its receive clock can be selected as a timing reference for the
Megaplex-4100 system.
External Port Parameters

The external port parameters depend on the operation mode, I or 1. The
mode can be independently selected for each port:
nt Port operates as a network termination unit in the I mode.
lt Port operates as a line termination unit in the I mode.
lt1 Port operates as a line termination unit in the 1 mode (used for
connection to NT equipment, such as ASMi-31).
If interface parameter has been selected as nt (external port operating in the

I mode), you must also select the ISDN activation mode of this port (activationtype parameter):
1 Normal operation
2 For application specific customization
3 For future use.
If interface parameter has been selected as lt1 (external port operating in the
1 mode), the following additional parameters should be configured for each
port: clock-mode, rate, mode (sync/async), end-to-end-control, data-bits, parity,
stop-bits and rate-adaptive (see Serial Ports in Chapter 5). All these parameters
B-229
are automatically downloaded by an HS-U-6/12 port to the connected ASMi-31

units. For other equipment, it is necessary to configure manually the
corresponding equipment parameters.
The available data rates depend on the port transmission mode:
Synchronous mode: 1.2, 2.4, 4.8, 9.6, 16, 19.2, 32, 38.4, 48, 56 (supported
only when connected to an ASMi-31 using V.110 rate adaptation), 64 or
128 kbps.
Asynchronous mode: 1.2, 2.4, 4.8, 9.6, 19.2, 38.4, 48, 57.6 or 115.2 kbps.
When selecting data bits, 5 or 6 data bits are supported only when the remote
equipment is an ASMi-31 using V.110 rate adaptation.
Configuring Internal (BRI, ISDN) Ports (I Mode only)

The internal (BRI) port parameters must be configured only when the
corresponding external ports are configured for operation in the I mode.
The rate-bit parameter specifies the number of bits that must be allocated to
each internal port (B-channel), in accordance with the payload data rate:
The data rates supported by each B-channel are as follows:
2 Used for payload data rates up to 16 kbps.
For the D-Channel rate-bits is constantly set to 2 (16 kbps).

Example. The following example illustrates how to configure the bri ports 3 and 4
(B1, B2 and D-channels) on the HS-U-6 module installed in slot 5:
B-230
mp4100>config# #--------HS-U-6, b-channels---------------mp4100>config#

mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
port
port
port
port
bri
bri
bri
bri
5/3/1 no shutdown
5/3/1 rate-bits 8
5/3/2 no shutdown
5/3/2 rate-bits 8
port
port
port
port
bri
bri
bri
bri
5/4/1
5/4/1
5/4/2
5/4/2
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
#-------- HS-U-6, d-channel-----port bri 5/3 no shutdown

port bri 5/3 rate-bits 2
port bri 5/4
port bri 5/4
no shutdown
rate-bits 8
no shutdown
rate-bits 8
no shutdown
rate-bits 2

via ds0 cross-connect. You can assign only timeslots of ports that have been
already configured, and are configured as no shutdown.
DS1 ports of the MPW-1 module.
Continuing the above example, we connect the B-channels as follows:
B1 channel of port 5/3 to TS #2 of E1 port 2 (I/O slot 1)
ds0
ds0
ds0
ds0
e1
e1
e1
e1
1/2
1/2
1/4
1/4
ts
ts
ts
ts
2
3
2
3
bri
bri
bri
bri
5/3/1
5/3/2
5/4/1
5/4/2
Handling of D Channels (Split Cross-connect on BRI Ports)

The user can independently select the handling of each D channel. The
available options are as follows:
Disconnect (ignore) the D channel.
Connect the D channel directly to the desired main link timeslot. This is done
via the split-ts command. The D channel requires two bits (one quarter
timeslot).
Example. The following example illustrates how to connect the bri ports
(D-channels) on the HS-U-6 module installed in slot 5 as follows:
BRI port 3 to bits 1,2 of TS 4 of E1 port 1/2
B-231
BRI port 4 to bits 1,2 of TS 4 of E1 port 1/4.
split-ts
split-ts
split-ts
split-ts
e1
e1
e1
e1
1/2
1/2
1/4
1/4
ts
ts
ts
ts
4
4
4
4
bits
bits
bits
bits
1
2
1
2
bri
bri
bri
bri
5/3
5/3
5/4
5/4
The list of tasks that can be performed on the HS-U-6/12 module and the
recommended configuration sequence is described in the table below. For
detailed description, refer to Chapter 5. The second column indicates the
Task

service
Configure the external (serial) port

parameters
Configure the BRI ports (rate-bits, I

mode only)
configure>port>bri
Reference
Note: you must also configure the CL.2 or uplink module port parameters (depending on the HS-U-6/12
module application). For the uplink module configuration procedure, refer to the appropriate section of
Appendix B.
Selecting a serial port as system timing
reference
domain(1)
Configure DS0 cross-connect (timeslot

assignment)
configure>cr>ds0

with HS-U-6/12 serial ports, see
Configure split timeslot cross-connect

on BRI ports (timeslot assignment)

with HS-U-6/12 BRI ports, see

The following loopback functions can be individually activated by the system
management for each module channel (serial port):
Remote digital loopback (not supported in the NT mode).
No performance monitoring and statistics is available on the serial ports.
B-232
To activate the loopbacks, use the loopback local and loopback remote
commands in the configure>port>serial context (see Testing Serial Ports in
Chapter 5).
B.11 HS-S Module

operation of the HS-S 4-channel ISDN S interface data module for use in the
use of the module in the Megaplex-2100, Megaplex-2104, and Megaplex-4100
Applications
Figure B-70 shows a typical basic application for HS-S modules that enables direct
connection to the user's ISDN terminal equipment.
Figure B-70. ISDN Extension over non-ISDN Infrastructure
Features
The HS-S modules provide four ISDN basic rate access S channels. Each channel
interface of the HS-S module serves as an ISDN basic rate repeater that enables
the extension of ISDN services to locations at which direct access to the ISDN
facilities is not available, or is not cost-efficient. The extension is provided over
non-ISDN communication media (i.e., over Megaplex data links), which can carry a
wide range of additional data and voice services. Each module channel is
terminated in a separate 8-pin RJ-45 connector.
All the channel operating parameters are controlled by the Megaplex-4100
system management. The timeslots assigned to each HS-S channel in the E1 or
T1 main link frame or SDH/SONET uplink can be individually assigned by the user.
External and Internal Ports

The HS-S module includes four external (BRI) ports, terminated in S interfaces.
Each S interface supports two 64 kbps B channels, which carry payload data,
and one 16 kbps D channel, which carries signaling information.
HS-S Module
B-233
In addition, the S interface can be used to connect the feed voltage (-48 VDC)
to the external line, to provide phantom feed to the equipment at the remote
end of each line.
Each B and D channel is connected to the corresponding internal (serial) port.
Each B channel requires one main link timeslot, whereas each D channel requires
only 2 bits (a quarter timeslot), and therefore can be routed using the split
timeslot function.
Line Interface Characteristics

Each HS-S module interface supports full duplex transmission of 2B+D channels
over unconditioned 4-wire telephone loops (two twisted pairs). The line data rate
is 192 kbps, and the line coding is pseudoternary. The HS-S channels support
data transmission over pairs having a maximum line attenuation of 6 dB at
96 kHz, and a maximum resistance of 100.
This corresponds to a typical range of 1 km (0.6 miles) over AWG 26 (0.4 mm)
pairs. The nominal line impedance is 100.
Each HS-S data channel is terminated in an 8-pin RJ-45 connector.
Phantom Feed Function

The HS-S modules can provide -48 VDC power to the equipment at the remote
ends of the lines that connected to the port, using the phantom feed method.
The source for the phantom feed power can be a -48 VDC chassis power supply,
a Ringer-2100R module installed in the chassis, or a standalone Ringer-2000 or
Ringer-2200N unit connected to the Megaplex AC power supply.
The phantom feed function is controlled by means of internal jumpers,
individually for each port. You can disconnect the feed voltage from each module
port if the equipment connected to that port does not require phantom feeding.
See Table 2-1 and Connecting External Phantom Feed Voltage Source in Chapter 2
for details.
Operating Modes
The HS-S modules have two operating modes, which are simultaneously selected
for all four channels:
TE Mode. The TE (terminal equipment) mode enables the connection of the

HS-S channels to network termination (NT) units. This mode should be used
when the HS-S channels are connected to an ISDN switch.
NT Mode. The NT (network termination) mode enables direct connection of

terminal equipment to the HS-S channels.
TDM Mapping
payload routing in the HS-S modules, independently configurable for each BRI
port, at the individual timeslots (DS0) level.
Each main link allocation unit generated by an HS-S module can be independently
routed to any other compatible module installed in the remote Megaplex unit,
B-234
HS-S Module
configured for the same combination of data rates. Moreover, the HS-S modules
support split timeslot allocation.
Management
All the module operating parameters are controlled by means of the
Megaplex-4100 system management. These systems support flexible timeslot
routing. The user selects the timeslots assigned to HS-S channels in the T1 or E1
main link frame, to route the bit stream generated as a result of the multiplexing
process described above by each local channel.
Each main link allocation unit generated by an HS-S module can be routed
independently to any other HS-S module installed in the remote Megaplex unit,
provided it has been configured for the same combination of data rates.
Timing
The transmit timing used by the HS-S module is locked to the Megaplex nodal
timing; however, the nodal timing mode depends on the selected operating
mode:
TE Mode. In the TE mode, the receive clock of one of the active HS-S
channels, which is recovered from the line signal received from the network
termination unit to which the channel is connected, must be selected as
reference for the nodal timing. This ensures that the HS-S channels transmit
data to the network termination unit using the same timing.
NT Mode. In the NT mode, the Megaplex nodal timing, whose reference can be
selected in accordance with other system considerations, determines the
timing of the data transmitted to the user's terminal equipment connected to
the HS-S channels. The receive timing is recovered from the line signal received
from the user's terminal equipment. Therefore, to ensure that the same timing
is used on the receive direction (from the user's terminal equipment to the
HS-S channel), the user's terminal equipment must operate with loopback
timing.
The HS-S module occupies one I/O module slot in the Megaplex-4100 chassis. All
the functional configuration parameters of the module are determined by
software. Jumpers are used only to select the module port interface (TE or NT),
to connect/disconnect internal terminations for the receive and transmit sides,
and to control the phantom feed function.
The module panel is shown in Figure B-71.
HS-S Module
B-235
HS-S
Channel
1
Channel
2
Channel
3
Channel
4
Figure B-71. HS-S Module Panel

The HS-S module panel includes four 8-pin RJ-45 port connectors, one for each
channel, and two status indicators for each channel.
LED Indicators
The HS-S panel includes two status indicators for each channel. Table 1-1 lists
their functions.
Table B-49. LED Indicators

Item
Description
TST (TEST) Indicator
On when a test is active on the corresponding channel
ACT (ACTIVE) Indicator
On when the corresponding channel is in the activation

state
S Interface
B-236
Number of
Channels
Four
Compliance
ETSI DTR/TM 300012 (physical layer)
Nominal Port Line

Rate
192 kbps (ISDN basic rate access, 2B+D channels)
Line Signal Format
Pseudoternary
Transmission
Full duplex
HS-S Module
Format
Line Type
4-wire unconditioned telephone loops (two twisted

pairs)
Nominal Line
Impedance
100
Transmit Level
750 mV
Receive Levels
+1.5 to -7.5 dB relative to nominal level
Maximum Loop
Loss
6 dB at 96 kHz, maximum resistance 100
Typical Range
1 km (0.6 miles) over AWG-26 (0.4 mm) pair
Line Connector
RJ-45 connector for each port
Port (Channel)
Timing
Transmit clock locked to the Megaplex nodal timing
B Channels
2, 4 or 8 bits (corresponds to data rates of 16, 32 or

64 kbps, respectively)
D Channels
2 bits (corresponds to data rate of 16 kbps)
Diagnostics (per
channel)
Test Loopbacks
Indicators
ACT (green)
On when activation is detected
TST (yellow)
On when a loopback is active
Trunk Interface
Bit Mapping
Receive clock recovered from line signal
Power
Consumption
1.5W
Configuration
Warning

HS-S Module
B-237
Caution The modules contain components sensitive to electrostatic discharge (ESD). To

Caution


The operating mode of the HS-S module is controlled by software. In addition,
several jumpers must be set before installing an HS-S module in the
Megaplex-4100 chassis. These jumpers control the module operating mode, the
internal terminations for the receive and transmit sides, the phantom feed
voltage (see description in Phantom Feed Function in Section 1.3), and
enable/disable the phantom feed function for each module port.
In addition, the modules include additional jumpers that are preset by the
manufacturer and must not be moved. The user-selectable jumpers located on
the HS-S module are shown in Figure B-72. The locations of the fuses that
protect the line interfaces of the four module ports are also shown.
Table B-50 describes the jumper functions and indicates their default settings. If
the factory (default) settings meet your specific requirements, you may skip this
section and proceed with the installation of the module in the equipment
enclosure.
Table B-50. Internal Jumpers

Name
Function
J3
Selects the operating mode, NT or TE, and changes accordingly the routing of the
timing signals.
Default setting: NT
Port 1
Port 2
Port 3
Port 4
TX J4
RX J8
TX J5
RX J9
TX J6
RX J10
TX J7
RX J11
J12, J18
Control the connection of an internal 100 termination to the receive or transmit pair
of each module port. The internal termination should be connected when the
corresponding module port is connected alone to the ISDN line, or when it is the last
module in a multidrop line.
Default setting: Transmit side termination connected
Receive side termination connected
Allow you to disconnect the phantom feeding on a module level (instead of disabling
each channel by its own).
INT=phantom feeding is enabled at the module level (used for NT mode).
EXT=phantom feeding is disabled at the module (used for TE mode).
Default setting: EXT
B-238
HS-S Module

Name
Port
Port
Port
Port
1
2
3
4
Function
J13
J14
J15
J16
Warning
Controls the connection of the phantom feed to each module port: install the
jumper over the two pins to connect the phantom feed voltage.
Default setting: Jumpers installed (phantom feed enabled)
Always disconnect the external supply voltages when the equipment connected to
the module does not require phantom feed. With the voltage connected, dangerous
voltages appear on the line conductors.
In addition, equipment which does not require phantom feed may present a low DC
input resistance and thus will draw unnecessary current from the phantom feed
source. A low resistance may even cause the activation of the overload protection of
the power supply, thereby disrupting the operation of all the other modules
connected to the same line.
HS-S Module
B-239

Jumpers (per Module) J12, J18

Jumpers (per Channel)
J13-J16
INT (Phantom
Feed Enabled
Phantom Feed
Enabled
EXT (Phantom
Feed Disabled)
Phantom Feed
Disabled
J3
Jumper J3
TX TERM
F1
J4
J12 J18
F2
F3
NT
NT Mode
F4
TE
J13
J8
TE Mode
F5
J5
F6
F7
J14
F8
J9
F9
J6
F10
F11
F12
J10
F13
J7
J15
F14
F15
J16
F16
J11
RX TERM
Transmit Side Termination

Jumpers J4, J5, J6, J7
NOTE
Line Protection Multifuses F1 through F16
Have a Rating of 0.1A
Receive Side Termination

Jumpers J8, J9, J10, J11
Internal
Termination
Connected
Internal
Termination
Connected
Internal
Termination
Disconnected
Internal
Termination
Disconnected
Figure B-72. HS-S Module, Internal Settings

Warning
To install an HS-S module:

B-240
HS-S Module

Note
When the Megaplex-4100 is connected to an external ringer, make sure to turn

off the ringer before inserting the module in the Megaplex-4100 chassis.
Turning off the ringer will disconnect on-going voice and ISDN connections;
therefore, coordinate this activity with the system administrator.

The connection of user equipment to HS-S modules is made to the RJ-45
connectors located on the module panel. Each channel of the HS-S module ends
in an RJ-45 connector. Channel connector pin assignment is given in Table B-51.
Table B-51. Channel Connector Wiring

Pin
Function
1, 2
Not connected
Transmit wire +
Receive wire +
Receive wire
Transmit wire
7, 8
Not connected
The channel connector is wired to enable direct connection of user equipment

when operating in the TE mode. When operating in the NT mode, user equipment
must be connected through a cross-cable wired in accordance with Figure B-73.
Figure B-73. Cable for NT Mode
Identify the cables intended for connection to each port of this module, and
connect them into the appropriate connectors (located either on the module
panel or on the interface module panel).
Connecting Internal Phantom Feed Voltage Source

The -48 VDC feed voltage used for phantom feeding can be supplied to the HS-S
module using one of the following methods (make sure to set the relevant
phantom feed control jumpers of the HS-S module accordingly Table B-50):
The HS-S module receives the -48 VDC via its internal connector to the
chassis voltage distribution bus. No external source or cable is required. This
method can be used when the chassis receives the required DC voltages
from:
-48 VDC power supply installed in any Megaplex chassis
HS-S Module
B-241
Ringer-2100R module installed in the chassis
Internal DC voltage distribution from an external source connected to the

chassis (AC-powered Megaplex-4100 only) the HS-S module receives the
-48 VDC via its internal connector from the chassis voltage distribution bus,
as in the method described above. However, the chassis receives the -48 VDC
feed voltage from an external source (for example, from a Ringer standalone
unit) via a cable connected to the dedicated connector on the chassis AC
power supply module panel.
RAD offers a variety of Ringer standalone units and modules, which can provide
the required DC power for the Megaplex modules. Refer to the appropriate Ringer
Installation and Operation Manual for details.
Caution
Since an external voltage source can supply voltage even when the Megaplex
enclosure is not operating, observe the following precautions:
Always turn off the external DC source, for example, Ringer-2000, before the
Megaplex enclosure is turned off.
Never connect external DC voltages to modules installed in a Megaplex
enclosure if it is not operating.
Do not connect/disconnect the Ringer while it is operating.
Normal Indications
The normal indications for an operational channel are as follows:
The ACT indicator of each connected channel lights.
The TST indicators must be off, except when the corresponding channel is
engaged in a test.
Each channel interface (also called module port) carries two B channels, and one
D channel. The maximum data rate supported by each B channel is 64 kbps (equal
to the main link bandwidth allocation unit of the Megaplex system), and the
D-channel data rate is 16 kbps.
Therefore, a maximum of 9 timeslots may be needed by a fully loaded module (all
channels carrying 128 kbps).
B-242
HS-S Module
Handling of D Channels
The handling of the D channels depends on the particular application, therefore
the HS-S module can be configured either to ignore the D channel with respect to
transmission via the main link, or to transfer the D channel transparently
end-to-end.
When the user enables transparent end-to-end transmission of D channels, the D
channels are handled in a similar way to B channels. The D channel of each
module port requires 16 kbps, therefore it is assigned 2 bits in a main link
timeslot.
When the transparent transmission of D channels is simultaneously enabled for
all four ports of the HS-S module, one additional timeslot is required
(4 D channels 2 bits each = one full timeslot).
Configuring the External (Serial) Ports

The interface type (TE or NT) must be set to the same value for all the HS-S
external ports.
Note: The selection made here must match the setting of the internal jumper J3.
If the selections are different, a configuration error message (HARDWARE
MISMATCH) will be generated.
Configuring Internal (BRI, ISDN) Ports

The rate-bit parameter specifies the number of bits that must be allocated to
each internal port (B-channel), in accordance with the payload data rate:
The data rates supported by each B-channel are as follows:
For the D-Channel, rate-bits is constantly set to 2 (16 kbps).

Example. The following example illustrates how to configure BRI ports 3 and 4
(B1, B2 and D-channels) on the HS-S module installed in slot 5:
HS-S Module
B-243
-------------HS-S---------------mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
mp4100>config#
port
port
port
port
bri
bri
bri
bri
5/3/1 no shutdown
5/3/1 rate-bits 8
5/3/2 no shutdown
5/3/2 rate-bits 8
port
port
port
port
bri
bri
bri
bri
5/4/1
5/4/1
5/4/2
5/4/2
-------------d-channel-----mp4100>config# port bri 5/3

mp4100>config# port bri 5/3
mp4100>config#
no shutdown
rate-bits 8
no shutdown
rate-bits 8
no shutdown
rate-bits 2
no shutdown
rate-bits 2
Handling of D Channels (Split Cross-connect on BRI Ports)

The user can independently select the handling of each D channel. The
available options are as follows:
Disconnect (ignore) the D channel.
Connect the D channel directly to desired particular main link timeslot. This is
done via the split-ts command. The D channel requires two bits (one quarter
timeslot).
Example. The following example illustrates how to connect the ports 3

(D-channels) on the HS-S module installed in slot 5 to bits 1,2 of TS 4 of the E1
port 1/2:
split-ts
split-ts
e1
e1
1/2 ts
1/2 ts
4 bits
4 bits
1
2
bri 5/3
bri 5/3
Configuring BRI (ISDN) Ports

The following parameters can be configured for the BRI ports:
Port name
Number of bits that must be allocated to each internal port (B-channel).

After an external (serial) port of HS-S is configured and at no shutdown, its
receive clock can be selected as a timing reference for the Megaplex-4100
system.
B-244
HS-S Module
The list of tasks that can be performed on the HS-S module and the
Task
Configuring a module and put it into

service
Configuring the serial port parameters

(selecting the interface type of the
HS-S external port: NT or TE)
Configuring the BRI ports (rate-bits)
configure>port>bri
Reference
Note: you must also configure the CL.2 or uplink module port parameters (depending on the HS-S module
reference
domain(1)

configure>cr>ds0

modules can be
cross-connected with HS-S
serial ports, see Cross-Connect
Table a in Chapter 5
Configuring split timeslot crossconnect on BRI ports (timeslot

assignment)

modules can be
cross-connected with HS-S BRI
ports, see Cross-Connect Table
in Chapter 5

HS-S diagnostic capabilities include local and remote digital loopbacks on each
The following loopback functions can be individually activated by the system
management for each module channel:
HS-S Module
B-245
Troubleshooting
The loops available on the HS-S modules provide a rapid and efficient way to
identify the general location of a fault in either of the HS-S modules connected in
a link, in the external equipment, or in the connections to the channels.
If a complaint is received regarding the transmission of data through one of the
HS-S channels, perform the following procedure until the problem is located.
After each step, continue to the next step only if the specified test is successfully
completed.
Note
When the problem is detected when a connection between two new users is
activated for the first time, before starting the troubleshooting procedure
described below, thoroughly check the timeslot allocation, the configuration of
the two Megaplex units that provide the new connection, and the configuration
of the user equipment connected to the module.
Request the user to perform a local loopback test on the local data
equipment. If the user equipment does not receive its own signal, the
problem is in the user equipment. After correcting the problem, continue
troubleshooting as explained below.
If the signal is not received when the remote digital loopback is activated,
activate the local main link loop on the local Megaplex unit:
If the user equipment does not receive its own signal when the main link
loop is connected, the problem is in the local Megaplex unit.
If the signal is received when the main link local loopback is activated,
activate the remote main link loop.
If the user equipment does not receive its own signal, the problem is either in the
timeslot allocation or in the remote Megaplex unit.
B.12 HS-703 Module

operation of the HS-703 four-channel G.703 codirectional data sub-multiplexer
module for use in the Megaplex-4100 Next Generation Multiservice Access Node,
ver 3.0 and higher. For use of the modules in the Megaplex-2100,
Megaplex-2104, and Megaplex-4100 ver 2.1 chassis, see their respective
Installation and Operation manuals.
Applications
The figure below shows a typical HS-703 application.
B-246
HS-703 Module
Figure B-74. Typical HS-703 Application
Features
High-Speed Data Transport
The HS-703 module provides Megaplex-4100 with four 64-kbps G.703
codirectional data channels (ports). Each channel can be independently enabled
or disabled by software configuration.
Any channel of the HS-703 module may be directed to any channel of another
HS-703 module at the remote site (the remote module may also be any other
compatible module type). The timeslots used on the E1 or T1 links are individually
assigned for each channel.
An HS-703 channel, when connected to a remote low speed module,
transparently transmits even multiplexed signals.
64 kbps Codirectional Interface

The 64 kbps codirectional interface is defined by ITU-T Rec. G.703, Section
1.1.4.1 and has the following functions:
Bidirectional transfer of data signals
Transfer of 64 kHz bit clock signals associated with the data signals
Transfer of 8 kHz byte clock signals associated with the data signals.
ITU-T Rec. G.703, Section 1 describes three different versions for 64 kbps
interfaces, which differ mainly in the type and direction of the clock signals, and
the number of wires used.
The term codirectional describes an interface that transmits the information and
the associated timing signals in the same direction. The interface uses four wires
(two twisted pairs), one pair for the transmit direction and the other pair for the
receive direction). Each pair carries both the data and the associated clock
signals.
Figure B-75 illustrates the flow of signals across the interface.
Figure B-75. G.703 Codirectional Interface

The 64 kbps codirectional interface transfers data at a nominal rate of 64 kbps,
and a maximum rate tolerance of 100 ppm. The interface uses two balanced
twisted pairs having a nominal impedance of 120.
The transmit pulse shape, measured across a 120 resistive load impedance, is
nominally rectangular. A mark is represented by a peak voltage of 1.0V, and a
HS-703 Module
B-247
space is represented by a voltage of 0 0.10V. The nominal pulse width is

3.9 sec. The maximum line attenuation that should be compensated for by the
receiver is 3 dB at up to 128 kHz.
The interface supports the delineation of byte intervals.
The signal waveform uses coding to carry both clock and timing information, and
to obtain a signal with essentially zero DC component. The coding is performed in
the following steps, illustrated in Figure B-76:
Step 1: The basic 64 kbps bit period is divided into four unit intervals.
Step 2: A binary one is encoded as a block of the following four symbols:

1100. A binary zero is encoded as a block of the following four symbols:
1010.
Step 3: The binary signal is converted into a three-level signal by alternating

the polarity of consecutive blocks (to ensure DC balance).
Step 4: To mark the start and end of a byte, the alternation in polarity of the
blocks is violated every eighth block. The violation block marks the last bit in a
byte.
One Byte
Byte Timing
Step 1 + 2
Bit Number
64 kbps Data
Binary Data
Step 3
Three-Level
Encoded Data
Step 4
Three-Level
Signal
with Polarity
Violations
Violation
Violation
Figure B-76. G.703 Codirectional Signal Coding
Handling of Fault Conditions

Fault conditions are reflected in the signals transmitted by the HS-703 modules:
B-248
If the input signal of a local HS-703 channel is lost, the local HS-703 module
sends an all-ones signal in the corresponding timeslot.
HS-703 Module
The remote HS-703 module channel that receives the all-ones" signal adds
bipolar violations for octet timing, and sends the resulting signal to the
connected user equipment. Thus, the user equipment receives a valid AIS
signal.
If the SDH/SONET uplink or E1/T1/E1-i/T1-i/DS-1 port with which the HS-703

module is cross-connected loses its synchronization, the HS-703 module
signals the local user equipment connected to its channels by sending an allones signal without bipolar violations (i.e., a pure AMI-coded all-ones
signal). The local user equipment must be able to interpret correctly the
reception of this signal.
Timing
HS-703 can provide external timing to the Megaplex-4100 system, thus locking
the Megaplex nodal timing to the external 64-kbps G.703 channel. The external
timing mode is suitable when the HS-703 channel is connected to a G.703 link
provided by a digital transmission network (e.g., a national network or a private
carrier network). Such networks usually incorporate very accurate timing source,
which are always preferable. External timing then allows to lock the transmit
timing of the Megaplex units to the accurate master clock provided by the
network.
TDM Mapping
payload routing in the HS-703 modules, independently configurable for each
Management
All operating parameters of HS-703 are soft-selectable via the management
system.
The HS-703 module occupies one I/O slot in the Megaplex-4100 chassis. The
module panel is shown below. It includes an RJ-45 connector and two status
indicators for each link.
HS-703 Module
B-249
Channel
1
Channel
2
Channel
3
Channel
4
Figure B-77. HS-703 Module Panel
LED Indicators
Separate LED indicators for each channel (see Table B-52) show loss of signal
(TX LOSS) or loss of octet timing/synchronization (OOS).
Table B-52. HS-703 Indicators

Indicator
Description
TX LOSS
Lights when the input signal of the corresponding

channel is missing
OOS
Lights when the octet timing carried by the receive

signal of the corresponding channel is lost
Number of Data
Channels
Data Rate per

Channel
64 kbps
Interface
Codirectional, per ITU-T G.703
Connectors
RJ-45 (one for each channel)
Transmit Pair
Timing (RX-OUT)
HS-703 channel timing is locked to Megaplex nodal

timing
B-250
HS-703 Module
Receive Pair Timing Internal

(TX-IN)
External
Locked to Megaplex nodal timing
Diagnostics
Per channel:
Megaplex nodal timing is locked to the external

G.703 timing source from one of the HS-703
channels
Local loopback (towards local G.703 equipment)
Indicators
(per channel)
Remote loopback (towards remote equipment)
TX LOSS (red)
Loss of signal
OOS (red)
Loss of octet timing
Power
Consumption
1.15W
Configuration
Programmable via Megaplex-4100 management system
Environment
Operating
Temperature
0C to 45C (32F to 113F)
Storage
Temperature
-20C to 70C (-4F to 160F)
Humidity
Warning
Caution
Caution

The HS-703 modules contain components sensitive to electrostatic discharge


HS-703 Module
B-251

HS-703 modules may be installed in an operating chassis (hot insertion).
The HS-703 module starts operating as soon as it is inserted in an operating
chassis.
Warning
To install an HS-703 module:

3. Insert the HS-703 module in its chassis slot and slide it in as far as possible.
4. Secure the HS-703 module by tightening its two fastening screws.

Each link interface of an HS-703 module is terminated in a shielded RJ-45
connector wired in accordance with Table B-53.
Table B-53. Channel Connector Wiring

Pin
Designation
Direction
Function
TD(T)
Input
Transmit data (tip)
TD(R)
Input
Transmit data (ring)
N/A
Not connected
RD(T)
Output
Receive data (tip)
RD(R)
Output
Receive data (ring)
6, 7, 8
N/A
Not connected
To connect the remote equipment:
Connect the remote user equipment directly to the prescribed HS-703 RJ-45
connectors.
Normal Indications
Once the equipment connected to the HS-703 ports is operational, the
corresponding LEDs are off.
B-252
HS-703 Module

After an external serial port of HS-703 is configured and at no shutdown, its
receive clock can be selected as a timing reference for the Megaplex-4100
system.
The list of tasks that can be performed on the HS-703 module and the
Task
Configuring an HS-703 module

Selecting a serial port as system

timing reference
domain(1)

configure>cr>ds0
Reference

with HS-703 serial ports, see CrossConnect Table in Chapter 5

HS-703 diagnostic capabilities include local and remote digital loopbacks on each
HS-703 Module
B-253
Troubleshooting
The loopbacks available on the HS-703 module provide a rapid and efficient way
to identify the general location of a fault in either of the two HS-703 modules
connected in a link, in the external equipment, or in the connections to the
channels.
If a complaint is received from one of the subscribers connected to the HS-703
channels, first activate the local test loop at the side where the complaint comes
from. The local subscriber must receive its own signal.
Check the connections to the user equipment or the user equipment itself.
Replace the local HS-703 module.
If the local subscriber receives its own signal when the local loopback is
connected, activate the remote loopback at the remote side and repeat the
check.
If the remote loopback indicates that the link operates normally, the problem is
at the remote end. To check, repeat the procedure on the remote Megaplex unit.
B.13 HSF-2 Module

operation of the HSF-2 teleprotection interface module for use in the
The module has a dual fiber optic interface, which provides a secure link in
hazardous or hostile environments, increases the maximum connection range,
and provides immunity against electrical interference and protection against the
deleterious effects of ground loops.
The function of the module is to interface between the Megaplex-4100 and an
external fiber optic link in compliance with IEEE PC37.94 standard draft for
n64 kbps fiber optic interfaces to teleprotection equipment. This enables the
teleprotection equipment to use the advanced transport capabilities offered by
Megaplex equipment. The HSF-2 module supports a teleprotection traffic payload in
the range of 64 to 640 kbps per port (that is, n = 1 to 10).
The fiber optic link operates at a line rate of 2.048 Mbps and uses the framing
mode specified in the IEEE PC37.94 standard draft (this framing is based on the
G.732N framing for E1 links).
The modules have two optical ports, operating at a nominal wavelength of
850 mm. The ports are terminated in two ST connectors, for connection to
standard multimode fibers.
B-254
HSF-2 Module
Applications
A typical HSF-2 application is shown in Figure B-78.
Figure B-78. Typical HSF-2 Application

The following configuration restrictions apply:
HSF payload timeslots must always be defined as data timeslots.
To comply with the requirements of the IEEE PC37.94 standard draft, the
Megaplex main link port carrying the HSF payload must be configured with
DATA OOS sequence=FF.
The equipment connected to the remote end of the link should use loopback
timing (i.e., its timing must be locked to the Megaplex nodal timing).
Features
Teleprotection Services
The frame structure used by the HSF-2 external port is in accordance with IEEE
PC37.94 standard draft. The frame structure specified in this standard draft is
similar to the 2.048 Mbps frame structure of ITU-T Rec. G.704 and the no-signaling
frame structure (G.732N) of ITU-T Rec. G.732. The main differences are as follows:
Timeslots 0 to 7 are used for the teleprotection link overhead, and therefore
the first payload timeslot is 8.
The payload data encoding method uses two teleprotection link bits to
represent each teleprotection payload bit. Therefore, two link timeslots
(128 kbps) are needed for each 64 kbps teleprotection channel.
For example, when the teleprotection payload rate is 64 kbps, the
teleprotection link rate is 128 kbps and used timeslots are 8 and 9. The other
payload timeslots, that is, 10 to 31, carry alternating 1 and 0. However,
within the HSF module the data received from the telecommunication
equipment is decoded and the contents of each pair of timeslots is restored
to 64 kbps before being routed to a Megaplex TDM bus. Therefore, in this
example, only one timeslot is transferred to the TDM bus.
The reverse process occurs in the HSF transmit path: each timeslot received
from a TDM bus is encoded and inserted in two consecutive timeslots
(starting with 8).
Link Interface Characteristics

The HSF-2 modules have dual optical interface for operation over multimode
fibers terminated in a ST connector. The nominal wavelength is 850 mm.
HSF-2 Module
B-255
The fiber optic interface offers high performance and has a wide dynamic range,
which ensures that the receiver will not saturate even when using short fiber
optic cables. (Saturation is caused when the optical power applied to the receiver
exceeds its maximum allowed input power, and results in very high bit error
rates.)
Handling of Fault Conditions

Fault conditions are reflected in the signals transmitted by the HSF-2 modules:
To the local teleprotection equipment: if local loss of frame synchronization

on the corresponding main link port occurs, the HSF module inserts a 1010...
sequence in the timeslots sent to the teleprotection equipment.
To the remote equipment: if local loss of frame synchronization or loss of

input signal occurs on the receive path of the HSF module, the module sends
a stream of 1 to the TDM bus toward the corresponding main link port
(equivalent to an FF out-of-service (OOS) sequence).
Timing
The HSF transmit path timing is derived from the nodal clock used by the
Megaplex-4100. The nodal clock source can be selected in accordance with
system requirements. The HSF-2 module cannot be selected as timing source.
The receive path of the HSF-2 optical port uses the clock signal recovered from
the corresponding received line signal. Therefore, user teleprotection equipment
should use loopback timing; that is, its link transmit clock should be locked to the
receive clock derived from the receive data of the same port.
TDM Mapping
payload routing in the HSF-2 modules, independently configurable for each port,
at the individual timeslots (DS0) level.
Management
All operating parameters of HSF-2 are soft-selectable via the management
system.
The HSF-2 module occupies one I/O slot in the Megaplex-4100 chassis. The
module panel is shown in Figure B-3. Each port has two optical connectors,
designated TX (transmit output) and RX (receive input).
B-256
HSF-2 Module
HSF-2
ALARM
TST
ON
LINE
LOC
REM
S. LOSS
RX
L
I
N
K
1
TX
ALARM
ON
TST
LOC
REM
S. LOSS
RX
L
I
N
K
2
TX
Figure B-79. HSF-2 Module Panel
LED Indicators
Table B-52 explains the functions of the indicators located on the module panel.
Table B-54. HSF-2 Indicators
Indicator
Description
ALARM
Lights when a fault has been detected in the module
ON LINE
Lights when the module is operating properly and is

active
Off when the module is defective, or is not connected to
a TDM bus
LOC S. LOSS
Lights when the local module has lost frame

synchronization
REM S. LOSS
Lights when a loss-of-frame synchronization indication is

received by the module from the equipment connected
to the remote end of the fiber-optic link
TST
Not used
HSF-2 Module
B-257
Number of Links 2
Payload Rate
n 64 kbps per port, where n = 1 to 10 (64 to 640 kbps)
Line Interface
Characteristics
Nominal Bit Rate
2.048 Mbps
Wavelength
850 nm
Fiber Type
62.5/125 m multimode
Transmitter Type
VSCEL
Power Coupled into Fiber
-19 to 11 dBm (-15 dBm typical)
Receiver Sensitivity
-32 dBm
Optical Budget
13 dB
Maximum Receiver Input Power
-11 dBm
Receiver Dynamic Range
21 dB
Typical Range
2 km (with 6.8 dB margin)
Frame
IEEE PC37.94 draft
Connectors
ST
Timing
Internal Oscillator
30 ppm
Indicators
Module
Alarm
Link Interface
On-line
Local sync loss
Remote sync loss
Power
Consumption
9.0W
Configuration
Programmable via Megaplex-4100

management system
Warning
B-258

HSF-2 Module

Caution
Caution
The HSF-2 modules contain components sensitive to electrostatic discharge



HSF-2 modules may be installed in an operating chassis (hot insertion).
The HSF-2 module starts operating as soon as it is inserted in an operating
chassis.
Warning
HSF-2 modules comply with laser product performance standards set by government
agencies for Class 1 laser products. The modules do not emit hazardous light, and
the beam is totally enclosed during all operating modes of customer operation and
maintenance.
HSF-2 modules are shipped with protective covers installed on all the optical
For your safety:
Warning
To install an HSF-2 module:

Refer to the system installation plan and identify the prescribed module slot.
HSF-2 Module
B-259
2. Insert the HSF-2 module in its chassis slot and slide it in as far as possible.
3. Secure the HSF-2 module by tightening its two fastening screws.

Before starting, refer to the installation plan to determine the fiber-optic cables
intended for connection to the HSF-2 module.
Before connecting, clean the optical connectors using an approved solvent, and
dry thoroughly using optical tissue. Avoid sharp bends and twisting of the fiber
optic cables.

Connect the prescribed cables to the following connectors on the module panel:
Connect the transmit cable to the TX connector
Connect the receive cable to the RX connector.
Normal Indications
When the link connected to the HSF-2 module is operational, its ALARM indicator
must be off.
The normal indications for an operational link interface are as follows:
The ON-LINE indicator of an active link lights steadily.
If the other communication equipment on the link is not yet operative, the
corresponding LOC S. LOSS and/or REM S. LOSS indicator may light. These
indicators turn off as soon as the link with the remote equipment is
established.
As a result of the IEEE PC37.94 requirements, the following configuration

guidelines apply:
B-260
HSF-2 Module
HSF-2 payload timeslots must always be defined as data timeslots.
To comply with the requirements of IEEE PC37.94 standard draft, the

Megaplex-4100 main link port carrying the HSF-2 payload must be configured
with DATA OOS sequence=FF.
The list of tasks that can be performed on the HSF-2 module and the
Task
Configuring an HSF-2 module and

put it into service
Reference
Note: you must also configure the CL.2 or uplink module port parameters (depending on the HSF-2 module
Configuring the serial port rate

configure>cr>ds0

with HSF-2 serial ports, see CrossConnect Table in Chapter 5

The HSF-2 module panel includes indicators that display the status of the link
interface (loss of local and remote synchronization), and the presence of alarms
in the module.
The HSF-2 modules do not support loopbacks and tests.
Caution
Activation of a loopback or test on the HSF-2 link disconnects the external link;
therefore it is not allowed under any circumstances.
Troubleshooting
If a problem occurs, check the displayed alarm messages and refer to Chapter 6
for their interpretation.
If the problem is related to the HSF-2 module, pull the module out, and wait
about one minute. After reinserting the module, read the power-up test results.
Replace the module if any fault is reported.
to the operation of the main link serving the HSF-2 module, perform the actions
HSF-2 Module
B-261
If the fault occurs after configuration changes or on the first time the module
is operated, check for correct configuration.
If traffic to other modules is served by the same main link port as used by the
HSF-2 module, troubleshoot the main link module:
Activate the local loopback on the corresponding main link port. If the
S. LOSS LOC indicator of the local main link port turns off while the loop
is connected, the problem is external. Check cable connections and the
transmission equipment providing the link to the remote Megaplex unit.
Quickly check the link to the remote Megaplex unit by activating the
remote main link loopback at the remote unit. If the corresponding link
operates properly, the S. LOSS LOC indicator of the corresponding local
main link turns off.
If the problem persists, the main link module is probably defective and needs to
be replaced.
B.14 LS-6N and LS-12 Modules

operation of the LS-6N and LS-12 data sub-multiplexer modules for use in the
ver 2.1 chassis, see their respectiveInstallation and Operation manuals.
The modules occupy one enclosure slot and provide six/twelve synchronous or
asynchronous data channels with ITU-T Rec. V.24/EIA RS-232 interfaces that can
operate at user-selectable data rates in the range of 2.4 to 64 kbps.
Applications
Figure B-80 shows a typical point-to-point application for a Megaplex system
equipped with LS-6N modules. In this application, the LS-6N modules connect a
group of remotely-located terminals to the central corporate computing
resources (a minicomputer or mainframe with communication front end).
6 data channels
(2.4 to 64 kbps)
6 data channels
(2.4 to 64 kbps )
14 .4 to
76 8 kbps
LS-6N
Mini computer
or
Mainfra me
ML -T1
MP-2 100
14.4 to
768 kbps
E 1/T1
Network
M L-T1
LS-6N
MP -410 0
CBL-LS 12
octop us
cabl e
Figure B-80. Typical LS-6N Point-to-Point Application
B-262
LS-6N and LS-12 Modules
Figure B-81 shows an application in which LS-6N is used by Megaplex-4100 to

connect low speed data traffic such as data terminals, surveillance cameras, and
train track signaling equipment, over T1 TDM lines. In this combined TDM/IP
application, LS-6N is employed, together with HS-6N modules for high speed data
channels, VC-8 modules for analog voice channels, and M8T1 modules for digital
voice channels. All data traffic is over a T1 line, while analog telephone and digital
PBX voice traffic is over IP. This is achieved using a single device, Megaplex-4100.
Network
Management
System
T1
T1
Digital voice
Digital voice
IP Network
M8T1
PBX
ice
Vo
Vo
ice
PBX
Analog voice
M8T1
MPW-1
MPW-1
VC-8
VC-8
Schedule
information
LS-6N
LS-6N
64 kbps
Surveillance
camera
T1 Network
MP-4100
Low
speed
data
Low
speed
data
4.8 kbps
9.6 kbps
Work Clock
Terminal
Da
ta
HS-6N
MP-4100
2.4 kbps
n x 56, 64 kbps
HS-6N
ta
Da
Server
12:45
M8T1
M8T1
n x 56, 64 kbps
High speed data
Analog voice
4.8 kbps
High speed data

Server
2.4 kbps
12:45
Schedule
information
64 kbps
Surveillance
camera
9.6 kbps
Work Clock
A.T.O.
system
A.T.O.
system
(Automatic Train
Operation)
(Automatic Train
Operation)
Terminal
Figure B-81. Connecting Data and Voice Traffic over T1 TDM /IP Network
The module data channels have standard EIA RS-232/ ITU-T Rec. V.24 interfaces.
The interface type, DCE or DTE, is user-selectable by means of internal switches,
separately for each channel.
Features
The LS-6N and LS-12 modules are used to achieve highly efficient utilization of
the uplink bandwidth for low-speed transfer applications, by dividing the uplink
bandwidth into smaller units with very little overhead.
The uplink bandwidth required by one LS-6N or LS-12 module depends on the
total channel data payload. The available selections are 14.4 kbps (quarter
timeslot), 32 kbps (half timeslot), 56 or 64 kbps (one timeslot), 128 kbps (two
timeslots), 192 kbps (three timeslots), 256 kbps (four timeslots), 384 kbps (six
timeslots), and 512 kbps (eight timeslots) and 768 kbps (twelve timeslots). The
uplink timeslots used by the LS-6N, LS-12 modules are user-selectable.
For flexibility, the LS-6N module is equipped with a single internal (serial-bundle)
port, which is used to form a composite data stream. All six external user (serial)
ports are routed to this internal port. The internal port can be routed to either of
the Megaplex uplink ports.
B-263
The LS-12 module is equipped with two internal (serial-bundle) ports, which can
be used to form two composite data streams. Each internal port can be routed to
either of the Megaplex uplink ports. Twelve external (user, serial) ports can be
routed to either of the two internal ports.
Data Channel Characteristics

The data channels have standard EIA RS-232/ ITU-T Rec. V.24 interfaces. The
interface type, DCE or DTE, is user-selectable by means of the interface module
internal switches, separately for each channel.
Each module channel can be configured for either synchronous or asynchronous
operation, with the asynchronous-to-synchronous conversion being made in
accordance with ITU-T Rec. V.14. The timing mode of channels configured for
operation in the synchronous mode is selectable.
Within the LS-6N module, channels are processed in three pairs: 1 and 2, 3 and 4,
5 and 6. Within the LS-12 module, channels are processed in six pairs: 1 and 2, 3
and 4, 5 and 6, 7 and 8, 9 and 10, 11 and 12.
Note
Each pair of the external user channel must be routed to the same internal
composite channel. The user channels must also operate at the data rates
belonging to the same rate group and support the end-to-end transmission of
the matching control signals, as explained in the following sections.
Each group of six data channels terminates in a single SCSI 68-pin female
connector, which enables connection of the LS-6N, LS-12 data channels to a
distribution frame. RAD also offers a special octopus cable, which ends in six
25-pin D-type male or female connectors, which enables the connection of each
channel directly to the user equipment.
The data rates and other operating parameters of the LS-6N, LS-12 data
channels are configured by means of the system management.
Channel Rates
Each channel supports three groups of data rates:
Group 1: all the standard rates in the range of 2.4 to 38.4 kbps (except the
rates defined as belonging to Group 2 and Group 3), in either the
synchronous or asynchronous mode.
Group 2: 7.2, 14.4, 28.8 and 57.6 kbps, in either the synchronous or
asynchronous mode.
Group 3: 8, 16, 24, 32, 48, 56, and 64 kbps in the synchronous mode only.
Channel rates can be freely selected, as long as both channels of a given pair operate
at rates taken from the same group. Channel data rates, as well as all the channel
operating parameters, are controlled by means of the system management.
Synchronous Data Channel Timing Modes

LS-6N, LS-12 channels configured for operation in the synchronous mode have
user-selectable timing modes, which can be independently selected for each
channel. Together with a set of internal channel buffers, these timing modes
B-264
permit connection to various types of digital lines, including digital data services,
and ensure data integrity.
The timing modes are as follows:
DCE: when this timing mode is selected, the LS-6N/12 channel provides the
timing (transmit and receive clock signals) to the user equipment connected
to it. These clock signals are derived from the Megaplex nodal clock.
The DCE timing mode is intended for use when equipment with a DTE
interface is connected to the LS-6N/12 channel. To use this mode, the
interface of the LS-12 channel must be set to DCE (via the SW switch of the
relative channel).
External DCE: the LS-6N/12 channel provides the receive timing signal
(derived from the Megaplex nodal clock) to the equipment connected to the
channel, and accepts the transmit timing from the connected equipment. In
this case, the LS-6N/12 channel internally buffers and retimes the transmit
data in accordance with the Megaplex nodal clock. To avoid clock slips, the
transmit timing should be locked to the receive timing.
The external DCE timing mode is intended for use when the LS-6N/12 channel
is connected to equipment with DCE interface in a tail-end circuit. To use this
timing mode, the interface of the LS-6N/12 channel must be set to DTE (via
the SW switch of the relative channel).
DTE: the LS-6N/12 channel requires receive and transmit timing signals from
the equipment connected to the channel. To use this timing mode, the
interface of the LS-6N/12 channel must be set to DTE (via the SW switch of
the relative channel).
One of the LS-6N/12 channels operating in the DTE timing mode can be
selected as the reference timing source for the Megaplex nodal timing,
provided the channel data rate is a multiple of 8 kbps (8, 16, 24, 32, 48, 56,
or 64 kbps). In this case, the Megaplex system will actually use the transmit
clock of the selected LS-12 channel as long as the channel RTS line is active.
The DTE mode is mainly intended for use when the LS-6N/12 channel is
connected to equipment with DCE interface, which is used to provide the
timing reference for the Megaplex system (e.g., when the LS-6N/12 channel
is connected to a data network, or to a channel of a higher-level multiplexer).
The DTE mode can be also used when the equipment connected to the
channel uses timing derived from the same source used to provide the
Megaplex nodal clock reference.
Asynchronous Channel Characteristics

The timing mode of asynchronous channels is always DCE; i.e., the channel data
rates are derived from the Megaplex nodal timing.
For channels operating in the asynchronous mode, the number of data bits in the
word is user-programmable: 6, 7, 8, or 9. When parity is used (from the remote
equipment), the total number of bits to be taken into account includes the parity
bit, because the parity bit is transparently transferred.
In addition to the selected number of data bits, the word format includes one
start bit and one stop bit.
B-265
Support of Interface Control Signals

The LS-6N, LS-12 modules provide two user-selectable modes of support for the
V.24/RS-232 interface control signals of its data channels:
Local control signal support. This mode can be independently selected for
each channel. When local support is enabled, the channel locally supports five
interface control signals, that is, the state of the control signals is not
transmitted to the remote channel. The locally-supported control signals are
as follows:
DTR: this is an input signal for channels with DCE interface, and an output
signal, always ON, for channels with DTE interface.
RTS: this is an input signal for channels with DCE interface, and an output
signal for channels with DTE interface.
CTS: this is an output signal for channels with DCE interface, and an input
For channels with DCE interface, the user can select between
permanently asserting the CTS line (CTS line always ON), or making the
CTS line follow the state of the RTS line.
DSR: this is an output signal for channels with DCE interface, and an input
For channels with DCE interface, the DSR line is constantly ON, except
when the link serving the internal port to which the channel is connected,
is down because of loss of frame synchronization.
DCD: this is an output signal for channels with DCE interface, and an
input signal for channels with DTE interface.
For channels with DCE interface, the DCD line is constantly ON, except
when the link serving the internal port to which the channel is connected,
is down because of loss of frame synchronization.
End-to-end transmission of control signals. This capability is used when

necessary to transmit the state of the interface control signals, which control
the channel data flow through the Megaplex link, e.g., for applications which
require hardware flow control. To minimize bandwidth requirements, two
selections are available:
End-to-end transmission of local RTS line state to the remote DCD line,
and vice versa. Note that this mode is relevant only when the two
channels are configured with DCE interfaces.
End-to-end transmission of local RTS line state to the remote DCD line,
and local DTR line to the remote DSR line, and vice versa. Note that this
mode is relevant only when a channel configured with DCE interface is
connected to a remote channel with DTE interface.
The end-to-end transmission mode can be independently selected for each

channel. However, when both channels of a given pair are configured for
end-to-end transmission, both must be configured to transmit the same
number of control signals, i.e., you cannot configure one channel to transmit
one control signal (i.e., RTS to DCD) end-to-end, and the other channel - two
control signals (RTS and DTR). Typical end-to-end delay is 2.5 msec.
B-266
The LS-6N and LS-12 modules occupy one I/O module slot in the Megaplex-4100
chassis. Typical panels of the LS-6N and LS-12 modules are shown in Figure B-82
and Figure B-83, respectively. The LS-6N panel includes one 68-pin female SCSI
connectors designated CH.1-6, for connection to the data channels. The LS-12
panel includes two such connectors designated CH.1-6 and CH.7-12.
LS-6N
CH.
1-6
LS-12
CH.
1-6
Channel
Connector
CH.1-6
Connector
S. LOSS
S. LOSS
CH.
7-12
Figure B-82. LS-6N Panel
S. LOSS B
Indicator
S. LOSS A
Indicator
Sync Loss
Indicator
CH.7-12
Connector
Figure B-83. LS-12 Panel
In addition, the module panels include alarm indicators.
LED Indicators
LS-12 has two alarm indicators, designated S.LOSS A and B. Each indicator lights
if the synchronization machine serving the corresponding composite channel
loses synchronization to the incoming signal. LS-6N has only one indicator,
designated S.LOSS.
General
Number of User
Channels (External
Ports)
6/12 channels, processed as 3/6 pairs (1 and 2, 3 and 4,

5 and 6, 7 and 8, 9 and 10, 11 and 12)
B-267
Number of
Composite Channels
(Internal Ports)
LS-6N: One, routable to either of the Megaplex uplink

ports
Uplink Bandwidth
Requirements
14.4 kbps (quarter timeslot)
LS-12: Two, each independently routable to either of

the Megaplex uplink ports
32 kbps (half timeslot)

56 kbps (one timeslot)
64 kbps (one timeslot)
128 kbps (two timeslots)
192 kbps (three timeslots)
256 kbps (four timeslots)
384 kbps (six timeslots)
512 kbps (eight timeslots)
768 kbps (twelve timeslots)
Channel Multiplexing
Technique
Data Channel
Data Channel
Characteristics Interface Type
Each pair of external channels can be independently

connected to each internal port
ITU-T Rec. V.24/EIA RS-232, user-selectable DCE or DTE
interface
Operation Mode
Synchronous or asynchronous, user-selectable
Async-to-Sync
Conversion Method
Compatible with ITU-T Rec. V.14
Synchronous
Operation Timing
Modes
DCE (for direct connection to DTE)

External DCE (for direct connection to DCE in the
tail-end mode)
DTE (for direct connection to DCE)
Asynchronous Word
Parameters
Number of Data
and Parity Bits
Total of 6, 7, 8 or 9, user-selectable
Parity Bit
Transparently transferred
Stop Bits
Data Channel
Connectors
B-268
One SCSI 68-pin female connector for each group of six

channels
Data Rates
Independently selectable for each channel, except that

the two channels of one pair must use rates from the
same group
Group 1
2400, 4800, 9600, 19200 and 38400 bps in either

synchronous or asynchronous mode
Group 2
7.2, 14.4, 28.8, and 57.6 kbps in either synchronous or

asynchronous mode
Group 3
8, 16, 24, 32, 48, 56, and 64 kbps in synchronous mode

only
Control Signals
Support mode is user-selectable for each channel
Local Support
RTS, CTS, DSR, DCD, DTR
End-to-End
Transfer
Selectable:
RTS-to-DCD (2.5 msec typical delay)
RTS-to-DCD and DTR-to-DSR (2.5 msec typical delay)
Diagnostics
Composite Data
Streams
Local digital loopback on the selected composite data

stream
Remote digital loopback on the selected composite
data stream
Data Channels

Indicators
S.LOSS A
S.LOSS B (LS-12
only)
Power
Consumption
Configuration
On when synchronization is lost on the composite

channel
LS-6N
4.9W
LS-12
6.25W
Warning

B-269
Caution
Caution



The operating mode of the LS-6N, LS-12 modules is controlled by software.
In addition, the modules have switches that select the interface mode of each
channel: DTE or DCE. Default setting is DCE.
Note
When selecting the data channel timing reference, observe the following DTE/DCE
switch settings:
DCE clock mode: the DTE/DCE switch is set to DCE.
DTE or External DCE clock mode: the DTE/DCE switch is set to DTE.
Figure B-84 shows the construction of the LS-12 modules, and identifies the
location of these switches (12 switches, one for each channel). The LS-6N
module differs only in that it contains 6 channels.
Before installing a module in the Megaplex-4100 enclosure, check the settings of
these switches. If the current settings of these switches meet your system
requirements, skip this section and proceed with the module installation in the
Megaplex-4100 enclosure, as explained below; otherwise, change the switch
settings as required.
B-270
Interface Mode
Selection
DTE
DTE
DCE
DCE
SW 1
SW13
SW 2
SW14
SW 3
SW15
SW 4
SW16
SW 5
SW17
SW 6
SW18
SW 7
SW19
SW 8
SW20
SW 9
SW21
SW 10
SW22
SW 11
SW23
SW 12
SW24
Channel 1
.
Channel
2
.
.
.
.
.
.
.
.
.
.
.
.
Channel 12
Figure B-84. Module LS-12, Internal Settings

Warning
To install an LS module:
B-271

Data Channel Connectors
The LS-12 user data channels terminate in two 68-pin female SCSI connectors,
designated CH.1-6 and CH.7-12. LS-6N includes only one connector, designated
CH.1-6. Table B-55 lists the connectors pin allocations. Note that the direction of
control signals depends on the channel interface mode.
Table B-55. CH.1-6 and CH.7-12 Connectors, Pin Assignment

Pin
Channel
CH.1-6
Designation
CH.7-12
DCE
DTE
Frame Ground, all channels
Transmit data, channel 1 (7)
In
Out
External transmit clock, channel 1 (7)
In
Out
Data carrier detect, channel 1 (7)
Out
In
Data set ready, channel 1 (7)
Out
In
Clear to send, channel 1 (7)
Out
In
In
Out
In
Out
Out
In
10
Out
In
11
Out
In
12
External receive clock, channel 3 (9)
In
Out
13
In
Out
14
In
Out
15
Out
In
16
Out
In
17
Out
In
18
10
In
Out
19
10
In
Out
20
10
Out
In
21
10
Out
In
22
10
Out
In
23
11
In
Out
24
11
In
Out
25
11
In
Out
B-272

Pin
Channel
CH.1-6

Designation
CH.7-12
DCE
DTE
26
11
Out
In
27
11
Out
In
28
11
Out
In
29
12
In
Out
30
12
In
Out
31
12
Out
In
32
12
Out
In
33
12
Out
In
34
12
In
Out
35
Receive clock, channel 1 (7)
Out
In
36
Request to send, channel 1 (7)
In
Out
37
Receive data, channel 1 (7)
Out
In
38
Transmit clock, channel 1 (7)
Out
In
39
Data terminal ready, channel 1 (7)
In
Out
40
In
Out
41
Out
In
42
In
Out
43
Out
In
44
Out
In
45
In
Out
46
In
Out
47
Out
In
48
In
Out
49
Out
In
50
Out
In
51
In
Out
52
10
Out
In
53
10
In
Out
54
10
Out
In
55
10
Out
In
56
10
In
Out
57
10
In
Out
B-273

Pin
Channel
CH.1-6
Designation
CH.7-12
DCE
DTE
58
11
Out
In
59
11
In
Out
60
11
Out
In
61
11
Out
In
62
11
In
Out
63
12
Out
In
64
12
In
Out
65
12
Out
In
66
12
Out
In
67
12
In
Out
68
Signal ground, all channels
Octopus Cable
For direct connection to users data equipment, RAD offers ready-made octopus
cables, CBL-LS12, having a length of 2m. These cables end in six 25-pin D-type
male connectors that can be directly connected to DTE's.
Table B-56 lists the connections between the pins of the 68-pin SCSI connector,
which connect to the CH.1-6 or CH.7-12 connector of the
LS-12 module, and the pins in the six user-side connectors of the cable.
Table B-56. CBL-LS12 Octopus Cable Wiring

LS-12
Connector
Pin
B-274
Designation
User Side 25-Pin Connector

and Pin
Frame Ground, all channels
All connectors, pin 1
Connector 1 (7), pin 2
10
11

LS-12
Connector
Pin

Designation

and Pin
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
B-275
LS-12
Connector
Pin

and Pin
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Signal ground, all channels
All connectors, pin 7
B-276
Designation
Connect one cable end to the module connectors, designated

CH.1-6 and CH.7-12, respectively, and the other end straight to the DTE
equipment.
Normal Indications
During normal operation, the indicators are off.
Routing to the Composite Channels
The LS-6N module has a single internal (serial-bundle) port, which connects the
composite data stream of the module to the TDM buses. The LS-12 module has
two internal (serial-bundle) ports, which connect the composite data stream(s) of
the module to the TDM buses. The functionality of the two ports can be
independently controlled:
External (serial) user ports can be routed to either of the two internal (serialbundle) ports. The only restriction is that the two ports of a pair are always
routed together, to the same internal port. Therefore, all 12 user ports can
be routed to the same internal port.
Each internal port can be routed to either of the Megaplex uplink ports.
Each internal port can use the following uplink bandwidths:
14.4 kbps, requires the allocation of quarter timeslot.
32 kbps, requires the allocation of half timeslot.
56 kbps, requires the allocation of one timeslot.
64 kbps, requires the allocation of one timeslot.
128 kbps, requires the allocation of two timeslots.
192 kbps, requires the allocation of three timeslots.
256 kbps, requires the allocation of four timeslots.
384 kbps, requires the allocation of six timeslots.
512 kbps, requires the allocation of eight timeslots.
768 kbps, requires the allocation of twelve timeslots.
The selection of the optimal bandwidth depends on the total user payload rate,
as is explained in the following section.
Timeslots can be freely allocated to each internal port, in accordance with the
standard timeslot allocation rules (e.g., timeslots allocated to one internal port
must not overlap timeslots allocated to the other port, or any other module in
the Megaplex unit).
The timeslots allocated to each internal port must always be handled as a bundle
(a single block of timeslots) with respect to the routing within the transmission
network. Splitting the bundle may affect the order of reception of the individual
bits at the remote location, and therefore may prevent the operation of the
LS-6N/12 link by disrupting the exchange of housekeeping and synchronization
information contained in the composite data stream.
B-277
Bandwidth Allocation
The Megaplex uplink bandwidth assigned to an LS-6N/12 composite data stream
(serial-bundle port) must be internally allocated to the individual user channels
routed to that port, and to the housekeeping information required for proper
transmission and reception of each composite data stream.
Each composite channel data stream carries two basic types of information:
User data, consisting of:
External channels payload data.
External channels end-to-end signaling.
Composite channel housekeeping data, consisting of:
Frame synchronization data for the link between the two module ports.
Inband management channel.
The technique used to manage the composite channel bandwidth is permanent

on-demand allocation. This means that within the module, bandwidth is
permanently allocated to the external channels connected to a composite
channel, in accordance with each external channel data rate and the end-to-end
signaling requirements. The internal bandwidth is automatically reallocated when
a change occurs in the number of user channels connected to a composite
channel.
The bandwidth that must be assigned to a composite channel on the
corresponding Megaplex TDM bus (i.e., E1/T1 card) must be equal to, or greater
than, the total bandwidth needed for carrying the various types of information
listed above.
Bandwidth allocation is performed by organizing the composite data stream in
frames. Each bit in a frame can be independently allocated, and therefore it
serves as the bandwidth allocation unit. Therefore, the total number of
bandwidth allocation units equals the frame length, in bits.
As a result, the frame length and the information-carrying capacity (in kbps) of
an allocation unit vary with the uplink bandwidth assigned to an LS-6N/12
composite channel, as listed in Table B-57.
Table B-57. Composite Channel Multiplexing Data
B-278
Assigned Bandwidth
Composite
Frame Length
Bandwidth
Allocation Unit
Bandwidth Available to
Users Payload
14.4 kbps
40 bits
0.4 kbps
12.8 kbps (36 units)
32 kbps
80 bits
0.4 kbps
56 kbps
70 bits
0.8 kbps
64 kbps
80 bits
0.8 kbps
128 kbps
160 bits
0.8 kbps
192 kbps
160 bits
0.8 kbps
256 kbps
160 bits
1.6 kbps
384 kbps
240 bits
1.6 kbps
512 kbps
160 bits
3.2 kbps
768 kbps
240 bits
3.2 kbps
Table B-58 provides detailed bandwidth allocation information for each supported
channel data rate, as a function of assigned bandwidth. Note that the supported
channel rates depend on the assigned bandwidth.
B-279
Table B-58. Bandwidth Allocations

Use
Allocation Units
Allocation Rule
Synchronization
Inband
management
Data
Channels
Channel
Rate
(kbps)
Composite Channel Rate (kbps)
14.4
2.4
4.8
7.2
8
9.6
14.4
16
19.2
24
28.8
32
38.4
48
56
57.6
64
Channel
end-to-end
control
signals
32
6
12
18
20
24
56, 64,
128, 192
6
12
18
20
24
36
40
48
60
72
3
6
9
10
12
18
20
24
30
36
40
48
60
70
72
80
256,
384
3
3
N/A
5
6
9
10
12
15
18
20
24
30
35
36
40
In accordance with channel data

rate.
512, 768
3
3
N/A
N/A
3
N/A
5
6
N/A
9
10
12
15
N/A
18
20
1 allocation unit for each pair of channels (1 allocation

unit can carry up to four control signals, e.g., two
signals for each channel)
Theoretical minimum is one

allocation unit per active
channel, however for low data
rate (i.e., for data rates lower
than the bandwidth allocation
unit), oversampling is used to
achieve an integer number of bit
samples: e.g., when the
bandwidth allocation unit is
3.2 kbps and the channel data
rate is 2.4 kbps, the effective
bandwidth being used is 3 times
higher, 9.6 kbps. 9.6 kbps
translate to 3 allocation units.
Therefore, the effect of
oversampling is to increase the
bandwidth used to transfer
low-rate channels.
64 kbps rate is available only for
uplink rates of 128 kbps and
higher
For each data channel that
requires end-to-end signaling
Numerical Example
The following two numerical examples illustrate how to use the above table
information to calculate the internal channel bandwidth required for various
operating configurations.
In the first example (see Table B-59), all six channels of an LS-6N module are
used, and are connected to the composite channel. In the second example (see
Table B-60), all 12 channels of an LS-12 module are used, and are connected to
one composite channel. In both cases, the Megaplex uplink bandwidth assigned
to the composite channel is 256 kbps (160 bits).
B-280
Table B-59. Bandwidth Allocations Example, LS-6N

Utilization
Allocation Units
4 data channels with 14.4 kbps per channel; these

channels (distributed among two channel pairs) require
36 units
2 units signaling
2 data channels with 32 kbps per channel, no end-to-end 40 units

signaling
Total user allocation
78 units
Frame synchronization and management channel
2 units
Total capacity used
80 units
Reserve capacity
80 units (128 kbps)
[composite channel assigned bandwidth of 256 kbps less [160 units - 80 units =
total capacity used]
80 units]
Table B-60. Bandwidth Allocations Example, LS-12

Utilization
Allocation Units
10 data channels with 14.4 kbps per channel; seven of

these channels (distributed among four channel pairs)
require end-to-end signaling
90 units
4 units signaling
2 data channels with 32 kbps per channel, no end-to-end

signaling
40 units
Total user allocation
134 units
Frame synchronization and management channel
2 units
Total capacity used
136 units
Reserve capacity
24 units (38.4 kbps)
Configuring External Ports

The following parameters can be configured for external (serial) ports of the
LS-6N/LS-12 modules:
Channel rate
Clock mode
Channel mode (sync/async)
CTS control
End-to-end-control.
When configuring the end-to-end control, both channels of a given pair must be
assigned to support the matching control signals.
When selecting the data channel timing reference, set the interface mode
DTE/DCE switches as follows:
B-281
DCE clock mode: the DTE/DCE switch is set to DCE
DTE or External DCE clock mode: the DTE/DCE switch is set to DTE.
The data rates are independently selectable for each channel, except that the
two channels of one pair must use rates from the same group:
Group 1: 2.4, 4.8, 9.6, 19.2, 38.4
Group 2: 7.2, 14.4, 28.8, 57.6
Group 3: 8.0, 16.0, 24.0, 32.0, 48.0, 56.0, 64.0
Group 3 rates can be selected only on channels using the synchronous protocol.
The following example illustrates how to configure the serial (external) ports 1
and 2 on the LS-12 module installed in slot 6:
Rate 14.4 kbps
Set the clock mode to external-dce
Set the CTS line to track the state of the local RTS line
Set the state of the local RTS and DTR lines to be reflected by the remote
DCD and DSR line, respectively
Leave all other parameters disabled or at their defaults (for example,

mode=sync).

mp4100>config>port>serial (6/1)#
no shutdown
rate 14.4
clock-mode external-dce
cts-rts
end-to-end-control rts-dtr
port serial 6/2 no shutdown
rate 14.4
clock-mode external-dce
cts-rts
end-to-end-control rts-dtr
Configuring Internal Ports

To configure the internal port (composite channel), you need to define its rate
and bind serial ports to it. This is done under configure>serial-bundle context.
Both channels of a given pair must be connected to the same internal composite
channel.
The following example illustrates how to configure the serial bundle (internal)
port 1 on the LS-12 module installed in slot 6:
B-282
Data rate 32 kbps.
Bind external serial ports 1 and 2 to be carried over this serial bundle port
mp4100>config# port serial-bundle 6/1

no shutdown
bind serial 1
bind serial 2
rate 32kbps
exit

The routing of the individual port timeslots on the serial-bundle ports (composite
streams) is configured via ds0 cross-connect. You can assign only timeslots of
ports that have already been configured, and are configured as no shutdown.

After an external (serial) port of LS-6N, LS-12 is configured and at no shutdown,
its receive clock can be selected as a timing reference for the Megaplex-4100
system.
In this case, the timing mode needs to be DTE (clock-mode=dte), and the channel
data rate must be a multiple of 8 kbps.
The list of tasks that can be performed on the LS-6N, LS-12 module and the
Task

service
Configure the external (serial) port

parameters
Reference
Features Supported by Megaplex-4100

Serial Ports
B-283
Task
Configure the serial-bundle ports

(binding the serial port to the
composite channel and specifying the
bandwidth allocated to the composite
channel)
configure>port>
serial-bundle
Reference
Note: you must also configure the CL.2 or uplink module port parameters (depending on the LS-6N/LS-12
module application). For the uplink module configuration procedure, refer to the appropriate section of this
Appendix.
reference
domain(1)
Configure DS0 cross-connect on serialbundle ports (timeslot assignment)
configure>cr>ds0
To find which ports on which modules

can be cross-connected with LS-6N,
LS-12 serial-bundle ports, see CrossConnect Table in Chapter 5
Configure split timeslot cross-connect

on serial-bundle ports (timeslot
assignment)

can be cross-connected with LS-6N,
LS-12 serial-bundle ports, see CrossConnect Table in Chapter 5
Example
The following section illustrates how to configure the LS-12 module installed in
slot 6 and cross-connect its serial ports with timeslot bits of the M8E1 module
installed in slot 1:
B-284
The rate of the serial-bundle port needs to be slightly higher than total
bandwidth of two serial ports. For this purpose, we selected 32 kbps from
the list of available rates
Then we must bind serial ports 1 and 2 to serial-bundle port 1
Now we must allocate four timeslot bits on the M8E1 port (32 kbps = 4 x 8
kbps), for this purpose we select bits 1,2,3,4 of timeslot 1 of E1 port 3
Cross-connect serial-bundle port 1 with bits 1,2,3,4 of timeslot 2 of E1 port 3

of M8E1 module installed in slot 1
slot 1 card-type e1-t1 m8e1

slot 6 card-type low-speed ls12
#------------ls12--------------------#
#------------external ports---------port serial 6/1 no shutdown
rate 14.4
exit
exit
port serial 6/2 no shutdown
rate 14.4
exit
exit
#------------internal ports--------port serial-bundle 6/1
no shutdown
bind serial 1
bind serial 2
rate 32kbps
exit
exit
cr split-ts
cr split-ts
cr split-ts
cr split-ts
commit
e1
e1
e1
e1
1/3
1/3
1/3
1/3
ts
ts
ts
ts
2
2
2
2
bits
bits
bits
bits
1
2
3
4
serial-bundle
serial-bundle
serial-bundle
serial-bundle
6/1
6/1
6/1
6/1

The LS-6N, LS-12 modules include powerful testing capabilities which help reduce
downtime to a minimum.
The test and loopback functions are available at two levels:
Composite data streams generated by the module (the data streams sent to
the uplink) on the module serial-bundle ports (see Serial-Bundle Ports in
Chapter 5).
Individual data channels on the module serial ports (see Serial Ports in
Chapter 5).
These functions are controlled by means of the Megaplex system management.

On each level the following loopback functions are available:
No performance monitoring and statistics are available on the serial and serialbundle ports.
Troubleshooting
The tests and loops available on the LS-6N, LS-12 modules provide a rapid and
efficient way to identify the general location of a fault either in the module or in
B-285
the external equipment serving the module channels. The following instructions
refer to local and remote units on the assumption that the system includes
one system management, which is connected to the local unit.
Use the following sequence of tests:
Step
Action
Interpretation of Results
Activate local composite data stream (serialbundle port) loops at both the remote and
local LS-6N, LS-12 modules
A fault indication at either side means that the

corresponding LS-6N, LS-12 module is faulty
Deactivate the local composite data stream

(serial-bundle port) loops
Not applicable
Activate a local channel loop on the side that

reports a channel problem
The equipment connected to the channel should

receive its own signal correctly. If not, the
problem is with the equipment and/or its
connections to the LS-6N/12 module
Deactivate the channel loop
Not applicable
B.15 VC-4, VC-4A, VC-8, VC-8A and VC-16 Modules

operation of the VC-4, VC-4A, VC-8, VC-8A and VC-16 voice interface modules for
use in the Megaplex-4100 Next Generation Multiservice Access Node, ver 3.0 and
higher. For use of the modules in the Megaplex-2100, Megaplex-2104, and
Megaplex-4100 ver 2.1 chassis, see their respective Installation and Operation
manuals.
The VC-16 module provides 16 voice channels using toll-quality 64 kbps PCM
voice encoding in compliance with ITU-T Rec. G.711 and AT&T Pub. 43801. The
VC-8 and VC-4 modules are similar, except that they provide 8 or 4 channels,
respectively.
The VC-8A and VC-4A modules provide 8, respectively 4, voice channels using one
of two user-selectable voice encoding modes:
Note
Toll-quality 64 kbps PCM voice encoding in compliance with ITU-T Rec. G.711
and AT&T Pub. 43801
Toll-quality 32 kbps ADPCM voice compression encoding in compliance with

ITU-T Rec. G.726 and G.727.
The VC-4A/8A module family, as opposed to the VC-4/8/16 family, has been
designed to provide mainly ADPCM services. If you need PCM services only, the
VC-4/8/16 family will fully satisfy your needs. However, in addition to their main
destination, the VC-4A/8A modules also support the PCM voice encoding.
The modules offer flexible configuration of all their operational parameters,
including automatic selection of the signaling information format in accordance
with the operation mode.
B-286
VC-4, VC-4A, VC-8, VC-8A and VC-16 Modules
Each voice channel of the VC modules supports Caller ID by transparently

transferring the FSK modem tones between the incoming rings. With this feature,
a customer subscribed to a Caller ID service can see the Caller ID of an incoming
or waiting call with any Caller ID display equipment.
The voice channels of the VC-4, VC-8 and VC-16 modules support SMS message
transfer between the telephones using DECT protocol.
In ADPCM encoding mode, each channel requires only half a timeslot. Therefore, a
single E1 link can carry up to 31 x 2=61 voice channels and a single T1 link can
carry up to 24 x 2=48 voice channels.
Product Options
The VC modules are available in the following versions:
Note
Note
E&M for operating with different types of E&M signaling: EIA RS-464 Types I,
II, III and V (British Telecom SSDC5). This version is typically used for
connection of tie lines between PBXs. Both 2-wire and 4-wire lines are
supported (user-selectable). A special E&M/POS version of VC-8 and VC-16
with positive signaling is available for use in those applications (for example,
radio transmitters) in which positive signaling voltage is required, enabling the
module signaling operation at +5V or +12V. A special E&M/EXT version can be
ordered for working with the standard E&M (48 VDC) voltage.
The E&M/POS version operates only with Type II Signaling.
FXS for direct connection to 2-wire telephones employing both loop-start

and wink-start signaling methods, with battery polarity reversal and pulse
metering.
FXO for connection to PBX extension lines employing both loop-start and
wink-start signaling, with battery polarity reversal and pulse metering.
In this section, the generic term VC is used when the information is applicable to
all the VC-4, VC-4A, VC-8, VC-8A and VC-16 module versions. The complete
designation is used only for information applicable to a specific version.
Applications
Basic VC-16/E&M Applications
Figure B-85 shows a basic E&M tie line application using VC-16/E&M modules.
In this application, one VC-16/E&M module is used to provide 16 E&M tie lines
between two analog PBXs through the SDH/SONET link interconnecting the
Megaplex systems.
B-287
Figure B-85. Basic Application for VC-16/E&M Modules
Off-Premises Extension (OPX) Applications

In a typical OPX application (see Figure B-86), one FXO module located at the PBX
side is used in a link with an FXS module to provide up to 16 off-premises
extensions for an analog PBX connected to the FXO module channels.
Figure B-86. OPX Application for FXO and FXS Modules

The system configuration shown in Figure B-86 permits using telephones
connected to the channels of an FXS module installed in the Megaplex unit
located at the other end of the link as extensions of an analog PBX. Each remote
telephone then becomes a regular local PBX subscriber, which can be dialed by
other subscribers using standard procedures, and can also dial any other PBX
subscriber and use all the services available to local PBX subscribers.
Automatic Ringdown (PLAR) Applications

Another application, which requires only FXS modules, is the private line with
automatic ringdown (PLAR), also called hot line.
In a PLAR or hot line application, telephone sets are connected to the channels
of FXS modules installed in two different Megaplex units that are connected by
an E1 or T1 link, as shown in Figure B-87. For AC-powered Megaplex units, the
subscriber feed voltage can be provided by Ringer-2100R modules installed in
each Megaplex.
Figure B-87. PLAR Application for FXS Modules

Each pair of telephones (local and remote) can then communicate directly
without dialing: when one telephone goes off-hook, the other telephone rings.
B-288
PSTN Access Applications

Due to the flexible signaling configuration capabilities, the FXO modules can also
be used on links ending in the public switched telephone network (PSTN). A
typical PSTN access application is shown in Figure B-88.
Figure B-88. PSTN Application for FXO Modules

In the application shown in Figure B-88, the extension lines of an analog PBX are
connected to the channels of an FXO module, installed in a Megaplex unit
connected to the PSTN through an E1/T1 or STM-1/OC-3/STM-4/OC-12 trunk line.
This enables the PBX subscribers to dial PSTN subscribers through the Megaplex
link, and PSTN subscribers can dial to PBX subscribers.
Direct Inward Dialing (DID) Applications

FXS and FXO modules support battery voltage polarity reversal for wink-start
signaling, which is used in direct inward dialing (DID) applications.
With DID, a PSTN subscriber first dials the number of one of the PBX external
(trunk) lines, and after getting the PBX dial tone, can continue dialing the number
of desired particular PBX extension, without requiring the assistance of the PBX
operator.
Figure B-89 shows a typical DID application.
Figure B-89. Wink-Start Trunk Extension for DID Application using FXO and FXS Modules
As shown in Figure B-89, the analog PBX trunk lines are connected to the PSTN
through a Megaplex link. The FXO module channels connect to the PBX
extensions, and the central office (PSTN switch) lines that use wink-start
signaling are connected to the corresponding FXS module channels.
B-289
Payphone Applications
Payphone applications use 12 kHz or 16 kHz pulses for metering line utilization.
The FXO module supports the detection of 12 or 16 kHz metering pulses at the
central office or PBX side, and the FXS module supports the generation of 12 or
16 kHz metering pulses, for direct connection to public payphones.
Therefore, a Megaplex link can be used to connect payphones to a central office
or PBX, as shown in Figure B-90.
Figure B-90. Payphone Application using FXO and FXS Modules

In the typical payphone application shown in Figure B-90, an FXO module is
installed at the PBX or central office side, and the public payphones are
connected to an FXS module installed in the off-premises Megaplex.
The remote payphone then becomes a regular local PBX subscriber, which can be
dialed by other subscribers using standard procedures, and can also dial any
other PBX subscriber, while transferring the metering signaling for billing
purposes.
Broadcast Applications
In addition to the normal (bidirectional) mode of operation, the VC modules
support the unidirectional broadcast mode. For a description of this mode, refer
to Unidirectional Broadcast Function under Cross-Connections in Chapter 5.
Features
E&M Modules
E&M modules are supplied in several panel versions, as described below in
Physical Description.
The E&M modules have user-selectable 2-wire or 4-wire analog interfaces using
E&M signaling. The interface type (2-wire or 4-wire) can be independently
selected for each pair of channels (1, 2; 3, 4; etc.). A special 4-wire version with
enhanced gain control is available for any E&M module.
The E&M modules support four types of E&M signaling: EIA RS-464 types I, II, III
and V (similar to British Telecom SSDC5). Figure B-91 shows the equivalent
signaling circuits for the different signaling modes.
B-290

E&M
Interface
PBX
Condition
-48VDC
M Lead
On-Hook
Off-Hook
GND
- 48VDC
Open
GND
E Lead
- 48VDC
A. RS-464 Type I
E&M
Interface
PBX
Condition
M Lead
On-Hook
Off-Hook
SB Lead
M/SB
E/SG
Open
- 48VDC
Open
GND
M/SB
E/SG
Open
- 48VDC
Open
GND
- 48VDC
E Lead
- 48VDC
SG Lead
B. RS-464 Type II
E&M
Interface
PBX
Condition
M Lead
On-Hook
Off-Hook
SB Lead
- 48VDC
E Lead
- 48VDC
SG Lead
C. RS-464 Type III

E& M
Interface
PBX
Condition
1.2 k
M Lead
- 48VDC
Open
GND
Open
GND
1.2 k
E Lead
- 48VDC
On-Hook
Off-Hook
D. RS-464 Type V, SSDC5

E& M
Interface
PBX
Condition
M Lead
+5 VDC
+12 VDC
+12 VDC
On-Hook
Off-Hook
SG
Open
GND
Open
GND
SG Lead
LEGEND
E. E&M/POS Version (Type II only)
= Signaling Detector Circuit
Figure B-91. E&M Equivalent Signaling Circuits

The signaling type can be independently selected for each group of four channels
(1, 2, 3, 4; 5, 6, 7, 8; etc.).
B-291
EIA RS-464 Type I signaling standard is supported without any external power
supply.
EIA RS-464 Type II, III and V (BT SSDC5) signaling standards are supported by
means of the internal -12 VDC power supply of the chassis. The -12 VDC
voltage is suitable for most PBX systems. However, for full support of the EIA
RS-464 Type II, III and V (BT SSDC5) signaling standards, a -48 VDC signaling
voltage is required. For this purpose, a special E&M/EXT version can be
ordered from RAD.
The required -48 VDC voltage is always available when the Megaplex chassis is
powered from a -48 VDC source. An AC-powered Megaplex-4100 chassis can
be either equipped with a Ringer-2100R module or connected to an external
ringer unit, for example, the Ringer-2000 or Ringer-2200N units offered by
RAD (see the appropriate Ringer Installation and Operation Manual for
details).
Note
See Connecting the Signaling and Feed Voltage Source in Chapter 2 for details on
DC power sources and connection methods.
A special E&M/POS version of VC-8 and VC-16 with positive signaling enables
the module signaling operation at +5V or +12V (see Figure B-91E). In this
mode, the VC module sends signaling to the PBX by connecting GND to the
SG pin. The E pin is permanently connected to GND and is not used. This
version operates only with Type II Signaling.
FXS and FXO Modules

The FXS and FXO modules are used to connect regular telephone sets (and other
equipment with similar interface properties) to central office (PSTN) and PBX
extension lines.
FXS and FXO modules are intended for operation in a link, with the FXS module at
the subscriber side and the FXO module at the central office or PBX side.
However, FXS modules can also operate in a link with E&M modules.
FXS Module Characteristics

FXS modules are supplied in several panel versions, as described below in Physical
Description.
The FXS modules have 2-wire analog interfaces and support FXS loop-start
signaling, for direct connection to subscriber telephone sets.
The FXS modules also support wink-start signaling. For VC-4 and VC-8 modules,
the selection is made for the entire group of the module channels. For VC-16/FXS
modules, the signaling mode (loop-start or wink-start) can be independently
selected for each group of eight channels (1 to 8 and 9 to 16).
To enable wink-start signaling, the FXS modules support feed voltage (battery)
polarity reversal.
For direct connection to payphones, the FXS modules also support metering pulse
generation. The user can select the metering pulses frequency (12 kHz or
16 kHz).
B-292
The FXS modules require -48 VDC to supply the subscriber feed and ring voltages.
The ring voltage is generated on the module itself, by an internal ringer.
The required voltage can be supplied via the internal supply voltage connector of
the module, from the chassis voltage distribution bus (see Connecting the
Signaling and Feed Voltage Source in Chapter 2 for details).
In addition to -48 VDC, the VC-4/FXS and VC-8/FXS/RJ modules can also operate
with -24 VDC. The VC-8/FXS and VC-16/FXS modules have a special ordering
option for -24 VDC operation.
Note
FXS modules can supply the subscriber feed voltage from any DC input voltage in
the range of -20 to -56 VDC. However, feed voltages lower than the nominal
-48 VDC will reduce the loop span. For example, for -24 VDC feed voltage, the
maximum loop span over typical local plant pairs is 1 km.
FXO Module Characteristics

FXS modules are supplied in several panel versions, as described below in Physical
Description.
The FXO modules have 2-wire analog interfaces and support FXO loop-start
signaling for direct connection to central office and PBX extension lines.
The FXO modules also support wink-start signaling. For VC-16/FXO modules, the
signaling mode (loop-start or wink-start) can be independently selected for each
group of eight channels (1 to 8 and 9 to 16).
To enable wink-start signaling, the FXO module supports the detection of feed
voltage (battery) polarity reversal.
To permit connection to payphones, the FXO modules also support metering
pulse detection. The user can select the metering pulse detection frequency
(12 kHz or 16 kHz).
The FXO modules do not require any external supply voltage.
System Capacity
The maximum capacity of transmitting VC channels in a chassis depends on the
following parameters:
The number and type of modules with E1/E1-i/T1/T1-i/DS1 ports installed in

the chassis
The number of free I/O slots for VC modules to be installed and the type of
VC modules
Operating mode (PCM or ADPCM).
The maximum MP-4100 chassis capacity is equivalent to 126 E1-i (over SDH) or
168 T1-i (over SONET) trunks.
B-293
TDM Mapping
payload routing in the VC modules, independently configurable for each port, at
the individual timeslots (DS0) level.
Management
All the module operational parameters are controlled by means of the Megaplex
system management.
The VC modules occupy one module slot in the Megaplex-4100 chassis.
The module panels are described below.
VC-16 Front Panels

Figure B-92 shows typical panels of VC-16 modules.
VC-16
E&M
Voice Channels
9 to 16
Connector
VC-16
FXO
VC-16
FXS
CH
9-16
Voice Channel
Connector
(for all channels)
Voice Channel
Connector
(for all channels)
CH
1-8
Voice Channels
1 to 8
Connector
VC-16/E&M
VC-16/FXS
VC-16/FXO
Figure B-92. VC-16 Module Panels

The VC-16 module panels have voice channel connectors only, and no indicators.
The VC-16/E&M modules have two 68-pin female SCSI connectors, one for voice
channels 1 to 8 and the other for voice channels 9 to 16.
VC-16/FXS and VC-16/FXO modules have one 50-pin female Telco connector, for
connection of all the voice channels.
B-294
VC-8 and VC-8A Front Panels

Figure B-93 shows typical panels of VC-8 modules.
VC-8
E&M
VC-8
FXS
VC-8/RJ
FXS
VC-8
FXO
VC-8/RJ
FXO
LOC
RING
CH-1
CH-1
REM
REM
LOC
RING
CH-2
CH-2
REM
REM
LOC
RING
CH-3
CH-3
REM
REM
LOC
RING
CH-4
CH-4
REM
CH
1-8
VC-8/E&M
LOC
Voice
Channel
Connector
(for all
channels)
Voice
Channel
Connector
(for all
channels)
REM
RING
CH-5
CH-5
REM
REM
LOC
RING
CH-6
CH-6
REM
REM
LOC
RING
CH-7
CH-7
REM
REM
LOC
RING
CH-8
CH-8
REM
VC-8/FXS
REM
VC-8/RJ/FXS
VC-8/FXO
VC-8/RJ/FXO

Figure B-93 shows typical panels of VC-8A modules.
VC-8A
E&M
VC-8A
FXS
LOC
VC-8A
FXO
RING
CH-1
REM
CH-1
REM
LOC
RING
CH-2
REM
CH-2
REM
LOC
RING
CH-3
REM
CH-3
REM
LOC
RING
CH-4
REM
CH-4
REM
LOC
RING
CH-5
CH
1-8
Voice
Channel
Connector
(for all
channels)
VC-8A/E&M
CH-5
REM
REM
LOC
RING
CH-6
CH-6
REM
REM
LOC
RING
CH-7
CH-7
REM
REM
LOC
RING
CH-8
REM
VC-8A/FXS
CH-8
REM
VC-8A/FXO
Figure B-94. VC-8A Module Panels

The VC-8/E&M and VC-8A/E&M module interfaces have one 68-pin female SCSI
connector.
B-295
The VC-8 FXS and FXO modules have two modifications with different type of
connectors: VC-8 and VC-8/RJ.
In VC-8 modules, all the module channels are terminated in a 50-pin female Telco
connector. The VC-8/RJ module interface and the VC-8A module interfaces are
terminated in eight RJ-12 connectors one per channel.
VC-4 and VC-4A Front Panels

Figure B-95 and Figure B-96 show typical panels of VC-4 and VC-4A modules,
respectively.
The 4-channel E&M module interface is terminated in four RJ-45 connectors
one per channel.
The 4-channel FXS and FXO module interfaces are terminated in four RJ-12
connectors one per channel.
VC-4
E&M
VC-4
FXS
LOC
VC-4
FXO
RING
CH1
CH1
M
REM
LOC
CH1
REM
RING
CH2
CH2
CH2
REM
REM
LOC
RING
CH3
CH3
M
E
REM
RING
CH4
CH4
M
VC-4/E&M
CH3
REM
LOC
REM
VC-4/FXS
CH4
REM
VC-4/FXO
B-296
VC-4A
E&M
VC-4A
FXO
VC-4A
FXS
LOC
RING
CH1
CH1
M
REM
LOC
CH1
REM
RING
CH2
CH2
CH2
REM
REM
LOC
RING
CH3
CH3
M
E
CH3
REM
REM
LOC
RING
CH4
CH4
CH4
REM
VC-4A/E&M
VC-4A/FXS
REM
VC-4A/FXO
Figure B-96. VC-4A Module Panels
LED Indicators
VC-16 modules do not have LED indicators. All VC modules with RJ connectors
have separate LED indicators for each channel listed in the tables below.
Table B-61. E&M Channel Indicators

Name
Description
On when the M line of the corresponding channel is off-hook

(channel in use).
On when the E line of the corresponding channel is off-hook

(channel in use).
Table B-62. FXS Channel Indicators

Name
Description
REM
On when a call initiated by the remote subscriber is being handled by

the corresponding channel (channel is busy).
LOC
On when the local subscriber of the corresponding channel is

off-hook (busy).
Table B-63. FXO Channel Indicators

Name
Description
REM
On when the remote subscriber of the corresponding channel is

off-hook (busy).
RING
On when ringing is received on the corresponding channel.
B-297
Number of
Channels
Voice Processing
VC-4, VC-4A
VC-8, VC-8A
VC-16
16
Modulation Technique
PCM: per ITU-T Rec. G.711 and AT&T Pub. 43801

ADPCM: per ITU-T G.726 and G.727
Bandwidth
Requirements
Echo Cancellation
4 ms per channel as per G.168
Companding
-law or A-law (user-selectable)
PCM
64 kbps per enabled channel (one timeslot)
ADPCM
32 kbps per enabled channel (one timeslot per

pair of channels) as per G.726
24 kbps per enabled channel (one timeslot per
pair of channels) as per G.727
Analog Interface
Interface Type
E&M
4-wire or 2-wire (user-selectable)
Note: A special 4-wire version with enhanced gain control (see

Table B-64) is available.
FXS, FXO
Analog Parameters
B-298
2-wire
Compliance
ITU-T Rec. G.712
Nominal Level
0 dBm
Nominal Impedance
600
Return Loss (ERL) at

300 to 3400 Hz
Better than 20 dB
Frequency Response
(Ref: 1020 Hz)
0 dB 0.5 dB, at 300 to 3000 Hz

0 dB 1.1 dB, at 250 to 3400 Hz
Transmit and Receive

Levels
User-selectable in 0.5 dB 0.15 dB steps, see

Table B-64.
Signal to Total
Distortion Using ITU-T
Rec. G.712 (8-bit PCM
encoding)
-30 to 0 dBm0:
better than 33 dB
-45 to +3 dBm0:
better than 22 dB
Idle Channel Noise
Better than -65 dBm0 (+20 dBrnc)
Transformer Isolation
1500 VRMS
Table B-64. Transmit and Receive Levels for Various Interfaces

Module Interface
Transmit
[dbm]
min
Receive
[dbm]
max
min
max
E&M regular
-10
+5
-17
+2
E&M 4W enhanced
-17
+5
-17
+9
FXS
-5
+5
-17
+1
FXO
-3.5
+5
-17
+1
E&M Interface
Characteristics
Signaling Method
(User-Selectable)
EIA RS-464 Type I

SSDC5) using internal -12 VDC in place of -48
VDC
Note: For full support of Types II, III, and V (SSDC5)
signaling standards, a -48 VDC supply is required.
FXS Interface
Characteristics
Dial Pulse Distortion
2 ms max
Signaling Modes
EIA RS-464 loop-start and wink-start,

user-selectable
On-Hook/Off-Hook
Threshold
(VIN = -20 to -54 VDC)
Off-hook state: 3V to 80% Vin between tip and

ring
On-hook state: more than 83% Vin between
tip and ring
Feed Current
24 mA (10%)
Ringer Characteristics
54 VRMS with up to 1 REN load

45 VRMS with up to 5 REN load
Protected against overload
22 Hz (10%)
1 second ON, 3 seconds OFF
Metering Pulse
Generation (PCM only)
12 kHz or 16 kHz (2 Hz), user-selectable

1.7 VRMS
B-299
FXO Interface
Characteristics
Reversal Polarity Pulse

Distortion
6 ms max
Signaling Modes
EIA RS-464 loop-start and wink-start,

user-selectable
DC Resistance
Off-hook: 100 at 100 mA feed, 230 at

25 mA feed.
On-hook: more than 1 M
Ring Detector
20 k for 70 VRMS, 20 Hz ring signal
Detection Thresholds
End-to-End
Detection: > 20 VRMS, 17 to 25Hz

No detection: < 5 VRMS
Metering Pulse
Detection Frequency
(PCM only)
12 kHz or 16 kHz (200 Hz), user-selectable
Reversal Polarity Pulse

Distortion
6 ms max
T1 Uplinks
User-selectable sampling rate:
Signaling
667 samples per second with SF (D4) framing

333 samples per second with ESF framing
E1 Uplinks
User-selectable as per ITU-T Rec. G.704, para.

3.3.32
Diagnostics

Forward tone injection (1 kHz, 0 dBm0)
Backward tone injection (1 kHz, 0 dBm0)
Connectors
E&M Modules
VC-4, VC-4A: RJ-45 connector for each channel

VC-8, VC-8A: 68-pin female SCSI connector for
all channels
VC-16: two 68-pin female SCSI connectors, one
for channels 1 to 8 and the other for channels
9 to 16
FXO and FXS Modules
VC-4, VC-4A, VC-8A, VC-8/RJ: RJ-12 connector

for each channel
VC-8, VC-16: One 50-pin female Telco
connector for all channels
Indicators
B-300
E&M Ports
E-lead, M-lead indicators per channel
Environment
FXS Ports
Remote call and local off-hook indicators per

channel
FXO Ports
Ring and remote off-hook indicators per channel
-10C to 55C (14F to 131F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
See Table B-65
Power
Consumption
Configuration
Table B-65. Power Consumption (in Watt) from Megaplex Power Supply
(without -48 VDC)
Module vs Interface Type
FXS
FXO
E&M
VC-4
2.5
1.9
2.8
VC-4A
3.3
2.7
3.6
VC-8
2.8
2.0
3.4
VC-8A
3.7
2.8
4.2
VC-16
4.7
2.5
5.2
Warning
Caution

The VC modules contain components sensitive to electrostatic discharge (ESD). To
B-301

VC modules may be installed in an operating chassis (hot insertion).
A VC module starts operating as soon as it is inserted in an operating chassis.
Warning
To install a VC module:

E&M Modules
The VC-4/E&M and VC-4A/E&M module interfaces have four RJ-45 connectors.
Table B-66 lists the wiring of the RJ-45 connectors used for the VC-4/E&M and
VC-4A/E&M modules.
Table B-66. RJ-45 Connector Wiring

Pin
Designation
Function
SB
Signaling battery
M lead input
R1-OUT
Voice output (4W)

Voice input/output (2W)
R-IN
Voice input (4W)
T-IN
Voice input (4W)
T1-OUT
Voice output (4W)

B-302
SG
Function depends on signaling mode:
RS-464 Type I, III: Direct connection to signal ground
RS-464 Type V, SSDC5: Connection to signal ground

through 1.2 k resistor
RS-464 Type II: SG lead
Pin
Designation
Function
E lead output
Each group of VC-8/VC-8A/VC-16 eight channels is terminated in a 68-pin female

SCSI connector located on the module panel. RAD offers a 2-meter adapter cable,
CBL-KVF8/E&M, terminated in eight RJ-45 male connectors, for direct connection
of the individual channels to the user equipment. Figure B-97 shows a general
view of the CBL-KVF8/E&M cable, and Table B-67 lists the cable wiring, together
with functions of the individual connector pins.
Figure B-97. CBL-KVF8/E&M

Table B-67. CBL-KVF8/E&M Cable Wiring and Connector Pin Functions
Channel
68-Pin SCSI
Designation
Function
RJ-45 Connector
37
SB
Signaling Battery
38
M Lead Input
R-IN
Voice Input (4-wire)
T-IN
R1-OUT
Voice Output (4-wire)

Voice Input/Output (2-wire)
T1-OUT

35
SG
Signaling Ground
36
E Lead Output
43
SB
Signaling Battery
44
M Lead Input
R-IN
T-IN
R1-OUT

Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
B-303

Channel
68-Pin SCSI
Designation
Function
RJ-45 Connector
10
T1-OUT

41
SG
Signaling Ground
42
E Lead Output
49
SB
Signaling Battery
50
M Lead Input
13
R-IN
14
T-IN
15
R1-OUT

16
T1-OUT

47
SG
Signaling Ground
48
E Lead Output
55
SB
Signaling Battery
56
M Lead Input
19
R-IN
20
T-IN
21
R1-OUT

22
T1-OUT

53
SG
Signaling Ground
54
E Lead Output
61
SB
Signaling Battery
62
M Lead Input
25
R-IN
26
T-IN
R1-OUT

T1-OUT

59
SG
Signaling Ground
60
E Lead Output
67
SB
Signaling Battery
27
28
B-304
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair

Channel
68-Pin SCSI
Designation
Function
RJ-45 Connector
68
M Lead Input
31
R-IN
32
T-IN
33
R1-OUT

34
T1-OUT

65
SG
Signaling Ground
66
E Lead Output
45
SB
Signaling Battery
46
M Lead Input
R-IN
T-IN
11
R1-OUT

12
T1-OUT

39
SG
Signaling Ground
40
E Lead Output
57
SB
Signaling Battery
58
M Lead Input
17
R-IN
18
T-IN
23
R1-OUT

24
T1-OUT

51
SG
Signaling Ground
52
E Lead Output
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
RAD also offers an open-end splitter cable, CBL-KVF8/E&M/OPEN/12M , for

connecting the SCSI-68 connector to the E&M user equipment. This cable
includes one male SCSI-68 and one open-ended connectors. The cable is 12m
(39.3 ft) long. See its drawing and pinout in the figure and table below.
B-305
Figure B-98. CBL-HSU12/OPEN/12M Cable

Table B-68. CBL-KVF8/E&M/OPEN/12M Pinout
Open-Ended Connector Pin
B-306
SCSI-68
Connector Pin
Blue
Signaling M Lead Input
38
White
Voice Rx Input
Orange
Voice Rx Input
White
Voice Tx Output
Green
Voice Tx Output
Brown
Signaling E Lead Output
36
Gray
44
White
Voice Rx Input
White/Blue
Voice Rx Input
White
Voice Tx Output
Orange/Blue
Voice Tx Output
10
Green/Blue
42
Brown/Blue
50
White
Voice Rx Input
13
Gray/Blue
Voice Rx Input
14
White
Voice Tx Output
15
White/Orange
Voice Tx Output
16
Orange/Green
48
Orange/Brown
56
White
Voice Rx Input
19
Gray/ Orange
Voice Rx Input
20
White
Voice Tx Output
21
White/Green
Voice Tx Output
22
Green/Brown
54
Notes
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Open-Ended Connector Pin
SCSI-68
Connector Pin
Gray/Green
62
White
Voice Rx Input
25
White/Brown
Voice Rx Input
26
White
Voice Tx Output
27
Gray/Brown
Voice Tx Output
28
White/Gray
60
Blue
68
Yellow
Voice Rx Input
31
Orange
Voice Rx Input
32
Yellow
Voice Tx Output
33
Green
Voice Tx Output
34
Brown
66
Gray
46
Yellow
Voice Rx Input
White/Blue
Voice Rx Input
Yellow
Voice Tx Output
11
Orange/Blue
Voice Tx Output
12
Green/Blue
40
Brown/Blue
58
Yellow
Voice Rx Input
17
Gray/Blue
Voice Rx Input
18
Yellow
Voice Tx Output
23
White/Orange
Voice Tx Output
24
Orange/Green
52
Drain Wire
Notes
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Twisted
Shell
FXS and FXO Modules

The FXS and FXO versions of VC-8 have two modifications with different types of
connectors: VC-8 and VC-8/RJ.
The VC-4, VC-4A, VC-8A and VC-8/RJ module interface is terminated in four or
eight RJ-12 connectors one per channel.
In the VC-16 and VC-8 modules, all module channels are terminated in a 50-pin
female TELCO connector.
RAD offers two adapter cables terminated in RJ-12 male connectors, for direct
connection of the individual channels to user equipment:
CBL-VC16/FXSO, intended for use with VC-16/FXS and VC-16/FXO modules,

which is terminated in 16 RJ-12 male connectors
B-307
CBL-VC8/FXSO, intended for use with VC-8/FXS and VC-8/FXO modules, which
is terminated in 8 RJ-12 male connectors.
Table B-69 lists the wiring of the RJ-12 connectors used for the FXO and FXS
modules.

Pin
Function
1, 2
Not connected
Ring
Tip
5, 6
Not connected
Figure B-99 shows a general view of CBL-VC16/FXSO. CBL-VC8/FXSO is similar,

except that it has only 8 RJ-12 connectors.
Table B-70 lists the wiring of the CBL-VC16/FXSO cable, together with the
functions of the VC-16 module connector. For VC-8 modules and CBL-VC8/FXSO
cables, only the pins assigned to channels 1 to 8 are connected.
Figure B-99. CBL-VC16/FXSO, General View
B-308
Table B-70. CBL-VC16/FXSO Cable Wiring and Connector Pin Functions

Channel
50-Pin TELCO
Function
RJ-12 Pin
12
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
Ring
Tip
13
9
10
6
7
49
50
46
47
24
25
3
4
26
27
29
30
10
21
22
11
18
19
12
15
16
13
43
44
14
40
41
15
37
38
16
34
35
Twisted Pair
Twisted Pair
Twisted Pair
}
}
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
Twisted Pair
B-309
In harsh environments, such as heavy industry or electrical switching stations, it is

recommended to use ferrite cores in order to reduce the effect of
electromagnetic interference.
The recommended ferrite core depends on the connector cable type.
For modules with RJ-12 connectors for each channel (VC-4, VC-4A, VC-8A,
VC-8/RJ), use FAIR RITE catalog number 0443167251 or equivalent for
small-diameter cables. The ferrite core must be installed on the cable close to
the RJ-12 connector as shown below:
For modules with a single 50-pin female Telco connector for all channels
(VC-8, VC-16) use FAIR RITE catalog number 0444173551 or equivalent. The
ferrite core must be installed on the main cable as shown below:
Connecting the Cables to Module Connector

Identify the cables intended for connection to each module connector.
To install the ferrite core on FXS/FXO modules:

1. Run the cable through the open core.
2. If cable thickness allows, wrap it around the core and run it through again.
Allow no more than 2 inches (5 cm) between the core and the cable
connector to the unit.
3. Snap the core shut.
Connect the cables into the appropriate connectors.
B-310
Caution When using a CBL-KVF8/E&M, CBL-VC16/FXSO or CBL-VC8/FXSO cable, take care

not to touch the exposed contacts of RJ-45 or RJ-12 connectors.
When using any of the adapter cables listed above, plug each channel connector
at the other end of the cable into the prescribed user equipment connector, in
Connecting the Signaling and Feed Voltage Source

The subscriber feed voltage used by FXS modules, or the -48 VDC signaling
battery voltage used by E&M/EXT modules for full compliance with the EIA RS-464
Type II, III and V (BT SSDC5) signaling standards is supplied to the VC module from
the chassis DC power distribution bus.
powered from a -48 VDC source. An AC-powered Megaplex-2100 or
Megaplex-4100 chassis can be either equipped with a Ringer-2100R module or
connected to an external ringer unit, for example, the Ringer-2000 or
Ringer-2200N units offered by RAD (see the appropriate Ringer Installation and
Operation Manual for details).
The Ringer-2100R module supports up to 40 concurrently active VC channels.
Ringer-2200N can support up to 200 active channels; when the maximum number
of active channels does not exceed 100, the Ringer-2000 can also be used.
Caution
Since an external voltage source can supply voltage even when the Megaplex is
Always turn off the external source (for example, Ringer-2000), before the
Megaplex chassis is turned off.
Never connect external DC voltages to modules installed in a Megaplex chassis
if it is not operating.
Do not connect/disconnect the ringer while it is operating.
For connection instructions, refer to the Installation and Operation Manual of the
appropriate Ringer.
Normal Indications
The module starts operating as soon as it is plugged into an operating Megaplex
enclosure. During normal operation, the two indicators of each channel indicate
the channel activity:
For E&M channels, the E and M indicators indicate the activity on the
signaling leads of the corresponding channel
For FXO channels, the RING indicator lights when ringing is received from the
local switch or PBX on the corresponding channel, and the REM indicator
lights when the remote subscriber is in the off-hook state
For FXS channels, the REM indicator lights when a call initiated by the
subscriber connected to the remote side is being handled by the
B-311
corresponding channel, and the LOC indicator lights when the local subscriber
is in the off-hook state.
General Module Parameters
Each VC port can be independently configured in accordance with the system
requirements. However, some configurable parameters pertain to the entire VC
module and/or to groups of ports.
The following parameters must be set to the same value for all the module ports:
meter-rate (FXS/FXO modules)
encoding
signaling
compression (VC-4A/VC-8A).
The following parameters must be set to the same value for a group of ports:
analog-signaling (FXS/FXO modules, for each group of 8 ports)
signaling-feedback (FXO modules, for each group of 8 ports)
e-m-type (for each group of four channels 1, 2, 3, 4; 5, 6, 7, 8; etc)
wires (E&M modules, for each pair of channels (1, 2; 3, 4; etc.)
This is done by forcing the last choice to all the module/group ports.
Selection of Transmit and Receive Levels

Transmit Level (tx-gain) selects the nominal input level of the transmit path. The
input level can be set in 0.5 dB steps in the range defined by Table B-64.
Select the transmit level to match the transmission level point (TLP-transmit) of
the equipment connected to the channel. Figure B-100 explains how to
determine the required level setting.
Note that the application of an input signal at the nominal transmit level results
in a 0 dBm digital level, and a far-end output signal equal to the far-end nominal
receive level.
Receive Level (rx-sensitivity) selects the nominal output level of the receive path.
The output level can be set in 0.5 dB steps in the range defined by Table B-64.
Select the receive level to match the TLP-receive of the equipment connected to
the channel (see Figure B-100).
B-312
VC Channel
Transmit TLP:
-8dB
T
Transmit
Input Circuit
Nominal Level
= 0 dBm
Adjust level (Tx Gain) to -8dBm
Receive TLP:
-2dB
T1
R1
Signal
Processor
Receive
Output Circuit
Adjust level (Rx Sensitivity) to -2dBm
Figure B-100. Selection of Transmit and Receive Levels

DS1 and PW ports of the MPW-1 module
The VC-4/8/16 modules use 64 kbps PCM encoding, and therefore require one
uplink timeslot per voice channel. The user can freely route each voice channel to
any uplink port. The voice channel data is provided in DS-0 (8 bits) compatible
format, permitting voice channel routing by DACS cross-connect systems.
The VC-4A/8A modules require one aggregate timeslot per voice channel in PCM
mode, or one timeslot per pair of voice channels in ADPCM mode. The main link
bandwidth required by a module depends on the encoding method, PCM or
ADPCM:
With PCM encoding, the modules require one main link timeslot, per voice
channel, and provide the data in a DS-0 (8-bits) compatible format,
permitting voice channel switching in a DACs-based cross-connect system.
When working with PCM encoding, use ds0 command.
With ADPCM encoding, the module requires only one main link timeslot for
each pair of voice channels. Note that consecutive channels (e.g. CH 12,
34, 15-16) must be assigned to share the same timeslot). When working
with ADPCM encoding, use split-ts command.
OOS Signaling
When choosing the OOS signaling option in the modules with E1/E1-i/T1/T1-i/DS1
ports working in one chassis with VC modules (see E1 Ports, T1 Ports or DS1
Ports in Chapter 5 for description), take into account the following:
types.
B-313
force-busy and idle-busy options are suitable for use with E&M and FXO
Handling of Signaling Information

The VC modules automatically adapt the generation and interpretation of the
signaling information to their analog interface type (E&M, FXS or FXO) and to the
signaling mode selected by the user (loop-start or wink-start).
When working with M8E1, M8T1 or M8SL modules, the VC modules also permit
flexible configuration of the signaling mode. The signaling format, down to the
level of the individual bits in the channel signaling information word, can be
modified by defining signaling profiles and then selecting a particular profile per
link or per timeslot on the E1/T1/E1-i port serving the VC module.
The following sections describe the handling of the signaling information in
Megaplex-4100.
Signaling Methods
You can select the format of the signaling information generated by VC modules
in accordance with the application requirements.
The signaling information of each channel is carried by means of up to four bits
(signaling bits), designated by the applicable standards as bits A, B, C, and D. The
number of bits actually available for carrying signaling information, and the data
rate at which signaling information can be transferred, depend on the main link
type (E1 or T1), the framing mode and the encoding type (PCM or ADPCM) being
used:
B-314
For E1 trunks with G.732N framing, no signaling information is transmitted.
For E1 trunks with G.732S framing, which use a 16-frame multiframe

structure, the standard signaling method is Channel Associated Signaling
(CAS). In the PCM mode, timeslot 16 carries four signaling bits for each
payload timeslot. In ADPCM mode two signaling bits are available for each
channel.
For T1 trunks with ESF framing, which use a 24-frame multiframe structure,
the standard signaling method is inband Robbed Bit Multiframe (RBMF)
signaling. The ESF multiframe structure includes four signaling bits for each
payload timeslot. When this method is used, the least significant bit of each
channel is periodically overwritten with signaling information. In ADPCM mode
two signaling bits are available for each channel.
T1 trunks with SF (D4) framing, which use a 12-frame multiframe structure,

also use the RBMF signaling method. Because of the shorter multiframe
structure, in this case only two signaling bits (A and B) are available for each
payload timeslot. In ADPCM mode only one signaling bit is available for each
channel.
RAD Proprietary Robbed Bit Frame (RBF) signaling, applicable for both E1
and T1 trunks, avoids the need for multiframe synchronization. This method
allocates the least significant bit of each channel to its own signaling
information. Therefore, signaling is transparently transferred within the
timeslot carrying the encoded audio signal, but because PCM encoding is
effectively done with 7-bit resolution, there is a slight decrease in
transmission quality. This proprietary method allows the transmission of 31

voice channels by a Megaplex system with E1 links, when using G.732N
framing.
For applications which do not require end-to-end signaling, or can use only
inband signaling (e.g., DTMF), the user can disable the transfer of signaling
information.
For your convenience, Table B-71 lists the number of signaling bits as a function
of voice encoding and framing method.
Table B-71. Number of Available Signaling Bits

Voice
M8E1
Signaling Type
Encoding
PCM
ADPCM
G.732S
M8T1
G.732N
ESF
SF (D4)
CAS
Not supported
Not supported
Not supported
Robbed Bit Multiframe

(RBMF)
Not supported
Not supported
Robbed Bit Frame (RBF)
CAS
Not supported
Not supported
Not supported
Robbed Bit Multiframe

(RBMF)
Not supported
Not supported
Robbed Bit Frame (RBF)
Signaling for ADPCM Mode

The signaling is slightly different when using ADPCM voice encoding:
With E1 trunks timeslot 16 consists of four bits A, B, C, D (as in PCM) for

a specific timeslot. However, since in ADPCM mode each channel requires
only half a timeslot, the first two bits serve the first channel and the last two
bits serve the second channel.
A B A B A B A B
CH1
TS1
CH2
CH(N) CH(N+1)
TS17
With T1 trunks the A, B, C and D bits of each channel are transmitted

through the following frames:
ESF Framing: 6,12,18 and 24. Each channel has two signaling bits.
SF Framing: 6 and 12 only. Each channel has a single signaling bit.
B-315
CH1
CH1
CH2
CH2
Frame
6
Frame
12
Frame
18
Frame
24
In ESF Mode Only
Note
When VC modules operate in ADPCM mode and RBMF signaling with T1 links in
the SF framing mode, the Tx/Rx Translation of the M8T1 module must be
configured in accordance with Table B-76.
Signaling Information
The signaling information exchanged by the channels of VC modules is used for
the following purposes:
Determine the state of the E and M leads
Report the detection of on-hook/off-hook conditions, and control DC closure

across the line
Report the detection of ringing and control the sending of ringing
Control the generation and detection of feed voltage polarity reversal (PCM
mode only)
Control the generation and detection of metering pulses (PCM mode only)
Each type of VC module generates and interprets signaling information in

accordance with the analog interface type (E&M, FXS or FXO) and the signaling
mode selected by the user (loop-start or wink-start).
The format of the signaling information generated by a VC module operating in
the PCM mode, which depends on the analog interface type (E&M, FXS or FXO)
and the signaling mode (loop-start or wink-start), is given in Table B-72, Table B73 and Table B-74. The identification of the signaling bit states is consistent with
the Megaplex default profile designations.
Table B-72. Default Signaling Bit States for E&M Modules (PCM mode)
Direction
Tx
Rx
B-316
Analog Interface
State
Signaling Bits
A
On-Hook
Off-Hook
Ring
No Ring
Table B-73. Default Signaling Bit States for FXS Modules (PCM mode)
Direction
Signaling
Mode
Tx
Loop Start
Rx
Tx
Wink Start
Rx
Analog Interface State
Signaling Bits
A
On-Hook
Off-Hook
Ring
No Ring
On-Hook
Off-Hook
Ring
No Ring
Reversed Polarity
Not Reversed Polarity
Metering Pulse
No Metering Pulse
Table B-74. Default Signaling Bit States for FXO Modules (PCM mode)
Signaling
Mode
Direction
Tx
Loop Start
Rx
Tx
Wink Start
Rx
Analog Interface State
Signaling Bits
A
No Ring
Ring Detected
Remote On-Hook
Remote Off-Hook
No Ring
Ring Detected
Reversed Polarity
Not Reversed Polarity
Metering Pulse
No Metering Pulse
Remote On-Hook
Remote Off-Hook
B-317
Table B-75. Default Signaling Bit States in ADPCM Mode

Direction
Tx
Rx
Note
Note
Analog Interface
State
Signaling Bits
A1
B1
A2
B2
On-Hook
Off-Hook
Ring
No-Ring
In the tables above, X indicates that the corresponding bit is not relevant.
In most applications, the user need not be concerned with the issue of signaling
information.
Signaling Profiles (M8E1, M8T1, M8SL)

The additional flexibility needed to meet the requirements of special applications
is provided by means of signaling profiles, which control the processing of
signaling information received and transmitted by each uplink:
A signaling profile enables the user to select the translation of each individual
signaling bit. The available selections are A, B, C, D (value copied from the
corresponding incoming bit), ~A, ~B, ~C, ~D (inverted value of corresponding
incoming bit), 0 (always 0), and 1 (always 1).

section can also be used to define the signaling bit patterns that indicate the
busy and idle states.
Signaling Profiles are available in the M8E1, M8T1 and M8SL modules only. For
more information on configuring signaling profiles, see Signaling Profiles in
Chapter 5.
Signal Profile Translation for M8T1 Links in ADPCM Mode

When VC-4A and VC-8A modules operate in ADPCM mode with T1 links in the SF
framing mode with RBMF signaling, the Tx/Rx Translation of the main link module
must be configured in accordance with Table B-76.
Table B-76. T1/SF Link Signaling Profile for Working with ADPCM Modules
Rx Translation
B-318
Tx Translation
Signaling Feedback
Certain types of PBX and central office switches require confirmation that the
signaling information has been received, a function referred to as
signaling-feedback in the Megaplex CLI.
Signaling feedback can be enabled only for FXO modules. For VC-4, VC-4A, VC-8
and VC-8A modules, the selection is made for the entire group of all the module
channels. For VC-16/FXO modules, the function can be separately enabled on
each group of eight channels (1 to 8 and 9 to 16).
The list of tasks that can be performed on the VC modules and the recommended
configuration sequence are described in the table below. For detailed
descriptions, refer to Chapter 5. The second column indicates the configuration
context for this task, under which it can be found in Chapter 5. The third column
refers to the reference tables that should be consulted when planning the
module operation.
Task
Reference
Configuring a VC module and put it

into service
Configuring the voice port parameters

(timeslot assignment for PCM voice
ports)
configure>cr>ds0

can be cross-connected with PCM
voice ports, see Cross-Connect Table
in Chapter 5.
Configuring split timeslot crossconnect (timeslot assignment for

ADPCM voice ports)

can be cross-connected with ADPCM
voice ports, see Cross-Connect Table
in Chapter 5.

The test and diagnostics functions available on each module channel are:
For more detail, see Voice Ports in Chapter 5.
B-319
Troubleshooting
The test tone injection functions and the loopbacks available on the VC module
provide a rapid and efficient way to identify the general location of a fault in
either of the two VC modules connected in a link, in the external equipment, or in
the connections to the channels.
If a complaint is received from one of the subscribers connected to the VC
channels, first activate the VC local test loop at the side where the complaint
comes from. The local subscriber must receive its own signal.
Check the connections to the subscriber equipment.
Replace the local VC module.
If the local subscriber receives its own signal when the local loop is activated,
activate test tone injection toward the complaining subscriber. If the subscriber
receives the test tone, the problem is probably in the connections at the remote
side (the side that sends the tone). You can check the computer path of the
remote module channel by activating the remote loopback and the tone injection
toward the remote subscriber, and checking that the local subscriber receives the
test tone.
If the problem is not corrected, the procedure must be repeated at the other side
of the link. Deactivate the local loop and activate the remote loop on the remote
Megaplex unit.
B.16 VC-4/OMNI Modules

operation of the VC-4/OMNI voice interface modules for use in the
The VC-4/OMNI module provides four toll-quality voice channels to support
omnibus applications in which each site communicates with multiple remote
stations simultaneously (such as to broadcast an important message).
Voice signals are digitized using PCM, in compliance with ITU-T G.711 standards,
enabling up to 30 voice channels to be transmitted over an E1 link, or 24 voice
channels over a T1 link. Encoding and decoding are in full compliance with ITU-T
requirements G.712, G.713 and G.714. Voice channel companding is selectable
for A-law or -law.
The module offers flexible configuration of all their operational parameters,
including automatic selection of the signaling information format in accordance
with the operation mode.
B-320
VC-4/OMNI Modules
Applications
The VC-4/OMNI module provides four toll-quality voice channels to support
omnibus applications in which a master site needs to communicate with
multiple remote stations simultaneously (such as to broadcast an important
message).
Voice signals are digitized using PCM, in compliance with ITU-T G.711 standards.
Encoding and decoding are in full compliance with ITU-T requirements G.712,
G.713 and G.714. Voice channel companding is selectable for A-law or -law.
VC-4/OMNI accesses any Megaplex internal TDM bus so that a channel may be
transmitted simultaneously to up to four different main links (trunks). This
enables establishing up to 5-way conference call per channel.
A conference call is established between the local party connected to the
VC-4/OMNI channel (external port) and the remote parties, which are connected
to up to four timeslots (internal ports) assigned to this external port
(see Figure B-101). All conferencing parties can speak to and hear each other. A
single VC-4/OMNI module can support up to four independent conference calls
simultaneously.
Figure B-101. Omnibus Connection

Point-to-multipoint applications for voice or voice-band modems are supported
as well (see Figure B-102). In this configuration, the PCM is broadcasted from the
master side (source) towards the stations (destinations). The stations can speak
to and hear only the master but not the other stations. When a module is initially
configured, it is necessary to define which link is associated with a Master side
and which is associated with a remote Station side.
Figure B-102. Typical Point-to-Multipoint (Modem) Connection
VC-4/OMNI Modules
B-321
Another mode supported is point-to-point. In this mode the channel is operated

as a regular E&M voice channel. Figure B-103 illustrates this mode on the
example of one central and three remote stations.
Figure B-103. Typical Point-to-Point Connection
Features
E&M Interface
The VC-4/OMNI module has 4-wire analog interfaces using E&M signaling.
The module supports four types of E&M signaling: EIA RS-464 types I, II, III and V
(similar to British Telecom SSDC5):
EIA RS-464 Type I signaling standard is supported without any external power
supply.
EIA RS-464 Type II, III and V (BT SSDC5) signaling standards are supported by
means of the internal -12 VDC power supply of the chassis. The -12 VDC
voltage is suitable for most PBX systems. However, for full support of the EIA
RS-464 Type II, III and V (BT SSDC5) signaling standards, a -48 VDC signaling
voltage is required.
powered from a -48 VDC source. An AC-powered Megaplex-4100 chassis can
be either equipped with a Ringer-2100R module or connected to an external
ringer unit, for example, the Ringer-2000 or Ringer-2200N units offered by
RAD (see the appropriate Ringer Installation and Operation Manual for
details).
Note
See Connecting the Signaling and Feed Voltage Source in Chapter 2 for details on
DC power sources and connection methods.
The signaling type is jumper-selectable. Figure B-104 shows the equivalent
signaling circuits for the different signaling modes.
Gain control is soft-selectable for both the receive and transmit directions,
enabling easy installation in all environments.
All operating parameters are configurable via the management system for both
the local and remote modules.
B-322
VC-4/OMNI Modules

E&M
Interface
PBX
Condition
-48VDC
M Lead
On-Hook
Off-Hook
GND
- 48VDC
Open
GND
E Lead
- 48VDC
A. RS-464 Type I
E&M
Interface
PBX
Condition
M Lead
On-Hook
Off-Hook
SB Lead
M/SB
E/SG
Open
- 48VDC
Open
GND
M/SB
E/SG
Open
- 48VDC
Open
GND
- 48VDC
E Lead
- 48VDC
SG Lead
B. RS-464 Type II
E&M
Interface
PBX
Condition
M Lead
On-Hook
Off-Hook
SB Lead
- 48VDC
E Lead
- 48VDC
SG Lead
C. RS-464 Type III

E& M
Interface
PBX
Condition
1.2 k
M Lead
- 48VDC
Open
-48VDC
Open
GND
1.2 k
E Lead
- 48VDC
On-Hook
Off-Hook
M/SB
D. RS-464 Type V, SSDC5

E& M
Interface
PBX
M Lead
SB Lead
+5 VDC
+12 VDC
Condition
- 48VDC
On-Hook
Off-Hook
SG
Open
GND
Open
GND
SG Lead
LEGEND
E. E&M/POS Version (Type II only)
= Signaling Detector Circuit
Figure B-104. E&M Equivalent Signaling Circuits
VC-4/OMNI Modules
B-323
Audio Channel Characteristics

The VC-4/OMNI modules provide high-quality voice channels using toll-quality
64 kbps PCM encoding in compliance with ITU-T Rec. G.711 and AT&T
Pub. 43801.
Two companding laws, -law and A-law, are supported. In accordance with ITU-T
Rec. G.711, A-law must be used on E1 trunks and -law must be used on T1
trunks. However, the user can select either -law or A-law, in accordance with
the specific system requirements.
To increase application flexibility, the nominal audio transmit and receive levels of
all the module versions can be adjusted over a wide range in 0.5 dBm steps.
Due to the high-quality audio reproduction, DTMF signaling is transparently
transferred through the voice channel. Therefore, the user can use DTMF
signaling as usual; e.g., using the telephone set keypad to access voice mail
systems, interactive systems, etc.
Signaling Processing
The VC-4/OMNI module also permits flexible configuration of the signaling mode.
The signaling format, down to the level of the individual bits in the channel
signaling information word, can be modified by defining signaling profiles and
then selecting a particular profile on the main link port serving the module.
TDM Mapping
payload routing in the VC-4/OMNI modules, independently configurable for each
The VC-4/OMNI module occupies one module slot in the Megaplex-4100 chassis.
The figure below shows a panel of the VC-4/OMNI module. The module interface
is terminated in four RJ-45 connectors one per channel.
B-324
VC-4/OMNI Modules
VC-4/Omni
E&M
E
CH-1
M
E
CH-2
M
E
CH-3
M
E
CH-4
M
VC-4/OMNI/E&M
Figure B-105. Megaplex-4100 Module Panel
LED Indicators
The VC-4/OMNI modules with RJ connectors have separate LED indicators for each
channel listed in the table below.
Table B-77. E&M Channel Indicators

Name
Description
On when the M line of the corresponding channel is off-hook

(channel in use).
On when the E line of the corresponding channel is off-hook

(channel in use).
Number of Channels
Voice Encoding
Main Link Bandwidth

Requirements
Method
PCM per ITU-T Rec. G.711, AT&T Pub. 43801
Companding
-law or A-law (user-selectable)

64 kbps per enabled channel (one main link
timeslot)
VC-4/OMNI Modules
B-325
CAS over Timeslot 16
Signaling
DTMF transparently transferred
Analog Interface
Interface Type
4-wire or 2-wire (soft-selectable)
Applicable Standards
2-wire: ITU-T Rec. G.713

4-wire: ITU-T Rec. G.712, G.714
Nominal Level
0 dBm
Nominal Impedance
600
Return Loss (ERL) in the Better than 20 dB

Range of 300 to 3400
Hz
Frequency Response
(Ref: 1020 Hz)
0 dB 0.5 dB, at 300 to 3000 Hz

0 dB 1.1 dB, at 250 to 3400 Hz
Level Adjustment
(soft-selectable)
TX: +5 dBm to -10 dBm

RX: +2 dBm to -10 dBm
Steps: 0.5dB (0.1 dB), nominal
Signal to Total Distortion -30 to 0 dBm0:

Using ITU-T Rec. G.712,
-45 to +3 dBm0:
G.713, Method 2 (8-bit
PCM encoding)
better than 33 dB
better than 22 dB
Idle Channel Noise
Better than -70 dBm0 (+20 dBrnc)
Transformer Isolation
1500 VRMS
E&M Interface Signaling

Method
(User-Selectable)
EIA RS-464 Type I

SSDC5) using internal -12 VDC in place of -48
VDC
Note: For full support of Types II, III, and V (SSDC5)
signaling standards, a -48 VDC supply is required. See
Chapter 2 for details.
End-to-End
Signaling Distortion
2 msec max
T1 Main Links
User-selectable sampling rate:
Signaling
667 samples per second with SF (D4) framing

333 samples per second with ESF framing
E1 Main Links
B-326
VC-4/OMNI Modules
User-selectable as per ITU-T Rec. G.704, para.

3.3.32
Diagnostics
Local digital loopback for any channel towards the local user equipment
Remote digital loopback for any channel towards the remote user
equipment
Forward test tone injection (1 kHz, 0 dBm0) on any channel towards the
remote user equipment
Backward test tone injection (1 kHz, 0 dBm0) on any channel towards the
local user equipment
Connectors
RJ-45 connector for each channel
Power Consumption
5.6W
Indicators
Per channel
E green
M - green
Configuration
Environment
-10C to 55C (14F to 131F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
Warning
Caution

The VC modules contain components sensitive to electrostatic discharge (ESD). To

Setting Internal Switches

The VC-4/OMNI module has several internal switches, which are used to select the
signaling mode. The signaling mode is simultaneously selected for all the
channels. Figure 2-1 shows the switch locations, and Table 2-1 lists the required
switch settings.
VC-4/OMNI Modules
B-327
SW2
OFF
ON
OFF
ON
SW3
SW4
OFF
ON
Figure B-106. VC-4/OMNI Internal Switches

Table B-78. Selection of E&M Signaling Mode
Signaling Mode
Switch SW2
Switch SW3
Switch SW4
RS-464 Type I
ON
ON
ON
RS-464 Type II
ON
OFF
ON
RS-464 Type III
ON
ON
ON
RS-464 Type V (BT SSDC5)
OFF
OFF
OFF
The E&M module signaling mode is factory-set for RS-464 Type V / BT SSDC5.
To configure the VC-4/OMNI module:
Select the signaling mode as required according to Table 2-1.

VC-4/OMNI modules may be installed in an operating chassis (hot insertion).
A VC module starts operating as soon as it is inserted in an operating chassis.
Warning
To install a VC module:
B-328
VC-4/OMNI Modules


Connector Data
The VC-4/OMNI module interface has four RJ-45 connectors. The table below lists
their wiring.

Pin
Designation
Function
SB
Signaling battery
M lead input
R1-OUT
Voice output (4W)

R-IN
Voice input (4W)
T-IN
Voice input (4W)
T1-OUT
Voice output (4W)

SG
Function depends on signaling mode:
RS-464 Type I, III: Direct connection to signal ground
RS-464 Type V, SSDC5: Connection to signal ground

through 1.2 k resistor
RS-464 Type II: SG lead
E lead output
Connecting the Signaling and Feed Voltage Source

The -48 VDC signaling battery voltage used by modules for full compliance with
the EIA RS-464 Type II, III and V (BT SSDC5) signaling standards is supplied to the
Megaplex-4100 module from the chassis DC power distribution bus.
powered from a -48 VDC source. An AC-powered Megaplex-4100 chassis can be
either equipped with a Ringer-2100R module or connected to an external ringer
unit, for example, the Ringer-2000 or Ringer-2200N units offered by RAD (see
the appropriate Ringer Installation and Operation Manual for details).
The Ringer-2100R module supports up to 40 concurrently active Megaplex-4100
channels. Ringer-2200N can support up to 200 active channels; when the
maximum number of active channels does not exceed 100, the Ringer-2000 can
also be used.
VC-4/OMNI Modules
B-329
Caution Since an external voltage source can supply voltage even when the Megaplex is
1. Always turn off the external source (for example, Ringer-2000), before the
Megaplex chassis is turned off.
2. Never connect external DC voltages to modules installed in a Megaplex chassis
if it is not operating.
3. Do not connect/disconnect the ringer while it is operating.
For connection instructions, refer to the Installation and Operation Manual of the
ringer.
Normal Indications
The module starts operating as soon as it is plugged into an operating Megaplex
enclosure. During normal operation, the E and M indicators indicate the activity
on the signaling leads of the corresponding channel.
Configuring External Ports
The encoding parameter must be set to the same value for all the module ports.
This is done by forcing the last choice to all the module ports.
Other parameters you may need to configure for each port are tx-gain, rxsensitivity, wires and operation-mode.
For parameter configuration, see Voice Ports in Chapter 5. For configuring the
transmit and receive levels, see below.
Selection of Transmit and Receive Levels

Transmit Level (tx-gain) selects the nominal input level of the transmit path. The
input level can be set in 0.5 dB steps in the range of +5 dBm to -10 dBm.
Select the transmit level to match the transmission level point (TLP-transmit) of
the equipment connected to the channel. Figure B-100 explains how to
determine the required level setting.
Note that the application of an input signal at the nominal transmit level results
in a 0 dBm digital level, and a far-end output signal equal to the far-end nominal
receive level.
Receive Level (rx-sensitivity) selects the nominal input level of the transmit path.
The input level can be set in 0.5 dB steps in the range of +2 dBm to -10 dBm.
Select the receive level to match the TLP-receive of the equipment connected to
the channel (see Figure B-100).
B-330
VC-4/OMNI Modules
VC Channel
Transmit TLP:
-8dB
T
Transmit
Input Circuit
Nominal Level
= 0 dBm
Signal
Processor
Adjust level (Tx Gain) to -8dBm
Receive TLP:
-2dB
T1
R1
Receive
Output Circuit
Adjust level (Rx Sensitivity) to -2dBm
Figure B-107. Selection of Transmit and Receive Levels
Configuring Internal Ports

The VC-4/OMNI module has 16 internal ports.
Each four consecutive internal ports are assigned to a definite external voice
port, enabling four conference calls simultaneously:
Conference call #1 is formed by any of internal voice ports <slot>/1/1 to

<slot>/1/4 and external voice port <slot>/1.



Each internal TDM port can be independently configured in accordance with the
system requirements.
In the example below, four internal ports of VC-4/OMNI module (installed in
slot 2) are configured and cross-connected with E1 link timeslots of M8E1
(installed in slot 1):
Internal ports 2/1/1 to 2/1/4 for conference call 1
VC-4/OMNI Modules
B-331
#=============================================================#
# Omni Conference CALL mode: Omni Ext1(int 1-4) vs VC8/FXS 4
Voice ports #
#=============================================================#
mp4100# config slot 1 card-type e1-t1 m8e1
mp4100# config slot 2 card-type voice vc4-omni
mp4100# config slot 8 card-type voice vc8fxs
#------------m8e1------------------mp4100# config port e1 1/1 no shutdown

mp4100# config port e1 1/1 line-type g732s
mp4100# config port e1 1/2 no shutdown
mp4100# config port e1 1/2 line-type g732s
#------------vc4-omni----------------mp4100# config port voice 2/1 no shutdown
mp4100# config port voice 2/1 coding a-law
mp4100# config port voice 2/1 operation-mode omni-bus
#----------int 1-4 for ext 1---------mp4100# config port voice 2/1/1 no shutdown
mp4100# config port voice 2/1/2 no shutdown
#------------------------------------#----------vc8fxs----------------mp4100# config port voice 8/1 no shutdown
mp4100# config port voice 8/1 signaling cas
mp4100# config port voice 8/2 no shutdown
mp4100#
mp4100#
mp4100#
mp4100#
config
config
config
config
cr
cr
cr
cr
ds0
ds0
ds0
ds0
e1
e1
e1
e1
1/1
1/1
1/1
1/1
ts
ts
ts
ts
1
2
3
4
voice
voice
voice
voice
2/1/1
2/1/2
2/1/3
2/1/4
mp4100#
mp4100#
mp4100#
mp4100#
mp4100#
config
config
config
config
commit
cr
cr
cr
cr
ds0
ds0
ds0
ds0
e1
e1
e1
e1
1/2
1/2
1/2
1/2
ts
ts
ts
ts
1
2
3
4
voice
voice
voice
voice
8/1
8/2
8/3
8/4
You can configure the internal port to use either legacy signaling (used by the
main link channel connected to this channel) or RAD proprietary signaling for
B-332
VC-4/OMNI Modules
VC-4/OMNI modules. This is done by configuring the omni-signaling parameter

(legacy or abcd).

DS1 and PW ports of the MPW-1 module
The VC-4/OMNI modules use 64 kbps PCM encoding, and therefore require one
uplink timeslot per voice channel. The user can freely route each voice channel to
any uplink port. The voice channel data is provided in DS-0 (8 bits) compatible
format, permitting voice channel routing by DACS cross-connect systems.
Handling of Signaling Information

The following sections describe the handling of the signaling information when
using the legacy main link service mode.
Transfer of Signaling Information

The signaling information of each channel is carried by means of up to four bits
(signaling bits), designated by the applicable standards as bits A, B, C and D. The
number of bits actually available for carrying signaling information, and the data
rate at which signaling information can be transferred depend on the main link
type (E1 or T1) and the framing mode being used:
For E1 trunks with G.732N framing, no signaling information is transmitted.
For E1 trunks with G.732S framing, which use a 16-frame multiframe

structure, the standard signaling method is Channel Associated Signaling
(CAS). In accordance with ITU-T Rec. G.704, the CAS information is
transmitted in timeslot 16. This timeslot carries four signaling bits for each
payload timeslot.
For T1 trunks with ESF framing, which use a 24-frame multiframe structure,
the standard signaling method is inband Robbed Bit Multiframe (RBMF)
signaling. The ESF multiframe structure includes four signaling bits for each
payload timeslot. This method is compatible with ITU-T Rec. G.704 and AT&T
Pub. 43801. When this method is used, the least significant bit of each
channel is periodically overwritten with signaling information.
T1 trunks with SF (D4) framing, which use a 12-frame multiframe structure,

also use the RBMF signaling method. Because of the shorter multiframe
structure, in this case only two signaling bits (A and B) are available for each
payload timeslot.
For applications that do not require end-to-end signaling or can use only inband
signaling (e.g., DTMF), you can disable the transfer of signaling information.
VC-4/OMNI Modules
B-333
For your convenience, Table B-80 lists the supported signaling methods and the
number of signaling bits for E1 and T1 links. Refer to the Chapter 5 for additional
information.
Table B-80. Signaling Methods and Number of Signaling Bits

Signaling Method
E1 Main Link
T1 Main Link
G.732S
G.732N
ESF
SF (D4)
No signaling
0 bits
0 bits
0 bits
0 bits
Legacy
4 bits
Not supported
4 bits
2 bits
ABCD (RAD proprietary for

VC-4/OMNI modules)
4 bits
Not supported
4 bits
2 bits
Signaling Profile
The signaling information exchanged by the channels of VC-4/OMNI module is
used to determine the state of the E and M leads.
Note
In most applications, the user need not be concerned with the issue of signaling
information.
The additional flexibility needed for special applications is provided by signaling
profiles, which control the processing of signaling information received and
transmitted by each main link:
A signaling profile enables the user to select the translation of each individual
signaling bit. The available selections are A, B, C, D (value copied from the
corresponding incoming bit), ~A, ~B, ~C, ~D (inverted value of corresponding
incoming bit), 0 (always 0), and 1 (always 1).

section can also be used to define the signaling bit patterns that indicate the
busy and idle states.
See Signaling Profiles in Chapter 5 for details.

The format of the signaling information generated by a VC-4/OMNI module is
provided in Table B-81. X in this table indicates that the corresponding bit is not
relevant.
Some applications, for example, certain T1 PSTN applications, may require
different signaling bit states. In this case, use configure>signaling-profile
command to define a profile that performs the desired conversions, and then
assign that profile to the main link port carrying the VC-4/OMNI traffic.
B-334
VC-4/OMNI Modules
Table B-81. Default Signaling Bit States for VC-4/OMNI Module

Analog Interface
State
Direction
Tx (M)
Rx (E)
Signaling Bits
A
Idle
Active
Idle
Active
The list of tasks that can be performed on the VC-4/OMNI modules and the
Task
Reference and Comments
Configuring a VC-4/OMNI module and

put it into service
Configuring the external voice port

parameters
<slot><port>
Configuring the internal voice port

parameters

(timeslot assignment for voice ports)
configure>cr>ds0

can be cross-connected with
VC-4/OMNI voice ports, see CrossConnect Table in Chapter 5

The test and diagnostics functions available on each module channel are:
For more detail, see Voice Ports in Chapter 5.
VC-4/OMNI Modules
B-335
Troubleshooting
The test tone injection functions and the loopbacks available on the VC module
provide a rapid and efficient way to identify the general location of a fault in
either of the two VC modules connected in a link, in the external equipment, or in
the connections to the channels.
If a complaint is received from one of the subscribers connected to the VC
channels, first activate the VC local test loop at the side where the complaint
comes from. The local subscriber must receive its own signal.
Check the connections to the subscriber equipment.
Replace the local VC-4/OMNI module.
If the local subscriber receives its own signal when the local loop is activated,
activate test tone injection toward the complaining subscriber. If the subscriber
receives the test tone, the problem is probably in the connections at the remote
side (the side that sends the tone). You can check the computer path of the
remote module channel by activating the remote loopback and the tone injection
toward the remote subscriber, and checking that the local subscriber receives the
test tone.
If the problem is not corrected, the procedure must be repeated at the other side
of the link. Deactivate the local loop and activate the remote loop on the remote
Megaplex unit.
B.17 ACM Module

operation of the ACM alarm module for the Megaplex-4100 Next Generation
Multiservice Access Node. ACM alarm card module includes 4 outbound switches
and 8 inbound sensors for Megaplex-4100 alarm control.
Applications
Figure 1-1 shows a typical alarm and control application for the ACM module. In
this application, the inbound ports of the ACM module installed in the
Megaplex-4100 are connected to the alarm relays of additional equipment units,
and to sensors that monitor the state of critical resources; for example, the
cooling fan of the communication rack, the mains power, etc.
B-336
ACM Module
Figure B-108. Typical ACM Application Alarm and Control

The system administrator can use a management station or a supervision
terminal connected to the Megaplex-4100 unit to monitor the equipment, which
may be located at a remote place, for example, a communication closet. Any
problem will be reported as a plain message displayed on the management
station or supervision terminal.
The outbound ports of the ACM module can be used to automatically take
corrective actions; for example,if a mains failure occurs, an outbound port of the
ACM module can activate a backup power source (for example, start an
emergency generator).
The management station can also activate the alarm that results in the activation
of a desired outbound port; in this way, it is possible to activate the backup
source before a scheduled maintenance activity, and thus prevent disruption of
normal system operation.
Features
The ACM module provides two main functions:
Input ports enable the management system to read inbound indications

from external sources.
Output ports provide outbound indications and control signals by means of

dry relay contacts controlled by the management system.
Inbound (Input) Ports

The ACM module has eight inbound ports, which enable it to report alarms
external to the Megaplex-4100 unit, and physical conditions in remote locations
ACM Module
B-337
to a central management station. The inbound ports of the ACM module can be
connected to relay contacts, environmental sensors, etc.
The ACM module is configured by the user to interpret the state of each input
and report events to the CL module of the local Megaplex-4100. For each event,
the CL module will send the corresponding alarm message, respectively SNMP
trap, to the supervision terminal and network management stations. Each event
can be associated with a user-selected message that describes the situation, or
prompts the remote user to take a prescribed action. For the list of available
alarms, refer to Chapter 6.
The user can monitor the state of each inbound port by means of indicators
located on the ACM front panel.
The input lines are usually connected to sensors (for example, relay contacts of
external equipment) that can be powered by the module. For this purpose, the
internal general-purpose +12 V and -12V voltages are also available in the ALARM
PORT connector. (The maximum current is limited by means of internal 300
series resistors.)
The general-purpose +12 V and -12V outputs can also be used to power directly
sensors and other devices that require small amount of power. For example, the
+12 V output can be used to power a device that requires a supply voltage of +5V
and draws up to 23 mA.
Outbound Ports
The ACM module has four outbound ports equipped with change-over dry relay
contacts. The default state (that is, the state of the relay contacts when the
Megaplex-4100 is operating) can be selected by the user, individually for each
outbound port.
The relay contacts can be used to report internal system alarms to outside
indicators (such as lights, buzzers and bells located on a bay alarm or remote
monitoring panel), and to control external devices or applications (such as fans,
dialers and backup power sources). Each relay can be controlled by a specific
event in the network, in accordance with the configuration defined by means of
the bind-alarm-to-relay and bind-alarm-source-to-relay commands.
The user can monitor the state of each outbound port by means of indicators
located on the ACM front panel.
Management
All operating parameters of ACM are soft-selectable via the management system.
The ACM module occupies one I/O slot in the Megaplex-4100 chassis. The module
panel is shown in the figure below. It includes 25-pin female D-type connector
for connection to the inbound and outbound ports and status indicators for each
inbound and outbound port.
B-338
ACM Module
Figure B-109. ACM Module Panel
LED Indicators
Separate LED indicators (see the table below) show the state of each inbound or
outbound port.
Table B-82. ACM Indicators

Indicator
Description
INBOUND 1 to 8
On when the corresponding input is active
OUTBOUND 1 to 4
On when the corresponding output is active
Inbound Ports
Outbound Ports
Number
Maximum Input Voltage Range
30 V
Number
Outbound Relay Characteristics
General-Purpose
Voltage Outputs
Maximum Voltage across Open

Contacts
24V
Maximum Current through Closed

Contacts
1.25A
Output Voltages
+12 V 5% through 300 series

resistor
-12 V 5% through 300 series
resistor
Connector
25-pin D-type female
Power
Consumption
1.6W
Configuration
Programmable via Megaplex-4100

management system
Environment
0C to 45C (32F to 113F)
Storage Temperature
-20C to 70C (-4F to 160F)
Humidity
ACM Module
B-339

All the module functions are controlled by software. No internal settings are
required.
Warning
Caution
Caution

The ACM modules contain components sensitive to electrostatic discharge (ESD).

To prevent ESD damage, always hold the module by its sides, and do not touch
the module components or connectors.


ACM modules may be installed in an operating chassis (hot insertion).
The ACM module starts operating as soon as it is inserted in an operating chassis.
Warning
To install an ACM module:

3. Insert the ACM module in its chassis slot and slide it in as far as possible.
B-340
ACM Module

The module has a 25-pin female ALARM PORT D-type connector for connection to
the inbound and outbound ports and status indicators for the inbound and
outbound ports. Table B-53 lists the functions of the pins in the connector.
Table B-83. ALARM PORT Connector, Pin Assignment

Pin
Designation
Function
SHIELD
Connection to frame ground
IN7
Inbound port 7 (port Ex11)
IN5
IN3
IN1
OUT4A
Outbound port 4 - center contact (port Ex4)
GROUND
Signal ground for inbound ports
OUT3A
OUT+12
+12V through 300 s e rie s re s is t o r
10
OUT-12
-12V through 300 s e rie s re s is t o r
11
OUT2A
12
OUT1C
Outbound port 1 - normally-closed contact (port Ex1)
13
OUT1B
Outbound port 1 - normally-open contact (port Ex1)
14
IN8
15
IN6
16
IN4
17
IN2
18
OUT4C
19
OUT4B
20
OUT3C
21
OUT3B
22
NC
Not connected
23
OUT2C
24
OUT2B
25
OUT1A
ACM Module
B-341

1. Prepare a cable in accordance with your specific system requirements, using
the information in Table B-53.
2. Connect the corresponding cable to the ALARM PORT connector.
Normal Indications
Once the equipment connected to the ACM ports is operational, the INBOUND
and OUTBOUND indicators display the state of the corresponding port.
Alarm outputs on a card are not bound to any alarm by default and users may
decide which alarm or pair of alarm and source will activate them.
Configuring the ACM Module

This section explains how to configure the inbound and outbound relays.
Configuration defaults are listed in the table below.
energized
no
active
off
To configure outbound and inbound ports:

1. Navigate to configure>reporting# context.
2. Type the configuration parameters listed in the following table:
Command
Syntax
Comments
Sending a signal to the

outbound port that will
assume the active state
when the alarm is active
and setting the active
state of the port relay
(the state of its
contacts when the
alarm conditions are
present)
alarm-output <slot>/<port>
energized {yes | no}
Outbound port range: 1 to 4
Binding an alarm of
specific source type to
an alarm output port
bind-alarm-to-relay <source-type>
<alarm-name> alarm-output
<slot/port>
energized yes The corresponding relay is

normally unenergized (the center contact is
connected to the normally-open contact),
and switches to the energized state when
the alarm is active.
energized no The corresponding relay is
normally energized (the center contact is
connected to the normally-open contact),
and switches to the unenergized state when
the alarm is active.
For the list of source types and
corresponding alarm names, refer to Alarm
list in Chapter 6.
Using no before the command cancels the
alarm binding
Binding an alarm of
specific source type on
a specific user port to
an alarm output port
B-342
ACM Module
bind-alarm-source-to-relay
<source-type> <alarm-name>
<slot/port> alarm-output
<slot/port>
For the list of source types and

corresponding alarm names, refer to Alarm
list in Chapter 6.
Using no before the command cancels the
alarm binding
Command
Syntax
Comments
Creating an alarm input

and setting the active
state of the port input
line and alarm
description
alarm-input <slot>/<port> [active

{high | low | off}] [description
<alarm-input-description-string>]
Inbound port range: 1 to 8

active low the port interprets a low level
(that is, a short-circuit to ground, or an input
voltage less than 0.45 V) as an alarm-active
condition.
active high the port interprets a high level
(that is, an open-circuit to ground, or an
input voltage higher than 2.5 V) as an alarmactive condition.
active off the input alarm port is not
connected
Description-string a free-text message that
will be sent when the corresponding port
switches to the active state
For example:
ACM module installed in slot 2
M8E1 module installed in slot 5.
To bind all los alarms for all fast Ethernet ports in the chassis to Alarm output
port 2/1:
mp4100>config>reporting# bind-alarm-to-relay ethernet los
alarm-output 2/1
To bind all los alarms for E1 port 5/1 to Alarm output port 2/2:
mp4100>config>reporting#bind-alarm-source-to-relay e1 los 5/1
alarm-output 2/2
Configuring the Outbound Relay
The recommended connections to the ALARM PORT connector for energized yes
are as follows:
To obtain an open-circuit when the alarm is active, connect the external line
to the pins corresponding to center and normally-closed contacts.
To obtain a short-circuit when the alarm is active, connect the external line to
the pins corresponding to center and normally-open contacts.
The recommended connections to the ALARM PORT connector for energized no

are as follows:
To obtain an open-circuit when the alarm is active, connect the external line
to the pins corresponding to center and normally-open contacts.
To obtain a short-circuit when the alarm is active, connect the external line to
the pins corresponding to center and normally-closed contacts.
ACM Module
B-343
The list of tasks that can be performed on the ACM module and the
recommended configuration sequence are described in the table below.
Task
Reference
Configuring an ACM module and

put it into service
See Chapter 5
Configuring the inbound and

outbound ports
configure>reporting
Displaying the Configured Ports

After the ACM module starts operating, you can display the state of the various
ports by means of the info detail command. A typical display is shown below.
mp4100>config>reporting# Info d
alarm-output port 2/1 energized no
alarm-input 2/1 active off description "fan off"
alarm-input 2/2 active off description ""
bind-alarm-to-relay ethernet los alarm-output 2/1
bind-alarm-source-to-relay e1 los 5/1 alarm-output
2/2
Troubleshooting
If a problem occurs, check the displayed alarm messages and refer to Chapter 6
for their interpretation.
to the operation of the ACM module, perform the actions listed below, until the
problem is corrected.
Inbound Alarm not Reported

Check whether the corresponding INBOUND indicator lights when the external
alarm condition is present.
B-344
ACM Module
If not, check the cable connecting the external equipment to the ACM ALARM
PORT connector, and make sure the alarm indication (open/short-circuit, or
voltage within the limits given in Inbound (Input) Ports) reaches the correct
pins at the cable end attached to the ACM module.
Note
If not, replace the cable connecting the external equipment, or troubleshoot

that equipment.
Depending on the characteristics of the equipment connected to the port, the

alarm indication can be either an open- or short-circuit or a voltage within the
limits given in Inbound (Input) Ports.
If the corresponding INBOUND indicator lights, check whether the alarm is

masked. If it is not masked, replace the ACM module.
Outbound Alarm not Reported

Check whether the corresponding OUTBOUND indicator lights when the alarm
condition is present.
If not, check whether the alarm is masked. If not masked, replace the ACM
module.
If the corresponding OUTBOUND indicator lights, check the cable connecting

the external equipment to the ACM ALARM PORT connector, and make sure
the alarm indication (open/short-circuit, in accordance with the port
configuration) reaches the correct pins at the cable end attached to the
equipment. If not, replace the cable connecting the external equipment, or
troubleshoot that equipment.
If the problem cannot be corrected by performing these actions, the ACM module
is probably defective and must be replaced.
B.18 Ringer-2100R Module

Ringer-2100R is a 4U-high DC feed power supply (ringer) module for the
Megaplex-2100 and Megaplex-4100 multiplexers.
In this manual, the generic term Megaplex is used to denote both Megaplex chassis.
Ringer-2100R supplies the standard -24 VDC or -48 VDC feed (battery) voltage
required by voice/fax and ISDN basic rate access modules. Ringer-2100R also
supplies a +60/+72 VDC ring voltage which can be used by certain ISDN basic rate
access modules for increasing the feed voltage.
Ringer-2100R can provide DC power for up to 32 voice/fax channels; the number of
ISDN channels that can be supported depends on the required current and the
ISDN DC loop resistance (determined by the pair gage and line length).
The connection of DC voltages to the various modules installed in the same
chassis is made through the internal power supply bus of the chassis.
Product Options
Ringer-2100R can be ordered in AC and DC input voltage versions:
The AC input options are 115 VAC and 230 VAC. The AC-powered
Ringer-2100R provides -48 VDC feed voltage and +72 VDC ring voltage.
Ringer-2100R Module
B-345
The DC input options are -24 VDC and -48 VDC:
Ringer-2100R operating on -24 VDC provides -24 VDC feed voltage and
+60 VDC ring voltage.
Ringer-2100R operating on -48 VDC provides -48 VDC feed voltage and
+60 VDC ring voltage.
Ringer-2100R is a dual-slot wide module, intended for installation in Megaplex
chassis. The module height is 4U.
Figure 2-1 shows front panels of AC- and DC-powered Ringer-2100R modules.
DC-powered
Module
AC-powered
Module
Figure B-110. Ringer-2100R Front Panels

The Ringer-2100R front panel includes two indicators that light when the module
provides normal battery (feed) and ring output voltages. The panel also includes
the external power connector and the POWER on/off switch.
The connection of the output voltages to the internal bus of Megaplex chassis is
made through a connector located at the rear end of the module.
Ringer-2100R does not include cooling fans. To improve cooling and reduce heat
transfer to adjacent modules, it is recommended to install the Ringer-2100R in
the two rightmost slots of the equipment chassis.
B-346
Ringer-2100R Module
Functional Block Diagram
Figure 1-2 shows the functional block diagram of an AC-powered Ringer-2100R
module, which provides -48 VDC and +72 VDC outputs.
The AC-powered Ringer-2100R includes two AC/DC converters powered from
115 VAC or 230 VAC, in accordance with order.
Ringer-2100R
Power
Switch
BATTERY
VOLTAGE
Fuse
AC Input
Power
Connector
-48 VDC
AC/DC
Converter
RING
VOLTAGE
+72 VDC
AC/DC
Converter
GND (common)
+72 VDC
-48 VDC
Rear
Connector
Figure B-111. Functional Block Diagram

The AC input voltage passes through a protection fuse located in the AC input
connector, and through the POWER on/off switch.
The POWER switch includes an internal indicator which lights when the
Ringer-2100R is turned on.
Each AC/DC converter of the Ringer-2100R generates a single DC output voltage,
which is connected to the internal connector located at the rear of the module.
This connector is used to connect the DC voltages generated by the module
directly to the internal power supply bus of the chassis.
Note that the output voltages generated by the Ringer-2100R are referenced to
the common ground.
Each output voltage is monitored by means of an indicator, located on the front
panel.
The DC-powered Ringer-2100R includes DC/DC converters, which operate directly
from the DC input voltage.
Ringer-2100R Module
B-347
DC Output Voltages
The actual DC output voltages generated depend on the Ringer-2100R version, as
shown in the table below.
Ring Voltage Output (may be required
Nominal Input
Voltage
Operating (Input)
Voltage
DC (Feed) Voltage Output
AC
115 to 230 VAC

(10%),
50/60 Hz
-48 VDC (5%), 1.2A max
+72 VDC (5%), 0.7A max
-24 VDC
-24 VDC (-18 to -36

VDC)
-24 VDC (5%), 1.2A max
+60 VDC (5%), 0.7A max
-48 VDC
-48 VDC (-36 to -72

VDC)
-48 VDC (5%), 1.2A max
+60 VDC (5%), 0.7A max
Note
for HS-U, HS-U-6/12, HS-S modules)
Maximum combined output for Battery and Ring voltages is 65W.
Using the Ring Output Voltage

The ring output voltage of the Ringer-2100R (+60 VDC or +72 VDC) can be used
to increase the line feed voltage generated by certain ISDN basic rate access
modules, e.g., HS-U (instead of the basic -24 VDC or -48 VDC feed voltage).
In this case, the feed voltage is generated by the HS-U combining the -24/-48
VDC and the +60/+72 VDC outputs, that is, by using the voltage appearing
between the negative output (the battery voltage line) and the positive output
(the ring voltage line). The maximum feed current is then determined by the
current rating of the +60/+72 VDC output.
The resulting nominal feed voltages that can be obtained in this way are as
follows:
Warning
Negative Voltage
Positive Voltage
Resulting Feed Voltage
-24 VDC
+60 VDC
84 VDC
-48 VDC
+60 VDC
108 VDC
+72 VDC
120 VDC
All voltages above 60 VDC are considered to be hazardous, and may cause
electrical shock or bodily injury.
DC-Output
Connector
Input voltage
Internal DC connector to chassis voltage bus
AC input
115 VAC
230 VAC
B-348
Ringer-2100R Module
DC input
-24 VDC
-48 VDC
Physical
Indicators
Environment
4U-high module, occupies two I/O slots of the Megaplex

chassis
RING VOLTAGE
(green)
On when ring voltage is within the normal range
BATTERY VOLTAGE
(green)
On when feed voltage is within the normal range
Operating
temperature
-10C to 55C (14F to 131F)
Storage
temperature
-20C to +70C (-4F to +158F)
Humidity
up to 95%, non-condensing
Site Requirements
Any interruption of the protective (grounding) connection inside or outside the
equipment, or the disconnection of the protective ground terminal can make this
equipment dangerous. Intentional interruption is prohibited.
Before switching on this equipment and before connecting any other cable, the
protective ground terminals of the equipment must be connected to a protective
ground. The grounding connection is made through the power cable, which must
be inserted in a power socket (outlet) with protective ground contact. Therefore,
the power plug must always be inserted in a socket outlet provided with a
protective ground contact, and the protective action must not be negated by use
of an extension cord (power cable) without a protective conductor (grounding).
Ringer-2100R Module
B-349
Installing the Module in the Chassis

Ringer-2100R is intended for installation in two adjacent slots of a Megaplex unit.
Warning
Note that the Ringer-2100R has an open-frame construction, which exposes

internal circuits. Therefore, for your protection, never operate the module
outside an equipment chassis. Moreover, never connect cables to a Ringer-2100R
module if it is not installed in a properly installed and grounded equipment
chassis, and always disconnect the power cable before removing the module
from the chassis.
To install the Ringer-2100R module in the chassis:
1. Set the POWER switch to OFF.
2. Insert the module in the assigned position, and gently push the module until
its rear connector mates the matching chassis connector. If resistance is felt
before the module panel is flush with the other panels, remove the module
and then repeat the insertion.
Note
Whenever possible, install the Ringer-2100R module in the two rightmost slots of
the chassis.
3. Fasten the two module screws.
Connecting the External Power

1. Connect the power cable to the POWER connector.
2. Connect the other end to the prescribed power outlet.
Operation
All voltages above 60 VDC are considered to be hazardous, that may cause
electrical shock or bodily injury.
Warning
To prevent damage to connected equipment due to incorrect application of feed

voltages, strictly observe the following procedures.
Turning On the Unit

The Ringer-2100R must always be turned on after the Megaplex unit in which it is
installed.
To turn the Ringer-2100R on:
Set the POWER switch to ON. The output voltage indicators must turn on and
light steadily.
Indicators
The module has the following LED status indicators:
B-350
Ringer-2100R Module
RING VOLTAGE: Lights when the ring output voltage is within the allowable
limits.
BATTERY VOLTAGE: Lights when the line feed output voltage is within the
allowable limits.

The Ringer-2100R must always be turned off before the Megaplex unit in which it
is installed is turned off.
To turn the Ringer-2100R off:
Set the POWER switch to OFF.

The indicators must turn off.
Caution
Always turn Ringer-2100R off before removing and installing a voice/ISDN

module in any connected chassis. After the module has been
installed/removed, Ringer-2100R can be turned back on.
Troubleshooting
Identify the closest description of the trouble symptoms listed in Table 3-1 and
perform the corresponding corrective actions.
Table B-84. Troubleshooting Instructions

No.
Symptoms
Corrective Actions
The POWER switch 1. Check that both ends of the power cable are properly connected. In particular,
indicator does not
check that the cable connector is fully inserted in the Ringer-2100R power
light
connector.
2. Check that AC or DC power (in accordance with the Ringer-2100R model) is

present in the power outlet in which the Ringer-2100R power cable is plugged.
Caution
The test must be performed by trained service personnel only, due

to the shock hazard.
For AC-powered modules: Disconnect the AC power cable as follows:

first disconnect the cable from the mains outlet and then disconnect it from the
Ringer-2100R power connector. Remove fuse compartment and check the
condition of the inner fuse: if blown, replace with a fuse of the same type and
ratings (2A/250V fast-blow). An appropriate fuse should be present in the other
position of the fuse compartment.
Warning
The equipment must be serviced by service personnel only, due to

the shock and energy hazards.
Always disconnect the power cable before replacing the fuse.
1. Replace the power cable.
Ringer-2100R Module
B-351
No.
Symptoms
Corrective Actions
The OUTPUT
1. Check that the POWER switch indicator lights. If not, proceed in accordance
VOLTAGE indicator
with item 1 above.
does not light
2. Turn the Ringer-2100R off, remove all the I/O modules installed in the
equipment chassis, and wait for 10 minutes.
3. Turn the Ringer-2100R on again: if the corresponding indicator does not light,
the Ringer-2100R must be serviced.
4. If the indicator lights, start reinstalling the modules one by one: in case the
indicator turns off when a module is inserted, replace that module.
3
Other equipment
does not receive
the required
voltage
Check that the required voltage indicator corresponding to the required output
voltage lights. If not, proceed in accordance with item 2 above.
B.19 MPF Standalone Power Supply for ASMi-54C/N

Modules
MPF (Megaplex Power Feed) is a DC power supply for Megaplex-4100 ASMi-54C/N
SHDSL modules that require DC voltage to phantom feed remote DSL repeaters
or modems.
Applications
The MPF standalone unit provides the DC power for up to 40 active SHDSL
modems or repeaters operating in 4-wire mode (see Figure B-112).
S-RPT
ASMi Modem
SHDSL
SHDSL
Up to 40 Lines
Megaplex-4100
Power Feed
ASMi Modem
MPF
Figure B-112. MPF Supporting Full Megaplex-4100 Chassis with up to 40 SHDSL

Ports
B-352
MPF Standalone Power Supply for ASMi-54C/N Modules
Features
MPF (Megaplex Power Feed) is a DC power supply for Megaplex SHDSL modules
that require DC voltage to phantom feed remote DSL repeaters or modems.
The MPF device has two output connectors to fit two Megaplex-4100 units or one
Megaplex-4100 unit equipped with two PS modules.
MPF is cooled by forced air cooling.
MPF is a standalone unit, intended for installation on shelves or in 19-inch racks.
The unit height is 1U. Figure B-113 shows a general view of an MPF unit with DC
input.
Figure B-113. Megaplex-4100, General View

All the connectors and LEDs are located on the front panel. The rear panel is
blank.
The front panel includes two 3-pin terminal block DC-output connectors, a DC
input power connector and an alarm connector. The panel also includes two LED
indicators.
MPF includes three fans that provide cooling air to the internal circuits. When
viewed from the front, the air intakes are on the left-hand wall, and the air
exhaust holes are located on the right-hand wall.
Functional Block Diagram
The figure below shows the functional block diagram of a typical Megaplex-4100
device.
B-353
Low
Voltages
PS
Fan Failure Indication
CPLD
Cooling
Fans
LEDs
Relays
48V to 72V
DC2DC
F
U
S
E
48VDC Input
Power Connector
Power
Sense
+V
-V
120VDC Output
Connector
A
+V
-V
120VDC Output
Connector
B
Figure B-114. MPF Functional Block Diagram

The input voltage passes through a protection fuse located on the board.
The DC/DC converter generates a single +72 VDC output voltage, which is
connected in parallel to both output connectors.
The -48 VDC voltage from the input connector is also routed to the output
connectors.
The +48V pole of the -48VDC input connector and the -72V pole of the DC-to-DC
output are short-wired, so that between +V and V pins of the output connector
120 VDC output voltage is delivered.
The device also includes a power sense mechanism, alarms relays, fans and LED
indicators.
DC Output
Two options will be supported in the future versions to provide different voltage
in accordance with the label on the panel:
B-354
120 VDC nominal. Pin connector assigned as -V has -48V in reference to

F.GND (0). Pin connector assigned as +V has +72V in reference to F.GND (0),
providing a total of 120 VDC.
144 VDC nominal. Pin connector assigned as -V has -48V in reference to

F.GND (0). Pin connector assigned as +V has +95V in reference to F.GND (0),
providing a total of 144 VDC.
Figure B-115. DC Input Label

Only 120 VDC option is supported in the current version (only +72 and -48 pins
are in use).
DC Input
DC Output
Voltage
36-57 VDC
Connector
3-pins TB (terminal block) male
Total max input power required:
1400W
For operating Megaplex-4100
300W
For power feeding
1100W
Current
29A maximum (@48VDC nominal input)
Connector current capacity
41A maximum
Nominal voltage
120 VDC
Connectors
Two 3-pins TB (terminal block) female
Current
15A maximum
Total output power:
1300W
For operating Megaplex-4100,

-48 VDC
For power feeding
300W
1000W
B-355
Power consumption of
ASMi-54C/E1/ETH/UTP/N/RPF module
from MPF, power feeding operation
(max)
3W + [P x (Cm + Cr)], where:

P number of module ports used for
phantom feeding
Cm remote modem power
consumption
Cr repeater power consumption
Alarm
Connector
LED Indicators
9-pin, D-type, female
PWR (green)
Lights when both +V and -V output

voltages are within normal range
ALARM (red)
Lights if one of the following occurs:

Power consumption from MPF for
power feeding reaches 90% of its
maximum capability
At least one of the fans fails
+V output voltage is at least 15% less
than the nominal voltage
-V voltage is higher than -38 VDC
Physical
Environment
Height
Height: 44 mm (1.7 in) (1U)
Width
480 mm (19.0 in)
Depth
310 mm (12.2 in)
Weight
3.515 kg/7.7 lb
-10 to +45C (14 to 113F)
Storage Temperature
-20 to +70C (0 to 150F)
Humidity
Site Requirements
DC-powered MPF units require a -48 VDC (-36 to -57 VDC) power source. If the
supplied voltage differs from -48 VDC, the MPF output voltage will be changed
accordingly.
Grounding
B-356
The case of the MPF unit must be properly grounded at all times. This is for your
protection, to prevent possible injury to yourself and damage to equipment when
a fault condition, e.g., a lightning stroke or contact with high-voltage power lines,
occurs on the lines which receive feed voltage from the MPF outputs.
Any interruption of the protective (grounding) connection inside or outside the

equipment, or the disconnection of the protective ground terminal can make this
equipment dangerous. Intentional interruption is prohibited.
Before switching on this equipment and before connecting any other cable, the
protective ground terminals of the equipment must be connected to a protective
ground. The grounding connection is made through the power cable, which must
be inserted in a power socket (outlet) with protective ground contact. Therefore,
the mains plug must always be inserted in a socket outlet provided with a
protective ground contact, and the protective action must not be negated by use
of an extension cord (power cable) without a protective conductor (grounding).
Whenever MPF units are installed in a rack, make sure that the rack is properly
grounded, and connected to a reliable, low-resistance grounding system.
MPF includes three internal cooling fans located on the right-hand side wall.
When planning equipment installation, make sure that the air intake and exhaust
holes located on the side walls are not obstructed.
Allow at least 90 cm (36 inches) of frontal clearance for operator access. Allow
the same clearance at the rear of the unit for cable connections.
MPF is intended for installation either on shelves or in 19-inch racks. It should be
located directly above the equipment that receives its DC outputs, e.g., a
Megaplex unit. When the MPF is installed in a 19-inch rack, allow at least 1U of
space below and above the unit.
Package Contents
The MPF package includes the following items:
One MPF unit
Technical documentation CD
RM-34 rack mounting kit.
Connecting the MPF Output

Connect an MPF terminal block DC-output connector to a terminal block DC-input
connector of a Megaplex PS module as shown in Figure B-117 and Table B-85.
B-357
Figure B-116. Connecting the MPF DC Output to Megaplex PS DC-Input Connector

Table B-85. Connecting the MPF DC Output to Megaplex PS DC-Input Connector
MPF TB Connector Pin
Megaplex PS TB Connector Pin
-48V/+72V
+V
+72V
-V
-48V
Connecting the Alarm Port

The alarm port is terminated in a 9-pin D-type female connector, designated
ALARM. The ALARM connector provides connections to the following functions:
Caution
1st and 2nd alarm relay contacts
Alarm output
3.3V auxiliary voltage output (through 2.2k series resistor).
Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
Caution To prevent damage to the internal alarm relay contacts, it is necessary to limit, by
external means, the maximum current that may flow through the contacts
(maximum allowed current through closed contacts is 1A, load switching capacity
is 60 W). The maximum voltage across the open contacts must not exceed 60
VDC.
B-358
Alarm Connector Pinout

To connect to the ALARM connector, you have to prepare a cable, in accordance with
the specific requirements of the site. MPF Alarm connector pin functions are listed in
the table below.
Table B-86. MPF ALARM Connector, Pin Functions

Pin No Function
States
Description
Normally Open (NO)
Activated (Center contact connected to pin 2) if

one of the following occurs:
1st Alarm Relay

t
Normally Closed (NC)
Center contact
GND
2nd Alarm Relay
Power consumption from MPF for power feeding

reaches 90% of its maximum capacity
(+V) Output voltage is 15% lower than nominal

voltage
(-V) voltage is higher than -38V (power failure)
Ground
Normally Open (NO)
Normally Closed (NC)
Center contact
Alarm Output
MPF OK
Activated (Center contact connected to pin 5) if at

least one of the fans fails
Activated (+3.3V via 2.2k resistor) if no alarm

exists
Left open if at least one alarm exists (see LED
Indicators in Chapter 1)
8
Auxiliary voltage
output
3.3V
3.3V auxiliary voltage output (through 2.2k series

resistor)
Connecting two MPF Alarm Out Sockets to CL Module

When two MPF devices are operating in the system, there is a problem to indicate
that at least one of them has a failure, since the working Megaplex CL module has
only one Alarm Input pin (7).
To solve this problem, you can prepare a Y-cable similar to the one shown in
Figure B-118.
To MPF 1
9-Pin
Connector
9-Pin
Connectors
To CL.2
To MPF 2
Figure B-117. Dual-MPF-to-Single-CL Alarm Output Cable
B-359
Figure B-119 shows schematically the cable pinout for the case of two MPF devices
connected to a CL module of Megaplex-4100.
CL
ALARM
1 2 3 4 5
MPF1
6 7 8 9
ALARM
1 2 3 4 5
6 7 8 9
ALARM
1 2 3 4 5
MPF2
6 7 8 9
1st Alarm
Relay
2nd Alarm
Relay
Figure B-118. Dual-MPF-to-Single-CL Alarm Output Cable Pinout

Such connection provides the following Alarm out response:
When both MPF units are OK, their response to CL alarm input is MPF OK.
If MPF 1 fails, the contact at its Pin 7 is left open, and MPF reports an alarm
to the CL module.
If MPF 2 fails, one of its relays is left open and MPF reports an alarm to the
CL module.
Connecting to Power
Caution MPF does not have a power on/off switch and will start operating as soon as
power is applied to its input power connector. It is recommended to use an
external power on/off switch to control the connection of power to MPF. For
example, the circuit breaker used to protect the supply line to MPF may also serve
as the on/off switch.
Power should be connected only after completing cable connections.
Connect the power cable(s) first to the MPF connector, and then to the power
outlet.
B-360
Note
For DC cables, pay attention to polarity. In case of inverse polarity connection

(-48 VDC to +, +48 VDC to -), the input voltage will be connected to the output
connector with the wrong polarity and MPF will not function.
Operation
This section describes the operating procedures with the Megaplex-4100 device.
To prevent damage to connected equipment due to incorrect application of feed
voltages, strictly observe the procedures described below.
-48 VDC outputs are considered as energy hazard, i.e., may cause fire or bodily
injury if short-circuited to GND.
Warning
Turning MPF On
To turn on MPF:
Note
The MPF device does not include a power switch. Use an external power ON/OFF
switch, for example, the circuit breaker used to protect the power lines.
The PWR indicator must turn on and light steadily. The ALARM indicators
should remain off.
The MPF unit must always be turned on after the connected equipment is already
turned on and operating.
Controls and Indicators

Figure B-120 shows a typical MPF front panel. The front panel includes two LED
indicators:
PWR (green) - Lights when both +V and -V output voltages are within normal
range.
ALARM (red) - Lights if one of the following occurs:
Power consumption from MPF for power feeding reaches 90% of its
maximum capability
At least one of the fans fails
+V output voltage is at least 15% less than the nominal voltage
-V voltage is higher than -38 VDC.
Figure B-119. Megaplex-4100 Front Panel

B-361
Over-Current Conditions
In case of over-current condition at the MPF output (about 103%, short circuit in
the worst case), the +V voltage is automatically disconnected for about 10 sec.
Turning MPF Off

MPF must always be turned off before the connected equipment is turned off.
To turn the MPF unit off:
B-362
Disconnect the power cord from the power source.
Publication No. 464-201-09/12
Order this publication by Catalog No. 803988
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

Megaplex-4100 Manual Sheet New PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Megaplex-4100 Manual Sheet New PDF

Încărcat de

Drepturi de autor:

Formate disponibile

INSTALLATION AND

The Access Company

Installation and Operation Manual

North America Headquarters

24 Raoul Wallenberg Street

900 Corporate Drive

19882012 RAD Data Communications Ltd.

Publication No. 464-201-09/12

General Safety Instructions

Do not attempt to adjust the laser drive current.

Do not use broken or unterminated fiber-optic cables/connectors or look

Use of controls, adjustments or performing procedures other than those

Handling Energized Products

Connecting Data and Telecommunications Cables

V.11, V.28, V.35, V.36, RS-530, X.21,

xDSL (without feeding voltage),

TNV-1 Telecommunication Network Voltage-1:

FXS (Foreign Exchange Subscriber)

TNV-2 Telecommunication Network Voltage-2:

FXO (Foreign Exchange Office), xDSL

TNV-3 Telecommunication Network Voltage-3:

Safety Extra Low Voltage:

Ports whose normal operating voltage is within the

Pour rduire les risques sincendie, utiliser seulement des conducteurs de

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Mise au rebut du produit

Instructions gnrales de scurit

Mise la terre de protection : la cosse ou la borne marque devrait tre connecte

Avant la mise en marche de l'quipement, assurez-vous que le cble de fibre

Ne tentez pas d'ajuster le courant de la commande laser.

N'utilisez pas des cbles ou connecteurs de fibre optique casss ou sans

L'usage de priphriques optiques avec l'quipement augmentera le risque pour

L'usage de contrles, ajustages ou procdures autres que celles spcifies ici

Manipuler des produits sous tension

Connexion au courant du secteur

A coded representation of the origin or destination of data.

In SNMP, this refers to the managed system.

AIS (Alarm Indication

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

American National Standards Institute.

An automatic service restoration function by which a network

See Asynchronous Transmission.

A transmission method that sends units of data one character at a

Signal power loss through equipment, lines or other transmission

The American Wire Gauge System, which specifies wire width.

A transmission line in which voltages on the two conductors are

A circuit in which neither side of the line is grounded. This

The range of frequencies passing through a given circuit. The

Refers to transmission of a digital or analog signal at its original

Unit of signaling speed equivalent to the number of discrete

Signaling method in E1/T1 representing a binary 1 by alternating

The smallest unit of information in a binary system. Represents

A process used in time division multiplexing where individual bits

bps (Bits Per Second)

A measure of data transmission rate in serial transmission.

A device interconnecting local area networks at the OSI data link

Wideband technology capable of supporting voice, video and data,

A storage device. Commonly used to compensate for differences

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