MP4100

OPERATION MANUAL
INSTALLATION AND
Megaplex-4100
Next Generation Multiservice Access Node
Version 2.0
The Access Company

Megaplex-4100
Next Generation Multiservice Access Node
Version 2.0
Installation and Operation Manual
Notice
This manual contains information that is proprietary to RAD Data Communications Ltd. ("RAD").
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RAD Data Communications.
Right, title and interest, all information, copyrights, patents, know-how, trade secrets and other
intellectual property or other proprietary rights relating to this manual and to the 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 North America Headquarters

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

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

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 unit’s use,
customers should provide for its collection for reuse, recycling or other form
of environmentally conscientious disposal.
General Safety Instructions
The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
Safety Symbols
This symbol may appear on the equipment or in the text. It indicates potential
safety hazards regarding product operation or maintenance to operator or service
personnel.
Warning
Danger of electric shock! Avoid any contact with the marked surface while the
product is energized or connected to outdoor telecommunication lines.
Protective ground: the marked lug or terminal should be connected to the building
protective ground bus.
Some products may be equipped with a laser diode. In such cases, a label with the
laser class and other warnings as applicable will be attached near the optical
transmitter. The laser warning symbol may be also attached.
Warning Please observe the following precautions:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the transmitter.
• Do not attempt to adjust the laser drive current.
• Do not use broken or unterminated fiber-optic cables/connectors or look
straight at the laser beam.
• The use of optical devices with the equipment will increase eye hazard.
• Use of controls, adjustments or performing procedures other than those
specified herein, may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
In some cases, the users may insert their own SFP laser transceivers into the product. Users are
alerted that RAD cannot be held responsible for any damage that may result if non-compliant
transceivers are used. In particular, users are warned to use only agency approved products that
comply with the local laser safety regulations for Class 1 laser products.
Always observe standard safety precautions during installation, operation and maintenance of
this product. Only qualified and authorized service personnel should carry out adjustment,
maintenance or repairs to this product. No installation, adjustment, maintenance or repairs
should be performed by either the operator or the user.
Handling Energized Products
General Safety Practices

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

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

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

The equipment is designed and approved to comply with the electromagnetic regulations of
major regulatory bodies. The following instructions may enhance the performance of the
equipment and will provide better protection against excessive emission and better immunity
against disturbances.
A good ground connection is essential. When installing the equipment in a rack, make sure to
remove all traces of paint from the mounting points. Use suitable lock-washers and torque. If an
external grounding lug is provided, connect it to the ground bus using braided wire as short as
possible.
The equipment is designed to comply with EMC requirements when connecting it with unshielded
twisted pair (UTP) cables. However, the use of shielded wires is always recommended, especially
for high-rate data. In some cases, when unshielded wires are used, ferrite cores should be
installed on certain cables. In such cases, special instructions are provided in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines
is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal
conversion loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with
plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines.
Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive
wrist strap.
FCC-15 User Information
This equipment has been tested and found to comply with the limits of the Class A digital device,
pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used
in accordance with the Installation and Operation manual, may cause harmful interference to the
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Canadian Emission Requirements

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

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

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

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

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

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

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

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

Manufacturer's Address: 24 Raoul Wallenberg St., Tel Aviv 69719,
Israel
declares that the product:
Product Name: Megaplex-4100
conforms to the following standard(s) or other normative document(s):
EMC: EN 55022:1998 + Information technology equipment – Radio
A1:2000, A2:2003 disturbance characteristics – Limits and
methods of measurement.
EN 50024:1998 + Information technology equipment – Immunity
A1:2000, A2:2003 characteristics – Limits and methods of
measurement.
Safety: 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 Communications GmbH, Otto-Hahn-Str. 28-30, 85521

Ottobrunn-Riemerling, Germany
Contents
Chapter 1. Introduction
1.1 Overview.................................................................................................................... 1-1
Product Options...................................................................................................... 1-1
Common Logic (CL) Modules ............................................................................... 1-1
Power Supply ..................................................................................................... 1-2
Applications ............................................................................................................ 1-2
Main Features ....................................................................................................... 1-10
1.2 Physical Description ................................................................................................. 1-12
System Structure .................................................................................................. 1-12
Equipment Description .......................................................................................... 1-13
I/O Modules .......................................................................................................... 1-14
Common Logic (CL) Modules ................................................................................. 1-18
Power Supply (PS) Modules ................................................................................... 1-20
1.3 Functional Description.............................................................................................. 1-21
System Functional Block Diagrams ........................................................................ 1-22
DS0 Cross-Connect Matrix ..................................................................................... 1-26
Handling the Payload of I/O Modules ................................................................ 1-26
Cross-Connect Modes....................................................................................... 1-27
Handling of CAS Information ............................................................................ 1-28
Handling of PDH Port Payload........................................................................... 1-28
Full Timeslot versus Split Timeslot Assignment .................................................. 1-29
Unidirectional Broadcast Function..................................................................... 1-29
SDH/SONET Subsystem (CL.1/155 and CL.1/155GbE) ............................................. 1-30
SDH/SONET Network Port Interfaces................................................................. 1-32
SDH/SONET Framer Subsystem and HO (STS-1) Cross-Connect Matrix ............... 1-32
SDH/SONET Link Protection Mechanisms........................................................... 1-33
Mapping Matrix ................................................................................................ 1-34
E1/T1 Framers and Mappers ............................................................................. 1-34
SDH/SONET Timing Subsystem.......................................................................... 1-34
Integration of SDH/SONET Subsystem with Ethernet Traffic Subsystem (CL.1/155GbE)
............................................................................................................................ 1-36
GbE Ethernet Switch ............................................................................................. 1-37
GbE Port Interfaces .......................................................................................... 1-38
Flow Control Options........................................................................................ 1-38
Forwarding Algorithms and VLAN Support ......................................................... 1-39
Using Virtual Concatenation (CL.1/155GbE) ........................................................... 1-39
Encapsulation Functions ................................................................................... 1-39
VCG Mapper Functions ...................................................................................... 1-40
Support for LCAS .............................................................................................. 1-41
Megaplex-4100 Ethernet Services ......................................................................... 1-41
Ethernet Service Model..................................................................................... 1-41
Ethernet Services Subsystem ............................................................................ 1-43
Timing Subsystem ................................................................................................. 1-47
System Timing Modes....................................................................................... 1-48
Data Channel Timing Modes ............................................................................. 1-55
ISDN Channel Timing Modes ............................................................................. 1-56
Redundancy Options ............................................................................................. 1-58
CL Module Redundancy .................................................................................... 1-58
Redundancy for SDH/SONET Network Connections (CL.1/155, CL.1/155GbE) ..... 1-59
Management Subsystem ....................................................................................... 1-74
Megaplex-4100 Ver. 2.0 i

Table of Contents Installation and Operation Manual
Management Alternatives ................................................................................. 1-75

Remote Software and Configuration Updating .................................................. 1-76
Supervisory Port Capabilities............................................................................. 1-76
Out-of-Band Access via CL Ethernet Management Port ..................................... 1-76
Inband Management Access through TDM Networks ......................................... 1-77
Inband Management Access through PSN Networks .......................................... 1-78
Performance Monitoring Statistics .................................................................... 1-79
Alarm Collection and Reporting ......................................................................... 1-79
Diagnostic Functions ............................................................................................. 1-80
Power Supply Subsystem ...................................................................................... 1-80
PS Modules ...................................................................................................... 1-80
Feed and Ring Voltage Sources ......................................................................... 1-80
1.4 Technical Specifications............................................................................................ 1-81
Chapter 2. Installation
2.1 Safety ........................................................................................................................ 2-1
General Safety Precautions ..................................................................................... 2-1
Grounding .............................................................................................................. 2-2
Laser Safety ........................................................................................................... 2-3
Protection against ESD............................................................................................ 2-3
Proper Handling of Modules .................................................................................... 2-4
2.2 Site Requirements ...................................................................................................... 2-4
AC Power Requirements .......................................................................................... 2-4
DC Power Requirements.......................................................................................... 2-4
Payload Connections ............................................................................................... 2-5
Connections to E1 and T1 Ports ......................................................................... 2-5
Connections to SHDSL Ports ............................................................................... 2-6
Connections to SDH/SONET Ports ....................................................................... 2-6
Connections to Ethernet Ports............................................................................ 2-7
Optical Cable Requirements ................................................................................ 2-7
Connections to Station Clock .................................................................................. 2-7
Management Connections ....................................................................................... 2-8
Ethernet Connections to CL Modules .................................................................. 2-8
Connection to Serial Port.................................................................................... 2-8
Connections to Alarm Port ...................................................................................... 2-9
Front and Rear Panel Clearance ............................................................................... 2-9
Ambient Requirements ........................................................................................... 2-9
Electromagnetic Compatibility Considerations .......................................................... 2-9
2.3 Package Contents .................................................................................................... 2-10
2.4 Required Equipment ................................................................................................. 2-10
2.5 Mounting the Megaplex-4100 Unit ........................................................................... 2-11
Familiarization with Megaplex-4100 ...................................................................... 2-11
Rear View......................................................................................................... 2-11
Front Panel ...................................................................................................... 2-12
Installing PS Modules ............................................................................................ 2-13
Module Panels .................................................................................................. 2-13
Internal Jumpers ............................................................................................... 2-14
Installing a PS Module....................................................................................... 2-16
Removing a PS Module ..................................................................................... 2-16
Installing CL Modules............................................................................................. 2-16
Module Panels .................................................................................................. 2-16
Preparing CL.1/155 and CL.1/155GbE Modules for Installation........................... 2-19
Installing a CL Module ....................................................................................... 2-20
ii Megaplex-4100 Ver. 2.0

Installation and Operation Manual Table of Contents
Removing a CL Module ..................................................................................... 2-21

Replacing a CL Module During Equipment Operation –Megaplex-4100 Chassis with
two CL Modules................................................................................................ 2-21
Replacing a CL Module During Equipment Operation –Megaplex-4100 Chassis with
Single CL Module .............................................................................................. 2-22
Installing I/O Modules............................................................................................ 2-23
Installing Blank Panels ........................................................................................... 2-23
Installing the Megaplex-4100 Enclosure ................................................................. 2-23
Installing in 19” Rack ........................................................................................ 2-23
Installing in 23” Rack ........................................................................................ 2-24
2.6 Connecting to Megaplex-4100 .................................................................................. 2-24
Grounding the Megaplex-4100 .............................................................................. 2-24
Connecting to Power ............................................................................................ 2-25
Connecting to External Feed and Ring Voltages ..................................................... 2-25
Connecting Cables to Megaplex-4100 CL Ports ...................................................... 2-25
Connecting Cables to CL.1/155 and CL.1/155GbE SDH Links .................................. 2-26
Connection Instructions for Optical Cables ........................................................ 2-26
Connecting Coaxial Cables to CL.1/155 and CL.1/155GbE SDH Links .................. 2-27
Connecting to I/O Modules .................................................................................... 2-27
Chapter 3. Operation
3.1 Turning Megaplex-4100 On ........................................................................................ 3-1
3.2 Indications ................................................................................................................. 3-3
System Indications .................................................................................................. 3-3
CONTROL ETH Interface Status Indications .............................................................. 3-3
SDH/SONET Interface Status Indications (CL.1/155 and CL.1/155GbE Only) .............. 3-3
GbE Interface Status Indications (CL.1/GbE and CL.1/155GbE Only) .......................... 3-3
CL CLOCK Interface Status Indications ..................................................................... 3-4
3.3 Default Settings ......................................................................................................... 3-4
3.4 Configuration and Management Alternatives .............................................................. 3-7
Access Levels for Configuration and Management ................................................... 3-8
Working with Supervision Terminal .......................................................................... 3-8
Preliminary Configuration Sequence.................................................................. 3-10
Configuring Megaplex-4100 via Supervisory Terminal ............................................. 3-15
Preparing New Configuration Parameters.......................................................... 3-15
Validity Checks ................................................................................................. 3-16
Megaplex-4100 Power-up Process .................................................................... 3-17
Organization of Terminal Screens ..................................................................... 3-17
General Supervision Terminal Operating Procedures .......................................... 3-19
Saving Changes to Configuration Database ....................................................... 3-20
Ending a Terminal Configuration Session........................................................... 3-21
Menu Structure of Supervision Utility ................................................................ 3-21
Working with Telnet .............................................................................................. 3-42
General Telnet Operating Procedures................................................................ 3-42
Working with Web Browsers.................................................................................. 3-43
Guidelines for Using Web Browsers................................................................... 3-43
Preparations for Using Web Browsers ............................................................... 3-43
General Web Browsers Operating Procedures ................................................... 3-43
Navigating the ConfiguRAD Menus .................................................................... 3-44
Working with SNMP Management Stations ............................................................ 3-44
Support for SNMP Management ........................................................................ 3-44
Preparing for SNMP Management ..................................................................... 3-45
3.5 Turning the Megaplex-4100 Off................................................................................ 3-46
Megaplex-4100 Ver. 2.0 iii

Chapter 4. Configuration
4.1 Configuring MP-4100 for Management ....................................................................... 4-1
Quick Setup ............................................................................................................ 4-1
Configuring the Control Ports .................................................................................. 4-3
Configuring the Serial Ports ................................................................................ 4-3
Changing the User Authorizations and Security Parameters of the Serial Ports .... 4-4
Configuring the Ethernet (ETH) Port ................................................................. 4-10
Configuring Host IP Parameters and SNMP Communities (with SNMPv3 Disabled) ... 4-11
Configuring Management Access ........................................................................... 4-14
Configuring the Manager List (with SNMPv3 Disabled) ........................................... 4-15
Configuring System Logistic Information................................................................ 4-18
4.2 Configuring Megaplex-4100 for SNMPv3 Management .............................................. 4-19
Overview of SNMPv3 Capabilities ........................................................................... 4-19
User-Based Security Model (USM) ..................................................................... 4-20
SNMP Security Levels........................................................................................ 4-20
SNMPv3 Administrative Features ...................................................................... 4-20
View-Based Access Control Model (VACM)......................................................... 4-21
Configuring SNMP Engine ID .................................................................................. 4-21
Enabling/Disabling SNMPv3 Security Features ........................................................ 4-23
Configuring for SNMP Management with SNMPv3 Security Features ....................... 4-24
SNMPv3 Configuration Sequence ...................................................................... 4-24
Configuring Authorized User Security Parameters ............................................. 4-26
Configuring SNMPv3 Management Attributes .................................................... 4-29
Configuring Target Parameters ......................................................................... 4-30
Configuring Notification Tags ........................................................................... 4-32
Configuring Target Transport Parameters.......................................................... 4-34
Configuring SNMPv1/v3 Mapping ...................................................................... 4-35
Viewing the Summary User Table ...................................................................... 4-36
Viewing the Summary Target Table ................................................................... 4-36
4.3 Configuring Megaplex-4100 for Operation ................................................................ 4-38
Managing Megaplex-4100 Configuration Databases ............................................... 4-38
Overview of DB Tools Menu .............................................................................. 4-39
Database Management .................................................................................... 4-39
Configuring System Parameters............................................................................. 4-44
Programming Modules .......................................................................................... 4-51
Configuring System Clock Sources ......................................................................... 4-52
Configuring Station Clock Parameters .................................................................... 4-56
Preparing Signaling Profiles ................................................................................... 4-59
Configuring Physical Layer Parameters................................................................... 4-61
Configuring the CL Physical Layer .......................................................................... 4-64
Configuring the Physical Layer Parameters of GbE Ports ........................................ 4-65
Configuring SDH/SONET Network Ports ................................................................. 4-70
Task Selection .................................................................................................. 4-71
Card Configuration ........................................................................................... 4-71
Configuring Common PDH LVC Parameters ........................................................ 4-74
Configuring SDH/SONET Link Parameters .......................................................... 4-74
Configuring DCC Parameters ............................................................................. 4-75
Configuring All Links ......................................................................................... 4-77
Configuring the Logical Layer ................................................................................ 4-78
Selecting a Specific I/O Module Virtual Port to be Configured ............................ 4-83
Configuring Logical Layer on SDH/SONET Links ...................................................... 4-84
Selecting the Specific CL Virtual Port to be Configured ...................................... 4-84
Configuring Virtual PDH Ports ........................................................................... 4-85
iv Megaplex-4100 Ver. 2.0

Configuring HVC Virtual Ports ............................................................................ 4-94

Configuring Ethernet Services ............................................................................. 4-101
Configuring HDLC Bundles for Ethernet Services ............................................. 4-103
Configuring MLPPP Bundles for Ethernet Services ............................................ 4-108
Configuring Virtual Concatenation Groups ....................................................... 4-111
Configuring Ethernet Flows............................................................................. 4-127
Configuring APS for SDH/SONET Links ................................................................. 4-138
Configuring Timeslot Assignment ........................................................................ 4-140
Configuring Payload Mapping to SDH/SONET Links ............................................... 4-151
Typical Mapping Procedure ............................................................................. 4-152
Using the Menu Mapping Mode....................................................................... 4-154
Bypassing between Links................................................................................ 4-156
Mapping Ports with Path Protection Enabled ................................................... 4-158
Configuring Fault Propagation ............................................................................. 4-159
4.4 Additional Tasks ..................................................................................................... 4-162
Setting the Internal Date & Time ......................................................................... 4-162
Performing File Transfers to CL Modules .............................................................. 4-163
File Utilities Menu ........................................................................................... 4-163
Before Starting File Transfers ......................................................................... 4-164
File Transfers to CL Modules ........................................................................... 4-164
Updating the CL Management Software .......................................................... 4-165
Downloading a Configuration File ................................................................... 4-167
Uploading a Configuration File ........................................................................ 4-168
File Transfers to I/O Modules and SDH/SONET Subsystems .................................. 4-168
Using the Dir Function .................................................................................... 4-172
Deleting Files ................................................................................................. 4-173
Viewing Logistic (Inventory) Information ............................................................. 4-174
Displaying System Inventory Information ........................................................ 4-174
Displaying SW/HW Revision Information .......................................................... 4-175
Reloading Factory Defaults ................................................................................. 4-176
Reset Device ....................................................................................................... 4-177
Chapter 5. Configuring Typical Applications

5.1 Overview.................................................................................................................... 5-1
Outline of Preliminary Configuration Sequence ........................................................ 5-1
General Configuration Sequence ............................................................................. 5-2
5.2 Configuration Procedure for Typical Ethernet Transport Application ............................ 5-5
Overview ................................................................................................................ 5-5
Configuration Sequence .......................................................................................... 5-6
Preliminary Configuration (All Sites) ........................................................................ 5-6
Configuring the Primary Site (Location A) ................................................................ 5-7
Configuring the Clock Sources ............................................................................ 5-7
Configuring the Physical Layer ............................................................................ 5-8
Configuring Bundles ........................................................................................... 5-9
Interconnecting Bundles to Form Flows ............................................................ 5-12
Connecting Bundle to the E1 Ports ................................................................... 5-17
Configuring Equipment at Location B..................................................................... 5-19
Configuring the Clock Source ............................................................................ 5-19
Configuring the Physical Layer .......................................................................... 5-20
Configuring Bundles ......................................................................................... 5-21
Connecting Bundles to the E1 Ports .................................................................. 5-29
Configuring Equipment at Location C ..................................................................... 5-31
Megaplex-4100 Ver. 2.0 v

Configuring the Clock Source ............................................................................ 5-31

Configuring the Physical Layer .......................................................................... 5-32
Configuring Bundles ......................................................................................... 5-33
Connecting Bundle to the E1 Ports ................................................................... 5-41
5.3 Configuration Procedure for Typical SONET Transport Application ............................. 5-44
Overview .............................................................................................................. 5-44
Configuration Sequence ........................................................................................ 5-45
Preliminary Configuration (All Sites) ...................................................................... 5-45
Configuring Equipment at Location A..................................................................... 5-46
Configuring SDH/SONET Subsystems................................................................. 5-46
Configuring OC-3 Physical Layer........................................................................ 5-47
Configuring System Clock Sources .................................................................... 5-48
Configuring and Mapping the PDH Ports ........................................................... 5-48
Configuring I/O Ports on Other Modules............................................................ 5-50
Configuring Ethernet Bundles ........................................................................... 5-52
Assign Timeslots on PDH Port 1 ........................................................................ 5-55
Configuration Equipment at Location B ................................................................. 5-56
Configuring OC-3 Physical Ports ........................................................................ 5-57
Configuring the Timing and Clock Sources ......................................................... 5-58
Configuring and Mapping the PDH Ports ........................................................... 5-58
Configuring the I/O Ports of M8T1 Modules ...................................................... 5-60
Configuring I/O Ports on Other Modules............................................................ 5-61
Configuring Ethernet Bundles ........................................................................... 5-66
Assign Timeslots on CL PDH Port 1 ................................................................... 5-68
Assign Timeslots on M8T1 Ports ....................................................................... 5-69
Configuration Equipment at Location C.................................................................. 5-70
Configuring OC-3 Physical Ports ........................................................................ 5-70
Configuring the Timing and Clock Sources ......................................................... 5-71
Bypassing PDH Ports ........................................................................................ 5-72
Chapter 6. Troubleshooting and Diagnostics

6.1 Monitoring Performance ............................................................................................. 6-1
Overview of Monitoring Menu ................................................................................. 6-2
Selecting a System Monitoring Task ........................................................................ 6-7
Displaying the Active Alarms ................................................................................... 6-7
Monitoring the Timing Source Status ..................................................................... 6-12
Monitoring the CL Module Status .......................................................................... 6-12
Monitoring the Megaplex-4100 Remote Agents ..................................................... 6-13
Monitoring the APS Status .................................................................................... 6-14
Selecting Virtual Ports for Monitoring .................................................................... 6-15
Monitoring Virtual Ports on I/O Modules ................................................................ 6-16
Selecting a Virtual Port or Bundle for Monitoring ............................................... 6-16
Displaying I/O Virtual Port Monitoring Data ....................................................... 6-17
Monitoring Virtual Ports on CL Modules ................................................................. 6-22
Selecting a CL Virtual Port for Monitoring .......................................................... 6-22
Monitoring SDH/SONET Virtual Ports ................................................................. 6-24
Monitoring – VC-4 and STS-1 Virtual Ports ........................................................ 6-25
Monitoring – VC-3 Virtual Ports......................................................................... 6-30
Monitoring – VC-12 or VT1.5 Virtual Ports ......................................................... 6-32
Displaying WAN Intervals Parameters ................................................................ 6-36
vi Megaplex-4100 Ver. 2.0

VCG WAN Side Statistics – LAPS Encapsulation .................................................. 6-37

WAN Side Statistics – GFP Encapsulation .......................................................... 6-38
Displaying LCAS Path Info Parameters for Virtual Ports ...................................... 6-41
Monitoring Physical Layer Parameters ................................................................... 6-42
Selecting the Class of Physical Ports ................................................................. 6-42
Monitoring I/O Physical Layer Parameters .............................................................. 6-43
Displaying I/O TDM Physical Layer Monitoring Data ........................................... 6-45
Displaying I/O Ethernet Physical Port Monitoring Data ....................................... 6-53
Monitoring CL Physical Ports ................................................................................. 6-59
Selecting the Class of CL Physical Ports for Monitoring ...................................... 6-59
Displaying Monitoring Data for Station Clock Port ............................................. 6-60
Displaying Monitoring Data for the SDH/SONET Subsystem ............................... 6-62
Displaying SDH/SONET Subsystem Timing Information ...................................... 6-62
Displaying Monitoring Data for an SDH/SONET Link ........................................... 6-64
Displaying Path Protection Monitoring Data for an SDH/SONET Link .................. 6-70
Displaying Monitoring Data for the GbE Ethernet Subsystem ............................. 6-72
Displaying Monitoring Data for a GbE Port ........................................................ 6-72
6.2 Detecting Errors ....................................................................................................... 6-78
6.3 Handling Alarms and Traps ....................................................................................... 6-95
Alarm Collection and Reporting ............................................................................. 6-95
Alarm Buffer .................................................................................................... 6-95
Alarm Relays .................................................................................................... 6-95
Customizing Alarm Handling (Alarm Configuration) ................................................ 6-95
Displaying Alarms................................................................................................ 6-108
Interpreting Alarm Messages ............................................................................... 6-109
Traps Generated by Megaplex-4100 .................................................................... 6-132
6.4 Troubleshooting ..................................................................................................... 6-136
Preliminary Checks .............................................................................................. 6-136
Troubleshooting Procedure ................................................................................. 6-136
6.5 Testing Megaplex-4100 Operation .......................................................................... 6-139
Description of Test and Loopback Functions ....................................................... 6-139
Local Loopback on I/O Port of I/O Module ....................................................... 6-142
Remote Loopback on I/O Port of I/O Module ................................................... 6-143
Local Loopback on E1 or T1 Port of I/O Module............................................... 6-143
Remote Loopback on E1 or T1 Port of I/O Module .......................................... 6-143
Local Loopback on Timeslots of E1 or T1 I/O Module Port ............................... 6-144
Remote Loopback on Timeslots of E1 or T1 I/O Module Port ........................... 6-144
Local Loopback on SDH/SONET Link (CL.1/155 and CL.1/155GbE only) ............ 6-144
Remote Loopback on SDH/SONET Link (CL.1/155 and CL.1/155GbE only) ........ 6-145
Local Loopback (LLB) on LVC (CL.1/155 and CL.1/155GbE only) ....................... 6-145
Remote Loopback on LVC (CL.1/155 and CL.1/155GbE only) ........................... 6-146
Global PDH Local Loopback (CL.1/155 and CL.1/155GbE only) ......................... 6-146
Global PDH Remote Loopback (CL.1/155 and CL.1/155GbE only) ..................... 6-146
Local Loopback on PDH Port (CL.1/155 and CL.1/155GbEonly) ........................ 6-146
Remote Loopback on PDH Port (CL.1/155 and CL.1/155GbEonly) .................... 6-147
Local Loopback on PDH Port Timeslots (CL.1/155 and CL.1/155GbE only) ........ 6-147
Remote Loopback on PDH Port Timeslots (CL.1/155 and CL.1/155GbEonly)..... 6-147
Activating Tests and Loopbacks........................................................................... 6-148
Overview of Diagnostics Menu ............................................................................ 6-148
Diagnosing Physical Layer ................................................................................... 6-150
Diagnosing the I/O Module Physical Layer ....................................................... 6-151
Diagnosing the CL.1/155 and CL.1/155GbE Modules ....................................... 6-151
Diagnosing the Virtual Ports ................................................................................ 6-155
Diagnosing the I/O Module Virtual Ports.......................................................... 6-156
Megaplex-4100 Ver. 2.0 vii

Diagnosing the CL.1/155 and CL.1/155GbE Virtual Ports ................................. 6-157

PDH Global Loop Test ..................................................................................... 6-158
Tests on a Selected PDH Port ......................................................................... 6-159
Ping Test ............................................................................................................ 6-162
6.6 Technical Support .................................................................................................. 6-163
Appendix A. Connection Data

Appendix B. Installing New Software Releases
Appendix C. Operating Environment
viii Megaplex-4100 Ver. 2.0

Quick Start Guide
If you are familiar with the Megaplex-4100, use this guide to prepare it for operation,
starting from its factory-default configuration.
Before performing the procedures described below, review the safety precautions
given in Chapter 2.
Warning
Installing Megaplex-4100
1. Refer to the site installation plan and install the Megaplex-4100 enclosure in
the prescribed position.
2. Install modules in accordance with the site installation plan (slot utilization is
identified below).
3. When necessary, install the prescribed SFPs on the CL modules.
Slot PS-A PS-B I/O 1 I/O 2 I/O 3 I/O 4 I/O 5 CL-A CL-B I/O 6 I/O 7 I/O 8 I/O 9 I/O 10
PS-A PS-B I/O 1 I/O 2 I/O 3 I/O 4 I/O 5 CL-A CL-B I/O 6 I/O 9 I/O 10
PS-200/DC PS-200/DC HSU-12 HSU-12 M8E1 M8T1 CL-1 CL-1 M8SL
1 5 5/GbE 1 5 5/GbE
STATUS STATUS STATUS
CH TST LOS CH TST LOS L 1 2 L 1 2 L 1 2
I 3 4 I 3 4 I 3 4
1 1 N N N
5 6 5 6 5 6
K K K
2 2 7 8 7 8 7 8
ON LINE ALM ON LINE ALM
ON LINE LOS LINK ACT ON LINE LOS LINK ACT ETH1
3 3 ETH2
L G L G LINK ACT
4 4
TX
TX
I b I b
N E N E
5 5 K 1 K 1
RX
RX
1 1
6 6
ON LINE LOS LINK ACT ON LINE LOS LINK ACT
7 7 L G L G
I I
TX
TX
b b
8 8 N E N E
K 2 K 2
LINK LINK
RX
RX
2 2
9 9 1-8 1-8
VDC-IN VDC-IN S
10 10 L L H
C O C O D
ON LINE LOS L S ON LINE LOS L S
11 11 O O S
E C E C L
X K O X K O
12 12
N N
L L
I A I A LASER
- - N C N C
LASER LASER CLASS
+ 72V + 72V CLASS CLASS

K E T K E T 1
-
1 1
+ - 48V + 48V T
L
T
L
+ - 24V + - 24V ACT
E
T ACT
E H
I
H
I E
TX
TX
TX
T N N T
ON ON H H K K H
LINK LINK
RX
RX
RX
1 1 1
C C
POWER POWER A O A O
CH. CH. E E L D N L D N E
TX
ACT
TX
T ACT
TX
T A C T A C T T
ON ON 1-12 1-12 R E R R E R
H H H
LINK LINK M O M O
RX
RX
RX
2 2 L L 2
E E AC T
OFF OFF ACT E
TX
T ACT
TX
T T
H H H
LINK LINK
RX
RX
3 3 3 LINK
PS Slots I/O Slots CL Slots I/O Slots
4. Refer to the site installation plan, and connect the prescribed cables to the
Megaplex-4100 modules.
Megaplex-4100 Ver. 2.0 1

Quick Start Guide Installation and Operation Manual
Configuration Instructions
Turn On
Caution
When an external feed and ring voltage source is connected to the PS modules
installed in the Megaplex-4100, always turn that source on only after the PS
module(s) have been turned on.
1. Set the POWER switch(es) on the rear panel(s) of the PS module(s) to ON,
and monitor the power-up initialization process.
2. 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.
Preparations for Configuration

1. Connect a terminal to the CONTROL DCE connector of the active CL module
(use a straight cable).
Note You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CL modules installed in the Megaplex-4100, using a Y-cable.
You may use any standard ASCII terminal (dumb terminal or personal
computer emulating an ASCII terminal) equipped with an RS-232
communication interface. Make sure to use VT-100 terminal emulation.
2. Configure the terminal for communication with the Megaplex-4100.
If the Megaplex-4100 default configuration has not yet been changed,
configure the terminal for 115.2 kbps, one start bit, eight data bits, no parity,
and one stop bit. Select the full-duplex mode, echo off, and disable any type
of flow control.
3. Press <Enter> once to obtain the log-in screen.
If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for the prompt: In
order to start working - press the ENTER button for few times before
pressing <Enter>.
4. Log in as administrator.
If the Megaplex-4100 default user name and password have not yet been
changed, log in as administrator using su as the user name and 1234 for
password.
5. If your password is accepted, you will see the Megaplex-4100 main menu.
2 Megaplex-4100 Ver. 2.0

Installation and Operation Manual Quick Start Guide
Preliminary Configuration Sequence

The table below provides the preliminary configuration sequence.
Step Action Using …
1 Select the default database, 1 Configuration>DB Tools>Default DB

2 If the Megaplex-4100 is equipped with all Configuration>DB Tools>Load HW
the modules, load the hardware
configuration.
Alternatively, configure the modules and Configuration>System>Card Type
then reload the factory-default parameters
installed in the Megaplex-4100. You can
also program modules not yet installed in
the chassis
3 Configure the preliminary set of IP Configuration>Quick Setup

communication parameters
4 Configure CONTROL DCE port parameters Configuration>System>Control Port>Serial Port
5 Configure CONTROL ETH port parameters Configuration>System>Control Port>ETH
6 Configure the Megaplex-4100 management Configuration>System>Management>Host IP
agent
7 Configure Megaplex-4100 management Configuration>System>Management>Mng Access
access
8 Configure specific management stations Configuration>System>Management>Manager List
(optional)
9 Set Megaplex-4100 real-time clock Configuration>System>Date & Time
(optional)
10 Save the configured information in Configuration>DB Tools>Update DB 1
database 1 or
Type %

General Application Configuration Sequence

The table below provides the general application configuration sequence for
Megaplex-4100. Skip steps not applicable to your particular application.
1 Configure Megaplex-4100 signaling profiles Configuration>System>Signaling Profile

2 Configure the CL modules physical ports:
• Station clock ports Configuration>Physical Ports>CL>CL-A, CL-B>Station
• GbE (LAN) ports (make sure to configure Clock
the GbE port redundancy parameters) Configuration>Physical Ports>CL>CL-A, CL-B>LAN
• SDH/SONET ports (make sure to configure
the frame structure) Configuration>Physical Ports>CL>CL-A, CL-B>
SDH/SONET
3 Configure the physical ports of the I/O Configuration>Physical Ports>I/O>I/O-1 to I/O-10
modules (E1, T1, SHDSL, Ethernet, etc.)
4 Configure the Logical Layer on the
SDH/SONET ports of the CL modules:
• PDH ports Configuration>Logical Layer>CL>PDH
• High-order VCs Configuration>Logical Layer>CL>HVC>CL-A, CL-B
5 Configure the Logical Layer of the I/O module Configuration>Logical Layer>I/O>I/O-1 to I/O-10
internal ports
6 Prepare the Megaplex-4100 for SNMP

management:
1. Select the SNMP support mode Configuration > System > Management > SNMPv3
(enable/disable SNMPv3).
If SNMP support mode is changed, save to
activate the change before continuing.
2. When SNMPv3 is Disabled, configure Configuration > System > Management > Host IP
SNMPv1 community names.
3. When SNMPv3 is Enabled, configure
parameters in the following order:
– SNMP Engine ID Configuration > System > Management > SNMP Engine
ID
– SNMPv3 users Configuration > System > Management > SNMPv3
Setting > Users
– SNMPv3 targets and notifications Configuration > System > Management > SNMPv3
Setting > Targets & Notify
– Configure SNMPv1/SNMPv3 mapping Configuration > System > Management > SNMPv3
Setting > SNMPv1/v3 Mapping

Installation and Operation Manual Quick Start Guide
7 Configure Ethernet services in the following

order:
• Configure the prescribed bundles Configuration>Logical Layer>Bundles
on I/O module ports, and on PDH ports
• Configure the prescribed virtually Configuration>Logical Layer>CL>CL-A, CL-B>VCAT
concatenated groups on SDH/SONET links,
and where necessary configure virtually
concatenated group redundancy
• Configure the Ethernet flows Configuration>Applications>Ethernet Services>Flows
8 Configure the inband management flow Configuration>System>Management>Flow
9 Configure path protection parameters for Configuration> Logical Layer>IO
each virtual and I/O module internal port
10 Configure clock sources and timing flow Configuration>System>Clock Source
11 Configure APS groups Configuration>System>APS
12 Configure internal cross-connections Configuration>System>TS Assignment
13 Configure internal mapping Configuration>System>Mapping
14 Configure fault propagation Configuration>System>Fault Propagation
15 Configure Megaplex-4100 alarm handling Configuration>System>Alarms Configuration
16 Save the final configuration as a database Configuration>DB Tools>Update DB
17 If necessary, prepare additional databases To start from an existing database, use
(up to 10) Configuration>DB Tools>Load DB. Repeat the relevant
steps as needed to create a new database


Chapter 1
Introduction
1.1 Overview
Megaplex-4100 is a highly versatile, high-capacity next-generation multiservice
access node with advanced management capabilities. In its full configuration,
Megaplex-4100 provides high-capacity, non-blocking 4/1/0 cross-connect with
SDH/SONET terminal (TM) and add-drop (ADM) functionality, Ethernet services
per Metro Ethernet Forum, and Ethernet gateway capabilities up to GbE rates.
Megaplex-4100 consists of a compact, fully modular chassis providing a flexible
and scalable node that supports a wide range of user services and provides
effective cross-connect and flexible transport options. The available services
include a wide range of voice services; data from low speed (sub-DS0) to high
speed at up to 2 Mbps; ISDN and ISDL; E1, T1, and E1 over two-wire SHDSL; fiber
multiplexing; pseudowire connectivity; multilink STM-1/OC-3, as well as multilink
Fast Ethernet and Gigabit Ethernet. Special services such as omnibus and party
line voice services, teleprotection channels, etc., are also available.
Redundancy with hot swapping is supported for all the critical subsystems (most
interfaces, common logic timing, and power supply), thereby achieving
carrier-class availability.
Advanced systems design confers the flexibility needed to meet the requirements
of practically every TDM and Ethernet application. Full redundancy for all the
critical subsystems ensures high availability for continuous, reliable service.
Extensive management capabilities, starting with supervision terminals and Telnet
hosts and up to SNMP-based network management, confer complete control over
all aspects of equipment operation, and support efficient provisioning and rapid
response to changing requirements. To protect network operations against
unauthorized access, Megaplex-4100 supports SNMP management with
authentication and privacy per SNMPv3, with continued support for SNMPv1.
Product Options
Common Logic (CL) Modules

Megaplex-4100 can be ordered with one or two common logic (CL) modules.
Currently, the following CL models are offered:
• CL.1: common logic and cross-connect module with basic functionality.
• CL.1/155: common logic and cross-connect module with two STM-1/OC-3
links, includes a complete SDH/SONET traffic handling subsystem.
Megaplex-4100 Ver. 2.0 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
• CL.1/GbE: common logic and cross-connect module with two GbE links for
connection to packet switched networks.
• CL.1/155GbE: common logic and cross-connect module with two STM-1/OC-3
and two GbE links. This module includes both SDH/SONET and Ethernet traffic
handling subsystems.
The GbE 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).
• SFP sockets, for installing SFP plug-in modules.
Power Supply
Megaplex-4100 can be ordered with AC or DC power supply modules. It can also
be ordered with one power supply module, or with two power supply modules,
for redundancy.
Applications
Figure 1-1 shows a typical access node application for a Megaplex-4100 equipped
with CL.1/155 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, for example, to dedicated FCD, ASMi, or DXC units
offered by RAD.
A single STM-1 or OC-3 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, or 84 T1 streams), with flexible mapping. In addition, the
DS0/DS1 cross-connect matrix of the chassis can also provide cross-connect
services among the I/O modules installed in the chassis. Since a single STM-1 or
OC-3 link is sufficient, only one CL.1/155 module must be installed in the
Megaplex-4100.
For better protection against transmission failures on the SDH/SONET link
between the Megaplex-4100 and the SDH/SONET backbone, APS (automatic
protection switching) should be used. This is achieved by enabling the two
SDH/SONET ports of the CL.1/155 module, connecting them by two STM-1 or
OC-3 links to two appropriately configured ADM ports, and configuring the
CL.1/155 ports as one APS group. For ensuring good service quality, protection
switching can be configured to also occur in case of signal degradation.
Availability can be significantly increased by installing two CL.1/155 modules: this
provides redundancy for the Megaplex-4100 management and system timing
subsystems, and also permits using STM-1 or OC-3 ports on different CL.1/155
modules as APS partners, for hardware redundancy, in addition to the
transmission path redundancy available with a single CL module.
1-2 Overview Megaplex-4100 Ver. 2.0

Installation and Operation Manual Chapter 1 Introduction
POP
SHDSL
n x E1/T1 E1
HS
CPE
IDSL
DXC-30
PBX
n x E1/T1
CPE MP-2100
E1/T1
POP
FCD-E1LC
CPE
STM-1/
OC-3 SHDSL
SDH/
SONET
ASMi-52
MP-4100
E1
CPE
FE1
DXC-4
E1
Figure 1-1. Megaplex-4100 as a Versatile Multiservice Access Node

The application of Figure 1-1 uses only two of the SDH/SONET ports that can be
installed in the Megaplex-4100 (the maximum is four, two on each CL module).
For better utilization of the link between the Megaplex-4100 and the ADM in the
PoP, this link can also be used to carry traffic for additional Megaplex-4100 units.
Figure 1-2 illustrates how to extend the application of Figure 1-1 to enable
additional Megaplex-4100 units to use the same SDH/SONET link (and thus, the
same ADM ports), using a chain topology. In the application of Figure 1-2, the
two SDH/SONET ports on CL module A provide an APS-protected link to the ADM,
with a total payload capacity of one STM-1/OC-3. CL module A is configured as
the active CL module, and therefore its internal cross-connect matrix provides the
add/drop function for the I/O ports installed in the chassis that need to connect
to the SDH/SONET backbone. The unused capacity of the protected link can be
bypassed to the desired link of CL module B, which provides STM-1 or OC-3 links
to other equipment, for example, to other Megaplex-4100 units.

Megaplex-4100 B
Link 1
Megaplex-4100 A
Link 1 Link 1
SDH/SONET STM-1/OC-3
Link 2 Link 2
CL-A CL-B
Megaplex-4100 C
Link 1
Figure 1-2. Megaplex-4100 in Chain Applications

When protection of the SDH/SONET link as illustrated in Figure 1-2 is not
required, each SDH/SONET port in the chassis can be independently used,
provided a few restrictions (explained in the SDH/SONET Subsystem (CL.1/155
and CL.1/155GbE) section) are observed:
• The total number of E1s or T1s that can be connected to internal I/O ports:
63 for SDH interfaces, 84 for SONET interfaces.
Note that all the connections to internal I/O ports are performed only by
means of the cross-connect matrix of the active CL module: the standby CL
module cannot provide any connections, although its SDH/SONET subsystem
is fully operational and its utilization is controlled by performing the desired
mapping for any other services
• The capacity of the internal bypass links between the SDH/SONET subsystems
on the two CL modules, a capacity which is equivalent to two STM-1/OC-3
links. These links are used for redundancy (APS) between SDH/SONET ports
on different modules (one link for each APS group comprising STM-1/OC-3
ports on different CL modules, and for LVC path protection (in this case, only
a number of low-order VCs equal to the number of VCs protected by means
of the adjacent CL module is used), and therefore only the remaining
bandwidth can be used for bypassing. However, the flexible mapping
capabilities of the Megaplex-4100 enable full utilization of the available
bandwidth on the bypassing links.
A few topologies that illustrate applications that require independent SDH/SONET
links are presented below:
• Figure 1-3 shows a topology that enables connecting several Megaplex-4100
via SDH/SONET links to an SDH/SONET ring
• Figure 1-4 shows a topology that enables connecting a Megaplex-4100 to
two SDH/SONET rings, with the local I/O ports connected to the desired ring,
in accordance with the active CL module. The four SDH/SONET links can be
used in two main ways: the two links of each CL module can be configured as
an APS group, or a bypass can be configured between two links, one on each
CL module (in this case, Megaplex-4100 bridges traffic between the two
rings).

Note that for satisfactory performance, the two SDH/SONET rings must either
use a common timing reference (synchronous timing), or their timing sources
must be primary sources (plesiochronous timing).
• Figure 1-5 shows a topology that enables connecting several Megaplex-4100
via SDH/SONET links to two SDH/SONET rings. As in the application of
Figure 1-4, some traffic can be bridged between the two rings, and other
traffic can be directed to local I/O ports. The timing requirements described
for the application of Figure 1-4 also apply to this application.
Megaplex-4100 B
Megaplex-4100 A
STM-1/OC-3 Link 1 Link 1

SDH/SONET
Link 2 Link 2
CL-A CL-B
Megaplex-4100 C
Megaplex-4100 D
Figure 1-3. Connecting Several Megaplex-4100 Units to a SDH/SONET Backbone

via Single STM-1/OC-3 Link
Megaplex-4100
SDH/SONET Link 1 Link 1 SDH/SONET

Ring A STM-1/OC-3 STM-1/OC-3 Ring B
Link 2 Link 2
To Local Users
Figure 1-4. Megaplex-4100 Interconnecting two SDH/SONET Rings
Megaplex-4100 A
SDH/SONET STM-1/OC-3 Link 1 Link 1 STM-1/OC-3 SDH/SONET

Ring A Ring B
Link 2 Link 2
CL-A CL-B
Megaplex-4100 B Megaplex-4100 C
Figure 1-5. Connecting Several Megaplex-4100 to two SDH/SONET Rings

Instead of connecting to the SDH/SONET ring via an ADM (as in Figure 1-1),
Megaplex-4100 can be directly attached to an SDH/SONET ring, as shown in

Figure 1-6. The SDH/SONET ring carries both TDM (“legacy”) traffic, and Ethernet
traffic, with the connection to the MPLS transport network being provided by an
FCD-155E unit. The traffic reaches Megaplex-4100 through its SDH/SONET links,
and is distributed to the headquarters’ internal services network, and well as to
remotely located customer offices.
MPLS Customer Offices
FCD-155
STM-1/OC-3 FE/GbE
Control Center ETX-102/
ETX-202
FE/GbE
FCD-155E
MP-4100 RICi-4E1/4T1
FCD-155E RICi-8E1/8T1
n x E1/T1
SDH/SONET
ASMi-52
SHDSL PBX
FCD-155E
FCD-IP SCADA
E1/T1
Internal Services Voice
E1/T1
MP-2104
Figure 1-6. Megaplex-4100 in a Typical Ethernet and TDM Termination Application

This application utilizes the Megaplex-4100 Ethernet and TDM termination
capabilities to provide a flexible and scalable solution in a central access node.
Ethernet traffic reaching I/O modules with Ethernet subsystem, for example,
M8E1, M8T1, M8SL, is handled as follows:
• Megaplex-4100 TDM I/O ports can receive Ethernet traffic processed by WAN
interfacing equipment such as ASMi-52 (over SHDSL), or FCD-E1LC, FCD-IP,
(over E1/T1), etc.
In each I/O module, the bundles carrying this HDLC-encapsulated Ethernet
traffic are terminated, their payload converted back to Ethernet, and then
forwarded to the destination (CL module or another I/O module).
In addition to the encapsulated Ethernet traffic, the I/O module can also
receive Ethernet traffic via its external Ethernet ports (Figure 1-6 shows
ETX-102/ETX-202 units connected to Megaplex-4100 Ethernet I/O ports). This
traffic is also forwarded to the destination (CL module or another I/O
module).
• The I/O module Ethernet switch determines the destination of each frame in
accordance with the configured flows. The classification of each user network
is based on the VLAN ID, or on the port, if no C-VLAN ID is configured. Traffic
from locally-terminated bundles can be forwarded to local Ethernet ports, or
to CL modules, or other I/O modules.
The CL module can forward the traffic either to the I/O module handling the
traffic to the specified destination, or to one of the GbE ports (on the same
CL module, or on the adjacent module), or encapsulate the traffic for

transmission over SDH/SONET using a virtually concatenated group (for

CL.1/155GbE modules – see also the application of Figure 1-8.
As in the application of Figure 1-1, a single CL.1/155 or CL.1/155GbE module is
required. However, for highest availability, two CL modules should be installed.
Figure 1-7 shows an application that provides a complete solution for corporate
communications based on Megaplex-4100 equipment. In this application,
Megaplex-4100 units are used both as STM-1/OC-3 add/drop multiplexers in the
backbone network, and as terminal multiplexers located at each service location.
The application of Figure 1-7 can be expanded to include access to packet
switched networks, for example, Internet or metropolitan Ethernet networks: this
is achieved by installing CL.1/155GbE modules, which provide Ethernet and GbE
links, in the Megaplex-4100.
Figure 1-8 shows a typical access node application for a Megaplex-4100 equipped
with CL.1/155GbE modules.
CPE
SDH/
SONET
Central Site
STM-1/
OC-3
MP-4100 STM-1/OC-3
E1/T1/SHDSL MP-4100
MP-4100
E1/T1
PSTN STM-1/OC-3
Ring CPE
MP-4100 E1/T1
STM-1/OC-3
FCD-155
E1/T1/SHDSL
MP-4100
POP
MP-4100 E1/T1
STM-1
DXC-10A/30
Figure 1-7. Single Node Corporate Solution

Figure 1-8. Single Node Corporate Solution Expanded to Provide PSN Access
In the application of Figure 1-8, Megaplex-4100 has an Ethernet termination
capacity of 1 Gbps, that is, Ethernet users connected to the Megaplex-4100 I/O
modules can get a total bandwidth of up to 1 Gbps on the external GbE links. This
capacity can be distributed over up to four GbE links, or up to two GbE links with
redundancy protection. However, Megaplex-4100 can provide a total bandwidth
of 2 Gbps on its GbE links, where 1 Gbps is provided to the internal I/O modules,
and an additional 1 Gbps is provided to other equipment. This capability is
illustrated in Figure 1-9:
• The connection to the PSN is provided by the two GbE ports on one of the CL
modules, for a total capacity of 2 Gbps. The internal GbE switch of this CL
module is used to distribute up to 1 Gbps of the Ethernet traffic to the
internal I/O modules (each module can get up to 100 Mbps via the internal
Fast Ethernet buses connecting it to the CL modules).
• In addition to the internal flows from this CL module to the I/O modules, an
additional flow can be configured between one of its GbE ports, and a GbE
port on the other CL module (actually, several flows can be configured, as
long as the total bandwidth does not exceed the capacity of the GbE bypass
link between the two CL modules, which is 1 GbE). The external GbE ports of
the other CL module are then connected to the other equipment.
Megaplex-4100 Megaplex-4100
GbE1
PSN GbE1
GbE2 GbE2
CL-A CL-B
Figure 1-9. Higher Capacity Connection to PSN

The CL module connecting to the PSN can be equipped with long-haul optical
SFPs, whereas the other CL module can have copper interfaces, for connection to
local equipment (for example, to another Megaplex-4100, which can then also
use copper interfaces for its GbE ports).
The modular, distributed architecture of the Megaplex-4100 chassis enables
redundancy at different levels of the network, and provides a resilient system
with no single point of failure. CL.1/155 and CL.1/155GbE modules provide
STM-1/OC-3 links with automatic switchover between the two links for 1+1
unidirectional protection against network or cable failure, and in addition can
provide path protection for selected services. The GbE links can also be protected
by configuring 1+1 bidirectional protection.
The single-node solution illustrated in Figure 1-7 can also be used even when
some corporate locations use North American standards, and other locations use
the European, as shown in Figure 1-10:
• The network side of the Megaplex-4100 can be configured to use either SDH
or SONET links
• M8E1 modules are used at the SDH side, and M8T1 modules are used at the
SONET side
• The CL modules automatically perform companding law conversion (A-law to
μ-law, and vice versa) for voice channels.
MP-4100 MP-4100 European

US Offices Offices
STM-1/OC-3 International STM-1
84×T1 SDH/SONET 63×E1
Network
Figure 1-10. Multinational Solutions

Megaplex-4100 can also be used in SNCP applications, as shown in Figure 1-11. In
this application, Megaplex-4100 are inserted in the subnet ring, which provides
SNCP for the main ring.
ADM ADM
Figure 1-11. Megaplex-4100 in Typical SNCP Application

Main Features
The services supported by the modules offered for Megaplex-4100 include:
• PDH access: E1/T1 and fractional E1/T1 level, including access over 2-wire
SHDSL, with up to 80 E1/T1/SHDSL ports per chassis
• Data services: 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), optical multiplexing, and
n×64 kbps high speed data (up to 2.048 Mbps for E1 environments, or up to
1.544 Mbps for T1 environments)
• Voice services: analog and digital voice (up to 2400 voice channels per chassis
for E1 ports, up to 1920 voice channels for T1 ports), and support for special
services such as omnibus and party lines. Voice channel processing can
include A/μ companding law conversions, and user-defined signaling
translations.
• SDH/SONET services: up to four separately configurable STM-1 or OC-3 links
per node, and support for 1+1 unidirectional APS (Automatic Protection
Switching) per ITU-T Rec. G.842 for line redundancy.
• Ethernet Layer 2 services complying with Metro Ethernet Forum (MEF)
specifications, supported by 10/100 Mbps Ethernet ports and Ethernet
switches on M8E1, M8T1, M8SL, MPW-1, OP-108C, OP-106C and ASMi-54C I/O
modules, and GbE ports and Ethernet switch with classifier 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, with support for 1+1 bidirectional redundancy for pairs of
ports. Megaplex-4100 can provide Ethernet traffic termination for transport
over E1, T1, SHDSL, and low-order SDH/SONET VC-12/VC1.5 virtual
containers, and can also serve as Ethernet access concentrator with GbE and
virtually concatenated group uplinks.
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, Megaplex-4100 supports 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.
The current SDH/SONET transport options include STM-1 or OC-3 links (the link
standard being user-selectable), with independent mapping for each link, and
configurable bypassing between links. Support for standard SFP optical
transceivers for the SDH/SONET link interfaces (copper interfaces are also

available) enables selecting the optimal interface for each application.

High-performance SFPs available from RAD can achieve ranges up to 80 km/50
miles.
The 10/100 Mbps Ethernet ports on the I/O modules, and the GbE ports on the
CL modules, may be equipped with optical SFPs, or ordered with copper
interfaces.
The Megaplex-4100 SDH/SONET subsystem can be configured as a terminal (TM)
or add/drop (ADM) multiplexer, and it supports ring topologies, 1+1 unidirectional
multiplex section protection (MSP) with automatic protection switching (APS) for
the STM-1/OC-3 level, and path (SNCP) protection for the E1/T1 level. Protection
switching occurs within less than 50 msec.
Internal signal routing is performed by a built-in non-blocking 4/1/0 cross-connect
matrix. The matrix supports DS0/DS1 cross-connect with a capacity of 80 E1/T1
for the internal ports (160 Mbps equivalent bandwidth), and in addition also
supports 63 E1 links towards the SDH interfaces, or 84 T1 links towards the
SONET interfaces. This matrix can therefore directly perform TDM cross-connect
from the DS0 to the STM-1/OC-3 level, and therefore can groom traffic from any
I/O channel directly to any aggregated link, including the STM-1/OC-3 links. For
efficient multiplexing of sub-DS0 channels, the matrix also supports split timeslot
assignment.
For applications that do not require access to SDH/SONET networks, the
Megaplex-4100 can be ordered without TDM interfaces: in this case, SHDSL ports
can be used to distribute traffic to user’s equipment located at ranges of up to
several kilometers. With this option, the Megaplex-4100 effectively serves as a
high-capacity E1/T1 digital cross-connect (DXC) unit with multiplexing capabilities.
Efficient handling of Ethernet traffic is made possible by Ethernet interfaces with
local Ethernet switches on I/O modules, and by the GbE ports and Ethernet
switches with classifier located on CL modules. The Ethernet services can operate
independently of the TDM services, however Megaplex-4100 Ethernet services
subsystem can also handle Ethernet traffic transported over TDM links, both over
PDH (E1/T1) and over virtually concatenated groups carried by SDH/SONET links.
Internal traffic forwarding is controlled by configuring flows, with classification in
accordance with VLANs.
Megaplex-4100 ability to handle a broad range of data, Ethernet, and voice
services and various network technologies in a single, compact managed node
makes it a versatile and cost-effective next-generation multiservice access node.
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. When
equipped with SDH/SONET links, Megaplex-4100 also provides traceable timing
quality and supports automatic selection of best-quality timing reference.
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.
Megaplex-4100 can be powered from AC and/or DC sources. Only a single power
supply module is required to provide power to a fully equipped Megaplex-4100,
however, for redundancy, Megaplex-4100 can be equipped with two power

supply modules. 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 support the connection of an external ringer,
for example, a Ringer-2200N/ISDN standalone unit offered by RAD.
Megaplex-4100 units, as a whole, are cooled by free air convection: air intake
vents are located on the bottom and exhaust vents are located on the top. In
addition, the power supply modules have miniature cooling fan installed on their
front panels that operate only when the ambient temperature is high.
1.2 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 user’s 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) modules. CL modules may also include optional network
interface subsystems (SDH/SONET and/or Ethernet), in accordance with the
ordered version
• 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).
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
1-12 Physical Description Megaplex-4100 Ver. 2.0

failure. Moreover, redundant modules may be inserted or removed even while the
system operates, without disrupting the traffic or degrading system performance.
Equipment Description
Figure 1-12 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.
10 I/O Modules
2 CL Modules
2 PS Modules
Figure 1-12. Typical Megaplex-4100 Enclosure, General View

Figure 1-13 shows a typical rear view of the Megaplex-4100 enclosure that
identifies the slots and their utilization. The enclosure has 14 slots:
• 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.
Megaplex-4100 Ver. 2.0 Physical Description 1-13

Slot PS-A PS-B I/O 1 I/O 2 I/O 3 I/O 4 I/O 5 CL-A CL-B I/O 6 I/O 7 I/O 8 I/O 9 I/O 10
PS-A PS-B I/O 1 I/O 2 I/O 3 I/O 4 I/O 5 CL-A CL-B I/O 6 I/O 9 I/O 10
PS-200/DC PS-200/DC HSU-12 HSU-12 M8E1 M8T1 CL-1 CL-1 M8SL
1 5 5/GbE 1 5 5/GbE
STATUS STATUS STATUS
CH TST LOS CH TST LOS L 1 2 L 1 2 L 1 2
I 3 4 I 3 4 I 3 4
1 1 N N N
5 6 5 6 5 6
K K K
2 2 7 8 7 8 7 8
ON LINE ALM ON LINE ALM
ON LINE LOS LIN K ACT ON LINE LOS LIN K ACT ETH1
3 3 ETH2
L G L G LINK ACT
4 4
TX
TX
I b I b
N E N E
5 5 K 1 K 1
RX
RX
1 1
6 6
ON LINE LOS LIN K ACT ON LINE LOS LIN K ACT
7 7 L G L G
I I
TX
TX
b b
8 8 N E N E
K 2 K 2
LINK LINK
RX
RX
2 2
9 9 1-8 1-8
VDC-IN VDC-IN S
10 10 L L H
C O C O D
ON LINE LOS L S ON LINE LOS L S
11 11 O O S
E C E C L
X K O X K O
12 12
N N
L L
I A I A LASER
- - N C N C
LASER LASER CLASS
+ 72V + 72V CLASS CLASS

K E T K E T 1
-
1 1
+ - 48V + 48V T
L
T
L
+ - 24V + - 24V AC T
E
T AC T
E H
I
H
I E
TX
TX
TX
T N N T
ON ON H H K K H
LINK LINK
RX
RX
RX
1 1 1
C C
POWER POWER A O A O
CH. CH. E E L D N L D N E
TX
AC T
TX
T AC T
TX
T A C T A C T T
ON ON 1-12 1-12 R E R R E R
H H H
LINK LINK M O M O
RX
RX
RX
2 2 L L 2
E E ACT
OFF OFF AC T E
TX
T AC T
TX
T T
H H H
LINK LINK
RX
RX
3 3 3 LINK
PS Slots I/O Slots CL Slots I/O Slots
Figure 1-13. Megaplex-4100 Enclosure, Typical Rear View
I/O Modules
Table 1-1 lists the I/O modules currently offered for the Megaplex-4100. Contact
RAD Marketing for information on additional modules that may be available for
your specific application requirements.
Note
• Some of the I/O modules (indicated by Yes in the Megaplex-2100 Compatible
Hardware column) use the same hardware as the Megaplex-2100 modules
with the same name. Note however that software updating may be required.
Contact RAD Technical Support Department for details.
• The minimum hardware and software versions of I/O modules supported by
the current Megaplex-4100 version is indicated next to each module. Contact
RAD Technical Support Department for details on other versions.
Table 1-1. Megaplex-4100 I/O Modules
Megaplex-2100
Module Description Compatible
Hardware
M8E1 Module with eight E1 interfaces and user-selectable DSU or LTU mode, and No
three 10/100 Mbps Ethernet license-controlled 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.
Includes a non-blocking full cross-connect matrix that supports direct bypassing
of timeslots and associated signaling information between the E1 links without
requiring bandwidth on the internal chassis buses for bypassing; together with
the CL module, this matrix also enables free routing of timeslots from any I/O
channel or from other module ports to any E1 timeslot.

Megaplex-2100
Hardware
M8T1 Module with eight T1 interfaces and user-selectable DSU or CSU mode, and No
three 10/100 Mbps Ethernet license-controlled ports with optical SFPs or
Includes a non-blocking full cross-connect matrix that supports direct bypassing
of timeslots and associated signaling information between the T1 links without
requiring bandwidth on the internal chassis buses for bypassing; together with
the CL module, this matrix also enables free routing of timeslots from any I/O
channel or from other module ports to any T1 timeslot.
M8SL Module with eight SHDSL interfaces, supports E1 and fractional E1 payloads, No
and three 10/100 Mbps Ethernet license-controlled ports with optical SFPs or
Each module port has an independent multi-rate SHDSL modem, supporting
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 ) and mode are user-selectable (ITU-T
Rec. G.991.2 Annex A for compatibility with North American networks, or Annex
B for compatibility with European networks).
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 Pseudowire server I/O module that provides TDM pseudowire access gateway No
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 Megaplex-4100 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).
ASMi-54C Eight-port SHDSL.bis modules with two Ethernet ports, enable transporting No
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 standalone unit offered by RAD.
All the ASMi-54C modules have eight SHDSL.bis independently configurable
external ports for SHDSL services, and two 10/100 Mbps Ethernet ports, for
packet-based services.
The module can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R)
SHDSL.bis Terminal Unit for use opposite up to 8 ASMi-54 standalone devices
or another ASMi-54C module.

Megaplex-2100
Hardware
OP-108C Dual E1 and Ethernet multiplexer, where each multiplexer operates No

independently and can operate in a link with the Optimux-108 4 E1 and
Ethernet Multiplexer standalone unit offered by RAD.
Each multiplexer is capable of transparently transporting 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 for the SDH/SONET link interfaces enables
selecting the optimal interface for each application. High-performance SFPs
available from RAD can achieve ranges up to 120 km/75 miles.
OP-106C Dual T1 and Ethernet multiplexer with characteristics similar to OP-108C, except
that it supports 4 T1 instead of 4 E1 streams.
Each multiplexer operates independently and can operate in a link with the
Optimux-106 4 T1 and Ethernet Multiplexer standalone unit offered by RAD.
LS-6N, Data sub-multiplexer modules with BERT support, provide 6, respectively 12, Yes
LS-12 synchronous or asynchronous data channels with ITU-T Rec. V.24/EIA RS-232
interfaces, each having an 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.
Current Megaplex-4100 version supports LS-6N modules with minimum
hardware version 1 and minimum software version 12; for LS-12 modules, the
minimum hardware version is 10 and the minimum software version is 9
HS-RN Low-speed data module, provides 4 synchronous or asynchronous data Yes
channels with ITU-T Rec. V.24/EIA RS-232 interfaces, each having 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. HDLC-based
end-to-end control signals are also supported.
Current Megaplex-4100 version supports HS-RN modules with minimum
hardware version 6 and minimum software version 54
HS-6N, High-speed data interface module, provides 6, respectively 12, high-speed V.35 Yes
HS-12N or RS-530/V.11 data channels, and supports the BERT function. Channel data
rates are user-selectable in the range of n×56 kbps or n×64 kbps, where n is up
to 24 for T1 operation, and up to 31 for E1 operation (maximum 1984 kbps).
Supports enhanced clock modes and BERT. Any channel can be directed to any
E1 or T1 link or internal PDH port.
Current Megaplex-4100 version supports HS-6N and HS-12N modules with
minimum hardware version 2 and minimum software version 6
HS-703 High-speed data sub-channel interface module, provides four 64 kbps Yes
codirectional ITU-T Rec. G.703 data channels.
Current Megaplex-4100 version supports HS-703 modules with minimum
hardware version 2 and minimum software version 3

Megaplex-2100
Hardware
HSF-2 Interface module for teleprotection equipment, complying with IEEE C37.94 Yes
requirements. Provides two ports with 850 nm multimode fiber interfaces, with a
capacity of up to 10 × 64 kbps per port.
Current Megaplex-4100 version supports HSF-2 modules with minimum
hardware version 4 and minimum software version 1.05
HS-S ISDN basic rate access interface module with four type “S” interfaces. Performs Yes
submultiplexing and data rate adaptation on B channels in accordance with ITU-T
Rec. I.460.
This module is intended for extension of ISDN lines over Megaplex-4100 links, and
can provide phantom feed to user's equipment.
Current Megaplex-4100 version supports HS-S modules with minimum hardware
version 6 and minimum software version 12
HS-U-6, ISDN basic rate access interface module with 6, respectively 12, type “U” Yes
HS-U-12 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's
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 modem 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.
Current Megaplex-4100 version supports HS-U-6 and HS-U-12 modules with
minimum hardware version 0 and minimum software version 3.06
VC- “Omnibus” E&M voice interface module providing four toll-quality voice Yes
4/OMNI 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 enables providing party-line service.
Current Megaplex-4100 version supports VC-4/OMNI modules with minimum
hardware version 0 and minimum software version 1.08
VC-16, Analog voice interface module, provides 16, 8 or 4 PCM-encoded toll-quality Yes
VC-8, voice channels.
VC-4 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.
Current Megaplex-4100 version supports VC-4, VC-8, VC-16 modules with

Megaplex-2100
Hardware
VC-8A, Analog voice interface module similar to VC-8 and VC-4 modules, except that Yes
VC-4A also support ADPCM.
Current Megaplex-4100 version supports VC-4A and VC-8A modules with
Common Logic (CL) Modules

Currently, the following CL models are offered:
• CL.1: common logic and cross-connect module. Provides the following
functionality:
Basic multiplexing functions up to the E1 and T1 level (including signaling
processing, user-defined signaling format translations, companding law
conversions (A-law to μ-law, and vice versa), etc.)
1/0 cross-connect functionality
Nodal timing for TDM ports
Ethernet services: only for M8E1, M8T1, M8SL modules with enabled
Ethernet ports. Support only for bundles from local Ethernet ports
terminated on the TDM ports of the same module
Management access via the local serial and Ethernet ports, and inband
management via dedicated management timeslot over E1, T1 or SHDSL
ports.
A Megaplex-4100 equipped with CL.1 modules (see functional block diagram
in Figure 1-14) can replace Megaplex-2100 units (and other equipment from
the Megaplex-2100 family) in applications that require higher port capacity
and enhanced transport of Ethernet traffic over E1, T1, and SHDSL
infrastructure.
• CL.1/155: common logic and cross-connect module with two STM-1/OC-3
links, includes a complete SDH/SONET traffic handling subsystem. Offers
expanded functionality beyond that of the CL.1 module, as follows:
Selectable link standard (SDH or SONET)
Multiplexing functions up to the SDH/SONET level
SDH/SONET terminal and add/drop multiplexer functionality
1+1 unidirectional APS (Automatic Protection Switching) per ITU-T
Rec. G.783 for SDH/SONET line redundancy
4/1/0 cross-connect functionality
Independent SDH/SONET timing subsystem, and extended nodal timing
for all the ports (including PDH and SDH/SONET ports)
Ethernet services: same as for the CL.1 module

Management access: all the options available for the CL.1 module, and in
addition inband management via the DCC over SDH/SONET links.
A Megaplex-4100 equipped with CL.1/155 modules (see functional block
diagram in Figure 1-16) supports E1 and T1 links, and in addition serves as a
SDH/SONET multiplexer, with enhanced transport of Ethernet traffic over E1,
T1, and SHDSL infrastructure.
• CL.1/GbE: common logic and cross-connect module (see functional block
diagram in Figure 1-15) with two GbE links for connection to packet switched
networks. This CL module version provides the same TDM services as the CL.1
module, and in addition includes an Ethernet traffic handling subsystem
complying with Metro Ethernet Forum (MEF) specifications for providing
Ethernet Layer 2 services. The forwarding of Ethernet payload within the
Megaplex-4100 is configured by defining flows (a generic type of Ethernet
virtual connections). The current Megaplex-4100 version supports E-line flows
(an E-line is a type of Ethernet virtual connection that interconnects exactly
two bridge ports and functions as a virtual bridge). CL.1/GbE modules support
the following types of bridge ports:
External Ethernet ports of I/O modules, and bundles configured on TDM
ports of I/O modules
External GbE ports of CL.1/GbE modules, for a maximum of 4 GbE links per
Megaplex-4100, and a total transport capacity up to 2 Gbps. To enhance
availability, pairs of GbE ports can be configured to use 1+1 bidirectional
protection.
A Megaplex-4100 equipped with CL.1/GbE modules supports Ethernet bundles
and E1, T1, and SHDSL links, and it provides Ethernet gateway services for
Ethernet traffic from I/O modules (either from the Ethernet ports, or
transported by bundles over E1, T1, and SHDSL infrastructure) toward the
packet switched network.
• CL.1/155GbE: common logic and cross-connect module with two STM-1/OC-3
and two GbE links. This module includes both SDH/SONET and Ethernet traffic
handling subsystems.
Therefore, a Megaplex-4100 equipped with CL.1/155GbE modules (see
functional block diagram in Figure 1-17) provides all the services supported
by CL.1/155 and CL.1/GbE modules, and in addition supports low-order
(VC-12/VT1.5 and VC-3), and high-order virtual concatenation (VC-4 or
STS-1), with multiple virtually concatenated groups per SDH or SONET link
respectively (up to eight low-order virtually concatenated groups). Each
virtually concatenated group can be used as a virtual bridge port. Both GFP
and LAPS encapsulation are supported, with or without LCAS.
Note
In this manual, the generic term CL module is used when the information is
applicable to all the CL models. The complete module designation is used only for
information applicable to a specific model.
All the CL module models provide the following main management functions:
• Control over all the aspects of Megaplex-4100 system operations, including
the system timing aspects.

• Interfacing with the supervision terminal and other management systems

(Telnet hosts, SNMP-based management stations and Web browsers).
• Storage of application software, which determines the Megaplex-4100
capabilities and features. This software is stored in flash memory, and
therefore can be remotely downloaded and updated through the
management link without taking the equipment off-line.
• Storage of configuration databases. This information is stored in non-volatile
memory. The configuration databases can also be uploaded and downloaded
through the management link.
• Collection of operational history (alarms, performance statistics, etc.).
Only one CL module is necessary per chassis, however the chassis has two slots
dedicated to this type of module. The second slot can be used to install a
redundant CL module of the same type, thereby providing a hot-standby
capability for the Megaplex-4100 system control functions.
Power Supply (PS) Modules

The Megaplex-4100 chassis can use both AC and 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 when
a higher voltage is required (for example, for ISDN modules), it must be
provided by an external source.
• AC-powered module, PS/AC: 200W power supply module, operates on
110 VAC and 230 VAC, 50/60Hz (nominal voltage is marked on the module
panel). When a phantom feed voltage must be supplied, it is always
necessary to use an external voltage source.
The recommended external feed and ring generation voltage source is the
Ringer-2200N/ISDN standalone unit offered by RAD.
The Megaplex-4100 chassis has two PS slots, thereby enabling the installation of
two PS modules. Normally a single PS module per unit is sufficient.
However, a second PS module may be added, for redundancy: both modules must
be of the same type (either standard, or low power), however it is allowed to
install an AC-powered and a DC-powered module. With a redundant PS module,
both modules are connected to power and share the load when the system is
operating. In case of failure or loss of input power, the remaining module
continues to supply the power alone. Switch-over is thus automatic and does not
disturb normal operation.

1.3 Functional Description

As shown in Figure 1-13, 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.
The bus subsystem on the backplane uses a dual-star topology, which comprises
two essentially identical sets of buses, each using a star topology (one star to
each CL module). The buses included in the backplane bus subsystem have the
following main functions:
• PCM buses: carry E1 and T1 TDM traffic between the I/O modules and each of
the two CL modules. The PCM buses use a star topology, in which each I/O
module is connected by 6 buses, each operating at 8 Mbps, to both CL
modules.
This results in a total TDM capacity of 24 × 32 timeslots per I/O module.
• Fast Ethernet data buses: carry Ethernet traffic between the I/O modules and
each of the two CL modules. The PCM buses use a star topology, in which
each I/O module is connected by 2 buses to each CL module.
The total payload bandwidth per I/O module is 100 Mbps. However, when
evaluating the bandwidth available to Ethernet payload generated by an I/O
module, this bandwidth should be interpreted as an average bandwidth; the
peak traffic handling value may be higher, considering the statistical
characteristics of the Ethernet traffic reaching the I/O module ports, and the
effects of activating the flow control option (independently configurable for
each external Ethernet port of an I/O module).
• Timing buses: Megaplex-4100 has a dual timing bus system that has two
functions:
Carry reference signals from the I/O modules and the SDH/SONET
subsystem to the timing subsystem
Carry nodal clock signals from the timing subsystem to all the other
modules.
• Control buses. The control buses carry control signals from the management
subsystem of each CL module to each I/O module installed in the chassis, and
transfer status and monitoring data from the I/O modules to the
management subsystem.
In addition to these sets of buses, the CL modules are interconnected by two
additional types of buses:
• GbE bus for exchanging Ethernet traffic, and for traffic protection
• STM-4/OC-12 bus for SDH/SONET traffic protection.
Megaplex-4100 Ver. 2.0 Functional Description 1-21

System Functional Block Diagrams

The functions available from a Megaplex-4100 chassis depend on two factors:
• The type of CL modules installed in the chassis. The capabilities of each type
of CL module are described in the Common Logic (CL) Modules section on
page 1-18.
• The types of I/O modules installed in the chassis.
The resulting functionality is described by means of functional block diagrams:
• Figure 1-14 shows the functional block diagram of a Megaplex-4100 unit
equipped with CL.1 modules
Megaplex-4100
I/O Subsystem CL.1
I/O Module
PCM
TDM Buses
Cross-Connect
I/O DS0
Matrix
Ports DS0
Cross-Connect
Cross-Connect
Timing
Buses
DS0
Timing CLOCK
Cross-Connect
Subsystem
10
1 2
Power Suppy Control and Status

Subsystem
AC DS0
or Power Supply Management
Cross-Connect
DC Module Subsystem
Power
ETH DCE ALARMS

CONTROL
Figure 1-14. Functional Block Diagram – Megaplex-4100 with CL.1 Modules

• Figure 1-15 shows the functional block diagram of a unit with CL.1/GbE
modules
• Figure 1-16 shows the functional block diagram of a unit with CL.1/155
modules
• Figure 1-17 shows the functional block diagram of a unit with CL.1/155GbE
modules
1-22 Functional Description Megaplex-4100 Ver. 2.0

Megaplex-4100
I/O Subsystem CL.1/GbE
Ethernet Traffic Subsystem

ETH1 Fast
Ethernet
ETH ETH2 Buses
I/O Ethernet
Ports ETH3 Switch GbE Ethernet GbE
GbE Ethernet Ports
Switch
Switch
Ethernet
Termination
and
Processing
I/O Module
PCM
TDM Buses
Cross-Connect
I/O Matrix DS0
Ports DS0
Cross-Connect
Cross-Connect
Timing
Buses
DS0
Timing CLOCK
Cross-Connect
Subsystem
10
2
1
Power Suppy Control and Status

Subsystem
AC DS0
or Power Supply Management
Cross-Connect
DC Module Subsystem
Power
ETH DCE ALARMS

CONTROL
Figure 1-15. Functional Block Diagram – Megaplex-4100 with CL.1/GbE Modules

Megaplex-4100
I/O Subsystem CL.1/155 SDH/SONET Subsystem
EX Port
PCM
Buses LO/HO
PDH LO/HO
Cross- SDH/
DS0 PDH
Mapper Cross-
Connect SONET Links
DS0
Cross-Connect Mapper Connect Interface
Cross-Connect
TDM I/O Module

Timing
I/O (same as Buses
Ports Figure 1-14)
DS0 CLOCK
Timing
Cross-Connect
Subsystem
10
2
1
Control and Status
Power Suppy
Subsystem
DS0
Management
AC Cross-Connect
Power Supply Subsystem
or
DC Module
Power
ETH DCE ALARMS

CONTROL
Figure 1-16. Functional Block Diagram – Megaplex-4100 with CL.1/155 Modules
Megaplex-4100
I/O Subsystem CL.1/155GbE
Ethernet Traffic Subsystem
GbE
Fast Ports
Ethernet
Buses 1 Encapsulation
GbE
GFP
Ethernet
ETH1 VCAT
Switch
ETH ETH2 Mapper
I/O
LAPS
Ports ETH3
8
VCG 1
to
VCG 8 SDH/SONET Subsystem
I/O Module EX Port
(same as PCM LO/HO
Figure 1-15) Buses LO/HO SDH/
PDH Cross-
DS0 PDH Cross- SONET Links
DS0 Mapper Connect
Cross-Connect Mapper Connect Interface
Cross-Connect
TDM
I/O Timing
Ports Buses
DS0 CLOCK
Timing
Cross-Connect
Subsystem
10
2
1
Control and Status

Power Suppy
Subsystem
AC DS0
Management
or Power Supply Cross-Connect
Subsystem
DC Module
Power
ETH DCE ALARMS

CONTROL
Figure 1-17. Functional Block Diagram – Megaplex-4100 with CL.1/155GbE Modules

A Megaplex-4100 system may include some, or all, of the following main

subsystems:
• I/O subsystem: provides interfaces to the user’s equipment. See list of I/O
modules and their main characteristics in Table 1-1. You can find functional
descriptions of the I/O modules in their Installation and Operation Manuals.
• DS0 cross-connect matrix: handles the TDM traffic. The matrix also handles
the signaling information associated with TDM traffic.
• SDH/SONET subsystem (CL.1/155 and CL.1/155GbE only): includes the circuits
needed to interface to an SDH/SONET network:
PDH mapper: handles the TDM traffic directed to the network, and
enables mapping any E1 or T1 port to any VC-12, respectively VT1.5.
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. Supports an expansion (EX) port, an option
not used in the current version.
SDH/SONET interfaces: provide the physical interfaces for the SDH/SONET
links.
• Ethernet traffic handling subsystem (CL.1/GbE and CL.1/155GbE only):
includes the circuits needed to interface to a packet-switched network. The
Ethernet traffic handling subsystem located on CL.1/GbE and CL.1/155GbE
modules includes:
GbE Ethernet switch: controls the forwarding of Ethernet traffic within
the Megaplex-4100, including forwarding from internal ports (bundles,
and for Megaplex-4100 with CL.1/155GbE modules – also virtually
concatenated groups) to external Ethernet ports
GFP or LAPS encapsulation, and group mapper (CL.1/155GbE only):
handles 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.
In addition to the Ethernet traffic handling subsystem components located on
the CL.1/GbE and CL.1/155GbE modules, I/O modules with Ethernet ports (for
example, M8E1, M8T1, M8SL) also include a local Ethernet handling
subsystem (its functional block diagram is included in Figure 1-15). This
subsystem includes:
Ethernet port interfaces: provide 10/100 Mbps physical interfaces for
external Ethernet links.
Layer 2 Ethernet switch: provides the local Ethernet classification and
switching functions.
Fast Ethernet data ports, used only when CL.1/GbE or CL.1/155GbE
modules are installed in the chassis: each port connects to the Ethernet
traffic handling subsystem of one CL module.

When neither CL.1/GbE, nor CL.1/155GbE modules, are installed in the

chassis, Ethernet traffic can flow only between Ethernet ports and E1/T1
ports of the same I/O module.
Ethernet termination and processing: provides the interface between the
Layer 2 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 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 The Ethernet termination and processing function can also serve Ethernet traffic
carried through PDH ports of CL.1/155GbE modules.
For a detailed description of I/O module Ethernet traffic handling subsystem,

refer to the corresponding I/O module Installation and Operation Manual.
• 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.
• 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.
• 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.
DS0 Cross-Connect Matrix
Handling the Payload of I/O Modules

The DS0 cross-connect matrix provides fully non-blocking 1/0 cross-connect
among I/O modules. This matrix operates in coordination with the cross-connect
matrices located on most types of I/O modules.
For CL.1/155 and CL.1/155GbE, fully non-blocking 1/0 cross-connect is also
supported among any combination of I/O module ports and virtual PDH ports of
the SDH/SONET subsystem, as described in the Handling of CAS Information
section below.
Note
In Megaplex-4100 with CL.1/155 and CL.1/155GbE modules, the operation of the
DS0 cross-connect matrix is fully coordinated with the operation of the LO/HO
cross-connect matrix, resulting in fully non-blocking 4/1/0 cross-connect.
The DS0 cross-connect matrix has a capacity of 240 × 32 DS0 (64 kbps timeslots)
for the I/O side, and therefore it supports the maximum number of E1 and T1 I/O
ports that can be installed in the Megaplex-4100 (80 when the chassis has 10
modules), and can also be used to route the associated signaling.

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
framing, T1 ports with SF or ESF framing, and for the inband management
timeslot. The traffic associated with ISDN ports 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, with A-law companding for
E1 ports and μ-law companding for T1 ports. Therefore, such timeslots
undergo conversion when transferred between ports with different standards
(E1 versus T1). The conversion is performed on the CL module.
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 user’s 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). See the Unidirectional Broadcast Function
section below.
Megaplex-4100 enables the user to individually route each timeslot. However, a
more efficient timeslot connection mode is also supported: a user-specified
group of consecutive timeslots can be cross-connected by specifying for the
source port the starting timeslot and the number of timeslots to be connected,
and the starting timeslot for the destination port. The same is true for a group of
consecutive cross-connected timeslots: they can also be disconnected as a group.
Cross-Connect Modes
The DS0 cross-connect matrix supports two cross-connect modes, 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. In the DS0 cross-connect mode, Megaplex-4100
enables connecting payload and signaling between E1 to T1 ports; it also
enables connecting timeslots between E1 ports and SONET PDH ports, and
between T1 ports and SDH ports.
• DS1 cross-connect mode – this cross-connect mode is used when it is
necessary to transparently transfer whole E1 or T1 streams. This is needed
for unframed streams, and for streams using proprietary framing; for E1
streams, it can also be used with ports using the basic G.704 framing mode
(G.732N and G.732N-CRC4) to transparently transfer all the payload timeslots
to a single destination. In the DS1 cross-connect mode, E1 ports can be

mapped only to other E1 ports (including SDH PDH ports), and T1 ports can
be mapped only to to other T1 ports (including SONET PDH ports).
Handling of CAS Information

When CAS is used, 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 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 the voice
interface modules installed in the Megaplex-4100, or by digital PBXs or local
exchange trunks connected by E1 or T1 trunks to one of the E1 or T1 ports of the
Megaplex-4100.
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.
Megaplex-4100 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.
For this purpose, 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). In addition to the translation of
individual bits, the receive path conversion section can also be used to define 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, and therefore
each port, and even individual timeslots of a port, can 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.
Handling of PDH Port Payload

The cross-connect matrix of CL.1/155 and CL.1/155GbE modules also controls the
routing of payload carried by the PDH ports of the SDH/SONET subsystem located
on the same module. Note that when two CL.1/155 or CL.1/155GbE modules are
installed in the chassis, only the cross-connect matrix of the active (online) CL
module provides the cross-connect functions, and therefore only PDH payload
from the SDH/SONET links of the online CL module can be used.
For the PDH ports, the cross-connect matrix supports the two cross-connect
modes described above, DS0 and DS1 (the cross-connect mode is selectable at
the level of the individual PDH port). The main difference is that PDH ports
cannot operate in the unframed mode: therefore, in the DS1 mode the
cross-connect matrix is used to transparently transfer all the payload timeslots of
a PDH port to a single destination.

The result is that the following services are available for the traffic flowing
through the PDH ports:
• Services related to the TDM traffic:
Connection of timeslots from I/O ports (channels) or virtual ports of other
modules installed in the Megaplex-4100 to the desired PDH port. When
using channel-associated signaling (CAS), the matrix also routes the
signaling information associated with each channel in parallel with the
channel data.
Bypassing timeslots among the PDH ports, or among ports located on
other modules and the PDH ports located on the CL module.
Unidirectional routing of timeslots, and broadcasting from one timeslot to
multiple destinations.
In addition to payload routing, the cross-connect matrix is also used to
activate local and remote loopbacks at the timeslot level on the CL PDH ports
(loopbacks should not be activated on timeslots assigned to bundles).
• Connection of Ethernet payload (received from other I/O modules) to virtual
ports, called bundles, defined on the local PDH ports.
Full Timeslot versus Split Timeslot Assignment

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 low-speed data modules and by ISDN
modules (see corresponding module Installation and Operation Manual).
The split timeslot assignment is performed in coordination with the modules
having sub-DS0 ports. It is not possible, nor practical, to mix bits from different
modules in the same DS0 timeslot.
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.
When using the unidirectional broadcast mode, it is necessary to instruct each
port how to handle the traffic flow and signaling information. This is performed
by defining the timeslot type. For regular bidirectional channels, the timeslot
types are data, voice, and management. The additional selections available for
the unidirectional broadcast mode are as follows:

• Unidirectional broadcast – data: the timeslot is handled as a data channel.

This means that any signaling information associated with the channel is
ignored.
• Unidirectional broadcast – voice: the timeslot is handled as a voice channel.
This means that:
1. 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.
2. The signaling information of the channel is routed (automatically) in
parallel with the channel payload.
The unidirectional broadcast capabilities depend on the module type:
• Modules with E1 and T1 ports ( for example, M8E1, respectively M8T1
modules): 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: not all the modules can 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-16/8/4 voice modules with E&M
interfaces, or by HS-12/6 or HS-R data modules; ISDN interface modules
cannot support this capability.
For I/O modules, the user can specify the operating mode of each
unidirectional channel either as unidirectional transmit, or unidirectional
receive:
Unidirectional transmit: the I/O channel transmits, but cannot receive (its
receive path is disconnected). The information transmitted by the channel
can be routed to any number of other compatible ports in the same
Megaplex-4100 chassis, as well as to E1 or T1 ports for distribution to
multiple remote Megaplex-4100 units.
Only one timeslot is required on the internal PCM buses for each I/O
channel using this mode, because each destination port extracts the
payload from the same bus timeslot.
The selection of the destination timeslot at each of the other ports
connected to a unidirectional transmit channel is made during the
configuration of timeslot utilization at each destination.
Unidirectional receive: the I/O channel receives, but cannot transmit (its
transmit path is disconnected). The user can select the source port (E1,
T1 or compatible I/O port) from which the channel receives, and the
specific timeslot. The same source port or bundle can be connected to
several channels operating in the unidirectional receive mode.
SDH/SONET Subsystem (CL.1/155 and CL.1/155GbE)

Figure 1-18 shows the functional block diagram of the complete SDH/SONET
subsystem, as integrated within the CL.1/155 modules. Figure 1-18 also presents

the APS and path protection connections between two CL.1/155 modules, and
the connections to the PCM and timing buses in the Megaplex-4100 chassis.
CONTROL ETH CONTROL DCE
CL.1/155 A
Management Subsystem
Mapping Network Interface

EX Port Interface EX
(Not Used)
63 E1/84 T1
PCM
Buses STM-1 or OC-3
Dual Framer
LO
DS0 (STM-1 or STS-3)
(VC-12/VT1.5/ Port 1 LINK 1
Cross- E1/T1 E1/T1 and
VC-3)
Connect Framer Mapper HO (STS-1)
Cross-Connect
Matrix Cross-Connect
Matrix
Matrix
Port 2 LINK 2
Clock Signals
Timing APS PDH SDH/SONET
Buses
Timing CLOCK
Subsystem
Timing
CLOCK
Subsystem
PDH SDH/SONET
Clock Signals
Mapping Network Interface

APS
63 E1/84 T1 (Not Used)
PCM
Buses STM-1 or OC-3
Dual Framer
LO
DS0 (STM-1 or STS-3)
(VC-12/VT1.5/ Port 1 LINK 1
Cross- E1/T1 E1/T1 and
VC-3)
Connect Framer Mapper HO (STS-1)
Cross-Connect
Matrix Cross-Connect
Matrix
Matrix
Port 2 LINK 2
CL.1/155 B
CONTROL ETH CONTROL DCE
Figure 1-18. Megaplex-4100 SDH/SONET Subsystem

CL.1/155GbE modules have a similar SDH/SONET subsystem, which is integrated
with the Ethernet traffic subsystem (see Figure 1-20), and in addition have a

virtual concatenation subsystem, explained in Using Virtual Concatenation

(CL.1/155GbE) section.
The SDH/SONET subsystem includes the following main sections:
• Network interface, comprising:
Network port interfaces
SDH/SONET framers and high-order (HO – STS-1) cross-connect matrix.
• Mapping section, comprising:
E1/T1 framers
E1/T1 mapper
Low-order (LO – VC-12/VT1.5/VC-3) cross-connect matrix.
• SDH/SONET timing subsystem.
For Megaplex-4100 equipped with two CL.1/155 or CL.1/155GbE modules, both
SDH/SONET subsystems are active: they operate independently of other CL
module subsystems that are switched to standby on the inactive (off-line) CL
module (although only the cross-connect matrix of the online CL module provides
service – see the Handling of PDH Port Payload section on page 1-28).
SDH/SONET Network Port Interfaces

Each CL.1/155 or CL.1/155GbE module has two STM-1/OC-3 ports. 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 in case abnormal conditions may cause damage or
performance degradation.
For safety, Megaplex-4100 uses automatic laser shut-down (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, whereas if the receive signal reappears the
transmitter remains (normal operation).
SFPs are hot-swappable, and can be replaced in the field. This enables upgrading
the network port interface characteristics as network topology changes.
SDH/SONET Framer Subsystem and HO (STS-1) 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
framers also handle the routing of the payload between the two CL modules, via
the automatic protection switching (APS) bus.

The STS-1 cross-connect matrices in the two CL.1/155 and CL.1/155GbE modules,
which are integrated with the SDH/SONET framers, provide the functions needed
to route the high-order payload in the SONET mode.
Note
The additional expansion port, terminated in the EX port, is not used in this
Megaplex-4100 release.
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.
The following network interface operating modes can be configured, depending
on the hardware installed in the Megaplex-4100:
• When a single CL.1/155 or CL.1/155GbE module is installed, it is possible to
use the two ports of the installed module in one of the following ways:
As two independent ports, to provide more bandwidth on the links to the
SDH/SONET network, or for connection to an SDH/SONET ring
Configure the two ports as a protection group, where at any time one
port serves the working link and the other serves the protection link.
• When two CL.1/155 or CL.1/155GbE modules are installed, a total of four
SDH/SONET ports are available. When protection of SDH/SONET links is not
required, each SDH/SONET port in the chassis can be independently used,
provided a few restrictions are observed:
The total number of E1s or T1s that can be connected to local I/O ports is
63 for SDH interfaces, and 84 for SONET interfaces. These E1s or T1s are
always taken from the SDH/SONET links of the active CL module
The capacity of the internal bypass links between the SDH/SONET
subsystems on the two CL modules is not exceeded.
However, it is also possible to activate APS on pairs of two ports, as
explained in the CL Module Redundancy section starting on page 1-58). Each
pair can provide one fully protected link, for example, for a terminal
multiplexer application.
SDH/SONET Link Protection Mechanisms

Megaplex-4100 units with at least two SDH/SONET links support the 1+1
MSP/APS (multiplex section protection with automatic protection switching)
physical layer protection mechanism. This mechanism can be activated on links on
the same CL.1/155 or CL.1/155GbE module, as well as between links on different
CL.1/155 or CL.1/155GbE modules (see the CL Module Redundancy section
starting on page 1-58).
The mechanism provides single-ended protection (also called unidirectional
protection for SDH, and unidirectional linear protection switching for SONET), for
the connection to the SDH/SONET network.
The reason the protection mode is called unidirectional is that each of the two
units at the end of the multiplex section can switch to protection after detecting
a signal failure or degradation, without any handshaking with the other end.
Therefore, switching to protection is fast (within 50 msec).

Although the unidirectional protection mode does not use the K1 and K2 bytes in
the STM-1/OC-3 overhead, the switching end will update the K1 and K2 bytes
sent to the network, to indicate the actual protection switching status.
The APS bus interconnecting the two SDH/SONET framers is capable of carrying
the full traffic load, and therefore supports both APS and path protection. The
bandwidth on the APS bus is configured with VC-12/VT1.5 granularity.
Mapping Matrix
The LO cross-connect matrix is used to perform the mapping of the traffic on the
SDH/SONET links. This is a non-blocking cross-connect matrix that controls the
mapping of payload and overhead to these interfaces. The matrix supports
low-order cross-connections (VC-12 and VC-3 for SDH links, VT1.5 for SONET
links).
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 virtual PDH
port, with user-selectable framing: each CL.1/155 or CL.1/155GbE 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:
• For E1 ports, the mapper enables mapping the port data stream to any of the
63 VC-12 in the STM-1 signal.
• For T1 ports, the mapper enables mapping the port data stream to any of the
84 VT1.5 in the OC-3 signal.
SDH/SONET Timing Subsystem

The timing subsystem of each CL.1/155 or CL.1/155GbE module generates a clean
clock signal (the S-subsystem clock signal) for use by the SDH/SONET subsystem
circuits. This signal can also be configured as reference source for the
Megaplex-4100 system timing subsystem (refer to Timing Subsystem section for
details). The functional block diagram of the SDH/SONET timing subsystem is
shown in Figure 1-19.
The SDH/SONET timing subsystem can be configured to use the following
reference sources:

• The recovered receive clock signals of the local SDH/SONET ports

• The system nodal clock
Note When the system (nodal) clock must be locked to the S-subsystem timing, never
select the system clock as reference for the SDH/SONET timing generator, or an
unstable clock will result.
• The Megaplex-4100 internal clock.

Receive Clocks
Main
from Local
SDH/SONET
Links Fallback
SDH/SONET
Main SDH/SONET
Subsystem
SDH/SONET (S-Subsystem)
Internal Timing
Reference Fallback Clock
Clock Generator
Selector
System Clock
(2048 kHz)
Figure 1-19. SDH/SONET Timing Subsystem

Two sources can be specified: a higher-priority main source, and a fallback source
used in case the main source fails. Alternatively, when using the recovered
receive clocks of SDH/SONET ports as reference sources, the SDH/SONET timing
subsystem can be configured to automatically select the best timing source in
accordance with the contents of the SSM message received from the SDH/SONET
ports (the SSM message is carried in the S1 byte of the SDH/SONET overhead). In
this case, the SSM sent by the Megaplex-4100 to the network links reflects the
quality of the selected source. This provides clock traceability.
The station clock can also be configured to serve as a clock source with traceable
quality, based on SSM in this case, the station clock must be configured as
system clock source, and the reception of SSM messages on the station clock
interface must be enabled. The system clock can then be used as reference
source for the SDH/SONET subsystem (see additional information in the Station
Timing section starting on page 1-52).
Note that automatic SSM-based selection should be used only when at least two
suitable sources are active. This minimum number can consist of two different
SDH/SONET links (this is always the case in a ring topology), or one SDH/SONET
link and one station clock interface.
Only one SDH/SONET subsystem timing reference is generated by each CL
module, because at any time only one timing subsystem is active. When two CL
modules are installed, the active module is selected to provide the reference
timing: this is the master timing source. The other CL module is automatically
used as fallback source.

Integration of SDH/SONET Subsystem with Ethernet Traffic Subsystem

(CL.1/155GbE)
Figure 1-20 shows the functional block diagram of the complete SDH/SONET and
Ethernet traffic subsystems, as integrated within a CL.1/155GbE module.
To Other CL
CL.1/155GbE Mapping APS SDH/SONET Network

Interface
(Not Used)
63 E1/84 T1
PCM Dual Framer

(STM-1 or STS-3) STM-1 or OC-3
Buses
LO and
DS0 HO (STS-1) Port 1 LINK 1
(VC-12/VT1.5/
Cross- E1/T1 E1/T1 Cross-Connect
VC-3)
Connect Framer Mapper Matrix
Cross-Connect
Matrix
Matrix
Port 2 LINK 2
Clock Signals
PDH SDH/SONET
To
Timing
Buses
Timing
CLOCK
Subsystem
Ethernet Traffic Subsystem Ethernet Mappers
Encapsulation
VCG 1
GFP
VCG
Mapper
10 Fast Ethernet GbE LAPS

Traffic Buses Ethernet VCG 8
to I/O Modules Switch
GbE Ports
(SFP Sockets
SFP or or RJ-45)
Copper GbE 1
Interface
GbE Interfaces to
Other CL.1/155GbE
SFP or
Copper GbE 2
Interface
10 Fast Ethernet Management

Management Buses Ethernet Management Subsystem
to I/O Modules Switch
LAN Serial RS-232

Interface Interface
CONTROL ETH CONTROL DCE ALARM
Figure 1-20. CL.1/155GbE Module with SDH/SONET and Ethernet Traffic Subsystem

• The interaction between the SDH/SONET subsystems located on different

CL.1/155GbE modules is as shown in Figure 1-18.
• The interaction between the two Ethernet traffic subsystems located on
different CL.1/155GbE modules is made via two internal GbE interfaces
Note For CL.1/GbE modules, the Ethernet traffic subsystem does not support virtual
concatenation, and therefore it does not include the encapsulation and virtually
concatenated group mapper (see Megaplex-4100 functional block diagram in
Figure 1-15).
The connection of Ethernet traffic from I/O modules to the CL.1/155GbE is made
through a set of 10 Fast Ethernet buses, one from each I/O slot. Another set of
Fast Ethernet buses is used for the management traffic.
The forwarding of the Ethernet traffic within the Megaplex-4100 is controlled by
the GbE Ethernet switch. For example, any Ethernet traffic between different I/O
modules uses the services of this switch.
GbE Ethernet Switch

The GbE Ethernet switch is a high-capacity Ethernet switch with classifier, capable
of handling a wide range of forwarding algorithms, and provides extensive
support for QoS features. The switch has memory-based switch fabric with true
non-blocking switching performance, and collects a wide range of performance
monitoring parameters, which can be read by management.
The Ethernet switch has 24 Fast Ethernet ports and 4 GbE 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 (see the Redundancy for PSN Connections
section starting on page 1-63 for details).
• 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 GbE switch of the other CL
module installed in the Megaplex-4100.
• Each switch 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 1600 bytes.
• The frames passed by the MAC controllers are analyzed by the ingress policy
controller of the corresponding port before being transferred, through the
switch fabric, to an internal queue 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 eight
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 switch includes a flow classification engine categorizing packets into

flows in accordance with user-defined classification rules. Multiple rules may
be applied to each flow. Classification takes place at full wire speed. The
switch recognizes standard frame types. Using this mechanism for Ethernet
services provided by Megaplex-4100 is described in the Megaplex-4100
Ethernet Services section.
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. RAD offers a wide range of SFPs covering
requirements from short-range low-cost optical interfaces to long-range,
high-performance interfaces.
This type of ports should be configured to operate without autonegotiation,
in the 1000 Mbps full duplex mode.
Flow Control Options

The user can enable flow control for the GbE 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 the 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 the 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.
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.

Forwarding Algorithms and VLAN Support

The Ethernet switch operates as a MAC bridge that automatically learns the MAC
addresses, and the port through which frames addressed to a foreign destination
are to be transmitted.
Only active MAC address/port number mappings are actually stored: after a
user-defined aging interval, inactive mappings are removed from the switch
memory.
The Ethernet switch can use both port information and the frame VLAN
information to select the ports among which traffic can be forwarded. Using only
the port information is referred to as the VLAN-unaware mode; any mode which
uses VLAN information is called VLAN-aware.
The VLAN mode can be separately selected for the customer’s edge side (toward
the I/O modules) and for the service provider side (toward the GbE ports and
virtually concatenated groups), in accordance with the specific application
requirements.
Note
In the Megaplex-4100, the switch operates in the IEEE 802.1Q shared (SVL)
learning mode.
Using Virtual Concatenation (CL.1/155GbE)

Virtual concatenation (VCAT) is available for Megaplex-4100 equipped with
CL.1/155GbE modules (see Figure 1-20). Refer to Appendix C for background
information on virtual concatenation.
The Ethernet mapper subsystem 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.
Megaplex-4100 also supports the Link Capacity Adjustment Scheme (LCAS),
covered by ITU-T Rec. G.7042.
Encapsulation Functions
Ethernet frames must be encapsulated before transport over the SDH/SONET
network. Two types of encapsulation are supported (see Appendix C for
additional details):
• 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.

The user can select the desired encapsulation mode, independently, for each
virtually concatenated group. The encapsulation parameters can also be
configured, for best performance in specific applications.
The encapsulated frames of each virtually concatenated group are applied to the
virtually concatenated group (VCG) mapper.
VCG Mapper Functions

The 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.
Note
For compatibility with equipment from other vendors, the user can configure the
mapper to simulate the use of virtual concatenation even when the group
comprises a single virtual container/SPE.
Alternatively, when a group comprises a single virtual container/SPE, the virtual
concatenation can be disabled: in this case, the Ethernet traffic from the port
connected to the mapper is assigned a whole TU/TUG on the network link.
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
8 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.
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 8
groups. For example, a group using 7 VT1.5 can be used to 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 allowed to build several virtually concatenated groups using different types
of VCs/VTs: for example, when using VC-12 to carry PDH 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 configure various LCAS protocol parameters, and can also 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.
Megaplex-4100 Ethernet Services
Ethernet Service Model

In typical applications, Megaplex-4100 enables customers connected to its ports
to access a remote service provider, or the Internet, over an Ethernet network.
The Megaplex-4100 Ethernet subsystem supports two main categories of
services:
• Ethernet gateway services: the Megaplex-4100 collects customer’s traffic
from the Ethernet ports located on I/O modules, and forwards the traffic
through the GbE ports located on CL.1/GbE or CL.1/155GbE modules toward
the service provider PoP, or to an Internet access node
• Ethernet transport services: traffic received from the Ethernet ports located
on I/O modules, and GbE ports located on CL.1/155GbE modules, is
transported over TDM links (by means of bundles over E1 and T1 links, and
virtually concatenated groups over SDH/SONET links)
The two categories are simultaneously supported, as explained below in the
Ethernet Services Subsystem section.
The service model is best described in the terms used by the Metro Ethernet
Forum (MEF), which specifies clearly-defined service standards for providing
Ethernet services over metropolitan Ethernet networks. The MEF service model,
adapted to the Megaplex-4100, is illustrated in Figure 1-21.

Ethernet Ports GbE Ports

on on
I/O Modules CL Modules
Metropolitan
Customer Ethernet
Network Network
Megaplex-4100
Customer (C) Service

Edge Provider (SP)
Edge
Figure 1-21. Megaplex-4100 as Access Node to Ethernet Services
Note The term customer’s edge refers to the physical or logical point at which
customer’s traffic is handed over to a network interface, for transport over the
network.
The service provider edge is the point at which customer’s traffic (received
through a customer’s edge network interface and processed for transport) is
handed over to a service provider access point or PoP.
MEF describes two Ethernet services types:

• E-line service: provides a point-to-point Ethernet virtual connection (EVC).
Within Megaplex-4100, E-line services can be provided between a customer
and a service provider’s PoP (Figure 1-22.A), or between two customers
(Figure 1-22.B).
Megaplex-4100
To Service
Provider (SP)
Customer’s E-Line
Equipment
(CE)
A. E-Line from Customer’s Equipment to Service Provider PoP

Megaplex-4100
Customer’s E-Line Customer’s

Equipment Equipment
(CE) (CE)
B. E-Line between two Customers

Figure 1-22. Megaplex-4100 E-Line Service Configurations
For simplicity, Figure 1-22 shows the customers connected directly to I/O
module Ethernet ports, and the link to the service provider’s PoP – directly

connected to a GbE port on a CL module. However, the connections can also

be made over bundles on E1 or T1 links (including bundles on PDH ports of CL
modules with SDH/SONET subsystems), or over virtually concatenated groups
(supported by CL module with SDH/SONET subsystems).
• E-LAN service: provides multipoint connectivity, i.e., may connect two or more
Ethernet users, in a way similar to that achieved by connection to a LAN. An
E-LAN implemented within Megaplex-4100 is illustrated in Figure 1-23.
Note The current Megaplex-4100 software revision supports only E-Line services.
Megaplex-4100
To Service
Provider (SP)
E-LAN
Customer’s
Equipment
(CE)
Customer’s Customer’s
Equipment Equipment
(CE) (CE)
Figure 1-23. Megaplex-4100 E-LAN Service Configuration
Ethernet Services Subsystem
Structure
Ethernet services are provided by means of the Megaplex-4100 I/O modules with
Ethernet ports (M8E1, M8T1, M8SL), which can serve as customer’s edge network
interfaces, and by means of the CL.1/GbE and CL.1/155GbE modules, which
provide GbE ports that can serve as service provider’s edge interfaces.
The structure of the complete Megaplex-4100 Ethernet services subsystem is
The customer’s 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:
• Bundles (a type of virtual port) defined on the local I/O module E1 or T1
ports, or on other modules with E1 or T1 ports (this includes PDH ports on
CL.1/155 and CL.1/155GbE modules).
Two types of bundles can be defined on E1 and T1 ports:
Bundles using HDLC as the Layer 2 protocol. The bandwidth assigned to a
HDLC bundle depends on the number of timeslots assigned by the user
(any even number of timeslots, up to a maximum of 30 for E1 ports, up
to 24 for T1 ports. Up to four HDLC bundles can be defined on a framed
port, where each bundle is assigned the desired fraction (number of
timeslots) of the port bandwidth, in accordance with user’s bandwidth
requirements.

An unframed E1 port supports a single HDLC bundle, which occupies the

whole port bandwidth (2048 kbps, equivalent to 32 timeslots).
PDH ports also support HDLC bundles, but CL modules do not include the
Ethernet termination subsystem needed to support Ethernet bundles:
only I/O modules with Ethernet ports (M8E1, M8T1, M8SL) have the
required subsystem. Therefore, the PDH port timeslots assigned to an
Ethernet bundle must be sent for processing to a user-selected I/O
module, via the Megaplex-4100 PCM buses, and the resulting Ethernet
traffic is returned to the CL module via the Fast Ethernet traffic bus of
that I/O module.
Fast Ethernet
Connections
I/O Module 1
(M8E1, M8T1, M8SL) CL.1/155GbE
Bundle GbE 1
TDM Ports Termination
GbE 2
(E1/T1) 1
1 VCG 1 Encapsulation, SDH/SONET
GbE Virtual
LINK 1
8 Ethernet Concatenation
Ethernet Mapper, and LINK 2
32 Layer 2 Switch
SDH/SONET
Switch Framer
ETH1 Motherboard VCG 8
ETH2
ETH3
CL.1/155GbE
GbE 1
GbE 2
VCG 1 Encapsulation, SDH/SONET

GbE Virtual
LINK 1
Ethernet Concatenation
Switch Mapper, and LINK 2
SDH/SONET
Framer
VCG 8
I/O Module 10
Figure 1-24. Ethernet Services Subsystem (Megaplex-4100 with CL.1/155GbE

Modules)
Bundles using MLPPP as the Layer 2 protocol. MLPPP 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 links to provide increased
bandwidth. For the current Megaplex-4100 version, only unframed E1
ports support MLPPP bundles, i.e., ports of M8E1 and M8SL modules; for
these modules, the user can configure the bundle to extend over any
number of E1 ports (all operating in the unframed mode), up to the
maximum supported by the module (8 ports). The bandwidth
automatically assigned to an MLPPP bundle depends on the selected
number of ports: therefore, the maximum bandwidth of an MLPPP bundle,
achieved when the bundle uses all the 8 ports of the module in the
unframed mode, is 8×2048 kbps (16384 kbps). Only one MLPPP bundle
may be active at any time on an I/O module.

The maximum number of bundles that may be defined on an I/O module

(M8E1, M8T1, or M8SL) is 32.
• Virtually concatenated groups, defined on the SDH/SONET links of CL.1/155
and CL.1/155GbE modules
• GbE ports located on the Megaplex-4100 CL.1/GbE and CL.1/155GbE modules
Each of the above-mentioned interfaces (either customer’s edge or service
provider’s edge interface) is generically referred to as a bridge port. The Ethernet
traffic flows (is forwarded) among the desired bridge ports in accordance with
user-configured rules that define Ethernet Virtual Connections (flows). The total
number of bridge ports supported by a Megaplex-4100 is 370, as follows:
• For I/O modules with Ethernet ports:
One bridge port can be defined on each Ethernet physical interface.
One bridge port can be defined on each bundle.
Therefore, the maximum number of bridge ports that can be defined on any
I/O module with Ethernet ports is up to 35 (3 bridge ports on Ethernet
physical interfaces, and 32 bridge ports defined on bundles).
• For CL modules:
One bridge port can be defined on each GbE physical interface
One bridge port can be defined on each bundle, up to a maximum of four
HDLC bundles per port
One bridge port can be defined on each virtually concatenated group
configured on an SDH/SONET port, up to a maximum of eight virtually
concatenated groups per SDH/SONET subsystem.
Using Flows to Control Ethernet Traffic Forwarding

As explained in the Ethernet Service Model section starting on page 1-41, the
forwarding of Ethernet traffic is controlled by configuring flows. A flow
interconnects at least two bridge ports, however 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.
Note An additional flow, 251, can be added to carry management traffic.
Ethernet switching occurs at Layer 2 (based on MAC addresses), and is basically

configured by first mapping bridge ports as termination points for flows, and
then specifying classification rules. Alternatively, forwarding can use only the
bridge port information (see the Forwarding Algorithms and VLAN Support section
starting on page 1-39).
A flow functions as a virtual bridge. The switching functionality is actually
distributed between the I/O module Ethernet switches, and the switches located
on CL.1/GbE and CL.1/155GbE modules, and is implemented in accordance with
the following rules:
• The I/O module Ethernet switch can handle alone local flows, i.e., flows
between local Ethernet ports and bundles located on the same module. It will
not allow E-line flows between Ethernet ports on the same module.

Whenever a flow is directed to another module, the I/O module Ethernet

switch sends the payload to the GbE Ethernet switch on the CL module via
the Fast Ethernet traffic connection.
As a result, the total Ethernet traffic handling capacity of an I/O module is a
maximum of 16 Mbps for traffic directed to local TDM ports via bundles, and a
maximum of 100 Mbps for traffic directed to other modules, that is, traffic
directed to another I/O module, to SDH/SONET ports, and/or GbE ports on
the CL modules.
Note The above-mentioned capacities should be interpreted as long-term average

capacities; considering the statistical characteristics of the customer’s Ethernet
traffic reaching the module ports, the short-term peak traffic handling value may
be much higher (because excess payload is temporarily stored in Ethernet switch
buffers), and the effects of activating the flow control option (independently
configurable for each Ethernet port).
• The CL module GbE Ethernet switch handles the flows terminated at GbE
ports, at the virtually concatenated groups on SDH/SONET links, and flows
between different modules (for example, flows between I/O modules, and
flows between the two CL modules). The CL module Ethernet switch also
allows flows between GbE ports on the same module.
The traffic between the two GbE Ethernet switches on the two CL modules
passes through two internal GbE ports; the capacity of this interconnection
ensures that there is no limitation when traffic must be transferred between
the CL modules.
The GbE Ethernet switch also enables using redundancy between the GbE
ports (refer to the Redundancy for PSN Connections section starting on page
1-63 for details). Note that when GbE port redundancy is enabled, all the
traffic is configured on the primary GbE port (no configuration can be
performed on the GbE port configured as secondary).
A flow connects only the user-mapped bridge ports, that is, transfers Ethernet
frames with user-specified characteristics only between these bridge ports and
prevents transfer of such frames to any bridge port which is not part of the same
flow (this is rather similar to what is expected of a virtual private network (VPN)).
Therefore, each flow must discriminate (be aware of) among the Ethernet frames
reaching an associated bridge port in order to determine how to handle
customers’ traffic. Although this discrimination can be made simply by defining
closed sets of ports (exactly two for the E-line service, two or more for the E-LAN
service), this approach does not permit Ethernet switching to take place. When
Ethernet switching is needed, the discrimination is mainly based on the
customer’s edge and service provider’s edge VLAN identifiers (C-VLAN ID and
SP-VLAN ID, respectively) received in each frame – a forwarding mode referred to
as VLAN-aware, and is supplemented by specifying the relevant ports. Another
forwarding mode, referred to as VLAN-unaware, is used to correctly forward
untagged frames, priority-tagged frames, and frames with unknown VLAN IDs
among user-specified ports.
The range of VLAN IDs that can be used for Ethernet traffic with IEEE 802.Q tags
is 1 to 4094.

The following configuration rules apply to flows and bridge ports:

1. A bridge port can terminate only one flow (EVC) classified as unaware (i.e.,
which does not discriminate Ethernet traffic in accordance with customer’s
and service provider’s VLANs).
2. When a bridge port is mapped to more than one EVC, the bridge port can
terminate several EVCs with specific VLAN IDs, but only one EVC classified as
unaware.
3. A bridge port can terminate any number of EVCs with specific VLAN IDs
(aware mode), up to the maximum supported per system.
4. It is not possible to configure E-line flows between Ethernet ports on the
same I/O module.
5. For E-line flows, the following VLAN assignment rules apply:
1. The bridge ports terminating an EVC (flow) must use the same VLAN
mode (either unaware or aware).
2. When using the aware mode, the same VLAN IDs must be configured at
both bridge ports. For example, this means that flows between two GbE
bridge ports must use the same SP-VLAN ID.
OAM Support
To enable personnel to identify problems in metropolitan Ethernet networks, it is
necessary to check connectivity at Layer 2 for each traffic-carrying link. For this
purpose, the standards define a link operations and maintenance (OAM) protocol.
The link OAM protocol uses special OAM protocol data units (PDUs) to check
connectivity between each bridge port and the attached equipment. The protocol
can be enabled on physical Ethernet ports, and on bundles carrying Ethernet
traffic over the TDM network: to be effective, the protocol must be enabled at
both ends of a link. For bundles, only one end can initiate the exchange of OAM
PDUs (the active endpoint), and the other (passive) endpoint only reacts to the
OAM PDUs sent by the active endpoint.
Timing Subsystem
Megaplex-4100 timing subsystem is a fully redundant system, 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. In case a problem is detected in the
active timing subsystem, the standby subsystem hitlessly takes over.
Figure 1-25 shows the functional block diagram of the timing subsystems for a
Megaplex-4100 equipped with SDH/SONET subsystems, and the connections to
the chassis timing bus.

Main CL-A
Receive Clocks
from
I/O Channels
Fallback Timing
Bus
Main to all
PDH Receive Chassis
Clocks Cards
Fallback
From Local
SDH/SONET System Transmit (System)
System Clock Timing
Subsystem (Nodal)
SDH/SONET Main Reference Bus
Selector Clock 2.048 MHz
(S-Subsystem) Interface
Generator
Clock Fallback
Internal On-Line/Standby
Clock
Input Station
CLOCK Clock
Interface
Output
Main CL-B
Receive Clocks
from
I/O Channels
Fallback
Main
PDH Receive
Clocks
Fallback
From Local
SDH/SONET System Transmit (System)
Subsystem System Clock Timing
(Nodal)
SDH/SONET Main Reference Bus
Clock 2.048 MHz
(S-Subsystem) Selector Interface
Generator
Clock Fallback
On-Line/Standby
Internal
Clock
Input Station
CLOCK Clock
Interface
Output
Figure 1-25. Functional Block Diagram of Megaplex-4100 Timing Subsystem (Unit with SDH/SONET
Subsystems)
System Timing Modes

Megaplex-4100 requires a system (nodal) clock source, and in addition it can use
separate, independent clocks for the SDH/SONET subsystem, and another for the
PDH subsystem. Therefore, for the SDH/SONET traffic a higher accuracy clock can
be provided; however, the PDH subsystem may also be synchronized to the
SDH/SONET timing.

Appropriate configuration permits hierarchical dissemination of timing throughout

the communication systems, and ensure use of reliable timing sources even in
case of transmission faults or equipment malfunctions.
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.
For flexibility, you can select master timing sources and fallback timing sources: a
fallback source is automatically selected when none of the preconfigured master
sources is capable of providing a good timing reference.
The Megaplex-4100 timing subsystem can use the following types of reference
sources:
• Internal Megaplex-4100 oscillator
• Clock signal derived from the receive clock of a specified user port, internal
DS1 port or pseudowire (Rx timing mode)
• S-subsystem clock signal, provided by the timing subsystem of the
SDH/SONET subsystems located CL.1/155 and CL.1/155GbE modules.
• Station clock, a special case of Rx timing, which uses an external clock signal
supplied to the CL module CLOCK connector
Table 1-2 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 be able of providing a timing
reference signal.
Table 1-2. 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
M8E1, M8T1 External T1 or E1 ports Not applicable
M8SL External SHDSL ports STU-R mode
MPW-1 Pseudowire ID Not for HDLCoPSN

pseudowires
OP-108C/OP-106C Internal DS1 ports Not applicable
RX Clock from HS-6N, HS-12N External ports DTE timing

Local User Port
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

RX Clock from CL.1/155, Internal T1 or E1 PDH Not applicable

Remote User Port CL.1/155GbE ports
Line (STM-1/OC-3) Signal from CL.1/155, Link port Not applicable

SDH/SONET Subsystem CL.1/155GbE
Internal Timing Mode

As listed in the Technical Specifications, the internal oscillator quality depends on
the presence of a SDH/SONET subsystem. When an SDH/SONET subsystem is
installed (CL.1/155 and CL.1/155GbE models), a higher quality internal oscillator is
used to provide a reference clock with characteristics suitable for SDH/SONET
equipment. Nevertheless, in most applications, the internal Megaplex-4100
oscillator is used mainly for maintenance purposes, because usually an external
clock source is used.
The internal oscillator is also used as a last recourse fallback source: it is
automatically selected when no master, nor fallback source is capable of
providing a good timing reference. Therefore, when you select the internal
oscillator, no fallback source can be selected.
Rx Timing Mode
In the Rx timing mode, the reference signal is derived from the receive (RX) clock
of a specified user port:
• 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 1-2.
• Megaplex-4100 units equipped with CL.1/155 or CL.1/155GbE modules also
permit locking the nodal timing to a remote user, that is, a user connected to
an internal (virtual) PDH port of the local Megaplex-4100 via the SDH/SONET
network.
Two lists of timing sources can be defined, one including master sources and the
other including fallback sources. Each list can include up to 10 different sources.
Each source port is assigned an index number in its list, which specifies its priority
relative to the other sources in the same list. The master sources have priority
over the fallback sources.
The algorithm that selects the Megaplex-4100 timing reference source is based
on these user-defined priorities, and works to automatically select the
operational port with the highest priority as the nodal timing reference. The
selection criteria are as follows:
1. Normally, Megaplex-4100 selects the operational port with the highest
available priority from the list of master sources.
2. If the currently-selected port can no longer provide a clock signal (for
example, because of loss of signal, malfunction, module replacement, etc.),
Megaplex-4100 selects the master source with the next highest priority.
3. If no master source is available, the operational fallback port with the highest
priority is selected.

The switching is revertive: whenever a timing source with a higher priority

than the current source becomes available, it is automatically selected.
4. If no operational port can be found in both the master and fallback lists, 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 fallback 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 reference, in accordance with the criteria
listed above. If a long time expires without any of the user-specified clock
sources returning to normal, Megaplex-4100 switches to the internal
oscillator.
S-Subsystem Timing Mode

In the S-subsystem timing mode, Megaplex-4100 uses the clock supplied by the
SDH/SONET timing subsystem (see details in the SDH/SONET Timing Subsystem
section starting on page 1-34).
The interaction between the system (nodal) timing generator, and the
SDH/SONET timing generator, is shown in Figure 1-26.
Local SDH/SONET Timing Subsystem

(CL.1/155, CL.1/155GbE Only)
Link Receive
Clocks SDH/SONET
SDH/SONET
Subsystem
Timing (S-Subsystem)
Internal Clock Clock
Generator
PDH
Receive
Clocks
Receive Reference System

(Nodal) System Clock
Clocks from
Timing (2048 kHz)
I/O Channels Generator
Input
CLOCK Output
Internal Clock
System Timing Subsystem

(All CL Versions)
Figure 1-26. Interaction between System (Nodal) Timing Generator and

SDH/SONET Timing Generator

The SDH/SONET timing subsystem can be configured to use as reference source

one of the following:
• A recovered receive clock signal of a local SDH/SONET link
• The internal clock
• The system (nodal) clock. The system clock itself may be locked to the station
clock (see Station Timing section below).
Note When the system (nodal) clock must be locked to the S-subsystem timing, never
select the system clock as reference for the SDH/SONET timing generator, or an
unstable clock will result.
Station Timing
In the station timing mode, the Megaplex-4100 system (nodal) timing is
synchronized to an external clock signal, supplied to the dedicated station clock
interface located on each CL module. This signal is usually provided by a
highly-accurate master clock source, 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.
When the SDH/SONET subsystem timing uses automatic source selection based
on SSM (see SDH/SONET Timing Subsystem section on page 1-34), it is possible
to include the station clock in the automatic selection scheme. For this purpose,
the user can enable the reading of SSM messages received within the station
clock signal stream (this capability is available only for the 2.048 Mbps and
1.544 Mbps options). For E1 ports, this requires to specify the national bit (one
of the Sa4 to Sa8 bits in timeslot 0) that carries the SSM message; for T1 ports, the
SSM message is carried by the FDL.
Each CL module can be connected to a separate station clock source, and
therefore each module can provide a separate reference signal. Therefore, when
both CL modules are connected to station clock sources, one can serve as master
source, and the other as fallback source.
The station clock interface has jumper-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 however 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 (see Application Considerations for Station Timing section on next
page). 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

• The Megaplex-4100 system (nodal) clock. In this case, only a 2.048 Mbps
signal can be provided (the frequency of the system clock is always
2.048 MHz).
The SSM message can be provided only by CL models with an SDH/SONET
subsystem, and is determined as follows:
When using the internal clock as the system timing reference, the SSM
message is SEC (SDH) or SMC (SONET).
When the system timing is derived from the SDH/SONET subsystem
timing, the SSM message is derived from the SSM received from the
SDH/SONET link that serves as the timing reference.
Application Considerations for Station Timing

The structure of the external clock interface provides a convenient way to
distribute clock signals to several equipment units installed in close proximity,
e.g., in the same equipment rack.
Typically, the external clock interface connectors can be simply connected in a
daisy-chain configuration, as shown in Figure 1-27. In this application, the clock
source is connected to the external clock input in the station clock interface, and
serves as the system (nodal) timing reference. The station output clock is
configured to use the system timing as reference. The clock signal appearing at
the external clock output is connected to the external clock input of the next
Megaplex-4100, and so on.
To protect the other equipment, the station clock interface has a bypass relay
that connects directly the input line to the output when the Megaplex-4100 is
not powered.
To minimize waveform degradation, it is recommended to use the RS-422
squarewave interface, and use high-quality shielded cables, as short as practical.
Note that only the first Megaplex-4100 unit receives the reference signal: the
other units receive the clock signal from the Megaplex-4100 nodal timing
subsystem, whose characteristics depend on the specific CL module model.
Station Clock Source
(GPS-Based Timing Source,
SDH/SONET ADM, etc.)
CLOCK CLOCK CLOCK CLOCK
Megaplex-4100
Figure 1-27. Clock Distribution Using the Megaplex-4100 Station Clock Interface
Another application for the station timing mode is to enable locking the timing of
an SDH/SONET ring network to a master clock, while ensuring that at any time
the ring timing uses the best quality clock available. This is achieved by using
automatic source selection based on SSM (see SDH/SONET Timing Subsystem
section on page 1-34). A typical application topology is illustrated in Figure 1-28.
In the topology of Figure 1-28, the timing references are configured as follows:
• System timing reference: for all the Megaplex-4100 units, except Unit A, the
system timing reference is configured as S-subsystem, with automatic SSM--

based selection. Unit A is configured to use the station clock as its system
timing reference (with SSM reception enabled for the station clock interfaces)
• SDH/SONET subsystem timing reference: for all the units, except Unit A, is
configured as Rx timing, using an SDH/SONET link as reference. To provide a
preferred timing flow direction within the ring, the master and the fallback
timing sources are selected in accordance with the normal payload transport
direction of the ring. Unit A is configured to use the system (nodal) clock as
reference.
Assuming that the station clock supplied to Unit A has superior timing quality, it is
selected as source and determines the timing quality of its SDH/SONET links. The
other units read the received SSM and select an SDH/SONET link as timing
reference. The resulting timing flow is illustrated in Figure 1-28.
If one of the links in the ring fails, the ring heals itself by changing the signal flow
direction. As a result, the timing reference of the links may change, but it remains
locked to the station clock supplied to Unit A.
System Timing: S-Subsystem System Timing: S-Subsystem System Timing: S-Subsystem
SDH/SONET Tx Clock: Rx Clock SDH/SONET Tx Clock: Rx Clock SDH/SONET Tx Clock: Rx Clock
Master: Link 2 Master: Link 2 Master: Link 2
Fallback: Link 1 Fallback: Link 1 Fallback: Link 1
B C D
Link 2 Link 1 Link 2 Link 1 Link 2 Link 1
SDH/SONET Ring
Link 1 Link 2 Link 1 Link 2 Link 1 Link 2
A F E
System Timing: Station System Timing: S-Subsystem System Timing: S-Subsystem
SDH/SONET Tx Clock: System SDH/SONET Tx Clock: Rx Clock SDH/SONET Tx Clock: Rx Clock
Master: Link 2 Master: Link 2
Fallback: Link 1 Fallback: Link 1
Station
Clock Source
Legend
STM-1/OC-3 Subsystem
CL Module
Normal Timing Flow
Main Path
Alternative Path
Figure 1-28. SDH/SONET Ring Using Station-Clock Derived Timing (Timing Flow in Normal Operation)
To enhance resiliency in rings containing many units, it is possible to configure an
additional unit, located midway along the ring (say Unit D in Figure 1-28), to also

use station timing as its second priority source, even if the available timing
quality of the station signal that can be supplied to Unit D is not equal to that of
Unit A. The SSM-based selection mechanism will always prefer the better quality
timing from Unit A as long as it is available, and will switch to the station clock
supplied to Unit D when Unit A timing source fails, or its quality is degraded.
Data Channel Timing Modes

Data channels operating in the asynchronous mode always use the nodal clock as
their rate generator clock.
For data channels operating in the synchronous mode, the user can select the
channel timing mode in accordance with the application requirements. The
various channel timing modes are described below.
DCE Timing Mode

In the DCE mode, the Megaplex-4100 data channel provides transmit and receive
clocks for the equipment connected to the data channel, as shown in Figure 1-29.
The clock signals are derived from the nodal clock.
This mode is usually required for connection to DTE equipment.
Asynchronous data channels also use the DCE timing mode for their internal timing.
Megaplex-4100
DTE
XMIT Clock
RCV Clock
Figure 1-29. DCE Channel Timing Mode
External DCE Timing Mode

In the external DCE mode, the Megaplex-4100 data channel sends data
accompanied by a receive clock to the connected equipment, and accepts
transmit data from the equipment according to the equipment clock. The flow of
timing signals in the external DCE mode is shown in Figure 1-30.
Megaplex-4100
DCE XMIT Clock

RCV Clock
Tail-End
Circuit
Figure 1-30. External DCE Timing Mode

The external DCE mode requires the equipment connected to the corresponding
channel to use loopback timing, because its transmit timing must be locked to the
Megaplex-4100 nodal timing.
The external DCE timing mode is often required for “tail end” connections, where a
modem (DCE) is connected to a data channel. In this case, the remote terminal

(DTE) connected to the remote end of the modem link must use loopback timing,
thereby ensuring that the rate of data applied to the Megaplex-4100 channel
transmit input is equal to the receive rate.
DTE Timing Mode

In the DTE mode, the Megaplex-4100 data channel transmits and receives data
according to the clock supplied by the connected equipment. To support this
mode, the Megaplex-4100 unit must use external timing, with the channel
operating in the DTE mode being selected as the timing reference source.
The flow of timing signals in a DTE timing application is shown in Figure 1-31.
The DTE timing mode is required in applications such as data channels connected
to a digital data switch or to a data carrier network: since the data switch
provides the timing reference for the whole network, is must be able to provide
clock signals for both the Megaplex-4100 and the equipment connected to it.
When operating channels in the DTE timing mode, one of the data channels can
be selected as the external source for the entire system timing. To compensate
for jitter and short-term instabilities, FIFO buffers are used at the input of each
channel. FIFO length is user-selectable, provided the channel is not used as an
external clock source.
Megaplex-4100
DTE
XMIT Clock
XMIT Clock Digital Data
RCV Clock
Network
RCV Clock
Master Clock
Figure 1-31. DTE Timing Mode
ISDN Channel Timing Modes

When a Megaplex-4100 link is used to connect remote ISDN equipment to the
ISDN network, it is necessary to ensure that the timing of the remote equipment
is locked to the network timing. Therefore, the operating mode of the
Megaplex-4100 units must enable dissemination of the ISDN network timing
through the Megaplex-4100 link. The various timing modes supported by ISDN
channels are described below.
In all the modes described below, the receive timing of a port is derived from the
incoming ISDN signal, and the transmit timing is derived from the Megaplex-4100
nodal clock.

Timing Modes for ISDN Channels with “S” Interface

ISDN channels with “S” interfaces support two timing modes, TE and NT. The TE
mode is used to connect an ISDN channel with “S” interface to the network, and
the NT mode is used at the remote end.
Figure 1-32 shows the flow of timing signals in a typical application, and the
relationship between the two timing modes.
Terminal
Equipment
NT
Transmit Timing
Locked to
ISDN ISDN Channel Loopback
Switch Timing
~
~
Megaplex-4100
Megaplex-4100
HS-S Module HS-S Module

(TE Mode) (NT Mode)
Figure 1-32. Timing Modes for ISDN Channels with “S” Interface
The characteristics of the two timing modes are described below:
• TE Mode. In the TE mode, the receive clock of one of the ISDN 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
Megaplex-4100 nodal timing.
As a result, the nodal timing is locked to the network timing, and can be
distributed to the remote Megaplex-4100 unit. This also ensures that the
channel transmit timing is also locked to the network timing.
• NT Mode. In the NT mode, the Megaplex-4100 nodal timing determines the
timing of the data transmitted to the user's terminal equipment connected to
the “S” interfaces. 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 “S”
interface), the user's terminal equipment must operate with loopback timing.
Note
When the ISDN network timing is available at the two Megaplex-4100 sites from
other sources, for example, from clock distribution units, it is also possible to use
the station clock mode at both ends of the link, instead of the timing modes
described above.
Timing Modes for ISDN Channels with “U” Interface

In general, ISDN channels with “U” interfaces support two timing modes: LT and
NT. When the channels are used to connect remote equipment to a network, the
channels must operate in the /I mode (see description of this mode in the
HS-U-6, HS-U-12 Installation and Operation Manual). The NT-I mode is used to
connect an ISDN channel to the network, and the LT mode is used at the remote
end.

Figure 1-33 shows the flow of timing signals in a typical application of ISDN
channels with “U” interfaces.
Terminal
Equipment
LT
Transmit Timing
Locked to
ISDN ISDN Channel Loopback
Switch Timing
~
~
Megaplex-4100
Megaplex-4100
HS-U-6/12 Module HS-U-6/12 Module

(NT-I Mode) (LT-I Mode)
Figure 1-33. Timing Modes for ISDN Channels with “U” Interface
• NT-I Mode: In the NT-I mode, the receive clock of one of the ISDN channels,
which is recovered from the line signal received from the line termination unit
to which the channel is connected, must be selected as reference for the
Megaplex-4100 nodal timing. As a result, the nodal timing is locked to the
network timing, and can be distributed to the remote Megaplex-4100 unit.
This also ensures that the channel transmit timing is also locked to the
network timing.
• LT-I Mode. In the LT-I mode, the Megaplex-4100 nodal timing determines the
timing of the data transmitted to the user's terminal equipment connected to
the “U” interfaces. 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 “U” interface), the user's terminal
equipment must operate with loopback timing.
Note
When the ISDN network timing is available at the two Megaplex-4100 sites from
other sources, for example, from clock distribution units, it is also possible to use
the station clock mode at both ends of the link, instead of the modes described
above.
Redundancy Options
Megaplex-4100 supports redundancy for the connections to the SDH/SONET
network and to the PSN, for virtually concatenated groups, and also for the E1
and T1 ports.
The following sections present the redundancy options for each type of
connections.
CL Module Redundancy
Only one CL module is necessary per chassis, however the chassis has two slots
dedicated to this type of module. The second slot can be used to install a
redundant CL module of the same type, thereby providing a hot-standby
capability for the Megaplex-4100 system control functions.

When a second CL module is installed, the two modules operate as a

master/slave pair; one module is the active (online) module, and the other is
off-line and serves as a hot standby.
Only the online CL module communicates with the management station/terminal
and actively manages the Megaplex-4100 system. The off-line CL module is
automatically updated by the online module with all the configuration and status
data, and therefore the off-line can take over at any time without disrupting
system operation. 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 slave CL module communicates only with the online module. Moreover, the
transmit line in the slave supervisory port connector is disabled, to enable
physical connection in parallel (e.g., by means of a Y cable) to a supervision
terminal or to a modem, and the CL Ethernet port is also disabled, and therefore
the Ethernet connectors of the two CL modules can be simultaneously connected
to the same LAN.
Note The SDH/SONET and/or Ethernet traffic subsystems located on the CL modules
operate independently of the management subsystems, and therefore the
redundancy switching of the management subsystems does not affect
SDH/SONET and/or Ethernet traffic.
Redundancy for SDH/SONET Network Connections (CL.1/155,

CL.1/155GbE)
SDH/SONET Link Redundancy Options

Megaplex-4100 supports 1+1 unidirectional (line) protection with APS per ITU-T
Rec. G.842 for the links to the SDH/SONET network.
Redundancy is activated by configuring APS groups using 1+1 unidirectional
protection. The supported APS configurations are as follows:
• When one CL module is installed in the chassis: one APS group including the
two ports of the CL module. In this case, the total bandwidth of the link to
the SDH/SONET network is one STM-1/OC-3.
• When two CL modules are installed in the chassis: two APS groups. In this
case, the total bandwidth of the links to the SDH/SONET network is two
STM-1/OC-3, in accordance with the following options:
APS group including the LINK 1 ports of the two CL modules, and another
group including the LINK 2 ports.
APS group including the two ports of one CL modules, and another group
including the two ports of the other.
Note that when redundancy is used, only one mapping is required for each link to
the network, because the ports must have identical configurations for line
redundancy to work. Therefore, the mapping can be configured only on the
primary port of an APS group (actually, the secondary port cannot be included in
an APS group before its mapping is deleted).

Operation of 1+1 Unidirectional Protection Function

Figure 1-34 illustrates the operation of the 1+1 unidirectional protection function
on a Megaplex-4100 using a single CL module.
1+1 unidirectional protection works as follows:
• Both the working and protection ports of an APS group simultaneously
transmit the same data toward the remote end, via two different paths.
• At each side, the signal received by each port of an APS group is evaluated in
accordance with the alarm weighting criteria specified in ITU-T Rec. G.707, to
determine the best signal (the signal with the lowest total alarm weight). The
results of this evaluation are used to select the receive signal actually
connected to the corresponding telecom bus (these tasks are performed by a
processing function identified as an internal protection switch). Figure 1-34.A
shows the normal operating conditions, under which the signal received
through the working port is selected for processing.
• When a fault occurs, protection switching takes place. Figure 1-34.B shows the
change in case the working signal path ending at the LINK 1 port of the West
Megaplex-4100 fails: the received signal is now taken from LINK 2. Note that
the same action would be taken in response to any problem along this path
(fault at location A, fault at location B, transmit failure at the East LINK 1
port, or receive failure at the West LINK 1 port).
Internal Internal
Protection Protection
Switch Switch
SDH/SONET
LINK 1 Network LINK 1
LINK 2 LINK 2
CL.1/GbE or CL.1/GbE or
CL.1/155GbE CL.1/155GbE
Module Module
Legend
Working link
Protection link
A. Normal Operation

Internal Internal
Switch Switch
Megaplex-4100 B Megaplex-4100
A SDH/SONET
LINK 1 Network LINK 1
LINK 2 LINK 2
Module Module
Legend
Working link
Protection link
B. Operation after Protection Switching due to Fault in Path to one Port
Figure 1-34. Operation of 1+1 Unidirectional Protection Function

The basic 1+1 unidirectional protection configuration shown in Figure 1-34 can be
extended to a dual-link configuration, by installing two CL modules at each side.
In this case, protection switching replaces the working port with the
corresponding protection port of the APS group (in the example given above, a
fault in the path ending at LINK 1 of one CL module would switch the traffic to
LINK 1 of the second CL module). In the same way, a hardware failure in one CL,
or a break in the optical cable connecting to an CL, would switch the traffic to the
other module.
With 1+1 unidirectional protection, each side independently selects the best
signal (in Figure 1-34.B, no change occurred at the East Megaplex-4100), and
therefore no protocol is needed to coordinate protection switching with the
remote side. For example, in Figure 1-34.B, the East side would also switch to the
protection port (LINK 2) if the West side problem is a break in both fibers
connected to the West LINK 1 port.
The alarm criteria taken into consideration for protection switching are as follows
(listed in decreasing weight order):
• The module with the other port in the APS group is not installed.
• Forced-flip command.
• Critical alarm. A critical alarm is caused by the detection of one or more of
the following fault conditions: loss of SDH/SONET line signal, reception of AIS
signal on the line, loss of SDH/SONET frame, or clock failure.
• Major alarm. A major alarm is caused by EED (excessive error degradation).
The EED threshold can be selected by the user.
• Minor alarm. A minor alarm is caused by an 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.
• Revert request (only when the revertive recovery mode is selected).

The working port always carries the traffic, as long as its total alarm weight does
not exceed that of the protection. The user can however force switching (flipping)
to the other port by a manual flip command: such command is always executed,
except when the other port in the APS group by a manual command, except when
it is located on a module not installed in the chassis.
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, which 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 take place, even if the restoration time
has not yet expired.
Path Protection for SDH/SONET Payload (CL.1/155, CL.1/155GbE)

Path (trail) protection is available for user-specified payload units (VC-12 and
VC-3 for SDH links, or VT1.5 and STS-1 for SONET links). Figure 1-35 shows the
path protection topology.
When path protection is enabled, the protected payload unit is assigned
bandwidth on both network links:
• The same payload is transmitted on both links.
• The receive interfaces of the two links continuously evaluate the received
signals. As long as the primary path operates satisfactorily, its signal is
selected for processing. When the primary path signal fails, or is degraded,
the receive side rapidly selects the other signal (shown in dashed lines in
Figure 1-35) for processing.
By provisioning appropriate alternative paths through the network, it is possible
to ensure that in case of a fault anywhere along the active path the traffic is
automatically switched to the standby path.
The protected payload positions can be manually configured on each link, and
therefore may be different.

Internal Path Internal Path

Switch Switch
LINK 1 SDH/SONET LINK 1

Network
LINK 2 LINK 2
Module Module
Figure 1-35. Operation of Path Protection
Redundancy for PSN Connections (CL.1/GbE, CL.1/155GbE)

Redundancy can be enabled for GbE ports of CL.1/GbE or CL.1/155GbE modules,
to provide protection for the connection to the PSN. Any pair of GbE ports can be
configured to form a redundancy pair, and therefore it is possible to protect
against hardware failures, as well as against transmission path failures.
When redundancy is enabled, the pair of GbE ports operate as a single PSN
interface. The protection mode is 1+1 redundancy, The recovery mode (revertive
or non-revertive) can be selected in accordance with the application
requirements. In the revertive mode, it is also possible to specify a wait-to-
restore interval, which delays the return to the original port after it immediately
returns to normal.
Two topologies can be used for the connections to the GbE ports of a
redundancy pair (for simplicity, only ports located on the same CL module are
shown in Figure 1-36 and Figure 1-37):
• Connection of both GbE ports to the same switch/router (Figure 1-36).
PSN
GbE1 GbE1
GbE2 GbE2
Module Module
Figure 1-36. Connection of Redundant GbE Ports to Same Switch/Router

• Connection of the GbE ports to different switch/routers, as shown in
Figure 1-37. The main advantage of this topology is its higher availability,
because each port can be routed along a different path through the network.

Megaplex-4100
Megaplex-4100
GbE1
GbE1
PSN
GbE2
GbE2
CL.1/GbE or
CL.1/GbE or
CL.1/155GbE
CL.1/155GbE
Module
Module
Legend
On-line link
Off-line link
Figure 1-37. Connection of Redundant GbE Ports to Different Switches/Routers

With 1+1 redundancy, at any time only one of the ports is actively carrying the
GbE traffic, and the other port serves as the backup port. The redundancy
algorithm uses loss of GbE signal to detect line failure.
The recovery mode after a protection switching can be selected in accordance
• Non-revertive mode – the GbE module will not automatically flip back after
the failed port returns to normal operation, but only when the currently used
port fails, or after a manual flip command.
• Revertive mode – the GbE module will flip back to the original port after it
returns to normal operation.
The equipment connected to the GbE ports must use compatible switching
criteria for redundancy to be available:
• For networks using Layer 2 switching: after protection switching (flipping) the
network will learn the same MAC address through a different interface (in the
topology of Figure 1-37, this will be an interface of a different router). After
learning again the MAC interface, connectivity is automatically restored.
• For networks using Layer 3 routing: the router must support some form of
redundancy, and the network must be able to accept the same IP subnet
from different interfaces.
Virtually Concatenated Group Redundancy Options

Megaplex-4100 equipped with CL.1/155GE modules support 1+1 redundancy for
virtually concatenated groups, thereby protecting against transmission failures on
the SDH/SONET links.
Any pair of virtually concatenated groups can be configured as a redundancy pair,
even if they have different capacity, or even use different encapsulation
methods, and/or parameters. Only the recovery mode (non-revertive or
revertive), and the restoration delay in the revertive mode, must be the same.
To use virtually concatenated group redundancy, both the primary (protected)
virtually concatenated group and the secondary (protection) virtually
concatenated group must be assigned bandwidth (mapped) on the desired links.
By provisioning appropriate trails through the network, it is possible to ensure

that in case of a fault anywhere along the primary group path, its traffic is
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 redundancy 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 virtually concatenated group 1+1 redundancy mode operates as follows:
• During normal operation, the payload is directed to the primary virtually
concatenated group, and transmitted only over the bandwidth assigned to
this group.
Note Only the primary virtually concatenated group can be included in a flow (the
secondary virtually concatenated group will not appear in the list of available
bridge ports).
• In case an alarm condition is detected on the primary group, the payload is

directed to the secondary group, and transmitted over its bandwidth. The
alarm criteria taken into consideration for redundancy switching include
physical port failures and virtually concatenated group failures (when using
LCAS, this also includes a decrease in available bandwidth below the specified
minimum).
The recovery mode after a redundancy switching can be selected in accordance
• Non-revertive mode – the traffic will not be automatically redirected back
after a failed group returns to normal operation, but only when the currently
used group fails.
• Revertive mode – 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
restoration 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 restoration time has not yet expired.
Redundancy for E1 and T1 Links

One of the simplest methods to protect against link and hardware failure is to
use the link redundancy function.
Redundancy provides two main advantages:
• Automatically restores service within a short time without user’s intervention
• In case of technical failure, allows service to continue while technical staff
finds the source of the failure and corrects it.
Moreover, when redundancy is used, planned maintenance for example, updating
software versions, or installing modules with enhanced capabilities, can also be
performed without disrupting service, provided a few precautions are taken:
• To minimize disruptions to traffic, do not simply pull module out but first
check that the module does not serve as the master. If one of the module

ports serves as the master, first force redundancy flipping by means of a

RESET command.
• After removing a module, wait at least 10 seconds before inserting a module
in the same slot.
Three different redundancy approaches are supported: dual-cable redundancy,
Y-cable redundancy and E1/T1 ring redundancy.
Dual Cable (Parallel TX) Redundancy

For this type of redundancy, two ports of the same type (either E1 or T1) are
connected to the remote unit via two parallel links. By defining these two links as
a redundant pair, it is possible to ensure that traffic carrying capacity is available
even if one of the links fails.
Figure 1-38 shows a typical system configuration using dual-cable redundancy. The
user can select the module ports operating as a redundant pair. When operating
with dual cable redundancy, the redundant port is configured with basically the
same parameters as the primary port (there may be differences in parameters
related to the link physical configuration parameters). Both ports process as usual
the transmit and receive signals, but the receive output of the redundant port is
disconnected.
During normal operation, the operational state of the redundant port is
continuously monitored, to ensure that it is operating O.K. If the primary link
fails, the corresponding port is disconnected, and the redundant port takes over.
The switching time between main and backup ports is maximum 50 msec, and
therefore redundancy 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 redundancy switching is not available on modules with SHDSL interfaces,
because of the long times needed to detect failure and put in service a standby
port (this is caused by the SHDSL link setup protocols specified by the
standards).
I/O Module with I/O Module with

E1 or T1 Ports E1 or T1 Ports
Primary (Active) Link
Redundant (Standby) Link

Figure 1-38. E1/T1 Link Redundancy Using Dual Cables
Y-Cable Redundancy
For Y-cable redundancy, 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 redundancy 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 1-39.

When operating with a Y cable, the redundant module port must be configured
with the same parameters as the primary module port.
During normal operation, the transmit output of the redundant module is
electrically disconnected from the link. Nevertheless, its operational state is
continuously monitored, to ensure that it is operating O.K. If the primary module
fails, it is disconnected from the link and from the internal buses, and the
redundant module takes over.
I/O Module with I/O Module with

E1 or T1 Ports E1 or T1 Ports
Transmission Link
Figure 1-39. E1/T1 Link Redundancy Using Y-Cable
E1/T1 Ring Redundancy

The E1/T1 ring redundancy is a RAD proprietary topology suitable for
Megaplex-4100 equipment that provides higher availability for critical applications
at the E1 and T1 level, with fast protection switching time (the switching time for
E1/T1 ring redundancy is less than 50 msec).
Figure 1-40 illustrates this topology in Figure 1-41. 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. For example, the ring paths
interconnecting Megaplex-4100 units A, B, and C of the E1 ring illustrated in
Figure 1-41 can run between physical E1 ports of M8E1 modules, and the ring
closing path (between Megaplex-4100 units D and A) may run over SHDSL, which
provides the additional E1 link. To support this option, one free M8SL port is
required in each of the Megaplex-4100 units D and A (in addition to the M8E1
modules which must be anyhow installed in these units to provide connectivity
between units A, B, and C).
MP-4100 B
MP-4100 A MP-4100 C
Primary Ring
(E1, T1 or SHDSL)
Secondary Ring
(E1, T1 or SHDSL)
MP-4100 D
Figure 1-40. E1/T1 Ring Topology

E1/T1 ring redundancy is based on the use of two transmission paths, each
requiring a single twisted pair: one pair, called the primary, is used instead of the
legacy transmit pair, and the other, called the secondary, is used instead of the
legacy receive pair. Therefore, E1/T1 ring redundancy can use the same cabling
infrastructure as regular point-to-point links, but provides several significant
advantages:
• There is no single point of failure
• Rapid switching time in case of failure (within 50 msec)
• Uses the full bandwidth of the E1 or T1 link
• Does not require additional hardware: actually, 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
Megaplex-4100)
• Flexible solution:
Supports any number of nodes along the ring
Any Megaplex-4100 unit in the ring can connect to additional rings, and
allows timeslot cross-connect between the 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 primary and secondary E1/T1
ports.
The E1/T1 ring redundancy topology can be efficiently implemented by any pair of
physical or internal (virtual) 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 redundancy pair. To enable handshaking between Megaplex-4100 units in an
E1/T1 ring, it is necessary to use the RAD proprietary RIP protocol, with inband
management carried over a dedicated timeslot.
Figure 1-41 shows a typical application that uses the ring redundancy topology.
Primary Ring
Secondary Ring
TS 13 MNG TS 13 MNG TS 13 MNG TS 13 MNG

TS 13 MNG TS 1-3 Local (3 TS) TS 4-6 Local (3 TS) TS 7-9 Local (3 TS) TS 10-12 Local (3 TS)
TS 1-12 Local TS 4-12 Bypass TS 1-3, 7-12 Bypass TS 1-6, 10-12 Bypass TS 1-9 Bypass
Primary Primary Primary Primary Primary
RX TX RX TX RX TX RX TX RX TX
Port 2 Port 1 Port 2 Port 1 Port 2 Port 1 Port 2 Port 1 Port 2 Port 1
TX RX TX RX TX RX TX RX TX RX
Central A B C D
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 1-41. E1/T1 Ring Redundancy – 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 1-41) are defined as a redundancy pair. One port of each
unit (in this example, port 2) is configured as primary port: under normal

conditions, each Megaplex-4100 transmits data to the next node through the
primary port, and receives through the secondary port. Timeslots not connected
to local channels are bypassed.
The payload is handled as follows:
• Primary ring: at each unit, timeslots used at the local unit are dropped from
the receive side of the secondary port, and added to the transmit side of the
primary port. Timeslots used by the other Megaplex-4100 units are bypassed
directly between these two ports.
• Secondary ring: all the timeslots received by port 2 are bypassed to the
transmit side of port 1.
When one of the segments in the ring fails (see Figure 1-42), 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,
now each unit 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.
Primary Ring
Secondary Ring
TS 13 MNG TS 13 MNG TS 13 MNG TS 13 MNG

TS 13 MNG TS 1-3 Local TS 4-6 Local TS 7-9 Local TS 10-12 Local
TS 1-12 Local TS 4-12 Bypass TS 1-3, 7-12 Remote Loop TS 1-6, 10-12 Remote Loop TS 1-9 Bypass
Primary Primary Primary Primary Primary

Central A B C D
HS-6N
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 1-42. E1/T1 Ring Redundancy – 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 redundant path, do not activate
remote loopbacks, nor loopbacks on timeslots, on ports connected to the ring.
• When it is necessary to perform local bypassing (on the same module)
between another port to one of the ports participating in ring redundancy,
you can do that only for the primary port; for the redundancy port, you get an
error message.
Timing Considerations for E1/T1 Ring Redundancy Applications

When using ring redundancy, it is necessary to ensure that the same reference
timing can always be used at all the units on the ring.
• Using an External Reference Signal. At sites where Megaplex-4100 equipment
is connected through ADMs to the SDH/SONET backbone (or has CL modules

with SDH/SONET subsystems and is configured to use S-subsystem timing), or

at sites using a GPS-based timing reference, a common timing reference is
always available.
When this common timing reference is available at all the sites along the ring,
it is recommended to use this external signal as the nodal timing reference
for all the units on the ring.
The main advantage of this approach is that it is not necessary to change the
timing reference when redundancy switching takes place.
• Using other Timing Reference. As an alternative, the equipment can be
configured so that the timing reference is distributed in a controlled way to
all the equipment units, for example, by locking the nodal timing to the clock
signal of a selected port (Rx timing mode). This requires:
Selecting appropriate timing reference sources
Configuring the main and fallback sources in a way that takes into
consideration the change in the direction of timing flow caused by
recovery from failure.
For example, in Figure 1-41 the timing flows clockwise through the whole ring
(the main timing source is port 1, and the fallback is port 2), whereas after
recovery from segment failure (Figure 1-42), in some parts of the ring the
direction of reference timing flow must be reversed. Figure 1-43 and
Figure 1-44 show the timing reference flow before and after recovery.
The timing state of the ring is carried by the periodic RIP update messages
(part of the RAD proprietary RIP protocol, which is mandatory for ring
redundancy to work). Typically, these update messages are sent every 30
seconds.
The ring redundancy protocol uses a special fault indication message (CLOCK
FAILURE IN THE RING) to notify other units in the ring that a fault event
occurred on the ring:
The reception of the NOT OK indication via a link configured as a master
timing source causes the receiving unit to switch from master to fallback
timing.
A unit that must switch to fallback will not select as source a link from
which NOT OK indications are received.
The NOT OK indication is ignored when a unit does not use a link as its
timing source.
Note The switching of the traffic to the secondary ring takes place as soon as a fault
occurs, without requiring any handshaking with other units.

Port 1: Master
Port 2: Fallback
Clock
Reference
(Station)
Figure 1-43. E1/T1 Ring Redundancy Topology – Normal Timing Reference Flow
Port 1: Master
Port 2: Fallback
RING CLOCK FAILURE
Clock
Reference
(Station)
Figure 1-44. E1/T1 Ring Redundancy Topology – Timing Reference Flow after Segment Failure
Since the fault indication is carried by the periodic RIP update messages, it
takes time for the fault notification to propagate through the ring. During the
propagation time, frame slips may occur.
For long rings including a large number of units, it is possible to reduce the
propagation time by distributing the same timing reference in two directions
through the ring. Note however that this approach must be analyzed with
respect to the maximum accumulating jitter.
Figure 1-45 shows an implementation of this alternative arrangement: the
corporate ring uses the PBX as the timing reference for the whole ring. For
redundancy, the PBX provides the timing signal to two units, Megaplex-4100
1 and Megaplex-4100 6. The timing sources configured for each unit, as well
as the flow of the timing information during normal conditions, are both
indicated in the figure. Figure 1-45 also shows how the clock status
messages (OK for all the units) reach all the units in the ring.

The recovery from faults is illustrated in Figure 1-46 and Figure 1-47:
In case a fault occurs on the ring (Figure 1-46), Megaplex-4100 unit 3 can
no longer use its master timing. Therefore, the CLOCK FAILURE ON THE
RING alarm state is declared, and the following exchange of messages
takes place:
1. Megaplex-4100 unit 2 does not need to report any clock problem (it
only switches the traffic).
2. Megaplex-4100 3 loses the link signal to which its timing is locked,
and therefore NOT OK indications are sent by Megaplex-4100 3 to the
next unit it can reach, Megaplex-4100 4.
3. Since Megaplex-4100 4 master timing is also lost when
Megaplex-4100 3 cannot provide its reference, Megaplex-4100 4 also
sends NOT OK indications to the next unit, Megaplex-4100 5.
4. Megaplex-4100 5 has a stable timing reference, and therefore, it can
continue reporting OK to the other units. Therefore, the
counterclockwise propagation of the NOT OK state stops.
5. Since Megaplex-4100 5 reports OK to Megaplex-4100 4, the latter unit
can select its signal as reference (that is, it can switch to its can also
be used as reference.
6. Megaplex-4100 3 now switches to fallback, and uses the
Megaplex-4100 4 signal as reference.
At this stage, Megaplex-4100 3 and 4 units have both reacquired stable
timing by switching to their fallback sources. The resulting timing flow is
also illustrated in Figure 1-46.
After the ring fault is corrected, the timing flow can return to normal: this
operation is triggered by the transmission of OK indications instead of
NOT OK by Megaplex-4100 3 and Megaplex-4100 4.
In case the fault occurs in the connection to the PBX (Figure 1-47),
Megaplex-4100 1 loses its master timing source. Therefore, the CLOCK
FAILURE ON THE RING alarm state is declared, and the following exchange
of messages takes place:
1. Megaplex-4100 1 reports NOT OK toward Megaplex-4100 6 (it will not
report NOT OK toward Megaplex-4100 2, because this is not relevant:
Megaplex-4100 1 uses the RX clock from the PBX as master source, not
the timing signal from the link connecting to Megaplex-4100 2).
2. Megaplex-4100 1 can switch to fallback (the signal from Megaplex-4100
6), because Megaplex-4100 6 reports OK.
At this stage, Megaplex-4100 1 has reacquired stable timing by switching
to the fallback sources.
The resulting timing flow is also illustrated in Figure 1-47.

5 4 3
Master: Port 1 Master: Port 1 Master: Port 1
Fallback: Port 2 Fallback: Port 2 Fallback: Port 2
Port 1 Port 2 Port 2 Port 1 Port 2 Port 1

OK OK OK OK OK OK
OK OK OK OK OK OK
Master: Port 2 Master: RX Clock Master: Port 1

Fallback: RX Clock Fallback: Port 2 Fallback: Port 2
6 1 2
PBX
Figure 1-45. E1/T1 Ring Redundancy Topology – Alternative Timing Flow
5 4 3
OK OK NOT OK OK NOT OK OK
OK OK OK OK OK OK

6 1 2
PBX
Figure 1-46. Timing Recovery Scenario – after a Ring Fault

5 4 3

OK OK OK OK OK OK
OK OK NOT OK OK OK OK

6 1 2
PBX
Figure 1-47. Timing Recovery Scenario – after Loss of Master Reference
The Megaplex-4100 management subsystem provides all the functions needed to
configure, control, and monitor the operation of the Megaplex-4100. The main
management subsystem functions are as follows:
• Interfacing with supervision terminals, SNMP network management stations,
and other types of external managers.
• Configuring the Megaplex-4100.
• Controlling the Megaplex-4100 system operation.
• Monitoring the Megaplex-4100 status, and reading its performance
monitoring statistics.
• Performing Megaplex-4100 tests and diagnostics.
• Collection of operational history (alarms, events, performance statistics, etc.
The collected information can be read by maintenance personnel through the
management link.
A real-time clock provides time stamps for all the collected information.

• Storage of the application software, which determines the capabilities and

features provided by the Megaplex-4100. This software can be remotely
downloaded and updated through the management link without taking the
equipment off-line. The stored software includes both system software, run
by the CL module, and software for the other modules installed in the chassis
that support internal software downloading.
• Storage of configuration databases. The configuration databases can also be
uploaded and downloaded through the management link.
The application software, as well as the configuration databases, are stored in
flash memory.
In addition, the management subsystem also enables signaling the
Megaplex-4100 alarm status to bay alarm panels or remote operator consoles by
means of two sets of dry relay contacts (one for major alarms, the other for
minor alarms) included in the dedicated front-panel ALARM connector.
Megaplex-4100 units can also be managed by the RADview EMS, an SNMP-based
Element Management System offered by RAD.
Management Alternatives
The Megaplex-4100 supervision and configuration activities can be performed
using one of the following methods:
• Supervision terminal (for example, implemented using a PC running ASCII
terminal emulation), or connected to the serial control port of a CL module.
No configuration information need be stored by the terminal
• Telnet hosts (using the same procedures as the supervision terminal utility),
Web browsers (using the ConfiguRAD utility run by the Megaplex-4100
management subsystem), and SNMP-based network management stations,
for example, RADview. The following access options are supported:
Out-of-band access via the dedicated Ethernet management port of the
CL module(s)
Inband access through TDM networks, supported by E1 or T1 ports (using
a dedicated management timeslot), or by the DCC carried in the
STM-1/OC-3 link overhead.
Inband access through the PSN, using a dedicated management VLAN.
This type of inband access is supported by Ethernet ports, virtually
concatenated groups, and bridge ports configured on bundles.
Management by SNMP-based network management stations, using the
access options described above for Telnet hosts. Megaplex-4100 includes
an internal SNMP agent that enables full SNMP management by SNMP-
based network management stations. The internal agent supports the
SNMPv3 authentication and privacy features, with continued support for
SNMPv1.
Web browsers (using the ConfiguRAD utility run by the Megaplex-4100
management subsystem), using the access options described above for
Telnet hosts

Except for the supervisory port, all the other management access ports use
IP-based communications, where a single IP address (the host IP address) is
assigned to the management subsystem. All the ports use the same IP and SNMP
communication parameters, and therefore management traffic can reach the
Megaplex-4100 management subsystem through any available access port.
Remote Software and Configuration Updating

The management subsystem supports TFTP for remote software updating and
downloading, in addition to cold software downloading using an ASCII terminal
directly connected to the Megaplex-4100.
TFTP can also be used to upload and download the Megaplex-4100 configuration
database. Network administrators can use the download capability to distribute
verified configuration files to all the managed Megaplex-4100 units in the
network from a central location. To further expedite the process, it is also
possible to upload the configuration data stored by an Megaplex-4100 unit to the
management station as a disk file, and then distribute this file to other units
which use a similar configuration.
Supervisory Port Capabilities

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.
The supervisory port enables performing 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, Web
browsers, 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.
Out-of-Band Access via CL Ethernet Management Port

All the CL models 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 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 (see the CL Module
Redundancy section on page 1-58.
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 module Ethernet ports is possible.

Inband Management Access through TDM Networks

Figure 1-48 illustrates the inband management access capabilities through TDM
networks.
Megaplex-4100
CL Megaplex-4100
Inband Management Traffic

to Other Equipment
CL
E1 E1
Megaplex-4100
SDH/SONET
Network
E1, T1 CL
or SHDSL
Megaplex-4100 Module
TDM Megaplex-4100
Network
CL E1, T1
or SHDSL E1, T1 CL
Network Module or SHDSL
Management Module
Station
Figure 1-48. Inband Management Access through TDM Networks

The following access methods are available:
• Access via E1 and T1 ports (including internal ports of SHDSL I/O modules)
using a framed mode: in this case, management access is provided by
configuring a dedicated management timeslot.
• Access 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.
Note
Inband management can also support more complex topologies, for example,
rings. However, this is possible only if the carrier’s SDH/SONET network provides
access to the DCC and enables transparent transfer of user’s 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.
As mentioned above, the inband management traffic is carried in the DCC
bytes, part of the SDH/SONET overhead. The user can select the DCC bytes to
carry the traffic:
Regenerator section DCC bytes (D1, D2, D3), which provide a 192 kbps
channel terminated at SDH/SONET regenerator section terminating
equipment
Multiplex section DCC bytes (D4 to D12), which provide a 576 kbps
channel terminated at SDH/SONET multiplex section terminating
equipment.
The user 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, the user 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.
Inband Management Access through PSN Networks

Figure 1-49 illustrates the inband management access capabilities through PSN
networks. As shown in Figure 1-49, management traffic received through the PSN
is also available on the TDM ports, to integrate the various management options.
To control the flow of management traffic through the PSN, a dedicated
management VLAN is normally used.
Within the Megaplex-4100, management traffic routing is controlled by
configuring a dedicated management flow, which is always assigned the flow
identifier 251 (see the Using Flows to Control Ethernet Traffic Forwarding section
starting on page 1-45 for a description of Ethernet flows).
Three types of bridge ports can be included in the internal management flow:
• Ethernet ports, including GbE ports
• Bridge ports configured on unframed bundles (both HDLC and MLPPP
bundles)
• Virtually concatenated groups configured on SDH/SONET ports

To avoid forming loops in the Ethernet communication topology when same

management traffic can be received through more than one bridge port, the user
can specify which bridge ports will accept management traffic from network
management stations (such ports are referred to as host NMS sources), and the
management subsystem selects one of these ports as the active port.
PSN
Inband Management Traffic
to Other Equipment
E1 E1
Network n x E1
Management n x E1
TDM
Station Network
CL M8E1 n x E1 n x E1 M8E1
Legend
Dedicated Management VLAN
Figure 1-49. Inband Management Access through PSN
Performance Monitoring Statistics

Megaplex-4100 management subsystem collects performance data, 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.
Alarm Collection and Reporting

The Megaplex-4100 management subsystem continuously monitors critical signals
and signal processing functions, and also performs automatic self-test upon
power-up. In case 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
the user-specified network management stations.
The alarms can be read on-line by the network administrator using a Telnet host, a
Web browser, SNMP-based network management station, or a supervision terminal.
Note
The 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 a bay alarm or remote monitoring panel.
To expedite the handling of alarms, the user can use several tools:
• Masking of alarm conditions, to prevent continuous reporting of known alarm
conditions, e.g., during maintenance activities.
• Inversion of selected alarm indications provided to the local operator by the
alarm indicators, and by the two alarm relays. “Inverted” alarms are ignored
while they are present, therefore the user will be alerted only upon return to
normal operation.
• Filtering of alarms, to prevent unnecessary reporting of alarms during
marginal conditions, which cause frequent changes in alarm states.
Diagnostic Functions
When a problem occurs, Megaplex-4100 offers a set of diagnostic functions that
permit to efficiently locate the problem (in the Megaplex-4100 chassis, one of
Megaplex-4100 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 to 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). A detailed
description of the test and loopback functions is given in Chapter 5, as well as in
the Installation and Operation Manuals of each module.
Power Supply Subsystem
PS Modules
Megaplex-4100 can be ordered with either AC or DC power supply 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.
Feed and Ring Voltage Sources

Megaplex-4100 PS modules support the connection of 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 Technical Specifications

Note For module technical specifications, refer to the module Installation and
Operation Manuals.
STM-1/OC-3 Ports Number of Ports • 2 per CL module

• 4 per chassis
Bit Rate 155.52 Mbps
Timing • Internal clock

• Clock recovered from the STM-1/OC-3
interface
• External clock recovered from TDM interfaces
• External clock recovered from any tributary
within STM-1/OC-3 links
Compliance • SDH: ITU-T G.957, G.783, G.798

• SONET (option): GR-253-CORE
Internal Clock • CL.1/155, CL.1/155GbE: Stratum 3 according

Characteristics to ITU-T Rec. G.813 option 1 and 2, and
GR-253-CORE SMC
• CL.1, CL.1/GbE: Stratum 4E
Framing • SDH: ITU-T Rec. G.707, G.708, G.709, G.783

• SONET: ANSI T1.105-1995, GR-253-CORE
Protection 1+1 unidirectional APS (G.842)
Connectors SFP-based in accordance with Table 1-3
Note: For detailed specifications of SFP transceivers,

see the RAD SFP Transceivers data sheet.
Megaplex-4100 Ver. 2.0 Technical Specifications 1-81

Table 1-3. SFP Connector Modules for STM-1/OC-3 Interfaces
Input power Output Power Typical Max.

Transmitter Connector (dBm) (dBm) Range
Transceiver Wavelength Fiber Type
Type Type
(min) (m ax) (min) (max) (km) (miles)
SFP-1 62.5/125 μm, VCSEL LC -30 -14 -20 -14 2 1.2

multi-mode
SFP-2 9/125 μm, Laser LC -28 -8 -15 -8 15 9.3
1310 nm
single mode
SFP-3 9/125 μm, Laser LC -34 -10 -5 0 40 24.8
single mode
SFP-4 1550 nm 9/125 μm, Laser LC -34 -10 -5 0 80 49.7
single mode
SFP-11 Copper Link 75Ω coaxial — Mini-BNC — — — — 0.135 0.08
cable over RG-59B/U
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
Optical GbE Port Interface Type 1000 Mbps full-duplex port

Interface
Characteristics Link Connectors SFP-based in accordance with Table 1-4
Table 1-4. SFP Connector Modules for GbE Interfaces
Input power Output Power Typical Max.

Transmitter Connector (dBm) (dBm) Range
Transceiver Wavelength Fiber Type
Type Type
(min) (max) (min) (max) (km) (miles)
SFP-5 850 nm 50/125 μm, VCSEL LC -17 0 -9.5 0 0.55 0.3

multi-mode
SFP-6 1310 nm 9/125 μm, Laser LC -20 -3 -9.5 -3 10 6.2
single mode
SFP-7 1550 nm 9/125 μm, Laser LC -22 -3 0 +5 80 49.7
single mode
SFP-8d 1310 nm 9/125 μm, Laser LC -21 -3 0 -4 40 24.8
single mode
Copper GbE Port Interface Type 10/100/1000BASE-T port, full-duplex, with

Interface autonegotiation
Characteristics
Link Connector RJ-45 shielded
1-82 Technical Specifications Megaplex-4100 Ver. 2.0

Serial Control Port Interface RS-232/V.24 (DCE)

(CONTROL DCE)
Data Rate 9.6, 19.2, 38.4, 57.6, 115.2 kbps asynchronous
Ethernet Interface 10/100BaseT with autonegotiation

Management Port
(CONTROL ETH) Connector RJ-45
Station Clock Rate • 2.048 MHz

Interface • 2.048 Mbps
• 1.544 Mbps
Interface Jumper-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
Connector RJ-45
Diagnostics Tests Local and remote loopbacks per link and per
timeslot
Alarms • Time and date stamped

• Last 256 alarms stored in RAM on CL module,
readable by management system or terminal
• Current alarms status
Statistics • AT&T statistics when using ESF framing for T1

trunks or CRC-4 with G.704 multiframing for
E1 trunks
• Performance statistics for bundles and LAN
ports
• SDH/SONET link monitoring
• Ethernet port statistics
Indicators ON LINE indicator • Lights green on the master (active) module

• Lights yellow on the master (active) module if
a test exists.
• Flashes green when this module is standby or
during software download
• Flashes yellow when software is
decompressed

ALM indicator • Flashes red when a major or critical alarm

exists in the Megaplex-4100 system
• Lights red when any alarm (not minor or
critical) exists in the Megaplex-4100 system
Station CLOCK Interface • ON (green) – Port is connected

Indicators • LOS (red) – Signal loss on the port
Ethernet Interface • LINK (green) – LAN link integrity

Indicators (per port) • ACT (yellow) – LAN data activity
STM-1/OC-3 Interface LOS (red) – STM-1/OC-3 link signal loss

Indicators (per port)
ON LINE:
• Lights green when the link is active
• Lights yellow if a test exists
Alarm Relay Port Port Functions • 1 inbound RS-232 alarm input

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

pins
Connector 9-pin, D-type, female
Power Supply Model Input
PS/AC Wide-range operation: 110/115, 220/230 VAC

Range: 100 to 240 VAC, 50/60Hz
Maximum output power: 200W + power supplied
for ring and feed voltage purposes (drawn
directly from external supply)
PS/48 • -48 VDC (allowed range: -36 to -72 VDC)

PS/24 • +24 VDC (allowed range: +18 to +40 VDC)
• Maximum input power: 250W + power
supplied for ring and feed voltage purposes
(drawn directly from external supply)
Caution
For PS/48 and PS/24, 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 RAD
Technical Support Department for detailed information.

Max. Power Supply Output Currents
+3.3V +5V -5V +12V -12V
PS/AC, PS/48, PS/24 30A 40A 6.5A 2A 2A
Physical Height 18 cm/7 in (4U)
Width 44 cm/17 in
Depth 33 cm/13 in
Weight (fully equipped 15.3 kg / 33.8 lb max.

chassis)


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 3). 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 Appendix B for detailed software installation instructions.
• After the preliminary configuration, the system can also be managed by
means of Telnet hosts, Web browsers, 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 Safety
General Safety Precautions
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
Warning precautions during installation, operation, and maintenance of this product.
Caution
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.
Megaplex-4100 Ver. 2.0 Safety 2-1

Chapter 2 Installation Installation and Operation Manual
Caution 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.
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 (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.
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.
Caution When working with VC-4/4A/8/8A/16 modules with FXS interfaces, refer to the
Frequently Asked Questions section in the VC-4/4A/8/8A/16 Installation and
Operation Manual for additional information on ground connections.
2-2 Safety Megaplex-4100 Ver. 2.0

Installation and Operation Manual Chapter 2 Installation
Laser Safety
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 be also attached.
Warning
For your safety:
• Before turning on the equipment, make sure that the fiber optic cable is intact
and is connected to the optical transmitter.
• Do not use broken or unterminated fiber-optic cables/connectors.
• Do not look straight at the laser beam, and do not directly into the optical
connectors while the unit is operating.
• Do not attempt to adjust the laser drive current.
• The use of optical instruments with this product will increase eye hazard.
Laser power up to 1 mW at 1300 nm and 1550 nm could be collected by an
optical instrument.
• Use of controls or adjustment or performing procedures other than those
specified herein may result in hazardous radiation exposure.
ATTENTION: The laser beam may be invisible!
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

An electrostatic discharge occurs between two objects when an object carrying
static electrical charges touches, or is brought near enough, the other object.
Static electrical charges appear as result of friction between surfaces of insulating
materials, separation of two such surfaces and may also be induced by electrical
fields. Routine activities such as walking across an insulating floor, friction
between garment parts, friction between objects, etc. can easily build charges up
to levels that may cause damage, especially when humidity is low.
Megaplex-4100 Ver. 2.0 Safety 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.
Proper Handling of Modules

Megaplex-4100 modules include small components installed on both sides of the
printed circuit boards. These components are exposed as long as the modules are
not installed in the chassis, are therefore may be unintentionally damaged. To
prevent physical damage to modules:
1. Always keep the modules in their protective shipping containers until installed
in the chassis. These containers also protect against ESD.
2. Avoid piling up modules.
3. While inserting modules in their chassis slots, support the modules and make
sure their components do not touch the chassis structure, nor other modules
while sliding into position.
2.2 Site Requirements

Warning
Before connecting this product to a power source, make sure to read the
Handling Energized Products section at the beginning of this manual.
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).
2-4 Site Requirements Megaplex-4100 Ver. 2.0

Caution Megaplex-4100 PS modules which do not have a power ON/OFF switch 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).
Caution 1. 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.
2. 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.
3. 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.
4. Megaplex-4100 chassis must always be connected to FGND (protective
ground).
Special ordering options with preconfigured floating ground settings are available.
Contact your local distributor for more information. When working with FXS voice
modules, see also Frequently Asked Questions section in the VC-4/4A/8/8A/16
Installation and Operation Manual.
Payload Connections
For information regarding connections to port types not covered below, refer to
the corresponding module Installation and Operation Manual.
Connections to E1 and T1 Ports

Megaplex-4100 systems may be equipped with external E1 and T1 ports. The
maximum allowable line attenuation between a Megaplex-4100 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.
Megaplex-4100 Ver. 2.0 Site Requirements 2-5

The E1 and T1 ports located on Megaplex-4100 M8E1 and M8T1 modules are
terminated in 44-pin female D-type connectors. RAD offers special adapter cables
for terminating the ports in standard RJ-45 or BNC connectors (see the module
Installation and Operation Manuals).
Connections to SHDSL Ports

The SHDSL ports of a M8SL module have ITU-T Rec. G.991.2 interfaces terminated
in a 40-pin female SCSI connector. RAD offers special adapter cables for
terminating the ports in standard RJ-45 connectors (see the Installation and
Operation Manuals of the specific modules).
Each SHDSL port requires one unloaded 24 AWG or 26 AWG twisted pair. The
maximum range depends on the data rate and pair gage. Table 2-1 lists typical
ranges over 2-wire 24 AWG and 26 AWG lines 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.
Table 2-1. Typical SHDSL Ranges over 24 AWG and 26 AWG Lines
Data Rate 24 AWG 26 AWG
[kbps] [km] [miles] [km] [miles]
256 9.0 5.5 7.1 4.4
512 7.7 4.7 5.9 3.6
768 7.0 4.3 5.6 3.5
1024 6.2 3.8 4.4 2.7
1536 4.7 2.9 3.9 2.4
2048 4.0 2.4 3.5 2.1
Connections to SDH/SONET Ports

SDH/SONET ports have STM-1/OC-3 ports. Each port has a socket for installing
the desired type of SFP transceiver. RAD offers SFPs that meet a wide range of
system requirements, including:
• Optical interfaces: SFPs with 1310 nm short-haul interfaces for use over
multimode fibers, or 1310 and 1550 nm long-haul interfaces for use over
single-mode fibers.
• Electrical interfaces, for use over 75 Ω coaxial cables. The SFPs offered by
RAD for this interface are terminated in two mini-BNC connectors.
RAD also offers an adapter cable, CBL-MINIBNC-BNC, that connects to the
mini-BNC connectors and is terminated in BNC connectors, for connection to
patch panels or equipment with BNC connectors.
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.

Connections to Ethernet Ports

Gigabit Ethernet (GbE) payload ports are located on CL.1/155GbE modules, and
10/100 Mbps Ethernet payload ports are located on M8E1, M8T1, and M8SL
modules. These ports either have sockets for installing the desired type of SFP
transceiver, or have fixed UTP interfaces.
RAD offers SFPs that meet a wide range of system requirements, for example,
SFPs with 850 or 1310 nm short-haul interfaces for use over multimode fibers, or
1310 and 1550 nm long-haul interfaces for use over single-mode fibers.
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.
Fixed UTP interfaces (either GbE or 10BASE-T/100BASE-TX) are terminated in an
RJ-45 connector. GbE interfaces always support auto-negotiation;
10BASE-T/100BASE-TX interfaces support MDI/MDIX crossover and therefore can
always be connected through a “straight” (point-to-point) cable to any other
type of 10/100BASE-T Ethernet port (hub or station).
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.
Connections to Station Clock

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:
• 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:
• 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.

Note One of the contacts in the station clock connector is used to sense the
connection of the unbalanced adapter cable (see Appendix A). Therefore, do not
connect cables with more than two pairs when you want to use the balanced
interface.
• 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.
Note
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.
Management Connections
Ethernet Connections to CL Modules

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).
Connection to Serial Port

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.
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.

Connections to 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:
• 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).
Caution
Protection devices must be used to ensure that the contact ratings are not
exceeded. For example, use current limiting resistors in series with the contacts, and
place voltage surge absorbers across the contacts.
The relays are controlled by software, and therefore the default state (that
is, the state during normal operation) can be selected by the user in
accordance with the specific system requirements.
• +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.
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 +45°C (32
to 113°F), at a relative humidity of up to 90%, non-condensing.
Most of the Megaplex-4100 modules are cooled by free air convection. 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:
• 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.
Note The serial control port is normally used only during preliminary configuration, and
for maintenance purposes. If you cannot obtain a shielded control cable, make
sure to connect the cable only for the minimum time required for performing the
task.
• 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.3 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
• 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.4 Required Equipment

The additional cables you may need to connect to the Megaplex-4100 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-10 Required Equipment Megaplex-4100 Ver. 2.0

2.5 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.
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; in addition, each slot is keyed,
therefore it is not possible to install the wrong module type.
Megaplex-4100 Ver. 2.0 Mounting the Megaplex-4100 Unit 2-11

Caution 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.
Sl ot PS- A P S-B I /O 1 I/O 2 I /O 3 I/O 4 I /O 5 C L-A CL-B I/O 6 I/O 7 I/O 8 I/O 9 I/O 10
- -
- -
- -
PS Slo ts I/O Slots CL Slots I/O Slots
Figure 2-2. Megaplex-4100 Enclosure, Typical Rear View
Front Panel
The front panel of the Megaplex-4100 enclosure includes labels for the system
status indicators.
Figure 2-3 identifies the front panel indicators, and Table 2-2 describes indicator
functions.
POWER SUPPLY
B A
SYSTEM
ALARM TEST
MEGAPLEX-4100
Figure 2-3. Megaplex-4100 Enclosure, Front Panel
2-12 Mounting the Megaplex-4100 Unit Megaplex-4100 Ver. 2.0

Table 2-2. Megaplex-4100 Front Panel Indicators
Indicator Function
POWER SUPPLY A, B Lights in green when the corresponding PS module is on, provided one of the CL
modules is active
SYSTEM TEST Lights in yellow when a test (or loopback) is being performed in the Megaplex-4100
SYSTEM ALARM (red) Flashes in red when a major and/or critical alarm has been detected in the
Megaplex-4100
Note
The indicator functions listed in Table 2-2 are the default functions. When the
alarm masking and/or alarm inversion functions are used (see Chapter 4 for
details), the meaning of the various alarm indications may change.
Installing PS Modules
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
Warning the PS module before removing it from the enclosure. The installation and
High preparation of the module shall be done by a qualified person who is aware of
Voltage 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: 200W 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 which do not include a
power on/off switch will 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.

Grounding Gr ounding
PS/AC PS/DC P S/DC
Screw Screw
Fan Fa n
DC Input
DC Input Connec tor
Connector
VDC-IN VDC-IN V DC-IN
Power
Switch RTN +72 -48
- -
+ 72 V
Input V oltages + 72 V
P
+ - 48 V + - 24 V
O
W
ON Indicat or
E
100-120VAC Input Voltage ON ON
R 200-240VAC Range Marking
Grounding
Screw
AC Power
Connector
AC-Powered Module -48 VDC-Powered Module 24 VDC-Powered Module
Figure 2-4. Typical Megaplex-4100 PS Module Panels

The PS modules support the connection of an external feed and ring voltage
source, e.g., a Ringer-2000 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 distributor for more information.
The jumpers of a typical PS module (PS/DC or PS/AC) are identified in Figure 2-5.
BGND = FGND
48/24 VDC Positive
Line Connected
YES to Frame Ground
48/24 VDC Positive

Line not Connected
NO
to Frame Ground
GND = FGND
Signal Ground
Connected
YES to Frame Ground
Signal Ground not

Connected
NO
to Frame Ground
NO YES NO YES
Figure 2-5. Typical PS Module, Location of Internal Jumpers

• Jumper designated GND=FGND. This jumper 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.
• Jumper designated BGND=FGND. This jumper 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.
Note 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 Installation and Operation Manuals
of the modules installed in the chassis for proper setting of their ground-control
jumpers.

Installing a PS Module
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, and disconnect the cable(s)
Warning from the module before it is removed from the chassis.
1. Make sure the module POWER switch is set to OFF.

2. Insert the PS module in the PS-A slot, and fasten it with the two screws.
3. Connect the power cable.
4. 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
• For modules with POWER switch – set the module POWER switch to ON.
Removing a PS Module
1. For modules with POWER switch – set the module POWER switch to OFF.
2. Disconnect the power cable(s) connected to the module.
3. Release the two module screws
4. 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.
Note When only one CL module is installed in the chassis, it must always be installed in
slot CL-A.
Moreover, if CL module B is programmed, CL module A must also be programmed
in the chassis.
The following types of CL modules are offered:

• CL.1: basic version, includes the chassis management and timing subsystem,
and a cross-connect matrix for TDM traffic
• CL.1/155: in addition to the functions provided by the CL.1 version, includes
two SDH/SONET ports with STM-1/OC-3 interfaces, and the capability to route
traffic to/from the STM-1/OC-3 links to the modules installed in the chassis.
• CL.1/155GbE: in addition to the functions provided by the CL.1/155 version,
includes two GbE ports (with SFPs or with copper interfaces, in accordance

with order), and has the capability to route packet traffic to/from modules
with Ethernet payload ports installed in the chassis.
• CL.1/GbE: in addition to the functions provided by the CL.1 version, includes
two GbE ports (with SFPs or with copper interfaces, in accordance with
order), and has the capability to route packet traffic to/from modules with
Ethernet payload ports installed in the chassis.
Figure 2-6 shows typical CL module panels. Table 2-3 describes the functions of
the panel components.
CL-1 CL-1 CL-1/GbE CL-1

155 155/GbE
ON LINE ALM ON LINE ALM ON LINE ALM ON LINE ALM

L G L G
b b
TX
TX
TX
I I
N E N E
K 1 K 1
RX
RX
RX
1 1
L G L G
I b I b
TX
TX
TX
N E N E
K 2 K 2
RX
RX
RX
2 2
L L L L
C O C O C O C O
L S ON LINE LOS L S ON LINE LOS L S ON LINE LOS L S
O O O O
C E C E C E C
X X K O X
K O K O K O
N N N N
L L L
A I A I A I A
C N C N C N C
E T K E T K E T K E T
T T T T
H L H L H L H L
I I I I
N N N N
K K K K
C C C C
A O A O A O A O
L D N L D N L D N L D N
A C T A C T A C T A C T
R E R R E R R E R R E R
M O M O M O M O
L L L L
CL.1 CL.1/155 CL.1/GbE with Copper CL.1/155GbE with

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

Table 2-3. Module CL, Panel Components
Item Function
ON LINE Indicator Provides the following indications:

• Master/standby status: lights in green on the master (active) CL module,
and flashes slowly in green on the standby CL module
• Test status: on the master (active) CL module, lights in yellow if a test is
being performed on the Megaplex-4100
• Software downloading: flashes rapidly in green
• Software decompression: flashes in yellow
ALM Indicator On the master CL module, provides the following indications (see also NOTE
below):
• Flashes in red when at least one major or critical alarm has been detected
in the Megaplex-4100.
• Lights in red when alarms have been detected in the Megaplex-4100, but
the highest alarm severity is minor or warning.
On the standby CL module, this indicator is always off, even while an alarm
condition is present
CLOCK Connector RJ-45 connector for the station clock input and output signals.
The built-in indicators (active only on the master CL module) provide the
following indications:
ON Indicator Lights in green when the station clock port is configured as connected
LOS Indicator Lights in red to indicate a loss-of-signal condition at the station clock port,
when configured as connected
CONTROL ETH Connector RJ-45 connector for the CL 10/100BASE-T Ethernet management port.
The built-in indicators (active only on the master CL module) provide the
following indications:
LINK Indicator Lights in green when the port is connected to an active Ethernet hub or switch
ACT Indicator Lights in yellow when this port transmits and/or receives data
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 STM-1/OC-3 ports
(CL.1/155 and CL.1/155GbE
versions only)

Item Function
LINK Indicators – per port Status indicators for STM-1/OC-3 ports. These indicators are active only when
(CL.1/155 and CL.1/155GbE the corresponding port is equipped with an SFP and configured as connected:
versions only)
ON LINE Indicator Lights in green when the corresponding port is active (that is, carries
SDH/SONET traffic, and there is no major alarm condition, nor any test on this
port).
Lights in yellow when a test is active on the port
LOS Indicator Lights in red to indicate loss-of-signal at the corresponding port.
Any other alarm condition related to SDH/SONET traffic handled by the port is
indicated only by the CL general alarm (ALM) indicator
GbE 1, 2 Connectors Sockets for installing SFP transceivers for the corresponding GbE ports,
(CL.1/GbE and CL.1/155GbE or RJ-45 connectors
version only)
GbE 1, 2 Indicators – per Status indicators for the corresponding GbE port.
port (CL.1/155GbE version These indicators are active only when the corresponding port is configured as
only) connected, and for optical ports – when the port is equipped with an SFP:
LINK Indicator Lights in green when the port is connected to an active Ethernet hub or switch
ACT Indicator Lights in yellow when the port transmits and/or receives data
Note
The ALM indicator functions listed in Table 2-3 are the default functions. When
the alarm masking and/or alarm inversion functions are used (see Chapter 4 for
details), the meaning of the various indications may change.
Preparing CL.1/155 and CL.1/155GbE Modules for Installation

Before installing a CL.1/155 or CL.1/155GbE module, you may have to install the
prescribed types of SFPs:
• To install an SFP, use the procedure given in the Installing an SFP section.
• To replace an SFP, use the procedure given in the Replacing an SFP section.
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 SFPs with optical interfaces.
However, the same procedures apply for SFPs with electrical (copper) interfaces.
³ To install the SFP:

• Lock the latch wire 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 latch wire.
Figure 2-7. Locking the Latch Wire of a Typical SFP

1. Carefully remove the dust covers from the corresponding SFP socket of the
CL.1/155 module, and from the SFP electrical connector.
2. Orient the SFP as shown in Figure 2-6, and then insert the rear end of the
SFP into the module socket.
3. 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 latch wire as a pulling handle, and then repeat the procedure.
4. If necessary, repeat the procedure for the other SFP.
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 CL-A and/or CL-B slots (see also Note on page
2-16). When two CL modules are installed, redundancy is available. In this case,
the module installed in slot CL-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.
³ To interconnect the expansion ports of CL.1/155 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 good CL modules, the standby module
can be removed/replaced with minimal disruption of Megaplex-4100 services:
when you replace the on-line CL module, the Megaplex-4100 will automatically
switch to the standby module, provided that module is OK.
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.
• For CL.1/155 and CL.1/155GbE modules, which have additional traffic
interfaces, removing a module always disconnects the traffic carried by the
active payload interfaces (GbE and/or STM-1/OC-3) 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 1+1 redundancy 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. Whenever possible, connect the supervision terminal directly to the CONTROL
DCE connector of the on-line CL module, and log in as administrator.
3. Use the Configuration>System>Reset Device screen 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.
Note
The command will not be executed if a fault is detected in the module that is to
become the on-line module. In this case, the ON LINE indicators state will not
change.
5. You can now disconnect the supervision terminal, and remove the module.
6. After installing again 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 good CL module of the same type be installed
in the free CL slot. The replacement can be temporary.
In this case, after inserting the additional CL module, first 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 the database update command, #, and then wait until the alarm CL DB
CHECKSUM IS DIFFERENT 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 I/O module Installation
and Operation Manual.
Installing Blank Panels

Install blank panels in all the chassis slots that are not occupied by modules.
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 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

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.6 Connecting to Megaplex-4100
Grounding the Megaplex-4100
Before connecting any cables and before switching on this instrument, the
protective ground terminals of this instrument must be connected to the
Warning 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. The
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.
2-24 Connecting to Megaplex-4100 Megaplex-4100 Ver. 2.0

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 the Megaplex-4100. For example, the circuit breaker used to protect
the supply line to the 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 the Ringer-2200N offered by
RAD. The 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 the Megaplex-4100 is turned on.
Turn off the Ringer-2200N external voltage source, or disconnect the external
voltages, only after the Megaplex-4100 is turned off.
Connecting Cables to Megaplex-4100 CL Ports

This section provides information on the connections required by the various CL
module versions.
³ 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.
Megaplex-4100 Ver. 2.0 Connecting to Megaplex-4100 2-25

³ 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.
³ To connect to a management station, Telnet host or Web browser:

The link to network management stations using SNMP, to Telnet hosts and/or
Web browsers 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).
³ 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 Cables to CL.1/155 and CL.1/155GbE SDH Links
Connection Instructions for Optical Cables

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 CL.1/155 and CL.1/155GbE SDH 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. 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 CL.1/155 and CL.1/155GbE SDH

Links
The SFPs offered by RAD for the CL.1/155 SDH 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 CL.1/155 and CL.1/155GbE SDH 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 to I/O Modules

Refer to corresponding module Installation and Operation Manual.
Megaplex-4100 Ver. 2.0 Connecting to Megaplex-4100 2-27


Chapter 3
Operation
This Chapter provides general operating instructions and preliminary configuration
instructions for Megaplex-4100 units.
The information presented in this Chapter is organized as follows:
• Turning on: Section 3.1
• Indications: Section 3.2
• Default settings: Section 3.3
• Configuration and management alternatives for Megaplex-4100: Section 3.4
• Turning off: Section 3.5
3.1 Turning Megaplex-4100 On

When turning the 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 the 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 the 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.
3. 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 CL-A (this module will be, by
default, the active CL module). Use a straight (point-to-point) cable.
Megaplex-4100 Ver. 2.0 Turning Megaplex-4100 On 3-1

Chapter 3 Operation Installation and Operation Manual
Note You can also connect the terminal in parallel to the CONTROL DCE connectors of
both CL modules installed in the Megaplex-4100, using a Y-cable.
³ To turn the Megaplex-4100 on:

Caution
When an external feed and ring voltage source is connected to the PS modules
installed in the Megaplex-4100, always turn that source on only after the PS
module(s) have been turned on.
1. Set the POWER switch(es) on the rear panel(s) of the PS module(s) to ON.
If you are using DC-powered PS modules without a POWER switch, it is
necessary to 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 the Megaplex-4100
performs its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4100. A typical display is shown in Figure 3-1.
Loading ...
Decompressing to RAM.
Processing archive: FLASH

Extracting MPCLX.BIN
.................................................................. CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
Figure 3-1. Typical Power-Up Display
Note The name of the file displayed on your Megaplex-4100 screen may be different.
4. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active (master) 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 Turning Megaplex-4100 On Megaplex-4100 Ver. 2.0

Installation and Operation Manual Chapter 3 Operation
3.2 Indications
The indications provided during normal operation are described below.
Note
For a complete description of Megaplex-4100 indicator functions, refer to
Chapter 2.
System Indications
1. As long as the Megaplex-4100 is powered, all its POWER indicators light
steadily.
2. The ON LINE indicator of one of the CL modules must light steadily.
3. The front panel TEST indicator must be off, unless a test has been activated
on the Megaplex-4100 (in this case, the ON LINE indicator of the master CL
module also lights in yellow).
4. The front panel ALARM indicators and the CL ALM indicators must be off.
However, they may flash or light, as long as one or more of the
Megaplex-4100 ports is not connected to operational equipment.
CONTROL ETH Interface Status Indications

If a Megaplex-4100 CONTROL ETH port is not yet connected to an active LAN, the
corresponding LINK and ACT indicators are off.
After connecting the CONTROL ETH port to an active LAN, the corresponding LINK
indicator must light. The ACT indicator of the port will flash, or appear to light
steadily, in accordance with the traffic.
SDH/SONET Interface Status Indications (CL.1/155 and CL.1/155GbE

Only)
The ON LINE indicator lights in green to indicate that the corresponding link is
active.
If an SDH/SONET port is not yet connected to operational equipment, the
corresponding port LOS indicator lights. However, if the equipment at the other
end of the link is operational and the link is physically connected, the port LOS
indicator must turn off.
GbE Interface Status Indications (CL.1/GbE and CL.1/155GbE Only)

If a GbE port is not yet connected to an active LAN, the corresponding LINK and
ACT indicators are off.
After connecting the GbE port to an active LAN, the corresponding LINK indicator
must light. The ACT indicator of the port will flash, or appear to light steadily, in
accordance with the traffic.
Megaplex-4100 Ver. 2.0 Indications 3-3

CL CLOCK Interface Status Indications

The ON indicator lights when the corresponding station clock interface is enabled
and connected to an operational clock source. In this case, the LOS indicator of
the corresponding station clock interface must be off.
3.3 Default Settings

Table 3-1 lists the Megaplex-4100 factory default parameters.
For factory default parameters of I/O modules, refer to the corresponding module
Table 3-1. Megaplex-4100 Factory Default Parameters
Parameter Factory Default Value Path
Admin Status Down Configuration>Physical Layer>CL>

CL-A(B)>Station Clock
Admin Status Down Configuration>Physical Layer>CL>

CL-A(B)>Ethernet>All Ports(GBE 1,
GBE 2)
Admin Status Up Configuration>Physical Layer>CL>
CL-A(B)>SDH/SONET>Link 1(2)
Alarm ID[1 - 2104] 3 Configuration>System>Alarms

Configuration>Trap Masking
Auto Negotiation Disable Configuration>Physical Layer>CL>

GBE 2)
Baud Rate 115.2 KBPS Configuration>System>Control
Port>Serial Port
BP 1 Configuration>Applications>Ethernet
Services>Flows>Bridge Port Mapping-
Flow
BP User Name Empty string Configuration>Applications>Etherne

Flow
Clock Rate 2048 KBPS Configuration>Physical Layer>CL>

Contact Person Name of contact person Configuration>System>Management>

Device Info
C-VLAN ID 1 Configuration>Applications>Etherne
Flow
C-VLAN Type Unaware Configuration>Applications>Etherne

Flow
3-4 Default Settings Megaplex-4100 Ver. 2.0

Default Gateway 0.0.0.0 Configuration>System>Management>

Host IP
Device Name Empty string Configuration>System>Management>

Device Info
EED Threshold 1E-3 Configuration>Physical Layer>CL>
Fault Propagation Enable Configuration>System>Fault

Propagation
Flow 251 Configuration>System>Management>
Flow
Flow Control Disable Configuration>Physical Layer>CL>

GBE 2)
Frame Structure STM-1 Configuration>Physical Layer>CL>

CL-A(B)>SDH/SONET>Card
Configuration
In Band Management Off Configuration>Physical Layer>CL>

CL-A(B)>SDH/SONET>Link 1(Link 2,
All Links)>DCC Configuration
Interface Type Balance Configuration>Physical Layer>CL>

IP Address 0.0.0.0 Configuration>System>Management>

Host IP
Line Code HDB3 Configuration>Physical Layer>CL>

Managers ID First free index number Configuration>System>Management>

Manager List
Object ID radMP4100 Configuration>System>Management>

Device Info
Password 1234 Configuration>System>Control

Port>Serial Port>Change Password
Port First bridge port of first slot available for Configuration>Applications>Etherne

connection to flow Services>Flows>Bridge Port Mapping-
Flow
Profile Number 1 Configuration>System>Signaling

Profile
Rate 100 Mbps Configuration>Applications>Etherne

Flow
RDI on Fail Enable Configuration>Physical Layer>CL>
Megaplex-4100 Ver. 2.0 Default Settings 3-5

RDI on path trace Disable Configuration>Physical Layer>CL>

Configuration>Common PDH LVC
Parameters
RDI on signal label Disable Configuration>Physical Layer>CL>

Configuration>Common PDH LVC
Parameters
Read Community public Configuration>System>Management>

Host IP
Rx Busy[0 - f] 0F Configuration>System>Signaling
Profile
Rx Gain Limit Short Haul Configuration>Physical Layer>CL>

Rx Idle[0 - f] 00 Configuration>System>Signaling
Profile
SD Threshold 1E-6 Configuration>Physical Layer>CL>

Security Timeout None Configuration>System>Control
Port>Serial Port
Slot First slot on which a bridge port is Configuration>Applications>Etherne

available for connection to flow Services>Flows>Bridge Port Mapping-
Flow
SNMP Enable Configuration>System>Management>

Mng Access
SNMPv3 Disabled Configuration>System>Management
Source Internal Configuration>System>Clock Source
Speed & Duplex 1000 MBPS Full Duplex Configuration>Physical Layer>CL>

GBE 2)
SP-VLAN 0 Configuration>Applications>Etherne
Flow
SSM Disable Configuration>Physical Layer>CL>

Subnet Mask 0.0.0.0 Configuration>System>Management>

Host IP
Sys Description Depends on equipment version Configuration>System>Management>

Device Info
Telnet Enable Configuration>System>Management>

Mng Access
3-6 Default Settings Megaplex-4100 Ver. 2.0

Transmit Timing Source Configuration>Physical Layer>CL>

> (System) CL-A(B)>Station Clock
Trap Community public Configuration>System>Management>

Host IP
Trap Send Yes Configuration>System>Alarms

Configuration>Trap Masking
Tx Clock Based on SSM Yes Configuration>Physical Layer>CL>

Configuration
VLAN ID [1 - 4094] 100 Configuration>System>Management>
Flow
VLAN Priority Tag [0 - 7 Configuration>System>Management>
7] Flow
WEB Enable Configuration>System>Management>

Mng Access
Write Community private Configuration>System>Management>

Host IP
3.4 Configuration and Management Alternatives

The Megaplex-4100 configuration activities can be performed by means of the
following:
• Supervision terminal
• Telnet
• Web browser, using the ConfiguRAD utility
• SNMP-based network management systems, e.g., the RADview network
management system (refer to the RADview User's Manual for instructions).
Note Megaplex-4100 also supports SNMPv3, which provides authentication and privacy
capabilities that replace the basic SNMP community-based authentication
available under SNMPv1.
The user can select whether to enable management by means of Telnet, SNMP,
and/or Web browsers: only the supervision terminal is always able to configure
the Megaplex-4100.
The capabilities of the four options listed above are similar, except that before
using Telnet, Web browsers and/or network management systems, it is necessary
to perform preliminary configuration using the supervision terminal.
The Megaplex-4100 supports simultaneous management sessions: it is user’s
responsibility to prevent access conflicts and configuration errors that may occur
when multiple users simultaneously access the same equipment.
Megaplex-4100 Ver. 2.0 Configuration and Management Alternatives 3-7

Access Levels for Configuration and Management

Megaplex-4100 supports three access levels, which determine the functions the
users can perform using supervisory terminals, Telnet hosts, and Web browsers.
Note When SNMPv3 security features are enabled, the term user refers to an SNMP
management station using part, or all of the SNMPv3 security features, and the
users’ authorizations are determined by configuring the parameters related to
the view-based security model (VACM) aspect of SNMPv3. Refer to Section 0 and
Chapter 4 for details.
The access level is determined by the user name, and the protection against
unauthorized access is conferred by passwords. The access levels supported by
Megaplex-4100 are described in Table 3-2.
Table 3-2. Megaplex-4100 Access Levels
Access Level User Name Menus Accessible at this Level
Administrator su All the menus
Technician tech Alarm Configuration (on Configuration menu),

Inventory, Monitoring, Diagnostics
Monitor user Inventory, Monitoring
The default passwords for all the levels are identical, 1234. The passwords can be
changed at the administrator level, using Configuration>System>Control Port>
Serial Port>Change Password.
Notes P
• The password is not case-sensitive.

• If the administrator password has been changed and is not known, contact
RAD Technical Support Department for help.
Working with Supervision Terminal

Configuration activities are performed by means of an ASCII terminal (or a PC
running a terminal emulation program) directly connected to one of the CL
CONTROL DCE connectors. A supervision terminal also permits performing the
preliminary configuration that enables other types of management access.
Any standard ASCII terminal (dumb terminal or personal computer emulating an
ASCII terminal) equipped with an RS-232 communication interface can be used to
configure and control the Megaplex-4100 operation.
The software necessary to run the Megaplex-4100 supervision program is
contained in the Megaplex-4100 CL modules. Moreover, the Megaplex-4100 CL
modules store all the configuration information generated or altered during the
communication with the terminal: no information is stored in the terminal.
3-8 Configuration and Management Alternatives Megaplex-4100 Ver. 2.0

Note For proper display of screens on terminals, you must:

1. Select a fixed-pitch system font for the display. Use your operating system
documentation to find how to select a proper font.
2. Configure the terminal utility to use VT-100 terminal emulation. If you are
using the Hyper Terminal utility available with Windows(™), configure the
utility to use the 132-column mode (Properties > Settings > Terminal Setup >
132 column mode).
³ To log in with a supervision terminal:

1. Connect a terminal to one of the Megaplex-4100 CONTROL DCE connectors.
2. If necessary, turn the Megaplex-4100 on as described in Section 3.1.
Note
• The CONTROL DCE port default data rate can be configured for any standard
rate in the range of 0.3 to 115.2 kbps (the factory-default data rate is
115.2 kbps).
• If the terminal is configured to use a word format differing from the CONTROL
DCE port (one start bit, 8 data bits, no parity and one stop bit), you may see
only random strings of characters, or there will be no response to the pressing
of the <Enter> key. Make sure you use the correct word format.
3. If the terminal has been configured to use the default parameters, after the
power-up initialization it will display the cursor (a blinking underscore) at the
home position of the screen (top left-hand corner).
4. Establish communication with the Megaplex-4100 by pressing <Enter> several
times in sequence (this enables automatic rate identification). You may see a
few status messages, and then you will see the log-in screen. A typical screen
is shown in Figure 3-2.
MP-4100
USER NAME:
PASSWORD:
ESC - clear; & - exit 0 M/ 1 C

-----------------------------------------------------------------------------
Figure 3-2. Terminal Log-In Screen

5. If the Megaplex-4100 default user name and password have not yet been
changed, log in as follows:
Type the default user name, su, and then press <Enter>.
Type the default password, 1234, and then press <Enter>.

6. If your password is accepted, you will see the Megaplex-4100 main menu. A
typical main menu screen is shown in Figure 3-3.
If your log-in is not accepted, after pressing <Enter> the user name and
password fields are cleared. In this case, try entering the user name and
password again.
MP-4100
Main Menu
1. Inventory >
2. Configuration >
3. Monitoring >
4. Diagnostics >
5. File Utilities >
>
Please select item <1 to 5>

%-Db Update; #-Db Undo; $-Sanity
ESC-prev.menu; !-main menu; &-exit; @-output; 1 M/ 1 C
-----------------------------------------------------------------------------
Figure 3-3. Megaplex-4100 Main Menu
Preliminary Configuration Sequence

The purpose of the preliminary configuration session is to prepare the minimal
set of parameters needed to manage the Megaplex-4100 using a supervision
terminal.
In particular, during preliminary configuration you can enable access by Telnet
hosts and Web browsers. However, after the preliminary configuration,
management access is possible only by hosts that are attached to a LAN directly
connected to the CONTROL ETH (Ethernet) port of the active CL module, or at a
remote location from which IP communication to the CL module Ethernet ports is
possible.
Note
To enable management access to the Megaplex-4100 from any relevant location,
it is necessary to fully configure the Megaplex-4100: only full configuration can
permit management traffic to reach the Megaplex-4100 via inband paths.
The steps usually included in the preliminary configuration, as necessary when

starting from the factory defaults, are described in Table 3-3.
For detailed operating instructions, refer to the Chapter 4 section describing each
activity.

Table 3-3. General Megaplex-4100 Configuration Sequence
1 Select the default database Configuration>DB Tools>Default DB
2 If the Megaplex-4100 is equipped with all the Configuration>DB Tools>Load HW

necessary modules, load the hardware
configuration.
Alternatively, configure the modules and then Configuration>System>Card Type
reload the factory default parameters
installed in the Megaplex-4100. You can also
program modules not yet installed in the
chassis
3 Configure the preliminary set of IP Configuration>Quick Setup

communication parameters
6 Configure Megaplex-4100 management agent Configuration>System>Management>Host IP
7 Configure management access Configuration>System>Management>Mng Access
9 Set Megaplex-4100 real-time clock Configuration>System>Date & Time

• Station clock ports Configuration>Physical Ports>CL>CL-A, CL-B>
• SDH/SONET ports (make sure to configure SDH/SONET
the frame structure) Configuration>Physical Ports>CL>CL-A, CL-B>ETHERNET
• GbE ports (make sure to configure the GbE
port redundancy parameters) Configuration>Physical Ports>CL>CL-A, CL-B>Station
Clock
12 Configure the physical ports of the I/O Configuration>Physical Ports>I/O>I/O-1 to I/O-10

modules (E1, T1, SHDSL, Ethernet, etc.)
13 Configure the virtual ports on the SDH/SONET

ports of the CL modules:
• PDH ports Configuration>Virtual Ports>CL>PDH
• High-order VCs Configuration>Virtual Ports>CL>HVC>CL-A, CL-B
14 Configure the virtual ports of the I/O modules Configuration>Virtual Ports>I/O>I/O-1 to I/O-10


order:
• Configure the prescribed bundles Configuration>Virtual Ports>Bundles
• Configure the prescribed virtually Configuration>Virtual Ports>CL>VCAT>CL-A, CL-B
and where necessary, also configure
virtually concatenated group redundancy
17 Configure path protection parameters for Configuration>Virtual Ports>IO

each virtual and I/O module internal port
20 Configure internal cross-connections Configuration>System>TS Assignment
21 Configure Megaplex-4100 internal mapping Configuration>System>Mapping

Configuration>DB Tools>Load DB. Repeat the relevant
steps as needed to create a new database
Note
• All the following menus are reached after opening the Configuration menu.
• During the configuration procedure, save the changed values, but update the
database only after completing the configuration activities.
³ Select the default database:

1. Open the DB Tools menu.
2. Select Default DB.
3. Select the default database number, 1.
³ Initialize the Megaplex-4100:

1. Select Load HW on the DB Tools menu.
2. Select Update DB on the DB Tools menu to activate the default configuration
for all the hardware installed in the Megaplex-4100. When prompted to
confirm, type Y.

The new database takes effect immediately. You will see the message
Configuration File Update is in Process while the database is saved in the CL
module flash memory.
³ Reload the factory defaults:

1. Select Factory Default on the Configuration>System menu.
³ To program modules not yet installed in the Megaplex-4100 chassis:

1. Select Card Type on the System menu.
2. Move the cursor to the desired slot.
3. The selections supported for each slot are automatically displayed under the
slots table. Type the item number corresponding to the desired selection and
then press <Enter>.
4. Repeat Steps 2, 3 for each slot.
³ Configure the serial port parameters:

1. Open Control Port on the System menu.
2. Open Serial Port on the Control Port submenu.
3. Select the desired value for Speed (recommended value: 115200).
³ Configure the Megaplex-4100 management agent parameters:

1. Open Host IP on the System>Management menu.
2. Configure the prescribed values for the following parameters:
IP Address. Enter the IP address of the Megaplex-4100 management
agent, using the dotted-quad format (four groups of digits in the range
of 0 through 255, separated by periods).
IP Mask. Enter the IP subnet mask of the Megaplex-4100 management
agent. Make sure to select a subnet mask compatible with the selected IP
address, and whose binary representation consists of consecutive
“ones”, followed by the desired number of consecutive “zeroes”.
Default Gateway. Specify the IP address (usually an IP router port) to
which the Megaplex-4100 management agent will send packets when the
destination IP address is not within the subnet specified in the Mask field.
Type the desired IP address, using the dotted-quad format. Make sure
that the IP address is within the subnet of the host IP address. The
default value, 0.0.0.0, means that no default gateway is defined.
Communities: to configure SNMP management when SNMPv3 is Disabled,
enter the prescribed Read, Write, and Trap community names, or leave
the defaults unchanged.
When SNMPv3 is Enabled¸ the community fields are not displayed.
Note
The community names are case-sensitive.

³ Configure the Ethernet port parameters:

1. Open Control Port on the System menu.
2. Open ETH on the Control Port submenu.
3. For each CL module, select UP for Admin Status. You may also assign a user
name (up to 10 characters) to each port.
4. At this stage, you may leave None for Routing Protocol.
³ Configure management access options:

1. Open Management on the System menu.
2. Open Mng Access on the Management submenu.
3. Select Enable or Disable, as prescribed, for SNMP, Telnet and Web.
³ Configure specific management stations:

1. Open Management on the System menu.
2. Open Manager List on the Management submenu.
3. Type a (add) and then press <Enter> to start the configuration of a new
management station.
4. Select the prescribed values for each parameter.
5. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new station. To display the Manager List
again, press ESC.
6. Repeat the process until all the desired management stations have been
defined.
³ Set the Megaplex-4100 real-time clock:

1. Open the System menu.
2. Select Date & Time on the System menu.
3. Open Set Date Format screen, and select the desired date format.
Note dd stands for day, mm for month and yyyy for year.
4. When done, save and then set each component of the time-of-day and date.
To change, select the desired item and then type the desired value. Confirm
each change by pressing <Enter>.
Notes • Time must be entered in the 24-hour format.

• It is recommended to set the time about one minute beyond the desired time,
and then press <Enter> at the correct instant.
³ Save the changes to the default database:

• On the DB Tools menu, select Update DB to save and activate the new
configuration.
You may also use the % shortcut.

Configuring Megaplex-4100 via Supervisory Terminal

Megaplex-4100 operating mode and all of its functions are controlled by a set of
configuration parameters organized as a database, which is stored in the flash
memory on the Megaplex-4100 CL module. The parameters in the database are
selected by the user in accordance with the requirements of each specific
application.
To provide a starting point for the user, RAD provides a fixed set of
factory-default parameters. The factory defaults are not modified by user
configuration activities, and therefore these factory-defaults can be reloaded
whenever needed.
The preparation of the desired set of configuration parameters is made in
accordance with a set of rules, which together form the Megaplex-4100
supervision utility, or user interface. The supervision utility is used to
communicate with the central control subsystem of the Megaplex-4100 located in
the CL modules, using a supervision terminal connected to the control port of the
CL module. The same user interface can also be used by Telnet hosts.
Alternative ways to change the configuration parameters are by means of SNMP
management stations, for example, RADview, and Web browsers.
Preparing New Configuration Parameters

Normally, only one database is needed to store the configuration parameters;
when necessary, one or more additional databases with alternative
configurations may also be prepared and stored in the Megaplex-4100 flash
memory. Megaplex-4100 databases are assigned index numbers in the range of 1
to 10.
At any time, one of the stored databases (the database assigned index number
1) serves as the active (online) database, and it is also the database
automatically loaded upon power-up. Since the active database is stored in flash
memory, the latest configuration parameters are always available upon power-up.
During the preparation of configuration parameters, the central control
subsystem of the Megaplex-4100 dedicates a section of its RAM, called editing
buffer, to this process. The editing buffer contains a copy of a user-selected
database (any of the databases stored by the Megaplex-4100, including the
currently-active database), and only this copy is modified by the commands
entered by the user. Therefore, you can make configuration changes and cancel
them as required without affecting the traffic flow through the Megaplex-4100.
Any changes to configuration parameters remain temporary, and thus are lost if
Megaplex-4100 is powered off or reset, until they are saved to one of the
databases in Megaplex-4100 flash memory. You can decide in which database to
save the changes: this also determines whether the changes take effect
immediately or not.
Two options are available:
• Normally, changes are saved to the active, or online, database. In this case,
the changes are also automatically activated, that is, Megaplex-4100 starts
using the new parameters. As mentioned above, the number of the active

database is always 1, irrespective of the number of the database loaded into

the edit buffer as a basis for changes.
• Alternatively, you can specify the number of another database, using the
Update DB command, in which to store the edit buffer contents. If the
database whose index is specified in the Update DB command is not yet
stored in the flash memory, a database with this index number is created and
the edit buffer contents are stored in it.
Note The storage space used by databases increases after each change. Sometimes,
the remaining storage space is not sufficient to save the updated database, and
you will see Save of Configuration File Failed. In this case, it is necessary to delete
unused databases.
Note that alternative databases may be assigned any desired number, except 1,
because 1 is reserved for the active database.
When preparing alternative databases, it is convenient to change the default
database, that is, the database which is updated when you use the shortcut
% - DB Update:
• If you do not select a specific default database, the shortcut updates the
active database (database 1).
• If you specify another database stored in the flash memory as default, the
shortcut updates the default database. In this case, after preparing the
alternative database, it is recommended to return the default to database 1.
Validity Checks
The Megaplex-4100 control subsystem automatically checks the validity of each
new subset of parameters selected by the user as soon as an attempt to save
them is made, alerts the user to potential conflicts, and rejects erroneous
selections.
The “sanity check” is performed on the configuration parameters stored in the
editing buffer.
This function provides messages which help identify incomplete configuration,
unconnected timeslots, conflicting parameters, inconsistent selection of related
parameter values, etc., so that the parameters can be corrected before
proceeding.
Only after all the validity and sanity checks are successfully passed, can the user
save the new (or modified) set of configuration parameters as a database (this is
made by means of the Update DB command). If the new set is saved under the
number of the active configuration database, the Megaplex-4100 system will
start operating in accordance with the new configuration.
Since the last validated sets of configuration parameters are stored in flash memory,
Megaplex-4100 configuration is not affected when the power is turned off.
However, any changes not yet saved are lost if the Megaplex-4100 is reset or
powered down.

Megaplex-4100 Power-up Process

Upon turn-on, the Megaplex-4100 central control subsystem always loads
database 1, and checks the validity of the configuration data. If everything is OK,
it loads the data into the working memory and reconfigures the system
accordingly. Therefore, the Megaplex-4100 is ready for operation in accordance
with the last configuration stored in database 1 immediately after power is
applied.
If necessary, after power-up another database can be loaded by means of the
Load DB command, and then activated by means of the shortcut % - DB Update.
This database will be assigned index number 1 (that is, will become database 1).
If the configuration data is not valid, the database will not be activated; instead,
a database with factory-default values will be activated. This database will be
assigned index number 1 (that is, will become database 1).
After the operating parameters have been loaded, a process called configuration
set-up, the Megaplex-4100 no longer requires operator attendance.
Organization of Terminal Screens

The Megaplex-4100 is managed via a simple, menu-driven utility that uses a basic
terminal user interface. Figure 3-4 shows a typical utility screen with most types
of items.
MP-4100
Configuration>Physical Ports>IO>I/O 1 (M8E1)>Link 1 (Up)
1. Admin Status (Up)

2. User Name ... ()
3. Line Type > (G.732N-CRC4)
4. Idle Code [0 - ff] ... (7F)
5. Redundancy > (None)
6. Rx Gain > (Short Haul)
7. Data OOS [0 - ff] ... (00)
8. Restoration Time > (CCITT)
9. Cross Connect (DS0)
10. In Band Management > (Off)
11. Interface Type (Balance)
12. Time Slot Assignment >
>

ESC-prev.menu; !-main menu; &-exit; @-output 1 M/ 1 C
-----------------------------------------------------------------------------
Figure 3-4. Typical Megaplex-4100 Supervision Utility Screen

Each screen includes the following main items (refer to Figure 3-4 for typical
appearance):
• Header: identifies the device being configured (Megaplex-4100).
• Status indicator: status indicators may appear in the top right-hand corner to
indicate one or more of the following conditions:

Alarm Indicator (e.g., MAJ): indicates highest severity of the alarm

conditions present in the Megaplex-4100.
B followed by a three-digit number: indicates the number of messages
currently stored in the alarm buffer. B000 means that no messages are
currently in the buffer: this generally occurs only after clearing alarms.
ERROR: displayed after the user action is rejected, for example, because
of an invalid selection or out-of-range value. The indicator disappears
after a valid action is performed.
• Work area: includes a description of the screen, followed by the items
available for the current screen. Each selectable item has its own number.
The screen description identifies the screen (in this example: Link 1), and
also displays navigation data, that is, the path through the Megaplex-4100
menu structure that has been traversed to reach this screen (Configuration>
Physical Ports>I/O>I/O 1>Link 1). If the full path is too long, its beginning is
truncated, in which case an ellipsis … appears.
In addition, the work area includes the terminal prompt, >. The item number
you type appears to the right of the prompt.
The lower part of the work area is also used to display a concise explanation
of the available options and prompts regarding the actions available to you. It
may also display messages that request you to confirm operations such as
configuration changes, resetting, etc., or alerts that errors have been
detected during the evaluation of the parameters selected by you (in this
case, you will see a $ – Sanity option).
• % – DB Update, # – DB Undo : after you make a configuration change, you
must either save it in one of the databases, or undo (cancel) it.
When you press the % hotkey, the changes are saved to the default
database, which is usually database 1, unless you selected a different default
database.
Changes that have been saved to a database using the Update DB command
will take effect only after that database is selected as active database.
• Save: after you make configuration changes on certain screens, you must
temporarily save the changes in the edit buffer, or undo (cancel). Changes
that have been saved can take effect only after the current database is
updated.
The indication that changes have been made is provided by the appearance
of the S – Save item in the bottom line of the configuration screen. After
saving, the S – Save item disappears.
• Bottom line: displays the keys used for navigation.
ESC returns to the previous screen (not relevant for main menu)
! returns directly to the main menu (not relevant for main menu)
&– ends the utility and displays the log-in screen again.
@– increases the area dedicated to the on line display.
?– displays additional help specific to the current screen.

In addition, the number of management connections (C) and the number of

managers (M) currently connected to the Megaplex-4100 is shown at the
lower right-hand corner (in Figure 3-4, this is 1 manager via one management
connection). The managers’ number indicates the total number of
management sessions active at the instant the screen was displayed,
irrespective of type (terminal, Telnet, SNMP or Web browser). If no user is
logged in, the number of managers is 0.
• The last two rows are reserved for displaying the last two alarms, or user
prompts.
Note
It is normal to see at least a RESET OCCURRED event after power up. If not all of
the Megaplex-4100 ports are connected to operating equipment, you may also
see alarms reporting loss of signals, etc.
General Supervision Terminal Operating Procedures
³ How to use the terminal to perform a desired activity:

• To select a menu item, type the corresponding line number and then press
<Enter>. This will either …
… display a submenu or a parameter selection screen …
or …
… let you type the (free text) parameter value in the same row
or …
… toggle the current value of the corresponding parameter (relevant to
ENABLE/DISABLE or ON/OFF selections).
• The type of response to be expected after selecting a menu item is indicated
as follows:
> Selecting that item will display a submenu or a parameter

selection screen (see for example item 6 in Figure 3-4).
... Selecting that item will let you type the desired value in the
same line (see for example item 1 in Figure 3-4).
Nothing When neither symbol is displayed, selecting that item will toggle
the current selection, now shown in brackets (for example, this
will change ENABLE to DISABLE or vice versa).
• When a menu does not fit on one screen (because it includes too many
lines), it is displayed on two consecutive pages. In this case, you will see …(N)
after the last line on the first page and …(P) after the last line on the second
page:
While on the first page, press N to display the second page
While on the second page, press P to return to the first page.
• When a configuration screen is organized as a table, a special set of keys is
used for navigation within the table (such screens always have a ? (help)

option that displays these keys). The following keys may be used for
navigation within tables:
Left Arrow (←) – move to the left Right arrow (→) – move to the right
Down Arrow (↓) –move down Up Arrow (↑) – move up
^D – scroll down ^U – scroll up
F – next B – previous
In addition, the following shortcuts are also available:

Tab – select the next cell that may be changed
M – switch to the menu mode
G followed by <row number>,<col number> – select a specific cell. For
example, type G2,5 to select the fifth cell in the second row.
• The current value of a parameter is listed within parentheses ( ). To change a
parameter value on a parameter selection screen:
Type the line number corresponding to the desired value, and then press
<Enter>
To enter a value which requires free text entry, type in the desired string
and then press <Enter>. Use backspace to erase the current string.
Note that whenever applicable, the allowed range of values of a
parameter is listed within square brackets [ ].
• The entry is checked after pressing <Enter>, and it is accepted only if it is
valid. If you make an error, for example, if you press a key not active on the
current screen or select an invalid parameter value, an ERROR indicator
appears in the upper right-hand corner. This indicator disappears as soon as
you make a correct operation.
• When done with the current screen, press ESC to return to the previous
screen, or type ! to return directly to the main menu.
Saving Changes to Configuration Database

To save all the pending changes, type % (DB Update). You will be prompted to
confirm: type y to continue or n to cancel.
After confirming, the new database takes effect immediately. You will see the
message Configuration File Update is in Process while the database is saved in
the CL module flash memory.
Note
If you save the changes to the default database, the changes will be activated,
that is, the operation mode of the Megaplex-4100 changes in accordance with
the new parameters values. In this case, press <Enter> several times in sequence
to reestablish communication with the Megaplex-4100.
• To undo (cancel) all the as-yet unsaved changes, type # – DB Undo and then
confirm.
Any unsaved changes are lost when the Megaplex-4100 is powered down.

Ending a Terminal Configuration Session
³ To end the current terminal session:

Type & and then press <Enter>.
In addition, Megaplex-4100 will automatically terminate the current session after
no activity is detected for a user-selected time-out interval (default – 3 minutes,
can be increased to 10 minutes). The automatic session termination can however
be disabled. The time-out option is selected using Configuration>System>
Control Port>Serial Port>Security Timeout.
After a session is ended, it is necessary to enter again a valid user name and
password to start a new session.
Menu Structure of Supervision Utility

Figure 3-5 shows the structure of the main menu.
Main Menu
1. Inventory
2. Configuration
3. Monitoring
4. Diagnostics
5. File Utilities Inventory
1. System
2. SW/HW Rev
Configuration
1. Quick Setup
2. System
3. Physical Layer
4. Logical Layer
5. Applications
6. DB Tools
Monitoring
1. System
2. Physical Layer
3. Logical Layer
Diagnostics
1. Physical Layer
2. Logical Layer
3. Active Tests
File Utilities
1. S/W & File Transfer CL
2. S/W & File Transfer I/O & S-Subsystem
Figure 3-5. Main Menu Structure

The functions of the various main menu items are as follows:
Inventory Displays logistics information on the Megaplex-4100. See

Chapter 4 for details.
Configuration Configure Megaplex-4100 operational parameters, and

manage its database files. See Chapter 4 for details.
Monitoring Display Megaplex-4100 alarms, events and status, and the

performance monitoring statistics. See Chapter 5 for details.
Diagnostics Activate tests and loopbacks on the various ports, and check
IP connectivity. See Chapter 5 for details.
File Utilities Use the file transfer utilities. See Chapter 4 for details.
Figure 3-6 through Figure 3-27 show the detailed menu structure of the
supervision utility.
You may use these figures to find the screen used for any desired activity. For
additional details, refer to the Chapter listed in the description of the main menu,
where you will find a detailed view and a description of the functions and
parameters available on each screen.
Note Unless specifically stated otherwise, where menu details depend on the frame
structure, STM-1 or OC-3, used by CL.1/155 and CL.1/155GbE modules for the
network links, the following figures illustrate menu structures for Megaplex-4100
using the STM-1 frame structure.
The frame structure, and thus the operating standard, SDH or SONET, is selected
by means of Configuration>Physical Ports>CL>Card Configuration screen.
The differences between SDH and SONET are described in Appendix C of this
manual.
Inventory
1. System
2. SW/HW Rev
System
SW/HW Rev
Figure 3-6. Inventory Menu Structure

Configuration
1. Quick Setup
2. System
3. Physical Layer
4. Logical Layer
5. Applications
6. DB Tools
Quick Setup
1. Host IP address
2. Subnet Mask
3. Default Gateway
System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
10. Reset Device
11. Signaling Profile
12. Alarms Configuration
13. Fault Propagation
Physical Layer
1. IO
2. CL
Logical Layer
1. IO
2. CL
3. Bundles
Applications
1. Ethernet Services
DB Tools
1. Load DB
2. Default DB
3. Load HW
4. Update DB
5. DB List
6. Delete DB
Figure 3-7. Configuration Menu Structure

System
1. Card Type Card Type
2. Clock Source
3. TS Assignment Slot: PS-A PS-B CL-A CL-B IO-1 IO-2 IO-3
4. Mapping Card: PS PS CL1/155 CL1/155 M8E1 M8E1 M8SL
5. APS
6. Management Slot: IO-4 IO-5 IO-6 IO-7 IO-8 IO-9 IO-10
7. Control Port Card: M8SL HSU-12 HSU-12 HSU-12 HSU-12 VC-16/FXS VC-16/E&M
8. Date & Time
9. Factory Default
10. Reset Device
Source
13. Fault Propagation 1. Internal
2. Rx Clock
Clock Source 3. S Subsystem
1. Source
2. Master Port Rx Clock only
3. Fallback Port Master Port/Fallback Port
Entry Num Slot Port
TS Assignment 1 NONE -
1. IO 2 NONE -
2. CL | 3 NONE -
v4 NONE -
5 NONE -
See Sheet 2 6 NONE -
Mapping 7 NONE -
or Sheet 3
1. CL-A
2. CL-B 1. CL-A (CL1/155) 4. IO-2 (M8E1) 7. IO-5 (HSU-12) 10. IO-8 (HSU-12) 13. NONE
2. CL-B (CL1/155) 5. IO-3 (M8SL) 8. IO-6 (HSU-12) 11. IO-9 (VC-16/FXS)
3. IO-1 (M8E1) 6. IO-4 (M8SL) 9. IO-7 (HSU-12) 12. IO-10 (VC-16/E&M)
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
7. Flip Upon SD See Sheet 4
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Date & Time

1. Display Date & Time
2. Set Date Format
3. Set Date
4. Set Time
Reset Device
1. CL-A (On-line CL)
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9 See
11. IO-10
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
Alarms Configuration
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
4. Init Alarm Priority
5. Init Alarm Report
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces
Figure 3-8. Typical Configuration>System Menu Structure (Sheet 1 of 6)

System
1. Card Type
2. Clock Source
3. TS Assignment Link 1
4. Mapping IO I/O-1
5. APS 1. Display Time Slots
6. Management 1. I/O-1 2. Manual
1. Link 1
7. Control Port 2. I/O-2 3. Connect Time Slots
2. Link 2
8. Date & Time 4. Delete TS (Per Slot and Port)
9. Factory Default See ..
3. I/O-3
..
3. Link 3
5. Delete TS (Number of TS)
10. Reset Device
Sheet 1
. . 6. Split

or
CL
PDH 1
1. PDH 1 (Up)> 12. PDH 12 (Up)> 23. PDH 23 (Up)> 34. PDH 34 (Up)>
Clock Source 2. PDH 2 (Up)> 13. PDH 13 (Up)> 24. PDH 24 (Up)> 35. PDH 35 (Up)> 1. Display Time Slots
1. Source 3. PDH 3 (Up)> 14. PDH 14 (Up)> 25. PDH 25 (Up)> 36. PDH 36 (Up)> 2. Manual
2. Master Port 4. PDH 4 (Up)> 15. PDH 15 (Up)> 26. PDH 26 (Up)> 37. PDH 37 (Up)> 3. Connect Time Slots
Rx Clock only 5. PDH 5 (Up)> 16. PDH 16 (Up)> 27. PDH 27 (Up)> 38. PDH 38 (Up)>
3. Fallback Port
. .. ..
. ... ... 4. Delete TS (Per Slot and Port)
. . .. . . . . 5. Delete TS (Number of TS)

6. Split
TS Assignment . . . .
1. IO
(See below)
2. CL
Mapping Display Time Slots

Ts# 1 2 3 4 5 6 7 8
1. CL-A
02:01:01 02:01:02 02:01:04 02:BND01 02:BND01 02:BND01 03:BND15 03:BND15
2. CL-B
Ts# 9 10 11 12 13 14 15 16
APS
----- ----- ----- -----
.. ----- ----- ----- -----
1. APS Group Id
.
2. Protection
3. Revertive Manual
4. Working Port Ts# Slot Port Ts Type
5. Protection Port TS 01 IO-2 (M8E1) Link 1 1 DATA
6. WTR Time (Sec) TS 02 IO-2 (M8E1) Link 1 2 DATA
7. Flip Upon SD See Sheet 4 | TS 03 IO-2 (M8E1) Link 1 4 DATA
or Sheet 5 v TS 04 IO-2 (M8E1)
.. BND 1 -- DATA
Management .
1. Device Info
2. Host IP Connect Time Slots
3. Manager List PDH 1 1. Start TS
4. Mng Access 2. Slot
5. Flow 3. Port
1. Display Time Slots
6. SNMP Engine ID 4. Number of TS
7. SNMPv3 2. Manual
3. Connect Time Slots 5. Type
8. SNMPv3 Setting
4. Delete TS (per Slot and Port) 6. Destination Start TS
5. Delete TS (Number of TS) 7. Save Configuration
6. Split
Control Port
1. Serial Port Delete TS (per Slot and Port)
2. ETH
1. Slot
2. Port
3. Save Configuration
Date & Time
2. Set Date Format Delete TS (Number of TS)
3. Set Date
4. Set Time 1. Start TS
2. Number of TS
Reset Device
1. CL-A (On-line CL) TS3
2. IO-1
3. IO-2
Split 1. Bit 1 ... (01:IN03)
2. Bit 2 ... (01:IN03)
4. IO-3 1. TS3 3. Bit 3 ... (------)
5. IO-4 2. TS15 4. Bit 4 ... (------)
6. IO-5 .. 5. Bit 5 ... (------)
7. IO-6
8. IO-7 See
. 6. Bit 6 ... (------)
7. Bit 7 ... (------)
9. IO-8 Sheet 6 8. Bit 8 ... (------)
10. IO-9
11. IO-10 9. Check Split Sanity
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling CL-A
4. Rx Busy
5. Rx Idle 1. Link 1
6. Profile Name 2. Link 2
Link 1
TUG3 1 TUG3 2 TUG3 3
1. Alarm Attributes
2. Alarm Report TU1 TU2 TU3 TU1 TU2 TU3 TU1 TU2 TU3
3. Alarm Priority TUG2-1 None None None None None None None None None
4. Init Alarm Priority TUG2-2 None None None None None None None None None
5. Init Alarm Report TUG2-3 None None None None None None None None None
6. Alarm Window TUG2-4 None None None None None None None None None
7. Trap Masking TUG2-5 None None None None None None None None None
TUG2-6 None None None None None None None None None
Fault Propagation
2. Interfaces
Figure 3-9. Typical Configuration>System Menu Structure – SDH Only (Sheet 2 of 5)

System
1. Card Type
Link 1
2. Clock Source IO I/O-1
3. TS Assignment
1. I/O-1 1. Link 1 2. Manual
4. Mapping
2. I/O-2 2. Link 2 3. Connect Time Slots
5. APS
4. Delete TS (Per Slot and Port)
6. Management
..
3. I/O-3
..
3. Link 3
7. Control Port
8. Date & Time
. . 6. Split
9. Factory Default See
10. Reset Device Sheet 1 or
11. Signaling Profile CL
PDH 1
12. Alarms Configuration 1. PDH 1 (Up)> 12. PDH 12 (Up)> 23. PDH 23 (Up)> 34. PDH 34 (Up)>
13. Fault Propagation 2. PDH 2 (Up)> 13. PDH 13 (Up)> 24. PDH 24 (Up)> 35. PDH 35 (Up)> 1. Display Time Slots
3. PDH 3 (Up)> 14. PDH 14 (Up)> 25. PDH 25 (Up)> 36. PDH 36 (Up)> 2. Manual
4. PDH 4 (Up)> 15. PDH 15 (Up)> 26. PDH 26 (Up)> 37. PDH 37 (Up)> 3. Connect Time Slots
Clock Source 5. PDH 5 (Up)> 16. PDH 16 (Up)> 27. PDH 27 (Up)> 38. PDH 38 (Up)>
1. Source . .. ..
2. Master Port
Rx Clock only
6. Split
3. Fallback Port . . . .
(See below)
TS Assignment
1. IO
2. CL Display Time Slots
Ts# 1 2 3 4 5 6 7 8
Mapping Ts# 9 10 11 12 13 14 15 16
1. CL-A ----- ----- ----- -----
.. ----- ----- ----- -----
2. CL-B
.
APS Manual
1. APS Group Id Ts# Slot Port Ts Type
TS 01 IO-2 (M8T1) Link 1 1 DATA
2. Protection
3. Revertive TS 02 IO-2 (M8T1) Link 1 2 DATA
4. Working Port | TS 03 IO-2 (M8T1) Link 1 4 DATA
5. Protection Port v TS 04 IO-2 (M8T1)
.. BND 1 -- DATA
6. WTR Time (Sec)
7. Flip Upon SD See Sheet 4 .
or Sheet 5
Connect Time Slots
Management PDH 1 1. Start TS
2. Slot
1. Device Info 1. Display Time Slots 3. Port
2. Host IP 2. Manual 4. Number of TS
3. Manager List 3. Connect Time Slots 5. Type
4. Mng Access 4. Delete TS (per Slot and Port) 6. Destination Start TS
5. Flow 5. Delete TS (Number of TS) 7. Save Configuration
6. SNMP Engine ID 6. Split
7. SNMPv3
8. SNMPv3 Setting
Delete TS (per Slot and Port)
1. Slot
Control Port 2. Port
1. Serial Port 3. Save Configuration
2. ETH
Delete TS (Number of TS)

Date & Time 1. Start TS
1. Display Date & Time 2. Number of TS
2. Set Date Format
3. Set Date
4. Set Time TS3
Split 1. Bit 1 ... (01:IN03)
2. Bit 2 ... (01:IN03)
Reset Device 1. TS3 3. Bit 3 ... (------)
2. TS15 4. Bit 4 ... (------)
1. CL-A (On-line CL) .. 5. Bit 5 ... (------)
2. IO-1
3. IO-2
. 6. Bit 6 ... (------)
4. IO-3 7. Bit 7 ... (------)
5. IO-4 8. Bit 8 ... (------)
7. IO-6 See
8. IO-7 Sheet 6
9. IO-8
10. IO-9
11. IO-10 CL-A
1. Link 1
Signaling Profile 2. Link 2
1. Profile Number
2. Rx Signaling Link 1
3. Tx Signaling
4. Rx Busy
5. Rx Idle
STS1-1 STS1-2 STS1-3
6. Profile Name TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4
TUG2-1 None None None None None None None None None None None None
Alarms Configuration TUG2-3 None None None None None None None None None None None None
1. Alarm Attributes TUG2-4 None None None None None None None None None None None None
2. Alarm Report TUG2-5 None None None None None None None None None None None None
3. Alarm Priority
5. Init Alarm Report TUG2-7 None None None None None None None None None None None None
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces
Figure 3-10. Typical Configuration>System Menu Structure – SONET Only (Sheet 3 of 5)


System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
See
10. Reset Device Sheet 1
11. Signaling Profile APS Group ID
13. Fault Propagation 1. A1-A2
2. B1-B2
3. A1-B1
Clock Source 4. A2-B2
1. Source
2. Master Port
Rx Clock only
3. Fallback Port
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping Users
Authentication Protocol
1. CL-A 1. Security Name
2. Authentication Protocol 1. usmNoAuthProtocol
2. CL-B 2. usmHMACMD5AuthProtocol
3. Privacy Protocol
4. Authentication Password 3. usmHMACSHAAuthProtocol
5. Privacy Password
APS
1. APS Group Id With Authentication
2. Protection
3. Revertive Privacy Protocol
4. Working Port 1 usmNoPrivProtocol
5. Protection Port 2. usmDESPrivProtocol
6. WTR Time (Sec)
7. Flip Upon SD
Only with Authentication

Management
1. Device Info See Only with Privacy
2. Host IP
3. Manager List
Sheet 4
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
Targets Params Message Processing
8. SNMPv3 Setting
Targets & Notify 1. Name
Model
1. Target Params 2. Message Processing Model 1. SNMPv1
SNMPv3 Setting 2. Target Address 3. Security Model 2. SNMPv2c
Engine Boots 3. Notify 4. Security Name 3. SNMPv2u
Engine Time 4. Trap 5. Security Level 4. SNMPv3
SNMP Message Size
Control Port 1. Users
2. Targets & Notify Security Model
1. Serial Port 3. SNMPv1/v3 Mapping
2. ETH 4. SNMPv3 Factory Defaults 1. Any
5. Summary User Table Target Address 2. SNMPv1
6. Summary Target Table 3. SNMPv2c
1. Name
4. USM
Date & Time 2. IP Address
5. Not defined
1. Display Date & Time 3. Params Name
2. Set Date Format 4. Tag List
3. Set Date
4. Set Time Security Level
1. noAuthNoPriv
Notify 2. authNoPriv
Reset Device 3. authPriv
2. IO-1
3. IO-2 See
Trap
4. IO-3 Sheet 6
5. IO-4
6. IO-5
7. IO-6
8. IO-7 SNMPv1/v3 Mapping
9. IO-8
10. IO-9 1. Community Index
11. IO-10 2. Community Name
3. Security Name
4. Transport Tag
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling Summary User Table
4. Rx Busy
5. Rx Idle User Security Model Security Level
6. Profile Name
1. Alarm Attributes Summary Target Table
2. Alarm Report Address MPModel SecModel SecName SecLevel
3. Alarm Priority
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces

System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time

Clock Source
1. Source
2. Master Port
Rx Clock only
3. Fallback Port
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping
1. CL-A
2. CL-B
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3 - Enabled Baud Rate
8. SNMPv3 Setting
For Administrator
Serial Port
Control Port Change Password
1. Serial Port 1. Baud Rate
2. Change Password 1. Change User Details Change User Details
2. ETH
3. Security Timeout 2. Show all Users
Date & Time Show all Users

1. Display Date & Time Security Timeout
2. Set Date Format
3. Set Date
4. Set Time
ETH
CL-A
Routing Protocol
Reset Device 1. CL-A
2. CL-B 1. Admin Status
2. Routing Protocol 1. None
3. User Name 2. RIP 2
2. IO-1
3. Proprietary RIP
3. IO-2
4. IO-3
5. IO-4 Set Date Format
6. IO-5
7. IO-6 1. DD-MM-YYYY
8. IO-7 2. MM-DD-YYYY
9. IO-8 3. YYYY-DD-MM
10. IO-9 4. YYYY-MM-DD
11. IO-10
Signaling Profile
1. Profile Number Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy Rx Signaling
5. Rx Idle
6. Profile Name Tx Signaling
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
5. Init Alarm Report Interfaces
6. Alarm Window
7. Trap Masking 1. Slot A
2. Port A
Interfaces 3. Slot B
Add
Fault Propagation 4. Port B
Slot A Port A Slot B Port B Mode 5. Mode
1. Fault Propagation IO-1 ETH 1 IO-5 ETH 2 BiDirectional (A<->B)
2. Interfaces

Physical Layer I/O E1

I/O-1
1. I/O 1. I/O-1
2. CL 2. I/O-2 1. E1 ..
1. Link 1
..
3. I/O-3 2. Ethernet ..
.. 8. Link 8
. 9. All Links
Ethernet Transmit Timing

Source
1. ETH1
2. ETH2 1. System
3. ETH3 2. Station RCLK
4. All Ports 3. Station RCLK after JA
Clock Rate
CL Station Clock
1. 2048 KBPS
1. Admin Status 2. 1544 KBPS Not for
1. CL-A
2. Transmit Timing Source 2. 2048 KHZ SYSTEM Source
2. CL-B
3. Clock Rate
4. Interface Type Balance
5. Line Code Unbalance
6. Rx Gain Limit Short Haul
7. SSM Disable Long Haul
8. Rx Source Rx
Only for SSM = Rx Line Code

Sa4
1. AMI 1544 KBPS only
CL-A Sa5
2. HDB3 2048 KBPS, 2048 KHZ
Sa6
3. B8ZS
1. Station Clock Sa7
2. Ethernet Sa8
3. SDH/SONET
GbE
Ethernet
1. Admin Status
1. GbE 1 2. Auto Negotiation
2. GbE 2 3. Speed & Duplex
3. All Ports 4. Flow Control
5. User Name
6. Redundancy
SDH/SONET Card Configuration

1. Card Configuration 1. Frame Structure – STM-1 Common PDH
2. Link 1 2. Tx Clock Based on SSM – YES LVC Parameters
3. Link 2 3. Common PDH LVC Parameters
4. All Links 1. RDI on Signal Label
or 2. RDI on Path Trace
Card Configuration
1. Frame Structure – STM-1 In Band Management
2. Tx Clock Based on SSM – NO
3. SDH Tx Clock 1. Off
4. Master Port 2. PPP Over HDLC
5. Fallback Port
RX CLOCK only
3. HDLC
6. Common PDH LVC Parameters
Link 1 Routing Protocol
1. Admin Status 1. None

3. RDI on Fail 3. Proprietary RIP
DCC Configuration
4. EED Threshold
5. SD Threshold 1. In Band Management
6. DCC Configuration 2. Routing Protocol
3. Management DCC Management DCC
4. Deviation Type
1. D1-D3
Standard 2. D4-D12
Type 1
Figure 3-14. Typical Configuration>Physical Layer Menu Structure (SDH)

Figure 3-15. Typical Configuration>Physical Ports Menu Structure (SONET)

Figure 3-16. Typical Configuration>Virtual Ports Menu Structure (SDH) (Sheet 1 of 2)

Logical Layer
1. IO
2. CL
3. Bundles
See
Sheet 1
CL
1. PDH
2. VCAT
3. HVC
HVC CL-A
1. CL-A 1. Port 1 Port 1
2. CL-B 2. Port 2
3. All Ports VC-4
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. J1 Path Trace
5. Padding
6. EED Threshold
7. SD Threshold
8. Signal Label
Bundles
1. Slot
2. Bundle
MLPPP Bundle
HDLC Bundle (Unframed E1 Ports Only)
Bundles Bundles
Rate (Kbps) Rate (Kbps)
1. Slot 1. Slot
2. Bundle 2. Bundle
3. Admin Status 3. Admin Status
4. User Name 4. User Name
5. L2 Protocol 5. L2 Protocol
6. Number of TS 6. MLPPP MTU
7. Link OAM 7. Link OAM
8. Link OAM Mode 8. Link OAM Mode
9. Remote Terminal 9. Remote Terminal
10. Source Slot CL 10. Number of Links
11. Source Port I/O 11. Source Slot
12. Source Port
.
.
For CL .
PDH Selection Screen
For I/O Modules

Link Selection Screen
Figure 3-17. Typical Configuration>Logical Layer Menu Structure (SDH) (Sheet 2 of 2)

Logical Layer
IO I/O-1 (HS-U12)
1. IO
2. CL 1. I/O-1 1. IN 1 13. IN 13 25. IN 25
2. I/O-2 2. IN 2 14. IN 14 26. IN 26
3. Bundles
.. 3. IN 3 15. IN 15 27. IN 27
.. I/O-2 (M8SL) 4. IN 4 16. IN 16 28. IN 28
5. IN 5 17. IN 17 29. IN 29
1. E1 1 6. IN 6 18. IN 18 30. IN 30
2. E1 2 7. IN 7 19. IN 19 31. IN 31
3. E1 3 8. IN 8 20. IN 20 32. IN 32
4. E1 4 9. IN 9 21. IN 21 33. IN 33
5. E1 5 10. IN 10 22. IN 22 34. IN 34
6. E1 6 11. IN 11 23. IN 23 35. IN 35
7. E1 7 12. IN 12 24. IN 24 36. IN 36
8. E1 8
9. All Ports
T1 Ports
PDH PDH 1
LVC Configuration
CL 1. PDH 1 1. Admin Status
.. 2. User Name 1. J2 Rx Path Trace
1. PDH . 3. Frame Type 2. J2 Path Trace
2. VCAT
.. 4. Redundancy 3. Padding
. 5. Restoration Time
3. HVC . 4. EED Threshold
84. PDH 84 6. Idle Code 5. SD Threshold
85. All PDHs 7. Cross Connect 6. Protection Mode
8. In Band Management 7. Mapping Mode
9. Routing Protocol 8. Protection Partner
10. LVC Configuration 9. Payload Label
VCAT
1. CL-A
2. CL-B VC Type LAPS Encapsulation
Typical
1. VT-1.5
2. STS-1/SPE
VCG 1
GFP Encapsulation
CL-A Typical Encapsulation 1. Admin Status
2. VC Type
1. VCG-1
VCG-1 1. GFP
3. LCAS
4. Number of VTs
2. VCG-2 2. LAPS
1. Admin Status 5. Encapsulation
3. VCG-3
2. VC Type 6. Minimum Number of VTs
4. VCG-4
3. LCAS 7. User Name
5. VCG-5 LVC Configuration 8. Redundancy For VCG.1 to
6. VCG-6 4. Number of VTs
5. Encapsulation 9. LVC Configuration VCG.8 only
7. VCG-7 1. J2 Rx Path Trace
6. Minimum Number of VTs 10. LAPS Configuration
8. VCG-8 2. J2 Path Trace
9. All VCGs 7. User Name 3. Padding
8. Virtual Concatenation 4. EED Threshold or
9. Redundancy 5. SD Threshold
10. LVC Configuration 6. First Sequence Indicator Redundancy = 1+1
For VCG.1 to 11. GFP Configuration 7. Extended Signal Label
VCG.8 only 8. RDI on Payload label VCG 1
Primary
Redundancy = 1+1 1. Admin Status
GFP Configuration 2. VC Type
VCG-1 3. LCAS
4. Number of VTs
1. FCS
Primary 5. Encapsulation
2. PTI for Client Data
1. Admin Status 6. Minimum Number of VTs
3. UPI for Client Data
2. VC Type 7. User Name
4. Delta
3. LCAS 8. Redundancy
5. Core Scrambling
4. Number of VTs 9. Revertive
6. Payload Scrambling
5. Encapsulation 10. Wait to Restore
6. Minimum Number of VTs
7. User Name 11. Redundancy Slot
8. Virtual Concatenation 12. Redundancy Port
9. Redundancy 13. LVC Configuration
10. Revertive 14. LAPS Configuration
11. Wait to Restore

12. Redundancy Slot LAPS Configuration
13. Redundancy Port
14. LVC Configuration 1. Address
HVC 15. GFP Configuration 2. Control
3. SAPI Value
1. CL-A
2. CL-B
See
Sheet 2
Bundles
1. Slot
2. Bundle
Figure 3-18. Typical Configuration>Virtual Ports Menu Structure (SONET) (Sheet 1 of 2)

Logical Layer
1. IO
2. CL
3. Bundles
See
Sheet 1
CL
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
1. Port 1 Port 1
2. Port 2
3. All Ports 1. STS1-1
4. Common Parameters 2. STS1-2 STS1-1
3. STS1-3
1. J1 Path Trace
2. Padding
3. Signal Label
Bundles Common Parameters

1. Slot 1. RDI on Signal Label
2. Bundle 2. RDI on Path Trace
3. J1 Rx Path Trace
4. EED Threshold
5. SD Threshold
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot CL
11. Source Port I/O
For CL
For I/O Modules

Figure 3-19. Typical Configuration>Virtual Ports Menu Structure (SONET) (Sheet 2 of 2)

Applications
Flows
Ethernet Services
1. Flow Flow Type
1. Flows 2. User Name
3. Flow Type 1. E-LINE
4. Bridge Port Mapping 2. E-LAN Reserved
Bridge Port Mapping

BP C-VLAN Type C-VLAN ID SP-VLAN Slot Port Rate BP User Name
Add (A) Display List (U)
Bridge Port Mapping

Flow Flow User Name C-VLAN ID SP-VLAN
Bridge Port Mapping

BP C-VLAN Type
1. C-VLAN Type 1. Unaware
C-VLAN ID 2. Aware
2. SP-VLAN
3. Slot
Port
Rate
BP User Name
Figure 3-20. Typical Configuration>Applications Menu

Load DB
DB Tools
Default DB
1. Load DB
2. Default DB
3. Load HW
4. Update DB Update DB
5. DB List
6. Delete DB
DB List
Delete DB
Figure 3-21. Configuration>DB Tools Menu

Figure 3-22. Typical Monitoring Menu Structure (SDH) (Part 1 of 2)


Monitoring
All Alarms
Active Alarms (ON)
1. System 1. All Alarms
2. Physical Layer 2. Slot Alarms Slot Alarms
3. Logical Layer
All Alarms
Active Alarms (ALL)
1. All Alarms
2. System Alarms System Alarms
3. Slot Alarms
System Slot Alarms

1. Active Alarms (ON)
2. Active Alarms (ALL) History Alarms
3. Clear Alarms
4. History Alarms
5. Timing Timing
6. CL Status
7. Remote Agents
8. APS CL Status
Remote Agents
I/O-1
1. CH1 APS
2. CH2
.. Interface Info
I/O .
Logical Layer
1. I/O-1 (HS-U12)
2. I/O-2 (M8SL)
1. I/O I/O-3
2. CL ..
3. I/O-3 (M8SL)
.. 1. Bundles Bundles (Selection) Bundle (Statistics)
CL
SDH/SONET Link 1
1. CL-A Port Status
2. CL-B 1. Link 1 1. VT1.5
VT1.5
2. Link 2 2. STS1-1
1. Port Status
3. STS1-2
4. STS1-3
2. Port Statistics Port Statistics
CL-A 1. Current Interval Current Interval
PDH 2. Select Interval
1. SDH/SONET 3. Total
2. PDH 1. PDH 1 Select Interval
.. PDH 1
3. VCAT ..
.. 1. Current Interval Total
. 2. Select Interval
84. PDH 84 3. Total
85. All PDHs
VCAT
1. VCG 1
2. VCG 2 VCG 1 WAN Intervals Current Interval
3. VCG 3
4. VCG 4
1. WAN Intervals 1. Current Interval
5. VCG 5
2. LCAS Path Info 2. Select Interval Select Interval
6. VCG 6
7. VCG 7 3. Total
8. VCG 8
Total
LCAS Path Info
Physical Layer
See
1. I/O
2. CL Part 2
Figure 3-24. Typical Monitoring Menu Structure (SONET) (Part 1 of 2)

Monitoring
1. System
2. Physical Layer
3. Logical Layer
System
2. Active Alarms (ALL) See
3. Clear Alarms Part 1
4. History Alarms
5. Timing
6. CL Status
7. Remote Agents
8. APS Typical
I/O-3 M8E1, M8T1, M8SL
Redundancy
1. Link 1
Logical Layer 2. Link 2
Link 1 Only
1. I/O ..
3. Link 3
1. Status Status
2. CL .. 2. Statistics
Link 1 Current Interval

I/O
Physical Layer M8E1, M8T1, M8SL 1. Current (15 min)
1. I/O-1 (HS-U12) 2. Select Interval (15 min) Select Interval
1. I/O 2. I/O-2 (M8T1) I/O-2 3. Current (24 hours)
3. I/O-3 (M8T1) 4. Select Interval (24 hours)
2. CL
.. 1. E1 or T1 or SHDSL 5. Clear Statistics Total
.. 2. Ethernet
Select Interval
SHDSL Only
Ethernet
ETH 1
1. ETH 1 Status
2. ETH 2
1. Status
3. ETH 3
2. Statistics
Statistics
CL Station Clock
1. CL-A Port Status
2. CL-B Ethernet
GbE 1
1. GbE 1 ETH Counters
2. GbE 2 1. Port Status
CL-A 2. ETH Counters
Link Status
1. Station Clock
2. Ethernet
3. SDH/SONET Timing Link Statistics Current Interval
1. Current Interval
Link 1 2. Select Interval Select Interval
3. Total
1. Link Status
2. Link Statistics Total
SDH/SONET 3. DCC Statistics DCC Statistics
4. Optical Parameters
1. Timing
2. Link 1
3. Link 2 Optical Parameters
4. Path Protection Path Protection

Figure 3-26. Typical Diagnostics Menu Structure (SDH and SONET)

File Utilities
1. S/W & File Transfer CL S/W & File Transfer CL
1. TFTP TFTP
TFTP State
1. File Name
Command
2. Server IP
1. SW Download
3. Command
2. Config Download
3. Config Upload
4. No Command
S/W & File Transfer I/O &
S-Subsystem TFTP
1. TFTP TFTP State

2. Download to Cards TFTP Error
1. File Name
3. Download Status
2. Server IP File #
4. Dir
5. Delete File 3. File #
4. S/W Download (To Flash) 1. File-1
2. File-2
Download to Cards
Download Status
Dir
Delete File
Figure 3-27. Typical File Utilities Menu Structure
Working with Telnet

Typically, the Telnet host is a PC or a UNIX station with the appropriate suite of
TCP/IP protocols. To enable a Telnet host to communicate, it is necessary to
configure the IP address of the Megaplex-4100 management subsystem. After
this preliminary configuration, you can use a Telnet host directly connected to
the CONTROL ETH port of the active or standby CL module in the managed
Megaplex-4100 to perform additional configuration tasks.
However, after configuring the communication parameters of the Megaplex-4100
management subsystem, you may also use a Telnet host located at a remote site,
the only requirement being that IP communication be established between the
LAN serving that site and the LAN connected to the Megaplex-4100 CONTROL
ETH port.
For inband Telnet access via E1 and T1 links, you also need to configure
dedicated management (MNG) timeslots.
General Telnet Operating Procedures

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 (see Table 3-3).
³ To prepare for using Telnet:

1. Configure the Megaplex-4100 host IP address.

Note When the Telnet host is not on a LAN directly connected to a Megaplex-4100
CONTROL ETH port, it is necessary to configure all the IP communication
parameters appearing on the Configuration>System>Management>Host IP
screen.
2. Enable Telnet access using Configuration>System>Management>Mng

Access>Telnet.
Working with Web Browsers

You may use any Web browser to access the Megaplex-4100 supervision utility
from any location that enables access to the Megaplex-4100 using Internet
protocols, for example:
• Internet Explorer 6.0 and up, running on Windows™
• Netscape Communicator 7.0 and up, running on Windows™, HPOV or Linux
• Firefox 1.0.4 and up, running on Windows™
• Mozilla 1.4.3 and up, running on Linux.
However, before using Web access, it is necessary to perform a preliminary
configuration of the Megaplex-4100 (see Table 3-3).
Guidelines for Using Web Browsers

When using a Web browser, pay attention to the following points:
• Enable scripts
• Configure the firewall that is probably installed on your PC to allow access to
the destination IP address (that is, the Megaplex-4100 management address)
• Disable pop-up blocking software (such as Google Popup Blocker); you may
also have to configure your spyware/adware protection program to accept
traffic from/to the destination IP address.
• Browsers store the last viewed pages in a special cache. To prevent
configuration errors, it is absolutely necessary to flush the browser’s cache
whenever you return to the same screen.
Preparations for Using Web Browsers
³ To prepare for using Web access:

1. Configure the Megaplex-4100 host IP address and all the IP communication
parameters (use the Configuration>System>Management>Host IP screen).
2. Enable Web browser access using Configuration>System>Management>
Mng Access>WEB.
General Web Browsers Operating Procedures

Before starting, obtain the Megaplex-4100 management (host) IP address.
1. Open the Web browser.

2. Enter the IP address of the Megaplex-4100 in the address field of the

browser in the following format: http://’IP address’ (‘IP address’ stands for
the actual Megaplex-4100 IP address).
3. After entering the address, press <Enter> to command the browser to
connect.
4. After the opening window of the ConfiguRAD utility is displayed, click LOGIN.
5. Perform log-in as described above for the supervision terminal.
6. You will see the main ConfiguRAD menu.
7. Use standard browser operating procedures to perform the desired activities.
Navigating the ConfiguRAD Menus

ConfiguRAD is a Web-based remote access terminal management software. It
provides a user-friendly interface for configuring, monitoring and performing
diagnostic tests on the Megaplex-4100 units.
³ To choose an option:
1. Click a link in the ConfiguRAD screen to display the next menu.
2. Once the target screen is displayed, select a value from the drop-down box or
enter it in a text box.
3. At the left-hand bottom corner, ConfiguRAD provides some auxiliary
management tools:
Status – shows the number of users currently managing Megaplex-4100
Trace – opens an additional pane for system messages, progress
indicators (ping, software and configuration file downloads) and alarms.
It is recommended to keep the trace pane open all the time.
Refresh All – refreshes all ConfiguRAD display elements.
Working with SNMP Management Stations
Support for SNMP Management

Megaplex-4100 can be configured by any SNMP-based network management
station, including third-party network management stations, provided IP
communication is possible with the management station.
Megaplex-4100 supports several management information bases (MIBs). A MIB
(Management Information Base) is a hierarchically-organized database of
managed objects, where each characteristic of the element to be managed is
defined as an object in the MIB.
Megaplex-4100 support the following standard MIBs:
• IANAifType-MIB (ifType table)
• RFC4188 (bridge MIB)
• RFC3418 (SNMPv2 MIB)

• RFC3592 (SONET-MIB)
• RFC3635 (EtherLike-MIB)
• RFC3636 (MAU-MIB)
• RFC4133 (ENTITY-MIB – physicalTable)
• RFC2819 (RMON MIB)
• RFC2863 (IF-MIB)
• RFC4805 (DS1-MIB)
• RFC4319 (HDSL2-SHDSL-LINE-MIB)
• RFC3273 (HC-RMON-MIB)
• RFC4878 (DOT3-OAM-MIB)
• SNMPv1 definitions are covered by the following documents:
RFC3418
RFC2578 (SMIV2)
RFC2579 (Textual Conventions SMIV2)
RFC2580 (Conformance SMIV2).
• SNMPv3 definitions are covered in RFC 3413 to RFC 3418.
Megaplex-4100 also support the RAD private MIB.
Additional MIB information can be obtained from your local RAD Authorized
Business Partner.
For information on traps, see Chapter 6.
Preparing for SNMP Management

To enable SNMP management, it is necessary to enable SNMP access, and
configure the minimal SNMP management parameters.
The required parameters depend on the required security level:
³ To prepare for SNMP management without SNMPv3 security features:

1. If necessary, configure SNMPv3 to Disabled. If the previous state has been
Enabled, you will be requested to confirm.
2. If necessary, configure the Megaplex-4100 host IP address.
Note
When the SNMP station is not on a LAN directly connected to a Megaplex-4100
CONTROL ETH port, it is necessary to configure all the IP communication
parameters appearing on the Configuration > System > Management > Host IP
screen.
3. Configure the SNMP community names on the Host IP screen.

4. Enable SNMP access using Configuration > System > Management > Mng
Access > SNMP.

³ To prepare for SNMP management with SNMPv3 security features:

1. If necessary, configure SNMPv3 to Enabled. If the previous state has been
Disabled, you will be requested to confirm.
2. If necessary, configure the Megaplex-4100 host IP address.
3. Configure SNMPv3 access using Configuration > System > Management > Mng
Access > SNMPv3 Setting, using the instructions given in Chapter 4.
4. Enable SNMP access using Configuration > System > Management > Mng
Access > SNMP.
For SNMP management instructions, refer to the User’s Guide of the desired
SNMP station.
3.5 Turning the Megaplex-4100 Off

³ To turn the Megaplex-4100 off:
Caution
When a feed and ring voltage source is connected to the Megaplex-4100
enclosure, always turn that source off before turning the PS module(s) off.
• Set the ON/OFF switch(es) of the PS module(s) to OFF.

If the Megaplex-4100 is equipped with DC-powered PS modules without
POWER switch, disconnect the DC power by means of an external switch or
circuit breaker.
3-46 Turning the Megaplex-4100 Off Megaplex-4100 Ver. 2.0

Chapter 4
Configuration
This Chapter provides detailed configuration instructions for the Megaplex-4100.
As part of these instructions, you can find:
• The purpose of each screen
• The parameters that can be selected on the each screen, considerations
regarding the selection of specific parameter values, and where applicable,
the effects of parameters selected on other screens
• Instructions for using each screen.
You can find a complete collection of supervision utility navigation maps in
Chapter 3. For your convenience, the relevant navigation map also appears in the
beginning section of each main configuration activity.
The configuration instructions are presented in the order the configuration
activities are performed when a new Megaplex-4100 is prepared for service (see
Chapter 5 for a detailed configuration sequence).
However, after performing the preliminary configuration of the Megaplex-4100 in
accordance with Chapter 3, the same configuration activities can also be
performed by means of a Telnet host, or Web browser.
You may also want to review Chapter 1, which presents technical and functional
descriptions of the Megaplex-4100, and Appendix C, which describes the
Megaplex-4100 operating environment and provides background information that
will help you understand the various Megaplex-4100 configuration parameters.
If you configure Megaplex-4100 for SNMP management as explained in this
Chapter, SNMP management stations using the appropriate SNMP version and
compatible parameters will also be able to configure and manage Megaplex-4100
units.
Note Unless otherwise specified, all the parameter values appearing in the following
screens are given for illustration purposes only. They do not reflect recommended
values.
4.1 Configuring MP-4100 for Management
Quick Setup
When starting the configuration of a new Megaplex-4100, you can use the Quick
Setup screen to prepare the preliminary set of Megaplex-4100 IP communication
parameters:
Megaplex-4100 Ver. 2.0 Configuring MP-4100 for Management 4-1

Chapter 4 Configuration Installation and Operation Manual
• The management IP address (mandatory)

• The associated IP subnet (mandatory)
• Default IP gateway (optional).
The IP information can also be defined or modified by means of the
Configuration>System>Management>Host IP screen.
To navigate to the required screen, use Configuration>Quick Setup.
A typical Quick Setup screen is shown below.
MP-4100
Configuration>Quick Setup
1. Host IP Address ... (176.123.1.102)

2. Subnet Mask ... (255.255.255.0)
3. Default Gateway ... (0.0.0.0)
>

-----------------------------------------------------------------------------
Figure 4-1. Typical Quick Setup Screen

To configure a parameter on the Quick Setup screen, select the corresponding
item by typing its number and then pressing <Enter>. You can then type the
desired value in the same line.
To confirm your entry, press <Enter>.
³ To configure the Megaplex-4100 management IP address:

1. Select Host IP address.
2. Enter the prescribed IP address of the Megaplex-4100 management agent, in
the dotted quad format, and then press <Enter>.
3. Select Subnet Mask.
4. Enter the IP subnet mask to be used by of the Megaplex-4100 management
agent, in the dotted quad format, and then press <Enter>. Make sure that the
subnet mask is compatible with the specified IP address, and that it represents
a string of consecutive 1s, followed by consecutive 0s.
5. You may also specify a default gateway. The default gateway is used by the
Megaplex-4100 management agent to send packets with destinations not
located on a local LAN. To specify a default gateway, select Default Gateway,
enter the IP address of the desired router port in the dotted-quad format, and
then press <Enter>. The default gateway IP address must be within the same IP
subnet as the management IP address. The default value, 0.0.0.0, means that
no default gateway is defined.
4-2 Configuring MP-4100 for Management Megaplex-4100 Ver. 2.0

Installation and Operation Manual Chapter 4 Configuration
³ To save and activate the new configuration:

Type % and then type y to confirm the action.
Configuring the Control Ports

Megaplex-4100 has two types of control ports:
• Serial control ports
• Ethernet control ports.
The following sections explain the configuration procedures for both types of
ports.
To navigate to the required screen, use Configuration>System>Control Port.
³ To select a control port:

1. Type its number and then press <Enter>.
MP-4100
Configuration>System>Control Port
1. Serial Port>
2. ETH >
>

-----------------------------------------------------------------------------
Figure 4-2. Control Port Selection Screen
Configuring the Serial Ports

The Configuration>System>Control Port>Serial Port screen is used to configure
the communication parameters of the serial RS-232 port, CONTROL DCE, located
on the CL modules, the authorizations of the users allowed to manage the
Megaplex-4100 via the serial port, and the security features.
The same set of parameters are used by both CL modules.
A typical Serial Port screen is shown in Figure 4-3.

MP-4100
Configuration>System>Control Port>Serial Port
1. Baud Rate > (115.2 KBPS)

2. Change Password >
3. Security Timeout > (None)
>

-----------------------------------------------------------------------------
Figure 4-3. Typical Serial Port Screen
³ To configure the serial port parameters:

1. Type the number corresponding to the desired parameter and then press
<Enter>.
2. You will see the serial port parameter selection screen. The parameters that
can be configured are explained in Table 4-1.
Table 4-1. Serial Port Parameters
Parameter Function Values
Baud Rate Selects the supervisory port data rate The available selections are 0.3, 1.2, 2.4, 4.8,
9.6, 19.2, 38.4, 57.6 and 115.2 KBPS.
Default: 115.2 KBPS
Security Controls the idle disconnect time of the NONE – Automatic session disconnection
Timeout CONTROL DCE port disabled. To disconnect the session, use the &
(exit) command.
3 MIN – Automatic disconnection after 3 minutes
if no input data is received by the CONTROL DCE
port.
10 MIN – Automatic disconnection after
10 minutes if no input data is received by the
CONTROL DCE port.
Default: NONE
Changing the User Authorizations and Security Parameters of

the Serial Ports
The Megaplex-4100 supports three access levels for supervision terminal, Telnet,
and Web browser users, explained in Chapter 3. The unit is delivered with three
factory-default user names, one for each access level, and with default
passwords.

Use the Change Password item on the Serial Port screen to perform the following
tasks:
• Manage the users’ list (add/delete users),
• Change access levels for added users
• Assign passwords to the various users.
Note When SNMPv3 security features are enabled, the term user refers to an SNMP
management station, and the users’ authorizations are determined by configuring
the parameters related to the view-based security model (VACM) aspect of
SNMPv3. Refer to the Configuring for SNMP Management with SNMPv3 Security
section for details.
³ To access the users’ security functions:

1. Type 2 on the Serial Port screen to display the Change Password submenu
(Figure 4-4).
MP-4100
Configuration>System>Control Port>Serial Port>Change Password
1. Change User details >

2. Show all users []>
>

-----------------------------------------------------------------------------
Figure 4-4. Typical Change Password Screen

2. Type the number corresponding to the desired task:
• To change the current password assigned to a user, select Change User
Details
• To add/delete users, select Show All Users.
Note It is not possible to change the access level of the three factory default users: su,
tech, user, but only the access levels of added users.
³ To change the current password of a factory default user:

1. Select Change User Details on the Change Password screen and pressing
<Enter>. You will see the Change User Details screen.
2. On the Change User Details screen, select Enter UserName and then press
<Enter>. You can type now the desired user name. When done, press <Enter>
to continue.

Note Password characters are not displayed on the screen (only an asterisk * appears
for each character you type). The string changes to 8 asterisks after pressing
<Enter>, irrespective of the number of characters typed.
3. After specifying a factory default user name, the New Password field appears.
Select New Password and then type the new password (4 to 8 characters).
4. After pressing <Enter>, the screen is updated, and a Confirm Password field
appears.
A typical Change User Details screen, as seen after Step 4, is shown in
Figure 4-5.
MP-4100
...>System>Control Port>Serial Port>Change Password>Change User details
Enter UserName (to change) ... (su)

New Password ... (********)
1. Confirm Password ... ()
>

-----------------------------------------------------------------------------
Figure 4-5. Typical Change User Details Screen (Factory Default User)
5. Select Confirm Password and then type the new password a second time for
confirmation. Press <Enter> when done.
After confirming password, the following message appears: Password has
been changed!! Update DB to finalize process!!
6. To activate the new password, type % to update the database and then
confirm the action.
³ To change the current password of an added user:

1. Select Change User Details on the Change Password screen and pressing
<Enter>. You will see the Change User Details screen.
2. On the Change User Details screen, select Enter UserName and then press
<Enter>. Now you can type the desired user name. When done, press <Enter>
to continue.
3. After specifying an added user name, the screen is updated to enable two
actions:
• Change the access level of the selected user
• Change the password of the selected user. Skip to Step 4 if that is what
you want to do.
• To change the access level, select Access Level and then press <Enter>.

• You will see a selection screen with four access levels (Figure 4-6). Note
that the Operator level is not defined for Megaplex-4100 (it has the same
capabilities as the Monitor). See Chapter 3 for details on the capabilities of
each access level.
• At this stage, type the number corresponding to the desired level, and then
press <Enter> to return to the screen of Figure 4-5.
MP-4100
...nge Password>Change User details> Change Access Level (Administrator)
1. Monitor
2. Technician
3. Operator
4. Administrator
>

-----------------------------------------------------------------------------
Figure 4-6. Typical Change Access Level Selection Screen for Added Users
Note Password characters are not displayed on the screen (only an asterisk * appears
for each character you type). The string changes to 8 asterisks after pressing
<Enter>, irrespective of the number of characters typed.
4. After specifying a new access level, the New Password field appears. Select
New Password and then type the new password (4 to 8 characters).
5. After pressing <Enter>, the screen is updated, and a Confirm Password field
appears.
A typical Change User Details screen, as seen after pressing <Enter>, is
MP-4100
...>System>Control Port>Serial Port>Change Password>Change User details
Enter UserName (to change) ... (oper)

New Password ... (********)
1. Change Access Level ... (Technician)
2. Confirm Password ... ()
>

-----------------------------------------------------------------------------
Figure 4-7. Typical Change User Details Screen (Added User)

6. Select Confirm Password and then type the new password a second time for
confirmation. Press <Enter> when done.
After confirming password, the following message appears: Password has
been changed!! Update DB to finalize process!!
7. To activate the new user details, type % to update the database and then
confirm the action.
³ To manage the users list:

1. Select Show All Users on the Change Password screen and then press <Enter>
to display the current list of users. Figure 4-8 shows a typical screen with
factory defaults.
MP-4100
...ation>System>Control Port>Serial Port>Change Password>Show all users
User ID UserName Access Level

1 su Administrator
2 user Monitor
3 tech Technician
4 oper Administrator
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity

ESC-prev.menu; !-main menu; &-exit; @-output; ?-help 1 M/ 1 C
-----------------------------------------------------------------------------
Figure 4-8. Typical Show All Users Screen
Note To see the options available for this screen, display the help screen by typing ?.
2. To delete an existing user, move the cursor to the appropriate row and then
type R. You will be required to confirm.
3. To add a new user, type A. You will see the Add New User screen. A typical
screen is shown in Figure 4-9.

MP-4100
...ation>System>Control Port>Serial Port>Change Password>Show all users
User ID (5)
1. UserName ... (new user)
2. Access Level > (Operator)
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 4-9. Typical Add New User Screen

4. Select UserName and type the desired user name (up to 8 characters).
5. If necessary, change the access level, which by default is Monitor (see Chapter
3 for details on the capabilities of each access level).
• To change the access level, select Access Level and then press <Enter>.
• You will see a selection screen with four access levels (Figure 4-10). The
Operator level is not defined for Megaplex-4100 (it has the same
capabilities as the Monitor).
MP-4100
...rt>Serial Port>Change Password>Show all users>Access Level (Monitor)
1. Monitor
2. Technician
3. Operator
4. Administrator
>

-----------------------------------------------------------------------------
Figure 4-10. Typical Access Level Selection Screen

• Type the number corresponding to the desired level, and then press
<Enter>.
6. To confirm the changes, select Save (type S).
7. You will see a User has been added!! Update DB to finalize process!! message.
Press any key to return to the Show All Users screen, updated with the new
user name and access level.

Note The new user is assigned the factory default password, 1234. To change it, use
the procedure described on page 4-5.
8. To add or delete all the required users, repeat the process described above as
required.
9. To activate the updates users, type % to update the database and then
confirm the action.
Configuring the Ethernet (ETH) Port

Navigate to Configuration>System>Control Port>ETH to configure the parameters
of the Ethernet management ports, CONTROL ETH, located on the CL modules.
Each CONTROL ETH port can be assigned its own parameters. However, both
ports use the management IP address of the Megaplex-4100, configured by
means of the Quick Setup or Host IP screen.
Figure 4-11 shows a typical ETH port selection screen.
MP-4100
Configuration>System>Control Port>ETH
1. CL-A>
2. CL-B>
>

-----------------------------------------------------------------------------
Figure 4-11. Typical ETH Port Selection Screen
³ To select the ETH port to be configured:

Type the number of the port on the ETH screen, and then press <Enter>. You will
see the port configuration screen. A typical screen is shown in Figure 4-12.

` MP-4100
Configuration>System>Control Port>ETH>CL-A
1. Admin Status > (Up)

2. Routing Protocol > (None)
3. User Name ... ()
>

-----------------------------------------------------------------------------
Figure 4-12. Typical ETH Configuration Screen
³ To define the CONTROL ETH port parameters:

Select the number of the desired parameter and then press <Enter>. The
parameters are explained in Table 4-2.
Table 4-2. ETH Configuration Parameters
Admin Status Used to enable/disable the flow DOWN – The flow of management traffic is disabled. This
of management traffic through state should be selected as long as the configuration of
the selected Ethernet port the corresponding port has not yet been completed, or
when it is necessary to stop traffic flow through the port.
UP – The flow of management traffic is enabled.
Default: UP
Routing Selects the routing protocol for NONE – Dynamic routing of management traffic is not
Protocol management traffic carried supported.
through the CONTROL ETH port PROPRIETARY RIP – The management traffic is routed
using the RAD RIP proprietary routing protocol.
RIP 2 – The management traffic is routed using the RIP2
protocol.
Default: NONE
User Name Used to enter a logical name for Up to 10 characters.

the selected CONTROL ETH port Default: Empty string
Configuring Host IP Parameters and SNMP Communities (with SNMPv3

Disabled)
Use the following procedure to define the Megaplex-4100 management agent IP
communication parameters (the management agent is referred to as the host) –
the same parameters that can be configured using Configuration > Quick Setup.

Note that only one IP address need be assigned to the Megaplex-4100

management agent, because at any time only one of the CL modules is online
(this IP address is automatically “moved” when the online CL module is changed).
When SNMPv3 security features are disabled (see Section 4.2) and you want to
enable SNMP management, you must also configure the SNMP community names.
However, before starting, first you may have to disable the SNMPv3 security
features, as explained below, because otherwise it is not possible to directly
configure SNMP community names.
³ To disable the SNMPv3 security features:

1. Navigate to Configuration > System > Management.
A typical Management screen with SNMPv3 security features enabled is
Megaplex-4100
Configuration>System>Management
1. Device Info >

2. Host IP >
3. Manager List []>
4. Mng Access >
5. Flow >
6. SNMP Engine ID >
7. SNMPv3 (Enabled))
8. SNMPv3 Setting >
>
ESC-prev.menu; !-main menu; &-exit; @-debug 1 M/ 1 C

-----------------------------------------------------------------------------
Figure 4-13. Typical Management Screen (SNMPv3 Enabled)

2. To change the state, select the state is toggled to Disabled, and you are
prompted to confirm by a message that explains the effects: Current
configuration of SNMP agent will be deleted! Continue? (Options: Y/N):
To abort, type n
To confirm, type y.
3. The screen is refreshed and the SNMPv3 Setting item is removed.
³ To define the host IP communication parameters:

1. Navigate to the Configuration > System > Management > Host IP screen.
A typical Host IP screen, as seen when SNMPv3 is Disabled, is shown
below.

Megaplex-4100
Configuration>System>Management>Host IP
1. IP address ... (172.17.171.234)

2. Subnet Mask ... (255.255.255.0)
3. Default Gateway ... (172.17.171.1)
4. Read Community ... (public)
5. Write Community ... (private)
6. Trap Community ... (public)
>

-----------------------------------------------------------------------------
Figure 4-14. Typical Host IP Screen (SNMPv3 Security Features Disabled)

1. Refer to Table 4-3, and configure the Host IP parameters.
Table 4-3. Host IP Parameters
Host IP Address Used to enter the IP address of the Type the desired IP address, using the
Megaplex-4100 management agent dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
periods).
Default: 0.0.0.0
Subnet Mask Used to enter the IP subnet mask of the Type the desired IP subnet mask, using the
Megaplex-4100 management agent dotted-quad format. Make sure to select a
subnet mask compatible with the selected IP
address, and whose binary representation
consists of consecutive “ones”, followed by
the desired number of consecutive “zeroes”.
Default: 0.0.0.0
Default Gateway Used to specify the IP address (usually an IP Type the desired IP address, using the
router port) to which the Megaplex-4100 dotted-quad format. Make sure the IP
management agent will send packets when address address is within the subnet of the
the destination IP address is not within the host IP address.
subnet specified in the Mask field. Default: 0.0.0.0
The default value, 0.0.0.0, means that no
default gateway is defined

Read Enter here the read-only SNMP community Enter the desired alphanumeric string (pay
name to be accepted by the Megaplex-4100 attention to case).
management agent. Default: public
SNMP-based management stations using
this community will not be able to modify
the Megaplex-4100 configuration, nor
initiate diagnostic activities.
This parameter is displayed only when
SNMPv3 is Disabled
Write Enter here the read-and-write SNMP Enter the desired alphanumeric string (pay
community name to be accepted by the attention to case).
Megaplex-4100 management agent. Default: private
Use this community for SNMP-based
management stations that must be able to
perform all the activities.
SNMPv3 is Disabled
Trap Enter here the SNMP community name that Enter the desired alphanumeric string (pay
will be specified by the Megaplex-4100 attention to case).
management agent in the traps sent to Default: public
SNMP-based management stations.
SNMPv3 is Disabled
Configuring Management Access

Use the following procedure to control globally the access to the Megaplex-4100
management agent using Telnet, SNMP management stations, and/or Web
browsers. This procedure enables to block the desired access options at the
Megaplex-4100 level, overriding the access rights of any user that may be logged
on the Megaplex-4100.
The supervisory terminal can always be used to access the Megaplex-4100
management agent.
To navigate to the required screen, use Configuration>System>Management>
Mng Access.
A typical Mng Access screen is shown below.

Megaplex-4100
Configuration>System>Management>Mng Access
1. Telnet> (Enable )
2. WEB > (Enable )
3. SNMP > (Enable )
>

-----------------------------------------------------------------------------
Figure 4-15. Typical Mng Access Screen
³ To change the global access rights:

1. Type the number corresponding to the management means to be modified,
and then press <Enter> to display the corresponding selection screen.
2. On the selection screen, type the number of the desired option and then press
<Enter>. The selection screen closes.
3. Repeat the process until all the desired management access means have been
defined.
4. The new selections are automatically saved.
Configuring the Manager List (with SNMPv3 Disabled)

Use the following procedure to define the IP addresses of Telnet hosts and Web
browsers that may manage the Megaplex-4100.
For SNMP management stations, the authorized managers are defined as follows:
• When SNMPv3 is Disabled¸ this procedure also defines the IP addresses of
SNMP management stations, and specifies whether a station will receive or
not traps generated by the local Megaplex-4100.
• When SNMPv3 is Enabled, refer to Section 4.2 for instructions.
Manager List.
A Manager List screen, as seen when first opened, is shown in Figure 4-16.

MP-4100
Configuration>System>Management>Manager List
Managers ID IP Address Alarms Trap
>
A-Add;%-Db Update; #-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-16. Typical Factory Default Manager List Screen
Note To see the navigation keys available for this screen, type ? (help).
³ To add a new management station:

1. Type a and then press <Enter> to display the new station configuration screen.
A typical screen with the factory defaults is shown in Figure 4-17.
MP-4100
Managers ID (1)
1. IP Address ... (0.0.0.0)
2. Alarms Trap > (Enable)
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 4-17. Add New Manager Screen

2. Select each parameter in sequence, and configure the desired value using the
guidelines in Table 4-4.
Table 4-4. Manager List Parameters
Managers ID Index number of management station, 1 to 10 Automatically assigned when a new manager is
added.
Default: Next free index

IP Address Used to enter the IP address of the Type the desired IP address, using the
management station dotted-quad format (four groups of digits in
the range of 0 through 255, separated by
periods).
Default: 0.0.0.0
Alarms Trap Specifies whether traps will be sent to the ENABLE — The Megaplex-4100 will send traps
management station, in case an alarm report to this management station.
is configured to result in the generation of a DISABLE— The Megaplex-4100 will not send
trap (for configuration instructions, refer to traps to this management station.
Chapter 6).
Default: ENABLE
Other types of traps are always sent to all the
configured managers
3. After ending the configuration and saving the changes, the Manager List
screen is updated to include the new station. To display the Manager List
again, press ESC.
MP-4100
Managers ID Ip Address Alarms Trap

1 172.123.102.8 Enable
1. Change cell ... (172.123.102.8)
>

-----------------------------------------------------------------------------
Figure 4-18. Typical Manager List Screen after Adding First Management Station
4. Repeat the process until all the desired management stations have been
defined. A new page is automatically added when the number of stations
exceeds the maximum that can be displayed on the first page.
5. When done, the configuration is automatically saved.
³ To edit an existing management station:

1. Use the left and right arrows to move the selection block to the desired cell in
the row of the management station to be edited.
2. Select Change cell to open the corresponding field for editing. Use the
procedure described above to select a new value for the selected field.

Configuring System Logistic Information

Use the following procedure to specify logistic information to be used to identify
the specific Megaplex-4100 unit, provide contact information, etc.
Device Info.
A typical Device Info screen is shown in Figure 4-19. The information that can be
defined using this screen is described in Table 4-5.
MP-4100
Configuration>System>Management>Device Info
Sys Description... (Sys type:MP-4100 Sys Ver:1.01 Chassis Revision:0)

Object ID ... (radMP4100)
1. Device Name ... ()
2. Contact Person ... (Name of contact person)
3. Location ID ... (The location of this device)
>

Figure 4-19. Typical Device Info Screen

To configure an entry, select its number and then type the desired text. When
done, press <Enter>.
Table 4-5. Device Info Parameters
Sys Description Displays a fixed string that identifies the system type, Depends on equipment version
its version and the chassis revision
Object ID Displays the formal Megaplex-4100 object identifier radMP4100

(its MIB root)
Device Name Used to assign an identification string to this unit Up to 22 characters.

Default: Empty string
Contact Person Used to enter the name of the person to be contacted Up to 46 characters.
in matters pertaining to this equipment unit Default: Name of contact person
Location ID Used to enter a description of the physical location of Up to 34 characters.

this equipment unit Default: The location of this device

4.2 Configuring Megaplex-4100 for SNMPv3

Management
This section presents the main SNMPv3 capabilities, and explains the following
procedures:
• How to enable the SNMPv3 security features
• How to configure Megaplex-4100 for management with SNMPv3 security
features.
• How to configure Megaplex-4100 for compatibility with management stations
that cannot use the SNMPv3 security features, to ensure compatibility with
SNMP support in previous Megaplex-4100 software and management station
versions. This is performed by mapping SNMPv1 settings to SNMPv3 settings.
You can find below a concise description of the main SNMPv3 capabilities
applicable to Megaplex-4100, and descriptions of terms related to the SNMPv3
configuration parameters of Megaplex-4100.
Overview of SNMPv3 Capabilities

The basic SNMP protocol (SNMP version 1, or SNMPv1) can neither authenticate
the source of a management message, nor provide privacy (encryption). The
SNMP version 2 of the protocol (SNMPv2) adds some functional improvements
and extensions to SNMPv1, but does not address security problems.
To overcome the security shortcomings of SNMPv1 and SNMPv2, Megaplex-4100
can be configured to use the security features of SNMP protocol version 3
(SNMPv3).
SNMPv3 provides a security framework for SNMPv1 and SNMPv2 that adds the
following main capabilities:
• Authentication – checks the integrity of management data, and also verifies
its origin to ensure that unauthorized users will not masquerade as
authorized users
• Privacy – ensures that unauthorized users cannot monitor the management
information passing between managed systems and management stations
• Authorization and access control – ensures that only authorized users can
perform SNMP network management functions and contact the managed
systems.
To support these additional capabilities, SNMPv3 also includes specific
administrative features, such as naming, security policies, user and key
management, and selectable notification capabilities.
Note Key management requires the using organization to implement an appropriate

key distribution method, which is beyond the scope of SNMPv3, and therefore is
also not covered in this manual. It is the responsibility of the using organization
to maintain appropriate key management and distribution channels.
Megaplex-4100 Ver. 2.0 Configuring Megaplex-4100 for SNMPv3 Management 4-19

User-Based Security Model (USM)

SNMPv3 authentication and privacy services are provided by means of the
User-Based Security Model (USM), defined in RFC2272. Proper use of USM
protects against modification of information in transit from an authorized entity
(including modification of message order, delaying or replaying of valid messages
to change their effect, etc.), prevents an unauthorized entity from performing
management operations by assuming the identity of an authorized entity, and
prevents disclosure of the contents of the messages exchanged between a
management station and an agent.
To achieve these goals, USM uses authentication to check the integrity of
transmitted messages, and encryption to prevent disclosure:
• Authentication mechanisms. Mechanisms that provide integrity checks based
on a secret key are usually called message authentication codes (MAC).
Typically, message authentication codes are used between two parties that
share a secret key in order to validate the information transmitted between
these parties. Therefore, an SNMP engine requires an authentication key and
a privacy key (actually, for each management session, a set of one-time
session keys are generated). Separate values of these two keys are
maintained for each local and remote user, and their values must be stored
by each user, because the keys are not accessible via SNMP.
USM authentication protocol is based on the key-Hashing Message
Authentication Code (HMAC), described in RFC2104. HMAC uses a user-
selected secure hash function and a secret key to produce a message
authentication code. USM allows the use of one of two alternative
authentication protocols, where both generate a 96-bit output that is used
to check message integrity:
HMAC-MD5-96: HMAC is used with MD5 (Message Digest algorithm 5) as the
underlying hash function.
HMAC-SHA-96: HMAC is used with SHA-1 (Secure Hashing Algorithm 1).
• Encryption mechanism. USM uses the cipher block chaining (CBC) mode of the
Data Encryption Standard (DES) for encryption, with a key length of 56 bits.
SNMP Security Levels

The USM capabilities enable the user to select the level of security at which SNMP
messages can be sent or with which operations are being processed. The
available options are as follows:
• No authentication and no privacy (encryption) – the lowest protection.
• With authentication, but without privacy
• With authentication and with privacy – the best protection level.
SNMPv3 Administrative Features

The administrative features of SNMPv3 enable determining the entities that are
allowed to manage an entity, for example, the Megaplex-4100. There are two
administrative aspects:
4-20 Configuring Megaplex-4100 for SNMPv3 Management Megaplex-4100 Ver. 2.0

• User management. During SNMPv3 configuration, it is necessary to define

allowed users and their security attributes. For each user, it is possible to
select the security level, and the passwords used for each type of protection
(authentication and/or privacy) needed at the selected level.
• Target and notification management. As part of the SNMPv3 configuration,
you can also define the notification capabilities for a list of entities referred
to as targets (of notification messages). For each target, you can specify a
message processing model, a security model, and the required security level.
You can also define a list of notifications that can be sent to the
corresponding target.
Note Megaplex-4100 supports only the sending of traps for notification purposes.
View-Based Access Control Model (VACM)

SNMP manager authorizations are defined by means of the view-based access
security model (the name of the model is derived from the method used to
define the authorizations: control over the MIB parts that can be viewed by each
manager).
VACM makes it possible to configure each SNMPv3 agent to allow different levels
of access to different managers: for example, the Megaplex-4100 SNMPv3 agent
may restrict some managers to view only the Megaplex-4100 performance
statistics, and allow others to view and update Megaplex-4100 configuration
parameters. Moreover, the SNMPv3 agent can also limit what a manager can do
by accepting only commands that invoke parameters included in certain parts of
the relevant MIBs (for example, read-only access to the configuration parameters
part of a MIB, and read-write access to the diagnostics part).
The access control policy used by the agent for each manager must be
preconfigured (the policy essentially consists of a table that details the access
privileges of each authorized manager). For Megaplex-4100, the configuration of
the VACM parameters can only be made by means of a MIB browser, and/or by
SNMP commands.
Note RAD also offers a dedicated SNMPv3 Manager utility to help you edit parameters
not covered by the supervision terminal screens. For additional information,
contact RAD Technical Support.
Configuring SNMP Engine ID

The SNMP engine ID is a parameter defined in relation with SNMPv3, whose
primary function is to provide a unique and unambiguous identifier of the local
SNMP engine (processor), which is part of the Megaplex-4100 management
subsystem. Thus, it thus also identifies the local Megaplex-4100.
SNMPv3 bases the generation of session keys on several parameters, one of
them being the SNMP engine ID. Therefore, the SNMP engine ID must always be
configured before configuring any other SNMPv3 parameters, and in particular –
before configuring users (if you change the SNMP engine ID, you must also
reconfigure the users). Thus, you can configure the SNMP engine ID even when
SNMPv3 support is disabled.

The SNMP engine ID is a string that has three components:

• An automatically-generated, fixed part
• A part that identifies the configuration type (method) used to derive the
user-defined part is selectable.
• A user-defined part, which must be unique within the SNMP-managed
network. The method used to configure this part depends on the
configuration type.
³ To specify the SNMPv3 Engine ID:

2. Select SNMPv3 Engine ID.
A typical SNMP Engine ID screen, as seen when using the text
configuration type, is shown in Figure 4-20. The current SNMP engine ID
string appears in the Engine ID field: whenever the Engine ID Config Type
is changed, the string is automatically updated.
3. To change the user-defined part and/or the configuration method used to
derive the user-defined part, select Engine ID Config Type and/or Rest Bytes,
(the appropriate procedure is described below). Megaplex-4100 supports the
following configuration types:
IPv4 The user-defined part is based on the host IP address. This

ensures that the user-defined part is unique within the
SNMP-managed network.
After selecting this option, the Engine ID field is updated to
reflect the automatically assigned user part (based on the
Megaplex-4100 host IP address), and the Rest Bytes field
disappears.
MAC Address The user-defined part is based on the host MAC address.
This option also ensures that the user-defined part is
unique.
After selecting this option, the Engine ID field is updated to
reflect the automatically assigned user part (based on the
Megaplex-4100 host MAC address), and the Rest Bytes
field disappears.
Text The user-defined part is entered as a text string, which

must comprise 4 to 27 alphanumeric characters.
After selecting this option, the Engine ID field is reset to
display only the fixed part and the configuration type part,
and a Rest Bytes field appears.
To modify the user-defined part, select Rest Bytes, and
then type the prescribed string.
When done, press <Enter> to confirm. The string is added
to the Engine ID field (if the string is too long for the
available display space, it is truncated, in which case the
last digits are replaced by an ellipsis …)

4. After making changes on the SNMP Engine ID screen, a new item, S – Save, is
added: to activate the new engine ID, type s.
MP-4100
Configuration>System>Management>SNMP Engine ID
Engine ID ... (800000a40400000000 )
1. Engine ID Config Type > (Text)
2. Rest Bytes ... ()
>

-----------------------------------------------------------------------------
Figure 4-20. Typical SNMP Engine ID Screen
Enabling/Disabling SNMPv3 Security Features

When starting the SNMP configuration activities, the first action is to select
whether to enable or disable the SNMPv3 security features: this action effects all
the other SNMP parameters except SNMP Engine ID.
When changing the SNMPv3 mode, all the SNMPv3 settings are erased, and the
factory defaults are restored. As explained in the Configuring Authorized User
Security Parameters section, starting from the factory defaults will enable
preparing a new set of SNMPv3 settings in accordance with your specific
application requirements.
To enable configuring the SNMPv3 parameters, you must enable SNMPv3.
³ To enable the SNMPv3 security features:

A typical Management screen with SNMPv3 security features disabled (the
factory default state) is shown in Figure 4-21.

MP-4100
Configuration>System>Management
1. Device Info >

2. Host IP >
3. Manager List []>
4. Mng Access >
5. Flow >
6. SNMP Engine ID >
7. SNMPv3 (Disabled))
>

-----------------------------------------------------------------------------
Figure 4-21. Typical Management Submenu (SNMPv3 Disabled)

2. To change the state, select SNMPv3: you are prompted to confirm by a
message that explains the effects: Current configuration of SNMP agent will be
deleted! Continue? (Options: Y/N):
To abort, type n
To confirm, type y.
3. After typing y, the SNMPv3 state is toggled to Enabled, and a S – Save item is
added.
4. To activate the selection, type s. The screen is refreshed and the SNMPv3
Setting item, used to access the SNMPv3 configuration tasks (see the
Configuring for SNMP Management with SNMPv3 Security section) is added.
Note The same sequence is used to disable SNMPv3 (see also the Configuring Host IP
Parameters and SNMP Communities (with SNMPv3 Disabled) section).
Configuring for SNMP Management with SNMPv3 Security Features
SNMPv3 Configuration Sequence
Note Before starting, make sure to configure the SNMP engine ID and enable SNMPv3
as explained above.
The SNMPv3 configuration sequence is as follows:

1. Configure security attributes for the prescribed users (management
stations).
2. Add the prescribed notification tags.
3. Assign traps to each notification tag, to create a tag list.
4. Specify for each target its IP address, define its parameter set, and assign
notification tags.
5. Add target (management stations) parameters.

Note With SNMPv3, the managers configured by means of the Manager List screen (see
the Configuring the Manager List (with SNMPv3 Disabled) section) are no longer
relevant: only the configured targets are managers.
However, to enable synchronizing the managers configured in the Manager List
table with SNMPv3 managers, all the IP addresses configured in the Manager List
table are automatically added to the target list when SNMPv3 is enabled (they
can be seen in the Summary Target Table – see the Viewing the Summary Target
Table section), but they are not active until their security and management
parameters are defined.
The SNMPv3 parameters are configured by means of the SNMPv3 Setting

submenu. A typical submenu is shown Figure 4-22. The parameters displayed on
the submenu and the tasks that can be initiated are explained in Table 4-6.
Note In addition to the parameters that can be configured using the SNMPv3 Setting
submenu, Megaplex-4100 supports additional parameters used to customize
SNMPv3 management in accordance with the application requirements. These
parameters can only be configured by means of a MIB browser, and/or SNMP
commands (RAD may also offer a dedicated SNMPv3 Manager utility to help you
edit the additional parameters). For additional information, contact RAD Technical
Support.
MP-4100
Configuration>System>Management>SNMPv3 setting
Engine Boots (4)

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

-----------------------------------------------------------------------------
Figure 4-22. Typical SNMPv3 Setting Submenu
Table 4-6. SNMPv3 Setting Submenu
Engine Boots Displays the number of times that the The display range is 1 to 2147483647.
SNMP engine has been reinitialized since Default: 0
the SNMP Engine ID was last configured

Engine Time Displays the time, in seconds, that expired The display range is 0 to 2147483647.
since the value of the Engine Boots field Default: 0
was last changed (that is, the time since
the last SNMP engine reinitialization)
SNMP Message Displays the maximum allowed length, in The allowed range is 484 to 2147483647.
Size octets, of the SNMP messages that the Default: 1500
Megaplex-4100 can send or receive, and
process.
In addition to the maximum supported by
the Megaplex-4100 SNMP engine, the
message size must be supported by all the
transport links available to communicate
with the SNMP engine
Users Opens the Users submenu, used to See Table 4-7

configure the USM parameters to be used
by the authorized SNMPv3 users
Targets & Notify Opens the Targets & Notify submenu, used See Table 4-8 to Table 4-11
to configure the parameters of the targets
(management stations that can manage
the Megaplex-4100), and configure
notifications of Megaplex-4100 events
SNMPv1/v3 Opens the SNMPv1/v3 Mapping submenu, See Table 4-11

Mapping used to configure the mapping of SNMPv1
security parameters to SNMPv3
parameters, to enable the Megaplex-4100
to support all the SNMP versions
SNMPv3 Factory Used to reload the SNMPv3 factory default To restore defaults, select SNMPv3 Factory
Defaults parameters. Defaults, and then confirm the action
This is useful for erasing the existing
configuration parameters and restoring the
SNMP engine to a known state.
In particular, this function is needed to
recover from configuration errors that may
prevent SNMP management
Summary User Displays information on the existing users See the Viewing the Summary User Table
Table and their main configuration data section
Summary Target Displays information on the existing See the Viewing the Summary Target Table
Table targets, and their main configuration data section
Configuring Authorized User Security Parameters

Megaplex-4100 supports up to ten SNMPv3 managers, each having
independently-configurable authorizations and security attributes. The security
attributes needed by the USM to protect the SNMP traffic between

Megaplex-4100 and the prescribed managers are configured by means of Users

screen.
Megaplex-4100 has a single factory-default user, designated by the security
name initial, which is configured for non-secure operations (that is, no
authentication and no privacy). Non-secure operations are essential as a starting
point for preliminary configuration, but additional users with appropriate
authorizations and security attributes must be configured as soon as possible, to
avoid defeating the very purpose of SNMPv3.
When several users are already defined, you can scroll the Security Name names
by typing f (forward) or b (backward). Always remove a user when you must
change its security parameters, and then define a new user with the desired
parameters.
You can view the existing users, and their authorizations and security attributes
by selecting Summary User Table, as explained in the Viewing the Summary User
Table section.
Note
User access control policies are defined via the vacmSecurityToGroupTable
and vacmAccessTable tables, which can be accessed only as explained in the
Note on page 4-25.
³ To configure USM parameters for new users:

1. Navigate to Configuration > System > Management > SNMPv3 Setting > Users.
A typical SNMPv3 Setting screen with the factory-default user parameters
is shown in Figure 4-23. The user configuration parameters are explained
in Table 4-7.
MP-4100
Configuration>System>Management>SNMPv3 setting>Users
1. Security Name ... (initial)

2. Authentication Protocol > (usmNoAuthProtocol)
>
F - Forward; B - Backward; R - Remove

-----------------------------------------------------------------------------
Figure 4-23. Typical Factory-Default Users Screen

2. To add a new user, select Security Name and then type the desired user name,
to replace the displayed user name.
3. Select Authentication Protocol, and then select one of the options listed in
Table 4-7.
4. Additional fields, explained in Table 4-7, are displayed automatically after you
make selections (and press <Enter> to confirm) for the Authentication Protocol

and Privacy Protocol. Figure 4-24 shows a typical new user configuration
screen, as seen after making all the necessary selections.
MP-4100
Configuration>System>Management>SNMPv3 setting>Users
1. Security Name ... (User1)

2. Authentication Protocol > (usmHMACMD5AuthProtocol)
3. Privacy Protocol > (usmDESPrivProtocol)
4. Authentication Password ...
5. Privacy Password ...
>

----------------------------------------------------------------------------
Figure 4-24. Typical Users Screen for New User

5. Repeat the configuration steps for the other users. When done, save the
configuration.
Table 4-7. SNMPv3 Users Security Parameters
Security Name Used to select the user name (the security Alphanumeric string of up to 32 characters.
name and the user name are equivalent Default: userName
under SNMPv3).
This security name is used to tie the USM
security attributes with management
attributes, in particular, the authorizations
configured by means of the Target Param
screen, the IP address configured by means
of the Target Address screen, etc.
Authentication Used to select the authentication protocol usmNoAuthProtocol – no authentication

Protocol for this user. protocol. This also prevents the use of
SNMPv3 uses the key-Hashing Message privacy (encryption) for this user.
Authentication Code (HMAC) authentication usmHMACMD5AuthProtocol – use of
method, described in RFC2104 authentication protocol enabled. The
authentication protocol is HMAC-MD5-96
(HMAC with MD5 (Message Digest algorithm
5) as the underlying hash function)
usmHMACSHAAuthProtocol – use of
authentication protocol enabled. The
authentication protocol is HMAC-SHA-96
(HMAC with SHA-1 (Secure Hashing Algorithm
1 as the underlying hash function).
Default: usmNoAuthProtocol

Privacy Protocol Used to select the privacy (encryption) usmNoPrivProtocol – no privacy protocol.
protocol for this user. usmDESPrivProtocol – use of privacy protocol
This parameter is not displayed when enabled. SNMPv3 uses the cipher block
Authentication Protocol is chaining (CBC) mode of the Data Encryption
usmNoAuthProtocol Standard (DES) for encryption, with a key
length of 56 bits.
Default: usmNoPrivProtocol
Authentication Used to enter the password to be used by Alphanumeric string of up to 32 characters.

Password the authentication protocol. Default: Empty string
Make sure to check, and if necessary
correct, your entry before pressing <Enter>
to confirm: after pressing <Enter>, the
typed string is removed.
This parameter is not displayed when
Authentication Protocol is
usmNoAuthProtocol
Privacy Used to enter the password required to use Alphanumeric string of up to 32 characters.
Password privacy. Default: Empty string
Make sure to check, and if necessary
correct, your entry before pressing <Enter>
to confirm: after pressing <Enter>, the
typed string is removed.
Privacy Protocol is usmDESPrivProtoco
³ To remove an existing user:

1. Display the required Security Name by scrolling with f (forward) or b
(backward).
2. Type r and then confirm.
Configuring SNMPv3 Management Attributes

A typical Targets & Notify submenu is shown in Figure 4-25. The activities started
from this submenu supplement the user security attributes by enabling to define
the additional attributes needed for management.
The submenu tasks are listed below:
• Target Params: used to configure a general set of parameters for each target,
and associate it with a particular set of user security attributes (identified by
specifying a Security Name already configured in accordance with Table 4-7).
Each target is assigned a unique logistic identifier, the target Name, for
identifying the associated set of parameters (see Table 4-8). Note however
that in Table 4-10 this identifier is referred to as Params Name
• Target Address: used to configure the IP address and notification parameters
for a selected target logistic Name (Table 4-10). The IP address is associated

with the Params Name (defined in Table 4-8) for identification, and with a
Tag List for identifying the set of notification parameters (see Table 4-9)
• Notify: used to configure notification tags (see Table 4-9). Each set of
notification parameters is assigned a unique Tag name for identification.
Note however that in Table 4-10 this identifier is referred to as Tag List
• Trap: used to select traps included in the list of each selected notification tag
You can view the existing targets and their management attributes by selecting
Summary Target Table, as explained in the Viewing the Summary Target Table
section.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify
1. Target Params >

2. Target Address >
3. Notify >
4. Trap >
>

-----------------------------------------------------------------------------
Figure 4-25. Typical Targets & Notify Submenu
Configuring Target Parameters
³ To configure a new set of target parameters:

1. Navigate to Configuration > System > Management > SNMPv3 Setting > Targets
& Notify.
2. Select Target Params.
A typical Target Params screen is shown in Figure 4-26.
3. Configure the target parameters, and then type s to save. The parameters that
can be configured are explained in Table 4-8.

MP-4100
...ation>System>Management>SNMPv3 setting>Targets & Notify>Target Params
1. Name ... ()
2. Message Processing Model > ()
3. Security Model > ()
4. Security Name ... ()
5. Security Level > ()
>

-----------------------------------------------------------------------------
Figure 4-26. Typical Targets Params Screen
Table 4-8. Target Params Parameters
Name Used to enter the unique logistic name Alphanumeric string of up to 32 characters.
assigned to the target (also referred to as Default: Empty string
Params Name on other screens).
To enter a new target name, type the
desired name in this field
Message Used to select the message processing The available selections are: SNMPv1, SNMPv2c
Processing model to be used when generating and (SNMPv2 with community-based security
Model processing SNMP messages for this target model), SNMPv2u (SNMPv2 with user-based
security model (USM)), and SNMPv3.
Default: SNMPv3
Security Model Used to select the security model to be The available selections are: Any, SNMPv1,
used when generating and processing SNMP SNMPv2c, USM (User-Based Security Model),
messages for this target and Not Defined.
Default: USM
Security Name Used to select the security name which Alphanumeric string of up to 32 characters.
identifies the security attributes applicable Default: Empty string
to SNMP traffic exchanged with this target.
Use one of the names configured by means
of the Users screen
Security Level Used to select the level of security to be The available selections are:
used when generating SNMP messages for noAuthNoPriv – No authentication, no privacy.
this target
authNoPriv – With authentication, no privacy.
authPriv – With authentication and privacy.
Default: noAuthNoPriv

When several targets are already defined, you can scroll the target logistic Name
by typing f (forward) or b (backward). Always remove a target when you must
change one of its management attributes, and then define a new target with the
desired parameters.
³ To remove an existing target:

1. Display the required Name by scrolling with f (forward) or b (backward).
Configuring Notification Tags

A notification tag identifies a list of traps that can be sent to selected targets.
The configuration of a new notification tag is performed in two steps:
1. Adding a new notification tag.
2. Selecting the list of traps identified by the notification tag.
³ To add a new notification tag:

& Notify.
2. Select Notify.
3. Configure the parameters as explained in Table 4-9, and then type s to save.
A typical Notify screen, as seen after configuring a new notification tag,
is shown in Figure 4-27. The Type field is displayed only after selecting a
Name.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Notify
Type > (trap)

1. Name ... (notify_set_1)
2. Tag ... (v3traps)
>

-----------------------------------------------------------------------------
Figure 4-27. Typical Notify Screen

Table 4-9. Notify Parameters
Type Displays the type of notifications generated The only option is Trap.
for the selected notification tag. Default: Trap
The type is always set to Trap, the only option
supported by Megaplex-4100
Name Used to enter the logistic identifier associated Alphanumeric string of up to 32 characters.
with this notification tag (also referred to as Default: Empty string
Notify Name on other screens).
To enter a new target name, type the desired
name in this field
Tag Used to enter the notification tag name, which Alphanumeric string of up to 32 characters.
is used to select entries for the events Default: Empty string
associated with the Tag List in Table 4-10
When several notification tags are already defined, you can scroll their names by
typing f (forward) or b (backward). Always remove a notification tag when you
must change one of its attributes, and then define a new notification tag with
the desired parameters.
³ To remove an existing notification tag:

1. Display the required notification tag Name by scrolling with f (forward) or b
(backward).
³ To configure the trap and notification tag associations:

& Notify.
2. Select Trap.
A typical Trap screen is shown in Figure 4-28.
MP-4100
Configuration>System>Management>SNMPv3 setting>Targets & Notify>Trap
1. Trap Name > (link Up)

2. Notify Name > (notify_set_1)
>

-----------------------------------------------------------------------------
Figure 4-28. Typical Trap Screen

Using the Trap screen, you can associate traps with the names appearing the
Notify screen (see Table 4-9). When done, type s to save.
Trap Name Used to select a trap name for association with the
notification tag.
The selection is made on a separate screen, which list the
available traps. Each trap has an index number: type the
index number and then press <Enter> to associate the trap
with the notification tag.
Notify Name Used to specify the corresponding notification tag (enter a

Name defined in Table 4-9).
The selection is made on a separate screen, which list the
available notification tags defined by means of Table 4-9.
Each name has an index number: type the index number
and then press <Enter> to select the notification tag.
³ To remove a trap from the list associated with a notification tag:

1. Display the required Trap by scrolling with f (forward) or b (backward).
Configuring Target Transport Parameters

The Target Address screen is used to configure the IP address and select a tag list
for a selected target.
³ To configure the target transport parameters:

& Notify.
2. Select Target Address.
A typical Target Address screen is shown in Figure 4-29.
MP-4100
...tion>System>Management>SNMPv3 setting>Targets & Notify>Target Address
1. Name ... ()
2. IP Address ... ()
3. Params Name ... ()
4. Tag List ... ()
>

-----------------------------------------------------------------------------
Figure 4-29. Typical Target Address Screen

3. Configure the target transport parameters, and then type s to save. The
parameters that can be configured are explained in Table 4-10.
Table 4-10. Target Address Parameters
Name Used to enter the logistic name assigned to Alphanumeric string of up to 32 characters.
the desired target transport parameters Default: Empty string
IP Address Specifies the IP address of this target Enter the prescribed IP address, in the dotted-
quad format.
Default: Empty string
Params Specifies the logistic name used to identify the Alphanumeric string of up to 32 characters.
Name set of SNMP parameters to be used when Default: Empty string
generating messages to be sent to this
transport address.
Use a Name defined in the Target Params
table (Table 4-8)
Tag List Specifies a list of tag values which are used to Alphanumeric string of up to 32 characters.
select target addresses for a particular Default: Empty string
operation.
Use a Tag defined in the Notify table
(Table 4-9)
Configuring SNMPv1/v3 Mapping

This screen is used to configure the mapping of SNMPv1 security parameters
(communities) to SNMPv3 security parameters, to enable the Megaplex-4100 to
support all the SNMP versions.
A typical SNMPv1/v3 Mapping screen is shown in Figure 4-30. The parameters
that can be configured are explained in Table 4-11.
MP-4100
Configuration>System>Management>SNMPv3 setting>SNMPv1/v3 Mapping
1. Community Index ... ()

2. Community Name ... ()
3. Security Name ... ()
4. Transport Tag ... ()
>

-----------------------------------------------------------------------------
Figure 4-30. Typical SNMPv1/v3 Mapping Screen

Table 4-11. SNMPv1/v3 Mapping Parameters
Community Used to enter a unique index for this Alphanumeric string of up to 32 characters.
Index mapping item Default: Empty string
Community Used to enter the community string (a Alphanumeric string of up to 32 characters.

Name SNMPv1 security parameter) to be mapped to Default: Empty string
a security name.
The community string is case-sensitive
Security Name Specifies the security name (which identifies Alphanumeric string of up to 32 characters.
a set of security attributes) to be used in Default: Empty string
SNMPv3 messages for the selected
community name.
Use a Security Name already configured in
accordance with Table 4-7
Transport Tag Specifies the IP address (manager) from Enter the prescribed IP address, in the
which SNMPv1 management requests will be dotted-quad format.
accepted for this community name. Default: Empty string
Use a IP Address already configured in
accordance with Table 4-10
Viewing the Summary User Table

The Summary User Table screen displays information on the existing users and
their main configuration data. A typical Summary User Table screen is shown in
Figure 4-31. The user parameters are explained in Table 4-7.
MP-4100
Configuration>System>Management>SNMPv3 setting>Summary User Table
User Security Model Security Level

initial USM noAuthNoPriv
>
ESC-prev.menu; !-main menu; &-exit; @-debug; ?-help 1 M/ 1 C

-----------------------------------------------------------------------------
Figure 4-31. Typical Summary User Table Screen
Viewing the Summary Target Table

The Summary Target Table screen displays information on the existing targets,
and their main configuration data:

• Address – target IP address

• MPModel – message processing model
• SecModel – security model
• SecName – security name
• SecLevel – security level
All the managers configured in the Manager List table are automatically added to
this table when SNMPv3 is enabled, but if no security and management
parameters have been defined for the corresponding target address, all the table
fields in the corresponding row, except Address, remain empty.
A typical Summary Target Table screen is shown in Figure 4-32. The target
parameters are explained in Table 4-8 and Table 4-10.
MP-4100
Configuration>System>Management>SNMPv3 setting>Summary Target Table
Address MPModel SecModel SecName SecLevel
>

-----------------------------------------------------------------------------
Figure 4-32. Typical Summary Target Table Screen
Megaplex-4100 Ver. 2.0 Configuring Megaplex-4100 for Operation 4-37

4.3 Configuring Megaplex-4100 for Operation
Managing Megaplex-4100 Configuration Databases

Before starting configuration activities, it is important to understand the
Megaplex-4100 database tools (reached from the DB Tools menu), used to
manage Megaplex-4100 databases.
Normally, only one database is needed to store the Megaplex-4100 configuration
parameters. However, Megaplex-4100 can store a few databases in the CL
module flash memory, and therefore, when necessary, it is possible to prepare
additional databases with alternative configurations, and store them in the
Megaplex-4100 flash memory for immediate availability. Megaplex-4100
databases are assigned index numbers in the range of 1 to 10.
Therefore, the following terms are used in respect to Megaplex-4100 databases:
• Online database file: one database file, which is always assigned index
number 1, serves as the current online (active) database. This is the file
from which parameters have been downloaded to the Megaplex-4100
modules, and therefore it determines the current Megaplex-4100 operation
configuration.
• All the other database files are simply stored in the flash memory. These
files may have been created by the user using the database tools or the
file system utilities, or received by TFTP from a remote host or
management station.
Any authorized user (including operators of management stations, etc.) can work
on the edit buffer without affecting the online database, for example:
• Make changes to the database copy located in the edit buffer
• Replace the edit buffer contents with the factory defaults
• Load into the edit buffer another database file, thus also replacing the
current contents with new contents.
A desired database can be created or updated by a dedicated Update DB
command, which performs the following actions:
4. Initiates a sanity check on the edit buffer contents, and reports errors and
warnings.
5. If no errors are detected, saves the edit buffer contents to a specified
database (the database number is selected by the user).
• Normally, changes are saved to the active, or online, database. In this case,
after successfully saving the buffer contents to flash memory,
configuration messages are automatically sent to the Megaplex-4100
subsystems to change their operating mode in accordance with the new
online database. As mentioned above, the number of the active database
is always 1, irrespective of the number of the database loaded into the edit
buffer as a basis for changes.
• Alternatively, you can specify the number of another database, using the
Update DB command, in which to store the edit buffer contents. If the
4-38 Configuring Megaplex-4100 for Operation Megaplex-4100 Ver. 2.0

database whose index is specified in the Update DB command is not yet

stored in the flash memory, a database with this index number is created
and the edit buffer contents are stored in it.
Note that alternative databases may be assigned any desired number,
except 1, because 1 is reserved for the active database.
6. When preparing alternative databases, it is convenient to change the default
database, that is, the database which is updated when you use the shortcut
% - DB Update:
• If you do not select a specific default database, the shortcut updates the
active database (database 1)
• If you specify another database stored in the flash memory as default, the
shortcut updates the default database. In this case, after preparing the
alternative database, it is recommended to return the default selection to
database 1.
Overview of DB Tools Menu

Figure 4-33 shows the structure of the DB Tools menu, used to manage the
Megaplex-4100 databases.
Load DB
DB Tools
Default DB
1. Load DB
2. Default DB
3. Load HW
4. Update DB Update DB
5. DB List
6. Delete DB
DB List
Delete DB
Figure 4-33. DB Tools Menu Structure
Database Management
A typical DB Tools menu is shown in Figure 4-34. The functions performed by
means of the various options available on the DB Tools menu are explained in
Table 4-12.

MP-4100
Configuration>DB Tools
1. Load DB >
2. Default DB > (1)
3. Load HW
4. Update DB >
5. Delete DB >
>

-----------------------------------------------------------------------------
Figure 4-34. Typical DB Tools Menu
Table 4-12. DB Tools Menu Functions
Item Action
Load DB Load a selected database into the edit buffer.

This database is now the candidate for becoming the online database (this
will occur after a successful database update)
Default DB Select the default database. This is the database to which parameters will
be saved when using the % – DB Update hotkey.
The factory defaults are provided as database 1
Load HW Load the factory defaults into the edit buffer, and then read the hardware
(modules) installed in the Megaplex-4100, and update the list of
programmed hardware accordingly
Update DB Copy the contents of the edit buffer to a selected database in the flash
memory. This function can also be used to create and store a new database.
If you save the changes to the default database, the changes will be
activated, that is, the operation mode of the Megaplex-4100 changes in
accordance with the new parameter values.
Delete DB Delete a database stored in the Megaplex-4100
The following sections explain how to use the commands available on the DB
Tools menu to perform typical activities. For typical applications of these
commands, refer to the preliminary configuration instructions given in Chapter 3.
³ To load a selected database into the edit buffer:

1. Select Load DB on the DB Tools menu.
2. On the Load DB screen (Figure 4-35), type the number of the desired
database. Note that only the numbers of the existing databases are displayed
on the screen.

MP-4100
Configuration>DB Tools>Load DB
1. 1
2. 2
>

-----------------------------------------------------------------------------
Figure 4-35. Typical Load DB Screen

3. Press <Enter>: after a short delay, the execution is confirmed by the following
message Database # was loaded. Press any key to continue, where # stands
for the number of the selected database.
4. Press any key: you will see the DB Tools menu again.
³ To select the default database:

1. Select Default DB on the DB Tools menu.
2. On the Default DB screen (Figure 4-36), type the desired database index
number, and then press <Enter>. Note that you can select any index number,
even if the corresponding database is not yet stored in the flash memory.
MP-4100
Configuration>DB Tools>Default DB (1)
1. 1
2. 2
3. 3
4. 4
5. 5
6. 6
7. 7
8. 8
9. 9
10. 10
>

-----------------------------------------------------------------------------
Figure 4-36. Typical Default DB Screen
Note On the next % (DB Update) command, the Megaplex-4100 will copy from the edit
buffer to the selected default database, provided the edit buffer configuration
passes successfully the sanity check.

³ To initialize the Megaplex-4100 database:

1. Select Load HW on the DB Tools menu.
2. You will see a “The DB will reset to default. Do you want to proceed – Y/N?”
message.
3. Type Y to confirm. You can now go back to the main menu and start the
configuration activities.
³ To update a desired database with the edit buffer configuration:

1. Select Update DB on the DB Tools menu.
2. On the Update DB screen (Figure 4-37), type the desired database index
number, and then press <Enter>. Note that you can select any index number,
even if the corresponding database is not yet stored in the flash memory. The
databases in use are identified on the displayed list.
MP-4100
Configuration>DB Tools>Update DB
1. 1 (in use)
2. 2 (in use)
3. 3
4. 4
5. 5
6. 6
7. 7
8. 8
9. 9
10. 10
>

-----------------------------------------------------------------------------
Figure 4-37. Typical Update DB Screen

3. You are requested to confirm by Are you sure you want to update active
database – Y/N?, or by Are you sure you want to update selected database –
Y/N?, depending on whether you update the active database, or other
database:
• Type n to cancel the request. The changes made to the database in the
edit buffer are not affected, and therefore you can either continue editing,
or simply postpone the update. However, take into consideration that any
unsaved changes are lost when the Megaplex-4100 is powered down.
• Type y to confirm. In this case, a sanity check is automatically performed
on the edited database.
4. The continuation depends on the results of the sanity check:
• If neither errors, nor warnings are detected by the sanity check, then you
will see a Configuration File Update is in Process message.

Wait for the message to disappear before continuing (this takes a few
seconds): although you can press <ESC> and return to the menu to
continue entering new commands, this is not recommended. In particular,
do not reset the Megaplex-4100 before the update is completed: this will
cause the configuration data to be lost. Neither should Megaplex-4100
power be disconnected during this interval.
Note The storage space used by databases increases after each change. Sometimes,
the remaining storage space is not sufficient to save the updated database, and
you will see Save of Configuration File Failed. In this case, it is necessary to delete
unused databases.
After a short delay, the specified database is updated (or a new database
with the selected index number is created). If you had updated the active
database, the changes will be activated, that is, the operation mode of
the Megaplex-4100 changes in accordance with the new parameters
values.
Note If the updated active database includes changes to the serial port communication
parameters, you need to press <Enter> several times in sequence to reestablish
communication with the Megaplex-4100.
• If only warnings are detected by the sanity check, then you are notified by
a Warnings exist. Database update started message, however the specified
database is updated, as explained above.
You can request to see the warnings by typing $ (the show sanity
command), even as the configuration file update proceeds (in this case,
first press <ESC>), and then correct the configuration accordingly.
• If errors have been detected, the updating request is rejected, and you see
Errors in configuration. Do you want to see errors?
You can type y to confirm. In this case, you will see the Errors and
Warnings screen. Refer to Chapter 5 for error explanations and
corrective actions.
Alternatively, type n to cancel and abort the update.
³ To delete an existing database:

1. Select Delete DB on the DB Tools menu.
2. You will see the DB screen (Figure 4-38). Note that only the numbers of the
existing databases are displayed on the screen.
3. Type the number of the desired database, and confirm.
You are requested to confirm: “Do you want to delete DB-#– Y/N?”. Type Y
to confirm, N to cancel.
4. You will see a Database deleted successfully. Press any key to exit screen.
After pressing any key, you return to the DB Tools menu. In parallel, you will
see a Configuration File Update is in Process message, which disappears when
the configuration file is successfully updated.

MP-4100
Configuration>DB Tools>Delete DB
1. 1
2. 2
3. 10
>

-----------------------------------------------------------------------------
Figure 4-38. Typical Delete DB Screen
Configuring System Parameters

³ To configure the system parameters:
1. Use Configuration>Quick Setup to configure the basic Megaplex-4100 IP
communication parameters.
2. Use the Configuration>System menu to perform the following activities:
1. If necessary, reload factory defaults to start the configuration from a
known baseline.
2. Program the modules installed in the Megaplex-4100 chassis.
3. Configure the Megaplex-4100 serial control port, and the authorizations
of the users allowed to use the serial port.
4. Configure the Megaplex-4100 Ethernet control port.
5. Select the SNMP support mode (SNMPv3 security features enabled or
disabled).
6. Configure Megaplex-4100 management parameters, and management
access authorizations.
Note Configuration instructions for SNMP management appear in Section 4.2.
7. Configure system logistics information.

8. Set system time-of-day and date.
9. Configure the signaling profiles.
The System menu provides access to additional system-level configuration
activities that should be performed after configuring other parameters
(Figure 4-39 to Figure 4-44).

System
1. Card Type Card Type
2. Clock Source
3. TS Assignment Slot: PS-A PS-B CL-A CL-B IO-1 IO-2 IO-3
4. Mapping Card: PS PS CL1/155 CL1/155 M8E1 M8E1 M8SL
5. APS
6. Management Slot: IO-4 IO-5 IO-6 IO-7 IO-8 IO-9 IO-10
7. Control Port Card: M8SL HSU-12 HSU-12 HSU-12 HSU-12 VC-16/FXS VC-16/E&M
8. Date & Time
9. Factory Default
10. Reset Device
Source
13. Fault Propagation 1. Internal
2. Rx Clock
Clock Source 3. S Subsystem
1. Source
2. Master Port Rx Clock only
3. Fallback Port Master Port/Fallback Port
Entry Num Slot Port
TS Assignment 1 NONE -
1. IO 2 NONE -
2. CL | 3 NONE -
v4 NONE -
5 NONE -
See Sheet 2 6 NONE -
Mapping 7 NONE -
or Sheet 3
1. CL-A
2. CL-B 1. CL-A (CL1/155) 4. IO-2 (M8E1) 7. IO-5 (HSU-12) 10. IO-8 (HSU-12) 13. NONE
2. CL-B (CL1/155) 5. IO-3 (M8SL) 8. IO-6 (HSU-12) 11. IO-9 (VC-16/FXS)
3. IO-1 (M8E1) 6. IO-4 (M8SL) 9. IO-7 (HSU-12) 12. IO-10 (VC-16/E&M)
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
8. SNMPv3 Setting
Control Port
1. Serial Port
2. ETH
Date & Time

2. Set Date Format
3. Set Date
4. Set Time
Reset Device
2. IO-1
3. IO-2
4. IO-3
5. IO-4
6. IO-5
7. IO-6
8. IO-7
9. IO-8
10. IO-9 See
11. IO-10
Sheet 6
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy
5. Rx Idle
6. Profile Name
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces
Figure 4-39. Typical Configuration>System Submenu Structure (Sheet 1 of 6)

System
1. Card Type
2. Clock Source
3. TS Assignment Link 1
4. Mapping IO I/O-1
5. APS 1. Display Time Slots
6. Management 1. I/O-1 2. Manual
1. Link 1
7. Control Port 2. I/O-2 3. Connect Time Slots
2. Link 2
8. Date & Time 4. Delete TS (Per Slot and Port)
9. Factory Default See ..
3. I/O-3
..
3. Link 3
10. Reset Device
Sheet 1
. . 6. Split

or
CL
PDH 1
1. PDH 1 (Up)> 12. PDH 12 (Up)> 23. PDH 23 (Up)> 34. PDH 34 (Up)>
Clock Source 2. PDH 2 (Up)> 13. PDH 13 (Up)> 24. PDH 24 (Up)> 35. PDH 35 (Up)> 1. Display Time Slots
1. Source 3. PDH 3 (Up)> 14. PDH 14 (Up)> 25. PDH 25 (Up)> 36. PDH 36 (Up)> 2. Manual
2. Master Port 4. PDH 4 (Up)> 15. PDH 15 (Up)> 26. PDH 26 (Up)> 37. PDH 37 (Up)> 3. Connect Time Slots
Rx Clock only 5. PDH 5 (Up)> 16. PDH 16 (Up)> 27. PDH 27 (Up)> 38. PDH 38 (Up)>
3. Fallback Port
. .. ..

6. Split
TS Assignment . . . .
1. IO
(See below)
2. CL
Mapping Display Time Slots

Ts# 1 2 3 4 5 6 7 8
1. CL-A
2. CL-B
Ts# 9 10 11 12 13 14 15 16
APS
----- ----- ----- -----
.. ----- ----- ----- -----
1. APS Group Id
.
2. Protection
3. Revertive Manual
4. Working Port Ts# Slot Port Ts Type
5. Protection Port TS 01 IO-2 (M8E1) Link 1 1 DATA
6. WTR Time (Sec) TS 02 IO-2 (M8E1) Link 1 2 DATA
7. Flip Upon SD See Sheet 4 | TS 03 IO-2 (M8E1) Link 1 4 DATA
or Sheet 5 v TS 04 IO-2 (M8E1)
.. BND 1 -- DATA
Management .
1. Device Info
2. Host IP Connect Time Slots
3. Manager List PDH 1 1. Start TS
4. Mng Access 2. Slot
5. Flow 3. Port
6. SNMP Engine ID 4. Number of TS
7. SNMPv3 2. Manual
3. Connect Time Slots 5. Type
8. SNMPv3 Setting
4. Delete TS (per Slot and Port) 6. Destination Start TS
5. Delete TS (Number of TS) 7. Save Configuration
6. Split
Control Port
1. Serial Port Delete TS (per Slot and Port)
2. ETH
1. Slot
2. Port
Date & Time
2. Set Date Format Delete TS (Number of TS)
3. Set Date
4. Set Time 1. Start TS
2. Number of TS
Reset Device
1. CL-A (On-line CL) TS3
2. IO-1
3. IO-2
Split 1. Bit 1 ... (01:IN03)
2. Bit 2 ... (01:IN03)
4. IO-3 1. TS3 3. Bit 3 ... (------)
5. IO-4 2. TS15 4. Bit 4 ... (------)
6. IO-5 .. 5. Bit 5 ... (------)
7. IO-6
8. IO-7 See
. 6. Bit 6 ... (------)
7. Bit 7 ... (------)
9. IO-8 Sheet 6 8. Bit 8 ... (------)
10. IO-9
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling CL-A
4. Rx Busy
5. Rx Idle 1. Link 1
6. Profile Name 2. Link 2
Link 1
1. Alarm Attributes
2. Alarm Report TU1 TU2 TU3 TU1 TU2 TU3 TU1 TU2 TU3
3. Alarm Priority TUG2-1 None None None None None None None None None
4. Init Alarm Priority TUG2-2 None None None None None None None None None
5. Init Alarm Report TUG2-3 None None None None None None None None None
6. Alarm Window TUG2-4 None None None None None None None None None
7. Trap Masking TUG2-5 None None None None None None None None None
Fault Propagation
2. Interfaces
Figure 4-40. Typical Configuration>System Submenu Structure – SDH Only (Sheet 2 of 6)

System
1. Card Type
Link 1
2. Clock Source IO I/O-1
3. TS Assignment
1. I/O-1 1. Link 1 2. Manual
4. Mapping
2. I/O-2 2. Link 2 3. Connect Time Slots
5. APS
4. Delete TS (Per Slot and Port)
6. Management
..
3. I/O-3
..
3. Link 3
7. Control Port
8. Date & Time
. . 6. Split
10. Reset Device Sheet 1 or
11. Signaling Profile CL
PDH 1
12. Alarms Configuration 1. PDH 1 (Up)> 12. PDH 12 (Up)> 23. PDH 23 (Up)> 34. PDH 34 (Up)>
13. Fault Propagation 2. PDH 2 (Up)> 13. PDH 13 (Up)> 24. PDH 24 (Up)> 35. PDH 35 (Up)> 1. Display Time Slots
3. PDH 3 (Up)> 14. PDH 14 (Up)> 25. PDH 25 (Up)> 36. PDH 36 (Up)> 2. Manual
4. PDH 4 (Up)> 15. PDH 15 (Up)> 26. PDH 26 (Up)> 37. PDH 37 (Up)> 3. Connect Time Slots
Clock Source 5. PDH 5 (Up)> 16. PDH 16 (Up)> 27. PDH 27 (Up)> 38. PDH 38 (Up)>
1. Source . .. ... ... ... 4. Delete TS (Per Slot and Port)
2. Master Port
Rx Clock only
. . . . . . . . 5. Delete TS (Number of TS)
6. Split
3. Fallback Port . . . .
(See below)
TS Assignment
1. IO
2. CL Display Time Slots
Ts# 1 2 3 4 5 6 7 8
Mapping Ts# 9 10 11 12 13 14 15 16
1. CL-A ----- ----- ----- -----
.. ----- ----- ----- -----
2. CL-B
.
APS Manual
1. APS Group Id Ts# Slot Port Ts Type
TS 01 IO-2 (M8T1) Link 1 1 DATA
2. Protection
3. Revertive TS 02 IO-2 (M8T1) Link 1 2 DATA
4. Working Port | TS 03 IO-2 (M8T1) Link 1 4 DATA
5. Protection Port v TS 04 IO-2 (M8T1)
.. BND 1 -- DATA
6. WTR Time (Sec)
7. Flip Upon SD See Sheet 4 .
or Sheet 5
Connect Time Slots
Management PDH 1 1. Start TS
2. Slot
1. Device Info 1. Display Time Slots 3. Port
2. Host IP 2. Manual 4. Number of TS
3. Manager List 3. Connect Time Slots 5. Type
4. Mng Access 4. Delete TS (per Slot and Port) 6. Destination Start TS
5. Flow 5. Delete TS (Number of TS) 7. Save Configuration
6. SNMP Engine ID 6. Split
7. SNMPv3
8. SNMPv3 Setting
Delete TS (per Slot and Port)
1. Slot
Control Port 2. Port
1. Serial Port 3. Save Configuration
2. ETH
Delete TS (Number of TS)

Date & Time 1. Start TS
1. Display Date & Time 2. Number of TS
2. Set Date Format
3. Set Date
4. Set Time TS3
Split 1. Bit 1 ... (01:IN03)
2. Bit 2 ... (01:IN03)
Reset Device 1. TS3 3. Bit 3 ... (------)
2. TS15 4. Bit 4 ... (------)
1. CL-A (On-line CL) .. 5. Bit 5 ... (------)
2. IO-1
3. IO-2
. 6. Bit 6 ... (------)
4. IO-3 7. Bit 7 ... (------)
5. IO-4 8. Bit 8 ... (------)
7. IO-6 See
8. IO-7 Sheet 6
9. IO-8
10. IO-9
11. IO-10 CL-A
1. Link 1
Signaling Profile 2. Link 2
1. Profile Number
2. Rx Signaling Link 1
3. Tx Signaling
4. Rx Busy
5. Rx Idle
STS1-1 STS1-2 STS1-3
6. Profile Name TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4
Alarms Configuration TUG2-3 None None None None None None None None None None None None
1. Alarm Attributes TUG2-4 None None None None None None None None None None None None
2. Alarm Report TUG2-5 None None None None None None None None None None None None
3. Alarm Priority
5. Init Alarm Report TUG2-7 None None None None None None None None None None None None
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces
Figure 4-41. Typical Configuration>System Submenu Structure – SONET Only (Sheet 3 of 6)


System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time
9. Factory Default
See
11. Signaling Profile APS Group ID
13. Fault Propagation 1. A1-A2
2. B1-B2
3. A1-B1
Clock Source 4. A2-B2
1. Source
2. Master Port
Rx Clock only
3. Fallback Port
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping Users
Authentication Protocol
1. CL-A 1. Security Name
2. Authentication Protocol 1. usmNoAuthProtocol
2. CL-B 2. usmHMACMD5AuthProtocol
3. Privacy Protocol
4. Authentication Password 3. usmHMACSHAAuthProtocol
5. Privacy Password
APS
1. APS Group Id With Authentication
2. Protection
3. Revertive Privacy Protocol
4. Working Port 1 usmNoPrivProtocol
5. Protection Port 2. usmDESPrivProtocol
6. WTR Time (Sec)
7. Flip Upon SD
Only with Authentication

Management
1. Device Info See Only with Privacy
2. Host IP
3. Manager List
Sheet 4
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3
Targets Params Message Processing
8. SNMPv3 Setting
Targets & Notify Model
1. Name
1. Target Params 2. Message Processing Model 1. SNMPv1
SNMPv3 Setting 2. Target Address 3. Security Model 2. SNMPv2c
Engine Boots 3. Notify 4. Security Name 3. SNMPv2u
Engine Time 4. Trap 5. Security Level 4. SNMPv3
SNMP Message Size
Control Port 1. Users
2. Targets & Notify Security Model
1. Serial Port 3. SNMPv1/v3 Mapping
2. ETH 4. SNMPv3 Factory Defaults 1. Any
5. Summary User Table Target Address 2. SNMPv1
6. Summary Target Table 3. SNMPv2c
1. Name
4. USM
Date & Time 2. IP Address
5. Not defined
1. Display Date & Time 3. Params Name
2. Set Date Format 4. Tag List
3. Set Date
4. Set Time Security Level
1. noAuthNoPriv
Notify 2. authNoPriv
Reset Device 3. authPriv
2. IO-1
3. IO-2 See
Trap
4. IO-3 Sheet 6
5. IO-4
6. IO-5
7. IO-6
8. IO-7 SNMPv1/v3 Mapping
9. IO-8
10. IO-9 1. Community Index
11. IO-10 2. Community Name
3. Security Name
4. Transport Tag
Signaling Profile
1. Profile Number
2. Rx Signaling
3. Tx Signaling Summary User Table
4. Rx Busy
5. Rx Idle User Security Model Security Level
6. Profile Name
1. Alarm Attributes Summary Target Table
2. Alarm Report Address MPModel SecModel SecName SecLevel
3. Alarm Priority
6. Alarm Window
7. Trap Masking
Fault Propagation
2. Interfaces

System
1. Card Type
2. Clock Source
3. TS Assignment
4. Mapping
5. APS
6. Management
7. Control Port
8. Date & Time

Clock Source
1. Source
2. Master Port
Rx Clock only
3. Fallback Port
TS Assignment
1. IO
2. CL
See Sheet 2
or Sheet 3
Mapping
1. CL-A
2. CL-B
APS
1. APS Group Id
2. Protection
3. Revertive
4. Working Port
5. Protection Port
6. WTR Time (Sec)
or Sheet 5
Management
1. Device Info
2. Host IP
3. Manager List
4. Mng Access
5. Flow
6. SNMP Engine ID
7. SNMPv3 - Enabled Baud Rate
8. SNMPv3 Setting
For Administrator
Serial Port
Control Port Change Password
1. Serial Port 1. Baud Rate
2. Change Password 1. Change User Details Change User Details
2. ETH
3. Security Timeout 2. Show all Users
Date & Time Show all Users

1. Display Date & Time Security Timeout
2. Set Date Format
3. Set Date
4. Set Time
ETH
CL-A
Routing Protocol
Reset Device 1. CL-A
2. CL-B 1. Admin Status
2. Routing Protocol 1. None
2. IO-1
3. Proprietary RIP
3. IO-2
4. IO-3
5. IO-4 Set Date Format
6. IO-5
7. IO-6 1. DD-MM-YYYY
8. IO-7 2. MM-DD-YYYY
9. IO-8 3. YYYY-DD-MM
10. IO-9 4. YYYY-MM-DD
11. IO-10
Signaling Profile
1. Profile Number Profile Number
2. Rx Signaling
3. Tx Signaling
4. Rx Busy Rx Signaling
5. Rx Idle
6. Profile Name Tx Signaling
1. Alarm Attributes
2. Alarm Report
3. Alarm Priority
5. Init Alarm Report Interfaces
6. Alarm Window
7. Trap Masking 1. Slot A
2. Port A
Interfaces 3. Slot B
Add
Fault Propagation 4. Port B
Slot A Port A Slot B Port B Mode 5. Mode
1. Fault Propagation IO-1 ETH 1 IO-5 ETH 2 BiDirectional (A<->B)
2. Interfaces

Programming Modules
Use the following procedure to program modules in the Megaplex-4100 chassis.
You can program modules even if they are not installed in the chassis.
Note When only one CL module is installed in the chassis, it must always be installed in
slot CL-A.
Moreover, if CL module B is programmed, CL module A must also be programmed
in the chassis.
To navigate to the required screen, use Configuration>System>Card Type.

A typical Card Type screen is shown in Figure 4-45.
MP-4100
Configuration>System>Card Type
Slot: PS-A PS-B CL-A CL-B IO-1 IO-2 IO-3

Card: PS PS CL1/155 CL1/155 M8E1 M8E1 M8SL
Slot: IO-4 IO-5 IO-6 IO-7 IO-8 IO-9 IO-10

Card: M8SL HSU-12 HSU-12 HSU-12 HSU-12 VC-16/FXS VC-16/E&M
1. ---------
2. PS
>

-----------------------------------------------------------------------------
Figure 4-45. Typical Card Type Screens
³ To program modules in the Megaplex-4100 chassis:

1. Move the cursor to the desired slot.
2. The selections supported for the selected slot are automatically displayed
under the slots table. Type the item number corresponding to the desired
selection and then press <Enter>.
Note It is not allowed to program different types of CL modules in the chassis, even if
only one CL module is currently installed.
3. When done, type % to update the current Megaplex-4100 database. You will
get warnings whenever you program modules not yet installed in the chassis:
at this stage, the warnings can be ignored.

Configuring System Clock Sources

Use the following procedure to configure the system (nodal) clock timing
references signals (sources) for the Megaplex-4100 timing subsystem.
Appropriate configuration permits hierarchical dissemination of timing throughout
the communication systems, and use of reliable timing sources even in case of
transmission faults or equipment malfunctions.
In addition to the system clock sources, for Megaplex-4100 with CL.1/155 and
CL.1/155GbE modules it is also necessary to configure the timing reference for
the SDH/SONET subsystem (see Configuring SDH/SONET Network Ports starting
on page 4-70).
Review the Megaplex-4100 Timing Subsystem section in Chapter 1 for a
description of the timing 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. For flexibility, you can select master timing sources
and fallback timing sources: a fallback source is automatically selected when none
of the preconfigured master sources is capable of providing a good timing
reference.
Only ports that are fully configured and with Admin Status=UP can be configured.
The Megaplex-4100 timing subsystem can use the following types of reference
sources:
• Internal Megaplex-4100 oscillator.
• Clock signal derived from the receive clock of a specified user port (Rx
timing mode).
• S-subsystem clock signal, provided by the timing subsystem of the
SDH/SONET subsystems located CL.1/155 and CL.1/155GbE modules.
• Station clock, a special case of Rx timing, which uses an external clock
signal supplied to the CL module CLOCK connector.
Table 4-13 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 be able of providing a timing
reference signal.
Table 4-13. Clock Reference Sources
Internal Not applicable Not applicable Not applicable
Station (external) CL Station clock Not applicable

M8E1, M8T1 External T1 or E1 ports Not applicable
M8SL External SHDSL ports STU-R mode
MPW-1 Pseudowire ID Not for HDLCoPSN

pseudowires
OP-108C/OP-106C Internal DS1 ports Not applicable
RX Clock from HS-6N, HS-12N External ports DTE timing

Local User Port
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
RX Clock from CL.1/155, Internal T1 or E1 PDH Not applicable

Remote User Port CL.1/155GbE ports
Line (STM-1/OC-3) Signal from CL.1/155, Link port Not applicable

SDH/SONET Subsystem CL.1/155GbE
To navigate to the required screen, use Configuration>System>Clock Source.

A typical Clock Source screen with the default source, Internal, is shown in
Figure 4-46.
MP-4100
Configuration>System>Clock Source
1. Source > (Internal)
>

-----------------------------------------------------------------------------
Figure 4-46. Typical Clock Source Screen
³ To select the timing reference mode (source type):

1. To start the nodal timing configuration, select Source to display the source
type selection screen (see Figure 4-47).

MP-4100
Configuration>System>Clock Source>Source (Internal)
1. Internal
2. Rx Clock
3. S Subsystem
>

-----------------------------------------------------------------------------
Figure 4-47. Selection Screen for Clock Source Type

2. The available selections are as follows:
Internal Timing locked to the Megaplex-4100 internal oscillator.
Rx Clock Timing locked to the receive clock signal of a user-selectable

interface.
S Subsystem Timing locked to the clock signal provided by the SDH/SONET

subsystem (refer to the Card Configuration section starting
on page 4-71 for details).
Do not select S Subsystem when the system SDH/SONET TX
Clock (see Configuring SDH/SONET Network Ports starting on
page 4-70) is SYSTEM, because this will result in unstable
timing.
Select the desired type and then press <Enter>.

3. After making your selection, the source selection screen closes and the new
source appears on the Clock Source screen.
³ To select RX timing sources:

1. If you selected Rx Clock, the Clock Source screen changes to enable selecting
master and fallback sources. A typical screen is shown in Figure 4-48.
The list includes only slots in which modules with ports capable of providing a
timing reference are installed and/or programmed.

MP-4100
1. Source > (Rx Clock)

2. Master Port []>
3. Fallback Port []>
>

-----------------------------------------------------------------------------
Figure 4-48. Typical Selection Screen for RX Clock Mode

2. Select Master Port to start the selection of the master timing sources. For each
source, you must specify a slot and a port. A typical slot selection screen is
shown in Figure 4-49 and a typical port selection screen – in Figure 4-50.
When the list extends on several pages, use the arrow keys or
CTRL+U/CTRL+D to scroll among the pages (for navigation help, use the
?-help item).
The screen includes a table with 3 columns:
Entry Num The index number, 1 to 10, which determines the relative
priority (1 is the highest priority).
Only the first 7 entries appear on the first page: scroll down to
display the other entries.
Slot The slot on which the source port is located. The slot is selected
on a list displayed under the table when the selection block is
moved to the Slot column.
Port The identifier of the desired port within the module installed in
the selected slot. The port is selected on a list displayed under
the table, when the selection block is moved to the Port
column. The list shows only the ports that can be used as
reference source on the module installed, or programmed, in
the selected slot.
3. To define a master source, move the cursor to the desired number, and select
the prescribed slot and port. You can skip priorities, that is, select NONE
wherever desired. You can also select NONE to delete a configured source
without changing the relative priorities of the remaining ports.
4. When done, press ESC to return to the Clock Source screen.
5. To select a fallback source, select Fallback Port and repeat the same actions.
Make sure to select different sources: you cannot select again a source already
included in the Master Port list.

6. To update the active database, and thus activate the new user definitions,
type % and then confirm the action.
MP-4100
Configuration>System>Clock Source>Master Port
Entry Num Slot Port

1 CL-A(CL1/155GbE) Clock
2 CL-B(CL1/155GbE) PDH 1
| 3 IO-1 (M8E1) Link 5
v 4 None -
5 None -
6 None -
7 None -
1. CL-A(CL1/155GbE) 4. IO-2 (M8E1) 7. None

2. CL-B(CL1/155GbE) 5. IO-3 (M8T1)
3. IO-1 (M8E1) 6. IO-5 (M8SL)
>

-----------------------------------------------------------------------------
Figure 4-49. Typical Master Port Screen – Selection of Source Slot

MP-4100
Entry Num Slot Port

1 CL-A(CL1/155GbE) Clock
2 CL-B(CL1/155GbE) PDH 1
| 3 IO-1 (M8E1) Link 5
v 4 None -
5 None -
6 None -
7 None -
1. Link 1 4. Link 4 7. Link 7

2. Link 2 5. Link 5 8. Link 8
3. Link 3 6. Link 6
>

-----------------------------------------------------------------------------
Figure 4-50. Typical Master Port Screen – Selection of Source Port
Configuring Station Clock Parameters

Use the following procedure to configure the physical layer parameters of the
station clock port located on a selected CL module.

For Megaplex-4100 equipped with two CL modules, each station clock port can be
separately configured.
To navigate to the required screen, use Configuration>Physical Layer>CL>CL-A or
CL-B>Station Clock.
Figure 4-51 shows a typical Station Clock screen. The station clock port
configuration parameters are explained in Table 4-14.
MP-4100
Configuration>Physical Layer>CL>CL-A>Station Clock
2. Transmit Timing Source > (System)
3. Clock Rate > (2048 KBPS)
5. Line Code > (HDB3)
6. Rx Gain Limit (Short Haul)
7. SSM (Enable)
8. Rx Source (Sa4)
>

-----------------------------------------------------------------------------
Figure 4-51. Typical Configuration>Physical Layer>CL>Station Clock Screen (2048 KBPS Clock Rate
³ To define the station clock port parameters:

Select the number of the desired parameter, and then press <Enter> to display
the appropriate parameter selection screen, or toggle the current selection.
Table 4-14. Station Clock Parameters
Admin Status Used to enable/disable the station DOWN – The station clock interface on the
clock interface corresponding CL module is disabled. This state should
be selected as long as the port configuration has not
yet been completed, or to stop using this port.
UP – The station clock interface on the corresponding
CL module is enabled.
Default: DOWN

Transmit Timing Selects the source of the clock SYSTEM – the output (transmit) clock is derived from
Source output signal provided in the the Megaplex-4100 nodal timing. In this case, the
station clock connector, for nominal frequency of the output clock is always
connection to other equipment 2048 kbps, irrespective of the Clock Rate selection.
STATION RCLK – the external clock signal applied to the
station clock receive input is returned through the
transmit output.
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.
Default: SYSTEM
Clock Rate Selects the rate and type of signal 2048 KBPS – 2.048 Mbps signal per ITU-T Rec. G.703
accepted and transmitted via the Para. 6.
station clock port 2048 KHZ – 2.048 MHz signal per ITU-T Rec. G.703
Para. 10.
1544 KBPS – 1.544 Mbps signal per ITU-T Rec. G.703
Para. 2. This option is not available when Transmit
Timing Source is SYSTEM.
Default: 2048 KBPS
Interface Type Selects the clock signal interface BALANCE – balanced interface (nominal impedance of
type 100 Ω for 1544 KBPS, and 120 Ω for 2048 KBPS and
2048 kHz).
UNBALANCE – 75 Ω unbalanced (coaxial) interface. This
selection is available only for 2048 KBPS and 2048 kHz.
Default: BALANCE
Line Code Selects the line code The available selections depend on Clock Rate:
• When Clock Rate is 2048 KBPS or 2048 kHz, the
only selection is HDB3.
• When Clock Rate is 1544 KBPS:
• AMI – alternate mark inversion coding
• B8ZS – Binary-8 zero suppression coding
Default: HDB3
Rx Gain Limit Determines the maximum SHORT HAUL – Maximum allowable attenuation of
attenuation of the receive signal 10 dB, relative to the nominal transmit level (similar to
that can be compensated for by DSU capabilities).
the station port receive path LONG HAUL – Maximum allowable attenuation of 34 dB,
relative to the nominal transmit level (similar to DSU
capabilities).
Default: SHORT HAUL

SSM Enables/disables the use of SSM DISABLE – SSM messages received through this station
messages received through this clock interface are ignored.
station clock interface RX – SSM messages received through this station clock
interface are taken into account when the SDH/SONET
subsystem uses automatic SSM-based clock source
selection (see Tx Clock Based on SSM in Table 4-17).
Default: DISABLE
Rx Source Specifies the national bit (located Sa4, Sa5, Sa6, Sa7, Sa8 – the national bit carrying the
in timeslot 0 of E1 streams) from SSM.
which the SSM message is read. Default: Sa4
This parameter is displayed only
when Clock Rate is 2048 KBPS and
SSM is Rx Source
Preparing 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.
To navigate to the required screen, use Configuration>System> Signaling Profile.
A typical signaling profile configuration screen is shown in Figure 4-52.
MP-4100
Configuration>System>Signaling Profile
1. Profile Number> (1)

2. Rx Signaling >
3. Tx Signaling >
4. Rx Busy[0 - f]... (0F)
5. Rx Idle[0 - f]... (00)
6. Profile Name ... ()
>

-----------------------------------------------------------------------------
Figure 4-52. Typical Signaling Profile Configuration Screen

You can specify different transmission 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).
In addition to the translation of individual bits, the receive path section can
also be used to define the signaling bit patterns that indicate the busy and
idle states.
• Transmit direction: defines the translation of the internal signaling bits to
the signaling bits transmitted through the external port.
³ To modify a signaling profile:

1. Select Profile Number, type the desired number, 1 to 5, and then press
<Enter>.
2. To change the translation rule for the receive or transmit direction, select Rx
Signaling or Tx Signaling, respectively, to display the bit selection screen.
A typical screen is shown in Figure 4-53. The screen lists the four signaling
bits, A to D, together with their current translations.
MP-4100
Configuration>System>Signaling Profile>Rx Signaling
1. A> ( A)
2. B> ( B)
3. C> ( C)
4. D> ( D)
>

-----------------------------------------------------------------------------
Figure 4-53. Typical Signaling Bit Selection Screen

To change the translation rule of a bit, select it and then press <Enter>. On
this screen, you can select for each internal signaling bit the method used to
determine its value. The available selections are as follows:
A, B, C, D Bit value copied from the corresponding incoming bit

(no translations).
~A, ~B, ~C, ~D Inverted bit value, related to the corresponding incoming
bit.
0 Bit value is always 0.
1 Bit value is always 1.
The defaults are no translation.

3. To change the incoming pattern to be interpreted internally as the busy state,
select Rx Busy, and then type the appropriate value. The pattern is specified by a
hexadecimal digit (0 to 9, A to F), which when converted to binary format yields
the ABCD sequence.

Example: if the busy state is indicated by the incoming sequence 1000, select 8.
Default: 0
4. To change the incoming signaling bit pattern to be interpreted internally as the
idle state, select Rx Busy, and then type the appropriate value.
The pattern is specified by a hexadecimal digit (0 to 9, A to F), which when
converted to binary format yields the ABCD sequence.
Default: 0
5. You can also assign a name to the profile: select Profile Name, and then type
the desired name (up to 12 alphanumerical characteristics).
Configuring Physical Layer Parameters

³ To configure Megaplex-4100 physical ports:
1. For each CL module: configure the station clock interface.
2. For each CL module with SDH/SONET subsystem (CL.1/155 and CL.1/155GbE):
• Configure the general module parameters and system timing sources
• Configure the physical link parameters
• When inband management is used: configure DCC parameters.
3. For each CL module with Ethernet traffic subsystem (CL.1/GbE and
CL.1/155GbE):
• Configure the GbE physical ports parameters
• Configure the GbE redundancy.
4. Configure the required I/O physical ports in accordance with the Installation
and Operation Manual of each module programmed in Megaplex-4100.
For your convenience, the structure of the Physical Layer submenu for SDH and
SONET links is shown in Figure 4-54 and Figure 4-55, respectively.

Physical Layer I/O E1

I/O-1
1. I/O 1. I/O-1
2. CL 2. I/O-2 1. E1 ..
1. Link 1
..
3. I/O-3 2. Ethernet ..
.. 8. Link 8
. 9. All Links
Ethernet Transmit Timing

Source
1. ETH1
2. ETH2 1. System
3. ETH3 2. Station RCLK
4. All Ports 3. Station RCLK after JA
Clock Rate
CL Station Clock
1. 2048 KBPS
1. Admin Status 2. 1544 KBPS Not for
1. CL-A
2. Transmit Timing Source 2. 2048 KHZ SYSTEM Source
2. CL-B
3. Clock Rate
4. Interface Type Balance
5. Line Code Unbalance
6. Rx Gain Limit Short Haul
7. SSM Disable Long Haul
8. Rx Source Rx
Only for SSM = Rx Line Code

Sa4
1. AMI 1544 KBPS only
CL-A Sa5
2. HDB3 2048 KBPS, 2048 KHZ
Sa6
3. B8ZS
1. Station Clock Sa7
2. Ethernet Sa8
3. SDH/SONET
GbE
Ethernet
1. Admin Status
1. GbE 1 2. Auto Negotiation
2. GbE 2 3. Speed & Duplex
3. All Ports 4. Flow Control
5. User Name
6. Redundancy
SDH/SONET Card Configuration

1. Card Configuration 1. Frame Structure – STM-1 Common PDH
2. Link 1 2. Tx Clock Based on SSM – YES LVC Parameters
3. Link 2 3. Common PDH LVC Parameters
4. All Links 1. RDI on Signal Label
Card Configuration
1. Frame Structure – STM-1 In Band Management
2. Tx Clock Based on SSM – NO
3. SDH Tx Clock 1. Off
4. Master Port 2. PPP Over HDLC
5. Fallback Port
RX CLOCK only
3. HDLC
6. Common PDH LVC Parameters
Link 1 Routing Protocol
1. Admin Status 1. None

3. RDI on Fail 3. Proprietary RIP
DCC Configuration
4. EED Threshold
5. SD Threshold 1. In Band Management
6. DCC Configuration 2. Routing Protocol
3. Management DCC Management DCC
4. Deviation Type
1. D1-D3
Standard 2. D4-D12
Type 1
Figure 4-54. Typical Configuration>Physical Layer Submenu Structure (SDH)

Figure 4-55. Typical Configuration>Physical Layer Submenu Structure (SONET)

The configuration of the physical layer parameters for the modules programmed
in the various Megaplex-4100 slots is started by selecting the class of ports to be
configured on the Physical Layer menu.
A typical Physical Layer type selection screen is shown in Figure 4-56. This screen
includes two options:
IO For configuring the physical layer parameters of modules installed in

I/O slots. Configuration instructions for these modules can be found
in the Installation and Operation Manual of each module.
CL For configuring the physical layer of the ports located on the CL

modules.
³ To select the class of physical ports to be configured:

Select the desired type and then press <Enter>.
MP-4100
Configuration>Physical Layer
1. IO >
2. CL >
>

-----------------------------------------------------------------------------
Figure 4-56. Typical Physical Layer Class Selection Screen
Configuring the CL Physical Layer

Use the following procedure to configure the CL Physical Layer parameters.
To navigate to the required screen, use Configuration>Physical Layer>CL.
³ To select the CL configuration task:

1. Select CL on the Physical Layer menu. A typical CL module selection screen is
shown in Figure 4-57. This screen is used to select between the two CL
modules that can be installed in the Megaplex-4100.

MP-4100
Configuration>Physical Layer>CL
1. CL-A>
2. CL-B>
>

-----------------------------------------------------------------------------
Figure 4-57. Configuration>Physical Layer>CL Selection Screen

2. Select the desired CL module and then press <Enter> to display the
configuration task selection screen for the selected CL module.
A typical screen, which shows all the available options, is shown in
Figure 4-58. The displayed options depend on the CL module model.
MP-4100
Configuration>Physical Layer>CL>CL-A
1. Station Clock>
2. Ethernet >
3. SDH/SONET >
>

-----------------------------------------------------------------------------
Figure 4-58. Configuration>Physical Layer>CL Task Selection Screen
Configuring the Physical Layer Parameters of GbE Ports

GbE ports located on the CL.1/GbE and CL.1/155GbE modules, and control the
use of the 1+1 redundancy feature.
CL-B>Ethernet.
³ To configure the physical layer parameters of the GbE ports:

1. Open the Configuration>Physical Layer>CL screen, and then select the desired
CL module to display the CL module task selection screen.
2. On the CL module task selection screen (Figure 4-58), select the Ethernet
configuration option. A typical Ethernet port selection screen is shown in
Figure 4-59.

MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet
1. GbE 1(Up)>
2. GbE 2(Up)>
3. All Ports>
>

-----------------------------------------------------------------------------
Figure 4-59. Typical Ethernet Port Selection Screen

3. Select a specific GbE port to configure its physical layer parameters.
Alternatively, first preconfigure both ports with the same basic parameters
(All Ports option), and then sequentially select each port and change its
parameters as required.
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 1(Up)

2. Auto Negotiation (Disable)
3. Speed & Duplex > (1000 MBPS Full Duplex)
4. Flow Control (Enable)
5. User Name ... ()
>

-----------------------------------------------------------------------------
Figure 4-60. Typical Ethernet Port Configuration Screen (No Redundancy)
Table 4-15 describes the GbE port configuration parameters.

Table 4-15. GbE Port Physical Layer Configuration Parameters
Admin Status Used to enable/disable the flow of DOWN – The flow of traffic is disabled. This
traffic through the selected GbE port state should be selected as long as the
configuration of the corresponding port has not
yet been completed, or when it is necessary to
stop traffic flow through the port.
UP – The flow of traffic is enabled.
Default: DOWN
Auto Negotiation Controls the use of auto-negotiation for ENABLE – Auto-negotiation is enabled. This is
the selected GbE port. the normal operation mode. It is not
Auto-negotiation is used to select recommended to use this option for GbE ports
automatically the mode providing the equipped with SFPs.
highest possible traffic handling DISABLE – Auto-negotiation is disabled. This is
capability the recommended state for the GbE ports
equipped with SFPs.
Default: DISABLE
Max. Capability When Auto Negotiation is ENABLE, The available selections are listed in ascending
Advertised selects the highest traffic handling order of capabilities:
capability to be advertised during the 10Mbps half duplex – Half-duplex operation at
auto-negotiation process. The operating 10 Mbps.
mode selected as a result of
10Mbps full duplex – Full-duplex operation at
auto-negotiation cannot exceed the
10 Mbps.
advertised capability.
100Mbps half duplex – Half-duplex operation at
When Auto Negotiation is DISABLE, this
100 Mbps.
parameter is replaced by Speed &
Duplex. 100Mbps full duplex – Full-duplex operation at
100 Mbps.
Only CL modules with copper GbE ports
support the full range of rate and mode 1000Mbps half duplex – Half-duplex operation at
options. GbE ports equipped with SFPs 1000 Mbps.
support only 1000Mbps full duplex (any 1000Mbps full duplex – Full-duplex operation at
other selection will result in a 1000 Mbps.
Hardware/Software Mismatch alarm) Default: 1000Mbps full duplex
Speed & Duplex When Auto Negotiation is DISABLE, Same selections as for the Max. Capability
selects the data rate and the operating Advertised parameter.
mode of the selected GbE port. For GbE ports equipped with SFPs, the only
When Auto Negotiation is ENABLE, this allowed selection is 1000Mbps full duplex (any
parameter is replaced by Max. Capability other selection will result in a
Advertised Hardware/Software Mismatch alarm).
Default: 1000Mbps full duplex

Flow Control Controls the use of flow control for the ENABLE – Flow control or back pressure is
selected GbE port (when operating in enabled. In this case, when the offered Ethernet
the full duplex mode), or back pressure traffic exceeds the available transmission
(when operating in the half-duplex bandwidth, the port forces the source to reduce
mode) its traffic volume.
DISABLE – Flow control and back pressure are
disabled.
Default: DISABLE
User Name Used to enter a logical name for the Up to 10 alphanumeric characters.
selected GbE port Default: Empty string
Redundancy Controls the use of 1+1 redundancy for NONE – No redundancy.

the selected port 1+1 – 1+1 redundancy is enabled.
Default: NONE
³ To configure GbE port redundancy:
Note When configuring the redundancy parameters, always start from the GbE port
that is to serve as the primary port of the pair.
If you must reconfigure the redundancy partners, it is recommended to first
select Redundancy = NONE for the current primary port, and then reconfigure all
the redundancy parameters.
1. On the Ethernet port selection screen (Figure 4-59), select the GbE port that
will serve as the primary port of the redundancy pair.
2. Select Redundancy, and then select 1+1 to enable redundancy. The screen
changes to display the additional parameters related to redundancy, and a
Primary (Yes) indicator appears at the top of the screen.
3. Configure the primary port parameters in accordance with the information
appearing in Table 4-16. A typical screen with all the redundancy-related
parameters is shown in Figure 4-61.

MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 1(Up)
Primary > (Yes)

2. Auto Negotiation (Enable)
3. Max Capability Advertised > (1000 MBPS Full Duplex)
5. User Name ... ()
6. Redundancy > (1+1)
7. Revertive > (Yes)
8. Wait To Restore[0 - 999] ... (300)
9. Redundancy Slot > (CL-A )
10. Redundancy Port > (GbE 2 )
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-61. Typical Screen for the Primary GbE Port of a Redundancy Pair
4. At this stage, configure the remaining parameters of the other GbE port (the
secondary port of the redundancy pair). A typical screen with all the
redundancy-related parameters for the secondary GbE port is shown in
Figure 4-62.
Note The other port, which is specified in the Redundancy Slot and Redundancy
Channel fields of the primary port, is automatically configured with compatible
parameters, and only the remaining parameters can be configured manually.
MP-4100
Configuration>Physical Layer>CL>CL-A>Ethernet>GbE 2
Admin Status (Up)

Redundancy > (1+1)
Primary > (No)
Revertive > (Yes)
Wait To Restore[0 - 999] ... (300)
Redundancy Slot > (CL-A )
Redundancy Port > (GbE 1 )
4. User Name ... ()
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-62. Typical Screen for the Secondary GbE Port of a Redundancy Pair

Table 4-16. GbE Port Redundancy Configuration Parameters
Revertive Selects the protection mode. NO – Switching is non-revertive, that is, the
This parameter is not displayed when Megaplex-4100 will not flip back to the primary
Redundancy is NONE port after the failed link returns to normal
operation, but only when the currently used link
fails.
YES – Switching is revertive: the Megaplex-4100
will automatically return to the original port
when it returns to normal operation.
Default: NO
Wait to Restore Specifies the time following the last The supported range is 0 to 999 seconds.
redundancy switching (flipping) during Default: 300
which alarms are ignored.
Therefore, the module starts evaluating
the criteria for redundancy switching
(flipping) only after this interval expires.
This ensures that another flipping
cannot occur before the specified
interval expires.
Redundancy is NONE
Redundancy Slot Selects the slot in which the other You can select either the same CL slot, or the
module of a redundancy pair is installed. other CL slot (provided a CL module with GbE
The selection must always be ports is programmed in the other slot).
symmetrical. Default: Same CL slot
Redundancy is NONE
Redundancy Port Selects the other port of a redundancy The available selections depend on the module
pair. selected by means of the Redundancy Slot
The selection must always be parameter:
symmetrical. • If the Redundancy Slot specifies the CL
This parameter is not displayed when module on which the primary port is located,
Redundancy is NONE the only selection is the other GbE port on
the same module.
• If the Redundancy Slot specifies the other CL
module, you can select any desired GbE port,
provided its Admin Status is Up.
Default: – (None)
Configuring SDH/SONET Network Ports

SDH or SONET ports and links located on the CL.1/155 and CL.1/155GbE modules.
Each SDH or SONET port can be separately configured.

This option is available only for Megaplex-4100 with CL.1/155 or CL.1/155GbE

modules.
CL-B>SDH/SONET
Task Selection
Figure 4-63 shows a typical SDH/SONET configuration task selection screen.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET
1. Card Configuration>
2. Link 1 >
3. Link 2 >
4. All Links>
>

-----------------------------------------------------------------------------
Figure 4-63. Configuration>Physical Layer>CL>SDH/SONET Task Selection Screen
³ To select a configuration task:

Select the number of the desired parameter, and then press <Enter> to display
the appropriate task:
Card Configuration Configure the SDH/SONET operating mode.
Link 1 Configure the parameters of link 1 of the selected

CL module.
Link 2 Configure the parameters of link 2 of the selected

CL module.
All Links Configure the same parameters for both links of

the selected CL module.
Even when it is necessary to select different
parameters for each link, you can use the common
configuration as a starting point, and modify the
parameters of each link as required.
Card Configuration
Figure 4-64 shows a typical Card Configuration screen. The parameters actually
displayed on the screen are automatically adjusted after each major selection.
Note After changing the Frame Structure, the CL.1/155 and CL.1/155GbE subsystems
will be automatically reset when the database is updated, and the factory

defaults for the new frame structure are automatically loaded. Therefore, it is not
recommended to perform this configuration change while the Megaplex-4100 is
connected to an operating network, and carries payload traffic.
The user is prompted to confirm the update by a DB values will change to
defaults, CL will restart after DB UPD. Are you sure Y/N message. Type y to
confirm.
³ To define the Card Configuration parameters:

Select the number of the desired parameter and then press <Enter>:
• For the SDH/SONET Tx Clock, Master Port and Fallback Port, Common LVC
Parameters items, you will see separate parameters selection screens for
each link. The relevant parameters are explained in Table 4-17.
• For the Common PDH LVC Parameters item, refer to page 4-74.
• For the other items, the selection is toggled.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Card Configuration
1. Frame Structure (STM-1)

2. Tx Clock Based on SSM (No)
3. SDH/SONET Tx Clock > (Rx Clock)
4. Master Port > (Link 1)
5. Fallback Port > (Link 2)
6. Common PDH LVC Parameters >
>

-----------------------------------------------------------------------------
Figure 4-64. Configuration>Physical Layer>CL-A>SDH/SONET>Card Configuration Screen
Table 4-17. SDH/SONET Card Configuration Parameters
Frame Structure Selects the set of standards defining the STM-1 – Operation in accordance with the
operating mode of the SDH/SONET. SDH standards.
Make sure to select the same value for both OC-3 – Operation in accordance with the
CL modules, although a change in one CL SONET standards.
module automatically changes the frame
Default: STM-1
structure of the other CL module (the last
selection governs)

Tx Clock Based Controls the selection mode of the YES – Automatic selection of the timing
on SSM STM-1/OC-3 transmit clock reference reference, using the SSM received in the S1
byte of the STM-1 or OC-3 overhead. This
option can be selected only when both STM-
1/OC-3 links are connected.
This option should be used only when the
Megaplex-4100 is equipped with two CL
modules.
You can extend the selection to include the
station clock, by enabling the reception of
SSM messages for station clock interfaces as
explained in the Configuring Station Clock
Parameters on page 4-56.
NO – The selection of the timing reference
does not use the SSM.
Default: YES
SDH/SONET Tx Selects the timing reference source of the SYSTEM – The SDH/SONET transmit clock is
Clock SDH/SONET transmit clock. locked to the Megaplex-4100 nodal timing.
This parameter is displayed only when Do not select SYSTEM when the system Clock
Tx Clock Based on SSM is NO Source (see page 4-54) is S-SUBSYSTEM,
because this will result in unstable timing.
INTERNAL – The SDH/SONET transmit clock is
derived from the Megaplex-4100 internal
oscillator.
RX CLOCK – The SDH/SONET transmit clock is
locked to the clock recovered from the signal
received by the STM-1/OC-3 links.
Default: SYSTEM
Master Port Selects the master timing reference source.The available selections are LINK 1 and
This parameter is displayed only when when LINK 2.
the SDH/SONET transmit clock is RX CLOCK Default: LINK 1
Fallback Port Selects the fallback timing reference source. The available selections are LINK 1 and
This parameter is displayed only when when LINK 2. Always select the link not selected as
the SDH/SONET transmit clock is RX CLOCK master port.
Default: LINK 2
Note
When an APS group is configured on the links specified as master and fallback
source, make sure to configure the corresponding redundancy partners with the
same clock priority, for example, if link 1 is a master clock source, then its partner
must also be included in the master clock lists.

Configuring Common PDH LVC Parameters

Figure 4-65 shows a typical Common PDH LVC Parameters screen. The parameters
are explained in Table 4-18.
MP-4100
...Ports>CL>CL-A>SDH/SONET>Card Configuration>Common PDH LVC Parameters
1. RDI on signal label (Enable)

2. RDI on path trace (Enable)
>

-----------------------------------------------------------------------------
Figure 4-65. Card Configuration – Common LVC Parameters Screens
Table 4-18. Card Configuration – Common PDH LVC Parameters
RDI on Signal Controls the sending of RDI indications by the ENABLE – RDI is sent when a signal label
Label port, in case the received signal label (OC-3 mismatch is detected.
overhead byte C2) is different from the DISABLE – RDI is not sent when signal label
expected signal label. mismatch is detected. Nevertheless, AIS and
Make sure to configure the same value for RDI are still sent in case of LOP (loss of
links configured as redundancy partners in an pointer) or unequipped signal label
APS group condition.
Default: DISABLE
RDI on Path Controls the sending of RDI indications by the ENABLE – RDI is sent in case a signal label
Trace port, in case the received path trace label mismatch is detected.
(carried in OC-3 overhead byte J1) is different
DISABLE – RDI is not sent when a signal
from the expected path trace label. label mismatch is detected. Nevertheless,
Make sure to configure the same value for RDI is still sent in case a LOP (loss of
links configured as redundancy partners in an pointer) or unequipped signal label
APS group condition is detected.
Default: DISABLE
Configuring SDH/SONET Link Parameters

Figure 4-66 shows a typical Link 1 screen (the same parameters are also included
on the Link 2 screen). The parameters that can be configured are explained in
Table 4-19.

MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1

2. User Name ... ()
3. RDI on Fail (Enable)
4. EED Threshold > (1E-3)
5. SD Threshold > (1E-6)
6. DCC Configuration >
>

-----------------------------------------------------------------------------
Figure 4-66. Typical SDH/SONET Link Screen
Table 4-19. SDH/SONET Link Parameters
Admin Status Used to enable/disable the DOWN – The link interface on the
corresponding link interface corresponding CL module is disabled. This
state should be selected as long as the port
configuration has not yet been completed, or
to stop using this port.
UP – The link interface on the corresponding
CL module is enabled.
Default: UP
User Name Assign a logic name to the link Alphanumeric string of up to 10 characters.
connected to this port Default: Empty string
RDI on Fail Controls the sending of RDI (remote ENABLE – RDI sending is enabled.
defect indication) in case of failure DISABLE – RDI sending is disabled.
Default: ENABLE
EED Threshold Selects the BER value, which if exceeded The available selections are 3 (BER threshold of
results in the generation of the error 10-3), 4 (10-4) or 5 (10-5).
rate degradation alarm for the port Default: 3 (BER of 10-3)
SD Threshold Selects the BER value, which if exceeded The available selections are 6 (BER threshold of
results in the generation of the 10-6), 7 (10-7), 8 (10-8) or 9 (10-9).
signal-degraded alarm for the port Default: 6 (BER of 10-6)
Configuring DCC Parameters

A typical DCC Configuration screen is shown in Figure 4-67. This screen is used to
configure the parameters needed to use the DCC for carrying inband
management traffic.

Note The DCC can be used to carry management traffic only when it is passed
transparently by the SDH/SONET equipment providing the links between the
Megaplex-4100 units. Contact RAD Technical Support Department for additional
information on this issue.
A typical screen is shown in Figure 4-67. The parameters that can be configured
are explained in Table 4-20.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration
1. In Band Management> (PPP Over HDLC)

2. Routing Protocol > (RIP 2)
3. Management DCC > (D1-D3)
4. Deviation Type (Standard)
>

-----------------------------------------------------------------------------
Figure 4-67. Typical DCC Configuration Screen
Note When you select In Band Management as OFF, no additional parameters are
displayed.
Table 4-20. DCC Configuration Parameters
In Band Selects the encapsulation protocol OFF – No encapsulation protocol selected; inband
Management used for inband management traffic management is not possible.
carried over the DCC PPP OVER HDLC – PPP over HDLC encapsulation.
This protocol is compatible with some RAD
equipment, and equipment from other vendors.
HDLC – HDLC encapsulation. This protocol is
compatible with all the RAD equipment.
Default: OFF

Routing Protocol Selects the routing protocol for NONE – Dynamic routing of management traffic is
management traffic carried over the not supported. In this case, static routing is used,
DCC and you must specify the information needed for
routing the management traffic.
PROPRIETARY RIP – The management traffic is
routed using the RAD RIP proprietary routing
protocol.
RIP 2 – The management traffic is routed using
the RIP2 protocol.
Default: NONE
Management DCC Selects the DCC bytes used to carry D1 – D3 – The management traffic is carried by
inband management traffic the regenerator section DCC bytes (D1, D2, D3).
The available bandwidth is therefore 192 kbps.
D4 – D12 – The management traffic is carried by
the multiplex section DCC bytes (D4 to D12). The
available bandwidth is therefore 576 kbps.
Default: D1 – D3
Deviation Type Selects the PPP over HDLC flavor STANDARD – PPP over HDLC in accordance with
supported by the Megaplex-4100. RFC1661 and RFC1662.
This field, which affects the TYPE 1 – PPP over HDLC based on RFC1661 and
protection loader format, is displayed RFC1662, but LCP (Link Control Protocol) packets
only when In Band Management is do not include address and control fields in their
HDLC or PPP OVER HDLC overhead.
Default: STANDARD
Configuring All Links

Figure 4-66 shows a typical All Links screen, which is used to configure the
SDH/SONET links of both CL modules with similar parameters. The parameters
that can be configured are explained in Table 4-19 and Table 4-20.
MP-4100
Configuration>Physical Layer>CL>CL-A>SDH/SONET>All Links

2. User Name ... ()
>

-----------------------------------------------------------------------------
Figure 4-68. Typical SDH/SONET All Links Screen

Configuring the Logical Layer

³ To configure Megaplex-4100 Logical Layer:
1. For Megaplex-4100 with CL.1/155 and CL.1/155GbE modules: configure the CL
low-order (PDH) and high-order (HVC) virtual ports. Refer to Configuring Logical
Layer on SDH/SONET Links for instructions.
2. Configure the required I/O virtual ports, in accordance with the Installation and
Operation Manual of the corresponding module.
3. Configure virtual ports for Ethernet services (relevant only for Megaplex-4100
with CL.1/GbE and CL.1/155GbE modules). Configuring a Megaplex-4100 for
providing Ethernet services is described in Configuring Ethernet Services below.
The virtual ports configuration activities are started from the Configuration>
Logical Layer submenu.
Figure 4-69 to Figure 4-72 show the structure of the Logical Layer submenu for
SDH and SONET links, respectively, and include typical virtual ports selection
screens. The options appearing on the selection screens depend on the modules
installed in the chassis.

Logical Layer
IO I/O-1 (HS-U12)
1. IO
2. CL 1. I/O-1 1. IN 1 13. IN 13 25. IN 25
2. I/O-2
3. Bundles
.. 2. IN 2
3. IN 3
14. IN 14
15. IN 15
26. IN 26
27. IN 27
.. I/O-2 (M8SL) 4. IN 4 16. IN 16 28. IN 28
5. IN 5 17. IN 17 29. IN 29
1. E1 1 6. IN 6 18. IN 18 30. IN 30
2. E1 2 7. IN 7 19. IN 19 31. IN 31
3. E1 3 8. IN 8 20. IN 20 32. IN 32
4. E1 4 9. IN 9 21. IN 21 33. IN 33
5. E1 5 10. IN 10 22. IN 22 34. IN 34
6. E1 6 11. IN 11 23. IN 23 35. IN 35
7. E1 7 12. IN 12 24. IN 24 36. IN 36
8. E1 8
9. All Ports
E1 Ports
PDH PDH 1
LVC Configuration
. 2. User Name 1. J2 Rx Path Trace
.
2. VCAT
VCAT
1. CL-A VC Type
2. CL-B
LAPS Encapsulation
1. VC12 Typical
2. VC3
3. VC4 VCG 1
GFP Encapsulation
1. Admin Status
CL-A Typical Encapsulation 2. VC Type
3. LCAS
1. VCG-1
VCG-1 1. GFP 4. Number of VCs
2. VCG-2 2. LAPS 5. Encapsulation
3. VCG-3 1. Admin Status 6. Minimum Number of VCs
4. VCG-4 2. VC Type 7. User Name
3. LCAS LVC Configuration
5. VCG-5
4. Number of VCs
8. Redundancy For VCG.1 to
6. VCG-6 9. LVC Configuration
7. VCG-7 5. Encapsulation 1. J2 Rx Path Trace 10. LAPS Configuration
VCG.8 only
8. VCG-8 6. Minimum Number of VCs 2. J2 Path Trace
8. Virtual Concatenation 4. EED Threshold
9. Redundancy or
5. SD Threshold
Primary
VCG-1 3. LCAS
1. FCS 4. Number of VCs
Primary 2. PTI for Client Data 5. Encapsulation
1. Admin Status 3. UPI for Client Data 6. Minimum Number of VCs
2. VC Type 4. Delta 7. User Name
3. LCAS 5. Core Scrambling 8. Redundancy
4. Number of VCs 6. Payload Scrambling 9. Revertive
6. Minimum Number of VCs
11. Wait to Restore

13. Redundancy Port
HVC 14. LVC Configuration 1. Address
15. GFP Configuration 2. Control
1. CL-A 3. SAPI Value
2. CL-B
See
Sheet 2
Bundles
1. Slot
2. Bundle
Figure 4-69. Typical Configuration>Logical Layer Submenu Structure (SDH) (Sheet 1 of 2)

Logical Layer
1. IO
2. CL
3. Bundles
See
Sheet 1
CL
1. PDH
2. VCAT
3. HVC
HVC CL-A
1. CL-A 1. Port 1 Port 1
2. CL-B 2. Port 2
3. All Ports VC-4
1. RDI on Signal Label
2. RDI on Path Trace
3. J1 Rx Path Trace
4. J1 Path Trace
5. Padding
6. EED Threshold
7. SD Threshold
8. Signal Label
Bundles
1. Slot
2. Bundle
MLPPP Bundle
HDLC Bundle (Unframed E1 Ports Only)
Bundles Bundles
Rate (Kbps) Rate (Kbps)
1. Slot 1. Slot
2. Bundle 2. Bundle
3. Admin Status 3. Admin Status
4. User Name 4. User Name
5. L2 Protocol 5. L2 Protocol
6. Number of TS 6. MLPPP MTU
7. Link OAM 7. Link OAM
8. Link OAM Mode 8. Link OAM Mode
9. Remote Terminal 9. Remote Terminal
10. Source Slot CL 10. Number of Links
11. Source Port I/O 11. Source Slot
12. Source Port
.
.
For CL .
For I/O Modules

Figure 4-70. Typical Configuration>Logical Layer Submenu Structure (SDH) (Sheet 2 of 2)

Logical Layer
IO I/O-1 (HS-U12)
1. IO
2. CL 1. I/O-1 1. IN 1 13. IN 13 25. IN 25
2. I/O-2 2. IN 2 14. IN 14 26. IN 26
3. Bundles
.. 3. IN 3 15. IN 15 27. IN 27
.. I/O-2 (M8SL) 4. IN 4 16. IN 16 28. IN 28
5. IN 5 17. IN 17 29. IN 29
1. E1 1 6. IN 6 18. IN 18 30. IN 30
2. E1 2 7. IN 7 19. IN 19 31. IN 31
3. E1 3 8. IN 8 20. IN 20 32. IN 32
4. E1 4 9. IN 9 21. IN 21 33. IN 33
5. E1 5 10. IN 10 22. IN 22 34. IN 34
6. E1 6 11. IN 11 23. IN 23 35. IN 35
7. E1 7 12. IN 12 24. IN 24 36. IN 36
8. E1 8
9. All Ports
T1 Ports
PDH PDH 1
LVC Configuration
.. 2. User Name 1. J2 Rx Path Trace
2. VCAT
VCAT
1. CL-A
2. CL-B VC Type LAPS Encapsulation
Typical
1. VT-1.5
2. STS-1/SPE
VCG 1
GFP Encapsulation
CL-A Typical Encapsulation 1. Admin Status
2. VC Type
1. VCG-1
VCG-1 1. GFP
3. LCAS
4. Number of VTs
2. VCG-2 2. LAPS
1. Admin Status 5. Encapsulation
3. VCG-3
2. VC Type 6. Minimum Number of VTs
4. VCG-4
3. LCAS 7. User Name
5. VCG-5 LVC Configuration 8. Redundancy For VCG.1 to
6. VCG-6 4. Number of VTs
5. Encapsulation 9. LVC Configuration VCG.8 only
7. VCG-7 1. J2 Rx Path Trace
6. Minimum Number of VTs 10. LAPS Configuration
8. VCG-8 2. J2 Path Trace
8. Virtual Concatenation 4. EED Threshold or
9. Redundancy 5. SD Threshold
Primary
VCG-1 3. LCAS
4. Number of VTs
1. FCS
Primary 5. Encapsulation
2. PTI for Client Data
1. Admin Status 6. Minimum Number of VTs
3. UPI for Client Data
2. VC Type 7. User Name
4. Delta
3. LCAS 8. Redundancy
5. Core Scrambling
4. Number of VTs 9. Revertive
6. Payload Scrambling
6. Minimum Number of VTs
11. Wait to Restore

13. Redundancy Port
14. LVC Configuration 1. Address
HVC 15. GFP Configuration 2. Control
3. SAPI Value
1. CL-A
2. CL-B
See
Sheet 2
Bundles
1. Slot
2. Bundle
Figure 4-71. Typical Configuration>Logical Layer Submenu Structure (SONET) (Sheet 1 of 2)

Logical Layer
1. IO
2. CL
3. Bundles
See
Sheet 1
CL
1. PDH
2. VCAT
3. HVC
HVC
1. CL-A
2. CL-B
CL-A
1. Port 1 Port 1
2. Port 2
3. All Ports 1. STS1-1
4. Common Parameters 2. STS1-2 STS1-1
3. STS1-3
1. J1 Path Trace
2. Padding
3. Signal Label
Bundles Common Parameters

1. Slot 1. RDI on Signal Label
2. Bundle 2. RDI on Path Trace
3. J1 Rx Path Trace
4. EED Threshold
5. SD Threshold
HDLC Bundle
Bundles
Rate (Kbps)
1. Slot
2. Bundle
3. Admin Status
4. User Name
5. L2 Protocol
6. Number of TS
7. Link OAM
8. Link OAM Mode
9. Remote Terminal
10. Source Slot CL
11. Source Port I/O
For CL
For I/O Modules

Figure 4-72. Typical Configuration>Logical Layer Menu Structure (SONET) (Sheet 2 of 2)

The configuration of the virtual port parameters for the modules programmed in
the various Megaplex-4100 slots is started from the Logical Layer submenu. This
screen is used to select the class of virtual ports to be configured.
To navigate to the required screen, use Configuration>Logical Layer.

A typical Logical Layer screen for a Megaplex-4100 equipped with CL.1/155 and
CL.1/155GbE modules is shown in Figure 4-73. This screen includes the following
options:
I/O For configuring the virtual port parameters of modules installed in I/O
slots. Configuration instructions for these modules can be found in
the Installation and Operation Manual of each module.
Note however that not all the I/O modules have virtual ports.
CL For configuring the parameters of the virtual ports located on the

CL.1/155 and CL.1/155GbE modules.
Note that the CL.1 module does not have virtual ports.
Bundles For configuring Ethernet services bundles on E1 and T1 ports

(including PDH ports on CL.1/155 and CL.1/155GbE modules).
MP-4100
Configuration>Logical Layer
1. IO >
2. CL >
3. Bundles>
>

-----------------------------------------------------------------------------
Figure 4-73. Typical Logical Layer Class Selection Screen
³ To select the type of virtual ports to be configured:

Type the corresponding item number and then press <Enter>.
Selecting a Specific I/O Module Virtual Port to be Configured

The selection of a virtual I/O port to be configured is made in two steps:
1. Select a specific I/O module.
2. Select a specific port on the selected module.
³ To select a virtual port on an I/O module:

1. On the screen of Figure 4-73, select IO and then press <Enter>.
2. You will see the I/O module selection screen. A typical screen is shown in
Figure 4-74. The screen includes only modules programmed in the chassis that
have virtual ports.

MP-4100
Configuration>Logical Layer>IO
1. I/O 1 (HS-U12)>
2. I/O 2 (M8SL)>
3. I/O 3 (M8SL)>
4. I/O 6 (HS-U12)>
5. I/O 7 (HS-U12)>
6. I/O 8 (HS-U12)>
>

-----------------------------------------------------------------------------
Figure 4-74. Typical I/O Logical Layer Module Selection Screen

3. Select a module from the list by typing the number corresponding to its slot,
and then press <Enter>.
4. You will see the Slot port selection screen for the selected module. The ports
appearing on the screen depend on the module type. Refer to the Installation
and Operation Manual of the module for configuration instructions.
Configuring Logical Layer on SDH/SONET Links
Selecting the Specific CL Virtual Port to be Configured

The selection of the CL virtual port to be configured is made in two steps:
1. Select the type of ports to be configured.
2. Select a specific port of the selected type.
³ To select a virtual port on a CL.1/155 or CL.1/155GbE module:

1. On the screen of Figure 4-73, select CL and then press <Enter>.
2. You will see the CL port type selection screen. A typical screen is shown in
Figure 4-75.
The screen includes the following options:
PDH Configure the parameters of the internal PDH ports.
VCAT Configure the virtually concatenated groups on the SDH/SONET links

(available only on CL.1/155GbE modules). See Configuring Ethernet
Services for instructions.
HVC Configure the parameters of the high-order virtual containers in the
SDH/SONET link frame.

MP-4100
Configuration>Logical Layer>CL
1. PDH >
2. VCAT>
3. HVC >
>

-----------------------------------------------------------------------------
Figure 4-75. Typical CL Logical Layer Type Selection Screen

3. Select the desired option, and then press <Enter>.
Configuring Virtual PDH Ports

Use the following procedure to configure the parameters of the virtual PDH ports
of the CL.1/155 or CL.1/155GbE modules, and assign the port timeslots (instead
of using Configuration>System>TS Assignment). It is not necessary to select a
specific CL.1/155 or CL.1/155GbE module; at any time, only the PDH mapper of
the active CL module is used to carry traffic, and therefore only one set of
configuration parameters is used for both CL modules.
For convenience, you can simultaneously configure the parameters of all the PDH
ports (except for redundancy parameters and timeslot assignment, which cannot
be simultaneously configured for all the ports). You can then change the
configuration of individual PDH ports as required.
To navigate to the required screen, use Configuration>Logical Layer>CL>PDH.
Configuring PDH Parameters

1. On the screen of Figure 4-73, select CL and then press <Enter>.
2. On the CL Logical Layer screen, select PDH and then press <Enter>.
3. You will see the PDH ports selection screen. A typical screen is shown in
Figure 4-76. The screen includes two pages: use N and P to scroll among the
two pages. The current Admin Status of each port appears next to its name.

MP-4100
Configuration>Logical Layer>CL>PDH
1. PDH 1 (Down)> 12. PDH 12 (Down)> 23. PDH 23 (Down)> 34. PDH 34 Down)>
... (N)
>

-----------------------------------------------------------------------------
Figure 4-76. Typical PDH Port Selection Screen
Note The number of ports appearing on the second page depends on the port type:
• For SDH links, the total number of PDH ports is 63, and all the ports simulate
internal E1 ports
• For SONET links, the total number of PDH ports is 84, and all the ports
simulate internal T1 ports.
The last item on the second page is All Ports.
4. Select the number of the desired port, for example, 1 for PDH 1 and then press
<Enter> to display the parameters configuration screen.
You can also select All Ports: in this case, Redundancy is a read-only
parameter, and is set to None.
5. You will see the corresponding PDH configuration screen. Typical PDH
configuration screens with default values are shown in Figure 4-77 and
Figure 4-78. Table 4-21 lists the port configuration parameters of E1 ports on
SDH links, and Table 4-22 lists the parameters of T1 ports on SONET links.
6. To configure the port parameters, select the desired item and then press
<Enter> to display the corresponding parameter selection screen, or toggle the
current selection.
For LVC Configuration instructions, see page 4-92.
For Time Slot Assignment instructions, see Configuring Timeslot Assignment
on page 4-140.

MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Down)

2. User Name ... ()
3. Frame Type > (G.732S)
6. Idle Code[0 - ff] ... (FF)
9. LVC Configuration >
>

-----------------------------------------------------------------------------
Figure 4-77. Typical PDH Configuration Screen (E1 Port on SDH Link)
MP-4100
1. Admin Status (Down)

2. User Name ... ()
3. Frame Type > (ESF)
5. FDL Type > (Response)
6. Restoration Time > (10 Seconds (62411))
7. Idle Code[0 - ff] ... (FF)
>

-----------------------------------------------------------------------------
Figure 4-78. Typical PDH Configuration Screen (T1 Port on SONET Link)

Table 4-21. PDH Virtual Port Parameters – E1 Ports (SDH Links)
Admin Status Used to enable/disable the flow of UP – The flow of traffic is enabled.
traffic through the selected port DOWN – The flow of traffic is disabled. This state
should be selected as long as the port
configuration has not yet been completed, or
when it is necessary to stop traffic flow through
the port.
Default: DOWN
User Name Used to assign a logical name to the Up to 25 alphanumerical characters.

selected port Default: Empty String
Frame Type Selects the port framing mode. G.732N – The port handles the traffic as a basic
Do not select G.732S or G.732S-CRC4 G.704 framed signal. The port terminates the E1
framing for ports used by Ethernet overhead.
services: if you intend to configure G.732N-CRC4 – The port handles the traffic as a
Ethernet bundles on this port, you must basic G.704 framed signal, with the CRC-4 option
select G.732N or G.732N-CRC4 framing. enabled. The port terminates the E1 overhead.
It is recommended to select a mode that G.732S – The port handles the traffic as a G.704
supports CRC-4, to enable the collection framed signal with multiframe structure based
of performance monitoring data on timeslot 16. The port terminates the E1
overhead.
G.732S-CRC4 – The port handles the traffic as a
G.704 framed signal with multiframe structure
based on timeslot 16, with the CRC-4 option
enabled. The port terminates the E1 overhead.
Default: G.732S
Redundancy Controls the use of port redundancy. NONE – Redundancy disabled for the port being
When redundancy is enabled, configured.
Megaplex-4100 uses the revertive mode. DUAL CABLE P. TX – Redundancy function is
Therefore, make sure to select an enabled. Each of the two ports in the
appropriate Wait to Restore value. redundancy pair is connected through a separate
After redundancy is enabled, additional connection to the remote equipment, and both
read-only fields appear to provide ports transmit in parallel the same data.
information on the redundancy partner Therefore, a remote Megaplex-4100 unit can
slot and channel (port), and the independently select an active port, and does
redundancy status of the port (primary not have to flip to synchronize its selection with
or not). The first port of a redundancy that of the local Megaplex-4100 unit.
pair always becomes the primary port, Default: NONE
therefore make sure to plan ahead the
order in which ports are configured.
See redundancy configuration guidelines
in the Note on page 4-92

Restoration Time Used to change the frame 1 SECOND (FAST) – After 1 second.
synchronization algorithm, to reduce the 10 SECONDS (62411) – Similar to the
time required for the port to return to requirements of AT&T TR-62411 (after
normal operation after local loss of 10 seconds).
synchronization
CCITT – Complies with ITU-T Rec. G.732.
Default: CCITT
Idle Code Selects the code transmitted to fill idle The available selections are 00 to FF (hexa).
(unused) timeslots in the frames Do not select 00, 08, 10, 12, 21, 24, 42, 49, 84,
transmitted through this port. or 92 as the idle code.
Default: 7F
Cross Connect Selects the handling of the data passing DS0 – Enables routing each individual timeslot
through the port from this port to other module ports or bundles.
Also supports split timeslot assignment.
DS1 – All the payload timeslots are transparently
connected.
Default: DS0
Destination Slot Specifies the module (I/O slot) to which The available selections are the CL modules
the data stream handled by the port is installed in the chassis, and I/O modules IO-1 to
routed. IO-10.
When the port serves as termination Default: – (None)
point of an Ethernet services bundle, it
is not necessary to select a destination
slot.
using the DS1 cross-connect mode
Destination Port Specifies the port to which the data The available selections are 1 to 8 for external or
stream handled by the port is routed. internal ports, or 1 to 63 for PDH ports (actual
When the port serves as termination range depends on the destination module).
point of an Ethernet services bundle, it Default: – (None)
is not necessary to select a destination
port.
using the DS1 cross-connect mode
Redundancy Slot Selects the slot in which the other The available selections are the CL modules
module of a redundancy pair is installed. installed in the chassis, and I/O 1 to I/O 10.
For ports on which Ethernet service Default: CL
bundles are defined, another PDH port,
or another module with Ethernet ports,
for example, M8E1 or M8SL, must be
selected.
The selection must always be
symmetrical.
Redundancy is NONE

Redundancy Selects the other port of a redundancy The available selections are 1 to 8 for external or
Channel pair. internal ports, or 1 to 63 for PDH ports (actual
The selection must always be range depends on the destination module).
symmetrical. Default: – (None)
Redundancy is NONE
Therefore, the module starts evaluating
the criteria for redundancy switching
(flipping) only after this interval expires.
This ensures that another flipping
cannot occur before the specified
interval expires.
Redundancy is NONE
Inband Controls the transfer of inband OFF – The transfer of management traffic is
Management management traffic through this port disabled.
DEDICATE PPP – The transfer of management
traffic is enabled. The management traffic is
transferred in a dedicated timeslot, using
synchronous PPP over HDLC encapsulation.
DEDICATE FR – The transfer of management
traffic is enabled. The management traffic is
transferred in a dedicated timeslot, using Frame
Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
Default: OFF
Routing Protocol When the transfer of inband NONE – Routing of management traffic not
management traffic is enabled, controls supported.
the transmission of RIP2 routing tables. PROPRIETARY RIP – Management traffic is
Transmitting these tables enables other routed using RAD proprietary routing protocol.
equipment to use the RIP2 routing
RIP2 – In addition to the RAD proprietary routing
protocol for management traffic carried
protocol, RIP2 routing is also supported.
through this port.
PROP RIP NO NMS TX – Same as RIP2, but the
routing tables transmitted through this port do
Inband Management is OFF
not include information on the network
management stations (NMS) learned by the
Megaplex-4100.
Default: NONE

Primary Displays the port function in a YES — This port serves as the primary port of a
redundancy pair. Configuration redundancy pair.
parameters prepared for the primary NO — This port serves as the alternative port of
port are automatically copied to the a redundancy pair.
other port as soon as the other port is
Default: NO
specified.
Redundancy is NONE
Table 4-22. PDH Virtual Port Parameters – T1 Ports
Admin Status See Table 4-21

User Name See Table 4-21
Frame Type Determines the framing mode for this SF (D4) – The port handles the traffic as an SF
port framed signal with robbed bit signaling (12
frames per multiframe).
ESF – The port handles the traffic as an ESF
framed signal with robbed bit signaling (24
frames per multiframe).
Default: ESF
Redundancy See Table 4-21
FDL Type Controls the operating mode of the FDL. RESPONSE – The Megaplex-4100 only answers
This option can be selected only when commands received through the FDL, and thus
the framing mode is ESF, otherwise this does not initiate FDL traffic.
field shows N/A, and cannot be changed COMMAND – The Megaplex-4100 can initiate
polling by sending commands through the FDL.
NONE – FDL is ignored.
Default: RESPONSE
Restoration Time Used to change the frame 1 SECOND (FAST) – After 1 second.
synchronization algorithm, to reduce the 10 SECONDS (62411) – Similar to the
time required for the port to return to requirements of AT&T TR-62411 (after
normal operation after local loss of 10 seconds).
synchronization Default: 10 SECONDS (62411)
Idle Code Selects the code transmitted to fill idle The available range is 60 to 7F, and C0 to FF
(unused) timeslots in frames (hexa).
transmitted through the port Do not select 84 or 92 as the idle code.
Default: 7F
Cross Connect See Table 4-21
Destination Slot See Table 4-21

Destination Port See Table 4-21.

The available selections are 1 to 8 for
external ports, or 1 to 84 for PDH ports
(actual range depends on the
destination module)
Redundancy Slot See Table 4-21

For ports on which Ethernet service
bundles are defined, another PDH port,
or another module with Ethernet ports,
for example, M8T1, must be selected
Redundancy See Table 4-21.

Channel The available selections are 1 to 8 for
external ports, or 1 to 84 for PDH ports
(actual range depends on the
destination module)
Wait to Restore See Table 4-21
Inband See Table 4-21
Management
Routing Protocol See Table 4-21
Primary See Table 4-21
Note When using the redundancy feature, it is necessary to select the same values for
the following parameters of the two ports configured as a redundancy pair:
• Admin Status • Restoration Time
• Frame Line • Inband Management
• Redundancy • Routing Protocol
• Idle Code • Cross Connect
However, you can select different Wait to Restore times, because the times
selected at the two ends should be different.
To save duplication of configuration parameters, all the parameters listed above
are selectable only for the primary port, and therefore make sure to configure
first the primary port of a redundancy pair. The parameters of the other
(alternative) port are automatically copied from the primary port after the
configuration of the primary port has been completed, even before the database
has been updated (you can display the port configuration parameters using the
Monitoring menu).
The same is true with respect to timeslot assignment: only the primary port must
be configured.
Configuring the LVC Parameters

A typical LVC Configuration screen is shown in Figure 4-77. The parameters that
can be configured are explained in Table 4-23. Note that in addition to the

parameters configured by means of the LVC Configuration screen, there is a

common set of LVC parameters, configured as port of the SDH/SONET physical
port parameters, by means of the Common PDH LVC Parameters screen (see
Configuring Common PDH LVC Parameters section starting on page 4-74).
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1 (Up)>LVC Configuration
1. J2 Rx path trace (Enable)

2. J2 path trace ... (www.rad.com)
3. Padding (NULLs)
6. Protection Mode > (Path Protection)
7. Mapping Mode > (Auto)
8. Protection Partner > (Adjacent CL)
9. Payload Label [0 – 7] ... (2)
>

-----------------------------------------------------------------------------
Figure 4-79. Typical LVC Configuration Screen for PDH Ports
Table 4-23. LVC Configuration Parameters for CL.1/155 and CL.1/155GbE PDH Ports
J2 Rx Path Trace Controls the checking of the received ENABLE – Path trace label is checked.
path trace label by the corresponding DISABLE – Path trace label is not checked.
group
Default: DISABLE
J2 Path Trace Specifies the path trace label. Alphanumeric string of 15 characters. If not
This parameter is relevant only when all of the 15 characters are needed for the
J2 Rx Path Trace is ENABLE prescribed label, make sure to specify the
appropriate Padding method.
Default: www.rad.com
Padding Specifies the type of characters used NULLS – NUL characters.

to pad the path trace label, when it SPACES – Space characters.
is shorter than the required length of
Default: NULLS
15 characters
EED Threshold Selects the BER value, which if The available selections are 1E-3 (BER
exceeded results in the generation of threshold of 10-3), 1E-4 (10-4) or 1E-5 (10-5).
the error rate degradation alarm for Default: 1E-3 (BER of 10-3)
the port

SD Threshold Selects the BER value, which if The available selections are 1E-6 (BER
exceeded results in the generation of threshold of 10-6), 1E-7 (10-7), 1E-8 (10-8) or
the signal-degraded alarm for the 1E-9 (10-9).
port Default: 1E-6 (BER of 10-6)
Protection Mode Selects the traffic protection mode OFF – No protection.

Path Protection – Path protection enabled.
Default: OFF
Mapping Mode Select the mapping mode of the TU AUTO – Automatic mapping: the mapping of
carrying the payload of the PDH port. the PDH port selected as primary on one
This parameter is not displayed when SDH/SONET link is automatically copied to the
Protection Mode is OFF same TU on the other SDH/SONET link. AUTO
cannot be selected when the PDH port is
already mapped (the mapping must be
manually performed, or perform the mapping
only after the Path Protection mode is
selected).
MANUAL – Manual mapping. The port is
mapped manually to different TUs of the
same link, or on different links.
Default: AUTO
Protection Partner Specifies the link serving as the ADJACENT CL – The protection link is the
protection link for link being SDH/SONET link with the same number
configured. located on the other CL module. For example,
This parameter is not displayed when if you are configuring link A of the CL module
Protection Mode is OFF A, the corresponding protection partner is
link A of the CL module B.
LOCAL CL – The protection link is the other
SDH/SONET link on the same CL module. For
example, if you are configuring link A of the
CL module A, the corresponding protection
partner is link B of the CL module A.
Default: LOCAL CL
Payload Label Specifies the expected signal label Number in the range of 0 to 7.
(one byte) Default: 2
Configuring HVC Virtual Ports

Use the following procedure to configure the parameters of the virtual high-order
ports (VC-4 virtual container for SDH links, or STS-1 SPE for SONET links) of the
CL.1/155 or CL.1/155GbE modules installed in the Megaplex-4100.
Separate parameters can be configured for each high-order port on each CL
module.
For convenience, you can simultaneously configure the parameters of all STS-1
ports of a CL module; you can then change the configuration of each port as
required.

To navigate to the required screen, use Configuration>Logical Layer>CL>HVC.
Selecting the CL.1/155 or CL.1/155GbE to be Configured

1. Select HVC on the CL menu. You will see the screen used to select between the
two CL modules that can be installed in the Megaplex-4100. A typical CL
module selection screen is shown in Figure 4-80.
MP-4100
Configuration>Logical Layer>CL>HVC
1. CL-A>
2. CL-B>
>

-----------------------------------------------------------------------------
Figure 4-80. Configuration>Logical Layer>CL>HVC>CL Selection Screen

2. Select the desired CL module and then press <Enter> to display the
configuration task selection screen for the selected CL module.
Configuring HVC Ports for CL.1/155 or CL.1/155GbE with SDH Links

For CL.1/155 or CL.1/155GbE modules with SDH links, you must select the target
port: all the ports on the selected CL module, or only the HVC port of a specific
SDH link.
Figure 4-81 shows a typical HVC task selection screen for the selected CL.1/155
or CL.1/155GbE module.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A
1. Port 1 >
2. Port 2 >
3. All Ports >
>

-----------------------------------------------------------------------------
Figure 4-81. Typical HVC Selection Screen for CL.1/155 or CL.1/155GbE Module with SDH Links

³ To select the HVC to be configured (SDH links):

1. Select the number of the desired task, and then press <Enter> to display the
appropriate configuration screen:
Port 1 Configure the VC-4 parameters of port 1 of the selected CL

module.
Port 2 Configure the VC-4 parameters of port 2 of the selected CL

module.
All Ports Configure the same parameters for both SDH ports of the
selected CL module.
When it is necessary to select different parameters for each
port, you can use the common configuration as a starting point,
and then modify the parameters of each port as required.
³ To configure HVC parameters (SDH links):

A typical VC-4 configuration screen with factory defaults for HVC Logical Layer is
The parameters that can be configured by means of the VC-4 screen are
described in Table 4-24.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1
VC-4
1. RDI on signal label (Disable)
2. RDI on path trace (Disable)
3. J1 Rx path trace (Disable)
7. Signal Label[0 - ff]... (02)
>

-----------------------------------------------------------------------------
Figure 4-82. Typical VC-4 Configuration Screen for Logical Layer (SDH Links)

Table 4-24. Configuration – VC-4 Parameters (CL with SDH Links)
RDI on Signal Controls the sending of RDI indications by the ENABLE – RDI is sent when a signal label
Label port, in case the received signal label is mismatch is detected.
different from the expected signal label DISABLE – RDI is not sent when signal label
mismatch is detected. Nevertheless, RDI is
still sent in case of LOP (loss of pointer) or
unequipped signal label condition.
Default: DISABLE
RDI on Path Controls the sending of RDI indications by the ENABLE – RDI is sent in case a signal label
Trace port, in case the received path trace label mismatch is detected.
(carried in SDH overhead byte J1) is different DISABLE – RDI is not sent when a signal
from the expected path trace label label mismatch is detected. Nevertheless,
RDI is still sent in case a LOP (loss of
pointer) or unequipped signal label
condition is detected.
Default: DISABLE
J1 Rx Path Trace Controls the checking of the received path ENABLE – Path trace label is checked.
trace label by the port DISABLE – Path trace label is not checked.
Default: DISABLE
J1 Path Trace Specifies the path trace label. Alphanumeric string of up to 15 characters.
This parameter is relevant only when J1 Rx If not all of the 15 characters are needed
Path Trace is ENABLE for the prescribed label, make sure to
specify the appropriate Padding method.
EED Threshold Selects the BER value, which if exceeded The available selections are 1E-3 (BER
results in the generation of the error rate threshold of 10-3), 1E-4 (10-4), 1E-5 (10-5).
degradation alarm for the port Default: 1E-3 (BER of 10-3)
SD Threshold Selects the BER value, which if exceeded The available selections are 1E-6 (BER
results in the generation of the threshold of 10-6), 1E-7 (10-7), 1E-8 (10-8) or
signal-degraded alarm for the port 1E-9 (10-9).
Default: 1E-6 (BER of 10-6)
Signal Label Specifies the expected signal label (one byte) Hexadecimal number in the range of 0 to FF
(two digits).
Default: 02
Configuring HVC Ports for CL.1/155 or CL.1/155GbE with SONET

Links
For CL.1/155 or CL.1/155GbE modules with SONET links, you must select the
target port: all the ports on the selected CL module, or only the HVC ports of a
specific SONET link. In addition, you need to configure common HVC parameters
for each SONET port.
Figure 4-83 shows a typical HVC task selection screen for the selected CL.1/155
or CL.1/155GbE module.

MP-4100
Configuration>Logical Layer>CL>HVC>CL-A
1. Port 1 >
2. Port 2 >
3. All Ports >
4. Common Parameters>
>

-----------------------------------------------------------------------------
Figure 4-83. Typical HVC Task Selection Screen for CL Module with SONET Links
³ To select the HVC to be configured (SONET links):

1. Select the desired task:
Port 1 Configure the STS-1 parameters used only for SONET port 1
of the selected CL module.
Port 2 Configure the STS-1 parameters used only for SONET port 2
of the selected CL module.
All Ports Configure the same parameters for all the STS-1s on both
SONET ports of the selected CL module.
When necessary to select different parameters for each
STS-1, you can use the common configuration as a starting
point, and then modify the parameters of each STS-1 as
required.
Common Configure the parameters that must have identical values for
Parameters all the STS-1s of the same CL module.
2. After selecting a specific SONET port, you must select a specific STS-1. The
STS-1 selection (Figure 4-85) screen opens after pressing <Enter>.
³ To configure HVC parameters (SONET links):

1. Select Common Parameters on the HVC selection screen. A typical screen is
shown in Figure 4-84. The parameters that can be configured by means of the
Common Parameters screen are described in Table 4-25.

MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Common Parameters
1. RDI on signal label (Disable)

>

-----------------------------------------------------------------------------
Figure 4-84. Typical HVC Common Parameters Screen for CL with SONET Links
Table 4-25. Configuration – Common Parameters (CL.1/155 with SONET Links)
RDI on Signal Controls the sending of RDI indications, in ENABLE – RDI is sent when a signal label
Label case the received signal label is different mismatch is detected.
from the expected signal label DISABLE – RDI is not sent when signal label
mismatch is detected. Nevertheless, RDI is still
sent in case of LOP (loss of pointer) or
unequipped signal label condition.
Default: DISABLE
RDI on Path Controls the sending of RDI indications by ENABLE – RDI is sent in case a signal label
Trace the ports, in case the received path trace mismatch is detected.
label (carried in SONET overhead byte J1) DISABLE – RDI is not sent when a signal label
is different from the expected path trace mismatch is detected. Nevertheless, RDI is still
label sent in case a LOP (loss of pointer) or
unequipped signal label condition is detected.
Default: DISABLE
J1 Rx Path Trace Controls the checking of the received path ENABLE – Path trace label is checked.
trace label by the ports DISABLE – Path trace label is not checked.
Default: DISABLE
EED Threshold Selects the BER value, which if exceeded The available selections are 1E-3 (BER
results in the generation of the error rate threshold of 103), 1E-4 (104), 1E-5 (105).
degradation alarm for the STS-1 ports Default: 1E-3 (BER of 103)
SD Threshold Selects the BER value, which if exceeded The available selections are 1E-6 (BER threshold
results in the generation of the of 106), 1E-7 (107), 1E-8 (1-8) or 1E-9 (109).
signal-degraded alarm for the STS-1 ports Default: 1E-6 (BER of 106)

2. Select the desired CL SONET port (Port 1 or Port 2), or All Ports on the HVC
task selection screen. If you select a specific SONET port, you will see the
STS-1 selection screen (Figure 4-85).
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1
1. STS1-1 >
2. STS1-2 >
3. STS1-3 >
>

-----------------------------------------------------------------------------
Figure 4-85. Typical STS-1 Selection Screen (CL with SONET Links)
3. After selecting the desired STS-1 port on the STS-1 selection screen, or All
Ports, you will see the STS-1 configuration screen. A typical screen is shown
in Figure 4-86. The parameters that can be configured by means of the STS-1
screen are described in Table 4-26.
MP-4100
Configuration>Logical Layer>CL>HVC>CL-A>Port 1>STS1-1

2. Padding (Nulls)
3. Signal Label ... (02)
>

-----------------------------------------------------------------------------
Figure 4-86. Typical STS-1 Configuration Screen (CL with SONET Links)

Table 4-26. Configuration – STS-1 Parameters (CL with SONET Links)
J1 Path Trace Specifies the path trace label. Alphanumeric string of up to 15 characters.
This parameter is relevant only when J1 Rx If not all of the 15 characters are needed
Path Trace is ENABLE for the prescribed label, make sure to
specify the appropriate Padding method.
Padding Specifies the type of characters used to pad NULLS – NUL characters.
the path trace label, when it is shorter than SPACES – Space characters.
the required length of 15 characters.
Default: NULLS
The selected value overrides the Common
Parameters selection
Signal Label Specifies the expected signal label (one byte) Hexadecimal number in the range of 0 to FF
(two digits).
Default: 02
Configuring Ethernet Services

Using the Metropolitan Ethernet Forum terms, Ethernet traffic is forwarded (or
flows) among specified bridge ports in accordance with user-configured rules that
define Ethernet Virtual Connections (flows). Therefore, Ethernet services are
configured by defining flows within the Megaplex-4100. A flow interconnects at
least two bridge ports, however a given bridge port can serve as the termination
point of several flows. The maximum number of flows that can be defined on a
Megaplex-4100 is 250.
Note For an overview of the MEF definition of Ethernet services, refer to Appendix C.
The current Megaplex-4100 version supports E-line flows per Metro Ethernet
Forum (MEF) specifications (an E-line is a type of Ethernet virtual connection that
interconnects exactly two bridge ports).
The following types of bridge ports can be defined:
• Logical ports configured on E1 or T1 ports (including PDH ports), called
bundles (M8E1, M8T1, and M8SL modules). Bundles use a special protocol
to support the flow of Ethernet traffic. Two types of bundle protocols can
be used: HDLC and MLPPP.
• Each Ethernet physical port (of the type located on M8E1, M8T1, M8SL,
MPW-1, OP-108C, OP-106C, or ASMi-54C modules) can also serve as a
bridge port.
• Each Internal Eth port of the OP-108C or OP-106C modules
• Each active PCS of the ASMi-54C module
• Virtually concatenated groups, defined on the SDH/SONET links of
CL.1/155GbE modules
• GbE ports located on the Megaplex-4100 CL.1/GbE and CL.1/155GbE
modules

The total number of bridge ports supported by a Megaplex-4100 is as follows.

• For I/O modules with Ethernet ports:
• One bridge port exists on each Ethernet physical interface.
• One bridge port exists on each bundle (M8E1, M8T1, and M8SL modules).
• Two internal Ethernet bridge ports exist on each OP-108C or OP-106C
module
• 8 bridge ports exist on each PCS of the ASMi-54C module
• 100 bridge ports exist on the router interface of the MPW-1 module.
The maximum number of bridge ports that exist on each module with
Ethernet interface is summarized in Table 4-27.
Table 4-27. Maximum Number of Bridge Ports for Megaplex-4100 Modules
Module Name External Ports Other
M8E1, M8T1, M8SL 3 32 (Bundles)
MPW-1 3 100 (Router interface)
ASMi-54 2 8 (PCS)
OP-108C, OP-106C 2 2 (Internal Ethernet)
• For CL modules:
• One bridge port exists on each GbE physical interface
• One bridge port exists on each virtually concatenated group, up to a
maximum of eight virtually concatenated groups per SDH/SONET
subsystem.
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.
³ To configure a Megaplex-4100 for providing Ethernet services:

1. After configuring the required physical ports, use Configuration>Logical Layer
to:
• Configure the prescribed Ethernet bundles on I/O module ports, and on
PDH ports
• Configure the prescribed virtually concatenated groups on SDH/SONET links
2. Use Configuration>Applications to configure Ethernet flows.
Figure 4-87 shows the detailed structure of the Applications menu.

Applications
Flows
Ethernet Services
1. Flow Flow Type
1. Flows 2. User Name
3. Flow Type 1. E-LINE
4. Bridge Port Mapping 2. E-LAN Reserved
Bridge Port Mapping

Add (A) Display List (U)
Bridge Port Mapping

Bridge Port Mapping

BP C-VLAN Type
1. C-VLAN Type 1. Unaware
C-VLAN ID 2. Aware
2. SP-VLAN
3. Slot
Port
Rate
BP User Name
Figure 4-87. Typical Configuration>Applications Menu Structure
Configuring HDLC Bundles for Ethernet Services

For framed E1 and T1 ports (including PDH ports located on CL modules), you can
configure up to four HDLC bundles for each port, where each bundle can be
assigned the desired fraction (number of timeslots) of the port bandwidth.
Moreover, you can select specific timeslots to be assigned to each bundle. The
number of timeslots assigned to a bundle must always be even, which means
that the bundle bandwidth is a multiple of 128 kbps, up to a maximum of
1920 kbps (30 × 64 kbps) for E1 ports, or 1536 kbps (24 × 64 kbps) for T1 ports.
For unframed ports, the port bandwidth cannot be split among multiple bundles,
and therefore the whole port bandwidth must be assigned to only one bundle.
Note This Megaplex-4100 version supports the unframed mode only for E1 ports.
The maximum number of bundles that can be defined on an eight-port I/O

module (M8E1, M8T1, M8SL) is 32, which is the maximum number of bundles that
may be configured when all the ports use a framed mode.
The CL modules do not include an Ethernet bundle termination function – only I/O
modules with Ethernet ports (M8E1, M8T1, M8SL) have this capability. Therefore,
when you plan to use Ethernet bundles on PDH ports, you must also select an I/O

module on which to perform Ethernet bundle termination (all the Ethernet

bundles of a given PDH port must be terminated on the same I/O module). This
I/O module must fulfill the following requirements:
1. The additional bundle is counted within the total number of bundles processed
by the selected I/O module (maximum 32).
2. Sufficient bandwidth must be available on the PCM buses connecting to the
selected I/O module to carry the bundle timeslots.
3. Sufficient bandwidth must be available on the Fast Ethernet traffic bus
connecting the selected I/O module to the CL module to carry the Ethernet
traffic of the bundle.
³ To configure an HDLC bundle:

1. Open the Configuration>Logical Layer menu, and select Bundles.
Note When you open the Bundles screen, it shows the parameters of the last
configured bundle. If you reach the screen after starting a new session, it shows
parameters for the first bundle that can be configured on the slot with the
lowest I/O number.
In both cases, you can sequentially scroll through all the existing bundles by
pressing the F or B key: first, this action will scroll the bundle numbers for the
current slot, and then will automatically move to the next slot, and scroll through
its bundles, and so on, cyclically.
2. Select Slot, and then press <Enter> to display the slot selection screen. The
slot selection screen displays only slots in which I/O modules that support
bundles are installed or programmed.
3. Select the desired slot, and then press <Enter> to return to the bundle
configuration screen. At this stage, you can either:
• Add a new bundle on the selected slot: type A (Add). The next free bundle
number is automatically assigned and appears in the Bundle field.
• Edit an existing bundle. The desired bundle number can be either typed
directly in the Bundle field, or can sequentially scroll through the Bundle
field by pressing the F or B key.
• Delete an existing bundle: first make sure to display the desired bundle
(check both the Slot and the Bundle fields), and then type D (Delete),
and confirm by pressing <Enter>.

MP-4100
Configuration>Logical Layer>Bundles
Rate(Kbps)[128 - 16384] (128)
1. Slot > (IO-1 (M8E1))
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
5. L2 Protocol > (HDLC)
6. Number Of TS[2 - 32] ... (2)
7. Link OAM (Enable)
8. Link OAM Mode (Active)
9. Remote Terminal (Disable)
10. Source Slot > (IO-1)
11. Source Port > (Link 1)
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
A. Bundle on I/O Module

MP-4100
Rate(Kbps)[128 - 16384] (128)
1. Slot > (IO-1 (M8E1))
2. Bundle[1 - 32] ... (2)
4. User Name ... ()
6. Number Of TS[2 - 32] ... (2)
7. Link OAM (Enable)
8. Link OAM Mode (Active)
10. Source Slot > (CL)
11. Source Port > (PDH 1 )
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
B. Bundle on PDH Port

Figure 4-88. Typical HDLC Bundle Configuration Screens
4. When you add a new bundle, or edit an existing one, you must also select the
Layer 2 protocol in the L2 Protocol field. For HDLC bundles, select HDLC and
the data form fields are immediately updated.
5. At this stage, select the HDLC bundle configuration parameters. The fields
displayed on the screen automatically adjust to the selected values.
Table 4-28 lists the available parameters for HDLC bundles.

Table 4-28. HDLC Bundle Parameters
Slot Selects the I/O slot number of the bundle Selected on a screen that opens when the
on which the bundle Ethernet traffic Slot field is selected, or sequentially changed
termination is performed: by pressing the F or B key.
• For a bundle using the local E1 or T1 Both methods display only slots in which I/O
ports for the transport of the Ethernet modules that support bundles are installed or
bundle traffic, this is also the I/O slot programmed.
number of the bundle. Default: I/O-1
• When you are configuring a HDLC
bundle on a PDH port, this parameter
specifies the I/O module that
processes the bundle traffic
Bundle Selects an existing bundle number, or 1 to 32.

displays the automatically assigned Default: 1
number for a new bundle
Admin Status Used to enable/disable the bundle DOWN – The bundle is disabled. This state
should be selected as long as the
configuration of the corresponding bundle
has not yet been completed, when you want
to prepare a bundle for future applications
that is not yet to become active, or when it is
necessary to stop the bundle traffic flow.
UP – The bundle is active and can support
traffic flow. However, traffic can flow only if
the Admin Status of the source port used by
the bundle is also UP.
Default: DOWN
User Name Used to enter a logical name for the Up to 25 alphanumeric characters.
selected bundle Default: Empty string
Number of TS Selects the number of timeslots assigned The allowed range depends on the source
to the bundle. This number determines port type and framing mode:
the bandwidth available to the bundle. • 2, 4, 6, …, 30 for bundles defined on E1
The number of timeslots must always be ports using a framed mode (including PDH
even ports). Do not select odd values (1, 3, …,
etc. ).
• 2, 4, 6, …, 24 for bundles defined on T1
ports using a framed mode. Do not select
odd values (1, 3, …, etc. ).
• 32 for bundles defined on UNFRAMED E1
ports (not relevant for PDH ports).
Default: 2

Rate Displays the nominal bandwidth assigned The values applicable to HDLC bundles are as
to the bundle. follows:
The displayed value, which is a multiple of • 128 to 1920 kbps when Number of TS is
128 kbps, is automatically adjusted to the in the range of 2 to 30.
previously selected parameters • 128 to 1536 kbps when Number of TS is
in the range of 2 to 24.
• 2048 kbps when Number of TS is 32 (not
relevant for PDH ports).
Default: 128 kbps
L2 Protocol Selects the bundle Layer 2 protocol HDLC – HDLC protocol. The bundle can be
defined on framed or unframed ports, and its
maximum bandwidth is that of a single port.
MLPPP – MLPPP protocol. The bundle can be
defined only on unframed ports, and its
maximum bandwidth is a multiple of the port
bandwidth (2048 kbps for E1 ports). The
multiple is selected by the Number of Links
field. For configuration details, refer to the
Configuring MLPPP Bundles for Ethernet
Services section starting on page 4-108.
Default: HDLC
Link OAM Used to enable/disable the link OAM DISABLE – Link OAM functionality is disabled.
functionality for the selected bundle. ENABLE – Link OAM functionality is enabled.
The link OAM functionality covers the link Default: DISABLE
segment between the local bundle
endpoint (which in this case is the
internal framer serving the port circuits),
and the remote bundle endpoint
Link OAM Mode Selects the link OAM mode at the local ACTIVE – The local endpoint of the bundle
endpoint of the bundle. Different modes initiates all the OAM PDU exchanges.
must be selected for each bundle PASSIVE – The local endpoint of the bundle
endpoint. only responds to the received OAM PDUs.
This field is displayed only when the Default: ACTIVE
bundle Link OAM is ENABLE
Remote Terminal Enables terminal access to a remote unit DISABLE – The remote terminal functionality
that receives the bundle traffic. is disabled.
This field is displayed only when the ENABLE – The remote terminal functionality is
bundle Link OAM is ENABLE enabled.
Default: DISABLE

Source Slot Selects the source slot for the bundle. You can specify either an I/O module, or a CL
When you are configuring a bundle on a module.
PDH port, select here the corresponding If the source port is located on an I/O
CL module module, the selected slot must be identical to
the value selected for the Slot field above.
Selected on a screen that opens when the
Slot field is selected
Source Port Selects the source TDM port of the bundle The available range is as follows:
on the currently selected source slot. • 1 to 8 for I/O modules
The source port cannot be included in a • 1 to 63 for E1 PDH ports on SDH links
redundancy configuration
• 1 to 84 for T1 PDH ports on SONET links.
Selected on a screen that opens when a
Source Slot field is selected.
Default: 1
A HDLC bundle defined on an unframed E1 port is automatically assigned all the

port bandwidth (the equivalent of 32 timeslots). Management traffic can be
carried inband, as part of the Ethernet traffic, using the dedicated management
VLAN configured for the Megaplex-4100 host.
However, to complete the configuration of a HDLC bundle on a framed E1 or T1
port, it is necessary to specify the individual port timeslots that are served by the
bundle (this action is referred to as timeslot assignment). The source port of the
bundle is selected during bundle configuration.
Make sure to assign a number of timeslots equal to the number selected in the
Number of TS field.
Note The total number of timeslots that can be assigned to HDLC bundles configured
on the same source port is 30 for E1 ports, and 24 for T1 ports, and this number
can be split as required between the various port users; for example, when only
one HDLC bundle is configured on the port, it can be assigned all the 30 or 24
timeslots.
Any given port timeslot can be assigned to only one use (a HDLC bundle, TDM
traffic, or to management). Timeslots assigned to bundles are always Data
timeslots.
For the supervision terminal, use Configuration>System>TS Assignment (see

Configuring Timeslot Assignment).
Configuring MLPPP Bundles for Ethernet Services

M8E1 and M8SL modules support one active MLPPP bundle per module, that is,
only one MLPPP bundle on an M8E1 or M8SL module can have its Admin Status as
Up. You may however configure additional MLPPP bundles on that module, as
long as their Admin Status is Down.
An MLPPP bundle can use 2 to 8 links, and all of them must be located on the
same module. All the links (ports) used by the MLPPP bundle must have identical

physical layer parameters, and their Line Type must be configured as Unframed.
Therefore, each bonded link adds 2048 kbps to the available bandwidth, for a
total of 4096 kbps for 2 links, and up to 16384 kbps for 8 links.
Management traffic can be carried inband, as part of the Ethernet traffic, using
the dedicated management VLAN configured for the Megaplex-4100 host (see
Management Flow Configuration Procedure section starting on page 4-133).
Note that links (ports) used by MLPPP bundles cannot be part of a redundancy
pair. 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.
³ To configure an MLPPP bundle:

1. Open the Configuration>Logical Layer menu, and select Bundles.
2. Select a slot for the MLPPP bundle in the same way as for HDLC bundles (see
page 4-103). You can select only modules that support unframed ports, i.e.,
M8E1 or M8SL modules.
3. At this stage, you can either add a new MLPPP bundle on the selected slot, edit
or delete an existing bundle (see page 4-103). After you select a specific
bundle, or add a new one, the screen displays the complete bundle
configuration data form. This form has two pages, as shown in Figure 4-89.
4. When you add a new bundle, or edit an existing one, you must also select the
Layer 2 protocol in the L2 Protocol field. For MLPPP bundles, select MLPPP and
the data form fields are immediately updated.
MP-4100
Rate(Kbps)[128 - 16384] (4096)

1. Slot > (IO-1 (M8E1))
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
5. L2 Protocol > (MLPPP)
6. MLPPP MTU[80 - 1600] ... (250)
7. Link OAM > (Enable)
8. Link OAM Mode > (Active)
10. Number Of Links[1 - 8] ... (2)
... (N)
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B - Bkwd

-----------------------------------------------------------------------------
A. First Page

MP-4100
... (P)
>
#-Db Undo; A-Add; D-Delete; F-Fwd; B - Bkwd

-----------------------------------------------------------------------------
B. Second Page
Figure 4-89. Typical MLPPP Bundle Configuration Screen
5. At this stage, select the MLPPP bundle configuration parameters. The fields
displayed on the screen automatically adjust to the selected values.
Table 4-29 lists the available parameters for MLPPP bundles.
Table 4-29. MLPPP Bundle Parameters
Rate Displays the nominal bandwidth assigned The range includes the multiples of 2048kbps
to the bundle. in the range of 2048 kbps (1 × 2048kbps) to
The displayed value is automatically 16384 kbps (8 × 2048 kbps), in accordance
adjusted with the Number of Links field.
Default: 2048 kbps
Slot Selects the I/O slot number for the bundle Selected on a screen that opens when the
(see Step 2 above) Slot field is selected, or sequentially changed
by pressing the F or B key.
Both methods display only slots in which
modules that support bundles are installed or
programmed
Bundle See Table 4-28
Admin Status See Table 4-28
User Name See Table 4-28

L2 Protocol Selects the bundle Layer 2 protocol HDLC – HDLC protocol. The bundle can be
defined on framed or unframed ports, and its
maximum bandwidth is that of a single E1
port. See the Configuring HDLC Bundles for
Ethernet Services section starting on
page 4-103 for configuration details.
MLPPP – MLPPP protocol. The bundle can be
defined only on unframed ports, and its
maximum bandwidth is a multiple of
2048 kbps. The multiple is selected by the
Number of Links field.
Default: HDLC
MLPPP MTU Selects the Ethernet maximum The supported range is 80 to 1600 bytes.
transmission unit (MTU) for the MLPPP Default: 250
bundle
Remote Terminal See Table 4-28
Link OAM See Table 4-28
Link OAM Mode See Table 4-28
Number of Links Selects the number of links (E1 ports) The available range is 1 to 8.
used by the MLPPP bundle. Default: 1
You should select at least two links
Source Port Selects the bundle source ports. The available range is LINK 1 to LINK 8.
Several Source Port fields are displayed: The port is selected on a screen that opens
the total number is determined by the when a Source Slot field is selected.
Number of Links field. All these ports Default: LINK 1
must have identical physical layer
parameters
Configuring Virtual Concatenation Groups

Virtually concatenated groups can be configured on SDH/SONET links of
CL.1/155GbE modules. Refer to Appendix C for background information on virtual
concatenation.
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.
Megaplex-4100 also supports 1+1 redundancy for virtually concatenated groups,
as described in Section 1.8. Refer to the Configuring Virtually Concatenated Group
Redundancy section starting on page 4-122 for instructions.
Selecting the Virtually Concatenated Groups to be Configured

You can perform virtually concatenated group configuration in two ways:

• Configure the parameters of a specific virtually concatenated group. After

configuring a virtually concatenated group, make sure to map its VCs/VTs
using Configuration>System>Mapping.
• Configure all the currently-defined virtually concatenated groups with
similar parameters. You can change the parameters of each virtually
concatenated group as required.
The virtually concatenated group parameters depend on the link type (SDH or
SONET), and on the encapsulation method used on the group (or groups) being
configured: LAPS or GFP.
To navigate to the required screen, use Configuration>Logical Layer.
A full VCAT group selection screen is shown in Figure 4-90.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A
1. VCG 1 >
2. VCG 2 >
3. VCG 3 >
4. VCG 4 >
5. VCG 5 >
6. VCG 6 >
7. VCG 7 >
8. VCG 8 >
9. All VCG >
>

-----------------------------------------------------------------------------
Figure 4-90. Typical VCAT Virtually Concatenated Group Selection Screen
³ To select a specific virtually concatenated group to be configured:

1. On the Logical Layer class selection screen (Figure 4-73), select CL and then
press <Enter>.
2. On the CL Logical Layer screen, select VCAT and then press <Enter>.
3. You will see the CL module selection screen.
4. Select the desired CL module, and then press <Enter>. You will see the virtually
concatenated group selection screen (a typical screen is shown in Figure 4-90).
5. Type the corresponding virtually concatenated group number, 1 to 8, and then
press <Enter>.
³ To configure all the virtually concatenated groups with similar parameters (except
for Redundancy):
1. Perform Steps 1 to 4 above.
2. On the virtually concatenated group selection screen, select All VCG and then
press <Enter>.

To navigate to the required screen, use Configuration>Logical Layer>CL>VCAT>

CL-A or CL-B.
Using LAPS Encapsulation for Virtually Concatenated Groups on SDH

Links
A typical individual VCG screen for a Megaplex-4100 with SDH links that uses LAPS
encapsulation over VC-12 is shown in Figure 4-91. The selected group is
identified in the screen header.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1

2. VC type > (VC12)
3. LCAS (No)
4. Number of VCs [1 - 63] ... (3)
5. Encapsulation > (LAPS)
6. User Name ... ()
7. Redundancy (None)
9. LAPS Configuration >
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-91. Typical VCG Configuration Screen for LAPS Encapsulation over VC-12 (SDH Links)
If you selected All VCGs on the VCAT screen, the header in Figure 4-91 is All VCGs.
The parameters that can be configured by means of the VCG screen are described
in Table 4-30. When a selection screen is used, the Values column in Table 4-30
also lists the options displayed on the selection screen.
³ To configure a virtually concatenated group using LAPS encapsulation:

1. Type the number corresponding to the desired parameter, and then press
<Enter>.
2. For LVC Configuration and LAPS Configuration, separate configuration screens
are used.
On the selection screen, type the number of the desired option and then
press <Enter>. The selection screen closes, and the new value appears in the
VCG screen.

Table 4-30. Configuration>Logical Layer>VCG Screen Parameters – LAPS Encapsulation over SDH
Admin Status Used to enable/disable the flow of traffic DISABLE – The flow of traffic is disabled. This
through the selected virtually concatenated state should be selected as long as the
group configuration of the corresponding group has
not yet been completed, or when it is
necessary to stop traffic flow through the
group.
ENABLE – The flow of traffic is enabled.
Default: DISABLE
VC Type Selects the type of VC used to carry the The available selections are VC-12, VC-3 and
corresponding virtually concatenated group. VC-4.
This parameter is one of the parameters that Default: VC-12
determine the bandwidth made available to
the virtually concatenated group
LCAS Used to enable/disable use of the Link NO – The use of LCAS is disabled.
Capacity Adjustment Scheme (LCAS) on the YES – The use of LCAS is enabled.
corresponding group.
Default: NO
LCAS is relevant only when the group includes
2 or more VCs, and therefore it is not
displayed when selecting VC-4 for the VC Type
Number of VCs Selects the number of VCs of the type The available range for each type are as
selected by VC Type used to carry the follows:
corresponding virtually concatenated group. • For VC-12: 1 to 63
This is another parameter that determines • For VC-3: 1, 2 or 3. The number that can
the bandwidth made available to the virtually be selected also depends on the mapping
concatenated group. of lower-order VCs assigned to other
When you select the All VCGs option, take groups: any groups using lower-order VCs
into consideration that the number selected must be mapped in a way that leaves one
by you is allocated to each active virtually or two whole VC-3s free.
concatenated group. When selecting VC-4 for • For VC-4: 1.
VC Type, the number is always 1
Default: 1
Encapsulation Selects the encapsulation standard used by LAPS – Link Access Procedure for SONET/SDH
the virtually concatenated group protocols per ITU-T Rec. X.85/X.86 draft.
GFP – Generic Framing Procedure in
accordance with ITU-T Rec. G.7041, framed
mode. See configuration instructions in the
Using GFP Encapsulation for Virtually
Concatenated Groups on SDH Links section
starting on page 4-120.
Default: GFP

Virtual Used to enable/disable the use of the virtual NO – The use of the virtual concatenation
Concatenation concatenation format when the number of format is disabled.
VCs in the group is 1. YES – The use of the virtual concatenation
This parameter is displayed only when 1 is format is enabled. This selection is necessary
selected in the Number of VCs field. This only for compatibility with equipment from
parameter is not displayed when selecting other vendors.
VC-4 for VC Type Default: YES
Minimum Selects the minimum allowed number of The allowed range is 1 to 63 for VC-12, and 1
Number of VCs operational VCs that must remain in to 3 for VC-3.
operation. If the number decreases below the Make sure to select a number not exceeding
selected value, an alarm is generated. the specified Number of VCs.
This parameter is displayed only when LCAS is Default: 1
enabled. This parameter is not displayed
when selecting VC-4 for VC Type
User Name Used to enter a logical name for the selected Up to 15 characters.
group Default: Empty string
Redundancy Controls the use of 1+1 redundancy for the NONE – No redundancy.
selected virtually concatenated group 1+1 – 1+1 redundancy is enabled. See the
Configuring Virtually Concatenated Group
Redundancy section for details.
Default: NONE
LVC Used to configure the parameters of the LVC See procedure below
Configuration used to transport the group payload. This
parameter is not displayed when selecting
VC-4 for VC Type
LAPS Used to configure the LAPS encapsulation See Table 4-33

Configuration parameters
³ To configure the LVC parameters of a virtually concatenated group (or groups):

1. Select LVC Configuration. A typical LVC Configuration screen showing the
default values for groups using VC-12 is shown in Figure 4-92; Figure 4-93
shows the screen for groups using VC-3. The parameters that can be
configured by means of the LVC Configuration screen are described in the
following tables:
• For groups using VC-12: Table 4-31
• For groups using VC-3: Table 4-32.
2. Type the desired item number and then press <Enter>:
• For items 1, 3, 7, 8, the selection is toggled as soon as you press <Enter>.
• For items 2 and 6, you can type the desired value in the same line. When
done, press <Enter>.

• For the other items, you will see the corresponding selection screen. In this
case, the Values column in Table 4-31 or Table 4-32 lists the options
displayed on the selection screen.
On the selection screen, type the number of the desired option and then
press <Enter>. The selection screen closes and the new value appears in
the LVC Configuration screen.
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>LVC Configuration

3. Padding (Nulls)
6. Extended Signal Label[0 - ff]... (0D)
7. RDI on payload label (Disable)
>

-----------------------------------------------------------------------------
Figure 4-92. Typical LVC Configuration Screen for Virtually Concatenated Groups Using VC-12
MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 3>LVC Configuration

3. Padding (Nulls)
6. Payload Label [0 - ff]... (1B)
7. RDI on payload label (Disable)
>

-----------------------------------------------------------------------------
Figure 4-93. Typical VC Configuration Screen for Virtually Concatenated Groups Using VC-3

Table 4-31. Configuration>VCG>LVC Configuration Parameters for VC Type – VC-12
group
Default: DISABLE
J2 Path Trace Specifies the path trace label. Alphanumeric string of 15 characters. If not all of
This parameter is relevant only when J2 the 15 characters are needed for the prescribed
Rx Path Trace is enabled label, make sure to specify the appropriate
Padding method.
Padding Selects the type of characters used to NULLS – NULL characters.

pad the path trace label, when it is SPACES – Space characters.
shorter than the required length of 15
Default: NULLS
characters
EED Threshold Selects the BER value, which if exceeded The available selections are 1E-3 (BER threshold
results in the generation of the error of 10-3), 1E-4 (10-4), 1E-5 (10-5).
rate degradation alarm for the Default: 1E-3 (BER of 10-3)
corresponding group
SD Threshold Selects the BER value, which if exceeded The available selections are 1E-6 (BER threshold
results in the generation of the of 10-6), 1E-7 (10-7), 1E-8 (10-8) or 1E-9 (10-9).
signal-degraded alarm for the Default: 1E-6 (BER of 10-6)
corresponding group
Payload label Specifies the expected payload label Hexadecimal number in the range of 0 to FF (two
(one byte) digits).
Default: 0D for groups with a single VC-12
(Virtual Concatenation=YES)
05 for other (Virtual Concatenation=NO)
Extended Signal Selects the extended payload label, Two hexadecimal digits, in the range of 00 to FF.
Label which is part of the SDH overhead when Default: 0D
virtual concatenation is used.
The default value, 0D, is the standard
value used to indicate the use of virtual
concatenation and therefore should not
be changed unless specifically required.
the value selected in the Number of VCs
field is different from 1; if the value is 1,
the parameter is displayed only when
the Virtual Concatenation field is YES
RDI on Payload Controls the sending of RDI indications ENABLE – RDI is sent when a payload label
Label by the corresponding group, in case the mismatch is detected.
received payload label is different from DISABLE – RDI is not sent when payload label
the expected payload label mismatch is detected. Nevertheless, RDI is still
sent in case of LOP (loss of pointer) condition.
Default: DISABLE

RDI on Path Controls the sending of RDI indications ENABLE – RDI is sent in case a path trace
Trace by the corresponding group, in case the mismatch is detected.
received path trace label (carried in SDH DISABLE – RDI is not sent when a path trace
overhead byte J2) is different from the mismatch is detected. Nevertheless, RDI is still
expected path trace label sent in case a LOP (loss of pointer) condition is
detected.
Default: DISABLE
Table 4-32. Configuration>VCG>LVC Configuration Parameters for VC Type – VC-3
group Default: DISABLE
J1 Path Trace Specifies the path trace label Alphanumeric string of 15 characters. If not all of
the 15 characters are needed for the prescribed
label, make sure to specify the appropriate
Padding method.
Padding See Table 4-31
EED Threshold See Table 4-31
SD Threshold See Table 4-31
Payload Label See Table 4-31
Extended Signal See Table 4-31 Default: 1B

Label
RDI on Payload See Table 4-31

Label
RDI on Path Controls the sending of RDI indications ENABLE – RDI is sent in case a path trace
Trace by the corresponding group, in case the mismatch is detected.
received path trace label (carried in SDH DISABLE – RDI is not sent when a path trace
overhead byte J1) is different from the mismatch is detected. Nevertheless, RDI is still
expected path trace label sent in case a LOP (loss of pointer) condition is
detected.
Default: DISABLE
³ To configure the LAPS parameters:

1. Select LAPS Configuration. A typical LAPS Configuration screen is shown in
Figure 4-94.

MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>LAPS Configuration
1. Address [0 - ff] ... (00)

2. Control [0 - ff] ... (00)
3. SAPI value [0 - ffff]... (0030)
>

-----------------------------------------------------------------------------
Figure 4-94. Typical LAPS Configuration Screen

2. The parameters displayed on the LAPS Configuration screen are explained in
Table 4-33.
Note Any changes to the default values should be carefully considered, to ensure
compatibility with other equipment.
Table 4-33. LAPS Configuration Parameters
Address Selects the HDLC address to be used by the Two hexadecimal digits, in the range of 00
LAPS protocol for handshaking. to FF.
The standardized HDLC address for Ethernet Default: 00
encapsulated with LAPS is 4
Control Selects the HDLC control address to be used Two hexadecimal digits, in the range of 00
by the LAPS protocol for handshaking. to FF.
The standardized HDLC control value for Default: 00
Ethernet encapsulated with LAPS is 3
SAPI Value Selects the service access point identifier Four hexadecimal digits, in the range of
(SAPI) for the LAPS protocol. 0000 to FFFF.
The standardized SAPI for the Ethernet MAC Default: 0030
is FE01

Using GFP Encapsulation for Virtually Concatenated Groups on SDH

Links
A typical individual VCG screen for a Megaplex-4100 with SDH link that uses GFP
encapsulation is shown in Figure 4-95.
MP-4100

2. VC type > (VC12)
3. LCAS (No)
4. Number of VCs [1 - 63] ... (3)
5. Encapsulation > (GFP)
6. User Name ... ()
7. Redundancy (None)
9. GFP Configuration >
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-95. Typical VCG Configuration Screen for GFP Encapsulation

The selected group is identified in the screen header. When you select All VCGs,
the header is All VCGs.
The parameters that can be configured by means of the VCG configuration screen
are the same as described in Table 4-30 for LAPS encapsulation, except that the
LAPS Configuration item is replaced by the GFP Configuration item, used to
configure the GFP encapsulation parameters.
³ To configure the GFP configuration parameters:

1. Select GFP Configuration. A typical GFP Configuration screen is shown in
Figure 4-96.

MP-4100
Configuration>Logical Layer>CL>VCAT>CL-A>VCG 1>GFP Configuration
1. FCS (Yes)
2. PTI For Client Data[0 - 8] ... (0)
3. UPI For Client Data[1 - 255] ... (1)
4. Delta [1 - 7] ... (1)
5. Core Scrambling > (Both Side)
6. Payload Scrambling > (Both Side)
>

-----------------------------------------------------------------------------
Figure 4-96. Typical GFP Configuration Screen

2. The parameters displayed on the GFP Configuration screen are explained in
Table 4-34.
Note Any changes to the default values should be carefully considered, to ensure
compatibility with other equipment.
Table 4-34. GFP Configuration Parameters
FCS Controls the use of error detection for NO – Payload error detection disabled.
the payload YES – Payload error detection enabled. In this case,
a frame checksum is calculated, using the 32-bit
polynomial recommended by ITU-T, and added to
the GFP frame structure.
Default: YES
PTI For Client Selects the payload type identifier (PTI) The allowed range is 0 to 8.
Data inserted in GFP frames Default: 0 (user data)
UPI For Client Selects the user payload identifier (PTI) The allowed range is 0 to 255.
Data inserted in GFP frames Default: 1 (frame-mapped Ethernet)
Delta Selects the number of error-free frame The allowed range is 1 to 7.

headers that must be received before Default: 1
frame synchronization is declared

Core Controls the use of frame core data BOTH SIDES – Core scrambling enabled for both the
Scrambling scrambling transmit and receive directions.
ONLY TRANSMIT – Core scrambling performed only
on transmitted frames. No descrambling performed
on the received core data.
ONLY RECEIVE – Core descrambling performed on
the received core data. No scrambling for the core
data inserted in the transmitted frames.
DISABLED – Core scrambling disabled for both the
transmit and receive directions.
Default: BOTH SIDES
Payload Controls the use of payload data BOTH SIDES – Payload scrambling enabled for both
Scrambling scrambling, before insertion in frames the transmit and receive directions.
ONLY TRANSMIT – Payload scrambling performed
only on transmitted frames. No descrambling
performed on the received payload.
ONLY RECEIVE – Payload descrambling performed on
the received core data. No scrambling for the
payload inserted in the transmitted frames.
DISABLED – Payload scrambling disabled for both
the transmit and receive directions.
Default: BOTH SIDES
Configuring Virtually Concatenated Group Redundancy

This section provides instructions for configuring redundancy for pairs of virtually
concatenated groups. The same procedures can be used for any pair of virtually
concatenated groups, even if they use different concatenation parameters.
The following screens provide configuration examples for virtually concatenated
groups using GFP encapsulation over SDH links, however the same configuration
procedures are used for other combinations of parameters, and for SONET links.
³ To configure virtually concatenated group redundancy:
Note When configuring the redundancy parameters, always start from the virtually
concatenated group that is to serve as the primary port of the pair.
If you must reconfigure the redundancy partners, it is recommended to first
select Redundancy = NONE for the current primary port, and then reconfigure all
the redundancy parameters.
1. On the virtually concatenated group selection screen (Figure 4-90), select the
virtually concatenated group that will serve as the primary port of the
redundancy pair.
2. On the virtually concatenated group configuration screen, select Redundancy,
and then select 1+1 to enable redundancy. The screen changes to display the

additional parameters related to redundancy, and a Primary (Yes) indicator

appears at the top of the screen.
3. Configure the primary virtually concatenated group redundancy parameters in
accordance with the information appearing in Table 4-35, in accordance with
the encapsulation method in use. A typical screen, with all the redundancy-
related parameters, comprising two pages, is shown in Figure 4-97.
MP-4100
Primary > (Yes)

2. VC type > (VC12)
3. LCAS (Yes)
4. Number of VCs [1 - 63] ... (3)
6. Minimum Number Of VCs[1 - 63]... (1)
7. User Name ... ()
8. Redundancy (1+1)
9. Revertive (Yes)
10. Wait To Restore[0 - 999] ... (300)
... (N)
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
A. First Page
MP-4100
... (P)
11. Redundancy Slot > (CL-A )
12. Redundancy Port > (VCG 3)
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
B. Second Page
Figure 4-97. Typical Screen for the Primary Virtually Concatenated Group of a Redundancy Pair
(GFP Encapsulation)

Note The other port, which is specified in the Redundancy Slot and Redundancy
Channel fields of the primary port, is automatically configured with compatible
parameters, and only the remaining parameters can be configured manually.
4. At this stage, configure the remaining parameters of the other virtually

concatenated group (the secondary port of the redundancy pair). A typical
screen with all the redundancy-related parameters for the secondary virtually
concatenated group, comprising two pages, is shown in Figure 4-98.
MP-4100
Admin Status (Up)

Redundancy (1+1)
Primary > (No)
Revertive (Yes)
Wait To Restore[0 - 999] ... (300)
Redundancy Slot > (CL-A )
Redundancy Port > (VCG 1)
1. VC type > (VC12)
2. LCAS (No)
3. Number of VCs [1 - 63] ... (1)
... (N)
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
A. First Page
MP-4100
... (P)
5. User Name ... ()
6. Virtual Concatenation (Yes)
>
#-Db Undo; $-Sanity

-----------------------------------------------------------------------------
B. Second Page
Figure 4-98. Typical Screen for the Secondary Virtually Concatenated Group of a Redundancy Pair
(GFP Encapsulation)

Table 4-35. Virtually Concatenated Group Redundancy Configuration Parameters
Revertive Selects the protection mode. NO – Switching is non-revertive, that is, the
This parameter is not displayed when Megaplex-4100 will not flip back to the primary
Redundancy is NONE VCG after the failed VCG returns to normal
operation, but only when the currently used VCG
fails.
YES – Switching is revertive: the Megaplex-4100
will automatically return to the original VCG when
it returns to normal operation.
Default: NO
Therefore, Megaplex-4100 starts
evaluating the criteria for redundancy
switching (flipping) only after this
interval expires. This ensures that
another flipping cannot occur before the
specified interval expires.
Redundancy is NONE
Redundancy Slot Selects the slot in which the other You can select either the same CL slot, or the
module of a virtually concatenated other CL slot (provided a CL module with
group redundancy pair is installed. available virtually concatenated groups is
The selection must always be programmed in the other slot).
symmetrical. Default: Same CL slot
Redundancy is NONE
Redundancy Port Selects the other VCG of a redundancy The available selections depend the virtually
pair. concatenated groups available on the module
The selection must always be selected by means of the Redundancy Slot
symmetrical. parameter.
This parameter is not displayed when Default: – (None)

Redundancy is NONE
Configuring VCG Parameters for Virtually Concatenated Groups on

SONET Links
This section covers the virtually concatenated group configuration activities
available when the Megaplex-4100 uses the SONET links.
For operating instructions and configuration guidelines, see Using LAPS
Encapsulation for Virtually Concatenated Groups on SDH Links and Using GFP
Encapsulation for Virtually Concatenated Groups on SDH Links sections,
respectively, except for the differences listed below, which also depend on the
encapsulation method used on the group (or groups) being configured: LCAS or
GFP:

• A typical individual VCG screen for a Megaplex-4100 with SONET links that
uses GFP encapsulation over VT1.5 SPEs is shown in Figure 4-99. The
selected group is identified in the screen header.
The screen is similar to that of a Megaplex-4100 with SDH links, except for
the following differences:
• VC Type is replaced by VT Type, and the available selections are as follows:
STS1/SPE – STS-1 SPE
VT1.5 – VT1.5 virtual tributary. This is the default selection.
• Number of VCs: the available selections are as follows:
For STS-1 SPEs: 1, 2 or 3
For VT1.5: 1 to 64.
MP-4100

2. VC Type > (VT1.5)
3. LCAS (Yes)
4. Number of VTs [1 - 64] ... (4)
7. User Name ... ()
>

-----------------------------------------------------------------------------
Figure 4-99. Typical VCG Configuration Screen (GFP Encapsulation on SONET Link)
• A typical individual VCG screen for a Megaplex-4100 with SONET links that
uses LAPS encapsulation is shown in Figure 4-100. The difference, relative
to the screen of Figure 4-99 is that the GFP Configuration item is replaced
by the LAPS Configuration item, used to configure the GFP encapsulation
parameters.

MP-4100

2. VC type > (VT1.5)
3. LCAS (Yes)
4. Number of VTs [1 - 64] ... (4)
5. Encapsulation > (LAPS)
7. User Name ... ()
9. LAPS Configuration >
>

-----------------------------------------------------------------------------
Figure 4-100. Typical VCG Configuration Screen (LAPS Encapsulation on SONET Link)
Configuring Ethernet Flows

After performing the configuration activities listed above, you can configure the
Ethernet services flows.
Two types of flows can be configured:
• Traffic flows
• Management flows.
For background information, refer to the Megaplex-4100 Ethernet Services
section in Chapter 1.
Traffic Flow Configuration Guidelines

The maximum number of traffic flows that can be defined on a Megaplex-4100 is
250 (an additional flow, assigned the identifier 251, can be configured for
management only). The following configuration rules apply to flows and bridge
ports:
1. A bridge port can terminate either only traffic flows from local ports, or only
traffic flows from other modules.
2. A bridge port can terminate only one traffic flow classified as unaware (i.e.,
which does not discriminate Ethernet traffic in accordance with customer’s and
service provider’s VLANs).
3. When a bridge port is mapped to more than one traffic flow, the bridge port
can terminate several traffic flows with specific VLAN IDs, but only one traffic
flow classified as unaware.
4. A bridge port can terminate any number of traffic flows with specific VLAN IDs

5. An I/O module can be configured to support either E-line flows, or E-LAN flows,
but not both.
Note The current Megaplex-4100 version does not support E-LAN flows.
6. It is not possible to configure flows between Ethernet ports on the same I/O
module.
7. For E-line flows, the following VLAN assignment rules apply:
• The bridge ports terminating a flow must use the same VLAN mode (either
unaware or aware).
• When using the aware mode, the same VLAN IDs must be configured at
both bridge ports. For example, this means that flows between two GbE
bridge ports must use the same SP-VLAN ID.
Traffic Flow Configuration Procedure
³ To add a new traffic flow:

1. On the Configuration>Applications menu, select Ethernet Services.
2. On the Ethernet Services screen, select Flows.
You will see the traffic flow configuration screen. A typical screen is shown in
Figure 4-101. If no flow is yet defined, it is always necessary to add a new
flow.
If traffic flows are already defined, the screen displays the first flow, and its
parameters. However, if you have already configured a flow in the current
management session, the screen displays the last configured flow.
MP-4100
Configuration>Applications>Ethernet Services>Flows
1. Flow[1 - 250] ... (2)

2. User Name ... ()
3. Flow Type > (E-LINE)
4. Bridge Port Mapping[]>
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
Figure 4-101. Typical Traffic Flow Configuration Screen

3. Type A (Add) to add a new flow. The flow is automatically assigned the next
free index number. The maximum allowed is 250: to free up index numbers,
delete an unnecessary traffic flow entry, or edit an unused flow.

Note If flows are already configured, you can also select an existing flow number to
modify or delete. You can select directly the flow number, or press F or B to scroll
among the existing flows.
4. Select the traffic flow type as E-LINE.

5. Assign a logical name to the traffic flow by selecting User Name: you can enter
up to 25 alphanumeric characters. When done, press <Enter>.
³ To map bridge ports to the traffic flow:

1. To map bridge ports to the selected flow (either a new one, or an existing flow
that is being modified), select Bridge Port Mapping in Figure 4-101.
2. The Bridge Port Mapping screen is displayed.
A typical screen is shown in Figure 4-102. If no bridge port has been mapped
to the selected flow, the screen is empty.
If the screen displays data for an already configured flow (see for example
Figure 4-105), you can change some of the flow parameters, for example,
C-VLAN Type, by bringing the cursor to the desired field: the available options
are then displayed under the list of the bridge ports.
Note For E-Line flows, you must configure exactly two bridge ports.
MP-4100
...ration>Applications>Ethernet Services>Flows>Bridge Port Mapping-Flow3
>
A-Add;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow

-----------------------------------------------------------------------------
Figure 4-102. Typical Bridge Port Mapping Screen for Traffic Flow (Before Configuration)
3. On the Bridge Port Mapping screen, type A (Add) to add a new bridge port.
4. You will see the bridge port mapping data form. A typical screen with the
default values is shown in Figure 4-103.

MP-4100
BP[1 - 512] ... (351)

1. C-VLAN Type > (Unaware)
C-VLAN ID[1 - 4094] ... (0)
2. SP-VLAN[0 - 4094] ... (0)
3. Slot > (CL-A)
Port > (VCG 1)
Rate > (6.3Mbps)
BP User Name ... ()
>
#-Db Undo; F-Fwd; B-Bkwd; S-Save

-----------------------------------------------------------------------------
Figure 4-103. Typical Bridge Port Mapping Data Form for Traffic Flow
5. Start by selecting an available bridge port, by pressing F or B: the Slot and Port
fields are automatically scrolled to display the available bridge ports.
• The Slot field displays only slots of modules on which bridge ports are still
available.
• The Port field displays the port type (link, Ethernet or GbE port, bundle, or
virtually concatenated group (VCG)), followed by its index number on the
selected slot. Bridge ports that are already not available are automatically
skipped as you configure flows, for example:
1. Any bridge port configured as VLAN-unaware in one flow cannot be
reused in another flow. A sanity error message will be generated if
you try including the same bridge port in another flow.
2. When a GbE port or VCG is included in a redundancy pair, only the
primary port or VCG can be selected (the secondary port/VCG cannot
be independently used, it only serves as standby for the primary
port/VCG traffic)
3. The maximum number of traffic flows allowed on a GbE port of a CL
module is 250, the same maximum as for the whole Megaplex-4100,
and therefore after reaching this number, no more flows can be
added.
Alternatively, select manually the desired Slot number, and scroll the bridge
ports available on the selected module.
6. Select the prescribed flow parameters, taking into consideration the
configuration guidelines presented on page 4-127. Table 4-36 lists the
available parameters. The fields displayed on the screen automatically adjust to
the selected values.

Table 4-36. Traffic Flow Bridge Port Mapping Parameters
BP Displays the internal index number of The available range is 1 to 512.

the bridge port being defined. The Default: 1
port number is automatically assigned
by the Megaplex-4100 management
subsystem.
The index number indicates the
location and type of the bridge port
for the internal processor, and
therefore it changes when you make
changes to the Slot field
C-VLAN Type Specifies the classification method for The selection is made on a submenu with the
customer’s edge traffic arriving at the following options:
selected bridge port AWARE – Only frames with the VLAN ID selected
in the C-VLAN ID field are accepted by this
bridge port.
UNAWARE – All frames are accepted.
Default: UNAWARE
C-VLAN ID Specifies the VLAN ID accepted when The allowed range is 1 to 4094. The selected
the C-VLAN Type is AWARE. VLAN ID must be unique per bridge port, but can
This field can be modified only when be reused on different bridge ports.
C-VLAN Type is AWARE 0 means that no VLAN ID has been selected (this
is also the only value displayed when C-VLAN
Type is UNAWARE).
Default: 1
SP-VLAN Specifies the service provider’s edge The allowed range is 1 to 4094. The selected
VLAN ID for the traffic at the selected VLAN ID must be unique per Megaplex-4100 GbE
bridge port ports.
0 means that no VLAN ID has been selected but
you should not use this value.
Default: 0
Slot Selects the number of the slot on The allowed range is I/O 1 to I/O 10, CL-A and
which the selected bridge port is CL-B.
defined Only slots on which bridge ports are available for
connection to the selected flow are displayed
Port Displays the port on which the The allowed port types include Ethernet ports
selected bridge port is defined (ETH or GbE), bundles (Bnd), and virtually
concatenated groups (VCG), as available on the
selected slot.
Only bridge port types available for connection
to the selected flow are displayed

Rate Displays the nominal bandwidth The actual data rate is as configured for the
assigned to the bridge port selected bridge port, for example:
• 128 to 1920 kbps for an HDLC bundle on a
framed E1 port, 128 to 1536 kbps for an
HDLC bundle on a framed T1 port, and
2048 kbps for an HDLC bundle on an
unframed E1 port.
• For an MLPPP bundle: multiples of 2048 kbps
in the range of 2048 kbps (1 × 2048 kbps) to
16384 kbps (8 × 2048 kbps)
• 100 Mbps for Ethernet (ETH) ports
• 1000 Mbps for GbE ports
• Virtually concatenated groups can provide
any bandwidth from one VC-12 or VT1.5, up
to the whole SDH/SONET port bandwidth
(155 Mbps)
BP User Name Displays the logical name for the port Up to 25 alphanumeric characters.
indicated by the Slot and Port fields Default: Empty string
7. When you select a bridge port, you can check whether it is already included in
a flow, together with the flow details, by pressing U. Figure 4-104 displays a
typical bridge port information screen (the selected bridge port index number
appears in the header).
Press <ESC> to close the bridge port information form and return to the
bridge port configuration screen.
MP-4100
...tion>Applications>Ethernet Services>Flows>Bridge Port Mapping>

2 1 12
>
#-Db Undo
-----------------------------------------------------------------------------
Figure 4-104. Typical Bridge Port Information Form for Traffic Flow
8. After ending the mapping of the first bridge port, press <ESC> to return to the
Bridge Port Mapping screen, which now displays the mapped bridge port.
9. Repeat the bridge port mapping process for the second bridge port of the
E-line flow being configured. Typical Bridge Port Mapping screens as seen after
configuration is ended, are shown in Figure 4-105.

MP-4100

351 Aware 1 12 CL-A VCG 1 6.3Mbps
359 Aware 1 12 CL-A GbE 1 1Gbps
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow

-----------------------------------------------------------------------------
A. Typical Traffic Flow between GbE Port and Virtually Concatenated Group
MP-4100

68 Unaware 0 0 IO-2 ETH 1 100Mbps
36 Unaware 0 0 IO-2 Bnd 1 6144Kbps
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd; U-BP-Flow

-----------------------------------------------------------------------------
B. Typical Traffic Flow between Ethernet Port and MLPPP Bundle

Figure 4-105. Typical Bridge Port Mapping Screen (After Traffic Flow Configuration)
Management Flow Configuration Procedure

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, through
virtually concatenated groups, or through bundles carrying Ethernet traffic
(including MLPPP bundles).
To control the flow of Ethernet inband management traffic within Megaplex-4100
and enable its distribution, through the Megaplex-4100 ports, to other
equipment, it is necessary to configure a dedicated management flow, which is
always assigned the flow identifier 251. In addition to selecting the bridge ports
connected to the management flow, when the same management traffic can be
received through more than one bridge port, it is also necessary to specify which
bridge ports may accept management traffic from network management stations
(such ports are referred to as host NMS sources). If management communication
through the currently selected port fails, another port is automatically selected.

When selecting host NMS source ports, make sure to plan ahead how to avoid
forming loops in the Ethernet communication topology.
Note The traffic flow configuration rules listed in the Traffic Flow Configuration
Guidelines section on page 4-127 also apply to the management flow.
³ To configure the management flow:

1. On the Configuration>System>Management menu, select Flow.
You will see the management flow configuration screen. A typical screen, as
seen before a flow is configured, is shown in Figure 4-106. If no flow is yet
defined, it is always necessary to add this flow.
MP-4100
Configuration>System>Management>Flow
>
%-Db Update; #-Db Undo; $-Sanity; A-Add

-----------------------------------------------------------------------------
Figure 4-106. New Management Flow Configuration Screen

2. Type A (Add) to add the new flow. The flow is automatically assigned the index
number 251.
MP-4100
Configuration>System>Management>Flow
Flow > (251)

1. User Name ... ()
2. VLAN ID[1 - 4094] ... (1)
3. VLAN Priority Tag[0 - 7]... (0)
4. Bridge Port Mapping []>
>
%-Db Update; #-Db Undo; $-Sanity; D-Delete

-----------------------------------------------------------------------------
Figure 4-107. Typical Management Flow Configuration – Add Screen

3. Assign a logical name to the management flow by selecting User Name: you
can enter up to 25 alphanumeric characters. When done, press <Enter>.
4. Select VLAN ID, and specify the management VLAN number (in the range of 1
to 4094).
5. Select VLAN Priority Tag, and then specify the priority of the management
VLAN traffic, in the range of 1 to 7, where 1 is the lowest priority. For
wideband ports, you may increase the priority, however, in general you should
leave the default priority, 1, unchanged.
³ To map bridge ports to the management flow:

1. To map bridge ports to the selected management flow (either a new one, or an
existing flow that is being modified), select Bridge Port Mapping in Figure 4-
107.
2. The Bridge Port Mapping screen is displayed. A typical screen is shown in
Figure 4-108.
• If no bridge port has been mapped to the selected flow, the screen is
empty.
• If the flow already includes bridge ports, you can remove an existing bridge
port by bringing the cursor to the desired row and typing R (you cannot
change parameters for an existing bridge port, but can remove it from the
flow and then configure a new one as required).
MP-4100
Configuration>System>Management>Flow>Bridge Port Mapping-Flow251
BP Host NMS Source Slot Port Rate BP User Name
>
A-Add;%-Db Update; #-Db Undo; $-Sanity

-----------------------------------------------------------------------------
Figure 4-108. Typical Bridge Port Mapping Screen for Management Flow (Before Configuration)
3. On the Bridge Port Mapping screen, type A (Add) to add a new bridge port.
4. You will see the bridge port mapping data form. A typical screen with the
default values is shown in Figure 4-103.
Table 4-37 lists the available parameters. The fields displayed on the screen
automatically adjust to the selected values.

MP-4100
BP[1 - 512] ... (1)

1. Host NMS Source > (Yes)
2. Slot > (IO-1)
Port > (Bnd 1)
Rate > (6144Kbps)
BP User Name ... ()
>
#-Db Undo; F-Fwd; B-Bkwd; S-Save

-----------------------------------------------------------------------------
Figure 4-109. Typical Bridge Port Mapping Data Form for Management Flow
5. Start by selecting an available bridge port, by pressing F or B: the Slot and Port
fields are automatically scrolled to display the bridge ports available for
connection to the management flow.
• The Slot field displays only slots of modules on which bridge ports are still
available.
• The Port field displays the port type, and its index number on the selected
slot. The available port types are Ethernet ports and bundles (HDLC and
MLPPP) on I/O modules, GbE ports and virtually concatenated groups on CL
modules, Bridge ports that are already not available are automatically
skipped as you configure flows.
Alternatively, select manually the desired Slot number, and scroll the bridge
ports available on the selected module.
6. Select Host NMS Source, and select Yes if you want to allow reception of
management traffic from the NMS through this port.
Table 4-37. Management Flow Bridge Port Mapping Parameters
BP Displays the internal index number of The available range is 1 to 512.

the bridge port being defined. The Default: 1
port number is automatically assigned
by the Megaplex-4100 management
subsystem.
The index number indicates the
location and type of the bridge port
for the internal processor, and
therefore it changes when you make
changes to the Slot field

Host NMS Source Specifies whether Megaplex-4100 NO – Megaplex-4100 management subsystem

management subsystem may access will not accept management traffic from the
management traffic from the NMS NMS through this port.
through this port YES - Megaplex-4100 management subsystem
can accept management traffic from the NMS
through this port. However, the port that is
actually used to communicate with the NMS is
automatically by the management subsystem.
Default: NO
Slot Selects the number of the slot on The allowed range is I/O 1 to I/O 10, CL-A and
which the selected bridge port is CL-B.
defined Only slots on which bridge ports are available for
connection to the management flow are
displayed
Port Displays the port on which the The allowed port types include Ethernet ports
selected bridge port is defined (ETH or GbE), bundles (Bnd), and virtually
concatenated groups (VCG), as available on the
selected slot.
Only bridge port types available for connection
to the management flow are displayed
Rate Displays the nominal bandwidth The actual data rate is as configured for the
assigned to the bridge port selected bridge port, for example:
• 128 to 1920 kbps for an HDLC bundle on a
framed E1 port, 128 to 1536 kbps for an
HDLC bundle on a framed T1 port, and
2048 kbps for an HDLC bundle on an
unframed E1 port.
• For an MLPPP bundle: multiples of 2048 kbps
in the range of 2048 kbps (1 × 2048 kbps) to
16384 kbps (8 × 2048 kbps)
• 100 Mbps for Ethernet (ETH) ports
• 1000 Mbps for GbE ports
• Virtually concatenated groups can provide
any bandwidth from one VC-12 or VT1.5, up
to the whole SDH/SONET port bandwidth
(155 Mbps)
BP User Name Displays the logical name for the port Up to 25 alphanumeric characters.
indicated by the Slot and Port fields Default: Empty string
7. After ending the mapping of the first bridge port, press <ESC> to return to the
Bridge Port Mapping screen, which now displays the mapped bridge port.
8. Repeat the bridge port mapping process for the other bridge ports to be
connected to the management flow. A typical Bridge Port Mapping screen, as
seen after configuration is ended, is shown in Figure 4-105.

MP-4100
BP Host NMS Source Slot Port Rate BP User Name

1 Yes IO-1 Bnd 1 6144Kbps
359 No CL-A GbE 1 1Gbps
379 Yes CL-B GbE 1 1Gbps
351 No CL-A VCG 1 6.3Mbps
34 No IO-1 ETH 2 100Mbps
>
A-Add;R-Remove;%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
Figure 4-110. Typical Management Flow Bridge Port Mapping Screen (After Management Flow
Configuration)
Configuring APS for SDH/SONET Links

The APS function is used to select the protection mode for the network
STM-1/OC-3 connection. This option is relevant only for Megaplex-4100 with
For details on the APS function, see the Redundancy Options section in
Chapter 1.
Currently, two options are supported:
• No protection. In this case, each link operates independently.
• 1+1 uni-directional protection with automatic switching (Yes). In this mode,
one CL.1/155 or CL.1/155GbE link serves as backup for the working link.
APS is configured by selecting an APS (Automatic Protection Switching) group
that includes the appropriate CL.1/155 or CL.1/155GbE ports.
For a Megaplex-4100 with two CL.1/155 or CL.1/155GbE modules, there are four
APS group options, and two groups can be active at the same time, provided they
are defined on different pairs of ports.
The recovery mode (revertive or non-revertive), and the restoration time in the
revertive mode, can be selected in accordance with the application requirements.
Note
After adding an APS protection group without enabling the protection (Protection
is NO), the APS group operates in the forced mode, that is, the working port of
the APS group selected on the screen is forced to be the active port.
To navigate to the required screen, use Configuration>System>APS.

Typical APS group configuration screens are shown in Figure 4-111 and
Figure 4-112. The configuration parameters appearing on these screens are
MP-4100
Configuration>System>APS
1. APS Group Id > (A1-A2)

2. Protection (No)
3. Working Port > (CL-A Link 1)
4. Flip Upon SD (No)
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete

-----------------------------------------------------------------------------
Figure 4-111. Typical APS Group Configuration Screen with Protection Disabled
MP-4100
Configuration>System>APS
1. APS Group Id > (B1-B2)

2. Protection (Yes)
3. Revertive (Yes)
4. Working Port > (CL-B Link 1)
5. Protection Port > (CL-B Link 2)
6. WTR time(Sec)[1 - 720] ... (60)
7. Flip Upon SD (No)
>
%-Db Update; #-Db Undo; $-Sanity; A-Add; D-Delete

-----------------------------------------------------------------------------
Figure 4-112. Typical APS Group Configuration Screen with Protection Enabled
Table 4-38. APS Configuration Parameters
APS Group ID Selects the CL links configured as an A1-A2 – Link 1 of CL A with link 2 of CL A.
APS group B1-B2 – Link 1 of CL B with link 2 of CL B.
A1-B1 – Link 1 of CL A with link 1 of CL B.
A2-B2 – Link 2 of CL A with link 2 of CL B.
Default: A1-A2

Protection Enables/disables the APS function NO – The APS group operates in the forced mode.
YES – MSP 1+1 unidirectional protection with
automatic switching.
Default: YES
Revertive Selects the protection mode NO – Switching is non-revertive, that is, the
Megaplex-4100 will not flip back after the failed link
returns to normal operation, but only when the
currently used link fails.
YES – Switching is revertive: the Megaplex-4100 will
return to the original link when it returns to normal
operation.
Default: NO
Working Port Selects the working link Provides two selections, in accordance with the links
included in the configured APS group.
Default: the first link in the APS group designation
Protection Port Selects the protection link The only option is the other link included in the
configured APS group.
Default: the second link in the APS group designation
WTR Time When protection switching is The supported range is 1 to 720 seconds.
enabled and a link interface Default: 60
becomes active, specifies the time
during which all the alarms reported
by the link will be ignored.
This field is displayed only when the
protection mode is Revertive=YES
Flip Upon SD Controls switching to protection NO – Protection switching on SD condition is

when a signal-degraded (SD) disabled.
condition is detected YES – Protection switching on SD condition is
enabled.
Default: NO
Configuring Timeslot Assignment

The following menus provide a central point of access for configuring the utilization
(assign timeslots) of E1 and T1 ports. This configures the internal routing (DS0
cross-connects) within the Megaplex-4100.
Any type of E1 or T1 port, either internal (virtual) or external, supports timeslot
assignment. For a Megaplex-4100 with CL.1/155 or CL.1/155GbE modules, it is also
possible to assign timeslots on internal (virtual) PDH ports, for transport over the
SDH or SONET network.
Timeslots can also be bypassed among E1 or T1 ports, including between E1 and T1
ports, and SDH or SONET PDH ports.

Note While configuring a specific E1, T1, or PDH port, you can directly access the TS
Assignment facility for the port being configured directly from the
Configuration>Physical Port screen of the port, without going through the
Configuration>System menu.
When starting a timeslot assignment task, first you use a TS Assignment submenu
to select the type of port: module installed in an I/O slot, or CL module, and then
you select a specific port on a module of the corresponding type. Only active
ports using the DS0 cross-connect mode can be selected.
Timeslots can be assigned to TDM ports and channels, to inband management, and
to Ethernet bundles using the HDLC port.
For user ports that do not require a full timeslot (eight bits, equivalent to a
bandwidth of 64 kbps), Megaplex-4100 permits split timeslot assignment, that is,
assignment of individual bits in a selected timeslot. Split timeslot assignment
increases the utilization efficiency of link bandwidth for TDM modules or
channels, because it enables the allocation of link bandwidth in smaller units
(16 kbps, carried by pairs of consecutive bits).
Timeslot assignment is designed to minimize errors:
• The various screens help you avoid assignment errors by presenting only
the relevant types of modules, ports and bundles, and ensuring that at
each stage only free timeslots can be assigned.
• The final assignment is checked for consistency, for example:
• It is checked that a given user port has indeed been assigned all the
timeslots (or bits in a split timeslot) needed to carry its payload, and that
all the timeslots are assigned on the same destination port.
• When timeslots are bypassed between ports, it is checked that the
assignment is symmetrical.
To navigate to the required screen, use Configuration>System>TS Assignment.
³ To select a port:
1. Select TS Assignment on the System menu. A typical TS Assignment submenu is

MP-4100
Configuration>System>TS Assignment
1. IO >
2. CL >
>

-----------------------------------------------------------------------------
Figure 4-113. Typical TS Assignment Submenu

2. Select the type of modules, I/O or CL, and then press <Enter>. For I/O modules,
you will see the slot selection screen, whereas if you select CL you will proceed
directly to the PDH port selection screen (only one set of PDH ports, 63 or 84,
in accordance with the SDH/SONET link framing mode, is available for add/drop
traffic).
A typical screen for selecting an I/O module is shown in Figure 4-114. Only
I/O modules with E1 or T1 ports that are programmed in the chassis appear
on the screen.
MP-4100
Configuration>System>TS Assignment>IO
1. I/O-2 (M8E1)>
2. I/O-3 (M8SL)>
3. I/O-4 (M8T1)>
4. I/O-5 (M8E1)>
5. I/O-6 (M8SL)>
>

-----------------------------------------------------------------------------
Figure 4-114. Typical IO Slot Selection Screen

3. Select a specific module, and then press <Enter> to continue to the port
selection screen. A typical screen for selecting ports on an I/O module is shown
in Figure 4-115; Figure 4-116 shows a typical CL port selection screen. Only
active ports (with Admin Status=UP) using a framed mode appear on the
screen.

Note For CL modules, the port selection screen (reached after selecting CL on the
submenu of Figure 4-113) displays the internal (virtual) PDH ports.
The total number of ports depends on their framing: 63 when the CL module PDH
ports are configured as E1 ports, and 84 when configured as T1 ports. It is not
possible to mix E1 and T1 ports.
MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)
1. Link 1>
2. Link 5>
3. Link 6>
4. Link 8>
>

-----------------------------------------------------------------------------
Figure 4-115. Typical CL Port Selection Screen for I/O Module

MP-4100
Configuration>System>TS Assignment>CL
1. PDH 1(Up) >

2. PDH 2(Up) >
3. PDH 5(Up) >
4. PDH 12(Up) >
5. PDH 21(Up) >
>

-----------------------------------------------------------------------------
Figure 4-116. Typical CL Port Selection Screen

4. Select a specific port, and then press <Enter> to continue to the timeslot
assignment task selection screen. A typical screen is shown in Figure 4-117.
Note If you select an unframed port, you will see a No Map – Unframed Port message.
5. Select the desired task and then press <Enter> to display the corresponding
screen.

MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)>Link 1
1. Display Time Slots []

2. Manual []>
3. Connect Time Slots >
4. Delete TS (Per Slot and Port) >
5. Delete TS (Number Of TS) >
6. Split >
>

-----------------------------------------------------------------------------
Figure 4-117. Typical Timeslot Assignment Task Selection Screen

The following tasks can be selected:
Display Time Slots Display the current timeslot assignment for the selected
port.
Manual Assign or deassign individual timeslots, and configure

timeslots for use with split timeslot assignment. This also
determines the handling of the payload carried by each
timeslot.
Connect Time Slots Assign a group of consecutive timeslots on the selected port
(such a group is also called bundle, but this is not related to
Ethernet bundles).
Delete Time Slots Deassign all the timeslots on a selected port of a specified
(Per Slot and Port) module.
Delete Time Slots Deassign a bundle of timeslots on the current port.

(Number of TS)
Split Assign the individual bits in a timeslot configured to use split

assignments.
³ To display the current timeslot assignment for a selected port:

1. Select Display Time Slots and then press <Enter>. A typical screen is shown in
Figure 4-118.

MP-4100
...System>TS Assignment>IO >I/O-2 (M8E1)>Link 1>Display Time Slots
Ts# 1 2 3 4 5 6 7 8
01:IN01 01:IN02 SPLIT ------ MNG ------ ------ ------
Ts# 9 10 11 12 13 14 15 16
------ ------ ------ ------ ------ ------ ------ ------
Ts# 17 18 19 20 21 22 23 24
------ ------ ------ ------ ------ ------ ------ ------
Ts# 25 26 27 28 29 30 31
------ ------ ------ ------ ------ ------ ------
>

-----------------------------------------------------------------------------
Figure 4-118. Typical Display Time Slots Screen

The screen displays a map of the port timeslots. For E1 ports, the map includes
31 timeslots; for T1 ports, the map includes 24 timeslots.
For each timeslot, you can see its current assignment:
–––– The timeslot is not assigned.
SS:PP The timeslot is assigned to the port PP of the module installed in slot
SS.
MNG The timeslot carries inband management traffic.
SPLIT The timeslot is configured to use split assignment, and its utilization
can be seen by selecting it on the list opened by means of the Split
item on the timeslot assignment task selection screen.
UNI BRD V The timeslot is unidirectionally broadcast to several ports, and is

handled as a voice channel (that is, with channel-associated
signaling).
UNI BRD D The timeslot is unidirectionally broadcast to several ports, and is

handled as a data channel (that is, without channel-associated
signaling).
RESERVED Timeslot reserved for future assignment. Assigning a RESERVED

timeslot has no effect on traffic.
³ To assign individual timeslots:

1. Select Manual on the timeslot assignment task selection screen. A typical

MP-4100
Configuration>System>TS Assignment>IO >I/O-2 (M8E1)>Link 1>Manual
Ts# Slot Port Ts Type

TS 01 IO-1 (HS-U12) IN 1 -- DATA
TS 02 IO-1 (HS-U12) IN 2 -- DATA
| TS 03 Split - -- DATA
v TS 04 IO-1 (HS-U12) IN 34 -- DATA
TS 05 ---- ---- -- MNG
TS 06 IO-2 (M8E1) BND 2 -- DATA
1. ---- 2. Split 3. CL (CL1/155GbE)

... (N)
>

-----------------------------------------------------------------------------
Figure 4-119. Typical Manual Timeslot Assignment Screen

2. The screen displays a table with the following columns. The meaning of the
fields appearing in this table, and the method used to select the desired
values, are explained below:
Ts# The number of the timeslot on the selected port. Each page contains
8 timeslots: to see the additional timeslots, scroll down to the
appropriate page (to see the various navigation options, select the
? (help) option).
The total number of timeslots is 31 for E1 ports, and 24 for T1 ports.
Slot The destination slot, followed by the name of the module

programmed in the corresponding slot.
The destination slot is displayed in a list that appears under the table
when the selection block is within this column. The list includes only
the modules that can be selected as destinations.
You can also select Split, to configure the timeslot for split timeslot
assignment (see page 4-150).
If no slot has been selected, you will see – – – – . Note however that
no slot can be selected when the corresponding timeslot carries
inband management (that is, the timeslot Type is MNG).
Port The destination port, within the selected Slot. The destination port is
displayed in a list that appears under the table when the selection
block is within this column. The list includes only the ports that can
be selected on the module installed in the destination slot, and any
HDLC Ethernet bundle configured on the selected slot.
If no slot or port has been selected, you will see ----. Note however
that no slot can be selected when the corresponding timeslot carries
inband management, nor for Split timeslots.

Ts The destination timeslot on the destination port. This selection is

relevant only when bypassing timeslots between two E1 (or T1)
ports: for other selections, you cannot select a destination timeslot.
Type Selects the type of traffic and the handling of its payload. The
selection is made on a list that appears under the table when the
selection block is within this column. The available types depend on
the destination port.
DATA Data timeslot. This is the default timeslot type. It is

assumed that no signaling information is associated with
a channel carrying data.
DATA is the only allowed selection for bundles.
VOICE Voice timeslot, that is, a timeslot with channel-associated

signaling information. This option is relevant only for E1
ports with G.704 multiframe (G.732S) framing and for T1
ports.
MNG Timeslot dedicated to inband management. If the

selected port is configured for inband management, you
must select one timeslot as management timeslot; if the
port inband management is off, MNG is not available.
Note that only one timeslot of any port can be defined
as management timeslot. Therefore, you can reach MNG
only if all the previous fields have been left empty
(----), and no other timeslot of the current port has
been configured as MNG.
UNI BRD D Unidirectional broadcast timeslot carrying data.
UNI BRD V Unidirectional broadcast timeslot carrying voice.
RESERVED Reserved for future assignment.
3. To assign/deassign a timeslot, move the selection block to the desired Ts# row,
and then move it to each of the columns in this row to select the desired value
as explained in Step 2 above. Note the exceptions for Split and MNG values.
4. Repeat the process for each timeslot.
5. When done, select % to update the database. The timeslot assignment is
automatically checked for validity. If errors are detected, a detailed list of
errors is displayed by the Sanity function. The list identifies omissions, double
assignments and incorrect assignment, for example, channels which require
more timeslots. If the assignment is not correct, it is not possible to update
the database.
³ To assign a bundle of timeslots:

1. Select Connect Time Slots on the timeslot assignment selection screen. You will
see the bundle assignment screen for the selected port. A typical screen is

MP-4100
...ration>System>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Connect Time Slots
1. Start TS[1 - 31] ... (5)

2. Slot > (CL (CL1/155GbE))
3. Port > (PDH 1 )
4. Number of TS[1 - 31]... (6)
5. Type > (DATA)
6. Destination Start TS... (1)
>

-----------------------------------------------------------------------------
Figure 4-120. Typical Connect Time Slots Screen

2. Select Start TS and specify the starting timeslot of the bundle on the selected
port. The range depends on the port type (maximum 31 for an E1 port, and
maximum 24 for a T1 port); you must also take into consideration the number
of timeslots to be connected to the destination port.
3. Select Slot: you will see a selection screen with the list of slots in which
modules that can accept a bundle of timeslots are programmed. When a
CL.1/155 or CL.1/155GbE module is installed, the list also includes the CL slot.
4. Select the desired module (the module type appears next to the chassis slot),
5. Select Port: you will see a selection screen with the list of ports on the module
programmed in the selected Slot. Select the desired port and then press
<Enter>.
6. Select Number of TS, enter the number of timeslots to be connected, and then
press <Enter>.
7. Select Type and then press <Enter>. You will see a selection screen for the
type of the timeslots in the bundle. Select the desired type and then press
<Enter>.
8. Select Destination Start TS and specify the position of the first timeslot of the
bundle in the destination port frame. Make sure to take into consideration the
number of timeslots to be connected to the destination port.
9. When done, you can either select Save Configuration and continue the timeslot
assignment tasks, or select $ to check timeslot assignment, and if OK – to save
and update the database.
Note The Save Configuration option updates only the temporary timeslot assignment
tables, without performing any sanity check.

³ To delete all the timeslots of a selected port:

1. Select Delete TS (Per Slot and Port) on the timeslot assignment task selection
screen. You will see the timeslot deassignment data form configuration screen
for the selected port. A typical screen is shown in Figure 4-121.
2. Select Slot: you will see a selection screen with the list of slots in which
modules that can accept a bundle of timeslots are programmed. When a
CL.1/155 or CL.1/155GbE module is installed, the list also includes the CL slot.
Select the desired module (the module type appears next to the chassis slot),
3. Select Port: you will see a selection screen with the list of ports on the module
programmed in the selected Slot. Select the desired port and then press
<Enter>.
MP-4100
..>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Delete TS (Per Slot and Port)
1. Slot > (IO-2 (M8E1))

2. Port > (Link 2)
>

-----------------------------------------------------------------------------
Figure 4-121. Typical Delete TS (Per Slot and Port) Screen

4. When done, you must select Save Configuration and continue the timeslot
assignment tasks, and then select % to save and update the database.
³ To delete a bundle of timeslots on the selected port:

1. Select Delete TS (Number of TS) on the timeslot assignment task selection
screen. You will see the delete-bundle configuration screen for the selected
port. A typical screen is shown in Figure 4-122.
2. Select Start TS and specify the starting timeslot of the bundle on the selected
port. The range depends on the port type (maximum 31 for an E1 port, and
maximum 24 for a T1 port.
3. Select Number of TS, enter the number of timeslots to be connected, and then
press <Enter>.
4. When done, you must select Save Configuration and continue the timeslot
assignment tasks, and then select % to save and update the database.

MP-4100
...stem>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Delete TS (Number Of TS)
1. Start TS[1 - 31] ... (1)

2. Number of TS[1 - 31] ... (1)
>

-----------------------------------------------------------------------------
Figure 4-122. Typical Delete TS (Number of TS) Screen
³ To perform split timeslot assignment:

1. Select Split on the timeslot assignment task selection screen. You will see a
screen that includes the list of timeslots reserved for split assignment: in this
example, the list includes only TS3. A typical screen is shown in Figure 4-123.
MP-4100
Configuration>System>TS Assignment>IO>I/O-2 (M8E1)>Link 1>Split
1. TS 3>
>

----------------------------------------------------------------------------
Figure 4-123. Typical Split Timeslot Selection Screen

2. Select the desired timeslot and then press <Enter>. You will see the selection
screen on which you can select the user’s port to be connected to each bit. For
each port, you must configure the bits that will carry the payload of a user’s
port that needs split timeslot assignment.
You must select either 2, 4, or 8 consecutive bits, starting at bit 1, 3, 5, or 7,
in accordance with the following list:
Number of Bits Allowed Starting Bit
2 1, 3, 5, 7
4 1, 5
8 1

Note Do not mix bits from timeslots of different slots in the same link timeslot.
Figure 4-124 shows a typical screen after configuring the split timeslot
assignment.
MP-4100
Configuration>System>TS Assignment>IO>I/O-1 (M8E1)>Link 1>Split>TS 3
1. Bit 1 ... (01:IN03)

2. Bit 2 ... (01:IN03)
3. Bit 3 ... (------)
4. Bit 4 ... (------)
5. Bit 5 ... (------)
6. Bit 6 ... (------)
7. Bit 7 ... (------)
8. Bit 8 ... (------)
9. Check Split Sanity
>
Insert IO Slot and Port in the next format: 2:1 or 2:IN1

-----------------------------------------------------------------------------
Figure 4-124. Typical Split Assignment Screen

3. When done, select Check Split Sanity to check the assignment. Correct the
assignment as required, and then continue the timeslot assignment tasks, or
select % to save and update the database.
Configuring Payload Mapping to SDH/SONET Links

Use the following procedure to map the payload from the various Megaplex-4100
interfaces to specific TUs or SPEs, for transmission through the SDH/SONET
network link.
Mapping is relevant only for Megaplex-4100 equipped with CL.1/155 or
CL.1/155GbE modules.
The mapping functions include:
• Mapping of internal PDH ports
• Mapping of virtually concatenated groups (only for Megaplex-4100 with
CL.1/155GbE modules)
• Mapping of protection ports for PDH ports and virtually concatenated
groups
• Bypassing between links.
When APS is being configured, all the ports mapped to the protection link are
automatically disconnected, and all the ports mapped to the working link are
protected.

Path protection (see Configuring the LVC Parameters starting on page 4-92) is
always available, even on links included in an APS group: in this case, path
protection provides an additional protection layer at the lower level (the LVC
level).
The mapping screen has been especially designed to help you avoid errors:
• The screen displays the map of the TU/SPEs of the selected link, which
reflects the current mapping
• The mapping is automatically adjusted for the operating network link
standard (SDH or SONET).
Note The following screens illustrate the mapping process for SDH links, however the
same procedures apply to SONET links.
• The PDH ports that can be mapped/bypassed, and where applicable, the
virtually concatenated groups that have been configured, appear in a list
which is displayed under the map of the selected link.
The list also includes the None option, for unmapping a mapped/bypassed
port, and items for all the other links to which bypassing is possible
• Only enabled ports (Admin Status = UP) appear in the list
• The list automatically includes the PDH protection ports associated with
those PDH ports on which path protection has been enabled.
To navigate to the required screen, use Configuration>System>Mapping.
Figure 4-125 shows a typical Mapping selection screen for a Megaplex-4100 with
two CL modules.
MP-4100
Configuration>System>Mapping
1. CL-A >
2. CL-B >
>

-----------------------------------------------------------------------------
Figure 4-125. Typical Mapping Selection Screen
Typical Mapping Procedure
³ To map the CL internal (virtual) ports:

1. Open the Configuration>System screen, and select Mapping.

2. On the Configuration> System>Mapping screen, select the desired CL module,

and then select the desired link on the CL screen.
3. On the Configuration>System>Mapping>CL>Link screen, select the mapping of
each internal (virtual) port, starting with PDH1: move the cursor to the desired
position on the map, and then select the number corresponding to the internal
port to be mapped. The mapping is identified by TUG-3:TUG-2:TU-12: in this
example, 1:1:1 means that PDH1 is mapped to TU-12 number 1, in TUG-2
number 1, in TUG-3 No. 1.
Figure 4-126.A shows an SDH mapping screen after selecting the PDH1
position, and Figure 4-126.B shows a SONET mapping screen (Figure 4-126.B
shows only the lefthand part of the screen is shown: to see the missing
columns, use the navigation keys explained after selecting ?-help).
When a TUG-3 is mapped as a whole, a dashed line appears around the area
occupied by the TUG-3, instead of the individual Tus/VTs.
MP-4100
Configuration>System>Mapping>CL-A>Link 1
TUG3-1 TUG3-2 TUG3-3
TU1 TU2 TU3 TU1 TU2 TU3 TU1 TU2 TU3
TUG2-1 PDH1 None None None None None None None None
1. PDH1 2. PDH2 3. PDH3 4. PDH4 5. PDH5 6. VCG1

... (N)
>
1:1:1 -> PDH1 1:1:1

-----------------------------------------------------------------------------
A. Mapping Display for Typical SDH Link

MP-4100
STS1-1 STS1-2
->>
1. PDH1 2. PDH2 3. PDH3 4. PDH4 5. VCG1 6. VCG2

... (N)
>
1:1:1 -> PDH1 1:1:1

-----------------------------------------------------------------------------
B. Mapping Display for Typical SONET Link (Lefthand Area)

Figure 4-126. Typical Mapping Screens
4. Repeat the process until all the required ports are mapped. When done,
select % to save and update the database.
Using the Menu Mapping Mode

As an alternative to the map display mode, you can switch to the menu mode, by
typing m (refer to the ?-help screens of Figure 4-126). Figure 4-127 shows a
typical map mode display, and Figure 4-128 shows the corresponding menu mode
display when the cursor is located on the top lefthand corner of the map.

MP-4100

TUG2-1 VCG1 VCG1 VCG1 None None None None None None
1. None 3. VCG4 5. L2B-TU3 7. L2B-TU

2. VCG1 4. L1B-TU3 6. L1B-TU
>
->VCG1 1:1:1
-----------------------------------------------------------------------------
Figure 4-127. Typical Map Mode Display

MP-4100
(TUG2-1)
1. > (VCG1)
2. TUG3-1 > (VCG1)
3. > (VCG1)
4. > (None)
5. TUG3-2 > (None)
6. > (None)
7. > (None)
8. TUG3-3 > (None)
9. > (None)
>
#-Db Undo
-----------------------------------------------------------------------------
Figure 4-128. Typical Menu Mode Display
³ To perform mapping using the menu mode:

1. Move the cursor to the desired TU, and then type its number to display the
available mapping selections. A typical mapping selections screen is shown in
Figure 4-129.

MP-4100
Configuration>System>Mapping>CL-A>Link 1> (VCG1)
1. None
2. VCG1
3. VCG4
4. L1B-TU3
5. L2B-TU3
6. L1B-TU
7. L2B-TU
>

#-Db Undo
-----------------------------------------------------------------------------
Figure 4-129. Typical Mapping Selections Screen for Menu Mapping Mode
2. Type the number corresponding to the desired selection, and then press
<Enter>.
3. Repeat the process until all the required ports are mapped.
4. At any time, you can return to the map display (for example, Figure 4-127) by
pressing <ESC>.
Bypassing between Links

A bypass connection between two links has a bandwidth of one TUG-3 or STS-1.
Therefore, it is possible to bypass individual PDH ports, TUs or VTs, as well as a
whole TUG-3 or STS-1.
Bypassing is always made to the same position in the other link, for example,
TUG-3 No. 2 or STS-1 No. 2 of link A is always bypassed to TUG-3 No. 2/STS-1
No.2 of link B.
Any ports mapped to the bypassed TU/VT or TUG-3/STS-1 are automatically
unmapped on both links.
Figure 4-130 shows a typical mapping screen illustrating the bypassing procedure
on SDH links (for SONET links, TUs are replaced by VTs, for example, L1B-TU is
replaced by L1B-VT, and the total number of PDH ports is 84 instead of 63). The
bypassing selections (one for each of the other enabled links on the
Megaplex-4100) are always located at the end of the list; for clarity, the screen
shows an example in which no PDH port is enabled (all PDH ports have Admin
Status = DOWN).

MP-4100
1. None 3. L1B-TU3 5. L1B-TU 7. L1B-TU

2. L2A-TU3 4. L2B-TU3 6. L2A-TU
>

-----------------------------------------------------------------------------
Figure 4-130. Typical Mapping Screen with Bypassing Options (SDH Links)
³ To bypass ports between links:

1. Move the cursor to the map position corresponding to the TU to be bypassed.
2. You will see the available bypassing options. For example, when nothing is yet
bypassed and all links are enabled, the bypassing options for CL A link 1 are
L1B-TU3 (map whole TUG-3 to the same TUG-3 on link 1 of the other CL), L1B-
TU, L2A-TU3 (map whole TUG-3 to the same TUG-3 on link 2 of the same CL),
L2A-TU, L2B-TU3, L2B-TU. Enabled PDH ports will also appear.
3. Type the number corresponding to the other link, and then press <Enter>.
Figure 4-131 shows an SDH mapping screen for link 1 of CL A, with the
selection cursor positioned on the TU-12 identified as 1:2:1, before entering
the Set command. The screen also displays additional bypass connections; for
example, note the bypass connection to L2B-TU3: when you open the
mapping display of link 2 of CL B, you will see L2A-TU3 for TUG-3 No. 2.
For SONET links, you will see a similar screen, except that the TUG3 are
replaced by STS, the maximum number of PDH ports is 84, and the total
number of TUs is 84 (3 columns of 28 TUs each).

MP-4100
Configuration>System>Mapping>CL-A >Link 1

TU1 TU2 TU3 TU1 TU2 TU3
TUG2-1 PDH1 PDH2 PDH3 --- ---- --- None None None
TUG2-2 L2A-TU None None | | None None None
TUG2-3 None None None | | None None None
TUG2-4 L2B-TU None None | L2B-TU3 | None None None
TUG2-7 None None None --- ---- --- None None None
1. None 3. PDH2 5. L2A-TU3 7. L2B-TU3 9. L2A-TU

2. PDH1 4. PDH3 6. L1B-TU3 8. L1B-TU 10. L2B-TU
>
Bypass from L1-A-TU 1:2:1 to L2-A-TU 1:2:1

-----------------------------------------------------------------------------
Figure 4-131. Typical Mapping Screen after Bypassing has been Configured (SDH Links)
4. The mapping selection list is replaced by the SET command. To confirm, press
<Enter>. The new mapping takes effect and the mapping display is updated.
³ To cancel bypassing between links:

1. Move the cursor to the label of the bypassed TUG-3/STS-1.
2. Select None.
3. The bypassed path is automatically unmapped.
Mapping Ports with Path Protection Enabled

Path protection is enabled at the level of the individual PDH port, by means of
the Configuration>Logical Layer>CL>PDH>LVC Configuration screen of the port(s)
to be protected.
³ To enable path protection for a PDH port:

1. On the LVC Configuration screen of the port to be protected, select Path
Protection for the port Protection Mode.
2. The last selection needed is the Mapping Mode:
• Auto – this is the default selection, and it means that the protection port
is automatically mapped in the same position as the protected port, but on
the automatically selected protection link:
For Local CL: on the other link on the same CL module
For Adjacent CL: on the same link on the other CL module.

After confirming the selection, the corresponding P-PDH protection port

appears on the above-mentioned mapping screen. You can latter
manually change the mapping, even if its origin is automatic mapping.
• Manual – in this case, you map the protection port (P-PDH) manually, as
explained in the Typical Mapping Procedure section on page 4-152.
Note The Protection Partner field is not displayed when Mapping Mode is Manual.
3. A Protection Partner field appears, used to select the CL.1/155 or CL.1/155GbE

module on which the protection port will be located. When two CL.1/155 or
CL.1/155GbE modules are installed, you can select between Local CL and
Adjacent CL, otherwise the only selection is Local CL.
Note At this stage, a protection port selection item is added to the selection list
appearing under the map of the appropriate protection link, as explained below.
The protection ports appear near the end of the selection list, just before the
bypassing selections.
For example, if the protected port is PDH3, the protection port is identified a P-
PDH3.
4. Repeat the process for each additional port to be protected.

To manually map a protection port, or change an automatic mapping, use the
basic mapping procedure, as explained in the Typical Mapping Procedure section
on page 4-152, for the P-PDH ports.
Configuring 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:
• Interconnected E1 ports (including internal E1 ports of M8SL modules)
• Interconnected T1 ports
• Between the TDM and Ethernet ends of a bundle, for example M8E1
modules support fault propagation for its Ethernet ports. MLPPP bundles
use the BCP Fail alarm to report fault conditions: in response to this alarm,
the corresponding port is closed to traffic.
Fault propagation cannot be enabled for ports with redundancy enabled.
³ To configure fault propagation:

1. On the Configuration>System menu, select Fault Propagation, and then press
<Enter>.

MP-4100
Configuration>System>Fault Propagation
1. Fault Propagation (Enable)

2. Interfaces []>
>

-----------------------------------------------------------------------------
Figure 4-132. Fault Propagation, Task Selection Screen

2. Select Fault Propagation to toggle the selection: to configure fault
propagation, select ENABLE.
3. Select Interfaces to display the interface configuration screen. A typical screen
is shown in Figure 4-133. If no interfaces has yet been mapped for fault
propagation, the screen is empty.
4. To add fault propagation between a new pair of interfaces, type A (Add) and
then press <Enter>.
You will see the Interface configuration data form. A typical screen is
5. Select the first endpoint, Slot A: you will see a submenu which lists the I/O
slots in which modules with ports that support fault propagation are installed,
or at least programmed.
6. After selecting the desired slot, select Port A: you will see a submenu which
lists the ports that can serve as one end of a fault propagation link.
7. After selecting the desired port, repeat the selections for the other endpoint
(Slot B and Port B).

MP-4100
Configuration>System>Fault Propagation>Interfaces
Slot A Port A Slot B Port B Mode

IO-1 ETH 1 IO-5 ETH 2 BiDirectional(A<->B)
>

-----------------------------------------------------------------------------
Figure 4-133. Typical Fault Propagation Interfaces Screen

MP-4100
Configuration>System>Fault Propagation>Interfaces
1. Slot A > (IO-1)

2. Port A > (ETH 1)
3. Slot B > (IO-1)
4. Port B > (ETH2)
5. Mode > (UniDirectional(A->B))
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 4-134. Typical Fault Propagation Interfaces, Interface Configuration Screen

8. After specifying the two endpoints, select the fault propagation direction by
means of the Mode field:
• UniDirectional(A->B): fault conditions are reported only from endpoint A to
endpoint B.
• BiDirectional(A<->B): fault conditions are reported in both directions.
9. After completing the configuration, the new set of endpoints appear on the
Interfaces screen.
10. Repeat the procedure for any additional endpoints.

4.4 Additional Tasks
Setting the Internal Date & Time

Use the following procedure to update the time-of-day and date of the
Megaplex-4100 internal real-time clock, and select the date format displayed on
the Megaplex-4100 screens.
You can set time and date up to the end of 2099. The screen also displays the
current time and date provided by the Megaplex-4100 clock.
To navigate to the required screen, use Configuration>System>Date & Time.
A typical Date & Time screen is shown in Figure 4-135.
MP-4100
Configuration>System>Date & Time
1. Display Date & Time >

2. Set Date Format > (DD-MM-YYYY)
3. Set Date >
4. Set Time >
>

-----------------------------------------------------------------------------
Figure 4-135. Typical Date & Time Screen
³ To display the current date and time:

1. Select Display Date & Time and then press <Enter>.
2. You will see the time and date retrieved from the Megaplex-4100 at the
instant the command has been received by the equipment.
³ To change the date format:

1. Select Set Date Format, and then press <Enter> to display the Set Date Format
selection screen.
2. On the Set Date Format selection screen, type the number corresponding to
the desired date format and then press <Enter>.
Note DD stands for day, MM for month and YYYY for year.
³ To change the time:

1. Select Set Time, and then press <Enter>.
4-162 Additional Tasks Megaplex-4100 Ver. 2.0

2. Each component of the time of day is separately set. To change, select the
desired item and then type the desired value.
Notes • Time must be entered in the 24-hour format.

• It is recommended to set the time about one minute beyond the desired time,
and then press <Enter> at the correct instant.
3. Confirm each change by pressing <Enter>.
³ To change the date:

1. Select Set Date, and then press <Enter>.
2. Each component of the time of day is separately set. To change, select the
desired item and then type the desired value.
3. Confirm each change by pressing <Enter>.
Performing File Transfers to CL Modules
File Utilities Menu

The File Utilities menu enables using TFTP to perform the following operations:
• Download software to the Megaplex-4100. This enables you to update the
Megaplex-4100 software when a new release becomes available, download
again the software in case the stored software has been corrupted,
download software to a new or repaired CL module, and download
software to I/O modules that support this capability.
In addition to the information appearing in this Section, you can find detailed
software downloading instructions in Appendix B.
• Download a configuration parameters file to the Megaplex-4100.
• Upload the configuration parameters file of the local Megaplex-4100.
Megaplex-4100 Ver. 2.0 Additional Tasks 4-163

Figure 4-136 shows the structure of the File Utilities menu.

File Utilities
1. S/W & File Transfer CL S/W & File Transfer CL
1. TFTP TFTP
TFTP State
1. File Name
Command
2. Server IP
1. SW Download
3. Command
2. Config Download
3. Config Upload
4. No Command
S/W & File Transfer I/O &
S-Subsystem TFTP
1. TFTP TFTP State

2. Download to Cards TFTP Error
1. File Name
3. Download Status
2. Server IP File #
4. Dir
5. Delete File 3. File #
4. S/W Download (To Flash) 1. File-1
2. File-2
Download to Cards
Download Status
Dir
Delete File
Figure 4-136. Typical File Utilities Menu Structure

All the file transfer operations accessed from the File Utilities menu are
performed by means of the TFTP protocol. Appendix B explains what you need to
do to use TFTP.
Before Starting File Transfers

1. Obtain the list of software distribution files to be downloaded, and check that
the required distribution files are stored on the TFTP server.
2. Make sure that the TFTP server can communicate with the Megaplex-4100, for
example, by sending pings to the IP address assigned to the
Megaplex-4100 management entity (the host IP address).
File Transfers to CL Modules

File transfers to the CL modules are managed by means of the S/W & File
Transfer CL submenu. Valid software image files have the extension .img, and
configuration files have the extension .dat.
³ To select a file transfer task:

1. Open the File Utilities menu. A typical screen is shown in Figure 4-137.

MP-4100
File Utilities
1. S/W & File Transfer CL >

2. S/W & File Transfer I/O & S-Subsystem >
>
File system and File transfer operations

-----------------------------------------------------------------------------
Figure 4-137. Typical File Utilities Menu

2. Select S/W & File Transfer CL on the File Utilities menu. You will see the S/W &
File Transfer CL submenu. A typical screen is shown in Figure 4-138.
MP-4100
File Utilities>S/W & File Transfer CL
1. TFTP >
>
File Transfer operations

-----------------------------------------------------------------------------
Figure 4-138. Typical S/W & File Transfer CL Submenu
Updating the CL Management Software

The following procedure is separately performed on each CL module, starting with
the on-line module.
Note The following procedure also updates the Ethernet subsystem software of
CL.1/GbE and CL.1/155GbE modules.
³ To start a TFTP transfer:

1. On the S/W & File Transfer CL screen, select TFTP to display the TFTP control
screen. Initially, the screen includes only the File Name and Server IP items.

2. On the TFTP control screen, select each of the items to define the parameters
needed to perform the TFTP transfer:
• Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). When done, press
<Enter> to continue.
• Select Server IP, and enter the IP address of the server that will download
the software distribution file. Enter the desired IP address in the dotted
quad format, and then <Enter> to continue.
• After the previous two items are configured, a third item, Command,
appears, together with a TFTP State field that displays the state of the
TFTP operations. Initially, this field displays NoOp (no operation).
A typical screen is shown in Figure 4-139 as seen after Step 2 is
completed.
MP-4100
File Utilities>S/W & File Transfer CL>TFTP
TFTP State > (NoOp)

1. File Name ... (cx150.img)
2. Server IP ... (172.17.65.12)
3. Command >
>
TFTP operations
-----------------------------------------------------------------------------
Figure 4-139. Typical TFTP Control Screen (S/W & File Transfer CL)
• Select Command to display the Command task selection screen (see typical
screen in Figure 4-140). The screen provides the following selections:
SW Download Download a software distribution file from the specified

TFTP server to the Megaplex-4100.
Config Download Download a configuration parameters file from the

specified TFTP server to the Megaplex-4100.
Config Upload Upload the current configuration parameters file of the

Megaplex-4100 to the specified TFTP server.
No Command Do not perform any operation.

MP-4100
File Utilities>S/W & File Transfer CL>TFTP>Command
1. SW Download
2. Config Download
3. Config Upload
4. No Command
>

-----------------------------------------------------------------------------
Figure 4-140. Typical TFTP Command Screen (S/W & File Transfer CL)
3. On the Command screen, select SW Download to start the software
downloading.
If no errors are detected, the downloading process starts, and its
progress is displayed in the TFTP State field. Errors (for example, a
protocol time-out) are reported in a separate TFTP Error field: if you see
an error message, check and correct the error cause, and then select
again the SW Download command.
4. After the transfer is successfully completed, the active CL module stores the
file in its flash memory. Now the Megaplex-4100 is automatically reset and the
new software is decompressed. After the resetting is successfully completed,
you will see the Megaplex-4100 log in screen again.
Note If downloading failed, repeat the whole procedure.
5. Log in with the default parameters as follows:

• In the User Name field, type the default user name, su, and then press
<Enter>
• In the Password field, type the default, 1234, and then press <Enter>.
6. You will see the main menu screen. The Megaplex-4100 now uses the
downloaded software.
7. Repeat the transfer to download the same file to the other CL module. For this
purpose, first switch the other CL module on-line (use Config>System>Reset
Device to send a reset command to the on-line module).
Downloading a Configuration File

Configuration files are downloaded to the Megaplex-4100 flash memory.

³ To download a configuration file:

• Perform Steps 1, 2, 3 of the Updating the CL Management Software
procedure (starting on page 4-165), but in Step 3 select Config Download.
After the transfer is successfully completed, the CL module stores the file
in its flash memory, replacing all the previously stored databases, and the
DB1 database automatically becomes the active one.
Uploading a Configuration File

The contents of the Megaplex-4100 edit buffer can also be uploaded to the
management station as a standard disk file. The management station can then
distribute this file, as a configuration file, to other units which use similar
configuration. The configuration of each unit can then be customized as required.
³ To upload a configuration file:

Perform Steps 1, 2, 3 of the Updating the CL Management Software procedure
(starting on page 4-165), but in Step 3 select Config Upload.
File Transfers to I/O Modules and SDH/SONET Subsystems

In addition to the CL module software (which also includes the software
controlling the Ethernet traffic handling subsystem used by CL.1/GbE and
CL.1/155GbE modules), the current Megaplex-4100 version also enables
downloading software to I/O modules that support this feature (for example, to
the I/O modules with E1, T1, SHDSL, and Ethernet interfaces, M8E1, M8T1,
M8SL), and to the SDH/SONET traffic handling subsystem located on CL.1/155
and CL.1/155GbE modules. Each of these modules or subsystems can be
independently updated, using separate software image files.
The CL module flash memory includes two dedicated software storage areas
(identified as File 1 and File 2 on the supervision terminal screens), where each
area can store two independent image files, in accordance with user’s
requirements: for example, each area can hold a different version of I/O modules
software, or one area can be dedicated to I/O modules software, and the other
to SDH/SONET software. Moreover, the user can specify from which area to
download software to each module or subsystem.
Note The contents of these storage areas are not checked for consistency between
the two CL modules.
File transfers to I/O modules and to the SDH/SONET subsystems are managed by
means of the S/W & File Transfer I/O & S-Subsystem submenu. This submenu is
used to download the required software image to a selected software storage
area of the CL modules, and then download the stored software image to each
I/O module or SDH/SONET subsystem. The required steps differ slightly, in
accordance with the type of software:
• For SDH/SONET subsystems, you need to download the required software
image to a selected software storage area of the active CL module, and

then download the stored software image from the active CL module to
the SDH/SONET subsystem of the same CL module.
• For I/O modules, a single CL module (the on-line module) can download
software to any number of I/O modules. Therefore, it is not mandatory to
download I/O modules software to both CL modules (but this is still a
recommended procedure). Moreover, the CL module can be configured to
download the software to the desired modules in one step (the
downloading itself is sequentially performed).
After the software is successfully downloaded to an SDH/SONET subsystem or I/O
module, that subsystem/module is automatically reset, and then starts using the
new software version. This process momentarily disrupts the traffic flowing
through the SDH/SONET subsystem or I/O module that is being updated (if the
updated component provides the Megaplex-4100 nodal timing reference, flipping
to another timing reference may also occur).
³ To download an I/O module or SDH/SONET software image to a CL module:

1. Open the File Utilities menu.
2. Select the S/W & File Transfer I/O and S-Subsystem option on the File Utilities
menu.
You will see the S/W & File Transfer I/O and S-Subsystem submenu. A
typical submenu is shown in Figure 4-141.
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem
1. TFTP >
2. Download To Cards >
3. Download Status >
4. Dir >
5. Delete File >
>

-----------------------------------------------------------------------------
Figure 4-141. Typical S/W & File Transfer I/O & S-Subsystem Submenu
3. On the S/W & File Transfer I/O and S-Subsystem submenu, select TFTP to
display the TFTP control screen (a typical screen is shown in Figure 4-142).
Initially, the screen includes only the File Name, Server IP, and File # items.

MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>TFTP
Tftp State > (NoOp)

1. File Name ... (mlx150.img)
2. Server IP ... (172.171.55.75)
3. File # > (File-1)
4. S/W Download (To Flash)
>

-----------------------------------------------------------------------------
Figure 4-142. Typical TFTP Control Screen (S/W & File Transfer I/O and S-Subsystem)
4. On the TFTP control screen, select each of the items to define the parameters
• Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). When done, press
• Select Server IP, and enter the IP address of the server that will download
• Select File # to open the storage area selection screen for the current CL
module. Select the desired storage area, File-1 or File-2, and then <Enter>
to continue.
• After the previous items are configured, a fourth item, S/W Download (To
Flash), appears, together with a TFTP State field that displays the state of
the TFTP operations. Initially, this field displays NoOp (no operation).
5. On the TFTP control screen, select SW Download (To Flash), to start the
software downloading.
again SW Download (To Flash).
file in the selected storage area of its flash memory.
7. Repeat the transfer to download the same file to the other CL module. For this
purpose, first switch the other CL module on-line (use Config>System>Reset
Device to send a reset command to the on-line module).

³ To load a software image to an I/O module or SDH/SONET subsystem:

1. On the File Utilities menu, select S/W & File Transfer I/O and S-Subsystem.
2. On the S/W & File Transfer I/O and S-Subsystem screen, select Download to
Cards to display the downloading target selection screen. A typical screen is
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Download To Cards
1. S-Subsystem CL-A > (Disable)

2. I/O-2 > (Disable)
>

-----------------------------------------------------------------------------
Figure 4-143. Typical Download to Cards Screen

3. On the Download to Cards screen, select the desired target, and then press
<Enter> to open the source storage area selection screen.
4. The source storage area selection screen provides the following selections:
Disable No software downloading to the corresponding target.
FIle-1 The software downloaded to the corresponding target is

taken from the File-1 storage area.
File-2 The software downloaded to the corresponding target is

taken from the File-2 storage area.
Select the storage area (File-1 or File-2) that stores the desired file, and then
press <Enter>.
Note If you are not sure of the image file location, use Config>S/W & File Transfer I/O
& S-Subsystem>Dir (page 4-172) to find it.
5. Repeat Steps 3, 4 for each I/O module, as necessary, or continue to Step 6.

6. After Step 4, an additional item, SW Download, appears on the Download to
Cards screen. When ready to start the software downloading, select SW
Download.
If no errors are detected, the downloading process starts. You can select
Download Status on the S/W & File Transfer I/O and S-Subsystem screen
to display the progress (a typical screen, as seen after successfully
downloading the software, is shown in Figure 4-144). If you see an error
message, check and correct the error cause, and then select again the SW
Download command.

MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Download Status
I/O-2 > (Successful)
>

-----------------------------------------------------------------------------
Figure 4-144. Typical Download Status Screen

7. After the transfer is successfully completed, the SDH/SONET subsystem or I/O
module is automatically reset and the new software is decompressed. After
the resetting is successfully completed, the SDH/SONET subsystem or I/O
module is again ready to carry traffic.
8. For SDH/SONET subsystems, it is necessary to repeat the procedure for the

other SDH/SONET subsystem.
Using the Dir Function

The Dir screen is used to display the flash memory contents of the on-line CL
module.
³ To display the flash memory directory:

2. On the S/W & File Transfer I/O and S-Subsystem screen, select Dir to display
the list of files stored in the flash memory. A typical screen is shown in
Figure 4-145.

MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>Dir
... (File-1 mp4ms18e.img)
>

-----------------------------------------------------------------------------
Figure 4-145. Typical Dir Screen
Deleting Files
The Delete File screen is used to delete a file stored in the flash memory of the
on-line CL module.
³ To delete a file from the flash memory:

2. On the S/W & File Transfer I/O and S-Subsystem screen, select Delete File to
display the file selection screen. A typical Delete File screen is shown in
Figure 4-146.
MP-4100
ile Utilities>S/W & File Transfer I/O & S-Subsystem>Delete File
1. File-1
>

#-Db Undo
-----------------------------------------------------------------------------
Figure 4-146. Typical Delete File Screen

3. Select the file to be deleted (File-1 or File-2), and then press <Enter>.

Viewing Logistic (Inventory) Information

The Inventory menu is used to display logistic information on the Megaplex-4100
system, and its subsystems.
The information displayed by means of the Inventory menu is automatically
retrieved from the various system components and from the Megaplex-4100
configuration and software files. Therefore, it cannot be directly modified.
³ To display the Inventory menu:

Select Inventory on the main menu and then press <Enter>.
A typical Inventory menu is shown in Figure 4-147.
MP-4100
Inventory
1. System []>
2. SW/HW Rev[]>
>

-----------------------------------------------------------------------------
Figure 4-147. Typical Inventory Menu

The menu includes two items:
• System: displays a list of the main components installed in the
Megaplex-4100 unit, and provides general logistic information.
• SW/HW Rev: displays information on the modules installed in each chassis
slot, together with the software version and hardware revision. Also
presents the module programmed for each slot.
Displaying System Inventory Information
³ To display the System Inventory screen:

Select System on the Inventory menu.
The System screen includes several pages, where each page can be scrolled to
view additional fields, beyond those displayed as a default (the leftmost section
of the screen). A typical first page of the System screen is shown in Figure 4-148.

MP-4100
Inventory>System
Description SW Version HW Revision

1 RAD.MP4100.PS-A.PS
2 RAD.MP4100.PS-B.-------------
| 3 RAD.MP4100.CL-A.CL1/155GbE 1.50B0/ 1.217 1. 0/ 0.0
v 4 RAD.MP4100.CL-B.-----------
5 RAD.MP4100.IO-1.-------------
6 RAD.MP4100.IO-2.M8E1 1.51 1
7 RAD.MP4100.IO-3.M8T1 1.UNDEF 1
->>
>

-----------------------------------------------------------------------------
Figure 4-148. Typical System Information Screens

The screen provides general logistics information for the main components of the
Megaplex-4100 system, starting with the chassis slots. Use the arrow keys to
scroll between screen pages (you can see additional navigation options by
selecting the ?-help option).
The main parameters appearing for each screen row are explained in Table 4-39.
In addition to these parameters, there are additional fields needed only by
management stations, or by support personnel. In particular, you can find, on the
rightmost screen, a Firmware field, which lists the firmware revision for the
corresponding component, when applicable.
Table 4-39. Main System Information Parameters
Parameter Description
Description Displays the formal name of the component. ----- appearing in this column indicates
that no item is installed in the corresponding position, or that no information is available
SW Version Lists the software version for the corresponding component, when applicable (for
example, when a module is installed in the corresponding slot)
HW Revision Lists the hardware revision for the corresponding component, when applicable (for
example, when a module is installed in the corresponding slot)
Displaying SW/HW Revision Information
³ To display the SW/HW Rev screen:

Select SW/HW Rev on the Inventory menu.
The SW/HW Rev screen includes two pages. A typical first page of the System

The screen displays the software and hardware versions for each module
installed in the Megaplex-4100 system, and also the module programmed for
each position in the currently active database. You can use this information to
rapidly check for inconsistencies between the modules installed in the chassis,
and those programmed in the active database.
MP-4100
Inventory>SW/HW rev
Slot Installed Card HW Revision SW Version Programmed Card

PS-A PS PS
PS-B ------------- PS
| CL-A CL1/155GbE 1. 2/ 0.0 2.0B0/ 0.0 CL1/155GbE
v CL-B ----------- CL1/155GbE
IO-1 ------------- M8E1
IO-2 M8E1 1 1.51 M8E1
IO-3 M8T1 1 1.UNDEF M8T1
IO-4 ------------- VC-16/E&M
IO-5 M8SL 1 1.50 M8SL
IO-6 ------------- HS-12N
IO-7 ------------- HS-U12
IO-8 ------------- HS-S
>

-----------------------------------------------------------------------------
Figure 4-149. Typical SW/HW Rev Screen

The information presented in Figure 4-149 displays logistics data that may be
needed by RAD technical support personnel when servicing the unit. The
information is retrieved from the modules installed in chassis.
Table 4-40. SW/HW Rev Information Parameters
Slot Displays the chassis slot designation
Installed Card Lists the module installed in the corresponding chassis slot.
----- in this column indicates that no module is installed in the corresponding slot
HW Revision When a module is installed in the corresponding slot, lists its hardware revision
SW Version When a module is installed in the corresponding slot, lists its software version
Programmed Card Lists the module programmed in the currently active database for the corresponding
chassis slot
Reloading Factory Defaults

Use the following procedure to reload the factory default configuration, instead
of the user’s configuration, in the edit buffer.

This action can be used to create a clean, known starting point, or delete the
existing configuration before starting configuring the Megaplex-4100 for
operation in a new application.
To avoid changing parameters that could cause loss of management
communication with the Megaplex-4100, the following parameters are not
modified:
• IP addresses, and all the management parameters
• Control port parameters
• STM-1/OC-3 frame structure
• Admin Status of the SDH/SONET link, if the DCC is used for management.
To navigate to the required screen, use Configuration>System>Factory Default.
³ To reload the factory default parameters:

1. Select Factory Default on the System menu.
2. You will see DB values will change to defaults. Are you sure?:
• To abort, type n.
• To confirm, type y.
3. If you confirmed, you must save the new configuration before it is actually
activated:
• If you change your mind, undo by typing #.
• To activate the default configuration, type % (the DB Update command). In
this case, You will see Are you sure you want to update active database –
Y/N? and therefore you must confirm again:
To abort, type n.
To confirm, type y.
4. At this stage, the Megaplex-4100 switches to the default parameters.
Note Usually, you must press <Enter> before you see again the menu.
However, if the Megaplex-4100 did not use the default supervisory port
communication parameters, then before you can establish again communication
with the Megaplex-4100 you must change the supervisory terminal
communication parameters to the default values: 115.2 kbps, one start bit, eight
data bits, no parity, one stop bit and VT-100 terminal emulation.
Reset Device
Use the following procedure to reset the Megaplex-4100 (that is, reset all the
modules installed in the chassis, including the CL modules), or a specific I/O
module. Resetting does not affect the configuration data changed by the user,
not even if it has not yet saved.
To navigate to the required screen, use Configuration>System>Reset Device.

³ To reset the Megaplex-4100:

1. Select Reset Device on the System menu.
2. Select CL-A or CL-B on the list (only the active CL module can be selected), and
then press <Enter>.
3. You will see The device will restart. Do you want to proceed – Y/N?:
4. At this stage, the Megaplex-4100 is reset.
³ To reset an I/O module:

1. Select Reset Device on the System menu.
2. Select the desired I/O module on the list, and then press <Enter>. only
modules installed in the chassis can be reset.
3. You will see The device will restart. Do you want to proceed – Y/N?:
4. At this stage, the corresponding I/O module is reset.

Chapter 5
Configuring Typical
Applications
5.1 Overview
This Chapter provides configuration guidelines for Megaplex-4100 systems in
typical applications.
To cover the wide range of possible applications, the Chapter presents two
examples, one for SDH environments and the other for SONET environments:
• Section 5.2 presents an application that enables transporting Ethernet traffic
over E1 links
• Section 5.3 presents an application that enables transporting TDM and
Ethernet traffic over a SONET ring.
screens are given for illustration purposes only, for the specific configuration
examples presented in this Chapter. They do not reflect recommended values for
other operating conditions.
The configuration activities presented in this Chapter assume that Megaplex-4100

is being configured using a standard ASCII terminal, and that you are familiar with
the Megaplex-4100 management, as described in Chapter 3. Detailed descriptions
and instructions for using each screen identified below appear in Chapter 4.
Note
In Appendix C, you can find concise descriptions of the Megaplex-4100 operating
environment, and technical background information on many Megaplex-4100
configuration parameters.
For your convenience, you can find below outlines of the preliminary
configuration sequence, and of the general configuration sequence
Outline of Preliminary Configuration Sequence

The purpose of the preliminary configuration is to prepare the minimal set of
parameters needed to manage the Megaplex-4100. In particular, after preliminary
configuration you will enable management access by Telnet hosts and
management stations, for example, RADview TDMoIP Service Center, that are
attached to a LAN directly connected to the Ethernet port of the Megaplex-4100

Chapter 5 Configuring Typical Applications Installation and Operation Manual
CONTROL module, or at a remote location from which IP communication with the

CONTROL module is possible.
After completing the preliminary configuration, you may also use Telnet hosts
and SNMP-based management stations to manage the Megaplex-4100.
Note
To enable management access to the Megaplex-4100 from any relevant location,
it is necessary to fully configure the Megaplex-4100: only full configuration can
permit management traffic to reach the Megaplex-4100 via inband paths.
The steps usually included in the preliminary configuration, when starting from
the factory defaults, are described in Table 5-1. For detailed operating
instructions, refer to the Chapter 4 section describing each activity.
Table 5-1. Megaplex-4100, Outline of Preliminary Configuration Procedure
1 Select the default database, 1 Configuration>DB Tools>Default DB
2 If the Megaplex-4100 is equipped with all the Configuration>DB Tools>Load HW

modules, load the hardware configuration.
Alternatively, configure the modules and then
reload the factory-default parameters installed in Configuration>System>Card Type
the Megaplex-4100. You can also program
modules not yet installed in the chassis
5 Configure the Megaplex-4100 management agent Configuration>System>Management>Host IP
6 Configure Megaplex-4100 management access Configuration>System>Management>Mng Access

(optional)
8 Set Megaplex-4100 real-time clock (optional) Configuration>System>Date & Time
9 Save the configured information in the selected Configuration>DB Tools>Update DB

database
General Configuration Sequence

Table 5-2 lists the additional steps needed to configure a Megaplex-4100 for
typical applications.
For detailed operating instructions, refer to the Chapter 4 section describing each
activity.

Installation and Operation Manual Chapter 5 Configuring Typical Applications
Table 5-2. Outline of Configuration Sequence for Typical Applications

• SDH/SONET ports (make sure to configure Configuration>Physical Layer>CL>CL-A, CL-B>
the frame structure) SDH/SONET
• GbE ports (make sure to configure the GbE Configuration>Physical Layer>CL>CL-A, CL-B>
port redundancy parameters) ETHERNET
• Station clock ports Configuration>Physical Layer>CL>CL-A, CL-B>Station
Clock
3 Configure the physical ports of the I/O modules Configuration>Physical Layer>I/O>I/O-1 to I/O-10
(E1, T1, SHDSL, Ethernet, etc.)
4 Configure the virtual ports on the SDH/SONET

ports of the CL modules:
• PDH ports Configuration>Logical Layer>CL>PDH
• High-order VCs Configuration>Logical Layer>CL>HVC>CL-A, CL-B
5 Configure the virtual ports of the I/O modules Configuration>Logical Layer>I/O>I/O-1 to I/O-10
6 Prepare the Megaplex-4100 for SNMP

management:
1. Select the SNMP support mode Configuration > System > Management > SNMPv3
(enable/disable SNMPv3).
If SNMP support mode is changed, save to
activate the change before continuing.
2. When SNMPv3 is Disabled, configure SNMPv1
community names. Configuration > System > Management > Host IP
3. When SNMPv3 is Enabled, configure
parameters in the following order:
– SNMP Engine ID Configuration > System > Management > SNMP
Engine ID
– SNMPv3 users Configuration > System > Management > SNMPv3
Setting > Users
– SNMPv3 targets and notifications Configuration > System > Management > SNMPv3
Setting > Targets & Notify
– Configure SNMPv1/SNMPv3 mapping Configuration > System > Management > SNMPv3
Setting > SNMPv1/v3 Mapping

order:
• Configure the prescribed bundles Configuration>Logical Layer>Bundles
• Configure the prescribed virtually Configuration>Logical Layer>CL>VCAT>CL-A, CL-B
and where necessary configure virtually
concatenated group redundancy

9 Configure path protection parameters for each Configuration>Logical Layer>IO

virtual and I/O module port
12 Configure internal cross-connections (timeslot Configuration>System>TS Assignment

assignment on framed ports)
13 Configure mapping to the SDH/SONET links Configuration>System>Mapping

Configuration>DB Tools>Load DB. Repeat the
relevant steps as needed to create a new database

5.2 Configuration Procedure for Typical Ethernet

Transport Application
Overview
This section provides detailed configuration procedures for a typical
Megaplex-4100 application that enables transporting Ethernet traffic over TDM
infra-structure. The application topology is shown in Figure 5-1.
Location B Location A
VLAN 1,2,3 to Location A VLAN 1,2,3 to Location B

VLAN 7,8,9 to Location C VLAN 4,5,6 to Location C
GbE GbE 20 E1 GbE GbE
GbE GbE Megaplex-4100 B Megaplex-4100 A GbE GbE

NMS
20 E1 20 E1
VLAN 4,5,6 to Location A

VLAN 7,8,9 to Location B
Megaplex-4100 C
GbE GbE
GbE GbE
Location C
Figure 5-1. Network Topology for Configuration Example
In this application, the three Megaplex-4100 units are interconnected by

point-to-point links, each having a capacity of 20 E1 trunks, used to transport
Ethernet traffic over MLPPP bundles.
In addition to the E1 trunks, a protective ring topology is built by connecting the
Megaplex-4100 units to a packet-switched network, using the GbE ports of the CL
modules (the ring is represented by the dashed lines in Figure 5-1. For this
purpose, each group of 8 E1 streams is sent via one bridge port and the
corresponding flow is assigned one VLAN. The total number of bridge ports
needed for 20 E1 trunks is 3 (each bridge port supporting 8 E1, 8 E1 and 4 E1,
respectively). A total of 6 VLANs are therefore needed for each Megaplex-4100.
The routers bind the VLANs into a trunk. The routing protocol provides load
sharing for the traffic, which in effect provides ring functionality.
Megaplex-4100 Ver. 2.0 Configuration Procedure for Typical Ethernet Transport Application 5-5
Network management is performed by an SNMP-based network management

station, for example, RADview NMS PC, using an out-of-band connection via a
serial or Ethernet port.
Configuration Sequence
For each of the 3 sites (Location A, Location B, Location C, in that order), the
configuration sequence is as follows:
1. Preliminary configuration.
2. Configuring the clock sources.
3. Configuring the physical ports.
4. Adding bundles.
5. Interconnecting bundles to form flows.
6. Connecting the bundles to their E1 ports.
Preliminary Configuration (All Sites)

1. Connect a terminal to the CONTROL DCE connector of the active CL module.
Make sure to use VT-100 supervision terminal emulation.
2. Configure the supervision terminal for communication with the
Megaplex-4100. Megaplex-4100 default configuration is as follows:
115.2 kbps, one start bit, eight data bits, no parity, one stop bit. Select
full-duplex mode, echo off, and disable flow control.
3. If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for a few seconds,
and then press <Enter> several times.
4. Type the default user name (su) and password (1234).
MP-4100
USER NAME: su
PASSWORD: ****
5. Set the factory default parameters for the Megaplex-4100, using

Configuration>System>Factory Default.
6. Press Y to confirm.
7. Set the time and date, using Configuration>System>Date & Time.
8. Load the hardware configuration (the installed modules), using
Configuration>DB Tools>Load HW, and then press Y to confirm.
9. To save and activate the new configuration, press the % key, and then press
Y to confirm.
Configuration File Update Is In Process will appear at the bottom of the
screen while the database is being saved (a few seconds).
10. Check the modules installed in the Megaplex-4100 chassis, using
Inventory>SW/HW Rev.
5-6 Configuration Procedure for Typical Ethernet Transport Application Megaplex-4100 Ver. 2.0
MP-4100
Inventory>SW/HW Rev

PS-A PS PS
PS-B PS PS
| CL-A CL1/155GbE 0. 2/ 0.1 1.50B2/ 1.13 CL1/155GbE
v CL-B CL1/155GbE 0. 2/ 0.1 1.50B2/ 1.13 CL1/155GbE
IO-1 M8E1 1 1.54 M8E1
IO-2 M8E1 1 1.54 M8E1
IO-3 M8E1 1 1.54 M8E1
IO-4 M8E1 1 1.54 M8E1
IO-5 M8E1 1 1.54 M8E1
IO-6 M8E1 1 1.54 M8E1
IO-7 ------------- -------------
IO-8 ------------- -------------
11. Configure the Megaplex-4100 management IP address and other IP

communication parameters, using Configuration>Quick Setup.
MP-4100
1. Host IP Address... (172.17.191.100)

2. Subnet Mask ... (255.255.255.0)
3. Default Gateway... (172.17.191.153)
12. Configure the Megaplex-4100 IP agent name, using Configuration>System>

Management>Device Info.
MP-4100
Sys Description... (Sys type:MP-4100 Sys Ver:1.50A0 Chassis Revision:0)

1. Device Name ... (MP4100)
2. Contact Person ... (Name of contact person )
3. Location ID ... (The location of this device )
Configuring the Primary Site (Location A)
Configuring the Clock Sources

1. Configure the system clock source of Megaplex-4100 A to Internal, using
Configuration>System>Clock Source.
As a result, Megaplex-4100 A serves as the timing reference for the
whole E1 network.
MP-4100
1. Source > (Internal)
Configuring the Physical Layer

1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>CL>
CL-A>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-A>LAN>GbE 1

4. Flow Control (Disable)
5. User Name ... ()
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>CL>

CL-B>LAN>GbE 1.
MP-4100
Configuration>Physical Layer>CL>CL-B>LAN>GbE 1

5. User Name ... ()
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration>Physical

Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links
Redundancy > (None)

2. User Name ... ()
3. Line Type > (Unframed)
5. Data OOS[0 - ff] ... (00)
8. Destination Slot > (IO-1 (M8E1))
9. Destination Port > (-)
4. You will be asked to confirm: Are you sure you want set all parameters
Y/N/C?. Press Y to confirm.
5. Repeat the same configuration steps for I/O slots 2, 4 and 5.
6. Activate the first 4 E1 ports on I/O slots 3 and 6, starting with link 1. Use
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down)

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)
7. Repeat Step 6 for links 2 to 4.

8. Repeat the same procedure (Steps 5, 7) for I/O slot 6.
Configuring Bundles
1. Add an MLPPP bundle with eight E1 links to I/O slot 1:
1. Open Configuration>Logical Layer>Bundles.
MP-4100
1. Slot > (IO-1)

2. Bundle[1 - 32] ... (1)
2. Type a to add a bundle to the M8E1 module in I/O slot 1.

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
7. Link OAM (Disable)
8. Number Of Links[1 - 8]... (8)
... (N)
3. Type N to display next page, which displays the other source ports.
MP-4100
... (P)
2. Add an MLPPP bundle with eight E1 links to I/O slot 2 (type P for previous
page):
1. Select Slot>IO-2.
MP-4100
1. Slot > (IO-2)

2. Bundle[1 - 32] ... (1)
2. Type a to add an MLPPP bundle to the M8E1 module in I/O slot 2.

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-2)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-3)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-3)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-4)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-4)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-5)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-5)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-6)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-6)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)
Interconnecting Bundles to Form Flows

1. Connect BND1 on I/O slot 1 to a physical ETH port by configuring a flow:
1. Open Configuration>Applications>Ethernet Services>Flows.
MP-4100
1. Flow[1 - 250] ... (1)
2. Type a to add a flow.
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()
3. Select Bridge Port Mapping and map the required bridge ports to the
flow.
MP-4100
4. Type a to add the first bridge port to this flow.

MP-4100
BP[1 - 512] ... (359)

1. C-VLAN Type > (Aware)
2. C-VLAN ID[1 - 4094] ... (1)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()
5. Use F to scroll among the available ports.

6. Type S to save and then type <ESC>.
7. Type a to add the second bridge port to this flow.
MP-4100
BP[1 - 512] ... (1)

2. C-VLAN ID[1 - 4094] ... (1)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-1)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()
MP-4100

1 Aware 1 0 IO-1 Bnd 1 16384Kbps
1. Unaware
2. Aware
9. Type <ESC>.
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()

MP-4100
1. Flow[1 - 250] ... (2)

2. User Name ... ()
flow.
MP-4100

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (2)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (36)

2. C-VLAN ID[1 - 4094] ... (2)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-2)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()
7. Type S to save and then type <ESC> twice.

3. Select Bridge Port Mapping.
MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (3)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (71)

2. C-VLAN ID[1 - 4094] ... (3)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-3)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()


MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (4)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (4)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-4)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (5)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (5)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (6)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (142)

2. C-VLAN ID[1 - 4094] ... (6)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()
Connecting Bundle to the E1 Ports

1. Connect the E1 ports of the modules in slots I/O 1 to I/O 4 to the bundles
configured above:
1. Open Configuration>Physical Layer>IO>I/O-1 (M8E1)>E1>All Links.

MP-4100
Redundancy > (None)

2. User Name ... ()
5. Data OOS[0 - ff] ... (00)
2. Type 9 to change Destination Port to Bundle 1.

MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links>Destination Port (-)
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1
2. Repeat the procedure for I/O slots 2, 4 and 5.
3. Connect the E1 ports 1 to 4 on I/O slot 5 to BND1:
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Up).
MP-4100
Configuration>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)
MP-4100
...on>Physical Layer>IO>I/O-5 (M8E1)>E1>Link 1 (Up)>Destination Port (-)
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1
4. Repeat the same procedure for I/O slot 6.

5. To save and activate the new configuration, press %.
6. Press Y to confirm. Configuration File Update Is In Process will appear at the
bottom of the screen for the time the database is being saved (a few
seconds).
Configuring Equipment at Location B
Configuring the Clock Source

1. Configure the system clock source to use the recovered clock signal of E1
link 1 of the M8E1 in I/O slot 1, using Configuration>System>Clock
Source>Source>Rx Clock>Master Port.
MP-4100
Entry Num Slot Port
1 IO-1 (M8E1) Link 1
2 None -
| 3 None -
v 4 None -
5 None -
6 None -
7 None -
2. Type <ESC> for previous screen, and then select Fallback Port to configure
the fallback clock source to use the recovered clock signal of E1 link 1 of the
M8E1 in I/O slot 6.
MP-4100
Configuration>System>Clock Source>Fallback Port
Entry Num Slot Port
2 None -
| 3 None -
v 4 None -
5 None -
6 None -
7 None -

1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>
CL>CL-A>LAN>GbE 1.
MP-4100

5. User Name ... ()
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>

CL>CL-B>LAN>GbE 1.
MP-4100

5. User Name ... ()
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration> Physical

Layer>IO>I/O-1 (M8E1)>E1>All Links.
MP-4100
Redundancy > (None)

2. User Name ... ()
5. Data OOS[0 - ff] ... (00)
5. Repeat the same configuration steps for I/O slot 2, 4 and 5.
Configuration> Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down).
MP-4100

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)

8. Repeat Step 6 for I/O slot 6.
Configuring Bundles
MP-4100
1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)
MP-4100
... (P)
page):
MP-4100
1. Slot > (IO-2)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-2)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-3)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-3)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-4)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-4)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-5)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-5)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-6)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-6)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Flow[1 - 250] ... (1)

MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()
flow.
MP-4100

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (1)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (1)

2. C-VLAN ID[1 - 4094] ... (1)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-1)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()
MP-4100

1. Unaware
2. Aware
9. Type <ESC>.
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()

MP-4100
1. Flow[1 - 250] ... (2)

2. User Name ... ()
flow.
MP-4100

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (2)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (36)

2. C-VLAN ID[1 - 4094] ... (2)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-2)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (3)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (71)

2. C-VLAN ID[1 - 4094] ... (3)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-3)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()


MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (7)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (7)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-4)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (8)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (8)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (9)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (142)

2. C-VLAN ID[1 - 4094] ... (9)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()
Connecting Bundles to the E1 Ports

configured above:

MP-4100
Redundancy > (None)

2. User Name ... ()
5. Data OOS[0 - ff] ... (00)

MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links >Destination Port (-)
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1> Link 1 (Up).
MP-4100

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)
MP-4100
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1

5. To save and activate the new configuration, press the % key.
seconds).
Configuring Equipment at Location C
Configuring the Clock Source

1. Configure the system clock source to use the recovered clock signal of E1
link 1 of the M8E1 in I/O slot 1, using Configuration>System>Clock
Source>Source>Rx Clock>Master Port.
MP-4100
Entry Num Slot Port

2 None -
| 3 None -
v 4 None -
5 None -
6 None -
7 None -
2. Type <ESC> for previous screen, and then select Fallback Port to configure
the fallback clock source to use the recovered clock signal of E1 link 1 of the
M8E1 in I/O slot 6.
MP-4100
Configuration>System>Clock Source>Fallback Port
Entry Num Slot Port

2 None -
| 3 None -
v 4 None -
5 None -
6 None -
7 None -

1. Activate the first GBE port on CL-A, using Configuration>Physical Layer>
CL>CL-A>LAN>GbE 1.
MP-4100

5. User Name ... ()
2. Activate the first GBE port on CL-B, using Configuration>Physical Layer>

CL>CL-B>LAN>GbE 1.
MP-4100

5. User Name ... ()
3. Activate all of the 8 E1 ports on I/O slot 1, using Configuration>Physical

Layer>IO> I/O-1 (M8E1)>E1>All Links.
MP-4100
Redundancy > (None)

2. User Name ... ()
5. Data OOS[0 - ff] ... (00)
5. Repeat the same configuration steps for I/O slots 2, 4 and 5.
Configuration> Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Down).
MP-4100

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)

8. Repeat Step 6 for I/O slot 6.
Configuring Bundles
MP-4100
1. Slot > (IO-1)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)
MP-4100
... (P)
page):
MP-4100
1. Slot > (IO-2)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-2)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-3)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-3)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-4)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (16384)

1. Slot > (IO-4)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-5)

2. Bundle[1 - 32] ... (1)
MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-5)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

MP-4100
1. Slot > (IO-6)

2. Bundle[1 - 32] ... (1)

MP-4100
Rate(Kbps)[64 - 16384] (8192)

1. Slot > (IO-6)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. MLPPP MTU[80 - 1600] ... (250)
... (N)

1. Open Configuration>Applications> Ethernet Services>Flows.
MP-4100
1. Flow[1 - 250] ... (1)
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()
flow.
MP-4100

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (4)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (1)

2. C-VLAN ID[1 - 4094] ... (4)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-1)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()
MP-4100

1. Unaware
2. Aware
9. Type <ESC>.
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()

MP-4100
1. Flow[1 - 250] ... (2)

2. User Name ... ()
flow.
MP-4100

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (5)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (36)

2. C-VLAN ID[1 - 4094] ... (5)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-2)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (359)

2. C-VLAN ID[1 - 4094] ... (6)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-A)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (71)

2. C-VLAN ID[1 - 4094] ... (6)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-3)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()


MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (7)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (7)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (IO-4)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

2. Type a to add a flow
MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (8)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (106)

2. C-VLAN ID[1 - 4094] ... (8)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (16384Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (379)

2. C-VLAN ID[1 - 4094] ... (9)
3. SP-VLAN[0 - 4094] ... (0)
4. Slot > (CL-B)
Port > (GbE 1)
Rate > (1Gbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (142)

2. C-VLAN ID[1 - 4094] ... (9)
3. SP-VLAN[0 - 4094] ... (0)
Slot > (IO-5)
Port > (Bnd 1)
Rate > (8192Kbps)
BP User Name ... ()
7. Type S to save and then type <ESC> twice
Connecting Bundle to the E1 Ports

configured above:

MP-4100
Redundancy > (None)

2. User Name ... ()
5. Data OOS[0 - ff] ... (00)

MP-4100
...ical Ports>IO>I/O-1 (M8E1)>E1>All Links>Destination Port (-)
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1
1. Open Configuration>Physical Layer>IO>I/O-3 (M8E1)>E1>Link 1 (Up).
MP-4100

2. User Name ... ()
6. Data OOS[0 - ff] ... (00)
MP-4100
1. Link 2
2. Link 3
3. Link 4
4. Link 5
5. Link 6
6. Link 7
7. Link 8
8. Bundle 1

6. To save and activate the new configuration, press %.
seconds).
5.3 Configuration Procedure for Typical SONET

Transport Application
Overview
This section provides detailed configuration procedures for a typical
Megaplex-4100 application that enables transport of TDM and Ethernet traffic in
a SONET ring. The application topology is shown in Figure 5-2.
Location B Location A
Link 1 Link 1
on CL A on CL A
Link 1 Megaplex-4100 B SONET Megaplex-4100 A Link 1

on CL B on CL B
Ring
Location C
Megaplex-4100 C
Link 1 Link 1
on CL A on CL B
Figure 5-2. Network Topology for SONET Application
In this application, three Megaplex-4100 units are interconnected in a SONET

ring. To achieve both link and hardware protection, the connection to the ring is
made via OC-3 ports located on different CL modules (one OC-3 port on CL
module A, and the other on CL module B).
The ring operates as a stand-alone network, and therefore its timing source, as
well as the timing service of the SDH/SONET subsystem, is the internal oscillator
of the Megaplex-4100 at Location A. The other sites will lock their system (nodal)
time to the timing recovered from the SONET line signal.
The I/O modules installed at Location A and B are connected through PDH port 1;
bypass connections at Location C ensure ring connectivity. The traffic carried by
PDH 1 also includes HDLC bundles with a bandwidth of 128 kbps, supported by
means of the M8T1 module in I/O slot 1.
For maximum protection, path protection is enabled for PDH 1, with the
protection partner located on the adjacent CL module.
Network management is performed by an SNMP-based network management
station, for example, RADview NMS PC, using an out-of-band connection via a
5-44 Configuration Procedure for Typical SONET Transport Application Megaplex-4100 Ver. 2.0
serial or Ethernet port. Management communication to other Megaplex-4100

units is transferred inband, over the SONET links, through the DCC.
Configuration Sequence
For each of the 3 sites (Location A, Location B, Location C, in that order), the
configuration sequence is as follows:
1. Preliminary configuration.
2. Configuring the SDH/SONET subsystem of the CL modules for SONET (OC-3
framing).
3. Configuring the clock sources.
4. Configuring the physical ports and assigning timeslots to I/O ports and
bundles.
5. Mapping the PDH ports to the OC-3 ports.
6. Adding bundles.
7. Interconnecting bundles to form flows.
8. Connecting the bundles to their T1 ports.
Preliminary Configuration (All Sites)

1. Connect a terminal to the CONTROL DCE connector of the active CL module.
Make sure to use VT-100 supervision terminal emulation.
2. Configure the supervision terminal for communication with the
Megaplex-4100. Megaplex-4100 default configuration is as follows:
115.2 kbps, one start bit, eight data bits, no parity, one stop bit. Select
full-duplex mode, echo off, and disable flow control.
3. If the power-up initialization has not yet been completed, you may see the
decompression and initialization process. In this case, wait for a few seconds,
and then press <Enter> several times.
4. Type the default user name (su) and password (1234).
MP-4100
USER NAME: su
PASSWORD: ****
5. Set the factory default parameters for the Megaplex-4100, using

Configuration>System>Factory Default.
6. Press Y to confirm.
7. Set the time and date, using Configuration>System>Date & Time.
8. Load the hardware configuration (the installed modules), using
Configuration>DB Tools>Load HW, and then press Y to confirm.
Y to confirm.
Megaplex-4100 Ver. 2.0 Configuration Procedure for Typical SONET Transport Application 5-45
Configuration File Update Is In Process will appear at the bottom of the

screen while the database is being saved (a few seconds).
10. Check the modules installed in the Megaplex-4100 chassis, using
Inventory>SW/HW Rev.
MP-4100
Inventory>SW/HW Rev

PS-A PS PS
PS-B PS PS
| CL-A CL1/155 0. 1/ 0.1 1.50A0/ 1.9 CL1/155
v CL-B CL1/155 0. 1/ 0.1 1.50A0/ 1.9 CL1/155
IO-1 M8T1 1 1.2 M8T1
IO-2 M8T1 1 1.2 M8T1
IO-3 HSF-2 4 1.05 HSF-2
IO-4 HS-12/N 2 6.00 HS-12/N
IO-5 HS-R/N 6 55.00 HS-R/N
IO-6 VC-8/FXO 2 8.00 VC-8/FXO
IO-7 VC-8/FXS 10 13.00 VC-8/FXS
IO-8 VC-8/E&M 10 13.00 VC-8/E&M
11. Configure the Megaplex-4100 management IP address and other IP

communication parameters, using Configuration>Quick Setup.
MP-4100
1. Host IP Address... (172.17.191.100)

2. Subnet Mask ... (255.255.255.0)
3. Default Gateway... (172.17.191.153)
12. Configure the Megaplex-4100 IP agent name, using Configuration>System>

Management>Device Info.
MP-4100
Sys Description... (Sys type:MP-4100 Sys Ver:1.50A0 Chassis Revision:0)

1. Device Name ... (MP4100)
2. Contact Person ... (Name of contact person )
3. Location ID ... (The location of this device )
Configuring Equipment at Location A
Configuring SDH/SONET Subsystems

1. Configure the SDH/SONET subsystems on the CL modules to work with OC-3
framing, using Configuration> Physical Layer>CL>CL-A>SDH/SONET>Card
Configuration. Your selection is automatically copied to the other CL module.
MP-4100
1. Frame Structure (OC-3)

2. Tx Clock Based on SSM (Yes)
2. You will be asked to confirm: press Y.

3. Configure the timing mode of the SDH/SONET subsystem of CL module A to
Internal (first, select No for Tx Clock Based on SSM).
MP-4100

3. SONET Tx Clock (Internal)
4. You may leave the Common PDH LVC Parameters default values unchanged.
5. Configure CL module B the same as CL module A (repeat Steps 3, 4 on CL-B).
Configuring OC-3 Physical Layer

1. Enable OC-3 port 1 of CL module A, using Configuration>Physical Layer>
CL>CL-A>SDH/SONET>Link 1.
MP-4100

2. User Name ... ()
2. Configure the OC-3 port 1 of CL module A for inband management using the
RAD proprietary management protocol, over DCC bits D4 to D12. Use
Configuration>Physical Layer>CL>CL-A>SDH/SONET>Link 1>DCC Configuration.
MP-4100
1. In Band Management> (HDLC)

2. Routing Protocol > (Proprietary RIP)
3. Disable OC-3 port 2 of CL module A, using Configuration>Physical Layer>

MP-4100

2. User Name ... ()
4. Repeat Steps 1, 2, 3 above for the OC-3 ports of CL module B, using

Configuration>Physical Layer>CL>CL-B>SDH/SONET>Link 1 and Link 2.
Configuring System Clock Sources

Configure the system to use the timing of the SDH/SONET subsystem as the clock
source, using Configuration>System>Clock Source.
MP-4100
1. Source > (S Subsystem)
Configuring and Mapping the PDH Ports

1. Activate PDH port 1 (which is the port used to carry the TDM and Ethernet
traffic in this example), using Configuration>Logical Layer>CL>PDH>PDH 1.
MP-4100

2. User Name ... ()
6. Restoration Time > (10 Seconds(62411))
7. Idle Code[0 - ff] ... (7F)
2. Configure the LVC parameters of PDH 1, and enable path protection with
automatic mapping on the adjacent CL (CL module B), using
Configuration>Logical Layer> CL>PDH>PDH 1>LVC Configuration.
Note Timeslot assignment for PDH 1 will be performed after configuring the Ethernet
bundles, and the physical ports of the I/O modules that will connect to PDH 1.
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Up)>LVC Configuration

3. Padding (Nulls)
9. Payload Label [0 - 7] ... (2)
3. Map PDH 1 to the desired TUG of OC-3 link 1 of CL-A, using

Configuration>System>Mapping> CL-A>Link 1.
MP-4100
STS1-1 STS1-2
->>
1. None 3. L2A-TU3 5. L2A-VT
2. PDH1 4. L2B-TU3 6. L2B-VT
4. Since automatic protection mapping is enabled, the protection PDH for PDH 1
of CL module A is mapped to the same PDH on CL module B, link 1. Check
using Configuration>System>Mapping>CL-B>Link 1.
MP-4100
Configuration>System>Mapping>CL-B>Link 1
STS1-1 STS1-2
TUG2-1 P-PDH1 None None None None None None None None
->>
2. PDH1 4. L2B-TU3 6. L2B-VT
Configuring I/O Ports on Other Modules

1. Activate HSF-2 ports 1 and 2, set each port to 64 kbps (1 x 64 kbps), and
connect the ports to CL port PDH 1, using Configuration>Physical Layer>IO>
I/O-3 (HSF-2)>All Ports.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>All Ports

2. Rate > (1 Ts)
3. Destination Slot > (CL(CL1/155))
4. Destination Port > (PDH 1)

3. Activate HS-6/N ports 1 and 2, set them for 128 kbps (2 x 64 kbps), and
connect them to CL port PDH 1:
1. Open Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 1 (Down)

2. Rate > (2x64 )
3. Clock Mode > (DCE)
4. CTS > (ON)
5. Fifo Size > (AUTOMATIC)
6. Operation Mode > (BI-DIR)
2. Select Port 2 and repeat the procedure.

4. Activate HS-R/N ports 1 and 2, set them for 9.6 kbps, and connect them to
CL port PDH 1:
1. Open Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1 (Up)

2. Format > (SYNC)
3. Rate > (9.6 KBPS)
4. Encapsulation Mode (Bandwidth Optimized)
5. CTS > (ON)
6. DCD & DSR > (Local)
2. Select Port 2 and repeat the procedure.

5. Configure the VC-8/FXO card:
1. Configure the VC-8/FXO card parameters, using Configuration>Physical

Layer>IO> I/O-6 (VC-8/FXO)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration
1. Coding Law (u LAW)

2. Signaling > (RBMF SIGNALING)
3. Encoding (PCM)
4. Metering > (12K)
2. Configure Port 1 and connect it to CL port PDH 1.

MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Port 1 (Down)
2. Transmit Level > (0.0)
3. Receive Level > (0.0)
4. Wires Number (2 WIRES)
5. Interface (LOOP START)
6. Signaling Feedback> (No)
7. Echo Canceler (Disable)
3. Configure Port 2 and connect it to CL port PDH 1, using the same

procedure.
6. Configure the VC-8/FXS card:
1. Configure the VC-8/FXS card parameters, using Configuration>Physical
Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration

3. Encoding (PCM)
4. Metering > (12K)

MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 1 (Up)


procedure.
7. Configure the VC-8/E&M card:
1. Configure the VC-8/E&M card parameters, using Configuration>Physical
Layer>IO>I/O-8 (VC-8/E&M)> Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration

3. Encoding (PCM)Open ports 1 and 2 and relate them to PDH 1 of the
CL:

MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Port 1 (Down)

6. Type > (SSDC5)

procedure.
Configuring Ethernet Bundles

1. Enable the ETH port on the M8T1 card in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1(Down)

2. User Name ... ()
4. Max Capability Advertised > (100 Mbps Full Duplex)
6. Link OAM(802.3ah) (Disable)
2. Add a HDLC bundle on the PDH 1 port, supported by means of the M8T1
module in I/O slot 1:
MP-4100
1. Slot > (IO-1)

2. Bundle[1 - 32] ... (1)
5. Type a and add a HDLC bundle, with a bandwidth of 128 kbps (two
timeslots).
MP-4100
Rate(Kbps)[64 - 16384] (128)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. Number Of TS[1 - 32] ... (2)
8. Source Slot > (CL-A)
9. Source Port > (PDH 1)
6. Type a and add a second HDLC bundle, with a bandwidth of 128 kbps
(two timeslots).
MP-4100
Rate(Kbps)[64 - 16384] (128)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (2)
4. User Name ... ()
6. Number Of TS[1 - 32] ... (2)
9. Source Port > (PDH 1 )
3. Configure a flow for bundle 1:

MP-4100
1. Flow[1 - 250] ... (1)
2. Type a to add a new flow.
MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()
3. Select Bridge Port Mapping to map the required bridge ports to the flow:
MP-4100

MP-4100
BP[1 - 512] ... (1)

C-VLAN ID[1 - 4095] ... (0)
SP-VLAN[0 - 4095] ... (0)
2. Slot > (IO-1)
Port > (Bnd 1)
Rate > (128Kbps)
BP User Name ... ()

6. Type S for save and then type <ESC>.
MP-4100
BP[1 - 512] ... (33)

C-VLAN ID[1 - 4095] ... (0)
SP-VLAN[0 - 4095] ... (0)
2. Slot > (IO-1)
Port > (ETH 1)
Rate > (100Mbps)
BP User Name ... ()

MP-4100

4. Configure an additional flow for bundle 2, using the same procedure as for
the first flow.
Assign Timeslots on PDH Port 1

1. Open the timeslot assignment menu for PDH port 1, and select Manual
assignment (Configuration>System>TS Assignment>CL>PDH 1>Manual).
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Manual

TS 01 ---- ---- -- -
TS 02 ---- ---- -- -
| TS 03 ---- ---- -- -
v TS 04 ---- ---- -- -
TS 05 ---- ---- -- -
TS 06 ---- ---- -- -
TS 07 ---- ---- -- -
TS 08 ---- ---- -- -
1. ---- 2. Split 3. CL (CL1/155)

... (N)
2. Assign the prescribed timeslots to each I/O port or Ethernet bundle (use the
keyboard arrow keys to move the cursor):
1. Start by moving the cursor to the desired PDH port timeslot, in the Ts#
column.
2. Move the cursor to the Slot column in the same row, and then select the
desired I/O module from the list of modules that require mapping to PDH
port 1 (displayed at the bottom of the page.
3. If the timeslot must use split timeslot allocation, then select Split in this
row, and skip to the next PDH port timeslot.
4. Move the cursor to the Port column in the same row, and then select the
desired port from the list of ports of the selected I/O module that require
mapping to PDH port 1 (displayed at the bottom of the page).
5. Move the cursor to the Ts column in the same row (the first timeslot that
is a candidate for being connected to the PDH port is automatically
displayed), and then select the prescribed I/O module timeslot.
6. Move the cursor to the Type column in the same row (the timeslot type
that should be selected is automatically displayed by default), and then
select the prescribed timeslot type.
7. Repeat the process for all the ports and bundles that must be connected
to PDH port 1.
MP-4100

TS 01 IO-3 (HSF-2) CH 1 -- DATA
| TS 03 IO-4 (HS-12/N) CH 1 -- DATA
v TS 04 IO-4 (HS-12/N) CH 1 -- DATA
TS 05 IO-4 (HS-12/N) CH 2 -- DATA
TS 06 IO-4 (HS-12/N) CH 2 -- DATA
TS 07 Split - -- DATA
TS 09 IO-6 (VC-8/FXO) CH 1 -- VOICE
| TS 11 IO-7 (VC-8/FXS) CH 1 -- VOICE
v TS 12 IO-7 (VC-8/FXS) CH 2 -- VOICE
TS 13 IO-8 (VC-8/E&M) CH 1 -- VOICE
TS 15 IO-1 (M8T1) BND 1 -- DATA
3. On the timeslot assignment menu for PDH port 1, select Split assignment,
and configure the bits in timeslot 7 using Configuration>System>TS
Assignment>CL>PDH 1>Split>TS 7.
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Split>TS 7
1. Bit 1 ... (05:01)

2. Bit 2 ... (05:01)
3. Bit 3 ... (------)
4. Bit 4 ... (------)
5. Bit 5 ... (------)
6. Bit 6 ... (------)
7. Bit 7 ... (------)
8. Bit 8 ... (------)
Y to confirm. Configuration File Update is in Process will appear in the bottom
of the screen while the database is being updated (a few seconds).
Configuration Equipment at Location B

MP-4100


Configuring OC-3 Physical Ports

MP-4100

2. User Name ... ()
MP-4100


MP-4100

2. User Name ... ()

Configuring the Timing and Clock Sources

use the recovered clocks from the active SONET link as reference source,
using Configuration> Physical Layer>CL>CL-A> SDH/SONET>Card
Configuration:
1. Select No for Tx Clock Based on SSM.
2. Select Rx Clock for SONET Tx Clock. The Master and Fallback sources are
automatically set to Link 1 (the only active link of the module).
MP-4100
1. Frame Structure (OC-3 )

3. SONET Tx Clock > (Rx Clock)
2. Configure CL module B the same as CL module A (repeat Step 1 on CL-B).

3. Configure the system to use the timing of the SDH/SONET subsystem as the
clock source, using Configuration>System>Clock Source.
MP-4100
Configuring and Mapping the PDH Ports

1. Activate PDH port 1 (which is the port used to carry the TDM and Ethernet
traffic in this example), using Configuration>Logical Layer>CL>PDH>PDH 1.
MP-4100

2. User Name ... ()
7. Idle Code[0 - ff] ... (7F)
2. Configure the LVC parameters of PDH 1, and enable path protection with
automatic mapping on the adjacent CL (CL module B), using
Configuration>Logical Layer> CL>PDH>PDH 1>LVC Configuration.
Note Timeslot assignment for PDH 1 will be performed after configuring the Ethernet
bundles, and the physical ports of the I/O modules that will connect to PDH 1.
MP-4100
Configuration>Logical Layer>CL>PDH>PDH 1(Up)>LVC Configuration

3. Padding (Nulls)
9. Payload Label [0 - 7] ... (2)
3. Map PDH 1 to the desired TUG of OC-3 link 1 of CL-A, for example, TUG-2 1
(this mapping must match the mapping at the far end of the link). Use
Configuration>System>Mapping> CL-A>Link 1.
MP-4100
STS1-1 STS1-2
->>
2. PDH1 4. L2B-TU3 6. L2B-VT
4. Since automatic protection mapping is enabled, the protection PDH for PDH 1
of CL module A is mapped to the same PDH on CL module B, link 1. Check
using Configuration>System>Mapping>CL-B>Link 1.
MP-4100
STS1-1 STS1-2
TUG2-1 P-PDH1 None None None None None None None None
->>
2. PDH1 4. L2B-TU3 6. L2B-VT
Configuring the I/O Ports of M8T1 Modules

1. Activate T1 port 1 on the M8T1 module in I/O slot 1 (the port used to carry
the TDM and Ethernet traffic in this example), and configure it to use
dual-cable parallel Tx redundancy, with the same port of the M8T1 module in
I/O slot 2. Use Configuration>Physical Layer>IO> I/O-1 (M8T1)> T1>Link 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>T1>Link 1 (Down)
Primary > (Yes)

2. User Name ... ()
3. Line Type > (ESF)
4. Signaling Profile > (1)
5. Idle Code[0 - ff] ... (7F)
6. Redundancy > (Dual Cable P. TX)
7. Voice OOS[0 - ff] ... (00)
8. Data OOS[0 - ff] ... (FF)
9. OOS Signaling > (Forced Idle)
... (N)
MP-4100
... (P)
12. In Band Management > (Dedicated FR)
13. Routing Protocol > (None)
14. Redundancy Slot > (IO-2 (M8T1))
15. Redundancy Channel > (Link 1)
16. Wait To Restore[0 - 999] ... (0)
17. Line Code > (B8ZS)
18. Line Interface > (CSU)
19. Attenuation(CSU)/Length (DSU) > (0 dB)
2. Activate T1 port 2 on the M8T1 module in I/O slot 1 (the port is used to carry
Ethernet traffic in this example). Use Configuration>Physical Layer>IO> I/O-1
(M8T1)> T1>Link 2.
MP-4100

2. User Name ... ()
3. Line Type > (ESF)
4. Signaling Profile > (1)
5. Idle Code[0 - ff] ... (7F)
7. Voice OOS[0 - ff] ... (00)
8. Data OOS[0 - ff] ... (00)
9. OOS Signaling > (Forced Idle)
3. Check that the T1 port parameters of the M8T1 module in I/O slot have been
copied to the redundancy partner port (T1 port 1 of the M8T1 module in I/O
slot 2), using Configuration> Physical Layer>IO>I/O-2 (M8T1)>T1>Link 2.
Configuring I/O Ports on Other Modules

1. Activate HSF-2 port 1, set it to 64 kbps (1 x 64 kbps), and connect the port
to CL port PDH 1, using Configuration>Physical Layer>IO> I/O-3 (HSF-2)> Port
1.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>Port 1 (Down)

2. Rate > (1 Ts)
2. Activate HSF-2 port 2, set it to 64 kbps (1 x 64 kbps), and connect the port
to T1 port 1 of the M8T1 module in I/O slot 1, using Configuration> Physical
Layer>IO> I/O-3 (HSF-2)> Port 2.
MP-4100
Configuration>Physical Layer>IO>I/O-3 (HSF-2)>Port 2 (Down)

2. Rate > (1 Ts)
3. Destination Slot > (IO-1 (M8T1))
4. Destination Port > (Link 1)
3. Activate HS-6/N port 1, set it for 128 kbps (2 x 64 kbps), and connect the
port to CL port PDH 1, using Configuration>Physical Layer>IO>I/O-4
(HS-6/N)>Port 1.
MP-4100

2. Rate > (2x64 )
4. CTS > (ON)
4. Activate HS-6/N port 2, set it for 128 kbps (2 x 64 kbps), and connect the
port to T1 port 1 of the M8T1 module in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-4 (HS-6/N)>Port 2.
MP-4100

2. Rate > (2x64 )
4. CTS > (ON)
5. Activate HS-R/N port 1, set it for 9.6 kbps, and connect the port to CL port
PDH 1, using Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1.
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 1 (Up)

2. Format > (SYNC)
5. CTS > (ON)
6. Activate HS-R/N port 2, set it for 9.6 kbps, and connect the port to T1 port 1
of the M8T1 module in I/O slot 1, using Configuration>Physical Layer>IO>
I/O-5 (HS-R/N)>Port 2.
MP-4100
Configuration>Physical Layer>IO>I/O-5 (HS-R/N)>Port 2 (Down)

2. Format > (SYNC)
5. CTS > (ON)
7. Configure the VC-8/FXO card:

1. Configuration the VC-8/FXO card parameters, using
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-6 (VC-8/FXO)>Card Configuration

3. Encoding (PCM)
4. Metering > (12K)

MP-4100
3. Configure Port 2 and connect it to T1 port 1 of the M8T1 module in I/O

slot 1, using the same procedure.
MP-4100

8. Configure the VC-8/FXS card:

1. Configure the VC-8/FXS card parameters, using Configuration>Physical
Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Card Configuration

3. Encoding (PCM)
4. Metering > (12K)

MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 1 (Up)


MP-4100
Configuration>Physical Layer>IO>I/O-7 (VC-8/FXS)>Port 2 (Down)

9. Configure the E&M card parameters:

1. Configure the VC-8/E&M card parameters, using Configuration>Physical
Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration.
MP-4100
Configuration>Physical Layer>IO>I/O-8 (VC-8/E&M)>Card Configuration

3. Encoding (PCM)Open ports 1 and 2 and relate them to PDH 1 of the
CL:

MP-4100

6. Type > (SSDC5)

MP-4100

6. Type > (SSDC5)
Configuring Ethernet Bundles

1. Enable the ETH port on the M8T1 card in I/O slot 1, using
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1.
MP-4100
Configuration>Physical Layer>IO>I/O-1 (M8T1)>Ethernet>ETH 1(Down)

2. User Name ... ()
4. Max Capability Advertised > (100 Mbps Full Duplex)
6. Link OAM(802.3ah) (Disable)
2. Add a HDLC bundle on the CL PDH 1 port, supported by means of the M8T1
module in I/O slot 1:
MP-4100
1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
2. Type a to add a HDLC bundle on the CL PDH 1 port, with a bandwidth of

128 kbps (two timeslots).
MP-4100
Rate(Kbps)[64 - 16384] (128)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (1)
4. User Name ... ()
6. Number Of TS[1 - 32] ... (2)
9. Source Port > (PDH 1)
3. Type a and add a second HDLC bundle on the T1 port 2 of the M8T1 module
in I/O slot 1, with a bandwidth of 128 kbps (two timeslots).
MP-4100
Rate(Kbps)[64 - 16384] (128)

1. Slot > (IO-1)
2. Bundle[1 - 32] ... (2)
4. User Name ... ()
6. Number Of TS[1 - 32] ... (2)
4. Configure a flow for bundle 1:

MP-4100
1. Flow[1 - 250] ... (1)
2. Type a to add a new flow.

MP-4100
1. Flow[1 - 250] ... (1)

2. User Name ... ()
3. Select Bridge Port Mapping to map the required bridge ports to the flow:
MP-4100

MP-4100
BP[1 - 512] ... (1)

C-VLAN ID[1 - 4095] ... (0)
SP-VLAN[0 - 4095] ... (0)
2. Slot > (IO-1)
Port > (Bnd 1)
Rate > (128Kbps)
BP User Name ... ()

MP-4100
BP[1 - 512] ... (33)

C-VLAN ID[1 - 4095] ... (0)
SP-VLAN[0 - 4095] ... (0)
2. Slot > (IO-1)
Port > (ETH 1)
Rate > (100Mbps)
BP User Name ... ()

MP-4100

1. Unaware
2. Aware
5. Configure an additional flow for bundle 2, using the same procedure as for
the first flow.
Assign Timeslots on CL PDH Port 1

1. Open the timeslot assignment menu for CL PDH port 1, and select Manual
assignment, using Configuration>System>TS Assignment>CL>PDH 1>Manual.
MP-4100

TS 01 ---- ---- -- -
TS 02 ---- ---- -- -
| TS 03 ---- ---- -- -
v TS 04 ---- ---- -- -
TS 05 ---- ---- -- -
TS 06 ---- ---- -- -
TS 07 ---- ---- -- -
TS 08 ---- ---- -- -
1. ---- 2. Split 3. CL (CL1/155)

... (N)
2. Manually assign the prescribed timeslots to each I/O port or Ethernet bundle
(use the keyboard arrow keys to move the cursor), using the procedure
described on page 5-55.
MP-4100

| TS 03 IO-4 (HS-12/N) CH 1 -- DATA
v TS 04 IO-4 (HS-12/N) CH 1 -- DATA
TS 05 IO-4 (HS-12/N) CH 2 -- DATA
TS 06 IO-4 (HS-12/N) CH 2 -- DATA
| TS 11 IO-7 (VC-8/FXS) CH 1 -- VOICE
v TS 12 IO-7 (VC-8/FXS) CH 2 -- VOICE
and configure the bits in timeslot 7 using Configuration>System>
TS Assignment>CL>PDH 1>Split>TS 7.
MP-4100
Configuration>System>TS Assignment>CL>PDH 1(Up)>Split>TS 7
1. Bit 1 ... (05:01)

2. Bit 2 ... (05:01)
3. Bit 3 ... (------)
4. Bit 4 ... (------)
5. Bit 5 ... (------)
6. Bit 6 ... (------)
7. Bit 7 ... (------)
8. Bit 8 ... (------)
Assign Timeslots on M8T1 Ports

1. Open the timeslot assignment menu for T1 port 1, and perform manual
timeslot assignment to the various I/O ports using Configuration>System>TS
Assignment>IO>I/O-1 (M8T1)> Link 1>Manual. Use the procedure described
on page 5-55.
MP-4100
Configuration>System>TS Assignment>IO>I/O-1 (M8T1)>Link 1>Manual

TS 01 ---- ---- -- -
TS 02 ---- ---- -- -
| TS 03 ---- ---- -- -
v TS 04 ---- ---- -- -
TS 05 ---- ---- -- -
TS 06 ---- ---- -- -
TS 07 ---- ---- -- -
TS 08 ---- ---- -- -
2. Open the timeslot assignment menu for T1 port 2, and perform manual
timeslot assignment for the Ethernet bundles, using
Configuration>System>TS Assignment>IO>I/O-1 (M8T1)> Link 2>Manual. Use
the procedure described on page 5-55.
3. To save and activate the new configuration press the % key.
4. Press Y to confirm. Configuration File Update Is In Process will appear in the
bottom of the screen while the database is being saved (a few seconds).
Configuration Equipment at Location C

MP-4100


Configuring OC-3 Physical Ports

MP-4100

2. User Name ... ()
MP-4100


MP-4100

2. User Name ... ()

Configuring the Timing and Clock Sources

use the recovered clocks from the active SONET link as reference source,
using Configuration> Physical Layer>CL>CL-A> SDH/SONET>Card
Configuration:
1. Select No for Tx Clock Based on SSM.
2. Select Rx Clock for SONET Tx Clock. The Master and Fallback sources are
automatically set to Link 1 (the only active link of the module).
MP-4100
1. Frame Structure (OC-3 )

3. SONET Tx Clock > (Rx Clock)
2. Configure CL module B the same as CL module A (repeat Step 1 on CL-B).

3. Configure the system to use the timing of the SDH/SONET subsystem as the
clock source, using Configuration>System>Clock Source.
MP-4100
Bypassing PDH Ports

1. To close the protection path through the SONET ring, it is necessary the
bypass the prescribed TUs between CL-A to CL-B. In this example, it is
necessary to bypass the TUs that carry the PDH 1 payload from Location A to
Location B. Start from OC-3 link 1 of the CL module A, using
Configuration>System>Mapping>CL-A>Link 1.
MP-4100
STS1-1 STS1-2
->>
1. None 3. L1B-TU3 5. L1B-VT 7. L2B-VT
2. L2A-TU3 4. L2B-TU3 6. L2A-VT
3. Use the keyboard arrow keys to move the cursor to the TU to be

bypassed to CL module B.
4. Select L1B-VT. After pressing <Enter>, you will see the map of the other
active link, link 1 of CL module B.
MP-4100
STS1-1 STS1-2
->>
1. SET
5. Use the keyboard arrow keys to move the cursor to the TU to be

bypassed to CL module A.
6. Select SET.
7. To save and activate the new configuration, press the % key.
8. Press Y to confirm. Configuration File Update Is In Process will appear at
the bottom of the screen while the database is being saved (a few
seconds).
Chapter 6
Troubleshooting and
Diagnostics
This Chapter describes the Megaplex-4100 monitoring and diagnostic functions.
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
• Diagnostic tests for checking transmission paths and IP connectivity.
These functions can be used to identify problems in the network incorporating
Megaplex-4100 units, test the proper operation of each Megaplex-4100 unit, and
locate rapidly the cause of the fault: within the Megaplex-4100 itself, in its
connections to the network or to a user’s equipment unit, or in the 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 the
Installation and Operation Manual of each module.
If you need additional support for this product, see Section 6.6 for technical
support information.
6.1 Monitoring Performance

Megaplex-4100 supports the following types of monitoring activities:
• Display performance monitoring statistics for the Megaplex-4100 physical and
virtual ports. 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 Megaplex-4100, the collected data can be used for diagnostic
purposes, because it can help identify the source of the problem.
The data is continuously collected during equipment operation. For TDM
ports, the basic performance data is calculated for each second, and
accumulated and displayed over a 15-minute (900 second) interval. The data
accumulated within the last 24-hour interval is also stored and displayed.
Megaplex-4100 Ver. 2.0 Monitoring Performance 6-1

Chapter 6 Troubleshooting and Diagnostics Installation and Operation Manual
• Display status information for system timing and control subsystems and for
physical and virtual ports
• Display the current APS and path protection status for Megaplex-4100 with
• Read the alarm history recorded in the log file, and clear desired alarms
• Read the current alarms. You can select the type of alarms to be displayed,
using various cross-sections to filter the relevant alarms.
The monitoring tasks are organized in accordance with three main types:
• System
• Physical Layer
• Logical Layer.
The selection of the desired type of monitoring activity is made on the
Monitoring task selection screen. A typical screen is shown in Figure 6-1.
MP-4100
Monitoring
1. System >
2. Physical Layer >
3. Logical Layer >
>

-----------------------------------------------------------------------------
Figure 6-1. Monitoring – Task Selection Screen
³ To select a monitoring activity:

Type its number and then press <Enter>.
Overview of Monitoring Menu

Figure 6-2 to Figure 6-5 show the typical structure of the Monitoring menu.
6-2 Monitoring Performance Megaplex-4100 Ver. 2.0

Installation and Operation Manual Chapter 6 Troubleshooting and Diagnostics
Figure 6-2. Typical Monitoring Menu Structure (SDH) (Part 1 of 2) layer



Monitoring
1. System
2. Physical Layer
3. Logical Layer
System
2. Active Alarms (ALL) See Typical
3. Clear Alarms Part 1 I/O-3
4. History Alarms
5. Timing
6. CL Status 1. Link 1
7. Remote Agents 2. Link 2 I/O Modules with
3. Link 3 Redundancy
8. APS
.. Ethernet
Only
.. Link 1 Status
Logical Layer 1. Status
Only for 2. Statistics
1. I/O E1 and T1 Ports 3. Signaling
2. CL with CAS
Signaling
I/O Modules with

I/O Link 1 Current Interval
Physical Layer Ethernet
1. I/O-1 (HS-U12) 1. Current (15 min)
1. I/O 2. I/O-2 (M8T1) I/O-2 2. Select Interval (15 min) Select Interval
3. I/O-3 (M8T1) 3. Current (24 hours)
2. CL
.. 1. E1 or T1 or SHDSL SHDSL Only 4. Select Interval (24 hours)
.. 2. Ethernet 5. Clear Statistics Total
Select Interval
Ethernet
ETH 1
1. ETH 1 Status
2. ETH 2
1. Status
3. ETH 3
2. Statistics
Statistics
CL Station Clock
1. CL-A Port Status
2. CL-B Ethernet
GbE 1
1. GbE 1 ETH Counters
2. GbE 2 1. Port Status
CL-A 2. ETH Counters
Link Status
1. Station Clock
2. Ethernet
3. SDH/SONET Timing Link Statistics Current Interval
1. Current Interval
Link 1 2. Select Interval Select Interval
3. Total
1. Link Status
2. Link Statistics Total
SDH/SONET 3. DCC Statistics DCC Statistics
4. Optical Parameters
1. Timing
2. Link 1
3. Link 2 Optical Parameters
4. Path Protection Path Protection

Selecting a System Monitoring Task

Use the following procedure to select a desired system-level monitoring task.
There are two main groups of tasks:
• Alarm handling tasks
• Status monitoring tasks, regarding the timing subsystem, CL module status,
information regarding the remote management agents known to the
Megaplex-4100 management agent, and APS status when APS is in use.
To navigate to the required screen, use Monitoring>System.
A typical System task selection submenu is shown in Figure 6-6.
MP-4100
Monitoring>System
1. Active Alarms (ON) >

2. Active Alarms (ALL)>
3. Clear Alarms >
4. History Alarms []
5. Timing >
6. CL Status []
7. Remote Agents []
8. APS >
>

-----------------------------------------------------------------------------
Figure 6-6. Typical System Task Selection Submenu
³ To select the type of system-level monitoring task:

Type the desired number and then press <Enter>.
For details, refer to following Sections.
Displaying the Active Alarms

You can display the currently active state alarms by means of the Active Alarms
(ON) item.
Note
• A state alarm is an alarm that is in the ON state while a certain condition is
present, and automatically changes to OFF when the condition is no longer
present. This type of alarm cannot be cleared (removed from the alarm buffer)
while it is in the ON (active) state.
• An event alarm is an alarm that records the occurrence of an event. This type
of alarm can be cleared at any time.
Each alarm is displayed in a separate row, which lists from left to right:

• The alarm code

• The module, and where applicable, the port for which the alarm is reported
• The alarm description – a short string that concisely explains the meaning of
the alarm code
• The alarm severity
• The number of times the alarm occurred
• The masking status of the alarm: an M to the right of the alarm row indicates
that the corresponding alarm has been masked.
For a description of the alarms, refer to Handling Alarms and Traps.
³ To select the type of active alarms (ON) to be displayed:

1. Select Active Alarms (ON) on the Monitoring>System menu, and then press
<Enter>.
2. You will see the alarm screen. A typical screen is shown in Figure 6-7.
Note
To see the navigation options for this screen, select the ? (help) option.
MP-4100
Monitoring>System>Active Alarms (ON)
Alarm Description
(0026)PS-B MODULE TYPE MISMATCH MAJOR 1 M
(2021)CL-A CL FAN FAILURE MAJOR 1
| (0026)CL-B MODULE TYPE MISMATCH MAJOR 1
v (2007)IO-1 BUS CLOCK FAILURE MAJOR 1
(0026)IO-2 MODULE TYPE MISMATCH MAJOR 1
(2007)IO-3 BUS CLOCK FAILURE MAJOR 1
(0026)IO-4 MODULE TYPE MISMATCH MAJOR 1
>
C-Clear; %-Db Update; #-Db Undo; $-Sanity

Figure 6-7. Typical Active Alarms (ON) Screen

3. You can clear the alarm buffer by typing C (clear). In response, you will see an
ALARM BUFFER CLEANED message, and the number of alarms in the buffer,
appearing at the top right-hand corner of the screen, decreases accordingly.
³ To display the active alarms (ON):

An alternative display mode for the currently active alarms is the ALL mode, which
includes both state alarms and event alarms.
You can display the currently active alarms in three cross-sections:
• All the alarms
• Alarms at the system level

• Alarms related to a specific chassis slot.

In addition, you can mask alarms, and clear the alarm buffer. For a description of
all the alarms, refer to Section 6.3.
³ To select the type of active alarms (ALL) to be displayed:

1. Select Active Alarms (ALL) on the Monitoring>System menu, and then press
<Enter>.
2. You will see the Active Alarms (ALL) type selection screen. A typical screen is
shown in Figure 6-8. Next to each option, you can see the highest alarm
severity that is currently active.
MP-4100
Monitoring>System>Active Alarms (ALL)
1. All Alarms (MAJOR) []>

2. System Alarms (EVENT) []>
3. Slot Alarms >
>

-----------------------------------------------------------------------------
Figure 6-8. Typical Active Alarms (ALL) Type Selection Screen

3. Type the desired alarm type number, and then press <Enter>.
Note
³ To display all alarms, and system alarms:

1. A typical screen for the All Alarms selection is shown in Figure 6-9. The
System Alarms screen is similar.
In most cases, the number of alarms exceeds the maximum that can be
displayed on one page, and therefore you may have to scroll down to the
page containing the alarm of interest.

MP-4100
Monitoring>System>Active Alarms (ALL)>All Alarms (MAJOR)
Alarm Description Alarm Mask

(0001) OFF 0 No
(0026)PS-B MODULE TYPE MISMATCH MAJOR 1 Temporary
| (2021)CL-A CL FAN FAILURE MAJOR 1 No
v (0026)CL-B MODULE TYPE MISMATCH MAJOR 1 No
(2007)IO-1 BUS CLOCK FAILURE MAJOR 1 No
(0022)IO-1 MODULE WAS INSERTED EVENT 1 No
(0026)IO-2 MODULE TYPE MISMATCH MAJOR 1 No
1. No
2. Temporary
3. Permanent
>

-----------------------------------------------------------------------------
Figure 6-9. Typical Active Alarm (ALL) – All Alarms Screen

2. Each alarm is displayed in a separate row, which lists from left to right:
The alarm code
The module and port for which the alarm is reported
The alarm description – a short string that concisely explains the meaning
of the alarm code
The alarm severity
The number of times the alarm occurred.
The screen has an additional field, Alarm Mask, which displays the current
attribute of each alarm: Normal, Temporary, Permanent.
The description of the various attributes appears in the Use – Selecting the
Alarms Attribute section of Chapter 4.
Note
3. After displaying the desired set of alarms, you have the option to modify the
attribute of each alarm. The attribute modification menu is located under the
alarms list.
To change the attribute of an alarm, scroll to the desired alarm
Type the number of the desired attribute. The corresponding attribute of
the currently selected alarm changes to reflect the new selection.
Note
It is not possible to invert event alarms, but only state alarms.
4. You can clear the alarm buffer by typing C (clear). In response, you will see an
ALARM BUFFER CLEANED message, and the number of alarms in the buffer,
appearing at the top right-hand corner of the screen, decreases accordingly.

³ To display slot alarms:

1. For the Slot Alarms option, you will see the slot alarm status screen. A typical
The screen lists the highest alarm severity present in each slot.
MP-4100
Monitoring>System>Active Alarms (ALL)>Slot Alarms
PS-A (OFF) (PS) > IO-4 (MAJOR) (M8E1) >

PS-B (OFF) (PS) > IO-5 (MAJOR) (M8SL) >
CL-A (MAJOR) (CL1/155GbE) > IO-6 (OFF) (-------------) >
CL-B (MAJOR) (CL1/155GbE) > IO-7 (OFF) (-------------) >
IO-1 (MAJOR) (M8E1) > IO-8 (OFF) (-------------) >
IO-2 (MAJOR) (M8E1) > IO-9 (OFF) (-------------) >
IO-3 (MAJOR) (M8T1) > IO-10 (OFF) (-------------) >
>

-----------------------------------------------------------------------------
Figure 6-10. Typical Slot Alarms Status Screen
³ To clear the history alarms:

1. Select Clear Alarms on the Monitoring>System menu, and then press <Enter>.
³ To display the recent history alarms:

1. Select History Alarms on the Monitoring>System menu, and then press
<Enter>.
2. You will see the History Alarms screen. A typical History Alarms screen is
MP-4100
Monitoring>System>History Alarms
Alarm Description
(0020)CL-A INTERNAL ERROR (26990649) EVENT 13-08-2099 02:33:08
(0003) ACTIVE DB HAS BEEN UPDATED EVENT 13-08-2099 02:15:09
| (0025)IO-3 NOT PROGRAMMED MODULE OFF 13-08-2099 02:15:09
v (0025)IO-2 NOT PROGRAMMED MODULE OFF 13-08-2099 02:15:09
(0026)IO-1 MODULE TYPE MISMATCH MAJOR 13-08-2099 02:15:09
(0026)CL-B MODULE TYPE MISMATCH MAJOR 13-08-2099 02:15:09
>

-----------------------------------------------------------------------------
Figure 6-11. Typical History Alarms Screen

3. To view the alarms, scroll as required. You can see all the navigation options
for this screen by selecting the ? (help) option.
Monitoring the Timing Source Status

Use the following procedure to display information on the current Megaplex-4100
timing source.
To navigate to the required screen, use Monitoring>System>Timing.
³ To display the timing:

1. Select Timing on the Monitoring>System menu, and then press <Enter>.
2. You will see the Timing screen. The information displayed on the screen
depends on the currently used timing source. A typical Timing monitoring
For a description of the information displayed on this screen, refer to the
Configuring System Clock Sources section in Chapter 4.
MP-4100
Monitoring>System>Timing
Timing .... (S Subsystem)
>

-----------------------------------------------------------------------------
Figure 6-12. Typical Timing Monitoring Screen
Monitoring the CL Module Status

Use the following procedure to display information on the CL modules installed in
the Megaplex-4100, and the system status information.
To navigate to the required screen, use Monitoring>System>CL Status.
³ To display the CL module status:

1. Select CL Status on the Monitoring>System menu, and then press <Enter>.
2. You will see the CL Status screen. A typical CL Status screen is shown in
Figure 6-13.

MP-4100
Monitoring>System>CL Status
CL-A CL-B
System Control Activity ON LINE NOT EXISTS
Test Status OFF OFF
Alarm Severity OFF OFF
Configuration File Usage (%) 10 0
Active DB 1 --
DB Checksum 1467 0
Last DB Update 01/12/05 00:02:16 00/00/00 00:00:00
CL Temperature (C) 32 0
>

-----------------------------------------------------------------------------
Figure 6-13. Typical CL Status Screen

3. The screen displays the following information:
System Control Displays the state of each CL module used by the

Activity system:
• ON LINE – indicates the active (master) module.
• OFF LINE – indicates the standby (slave) module.
• NOT EXISTS – the module is not installed.
Test Status Indicates whether tests are present in the system.
Alarm Severity Indicates the type of the most severe alarm that exists
in the system: CRITICAL, MAJOR, MINOR, or EVENT. OFF
means that no alarm has been reported.
Configuration File Displays the percentage of the total capacity of the

Usage corresponding CL module flash memory currently
assigned to configuration files.
Active DB Displays the database number currently in use.
DB Checksum Displays the database checksum, used to detect

corruption.
Last DB Update Indicates the date and time of the last database update.
CL Temperature The internal temperature of the CL module, in degrees

Celsius, as indicated by an internal temperature sensor.
Monitoring the Megaplex-4100 Remote Agents

Use the following procedure to display information on the remote management
agents known to the management agent of the Megaplex-4100.
To navigate to the required screen, use Monitoring>System>Remote Agents.

³ To display the remote agents:

1. Select Remote Agents on the Monitoring>System menu, and then press
<Enter> to display the Remote Agents screen. A typical screen is shown in
Figure 6-14.
MP-4100
Monitoring>System>Remote Agents
IP Address MUX Name Physical Distance Logical Distance Interface
>

-----------------------------------------------------------------------------
Figure 6-14. Typical Remote Agents Screen

2. The screen shows the following information:
IP Address The IP address of the corresponding remote agent.
Mux Name The logical name (maximum 8 alphanumeric characters)

assigned to the corresponding agent.
Physical Metric that indicates the number of hops (through the

Distance management network) to the corresponding remote agent.
Logical Metric that indicates the logical distance (through the

Distance management network) to the remote agent; used, among
other factors, in the selection of the optimal route to be used
for the management traffic. The distance calculation also takes
into account the quality of the line.
Interface Slot and port through which the communication with the
corresponding remote agent has been established.
Monitoring the APS Status

Use the following procedure to display information on the APS function on this
Megaplex-4100.
To navigate to the required screen, use Monitoring>System>APS.
³ To display APS status:

1. Select APS on the Monitoring>System screen, and then press <Enter>. A
typical screen is shown in Figure 6-15.

MP-4100
Monitoring>System>APS
APS Group Id > (A1-A2)

APS Mode > (1+1 Uni-Directional)
Current Working Slot > (CL-A)
Current Working Port > (Link 1)
>

-----------------------------------------------------------------------------
Automatic Refresh Is Activated !
Figure 6-15. Typical APS Monitoring Screen

2. The screen provides information on the configured APS group, the state of
the APS function, and the configured working module slot and port.
Refer to the Configuration – APS section in Chapter 4 for a description of the
displayed parameters.
Selecting Virtual Ports for Monitoring

Use the following procedure to select the type of virtual ports for which
monitoring information will be displayed.
To navigate to the required screen, use Monitoring>Virtual Ports.
A typical Logical Layer submenu is shown in Figure 6-16. This screen includes two
options:
I/O For displaying performance monitoring for the virtual ports of the
modules installed in I/O slots. The parameters available for these
modules depend on the module type.
For additional information, refer to the Monitoring Virtual Ports on I/O
Modules section.
Note
Some I/O modules do not have virtual ports, or no
monitoring activities are available for their ports.
CL For displaying performance monitoring and status parameters for the

virtual ports located on the CL.1/155 or CL.1/155GbE modules. Refer
to Monitoring Virtual Ports on CL Modules section on page 6-19.

MP-4100
Monitoring>Logical Layer
1. I/O>
2. CL >
>

-----------------------------------------------------------------------------
Figure 6-16. Typical Logical Layer Type Selection Submenu
³ To select the type of virtual ports to be monitored:

Monitoring Virtual Ports on I/O Modules
Selecting a Virtual Port or Bundle for Monitoring

Use the following procedure to select the I/O virtual port for which you want to
display the performance monitoring data.
The selection is made in two steps:
1. Select a specific I/O module
2. Select a specific virtual port or bundle terminated on the selected I/O module.
To navigate to the required screen, use Monitoring>Logical Layer>I/O
³ To select a virtual port on an I/O module:

1. On the screen of Figure 6-16, select I/O and then press <Enter>.
2. You will see the I/O module selection screen. A typical screen is shown in
Figure 6-17. The screen includes only I/O modules installed in the chassis that
have virtual ports.

MP-4100
Monitoring>Logical Layer>I/O
1. I/O 1 (HS-U12)>
2. I/O 2 (M8SL)>
3. I/O 3 (M8SL)>
>

-----------------------------------------------------------------------------
Figure 6-17. Typical I/O Slot Selection Screen for Modules with Virtual Ports
4. You will see the virtual port selection screen for the selected module. The
ports appearing on the screen depend on the module type. For I/O modules
with Ethernet ports, you may also see a Bundles option: this option appears
when bundles are configured on the module ports. The screen includes only
active ports and/or bundles (Admin Status=UP).
A typical screen for an M8SL module with bundles terminated on its internal
E1 ports is shown in Figure 6-18.
MP-4100
Monitoring>Logical Layer >I/O>I/O 3 (M8SL/E1)
1. E1 1 >
2. E1 5 >
3. E1 6 >
4. Bundles >
>

-----------------------------------------------------------------------------
Figure 6-18. Typical I/O – Virtual Port Selection Screen
Displaying I/O Virtual Port Monitoring Data

Use the following procedure to select the desired performance statistics view,
and clear statistics for the corresponding port.
The supported performance views include:

• Current 15-minute interval

• A previous 15-minute interval within the last 24 hours, for which valid
performance data exists
• Current 24-hour interval
• For SHDSL ports: a previous 24-hour interval within the last 7 days, for which
valid performance data exists.
For E1 ports of M8SL modules that use CAS (that is, G.732S or G.732S-CRC4
framing), you can also display the signaling information associated with each
timeslot.
To navigate to the required screen, use Monitoring>Logical Layer>I/O.
Displaying Performance Monitoring Statistics for I/O Module Virtual

Ports
³ To select the I/O module performance monitoring interval:

1. On the Slot screen, select the desired port, and then press <Enter>.
2. You will see the port monitoring interval selection screen. A typical selection
screen, which shows all the supported selections, appears in Figure 6-19.
MP-4100
Monitoring>Logical Layer>I/O>I/O 3 (M8SL)>E1 1
1. Current (15 min) >

2. Select Interval(15 min) >
3. Current (24 hours) >
4. Select Interval(24 hours)>
5. Clear Statistics
>
*

-----------------------------------------------------------------------------
Figure 6-19. Typical Virtual Port I/O Performance Monitoring Interval Selection Screen
3. The information displayed after selecting a specific performance view
depends on the module type. Refer to the module Installation and Operation
Manual for detailed information.
4. To clear (reset to 0) the performance statistics counters for the selected
port, select Clear Statistics: after pressing <Enter>, you will see a
confirmation message. Press <ESC> to continue.
Note Clearing the statistics counters does not clear the data collected for other ports.

Displaying Signaling Information for I/O Module E1 Virtual Ports
³ To monitor the signaling information for an E1 virtual port (M8SL modules only):
1. On the port selection screen of an M8SL module (Figure 6-18), select the
desired E1 port, and then press <Enter>.
2. On the E1 port task selection screen of the selected E1 port, select Signaling
3. You will see the Signaling monitor screen.
The screen includes several pages, where each page presents the signaling
information for 8 timeslots. A typical first page is shown in Figure 6-20: scroll
down to see the other pages (to see the navigation options, select? (help)).
The screen presents information only for connected voice timeslots: for other
timeslots, you will see only ––––.
MP-4100
Monitoring>Logical Layer>I/O>I/O-5 (M8SL)>E1 1>Signaling
Ts# Rx From Link Tx To CL Rx From CL Tx To Link Type

TS 01 ---- ---- ---- ---- -
TS 02 ---- ---- ---- ---- -
| TS 03 ---- ---- ---- ---- -
v TS 04 ---- ---- ---- ---- DATA
TS 05 0000 0101 0000 0000 VOICE
TS 06 0000 0101 0000 0000 VOICE
TS 07 ---- ---- ---- ---- -
TS 08 ---- ---- ---- ---- -
>

-----------------------------------------------------------------------------
Figure 6-20. Typical Signaling Monitor Screen for E1 Virtual Port
Table 6-1. Signaling Monitoring Parameters
Ts# The timeslot number within the E1 frame
Rx from Link The ABCD signaling bits received from the E1 link
Tx to CL The ABCD signaling bits transmitted to the CL module, after processing by the E1
port in accordance with the signaling profile configured for the corresponding port
Rx from CL The ABCD signaling bits received from the CL module, intended for transmission
through the E1 port (after processing in accordance with the signaling profile
configured for the corresponding port)

Tx to Link The ABCD signaling bits transmitted through the E1 port (after processing in
accordance with the signaling profile configured for the corresponding port)
Type The configured timeslot type:

• DATA – Data timeslot (no signaling is associated with this type of
timeslot)
• VOICE – Voice timeslot (timeslot with channel-associated signaling)
• MNG – Timeslot dedicated to inband management (no signaling is
associated with this type of timeslot)
• UNI BRD D – Unidirectional broadcast timeslot carrying data (no signaling
is associated with this type of timeslot)
• UNI BRD V – Unidirectional broadcast timeslot carrying voice (timeslot with
channel-associated signaling)
• RESERVED – Reserved for future assignment (no signaling is associated
with this type of timeslot).
4. The displayed signaling status is correct at the time the request had been
received by the Megaplex-4100: to refresh the display, press <ESC> to return
to the E1 port task selection screen and then to send again the request.
Displaying Performance Monitoring Statistics for I/O Module

Bundles
1. On the port selection screen (Figure 6-18), select Bundles.
2. You will see the Bundles selection screen, which lists the bundles terminated
in the selected I/O module.
3. Select the desired bundle, and then press <Enter>. A typical bundle
performance monitoring screen is shown in Figure 6-21.
The information displayed on the screen, which is accumulated continuously,
is automatically refreshed every few seconds. You can type F or B to scroll
between the other bundles on the selected I/O module.
You can clear the displayed statistics (that is, reset the displayed
performance monitoring counters) by typing C. The counters are also reset
when the Megaplex-4100 is powered up.
The performance monitoring counters displayed on the screen are explained
in Table 6-2. In addition to these counters, you can also read the time (as
retrieved from the Megaplex-4100 internal real-time clock) at which the
counters have been last reset.

MP-4100
Monitoring>Logical Layer>I/O>I/O-2 (M8E1)>Bundles>Bundle 1
E1 ... (1)
=============
Rx statistics Tx statistics
============= =============
Total Frames ... (0) Total Frames ... (0)
Total Octets ... (0) Total Octets ... (0)
Total Errors ... (0) Total Errors ... (0)
Congestion Dropped... (0)
>
C-Clear; %-Db Update; #-Db Undo; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
Figure 6-21. Typical Bundle Performance Monitoring Screen
Table 6-2. Bundle Performance Monitoring Statistics
Rx Statistics – Total Total number of frames received through the bundle

Frames
Rx Statistics – Total Total number of data octets carried by all the frames received through the bundle
Octets
Rx Statistics – Total Total number of frames with error received through the bundle
Errors
Tx Statistics – Total Total number of frames transmitted through the bundle

Frames
Tx Statistics – Total Total number of data octets carried by all the frames transmitted through the bundle
Octets
Tx Statistics – Total Total number of frames with error transmitted through the bundle
Errors
Tx Statistics – Total number of valid frames that were intended for transmission through the
Congestion Dropped bundle that have been discarded because congestion at the output

Monitoring Virtual Ports on CL Modules
Selecting a CL Virtual Port for Monitoring

Virtual ports are located only on CL.1/155 and CL.1/155GBE modules.
³ To select the CL.1/155 or CL.1/155GBE virtual ports for performance monitoring:

1. Select a specific CL module. This selection is necessary only when the
Megaplex-4100 is equipped with two CL.1/155 or CL.1/155GbE modules.
2. Select a type of port on the selected module.
3. Select a specific virtual port on the selected module. The available selections
depend on the link standard, SDH or SONET, and on the use of virtual
concatenation.
To navigate to the required screen, use Monitoring>Logical Layer>CL.
A typical CL selection screen is shown in Figure 6-22.
MP-4100
Monitoring>Logical Layer>CL
1. CL-A >
2. CL-B >
>

-----------------------------------------------------------------------------
Figure 6-22. Typical Virtual Port CL Module Selection Screen
³ To select a CL module virtual port:

1. Select the desired CL module on the CL module selection screen, and then
press <Enter>.
2. You will see the port type selection screen for the corresponding CL module.
A typical screen for CL-A is shown in Figure 6-23. VCAT appears only when
virtually concatenated groups have been configured and mapped on the
corresponding CL module.

MP-4100
Monitoring>Logical Layer>CL>CL-A
1. SDH/SONET >
2. PDH >
3. VCAT >
>

-----------------------------------------------------------------------------
Figure 6-23. Typical CL Virtual Port Type Selection Screen

3. After selecting a port type, select a specific virtual port on the corresponding
screen:
A typical screen for SDH/SONET virtual ports is shown in Figure 6-24.
A typical screen for PDH virtual ports is shown in Figure 6-25. The screen
includes several pages: use the N and P keys to scroll.
A typical screen for virtually concatenated groups is shown in Figure 6-26.
The screen displays only the configured virtually concatenated groups
(maximum 8).
MP-4100
Monitoring>Logical Layer>CL>CL-A >SDH/SONET
1. Link 1 >
2. Link 2 >
>

-----------------------------------------------------------------------------
Figure 6-24. Typical SDH/SONET Virtual Port Selection Screen

MP-4100
Monitoring>Logical Layer>CL>CL-A >PDH
1. PDH 1 >
2. PDH 2 >
3. PDH 3 >
4. PDH 5 >
5. PDH 7 >
6. PDH 9 >
... (N)
>

-----------------------------------------------------------------------------
Figure 6-25. Typical PDH Virtual Port Selection Screen

MP-4100
Monitoring>Logical Layer>CL>CL-A>VCAT
1. VCG 1>
2. VCG 2>
3. VCG 3>
4. VCG 6>
5. VCG 7>
6. VCG 8>
>

-----------------------------------------------------------------------------
Figure 6-26. Typical VCG Virtual Port Selection Screen
Monitoring SDH/SONET Virtual Ports

Megaplex-4100 supports the collection of monitoring data for the following
SDH/SONET virtual ports:
• High-order virtual ports: VC-4 for SDH links, and STS-1 for SONET links
• Low-order virtual ports: VC-3 and VC-12 for SDH links and VT1.5 for SONET
links.
Typical screens are shown in Figure 6-27. When VT1.5 virtual ports are used, the
VC-12 option is replaced by VT1.5/VC-12.

MP-4100
Monitoring>Logical Layer>CL>CL-A >SDH/SONET>Link 1
1. VC-4>
2. VC-3>
3. VC-12>
>

-----------------------------------------------------------------------------
A. SDH Links
MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1
1. VT1.5 >
2. STS1-1 >
3. STS1-2 >
4. STS1-3 >
>

-----------------------------------------------------------------------------
B. SONET Links
Figure 6-27. Typical Logical Layer Link Statistics Selection Screens
Monitoring – VC-4 and STS-1 Virtual Ports

The VC-4 and STS-1 virtual port monitoring tasks include:
• Display port status
• Display port performance monitoring statistics for the VC-4 or STS-1 level.
The performance data is collected over 15-minute intervals, and up to 97 of
the most current intervals are stored for retrieval. The performance
monitoring information is lost when the Megaplex-4100 is powered down.
A typical VC-4 port task selection screen is shown in Figure 6-28. The STS-1
screen is similar, except that it also identifies the specific STS-1 (1, 2, or 3). The
type of port is identified in the screen header.

MP-4100
VC4
1. Port Status >

2. Port Statistics >
>
The statistic is for connected ports

-----------------------------------------------------------------------------
Figure 6-28. Typical VC-4 or STS-1 Port Task Selection Screen
³ To display the status of the VC-4 or STS-1 virtual port:

1. Select Port Status on the VC-4 or STS-1 Port task selection screen and then
press <Enter>.
2. You will see the Port Status screen. A typical Port Status screen is shown in
Figure 6-29.
MP-4100
Port Status B249
J1 Received... ()
C2 Received[0 - 255]... (0)
>

-----------------------------------------------------------------------------
Figure 6-29. Typical VC-4 or STS-1 Port Status Virtual Port Screen
The parameters displayed on the Port Status screen are explained in Table 6-3.
Table 6-3. VC-4 or STS-1 Port Status Virtual Port Parameters
J1 Received Displays the received J1 string

C2 Received Displays the received C2 byte (signal label)
³ To display the VC-4 or STS-1 virtual port statistics:

1. Select Port Statistics on the VC-4 or STS-1 Port task selection screen and
then press <Enter>.
2. You will see the VC-4 or STS-1 statistics interval selection screen. The STS-1
screen is similar, except that it also identifies the specific STS-1 (1, 2, or 3). A
typical VC-4 interval selection screen is shown in Figure 6-30.

MP-4100
Port Statistics
1. Current Interval>
2. Select Interval >
3. Total >
>

-----------------------------------------------------------------------------
Figure 6-30. Typical VC-4 or STS-1 Interval Selection Screen
³ To display VC-4 or STS-1 performance monitoring data for the current interval:
1. Select Current Interval and then press <Enter>.
2. You will see the Current Interval performance monitoring screen for the VC-4.
A typical screen is shown in Figure 6-31. The STS-1 screen is similar, except
that it also identifies the specific STS-1 (1, 2, or 3).
MP-4100
Current Interval
Valid Intervals [0 - 96]... (48)

Elapsed time ... (00:00:00)
ES ... (0)
SES ... (0)
UAS (SEFS) ... (0)
CV ... (0)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-31. Typical Current Interval VC-4 or STS-1 Performance Monitoring Screen
The information displayed on the performance monitoring screen is explained in

Table 6-4.

Table 6-4. Virtual Port Performance Monitoring Data
Valid Intervals The number of intervals (up 96 intervals) for which performance monitoring information
can be displayed.
Elapsed Time The elapsed time (minutes and seconds) since the beginning of the current interval, in
seconds. The range is 1 to 15 minutes.
ES Displays the number of errored seconds (ES) in the current interval.

An errored second is any second containing one or more of the following types of errors:
• 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 when no transitions are detected in the incoming
line signal (before descrambling) during an interval of 2.3 to 100 microseconds.
The LOS defect is terminated after a 125-microsecond interval (one frame) during
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.
SES Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second during which multiple error events of the types taken into
consideration for an ES have occurred.
UAS (SEFS) 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.
CV Displays the number of coding violations (CV) in the current interval.
Interval Number The number of the 15-minute interval to be displayed, in the range of 1 to 96. This field
appears only for the Select Interval screen.
The default value is “1”, which designates the current interval. However, you can also
select another interval, by typing its number (0 to 96) and then pressing <Enter>: you can
then enter the desired interval number, up to the number displayed in the Valid Intervals
field.
The information displayed on the screen for the current interval is automatically
refreshed every five seconds.

You can clear the displayed parameters (that is, reset the displayed performance
monitoring counters) by typing C. Note however that clearing the data does not
clear the VC-4 or STS-1 data collected for other intervals or for other VCs, nor the
number of valid intervals and the start time.
³ To display VC-4 or STS-1 performance monitoring data on a selected interval:

1. Select Select Interval on the VC-4 interval selection screen (Figure 6-30) and
then press <Enter>.
2. You will see the Select Interval performance monitoring screen for the VC-4. A
typical screen is shown in Figure 6-32. The STS-1 screen is similar, except
MP-4100
Select Interval

ES ... (0)
SES ... (0)
UAS (SEFS) ... (0)
CV ... (0)
1. Interval Number [0 - 96]... (0)
>

-----------------------------------------------------------------------------
Figure 6-32. Typical Select Interval VC-4 or STS-1 Performance Monitoring Screen
3. Select the desired interval, by typing 1 and pressing <Enter>: you can then
enter the desired interval number, up to the number displayed in the Valid
Intervals field.
4. After pressing <Enter>, the data displayed on the screen is updated in
accordance with your selection.
For a description of the displayed parameters, refer to Table 6-4.
You can clear the displayed parameters (that is, reset the displayed performance
monitoring counters) for the current interval by typing C. Note however that
clearing the data does not clear the data collected for other intervals, nor the
total data.
³ To display the totaled VC-4 or STS-1 performance monitoring data:

1. Select Total on the VC-4 or STS-1 interval selection screen (Figure 6-30) and
then press <Enter>.
2. You will see the Total performance monitoring screen for the VC-4 or STS-1.
A typical screen is shown in Figure 6-33.
For a description of the displayed parameters, refer to Table 6-4.

MP-4100
Total

ES ... (0)
SES ... (0)
UAS (SEFS) ... (0)
CV ... (0)
>

-----------------------------------------------------------------------------
Figure 6-33. Typical Total VC-4 or STS-1 Performance Monitoring Screen
Monitoring – VC-3 Virtual Ports

The VC-3 virtual port monitoring tasks include:
• Display the port status of a selected VC-3
• Display of port performance monitoring statistics for a selected VC-3. You can
display performance monitoring statistics only on connected (mapped) VC-3
ports.. The performance data is collected over 15-minute intervals, and up to
97 of the most current intervals are stored for retrieval. The performance
monitoring information is lost when the Megaplex-4100 is powered down.
A typical VC-3 task selection screen is shown in Figure 6-34.
MP-4100
VC-3
1. Port Status >

2. Port Statistics >
>

-----------------------------------------------------------------------------
Figure 6-34. Typical VC-3 Virtual Port Task Selection Screen
³ To display the status of a VC-3 virtual port:

1. Select Port Status on the VC-3 Port task selection screen and then press
<Enter>.

2. You will see the Port Status screen. A typical Port Status screen is shown in
Figure 6-35.
MP-4100
Port Status
J1 Received ... (48)

C2 Received ... (0)
1. VC Port[1 – 3] ... (1)
>

-----------------------------------------------------------------------------
Figure 6-35. Typical VC-3 Port Status Virtual Port Screen

The information displayed on the Port Status screen includes the following items:
• VC Port: used to select the VC-3 port for which the port statistics data is
displayed. The allowed range is 1 to 3, however only connected (mapped)
ports may be selected. If you select an unconnected port, the Valid Intervals
field displays Error.
• The other items are explained in Table 6-3.
³ To display the VC-3 virtual port statistics:

1. Select Port Statistics on the VC-3 Port task selection screen and then press
<Enter>.
2. You will see the VC-3 statistics interval selection screen. Figure 6-36 shows a
typical VC-3 interval selection screen.
MP-4100
Port Statistics
3. Total >
>

-----------------------------------------------------------------------------
Figure 6-36. Typical VC-3 Interval Selection Screen
³ To display VC-3 performance monitoring data for the current interval:

1. Select Current Interval on the VC-3 interval selection screen and then press
<Enter>.

2. You will see the Current Interval port statistics screen for VC-3s. A typical
The information displayed for the current interval port statistics screen includes
the following items:
• Item 1 – VC Port: used to select the VC-3 port for which the port statistics
data is displayed. The allowed range is 1 to 3, however only connected ports
may be selected. If you select an unconnected port, the Valid Intervals field
displays Error.
³ To display VC-3 performance monitoring data on a selected interval:

Select Select Interval on the VC-3 interval selection screen and then press
<Enter>.
Except for first selecting a specific VC-3 port, use the procedure described on
page 6-29 for VC-4.
³ To display totaled VC-3 performance monitoring data:

Select Total on the VC-3 interval selection screen and then press <Enter>.
Except for first selecting a specific VC-3 port, use the procedure described on
page 6-30 for VC-4.
MP-4100
Current Interval
Valid Interval ... (52)

ES ... (0)
SES ... (0)
UAS (SEFS) ... (0)
CV ... (0)
1. VC Port[1 - 3] ... (48)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-37. Typical Current Interval Port Statistics Screen for VC-3s
Monitoring – VC-12 or VT1.5 Virtual Ports

The low-order virtual port monitoring tasks include:
• Display the port status of a selected VC-12 or VT1.5
• Display of port performance monitoring statistics for a selected VC-12 or
VT1.5. You can display performance monitoring statistics only on connected
(mapped) VC-12 or VT1.5 ports. The performance data is collected over

15-minute intervals, and up to 97 of the most current intervals are stored for
retrieval. The performance monitoring information is lost when the
Megaplex-4100 is powered down.
A typical VC-12 or VT1.5 task selection screen is shown in Figure 6-38.
MP-4100
VC-12
1. Port Status >

2. Port Statistics>
>

-----------------------------------------------------------------------------
Figure 6-38. Typical VC-12 or VT1.5 Virtual Port Task Selection Screen
³ To display the status of a VC-12 or VT1.5 virtual port:

1. Select Port Status on the VC-12 or VT1.5 port task selection screen and then
press <Enter>.
2. You will see the Port Status screen. Typical Port Status screens are shown in
Figure 6-39 and Figure 6-40.
MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1>VC-12>Port Status
J2 Received ... (10)

V5 (Bits 5-7) Received... (48)
1. VC Port[1 - 63] ... (1)
>

-----------------------------------------------------------------------------
Figure 6-39. Typical VC-12 Port Status Virtual Port Screen (Megaplex-4100 with E1 Ports)

MP-4100
Monitoring>Logical Layer>CL>CL-A>SDH/SONET>Link 1>VT1.5>Port Status
J2 Received ... (Error)

V5 (Bits 5-7) Received... (Error)
1. VT Port[1 - 84] ... (1)
>

-----------------------------------------------------------------------------
Figure 6-40. Typical VT1.5 Port Status Virtual Port Screen (Megaplex-4100 with T1 Ports)
The information displayed on the Port Status screen includes the following items:
• VC Port or VT port: used to select the VC-12 or VT1.5 port for which the port
statistics data is displayed.
The allowed range is 1 to 63 when the Megaplex-4100 uses SDH links, and 1
to 84 when Megaplex-4100 uses SONET links. Note however that only
connected ports may be selected. If you select an unconnected port, the
Valid Intervals field displays Error.
• J2 Received: explained in Table 6-5
• V5 (Bits 5-7) Received: explained in Table 6-5.
Table 6-5. VC-12 Port Status Virtual Port Status Parameters
J2 Received Displays the received J2 string
V5 (Bits 5-7) Received Displays the bits 5 to 7 of the received V5 byte, which carry
the signal label
³ To display the VC-12 or VT1.5 virtual port statistics:

1. Type Port Statistics on the VC-12 or VT1.5 Port task selection screen and
then press <Enter>.
2. You will see the VC-12 or VT1.5 statistics interval selection screen. A typical
interval selection screen is shown in Figure 6-41.

MP-4100
Port Statistics
3. Total >
>

-----------------------------------------------------------------------------
Figure 6-41. Typical Interval Selection Screen
³ To display VC-12 or VT1.5 performance monitoring data for the current interval:
2. You will see the Current Interval port statistics screen for VC-12s or VT1.5s.
A typical screen is shown in Figure 6-42. The STS-1 screen is similar, except
MP-4100
Current Interval
Valid Intervals... (48)

ES ... (0)
SES ... (0)
UAS (SEFS) ... (0)
CV ... (0)
1. VC Port[1 - 63]... (0)
2. Interval Number... (0)
>

-----------------------------------------------------------------------------
Figure 6-42. Typical Current Interval Port Statistics Screen for VC-12s
The information displayed for the current interval port statistics screen includes
the following items:
• VC Port or VT Port: used to select the VC-12 port for which the port statistics
data is displayed. The allowed range is 1 to 63 when the Megaplex-4100 is
equipped with SDH links, and 1 to 84 for a Megaplex-4100 with SONET links.
Note however that only connected ports may be selected. If you select an
unconnected port, the Valid Intervals field displays Error.

³ To display VC-12 or VT1.5 performance monitoring data on a selected interval:

1. Select Select Interval and then press <Enter>.
2. Except for first selecting a specific VC-12 or VT1.5 port, use the procedure
described on page 6-29 for VC-4 or STS-1.
³ To display totaled VC-12 or VT1.5 performance monitoring data:

1. Select Total and then press <Enter>.
2. Except for first selecting a specific VC-12 or VT1.5 port, use the procedure
described on page 6-30 for VC-4 or STS-1.
Displaying WAN Intervals Parameters

The performance monitoring statistics for the WAN side of the selected virtually
concatenated group depend on the encapsulation mode selected for the group:
LAPS or GFP.
Note When using GFP multiplexing, only the statistics of the primary group can be
displayed. This is sufficient for performance monitoring, because these statistics
represent the WAN side transmission performance for all the groups handled by
the corresponding GFP multiplexer.
The statistics are collected over 15-minute intervals, and up to 97 of the most
current intervals are stored for retrieval. The performance monitoring information
is lost when the Megaplex-4100 is powered down.
A typical WAN Intervals selection screen is shown in Figure 6-43.
MP-4100
Monitoring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals
3. Total >
>

ESC-prev.menu; !-main menu; &-exit; @-debug 1M/1C
-----------------------------------------------------------------------------
Figure 6-43. Typical WAN Intervals Selection Screen
³ To display WAN side performance monitoring data for the current interval:
1. Type 1 and then press <Enter>.
2. You will see the first page of the Current Interval performance monitoring
screen for the WAN side. The Current Interval screen includes a large number
of items and therefore it consists of two pages:
To continue from the first page to the second page, type n (next)
To return from the second page to the first page, type p (previous).

³ To display WAN side performance monitoring data on a selected interval:

Type 2 and then press <Enter>.
³ To display totaled WAN side performance monitoring data:

Type 3 and then press <Enter>.
³ To clear the accumulated statistics (reset all the counters, except items 2, 3, 4):
Type C and then press <Enter>.
VCG WAN Side Statistics – LAPS Encapsulation

The two pages of a typical WAN side statistics screen for a virtually concatenated
group using LAPS encapsulation are shown in Figure 6-44 and Figure 6-45. The
WAN side statistics parameters for groups using LAPS encapsulation are described
in Table 6-6.
MP-4100
oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval

2. Valid Intervals [0 - 96]... (1)
3. Elapsed time ... (00:08:40)
4. Number of Total Rx Frames ... (0)
5. Number of Total Tx Frames ... (0)
6. Rx Payload Max length violation ... (0)
7. Rx Payload Min length violation ... (0)
8. FCS error ... (0)
9. Receive Abort Frames ... (0)
10. Byte De-stuffing violations ... (0)
... (N)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-44. Typical WAN Side Statistics Screen – LAPS Encapsulation (First Page)
MP-4100
oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
... (P)
11. Receive address field mismatch counter... (0)
12. Receive control field mismatch counter... (0)
13. Receive SAPI field mismatch counter ... (0)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-45. Typical WAN Side Statistics Screen – LAPS Encapsulation (Second Page)

Table 6-6. WAN Side Statistics – LAPS Encapsulation
Interval Number The number of the 15-minute interval to be displayed, in the range of 1 to 96.
To select a different interval, type 1 and then press <Enter>: you can then enter the
desired interval number, up to the number displayed in the Valid Intervals field
Valid Intervals The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed
Elapsed Time The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds
Number of Total Rx Total number of frames received from the WAN

Frames
Number of Total Tx Total number of frames transmitted to the WAN

Frames
Rx Payload Max Total number of frames received with payload fields exceeding the maximum allowed
Length Violation number of bytes
Rx Payload Min Total number of frames received with payload fields shorter than the minimum
Length Violation allowed number of bytes
FCS Error Total number of frames received with frame checksum errors
Receive Abort Total number of frames whose reception has been aborted
Frames
Byte De-stuffing Total number of byte destuffing violations detected during the processing of received
Violations frames
Receive Address Total number of valid received LAPS frames with mismatching address field
Field Mismatch
Counter
Receive Control Total number of valid received LAPS frames with mismatching control field
Field Mismatch
Counter
Receive SAPI Field Total number of valid received LAPS frames with mismatching SAPI field
Mismatch Counter
WAN Side Statistics – GFP Encapsulation

The two pages of a typical WAN side statistics screen for a virtually concatenated
group using GFP encapsulation are shown in Figure 6-46 and Figure 6-47.
The WAN side statistics parameters for groups using GFP encapsulation are

MP-4100
...oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval

2. Valid Intervals [0 - 96]... (7)
3. Elapsed time ... (00:08:25)
4. Number of Total Rx Frames ... (0)
5. Number of Total Tx Frames ... (0)
6. Rx Payload Max length violation ... (0)
7. FCS error ... (0)
8. Receive Idle frame error ... (0)
9. Receive cHEC single bit error ... (0)
10. Receive PTI mismatch ... (0)
... (N)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-46. Typical WAN Side Statistics Screen – GFP Encapsulation (First Page)
MP-4100
...oring>Logical Layer>CL>CL-A>VCAT>VCG 1>Wan Intervals>Current Interval
... (P)
11. Receive EXI mismatch ... (0)
12. Receive UPI mismatch ... (0)
13. Receive tHEC single bit error ... (0)
14. Receive tHEC multi bit error ... (0)
15. Receive CID mismatch ... (0)
16. Receive eHEC single bit error ... (0)
17. Receive eHEC multi bit error ... (0)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-47. Typical WAN Side Statistics Screen – GFP Encapsulation (Second Page)

Table 6-7. WAN Side Statistics – GFP Encapsulation
To select a different interval, type 1 and then press <Enter>: you can then
Intervals field.
Valid Intervals The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed.
Elapsed Time The elapsed time (in seconds) since the beginning of the current interval, in
seconds. The range is 1 to 900 seconds.
Start Time The time at which the current interval was initiated, in accordance with the
Megaplex-4100 internal real-time clock.
Since the Megaplex-4100 time may not be coordinated with the network
management station time, or they may be located in different time zones, you
should compare the Megaplex-4100 internal time (displayed by means of the
Configuration – System – Date & Time Update) with the station time.
Number of Total Rx Frames Total number of GFP frames received from the WAN.
Number of Total Tx Frames Total number of GFP frames transmitted to the WAN.
Rx Payload Max Length Total number of GFP frames received with payload fields exceeding the
Violation maximum allowed number of bytes.
FCS Error Total number of GFP frames received with frame checksum errors.
Receive Idle Frame Error Total number of GFP IDLE frames received with errors error.
Receive cHEC Single Bit Total number of received GFP frames that are detected to have only single-bit
Error errors in the GFP Core header (cHEC field).
Receive PTI Mismatch Total number of received GFP frames with a mismatch in the PTI field (i.e., PTI
value not corresponding to the Client Data or Management frame).
Receive EXI Mismatch Total number of received GFP frames with a mismatch in the EXI field (i.e.,
value of EXI is not equal to NULL or LINEAR modes).
Receive UPI Mismatch Total number of received GFP frames with a mismatch in the UPI field (i.e., EXI
value not equal to 00000001).
Receive tHEC Single Bit Total number of received GFP frames with single-bit errors only in the GFP Type
Error header (tHEC field).
Receive tHEC Multi Bit Error Total number of received GFP frames with multi-bit errors in the GFP Type
header (tHEC field).
Receive CID Mismatch Total number of received GFP frames with a mismatch or unsupported value in
the GFP CID field.
Receive eHEC Single Bit Total number of received GFP frames with only single-bit errors in the GFP
Error Extension header (eHEC field).
Receive eHEC Multi Bit Error Total number of received GFP frames that are detected to only have multi-bit
errors in the GFP Extension header (eHEC field).

Displaying LCAS Path Info Parameters for Virtual Ports

For virtually concatenated groups configured to use LCAS, you can display
information on the LCAS status for the selected virtually concatenated group.
A typical LCAS Path Info selection screen is shown in Figure 6-48.
MP-4100
Monitoring>Virtual Ports>VCAT>VCG 1>LCAS PATH info
Index VC Number Source State Sink State

0 L1 1:1:1 Add Fixed
>
ESC-prev.menu; !-main menu; &-exit; @-debug ; ?-help 1M/1C

-----------------------------------------------------------------------------
Figure 6-48. Typical LCAS Path Info Screen

The parameters displayed by means of the LCAS Path Info screen are as follows:
Index Displays the index number of the VC within the selected virtually
concatenated group. The index number is automatically assigned.
VC Number Identifies the position of the corresponding VC or VT within the

STM-1 or STS-3 frame, using the TUG-3:TUG-2:TU format
described in Table 6-8 and Table 6-9.
The VC Number also includes the identification of the link, L1 or
L2.
Source State 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 State Same as above for the sink side (remote end of the path).
For each current parameter value, you can also see the allowed range of values.
Table 6-8. Identification of VC-12 Position in STM-1 Frame
TUG-3 No. 1 TUG-3 No. 2 TUG-3 No. 3

TU Type
TU 1 TU 2 TU 3 TU 1 TU 2 TU 3 TU 1 TU 2 TU 3
TUG-2 No. 1 1 2 3 22 23 24 43 44 45
TUG-2 No. 2 4 5 6 25 26 27 46 47 48
TUG-2 No. 3 7 8 9 28 29 30 49 50 51
TUG-2 No. 4 10 11 12 31 32 33 52 53 54
TUG-2 No. 5 13 14 15 34 35 36 55 56 57
TUG-2 No. 6 16 17 18 37 38 39 58 59 60
TUG-2 No. 7 19 20 21 40 41 42 61 62 63
Table 6-9. Identification of VT1.5 Position in STS-3 Frame
STS-1 No. 1 STS-1 No. 2 STS-1 No. 3

TU Type
TU 1 TU 2 TU 3 TU 4 TU 1 TU 2 TU 3 TU 4 TU 1 TU 2 TU 3 TU 4
TUG-2 No. 1 1 2 3 4 29 30 31 32 57 58 59 60
TUG-2 No. 2 5 6 7 8 33 34 35 36 61 62 63 64
TUG-2 No. 3 9 10 11 12 37 38 39 40 65 66 67 68
TUG-2 No. 4 13 14 15 16 41 42 43 44 69 70 71 72
TUG-2 No. 5 17 18 19 20 45 46 47 48 73 74 75 76
TUG-2 No. 6 21 22 23 24 49 50 51 52 77 78 79 80
TUG-2 No. 7 25 26 27 28 53 54 55 56 81 82 83 84
Monitoring Physical Layer Parameters
Selecting the Class of Physical Ports

Select a class of physical ports for which monitoring information will be displayed.
This screen includes two options:
I/O For displaying performance monitoring and status parameters for the
physical ports of the modules installed in I/O slots. The parameters
available for these modules depend on the module type.
For additional information, refer to the Monitoring I/O Physical Layer
Parameters section.
CL For displaying performance monitoring and status parameters for the
physical ports located on the CL modules. See Monitoring CL Physical
Ports section.
To navigate to the required screen, use Monitoring>Physical Layer.

A typical Physical Layer submenu is shown in Figure 6-49.

MP-4100
Monitoring>Physical Layer
1. I/O>
2. CL>
>

-----------------------------------------------------------------------------
Figure 6-49. Typical Physical Layer Selection Submenu
³ To select a class of physical ports:

Monitoring I/O Physical Layer Parameters

The Physical Layer submenu is used to monitor the physical layer status and
display performance statistics for the desired module and/or port. The selection
of a monitoring task is made in the following steps:
• Selection of the target type
• Selection of a specific I/O module
• Selection of a specific port on the selected I/O module. For modules that
have more than one type of ports, first you must select a port type
(depending on the type of ports available on the module), and then a specific
port
• Selection of a specific monitoring task.
³ To start physical layer monitoring:

1. After opening the Monitoring>Physical Layer submenu, you will see the
Physical Layer type selection screen (a typical screen is shown in
Figure 6-50): select IO (I/O modules), and then press <Enter>.

MP-4100
Monitoring>Physical Layer
1. IO >
2. CL >
>

-----------------------------------------------------------------------------
Figure 6-50. Typical Physical Layer Class Selection Screen

2. After selecting IO (I/O modules), you will see the I/O module selection screen.
A typical screen is shown in Figure 6-51. The screen includes only the
modules installed in the chassis.
MP-4100
Monitoring>Physical Layer>I/O
1. I/O 1 (M8E1)>
2. I/O 2 (M8E1)>
3. I/O 3 (M8SL)>
>

-----------------------------------------------------------------------------
Figure 6-51. Typical I/O Module Selection Screen

4. For I/O modules that have more than one type of physical ports, you will see
the port type selection screen.
For example, for M8E1 and M8T1 modules you can select between E1,
respectively T1, and Ethernet ports, and for M8SL modules you can select
between SHDSL and Ethernet ports.
5. You will see the port selection screen for the selected module. The ports
appearing on the screen depend on the selected module type, but only
configured modules with Admin Status = UP are included.

A typical screen for TDM links is shown in Figure 6-52, and a typical screen
for Ethernet ports is shown in Figure 6-53.
Note the Active label next to Link 1 in Figure 6-52: this label indicates the
redundancy status for a port that is part of a redundancy pair (in this
example, the Standby port is on another module).
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1 B257
1. Link 1(Active) >

2. Link 3 >
3. Link 4 >
4. Link 6 >
>

-----------------------------------------------------------------------------
Figure 6-52. Typical I/O Physical Port Selection Screen (E1, T1, or SHDSL Ports)
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet
1. ETH 1 >
2. ETH 3 >
>

-----------------------------------------------------------------------------
Figure 6-53. Typical I/O Physical Port Selection Screen (Ethernet Ports)
Displaying I/O TDM Physical Layer Monitoring Data

Use the following procedure to select the desired monitoring data view (status or
performance statistics) for TDM I/O module ports, and clear statistics for the
corresponding port.
The supported performance views include:
• Current 15-minute interval (interval 0)

• A previous 15-minute interval within the last 24 hours, for which valid
performance data exists
• Current 24-hour interval
• For SHDSL ports: a previous 24-hour interval within the last 7 days, for which
valid performance data exists.
For E1 ports using CAS (that is, G.732S, G.732S-CRC4 framing) and for framed T1
ports, you can also display the signaling information associated with each voice
timeslot.
To navigate to the required screen, use Monitoring>Physical Layer>I/O>E1 or T1
or SHDSL
³ To select a TDM port monitoring task:

1. On the Slot screen, select the desired port, and then press <Enter>.
2. You will see the port monitoring task selection screen. A typical selection
screen, which shows all the supported selections, appears in Figure 6-54:
The Status item is displayed only for a port that is part of a redundancy
pair.
The Signaling item is displayed only for a framed port using CAS.
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1>Link 1(Active)
1. Status >
2. Statistics>
3. Signaling >
>

-----------------------------------------------------------------------------
Figure 6-54. Typical Monitoring Task Selection Screen for I/O TDM Physical Port
³ To display the TDM port status:

1. Select Status, and then press <Enter>. A typical screen is shown in
Figure 6-55.
2. The screen displays the current function of the selected port within the
redundancy pair:
Active The port is the active port (the port carrying the traffic).
Standby The port is in standby, and does not carry traffic.

MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Status
Redundancy State> (Active)
>

-----------------------------------------------------------------------------
Figure 6-55. Typical I/O TDM Physical Port Status Screen
³ To display the I/O TDM port performance monitoring statistics:

1. Select Statistics, and then press <Enter>.
2. You will see the port statistics interval selection screen. A typical interval
selection screen is shown in Figure 6-56. The Select Interval (24 hours) is
displayed only for SHDSL ports (on M8SL modules).
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8SL)>E1>Link 1(Active)>Statistics
1. Current (15 min) >

3. Total (24 hours) >
4. Select Interval (24 hours)>
5. Clear Statistics
>

-----------------------------------------------------------------------------
Figure 6-56. Typical I/O TDM Physical Port Statistics Interval Selection Screen (M8SL Port)
³ To display the I/O TDM physical port performance monitoring statistics for the
current interval:
1. Select Current (15 min), and then press <Enter>.
2. You will see the Current (15 min) statistics screen for the selected port. The
information displayed after selecting a specific performance view depends on

the module type: refer to the module Installation and Operation Manual for
detailed information.
A typical screen for E1 ports is shown in Figure 6-57; the same parameters
are also used for T1 ports. SHDSL ports have additional performance
parameters that cover the performance of the SHDSL subsystem. The
selected port is identified in the screen header. If the port is part of a
redundancy pair, a label next to the port identification indicates the
redundancy status of the port (Active or Standby).
MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Current (15 min)
CRC Error Per Second ... (0)

CRC Average Error/Sec... (0)
Current ES ... (0)
Current UAS ... (441)
Current SES ... (0)
Current BES ... (0)
Current LOFC ... (0)
Current CSS ... (0)
Current Timer ... (441)
Num Of Intervals ... (41)
>

-----------------------------------------------------------------------------
Figure 6-57. Typical I/O TDM Physical Port Current Interval Statistics Screen (E1 Ports)
The information displayed on the screen, which is accumulated continuously, is
automatically refreshed every few seconds. To stop refreshing, type CTRL+B.
You can clear the displayed statistics (that is, reset the displayed performance
monitoring counters) by typing C. The counters are also reset when the
Megaplex-4100 is powered up.
The performance monitoring counters displayed on the E1 and T1 Statistics
screens are explained in Table 6-10, and the parameters displayed for SHDSL
ports are explained in Table 6-11.
Table 6-10. E1 and T1 Physical Port Statistics Parameters – 15-Minute Intervals
0 is the current interval.
Num of Intervals The number of intervals (up 96 intervals) for which performance monitoring
information can be displayed.
Current Time The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.

CRC Error per Displays the total number of CRC errors detected in the current second.
Second A CRC error is any CRC error detected by the CRC-4 function. Available only for E1
links.
CRC Average Error Displays the average number of CRC errors per second detected in the current
per Second measurement interval. Available only for E1 links.
ESF Error Displays the number of ESF error events in the current 15-minute interval.
An ESF error event is any extended super-frame containing a CRC error and/or OOF
event. Available only for T1 links.
Current ES Displays the number of errored seconds (ES) in the current interval.
An errored second is any second which is not declared a UAS that contains one or
more Out-of-Frame (OOF) events and/or CRC errors.
Current UAS Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
• 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.
Current SES Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second which is not declared a UAS that contains more than 320 CRC
errors.
Current BES Displays the number of bursty errored seconds (BES) in the current interval.
An BES is any second which is not declared a UAS that contains 2 to 319 CRC errors.
Current Loss of The loss of frame (LOF) counter counts the loss of frame alignment events. The data
Frame Counter is collected for the current 15-minute interval.
(LOFC)
Current Slip Displays the number of controlled slip errored seconds (CSS) in the current 15-minute
Second Counter interval.
(CSS) A CSS is a second with one or more controlled slip events.
Table 6-11. SHDSL Physical Port Statistics Parameters – 15-Minute Intervals
Interval Number See Table 6-10
Num of Intervals See Table 6-10
Current Time See Table 6-10
Current ES Displays the number of SHDSL errored seconds (ES) in the current interval.
An SHDSL ES is a second during which one or more CRC anomalies are declared,
and/or one or more LOSW defects are declared

Current UAS Displays the number of SHDSL unavailable seconds (UAS) in the current interval.
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)
Current SES Displays the number of SHDSL severely errored seconds (SES) in the current interval.
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
Current CRC Displays the number of CRC anomalies in the current interval.
Anomalies 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.
Current LOSWS Displays the number of SHDSL LOSW seconds (LOSWS) in the current interval.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW defects are
declared
Current LOSW Displays the number of loss of SHDSL synchronization word (LOSW) events in the
current interval.
An LOSW failure is declared after 2.5 ± 0.5 seconds of contiguous LOSW defect. The
LOSW failure is cleared when the LOSW defect is absent for 20 seconds, but not less
than 2 seconds
Loop Attenuation Displays the loop attenuation, in dB, measured in the current interval
SNR Margin Displays the signal/noise margin, in dB, measured in the current interval
Actual Power Displays the transmit power backoff, in dB, used in the current interval
Backoff
³ To display I/O TDM port performance monitoring statistics for a selected interval:
1. Select Select Interval on the port statistics interval selection screen, and then
press <Enter>.
2. You will see the Select Interval performance monitoring screen. A typical
screen is shown in Figure 6-58. The selected port is identified in the screen
header. If the port is part of a redundancy pair, a label next to the port
identification indicates the redundancy status of the port (Active or Standby).
enter the desired interval number, up to the number displayed in the Num of
Intervals field (see Figure 6-57).

MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Select Interval
Current ES ... (0)

Current UAS ... (900)
Current SES ... (0)
Current BES ... (0)
Current LOFC ... (0)
Current CSS ... (0)
1. Interval [1-96] ... (1)
>

-----------------------------------------------------------------------------
Figure 6-58. Typical I/O TDM Physical Port Select Interval Statistics Screen (E1 Ports)
³ To display totaled I/O TDM port performance monitoring statistics for last
24-hour interval:
1. Select Total on the TDM port statistics interval selection screen and then
press <Enter>.
2. You will see the Total performance monitoring screen for the selected TDM
port. A typical screen is shown in Figure 6-58. The selected port is identified
in the screen header. If the port is part of a redundancy pair, a label next to
the port identification indicates the redundancy status of the port (Active or
Standby).
MP-4100
... Ports>I/O>I/O-2 (M8E1)>E1>Link 1(Active)>Statistics>Total (24 hours)
ES ... (0)
UAS ... (36900)
SES ... (0)
BES ... (0)
LOFC ... (1)
CSS ... (1)
Current 24 Hour Degraded min ... (0)
Last 24 Hour Degraded min ... (0)
>

-----------------------------------------------------------------------------
Figure 6-59. Typical I/O TDM Physical Port Total (24 Hours) Statistics Screen (E1 Ports)

Table 6-12. E1 and T1 Physical Port Statistics Parameters – 24-Hour Totals
ES Displays the total number of errored seconds (ES) in the 24-hour interval.
UAS Displays the total number of unavailable seconds (UAS) in the 24-hour interval.
SES Displays the total number of severely errored seconds (SES) in the 24-hour interval.
BES Displays the total number of bursty errored seconds (BES) in the 24-hour interval.
LOFC Displays the total number of LOF events (BES) in the 24-hour interval.
CSS Displays the total number of controlled slip errored seconds (CSS) in the 24-hour
15-minute interval.
Current Degraded Displays the total number of degraded minutes in the current 24-hour interval. A
-6
Minutes degraded minute is a minute in which the bit error rate (BER) exceeded 1×10 . This
number is updated every minute.
Last Degraded Displays the total number of degraded minutes in the last 24-hour interval. This
Minutes number is updated every 24 hours.
Table 6-13. SHDSL Physical Port Statistics Parameters – 24-Hour Totals
Current ES Displays the total number of SHDSL errored seconds (ES) in the last 24-hour interval.
Current UAS Displays the total number of SHDSL unavailable seconds (UAS) in the last 24-hour
interval.
Current SES Displays the total number of SHDSL severely errored seconds (SES) in the last 24-hour
interval.
Current CRC Displays the total number of CRC anomalies in the last 24-hour interval.
Anomalies
Current LOSWS Displays the total number of SHDSL LOSW seconds (LOSWS) in the last 24-hour
interval.
³ To display totaled I/O SHDSL port performance monitoring statistics for a

selected 24-hour interval:
1. Select Select Interval (24 Hours) on the TDM port statistics interval selection
screen and then press <Enter>.
enter the desired interval number, up to 7.
accordance with your selection. The selected port is identified in the screen
header. If the port is part of a redundancy pair, a label next to the port
identification indicates the redundancy status of the port (Active or Standby).
The performance monitoring counters are explained in Table 6-13.
³ To monitor the signaling information for an E1 or T1 physical port:

1. On the physical port selection screen (Figure 6-49), select the desired E1
port, and then press <Enter>.

2. On the port task selection screen of the selected port (Figure 6-54), select
Signaling and then press <Enter>.
3. You will see the Signaling monitor screen.
The screen includes several pages, where each page presents the signaling
information for 8 timeslots. A typical first page is shown in Figure 6-20: scroll
down to see the other pages (to see the navigation options, select? (help)).
The screen presents information only for connected voice timeslots: for other
timeslots, you will see only ––––.
MP-4100
Monitoring>Physical Layer>I/O>I/O-1 (M8E1)>Link 1>Signaling
Ts# Rx From Link Tx To CL Rx From CL Tx To Link Type

TS 01 ---- ---- ---- ---- -
TS 02 ---- ---- ---- ---- -
| TS 03 ---- ---- ---- ---- -
v TS 04 ---- ---- ---- ---- DATA
TS 05 0000 0101 0000 0000 VOICE
TS 06 0000 0101 0000 0000 VOICE
TS 07 ---- ---- ---- ---- -
TS 08 ---- ---- ---- ---- -
>

-----------------------------------------------------------------------------
Figure 6-60. Typical Signaling Monitor Screen for Physical Port

For a description of the Signaling monitoring parameters, refer to Table 6-1.
Displaying I/O Ethernet Physical Port Monitoring Data

Use the following procedure to select the desired monitoring data view (status or
performance statistics) for I/O module Ethernet ports, and clear statistics for the
corresponding port.
Statistics can be displayed only for enabled ports: if the Ethernet port is not
enabled, its monitoring display is empty.
The information is accumulated continuously while the Megaplex-4100 operates,
and is automatically refreshed every few seconds. The performance monitoring
information is lost when the Megaplex-4100 is powered down.
To navigate to the required screen, use Monitoring>Physical Layer>I/O>Ethernet.
³ To select an I/O Ethernet port monitoring task:

1. On the Slot screen (Figure 6-54), select the desired Ethernet port, and then
press <Enter>.
2. You will see the Ethernet port monitoring task selection screen. A typical
selection screen appears in Figure 6-61.

MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1
1. Status >
2. Statistics>
>

-----------------------------------------------------------------------------
Figure 6-61. Typical Monitoring Task Selection Screen for I/O Module Ethernet Physical Port
³ To display the I/O Ethernet port status:

1. Select Status, and then press <Enter>.
2. You will see the Port Status screen for the selected Ethernet port. A typical
The parameters displayed on the Ethernet port Status screen are explained in
Table 6-14.
MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Status
Connector Type > (SFP)

Operation Status> (Up)
Auto Negotiation> (Disabled)
Speed & Duplex > (100 Mbps Full Duplex)
>

-----------------------------------------------------------------------------
Figure 6-62. Typical I/O Ethernet Physical Port Status Screen
Table 6-14. I/O Physical Port Ethernet Port Status Parameters
Connector Type Displays the port connector type:

• RJ-45 – RJ-45 connector for copper interface.
• SFP – in accordance with the installed SFP.
• Missing – port equipped with SFP socket, but no SFP is installed.

Operation Status Displays the Ethernet port status:

• Up – the port is connected to a LAN and operating normally
• Down – the port does not carry traffic, e.g., it is not connected to an active
LAN
Auto Negotiation Displays the auto-negotiation status:

• Configuring – the port uses auto-negotiation, and is currently performing the
negotiation process needed to select the operating rate and mode
• Complete – the port completed the negotiation process and the operating
rate and mode has been selected
• Disabled – the port operating rate and mode is manually selected
Speed and Duplex Displays the port current rate and mode:
• 10Mbps half duplex – Half-duplex operation at 10 Mbps.
• 10Mbps full duplex – Full-duplex operation at 10 Mbps.
• 100Mbps half duplex – Half-duplex operation at 100 Mbps.
• 100Mbps full duplex – Full-duplex operation at 100 Mbps.
³ To display the I/O Ethernet port performance monitoring statistics:

1. Select Statistics in Figure 6-61, and then press <Enter>.
2. You will see the Statistics screen for the selected Ethernet port. The screen
includes a large number of items and therefore it consists of three pages:
To continue from the first page to the next page, type n (next)
To return from the second page to the previous page, type p (previous).
Typical Statistics screens are shown in Figure 6-63. Table 6-15 explains the
statistics parameters.
automatically refreshed every few seconds. You can clear the displayed statistics
(that is, reset the displayed performance monitoring counters) by typing C. The
counters are also reset when the Megaplex-4100 is powered up.

MP-4100
Monitoring>Physical Layer>I/O>I/O-2 (M8E1)>Ethernet>ETH 1>Statistics
RX Statistics TX Statistics
============= =============
Total Frames ... (0) Total Frames ... (0)
Total Octets ... (0) Total Octets ... (0)
Correct Frames ... (0) Correct Frames ... (0)
FCS Errors ... (0)
Jabber Errors ... (0)
Fragments Errors ... (0)
Pause Frames ... (0)
Undersized Frames... (0)
Oversized Frames ... (0)
... (N)
>

-----------------------------------------------------------------------------
A. First Page
MP-4100
... (P)
============= =============
Collisions ... (0)
Discard Frames ... (0) Discard Frames ... (0)
Errors ... (0)
Unicast Frames ... (0) Unicast Frames ... (0)
MultiCast Frames ... (0) MultiCast Frames ... (0)
Broadcast Frames ... (0) Broadcast Frames ... (0)
64 Octets ... (0)
65-127 Octets ... (0)
128-255 Octets ... (0)
... (N)
>

-----------------------------------------------------------------------------
B. Second Page

MP-4100
... (P)
============= =============
256-511 Octets ... (0)
512-1023 Octets ... (0)
1024-long Octets ... (0)
>

-----------------------------------------------------------------------------
C. Third Page
Figure 6-63. Typical I/O Ethernet Physical Port Statistics Screen
Table 6-15. I/O Ethernet Physical Port Performance Monitoring Statistics
Rx Total Frames Total number of frames received through the corresponding Ethernet port
Rx Total Octets Total number of data octets carried by all frames received through the
corresponding Ethernet port
Rx Correct Frames Total number of good frames received through the corresponding Ethernet
port
Rx FCS Errors Total number of frames received by the corresponding Ethernet port which
has an invalid FCS, but met the following conditions:
• Frame data length is between 64 bytes, and 1518 or 1536 bytes
(depending on mode)
• Collision event has not been detected
• Late collision event has not been detected
Rx Jabber Errors Total number of frames received by the corresponding Ethernet port during
jabber (such frames are frames with a data field length exceeding 1518 or
1536 bytes, and also having invalid CRC)
Rx Fragment Errors Number of fragmented frames received at the corresponding Ethernet port (a
fragmented frame is a frame with a data field length less than 64 bytes and
invalid CRC, for which no collision event and no late collision event have not
been detected during its reception)
Rx Pause Frames Total number of pause frames (used for flow control) received through the

Undersized Frames Total number of frames with size less than 64 bytes received through the
Oversized Frames Total number of frames with size more than the maximum allowed received
through the corresponding Ethernet port
Rx Discard Frames Total number of valid frames received by the corresponding Ethernet port
that have been discarded because of a lack of buffer space. This includes
frames discarded at ingress, as well as those dropped due to priority and
congestion considerations at the output queues
Rx Errors Total number of frames received by the corresponding Ethernet port that had
other types of errors
Rx Unicast Frames Total number of good unicast frames received through the corresponding
Ethernet port
Rx Multicast Frames Total number of good multicast frames received through the corresponding
Ethernet port
Rx Broadcast Frames Total number of good broadcast frames received through the corresponding
Ethernet port
Rx 64 Octets Total number of 64-byte frames received through the corresponding Ethernet
port
Rx 65-127 Octets Total number of frames with size of 65 to 127 bytes received through the
Rx 1024-long Octets Total number of frames with size of 1024 up to 1600 bytes received through
the corresponding Ethernet port
Tx Total Frames Total number of good frames transmitted by the corresponding Ethernet port
Tx Total Octets Total number of data octets carried by all the good frames transmitted by the
Tx Correct Frames Total number good frames transmitted by the corresponding Ethernet port
Tx Total Collisions Total number of collisions detected at the corresponding Ethernet port
Tx Unicast Frames Total number of good unicast frames transmitted by the corresponding
Ethernet port
Tx Multicast Frames Total number of good multicast frames transmitted by the corresponding
Ethernet port
Tx Broadcast Frames Total number of good broadcast frames transmitted by the corresponding
Ethernet port

Monitoring CL Physical Ports
Selecting the Class of CL Physical Ports for Monitoring

Use the following procedure to select the class of CL physical ports for which you
want to display the performance monitoring data. There are three classes of
physical ports:
• External (station) clock port
• SDH/SONET physical ports. SDH/SONET physical ports are located only on
• GbE physical ports. SDH/SONET physical ports are located only on CL.1/GbE
and CL.1/155GbE modules.
The selection is made in three steps:
• Selection of a specific CL module. This selection is necessary only when the
Megaplex-4100 is equipped with two CL modules.
• Selection of a type of port on the selected module.
• For SDH/SONET and GbE ports: selection of a specific port on the selected
module.
In addition to port performance and status data, you can also display the current
timing reference source for the SDH/SONET side.
To navigate to the required screen, use Monitoring>Physical Layer>CL.
A typical CL class selection screen is shown in Figure 6-64.
MP-4100
Monitoring>Physical Layer>CL
1. CL-A >
2. CL-B >
>

-----------------------------------------------------------------------------
Figure 6-64. Typical Physical Port CL Module Selection Screen
³ To select a class of CL physical ports:

1. Select the desired CL module on the CL module selection screen, and then
press <Enter>.
2. You will see the port type selection screen for the corresponding CL module.
A typical screen for CL-A is shown in Figure 6-65.

MP-4100
Monitoring>Physical Layer>CL>CL-A
1. Station Clock>
2. Ethernet >
3. SDH/SONET >
>

-----------------------------------------------------------------------------
Figure 6-65. Typical CL Physical Port Selection Screen
Displaying Monitoring Data for Station Clock Port

A typical physical port monitoring screen for the CL station clock interface is
shown in Figure 6-66. You can see this screen only if the Admin Status of the
clock interface on the selected CL module is Up.
MP-4100
Monitoring>Physical Layer>CL>CL-A >Station Clock
Status > (Normal)

Cable Type > (Balance)
Rx SSM > (SEC)
>

-----------------------------------------------------------------------------
Figure 6-66. Typical Station Clock Physical Port Monitoring Screen

The information displayed on the Station Clock monitoring screen is explained in
Table 6-16.

Table 6-16. Station Clock Physical Port Monitoring Parameters
Status Displays the status of the station clock interface :

• Normal – normal operation.
• Loss of Signal – no input signal. Often, this occurs when the input signal
is not connected, or the connected cable type (see Cable Type below)
does not match the selected interface.
• Loss of Sync – interface could not lock to the input signal. Often, this
occurs when the input signal frequency is different from the configured
frequency.
Cable Type Displays the type of cable actually connected to the station clock interface:
• Balance – cable suitable for use with a balanced interface.
• Unbalance – cable suitable for use with an balanced interface.
Rx SSM Displays the SSM message received by the clock interface. This parameter is
displayed only when using the 2048 kbps or 1544 kbps clock rate, provided clock
interface is configured to read the received SSM message.
The values available for SDH operation (relevant for 2048 KBPS) are as follows:
PRC – Primary source per ITU-T Rec. G.811 (associated SSM: 0010).
SSU-T – transit (T-type) secondary synchronization source per ITU-T Rec. G.812
(associated SSM: 0100).
SSU-L – Local (L-type) secondary synchronization source per ITU-T Rec. G.812
(associated SSM: 1000).
SEC – SDH equipment clock per ITU-T Rec. G.813 (associated SSM: 1011).
Unknown – unknown quality (associated SSM: 0000).
DNU – Do not use (associated SSM: 1111).
The values available for SONET operation per Telcordia GR-436-CORE (relevant for
1544 KBPS) are as follows:
ST1 – Stratum 1 traceable reference source (associated SSM: 0001).
TNC – Transit mode clock, traceable (associated SSM: 0100).
SMC – SONET Minimum Clock, Traceable (sub Stratum 3 quality – associated SSM:
1100).
Unknown – unknown quality (associated SSM: 0000).
Default: Unknown

Displaying Monitoring Data for the SDH/SONET Subsystem

Megaplex-4100 equipped with CL.1/155 or CL.1/155GbE modules can provide
monitoring data for the SDH/SONET subsystem current clock source, and for each
physical link of the SDH/SONET subsystem.
When path protection is used, you can also display the current protection status.
A typical task selection screen is shown in Figure 6-67.
MP-4100
Monitoring>Physical Layer>CL>CL-A >SDH/SONET
1. Timing >
2. Link 1 >
3. Link 2 >
4. Path Protection >
>

-----------------------------------------------------------------------------
Figure 6-67. Typical SDH/SONET Physical Layer Monitoring Task Selection Screen
³ To select a SDH/SONET physical port monitoring task:

Select the desired task, and then press <Enter>.
Displaying SDH/SONET Subsystem Timing Information
³ To display the SDH/SONET subsystem current clock source:

1. Select Timing and then press <Enter>.
2. You will see the Timing screen for the selected port. The information
presented on the screen depends on the timing mode configured in
accordance with the Configuring System Clock Sources section in Chapter 4.
Typical screens are shown in Figure 6-68.

MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Timing
Based on SSM > (Yes)

Tx Clock Source > (Internal)
Holdover > (No)
1. Port > (LINK 1)
2. Rx SSM > (UNKNOWN)
3. Tx SSM > (SEC)
>

-----------------------------------------------------------------------------
A. Typical Screen for Automatic SSM-Based Timing Selection

MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Timing
Based on SSM > (No)

Mode > (Master)
Tx Clock Source > (CL-A Link 1)
Holdover > (Yes)
1. Port > (LINK 1)
2. Rx SSM > (UNKNOWN)
3. Tx SSM > (SEC)
>

-----------------------------------------------------------------------------
B. Typical Screen for Preconfigured Timing Selection

Figure 6-68. Typical Timing Screens
The parameters displayed on the Timing screen are explained in Table 6-17.
Table 6-17. SDH/SONET Subsystem Timing (Physical Ports) Parameters
Based on SSM Displays the selection mode of the link transmit clock reference:
• Yes – The selection of the timing reference uses the SSM received in the S1
byte of the STM-1 or OC-3 overhead.
• No – The selection of the timing reference does not use the SSM.

Tx Clock Source Displays the source that provides the SDH/SONET subsystem transmit clock reference:
• A CL module port: displays the module (CL A or CL B) followed by the port
(Link 1 or Link 2)
• Internal – the internal oscillator has been selected
• System – the Megaplex-4100 nodal clock
Holdover Displayed only when Based on SSM is Yes:

• Yes – the SDH/SONET timing subsystem switched to the hold-over mode,
because no suitable reference source is available. If the problem persists for
more than 24 hours, the subsystem will switch to the Internal mode.
• No – normal operation
Port Type 1 and then press <Enter> to select a CL module port for which you want to display
the SSM parameters. After selecting a port, press <Enter> to display the current SSM
parameters
Rx SSM Displays the SSM received by the selected port. See Table 6-16 for the list of SSM
values.
When you see a number next to this field, you can display a help screen containing the
list of SSM by typing the number and then pressing <Enter>.
Tx SSM Display the SSM transmitted by the selected port.

When you see a number next to this field, you can display a help screen containing the
list of SSM by typing the number and then pressing <Enter>.
Displaying Monitoring Data for an SDH/SONET Link

After selecting a specific link on the screen of Figure 6-67, you can select the
desired monitoring data on a task selection submenu:
• Link status and manufacturer-provided data for the installed SFP
• Link performance monitoring statistics
• DCC transmission statistics
• Current optical parameters of the SFP serving the link interface
A typical task selection submenu for SDH/SONET link monitoring data is shown in
Figure 6-69.

MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Link 1
1. Link Status >

2. Link Statistics >
3. DCC Statistics >
4. Optical Parameters>
>

-----------------------------------------------------------------------------
Figure 6-69. Typical SDH/SONET Link Monitoring Task Selection Submenu
³ To display the SDH/SONET link status:

1. Select Link Status on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Link Status screen for the selected port. A typical Link Status
MP-4100
Monitoring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>Link Status
Section Status> (Normal)

Line Status > (Normal)
S1 Value > (0)
1. SFP >
>
ESC-prev.menu; !-main menu; &-exit; @-Output 1 M/ 1 C

-----------------------------------------------------------------------------
Figure 6-70. Typical Link Status (Physical Layer) Screen

The parameters displayed on the Link Status screen are explained in Table 6-18.

Table 6-18. Link Status (Physical Layer) Parameters
Section Status Displays the status of the SDH or SONET section (see Figure 6-71) terminated at the
selected link interface:
• Normal – normal operation
• LOS – loss of signal
• LOF – loss of frame alignment
• LOS and LOF – loss of signal and loss of frame alignment
Line Status Displays the status of the SDH or SONET line (see Figure 6-71) terminated at the
selected link interface:
• Normal – normal operation
• AIS – reception of AIS (alarm indication signal)
• RDI – reception of RDI (remote defect indication)
• AIS and RDI – reception of AIS and RDI
S1 Value Displays the value of the S1 byte of the STM-1 or OC-3 overhead
SFP Type 1 and then press <Enter> to display the manufacturer-provided SFP characteristics,
as retrieved from the SFP serving the selected link interface:
• Connector Type – displays the optical connector type, usually LC. MISSING
means that no SFP is inserted in the link SFP socket, or that the SFP cannot
provide the required information.
• Manufacturer Name – a concise identification of the SFP manufacturer
• Typical Max Range (km) – the maximum range to be expected in a typical
application, for a link terminated by two SFPs operating over the
recommended fiber
• Wave Length (nm) – nominal operating wavelength, in nm
• Fiber Type – SINGLE MODE or MULTI MODE fiber
No information can be displayed without an SFP inserted in the link SFP socket
Figure 6-71 explains the difference between an SDH/SONET section and

SDH/SONET line:
• An SDH/SONET section is a connection between two section termination
equipment units, that is, between units that handle only the section
overhead bytes carried in the SDH/SONET frames.
Equipment such as repeaters (regenerators) that regenerate the SDH/SONET
signal but do not process other parts of the SDH/SONET frames can serve
only as section termination units.
• An SDH/SONET line is a connection between two line termination units. Such
units handle both the section and line overhead bytes carried in the
SDH/SONET frames, and can also add and remove payload. A line can include
one or more sections.
Line termination equipment always serves also as section termination
equipment.

Line Line
Section Section Section
SDH/SONET SDH/SONET
.. Multiplexer Add-Drop Multiplexer ..
. (Path Multiplexer (Path .
Termination) Termination)
SDH/SONET Repeaters
(Regenerators)
Figure 6-71. Structure of Transmission Path in SDH/SONET Network
³ To display the SDH/SONET link physical port statistics:

1. Select Link Statistics on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Link Statistics interval selection screen. A typical Port
Statistics interval selection screen is shown in Figure 6-72.
MP-4100
...oring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>Link Statistics
3. Total >
>
ESC-prev.menu; !-main menu; &-exit 1 M/ 1 C

-----------------------------------------------------------------------------
Figure 6-72. Typical Interval Selection Screen
³ To display SDH/SONET link performance monitoring statistics for the current

interval:
2. You will see the Current Interval performance monitoring screen for the
selected link. A typical screen is shown in Figure 6-73. The selected port is
identified in the screen header.

MP-4100
...sical Ports>CL>CL-A>SDH/SONET>Link 1>Link Statistics>Current Interval
Valid Intervals[0 - 96]... (0)

ES ... (0)
SES ... (0)
UAS(SEFS) ... (689)
CV ... (0)
>

-----------------------------------------------------------------------------
Figure 6-73. Typical SDH/SONET Link Statistics>Current Interval Screen

The information displayed on the screen is automatically refreshed every few
seconds.
The performance monitoring counters displayed on the Link Statistics screen are
explained in Table 6-4.
³ To display SDH/SONET link performance monitoring statistics for a selected

interval:
1. Select Select Interval on the link statistics interval selection screen, and then
press <Enter>.
2. You will see the Select Interval performance monitoring screen for the
SDH/SONET link. This screen is similar to the screen for the current interval
shown in Figure 6-73, respectively, except for its header, Select Interval.
Intervals field.
³ To display totaled SDH/SONET link performance monitoring statistics:

1. Select Total on the link statistics interval selection screen and then press
<Enter>.
2. You will see the Total performance monitoring screen for the selected
SDH/SONET link. This screen is similar to the screen for the current interval
shown in Figure 6-73, respectively, except for its header, Total, and the
number of the 15-minute intervals to be displayed, which is by default 97,
which means all the intervals.

³ To display the SDH/SONET link DCC performance monitoring statistics:

1. Select DCC Statistics on the screen of Figure 6-69, and then press <Enter>.
2. You will see the DCC Statistics screen. A typical screen is shown in
Figure 6-74.
automatically refreshed every few seconds.
The statistics displayed on the DCC Statistics screen are explained in Table 6-19.
MP-4100
...toring>Physical Layer >CL>CL-A >SDH/SONET>Link 1>DCC Statistics
Rx Total Frames ... (0)

Rx Total Bytes ... (0)
Rx CRC Error ... (0)
Rx Dropped ... (0)
Tx Total Frames ... (0)
Tx Total Bytes ... (0)
>
C - Clear
-----------------------------------------------------------------------------
Figure 6-74. Typical DCC Statistics Screen
Table 6-19. DCC Statistics Performance Monitoring Statistics
Rx Total Frames Total number of frames received through the DCC
Rx Total Bytes Total number of data octets carried by all the frames received through the DCC
Rx CRC Error Total number of frames with invalid CRC received through the DCC
Rx Dropped Total number of valid frames received through the DCC that have been dismoduleed
because of a lack of buffer space. This includes frames discarded at ingress, as well as
those dropped due to priority and congestion considerations at the output queues
Tx Total Frames Total number of frames transmitted through the DCC
Tx Total Bytes Total number of data octets carried by all the frames transmitted through the DCC
³ To display the port Optical Parameters screen:

1. Select Link Status on the screen of Figure 6-69, and then press <Enter>.
2. A typical link Optical Parameters screen is shown in Figure 6-75. The
information displayed on the screen is explained in Table 6-20.

MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Link 1>Optical Parameters
SFP inserted > (Yes)

TX Optical Power(dBm) ... (-2)
LASER Bias (mA) ... (5)
LASER Temp C(F)[0 - 25... (40)
RX Optical Power (dBm)... (-12)
Supply Voltage(V) > (3)
>

-----------------------------------------------------------------------------
Figure 6-75. Typical Link Optical Parameters Screen
Table 6-20. Typical Link Optical Parameters
SFP Inserted Displays Yes when an SFP is installed in the port connector.
If no SFP is inserted, the next fields are not displayed
Tx Optical Power(dBm) The current optical power, in dBm, transmitted by the SFP
Laser Bias (mA) The measured SFP laser bias current, in mA
Laser Temp C(F) The measured SFP laser temperature, in °C or °F
Rx Optical Power(dBm) The current optical power, in dBm, received by the SFP
Supply Voltage (V) The measured SFP laser supply voltage, in volts
Displaying Path Protection Monitoring Data for an SDH/SONET

Link
³ To display the current path protection situation:

1. Select Path Protection on the screen of Figure 6-69, and then press <Enter>.
2. You will see the Path Protection screen port selection screen. The screen
presents the list of PDH ports for which path protection has been configured.

MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Path Protection
1. PDH []
>

-----------------------------------------------------------------------------
Figure 6-76. Typical SDH/SONET Path Protection PDH Port Selection Screen
3. Select the desired PDH ports, and then press <Enter> to display the path
protection information.
A typical screen is shown in Figure 6-77. The information displayed on the Path
Protection screen is explained in Table 6-21.
MP-4100
Monitoring>Physical Layer>CL>CL-A>SDH/SONET>Path Protection>PDH 1
# Payload Working Protection Current

1 PDH3 LA1:2:6:3 LB1:3:2:1 Protection3
>

-----------------------------------------------------------------------------
Figure 6-77. Typical SDH/SONET Path Protection Screen
Table 6-21. SDH/SONET PDH Port Path Protection Monitoring Data
# Index number
Payload Identifies the payload (PDH) port mapped to the corresponding TU-12 or VT1.5
Working Identification of the configured working port in the following format:

LX:TUG3:TUG2:TU12 for SDH, and L:STS-1:TUG2:VT1.5 for SONET, where X is the CL
module identification, A or B, and L is the link number, L1 or L2.
The TUG-3:TUG-2:TU format is described in Table 6-8 and Table 6-9.
Protection Identification of the configured protection port (same format)
Current Identification of the current protection port: Working or Protection

Displaying Monitoring Data for the GbE Ethernet Subsystem

Megaplex-4100 equipped with CL.1/GbE or CL.1/155GbE modules can provide
monitoring data for each physical port of the GbE subsystem.
A typical port selection screen is shown in Figure 6-78.
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet
1. GbE 1>
2. GbE 2>
>

-----------------------------------------------------------------------------
Figure 6-78. Typical Ethernet Physical Layer Monitoring Task Selection Screen
³ To select a GbE port for monitoring:

Select the desired port, and then press <Enter>.
Displaying Monitoring Data for a GbE Port

After selecting a specific link on the screen of Figure 6-78, you can select the
desired monitoring data on a task selection submenu:
• Port status.
• Ethernet performance monitoring counters
For ports equipped with SFP sockets, you can also display information on the SFP
serving the port interface.
A typical task selection submenu for GbE port monitoring data is shown in
Figure 6-69.

MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet
1. GbE 1>
2. GbE 2>
>

-----------------------------------------------------------------------------
Figure 6-79. Typical GbE Link Monitoring Task Selection Submenu
³ To display the GbE port status:

1. Select Port Status on the screen of Figure 6-79, and then press <Enter>.
2. You will see the Port Status screen for the selected port. A typical Port Status
screen, for a GbE port with electrical interface (RJ-45 connector), is shown in
Figure 6-80.
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>Port Status
Admin Status> (Up)

Link Status > (Link Up)
Rate > (1000 Mbps Full Duplex)
Rdn status > (No redundancy)
>

-----------------------------------------------------------------------------
Figure 6-80. Typical GbE Port Status (Physical Layer) Screen

The parameters displayed on the Link Status screen are explained in Table 6-22.

Table 6-22. GbE Port Status (Physical Layer) Parameters
Admin Status Displays the GbE port administrative status:

• Up – the port is enabled, and can carry traffic
• Down – the port is disabled, and cannot carry traffic
Link Status Displays the status of the link connected to the GbE port:
• Up – the link is operating normally, and carrying traffic
• Down – the link does not carry traffic, e.g., because it is not connected to an
active LAN
Rate Displays the port current rate and mode:

• 10Mbps Half Duplex – Half-duplex operation at 10 Mbps.
• 10Mbps Full Duplex – Full-duplex operation at 10 Mbps.
• 100Mbps Half Duplex – Half-duplex operation at 100 Mbps.
• 100Mbps Full Duplex – Full-duplex operation at 100 Mbps.
• 1000Mbps Half Duplex – Half-duplex operation at 1000 Mbps
• 1000Mbps Full Duplex – Full-duplex operation at 1000 Mbps
Rdn Status Displays the redundancy status of the port:

• No Redundancy – the port is not part of a redundancy pair
• Active – 1+1 redundancy is used, and the port is the active port of the
redundancy pair
• Standby – 1+1 redundancy is used, and the port is the standby port of the
redundancy pair
SFP This item appears only when the port is equipped with an SFP, and is used to display
the manufacturer-provided SFP characteristics, as retrieved from the SFP serving the
selected port. To display the SFP characteristics, type 1 and then press <Enter>:
• Connector Type – displays the optical connector type, usually LC
• Manufacturer Name – a concise identification of the SFP manufacturer
• Typical Max Range (km) – the maximum range to be expected in a typical
application, for a link terminated by two SFPs operating over the
recommended fiber
• Wave Length (nm) – nominal operating wavelength, in nm
• Fiber Type – SINGLE MODE or MULTI MODE fiber
No information can be displayed without an SFP inserted in the port SFP socket
³ To display the GbE port Ethernet counters:

1. Select ETH Counters on the screen of Figure 6-79, and then press <Enter>.
2. You will see the ETH Counters screen for the selected port. The screen
includes two pages: use N and P to scroll between two pages. A typical ETH
Counters screen is shown in Figure 6-81.

MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>ETH Counters
============= =============
Rx Total Frames ... (0) Tx Total Frames ... (0)
Rx Broadcast Frames ... (0) Tx Unicast Frames ... (0)
Rx Multicast Frames ... (0) Tx Total Bytes ... (0)
Rx Correct Frames ... (0) Tx Correct Frames ... (0)
Rx Total Bytes ... (0) Tx Discard Frames ... (0)
Rx Dropped ... (0) Total Collision ... (0)
Rx Jabber Frames ... (0)
Rx Invalid CRC Frames... (0)
Rx Fragment Frames ... (0)
... (N)
>

-----------------------------------------------------------------------------
A. First Page
MP-4100
Monitoring>Physical Layer>CL>CL-A>Ethernet>GbE 1>ETH Counters
... (P)
RX Statistics
=============
Rx 64b Frames ... (0)
Rx 65b-127b Frames ... (0)
Rx 256b-511b Frames ... (0)
Rx 512b-1023b Frames... (0)
Rx 1024b-max Frames ... (0)
Rx Pause Frames ... (0)
Rx Undersized Frames... (0)
Rx Oversized Frames ... (0)
>

-----------------------------------------------------------------------------
B. Second Page
Figure 6-81. Typical GbE Port ETH Counters (Physical Layer) Screens
Table 6-23 explains the statistics parameters.
automatically refreshed every few seconds. You can clear the displayed statistics
(that is, reset the displayed performance monitoring counters) by typing C. The
counters are also reset when the Megaplex-4100 is powered up.

Table 6-23. GbE Port ETH Counters (Physical Layer) Performance Monitoring Statistics
Rx Total Frames Total number of frames received through the Gbe port
Rx Broadcast Frames Total number of good broadcast frames received through the Gbe port
Rx Multicast Frames Total number of good multicast frames received through the Gbe port
Rx Correct Frames Total number of frames with correct FCS that have been received through the
Gbe port
Rx Total Bytes Total number of data octets carried by all frames received through the Gbe
port
Rx Dropped Total number of valid frames received by the Gbe port that have been
discarded because of a lack of buffer space. This includes frames discarded at
ingress, as well as those dropped due to priority and congestion
considerations at the output queues.
Frames dropped at egress due to excessive collisions are not included in this
count, but are counted by the Excessive Collision counter
Rx Jabber Frames Total number of frames received by the Gbe port during jabber (such frames
are frames with a data field length exceeding 1518 or 1536 bytes, and also
having invalid CRC)
Rx Invalid CRC Frames Total number of frames received by the Gbe port which met the following
conditions:
• Frame data length is between 64 bytes, and 1518 or 1536 bytes
(depending on mode)
• Frame has invalid CRC
• Collision event has not been detected
• Late collision event has not been detected
Rx Fragment Frames Number of fragmented frames received at the Gbe port (a fragmented frame
is a frame with a data field length less than 64 bytes and invalid CRC, for
which no collision event and no late collision event have not been detected
during its reception)
Rx 64b Frames Total number of 64-byte frames received through the Gbe port
Rx Frames 65b-127b Total number of frames with size of 65 to 127 bytes received through the
Frames Gbe port
Frames Gbe port
Frames Gbe port
Frames Gbe port
Rx Frames 1024b-max Total number of frames with size of 1024 to 1600 bytes received through the
Frames Gbe port
Rx Pause Frames Total number of pause frames received through the Gbe port

Rx Undersized Frames Total number of frames shorter than 64 bytes received through the Gbe port
Rx Oversized Frames Total number of frames longer than 1600 bytes received through the Gbe
port
Tx Total Frames Total number of good frames transmitted by the Gbe port
Tx Unicast Frames Total number of good unicast frames transmitted by the Gbe port
Tx Total Bytes Total number of data octets carried by all the good frames transmitted by the
Gbe port
Tx Correct Frames Total number of correct frames that have been transmitted by the Gbe port
Tx Discard Frames Total number of valid frames that were intended for transmission through the
bundle that have been discarded because congestion at the output
Total Collision Total number of collisions detected at the Gbe port

6.2 Detecting Errors

The Megaplex-4100 includes an extensive subsystem that checks the validity of
the user’s configuration activities and reports any conflicts and errors.
Table 6-24 lists the error messages generated by Megaplex-4100, and explains
their interpretation (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, you will get a warning when a programmed
module is not installed in the chassis.
Error Errors that prevent proper operation of the Megaplex-4100

in its intended application (for example, invalid or timeslot
assignment).
The messages are listed in ascending order of their codes.
Table 6-24. Error Messages
Code Type Syntax Meaning
Global Sanity Messages
000 to N/A Reserved N/A

099
100 Error AT LEAST ONE PS CARD MUST Check that at least one power supply module is defined in
BE DEFINED the system configuration
101 N/A Reserved N/A
102 Error AT LEAST ONE CL CARD MUST At least one CL module must be defined in the system
BE DEFINED configuration
103, N/A Reserved N/A

104
105 Error ILLEGAL CLOCK SOURCE FOR The selected master clock source is invalid for one of the
MASTER CLOCK following reasons:
• The configured module port cannot supply a
reference clock
• The configured port number is invalid for the
selected module
• The port rate is not suitable for use as clock
source (e.g., LS-12 channel operating at a rate
of 14.4 kbps)
108
6-78 Detecting Errors Megaplex-4100 Ver. 2.0

109 Error ILLEGAL MASTER CLOCK The I/O module port is selected as master clock source,
SOURCE MODE but its interface type is not DTE
110 Warning MODULE TYPE MISMATCH Differences have been found between the modules
actually installed in the equipment, and the modules
programmed in the database
111 Error MASTER CLOCK NOT When configuring the master clock source to be locked to
CONNECTED the receive clock of a module/channel, the source
module/channel must be connected
112 Error FALLBACK CLOCK NOT When configuring the fallback clock source to be locked
CONNECTED to the receive clock of a module/channel, the source
module/channel must be connected
113 Error ILLEGAL CLOCK SOURCE FOR The selected fallback clock source is invalid for one of the
FALLBACK CLOCK following reasons:
• The configured module port cannot supply a
reference clock
• The configured port number is invalid for the
selected module
• The port rate is not suitable for use as clock
source (e.g., LS-12 channel operating at a rate
of 14.4 kbps)
115 Error ILLEGAL FALLBACK CLOCK The I/O module port has been selected as fallback clock
SOURCE MODE source, but its interface type is not DTE
117 Error ILLEGAL MASTER CLOCK The interface of the ISDN channel selected as master
SOURCE INTERFACE clock reference cannot provide a reference clock.
For HSU-6/HSU-12 modules, the channel must be
configured as NT
118 Error ILLEGAL FALLBACK CLOCK The interface of the ISDN channel selected as fallback
SOURCE INTERFACE clock reference cannot provide a reference clock.
For HSU-6/HSU-12 modules, the channel must be configured
as NT
119 N/A Reserved for future use N/A
121 Warning INTERFACE HW/SW MISMATCH The interface type configured by the management system
differs from the interface selected by means of jumpers
123 Error DIFFERENT CL CARDS FOR Different CL module types have been installed in slots
REDUNDANCY CL-A and CL-B, and therefore CL redundancy is not
available
124 to N/A Reserved for future use N/A

139
Megaplex-4100 Ver. 2.0 Detecting Errors 6-79

Global Module Sanity Messages

144
145 Error CLOCK MODE/CLOCK SOURCE The EXT-DCE clock mode cannot be selected when the
MISMATCH port interface is configured as LT-1 (applicable only for
HSU-6 and HSU-12 modules)

151
152 Warning RESTORATION TIME DOES NOT For T1 links, the restoration time should be 10 seconds,
MATCH THE STD according to the standard.
For E1 links, the restoration time should be in accordance
with ITU-T recommendations
154 Error ILLEGAL NUMBER OF WIRES Voice modules with /FXO and /FXS interfaces support only
the two-wire interface.
Only for voice modules with /E&M interface, is it possible
to select between two-wire and four-wire interfaces. In
addition, for VC-4/8/16 modules with /E&M interface, you
must select the same interface type for consecutive pairs
of channels (for example, 1, 2 or 15, 16)

161
162 Error ROUTING PROTOCOL/ You can enable the RIP 2 protocol on an I/O module port
MNG TYPE MISMATCH only when the inband management method is configured
for DEDICATE PPP or DEDICATE FR

164

179
Port Sanity Messages

184
185 Error ILLEGAL REDUNDANCY The redundancy assignment of one port does not point to
ASSIGNMENT another port
186 Error ASYMMETRIC REDUNDANCY The configuration of two ports operating as a redundant
ASSIGNMENT pair must be identical

192

193 Error Y CABLE ENABLE ONLY When using port redundancy with Y-cable, the redundancy
BETWEEN TWO CARDS partner slot must be an external port of another module
of the same type
194 Error ILLEGAL IDLE CODE SELECTION When configuring the idle code for a module with T1
interface, the second digit of the idle code must not be 0

196
197 Error LINE CODE/INBAND MNG TYPE For ports with T1 using the B7 line code, it is not allowed
MISMATCH to use inband management

239

247

259
HS-12N/HS-6N Sanity Messages
260 Error FIFO SIZE TOO SMALL The manually-selected FIFO size must be equal or larger
than the minimum required FIFO size, as required for the
selected rate and link type (E1 or T1)
261 Error ILLEGAL CHANNELS RATE All the channels are configured either for operation at
COMBINATION 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 adjacent channel (e.g., channel
2) is not allowed.
• The total rate of 2 adjacent channels must not require
more than 31 timeslots
263 Error CTS SHOULD BE SAME FOR ALL All the channels of the specified module must be
CHANNELS configured with the same CTS mode

269
HSU-12/HSU-6 Sanity Messages

273

274 Error EXTERNAL MODEM HW/SW For HSU-6 or HSU-12 port configured for operation in the
CONFIG MISMATCH /1 mode and connected to external modems, the
following restrictions apply:
• ASMi-31-2 modems with V.110 rate adaptation:
in the asynchronous mode, the number of data
bits can be only 7 or 8, and the supported data
rates are 1.2 to 38.4 kbps
• ASMi-31-2 modems without V.110 rate
adaptation: do not support the 56 kbps rate in
the synchronous mode
• ASMi-31 modems: do not support 5 and 6 data
bits in the asynchronous mode; the 56 kbps
rate; the RLB and LLB functions; the use of
V.110 rate adaptation
299
VC Modules Sanity Messages
300 Error ILLEGAL SIGNALING METHOD You can select the channel associated signaling method
only when an E1 module port with G732S framing is used.
You can select the ROBBED BIT MULTIFRAME signaling
transfer method only for E1 links with G732S framing, or
on T1 links.
The signaling mode of a voice channel connected as a
PSTN port to a V5.1 port must be CAS
301 Warning VOICE CODING LAW STD The selected voice companding law differs from the
(T1/E1) MISMATCH companding law specified by the standards: the A-law is
generally used for E1 links, and the μ-law is generally used
on T1 links
302 Warning PROPRIETARY SIGNALING For E1 links with G732S framing, it is not recommended to
METHOD use the ROBBED BIT FRAME and the ROBBED BIT
MULTIFRAME signaling transfer modes.
For T1 links, it is not recommended to use the ROBBED
BIT FRAME signaling transfer mode
303 Error TX LEVEL/INTERFACE The transmit gain selected for the specified channel is not
MISMATCH within the supported range
304 Error RX LEVEL/INTERFACE The receive gain selected for the specified channel is not
MISMATCH within the supported range
305 Error OOS/INTERFACE MISMATCH The selected OOS mode cannot be used on this interface
type
306 Error SIGNALING PROFILE/INTERFACE The selected profile cannot be used on this type of
MISMATCH interface

308

309 Error SIG PROFILE/NUM OF SIG BITS The selected signaling profile cannot be used with G732N
MISMATCH or SF (D4) framing mode

311
312 Error NO SIG IS ILLEGAL FOR THIS The selected interface cannot be used with the
INTERFACE NO SIGNALING option

319
Timeslot Sanity Messages
320 Error ILLEGAL DEST SLOT/PORT One of the following conditions has been detected:
CONNECTION • One or more module channels are connected to a
disabled port (that is, a port with Admin Status =
DOWN).
• 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 DS1 cross-connection: the port cross-connect
definitions are not symmetrical
321 Error ILLEGAL TIMESLOT Check 320 has been successfully passed, but the required
ASSIGNMENT number of timeslots does not match exactly the number
of timeslots assigned on the relevant module port
323 Error ILLEGAL BYPASS CONNECTION The number of timeslots routed between two module
ports must be the same
325 Error TS-16 IS RESERVED FOR CAS To bypass signaling information between E1 ports on
SIGNALING different modules, the following requirements must be
met:
• Both ports must use G732S framing, with or without
CRC-4 (G732S, G723S-CRC4).
• Timeslot 16 of one module must be routed to timeslot
16 on the other module
327 Error ILLEGAL POSITION OF TS BIT When using split timeslot assignment:
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
328 Error TS ASSIGNMENT/TS REQUEST The timeslot bit assignment does not match the
MISMATCH requirements for such timeslots

331

332 Error INCORRECT DATA TYPE Check that the definition of the timeslot type corresponds
to the type of information generated by the module using
the timeslot:
• Timeslot routed to data I/O module: the type must be
DATA (this also applies to timeslots routed to HSF
modules).
• Timeslot routed to voice I/O module: the type must be
VOICE.
In addition, check the following:
• The types of timeslots bypassed between links must be
identical.
• No timeslot is assigned for management traffic when
inband management is disabled
334 Warning TS DATA TYPE DOESN’T MATCH For T1 links, do not use the B7 line code when one or
B7 LINE CODE more timeslots are defined as data timeslots

337
338 Error ILLEGAL BROADCAST The timeslot assignment for the specified channel is not
DEFINITION correct. Check the configuration and correct as required
339 Error NOT COMPLETE BROADCAST The timeslot assignment for the specified channel is not
DEFINITION complete. Check the timeslot assignment at both the
channel and the port level and correct as required

349
LS-6N/LS-12 Sanity Messages
351 Error BANDWIDTH OVERFLOW The bandwidth allocated to the internal port of the LS-6N
module must be greater than, or equal to the sum of the
following:
• The bandwidths allocated to the external ports.
• Management channel, in case the remote unit is a KM
working in slave mode.
• Frame synchronization.
• Channel end-to-end control signals (one per pair)
353
354 Error SUB PORTS NOT IN SAME RATE Pairs of channels of an LS-12 module must operate in the
GROUP same rate group

356 Error SUB PORTS NOT SAME Pairs of channels of an LS-12 module must be connected
INTERNAL to the same internal port
358 Error EXT RATE NOT APPLICABLE The external port rate is not compatible with the data
WITH INT RATE rate allocated on the link to the corresponding internal
port
359 Error NO EXTERNAL CHANNEL The internal port is connected to the link, but no external
CONNECTED port is connected to it
360 Error INTERNAL CHANNEL NOT The internal channel is not connected to a link
CONNECTED

362

389

403

409
HSU-12, HSU-6 Additional Sanity Messages
410 Error ILLEGAL D CHANNEL To connect an internal compression port, at least one
COMPRESS ASSIGNMENT internal D-channel port must be configured as connected
to that port
412 Error ILLEGAL INTERFACE All the open external ports must be configured with same
COMBINATION interface (NT-I, LT-I, LT-1)

419
Voice Modules Sanity Messages
421 Error ILLEGAL E&M TYPE This message, relevant only for E&M modules, is displayed
COMBINATION when different signaling types have been selected for
channels in a group of 4 consecutive channels (for
example, 1, 2, 3, 4; 5, 6, 7, 8; etc.)
422 Error ILLEGAL INTERFACE This message, relevant only for VC-8/VC-16 modules with
COMBINATION FXS and FXO interfaces, is displayed when you are trying
to configure different signaling interfaces for channels
within the same group of 8 consecutive channels (1 to 8
or 9 to 16)

423 Error ILLEGAL SIGNAL FEEDBACK FXO This message, relevant only for VC-8/VC-16 modules with
COMBINATION FXO interfaces, is displayed when you are trying to
configure different signaling feedback states for channels
within the same group of 8 consecutive channels (1 to 8
or 9 to 16)

429

431

434

440
441 Error UNCONSECUTIVE ONES IN The binary representation of an IP subnet mask must
SUBNET MASK start with a string of consecutive “1s” followed by the
desired number of consecutive “0s”.

450

454

481
M8SL Sanity Messages
482 Error RATE/TIME SLOT ASSIGNMENT The line rate configured for the M8SL port does not
MISMATCH match the number of timeslots assigned
483 Error ILLEGAL CLOCK SOURCE The M8SL port configured as clock reference is not
configured as STU-R

489

514

539

550
551, N/A Reserved for future use N/A

552

554 Error TS COMPACTION MODE DOES It is not allowed to configure timeslots as Spare when the
NOT MATCH WITH SPARE TS TS Compaction Mode is No Mapping or Low Ts Mapping
TYPE

559

699
VC-4/OMNI Sanity Messages
700 Error OTHER INTERNAL THAN THE If the DSP Mode is POINT-TO-POINT for the external level,
FIRST ONE IS CONNECTED only the first internal channel of this external link can be
connected. All the other internal channels must be
configured as NOT CONNECTED)
701 Error ILLEGAL BUS PROTECTION If the Bus Protection Point is YES for the external level,
POINT TYPE only the first two internal channels of this external link
can be connected (internal channels 3 and 4 must be
configured as NOT CONNECTED)
702 Error FIRST CORRESPONDING If the Operation Mode is POINT-TO-POINT DST, and the
INTERNAL (1,5,9,13) MUST BE first internal channel is not connected, the other internals
CONNECTED can be connected and can carry traffic
703 to N/A Reserved for future use

999
SDH/SONET Sanity Messages
1000 Error TOO MUCH VCS/VTS The maximum number of virtual containers hat can be
used by one virtually concatenated group cannot exceed
63 for VC-12, or 64 for VT1.5
1001 Error TOO MUCH MINIMUM NUMBER The minimum number of virtual containers (VC-12 or
OF VCS/VTS VT1.5) in a group is 2
1002 Error VC GROUP IS NOT CONNECTED The virtually concatenated group is not connected. Check
and correct
1003 N/A Reserved

to
1006
1007 Error DIFFERENT CLS FRAME The two CL modules installed in the Megaplex-4100 must
STRUCTURE use the same link standards (either SDH or SONET)
1008 Error DIFFERENT CLS PDH FRAME It is not allowed to use both E1 and T1 framing
1009 N/A Reserved
1010 Error ILLEGAL PDH CHANNEL Check and correct the mapping of the PDH ports to the
MAPPING SDH/SONET link
1011 Error ILLEGAL TUG3/STS1 PORT The TUG-3/STS-1 cannot be used to carry traffic and
COMBINATION serve for protection at the same time

1012 Error ILLEGAL VCG MAPPING Check and correct the virtually concatenated group
mapping
1013 Error ASYMMETRIC VCG MAPPING When the use of path trace is enabled, make sure that
identical numbers of VCs/VTs are assigned on the two
links
1014 Error PDH CHANNEL IS NOT The PDH channel is mapped, but its Admin Status is
CONNECTED DOWN

to
1999
System Sanity Messages
2000 Error DIFFERENT CL CARDS FOR Different CL module types have been installed in slots
REDUNDANCY CL-A and CL-B, and therefore CL redundancy is not
available
2001 Error AT LEAST ONE CLOCK SRC At least one clock source must be defined in the master
MUST BE DEFINED clock reference list
2002 Error ILLEGAL IP ADDRESS The selected IP address is invalid, or the default gateway
is not in same subnet as the host IP address
2003 Error INSUFFICIENT LICENSE POINTS License points purchased not sufficient for activated
services.

to
2029
Bundle Sanity Messages
2030 Error REDUNDANCY IS N/A FOR Ports bonded in an MLPPP bundle cannot be included in a
MLPPP LINKS redundancy pair
2031 Error UNFRAMED T1 CAN’T BE An HDLC bundle cannot be terminated at an unframed T1

ASSIGNED TO BUNDLE port
2032 Error MLPPP LINK SHOULD BE Ports bonded in an MLPPP bundle must use the DS1
UNFRAMED cross-connect mode, and must be configured as
UNFRAMED
2034 Error DIFFERENT BUNDLE AND LINK The I/O slot specified for a bundle and its link must be the
SLOTS same
2035 Error BUNDLE BANDWIDTH ALREADY The total number of links (for an MLPPP bundle) or
ASSIGNED timeslots (for a HDLC bundle) assigned to a bundle must
be equal to the bundle rate
2036 Error MORE THAN ONE MLPPP Only one MLPPP bundle can be active on any given I/O
BUNDLE FOR SLOT module

2037 Error BUNDLE BW MORE THAN LINK The maximum number of timeslots available to a HDLC
CAPABILITY bundle is 24 timeslots when terminated at a T1 port, and
32 when terminated at an E1 port
2038 Error ILLEGAL SRC SLOT/PORT Before setting the bundle Admin Status to UP, make sure
CONNECTION that the source ports are connected to this bundle, and
vice-versa
2039 Error EVEN TS NUM MUST DEFINED Ethernet bundle payload rate must be a multiple of
FOR BUNDLE 128 kbps, and thefore the bundle must contain an even
number of timeslots
2040 Error LINKS ASSIGNED FOR CARD Maximum number of ports associated with Ethernet
BNDS EXCEEDED bundles in any specific I/O slot is 8
2041 Error ILLEGAL NUMBER OF The maximum number of timeslots that can be assigned
TIMESLOTS to an Ethernet bundle on a framed E1/PDH E1 port is 30,
and the maximum for a T1/PDH T1 port is 24.
The maximum for a unframed E1/PDH E1 port is 32
timeslots
2042 Error ILLEGAL BUNDLE SLOT All 4 Ethernet bundles that can be defined on a specific
ASSIGNMENT PDH port can be assigned (for processing) to the same
I/O module
2043 Error MAX 4 BUNDLES MAY BE Maximum number of Ethernet bundles per E1/T1/PDH port
DEFINED PER LINK is 4
2044 Error DS1 FRAME TYPE MISMATCH When using DS1 cross-connect on E1/PDH E1 ports, the
Line Type must be G.732N, G.732N-CRC4, or Unframed.
2045 Error DS1 LINE CODE MISMATCH For T1 ports, the Line Code must be B8ZS or Transparent.
2046 Error SIG PROFILE/REDUNDANT If redundancy partner port is a PDH port, the signaling
PARTNER MISMATCH profile of the associated port must be NONE.

to
2049
Flow Sanity Messages
2051 Error ILLEGAL C-VLAN/SP-VLAN When configuring an E-line flow with C-VLAN configured
COMBINATION as aware, you must also configure the SP-VLAN of the CL
GbE port
2052 Error SP-VLAN MUST BE VALID When configuring an E-LAN flow type, the CL GbE ports
must have their SP-VLAN configured
2053 Error C-VLAN TYPE CAN'T BE When configuring an E-line flow with C-VLAN configured
UNAWARE as unaware, the corresponding CL GbE port must have an
SP-VLAN configured

2054 Error ILLEGAL FLOW/SP-VLAN When configuring an E-line flow on an MLPPP bundle, an
COMBINATION SP-VLAN can be configured only when all the flow ports
are from same slot
2055 Error Reserved for future use N/A
2056 Error FLOW CONSISTS OF MINIMUM A flow must include at least two bridge ports
TWO BP'S
2057 Error C-VLAN MUST BE UNIQUE PER The C-VLAN ID configured on a bridge port must be
BP unique. The same C-VLAN ID can however be used for
other bridge ports in other E-line flows
2058 Error IO BP'S MEMBERS IN DIFF An I/O port can not be a included in different flow types
FLOW TYPES
2059 Error SP-VLAN ALREADY USED BY An SP-VLAN ID must be unique per system
ANOTHER BP
2060 Error BP WITH C-VLAN UNAWARE IS If a bridge port VLAN mode is unaware, it can participate
UNIQUE in only one flow
2061 Error SECONDARY GBE CAN'T When using 1+1 redundancy for the GbE ports, it is not
CONTAIN FLOWS allowed to configure the secondary GBE port as a bridge
port in any flow
2062 Error ETH BP OF SAME SLOT CAN’T An Ethernet port configured as a bridge port located on
BE ON OTHER the same module in one flow cannot be configured in
flows that include bridge ports on other modules
2063 Error ILLEGAL FLOW, TWO ETH BPS It is allowed to configure a flow between two Ethernet
OF SAME SLOT ports on the same module

to
2074
M8SL Sanity Messages
2075 Error MAX BANDWIDTH MISMATCH Maximum bandwidth configured on the SHDSL line does
not match the number of timeslots assigned
MPW-1 Sanity Messages
2100 Error SAME IP FOR ROUTER IFACE & The same IP address has been defined for both the
D.GATEWAY 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 addresses (0.0.0.0) have not yet been changed.
2101 Error ROUTER IFACE IP&GTWAY At least one of the IP addresses assigned to router
NOT SAME SUBNET interfaces must be in the IP subnet of the Megaplex-4100
router default gateway.

2103 Error OUT PW LABEL IS NOT This message, which is generated only after the specified
UNIQUE pseudowire is switched to the Connect state, indicates
that two or more pseudowires directed to a given
destination IP address 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.
For UDP/IP PSNs, the UDP port is automatically assigned in
accordance with the pseudowire label value, therefore you
need to change the pseudowire labels to avoid conflict.
The assignment rules are as follows (see Chapter 3 for
parameter descriptions):
• When the configured pseudowire Payload
Format is V1 (proprietary format), the source
UDP port is Out PW Label + 1
• In all the other cases, the source UDP port value
is equal to the configured Out PW Label value
See also sanity error 2123.
2104 Error IN PW LABEL IS NOT UN This message, which is generated only after the specified
pseudowire is switched to the Connect state, 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.
See sanity error 2103 for UDP port assignment rules.
2105 Error IP & NEXT HOP SAME FOR This message is generated after the specified static route
STATIC ROUT 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.
2106 Error STATIC ROUTE IP IS NOT This message, which is generated only after the specified
UNIQUE 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
2107 Error ROUTER IFACES CAN'T BE ON The IP addresses assigned to the router interfaces must
SAME SUBNET be in different IP subnets.
2108 Error MORE THAN 16 PWS FOR You are trying to connect too many pseudowires to the
INTERNAL DS1 same internal DS1 port (the maximum is 16 pseudowire
per port).

2110 Error ILLEGAL FAR END TYPE The pseudowire Far End Type parameter must match the
CONFIGURATION framing mode of the internal DS1 port supporting the
pseudowire:
• Framed mode: select E1, T1 ESF, or T1 SF
• Unframed mode: select UNFRAMED.
2111 Error INTERNAL DS1 OF PW IS The internal DS1 port assigned to a pseudowire is
DOWN configured as Down. Change its administrative status to
Up.
2112 Warning PW ASSIGNMENT MISMATCH When a pseudowire is created, it is necessary to assign it

timeslots on a specific internal DS1 port.
This message is generated only after the specified
pseudowire is in the connecting state.
You can assign the timeslots during the configuration of
the pseudowire service parameters; in addition, connect
the same timeslots of the internal DS1 port to the
prescribed I/O or PDH port.
2113 Error TOO MANY ROUTER You are trying to configure more than 6 router interfaces
INTERFACES on a Megaplex-4100 module (Megaplex-4100 supports a
maximum of 6 router interfaces). Check and remove
unused interfaces.
2114 Error NUM OF BYTES IN FRAME When using the CESoPSN protocol, the maximum number
EXCEEDS 1440 of bytes per packet exceeds the maximum allowed, 1440
bytes.
The number of bytes is determined by the Payload Size
(Frames in Packet) parameter, multiplied by the number of
timeslots assigned to the corresponding pseudowire.
2115 Warning CHANGE MAY CAUSE DATA As a result of the last configuration actions, during the
INTERFERENCE database update you are initiating the internal
Megaplex-4100 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 Megaplex-4100. If this is not
acceptable, postpone the update and perform it while
traffic load is light.
2116 Error WRONG TIMESLOT When the redundancy partner of an internal DS1 port of
ASSIGNMENT the Megaplex-4100 is a T1 port, it is not allowed to assign
more than 24 timeslots on the internal DS1 port.
2117 Error WRONG SATOP PARAMETERS When using the SAToP protocol, make sure to configure
the following parameters as explained below:
• Cross-connect mode of internal DS1 port: DS1.
Therefore, only a single pseudowire can be
defined on this internal DS1 port.
• Far End Type: UNFRAMED.

2118 Error FAR END WRONG Pseudowires configured on different Megaplex-4100

PARAMETERS modules must be configured with different peers, even if
the destination address is the same (see also sanity error
2128).
Using different peer numbers will result in the creation of
different internal flows, each directed to the relevant
router interface
2119 Error REDUNDANCY PARAMETERS When redundancy is configured between two internal DS1
ASSYMETRIC ports, all their physical layer parameters must be identical
(including the Signaling Mode)
2120 Error PEER DOESN'T EXIST You have specified a peer index during the creation of a
pseudowire, but the peer has not yet been created.
2121 Error PEER NEEDS ROUTER It is not possible to configure peers before at least one
INTERFACE router interface has been configured.
2122 Error PW ASSIGNENT IS The same timeslot(s) of an internal DS1 port have been
DUPLICATED assigned to more than one pseudowire (this may happen
because you can assign timeslots either during the
configuration of the pseudowire service parameters, or
assign them using the internal DS1 port timeslot
assignment configuration screen).
Check and correct the timeslot assignment
2123 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).
See details given for sanity error 2103
2124 Error PEER NOT ATTACHED TO PW You have created a PEER without attaching it to any
pseudowire.
2125 Error SLOT/PORT OF R.IFACE IS You must specify a valid I/O slot and port number to the
NOT CONNECTED specified router interface
2126 Error WRONG FAR END TYPE When redundancy is configured between two internal DS1
ASSIGNED TO RDN CH ports, all their physical layer parameters must be identical
(including the Far End Type)
2127 Error PW FAR END TYPE PER SLOT When signaling is enabled on the internal DS1 port
IS NOT EQUAL attached to a pseudowire, the Far End Type for all the
pseudowires terminated on the corresponding
Megaplex-4100 must be a framed mode (either E1 or T1).
2128 Error FAR END TYPE MISMATCH FAR END TYPE of PW should match Internal DS1 Framing
INT-DS1 FRAMING as follows:
• E1, T1 ESF, T1 SF <-> Framed.
• Unframed <-> Unframed.

2118 Error PWS FROM DIFF SLOTS Pseudowires configured on different Megaplex-4100
DEMAND DIFF PEERS modules must be configured with different peers, even if
the destination address is the same (see also sanity error
2128).
Using different peer numbers will result in the creation of
different internal flows, each directed to the relevant
router interface
2129 Error CAN’T CARRY MIXED ETH & An Ethernet port on an I/O module cannot be a member
PW TRAFFIC of a flow that carries Ethernet traffic and at the same
time, be a member of another flow that carries
pseudowire traffic
2130 Warning TS NOT ASSIGNED TO ANY The specified Megaplex-4100 internal DS1 port is
PW connected to local module ports, but no pseudowire has
been assigned timeslots on the same port (the reverse
situation is detected by sanity error 2122).
You must specify timeslots to be connected to the
internal DS1 port

to
2199
OP-108C/OP-106C Sanity Messages

2200 Warning FAR-END TYPE CHANGED, The type of the connected FAR-END device is different
DEVICE WILL RESTART than the one configured. The module is going to perform
a reset.
2201 Error NOT IDENTICAL FAR-END When two far end devices are connected to the
OP-108C/OP-106C module, they should be identical.
DEVICE TYPE
2202 Error PORT ASSIGNED TO The Optical link Admin Status is set to Down, while a DS1
DISCONNECTED LINK or Ethernet port is set to UP. Set the optical link status to
UP.

6.3 Handling Alarms and Traps
Alarm Collection and Reporting
Alarm Buffer
The 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.
In case a problem is detected, the 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 256 alarm messages, together with their time stamps. The alarm
history buffer is organized as a FIFO queue, therefore after 256 alarms are
written into the buffer, new alarms overwrite the oldest alarms.
Alarm messages can also be automatically sent 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 the Megaplex-4100 is powered down, the alarm messages are erased, and
therefore 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 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 a bay alarm or remote
monitoring panel.
Customizing Alarm Handling (Alarm Configuration)

Use the following procedure to configure the alarms generated by the
Megaplex-4100, and the alarm handling, indications and reporting capabilities, in
accordance with your specific application requirements.
To navigate to the required screen, use Configuration>System>
Alarms Configuration.
Megaplex-4100 Ver. 2.0 Handling Alarms and Traps 6-95

A typical Alarms Configuration submenu, which serves as a task selection screen,

is shown in Figure 6-82. The tasks accessed via this submenu are explained in
Table 6-25.
MP-4100
Configuration>System>Alarms Configuration
1. Alarm Attributes []>

2. Alarm Report []>
3. Alarm Priority []>
6. Alarm Window >
7. Trap Masking >
>
-----------------------------------------------------------------------------
Figure 6-82. Typical Alarms Configuration Task Selection Submenu
Table 6-25. Alarms Configuration Submenu Tasks
Alarm Attributes Configure the alarm attribute: normal handling, versus masking or inversion
Alarm Report Configure the alarm reporting method and indications
Alarm Priority Define the alarm priority (severity) level
Init Alarm Priority Return alarm severities to the factory defaults
Init Alarm Report Return alarm report specifications to the factory defaults
Alarm Window Define observation windows for alarm filtering
Trap Masking Control the generation of traps in response to alarm conditions
³ To select a specific task:

1. Type the desired task number and then press <Enter> to display the
corresponding screen.
For Init Alarm Priority and Init Alarm Report, you are required to confirm. The
change takes effect only after confirming the action.
2. Perform the desired task.
3. When done, save the changes by pressing <Esc> to close the current screen
and return to the previous screen. At this stage, the changes are stored in
the Megaplex-4100 configuration files and take effect.
Selecting the Alarm Attributes

The alarm attributes can be used to modify the standard response in case an
alarm is detected in a specific slot or port. For example, you can temporarily or
6-96 Handling Alarms and Traps Megaplex-4100 Ver. 2.0

permanently mask an alarm to prevent it from being reporting, for example,

during maintenance or when a link is taken out of service for a long period.
Since the attributes are specific to a module and to its ports, they must be
configured on the programmed modules and thus are generally affected by the
active database. If there is a mismatch between the module programmed in a
slot, versus the module actually installed in that slot, Megaplex-4100 will not
report any alarm for the installed module. Moreover, when the module
programmed in a slot is changed, all the alarm attributes related to the replaced
module and its ports are automatically removed.
The attributes are stored in the Megaplex-4100 configuration files, and are not
associated with a specific database. This means that when changes to the
programmed modules occur as a result of a database change, and the associated
alarm attributes are deleted, restoring the original database does not restore the
associated alarm attributes, because they have been deleted from the
configuration files. The screen used to configure alarm attributes is Alarm
Attributes. The screen is divided into two sections: you can scroll to the right or
to the left to display the desired section. A typical screen is shown in Figure 6-83.
MP-4100
Configuration>System>Alarms Configuration>Alarm attributes
Alarm Id Slot Port Type Port Num Mask

1 None None None No
122 IO-3 Link Link 4 No
->>
>

-----------------------------------------------------------------------------
A. Lefthand Section of Screen

MP-4100
Invert Filter/Threshold Set Val Reset Val Alarm Description

No - 255 0
No - 70 35 RTS IS OFF
<<-
>

-----------------------------------------------------------------------------
B. Righthand Section of Screen

Figure 6-83. Alarm Attributes Screen (Factory Defaults)
The screen includes a table with the following columns:
Alarm Id The index number of the alarm in the Megaplex-4100. See

Chapter 5.
Slot The Megaplex-4100 slot for which the attribute to be defined
will effect the alarm appearing in the same row.
Port Type The type of the port in the selected Slot, relevant for modules
with several types of ports.
Port Num The number (within the range of the selected ports type) of
port in the selected Slot for which the attribute to be defined
will affect the alarm appearing in the same row.
You can define different attributes for the same alarm, where
each attribute is associated with a specific slot, and where
applicable with a specific port on that slot.
Mask Indicates whether the corresponding alarm is currently masked

permanently (Permanent), temporarily (Temporary) or not
masked (No).
Invert Indicates whether the corresponding alarm is currently inverted

(Yes) or not (No).
Filter/Threshold Indicates whether filtering applies to the corresponding

attribute:
No – means that no filtering is used.
Filter – filtering is used. The filtering parameters are then

displayed in the following columns.
Set Val The set threshold value.

Reset Val The reset threshold value.
Alarm Description The alarm string associated with the selected Alarm Id.
Note
To see the navigation keys available for this screen, type ? (help).
³ To add an attribute:
1. Type a to display the Alarm Attribute screen. A typical Alarm Attribute screen
with default values is shown in Figure 6-84.
MP-4100
Set Val[1 - 100] ... (0)
Reset Val[1 - 100] ... (0)
Alarm Description ... ()
1. Alarm Id[1 - 2073] ... (0)
2. Slot > (None)
3. Port Type > (None)
4. Port Num > (None)
5. Mask > (No)
6. Invert > (No)
7. Filter/Threshold > (No)
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 6-84. Typical Alarm Attributes Configuration Screen

2. Use Alarm Id to select the desired alarm. The corresponding alarm description
appears in the Alarm Description field. If you need a description of the
various alarms, refer to Chapter 5.
3. Select Slot to open the slot selection screen, and then select the slot for
which the attribute will be in effect Make sure to select only slots for which
modules have already been programmed..
4. Select Port Type to open the port type selection screen for the selected Slot,
and then select the desired type of ports. The displayed options depend on
the module programmed in the selected slot.
5. Select Port Num to open the port selection screen (only ports of the selected
Port Type will be displayed), and then select a specific port for which the
attribute will be in effect. Make sure to select a configured port with Admin
Status=UP.
Note You need to define separately the attribute for each required port, even when
the attribute applies to the same alarm.
6. Select Mask to open the masking attribute selection screen. You can change
the masking attribute by typing the item number for the new attribute, and

then pressing <Enter>. To cancel the permanent masking of an alarm, select

the Normal attribute.
The meaning of the various masking attributes is as follows:
Normal The alarms are generated in accordance with the conditions

defined in Chapter 5, and reported in accordance with the
selections made using the Alarm Report screen.
Selecting Normal for an alarm effectively deletes any special
masking attribute defined for this alarm.
Temporary The alarm is temporarily masked, and therefore if the

Megaplex-4100 is reset or is turned off and then back on, the
masking is automatically canceled.
A masked alarm does not effect the Megaplex-4100 alarm
status. As a result, the various alarm indicators of the
Megaplex-4100 will not turn on as a result of a masked alarm,
and the generation of the corresponding trap is disabled.
Masking an alarm cancels the Invert attribute, if currently
defined for this alarm.
Permanent The alarm is permanently masked: the masking information is

stored in the non-volatile memory, and therefore masking is
still active after the Megaplex-4100 is reset, or is turned off
and then back on.
7. Select Invert to open the inversion attribute selection screen: you can select
between No and Yes.
Note It is not possible to invert event alarms, but only state alarms. A state alarm is an
alarm that is in the ON state while a certain condition is present, and
automatically changes to OFF when the condition is no longer present. This type
of alarm cannot be cleared (removed from the alarm buffer) while it is in the ON
state.
Selecting Yes for an alarm cancels the masking attribute, if currently defined for
this alarm.
The meaning of the inversion attributes is as follows:
No Normal interpretation of the alarm condition: an alarm is

interpreted as being active when the associated condition, is
present (true).
Yes The interpretation of a selected alarm condition is inverted

with respect to Megaplex-4100 visual indicators and alarm
relays.
When the alarm is inverted, the normal condition is the
presence of an alarm condition, and the condition that
requires alerting is the absence of the alarm state.
For example, when an E1 port is temporarily out of service, the
alarm indication related to loss-of-signal on the corresponding
port can be inverted. As a result, the general Megaplex-4100
alarm indicators and the port indicator on the E1 module will

be turned off as long as the loss-of-signal condition is present,

and will turn on when the port returns to normal operation.
The same is true with respect to the alarm relays: if one of the
alarm relays is to be activated by that alarm, then inverting the
alarm returns the alarm relay to its non-alarm state while the
alarm state is present.
Alarm inversion does not effect the state of the alarm
recorded in the Megaplex-4100 alarm buffer (the alarm buffer
shows the true state).
Note
When alarms are displayed, masked alarms are identified by an M appearing at
the righthand side of the alarm line, and inverted alarms are identified by an I.
8. Select Filter/Threshold to open the filtering control screen. The screen

No No filtering is used.
Yes Filtering is enabled. This option appears only when the

selected alarm is a state alarm.
The purpose of filtering is to reduce the number of alarms
generated under marginal conditions, when the alarm changes
state often. For this purpose, the system monitors the alarm
state during a fixed time window, defined by means of the
Alarm Window screen:
• If the alarm is active for a specified fraction of the
observation window (the set threshold), the alarm is
declared active, and is reported.
• To cancel the alarm condition, it must be found active for a
smaller fraction of the observation window (the reset
threshold).
Threshold Enable the use of threshold values. This option appears only
when the selected alarm is an event alarm.
Note
An event alarm is an alarm that records the occurrence of an event. This type of
alarm can be cleared at any time.
The threshold values are used in conjunction with the filtering

window defined by means of the Alarm Window screen to
determine when to generate an alert because the frequency of
the specified events is too high. Alerts generated when the
specified threshold is exceeded cannot be masked, even in
case the monitored event is masked.
A separately defined threshold is used to cancel the alert
when the frequency of the monitored events decreases below
that threshold.
• For event alarms, select threshold values:

Set Val The minimum number of times the specified alarm must
occur during the observation window for the alarm to be
declared active. The allowed range is 0 through 100.
Reset Val The maximum number of times the specified alarm must
occur during the observation window for the alarm to be
declared inactive. The allowed range is 0 through 100, but
the number entered in this field must be less than the
number entered as the set threshold.
• For state alarms, select filtering values:
Set Val The minimum percentage of the observation window

during which the alarm must remain in the active state to
be declared as active. The allowed range is 0 through 100.
Reset Val The maximum percentage of the observation window

during which the alarm may remain in the active state to
be declared as inactive. The allowed range is 0 through
100, but the number entered in this field must be less
than the number entered as the set threshold.
9. After configuring the desired values, the alarm attribute configuration is

ended. A typical screen is shown in Figure 6-85.
MP-4100
Alarm Description ... (RTS IS OFF )

1. Alarm Id[1 - 2073] ... (122)
2. Slot > (IO-3 (M8T1))
3. Port Type > (Link)
4. Port Num > (Link 1)
5. Mask > (Temporary)
6. Invert > (No)
7. Filter/Threshold > (Yes)
8. Set Val[1 - 100] ... (75)
9. Reset Val[1 - 100] ... (50)
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 6-85. Typical Alarm Attributes Screen (After Parameter Selection)

10. After configuring the desired values, select S – Save. After pressing <ESC>,
the new attribute definition appears in the table of the Alarm Attributes
screen (Figure 6-83).
11. Repeat the process to configure all the required attributes for all the ports.

Selecting the Alarm Reporting Method

Megaplex-4100 has a factory default set of reporting rules for alarms. You can
change this set, and define different alarm reporting method and indications for
each alarm severity (priority) level using the Alarm Report screen.
A typical Alarm Report screen is shown in Figure 6-86. The screen has two pages:
use the arrow keys to scroll between screen pages.
The Alarm Report screen includes a list of the alarm severities, and six columns
which are used to select the action to be taken for each alarm severity and state
(ON or OFF). The fields appearing on the screen are explained below.
Alarm The alarm state.
Report YES indicates that the corresponding alarm state is reported by

means of messages sent to the supervisory terminal, and traps
sent to management stations.
Log YES indicates that the corresponding alarm state is recorded in

the alarm buffer.
Relay-1 YES indicates that the alarm relay 1 is activated when the
corresponding state occurs.
Default: relay 1 is activated for major and critical alarm levels.
Relay-2 YES indicates that the alarm relay 2 is activated when the
Default: relay 2 is activated for minor and higher alarm levels.
Minor LED YES indicates that the ALARM indicator lights steadily when the
Major LED YES indicates that the ALARM indicator flashes when the
corresponding condition occurs.

MP-4100
Configuration>System>Alarms Configuration>Alarm report
Alarm Report Log Relay-1 Relay-2 Minor Led Major Led

Critical on Yes Yes Yes Yes Yes Yes
Critical off Yes Yes - - - -
| Major on Yes Yes Yes Yes Yes Yes
v Major off Yes Yes - - - -
Minor on Yes Yes No Yes Yes No
Minor off Yes Yes - - - -
1. No
2. Yes
>

-----------------------------------------------------------------------------
A. Page 1 of Typical Screen

MP-4100
Configuration>System>Alarms Configuration>Alarm report
^ Alarm Report Log Relay-1 Relay-2 Minor Led Major Led

| Major off Yes Yes - - - -
Minor on Yes Yes No Yes Yes No
Minor off Yes Yes - - - -
Warning on Yes Yes No No Yes No
Warning off Yes Yes - - - -
Event Yes Yes No No Yes No
1. No
2. Yes
>

-----------------------------------------------------------------------------
B. Page 2 of Typical Screen

Figure 6-86. Typical Alarm Report Screen
³ To change an alarm reporting or indication selection:

1. Move the cursor to the desired location.
2. Select No or Yes to change the selected location.
To ensure consistent display and reporting of alarm conditions, pay attention to
the following points:
• For any alarm function, once it is set to YES at a certain alarm level, it needs
to be set to YES for all the alarm levels above it. For example, if the Minor
LED is set to be YES for minor alarms, it will also be activated for major and
critical alarms.

• For any alarm condition, once it is set to NO at a certain alarm level, it needs
to be set to NO for all the lower alarm levels. For example, if the Major LED is
set to be activated for major alarms, must also be deactivated for minor,
warning and event alarms.
• Report and Log functions can also be independently set when a particular
alarm condition ceases (for example, for Minor off). In this case, all the OFF
alarm conditions above that level must also be set to YES.
• Relays and LEDs cannot be activated for alarm OFF conditions, and therefore
N/A appears in the rows corresponding to the end-of-alarm conditions.
Changing the Alarm Priority

Megaplex-4100 supports four alarm severity levels (priorities): warning (lowest
level), minor, major, and critical (highest level).
You can change the factory default priority levels for the desired alarms by means
of the Alarm Priority screen.
A typical Alarm Priority display screen is shown in Figure 6-87. The screen shows
the list of alarms whose default priorities have been changed.
MP-4100
Configuration>System>Alarms Configuration>Alarm Priority
Alarm Id Alarm Description Alarm Priority

1 MINOR
10 CLK CHANGED TO MASTER CLK CRITICAL
14 AGENT WITH SAME NAME IN NET MAJOR
36 SOFTWARE LOADING STARTED MINOR
69 MAJOR
70 MAJOR
>

-----------------------------------------------------------------------------
Figure 6-87. Typical Alarm Priority Display Screen
³ To change the priority (severity) of an alarm:

3. Select Add (type a) to display the alarm modification screen.
4. On the alarm modification screen, select Alarm Id, type the number of the
desired alarm, and then press <Enter>. The corresponding alarm string
appears in the Alarm Description field, and the current priority of the alarm
appears in the Alarm Priority field. A typical screen is shown in Figure 6-88.
Note For an explanation of the alarm meaning, refer to Chapter 5.

MP-4100
Configuration>System>Alarms Configuration>Alarm priority
1. Alarm Id[1 - 2073] ... (212)

Alarm Description ... (LOSS OF SIGNAL ERR)
2. Alarm Priority > (MAJOR)
>
#-Db Undo; S-Save

-----------------------------------------------------------------------------
Figure 6-88. Typical Alarm Priority Modification Screen

5. To change the current priority, select Alarm Priority, and then press <Enter>
to display the alarm priority selection screen. A typical screen is shown in
Figure 6-89.
MP-4100
Configuration>System>Alarms Configuration>Alarm Priority
1. WARNING
2. MINOR
3. MAJOR
4. CRITICAL
>

-----------------------------------------------------------------------------
Figure 6-89. Typical Alarm Priority Selection Screen

6. The selection screen offers four options: Warning, Minor, Major, and Critical.
Select the desired severity, and then press <Enter>.
7. The updated alarm display appears in the alarm priority display screen.
8. You can repeat Steps 1 to 4 for other alarms, as required.
Selecting the Threshold Alarms Window

Megaplex-4100 uses the alarm Set and Reset values defined by means of the
Alarm Attribute Threshold screen, in conjunction with the observation window
defined by means of the Alarm Threshold Window screen.
A typical Alarm Threshold Window screen is shown in Figure 6-90.

³ To select the observation window:

1. Select Alarm Window and then enter the desired window duration, in the
range of 1 to 255 seconds.
2. When done, press <Enter>.
3. Type % to save and update the database.
MP-4100
Configuration>System>Alarms Configuration>Alarm Window
1. Time Window Value (sec)[1 - 255]... (20)
>

-----------------------------------------------------------------------------
Figure 6-90. Typical Alarm Threshold Screen
Configuring Trap Masking

The Trap Masking screen is used to control the generation of traps in response to
alarm conditions.
The user can enable or disable the sending of all the traps to the selected
managers, or can select specific alarms. A typical Trap Masking screen is shown in
Figure 6-91.
MP-4100
Configuration>System>Alarms Configuration>Trap Masking
Description... (ACTIVE DB HAS BEEN UPDATED )

1. Alarm ID[1 ... (3)
2. Trap Send (Yes)
3. Enable All
4. Disable All
>
%-Db Update; #-Db Undo; $-Sanity; F-Fwd; B-Bkwd

-----------------------------------------------------------------------------
Figure 6-91. Typical Trap Masking Screen

³ To configure trap sending for individual alarms:

1. Select Alarm ID and then enter the desired alarm number: after pressing
<Enter>, the alarm string is displayed in the Description field, and the current
state (Yes or No) is displayed in the Trap Send field.
2. To change the state, select Trap Send and then press <Enter>.
³ To configure trap sending for all the alarms:

1. After displaying the Trap Masking screen, select the desired state: Enable All
or Disable All and then press <Enter>
2. The state displayed in the Trap Send field for the currently selected alarm
changes accordingly.
Note If necessary, change now the state of individual alarms as explained above.
Displaying Alarms
³ To select the type of alarms to be displayed:
1. Open the Monitoring>System submenu and then select one of the following
options:
1. To display active alarms, select one of the following:
Active Alarms (ON) – for displaying the currently active (ON) state
alarms.
Active Alarms (ALL) – for displaying all the alarms, including events.
2. To display the alarm history (log), select History Alarms.
For additional details on the available selections and detailed instructions,
refer to Handling Alarms and Traps.
2. You will see the corresponding screen. For example, Figure 6-92 shows a
typical Active Alarms (ALL) submenu. This submenu is used to select (filter)
the alarms to be displayed:
1. To see all the alarms, use All Alarms.
2. To filter the alarms list, select System Alarms or Slot Alarms.
Where applicable, the highest severity level of the alarms included in the
corresponding category is listed in brackets next to each option.

MP-4100
Monitoring>System>Active Alarms (ALL)
1. All Alarms (MAJOR) []>

2. System Alarms (EVENT) []>
3. Slot Alarms >
>

-----------------------------------------------------------------------------
Figure 6-92. Typical Monitoring Active Alarms (ALL) Submenu

3. Type the number of the desired display option, and then press <Enter>.
Interpreting Alarm Messages

Table 6-26 lists the alarm messages generated by the Megaplex-4100 and
explains their interpretation. The alarm messages are listed in ascending order of
their codes.
For each alarm, Table 6-26 also specifies the type (system, slot (SL), CL, or
channel (CH)), and lists the default severity (called priority in the supervision
terminal screens) for state alarms. The severity level can be modified in
accordance with the specific customer’s requirements using the
Configuration>System>
Alarms Configuration screen.
Note A state alarm is an alarm that is in the ON state while a certain condition is
present, and automatically changes to OFF when the condition is no longer
present. This type of alarm cannot be cleared (removed from the alarm buffer)
while it is in the ON state.
An event alarm is an alarm that records the occurrence of an event. This type of
alarm can be cleared at any time.
Table 6-26. Alarms List
Default
Code Message Type Interpretation
Severity
System Alarms
000 to Reserved N/A N/A N/A

002
003 ACTIVE DB HAS BEEN System Event The active database of the Megaplex-4100 has been changed
UPDATED (appears after executing a DB Update command)

Default
Severity
004 LOSS OF ALMS FROM System Event More than 256 alarms have occurred since the Megaplex-4100
HISTORY BUFFER alarm buffer was last read.
The alarm buffer of the Megaplex-4100 has been filled up and
the new alarms are overwriting the oldest alarms (the first
alarms stored in the alarm buffer)
005 NO MEM LEFT TO TRACE System Major No additional memory space can be allocated for tracing new
NEW ALMS alarms in the Megaplex-4100. New alarms will be lost
006 Reserved N/A N/A N/A
007 CL-A & CL-B HAVE DIFF System Major Different software versions are stored by the two CL modules
SW/HW installed in the Megaplex-4100. Ignore this message if it
appears during the downloading of a new software version
009 CLK IS DIFF FROM System Major The Megaplex-4100 has switched to the fallback clock source,
MASTER CLK or to the internal oscillator. This indicates a major failure in
the source which provided the master clock source
010 CLK CHANGED TO

MASTER CLK
011 CLK CHANGED TO
System Event The clock source has been changed to the specified source
FALLBACK CLK
012 CLK CHANGED TO
INTERNAL CLK
013 AGENT WITH SAME IP IN SL (CL) Major Another RAD IP entity in the network uses the IP address
NET configured on the Megaplex-4100 SNMP agent. Check and
correct the IP address
014 AGENT WITH SAME NAME SL (CL) Minor Another IP entity in the network used for SNMP management
IN NET uses the logical name configured on the SNMP agent of the
Megaplex-4100. Check and correct the logical name

017
018 DB UPDATE OCCURRED System Event Megaplex-4100 stores the edited database in the non-volatile
memory (appears after executing a DB Update command).
The writing to the non-volatile memory take time, thus a
Configuration File Update Is In Process message is displayed
until the process is finished
General Module Alarms
020 INTERNAL MESSAGE SL Event The module reports an internal RAD message used for
software tracing. Report the internal error number to RAD
technical support personnel
021 MODULE WAS REMOVED SL Event A module has been removed from the specified slot

Default
Severity
022 MODULE WAS INSERTED SL Event A module has been inserted in the specified slot
023 RESET OCCURRED SL Event The module installed in the specified slot has been reset
automatically
024 HARDWARE/INIT FAILURE SL Major An error has been detected during the power-up self-test
and/or during the module initialization process. In case the
alarm remains in the ON state, remove the module, and then
reinsert it in its slot. If problem recurs, replace the module
025 NOT PROGRAMMED SL Minor The module identified by the CL module as being installed in
MODULE the specified slot is not programmed in the active database
026 MODULE TYPE MISMATCH SL Major The module identified by the CL module as being installed in
the specified slot is not of the type programmed in the active
database
028 HARDWARE/SOFTWARE SL:CH Major The meaning of this alarm depends on the module type, as
MISMATCH explained below:
HSU-6, You cannot enable RLB or LLB when using V.110

HSU-12 rate adaptation.
It is not allowed to select 56 kbps or 128 kbps in
the synchronous mode.
HS-RN 1. You are trying to configure a HS-R module for

using all the four TDM buses in the chassis, but
this capability is supported only by HS-RN
modules (that is, module hardware version 6 and
higher).
2. You are trying to configure a HS-RN module for
operation at 48 kbps, but this capability is
supported only by HS-R modules (that is, module
hardware version 5 or lower).
3. You are trying to configure a HS-R or
HS-RN/V.110 module for operation at 7.2, 14.4,
or 28.8 kbps, but this capability is supported
only by HS-RN modules (that is, module
hardware version 6 and higher).
operation at Encapsulation mode=Latency
Optimized in an HS-RN/V.110 module.
operation at Encapsulation mode=Latency
Optimized, but this capability is supported only
by HS-RN modules with SW version higher than
50.

Default
Severity
LS-12N, 1. In the synchronous mode, it is not allowed to

LS-6N select the DCE mode when the port hardware
interface is DTE.
2. In the synchronous mode, it is not allowed to
select the DTE mode when the port hardware
interface is DCE.
3. The hardware version of the module does not
support the selection of a 14.4 kbps rate. This
option is supported only by hardware versions
higher than 6
028 VC-4, 1. You are trying to enable signaling, but the

(Cont.) VC-8, hardware version of the module does not support
VC-16 metering pulses and reverse polarity signaling.
2. The hardware version of a module with FXS or
FXO interface does not support metering pulses
and reverse polarity signaling, and you select the
WINK START mode.
3. You are trying to select ADPCM on a module does
not include the additional hardware needed to
support ADPCM.
4. You are trying to select ADVANCED signaling
services for a module whose software version
does not support this feature. This option is
supported only by software versions higher than 4.
Contact RAD Technical Support Department for
information on software upgrades.
HS-12N, The module hardware or software revisions are not

HS-6N suitable for use in the Megaplex-4100 system. The
hardware revision must be 2 or higher, and the
software revision must be 6 or higher
029 NOT SUPPORTED SL Major The module software version is not supported by the CL
SOFTWARE VER software
031 COMMUNICATION SL Event The CL module reported a temporary failure in the

FAILURE communication with I/O modules
033 MANAGEMENT LINK IS SL:CH Major The CL module cannot establish IP communication with the
DOWN remote end. This may indicate incorrect set-up of the
management port communication parameters, a
disconnection along the communication path, or a hardware
failure
034 NOT SUPPORTED SL Major The module hardware version is not supported by the CL
HARDWARE VER software

Default
Severity
035 ALARMS EXIST IN SL Major Notification message sent to RADview network management
MODULES’ PORTS station that alarms are present for one or more of the module
channels
036 SOFTWARE LOADING SL Event Informative message – indicates that software downloading
STARTED using TFTP has been started
037 SOFTWARE LOADING SL Event Informative message – indicates that software downloading
COMPLETED has been successfully completed
038 ABORT SOFTWARE SL Event Informative message – indicates that software downloading
LOADING has been stopped before its successful completion
Power Supply Alarms
040 MAIN VOLTAGE FAIL SL (PS) Major The +5V or +3V voltage is missing. Turn the
Megaplex-4100 off and then on again. If problem recurs,
replace the power supply unit
041 -5V POWER SUPPLY SL (PS) Major The -5V voltage is missing. Turn the Megaplex-4100 off and
FAILURE then on again. If problem recurs, replace the power supply
unit
042 12V POWER SUPPLY SL (PS) Major The 12V voltage is missing. Turn the Megaplex-4100 off and
FAILURE then on again. If problem recurs, replace the power supply
unit
043 POWER SUPPLY’S FAN SL (PS) Major The internal cooling fan of the power supply failed. Replace
FAILURE the module as soon as possible (you can always replace the
module when another PS module is installed in the chassis)
044 to Reserved for future use N/A N/A N/A

049
Additional SNMP Agent Alarms
050 CL FLIP OCCURRED System Event Megaplex-4100 has switched to the other CL module
051 Reserved for future use N/A N/A N/A

054
055 DBS UPDATED BY TFTP System Event Informative message – indicates that after the downloading
of all the databases is successfully completed, all the
databases have been automatically updated
056, Reserved N/A N/A N/A

057
058, Reserved for future use N/A N/A N/A

059

Default
Severity
CL Module Alarms
060 DEFAULT DB LOADED ON SL (CL) Event During the power-up self-test it was found that the
STARTUP Megaplex-4100 database is missing or corrupted. The
factory-default parameters have been loaded in the database
062 DIFF DB CKSUM BETWEEN System Major The checksums calculated by the system for the contents of
CL'S the databases stored in the CL modules installed in the
Megaplex-4100 chassis are different. Either database may be
correct

064
065 SAVE LAST DB FAIL SL (CL) Event The new or modified database could not be saved (written) to
the non-volatile memory of the CL module.
066 CONFIGURATION FILE M SL (CL) Major The remaining capacity of the CL non-volatile memory is low,
ALMOST FULL and may not enable proper operation
067 COPY DB TO RDN CL IN SL (CL) Minor The database of the active CL module is being copied to the
PROCESS slave CL module (relevant only when the Megaplex-4100
chassis includes two CL modules, for redundancy)
068 COPY DB TO RDN CL SL (CL) Event The database of the active CL module has been successfully
COMPLETED transferred to the slave CL module (relevant only when the
Megaplex-4100 chassis includes two CL modules, for
redundancy)

079
Link Alarms
080 T1/E1 FRAME SLIP HAS SL:CH Event A link frame slip has occurred. This is usually caused by
OCCURRED incorrect selection of clock sources
081 BPV ERROR HAS SL:CH Event A bipolar violation error has been detected on the link
OCCURRED
082 EXCESSIVE BIPOLAR SL:CH Major The number of coding errors detected in the link signal
VIOLATION received by the active module port is too high (the bipolar
violation rate exceeds 1×10-6 for 1000 consecutive seconds).
This may indicate a fault in the link or in the link transmission
equipment, or a failure in the active module port. This
message is not available when the T1 link operates with ESF
framing
083 EXCESSIVE ERROR RATIO SL:CH Major The error rate detected on the frame synchronization bits is
high as defined by ITU-T Rec. G.732. This may indicate
hardware problems or defective connections (appears only
when an E1 link is used)

Default
Severity
085 AIS RED ALARM SL:CH Major The local frame synchronization has been lost because of AIS
reception
086 LOC SYNC LOSS SL:CH Major Local module port lost synchronization to incoming data
stream. May indicate a configuration error or a technical
failure. For T1 links, this condition is the red alarm
087 REM SYNC LOSS SL:CH Major Remote module port lost synchronization to the incoming
data stream. May indicate a configuration error or a technical
failure. For T1 links, this condition is the yellow alarm
088 E1 MULTIFRAME LOCAL SL:CH Minor On an E1 link operating with G732S framing, the
SYNC LOSS corresponding local module port has lost multiframe
synchronization
089 E1 MULTIFRAME REMOTE SL:CH Minor On an E1 link operating with G732S framing, the
SYNC LOSS corresponding remote module port has lost multiframe
synchronization
090 LOST SIGNAL ON E1/T1 SL:CH Major The corresponding module port does not receive the link
MODULE signal
091 T1/E1 DRIVER FAILURE SL Major Hardware failure on the corresponding module port (defective
transmit line driver)
092 NETWORK LLB SL:CH Minor A network-initiated line loopback has been activated on the
corresponding module port. This loopback cannot be
disconnected by the system management.
This message may appear only for T1 links
093 NETWORK PLB SL:CH Minor A network-initiated payload loopback has been activated. This
loopback cannot be disconnected by the system management.
This message may appear only when using a T1 link with ESF
framing
094 CRC ERROR SL:CH Event The corresponding module port reports the detection of a CRC
error.
This message may appear only for E1 links using the CRC-4
option
095 AIS WAS DETECTED SL:CH Major The Alarm Indication Signal (AIS), a framed “all ones”
sequence, is received on the corresponding port

100
101 REDUNDANCY FLIP SL:CH Event A switch to the other port has been performed by the
OCCURRED redundancy function (applicable only for dual-link redundant
configurations)

107

Default
Severity
108 RING CLOCK FAILURE SL:CH Major An E1 or T1 port participating in a ring topology lost its clock
reference. This alarm is reported when a port whose receive
clock has been configured as nodal clock source loses its
receive signal

110
111 RING CONNECTION SL:CH Major East-West mismatch indication in physical connections of
MISMATCH primary or secondary ports of an E1 or T1 ring: the primary
port of each ring node must be connected to the secondary
port of the adjacent ring node

119
High-Speed Data Module Alarms
120 FIFO BUFFER OVERFLOW/ SL:CH Event The FIFO buffer of the specified HS-12 module channel
UNDERFLOW overflowed or underflowed. If the event recurs, it is usually
caused by incorrect selection of the timing mode on the
module channels and/or user's equipment, or by technical
problems (unstable clock) in the timing circuits of the user's
equipment.
This message can appear only when the channel RTS line is
active
121 INTERNAL RATE SL:CH Major The internal baud rate generator of the specified channel
GENERATOR FAIL failed. The module must be repaired
122 RTS IS OFF SL:CH Minor The RTS line (or the CI line for a channel with X.21 interface)
is off
124 CARD/INTERFACE SL Major The selected interface type is not supported by the specified
MISMATCH HS-12 module
125 ILLEGAL LINK RATE FOR SL:CH Major When the interface is RS-232, only the 64 kbps rate can be
RS232 selected

139

144

159
Voice Module Alarms
160 COMBO FAILURE ERROR SL:CH Major The COMBO of the specified voice channel failed. This state is
often reported because of a transient fault. If the fault state
persists, the module must be repaired as soon as possible

Default
Severity

163
164 RINGER VOLTAGE NOT SL Major The voice module reports that it does not receive the voltage
SUPPLIED needed to generate the ring voltage

166
167 ADPCM SYNC LOSS SL Major The ADPCM codec has lost synchronization. If the problem
persists after module is reset, replace the module

179

184

199

209
Module HS-RN Alarms
211 SYNC LOSS SL:CH Major The specified channel reports loss of input signal or loss of
synchronization
212 LOSS OF SIGNAL ERR SL:CH Major Loss of input signal or loss of synchronization at the specified
port
213 FIFO BUFFER SL:CH Event The FIFO of the specified port has overflowed/underflowed
OVERFLOW/UNDERFLOW

219

223

229

233

239

241

Default
Severity

249
HS-703 Module Alarms
250 SIGNAL LOSS SL:CH Major The input signal of the specified HS-703 channel is missing
251 LOC SYNC LOSS SL:CH Major Loss of synchronization to the received data on the specified
HS-703 channel
252 BIPOLAR VIOLATION SL:CH Major The octet timing of the specified HS-703 channel (carried by
ERROR bipolar violations) has been lost

255

257

259

263

265

267

274

287

289
LS-12/LS-6N Module Alarms
290 LOC SYNC LOSS SL:CH Major The specified internal port lost synchronization to incoming
data stream
291 REM SYNC LOSS SL:CH Major The specified internal port of the remote module reports loss
of synchronization
292 BUFFER OVERFLOW SL:CH Event An overflow/underflow event has occurred in the buffer of the
specified channel. If the event recurs, it is usually caused by
incorrect selection of the timing mode and/or user's
equipment, or by technical problems (unstable clock) in the
timing circuits of the external equipment

Default
Severity
294 INTERNAL RATE SL:CH Major The internal rate generator of the corresponding internal port
GENERATOR FAIL failed. If the message persists, the module must be repaired

300

309

379
HSU-6/HSU-12 Module Alarms
380 COMPLETE LOOPBACK ON SL:CH Minor Loopbacks have been activated on all the channels (B1, B2,
B1 B2 D and D) of the specified ISDN port
381 LOOPBACK ON B1 SL:CH Minor A loopback has been activated on the B1 channel of the
specified ISDN port
382 LOOPBACK ON B2 SL:CH Minor A loopback has been activated on the B2 channel of the
specified ISDN port
383 PRIMARY POWER SUPPLY SL:CH Major The power supply installed in the PS-A slot has failed
FAILURE
384 SECONDARY POWER SL:CH Major The power supply installed in the PS-B slot has failed
SUPPLY FAILURE
385 NT DEVICE UNDER TEST SL:CH Major A test has been activated on the NT or NT1 device connected
to the specified ISDN port
386 ASMi-31A CONFIG SL:CH Major The ASMi-31 unit connected to the specified HSU-6/HSU-12
MISMATCH port uses an incompatible configuration
387 ASMi-31B NVRAM FAILED SL:CH Major The non-volatile memory of the ASMi-31 unit connected to
the specified HSU-6/HSU-12 port has failed
388 ASMi-31C NO INTERFACE SL:CH Major No interface module is installed in the ASMi-31 unit connected
to the specified HSU-6/HSU-12 port
390 ASMi-31 ILLEGAL CLOCK SL:CH Major The clock source selected for the ASMi-31 unit connected to
SOURCE the specified HSU-6/HSU-12 port is not valid for the current
operation mode
391 ASMI-31 LLB INITIATED SL:CH Minor A local loop has been activated by the corresponding HSU-12
BY DTE module port, in response to a request from ASMi-31 (applied
through the LLB pin in the ASMi-31 user’s connector)
393 ASMI-31 RTS OFF SL:CH Minor A remote loop has been activated by the corresponding
HSU-12 module port, in response to a request from ASMi-31
(applied through the RLB pin in the ASMi-31 user’s connector)

Default
Severity

399

402

410

529
Additional HSU-6, HSU-12 Module Alarms – Full Duplex Support
530 NT DEVICE UNDER TEST SL:CH Minor The NT device reports a test condition (indication provided
only by a port configured for the /I mode)
531 ASMi-31 NO INTERFACE SL:CH Major The ASMi-31 connected to the corresponding port reports
that it does not include the user’s interface board (this
indication is generated only when the port is configured for
operation in the synchronous mode)
532 ASMi-31 LLB INITIATED SL:CH Minor The ASMi-31 connected to the corresponding port reports
BY DTE that a local loopback has been activated in response to the
control signal received from the user’s equipment via the LLB
pin in the user’s interface connector
533 ASMi-31 RLB INITIATED SL:CH Minor A local loopback has been activated on the corresponding
BY DTE module port in response to a command sent by the ASMi-31
(this command is sent when the user’s equipment activates
the RLB pin in the user’s interface connector)
534 ASMi-31 RTS OFF SL:CH Minor The user’s equipment connected to the ASMi-31 dropped the
RTS line
535 EXTERNAL UNIT SL:CH Minor HSU modules: The modem connected to a port configured for
MISMATCH the /1 mode is not the modem type configured by the user
OP-108C/OP106C modules: The remote device connected to
the port is not of the type configured by the user

539

543

549

564

569

Default
Severity

571

579

595

599

616

619

627
628 LOSS OF RX CLK The module is configured to use the EXT-DCE or DTE timing
mode, but no receive clock exists

644
M8SL and ASMi-54C Modules – SHDSL Alarms
645 SHDSL LOOP SL:CH Minor Loop attenuation has exceeded the alarm threshold
ATTENUATION ERROR
646 SHDSL SNR MARGIN SL:CH Minor Signal-to-noise margin has exceeded the alarm threshold
ERROR
647 SHDSL LOSW FAILURE SL:CH Minor Loss of SHDSL Sync Word is detected
648 SHDSL PSD NOT SL:CH Minor Mismatch between PSD mode selected by the user and PSD
COMPATIBLE mode used by the line
649 SHDSL CRC6 EXCESSIVE SL:CH Minor Excessive CRC-6 errors have been detected on the SHDSL line
ERROR
650 SHDSL WIRE MODE NOT SL:CH Major Mismatch between line interface types (2-wire versus 4-wire)
COMP between local and remote units
651 SHDSL CRC6 ERROR SL:CH Event CRC errors are detected
652 SHDSL SYNC LOSS SL:CH Major SHDSL line is not synchronized
653 SHDSL NO MANAGEMENT SL:CH Major The management link between local and remote units is down
654 SHDSL PROPRIETARY SL:CH Major The SHDSL inband proprietary protocol management channel
PROT FAILED (eoc) is not operational
655 TEST ACTIVE BY REMOTE SL:CH Minor A test has been activated on the specified SHDSL line by the
UNIT remote unit

Default
Severity
656 REM LOSS OF SIGNAL SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports loss of signal on E1 port
657 REM BPV ERROR SL:CH Event The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports bipolar violation error
658 REM FRAME SLIP SL:CH Event The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports frame slip
659 REM EXCESSIVE BPV SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports high rate of bipolar violation errors
660 REM EXCESSIVE ERROR SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports excessive bit error rate higher than 10-3
661 REM AIS OCCURRED SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports reception of AIS
662 REM CRC4 ERROR SL:CH Event The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports CRC-4 error event
663 REM AIS SYNC LOSS SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports AIS and loss of frame alignment
664 REM SYNC LOSS SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports loss of frame alignment to the user’s E1
signal
665 REM REMOTE SYNC LOSS SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
SHDSL port reports remote loss of frame alignment to the
user’s E1 signal
666 REM SHDSL LOSW SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
FAILURE port reports that Loss of Sync Word is detected
667 REM CRC6 ERROR SL:CH Event The remote ASMi-52 unit connected to the specified SHDSL
port reports an SHDSL CRC error event
668 REM SHDSL SNR MARGIN SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
ERROR port reports that the signal-to-noise margin has exceeded the
alarm threshold.
669 REM SHDSL LOOP SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
ATTENUATION ERROR port reports that the loop attenuation has exceeded the alarm
threshold
670 REM LLB FROM DTE SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports the reception of a local loopback request from
the user’s equipment
671 REM RLB FROM DTE SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports the reception of a remote loopback request from
the user’s equipment
672 REM LAN NOT SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
CONNECTED port reports that no LAN is connected to its Ethernet port

Default
Severity
673 REM DATA LINE RATE SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
MISMATCH port reports that its data rate does not match the number of
timeslots open on the port to which it is connected
674 REM CONFIG CHANGED SL:CH Event The remote ASMi-52 unit connected to the specified SHDSL
port reports a change of configuration
675 REM ILLEGAL EXT CLOCK SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports incorrect selection of its nodal clock source
676 REM SELF TEST ERROR SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports that a failure occurred during self-test
677 REM SOFTWARE SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
DOWNLOAD port reports that software download is in progress
678 REM SHDSL PSD NOT SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
COMPATIBLE port reports a mismatch between PSD mode selected by the
user and PSD mode used by the line
679 REM SHDSL SYNC LOSS SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports that the SHDSL line is not synchronized
680 REM NO DTE INTERFACE SL:CH Minor The remote ASMi-52 unit connected to the specified SHDSL
port reports that no DTE interface is detected
681 REM E1-TS RATE NOT SL:CH Minor The remote ASMi-52/E1 unit connected to the specified
COMPATIBLE SHDSL port reports that the current line rate does not support
the number of assigned E1 timeslots
682 REM MF SYNC LOSS SL:CH Minor The remote ASMi-52/E1 unit connected to the specified SHDSL
port reports loss of multi frame synchronization
683 REM MF REMOTE SYNC SL:CH Minor The remote ASMi-52/E1 unit connected to the specified SHDSL
LOSS port reports a remote loss of multiframe synchronization
684 REM E1 TS NOT X128 SL:CH Minor The remote ASMi-52/E1 unit connected to the specified SHDSL
port reports that the number of timeslots assigned for the
ASMi-52 unit with 4-wire line interface is not the correct
number needed to obtain a rate of n×128 kbps
685 REM E1 TS NOT COMP SL:CH Minor The remote ASMi-52/E1 unit connected to the specified SHDSL
port reports that the number of timeslots assigned for the
local unit does not match the number of timeslots assigned for
the remote unit

999
SDH/SONET Subsystem Alarms (CL.1/155 and CL.1/155GbE Modules)

1001

Default
Severity
1002 ALARM BUFFER System Major The alarm buffer of the Megaplex-4100 has been filled up and
OVERFLOW the new alarms are overwriting the oldest alarms (the first
alarms stored in the alarm buffer). Read the alarms and then
clear the buffer
1003 SFP NOT EXIST System Major The corresponding port is not equipped with an SFP. If the
problem persists after installing a good SFP, replace the
corresponding CL module
1005 CLOCK CHANGE TO System Event The SDH/SONET subsystem has switched to the fallback clock
FALLBACK source
1006 CLOCK CHANGE TO System Event The SDH/SONET subsystem has switched to the internal clock
INTERNAL source
1007 CLOCK CHANGE TO System Event The SDH/SONET subsystem has returned to the master clock
MASTER source

1009

to
1013
1014 SIGNAL LOSS SL(CL):CH Major The specified CL module port reports loss of STM-1 input signal
1015 LOCAL SYNC LOSS SL(CL):CH Major The specified CL module port reports lost synchronization to
incoming data stream. May indicate a configuration error or a
technical failure
1016 REMOTE SYNC LOSS SL(CL):CH Major Remote port lost synchronization to the incoming data stream.
May indicate a configuration error or a technical failure

to
1022
1023 LINE CODE VIOLATION SL(CL):CH Event A bipolar violation (BPV) error has been detected by the
specified PDH port.
This alarm may also appear when an “excessive zeroes” error
occurs (more than three consecutive error occurs (more than
three consecutive error occurs (more than three consecutive
“0”s for an E1 port, or more than 8 consecutive “0”s for a T1
port using B8ZS zero suppression)

Default
Severity
1024 AIS OCCURRED SL(CL):CH Major The Alarm Indication Signal (AIS), a framed "all ones"
sequence, is received by the specified PDH port, VC or VT.
AIS on an E1 link is declared when less than three spaces (i.e.,
2 or less zeros) are detected in a sequence of 512 bits (256
μsec window).
AIS on a T1 link (blue alarm) is declared when less than five
spaces are detected in a 3-msec window
1025 FRAME SLIP SL(CL):CH Event A frame slip occurred on the E1 or T1 port
1027 PAYLOAD LABEL SL(CL):CH Major The specified VC-4/STS-1 receives an unequipped payload label
UNEQUIPPED (Signal Label).
This alarm condition may often occur while a new trail is being
prepared
1028 PATH TRACE ID SL(CL):CH Major The path trace ID received from the far end does not match
MISMATCH (TIM) the expected ID for the specified VC-4/STS-1. This may indicate
incorrect routing of the corresponding VC-4/STS-1
1029 PAYLOAD LABEL SL(CL):CH Major A payload label mismatch has been detected for the specified
MISMATCH (PLM) VC-4/STS-1. This may indicate incorrect routing of the
corresponding VC.
prepared
1030 REMOTE DEFECT SL(CL):CH Major A remote defect indication is received from the remote
INDICATION (RDI) equipment through the specified STM-1 link
1031 LOSS OF POINTER SL(CL):CH Major The STM loss of pointer (LOP) state is entered when N
consecutive invalid pointers are received by the specified VC-4,
STS-1, VC-3, VC-12, or VT1.5 (N = 8, 9, ...).
LOP state is exited when 3 equal valid pointers or 3
consecutive AIS indications are received
1032 SIGNAL DEGRADED ERROR SL(CL):CH Minor The bit error rate of the received STM-1, VC-4, STS-1, VC-3,
VC-12, or VT1.5 signal exceeds the preset signal-degraded
threshold
1033 EXCESSIVE BIT ERROR SL(CL):CH Major The bit error rate of the received STM-1, VC-4, STS-1, VC-3,
RATE VC-12, or VT1.5 signal exceeds the preset excessive-BER
threshold
1034 FRAME LOSS SL(CL):CH Major The loss of frame (LOF) state is entered when an out-of-frame
(OOF) state exists at the specified STM-1 port 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.
The LOF state is exited when an in-frame state exists
continuously for 1 to 3 ms
1035 TX FAIL (TX PWR OUT OF SL(CL):CH Major Laser TX power monitor value exceeds the high level alarm
RANGE) threshold

Default
Severity
1036 TX DEGRADE (LASER BIAS) SL(CL):CH Major Laser Bias monitor value exceeds the high level alarm threshold
1038 STM OUT OF FRAME SL(CL):CH Major Loss of frame alignment for the specified STM-1 port

to
1048

1050
1051 TX LCAS ADD NORMAL SL(CL):CH Event When using LCAS encapsulation, time-out occurred while
TIMEOUT waiting to transmit an ADD NORMAL message
1052 RX LOSS OF SEQUENCE SL(CL):CH Event The sequence number of a received LCAS message is out of
sequence
1053 RX LCAS CRC ERROR SL(CL):CH Event A CRC error has been detected in an LCAS message
1055 MAC RX FIFO BUFFER SL(CL):CH Event The rate of frame ingress from the local LAN port exceeds the
OVERFLOW egress rate toward the WAN (through the STM-1/OC-3 link)
1056 MAC TX FIFO BUFFER SL(CL):CH Event The rate of frame ingress from the WAN (from the STM-1/OC-3
OVERFLOW link) exceeds the egress rate to the local LAN

to
1059
1060 RX LAPS/FRAME SL(CL):CH Minor This alarm indicates a mismatch in the ADDRESS, CONTROL or
MISMATCH SAPI fields of the received LAPS/LAPF frame. This alarm is set
(ON) after the detection of any one of these errors and is
reset (OFF) after the user displays the statistics counters.

1062
1063 NUMBER OF VCS UNDER SL(CL):CH Major When using LCAS encapsulation, the number of active VCs per
MINIMUM group can be changed dynamically. This alarm is set (ON) when
the number of active VCs drops below the minimum configured
value, and is reset (OFF) after the failed VCs recover, or the
configuration is changed
1064 GFP OUT OF SYNC SL(CL):CH Major When GFP encapsulation is used, the GFP multiplexer
subsystem serving the LAN interface has lost synchronization
to the incoming stream
1065 DIFFERENTIAL DELAY SL(CL):CH Major This alarm is set (ON) when the differential delay exceeds the
EXCEEDS MAX maximum delay configured in the database for the
corresponding virtual group, and is reset (OFF) when the delay
decreases below the maximum value.

Default
Severity
1066 TX LCAS ADD ACK SL(CL):CH Event When using LCAS encapsulation, time-out occurred when
TIMEOUT waiting to transmit an ADD ACK message
1067 TX LCAS REMOVE ACK SL(CL):CH Event When using LCAS encapsulation, time-out occurred when
TIMEOUT waiting to transmit a REMOVE ACK message
1068 GFP CHANNEL ID SL(CL):CH Event The GFP multiplexer subsystem detects an unexpected channel
MISMATCH number (CID)
1069 CLOCK FAIL System Major The internal clock oscillator serving the STM-1 ports failed
1070 LOSS OF MULTIFRAME SL(CL):CH Major Loss of multiframe synchronization occurred on the specified
VC-4/STS-1/VC-3/VC-12/VT1.5
1072 SOFTWARE DOWNLOAD System Event Software downloading to the SDH/SONET subsystem failed.
FAIL Repeat the process
1073 NETWORK LINE SL(CL):CH Major The alarm is set (ON) when a network-initiated line loopback
LOOPBACK has been activated on the corresponding port. This loopback
cannot be disconnected by the system management.
The alarm is reset (OFF) after the loopback is deactivated
1075 FLIP OCCURRED SL(CL):CH Event Flipping to the alternate path occurred
1076 REMOTE FAIL INDICATION SL(CL):CH Major A remote fail indication has been received by the specified
VC-3, VC-12 or VT1.5

1078
1079 PAYLOAD LABEL SL(CL):CH Minor The specified VC-3, VC-12 or VT1.5 receives an unequipped
UNEQUIPPED signal label.
prepared
1080 PATH TRACE ID MISMATCH SL(CL):CH Minor The path trace ID received from the far end for the specified
(TIM) VC-3, VC-12 or VT1.5 does not match the expected value. This
may indicate incorrect routing of the corresponding VC or VT.
1081 PAYLOAD LABEL SL(CL):CH Minor A payload label mismatch has been detected for the specified
MISMATCH (PLM) VC-3, VC-12 or VT1.5. This may indicate incorrect routing of
the corresponding VC or VT.
prepared
1082 REMOTE DEFECT SL(CL):CH Minor A remote defect indication is received through the specified
INDICATION (RDI) VC-4/STS-1/VC-3/VC-12/VT1.5
1083 SIGNAL DEGRADED ERROR SL(CL):CH Minor The bit error rate of the signal received through the specified
VC or VT exceeds the preset signal-degraded threshold

Default
Severity
1084 EXCESSIVE BIT ERROR SL(CL):CH Minor The bit error rate of the signal received through the specified
RATE VC or VT exceeds the preset excessive BER threshold

1086
1087 IP ADDRESS NOT System Major No IP address has been allocated by the DHCP server
ALLOCATED
1089 VC AIS OCCURRED SL(CL):CH Major An Alarm Indication Signal (AIS indication) is received through
the specified VC-4/STS-1 Signal Label (C2)
1090 E1 MULTIFRAME REMOTE SL(CL):CH Minor On an E1 port operating with G732S framing, the
SYNC LOSS corresponding remote module port has lost multiframe
synchronization
1091 NETWORK PLB SL(CL):CH Minor A network-initiated payload loopback has been activated. This
loopback cannot be disconnected by the system management.
This message may appear only when using a T1 port with ESF
framing
1092 EXCESSIVE ERROR RATIO SL(CL):CH Major The error rate detected on the frame synchronization bits is
high, as defined by ITU-T Rec. G.732. This may indicate
hardware problems or defective connections (appears only
when an E1 port is used)
1093 AIS RED ALARM SL(CL):CH Major The local frame synchronization has been lost because of AIS
reception
1094 AIS WAS DETECTED SL(CL):CH Major The Alarm Indication Signal (AIS), a framed “all ones”
sequence, is received on the corresponding port
1095 CRC ERROR SL(CL):CH Event The corresponding PDH port reports the detection of a CRC
error.
This message may appear only for E1 port using the CRC-4
option
1096 E1 MULTIFRAME LOCAL SL(CL):CH Minor On an E1 port operating with G732S framing, the
SYNC LOSS corresponding local module port has lost multiframe
synchronization
1097 SFP FAILURE SL(CL):CH Major The SFP module was removed or failed
1098 FAR END CSF ERROR SL(CL):CH Major Far end CSF indication (detection of a CSF indication. Cleared
on receipt of the first valid GFP Client data frame, or after
failing to receive 3 CSF indications in 3 seconds)
1099 RESET TO ACTIVATE NEW System Major The alarm it set (ON) after the after completing software
SOFTWARE downloading without resetting, and is reset (OFF) after
performing the reset or restarting the device
1100 TX DEGRADE(LASER SL(CL):CH Major Indicates that the internal temperature of the port laser
TEMPERATURE) transmitter exceeds the high-temperature threshold

Default
Severity
1101 CLOCK OUT OF RANGE SL(CL):CH Major The frequency of the timing reference clock is not within the
allowed range
1103 RX TRAIL FAILURE CH Major Indication in VCG that prevents the connection of the data
path. Required to trigger fault propagation when LCAS
encapsulation not used

to
1999
System Alarms
2001 DB SAVE STARTED System Event Database saving to flash memory was started
2002 DB SAVE COMPLETED System Event Database saving completed
2003 DB SAVE IN PROCESS System Minor Database is being saved to flash memory
2004 CLK CHANGED TO System Event The clock source has been changed to S-SUBSYSTEM
S-SUBSYSTEM (SDH/SONET subsystem)
2005 MASTER CLK SWITCH System Event The clock source has been changed to another clock in the
OCCURRED master clock list
2006 FALLBACK CLK SWITCH System Event The clock source has been changed to another clock in the
OCCURRED fallback clock list
2007 BUS CLOCK FAILURE SL Major Internal 16MHz clock failure. If problem occurs after resetting
the Megaplex-4100, it must be replaced

to
2019
CL Module Alarms
2020 CL POWER SUPPLY SL(CL) Major Power supply failure

FAILURE
2021 CL FAN FAILURE SL(CL) Major Failure of the internal cooling fan of the CL module. replace
the module as soon as possible
2022 STATION CLOCK FAIL SL(CL) Major Station clock port reports sync loss or signal loss
2023 TFTP SW DOWNLOAD SL(CL) Event TFTP software downloading session started
STARTED
2024 TFTP DB DOWNLOAD SL(CL) Event TFTP database downloading session started
STARTED
2025 TFTP DB UPLOAD SL(CL) Event TFTP database uploading session started
STARTED

Default
Severity
2026 TFTP PROCESS SL(CL) Event TFTP process completed

COMPLETED
2027 TFTP PROCESS ABORTED SL(CL) Event TFTP process aborted
2028 CL OVERHEATED SL(CL) Major The corresponding CL module reports excessive internal
temperature.
This may occur because the cooling vents have been
obstructed, or because of a failure of the internal cooling fan:
in this case, replace immediately the module
2029 SFP NOT EXIST SL Major The corresponding SFP is not inserted.
If the corresponding socket is occupied by an SFP, first try to
remove it, and then reinsert the SFP

to
2059
I/O Module Ethernet Port Alarms (M8E1/M8T1/M8SL/OP-108C/OP-106C)
2060 LAN NOT CONNECTED SL:CH Major No signal on Ethernet port (this alarm will not appear when
the user disables the corresponding LAN port)
2061 LCP FAIL E1 1 SL: BND Major
2064 LCP FAIL E1 4 SL: BND Major PPP LCP protocol failure on specified E1 port of an MLPPP
2065 LCP FAIL E1 5 SL: BND Major bundle
2069 BCP FAIL SL:BND Major PPP BCP protocol failure for the MLPPP bundle
2070 PHYSICAL LOOP DETECTED SL:CH Major Physical loopback detected on one of the E1 ports included in
an MLPPP bundle
2071 OAM REMOTE FAILURE SL:BNDETH Major Remote failure occured. The failure is discovered by OAM
message process. This alarm is relevant for both bundles and
Ethernet ports
2072 PORT DOWN DUE TO FP SL:CH Major Port operation status changed to Down by the fault
propagation mechanism

to
1200

Default
Severity
MPW-1 Module Alarms
1201 PW OAM OUT OF SYNC PW Major The OAM signaling mechanism (used to check connectivity)
detected loss of connectivity
1202 PW OAM CONFIGURATION PW Major Packet discarded due to mismatch in TDMoIP frame format
MISMATCH between the received packet and the PW configuration
1204 PW HW LACK OF TX PW Major Packet discarded due to mismatch between received packet
BUFFERS length and bundle configuration
1205 PW LOCAL FAIL PW Major Ethernet frames are not received by the local PW on the
specified connection
1206 PW LINK FAIL IN REMOTE PW Major The remote unit reports the reception of a packet with Local
UNIT Fail indication (L-bit set)
1207 PW REMOTE FAIL (RDI) PW Major The remote unit reports the reception of a packet with
Remote Fail indication (R-bit set).
1209 PW RX FRAME LENGTH Major Packet discarded due to mismatch between received Ethernet
MISMATCH packet length and PW configuration
1210 PW SEQUENCE ERR PW Event TDMoIP/MPLS packet sequence number error found within the
INSIDE WINDOW window
1212 PW SEQUENCE ERR PW Event TDMoIP/MPLS packet sequence number error found outside
OUTSIDE WINDOW the tracking window
1214 PW JITTER BUFFER PW Event Underrun has occurred in the jitter buffer of the
UNDERRUN corresponding pseudowire
1216 PW JITTER BUFFER PW Event Overrun has occurred in the jitter buffer of the corresponding
OVERRUN pseudowire

to
1219
1220 PW RX TDMOIP VERSION PW Major Mismatch between local and remote PW TDMoIP versions
MISMATCH

to
1322
1323 RX MISS ORDERED PW Event Packets discarded due to misordering situation

FRAMES DISCARDED

Default
Severity

to
1399
OP-108C/OP-106C Module Alarms (see also E1/T1 alarms)

1400 REMOTE CONNECTION System Major Loss of connection between the devices
FAIL
1404 SIGNAL LOSS SL:CH Major The specified port on the local module or remote unit reports
the loss of input signal
1405 FRAME LOSS SL:CH Major The specified port on the local module or remote unit reports
the loss of frame
1406 RX AIS WAS DETECTED SL:CH Major The Alarm Indication Signal (AIS), a framed “all ones”
sequence, is received on the corresponding port of the local
module or remote unit
1407 TX FAILURE SL:CH Major The OP-108C/OP-106C module failed to transmit frames
towards the remote unit

to
1999
Traps Generated by Megaplex-4100

Megaplex-4100 generates several types of traps that report special events. These
traps are presented in Table 6-27, together with a description of their formal
object identifier (OID) and attached parameters.
Note
Trap parameters appearing in bold font in Table 6-27 do not appear in the MIB
trap definition.

Table 6-27. Traps List
No. Trap Attached Parameters Interpretation
General Traps
1 rfc3418.coldStart 3418.sysName, Reports that the Megaplex-4100 has

::= { snmpTraps 1 } 3418.sysLocation been powered up, and successfully
completed the cold-start process.
OID: 1.3.6.1.6.3.1.1.5.1
In response, a network management
station should perform all the
operations necessary to open the
Megaplex-4100 element manager
application
2 rfc3418.warmStart 3418.sysName, Reports that the Megaplex-4100 has

::= { snmpTraps 2 } 3418.sysLocation been restarted (for example, by
resetting the CL modules), and
OID: 1.3.6.1.6.3.1.1.5.2
successfully completed the warm-start
process.
In response, a network management
station should perform all the
operations necessary to open the
Megaplex-4100 element manager
application
3 rfc2863.linkUp ifIndex, ifAdminStatus, Reports that the status of the

::= { snmpTraps 4 } ifOperStatus, 2863.ifDescr corresponding link (ifOperStatus) has
2863.ifAlias, 3418.sysName, changed from down to any other value
OID: 1.3.6.1.6.3.1.1.5.4
3418.sysLocation, except notPresent.
openViewSeverity For any value other than normal, see
description of ifOperStatus in the
following Note
4 rfc2863.linkDown ifIndex, ifAdminStatus, Reports that the status of the

::= { snmpTraps 3 } ifOperStatus, 2863.ifDescr, corresponding link (ifOperStatus) has
2863.ifAlias, 3418.sysName, changed to down from any other value
OID: 1.3.6.1.6.3.1.1.5.3
3418.sysLocation, except notPresent.
openViewSeverity For any value other than normal, see
description of ifOperStatus in the
following Note
5 rfc3418.authenticationFailure 3418.sysName, Reports an SNMP authentication

::= { snmpTraps 5 } 3418.sysLocation failure (this is usually the result of an
attempt by a manager using an
OID: 1.3.6.1.6.3.1.1.5.5
unauthorized community to access
Megaplex-4100)
radGen Traps
6 rad.tftpStatusChangeTrap tftpStatus Reports a change in the status of the

OID: 1.3.6.1.4.1.164.6.1.0.1 TFTP protocol (used by the RADView
map application SWDL function)

No. Trap Attached Parameters Interpretation
7 rad.agnStatusChangeTrap agnIndication, Indicates the Megaplex-4100 alarm

::= { systemsEvents 2 } agnTestStatus, severity associated with the reported
openViewSeverity (same trap or event.
OID: 1.3.6.1.4.1.164.6.1.0.2
value as agnIndication) Used by RADView HPOV map
application to provide the node status
indication (for example, select the
node color on the map)
WAN Traps
8 rad.alarmsTrap alrBufDescription, Provides information on alarms in a

::= { muxHubEvents 1 } alrBufCode, alrBufSlot, format that includes the information
alrBufPort, alrBufSeverity, explained in Table 6-26.
1.3.6.1.4.1.164.3.2.0.1
alrBufState, 3418.sysName, This trap is used by the RADView TDM
3418.sysLocation, Service Center.
openViewSeverity,
2863.ifAlias (only for alarms
related to interfaces)
9 rad.sanityTrap agnSSanityCheckStatus, Provides information on sanity

::= { muxHubEvents 2 } agnCSaveCnfgIdxCmd, warnings and errors detected by the
mngIP (of the manager that Megaplex-4100 sanity check function,
1.3.6.1.4.1.164.3.2.0.2
initiated the Update in a format that includes the
command) information explained in Table 6-24
10 rad.cnfgFlipTrap agnSActiveCnfg, Reports that a configuration update,

::= { muxHubEvents 3 } mngIP (of the manager that initiated by the specified manager, is
initiated the Update being performed.
OID 1.3.6.1.4.1.164.3.2.0.3
command) A network management station that
detects this trap should display an
Update Performed message, and
should take steps to avoid errors as a
result of the configuration change (for
example, close windows associated
with the Megaplex-4100 being
updated)
11 rad.flipDbChangeTrap agnSAlrStatusAll, Reports that a configuration update

::= { muxHubEvents 4 } agnSAlrStatus has been initiated by an automatic
database flip.
OID: 1.3.6.1.4.1.164.3.2.0.4
This trap is not yet in use

Note For your convenience, the RFC2863 definitions of ifOperStatus are presented
below:
• up (1) – If ifAdminStatus is changed to up(1), ifOperStatus will change to
up(1) if the interface is ready to transmit and receive network traffic.
• down (2) – If ifAdminStatus is down(2), ifOperStatus must be down(2).
If ifAdminStatus is changed to up(1), ifOperStatus should remain in the
down(2) state if and only if there is a fault that prevents it from going to the
up(1) state.
ifOperStatus will change from up(1) to down(2) if the interface cannot pass
packets to/from the network.
• testing (3) – A test is active on the interface.
The testing(3) state indicates that no operational packets can be passed.
• unknown (4) – Interface status cannot be determined.
• dormant (5) – If ifAdminStatus is changed to up(1), ifOperStatus should
change to dormant(5) if the interface is waiting for external actions (such as a
serial line waiting for an incoming connection).
• notPresent (6) – Some component is missing.
If ifAdminStatus is changed to up(1), ifOperStatus should remain in the
notPresent(6) state if the interface has missing (typically, hardware)
components.
• lowerLayerDown (7) – The interface is down due to the state of lower-layer
interface(s).

6.4 Troubleshooting
Preliminary Checks
In case a problem occurs, perform the following preliminary checks:
• If the problem is detected the first time the Megaplex-4100 is put into
operation, first perform the following checks:
Check for proper chassis and module installation, and correct cable
connections, in accordance with the system installation plan.
Check the system and module configuration parameters 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 fallback 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, and that of the standby must
flash. If not, first check the configuration.
• Check the displayed alarm messages and refer to Handling Alarms and Traps
for their interpretation and associated corrective actions.
Troubleshooting Procedure
If the problem cannot be corrected by performing the actions listed above, refer
to Table 6-28. 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-28. Troubleshooting Chart
No. Trouble Symptoms Probable Cause Corrective Measures
1 Megaplex-4100 does not 1. No power Check that power is available at the power
turn on outlets or power distribution panel serving
the Megaplex-4100.
Check that both ends of all the
Megaplex-4100 power cables are properly
connected.
2. Defective PS module Replace the suspected PS module
3. Defective Megaplex-4100 Replace Megaplex-4100
6-136 Troubleshooting Megaplex-4100 Ver. 2.0

2 The local Megaplex-4100 1. Connection made to the Check that the connection is made to the
cannot be configured inactive CL module CONTROL DCE connector of the CL module
through its CONTROL DCE whose ON LINE indicator lights
port
2. Configuration problem Restore the default parameters as
explained in Chapter 2, and then perform
the preliminary supervision terminal
configuration instructions given in
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
4. Software not yet loaded Download the appropriate Megaplex-4100

into CL module, or software to the CL modules in accordance
corrupted with Appendix B
5. Defective CL module Replace the corresponding CL module
3 The local Megaplex-4100 1. Configuration problems Check the CONTROL ETH port configuration.
cannot be managed Check that the ON LINE indicator of the CL
through its CONTROL ETH module lights
port
2. Problem in the connection Check that the LINK indicator of the
between the CONTROL CONTROL ETH port lights.
ETH port and the LAN 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 Check the external equipment (for example,

the default gateway and other routers) 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
Megaplex-4100 Ver. 2.0 Troubleshooting 6-137

4 The LINK LOS indicator of a 1. Cable connection Check for proper connections of the cables
port of the CL.1/155 or problems to the LINK connector of each CL.1/155 or
CL.1/155GbE module lights CL.1/155GbE port.
Repeat the check at the user’s equipment
connected to the port.
2. External problem Activate the remote loopback at the local
CL.1/155 or CL.1/155GbE module port.
• If the user’s equipment
connected to the LINK 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 Port,
replace the CL.1/155 or
CL.1/155GbE module
5 The status indicator of a 1. Cable connection Check for proper connections of the cables
local I/O module port lights problems to the module connector.
in red Repeat the check at the user’s equipment
connected to the port.
2. External problem 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 providing the link
to the remote unit.
3. Defective I/O module Replace the I/O module
6 The LOS indicator of the 1. Cable connection Check for proper connections of the cables
STATION CLK port lights in problems to the connector.
red Repeat the check at the equipment
providing the station clock signal to the
Megaplex-4100.
2. Defective CL module Replace the CL module
6-138 Troubleshooting Megaplex-4100 Ver. 2.0

6.5 Testing Megaplex-4100 Operation

When a problem occurs, Megaplex-4100 offers a set of diagnostic functions that
permit to efficiently locate the problem (in the Megaplex-4100 chassis, one of
Megaplex-4100 modules, a connecting cable, or external equipment) and rapidly
restore full service.
The diagnostic functions include:
• Diagnostic tests for checking transmission paths. These tests include
loopbacks at the various ports, which enable to 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).
The available diagnostic functions depend on the installed modules. For
specific instructions, refer to the corresponding module Installation and
Operation Manual.
• Ping for IP connectivity testing.
Description of Test and Loopback Functions

Table 6-29 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.
Note For CL modules with SDH/SONET links, Table 6-29 illustrates the test and
loopback functions for CL.1/155 modules, however the same options are also
available for CL.1/155GbE modules.
For a description of the test and loopbacks supported by a specific I/O module,
refer to the corresponding module Installation and Operation Manual.
Table 6-29. Megaplex-4100 Test and Loopback Functions
Megaplex-4100
SDH/SONET Interface
(CL.1/155 & CL.1/155/GbE only)
CL PDH Framers
1
Diagnostic 2
Function .
I/O Port Cross-Connect . VC
Matrix .. Mapper
Matrix
Framer
.
.
..
Megaplex-4100 Ver. 2.0 Testing Megaplex-4100 Operation 6-139

Megaplex-4100
SDH/SONET Interface
(CL.1/155 & CL.1/155/GbE only)
CL PDH Framers
1
Diagnostic 2
Function Cross-Connect .. VC
I/O Port
Matrix . Mapper
Matrix
Framer
..
.
.
.
Local loopback on I/O Port Cross-Connect

Interface Matrix
I/O module port
Remote loopback on Port Cross-Connect

Interface Matrix
I/O module port
Local loopback on Port Cross-Connect

Interface Matrix
E1 or T1 port
"1 "
Remote loopback on Port Cross-Connect

Interface Matrix
E1 or T1 port
PDH Framers
1
Local loopback on E1 2 Cross-Connect
or T1 timeslots .. Matrix
..
.
6-140 Testing Megaplex-4100 Operation Megaplex-4100 Ver. 2.0

Megaplex-4100
SDH/SONET Interface
(CL.1/155 & CL.1/155/GbE only)
CL PDH Framers
1
Diagnostic 2
I/O Port
Matrix . Mapper
Matrix
Framer
..
.
.
.
PDH Framers
1
Remote loopback on 2 Cross-Connect
E1 or T1 timeslots
.. Matrix
..
.
Framer
Local loopback on
SDH/SONET link
Framer
Remote loopback on
SDH/SONET link
VC Matrix
Local LVC Loopback
VC Matrix
Remote LVC
Loopback
Mapper
Global PDH local
loopback
Mapper
Global PDH remote
loopback

Megaplex-4100
SDH/SONET Interface
(CL.1/155 & CL.1/155/GbE only)
CL PDH Framers
1
Diagnostic 2
I/O Port
Matrix . Mapper
Matrix
Framer
..
.
.
.
PDH Framers
Local loopback on
2
PDH port ..
.
..
.
PDH Framers
Remote loopback on
2
PDH port ..
..
..
PDH Framers
1
Local loopback on
timeslots of 2
PDH port
..
..
..
PDH Framers
1
Remote loopback on
timeslots of 2
PDH port
..
..
..
Local Loopback on I/O Port of I/O Module

The local port loopback is used to test the connections between a selected I/O
port and the equipment connected to that port. For details, see the I/O module

Within the tested module, the loopback signal path includes most of the line
interface circuits serving the selected port.
Remote Loopback on I/O Port of I/O Module

The remote port loopback is used to test the line interface circuits of a selected
external port. This test also checks the transmission plant connecting the remote
equipment to the corresponding port. For details, see the I/O module Installation
and Operation Manual.
Within the tested module, the loopback signal path includes most of the module
circuits, except for line interface circuits serving the selected port.
Local Loopback on E1 or T1 Port of I/O Module

The local port loopback is used to test the path of the signals intended for
transmission through a selected E1 or 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 6-29, 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 or T1 Port of I/O Module

The remote port loopback is used to test the line interface circuits of a selected
E1 or T1 external port. This test also checks the transmission plant connecting
the equipment connected to the corresponding port.
As shown in Table 6-29, when a remote loopback is activated on an E1 or 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.
The remote loopback should be activated only after checking that the remote unit
operates normally with the 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 also operated normally when the local port
loopback has been 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 or T1 I/O Module Port

The local loopback on selected timeslots of an E1 or T1 port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
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 or T1 port.
As shown in Table 6-29, 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.
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
assigned to bundles.
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).
Remote Loopback on Timeslots of E1 or T1 I/O Module Port

The remote loopback on selected timeslots of an E1 or T1 port is used to return
the receive payload carried by the selected timeslots through the same timeslots
of the transmit path. This test is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the E1 or T1 port, to
an I/O port of another module that uses only a fraction of the available port
bandwidth.
As shown in Table 6-29, 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.
It is not allowed to activate loopbacks on timeslots assigned to bundles.
The other features related to loopback activation/deactivation described above
for the local loopback on timeslots are also applicable to the remote loopback.
Local Loopback on SDH/SONET Link (CL.1/155 and

CL.1/155GbE only)
As shown in Table 6-29, the local loopback is activated within the SDH/SONET
framer. When the local loopback is activated, the framed transmit signal is
returned to the input of the framer receive path at a point just before the output

to the network. To provide a keep-alive signal to the transmission equipment

serving the link under test while the loopback is activated, the transmit signal is
also sent to the network.
While the loopback is activated, the local Megaplex-4100 must receive its own
signal, and thus it must be frame-synchronized. In addition, each Megaplex-4100
local port (must also receive its own signal: therefore, for all the TDM ports in the
Megaplex-4100 the result is that the port interfaces are synchronized and do not
generate alarm indications. Moreover, the signal received from the user’s
equipment connected to the port is also returned to the user.
The local SDH/SONET link loopback is used to test the path of the signals
intended for transmission to the network, starting at the other Megaplex-4100
ports, passing through the cross-connect matrix in the CL module, and up to the
SDH/SONET framer. The path includes most of the Megaplex-4100 circuits,
including the SDH/SONET interface in the active CL module.
Remote Loopback on SDH/SONET Link (CL.1/155 and

CL.1/155GbE only)
As shown in Table 6-29, 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 only after checking that the remote 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.
The received signal remains connected to the receive path of the local
Megaplex-4100. Assuming that the local Megaplex-4100 unit also operates
normally when its SDH/SONET local loopback is activated, then if the port status
of the active network port is normal, the local Megaplex-4100 should be
synchronized.
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 (LLB) on LVC (CL.1/155 and CL.1/155GbE only)

As shown in Table 6-29, 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 at a point just before the output to the SDH/SONET
framer.

While the loopback is activated, the equipment mapped to the tested PDH port of
the local Megaplex-4100 must receive its own signal, and thus it must be
frame-synchronized.
Remote Loopback on LVC (CL.1/155 and CL.1/155GbE only)

As shown in Table 6-29, the remote loopback is activated within the network side
circuits of the VC cross-connect matrix, and therefore the loopback signal paths
includes all the circuits 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 VC 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.
Global PDH Local Loopback (CL.1/155 and CL.1/155GbE only)

As shown in Table 6-29, the global PDH local loopback is activated on all the
active PDH ports, by means of the mapper serving the SDH/SONET link interface.
The result is similar to that of the local SDH/SONET link loopback, except for the
location of the loopback itself within the SDH/SONET link interface.
Global PDH Remote Loopback (CL.1/155 and CL.1/155GbE

only)
As shown in Table 6-29, the global PDH remote loopback is activated on all the
active PDH ports, by means of the mapper serving the SDH/SONET link interface.
The result is similar to that of the remote SDH/SONET link loopback, except for
the location of the loopback itself within the SDH/SONET link interface.
Local Loopback on PDH Port (CL.1/155 and CL.1/155GbEonly)

The local PDH port loopback is used to test the intra-Megaplex-4100 paths of the
signals intended for transmission through a selected PDH port: these paths start
at the other Megaplex-4100 port(s) connected to the tested PDH port, passes
through the cross-connect matrix in the CL module, and continues up to the
framer of the PDH port within the SDH/SONET link interface. Therefore, these
paths include all of the Megaplex-4100 local ports connected to the tested PDH
port, and in the particular the operation of the cross-connect matrix circuits that
handle the signals directed to the tested PDH port within the CL module.
As shown in Table 6-29, the local PDH port loopback is activated within the PDH
framer of a selected CL virtual PDH port. When the local PDH port loopback is
activated, the port transmit signal is returned through receive path of the same
port within the PDH port framer. The local PDH port must receive its own signal,

and thus it must be frame-synchronized. In addition, each local port 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.
Remote Loopback on PDH Port (CL.1/155 and

CL.1/155GbEonly)
As shown in Table 6-29, the PDH port remote loopback is activated on the framer
serving the port within the SDH/SONET link interface. The result is similar to that
of the remote global PDH port loopback, except that it affects only the selected
PDH port.
Local Loopback on PDH Port Timeslots (CL.1/155 and

CL.1/155GbE only)
The local loopback on selected timeslots of a PDH 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 an I/O port of
another module that uses only a fraction of the available PDH port bandwidth,
and the PDH port.
As shown in Table 6-29, 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
PDH 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.
Remote Loopback on PDH Port Timeslots (CL.1/155 and

CL.1/155GbEonly)
The remote loopback on selected timeslots of a PDH 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 PDH port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
As shown in Table 6-29, 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
PDH port: only the flow of payload carried by the specified timeslots is disrupted.

Activating Tests and Loopbacks

³ To activate/deactivate a test or loopback:
1. Open the Diagnostics menu.
2. Select the type of ports on which you want to activate a test or loopback
(see Activating Tests and Loopbacks for detailed instructions).
A typical Diagnostics task selection screen is shown in Figure 6-93.
MP-4100
Diagnostics
1. Physical Layer>
2. Logical Layer >
3. Active Tests []>
>

-----------------------------------------------------------------------------
Figure 6-93. Typical Diagnostics Task Selection Screen

4. Select the diagnostic task by typing the number corresponding to the desired
type of ports, and then press <Enter>.
Tests and loopbacks can be activated only on active ports (ports configured with
Admin Status = UP). The selections available on the various screens are
automatically adjusted to the port type.
Overview of Diagnostics Menu

Figure 6-94 shows the structure of the Diagnostics menu.

Figure 6-94. Typical Diagnostics Menu Structure (SDH and SONET)

The Diagnostics menu is used to:
• Enable/disable a test or loopback
• Display the tests and loopbacks that are currently active.
To navigate to the required screen, use Diagnostics.
A typical Diagnostics task selection screen is shown in Figure 6-93.

MP-4100
Diagnostics
1. Physical Layer>
2. Logical Layer >
3. Active Tests []>
>
tests/loops, ping operations

-----------------------------------------------------------------------------
Figure 6-95. Typical Diagnostics Task Selection Screen
³ To select a diagnostic task:

Type the corresponding item number and then press <Enter>.
Diagnosing Physical Layer

Select a diagnostic task to be performed on a physical port. Diagnostic tasks can
be performed only on connected ports.
This screen includes two options:
I/O For controlling the diagnostic tasks available for the physical ports of
the modules installed in I/O slots. The parameters available for these
For additional information, refer the corresponding module
CL For controlling the diagnostic tasks available for the physical ports
located on the CL.1/155 or CL.1/155GbE modules.
To navigate to the required screen, use Diagnostics>Physical Layer

A typical Physical Layer selection screen is shown in Figure 6-96.

MP-4100
Diagnostics>Physical Layer
1. I/O >
2. CL >
>

-----------------------------------------------------------------------------
Figure 6-96. Typical Physical Layer Diagnostics Selection Screen

To select a port type, type its number and then press <Enter>.
Diagnosing the I/O Module Physical Layer
³ To select a port of an I/O module:

1. Select I/O on the Physical Layer screen and then press <Enter>.
2. You will see the I/O module selection screen, which displays only modules
installed in the Megaplex-4100.
3. Select the desired module and then press <Enter> to display the module port
selection port.
4. Select the desired port and then press <Enter> to display the test control
screen for the selected port.
³ To automatically limit the test duration:

• On the physical port test control screen for the selected module port, select
Timeout and then press <Enter>. A typical test duration selection screen is
shown in Figure 6-99. The current test duration appears in the header.
³ To select the test type:

• On the physical port test control screen for the selected module port, select
Test Type and then press <Enter>. The current test appears in the header.
For a list of the available options, refer to the module Installation and
Operation Manual.
Diagnosing the CL.1/155 and CL.1/155GbE Modules
³ To select a CL.1/155 or CL.1/155GbE port:

1. Select CL on the Physical Layer screen and then press <Enter>.
2. You will see the CL module selection screen. A typical screen is shown in
Figure 6-97.

MP-4100
Diagnostics>Physical Layer>CL
1. CL-A >
2. CL-B >
>

-----------------------------------------------------------------------------
Figure 6-97. Typical Physical Port Diagnostics CL Module Selection Screen

3. Select the desired CL-A or CL-B module on the CL module selection screen,
4. You will see the port type selection screen for the corresponding CL-A or CL-B
module. A typical screen for CL-A is shown in Figure 6-98.
MP-4100
Diagnostics>Physical Layer>CL>CL-A
1. Link 1 >
2. Link 2 >
>

-----------------------------------------------------------------------------
Figure 6-98. Typical Physical Port Diagnostics CL Link Selection Screen

5. Select the desired link on the CL link selection screen, and then press
<Enter>.
6. You will see the physical port test control screen for the selected link. A
typical screen is shown in Figure 6-99.

MP-4100
Diagnostics>Physical Layer>CL>CL-A >Link 1
1. Test Type> (None)

2. Timeout > (INFINITE )
3. LVC []>
>

-----------------------------------------------------------------------------
Figure 6-99. Typical Physical Port Link Diagnostics Control Screen

1. On the physical port test control screen for the selected link, select Timeout
and then press <Enter>. A typical test duration selection screen is shown in
Figure 6-100. The current test duration appears in the header.
2. Select the desired test duration, in minutes, and then press <Enter>. The
screen includes several pages: use the N and P keys to scroll.
Note
You can end the test at any time, even before the time-out interval expires, by
selecting None for Test Type.
MP-4100
Timeout (INFINITE )
1. INFINITE
2. 1 minute
3. 2 minutes
4. 3 minutes
5. 4 minutes
6. 5 minutes
7. 6 minutes
8. 7 minutes
9. 8 minutes
10. 9 minutes
11. 10 minutes
... (N)
>

-----------------------------------------------------------------------------
Figure 6-100. Typical Physical Port Link Timeout Control Screen


1. On the physical port test control screen for the selected link, select Test Type
and then press <Enter>. A typical test type selection screen is shown in
Figure 6-101. The current test appears in the header.
MP-4100
Test Type (None)
1. None
2. Local Loop
3. Remote Loop
>

-----------------------------------------------------------------------------
Figure 6-101. Typical Physical Port Link Test Selection Screen

2. Select the desired test, and then press <Enter>; to cancel the current test,
select None.
For a description of the tests, refer to Section 6.4.
³ To activate a LVC loopback:

1. Select LVC on the task selection screen of the selected link.
A typical LVC loopback control screen for a Megaplex-4100E with SDH
network interface is shown in Figure 6-102.A; a typical screen for a
Megaplex-4100E with SONET network interface is shown in Figure 6-102.B.
2. Move the selection block to the desired TU on the screen, and then type the
number of the desired loopback state:
2 for LLB (local loopback). This option is not displayed when the port is
disconnected or is path-protected.
3 for RLB (remote loopback). This option is always displayed.
1 for cancelling any current loopback.
3. When done, press <Enter>. The new state of the loopback for the selected
TU appears on the screen.
4. Repeat the procedure until all the desired loopbacks are configured.
5. To activate the new loopback states, type T (Test Activate).

MP-4100
Diagnostics>Physical Layer>CL>CL-A>Link 1>LVC

TUG2-1 LLB None None None None None None None None
1. None 2. LLB 3. RLB
>
%-Db Update; #-Db Undo; $-Sanity; T – Test Activate

-----------------------------------------------------------------------------
A. SDH Screen
MP-4100
Diagnostics>Physical Layer>CL>CL-A>Link 1>LVC
STS1 1 STS1 2 STS1 3

TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4 TU1 TU2 TU3 TU4
1. None 2. LLB 3. RLB
>
%-Db Update; #-Db Undo; $-Sanity; T – Test Activate

-----------------------------------------------------------------------------
B. SONET Screen
Figure 6-102. Typical LVC Loopback Control Screens
Diagnosing the Virtual Ports

The following procedure is used to select a diagnostic task to be performed on a
virtual port. Diagnostic tasks can be performed only on connected ports.
To navigate to the required screen, use Diagnostics>Logical Layer.

A typical Logical Layer selection screen is shown in Figure 6-103. This screen
I/O For controlling the diagnostic tasks available for the virtual ports of
the modules installed in I/O slots. The parameters available for these
For additional information, refer the corresponding module
CL For controlling the diagnostic tasks available for the virtual ports
located on the CL.1/155 or CL.1/155GbE modules.
MP-4100
Diagnostics>Logical Layer
1. I/O>
2. CL >
>

-----------------------------------------------------------------------------
Figure 6-103. Typical Logical Layer Diagnostics Selection Screen

To select a port, type its number and then press <Enter>.
Diagnosing the I/O Module Virtual Ports
³ To select a port of an I/O module:

1. Select I/O on the Logical Layer screen and then press <Enter>.
2. You will see the I/O module selection screen, which displays only modules
installed in the Megaplex-4100 that have virtual ports.
3. Select the desired module and then press <Enter> to display the module port
selection port.
4. Select the desired port and then press <Enter> to display the test control
screen for the selected port.

On the virtual port test control screen for the selected module port, select Time
Out and then press <Enter>. A typical test duration selection screen is shown in
Figure 6-99. The current test duration appears in the header.


On the virtual port test control screen for the selected module port, select Test
Type and then press <Enter>. The current test appears in the header. For a list of
the available options, refer to the module Installation and Operation Manual.
Diagnosing the CL.1/155 and CL.1/155GbE Virtual Ports
³ To select a CL module and test target:

1. Select CL on the Logical Layer diagnostics selection screen, and then press
<Enter>.
2. You will see the CL module selection screen. A typical screen is shown in
Figure 6-104.
MP-4100
Diagnostics>Logical Layer>CL
1. CL-A >
2. CL-B >
>

-----------------------------------------------------------------------------
Figure 6-104. Typical Virtual Port Diagnostics CL Module Selection Screen

3. Select the desired CL-A or CL-B module on the CL module selection screen,
and then press <Enter>. You will see the test type selection screen for the
corresponding CL.1/155 or CL.1/155GbE module. A typical screen for CL-A is

MP-4100
Diagnostics>Logical Layer>CL>CL-A
1. PDH Global Loop >

2. PDH >
3. Clear All Loops > (No)
>

-----------------------------------------------------------------------------
Figure 6-105. Typical Virtual Port Diagnostics CL Test Selection Screen

4. On the virtual port test control screen, select the desired test, and then press
<Enter>.
5. To cancel all the current tests, select Clear All Loops, select Yes, and then
press <Enter>.
PDH Global Loop Test
³ To perform the PDH Global Loop test:

1. On the CL virtual port test selection screen, select PDH Global Loop, and then
press <Enter>.
2. You will see the PDH Global Loop test control screen. A typical test control
screen is shown in Figure 6-106. The current test appears in the header.
MP-4100
Diagnostics>Logical Layer>CL>CL-A >PDH Global Loop
1. Test Type > (-)

>

-----------------------------------------------------------------------------
Figure 6-106. Typical PDH Global Loop Test Control Screen

³ To automatically limit the PDH Global Loop test duration:

1. On the virtual port test control screen, select Timeout and then press
<Enter>. A typical test duration selection screen is shown in Figure 6-100.
The current test duration appears in the header.
Note
You can end the test at any time, even before the time-out interval expires, by
³ To select the PDH Global Loop test type:

1. On the virtual port PDH Global Loop test control screen, select Test Type and
then press <Enter>. A typical test type selection screen is shown in
Figure 6-107. The current test appears in the header.
select None.
MP-4100
Test Type (None)
1. None
2. Local Loop
3. Remote Loop
>

-----------------------------------------------------------------------------
Figure 6-107. Typical Virtual Port PDH Global Loop Test Selection Screen
Tests on a Selected PDH Port
³ To select a PDH port:

1. On the CL module virtual port test selection screen, select PDH, and then
press <Enter>.
2. You will see the PDH port test control screen. A typical test control screen is

MP-4100
Diagnostics>Logical Layer>CL>CL-A>PDH
1. Port > (PDH 1)

2. Test Type > (None)
3. Timeout > (INFINITE)
>

-----------------------------------------------------------------------------
Figure 6-108. Typical PDH Port Test Control Screen

3. Type Port and then press <Enter>. A typical PDH port selection screen is
4. Select the desired PDH port, and then press <Enter>. The screen has several
pages: use N and P to scroll.
MP-4100
Port (PDH 1)
1. PDH 1
2. PDH 2
3. PDH 3
4. PDH 4
5. PDH 5
6. PDH 6
7. PDH 7
8. PDH 8
9. PDH 9
10. PDH 10
11. PDH 11
... (N)
>

-----------------------------------------------------------------------------
Figure 6-109. Typical PDH Port Selection Screen
³ To automatically limit the PDH test duration:

1. On the PDH test control screen, select Timeout and then press <Enter>. A
typical test duration selection screen is shown in Figure 6-100. The current
test duration appears in the header.

Note You can end the test at any time, even before the time-out interval expires, by
³ To select the PDH port test type:

1. On the virtual port PDH test control screen, select Test Type and then press
<Enter>. A typical test type selection screen is shown in Figure 6-110. The
current test appears in the header.
select None.
MP-4100
Diagnostics>Logical Layer>CL>CL-A>PDH>Test Type (None)
1. None
2. Local Loop
3. Remote Loop
4. Loop Per TS
>

-----------------------------------------------------------------------------
Figure 6-110. Typical Virtual Port PDH Port Test Selection Screen
3. If you select Loop per TS, after pressing <Enter>, the screen changes to allow
you to select a desired timeslot test (see Figure 6-111).
MP-4100
Diagnostics>Logical Layer>CL>CL-A>PDH
1. Port > (PDH 1)

2. Test Type > (Loop Per TS)
4. TS Test []>
>

-----------------------------------------------------------------------------
Figure 6-111. Typical PDH Port – Timeslot Test Selection Screen

Note It is not allowed to activate tests and loopbacks on timeslots assigned to

bundles.
4. To continue, select TS Test, and then press <Enter>. You will see the timeslot
test control screen. A typical screen is shown in Figure 6-112.
5. To select the tests to be performed:
Move the selection block to the desired timeslot. The screen has several
pages: use the N and P keys to scroll.
Select the desired test, and then press <Enter>; to cancel the current
test, select None. For a description of the tests, refer to Section 6.4.
6. Repeat the process as required for any additional timeslots.
MP-4100
Diagnostics>Logical Layer>CL>CL-A>PDH>TS Test
Time Slot Test Type

TS 01 NONE
TS 02 NONE
| TS 03 NONE
v TS 04 NONE
TS 05 NONE
TS 06 NONE
TS 07 NONE
TS 08 NONE
1. NONE 3. REMOTE LOOP

2. LOCAL LOOP
>
%-Db Update; #-Db Undo; $-Sanity; T - Test Activate

----------------------------------------------------------------------------
Figure 6-112. Typical Timeslot Test Control Screen for PDH Ports
7. When ready, type T to activate the new timeslot tests. You will see a
confirmation message.
Ping Test
Megaplex-4100 supports the ping function, to check IP connectivity to a
destination IP address. You can select the destination IP address and configure
the number of ping packets sent.
For the supervision terminal, use the following procedure to send pings:
1. Open the Diagnostics menu, and then select Ping Test.
A typical Ping Test screen, as seen before ping parameters are
configured, is shown in Figure 6-113.

MP-4100 MAJ
Diagnostics>Ping Test B049
1. Destination IP Address ... (0.0.0.0)

2. Number of Frames to Send[0 - 50] ... (0)
3. Send Ping
>

-----------------------------------------------------------------------------
Figure 6-113. Typical Ping Test Screen

2. On the Ping Test screen, select the following parameters:
The desired destination IP address
The number of ping packets (up to 50) to be sent. Pinging will be
automatically stopped after sending the specified number of ping
packets.
3. To start ping sending, select Send Ping, and then press <Enter>.
4. If you set the “Number of frames to send” to 0, pinging will not stop
automatically. In this case the Send Ping option turns into Stop Ping. Select it
to stop pinging.
5. The prompt area at the bottom of the screen starts displaying the results of
each ping packet. After the selected number of packets, you will see the test
summary, which indicates:
The number of ping packets sent
The number of ping packets received
The number of lost ping packets (packets not answered before the
standard time-out interval expires).
6.6 Technical Support

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

6-164 Technical Support Megaplex-4100 Ver. 2.0

Appendix A
Connection Data
A.1 CONTROL DCE Connector
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

1 Data Carrier Detect (DCD) From Megaplex-4100
2 Receive Data (RD) From Megaplex-4100
3 Transmit Data (TD) To Megaplex-4100
4 Data Terminal Ready (DTR) To Megaplex-4100
5 Signal Ground (SIG) Common reference and DC power supply ground
6 Data Set Ready (DSR) From Megaplex-4100
7 Request to Send (RTS) To Megaplex-4100
8 Clear to Send (CTS) From Megaplex-4100
9 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.
Megaplex-4100 Ver. 2.0 CONTROL DCE Connector A-1

Appendix A Connection Data Installation and Operation Manual
9 Pin 25 Pin
Connector Connector
TD 3 2
RD 2 3
RTS 7 4
CTS 8 5
To
CONTROL DCE DSR 6 6 To Terminal
Connector DCD 1 8
RI 9 22
DTR 4 20
GND 5 7
CL Side Terminal Side
Figure A-1. 25-Pin Terminal Cable Wiring - Connection to CONTROL DCE

Connector
9-Pin 9-Pin
Connector TD 3 2 Connector
RD 2 3
RTS 7 8
CTS 8 7
To
CONTROL DCE DSR 6 4 To Modem
Connector DCD 1 1
RI 9 9
DTR 4 6
GND 5 5
CL Side Modem Side
Figure A-2. 9-Pin Crossed Cable Wiring - Connection to CONTROL DCE Connector
A-2 CONTROL ETH Connector Megaplex-4100 Ver. 2.0

Installation and Operation Manual Appendix A Connection Data
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
1 TxD+ Transmit Data output, + wire
2 TxD– Transmit Data output, – wire
3 RxD+ Receive Data input, + wire
4, 5 – Not connected
6 RxD– Receive Data input, – wire
7, 8 – 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.
Megaplex-4100 Ver. 2.0 ALARM Connector A-3

Table A-3. ALARM Connector, Pin Functions
Pin Function
1 Major alarm relay – normally-open (NO) contact
2 Major alarm relay – normally-closed (NC) contact
3 Ground
4 Minor alarm relay – normally-open (NO) contact
5 Minor alarm relay – normally- closed (NC) contact
6 Major alarm relay – center contact
7 External alarm input
8 +5V auxiliary output (through 330 Ω series resistor)
9 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
Pin Direction Function
1 Input Clock In (ring)
2 Input Clock In (tip)
3 ↔ Signal Ground (connection controlled by internal jumper)
4 Output Clock Out (ring)
5 Output Clock Out (tip)
6 ↔ Frame Ground (connection controlled by internal jumper)
7 – Not connected
8 – Not connected
A-4 CL CLOCK Connector Megaplex-4100 Ver. 2.0

Installation and Operation Manual Appendix A Connection Data
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 Output
CLOCK IN Ring 1 (Red)
CLOCK IN Tip 2 .. Input

. (Green BNC)
NC 3
CLOCK OUT Ring 4
CLOCK OUT Tip 5 . Output

..
(Red BNC)
NC 6
Cable Sense (option) 7
GND 8
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.
Megaplex-4100 Ver. 2.0 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
1 Common reference (0V ground), BGND
2 +72 VDC ring and feed voltage input

RTN +72 -48
3 -48 VDC ring and feed voltage input
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 24 VDC Module 48 VDC Module
1 Common reference (0V ground), BGND
2 +72 VDC ring and feed voltage input
3 -24 or -48 VDC supply voltage input - + 72V - + 72V

+ - 24V + - 48V
Note
RAD supplies mating connectors for the DC power connectors. For information on
preparing cables using the supplied connectors, refer to the DC Power Supply
Connection Supplement.
Ground Connection
All PS modules are equipped with a grounding screw on the module panel for
connecting the protective ground.
A-6 Power Connectors Megaplex-4100 Ver. 2.0

Appendix B
Installing New Software
Releases
This Appendix presents procedures for downloading software to the Megaplex-4100.
The procedures appearing in this Appendix can be used to:
1. Update the Megaplex-4100 software when a new release becomes available.
2. Download again the software in case the stored software has been
corrupted.
3. Download software to a new or repaired CL module.
4. Download software to I/O modules that support this capability.
B.1 Overview
Megaplex-4100 operation is controlled by its management subsystem, located on
the CL module, which cooperates with the local management subsystems of the
other modules installed in the chassis. The software needed by the CL module is
stored in flash memory, and therefore can be loaded by external means. This
enables distributing software updates from remote locations, or from PCs used
by technical support and maintenance personnel.
The CL module software also includes the software controlling the Ethernet
traffic handling subsystem (located on CL.1/GbE and CL.1/155GbE modules).
In addition to the CL module software, the current Megaplex-4100 version also
enables downloading software to link modules with E1, T1, SHDSL, and Ethernet
interfaces (for example, M8E1, M8T1, M8SL), and to the SDH/SONET traffic
handling subsystem located on CL.1/155 and CL.1/155GbE modules.
Each of these subsystems can be independently updated, using separate
software image files (these files have the extension .img). The following naming
conventions are generally observed:
• Software files for CL modules (which also includes the Ethernet traffic
handling subsystem software) have the prefix cx.
• Software files for link modules have the prefix ml8e.
• Software files for the SDH/SONET traffic handling subsystem have the prefix
mlx.
Megaplex-4100 Ver. 2.0 Overview B-1

Appendix B Installing New Software Releases Installation and Operation Manual
As a standard, the prefix is followed by a four-digit number that identifies a

specific version (additional letters used for RAD internal purposes may follow the
version number).
The CL module flash memory includes three software storage areas, one for each
type of software image file:
• One area is automatically reserved for the CL module software.
The same software version must be stored in both CL modules: an alarm is
generated if the CL modules hold different software versions.
• The other two areas (identified as File 1 and File 2 on the supervision
terminal screens) can store two independent image files, in accordance with
user’s requirements (for example, each area can hold a different version of
link modules software, or one area can be dedicated to link modules
software, and the other to SDH/SONET software). Moreover, the user can
specify from which area to download software to each module or subsystem.
The contents of these storage areas are not checked for consistency
between the two CL modules.
The File Utilities menu provides the tools necessary to control downloading, and
to manage the stored software files (refer to Chapter 4 for details).
Downloading Options for CL Modules Software

The CL module contains the most critical part of the system software, and
therefore Megaplex-4100 provides two options for downloading software to the
CL modules:
• Using the File Utilities menu
• Using the boot menu.
Using the File Utilities Menu

The recommended software downloading method, explained in Section B.2, is
downloading by means of the TFTP protocol, using SW & File Transfer CL option
of the File Utilities menu.
Network administrators can use this procedure to distribute new software
releases to all the managed Megaplex-4100 units in the network from a central
location.
When downloading by TFTP, the new software is always downloaded into the
on-line CL module, and is stored in its flash memory.
After software decompression is completed, the on-line CL module is
automatically reset. Resetting the on-line CL module has two effects:
• The new software is activated
• The other CL module (which currently stores the previous software version) is
switched on-line.
Therefore, after receiving the messages that indicate flipping (switching) to the
other CL module, repeat the downloading procedure: this time the new software
will be downloaded into the other module. Following the resetting of the second
B-2 Overview Megaplex-4100 Ver. 2.0

Installation and Operation Manual Appendix B Installing New Software Releases
CL module at the end of software downloading, the original CL module returns

on-line.
Using the Boot Menu

Software downloading may also be performed using the boot menu, as explained
in Section B.3. 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 whenever it is not
possible to activate TFTP from the File Utilities menu (for example, because
the Megaplex-4100 software has not yet been downloaded or is corrupted).
Note It is recommended that only authorized personnel use the boot menu
procedures, because this menu provides many additional options that are
intended for use only by technical support personnel.
The boot menu enables downloading two types of files:

• Boot manager files. The boot manager is a critical function that controls the
power-up initialization and ensures that the application program is
automatically run upon power-up. The boot manager also includes several
utilities (some of them are used to download files, as explained in this
Appendix). This type of file is seldom updated.
Downloading a boot manager file should be performed only by technical
support personnel.
• Application files. These files carry the regular version updates. The following
sections provide instructions for downloading application files.
Two software downloading options are available from the boot menu:
• Downloading using the Xmodem protocol. This is usually performed by
downloading from a PC directly connected to the CONTROL DCE port of the CL
module.
• Downloading using the TFTP protocol. This is usually performed by
downloading from a host connected to the CONTROL ETH port of the active
CL module, or from a remote location that provides an IP communication
path to this Megaplex-4100 port.
When downloading from the boot menu, you connect only to one CL module (the
module to be loaded). Therefore, when updating the software to a new release,
always repeat the process for the second module.
Downloading Options for Other Software

The other types of software are downloaded to the CL module using TFTP (using
the File Utilities menu), and stored into the user-specified software storage area.
As for the CL module software, downloading must be separately performed for
each module (preferably starting with the on-line module).
After a software image is stored in the CL module, it can be downloaded to the
desired modules using the SW & File Transfer I/O and S-Subsystem submenu of
the File Utilities menu. As part of the downloading process, the CL module checks
Megaplex-4100 Ver. 2.0 Overview B-3

that the file being downloaded to a specific I/O module or subsystem is a valid
software image file for that target.
B.2 Software Updating Using File Utilities Menu
screens are given for illustration purposes only, and do not reflect recommended
values.
Preparations for Using TFTP

The following conditions must be fulfilled before the TFTP protocol can be used
for software downloading:
1. The required suite of protocols (which includes as a minimum the TCP/IP stack
and the TFTP server and client software) must be installed on the other
computer (the computer used to download files and/or accept uploaded
files).
2. The Megaplex-4100 must be assigned IP parameters for its management
entity (that is, IP address, the associated subnet mask and a default gateway
IP address for the online CL module) using the Configuration>System>
Management>Host IP screen.
3. The management access options must be properly configured.
4. You must obtain the IP address of the other computer.
5. The TFTP protocol runs over IP, therefore it is necessary to ensure IP
connectivity between the Megaplex-4100 and the other computer. For
example:
The Ethernet port of the other computer may be directly connected to
one of the Megaplex-4100 CONTROL ETH ports. In this case, their IP
addresses must be in the same subnet.
The CONTROL ETH port and the other computer may be attached to the
same LAN. In this case, their IP addresses must be in the same subnet.
The Megaplex-4100 and the other computer may be attached to
interconnected LANs.
Note
IP connectivity can be checked using standard tools such as ping.
6. If you intend to initiate TFTP transfer using a supervision terminal connected

to the Megaplex-4100 CONTROL DCE connector, make sure that the
Megaplex-4100 supervisory port is properly configured. This is performed by
means of the Configuration>System>Control Port>Serial Port screen.
Alternatively, you may use a Telnet host that can communicate with the
Megaplex-4100 either through the CONTROL ETH ports, or through the one of
the external links.
B-4 Software Updating Using File Utilities Menu Megaplex-4100 Ver. 2.0
Software Updating Procedure for CL Modules
Before Starting
1. Obtain the list of distribution files to be downloaded, and check that the
required distribution files are stored on the TFTP server. Valid files have the
extension .img, and the prefix depends on the image type (see page B-1).
Note Refer to the Updating the SDH/SONET Subsystem Software section starting on
page B-7 for instructions regarding the updating of the CL module SDH/SONET
subsystem software.
2. Make sure that the TFTP server can communicate with the Megaplex-4100,
for example, by sending pings to the IP address assigned to the
Megaplex-4100 management entity (the host IP address).
Updating the CL Management Software

The following procedure is separately performed on each CL module, starting with
the on-line module.
Note The following procedure also updates the Ethernet subsystem software of
CL.1/GbE and CL.1/155GbE modules.

MP-4100
File Utilities
1. S/W & File Transfer CL >

2. S/W & File Transfer I/O & S-Subsystem >
>
File system and File transfer operations

-----------------------------------------------------------------------------
2. Select S/W & File Transfer CL on the File Utilities menu. You will see the S/W
& File Transfer CL submenu.
Megaplex-4100 Ver. 2.0 Software Updating Using File Utilities Menu B-5
MP-4100
File Utilities>S/W & File Transfer CL
1. TFTP >
>
File Transfer operations

-----------------------------------------------------------------------------
3. On the S/W & File Transfer CL screen, select TFTP to display the TFTP screen.
Initially, the screen includes only the File Name and Server IP items.
4. On the TFTP screen, select each of the items to define the parameters
Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). Usually, a CL
module image file name starts with cx (see page B-1). When done, press
Select Server IP, and enter the IP address of the server that will download
After the previous two items are configured, a third item, Command,
appears, together with a TFTP State field that displays the state of the
TFTP operations. Initially, this field displays NoOp (no operation).
MP-4100
File Utilities>S/W & File Transfer CL>TFTP
TFTP State > (NoOp)

1. File Name ... (cx150.img)
2. Server IP ... (172.17.65.12)
3. Command >
>
TFTP operations
-----------------------------------------------------------------------------
Select the Command item to display the Command task selection screen.
MP-4100
File Utilities>S/W & File Transfer CL>TFTP>Command
1. SW Download
2. Config Download
3. Config Upload
4. No Command
>

-----------------------------------------------------------------------------
5. On the Command screen, select SW Download, to start the software

downloading.
again the SW Download command.
file in its flash memory. Now the Megaplex-4100 is automatically reset and
the new software is decompressed. After the resetting is successfully
completed, you will see the Megaplex-4100 log in screen again.

In the User Name field, type the default user name, su, and then press
<Enter>
In the Password field, type the default, 1234, and then press <Enter>.
8. You will see the main menu screen. The Megaplex-4100 now uses the
9. Repeat the transfer to download the same file to the other CL module. For
this purpose, first switch the other CL module on-line (use
Config>System>Reset Device to send a reset command to the on-line
module).
Updating the SDH/SONET Subsystem Software

To update the SDH/SONET subsystem software, first download the required
software image to a selected software storage area of each CL module, and then
download the stored software image to the SDH/SONET subsystem of each CL
module.
This procedure must be separately performed on each CL.1/155 or CL.1/155GbE

module.
After the software is successfully downloaded to the SDH/SONET subsystem, that
subsystem is automatically reset, and then starts using the new software version.
This process momentarily disrupts the traffic flowing through the SDH/SONET
subsystem that is being updated (if this subsystem provides the Megaplex-4100
nodal timing reference, flipping to another timing reference may also occur).
You can minimize traffic disruptions as a result of SDH/SONET software updating
by taking the following steps:
• Whenever possible, download and store the updated SDH/SONET software in
the CL modules before updating the SDH/SONET subsystems
• Whenever possible, first change the Megaplex-4100 nodal timing reference
before updating the software of an SDH/SONET subsystem that provides the
nodal timing reference
• Whenever APS groups are configured between the identical links of the two
SDH/SONET subsystems, first switch the traffic to the other subsystem
before updating the software of the on-line subsystem.
For the same reason, if path protection is configured, first switch the
low-order paths to their protection paths on the other subsystem, even when
APS is not used.
³ To download the SDH/SONET software image to a CL module:

menu.
You will see the S/W & File Transfer I/O and S-Subsystem submenu.
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem
1. TFTP >
2. Download To Cards >
3. Download Status >
4. Dir >
5. Delete File >
>

-----------------------------------------------------------------------------
3. On the S/W & File Transfer I/O and S-Subsystem submenu, select TFTP to
display the TFTP screen. Initially, the screen includes only the File Name,
Server IP, and File # items.
4. On the TFTP screen, select each of the items to define the parameters
Select File Name, and enter the name of the desired software distribution
file (make sure to include the path, when necessary). Usually, an
SDH/SONET subsystem image file name starts with mlx (see page B-1).
When done, press <Enter> to continue.
Select Server IP, and enter the IP address of the server that will download
Select File # to open the storage area selection screen for the current CL
module. Select the desired storage area, File-1 or File-2, and then
After the previous items are configured, a fourth item, S/W Download (To
Flash), appears, together with a TFTP State field that displays the state of
the TFTP operations. Initially, this field displays NoOp (no operation).
MP-4100
File Utilities>S/W & File Transfer I/O & S-Subsystem>TFTP
Tftp State > (NoOp)

1. File Name ... (mlx150.img)
2. Server IP ... (172.171.55.75)
3. File # > (File-1)
4. S/W Download (To Flash)
>

-----------------------------------------------------------------------------
5. On the TFTP screen, select SW Download (To Flash), to start the software
downloading.
again SW Download (To Flash).
file in the selected storage area of its flash memory.
7. Repeat the transfer to download the same file to the other CL module. For
module).
³ To load a software image to an SDH/SONET subsystem:

menu.
Cards to display the downloading target selection screen.
MP-4100

>

-----------------------------------------------------------------------------
4. On the Download to Cards screen, select the desired target (S-Subsystem

CL-A or S-Subsystem CL-B), in accordance with the on-line CL module, and
then press <Enter> to open the source storage area selection screen.
5. Select the storage area (File-1 or File-2) that stores the desired file, and then
press <Enter>.
& S-Subsystem>Dir to find it.
6. At this stage, an additional item, SW Download, appears on the Download to

Cards screen. Select SW Download to start the software downloading.
to display the progress. If you see an error message, check and correct
the error cause, and then select again the SW Download command.
7. After the transfer is successfully completed, the SDH/SONET subsystem is
automatically reset and the new software is decompressed. After the
resetting is successfully completed, the SDH/SONET subsystem is again ready
to carry traffic.
8. If necessary, repeat the procedure for the other SDH/SONET subsystem. For
module).
Software Updating Procedure for I/O Modules

To update the software of I/O modules that have this capability, first download
the required software image to a selected software storage area of the CL
module, and then download the stored software image to each I/O module.
A single CL module (the on-line module) can download software to any number
of I/O modules. Therefore, it is not mandatory to download I/O modules software
to both CL modules.
Moreover, the CL module can be configured to download the software to the
desired modules in one step (the downloading itself is sequentially performed).
After the software is successfully downloaded to an I/O module, that module is
automatically reset, and then starts using the new software version. This process
momentarily disrupts the traffic flowing through the module that is being
updated (if this module provides the Megaplex-4100 nodal timing reference,
flipping to another timing reference may also occur).
You can minimize traffic disruptions as a result of software updating by taking
the following steps:
• Whenever possible, first change the Megaplex-4100 nodal timing reference
before updating the software of an I/O module that provides the nodal timing
reference
• Whenever redundancy is configured between the ports of two different
modules, first switch the traffic to the other module before updating the
software of the on-line module.
For the same reason, if path protection is configured, first switch the
low-order paths to their protection paths.
³ To download an I/O module image to a CL module:

Use the procedure described in the Updating the SDH/SONET Subsystem Software
section starting on page B-7.
³ To load a software image to an I/O module:

menu.
Cards to display the downloading target selection screen.
MP-4100

>

-----------------------------------------------------------------------------
4. On the Download to Cards screen, select the desired target, and then press
<Enter> to open the source storage area selection screen.
5. Select the storage area (File-1 or File-2) that stores the desired file, and then
press <Enter>.
& S-Subsystem>Dir to find it.
6. Repeat Steps 4, 5 for each I/O module, as necessary, or continue to Step 7.

7. After Step 5, an additional item, SW Download, appears on the Download to
Cards screen. When ready to start the software downloading, select SW
Download.
to display the progress. If you see an error message, check and correct
the error cause, and then select again the SW Download command.
8. After the transfer is successfully completed, the I/O module is automatically
reset and the new software is decompressed. After the resetting is
successfully completed, the module is again ready to carry traffic.
B-12 Software Downloading From the Boot Menu Megaplex-4100 Ver. 2.0
B.3 Software Downloading From the Boot Menu
Software Downloading Procedure Using Xmodem Protocol

Before starting, copy the prescribed software file to the PC disk.
Preparations for Using Xmodem Protocol

1. Connect the serial RS-232 communication port of a PC running a terminal
emulation program (for example, the HyperTerminal utility available with most
Microsoft Inc. Windows™ releases) to the Megaplex-4100 CONTROL DCE
connector. Select the emulated terminal type as VT-100.
2. Configure the communication parameters of the selected serial port for
asynchronous communication for 115.2 kbps, no parity, one start bit, eight
data bits and one stop bit. Turn flow control off.
3. If the Megaplex-4100 operates, disconnect its power.
Procedure
1. Start the terminal emulation program in accordance with the configuration
parameters described above.
2. When ready, turn the Megaplex-4100 on, and immediately start pressing the
<Enter> key many times in sequence until you see the boot manager screen.
A typical screen is shown below (the exact version and date displayed by your
Megaplex-4100 may be different).
Note If you miss the timing, the Megaplex-4100 will perform a regular reboot process
(this process starts with Loading and ends with a Running message).
MPCLX boot version 2.00 (Jun 5 2005)

Boot manager version 10.00 (Jun 5 2005)
0 - Exit boot-manager
1 - Dir
2 - Set active software copy
3 - Delete software copy
4 - Download boot manager or an application by XMODEM
5 - Format Flash
6 - Show basic hardware information
7 - Reset board
8 - System configuration
9 - Download boot manager or an application by TFTP
Press the ESC key to return to the main menu
Select:
3. Select Download boot manager or an application by XMODEM. You are now

prompted to select the type of file to be downloaded.
Megaplex-4100 Ver. 2.0 Software Downloading From the Boot Menu B-13
Choose the software you want to work on

0 - boot-manager
1 - application file
Select: 1
4. Type 1 to download a Megaplex-4100 software update.

5. You will see a message that requests the partition number to which the new
software is to be downloaded, and offers a recommended value. If there is
no special reason to select a different value, type the recommended number
and then press <Enter>. A typical display is shown below:
Select Copy number for download ( 1 )
Select: 1
6. The process starts, and you will see:

Erasing Partition please wait ....
Please start the XMODEM download.
7. Start the transfer in accordance with the program you are using. For example,
if you are using the Windows HyperTerminal utility:
Select Transfer in the HyperTerminal menu bar, and then select Send File
on the Transfer menu.
You will see the Send File window:
Select the prescribed Megaplex-4100 software file name (you may
use the Browse function to find it). Usually, a CL module image file
name starts with cx (see page B-1).
In the Protocol field, select Xmodem.
When ready, press Send in the Send File window. You can now monitor
the progress of the downloading in the Send File window. The ON LINE
indicator of the CL module flashes in green during the downloading.
Note If downloading fails, repeat the whole procedure.
8. When the downloading process is successfully completed, you will see a

sequence of messages similar to the following, while the new software is
decompressed (during this process, the ON LINE indicator flashes in yellow).
Loading ...
Decompressing to RAM.
Processing archive: FLASH

Extracting MPCLX.BIN
..........................................................
.................................................................... CRC OK
Running ...
*******************************************************************
* In order to start working - press the ENTER button for few times*
*******************************************************************
9. At this stage, press <Enter> several times in sequence to display the

Megaplex-4100 log-in screen.
<Enter>
11. You will see the main menu screen. Megaplex-4100 now uses the
12. Repeat the transfer to download the file to the other CL module. For this
purpose, you must connect to the CONTROL DCE connector of the other
module.
Software Downloading Procedure Using TFTP Protocol
Preparations for Using TFTP Protocol:

The preparations needed for using the TFTP protocol from the boot menu are
similar to the preparations needed to download software from the File Utilities
menu (see Preparations for Using TFTP section on page B-4), except that you
must connect to the CONTROL ETH connector of the desired CL module.
The main difference is that you need to define the IP communication parameters
for the corresponding CL module (IP addresses and the associated subnet mask,
and a default gateway IP address).
Note The IP parameters used for TFTP transfers from the boot menu should be
different from those you intend to use during normal operation.
³ To define management IP parameters from the boot menu:

1. Connect the Ethernet cable from the TFTP server to the CONTROL ETH
connector of the desired Megaplex-4100 CL module.
2. Use the procedure described on page B-13 to display the boot menu.
Note
The exact versions and dates displayed by your Megaplex-4100 may be different
from the example below.

1 - Dir
5 - Format Flash
7 - Reset board
Select: 8
IP Address [172.17.171.139]: 168.119.10.101

IP Mask [255.255.255.0]: 255.255.255.0
Default Gateway Address [172.17.171.1]: 168.119.10.1
3. Select 8: System Configuration to start the configuration of the CL module IP

communication parameters, as needed for the TFTP transfer.
4. The parameters are displayed in consecutive lines. For each parameter, you
can accept the current values by simply pressing <Enter> to continue, or type
a new value:
IP Address: used to select the IP address of the CL module. To change the
current value, type the desired IP address in the dotted quad format, and
then press <Enter> to continue.
IP Mask: used to select the IP subnet mask of the CL module. To change
the current value, type the IP subnet mask address in the dotted quad
format, and then press <Enter> to continue.
Default Gateway Address: when the TFTP server is located on a different
LAN, you must define the IP address of the default gateway to be used
by the CL module. Make sure to select an IP address within the subnet of
the assigned CL module IP address. To change the current value, type the
desired IP address in the dotted quad format, and then <Enter> to end
the configuration.
If no default gateway is needed, for example, because the TFTP server is
attached to the same LAN as the CL module being loaded, enter 0.0.0.0.
5. After pressing <Enter>, you will see again the boot menu.
6. Select Reset board to reset the CL module. The new parameters take effect
only after the resetting is completed.
Downloading Procedure
³ To download software from the boot menu using TFTP:

1. On the boot menu, select Download boot manager or an application by TFTP
and then press <Enter> to start the TFTP transfer.
2. You will see Enter TFTP timeout in case of failure, followed by the current
default time-out value (in seconds):
To select the default, press <Enter>
To change, type the desired time-out and then press <Enter>.
3. After you see Enter the Target File Name, enter the name of the desired
software distribution file (make sure to include the path, when necessary).
When done, press <Enter> to continue.
4. You will see Enter the Server IP address: enter the IP address of the server
that will download the software distribution file, using the dotted quad
format, and then press <Enter> to continue.
1 - Dir
5 - Format Flash
7 - Reset board
Select:9
Enter TFTP timeout in case of failure [20 sec]: 40
Enter the target file name [MP4100.img]:
Enter the server IP address [172.17.174.50]:
5. You are now prompted to select the type of file to be downloaded.

Select Application File to download a Megaplex-4100 software update.
Choose the software you want to work on
0 - boot-manager
1 - application file
Select: 1
6. If no errors are detected, the downloading process starts.

7. After the transfer is successfully completed, return to the boot menu and
select Exit Boot-Manager.
8. After the Megaplex-4100 initialization is ended, the CL module loads the new
software and the new software is decompressed
9. At this stage, press <Enter> several times in sequence to display the

Megaplex-4100 log-in screen.
<Enter>
11. You will see the main menu screen.
12. If necessary, repeat the process for the second CL module.
Appendix C
Operating Environment
C.1 Overview
This Appendix presents a concise description of the Megaplex-4100 operating
environment, to provide the background information required for understanding
the Megaplex-4100 configuration and performance monitoring parameters.
This Appendix covers the following issues:
• PDH environment – Section C.2
• SHDSL environment – Section C.3
• SDH environment – Sections C.4 through C.8
• SONET Environment – Section C.9
• Ethernet transmission technology – Section C.10
• IP environment – Section C.12
• Management using SNMP – Section C.13
C.2 PDH Environment
Scope
This section presents information on the main characteristics of the
Plesiochronous Digital Hierarchy (PDH) signals. Table C-1 shows the PDH
multiplexing hierarchies used in the main geographical areas.
Table C-1. PDH Multiplexing Hierarchy
Multiplex Level Europe North America (USA) Japan
1 E1 – 2.048 Mbps DS1 – 1.544 Mbps JT1 – 1.544 Mbps
2 E2 – 8.448 Mbps DS2 – 6.312 Mbps 6.312 Mbps
3 E3 – 34.368 Mbps DS3 – 44.736 Mbps 32.064 Mbps
4 E4 – 139.264 Mbps DS4NA – 139.264 Mbps 97.729 Mbps
Megaplex-4100 Ver. 2.0 PDH Environment C-1

Appendix C Operating Environment Installation and Operation Manual
E1 Environment
E1 Line Signal Characteristics

E1 signal characteristics are specified in ITU-T Rec. G.703. The nominal data rate
of the E1 signal is 2.048 Mbps. The E1 line signal is encoded in the High-Density
Bipolar 3 (HDB3) code.
HDB3 is based on the alternate mark inversion (AMI) code. In the AMI code, “1”s
are alternately transmitted as positive and negative pulses, whereas “0”s are
transmitted as a zero voltage level. To prevent the transmission of long strings of
“0”s, which do not carry timing information, the HDB3 coding rules restrict the
maximum length of a “0” string that can be transmitted through the line to three
pulse intervals. Longer strings of “0”s are encoded at the transmit end to
introduce non-zero pulses.
To allow the receiving end to detect the artificially-introduced pulses and enable
their removal to restore the original data string, the encoding introduces
intentional coding violations in the sequence transmitted to the line. The
receiving end detects these violations and when they appear to be part of an
encoded “0” string – it removes them.
Coding violations may also be caused by transmission errors. Therefore, any
coding violations that cannot be interpreted as intentional coding violations can
be counted, to obtain information on the quality of the transmission link.
E1 Signal Structure
The E1 line operates at a nominal rate of 2.048 Mbps. The data transferred over
the E1 line is organized in frames. Each E1 frame includes 256 bits.
The E1 frame format, as defined in ITU-T Rec. G.704, is shown in Figure C-1.
Time Slot 0 Time Slot 16 Time Slots 1-15, 17-31
a. Even Frames (0,2,4-14) a. Frame 0

8 Bits per
Time Slot 1 0 0 1 1 0 1 1 0 0 0 0 X Y X X
FAS MAS
Channel Data
b. Odd Frames (1,3,5-15) b. Frames 1-15
I 1 A N N N N N A B C D A B C D 1 2 3 4 5 6 7 8
TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS TS
32 Time Slots/Frame 0 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
FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR FR
16 Frames/Multiframe 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Notes
I International Bit ABCD ABCD Signaling Bits
N National Bits (Sa4 through Sa8) X Extra Bit
A Alarm Indication Signal (Loss of Frame Alignment - Red Alarm) Y Loss of Multiframe Alignment
FAS Frame Alignment Signal, occupies alternate MAS Multiframe Alignment Signal
(but not necessarily even) frames
Figure C-1. E1 Frame Format

The 256 bits included in a frame are organized of 32 timeslots of eight bits each.
The frame repetition rate is 8,000 per second, therefore the data rate supported
by each timeslot is 64 kbps.
C-2 PDH Environment Megaplex-4100 Ver. 2.0

Installation and Operation Manual Appendix C Operating Environment
Timeslot 0
Timeslot 0 of E1 frames is used for two main purposes:
• Delineation of frame boundaries. For this purpose, in every second frame,
timeslot 0 carries a fixed pattern, called frame alignment signal (FAS). Frames
carrying the FAS are defined as even frames, because they are assigned the
numbers 0, 2, 4, etc. when larger structures (multiframes) are used.
The receiving equipment searches for the fixed FAS pattern in the data
stream using a special algorithm, a process called frame synchronization.
Once this process is successfully completed, the equipment can identify each
bit in the received frames.
• Interchange of housekeeping information. In every frame without FAS (odd
frames), timeslot 0 carries housekeeping information. This information is
carried as follows:
Bit 1 – this bit is called the international (I) bit. Its main use is for error
detection using the optional CRC-4 function (CRC-4 stands for Cyclic
Redundancy Check, using a fourth-degree polynomial). This function is
described below.
Bit 2 is always set to 1, a fact used by the frame alignment algorithm.
Bit 3 is used as a remote alarm indication (RAI), to notify the equipment
at the other end that the local equipment lost frame alignment, or does
not receive an input signal.
The other bits, identified as Sa4 through Sa8, are designated national
bits, and are actually available to the users, provided agreement is
reached as to their use. RAD equipment with SNMP agents can use the Sa
bits for inband management traffic. The total data rate that can be
carried by each national bit is 4 kbps.
Multiframes
To increase the information carrying capacity without wasting bandwidth, the
frames are organized in larger patterns, called multiframes. ITU-T Rec. G.704
recommendation defines the following types of multiframes:
• Basic G.704 framing
• G.704 framing with timeslot 16 multiframe.
Basic G.704 Framing

The basic G.704 multiframe structure consists of two frames, which are identified
by means of the information included in timeslot 0:
• The even frame of the pair includes the frame alignment signal (FAS).
• The odd frame includes an 1 in bit position 2, and housekeeping information
in the other bits.
The number of timeslots available for user’s data is 31, and therefore the
maximum payload rate is 1984 kbps.

To enable the transmission of network management information, a separate

timeslot may have to be assigned within the frame. This procedure is called
common channel signaling (CCS). The CCS information is often transmitted in
timeslot 16.
G.704 Framing with Timeslot 16 Multiframe (“G.704 Multiframe”)

The G.704 multiframe structure includes 16 frames, which are identified by means of
a separate multiframe alignment signal (MAS) contained in timeslot 16 of each
frame.
The G.704 multiframe structure is generally used when timeslot 16 serves for the
end-to-end transmission of channel-associated signaling (CAS). A typical
application in which timeslot 16 serves for the transmission of signaling is the
transfer of voice channels by means of voice modules, using the standard E1 PCM
format based on channel-associated signaling.
Since timeslot 16 must be reserved for the transmission of the MAS and system
signaling, only 30 timeslots are available for the user’s payload, and the maximum
payload rate is 1920 kbps.
When using the G.704 multiframe format, timeslot 16 of each of the 16 frames in
each multiframe carry the following information:
• The first four bits of timeslot 16 in multiframe 16 always carry the multiframe
alignment sequence, 0000.
• Bit 6 in timeslot 16 in multiframe 16 is used to notify the equipment at the
other end of the link that the local equipment lost multiframe alignment.
• The other bits of this timeslot are not assigned mandatory functions.
Channel Associated Signaling

When using the G.704 multiframe format, timeslots 16 in frames 1 through 15 of
each multiframe are available for carrying user’s information. In general, this
information is the signaling information for the 30 payload timeslots (channels).
As shown in Figure C-1, four signaling bits, designated A, B, C, and D, are
available for each channel, thereby enabling end-to-end transmission of four
signaling states. Note that each frame in the multiframe carries the signaling
information of two channels.
CRC-4 Error Detection

The Megaplex-4100 system supports the CRC-4 function in accordance with ITU-T
Rec. G.704 and G.706. The CRC-4 function is used to detect errors in the received
data, and therefore can be used to evaluate data transmission quality over E1
links.
This function can be enabled or disabled by the user, independently for each link.
To enable error detection, additional information must be provided to the
receiving equipment. The additional information is transmitted to the receiving
equipment by using a multiframe structure called CRC-4 multiframes. A CRC-4
multiframe is an arbitrary group of 16 frames. This group is not related in any
way to the G.704 16-frame multiframe structures explained above.

• A CRC-4 multiframe always starts with an even frame (a frame that carries
the frame alignment signal). The CRC-4 multiframe structure is identified by a
six-bit CRC-4 multiframe alignment signal, which is multiplexed into bit 1 of
timeslot 0 of each odd-numbered (1, 3, 5, etc.) frame of the CRC-4
multiframe (i.e., in frames 1 through 11 of the CRC-4 multiframe).
• Each CRC-4 multiframe is divided into two submultiframes of 8 frames (2048
bits) each. The detection of errors is achieved by calculating a four-bit
checksum on each 2048-bit block (submultiframe). The four checksum bits
calculated on a given submultiframe are multiplexed, bit by bit, in bit 1 of
timeslot 0 of each even-numbered frame of the next submultiframe.
• At the receiving end, the checksum is calculated again on each submultiframe
and then compared against the original checksum (sent by the transmitting
end in the next submultiframe). The results are reported by two bits
multiplexed in bit 1 of timeslot 0 in frames 13, 15 of the CRC-4 multiframe,
respectively. Errors are counted and used to prepare statistic data on
transmission performance.
E1 Line Alarm Conditions

• Excessive bit error rate. The bit error rate is measured on the frame
-3
alignment signal. The alarm threshold is an error rate higher than 10 that
persists for 4 to 5 seconds. The alarm condition is canceled when the error
-4
rate decreases below 10 for 4 to 5 consecutive seconds.
• Loss of frame alignment (also called loss of synchronization) . This condition
is declared when too many errors are detected in the frame alignment signal
(FAS), e.g., when 3 or 4 FAS errors are detected in the last 5 frames. Loss of
frame alignment is cleared after no FAS errors are detected in two
consecutive frames.
The loss of frame alignment is reported by means of the A bit (Figure C-1).
• Loss of multiframe alignment (applicable only when the G.704 multiframe
structure is used) . This condition is declared when too many errors are
detected in the multiframe alignment signal (MAS) (same conditions as for
loss of frame alignment).
The loss of multiframe alignment is reported by means of the Y bit
(Figure C-1).
• Alarm indication signal (AIS) . The AIS signal is an unframed “all-ones” signal,
and is used to maintain line signal synchronization in case of loss of input
signal, e.g., because an alarm condition occurred in the equipment that
supplies the line signal. Note that the equipment receiving an AIS signal loses
frame synchronization.
T1 Environment
T1 Line Signal
The basic T1 line signal is coded using the alternate mark inversion (AMI) rules,
explained in Section C.2.

The AMI format cannot transmit long strings of “zeros”, because such strings do
not carry timing information. Therefore, the AMI signal source must generate a
signal with guaranteed minimum “1” density. The minimum average “1” density
required by the applicable standards is 1:8.
Therefore, when a T1 signal is transmitted over an AMI line, each frame timeslot
must include at least one “1” bit. This effectively reduces user data rate to
56 kbps per timeslot, and precludes the provision of clear channel capability
(CCC).
To circumvent this problem, modified line codes are used, that perform zero
suppression by substituting special codes for long “0” strings. The generally
accepted zero suppression methods are B7 and B8ZS.
• With B7, the maximum length of “0” strings in the user data must not exceed
seven zeros (when a longer string is detected, the seventh bit is changed to
“one”, to meet the minimum “1” density requirement and thus ensure that
the remote end can properly recover the clock signal). Although this
requirement can be fulfilled in many applications, it does not provide 64 kbps
clear channel capability. Therefore, when the B7 line code is used, inband
management is not supported.
• Only the B8ZS zero suppression method provides clear channel capability, and
the “1” density requirement no longer restricts user data characteristics. This
means that each T1 frame timeslot can support the full 64 kbps.
Since the AMI coding does not affect the signal transmitted to the line, it is also
called transparent coding. This emphasizes the fact that although the other methods
are also transparent to user’s data, perfect transparency is achieved only when the
zero-string substitution sequences are correctly recognized. Thus, the other methods
are more sensitive to transmission errors (transmission errors may affect the
decoding of zero-string substitution sequences).
T1 Signal Structure
The T1 line operates at a nominal rate of 1.544 Mbps. The data transferred over
the T1 line is organized in frames.
The T1 frame format is shown in Figure C-2.
8 Other Frames Bit B Conveys
Byte Organization 8 Bits/Channel 1 2 3 4 5 6 7 A Frame 6 Signaling
(D4 Frame - See NOTE) B Frame 12 Information
Frame 24 Channels/Frame Ft CH CH CH CH
Organization Frame = 193 Bits or
1 2 13 24
Fs
Multiframe
Organization FR FR FR FR FR
1 2 7 11 12
Multiframe
SF (D4) 12 Frames
NOTE: ESF: 24 Frames
In addition, ESF has a C-bit in frame 18 and a D-bit in frame 24
Figure C-2. T1 Frame Format

Each T1 frame includes 193 bits. 192 bits are organized in 24 timeslots of eight
bits each, that carry the payload data. An additional timeslot, including one bit
(the F-bit) carries framing and supervision information. As a result, the data rate
supported by each payload timeslot is 64 kbps. The data rate of the framing slot
is 8 kbps.
The T1 frame does not include a dedicated timeslot for the transfer of channel
signaling. When end-to-end transfer of signaling is necessary, a technique called
“robbed-bit signaling” is used. The robbed-bit is the least significant bit (bit 8) of
the channel byte, and is actually “robbed” only once in every six frames.
In order to enhance link/system supervision capabilities, the frames are organized
in larger patterns, called super-frames. Two types of super-frames are used:
• SF (also called D4), consists of 12 T1 frames.
• Extended SF (ESF), consists of 24 T1 frames.
The SF format provides limited supervision capabilities, such as end-to-end
reporting of local loss-of-signal (yellow alarm), and line loopback.
The ESF format provides improved supervision capabilities, and allows better
utilization of the 8 kbps framing timeslots. The major advantage of the ESF
format is that it supports on-line link performance monitoring (by means of a
2 kbps Cyclic Redundancy Check (CRC) channel) and in addition provides a 4 kbps
end-to-end supervision and control data link. The data link can be used for
performance monitoring and failure reporting, for activation of maintenance
loopbacks, and for transmission of various commands to the far end equipment.
The implementation of the multiframing format is based on the use of various
F-bit patterns. The F-bit pattern is used to perform three functions:
• Framing Pattern Sequence (FPS), defines frame and multiframe boundaries.
• Facility Data Link (FDL), allows transfer of supervisory data, e.g. alarms, error
performance, test loop commands, etc. to be passed through the T1 link.
Note
RAD equipment with SNMP agents can use the FDL to carry inband management
traffic. The management data rate is then 4 kbps.
• Cyclic Redundancy Check (CRC), allows the measurement of the bit error rate
and enhances the reliability of the framing algorithm.
The F-bit pattern defines the structure of frames and multiframes. In the D4 (SF)
frame format, the F-bit of consecutive frames is alternately interpreted as an
Ft bit (terminal framing bit) or Fs bit (frame signaling bit).
• Ft pattern: alternating 0's and 1's, defines the frame boundaries.
• Fs pattern: fixed 001110 pattern, defines the multiframe boundaries, so that

one frame may be distinguished from another. In particular, the Fs pattern is
needed so that frames 6 and 12 may be identified for the recovery of
signaling bits.
In the ESF frame format, the multiframe structure is extended to 24 frames, but
the frame and channel structure are the same as in the D4 (SF) format.

T1 Alarm Conditions
The basic alarm conditions are the red alarm and the yellow alarm. Note that with
the ESF format, the FDL link can be used for more sophisticated status
transmissions, in accordance with the ANSI Standard T1.403-1989 and AT&T
Pub. 54016.
• Red Alarm. A red alarm is generated when the local unit has lost frame
synchronization for more than 2.5 consecutive seconds, or the bit error rate
-2
exceeds 10 for 2.5 consecutive seconds. Loss of frame synchronization may
be caused either by Fs or Ft errors, by the reception of an AIS signal, or by
the loss of the input signal (receive data remains zero for 31 consecutive
bits). In accordance with AT&T TR-62411, a system automatically recovers
synchronization when there has been a period of 10 to 20 consecutive
seconds free of the loss of sync condition.
Since in many system applications this is a overly conservative specification,
the Megaplex-4100 system offers faster frame synchronization algorithms,
which allow the user to select a “fast” mode. In the “fast” mode, the time
necessary to declare synchronization is reduced to approximately one second
free of the loss of sync condition.
• Yellow Alarm. A yellow alarm is sent from the remote unit to inform the
local unit that a red alarm exists at the remote end.
• Alarm Indication Signal (AIS) . The AIS signal is an unframed “all-ones”
signal, and is used to maintain line signal synchronization when an alarm
condition occurs in the equipment that supplies the line signal.
C.3 SHDSL Environment
Overview
Many DSL technologies have been developed in the recent years. Their purpose it
to enable using the wide installed base of copper (twisted pair) cables laid by the
telephone companies to provide the ubiquitous phone service (plain old
telephone service – POTS) for high-speed digital transmission.
One of these DSL technologies is the single-pair high-speed digital subscriber line
(SHDSL) technology, which supports symmetrical transmission rates of up to
2.312 Mbps. SHDSL has been standardized in ITU-T Rec. G.991.2.
The SHDSL technology covers ranges up to a few km over typical unloaded
twisted pairs.
SHDSL standards describe two types of transmission systems:
• 2-wire (2W) SHDSL system – uses a single unloaded twisted pair.
• 4-wire (4W) SHDSL system – uses two unloaded twisted pairs, and distributes
the payload among the two pairs using the same modulation methods as the
2W system. The 4W system has longer range, because it operates at lower
line rates.
C-8 SHDSL Environment Megaplex-4100 Ver. 2.0

This section presents only the 2W system, which is the system used by
Megaplex-4100 modules.
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’s side, on
the customer’s premises (CPE).
SHDSL Modulation Method

SHDSL uses multi-level pulse-amplitude modulation (PAM) together with trellis
coding. Using advanced digital signal processing (DSP) techniques enables
symmetric data transmission at rates in the range of 192 to 2304 kbps
(corresponding to lines rates of 200 to 2312 kbps). The modulation method is
spectrally compatible with other transmission technologies deployed in the
access network, including other DSL technologies.
The Megaplex-4100 SHDSL subsystem can be configured to ensure compatibility
with regional standards, ITU-T Rec. G.991.2 specifies three sets of regional signal
characteristics for SHDSL modems, however only two of the sets are currently
offered for the Megaplex-4100:
• The set of characteristics specified in Annex A is required for compatibility in
North American networks
• The set of characteristics specified in Annex B is required for compatibility in
European networks.
SHDSL Signal Structure

The SHDSL line signal is organized in frames. The line signal structure enables the
transmission of both payload and overhead data. The main types of overhead
data are:
• Synchronization word, for frame alignment.
• Error detection and correction data, also used for performance monitoring
data.
• Embedded operations channel (eoc) - enables supervision and management
of the whole SHDSL transmission subsystem (STU-C and STU-R), and initiation
of diagnostic loopbacks and tests.
The transmit SHDSL data stream is generated by a framer, which also
demultiplexes the received data stream.
Megaplex-4100 Ver. 2.0 SHDSL Environment C-9

SHDSL Line Transmission Process

The SHDSL line transmission process includes two stages: start-up and data
transmission.
To enable link establishment under various conditions, the SHDSL subsystem
operates in a master-slave mode, where the STU-C unit serves as the master, and
the STU-R unit is the slave.
The STU-C unit performs the following functions:
• Controls the link start-up procedure.
• Provides the timing reference for SHDSL transmission.
• Manages the communication on the eoc channel.
The start-up process is automatically initiated by the STU-C upon power-up, and
uses advanced digital signal processing techniques together with a special link
activation process. It includes the following sequence of operations:
• Link activation. This process has three main steps:
Analysis of line transmission characteristics (line probing) whenever a link
must be setup between two SHDSL modems.
Exchange of transmission parameters (handshaking) between the two
modems.
Note As a user-configurable option, it is possible to include in the link activation

process a data rate negotiation stage, which attempts to set up the link at the
highest rate possible (the maximum allowed rate is selected by the user, as part
of the link configuration parameters).
Transmission of special signals that enable training of echo cancellers and

equalizers, and the synchronization of SHDSL receivers to transmitters in
both directions of transmission.
• Automatic detection and compensation of tip/ring polarity reversal on the
line.
After start-up, the SHDSL links support transmission of payload, as well as an
eoc. Data transmission is automatically started after start-up is successfully
completed.
The total overhead carried by an SHDSL signal is always 8 kbps. For example:
• When the payload data rate is 192 kbps (3 × 64 kbps), the line rate is 200 kbps
• When the payload data rate is 2304 kbps (36 × 64 kbps), the line rate is
2312 kbps.
Note A lower link rate increases the maximum range, therefore when the link cannot
be set up at the requested rate, try selecting a lower rate.
C-10 SHDSL Environment Megaplex-4100 Ver. 2.0

C.4 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.
Basic SDH Principles

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.
2. 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 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.
Megaplex-4100 Ver. 2.0 SDH Implementation Principles C-11

This overhead permits the integration of the network management and

maintenance functions within the transport network itself.
General Structure of SDH Signals

The SDH signal is a serial signal stream with a frame structure. Figure C-3 shows
the general structure of SDH signals.
N x M Bytes
Order of
Transmission
F F F F
F B B
B B B
N x M Bytes 1
N Rows
2
Order of
Transmission
B B B
M Columns
Legend
B Signal Byte
F Framing Byte
Figure C-3. 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.
The frame bytes are transmitted bit by bit, sequentially, starting with those in the
first row (see arrow in Figure C-3). 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.
C-12 SDH Implementation Principles Megaplex-4100 Ver. 2.0

SDH Frame Organization

As shown in Figure C-4, an SDH frame comprises two distinct parts:
• Section Overhead (SOH)
• Virtual Container (VC).
F F F F
Path Overhead (One Column)

Section
Virtual Container
N Rows Overhead
(VC)
M Columns
Figure C-4. 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
Megaplex-4100 Ver. 2.0 SDH Implementation Principles C-13

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
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.
C-14 SDH Implementation Principles Megaplex-4100 Ver. 2.0

C.5 STM-1 Frame Structure

Megaplex-4100 handles the base-level SDH signal, which is called Synchronous
Transport Mode Level 1 (STM-1).
Description of STM-1 Frame

Figure C-5 shows the STM-1 frame structure.
2430 Bytes/Frame
Serial Signal
Stream
F F F F
155.52 Mbps
Path Overhead (9 Bytes)

STM-1 Virtual Container (VC-4)
Section
9 Rows Overhead
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 C-5. STM-1 Frame Structure

STM-1 frames are transmitted at a fixed rate of 8000 frames per second.
Note At a transmission rate of 8000 frames per second, each byte supports a data rate
of 64 kbps.
The STM-1 signal frame comprises 9 rows by 270 columns, resulting in a total
signal capacity of 2430 bytes (19440 bits per frame). Considering the STM-1
frame repetition rate, 8000 frames per second, this yields a bit rate of
155.520 Mbps.
The STM-1 frame comprises the following parts:
• Section Overhead. The STM-1 section overhead occupies the first nine
columns of the STM-1 frame, for total of 81 bytes.
• Virtual Container. The remaining 261 columns of the STM-1 frame, which
contain a total of 2349 bytes, are allocated to the virtual container. The
virtual container itself comprises a container for the payload signal (260
columns), preceded by one column of path overhead.
The virtual container carried in an STM-1 frame is referred to as a Virtual
Container Level 4, or VC-4. VC-4, which is transported unchanged across the
SDH network, provides a channel capacity of 150.34 Mbps.
Megaplex-4100 Ver. 2.0 STM-1 Frame Structure C-15

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 C-5, 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
to permit reliable distribution of timing to minimize the number of pointer
adjustments.
C-16 STM-1 Frame Structure Megaplex-4100 Ver. 2.0

C.6 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 C-6.
Multiplexer
Section Multiplexer Section
Regenerator Regenerator Regenerator

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

As shown in Figure C-6, 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.
Megaplex-4100 Ver. 2.0 SDH Overhead Data C-17

• 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 Section C.7 for a
description of the low-order path overhead.
Figure C-7 shows the detailed structure of the overhead data in STM-1 frames.
Path
Section Overhead Overhead
Framing Framing Framing Framing Framing Framing ID Path Trace

A1 A1 A1 A2 A2 A2 C1 J1
Regenerator
BIP-8 Orderwire User BIP-8
Section B1 E1 F1 B3
Overhead
(Rows 1 - 3)
DCC DCC DCC Signal Label
D1 D2 D3 C2
AU Pointers Pointer Pointer Pointer Pointer Pointer Path Status

(Row 4) H1 H2 H3 H3 H3 G1
BIP-24 APS APS

User Channel
B2 B2 B2 K1 K2 F2
DCC DCC DCC Multiframe

D4 D5 D6 H4
Multiplex
DCC DCC DCC
Section D7 D8 D9
Z3
Overhead
(Rows 5 - 9)
DCC DCC DCC
D10 D11 D12
Z4
Orderwire
Z1 Z1 Z1 Z2 Z2 Z2
E2
Z5
Bytes reserved for future use
Figure C-7. 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.
C-18 SDH Overhead Data Megaplex-4100 Ver. 2.0

Channel Identifier (C1 Byte)

The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
Parity Check (B1 Byte)

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.
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 Section C.8.
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.
C-20 SDH Overhead Data Megaplex-4100 Ver. 2.0

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 “0”s code represents the VC-4 unequipped state (i.e., the VC-4 does
not carry any tributary signals)
• The code “00000001” represents the VC-4 equipped state.
Path Status (G1 Byte)

The G1 byte is used to send status and performance monitoring information from
the receive side of the path terminating equipment to the path originating
equipment. This allows the status and performance of a path to be monitored
from either end, or at any point along the path.
Multiframe Indication (H4 byte)

The H4 byte is used as a payload multiframe indicator, to provide support for
complex payload structures, for example payload structures carrying multiple
tributary units (TUs – see Section C.7). 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 Section C.8.

C.7 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, described in Section C.3. With reference to Figure C-4, the tributary
unit frame also includes a section overhead part and a virtual container part,
which comprises a container and path overhead.
In general, the tributary unit frame is generated in three steps:
• A low rate tributary signal is mapped into the TU “container”
• Low-path path overhead is added before the container, to form the
corresponding virtual container (VC-11, VC-12, VC-2 or VC-3, depending on
the TU type)
• A TU pointer is added to indicate the beginning of the VC within the TU
frame. This is the only element of TU section overhead.
The TU frame is then multiplexed into a fixed location within the VC-4.
Because of the byte interleaving method, a TU frame structure is distributed over
four consecutive VC-4 frames. It is therefore more accurate to refer to the
structure as a TU multiframe. The phase of the multiframe structure is indicated
by the H4 byte contained in the VC-4 path overhead.
Tributary Unit Types

As mentioned above, specific containers (C), virtual containers (VC) and
associated TU structures have been defined for each standard PDH multiplex
signal level. These structures are explained below:
• 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.
C-22 SDH Tributary Units Megaplex-4100 Ver. 2.0


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 C-8 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 C-9.
2430 Bytes/Frame
Serial Signal
Stream
F F F F
155.52 Mbps
VC-4 Path Overhead
Section TU-12 TU-12 No.2 TU-12

9 Rows Overhead No. 1 to No. 63
TU-12 No.62
9 Columns 260 Columns
1 Column
Figure C-8. VC-4 Carrying TU-12 Payload

As shown in Figure C-8, 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.
SDH Multiplexing Hierarchy

Figure C-9 shows a general view of the SDH multiplexing hierarchy. The hierarchy
illustrates all the both the European and North American PDH multiplex levels
(see Table C-1 for details on the PDH multiplexing hierarchy).
Figure C-9 also shows the utilization of additional SDH signal structures:
• 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.
Megaplex-4100 Ver. 2.0 SDH Tributary Units C-23

• 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).
Note 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 139.264 Mbps
×1 C-4
STM-1 AU-4 VC-4 (E4)
(155.520 Mbps)
AUG
×1
AU-3 VC-3
×3
44.736 Mbps
(DS3)
×3 C-3
TU-3 VC-3
×7
34.368 Mbps
×1 (E3)
TUG-
3
C-2 6.312 Mbps
TU-2 VC-2
×1 (DS2)
×7
×2 3.152 Mbps
VT3
TUG- (DS1C)
2
Legend ×4
TU-11 C-11
1.544 Mbps
VC-11
Pointer Processing (DS1)
×3
TU-12 C-12
2.048 Mbps
Mapping VC-12
(E1)
Figure C-9. 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 C-9
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)
• 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.
C-24 SDH Maintenance Signals Megaplex-4100 Ver. 2.0

C.8 SDH Maintenance Signals
SDH Maintenance Signals

The maintenance signals transmitted within the SDH signal structure are
explained in Table C-2.
Table C-2. 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 The AIS indication is an “all 1’s” pattern in pointer bytes.
Multiplexer Section AIS 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 1’s” 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 Sent upstream by multiplexer section terminating equipment (MSTE) within
(FERF or MS-FERF) 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
-3
“110”.
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
Megaplex-4100 Ver. 2.0 SDH Maintenance Signals C-25

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
1’s” pattern in the H1, H2, H3 pointer bytes plus all bytes of associated VC-3 and
VC-4).
Detected by HO PTE when “all 1’s” 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 Generated by high order path terminating equipment (HO PTE) in response to
Alarm Indication received AU path AIS. Sent upstream to peer HO PTE. Indicated by setting bit 5 of
(HO Path RAI, also known POH G1 byte to “1”.
as HO Path FERF) 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”
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 1’s”
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 1’s” pattern).
Detected by LO PTE when “all 1’s” pattern received in bytes V1 and V2 for 3
consecutive multiframes. Removal is detected when 3 consecutive valid TU
pointers are received.
Note TU Path AIS is only available when generating and/or receiving “floating
mode” tributary unit payload structures.
Low Order Path Remote Generated by low order path terminating equipment (LO FTE) in response to
Alarm Indication received TU Path AIS. Sent upstream to peer LO PTE.
(LO Path RAI, also known Indicated by setting bit 8 of LO POH V5 byte to “1”.
as LO Path FERF)
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.
Response to Abnormal Conditions

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 C-10 provides a graphical representation of the flow of alarm and
indication signals through an SDH transmission path.
C-26 SDH Maintenance Signals Megaplex-4100 Ver. 2.0

Low Order Path
High Order Path
Multiplexer Section
Regenerator Regenerator
Section Section
LO PTE HO PTE MS TE RS TE MS TE HO PTE LO PTE

LOP LOP LOP
LOS LOS
LOF LOF
Tributary
AIS (X2) AIS AIS AIS
(H1H2) (V1V2)
FERF
(X2)
RAI RAI (G1)
(G1)
RAI
(VS) RAI (VS)
B1(BIP-8) B1(BIP-8)
B2(BIP-24)
B3(BIP-8)
FEBE FEBE
(G1)
(G1)
BIP-2
(VS)
FEBE FEBE
(VS) (VS)
Legend
Collection LO Low Order PTE Path Terminating Equipment
Transmission HO High Low Order RS TE Regenerator Section Terminating Equipment
Generation MS TE Multiplexer Section Terminating Equipment
Figure C-10. 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:
• 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
Megaplex-4100 Ver. 2.0 SDH Maintenance Signals C-27

• 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.
C.9 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 in Sections C.3 through C.8.
Figure C-11 shows the SONET multiplexing hierarchy.
STS-3 139.264 Mbps
(155.520 Mbps) ×1 ×1 STS-3c
STS-3c (E4)
STS-3 SPE
×3 ×3
44.736 Mbps
(DS3)
VT6 6.312 Mbps

VT6
SPE (DS2)
×1
×2 VT3 3.152 Mbps

VT3
STS-1 SPE (DS1C)
SPE ×7 VT
STS-1 Group
Legend
×4 VT1.5 1.544 Mbps
VT1.5
SPE (DS1)
Pointer Processing
×3
VT2 2.048 Mbps
Mapping VT2
SPE (E1)
Figure C-11. SONET Multiplexing Hierarchy
C-28 SONET Environment Megaplex-4100 Ver. 2.0

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
• 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.
C.10 Using Virtual Concatenation
Purpose and Main Features

Virtual concatenation is a method that enables carrying payload at other data
rates (for example, Ethernet signals), beyond the data rates listed in Table C-1,
without wasting bandwidth. In this approach, the contiguous bandwidth of the
payload signal is divided into several streams, each having the rate necessary for
insertion into individual VCs or SPEs.
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.
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.
Implementation
Virtual concatenation is implemented mainly by appropriate management
measures, with hardware support needed only at the end points of a
transmission path. The processing is as follows:
Megaplex-4100 Ver. 2.0 Using Virtual Concatenation C-29

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.
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.
Table C-3 lists the bandwidth that can be provided by the virtual concatenation
containers built using the virtual concatenation method.
Table C-3. Virtual Concatenation Container Bandwidth
SDH SONET Maximum Minimum Maximum Bandwidth

Designation of Designation of Number of Resulting Resulting Selection
Member Member Containers in Bandwidth Bandwidth Granularity
Containers Containers Group (Mbps) (Mbps) (Mbps)
VC-11 VT1.5 64 1.600000 102.400000 1.600000
VC-12 VT2 64 2.176000 139.264000 2.176000
– VT3 64 3.328000 212.992000 3.328000
VC-2 VT6 64 6.784000 434.176000 6.784000
VC-3 STS-1 SPE 256 48.384000 12386.304000 48.384000
VC-4 STS-3c SPE 256 149.760000 38388.560000 149.760000
C-30 Using Virtual Concatenation Megaplex-4100 Ver. 2.0

C.11 Ethernet Transmission Technology
Introduction to Ethernet Transmission

One of the most successful digital transmission technologies is referred to by the
generic term Ethernet. The Ethernet technology is suitable for a wide range of
physical media: coaxial cable, twisted pairs and optical fibers. The current
standards for Ethernet transmission cover rates from 10 Mbps to 10 Gbps. In
many office LANs, Ethernet runs at 10 Mbps and 100 Mbps (Fast Ethernet);
1000 Mbps (1 Gbps, also called Gigabit Ethernet, or GbE) is rapidly becoming
commonplace.
The basic standards covering Ethernet LANs are included in the IEEE 802.3 family.
In addition to the aspects covered by the IEEE 802.3 standards, there is a wide
range of LAN standards (the IEEE 802 family) that cover other aspects of LAN
transmission, for example, bridging, with particular emphasis on Ethernet LANs.
Ethernet standards (in their broadest interpretation) cover the physical and data
link control layers (layers 1 and 2 in the OSI model; IP is a layer 3 protocol). The
data link control layer is split into two sublayers: media access control (MAC) and
logical link control (LLC).
Ethernet LAN Topologies

Ethernet LANs use a multidrop topology. The LANs can be implemented either in
bus or star (hub-based) topology.
For the Megaplex-4100, only the star (hub-based) topology is relevant.
Figure C-12 shows the general structure of a LAN using the star topology.
In the star topology, all the nodes on the LAN are connected to a common unit,
which serves as the hub of the LAN. The hub can be implemented in two ways:
• Simple Ethernet hub, which detects the transmitting node and transparently
distributes its signal to all the other nodes. A hub supports only half-duplex
communication (the same as in a bus topology).
• Ethernet switch: the switch includes more sophisticated circuits that enable
both half-duplex and full-duplex operation and prevent collisions.
In a star topology, the LAN cables are usually made of two twisted pairs (one
transmit pair and one receive pair). The standard connector type is RJ-45, and its
pin assignment has also been standardized. However, because of the need to use
separate transmit and receive pairs, two types of port pin assignments have
developed: station ports and hub ports (the difference is interchanging of the
transmit and receive pins in the connector). This permits to interconnect
connectors of different types by a cable wired pin-to-pin (straight cable).
A fixed assignment of pin functions in the connectors requires using a crossed
cable (a cable wired to interconnect the transmit pair at one end to the receive
pair at the other end) to interconnect ports of same type. To avoid the need for
Megaplex-4100 Ver. 2.0 Ethernet Transmission Technology C-31

using two types of cables (straight and crossed), special methods have been
developed to enable automatic detection of pairs by the Ethernet interface, thus
enabling the interface to select the correct connection irrespective of the type of
cable.
Interfaces operating on twisted pairs are designated in accordance with data
rate: 10BASE-T (10 Mbps), 100BASE-TX (100 Mbps, where X is the number of
pairs) and 1000BASE-T (1000 Mbps, which always uses 2 twisted pairs).
100 Mbps fiber optic interfaces are identified as 100BASE-FX (where X is the
number of fibers, and 1000 Mbps fiber optic interfaces carry a label that indicates
the range (SX for short range, etc.).
Interfaces that support multiple rates are identified as 10/100BASET,
10/100/1000BASET, etc.
10/100BaseT Ethernet Hub
SD
TX Pair
RX Pair
Figure C-12. Star (Hub-Based) Ethernet LAN Topology
Ethernet Communication Protocol

Today, Ethernet is used as a generic term for a LAN transmission technology that
uses Carrier Sense and Multiple Access with Collision Detection (CSMA/CD) to
enable the transmission of short bursts of data (called frames) between two or
more stations (nodes).
All the users have permanent access to the full bandwidth of the transmission
medium but can only use it for short times, by transmitting short data bursts.
Each data burst has a fixed structure, called a frame. The frame structure is
explained below. The connection point of each user to the transmission media is
called a node. For identification purposes, each LAN node has its own unique
number, called MAC address.
Media Access Method

Media access is performed by means of the carrier sense, multiple access
protocol (CSMA) with collision detection (CD), defined by IEEE Standard 802.3.
The protocol defines three basic steps:
• A node that wants to transmit checks that the LAN is free. If another node is
already transmitting, the node waits until the LAN is free.
• When the LAN is free, the node starts transmission and sends its frame. Each
node has equal access rights, therefore the first node that starts transmitting
is the one that seizes the LAN.
C-32 Ethernet Transmission Technology Megaplex-4100 Ver. 2.0

• When two nodes start transmitting at the same instant, a collision occurs. In
this case, the transmitting nodes will continue to transmit for some time, in
order to ensure that all transmitting nodes detected the collision (this is
called “jamming”). After the jamming period, all transmitting nodes stop the
transmission and wait for a random period of time before trying again.
The delay times are a function of collision numbers and random time delay,
therefore there is a good chance that an additional collision between these
nodes will be avoided, and the nodes will be able to transmit their messages.
The basic procedure described above has been developed for half-duplex
communication, because it declares a collision whenever data is received during a
local transmission. However, when using twisted pairs, separate pairs are used
for the transmit and receive directions. Therefore, each node is capable of
simultaneously transmitting and receiving (full-duplex operation), thereby
doubling the effective data rate on the LAN.
Autonegotiation
As mentioned above, modern Ethernet interfaces are often capable of operation
at the two basic rates, 10 Mbps and 100 Mbps, or even at three rates
(10/100/1000 Mbps). Therefore, the rate and operating mode (half-duplex or
full-duplex) are user-configurable options.
When connecting equipment from different vendors to a common LAN, several
operating modes are possible, depending on the specific characteristics of the
equipment interconnected by means of the LAN . These modes are listed below,
in ascending order of capabilities:
• Half-duplex operation at 10 Mbps.
• Full-duplex operation at 10 Mbps.
To ensure interoperability (which practically means to select the highest transport
capability supported by all the equipment connected to the LAN), two approaches
can be used: manual configuration of each equipment interface, or automatic
negotiation (auto-negotiation) in accordance with IEEE Standard 802.3.
The auto-negotiation procedure enables automatic selection of the operating
mode on a LAN, and also enables equipment connecting to an operating LAN to
automatically adopt the LAN operating mode (if it is capable of supporting that
mode).
When auto-negotiation is enabled on all the nodes attached (or trying to attach)
to a LAN, the process is always successful. However, even if the nodes on an
operating LAN are manually configured for operation in a fixed mode, a
late-comer node with auto-negotiation capability can still resolve the LAN
operating rate can be resolved, thereby enabling it to adopt the LAN rate. Under
these conditions, an auto-negotiating node cannot detect the operating mode
(half or full duplex), and therefore they will default to half-duplex. Therefore, as a

practical configuration rule, do not enable the full-duplex mode without enabling
auto-negotiation, except when all the nodes have been manually configured for
the desired operating mode (which may of course be full duplex).
Basic Ethernet Frame Structure

The frame transmitted by each node contains routing, management and error
correction information. For Ethernet LANs, the characteristics of frames are
defined by IEEE Standard 802.3.
Basic frame lengths can vary from 72 to 1526 bytes and have the typical
structure shown in Figure C-13.
72 to 1526 Bytes
Length/ Frame
Preamble SFD MAC Destination MAC Source MAC Client data
Type Padding Check
Address Address
Bytes Sequence
(7 Bytes) (1 Byte) (6 Bytes) (6 Bytes) (0 to 1600 Bytes)
(2 Bytes) (4 Bytes)
Start Frame
Delimiter
Figure C-13. Basic Ethernet Frame Structure

• Preamble. Each frame starts with a preamble of seven bytes. The preamble is
used as a synchronizing sequence for the interface circuits, and helps bit
decoding.
• Start-Frame Delimiter (SFD) field – consists of one byte. The SFD field
indicates where the useful information starts.
• Medium-Access (MAC) Destination Address (DA) field – consists of six bytes.
The MAC DA field carries the address of the destination node.
• Medium-Access (MAC) Source Address (SA) field – consists of six bytes. The
MAC SA field carries the address of the source node.
Note In conventional notation MAC addresses are represented as 6 pairs of

hexadecimal digits, separated by dashes, for example, 08-10-39-03-2F-C3.
• Length/Type field – consists of two bytes that indicate the number of bytes
contained in the logical link control (LLC) data field. In most Ethernet protocol
versions, this field contains a constant indicating the protocol type (in this
case, this field is designated EtherType).
• MAC Client Data field. The MAC client data field can contain 0 to 1600 bytes
of user-supplied data.
• Padding field. The optional padding field contains dummy data, that is used
to increase the length of short frames to at least 64 bytes.
• Frame Check Sequence (FCS) field – contains four check bytes generated by a
cyclic redundancy check (CRC) code. The FCS field is used to detect errors in
the data carried in the frame.

Bridging
Communication between Nodes on Same LAN

A MAC address is unique and identifies a single physical port. Therefore, two
Ethernet nodes attached to the same LAN exchange frame directly, by specifying
the desired MAC destination address, together with the source MAC address.
The node that identifies its MAC address in the destination field can send a
response by copying the source address of the frame to the destination address
field.
Communication between Nodes on Different LANs

To enable nodes on different LANs to communicate, it is necessary to transfer
frames between the two LANs. The device used for this purpose is called MAC
bridge, or just bridge. Two types of bridges are used:
• Local bridges, which have Ethernet ports attached to the two LANs. The
bridge control mechanism learns the nodes attached to each LAN by reading
the source MAC addresses of the frames generated by the nodes. When the
destination address of a frame is not on the LAN from which it was received,
the bridge transfers it to the other LAN.
• Remote bridges, which are used in pairs. A basic remote bridge has one LAN
port and one WAN port. The WAN port communicates through a link with the
WAN port of the remote bridge connected to the desired remote LAN. In this
case, the traffic addressed to destinations not located on the local LAN is
transferred through the WAN link to the remote bridge.
Using Virtual Bridged LANs

VLAN can be used to provide separation between traffic from different sources
sharing the same physical transmission facilities, and provide information on the
relative priority the user assigns to each frame. The characteristics and use of
virtual LANs (VLANs) and of the MAC bridges capable of handling tagged frames
are defined in IEEE Standard 802.1Q.
VLANs are made possible by a slight modification to the Ethernet frame structure
shown in Figure C-13.
The structure of an Ethernet frame with VLAN support is shown in Figure C-14
(for simplicity, the figure does not include the preamble and SFD fields).
Ethernet frames with VLAN support include a tag header immediately after the
source MAC address (therefore, such frames are also referred to as tagged
frames).
The tag header comprises 4 bytes:
• Two bytes for the tag protocol identifier. For Ethernet-encoded tags in
accordance with IEEE802.1Q, these bytes carry the equivalent of 8100.
• Priority (PRI) specified by the user (3 bits: 7 is the highest priority and 0 is
the lowest priority).
• One bit for the canonical format indicator (always 0 as shown in Figure C-14).

• VLAN ID (12 bits), used to indicate the VLAN to which the frame belongs.
0 4 8 12 16 20 24 28 31
Destination MAC Address (DA)
Destination MAC Address (DA) Source MAC Address (SA)
Source MAC Address (SA)
Tag Protocol Identifier (8100) PRI 0 VLAN ID
EtherType (IP = 0800) Ethernet Payload (42 to 1500 Bytes)
Ethernet Payload
.
.
.
CRC
Figure C-14. Structure of Ethernet Frame with VLAN Support
MEF View of Ethernet Services

The Metro Ethernet Forum (MEF) specifications supplement the existing technical
standards in order to ensure interoperability and adequate performance of
Ethernet networks in metropolitan applications.
The function of a metropolitan Ethernet network is to handle customers’ edge
traffic reaching the network interfaces in accordance with clearly-defined service
standards:
• The term customer’s edge refers to the physical or logical point at which
customer’s traffic is handed over to a network interface, for transport over
the network.
• The service provider edge is the point at which customer’s traffic (received
through a customer’s edge network interface and processed for transport) is
handed over to a service provider access point or PoP.
Note • The customer-network interface is referred to as a User-Network Interface

(UNI); additional interfaces may be used between networks, and these are
referred to as Network-Network Interfaces (NNIs). The generic term xNI is
used for both types of interfaces.
• On Megaplex-4100 management screens, EVCs are referred to as flows, and
xNIs are referred to as bridge ports.
The Ethernet traffic reaching the Ethernet interfaces, for example, Ethernet
interfaces located on modules such as M8E1, M8T1, M8SL, can be forwarded
among xNIs (network interfaces) defined on the module physical and logical ports
by entities referred to as Ethernet Virtual Connections (EVCs) that function as
virtual bridges.

Ethernet switching occurs at Layer 2 (based on MAC addresses), and is basically

configured by first mapping xNIs as termination points for EVCs, and then
specifying a classification method.
Two types of EVCs (flows) are described in MEF specifications:
• E-line: a point-to-point type of Ethernet virtual connection that interconnects
exactly two network interfaces (bridge ports). This functionality is similar to
that of a line connection between these interfaces.
• E-LAN: a multipoint type of Ethernet virtual connection that interconnects
more than two network interfaces (bridge ports), and provides any-to-any
interconnectivity. This functionality is similar to that of a LAN interconnecting
several interfaces.
An EVC connects only the user-mapped xNIs, that is, transfers Ethernet frames
with user-specified characteristics only between the specified xNIs and prevents
transfer of such frames to any xNI which is not part of the same EVC (this is
rather similar to what is expected of a virtual private network (VPN)).
An EVC interconnects at least two xNIs, however a given xNI can serve as the
termination point of several EVCs. Therefore, in general each EVC must
discriminate (be aware of) among the Ethernet frames reaching an associated xNI
in order to determine how to handle the customers’ traffic. Although this
discrimination can be made simply by defining closed sets of ports (exactly two
for the E-line service, two or more for the E-LAN service), this approach does not
permit Ethernet switching to take place. When Ethernet switching is needed, the
discrimination is mainly based on the customer’s edge and service provider’s edge
VLAN identifiers received in each frame – a forwarding mode referred to as VLAN-
aware, and is supplemented by specifying the relevant ports. To correctly forward
untagged or priority-tagged traffic (a forwarding mode referred to as VLAN-
unaware) among user-specified ports, Megaplex-4100 automatically assigns a
special (internal) VLAN ID.
The range of VLAN IDs that can be used for customer’s Ethernet traffic with IEEE
802.Q tags is 1 to 4094.
Note Untagged and priority-tagged frames are collectively referred to as untagged

frames, and are handled in the unaware mode.
To prevent ambiguities, any specific C-VLAN ID can be used only once per xNI, but
can be reused on different xNIs. For the same reason, a specific SP-VLAN ID must
be unique per Megaplex-4100.
The MEF standards enable providing different classes of services (CoS), which
may be based on several options. The most common options are:
• Physical ports
• Use of the priority bits in the VLAN tag as a CoS designator in accordance
with IEEE 802.1p (this results in a maximum of eight classes of service)
• Use of the Type of Service (ToS) or DiffServ (DSCP) fields in IP packets as a
CoS designator (this results in a maximum of 64 classes of service)
To enable personnel to identify problems in metropolitan Ethernet networks, it is
necessary to check connectivity at Layer 2 for each traffic-carrying link. For this
purpose, the standards define a link operations and maintenance (OAM) protocol.

The link OAM protocol uses special OAM protocol data units (PDUs) to check
connectivity between each xNI and the attached equipment. The protocol can be
enabled on physical Ethernet ports, and on bundles carrying Ethernet traffic over
the TDM network: to be effective, the protocol must be enabled at both ends of
a link. For bundles, only one end can initiate the exchange of OAM PDUs (the
active endpoint), and the other (passive) endpoint only reacts to the OAM PDUs
sent by the active endpoint.
Bundles
To transport Ethernet traffic through E1 and T1 links, virtual ports called bundles
can be defined on the physical or virtual E1 or T1 ports. For SDH/SONET links,
virtually concatenated groups can also be used for this purpose (see the Ethernet
Transport over SDH/SONET Networks section below).
Two types of bundles can be defined:
• Bundles using HDLC as the Layer 2 protocol. The bandwidth assigned to a
HDLC bundle depends on the number of timeslots assigned by the user
(maximum 30 for an E1 port, and maximum 24 for a T1 port). HDLC bundles
are also supported by the virtual PDH ports of SDH/SONET links.
For unframed E1 ports (available on the M8E1 and M8SL modules), an E1 port
supports a single HDLC bundle, and it occupies the whole port bandwidth
(2048 kbps, equivalent to 32 timeslots).
• Bundles using MLPPP as the Layer 2 protocol (for the current Megaplex-4100
version supports MLPPP bundles only over unframed ports, and such ports are
available only on the M8E1 and M8SL modules). MLPPP 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 links to provide increased bandwidth. For
M8E1 and M8SL modules, the user can configure the bundle to extend over
any number of ports, up to the maximum supported by the module (8 ports).
All the ports associated with an MLPPP bundle must use the same framing
mode. The bandwidth automatically assigned to an MLPPP bundle depends on
the selected number of ports: therefore, the maximum bandwidth of an
MLPPP bundle, achieved when the bundle uses all the 8 ports of the module
in the unframed mode, is 8 × 2048 kbps (16384 kbps).
xNIs (Bridge Ports)

The following types of xNIs (bridge ports) can be defined on Megaplex-4100:
• One xNI can be defined on each Ethernet physical interface.
• One xNI can be defined on each bundle.
• One xNI can be defined on each virtually concatenated group.
The following configuration rules apply to the types of EVCs to which any given
bridge port can be mapped:
1. A bridge port can terminate only one flow (EVC) classified as unaware (i.e.,
which does not discriminate Ethernet traffic in accordance with customer’s
and service provider’s VLANs).

2. 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 EVC classified as
unaware.
3. A bridge port can terminate any number of flows with specific VLAN IDs
Flows (EVCs)
The maximum number of flows that can be defined on the current
Megaplex-4100 version is 250. It is not possible to configure flows between
Ethernet ports on the same module (neither for ports on I/O modules, nor for
ports on CL modules).
For E-line flows, the following VLAN assignment rules apply:
1. The bridge ports terminating an EVC (flow) must use the same VLAN mode
(either unaware or aware).
2. When using the aware mode, the same VLAN IDs must be configured at both
bridge ports. For example, this means that flows between GbE bridge ports
must use the same SP-VLAN ID.
Ethernet Transport over SDH/SONET Networks

Ethernet payloads can be carried over SDH/SONET using several encapsulation
protocols. Megaplex-4100 supports two encapsulation protocols:
• Link Access Protocol – SDH (LAPS) in accordance with ITU-T Rec. X.86
• Generic Framing Procedure (GFP) in the framed mode, in accordance with
ITU-T Rec. G.7041. With GFP, it is possible to increase the bandwidth
utilization efficiency using the GFP multiplexing method.
LAPS Encapsulation
With LAPS, each Ethernet frame is encapsulated in the frame structure shown in
Figure C-15. The LAPS frame is delineated by flags, followed by HDLC information
(address and control), and by a LAPS service access point identifier (SAPI). The
Ethernet frame is followed by a LAPS frame checksum (FCS), for error detection.
LAPS Frame
Ethernet Frame
HDLC HDLC
Flag LAPS SAPI Ethernet Frame LAPS FCS Flag
Address Control
(1 byte) (1 byte) (1 byte) (2 bytes( (64 to 1500 bytes) (4 bytes) (1 byte)
Figure C-15. LAPS Encapsulation Format

GFP Encapsulation
The GFP encapsulation method uses the basic frame structure of Figure C-16.
GFP Frame
Ethernet Frame
Core Header Payload Header Ethernet Frame
(4 bytes) (4 bytes) (1500 bytes)
Figure C-16. Basic GFP Encapsulation Format

Figure C-17 shows the detailed structure of the basic GFP frame. The frame
includes the following fields:
PLI Payload length indicator
cHEC Core header CRC (calculated using ITU-T CRC-16 polynomial)
Payload Area Carries a framed PDU
Payload Header Header used for client PDU management
pFCS Optional payload FCS (calculated using ITU-T CRC-32

polynomial)
GFP Frame
Core Payload Payload

Header Area FCS
PLI cHEC Payload Header Payload Area pFCS
(16 bits) (16 bits) (4 bytes) (framed PDU – 4 to 65535 bytes) (32 bits)
Figure C-17. Detailed Structure of Basic GFP Frame

All the GFP OAM&P functions are handled by the GFP core header.
The payload header supports the payload-specific adaptation functions, which
depend on the client application (for Megaplex-4100, the client application is
Ethernet). The payload header also supports multiplexing (using extension
headers), and any application-dependent link management functions (using
dedicated client management frames)
Protection against errors (on a per frame basis) is provided by the optional
payload frame checksum (FCS) field.
Idle frames are used for asynchronous rate adaptation.
GFP Protocol Stack

The encapsulation process can be described by means of a GFP protocol stack,
illustrated in Figure C-18:

Ethernet
GFP – Client Specific Aspects

(Client Dependent)
GFP – Common Aspects

(Client Independent)
SDH/SONET Path
Figure C-18. GFP Protocol Stack

• The top layer is the client application, in this case Ethernet. For the
Megaplex-4100, the Ethernet switch provides up to four independent
application streams (one stream per virtual group).
• The link layer is divided into two sections:
GFP common aspects section: performs adaptation to the physical layer.
GFP client-specific aspects section: handles the frames received from the
client application, and presents them in a standardized format to the GFP
common aspects section.
• The physical layer is provided by the SDH or SONET path.
GFP Multiplexing
In the Megaplex-4100, each data stream may be mapped to a different VC or SPE
(or to a user-defined virtually concatenated group of VCs or SPEs), however in
this case bandwidth may be wasted, because this approach always occupies the
full SDH/SONET bandwidth, irrespective of the actual traffic load generated by the
client application, which in general varies randomly with time.
To take advantage of the statistical distribution of traffic, multiplexing can be
used. GFP provides support for multiplexing, using two approaches
(see Figure C-19):
• Frame multiplexing in accordance with the frame type, using the PTI (payload
type identifier) field:
Client data frames have priority over client management frames
Client management frames have priority over idle frames.
Payload Type MSB PTI PFI EXI

Core Header
Payload Header Payload Type LSB UPI
Type HEC MSB
Type HEC LSB

CID
Payload Area 0-60 Bytes of Spare

Extension
Headers Extension HEC MSB
(Optional)
Extension HEC LSB
Figure C-19. Support for GFP Multiplexing at the GFP Frame Level

• Client multiplexing, implemented by adding extension headers. For this

purpose, the extension header includes a customer, or channel, identifier
(CID). The CID enables discriminating among various data sources using the
same transmission path.
To take advantage of the GFP client multiplexing capability, the user can
configure:
• The virtual groups to be multiplexed
• The fraction of physical layer bandwidth to be guaranteed to each virtual
group, in 12.5% steps
• The VCs/SPEs to carry the multiplexed groups, and the specific mapping.
With GFP multiplexing, the bandwidth available to each virtual group is never less
that the specified minimum. However, if the instantaneous traffic carried by a
virtual group does not fully utilizes the reserved bandwidth, any unused
bandwidth is made available to the other virtual groups. This ensures the best
possible utilization of the available bandwidth, without degrading the quality of
service.

C.12 IP Environment
This section provides background information on the IP environment.
The information presented in this section refers to Version 4 of the IP protocol
(IP4), currently the most widely used protocol version.
Introduction to IP
IP means “Internet Protocol”. The term IP protocol is often used to indicate a
standardized set of rules and procedures that enable data exchange through a
packet-switched network.
Accordingly, the term Internet indicates the set of networks that use the IP
protocol and are interconnected in a way that, at least in principle, permits any
entity on one network to communicate with any entity on another network.
Note The term “suite of IP protocols” is also often used, in recognition of the fact that
the operation of the Internet is actually defined by many related protocols.
IP Networks, IP Hosts and IP Ports

Any entity that can communicate using the IP protocol is called an IP host. The
connection point between an IP host and an IP network is called IP port.
An IP network forms when a number of IP ports can communicate directly (peer
to peer) using the IP protocol, without any intermediaries.
An IP host can have any number of IP ports. Moreover, the ports may be located
on different IP networks.
IP Addresses
To enable IP communication between two IP hosts, it is necessary to find a route
between their IP ports. For this purpose, each IP port is assigned an IP address.
The only purpose of an IP address is to permit unambiguous identification of an
IP port. Therefore, each IP port must be assigned a distinct and unique IP
address.
The IP protocol does not require the IP port to be related in an unambiguous way
to a physical (communication) port. This has two main implications:
• Since the IP port is actually a connection to an IP network, any number of IP
ports can share a given physical port.
• An IP port may be reached through several physical ports.
Note By convention, the scope of IP addresses has been extended in two ways:
• To permit identification of IP networks
• To permit simultaneous addressing of all the ports connected to a IP network
(this operation is called broadcasting).
Megaplex-4100 Ver. 2.0 IP Environment C-43

IP Packet Structure
The information exchanged through IP networks is organized in packets. The
structure of an IP packet, as specified by IP protocol Version 4, is as follows (the
numbers are byte numbers):
0 4 8 12 16 20 24 28 31
IP IP IP Type of Service Total IP Packet Length

Version Header (IP TOS) (total number of octets in header +
(4) Length payload)
Fragment Identification Flags Fragment Offset

(16 bits) (3 bits) (13 bits)
(These fields are used for IP packet fragmentation)
Time to Live Number of IP Header Checksum

(Range: 0 to 255; Upper-Layer
when 0, packet is Protocol Carried in
discarded) Payload
(IGMP = 2)
(UDP = 17)
Source IP Address
Destination IP Address
Options (when used) Padding (as required)
Payload (maximum bytes: 65535 – “header length”)
IP Address Structure
An IP address is a 32-bit number, represented as four 8-bit bytes. Each byte
represents a decimal number in the range of 0 through 255.
The address is written in decimal format, with the bytes separated by decimal
points, e.g., 164.90.70.47. This format is called dotted quad notation.
An IP address is logically divided into two main portions:
• Network portion
• Host portion.
Network Portion
In general, the network portion is assigned by the Internet Assigned Numbers
Authority (IANA), and its main purpose is to identify a specific IP network.
There are five IP address classes: A, B, C, D, and E. However, only the A, B and C
classes are used for IP addressing. Consult your network manager with respect to
the class of IP addresses used on your network.
The network portion of an IP address can be one, two, or three bytes long, in
accordance with the IP address class.
C-44 IP Environment Megaplex-4100 Ver. 2.0

This arrangement is illustrated below:
IP Address
Byte 1 Byte 2 Byte 3 Byte 4
Class A Network Portion Host Portion
Class B Network Portion Host Portion
Class C Network Portion Host Portion
The class of each IP address can be determined from its leftmost byte, in
accordance with the following chart:
Address Class First Byte Address Range
Class A 0 through 127 0.H.H.H through 127.H.H.H
Class B 128 through 191 128.N.H.H through 191.N.H.H
Class C 192 through 223 192.N.N.H through 223.N.N.H
where:
N – indicates bytes that are part of the network portion
H – indicates bytes that are part of the host portion.
Host Portion
In general, the host portion is used to identify an individual host connected to an
IP network.
After obtaining an IP network address, the using organization is free to assign
host identifiers in accordance with its specific needs.
Note
The following host identifiers have special meanings, and must not be assigned
to an actual host:
• The “all-zeros“ host identifier is interpreted as a network identifier.
• The “all-ones“ host identifier is interpreted as a broadcast address. Therefore,
a message with an “all-ones“ host identifier is accepted by all the hosts in the
network.
Subnetting
Given the scarcity of IP network addresses, for organizations operating several
relatively small, physically separated, IP networks, e.g., several departmental
networks, it is advantageous to enable several physical networks to share a
common IP network address. Small in this context means that the number of IP
ports connected to each of these networks is small relative to the host address
space for the corresponding IP address class.

The approach taken to enable the sharing of an IP network address by two or

more networks is called subnetting, which means use of subnets. The subnetting
is relevant only within the using organization, and therefore can be freely
selected to meet its specific needs.
To enable subnetting, the meaning of the bits in the host portion of the IP
address is further sub-divided into two portions:
• Subnet number. For example, subnet numbers can be used to identify
departmental subnets. The subnet number follows the network identifier.
• Host number – the last bits of the IP address.
This subdivision is illustrated below:
Net Number Subnet Number Host Number
For example, when the subnet includes 16 IP hosts, only the last four bits need
to be reserved for the host number. For an organization which obtained one
global Class C network address, this means that four bits are available to identify
subnets. Therefore, this organization can implement 16 IP subnets, each
comprising up to 16 hosts (except for two subnets that are limited to 15 hosts).
Subnet Masks
Subnet masks are used to indicate the division of the IP address bits between the
net and subnet portion and the host portion.
The mask is a 32-bit word that includes “ones” in the positions used for net and
subnet identification, followed by “zeros” up to the end of the IP address.
For example, the default subnet mask for any Class C address (i.e., all the eight
bits in the host address space are used for hosts in the same net) is
255.255.255.000.
However, if the same address is used in a subnet comprising up to 16 hosts and
for which the host numbers range is 00 to 15, the subnet mask changes as
follows:
IP Address 192 70 55 13
(Dotted-Quad)
IP Address (Binary) 1011 1111 0100 0110 0011 0111 0000 0111
Subnet Mask 1111 1111 1111 1111 1111 1111 1111 0000
(Binary)
Subnet Mask 255 255 255 240

(Dotted-Quad)
In most applications, the binary subnet mask is built as a contiguous string of

“ones”, followed by a number of “zeros” (the number of “zeros” is selected as
needed, to complete the number of subnet mask bits to 32). Therefore, when
this conventional approach is used, the subnet mask can also be specified simply
by stating the number of “ones” in the mask. For example, the subnet mask
shown above is specified by stating that it comprises 28 bits.
C-46 IP Environment Megaplex-4100 Ver. 2.0

IP Routing Principles
The exchange of information between IP hosts is made in packets using the
structure specified by the IP protocol. As explained in the IP Packet Structure
section above, IP frames carry, within their header, the IP addresses of the
destination and source hosts.
In accordance with the IP protocol, an IP host checks the addresses of all the
received frames, and accepts only frames carrying its own IP address as the
destination. The source address is then used to enable the destination to
respond to the source.
An IP host will also respond to broadcasts (frames whose destination host
identifier is “all-ones”).
Note IP hosts support additional protocols within the IP suite, e.g., protocols used for
connectivity checking, maintenance, etc. Therefore, IP hosts will accept additional
types of messages, which are beyond the scope of this description.
When checking the destination address of an IP frame, an IP host starts by

checking the network identifier. If the network identifier is different, the host will
immediately reject the frame. Therefore, IP hosts can communicate only if they
have the same network identifier.
For example, this means that when a management station managing the
Megaplex-4100 is connected directly, through a LAN, to the Megaplex-4100
Ethernet management port, the network identifier part of the IP address assigned
to the Megaplex-4100 Ethernet port must be identical to the network identifier
of the management station.
To enable hosts located on different IP networks to communicate, IP routers are
needed. The routers monitor the flowing traffic and identify the IP addresses of
the local hosts connected to them, and then communicate this information to the
other routers which are “known” to it using special protocols. Therefore, a router
can determine to which other router to send a packet with a foreign IP address.
The user can increase the routing efficiency by specifying a default gateway to
handle IP traffic to other networks (this is always an IP router). When a default
gateway address is specified, packets with IP destinations located on other
networks are sent to the default gateway for processing: the router serving as
default gateway then sends them to their destination.
The default gateway must always be in the same IP subnet as the port sending
traffic to the gateway.
Note As an alternative, static IP routing may also be used. To define a static route, the
user must specify the next hop, that is, IP address of the next port to which IP
packets are to be forwarded.

Tools for Checking IP Connectivity

The IP protocol is referred to as an unreliable connectionless packet delivery
protocol, because each packet transmitted by an IP host travels on its own
through the network until it eventually reaches its destination. To ensure reliable
delivery, higher layer protocols are used, for example, the widely-used TCP
protocol.
However, using higher layer protocols cannot provide an answer to the need to
check that it is indeed possible to reach the desired IP destination address,
because configuration errors or a network fault, for example, temporary
congestion or failure of critical communication links, may still prevent the
establishment of an IP connection. Therefore, it is often necessary to check for IP
connectivity.
The IP protocol suite includes a special protocol, the Internet Control Message
Protocol (ICMP), that enables IP hosts connected to the Internet to report a wide
range of errors and provide information about the conditions that caused the
errors. Support for this protocol is mandatory on every IP host.
ICMP includes a dedicated connectivity test procedure, implemented by means of
two types of ICMP messages: echo request and echo reply. This procedure is
often referred to as pinging: the host wanting to check IP connectivity to a
destination sends one or more ping (echo request) messages, and the
destination returns an echo reply message for each request. By comparing the
number of pings sent to the number received and the time needed for each reply
to reach the ping source, the source host can obtain useful information regarding
the transmission conditions.
C.13 SNMP Environment
General
The SNMP management functions of the Megaplex-4100 are provided by an
internal SNMP agent.
The SNMP management communication uses the User Datagram Protocol (UDP), a
connectionless-mode transport protocol, part of the suite of protocols of the
Internet Protocol (IP). This section covers the information related to the SNMP
environment.
Note Telnet management uses the TCP protocol over IP for management
communication. After a Telnet session is started, the management interface is
similar to that used for the supervision terminal.
SNMP Principles
The SNMP management protocol is an asynchronous command/response polling
protocol: all the management traffic is initiated by the SNMP-based network
management station (except for trap messages), which addresses the managed
C-48 SNMP Environment Megaplex-4100 Ver. 2.0

entities in its management domain. Only the addressed managed entity answers
the polling of the management station.
The managed entities include a function called an “SNMP agent”, which is
responsible for interpretation and handling of the management station requests
to the managed entity, and the generation of properly-formatted responses to
the management station.
SNMP Operations
The SNMP protocol includes four types of operations:
getRequest Command for retrieving specific management information

from the managed entity. The managed entity responds
with a getResponse message.
getNextRequest Command for retrieving sequentially specific management

information from the managed entity. The managed entity
responds with a getResponse message.
setRequest Command for manipulating specific management

information within the managed entity. The managed
entity responds with a setResponse message.
trap Management message carrying unsolicited information on

extraordinary events (e.g., alarms) reported by the
managed entity.
Management Information Base

The management information base (MIB) includes a collection of managed
objects. A managed object is defined as a parameter that can be managed, such
as a performance statistics value.
The MIB includes the definitions of relevant managed objects. Various MIBs can be
defined for various management purposes, types of equipment, etc.
An object's definition includes the range of values and the “access” rights:
Read-only Object value can be read, but cannot be set.
Read-write Object value can be read or set.
Write-only Object value can be set, but cannot be read.
Not accessible Object value cannot be read, nor set.
MIB Structure
The MIB has an inverted tree-like structure, with each definition of a managed
object forming one leaf, located at the end of a branch of that tree. Each “leaf” in
the MIB is reached by a unique path, therefore by numbering the branching points,
starting with the top, each leaf can be uniquely defined by a sequence of numbers.
The formal description of the managed objects and the MIB structure is provided in
a special standardized format, called Abstract Syntax Notation 1 (ASN.1).
Megaplex-4100 Ver. 2.0 SNMP Environment C-49

Since the general collection of MIBs can also be organized in a similar structure,
under the supervision of the Internet Activities Board (IAB), any parameter
included in a MIB that is recognized by the IAB is uniquely defined.
To provide the flexibility necessary in a global structure, MIBs are classified in
various classes (branches), one of them being the experimental branch, and
another the group of private (enterprise-specific) branch. Under the private
enterprise-specific branch of MIBs, each enterprise (manufacturer) can be
assigned a number, which is its enterprise number. The assigned number
designates the top of an enterprise-specific sub-tree of non-standard MIBs.
Within this context, RAD has been assigned the enterprise number 164.
Therefore, enterprise MIBs published by RAD can be found under
1.3.6.1.4.1.164.
MIBs of general interest are published by the IAB in the form of a Request for
Comment (RFC) document. In addition, MIBs are also often assigned informal
names that reflect their primary purpose. Enterprise-specific MIBs are published
and distributed by their originator, which is responsible for their contents.
Enterprise-specific MIBs supported by RAD equipment, including Megaplex-4100,
are available in ASN.1 format from the RAD Technical Support Department.
Management Domains Under SNMP

SNMP enables, in principle, each management station that knows the MIBs
supported by a device to perform all the management operations available on
that device. However, this is not desirable in practical situations, so it is
necessary to provide a means to delimit management domains.
SNMP Communities
To enable the delimitation of management domains, SNMP uses “communities”.
Each community is identified by a name, which is a case-sensitive alphanumeric
string defined by the user.
Any SNMP entity (this term includes both managed entities and management
stations) can be assigned by its user community names.
Access Restriction Using SNMP Communities

In general, SNMP agents support two types of access rights:
• Read-only: the SNMP agent accepts and processes only SNMP getRequest and
getNextRequest commands from management stations which have the same
read-only community name.
• Read-write: the SNMP agent accepts and processes all the SNMP commands
received from a management station with the same write community name.
For each SNMP entity it is possible to define a list of the communities which are
authorized to communicate with it, and the access rights associated with each
community (this is the SNMP community name table of the entity).
For example, the SNMP community name table of the Megaplex-4100 SNMP agent
can include three community names.

In accordance with the SNMP protocol, the SNMP community of the originating
entity is sent in each message.
When an SNMP message is received by the addressed entity, first it checks the
originator's community: if the community name of the message originator differs
from the community name specified for that type of message in the agent, the
message it discarded (SNMP agents of managed entities report this event by
means of an authentication failure trap).
Megaplex-4100 Communities
The SNMP agent of the Megaplex-4100 is programmed to recognize the following
community types:
Read SNMP community that has read-only authorization, i.e., the SNMP
agent will accept only getRequest and getNextRequest commands
from management stations using that community.
Write SNMP community that has read-write authorization, i.e., the SNMP
agent will also accept setRequest commands from management
stations using that community.
Trap SNMP community which the SNMP agent will send within trap
messages.
SNMP Traps
The Megaplex-4100 SNMP agent supports the MIB-II authentication trap, and in
addition generates enterprise-specific traps for each alarm message.
Traps are also sent to notify the management station of the following events:
• Resetting (warm start trap)
• Change in status of the management link (up or down)
• Authentication failure (use of wrong community).
Megaplex-4100 Ver. 2.0 SNMP Environment C-51


Index
Boot menu
—1— TFTP
1+1 unidirectional protection, 1-58 preparations, B-15
TFTP transfer, B-15
—A— default gateway address, B-16
downloading procedure, B-16
AC power connector data, A-6
IP address, B-16
Admin Status
IP mask, B-16
E1, 4-69
Reset board, B-16
ETH, 4-27
X-modem transfer
GbE port, 4-46
preparations, B-13
SDH/SONET link, 4-55
procedure, B-13
T1, 4-72
Protocol, B-14
Alarm Attributes
Send File, B-14
Alarm Description, 4-154
Transfer, B-14
Alarm ID, 4-153
Brackets, 2-25
Filter/Threshold, 4-154
Bridge ports, C-38
Invert, 4-154
mapping to management flow, 4-118
Mask, 4-154
add new bridge port to flow, 4-118
Port Num, 4-154
mapping to traffic flows, 4-112
Port Type, 4-153
add new bridge port to flow, 4-112
Reset Val, 4-154
Port, 4-113
Set Val, 4-154
Slot, 4-113
Slot, 4-153
Broadcast
ALARM connector, 2-19, A-3
unidirectional broadcast, 1-28
Alarms, 6-15
Bundles, 1-42, C-38
alarm attributes, 4-152
HDLC, 1-42
alarm buffer, 6-15
Admin Status, 4-88
alarm priority, 4-160
configuration, 4-86
alarm relays, 6-15
L2 Protocol, 4-89
alarm reporting, 4-158
Link OAM, 4-89
Alarm, 4-158
Link OAM Mode, 4-90
Log, 4-158
Number of TS, 4-89
Major LED, 4-159
Rate, 4-89
Minor LED, 4-159
Remote Terminal, 4-90
Relay-1, 4-158
Source Port, 4-90
Relay-2, 4-159
Source Slot, 4-90
Report, 4-158
timeslot assignment, 4-90
alarm threshold window, 4-162
User Name, 4-88
configuring alarm handling, 4-151
MLPPP, 1-43
displaying, 6-15
Admin Status, 4-93
interpreting, 6-16
configuration, 4-91
list, 6-17
L2 Protocol, 4-93
monitoring, 6-48, 6-50
Link OAM, 4-93
ALM indicator, 2-19
Link OAM Mode, 4-93
ALS, 1-31
MLPPP MTU, 4-93
APS, 1-32, 1-58
Number of Links, 4-93
1+1 unidirectional protection, 1-58
Rate, 4-93
Auto Negotiation
GbE port, 4-46
Slot, 4-93
Source Port, 4-93
—B— User Name, 4-93
Blank panel, 2-24
I-1
Index Installation and Operation Manual
—C— APS Group ID, 4-128

CAS Flip upon SD, 4-129
CAS signaling information handling, 1-27 Protection, 4-128
CL modules, 1-10 Protection Port, 4-129
ALARM connector, 2-19 Revertive, 4-129
ALM indicator, 2-19 Working Port, 4-129
CL installation, 2-22 WTR Time, 4-129
SFP, 2-21 CL HVC ports parameters, 4-76
CL panel, 2-17 SDH links, 4-77
CL removing, 2-22 SONET links, 4-79
CL replacement during operation, 2-23 CL physical ports
CLOCK connector, 2-19 GbE port configuration, 4-45
LOS indicator, 2-19 station clock, 4-43
ON indicator, 2-19 CL SDH/SONET configuration task selection, 4-50
connections, 2-27, 2-28, 2-29 CL.1/155 virtual ports
CONTROL DCE PDH ports, 4-67
connector, 2-19 CL.1/155GbE virtual ports
CONTROL ETH PDH ports, 4-67
ACT indicator, 2-19 control port parameters, 4-20
connector, 2-19 date & time parameters, 4-35
LINK indicator, 2-19 device info, 4-34
GbE connector, 2-20 ETH port parameters, 4-26
ACT indicator, 2-20 Ethernet flows, 4-110
LINK indicator, 2-20 management flow, 4-116
LINK connector, 2-19 traffic flow, 4-111
LOS indicator, 2-20 fault propagation, 4-149
ON LINE indicator, 2-20 GbE physical ports configuration, 4-45
module installation, 2-17 Redundancy, 4-48
normal indications, 3-3, 3-4 host IP parameters, 4-28
ON LINE indicator, 2-19 management access parameters, 4-30
CL physical ports manager list, 4-31
GbE port configuration, 4-45 Alarms Trap, 4-32
CL.1/155 IP Address, 4-32
SDH/SONET protection, 1-58 Managers ID, 4-32
path protection, 1-61 mapping
CL.1/155GbE SDH/SONET links, 4-141
PSN interface redundancy, 1-62 nodal timing, 4-123
SDH/SONET protection, 1-58 path protection, 4-74
path protection, 1-61 PDH ports, 4-67
SDH/SONET subsystem E1 parameters, 4-69
integration with Ethernet traffic subsystem, 1- LVC parameters, 4-67, 4-74
35 path protection, 4-74
virtual concatenation, 1-38 T1 parameters, 4-72
CLOCK connector, 2-19 physical ports parameters, 4-38
connection cable SDH/SONET physical ports
balanced interface, A-5 card configuration, 4-51
unbalanced interface, A-5 common PDH LVC parameters, 4-54
connector data, A-4 DCC parameters, 4-55
LOS indicator, 2-19 link parameters, 4-54
ON indicator, 2-19 serial port parameters, 4-21
Clock Source signaling profile parameters, 4-36
EntryNum, 4-125 station clock, 4-43
Port, 4-125 system clock sources, 4-123
Slot, 4-125 system parameters, 4-10
Configuration, 3-19 TS assignment, 4-130
Configuration errors, 6-2 typical application
list, 6-2 Ethernet transport, 5-4
Configuration menu, 3-20 SONET transport, 5-43
Configuration procedure VCG, 4-94
Alarms, 4-151 GFP encapsulation, 4-103
alarm attributes, 4-152 LAPS encapsulation, 4-95
alarm priority, 4-160 VCG redundancy, 4-105
alarm reporting, 4-158 Redundancy Port, 4-108
alarm threshold window, 4-162 Redundancy Slot, 4-108
APS, 4-127 Revertive, 4-108
I-2 Megaplex-4100 Ver. 2.0

Installation and Operation Manual Index
virtual ports parameters, 4-59 diagnostic task selection, 6-130

virtually concatenated groups, 4-94 menu, 3-37, 6-129
Configuration>Applications, 3-32, 4-85 physical ports, 6-130
Configuration>DB Tools, 3-32, 4-3 virtual ports, 6-136
Configuration>Physical Ports Dir function, 4-172
SDH, 3-26, 4-39 Display Time Slots, 4-133
SONET, 3-27, 4-40 Download to Cards, B-10
Configuration>System, 3-21, 3-22, 4-11 Downloading
SDH, 4-12 Boot menu, B-3, B-13
SONET, 3-23, 4-13 X-modem transfer, B-13
Configuration>Virtual Ports File Utilities, B-2, B-4
SDH, 3-28, 4-60 downloading to CL Ethernet traffic subsystem,
SONET, 3-30, 4-62 B-2
Connect Time Slots, 4-133 downloading to CL modules, B-2
Connections, 2-26 downloading to CL SDH/SONET subsystem, B-2
alarm port, 2-9 downloading to I/O modules, B-3
CL modules, 2-8, 2-9 software image types, B-1
E1 port, 2-6 DS0 cross-connect matrix, 1-25
Ethernet port, 2-7 DS0 cross-connect mode, 1-26
SDH port, 2-7 DS1 cross-connect mode, 1-26
SHDSL port, 2-6
SONET port, 2-7 —E—
station clock, 2-7
E1
T1 port, 2-6
CAS, C-4
Contact Person, 4-34
CRC-4, C-4
CONTROL DCE, 2-19
frame format, C-2
connection data, A-1
line alarm, C-5
connector data, A-1
excessive BER, C-5
CONTROL ETH, 2-19
line signal characteristics, C-2
ACT indicator, 2-19
loss of frame synchronization, C-5
connection data, A-3
loss of multiframe alignment, C-5
connector data, A-3
multiframes, C-3
LINK indicator, 2-19
basic G.704 framing, C-3
Cross Connect
G.704 timeslot 16 multiframe, C-4
E1, 4-70
timeslot 0, C-3
T1, 4-73
E1 and T1 statistics, 15-minute
Customer’s edge, 1-41
CRC Average Error per Second, 6-90
CRC Error per Second, 6-90
—D— Current BES, 6-90
DATA, 4-136 Current ES, 6-90
DB Tools, 3-32, 4-3 Current Loss of Frame Counter (LOFC), 6-90
DC power connector data, A-6 Current SES, 6-90
DCC, C-19 Current Slip Second Counter (CSS), 6-90
DCC statistics Current UAS, 6-90
Rx CRC Error, 6-110 ESF Error, 6-90
Rx Dropped, 6-110 E1 and T1 statistics, 24-hour
Rx Total Bytes, 6-110 BES, 6-93
Rx Total Frames, 6-110 CSS, 6-93
Tx Total Bytes, 6-110 Current Degraded Minutes, 6-93
Tx Total Frames, 6-110 ES, 6-93
Default DB, 4-4 Last Degraded Minutes, 6-93
Define Alarm Attributes, 4-151 LOFC, 6-93
Define Alarm Priority, 4-151 SES, 6-93
Define Alarm Report, 4-151 UAS, 6-93
Define Alarm Window, 4-152 EED Threshold
Delete DB, 4-4 PDH ports, 4-75
Delete Time Slots SDH/SONET link, 4-55
number of TS, 4-133 STS-1, 4-81
per slot and port, 4-133 VC-12, 4-100
Deleting files, 4-173 VC-3, 4-101
Deviation Type VC-4, 4-79
DCC, 4-57 Encapsulation, 1-38
Device Name, 4-34 ESD, 2-3
Diagnostics, 1-80, 3-19, 6-119 ETH Counters
Megaplex-4100 Ver. 2.0 I-3

Rx 1024b-max Frames, 6-117 HDLC, 1-42

Rx 128b-255b Frames, 6-117 MLPPP, 1-43
Rx 256b-511b Frames, 6-117 Ethernet flows, 1-44
Rx 512b-1023b Frames, 6-117 Ethernet service model
Rx 64b Frames, 6-117 customer’s edge, 1-41
Rx 65b-127b Frames, 6-117 service provider’s edge, 1-41
Rx Broadcast Frames, 6-117 Ethernet services subsystem, 1-42
Rx Correct Frames, 6-117 OAM, 1-46
Rx Dropped, 6-117 VLAN-aware, 1-45
Rx Fragment Frames, 6-117 VLAN-unaware, 1-45
Rx Invalid CRC Frames, 6-117 Ethernet transmission
Rx Jabber Frames, 6-117 autonegotiation, C-33
Rx Multicast Frames, 6-117 bridging, C-35
Rx Oversized Frames, 6-118 frame structure, C-34
Rx Pause Frames, 6-117 FCS, C-34
Rx Total Bytes, 6-117 length/type, C-34
Rx Total Frames, 6-117 MAC client data, C-34
Rx Undersized Frames, 6-118 MAC DA, C-34
Total Collision, 6-118 MAC SA, C-34
Tx Correct Frames, 6-118 padding, C-34
Tx Discard Frames, 6-118 preamble, C-34
Tx Total Bytes, 6-118 SFD, C-34
Tx Total Frames, 6-118 introduction, C-31
Tx Unicast Frames, 6-118 LAN, C-31
Ethernet flows media access, C-32
configuration, 4-110 VLAN, C-35
management flow, 4-116 EVCs, C-39
traffic flow, 4-111 Extended Signal Label
Ethernet port statistics VC-12, 4-100
Errors, 6-99 VC-3, 4-101
Oversized Frames, 6-99 External feed and ring connections, 2-27
Rx 1024-long Octets, 6-99
Rx 128-255 Octets, 6-99 —F—
Rx 256-511 Octets, 6-99
Fault propagation
Rx 512-1023 Octets, 6-99
configuration, 4-149
Rx 64 Octets, 6-99
FDL Type, 4-73
Rx 65-127 Octets, 6-99
Feed and ring voltage sources, 1-80
Rx Broadcast Frames, 6-99
File Utilities, 3-19, 3-38, 4-164
Rx Correct Frames, 6-98
Download/upload by TFTP
Rx Discard Frames, 6-99
Config Download, 4-167
Rx FCS Errors, 6-98
Config Upload, 4-167
Rx Fragment Errors, 6-98
SW Download, 4-166
Rx Jabber Errors, 6-98
File system
Rx Multicast Frames, 6-99
Delete File, 4-173
Rx Pause Frames, 6-98
Dir function, 4-172
Rx Total Frames, 6-98
TFTP
Rx Total Octets, 6-98
Client File Name, 4-166, 4-170, B-6, B-9
Rx Unicast Frames, 6-99
Command, B-7
Tx Broadcast Frames, 6-99
download configuration files, 4-168
Tx Correct Frames, 6-99
downloading to CL modules, B-5
Tx Multicast Frames, 6-99
downloading to I/O modules, B-11
Tx Total Collisions, 6-99
File #, 4-170, B-9
Tx Total Frames, 6-99
preparations for transfer, B-4
Tx Total Octets, 6-99
Server IP, 4-166, 4-170, B-6, B-9
Tx Unicast Frames, 6-99
to I/O modules, 4-168
Undersized Frames, 6-99
update CL software, 4-166, B-5
Ethernet port status
update SDH/SONET software, B-7
Auto Negotiation, 6-96
upload configuration files, 4-168
Connector Type, 6-96
Flow Control
Operation Status, 6-96
GbE port, 4-47
Speed and Duplex, 6-96
Flows, 1-44, C-39
Ethernet services, 1-40, C-36
Ethernet flow configuration, 4-110
E-LAN, 1-42
Ethernet management flow configuration, 4-116
E-line, 1-41
add new management flow, 4-117
Ethernet bundles, 1-42

BP, 4-119 Only Receive, 4-105

BP User Name, 4-120 Only Transmit, 4-105
Host NMS Source, 4-120 Ground connection, A-6
mapping bridge ports, 4-118 Grounding, 2-2, 2-26
Port, 4-120
Rate, 4-120 —H—
Slot, 4-120
Hardware Problems
User Name, 4-118
troubleshooting, 6-143
VLAN ID, 4-118
HDLC bundles, 1-42
VLAN Priority Tag, 4-118
configuration, 4-86
Ethernet traffic flow configuration, 4-111
Admin Status, 4-88
add new traffic flow, 4-112
L2 Protocol, 4-89
BP, 4-114
Link OAM, 4-89
BP User Name, 4-115
Link OAM Mode, 4-90
C-VLAN ID, 4-114
Number of TS, 4-89
C-VLAN Type, 4-114
Rate, 4-89
E-LINE, 4-112
mapping bridge ports, 4-112
Source Port, 4-90
Port, 4-114
Source Slot, 4-90
Rate, 4-115
User Name, 4-88
Slot, 4-114
timeslot assignment, 4-90
SP-VLAN, 4-114
Host IP
User Name, 4-112
Default Gateway, 4-29
Frame Structure
Host IP Address, 4-29
SDH/SONET card parameters, 4-52
Read community, 4-29
Frame Type
Subnet Mask, 4-29
E1, 4-69
Traps community, 4-30
T1, 4-72
Write community, 4-30
Functional description
HVC (SDH)
CL.1 modules, 1-21
All Ports, 4-78
CL.1/155 modules, 1-23
Port 1, 4-78
CL.1/155GbE modules, 1-25
Port 2, 4-78
CL.1/GbE modules, 1-20
HVC (SONET)
All Ports, 4-80
—G— Common Parameters, 4-80
GbE Port 1, 4-80
All Ports, 4-46 Port 2, 4-80
physical ports configuration, 4-45
Redundancy, 4-48 —I—
GbE connector, 2-20
I/O modules, 1-6
ACT indicator, 2-20
connections, 2-29
LINK indicator, 2-20
installation, 2-24
GbE Ethernet switch, 1-36
Supported modules, 1-7
flow control, 1-37
I/O ports
back pressure, 1-37
monitoring
pause frames, 1-37
physical ports, 6-84
forwarding algorithms, 1-38
virtual ports, 6-58
VLAN support, 1-38
Idle Code
GbE port
E1, 4-70
flow control, 4-47
T1, 4-73
Max. Capability Advertised, 4-47
Inband Management
GbE port interfaces, 1-36
DCC, 4-56
GFP, C-39, C-40
E1, 4-72
GFP configuration
T1, 4-73
Core Scrambling, 4-105
Indications
Delta, 4-104
normal
FCS, 4-104
CLOCK interface status, 3-4
Payload Scrambling, 4-105
CONTROL ETH interface status, 3-3
PTI For Client Data, 4-104
GbE interface status, 3-3
UPI For Client Data, 4-104
SDH/SONET interface status, 3-3
GFP Multiplexing, C-41
system, 3-3
GFP parameters
Init Alarm Priority, 4-152
Core Scrambling
Init Alarm Report, 4-152
Both Sides, 4-105
Installation

blank panels, 2-24 STS-1, 4-81

bracket attachment, 2-25 VC-3, 4-101
CL modules, 2-17, 2-22 VC-4, 4-79
coaxial connections, 2-29 J2 Path Trace
connecting to CL module, 2-27 PDH ports, 4-75
connections, 2-27 VC-12, 4-100
module panel, 2-17 J2 Received
optical connections, 2-28 VC-12, 6-75
connecting coaxial cables, 2-29 VT1.5, 6-75
connecting optical cables, 2-28 J2 Rx Path Trace
connecting power, 2-27 PDH ports, 4-75
grounding, 2-26 VC-12, 4-99
I/O modules, 2-24
connecting to I/O modules, 2-29 —L—
Megaplex-4100
LAPS, C-39
cable connections, 2-26
LAPS configuration parameters
external feed and ring connections, 2-27
Address, 4-102
front panel, 2-13
Control, 4-102
rear panel, 2-12
SAPI Value, 4-102
Megaplex-4100 enclosure, 2-25
LCAS, 1-40
brackets for 19 in. racks, 2-25
LCAS Path Info parameters, 6-82
brackets for 23 in. racks, 2-26
Sink State, 6-83
PS modules, 2-14
Source State, 6-82
internal setting, 2-15
VC Number, 6-82
panels, 2-14
LINK connector, 2-19
removing, 2-17
LOS indicator, 2-20
requirements
ON LINE indicator, 2-20
AC power, 2-5
Load DB, 4-4
ambient, 2-9
Load HW, 4-4
DC power, 2-5, A-6
Location ID, 4-34
electromagnetic compatibility, 2-10
Log-in, 3-5
front and rear panel clearance, 2-9
Logistic (inventory) information, 4-174
site requirements, 2-5
Loopbacks
SFP, 2-21
E1 or T1 port
Inventory menu, 3-19, 4-174
local, 6-123
SW/HW Rev, 4-175
remote, 6-124
Hardware Revision, 4-176
E1 or T1 timeslots
Installed Card, 4-176
local, 6-124
Programmed Card, 4-176
remote, 6-125
Slot, 4-176
global PDH
Software Version, 4-176
local, 6-126
System, 4-174
remote, 6-127
Hardware Revision, 4-175
I/O port
Software Version, 4-175
local, 6-123
System Description, 4-175
remote, 6-123
IP environment
LVC
IP address, C-43
local, 6-126
host portion, C-45
remote, 6-126
network portion, C-44
PDH port
subnet masks, C-46
local, 6-127
subnetting, C-45
remote, 6-127
IP connectivity check, C-48
PDH port timeslots
IP hosts, C-43
local, 6-127
IP networks, C-43
remote, 6-128
IP packet, C-44
SDH/SONET link
IP ports, C-43
local, 6-125
IP routing, C-47
remote, 6-125
LVC configuration
—J— PDH ports
J1 Path Trace EED Threshold, 4-75
STS-1, 4-83 J2 Path Trace, 4-75
VC-3, 4-101 J2 Rx Path Trace, 4-75
VC-4, 4-79 Mapping Mode, 4-75
J1 Rx Path Trace Padding, 4-75

Payload Label, 4-76 typical applications, 1-12

Protection Mode, 4-75 Menu structure
Protection Partner, 4-76 Configuration menu, 3-20
SD Threshold, 4-75 Configuration>Applications, 3-32, 4-85
Configuration>DB Tools, 3-32, 4-3
—M— Configuration>Physical Ports
SDH, 3-26, 4-39
Main menu, 3-18
SONET, 3-27, 4-40
Management DCC, 4-57
Configuration>System, 3-21, 3-22, 4-11
Management subsystem, 1-73
SDH, 4-12
access options, 1-74
SONET, 3-23, 4-13
alarm collection, 1-79
Configuration>Virtual Ports
SDH, 3-28, 4-60
CL module functions, 1-73
SONET, 3-30, 4-62
CL module redundancy, 1-78
Diagnostics menu, 6-129
Ethernet port, 1-75
SDH and SONET, 3-37
inband management access
File Utilities menu, 3-38, 4-164
via PSN, 1-77
Inventory menu, 3-19
via TDM links, 1-75
Main menu, 3-18
remote updating, 1-74
Monitoring menu
serial port, 1-75
SDH, 3-33, 3-34, 6-44, 6-45
statistics support, 1-79
SONET, 3-35, 3-36, 6-46, 6-47
Manual timeslots assignment, 4-133
MLPPP bundles, 1-43
Mapping
configuration, 4-91
SDH/SONET links, 4-141
Admin Status, 4-93
bypassing, 4-145
L2 Protocol, 4-93
map display, 4-142
Link OAM, 4-93
menu mapping mode, 4-143
Link OAM Mode, 4-93
path protection, 4-147
MLPPP MTU, 4-93
Max. Capability Advertised
Number of Links, 4-93
GbE port, 4-47
Rate, 4-93
MEF, C-36
Megaplex-4100
Slot, 4-93
CL modules, 1-10
Source Port, 4-93
management functions, 1-73
User Name, 4-93
module installation, 2-17
MNG, 4-134, 4-136
SFP installation, 2-21
Monitoring, 3-19
connections
GbE port, 6-113
external feed and ring voltages, 2-27
Admin Status, 6-115
enclosure description, 1-4, 2-12, 2-25
ETH Counters, 6-115
Ethernet services, 1-40
Link Status, 6-115
service model, 1-40
Port Status, 6-115
feed and ring voltage sources, 1-80
Rate, 6-115
front panel, 2-13
Rdn Status, 6-115
I/O modules, 1-6
SFP, 6-115
indicators, 2-13
SDH/SONET port, 6-105, 6-111
installation
DCC statistics, 6-110
bracket attachment, 2-25
link statistics, 6-108
enclosure, 2-25
optical parameters, 6-110
power supply subsystem, 1-80
SFP, 6-110
PS modules, 1-12, 1-84
status, 6-106
installation, 2-14
Monitoring menu
rear panel, 2-12
active alarms, 6-48, 6-50
redundancy, 1-58
Alarms, 6-15
1+1 unidirectional protection, 1-58
Bundles, 6-62
dual cable (parallel TX) redundancy, 1-65
Rx Statistics - Total Errors, 6-63
E1/T1 ring, 1-66
Rx Statistics - Total Frames, 6-63
link, 1-64
Rx Statistics - Total Octets, 6-63
PSN interface, 1-62
Tx Statistics - Congestion Dropped, 6-63
SDH/SONET interface, 1-58
Tx Statistics - Total Errors, 6-63
virtually concatenated group, 1-63
Tx Statistics - Total Frames, 6-63
Y-cable redundancy, 1-65
Tx Statistics - Total Octets, 6-63
ringer options, 1-12
CL physical ports, 6-100
technical specifications, 1-81
GbE Ethernet subsystem, 6-113
timing subsystem, 1-46
GbE port, 6-113

SDH/SONET port, 6-105, 6-111 Protection Mode, 4-75

SDH/SONET subsystem, 6-103 Protection Partner, 4-76
station clock, 6-101 Status
CL Status Current, 6-112
Active DB, 6-54 Payload, 6-112
Alarm Severity, 6-54 Protection, 6-112
CL Temperature, 6-55 Working, 6-112
Configuration File Usage, 6-54 Payload Label
DB Checksum, 6-54 PDH ports, 4-76
Last DB Update, 6-54 VC-12, 4-100
System Control Activity, 6-54 VC-3, 4-101
Test Status, 6-54 Payload mapping
CL virtual ports, 6-63 SDH/SONET links, 4-141
STS-1, 6-66 bypassing between links, 4-145
VC-12, 6-74 map display, 4-142
VC-3, 6-71 menu mapping mode, 4-143
VC-4, 6-66 path protection, 4-147
VCAT, 6-77 PDH
VT1.5, 6-74 All Ports, 4-68
I/O Ethernet physical ports, 6-94 PDH overview, C-1
statistics, 6-96 Physical ports
status, 6-95 configuration, 4-38
I/O physical ports, 6-84 diagnostics, 6-130
signaling, 6-94 monitoring, 6-83
I/O TDM physical ports, 6-86 Power
statistics, 6-88 AC, 2-5
Status, 6-87 DC, 2-5, A-6
I/O virtual ports, 6-58 floating source, 2-5
signaling, 6-60 positive source terminal grounded, 2-5
monitoring task selection, 6-48 POWER SUPPLY indicator, 2-14
physical ports, 6-83 Power supply subsystem, 1-80
SDH, 3-33, 3-34, 6-44, 6-45 Preliminary configuration, 3-6
SONET, 3-35, 3-36, 6-46, 6-47 Primary
system E1, 4-72
APS status, 6-56 T1, 4-73
CL status, 6-53 Protection
remote agents, 6-55 1+1 unidirectional protection, 1-58
system timing, 6-53 Protection Mode
virtual ports, 6-57 PDH ports, 4-75
Monitoring power-up sequence, 3-1 Protection Partner
PDH ports, 4-76
—O— PS modules, 1-12, 1-84
installation, 2-14
Object ID, 4-34
internal settings, 2-15
OC-3, C-29
panels, 2-14
ON LINE indicator, 2-19
removing, 2-17
Operating
PSN interface
turning on, 3-2
redundancy, 1-62
Optical parameters
Laser Bias, 6-111
Laser Temp, 6-111 —R—
Rx Optical Power, 6-111 RDI on Fail
SFP Inserted, 6-111 SDH/SONET link, 4-55
Supply Voltage, 6-111 RDI on Path Trace
Tx Optical Power, 6-111 LVC, 4-54
STS-1, 4-81
—P— VC-12, 4-101
VC-3, 4-101
Package contents, 2-11
VC-4, 4-79
Padding
RDI on Payload Label
PDH ports, 4-75
VC-12, 4-100
STS-1, 4-83
VC-3, 4-101
Path protection, 1-61
RDI on Signal Label
configuration, 4-74
LVC, 4-54
PDH ports
STS-1, 4-81
Mapping Mode, 4-75

VC-4, 4-78 VC-3, 4-101

Redundancy, 1-58 VC-4, 4-79
CL modules, 1-78 SDH
E1, 4-70 AU pointers, C-19
E1, T1 link, 1-64 DCC, C-20
GbE port, 4-47 frame organization, C-13
link implementation, C-11
dual cable (parallel TX) redundancy, 1-65 J1 byte, C-20
E1/T1 ring, 1-66 maintenance signals, C-25
Y-cable redundancy, 1-65 AIS, C-25
PSN interface, 1-62 AIS AU Path, C-26
SDH/SONET interface, 1-58 AIS TU Path, C-26
T1, 4-73 alarms, C-26
virtually concatenated groups, 1-63 FERF, C-25
Redundancy Channel HO Path FERF, C-26
E1, 4-71 HO Path RAI, C-26
T1, 4-73 LO Path FERF, C-26
Redundancy Port LO Path RAI, C-26
GbE port, 4-50 LOF, C-25
Redundancy Slot LOP, C-25
E1, 4-71 LOS, C-25
GbE port, 4-50 MS-FERF, C-25
T1, 4-73 OOF, C-25
Remote agents, 6-55 MSOH, C-19
Interface, 6-56 overhead data, C-17
IP Address, 6-55 DCC, C-19
Logical Distance, 6-56 K1, K2 bytes, C-20
Mux Name, 6-55 RSOH, C-18
Physical Distance, 6-55 path trace message, C-20
Required equipment, 2-11 principles, C-11
Reset, 6-18 section overhead, C-13
Restoration Time signal structure, C-12
E1, 4-70 STM-1
T1, 4-73 frame format, C-15
Revertive pointers, C-16
GbE port, 4-49 tributary units, C-22
Ring sources, 1-80 frame structure, C-22
Routing Protocol SDH hierarchy, C-23
DCC, 4-57 TU-11, C-22
E1, 4-72 TU-12, C-22
ETH, 4-28 TU-2, C-23
T1, 4-73 TU-3, C-23
types, C-22
—S— VC (virtual container), C-13
VC assembly/disassembly, C-14
S/W & File Transfer CL, 4-166, 4-169, 4-171, 4-
VC-4 path overhead, C-20
172, B-6
SDH/SONET
S/W & File Transfer I/O and S-Subsystem, B-8, B-
All Links, 4-51
10
Card Configuration, 4-51
Download to Cards, B-11
card configuration parameters
Download to I/O modules, B-11
Fallback Port, 4-53
Safety, 2-1
Frame Structure, 4-52
ESD, 2-3
Master Port, 4-53
grounding, 2-2
SDH/SONET Tx Clock, 4-53
laser, 2-3
Tx Clock Based on SSM, 4-53
module handling, 2-4
Link 1, 4-51
Sanity errors, 6-2
Link 2, 4-51
errors, 6-2
physical ports
list, 6-2
card configuration parameters, 4-51
warnings, 6-2
common PDH LVC parameters, 4-54
SD Threshold
DCC parameters, 4-55
PDH ports, 4-75
link parameters, 4-54
SDH/SONET link statistics, 6-108
STS-1, 4-81
DCC statistics, 6-110
VC-12, 4-100
SDH/SONET link status

Line Status, 6-107 VC-4, 4-79

S1 Value, 6-107 Signaling monitor, 6-60, 6-94
Section Status, 6-107 Rx from CLX, 6-61
SFP, 6-107 Rx from Link, 6-61
SDH/SONET subsystem Ts#, 6-61
APS, 1-32 Tx to CLX, 6-61
CL.1/155, 1-29 Tx to Link, 6-61
CL.1/155GbE, 1-29 Type, 6-61
E1/T1 framers and mappers, 1-33 Site requirements, 2-5
framer subsystem, 1-31 AC power, 2-5
integration with Ethernet traffic subsystem, 1- ambient, 2-9
35 connections
link monitoring, 6-105 alarm port, 2-9
optical parameters, 6-110 E1, 2-6
path protection status, 6-111 Ethernet, 2-7
statistics, 6-108 Ethernet management port, 2-8
status, 6-106 optical cables, 2-7
link protection mechanisms, 1-32 SDH, 2-7
mapping matrix, 1-33 serial port, 2-9
monitoring, 6-103 SHDSL, 2-6
link, 6-105 SONET, 2-7
path protection status, 6-111 station clock, 2-7
timing, 6-103 T1, 2-6
network port interfaces, 1-31 DC power, 2-5
ALS, 1-31 electromagnetic compatibility, 2-10
STS-1 cross-connect matrix, 1-31 front and rear panel clearance, 2-9
timing subsystem, 1-33 SNMP
SDH/SONET Timing communication requirements, 3-41
Based on SSM, 6-104 general, C-48
Holdover, 6-105 management domains, C-50
Port, 6-105 principles, C-48
Rx SSM, 6-105 traps, C-51
Tx Clock Source, 6-105 SONET, C-28
Tx SSM, 6-105 OC-3, C-29
SDH/SONET Tx Clock, 4-53 SPE, C-29
Serial Port STS-1, C-29
Baud Rate, 4-21 STS-3, C-29
Security Timeout, 4-21 VT, C-29
Service provider’s edge, 1-41 Source
SFP Internal, 4-124
GbE, 6-115 Rx Clock, 4-124
installation, 2-21 SPE, C-29
SHDSL Speed & Duplex
frame format, C-9 GbE port, 4-47
modulation method, C-9 Split timeslots, 4-133, 4-134
overview, C-8 SSM
subsystem structure, C-9 values, 6-102
SHDSL statistics, 15-minute S-Subsystem, 4-124
Actual Power Backoff, 6-91 Station Clock
Current CRC Anomalies, 6-91 Admin Status, 4-43
Current ES, 6-90 Cable Type, 6-102
Current LOSW, 6-91 Clock Rate, 4-44
Current LOSWS, 6-91 Interface Type, 4-44
Current SES, 6-91 Line Code, 4-44
Current UAS, 6-91 Rx Gain Limit, 4-44
Loop Attenuation, 6-91 Rx Source, 4-45
SNR Margin, 6-91 Rx SSM, 6-102
SHDSL statistics, 24-hour SSM, 4-45
Current CRC Anomalies, 6-93 Status, 6-102
Current ES, 6-93 Transmit Timing Source, 4-44
Current LOSWS, 6-93 Statistics, 1-79
Current SES, 6-93 STM-1
Current UAS, 6-93 frame format, C-15
Signal Label pointers, C-16
STS-1, 4-83 timing differences, C-16

VC-4, C-16 parameters, 4-28

STS-1, C-29 Load HW, 3-8
C2 Received, 6-67 log-in, 3-5
CV, 6-69 Management, 3-10
Elapsed Time, 6-69 management access, 4-30
ES, 6-69 Manager List, 3-10, 4-31
Interval Number, 6-69 managing databases, 4-2
J1 Received, 6-67 Mng Access, 3-10
monitoring, 6-66 preliminary configuration, 3-4
SES, 6-69 sequence, 3-6
UAS (SEFS), 6-69 terminal, 3-5
Valid Intervals, 6-69 reloading factory defaults, 4-16
STS1/SPE, 4-109 reset device, 4-17
STS-3, C-29 serial port parameters, 4-21
Supervision terminal, 3-11, 3-16 Set Date Format, 3-10
ending terminal session, 3-17 Signaling Profile, 4-36
general procedures, 3-15 SNMP
menu structure communication requirements, 3-41
Configuration menu, 3-20 SNMP Access, 3-10
Configuration>Applications, 3-32, 4-85 Speed, 3-9
Configuration>DB Tools, 3-32, 4-3 supervision terminal, 3-11
Configuration>Physical Ports, 4-39, 4-40 Telnet, 3-39
Configuration>Physical Ports (SDH), 3-26 communication requirements, 3-39
Configuration>Physical Ports (SONET), 3-27 general procedures, 3-39
Configuration>System, 3-21, 4-11 Telnet Access, 3-10
Configuration>System (SDH), 3-22, 4-12 timing flow
Configuration>System (SONET), 3-23, 4-13 clock interfaces, 4-43
Configuration>Virtual Ports (SDH), 3-28, 4-60 station clock interfaces, 4-43
Configuration>Virtual Ports (SONET), 3-30, 4- Update DB, 3-9, 3-10
62 Web
Diagnostics menu, 6-129 communication requirements, 3-40
Diagnostics menu (SDH and SONET), 3-37 Web Access, 3-10
File Utilities menu, 3-38, 4-164 SYSTEM TEST indicator, 2-14
Inventory menu, 3-19
Main menu, 3-18 —T—
Monitoring menu (SDH), 3-33, 3-34, 6-44, 6-
T1
45
AIS, C-5, C-8
Monitoring menu (SONET), 3-35, 3-36, 6-46,
alarm, C-8
6-47
AIS, C-8
power-up process, 3-13
FDL, C-7
saving changes, 3-16
frame format, C-6
terminal screen description, 3-13
ESF, C-7
bottom line, 3-14
SF (D4), C-7
header, 3-14
line signal, C-5
save, 3-14
red alarm, C-8
status indicator, 3-14
yellow alarm, C-8
work area, 3-14
TDM link
Sys Description, 4-34
dual cable (parallel TX) redundancy, 1-65
System configuration
E1/T1 ring, 1-66
Alarms, 4-151
timing, 1-68
alarm attributes, 4-152
redundancy, 1-64
alarm priority, 4-160
Y-cable redundancy, 1-65
Technical specifications, 1-81
alarm threshold window, 4-162
Technical support, 6-145
Card Type, 3-9
Telnet, 3-39
card types, 4-18
communication requirements, 3-39
clock sources, 4-122
general procedures, 3-39
configuration options, 3-4
Test and Loopbacks, 6-119
Control Port, 3-9, 4-20
Testing, 6-119
Date & Time, 3-10, 4-35
TFTP, 4-166, 4-169, 4-171, 4-172, B-6, B-8
Default DB, 3-8
Client file name, 4-166, 4-170, B-6, B-9
device info, 4-34
Command, B-7
ETH port, 4-26
Config Download, 4-167
Factory Defaults, 3-9, 4-16
Config Upload, 4-167
Host IP, 3-9

downloading/uploading files, 4-166 Elapsed Time, 6-69

File #, 4-170, B-9 ES, 6-69
Server IP, 4-166, 4-170, B-6, B-9 Interval Number, 6-69
SW Download, 4-166 J1 Received, 6-67
Time, 6-4 monitoring, 6-66
Timeslots SES, 6-69
types, 1-28 UAS (SEFS), 6-69
Timing Valid Intervals, 6-69
data channels, 1-54 VCG, C-30
DCE mode, 1-54 encapsulation, 1-38
DTE mode, 1-55 mapper function, 1-39
external DCE mode, 1-54 monitoring, 6-77
ISDN channels, 1-55 LCAS Path Info, 6-82
S interface, 1-55, 1-56 WAN side, 6-77
U interface, 1-56 redundancy, 1-63
system VCG configuration, 4-94
internal timing, 1-49 Admin Status, 4-96
Rx timing, 1-49 EED Threshold
S-Subsystem timing, 1-50 VC-12, 4-100
station timing, 1-51 VC-3, 4-101
station timing applications, 1-52 Encapsulation, 4-97
system timing, 1-47 Extended Signal Label
clock sources, 1-48 VC-12, 4-100
timing subsystem, 1-46 VC-3, 4-101
Traps, 6-39 GFP encapsulation, 4-103
list, 6-40 SDH links, 4-103
OID, 6-40 SONET links, 4-109
Troubleshooting J1 Path Trace
hardware problems, 6-143 VC-3, 4-101
preliminary checks, 6-143 J1 Rx Path Trace
TS assignment VC-3, 4-101
bundle of timeslots, 4-136 J2 Path Trace
individual timeslots, 4-134 VC-12, 4-100
Turn off, 3-4 J2 Rx Path Trace
Tx Clock Based on SSM VC-12, 4-99
SDH/SONET card parameters, 4-53 LAPS Configuration, 4-98
LAPS encapsulation, 4-95
—U— SDH links, 4-95
SONET links, 4-109
UNI BRD D, 4-134, 4-136
LCAS, 4-97
UNI BRD V, 4-134, 4-136
LVC Configuration, 4-98
Unidirectional broadcast
Minimum Number of VCs, 4-98
general description, 1-28
Number of VCs, 4-97
unidirectional receive, 1-29
Payload Label
unidirectional transmit, 1-29
VC-12, 4-100
voice timeslot, 1-29
VC-3, 4-101
Update DB, 4-4
RDI on Path Trace
User Name
VC-12, 4-101
E1, 4-69
VC-3, 4-101
ETH, 4-28
RDI on Payload Label
GbE port, 4-47
VC-12, 4-100
VC-3, 4-101
T1, 4-72
Redundancy, 4-98, 4-105
Redundancy Port, 4-108
—V— redundancy Revertive, 4-108
V5 (Bits 5-7) Received Redundancy Slot, 4-108
VC-12, 6-75 SD threshold
VT1.5, 6-75 VC-12, 4-100
VC-12 SD Threshold
monitoring, 6-74 VC-3, 4-101
VC-3 VC Type, 4-97
monitoring, 6-71 VCG Name, 4-98
VC-4 Virtual Concatenation, 4-97
C2 Received, 6-67 Wait to Restore, 4-108
CV, 6-69 Virtual Concatenation, 1-38, C-29

encapsulation, 1-38 Interval Number, 6-79

GFP, 1-38 LAPS encapsulation, 6-78
LAPS, 1-38 Number of Total Rx Frames, 6-79
LCAS, 1-40 Number of Total Tx Frames, 6-79
Virtual Ports Receive Abort Frames, 6-79
Bundles, 4-64 Receive Address Field Mismatch Counter, 6-79
CL, 4-64 Receive Control Field Mismatch Counter, 6-79
configuration, 4-59 Receive SAPI Field Mismatch Counter, 6-79
HVC, 4-66 Rx Payload Max Length Violation, 6-79
I/O, 4-64 Rx Payload Min Length Violation, 6-79
monitoring, 6-57 Rx Statistics
PDH, 4-66 Elapsed Time, 6-81
VCAT, 4-66 FCS Error, 6-81
Virtually concatenated group, C-30 Interval Number, 6-81
configuration, 4-94 Number of Total Rx Frames, 6-81
redundancy, 1-63 Number of Total Tx Frames, 6-81
VLAN, C-35 Receive cHEC Single Bit Error, 6-81
priority, C-35 Receive CID Mismatch, 6-81
VLAN ID, C-36 Receive eHEC Multi Bit Error, 6-81
VOICE, 4-136 Receive eHEC Single Bit Error, 6-81
VT, C-29 Receive EXI Mismatch, 6-81
VT Type, 4-109 Receive Idle Frame Error, 6-81
VT1.5, 4-109 Receive PTI Mismatch, 6-81
monitoring, 6-74 Receive tHEC Multi Bit Error, 6-81
Receive tHEC Single Bit Error, 6-81
—W— Receive UPI Mismatch, 6-81
Rx Payload Max Length Violation, 6-81
Wait to Restore
Start Time, 6-81
E1, 4-71
Valid Intervals, 6-81
GbE port, 4-49
Valid Intervals, 6-79
T1, 4-73
Web browser
WAN Statistics
communication requirements, 3-40
Byte De-stuffing Violations, 6-79
Elapsed Time, 6-79
FCS Error, 6-79 —X—
GFP encapsulation, 6-79 xNI, C-38


24 Raoul Wallenberg Street, Tel Aviv 69719, Israel
Tel: +972-3-6458181, Fax +972-3-6483331, +972-3-6498250
E-mail: erika_y@rad.com, Web site: http://www.rad.com
Customer Response Form

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

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

End user
VAR
Other
Who is your distributor?
Your name and company:
Job title:
Address:
Direct telephone number and extension:
Fax number:
E-mail:
Publication No. 464-200-12/08
Order this publication by Catalog No. 803726
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@rad.com
www.rad.com The Access Company

MP4100

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MP4100

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

The Access Company

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

© 1988–2008 RAD Data Communications Ltd. Publication No. 464-200-12/08

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

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

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

Instructions générales de sécurité

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

Manipuler des produits sous tension

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

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

Manufacturer's Name: RAD Data Communications Ltd.

Tel Aviv, 7 August, 2007

European Contact: RAD Data Communications GmbH, Otto-Hahn-Str. 28-30, 85521

Megaplex-4100 Ver. 2.0 i

Management Alternatives ................................................................................. 1-75

ii Megaplex-4100 Ver. 2.0

Removing a CL Module ..................................................................................... 2-21

Megaplex-4100 Ver. 2.0 iii

iv Megaplex-4100 Ver. 2.0

Configuring HVC Virtual Ports ............................................................................ 4-94

Chapter 5. Configuring Typical Applications

Megaplex-4100 Ver. 2.0 v

Configuring the Clock Source ............................................................................ 5-31

Chapter 6. Troubleshooting and Diagnostics

vi Megaplex-4100 Ver. 2.0

VCG WAN Side Statistics – LAPS Encapsulation .................................................. 6-37

Megaplex-4100 Ver. 2.0 vii

Diagnosing the CL.1/155 and CL.1/155GbE Virtual Ports ................................. 6-157

Appendix A. Connection Data

viii Megaplex-4100 Ver. 2.0

+ 72V + 72V CLASS CLASS

PS Slots I/O Slots CL Slots I/O Slots

Megaplex-4100 Ver. 2.0 1

Preparations for Configuration

2 Megaplex-4100 Ver. 2.0

Preliminary Configuration Sequence

Step Action Using …

1 Select the default database, 1 Configuration>DB Tools>Default DB

3 Configure the preliminary set of IP Configuration>Quick Setup

Megaplex-4100 Ver. 2.0 3

General Application Configuration Sequence

Step Action Using …

1 Configure Megaplex-4100 signaling profiles Configuration>System>Signaling Profile

6 Prepare the Megaplex-4100 for SNMP

4 Megaplex-4100 Ver. 2.0

Step Action Using …

7 Configure Ethernet services in the following

Megaplex-4100 Ver. 2.0 5

6 Megaplex-4100 Ver. 2.0

Common Logic (CL) Modules

Megaplex-4100 Ver. 2.0 Overview 1-1

1-2 Overview Megaplex-4100 Ver. 2.0

Figure 1-1. Megaplex-4100 as a Versatile Multiservice Access Node

Megaplex-4100 Ver. 2.0 Overview 1-3

Figure 1-2. Megaplex-4100 in Chain Applications

1-4 Overview Megaplex-4100 Ver. 2.0