Megaplex-4100

OPERATION MANUAL
INSTALLATION AND
Megaplex-4
Next Generation Multiservice Access Node
Version 4.7
Megaplex-4
Next Generation Multiservice Access Node
Version 4.7
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-4
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-4 product name is owned by RAD. The Megaplex-4 product name is owned by RAD.
No right, license, or interest to such trademark is granted hereunder, and you agree that no such
right, license, or interest shall be asserted by you with respect to such trademark. RAD
products/technologies are protected by registered patents. To review specifically which product
is covered by which patent, please see ipr.rad.com. The RAD name, logo, logotype, and the
product names MiNID, Optimux, Airmux, 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-4. 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-4, based on or derived in any way from the Megaplex-4. Your undertaking in this
paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of the Megaplex-4 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-4 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–2015 RAD Data Communications Ltd. Publication No. 464-201-09/15

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

The following instructions serve as a general guide for the safe installation and operation of
telecommunications products. Additional instructions, if applicable, are included inside the
manual.
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.
Megaplex-4 iii
Handling Energized Products
General Safety Practices

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

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

V.11, V.28, V.35, V.36, RS-530, X.21, SELV Safety Extra Low Voltage:
10BaseT, 100BaseT, 1000BaseT, Ports which do not present a safety hazard. Usually
Unbalanced E1, E2, E3, STM, DS-2, up to 30 VAC or 60 VDC.
DS-3, S-Interface ISDN, Analog voice
E&M
xDSL (without feeding voltage), TNV-1 Telecommunication Network Voltage-1:
Balanced E1, T1, Sub E1/T1, POE Ports whose normal operating voltage is within the
limits of SELV, on which overvoltages from
telecommunications networks are possible.
FXS (Foreign Exchange Subscriber) TNV-2 Telecommunication Network Voltage-2:
Ports whose normal operating voltage exceeds the
limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are not possible. These
ports are not permitted to be directly connected to
external telephone and data lines.
FXO (Foreign Exchange Office), xDSL TNV-3 Telecommunication Network Voltage-3:
(with feeding voltage), U-Interface Ports whose normal operating voltage exceeds the
ISDN limits of SELV (usually up to 120 VDC or telephone
ringing voltages), on which overvoltages from
telecommunication networks are possible.
Always connect a given port to a port of the same safety status. If in doubt, seek the assistance
of a qualified safety engineer.
Always make sure that the equipment is grounded before connecting telecommunication cables.
Do not disconnect the ground connection before disconnecting all telecommunications cables.
Some SELV and non-SELV circuits use the same connectors. Use caution when connecting cables.
Extra caution should be exercised during thunderstorms.
Megaplex-4 v
When using shielded or coaxial cables, verify that there is a good ground connection at both
ends. The grounding and bonding of the ground connections should comply with the local codes.
The telecommunication wiring in the building may be damaged or present a fire hazard in case of
contact between exposed external wires and the AC power lines. In order to reduce the risk,
there are restrictions on the diameter of wires in the telecom cables, between the equipment
and the mating connectors.
Caution To reduce the risk of fire, use only No. 26 AWG or larger telecommunication
line cords.
Attention Pour 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 with the exception of 1000BaseT ports that must always use shielded
twisted pair cables of good quality (CAT 5E or higher). However, the use of shielded wires is
always recommended, especially for high-rate data. In some cases, when unshielded wires are
used, ferrite cores should be installed on certain cables. In such cases, special instructions are
provided in the manual.
Disconnect all wires which are not in permanent use, such as cables used for one-time
configuration.
The compliance of the equipment with the regulations for conducted emission on the data lines
is dependent on the cable quality. The emission is tested for UTP with 80 dB longitudinal
conversion loss (LCL).
Unless otherwise specified or described in the manual, TNV-1 and TNV-3 ports provide secondary
protection against surges on the data lines. Primary protectors should be provided in the building
installation.
The equipment is designed to provide adequate protection against electro-static discharge (ESD).
However, it is good working practice to use caution when connecting cables terminated with
plastic connectors (without a grounded metal hood, such as flat cables) to sensitive data lines.
Before connecting such cables, discharge yourself by touching ground or wear an ESD preventive
wrist strap.
vi Megaplex-4
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.
Megaplex-4 vii
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.
viii Megaplex-4
Certains produits peuvent être équipés d'une diode laser. Dans de tels cas,
Français
une étiquette indiquant la classe laser ainsi que d'autres avertissements, le
cas échéant, sera jointe près du transmetteur optique. Le symbole
d'avertissement laser peut aussi être joint.
Avertissement
Veuillez observer les précautions suivantes :
• Avant la mise en marche de l'équipement, assurez-vous que le câble de
fibre optique est intact et qu'il est connecté au transmetteur.
• Ne tentez pas d'ajuster le courant de la commande laser.
• N'utilisez pas des câbles ou connecteurs de fibre optique cassés ou sans
terminaison et n'observez pas directement un rayon laser.
• L'usage de périphériques optiques avec l'équipement augmentera le
risque pour les yeux.
• L'usage de contrôles, ajustages ou procédures autres que celles
spécifiées ici pourrait résulter en une dangereuse exposition aux
radiations.
ATTENTION : Le rayon laser peut être invisible !
Les utilisateurs pourront, dans certains cas, insérer leurs propres émetteurs-récepteurs Laser SFP
dans le produit. Les utilisateurs sont avertis que RAD ne pourra pas être tenue responsable de
tout dommage pouvant résulter de l'utilisation d'émetteurs-récepteurs non conformes. Plus
particulièrement, les utilisateurs sont avertis de n'utiliser que des produits approuvés par
l'agence et conformes à la réglementation locale de sécurité laser pour les produits laser de
classe 1.
Respectez toujours les précautions standards de sécurité durant l'installation, l'opération et la
maintenance de ce produit. Seul le personnel de service qualifié et autorisé devrait effectuer
l'ajustage, la maintenance ou les réparations de ce produit. Aucune opération d'installation,
d'ajustage, de maintenance ou de réparation ne devrait être effectuée par l'opérateur ou
l'utilisateur.
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.
Megaplex-4 ix
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 (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de
court-circuit dépassant 35A (40A aux Etats-Unis et Canada).
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.
Assurez-vous que l'alimentation CC est isolée de toute source de courant CA (secteur) et que
l'installation est conforme à la réglementation locale.
La capacité maximale permissible en courant du circuit de distribution de la connexion alimentant
le produit est de 16A (20A aux Etats-Unis et Canada). Le coupe-circuit dans l'installation du
bâtiment devrait avoir une capacité élevée de rupture et devrait fonctionner sur courant de
court-circuit dépassant 35A (40A aux Etats-Unis et Canada).
Avant la connexion des câbles d'alimentation en courant CC, assurez-vous que le circuit CC n'est
pas sous tension. Localisez le coupe-circuit dans le tableau desservant l'équipement et fixez-le
en position OFF. Lors de la connexion de câbles d'alimentation CC, connectez d'abord le
conducteur de mise à la terre à la borne correspondante, puis le pôle positif et en dernier, le
pôle négatif. Remettez le coupe-circuit en position ON.
Un disjoncteur facilement accessible, adapté et approuvé devrait être intégré à l'installation du
bâtiment.
Le disjoncteur devrait déconnecter simultanément les deux pôles si l'alimentation en courant CC
est flottante.
x Megaplex-4
Declarations of Conformity
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
Product Options: All
conforms to the following standard(s) or other normative

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

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

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

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

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

A11:2009, A1:2010 General requirements.
+ A12:2011
Supplementary Information: The product herewith complies with the requirements of the EMC
Directive 2004/108/EC, the Low Voltage Directive 2006/95/EC, the
R&TTE Directive 99/5/EC for wired equipment and the ROHS
Directive 2011/65/EU.
The product was tested in a typical configuration.
Tel Aviv, 1 January 2013
Nathaniel Shomroni
Homologation Team Leader
European Contact: RAD Data Communications GmbH

Otto-Hahn-Str. 28-30, D-85521 Ottobrunn-Riemerling, Germany
Megaplex-4 xi
Product Name: Megaplex-4104
Product Options: All

document(s):



phase)


+ A12:2011
Tel Aviv, 6 March 2013
Nathaniel Shomroni

xii Megaplex-4
Product Name: MPF
Product Option: MPF/48/120VDC

document(s):



phase)


+ A12:2011
Valid only when operating in conjunction with RAD Megaplex®
systems.
Tel Aviv, 6 March 2013
Nathaniel Shomroni

Megaplex-4 xiii
xiv Megaplex-4
Quick Start Guide
This section describes the minimum configuration needed to prepare
Megaplex-4 for operation.
1. Installing the Unit

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

 To connect the interfaces:
1. Insert the SFP modules (if applicable) into the relevant SFP-based Ethernet
ports.
2. Refer to the site installation plan, and connect the prescribed cables to the
Megaplex-4 modules.
Connecting to a Terminal
 To connect to an ASCII terminal:
1. Connect one side of the cable supplied by RAD (CBL-DB9F-DB9M-STR for
Megaplex-4100, CBL-MUSB-DB9F for Megaplex-4104) to the Megaplex
connector, designated CONTROL DCE.
2. Connect the other side of the cable to the ASCII terminal equipment.
Connecting the Power

Connect the power cable(s) first to the connector on the PS module, and then to
the power outlet. For DC cables, pay attention to polarity.
Megaplex-4 Installing the Unit 1

Quick Start Guide Installation and Operation Manual
2. Configuring the Unit for Management

Configure Megaplex-4 for management, using a local ASCII-based terminal.
Starting a Terminal Session for the First Time

 To start the terminal session:
1. Connect an ASCII terminal to the CONTROL DCE connector of the active CL
module (use a straight cable).
2. Configure the ASCII terminal to the settings listed below and then set the
terminal emulator to VT100 emulation for optimal view of system menus.
 Data Rate: 9,600 bps
 Data bits: 8
 Parity: None
 Stop bits: 1
 Flow control: None.
3. If you are using HyperTerminal, set the terminal mode to 132-column mode
for optimal view of system menus (Properties> Settings> Terminal Setup>
132 column mode).
4. Turn the power on.
Note The Megaplex-4 PS modules do not include a power switch. Use an external
power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
5. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
 After a few seconds, Megaplex-4 starts decompressing its software.
 After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4 performs
its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4.
6. When the startup process is completed, you are prompted to press <Enter>
to receive the login prompt.
7. Press <Enter> until you receive the login prompt.
8. If the Megaplex-4 default user name and password have not yet been
changed, log in as administrator using su as the user name (su for full
configuration and monitoring access) and 1234 for password.
9. The device prompt appears:
mp4100#
You can now type the necessary CLI commands.
2 Configuring the Unit for Management Megaplex-4

Installation and Operation Manual Quick Start Guide
Configuring the Router

The router must be configured with a router interface that is bound to the SVI
used for the management flows, and assigned an IP address. Also, a static route
must be set up for the default gateway.
This section illustrates the following configuration:
• Router interface 1:
 Bound to SVI 1
 IP address 172.17.154.96 with mask 255.255.255.0
• Router: Static route associated with IP address 172.17.154.1 (default
gateway).
 To define the router:

• Enter the following commands:
configure router 1
interface 1
bind svi 1
# IP address 172.17.154.96 with mask 255.255.255.0
address 172.17.154.96/24
no shutdown
exit
# Default gateway 172.17.154.1
static-route 0.0.0.0/0 address 172.17.154.1
exit all
3. Saving Management Configuration
Saving Configuration
Type save in any level to save your configuration in startup-config.
Copying User Configuration to Default Configuration

In addition to saving your configuration in startup-config, you may also wish to
save your configuration as a user default configuration.
Megaplex-4 Saving Management Configuration 3

Quick Start Guide Installation and Operation Manual
 To save user default configuration:

• Enter the following commands:
exit all
file copy startup-config user-default-config
y
4. Verifying Connectivity
At the ASCII terminal, ping the IP address assigned to Megaplex-4 and verify that
replies are received. If there is no reply to the ping, check your configuration and
make the necessary corrections.
4 Verifying Connectivity Megaplex-4

Contents
Chapter 1. Introduction
1.1 Overview .............................................................................................................................. 1-1
Product Options ................................................................................................................. 1-1
Chassis .......................................................................................................................... 1-1
CL Modules.................................................................................................................... 1-2
PS Modules ................................................................................................................... 1-4
Applications ....................................................................................................................... 1-4
Central Solution for RAD CPE Devices ............................................................................ 1-4
TDM and Ethernet Multiservice Access .......................................................................... 1-5
Smooth Migration from TDM to PSN .............................................................................. 1-5
Carrier Ethernet Services ............................................................................................... 1-6
Features ............................................................................................................................ 1-9
Forwarding Schemes ..................................................................................................... 1-9
Service Types .............................................................................................................. 1-10
Flow Classification ....................................................................................................... 1-10
Tagging and Marking ................................................................................................... 1-11
L2CP Handling ............................................................................................................. 1-11
Fault Propagation ........................................................................................................ 1-12
Traffic Management and Service Level Agreement (SLA) Monitoring, Troubleshooting and
Measurement .............................................................................................................. 1-12
Flexible Ethernet Transport over TDM .......................................................................... 1-15
Flexible TDM Transport over Ethernet .......................................................................... 1-15
Fiber Multiplexing ........................................................................................................ 1-15
DS0 Cross-Connect ..................................................................................................... 1-15
Protection ................................................................................................................... 1-16
Diversity of Rings ........................................................................................................ 1-17
Modularity and Flexibility ............................................................................................. 1-17
Next-Generation ADM/Terminal ................................................................................... 1-17
Timing ......................................................................................................................... 1-17
Simple Network Time Protocol .................................................................................... 1-18
Management ............................................................................................................... 1-18
Syslog ......................................................................................................................... 1-19
Diagnostics ................................................................................................................. 1-20
Alarm Collection and Reporting ................................................................................... 1-20
Performance Monitoring.............................................................................................. 1-20
RADview Performance Management ............................................................................ 1-21
Security ....................................................................................................................... 1-21
1.2 New in this Version ............................................................................................................ 1-21
1.3 Physical Description ........................................................................................................... 1-22
System Structure ............................................................................................................. 1-22
Description of Megaplex-4100 Chassis ............................................................................. 1-23
Rear View .................................................................................................................... 1-23
Front Panel ................................................................................................................. 1-24
Description of Megaplex-4104 Chassis ............................................................................. 1-24
I/O Modules ..................................................................................................................... 1-25
Common Logic (CL.2) Modules ......................................................................................... 1-31
Power Supply (PS) Modules .............................................................................................. 1-31
PS Modules ................................................................................................................. 1-31
Feed and Ring Voltage Sources ................................................................................... 1-31
1.4 Functional Description ........................................................................................................ 1-32
Megaplex-4 i
Table of Contents Installation and Operation Manual
Megaplex-4 Architecture .................................................................................................. 1-32

TDM Engine ...................................................................................................................... 1-35
DS0 Cross-Connect Matrix ........................................................................................... 1-35
DS1 Cross-Connect Matrix ........................................................................................... 1-37
E1/T1 Framers and Mappers ........................................................................................ 1-37
SDH/SONET Engine .......................................................................................................... 1-38
SDH/SONET Network Port Interfaces ........................................................................... 1-38
SDH/SONET Framer and LO/HO Cross-Connect Matrix ................................................. 1-38
Packet Engine .................................................................................................................. 1-38
Packet Processor ......................................................................................................... 1-39
Carrier Ethernet (CL.2/A Assembly) ............................................................................. 1-40
VCAT Engine ................................................................................................................ 1-42
HO/LO Mapper ............................................................................................................ 1-43
Ethernet over SDH/SONET, Full/Channelized T3, E1/T1 - General Concept ................... 1-43
Ethernet over E1/T1 .................................................................................................... 1-44
Ethernet over SDH/SONET ........................................................................................... 1-45
Ethernet over Full/Channelized T3 ............................................................................... 1-46
I/O Modules ..................................................................................................................... 1-47
Megaplex-4 Architecture Entities ..................................................................................... 1-49
1.5 Technical Specifications...................................................................................................... 1-54
Chapter 2. Installation
2.1 Site Requirements and Prerequisites .................................................................................... 2-1
Safety Precautions ............................................................................................................. 2-1
Grounding .......................................................................................................................... 2-2
Laser Safety ....................................................................................................................... 2-3
Protection against ESD ...................................................................................................... 2-3
AC Power Requirements ..................................................................................................... 2-4
DC Power Requirements .................................................................................................... 2-4
Front and Rear Panel Clearance ......................................................................................... 2-5
Ambient Requirements ...................................................................................................... 2-5
Megaplex-4100 ............................................................................................................. 2-5
Megaplex-4104 ............................................................................................................. 2-5
Electromagnetic Compatibility Considerations .................................................................... 2-6
Optical Cable Requirements ............................................................................................... 2-7
2.2 Package Contents................................................................................................................. 2-7
Megaplex-4100 Package Contents ..................................................................................... 2-7
Megaplex-4104 Package Contents ..................................................................................... 2-8
2.3 Required Equipment ............................................................................................................. 2-8
2.4 Mounting the Products ......................................................................................................... 2-8
Installing the Megaplex-4100 Chassis................................................................................. 2-9
Installing in a 19” Rack .................................................................................................. 2-9
Installing in 23” Rack................................................................................................... 2-10
Installing the Megaplex-4104 Chassis............................................................................... 2-10
2.5 Installing Modules .............................................................................................................. 2-11
Installing PS Modules ....................................................................................................... 2-11
Megaplex-4100 Module Panels .................................................................................... 2-11
Megaplex-4100 Internal Jumpers ................................................................................. 2-13
Megaplex-4104 Internal Jumpers ................................................................................. 2-14
Installing a PS Module ................................................................................................. 2-16
Removing a PS Module ................................................................................................ 2-16
Installing CL Modules........................................................................................................ 2-16
ii Megaplex-4
Installation and Operation Manual Table of Contents

Installing and Replacing SFPs ....................................................................................... 2-20
Installing a CL Module.................................................................................................. 2-22
Removing a CL Module ................................................................................................ 2-23
Replacing a CL Module during Equipment Operation –Megaplex-4 Chassis with two CL
Modules ...................................................................................................................... 2-23
Replacing a CL Module during Equipment Operation –Megaplex-4 Chassis with Single CL
Module ........................................................................................................................ 2-24
Adding a Protection CL Module to a Working Module Configured as SONET ................. 2-24
Installing System Modules in Megaplex-4104 Chassis ....................................................... 2-25
Installing I/O Modules ...................................................................................................... 2-25
Installing Blank Panels ...................................................................................................... 2-25
2.6 Connecting to Power .......................................................................................................... 2-25
Grounding Megaplex-4 ..................................................................................................... 2-25
Connecting to Power ....................................................................................................... 2-26
Connecting to External Feed Voltages .............................................................................. 2-26
2.7 Connecting Megaplex-4 to the Terminal ............................................................................. 2-26
Megaplex-4100 CL.2 Module ....................................................................................... 2-27
Megaplex-4104 CL.2 Module ....................................................................................... 2-27
2.8 Connecting to a Management Station or Telnet Host ......................................................... 2-28
2.9 Connecting to a Station Clock ............................................................................................ 2-28
2.10 Connecting to Alarm Equipment ......................................................................................... 2-29
2.11 Connecting to SDH/SONET Equipment ................................................................................ 2-30
Connecting Optical Cables to the SDH/SONET Links ..................................................... 2-30
Connecting Coaxial Cables to SDH/SONET Links ........................................................... 2-31
2.12 Connecting I/O Modules to Remote Equipment .................................................................. 2-32
2.13 Connecting to E1 and T1 Equipment .................................................................................. 2-32
2.14 Connecting to Ethernet Equipment..................................................................................... 2-32
Chapter 3. Operation
3.1 Turning On the Unit ............................................................................................................. 3-1
3.2 Indicators ............................................................................................................................. 3-2
CL.2 Front Panel Indicators ................................................................................................ 3-2
Front Panel Indicators ........................................................................................................ 3-5
3.3 Startup ................................................................................................................................. 3-6
Configuration Files ............................................................................................................. 3-6
Loading Sequence .............................................................................................................. 3-7
3.4 Saving Configuration Changes .............................................................................................. 3-7
3.5 Using a Custom Configuration File ........................................................................................ 3-8
3.6 Turning Off the Unit ............................................................................................................. 3-8
Chapter 4. Management and Security

4.1 Management Access Methods .............................................................................................. 4-2
Layer-3 Management Access ......................................................................................... 4-2
Layer-2 Management Access ......................................................................................... 4-3
4.2 CLI-Based Configuration ....................................................................................................... 4-4
Working with Terminal ....................................................................................................... 4-4
Working with Telnet and SSH ............................................................................................. 4-7
Working with Telnet ...................................................................................................... 4-7
Using SSH ..................................................................................................................... 4-7
Login ................................................................................................................................. 4-8
Megaplex-4 iii
Using the CLI ...................................................................................................................... 4-9

CLI Prompt .................................................................................................................... 4-9
Navigating ................................................................................................................... 4-10
Command Tree ............................................................................................................ 4-11
Command Structure .................................................................................................... 4-12
Special Keys ................................................................................................................ 4-12
Getting Help ................................................................................................................ 4-13
Using Scripts .................................................................................................................... 4-17
4.3 GUI-Based Configuration .................................................................................................... 4-18
Preconfiguring Megaplex-4 for SNMP Management .......................................................... 4-18
Working with RADview ..................................................................................................... 4-19
Working with Shelf View .................................................................................................. 4-19
Working with SNMP.......................................................................................................... 4-19
4.4 Services for Management Traffic ........................................................................................ 4-20
4.5 Control Port ....................................................................................................................... 4-20
Standards ........................................................................................................................ 4-21
Functional Description ..................................................................................................... 4-21
Factory Defaults .............................................................................................................. 4-21
Configuring the Control Port ............................................................................................ 4-21
4.6 Management Ethernet Port ................................................................................................ 4-22
Benefits ........................................................................................................................... 4-22
Configuring the Out-Of-Band Management Port .............................................................. 4-22
4.7 User Access ........................................................................................................................ 4-23
Defining Users and Passwords ......................................................................................... 4-23
Example ........................................................................................................................... 4-24
Viewing Connected Users ................................................................................................. 4-25
4.8 Access Control List (ACL) .................................................................................................... 4-25
Standards and MIBs ......................................................................................................... 4-26
Benefits ........................................................................................................................... 4-26
Binding Access Control Lists ........................................................................................ 4-26
Filtering ....................................................................................................................... 4-26
Statistics ..................................................................................................................... 4-26
Configuring ACL ............................................................................................................... 4-27
Access-Control-Level Tasks ......................................................................................... 4-27
Management-Level Tasks ............................................................................................ 4-28
Example ...................................................................................................................... 4-28
Displaying Status......................................................................................................... 4-29
Displaying Statistics .................................................................................................... 4-29
4.9 SNMP Management ............................................................................................................ 4-30
Standards ........................................................................................................................ 4-30
Benefits ........................................................................................................................... 4-31
SNMP Message Formats .............................................................................................. 4-32
The SNMPv3 Mechanism .............................................................................................. 4-36
Configuring for SNMP Management.................................................................................. 4-37
Specifying an SNMPv3 Engine ...................................................................................... 4-37
Enabling SNMPv3 ......................................................................................................... 4-38
Specifying an SNMPv3 User ......................................................................................... 4-38
Specifying a Trap Source Address for Management Router ......................................... 4-39
Defining User (Access) Groups .................................................................................... 4-39
iv Megaplex-4
Setting up a View ........................................................................................................ 4-41

Mapping SNMPv1 to SNMPv3 ....................................................................................... 4-41
Configuring Targets ..................................................................................................... 4-42
Configuring SNMP Communities for SNMPv1 ............................................................... 4-44
Adding SNMPv3 Notification Entries ............................................................................ 4-44
Configuring a Notification Filter................................................................................... 4-45
Configuring a Notification Filter Profile ........................................................................ 4-45
Linking User (Access) Groups to an Access Control Policy............................................ 4-46
4.10 Managers ........................................................................................................................... 4-46
4.11 Management Access........................................................................................................... 4-47
Configuring Access ........................................................................................................... 4-48
4.12 Access Policy ...................................................................................................................... 4-49
Configuring Access Policy ................................................................................................. 4-49
4.13 Authentication via RADIUS Server ....................................................................................... 4-50
Standards ........................................................................................................................ 4-50
Benefits ........................................................................................................................... 4-51
Configuring the RADIUS Server ......................................................................................... 4-51
Viewing the RADIUS Server Profile Status ......................................................................... 4-52
Viewing RADIUS Statistics ................................................................................................ 4-52
4.14 Authentication via TACACS+ Server..................................................................................... 4-53
Standards ........................................................................................................................ 4-53
Benefits ........................................................................................................................... 4-53
Components................................................................................................................ 4-54
Accounting .................................................................................................................. 4-54
Defining TACACS+ Server ................................................................................................. 4-55
Configuring Accounting Groups ........................................................................................ 4-56
Example – Defining Server ............................................................................................... 4-56
Example – Defining Accounting Group .............................................................................. 4-57
Displaying Statistics ......................................................................................................... 4-57
Defining Accounting Groups ............................................................................................. 4-58
4.15 IEEE 802.1X - Port-based Network Access Control ............................................................. 4-59
Standards ........................................................................................................................ 4-59
Benefits ........................................................................................................................... 4-59
Components................................................................................................................ 4-60
Typical Authentication Progression.............................................................................. 4-61
Configuring 802.1X Access Control .................................................................................. 4-62
Example ........................................................................................................................... 4-63
Displaying Statistics ......................................................................................................... 4-68
Viewing the 802.1X Status ............................................................................................... 4-69
4.16 Syslog ................................................................................................................................ 4-70
Benefits ........................................................................................................................... 4-70
Elements ..................................................................................................................... 4-71
Transport Protocol ...................................................................................................... 4-71
Megaplex-4 v
Message Format .......................................................................................................... 4-71

Facilities and Severities ............................................................................................... 4-72
Syslog Configuration ........................................................................................................ 4-72
Chapter 5. Services
5.1 Service Elements .................................................................................................................. 5-1
Profiles .............................................................................................................................. 5-1
Scheduling and Shaping Entities......................................................................................... 5-2
Physical Ports .................................................................................................................... 5-2
Logical Ports ...................................................................................................................... 5-3
Forwarding Entities ............................................................................................................ 5-4
Flows ............................................................................................................................ 5-4
Bridge ........................................................................................................................... 5-5
Router........................................................................................................................... 5-5
5.2 Services Provided by Megaplex-4 .......................................................................................... 5-5
5.3 E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a) ...................................... 5-15
5.4 E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b) ................................................... 5-17
5.5 E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a) ...................................... 5-19
5.6 Fast Ethernet Traffic to PSN over Fiber (2b) ....................................................................... 5-21
5.7 Fast Ethernet Traffic to SDH/SONET (3) ............................................................................. 5-22
5.8 Shared E-LAN Service with Multiple Drops per Node over SDH/SONET ................................ 5-24
5.9 E1 to SDH Traffic over Copper via DS0 Mapping (3a) .......................................................... 5-27
5.10 Fast Ethernet Traffic to PSN over Copper (3b).................................................................... 5-29
5.11 High-Speed Traffic to SDH/SONET (4) ................................................................................ 5-30
5.12 High-Speed Traffic to PSN (4a, 4b) .................................................................................... 5-32
5.13 Low-Latency High-Speed Traffic to PSN (4c, 4d) ................................................................ 5-35
5.14 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection ..................... 5-38
5.15 Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a) ........................................................... 5-42
5.16 Fast Ethernet Traffic to Multiple E1 (MLPPP Protocol) (5b) ................................................. 5-44
5.17 Voice Traffic to SDH/SONET (6) .......................................................................................... 5-46
5.18 Voice Traffic to PSN (6a) .................................................................................................... 5-48
5.19 Teleprotection Traffic to SDH/SONET (7) ............................................................................ 5-51
5.20 T3 Traffic to SONET (8) ...................................................................................................... 5-53
5.21 Voice to T3 via DS0 Cross-Connect (9) ............................................................................... 5-55
5.22 Ethernet Traffic over PDH to SDH/SONET (10a) .................................................................. 5-56
5.23 Ethernet Traffic over PDH to E1/T1 (10b) ........................................................................... 5-58
Chapter 6. Cards and Ports

6.1 Cards.................................................................................................................................... 6-1
I/O Modules ....................................................................................................................... 6-1
Configuring Modules in the Chassis .................................................................................... 6-1
Example ............................................................................................................................. 6-3
Displaying Modules in the Chassis ...................................................................................... 6-3
Resetting I/O Module ....................................................................................................... 6-15
Configuration Errors ......................................................................................................... 6-15
6.2 Port-Related Profiles .......................................................................................................... 6-16
Signaling Profiles ............................................................................................................. 6-16
Functional Description................................................................................................. 6-16
Factory Defaults .......................................................................................................... 6-17
Configuring CAS Signaling Profiles ............................................................................... 6-17
Example ...................................................................................................................... 6-19
Analog Signaling Profiles .................................................................................................. 6-20
vi Megaplex-4

Configuring Analog Signaling Profiles .......................................................................... 6-23
Example ...................................................................................................................... 6-24
VC Profiles ....................................................................................................................... 6-25
Configuring VC Profiles ................................................................................................ 6-27
6.3 Physical Ports ..................................................................................................................... 6-28
Binary Command Ports ..................................................................................................... 6-28
Applicable Modules ..................................................................................................... 6-28
Configuring CMD-IN Ports ............................................................................................ 6-29
Configuring CMD-OUT Ports ........................................................................................ 6-30
Configuring CMD-CHANNEL Ports................................................................................. 6-30
Viewing Status Information ......................................................................................... 6-30
Displaying Binary Command Statistics ......................................................................... 6-31
Clearing Statistics ........................................................................................................ 6-32
DS1 Optical Ports (Fiber Optic Links of VS-6/C37 Modules) .............................................. 6-32
Standards ................................................................................................................... 6-32
Configuring DS1 Optical Port Parameters .................................................................... 6-33
Configuration Errors .................................................................................................... 6-34
Viewing a DS1-Opt Port Status.................................................................................... 6-34
Testing DS1 Optical Links ............................................................................................ 6-34
Ethernet Ports ................................................................................................................. 6-36
Standards ................................................................................................................... 6-36
Configuring User Ethernet Ports .................................................................................. 6-41
Example ...................................................................................................................... 6-45
Displaying Ethernet Port Status ................................................................................... 6-45
Displaying PoE Status .................................................................................................. 6-46
Testing Ethernet Ports ................................................................................................ 6-48
Displaying Ethernet Port Statistics .............................................................................. 6-48
E1 Ports ........................................................................................................................... 6-51
Standards ................................................................................................................... 6-53
Configuring an E1 Port ................................................................................................ 6-57
Configuring an Internal E1 Port ................................................................................... 6-59
Example 1 ................................................................................................................... 6-61
Example 2 ................................................................................................................... 6-61
Example 3 ................................................................................................................... 6-62
Viewing an E1 Port Status ........................................................................................... 6-63
Testing E1 Ports .......................................................................................................... 6-64
Displaying E1 Port Statistics ........................................................................................ 6-76
Megaplex-4 vii

Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules) ............................................. 6-80
Standards ................................................................................................................... 6-81
Configuring Optical Link Parameters and Accessing the Remote Unit .......................... 6-83
Example ...................................................................................................................... 6-87
Viewing Optical Link SFP Status Information ................................................................ 6-88
Testing Optical Links ................................................................................................... 6-89
Serial Ports ...................................................................................................................... 6-93
Standards ................................................................................................................... 6-95
Configuring Serial Port Parameters .............................................................................. 6-96
Example .................................................................................................................... 6-101
Viewing Status Information ....................................................................................... 6-101
Displaying VS Serial Port Statistics............................................................................. 6-102
Clearing Statistics ...................................................................................................... 6-103
Configuration Errors .................................................................................................. 6-103
Testing Serial Ports ................................................................................................... 6-103
SDH/SONET Ports ........................................................................................................... 6-106
Applicable Modules ................................................................................................... 6-106
Standards ................................................................................................................. 6-106
Functional Description............................................................................................... 6-106
Factory Defaults (SDH/SONET Parameters) ............................................................... 6-125
Configuring an SDH/SONET Link ................................................................................ 6-126
Assigning VC Profiles to AUG/OC-3 ............................................................................ 6-128
Viewing SDH/SONET Status Information .................................................................... 6-131
Testing SDH/SONET Ports .......................................................................................... 6-134
Displaying SDH/SONET Statistics ............................................................................... 6-138
SHDSL Ports ................................................................................................................... 6-142
Standards ................................................................................................................. 6-145
Benefits .................................................................................................................... 6-145
Factory Defaults ........................................................................................................ 6-147
Configuring an SHDSL Port ........................................................................................ 6-147
Displaying the Status of SHDSL Port and Repeaters .................................................. 6-152
Testing SHDSL Ports .................................................................................................. 6-153
Displaying SHDSL Port Statistics ................................................................................ 6-158
Displaying SHDSL Repeater Statistics ........................................................................ 6-161
T1 Ports ......................................................................................................................... 6-163
Standards ................................................................................................................. 6-164
Configuring a T1 Port ................................................................................................ 6-168
viii Megaplex-4
Configuring an Internal T1 Port ................................................................................. 6-170

Example 1 ................................................................................................................. 6-171
Example 2 ................................................................................................................. 6-171
Example 3 ................................................................................................................. 6-172
Viewing a T1 Port Status ........................................................................................... 6-173
Testing T1 Ports ........................................................................................................ 6-174
Testing T1 Ports ........................................................................................................ 6-174
Displaying T1 Port Statistics ...................................................................................... 6-180
T3 Ports ......................................................................................................................... 6-184
Standards ................................................................................................................. 6-184
Configuring a T3 Port ................................................................................................ 6-185
Viewing a T3 Port Status ........................................................................................... 6-186
Testing T3 Ports ........................................................................................................ 6-186
Displaying T3 Port Statistics ...................................................................................... 6-188
Teleprotection Ports (Physical) ...................................................................................... 6-193
Configuring CMD-IN Ports .......................................................................................... 6-194
Configuring CMD-OUT Ports ...................................................................................... 6-195
Configuring CMD-CHANNEL Ports............................................................................... 6-197
Clear-Cmd-Led Command per System ........................................................................ 6-197
Viewing Status Information ....................................................................................... 6-198
Displaying Teleprotection Statistics ........................................................................... 6-200
Voice Ports .................................................................................................................... 6-202
Standards ................................................................................................................. 6-203
Configuring External Voice Port Parameters ............................................................... 6-206
Example .................................................................................................................... 6-211
Configuring Internal Voice Port Parameters ............................................................... 6-211
Viewing a Voice Port Status ....................................................................................... 6-213
Testing Voice Ports ................................................................................................... 6-214
6.4 Logical Ports .................................................................................................................... 6-218
BRI Ports ........................................................................................................................ 6-218
Standards ................................................................................................................. 6-218
Configuring a BRI (ISDN) Port .................................................................................... 6-219
Example .................................................................................................................... 6-219
DS1 Ports ...................................................................................................................... 6-220
Megaplex-4 ix
Configuring Internal DS1 Port Parameters ................................................................. 6-221

Example .................................................................................................................... 6-222
Viewing DS1 Port Status............................................................................................ 6-222
E1-i, T1-i Ports ............................................................................................................... 6-225
GFP Ports ....................................................................................................................... 6-226
Standards ................................................................................................................. 6-226
Configuring GFP Ports ............................................................................................... 6-226
Displaying GFP Statistics ........................................................................................... 6-227
HDLC Ports (CL.2 Modules) ............................................................................................ 6-229
Standards ................................................................................................................. 6-230
Configuring HDLC Ports ............................................................................................. 6-230
Displaying HDLC Statistics ......................................................................................... 6-230
HDLC Ports (I/O Modules) .............................................................................................. 6-233
Standards ................................................................................................................. 6-233
Configuring HDLC Ports ............................................................................................. 6-233
Internal Ethernet (D-NFV) Ports ..................................................................................... 6-235
Standards ................................................................................................................. 6-235
Configuring Internal Ethernet Ports ........................................................................... 6-236
Displaying D-NFV Internal Ethernet Port Status ......................................................... 6-237
Testing D-NFV Ports .................................................................................................. 6-237
Displaying Ethernet Port Statistics ............................................................................ 6-237
Logical MAC Ports .......................................................................................................... 6-239
Configuring Logical MAC Ports ................................................................................... 6-240
Viewing MAC Address ................................................................................................ 6-241
Displaying Logical MAC Statistics ............................................................................... 6-241
MLPPP Ports ................................................................................................................... 6-243
Standards ................................................................................................................. 6-243
Configuring MLPPP Ports ........................................................................................... 6-243
Example .................................................................................................................... 6-244
PCS Ports ....................................................................................................................... 6-245
Standards ................................................................................................................. 6-246
Configuring a PCS Port .............................................................................................. 6-248
Displaying PCS Port Status ........................................................................................ 6-249
x Megaplex-4
Testing PCS Ports ...................................................................................................... 6-249

Displaying PCS Statistics ............................................................................................ 6-250
PPP Ports ....................................................................................................................... 6-251
Standards ................................................................................................................. 6-251
Configuring PPP Ports ................................................................................................ 6-251
Example .................................................................................................................... 6-252
Serial Bundle Ports ......................................................................................................... 6-253
Configuring Serial Bundle Port Parameters ................................................................ 6-254
Example .................................................................................................................... 6-254
Testing Serial-Bundle Ports ....................................................................................... 6-255
SVI (Switched Virtual Interface) Ports ............................................................................. 6-258
TDM Bridge Ports ........................................................................................................... 6-259
Standards ................................................................................................................. 6-259
Configuring TDM Bridge Ports .................................................................................... 6-259
Example .................................................................................................................... 6-259
Teleprotection Ports (Logical) ........................................................................................ 6-259
Configuring CMD-IN-I Ports........................................................................................ 6-260
Configuring CMD-OUT-I Ports .................................................................................... 6-261
Viewing Status Information of Logical Teleprotection Ports ....................................... 6-261
Testing Teleprotection Ports ..................................................................................... 6-262
VCG Ports ....................................................................................................................... 6-263
Standards ................................................................................................................. 6-263
Benefits .................................................................................................................... 6-264
Configuring VCG Ports ............................................................................................... 6-267
Viewing LCAS Status Information............................................................................... 6-269
Displaying LCAS Statistics .......................................................................................... 6-271
Chapter 7. Resiliency
7.1 Fault Propagation ................................................................................................................. 7-2
Functional Description ....................................................................................................... 7-2
Factory Defaults ................................................................................................................ 7-5
Configuring Fault Propagation ............................................................................................ 7-5
Configuration Errors ........................................................................................................... 7-6
7.2 APS Protection ..................................................................................................................... 7-7
Standards .......................................................................................................................... 7-7
Benefits ............................................................................................................................. 7-7
Megaplex-4 xi

Configuring Automatic Protection Switching ...................................................................... 7-9
Adding and Removing an APS Group ............................................................................. 7-9
Binding Ports to an APS Group ...................................................................................... 7-9
Viewing the Status of an APS Group ................................................................................ 7-11
Example ........................................................................................................................... 7-12
7.3 Ethernet Group Protection ................................................................................................. 7-12
Applicable Modules .......................................................................................................... 7-13
Standards ........................................................................................................................ 7-13
Configuring Ethernet Protection Group ............................................................................ 7-16
Adding and Removing an Ethernet Protection Group ................................................... 7-16
Binding Ports to an Ethernet Protection Group ........................................................... 7-17
Example ........................................................................................................................... 7-17
Viewing the Status of an Ethernet Protection Group ........................................................ 7-19
7.4 Ethernet Ring Protection (ERP) ........................................................................................... 7-20
Applicable Modules .......................................................................................................... 7-20
Standards ........................................................................................................................ 7-21
Benefits ........................................................................................................................... 7-21
Ring Topology ............................................................................................................. 7-22
R-APS Messaging ......................................................................................................... 7-22
Mechanism of Operation ............................................................................................. 7-23
Administrative Commands ........................................................................................... 7-23
Multiple Rings.............................................................................................................. 7-24
Timers ......................................................................................................................... 7-25
ERP Configuration ............................................................................................................ 7-25
Configuring ERP ........................................................................................................... 7-25
Displaying ERP Status .................................................................................................. 7-28
Displaying ERP Statistics.............................................................................................. 7-29
Example ...................................................................................................................... 7-30
7.5 HSR Protection ................................................................................................................... 7-33
Benefits ........................................................................................................................... 7-33
Standards ........................................................................................................................ 7-33
Node Functionalities ................................................................................................... 7-34
Duplicate Discard ........................................................................................................ 7-35
Supervision Packet Analysis ......................................................................................... 7-35
Configuring the HSR ......................................................................................................... 7-35
Example ........................................................................................................................... 7-37
Viewing the LRE Status .................................................................................................... 7-40
Displaying a Node Table .............................................................................................. 7-40
Displaying a Proxy Table .............................................................................................. 7-41
Displaying LRE Statistics................................................................................................... 7-41
7.6 I/O Group Protection .......................................................................................................... 7-42
Benefits ........................................................................................................................... 7-42
Standards ........................................................................................................................ 7-43
Protection Mode ......................................................................................................... 7-43
xii Megaplex-4
Configuring I/O Group Protection ..................................................................................... 7-43

Example ........................................................................................................................... 7-45
7.7 LAG Protection ................................................................................................................... 7-45
Benefits ........................................................................................................................... 7-46
Configuring the LAG ......................................................................................................... 7-46
Displaying LAG Status ...................................................................................................... 7-48
Displaying LACP Status ..................................................................................................... 7-48
Displaying LAG Statistics .................................................................................................. 7-49
Displaying LACP Statistics ................................................................................................ 7-50
7.8 Path Protection for SDH/SONET Payload ............................................................................ 7-51
Configuring VC Path Protection ........................................................................................ 7-52
Adding and Removing a VC Path Protection Group ...................................................... 7-52
Binding Ports to a VC path Protection Group ............................................................... 7-52
Viewing the Status of a VC Path Protection Group ........................................................... 7-53
Example ........................................................................................................................... 7-53
7.9 PW Protection .................................................................................................................... 7-54
Benefits ........................................................................................................................... 7-54
Standards ........................................................................................................................ 7-55
Working and Protection Port Parameters..................................................................... 7-55
Configuring PW Protection ............................................................................................... 7-55
Example ........................................................................................................................... 7-56
Viewing the PW Protection Status .................................................................................... 7-57
7.10 TDM Group Protection ........................................................................................................ 7-57
Benefits ........................................................................................................................... 7-58
Standards ........................................................................................................................ 7-58
Working and Protection Port Parameters..................................................................... 7-59
Protection Mode ......................................................................................................... 7-60
Traffic Duplication ....................................................................................................... 7-60
Configuring TDM Group Protection ................................................................................... 7-61
Example 1 ........................................................................................................................ 7-64
Example 2 ........................................................................................................................ 7-64
Example 3 ........................................................................................................................ 7-65
Example 4 ........................................................................................................................ 7-66
Example 5. ....................................................................................................................... 7-66
Example 6 ........................................................................................................................ 7-68
7.11 TDM Ring Protection .......................................................................................................... 7-70
Benefits ........................................................................................................................... 7-71
Standards ........................................................................................................................ 7-71
Configuring TDM Ring Protection ..................................................................................... 7-73
Example ........................................................................................................................... 7-74
Megaplex-4 xiii
Chapter 8. Networking
8.1 Bridge .................................................................................................................................. 8-1
Standards .......................................................................................................................... 8-1
Benefits ............................................................................................................................. 8-1
Bridge Model ................................................................................................................. 8-2
Deleting Bridge Elements .............................................................................................. 8-2
Using the Bridge for Management ................................................................................. 8-2
Admission to Bridge ...................................................................................................... 8-3
Packet Editing on Reverse Flows ................................................................................... 8-3
Spanning Tree Protocol ................................................................................................. 8-5
Configuring the Bridge ....................................................................................................... 8-6
Configuring for Traffic ................................................................................................... 8-6
Configuring for Management ......................................................................................... 8-6
Configuring the Bridge .................................................................................................. 8-6
Example 1. Layer-2 Management Access ..................................................................... 8-10
Example 2. Layer-2 VLAN-aware Bridging between CL and M-ETH Ports ...................... 8-12
Example 3. Cascading Bridges on Different M-ETH Modules via CL Bridge .................... 8-14
Example 4. RSTP Basic Application ............................................................................... 8-18
Displaying MAC Address Table ..................................................................................... 8-23
8.2 Cross-Connections ............................................................................................................. 8-26
Benefits ........................................................................................................................... 8-28
Timeslot Types ............................................................................................................ 8-28
Full Timeslot versus Split Timeslot Assignment (Split Timeslot Cross-Connect) ............ 8-28
Bidirectional Transfer Mode ........................................................................................ 8-29
Unidirectional Broadcast Function ............................................................................... 8-29
Bidirectional Broadcast Applications ............................................................................ 8-30
DS0 Cross-Connect .......................................................................................................... 8-34
Configuring a DS0 Cross-Connection ........................................................................... 8-34
Example 1. Bidirectional DS0 Cross-Connect: CL <-> I/O Modules, Single Timeslot ....... 8-37
Example 2. Consecutive Timeslot Assignment: E1/T1/E1-i/T1-i Port <-> Serial Module Port
................................................................................................................................... 8-37
Example 3. Consecutive Timeslot Assignment: Two E1/T1/E1-i/T1-i I/0 Module Ports .. 8-37
Example 4. Unidirectional Broadcast: M8E1 Port is Sending Data to three M8E1
ports using UniRx ........................................................................................................ 8-37
Example 5. Unidirectional Broadcast: Voice Port is Sending Data to M8E1 Port using UniTx
................................................................................................................................... 8-38
Example 6. Unidirectional Broadcast: Serial Port is Sending Data to M8E1 Port using UniTx
................................................................................................................................... 8-38
Examples 7a and 7b. Bidirectional Voice-Grade Data Broadcast 1:n ............................ 8-38
Example 8. Bidirectional Broadcast: Serial Port is Sending Data to Remote RTUs over
Various E1 Ports .......................................................................................................... 8-40
Example 9. Bidirectional Broadcast with Monitoring over E1 ........................................ 8-40
TDM Cross-Connect.......................................................................................................... 8-41
Configuring a TDM Cross-Connection .......................................................................... 8-41
Example 1 ................................................................................................................... 8-42
Example 2 ................................................................................................................... 8-42
Split Timeslot Cross-Connect............................................................................................ 8-43
Configuring a Cross-Connection .................................................................................. 8-43
Example ...................................................................................................................... 8-44
xiv Megaplex-4
SDH/SONET Cross-Connect .............................................................................................. 8-45

Configuring an SDH/SONET Cross-Connection ............................................................. 8-45
Example 1. Direct Transparent Mapping of E1 Links over SDH ..................................... 8-46
Example 2. Mapping Framed E1 Link Payload to VC-12 Container ................................ 8-47
PW-TDM Cross-Connect ................................................................................................... 8-47
Configuring a PW-TDM Cross-Connection .................................................................... 8-47
Example 1 ................................................................................................................... 8-48
Example 2 ................................................................................................................... 8-48
8.3 Ethernet OAM (CFM) .......................................................................................................... 8-51
Standards ........................................................................................................................ 8-51
Benefits ........................................................................................................................... 8-51
OAM Elements ................................................................................................................. 8-53
OAM Functions ................................................................................................................ 8-54
MEPs and Services ........................................................................................................... 8-55
Down MEP ................................................................................................................... 8-55
Up MEP ....................................................................................................................... 8-56
Messaging System ........................................................................................................... 8-56
CC Messages ............................................................................................................... 8-56
Loopback Messages .................................................................................................... 8-57
Link Trace Messages ................................................................................................... 8-58
Performance Monitoring.............................................................................................. 8-58
Configuring OAM .............................................................................................................. 8-59
Configuring OAM CFM General Parameters .................................................................. 8-59
Configuring Maintenance Domains .............................................................................. 8-63
Configuring Maintenance Associations ........................................................................ 8-64
Configuring Maintenance Endpoints ............................................................................ 8-65
Configuring Maintenance Intermediate Points ............................................................. 8-67
Examples ..................................................................................................................... 8-68
Configuring Maintenance Endpoint Services ................................................................ 8-71
Configuring Destination NEs ........................................................................................ 8-72
Configuring OAM CFM Service Event Reporting ............................................................ 8-73
Displaying OAM CFM Statistics..................................................................................... 8-77
Clearing OAM Statistics ............................................................................................... 8-81
Performing OAM Loopback .......................................................................................... 8-81
Performing OAM Link Trace ......................................................................................... 8-82
8.4 Ethernet OAM (EFM)........................................................................................................... 8-83
Standards ........................................................................................................................ 8-83
Benefits ........................................................................................................................... 8-83
Configuring OAM EFM ...................................................................................................... 8-84
Example ........................................................................................................................... 8-85
8.5 Flows ................................................................................................................................. 8-86
Standards ........................................................................................................................ 8-86
Benefits ........................................................................................................................... 8-86
Ethernet Entities ......................................................................................................... 8-87
Aware and Unaware Traffic ......................................................................................... 8-88
Defining Classifier Profiles ........................................................................................... 8-89
Tagging and Marking ................................................................................................... 8-90
Megaplex-4 xv
Configuring Flows ............................................................................................................ 8-90

Example ........................................................................................................................... 8-94
Viewing the Flow Summary .............................................................................................. 8-95
Testing the Flows............................................................................................................. 8-96
Displaying Flow Statistics ................................................................................................. 8-97
8.6 Peer ................................................................................................................................. 8-102
Factory Defaults ............................................................................................................ 8-102
Benefits ......................................................................................................................... 8-102
Functional Description ................................................................................................... 8-102
Adding and Configuring Remote Peers ........................................................................... 8-102
Examples ....................................................................................................................... 8-103
Configuration Errors ....................................................................................................... 8-104
8.7 Pseudowires ..................................................................................................................... 8-104
Standards ...................................................................................................................... 8-104
Benefits ......................................................................................................................... 8-105
Pseudowire Packet Processing Subsystem ................................................................. 8-106
PSN Configuration Parameters .................................................................................. 8-112
Pseudowire QoS/CoS ................................................................................................. 8-112
ToS ........................................................................................................................... 8-112
Jitter Buffer ............................................................................................................... 8-113
Adaptive Timing ........................................................................................................ 8-114
OAM Protocol ............................................................................................................ 8-115
Configuring Pseudowires ................................................................................................ 8-117
Examples ....................................................................................................................... 8-124
Displaying PW Statistics ................................................................................................. 8-126
Clearing Statistics .......................................................................................................... 8-132
Viewing the Pseudowire Status and Summary ................................................................ 8-132
8.8 Router (Management) ...................................................................................................... 8-137
Benefits ......................................................................................................................... 8-137
Configuring Inband Management ................................................................................... 8-137
Loopback Router Interface ............................................................................................. 8-138
Configuring the Management Router ............................................................................. 8-138
Displaying the Routing Table .......................................................................................... 8-140
Example ......................................................................................................................... 8-142
8.9 Router (Pseudowire) ........................................................................................................ 8-145
Adding and Configuring Router Interfaces ...................................................................... 8-147
Adding a Router Interface ......................................................................................... 8-147
Configuring the Router Interface ............................................................................... 8-148
Displaying the Routing Table .......................................................................................... 8-149
Configuring Static Routes and Default Gateway ............................................................. 8-150
Example 1. Establishing PW Connectivity between HS-12N Module and MPW-1 Fast Ethernet
Port ............................................................................................................................... 8-151
Example 2. Establishing PW Connectivity between HS-12N Module and VCG .................. 8-152
8.10 Quality of Service (QoS) ................................................................................................... 8-154
Bandwidth Profiles ......................................................................................................... 8-154
xvi Megaplex-4
Configuring Shaper Profiles ....................................................................................... 8-155

Configuring Policer Profiles........................................................................................ 8-156
Queue Mapping Profiles ................................................................................................. 8-159
Adding Queue Mapping Profiles ................................................................................. 8-160
Configuring Queue Mappings .................................................................................... 8-161
Examples ................................................................................................................... 8-161
Marking Profiles ............................................................................................................. 8-162
Configuring Marking Profiles ...................................................................................... 8-163
Queue Block Profiles ...................................................................................................... 8-163
Adding Queue Block Profiles...................................................................................... 8-164
Configuring Queue Block Profile ................................................................................ 8-164
Example .................................................................................................................... 8-165
Queue Group Profiles ..................................................................................................... 8-166
Adding Queue Group Profiles .................................................................................... 8-167
Configuring Queue Group Parameters ....................................................................... 8-167
Example .................................................................................................................... 8-168
WRED Profiles ................................................................................................................ 8-169
Configuring WRED Profiles ......................................................................................... 8-170
Example .................................................................................................................... 8-170
Chapter 9. Timing and Synchronization

9.1 Clock Selection ..................................................................................................................... 9-1
Standards .......................................................................................................................... 9-1
Clock Synchronization ................................................................................................... 9-1
System Timing Modes ................................................................................................... 9-3
Clock Domain ................................................................................................................ 9-5
Configuring the Clock Domain ............................................................................................ 9-7
Displaying the Clock Domain Status ................................................................................... 9-8
Configuring the Clock Sources ............................................................................................ 9-9
Displaying the Clock Source Status .................................................................................. 9-11
Displaying Clock Source Statistics .................................................................................... 9-12
Configuring the Station Clock ........................................................................................... 9-12
Displaying the Station Clock Status .................................................................................. 9-14
Configuring the Recovered Clock ...................................................................................... 9-14
Displaying the Recovered Clock Status ............................................................................. 9-14
9.2 Date and Time.................................................................................................................... 9-16
Setting the Date and Time ............................................................................................... 9-16
Example ........................................................................................................................... 9-17
Displaying the Date and Time .......................................................................................... 9-17
Working with SNTP........................................................................................................... 9-17
Configuring SNTP Parameters ...................................................................................... 9-18
Defining SNTP Servers ................................................................................................. 9-18
Configuring SNTP Server Parameters ........................................................................... 9-18
Example ...................................................................................................................... 9-19
Megaplex-4 xvii
Chapter 10. Administration

10.1 Administrative Information ................................................................................................. 10-1
10.2 MAC Address Allocation ...................................................................................................... 10-2
10.3 Managing the SONET/SDH Link Rate Selection License ....................................................... 10-3
Checking the License Availability ...................................................................................... 10-3
Ordering the License ........................................................................................................ 10-4
Downloading the License File Using TFTP ......................................................................... 10-5
Downloading the License File Using XModem .............................................................. 10-5
Installing the License for Redundant CL Modules ......................................................... 10-6
10.4 Inventory............................................................................................................................ 10-6
Benefits ........................................................................................................................... 10-6
Displaying Inventory Information ..................................................................................... 10-6
Displaying Inventory Component Information .................................................................. 10-7
Setting Administrative Inventory Information ................................................................... 10-7
Example ...................................................................................................................... 10-8
10.5 File Operations ................................................................................................................... 10-9
File Names in the Unit...................................................................................................... 10-9
Copying Files within Megaplex-4 .................................................................................... 10-10
Displaying Files within Megaplex-4 ................................................................................. 10-12
Deleting Files ................................................................................................................. 10-13
Saving the Configuration ................................................................................................ 10-13
Resetting Megaplex-4 .................................................................................................... 10-13
Resetting to Factory Defaults.................................................................................... 10-13
Resetting to User Defaults ........................................................................................ 10-14
Rebooting the Megaplex-4 Chassis ............................................................................ 10-14
Rebooting the Module ............................................................................................... 10-14
Downloading/Uploading Files ......................................................................................... 10-15
Example – Download via SFTP ................................................................................... 10-16
Example – Upload via SFTP ........................................................................................ 10-16
Chapter 11. Monitoring and Diagnostics

11.1 Detecting Problems ............................................................................................................ 11-1
Indicators......................................................................................................................... 11-1
Alarms and Traps ............................................................................................................. 11-2
Statistic Counters ............................................................................................................ 11-2
Configuration Error Messages .......................................................................................... 11-2
11.2 Handling Events ................................................................................................................. 11-3
Masking ........................................................................................................................... 11-3
Alarm Buffer .................................................................................................................... 11-4
Alarm Relays .................................................................................................................... 11-4
Configuring Alarm Reporting ............................................................................................ 11-5
Examples ..................................................................................................................... 11-8
Working with the Alarm and Event Logs ........................................................................... 11-8
Example 1: Displaying Active Alarms ............................................................................ 11-9
Example 2. Displaying Active Alarms Details ................................................................ 11-9
Example 3. Displaying Information of LOF alarm on SDH/SONET port ........................ 11-10
Example 4. Alarm Log ................................................................................................ 11-10
Example 5. Alarm List ................................................................................................ 11-11
Alarm, Event and Trap Lists ............................................................................................ 11-12
Configuration Error Messages ........................................................................................ 11-12
11.3 Troubleshooting ............................................................................................................... 11-12
xviii Megaplex-4
Preliminary Checks ......................................................................................................... 11-12

Troubleshooting Procedure ............................................................................................ 11-13
11.4 Performing Diagnostics Tests ........................................................................................... 11-15
Ethernet BERT (RFC-2544 Testing) ................................................................................. 11-15
Standards ................................................................................................................. 11-15
Benefits .................................................................................................................... 11-15
Performing the Test .................................................................................................. 11-16
Configuration Error Messages ................................................................................... 11-18
Example .................................................................................................................... 11-18
Performing a Ping Test ................................................................................................... 11-19
Running Diagnostic Loopbacks ....................................................................................... 11-20
11.5 Performance Management ............................................................................................... 11-25
Benefits ......................................................................................................................... 11-25
Configuring Performance Management .......................................................................... 11-27
Examples ....................................................................................................................... 11-27
11.6 Technical Support ............................................................................................................. 11-28
Chapter 12. Software Upgrade

12.1 Compatibility Requirements................................................................................................ 12-1
12.2 Impact ................................................................................................................................ 12-1
12.3 Software Upgrade Options ................................................................................................. 12-1
12.4 Prerequisites ...................................................................................................................... 12-2
Software Files .................................................................................................................. 12-2
System Requirements ...................................................................................................... 12-2
12.5 Upgrading Software using the CLI (TFTP) ............................................................................ 12-3
Verifying the IP Settings ................................................................................................... 12-4
Pinging the PC .................................................................................................................. 12-4
Activating the TFTP Server ............................................................................................... 12-4
Downloading the New Software Release File to Megaplex-4 Flash Disk............................ 12-4
Installing the New Software Release File from the Flash Disk........................................... 12-6
12.6 Upgrading Software using the CLI (SFTP) ............................................................................ 12-8
Pinging the PC .................................................................................................................. 12-8
Activating the SFTP Server ............................................................................................... 12-8
Downloading the New Software Release File to Megaplex-4 Flash Disk............................ 12-9
Installing the New Software Release File from the Flash Disk......................................... 12-11
12.7 Upgrading Megaplex-4 Software via the Boot Menu ......................................................... 12-12
Starting Boot Manager ................................................................................................... 12-13
Using the TFTP/FTP Protocol .......................................................................................... 12-15
Using the XMODEM Protocol .......................................................................................... 12-17
12.8 Verifying the Upgrade Results .......................................................................................... 12-19
12.9 Restoring the Previous Software Version.......................................................................... 12-20
Appendix A. Connection Data

Appendix B. I/O Modules
Appendix C. Test Plan
Megaplex-4 xix
xx Megaplex-4
Chapter 1
Introduction
1.1 Overview
RAD’s Megaplex-4 multiservice next generation access nodes are high-capacity,
carrier-class multiservice concentrators, which transport traffic over fiber or
copper and provide multiple Legacy and next-generation services on
PDH/SDH/SONET or packet-switched networks (PSN). The Megaplex-4 family
includes two devices: a powerful 10-slot Megaplex-4100 and a compact 4-slot
Megaplex-4104.
Megaplex-4 is an ideal solution for carriers and private network operators in
migrating their networks and services to next-generation communications.
Featuring dual star connection architecture with hybrid TDM-Ethernet modules
allows native TDM and native Ethernet traffic handling with minimal encapsulation
delays and zero bandwidth overhead. In networks with SDH/SONET backbone,
Ethernet can be carried over VCG. In addition, it is equipped with a full standards-
based pseudowire emulation suite, ensuring TDM service quality is maintained
when migrating the services from TDM network to packet switched network.
Carrier class service reliability is ensured with system redundancy options, link
and path protection schemes and enhanced support for diverse ring topologies.
Handling a broad range of SDH/SONET, E1/T1, Ethernet, data and voice services,
various network topologies and versatile access media in a single compact
managed node, makes Megaplex-4 a versatile and cost-effective next-generation
multiservice access node solution for large enterprises, including utilities,
transportation and campuses, as well as for carriers and service providers.
Product Options
Chassis
Megaplex-4 systems are available in two chassis sizes:
• Megaplex-4100 – 4U-high chassis can accommodate up to 10 I/O modules.
• Megaplex-4104 – compact 2U-high chassis can accommodate up to 4 I/O
modules. It is a cost-effective alternative for power utility substations, service
providers, and small POP or branch office applications or for sites with limited
space. There is also a special Megaplex-4104 chassis ordering option
complying with IEEE-1613 environmental requirements (for
teleprotection/communications devices in the power utilities substations as
well as other markets, see Chapter 2 for details).
Megaplex-4 Overview 1-1

Chapter 1 Introduction Installation and Operation Manual
CL Modules
The CL.2 modules are provided in several flavors, to cater for specific needs of
each customer. Table 1-1 lists the functionalities supported by each CL.2 option.
A short description of CL.2/A and CL.2/DS0 options is given in this section below.
Table 1-1. Features Supported by CL.2 Options
CL.2/622GBEA CL.2/GBEA CL.2/622GBE CL.2/DS0
SDH/SONET + - + -
DS0 Cross-Connect + + + +
E-line + + + Inside modules only
E-LAN + + M-ETH only M-ETH only
E-Tree + + - -
Management VLAN via VCG + - - -
Flow between modules (CL and I/O) + + + -
Traffic Management
+ + - -
(Scheduling/Shaping)
Ethernet Protection
ERPS + + - -
LAG + LACP + + - -
LAG + + + -
HSR + + - -
RSTP + + - -
Ethernet group protection - - + -
Security
802.1x + + - -
Service Assured Access
CIR, CBS, EIR and EBS per flow + + - -
CIR, CBS per port + + - -
Classification per P-Bit/DSCP + + - -
Classification per single or double VLAN + + + -
Ethernet OAM + + - -
VLAN editing Inner + Outer Inner + Outer Outer Outer
Ethernet PM + + - -
Timing
Internal Clock Quality ST-3E ST-3E ST-3E ST-4
1-2 Overview Megaplex-4

Installation and Operation Manual Chapter 1 Introduction
Clock Quality Status (SSM) + + - -
SyncE + + -
Diagnostics
Ethernet BERT + + + -
TDM BERT + + + +
Carrier Ethernet (CL.2/A Assembly)

The CL.2/A assembly provides carrier Ethernet capabilities, such as Ethernet
traffic management (TM), standards-based Ethernet Operations, Administration
and Maintenance and Performance Monitoring (OAM&P), as well as carrier grade
Ethernet functionality.
These functionalities are available on any MAC entity, such as the CL module GbE
ports, VCG, Ethernet module (M-ETH)_ports, etc.
This assembly can be ordered with or without SDH/SONET interface.
SDH/SONET Interface
Two SDH/SONET ports located on the CL.2 modules can be ordered in two
versions:
• STM-1/OC-3 only, with software key license upgrade to STM-4/OC-12 if
required
• Software-configurable to STM-4/OC-12 or STM-1/OC-3, with software key
license built-in.
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical.
GbE Interface
The GbE ports can be ordered with one of the following interfaces:
• 10/100/1000BASE-T (UTP) copper ports. This type of ports support 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.
DS0 Cross-Connect
A basic low-cost version of CL.2 modules is supplied without SDH/SONET and GbE
ports.
CL Module for “No Fans” Operation
The Megaplex-4100 chassis can be ordered with special CL.2 options complying
with IEEE-1613 to support “No Fans operation” requirement.

PS Modules
PS modules for Megaplex-4100 and Megaplex-4104 have different shape and
technical characteristics (see Table 1-10). AC or DC power supplies are available
for both chassis. The DC modules can be ordered with selectable ground
reference or floating ground.
Megaplex-4 can be ordered with one power supply module, or with two power
supply modules, for redundancy.
The Megaplex-4100 chassis also has a selection of PS options complying with
IEEE-1613 to support “No Fans operation” requirement.
Applications
Central Solution for RAD CPE Devices

Megaplex-4 offers a complete, end-to-end solution as a central aggregation
platform for diverse CPE devices managed together under RADview. Megaplex-4 is
interoperable with DXC, MP-2100/2104, FCD, ASMi, Optimux, as well as ETX, RICi
and IPMUX family devices.
Figure 1-1 illustrates Megaplex-4 as a central site solution, Ethernet and TDM
aggregator for SDH/SONET and PSN networks.
Wireless
FE
Airmux
Video
Airmux
E3 Chanellized
FE
Router FCD-IP
STM-1
DXC-8R FCD-E1E
n x E1 ETH E1
FE/GbE
PSN RICi-8 DXC-4
POP FE E1
IPmux
SHDSL ETH
E1/V.35
SHDSL.bis
ASMi
ETH
Megaplex-4 FO
STM-4/ n x E1
OC-12 Optimux
SDH/SONET
STM-1/
SHDSL ETH
OC-3
SHDSL.bis E1/V.35
ASMi-53
T3 FE ETH
RV Station ETX
ETH
STM-1/OC-3
E1/T1
FCD-155E
Voice
E1/T1 Data
ETH
MP-2100/2104
T3
Radio
Megaplex-4104
Radio
Figure 1-1. Megaplex-4 as a Central Site Aggregator for different RAD CPEs,
Ethernet and TDM Aggregator for SDH/SONET and PSN

TDM and Ethernet Multiservice Access

Enterprises, campuses and utility companies can deploy Megaplex-4 as a core or
an edge device to create a diversity of STM-1/STM-4/OC-3/OC-12 or Ethernet
rings, multiplexing voice, fax, data, and other low speed traffic. Megaplex-4 can
also groom and cross-connect between channels and terminate Ethernet traffic.
Megaplex-4 can work with industry-specific devices, such as Teleprotection and
Omnibus units (see Figure 1-2).
Control Center
GbE
PSN
Megaplex-4100 SDH/SONET/ETH
FO
E1/T1 Megaplex-4104 Megaplex-4104
Airmux-400
Megaplex-4100 FXS FXS

E&M PA E&M PA
SHDSL.bis FO
E1/T1
Airmux-400
TAC TAC
Megaplex-2100 PBX PBX
LAN LAN
ASMi Optimux
SCADA
LAN LAN
Figure 1-2. Megaplex-4 as Multiservice Platform for Transportation and Power Utilities
Smooth Migration from TDM to PSN

Megaplex-4 equipped with the MPW-1 module provides legacy services over
packet-switched networks (PSN). The MPW-1 module converts the data stream
from other modules in the Megaplex-4 chassis (E1/T1, SHDSL, data or voice
ports) delivered by the internal Megaplex backplane via MPW-1’s internal DS1
ports into IP or MPLS packets for transmission over Ethernet, IP or MPLS
networks. The ASIC-based architecture provides a robust and high performance
pseudowire solution with minimal processing delay. MPW-1 supports various
legacy services over packet transport types, including TDMoIP, CESoPSN, SAToP,
HDLCoPSN (see Figure 1-3).

E1
Remote Sites
SHDSL.bis
PBX
E1 POP ASMi-54
FE
FO Megaplex-4100
PBX
LAN
Optimux-108 GbE
FE ERP
E1
Video
FO
PBX
E1 Optimux-108
FE
SHDSL.bis
PBX Central Office
VoIP
ASMi-54
FE
Megaplex-4100
E1
Video
PBX
E1
FO ASMi-54
SHDSL.bis FE
PBX
NMS LAN
Optimux-108
FE
POP
LAN E1
STM-1/
OC-3 FO
SDH/SONET PBX
FXS Optimux-108
Megaplex-4104 FE
E1
Video
X.21 FCD-E1L
FXS
E1/T1
Megaplex-2104 V.35
Figure 1-3. Migrating TDM and Ethernet Services from SDH/SONET to PSN
Carrier Ethernet Services

Megaplex-4 delivers Ethernet services as defined by the MEF standards. MEF
identifies three types of standardized Carrier Ethernet services, each of
which corresponds with a set of UNI attributes and EVC attributes:
• E-Line: A point-to-point connection, where each EVC links two UNIs. E-Line
services can be of either of two variants:
 Ethernet Private Line (EPL): An E-Line-type service (see Figure 1-4) in
which only one point-to-point EVC is supported by the same physical
interface at both UNIs, i.e. no service multiplexing is allowed. EPL may
be delivered as a guaranteed bandwidth service, whereby the carrier
provides SLA-based rate and performance commitments and allocates
network resources accordingly, similar to a leased line service.
 Ethernet Virtual Private Line (EVPL): An E-Line service (see Figure 1-5)
allowing service multiplexing so that a single UNI supports multiple
EVCs. As data frames may be mapped to different EVCs, an EVPL
service is not required to provide full frame transparency, unlike an EPL
service. User traffic is distinguished by different VLAN IDs and

transported over common network resources, thereby necessitating

traffic policing/shaping functionalities at the provider network ingress.
• E-LAN (Ethernet Local Area Network): A multipoint-to-multipoint topology,
where each EVC links more than two UNIs. The following are designated as E-
LAN services:
 Ethernet Private LAN (EPLAN): A multipoint service (see Figure 1-6),
requiring a dedicated UNI per EVC, in which service multiplexing is
prohibited. Other service attributes are similar to those of a point-to-
point EPL service.
 Ethernet Virtual Private LAN (EVPLAN): An E-LAN-type service (see
Figure 1-7) allowing EVC multiplexing at the UNI, similar in attributes to
an EVPL. A flow based EVPLAN service enables service multiplexing for
applications such as departmental LAN differentiation – by service,
location or user function – at the UNI level.
• E-Tree: A service using a multipoint rooted EVC, whereby one or more of the
UNIs are classified as “Roots”, while all other UNIs are designated as
“Leaves”. Traffic delivery is permitted between a Root and a Leaf, in both
directions, but prohibited between Leaves. Specific Root/Leaf subsets and
the corresponding traffic delivery rules depend on particular service
definitions.
Figure 1-4. EPL (Ethernet Private Line) Service

Figure 1-5. EVPL (Ethernet Virtual Private Line) Service
Figure 1-6. EP-LAN (Ethernet Private LAN) Service
Figure 1-7. EVP-LAN (Ethernet Virtual Private LAN) Service

Features
PDH Access
Megaplex-4 delivers PDH Access at E1/T1 and fractional E1/T1 level with up to
160 E1/T1 ports per chassis over copper or fiber, including access over
2-wire/4-wire/8-wire SHDSL, with up to 80 SHDSL ports per chassis.
Data Services
Megaplex-4 provides up to 120 multichannel sub-DS0 low speed data, 64-kbps
codirectional G.703 channels, teleprotection channels, multichannel ISDN access
(up to 120 ISDN “U” and/or “S” type ports per chassis), and 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
Voice services are provided by analog and digital voice modules (up to 4800 voice
channels per chassis for E1 ports, up to 3840 voice channels for T1 ports), with
support for special services such as omnibus and party lines. Voice channel
processing can include user-defined signaling translations.
SDH/SONET Services
SDH/SONET services are provided by up to 4 separately configurable STM-1/STM-
4 or OC-3/OC-12 links per node, with support for APS (Automatic Protection
Switching) for line redundancy.
Ethernet Layer 2 Services

Ethernet Layer 2 services are supported by various I/O modules with Ethernet
ports, and 4 GbE ports on CL modules. Up to eight separately configurable
Ethernet ports are available per I/O module; each CL module has two GbE ports,
for up to four separately configurable GbE ports per chassis. Megaplex-4 can
provide Ethernet traffic termination for transport over E1, T1, SHDSL uplinks,
virtually concatenated group uplinks and high and low-order SDH/SONET
VC-12/VC1.5 virtual containers. It can also serve as Ethernet access concentrator
with GbE uplinks.
Incoming Ethernet traffic is classified and mapped according to port-based
(all-in-one) bundling or by user port and CE VLAN-ID, VLAN priority, DSCP, IP
precedence, and Ethertype. This offers operators the flexibility to differentiate
services using traffic management TM tools, such as traffic policing, queuing and
shaping, and enforce SLA per service.
Megaplex-4 supports powerful bandwidth profiles such as CIR/CBS and EIR/EBS for
differentiated Ethernet services and includes comprehensive Ethernet OAM
(Operation, Administration, and Maintenance) and Ethernet Performance
Monitoring functionality together with SLA monitoring.
Forwarding Schemes
Traffic forwarding is performed using point-to-point (E-Line) or bridge (E-LAN,
E-TREE) mechanisms.

Service Types
Megaplex-4 provides port- and flow-based services.
Port-Based Service
In a typical port-based (all-to-one bundling) application Megaplex-4 receives
different services via different user ports (Figure 1-8). This method achieves
clearer service separation, it does not require any customer marking for CoS.
Customer Premises
Service Provider Node GbE
VoIP
Packet Switched GbE Premium

Network Data
(Ethernet, IP or MPLS)
PE Megaplex-4
GbE Best Effort
Data
Figure 1-8. Port-Based Service
Flow-Based Service
In a typical flow-based application different services are assigned to different
Ethernet flows received by the same user port (Figure 1-9). This provides a
cheaper, more scalable solution, with a possibility of mixing different service
types.
Service Provider Node Customer Premises
Packet Switched GbE Premium Best Effort

VoIP
Network Data Data
PE Megaplex-4
Figure 1-9. Flow-Based Service
Flow Classification
The ingress user traffic is mapped to the Ethernet flows using the following list of
per-port classification criteria. In the classifications, VLAN refers to the service
provider (outer) VLAN, previously referred to as SP-VLAN, while inner VLAN refers
to the Customer Entity VLAN, previously referred to as CE-VLAN.
• Port-based (All to one bundling)
• VLAN
• VLAN + VLAN priority
• VLAN + IP precedence
• VLAN + DSCP
• VLAN + inner VLAN
• VLAN + VLAN priority + inner VLAN
• VLAN + Ethertype

• VLAN priority
• IP precedence
• DSCP
• Ether Type
• Untagged
Megaplex-4 supports up to 512 Ethernet flows. Flows between external Ethernet
ports and the CL.2/A bridge are bidirectional. All other flows are unidirectional.
Tagging and Marking

Megaplex-4 supports several options for marking and tagging.
You can perform the following marking and tagging actions:
• Overwrite inner or outer VLAN with a new value
• Overwrite inner or outer VLAN p-bit with a new value.
You can perform the following tagging actions:
• Add (push) outer VLAN, with p-bit value that can be copied from the original
value or set to a new value. When you add a new VLAN, the original outer
VLAN becomes the inner VLAN.
• Remove (pop) outer VLAN and p-bit. When you remove a VLAN, the inner
VLAN becomes the outer VLAN.
• Add (push) inner VLAN, with p-bit value that can be copied from the original
value or set to a new value
• Remove (pop) inner VLAN and p-bit.
Only certain combinations of actions on the outer and inner VLAN are allowed.
Refer to Chapter 8 for details on the permitted combinations of actions.
L2CP Handling
Megaplex-4 can be configured to pass through (“tunnel”) Layer-2 control frames
(including other vendors’ L2CP frames) across the network, to peer supported
protocols, or to discard L2CP frames.

Fault Propagation
The user can configure fault propagation between any two ports in Megaplex-4,
as shown in the figure below.The fault propagation behavior is according to the
port type (refer to Chapter 7 for details).
Megaplex-4
Packet Switched
Network
CPE
Network Termination
Unit
Figure 1-10. Fault Propagation
Traffic Management and Service Level Agreement (SLA)

Monitoring, Troubleshooting and Measurement
Powerful tools assure Megaplex-4’s ability to analyze the current traffic load and
dynamically make necessary adjustments to accommodate the different types of
traffic or changing conditions. RAD also provides effective service-level
agreement (SLA) monitoring tools such as Ethernet service OAM (CFM), Ethernet
link OAM (EFM) etc.
Quality of Service (QoS)

Megaplex-4 efficiently handles multi-priority traffic on a per-flow basis, that
enables simultaneous processing of hundreds of service flows. The device
enables multi-criteria traffic classification as well as metering, policing and
shaping to help carriers rate-limit user traffic according to predefined CIR
(committed information rate) and EIR (excess information rate) profiles.
Enhanced quality of service is further supported by up to 2-level hierarchical
scheduling mechanism that combines Strict Priority (SP) and weighted fair queue
(WFQ) scheduling, to efficiently handle real-time, premium and best-effort traffic.
Scheduling and shaping are supported at the EVC, and port levels.
Megaplex-4 also uses weighted random early detection (WRED) policy for
intelligent queue management and congestion avoidance. Packet editing
capabilities include 802.1ad Q-in-Q tagging and color-sensitive P-bit re-marking,
which ensures metering continuity across color-aware and color-blind Metro
networks and WANs.
Different service types require different levels of QoS to be provided end-to-end.
QoS can be defined per subscriber as well as per flow. QoS has three aspects:
policing (rate limitation), traffic prioritization and traffic shaping.
Traffic Policing
A policer is per flow. The policers meter, mark and rate-limit the traffic according
to the dual token bucket mechanism (CIR+CBS, EIR+EBS). A special mechanism

compensates for Layer 1 headers. Traffic can be limited to the line rate or the
data rate.
In addition, Megaplex-4 features unique p-bit re-marking capabilities that assign
color-specific p-bit values to Ethernet frames at network ingress to ensure
metering continuity across the Metro Ethernet network. User traffic that was
marked “yellow” according to the CIR/EIR parameters by the device QoS engine is
assigned a new p-bit value to signal its status and priority, so that it is dropped
first by 802.1Q and 802.1ad (a.k.a IEEE 802.1QinQ ) network elements in the
event of congestion. This is especially useful in color-blind as well as color-aware
networks with no “discard eligible” (“yellow”) marking.
Traffic Prioritization (Queuing)

Once traffic is classified to a flow, it can be mapped to Strict (Strict Priority)
queues or WFQ (Weighted Fair Queues):
• Strict. The data flow set to the highest priority is transmitted first. If this data
flow stops, all tasks at lower priorities move up by one priority level. For
example, the data flow set to the second-highest priority is then transmitted
at the highest priority.
• WFQ. Allows different scheduling priorities to statistically multiplex data flows
with different shares on the service. Each data flow has a separate FIFO
queue. A link transmitting at a data rate R, all non-empty data flows N are
served simultaneously according to the assigned share w, each at an average
rate of R/(w1 + w2 + w3 + … +wN). If one data flow stops, the remaining data
flows each receive a larger share w.
The WRED mechanism ensures that queues are not congested and high-priority
traffic is maintained. Each queue is assigned a WRED profile for which you can
configure the thresholds and probability to suit your needs.
Queue Group
Level 0 Level 1
1
Flow1 2
Queue 3
Block 0
4
UNI Flow2 1
2
2 3
Queue
Block 1 3
4
Flow3
1
Figure 1-11. Queue Structure – Towards CL.2/A GbE Port

Level 0 contains up to 8 queue blocks per CL.2/A GbE port. Each block has up to
eight queues and its own scheduling (Strict and WFQ). For each queue block in
level 0, there is a queue in level 1 that represents the scheduling between the
queue blocks in level 0. Flows can be bound to each queue block in level 0.
Queue Group
Level 0
Flow1
UNI Flow2 2
Flow3
Figure 1-12. Queue Structure – Towards User Ethernet or VCG Ports

Level 0 contains a single queue block per Ethernet port. Each block has up to
eight queues and its own scheduling (Strict and WFQ). Flows can be bound to
each queue block in level 0.
Queue Mapping
For the network ports (CL.2/A GbE), Megaplex-4 supports up to 8 queue blocks
per queue group. Towards the user ports, a single queue block with up to eight
queues is supported. Flows that are in the direction user port to network port
can be bound to one of up to 8 queue blocks, and flows that are in the direction
network port to user port can be bound to one of eight queues.
The queue mapping functionality associates the user priorities with queue
numbers (CoS).
The queue mapping functionality is bound to each flow.
Hardware-Based SLA Monitoring and Troubleshooting (Ethernet

OAM) and Measurement (Performance Monitoring)
Featuring ultra-fast, hardware-based processing capabilities, Megaplex-4
performs OAM and PM measurements in under1 ms with maximum precision.
Megaplex-4 provides OAM to monitor and troubleshoot an Ethernet network and
quickly detect failures:
• CFM OAM (End-to-end OAM) based on IEEE 802.1ag and Y.1731 for continuity
check, non-intrusive loopback and link-trace, and performance monitoring

• EFM OAM (Link OAM) according to IEEE 802.3-2005 (formerly IEEE 802.3ah)
for remote management and fault indication, including discovery, link
monitoring, remote fault detection (dying gasp) and remote loopback.
Megaplex-4 offers advanced Ethernet service assurance tools, including user-
defined KPI (key performance indicators) threshold configuration for delay
(latency), delay variation (jitter), packet loss and availability. Other tools include
real-time SLA violation alerts and per-flow statistics reporting.
Flexible Ethernet Transport over TDM

Flexible Ethernet transport options over TDM links provide full support for
Ethernet services over existing TDM infrastructures with efficient bandwidth
utilization for each type of application, and also enable cost-effective migration
to packet switched transport. The available Ethernet transport options include:
• HDLC bundles with selectable number of timeslots over individual external E1
and T1 links, and internal PDH ports of the SDH/SONET subsystem
• Wideband, multilink MLPPP bundles over E1 links, with a bandwidth of up to
16.384 Mbps (the equivalent of eight E1 links)
• Virtually concatenated groups over SDH/SONET links, with selectable
granularity down to VC-12/VT1.5/VC-3/VC-4/STS-1/STS-3C, Megaplex-4
performs low-order and high-order virtual concatenation, including GFP
encapsulation per ITU-T Rec. G.7041 or LAPS per ITU-T Rec. X.85/X.86. For
reliable transmission, Megaplex-4 also supports LCAS per ITU-T Rec. G.7042.
Flexible TDM Transport over Ethernet

Megaplex-4 supports TDM pseudowire (PW) circuit emulation for E1 and T1 over
IP and MPLS packet-switched networks. It complies with the pseudowire edge-to
edge emulation (PWE3) standards, including TDMoPSN, HDLCoPSN, CESoPSN and
SAToP, and therefore it is compatible with other pseudowire equipment offered
by RAD, such as Gmux-2000 Pseudowire Gateways, the IPmux family of TDM
Pseudowire Access Gateways, as well as with previous generations of Megaplex
equipment with IP main link modules.
Fiber Multiplexing
Megaplex-4 also features multiport fiber multiplexing modules, for transporting 4
or 16 E1 streams, together with Ethernet traffic of up to 100 Mbps, over
proprietary fiber optic links to compatible standalone units offered by RAD for
use at customers’ premises.
DS0 Cross-Connect
Megaplex-4 features an internal DS0 cross connect matrix of up to 8384/6080
channels. Traffic from any channel can be cross-connected directly to any other
channel.
These capabilities enable Megaplex-4 to function as a service differentiation point
at the headquarters, handing off traditional voice and data services to the
transport network.

At the remote offices or customer premises, Megaplex-4 may also be deployed to

effectively fan out multiple voice and data services.
A special low-cost version of CL.2 modules is supplied without SDH/SONET and
GbE ports. This version provides an improved price/performance solution for DS0
cross-connect and channel-bank applications (see Table 1-4 for maximum
capacity) and LRS-102 replacement. It also creates a platform that allows
upgrade from a transparent rack to an aggregation with GbE &
STM-4/OC-12/STM-4/OC-3 solutions by simple replacement of a CL module.
Protection
The modular, distributed architecture of Megaplex-4 enables redundancy at
different levels of the network and provides a resilient system with no single
point of failure. Hardware redundancy is provided through an optional redundant
power supply and CL modules, with switchover to the backup CL links within
50 msec.
Each combined common logic, cross-connect matrix and broadband link module
(CL) provide automatic switchover between each two STM-1/STM-4/OC-3/OC-12
links within 50 msec, for 1+1 protection against hardware, network or cable
failure. The SDH/SONET employs APS 1+1 protection against link or hardware
failure as well as subnetwork connection protection according to ITU-T Rec G.841
(SNCP for SDH and UPSR for SONET) for path protection and ring topology. This
provides end-to-end service protection.
The CL Ethernet GbE ports employ LAG protection against link or hardware failure.
With the CL.2/A capabilities, Megaplex-4 supports Ethernet Ring Protection
Switching (ERPS) per ITU-T G.8032v1.
Selected I/O modules can also be configured for redundancy and can be
hot-swapped, allowing for continuous service.
For more detailed information about different redundancy types, refer to the
following:
• CL redundancy –Common Logic (CL.2) Modules in this chapter
• PS redundancy – Power Supply (PS) Modules in this chapter
• APS – Automatic Protection Switching section in Chapter 7
• Path protection – Path Protection for SDH/SONET Payload section in
Chapter 7
• I/O module redundancy – TDM Ring Protection, and TDM Group Protection
and I/O Group Protection sections in Chapter 7
• Ethernet protection – Configuring the LAG section in Chapter 7
• Ethernet group (Logical MAC-based) protection – Ethernet Group Protection
section in Chapter 7
• Hitless Switching Redundancy in Ring topology –HSR Protection section in
Chapter 7
• Ethernet Ring Protection - Ethernet Ring Protection (ERP) section in
Chapter 7.

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

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

module timing subsystem. If a problem is detected in the active timing

subsystem, the standby subsystem hitlessly takes over.
The user can define the following clock sources:
• Recovered from the STM-1/STM-4/OC-3/OC-12 interface, including automatic
selection, based on SSM (Synchronization Status Messaging)
• Recovered from the GbE interface (CL modules only), including automatic
selection based on ESMC (Ethernet Synchronization Messaging Channel)
• Internal crystal free-running oscillator-based clock
• Derived from the receive clock of a specified module user port
• ACR Adaptive clock recovered from a pseudowire circuit (MPW-1 modules
only)
• External station clock.
Multiple clock sources can be set and assigned corresponding quality and priority.
Megaplex-4 uses the highest quality stratum available, determined by monitoring
the synchronization status messages (SSM) of the configured SDH/SONET clock
sources.
For detailed information about the different system timing modes, refer to the
following sources:
• Clock Selection in Chapter 9
• Relevant I/O module section in the Megaplex-4 I/O Modules Installation and
Operation Manual.
Simple Network Time Protocol

The Simple Network Time Protocol (SNTP) provides the means of synchronizing all
managed elements across the network to a clock source provided by NTP servers.
Megaplex-4 supports the client side of a simple network time protocol (SNTP) v.3
(RFC 1769).
Management
Megaplex-4 offers carrier-class service provisioning features, including end-to-end
path management, to ensure continuous service availability. Advanced SNMP
management capabilities provide control and monitoring of all network elements:
SDH/SONET access and ring units as well as remote POP and Last Mile broadband
access feeders and CPEs.
Complete control over the Megaplex-4 functions can be attained via the following
applications:
• CLI-driven terminal utility for management via a local ASCII-based terminal
connection (see Working with Terminal and Terminal Control Port in Chapter
4). Telnet access is supported via IP-based connection.
• RADview – RAD’s SNMP-based element management system, providing a
dedicated PC/Unix-based GUI for controlling and monitoring the unit from a
network management station. It also includes northbound CORBA interface

for integration into any third-party NMS (network management system). For
more information, refer to the RADview User's Manual.
• Shelf View – RAD’s SNMP-based standalone application with fully FCAPS-
compliant element management. It displays a dynamic graphic representation
of the device panel(s), providing an intuitive, user-friendly GUI.
For more information about configuration alternatives, refer to Management

Alternatives in Chapter 4.
The unit can be managed by and report to up to 10 different users
simultaneously. Accounts of existing and new users can be defined/changed
remotely, using a dedicated RADIUS server as explained under Authentication via
RADIUS Server in Chapter 4.
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-4-based network.
Remote units can be managed in the following ways:
• Out-of-band, using the 10/100 Ethernet management port (for more
information, see Out-Of-Band Ethernet Control in Chapter 6)
• Inband, using IP/PPP or IP/HDLC over DCC, via the STM-1/STM-4/OC-3/OC-12
links (for more information, see SDH/SONET Ports in Chapter 6)
• Inband, using the IP/PPP or IP/FR over a dedicated timeslot in any E1/T1 or
SHDSL link (for more information, see the description of a relevant port in
Chapter 6, for example, Configuring E1 Ports).
• Inband, via any of the user Ethernet ports, including the CL module GbE ports
(see Configuring Flows in Chapter 8)
• Via a network management station running RADview, RAD’s SNMP element
management application.
Databases and scripts of commonly used commands can be easily created and
applied to multiple units using command line interface.
Software upgrades can be downloaded to CL and selected I/O modules. Preset
configuration files can be downloaded/uploaded to/from Megaplex-4 via TFTP or
SFTP. For more information and instructions, refer to Chapter 12.
Syslog
The syslog protocol is a client/server-type protocol, featuring a standard for
forwarding log messages in an IP network and supports up to four syslog servers
at present. A syslog sender sends a small text message of less than 1024 bytes
to the syslog receiver. Syslog messages are sent via UDP in cleartext. The Syslog
server acts as a centralized repository for all elements in the network, providing
for a unified logging infrastructure, easier troubleshooting and forensics, lower
operational risks and costs and higher availability and SLA through faster
response time.

Diagnostics
When a problem occurs, Megaplex-4 offers a set of diagnostic functions that
efficiently locate the problem (in the Megaplex-4 chassis, one of I/O modules, a
connecting cable, or external equipment) and rapidly restore full service.
The diagnostic functions are based on the activation of loopbacks at various
ports. These loopbacks enable identifying whether a malfunction is caused by
Megaplex-4 or by an external system component (for example, equipment, cable,
or transmission path connected to the Megaplex-4). A detailed description of the
test and loopback functions is given in Chapter 6, under the corresponding
section (for example, E1 Ports, SHDSL Ports).
Comprehensive diagnostic capabilities include:
• Local and remote loopbacks
• Real-time alarms to alert the user on fault conditions
• SDH/SONET link monitoring
• Ethernet traffic counters
• Ethernet, E1/T1, SHDSL and Optical interface status monitoring.
Alarm Collection and Reporting

Megaplex-4 continuously monitors critical signals and signal processing functions.
If a problem is detected, the Megaplex-4 generates time-stamped alarm
messages. The time stamp is provided by an internal real-time clock.
For continuous system monitoring, the user can monitor alarm messages through
the supervisory port. Alarm messages can also be automatically sent as traps to
user-specified network management stations.
The alarms can be read on-line by the network administrator using a Telnet host, an
SNMP-based network management station, or a supervision terminal.
Note
Megaplex-4 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-4 has two
alarm relays with floating change-over contacts: one relay for indicating the
presence of major alarms and the other for minor alarms. Each relay changes
state whenever the first alarm is detected, and returns to its normal state when
all the alarms of the corresponding severity disappear. The relay contacts can be
used to report internal system alarms to outside indicators, e.g., lights, buzzers,
bells, etc., located on an alarm bay or remote monitoring panel.
Performance Monitoring
Megaplex-4 collects statistics per physical port and per connection for 15-minute
intervals, which enables the network operator to monitor the transmission
performance and thus the quality of service provided to users, as well as identify
transmission problems. Performance parameters for all the active entities are
continuously collected during equipment operation.

Statistics for the last 24 hours are stored in the device and can be retrieved by
the network management station. For additional information, refer to the
Statistics section for the relevant port (for example Viewing Ethernet Port
Statistics under Ethernet Ports in Chapter 6).
Megaplex-4 maintains a cyclic event log file that stores up to 256 time-stamped
events. In addition, an internal system log agent can send all reported events to a
centralized repository or remote server. For additional information, refer to
Handling Events in Chapter 6.
RADview Performance Management

Megaplex-4 maintains performance management (PM) statistics for selected
entities in the device. The PM statistics are collected into a file periodically, for
retrieval by RADview, for display in the RADview PM portal (refer to the RADview
System User’s Manual for further details on the PM portal). The PM collection
process can be globally enabled or disabled for the entire device. In addition, the
statistics collection can be enabled for all entities of a specific type, or for
specific entities.
Security
User access to Megaplex-4 is restricted via user name and password. For more
information, refer to Management Access Methods in Chapter 4.
Telnet-like management can be secured using a Secure Shell (SSH) client/server
program. Instead of sending plain-text ASCII-based commands and login requests
over the network, SSH provides a secure communication channel.
SFTP (Secure File Transfer Protocol, also known as SSH File Transfer Protocol) is
supported, to provide secure (encrypted) file transfer using SSHv2.
In addition, Megaplex-4 supports SNMP version 3, providing secure access to the
device by authenticating and encrypting packets transmitted over the network.
For more information, refer to The SNMPv3 Mechanism in Chapter 4.
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network. For more information, refer to Authentication via RADIUS Server
Mechanism in Chapter 4.
1.2 New in this Version

The following new functionalities have been added since version 4.6:
• D-NFV Module –Full integration in the Megaplex-4 CLI
• SH-16 module –E1, PW and STU-R (CPE) support
• New interfaces added to multiservice VS I/O module:
 E1/T1 interfaces with EoP capabilities
 E1/T1 interfaces with pseudowire capabilities
 Various combinations of E1/T1 and serial services in a single module
Megaplex-4 New in this Version 1-21

• 802.1x – Port authorization based on 802.1x standard

• RSTP – Rapid Spanning Tree Protocol on CL.2/A GbE ports.
1.3 Physical Description
System Structure
Megaplex-4 units use modular chassis. The chassis has physical slots in which
modules are installed by the user to obtain the desired equipment configuration.
Megaplex-4 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 for
Megaplex-4100 and 4 for Megaplex-4104
• Multiplexing, timing and control subsystem, located on the common logic and
cross-connect (CL.2) modules.
• Power supply subsystem, located on the power supply (PS) modules
• Chassis. The main function of the chassis is to provide interconnections
between the various modules, and in particular to connect between the user
interfacing (I/O) modules, and the CL modules that provide the multiplexing
function and the optional connections to SDH/SONET and/or Ethernet
networks.
CL and PS modules are always installed in their dedicated chassis slots, whereas
the user interfacing modules can be installed in any of the other chassis slots
(called I/O slots).
Any operational Megaplex-4 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-4 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-4 units should be equipped with an additional
redundant system module of each type. Redundancy is also available for the
network interfacing subsystems.
The Megaplex-4 system is designed to automatically put a redundant module or
subsystem in service in case the corresponding system component fails, thereby
ensuring continuous system operation in the event of any single module failure.
Moreover, redundant modules may be inserted or removed even while the system
operates.
Description of Megaplex-4100 Chassis

Figure 1-13 shows a general view of the Megaplex-4100 chassis.
1-22 Physical Description Megaplex-4

Megaplex-4100 is built in a 4U-high chassis that is intended for installation in 19”

and 23” racks, using brackets attached to the sides of the chassis, 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 ANSI practice), or with the module panels toward the front
(per ETSI 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.
Figure 1-13. Typical Megaplex-4100 Chassis, General View
Rear View
Figure 1-14 show a typical rear panel of the Megaplex-4100 chassis and identifies
the slots and their use. The chassis 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.
Note the labels which designate the type of module that can be installed in each
slot:
• Slots labeled PS-A and PS-B (identified as ps-a and ps-b on supervision
terminal screens): power supply modules
• Slots labeled I/O-1 to I/O-10 (identified as slot 1 to slot 10 on supervision
terminal screens): I/O modules
• Slots labeled CLX-A and CLX-B (identified as cl-a and cl-b on supervision
terminal screens): CL modules.
In addition, each slot is keyed, therefore it is not possible to install a wrong
module type.
Megaplex-4 Physical Description 1-23

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.
Slot PS-A PS-B IO-1 IO-2 IO-3 IO-4 IO-5 CL-A CL-B IO-6 IO-7 IO-8 IO-9 IO-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 7 I/O 8 I/O 9 I/O 10
PS/DC PS/AC
PS/DC M8E1 HS-12/N VC-8/RJ VC-4/Omni HS-R/N CL-2 CL-2 MPW-1 M8E1 OP-34C ASMi-54C OP-106C
PS/DC FXS E&M
RS-232 CH. TST LOS
STATUS STATUS
1 LASER LASER
1 2 CLASS CLASS 1 2
L LOC E
1 1 L
I 3 4 2 I 3 4 S
N N H
5 6 CH-1 CH-1 LINK ACT 5 6
K ETH1 K D
7 8 REM M 3 ON LINE ALM ON LINE ALM 7 8 S
ETH2 L LINK/
LOC E LOS LOS ACT
.
4 b
CH-2 CH-2 S S
D D I O
REM M H 1 H 1 s P
/ / E A
LOC E S S
O O T
CH CH CH-3 CH-3 N N LINK/ HO
4-6 1-3 E 2 E 2 ACT P
REM M T T E
ON ON T B
LINK LOC E LINE LINE LINK
1-8 1-8
H
CH-4 CH-4 CH. ACT ACT 100 100
1-2 ACT
REM M
VDC-IN 1 1
VDC-IN
G G 1
b b O
LOC E E LASER LASER P
CLASS CLASS
2 2 1 1 A
CH-5 LASER
CLASS
C C 1 2
LASER REM O LINK O LINK LOSS
- + 72V CLASS E L
1 LOC N D N D
LASER
I
RTN +72V -48V T CLASS
+ - ACT ACT A ACT 1

24V T C T C H ACT N
E CH-6 E E E
R E R E L
Rx
ON 100-120VAC ACT 1
1 3 K
T O T O T T I AIS
REM
200-240VAC H L LINK H L LINK H H N
LINK LOC E O
Tx
1 E 1 LOSS
CH CH T LINK K T P
ON CH-7
10-12 7-9 H B H B
ACT 4
E C C 2
E
Rx
ACT REM CH. L L AIS 2

T T
LOC 3-4 O O LOSS
H E H
LINK A C A C LINK
Tx
2 CH-8
T 2
L K L K H LINK
REM A A 3
ACT
E R ON/LOS R ON/LOS E
Rx
ACT
T M M T
H H
LINK
Tx
3 3
LINK
PS Slots I/O Slots CL Slots I/O Slots
Figure 1-14. Megaplex-4100 Chassis, Typical Rear View
Front Panel
The front panel of the Megaplex-4100 chassis is shown in Figure 1-15. For
description of LED indicators, see Chapter 3.
POWER SUPPLY
B A
SYSTEM
ALARM TEST
MEGAPLEX-4100
Figure 1-15. Megaplex-4100 Chassis, Front Panel
Description of Megaplex-4104 Chassis

Figure 1-16 shows a general view of the Megaplex-4104 chassis.

Figure 1-16. Megaplex-4104 Chassis

The chassis has 8 slots:
• Two slots are reserved for power supply (PS) modules
• Two slots are reserved for CL modules
• The other 4 slots are intended for I/O modules. Each I/O slot can accept any
type of I/O module.
The Megaplex-4104 chassis is supplied with brackets for installation in racks. The
brackets are attached to the sides of the chassis, as explained in Chapter 2.
Figure 1-17 shows a typical rear view of the Megaplex-4104 chassis equipped
with two CL.2/4104 modules, and identifies the slots and their use.
Figure 1-17. Megaplex-4104, Front View

The front panel of the Megaplex-4100 chassis is shown below. For description of
LED indicators, see Chapter 3.
I/O Modules
Table 1-2 lists the I/O modules currently offered for the Megaplex-4 in the
alphabetical order of their names. Contact RAD Marketing for information on

additional modules that may be available for your specific application

requirements.
Table 1-2. Megaplex-4 I/O Modules
Megaplex-
Module Description 2100/2104
Compatible
ACM Alarm and diagnostics module with four outbound relays for reporting Yes
internal alarms to outside indicators such as bells, buzzers, etc. Eight
inbound sensors enable external alarms or conditions to be reported to
the Megaplex system.
ASMi-54C Eight-port SHDSL.bis module with two Ethernet ports, for 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/ASMi-54L
standalone unit offered by RAD.
Has eight independently configurable SHDSL.bis external ports for SHDSL
services, and two 10/100 Mbps Ethernet ports, for packet-based
services.
Can operate as a Central SHDSL.bis (STU-C) or Remote (STU-R) SHDSL.bis
Terminal Unit for up to 8 ASMi-54 standalone devices or another ASMi-
54C module.
ASMi-54C/N Eight-port SHDSL.bis modules with eight E1 and two optional Ethernet No
ports, for transporting digital data to customer premises over the
existing copper infrastructure of the distribution network, while
eliminating the need for repeaters. Transparently forward E1 data and
optionally Ethernet, over 1 or 2 pairs of SHDSL.bis/SHDSL copper lines to
ASMi-54/ASMi-54L (SHDSL.bis) or ASMi-52/ASMi-52L (SHDSL) standalone
modems on the remote site.
Have eight independently configurable SHDSL.bis external ports for
SHDSL services, eight E1 ports for E1 services and two optional 10/100
Mbps Ethernet ports, for packet-based services.
D-NFV Virtualization module, adding to Megaplex-4 a built-in standard Intel x86 No

core that hosts virtual machines providing virtual network functions (VFs)
or value-added service capabilities. The module had one GbE and four
Fast Ethernet user ports.
HS-6N, High-speed data module, providing 6, respectively 12, high-speed V.35 Yes
HS-12N or RS-530/V.11 data channels. 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. Any channel can be directed to any E1
or T1 link or internal PDH port.
HS-703 High-speed data sub-channel module, providing four 64-kbps Yes
codirectional ITU-T Rec. G.703 data channels.

Megaplex-
Compatible
HS-RN Low-speed data module, providing 4 synchronous or asynchronous data Yes

channels with ITU-T Rec. V.24/EIA RS-232 interfaces, each operating at
an independently selectable data rate in the range of 0.6 kbps up to
38.4 kbps in the asynchronous mode, and up to 64 kbps in the
synchronous mode. End-to-end control signals are also supported.
Available in two models:
• HS-RN/HDLC: employing proprietary, HDLC-based, rate adaptation for
performance optimization with respect to either bandwidth or
latency, in accordance with user configuration
• HS-RN/V.110: employing V.110 rate adaptation, fully compatible with
the old HS-R module. Enables optimum rate utilization of uplink
bandwidth and minimum end-to-end data latency
Supports unidirectional broadcast applications.
HS-S ISDN basic rate access module with four type “S” interfaces. Performs 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-4 links,
and can provide phantom feed to user equipment
HS-U-6, ISDN basic rate access module with 6, respectively 12, type “U” interfaces. Yes
HS-U-12 Performs submultiplexing and data rate adaptation on B channels per ITU-T
Rec. I.460. The module supports two operation modes:
• /I: intended for extension of ISDN lines, can provide phantom feed to
user equipment. Supports 2B + D channels, and the channel data rates
are user-selectable (16, 32, and 64 kbps for each B channel, and
16 kbps for the D channel).
• /1: intended for use over leased lines, and can be used as dedicated
line termination units for the ASM-31 and ASMi-31 short-range
modems offered by RAD. Supports user channel data rates of 4.8,
9.6, 19.2, 48, 56, and 64 kbps over each B channel, and 128 kbps by
combining the two B channels. The D channel is ignored.
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.
LS-6N, Data sub-multiplexer modules, providing 6, respectively 12, synchronous Yes
LS-12 or asynchronous data channels with ITU-T Rec. V.24/EIA RS-232
interfaces, each operating at independently selectable data rate in the
range of 2.4 to 64 kbps. Support end-to-end transmission of control line
per channel. LS-12 channels can be bundled into two groups, each
independently routed to a different destination.
M-ETH Module with 8 GbE interfaces supporting optical or electrical media and No
providing 9 Gbps switching capacity (up to 1 Gbps capacity to the CL.2
module and 8 Gbps shared among its 8 external ports). The capacity can
be allocated among the 8 interfaces with a granularity of 100 Kbps.

Megaplex-
Compatible
M16E1 Module with 16 E1 DSU interfaces, providing up to 160 E1 ports per No

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

chassis and transparent T1 transfer to SONET.
M8E1 Module with eight E1 interfaces and user-selectable DSU or LTU mode, No
and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
M8T1 Module with eight T1 interfaces and user-selectable DSU or CSU mode, No
and three 10/100 Mbps Ethernet ports with optical SFPs or copper
interfaces (in accordance with order) for Ethernet services. The three
Ethernet ports are connected to an internal Ethernet switch, and share a
100 Mbps Fast Ethernet connection to the CL module.
M8SL Module with eight SHDSL interfaces, for transporting E1 and fractional No
E1 payloads, and three 10/100 Mbps Ethernet ports with optical SFPs or
copper interfaces (in accordance with order) for Ethernet services. The
three Ethernet ports are connected to an internal Ethernet switch, and
share a 100 Mbps Fast Ethernet connection to the CL module.
Each port features an independent multi-rate SHDSL modem,
transmitting at user-selectable data rates in the range of 192 kbps to
2048 kbps. Has internal non-blocking full cross-connect matrix similar to
M8E1 and M8T1 modules.
SHDSL interface type (STU-C or STU-R) is user-selectable.
Compatible with other RAD equipment having STU-R SHDSL interfaces,
such as the ASMi-52 SHDSL Modems. M8SL modules will also operate in
a link with 991.2-compatible STU-R units from other vendors.
MPW-1 Pseudowire server I/O module that provides TDM pseudowire access No
gateway services over packet-switched networks (Ethernet, IP, and
MPLS) for TDM traffic (E1, T1, SHDSL, ISDN, high-speed and low-speed
data, voice) received via the Megaplex-4 TDM buses from other modules.
Has eight independently-configurable internal DS1 ports, each capable of
handling 32 timeslots, for a total processing capacity of 256 timeslots
(the equivalent of 8 E1, or 2.048 Mbps streams).

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

independently and can operate in a link with the Optimux-108 and
Optimux-108L, 4 E1 and Ethernet Multiplexer standalone units offered by
RAD.
Each multiplexer transparently transports four independent E1 data
streams and one 100BASE-TX Ethernet channel over one optical link.
Each link has two optical ports, with user-configurable redundancy
between the two ports.
The optical ports can be equipped with field-replaceable SFPs. Support
for standard SFP optical transceivers link interfaces enables selecting the
optimal interface for each application. High-performance SFPs available
from RAD can achieve ranges of up to 120 km (75 miles).
OP-34C 16-channel E1 and Ethernet multiplexer, transporting 16 independent E1 No

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

customer premises via High speed Digital Subscriber Line
(SHDSL/SHDSL.bis) technology, as standardized by ITU-T Rec. G.991.2.
Each SHDSL.bis port is a multirate SHDSL/SHDSL.bis modem transmitting
user-selectable data rates up to 5.7 Mbps on each pair. Extended rates
of up to 15 Mbps per 2W/30 Mbps for 4W are available for ASMi-54L
modem at the far end (EFM mode).
SH-16 transports Ethernet over 1 (2-wire), 2 (4-wire), and 4 (8-wire)
pairs of SHDSL.bis copper lines.
T3 Single-port multiplexer module, providing access to standard T3 No

equipment over unbalanced copper lines with full duplex data rates of
44.7 Mbps.
TP Command In/Out teleprotection module with four selectable voltage No

(Teleprotection) inputs and eight outputs, secured and reliable end-to-end commands
transmission.

Megaplex-
Compatible
VC-16, Analog voice modules VC-16, VC-8 and VC-4 provide 16, 8 or 4 Yes
VC-8, PCM-encoded toll-quality voice channels.
VC-4, The modules are available in three models:
VC-8A,
• E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464
VC-4A
Types I, II, III and V, and BT SSDC5
• FXS: 2-wire interfaces for direct connection to telephone sets
• FXO: 2-wire interfaces for direct connection to PBX extension lines.
VC-8A and VC-4A are similar to VC-8 and VC-4 modules, except that they
also support ADPCM.
VC-6/LB 6-port PCM voice module for local battery telephones. It is a Yes
user-programmable voice interface module for Megaplex-4 used for
connection of local battery-powered (LB) telephones. The voice channels
use toll-quality 64 kbps PCM voice encoding in compliance with ITU-T
Rec. G.711 and AT&T Pub. 43801.
VC-4/ OMNI “Omnibus” E&M voice module providing four toll-quality voice channels. Yes
Intended for broadcast applications, in which a master site needs to
communicate with multiple remote stations simultaneously (such as to
broadcast an important message). Also provides party-line service.
VS Modules Multiservice versatile module with broad variety of services available in a No

single module:
• VS-12: 12 serial data ports and 2 Ethernet ports
• VS-6/BIN: 6 serial data ports, 8 in/out binary command ports and 1
Ethernet port.
• VS-6/C37: 6-port serial module with 2 fiber optic C37.94 ports and 1
Ethernet port
• FXS/E&M: Voice module with 4 E&M ports and 8 FXS ports
• VS-6/E&M: 6-port serial module with 4 E&M voice ports and 1
Ethernet port
• VS-6/FXO: 6-port serial module with 8 FXO voice ports and 1 Ethernet
port
• VS-6/FXS: 6-port serial module with 8 FXS voice ports and 1 Ethernet
port
• VS-16E1T1-EoP 16-port E1/T1 module with EOP support
• VS-16E1T1-PW: 16-port E1/T1 module with pseudowire support
• VS-6/E1T1: 6 serial data ports, 8 E1/T1 ports and 1 Ethernet port
Note
Some of the modules behave differently in the Megaplex-4100 /4104 and
Megaplex-2100/2104 chassis.

Common Logic (CL.2) Modules

The Common Logic (CL.2) module controls the Megaplex operation and is the
interface for its configuration and management.
CL.2 houses the TDM and Packet processing engines, as well as the GbE and
SDH/SONET uplinks.
For direct connection to the SDH/SONET network, CL.2 features two standard
network ports with a software-configurable STM-1/STM-4 or OC-3/OC-12
interface. The dual ports on the CL.2 module can be used either for operation in
parallel or for redundancy.
For direct connection to packet-based networks, CL.2 has two UTP or SFP-based
GbE ports. The UTP interface features autonegotiaton speed detection
capabilities.
Megaplex-4 allows the installation of two CL.2 modules of the same type, to
ensure continuous operation when one module is reset, restarted, or stops
operating for any reason. In such a case, the redundant main module immediately
takes over the unit, using its own pre-configured settings. The switch-over to the
protecting module occurs automatically upon detection of failure in the active
module, or upon removing the active module from the chassis. The SDH/SONET
and/or Ethernet traffic subsystems located on the CL modules operate
independently of the management subsystems. For instructions on extracting and
inserting a CL module, refer to Removing/Installing the CL Module in Chapter 2.
Power Supply (PS) Modules
PS Modules
Two PS modules can be installed in the chassis. Only one PS module is required to
provide power to a fully equipped Megaplex-4; 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 automatic and does not disturb normal
operation. For instructions on extracting and inserting a power supply, refer to
Removing/Installing the PS Module in Chapter 2.
PS modules for Megaplex-4100 and Megaplex-4104 have different shape and
technical characteristics. -48 VDC nominal DC power supplies are available for
both chassis. In addition, Megaplex-4100 can be ordered with AC (115 or 230
VAC nominal) or 24 VDC nominal power supply modules. For the full list of module
options for the Megaplex-4100 and Megaplex-4104 chassis, see Table 1-8.
Feed and Ring Voltage Sources

External feed voltages are required by the following modules:
• Voice modules installed in AC-fed chassis
• ISDN modules
• SHDSL modules.

The recommended source for external voltages in the case of voice and ISDN
modules is Ringer-2200N offered by RAD. Ringer-2200N is a standalone unit
intended for rack mounting, capable of providing power for up to 120 voice
channels. Refer to the Ringer-2200N Installation and Operation Manual for
connection instructions.
The recommended source for external phantom feed voltages in the case of
SHDSL modules is MPF (Megaplex Power Feed) offered by RAD. standalone unit
intended for rack mounting, MPF provides power for Megaplex SHDSL modules
that require DC voltage to remote DSL repeaters or modems (up to 40 active
SHDSL modems or repeaters operating in 4-wire mode). Refer to the MPF
Installation and Operation Manual for connection instructions.
For additional details, refer to the Ringer-2200N Installation and Operation Manual
and MPF Standalone Power Supply for ASMi-54C/N modules section in the
Megaplex-4 I/O Modules Installation and Operation Manual.
1.4 Functional Description
Megaplex-4 Architecture
Megaplex-4 unique dual star topology architecture (see Figure 1-19) connects the
common logic processing engines to any of the 10 I/O slots independently. In
addition each of the I/O slots is connected by a TDM path, as well as an Ethernet
path, allowing true native TDM and Ethernet traffic handling with minimal
encapsulation delays, no overhead and dual TDM-Ethernet mode modules.
1-32 Functional Description Megaplex-4

STM-n/OC-n
STM-n/OC-n
GbE
GbE
Common Logic
Packet TDM Dual Star

Topology Connection
Engine Engine
Each I/O Module has an

Independent “Traffic Highway”
I/O I/O I/O
Ethernet TDM Ethernet TDM Ethernet TDM

Interface Interface Interface Interface Interface Interface
10/4 x I/O
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Interface
Ethernet
Ethernet
Ethernet
Ethernet
Ethernet
Ethernet
TDM
TDM
TDM
TDM
TDM
TDM
Figure 1-19. Megaplex-4 Internal Architecture
The Megaplex-4 architecture includes the following main subsystems:
• I/O subsystem: provides interfaces to the user’s equipment. For description,
see I/O Modules section below.
• TDM engine:
 DS0 cross-connect matrix: handles the TDM traffic. The matrix also
handles the signaling information associated with TDM traffic.
 DS1 cross-connect matrix: provides direct timing-independent cross-
connect of E1/T1 streams directly to any selected VC-12/VT1.5.
 PDH mapper and framer: handle the TDM traffic directed to the network,
and enable mapping any E1/T1 port to any VC-12/VT1.5, respectively.
• SDH/SONET engine: includes the circuits needed to interface to an
SDH/SONET network:
 Low-order/high-order (LO/HO) cross-connect matrix: controls the routing
of VCs/VTs at all the levels among the PDH mapper, and the SDH/SONET
links. Also provides automatic protection switching (APS) for the network
links, and path protection.
 SDH/SONET interfaces: provide the physical interfaces for the SDH/SONET
links.
• Ethernet (packet) engine: includes the circuits needed to interface to a
packet-switched network. The Ethernet traffic handling subsystem includes:
 Packet processor: controls the forwarding of Ethernet traffic within the
Megaplex-4 (including forwarding from internal ports, Ethernet-over-TDM
and virtually concatenated groups) to external Ethernet ports as well as
Megaplex-4 Functional Description 1-33

carrier Ethernet functionality (traffic-management, OAM&P) and carrier

grade capabilities (G.8032v1 ERPS) when using the CL.2/A assembly
 HO/LO mapper and VCAT engine: handle the Ethernet traffic directed for
transport over the SDH/SONET network by means of virtually
concatenated groups, with optional LCAS support (per ITU-T Rec.
G.7042).
 GbE interfaces: provide the physical interfaces for the packet switched
network links.
• Timing subsystem: provides timing signals to all the Megaplex-4 circuits, and
external (station) clock interfaces. For redundancy, two independent
subsystems, each located in a CL module, are used. For more information,
see Clock Selection in Chapter 5.
• Management subsystem: controls Megaplex-4 operation, stores its software
and configuration, and provides interfaces for local and remote management,
and for alarm reporting. The management subsystem is also redundant: two
independent subsystems, each located in a CL module, are used. For more
information, see Management Access Methods in Chapter 4, Management
Bridge and Management Router in Chapter 8, as well as Chapter 12, Software
Upgrade.
• Power supply subsystem: includes power supply modules that provide power
to the internal circuits, and an interface for external line feed. For
redundancy, two power supply modules can be installed in the chassis. For
more information, see Power Supply (PS) Modules in this chapter and
Installing PS Modules in Chapter 2.
Figure 1-20 illustrates the position and the contents of the TDM, SDH/SONET and
Packet engines in the Megaplex-4 Data Flow Block Diagram.

GbE Ports SDH/SONET Ports
SDH/SONET
SDH/SONET
Engine
HO/LO Framers and
and VCAT HO/LO VC/VT
Mapper Cross-Connect
Matrix
Packet Engine Packet VCAT E1/T1

Processor Engine Mapper
DS1
TDM Engine
Cross-Connect
Matrix
E1/T1
Framer
DS0
Cross-Connect
Matrix
ETH DS0 DS1
Figure 1-20. Data Flow Block Diagram
TDM Engine
TDM traffic can be switched between any of the following entities on the specific
level:
• DS0 (analog and digital interfaces: voice, serial, framed E1/T1, E1 over DSL,
E1/T1 over PW or multiplexed fiber, E1/T1 coming from VC-12/VT1.5)
• DS1 (unframed E1/T1 coming from M16E1/M16T1, Optimux modules or
ASMi-54C/N): transparent and clock independent DS1 processing towards
SONET/SDH or other I/O ports
• SDH/SONET (high and low level cross connect between SDH/SONET ports).
The cross-connect level can be selected to DS1 or DS0 operation mode per port.
DS0 Cross-Connect Matrix

The DS0 cross-connect matrix located on CL modules provides fully non-blocking
1/0 cross-connect among I/O modules and PDH ports of the CL.2 modules. This
matrix operates in coordination with the cross-connect matrices located on most
types of I/O modules.
The DS0 cross-connect matrix provides full control over the routing of individual
timeslots. This is needed for handling the payload of E1 ports with G.704
framing, T1 ports with SF or ESF framing, and for the inband management
timeslot. The traffic associated with sub-E1 ports (such as ISDN, voice or serial

interfaces} is always handled in the DS0 mode. Accordingly, Megaplex-4

distinguishes among three main types of payload per timeslot:
• Voice: timeslots carrying PCM-encoded payload.
Channel-associated signaling (CAS) information is always associated with
voice timeslots, and therefore it must also be converted when
cross-connecting timeslots from ports using different standards.
• Data: data timeslots are transparently transferred from port to port. In
general, it is assumed that no CAS is associated with data timeslots.
• Management: one timeslot can be assigned in any E1 or T1 port to carry
inband management traffic to the end 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). For more information, see the Unidirectional
Broadcast Function section under Cross-Connections in Chapter 5.
The following diagram and table illustrate the DS0 matrix capacity.
For the regular CL.2 modules (with SDH/SONET and GbE ports), the maximum
capacity on the I/O side is achieved with the following module combination:
• Megaplex-4100: 8 M16E1/M16T1 modules + 2 M8E1/M8T1 modules
• Megaplex-4104: 4 M16E1/M16T1 modules.
For the CL.2 modules without SDH/SONET and GbE ports (DS0 only option), the
maximum capacity on the I/O side is achieved with 10 M16E1/M16T1 modules for
Megaplex-4100 and 4 M16E1/M16T1 modules for Megaplex-4104.
Table 1-3. Maximum DS0 Matrix Capacity
Modules SDH SONET
SDH/SONET 2 CL.2 modules 4032 (2 x 63 × 32) DS0 4032 (2 x 84 × 24) DS0

(Network) side
I/O (Tributary) side 8 M16E1/M16T1 modules 3840 (120* × 32) DS0 2880 (120* × 24) DS0
MP-4100
2 M8E1/M8T1 modules 512 (2 x 8 × 32) DS0 384 (2 x 8 × 24) DS0
I/O (Tributary) side 4 M16E1/M16T1 modules 2048 (64 × 32) DS0 1536 (64 × 24) DS0
MP-4104
Total MP-4100 8384 DS0 7296 DS0
Total MP-4104 6080 DS0 5568 DS0
*8 x 16 =128 – the closest number to the 120 E1/T1 restriction.

The resulting I/O + CL.2 capacity is up to 8384 DS0 for SDH and 7296 DS0 for
SONET.

Table 1-4. Maximum DS0 Matrix Capacity (DS0 only option)
Modules E1 T1
SDH/SONET 2 CL.2 modules - -

(Network) side
MP-4100
MP-4104
Total MP-4100 5120 DS0 3840 DS0
Total MP-4104 2048 DS0 1536 DS0
DS1 Cross-Connect Matrix

The DS1 cross-connect matrix provides direct timing-independent cross-connect
of E1/T1 streams directly to any selected VC-12/VT1.5. The E1/T1 traffic from
selected modules (M16E1/M16T1, ASMi-54C/N, Optimux) can be mapped directly
to SONET/SDH without passing the DS0 matrix, thus maintaining independent
timing of the E1/T1 links.
When using the DS1 cross-connect for Megaplex-4100, up to 160 E1/T1 links can
be added and dropped at each node when connected over STM-4/OC-12. The
DS1 cross-connect matrix has a capacity of 160 × DS1 for the I/O side. On the
CL.2 side, the matrix capacity is 252 × VC-12/VT1.5 per Megaplex-4 node. The
252 x VC/VT is the total budget of cross-connected LO (VC-12/VC-3/VT1.5) and
HO (VC-4/STS-1) containers.
E1/T1 Framers and Mappers

The TDM payload directed to the network is structured by the DS0 cross-connect
matrix and applied to the E1/T1 framers. Each framer behaves as a logical E1/T1
port, with user-selectable framing: each CL.2 module can have up to 63 E1 ports,
or up to 84 T1 ports, in accordance with the SDH/SONET framing mode.
The operation mode of each framer can be configured by the user:
• For SDH network interfaces, E1 ports are supported
• For SONET network interfaces, T1 ports are supported.
The frame type is also selectable, separately for each port:
• For E1 ports, either basic G.704 framing (identified as G732N) or G.704
multiframe (G.732S) can be selected.
• For T1 ports, the selections are SF (D4) and ESF.
Each framer adds the appropriate overhead and creates the frame structure. The
data stream provided by each framer is applied to the E1/T1 mappers:
• For E1 ports, the mapper enables mapping the port data stream to any of the
63/252 VC-12 in the STM-1/STM-4 signal.

• For T1 ports, the mapper enables mapping the port data stream to any of the
84/336 VT1.5 in the OC-3/OC-12 signal.
SDH/SONET Engine
The SDH/SONET engine includes the following parts:
• Network port interfaces
• SDH/SONET framers and high-order (HO – STS-1/VC-4) cross-connect matrix.
The SDH/SONET subsystem is integrated with the Ethernet over SDH/SONET
engine.
SDH/SONET Network Port Interfaces

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

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

• Two Gigabit Ethernet ports located on CL.2 modules

• SDH/SONET ports by using Virtual or Contiguous concatenation (up to 32 VCG
per CL.2) with GFP or LAPS and optional LCAS support.
The Ethernet engine flow classification mechanism is based on port (unaware
mode) or VLAN (aware mode with pop/push or preserve capabilities).
Packet Processor
The GbE packet processor is a high-capacity Ethernet processor with classifier,
capable of handling a wide range of VLAN and port-based flows.
The processor includes GbE and Fast Ethernet ports, which are used as follows:
• Two external GbE ports, one connected to the GbE 1 interface and the other
to the GbE 2 interface. The two ports can be configured to operate as a
redundancy pair, using hardware-based path and link failure for rapid
switching to the backup link.
• Fast Ethernet ports are used for Ethernet traffic from I/O modules, one from
each I/O slot.
• Two GbE ports are internally connected to the Ethernet processor of the
other CL module installed in the Megaplex-4.
• 8 GbE ports on the dedicated M-ETH module, with 1 GbE uplink to the CL.2
modules, supporting VLAN-aware bridging inside the module between all its
ports
• Each Ethernet port is supported by an independent MAC controller that
performs all the functions required by the IEEE 802.3 protocol. The maximum
frame size supported by the basic Ethernet switch is 9600 bytes. For
maximum frame sizes supported by different I/O modules, see Configuring
User Ethernet Ports in Chapter 6.
• The frames passed by the MAC controllers are analyzed by the ingress rate
policy controller of the corresponding port before being transferred, through
the switch fabric, to an internal port controller, which controls the frame
egress priorities and inserts them in separate queues. The switch supports up
to four transmission classes (queues) for the Fast Ethernet ports, and up to 8
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.
Note In the Megaplex equipped with CL.2/A assembly, the queue mapping functionality
associates the user priorities with queue numbers (CoS) and the marking
functionality maps the user priority to the SP priority, according to
p-bit/DSCP/IP precedence. In the Megaplex with regular CL.2 module, queue
mapping is fixed and based on p-bit.
The available number of queues depends on flow classification and flow editing
(for details, see Chapter 8).

• The processor includes a flow classification engine categorizing packets into

flows in accordance with user-defined classification rules. Classification takes
place at full wire speed. The processor recognizes standard frame types.
In addition to the Ethernet traffic handling subsystem components located on
the CL.2 modules, I/O modules with Ethernet ports (M-ETH, M8E1, M8T1,
M8SL, OP-34C, OP-108C, ASMi-54C, ASMi-54C/N, MPW-1, VS) also include a
local Ethernet handling subsystem. This subsystem includes:
 Ethernet port interfaces: provide 10/100/1000 Mbps physical interfaces
for external Ethernet links.
 Layer 2 Ethernet switch: provides the local Ethernet VLAN classification.
 GbE (M-ETH) or Fast Ethernet data ports
 Ethernet termination and processing: provides the interface between the
Layer 2 Ethernet switch and the I/O module specific technology interface.
 For M8E1, M8T1, and M8SL modules, this function terminates
Ethernet frames in the direction from the switch to the local
cross-connect matrix and processes them for transmission through
the appropriate bundles, that is, over TDM media. In the inverse
direction, the payload received from TDM media is packetized and
inserted in Ethernet frames for transmission to the appropriate
Ethernet port
 For MPW-1 and VS modules, this function provides the interfaces for
pseudowire packet traffic
 For the Optimux modules, this function terminates Ethernet frames
over the fiber-optic TDM interface
 For the ASMi-54C/N and ASMi-54C modules, this function terminates
the Ethernet frames over SHDSL.
Note The Ethernet termination and processing function can also serve Ethernet traffic
carried through E1-i/T1-i ports of CL.2 modules.
For a detailed description of I/O module Ethernet traffic handling subsystem,

refer to the Megaplex-4 I/O Modules Installation and Operation Manual.
Carrier Ethernet (CL.2/A Assembly)

In addition to the basic functionality described above, the CL.2/A assembly
provides carrier Ethernet capabilities, such as Ethernet traffic management (TM),
standards-based Ethernet Operations, Administration and Maintenance and
Performance Monitoring (OAM&P), as well as carrier grade Ethernet functionality.
These functionalities are available on any MAC entity, such as the CL module GbE
ports, VCG, Ethernet module (M-ETH)_ports, etc.
Figure 1-21 and Figure 1-22 show the data flow in the device equipped with
CL.2/A for the CL.2 GbE ports and other ports supporting hierarchical scheduling,
respectively. Table 1-5 provides an overview of the traffic handling stages.

Figure 1-21. Data Flow in the Megaplex equipped with CL.2/A – CL.2 GbE ports
Figure 1-22. Data Flow in the Megaplex equipped with CL.2/A – other MAC Ports
Table 1-5. Traffic Handling Stages
Processing Stage Relevant Profiles Applied to Description
L2CP processing L2CP Port, flow Defines actions for L2CP processing (discard, peer,
tunnel)
Classification Classifier Flow Classifying traffic such as email traffic, content

streaming, large document transmission, etc.
Policing Policer Flow Policing the traffic within the flow (CIR, CBS, EIR and

Processing Stage Relevant Profiles Applied to Description

EBS parameters)
Mapping of flow CoS mapping Flow Dividing the services using a 3-bit field, specifying a
to queue priority value between 0 (signifying best-effort) and
7 (signifying highest priority)
Defines method and values for mapping packet
attributes (P-bit, DSCP, IP-Precedence) to internal
CoS Values
Scheduling ‘Storing’ data that is transmitted according to the

(between CoS) CoS level specified
Scheduling and ‘regulating’ traffic
WRED Queue Defines green and yellow packet thresholds and

drop probabilities
Queue Queue block Defines queue type with shaper and WRED profile
Queue block Queue block Defines queue block parameters (queues, scheduling
within scheme, weights)
queue group
Queue group Port Defines level-1, -2 and -3 scheduling elements and

structures within queue group
Shaping Shaper Queue, Ensuring that traffic is shaped to the desired rate
queue block (CIR, CBS Parameter)
Scheduling ‘Storing’ data that is transmitted according to the

(between EvC) CoS level specified
(GbE ports only) Scheduling and ‘regulating’ traffic
WRED Queue Defines green and yellow packet thresholds and

drop probabilities
Queue Queue block Defines queue type with shaper and WRED profile
Queue block Queue block Defines queue block parameters (queues, scheduling
within scheme, weights)
queue group
Queue group Port Defines level-1, -2 and -3 scheduling elements and

structures within queue group
Editing and Marking Flow Adding or removing VLAN IDs, as well as marking the
Marking priority on the outer VLAN header (defines method
of mapping CoS and packet color values into P-bit)
VCAT Engine
The VCAT Engine handles all the functions related to the use of virtual
concatenation, and the preparation of Ethernet traffic for efficient transport over
the SDH/SONET network.
The Ethernet mapper subsystem includes the following functions:

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

General Concept
To describe and map the Ethernet traffic passing over different media (E1/T1,
SDH/SONET, T3 etc), the Megaplex-4 architecture uses a concept of Logical MAC
ports. Logical MAC represents the Ethernet part of the entity. It should be bound
to a gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical
layer.
The meaning of the gfp, hdlc or mlppp ports and their further mapping depends
on the Ethernet traffic media:
• GFP ports exist on CL.2, VS-16E1T1-EoP and T3 modules and represent VCGs
(Virtual Concatenation Groups) with GFP encapsulation. They can be mapped
either directly to the physical layer or to VCG. In the latter case the binding is
done in two stages and this VCG should be further bound to the physical
layer.
• HDLC ports exist in two flavors:
 HDLC ports defined on CL.2 modules represent VCGs (Virtual
Concatenation Groups) with LAPS encapsulation. They can be mapped
either directly to the physical layer or to another VCG. In the latter case
the binding is done in two stages and this VCG should be further bound
to the physical layer
 HDLC ports defined on M8E1, M8T1 and M8SL modules represent HDLC
bundles which can be bound to the physical layer representing E1/T1
ports or specific timeslots.
• MLPPP ports exist only on M8E1 and M8SL modules and are mapped to the
PPP port. The binding is done in two stages and this PPP port should be
further bound to the physical layer.

Ethernet over E1/T1

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

links to provide increased bandwidth. Each PPP port binds an E1 port. The MLPPP
bundle can be defined only on unframed ports, and its maximum bandwidth is a
multiple of 2048kbps.
The binding of HDLC/MLPPP to flow is done by the intermediate Logical MAC
entity.
Ethernet over SDH/SONET

To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
1. At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
2. The resulting streams are mapped to the desired VCs/SPEs, also configured by
management. The Path Overhead (POH) byte carried by all the group
members is used to transfer to the far endpoint the information needed to
identify:
 The relative time difference between arriving members of the virtual
group.
 The sequence number of each arriving member.
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.
over SDH/SONET functionality. Ethernet is mapped to SDH/SONET in the following
steps.
1. Bind VC/VT/STS containers to GFP or HDLC ports. This can be done in two
ways:
 Directly 1:1 without using virtual concatenation ( no VCAT)
 Using virtual concatenation (VCAT). In this case VC/VT/STS should be first
bound n:1 to a VCG port and then this VCG should be bound to a GFP/
HDLC port.

2. Bind a GFP/HDLC port to a Logical MAC port (1 to 32).

3. Create ingress/egress flows.
Note The maximum total number of GFP and HDLC ports per CL.2 is 32.
Flow
Egress/Ingress Port
Logical MAC Logical MAC

ETH Group 1 32
OR
Bind 1:1
GFP 1..32 HDLC 1..32
OR
Bind 1:1
VCG
Bind 1:1
1..32
Bind 1:n
VCAT No
VC4-4C/
VC4/STS-3C VC3/STS-1 VC12/VT1.5
STS-12C
Figure 1-24. Logical Entities Representing Ethernet Traffic over SDH/SONET Media
Ethernet over Full/Channelized T3

T3 modules allow encapsulating Ethernet traffic with the GFP protocol and
transferring it over full or channelized T3 media. In both cases Ethernet ports are
connected to Logical MAC ports via flows, and these Logical MAC ports are bound
to GFP ports. Starting from the GFP ports, two ways are available:
• To transfer Ethernet over full T3, only one GFP/Logical MAC port is created
and T3 port is bound directly to it.
• To transfer Ethernet over channelized T3, up to 16 Logical MAC, GFP and VCG
ports are created, so that the VCG ports are bound to GFP ports and VCG
ports are bound to Logical MAC ports. Up to 16 T1 ports can be bound to
each VCG port, but the total T1 number is limited by 28 T1 ports per T3
module. On the remaining T1s, regular TDM traffic can be mapped.

over T3/T1 functionality.
Flow
Egress/Ingress Port

ETH Group 1 16
Bind 1:1 Bind 1:1
GFP 1 GFP 16
OR
Bind 1:1
VCG 1..16
Bind 1:1
Bind 1:n
T1 T3
Figure 1-25. Logical Entities Representing Ethernet Traffic over Full/Channelized T3 Media
I/O Modules
The figure below illustrates Architectural Entities involved in the Megaplex-4 I/O
modules. Each entity is described in detail in Chapter 6 under the section for
corresponding type of ports: E1, T1, Ethernet, Serial, Logical Mac, Teleprotection
etc.
For possible values and hierarchy of the entities, see also Table 1-6.

FE 8 x E1/T1 FE 8 x E1/T1 FE 8 x E1 8 x E1/T1 8 x E1/T1 8 x E1/T1 8 x E1/T1 8 x E1/T1
Switch DS1 DS0 DS0 DS0 DS0 DS0

Mux L. HDLC L. HDLC
Switch DS0 Switch DS0
MAC 1..32 MAC 1..32
DS1 Voice Serial

PW (32) B1,B2,BRI (D) BRI
1..8 MLPPP PPP MLPPP PPP E1-i 1,2,3,4.1..1 Bundle
1.0,1..4.0,1 1.2..4.2
1 1..8 1 1..8 1..8 ,2,3,4..4 1..2
FE FE
Voice
ETH ETH E1/T1 ETH SHDSL Serial Voice Serial Serial
1..4/8/16
1..3 1..3 1..8 1..3 1..8 1..4/6/12 1..4 1..12 1..4
1..6
HS-6N/HS-12N VC-4/8/16,
MPW-1 M8E1/M8T1 M8SL VC-4/OMNI LS-6N/LS-12 HSU-6,12/HS-S
HS-703 VC-6/LB
16 x E1/T1 16 x E1 FE 16 x E1 FE FE 16 x E1 FE GbE
DS1 DS1 DS1 DS1

Switch Switch Switch Switch Switch
Mux Mux Mux Mux
E1 1.1..1.4 Ethernet E1-i PCS PCS E1 ETH

3.1..3.4 1.1,3.1 1..8 1..8 1..8 1.1..1.16 1.1
E1/T1 mux_eth_tdm Fast- E1 ETH SHDSL SHDSL ETH mux_eth_tdm

E1 1..8 ETH 1 ETH 1..8
1..16 1,3 Ethernet 1,2 1..8 1,2 1..8 1..8 1,2 1
M16E1/M16T1 OP-108C ASMi-54C/E1/ETH/N ASMi-54C OP-34C M-ETH
16 x E1 GbE 13 x E1/T1 GbE
tdm-bridge 4 x E1/T1 12 x E1/T1 tdm-bridge 6 x E1/T1 12 x E1/T1

DS0 DS1 Switch DS0 DS1 Switch
1..4 1...12 1..6 1...12
12 x E1/T1
6 x E1/T1 64 kdps
12 x E1/T1 Bind 12 x E1/T1
64 kdps
12 x E1/T1 serial
Bind 12 x E1 PW cmd-channel 1 cmd-channel 2 PW
1...24 1..6 1...24
Serial cmd-in/out cmd-in/out ETH 1

ETH 1..2
1..12 1.1..1.4 2.1..2.4
VS-12 VS-6/BIN
13 x E1 GbE 29 x E1 GbE
8 x E1 DS1 tdm-bridge 6 x E1 12 x E1 DS1

DS0 Switch DS0 Switch
1...8 1..6 1...12
8 x E1 12 x E1/T1
1 x E1 4 x E1 Bind 1 x E1 4 x E1
PW 6 x E1 PW
1...16 1...24
Voice 1...8 Voice 9..12 serial Voice 1...8 Voice 1...4 ETH 1
(FXS) (E&M) 1..6 (FXS) (E&M)
FXS/E&M
VS-6/FXS, VS-6/FXO, VS-6/E&M
GbE GbE
24 x E1 26 x E1/T1 GbE
FE
Switch ETH 1..4
Switch
DS0/1 GbE FE
tdm-bridge 6 x E1/T1 12 x E1/T1 DS1 INT-ETH 1 INT-ETH 2

L. MAC 1..16 DS0 Switch
1..6 1..12
T1 1:1
1:1..16 12 x E1/T1 12 x E1/T1 Open
1/ 1..28 Bind 6 x E1/T1
GFP 1..16 2 x E1/T1 V-Switch
X.86
1:1 1:1 GbE
Serial C37.94
T3 VCG 1..16 PW 1..24 ETH 1 Control GbE USB
1..6 1..2
T3 VS-6/C37 D-NFV
GbE 16 x E1
GbE 16 x E1 GbE
FE
4 x E1 ds1 4 x E1 Switch Switch PW 1..32

DS0 PW 1..24 Switch
1..4 Switch
PCS 1..16 DS1 1..16

cmd-channel cmd-channel cmd-channel cmd-channel cmd-channel cmd-channel
#1 #2 #3 #4 #5 #6
E1-i 1..16 PCS 1..16 PCS 1..16
OR
East West Automation
cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i cmd-out-i SHDSL E1-i 1..16
#1 #4 #1 #4 #1 #4 #1 #4 #1 #4 #1 #4 1..16
SHDSL1..16
Trip Cross-connect
SHDSL1..16
cmd-out cmd-out 1:n cmd-out-i cmd-out-i cmd-out-i cmd-out-i
#5 #8 #1 #4 #1 #4
Secondary Primary
Trip In
Trip Out Trip Out
RTU
SH-16 SH-16/E1 SH-16/E1/PW
TP
32 x E1 GbE 32 x E1 GbE 32 x E1 GbE
Switch
DS0 DS0 Switch DS0 Switch
Data Data + L. MAC 1..16 6 x E1 16 x E1 6 x E1 16 x E1

only Signaling
1:1 DS1 16 x E1 DS1 16 x E1
E1/T1 PW 1..64 ETH 1 PW 1..64 ETH 1
1..16 1..16
GFP 1..16
1..16
1:1 Serial Serial

1..6 1..6
E1-i/T1-i E1/T1 E1/T1
VCG 1..16
1..16 1..8 1..8
VS-16E1T1-EoP VS-6/E1T1 VS-16E1T1-PW
Figure 1-26. I/O Modules and their Architectural Entities

Megaplex-4 Architecture Entities

Table 1-6 lists the possible values and hierarchy of different Megaplex-4
architecture entities.
Table 1-6. Megaplex-4 Architecture Entities and their Hierarchy
Modules Port Type Hierarchy Possible Values
CL.2 sdh-sonet slot: port slot/1..2
aug slot: au4 speed 155: slot/1

speed 622: slot/1..4
vc-12 slot:port:au4:tug3:tug2: slot/port/au4/tug3/tug2/

tributary 1..63
(port = sdh-sonet)
(tributary = vc12)
vc3-sts1 slot:port:au4:tug3 slot/port/au4/tug3/1..3
vt1.5 slot:port:au4:tug3:tug2: slot/port/au4/tug3/tug2/

tributary 1..84
(port = sdh-sonet)
(tributary = vt1.5)
oc-3 slot: oc-3 speed 155: slot/1

speed 622: slot/1..4
e1-i slot:port:tributary slot/port/1..63

(tributary = e1-i)
t1-i slot:port:tributary slot/port/1..84

(tributary = t1-i)
hdlc slot:hdlc slot/1..32
gfp slot:gfp slot/1..32
vcg slot:vcg slot/1..32
logical-mac slot: logical-mac slot/1..32
ethernet slot:port slot/1..2
mng- slot:port slot/1

ethernet
station id cl-a; cl-b
ASMi-54C shdsl slot:port slot/1..8
pcs slot:pcs slot/1..8
ASMi-54C/N shdsl slot: port slot/1..8
e1 slot: port slot/1..8

e1-i slot: port slot/1..8
pcs slot: pcs slot/1..8
HSU-6, HSU-12, HS-S serial slot:port slot/1..6, slot/1..12,

slot/1..4
bri slot: port slot/1..6, slot/1..12,

(port=d-channel) slot/1..4
bri slot:port:tributary slot/port/1..2

(port=serial,
tributary = b1,b2)
HS-6N, HS-12, serial slot:port slot/1..6, slot/1..12,

HS-703 slot/1..4
HSF-2 serial slot: port slot/1..2
LS-6N, LS-12N serial slot:port slot/1..6, slot/1..12
serial-bundle slot:port slot/1..2
M-ETH ethernet slot:port slot/1..8
M8E1, M8T1 e1/t1 slot: port slot/1..8
hdlc slot: hdlc slot/1..32
ppp slot: ppp slot/1..8
mlppp slot: mlppp slot/1
ethernet slot: port slot/1..3
M8SL shdsl slot: port slot/1..8
e1-i slot: port slot/1..8
hdlc slot: hdlc slot/1..32
ppp slot: ppp slot/1..8
mlppp slot: mlppp slot/1
M16E1/M16T1 e1/t1 slot: port slot/1..16
OP-108C e1 slot:mux eth tdm:port slot/1/1..1/4, slot/3/1..3/4
mux-eth-tdm slot: port slot/1..2
ethernet slot:mux_eth_tdm:ethernet slot/1/1, slot/3/1

OP-108C/E1 e1 slot: port slot/1..8
mux-eth-tdm slot: port slot/1..2
int-eth slot:port:tributary slot/1/1, slot/3/1

(port = mux_eth_tdm)
(tributary = int-eth)
OP-34C e1 slot:port:tributary slot/1/1..16

(tributary = e1)
mux-eth-tdm slot: port slot/1
ethernet slot:port slot/1
int-eth slot:port:tributary slot/1/1

SH-16 shdsl slot:port slot /1..slot/16
pcs slot:port slot /1..slot/16
SH-16/E1 shdsl slot:port slot /1..slot/16
pcs slot:port slot /1..slot/16
e1-i slot: port slot /1..slot/16
ds1 slot:port slot/1.. slot/16
pw slot:port slot/1.. slot/32
T3 t3 slot:port slot/1
t1 slot:port slot/1/1 .. slot/1/28
logical-mac slot:port slot/1 .. slot/16
gfp slot:port slot/1 .. slot/16
vcg slot:port slot/1 .. slot/16
VC-4/4A/8/8A/16 voice slot:port slot/1..4, slot/1..8,

slot/1..16
VC-6/LB voice slot:port 1..6
VC-4/OMNI voice slot:port 1..4
voice slot:port:tributary slot/1/1..4/4

(port = voice) (tributary =
internal)
TP (Teleprotection) cmd-in slot:port slot/1..4

cmd-in-i slot:port:tributary slot/1/1..1/4

(port = cmd-channel) slot/3/1..3/4
(tributary = internal)
cmd-out slot:port slot/1..4, 5..8
cmd-out-i slot:port:tributary slot/1/1..1/4

(port = cmd-channel) slot/3/1..3/4
cmd-channel slot:port slot/1..4
VS-12 serial slot:port slot/1… slot/12
tdm-bridge slot:port slot/1… slot/4
ethernet slot:port slot/1, slot/2
ds1 slot:port slot/1.. 12
pw slot:port slot/1.. 24
VS-6/BIN serial slot:port slot/1… slot/6
cmd-in slot:port:tributary slot /1/1 …… slot /1/4

(port = cmd-channel) slot /2/1 …… slot /2/4
cmd-out slot:port:tributary slot /1/1 …… slot /1/4

(port = cmd-channel) slot /2/1 …… slot /2/4
cmd-channel slot:port slot /1, slot /2
VS-6/C37 serial slot:port slot/1… slot/6
ds1-opt slot:port slot /1, slot /2
VS-6/FXS serial slot:port slot/1… slot/6
voice slot:port slot/1.. 8

VS-6/FXO serial slot:port slot/1… slot/6
VS-6/E&M serial slot:port slot/1… slot/6
FXS/E&M voice (FXS) slot:port slot/1.. 8
voice (E&M) slot:port slot/9.. 12
VS-16E1T1-EoP e1-i/t1-i slot:port slot/1… slot/16
e1/t1 slot:port slot/1… slot/16
vcg slot:port slot/1… slot/16
gfp slot:port slot/1… slot/16
logical mac slot:port slot/1… slot/16
VS-16E1T1-PW e1/t1 slot:port slot/1… slot/16
VS-6/E1T1 serial slot:port slot/1… slot/6
e1/t1 slot:port slot/1… slot/8

1.5 Technical Specifications

Note For I/O module technical specifications, refer to the corresponding section in the
Megaplex-4 I/O Modules Installation and Operation Manual.
STM-1/STM-4/ Number of Ports • 2 per CL module

OC-3/OC-12 Ports • 4 per chassis
Bit Rate • STM-1/OC-3:155.52 Mbps ± 4.6 ppm

• STM-4/OC-12: 622.08 Mbps ± 4.6 ppm
Compliance • SDH: ITU-T G.957, G.783, G.798

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

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

G.7041, ANSI T1-105.02, framed mode
• LAPS (Links Access Procedure); X.86
• LCAS (Link Capacity Adjustment Scheme):
ITU-T G.7042
Protection • 1+1 unidirectional APS (G.842)

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

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

see the RAD SFP Transceivers data sheet.
1-54 Technical Specifications Megaplex-4

Table 1-7. 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) (max) (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
Table 1-8. SFP Connector Modules for STM-4/OC-12 Interfaces

Type Type
SFP-15 1310 9/125 single Laser LC -28 -8 -15 -8 15 9.3

mode
SFP-16 1550 9/125 single Laser LC -28 -8 -3 +2 80 49.7
mode
GbE Ports Number of Ports • 2 per CL module

• 4 per chassis
External Ports In accordance with order:

• Two GbE ports with SFP modules
• Two GbE ports with copper (RJ-45) interfaces
Maximum Frame Size 9600 bytes (for max. frame sizes supported by
different I/O modules, see Configuring User
Ethernet Ports in Chapter 6)
Protection On the same CL module (link protection) or

between CL modules (link and equipment
protection):
• LAG with or without LACP
• ERPS (G.8032v1)
Copper GbE Ports Interface Type 10/100/1000BASE-T port, full-duplex, with

autonegotiation
Megaplex-4 Technical Specifications 1-55

Connectors (per port) RJ-45, shielded
Optical GbE Ports Interface Type 1000 Mbps full-duplex port
Link Connectors SFP-based in accordance with Table 1-9
Note: For detailed specifications of SFP transceivers,

see the RAD SFP Transceivers data sheet.
Table 1-9. SFP Connector Modules for GbE Interfaces

Type Type
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
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
Connector • CL.2: DB-9

• CL.2/4104: MINI-USB
Ethernet Interface 10/100BaseT with autonegotiation

Management Port
(CONTROL ETH) Connector RJ-45
Timing Clock Sources • Recovered from the STM-4/STM-1/OC-12/OC-

3 interface, including automatic selection
based on SSM (Synchronization Status
Messaging)
• Internal crystal free-running oscillator-based
clock
• Derived from the receive clock of a specified
user port
• Adaptive clock recovered (ACR) from a
pseudowire circuit
• External station clock

Internal Clock Quality CL.2/622GBEA: ST-3E

CL.2/GBEA: ST-4
CL.2 ST-3E:
CL.2/DS0: ST-4
Station Clock Interface Rate:

• 2.048 MHz
• 2.048 Mbps
• 1.544 Mbps
Interface (software-selectable):
• RS-422 squarewave
• ITU-T Rec. G.703, HDB3 coding for 2.048 MHz
and 2.048 Mbps
• ITU-T Rec. G.703, B8ZS coding for 1.544 Mbps
Connector RJ-45
Diagnostics Tests Local and remote loopbacks per link
Alarms Time and date stamped
Performance Statistics Ethernet, SDH/SONET, E1/T1, SHDSL, VCG, PCS,

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

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

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

been detected in Megaplex-4
• On: a minor alarm has been detected in
Megaplex-4
• Off: No active alarms
CL.2 Module

ON LINE (green/yellow) • On (green): CL module is active or software

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

Megaplex-4, but the highest alarm severity is
minor or warning.
• Blinking: a major and/or critical alarm has
SDH/SONET Ports
ON LINE (green/yellow) On (green): the corresponding port is active

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

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

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

ETH frames are received or transmitted
Off: ETH frames are not received and
transmitted
Management Ethernet
Ports
LINK (green) On: the port is connected to an active Ethernet

hub or switch

ACT (yellow) On or Blinking (in accordance with the traffic):

transmitted
Station CLOCK Port
ON (green) On: the station clock port is configured as no

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

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

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

pins
Connector • CL.2: DB-9, female

• CL.2/4104: 9-pin, flat
Power Consumption 27.75 W (per CL, max)
Power Supplies See Table 1-10
Caution
The DC input is primarily designed for negative input voltage (grounded positive
pole). However, the DC input voltage can be floated with respect to Megaplex-4
ground by means of field-selectable jumpers. Internal jumpers can also be set to
match operational requirements that need either the + (positive) or – (negative)
terminal of the power source to be grounded. Contact your nearest RAD Partner
for detailed information.
Table 1-10. Power Supplies
MP-4100 MP-4104
PS/AC PS/DC PS/AC PS/DC
Operating 115 VAC/230 VAC -48 VDC 90 VAC to 260 VAC -48 VDC
Range (85 to 264 (-36 to -56 VDC) (-36 to -56 VDC)
VAC) 24 VDC
(20 to 36 VDC)
Frequency 50/60Hz - 50/60Hz -
HVDC support 100 to 360 VDC - 110 to 300 VDC -

MP-4100 MP-4104
PS/AC PS/DC PS/AC PS/DC
Maximum AC 315W + power supplied for ring and feed 200W + power supplied for ring and feed
input power voltage purposes voltage purposes
Total output 250W + power supplied for ring and feed 160W + power supplied for ring and feed
voltage purposes (drawn directly from voltage purposes (drawn directly from external
external source) source)
Selectable - Yes - Yes

ground reference
or floating
ground
Maximum Power Supply Output Currents
Regulated Output Voltage +3.3V +5V -5V +12V -12V
PS/4100 30A 40A 6.5A 2A 2A
PS/4104 25A 15A 2.4A 2A 0.8A
Megaplex-4100 Number of Module Slots 14-slot chassis

Chassis
Slot Usage • 2 power supply slots
• 2 common logic slots
• 10 identical slots for I/O modules
Megaplex-4104 Number of Module Slots 8-slot chassis

Chassis
Slot Usage • 2 power supply slots (of different shape)
• 2 common logic slots (can also accommodate a
single dual-slot CL.2 module)
• 4 identical slots for I/O modules
Chassis Megaplex-4100 Megaplex-4104

Dimensions
Height 18 cm/7 in (4U) 9 cm/3.5 in (2U)
Width 44 cm/17 in 44 cm/17 in
Depth (without handles) 33 cm/13 in 33 cm/13 in
Weight (fully loaded Weight: 15.3 kg/33.8 lb 7.54 kg/16.6 lb max.
chassis) max.

CL.2 Dimensions CL.2/4100 CL.2/4104

Height 17.3 cm (6.8 in) 17.3 cm (6.8 in)
Width 4.5 cm (1.8 in) 2.5 cm (1 in)
Depth 32.5 cm (12.8 in) 32.5 cm (12.8 in)
Weight 630 g (1.3 lb) 540 g (1.2 lb)
Rack Installation Megaplex-4100 RM-MP-MX-23/19: hardware kit for installing one

Kits Megaplex-4100 in either a 19-inch or 23-inch rack
MP-2100-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)
Megaplex-4104 RM-42: hardware kit for installing one Megaplex-4104

in a 19-inch rack
RM-42-CM: hardware kit for installing one Megaplex-
4104 in a 19-inch rack with cable management
WM-42: wall-mounting kit for installing Megaplex-4104
WM-42-CM: wall-mounting kit for installing Megaplex-
4104 with cable management
Note
Chassis handles installed on the rack mount brackets add 4 cm (1.6 in) to the
total depth.
Environment Operating Temperature -10°C to 55°C (14°F to 131°F)

Note: For extended operating temperature ranges, and
for “no-fans” Megaplex-4104 chassis temperature
ranges, refer to Ambient Requirements section in
Chapter 2. For additional questions, contact your local
RAD Business Partner.
Storage Temperature -20°C to +70°C (-4°F to +160°F)
Humidity Up to 95%, non-condensing
Note
Actual operating temperature range is determined by the specific modules
installed in the chassis.


Chapter 2
Installation
This chapter provides installation instructions for Megaplex-4 devices.
The chapter presents the following information:
• General description of equipment enclosure and its panels.
• Mechanical and electrical installation instructions for the enclosure itself and
for system modules, that is, PS and CL modules.
After installing the system, it is necessary to configure it in accordance with the
specific user's requirements:
• The preliminary system configuration is always performed by means of a
supervision terminal (procedures for using the terminal are given in
Chapter 4). The software necessary for using the terminal is stored in the CL
module: if the CL module is not yet loaded with the required software, refer
to Chapter 12 for detailed software installation instructions.
• After the preliminary configuration, the system can also be managed by
means of Telnet hosts and/or SNMP-based network management stations,
e.g., RADview. Refer to the User's Manual of the network management
station for operating instructions.
2.1 Site Requirements and Prerequisites
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.
Megaplex-4 Site Requirements and Prerequisites 2-1

Chapter 2 Installation Installation and Operation Manual
Megaplex-4 modules contain components sensitive to electrostatic discharge

Cautions (ESD). To prevent ESD damage, always hold the module by its sides, and do not
touch the module components or connectors.
Delicate electronic components are installed on both sides of the printed circuit
boards (PCBs) of the Megaplex-4 modules. To prevent physical damage:
• Always keep modules in their protective packaging until installed in the
Megaplex-4 chassis, and return them to the packaging as soon as they are
removed from the enclosure.
• Do not stack modules one above the other, and do not lay any objects on
PCBs.
When inserting a module into its chassis slot, align it carefully with the chassis
slot guides, and then push it in gently. Make sure the module PCB does not touch
the adjacent module, nor any part of the chassis. If resistance is felt before the
module fully engages the mating backplane connector, retract the module, realign
it with the slot guides and then insert again.
Before connecting this product to a power source, make sure to read the
Warning Handling Energized Products section at the beginning of this manual.
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-4 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-4 and its modules.
Warning • Never connect cables to Megaplex-4 if not properly installed and grounded.
• Disconnect all the cables connected to the electrical connectors of the
Megaplex-4 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-4 grounding terminals are located on the Megaplex-
4 PS module panels.
Whenever Megaplex-4 units are installed in a rack, make sure that the rack is
properly grounded and connected to a reliable, low-resistance grounding system,
because the rack can also provide a connection to ground.
2-2 Site Requirements and Prerequisites Megaplex-4

Installation and Operation Manual Chapter 2 Installation
In addition, the grounding connection is also made through each one of the AC
power cables. Therefore, the AC power cable plug must always be inserted in a
socket outlet provided with a protective ground.
Laser Safety
Megaplex-4 modules may be equipped with a laser diode. In such cases, a label
with the laser class and other warnings as applicable will be attached near the
optical transmitter. The laser warning symbol may also be attached.
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 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-4 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-4 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-4 modules are shipped with protective covers
installed on all the optical connectors. Do not remove these covers until you are
ready to connect optical cables to the connectors. Keep the covers for reuse, to
reinstall the cover over the optical connector as soon as the optical cable is
disconnected.
Protection against ESD

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

Caution Megaplex-4 modules contain components sensitive to electrostatic discharge

(ESD). To prevent ESD damage, always hold a module by its sides, and do not
touch the module components or connectors. If you are not using a wrist strap,
before touching a module, it is recommended to discharge the electrostatic
charge of your body by touching the frame of a grounded equipment unit.
Whenever feasible, during installation works use standard ESD protection wrist
straps to discharge electrostatic charges. It is also recommended to use garments
and packaging made of antistatic materials or materials that have high resistance,
yet are not insulators.
AC Power Requirements
AC-powered Megaplex-4 units should be installed within 1.5m (5 feet) of an
easily-accessible grounded AC outlet capable of furnishing 150/230 VAC (nominal),
50/60 Hz.
DC Power Requirements
DC-powered Megaplex-4 units require a -48 VDC (-36 to -57 VDC) or 24 VDC (18
to 40 VDC, Megaplex-4100 only) power source (in accordance with the nominal
mains voltage of the ordered PS module).
Cautions • Megaplex-4 PS modules have no power switch and start operating as soon as
power is applied. Therefore, an external power ON/OFF switch is required (for
example, the circuit breaker that protects the power line can also serve as an
ON/OFF switch).
• It is not allowed to install DC-powered PS modules operating on different
voltages (i.e., 24 VDC and -48 VDC) in the same Megaplex-4100 chassis.
• Internal jumpers on the DC PS modules can be set to match operational
requirements that need either the + (positive) or – (negative) terminal of the
power source to be grounded. The normal factory setting is for a power
source with the +(positive) terminal grounded (the power supply module
jumpers are installed in the BGND=FGND and GND=FGND positions). When it is
necessary to use a power source with the – (negative) terminal grounded, or a
floating power source, the jumpers must be disconnected (set to NO).
Check the position of jumpers in the Megaplex-4 power supply module (see
Figure 2-5 and Figure 2-6) 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.

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

Allow at least 90 cm (36 inches) of frontal clearance for operator access. Allow
the same clearance at the rear of the unit for interface cable connections and
module replacement.
Ambient Requirements
Megaplex-4100
The Megaplex-4100 I/O modules are cooled by free air convection.
The ambient operating temperature range of Megaplex-4100 is -10 to +55°C (14
to 131°F), at a relative humidity of up to 95%, non-condensing. The storage
temperature is -20°C to +70°C (-4°F to +160°F). Actual operating temperature
range is determined by the specific modules installed in the chassis.
The Megaplex-4100 chassis has no fans and is cooled mainly by free air
convection. Cooling vents are located in the bottom and upper covers. Do not
obstruct these vents. When the chassis is installed in a 19" rack, allow at least 1U
of space below and above the unit.
The PS power supply modules have a miniature cooling fan installed on their front
panels: this fan operates only when the temperature is high.
CL.2 modules also have internal fans.
The Megaplex-4100 chassis ordered with special options of CL and PS system
modules complies with IEEE-1613 standard including “No Fans operation”.
The I/O modules supported in this chassis are as follows:
• M16E1/M16T1, HSF-2 (all flavors)
• M8E1/M8T1, MPW-1, M-ETH, HS-RN, TP, HS-6N/HS-12N (specific flavors).
These modules also require a special ordering option (if needed, please contact
your local RAD Business Partner).
Megaplex-4104
The Megaplex-4104 chassis has 2 cooling fans on its right side. Do not obstruct
these vents. When the chassis is installed in a 19" rack, allow at least 10 cm of
spacing at the sides of the device.

The Megaplex-4104 PS power supply and CL.2 modules do not include fans.
The ambient operating temperature range of Megaplex-4104 is -10 to +55°C (14
to 131°F), at a relative humidity of up to 95%, non-condensing. The storage
temperature is -20°C to +70°C (-4°F to +160°F). Actual operating temperature
range is determined by the specific modules installed in the chassis.
There is a Megaplex-4104 chassis that complies with IEEE-1613 standard
including “No Fans operation”. This chassis option supports a pre-defined
configuration, including card slot assignment (see Table 2-1). If a different
configuration is required, please contact your local RAD Business Partner.
Table 2-1. Operating Temperature Ranges for Megaplex-4104 IEEE-1613

Compliant Configurations
Configuration Operating Temperature

Range
1 CL.A: MP-4104M-CL.2/DS0 -20°C – 55°C

CL.B: MP-4104M-CL.2/DS0
IO-1: HSF-2
IO-2: M16E1
IO-3: HS-RN
IO-4: HS-12
PS-A: MP-4104M-PS/48
PS-B: MP-4104M-PS/48
Make sure to insert a right module to the right slot; double-check the slot labels
in accordance with the diagram below.
PS-B
CL-B I/O 2
CL-B I/O 2 PS-B

RAD
MEGAPLEX-4104
CL-A I/O 3
CL-A I/O 3 PS-A
I/O 1
I/O 1
I/O 4
I/O 4
PS-A
Electromagnetic Compatibility Considerations

The Megaplex-4 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-4 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-4 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, 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
Optical Cable Requirements

The cables connected to Megaplex-4 optical ports should use 2-mm optical fibers
terminated in the corresponding type of connectors. When routing fibers, make
sure to observe the minimum bending radius (35 mm). RAD recommends
installing plastic supports on each cable connector: these supports determine the
fiber bending radius at the connector entry point and also prevent stress at this
point.
2.2 Package Contents
Megaplex-4100 Package Contents

The Megaplex-4100 package (P/N beginning with MP-4100-2) 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-2100-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)
• Multiservice Access Multiplexers Technical documentation CD.
I/O modules are shipped either separately, or preinstalled in the chassis, in
accordance with your order.
Megaplex-4 Package Contents 2-7

Megaplex-4104 Package Contents

The Megaplex-4104 package (P/N beginning with MP-4104-2) includes the
following items:
• Megaplex-4104 chassis, including CL and PS modules in accordance with order
• Power cables in accordance with order, and a DC plug for the DC power cable
• Supervision terminal cable, CBL-MUSB-DB9F
• Open-ended alarm cable, CBL-MP-4104/AR/OPEN/2M
• Rack installation kit in accordance with order:
 RM-42: hardware kit for installing one Megaplex-4104 in a 19-inch rack
(supplied with the device)
 RM-42-CM: hardware kit for installing one Megaplex-4104 in a 19-inch
rack with cable management
 WM-42: wall-mounting kit for installing Megaplex-4104
 WM-42-CM: wall-mounting kit for installing Megaplex-4104 with cable
management
• Multiservice Access Multiplexers Technical Documentation CD.
I/O modules are shipped either separately, or preinstalled in the chassis, in
accordance with your order.
2.3 Required Equipment

The additional cables you may need to connect to the Megaplex-4 device depend
on the Megaplex-4 application.
You can use standard cables or prepare the appropriate cables yourself in
accordance with the information given in Appendix A, and in the Installation and
Operation Manuals of the installed modules.
2.4 Mounting the Products

This section presents instructions for installing Megaplex-4 units. To help you
familiarize with the equipment, it also presents a physical description of the
Megaplex-4 versions.
Do not connect any cables to the Megaplex-4 before it is installed in the

designated position.
Warning
2-8 Mounting the Products Megaplex-4

Installing the Megaplex-4100 Chassis

Megaplex-4100 is intended for installation on shelves and racks. Do not connect
power to the enclosure before it is installed in the designated position.
Installing in a 19” Rack

For rack installation, it is necessary to install two brackets to the sides of the
unit. As illustrated in Figure 2-1, 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-1. Attachment of Brackets to Megaplex-4100 Case for Installing in 19” Rack
Megaplex-4 Mounting the Products 2-9

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-2 shows how to attach the brackets for installation in 23”
racks (only front installation is shown in this figure).
Figure 2-2. 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.
Installing the Megaplex-4104 Chassis

Megaplex-4104 can be installed on shelves, racks and mounted on the wall. Do
not connect power to the enclosure before it is installed in the designated
position.
For rack and wall-mount installation, refer to the leaflets supplied with RM-42,
RM-42-CM, WM-42 and WM-42-CM rack-mount and wall-mount kits.
2-10 Mounting the Products Megaplex-4

2.5 Installing Modules
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-4 enclosure. Always disconnect the input power from the PS
Warning module before removing it from the enclosure. The installation and preparation
High of the module shall be done by a qualified person who is aware of the hazards
Voltage involved.
Megaplex-4100 Module Panels

The following PS versions are offered for Megaplex-4100:
• DC-powered modules, PS/24 and PS/48: 250W modules, operating on 24 VDC
and -48 VDC (nominal), respectively
• AC-powered module, PS/AC: 250W module, operates on 115 VAC or 230 VAC,
50/60Hz (nominal voltage is marked on the module panel) and includes HVDC
support of 100 to 360 VDC.
Typical PS panels are shown in Figure 2-3. PS modules do not include a power
on/off switch and start operating as soon as power is applied. It is recommended
to use an external power on/off switch, for example, the circuit breaker used to
protect the supply line to the Megaplex-4100 may also serve as the on/off
switch.
Megaplex-4 Installing Modules 2-11

AC-Powered Module 24 VDC-Powered Module -48 VDC-Powered Module
Figure 2-3. Typical Megaplex-4100 PS Module Panels

The PS modules connect to an external feed and ring voltage source, e.g., a
Ringer-2200N standalone unit offered by RAD:
• The AC-powered PS versions have a separate connector, designated VDC-IN,
for the external -48 VDC and +72 VDC voltages.
• The connection of the +72 VDC voltage to the DC-powered PS versions is
made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
The PS modules have a miniature cooling fan on the front panel. Make sure to
keep the fan opening free of obstructions.

The following PS versions are offered for Megaplex-4104:
• DC-powered modules, PS/48: 160W modules, operating on -48 VDC (-36 to
-56 VDC)
• AC-powered module, PS/AC: 160W module, operates on 100 VAC to 260 VAC,
50/60Hz (including HVDC support of 110 to 300 VDC)
Typical PS panels are shown in Figure 2-4. PS modules do not include a power
on/off switch and start operating as soon as power is applied. It is recommended
to use an external power on/off switch, for example, the circuit breaker used to
protect the supply line to the Megaplex-4104 may also serve as the on/off
switch.
2-12 Installing Modules Megaplex-4

AC-Powered Module DC-Powered Module
Figure 2-4. Typical Megaplex-4104 PS Module Panels

Ringer-2200N standalone unit offered by RAD:
• The AC-powered PS versions have a separate connector, designated VDC-IN,
for the external -48 VDC and +72 VDC voltages.
• The connection of the +72 VDC voltage to the DC-powered PS versions is
made through the VDC-IN input connector. The DC feed voltage is derived
from the DC input voltage, and therefore has the same voltage and polarity.
Ringer-2200N standalone unit offered by RAD. The connection of the +72 VDC
voltage to the DC-powered PS 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.
Megaplex-4100 Internal Jumpers

The PS modules include two internal jumpers that control the connection of
frame ground to the internal ground lines.
Caution
If the Megaplex-4100 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local RAD Partner for more information.
The jumpers of a typical PS module (PS/DC or PS/AC) are identified in Figure 2-5.

Front Panel
BGND = FGND
48/24 VDC Positive
Line Connected to
YES Frame Ground
48/24 VDC Positive

Line not Connected
NO
to Frame Ground
GND = FGND
Signal Ground
Connected to
YES Frame Ground
Signal Ground
not Connected to
NO
Frame Ground
NO YES NO YES
Figure 2-5. Typical Megaplex-4100 PS Module (Lateral View), Location of Internal Jumpers
• The jumper designated GND=FGND controls the connection between the
internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
• The jumper designated BGND=FGND controls the connection between the
positive (+) line of the external 24/48 VDC voltage and the frame (enclosure)
ground. The module is normally delivered with the jumper set to YES. If
necessary, you can set the jumper to NO to float the external 24/48 VDC
positive line with respect to the frame ground. This is usually necessary when
the DC voltage is used to feed or ring voltages.
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 appropriate sections of Appendix B
describing the modules installed in the chassis for proper setting of their ground-
control jumpers.
Megaplex-4104 Internal Jumpers

Megaplex-4104 PS modules include two sets of internal jumpers that control the
connection of frame ground to the internal ground lines.

Caution If the Megaplex-4104 chassis must be operated with floating ground, it may also
be necessary to disconnect the ground reference on all the installed modules and
check the ground and shield wiring on the cables connected to the chassis. This
may require changing the hardware settings on the installed modules and
appropriate cables.
Special ordering options with preconfigured settings are available. Contact your
local RAD Partner for more information.
The jumpers of a typical PS module (PS/DC) are identified in Figure 2-6.

Front Panel
YES
NO
YES NO
GND = FGND BGND = FGND

Signal Ground 48 VDC Positive Line
Connected to Connected to Frame
YES Frame Ground YES Ground
Signal Ground 48 VDC Positive Line

not Connected to not Connected
NO NO
Frame Ground to Frame Ground
Figure 2-6. Typical Megaplex-4104 PS Module (Top View), Location of Internal Jumpers
• The jumper designated GND=FGND controls the connection between the
internal signal ground and the frame (enclosure) ground. The module is
normally delivered with the jumper set to YES. If necessary, you can set the
jumper to NO to float the signal ground with respect to the frame ground.
• The jumper designated BGND=FGND controls the connection between the
positive (+) line of the external 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 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 appropriate sections of Appendix B
describing 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-4 chassis. Disconnect the cable(s) from the
module before it is removed from the chassis.
Warning
1. Insert the PS module in the PS-A slot, and fasten it with the two screws.
2. Connect the power cable according to the voltages indicated on the panel.
3. If an additional redundant module is used, install it in the PS-B slot.
Note
You can install a redundant module in an operating enclosure without turning the
Megaplex-4 power off. In this case:
• First insert the module in its slot
• Connect its power cable.
Removing a PS Module
1. Disconnect the power cable(s) connected to the module.
2. Release the two module screws
3. Pull the PS module out.
Installing CL Modules
Megaplex-4100 accommodates two dual-slot CL.2 modules. A special compact
single-slot CL.2 module version is available, allowing the use of two CL.2 modules
in the Megaplex-4104 chassis. Megaplex-4104 can also use the regular dual-slot
module (one per chassis).
The modules include the chassis management and timing subsystem, and a
cross-connect matrix for TDM traffic, two SDH/SONET ports (with STM-1/OC-3 or
STM-4/OC-12 interfaces, in accordance with order) and two GbE ports (with SFPs
or with copper interfaces, in accordance with order). The panels for the
STM-1/OC-3 or STM-4/OC-12 versions are identical. A special version without
SDH/SONET and GbE ports can be used for DS0 cross-connect services only.

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.
Figure 2-7 shows CL.2 module panels and Figure 2-8 – CL.2/A module panels.
Table 2-2 describes the functions of the panel switches. For description of LED
indicators, see Chapter 3.

CL.2 CL.2 CL.2
LASER LASER
CLASS CLASS
1 1
ON LINE ALM ON LINE ALM ON LINE ALM

LOS LOS
S S
D D
H 1 H 1
/ /
S S
O O
N N
E 2 E 2
T ON T ON
LINE LINE
ACT
ACT
1 1
G G
b b
E E
2 2
C LINK C C
O O LINK O
N D N D N D
T C ACT T C ACT T C ACT
R E E R E E R E E
O T O T O T
L LINK H L LINK H L LINK H
C C C
L L L
O O O
A C A C A C
L K L K L K
A A A
R ON/LOS R ON/LOS R ON/LOS
M M M
CL.2 with Copper CL.2 with Optical CL.2 for DS0 Cross-
GbE Interfaces GbE Interfaces connect only
Figure 2-7. CL.2 Module Panels

CL.2 CL.2 CL.2 CL.2

A A A A
LASER LASER
CLASS CLASS
1 1
ON LINE ALM ON LINE ALM ON LINE ALM ON LINE ALM

LOS LOS
S S
D D
H 1 H 1
/ /
S S
O O
N N
E 2 E 2
T ON T ON
LINE LINE
ACT ACT
ACT ACT
1 1 1 1
G G G G
b b b b
E E E E
2 2 2 2
C LINK C C LINK C
O O LINK O O LINK
N D N D N D N D
T C ACT T C ACT T C ACT T C ACT
R E E R E E R E E R E E
O T O T O T O T
L LINK H L LINK H L LINK H L LINK H
C C C C
L L L L
O O O O
A C A C A C A C
L K L K L K L K
A A A A
R ON/LOS R ON/LOS R ON/LOS R ON/LOS
M M M M
CL.2/A with Copper CL.2/A with Optical CL.2/A (GbE only) with CL.2/A (GbE only) with
GbE Interfaces GbE Interfaces Copper GbE Interfaces Optical GbE Interfaces
Figure 2-8. CL.2/A Module Panels
Table 2-2. Module CL.2 for Megaplex-4100, Panel Components
Item Function
CLOCK Connector RJ-45 connector for the station clock input and output signals
CONTROL ETH Connector RJ-45 connector for the 10/100BaseT Ethernet management port
CONTROL DCE Connector 9-pin D-type female connector with RS-232 DCE interface, for connection to
system management. Connector pin allocation is given in Appendix A
ALARM Connector 9-pin D-type female connector, for connection to the Megaplex-4100 alarm
relay outputs, and an external alarm input. Connector pin allocation is given in
Appendix A
SDH/SONET 1, 2 Connectors Sockets for installing SFP transceivers for the corresponding SDH/SONET ports
GbE 1, 2 Connectors Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors


A special compact single-slot CL.2 module allows the use of two CL.2 modules in
the Megaplex-4104 chassis. At any time, only one module is active, and the other
serves as hot standby.
Megaplex-4104 can also use the regular dual-slot module (one per chassis).
Figure 2-9 shows CL.2/4104 module panels and Figure 2-10 – CL.2/A/4104
module panels. Table 2-3 describes the functions of the panel switches. For
description of LED indicators, see Chapter 3.
CL.2 CL.2 CL.2
LASER LASER
CLASS CLASS
1 1
ON LINE ALM ON LINE ALM ON LINE ALM

LOS LOS
S S
D D
H 1 H 1
/ /
S S
O O
N N
E 2 E 2
T ON T ON
LINE LINE
ACT
ACT
1 1
G G
b b
E E
2 2
LINK
LINK
ACT ACT ACT
C C C
O E O E O E
N T N T N T
T H T H T H
R R R
O LINK O LINK O LINK
L L L
D C D C D C
C L C L C L
E O E O E O
A C A C A C
L K L K L K
A A A
R ON/LOS R ON/LOS R ON/LOS
M M M
CL.2 with Copper CL.2 with Optical CL.2 for DS0 Cross-
GbE Interfaces GbE Interfaces connect only
Figure 2-9. CL.2/4104 Module Panels

CL.2 CL.2 CL.2 CL.2

A A A A
LASER LASER
CLASS CLASS
1 1
ON LINE ALM ON LINE ALM ON LINE ALM ON LINE ALM

LOS LOS
S S
D D
H 1 H 1
/ /
S S
O O
N N
E 2 E 2
T ON T ON
LINE LINE
ACT ACT
ACT ACT
1 1 1 1
G G G G
b b b b
E E E E
CL.2
A
2 2 2 2
LINK LINK
LINK LINK
ACT ACT ACT ACT
C C C C
O E O E O E O E
N T N T N T N T
T H T H T H T H
R R R R
O LINK O LINK O LINK O LINK
L L L L
D D D C D
C C C
C C C L C
L L L
E E E O E
O O O
A C A C A C A C
L K L K L K L K
A A A A
R ON/LOS R ON/LOS R ON/LOS R ON/LOS
M M M M
CL.2/A with Copper CL.2/A with Optical CL.2/A (GbE only) with CL.2/A (GbE only) with
GbE Interfaces GbE Interfaces Copper GbE Interfaces Optical GbE Interfaces
Figure 2-10. CL.2/A/4104 Module Panels
Table 2-3. Module CL.2 for Megaplex-4104, Panel Components
Item Function
CLOCK Connector RJ-45 connector for the station clock input and output signals
CONTROL ETH Connector RJ-45 connector for the 10/100BaseT Ethernet management port
CONTROL DCE Connector MINI-USB connector, for connection to system management. Connector pin
allocation is given in Appendix A
ALARM Connector 9-pin flat connector, for connection to the Megaplex-4104 alarm relay outputs,
and an external alarm input. Connector pin allocation is given in Appendix A
SDH/SONET 1, 2 Connectors Sockets for installing SFP transceivers for the corresponding SDH/SONET ports
GbE 1, 2 Connectors Sockets for installing SFP transceivers for the corresponding GbE ports,
or RJ-45 connectors
Installing and Replacing SFPs

Before installing a CLyou may have to install the prescribed types of SFPs ,module .

Installing an SFP
When installing an optical SFP in an operating module, be aware that it may

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

local laser safety regulations for Class 1 laser equipment.
Warning
 To install the SFP module:

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

2. Carefully remove the dust covers from the corresponding SFP socket of the CL
module, and from the SFP electrical connector.
3. Orient the SFP as shown in Figure 2-11, and then insert the rear end of the
SFP into the module socket.
4. Push SFP slowly backwards to mate the connectors, until the SFP clicks into
place. If you feel resistance before the connectors are fully mated, retract the
SFP using the wire latch as a pulling handle, and then repeat the procedure.
5. If necessary, repeat the procedure for the other SFP.

Caution Insert the SFP gently. Using force can damage the connecting pins.
6. Remove the protective rubber caps from the SFP modules.

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

• Connect the expansion cable between the EX LINK connectors of the two
modules.

Removing a CL Module
 To remove a CL module:
1. Fully release the two screws fastening the module to the chassis.
2. Simultaneously push the extractor handles outward, to disengage the rear
connector.
3. Pull the module out.
Replacing a CL Module during Equipment Operation –

Megaplex-4 Chassis with two CL Modules
In a Megaplex-4 equipped with two functional CL modules, the standby module
can be removed/replaced with minimal disruption of Megaplex-4 services: when
you replace the on-line CL module, Megaplex-4 will automatically switch to the
standby module, provided that module is operational.
The expected disruptions can be minimized in the following ways:
• An active CL module also provides routing services and clock signals to other
Megaplex-4 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-4
chassis. It is therefore important to prevent this type of disruption, and this
can be achieved by first switching (flipping) to the standby CL module before
replacing the on-line CL module.
• Removing a module always disconnects the traffic carried by the active
payload interfaces (GbE and/or SDH/SONET) located on the replaced module.
Note that these traffic interfaces can be active even on the standby CL
module, and therefore the only way to avoid traffic disconnections is to use
automatic protection for these interfaces: for example, APS can be used to
protect SDH/SONET traffic, and LAG protection can be used to protect
Ethernet traffic.
You can identify the active and standby modules by their ON LINE indicators.
Caution
To prevent service disruption, check that the ON LINE indicator of the CL module
you want to remove is flashing. If not, use the supervisory terminal (or any other
management facility) to reset the module to be replaced, and wait for execution
of this command before continuing: this will cause the Megaplex-4 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. At the mp4100>admin# prompt, type reboot active to send a reset command
to the module to be replaced.

4. Wait for the flipping to be executed. After it is executed, the ON LINE

indicator of the CL module the supervision terminal is connected to starts
flashing, while that of the other module stops flashing and lights steadily.
5. You can now disconnect the supervision terminal, and remove the module.
6. When installing a CL module in the slot of the removed module, you may
cause flipping to the original module by resetting the current on-line CL
module.
Replacing a CL Module during Equipment Operation –

Megaplex-4 Chassis with Single CL Module
In a Megaplex-4 equipped with a single CL module, before replacing the CL
module it is recommended that a functional CL module of the same type be
installed in the free CL slot. The replacement can be temporary.
After inserting the additional CL module, it is necessary to let it update its
database from the information provided by the existing CL module:
1. If necessary, program the additional module in the Megaplex-4 database.
2. Enter commit to update the databases, and then wait until the CL DB
CHECKSUM IS DIFFERENT alarm is off.
3. At this stage, continue in accordance with the steps listed above for a
Megaplex-4 with two CL modules.
If the only CL module in the chassis is replaced, Megaplex-4 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.
Adding a Protection CL Module to a Working Module

Configured as SONET
When the working CL module is configured as SONET, inserting a new CL module
for protection requires the following configuration steps:
1. Retrieve the “startup-config” file.
2. Add the protection CL to the retrieved “startup-config” script (if the working
module is CL-A, add the following string: “configure slot cl-b card-type
cl2-622gbe…” etc.)
3. Copy the new script to the database.
4. Save the changes.
5. Insert the module into the chassis.
6. Reboot the device.

Installing System Modules in Megaplex-4104 Chassis

Refer to the above sections for MP-4100. The only difference is that the power
supply has a different shape.
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.
This precaution is particularly important when installing modules into the two
lower I/O slots (1 and 4) of the Megaplex-4104 chassis: take special care to
support the module from below, while pushing it in gently.
Installing I/O Modules

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

Install blank panels in all the chassis slots that are not occupied by modules.
2.6 Connecting to Power
Grounding Megaplex-4
Before connecting any cables and before switching on this instrument, the
protective ground terminals of this instrument must be connected to the
protective ground conductor of the (mains) power cord. The mains plug shall only
Warning
be inserted in a socket outlet provided with a protective ground contact. Any
interruption of the protective (grounding) conductor (inside or outside the
instrument) or disconnecting the protective ground terminal can make this
instrument dangerous. Intentional interruption is prohibited.
Make sure that only fuses of the required rating are used for replacement. Use of
repaired fuses and the short-circuiting of fuse holders is forbidden.
Whenever it is likely that the protection offered by fuses has been impaired, the
instrument must be made inoperative and be secured against any unintended
operation.
Connect a short, thick copper braid between the grounding screw on each PS
module panel and a nearby grounding point.
Megaplex-4 Connecting to Power 2-25

Connecting to Power
Caution Megaplex-4 does not have a power on/off switch and will start operating as soon
as power is applied to at least one of its PS modules. It is recommended to use
an external power on/off switch to control the connection of power to Megaplex-
4. For example, the circuit breaker used to protect the supply line to Megaplex-4
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 Voltages

External feed voltages are required by the following modules:
• Voice modules installed in AC-fed chassis
• ISDN modules
• SHDSL modules.
The recommended source for external voltages in the case of voice and ISDN
modules is Ringer-2200N offered by RAD. Ringer-2200N is a standalone unit
intended for rack mounting, capable of providing power for up to 120 voice
channels. Refer to the Ringer-2200N Installation and Operation Manual for
connection instructions.
The recommended source for external phantom feed voltages in the case of
SHDSL modules is MPF (Megaplex Power Feed) offered by RAD. standalone unit
intended for rack mounting, MPF provides power for Megaplex SHDSL modules
that require DC voltage to remote DSL repeaters or modems (up to 40 active
SHDSL modems or repeaters operating in 4-wire mode). Refer to the MPF
Installation and Operation Manual for connection instructions.
Caution
Turn on the Ringer-2200N/MPF external voltage source, or connect the external
voltages, only after Megaplex-4 is turned on.
Turn off the Ringer-2200N/MPF external voltage source, or disconnect the
external voltages, only before Megaplex-4 is turned off.
2.7 Connecting Megaplex-4 to the Terminal

Two of the four connectors available on CL.2 modules (CONTROL DCE and ALARM)
are different for Megaplex-4100 and Megaplex-4104 CL.2 modules. Be sure to
refer to the correct section below.
2-26 Connecting Megaplex-4 to the Terminal Megaplex-4

Megaplex-4100 CL.2 Module

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

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.
Megaplex-4104 CL.2 Module

The CL.2/4104 supervisory port has a serial RS-232 asynchronous DCE interface
terminated in a mini-USB 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
Ethernet ports of redundant CL modules do not require any special connections:
each one can be connected to a separate Ethernet hub port.
 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 the
CBL-MUSB-DB9F cable supplied by RAD.
Megaplex-4 Connecting Megaplex-4 to the Terminal 2-27

• Connection to modem with 9-pin connector (for communication with remote

supervision terminal): by means of an additional crossed cable connected to
the CBL-MUSB-DB9F cable.
Additional connection options are presented in Appendix A.

1. Connect the mini-USB connector of the CBL-MUSB-DB9F cable available from
RAD to the CONTROL DCE connector.
2. Connect the other connector of the CBL-MUSB-DB9F 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.
2.8 Connecting to a Management Station or Telnet

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

• The link to network management stations using SNMP, and/or Telnet hosts is
made to the RJ-45 connector designated CONTROL ETH.
• You can use any standard cable (straight or crossed) to connect to any type
of Ethernet port (hub or station).
2.9 Connecting to a 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-4 nodal clock signal,
to other equipment.
2-28 Connecting to a Station Clock Megaplex-4

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). 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, 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.
2.10 Connecting to Alarm Equipment

The alarm port is terminated in a 9-pin D-type female (Megaplex-4100 CL
module) or 9-pin flat (Megaplex-4104 CL module) 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.
Megaplex-4 Connecting to Alarm Equipment 2-29

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.
 To connect to the ALARM connector:

The connection to the ALARM connector of Megaplex-4100 is made by means of a
cable provided by the customer, in accordance with the specific requirements of each
site. The alarm cable for Megaplex-4104 is supplied by RAD. 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.
2.11 Connecting to SDH/SONET Equipment
Note SFP transceivers can also be installed in the field by the customer, however RAD
strongly recommends to order modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Connecting Optical Cables to the SDH/SONET Links

The optical fibers intended for connection to equipment installed in a rack should
pass through fiber spoolers, located at the top or bottom of the rack, in
accordance with the site routing arrangements (overhead or under-the-floor
routing). The spoolers must contain enough fiber for routing within the rack up to
the CL optical connectors, and for fiber replacement in case of damage (splicing
repairs).
From the spoolers, the optical fibers should be routed through cable guides
running along the sides of the rack frame to the level of the equipment to which
they connect.
When connecting optical cables, make sure to prevent cable twisting and avoid
sharp bends (unless otherwise specified by the optical cable manufacturer, the
minimum fiber bending radius is 35 mm). Always leave some slack, to prevent
stress. RAD recommends installing plastic supports on each cable connector:
these supports determine the fiber bending radius at the connector entry point
and also prevent stress at this point.
2-30 Connecting to SDH/SONET Equipment Megaplex-4

Caution When calculating optical link budget, always take into account adverse effects of
temperature changes, optical power degradation and so on. To compensate for
the signal loss, leave a 3 dB margin. For example, instead of the maximum
receiver sensitivity of -28 dBm, consider the sensitivity measured at the Rx side
to be -25 dBm. Information about Rx sensitivity of fiber optic interfaces is
available in SFP/XFP Transceivers data sheet .
Caution Make sure all the optical connectors are closed at all times by the appropriate
protective caps, or by the mating cable connector.
Do not remove the protective cap until an optical fiber is connected to the
corresponding connector, and immediately install a protective cap after a cable is
disconnected.
Before installing optical cables, it is recommended to clean thoroughly their

connectors using an approved cleaning kit.
 To connect optical cables to the SDH/SONET links:

1. For each optical interface, refer to the site installation plan and identify the
cables intended for connection to the SFP serving the corresponding
interface.
2. Where two fibers are used, pay attention to TX and RX connections, and
leave enough slack to prevent strain:
 Connect the prescribed transmit fiber (connected to the receive input of
the remote equipment) to the TX connector of the SFP.
 Connect the prescribed receive fiber (connected to the transmit output of
the remote equipment) to the RX connector of the SFP serving the same
interface.
Connecting Coaxial Cables to SDH/SONET Links

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

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

2.12 Connecting I/O Modules to Remote Equipment

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

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

SFP transceivers can also be installed in the field, by the customer, however RAD
strongly recommends ordering modules with preinstalled SFPs, as this enables
performing full functional testing of equipment prior to shipping.
Caution When calculating optical link budget, always take into account adverse effects of
temperature changes, optical power degradation and so on. To compensate for
the signal loss, leave a 3 dB margin. For example, instead of the maximum
receiver sensitivity of -28 dBm, consider the sensitivity measured at the Rx side
to be -25 dBm. Information about Rx sensitivity of fiber optic interfaces is
available in SFP/XFP Transceivers data sheet .
2-32 Connecting to Ethernet Equipment Megaplex-4

Chapter 3
Operation
This chapter:
• Explains power-on and power-off procedures.
• Describes the Megaplex-4 LED indicators and their function.
3.1 Turning On the Unit

When turning Megaplex-4 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-4 operation).
 To monitor Megaplex-4:
1. Configure the terminal for 115.2 kbps, one start bit, eight data bits, no
parity, and one stop bit.
2. Select the full-duplex mode, echo off, and disable any type of flow control.
Make sure to use VT-100 terminal emulation: using a different terminal type
will cause display problems, for example, the cursor will not be located at the
proper location, text may appear jumbled, etc.
 To prepare Megaplex-4 for first-time turn-on:

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

Caution
When an external feed and ring voltage source is connected to the PS modules
installed in Megaplex-4, always turn that source on only after the PS module(s)
have been turned on.
Megaplex-4 Turning On the Unit 3-1

Chapter 3 Operation Installation and Operation Manual
1. Turn the power on.
Note The Megaplex-4 PS modules do not include a power switch. Use an external
power ON/OFF switch, for example, the circuit breaker used to protect the power
lines.
2. Wait for the completion of the power-up initialization process. During this
interval, monitor the power-up indications:
 After a few seconds, Megaplex-4 starts decompressing its software.
 After software decompression is completed, all the indicators turn off for
a few seconds (except for the POWER indicators) as Megaplex-4 performs
its power-up initialization.
You can monitor the decompression and initialization process on the terminal
connected to the Megaplex-4.
3. After the power-up initialization ends, all the POWER indicators must light,
the ON LINE indicator of the active CL module lights in green and that of the
other CL module flashes slowly in green. At this stage, the indicators display
the actual Megaplex-4 status.
3.2 Indicators
The following tables summarize the function of all LED indicators in
Megaplex-4. The normal indications on power-up (provided the corresponding
port is connected) are marked in bold.
CL.2 Front Panel Indicators

Figure 3-1 shows typical dual-slot CL.2 module panels with SDH/SONET and GbE
interfaces (all possible CL.2 panels are described in Chapter 2). Indicators for
single-slot CL.2 modules of Megaplex-4104 are identical. Table 3-1 to Table 3-6
describe the functions of the panel components.
3-2 Indicators Megaplex-4

Installation and Operation Manual Chapter 3 Operation
CL-2 CL-2
LASER LASER
CLASS CLASS
1 1
ON LINE ALM ON LINE ALM

LOS LOS
S S
D D
H 1 H 1
/ /
S S
O O
N N
E 2 E 2
T ON T ON
LINE LINE
ACT
ACT
1 1
G G
b b
E E
2 2
C LINK C
O O LINK
N D N D
T C ACT T C ACT
R E E R E E
O T O T
L LINK H L LINK H
C C
L L
O O
A C A C
L K L K
A A
R ON/LOS R ON/LOS
M M
Copper GbE Interfaces Optical GbE Interfaces
Figure 3-1. CL.2 Module Panels
Table 3-1. CL.2 System LED Indicators
Name LED Color Function
ON LINE Yellow/green • On (green): CL module is active or software

decompression
• Blinking slowly (green): CL module is on
standby
• On (yellow): a test is being performed
(active module only)
Megaplex-4 Indicators 3-3

ALM Red • On: alarms have been detected in the

Megaplex-4, but the highest alarm severity
is minor or warning.
• Blinking: a major and/or critical alarm has
Note 1: On the standby CL module, this
indicator is always off, even while an alarm
condition is present
Note 2: The LED still remains on even when
active alarms are already cleared. It only turns
off once active alarms have been cleared via
clear-alarm-log all-logs command.
Table 3-2. SDH/SONET Link LED Indicators
ON LINE Green/Yellow On (green): the corresponding port is active

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

Note: Any other alarm condition related to
SDH/SONET traffic handled by the port is
indicated only by the CL general alarm (ALM)
indicator
Note
Status indicators for SDH/SONET ports are active only when the corresponding
port is equipped with an SFP and configured as no shutdown.
Table 3-3. Gigabit Ethernet Port LED Indicators
LINK (per port) Green On: the port is connected to an active Ethernet
hub or switch
ACT (per port) Yellow On or Blinking (in accordance with the traffic):
transmitted
3-4 Indicators Megaplex-4

Note GbE Status indicators are active only when the corresponding port is configured
as no shutdown, and for optical ports – when the port is equipped with an SFP
Table 3-4. Management Ethernet Port LED Indicators
LINK (per port) Green On: the port is connected to an active Ethernet hub or
switch
ACT (per port) Yellow On or Blinking (in accordance with the traffic): ETH
frames are received or transmitted
Off: ETH frames are not received and transmitted
Table 3-5. Clock LED Indicators
ON Green On: the station clock port is configured as no shutdown

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

connected)
Front Panel Indicators

The front panels of the Megaplex-4100 and Megaplex-4104 chassis include
additional system status indicators. The figures below identify the front panel
indicators, and Table 3-6 describes indicator functions.
POWER SUPPLY
B A
SYSTEM
ALARM TEST
MEGAPLEX-4100
Megaplex-4 Indicators 3-5

Table 3-6. System LED Indicators
Name Color Function
POWER SUPPLY Green • On: the corresponding PS module is on (and one of

A, B the CL modules is active)
• Off: Power supply is off
SYSTEM TEST Yellow • On: a test (or loopback) is being performed in the
Megaplex-4100
• Off: No active tests
SYSTEM ALARM Red • Blinking: a major and/or critical alarm has been
detected in Megaplex-4100
• On: a minor alarm has been detected in Megaplex-
4100
3.3 Startup
Configuration Files
The following files contain configuration settings:
• factory-default contains the manufacturer default settings
• running-config contains the current configuration that is different from the
default configuration
• startup-config contains the saved non-default user configuration. This file is
not automatically created. You can use the save or copy command to create
it.
• user-default-config contains default user configuration. This file is not
automatically created. You can use the copy command to create it.
• candidate stores any configuration before it is copied to running-config via
commit command.
• main-sw contains the active software image.
3-6 Startup Megaplex-4

Loading Sequence
At startup, the device boots from the startup-config file, the user-default file, or
the factory-default file, in the sequence shown in Figure 3-4 . If none of these
files exist, the device boots using hard-coded defaults.
Start
Boot from Pass Sanity Yes

Startup-config exist?
Startup-config Check
Fail
No
Boot from Pass Sanity Yes User-default-config

User-default-config Check exist?
Fail No
Boot from
Factory-default-config
End
Figure 3-4. Loading Sequence
If the loading of startup-config or the user-default file fails, the loading failure
event is registered in the event log.
To display the parameter values after startup, use the info [detail] command.
3.4 Saving Configuration Changes

Figure 3-5 shows the commands that can copy configuration files in a visual
diagram. For details on file operations, refer to File Operations in Chapter 10.
Megaplex-4 Saving Configuration Changes 3-7

Admin user-default
Sanity
check
Copy
Commit Copy
Configuration
User-Default -
Session Running-config Startup-Config Factory-Default
Config
(Candidate DB)
TFTP
TFTP
Save
Copy
Admin factory-default
Figure 3-5. Commands that Copy Configuration Files Mark
3.5 Using a Custom Configuration File

In large deployments, often a central network administrator sends configuration
scripts to the remote locations and all that remains for the local technician to do
is to replace the IP address in the script or other similar minor changes (using any
text editor), and then download the file to the device.
To download the configuration file, use the copy command. It is recommended to
copy the file to both startup-config and the user-default file and check that the
device passes the sanity test (no configuration errors are displayed).
After downloading the configuration file to startup-config, you have to execute
the file. This can be done in two ways:
• Reset the unit. After the unit completes its startup, the custom configuration
is complete.
• Instead of resetting the unit, you can simply copy the configuration file to the
running-config file (see File Operations in Chapter 10).
3.6 Turning Off the Unit

 To turn the Megaplex-4 unit off:
• Disconnect the power cord from the power source.
3-8 Turning Off the Unit Megaplex-4

Chapter 4
Management and Security
This chapter provides general operating instructions and preliminary configuration
instructions for Megaplex-4 units.
Once installed, there are no special operating procedures for Megaplex-4. The
unit operates automatically after it has started up. The unit’s operational status
can be constantly monitored. If required, Megaplex-4 can be reconfigured.
Table 4-1 summarizes management alternatives for Megaplex-4.
Table 4-1. Management Alternatives
Port Manager Transport Management Application

Location Method Protocol
CONTROL DCE Local Out-of-band RS-232 Terminal emulation programs

(HyperTerminal, Procomm, Putty).
See Management Access Methods
below.
CONTROL ETH, any Local, Out-of-band Telnet, SSH over Procomm, Putty (see Working with
user ETH port on CL remote (via CONTROL Ethernet Telnet and SSH below)
or I/O modules ETH only),
Inband
STM-1/STM-4/ Remote Inband Telnet, SSH over Procomm, Putty (see Working with
OC-3/OC-12 links DCC (IP/PPP or Telnet and SSH below)
IP/HDLC)
Any E1/T1 or SHDSL Remote Inband Telnet, SSH over Procomm, Putty (see Working with
link a dedicated Telnet and SSH below)
timeslot (IP/PPP
or IP/FR)
SNMP over a RADview (see Working with

dedicated RADview below)
timeslot (IP/PPP 3rd-party NMS (see Working with
or IP/FR) Shelf View below)
Optical (mux-eth- Local, Inband RAD proprietary HyperTerminal, Procomm, Putty,

tdm) link of OP remote any NMS
modules
Megaplex-4 Management Access Methods 4-1

Chapter 4 Management and Security Installation and Operation Manual
Port Manager Transport Management Application

Location Method Protocol
SHDSL ports of Local, Inband EOC HyperTerminal, Procomm, Putty,

ASMi-54C/E1/ETH/N remote any NMS
and ASMi-54/ETH
modules
Note By default, the terminal, Telnet (SSH), and SNMP management access methods
are enabled.
The following functions are supported by the Megaplex-4 management software:

• Viewing system information
• Modifying configuration and mode of operation, including setting system
default values and resetting the unit
• Monitoring performance
• Initiating connectivity tests
• Uploading and downloading software and configuration files.
4.1 Management Access Methods

Two methods used to access the Megaplex-4 management host are via Layer 2 or
Layer 3 networks. By default, Megaplex-4 is managed by Router 1, via Layer-3. If
you want to manage the device via a management VLAN (Layer-2 management),
the bridge must be configured.
Layer-3 Management Access

Figure 4-1 illustrates a typical Layer-3 management scheme.
Megaplex-4 and remote CPE devices are managed using:
• Out-of-band traffic via a dedicated Ethernet management port, or
4-2 Management Access Methods Megaplex-4

Installation and Operation Manual Chapter 4 Management and Security
• Inband traffic via E1/T1 and SDH/SONET ports.
mng-eth mng-eth
cl-a cl-b
RI#2
DTS
PPP
Router
DCC
RI#3
PPP
RI#1
Host
SVI#1
Figure 4-1. Layer-3 Management Access
The Megaplex-4 host can be accessed by defining IP address and enabling

management on any of the internal router interfaces.
By default, Megaplex-4 has router interface 1 connected to out-of-band Ethernet
management port internally (when no flows are configured between the bridge
and the out-of-band Ethernet management port).
For description of Layer-3 management access, see Management Router section
in Chapter 3.
Layer-2 Management Access

Figure 4-2 illustrates a typical Layer-2 management scheme. Megaplex-4 and
remote CPE devices share the same Layer-2 broadcast domain (VLAN X) and
Layer-2 forwarding entity (bridge) is used for access.
In this scheme, Megaplex-4 and remote CPE devices can be managed using:
• Out-of-band traffic via a dedicated Ethernet management port, or
• Inband traffic via any Ethernet port.
The Megaplex-4 host is an IP address of a router interface, connected to a bridge
port.
Megaplex-4 Management Access Methods 4-3

mng-eth mng-eth
cl-a cl-b
RI#2
DTS
PPP
Router
BP#3 BP#2
DCC
RI#3
1 PPP
RI#1
Bridge#1 Aware Host
BP#1
SVI#1
For description of Layer-2 management access, see Bridge section in Chapter 3.
4.2 CLI-Based Configuration
Working with Terminal

Megaplex-4 has a V.24/RS-232 asynchronous DCE port, designated CONTROL DCE
and terminated in a 9-pin D-type female connector. The control port continuously
monitors the incoming data stream and immediately responds to any input string
received through this port.
 To set up terminal control:

1. Verify that all the cables are properly connected. For more information, refer
to Chapter 2.
2. Connect Megaplex-4 to a PC equipped with HyperTerminal. Refer to
Connecting to a Terminal in Chapter 2 for additional information on
connecting to the control port.
3. Turn on the control terminal or start the PC terminal emulation. To do so, go
to Start> All Programs> Accessories> Communications>HyperTerminal to
create a new terminal connection.
The HyperTerminal application opens, and the Connection Description
dialog box is displayed.
4-4 CLI-Based Configuration Megaplex-4

Figure 4-3. HyperTerminal, Connection Description Dialog Box
4. Enter a name for the terminal connection.

5. Select an icon to represent the terminal connection, or leave the default icon
selected.
6. Click <OK>.
The Connect To dialog appears.
Figure 4-4. Connect To Dialog Box
7. Select a PC COM port to be used to communicate with Megaplex-4 and click

<OK>.
The COM Properties dialog appears.
Megaplex-4 CLI-Based Configuration 4-5

Figure 4-5. Properties Dialog Box
8. Configure the communication port parameters as follows:

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

Working with Telnet and SSH

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

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

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

enabled.
 To enable or disable access via Telnet:

1. At the config>mngmnt# prompt, enter access.
The config>mngmnt>access# prompt appears.
2. Type telnet to enable or no telnet to disable Telnet access. The access is
enabled by default.
Using SSH
 To prepare for using SSH:

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



2. Type ssh to enable or no ssh to disable Telnet access. The access is enabled
by default.
3. Connect the Ethernet port of the PC to the CONTROL ETH port of the active
CL module, or to the same LAN the CONTROL ETH port is attached to.
4. Start the SSH client program, and select the following parameters:
 Connection type: SSH
 IP address: use the preconfigured host IP address
 Port: 22 (the default SSH port)
5. Click Open to open the SSH session with the Megaplex-4.

6. You will see the log-in prompt: type the prescribed user name, for example,
su, and then press <Enter>.
7. You will see a request for password: enter the prescribed password, for
example, 1234, and then press <Enter>.
8. If login is successful, you will see the main menu.
Login
To access the unit's management/configuration/monitoring options, you must
log in.
Megaplex-4 supports the following access levels:
• Superuser (su) can perform all the activities supported by the Megaplex-4
management facility, including defining new users of any level and changing
their passwords.

• Operator (oper) can perform all the activities except defining new users and
changing passwords.
• User (user) can only monitor the device or change his/her own password
• Technician (tech) can monitor the device, perform diagnostics and clear
alarms)
 To enter the Megaplex-4100 CLI:

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

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

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

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

If a new dynamic entity is not being configured, the last character of the prompt
is > (for tech or user access levels) or # (for other access levels).
In addition to being the default prompt, the # symbol also indicates a static or
already configured entity. The $ symbol indicates a new dynamic entity that takes
several commands to configure. The dynamic entity is created as inactive. After
the configuration is completed, it is activated by using the no shutdown
command, as shown in the following example.
mp4100# configure port logical-mac 5/1
mp4100>config>port>log-mac(5/1)$ bind mlppp 5/1
mp4100>config>port>log-mac(5/1)$ no shutdown
mp4100>config>port>log-mac(5/1)$ commit
Figure 3-7. Creating and Activating Dynamic Entity
The shutdown command disables a hardware element (such as a port), while no

shutdown enables/activates it.
Note The examples in this manual use # as the last character of the prompt, unless the
creation of a new dynamic entity is being illustrated.
After you type a command at the CLI prompt and press <Enter>, responds
according to the command entered.
Navigating
To navigate down the tree, type the name of the next level. The prompt then
reflects the new location, followed by #. To navigate up, use the global command
exit. To navigate all the way up to the root, type exit all.
At the prompt, one or more level names separated by a space can be typed,
followed (or not) by a command. If only level names are typed, navigation is
performed and the prompt changes to reflect the current location in the tree. If
the level names are followed by a command, the command is executed, but no
navigation is performed and the prompt remains unchanged.
Note To use show commands without navigating, type show followed by the level
name(s) followed by the rest of the show command.
In the example below the levels and command were typed together and therefore
no navigation was performed, so the prompt has not changed.
mp4100# configure port ppp 5/1 bind e1 5/1
Figure 4-8. Commands without Level Navigation

In the following example, the levels were typed separately and the navigation is
reflected by the changing prompt.
mp4100#
mp4100# configure
mp4100>config# port
mp4100>config>port# ppp 5/1
mp4100>config>port# ppp(5/1)# bind e1 5/1
mp4100>config>port# ppp(5/1)#
Figure 3-9. Commands with Level Navigation
Note Level names are abbreviated in the prompt.
Command Tree
The tree command displays a hierarchical list of all the commands in the CLI tree,
starting from the current context.
 To view the entire CLI tree (commands only):

1. At the root level, type tree.
mp4100# tree
|
+---admin
| |
| +---factory-default
| |
| +---reboot
| |
| +---software
| | |
| | +---install
| | |
| | +---show status
more..
2. Press <Enter> to see more or <CTRL-C> to return to the prompt.
When adding the detail parameter, the output also includes the parameters and
values for each command.
 To view the CLI tree including all parameters and values:

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

mp4100>config# tree detail

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

[] Indicates an optional parameter
<> Indicates a value to be typed by the user according to
parameter requirements
You can type only as many letters of the level or command as required by the
system to identify the level or command, for example you can enter config manag
to navigate to the management level.
CLI commands have the following basic format:
command [parameter]{value1 | value2 | … | valuen} [optional parameter <value>]
where:
{} Indicates that one of the values must be selected
[] Indicates an optional parameter
<> Indicates a value to be replaced by user text
Special Keys
The following keys are available at any time:
? List all commands and levels available at the current level

<Tab> Command autocomplete
↑ Display the previous command (history forward)
↓ Display the next command (history backward)

<Backspace> Delete character before cursor

<Delete> Delete character before cursor
<- Move cursor one character left
-> Move cursor one character right
<Ctrl-E> Log out
<Ctrl>+Z Navigate to base level
The following commands are available at any time and at any level:
echo [<text-to-echo>] Echoes the specified text
exec <file-name> [echo] Executes a file, optionally echoing the commands
help [hotkeys] [globals] Displays general help, or optionally just the

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

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

accessible from the current context level
Getting Help
You can get help in the following ways:
• Type help to display general help (see General Help)
• Type help <command> to display information on a command and its
parameters
• Type ? to display the commands available in the level (see
• Level Help)
• Use <Tab> while typing commands and parameters, for string completion
• Use ? after typing a command or parameter, for interactive help (see
Interactive Help).
General Help
Enter help at any level to display general CLI help, including:

• Short description of CLI interactive help
• Commands and levels available at the current level
• Globally available commands
• CLI special keys (hotkeys)
• Output modifiers for filtering output.

Example of help command output from the root level:

1. Full help - 'help <cmd>'.
2. To complete level name, command, keyword, argument - <tab> ('conf<tab>' =>
'configuration').
3. To display all currently valid levels, commands, keywords or arguments -
'?' ('name ?' => '<name-of-device>').
Commands and levels:
admin + Administrative commands
configure + Configure device
file + File commands
Global commands:
commit - Update the candidate database to the running
database
discard-changes - Resets to last-saved parameter profile
echo - Displays a line of text (command) on the screen
exec - Executes a file
exit - Returns to the next higher command level (context)
help - Displays information regarding commands in the
current level
history - Displays the history of commands issued since the
last restart
info - Displays the current device configuration
level-info - Displays the current device configuration -
commands from the current level only
logout - Logs the device off
ping - Ping request to verify reachability of remote host
sanity-check - Initiates a self test of the device
save - Saves current settings
startup-config-confi* - Confirm configuration
tree - Displays the command levels from the current
context downwards
virtual-terminal - Enter the virtual terminal
Hotkeys:
DEL -delete character
<- -move cursor right
-> -move cursor left
TAB -complete token
? -help
Arrow up -history forward
Arrow down -history backward
BACKSPACE -delete character
^Z -return to configuration root
^E -exit cli
Command Help
Enter help <command> to display command and parameter information.
mp4100>config>system# help name
- name <name-of-device>
- no name
<name-of-device> : Adds free text to specify the device name [0..255 chars]

Level Help
Enter ? at the command prompt to display the commands available in the current
level.
mp4100>file# ?
copy - Copies a file
delete - Deletes a file from the device
dir - Lists all files in the device
show copy - Displays copy status

show sw-pack - Displays the existing sw-packs and their content
String Completion
Megaplex-4 automatically completes levels, commands, and parameters when you
press <Tab> immediately after a string.
If the string can be completed in more than one way, Megaplex-4 appends the
characters that are common to all the possibilities.
If the string can be completed in only one way, [RADDoc_ProductName]
completes it and appends a space.
If the string is already a complete level/command/parameter or cannot be
completed to a level/command/parameter, no completion is done.
Pressing <Tab> a second time displays any available command parameters.
Some user-defined strings such as flow names or profile names can be completed
as well. If the user enters an entity name (flow, profile or similar) that does not
exist in the database, Megaplex-4 creates this entity with the selected name.
The following table shows examples of string completion.
Table 4-2. String Completion
Level String Possibilities for Completion Result After Pressing <Tab>
file show c show configuration-files show co

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

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

This is a new flow, as my-flow-3
did not exist before.

Interactive Help
To get interactive help, type ?.
In general, typing a ? directly after a string performs string completion, while
typing <space> and then a ? executes the command.
When a <CR> appears in a ? list, the string you entered is itself a valid command
needing no further additions. Pressing <Enter> executes the command or
navigates to the indicated level.
Typing ? immediately after a command or partial command with no space before
the ?, tells Megaplex-4 to display all possibilities for completing the string. Help
output is always followed by the string you typed with the cursor at the end of
the string waiting for input.
mp4100>config>flows# classifier-profile myclass m?
match-any
mp4100>config>flows# classifier-profile myclass m
mp4100>admin# fact?
factory-default-all - Resets all configuration and counter
factory-default - Loads factory default configuration
mp4100>admin# fact
mp4100>admin# factory-default?
factory-default-all - Resets all configuration and counters
<CR>
mp4100>admin# factory-default
When a string cannot be completed, Megaplex-4 displays “cli error: Invalid
Command”.
mp4100>admin# stac?
# cli error: Invalid Command
mp4100>admin# stac
mp4100>file# da ?
# cli error: Invalid Command
mp4100>file# da
Typing <?> after a space between a command or level name and the ? tells
Megaplex-4 to try to execute the command. The space tells the CLI that you are
finished typing and to try to match the string to an appropriate command. The
string does not have to be a complete command.
If there is only one possible command starting with that string, pressing <Enter>
will execute the command. If there is more than one command that starts with
the string, the CLI displays a message that it can’t clarify which command you
want.
172_17_155_24>admin# factory?
factory-default-all - Resets all configuration and counters

factory-default - Loads factory default configuration
A command followed by a ? without a space, shown above, returns a list of

possible completions. The same command followed by a space and then the ?
returns an ambiguous command message. This means the string entered could be
completed to more than one command is therefore ambiguous, as shown below.

172_17_155_24>admin# factory ?
# cli error: Ambiguous Command
172_17_155_24>admin# factory
A string that is a complete command name followed by a space ? displays all
possible command parameters.
mp4100>config>flows# show ?
summary - Displays list of flows
mp4100>config>flows# show
mp4100>config>flows# classifier-profile ?
<classification-n*> : [1..32 chars]
mp4100>config>flows# classifier-profile
The next example shows a complete command to which a parameter could be
appended. It also shows how a string that is a complete command is executed by
pressing <CR>, or <Enter>.
mp4100>config>access-control# resequence access-list acl_1 ?
<CR>
<number> : [0..100000]
The next example shows a complete command that has no parameters.
mp4100>config>flows# classifier-profile myclass match-any ?
<CR>
mp4100>config>flows# classifier-profile myclass match-any
Using Scripts
CLI commands can be gathered into text files. They may be created using a text
editor, by recording the user commands or by saving the current configuration.
These files can be configuration files or scripts. Configuration files have specific
names and contain CLI commands that Megaplex-4 can use to replace the current
configuration, while scripts contain CLI commands that add to the current
configuration. Configuration files can be imported from and exported to RAD
devices via file transfer protocols.
Note Although scripts can be created using a text editor, it is recommended to save
the configuration file and then edit it rather than write a script from scratch. The
sequence of the commands is very important and if a script fails during startup at
a certain command, the entire configuration file is discarded.
For more information on configuration files, refer to the description in the

Operation chapter.
In order to execute a CLI script, you have to copy/paste it to the CLI terminal, or
send it to Megaplex-4 via the RADview Jobs mechanism, CLI script option.

4.3 GUI-Based Configuration
Preconfiguring Megaplex-4 for SNMP Management

Megaplex-4 can be managed by any SNMP-based network management station,
such as the RADview family of network management stations, provided IP
communication is possible with the management station, as well as with the
standalone RADview stations.
To manage the Megaplex-4 from a remote NMS, it is necessary to preconfigure
the basic parameters using a supervision terminal connected to the Megaplex-4
CONTROL DCE port. RAD recommends Layer-3 management access via
out-of-band Ethernet management port.
 To preconfigure Megaplex-4 for Layer-3 management access:

1. Add a router interface, bind it to the SVI and add a static route to the next
hop.
2. Configure SNMPv3 parameters:
 OID tree visibility, mask and type
 Access group
 Trap report policy.
Script below provides all necessary configuration steps. Replace IP addresses and
entity names with values relevant for your network environment.
### Defining the Router Interface####
configure
router 1 interface 1 address 172.18.171.121/24
router 1 interface 1 bind svi 1
router 1 static-route 0.0.0.0/0 address 172.18.171.1
exit all
#*********************Configuring_SNMP_View/Mask/Type************************
configure management snmp
view internet 1
mask 1
type included
no shutdown
exit all
#**********************************End***************************************
#*********************Enabling_SNMP_V3***************************************
snmpv3
no shutdown
exit all
#**********************************End***************************************
#*********************Configuring_SNMP_Access_Group************************
access-group initial usm no-auth-no-priv
context-match prefix
4-18 GUI-Based Configuration Megaplex-4

exit all
#**********************************End***************************************
#**************************Configring_SNMP_Traps*****************************
target-params p
message-processing-model snmpv3
version usm
security name initial level no-auth-no-priv
no shutdown
exit
target a
target-params p
tag-list unmasked
address udp-domain 172.17.176.35
no shutdown
exit
notify unmasked
tag unmasked
no shutdown
exit all
#**********************************End************************************
Working with RADview

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

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

Megaplex-4 can be integrated into 3rd-party management systems at different
levels:
• Viewing device inventory and receiving traps (see Chapter 11 for trap list)
Megaplex-4 GUI-Based Configuration 4-19

• Managing device, including configuration, statistics collection, diagnostics,

using standard and private MIBs:
 IANAifType-MIB
 IETF Syslog Device MIB
 IEEE8023-LAG-MIB
 MEF-R MIB
 RAD private MIB
 RFC 2819 (RMON-MIB)
 RFC 2863 (IF-MIB)
 RFC 3273 (Remote Network Monitoring MIB)
 RFC 3411 (SNMP-FRAMEWORK-MIB)
 RFC 3413 (SNMP-TARGET-MIB)
 RFC 3414 (SNMP-USER-BASED-SM-MIB)
 RFC 3415 (SNMP-VIEW-BASED-ACM-MIB)
 RFC 3418 (SNMPv2-MIB)
 RFC 3636 (MAU-MIB)
 RFC 4668 (RADIUS-AUTH-CLIENT-MIB)
 RFC 4836.MIB (MAU-MIB)
 RFC 3592 SONET MIB
 RFC 4319 SHDSL2-SHDSL-LINE-MIB
 RFC 4805 DS1-MIB.
4.4 Services for Management Traffic

To gain access to the devices, as explained in Management Access Methods, you
must provision an E-LAN (Layer-2) or routing (Layer-3) service. Services are
explained in Chapter 5.
4.5 Control Port

All the Megaplex-4 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-4 serial RS-232 asynchronous supervisory port, located on its front
panel. The terminal is controlled by the program stored in the Megaplex-4. No
information has to be stored in the terminal.
4-20 Control Port Megaplex-4

Standards
The control port complies with the EIA RS-232/ITU-T V.24 standards.
Functional Description
The supervisory port enables the preliminary configuration of the Megaplex-4.
After the preliminary configuration is completed, Megaplex-4 can also be
managed by the other means, for example, Telnet hosts and SNMP network
management stations.
The supervisory port has a DCE interface, and supports data rates in the range of
9.6 to 115.2 kbps.
The terminal control parameters determine the control port's baud rate,
password used for each control session, and availability of the fixed security
timeout.
The following parameters can be configured for the control ports:
• Data rate
• Security timeout
• Length of the screen from which you are accessing the device.
Note Terminal parameters can only be configured when using a terminal connection.
Factory Defaults
Megaplex-4 is supplied with the control port enabled. Other parameter defaults
are listed in the table below.
Parameter Default Value
baud-rate 9600 bps
timeout 10
Configuring the Control Port

 To configure the terminal parameters:
• At the config>terminal# prompt, enter the necessary parameters according to
the table below.
Task Command Comments
Setting the baud rate (bps) baud-rate {9600bps | 19200bps |

38400bps | 57800bps | 115200bps}
Enabling and defining a security timeout limited <timeout in minutes> Possible values are 0 to 60.
timeout (in minutes)
Megaplex-4 Control Port 4-21

To specify the number of rows to length <number-of-rows> The number of rows can be 0,
display to indicate no limit on the
number of lines displayed, or
20.
Disabling the security timeout timeout forever
For example:
 To set up a terminal connection at 19200 kbps with timeout after 10 minutes:

• Set up the baud rate to 19200 kbps and make sure that the same rate is
selected in HyperTerminal for any future HyperTerminal connections.
• Set the security timeout to 10 minutes.
mp4100>config>terminal# baud-rate 19200bps
mp4100>config>terminal# timeout-limited 10
4.6 Management Ethernet Port

Megaplex-4 has one out-of-band management Ethernet port (CONTROL ETH)
located on each CL.2 module panel dedicated to management traffic. The port
has 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 CONTROL ETH ports of both CL modules can be simultaneously connected to
the same LAN, through standard Ethernet hubs or switches.
To support out-of-band management, management stations, Telnet hosts, etc
can be attached to the same LAN, or to any LAN from which IP communication
with the CL.2 module Ethernet ports is possible.
Benefits
Configuring a dedicated management port eliminates the possibility of
management traffic reducing bandwidth and/or causing interruptions in the
traffic flow caused by the management.
Configuring the Out-Of-Band Management Port

The following parameters can be configured for the management Ethernet port:
• Port name
• Administrative status.
 To configure the Management Ethernet port parameters:

1. Navigate to configure port mng-ethernet <slot>/<port> to select the
Ethernet port to configure.
4-22 Management Ethernet Port Megaplex-4

The config>port>mng-ethernet>(<slot>/<port>)# prompt is displayed.

2. Enter all necessary commands according to the tasks listed below.
Assigning short description to port name <string> Using no before name removes the name
Administratively enabling port no shutdown Using shutdown disables the port
Configuring collection of pm-collection interval <seconds> Note: You can enable PM statistics
performance management statistics collection for all Ethernet ports rather than
for the port, that are presented via enabling it for individual ports. In addition
the RADview Performance to enabling PM statistics collection for the
Management portal ports, it must be enabled for the device.
Refer to the Performance Management
section in the Monitoring and Diagnostics
chapter for details.
4.7 User Access

Megaplex-4 management software allows you to define new users, their
management and access rights. Only superusers (su) can create new users, the
regular users are limited to changing their current passwords, even if they were
given full management and access rights.
You can specify a user password as a text string. You can add a second user with
the same password using the hash function as explained below.
Factory Defaults
By default, the following users exist, with default password 1234:
• su
• tech
• user.
 To add a new user:

1. Make sure that you are logged on as superuser (su).
2. Navigate to the Management context (config>mngmnt).
3. Define a new user: user <name> [ level { su | tech | user } ]
[[ password <password> [hash] ]
Defining Users and Passwords

Follow the instructions below to add users and assign passwords.
Megaplex-4 User Access 4-23

Notes • User passwords are stored in a database so that the system can perform
password verification when a user attempts to log in. To preserve
confidentiality of system passwords, the password verification data is typically
stored after a one-way hash function is applied to the password, in
combination with other data. When a user attempts to log in by entering a
password, the same function is applied to the entered value and the result is
compared with the stored value.
• A cryptographic hash function is a deterministic procedure that takes an
arbitrary block of data and returns a fixed-size bit string, the (cryptographic)
hash value, such that any change to the data changes the hash value.
 To add a new user:

1. Make sure that you are logged on as superuser (su).
2. At the user prompt config>mngmnt>, enter
user <name> [level <debug | su | oper | tech | user>] [password <password of
up to 40 characters>].
The user name, the associated user level and the password are defined.
 To add another user with the same password using the hash function:
1. At the user prompt config>mngmnt> prompt, enter info.
The first user’s password’s hash value appears as illustrated below.
mp4100>config>mngmnt# info
user "staff1" level user password
"3fda26f8cff4123ddcad0c1bc89ed1e79977acef" hash
2. Define another user with the hashed password obtained from the info
output.
The second user is added and can log on with the text password defined
in step 1.
 To delete an existing user:

• At the config>mngmnt# prompt, enter no user <name>.
The specified user is deleted.
Example
 To add a super user with a text password and access to all possible ways of
management:
• Specify the user name staff for the user level su.
• Assign the password 1234.
mp4100>config>mngmnt# user staff level su password 1234
# Password is encrypted successfully
Megaplex-4>config>mngmnt#
 To add two new users with identical passwords using the hash function:
• Assign the user name staff1.
4-24 User Access Megaplex-4

• Assign the password 4222.

• Assign the user name staff2.
• Assign the same password 4222 to staff2 by linking the hash output to
staff2.
mp4100>config>mngmnt# user staff1 level user password 4222
# Password is encrypted successfully
Megaplex-4>config>mngmnt# info
user "su"
mp4100>config>mngmnt# user staff2 level user password

3fda26f8cff4123ddcad0c1bc89ed1e79977acef hash
mp4100>config>mngmnt# info
user "su"
mp4100>config>mngmnt# logout
CLI session is closed
user>staff2
password>4222
mp4100#
Viewing Connected Users

35B
This section explains how to view users currently logged on to the unit.
 To view all connected users:

• At the config>mngmnt# prompt, enter show users.
A list of all connected users is displayed, showing their access level, the
type of connection, and the IP address from which they are connected.
mp4100# configure management
mp4100>config>mngmnt# show users
User Access Level Source IP-address
-----------------------------------------------------------------------------
su SU Terminal 172.4.3.3
Megaplex-4>config>mngmnt#
4.8 Access Control List (ACL)

Access control lists are used to flexibly filter and mark incoming network traffic.
Megaplex-4 Access Control List (ACL) 4-25

Standards and MIBs

Relevant sections of RFC 1812
Benefits
The service providers use the ACLs to maintain the network security by
preventing the malicious traffic from entering the device.
Devices featuring ACLs can flexibly filter management traffic, by denying or
permitting IP packets to enter entities in the device, according to the packet’s
source address, protocol type or other criteria.
ACL entries are sequentially numbered rules, or ACEs (Access Control Elements)
containing statements (Deny, Permit) and conditions. You can create up to 3 ACL
and up to 128 ACEs per system.
Packets are permitted or denied access, based on the following conditions:
• IP source address
• TCP and UDP port.
The ACL structure is illustrated in the Example section.
If there is a need to add a rule between already existing rules with consecutive
numbers, the rules can be interspaced to accommodate additional rules between
them.
Binding Access Control Lists

Once created, ACLs are applied (bound) to the virtual management entity for
filtering management traffic (only inbound direction is supported).
Filtering
Packets attempting to enter an entity to which the ACL is bound are checked
against the access list rules, one by one. Access of matching packets is denied
(packets are dropped) or permitted, as directed by the ACL statement.
Packets matching a Deny statement (rule) are dropped unless permitted by a
previous rule.
Packets matching a Permit statement (rule) are permitted to access an entity
unless denied by a previous statement.
After a match, the rest of the rules are ignored. Packets not matching any rule
are dropped. Empty ACLs deny access of all packets matched to them.
Statistics
The device collects ACL statistics per management entity. The statistic counters
include the number of rule matches that occurred since the counters were last
cleared. The statistic counters are cleared upon device reboot. The user may also
clear ACL statistics of any entity and direction pair.
4-26 Access Control List (ACL) Megaplex-4

Factory Defaults
By default there are no ACL lists configured.
Configuring ACL
The ACL configuration tasks are performed at the access control and
management levels.
 To configure an ACL:
1. Create an access control list.
2. Add deny and permit rules to the ACL.
3. Bind the ACL to a management entity
Access-Control-Level Tasks
The following commands are available in the CLI access-control context:
config>access-control#. The exception to this are the deny and permit
commands, which are performed in the access-list(acl_name) context:
configure>access-control>access-list(acl_name)#.
Table 4-3. Access-Control-Level Commands
Creating and access-list <acl_name> You can create up to 3 ACLs per system.
deleting an ACL no access-list <acl_name> Creating an ACL is performed by assigning
a name. The ACL names must be unique
and contain up to 252 alphanumeric
characters.
Adding deny deny {tcp | udp} <src-address>[<src-port- Management-bound ACLs have the
rules to an ACL range>] <dst-address>[<dst-port>] [log] following configuration limitations:
[sequence <sequence-number>] • <src-port-range> must be any port –
do not indicate specific ports
• The destination IP address (<dst-
address>) must be any
• The destination port must be tcp/23
(Telnet), tcp/22 (SSH) or udp/161
(SNMP)
Sequence number range is 1–
2147483648.
log – not in use in the current version

Adding permit permit {tcp | udp} <src-address>[<src-port- Management-bound ACLs have the
rules to an ACL range>] <dst-address> [<dst-port-range>] following configuration limitations:
[log] [sequence <sequence-number>] • <src-port-range> must be any port –
do not indicate specific ports
• The destination IP address (<dst-
address>) must be any
• The destination port must be tcp/23
(Telnet), tcp/22 (SSH) or udp/161
(SNMP)
Sequence number range is 1–
2147483648.
log – not in use in the current version
Removing rules delete <sequence-number> The value range is 1–2147483647

from an ACL seconds
Setting the logging access-list <value> Enable logging at the maximum rate of the
logging interval no logging access-list value set at Access Control level.
of all ACLs no logging access-list disables event
logging for all rules in the ACL.
Management-Level Tasks
The following commands are available in the CLI management context:
configure>management>access#.
Table 4-4. Management-Level Commands
Binding the ACL to a access-group <acl-name> in The management entity supports the ACLs
management entity no access-group only in the in direction.
Displaying ACL statistics show access-list statistics See Displaying Statistics below.
Clearing ACL statistics clear-statistics access-list
Displaying the summary show access-list summary Displays ACL status at the current level
of ACLs bound to a See Displaying Status below
management entity
Example
 To create an ACL:
The example below illustrates a typical ACL applied to the incoming management
traffic:
• Allows SNMP (UDP port 161) traffic from source 172.17.170.81/32
• Allows SSH (TCP port 22) traffic from source 172.17.170.81/32
• Allows Telnet (TCP port 23) traffic from source 172.17.170.81/32
4-28 Access Control List (ACL) Megaplex-4

configure
access-control
access-list mng1
permit udp 172.17.170.81/32 any 161 sequence 1
permit tcp 172.17.170.81/32 any 22 sequence 2
permit tcp 172.17.170.81/32 any 23 sequence 3
Note
You cannot edit a rule with the same sequence number. To edit a rule, delete the
existing one and create a new rule with a new sequence number.
The table below summarizes the rules configured for the ACL. Items in red are
either implied or unavailable for the current parameter or serve as system
settings that cannot be changed.
Sequence Action Protocol Source IP TCP/UDP Dest. IP TCP/UDP Dest. Port

Number Source Port
1 Permit UDP 172.17.170.81/32 Any Any 161
2 Permit TCP 172.17.170.81/32 Any Any 22
3 Permit TCP 172.17.170.81/32 Any Any 23
Displaying Status
The ACL status displays information on the ACL name, type (IPv4), the entity that
the ACL is bound to and its direction. The status information is available for the
ACLs at the management access levels.
 To display the ACL status:

• In the config>mngmnt>access# prompt, enter the show access-list summary
command.
The following status information is displayed:
ACL Name Type Bound to Direction
---------------------------------------------------------------
mng1 IPv4 management inbound
Displaying Statistics
The ACL statistic counters gather information on the number of rule matches
registered on the ACL since the last reboot or counter clearing.
Note All ACLs have an implied last rule that denies all packets. The device does not
provide statistic counters for this rule. If you intend to collect statistics on the
number of the packets discarded by the default ACL mechanism, you must add
the deny ip any any rule at the end of the ACL.

 To display the ACL statistics:

• In the config>mngmnt>access# prompt, enter the show access-list statistics
command.
The following statistic information is displayed:
IPv4 access list: mng1 (in)
Bound to: Management
Matches counted for: 0 days 0 hours 2 minutes 33 seconds
---------------------------------------------------------------
10 permit tcp 172.17.154.154/24 any 22 (0 matches)
20 permit tcp 172.17.154.154/24 any 23 (0 matches)
30 permit udp 172.17.154.154/24 any 161 (0 matches)
4.9 SNMP Management

SNMP stands for ‘Simple Network Management Protocol’ and is an application
layer protocol that provides a message format for the communication between
managers and agents. SNMP systems consist of an SNMP manager, an SNMP
agent and a MIB. The NMS can be part of a management network system. To
configure SNMP, you have to define the relationship between the manager and
the agent. Megaplex-4 supports SNMPv3, the latest SNMP version to date.
SNMPv3 provides secure access to devices in the network such as Megaplex units
by using authentication and data encryption.
Standards
This section states the standards that the supported SNMP versions are based
on.
• RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working
Group.
• RFC 1902, Structure of Management Information for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group.
• RFC 1903, Textual Conventions for Version 2 of the Simple Network
Management Protocol (SNMPv2). SNMPv2 Working Group.
• RFC 1904, Conformance Statements for Version 2 of the Simple Network
• RFC 1905, Protocol Operations for Version 2 of the Simple Network
• RFC 1906, Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2).
• RFC 1907, Management Information Base for Version 2 of the Simple
Network Management Protocol (SNMPv2). SNMPv2 Working Group.
• RFC 1908, Coexistence between Version 1 and Version 2 of the Internet-
standard Network Management Framework. SNMPv2 Working Group.
• RFC 2104, Keyed Hashing for Message Authentication.
4-30 SNMP Management Megaplex-4

• RFC 2271, Architecture for Describing SNMP Management Frameworks.

• RFC 2272, message processing and dispatching for the Simple Network
Management Protocol (SNMP).
• RFC 2273, SNMPv3 Applications.
• RFC 2274, User-Based Security Model (USM) for version 3 of the Simple
Network Management Protocol (SNMPv3).
• RFC 2275, View-Based Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP).
• RFC 3412, Version 3 Message Processing and Dispatching.
• RFC 3414, User-based Security Model for SNMPv3
• RFC 3416, Update for RFC 1904.
Benefits
The SNMP protocol allows you to remotely manage multiple units from a central
work station using RADview EMS. RADview EMS offers a graphical user interface
that resembles the front panel of your unit with its interfaces and LEDs.
Megaplex-4 supports SNMPv3, which allows data to be collected securely from
SNMP devices. Confidential information such as SNMP commands can thus be
encrypted to prevent unauthorized parties from being able to access them.
In an SNMP configuration, one or more administrative computers manage a group
of hosts or devices. Each managed system continuously executes a software
component called agent, which reports information via SNMP back to the
managing systems.
get_request
get_response
get_next_request
get_response
set_request
Megaplex Unit
(MIB, SNMP Agent)
Work Station with get_response
RADview
(SNMP Manager)
traps
Figure 4-10. SNMP Network Scheme
The SNMP agent contains MIB variables whose values the SNMP manager can
request or change. A manager receives/transmits a value from/to an agent. The
agent gathers data from the MIB (Management Information Base). A MIB module
is actually the ‘store’ for data on network and device parameters. In addition, the
Megaplex-4 SNMP Management 4-31

agent may set or get data according to manager commands. Commands are used
to send and receive data as follows:
• get. Retrieving specific management information.
• get-next. Retrieving management information via traversal
• set. Manipulating management information.
• get-response. Sent by an agent to respond to any of the above.
• trap. Messages on events such as improper authentication, link status,
loss/restoration of connections etc, sent by the agent to notify the manager
of the current conditions.
SNMP Message Formats

Megaplex-4 supports SNMPv1, SNMPv2c and SNMPv3. The SNMP message formats
of those three standards are illustrated below. Additional SNMPv2 formats exist,
but are not supported by Megaplex-4.
SNMPv1 Message Format

The SNMP general message format was originally used to define the format of
messages in the original SNMP Protocol (SNMPv1), and was therefore relatively
straight-forward.
The general message format in SNMPv1 is a wrapper that consists of a small
header and an encapsulated PDU as illustrated and explained below.
There are not many header fields needed in SNMPv1 because of the simple
nature of the community-based security method in SNMPv1.
Table 4-5. SNMPv1 Header Fields
Field Name Syntax Size (Bytes) Description
Version Integer 4 Version Number. Describes the SNMP version number of

this message; used for ensuring compatibility between
versions. For SNMPv1, this value is 0.
Community Octet string Variable Community String. Identifies the SNMP community in which
the sender and recipient of this message are located. This
is used to implement the simple SNMP community-based
security mechanism.
PDU -- Variable Protocol Data Unit. The PDU is communicated at the body
of the message.

0 16 32
Version Number = 0
Community String
PDU Control Fields
Message Body (PDU)
PDU Variable Bindings
Figure 4-11. SNMPv1 General Message Format
SNMPv2c Message Format

Amongst various approaches to introduce SNMPv2, SNMPv2c was the most
accepted one. Its architecture is identical to SNMPv1 except for the version
number, which is 1 instead of 0. 0 is the version number for SNMPv1.
SNMPv3 Message Format

SNMPv3 adds security methods and parameters and completes the respective
approach that has been started with SNMPv2, but did not lead to a common
standard. This standard has been established with SNMPv3.
The significant changes made in SNMPv3 include a more flexible way of defining
security methods and parameters, to allow the coexistence of multiple security
techniques.
The general message format for SNMPv3 still follows the idea of an overall
message “wrapper” that contains a header and an encapsulated PDU, but it has
been significantly refined. The fields in the header have been divided into those
dealing with security and those not dealing with security. The ’non-security’ fields
are common to all SNMPv3 implementations, while the use of the ‘security’ fields
can be tailored by each SNMPv3 security model, and processed by the module in
an SNMP entity that deals with security. The entire processing in SNMPv3 is
described in RFC 3412.
For a detailed illustration and explanation, refer to the figure and the table
below.

0 16 32
Message Version Number = 3
Message Identifier
Maximum Message Size

Message Security Model
Message Flags
(bytes 1 to 3)
Message Security
Model (byte 4)
Message Security Parameters
Context Engine ID
Context Name
Scoped PDU
PDU Control Fields
Message Body (PDU)
PDU Variable Bindings
0 4 8
Privacy Authen-
Reportable tication
Reserved Flag Flag
Flag
(Priv)
(Auth)
Figure 4-12. SNMPv3 General Message Format

Table 4-6. SNMPv3 General Message Format
Msg Version Integer 4 Message Version Number. Describes the SNMP version
number of this message; used for ensuring compatibility
between versions. For SNMPv3, this value is 3.
Msg ID Integer 4 Message Identifier. A number used to identify an SNMPv3

message and to match response messages to request
messages. This field was created to allow the matching at
the message processing level to protect against certain
security attacks regardless of the PDU content. Thus, Msg
ID and Request ID are used independently.
Msg Max Size Integer 4 Maximum Message Size. The maximum size of message that
the sender of this message can receive. Minimum value of
this field is 484.
Msg Flags Octet String 1 Message Flags. A set of flags tcontrols processing the
message. the substructure of this field is illustrated in
Table 4-7.
Msg Security Integer 4 Message Security Model. An integer value indicating which
Model security model was used for this message. For the user-
based security model (default), this value is 3.
Msg Security -- Variable Message Security Parameters. A set of fields that contain
Parameter parameters required to implement the respective security
model for this message. The contents of this field are
specified in every document that describes an SNMPv3
security model. For example, the parameters for the user-
based model are defined in RFC 3414.
Scoped PDU -- Variable Scoped PDU. Contains the PDU to be transmitted along
with parameters that identify an SNMP context, which
describes a set of management information accessible by a
particular entity. The PDU is referred to as ‘scoped’
because it is applied within the scope of this context. This
field may or may not be encrypted, depending on the value
of the Private Flag. The structure of the PDU field is
illustrated in Table 4-8.
Table 4-7. SNMPv3 Message Flag Substructure
Field Name Size (Bytes)
Reserved 5/8 (5 bits) Reserved. For future use
Reportable Flag 1/8 (1 bit) Reportable Flag. If set to 1, a device receiving this message has
to return a Report-PDU whenever conditions arise that require
such a PDU to be generated.
Priv Flag 1/8 (1 bit) Privacy Flag. If set to 1, it indicates that the message was
encrypted to ensure its privacy.

Field Name Size (Bytes)
Auth Flag 1/8 (1 bit) Authentication Flag. If set to 1, it indicates that authentication
was used to protect the authenticity of this message.
Table 4-8. Structure of the PDU Field
Context Engine ID Octet String Variable Context Engine ID. Used to identify to which
application the PDU will be sent for processing.
Context Name Octet String Variable Context Name. An object identifier specifying the
particular context associated with this PDU.
PDU -- Variable PDU. The protocol data unit being transmitted.
The SNMPv3 Mechanism

SNMPv3 uses the basic SNMP protocol and adds the following security
functionalities:
• Message integrity. Ensuring that the package has not been tempered with
during transmission.
• Authentication. Verifying that the message comes from a valid source.
• Encryption. Preventing snooping by unauthorized sources.
SNMPv3 does not refer to managers and agents, but to SNMP entities. Each
entity consists of an SNMP engine and one or more SNMP components. The new
concepts define an architecture that separates different components of the
SNMP system in order to make a secure implementation possible. The SNMPv3
components are explained in the following sections.
The SNMPv3 Engine

The SNMPv3 engine consists of four subsystems that address authentication and
access authorization.
• Dispatcher. Sending and receiving messages. It tries to determine the SNMP
version of each message (SNMPv1, SNMPv2c or SNMPv3) once it is handed
over to the message processing subsystem.
• Message processing subsystem. Prepares messages to be sent and extracts
data from received messages.
• Security subsystem. Provides authentication and privacy services. The
authentication uses either community strings to support SNMP Versions 1 and
2, or user-based authentication for SNMPv3. SNMPv3 user-based
authentication uses the MD5 or SHA algorithms to authenticate users without
sending a clear password. The privacy service uses the DES algorithm to
encrypt and decrypt SNMP messages. Currently, DES is the only algorithm
used, though others may be added in the future.
• Access control system. Managing the access control to MIB objects. You can
define objects that a user can access as well as operations that a user is
allowed to perform on those objects. For example, you may grant read-write

access to certain parts of the MIB-2 tree, while allowing read-only access to
the remaining parts of the tree.
SNMPv3 Components
SNMPv3 consists of components that deal with receiving/issuing requests,
generating traps etc. These commands are listed and explained below.
• Command generator. Generates the Get, Get-Next, Get-Bulk requests, Set
requests, and processes the responses. This application is implemented by an
NMS to issue queries and set requests against entities on routers, switches,
Unix hosts etc.
• Command responder. Responds to Get, Get-Next, Get-Bulk requests. The
command responder is implemented by the SNMP agent.
• Notification originator. Generates SNMP traps and notifications. This
application is implemented by an entity on a router or host.
• Proxy forwarder. Facilitates the passing of messages between entities.
RFC 2571 allows additional applications to be defined over time, which is a
significant advantage over the older SNMP versions. The figure below illustrates
how the components fit together creating an entity.
SNMP Entity
SNMP Engine (idntified by SnmpEngineID)
Message Access
Dispatcher Security
Processing Control
Subsystem
Subsystem Subsystem
SNMPv3 Components
Command Generator Notification Receiver Proxy Forwarder
Command Responder Notification Originator Other
Figure 4-13. SNMPv3 Entity
Factory Defaults
By default, SNMPv1 is enabled. SNMPv2c and SNMPv3 are disabled.
Configuring for SNMP Management

Before configuring SNMPv3, you should specify an SNMPv3 engine.
Specifying an SNMPv3 Engine

By default, the SNMPv3 engine ID config type is set to MAC-address. To use a
different ID config type, refer to the instructions below.

 To specify the SNMP engine ID config type:

1. At the config>mngmnt# prompt, enter snmp.
The config>mngmnt>snmp# prompt appears.
2. At the config>mngmnt>snmp# prompt, enter snmp-engine-id {mac<MAC
address>|ip4 <IP address>|text <string>}.
The SNMP engine ID config type ID is specified.
Note If you use the CL.2 protection, the SNMP engine ID must be identical for both the
working card and the protection card, which means that you have to assign the
same MAC address or IP address etc. to both cards.
 To enter the SNMP engine ID string:

• At the config>mngmnt>snmp# prompt, enter snmp-engine-id-string <string
of up to 27 alphanumeric characters>.
The SNMP engine ID is specified and SNMPv3 can be enabled and
configured.
Enabling SNMPv3
 To enable/disable SNMPv3:
• To enable the SNMPv3 engine, at the config>mngmnt>snmp# prompt, enter
snmpv3.
The SNMPv3 engine is enabled.
• To disable the SNMPv3 engine, at the config>mngmnt>snmp# prompt, enter
no snmpv3.
The SNMPv3 engine is disabled.
Specifying an SNMPv3 User
 To specify an SNMPv3 user:

• After SNMPv3 has been enabled, at the config>mngmnt>snmp# prompt,
enter the following, depending on the SNMPv3 authentication protocol used:
Adding a user who user <security-name> • security name. The user specific security
authenticates using the [md5-auth [{des|none}]] name, consisting of up to 32 alphanumeric
MD5 protocol. characters.
• md5-auth. MD5 authentication protocol.
• des. Using the DES privacy protocol.
• none. No privacy protocol used.
Adding a user who user <security-name> • sha-auth. SHA authentication protocol.

authenticates using the [sha-auth [{des|none}]]
SHA protocol.

Adding a user who does user <security-name> • none-auth. No authentication performed.

not authenticate. [none-auth]
Removing a user no user <security-name>
 To deactivate a user:
1. At the config>mngmnt>snmp# prompt, enter user <security name>.
The config>mngmnt>snmp>user(<security name>)# prompt appears.
2. Enter shutdown.
The user is deactivated but remains available.
Specifying a Trap Source Address for Management Router

You can specify a trap source address.
 To specify a trap source address:

1. Navigate to config>mngmnt>snmp>server# prompt.
2. Enter the following:
Defining the trap source trap-source-address <IP Using no before trap-source-address disables
address address> the address.
If the trap source address is not defined, the
traps will be sent with the following source
addresses:
• if the loopback interface is defined (see
Configuring the Management Router in
Chapter 8), the traps will be sent with the
loopback interface IP address.
• if the loopback interface is not defined, the
traps will be sent with the Interface 1 IP
address.
Defining User (Access) Groups

Megaplex-4 supports up to 10 SNMPv3 managers with different authorization and
privacy tributes.
 To define and remove an SNMP access group:

• At the config>mngmnt>snmp# prompt, enter the following:
access-group <group-name> {snmpv1 |snmpv2c | usm} {no-auth-no-priv |
auth-no-priv | auth-priv}
The config>mngmnt>snmp>access-group(<group name>/<snmpv1 |
snmpv2c | usm>/<no-auth-no-priv|auth-no-priv|auth-priv>)# prompt
appears.

Defining an access access-group <group-name> {snmpv1 • group name. Identifies the access
group |snmpv2c | usm} {no-auth-no-priv | group.
auth-no-priv | auth-priv} • snmpv1, snmpv2c, usm. Security
model for the SNMP messages.
• usm. User based security model
• no-auth-no-priv. Authorization and
privacy are disabled, lowest level of
security for generating SNMP
messages.
• auth-no-priv. Authorization enabled,
privacy disabled.
• auth- priv. Authorization and privacy
disabled, highest level of security for
generating SNMP messages.
Removing an access no access-group <group-name>

group {snmpv1 |snmpv2c | usm}
{no-auth-no-priv | auth-no-priv | auth-
priv}
 To configure the access criteria for the SNMP access group:

• At the config>mngmnt>snmp>access-group(<group
name>/<snmpv1|snmpv2c|usm>/<no-auth-no-priv|auth-no-priv|auth-priv>)#
prompt, enter the following;
context-match {exact|prefix} • exact. In order to gain access rights,

the group name must match exactly
the value of the instance of this
project.
• prefix. The group name must match
partially the value of the instance of
this project.
Specifying the read view of the read-view <name>

access group
Specifying the write view of the write-view <name>

access group
Specifying the notify view of the notify-view <name>

access group
 To define the access control policy for users:

• At the config>mngmnt>snmp# prompt, enter the following:

Linking a user to a security security-to-group {any | snmpv1 | snmpv2c | • security name. The user
model usm} sec-name {security-name} specific security name.
• snmpv1, snmpv2c, usm.
Security model for the
SNMP messages as
explained previously.
• any. Any security model is
allowed for the relevant
access group.
Removing the link of a user no security-to-group {any | snmpv1 |

to a security model snmpv2c | usm} sec-name {security-name}
Setting up a View
 To define a view:
• At the config>mngmnt>snmp# prompt, enter parameters as illustrated and
explained below.
The mngmnt>snmp>view(<view name>/<subtree OID>)# prompt appears.
Assigning a name and an view <view name> <subtree OID>

object ID to the view
Removing the view no view <view name> <subtree OID>
 To configure the view you previously defined:

• At the config>mngmnt>snmp>view(<view name>/<subtree OID>)# prompt,
enter parameters as illustrated and explained below.
Enabling the view no shutdown
Disabling the view shutdown The view is disabled, but remains

available.
Masking a view mask <mask name>
Including, excluding the type {included | excluded}

view.
Mapping SNMPv1 to SNMPv3

Megaplex-4 supports coexistence of different SNMP versions by mapping
SNMPv1/SNMPv2 community names to the SNMPv3 security name values. The
mapping is performed according to the RFC 3584 requirements.

 To set up an SNMPv3 community:

• At the config>mngmnt>snmp# prompt, enter parameters as illustrated and
explained below.
The config>mngmnt>snmp>community(<community-index>)# prompt
appears.
Defining a community community <community-index> community-index. Free text, consisting

of up to 32 alphanumeric characters.
Removing a community no community <community-index>
 To map an SNMPv1/SNMPv2 community to SNMPv3:

• At the config>mngmnt>snmp>community(<community-index>)# prompt,
enter parameters as illustrated and explained below.
Specifying the SNMPv1/SNMPv2 name <community-string> community-string. Free text,

community name for which the consisting of up to 32 alphanumeric
information is presented. characters.
Specifying the SNMPv3 security name sec-name <sec-name> sec-name. Free text, consisting of
to be mapped to the SNMPv1/SNMPv2 up to 32 alphanumeric characters
community name
Activating the community no shutdown
De-activating the community shutdown The community is de-activated, but

remains available.
Specifying a set of the transport tag <transport-tag> As defined for each target
endpoints that are used in either of
the following methods:
• Specifying the transport endpoints
from which an SNMP entity accepts
management requests.
• Specifying the transport endpoints
to which a notification may be sent,
using the community string
matching the corresponding
instance of community name.
Configuring Targets
A target is a network management station to which Megaplex-4 should send trap
notifications over SNMPv3. A set of parameters must be configured and assigned
to each target. Then, each target must have a valid IP address and IP mask. In
addition, a previously configured parameter set and notification tags must be
assigned to the target.
To configure a target, you have to first configure a parameter set that you will
have to attach to the relevant target when it is being configured.

 To configure a target parameter set:

• At the config>mngmnt>snmp# prompt, enter target-params <params-name>.
The config>mngmnt>snmp>target(<params-name>)# prompt appears and
the target parameters can be set as illustrated and explained below.
The target parameter set you configure must be attached to the relevant
target as explained on the next page.
Defining the message message-processing-model {snmpv1 |

preprocessing model to be used snmpv2 | snmpv3}
when generating SNMP
messages.
Specifying the security level to security [name <security-name>][level • security-name. Free

be used when generating SNMP {no-auth-no-priv|auth-no-priv | auth-priv}] text, consisting of up to
messages. 32 alphanumeric
characters.
• no-auth-no-priv. No
authentication, no
privacy
• auth-no-priv.
Authentication, no
privacy
• auth-priv.
Authentication and
privacy
Specifying the SNMP version version { snmpv1 | snmpv2c | usm} • usm. User based
(security model) security model
 To configure the target:

• At the config>mngmnt>snmp# prompt, enter target <name>.
The config>mngmnt>snmp>target(<name>)# prompt appears and the
target parameters can be set as illustrated and explained below.
Identifying the address udp-domain <0.0.0.0..255.255.255.255> You have to enter the domain
target NMS address oam-domain <oam-port> and the IP address or the OAM
port, depending on whether
the target NMS belongs to a
UDP domain or an OAM
domain.
Activating the no shutdown address

transmission of
SNMP message to
the target NMS

Deactivating the shutdown address

transmission of
SNMP message to
the target NMS
Selecting a tag from tag-list <list>

the list of previously
defined notification
tags.
Configuring SNMP Communities for SNMPv1

This section instructs you on setting up read-, write-, and trap communities for
SNMPv1.
 To set up communities:
• Make sure that SNMPv3 is disabled and at the
Megaplex-4>config>mngmnt>snmp# prompt, define the desired community
as illustrated and explained below.
Defining a read community community read <name> Assign a name consisting of up to 20

alphanumerical characters.
Defining a write community community write <name> Assign a name consisting of up to 20

Defining a trap community community trap <name> Assign a name consisting of up to 20

Note
The names you assign to the communities are case sensitive.
Adding SNMPv3 Notification Entries

You can define which types of notification will be sent to previously configured
target management stations as explained under Configuring Targets.
 To define and enable a notification entry:

1. At the config>mngmnt>snmp# prompt, enter notify <notify_name>.
The config>mngmnt>snmp>notify(<notify_name>)# prompt appears.
2. Configure the notification entries as illustrated and explained in the table
below.
Assigning a single tag tag <name>

value to the notification
used to identify the
notification entry when
configuring the target

Associating traps with the bind {<trap name> or <list of traps names>} You can associate
notification entry one or more traps to
the notification
entry
Activating the notification no shutdown

entry
De-activating the shutdown

notification entry
 To disable notification:
• At the config>mngmnt>snmp# prompt, enter no notify <notify_name>.
The notification is disabled.
Configuring a Notification Filter

You can customize a notification filter view as explained below.
 To set up a notification filter:

1. At the config>mngmnt>snmp# prompt, define a notification filter and assign
a name and an object ID (sub-tree-oid) to it by entering
notify-filter <name> <sub-tree-oid>.
The config>mngmnt>snmp>notify-filter(<name>/<sub-tree-oid>) prompt
appears.
 name. Refers to the name of the notify filter.
 sub-tree-oid. Refers to the MIB subtree, which defines a family of
subtrees included in or excluded from the filter profile, if combined with
the corresponding instance of snmpNotifyFilterMask.
2. Configure the notification filter as illustrated and explained in the table
below.
Activating the notification filter no shutdown
De-activating the notification filter shutdown
Defining if the notification filter includes type {included|excluded} • included. The subtrees defined by
or excludes specific notifications. sub-tree-oid are included in the
notification profile.
• excluded. The listed subtrees by
sub-tree-oid excluded from the
notification profile.
Masking the notification filter mask
Configuring a Notification Filter Profile

You can customize the notification view as explained below.

 To define a notification filter profile:

1. At the config>mngmnt>snmp# prompt, enter
notify-filter-profile <params-name>.
The config>mngmnt>snmp>filter-profile# prompt appears. params-name.
refers to the name of the profile notification parameter set.
2. Configure the notification filter profile as illustrated and explained in the table
below.
Assigning a name to the notification profile-name <name> Refers to the name of the profile
profile itself
Enabling the notification filter profile no shutdown
Disabling the notification filter profile shutdown
Linking User (Access) Groups to an Access Control Policy
 To create a user group linked to a specific access control policy:

1. At the config>mngmnt>snmp# prompt, enter security-to-group <any | snmpv1
| snmpv2c | usm> sec-name <security name>.
The config>mngmnt>snmp>security-to-
group(<any|snmpv1|snmpv2c|usm>/<security name>)# prompt appears.
2. Enter group-name <group name>.
The current user is linked to the group.
3. Repeat steps 1 and 2 for another user with the same security-to-group
setting.
A user group consisting of two users linked to the same security model
has been created.
 To disable a user group:

• At the config>mngmnt>snmp>security-to-group(<any|snmpv1|snmpv2c|usm>/
<security name>)# prompt, enter shutdown.
The user group is disabled.
 To enable a user group again:

• At the config>mngmnt>snmp>security-to-group(<any|snmpv1|snmpv2c|usm>/
<security name>)# prompt, enter no shutdown.
The user group is enabled.
4.10 Managers
This section explains how to add and remove managers. You can add up to 10
managers.
4-46 Managers Megaplex-4

 To add a manager:
1. At the config# prompt, enter manager.
The config>mngmnt# prompt appears.
2. At the config>mngmnt# prompt, enter manager <0.0.0.0..255.255.255.255>.
The specified manager has been added and the
config>mngmnt>manager <0.0.0.0..255.255.255.255> prompt appears
displaying the IP address of the manager you just added.
 To remove a network manager:

• To delete a manager, in the management context (config>mngmnt), enter no
manager <ip-address>/<ip-mask>
• To delete all managers, enter no manager.
4.11 Management Access

You can enable or disable access to the Megaplex-4 management system via
Telnet, SSH, or SNMP applications for a specific router interface. By disabling
Telnet, SSH, or SNMP, you prevent unauthorized access to the system when
security of the associated IP address has been compromised. When Telnet, SSH,
and SNMP are disabled, Megaplex-4 cannot be managed using the relevant router
interface. If Telnet, SSH and SNMP are disabled for all router interfaces, the unit
can be managed via an ASCII terminal only. In addition, you can limit access to the
device to only the defined management stations.
In addition, Megaplex-4 can use up to four RADIUS servers to facilitate remote
authentication. Introducing a RADIUS server allows configuring up to two
authentication protocols according to a user-configured order. If the first
authentication method is unavailable or the user is not found, the next method is
used.
The table below lists management access implementation, according to the
defined management access and whether network managers are defined.
Megaplex-4 Management Access 4-47

Access Method Mode Allowed to Access Megaplex-4
Network Manager(s) Network Manager(s)

Defined not Defined
Enable Anybody Anybody

Telnet Access
Disable Nobody Nobody

SSH Access (Secure Shell)

SNMP Access
Factory Defaults
By default, access is enabled via Telnet, SSH, and SNMP.
Configuring Access
Follow the instructions below to enable/disable access via Telnet, SSH or SNMP. In
addition, you have to configure the access policy.
 To enable or disable access via management protocols:

2. Configure as illustrated and explained in the table below.
Enabling access via Telnet telnet
Disabling acess via Telnet no telnet
Enabling access via Secure Shell (SSH) ssh
Disabling access via SSH no ssh
Enabling access via SNMP snmp
Disabling access via SNMP no snmp
 To define the access policy:

• At the config>mngmnt>access# prompt, configure the access levels as
illustrated and explained in the table below.
4-48 Management Access Megaplex-4

Specifying authentication auth-policy 1st-level radius [2nd-level If 2nd-level is set to local,

preferably via database {local | none }] authentication is performed via the
stored on RADIUS server, RADIUS server. If the RADIUS server
then optionally local does not answer the authentication
request, then Megaplex-4
authenticates via the local database. If
the RADIUS server rejects the
authentication request, Megaplex-4
ends the authentication process.
If 2nd-level is set to none,
authentication is performed via the
RADIUS server only
4.12 Access Policy

The access policy allows specifying up to three user authentication methods
(local, RADIUS, TACACS+). If an authentication method is not available or the user
is not found, the next method is used if applicable.
Factory Defaults
By default, authentication is via the locally stored database (1st-level local).
Configuring Access Policy

 To define the access policy:
• In the config>mngmnt>access# prompt, enter the necessary commands
according to the tasks listed below.
Megaplex-4 Access Policy 4-49

Specifying authentication method auth-policy 1st-level radius [2nd-level Megaplex-4 first attempts authentication via
preferably via RADIUS/TACACS+, then tacacs+ [3rd-level {local | none}]] the server specified by 1st-level. If the
optionally TACACS+/RADIUS, then auth-policy 1st-level tacacs+ [2nd-level server does not answer the authentication
optionally local radius [3rd-level {local | none}]] request, then Megaplex-4 attempts to
authenticate via the server specified by
2nd-level. If the server does not answer the
authentication request, then Megaplex-4
attempts to authenticate according to
3rd-level:
• local – Megaplex-4 authenticates via the
local database
• none –No further authentication is
done, and the authentication request is
rejected.
Note: If at any time in this process, an
authentication server rejects an
authentication request, Megaplex-4 ends
the authentication process and does not
attempt authentication at the next level.
Specifying authentication method auth-policy 1st-level tacacs+ [2nd-level { If 2nd-level is set to local, authentication is
preferably via TACACS+, then local | none } ] performed via the TACACS server. If the
optionally local TACACS server does not answer the
authentication request, then Megaplex-4
authenticates via the local database. .If the
TACACS server rejects the authentication
request, Megaplex-4 ends the
authentication process.
If 2nd-level is set to none, authentication is
performed via the TACACS server only.
4.13 Authentication via RADIUS Server

Megaplex-4 provides connectivity to up to four Radius authentication servers. You
have to specify access parameters such as assigning Radius server IDs, specifying
the associated server IP addresses and the number of retries.
Standards
RFC 2865, Remote Authentication Dial In User Service (RADIUS).
RFC 2618, RADIUS Authentication Client MIB.
4-50 Authentication via RADIUS Server Megaplex-4

Benefits
The RADIUS protocol allows centralized authentication and access control,
avoiding the need of maintaining a local user database on each device on the
network.
Because of its generic nature, the RADIUS protocol can easily be used by service
providers and enterprises to manage access to the Internet, internal networks,
wireless networks, and integrated e-mail services. These networks may
incorporate DSL, access points, VPNs, network ports etc.
A work station attempts to log on to a Megaplex unit, which in turn submits an
authentication request to the RADIUS server.
The password is not transmitted over the network. A hash code is generated over
it instead and a previously defined shared secret (string of free text) between the
RADIUS server and the Megaplex unit is transmitted.
Verifying credentials and privileges via RADIUS data base
Logon request to Megaplex-4
Network
Logging on to Megaplex-4 or
returning authentication error Megaplex-4
RADIUS Server
Management Work Station Access accepted or denied
Shared Secret
Figure 4-14. RADIUS Server Operation Scheme
The RADIUS server verifies the user information against a database stored at the
RADIUS server. The RADIUS server replies in one of the following ways:
• Access Rejected. Access to all resources denied.
• Access Accepted. Access to the requested network resources granted.
Factory Defaults
Description Default Value
The max number of authentication attempts. 2
Time interval between two authentication attempts. 2 seconds
UDP port used for the authentication channel 1812
Configuring the RADIUS Server

Megaplex-4 provides connectivity to up to four Radius authentication servers. You
have to specify access parameters such as assigning Radius server IDs, specifying
the associated server IP addresses and the number of retries.
Megaplex-4 Authentication via RADIUS Server 4-51

This section explains how to define and configure a RADIUS server, activate and
de-activate it.
 To define a Radius server:

1. At the config>mngmnt# prompt, enter radius.
The config>mngmnt>radius# prompt appears.
2. Enter server <1..4>.
The config>mngmnt>radius>server <1..4># prompt appears.
3. Define the parameters for the relevant Radius server as illustrated and
explained in the table below.
Task Command
Assigning an IP address to the server address <1.1.1.1..255.255.255.255>
Defining a non-disclosed string (shared key <string of free text>

secret) used to encrypt the user password.
Defining the number of authentication retry <0..10>

request attempts
Defining the period of time during which timeout <1..5>

Megaplex-4 waits for a response from the
RADIUS server.
Specifying the UDP port used for the auth-port <1..65535>

authentication channel
Viewing the RADIUS Server Profile Status

This section explains how to display the status of the RADIUS servers.
 To display the RADIUS server profile status:

• At the config>mngmnt>radius# prompt, enter show status.
The status of the four RADIUS server entries appears regardless if they
are configured and enabled or not.
mp4100>config>mngmnt>radius# show status
Server IP Address Access Status
-----------------------------------------------------------------------------
1. 172.17.143.3 Enable Connected
2. 0.0.0.0 Disable Not connected
mp4100>config>mngmnt>radius#
Viewing RADIUS Statistics

This section explains how to display RADIUS sever statistics.
4-52 Authentication via RADIUS Server Megaplex-4

 To display RADIUS statistics:

• At the config>mngmnt>radius# prompt, enter show statistics.
RADIUS statistics appear as illustrated below.
mp4100>config>mngmnt>radius# show statistics
Server1 Server2 Server3 Server4
---------------------------------------------------------------
Access Requests : 0 0 0 0
Access Retransmits : 0 0 0 0
Access Accepts : 0 0 0 0
Access Rejects : 0 0 0 0
Access Challenges : 0 0 0 0
Malformed Response : 0 0 0 0
Bad Authenticators : 0 0 0 0
Pending Requests : 0 0 0 0
Timeouts : 0 0 0 0
Unknown Types : 0 0 0 0
Packets Dropped : 0 0 0 0
4.14 Authentication via TACACS+ Server

TACACS+ (Terminal Access Controller Access Control System Plus) is a security
application that provides access control for routers, network access servers, and
other networked computing devices via one or more centralized servers. TACACS+
provides separate authentication, authorization, and accounting services. It is
used to communicate between the switch and an authentication database.
Because TACACS+ is based on TCP, implementations are typically resilient against
packet loss.
Standards
RFC 1492, An Access Control Protocol, sometimes called TACACS.
Benefits
The TACACS+ protocol allows centralized authentication and access control,
avoiding the need to maintain a local user data base on each device on the
network. The TACACS+ server encrypts the entire body of the packet but leaves a
standard TACACS+ header.
Factory Defaults
By default, no TACACS+ servers are defined. When the TACACS+ server is first
defined, it is configured as shown below.
retry 1
timeout 5 seconds
Megaplex-4 Authentication via TACACS+ Server 4-53

authentication-port 49
accounting-port 49
TACACS+ is a protocol that provides access control for routers, network access
servers and other networked computing devices via one or more centralized
servers. TACACS+ is based on AAA model:
• Authentication – The action of determining who a user is.
• Authorization – The action of determining what a user is allowed to do. It can
be used to customize the service for the particular user.
• Accounting – The action of recording what a user is doing, and/or has done.
The TACACS+ client can be configured to use authentication/authorization with or
without accounting functionality.
Components
The TACACS+ remote access environment has three major components: access
client, TACACS+ client, and TACACS+ server.
• The access client is an entity which seeks the services offered by the
network.
• TACACS+ client running on Megaplex-4, processes the requests from the
access client and pass this data to TACACS+ server for authentication.
• The TACACS+ server authenticates the request, and authorizes services over
the connection. The TACACS+ server does this by matching data from the
TACACS+ client`s request with entries in a trusted database.
TACACS+ server decides whether to accept or reject the user's authentication or
authorization. Based on this response from the TACACS+ server, the TACACS+
client decides whether to establish the user's connection or terminate the user's
connection attempt. The TACACS+ client also sends accounting data to the
TACACS+ server to record in a trusted database.
TACACS+ uses TCP for its transport and encrypts the body of each packet.
TACACS+ client and server can agree to use any port for authentication and
accounting. TACACS+ supports authentication by using a user name and a fixed
password.
Accounting
Megaplex-4 supports up to five accounting groups, with up to five TACACS+
servers per group. However, each TACACS+ server can be bound to a single
accounting group only.
A group can be defined with its own accounting level:
• Shell accounting, which logs the following events:
 Successful logon
4-54 Authentication via TACACS+ Server Megaplex-4

 Logon failure
 Successful logoff
 Megaplex-4-terminated management session.
• System accounting, which records system events/alarms registered in local
log file
• Command accounting, which logs the following events:
 Any shell command that was successfully executed by Megaplex-4
 Any level that was successfully changed in a shell.
Defining TACACS+ Server

Megaplex-4 provides connectivity to up to five TACACS+ authentication servers.
You must specify the associated server IP address, key, number of retries, etc.
 To define TACACS+ server:

1. If you intend to use TACACS+ for authentication, verify that TACACS+ is
selected as level-1 authentication method (see Access Policy).
2. At the config>mngmnt>tacacsplus# prompt, type server <ip-address> to
specify the server IP address.
The config>mngmnt>tacacsplus>server(<ip-address>)# prompt is
displayed.
3. Enter the necessary commands according to the tasks listed below.
Defining a new TACACS+ server server <ip-address> no server deletes a TACACS+

server
Defining a non-disclosed string (shared key <string> [hash] The shared secret is a secret
secret) used to encrypt the user key consisting of free text
password known to the client and the
server for encryption. It is
hashed if specified.
Defining the TCP port to be used for accounting-port Range 1–65535

accounting <tcp-port-number>
Defining the TCP port to be used for authentication-port Range 1–65535

authentication <tcp-port-number>
Binding accounting group to TACACS+ group <string> no group detaches accounting

server group from server
Defining the number of authentication retry <number-of-retries> Permanently set to 1

request attempts
Defining timeout (in seconds) for timeout <seconds> Range 1–10

response from TACACS+ server
Administratively enabling server no shutdown shutdown administratively

disables the server

Displaying statistics show statistics
Clearing statistics clear-statistics
Configuring Accounting Groups

 To configure accounting groups:
1. At the config>mngmnt>tacacsplus# prompt, type group <group-name> to
configure an accounting group with the specified name.
The config>mngmnt>tacacsplus>group(<group-name>)# prompt is
displayed.
2. To define the accounting for the group, enter accounting [shell] [system]
[commands]
Note You can enter any combination of shell, system, and commands, but you must
enter at least one of them.
3. Type exit to return to the TACACS+ level.

The config>mngmnt>tacacsplus# prompt is displayed.
4. Type server <ip-address> to select the TACACS+ server to which to bind the
group.
displayed.
5. At the config>mngmnt>tacacsplus>server(<ip-address>)# prompt, enter
group < group-name> to bind the previously defined accounting group to the
TACACS+ server.
Example – Defining Server

The example below illustrates the procedure for defining a TACACS+ server.
• Server IP address: 175.18.172.150
• Key: TAC_server1.
mp4100# configure management tacacsplus
mp4100>config>mngmnt>tacacsplus# server 175.18.172.150
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)$ key TAC_server1
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)$ no shutdown
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)$ information detail
key "244055BF667B8F89225048C6571135EF" hash
retry 1
timeout 5
accounting-port 49
no group
no shutdown

Example – Defining Accounting Group

The example below illustrates the procedure for defining an accounting group.
• Group name: TAC1
• Accounting: Shell, system, and commands
• Bound to server defined in Example – Defining Server.
mp4100# configure management tacacsplus
mp4100>config>mngmnt>tacacsplus# group TAC1
mp4100>config>mngmnt>tacacsplus>group(TAC1)$ accounting shell system commands
mp4100>config>mngmnt>tacacsplus>group(TAC1)$ info detail
accounting shell system commands
mp4100>config>mngmnt>tacacsplus>group(TAC1)$ exit
mp4100>config>mngmnt>tacacsplus# server 175.18.172.150
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)# group TAC1
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)# info detail
key "244055BF667B8F89829AB8AB0FE50885" hash
retry 1
timeout 5
accounting-port 49
group "TAC1"
no shutdown
 To display TACACS+ statistics:
• At the config>mngmnt>tacacsplus>server <ip-address># prompt, type:
show statistics.
The TACACS+ statistic counters are displayed.
mp4100>config>mngmnt>tacacsplus>server(175.18.172.150)$ show statistics
Requests 0
Request Timeouts 0
Unexpected Responses 0
Server Error Responses 0
Incorrect Responses 0
Transaction Successes 0
Transaction Failures 0
Pending Requests 0
Table 4-9. TACACS+ Statistic Counters
Counter Description
Requests Number of authentications performed toward a specific TACACS+ server
Request Timeouts Number of transaction timeouts that occurred between the client and
server

Counter Description
Unexpected Responses Number of times the TACACS+ client receives a TACACS+ packet that is
not expected at that time. Usually, this occurs due to a delayed response
to a request that has already timed out
Server Error Responses Number of errors received from the TACACS+ server
Incorrect Responses Number of times the TACACS+ client:

• Fails to decrypt the packet
• Detects an invalid field in the TACACS+ packet
• Receives a response that is not valid according to the initial request
Transaction Successes Number of successful transactions between the client and TACACS+
server
Transaction Failures Number of times the TACACS+ client’s request is aborted by the TACACS+
server or the server fails to respond after maximum retry is exceeded
Pending Requests Number of TACACS+ client’s requests minus number of TACACS+ server
responses or timeouts
 To clear TACACS+ statistics:

• At the config>mngmnt>tacacsplus>server <ip-address># prompt, type clear
statistics.
TACACS+ statistic counters are set to 0.
Defining Accounting Groups

 To define an accounting group:
1. At the config>mngmnt>tacacsplus# prompt, type group <string> to create an
accounting group.
The config>mngmnt>tacacsplus>group(string)# prompt is displayed.
3. At the config>mngmnt>tacacsplus# prompt, type server ip-address to display
previously defined TACACS+ server.
displayed.
4. At the config>mngmnt>tacacsplus>server(ip-address)# prompt, enter group
<string> to bind a previously defined accounting group to the TACACS+
server.
Creating an accounting group group no group deletes accounting

group

Enabling TACACS+ accounting for the accounting [shell] [system] Accounting can be of any
group [commands] combination
no accounting disables
TACACS+ accounting for the
group
4.15 IEEE 802.1X - Port-based Network Access

Control
IEEE 802.1X is an IEEE Standard for Port-based Network Access Control (PNAC). It
provides an authentication mechanism to devices wishing to attach to
a LAN or WLAN. IEEE 802.1X defines the encapsulation of the Extensible
Authentication Protocol (EAP) over IEEE 802 which is known as "EAP over LAN" or
EAPOL.
The host that is seeking access to the network is known as the Supplicant, and
the system providing the point of access to the network is the Authenticator.
Authenticator role can be configured for CL.2/A GbE ports, physical Ethernet ports
of M-ETH and VS modules. The supplicant role is supported by CL.2/A GbE ports.
Authenticator and supplicant cannot be enabled on the same port at the same
time.
IEEE 802.1X access control is not supported on the ports configured for HSR, LAG
or ERP protection.
Standards
IEEE 802.1X
Benefits
Secured access to the customer network.
Factory Defaults
The parameter defaults are listed in the table below.
Parameter Description Default Value
authenticator
quiet-period Configuring quiet period after authentication failure (sec) 60
re-authentication-period Configuring reauthentication period (sec) 3600
max-authentication Configuring the maximum number of authentication 2

attempts
Megaplex-4 IEEE 802.1X - Port-based Network Access Control 4-59

tx-period Configuring the time to wait before retransmitting EAP 30

frame (sec)
max-frame-tx Configure the maximum number of EAP frame 2

retransmissions
supplicant
held-period Configuring held period after authentication failure (sec) 60
max-authentication Configuring the maximum number of authentication 2

attempts
tx-period Configuring the time to wait before retransmitting EAP 30

frame (sec)
max-frame-tx Configure the maximum number of EAP frame 2

retransmissions
Components
802.1X authentication involves three parties: a supplicant, an authenticator, and
an authentication server.
• The supplicant is a client device that wishes to attach to the LAN.
• The authenticator is a network device, such as an Ethernet switch or wireless
access point.
• The authentication server is typically a host running software supporting
the RADIUS and EAP protocols.
The authenticator acts like a security guard to a protected network. The
supplicant (i.e. the client device) is not allowed access through the authenticator
to the protected side of the network until the supplicant’s identity has been
validated and authorized.
With 802.1X port-based authentication, the supplicant provides credentials, such
as user name/password, to the authenticator, and the authenticator forwards the
credentials to the authentication server for verification. If the authentication
server determines the credentials are valid, the supplicant (client device) is
allowed to access resources located on the protected side of the network.
EAPOL operates at the network layer on top of the data link layer, and
in Ethernet II framing protocol has an EtherType value of 0x888E.
4-60 IEEE 802.1X - Port-based Network Access Control Megaplex-4

Authentication (Radius Message)

EAP Negotiation
Authentication Algorithm
Supplicant: Authenticator: Radius Message
ETH CL-A/1 M-ETH/VS-ETH EAP – Success/Failure
Radius Frames
Authentication
EAPOL Frames Radius Server
Initiation: PSN
EAPOL Request/Response
Megaplex-4 Megaplex-4
RV EMS
Server
Figure 4-15. Network Access Control
Typical Authentication Progression

Initialization. On detection of a new supplicant, the port on the switch
(authenticator) is enabled and set to the "unauthorized" state. In this state, only
802.1X traffic is allowed; other traffic, such as the Internet Protocol (and with
that TCP and UDP), is dropped.
Initiation. To initiate authentication, the authenticator will periodically transmit
EAP-Request Identity frames to a special Layer 2 address on the local network
segment. The supplicant listens on this address, and on receipt of the EAP-
Request Identity frame it responds with an EAP-Response Identity frame
containing an identifier for the supplicant such as a User ID. The authenticator
then encapsulates this Identity response in a RADIUS Access-Request packet and
forwards it on to the authentication server. The supplicant may also initiate or
restart authentication by sending an EAPOL-Start frame to the authenticator,
which will then reply with an EAP-Request Identity frame.
Negotiation. The authentication server sends a reply (encapsulated in a RADIUS
Access-Challenge packet) to the authenticator, containing an EAP Request
specifying the EAP Method (the type of EAP based authentication it wishes the
supplicant to perform). The authenticator encapsulates the EAP Request in an
EAPOL frame and transmits it to the supplicant. At this point the supplicant can
start using the requested EAP Method, or do an NAK ("Negative
Acknowledgement") and respond with the EAP Methods it is willing to perform.
Authentication. If the authentication server and the supplicant agree on an EAP
Method, EAP Requests and Responses are sent between the supplicant and the
authentication server (translated by the authenticator) until the authentication
server responds with either an EAP-Success message (encapsulated in a RADIUS
Access-Accept packet), or an EAP-Failure message (encapsulated in a RADIUS
Access-Reject packet). If authentication is successful, the authenticator sets the
port to the "Authenticated" status and normal traffic is allowed. If it is
unsuccessful the port remains in the "Unauthenticated" status. When the
supplicant logs off, it sends an EAPOL-logoff message to the authenticator, the
authenticator then sets the port to the "Unauthenticated" status, once again
blocking all non-EAP traffic.

Configuring 802.1X Access Control

To configure 802.1X access control, you must first enable it on the system level
and then configure it for all authenticator and supplicant ports.
 To enable 802.1X on the system level:

1. Navigate to the config>system>dot1x# prompt and enter the necessary
commands according to the tasks listed below.
Enabling 802.1X access-control no access-control disables 802.1X

access control
 To configure 802.1X on the port level:

1. At the config>port>ethernet <slot>/<port># prompt, type dot1x command.
The config>port>ethernet(<slot>/<port>)dot1x# prompt is displayed.
Reinitializing 802.1X initialize
Enabling authenticator role authenticator-enable no authenticator-enable

disables authenticator role
Enabling supplicant role supplicant-enable no supplicant-enable disables

supplicant role
Displaying 802.1X status show status
Displaying 802.1X statistics show statistics
Authenticator configuration level (see authenticator

below)
Supplicant configuration level (see supplicant

below)
The following commands are available in the autenticator level, at the config>
port ethernet (<slot><port>)dot1x>authenticator# prompt.
Enabling periodic re-authentication-periodic re-authentication-periodic disables

reauthentication periodic reauthentication
Configuring quiet period after quiet-period <0 – 65535>

authentication failure (sec)
Configuring reauthentication re-authentication-period <0 –

period (sec) 65535>

Configuring the maximum max-authentication <1 –

number of authentication 65535>
attempts
Configuring the time to wait tx-period <1 – 65535>

before retransmitting EAP frame
(sec)
Configuring the maximum max-frame-tx <1 – 10>

number of EAP frame
retransmissions
The following commands are available in the supplicant level, at the config> port
ethernet(<slot><port>) dot1x > supplicant# prompt.
Configuring held period after held-period <0 – 65535>

authentication failure (sec)
Configuring the maximum max-authentication <1 –

number of authentication 65535>
attempts
Configuring RADIUS username radius-credentials username no radius-credentials cancels the

and password <name 1-244 characters> current RADIUS username and
password <password 1-244 password
characters>
Configuring the time to wait tx-period <1 – 65535>

before retransmitting EAP frame
(sec)
Configure the maximum number max-frame-tx <1 – 10>

of EAP frame retransmissions
Note
In order for 802.1x access control to function properly, the relevant Ethernet
ports must be associated with an L2CP profile that specifies peer action for MAC
01-80-C2-00-00-03.
Example
The example below illustrates the 802.1X protocol operation.
• Authenticators: ports of M-ETH module installed in MP 1 slot 2
• Supplicant: CL-A/1 port of MP 2
• All the authenticator/supplicant parameters are at their defaults.
############# MP-Authenticator M-ETH Vs. MP - Supplicant ########
####### using Radius EAP Authentication method = EAP-MDS #####
#############################################################################

############ 1st script MP-Authenticator M-ETH port #########################

#############################################################################
#######################IP-Address and Card_Types ################

configure router 1 interface 1 address 172.18.92.254/24
configure router 1 static-route 0.0.0.0/0 address 172.18.92.1
exit all
configure slot cl-a card-type cl cl2-622gbea

configure slot 2 card-type eth meth
############## Define radius client servers ############################
config management radius
server 1
address 172.18.92.219
auth-port 1812
key ALPHA
no shutdown
exit all
############## Enable l2cp for 802.1x on ethernet port ###################
configure port l2cp-profile L2cpDefaultProfile mac 01-80-C2-00-00-03 peer
############## Enable 802.1x on all ethernet ports ###################
configure system dot1x access-control

configure port ethernet 2/1 dot1x authenticator-enable
configure port ethernet 2/1 l2cp profile L2cpDefaultProfile








configure port ethernet 2/1 no shutdown

conf port ethernet cl-a/1 no shutdown

conf bridge 1 port 1 no shutdown
conf bridge 1 vlan-aware
conf bridge 1
vlan 100
tagged-egress 1,3,21,22,23,24,25,26,27,28
exit all
configure qos
queue-group-profile qg1
queue-block 1/1
exit
queue-block 0/1
bind queue 0 queue-block 1/1
exit all
configure port ethernet 2/1 queue-group profile qg1

conf flows classifier-profile all match-any match all

conf flows classifier-profile mng match-any match vlan 100
conf flows classifier-profile traffic match-any match vlan 50
conf flows flow mng3 classifier all

conf flows flow mng3 ingress-port svi 1
conf flows flow mng3 egress-port bridge-port 1 1
conf flows flow mng3 vlan-tag push vlan 100 p-bit fixed 7
conf flows flow mng3 no shutdown

conf flows flow mng4 classifier mng

conf flows flow mng4 ingress-port bridge-port 1 1
conf flows flow mng4 egress-port svi 1
conf flows flow mng4 vlan-tag pop vlan

conf flows flow mng21 ingress-port ethernet 2/1
conf flows flow mng21 reverse-direction queue 0 block 0/1








conf flows flow TRAF classifier traffic

conf flows flow TRAF ingress-port ethernet 2/1
conf flows flow TRAF egress-port ethernet cl-a/1
conf flows flow TRAF reverse-direction queue 0 block 0/1
conf flows flow TRAF no shutdown
commit
#############################################################################
############2nd script MP-Supplicant cl-a/1 #port ########################
#############################################################################
conf slot cl-a card-type cl cl2-622gbea

configure slot 1 card-type versatile vs-12
conf router 1 interface 1 address 172.18.92.251/24

conf router 1 static-route 0.0.0.0/0 address 172.18.92.1
exit all
############## Enable l2cp for 802.1x on ethernet port ###################
configure port l2cp-profile L2cpDefaultProfile mac 01-80-C2-00-00-03 peer
############## Enable 802.1x on all ethernet ports ###################
configure system dot1x access-control
configure port ethernet cl-a/1 no shutdown

configure port ethernet cl-a/1 l2cp profile L2cpDefaultProfile
configure port ethernet cl-a/1 dot1x supplicant-enable
configure port ethernet cl-a/1 dot1x supplicant
radius-credentials user-name HU password 4321
exit all
configure qos
queue-group-profile qg1
queue-block 1/1
exit
queue-block 0/1
exit all
conf port ethernet cl-a/1 queue-group profile qg1

conf port ethernet cl-a/1 no shutdown
conf port ethernet 1/1 no shutdown


conf bridge 1 vlan-aware
conf bridge 1
vlan 100
tagged-egress 1,2
exit all
conf flows classifier-profile all match-any match all

conf flows classifier-profile v100 match-any match vlan 100
conf flows classifier-profile traffic match-any match vlan 50
conf flows flow MNG classifier all

conf flows flow MNG ingress-port ethernet cl-a/1
conf flows flow MNG egress-port bridge-port 1 1
conf flows flow MNG vlan-tag push vlan 100 p-bit fixed 7
conf flows flow MNG reverse-direction queue 0 block 0/1
conf flows flow MNG no shutdown
conf flows flow mng_1 classifier all

conf flows flow mng_1 ingress-port svi 1
conf flows flow mng_1 egress-port bridge-port 1 2
conf flows flow mng_1 vlan-tag push vlan 100 p-bit fixed 7
conf flows flow mng_1 no shutdown
conf flows flow mng_2 classifier v100

conf flows flow mng_2 ingress-port bridge-port 1 2
conf flows flow mng_2 egress-port svi 1
conf flows flow mng_2 vlan-tag pop vlan
conf flows flow mng_2 no shutdown
conf flows flow TRAF classifier traffic

conf flows flow TRAF ingress-port ethernet 1/1
conf flows flow TRAF egress-port ethernet cl-a/1
conf flows flow TRAF reverse-direction queue 0 block 0/1
conf flows flow TRAF no shutdown
commit
 To display 802.1X statistics:
1. Navigate to configure port ethernet <slot>/<port> dot1x context.
2. Type: show statistics.
The 802.1X statistic counters are displayed.

EAPOL Rx Frames Statistics

-----------------------------------------------------------------------------
Rx Invalid Frames : 0
Rx Length Error Frames : 0
Rx Unavailable Frames : 0
Rx Start Frames : 0
Rx Frames : 33
Rx Logoff Frames : 0
Rx Last Version Frames : 3
Rx Last Source Frames : 00-01-C1-00-00-02
EAPOL Tx Frames Statistics

-----------------------------------------------------------------------------
Tx Supp Frames : 22
Tx Logoff Frames : 0
Tx Start Frames : 20
Tx Auth Frames : 0
Tx MKA Frames : 0
Table 4-10. 802.1X Statistic Counters
Counter Description
Rx Frames Number of EAPOL-EAP frames received
Rx Start Frames Number of EAPOL-Start frames received
Rx Logoff Frames Number of EAPOL- Logoff frames received
Rx Announcement Frames Number of EAPOL-Announcement frames received
Rx Announcement Req Frames Number of EAPOL-Announcement-Req frames received
Rx Invalid Frames Number of invalid EAPOL frames received
Rx Length Error Frames Number of EAPOL frames with wrong length received
Rx Unavailable Frames Number of EAPOL frames discarded due to unavailable virtual port
Last Rx Frame Version Version of last received EAPOL frame
Last Rx Frame Source Source MAC address of last received EAPOL frame
Tx Auth Frames Number of EAPOL-EAP frames transmitted by the authenticator
Tx Supp Frames Number of EAPOL-EAP frames transmitted by the supplicant
Tx Start Frames Number of EAPOL-Start frames transmitted
Tx Logoff Frames Number of EAPOL-Logoff frames transmitted
Viewing the 802.1X Status

This section explains how to display the status of the 802.1X protocol operation.
 To display 802.1X status:

1. Navigate to configure port ethernet <slot>/<port> dot1x.
2. Type show statistics.
The 802.1X status is displayed.

mp4100>config>port>eth(2/1)>dot1x# show status

Role : Authenticator
Connect Status : Authenticated
The status display provides information about:
• Role of the 802.1x port:
 Authenticator
 Supplicant
• Port status:
 Pending
 Unauthenticated
 Authenticated.
 To display the version information:

• At the config>system>dot1x# prompt, enter version-information.
The supported versions of EAPOL protocol and MKA protocols are
displayed.
Note MKA protocol will be implemented in the future version.
mp4100# show configure system dot1x version-information

EAPoL version : 3
MKA version : 0
4.16 Syslog
Megaplex-4 uses the Syslog protocol to generate and transport event notification
messages over IP networks to Syslog servers.
Standards and MIBs

RFC 3164, RFC 5674.
Benefits
The Syslog protocol collects heterogeneous data into a single data repository. It
provides system administrators with a single point of management for collecting,
distributing and processing audit data. Syslog standardizes log file formats,
making it easier to examine log data with various standard tools. Data logging can
be used for:
• Long-term auditing
• Intrusion detection
• Tracking user and administrator activity
4-70 Syslog Megaplex-4

• Product operation management.
Factory Defaults
By default, Syslog operation is disabled. When enabled, the default parameters
are as follows:
facility local1
port 514
severity-level informational
The Syslog protocol provides an instrument for generating and transporting event
notification messages from Megaplex-4 to the server across IP networks.
Mess
ages
Megaplex-4100
PSN
Syslog
Server
ages
Mess
Megaplex-4100
Figure 4-16. Syslog Functionality
Elements
A typical Syslog topology includes message senders (devices) and message
receivers (servers). Megaplex-4 supports up to 5 Syslog servers. The receiver
displays, stores or forwards logged information. The standard designates two
types of receivers:
• Relay, which forwards messages
• Collector which displays and stores messages.
Transport Protocol
Syslog uses User Datagram Protocol (UDP) for its transport. The UDP port that
has been assigned to Syslog is 514, but devices and servers can agree to use any
port for communication.
Message Format
The length of a Syslog message is 1024 bytes or less. It contains the following
information:
• Facility and severity (see below)
• Host name or IP address of the device
Megaplex-4 Syslog 4-71

• Timestamp
• Message content.
A typical Syslog message looks like this: <145>Jan 15 13:24:07 172.17.160.69
Eth 1: Loss of signal (LOS)
Facilities and Severities

Facility designates a device or application that sends a message. The standard
includes some pre-defined facilities in the 0–15 range. Megaplex-4 uses facilities
local1–7 for originator identification.
Severity is assigned to a message to specify its importance. Megaplex-4 uses the
following severity designations:
Table 4-11. Syslog Severities
Code Syslog Type Description
0 Emergency Emergency message, not in use
1 Alert Critical alarm
2 Critical Major alarm
3 Error Minor alarm
4 Warning Event
5 Notice Cleared alarm
6 Informational Informational message, not in use
7 Debug Debug-level messages, not in use
Syslog Configuration
When configuring Syslog parameters, it is necessary to define Syslog device and
servers.
 To configure a Syslog device:

1. Navigate to the syslog device context (config>system>syslog device).
The config>system>syslog(device)# prompt is displayed.
Defining a facility from which facility {local1 | local2 | local3 |

Syslog messages are sent local4 | local5 | local6 | local7}
Defining Syslog device UDP port port <udp-port-number> Range 1–65535

for communication Port configuration is allowed only if a
Syslog device is administratively
disabled

Defining severity level severity-level { emergency | alert | The log messages that contain
critical | error | warning | notice | severity level above or equal the
informational | debug} specified level are transmitted
Administratively enabling Syslog no shutdown shutdown administratively disables

device Syslog device
Displaying statistics show statistics
An example below illustrates procedure for defining a Syslog device.

• Facility: local2
• UDP port: 155
• Severity level: major.
mp-4100# configure system syslog device
mp-4100>config>system>syslog(device)#
mp-4100>config>system>syslog(device)# facility local2
mp-4100>config>system>syslog(device)# port 155
mp-4100>config>system>syslog(device)# severity-level critical
mp-4100>config>system>syslog(device)# no shutdown
 To display Syslog statistics:

2. At the config>system>syslog(device)# prompt, enter show statistics.
Syslog statistics appear as shown in Figure 4-17. The counters are
described in Table 4-12.
mp-4100>config>system>syslog(device)# show statistics
Total Tx Messages : 356
Non-queued Dropped Messages : 265
Figure 4-17. Syslog Statistics
Table 4-12. Syslog Statistic Parameters
Parameter Description
Total Tx Messages The total number of Syslog messages transmitted
Non-queued Dropped The total number of Syslog messages that were

Messages dropped before being queued
 To clear Syslog statistics:

2. At the config>system>syslog(device)# prompt, enter clear-statistics.
Megaplex-4 Syslog 4-73

The Syslog statistic counters are set to 0.
 To define a Syslog server:

1. Navigate to system context (config>system).
The config>system# prompt is displayed.
2. At the config>system# prompt, enter server <server-ID> to specify server to
receive Syslog messages, from 1 to 5.
The config>system>syslog(server/1–5)# prompt is displayed.
Defining Syslog server IP address

<0.0.0.0–255.255.255.255>
Defining Syslog server UDP port for port <udp-port-number> Range 1–65535
communication Port configuration is allowed
only if a Syslog server is
administratively disabled
Administratively enabling Syslog server no shutdown shutdown administratively

disables Syslog server
For example:
• Server IP address: 178.16.173.152
• UDP port: 155
mp-4100# configure system syslog server 1
mp-4100>config>system>syslog(server/1)#
mp-4100>config>system>syslog(server/1)# address 178.16.173.152
mp-4100>config>system>syslog(server/1)# port 155
mp-4100>config>system>syslog(server/1)# no shutdown

Chapter 5
Services
This chapter presents information on the service elements and services provided
by Megaplex-4.
5.1 Service Elements

This section details the managed elements that need to be configured during
service provisioning.
Service provisioning elements are as follows:
• Profiles
• Physical ports (User Ethernet, SHDSL, E1, T1, T3, Voice, Serial, Mux-Eth-Tdm
(fiber optic links of Optimux modules), DS1-opt (fiber optic links of VS-6/C37
modules), SDH/SONET, Teleprotection and VS-6/BIN CMD CHANNEL, CMD-IN,
CMD-OUT ports)
• Logical ports (PCS, HDLC, MLPPP, PPP, BRI, Serial Bundle, Logical MAC, VCG,
GFP, SVI, Internal DS1, PW, LAG, LRE, Teleprotection CMD-IN-I and CMD-OUT-I)
• Forwarding entities (flow, bridge, router).
Profiles
Most traffic processing features are defined by creating and applying various
profiles. Profiles comprise sets of attributes related to a specific service entity.
Profiles must be defined prior to other managed objects.
Table 5-1. Profile Types
Profile Type Applied to Description Scale per Chassis
Classifier Flow Defines criteria for flow classification 128
Shaper Queue, queue block Defines CIR, CBS, EIR and EBS 30
parameter
WRED Queue Defines green and yellow packet 8

thresholds and drop probabilities
Queue block Queue block within Defines queue block parameters 128
queue group (queues, scheduling scheme,
weights)
Megaplex-4 Service Elements 5-1

Chapter 5 Services Installation and Operation Manual
Profile Type Applied to Description Scale per Chassis
Queue group Port Defines level-0 and -1 scheduling 15

elements and structures within
queue group
L2CP Port, flow Defines actions for L2CP processing 6

(drop, peer, tunnel)
Policer Flow Define CIR, CBS, EIR and EBS 60

parameters
Marking Flow Defines method of mapping CoS and 12

packet color values into P-bit
Signaling E1/T1 ports Specifies translation rules for 5

signaling information
VC GFP, HDLC, E1, E1-I, Defines the handling of SDH/SONET 64

AUG, T1, T1-I, OC3 (VC/VT/STS) traffic
ports
Analog Signaling Voice ports Specifies translation rules for 8

signaling information
Scheduling and Shaping Entities

Megaplex-4 schedules traffic using the following hierarchical scheduling entities:
• Queue – a lowest-level scheduling element. Its priority can be strict or weight
fair. Queues have shaper and WRED profiles assigned to them.
• Queue block (also referred to as scheduling element, or SE) – a mid-level
scheduling element that consists of several queues. Queue blocks are created
by associating queues with queue block profiles. There are two levels of
queue blocks for CL GbE ports and one level for other Ethernet ports. Queue
blocks have shaper profiles assigned to them.
• Queue group – a top-level scheduling element that consists of several queue
blocks. Queue groups are created by associating queue group profile to ports.
Megaplex-4 provides the following shaping tools:
• Dual leaky bucket shaper (CIR/EIR)
• Single leaky bucket shaper (CIR).
Congestion is avoided by using the WRED mechanism.
Physical Ports
Services provided by Megaplex-4100/4104 are based on its physical ports. These
ports are located on the following modules (which can sometimes be
interchangeable in providing specific services):
• SDH/SONET –CL.2
• GbE – CL.2, M-ETH
5-2 Service Elements Megaplex-4

Installation and Operation Manual Chapter 5 Services
• Fast Ethernet – OP-108C, OP-34C, ASMi-54C/N, ASMi-54C, MPW-1, M8E1,

M8T1, M8SL, VS
• SHDSL – ASMi-54C/N, ASMi-54C, M8SL
• E1 – OP-108C, OP-34C, ASMi-54C/N, M8E1, M16E1, VS-16E1T1-EoP
• T1 – M8T1, M16T1, VS-16E1T1-EoP
• T3 – T3
• Voice – VC-4/VC-8/VC-4A/VC-8A/VC-16, VC-4/OMNI, VC-6/LB, VS Voice family
• Serial – HS-6N/12N, HS-U-6/12, HS-S, HS-RN, HSF-2, LS-6N/12, VS family
• Mux-Eth-Tdm (Optimux fiber optic links) – OP-108C, OP-34C
• DS1-Opt (VS fiber optic links) – VS-6/C37
• CMD CHANNEL, CMD-IN, CMD-OUT – TP (Teleprotection), VS-6/BIN
Logical Ports
Logical ports maintained by Megaplex-4 do not have physical port attributes and
serve different purposes, depending on the module and on the service provided
by the module/system physical ports. The following logical ports exist:
• Switched Virtual Interface (SVI) located on CL.2 modules and used for binding
flows to bridge ports, router interfaces or Layer-2 TDM pseudowires. SVIs
serve as intermediaries for bridges and routers, which must comply with
standards of their own (VLAN domains for bridge ports or IP address for
router interfaces) and. They also serve as aggregation points for TDM PWs
• VCG, GFP and HDLC ports located on CL.2 modules and used for efficient
transport of Ethernet traffic over the SDH/SONET network. GFP and HDLC
ports are mapped either directly to the physical layer or to VCG. In the latter
case, the binding is done in two stages and the VCG is further bound to the
physical layer.
• VCG and GFP ports located on T3 modules and used for efficient transport of
Ethernet traffic over the T1/T3 networks. GFP ports are mapped either
directly to the physical layer or to VCG. In the latter case, the binding is done
in two stages and the VCG is further bound to the physical layer.
• VCG and GFP ports located on VS-16E1T1-EoP modules and used for efficient
transport of Ethernet traffic over the E1/T1 networks. VCG ports are bound
directly to GFP.
• HDLC, MLPPP and PPP ports used for efficient transport of Ethernet traffic
over E1/T1. HDLC ports defined on located on M8E1, M8T1 and M8SL
modules and are bound to the physical layer. MLPPP and PPP ports exist only
on M8E1 and M8SL modules; PPP ports are bound to the physical layer,
serving an intermediary to MLPPP ports. MLPPP and HDLC ports are connected
to Ethernet media via Logical MAC ports.
• Logical MAC ports located on CL.2, T3, VS-16E1T1-EoP and M8E1/M8T1/M8SL
modules used to describe and map the Ethernet traffic passing over different
media (E1/T1, T3, SDH/SONET, etc) and representing the MAC layer of the
entity. Logical MAC ports are bound to a GFP, HDLC or MLPPP ports, which, in
its turn, are bound to the physical layer.
Megaplex-4 Service Elements 5-3

• PCS (Physical Coding Sublayer) ports located on the ASMi-54C/N, ASMI-54C

and SH-16 modules, which determine the Ethernet (packet) physical layer
transmission capabilities over SHDSL lines
• BRI ports located on HSU-6, HSU-12 and HS-S I/O modules and used to
provide ISDN services.
• The serial bundle ports located on LS-6N, LS-12 modules and used to form
single/dual composite data stream, serving as intermediaries to bind serial
ports to either of the Megaplex uplink ports
• Internal DS1 Ports located on MPW-1 and VS modules and used to connect
between pseudowires and serial ports.
• CMD-IN-I and CMD-OUT-I ports located on Teleprotection module and used to
manipulate the logical Rx/Tx information over the corresponding CMD
CHANNEL
• PW ports located on MPW-1 and VS modules.
Forwarding Entities
Several internal entities carry traffic and make forwarding and switching
decisions. These are:
• Flows – the main traffic-carrying elements
• Bridge – traffic-forwarding element for Layer-2 E-LAN services
• Router – traffic-forwarding element for Layer-3 services.
Flows
Flows interconnect two physical or logical ports and are the main traffic-carrying
elements in Megaplex-4 architecture. You can use classifier profiles to specify the
criteria for flows. The classification is per port and is applied to the ingress port
of the flow.
Flows defined in Megaplex-4100/4104 can be unidirectional (between
physical/logical ports) or bidirectional (between physical/logic ports and brigde
ports of CL modules).
Note Bridge ports in M-ETH modules are bound directly (without using flows).
Flow processing is performed as follows:

• Ingress traffic is mapped in flows using classification match criteria defined
via classification profile.
• L2CP frames are handled per flow according to L2CP profile settings.
• User priority (P-bit, IP Precedence, DSCP) is mapped into internal Class of
Service (CoS) according to assignment per flow.
• User priority (P-bit, IP Precedence, DSCP) can be mapped into packet color
(yellow or green) according to assignment per flow.
• VLANs can be edited per flow by stacking (pushing), removing (popping), or
swapping (marking) tags on single-, or double-tagged packets. P-bit values
are either copied or set according to CoS marking profile.
5-4 Service Elements Megaplex-4

• A single policer can be applied to a flow, using policer profile.

• A flow is mapped to a specific queue block within a queue group associated
with egress port.
Bridge
The bridge is a forwarding entity used by Megaplex-4 for delivering E-LAN services
in multipoint-to-multipoint topology and G.8032 ring protection. With up to 11
bridge instances, Megaplex-4 provides up to 170 bridge ports, subdivided as
follows:
• 80 ports on the CL.2 bridge
• 9 ports per M-ETH module bridge (8 external + 1 internal) – maximum 90
ports per chassis.
The bridge uses bridge ports for connecting to logical and physical ports.
The bridge is defined by a bridge number, bridge ports and a VLAN membership
table that specifies which bridge ports are members in a certain broadcast
domain (VLAN). The bridge supports one level of VLAN editing on ingress and one
level on egress. The editing is performed at the flow level.
Router
The Megaplex-4 router is an internal Layer-3 interworking device that forwards
traffic between its interfaces. Each router interface is assigned an IP address and
can be bound to one of the following:
• Physical/logical E1/T1/DS1-opt (via DTS) or SDH/SONET (via DCC) port
• SVI port connected via flow to a bridge port (which provides access to any
Ethernet-type physical/logical port)
The router uses switched virtual interfaces (SVIs) for connecting to logical and
physical ports. The connection is always made by directing flows from a port to
an SVI, and then binding the SVI to a router interface.
5.2 Services Provided by Megaplex-4

Both carriers and transportation and utility services providers can benefit from
Megaplex-4 capabilities. The services for carriers and service providers (TDM
and/or ETH grooming) are as follows.
Carrier and utility services provided by Megaplex-4 include:
• Aggregation Services:
 TDM (E1/T1) service aggregation over copper/fiber lines into SDH/SONET
backbone
 TDM (E1/T1) service aggregation over copper/fiber lines into PSN
backbone
 TDM (E1/T1) and Ethernet service aggregation over copper/fiber lines into
SDH/SONET backbone
Megaplex-4 Services Provided by Megaplex-4 5-5

SDH/SONET and PSN backbone (TDM to TDM, Ethernet to PSN)
PSN backbone
 Ethernet service aggregation over copper/fiber lines into PSN.
 Voice aggregation to T3 backbones.
• Cross-connect services:
 Legacy (Voice, serial, ISDN) services cross-connect for interbranch
connectivity
 Multiplexing any traffic (Legacy/TDM/Ethernet) for cross-connect services.
 T3 traffic to SONET (via T1 x-connect).
Transportation and utility services provided by Megaplex-4 include:
• TDM- and Ethernet service aggregation to SDH/SONET backbones
• Legacy and new Ethernet-based service aggregation to SDH/SONET and PSN
backbones (keeping mission-critical services towards the TDM backbone)
• Legacy and new Ethernet-based service aggregation to PSN backbones
• Resilient ring topology for legacy and Ethernet services with minimal
downtime
• Teleprotection over SDH/SONET.
Selected services from the above list are summarized in Table 5-2 and schematic
diagrams in Figure 5-1 to Figure 5-7. Modules shown in diagrams as examples are
listed in Table 5-2 in bold. If you want to draw a diagram for a specific service
provided by another module, you can use the relevant elements of sample
services to draw a service of your own.
Table 5-2. Selected Services Provided by Megaplex-4
No Description I/O Modules Providing Schematic Configuration

the Service Diagram Procedure
1a TDM (E1) service aggregation over copper OP-108C, OP-34C, Figure 5-1 Figure 5-13
lines into SDH/SONET backbone (via direct ASMi-54C/N, M16E1, Table 5-3
transparent mapping) M16T1, VS-16E1T1-EoP
1b TDM (E1/T1) service aggregation over OP-108C, OP-34C, Figure 5-1 Figure 5-14
copper lines into SDH/SONET backbone ASMi-54C/N, M8E1, M8T1, Table 5-4
(via DS0 mapping) M16E1, M16T1, VS-
16E1T1-EoP
2a TDM (E1/T1) service aggregation over OP-108C, OP-34C Figure 5-1 Figure 5-15
fiber lines into PSN backbone Table 5-5
2b Ethernet service aggregation over fiber OP-108C, OP-34C, Figure 5-1 Figure 5-16
lines into PSN backbone ASMi-54C/N, ASMi-54C, Table 5-6
MPW-1, M8E1, M8T1, M8SL
5-6 Services Provided by Megaplex-4 Megaplex-4


3 Fast Ethernet service aggregation to OP-108C, OP-34C, Figure 5-2 Figure 5-17
SDH/SONET backbones ASMi-54C/N, ASMi-54C, Table 5-7
MPW-1, M8E1, M8T1,
M16E1, M16T1
3a TDM (E1) service aggregation over copper ASMi-54C/N Figure 5-2 Figure 5-19
lines into PSN backbone Table 5-9
3b Ethernet service aggregation over copper ASMi-54C/N, ASMi-54C Figure 5-2 Figure 5-20
lines into PSN backbone Table 5-10
3c Shared E-LAN service with multiple drops M-ETH Figure 5-3 Figure 5-18
per node over SDH/SONET Table 5-8
4 High-Speed service aggregation to HS-6N/12N Figure 5-4 Figure 5-21

SDH/SONET backbones Table 5-11
4a High-Speed service aggregation to Fast HS-6N/12N + MPW-1 Figure 5-4 Figure 5-22
Ethernet Table 5-12
4b High-Speed service aggregation into PSN HS-6N/12N + MPW-1 Figure 5-4 Figure 5-22
backbone Table 5-12
4c High-Speed service aggregation into PSN HS-6N/12N, MPW-1 Figure 5-5 Figure 5-24
backbone with G.8032 protection Table 5-14
4d High-Speed service aggregation to Fast VS Figure 5-6 Figure 5-22

Ethernet (low-latency) Table 5-12
4e High-Speed service aggregation into PSN VS Figure 5-6 Figure 5-24

backbone (low-latency) Table 5-14
5a Fast Ethernet service aggregation to M8E1, M8T1, M8SL Figure 5-7 Figure 5-25
E1/T1 links Table 5-15
5b Fast Ethernet service aggregation to M8E1, M8SL Figure 5-7 Figure 5-26
multiple E1 links Table 5-16
6 Voice aggregation to SDH/SONET VC-4/VC-8/ VC-4A/ Figure 5-7 Figure 5-27

backbones VC-8A/VC-16, VC-4/OMNI, Table 5-17
6a Voice service aggregation into PSN VS Voice Figure 5-8 Figure 5-28
backbone Table 5-18
7 Teleprotection over SDH/SONET TP Figure 5-9 Figure 5-29

Table 5-19
8 Voice aggregation to T3 backbones T3 Figure 5-10 Figure 5-30

VC-4/VC-8/ VC-4A/ Table 5-20
VC-8A/VC-16, VC-4/OMNI,
VS Voice


9 T3 traffic to SONET T3 Figure 5-11 Figure 5-31

Table 5-21
10a Ethernet traffic over PDH to SDH/SONET VS-16E1T1-EoP Figure 5-12 Figure 5-32
Table 5-22
10b Ethernet traffic over PDH to TDM (E1/T1) VS-16E1T1-EoP Figure 5-12 Figure 5-33
Table 5-23
The following figures schematically describe selected services provided by

Megaplex-4.
M8E1/T1
M16E1/T1, VS-16E1T1-EoP
OR E1
1a
CL.2 TP
1b
SDH/ SDH/SONET SDH/SONET DS0

SONET E1-i/T1-i Voice
Link X-Connect X-Connect
HS-12N
ETH
VCAT GFP L.MAC
Engine
OP-108C
2a
E1i E1
Mux-ETH-
TDM
Int- ETH
PSN GbE 2b
ETH
ETH
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via ASMi-54C/N
direct transparent mapping)
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via DS0
mapping)
Ethernet service aggregation over fiber lines into PSN backbone MPW-1
TDM (E1/T1) service aggregation over fiber lines into PSN backbone
Figure 5-1. Services 1, 1a, 2a, 2b

M8E1/T1
M16E1/T1
Voice
CL.2
SDH/ SDH/SONET SDH/SONET DS0 HS-12N

E1-i/T1-i
SONET Link X-Connect X-Connect
3a
TP
ETH
VCAT GFP L.MAC
Engine
ASMi-54C/N
3
E1i E1
SHDSL
PCS ETH
PSN GbE
3b
ETH
OP-108C
Fast Ethernet service aggregation to SDH/SONET backbones
TDM (E1) service aggregation over copper lines into PSN backbone
Ethernet service aggregation over copper lines into PSN backbone MPW-1
Figure 5-2. Services 3, 3a, 3b
M8E1/T1
M16E1/T1
CL.2 VC-4/4A/8/8A/16
VC-4/OMNI

E1-i/T1-i
HS-12N
L.MAC
M-ETH
ETH ETH
VCAT GFP L.MAC Engine Engine
3c
GbE
PSN
ASMi-54C/N
OP-108C
Shared E-LAN service with multiple drops per node over SDH/SONET
MPW-1
Figure 5-3. Service 3c

M8E1/T1
M16E1/T1
Voice
CL.2
TP
E1-i/T1-i
SONET Link X-Connect X-Connect 4
Serial
ETH HS-12N
VCAT GFP L.MAC
Engine
4b ASMi-54C/N
PSN GbE 4a
OP-108C
PW
Router SVI
MPW-1
DS1
PW
X-Connect
High-Speed service aggregation to SDH/SONET backbones PW
High-Speed service aggregation to Fast Ethernet
High-Speed service aggregation into PSN backbone ETH
Figure 5-4. Services 4, 4a, 4b

M8E1/T1
M16E1/T1
Voice
CL.2
TP
E1-i/T1-i
Serial
ETH HS-12N
VCAT GFP L.MAC
Engine
East 4c ASMi-54C/N
GbE
PSN
West
GbE
OP-108C
PW
Router SVI
MPW-1
DS1
PW
X-Connect
PW
High-Speed service aggregation into PSN backbone

with G.8032 protection ETH
Figure 5-5. Service 4c
E1/T1
Voice
CL.2
TP
E1-i/T1-i
Serial
4f ASMi-54C/N
ETH
VCAT GFP L.MAC
Engine
OP-108C
PSN GbE
VS
PW Serial
Router SVI
4d
DS1
PW
X-Connect
High-Speed service aggregation to SDH/SONET backbones 4e
PW
High-Speed service aggregation to Fast Ethernet
High-Speed service aggregation into PSN backbone ETH
Figure 5-6. Services 4d, 4e, 4f

M8E1/T1
5a
HDLC E1/T1
ETH L.MAC
CL.2
VC-4/4A/8/8A/16, VC-4/OMNI
VS voice
SDH/SONET SDH/SONET DS0
SDH/ E1-i/T1-i Voice
SONET 6
M8E1
5b
PPP E1
ETH MLPPP
VCAT GFP L.MAC
Engine
ETH L.MAC
GbE
PSN
TP
M16E1/T1
Fast Ethernet service aggregation to E1/T1 links

Fast Ethernet service aggregation to multiple E1 links HS-12N
Voice aggregation to SDH/SONET backbones
ASMi-54C/N
MPW-1
Figure 5-7. Services 5a, 5b, 6
CL.2

E1-i/T1-i
ETH
VCAT GFP L.MAC
Engine
6a
GbE VS Voice
PSN
Voice
PW
Router SVI
DS1
1/1
PW
X-Connect
PW
1/1
DS1/PW 1:1
Voice service aggregation into PSN backbone
Figure 5-8. Service 6a

M8E1/T1
Voice
CL.2
SDH/ SDH/SONET SDH/SONET DS0 CMD-IN-I CMD-IN

E1-i/T1-i CMD
Channel
7 CMD-OUT-I CMD-OUT
TP
ETH M16E1/T1
VCAT GFP L.MAC
Engine
HS-12N
GbE
PSN
ASMi-54C/N
MPW-1
Teleprotection Traffic over SDH/SONET
Figure 5-9. Service 7
M8E1/T1
T3
8
T1 T3
CL.2
SDH/SONET TP
SONET SONET Link
X-Connect
M16E1/T1
ETH
VCAT GFP L.MAC
Engine HS-12N
GbE ASMi-54C/N
PSN
MPW-1
T3 Module CL.2
VC-4/4A/8/8A/16, VC-4/OMNI,
VS voice
T3 DS0
T1 Voice
T3 Link X-Connect
9
T3 to SONET
Voice aggregation to T3 backbones
Figure 5-10. Services 8,9

M8E1/T1
M16E1/T1, VS-16E1T1-EoP
OR E1
1a
CL.2 TP
1b

SONET E1-i/T1-i Voice
HS-12N
ETH
VCAT GFP L.MAC
Engine
OP-108C
2a
E1i E1
Mux-ETH-
TDM
Int- ETH
PSN GbE 2b
ETH
ETH
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via ASMi-54C/N
direct transparent mapping)
TDM (E1/T1) service aggregation over copper lines into SDH/SONET backbone (via DS0
mapping)
Ethernet service aggregation over fiber lines into PSN backbone MPW-1
TDM (E1/T1) service aggregation over fiber lines into PSN backbone
Figure 5-11. Services 8,9
VS-16E1T1-EoP
CL.2
10b
10a
SDH/ SDH/SONET SDH/SONET E1i E1
SONET Link X-Connect
GFP VCG
L.MAC
VCAT GFP L.MAC ETH

Engine
M-ETH
PSN GbE ETH

Engine
Ethernet Traffic over PDH to SDH/SONET
Ethernet Traffic over PDH to TDM(E1/T1)
Figure 5-12. Services 10a,10b

Sections 5.3 to 5.21 summarize the steps required to configure selected services
shown in the above diagrams. For further details on a configuration step, refer to
the corresponding section indicated in the service provisioning table.
Note • Applications in the following diagrams may be implemented in a different way;

Sections 5.3 to 5.21 just show typical service elements.
• The diagrams below display all possible protection alternatives. In most cases
there is no need to configure all of them and it is recommended to select the
one most suitable for your application.
5.3 E1/T1 Traffic to SDH/SONET via Direct

Transparent Mapping (1a)
Figure 5-13 illustrates an E1/T1 to SDH/SONET service via direct transparent
mapping. This service is used for unframed E1/T1 ports of all I/O modules except
M8E1/M8T1. Table 5-3 details configuration steps needed for service
provisioning.
Megaplex-4 E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a) 5-15
1. Define profiles vc profile
VC-12/VT1.5 E1/T1 I/O Module,

SDH/SONET Link
E1/T1 Port
Configure I/O
Configure link
card e1/t1 port
Set sdh-sonet link

parameters
Assign vc profile
2. Configure ports
for each aug/oc-3
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
4. Configure Configure aps Configure vc-path

protection protection protection
Legend:
Mandatory
Optional
Figure 5-13. E1/T1 to SDH/SONET Service via Direct Transparent Mapping
5-16 E1/T1 Traffic to SDH/SONET via Direct Transparent Mapping (1a) Megaplex-4
Table 5-3. E1/T1 to SDH/SONET Service Provisioning – Direct Transparent Mapping
Sequence Step Commands Comments
VC Profiles port vc-profile Configuring VC Profiles (to be assigned to

1. Define
profiles
E1-i/T1-i and AUG/OC-3 ports)
E1 Ports port {e1 | t1} Configuring physical E1/T1 ports of I/O module
2. Configure
T1 Ports
physical
ports
SDH/SONET Ports port sdh-sonet Configuring physical SDH/SONET ports

Selecting aug/oc3 group
Assigning vc profile to aug/oc3
SDH/SONET cross-connect sdh-sonet Cross-connecting between E1-i/T1-i ports and

3. Configure
connections
Cross-Connect VC-12/VT1.5 containers (CL.2 module)

cross-
Path Protection protection vc-path Protecting SDH/SONET payload units

3. Configure
protection
for SDH/SONET
Payload
APS Protection protection aps Protecting SDH/SONET links
5.4 E1/T1 Traffic to SDH/SONET via DS0

Cross-Connect (1b)
Figure 5-14 illustrates an E1/T1 to SDH/SONET service via DS0 cross-connect. This
service is used for framed E1/T1 ports of all I/O modules and for unframed ports
of M8E1/M8T1 modules (M8E1/M8T1 do not support direct transparent mapping).
Table 5-4 details configuration steps needed for service provisioning.
Megaplex-4 E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b) 5-17

signaling
profile
VC-12/VT1.5 E1/T1 CL.2 Module, E1/T1 I/O Module,

SDH/SONET Link
E1-i/T1-i Ports E1/T1 Port
Configure
e1-i/t1-i Configure I/O
Configure link
parameters card serial port
Set sdh-sonet Set e1-i/t1-i port

link parameters parameters
Assign vc profile
2. Configure ports for each aug/oc-3 Assign vc profile
3. Configure
cross-connect
Configure Configure DS0

sdh-sonet cross-connect
cross-connect
4. Configure Configure aps Configure tdm-

protection protection group protection
Legend:
Mandatory
Optional
Figure 5-14. E1/T1 to SDH/SONET Service via DS0 Mapping
Table 5-4. E1/T1 to SDH/SONET Service Provisioning

1. Define profiles
Signaling Profiles port signaling-profile Configuring signaling profiles (to be assigned

to E1/T1 ports – M8E1/M8T1 modules only)
E1 Ports port {e1 | t1} Configuring physical E1/T1 ports of I/O module
T1 Ports
2. Configure physical
and logical ports
E1 Ports port { e1-i | t1-i} Configuring physical parameters of E1-i/T1-i

T1 Ports ports (CL.2 module)
Assigning vc profile

5-18 E1/T1 Traffic to SDH/SONET via DS0 Cross-Connect (1b) Megaplex-4

3. Configure cross- DS0 Cross- cross-connect ds0 Cross-connecting between E1/T1 port of
connections Connect M16E1/M16T1 module and e1-i/t1-i port of
CL.2 module
SDH/SONET cross-connect sdh-sonet Cross-connecting between E1-i/T1-i ports and

Cross-Connect VC-12/VT1.5 containers (CL.2 module)
TDM Group protection tdm-group Protecting E1/T1 service

4. Configure
protection
Protection
5.5 E1 Traffic to SDH over Fiber via Direct

Transparent Mapping (2a)
Figure 5-15 illustrates an E1 to SDH over fiber service. This example is done via
direct transparent mapping since E1 links are framed. For unframed links you
must use DS0 cross-connect (as shown in Figure 5-1 and Figure 5-14 for M16E1).
Megaplex-4 E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a) 5-19
OP-108C
VC-12 E1 OP-108C
Module,
SDH Link Module, Optimux-108
MUX-ETH-TDM
E1-i Port
Port
Configure E1-i Configure Configure E1 and

Configure link
port mux-eth-tdm Fiber Optic ports
port
Set sdh link
parameters
2. Configure Assign vc profile

ports for each aug
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect

Legend:
Mandatory
Optional
Figure 5-15. E1 to SDH over Fiber Service via Direct Transparent Mapping
Table 5-5. E1 to SDH over Fiber Service Provisioning
VC Profiles port vc-profile Configuring VC Profiles (to be assigned to E1-i

1. Define
profiles
and AUG ports)
E1 Ports port e1 (<slot>/<port>/ Configuring E1-i ports of I/O module

<tributary>)
and logical ports
Mux-Eth-Tdm port mux-eth-tdm Configuring Mux-Eth-Tdm ports of I/O module

Ports (Fiber Optic
Links of Optimux
Modules)
SDH/SONET Ports port sdh-sonet Configuring physical SDH ports

Selecting aug group
Assigning vc profile to aug
5-20 E1 Traffic to SDH over Fiber via Direct Transparent Mapping (2a) Megaplex-4
SDH/SONET cross-connect sdh-sonet Cross-connecting between E1 ports

Cross-Connect (<slot>/<port>/<tributary>) and VC-12
containers (CL.2 module)
Path Protection protection vc-path Protecting SDH payload units

4. Configure
protection
for SDH/SONET
Payload
APS Protection protection aps Protecting SDH links
5.6 Fast Ethernet Traffic to PSN over Fiber (2b)

Figure 5-16 illustrates a Fast Ethernet to PSN over fiber service. Table 5-6 details
configuration steps needed for service provisioning.
classifier policer
1. Define profiles
profile profile
Flow 1a OP-108C OP-108C Module,

CL.2 Module,
GbE Port Flow 1b Module, MUX-ETH-TDM Optimux-108
Int-Eth Port Port
Configure GbE Configure int-eth Configure Configure

port port mux-eth-tdm Ethernet and
port Fiber Optic ports
Set Ethernet
port parameters
Set Mux-Eth-Tdm
port parameters
2. Configure ports
Assign policer
profile for remote
Optimux-108
Configure flow Configure flow

1a 1b
Assign Assign
ingress and ingress and
3. Configure flows egress ports egress ports
Assign Assign
classifier classifier
profile profile
Define vlan Define vlan
editing editing
actions actions
Legend:
Mandatory
Optional
Figure 5-16. Fast Ethernet to PSN over Fiber Service
Megaplex-4 Fast Ethernet Traffic to PSN over Fiber (2b) 5-21

Table 5-6. Fast Ethernet to PSN over Fiber Service Provisioning
Policer Profiles qos policer-profile Configuring policer profiles (to be assigned to

1. Define
profiles
remote Optimux Ethernet ports)
Classifier Profiles flows classifier-profile Define classification profile for traffic

originating from I/O port
Mux-Eth-Tdm port mux-eth-tdm Configuring fiber optic ports of I/O module

Ports (Fiber Optic and some remote device parameters (for
Links of Optimux example, assigning policer profile)
and logical ports
Modules)
User Ethernet port ethernet Defining internal Ethernet ports of I/O module
Ports <slot>/<port>/<tributary>
User Ethernet port ethernet Configuring physical GbE ports on the CL.2
Ports <slot>/<port> module
Assigning policer profile
Flows flows>flow Define flow 1a:

• egress port – GbE port of CL.2 module
• ingress port – internal Ethernet port of
OP-108C module
Assign classifier profile
Define required VLAN editing actions:
•
4. Configure flows
match-all
• push vlan <x>
• p-bit fixed
Define flow 1b:

• ingress port – GbE port of CL.2 module
• egress port – internal Ethernet port of OP-
108C module
• match vlan <x>
• pop
5.7 Fast Ethernet Traffic to SDH/SONET (3)

Figure 5-17 illustrates a Fast Ethernet to SDH/SONET service. This service is
shown in Figure 5-2 on the example of ASMi-54C/N module. Table 5-7 details
5-22 Fast Ethernet Traffic to SDH/SONET (3) Megaplex-4

1. Define profiles Classifier

VC profile Policer profile
profile
Flow 1a
VC-12/VT1.5 I/O Module,
Logical Flow 1b
SDH/SONET Link VCG Port GFP Port Fast Ethernet
MAC
Port
Configure VCG Configure GFP Define logical Configure

Configure link port port mac port and Ethernet port
bind gfp port
Set sdh-sonet Set vcg port Set gfp port Set Ethernet
link parameters parameters parameters port parameters
Assign vc Assign vc Assign policer
Bind vcg port
profile for each profile profile
aug/oc-3
Bind vc/vt Assign vc
2. Configure ports
profile

1a 1b
3. Configure flows
Assign Assign
egress ports egress ports
Assign Assign
profile profile
editing editing
actions actions
Configure
Configure aps Configure vc-
4. Configure protection ethernet-group
protection path protection
protection
Legend:
Mandatory
Optional
Figure 5-17. Fast Ethernet to SDH/SONET Service
Table 5-7. Fast Ethernet to SDH/SONET Service Provisioning
VC Profiles port vc-profile Configuring VC profiles (to be assigned to gfp,

1. Define profiles
vcg and aug/oc3 ports)

Ethernet ports)

originating from I/O port.
Fast Ethernet Ports port ethernet Configuring physical Ethernet ports of I/O
module
Logical MAC Ports port logical-mac Defining logical MAC port to establish
and logical ports
connectivity between gfp and fast ethernet

ports.
GFP Ports port gfp Configuring physical parameters of GFP port

Binding the corresponding VCG to the GFP port
When Ethernet service contains a single

VC-3/STS-1 or VC-12/VT1.5 container, the GFP
port can be bound to it directly
Megaplex-4 Fast Ethernet Traffic to SDH/SONET (3) 5-23

VCG Ports port vcg Configuring physical parameters of VCG port

Binding the corresponding VC-4/STS-3c,

VC-3/STS-1 or VC-12/VT1.5 to the VCG

Flows flows>flow Define unaware flows over EoS with n x

VC-12/VT1.5 and SP VLAN:
Define flow 1:
• ingress port – I/O card ethernet port
• egress port – logical-mac
Bind classifier profile
3. Configure flows
• match-all
• push vlan <x>
• p-bit fixed
Define flow 2:
• ingress port –logical-mac,
• egress port – I/O card port ethernet
• match vlan <x>
• pop
Ethernet Group protection ethernet- Protecting Ethernet and packet traffic against
4. Configure
Protection group transmission failures on the SDH/SONET links

protection
Path Protection for protection vc-path Protecting SDH/SONET payload units

SDH/SONET Payload
5.8 Shared E-LAN Service with Multiple Drops per

Node over SDH/SONET
Figure 5-18 illustrates a shared E-LAN service with multiple drops per node over
SDH/SONET, schematically shown in Figure 5-3. Table 5-8 details configuration
steps needed for service provisioning.
5-24 Shared E-LAN Service with Multiple Drops per Node over SDH/SONET Megaplex-4
WRED Shaper
Queue
VC profile
Queue block
1. Define profiles
Classifier Queue group
Marking
CL Bridge (1)
Flows
1a, 1b Bind
Flow 3 M-ETH
Logical BP Bridge BP
SDH/SONET Link VCG Port GFP Port Logical
SDH/SONET Link VC-12/VT1.5 VCG Port GFP Port MAC M-ETH Module,
MAC BP BP GbE Ports
Bind
Flow 2 ERP
BP BP
Configure VCG Configure GFP Define logical
Configure link port port mac port and
2. Configure ports bind gfp port
Set sdh-sonet Set vcg port Set gfp port
link parameters parameters parameters Bind queue Configure
Assign vc Assign vc group profile Ethernet port
Bind vcg port
profile for each profile
aug/oc-3 Set Ethernet
Bind vc/vt Assign vc port parameters
profile
Define a bridge Define a bridge
Define bridge Define bridge

ports ports
3. Configure bridge and ERP Bind to M-ETH

Ethernet port
Configure VLAN
Configure ERP
membership
Define ERP Define VLANs
Configure bridge
Configure East ports as VLAN
and West ports members
Configure RPL Configure MAC
owner table size
Configure flows Configure flows

4. Configure flows 2,3 1a, 1b
Bind ingress and Assign ingress

egress ports and egress ports
Bind classifier Assign classifier

profile profile
Bind queue Define vlan

Legend: mapping profile editing actions
Mandatory
Bind queue
Optional block instance
Figure 5-18. Shared E-LAN Service with Multiple Drops per Node over
SDH/SONET
Table 5-8. Shared E-LAN over SDH/SONET Service Provisioning

1. Define profiles
Classifier Profiles classifier-profile Define classification profiles for Flows 1a, 1b

and bidirectional Flows 2 and 3.
Flows 1a, 1b:
• Use “match all” setting
• Push/pop Data VLAN of the ERP.
Flows 2 and 3: use “match all” setting.
Data VLAN is part of ERP definition.
Megaplex-4 Shared E-LAN Service with Multiple Drops per Node over SDH/SONET 5-25
Priority Queue queue-map-profile Define profile for mapping CoS values to

Mapping queues.
Congestion wred-profile Define WRED profiles to be attached to queue

Avoidance (WRED) profiles
Shaper shaper-profile Define shaper profiles to be attached to a

queue and queue group profiles
Queue Block queue-block-profile Define queue block profiles to be attached to

queue group profiles
Queue Group queue-group-profile Define queue group profile for GbE CL ports
Marking marking-profile Define profile for conversion of CoS and packet

color values into P-bit when push or mark tag
editing is used
Ethernet Ports port ethernet Configure physical parameters of GbE port

(M-ETH module)
Logical MAC Ports port logical-mac Define logical MAC ports to establish
connectivity between gfp ports of CL module
and bp ports of CL Bridge (1).
Bind the queue group profile intended for
Flows 2, 3 to Logical Mac port
GFP Ports port gfp Configure physical parameters of GFP port

Assign vc profile
and logical ports
Bind the corresponding VCG to the GFP port
When Ethernet service contains a single

VC-3/STS-1 or VC-12/VT1.5 container, the GFP
port can be bound to it directly
VCG Ports port vcg Configure physical parameters of VCG port

Assign vc profile
Bind the corresponding VC-4/STS-3c, VC-3/STS-

1 or VC-12/VT1.5 to the VCG
SDH/SONET Ports port sdh-sonet Configure physical SDH/SONET ports

Select aug/oc3 group
Assign vc profile to aug/oc3
Bridge bridge Define, assign a number and configure bridge

entities:
3. Define
bridge
• M-ETH bridge (aware or unaware)

• CL bridge (always aware) with VLAN table
where the Data VLAN of ERP is configured
with proper bridge ports
5-26 Shared E-LAN Service with Multiple Drops per Node over SDH/SONET Megaplex-4
4. Define Bridge bridge Define bridge ports

bridge
ports
M-ETH Bridge: Bind to M-ETH GbE ports
Bridge bridge Add VLANs, define bridge ports as VLAN

membership
5. Configure
members and specify MAC table size for each

VLAN
VLAN
Bridge protection Define ERP, configure RPL owner, configure

6. Configure
East and West ports

ERP
Flows flows>flow Define the following flows:

• Flow 1a: ingress – BP (CL), egress –
BP (M-ETH)
• Flow 1b: ingress – BP (M-ETH), egress –
7. Configure flows
BP (CL)
• Flows 2,3: ingress – Logical Mac, egress –
BP
Define VLAN editing actions
Bind classifier profiles to all flows
Bind queue mapping profile to flows 2,3
Bind queue block instance to flows 2,3
Bind marking profile to flows 2, 3
5.9 E1 to SDH Traffic over Copper via DS0

Mapping (3a)
Figure 5-19 illustrates an E1 to SDH over copper service. This example is done via
DS0 mapping since E1 links are framed. Note that for unframed links you can use
direct transparent mapping as shown in Figure 5-4 and Figure 5-14 for M16E1.
Megaplex-4 E1 to SDH Traffic over Copper via DS0 Mapping (3a) 5-27
VC-12 E1 CL.2 Module, E1 I/O Module, I/O Module,

SDH Link ASMi Modem
E1-i Ports E1-i Port SHDSL Port
Configure
Configure E1-i Configure SHDSL Configure E1 and
Configure link e1-i parameters
port port SHDSL ports
Set sdh link Set e1-i port

parameters parameters
2. Configure Assign vc profile

Assign vc profile
ports for each aug
3. Configure
cross-connect
Configure Configure DS0

sdh-sonet cross-connect
cross-connect
4. Configure Configure aps Configure vc-path Configure

protection protection protection tdm-group
protection
Legend:
Mandatory
Optional
Figure 5-19. E1 to SDH over Copper Service via DS0 Mapping
Table 5-9. E1 to SDH over Copper Service Provisioning
VC Profiles port vc-profile Configuring VC Profiles (to be assigned to E1-i

1. Define
profiles
and AUG ports)
E1 Ports port e1-i Configuring E1-i ports of I/O module

SHDSL Ports port shdsl Configuring SHDSL ports of I/O module

and logical ports
E1 Ports port e1-i Configuring E1-i ports (CL.2 module)

SDH/SONET Ports port sdh-sonet Configuring physical SDH ports

Selecting aug group
Assigning vc profile to aug
DS0 Cross- cross-connect ds0 Cross-connecting between E1-i port of

Configu
cross-
re
3.
Connect ASMi-54C/N module and E1-i port of CL.2

module
5-28 E1 to SDH Traffic over Copper via DS0 Mapping (3a) Megaplex-4
SDH/SONET cross-connect sdh-sonet Cross-connecting between E1-i ports and

Cross-Connect VC-12 containers (CL.2 module)
TDM Group protection tdm-group Protecting E1 service

Protection
4. Configure
protection
Path Protection protection vc-path Protecting SDH payload units

for SDH/SONET
Payload
APS Protection protection aps Protecting SDH links
5.10 Fast Ethernet Traffic to PSN over Copper (3b)

Figure 5-20 illustrates a Fast Ethernet to PSN over copper service. Table 5-10
details configuration steps needed for service provisioning.
classifier policer
1. Define profiles
profile profile
Flow 1a
CL.2 Module, I/O Module, I/O Module,
Flow 1b ASMi Modem
GbE Port PCS Port SHDSL Port
Configure Configure
Configure GbE Define PCS port
SHDSL port Ethernet and
port and bind it to
SHDSL ports
SHDSL port
Set Ethernet
port parameters
2. Configure ports

1a 1b
Assign Assign
3. Configure flows egress ports egress ports
Assign Assign
profile profile
editing editing
actions actions
Legend:
Mandatory
Optional
Figure 5-20. Fast Ethernet to PSN over Copper Service
Megaplex-4 Fast Ethernet Traffic to PSN over Copper (3b) 5-29

Table 5-10. Fast Ethernet to PSN over Copper Service Provisioning

1. Define
profiles
originating from I/O port
SHDSL Ports port shdsl Configuring SHDSL ports of I/O module

and logical ports
2. Configure
physical
PCS Ports port pcs Configuring PCS ports of I/O module and
binding an SHDSL port to it
User Ethernet port ethernet Configuring physical GbE ports on the CL.2
Ports module
Flows flows>flow Define flow 1a:

• egress port – GbE port of CL.2 module
• ingress port – PCS port of ASMi module
•
4. Configure flows
match-all
• push vlan <x>
• p-bit fixed
Define flow 1b:

• ingress port – GbE port of CL.2 module
• egress port – PCS port of ASMi module
• match vlan <x>
• pop
5.11 High-Speed Traffic to SDH/SONET (4)

Figure 5-21 illustrates a high-speed to SDH/SONET service. Table 5-11 details
5-30 High-Speed Traffic to SDH/SONET (4) Megaplex-4

VC-12/VT1.5 E1/T1 CL.2 Module, Timeslots n*64 I/O Module,

SDH/SONET Link
E1-i/T1-i Ports Serial Port
Configure Configure I/O

Configure link
e1-i/t1-i parameters card serial port
Set sdh-sonet Set e1-i/t1-i

link parameters port parameters
Assign vc profile Assign vc profile

2. Configure ports
for each aug/oc-3
3. Configure cross
connect
Configure Configure ds0

sdh-sonet cross cross connect
connect

protection Configure tdm-
Legend:
Mandatory
Optional
Figure 5-21. High-Speed to SDH/SONET Service
Megaplex-4 High-Speed Traffic to SDH/SONET (4) 5-31

Table 5-11. High-Speed to SDH/SONET Service Provisioning
VC Profiles port vc-profile Configuring VC Profiles (to be assigned to E1-

1. Define
profiles
i/T1-i and AUG/OC-3 ports)
Serial Ports port serial Configuring physical serial ports of I/O module
and logical ports


DS0 cross-connect cross-connect ds0 Cross-connecting between serial ports of high-

3. Configure timeslot
cross-connections
speed module and timeslots of e1-i/t1-i ports

of CL.2 module
SDH/SONET cross-connect sdh-sonet Cross-connecting between timeslots of

cross-connect E1-i/T1-i ports and VC-12/VT1.5 containers
(CL.2 module)

Protection
3. Configure
protection

for SDH/SONET
Payload
5.12 High-Speed Traffic to PSN (4a, 4b)

Figure 5-22 illustrates in detail high-speed to PSN (Ethernet) services
schematically shown in Figure 5-4:
• Service 4a: The traffic from serial port is forwarded to Ethernet port, which
serves as a pseudowire exit port toward the PSN.
• Service 4b: The traffic from serial port is forwarded to GbE port, which serves
as a pseudowire exit port toward the PSN.
These services use the pseudowire engine of the MPW-1 module. Table 5-12
5-32 High-Speed Traffic to PSN (4a, 4b) Megaplex-4

1. Define profiles classifier policer

profile profile
Flow 1a MPW-1 Module, TS x 64 kbps I/O Module,

MPW-1/FE Port or PW
CL.2/GbE port Flow 1b SVI RIF PW DS1 Ports Serial Port
Router
Configure Configure ds1 Configure I/O

ethernet port port card serial port
Set Ethernet
port parameters
Assign policer
2. Configure ports
profile
Define SVI port
3. Define SVI
Define RIFs
4. Define and bind Define router

router interfaces interfaces
Bind router
interfaces to
SVIs
Add static
routing table Define remote
5. Define PW peer PW peer
Add and configure

6. Add a pseudowire
a pseudowire
7. Configure Configure pw-tdm Configure ds0

cross-connections cross-connect cross-connect

1a 1b
Assign Assign
8. Configure flows ingress and ingress and
Assign Assign
profile profile
editing editing
actions actions
9. Configure
group protection
Legend:
Mandatory
Optional
Figure 5-22. High-Speed to Ethernet Service
Megaplex-4 High-Speed Traffic to PSN (4a, 4b) 5-33

Table 5-12. High-Speed to Fast Ethernet Service Provisioning
Defining Classifier flows flow classifier- Create classifier profile “match-all”

1. Define profiles
Profiles profile

Fast Ethernet ports)
Serial Ports port serial Configuring physical parameters of serial ports

of I/O module
and logical ports
DS1 Ports port ds1 Configuring physical parameters of DS1 ports

(MPW-1 module)
Ethernet Ports port ethernet Configuring physical parameters of Fast

Ethernet port (MPW-1 module, Service 4a) or
GbE port (CL.2 module, Service 4b)
Switched Virtual port svi Define an SVI port.

3. Define SVIs
Interface Keep in mind that PW SVI represents untagged

traffic termination point. This means that VLAN
tags must be pushed on exiting it and popped
on the flows terminating at SVI.
Pseudowire Router router (2) Add interfaces to the router

4. Add RIFs and
bind them to
Define static routing table

SVIs
Bind the RIFs to the SVIs
Peer peer Configure remote pseudowire peer

5. Define PW peer
Pseudowires pwe Add and configure pseudowires

pseudowire
6. Define
5-34 High-Speed Traffic to PSN (4a, 4b) Megaplex-4

DS0 Cross-connect cross-connect ds0 Cross-connecting between serial ports of

high-speed module and timeslots of DS1 ports
of MPW-1 module
7. Configure cross-connections
PW-TDM cross-connect pw-tdm Cross-connecting between timeslots of DS1

Cross-connect ports and PW (MPW-1 module)
Flows flows>flow Define two flows:

8. Configure flows
• Flow 1a: ingress – SVI, egress – Ethernet

port of MPW-1 module
• Flow 1b: ingress – Ethernet port of MPW-1
module, egress –SVI
Assign classifier profile to flows 1a and 1b

9. Configure
protection
Protection
5.13 Low-Latency High-Speed Traffic to PSN (4c,

4d)
Figure 5-23 illustrates in detail low-latency high-speed to PSN (Ethernet) services
using the pseudowire engine of RAD’s versatile VS modules, schematically shown
in Figure 5-6:
• Service 4d: The traffic from serial port is forwarded to Ethernet port, which
• Service 4e: The traffic from serial port is forwarded to GbE port, which serves
The VS modules providing these services have two advantages over the legacy
modules:
• No additional MPW-1 module is needed to perform cross-connect
• The cross-connect is latency-optimized due to the absence of additional ds0
cross-connect in the middle.
Megaplex-4 Low-Latency High-Speed Traffic to PSN (4c, 4d) 5-35

However, cross-connection of multiple ports has to be done via ds0 ports.

Service 4f shown in Figure 5-6 is the same as Service 4 in Figure 5-4.
profile profile
CL.2/GbE or Flow 1a TS x 64 kbps VS Module,

any FE PW VS Module,
Flow 1b SVI RIF Serial Port
port Router PW

ethernet port card serial port
Set Ethernet
port parameters
Assign policer
2. Configure ports
profile
Define SVI port
3. Define SVI
Define RIFs

Bind router
interfaces to
SVIs
Add static
Add and configure

6. Add a pseudowire
a pseudowire
7. Configure Configure pw-tdm

cross-connections cross-connect

1a 1b
Assign Assign
Assign Assign
profile profile
editing editing
actions actions
9. Configure
protection Configure pw-
tdm protection
Legend:
Mandatory
Optional
Figure 5-23. Low-Latency High-Speed to Ethernet Service
5-36 Low-Latency High-Speed Traffic to PSN (4c, 4d) Megaplex-4

Table 5-13. Low-Latency High-Speed to Fast Ethernet Service Provisioning

1. Define profiles
Profiles profile

Serial Ports port serial Configuring physical parameters of serial ports

and logical ports
2. Configure
of I/O module
physical
Ethernet Ports port ethernet Configuring physical parameters of Fast

Ethernet port (Service 4d) or GbE port (CL.2
module, Service 4e)

3. Define SVIs


4. Add RIFs and
bind them to

SVIs

5. Define PW peer

pseudowire
6. Define
PW-TDM cross-connect pw-tdm Cross-connecting between serial ports of

cross-connections
Cross-connect high-speed module and PW

7. Configure
Megaplex-4 Low-Latency High-Speed Traffic to PSN (4c, 4d) 5-37

8. Configure flows Flows flows>flow Define two flows:

• Flow 1a: ingress – SVI, egress – Fast
Ethernet port of I/O module
• Flow 1b: ingress – Ethernet port of I/0
PW Protection protection pw Protecting PW service

9. Configure
protection
5.14 High-Speed Service Aggregation into PSN

Backbone with G.8032 Protection
Figure 5-24 illustrates in detail high-speed service aggregation into PSN backbone
with G.8032 protection (schematically shown in Figure 5-5). In this application,
the traffic from serial port is forwarded to GbE port, which serves as a
pseudowire exit port toward the PSN.
These services use the pseudowire engine of the MPW-1 module. Table 5-14
5-38 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection Megaplex-4
WRED Shaper
Queue
Queue block Shaper
L2CP Classifier Queue group
1. Define profiles
Policer Marking
Flow 3 Flows
CL.2/GbE port 1a, 1b
BP Bridge PW TS x 64 kbps
SVI RIF PW MPW-1 Module, I/O Module,
BP Router DS1 Ports Serial Port
CL.2/GbE port Flow 2
ERP
BP
Configure
ethernet port Configure ds1 Configure I/O
port card serial port
Configure
physical layer
Define
2. Configure ports classifier
(“match-all”)
Bind L2CP
profile
Bind queue
group profile
3. Define SVI Define SVI port
Define RIFs
4. Define and bind router interfaces
Define router
interfaces
Bind router
interfaces to
SVIs
Add static
routing table
Define remote
Add and configure

6. Add a pseudowire
a pseudowire
Configure pw-tdm Configure ds0

7. Configure cross-connections cross-connect
cross-connect
8. Define a bridge Define a bridge
9. Define bridge ports Define bridge ports
Configure VLAN
Configure ERP
membership
10. Configure VLAN membership and ERP

Define ERP Define VLANs
Configure East Configure bridge

and West ports ports as VLAN
members
Configure RPL Configure MAC
owner table size
Configure flows 2,3 Configure flow 1
Bind ingress and Bind ingress and

12. Configure flows
Bind L2CP Bind classifier
profile profile
Bind classifier Define VLAN

profile editing actions
Bind policer
profile
Legend: Bind queue
Mandatory mapping profile
Optional
Bind queue
block instance
Figure 5-24. High-Speed Service Aggregation into PSN Backbone with G.8032
Protection
Megaplex-4 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection 5-39
Table 5-14. High-Speed Service Aggregation into PSN Backbone with G.8032 Protection
Classifier Profiles classifier-profile Define classification profiles for Flows 1a, 1b

and Flows 2 and 3). Use “match all” setting for
1. Define profiles
Flows 1a, 2 and 3. For Flow 1b, define classifier

for the VLAN pushed in Flow 1a.
Policing policer-profile Create a policer bandwidth profile with

required CIR, CBS, EIR, EBS values. Not relevant
for flow 1.
Layer 2 Control l2cp-profile Define policy for L2CP traffic handling by port
Protocol (L2CP) and/or flow (peer, tunnel or drop)
Priority Queue queue-map-profile Define profile for mapping CoS values to

Mapping queues.
Congestion wred-profile Define WRED profiles to be attached to queue

Avoidance (WRED) profiles
Shaper shaper-profile Define shaper profiles to be attached to a

queue and queue group profiles
Queue Block queue-block-profile Define queue block profiles to be attached to

queue group profiles
Queue Group queue-group-profile Define queue group profile for Gbe CL ports
Marking marking-profile Define profile for conversion of CoS and packet

color values into P-bit when push or mark tag
editing is used. Not relevant for flow 1.
Serial Ports port serial Configure physical parameters of serial ports of

I/O module
and logical ports
DS1 Ports port ds1 Configure physical parameters of DS1 ports

(MPW-1 module)

(CL.2 module)
Bind previously created L2CP profile
Bind the queue group profile intended for
flows 2. 3 to GbE port

3. Define SVIs

5-40 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection Megaplex-4
4. Add RIFs and Pseudowire Router router (2) Add interfaces to the router
bind them to Define static routing table
SVIs

5. Define PW
peer

pseudowire
6. Define
DS0 Cross-connect cross-connect ds0 Cross-connecting between serial ports of

high-speed module and timeslots of DS1 ports
cross-connections
of MPW-1 module
7. Configure

Cross-connect ports and PW (MPW-1 module)
Bridge bridge Define, assign a number and configure a bridge

8. Define
bridge
entity
Bridge bridge Define bridge ports

bridge ports
9. Define
Bridge bridge Add VLANs, define bridge ports as VLAN

10. Configure
membership

VLAN
VLAN
Protection protection Define ERP, configure RPL owner, configure

11. Configure
East and West ports

ERP
Megaplex-4 High-Speed Service Aggregation into PSN Backbone with G.8032 Protection 5-41

• Flow 1a: ingress – SVI, egress – BP
• Flow 1b: ingress – BP, egress – SVI
• Flows 2,3: ingress – GBE, egress – BP
12. Configure flows

Bind L2CP profile to flows 2,3
Bind policer profile to flows 2,3
Bind queue mapping profile to flows 2,3
Bind queue block instance to flows 2,3
Define required VLAN editing actions for flow 1
Bind marking profile to flows 2, 3
5.15 Fast Ethernet Traffic to E1/T1 (HDLC Protocol)

(5a)
Figure 5-25 illustrates a Fast Ethernet to E1/T1 service. This service is shown in
Figure 5-4 on the example of M8E1 module. Table 5-15 details configuration
5-42 Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a) Megaplex-4


Policer profile
profile
Flow 1a
I/O Module,
Logical Flow 1b
E1/T1 Port HDLC Port Fast Ethernet
MAC
Port
Configure E1/T1 Configure HDLC Define logical Configure

Port port mac port and Ethernet port
bind hdlc port
Set Ethernet
port parameters
Assign policer
profile
2. Configure ports
3. Configure Configure ds0

cross-connections cross-connect

1a 1b
4. Configure flows Assign Assign

Assign Assign
profile profile
editing editing
actions actions
Configure tdm-
5. Configure protection
group protection
Legend:
Mandatory
Optional
Figure 5-25. Fast Ethernet to E1/T1 Service (HDLC Protocol)
Table 5-15. Fast Ethernet to E1/T1 Service Provisioning (HDLC Protocol)

1. Define
Ethernet ports)
profiles

module
and logical ports
connectivity between hdlc and fast ethernet
ports.
Binding HDLC port to Logical MAC
HDLC Ports port hdlc Configuring parameters of HDLC port
Megaplex-4 Fast Ethernet Traffic to E1/T1 (HDLC Protocol) (5a) 5-43

E1/T1 Ports port {e1 | t1} Configuring physical E1/T1 ports

Define flow 1:
3. Configure flows
• match-all
• push vlan <x>
• p-bit fixed
Define flow 2:
• match vlan <x>
• pop
TDM Group protection tdm-group Protecting E1/T1 links

protection
Configure
Protection
4.
5.16 Fast Ethernet Traffic to Multiple E1 (MLPPP

Protocol) (5b)
Figure 5-26 illustrates a Fast Ethernet to multiple E1 service. This service is shown
in Figure 5-4 on the example of M8E1 module. Table 5-16 details configuration
5-44 Fast Ethernet Traffic to Multiple E1 (MLPPP Protocol) (5b) Megaplex-4


Policer profile
profile
Flow 1a
I/O Module,
Up to 8 PPP Logical Flow 1b
MLPPP Port Fast Ethernet
Ports MAC
E1 Port PPP Port Port
Configure Define logical Configure

Configure E1 Configure PPP MLPPP port mac port and Ethernet port
Port port bind mlppp port
Set mlppp port Set Ethernet
Set E1 Define ppp parameters port parameters
parameters port
Bind ppp port Assign policer
profile
Bind e1 port
2. Configure ports

1a 1b
3. Configure flows
Assign Assign
Assign Assign
profile profile
editing editing
actions actions
Configure tdm-
group protection
Legend:
Mandatory
Optional
Figure 5-26. Fast Ethernet to Multiple E1 Service (MLPPP Protocol)
Table 5-16. Fast Ethernet to E1/T1 Service Provisioning (MLPPP Protocol)

1. Define
Ethernet ports)
profiles

module
connectivity between mlppp and fast ethernet
ports.
and logical ports
Binding MLPPP port to Logical MAC
MLPPP Ports port mlppp Configuring physical parameters of the MLPPP

port
Binding the PPP port to the MLPPP port
PPP Ports port ppp Defining and binding the PPP port to the E1
physical port of a M8E1 module
E1 Ports port e1 Configuring physical E1 ports
Megaplex-4 Fast Ethernet Traffic to Multiple E1 (MLPPP Protocol) (5b) 5-45


Define flow 1:
3. Configure flows
• match-all
• push vlan <x>
• p-bit fixed
Define flow 2:
• match vlan <x>
• pop
TDM Group protection tdm-group Protecting E1/T1 links

4. Configure
protection
Protection
5.17 Voice Traffic to SDH/SONET (6)

Figure 5-27 illustrates voice to SDH/SONET service. Table 5-17 details
5-46 Voice Traffic to SDH/SONET (6) Megaplex-4

VC-12/VT1.5 E1/T1 CL.2 Module, Voice I/O Module,

SDH/SONET Link
E1-i/T1-i Ports Voice Port

Configure link
e1-i/t1-i parameters card voice port

link parameters port parameters
Assign vc profile Assign vc profile

2. Configure ports
for each aug/oc-3
3. Configure cross
connect
Configure Configure ds0

connect

Legend:
Mandatory
Optional
Figure 5-27. Voice to SDH/SONET Service
Table 5-17. Voice to SDH/SONET Service Provisioning

1. Define
profiles
Voice Ports port voice Configuring physical voice ports of I/O module
and logical ports


Megaplex-4 Voice Traffic to SDH/SONET (6) 5-47

3. Configure timeslot DS0 cross-connect cross-connect ds0 Cross-connecting between serial ports of high-
cross-connections speed module and timeslots of e1-i/t1-i ports
of CL.2 module

(CL.2 module)

Protection
3. Configure
protection

for SDH/SONET
Payload
5.18 Voice Traffic to PSN (6a)

Figure 5-22 illustrates in detail high-speed to PSN (Ethernet) services
schematically shown in Figure 5-4:
• Service 6a: The traffic from voice port is forwarded to GbE port, which serves
These services use the pseudowire engine of the VS voice module. Table 5-12
5-48 Voice Traffic to PSN (6a) Megaplex-4


profile profile
Flow 1a VS Voice 64 kbps VS Voice Module,

CL.2/GbE PW
Flow 1b SVI RIF PW Module, Voicel Port
port Router DS1 Ports
Configure Configure ds1 Configure I/O card

ethernet port port voice port
Set Ethernet
port parameters
Assign policer
2. Configure ports
profile
Define SVI port
3. Define SVI
Define RIFs

Bind router
interfaces to
SVIs
Add static
Add and configure

6. Add a pseudowire
a pseudowire
Configure pw-tdm
7. Configure cross-connect Configure ds0
cross-connections DS1/PW 1:1 cross-connect

1a 1b
Assign Assign
Assign Assign
profile profile
editing editing
actions actions
Legend:
Mandatory
Optional
Figure 5-28. Voice to Ethernet Service
Megaplex-4 Voice Traffic to PSN (6a) 5-49

Table 5-18. Voice to Ethernet Service Provisioning

1. Define profiles
Profiles profile

Voice Ports port voice Configuring physical parameters of voice ports

of I/O module
and logical ports
DS1 Ports port ds1 Configuring physical parameters of DS1 ports

(I/O module)
Ethernet Ports port ethernet Configuring physical parameters of GbE port

(CL.2 module, Service 6a)

3. Define SVIs


4. Add RIFs and
bind them to

SVIs

5. Define PW peer
Pseudowires pwe Add and configure pseudowires.

Voice channels are sharing same PW.
pseudowire
6. Define
5-50 Voice Traffic to PSN (6a) Megaplex-4

DS0 Cross-connect cross-connect ds0 Cross-connecting between voice ports and

timeslots of DS1 ports of VS voice module
7. Configure cross-connections

Cross-connect ports and PW

8. Configure flows
• Flow 1a: ingress – SVI, egress – Fast

Ethernet port of I/O module
• Flow 1b: ingress – Ethernet port of I/0
5.19 Teleprotection Traffic to SDH/SONET (7)

Figure 5-29 illustrates teleprotection over SDH/SONET service. Table 5-19 details
Megaplex-4 Teleprotection Traffic to SDH/SONET (7) 5-51

vc profile
1. Define profiles I/O Module, I/O Module,

CMD-IN-I Ports CMD-IN Ports
Configure Configure cmd-in

VC-12/VT1.5 E1/T1 64/128 kbps I/O Module, cmd-in-i port port
CL.2 Module,
SDH/SONET Link CMD Channel
E1-i/T1-i Ports
Ports Set cmd-in-i
port parameters
Configure Configure cmd- Bind cmd-in
Configure link
e1-i/t1-i parameters channel port port

link parameters port parameters I/O Module,
I/O Module,
CMD-OUT-I
CMD-OUT Ports
Assign vc profile Ports
2. Configure ports Assign vc profile
for each aug/oc-3
Configure Configure cmd-

cmd-out-i port out port
Set cmd-out
port parameters
Bind cmd-out-i
port
3. Configure cross
connect
Configure Configure TP
Configure ds0
cross connect
connect
4. Configure Configure aps Configure vc-path Configure tdm-

protection protection group protection group protection
Legend:
Mandatory
Optional
Figure 5-29. Teleprotection Service
Table 5-19. TP to SDH/SONET Service Provisioning

1. Define
profiles
CMD-IN Ports port cmd-in Configuring cmd-in ports
CMD-IN-I Ports port cmd-in-i Configuring cmd-in-i ports

Binding the cmd-in port to the cmd-in-i port

and logical ports
CMD-OUT Ports port cmd-out Configuring cmd-out ports

Binding the cmd-out-i port to the cmd-out
port
CMD-OUT-I Ports port cmd-out-i Configuring cmd-out-i ports
CMD-CHANNEL port cmd-channel Configuring cmd channels

Ports
5-52 Teleprotection Traffic to SDH/SONET (7) Megaplex-4

E1 Ports port {e1-i | t1-i} Configuring physical parameters of E1-i/T1-i


DS0 cross-connect cross-connect ds0 Cross-connecting between the cmd-channel

timeslot cross-
and timeslots on the E1/T1 ports of the uplink

3. Configure
connections
module

(CL.2 module)

Protection Protecting CMD channels
3. Configure
protection

for SDH/SONET
Payload
5.20 T3 Traffic to SONET (8)

Figure 5-30 illustrates a T3 to SONET service using T3 module. Table 5-20 details
Megaplex-4 T3 Traffic to SONET (8) 5-53

VT1.5 T1 T3 Module, Fixed T3 I/O Module,

SONET Link
T1 Ports connection T3 Port
Configure
Configure I/O
Configure link t1 parameters
card T3 port
Set sdh-sonet Set t1 port

link parameters parameters
Assign vc profile
2. Configure ports for each aug/oc-3
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect
4. Configure Configure aps Configure tdm-

Legend:
Mandatory
Optional
Figure 5-30. T3 to SDH/SONET Service
Table 5-20. T3 to SDH/SONET Service Provisioning
VC Profiles port vc-profile Configuring VC Profiles (to be assigned to OC-3

1. Define
profiles
ports)
T1 Ports configure port e1-t1 t1 Configuring parameters of T1 ports (T3

module)
and logical ports
T3 Ports configure port e3-t3 t3 Configuring physical T3 ports
SONET Ports port sdh-sonet Configuring physical SONET ports

Selecting oc3 group
Assigning vc profile to oc3
5-54 T3 Traffic to SONET (8) Megaplex-4

3. Configure SDH/SONET cross-connect sdh-sonet Cross-connecting between T1 ports (T3
connections
cross- Cross-Connect module) and VT1.5 containers (CL.2 module)
TDM Group protection tdm-group Protecting T3 and T1 services

4. Configure
protection
Protection
5.21 Voice to T3 via DS0 Cross-Connect (9)

Figure 5-31 illustrates a voice to T3 service via DS0 cross-connect. Table 5-21
T3 Module, Fixed T3 Module, I/O Module,

T3 Port connection T1 Ports Voice Port
Configure
Configure I/O
Configure t3 port t1 parameters
card voice port
Set t3 link Set t1 port

parameters parameters
1. Configure ports
2. Configure
cross-connect
Configure DS0
cross-connect
Configure Configure
3. Configure tdm-group tdm-group
Legend:
Mandatory
Optional
Figure 5-31. Voice Aggregation to T3 Link
Megaplex-4 Voice to T3 via DS0 Cross-Connect (9) 5-55

Table 5-21. Voice Aggregation to T3 Link Provisioning
Voice Ports configure port voice Configuring physical voice ports of I/O module
And logical ports
T1 Ports configure port e1-t1 t1 Configuring parameters of internal T1 ports

(T3 module)
T3 Ports configure port e3-t3 t3 Configuring physical T3 ports
DS0 Cross- cross-connect ds0 Cross-connecting between the voice port of VC

connection
Configure
cross-
Connect module and internal T1 port of T3 module

2.
TDM Group protection tdm-group Protecting T3 ports

Protection
TDM Group protection tdm-group Protecting T1 ports

Protection
5.22 Ethernet Traffic over PDH to SDH/SONET (10a)

Figure 5-32 illustrates an Ethernet traffic over PDH to SDH/SONET service. This
service is shown in Figure 5-12 on the example of VS-16E1T1-EoP module.
5-56 Ethernet Traffic over PDH to SDH/SONET (10a) Megaplex-4


VC profile Policer profile
profile
Flow 1a
VC-12/VT1.5 E1/T1 Logical Flow 1b CL.2/GbE
SDH/SONET Link E1-i/T1-i Port VCG Port GFP Port MAC port
Configure VCG Configure

Configure Configure GFP Define logical
Configure link port Ethernet port
e1-i/t1-i port mac port and
parameters bind gfp port
Set vcg port Set gfp port Set Ethernet
Set sdh-sonet
parameters parameters port parameters
link parameters Set e1-i/t1-i port
Assign vc parameters Assign vc Assign policer
profile Bind vcg port
profile for each profile
aug/oc-3 Assign vc profile
Bind vc/vt Assign vc
2. Configure ports
profile
3. Configure
cross-connect
Configure
sdh-sonet
cross-connect

1a 1b
4. Configure flows
Assign Assign
Assign Assign
profile profile
editing editing
actions actions
Configure aps
protection
Configure vc-
path protection
Legend:
Mandatory
Optional
Figure 5-32. Ethernet traffic over PDH to SDH/SONET Service
Table 5-22. Ethernet traffic over PDH to SDH/SONET Service Provisioning

1. Define profiles

Ethernet ports)

originating from the port.
Ethernet Ports port ethernet Configuring physical Ethernet ports CL.2 module
and logical ports
connectivity between gfp and ethernet ports.
GFP Ports port gfp Configuring physical parameters of GFP port
Binding the corresponding VCG to the GFP port
VCG Ports port vcg Configuring physical parameters of VCG port
Megaplex-4 Ethernet Traffic over PDH to SDH/SONET (10a) 5-57


T1 Ports ports (VS-16E1T1-EoP module)
SDH/SONET cross-connect sdh- Cross-connecting between E1-i/T1-i ports (VS-

3. Configure
connections
Cross-Connect sonet 16E1T1-EoP module) and VC-12/VT1.5

cross-
containers

• Flow 1a: ingress – logical mac, egress –GbE
4. Configure flows
port of CL.2 modules

• Flow 1b: ingress –GbE port of CL.2 modules,
egress –logical mac
Path Protection for protection vc-path Protecting SDH/SONET payload units

Configure
protectio
SDH/SONET Payload
5.
5.23 Ethernet Traffic over PDH to E1/T1 (10b)

Figure 5-33 illustrates an Ethernet traffic over PDH to E1/T1 service. This service
is shown in Figure 5-12 on the example of VS-16E1T1-EoP module. Table 5-23
5-58 Ethernet Traffic over PDH to E1/T1 (10b) Megaplex-4


VC profile
profile
Flows
1a, 1b Bind
M-ETH
Bridge BP M-ETH Module,
Logical GbE Ports
E1/T1 Port VCG Port GFP Port
MAC BP Bind
BP
Configure VCG Configure GFP Define logical
Configure port port mac port and
e1/t1 port
bind gfp port
2. Configure ports Set vcg port Set gfp port
parameters parameters Configure
Ethernet port
Assign vc
Bind vcg port
profile Set Ethernet
Bind e1/t1 Assign vc port parameters
port profile
Define a bridge
Define bridge
ports
Bind to M-ETH
3. Configure bridge
Ethernet port
Configure VLAN
membership
Define VLANs
Configure bridge
ports as VLAN
members
Configure MAC
table size
Configure flows
1a, 1b
4. Configure flows
Assign ingress
and egress ports
Assign classifier
profile
Define vlan
editing actions
Legend:
Mandatory
Optional
Figure 5-33. Ethernet traffic over PDH to E1/T1 Service
Table 5-23. Ethernet traffic over PDH to E1/T1 Service Provisioning

1. Define
profiles
Classifier Profiles classifier-profile Define classification profile for traffic

originating from the port.

and logical ports
2. Configure
(M-ETH module)
physical
Logical MAC Ports port logical-mac Define logical MAC ports to establish
connectivity between gfp ports of VS-16E1T1-
EoP module and bp ports of M-ETH Bridge.
Megaplex-4 Ethernet Traffic over PDH to E1/T1 (10b) 5-59

GFP Ports port gfp Configure physical parameters of GFP port

Assign vc profile
Bind the corresponding VCG to the GFP port
VCG Ports port vcg Configure physical parameters of VCG port

Assign vc profile
Bind the corresponding E1/T1 port to the VCG
E1 Ports port { e1 | t1} Configuring physical parameters of E1/T1 ports

T1 Ports (VS-16E1T1-EoP module)
Bridge bridge Define, assign a number and configure bridge

entities:
• M-ETH bridge
Bridge bridge port Define bridge ports

3. Define
M-ETH Bridge: Bind to M-ETH GbE ports

bridge
Bridge bridge vlan Add VLANs, define bridge ports as VLAN

VLAN

4. Configure flows
• Flow 1a: ingress – Logical Mac (VS-16E1T1-

EoP), egress – BP (M-ETH)
• Flow 1b: ingress – BP (M-ETH), egress –
Logical Mac (VS-16E1T1-EoP)
5-60 Ethernet Traffic over PDH to E1/T1 (10b) Megaplex-4

Chapter 6
Cards and Ports
6.1 Cards
I/O Modules
Cards (I/O modules) currently offered for Megaplex-4 are listed in Chapter 1,
Table 1-2.
Configuring Modules in the Chassis

Use the following procedure to program modules in the Megaplex-4 chassis. After
physical installation in the chassis, each module must be defined manually. The
system identifies module types, but powers the modules up and downloads
operation software only after modules are defined by the user. You can program
modules even if they are not installed in the chassis.
 To program modules in the Megaplex-4 chassis:

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

modules Using no card-type removes the selection
Defining common logic card-type cl {cl2-622gbe | cl2- Slots: cl-a, cl-b

modules 622gbea | cl2 } cl2-622gbe – CL.2 module with 2 GbE ports
and 2 STM-1/OC-3 or STM-4/OC-12 links
cl2-622gbe/a – CL.2 module with 2 GbE ports
(possibility of upgrade to advances Ethernet
capabilities) and 2 STM-1/OC-3 or STM-4/OC-12
links
cl2 – CL.2 module without GbE and SDH/SONET
ports for DS0 cross-connect
Using no card-type removes the selection
Megaplex-4 Cards 6-1

Chapter 6 Cards and Ports Installation and Operation Manual
Defining card-type e1-t1 {m8e1 | m8t1 Slots: 1 to 10

M8E1/M8T1/M16E1/M16T1 | m16e1 | m16t1} Using no card-type removes the selection
modules
Defining high speed card-type high-speed {hs12n | Slots: 1 to 10

modules hs6n | hsf2 | hs703} Using no card-type removes the selection
Defining SHDSL modules card-type=dsl {asmi54c | Slots: 1 to 10

asmi54c-e1eth | asmi54c-e1 | Using no card-type removes the selection
m8sl | sh16 | sh16-e1|
sh16-e1-pw}
Defining ISDN modules card-type isdn {hsu12 | hsu6 | Slots: 1 to 10

hss} Using no card-type removes the selection
Defining low speed card-type low-speed {ls6n | Slots: 1 to 10

modules ls12 | hsr-n} Using no card-type removes the selection
Defining T3 modules card-type e3-t3 mt3 Slots: 1 to 10

Defining versatile modules card-type versatile {vs-12 | Slots: 1 to 10

vs-6-bin | vs-6-c37 | vs-6-fxs | Using no card-type removes the selection
vs-6-fxo | vs-6-em | vs-fxs-em
vs-e1-eop | vs-t1-eop | vs-e1-pw
| vs-t1-pw | vs-6-e1 | vs-6-t1}
Defining voice modules card-type voice {vc4fxs | vc4fxo | Slots: 1 to 10

vc4e-m | vc8fxs | vc8fxo | vc8e- Using no card-type removes the selection
m | vc16fxs | vc16fxo | vc16e-m |
vc4-omni | vc6lb }
Defining alarm relay card-type alarm-relay {acm | tp} Slots: 1 to 10

Defining Optimux modules card-type optimux {op108c | Slots: 1 to 10

op108c-e1 | op34c | op34c-e1} Using no card-type removes the selection
Defining pseudowire card-type pw mpw1 Slots: 1 to 10

Defining D-NFV modules card-type virtual-engine ve Slots: 2, 3, 4, 5, 7, 8, 9, 10

Note: Out of two slots taken by each
D-NFV module, it is the right one that is
identified in the terminal.
Note
The Megaplex-4100 chassis is supplied with a power supply in slot PS-A and a
CL.2 module in slot CL-A configured as factory defaults:
(slot ps-a card-type power-supply ps
slot cl-a card-type cl cl2-622gbe).
6-2 Cards Megaplex-4

Installation and Operation Manual Chapter 6 Cards and Ports
Example
 To configure a chassis with:
• Two power supply modules
• Two CL.2 modules
• One ASMi-54C/N module in slot 6
• Five M8E1 modules in slots 1–5.
mp4100# config slot ps-a card-type ps-a power-supply ps
mp4100# config slot ps-b card-type ps-b power-supply ps
mp4100# config slot cl-a card-type cl cl2-622gbe
mp4100# config slot cl-b card-type cl cl2-622gbe
mp4100# config slot 1 card-type e1-t1 m8e1
mp4100# config slot 6 card-type dsl asmi54c-e1eth
 To delete the ASMi-54C/N module in slot 6 from the database:

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

You can display information on the following:
• Modules installed in the chassis: show cards-summary command
• Module programmed in the specific slot: info or show card-type command
• All the parameters configured in the database (per chassis): info detail
command.
 To d is p la y t h e m o d u le s in s t a lle d in t h e ch a s s is :
• At the config# prompt, enter the show cards-summary command.

mp4100>config# show cards-summary

Slot Family Type HW Ver SW Ver
---------------------------------------------------------------
--------------
PS-A Power Supply ps Undefined Undefined
PS-B Not Installed-- Undefined Undefined
CL-A CL CL2 622GbE 0.0/ 0.0 3.00P14/ 0
CL-B Not Installed-- Undefined Undefined
1 Optimux OP-34C 1 1.50A0
2 Optimux OP-34C 1 1.50A0
3 Optimux OP-34C Eth E1 1 1.50A0
4 E1-T1 M8 E1 1 1.69
5 E1-T1 M16 E1 1 1.50
6 E1-T1 M8 T1 1 1.69
7 Optimux OP-108C 2 2.UNDEF
8 Optimux OP-108C 2 2.UNDEF
9 E1-T1 M16 T1 1 1.50
10 High Speed HS6N 2 6.00
 To display information on the module programmed in the slot:

• At the slot# prompt, enter the info command.
MP4100>config>slot(1)# info
card-type e1-t1 m8t1
OR
• At the slot# prompt, enter the show card-type command.
MP4100>config>slot(1)# show card-type
Family : E1-T1
Type : M8 E1
HW Ver : 1
SW Ver : 1.73
 To display information on all the parameters configured in the database (per

chassis):
• At the config# prompt, enter the info detail command.
mp4100# configure info detail
echo "Management configuration"
# Management configuration
management
echo "SNMP Configuration"
# SNMP Configuration
snmp
snmp-engine-id mac 00-00-00-00-00-00
no snmpv3
exit
more..
echo "RADIUS"
# RADIUS
radius
server 1
exit
server 2
exit
server 3
exit

server 4
exit
exit
exit
echo "Slot Configuration"
# Slot Configuration
slot ps-a
card-type power-supply ps
exit
more..
slot ps-b
exit
slot cl-a
card-type cl cl2-622gbe
exit
slot cl-b
exit
slot 1
card-type voice vc4e-m
exit
slot 2
exit
slot 3
more..
exit
slot 4
exit
slot 5
exit
slot 6
exit
slot 7
exit
slot 8
exit
more..
slot 9
exit

slot 10
card-typevoice vc4e-m
exit
echo "System Configuration"
# System Configuration
system
echo "Clock Configuration"
# Clock Configuration
clock
echo "Station Clock Configuration"
# Station Clock Configuration
station 1
exit
exit
exit
more..
echo "QoS - Configuration"
# QoS - Configuration
qos
echo "Policer Profile configuration"
# Policer Profile configuration
policer-profile "Policer1"
exit
exit
echo "Port Configuration"
# Port Configuration
port
echo "Signaling Profile Configuration"
# Signaling Profile Configuration
signaling-profile ""
exit
exit
exit
exit
exit
echo "Ethernet - Port Configuration"
# Ethernet - Port Configuration
ethernet cl-a/1
no policer
exit
# Ethernet - Port Configuration
ethernet cl-a/2
no policer
exit
echo "Managment Ethernet - Port Configuration"
# Managment Ethernet - Port Configuration
mng-ethernet cl-a/1
exit
echo "E1 Internal - Port Configuration"
# E1 Internal - Port Configuration
e1-i cl-a/1

exit
e1-i cl-a/2
exit
e1-i cl-a/3
exit
e1-i cl-a/4
exit
e1-i cl-a/5
exit
e1-i cl-a/6
no shutdown
more..
exit
e1-i cl-a/7
no shutdown
exit
e1-i cl-a/8
exit
e1-i cl-a/9
exit
e1-i cl-a/10
exit
e1-i cl-a/11
exit
e1-i cl-a/12
exit
more..
e1-i cl-a/13
exit
e1-i cl-a/14
exit
e1-i cl-a/15
exit
e1-i cl-a/16
exit
e1-i cl-a/17
exit
e1-i cl-a/18
exit
e1-i cl-a/19
exit

more..
e1-i cl-a/20
exit
e1-i cl-a/21
exit
e1-i cl-a/22
exit
e1-i cl-a/23
exit
e1-i cl-a/24
exit
e1-i cl-a/25
exit
more..
e1-i cl-a/26
exit
e1-i cl-a/27
exit
e1-i cl-a/28
exit
e1-i cl-a/29
exit
e1-i cl-a/30
exit
e1-i cl-a/31
exit
e1-i cl-a/32
exit
more..
e1-i cl-a/33
exit
e1-i cl-a/34
exit
e1-i cl-a/35
exit
e1-i cl-a/36
exit
e1-i cl-a/37
exit
e1-i cl-a/38

exit
e1-i cl-a/39
exit
more..
e1-i cl-a/40
exit
e1-i cl-a/41
exit
e1-i cl-a/42
exit
e1-i cl-a/43
exit
e1-i cl-a/44
exit
e1-i cl-a/45
exit
e1-i cl-a/46
more..
no shutdown
exit
e1-i cl-a/47
no shutdown
exit
e1-i cl-a/48
exit
e1-i cl-a/49
exit
e1-i cl-a/50
exit
e1-i cl-a/51
exit
more..
e1-i cl-a/52
exit
e1-i cl-a/53
exit
e1-i cl-a/54
exit
e1-i cl-a/55
exit
e1-i cl-a/56

exit
e1-i cl-a/57
exit
e1-i cl-a/58
exit
e1-i cl-a/59
exit
e1-i cl-a/60
exit
e1-i cl-a/61
exit
e1-i cl-a/62
exit
e1-i cl-a/63
exit
echo "Voice - Port Configuration"
# Voice - Port Configuration
voice 1/1
no shutdown
signaling cas
exit
voice 1/2
no shutdown
signaling cas
exit
voice 1/3
no shutdown
signaling cas
no shutdown
signaling cas
exit
voice 1/4
no shutdown
signaling cas
exit
voice 2/1
no shutdown
signaling cas
more..
exit
voice 2/2
no shutdown
signaling cas
exit
voice 2/3
no shutdown

signaling cas
exit
voice 2/4
no shutdown
signaling cas
exit
voice 3/1
no shutdown
signaling cas
more..
exit
voice 3/2
no shutdown
signaling cas
exit
voice 3/3
no shutdown
signaling cas
exit
voice 3/4
no shutdown
signaling cas
exit
voice 4/1
no shutdown
signaling cas
more..
exit
voice 4/2
no shutdown
signaling cas
exit
voice 4/3
no shutdown
signaling cas
exit
voice 4/4
no shutdown
signaling cas
exit
voice 5/1
no shutdown
signaling cas
more..
exit
voice 5/2
no shutdown
signaling cas

exit
voice 5/3
no shutdown
signaling cas
exit
voice 5/4
no shutdown
signaling cas
exit
voice 6/1
no shutdown
signaling cas
more..
exit
voice 6/2
no shutdown
signaling cas
exit
voice 6/3
no shutdown
signaling cas
exit
voice 6/4
no shutdown
signaling cas
exit
voice 7/1
no shutdown
signaling cas
more..
exit
voice 7/2
no shutdown
signaling cas
exit
voice 7/3
no shutdown
signaling cas
exit
voice 7/4
no shutdown
signaling cas
exit
voice 8/1
no shutdown
signaling cas
more..
exit


voice 8/2
no shutdown
signaling cas
exit
voice 8/3
no shutdown
signaling cas
exit
voice 8/4
no shutdown
signaling cas
exit
voice 9/1
no shutdown
signaling cas
more..
exit
voice 9/2
no shutdown
signaling cas
exit
voice 9/3
no shutdown
signaling cas
exit
voice 9/4
no shutdown
signaling cas
exit
voice 10/1
no shutdown
signaling cas
exit
voice 10/2
no shutdown
signaling cas
exit
voice 10/3
no shutdown
signaling cas
exit
voice 10/4
no shutdown
signaling cas
exit
echo "SDH/Sonet - Port Configuration"
# SDH/Sonet - Port Configuration
sdh-sonet cl-a/1

exit
# SDH/Sonet - Port Configuration
sdh-sonet cl-a/2
exit
exit
echo "Cross Connect"
# Cross Connect
cross-connect
ds0 e1-i cl-a/6 ts 3 voice 9/2
more..
more..
sdh-sonet vc12-vt2 cl-a/1/1/2/1/1 e1-i cl-a/46
exit
router 1
exit
router 2
exit

echo "Port Configuration"

# Port Configuration
port
echo "SDH/Sonet VC Profile Configuration"
# SDH/Sonet VC Profile Configuration
vc-profile "tug-structure"
exit
vc-profile "hvc-laps"
payload-label 0x18
exit
vc-profile "hvc-gfp"
payload-label 0x1b
exit
vc-profile "lvc-eos"
payload-label 0x05
exit
exit
Resetting I/O Module

 To reset an I/O module:
Navigate to configure slot(slot number)#.
The config>slot(slot number)# prompt is displayed.
Enter reset to reset the module installed in the selected slot.
Note Resetting a module will temporarily disrupt services supported by that module.
Configuration Errors
Table 6-1 lists messages generated by Megaplex-4 when a configuration error is
detected.
Table 6-1. Configuration Error Messages
Code Type Syntax Meaning
100 Error AT LEAST ONE PS CARD MUST At least one power supply module must be defined in the
BE DEFINED system configuration
101 Error AT LEAST ONE CL CARD MUST At least one CL module must be defined in the system
BE DEFINED configuration
102 Warning MODULE TYPE MISMATCH The modules actually installed in the equipment and the
modules programmed in the database are not the same
103 Warning INTERFACE HW/SW MISMATCH The interface type configured by the management system
is different from the interface selected by means of
jumpers

104 Error MODULE DATABASE MISMATCH The CL module type configured in the database {cl2-
622gbe | cl2-622gbea |cl2-gbea | cl2-ds0 } does not match
the installed module type (can be displayed by
“show config cards-summary” command ("CL2 622GbE",
"CL2 622GbEa", "CL2 GbEa" or "CL2 DS0").
400 Error DIFFERENT CL CARDS FOR Different CL module types are installed in slots CL-A and
REDUNDANCY CL-B; CL redundancy is not available
404 Error PORT ASSIGNED IS IN One of the two ports connected via flow, cross-connect or
SHUTDOWN STATE bind command is in shutdown state. Set this port to “no
shutdown”.
766 Error ILLEGAL CARD TYPE Since out of two slots taken by each D-NFV module, it is
DEFINITION the right one that is identified in the terminal, the D-NFV
module cannot be configured in the following I/O slots.
• MP-4100: slots 1 & 6.
• MP-4104 slots 1 & 2.
Similarly, it cannot be configured in a slot, following a slot
occupied with any other module.
6.2 Port-Related Profiles
Signaling Profiles
This feature is available for the E1/T1 ports on the M8E1/M8T1 modules.
When CAS is used (always in an M8T1 module, and in an M8E1 module when the
E1 port uses G.732S framing, with or without CRC-4 support), the signaling
information of each voice channel is carried by means of up to four bits (signaling
bits), designated by the applicable standards as bits A, B, C, and D.
The number of bits actually available for carrying signaling information and the
data rate at which signaling information can be transferred, depend on the port
(E1 or T1) and the framing mode being used, which are determined by the
applicable international standards.
The information appearing in the signaling bits can be provided either by voice
interface modules installed in the Megaplex-4, or by digital PBXs or local exchange
trunks connected to one of the E1 or T1 Megaplex-4 ports.
Digital PBXs and local exchanges often use dedicated signaling protocols to
exchange the signaling information through the E1 or T1 trunk bits assigned to
CAS, and therefore may interpret the state of CAS bits in proprietary ways. The
CL module can perform signaling protocol conversions, for example – to enable
the termination of PBX timeslots by a voice module installed in an I/O slot, to
connect a PBX to PSTN lines, etc.
6-16 Port-Related Profiles Megaplex-4

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 also defines the signaling bit patterns that indicate the busy and idle
states.
The user can assign a separate profile to each TDM (E1 or T1) port. Each port,
and even individual timeslots of a port, can therefore use different receive and
transmit translation rules. Up to 5 different profiles, each covering a different set
of interoperability requirements, can be defined and stored in the Megaplex-4
configuration databases.
See also VC-4, VC-4A, VC-8, VC-8A, VC-16 section in Megaplex-4 I/O Modules
Installation and Operation Manual, Voice Modules Chapter, for specific
considerations regarding voice ports.
Factory Defaults
The default signaling profiles (profile1 to profile5) are provided with no signaling
translation.
idle-code 0x00
busy-code 0x0f
Each default signaling profile looks as follows.

busy-code 0x0f
idle-code 0x00
a-bit-code tx a rx a
b-bit-code tx b rx b
c-bit-code tx c rx c
d-bit-code tx d rx d
You can change the contents but not the names of each of the 5 profiles.
Configuring CAS Signaling Profiles

Use the following procedure to modify the signaling translation rules contained in
the five signaling profiles supported by Megaplex-4, in accordance with your
specific application requirements. You can specify different rules for the receive
and transmit directions.
• Receive direction: defines the interpretation of the incoming signaling
information, that is, the signaling information received from the external
port. This section enables the user to select the translation of each incoming
bit to the corresponding internal signaling bit (the signaling bit actually sent
to each module which needs the signaling information received by a main
link).
Megaplex-4 Port-Related Profiles 6-17

• Transmit direction: defines the translation of the internal signaling bits to the
signaling bits transmitted through the external port.
 To add a signaling profile:

1. Navigate to configure port.
The config>port# prompt is displayed.
2. Type signaling-profile <signaling-profile-name>. Signaling profile name has
the fixed format: profile1 to profile5.
A signaling profile with the specified name is created and the following
prompt is displayed, for example:
config>port>signaling-profile(<profile2>)#.
3. Configure the signaling profile as described below.
 To configure a signaling profile:

1. Navigate to configure port signaling-profile < signaling-profile-name> to
select the signaling profile to configure.
The config>port>signaling-profile(<signaling-profile-name>)# prompt is
displayed.
Specifying translation rules a-bit-code tx {0 | 1 | a | b 0 – bit value is always 0

for signaling bit A (receive | c | d | inverse-a | inverse-b 1 – bit value is always 1
and transmit directions) | inverse-c | inverse-d}
a, b, c, d – bit value copied from the
rx {0 | 1 | a | b | c | d | inverse-a
corresponding incoming bit
| inverse-b | inverse-c | inverse-d}
inverse-a, inverse-b, inverse-c, inverse-d
– inverted bit value, related to the
Specifying translation rules b-bit-code tx {0 | 1 | a | b 0 – bit value is always 0

for signaling bit B (receive | c | d | inverse-a | inverse-b 1 – bit value is always 1
rx {0 | 1 | a | b | c | d | inverse-a
Specifying translation rules c-bit-code tx {0 | 1 | a | b 0 – bit value is always 0

for signaling bit C (receive | c | d | inverse-a | inverse-b 1 – bit value is always 1
rx {0 | 1 | a | b | c | d | inverse-a

Specifying translation rules d-bit-code tx {0 | 1 | a | b 0 – bit value is always 0

for signaling bit D (receive | c | d | inverse-a | inverse-b 1 – bit value is always 1
rx {0 | 1 | a | b | c | d | inverse-a
Specifying the signaling bit busy-code {00 to 0F (hexa)} Hexadecimal number in the range of 0 to
pattern indicating the busy 0F (two digits)
state The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which, when
converted to binary format, yields the
desired ABCD sequence.
Example: if the busy state is indicated by
the incoming sequence 1000, select 8.
Specifying the signaling bit idle-code {00 to 0F (hexa)} Hexadecimal number in the range of 0 to
pattern indicating the idle 0F (two digits)
state The pattern is specified by a hexadecimal
digit (0 to 9, A to F), which when
converted to binary format yields the
desired ABCD sequence.
Example
 To create and configure signaling profile “1”:

• a-bit-code rx and tx – translated to inverse-a
• b-bit-code rx and tx – b
• c-bit-code rx and tx – translated to 1
• d-bit-code rx and tx – d

mp4100>config# port signaling-profile profile1 a-bit-code tx

inverse-a rx inverse-a
mp4100>config# port signaling-profile profile1 b-bit-code tx b rx
b
mp4100>config# port signaling-profile profile1 c-bit-code tx 1 rx
1
mp4100>config# port signaling-profile profile1 d-bit-code tx d rx
d
 To display the resulting signaling profile:

mp4100>config>port>signaling-profile(profile1)# info detail
busy-code 0x0f
idle-code 0x00
a-bit-code tx inverse-a rx inverse-a
b-bit-code tx b rx b
c-bit-code tx 1 rx 1
d-bit-code tx d rx d
The screen lists the four signaling bits, A to D, together with their current
translations. In this case, the busy and idle codes are left at their
defaults.
 To assign profile 1 to an E1 port:

mp4100>config>port>e1(9/1)# signaling-profile 1
Note
Pay attention to the syntax:
• When configuring the profile n (n=1,2,3,4,5), use “profile<n>” number
• When assigning the configured profile to an E1/T1 port, use simply “<n>”, not
“profile<n>”)
Analog Signaling Profiles

This feature is available for the voice ports of the VS modules.
Analog voice signals are digitized using PCM (Pulse-code modulation), in
compliance with ITU-T G.711 and AT&T Pub. 43801 standards. The signaling
information of each voice channel is carried by means of up to four bits (signaling
bits), designated by the applicable standards as bits A, B, C and D. Analog
signaling profile is configured per channel and per direction.
Table 6-2 and Table 6-3 show the analog signaling profile actions for FXS and
FXO modules, respectively.
Table 6-2. Analog Signaling Profile Actions for FXS Modules
Signaling Direction Signaling Bits

Mode
A B C D
Loop signaling/inverse-sig 1/0 1/0 1

Tx
Start 1/0 signaling/inverse-sig 1/0 1

signaling/inverse-sig not-used not-used not-used
not-used signaling/inverse-sig not-used not-used
signaling/inverse-sig forward-disconnect/ not-used not-used

Rx inverse-forward-disconnect
forward-disconnect/ signaling/inverse-sig not-used not-used

inverse-forward-
disconnect
Tx signaling/inverse-sig 1/0 1/0 1
signaling/inverse-sig wink not-used not-used
Wink signaling/inverse-sig wink forward- not-used

Start Rx disconnet
signaling/inverse-sig forward-disconnect/ wink not-used

inverse-forward-disconnect
Table 6-3. Analog Signaling Profile Actions for FXO Modules
Signaling Direction Signaling Bits

Mode
A B C D
signaling/inverse- 1/0 1/0 1

Tx sig
1/0 signaling/inverse-sig 1/0 1
signaling/inverse- loop-disconnect/ 1/0 1

sig inverse-loop-
Loop Start disconnect
loop-disconnet signaling/inverse-sig 1/0 1
signaling/inverse- not-used not-used not-

sig used
Rx
1/0 signaling/inverse-sig not-used not-
used
signaling/inverse- wink 1/0 1

sig
signaling/inverse- wink loop-disconnet 1

Tx sig
Wink Start signaling/inverse- loop-disconnect/ wink 1

sig inverse-loop-
disconnect
signaling/inverse- not-used not-used not-

Rx
sig used

For E&M modules, the A/B bits are selected based on tx-a-bit/tx-b-bit sent by the
remote unit and the received signaling.
In the tables above, the corresponding bit states are shown as follows:
• not-used indicates that the corresponding bit is not relevant;
• signaling states:
 For FXS module, 0 indicates on-hook and 1 indicates off-hook.
 For FXO module, 0 indicates no ring and 1 indicates ring.
• inverse-sig has two states:
 For FXS module, 0 indicates off-hook and 1 indicates on-hook.
 For FXO module, 0 indicate ring and 1 indicates no ring.
• loop-disconnect has two states:
 0 indicates the far-end party is not disconnected (CO is feeding the
line);
 1 indicates the far-end party has disconnected (CO has disconnected
the line feeding);
• inverse-loop-disconnect has two states:
 0 indicates loop current feed open state (CO has disconnected the line
feeding);
 1 indicates no loop current feed open state (CO is feeding the line) ;
• forward-disconnect has two states:
 0 indicates the far-end party is not disconnected (FXS port is feeding
the line) ;
 1 indicates the far-end party has disconnected (FXS port has
disconnected the line feeding);
• inverse-forward-disconnect has two states:
 0 indicates the far-end party has disconnected (FXS port has
disconnected the line feeding);
 1 indicates the far-end party is not disconnected (FXS port is feeding
the line) ;
• wink indicates reverse battery polarity:
 0 indicates reversion battery polarity,
 1 indicates normal battery polarity.
Factory Defaults
The following default analog signaling profiles are provided:
mp-4100>config>port# inf detail
analog-signaling-profile "sig_over_a_bit"
a-bit-tx signaling
a-bit-rx signaling
b-bit-tx 1

b-bit-rx not-used
c-bit-tx 0
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
exit
analog-signaling-profile "sig_tx_a_rx_b"
a-bit-tx signaling
a-bit-rx not-used
b-bit-tx 1
b-bit-rx inverse-sig
c-bit-tx signaling
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
exit
analog-signaling-profile "sig_tx_b_rx_a"
a-bit-tx 0
a-bit-rx signaling
b-bit-tx inverse-sig
b-bit-rx not-used
c-bit-tx 0
c-bit-rx not-used
d-bit-tx inverse-sig
d-bit-rx not-used
exit
The default analog signaling profiles cannot be modified or deleted.
Configuring Analog Signaling Profiles
 To configure an analog signaling profile:

1. Navigate to configure port analog-signaling-profile <analog-
signaling-profile-name> to configure.
The config>port>analog-signaling-profile(<analog-
signaling-profile-name>)# prompt is displayed.
Specifying translation rules a-bit-tx {1 | 0 | signaling | inverse-

for signaling bit A (receive sig | loop-disconnect}
and transmit directions) a-bit-rx {not-used | signaling |
inverse-sig | forward-disconnect |
inverse-forward-disconnect}

Specifying translation rules b-bit-tx {1 | 0 | signaling | inverse-

for signaling bit B (receive sig | loop-disconnect | inverse-loop-
and transmit directions) disconnect | wink}
b-bit-rx {not-used | signaling |
inverse-sig | forward-disconnect |
inverse-forward-disconnect | wink}
Specifying translation rules c-bit-tx {1 | 0 | signaling | loop-

for signaling bit C (receive disconnect | wink}
and transmit directions) c-bit-rx {not-used | forward-
disconnect | wink}
Specifying translation rules d-bit-tx {1 | 0 | signaling | inverse-

for signaling bit D (receive sig}
and transmit directions) d-bit-rx {not-used | signaling |
inverse-sig}
Example
 To create and configure analog signaling profile “profile1”:

• a-bit-tx– translated to 1
• a-bit-rx– translated to not-used
• b-bit-tx– signaling
• b-bit-rx– signaling
• c-bit-tx and rx, d-bit-tx and rx use the default value

mp4100>config>port>analog-signaling-pro(profile1)# a-bit-tx 1
mp4100>config>port>analog-signaling-pro(profile1)# a-bit-rx not-
used
mp4100>config>port>analog-signaling-pro(profile1)# b-bit-tx
signaling
mp4100>config>port>analog-signaling-pro(profile1)# b-bit-rx
signaling
 To display the resulting signaling profile:

mp4100>config>port>signaling-profile(profile1)# info detail
a-bit-tx 1
a-bit-rx not-used
b-bit-tx signaling
b-bit-rx signaling
c-bit-tx 0
c-bit-rx not-used
d-bit-tx 1
d-bit-rx not-used
 To assign profile 1 to a voice port:

mp4100>config>port>voice(10/3)# analog-signaling-profile profile1
VC Profiles
In the Megaplex-4 architecture, any SDH/SONET unit of order lower than
SDH/SONET port is configured by creating VC profiles and binding it to the
corresponding unit. You can create up to 64 profiles to define the handling of
SDH/SONET (VC/VT/STS) traffic. You can then assign the required profile to a gfp,
hdlc, e1, e1-i, aug, t1, t1-i or oc-3 port.
Four pre-defined default VC profiles are available in the system. They are bound
automatically to VC-12/VT-1.5/ VC-3/VC-4/STS-1/STS-3C or E1/T1 ports when
certain configurations take place in the system. Table 6-4 lists these profiles
together with their names and corresponding configurations.
Table 6-4. Default VC Profiles
Name VC Profile Matches Configuration
lvc-eos payload-label 0x05 VC-12/VT-1.5 bound to VCG

pathtrace direction tx length 15plus-crc string Note: When this profile is
"www.rad.com" padding nulls assigned to GFP ports (which
no plm-response is done automatically), the
pathtrace parameters define
no tim-response
the J2 pathtrace
rate-threshold eed e-3 sd e-6
interval-threshold cv 25 es 20 ses 3 uas 10
day-threshold cv 250 es 200 ses 7 uas 10

Name VC Profile Matches Configuration
tug-structure payload-label 0x02 VC-12/VT1.5 bound to VCG on

pathtrace direction tx length 15plus-crc string the overhead (POH) level or
"www.rad.com" padding nulls E1/T1 is cross-connected to
SDH/SONET ports directly
no plm-response
Note: When this profile is
no tim-response
assigned to AUG/OC-3 ports
rate-threshold eed e-3 sd e-6 (which is done automatically),
interval-threshold cv 25 es 20 ses 3 uas 10 the pathtrace parameters
day-threshold cv 250 es 200 ses 7 uas 10 define the J1 pathtrace
When this profile is assigned
to E1/T1 ports (which is done
automatically), the pathtrace
parameters define the J2
pathtrace
hvc-laps payload-label 0x18 VC-3/VC-4/STS-1/STS-3C

pathtrace direction tx length 15plus-crc string bound to VCG with LAPS
"www.rad.com" padding nulls encapsulation (hdlc)
no plm-response Note: When this profile is

assigned to HDLC ports (which
no tim-response
is done automatically), the
rate-threshold eed e-3 sd e-6 pathtrace parameters define
interval-threshold cv 25 es 20 ses 3 uas 10 the J1 pathtrace
hvc-gfp payload-label 0x1b VC-3/VC-4/STS-1/STS-3C

pathtrace direction tx length 15plus-crc string bound to VCG with GFP
"www.rad.com" padding nulls encapsulation (gfp)
no plm-response Note: When this profile is

assigned to GFP ports (which
no tim-response
is done automatically), the
rate-threshold eed e-3 sd e-6 pathtrace parameters define
interval-threshold cv 25 es 20 ses 3 uas 10 the J1 pathtrace
Factory Defaults
The VC profile parameter defaults are listed in the table below.
payload-label 0x02 (default values for pre-defined profiles are listed in

Table 6-4)
pathtrace direction tx
pathtrace padding nulls
pathtrace length 15plus-crc
plm-response disable

tim-response disable
rate-threshold eed e-3
rate-threshold sd e-6
interval-threshold cv 25
interval-threshold es 20
interval-threshold ses 3
interval-threshold uas 10
day-threshold cv 250
day-threshold es 200
day-threshold ses 7
day-threshold uas 10
Configuring VC Profiles
Usually the four predefined VC profiles assigned to the corresponding units by
default should satify the user needs. However, if it is necessary to add and
configure a new user-defined profile, you must first disconnect the respective
predefined profile and only then configure and assign the new one.
 To add a user-defined VC profile:

2. Type vc profile <vc-profile-name>.
A VC profile with the specified name is created and the following prompt
is displayed: config>port>vc-profile(<vc-profile-name>)$.
3. Configure the VC profile as described below.
 To configure a VC profile:
1. Navigate to configure port vc-profile <vc-profile-name> to select the VC
profile to configure.
The config>port>vc-profile(<vc-profile-name>)# prompt is displayed.
Specifying the expected payload payload-label { 00 to FF Hexadecimal number in the range of 0 to

label (one byte) (hexa) } FF (two digits)

Using no pathtrace disables the checking

Enabling the checking of the pathtrace [direction { tx | rx- When the VC profile is assigned to
receive/transmit path trace label tx}] [length {64 | 15plus- au-4/oc-3 ports, this string defines the J1
by the port and configuring the crc}] [string <path-trace- pathtrace.
optional path trace direction and string>] [padding {spaces | When the VC profile is assigned to
padding nulls}] gfp/hdlc/e1/t1 ports, this string defines
the J2 pathtrace.
Enables the sending of RDI plm-response rdi Using no plm-response disables RDI
indications by the port, in case indications
the received signal label (SDH
overhead byte C2 or V5) is
different from the expected
signal label
Enables the sending of RDI tim-response rdi Using no tim-response disables RDI
indications by the port, in case indications
the received path trace label
(carried in SDH overhead byte J1
or J2) is different from the
expected path trace label
Selecting EED (error rate rate-threshold [eed {e-3 | e- If the selected BER value is exceeded,
degradation) and SD (signal 4 | e-5} ] [ sd {e-6 | e-7 | e-8 Megaplex-4 generates the relevant (EED
degrade) thresholds | e-9}] or SD) alarm
Setting CV, ES, SES and/or UAS interval-threshold [cv

counter value during a 15-min <cv-value 0-900>] [es <es-
interval starting from which a value 0-900>] [ses <ses-
trap will be sent value 0-900>] [uas
<uas-value 0-900>]
Setting CV, ES, SES and/or UAS day-threshold [cv <cv-value

counter value during 24-hours 0-86400>] [es <es-value 0-
interval starting from which a 86400>] [ses <ses-value 0-
trap will be sent 86400>] [uas <uas-value 0-
86400>]
6.3 Physical Ports
Binary Command Ports
Applicable Modules
The Binary command module VS-6/BIN has 8 command inputs and 8 outputs,
enabling binary equipment to utilize the advanced transport capabilities offered
by Megaplex.
6-28 Physical Ports Megaplex-4

The binary commands can be locally output or be carried to a peer card/Megaplex

over a TDM/SDH network or over a packet-switched network using two
cmd-channel ports. Up to 4 commands can be carried over a single DS0.
See Versatile Modules chapter in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all binary command ports disabled. Other parameter
defaults are listed in the table below.
cmd-in
input-active Association between the cmd-in active state and the high
supplied voltage
cmd-out
alarm-state-energized cmd-out alarm state indication yes
Configuring CMD-IN Ports
 To configure a cmd-in port:

1. Navigate to configure port cmd-in <slot>/<port>/<trib> to select the cmd-in
port to configure.
The config>port>cmd-in>(<slot>/<port>/<trib>)# prompt is displayed.
Assigning short description name <string> Using no name removes the name
to port
Administratively enabling no shutdown Using shutdown disables the port

port
Defining the association input-active {high | low} • low – command input is activated by low
between the cmd-in active voltage (0 to 18 VDC)
state and the supplied • high – command input is activated by high
voltage voltage (24 to 48 VDC)
Forcing the cmd-in port into force-active Using no force-active cancels the command
active state, disregarding
the actual input state
Megaplex-4 Physical Ports 6-29

Configuring CMD-OUT Ports
 To configure the cmd-out port parameters:

1. Navigate to configure port cmd-out <slot>/<port>/<trib> to select the port
to configure.
The config>port>cmd-out>(<slot>/<port>/<trib>)# prompt is displayed.
to port

port
Defining cmd-out alarm alarm-state-energized {yes | Energizing:

state indication no} • energized yes – The corresponding relay is
normally unenergized and switches to the
energized state when the alarm is active.
• energized no – The corresponding relay is
normally energized and switches to the
unenergized state when the alarm is
active.
The relay contacts are normally open.
Configuring CMD-CHANNEL Ports
 To configure the cmd-channel port parameters:

1. Navigate to configure port cmd-channel <slot>/<port> to select the port to
configure.
The config>port>cmd-channel>(<slot>/<port>)# prompt is displayed.
Assigning short description to port name <string> Using no name removes the name
Viewing Status Information

For viewing the status of the binary command ports, follow the instructions
below.
 To view the status of a cmd-in port:

1. Navigate to config>port> cmd-in> (<slot>/<port>/<tributary>)#
2. Type show status.

The status is displayed, for example as follows:

mp4100>config>port>cmd-in(10/1/1)# show status
Name : VS-6/BIN CMD In 1
Administrative Status : Up
Operation Status : Up
Value : 0
Forced : No
 Administrative and operational status
 Value – Command value (0, 1),
 Forced – Whether the port is in force-active state (Yes/No).
 To view the status of a cmd-out port:

1. Navigate to config>port> cmd-out> (<slot>/<port>/<tributary>)#
mp4100>config>port>cmd-out(10/1/1)# show status
Name : VS-6/BIN CMD Out 1
Value : 0
 Value – Command value (0, 1).
 To view the status of a cmd-channel port:

1. Navigate to config>port> cmd-channel> (<slot>/<port>)#
mp4100>config>port>cmd-channel(10/1)# show status
Name : VS-6/BIN CMD CH 1
Displaying Binary Command Statistics

Binary command ports cmd-in, cmd-out and cmd-channel feature RAD proprietary
statistical diagnostics.
 To display the statistics of a cmd-in port:

1. Navigate to config>port> cmd-in> (<slot>/<port>/<tributary>)#
The statistics is displayed, for example as follows:

mp4100>config>port>cmd-in(2/1/1)# show statistics

Trip : 1
The statistics shows the number of trips occurred since the port has been open.
 To display the statistics of a cmd-out port:

1. Navigate to config>port> cmd-out> (<slot>/<port>/<tributary>)#
The statistics (number of trips) is displayed, for example as follows:
mp4100>config>port>cmd-out(2/1/1)# show statistics
Trip Counter : 1
 To display the statistics of a cmd-channel port:

mp4100>config>port>cmd-channel(2/1)# show statistics
Frame Error : 0
CRC Error : 0
Table 6-5. Binary Command Statistics Parameters
Frame Error Number of frame errors received on the cmd channel since last reset or power-up
CRC Error Number of CRC errors received on the cmd channel since last reset or power-up
A CRC error is declared when the CRC bits generated locally on the data in the received
frame (protecting critical teleprotection bits) do not match the CRC bits (crc1 – crc4)
received from the transmitter.
Clearing Statistics
 To clear the statistics on a binary command port:

1. Navigate to the corresponding port.
2. Enter clear-statistics.
The statistics for the specified port are cleared.
DS1 Optical Ports (Fiber Optic Links of VS-6/C37 Modules)
Applicable Modules
Ds1-opt ports denote fiber optic links of VS-6/C37 modules.
Standards
IEEE C37.94

The IEEE C37.94 standard defines a programmable nx64 kbps (n = 1…12)
multimode optical fiber interface between teleprotection and digital multiplexer
equipment, for distances of up to 2 km.
The VS-6/C37 module features a dual-port fiber optic interface, operating at a
nominal wavelength of 830 nm and nominal line rate of 2.048 Mbps. Each port is
terminated in a pair of ST connectors for connection to standard multimode fiber.
The fiber optic interface has a wide dynamic range, which ensures that the
receiver will not saturate even when using short fiber optic cables (saturation is
caused when the optical power applied to the receiver exceeds its maximum
allowed input power, and results in very high bit error rates).
The interface can be used for both user and network ports – either for inter-
substation communication or for transmitting distance Teleprotection
information.
Factory Defaults
Megaplex-4 is supplied with all ds1-opt ports disabled. Other parameter defaults
inband-management no inband-management (disabled)
inband-management – routing-protocol none
Configuring DS1 Optical Port Parameters
 To configure the DS1 optical link parameters:

1. Navigate to configure port ds1-opt <slot>/<port> to select the port to
configure.
The config>port>ds1-opt>(<slot>/<port>)# prompt is displayed.
Assigning short name <string> Using no name removes the name

description to port

port

Enabling inband inband-management <timeslot> protocol ppp – synchronous PPP over HDLC
management and setting {ppp | fr} [routing-protocol {none | prop- encapsulation
its parameters rip | rip2} ] fr –Frame Relay encapsulation (under
DLCI 100) in accordance with RFC
2427
See also Configuring Inband
Management in Chapter 8 for
important considerations on
selecting routing protocol.
Using no inband management
<timeslot> disables inband
management through this timeslot
There are no special error messages for DS1-Opt ports.
Viewing a DS1-Opt Port Status

Follow the instructions below for viewing the status of the DS1-opt port 5/1 as
an example.
 To view the DS1-opt port status:

• At the config>port>ds1-opt (<slot>/<port>)# prompt, enter show status.
The status information appears as illustrated below.
mp4100>config>port>ds1-opt(5/1)# show status
Name : IO-5 Ds1 Opt01
Loopback Type : None
Testing DS1 Optical Links

The test and diagnostics functions available on each optical link are:
• Local loopback on local optical link
• Remote loopback on local optical link
Local Digital Loopback (Local Loop)

The local loopback is a digital loopback performed at the digital output of a
selected channel, by returning the transmit signal of the channel in the same
timeslot of the receive path. The transmit signal is still sent to the remote
Megaplex unit.
While the loopback is connected, the local serial port should receive its own
signal.
The loopback signal path is shown below.

Figure 6-1. Local Loopback, Signal Path
Remote Digital Loopback (Remote Loop)

The remote loopback is a digital loopback performed at the digital input of the
channel, by returning the digital received signal of the channel to the input of the
transmit path. The receive signal remains connected to the local user, and can be
received by user.
While the loopback is connected, the remote serial port should receive its own
signal.
Figure 6-2. Remote Loopback, Signal Path
Loopback Duration
The activation of a loopback disconnects the local and remote equipment served
by the VS-6/C37 module. Therefore, when you initiate a loopback, you have the
option to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated,
without operator intervention. However, you can always deactivate a loopback
activated on the local module before this timeout expires. When using inband
management, always use the timeout option; otherwise, the management
communication path may be permanently disconnected.
The default is infinite duration (without timeout).

Activating the Loopbacks
 To perform a loopback on the DS1 optical link:

1. Navigate to configure port ds1-opt <slot>/<port> to select the optical link to
be tested.
The config>port>ds1-opt>(<slot>/<port>)# prompt is displayed.
Activating and configuring the loopback {local | remote} local – local loopback
direction of the loopback and [duration <duration in minutes remote – remote loopback
the duration of it (in minutes) 1..30> ]
Stopping the loopback no loopback
Ethernet Ports
Applicable Modules
Megaplex-4 features the following user Ethernet ports:
• Two fiber optic or copper Gigabit Ethernet network ports on each CL.2
module
• Eight fiber optic or copper Gigabit Ethernet network ports on each M-ETH I/O
module
• Various fiber-optic/copper external Fast Ethernet user ports on the following
I/O modules: M8E1, M8T1, M8SL, OP-108C, OP-34C, ASMi-54C, ASMi-54C/N,
MPW-1, VS, D-NFV.
Optimux modules, in addition to external Ethernet ports, also have internal
Ethernet ports, serving to increase the total payload and management bandwidth
transferred to the optical link.
Standards
IEEE 802.3, RFC 4836, RFC 3635.
GbE Port Interfaces

The GbE ports on CL modules provide the physical connection to the packet
switched network. The GbE ports on M-ETH modules provide Megaplex-4 with a
multirate FE/GE interface, for optical or electrical media. This module can be used
to provide LAN connectivity among Ethernet ports on the same module, as well
as Ethernet services, thus eliminating the need for an external switch while
providing a dependable Ethernet connectivity solution.
These ports can be ordered with one of the following interfaces:

• 10/100/1000BASE-T copper ports. This type of ports support

autonegotiation, with user-specified advertised data rate (10, 100 or
1000 Mbps) and operating mode (half- or full-duplex).
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 100/1000BASE-X SFP plug-in modules. Support for
standard SFP optical transceivers for the GbE link interfaces enables selecting
the optimal interface for each application. This type of ports does not
support autonegotiation.
The interfaces support Synchronous Ethernet (Sync-E) master and slave modes
according to ITU-T G.8261–G.8266 requirements. This allows each port to:
• Extract the port clock. The derived clock will be used by the clock selection
mechanism as a source clock
• Set the port Tx clock according to the domain clock available from the CL
module
• Act as a source of ESMC messages for SSM-based clock modes.
Fast Ethernet Port Interfaces

The external Ethernet ports have 10/100 Mbps interfaces capable of
auto-negotiation. The user can configure the advertised data rate (10 or
100 Mbps) and operating mode (half-duplex or full-duplex). Alternatively,
auto-negotiation can be disabled, and the rate and operating mode be directly
specified.
The Ethernet ports can be ordered with one of the following types of interfaces:
• Sockets for SFP Fast Ethernet transceivers. RAD offers several types of SFPs
with optical interfaces, for meeting a wide range of operational requirements
(SFPs with copper interfaces are also available). The SFPs are hot-swappable.
• 10/100BASE-TX interfaces terminated in RJ-45 connectors. In addition to
auto-negotiation, MDI/MDIX polarity and cross-over detection and automatic
cross-over correction are also supported. Therefore, these ports can always
be connected through a “straight” (point-to-point) cable to any other type of
10/100BASE-T Ethernet port (hub or station).
The ordering options depend on the specific I/O module.
Hierarchy and Values

The following table shows the number of Ethernet ports on each Megaplex-4
module, their CLI denomination, hierarchy and possible values. The hierarchical
position of external Ethernet ports is slot:port for all the modules. The internal
Ethernet ports of the Optimux modules are designed as slot:port:tributary (in
these modules port=mux_eth_tdm).

Table 6-6. Ethernet Ports on I/O Modules
Modules CLI Name Hierarchy Possible Values
M-ETH ethernet slot: port 1..8
M8E1, M8T1, M8SL ethernet slot: port 1..3
OP-108C ethernet slot:port 1..2
int-eth slot:port:tributary 1/1, 3/1

OP-34C ethernet slot:port 1
int-eth slot:port:tributary 1/1

ASMi-54C, ethernet slot:port 1..2

ASMi-54C/N
MPW-1 ethernet slot:port 1..3
VS ethernet slot:port 1 per submodule
D-NFV ethernet slot:port 1..4
int-eth slot:port 1
For more information, see the respective module section in Megaplex-4 I/O
Modules Installation and Operation Manual, Voice Modules Chapter.
Flow Control
A flow control is a mechanism that allows an Ethernet receiving end that is
unable to process all the traffic sent to it, to hold the transmitted traffic until it is
able to process packets again.
The mechanism uses a PAUSE frame, which is a packet that instructs the far-end
device to stop transmission of packets until the receiver is able to handle traffic
again. The PAUSE frame has a timer value included (set by the originating
receiver), which tells the far-end device how long to suspend transmission. If that
timer expires or is cleared by getting a PAUSE frame with timer value set to 0, the
far-end device can then send packets again. Flow control is an optional port-level
parameter.
Flow control is supported on both directly- and indirectly-attached ports:
• Directly-attached ports support symmetrical flow control (both Rx and Tx)
• Indirectly-attached ports support Rx flow control only, without issuing Tx
PAUSE frames (asymmetric flow control).
When autonegotiation is enabled, flow control mode is negotiated and a port
advertises its user-selected flow control capabilities to the peer. The actual flow
control mode, as well as duplex mode and transmission speed are set after the
negotiation is completed.

When autonegotiation is disabled, the flow control mode is manually selected by

the user.
All Megaplex-4 Ethernet interfaces, except the OOB management port, support
flow control.
L2CP Handling
Megaplex-4 handles Layer-2 control protocol traffic on a per-port basis. The L2CP
traffic is processed using a two-stage mechanism comprising per-port L2CP
profiles (set of rules for traffic handling). The L2CP profile affects untagged L2CP
frames. In total, Megaplex-4 supports up to 16 L2CP profiles:
• Up to 4 (including default) port-level profiles can be defined on directly-
attached ports
• Up to 32 different addresses/protocols can be selected per L2CP profile.
If no default action is configured for an unspecified address or protocol, this
traffic is tunneled.
Note If an L2CP profile has been attached to a port, the profile cannot be deleted or
modified.
L2CP Profile Settings

Megaplex-4 can tunnel, discard or peer (trap to host for protocol processing)
L2CP packets. These actions are defined by L2CP profiles, which also provide
different L2CP addresses. The following MAC addresses are supported by L2CP
profiles: 01-80-C2-00-00-00, 01-80-C2-00-00-02 – 10 and 01-80-C2-00-00-20 –
2F.
Note • PAUSE frames (01-80-C2-00-00-01) are not part of L2CP profiles. They are
either peered or discarded according to flow control setting of a port.
According to L2CP profiles, Megaplex-4 performs the following:

• Discards L2CP traffic.
• Tunnels L2CP traffic. Megaplex-4 forwards the traffic according to its
configuration (flows etc).
• Peers L2CP traffic. Megaplex-4 forwards the traffic to the CPU.
Note Megaplex-4 supports peer action only for the following MAC addresses/protocols:
• 01-80-C2-00-00-00 (RSTP)
• 01-80-C2-00-00-02 (LACP, OAM (EFM))
• 01-80-C2-00-00-03 (802.1x).
Default L2CP Profile

By default, a “tunnel all” profile is attached to every port.

Autonegotiation
The speed and duplex mode of an Ethernet interface is set either manually by the
operator or negotiated with the peer interface. The autonegotiation procedure
enables automatic selection of the operating mode on a LAN. It enables
equipment connecting to an operating LAN to automatically adopt the LAN
operating mode (if it is capable of supporting that mode).
Queue Group Profile

Queue group profiles are the largest entities used in pre- and post-forwarding
traffic management. They are attached to physical ports and consist of queue
block and shaper profiles. See Queue Group Profiles section in Chapter 8 for
details.
PoE
See Power over Ethernet (PoE) section under M-ETH Module in Megaplex-4 I/O
Modules Installation and Operation Manual, Ethernet and Pseudowire Modules
Chapter.
Factory Defaults
By default, the Ethernet non-management ports have the following configuration.
Fast Ethernet ports:
mp4100>config>port>eth(4/1)# info detail
name "IO-4 ethernet 01"
shutdown
auto-negotiation
max-capability 100-full-duplex
no flow-control
no policer
egress-mtu 1790
queue-group profile "FeDefaultQueueGroup"
no l2cp
tag-ethernet-type 0x8100
GbE ports of CL modules:
mp4100>config>port>eth(cl-b/1)# info detail
name "CL-B ethernet 01"
shutdown
auto-negotiation*
max-capability 1000-full-duplex**
min-tagged-frame-length 68
no efm
no shaper
egress-mtu 1790
queue-group profile "GbeDefaultQueueGroup"
l2cp profile "L2cpDefaultProfile"
GbE ports of M-ETH modules:

shutdown
auto-negotiation*
max-capability 1000-full-duplex**
no flow-control
no efm
no policer
egress-mtu 1790
queue-group profile "MeDefaultQueueGroup"
no l2cp
mode never***
priority low***
*copper ports only
**for fiber ports: 1000-x-full-duplex
***PoE modules only
For description of default queue group profiles, see Queue Group Profiles section
in Chapter 8.
Configuring User Ethernet Ports
 To configure the user Ethernet port parameters (any module with Ethernet ports):
1. Navigate to configure port ethernet <slot>/<port> to select the Ethernet port
to configure.
The config>port>eth>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed in the table
below.
Assigning short description to the name <string> Using no name removes the name
port
Enabling autonegotiation auto-negotiation For copper ports only

Using no auto-negotiation disables
autonegotiation
Enabling OAM (EFM) on the efm See Ethernet OAM (EFM) in Chapter 8.
Ethernet port GbE ports of CL.2 and M-ETH modules only
no efm disables OAM (EFM) on the Ethernet
port

Setting maximum frame size (in egress-mtu <64–9600> The maximum frame size for GBE Ethernet
bytes) to transmit (frames above ports of CL and M-ETH modules is 9600.
the specified size are discarded) The maximum frame size for Fast Ethernet
ports of different I/O modules is as follows:
• ASMi-54C/N – 9600
• VS/SH/D-NFV – 9140
• M8E1, M8T1, M8SL, OP-34C, OP-108C,
ASMi-54C/N, MPW-1,
• ASMi-54C – 1522.
Setting maximum advertised max-capability {10-half-duplex | 10-full-duplex –10baseT full duplex (copper
capability (highest traffic handling 10-full-duplex | 100-half-duplex | ports only)
capability to be advertised during 100-full-duplex | 1000-full-duplex 10-half-duplex – 10baseT half duplex (copper
the autonegotiation process) | 1000-x-full-duplex} ports only)
100-full-duplex – 100baseT full duplex
100-half-duplex – 100baseT half duplex (in
the case of M-ETH – copper ports only)
1000-full-duplex – 1000base T full duplex
(copper GbE ports only)
1000-x-full-duplex – 1000base T full duplex
(fiber GbE ports only)
This parameter applies only if
autonegotiation is enabled.
Setting data rate and duplex speed-duplex 10-half-duplex | 10- 10-full-duplex –10baseT full duplex (copper
mode of the Ethernet port, when full-duplex | 100-half-duplex | ports only)
autonegotiation is disabled 100-full-duplex | 1000-full-duplex 10-half-duplex – 10baseT half duplex (copper
| 1000-x-full-duplex} ports only)
100-full-duplex – 100baseT full duplex
100-half-duplex – 100baseT half duplex (in
the case of M-ETH – copper ports only)
1000-full-duplex – 1000base T full duplex
(copper GbE ports only)
1000-x-full-duplex – 1000base T full duplex
(fiber GbE ports only)
Setting flow control for the flow-control Using no flow-control disables flow control
selected port (when operating in
the full duplex mode), or back
pressure (when operating in the
half-duplex mode)

Assigning queue group profile to queue-group profile <queue- Megaplex-4 with CL.2/A modules only
Ethernet port group-profile-name> The queue group profile is defined under
Quality of Service (QoS) in Chapter 8.
no queue-group removes queue group
association
The default queue group profile for Fast
Ethernet ports is defined with 10 Mbps
shaper. Define a new queue group profile if
you need more bandwidth.
The queue group profile cannot be edited.
Thus to use bridge connectivity you need to
remove the existing queue group profile from
this Ethernet port, configure a new queue
group profile and assign it to this port.
Associating a Layer-2 control l2cp <l2cp-profile-name> Megaplex-4 with CL.2/A modules only
processing profile with the port no l2cp GbE ports of CL.2 and M-ETH modules only
Defines discarding or tunneling policy for
Layer-2 protocols.
no l2cp removes association with L2CP profile
The associated L2CP profile specifies peer
action for the following MAC addresses
depending on the protocol in use:
• 01-80-C2-00-00-00 (RSTP)
• 01-80-C2-00-00-02 (LACP, OAM (EFM))
• 01-80-C2-00-00-03 (802.1x).
Configuring collection of pm-collection interval <seconds> You can enable PM statistics collection for all
performance management Ethernet ports rather than enabling it for
statistics for this port, which are individual ports. In addition to enabling PM
presented via the RADview statistics collection for the ports, it must be
Performance Management portal enabled for the device. Refer to the
Performance Management section in the
Monitoring and Diagnostics chapter for
details.
Activating/deactivating a policer policer-profile <name> The policer profile is defined under Quality of
profile Service (QoS) in Chapter 8.
Using no policer <name> deactivates this
policer profile
The total sum of bandwidths defined in
policer profiles for all 8 ports of the M-ETH
module must not exceed 1 GbE.
Setting the minimum VLAN-tagged min-tagged-frame-length {64 | 68 CL GbE and internal D-NFV ports only
frame length (in bytes) that will | 72}
be accepted

Specifying the Ethertype expected tag-ethernet-type Megaplex-4 with CL.2/A modules only
in Ethernet packet <0x0000-0xFFFF>
Enabling transmitting of Sync-E tx-ssm CL GbE ports only

clock availability and quality via no tx-ssm disables ESMC messages
ESMC messages transmission
Configuring PoE operation mode, power-inline mode Available operation modes:

setting maximum power per port {auto [<4000..30000 mW>] | never – Auto-detection is disabled and no
and priority (M-ETH ports only) fixed [<4000..30000 mW>] | power is provided even if an unpowered
never]} priority {critical | high | device is connected to the port.
low}
fixed – Auto-detection is disabled and the
device reserves the maximum power allowed
by the standard or the one configured by the
user, whichever is lower. This mode is used
to support legacy devices (such as Airmuxes)
that do not support auto-detection. Set
maximum power per port in mW
auto – Auto-detection and auto-allocation
are enabled. The user may set a consumption
limit; otherwise, the device allocates
whatever the PD requires, up to the
maximum allowed by the standard (According
to the Class, which was detected). Set
maximum power per port in mW
Port priority levels: critical, high and low.
Within each priority level, ports with a lower
port number are given precedence over ports
with a higher port number (for detailed
description, see Dynamic Power Balancing
under M-ETH Module in Megaplex-4 I/O
Modules Installation and Operation Manual)
 To configure the internal Ethernet port parameters (Optimux cards only):

1. Navigate to configure port ethernet <slot>/<port>/<tributary> to select the
internal Ethernet port to configure.
The config>port>eth>(<slot>/<port>/<tributary>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed in the below.
Assigning short description to the port name <string> Using no name removes the name
Administratively enabling the port no shutdown Using shutdown disables the port
Setting maximum frame size (in bytes) to egress-mtu <64–1600>

transmit (frames above the specified size
are discarded)

Assigning queue group profile to Ethernet queue-group <queue- no queue-group removes queue group
port group-profile-name> association
Ethernet ports is defined with 10 Mbps shaper.
Define a new queue group profile if you need
more bandwidth.
Specifying the Ethertype expected in tag-ethernet-type

Ethernet packet <0x0000-0xFFFF>
Example
 To configure the Ethernet interface:

• Port – port 1 on CL-A module
• Autonegotiation – enabled
• L2CP profile – l2cp_prof1
• Maximum frame size to transmit – 9600 bytes
• Queue group profile –_group1
• Administratively enabled.
mp4100# config port eth cl-a/1 no shutdown
mp4100# configure port ethernet cl-a/1 queue-group profile group1
mp4100# configure port ethernet cl-a/1 l2cp prof1
mp4100# configure port ethernet cl-a/1 egress-mtu 9600
Displaying Ethernet Port Status

You can display the status and configuration of an individual external Ethernet
port. Status of internal Ethernet ports of Optimux modules cannot be displayed.
 To display status of an Ethernet port:

• At the prompt config>port>eth(<slot>/<port>)#, enter show status.
The Ethernet port status parameters are displayed.
For example: Module – M8E1, Slot – 6, Ethernet port – 1, copper SFP-9F
connector.
mp4100>config>port>eth(6/1)# show status
Name :
Connector Type : SFP In
Auto Negotiation : Enabled
Speed And Duplex : 100 Half Duplex
SFP
---------------------------------------------------------
Connector Type : Copper

Manufacturer Name : RAD data comm.

Manufacturer Part Number : SFP-9F
Typical Maximum Range (Meter) : 100
Wave Length (nm) : Not Applicable
Fiber Type : Not Applicable
Note
For GbE ports, assigned MAC addresses are also displayed. For MAC address
allocation mechanism, see Chapter 10.
Displaying PoE Status

For M-ETH PoE-capable ports, you can display the status and configuration of
either individual ports or the entire I/O port.
 To display PoE status of an M-ETH port:

• At the prompt config>port>eth(<slot>/<port>)> power-inline#, enter show
status.
The PoE status parameters are displayed.
For example:
mp4100>config>port>eth(4/1)>power-inline# show status
Interface Mode Pri State Class Alloc PS PD/Max
IO-4 ethernet 01 Auto Low On 3 15.400 15.400 0.800/0.800
IO-4 Pwr Available-> 79.200 On 80.0 15.400 0.800/0.800
Table 6-7. PoE Parameters
Parameter Description Values
Interface Number of M-ETH port
Mode Operation mode “Auto”, “Fixed”, “Never”,
Pri Priority level “Cri”, “High”, “Low”

Parameter Description Values
State Port/module state Port:

Disable – Port is configured as
“never” by the user.
On – PSE is delivering power to
attached PD.
Search – PSE is searching for new
connected PD device.
Fault – Overload/Budget exceeded
due the fact that PD is trying to
consume more power than it is
allowed
Module:
On – All POE-capable ports which are
open and have a PD device connected
to them are delivering power
Off –At least one of open POE-
capable ports is not delivering power,
being in search mode
Faulty – One of POE ports of card are
faulty. “On”, “Off”, “Faulty”
Class PD class detected (per PoE port) 0,1,2,3,4

For more detail, see PoE Power
Classes under M-ETH Module in
Megaplex-4 I/O Modules Installation
and Operation Manual.
Alloc Power (in Watts) allocated by M-ETH, Per port - according to Class
per port/module, in order to fulfill PD supported
requirements Per module - according to power
assigned by CL to this module, based
on port priority algorithm (up to 80W)
PS Power (in Watts), which the POE

port/module decided to deliver to the
PD device/s
PD/Max Power (in Watts), which was actually

drawn by PD device/s per port/module
and its maximum available value
PWR Available Power (in Watts) still available per

module, in order to serve PD devices,
which will be connected later.
 To display PoE status for all ports of a specific M-ETH slot:

• At the prompt config>port>eth(<slot>)> power-inline#, enter show status.
The PoE status parameters are displayed for all the ports. The lines are
repeated for all PoE-capable ports in the module.

Testing Ethernet Ports

No testing is available.
The following tables list messages generated by Megaplex-4 when a configuration
error on Ethernet ports is detected.
Table 6-8. Ethernet Configuration Error Messages
134 Error ALLOCATED POWER EXCEEDED The total allocated power for all the ports of M-ETH/POE
module, which are configured at auto/fix mode, must not
exceed 80W per slot.
407 Error SUM POWER EXCEEDED The total allocated power per Megaplex-4 system must
not exceed 250W.
There is limitation of 250W, per Megaplex-4 chassis, due
to PS limitation. These 250W are shared between the
following modules:
• Voice FXS (VC) modules – consuming 1.5W per port.
• ASMi-54C with power feeding – consuming 3.5W per
port.
• M-ETH/POE – According to user configuration (only on
ports with critical priority)
This sanity appears if you open too many ports, with
overall consumption of more than 250W. To correct,
close some ports, or decrease the maximum power
allocated for M-ETH/POE ports.
587 Warning SUM OF POLICERS RATE The total sum of bandwidths defined in policer profiles for
EXCEED SUPPORTED BW all 8 ports of the M-ETH module must not exceed 1 GbE.
Displaying Ethernet Port Statistics

The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819. The statistics are available both on external Ethernet ports and
internal Ethernet ports of Optimux modules.
 To display the internal Ethernet port statistics on Optimux modules:

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

• At the prompt config>slot>port>eth(<slot>/<port>)#, enter show statistics.

Ethernet port statistics are displayed. The counters are described in the
table below.
Screens and counters are different for Fast Ethernet ports of I/O modules
and GbE ports of CL.2 modules.
M8E1 Module:
mp4100>config>port>eth(8/1)# show statistics
Running
---------------------------------------------------------------
Counter Rx Tx
Total Frames 0 0
Total Octets 0 0
Unicast Frames 0 0
Multicast Frames 0 0
Broadcast Frames 0 0
Paused Frames 0 0
FCS Errors 0 --
Filtered Frames 0 --
Jabber Errors 0 --
Undersize Frames 0 --
Oversize Frames 0 --
64 Octets 0 --
65-127 Octets 0 --
128-255 Octets 0 --
256-511 Octets 0 --
512-1023 Octets 0 --
1024-1528 Octets 0 --
M-ETH Module:
mp4100>config>port>eth(7/3)# show statistics
Running
-----------------------------------------------------------------
Counter Rx Tx
Total Frames 0 9
Total Octets 0 2002
Unicast Frames 0 0
Paused Frames 0 0
FCS Errors 0 --
Jabber Errors 0 --
Oversize Frames 0 --
Discard Frames -- 0
64 Octets 0 0
65-127 Octets 0 4
128-255 Octets 0 0
256-511 Octets 0 5

512-1023 Octets 0 0
1024-1518 Octets 0 0
1519-Max Octets 0 0
CL.2 Module:
mp4100>config>port>eth(cl-a/1)# show statistics
Running
---------------------------------------------------------------
Counter Rx Tx
Total Frames 0 0
Total Octets 0 0
Unicast Frames 0 0
Single Collision -- 0
Paused Frames 0 0
FCS Errors 0 --
Table 6-9. Ethernet Statistics Parameters
Parameter Description Note
Total Frames Total number of frames received/transmitted
Total Octets Total number of bytes received/transmitted
Unicast Frames Total number of unicast frames received/transmitted
Multicast Frames Total number of multicast frames received/transmitted
Broadcast Frames Total number of broadcast frames received/transmitted
Single Collision The number of successfully transmitted frames on this CL.2 GbE ports only
interface for which transmission is inhibited by exactly one
collision.
Paused Frames Total number of pause frames (used for flow control)
received/transmitted through the corresponding Ethernet port
FCS Errors The number of frames received on this interface that are an
integral number of octets in length but do not pass the FCS
check
Filtered Frames Total number of filtered frames received/transmitted I/O Ethernet ports only
Jabber Errors Total number of frames received with jabber errors I/O Ethernet ports only
Oversize Frames Total number of oversized frames received/transmitted I/O Ethernet ports only
Undersize Frames Total number of undersized frames received/transmitted I/O Ethernet ports only
Discard Frames Total number of discarded frames received/transmitted M-ETH ports only
64 Octets Total number of received/transmitted 64-byte packets I/O Ethernet ports only
65–127 Octets Total number of received/transmitted 65–127-byte packets I/O Ethernet ports only

1024–1518 Octets Total number of received/transmitted 1024–1518-byte I/O Ethernet ports only
packets
1519 - Max Octets Total number of received/transmitted packets with 1519 M-ETH ports only
bytes and up to maximum
Clearing Statistics
 To clear the statistics for an Ethernet port:

• At the prompt config>port>eth<slot>/<port>)#, enter clear-statistics.
E1 Ports
Applicable Modules
The following table shows the number of E1 and E1-i ports and their features
supported by each Megaplex-4 module. The hierarchical position of e1 and e1-i
ports is slot:port for all the modules, with the exception of Megaplex cards
OP-108C and OP-34C, where it is slot:port:tributary (in these modules
slot:port=mux_eth_tdm). The digits in brackets (1 to 4) denote restrictions or
other special remarks regarding implementation of this feature in specific
modules.
Table 6-10. Features Supported by Megaplex-4 External E1 Ports
Feature/ M8E1 M16E1 OP-108C OP-108C/ OP-34C ASMi-54C/N VS-16E1T1- VS-16E1T1- VS-6/E1T1
Command E1 EoP PW
Number of ports 8 16 8 8 16 8 16 16 8
name √ √ √ √ √ √ √ √ √
shutdown √ √ √ √ √ √ √ √ √
inband- √(1) √(1) √(1) – √(1) √(1) √(8) √(1) √(1)

management
interface-type √ √ – √ – √ √ √ √
line-type √ √ √ – √ √ √(9) √ √

Feature/ M8E1 M16E1 OP-108C OP-108C/ OP-34C ASMi-54C/N VS-16E1T1- VS-16E1T1- VS-6/E1T1
Command E1 EoP PW
out-of-service √ √ √ – √ √ √ √ √
(voice, data) (2)(1) (2)(1) (2)(1) (2)(1) (2)(1) (2)(1) (2)(1)
restoration-time √ – – – – – – – –
rx-sensitivity √ – – – – – √ √ √
√ – – – – – – – –
signaling- profile (1)(4)
timeslots-signaling- √ – – – – – – – –
profile (1)(4)
idle-code √ (1) √ (1) √ (1) – √ (1) √ (1) √ √ (1) √ (1)
ts0-over-dsl – – –
remote-crc √ – – –
vc-profile – √ (7) √ (7) – √ (7) √ (7) √ (7) √ (7) √ (7)
tx-clock-source – – – – – – – √ (10) √ (10)
Table 6-11. Features Supported by Megaplex-4 Internal E1 Ports
Feature/ CL.2 M8SL ASMi-54C/N, VS-16E1T1-EoP

Command SH-16/E1
ASMi-54C/N: 8
Number of ports 63 8 SH-16/E1: 16 16
name √ √ √ √
shutdown √ √ √ √
inband-management √(1) √(1) √(1) –
interface-type – – – –
line-type √ √(6) √ √(9)
out-of-service (voice, √ (2)(1) √ √ –

data) (2)(1) (2)(1)
restoration-time – – – –
rx-sensitivity – – – –
signaling- profile – √ (1)(4) – –
timeslots-signaling- – √ (1)(4) – –
profile
idle-code √ (1) √(1) √(1) –
ts0-over-dsl √ √ –
remote-crc √(5) – –

Feature/ CL.2 M8SL ASMi-54C/N, VS-16E1T1-EoP

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

• Unframed mode for transparent transfer of 2.048 Mbps streams, including

streams with proprietary framing. Also enables transferring framed E1
streams without terminating timeslot 0, and timeslot 16.
The framer automatically adds the appropriate overhead. Unused timeslots are
filled with a user-specified idle code. The user can also select specific timeslots to
be transferred (DS0 cross-connect).
The framing mode can be independently selected for each extermal or internal E1
port of the I/O module. It is configured by means of the line-type parameter.
Interface Type
The external ports support two line interfaces:
• 120Ω balanced line interface. The nominal balanced interface transmit level is
±3V.
• 75Ω unbalanced interface. The nominal unbalanced interface transmit level is
±2.37V.
Only one of these interfaces can be active at any time. The active interface can
be selected by the user, separately for each port.
Receive Signal Attenuation (M8E1, VS-6/E1T1, VS-16E1T1-PW and

VS-16E1T1-EoP Modules)
The E1 line interfaces have integral LTUs, which enable long-haul operation with
line attenuation of up to 43 dB. The line interface can also emulate a DSU
interface, for short-haul applications: in this case, the maximum line attenuation
is 12 dB. The receive signal attenuation level is configured by means of the
rx-sensitivity parameter. In addition, this parameter can be also configured to
monitor E1 services, with line attenuation of up to12 dB.
Note To assure effective monitoring for M8E1, connect two 510 Ω resistors between
the monitored line and the monitoring port. The resistors should be connected in
series between the monitored line and the monitoring port, one resistor for the
TIP wire and the second one for the RING wire.
E1 Payload Processing
Megaplex-4 E1 modules support three main types of payload per timeslot:
• Data timeslots: timeslots which are transparently transferred from port to
port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
• Voice timeslots: timeslots carrying PCM-encoded payload, with A-law
companding for M8E1 ports and µ-law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
standards. The user can specify translation rules for the signaling information
by defining signaling profiles – see details in the Signaling Profiles section.

• Management timeslots: with framed signals, one timeslot per port can be
assigned to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). However, it is also possible to define unidirectional flows, called
unidirectional broadcasts, from one source (a timeslot of a source port) to
multiple destinations (each destination being a selected timeslot of another
port).
In case of data timeslots, the flow of payload is normally unidirectional. If the
application requires bidirectional flows, cross-coneect must be configured
symmetrically for both directions.
Handling E1 Alarm Conditions

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

• Signaling forced to busy state for 2.5 seconds, and then changed to idle
state for the remaining duration of the out-of-service condition (busy-idle).
This option is suitable for use with all the VC module types.
Inband Management
E1 and internal E1 ports of Megaplex-4 using a framed mode feature inband
management access to the end user’s equipment provided by configuring a
dedicated management timeslot.
The transfer of inband management traffic is controlled by using synchronous
PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
RIP2 routing tables are transmitted as follows:
• Proprietary RIP – Management traffic is routed using RAD proprietary routing
protocol
• RIP2 – In addition to the RAD proprietary routing protocol, RIP2 routing is
also supported.
Factory Defaults
Megaplex-4 is supplied with all e1/e1-i ports disabled. Other parameter defaults
line-type g732s
restoration-time immediate
rx-sensitivity short-haul
interface-type balanced
idle-code 0x7f
out-of-service - voice 0x00
out-of-service - data 0x00
out-of-service - signaling force-idle
signaling-profile no signaling-profile
ts0-over-dsl enabled
vc profile tug-structure

Configuring an E1 Port
 To configure the E1 port parameters of OP-108C, OP-34C modules:

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

1. Navigate to configure port e1 <slot>/<port> to select the E1 port to
configure.
The config>port>e1>(<slot>/<port>)# prompt is displayed.
2. Enter all necessary commands according to the tasks listed below (see
Table 4-5 for parameters supported in each module).

description to port

port
Specifying E1 framing line-type {unframed | g732n When the E1 port is bound to a VCG port,
mode | g732n-crc | g732s | g732s-crc} VS-16E1T1-EoP supports g732n-crc option
only.
Setting attenuation level rx-sensitivity {short-haul | long-haul | M8E1 and VS E1T1 modules only:
of the receive signal monitor } short-haul – low sensitivity (-12 dB)
long-haul – high sensitivity (-43 dB)
monitor – monitor sensitivity (-12 dB)
Specifying port interface-type {balanced | unbalanced}

impedance
Specifying the code idle-code { 00 to FF (hexa) } The available selections are [0x01 to 0xFF]
transmitted to fill unused with the following values that are illegal:
timeslots in E1 frames 0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92

its parameters rip | rip2} ] fr –Frame Relay encapsulation (under DLCI
100) in accordance with RFC 2427
See also Configuring Inband Management in
Chapter 8 for important considerations on
selecting routing protocol.
Not available for VS-16E1T1-EoP modules
when this E1 port is bound to a VCG port
Using no inband management <timeslot>
disables inband management through this
timeslot
Transmitting an out-of-service [voice <00 to FF (hexa)>] [ The hexadecimal number is in the range of 0
out-of-service signal data <00 to FF (hexa)>] [signaling to FF (two digits)
(OOS) {force-idle | force-busy | idle-busy | The selected out-of-service data code is
busy-idle}] also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
Specifying the signaling signaling-profile {1 | 2 | 3 | 4 | 5 | per-ts} 1 to 5 –All the voice timeslots of the port
profile (M8E1 only) being configured use the same signaling
profile, and the number specifies the signaling
profile to be used, in the range of 1 to 5.
per-ts – The signaling profile can be
individually selected for each voice timeslot of
the port being configured.
This parameter is relevant only when using a
framing mode that supports CAS (line-type
= g732s)
Using no signaling-profile cancels signaling
profile setting (signaling information is
transparently transferred)
For creating and configuring signaling
profiles, see Signaling Profiles.
Specifying the signaling timeslots-signaling-profile [tsx] {1 | 2 | 3 | This command is available for voice
profile per a single 4 | 5} timeslots only, if you selected per-ts under
timeslot or per timeslot timeslots-signaling-profile [tsx..tsy] {1 | 2 | signaling-profile
range 3 | 4 | 5} This command is not available for TS #16.
This command is possible for multiple
timeslots only if they are consecutive

Setting the time required restoration-time {1-sec | immediate | Used to change the frame synchronization
for a port to resume 10-sec} algorithm, to reduce the time required for
normal operation after the port to return to normal operation after
loss of frame local loss of synchronization.
1-sec – After 1 second.
10-sec – Similar to the requirements of
AT&T TR-62411 (after 10 seconds).
Immediate – Immediate, complies with ITU-T
Rec. G.732.
This parameter cannot be changed when
using the Unframed mode.
Selecting the timing tx-clock-source loopback loopback – Clock received from the E1/T1
reference source used by tx-clock-source domain <number> port
the port for the domain – Clock provided by system clock
tx-clock-source through-timing
transmit-to-network domain
direction
through-timing – Clock received from
VC12/VT1.5 or PW (according to the
transport network)
This field is valid for VS-16E1T1-PW and
VS-6/E1T1 modules only.
Assigning VC profile to vc profile <profile name> For creating VC profiles, see VC Profiles.
the port Relevant for M16E1, Optimux modules (in
Megaplex chassis only), VS-6/E1T1,
VS-16E1T1-PW, VS-16E1T1-EoP and
ASMi-54C/N. M8E1 does not support this
feature.
Using no vc removes the profile
Configuring an Internal E1 Port
 To configure the internal E1 port parameters:

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

description to the port

the port

Specifying E1 framing line-type { unframed | g732n | g732n-crc | g732n-crc and g732s-crc options are not
mode g732s | g732s-crc } relevant for the M8SL module.
For even e1-i ports representing the serial
ASMi-52 interface (far-end-type=high-
speed-mux-serial-e1), the only possible
selection is g732n.
When the internal E1 port is bound to a VCG
port, VS-16E1T1-EoP supports g732n-crc
option only.
Specifying the code idle-code <00 to FF (hexa)> The available selections are [0x01 to 0xFF]
transmitted to fill unused with the following values that are illegal:
timeslots in E1 frames 0x00, 0x08, 0x10, 0x12, 0x21, 0x24, 0x42,
0x49, 0x84, 0x92
its parameters rip | rip2} ] fr –Frame Relay encapsulation (under DLCI
selecting the routing protocol.
timeslot
Inband management is not available for
even e1-i ports representing the serial
ASMi-52 interface (far-end-type=high-
speed-mux-serial-e1).
Transmitting an out-of-service [voice <00 to FF (hexa)>] [ The hexadecimal number is in the range of 0
out-of-service signal data <00 to FF (hexa)>] [signaling to FF (two digits)
(OOS) {force-idle | force-busy | idle-busy | The selected out-of-service data code is
busy-idle}] also sent during out-of-service periods
instead of the external data stream when
the unframed mode is used
out-of-service voice selection is relevant
only when the g732s or g732s-crc modes
are selected
For even e1-i ports representing the serial
ASMi-52/53 interface (far-end-type=high-
speed-mux-serial-e1), the only possible
selection is data.

Selecting the handling of ts0-over-dsl Timeslot 0 is transparently transferred

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

detection at the remote available only when the ASMi-52/52L
ASMi-52/52L unit (M8SL includes an E1 user port
only) Using no remote-crc disables the remote
CRC-4 error detection
Assigning VC profile to vc profile <profile name> For creating VC profiles, see VC Profiles.
the port Using no vc removes the profile
Example 1
The following section illustrates how to configure the E1 port labeled 1 on the
M8E1 module installed in slot 9:
• Set the E1 framing mode to G.732N with CRC.
• Set the line interface to unbalanced.
• Set the attenuation level of the receive signal to long-haul.
• Set the idle code to 8E.
• Administratively enable the port.
• Leave all other parameters disabled or at their defaults.
mp4100>config>port>e1(9/1)# interface-type unbalanced
mp4100>config>port>e1(9/1)# line-type g732n-crc
mp4100>config>port>e1(9/1)# rx-sensitivity long-haul
mp4100>config>port>e1(9/1)# idle-code 0x8E
mp4100>config>port>e1(9/1)# no shutdown
Example 2
This section illustrates how to configure inband management via a dedicated
timeslot on M8E1 Module.

1. Define an M8E1 module in Slot 1 and configure inband management via E1

port 1 with the following parameters:
 Dedicated timeslot - #31
 Inband management protocol: synchronous PPP over HDLC encapsulation
 Routing protocol: RAD proprietary RIP.
mp4100>config>slot# 4 card-type e1-t1 m8e1
mp4100>config>port# e1 1/1 no shutdown
mp4100>config>port# e1 1/1 line-type g732n
mp4100>config>port# e1 1/1 inband-management 31 protocol ppp
routing-protocol prop-rip
2. Configure router interface 5.
mp4100>config>router# 1 interface 5 address 17.17.17.17/24
3. Bind E1 port 1/1 to router interface 5.
mp4100>config>router# 1 interface 5 bind e1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate E1 port 2 of M8E1 module in Slot 9.
2. Configure signaling profile per ts:
 TS-10 to profile 2
 TS-1 to 9 to profile 3
mp4100>config>port>e1(9/2)# signaling-profile per-ts
mp4100>config>port>e1(9/2)# timeslots-signaling-profile 10 2
mp4100>config>port>e1(9/2)# timeslots-signaling-profile [1..9] 3
mp4100>config>port>e1(9/2)# commit
Result : OK
3. Displaying signaling profile per ts:
mp4100>config>port>e1(9/2)# info detail
name "IO-9 e1 02"
no shutdown
line-type g732s
line-code hdb3
idle-code 0x7f
restoration-time immediate
out-of-service voice 0x00 data 0x00 signaling force-idle
signaling-profile per-ts
timeslots-signaling-profile 1 3

The following table lists messages generated by Megaplex-4 when a configuration
error on E1 modules is detected.
Table 6-12. E1 Configuration Error Messages
131 Warning RESTORATION TIME DOES NOT For E1 links, the restoration time must be in accordance
MATCH THE STD with ITU-T recommendations
132 Error FRAME TYPE / PROFILE One of the following:

MISMATCH • The selected framing mode does not support
signaling profiles
• When the station clock is configured to interface-
type= e1 with tx-ssm enabled, line-type must be
g732n-crc
141 Error ROUTING PROTOCOL/ The rip2 protocol on an I/O module port can be enabled
MNG TYPE MISMATCH only when the inband management method is configured
to ppp or fr
144 Error ILLEGAL IDLE CODE SELECTION Code transmitted in idle timeslots is illegal. The available
selections for E1/E1-i ports are [0x01 to 0xFF] with the
following values that are illegal: 0x00, 0x08, 0x10, 0x12,
0x21, 0x24, 0x42, 0x49, 0x84, 0x92
146 Error NUM OF E1/T1 PORTS The maximum number of framed E1 ports opened on the
EXCEEDS 120 M16E1, ASMi-54C/N or OP modules must not exceed 120.
Viewing an E1 Port Status

Follow the instructions below for viewing the status of the E1 port 5/1 as an
example.
 To view the E1 port status:

• At the config>port>e1(<slot>/<port>/<tributary>)# prompt, enter show
status.
Note <tributary> relates to OP modules only:

• For OP-108C, <port>/<tributary> is 1/1 to 1/4, 3/1 to 3/4.
• For OP-34C, <port>/<tributary> is 1/1 to 1/16.

M8E1:
mp4100>config>port>e1(5/1)# show status
Name :
Administrative Status : Down
Connector Type : DB44
SH-16/E1:
mp4100>config>port>e1-i(10/2)# show status
Name : IO-10 e1-i 02
Testing E1 Ports
Megaplex-4 E1 ports feature test and loopback functions at the port and timeslot
levels. The available loopbacks depend on the port type (E1, E1-i) and specific
module. The following table shows the loopbacks supported by E1 and E1-i ports
on each Megaplex-4 module. The hierarchical position of e1 and e1-i ports is
slot:port for all the modules, with the exception of Megaplex cards OP-108C and
OP-34C, where the e1 port is found at slot:port:tributary (in these modules
slot:port=mux_eth_tdm). The digits in brackets (1 to 3) denote restrictions or
other special remarks regarding implementation of this loopback in specific
modules.
Table 6-13. Loopbacks Supported by Megaplex-4 E1 and E1-i Ports
E1 Ports (e1) Internal E1 Ports (e1-i)
M8E1 M16E1 OP-108C OP-108C/ OP-34C ASMi-54C/N CL.2 M8SL ASMi-54C/N,

Lopback Type E1 VS-16E1T1-EoP VS-16E1T1- SH-16/E1
VS-16E1T1-PW EoP
VS-6/E1T1
Local Loop √ √ √(1) √ √(1) √ √ – √
Remote Loop √ √ √ √ √ √ √ – √
Loop per TS
Local √ √ √(2) – √(2) √ √ √ √
Loop per TS
Remote √ √ √(2) – √(2) √ √ √ √
Local on
remote – – √ √ √ – – – √
Remote on
remote – – √ √ √ – – – √
Ber Test √ √ √ √ √ √ √ √ √
1 - Loopback on local and remote devices
2 - Only for local internal e1 ports.

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

Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
DS1 . SDH/
SONET
Mapper Matrix
Matrix .. Framer
..
.
E1-i/T1-i Framers
1
Remote loopback on
timeslots of 2
E1-i port ..
..
.
.
Local Loopback on E1-i Port

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

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

The local loopback on selected timeslots of an E1-i port is used to return the
transmit payload carried by the selected timeslots through the same timeslots of
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.
This test is recommended for testing the signal paths between the E1-i port and
an I/O port of another module that uses only a fraction of the available E1-i port
bandwidth.

As shown in Table 6-14, the loopback is activated only on the timeslots specified
by the user during the activation of the loopback. As a result, there is no
disturbance to services provided by means of the other timeslots of the same
E1-i port, only the flow of payload carried by the specified timeslots is disrupted.
The user can activate the loopback on any individual timeslot, or on several
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
cross-connected with HDLC ports.
Remote Loopback on E1-i Port Timeslots

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

DS1
(M8E1, M16E1, ASMi-54C/N, OP- Port Cross-Connect
Interface
108C/E1, SH-16/E1, VS-16E1T1- Matrix
EoP, OP-108C, OP-34C modules)
"1 "
Remote loopback on E1/E1-i port

(M8E1, M16E1, ASMi-54C/N, OP- DS1
Port
108C/E1, SH-16/E1, VS-16E1T1- Interface
Cross-Connect
Matrix
EoP, OP-108C, OP-34C modules)

I/O CL
I/O Interface
Local loopback on E1/E1-i 1

timeslots (M8E1, M16E1, ASMi- 2
DS1
54C/N, SH-16/E1, VS-16E1T1-EoP, .. Cross-Connect
.. Matrix
OP-108C, OP-34C modules) .
I/O Interface
Remote loopback on E1/E1-i 1

timeslots (M8E1, M16E1, ASMi- 2 DS1
54C/N, SH-16/E1, VS-16E1T1-EoP,
.. Cross-Connect
.. Matrix
OP-108C, OP-34C modules) .
Local Loopback on E1 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 port: this path starts at the other Megaplex-4
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-15, when a local loopback is activated, the port transmit
signal is returned to the input of the same port receive path at a point just
before the line interface. The local port must receive its own signal, and thus it
must be frame-synchronized. In addition, each I/O module connected to the
corresponding port must also receive its own signal. In general, the result is that
these modules are synchronized and do not generate alarm indications.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed “all-ones” signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on E1 Port of I/O Module

The remote port loopback is used to test the line interface circuits of a selected
E1 external port. This test also checks the transmission plant connecting the
equipment connected to the corresponding port.
As shown in Table 6-15, when a remote loopback is activated on an E1 port, that
port returns the received signal to the remote unit, via the transmit path. The
received signal remains connected as usual to the receive path of the
corresponding port. To correct transmission distortions, the returned signal is
regenerated by the corresponding line interface circuits.

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-4 unit also operated normally when the local port loopback
was activated, then while the remote loopback is connected the local unit should
receive a valid signal, and thus it must be frame-synchronized.
The remote port loopback should be activated at only one of the units connected
in a link, otherwise an unstable situation occurs.
Local Loopback on Timeslots of E1 I/O Module Port

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

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

Megaplex-4 features local and remote E1 loopbacks on the remote Optimux
devices connected to optical links of its OP-108C and OP-34C modules.

A typical signal flow for a local loopback on an E1 port of a remote Optimux is

shown in Figure 6-3. The remote Optimux device can be one of the following:
• Optimux-108/108L connected to OP-108C module (Section A or B)
• Optimux-34 connected to OP-34C module.
The number of E1 ports is 4 for Optimux-108/108L and 16 for Optimux-34.
Megaplex-4100 Remote Optimux

"1"
CL
LIU 1 E1
.
Port 1
. .
Uplink Uplink E1 Payload
. .
Other Port
Interface
Routing
Matrix
E1 Payload
Mux/Demux Interface Interface Mux/Demux
. .
.
E1
LIU 4 Port
4(16)
Figure 6-3. Typical Signal Flow for E1 Port Local Loopback on Remote Optimux Device
When a local loopback on an E1 port of the connected Optimux is activated by an
OP module command, the E1 port transmit signal is returned to the input of the
port receive path (the E1 port signal is disconnected from the transmit path and
is replaced by an AIS signal).
While the loopback is activated, the tested Optimux port will receive its own
signal, and therefore must operate normally. In addition, the user equipment
connected to the tested E1 port must also receive its own signal and thus it must
be synchronized.
This test checks the operation of the far end Optimux E1 port interface, and the
connections to the E1 equipment attached to the far end E1 port.
A typical signal flow for a remote loopback on an E1 port of a remote Optimux is
shown in Figure 6-4.
Megaplex-4100 Local OP-34C or Remote Optimux

"1"
OP-108C Section
CL
LIU 1 E1
..
Port 1

.. .
Other Port
Interface
Routing
Matrix
E1 Payload
. ..
LIU 4 E1
Port 4
(16) (16)
Figure 6-4. Typical Signal Flow for E1 Port Remote Loopback on Remote Optimux
When a remote loopback on an E1 port of the connected Optimux is activated by
an OP module command, the received E1 signal is returned to the input of the
port transmit path after being processed by the internal E1 port, and is
transmitted back to the OP module (the E1 port signal is disconnected from the
receive path and is replaced by an AIS signal).

Therefore, the corresponding internal E1 port of the OP module receives its own
signal, and it must operate normally. In addition, the OP module user equipment
connected via the tested E1 port must also receive its own signal and thus it
must be synchronized.
This test checks the connections between the user’s E1 equipment connected via
the tested internal E1 port of the local OP module, the operation of the OP
module link (section) and of the remote Optimux, and the network connections
between the local OP module and the remote Optimux.
Note The same loopback can be activated/deactivated by a supervision terminal

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

Tested
asmi52* (ASMi-52 or remote-on-remote E1 Figure 6-5

ASMi-52L standalone) local-on-remote Figure 6-6
asmi52-e1-eth* (ASMi- remote-on-remote E1 Figure 6-5

52 standalone with E1 local-on-remote Figure 6-6
and LAN ports (Mux
type))
asmi52-e1-dte* (ASMi-52 remote-on-remote serial Serial Figure 6-5

standalone with E1 and local-on-remote serial Serial Figure 6-6
serial ports (Mux type))
remote-on-remote e1 E1 Figure 6-5
local-on-remote e1 E1 Figure 6-6
high-speed-mux-serial-e1 remote-on-remote Odd e1-i ports of the I/O Figure 6-5

(ASMi-52/53 standalone local-on-remote module = loopback on E1 Figure 6-6
with E1 and serial ports ports of remote modem
(Mux type), 4M/4W Even e1-i ports =
functionality) loopback on Serial ports
of remote modem
asmi54 (ASMi-54 or remote-on-remote E1 ports Figure 6-5

ASMi-54L standalone) local-on-remote E1 ports Figure 6-6

Far-end-type Loopback Far-end Device Ports Figure

Tested
managed (ASMi-54L remote-on-remote E1 ports Figure 6-5

standalone configurable local-on-remote E1 ports Figure 6-6
via EOC or ASMi-53)
*ASMi-54C/N only
Note
Only one loopback at a time can be activated from Megaplex-4. At any moment
the last loopback command is valid and overrides the previous loopback
command.
Figure 6-5 shows the signal paths of a typical remote loopback on the remote
ASMi modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
The loopback is activated within the user interface of the remote modem, which
returns the received data through the transmit path.
Megaplex-4100/4104 Remote
Loopback
CL ASMi-54C/N ASMi-52/54
E1 or DTE
Routing Port e1-i 1
Matrix .. E1 or Serial
.. .. Port*
Other Port Bus ..
Interface Interface .. *When far-end-type=high-speed-
. .. mux-serial-e1, loops on ASMi E1
ports are activated from odd e1-i
Port e1-i 8 ports and loops on ASMi serial
ports - from even e1-i ports
Figure 6-5. Remote Loopback on Remote Unit, Signal Paths
Local Loopback on Remote Unit

Figure 6-6 shows the signal paths of a typical local loopback on the remote ASMi
modem.
Depending on the modem type, the loopback is performed on the E1 or serial
port of the remote modem and tests the E1/serial traffic passing on the SHDSL
line, leaving aside Ethernet traffic related to this line.
When this loopback is activated, the selected port sends a local loopback request
to the remote modem connected to that channel. The command is sent through
the inband eoc channel configured on the remote modem.

Megaplex-4100/4104 Local
Loopback
CL ASMi-54C/N ASMi-52/54
E1 or DTE
Routing Port e1-i 1
Matrix .
. . E1 or Serial
Other Port Bus . .. Port*

Interface
.. . *When far-end-type=high-speed-
Interface .
. . mux-serial-e1, loops on ASMi E1
. ports are activated from odd e1-i
Port e1-i 8 ports and loops on ASMi serial
ports - from even e1-i ports
Figure 6-6. Local Loopback on Remote Unit, Signal Paths
BER Test
The BER test, activated by the command bert, is used to evaluate data
transmission through selected timeslots of the link connected to a selected E1 or
E1-i port without using external test equipment. It is available on the following
ports:
• E1 ports of ASMi-54C/N and M16E1 modules
• E1-i ports of ASMi-54C/N and SH-16/E1 modules.
Data transmission is checked by applying a test sequence generated by an
internal test sequence generator towards the remote equipment. The timeslots in
which the sequence is transmitted, are defined by means of the bert command.
The test sequence is 2E-15.
To check that the line is alive or verify the BER detection calibration, the user can
also inject single errors into the transmitted pattern.
The BER Test on unframed ports is performed per port, while on framed ports it
is performed also per individual timeslot.
The timeslot on which BERT is performed must be cross-connected.
The transmitted data is returned by means of a loop, somewhere along the data
path, to the test sequence evaluator. The evaluator compares the received data,
bit by bit, to the original data and detects any difference (bit error). The output
of the evaluator is sampled during module polling, to check whether errors were
detected in the interval between consecutive pollings.
The number of errors is accumulated from the activation of the BER test.
The test results are displayed on a supervision terminal as a number in the range
of 0 (no errors detected during the current measurement interval) through
63535. The meaning of the displayed parameters is given in the table below.
The BER test duration is infinite (to stop the test manually, use no bert
command).
Table 6-17. Bert Performance Parameters
Status Displays the BERT status: Not Active, In Sync or Out of Sync

Run Time (Sec) Displays the total time the test is running in seconds
Sync Loss (Sec) Displays the number of times Sync Loss was detected since BERT
started to run
Bert Error Count Displays the total number of bit errors detected
Pattern Displays the BERT pattern (always 2e-15)
ES (Sec) Displays the total number of seconds in which errors have been
detected
Loopback Duration
by the Megaplex-4. Therefore, when you initiate a loopback, you have the option
to limit its duration to an interval in the range of 1 through 30 minutes.
After the selected interval expires, the loopback is automatically deactivated
activated on the local Megaplex-4 before this timeout expires. When using inband
Activating Loopbacks and BER Tests
 To perform a loopback or BER test on the E1 port:

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

 To perform a loopback or BER test on the internal E1 port:

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

Activating and configuring loopback {local | remote} [time-slot local – local loopback (per port and per
the direction of the loopback <1..31>] [duration <duration in timeslot)
(all modules) minutes 1..30> ] remote – remote loopback (per port and
per timeslot)
For additional loopbacks on e1-i ports of
ASMi-54C/N modules, see two table rows
below.
Activating and configuring loopback { remote-on-remote | remote-on-remote – remote loopback on

the direction of the loopback local-on-remote } [duration remote ASMi modem
(additional loopbacks on e1-i <duration in minutes 1..30> ] local-on-remote – local loopback on
ports of SH-16/E1 and remote ASMi modem
ASMi-54C/N modules, any
far-end-type except
asmi52-e1-dte)
Activating and configuring loopback { remote-on-remote serial remote-on-remote serial – remote

the direction of the loopback <port-number> | local-on-remote loopback on serial port of remote
(additional loopbacks on e1-i serial <port-number> | remote-on- ASMi-52/53 (E1+DTE) modem
ports of ASMi-54C/N, far- remote e1 <port-number> | local- local-on-remote serial – local loopback on
end-type = asmi52-e1-dte, on-remote e1 <port-number> } serial port of remote ASMi-52/53 (E1+DTE)
and SH-16/E1 modules, far- [duration <duration in minutes modem
end-type = non-manage ) 1..30> ]
remote-on-remote e1 – remote loopback
on E1 port of remote ASMi-52/53
(E1+DTE) modem
local-on-remote e1 – local loopback on E1
port of remote ASMi-52/53 (E1+DTE)
modem
Activating the BER test and bert [ts <ts number 1..31>] [inject- The [ts <ts number in the range from 1 to
configuring its parameters error single] 31>] command is used only for framed
ports and is mandatory for these ports.
The timeslot on which BERT is performed
must be cross-connected.
CL flip stops the BERT session.
Stopping the BER test no bert
Displaying the BER test show bert A typical display:

results Status : Not Active
Bit Error Count: 1
Pattern : 2e-15
Run Time (Sec) : 1
ES (Sec) : 1
Sync Loss (Sec): 1
Clearing the BER test clear-bert-counters
counters

 To perform a loopback on the E1 port of the remote Optimux:

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

• 1 or 3 for OP-108C
• 1 for OP-34C
Remote devices connected to protection ports 2 and 4 cannot be configured.
The config>port>mux-eth-tdm>(<slot>/<port>)# prompt is displayed.

2. Type remote.
3. Type configure port e1 <port> to select the E1 port of the remote device to
be tested.

• 1 to 4 for Optimux-108/108L
• 1 to 16 for Optimux-34.
Activating and configuring the loopback {local | remote} local – local loopback:
Displaying E1 Port Statistics

E1 and E1-i ports of Megaplex-4 feature the collection of statistical diagnostics
per relevant parts of ITU-T G.826, thereby allowing the carrier to monitor the
transmission performance of the links.
 To display the E1 port statistics:

• At the prompt config>slot>port>e1(<slot><port>[<tributary>])#, enter show
statistics followed by the parameters listed below.

 To display the E1-i port statistics:

• At the prompt config>slot>port>e1-i(<slot><port>)#, enter show statistics
followed by the parameters listed below.

Displaying statistics show statistics {total | all | current} • total –total statistics of last 96
intervals
• current –current statistics
• all –all statistics: first current
statistics, then statistics for all
valid intervals, and finally total
statistics
Displaying statistics show statistics interval <interval-num 1..96>

for a specific
interval
E1 port statistics are displayed.
Note BES, LOFC and Rx Frames Slip are displayed for framed formats only.
For example:
Current statistics:
mp4100>config>port>e1(1/2)# show statistics current
Current
---------------------------------------------------------------
Time Elapsed (Sec) : 191
Valid Intervals : 2
ES : 0
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Statistics for interval 67:
mp4100>config>port>e1(3/1)# show statistics interval 67
Interval Number : 67
Interval
---------------------------------------------------------------
ES : 16
SES : 1
UAS : 589
BES : 0
Rx Frames Slip : 0
LOFC : 0
Total statistics:

mp4100>config>port>e1(1/2)# show statistics total

Total
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
All statistics:
mp4100>config>port>e1(1/2)# show statistics all
Current
---------------------------------------------------------------
Valid Intervals : 2
mp4100>config>port>e1(1/2)#
ES : 0
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Interval Number : 1
Interval
---------------------------------------------------------------
ES : 0
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Interval Number : 2
Interval
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Total
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
The counters are described in Table 6-18, Table 6-19 and Table 6-20.

Table 6-18. E1 Port Statistics Parameters – Current 15-Minute Interval
ES Displays the number of errored seconds in the current 15-minute interval.

An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
UAS Displays the number of unavailable seconds (UAS) in the current interval.
An unavailable second is one of the following:
• 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.
SES Displays the number of severely errored seconds (SES) in the current interval.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
LOFC Displays the number of LOFC in the current interval.

The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip Displays the number of Rx Frames Slips in the current 15-minute interval.
A CSS is a second with one or more controlled slip events.
Time elapsed The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds.
Valid Intervals The number of elapsed finished 15-min intervals for which statistics data can be
displayed, in addition to the current (not finished) interval (up to 96).
Table 6-19. E1 Port Statistics Parameters – Selected 15-Minute Interval
ES Displays the total number of errored seconds (ES) in the selected interval
UAS Displays the total number of unavailable seconds (UAS) in the selected interval
SES Displays the total number of severely errored seconds (SES) in the selected interval
BES Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number The number of interval for which statistics is displayed.

Note: The sequence of intervals is different for the E1 ports of different module
families:
• For the M8E1 modules, Interval #1 is the latest in time
• For the M16E1, ASMi-54C/N, SH-16/E1, OP-108C and OP-34C modules, Interval #1
is the earliest in time.

Table 6-20. E1 Port Statistics Parameters – Total Statistics
ES Displays the total number of errored seconds (ES) since statistics are available
UAS Displays the total number of unavailable seconds (UAS) since statistics are available
SES Displays the total number of severely errored seconds since statistics are available
BES Displays the total number of bursty errored seconds (BES) since statistics are available
LOFC Displays the total number of loss of frame alignment events since statistics are available
Rx Frames Slip Displays the total number of loss of of Rx Frames Slip events since statistics are
available
Clearing Statistics
 To clear the statistics for an E1 port:

• At the prompt config>port>e1<slot>/<port>)#, enter clear-statistics.
 To clear the statistics for an E1-i port:

• At the prompt config>port>e1-i<slot>/<port>)#, enter clear-statistics.
Mux-Eth-Tdm Ports (Fiber Optic Links of Optimux Modules)
Applicable Modules
Mux-eth-tdm ports denote fiber optic links of Optimux modules.
Each Optimux module link has two optical ports, which can be operated as a
protection group, to enhance service availability to critical users. The service
provider can control each standalone unit through the link connecting the unit to
the Optimux module, and therefore can manage a large number of standalone
units from a central location.
OP-108C comprises two identical independently-operating sections, identified as
OP A and OP B, each of which is capable of multiplexing four independent internal
E1 data streams and up to 100 Mbps of Ethernet payload for transport over a
fiber-optic link. OP-34C has a single section capable of multiplexing 16
independent internal E1 data streams and up to 32 Mbps of Ethernet payload for
transport over a fiber-optic link.
In addition to its own OP modules, Megaplex-4 can also operate with similar
modules initially designed for operation in the LRS-102 chassis. The difference
between the Megaplex and LRS modules is in the type of E1 ports:
• Megaplex modules have internal E1 ports, and can be connected to other
ports within Megaplex-4 via the chassis TDM buses

• LRS modules have external E1 ports which can be connected only to external
users, but cannot be connected to other ports within Megaplex-4 via the
chassis TDM buses.
In the CLI, LRS-102 modules are identified by “-e1” at the end of the module
name: for example, the LRS-102 OP-108C (OP-108C/E1) module is identified as
op108c-e1.
The following table shows the number of mux-eth-tdm ports on Megaplex-4 and
LRS-102 I/O modules.
Table 6-21. Mux-Eth-Tdm Ports
Module Number of Ports
OP-108C, OP-108C/E1 4:
• 2 for Section OP A (mux-eth-tdm 1 main,
mux-eth-tdm 2 redundant)
• 2 for Section OP B (mux-eth-tdm 3 main,
mux-eth-tdm 4 redundant)
OP-34C 2 (mux-eth-tdm 1 main, mux-eth-tdm 2 redundant)
Standards
Fiber optic links of Optimux modules are RAD proprietary technology.
The link interface subsystem of each Optimux module section includes a link
redundancy switch, and two independent link interfaces (one for each link port)
with SFP sockets.
The link redundancy switch operates as follows:
• When only one SFP is installed, only one link port is active. The link
redundancy switch then connects the link mux/demux to this port.
• When both SFP are installed, but redundancy is disabled, the link redundancy
switch connects the link mux/demux to the first port (LINK 1 or LINK 3 in
OP-108C, OP-108C/E1, LINK 1 in OP-34C).
• When both SFP are installed, and redundancy is enabled, the link redundancy
switch connects the link mux/demux to the port selected as the primary port
of the corresponding link. When signal loss is detected by the primary port,
the switch transfers the traffic to the other (secondary) port.
Each link interface performs the following functions:
• The transmit path converts the link data and the associated clock signal
provided by the link mux/demux to the signals needed to drive the SFP that
provides the physical interface of each port, for transmission to the far end
equipment.
• The receive path recovers the link data stream received from the far end
equipment, and the associated clock, and provides the data and clock to the
link mux/demux.

The link interfaces accept a wide range of SFPs, and therefore the performance
depends on the installed SFP model. RAD offers a wide range of SFPs to meet a
wide range of system requirements. The fiber-optic interfaces can operate over
62.5/125 micron multi-mode, or 9/125 micron single-mode fibers (typical
attenuation of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm). The offered SFPs include models that need a single fiber instead of the
customary two fibers; for example, WDM models SF1 and SF2 operating at two
different wavelengths, or the SF3 model with SC/APC (angled polished connector)
that operates at a single wavelength.
Note It is strongly recommended to order OP modules with RAD SFPs installed: this will
ensure that prior to shipping RAD has performed comprehensive functional
testing on the assembled module, including SFPs. Although users can install their
own SFPs into OP modules, RAD cannot guarantee full compliance to product
specifications when using non-RAD SFPs, and cannot be held responsible for any
damage that may result if non-compliant transceivers are used. In particular,
users are warned to use only agency approved SFPs that comply with the local
laser safety regulations for Class 1 laser products.
Table 6-22 provides information on the characteristics of the SFPs offered by

RAD, together with typical maximum ranges (calculated assuming typical fiber
attenuations of 3.5 dB/km at 850 nm, 0.4 dB/km at 1310 nm, and 0.25 dB/km at
1550 nm, and a 3-dB margin).
All the fiber-optic interface options offer high performance and have a wide
dynamic range, which ensures that the receiver will not saturate even when using
short fiber-optic cables. (Saturation is caused when the optical power applied to
the receiver exceeds its maximum allowed input power, and results in very high
bit error rates.)
Table 6-22. Link Port Interface Characteristics
Module Transmitter Connector Fiber Type Typical Receiver Typical Range

Name Type and Type Output Sensitivity
Wavelength Power
[nm] [dBm] [km] [miles]
[dBm]
SFP-1 LED, 1310 LC 62.5/125 Multimode -18 -31 6.5 4.0
SFP-2 Laser, 1310 LC 9/125 Single mode -12 -31 38 23.6
SFP-3 Long haul LC 9/125 Single mode -2 -34 70 43.4

laser, 1310
SFP-4 Long haul LC 9/125 Single mode -2 -34 120 74.5

laser, 1550
SFP-10a Laser WDM, LC 9/125 Single mode -12 -30 40 24.8

Tx –1310, Rx – (single fiber)
1550
SFP-10b Laser WDM, LC 9/125 Single mode -12 -30 40 24.8

1310

Module Transmitter Connector Fiber Type Typical Receiver Typical Range

Name Type and Type Output Sensitivity
Wavelength Power
[nm] [dBm] [km] [miles]
[dBm]
SFP-18A Tx – 1310, Rx LC 9/125 single mode -2 -30 60 37.3

– 1550 (single fiber)
SFP-18B Tx – 1550, Rx LC 9/125 single mode -2 -30 60 37.3

– 1310 (single fiber)
SFP-19A Laser WDM, LC 9/125 single mode -8 -30 80 49.7

1570
SFP-19B Laser WDM, LC 9/125 single mode -8 -30 80 49.7

Tx –1570/Rx – (single fiber)
1490
SFP-24 VCSEL LC 62.5/125 Multimode -7 -31 6.5 4.0
The OP-34C, OP-108C modules (Megaplex-4) and the OP-108C/E1 modules

(LRS-102) can be connected to remote standalone Optimux units, or to other
modules installed in the Megaplex-4 or LRS-102 chassis via fiber optic links.
Factory Defaults
Megaplex-4 is supplied with all mux-eth-tdm ports disabled. The default far-end-
type value is no far-end-type.
Configuring Optical Link Parameters and Accessing the

Remote Unit
Configuring the Local Optical Link
 To configure the optical link parameters:

5. Navigate to configure port mux-eth-tdm <slot>/<port> to select the port to
configure.

• 1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively. To use links 2
and 4 as protection links they must be set manually to “no shutdown”.


description to port

port
See Table 6-23 for device definitions

Specify the type of far far-end-type {op-108 | op-108-eth | mp- and possible interconnections.
end equipment lrs-card | op-34 | op-34-v35 | op-xl-
connected to this port Using no far-end-type removes the
e1 | op-xl-t1 | op-xl-e1-16 | other | op-
name
108l | op-108l-eth}
Assigning short far-end-name <string> Using no far-end-name removes the

description to the remote name
port connected to this
link
Once the remote device has been

Accessing
accessed by this command, you can
the remote device remote
activates loopbacks and configure
connected to the uplink
parameters of the remote device
Table 6-23. Far End Devices
Local Device Remote Device Description
OP-108C, OP-108C/E1 no far-end-type No far end equipment is connected
op-108 Optimux-108 or Optimux-108L standalone unit without

Ethernet ports
op-108-eth Optimux-108 or Optimux-108L standalone unit with

Ethernet ports
op-108l Optimux-108L/BM standalone unit without Ethernet

ports
op-108l-eth Optimux-108L/BM standalone unit with Ethernet ports
mp-lrs-card OP-108C card installed in another Megaplex-4 or

OP-108C/E1 card installed in an LRS-102 or in another
Megaplex-4
other Other type of equipment compatible with OP-108C.
For OP-34C no far-end-type No far end equipment is connected
op-34 Optimux-34 standalone unit with 16 E1 ports and one

user Ethernet port with configurable throughput rate
op-xl-e1 Optimux-XLE1 standalone unit with 12 E1 ports and one

user Ethernet port providing a fixed throughput rate of
8 Mbps
op-xl-e1-16 Optimux-XLE1/16 standalone unit

Local Device Remote Device Description
op-34-v35 Optimux-34 standalone unit with 16 E1 ports, one V.35

port, and one user Ethernet port with configurable
Ethernet throughput rate
mp-lrs-card OP-34C card installed in another Megaplex-4
other Other type of equipment compatible with OP-34C.
Configuring the Remote Optimux

To configure the remote Optimux ports, you must first access the remote unit.
 To access the remote unit:


• 1 for OP-34C
Ports 2 and 4 serve for protection of links 1 and 3, respectively, and cannot be
configured.

2. Type remote.
Now you are at the remote Optimux context and can configure the
followings ports:
 Management Ethernet port
 User Ethernet port
 Optical link
 E1 ports.
 To configure the remote Optimux management Ethernet port parameters:

1. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type
configure port mng-eth 1. (There is only one management Ethernet port on
any Optimux standalone device.)
 To configure the remote Optimux user Ethernet port parameters:

configure port eth 1. (There is only one management Ethernet port on any
Optimux standalone device.)

Assigning short description to name <string> Using no name removes the name
port
Enabling autonegotiation auto-negotiation Using no auto-negotiation disables

autonegotiation
Setting maximum advertised max-capability {100-full-duplex } 100-full-duplex – 100baseT full duplex

capability (highest traffic This parameter applies only if
handling capability to be autonegotiation is enabled and is
advertised during the always 100-full-duplex. When
autonegotiation process) autonegotiation is disabled, this
parameter is replaced by speed-duplex.
This parameter is not relevant for the
Ethernet management port.
Setting data rate and duplex speed-duplex {10-full-duplex | 10-full-duplex –10baseT full duplex
mode of the Ethernet port, 100-full-duplex |10-half-duplex 100-full-duplex – 100baseT full duplex
when autonegotiation is |100-half-duplex }
10-half-duplex – 10baseT half duplex
disabled
100-half-duplex – 100baseT half
duplex.
When autonegotiation is enabled, this
parameter is replaced by max-capability.
Setting flow control for the flow-control Using no flow-control disables flow
selected port (when operating control
in the full duplex mode), or
back pressure (when operating
in the half-duplex mode)
Activating/deactivating a policer-profile <name> The policer profile for ingress rate

policer profile to set ingress limitation is defined under qos (see
rate limitation (user port only) Configuring Policer Profiles in
Chapter 8).
Using no policer <name> deactivates
this policer profile
 To configure the remote Optimux optical link parameters:

configure port mux-eth-tdm <port 1..2> to select the optical link of the
remote device to be tested.
to port


port
 To configure the remote Optimux E1 parameters:

1. Under the config>port>mux-eth-tdm>(<slot>/<port>)#remote# context, type:
configure port e1 <port>.

• 1 to 4 for each section for Optimux-108/108L
• 1 to 16 for Optimux-34.

description to port

port
Specifying port interface-type {balanced | unbalanced}

impedance used by the
E1 port
Example
The following section illustrates how to configure the remote Optimux-108
connected to port 3 of local OP-108C module installed in slot 1:
• Administratively enable the optical links, Ethernet port and all E1 ports.
• Leave their parameters at their defaults.
configure port mux-eth-tdm 1/3 remote
configure port mux-eth-tdm 1 no shutdown
configure port mux-eth-tdm 2 no shutdown
configure port ethernet 1 no shutdown
configure port e1 1 no shutdown
exit-remote
exit all
The table below lists messages generated by Megaplex-4 when a configuration
error on modules with mux-eth-tdm ports (OP-108C/OP-34C) is detected.

Table 6-24. OP-108C/OP-34C Configuration Error Messages
500 Warning FAR-END CHANGED, DEVICE The type of far-end device connected to the OP-108C
WILL RESTART module is different from the one configured. The module
will perform a reset.
501 Error NOT IDENTICAL FAR-END When two far end devices are connected to the OP-108C
DEVICE TYPE module, they must be identical.
502 Error PORT ASSIGNED TO The optical link (mux-eth-tdm port) status is set to
DISCONNECTED LINK shutdown, while the corresponding E1 or Ethernet ports
are configured as “no shutdown”.
503 Error ETH RATE & E1/T1/TRIBUTARY The far-end user Ethernet port rate exceeds the available
RATE MISMATCH link bandwidth. Increase the bandwidth by reducing the
number of active E1 ports
Viewing Optical Link SFP Status Information

For viewing the status of the optical link SFP, follow the instructions below.
 To view the status of a local optical link SFP:

1. Navigate to mux-eth-tdm (<slot>/<port>)#
2. Type show sfp-status.
mp4100>config>port>mux-eth-tdm(11/3)# show sfp-status
SFP
---------------------------------------------------------------
Connector Type : LC
Manufacturer Name : WTD
Manufacturer Part Number : RTXM139-BG-RAD
Wave Length (nm) : 1310
Fiber Type : SM
SFP
---------------------------------------------------------------
Current Minimum Maximum
RX Power (dBm) : 0.0 dBm
TX Power (dBm) : 0.0 dBm
Laser Bias (mA) : 0.0 mA
Laser Temperature (Celsius) : 0.0 C
Power Supply (V) : 3.3 V
The performance monitoring data for the OP module link physical layer includes
status data for each link port, and SFP data for the installed SFPs. Table 4-4
explains the parameters of the SFP installed for selected link port.

Table 4-4. Link SFP Parameters
Connector Type Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name Displays the original manufacturer’s name
Vendor PN Displays the original vendor’s part number
Typical Max. Range Displays the maximum range expected to be achieved over typical optical fibers, in
(Meter) meters
Wave Length (nm) Displays the nominal operating wavelength of the SFP, in nm
Fiber Type Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm) Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm) Displays the current optical power, in dBm, received by the SFP
Laser Bias (mA) Displays the measured laser bias current, in mA
Laser Temperature Displays the measured laser temperature, in °C

(Celcius)
Power Supply (V) Displays the SFP power supply voltage
For displaying protection status, see Example 2 in TDM Group Protection section
in Chapter 7.
Testing Optical Links

The test and diagnostics functions available on each optical link are:
• Local loopback on local OP module link
• Remote loopback on local OP module link
• Local loopback on remote Optimux unit (OP module only, with limited
duration)
• Remote loopback on remote Optimux unit
Local Loopback on Local Optical Link

A typical signal flow for a local loopback on the local OP module link is shown in
Figure 6-7. Note that AIS is sent to the link as shown in Figure 6-7 only when the
far end device configured for the tested section is a basic Optimux unit (with E1
ports only); when the far end device includes an Ethernet port, a special pattern
is sent, and the Ethernet ports (both on the tested section of the local OP
module, and on the remote Optimux) are shut down for the duration of the test.

Megaplex-4100
OP-108C Section
CL or OP-34C
Other Port Routing E1 Payload

Interface Matrix Mux/Demux Uplink
Link Interface
Mux/Demux
Figure 6-7. Signal Flow for Link Local Loopback on Local OP Module
When a link local loopback is activated on an OP module, the link transmit signal
is returned to the input of the link receive path at a point just before the uplink
interface. The local link receive path will receive its own signal, and therefore
must operate normally.
In addition, user equipment connected via each E1 internal port served by the
corresponding link must also receive its own signal and thus it must be
synchronized.
This test checks the operation of the local OP link (section), and the connections
to the E1 equipment attached via local internal E1 ports.
Remote Loopback on Local Optical Link

A typical signal flow for a remote loopback on the local OP-108C link is shown in
the figure below.
Megaplex-4100
OP-108C - OP-A Section
CL
Other Port Routing E1 Payload Uplink

Interface Matrix Mux/Demux Interface
Link
Mux/Demux
Figure 6-8. Signal Flow for Link Remote Loopback on Local

OP Link
When a link remote loopback is activated on an OP module, the received link
signal is processed by the uplink interface, returned to the input of the link
transmit path at a point just before the uplink interface, and transmitted back to
the far end device. Therefore, the far end device receives its own TDM signal, and
its TDM paths must operate normally.
During the test, the local link receive path supplies AIS signals to each local
internal E1 port.

This test checks the connections between the user E1 equipment attached to the
E1 ports of the far end device, the operation of the far end device, the uplink
interface of the local OP module (module section), and the network connections
between the local OP module and the far end device.
Link Local Loopback on Remote Optimux

A typical signal flow for a local link loopback on the remote Optimux-108/108L is
shown in Figure 6-9. Note that AIS is sent to the link as shown in Figure 6-9 only
when the far end device connected to the tested section is a basic Optimux (with
E1 ports only).
The link local loopback signal path on the remote Optimux is shown in Figure 6-9.
Megaplex-4100 Local OP-108C Section Remote Optimux
CL
LIU 1 E1
..
Port 1
Other Port Routing E1 Payload Uplink Uplink E1/ Payload

.. .
Interface Matrix Mux/Demux Interface Interface Mux/Demux
. .
"1" LIU 4
.
E1
Port 4
(16) (16)
Figure 6-9. Typical Signal Flow for Link Local Loopback on Remote Optimux
When a link local loopback is activated by an OP module command on the
connected Optimux, the Optimux link transmit signal is returned to the input of
its link receive path within the uplink interface. The Optimux link receive path will
receive its own signal, and therefore must operate normally.
In addition, user equipment connected to each OP module E1 port served by the
link must receive an AIS signal.
Ethernet traffic will not be disrupted while the loopback is activated.
This test checks the operation of the far end Optimux, and the connections to
the E1 equipment attached to the far end E1 ports.
This test is possible for OP-108C only with limited (not infinite) duration and not
available for OP-34C.
Link Remote Loopback on Remote Optimux

A typical signal flow for a link remote loopback is shown in Figure 6-10. Note that
AIS is applied only when the far end device connected to the tested section is a
basic Optimux (with E1 ports only). Ethernet traffic will not be disrupted while the
loopback is activated.

Megaplex-4100 Remote Optimux
CL
LIU 1 E1
"1"
..
Port 1

.. .
Other Port
Interface
Routing
Matrix
E1 Payload
. ..
LIU 4 E1
Port 4
(16) (16)
Figure 6-10. Typical Signal Flow for Link Remote Loopback on Remote Optimux
When a link remote loopback is activated on an Optimux, the received link signal
is processed by the uplink interface, returned to the input of the link transmit
path, and transmitted back to the local OP module. Therefore, the local OP
module receives its own TDM signal, and its TDM paths must operate normally.
In addition, user equipment connected via each local OP module internal E1 port
served by the corresponding link must also receive its own signal and thus it must
be synchronized.
This test checks the connections between the user E1 equipment attached to the
internal E1 ports of the local OP module, the operation of the local OP module,
the uplink interface of the far end device, and the network connections between
the local OP module and the far end device.
Loopback Duration
by the OP module. Therefore, when you initiate a loopback, you have the option
activated on the local module before this timeout expires. When using inband
 To perform a loopback on the local optical link:

link to be tested.

• 1 for OP-34C
Loopbacks on protection ports 2 and 4 (of the same kind as on links 1 and 3) are
activated automatically, provided the protection links are at “no shutdown”.

Activating and configuring the loopback {local | remote} local – local loopback
 To perform a loopback on the remote optical link:


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

2. Type remote.
3. Navigate to configure port mux-eth-tdm <port 1..2> to select the optical link
of the remote device to be tested.
Activating and configuring the loopback {local | remote} local – local loopback:
direction of the loopback and [duration <duration in minutes • not available for OP-34C
• for OP-108C available only when
the duration is not infinite
remote – remote loopback
Serial Ports
Applicable Modules
The following table shows the type and number of serial ports available on each
Megaplex-4 serial I/O module.
Table 6-26. Megaplex-4 Serial Ports
Module Type of Module Number of Ports
HS-6N, HS-12N n x 64 kbps high speed 6/12
HSU-6, HSU-12 ISDN “U” 6/12
HS-S ISDN “S” 4

HS-703 Codirectional data 4
HS-RN sub-DSO low speed 4
HSF-2 fiber optic teleprotection 2
LS-6N, LS-12 low speed 6/12
VS-6/BIN, VS-6/C37 versatile 6

VS-6/FXS, VS-6/FXO,
VS-6/E&M, VS-6/E1T1
VS-12 versatile 12
The following parameters can be configured for the serial ports:

• Port name
• Administrative status
• Clock mode
• Port data rate
• Size of the FIFO buffer used by the channel
• Port transmission mode
• Setting CTS line to track the state of the local RTS line
• Selecting the number of data bits/ stop bits and controlling the
end-to-end transfer of the parity bit in the asynchronous word format
• Selecting other parameters for specific kind of modules.
Table 6-27 summarizes the features available for serial ports of different I/O
modules. To configure a specific module, select its supported parameters in
Table 6-27 and then refer to Configuring Serial Port Parameters for configuration
instructions. In addition, consult the corresponding module section in Megaplex-4
I/O Modules Installation and Operation Manual for specific configuration
considerations.
Table 6-27. Features Supported by Megaplex-4 Serial Ports
Feature/Command HS-RN HS-6N/12N VS HS-S HS-U-6/12 HS-U-6/12 LS-6N, LS-12 HSF-2

“I” Mode “1” Mode
Number of ports 4 6/12 6/12 4 6/12 6/12 6/12 2
cmd-in* bri bri serial-bundle

cmd-out*
Additional ports – – cmd-ch* – –
Split TS cross-
connect (for serial
ports) √ – √ – – – – –
name √ √ √ √ √ √ √ √

Feature/Command HS-RN HS-6N/12N VS HS-S HS-U-6/12 HS-U-6/12 LS-6N, LS-12 HSF-2

“I” Mode “1” Mode
shutdown √ √ √ √ √ √ √ √
clock-mode √ √ – – – √ √ –
cts-rts √ √ √ – – – √ –
rate √ √ √ – – √ – √
fifo-size – √ – – – – – –
mode √ – √ – – √ √ –
encapsulation-mode √ – √ – – – – –
end-to-end-control √ – √ – – √ √ –
data-bits √ – √ – – √ √ –
parity √ – √ – – √ – –
stop-bits √ – √ – – √ – –
rate-adaptive – – – – – √ – –
interface – – √ √ √ – – –
activation-type – – – – √ – – –
*for VS-6/BIN modules
Standards
The Megaplex-4 serial ports comply with following standards:
• HS-703: ITU-T G.703, Codirectional interface
• LS-6N/LS-12 channel interface: ITU-T Rec. V.24/EIA RS-232, user-selectable
DCE or DTE
• LS-6N/LS-12 async-to-sync conversion method compatible with ITU-T Rec.
V.14
• HS-RN channel interface: ITU-T Rec. V.24/EIA RS-232, ITU-T Rec. V.110
• HSF-2: IEEE PC37.94 standard draft
• VS: Serial channels interface: V.35, V.11/RS-422, V.24/ EIA RS-232, ITU-T Rec.
V.110.
See corresponding section in Megaplex-4 I/O Modules Installation and Operation
Manual for each module.
Factory Defaults
Megaplex-4 is supplied with all serial ports disabled. Other parameter defaults are
listed in the table below.

clock-mode dce
HSF-2: 1x64
HSU-6/12: 1.2
rate HS-RN: 0.6
LS-6N/LS-12: 9.6
HS-6N/12N: T1: 1 x 56kbps, E1: 1 x 64kbps
fifo-size auto
mode sync
encapsulation-mode VS modules: none

HS-RN: bandwidth
cts-rts no cts-rts (disabled)
end-to-end-control no end-to-end-control (disabled)
data-bits 8 (HSU-6/12 modules:7)
parity no parity (disabled)
stop-bits 1
rate-adaptive proprietary
VS modules: v35
interface
HSU modules: nt
activation-type 1
Configuring Serial Port Parameters
 To configure the serial port parameters:

1. Navigate to configure port serial <slot>/<port> to select the serial port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.
to port

port

Configuring the clock mode HS-RN, HSU-6/12 (lt1 mode • dce – The port provides transmit and
in synchronous mode only): clock-mode receive clocks to the DTE
{dce|external-dce} • external-dce – The port provides the
HS-6N/12N, LS-6N/LS-12: receive clock to the DTE, and accepts the
clock-mode {dce | external- transmit clock from the DTE
dce | dte } • dte – The channel interface requires
transmit and receive clock signals from
the user’s equipment
In modules with sync/async operation this
selection is relevant only for synchronous
mode
Setting the data rate of this HS-6N/12N: rate {1 | 2 | 3 | 4 | The allowed range is n×56 kbps or n×64 kbps,
port in kbps. The selection 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | where n is 1 through 24 for a T1 link, and 1
depends on the module and 13 | 14 | 15 | 16 | 17 | 18 | 19 through 31 for an E1 link.
encapsulation type | 20 | 21 | 22 | 23 | 24 | 25 | In HS-6N/12N modules with V.24/RS-232
26 | 27 | 28 | 29 | 30 | 31} x interface, the data rate for all channels is
{56kbps | 64kbps} 64 kbps only.
HSF-2: rate {1x64 | 2x64 |

3x64 | 4x64 | 5x64 | 6x64 |
7x64 | 8x64 | 9x64 | 10x64}
HSU-6/12 (lt1 mode only): The available data rates depend on the port
rate {1.2 | 2.4 | 4.8 | 9.6 | 16 | transmission mode:
19.2 | 32 | 38.4 | 48 | 56 | • Synchronous mode: 1.2, 2.4, 4.8, 9.6, 16,
57.6 | 64 | 115.2 | 128} 19.2, 32, 38.4, 48, 56 (supported only
when connected to an ASMi-31 using
V.110 rate adaptation), 64 or 128 kbps.
• Asynchronous mode: 1.2, 2.4, 4.8, 9.6,
19.2, 38.4, 48, 57.6 or 115.2 kbps.
HS-RN: rate {0.6 | 1.2 | 2.4 | The supported range is as follows:

4.8 | 7.2 | 9.6 | 14.4 | 19.2 | ASYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
28.8 | 38.4 | 48 | 56 | 64} 14.4*, 19.2, 28.8*, or 38.4 kbps.
SYNC mode: 0.6, 1.2, 2.4, 4.8, 7.2*, 9.6,
14.4*, 19.2, 28.8*, 38.4, 56, or 64 kbps.
The rates marked by an asterisk (*) are
supported only by the HDLC-based model
When encapsulation-mode=latency, only
rates up to 19.2 kbps are supported, and the
required uplink bandwidth is always one full
timeslot. In sync mode, also 56 kbps and
64 kbps are supported.
When encapsulation-mode=3bit-transitional,
only 64 kbps is supported (rate is not
configurable).

LS-6N/LS-12: rate {2.4 | 4.8 | Determines the channel data rate, in kbps.
7.2 | 8 | 9.6 | 14.4 | 16 | 19.2 | Group 1: 2.4, 4.8, 9.6, 19.2, 38.4
24 | 28.8 | 32 | 38.4 | 48 | 56 |
Group 2: 7.2, 14.4, 28.8, 57.6
57.6 | 64}
Group 3: 8.0, 16.0, 24.0, 32.0, 48.0, 56.0,
64.0
Note: Both channels of a given pair must
operate at rates belonging to the same group.
Group 3 rates can be selected only on
channels using the synchronous protocol.
VS (encapsulation-
mode=none) : rate {1 | 2 | 3 |
4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18
| 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 |
31} x {56kbps | 64kbps}
VS (encapsulation-
mode=v110) : rate {2.4 | 4.8 |
9.6 | 19.2 | 38.4 }
VS (encapsulation-
mode=3bit-transitional) : rate
{1 | 2 } x 64kbps
Selecting the size of the fifo-size {auto | 16bit | 30bit | In general, you should select auto. The
FIFO buffer used by the 52bit | 72bit} automatically selected value depends on the
channel (HS-6N/12N only) channel data rate:
• ±16 bits for 64 kbps
• ±30 bits for 128 and 192 kbps
• ±52 bits for 256 through 320 kbps
• ±30 bits for 1856 and 1920 kbps
• ±16 bits for 1984 kbps.
For special applications that require longer
buffers, you may want to manually select one
of the supported FIFO sizes (±16 bits, ±30
bits, ±52 bits, or ±72 bits)
Selecting the port mode {sync | async} HS-RN: this command is irrelevant for
transmission mode (HS-RN, encapsulation-mode=3bit-transitional
HSU-6/12, LS-6N/LS-12, VS) VS: this command is relevant only for
encapsulation mode=v110.

Selecting the encapsulation encapsulation-mode {latency | Setting encapsulation mode per channel
mode for the HS-RN module bandwidth | 3bit-transitional } depends on the HS-RN hardware option:
• All the ports of the HS-RN/HDLC module
must use the same encapsulation mode.
This is done by forcing the last choice to
all the module ports.
• In the HS-RN/V.110 module, encapsulation
mode can be set independently per each
channel.
3bit-transitional mode is available only for
HS-RN/V.110 hardware option.
Selecting the encapsulation encapsulation-mode {v110 | This parameter defines the serial port
mode for the VS modules 3bit-transitional | none} behaviour of VS modules (see diagram in
Megaplex-4 I/O Modules Installation and
Operation Manual, Versatile Modules chapter,
Encapsulation Modes).
Setting CTS line to track the cts-rts HS-RN, HS-6N/12N, LS-6N/LS-12, VS modules
state of the local RTS line only
Using no cts-rts sets the CTS line continously
to on.
Configuring end-to-end end-to-end-control When configured, the state of the local RTS
control (VS, HS-RN, and DTR lines are reflected by the remote
HSU-6/12: lt1 mode) DCD and DSR line, respectively. For HS-RN, do
not use this selection for data rates
exceeding 38.4 kbps.
Using no end-to-end-control disables end-to-
end control. For HS-RN, always use this
selection for data rates exceeding 38.4 kbps.
When encapsulation-mode=3bit-transitional,
only the state of the local RTS line can be
transmitted end-to-end to the remote DCD
line, but not local DTR to the remote DSR
In VS modules, DTR and DSR lines are relevant
only for low-speed mode (encapsulation-
mode=v110).
In VS modules, in high-speed mode
(encapsulation-mode=none) this selection is
available only for n x 56 kbps data rates.

Configuring end-to-end end-to-end-control {rts | rts- rts – the state of the local RTS line is
control (LS-6N/LS-12) dtr} reflected by the remote DCD line
rts-dtr – the state of the local RTS and DTR
lines are reflected by the remote DCD and
DSR line, respectively
Using no end-to-end-control disables end-to-
end control (only local support is enabled)
Both channels of a given pair must be
assigned to support the matching control
signals.
Selecting the number of HS-RN, HSU-6/12, HS-S, VS: HSU-6/12: 5 or 6 data bits are supported only
data bits in the v110 encapsulation mode: when the remote equipment is an ASMi-31
asynchronous word format data-bits {5 | 6 | 7 | 8} using V.110 rate adaptation.
LS-6N/LS-12: data-bits {6 | 7 | LS-6N/12: The number is equal to the total
8 | 9} number of data and parity bits
HS-RN: this command is irrelevant for
encapsulation-mode=3bit-transitional
VS: this command is relevant only for
encapsulation mode=v110
Controlling the VS, HS-RN: parity Using no parity means that the parity bit is
end-to-end transfer of the HSU-6/12 (lt1 mode only), not transferred
parity bit in the HS-S: parity {odd | even} LS-6N/12: Parity is transparently transferred
asynchronous word format
HS-RN: this command is irrelevant for
encapsulation-mode=3bit-transitional
VS: this command is relevant only for
encapsulation mode=v110
Selecting the number of stop-bits {1 | 2} HS-RN: this command is irrelevant for

stop bits in the encapsulation-mode=3bit-transitional
asynchronous word format VS: this command is relevant only for
(VS, HS-RN, HSU-6/12, lt1 encapsulation mode=v110
mode only)
Selecting the multiplexing rate-adaptive {proprietary | • proprietary – RAD proprietary method

and rate adaptation method v110} based on ITU-T Rec. I.460
supported by the • v110 – Multiplexing and rate adaptation in
corresponding HS-U-6/12 accordance with ITU-T Rec. V.110
port (lt1 mode only)

Selecting the function and interface {lt | nt | te | lt1} Selections for HS-U-6/12 are:
mode of the HS-U-6/12/ • nt –port operates as a network
HS-S external port termination unit in the “I” mode.
• lt – port operates as a line termination
unit in the “I” mode.
• lt1– port operates as a line termination
unit in the “1” mode (used for connection
to NT equipment, such as ASMi-31).
Selections for HS-S are:
• te – terminal mode.
• nt – network termination mode.
Setting the physical interface {rs-232 | v35 |

interface type for VS rs-422}
modules
Selects the ISDN activation activation-type {1 | 2 | 3}

mode of an HS-U-6/12 port
configured for operation in
the nt mode
Example
The following section illustrates how to configure serial port 1 on the HS-6N
module installed in slot 5:
• Data rate 128 kbps.
• Set CTS line to track the state of the local RTS line
mp4100>config>port>serial(5/1)# rate 2 x 64kbps
mp4100>config>port>serial(5/1)# cts-rts
mp4100>config>port>serial(5/1)# no shutdown

This feature is available only for VS modules (card type=versatile). For viewing the
status of the VS serial ports, follow the instructions below.
 To view the status of a VS serial port:

1. Navigate to config>port> serial> (<slot>/<port>)#

mp4100>config>port>serial(3/7)# show status

Name : IO-3 serial 07
RTS : High
CTS : High
DCD : High
DTR : Low
DSR : High

 Loopback Type – Status of loopback activated on the port (None, Local,
Remote)
 State of control signals (High/Low)
Displaying VS Serial Port Statistics

Serial ports feature RAD proprietary statistical diagnostics. This feature is
available only for VS modules (card type=versatile) and for over-sampling mode
(encapsulation mode=3bit-transitional).
 To display the statistics of a serial port:

1. Navigate to config>port> serial> (<slot>/<port>)#
mp4100# config port serial 3/3
mp4100>config>port>serial(3/3)# show statistics
DTE Rx Counter : 609087
DTE Tx Counter : 0
WAN Rx Violation : 0
Table 6-28. VS Module Serial Port Statistics Parameters
DTE Rx Counter Number of data transitions on the input/output data wires since last reset or power-
up
DTE Tx Counter Number of data transitions on the input/output data wires since last reset or power-
up
WAN Rx Violation Number of 3-bit transitional protocol code violation since last reset or power-up

Clearing Statistics
 To clear the statistics on a serial port:

The tables below list messages generated by Megaplex-4 when a configuration
error on modules with serial ports is detected.
Table 6-29. HS-12N/HS-6N Configuration Error Messages
150 Error FIFO SIZE TOO SMALL The manually-selected FIFO size must be equal or larger
than the minimum FIFO size required for the selected rate
and link type (E1 or T1)
151 Error ILLEGAL CHANNELS RATE All channels are configured for operation in multiples of
COMBINATION 64 kbps or 56 kbps. This error may be caused by:
• Selection of 64K in an odd-numbered channel (e.g.,
channel 1) and 56K in an adjacent channel (e.g.,
channel 2) is not allowed.
• The total rate of 2 adjacent channels must not
require more than 31 timeslots
152 Error CTS SHOULD BE SAME FOR ALL All the channels of the specified module must be
CHANNELS configured with the same CTS mode
Table 6-30. HS-U-6/12 Configuration Error Messages
130 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
HS-U-6 and HS-U-12 modules)
Testing Serial Ports

The following test and diagnostics functions available on each serial port:
• Local digital loopback
• Remote digital loopback
Some additional tests and loopbacks are available for HS-U-6/12 modules working
in “1” Mode in conjunction with remote ASMi-31 modems. For their description,
see HS-U-6 and HS-U-12 Modules section in Megaplex-4 I/O Modules Installation


Megaplex unit.
While the loopback is connected, the local serial port should receive its own
signal.
Channel 1 ..
.. .. ..
... . ..
. .. .
User or ..
Test .
Equipment
User or
HS-703 HS-703 Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management

received by user.
While the loopback is connected, the remote serial port should receive its own
signal.

Channel 1 ..
.. ..
.. . ..
.. .. ..
User or . .. .
Test .
Equipment
User or
HS-703 HS-703 C Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management
Loopback Duration
 To perform a loopback on the serial port:

1. Navigate to configure port serial <slot>/<port> to select the serial port to
configure.
The config>port>serial>(<slot>/<port>)# prompt is displayed.

Activating and configuring the loopback {local | remote} • local. Returns the transmitted data
direction of the loopback at the physical layer to the receiving
path. The local physical loopback
includes a configurable timeout
mechanism that ends the loopback
operation after a user-defined
duration.
• remote. Returns the received data
at the physical layer to the
transmitting path.
Using no loopback stops the loopback.
SDH/SONET Ports
Applicable Modules
Megaplex-4 features four SDH/SONET ports (two ports located on each of the
two CL.2 modules). The ports can be ordered either with STM-1/OC-3 or
STM-4/OC-12 interfaces. The panels and terminal identification for the STM-1/OC-
3 and STM-4/OC-12 versions are identical.
Standards
The SDH/SONET ports comply with the following standards:
• SDH: ITU-T G.957, G.783, G.798
• SONET: GR-253-core.
In particular, framing complies with the following:
• SDH: ITU-T G.707, G.708, G.709
• SONET: GR-253-core.
SDH Implementation Principles

This section describes the implementation principles for the Synchronous Digital
Hierarchy (SDH), as a background for the detailed presentation of the SDH signal
structures. In the following explanations, the following terms are used to describe
SDH networks:
• Network node. The SDH network node is a facility at which signals built in
accordance with the SDH frame structure are generated and/or terminated.
Therefore, a network node provides a convenient access point to add or drop
payload signals, e.g., PDH tributary signals, for transmission over the SDH
network.
• SDH transport system. An SDH transport system provides the technical means
to transfer SDH signals between two network nodes.

• SDH network. An SDH network is formed by interconnecting the required

number of network nodes by means of SDH transport systems.
The Synchronous Digital Hierarchy (SDH) is implemented on the basis of two
principles:
1. Direct synchronous multiplexing of individual tributary signals within the
structure of the higher-rate multiplexed signal.
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 the user to build
cost-effective add/drop multiplexers, the key component of flexible networks,
instead of implementing digital cross-connect systems as entities separated
from multiplexing equipment.
In addition, the SDH signal structure includes sufficient overhead for management
and maintenance purposes, and therefore provides the network operator full
control over all the operational aspects of SDH networks and equipment units.
This overhead permits the integration of the network management and
maintenance functions within the transport network itself.
General Structure of SDH Signals

The SDH signal is a serial signal stream with a frame structure. Figure 6-13 shows
the general structure of SDH signals.
The SDH frame structure is formed by byte-interleaving the various signals carried
within its structure. Each SDH frame starts with framing bytes, which enable
equipment receiving the SDH data stream to identify the beginning of each
frame. The location of the other bytes within this frame structure is determined
by its position relative to the framing byte.
The organization of the frame can be easily understood by representing the
frame structure as a rectangle comprising boxes arranged in N rows and M
columns, where each box carries one byte. In accordance with this
representation, the framing byte appears in the top left-hand box (the byte
located in row 1, column 1), which by convention is referred to as byte 1 of the
SDH frame.

N x M Bytes
Order of
Transmission
F 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 6-13. General Structure of SDH Signals

The frame bytes are transmitted bit by bit, sequentially, starting with those in the
first row (see arrow in Figure 6-13). After the transmission of a row is completed,
the bits in the next lower row are transmitted. The order of transmission within
each row is from left to right. After transmission of the last byte in the frame
(the byte located in row N, column M), the whole sequence repeats - starting
with the framing byte of the following frame.
SDH Frame Organization

As shown in Figure 6-14, 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 6-14. SDH Frame Organization

Section Overhead
In SDH networks, the term section refers to the link between two consecutive
SDH equipment units of the same type.
Some signal carrying capacity is allocated in each SDH frame for the section
overhead. This provides the facilities (alarm monitoring, bit error monitoring, data
communications channels, etc.) required to support and maintain the
transportation of a VC between nodes in an SDH network.
The section overhead pertains only to an individual SDH transport system. This
means that the section overhead is generated by the transmit side of a network
node, and is terminated at the receive side of the next network node.
Therefore, when several SDH transport systems are connected in tandem, the
section overhead is not transferred together with the payload (VC) between the
interconnected transport systems.
Virtual Container (VC)

The VC is an envelope (i.e., a special type of signal structure, or frame) that is
used to transport a tributary signal across the SDH network.
The path followed by a VC within the network may include any number of nodes,
therefore the VC may be transferred from one SDH transport system to another,
many times on its path through the network. Nevertheless, in most cases the VC
is assembled at the point of entry to the SDH network and disassembled only at
the point of exit.
Since the VC is handled as an envelope that is opened only at the path end
points, some of its signal carrying capacity is dedicated to path overhead. The
path overhead provides the facilities (e.g., alarm and performance monitoring),
required to support and maintain the transportation of the VC between the end
points.
VC Assembly/Disassembly Process
The concept of a tributary signal being inserted into a virtual container, to be
transported end-to-end across a SDH network, is fundamental to the operation
of SDH networks. This process of inserting the tributary signal into the proper
locations of a VC is referred to as “mapping”.
In all the SDH signal structures, the carrying capacity provided for each individual
tributary signal is always slightly greater than that required by the tributary rate.
Thus, the mapping process must compensate for this difference. This is achieved
by adding stuffing bytes, e.g., path overhead bytes, to the signal stream as part
of the mapping process. This increases the bit rate of the composite signal to the
rate provided for tributary transport in the SDH structure.
At the point of exit from the SDH network, the tributary signal must be recovered
from the virtual container, by removing the path overhead and stuffing bits. This
process is referred to as “demapping”. After demapping, it is necessary to
restore the original data rate of the recovered tributary data stream.

STM-1 Frame Structure

Figure 6-15 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 6-15. 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.
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 6-15, 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.
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 6-16.
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 6-16. Structure of Transmission Path in SDH Network

As shown in Figure 6-16, 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.
• Path overhead, carried in the first column of a VC-4. The path overhead
carried in the VC-4 is called high-order path overhead; see the SDH Tributary
Units section for a description of the low-order path overhead.
Figure 6-17 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 6-17. Organization of STM-1 Overhead Data
Regenerator Section Overhead (RSOH)

A regenerator section of an SDH network comprises the transmission medium
and associated equipment between a network element and the adjacent
regenerator, or between two adjacent regenerators. The associated equipment
includes the aggregate interfaces and SDH processing equipment which either
originates or terminates the regenerator section overhead.
The functions of the various bytes carried in the STM-1 regenerator section
overhead are described below.
Framing (A1, A2 Bytes)
The six framing bytes carry the framing pattern, and are used to indicate the start
of an STM-1 frame.
Channel Identifier (C1 Byte)
The C1 byte is used to identify STM-1 frames within a higher-level SDH frame
(STM-N, where the standardized values of N are 4, 16, etc.). The byte carries the
binary representation of the STM-1 frame number in the STM-N frame.
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 the SDH Maintenance Signals and Response to Abnormal Conditions section
below.
VC-4 Path Overhead Functions

The path overhead (POH) is contained within the virtual container portion of the
STM-1 frame. The POH data of the VC-4 occupies all the 9 bytes of the first
column. The functions of the various bytes carried in the VC-4 path overhead are
described below.
Path Trace Message (J1 Byte)
The J1 byte is used to repetitively transmit a 64-byte string (message). The

message is transmitted one byte per VC-4 frame.
A unique message is assigned to each path in an SDH network. Therefore, the
path trace message can be used to check continuity between any location on a
transmission path and the path source.
Parity Check (B3 Byte)
An 8-bit wide bit-interleaved parity even checksum, used for error performance
monitoring on the path, is calculated over all the bits of the previous VC-4. The
computed value is placed in the B3 byte.
Signal Label (C2 Byte)
The signal label byte, C2, indicates the structure of the VC-4 container. The signal
label can assume 256 values, however two of these values are of particular
importance:
• The all “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 the SDH Tributary Units section). If, for example, the TU
overhead is distributed over four TU frames, these four frames form a TU
multiframe structure. The H4 byte then indicates which frame of the TU
multiframe is present in the current VC-4.
User Communication Channel (F2 Byte)
The F2 byte supports a user channel that enables proprietary network operator
communications between path terminating equipment.
Alarm Signals
Alarm and performance information is included as part of the path overhead.

These functions are explained in SDH Maintenance Signals and Response to
Abnormal Conditions section below.
SDH Tributary Units

The VC-4 channel capacity, 149.76 Mbps, has been defined specifically for the
transport of a fourth level (139.264 Mbps) PDH multiplex signal.
To enable the transport and switching of lower-rate tributary signals within the
VC-4, several special structures, called Tributary Units (TUs), have been defined.
The characteristics of each TU type have been specifically selected to carry one of
the standardized PDH signal rates. In addition, a fixed number of whole TUs may
be mapped within the container area of a VC-4.
Tributary Unit Frame Structure

The structure of the tributary unit frame is rather similar to the SDH frame
structure. With reference to Figure 6-14, 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.
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 6-18 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 6-19.
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 6-18. VC-4 Carrying TU-12 Payload

As shown in Figure 6-18, 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 6-19 shows a general view of the SDH multiplexing hierarchy. The
hierarchy illustrates both the European and North American PDH multiplex levels.
Figure 6-19 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.
• 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)
Legend 2
×4 1.544 Mbps
TU-11 VC-11 C-11
Pointer Processing (DS1)
×3
TU-12 C-12
2.048 Mbps
Mapping VC-12
(E1)
Figure 6-19. 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 6-19
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.
SDH Maintenance Signals and Response to Abnormal Conditions

The maintenance signals transmitted within the SDH signal structure are
explained in Table 6-31.
Table 6-31. 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

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.
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 6-20 provides a graphical representation of the flow of alarm and
indication signals through an SDH transmission path.

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 6-20. 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

• 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 at each level in the maintenance hierarchy is based on
the use of the byte interleaved parity (BIP) checksums calculated on a frame by
frame basis. These BIP checksums are sent downstream in the overhead
associated with the regenerator section, multiplexer section and path
maintenance spans.
In response to the detection of errors using the BIP checksums, the equipment
terminating the corresponding path sends upstream Far End Block Error (FEBE)
signals.
SONET Environment
SONET (Synchronous Optical Network) is an alternative standard to SDH, widely
used in North America and other parts of the world. SONET uses similar
implementation principles, and even the frame structures are quite similar to
those used by SDH. Therefore, the following description is based on the
information already presented for SDH.
Figure 6-21 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 6-21. SONET Multiplexing Hierarchy

The designations of the main signal structures in the SONET hierarchy are as
follows:
• Containers are replaced by Synchronous Payload Envelopes (SPE) for the
various virtual tributaries (VTs)
• Virtual containers (VCs) are replaced by virtual tributaries (VTs), however the
rates are similar to those used in the SDH hierarchy

• Tributary unit groups (TUGs) are replaced by virtual tributary groups

• The VC-3 level is replaced by the Synchronous Transport Signal level 1
(STS-1), and has the same rate (51.840 Mbps).
• 3 STS-1 can be combined to obtain one Synchronous Transport Signal level 3
(STS-3) at the same rate as STM-1 (155.520 Mbps). The corresponding
optical line signal is designated OC-3.
SDH/SONET Interfaces
Each CL.2 module has two STM-1/OC-3/STM-4/OC-12 ports. The ports can be
ordered with the following interfaces:
• STM-1/OC-3:155.52 Mbps ±20 ppm
• STM-4/OC-12: 622.08 Mbps ±20 ppm
The panels and terminal identification for the STM-1/OC-3 and STM-4/OC-12
versions are identical. The bit rate for the STM-4/OC-12 version is set by means
of the speed parameter.
The framer operating mode, SDH or SONET, is selected by software configuration.
The two modules must always use the same mode, and therefore selecting the
mode for one module automatically switches the other to the same mode.
Each port has an SFP socket that provides the physical interface. RAD offers a
wide range of SFPs covering requirements from short-range low-cost optical
interfaces to long-range, high-performance interfaces. Optical SFPs are
terminated in LC connectors. RAD also offers SFPs with electrical interfaces for
intra-office applications.
The port interfaces support the enhanced digital diagnostic monitoring interface
per SFF-8472, which enables collecting status and performance data from the
SFPs, as well as alerting if abnormal conditions might cause damage or
performance degradation.
SFPs are hot-swappable, and can be replaced in the field. This enables upgrading
the network port interface characteristics as network topology changes.
Automatic Laser Shutdown

For safety, Megaplex-4 uses automatic laser shutdown (ALS), which protects
against accidental exposure to laser radiation in case of fiber breaks or
disconnections. This is achieved by automatically switching off the transmitter of
an SDH/SONET interface when the receiver of the same interface reports loss of
the optical signal. To enable automatic recovery, the transmitter is periodically
turned back on, for a short time. If the receive signal does not reappear, the
transmitter is turned back off; if the receive signal reappears, the transmitter
remains on (normal operation).
Inband Management Access through SDH/SONET Networks

Figure 6-22 illustrates the inband management access through SDH/SONET
networks. The inband management is done via the Data Communication Channel
(DCC) carried in the SDH/SONET overhead. Each SDH/SONET link can have its DCC
used for management. DCC ports use the host IP address of the Megaplex-4
management subsystem.

Note Inband management can also support more complex topologies, such as rings.
However, this is possible only if the carrier’s SDH/SONET network provides access
to the DCC and enables transparent transfer of user data through the DCC. In this
case, a Telnet host or an SNMP-based network management station connected to
one of the Megaplex-4 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-4 unit. To enable remote management, the
management traffic not addressed to the internal management subsystem of the
Megaplex-4 is also connected by this subsystem to the DCCs carried by the other
SDH/SONET links connected to the Megaplex-4.
At the remote Megaplex-4 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-4 unit.
Figure 6-22. Inband Management Access through SDH/SONET Networks

As mentioned above, the inband management traffic is carried in the DCC bytes,
as part of the SDH/SONET overhead. The user can select the DCC bytes to carry
the traffic, which are named differently for SDH and SONET environments.
SDH:
• Regenerator DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
• Multiplex DCC bytes (D4 to D12), which provide a 576 kbps channel
terminated at SDH multiplex section terminating equipment.

SONET:
• Section DCC bytes (D1, D2, D3), which provide a 192 kbps channel
terminated at SDH regenerator section terminating equipment
• Line DCC bytes (D4 to D12), which provide a 576 kbps channel terminated at
SDH multiplex section terminating equipment.
You can also select the encapsulation and routing protocols used for inband
management parameters:
• Two encapsulation options are available: HDLC, or PPP over HDLC in
accordance with RFC1661 and RFC1662.
For compatibility with particular implementations of the HDLC encapsulation
protocol for management purposes, you can select the Type 1 flavor (for this
flavor, the LCP (Link Control Protocol) packets do not include address and
control fields in their overhead).
• Two options are also available for the management traffic routing protocol:
 RAD proprietary protocol. This protocol is sufficient for managing any
RAD equipment and should always be used with HDLC encapsulation.
 RIP2: the Megaplex-4 transmits RIP2 routing tables. This permits
standard RIP routers to reach the Megaplex-4 SNMP agent through the
inband (DCC) channel. The RIP2 network is limited to 14 nodes.
SDH/SONET Hierarchy and Allowed Activities

The Megaplex-4 CLI architecture follows the SDH/SONET hierarchy. The kinds of
activities available on each SDH/SONET hierarchical level are listed below:
Activities SDH/SONET AUG/OC-3 TUG-3/STS-1 VC-12/VT-1.5
Configuring Port Parameters v - - -
Assigning VC Profile - v - -
Activating Loopbacks v v v v
Displaying Status v v v v
Displaying Statistics v v v v
The following sections explain how these activities are performed.
Factory Defaults (SDH/SONET Parameters)

Megaplex-4 is supplied with all SDH/SONET ports enabled. Other parameter
frame-type sdh
speed 155mbps
dcc disabled
dcc mode d1-to-d3

dcc routing-protocol none
dcc deviation standard
threshold eed 1e-3
threshold sd 1e-6
j0-pathtrace direction tx
j0-pathtrace padding nulls
j0-pathtrace string www.rad.com
rdi-on-failure enabled
tim-response enabled
automatic-laser-shutdown disabled
loopback disabled
Tx-ssm enabled
Configuring an SDH/SONET Link
 To configure external SDH/SONET parameters:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
port
Setting the type of operation in frame-type {sdh | sonet}

accordance with the SDH or
SONET standards
Selecting the SDH/SONET port 155mbps: STM-1 (SDH)/OC-3 (SONET)

speed {155mbps | 622mbps}
speed and operating mode 622mbps: STM-4 (SDH)/OC-12 (SONET)
Enabling DCC inband dcc [encapsulation {hdlc | See Functional Description above for
management and configuring ppp-o-hdlc | type1}] [mode parameter explanation. Using no dcc
DCC parameters: encapsulation {d1-to-d3 | d4-to-d12}] disables inband management
protocol and the DCC bytes used [routing-protocol See also Configuring Inband Management
to carry inband management { none | prop-rip | rip2}] in Chapter 8 for important considerations
traffic [deviation {standard | type1} on selecting the routing protocol.

Selecting EED (error rate threshold [eed {1e-3 | 1e-4 | If the selected BER value is exceeded,
degradation) and SD (signal 1e-5}] [sd {1e-6 | 1e-7 | 1e- Megaplex-4 generates the relevant (EED
degrade) thresholds 8 | 1e-9}] or SD) alarm
Enabling the checking of the j0-pathtrace [direction { tx | Using no j0-pathtrace disables the
receive/transmit path trace label rx-tx }] [string <path-trace- checking
by the port and configuring the string> ] [padding {spaces |
optional path trace direction and nulls }]
padding (when the path label is
shorter than the required length
of 15 characters)
Enabling RDI (remote defect rdi-on-failure The SDH fault conditions are:
indication) sending in case of • LOS (loss of SDH signal)
failure
• LOF (loss of SDH frame)
• AIS (alarm indication signal)
Using no rdi-on-failure disables RDI
sending
Enabling the sending of RDI tim-response Using no tim-response disables sending

indications by the port, in case of RDI indications
the received path trace label
(carried in SDH overhead byte
J0) is different from the
expected path trace label
Enabling automatic laser automatic-laser-shutdown Using no automatic-laser-shutdown

shutdown of optical laser link on disables automatic shutdown
sync loss
Defines the administrative unit aug <aug number> This option is valid only when
group (AUG) frame-type=sdh.
Possible values:
• for speed=155mbps: 1
• for speed=622mbps: 1 to 4
See also Assigning VC Profiles to
AUG/OC-3 below
Enabling SSM transmission tx-ssm
Defines an OC-3 connection oc3 <oc3 number> This option is valid only when
frame-type=sonet.
Possible values:
• for speed=155mbps: 1
• for speed=622mbps: 1 to 4
See also Assigning VC Profiles to
AUG/OC-3 below

Example
This example illustrates how to configure an SDH Port with management via DCC
(Dedicated Communication Channel).
1. Program SDH Port 1 in Slot CL-A and configure DCC management with the
following parameters:
 Speed: 155 Mbps
 DCC encapsulation protocol: HDLC
 DCC bytes used to carry inband management traffic: D1 – D3
mp4100>config>slot# cl-a card-type cl cl2-622gbe
mp4100>config>port# sdh-sonet cl-a/1 no shutdown
mp4100>config>port# sdh-sonet cl-a/1 frame-type sdh
mp4100>config>port# sdh-sonet cl-a/1 speed 155mbps
mp4100>config>port# sdh-sonet cl-a/1 dcc encapsulation hdlc mode
d1-to-d3
2. Configure router interface 3, address 10.10.10.9, subnet mask 24
mp4100>config>router 1 interface 3 address 10.10.10.9/24
3. Bind SDH port 1 on CL-A to router interface 2
mp4100>config>router# 1 interface 3 bind sdh-sonet cl-a/1
The inband management connectivity via DCC is established.
Assigning VC Profiles to AUG/OC-3
 To assign a VC profile to AUG:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH port
to configure.
The config>port>sdh-sonet>(<slot>/<port># prompt is displayed.
2. Set frame-type to sdh.
3. Enter the aug command followed by the desired aug number (1 for 155
Mbps, 1 to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> aug(number)# prompt is
displayed.
Assigning user-defined VC profile vc profile <profile name> For creating VC profiles, see VC Profiles.
to the port Using no vc removes the profile
Before you assign the user-defined
profile, you must use the no vc command
to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement

 To assign a VC Profile to OC-3:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SONET port
to configure.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.
2. Set frame-type to sonet.
3. Enter the oc3 command followed by the desired OC-3 number (1 for
155 Mbps, 1 to 4 for 622 Mbps).
The config>port>sdh-sonet(<slot>/<port>)> oc3(number)# prompt is
displayed.
to remove the automatical tug-structure/
hvc-laps/hvc-gfp profile assignement
detected.
Table 6-32. SDH/SONET Configuration Error Messages
300 Error TOO MUCH VCS/VTS The maximum number of virtual containers that can be
used by one virtually concatenated group cannot exceed
63 for VC-12, or 64 for VT1.5
301 Error MINIMUM NUMBER OF VCs/VTs The minimum number of virtual containers (VC-12 or
IS 2 VT-1.5) in a group is 2
302 Error VC GROUP IS NOT CONNECTED The virtually concatenated group is not bound to any
other entity. Check and correct
303 Error DIFFERENT CLS FRAME The two CL modules installed in the Megaplex-4 must use
STRUCTURE the same link standards (either SDH or SONET)
305 Error MISSING E1-I/T1-I SDH-SONET An E1-i/T1-i port is opened on CL.2 but not cross-
CROSS CONNECT connected to VC/VT on SDH/SONET.
307 Error ILLEGAL VCG MAPPING The virtually concatenated group mapping is not correct
309 Error E1-I/T1-I PORT IS AT e1-i/t1-i port cannot be cross-connected when it is in

SHUTDOWN shutdown state. Set the port to no shutdown
310 Warning NO LICENSE FOR STM-4/OC-12 The port is configured to 622mbps but the CL does not
have an appropriate license.

311 Error ILLEGAL BINDING Pay attention to the following:

• A VCG and a VC-VT container bound to it must belong
to the same CL module (A or B).
• A Logical MAC and a GFP/HDLC port bound to it must
belong to the same CL module (A or B).
• A GFP/HDLC port and a VCG bound to it must belong to
the same CL module (A or B).
• A GFP/HDLC port defined as “no shutdown” must be
bound to a Logical MAC
• A VCG port defined as “no shutdown” must be bound
to a GFP/HDLC port.
312 Error ILLEGAL SDH/SONET CROSS An E1-i/T1-i port and a VC-VT container cross-connected
CONNECT with it must belong to the same CL module (A or B).
313 Error NUMBER OF LIMITED VC-VT X- Pay attention to the following:

CONNECTS EXCEEDED • Number of vc-vt containers per CL module is limited
to 252.
• Number of vc-vt containers for EoS per CL module is
limited to 128.
314 Error ASSIGNMENT/NUMBER OF VC One of the following:

MISMATCH • Mismatch between the link speed
(155mbps/622mbps) and the number of virtual
containers defined. The numbers should not exceed
the following ranges:
SDH:
<port 1..2>
aug <aug number 1..4> (1 for STM-1)
tug3 <tug3 number 1..3>
vc12 <tug2 number 1..7>
<tributary number 1..3>
SONET:
<port 1..2>
oc3 (<oc3 number 1..4> (1 for OC-3)
sts1 (<sts1 number 1..3>
vt1-5 (<tug2 number 1..7>
<tributary number 1..4>).
• A VC cannot be bound/cross-connected
simultaneously to multiple sources (VCG port,
E1-i/T1-i port, etc).
315 Error VCAT NUMBER OF VCs LIMITED The maximum number of virtual containers (VC-12 or VT-
TO 64 1.5) that can be bound to one VCG cannot exceed 64
316 Error GFP/HDLC PORT CAN BE A GFP or HDLC port of the CL module can be bound only
BOUND TO SINGLE VC-VT to a single vc-vt container.
ONLY

317 Error VC-PROFILE DOES NOT MATCH The VC profile content does not match the port type.
PORT TYPE
318 Error WRONG LCAS PARAMETER One of the LCAS parameters does not match one of the
VCG parameters.
776 Error INSUFFICIENT BUS BANDWIDTH When SDH/SONET services are activated, the maximum
number of activated TUG-2 ports is 60 for all the I/O
modules. Due to this restriction on PDH bus occupancy,
the maximum number of ports supported on all I/O
modules in the chassis is as follows:
When CL is assembled with SDH/SONET ports, the
communication between CL and I/O modules is over
proprietary PDH links, terminated by SDH/SONET framer
with maximum 60 activated TUG-2 ports. Due to this
restriction on PDH bus occupancy, the maximum number
of ports supported on all I/O modules in the chassis is as
follows:
• 180 E1 ports
• 240 T1 ports
• 180 or 240 DS1 ports depending on the respective
service (E1 or T1).
Viewing SDH/SONET Status Information

For viewing the status of the SDH/SONET hierarchical entities, follow the
instructions below.
 To view the status of an SDH/SONET port:

1. Navigate to config>port>sdh-sonet> (<slot>/<port>)#

mp4100>config>port>sdh-sonet(cl-a/1)# show status

General
---------------------------------------------------------------
Name : CL-A sdh-sonet 01
Operational Status : Up
Connector Type : SFP In
Expected Trace Message (J0) : www.rad.com
Received Trace Message (J0) :
Rx Quality : SEC
Tx Quality : SEC
SFP
---------------------------------------------------------------
Connector Type : LC
Manufacturer Name : CORETEK
Manufacturer Part Number : CT-0155TSP-MB5L
Wave Length (nm) : 1310
Fiber Type : SM
RX Power (dBm) : -50.0 dBm
TX Power (dBm) : -12.0 dBm

Laser Bias (mA) : 14.0 mA
Laser Temperature (Celsius) : 47.0 C
Power Supply (V) : 3.3 V
Note The last 5 rows are displayed only for SFPs with built-in DDM functionality.
The performance monitoring data for the SDH/SONET link physical layer includes
status data for each link port, and SFP data for the installed SFPs. The table
below explains the parameters of the SFP installed for selected port.
Table 6-33. Link SFP Parameters
Connector Type Displays the SFP connector type, for example, LC, SC, SC/APC, FC, etc.
Manufacturer Name Displays the original manufacturer’s name
Vendor PN Displays the original vendor’s part number
Typical Max. Range Displays the maximum range expected to be achieved over typical optical fibers, in
(Meter) meters
Wave Length (nm) Displays the nominal operating wavelength of the SFP, in nm
Fiber Type Displays the type of optical fiber for which the SFP is optimized: SM (single mode) or
MM (multi mode)
TX Power (dBm) Displays the current optical power, in dBm, transmitted by the SFP
RX Power (dBm) Displays the current optical power, in dBm, received by the SFP

Laser Bias (mA) Displays the measured laser bias current, in mA
Laser Temperature Displays the measured laser temperature, in °C

(Celcius)
Power Supply (V) Displays the SFP power supply voltage
 To view the status of an AUG-3/OC-3:

1. Navigate to:
SDH:
config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4> )#
SONET:
oc3 (<oc3 number 1..4>#
mp4100>config>port>sdh-sonet(cl-a/1)>aug(1)# show status
General
------------------------------------------------------------
Received Trace Message (J1) : www.rad.com
Expected Signal Label : 0x1B
Received Signal Label : 0x1B
 To view the status of a TUG-3/STS-1:

1. Navigate to:
SDH:
aug (<aug number 1..4> )
tug3 (<tug3 number 1..3>)#
SONET:
oc3 (<oc3 number 1..4>
sts1 (<sts1 number 1..3>) #

mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)# show status

General
---------------------------------------------------------------
Expected Signal Label : 0x02
Received Signal Label : 0x02
 To view the status of a VC-12/VT-1.5:

1. Navigate to:
SDH:
aug (<aug number 1..4> )
tug3 (<tug3 number 1..3>)
vc12 (<tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
oc3 <oc3 number 1..4>)
sts1 <sts1 number 1..3>)
vt1-5 <tug2 number 1..7>)/ <tributary number 1..4>)#.
mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)#
show status
General
---------------------------------------------------------------
Expected Signal Label : 0x05
Received Signal Label : 0x05
Testing SDH/SONET Ports

Megaplex-4 features remote loopbacks on the SDH/SONET ports of the CL.2
modules, local loopbacks on AUG/OC-3 and TUG-3/STS-1 and remote loopbacks
on AUG/OC-3, TUG-3/STS-1 and VC-12/VT-1.5. The following sections briefly
describe each type of loopback. Table 6-34 shows the paths of the signals when
each loopback is activated.

Table 6-34. SDH/SONET Loopbacks
Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
Diagnostic 2
Function DS1 . SDH/
SONET
Mapper Matrix
Matrix .. Framer
..
.
Framer
Remote
loopback on
SDH/SONET link
Local loopbacks VC/VT

Matrix
on AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
Remote VC/VT
Matrix
loopbacks on
AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5
Remote Loopback on SDH/SONET Link

As shown in Table 6-34, 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-4 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-4 SDH/SONET interface and
then returned to the input of the transmit path through the framer. Therefore,
when the remote loopback is activated on the external port, the receive signal is
returned to the remote unit. To correct transmission distortions, the returned
signal is regenerated by the SDH/SONET interface circuits.
The remote loopback should be activated at only one of the two units
interconnected by the SDH/SONET link, otherwise an unstable situation occurs.
Local Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5

As shown in Table 6-34, the local loopback is activated within the SDH/SONET VC
cross-connect matrix. When the local loopback is activated, the transmit signal is
returned to the receive path before the output to the SDH/SONET framer, at
different points for each entity.

While the loopback is activated, the equipment mapped to the corresponding

E1-i/T1-i port of the local Megaplex-4 must receive its own signal, and thus it
must be frame-synchronized.
Note The local loopback on VC-12/VT-1.5 is supported for unframed E1/T1 or VC-
12/VT-1.5 ports mapped to VCG ports. It is not supported for VC-12/VT-1.5 ports
mapped to E1-i/T1-I ports of CL modules.
Remote Loopback on AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5

As shown in Table 6-34, the remote loopback on AUG/OC-3, TUG-3/STS-1, or
VC-12/VT-1.5 is activated within the network side circuits of the VC/VT
cross-connect matrix. Therefore, the loopback signal path includes all the circuits
of the local Megaplex-4 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-4 SDH/SONET interface and
then returned to the input of the transmit path through the framer. Therefore,
when the remote loopback is activated on the external port, the receive signal is
returned to the remote unit.
The remote loopback should be activated only after checking that the equipment
connected at the remote side to the tested unit operates normally during a local
loopback. In this case, the remote unit must receive its own signal, and thus it
must be frame-synchronized. The effect on the ports of the remote unit is mixed,
as explained above for the local loopback.
Loopback Duration
to limit its duration to a selectable interval in the range of 1 through 60 minutes.
Activating Loopbacks
 To perform a loopback on the SDH/SONET port:

1. Navigate to configure port sdh-sonet <slot>/<port> to select the SDH/SONET
port to be tested.
The config>port>sdh-sonet>(<slot>/<port>)# prompt is displayed.

Activating the remote loopback {remote} [duration Using no loopback remote disables the
loopback and setting its <duration in minutes 1..60> ] loopback
duration (in minutes) Default (without duration parameter) is
infinite loopback
 To perform a loopback on the AUG/OC-3 port:

• From the config>port>sdh-sonet> (<slot>/<port 1..2>)
aug (<aug number 1..4>) or config>port>sdh-sonet> (<slot>/<port 1..2>)
oc3 (<oc3 number 1..4>) # context, activate the loopback as follows:
Activating the local or loopback { remote | local} Using no loopback followed by the
remote loopback on this corresponding command disables the
aug/oc3 port loopback
 To perform a loopback on the TUG-3/STS-1 port:

1. Navigate to:
SDH:
aug (<aug number 1..4>)
SONET:
oc3 (<oc3 number 1..4>)
2. Activate the loopback as follows:
Activating the local or loopback {remote | local} Using no loopback followed by the
remote loopback on this corresponding command disables the
tug3/sts1 loopback
 To perform a loopback on the VC-12/VT-1.5:

3. Navigate to:
SDH:
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:

sts1 (<sts1 number 1..3>)

vt1-5 (<tug2 number 1..7>)/ <tributary number 1..4>)#.
4. Activate the loopback as follows:
Activating the remote Using no loopback remote disables the

loopback remote
loopback on this vc12/vc1-5 loopback
Displaying SDH/SONET Statistics

SDH/SONET ports of Megaplex-4 feature the collection of statistical diagnostics at
different hierarchical levels, per ANSI T1.403.
Note Only locally-terminated entities (AUG/OC-3, TUG-3/STS-1, VC-12/VT-1.5) are

monitored by Megaplex-4.
 To display the SDH/SONET port statistics:

• At the prompt config>slot>port>sdh-sonet (<slot><port>)#, enter show
statistics followed by parameters listed below.
 To display the AUG/OC-3 statistics:

1. Navigate to:
SDH:
aug (<aug number 1..4> )#
SONET:
oc3 (<oc3 number 1..4> )#
2. Enter show statistics followed by parameters listed in the table below.
 To display the TUG-3/STS-1 statistics:

1. Navigate to:
SDH:
aug (<aug number 1..4>)
SONET:

 To display the VC-12/VT-1.5 statistics:

1. Navigate to:
SDH:
aug <aug number 1..4>
tug3 <tug3 number 1..3>)
vc12 <tug2 number 1..7>)/<tributary number 1..3>)#
SONET:
sts1 (<sts1 number 1..3>)
vt1-5 (<tug2 number 1..7>)/ (<tributary number 1..4>)#.
Displaying statistics show statistics {all | current} • current –Displays the current
statistics
• all –Displays all statistics: first
current interval statistics, then
statistics for all valid intervals

for a specific interval
SDH/SONET statistics are displayed. The counters are described in

Table 6-35 and Table 6-36. For example:

Current statistics:
mp4100>config>port>sdh-sonet(cl-a/1)# show statistics current
Current
---------------------------------------------------------------
Valid Intervals : 2
ES : 0
SES : 0
SEFS : 0
CV : 0
mp4100>config>port>sdh-sonet(cl-a/1)# show statistics interval 67
Interval
---------------------------------------------------------------
Section ES : 0
Section SES : 0
Section SEFS : 31
Section CV : 0
All statistics:
mp4100>config>port>sdh-sonet(cl-a/1)>oc3(1)>sts1(2)>vt1.5(1/1)#
show statistics all
Current
---------------------------------------------------------------
Valid Intervals : 1
ES : 0
SES : 0
UAS : 0
CV : 0
Interval
--------------------------------------------------------------
Interval Number : 1
ES : 3
SES : 2
UAS : 57
CV : 0

Table 6-35. SDH/SONET Port Statistics Parameters – Current 15-Minute 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 no transitions are detected in the incoming line
signal (before descrambling) in an interval of 2.3 to 100 microseconds.
 The LOS defect is terminated after a 125-microsecond interval (one frame) in
which no LOS defect is detected.
• Loss of Pointer (LOP) defect:
 A LOP defect is declared after no valid pointer is detected in eight consecutive
frames. The LOP defect will not be reported while an AIS signal is present.
 The LOP defect is terminated after a valid pointer is detected.
• Alarm Indication Signal (AIS) received in the SDH overhead.
• Coding Violation (CV): a coding violation is declared when a Bit Interleaved Parity
(BIP) error is detected in the incoming signal. The BIP information is collected using
the B1 byte in the Section Overhead.
SEFS (UAS) 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.
A SES is any second in which multiple error events of the types taken into
consideration for an ES have occurred.
CV Displays the number of coding violations (CV) in the current interval.
The range is 1 to 900 seconds
displayed, in addition to the current (not finished) interval (up to 96)
Table 6-36. SDH/SONET Port Statistics Parameters – Selected 15-Minute Interval
Section ES Displays the total number of errored seconds (ES) in the selected interval
Section SES Displays the total number of severely errored seconds (SES) in the selected interval
Section SEFS Displays the total number of unavailable seconds (SEFS/UAS) in the selected interval
Section CV Displays the total number of code violations (CV) in the selected interval

Interval number Number of interval for which statistics is displayed
Clearing Statistics
There are two options for clearing SDH/SONET statistics data:
• Clearing current interval statistics
• Clearing all statistics, except for the current interval.
 To clear the current interval statistics:

1. Navigate to the corresponding entity as described above.
2. Enter clear-statistics current-interval.
The statistics for the specified entity are cleared.
 To clear all statistics data except for from the current interval:
2. Enter clear-statistics current-all.
SHDSL Ports
Applicable Modules
The SHDSL ports are available on the M8SL, ASMi-54C family and SH-16 I/O
modules.
The ASMi-54C includes three main modules:
• ASMi-54C/ETH –Ethernet over SHDSL.bis 8-port module with EFM support
• ASMi-54C/E1/N - E1 over SHDSL 8-Port module
• ASMi-54C/E1/ETH/N –E1 and Ethernet over SHDSL/SHDSL.bis 8-port module.
•
Note ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules have the same features for their
SHDSL ports; in this section they are denoted as ASMi-54C/N, to distinguish from
the older ASMi-54C/ETH version. The generic term ASMi-54C is used when the
information is applicable to all of the ASMi-54C models.
•
The SH-16 module includes two main modules:

• SH-16 –Ethernet over SHDSL/SHDSL.bis 16-port module
• SH-16/E1 - E1/Ethernet over SHDSL/SHDSL.bis 16-port module
•
Note In this chapter, the generic term SH-16 is used when the information is applicable
to both SH-16 and SH-16/E1 models. The designation SH-16/E1 is used when
information is applicable only to this model.
•

The following table shows the number of SHDSL/SHDSL.bis ports and the features
supported by each Megaplex-4 module. The digits in brackets (1 to 5) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Note ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules have the same features for their
SHDSL ports; in this section they are denoted as ASMi-54C/N, to distinguish from
the older ASMi-54C/ETH version. The generic term ASMi-54C is used when the
information is applicable to all of the ASMi-54C models.
Table 6-37. Features Supported by Megaplex-4 SHDSL/SHDSL.bis Ports
Feature/ ASMi-54C/ETH ASMi-54C/E1/N, SH-16 M8SL

Command ASMi-54C/E1/ETH/N
STU-C STU-R STU-C STU-R
Number of 16 16
ports 8 8 8 8
name √ √ √ √ √ √
shutdown √ √ √ √ √ √
far-end- non-managed (4) non-managed non-managed or non- asmi52 (ASMi-52 or

type or asmi54 asmi52 (ASMi-52 or or asmi54 asmi54 (ASMi-52 managed ASMi-52L
(ASMi-54 or ASMi-52L standalone) (ASMi-54, (E1 or V.35), (SH-16) standalone)
ASMi-54L ASMi-53 or ASMi-54, ASMi-53 asmi52-e1-dte
asmi52-e1-eth (ASMi-
standalone) ASMi-54L or ASMi-54L (ASMi-52 standalone
52 standalone with E1
managed or standalone) standalone) with E1 and serial
and LAN ports (Mux
asmi54-eoc type)) (R/O) managed or ports (Mux type))
(ASMi-54L asmi54-eoc asmi52-e1-eth
non-managed or
standalone (ASMi-54L (ASMi-52 standalone
asmi54 (ASMi-54 or
configurable standalone with E1 and LAN
ASMi-54L standalone)
via EOC or configurable via ports (Mux type))
ASMi-53) managed or asmi54- EOC or ASMi-53
eoc (ASMi-54L asmi52-eth-dte
standalone)
standalone (ASMi-52 standalone
high-speed-mux- with serial and LAN
configurable via EOC or
serial-e1 (ASMi- ports (Mux type))
ASMi-53) ,
53 standalone
ASMi-54C/E1/ETH/N mp-card (M8SL
with E1 and serial
module only) module installed in
ports (Mux type),
asmi52-e1-dte (ASMi- Megaplex-4 unit)
4M/4W
52 standalone with E1 fcd-ip (FCD-IP device)
functionality)
and serial ports (Mux dxc (equipment from
type)) the
high-speed-mux-serial- DXC-8R/10A/30
e1 (ASMi-52 or ASMi- family of multiservice
53 standalone with E1 access nodes
and serial ports (Mux
type), 4M/4W
functionality)

Feature/ ASMi-54C/ETH ASMi-54C/E1/N, SH-16 M8SL

Command ASMi-54C/E1/ETH/N
STU-C STU-R STU-C STU-R
stu √ √ √ √ √ √
line-prob √ √ – √ – –
data-rate- √ √ – √ – √
maximum
tc √ –(1) √ √ √ –(1)
wires √ √ √ √ √ –(2)
power- √ – √ √ √ √
backoff
default
current- √ – √ √ √ –
margin
worst- √ – – √ – –
margin
loop- √ √ – √ – √
attenuation
-threshold
snr-margin- √ √ √ √ √ √
threshold
clock-mode – √ – – – –
remote- – √ – – – –
ch1-ts-num
power- √ √ – √ – –
feeding
ts- – – – – – √
compaction
-mode
ts0-over-dsl – √ √ – √ √
(3)
remote-crc – – – – – √
(3)
1 – HDLC only
2 – 2 wire only
3 – these parameters are configured under e1-i ports
4 – ASMi-54C/E1/N and ASMi-54C/E1/ETH/N modules cannot work with a mix of ASMi-54/53 and ASMi-52 modems at the
far end. At every moment, all the remote modems should be either ASMi-54/ ASMi-54L/ASMi-53 or ASMi-52/ ASMi-52L.

Standards
SHDSL and SHDSL.bis ports comply with ITU-T Rec. G.991.2 and ETSI TS 101 524.
Benefits
The SHDSL/SHDSL.bis technology is an efficient method for transmitting
full-duplex data at high rates over a single unloaded and unconditioned twisted
copper pair, of the type used in the local telephone distribution plant. Therefore,
SHDSL provides a cost-effective solution for short-range data transmission and
last-mile applications.
SHDSL has been standardized in ITU-T Rec. G.991.2, and has been extended
beyond the original specifications, which called only for support of rates up to
2.312 Mbps per pair. The current SHDSL.bis version, as standardized in ITU-T Rec.
G.991.2, supports variable payload data rates up to 5.696 Mbps (5.7 Mbps line
rate) on a single unloaded and unconditioned twisted copper pair, of the type
used in the local telephone distribution plant. SHDSL.bis includes an extension,
referred to as M-pair, that enables to bond multiple pairs (up to four) to achieve
variable payload rates up to 22.784 Mbps (22.8 Mbps equivalent line rate).
SHDSL Transmission Subsystem Structure

The basic SHDSL transmission subsystem includes two units interconnected by a
single pair of wires, usually a regular unloaded twisted pair. The pair is used for
duplex transmission.
Two different types of SHDSL units are defined by ITU-T Rec. G.991.2:
• SHDSL central unit (STU-C), usually located at the network side, at the central
office (CO), which controls the operation of the whole subsystem, supervises
the link setup process and provides the timing reference.
• SHDSL remote unit (STU-R), which terminates the line at the user side, on the
customer premises (CPE).
This feature is supported by all SHDSL modules.
Note When the ASMi-54C/ETH module is operating in the STU-R mode, the maximum
number of remote units is two. These units are served by PCS 1 and PCS 5.
When the SH-16 module is operating in the STU-R mode, the maximum number
of remote units is four. These units are served by PCS 1, PCS 5, PCS 9 and PCS 13.
SHDSL Modulation Method

SHDSL uses multi-level pulse-amplitude modulation (PAM) together with trellis
coding. Advanced digital signal processing (DSP) techniques enable symmetric
data transmission at rates of 192 to 2304 kbps (3 to 36 x 64 kbps timeslots), or
5.696 Mbps (up to 89 timeslots) for SHDSL.bis, which corresponds to lines rates
of 200 to 2312 kbps, respectively 5.7 Mbps. The modulation method is spectrally

compatible with other transmission technologies deployed in the access network,

including other DSL technologies.
Handling of Timeslot 0
To meet various systems requirements, the user can select the handling method
of timeslot 0 of an E1 stream by each SHDSL port of M8SL and ASMi-54C/N
modules. Two options are available:
• Terminate (loop back) timeslot 0. This option is available in the basic G.704
mode only.
• Transfer timeslot 0 transparently through the SHDSL link, down to the E1
port of the unit connected to the remote ASMi-52/ASMi-52L unit. This option
is available in both G.704 framing modes.
The handling method of TS0 is configured by means of ts0-over-dsl parameter.
See also ASMi-54C Modules, SH-16 Modules and M8SL Modules in Megaplex-4 I/O
Modules Installation and Operation Manual, SHDSL Modules Chapter for additional
configuration considerations.
Management via Embedded Operational Channel (EOC)

SH-16, ASMi-54C/ETH and ASMi-54C/E1/ETH/N modules provide an inband
management channel (EOC) for end-to-end system management and supervision
of ASMi-54L and ASMi-53 standalone modems. SH-16 and ASMi-54C/E1/ETH/N
can also manage ASMi-52 standalone modems with E1 or V.35 interface. This
management channel uses SHDSL overhead bits and operates without interfering
with data transmission.
EOC management can be used to configure unaware flows between the GbE
ports of CL modules and PCS ports of SHDSL modules without configuring the
module itself.
Note Configuring aware flows requires dedicated VLAN management.
Single IP Management
The ASMi-54L modems (starting from version 2.6 and higher) can be fully
managed via SH-16, ASMi-54C/ETH or ASMi-54C/E1/ETH/N modules installed in
the Megaplex-4 chassis, using RADview with the Single IP solution.
The Single IP solution uses one legal IP address (the Megaplex-4 CL module IP
address) to manage up to 96 standalone units via the chassis. The remote
standalone ASMi-54L/ASMi-53 is assigned a private IP address derived from the
CL.2 IP by an internal algorithm. This solution saves IP addresses on the
Megaplex-4 working with a remote standalone ASMi-54L/ASMi-53 modem.
This IP address is assigned to all the system which includes the Megaplex-4 with
all its CL.2 and ASMi-54C/SH-16 modules and the remote standalone ASMi-54L
units.
If dedicated VLAN management is not configured on an ASMi-54C/SH-16 PCS
port, single IP management is automatically established.

When working in Single IP mode, RADview sends packets to the ASMi-54L using
the Megaplex-4 IP address. The Megaplex-4 CL.2 module works as NAPT router
and routes the management packets to the appropriate entity.
Factory Defaults
Megaplex-4 is supplied with all SHDSL ports disabled. Other parameter defaults
wires 2
tc 64-65-octets
stu central
far-end-type none
power-backoff default 0
line-prob line-prob (enabled)
ts-compaction-mode no-mapping
data-rate [kbps] 192
loop-attenuation-threshold 0
clock-mode {plesiochronous1 | plesiochronous1

plesiochronous2 | synchronous3a }
snr-margin-threshold 0
current-margin 0
worst-margin no worst-margin (disabled)
remote-ch1-ts-num 0
power-feeding no power-feeding (disabled)
Configuring an SHDSL Port
 To configure the SHDSL port parameters:

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


port
Specifying number of wires wires {2 | 4 | 8} In ASMi-54C/ETH and SH-16, the available selections
for an M-pair group depend on the tc parameter:
• tc=64-65-octets: 2/4/8 wires are supported, no
TDM payload
• tc=hdlc: 2/4 wires and TDM payload are
supported
ASMi-54C/N supports only 2- or 4-wire operation
M8SL supports only 2-wire operation
When SH-16 is working in HDLC mode, only one type
of service (4x2W, 2x4W or 8W) is allowed per each
group of 4 ports (1-4 ,5-8, 9-12, 13-16).
Specifying TC layer and tc {64-65-octets | hdlc} All the module ports use the same Transmission
functional mode Convergence layer (the last selection is automatically
(ASMi-54C/ETH and SH-16 applied to all the ports)
modules) The selection is done per four lines.
Setting the port operation stu {central | remote} This option is available for M8SL, SH-16 and
mode: CO or CPE ASMi-54C modules when the equipment connected
to the far end of the line is another M8SL, SH-16 or
ASMi-54C module installed in a Megaplex-4.
When a SH-16 modules is operating 2W or 4W as a
CO, it is not recommended to connect the entire
group of 4 ports (1-4, 5-8, 9-12, 13-16) on the CO
module to the entire group of 4 ports on the CPE
module, since short interruption of data may occur
when connecting/disconnecting one of the links.
Specifying the far end far-end-type {none | asmi52 | To specify far-end equipment for specific SHDSL
equipment connected to asmi52-e1-dte | modules, consult Table 6-37. Note that non-
this SHDSL port high-speed-mux-serial-e1 | managed and asmi54 options denote the same
asmi52-e1-eth | asmi52-eth- functionality and are interchangeable. The same
dte | non-managed | asmi54 holds for managed and asmi54-eoc options.
|managed | asmi54-eoc |fcd-ip |For working with far-end-type=high-speed-mux-
dxc | mp-card} serial-e1, see the relevant module (ASMi-54C/N or
SH-16/E1) in Megaplex-4 I/O Modules Installation
and Operation Manual, SHDSL Modules Chapter.
Enabling the transmit power-backoff default <value Possible values are 0 to 31 dbm.
power backoff and setting in dbm> Power backoff is used to reduce the transmit power
its value (for SH-16, below the nominal value specified in the standards:
ASMi-54C/ETH and M8SL this reduces interference caused by your signal to
modules) other equipment using pairs in the same cable,
without degrading the link transmission quality.
Values set for STU-C are copied automatically to
STU-R.
Using no power-backoff disables the power backoff

Controlling the use of line line-prob This parameter is relevant for ASMi-54C/ETH and
probing per ITU-T Rec. SH-16, only when tc = 64-65-octets.
G.991.2 for the Using no line-prob disables line probing
corresponding line (to
When line probing is enabled, either the current-
automatically select the
margin or worst-margin parameter must be enabled
maximum data rate
and set
supported by the line)
Controlling the mapping of ts-compaction-mode {no- This parameter is relevant only for M8SL when far
the connected E1 port mapping | low-ts-mapping} end device is MP card, FCD-IP, or DXC.
timeslots into the SHDSL no-mapping – The connected timeslots of the E1
frames frame are placed in the SHDSL frame in consecutive
timeslots, in ascending order.
when a new E1 timeslot, lower than the timeslots
already connected, is added, the timeslots with
higher numbers must be moved (reassigned): this
results in a brief interruption of data transfer for the
moved timeslots.
low-ts-mapping – The first two timeslots of the
SHDSL frame are reserved for the signaling timeslot
(timeslot 16) and the dedicated management
timeslot. The payload starts from the third timeslot,
and is inserted in consecutive timeslots according to
the E1 frame order.
This ensures that the signaling and dedicated
timeslots will continue to function even when new
timeslots are connected in the E1 frame. Service
interruption might still occur when timeslots are
moved, but in this case only data timeslots are
moved.
When the far end device is an ASMi-52/ASMi-52L,
no-mapping is automatically used.
Setting the SHDSL port data-rate maximum [rate in In ASMi-54C/ETH and SH-16, this parameter is
data rate (line payload kbps] relevant only when line probing is disabled (no line-
rate) prob).
For available selections, see the respective SHDSL
Data Rate tables in Chapter 7 of the Megaplex-4 I/O
Modules Installation and Operation Manual.
Selecting the loop loop-attenuation-threshold The range is 0 to 127 (the number specifies the
attenuation threshold in <value in dbm> maximum value, in dB).
db If the attenuation measured on the SHDSL link
exceeds the threshold value, an alarm is generated.

Selecting clock clock-mode {plesiochronous1 | Not for ASMi-54C/ETH

synchronization mode in plesiochronous2 | When SH-16 (with E1 interface) or ASMi-54C/E1/N is
accordance with the SHDSL synchronous3a} working with ASMi-52 at the far end,
bit rates available in plesiochronous1 mode must be used.
remote devices
ASMi-54C/E1/N modules cannot work with a mix of
ASMi-54/54L/53 and ASMi-52 modems at the far
end.
Selecting the SNR margin snr-margin-threshold <value in The range is 0 to 15 (the number specifies the
threshold in db db> maximum value, in dB).
If the attenuation measured on the SHDSL link
exceeds the specified value, an alarm is generated.
Specifying the target current-margin <value in db> This parameter is relevant for SH-16 and
margin for the measured ASMi-54C/ETH modules only, when line probing is
signal-to-noise ratio enabled.
relative to the current The range is -10 db to +21 dB).
noise level
STU-R.
Using no current-margin disables the use of the
signal-to-noise ratio measured relative to the
current noise level.
Alternatively, line activation may be performed in
accordance with the Worst Margin value.
Specifying the target worst-margin <value in db> This parameter is relevant for ASMi-54C/ETH and
margin for the measured SH-16 only, when line probing is enabled.
signal-to-noise ratio The range is -10 db to +21 dB.
relative to the reference
worst-case near-end
STU-R.
crosstalk noise specified in
ITU-T Rec. G.991.2 Using no worst-margin disables the use of the
signal-to-noise ratio measured measured relative to
crosstalk.
Alternatively, line activation may be performed in
accordance with the Current Margin value.
Setting the number of remote-ch1-ts-num <value> The available selections are 0 to 31.
timeslots connected to This parameter is relevant only for ASMi-54C/N
CH1 (E1) on the remote when the remote modem is ASMi-52/ASMi-52L MUX
modem type

Activating power feeding power-feeding {local |forward} local – provides power feeding only to the nearest
to this SHDSL line repeater
forward – provides power feeding to the nearest
repeater and forwards it also to the next one (this
feature is available only for RAD’s S-RPT/EFM
repeaters)
Using no power-feeding disables the power feeding
of this line.
This command is not available for a module working
in STU-R mode.
See also Megaplex-4 I/O Modules Installation and
Operation Manual, SHDSL Modules Chapter, Working
with Power Feeding, in ASMi-54C Modules and SH-16
Modules sections.
 To verify the SHDSL port parameters:

• At the config>port>shdsl>(<slot>/<port>)# prompt, type info detail.
The configured SHDSL port parameters are displayed.
For example:
mp4100>config>port>shdsl(2/1)# info detail
name "IO-2 shdsl 01"
far-end-type managed
wires 4
stu central
power-backoff default 0
power-feeding local
data-rate maximum 5632
loop-attenuation-threshold 0
snr-margin-threshold 0
clock-mode plesiochronous1
no shutdown
Displaying the Status of SHDSL Port and Repeaters

You can display the status and configuration of an individual SHDSL port. If
relevant, the display also shows the number and parameters of SHDSL repeaters
installed in the line. For each repeater and wire, the values of SNR Margin (db)
and Loop Attenuation (db) are displayed on the Network and Customer sides.
 To display status of an SHDSL port:

• At the prompt config>port>shdsl(<slot/port)#, enter show status.
The SHDSL port status parameters are displayed.
Note The possible status values are interpreted as follows:

• ON – Power feeding is connected
• OFF – Power feeding is disconnected

• Failure – Current overload or failure on the line

• N/A – Power feeding is not relevant for this module
mp4100>config>port>shdsl(8/1)# show status

Interface Type : STU-C
Far-End-Device-Type : MP-card
Wires : 4
Transmission Mode : B-G
Line Rate (Kbps) : 1552
HW Type : shdsl
Number Of repeaters : 1
Wires
----------------------------------------------------------------------
State SNR Loop Power Power
Margin Attenuation Backoff Feeding
(db) (db)
----------------------------------------------------------------------
Data 23 0 6 ON
Repeater Number : 1
Repeater Side : Customer Network

Wire Num : 1 2 1 2
SNR Margin (db) : 23 23 24 24
Loop Attenuation (db) : 0 0 0 0
Loopback Type : Remote
Testing SHDSL Ports

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

transmission through a selected SHDSL port: this path starts at the other port(s)
within the same Megaplex-4 chassis that are connected to the selected port,

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

The remote port loopback is used to test the SHDSL modem circuits of a selected
SHDSL external port. This test also checks the transmission plant connecting the
remote equipment to the corresponding port of the I/O module.
A typical remote port loopback signal path is shown in Figure 6-24.

Megaplex-4100
CL M8SL
Port 1
. .
. .
Other Port Routing Bus . .
Interface Matrix Interface .. ..
.
.
Port 8
Figure 6-24. Remote Port Loopback Signal Path

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

The remote loopback on remote unit is relevant for M8SL, SH-16 and ASMi-54C/N
SHDSL ports connected to remote modems. This loopback is used to test all the
circuits of the corresponding module port, the line to the remote unit, and the
operation of the remote unit.
When this loopback is activated, the selected port sends a remote loopback
request to the remote modem connected to that channel. The command is sent
through the inband eoc channel configured on the remote modem.
Figure 6-25 shows the signal paths of a typical remote loopback on the remote
ASMi-52/ASMi-52L.

Figure 6-25. Remote Loopback on Remote Unit, Signal Paths
Activating SHDSL Loopbacks

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

1. Navigate to configure port shdsl <slot>/<port> to select the SHDSL port to
configure.
The config>port>shdsl>(<slot>/<port>)# prompt is displayed.
Before activating the remote-on-remote loopback on an SHDSL port, be aware

that if Ethernet services are being provided by the system, the traffic passing
Warning through the SHDSL port will be looped. Take appropriate care to prevent this
scenario. Do not activate this loop when the system is connected to the live
network.
Setting loopback duration loopback {local | remote | remote-on- Local and remote loopbacks are available
and activating the remote } [ duration <duration in for M8SL modules only.
corresponding loopback on minutes 1..30> ] Using no loopback disables the loopback
this port
 To perform a loopback on an SHDSL repeater:

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

Activating the remote loopback remote Using no loopback remote disables the
loopback on the repeater loopback
The following tables list messages generated by Megaplex-4 when a configuration
error on SHDSL modules is detected.
Table 6-38. ASMi-54C and SH-16 Configuration Error Messages
510 Error INCORRECT SHDSL LINES IN When the configured TC Layer is 64/65-Octets, the wrong
PCS combination of SHDSL lines is used in a PCS
511 Error SHDSL ADMIN IS NOT One of the SHDSL lines is in “shutdown” state
CONNECTED
512 Error ILLEGAL SHDSL RATE The selected SHDSL rate is not compatible with the
selected operating mode
513 Error NOT IDENTICAL SHDSL When the Wire parameter of an SHDSL line is configured
DEFINITION to 4W or 8W, all the parameters of the corresponding
SHDSL wire pairs must be identical
514 Error ILLEGAL PCS DEFINITION FOR When the STU side is configured as the Remote, and the
STU-R TC Layer is 64/65 Octets, the only PCS and SHDSL line
combinations allowed are as follows:
• PCS 1 can bound to SHDSL lines 1, or 1,2, or 1,2,3,4
• PCS 5 can bound to SHDSL lines 5, or 5,6, or 5,6,7,8
515 Error NOT IDENTICAL LINE PROBE When the STU side is configured as the Remote, Line
DEFINITION Probe (line-prob) must be enabled
516 Error NOT IDENTICAL WIRE NUMBER When the TC Layer is 64/65-Octets, the wires parameter
DEFINITION must be set to 2W
517 Error AT LEAST ONE MARGIN MUST When line probing is enabled, either the current-margin or
BE SET worst-margin parameter must be enabled and set
518 Error ILLEGAL SHDSL DEFINITION When the STU side is configured as the Remote, and the
FOR STU-R TC Layer is HDLC, only SHDSL lines 1 and 5 can be set to
4W or 8W.
519 Error ILLEGAL NUMBER OF WIRE When the TC Layer is HDLC, the wires parameter of the
COMBINATION SHDSL lines must be configured according to Supported
Lines versus Wires Parameter table in ASMi-54C module
section of Megaplex-4 I/O Modules Installation and
Operation Manual, SHDSL Modules Chapter.

520 Error ILLEGAL E1-i DEFINITION When the TC Layer is HDLC, the E1-i port is configured to
“no shutdown” and the corresponding SHDSL line to
“shutdown” (make sure that only the allowed e1-i ports
are set to “no shutdown”).
When the TC Layer is 64/65 Octets, one of the e1-i ports
is set to “no shutdown”
521 Error STU-MODE MUST BE THE SAME The STU parameter of all the SHDSL lines in a module
IN ALL LINES must be set to same value
522 Error TC-LAYER MUST BE THE SAME The TC Layer parameter of all the SHDSL lines in a module
IN ALL LINES must be set to same value
524 Error TS0 MODE DOESN'T FIT TO Contradiction between TS0 mode and line type
LINE TYPE
525 Error FE TYPE MUST BE THE SAME IN Far-end-type parameter must be set to the same value for
ALL LINES all SHDSL ports (not for SH-16).
526 Error ILLEGAL PCS BINDING When working in 4W/8W mode, some PCS ports cannot be
bound to some SHDSL ports. For allowed binding, see
Supported Ports versus Wires Parameter table in
Megaplex-4 I/O Modules Installation and Operation
Manual, SHDSL Modules Chapter.
527 Error ILLEGAL PARAM VALUE FOR When far-end-type=high-speed-mux-serial-e1, the

E1-I PORT following combinations (either of them) at the
corresponding e1-i port are illegal:
• inband-management is activated
• wires=4 + line-type=g732n + ts0-over-dsl = yes
• wires=4 + line-type=unframed + ts0-over-dsl = no.
If one of these statements is true, modify the
corresponding settings.
528 Error UNUSED E1-I PORT IS Even E1-i ports cannot be connected when working in 4W
CONNECTED mode.
529 Warning FAR-END CHANGED, DEVICE When far-end-type=high-speed-mux-serial-e1 is selected

WILL RESTART instead of another far-end-type setting, both the
ASMi-54C module and the remote modem will be
automatically restarted (SH-16 module will not restart).
530 Error DATA RATE EXCEEDS MAXIMAL The data rate configured for SHDSL port exceeds the
RATE maximum rate (see SH-16 SHDSL Data Rates and
ASMi-54C SHDSL Data Rates tables in Chapter 7 of the
Megaplex-4 Modules Installation and Operation Manual).
531 Error DATA RATE NOT SUPPORTED For 4W/HDLC operation, rates 17024 to 18432 kbps are
unavailable.
532 Error ILLEGAL REMOTE CH1 TS The number of timeslots connected to CH1 (E1) on the
NUM remote modem (remote-ch1-ts-num) exceeds the number
of open timeslots (not for SH-16).

533 Error CL-DS0/HIGH-SPEED-MUX- Far-end-type=high-speed-mux-serial-e1 is not supported

SERIAL-E1 NOT SUPPORTED" when CL.2 type is DS0 only.
534 Error POWER-FEEDING MUST BE THE When 2 lines are bonded together, power feeding must be
SAME IN SHDSL LINES either On or Off for both lines.
536 Error STU-C MODE CAN'T BE A port configured in STU-C mode cannot be selected as a
SELECTED AS CLOCK SOURCE clock source
537 Error ILLEGAL_FAR_END_TYPE_FOR For a port working in STU-R mode, far-end-type can be
STU-R MODE only “non-managed”.
538 Error ILLEGAL_PARAMETER_FOR When working with tc=64-65-octets, the following

TC_LAYER_64-65 OCTET parameters cannot be configured (SH-16 only):
• far-end-type= high-speed-mux-serial-e1
• clock-mode=plesiochronous1
Table 6-39. M8SL Configuration Error Messages
220 Error RATE/TS ASSIGNMENT The line rate configured for the M8SL port must match the
MISMATCH number of timeslots assigned
221 Error CLOCK REFERENCE PORT The M8SL port configured as clock reference must be
SHOULD BE SET STU-R configured as STU-R
222 Error MAX BANDWIDTH MISMATCH Maximum bandwidth configured on the SHDSL line must
match the number of timeslots assigned
Displaying SHDSL Port Statistics

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

At the prompt config>slot>port>shdsl (<slot>/<port>)#, enter show statistics
followed by parameters listed below. <wire-num> specifies the number of the
SHDSL interface wire for which the statistics is displayed.
Note
Day statistics (all types) are supported only for ASMi-54C/ETH and SH-16, other
statistic types are supported by all SHDSL modules.

Displaying show statistics <wire-num> {all | all-intervals | all- All SHDSL modules:
statistics days-interval | current | current-day} • current - current statistics (up to
15 min)
• all-intervals - all intervals during
the last 24 hours
Additional statistics (ASM-54C/ETH
and SH-16 modules only):
• current-day - current today's
statistics
• all-days-interval - all intervals
during the last 7 days
• all - current, all-intervals,
current-day, all-days-interval
Displaying show statistics <wire-num> interval <interval-num All SHDSL modules

statistics for a 1..96>
specific 15-min
interval
Displaying show statistics <wire-num> day <day-num 1..7> ASMi-54C/ETH only

statistics for a
selected day
SHDSL port statistics are displayed. For example:

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

mp4100>config>port>shdsl(4/2)# show statistics 1 current-day

Wire Num : 1
Current Day
---------------------------------------------------------------
Valid Days : 0
ES : 0 LOSWS : 11
UAS : 1163
Statistics for Day 1, Wire 1 (ASMi-54C/ETH):

mp4100>config>port>shdsl(4/2)# show statistics 1 day 1
Wire Num : 1
Day Interval
---------------------------------------------------------------
Day Number : 1
ES : 0 LOSWS : 1
UAS : 395
The counters are described in the table below.
Table 6-40. SHDSL Statistics Parameters
Time elapsed (for current The elapsed time (in seconds) since the beginning of the current interval, in
interval) seconds. The range is 1 to 900 seconds
Time elapsed (for current The elapsed time (in seconds) since the beginning of the current day, in
day, ASMi-54C/ETH only) seconds. The range is 1 to 8640 seconds
Interval number Number of interval for which statistics are displayed

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

interval/day/week.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared

UAS The number of unavailable SHDSL seconds (UAS) in the current/selected

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

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

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

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

At the prompt config>port>shdsl (<slot>/<port>) repeater (repeater ID)#, enter
show statistics running.
SHDSL statistics are displayed separately for each repeater and each wire
on the customer and the network side. The number of columns depends
on number of wire-pairs configured in the line menu. The statistics are
accumulated since the corresponding SHDSL port of the ASMi-54C/N
module is on.

For example:
mp4100>config>port>shdsl(2/5)# repeater 1
mp4100>config>port>shdsl(2/5)>repeater(1)# show statistics
running
Repeater Side : Customer Network
Wire Num : 1 2 1 2
ES : 4 4 0 0
SES : 0 0 0 0
UAS : 248 248 47 47
LOSWS : 248 248 47 47
CRC Anomalies : 19 19 0 0
The counters are described in the table below.
Table 6-41. SHDSL Repeater Statistics Parameters
ES The number of errored SHDSL seconds (ES) accumulated since the module is
on.
An SHDSL ES is a second during which one or more CRC anomalies are
declared, and/or one or more LOSW defects are declared
UAS The number of unavailable SHDSL seconds (UAS) accumulated since the
module is on.
The SHDSL UAS is a second during which the SHDSL line is unavailable. The
SHDSL line becomes unavailable at the onset of 10 contiguous SESs (the 10
SESs are included in the unavailable time).
Once unavailable, the SHDSL line becomes available at the onset of 10
contiguous seconds with no SESs (the 10 seconds with no SESs are excluded
from the unavailable time)
SES The number of severely errored SHDSL seconds (SES) accumulated since the
module is on.
The SHDSL SES is any second which is not declared a UAS, during which at
least 50 CRC anomalies are declared, or one or more LOSW defects are
declared
CRC Anomalies The number of CRC anomalies accumulated since the module is on.
A CRC anomaly is declared when the CRC bits generated locally on the data in
the received SHDSL frame do not match the CRC bits (crc1 - crc6) received
from the transmitter. A CRC anomaly only pertains to the frame over which it
was declared.
LOSWS Displays the number of SHDSL LOSW seconds (LOSWS) accumulated since
the module is on.
The SHDSL LOSWS is a second during which one or more SHDSL LOSW
defects are declared
Clearing Statistics
 To clear the statistics for an SHDSL port:

• At the prompt config>port>shdsl<slot>/<port>)#, enter clear-statistics.


You cannot clear repeater statistics.
Note If the SHDSL cable is removed, the repeater statistics is cleared. However, do not
use this as a method to clear repeater statistics.
T1 Ports
Applicable Modules
The following table shows the number of t1 and t1-i ports and the features
supported by each Megaplex-4 module. The digits in brackets (1 to 3) denote
restrictions or other special remarks regarding implementation of this feature in
specific modules.
Table 6-42. Megaplex-4 T1 and Internal T1 Ports
T1 Ports (t1) Internal T1 Ports

(t1-i)
Feature/
Command M8T1 M16T1 T3 VS- VS- VS-6/E1T1 CL.2 VS-
16E1T1- 16E1T1- 16E1T1-
EoP PW EoP
Number of ports 8 16 28 16 16 8 84 16
name √ √ √ √ √ √ √ √
shutdown √ √ √ √ √ √ √ √
slot: slot: slot:1 slot: slot: slot: slot: slot:

hierarchy port port :trib port port port port port
inband- √ (1) √(1)(4) √(1) √(1) –

management √(1) √(1) √(1)
line-interface √ – – √ √ √ – –
line-type √(2) √ √ √ (5) √ √ √ √
line-length (DSU √ √ √ –
only) √ √ – –
line-code √ √ – √ √ √ – –
line-buildout (CSU –
only) √ – – √ √ √ –
out-of-service √ (1) √ (1) √ (1) √ (1) –

(voice, data,
signaling) √ (1) √ (1) √ (1)
restoration-time √ – √ – – – – –
signaling- profile √ (1) – – – – – – –

T1 Ports (t1) Internal T1 Ports

(t1-i)
Feature/
Command M8T1 M16T1 T3 VS- VS- VS-6/E1T1 CL.2 VS-
16E1T1- 16E1T1- 16E1T1-
EoP PW EoP
timeslots-signaling- – – – –
profile √ (1) – – –
idle-code √ (1) √ (1) √ (1) √ (1) √ (1) √ (1) √ (1) –
vc-profile – √ (3) √ √ (3) √ (3) √ (3) √ √
tx-clock-source – – – – √(6 ) √(6 ) – –
1 - N/A for Unframed
2 – Unframed is not supported when working with CL.2 module without SDH/SONET
ports
3 – Applicable if line type is unframed and the link is directly mapped to SDH-SONET
vc12-vt2
4 –N/A for T1 bound to VCG
5 –When T1 is bound to VCG, line-type=esf only
6 - Applicable when T1 is cross connected directly to PW
Standards
The T1 interface complies with ANSI T1.403-1989, AT&T Pub. 54016, AT&T
TR-62411 and ANSI T1.107.4 standards.
External T1 Link Interfaces are available in M8T1, VS-16E1T1-PW, VS-6/E1T1,
VS-16E1T1-EoP and M16T1 I/O modules. Internal T1 ports are available in CL.2
and VS-16E1T1-EoP modules (denoted in CLI as t1-i) and T3 modules (denoted in
CLI as t1). The parameters configurable for each module can be chosen from
Table 6-10 . General description of T1 port parameters is given in the following
sections.
Framing
The external and internal T1 ports can be independently configured in accordance
with the desired ITU-T framing mode and signaling formats:
• D4 (SF) framing (12 frames per multiframe)
• ESF framing (24 frames per multiframe)
• Unframed mode: enables transparent transfer of 1.544 Mbps streams,
including streams with proprietary framing.

The framing mode can be independently selected for each extermal or internal T1
port of the I/O module. It is configured by means of line-type parameter.
Line Interface (M8T1, VS-16E1T1-EoP, VS-16E1T1-PW, VS-6/E1T1

Only)
Each T1 line interface has an integral CSU, which enables operation with line
attenuations up to 34 dB. The nominal transmit level is ±3V.
The CSU transmit level must be adjusted to ensure reliable operation of the
network. It can be attenuated by 7.5, 15, or 22.5 dB, for compliance with FCC
Rules Part 68A. This adjustment minimizes the interference your transmit signal
causes to other users that transmit their signals on other pairs of the same cable.
The required setting depends mainly on the length of the cable that connects the
T1 port and the first repeater down the line.
Repeaters are usually spaced a mile apart. They are therefore designed to
optimally handle signals attenuated by one mile length of cable. If the T1 port
were closer, the repeater would receive your signal at a higher level. This will not
significantly improve the handling of your signal, but will certainly increase the
interference coupled from your pair to repeaters that serve other pairs in the
cable. To prevent this, you can select an attenuation value that will bring your
signal level closer to the expected repeater signal level. This is achieved by
connecting, as required, one, two, or three artificial line sections in series with
your T1 transmit signal. Each line section introduces a nominal attenuation of
7.5 dB (equivalent to the attenuation of approximately 1000 feet of cable). Your
system administrator or data carrier will give you the proper setting for each
port.
The line interface can also emulate a DSU interface. The selection CSU/DSU is
defined by the line-interface parameter. The relative output transmit level of the
port is selected by means of the line-buildout parameter.
Line Length
When configured for DSU emulation, the line transmit signal is user-adjustable for
line lengths of 0 to 655 feet in accordance with AT&T CB-119. The transmit signal
mask is selected in accordance with the transmit line length, to meet DSX-1
requirements, as specified by AT&T CB-119. The following selections are
available:
• 0 – 133 Ft
• 133 – 266 Ft
• 266 – 399 Ft
• 399 – 533 Ft
• 533 – 655 Ft.
These values define the length of the cable (in feet) connected between the port
connector and the network access point.

Zero Suppression
Zero suppression is user-selectable, separately for each port: transparent (AMI)
coding, B7ZS, or B8ZS. It is configured by means of line-code parameter.
Interface Type
The external T1 links have 100 Ω balanced interfaces.
Handling of T1 Alarm Conditions

The external and internal T1 ports support two types of indications in the individual
timeslots: idle timeslots and out-of-service (OOS) indications.
• Idle Timeslot Indication. A special code can be transmitted in empty timeslots
(timeslots which do not carry payload).
• OOS Indications. The OOS code is inserted in individual timeslots to signal the
equipment routed to one of the module ports that the link connected to the
external port is out-of-service (e.g., because of a loss of frame
synchronization).
The idle code and OOS indications can be independently configured for each
module port. Moreover, separate OOS codes can be transmitted in the timeslots,
in accordance with the type of payload carried by each timeslot (voice or data).
T1 Payload Processing
The Megaplex-4 T1 modules support three main types of payload per timeslot:
• Data timeslots: timeslots which are transparently transferred from port to
port. In general, it is assumed that no CAS is associated with data timeslots.
Timeslots assigned to HDLC ports are always processed as data timeslots.
• Voice timeslots: timeslots carrying PCM-encoded payload, with A-law
companding for M8E1 ports and µ-law companding for M8T1 ports. When
transferred between ports with different standards (for example, between E1
and T1 ports), these timeslots are converted by the CL module.
In general, CAS is always associated with voice timeslots, and therefore it
must also be converted when transferred between ports with different
standards. The user can specify translation rules for the signaling
information, called signaling profiles – see details in the Signaling Profiles
section.
• Management timeslots: with framed signals, one timeslot can be assigned in
any port to carry management traffic. Such timeslots are always directed to
the CL management subsystem, for processing.
The flow of payload carried by voice timeslots is normally bidirectional (full duplex
connection). It is also possible to define unidirectional flows, called unidirectional
broadcasts, from one source (a timeslot of a source port) to multiple destinations
(each destination being a selected timeslot of another port).
In case of data timeslots, the flow of payload is normally unidirectional. If the
application requires bidirectional flows, cross-connect must be configured
symmetrically for both directions.

OOS Signaling
If communication between modules located in different Megaplex units fails, e.g.,
because loss of main link synchronization, it is necessary to control the state of
the signaling information at each end of the link. This activity, called
out-of-service (OOS) signaling, is performed by the M8T1 modules and can be
selected in accordance with the specific application requirements, on a per-link
basis.
The OOS signaling options supported by the M8T1 modules are as follows:
• Signaling forced to the idle state for the duration of the out-of-service
condition (force-idle). This option is suitable for use with all the VC module
types.
• Signaling forced to the busy state for the duration of the out-of-service
condition (force-busy). This option is suitable for use with E&M and FXO
modules, but not with FXS modules.
• Signaling forced to the idle state for 2.5 seconds, and then changed to the
busy state for the remaining duration of the out-of-service condition
(idle-busy). This option is suitable for use with E&M and FXO modules, but
not with FXS modules.
• Signaling forced to the busy state for 2.5 seconds, and then changed to the
idle state for the remaining duration of the out-of-service condition
(busy-idle). This option is suitable for use with all the VC module types.
Inband Management
T1 and internal T1 ports of Megaplex-4 using a framed mode feature inband
management access to the end user’s equipment provided by configuring a
dedicated management timeslot.
The transfer of inband management traffic is controlled by using synchronous
PPP over HDLC encapsulation or Frame Relay encapsulation (under DLCI 100) in
accordance with RFC 2427.
Transmission of RIP2 routing tables is done via the following options:
• Proprietary RIP – Management traffic is routed using RAD proprietary routing
protocol
• RIP2 – In addition to the RAD proprietary routing protocol, RIP2 routing is
also supported.
Factory Defaults
Megaplex-4 is supplied with all t1/t1-i ports disabled. Other parameter defaults
line-type esf
restoration-time 10sec
line-interface csu

idle-code 0x7f
out-of-service - voice 00
out-of-service - data 00
out-of-service - signaling force-idle
signaling-profile 1
line-code b8zs
line-length 0-133
line-buildout 0db
duration infinite
Configuring a T1 Port
 To configure the T1 port parameters of I/O modules:

1. Navigate to configure port t1 <slot>/<port>/<tributary> to select the T1 port
to configure.
The config>port>t1>(<slot>/<port>/<tributary>)# prompt is displayed.
Note <tributary> refers to T1 ports of T3 modules.
2. Enter all necessary commands according to the tasks listed below (see
Table 6-42 for parameters supported in each module).

description to port

port
Specifying T1 framing line-type {unframed | esf | sf} When the T1 port is bound to a VCG port,
mode VS-16E1T1-EoP supports esf option only.
Setting the line code line-code {ami | b8zs} For guaranteed clear channel capability, use
used by the port, and the B8ZS; do not use B7ZS for ports carrying
zero suppression method inband management
Specifying T1 operation line-interface {dsu | csu}

mode
Specifying the length of line-length {0-133 | 134-266 | 267-399 |

the T1 line in DSU mode 400-533 | 534-655}

Specifying the code idle-code <00 to FF (hexa)> The available selections are [0x40 to 0x7F]
transmitted to fill unused and [0xC0 to 0xFF]
timeslots in T1 frames
management and setting {ppp | fr} [routing-protocol {none | encapsulation
its parameters prop-rip | rip2} ] fr –Frame Relay encapsulation (under DLCI
timeslot
Not available for VS-16E1T1-EoP when this
T1 port is bound to a VCG port
Transmitting an out-of-service [ voice <00 to FF (hexa)>]

out-of-service signal [data <00 to FF (hexa)>] [signaling
(OOS) {force-idle | force-busy | idle-busy |
busy-idle} ]
Specifying the signaling signaling-profile { 1 | 2 | 3 | 4 | 5 | per-ts} Using no signaling-profile cancels signaling

profile profile setting
For creating and configuring signaling
profiles, see Signaling Profiles.
Specifying the signaling timeslots-signaling-profile [tsx] {1 | 2 | 3 | This command is available for voice
profile per a single 4 | 5} timeslots only, if you selected per-ts under
timeslot or per timeslot timeslots-signaling-profile [tsx..tsy] {1 | 2 | signaling-profile
range 3 | 4 | 5} This command is possible for multiple
timeslots only if they are consecutive
Setting the time required restoration-time {1sec | 10sec} Used to change the frame synchronization
for a port to resume algorithm, to reduce the time required for
1sec – After 1 second.
10sec – Similar to the requirements of AT&T
TR-62411 (after 10 seconds).
Specifying the line build- line-buildout {0db | -7dot5db | -15db | M8T1, VS-16E1T1-EoP, VS-16E1T1-PW and
out (relative output -22dot5db} VS-6/E1T1 modules only
transmit level of the port) CSU mode only

Selecting the timing tx-clock-source loopback loopback – Clock received from the E1/T1
reference source used by tx-clock-source domain <number> port
the port for the domain – Clock provided by system clock
tx-clock-source through-timing
transmit-to-network domain
direction
through-timing – Clock received from
VC12/VT1.5 or PW (according to the
transport network)
This field is valid for VS-16E1T1-PW and
VS-6/E1T1 modules only.
Assigning VC profile to vc profile <profile name> Relevant for M16T1, VS-16E1T1-EoP and T3
the port modules, VS-16E1T1-PW, VS-6/E1T1. M8T1
does not support this feature.
For creating VC profiles, see VC Profiles.
Using no vc removes the profile.
Configuring an Internal T1 Port
 To configure the internal T1 port parameters:

1. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
configure.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.

description to port

port
Specifying T1 framing line-type {unframed | esf | sf} When the internal T1 port is bound to a VCG
mode port, VS-16E1T1-EoP supports esf option
only.
Specifying the code idle-code <00 to FF (hexa)> The available selections are [0x40 to 0x7F]
transmitted to fill unused and [0xC0 to 0xFF]
timeslots in T1 frames

management and setting {ppp | fr} [routing-protocol {none | encapsulation
its parameters prop-rip | rip2} ] fr –Frame Relay encapsulation (under DLCI
Not available for VS-16E1T1-EoP when this
T1 port is bound to a VCG port
timeslot
Setting the time required restoration-time {1sec | 10sec} Used to change the frame synchronization
for a port to resume algorithm, to reduce the time required for
1sec – After 1 second.
10sec – Similar to the requirements of AT&T
TR-62411 (after 10 seconds).
Assigning VC profile to vc profile <profile name> Using no vc removes the profile

the port
Example 1
14B
The following example illustrates how to configure the T1 port labeled 1 on the
M8T1 module installed in slot 9 as follows:
• Set the T1 framing mode to SF.
• Set the restoration time to 10 sec.
• Set the line code to AMI.
• Set the idle code to 8E.
mp4100>config>port>t1(9/1)# line-type sf
mp4100>config>port>t1(9/1)# line-code ami
mp4100>config>port>t1(9/1)# restoration-time 10sec
mp4100>config>port>t1(9/1)# idle-code 0x8E
mp4100>config>port>t1(9/1)# no shutdown
Example 2
145B
This section illustrates how to configure inband management via a dedicated

timeslot on M8T1 Module.

1. Program an M8T1 module in Slot 1 and configure inband management via T1

port 1 with the following parameters:
 Dedicated timeslot - #24
 Inband management protocol: synchronous PPP over HDLC encapsulation
mp4100>config>slot# 4 card-type e1-t1 m8t1
mp4100>config>port# t1 1/1 no shutdown
mp4100>config>port# t1 1/1 line-type sf
mp4100>config>port# e1 1/1 inband-management 24 protocol ppp
routing-protocol prop-rip
2. Configure router interface 5.
mp4100>config>router# 1 interface 5 address 17.17.17.17/24
3. Bind T1 port 1/1 to router interface 5.
mp4100>config>router# 1 interface 5 bind t1 1/1
Example 3
This section illustrates how to set signaling profile on timeslots.
1. Activate T1 port 2 of M8T1 module in Slot 9.
2. Configure signaling profile per ts:
 TS-10 to profile 2
 TS-1 to 9 to profile 3
mp4100>config>port>e1(9/2)# signaling-profile per-ts
mp4100>config>port>e1(9/2)# timeslots-signaling-profile 10 2
mp4100>config>port>e1(9/2)# timeslots-signaling-profile [1..9] 3
mp4100>config>port>e1(9/2)# commit
Result : OK
3. Displaying signaling profile per ts:

mp4100>config>port>t1(9/2)# info detail

name "IO-9 e1 02"
no shutdown
line-type sf
line-code ami
idle-code 0x7f
restoration-time 10sec
out-of-service voice 0x00 data 0x00 signaling force-idle
signaling-profile per-ts
error on T1 modules is detected.
Table 6-43. T1 Configuration Error Messages
131 Warning RESTORATION TIME DOES NOT For T1 links, the restoration time must be 10 seconds,
MATCH THE STD according to the standard.
132 Error FRAME TYPE / PROFILE The selected framing mode does not support signaling
MISMATCH profiles.
141 Error ROUTING PROTOCOL/ The rip2 protocol on an I/O module port can be enabled
MNG TYPE MISMATCH only when the inband management method is configured
to ppp or fr
144 Error ILLEGAL IDLE CODE SELECTION Code transmitted in idle timeslots is illegal. The available
selections for T1/T1-i ports are [0x40 to 0x7F] and [0xC0
to 0xFF]
146 Error NUM OF E1/T1 PORTS The maximum number of framed T1 ports opened on the
EXCEEDS 120 M16T1 modules must not exceed 120.
Viewing a T1 Port Status

Follow the instructions below for viewing the status of a T1 port.
 To view the T1 port status:

• At the config>port>t1(<slot>/<port>/<tributary>)# prompt, enter show
status.

Note The index <tributary> is applicable to internal T1 ports of T3 modules.

For T1 ports of M8T1, M16T1 modules:
mp4100>config>port>t1(5/1)# show status
Name : IO-5 t1 01
Connector Type : DB44
For T1-i ports of CL.2 modules:
mp4100>config>port>t1-i(cl-a/1)# show status
Name : CL-A t1-i 01
For T1 ports of T3 modules:
mp4100>config>port>t1(3/1/1)# show status
Name : IO-1 t1 01/01
Testing T1 Ports
The Megaplex-4 T1 ports feature test and loopback functions at the port and
timeslot levels. The following loops are supported on all t1/t1-i ports:
• Local loopback on t1/t1-i module port
• Remote loopback on t1/t1-i module port
• Local loopback on timeslots of t1/t1-i module port
• Remote loopback on timeslots of t1/t1-i module port.
In addition, M8T1 modules support network line loopback (LLB) and network
payload loopback (PLB). T1 ports of other I/O modules do not support
network-controlled loopbacks.
The hierarchical position of t1 ports is as follows:
• For t1 ports of T3 modules: slot:1:tributary
• For t1 and t1-i ports of other modules: slot:port.
CL Modules
The following sections briefly describe each type of loopback on T1-i ports of CL
modules. Table 6-44 shows the paths of the signals when each or loopback is
activated.

Table 6-44. Loopbacks on T1-i ports of CL.2 Modules
Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
DS1 . SDH/
SONET
Mapper Matrix
Matrix .. Framer
..
.
E1-i/T1-i Framers
Local loopback on
2
T1-i port ..
..
..
E1-i/T1-i Framers
Remote loopback on
T1-i port 2
..
..
..
E1-i/T1-i Framers
Local loopback on
2
timeslots of ..
T1-i port ..
..

Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
DS1 . SDH/
SONET
Mapper Matrix
Matrix .. Framer
..
.
E1-i/T1-i Framers
Remote loopback on
2
timeslots of ..
T1-i port ..
..
Local Loopback on T1-i Port

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

The T1-i port remote loopback is activated on the framer serving the port within
the SDH/SONET link interface, as shown in Table 6-44.
Local Loopback on T1-i Port Timeslots

The local loopback on selected timeslots of a T1-i port is used to return the
the receive path. The timeslots looped back remain connected to the transmit
path of the port, but the corresponding timeslots received from the remote end
are disconnected.

This test is recommended for testing the signal paths between the T1-i port and
an I/O port of another module that uses only a fraction of the available T1-i port
bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 6-44. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
You can activate the loopback on any individual timeslot, or on several arbitrarily
selected timeslots. You cannot activate loopbacks on timeslots cross-connected
with HDLC ports.
Remote Loopback on T1-i Port Timeslots

The remote loopback on selected timeslots of a T1-i port is used to return the
the transmit path. The corresponding timeslots received from the local equipment
are disconnected.
through the selected timeslots of the T1-i port, to an I/O port of another module
that uses only a fraction of the available port bandwidth.
The loopback is activated only on the timeslots specified by the user, as shown in
Table 6-44. As a result, there is no disturbance to services provided by means of
the other timeslots of the same T1-i port: only the flow of payload carried by the
specified timeslots is disrupted. You cannot to activate loopbacks on timeslots
assigned to HDLC ports.
I/O Modules
The following sections briefly describe each type of loopback on T1 ports of I/O
modules. Table 6-15 shows the paths of the signals when each or loopback is
activated.
Table 6-45. Loopbacks on T1 Ports of I/O Modules
I/O CL
Local loopback on T1 port (M8T1, DS1

Port Cross-Connect
M16T1, VS-16E1T1-EoP, VS-16E1T1-PW, Interface
Matrix
VS-6/E1T1, T3 modules)
"1 "
Remote loopback on T1 port (M8T1, DS1

Port
M16T1, VS-16E1T1-EoP, VS-16E1T1-PW, Interface
Cross-Connect
Matrix
VS-6/E1T1 modules)

I/O CL
I/O Interface
1
Local loopback on T1 timeslots (M8T1, DS1
2
M16T1, VS-16E1T1-PW, VS-6/E1T1, .. Cross-Connect
VS-16E1T1-EoP modules) .. Matrix
.
I/O Interface
1
Remote loopback on T1 timeslots DS1
2
(M8T1, M16T1, VS-16E1T1-EoP, .. Cross-Connect
VS-16E1T1-PW, VS-6/E1T1 modules) .. Matrix
.
Local Loopback on T1 Port of I/O Module

transmission through a selected T1 port: this path starts at the other
Megaplex-4 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.
To provide a keep-alive signal to the transmission equipment serving the link
under test while the loopback is activated, the port line interface transmits an
unframed “all-ones” signal (AIS) to the line. AIS reception will cause the remote
equipment to lose frame synchronization while the loopback is connected. This is
normal and does not necessarily indicate a fault.
Remote Loopback on T1 Port of I/O Module

T1 external port. This test also checks the transmission plant connecting the
As shown in Table 6-15, when a remote loopback is activated on a T1 port, that

Local Loopback on Timeslots of T1 I/O Module Port

The local loopback on selected timeslots of a T1 port is used to return the
the receive path. This test is recommended for testing the signal paths between
an I/O port of another module that uses only a fraction of the available port
bandwidth, and the T1 port.
of the other timeslots of the same port: only the flow of payload carried by the
arbitrarily selected timeslots. It is not allowed to activate loopbacks on timeslots
assigned to HDLC ports.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the protection
group (even if it has been activated by a command to the other port).
Remote Loopback on Timeslots of T1 I/O Module Port

The remote loopback on selected timeslots of a T1 port is used to return the
the transmit path. This test is recommended for testing signal paths from a
remote equipment unit, through the selected timeslots of the T1 port, to an I/O
port of another module that uses only a fraction of the available port bandwidth.
matrix, and only on the timeslots specified by the user. As a result, there is no
port: only the flow of payload carried by the specified timeslots is disrupted.
It is not allowed to activate loopbacks on timeslots assigned to HDLC ports.
BER Test
The BER test, activated by the command bert, is used to evaluate data
transmission through selected timeslots of the link connected to a selected T1
without using external test equipment. It is available on the M16T1 module ports.

Loopback Duration
Activating Loopbacks and BER Tests
 To perform a loopback or BER test on the T1 port:

1. Navigate to configure port t1 <slot>/<port>/[<tributary>] to select the T1
port to be tested.
The config>port>t1>(<slot>/<port>[<tributary>])# prompt is displayed.

 To perform a loopback on the internal T1 port:

1. Navigate to configure port t1-i <slot>/<port> to select the internal T1 port to
be tested.
The config>port>t1-i>(<slot>/<port>)# prompt is displayed.
Activating and configuring loopback {local | remote} [time- local – local loopback
the direction of the slot <1..24>] [duration <duration remote – remote loopback
loopback and the duration in minutes 1..30> ]
of it (in minutes)
Activating the BER test and bert [ts <ts number 1..24>] The [ts <ts number in the range from 1
configuring its parameters [inject-error single] to 24>] command is used only for
framed ports and is mandatory for these
ports.
The timeslot on which BERT is performed
must be cross-connected.
CL flip stops the BERT session.
Stopping the BER test no bert

Displaying the BER test show bert A typical display:

results Status : Not Active
Bit Error Count: 1
Pattern : 2e-15
Run Time (Sec) : 1
ES (Sec) : 1
Sync Loss (Sec): 1
Clearing the BER test clear-bert-counters
counters
Displaying T1 Port Statistics

T1 and T1-i ports of Megaplex-4 feature the collection of statistical diagnostics
per ANSI T1.403, thereby allowing the carrier to monitor the transmission
performance of the links.
 To display the T1 port statistics:

• At the prompt config>slot>port>t1(<slot>/<port>/[tributary])#, enter show
statistics followed by the parameters listed below.
 To display the T1-i port statistics:

• At the prompt config>slot>port>t1-i(<slot>/<port>)#, enter show statistics
Displaying statistics show statistics {total | all | all-intervals | current} • total - Total statistics of last 96
intervals
• all-intervals – Statistics for all
valid intervals
• current - Current statistics
• all – All statistics: first current
statistics

for a specific
interval
T1 port statistics are displayed. The counters are described in

Table 6-46, Table 6-47 and Table 6-48.
Note BES, LOFC and Rx Frames Slip are displayed for framed formats only and are not
displayed for T1 ports of T3 modules.
For example:

Current statistics:
mp4100>config>port>t1(1/2)# show statistics current
Current
---------------------------------------------------------------
Valid Intervals : 2
ES : 0
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
mp4100>config>port>t1(3/1)# show statistics interval 67
Interval
---------------------------------------------------------------
ES : 16
SES : 1
UAS : 589
BES : 0
Rx Frames Slip : 0
LOFC : 0
Total statistics:
mp4100>config>port>t1(1/2)# show statistics total
Total
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
All statistics:
mp4100>config>port>t1(1/2)# show statistics all
Current
---------------------------------------------------------------
Valid Intervals : 2
mp4100>config>port>e1(1/2)#
ES : 0
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Interval Number : 1
Interval
---------------------------------------------------------------
ES : 0
SES : 0
UAS : 0

BES : 0
Rx Frames Slip : 0
LOFC : 0
Interval Number : 2
Interval
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Total
---------------------------------------------------------------
ES : 2
SES : 0
UAS : 0
BES : 0
Rx Frames Slip : 0
LOFC : 0
Table 6-49. T1 Port Statistics Parameters – Current 15-Minute Interval

An errored second is any second not declared a UAS in which a OOF (Out of Frame) or
CRC (Cyclic Redundancy Check error) occurred.
A SES is any second not declared a UAS which contains an OOF or more than 320 CRC
errors.
BES Displays the number of bursty errored seconds (BES) in the current interval.
A BES is any second which is not declared a UAS and contains 2 to 319 CRC errors
LOFC Displays the number of LOFC in the current interval.

The loss of frame (LOF) counter counts the loss of frame alignment events. The data
is collected for the current 15-minute interval.
Rx Frames Slip Displays the number of Rx Frames Slips in the current 15-minute interval.
A CSS is a second with one or more controlled slip events.
The range is 1 to 900 seconds.

Table 6-50. T1 Port Statistics Parameters – Selected 15-Minute Interval
ES Displays the total number of errored seconds (ES) in the selected interval
UAS Displays the total number of unavailable seconds (UAS) in the selected interval
SES Displays the total number of severely errored seconds (SES) in the selected interval
BES Displays the total number of bursty errored seconds (BES) in the selected interval
LOFC Displays the total number of loss of frame alignment events in the selected interval
Rx Frames Slip Displays the total number of loss of of Rx Frames Slip events in the selected interval
Interval number Displays the number of interval for which statistics is displayed
Note: The sequence of intervals is different for the T1 ports of different module
families:
• For the M8T1 modules, Interval #1 is the latest in time
• For the M16T1 and T3 modules, Interval #1 is the earliest in time.
Table 6-51. T1 Port Statistics Parameters – Total Statistics
ES Displays the total number of errored seconds (ES) since statistics is available
UAS Displays the total number of unavailable seconds (UAS) since statistics is available
SES Displays the total number of severely errored seconds since statistics is available
BES Displays the total number of bursty errored seconds (BES) since statistics is available
LOFC Displays the total number of loss of frame alignment events since statistics is available
Rx Frames Slip Displays the total number of loss of of Rx Frames Slip events since statistics is available
 To clear the statistics for a T1 port:

• At the prompt config>port>t1<slot>/<port>)#, enter clear-statistics.
T3 Ports
Applicable Modules
T3
Standards
The T3 interface complies with ANSI T1.107 and ANSI T1.102 standards.

T3 ports of Megaplex-4 provide access to standard T3 equipment over
unbalanced copper lines with full duplex data rates of 44.7 Mbps, enabling easy
connectivity to a T3/SONET network.
General description of T3 port parameters is given in the following sections.
Framing
The T3 ports can be independently configured in accordance with the desired
framing mode:
• Synchronous M13 (SYNTRAN) in accordance with ANSI T1.107a.
• Asynchronous C-bit parity multiplex applications in accordance with ANSI
T1.107-1995
• Unframed.
The framing mode is configured by means of line-type parameter.
Line Length
The maximum allowed signal attenuation is in accordance with ITU-T Rec. G.703
requirements. For optimal performance, the receive side includes an equalizer
which must be preset in accordance with cable length: up to 225 ft, or more than
225 ft.
This is configured by means of line-length parameter.
Interface Type
The T3 links have 75 Ω unbalanced interfaces.
Factory Defaults
Megaplex-4 is supplied with all T3 ports disabled. Other parameter defaults are
line-type m13
line-length up-to-225ft
vc profile "tug-structure"
Configuring a T3 Port
 To configure the T3 port parameters of I/O modules:

1. Navigate to configure port t3 <slot>/<port> to select the T3 port to
configure.

The config>port>t3>(<slot>/<port>)# prompt is displayed.


description to port
Defining the port as channelized Using no channelized cancels channelization

channelized

port
Specifying T3 framing line-type {c-bit-parity | m13 | unframed} m13 – synchronous M13 multiplex framing
mode mode
c-bit-parity – asynchronous C-bit parity
framing mode
unframed – unframed mode. This mode is
used for transferring Ethernet over T3 and
is not relevant for Ethernet transport over
T1.
Specifying the length of line-length {up-to-225ft | over-225ft}

the T3 line
The following example illustrates how to configure the T3 port labeled 1 on the
T3 module installed in slot 9 as follows:
• Set the T3 framing mode to c-bit-parity.
mp4100>config>port>t3(9/1)# line-type c-bit-parity
mp4100>config>port>t3(9/1)# no shutdown
error on T3 modules is detected.
Table 6-52. T3 Configuration Error Messages
772 Warning MISSING ASSOCIATED T1 IN When T3 is configured as channelized (framed) it must

CHANNELIZED PORT contain at least one T1 port
773 Warning UNCHANNELIZED PORT CANT When T3 is configured as unchannelized (unframed), it

CONTAIN ASSOCIATED T1 cannot contain associated T1 ports
774 Warning SHUTDOWN PORT CONTAINS When a T3 port contains associated open T1 ports, it
ASSOCIATED T1 CHANNELS must be open as well.

775 Error ILLEGAL X-CONNECT FOR T1 If one of the timeslots is defined as voice and the CL
PORTS 17-28 module has no SDH/SONET ports, this cross-connect is
impossible for internal T1 ports 17 to 28 of the T3
module.
Viewing a T3 Port Status

Follow the instructions below for viewing the status of a T3 port.
 To view the T3 port status:

• At the config>port>t3(<slot>/<port>)# prompt, enter show status.
mp4100>config>port>t3(1/1)# show status
Name : IO-1 t3 01
Testing T3 Ports
The Megaplex-4 T3 ports feature local and remote loopbacks at the port level.
Table 6-15 shows the paths of the signals when each or loopback is activated.
Table 6-53. Loopbacks on T3 Ports
I/O CL
DS1
Port Cross-Connect
Local loopback on T3 port Interface
Matrix
"1 "
DS1
Port
Remote loopback on T3 port Interface
Cross-Connect
Matrix
Local Loopback on T3 Port

transmission through a selected T3 port: this path starts at the other
Megaplex-4 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.
Remote Loopback on T3 Port

T3 external port. This test also checks the transmission plant connecting the
As shown in Table 6-15, when a remote loopback is activated on a T3 port, that
Loopback Duration
 To perform a loopback on the T3 port:

1. Navigate to configure port t3 <slot>/<port> to select the T3 port to be
tested.
The config>port>t3>(<slot>/<port>)# prompt is displayed.

Activating and configuring loopback {local | remote} [duration local – local loopback
the direction of the <duration in minutes 1..30> ] remote – remote loopback
loopback and the duration
of it (in minutes)
Displaying the loopback show loopback

status
Displaying T3 Port Statistics

T3 ports of Megaplex-4 feature the collection of statistical diagnostics per
RFC-3896, allowing the carrier to monitor the transmission performance of the
links.
 To display the T3 port statistics:

• At the prompt config>slot>port>t3(<slot><port>)#, enter show statistics
Displaying statistics show statistics {total | all | all-intervals | current} • total - Total statistics of last 96
intervals
• all-intervals – Statistics for all
valid intervals
• current - Current statistics
• all – All statistics: first current
statistics

for a specific
interval
T3 port statistics are displayed. The counters are described in Table 6-54.
For example:
Current statistics:
mp4100>config>port>e1(1/2)# show statistics current
Current
---------------------------------------------------------------
Valid Intervals : 3
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 20
PCV : 0


mp4100>config>port>t3(2/1)# show statistics interval 4
Interval
---------------------------------------------------------------------
Interval Number : 4
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
All intervals:
mp4100>config>port>t3(2/1)# show statistics all-intervals
Interval
---------------------------------------------------------------------
Interval Number : 1
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
Interval
Interval Number : 2
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
Interval
Interval Number : 3
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
Total statistics:
mp4100>config>port>t3(2/1)# show statistics total

Total
-----------------------------------------------------------------
PES : 5 LES : 0
PSES : 5 CES : 5
SEFS : 5 CSES : 5
UAS : 1159
PCV : 0
All statistics:
mp4100>config>port>t3(2/1)# show statistics all
Current
----------------------------------------------------------------
Valid Intervals : 3
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
Interval
-----------------------------------------------------------------
Interval Number : 1
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 10 CSES : 0
UAS : 0
PCV : 0
Interval
-----------------------------------------------------------------
Interval Number : 2
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 21 CSES : 0
UAS : 0
PCV : 0
Interval
-----------------------------------------------------------------
Interval Number : 3

PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 0 CSES : 0
UAS : 0
PCV : 0
Total
---------------------------------------------------------------
PES : 0 LES : 0
PSES : 0 CES : 0
SEFS : 31 CSES : 0
UAS : 0
PCV : 0
Table 6-54. T3 Port Statistics Parameters
(Current statistics The range is 1 to 900 seconds
only)
(Current statistics displayed, in addition to the current (not finished) interval (up to 96)
only)
Interval number Number of interval for which statistics is displayed. Interval #1 is the earliest in time.
(Selected interval
and “all-intervals”
statistics only)
LES A Line Errored Second is a second in which one or more CV OR one or more LOS
defects occurred.
PES Displays the number of P-bit Error Seconds (PES) in the current interval. A Line error
Second is a second in which one or more PCV occurred OR one or more LOS defects.
PCV Displays the number of P-bit Coding Violations (PCV).

A P-bit Coding Violation or a P-bit Parity Error event is the occurrence of a received P-
bit code on the DS3 M-frame that is not identical to the corresponding locally-
calculated code.
Displays the namber of C-bit Errored Seconds (CES).

A CES is a second with one or more CCVs OR one or more Out of Frame defects OR
detected incoming AIS. This count is only for the SYNTRAN and C-bit Parity DS3
applications. This gauge is not incremented when UASs are counted.

PSES Displays the namber of P-bit Severely Errored Seconds (PSES)

A PSES is a second with 44 or more PCVs OR one or more Out of Frame defects OR
detected incoming AIS. This gauge is not incremented when UASs are counted.
CSES Displays the number of C-bit severely errored seconds (CSES) in the current interval.
A CSES is a second with 44 or more CCVs OR one or more Out of Frame defects OR
CSES Displays the number of C-bit severely errored seconds (CSES) in the current interval.
A CSES is a second with 44 or more CCVs OR one or more Out of Frame defects OR
SEFS Displays the number of Severely Errored Framing Seconds (SEFS)

A SEFS is a second with one or more Out of Frame defects OR detected incoming AIS.
This item is not incremented during unavailable seconds.
 To clear the statistics for a T3 port:

• At the prompt config>port>t3<slot>/<port>)#, enter clear-statistics.
Teleprotection Ports (Physical)
Applicable Modules
The TP module supports up to 4 command inputs and 8 outputs, enabling
teleprotection equipment to utilize the advanced transport capabilities offered by
Megaplex.
It also includes two independent groups of CMD channels:
• East – CMD channels 1 (working) and 2 (protection)
• West – CMD channels 3 (working) and 4 (protection).
The teleprotection commands can be locally output or be carried to a peer
card/Megaplex over a TDM/SDH network or over a packet-switched network. Up
to 4 commands can be carried over a single DS0.
See Alarm Relay Modules chapter in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
The Megaplex-4 is supplied with all teleprotection ports disabled. Other
parameter defaults are listed in the table below.

cmd-in
input-active Association between the cmd-in active state and the high
supplied voltage
preset-duration Extended cmd-in duration period (msec) 0
bounce-override Debounce filter window time (time during which the cmd- 1000
in signal is sampled, µsec)
switching-voltage Switching voltage 110
cmd-out
prolongation Minimum duration of pulse period (msec) 0
alarm-state-energized cmd-out alarm state indication yes
led-latched LED behavior when the related command turns inactive no led-latched
pulse-duration Maximum duration of pulse period (msec) 0
cmd-channel
rate Setting cmd-channel rate 64

(in kbps)
tx-address Tx address for recognizing and preventing wrong cross- 1

connect of teleprotection data in the network
rx-address Rx address for recognizing and preventing wrong cross- 2

connect of teleprotection data in the network
trigger-mode Teleprotection triggering mode speed-optimized
oos-recovery Mode of recovery from sending oos code and switching auto
back from the protection state
Configuring CMD-IN Ports
 To configure a cmd-in port:

1. Navigate to configure port cmd-in <slot>/<port> to select the cmd-in port to
configure.
The config>port>cmd-in>(<slot>/<port>)# prompt is displayed.
to port

port

Setting the debounce filter bounce-override <µsec > 0 to 32000 µsec, in 250-µsec steps
window time (time during For more information on bounce-override
which the cmd-in signal is command, see Teleprotection section in
sampled) Megaplex-4 I/O Modules Installation and
Operation Manual, Alarm Relay Modules
Chapter.
Setting the extended cmd-in preset-duration <msec> 0 to 2000 msec, in 1-msec steps
duration period For more information on preset-duration
command, see Teleprotection section in
Megaplex-4 I/O Modules Installation and
Operation Manual, Alarm Relay Modules
Chapter.
Defining the association input-active {high | low} • low – low voltage means that command
between the cmd-in active input is in active state
state and the supplied • high – high voltage means that
voltage command input is in active state
Defining LED behavior when led-latched • led-latched – the LED lights once the
the related command turns related command becomes active, and
inactive stays on even when the command is not
active, until explicit clear-cmd-led
command is issued by the user
• no led-latched – the LED follows the
related command activity
Clearing the led-latched clear-cmd-led See also Clear-Cmd-Led Command per

state System
Forcing the cmd-in port into force-active Using no force-active cancels the command
active state, disregarding
the actual input state
Selection of the switching switching-voltage

voltage {24 |48 |110 | 125 | 220 | 250}
Configuring CMD-OUT Ports

Cmd out ports 1 to 4 always serve as primary ports.
Cmd out ports 5 to 8 can either serve as secondary cmd-out ports or used to
report internal system alarms to outside indicators. In the first case they are
bound to the primary ports and automatically copy their configuration. In the
second case you have to bind them to the corresponding alarms under reporting
context by using bind-alarm-to-relay and bind-alarm-source-to-relay commands,
as described in Chapter 11.
 To configure the cmd-out port parameters:

1. Navigate to configure port cmd-out <slot>/<port> to select the port to
configure.

The config>port>cmd-out>(<slot>/<port>)# prompt is displayed.

to port

port
Setting minimum cmd-out prolongation <msec> If the received pulse period of cmd-out-i
signal duration (for very signal (received via cmd-channel) is shorter
short pulses) than this specific value, the cmd-out pulse
duration will be extended to this value.
Allowed values: 0 to 15000, with steps of
1 msec
If prolongation =0, the command is not
activated and the received pulse period is not
extended
When cmd-out is functioning as a binary
output port, this parameter does not appear.
Setting maximum cmd-out pulse-duration <msec> If the received pulse period of cmd-out-i
signal duration (for very signal (received via cmd-channel) is longer
long pulses) than this specific value, the cmd-out pulse
duration will be shortened to this value.
Allowed values: 0 to 15000, with steps of
1 msec
If pulse-duration=0, the command is not
activated and the received pulse period is not
shortened
When cmd-out is functioning as a binary
output port, this parameter does not appear.
Defining cmd-out alarm alarm-state-energized {yes | yes – alarm state is indicated by closed cicruit
state indication no} no – alarm state is indicated by open cicruit
Defines LED behavior when led-latched • led-latched – the LED lights once the
the related command turns related command becomes active, and
inactive stays on even when the command is not
active, until explicit clear-cmd-led
command is issued by the user.
• no led-latched – the LED follows the
related command activity.

Creating a set of ports that trigger-bind < number> cmd- See Command Cross-Connect in Megaplex-4
will be trigger sources for out-i <slot/port/tributary I/O Modules Installation and Operation
the current port [none | or | and] Manual, Alarm Relay Modules Chapter.
trigger-bind < number> cmd- Using no trigger-bind < number> removes the
in <slot/port> [none | or | set.
and] “none” is default operator and can be
omitted when only one trigger source is
defined.
When more than one trigger sources are
defined, the operator must be either “or” or
“and” for all trigger sources.
Binding a secondary cmd- secondary-bind <slot>/<port> Primary cmd-out ports: 1 to 4.

out port to a primary cmd- Secondary cmd-out ports: 5 to 8.
out port
One or more secondary ports can be bound
to one primary port.
A cmd-out port cannot be simultaneously
bound as Alarm Relay (see Chapter 11) and
bound as secondary cmd-out port to a
primary cmd-out port (the current command).
To view the command result, use “info detail”
command.
Clearing the led-latched clear-cmd-led See also Clear-Cmd-Led Command per System
state
Configuring CMD-CHANNEL Ports
 To configure the cmd-channel port parameters:

1. Navigate to configure port cmd-channel <slot>/<port> to select the port to
configure.
The config>port>cmd-channel>(<slot>/<port>)# prompt is displayed.
Setting cmd-channel rate rate {64 | 128}

(in kbps)
Configuring Tx address for tx-address The allowed values are 1 to 254.

recognizing and preventing wrong
cross-connect of teleprotection
data in the network

Configuring Rx address for rx-address The allowed values are 1 to 254.

recognizing and preventing wrong
cross-connect of teleprotection
data in the network
Stopping transmitting the oos code reactivate For oos-recovery=manual only
Controlling the mode of recovery oos-recovery {auto | • auto – when the OOS condition is over,
from sending oos code and manual} the cmd-in-i port automatically stops
switching back from the protection sending the oos code and switches back
state from the protection state
• manual – when the OOS condition is over,
the oos code continues to be sent and
the system remains in the protection
state until the user sends “reactivate”
command
Defining teleprotection triggering trigger-mode {speed- • speed-optimized – one frame is enough

mode optimized | security- to trigger command change
optimized} • security-optimized – in order to trigger
the command change, the value must be
stable for at least two frames (this adds
1.5 msec delay)
Clear-Cmd-Led Command per System

The clear-cmd-led command can be performed not only for a specific port, but
system-wide.
 To clear the Latched Led state system-wide:

The config>port># prompt is displayed.
2. Enter clear-cmd-led {all | cmd-in | cmd-out} for the required ports:
 cmd-in – all cmd-in ports
 cmd-out – all cmd-out ports
 all – all cmd-in and cmd-out ports.
The state is cleared for all the ports indicated in the command.
The tables below list messages generated by Megaplex-4 when a configuration
error on the Teleprotection module is detected.

Table 6-55. TP Configuration Error Messages
680 Error IDENTICAL TX/RX ADDRESSES The Tx&Rx addresses on a cmd channel cannot be
ARE ILLEGAL configured to the same value (with the exception of 254)
681 Error BOUND PORT IS IN One of the following ports is in shutdown state:
SHUTDOWN STATE • cmd-out-i or cmd-in port participating in trigger-bind
command
• cmd-out port participating in secondary-bind command
682 Error SECONDARY PORT IS BOUND A secondary cmd-out port can be bound to a primary cmd-
MORE THAN ONCE out port only once
684 Error ASSOCIATED CMD CHANNEL IS When a cmd-in-i and/or cmd-out-i port is in “no
IN SHUTDOWN STATE shutdown” state, its associated cmd-channel ports must
be also at “no shutdown”.
685 Error ILLEGAL LOGIC OPERATOR IN When more than one trigger sources are defined, the
TRIGGER-BIND operator must be either “or” or “and” for all trigger
sources.
686 Error ILLEGAL PORT TYPE USED IN For cmd-out and cmd-in-i ports, the associate trigger
TRIGGER BIND port can be either cmd-out-i or cmd-in.
687 Error ILLEGAL SECONDARY Primary and secondary cmd-out ports bound to each other
SLOT/PORT BOUND must reside in the same slot.
688 Error PULSE DURATION IS SHORTER Command prolongation must be shorter than pulse
THAN PROLONGATION duration.

For viewing the status of the physical Teleprotection ports, follow the
instructions below.
 To view the status of a cmd-in port:

1. Navigate to config>port> cmd-in> (<slot>/<port>)#
config port cmd-in 4/1 show status

Name : IO-4 Cmd in 01
Value : 1
Led : Latched
Force : Yes
Input Control Voltage : 220 VDC

 Value - Command value (0, 1, or N/A)

 Led – LED behavior when the related command turns inactive
(Latched/No Latched)
 Force – Whether the port is in force-active state (Yes/No)
 Input Control Voltage (24, 48, 110, 125, 220 or 250 VDC)
 To view the status of a cmd-out port:

1. Navigate to config>port> cmd-out> (<slot>/<port>)#
config port cmd-out 4/1 show status
Name : IO-4 Cmd out 01
Operation Status : Down
Value : 1
Led : Not Latched
Relay Type : Electro Mechanical
 Value – Command value (0, 1, or N/A)
 Led – LED behavior when the related command turns inactive
(Latched/No Latched)
 Relay Type (Electro Mechanical or Solid State). The value is identical for all
cmd-out ports and based on the card type.
 To view the status of a cmd-channel port:


config port cmd-channel 4/1 show status

Name : IO-4 CMD Channel 01
Operation Status : Down
Detail Status : No Sync
Rx Address : 0
Latency (millisec) : 2
Protection State : Active
CMD IN I Name Admin Oper Tx Val
4/1/1 IO-4 Cmd in-i 01 Up Up 0

CMD OUT I Name Admin Oper Loopback Rx Val
4/1/1 IO-4 Cmd out-i 01 Up Up No Loop 0

 Detail Status:
o Sync – port is synchronized
o No Sync –port is not synchronized
o Address mismatch – there is a mismatch between the Rx address and
the expected Tx address
o N/A – not relevant
 Rx Address –recieved Rx address
 Latency –cmd-channel data end-to-end latency
 Protection state for cmd-channels 1/2 and 3/4 (Active/Standby or N/A if
protection not defined)
 Cmd-in and cmd-out-i status (see Viewing Status Information of Logical
Teleprotection Ports for details)
Displaying Teleprotection Statistics

Teleprotection ports cmd-in, cmd-out and cmd-channel feature RAD proprietary
statistical diagnostics.
 To display the statistics of a cmd-in port:

1. Navigate to config>port> cmd-in> (<slot>/<port>)#

config port cmd-in 4/1 show statistics

Raw Debounced
Trip : 1 1
The statistics shows the number of trips occurred before (raw) and after
(debounced) debounce filtering.
 To display the statistics of a cmd-out port:

1. Navigate to config>port> cmd-out> (<slot>/<port>)#
The statistics (number of trips) is displayed, for example as follows:
config port cmd-out 4/1 show statistics
Trip Counter : 4
 To display the statistics of a cmd-channel port:

config port cmd-channel 4/1 show statistics
Frame Error : 2
CRC Error : 3
CMD IN I Trip Counter
4/1/1 0
4/1/2 0
4/1/3 0
4/1/4 0
CMD OUT I Trip Counter
4/1/1 0
4/1/2 0
4/1/3 0
4/1/4 0
Table 6-56. TP Statistics Parameters
Frame Error Number of frame errors received on the cmd channel since last reset or power-up
CRC Error Number of CRC errors received on the cmd channel since last reset or power-up
A CRC error is declared when the CRC bits generated locally on the data in the received
frame (protecting critical teleprotection bits) do not match the CRC bits (crc1 – crc4)
received from the transmitter.

Clearing Statistics
 To clear the statistics on a TP port:

Voice Ports
Applicable Modules
Voice ports are available on the following modules:
• VC-4, VC-8 and VC-16
• VC-4A, VC-8A
• VC-4/OMNI
• VC-6/LB
• VS voice modules
• VS voice modules (VS-6/FXS, VS-6/FXO, VS-6/E&M and FXS/E&M).
The following table shows the number of voice ports on each Megaplex-4 I/O
module.
Table 6-57. Megaplex-4 Voice Ports
Module Number of Ports
VC-4/OMNI 4
VC-4A/8A 4/8
VC-4/8/16 4/8/16
VC-6/LB 6
VS-6/FXS 8
VS-6/FXO 8
VS-6/E&M 4
FXS/E&M 8(FXS)+4(E&M)
Analog voice interface modules, VC-4, VC-8 and VC-16, provide 4, 8 or 16

PCM-encoded toll-quality voice channels (ports). The modules are available in
three models:
• E&M: 4-wire or 2-wire interfaces with E&M signaling per RS-464 Types I, II, III
and V, and BT SSDC5.
• FXS: 2-wire interfaces for direct connection to telephone sets.
• FXO: 2-wire interfaces for direct connection to PBX extension lines

VC-4A and VC-8A modules are analog voice interface module similar to VC-4 and
VC-8, except that they also support ADPCM.
The VC-6/LB module is used for connection of local battery-powered (LB)
telephones. It provides 6 voice channels using toll-quality 64 kbps PCM voice
encoding in compliance with ITU-T Rec. G.711 and AT&T Pub. 43801.
A special ”omnibus“ VC-4/OMNI module provides four toll-quality voice channels
for applications where a master site needs to communicate with multiple remote
stations simultaneously (such as to broadcast an important message).
The VS voice modules (VS-6/FXS, VS-6/FXO, VS-6/E&M and FXS/E&M) provide
8 FXS, 8 FXO or 4 E&M toll-quality analog voice channels.
The following parameters can be configured for the voice ports:
• Port name
• End-to-end signaling transfer method
• Pulse metering frequency for FXO/FXS channels (VC modules only)
• Number of wires for E&M channels
• Specifying the compression method used in the ADPCM encoding.
• Analog signaling method for FXO/FXS channels
• Analog signaling profile (VS voice modules only)
• E&M signaling standard
• Energy recognition engine status for E&M channels (VS voice modules only)
• Impedance for FXS and FXO modules (VS voice modules only)
• Cadence for FXS and FXO modules (VS voice modules only)
Standards
The Megaplex-4 voice ports comply with following standards:
Modulation Technique PCM: per ITU-T Rec. G.711 and AT&T Pub. 43801
ADPCM: per ITU-T G.726 and G.727
Echo Cancellation ITU-T G.168
Analog Interface ITU-T Rec. G.712
E&M Signaling Method EIA RS-464 Type I

EIA RS-464 Type II, III and V (British Telecom SSDC5)
using internal -12 VDC in place of -48 VDC
FXS/FXO Signaling Modes EIA RS-464 loop-start and wink-start
End-to-End Signaling for User-selectable as per ITU-T Rec. G.704, para. 3.3.32
E1 Uplinks

All the VC/VS voice modules provide high-quality voice channels. The functional
difference between the various modules is in the signaling interface and mode.
The analog interface depends on the module type:
• VC-4/4A/8/8A/16 E&M modules: user-selectable for 2-wire or 4-wire
• VC-4/4A/8/8A/16 FXS/FXO and VC-6/LB modules: always 2-wire
• VC-4/OMNI modules: always 4-wire
• VS-6/E&M, FXS/E&M E&M submodules: user-selectable for 2-wire or 4-wire
• VS-6/FXS, VS-6/FXO, FXS/E&M FXS/FXO submodules: always 2-wire
Voice encoding method for all VC-4A and VC-8A module versions is
user-selectable for either toll-quality 64 kbps PCM or 32/24 kbps ADPCM. The
VC-4, VC-8, VC-16, VS-6/E&M, FXS/E&M, VS-6/FXS, and VS-6/FXO modules
feature only PCM encoding.
The user can select the companding law, µ-law or A-law, in accordance with
system requirements. In accordance with ITU-T Rec. G.711, the A-law should be
used on E1 trunks and the µ-law should be used on T1 trunks. However, the user
can select the desired companding law, µ-law or A-law, in accordance with the
specific system requirements.
To increase application flexibility, the nominal audio transmit and receive levels of
all the module versions can be adjusted over a wide range (see Table 6-58).
Table 6-58. Transmit and Receive Levels for Various Interfaces
Module Interface Transmit Receive

[dbm] [dbm]
min max min max
VC modules
E&M regular -10 +5 -17 +2
E&M 4W enhanced -17 +5 -17 +9
FXS -5 +5 -17 +1
LB -17 +8 -23 +2
FXO -3.5 +5 -17 +1
VS voice modules
E&M 2/4 wire mixed -8 +5 -17 +2
E&M 4 wire only -17 +5 -17 +9
FXS/FXO -5 +5 -17 +1
Due to the high quality audio reproduction, DTMF signaling is transparently

transferred, inband. Therefore, the user can use DTMF signaling as usual, e.g.,
can operate the telephone set keypad to access voice mail systems, interactive
systems, etc.

The VC-4A and VC-8A modules use G.168 standard for echo cancellation (up to
4 ms per channel).
For VS voice modules, pulse metering frequency is not supported.
For more information, see also the following sections in the Megaplex-4 I/O
Modules Installation and Operation Manual:
• VC-4/VC-4A/VC-8/VC-8A/VC-16, VC-6/LB and VC-4/OMNI sections in Voice
Modules chapter
• VS Voice section in Versatile Modules chapter.
Factory Defaults
Megaplex-4 is supplied with all voice ports disabled. Other parameter defaults are
coding a-law
no signaling (disabled)
Note: this default value is not used in the
signaling VC-6/LB module and must be changed to one of
the other options, as explained in the
configuration section.
analog-signaling-profile sig_over_a_bit
meter-rate 12khz
wires 2
compression no compression (disabled)
analog-signaling loop-start
e-m-type ssdc5
echo-canceler no echo-canceler (disabled)
operation-mode ptp
signaling-feedback no signaling-feedback (disabled)
tx-gain 0 dbm
rx-sensitivity 0 dbm
impedance 600
cadence local
loop-disconnect-time 250msec
forward-disconnect 250msec
energy-detection no energy-detection (disabled)
duration infinite
omni-signaling legacy

disconnect-tone no disconnect-tone (disabled)
ring-voltage normal
Configuring External Voice Port Parameters

The sets of configurable parameters are different for voice ports of VC modules
and VS voice modules.
 To configure the external voice port parameters for VC modules:

1. Navigate to configure port voice <slot>/<port> to select the voice port to
configure.
The config>port>voice>(<slot>/<port>)# prompt is displayed.
For VC modules:
Assigning short name <string> Using no before name removes the name
description to port

port
Specifying the coding {a-law | u-law} a-law - A-law coding, intended for use on
companding law to be E1 links
used by the voice u-law -µ-law coding, intended for use on T1
channels links

Specifying the signaling {rbmf | cas | rbf} This command is relevant for
end-to-end signaling VC-4/4A/8/8A/16 and VC-6/LB modules. For
transfer method for voice VC-4/OMNI modules, see omni-signaling
modules command.
The signaling transfer options depend on
the type of link module installed in the
Megaplex chassis:
• with T1 link modules, RBMF and RBF is
used
• with E1 link modules, CAS and RBF is
used
rbf – proprietary “robbed bit” signaling
method that does not require multiframe
synchronization, used as follows:
• 7-bit PCM with channel signaling carried
by the 8th bit of each channel
• 3-bit ADPCM with channel signaling
carried by the 4th bit of each channel
when using G.727
This option is used for VC-4A/VC-8A and
VC-6/LB modules only.
rbmf – robbed bit signaling in accordance
with AT&T Pub 43801.
cas – Channel-associated signaling in
accordance with ITU-T Rec. G.704.
Using no signaling means that channel
signaling is not transferred (not used in the
VC-6/LB module)
Specifying the omni-signaling {legacy | abcd} legacy The channel uses legacy signaling
end-to-end signaling (used by the uplink port connected
transfer method for to this channel)
VC-4/OMNI modules abcd The channel uses RAD proprietary
signaling for VC-4/OMNI modules
Using no omni-signaling means that channel
signaling is not transferred
Specifying the pulse meter-rate { 16khz | 12khz } This feature is supported only on FXS and
metering frequency FXO modules in PCM mode
Specifying the interface wires {2 | 4} Selection between 2-wire and 4-wire

to be used by the voice interface is available only for the
channels VC-4/4A/8/8A/16 E&M modules. Can be
independently selected for each pair of
channels (1, 2; 3, 4; etc.).

Specifying the compression {g726 | g727} Always use G.727 when working with RBF or
compression method RBMF signaling.
used in the ADPCM If PCM encoding is used, a sanity error is
encoding sent.
Using no compression disables compression
Specifying the analog analog-signaling {loop-start | wink-start} Can be selected only for FXO and FXS
signaling method used modules operated in PCM mode.
for all FXO/FXS channels For VC-4, VC-4A, VC-8 and VC-8A modules,
the selection is made for the entire group
of all the module channels. For VC-16
modules, the selection can be separately
made for each group of eight channels: 1 to
8 and 9 to 16.
Specifying the E&M e-m-type {1 | 2 | 3 | ssdc5} This selection is available only for E&M
signaling standard modules. The E&M signaling type can be
independently selected for each group of
four channels 1, 2, 3, 4; 5, 6, 7, 8; etc.).
Note: For the E&M/POS module, select 2
only.
Enabling the built-in echo-canceler This option is relevant only for VC-4A and
adaptive echo canceller, VC-8A modules.
supporting up to a 4 Using no before echo-canceler disables
msec delay echo canceling
Setting the operating operation-mode {ptp | omni-bus | This parameter is valid only for
mode of the channel for p2mp-dst | p2mp-src} VC-4/OMNI modules:
VC-4/OMNI modules • omni-bus – The channel is operated in
an “omnibus” (conference call)
application.
• ptp – The channel is operated as a
regular E&M voice channel.
• p2mp-dst –The channel is operated as a
destination (remote station) in a point-
to-multipoint application
• p2mp-src –The channel is operated as a
source (master) in a point-to-multipoint
application.

Controlling the use of signaling-feedback Available only for FXO modules.

signaling feedback for For VC-4, VC-4A, VC-8 and VC-8A, the
FXO modules selection should be the same for all the
module channels. For VC-16 modules, the
selection can be separately made for each
group of eight channels: 1 to 8 and 9 to 16.
This is done by forcing the last choice
(signaling-feedback/no signaling-feedback)
to all the module/group ports.
Using no before signaling-feedback disables
the signaling feedback.
Selecting the nominal tx-gain <value in dbm> The input level can be set in 0.5 dB steps in
input level of the the range of +8 dBm to -17 dBm, depending
transmit path on the module type (see Table 6-58).
Selects the nominal rx-sensitivity <value in dbm> The output level can be set in 0.5 dB steps
output level of the in the range of +9 dBm to -23 dBm,
receive path depending on the module type (see
Table 6-58).
Enabling the “end of disconnect-tone FXS modules only

speech” signal (short Using “no disconnect-tone” disables the
tones) on hanging up on tone
the partner side
 To configure the external voice port parameters for VS voice module:

configure.
description to port

port
Specifying the coding {a-law | u-law} a-law - A-law coding, intended for use on
companding law to be E1 links
used by the voice u-law -µ-law coding, intended for use on T1
channels links

Specifying the signaling {rbmf | cas | rbf} The signaling transfer options depend on
end-to-end signaling the type of link module installed in the
transfer method for voice Megaplex chassis:
modules • with T1 link modules, RBMF and RBF is
used
• with E1 link modules, CAS and RBF is
used
RBF is a proprietary “robbed bit” signaling
method that does not require multiframe
synchronization, it is supported by E&M
module only.
Using no signaling means that channel
signaling is not transferred
Activating the energy energy-detection Selection of the energy- recognition is

recognition engine available only for the E&M modules.
Using no energy-recognition means that
energy-recognition is not active.
Specifying the interface wires {2 | 4} Selection between 2-wire and 4-wire

to be used by the voice interface is available only for the E&M
channels modules.
Can be independently selected for each
channel.
Specifying the analog analog-signaling {loop-start | wink-start} Can be selected only for FXO and FXS
signaling method used modules.
for all FXO/FXS channels
Specifying the E&M e-m-type {1 | 2 | 3 | ssdc5 | positive} This selection is available only for E&M
signaling standard modules.
The E&M signaling type can be
independently selected for each group of
four channels 1, 2, 3, 4; 5, 6, 7, 8; etc.)
Controlling the use of signaling-feedback This parameter is available only for FXO
signaling feedback for modules and is needed when FXO is working
FXO modules opposite E&M interface.
Using no before signaling-feedback disables
the signaling feedback.
Selecting the nominal tx-gain <value in dbm> The input level can be set in 0.5 dB steps in
input level of the the range of +5 dBm to -17 dBm, depending
transmit path on the module type (see Table 6-58).
Selects the nominal rx-sensitivity <value in dbm> The input level can be set in 0.5 dB steps in
output level of the the range of +9 dBm to -17 dBm, depending
receive path on the module type (see Table 6-58).
Specifying the analog analog-signaling-profile <profile-name> By default the analog signaling profile shall
signaling profile be sig_over_a_bit

Specifying the line impedance {600 | 900} Available only for FXS/FXO modules
impedance
Specifying if the cadence cadence {local | transparent} Available only for FXS/FXO modules
of the ring is generated
locally or translated
directly from the received
signaling bit
Specifying the amount of forward-disconnect {250msec | 500msec | Available only for FXS modules
time during which the 750msec | 1sec | 2sec}
battery voltage is
disconnected by the FXS
port after a far-end
notification has been
received
Specifying the amount of loop-disconnect-time {250msec | 500msec Avaliable only for FXO modules
time of momentary | 750msec | 1sec | 2sec}
battery voltage removal
that will be detected by
the FXO port
Specifying the ring ring-voltage {normal | high} Available only for FXS ports:
voltage value • normal – 54 Vrms
• high – 85 Vrms
For each pair of channels (1-2, 3-4, 5-6 or
7-8) only one channel can be set to 'high'.
Example
The following section illustrates how to configure the voice FXS port 1 on the
VC-8 module installed in slot 9:
• Set -µ-law coding
• Set CAS signaling
• Administratively enable the port
mp4100>config# #----------vc8fxs-----------------
mp4100>config# port voice 9/1 no shutdown
mp4100>config# port voice 9/1 coding a-law
mp4100>config# port voice 9/1 signaling cas
Configuring Internal Voice Port Parameters
 To configure the internal voice port parameters (VC-4/OMNI only):

1. Navigate to configure port voice <slot>/<port>/<tributary> to select the
internal voice port to configure.

The config>port>voice>(<slot>/<port>/<tributary>)# prompt is displayed.

Assigning short description to port name <string> Using no before name removes the name
Specifying the end-to-end signaling omni-signaling {legacy | abcd} Using no before omni-signaling means that
transfer method for VC-4/OMNI channel signaling is not transferred
modules
Table 6-59 and Table 6-60 list messages generated by Megaplex-4 when a
configuration error on voice modules is detected.
Table 6-59. VC and VS Voice Modules Configuration Error Messages
170 Error ILLEGAL SIGNALING METHOD You can select the channel associated signaling method
only when an E1 module port with G.732S framing is used.
You can select the robbed bit multiframe signaling transfer
method only for E1 links with G.732S framing, or on T1
links.
171 Warning VOICE CODING LAW (E1/T1) The selected voice companding law differs from the
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
172 Error TX GAIN VALUE OUT OF RANGE The transmit gain selected for the specified channel is not
within the supported range
173 Error RX SENSITIVITY VALUE OUT OF The receive sensitivity (gain) selected for the specified
RANGE channel is not within the supported range
174 Error OOS/INTERFACE MISMATCH The selected OOS mode cannot be used on this type of
interface
175 Error SIGNALING PROFILE/INTERFACE The selected profile cannot be used on this type of
MISMATCH interface
176 Error ILLEGAL NUMBER OF WIRES Voice modules with /FXO and /FXS interfaces support only
the two-wire interface.
For voice modules with /E&M interface only, it is possible
to select two-wire or four-wire interfaces. In addition, for
VC-4/4A/8A/16 modules with /E&M interface, the same
interface type must be selected for consecutive pairs of
channels (for example, 1, 2 or 15, 16)
177 Error NO SIGNALING IS ILLEGAL FOR The selected interface cannot be used with no signaling –
THIS INTERFACE the signaling option must be specified

179 Error ILLEGAL ANALOG SIG For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of
COMBINATION analog-signaling parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
180 Error ILLEGAL FXO SIG FEEDBACK For VC-4, VC-4A, VC-8 and VC-8A modules, the selection of
COMBINATION signaling-feedback parameter must be made for the entire
group of all the module channels. For VC-16 modules, the
selection can be separately made for each group of eight
channels: 1 to 8 and 9 to 16.
181 Error ILLEGAL TS SPLIT CONFIG FOR Split timeslot cross-connect must be peformed on a pair
ADPCM MODE of ports (1,2 or 3,4..)
182 Error TX/RX GAIN LEVEL MUST BE Step value is not legal for VS voice modules.
SET IN 0.5 dB STEPS
750 Error NUM OF BI-DIRECTION-RX TS The number of bidirection-rx timeslots cross-connected to

EXCEEDS 30 the voice port in VS voice modules cannot exceed 30.
762 Error NO SIGNALING / ENERGY When energy recognition is active in VS voice modules,
RECOGNITION MISMATCH “no signaling” is illegal.
763 Error SERIAL PORT/PW BANDWIDTH In VS modules, the serial port rate must match the number
MISMATCH of timeslots on this serial port listed in the cross-connect
pw-tdm command.
764 Error ILLEGAL RING VOLTAGE/PORTS For each pair of channels (1-2, 3-4, 5-6 or 7-8) only one
ADMIN COMBINATION channel can be set to 'high' ring voltage.
Table 6-60. VC-4/OMNI Configuration Error Messages
241 Error ONLY FIRST TRIBUTARY CAN If operation-mode is ptp, only the first tributary channel
BE CONNECTED of this voice port can be connected. All the other tributary
channels must be set to shutdown.
242 Error FIRST TRIBITURY MUST BE If the operation-mode is p2mp-dst, and the first internal
CONNECTED channel is not connected, the other internals cannot be
connected and cannot carry traffic.
Viewing a Voice Port Status

Follow the instructions below for viewing the status of a voice port.
 To view the voice port status:

• At the config>port>voice(<slot>/<port>/<tributary>)# prompt, enter show
status.

Note <tributary> relates to VC-4/OMNI modules only.
mp4100>config>port>voice(3/1)# show status

Name : IO-3 voice 01
Testing Voice Ports

The test and diagnostics functions available on each voice channel are:
• Forward tone injection
• Backward tone injection.
Note VC-6/LB modules support only forward tone injection.

Megaplex unit.
While the loopback is connected, the local voice channel should receive its own
signal, e.g., a strong sidetone should be heard in the earpiece if the channel is
connected to a telephone set.
The loopback signal path is shown in Figure 6-26.
Channel 1 ..
.. .. ..
... . ..
. .. .
User or ..
Test .
Equipment
User or
VC-16 VC-16 Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management

Note When working in the ADPCM mode, the local digital loopback towards the local
user equipment is performed for each pair of consecutive channels (1-2, 3-4,
etc.)

received by user.
While the loopback is connected, the remote voice channel should receive its own
signal, e.g., a strong sidetone should be heard in the earpiece if the channel is
connected to a telephone set.
The loopback signal path is shown in Figure 6-27.
Channel 1 ..
.. ..
.. . ..
.. .. ..
User or . .. .
Test .
Equipment
User or
VC-16 VC-16 Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management
Forward Tone Injection

The test tone is a data sequence repeating at a rate of 1 kHz. This data sequence
is identical to the data sequence that would have been generated if a 1-kHz
signal having a nominal level of 1 mW (0 dBm0) were applied to the input of the
channel codec.
The tone is injected to the local transmit path multiplexer, instead of the transmit
signal of the channel. The signal received from the other end remains connected
to the local subscriber.

While the forward tone injection is activated, the remote user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 6-28 shows the signal path.
Channel 1 ..
.. ..
.. . ..
.. .. ..
User or . .. .
Test .
Equipment
Test
~ Tone
User or
VC-16 VC-16 Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management
Figure 6-28. Forward Test Tone Injection Path
Backward Tone Injection

When the backward test tone injection is enabled, the test tone (a data sequence
repeating at a rate of 1 kHz) is injected to the local receive input of the channel
decoder, instead of the received signal of the channel, and the resulting analog
signal is supplied to the local subscriber. The signal received from the other end is
disconnected from the local subscriber.
While the backward tone injection is activated, the local user should hear the
tone in the earpiece if the channel is connected to a telephone set.
Figure 6-29 shows the signal path.

Channel 1 ..
.. ..
.. . ..
.. .. ..
User or . .. .
Test .
Equipment
Test
Tone
User or
VC-16 VC-16 Test
Equipment
I/O Modules
I/O Modules
Local Remote
Unit Unit
System
Management
Figure 6-29. Backward Test Tone Injection Path
Loopback Duration
Activating Loopbacks and Tone-Inject Tests
 To perform a loopback on the voice port:

configure.

Activating and loopback {local | remote} [tone-inject] local – local loopback

configuring the [duration <duration in minutes 1..30> ] remote – remote loopback
direction of the
local tone-inject – backward tone
loopback and the
injection (not for VC-6/LB modules)
duration of it (in
seconds) remote tone-inject – forward tone
injection
6.4 Logical Ports
BRI Ports
Applicable Modules
The following table shows the number of BRI ports on the HSU-6, HSU-12 and
HS-S I/O modules.
Table 6-61. BRI Ports
HSU-6, HSU-12 ISDN “U” 6/12
HS-S ISDN “S” 4
The following parameters can be configured for the BRI ports:

• Port name
• Number of bits that must be allocated to each internal port (B-channel)
Standards
The BRI ports comply with the ANSI T1.601 and ITU-T Rec. G.961 standards.
See the corresponding module section in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all BRI ports disabled. Other parameter defaults are
Megaplex-4 Logical Ports 6-219

rate-bits 2
Configuring a BRI (ISDN) Port
 To configure the BRI port parameters:

1. Navigate to configure port bri <slot>/<port>[tributary] to select the BRI port
to configure:
 To configure Channel B1, use configure port bri <slot>/<port>/1
 To configure Channel B2, use configure port bri <slot>/<port>/2
 To configure Channel D, use configure port bri <slot>/<port>
The config>port>bri>(<slot>/<port>/[tributary>]# prompt is displayed.
to port

port
Specifying the number of rate-bits {2 | 4 | 8} The data rates supported by each

bits that must be allocated B-channel are as follows:
to each internal port 2 Used for payload data rates up to 16
(B-channel), in accordance kbps.
with the payload data rate
4 Used for payload data rates up to 32
kbps.
8 Used for payload data rates up to 64
kbps.
For the D-Channel rate-bits is constantly
set to 2 (16 kbps).
Example
The following section illustrates how to configure the bri ports 3 and 4 (B1, B2
and D-channels) on the HS-U-6 module installed in slot 5:
• Data rate 8 kbps on each B-channel (total 32 kbps).
• Data rate 2 kbps on each D-channel (total 4 kbps).
• Administratively enable the ports.
6-220 Logical Ports Megaplex-4

------------hs-U6----------------
mp4100>config# port bri 5/3/1 no shutdown

mp4100>config# port bri 5/3/1 rate-bits 8
mp4100>config#
mp4100>config# #------------d-channel------
mp4100>config# port bri 5/3 no shutdown
mp4100>config# port bri 5/3 rate-bits 2
mp4100>config#
mp4100>config# port bri 5/4 no shutdown
mp4100>config# port bri 5/4 rate-bits 2
DS1 Ports
Applicable Modules
The following table shows the number of ds1 ports and the features supported
by each Megaplex-4 module.
mpw-1 vs-12 vs-6-fxs vs-fxs-em tp vs-6-e1t1

Feature/
vs-6-bin vs-6-fxo vs-e1-t1-pw
Command
vs-6-c37 vs-6-em sh16-e1-pw
Number of 8 12 12 8 4 16
ports
name √ √ √ √ √ √
shutdown √ √ √ √ √ √
signaling √ - √ √ - -
line-type √ - - - - √
Idle-code - - - - - √
vc-profile - - - - - √
The internal DS1 ports are logical ports that provide the linkage between the
packet processing subsystem and the TDM subsystem:
• On the TDM side, a DS1 port serves as an endpoint for traffic from the TDM
and signaling buses. Each I/O or E1-i/T1-i port in the Megaplex-4 that will use
pseudowires on a PW module must be assigned bandwidth (timeslots) on the
internal DS1 port, using the standard Megaplex-4 timeslot assignment
procedures.

• On the pseudowire side, a DS1 port serves as the collection point for
timeslots to be carried by each pseudowire. Thus, to carry traffic from a
specific TDM port by means of a pseudowire, it is necessary to assign the
same timeslots on the TDM side and on the pseudowire side. The pseudowire
timeslot assignment is made as part of the pseudowire configuration
procedure, and it determines the cross-connect operations performed by the
pseudowire cross-connect matrix (see Configuring a PW-TDM Cross
Connection in Chapter 8).
When using the PW-equipped modules, the user can independently configure
each internal DS1 port in accordance with the table above.
Factory Defaults
Megaplex-4 is supplied with all DS1 ports disabled. Other parameter defaults are
line-type SH-16/E1/PW, VS-16E1T1-PW, VS-6/E1T1: g732s

Other modules: framed
signaling disabled
tx-clock-source domain 1
idle-code 0x7f
vc profile tug-structure
Configuring Internal DS1 Port Parameters
 To configure the internal DS1 port parameters:

1. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to configure.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
description to port

port
Specifying the code idle-code <00 to FF (hexa)> Specifying the code transmitted to fill
transmitted to fill unused unused timeslots
timeslots This field is valid for SH-16/E1/PW,
VS-6/E1T1 and VS-E1T1/PW modules only.

Specifying the framing This field is valid for MPW-1 only.

mode of the internal DS1 line-type {unframed | framed} Make sure to select the same value at both
port (MPW-1 module) end points.
These options are valid for the following

card types:
Specifying the framing
mode of the internal DS1 • vs-e1-pw
line-type {unframed | g732n | g732n-crc |
port for SH-16/E1/PW, • vs-6-e1.
g732s | g732s-crc}
VS-6/E1T1 and VS- • sh16-e1-pw.
E1T1/PW modules
Make sure to select the same value at both
end points.
These options are valid for the following

card types:
Specifying the framing
mode of the internal DS1 • vs-t1-pw
line-type {unframed | esf | sf}
port for VS-6/E1T1 and • vs-6-t1.
VS-E1T1/PW modules Make sure to select the same value at both
end points.
This field is valid for MPW-1 and VS voice

Enabling transmitting an
only.
out-of-service signal signaling
no signaling disables transmitting an OOS
(OOS) on PW failure
signal
Assigning VC profile to vc profile <profile name> Relevant for SH-16/E1/PW, VS-16E1T1-PW

the port and VS-6/E1T1 modules.
For creating VC profiles, see VC Profiles.
Using no vc removes the profile.
Example
The following section illustrates how to configure the internal DS1 port 1 on the
MPW-1 module installed in slot 9:
• Set the line type to unframed.
mp4100>config>port>ds1(9/1)# line-type unframed
mp4100>config>port>ds1(9/1)# no shutdown
Viewing DS1 Port Status

Follow the instructions below for viewing the status of an internal DS1 port.
 To view the DS1 port status:

• At the config>port>ds1(<slot>/<port>)# prompt, enter show status.

mp4100>config>port>ds1(4/2)# show status

Name : IO-4 Ds1 02
Testing DS1 Ports

The DS1 ports feature test and loopback functions at the timeslot level.
Local Loopback on Selected DS1 Port Timeslots

The local loopback on timeslots of an DS1 port is used to return the transmit
payload carried by selected timeslots of the tested port through the same
timeslots of the receive path. The timeslots looped back remain connected to the
transmit path of the port, but the corresponding timeslots received from the
remote end are disconnected.
This test is recommended for testing signal paths between the I/O port of the
other local module which uses the pseudowire, and the MPW-1/VS port.
The loopback is activated within the CL module routing matrix, and only on the
timeslots specified by the user during the activation of the loopback. As a result,
there is no disturbance to services provided by means of the other timeslots
(pseudowires) of the same port: only the flow of payload carried by the specified
timeslots is disrupted.
The signal paths for a local loopback on timeslots are shown in Figure 6-30 on an
MPW-1 example.
arbitrarily selected timeslots.
When the loopback is activated on timeslots of a port which is part of a
redundancy pair, the CL module automatically activates the loopback on the same
timeslots of the other port of the pair. The same is true for timeslots assigned to
the same pseudowire.
This convenience feature is also available for loopback deactivation: the
deactivation command can be issued to either one of the ports of the
redundancy pair (even if it has been activated by a command to the other port).

Int DS1 Port n

TS n
Megaplex-4100
MPW-1 Module
CL MPW-1
Int DS1 Port 1
TS n
.. .. Pseudowire
TDM Cross-
Other Routing Bus .. ..
Connect
Cross- Packet Ethernet To PSN
Ports Matrix Interface Connect Processor Switch
. ..
Matrix
Matrix
.
Int DS1 Port 8
Figure 6-30. Local Loopback on Selected Internal DS1 Port Timeslots, Signal Paths
Remote Loopback on Selected Internal DS1 Port Timeslots

The signal paths for a remote loopback on timeslots are shown in Figure 6-31 on
an MPW-1 example.
Int DS1 Port n

TS n
Megaplex-4100
MPW-1 Module
CL MPW-1
Int DS1 Port 1
TS n
.. .. Pseudowire
TDM Cross-
Other Routing Bus .. ..
Connect
Cross- Packet Ethernet To PSN
Ports Matrix Interface Connect Processor Switch
. ..
Matrix
Matrix
.
Int DS1 Port 8
Figure 6-31. Remote Loopback on Selected Internal DS1 Port Timeslots, Signal Paths

The remote loopback on timeslots of an MPW-1/VS DS1 port is used to return the
receive payload carried by selected timeslots of the tested port through the same
timeslots of the transmit path. The corresponding timeslots received from the
local equipment are disconnected.
through a selected pseudowire served by the corresponding MPW-1 port.
The loopback is activated within the CL module routing matrix, and only on the
timeslots specified by the user during the activation of the loopback. As a result,
there is no disturbance to services provided by means of the other timeslots
(pseudowires) of the same port: only the flow of payload carried by the specified
timeslots is disrupted.
Loopback Duration
by the MPW-1/VS modules. Therefore, when you initiate a loopback, you have the
option to limit its duration to a selectable interval in the range of 1 through 30
minutes.
 To perform a loopback on the internal DS1 port:

1. Navigate to configure port ds1 <slot>/<port> to select the internal DS1 port
to be tested.
The config>port>ds1>(<slot>/<port>)# prompt is displayed.
Activating and configuring loopback {local | remote} time-slot local – local loopback
the direction of the <1..31>] [duration <duration in remote – remote loopback
loopback and the duration minutes 1..30> ]
of it (in minutes)
E1-i, T1-i Ports

See E1 Ports and T1 Ports sections, respectively.

GFP Ports
Applicable Modules
GFP ports represent VCGs (Virtual Concatenation Groups) with GFP encapsulation
and can be configured for the following ports:
• SDH/SONET (CL.2 modules)
• E1/T1 (VS-16E1T1-EoP modules)
• T3 (T3 modules).
They can be mapped either directly to the physical layer or to VCG. In the latter
case, the binding is done in two stages and the VCG is further bound to the
physical layer.
Standards
GFP Ports comply with ITU-T Rec. G.7041, using the framed mode.
Factory Defaults
Megaplex-4 is supplied with all GFP ports disabled.
Configuring GFP Ports
 To configure a GFP port:

1. Navigate to configure port gfp <slot>/<port> to select the gfp port to
configure.
The config>port>gfp>(<slot>/<port>)# prompt is displayed.

`
port
Binding the corresponding bind vc4-sts3c For the allowed ranges, seeTable 6-66.
VC/VT/STS-1/VCG to the GFP port <slot>/<port>/<tributary> The connection to a VC or VT/STS
(CL modules) bind vc3-sts1 depends on the frame selection
<slot>/<port>/<au4>/ (frame=sdh or frame=sonet)
<tributary>
You cannot bind both a VCG and a
bind vc-vt <slot>/<port>/
VC/VT/STS-1 to a GFP port
<au4>/<tug_3>/<tug_2>
[/<tributary>] Using no before the corresponding
command removes the binding
bind vcg <slot>/<port>


`
Binding the corresponding bind t3 <slot>/<1> The allowed ranges of VCG ports is 1 to
T3/VCG to the GFP port (T3 bind vcg <slot>/<port> 16 paer slot.
modules) Using no before the corresponding
Binding the corresponding VCG bind vcg <slot>/<port> The allowed ranges of VCG ports is 1 to
to the GFP port (VS-16E1T1-EoP 16 per slot.
modules) Using no before the corresponding
Enabling payload error detection: fcs-payload Using no fcs-payload disables payload

in this case, a frame checksum is error detection
calculated, using the 32-bit
polynomial recommended by
ITU-T, and added to the GFP
frame structure
Enabling the use of payload data scrambler-payload { rx | tx | Using no scrambler-payload disables

scrambling in the transmit and rx-tx } payload scrambling for both the transmit
receive directions, before and receive directions
insertion in frames
to remove the automatical lvc-eos or
hvc-gfp profile assignement
Displaying GFP Statistics

GFP ports feature the collection of statistical diagnostics.
 To display the GFP port statistics:

• At the prompt config>slot>port>gfp (<slot><port>)#, enter show statistics
followed by parameters listed below.
statistics


GFP statistics are displayed. The counters are described in Table 6-62.
For example:
Current Statistics:
mp4100>config>port>gfp(cl-b/6)# show statistics current
Current
---------------------------------------------------------------
Valid Intervals : 96
Total RX Frames : 475682
Idle Frames Error : 237726
cHEC Errors : 0
tHEC Errros : 0
eHEC Errors : 0
FCS Errors : 0
PTI Mismatch : 0
EXI Mismatch : 0
mp4100>config>port>gfp(cl-a/1)# show statistics interval 67
Interval
---------------------------------------------------------------
Idle Frames Error : 0
cHEC Errors : 0
tHEC Errros : 0
eHEC Errors : 0
FCS Errors : 0
PTI Mismatch : 0
EXI Mismatch : 0
Table 6-62. GFP Statistics Parameters
Time elapsed (Current The elapsed time (in seconds) since the beginning of the current interval, in
statistics only) seconds. The range is 1 to 900 seconds
Valid Intervals (Current The number of elapsed finished 15-min intervals for which statistics data can
statistics only) be displayed, in addition to the current (not finished) interval (up to 96)
Interval number (Selected Number of interval for which statistics is displayed

interval statistics only)
Total Rx Frames Total number of frames received
Total Tx Frames Total number of frames transmitted

Idle Frames Error Number of idle frames errors.

Idle frame is a special four-octet GFP control frame consisting of only a GFP
Core Header with the PLI and cHEC fields (see 6.1.1 in G.7041) set to 0, and
no Payload Area. The Idle frame is intended for use as a filler frame for the
GFP transmitter to facilitate the adaptation of the GFP octet stream to any
given transport medium where the transport medium channel has a higher
capacity than required by the client signal
cHEC Errors Number of cHEC errors.

GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Core Header Error Check (cHEC).
tHEC Errors Number of tHEC errors.

GFP Core Header consists of a 16-bit PDU Length Indicator field and a 16-bit
Type Header Error Check (tHEC).
FCS Errors The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
PTI Mismatch Number of payload Headers with incorrect PTI values
EXI Mismatch Number of payload Headers with incorrect EXI values
Clearing Statistics
There are two options for clearing GFP statistics data:
• Clearing all statistics.

 To clear all statistics data:

The statistics are cleared.
HDLC Ports (CL.2 Modules)
Applicable Modules
HDLC ports defined on CL.2 modules represent VCGs (Virtual Concatenation
Groups) with LAPS encapsulation. They can be mapped either directly to the
physical layer or to a VCG. In the latter case, the binding is done in two stages

and the VCG is further bound to the physical layer. The maximum total number of
GFP and HDLC ports that can be configured per slot is 32.
For HDLC ports defined on M8E1, M8T1 and M8SL modules, see HDLC Ports (I/O
Modules).
Standards
HDLC ports in CL.2 modules comply with ITU-T Rec. X.86.
Factory Defaults
Megaplex-4 is supplied with all HDLC ports disabled.
Configuring HDLC Ports
 To configure an HDLC port:

1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.
description to the port

the port
Binding the bind vc4-sts3c <slot>/<port>/<tributary> For the allowed ranges, seeTable 6-66.
corresponding bind vc3-sts1 <slot>/<port>/<au4>/ The connection to a VC or VT/STS depends
VC/VT/STS-1/VCG to the <tributary> on the frame selection (frame=sdh or
HDLC port bind vc-vt <slot>/<port>/ frame=sonet)
<au4>/<tug_3>/<tug_2>/
You cannot bind both a VCG and a
[<tributary>]
VC/VT/STS-1 to a GFP port
bind vcg <slot>/<port>
Using no before the corresponding
Assigning user-defined VC vc profile <profile name> For creating VC profiles, see VC Profiles.
profile to the port Using no vc removes the profile
Before you assign the user-defined profile,
you must use the no vc command to
remove the automatical hvc-laps or lvc-eos
profile assignement
Displaying HDLC Statistics

HDLC ports of CL.2 modules feature the collection of statistical diagnostics.

 To display the HDLC port statistics:

• At the prompt config>slot>port>hdlc (<slot><port>)#, enter show statistics
statistics

HDLC statistics are displayed. The counters are described in Table 6-63.
For example:
Current Statistics:
mp4100>config>port>hdlc(cl-b/6)# show statistics current
Current
---------------------------------------------------------------
Total TX Frames : 569703
Address Mismatch : 0
Control Mismatch : 0
LAPS Sapi Mismatch : 0
FCS Errors : 0
Abort Frames : 0
Minimum Length Violation : 0
Maximum Length Violation : 0

mp4100>config>port>sdh-sonet(cl-a/1)# show statistics interval 67
Interval
---------------------------------------------------------------
Address Mismatch : 0
Control Mismatch : 0
LAPS Sapi Mismatch : 0
FCS Errors : 0
Abort Frames : 0
Minimum Length Violation : 0
Maximum Length Violation : 0
Table 6-63. HDLC Statistics Parameters

Total Rx Frames Total number of frames received
Total Tx Frames Total number of frames transmitted
Address Mismatch The number of frames with wrong address value (the correct value of
Address byte in LAPS Overhead is 0x4)
Control Mismatch The number of frames with wrong control value (the correct value of Control
byte in LAPS Overhead is 0x3)
LAPS Sapi Mismatch The number of frames with wrong SAPI value (the correct value of SAPI byte
in LAPS Overhead is 0xF0E1)
FCS Errors The number of frames received on this interface that are an integral number
of octets in length but do not pass the FCS check
Abort Frames The number of abort frames received (a packet can be aborted by inserting
the abort sequence, 0x7d7e. Reception of this code at the far end will cause
the receiver to discard this frame)
Minimum Length Violation Total number of undersized frames received/transmitted
Maximum Length Violation Total number of oversized frames received/transmitted
Clearing Statistics
There are two options for clearing HDLC statistics data:


HDLC Ports (I/O Modules)
Applicable Modules
This section describes HDLC ports defined on M8E1, M8T1 and M8SL modules.
These ports can be bound to the physical layer representing E1/T1 ports or
specific timeslots. For HDLC ports defined on CL.2 modules, see HDLC Ports (CL.2
Modules).
Standards
HDLC ports in E1/T1 I/O modules comply with IETF RFC 1990.
Factory Defaults
Megaplex-4 is supplied with all HDLC ports disabled.
Configuring HDLC Ports
 To configure an HDLC port:

1. Navigate to configure port hdlc <slot>/<port> to select the HDLC port to
configure.
The config>port>hdlc>(<slot>/<port>)# prompt is displayed.

description to the
port
Administratively no shutdown Using shutdown disables the port

enabling the port

Binding the bind e1 For the allowed ranges, seeTable 6-66.

corresponding <slot>/<port>/[<tributary>] When binding e1 ports, optional <tributary> index
E1/T1 port to the bind t1 relates to Megaplex Optimux cards (OP-34C, OP-108C)
HDLC port <slot>/<port>/[<tributary>] only and denotes their internal E1 ports.
bind e1-i <slot>/<port> Binding the HDLC port to specific timeslots of E1/T1
bind t1-i <slot>/<port> physical port is done via the xc command.
Using no before the corresponding command removes
the binding
HDLC ports of the M8E1, M8T1 and M8SL modules
cannot be bound to E1-i/T1-i ports of CL-B.
Selecting encapsulation {raw-hdlc | raw-hdlc – HDLC encapsulation protocol

encapsulation c-hdlc} c-hdlc – CISCO HDLC encapsulation protocol
method of the
HDLC port
Assigning VC vc profile <profile name> Using no vc removes the profile

profile to the port
Note
It is possible to open only 8 E1/E1-i/T1 links per M8E1/M8SL/M8T1 module and
assign up to 4 HDLC ports to each of them so that the total capacity is 32 HDLC
ports per module. Moreover, every E1/E1-i/T1 used reduces the number of
external E1/T1 links that can be connected to E1/T1 equipment.
Table 6-64 lists messages generated by Megaplex-4 when a configuration error
on HDLC/PPP/MLPP ports is detected.
Table 6-64. HDLC/PPP/MLPPP Port Configuration Error Messages
420 Error MLPPP PORT CAN'T BE BOUND E1 port bound to MLPPP port cannot be a member of
TO TDM GROUP protection group
422 Error MLPPP PORT SHOULD BE MLPPP port cannot be bound to a framed port
BOUND TO UNFRAMED E1
423 Error HDLC/PPP PORT OR Whenever the HDLC/PPP port is connected, the associated
ASSOCIATED E1/T1 PORT ports should be at ‘no shutdown’, and vice-versa.
DOWN
424 Error HDLC/PPP ILLEGAL SLOT The I/O slot specified for an HDLC port and the slot of its
ASSOCIATION associated E1/E1-i/T1/T1-i port cannot be another I/O
slot. It must be either the same I/O slot or CL-A/CL-B.
The I/O slot specified for a PPP port and the slot of its
associated E1 port must be the same I/O slot.
426 Error MORE THAN ONE MLPPP PORT Only one MLPPP port can be active on any given I/O
PER SLOT module

427 Error ONLY ONE E1/T1 PORT CAN BE Only one E1/T1 port can be bound to a single HDLC port
BOUND TO HDLC PORT
429 Error EVEN TS NUM MUST BE HDLC rate must be a multiple of 128 kbps (even number
DEFINED PER HDLC PORT of timeslots).
430 Error LINKS ASSIGNED FOR MLPPP The maximum number of E1 ports that can be bound to
PORT EXCEEDED MLPPP port is 8.
431 Error ILLEGAL NUMBER OF Illegal number of timeslots has been selected
TIMESLOTS
432 Error ILLEGAL HDLC SLOT All 4 HDLC ports bound to a specific E1-i/T1-i port must be
ASSIGNMENT assigned (for processing) to the same I/O module.
433 Error MAX 4 HDLC PORTS MAY BE The maximum number of HDLC ports defined per
DEFINED PER LINK E1/E1-i/T1/T1-i port is 4
434 Error PORT LINE TYPE MISMATCH TDM cross conect can be done only for unframed E1/T1
ports
437 Error SAME E1 BOUND TO E1 port can’t be bound to more than one PPP port
DIFFERENT PPP PORTS
Internal Ethernet (D-NFV) Ports
Applicable Modules
These ports are available in D-NFV modules.
Standards
IEEE 802.3, RFC 4836, RFC 3635.
Factory Defaults
By default, the D-NFV Ethernet ports have the following configuration.
mp4100>config>port>int-eth(2/1)# info detail
min-tagged-frame-length 68
egress-mtu 1790
queue-group profile "MaxDefaultQueueGroup"
no policer
For description of default queue group profiles, see Queue Group Profiles section
in Chapter 8.

Configuring Internal Ethernet Ports
 To configure the internal Ethernet port parameters of the D-NFV module:

1. Navigate to configure port int-ethernet <slot>/<1> to select the Ethernet
port to configure.
The config>port>eth>(<slot>/<1>)# prompt is displayed.
Note Port 2 will be activated in the future versions.
2. Enter all necessary commands according to the tasks listed in the table
below.
Note There is no need in opening the internal Ethernet port, since it always up.
port
Setting maximum frame size (in egress-mtu <64–9600>

bytes) to transmit (frames above
the specified size are discarded)
Assigning queue group profile to queue-group profile <queue- Megaplex-4 with CL.2/A modules only
Ethernet port group-profile-name> The queue group profile is defined under
Quality of Service (QoS) in Chapter 8.
no queue-group removes queue group
association
Ethernet ports is defined with 10 Mbps
shaper. Define a new queue group profile if
you need more bandwidth.
The queue group profile cannot be edited.
Thus to use bridge connectivity you need to
remove the existing queue group profile from
this Ethernet port, configure a new queue
group profile and assign it to this port.
Activating/deactivating a policer policer-profile <name> The policer profile is defined under Quality of
profile Service (QoS) in Chapter 8.
Using no policer <name> deactivates this
policer profile
Setting the minimum VLAN-tagged min-tagged-frame-length {64 | 68

frame length (in bytes) that will | 72}
be accepted
Specifying the Ethertype expected tag-ethernet-type Megaplex-4 with CL.2/A modules only
in Ethernet packet <0x0000-0xFFFF>

Displaying D-NFV Internal Ethernet Port Status

You can display the status and configuration of an individual internal Ethernet
port.
 To display status of a D-NFV internal Ethernet port:

• At the prompt config>port>int-eth(<slot>/<1>)#, enter show status.
The Ethernet port status parameters are displayed.
For example:
mp4100>config>port>int-eth(2/1)# show status
Name IO-2 ethernet 01
Operational Status : Up
Auto Negotiation : Complete
Speed And Duplex : 1000 Full Duplex
Testing D-NFV Ports

No testing is available.
Displaying Ethernet Port Statistics

The Ethernet ports feature statistics collection in accordance with
RMON-RFC2819.
 To display the D-NFV Ethernet port statistics:

• At the prompt config>slot>port>int-eth(<slot>/<port>)#, enter show
statistics.
Ethernet port statistics are displayed. The counters are described in the
table below.
mp4100>config>port>int-eth(2/1)# show statistics
Running
-----------------------------------------------------------------------------
Counter Rx Tx
Total Frames 918141957
Total Octets 878307843 2624907620
Unicast Frames 917997904 18446744073418874042
FCS Errors --
Jabber Errors 0 --
Oversize Frames 0
Discard Frames -- 1519-Max Octets 0
Paused Frames
64 Octets 142072

65-127 Octets 518879389

128-255 Octets 539
256-511 Octets 134
512-1023 Octets 167213425
1024-1518 Octets 231906387
1519-Max Octets 0
Table 6-65. Ethernet Statistics Parameters
Unicast Frames Total number of unicast frames received/transmitted
Multicast Frames Total number of multicast frames received/transmitted
Broadcast Frames Total number of broadcast frames received/transmitted
Paused Frames Total number of pause frames (used for flow control)
received/transmitted through the corresponding Ethernet port
FCS Errors The number of frames received on this interface that are an
integral number of octets in length but do not pass the FCS
check
Filtered Frames Total number of filtered frames received/transmitted
Jabber Errors Total number of frames received with jabber errors
Oversize Frames Total number of oversized frames received/transmitted
Undersize Frames Total number of undersized frames received/transmitted I/O Ethernet ports only
Discard Frames Total number of discarded frames received/transmitted Not relevant for D-NFV
64 Octets Total number of received/transmitted 64-byte packets
65–127 Octets Total number of received/transmitted 65–127-byte packets
1024–1518 Octets Total number of received/transmitted 1024–1518-byte

packets
1519 - Max Octets Total number of received/transmitted packets with

1519 bytes and up to maximum
Clearing Statistics

• At the prompt config>port>int-eth<slot>/<port>)#, enter clear-statistics.

Logical MAC Ports
Applicable Modules
To describe and map the Ethernet traffic passing over different media (E1/T1, T3,
SDH/SONET, etc), the Megaplex-4 architecture uses a concept of Logical MAC
ports. Logical MAC represents the MAC layer of the entity. It should be bound to a
gfp, hdlc or mlppp port, which, in its turn, should be bound to the physical layer.
Table 6-66 lists the possible entities that can be bound to the Logical MAC, with
their corresponding media, protocols and possible values.
Table 6-66. Entities Bound to Logical MAC
Entities Media Protocol Module Possible

Values
gfp Ethernet over GFP encapsulation CL.2 1 to 32

SDH/SONET protocol
gfp Ethernet over T3 GFP encapsulation T3 1 to 16

protocol
gfp Ethernet over GFP encapsulation VS-16E1T1-EoP 1 to 16

E1/T1 protocol
hdlc Ethernet over LAPS encapsulation CL.2 1 to 32

SDH/SONET protocol
hdlc Ethernet over HDLC Layer 2 protocol M8E1/M8T1, M8SL 1 to 32

E1/T1
mlppp Ethernet over E1 MLPPP, PPP Layer 2 M8E1, M8SL 1

protocols
Factory Defaults
By default, the Logical MAC ports have the following configuration.
For CL module:
mp4100>config>port>log-mac(cl-a/5)$ info detail
name "CL-A Logical mac 05"
shutdown
egress-mtu 1790
queue-group profile "LMDefaultQueueGroup"
For T3 module:
name "IO-3 Logical mac 05"
shutdown
For VS-16E1T1-EoP module:


name "IO-10 Logical mac 05"
shutdown
egress-mtu 1790
queue-group profile "LMDefaultQueueGroup"
For description of the Logical Mac default queue group profile, see Queue Group
Profiles section in Chapter 8.
Configuring Logical MAC Ports
 To configure the Logical MAC port:

1. Navigate to configure port logical-mac <slot>/<port> to select the Logical Mac
entity to configure.
The config>port>logical-mac>(<slot>/<port>)# prompt is displayed.
Assigning short description to name <string>* Using no name removes the name
Logical MAC
Administratively enabling Logical no shutdown* Using shutdown disables the Logical MAC
MAC
Binding HDLC port to Logical MAC bind hdlc <slot>/<port> Ethernet over E1/T1: port=HDLC bundle
Ethernet over SDH/SONET: port=VCG using
LAPS encapsulation protocol
Binding GFP port to Logical MAC bind gfp <slot>/<port>* GFP port=VCG using GFP encapsulation
protocol
Binding MLPPP port to Logical bind mlppp <slot>/<port>

MAC
Enabling OAM (EFM) on the efm See Ethernet OAM (EFM) in Chapter 8.
Logical MAC port no efm disables OAM (EFM)

bytes) to transmit (frames above
the specified size are discarded)
Assigning queue group profile to queue-group <queue- no queue-group removes queue group
Ethernet port group-profile-name> association
Specifying the Ethertype tag-ethernet-type

expected in Ethernet packet <0x0000-0xFFFF>
Note
The only parameters used for configuration of logical-mac ports of T3 modules
are marked with an asterisk (*).

To bind a flow to a Logical MAC port, see ingress-port logical-mac command

under config>flows>flow.
Viewing MAC Address

For viewing the MAC address used by the Logical MAC port, follow the
instructions below.
 To view the MAC address used by the Logical MAC port:

1. Navigate to config>port> log-mac (<slot>/<port>)#
mp4100>config>port>log-mac(cl-a/1)$ show status
MAC Address : 00-20-D2-F3-BC-D5
Note For MAC address allocation mechanism, see Chapter 10.
Displaying Logical MAC Statistics

You can display statistics for the Logical MAC ports of T3 modules.
 To display the Logical MAC statistics:

At the prompt config>slot>port>log-mac (<slot>/<port>)#, enter show statistics.
Logical MAC statistics are displayed. The counters are described in the table
below. For example:

mp4100>config>port>log-mac(9/1)# show statistics

Running
-----------------------------------------------------------------
Counter Rx Tx
Total Frames 23785 23789
Total Octets 2473744 2473952
Total Frames/Sec 914 914
Total Bits/Sec 761152 761216
Minimum Bits/Sec 0 0
Maximum Bits/Sec 761152 0
Unicast Frames 23786 23788
Error Frames 0
64 Octets 0 0
65-127 Octets 23784 23784
128-255 Octets 0 0
256-511 Octets 0 0
512-1023 Octets 0 0
1024-1518 Octets 0 0
1519-2047 Octets 0 0
2048-Max Octets 0 0
Table 6-67. Logical MAC Statistics Parameters
Total Frames Rx/Tx Total number of frames received/transmitted
Total Octets Rx/Tx Total number of bytes received/transmitted
Unicast Frames Rx/Tx Total number of unicast frames received/transmitted
Multicast Frames Rx Total number of multicast frames received/transmitted
Broadcast Frames Rx Total number of broadcast frames received/transmitted
Total Frames/Sec Rx/Tx Number of frames received/transmitted per second
Total Bits/Sec Rx/Tx Number of bits received/transmitted per second
Minimum Bits/Sec Rx/Tx Minimum number of bits received/transmitted per second
Maximum Bits/Sec Rx/Tx Maximum number of bits received/transmitted per second
2048-Max Octets Total number of received/transmitted packets with 2048 bytes and up to
maximum

Clearing Statistics
 To clear the statistics for a Logical MAC port:

• At the prompt config>port>log-mac<slot>/<port>)#, enter clear-statistics.
MLPPP Ports
Applicable Modules
MLPPP ports exist only on M8E1 and M8SL modules and are mapped to a PPP
port. The binding is done in two stages and the PPP port should be further bound
to the physical layer (see Figure 1-8 in Chapter 1).
M8E1 and M8SL modules have one MLPPP port per module.
The MLPPP bundle can use any number of the links supported by the module, that
is, from 1 to 8. All the links (ports) used by the MLPPP bundle must have identical
physical layer parameters and their line-type parameter must be configured as
unframed. Therefore, each bonded link adds 2048 kbps to the available
bandwidth.
Management traffic is carried inband, as part of the Ethernet traffic, using the
dedicated management VLAN configured for the Megaplex-4 host.
Note that ports bound to MLPPP ports cannot be part of a protection group.
However, some redundancy is inherent in the MLPPP protocol, because if one of
the bonded links is out-of-service, the result is only a reduction in the available
transmission bandwidth.
Standards
The MLPPP ports conform to the IETF RFC 1990 standard.
Factory Defaults
Megaplex-4 is supplied with all MLPPP ports disabled. The MTU default value is
250.
Configuring MLPPP Ports
 To configure an MLPPP port (bundle):

1. Navigate to configure port mlppp <slot>/<port> to select the MLPPP port
(bundle) to configure.
The config>port>mlppp>(<slot>/<port>)# prompt is displayed.

port
Administratively enabling the port no shutdown Using shutdown disables the bundle
Slot: 1 to 10, Port: 1 to 8

Binding the PPP port to the MLPPP bind ppp <slot>/<port>
Using no bind ppp<slot>/<port>
port
removes the binding
Selecting the MTU (maximum The supported range is 80 to 1600

transmission unit) for fragmented mtu <value in bytes> bytes.
packet
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
 To map E1 port 1 to Ethernet Port 2:

• Bind corresponding E1 streams to each PPP port
• Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
• Configure Logical Mac port 5/1 and bind to it the MLPPP port
• Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.


mp4100#
mp4100# exit all
mp4100# configure port mlppp 5/1 no shutdown
mp4100# configure port mlppp 5/1 bind ppp 5/1

mp4100# configure flows classifier-profile unw match-any match

all
mp4100>config>flows>flow(01)$ classifier unw
mp4100>config>flows>flow(01)$ egress-port eth 5/2
mp4100>config>flows>flow(01)$ ingress-port logical-mac 5/1
mp4100>config>flows>flow(01)$ commit
mp4100>config>flows>flow(01)$ no shutdown

mp4100>config>flows>flow(02)$ egress-port logical-mac 5/1
mp4100>config>flows>flow(02)$ ingress-port eth 5/2
See Table 6-64.
PCS Ports
Applicable Modules
PCS (Physical Coding Sublayer) ports available on the ASMi-54C and SH-16
modules determine the Ethernet (packet) physical layer transmission capabilities
over SHDSL lines. The number of PCS ports on each module is 8 for ASMi-54C
modules and 16 for SH-16 modules.
The following can be configured for the PCS ports:

• Assigning PCS port name

• Setting port administrative status
• Binding an SHDSL port to a PCS port
Standards
PCS ports comply with IEEE 802.3-2005.
In Megaplex-4, PCS ports are used to transport Ethernet traffic over SHDSL.
The internal SHDSL processing subsystem of ASMi-54C and SH-16 modules
enables configuring the desired Physical Coding Sublayer parameters for each
SHDSL line (actually – for each SHDSL port).
PCS ports are processed in groups of four:
• ASMi-54C modules include two groups of PCS ports: 1 to 4, and 5 to 8.
• SH-16 modules include four groups of PCS ports: 1 to 4, 5 to 8, 9 to 12 and
13 to 16.
PCS ports are independently configurable.
In ASMi-54C/ETH and SH-16 modules, the available bandwidth is the payload rate
of the associated line. In ASMi-54C/N, the available PCS bandwidth is the payload
rate of the associated line, less any bandwidth assigned to the associated E1
port of the same line.
Even when all SHDSL lines of the ASMi-54C/SH-16 modules operate in 2-wire
mode, the PCS transport bandwidth can be increased using PAF (PME Aggregation
Function), also defined in IEEE 802.3-2005. PAF creates PCS groups. The PCS
groups that can be configured on the ASMi-54C/N, ASMi-54C/ETH and SH-16
modules are listed in Table 6-68, Table 6-69 and Table 6-70, respectively.
The main functions performed for each PCS port include:
• Ethernet payload data rate matching: the average payload rate accepted by
each PCS port is matched to the physical rate supported by the
corresponding PME.
• As for M-pair bonding, one of the PCS ports (the PCS with the lowest index in
the group) is automatically selected as the master PCS port, from which all
the other PCS ports copy their parameters.
Each active PCS port can serve as a bridge port that can terminate Ethernet flows
configured within the Megaplex-4.
Table 6-68. Supported PCS Groups versus Lines Parameter, ASMi-54C/N module
Maximum Number of Number of SHDSL Ports SHDSL Ports in PCS Master PCS in the
PCS Groups in PCS Group Group Group
1, 2 1
4 2 (4 wires)
3, 4 3

Maximum Number of Number of SHDSL Ports SHDSL Ports in PCS Master PCS in the
PCS Groups in PCS Group Group Group
5, 6 5
2 (4 wires)
7, 8 7
8 1 (2 wires) 1 to 8 N/A
Table 6-69. Supported PCS Groups versus Lines Parameter for ASMi-54C/ETH
Maximum Number Number of SHDSL Ports SHDSL Lines in PCS Master PCS in the
of PCS Groups (Lines) in PCS Group Group Group
4 1, 2, 3, 4 1
2
4 5, 6, 7, 8 5
1, 2 1
2
3, 4 3
4
5, 6 5
2
7, 8 7
Table 6-70. Supported PCS Groups versus Lines Parameter for SH-16
Maximum Number Number of SHDSL Ports SHDSL Lines in PCS Master PCS in the
of PCS Groups (Lines) in PCS Group Group Group
1, 2, 3, 4 1
5, 6, 7, 8 5
4 4(8 wires)
9,10, 11,12 9
13,14, 15,16 13
1, 2 1
3, 4 3
5, 6 5
7, 8 7
8 2(4 wires)
9,10 9
11,12 11
13,14 13
15,16 15
16 1(2 wires) 1,2…, 16 -
Factory Defaults
By default, the PCS ports have the following configuration.
mp4100>config>port>pcs(3/3)# info detail

name "IO-3 Pcs 03"

shutdown
no efm
egress-mtu 1790
queue-group profile "PcsDefaultQueueGroup"
no l2cp
For description of the PCS default queue group profile, see Queue Group Profiles
section in Chapter 8.
Configuring a PCS Port

235B
 To configure a PCS port:

1. Navigate to configure port pcs <slot>/<port> to select the port to configure.
The config>port>pcs>(<slot>/<port># prompt is displayed.
Assigning short description to a name <string> Using no name removes the name
PCS port
Administratively enabling the no shutdown Using shutdown disables the PCS

port
Enabling OAM (EFM) on the PCS efm See Ethernet OAM (EFM) in Chapter 8.
port (Carrier Ethernet class CL ASMi-54C/ETH modules (without E1 links)
only) and SH-16 modules
no efm disables OAM (EFM) on the PCS
port

bytes) to transmit (frames
above the specified size are
discarded)
Associating a Layer-2 control l2cp <l2cp-profile-name> ASMi-54C/ETH modules (without E1 links)

processing profile with the port no l2cp and SH-16 modules
(Carrier Ethernet class CL only) Defines discarding or tunneling policy for
Layer-2 protocols.
no l2cp removes association with L2CP
profile
The associated L2CP profile specifies peer
action for the following MAC addresses
depending on the protocol in use:
• 01-80-C2-00-00-00 (RSTP)
• 01-80-C2-00-00-02 (OAM (EFM))

Configuring collection of pm-collection interval <seconds> Note: You can enable PM statistics
performance management collection for all Ethernet ports rather
statistics for the port that are than enabling it for individual ports. Not
presented via the RADview here – ask Maxim/Alex In addition to
Performance Management enabling PM statistics collection for the
portal ports, it must be enabled for the device.
Refer to the Performance Management
section in the Monitoring and Diagnostics
chapter for details.
Configuring collection of pm-collection interval <seconds> Note: In addition to enabling PM statistics

performance management collection for the port, it must be enabled
statistics for the port, that are for the device. Refer to the Performance
presented via the RADview Management section in the Monitoring
Performance Management and Diagnostics chapter for details.
portal
Assigning queue group profile queue-group profile <queue- no queue-group removes queue group
to the PCS port (Carrier group-profile-name> association
Ethernet class CL only)
Specifying the Ethertype tag-ethernet-type

expected in Ethernet packet <0x0000-0xFFFF>
(Carrier Ethernet class CL only)
Binding a SHDSL port to a PCS

bind shdsl <slot><port> Using no before bind removes the binding
port
Displaying PCS Port Status

You can display the status and configuration of an individual PCS port.
 To display the status of a PCS port:

• At the prompt config>port>pcs(<slot/port)#, enter show status.
The PCS port status parameters are displayed.
For example:
 To display the status of PCS port 15 of an SH-16 module installed in slot 3:

mp4100>config>port>pcs(3/15)# show status
Name : IO-3 Pcs 15
Operation Status : Testing
Loopback : Remote On Remote
Testing PCS Ports

You can perform a remote-on-remote loopback of the PCS port of the
ASMi-54C/N and SH-16 modules. In ASMi-54C/N, this loopback is mainly used in
the Ethernet BERT test but can be also used to check Ethernet connectivity using
external test equipment.

The ASMi-54C/ETH module does not support loopbacks on its PCS ports.
 To perform a loopback on a PCS port of the ASMi-54C/N or SH-16 module:

1. Navigate to configure port pcs <slot>/<port> to select the PCS port to
configure.
The config>port>pcs>(<slot>/<port>)# prompt is displayed.
Before activating the remote-on-remote loopback on a PCS port, be aware that if

Ethernet services are being provided by the system, the traffic passing through
Warning the PCS port will be looped. Take appropriate care to prevent this scenario. Do
not activate this loop when the system is connected to the live network.
Setting loopback duration loopback remote-on-remote duration Using no loopback disables the loopback
and activating the loopback <duration in minutes 1..30> ]
on the PCS port
Displaying PCS Statistics

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

At the prompt config>slot>port>pcs (<slot>/<port>)#, enter show statistics
PCS statistics are displayed. The counters are described in the table
below. For example:
mp4100>config>port>pcs(3/1)# show statistics
Running
-----------------------------------------------------------------
Total Frames Rx : 36911
Total Frames Tx : 23851
Total Octets Rx : 2511512
Total Octets Tx : 1620916
Unicast Frames Tx : 0
Multicast Frames Rx : 0
Broadcast Frames Rx : 0
FCS Errors : 0
Jabber Errors : 0
Undersize Frames : 0
Oversize Frames : 0
Paused Frames : 0
64 Octets : 0
65-127 Octets : 36706
128-255 Octets : 0
256-511 Octets : 0

512-1023 Octets : 0
1024-1528 Octets : 0
Table 6-71. PCS Statistics Parameters
Total Frames Rx/Tx Total number of frames received/transmitted
Total Octets Rx/Tx Total number of bytes received/transmitted
Unicast Frames Tx Total number of unicast frames transmitted
Multicast Frames Rx Total number of multicast frames received
Broadcast Frames Rx Total number of broadcast frames received
FCS Errors Total number of frames received on this PCS that are an integral number of
octets in length but do not pass the FCS check
Jabber Errors Total number of frames received with jabber errors
Undersize Frames Total number of undersized frames received/transmitted
Oversize Frames Total number of oversized frames received/transmitted
Paused Frames Total number of pause frames (used for flow control) received/transmitted
through the corresponding PCS
Clearing Statistics
 To clear the statistics for a PCS:

• At the prompt config>port>pcs<slot>/<port>)#, enter clear-statistics.
PPP Ports
Applicable Modules
PPP is the intermediate layer between the MLPPP and the physical (E1) layer.
Dividing the Ethernet traffic between several PPP ports grouped by a single
MLPPP entity provides increased bandwidth over several physical connections.
PPP ports exist only on M8E1 and M8SL modules.

Standards
The PPP ports conform to the IETF RFC 1990 standard.
Factory Defaults
Megaplex-4 is supplied with all PPP ports disabled.
Configuring PPP Ports
 To configure a PPP port:

1. Navigate to configure port ppp <slot>/<port> to select the PPP port to
configure.
The config>port>ppp>(<slot>/<port>)# prompt is displayed.
Binding the PPP port (logical entity) to Slot: 1 to 10; Port: 1 to 8

bind e1 <slot>/<port>
the E1 physical port of a M8E1/M8SL Using no bind e1 <slot>/<port>
module removes the binding
Example
The following section illustrates how to map E1 traffic to Ethernet on the M8E1
module installed in slot 5, via configuring PPP and MLPPP ports.
 To map E1 port 1 to Ethernet Port 2:

• Bind corresponding E1 streams to each PPP port
• Bind the all the 8 PPP ports to the MLPPP port of the M8E1 module
• Configure Logical Mac port 5/1 and bind to it the MLPPP port
• Configure ingress and egress flows between and Logical MAC port 5/1 and
Ethernet Port 2 of the M8E1 module.
Note The PPP ports are administratively enabled by default so there is no need for the
no shutdown command.


mp4100#
mp4100# exit all
mp4100# configure port mlppp 5/1 no shutdown

mp4100# configure flows classifier-profile unw match-any match all

mp4100>config>flows>flow(01)$ egress-port eth 5/2
mp4100>config>flows>flow(01)$ ingress-port logical-mac 5/1

mp4100>config>flows>flow(02)$ egress-port logical-mac 5/1
mp4100>config>flows>flow(02)$ ingress-port eth 5/2
See Table 6-64.
Serial Bundle Ports
Applicable Modules
The serial bundle ports are available only on LS-6N, LS-12 modules. The following
parameters can be configured for the serial bundle ports:
• Port name
• Setting the port data rate.

See the LS-6N, LS-12 Modules section in Megaplex-4 I/O Modules Installation and
Operation Manual.
Factory Defaults
Megaplex-4 is supplied with all serial bundle ports disabled. Other parameter
rate 64kbps
Configuring Serial Bundle Port Parameters
 To configure the serial bundle port parameters:

1. Navigate to configure port serial-bundle <slot>/<port> to select the port to
configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.
to port

port
Specifying the bandwidth

allocated to the rate {14.4kbps | 32kbps | 56kbps |
corresponding composite 64kbps | 128kbps | 192kbps | 256kbps |
channel on the Megaplex 384kbps | 512kbps | 768kbps}
uplink
Binding external serial ports

To remove the binding, you must bind this
that will be carried over this bind serial <slot> serial-bundle port to another serial port
serial bundle port
(composite channel)
Example
The following section illustrates how to configure the serial bundle (internal) port
1 on the LS-12 module installed in slot 6:
• Data rate 32 kbps.
• Bind external serial ports 1 and 2 to be carried over this serial bundle port

mp4100>config# port serial-bundle 6/1

mp4100>config>port>serial-bundle(6/1)# no shutdown
mp4100>config>port>serial-bundle(6/1)# bind serial 1
mp4100>config>port>serial-bundle(6/1)# bind serial 2
mp4100>config>port>serial-bundle(6/1)# rate 32
mp4100>config>port>serial-bundle(6/1)# exit
mp4100>config>port# exit
error on modules with serial-bundle ports (LS-6N/LS-12) is detected.
Table 6-72. LS-6N/LS-12 Configuration Error Messages
210 Error BANDWIDTH OVERFLOW The bandwidth allocated to the internal port of the
LS-6N/LS-12 module must be greater than, or equal to the
sum of the following:
• The bandwidths allocated to the external ports
• Management channel, if the remote unit is a KM
working in slave mode
• Frame synchronization
• Channel end-to-end control signals (one per pair)
211 Error SERIAL PORTS NOT IN SAME The two adjacent serial ports (1/2, … 11/12) of an LS-12
RATE GROUP module must operate in the same rate group.
212 Error SERIAL PORTS NOT BOUND TO The two adjacent serial ports (1/2, … 11/12) of an LS-12
SAME SERIAL BUNDLE PORT module must be bound to same serial bundle port.
213 Error SERIAL PORT/SERIAL-BUNDLE The external port rate is not compatible with the data rate
PORT RATE MISMATCH allocated on the link to the corresponding internal port
214 Error NO EXTERNAL CHANNEL IS The internal port is connected to the link, but no external
CONNECTED port is connected to the internal port
Testing Serial-Bundle Ports

The LS-6N and LS-12 modules feature the test loopbacks on each composite data
stream (serial-bundle port). The test and diagnostics functions available on each
serial-bundle port are:
Composite Data Stream Local Digital Loopback

When a local loop is activated on the Megaplex-4 composite data stream, the
module composite transmit signal is returned to its receive path. As a result, each
individual channel receives its own signal.

The composite transmit signal is still connected to the transmit path and reaches
the LS-6N/12 module installed in the remote Megaplex unit, therefore the remote
equipment does not lose synchronization.
While the loop is connected, all the local users connected to the module must
receive their own signals, and the S.LOSS indicators of the local module must be
off. This loopback provides a quick operational check of the local module. The
loopback signal path is shown in Figure 6-32.
Composite Data Stream Remote Digital Loopback

When a remote composite data stream loopback is activated, the LS-6N/12
module loops back the receive signal toward the remote equipment. The received
signal remains connected as usual to the receive path of the local module, and
therefore the local S.LOSS indicates must be off. The loopback signal path is
shown in Figure 6-33.
While the loop is connected, and the link to the remote equipment operates
normally, all the users connected to the remote module must receive their own
signals, and the S.LOSS indicators of the modules must be off.
This loop allows the user to perform a quick operational check of the end-to-end
transmission via this module.
Channel 1
.
Channel 2 .
. .
. .
User or . . .
Channel 12 .
Test
Equipment
User or
LS-12 LS-12 Test
Equipment
I/O MODULES
I/O MODULES
Local Unit Remote Unit
System
Management
Figure 6-32. Composite Local Loopback, Signal Path

Channel 1
.
Channel 2 .
. .
. .
User or . . .
Channel 12 .
Test
Equipment
User or
LS-12 LS-12 Test
Equipment
I/O MODULES
I/O MODULES
Local Unit Remote Unit
System
Management
Figure 6-33. Composite Remote Loopback, Signal Path
Loopback Duration
to limit its duration to a selectable interval in the range of 1 through 30 minutes.
 To perform a loopback on the serial-bundle port:

1. Navigate to configure port serial-bundle <slot>/<port> to select the serial
port to configure.
The config>port>serial-bundle>(<slot>/<port>)# prompt is displayed.

Activating and loopback {local | remote} • local. Returns the transmitted data
configuring the at the physical layer to the receiving
direction of the path. The local physical loopback
loopback includes a configurable timeout
mechanism that ends the loopback
operation after a user-defined
duration.
• remote. Returns the received data
at the physical layer to the
transmitting path.
SVI (Switched Virtual Interface) Ports

A switched virtual interface (SVI) is a VLAN of switch ports represented by one
interface to a routing or bridging system. There is no physical interface for the
VLAN, and the SVI provides the Layer 3 processing for packets from all switch
ports associated with the VLAN.
There is one-to-one mapping between a VLAN and SVI, thus only a single SVI can
be mapped to a VLAN.
In Megaplex-4, an SVI port is an intermediate Ethernet entity between the
Bridge/Router and another Ethernet port (bound one-to-one). It also serves as an
ingress or egress port for terminating management flows. The flow is configured
between the physical port, which is the management source, and the
corresponding SVI port bound to the bridge port. This flow will classify the
management traffic to be forwarded to the bridge port. For illustration, see
Example under Management Bridge in Chapter 8.
You can enable and operate a switched virtual interface (SVI port) as explained
below.
 To define an SVI port:

• At the config>port# prompt, enter svi <port number>.
The config>port>svi <port number># prompt appears and the relevant SVI
port is defined.
 To administratively enable an SVI port:

• At the config>port>svi<port number># prompt, enter no shutdown.
The SVI port is administratively enabled.
 To administratively disable an SVI port:

• At the config>port>svi<port number># prompt, enter shutdown.
The SVI port is administratively disabled.

TDM Bridge Ports
Applicable Modules
To implement specific bidirectional broadcast applications over serial ports of VS
modules, Megaplex-4 architecture uses an entity named TDM bridge port. TDM
bridge ports exist only on VS modules and are mapped to serial ports. The
maximum number of TDM bridge ports is 6 per VS-6/BIN module and 4 per VS-12
module.
Standards
TDM bridge ports are RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with all TDM bridge ports disabled.
Configuring TDM Bridge Ports
 To configure a TDM Bridge port:

1. Navigate to configure port tdm-bridge <slot>/<port> to select the TDM
bridge port to configure.
The config>port>tdm-bridge>(<slot>/<port>)# prompt is displayed.
port
Binding the serial port to the bind serial <slot>/<port> Serial slot number must be the same as
tdm-bridge port tdm-bridge slot number.
Example
See DS0 Cross-Connect section in Chapter 8, Example 9.
Teleprotection Ports (Logical)
Applicable Modules
Teleprotection ports are available on TP modules. Four cmd-in-i and four cmd-
out-i ports for each of cmd channels 1 and 3 house the logic to manipulate the
logical Rx/Tx information over the corresponding cmd channel. This logic is
capable to perform either basic transparent command cross-connect or logical

(and/or) operation between the external/logical inputs/outputs and

teleprotection information transported over cmd channels.
Automation cmd channels 5 and 6 can be connected to four cmd-out-i ports
each.
See the Teleprotection Modules section in Megaplex-4 I/O Modules Installation
and Operation Manual, Alarm Relay Modules Chapter.
Factory Defaults
The Megaplex-4 is supplied with all teleprotection ports disabled. Cmd in-i ports
have no factory defaults. Cmd-out-i parameter defaults are listed in the table
below.
oos-code The value that will be inserted to the related cmd-out last-valid-state
output when the cmd-channel is in the out-of-service
state
Configuring CMD-IN-I Ports
 To configure the cmd-in internal port parameters:

1. Navigate to configure port cmd-in-i <slot>/<port>/<tributary> to select the
port to configure.
The config>port>cmd-in-i>(<slot>/<port>/<tributary>)# prompt is displayed.

port
to port
Creating a set of ports that trigger-bind < number> cmd-out-i See Command Cross-Connect in
will be trigger sources for <slot/port/tributary> [none | or | Megaplex-4 I/O Modules Installation and
the current port and] Operation Manual, Alarm Relay Modules
trigger-bind < number> cmd-in Chapter, Teleprotection section.
<slot/port> [none | or | and] Using no trigger-bind < number>
removes the set.
“none” is default operator and can be
omitted when only one trigger source is
defined.
When more than one trigger sources are
defined, the operator must be either
“or” or “and” for all trigger sources.

Configuring CMD-OUT-I Ports
 To configure the cmd-out internal port parameters:

1. Navigate to configure port cmd-out-i <slot>/<port>/<tributary> to select the
port to configure.
The config>port>cmd-out-i>(<slot>/<port>/<tributary>)# prompt is displayed.

port
to port
Selecting the value that will oos-code {on | off | off – Cmd-out is forced to off
be inserted to the related last-valid-state} on – Cmd-out is forced to on
cmd-out output when the
last-valid-state – Cmd-out takes the last valid
cmd-channel is in the out-
state value (on or off)
of-service state
Activating remote loopback loopback remote [duration See Testing Teleprotection Ports below
<minutes>]
Viewing Status Information of Logical Teleprotection Ports

For viewing the status of the logical Teleprotection ports, follow the instructions
below.
 To view the status of a cmd-out-i port:

1. Navigate to config>port> cmd-out-i> (<slot>/<port>/<trib>)#
config port cmd-out-i(4/1/1)# show status
Name : IO-4 Cmd out-i 01
Value : 1
Loopback : No Loop
 Value - Command value (0, 1, N/A)
 Whether a remote loopback is active on the port.
 To view the status of a cmd-in-i port:

1. Navigate to config>port> cmd-in-i> (<slot>/<port>/<trib>)#


config port cmd-in-i(4/1/1)# show status
Name : IO-4 Cmd-in-i 01
Value : 1
 Value - Command value (0, 1, N/A).
Testing Teleprotection Ports

The remote digital loopback in the TP module are activated from cmd-out-i ports.
The loopback can be performed independently per each entity.
The remote loopback is a digital loopback performed at the cmd-out-i port, by
returning the received teleprotection signal from the communication network
(cmd-channel) back to the remote RTU. This loopback checks network
connectivity of the remote RTU.
The diagram below shows where the loopback is implemented.
CMD-CH 3/4 CMD-CH 1/2
CMD-OUT-I #4
CMD-OUT-I #3
CMD-OUT-I #2
CMD-OUT-I #1
CMD-OUT-I #4
CMD-OUT-I #3
CMD-OUT-I #2
CMD-OUT-I#1
CMD In #4
CMD In #3
CMD In #2
CMD In #1
CMD Out #1
CMD Out #2
CMD Out #3
or
or
or
or
CMD Out #4
Re
mo
CMD Out #5
te
loo
CMD Out #6
pb
ac
CMD Out #7
k
CMD OUT 1..4 – Primary CMD Out #8
CMD OUT 5..8 - Secondary CMD-IN-I #1

CMD-CH 1/2
CMD-IN-I #2
CMD slot:port CMD-IN-I #3
CMD-IN-I #4
CMD slot:port:tributary
CMD-IN-I #1
CMD-CH 3/4
Logical AND/OR CMD-IN-I #2

CMD-IN-I #3
Selected cross connect CMD-IN-I #4
Primary CMD selection
Figure 6-34. Remote Loopback Functionality inside TP Cross-Connect

Loopback Duration
The activation of a loopback disconnects the remote equipment served by the
Megaplex-4. Therefore, when you initiate a loopback, you have the option to limit
its duration to an interval in the range of 1 through 30 minutes.
activated on the local Megaplex-4 before this timeout expires.
Activating the Loopback
 To perform a loopback on the cmd-out-i port:

1. Navigate to configure port cmd-out-i <slot>/<port>/<trib>.
The config>port> cmd-out-i>(<slot>/<port>/<trib>)# prompt is displayed.
Activating and configuring the loopback remote [duration Returns the received data at the
direction of the loopback <minutes>] physical layer to the transmitting path.
Using no loopback stops the loopback.
Duration –1 to 30 minutes or infinite
VCG Ports
Applicable Modules
Virtually concatenated groups (VCGs) can be configured on the following ports:
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. Ethernet transport over T3 and
Ethernet transport over E1/T1 is done using GFP encapsulation. Megaplex-4 also
supports the Link Capacity Adjustment Scheme (LCAS), covered by ITU-T Rec.
G.7042.
In Megaplex-4, VCGs are protected by the Ethernet group redundancy. For
description and instructions, refer to Ethernet Group Protection in Chapter 7.
Standards
Two types of supported encapsulation comply with the following standards:
• LAPS (Link Access Protocol – SDH) encapsulation in accordance with ITU-T
Rec. X.86

• GFP (Generic Framing Procedure) encapsulation in accordance with ITU-T Rec.

G.7041, using the framed mode.
Benefits
Virtual concatenation has the following main advantages:
• Scalability: allows bandwidth to be selected in relatively small increments, as
required to match the desired payload data rate.
• Efficiency: the resulting signals are easily routed through a SDH/SONET
network, without wasting bandwidth, and therefore allows for more efficient
utilization of the bandwidth available on existing networks.
• Compatibility: virtual concatenation requires only the end nodes to be aware
of the containers being virtually concatenated, and therefore is transparent
to the core network elements.
• Resiliency: individual members of a virtually concatenated group can be freely
routed across the network.
Ethernet over SDH/SONET

To carry Ethernet payload without wasting bandwidth over SDH/SONET link,
Megaplex-4 uses the Virtual Concatenation method. In this method, the
contiguous bandwidth of the payload signal is divided into several streams, each
having the rate necessary for insertion into individual VCs (SDH) or SPEs (SONET).
With virtual concatenation, the individual VCs or SPEs are transported over the
SDH or SONET network in the usual way, and then recombined to restore the
original payload signal at the end point of the transmission path, using a
technology similar to inverse multiplexing.
The processing is as follows:
1. At the source end, the inverse multiplexing subsystem splits the payload
signal into several streams at a rate suitable for transmission over the desired
type of VC (VC-12, VC-3 or VC-4) or SPE. The required information (type and
number of VCs or SPEs) are defined when the virtually concatenated group
(VCG) is defined.
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.
Encapsulation Modes
Ethernet frames must be encapsulated before transport over the SDH/SONET
network. You can select the desired encapsulation mode, independently, for each
virtually concatenated group. This can be done by binding VCG ports to the
corresponding entity:
• For LAPS encapsulation, see Configuring HDLC Ports.
• For GFP encapsulation, see Configuring GFP Ports.
Support for LCAS

Each virtually concatenated group with two or more VCs/VTs can be configured to
support LCAS.
With LCAS, the capacity of a virtually concatenated group can be hitlessly
decreased when one of the VCs/VTs fails; when the failure is no longer present,
the group will automatically and hitlessly recover to return to the normal capacity.
Another LCAS advantage is that it allows setting up a link even when the number
of VCs/VTs at the two endpoints, or anywhere along the trail followed by the VCG,
is not equal.
The user can specify a minimum number of VCs/VTs for the group capacity: if the
number of VCs/VTs decreases below this minimum, an alarm will be generated.
Ethernet over Full/Channelized T3

T3 modules allow encapsulating Ethernet traffic with the GFP protocol and
transferring it over full or channelized T3 media. In both cases Ethernet ports are
connected to Logical MAC ports via flows, and these Logical MAC ports are bound
to GFP ports. Starting from the GFP ports, two ways are available:
• To transfer Ethernet over full T3, only one GFP/Logical MAC port is created
and T3 port is bound directly to it.
• To transfer Ethernet over channelized T3, up to 16 Logical MAC, GFP and VCG
ports are created, so that the VCG ports are bound to GFP ports and VCG
ports are bound to Logical MAC ports. Up to 16 T1 ports can be bound to
each VCG port, but the total T1 number is limited by 28 T1 ports per T3
module. On the remaining T1s, regular TDM traffic can be mapped.
over T3/T1 functionality.

Flow
Egress/Ingress Port

ETH Group 1 16
Bind 1:1 Bind 1:1
GFP 1 GFP 16
OR
Bind 1:1
VCG 1..16
Bind 1:1
Bind 1:n
T1 T3
Figure 6-35. Logical Entities Representing Ethernet Traffic over Full/Channelized T3 Media
Ethernet over E1/T1

VS-16E1T1-EoP modules allow encapsulating Ethernet traffic with the GFP
protocol and transferring it over E1/T1 media. Ethernet ports are connected to
Logical MAC ports via flows, these Logical MAC ports are bound to GFP ports and
GFP ports are bound to VCG ports. Up to 16 E1/T1 or E1-i/T1-i ports can be
bound to each VCG port.
over E1/T1 functionality.

Flow
Egress/Ingress Port

ETH Group 1 16
Bind 1:1 Bind 1:1
GFP 1 GFP 16
Bind 1:1 Bind 1:1
VCG 1 VCG 16
OR
Bind 1:n Bind 1:n
E1/T1 E1-i/T1-i
Figure 6-36. Logical Entities Representing Ethernet Traffic over E1/T1 Media
Factory Defaults
Megaplex-4 is supplied with all VCG ports disabled.
Configuring VCG Ports
 To configure a VCG:
• At the config>port>vcg (slot/port)# prompt, enter all necessary commands
according to the tasks listed below:
Assigning short description to a name <string> Using no name removes the name
VCG port

Administratively enabling a VCG no shutdown Using shutdown disables the VCG port
port
Binding the corresponding bind vc4-sts3c For the allowed ranges, seeTable 6-66.
VC/VT/STS-1 to the VCG port <slot>/<port>/<tributary> The connection to a VC or VT/STS
bind vc3-sts1 depends on the frame selection
<slot>/<port>/<au4>/ (frame=sdh or frame=sonet)
<tributary>
bind vc-vt <slot>/<port>/
<au4>/<tug_3>/<tug_2>
[/<tributary>] The maximum number of VC-4/STS-3C
containers per system is limited to the
full STM-4/OC-3 capacity of a single CL.2
module.
The maximum number of vc-vt containers
for EoS per CL module is limited to 128.
Binding the T1 internal port of bind t1 The maximum number of T1 ports bound
the T3 module to the VCG port <slot>/1/<tributary t1> to one VCG port is 16.
Binding the E1/T1 external and bind t1 <slot>/<port> The maximum number of E1/T1 or
internal ports of the VS-16E1T1- bind t1-i <slot>/<port> E1-i/T1-i ports bound to one VCG port is
EoP module to the VCG port 16.
bind e1 <slot>/<port>
Ports bound to VCG must be defined on
bind e1-i <slot>/<port>
same slot as this VCG port.
The ports bound to a specific VCG must
belong to the same type (no mix is
allowed between e1 and e1-i ports or t1
and t1-I ports).
Enabling the use of the Link lcas LCAS is relevant only when the group
Capacity Adjustment Scheme includes 2 or more VCs/T1s. Therefore for
(LCAS) on the corresponding VC-4 (STS-3c) binding it is relevant only
group when STM-4/OC-12 ports are configured
Using no lcas disables the use of LCAS
Selecting the minimum allowed minimum-number-of-links This parameter is relevant only when
number of operational <value> LCAS is enabled.
VC/VT/STS/T1s that must remain
in operation. If the number
decreases below the selected
value, an alarm is generated.
Selecting the maximum max-differential-delay The range is 1 to 256 (in msec)

differential delay (delay <value> Default: 64 msec
compensation needed for
For optimal latency performance of the
alignment of low- and
ETHoSDH services, it is recommended to
high-order virtually concatenated
set low values of max-differential-delay
payloads in the SONET/SDH
(the minimum value needed for your
network)
application).

Viewing LCAS Status Information

For viewing the LCAS status information, follow the instructions below.
 To view the LCAS status information:

1. Navigate to config>port>vcg> (<slot>/<port>)#
The status is displayed.
Example for SDH/SONET:
mp4100>config>port>vcg(cl-a/2)# show status
Name : CL-A vcg 02
LCAS Status : All Normal
Members
---------------------------------------------------------------
Link : cl-a/2/1/1/1/2
Source Status : Norm
Sink Status : Norm
Status : OK
Link : cl-a/2/1/1/1/3
Sink Status : Norm
Status : OK
Link : cl-a/2/1/2/2/3
Sink Status : Norm
Status : OK
Link : cl-a/2/1/3/5/1
Sink Status : Norm
Status : OK
Link : cl-a/1/2/1/2/1
Sink Status : Norm
Status : OK
Link : cl-a/1/2/2/3/1
Sink Status : Norm
Status : OK
Link : cl-a/1/2/2/5/1
Source Status : EOS
Sink Status : EOS
Status : OK
Example for T3:
mp4100>config>port>vcg(3/1)# show status
Name : IO-3 vcg 01
LCAS Status : All Normal

Members
-----------------------------------------------------------------
Link : 3/1/3
Sink Status : Norm
Status : OK
Link : 3/1/4
Sink Status : Norm
Status : OK
Link : 3/1/5
Sink Status : Norm
Status : OK
Link : 3/1/6
Source Status : EOS
Sink Status : EOS
Status : OK
The parameters displayed in the screen are as follows:
Administrative Displays the administrative status of the corresponding VC/VT or T1 link:

Status Up or Down
Operation Status Displays the operation status of the corresponding VC/VT or T1 link: Up or
Down
LCAS Status Displays the LCAS status of the corresponding VC/VT or T1 link:
• All Normal –all T1/VC/VT ports bound to the selected VCG are active
• Within Range –number of active T1/VC/VT ports bound to the selected
VCG is not below the value set by the “minimum-number-of-links”
parameter
• Below Min No of VC –number of active T1/VC/VT ports bound to
the selected VCG and active is below the value set by the “minimum-
number-of-links” parameter
Link SDH/SONET: Identifies the position of the corresponding VC or VT within

the STM-1/STM-4 or OC-3/OC-12 frame, using the vc4-sts3c/
tug-3/tug-2/tu format. The Link number also includes the identification of
the link, cl-a/1, cl-a/2, cl-b/1 or cl-b/2.
T3: Identifies the position of the corresponding T1 within the T3 frame,
using the <slot>/1/<t1 tributary> format.

Source Status Displays the state of the corresponding VC/VT (SDH/SONET) or T1 (T3
module) on the local end of the path serving the selected VCG (that is, the
end located on the Megaplex-4 to which the supervisory terminal is
connected):
• Fixed – the end uses the fixed bandwidth (not LCAS)
• Add – the corresponding VC/VT or T1 is about to be added to the VCG
• Norm – normal transmission state
• EOS – end-of-sequence indication
• Idle – the corresponding VC/VT or T1 is not part of the VCG, or is about
to be removed from the group
• DNU – do not use the corresponding VC/VT or T1, 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-4.
Sink Status Same as above for the sink side (remote end of the path).
Status Displays the member status of the corresponding VC/VT or T1 link: OK or

Failed
Displaying LCAS Statistics

VCG ports feature the collection of LCAS statistical diagnostics.
 To display the LCAS statistics:

• At the prompt config>slot>port>vcg (<slot><port>)#, enter show statistics
statistics

LCAS statistics are displayed. The counters are described in the table
below. For example:
Current Statistics (SDH/SONET):
mp4100>config>port>vcg(cl-a/2)# show statistics current
Current
-----------------------------------------------------------------
Valid Intervals : 3
Number of Active VCs/VTs : 4
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0

Current Statistics (T3):

mp4100>config>port>vcg(3/1)# show statistics current
Current
-----------------------------------------------------------------
Number of Active Links : 4
Maximum Number of Active Links : 4
Minimum Number of Active Links : 0
Statistics for interval 2 (SDH/SONET):
mp4100>config>port>vcg(cl-a/2)# show statistics interval 2
Interval
-----------------------------------------------------------------
Interval Number : 2
Maximum Number of Active VCs/VTs : 4
Minimum Number of Active VCs/VTs : 0
Under Minimum Limit Time : 0
Statistics for interval 2 (T3):
mp4100>config>port>vcg(3/1)# show statistics interval 2
Interval
-----------------------------------------------------------------
Interval Number : 2
Maximum Number of Active Links : 4
Minimum Number of Active Links : 0
Under Minimum Limit Time : 0
Table 6-73. LCAS Statistics Parameters

Number of Active Displays the current number of active VCs/VTs (for SDH/SONET) or T1 links
VCs/VTs/Links (Current (for T3 modules) reported for the corresponding VCG
statistics only)
Maximum Number of Active Displays the maximum number of active VCs/VTs(for SDH/SONET) or T1 links
VCs/VTs/Links (for T3 modules) reported for the corresponding VCG during the selected
interval
Minimum Number of Active Displays the minimum number of active VCs/VTs(for SDH/SONET) or T1 links
VCs/VTs/Links (for T3 modules) reported for the corresponding VCG during the selected
interval
Under Minimum Limit Time Displays the accumulated time, in seconds, during which the number of
(Selected interval statistics active VCs/VTs (for SDH/SONET) or T1 links (for T3 modules) for the
only) corresponding VCG has been less than the configured minimum allowed
number

Clearing Statistics
There are two options for clearing LCAS statistics data:


Chapter 7
Resiliency
The modular, distributed architecture of Megaplex-4 enables redundancy at
different levels of the network and provides a resilient system with no single
point of failure. Hardware redundancy is provided through an optional redundant
power supply and CL modules, with switchover to the backup CL links within
50 msec.
Each combined common logic, cross-connect matrix and broadband link module
(CL) provide automatic switchover between each two STM-1/STM-4/OC-3/OC-12
links within 50 msec, for 1+1 protection against hardware, network or cable
failure. The SDH/SONET employs APS 1+1 protection as well as Subnetwork
connection protection (SNCP for SDH and UPSR for SONET) for path protection.
The Ethernet traffic is protected by a G.8032 Layer-2 Ethernet ring. This
technology builds a logical ring, defined as a set of IEEE 802.1-compliant bridges,
and protects against link and node failures. Megaplex-4 supports 5 rings per
chassis.
The Ethernet GbE ports also feature LAG- and VCG-based link protection
mechanism over SDH/SONET. In addition, any E1/T1 stream can be protected
using various mechanisms over any interface.
Selected I/O modules can also be configured for redundancy and can be
hot-swapped, allowing for continuous service. In addition to supporting standard
SDH/SONET rings, Megaplex-4 can be used to create E1, T1, TDM over fiber, or a
mix of ring topologies.
External and internal E1/T1 links feature the TDM group and TDM ring protection
on the port level. In addition, M8E1/M8T1 and M16T1 modules support the I/O
group protection on the module level, which is hardware type redundancy
established between two identical modules installed in the same Megaplex
chassis and connected by a Y-cable. These three types of protection are
described in the following sections.
The following tables show the protection features supported by each I/O module
on the port level. The hierarchical position of e1/t1 and e1-i/t1-i ports is slot:port
for all the modules, with the exception of the OP-108C and OP-34C Megaplex
cards, where it is slot:port:tributary (in these modules slot:port=mux_eth_tdm).
In addition, Optimux, TP and T3 modules feature TDM group protection on their
mux-eth-tdm, cmd-channel and t3 ports, respectively.
MPW-1 and VS modules provide TDM group protection on their DS1 ports. In
addition, VS modules feature PW protection.
Megaplex-4 Fault Propagation 7-1

Chapter 7 Resiliency Installation and Operation Manual
Table 7-1. TDM Protection on E1/T1 Ports
E1/T1 Ports (e1/t1)

Protection
type M8E1 M16E1 OP-108C OP-108C/E1 OP-34C ASMi-54C/N
M8T1 M16T1 (E1 only)
dual-cable-tx √ √(1) √(1) – √(1) √(1)
tdm-ring √ √ √ – √ √
1 – Not available for Transparent E1/T1 over SDH/SONET
Table 7-2. TDM Protection on E1-i/T1-i and DS1 Ports
Internal E1/T1 Ports (e1-i/t1-i) Internal DS1 Ports (ds1)

Protection type
CL.2 M8SL (E1 only) ASMi-54C/N (E1 only) MPW-1, VS
dual-cable-tx √ √ √(1) √
tdm-ring – √(2) √ –
1 - Not available for Transparent E1/T1 over SDH/SONET
7.1 Fault Propagation

The fault propagation function can be used to notify equipment at a far end port
that a fault condition has been detected at a local port connected to it.
Fault propagation is supported for compatible types of ports, for example:
• Between interconnected external E1/T1, internal E1-i/T1-i or PW ports
• Between the Ethernet, PCS, GFP or MLPPP ports.
For each port type, Table 7-3 lists the following:
• Failure or alarm conditions at this (failed) port used to initiate a response at
another (affected) port
• Response (action) at this port when it is affected (“to” port in CLI).
Table 7-3. Fault Propagation Response
Port Type Detected Failure or Alarm Condition Action at the Port when it is
Affected
GbE • “eth – los” alarm Disconnecting GbE port

• “card – card_mismatch” alarm (module
removed)
7-2 Fault Propagation Megaplex-4

Installation and Operation Manual Chapter 7 Resiliency
Affected
External Fast • “eth – los” alarm Disconnecting the Ethernet port

Ethernet (I/O • “card – card_mismatch” alarm (module
modules) removed)
Internal Ethernet • “mux-eth-tdm – los” alarm Disconnecting user Ethernet port of the
(MP Optimux • “card – card_mismatch” alarm (module remote standalone device
modules) removed)
GFP • With LCAS: “vcg –minimum members tca” CSF(Client Signal Failure) frame will be
alarm sent instead of idle GFP frames on the
• Without LCAS: “gfp – rx_trail_failure” associated VCGs
alarm
• “gfp – csf” alarm
removed)
MLPPP • “ppp – bcp_failure” alarm MLPPP port is down (BCP down)

removed)
PCS • “shdsl – lof” alarm N/A (can only affect other ports)
• “shdsl – losw” alarm
removed)
PW • “pw –pw_configuration_mismatch” alarm Sending of OAM packets with Local Fail

• “pw –pw_oam_failure” alarm indication (L-bit set) to remote PW
Note: OAM must be enabled.
• “pw – fe_rdi” alarm
• “pw –rx_failure” alarm
• “pw –fe_rx_failure” alarm
removed)
E1-i/T1-i • “e1t1 – ais” alarm Sending of AIS

(CL.2 module) • “e1t1 – lof” alarm
• “e1t1 – rai” alarm
• “e1t1 – lomf” alarm
• “e1t1 – lomf_fe” alarm
• “e1t1 – los” alarm
removed)

Affected
E1-i (M8SL, SH-16 • “e1t1 – ais” alarm N/A (can only affect other ports)
modules) • “e1t1 – lof” alarm
removed)
E1-i/T1-i • “e1t1 – ais” alarm Unframed AIS is generated

(VS-16E1T1-EoP • “e1t1 – lof” alarm
module)
removed)
E1/T1 ports • “e1t1 – ais” alarm Sending of AIS

(M8E1/M8T1, • “e1t1 – lof” alarm
M16E1/M16T1)
removed)
E1/T1 ports • “e1t1 – ais” alarm Unframed AIS is generated

(VS-16E1T1-EoP, • “e1t1 – lof” alarm
VS-16E1T1-PW,
VS-6/E1T1
modules) • “e1t1 – lomf” alarm
removed)
Internal E1/T1 • “e1t1 – ais” alarm Sending of AIS by the associated E1

ports (MP Optimux • “e1t1 – lof” alarm port of the remote standalone device
modules)
• “mux-eth-tdm – los” alarm
removed)

Affected
C37.94 • “e1t1 – ais” alarm AIS shall be generated

• “e1t1 – lof” alarm
removed)
Internal T1 ports • “e1t1 – ais” alarm AIS shall be generated

(T3 module) • “e1t1 – lof” alarm
removed)
Factory Defaults
By default, fault propagation is not configured.
Configuring Fault Propagation

Follow this procedure to configure fault propagation:
 To add fault propagation for a pair of interfaces:

1. Navigate to configure fault.
2. Type the command:
fault-propagation <from-interface> to <to-interface>, as shown in
Table 7-4.
The fault propagation in the “to” direction is established.
Table 7-4. Fault Propagation
Configuring fault fault-propagation port {e1 | t1 | e1-i | Optional <tributary> index refers only to
propagation for t1-i | ds1-opt | pw} e1 ports of Megaplex Optimux cards
external/internal e1/ <slot>/<port>/[<tributary>] (OP-34C, OP-108C) and t1 ports of T3
t1 ports and to port {e1 | t1 | e1-i | t1-i | ds1-opt | cards.
pseudowires pw} <slot>/<port>/[<tributary>] In the case of a PW participating in the
fault propagation, <slot>/<port>/
[<tributary>] on the corresponding side
must be replaced by <pw number>.
Using no before fault-propagation disables
the command.

Configuring fault fault-propagation port {ethernet | pcs | Optional <tributary> index refers only to
propagation for gfp | mlppp | pw } ethernet ports of Megaplex Optimux cards
ethernet type ports <slot>/<port>/[<tributary>] (OP-34C, OP-108C)
and pseudowires to port {ethernet | gfp | mlppp | pw } In the case of a PW participating in the
<slot>/<port>/[<tributary>] fault propagation, <slot>/<port>/
[<tributary>] on the corresponding side
must be replaced by <pw number>.
The PCS port can be on the “from” side
only.
Using no before the full command disables
the command.
When configuring fault propagation, the following must be taken into account:
• The maximum number of affected ports defined per one failed port is 10
• In bidirectional fault propagation, one failed port corresponds to one affected
port and vice versa
• The maximum number of fault propagation entries defined in the system is
200
• Neither failed nor affected E1/T1/E1-i/T1-i port can be configured
as unframed
• An E1/T1/E1-i/T1-i port defined as protection in a TDM protection group
cannot be selected by the user as failed or affected.
• If a working port in a TDM protection group is selected as failed or affected,
the protection port is internally added to the fault propagation configuration.
In particular:
 If a working port of a TDM group is selected as failed, the port selected
as affected responds only if both working and protection ports fail
 If a working port of a TDM group is selected as affected, both working
and protection ports will be affected by the failed port.
error is detected.
631 Error FP PORT IS IN SHUTDOWN The port configured for fault propagation is in shutdown
STATE state and the other one is set to no shutdown. Both ports
must be set either to shutdown or to no shutdown.
632 Error FP PORT CAN'T AFFECT ITSELF The same port cannot be failed and affected at the same
time.

633 Error UNFRAMED PORT CAN'T Neither failed nor affected E1/T1/E1-i/T1-i/DS-1 port can
PARTICIPATE IN FP be configured as unframed.
634 Error UP TO 200 FP ENTRIES CAN BE The maximum number of fault propagation entries has
CONFIGURED been exceeded
635 Error FP AFFECTED PORT IS USED A port cannot be defined as affected by more than one
MORE THAN ONCE failed port
636 Error FAILED PORT CAN AFFECT UP The maximum number of affected ports per one failed
TO 10 PORTS port has been exceeded
637 Error ASYMMETRIC BI DIR FP In bidirectional fault propagation, one failed port must
CONFIGURATION correspond to one affected port, and vice versa
638 Error PROTECTED PORT CAN'T BE A port defined as protection in a protection group cannot
CONFIGURED IN FP be selected by user as failed or affected. If a working port
is selected as failed or affected, the protection port is
internally added to the fault propagation configuration.
639 Error FP FAILED PORT IS NOT The failed port configured is not supported by Fault
SUPPORTED Propagation process
640 Error FP AFFECTED PORT IS NOT The affected port configured is not supported by Fault
SUPPORTED Propagation process
7.2 APS Protection

Two SDH/SONET ports can work in APS (Automatic Protection Switching) mode.
The APS configuration allows you to specify the two working ports and their
operational mode, which can comply with one of the standards quoted below.
Standards
Automatic Protection Switching complies with the following standards:
• 1+1 unidirectional APS (G.842, Clause 7.1.4.4)
• 1+1 bidirectional compatible APS (G.841, Clause 7.1).
• 1+1 bidirectional optimized APS (G.841 Annex B. Linear Multiplex Section
(MSP); compatible with 1:1 bidirectional switching)
Benefits
APS switches over traffic with minimal loss of data, thus avoiding time-consuming
reroutes. With APS, there is no indication beyond the affected network element
that a failure has occurred; other nodes stay intact. SDH/SONET APS performs
switchovers at Layer 1 significantly faster than at Layer 2 or Layer 3. The effect
of a failure is greatly minimized, and a fast switchover guarantees minimal effect
on the network.
Megaplex-4 APS Protection 7-7

Automatic protection switching (APS) is a link-level protection mechanism for
ensuring service continuity in the case of interface failure/error.
In Megaplex-4, the APS can be configured with the following operating modes:
• 1+1 optimized bi-directional mode. You specify two working ports, 1 and 2,
and bind one of the four ports available on CL.2 module (sdh-sonet cl-a/1,
cl-a/2, cl-b/1, cl-b/2) to working port 1 and another one to working port 2
respectively. The protocol used to handle the switching is carried out using
K1 and K2 bytes from the line header of the SONET/SDH frame.
• 1+1 compatible bi-directional mode. You specify a working port and a
protection port. Bind one of the four ports available on CL.2 module (sdh-
sonet cl-a/1, cl-a/2, cl-b/1, cl-b/2) to the working port and another one to
the protection port respectively. The protocol used to handle the switching is
carried out using K1 and K2 bytes from the line header of the SONET/SDH
frame.
• 1+1 unidirectional mode. You specify a working port and a protection port.
Bind one of the four ports available on CL.2 module (sdh-sonet cl-a/1, cl-a/2,
cl-b/1, cl-b/2) to the working port and another one to the protection port
respectively. The protocol used to handle the switching is carried out using
SDH/SONET alarms.
The alarm criteria taken into consideration for protection switching are grouped
into two categories: major alarm and minor alarm.
The major alarms are caused by any of the following:
• An SFP is removed from the socket
• Loss of SDH/SONET line signal is detected
• Loss of SDH/SONET frame is reported
• AIS signal is received on the line
• OOS condition is reported.
The minor alarms are caused by the following:
• EED (excessive error degradation). The EED threshold can be selected by the
user.
• SD (signal degraded) condition, where the threshold can be selected by the
user. However, the user can configure APS parameters to ignore the SD
criterion.
• Forced-flip command.
The working port always carries the traffic, as long as its total alarm weight does
not exceed that of the protection. The user can force switching (flipping) to the
other port by a manual flip command.
The two ports in an APS group can be assigned priorities. Megaplex-4 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.
7-8 APS Protection Megaplex-4

The recovery mode after a protection switching can be selected in accordance

with the application requirements:
• Non-revertive mode – the CL module will not automatically flip back after the
failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
However, as explained above, the user can always initiate flipping back by a
manual flip command.
• Revertive mode – the CL module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
To prevent switching under marginal conditions, the user can specify a
restoration time (wait-to-restore). This is the minimum interval before flipping
back to the original port. During the restoration time, alarms with the same
weight, or with lower weights, are ignored. As a result, the module starts
evaluating the criteria for protection switching (flipping) only after the
restoration time expires, thereby ensuring that another flip cannot occur before
the specified time expires.
However, if an alarm with a weight exceeding that of the alarm which caused
flipping appears, immediate flipping will occur, even if the restoration time has
not yet expired.
Factory Defaults
In Revertive mode, the wait-to-restore time is 300 sec.
Configuring Automatic Protection Switching
Adding and Removing an APS Group
 To add and define an APS group:

1. At the config> prompt, enter protection.
The config>protection# prompt appears.
2. Enter aps <group name>. The group name may consist of up to 80
alphanumeric characters.
The APS group is defined and enabled and the
config>protection>aps(<group name>)# prompt appears.
 To remove an APS group:

• At the config>protection# prompt, enter no aps <group name>.
The APS group is removed.
Binding Ports to an APS Group

Before you can bind ports to the APS group, you have to first specify the desired
operation mode.

 To specify the operation mode:

• At the config>protection>aps(<group name>)# prompt, enter
oper-mode {uni-directional | optimized-1-plus-1 | compatible-1-plus-1}.
You are now able to bind a port to the APS group.
 To define the working ports for the APS group if ‘optimized-1-plus-1’ is selected:
1. At the config>protection>aps <group name># prompt, enter
bind working 1 sdh-sonet <slot><port>.
Working port 1 is bound to the APS group.
bind working 2 sdh-sonet <slot><port>.
Working port 2 is bound to the APS group.
 To bind the working and protecting ports to the APS group if ‘compatible-1-plus-1’
or ‘uni-directional’ is selected:
bind working sdh-sonet <slot><port>.
The working port is bound to the APS group.
bind protection sdh-sonet <slot><port>.
The protection port is bound to the APS group.
 To configure the SDH/SONET APS:

• At the config>protection>aps(group name)# prompt, enter all necessary
commands according to the tasks listed below:
Activating the APS group no shutdown Using shutdown switches the

APS to standby mode
Defining operation mode of the oper-mode {uni-

APS directional | optimized-
1-plus-1 | compatible-1-
plus-1}
Adding a working port to the APS bind { working | Available for the compatible 1+1 and
group (compatible 1+1 and protection } sdh-sonet unidirectional modes
unidirectional modes) <slot/port> Using no bind { working | protection }
removes a port from APS group
Adding a working port to the APS bind working {1 | 2} sdh Available for the 1+1 optimized bi-
group (1+1 optimized bidirectional -sonet <slot/port> directional mode.
mode) Using no bind { working | protection }
removes a port from APS group
7-10 APS Protection Megaplex-4

Enabling the reverting of the revertive Using no revertive disables the reverting
working and protection ports (not
available in 1+1 optimized mode)
Defining the wait-to-restore wait-to-restore <1– The unit of time is seconds

period for the revertive recovery 720>
mode (the time to elapse
after the link recovery
before traffic switches back)
Enabling the flip of the two flip-upon-sd Using no flip-upon-sd disables the flip
SDH/SONET ports upon signal
degradation
Denying access of all traffic lockout-of-protection Available only in compatible 1+1 and
signals to the protection port by unidirectional modes
issuing a "Lockout of protection"
request, unless an equal
protection switch command is in
effect
Clears all externally initiated clear

switch commands and the WTR
time
Forced switching of traffic from force-switch-to-working Since a forced switch has a higher priority
the protection port to the working than SF or SD on a working port, this
port (unless an equal or higher command is carried out regardless of the
priority request has been issued) current condition of the working port
Forced switching of traffic from force-switch-to-

the working port to the protection protection
port, unless an equal or higher
priority switch command is in
effect, or if an SF condition exists
on the protection port.
Manual switching of traffic from manual-switch-to- Since a manual switch has lower priority
the protection port back to the working than SF or SD on a working port, this
working port, unless an equal or command is carried out only if the working
higher priority request is in effect port is not in SF or SD condition.
Forced switching of traffic from manual-switch-to-

the working port to the protection protection
port, unless a failure condition
exists on the protection port or
an equal/higher priority switch
command is in effect
Viewing the Status of an APS Group

This section illustrates the status display of an APS group created in
1+1 Optimized Bi-directional mode.

 To view the APS group’s status:

• At the config>protection>aps(<group name>)# prompt, enter show status.
The APS group’s status appears.
 In this example, the APS group name is test.
mp4100>config>protection>aps(test)# show status
Group
---------------------------------------------------------------
Mode : Uni Directional
Current Working : cl-b/1
Rx K1K2 : 0x0010
Tx K1K2 : 0x0010
Ports
---------------------------------------------------------------
Port Admin Status Active
cl-a/1 Up Up No
cl-b/1 Up Up Yes
Example
 To add and configure an APS group:
• APS group name – test
• Working port – Port 2 of the module installed in slot cl-a
• Protection port – Port 1 of the module installed in slot cl-a
• Recovery mode – revertive
• Wait-to-restore period – 200 seconds.
mp4100#configure protection aps test bind working sdh-sonet cl-a/2
mp4100>config>protection>aps(test)#bind protection sdh-sonet cl-a/1
mp4100>config>protection>aps(test)#revertive
mp4100>config>protection>aps(test)#wait-to-restore 200
 To delete APS group named test:

mp4100#configure protection no aps test
7.3 Ethernet Group Protection

Megaplex-4 supports 1+1 protection (redundancy) for Ethernet, protecting
Ethernet and packet traffic against transmission failures on the SDH/SONET, T3 and
E1/T1 links.
7-12 Ethernet Group Protection Megaplex-4

Applicable Modules
This feature is available for the following modules and technologies:
• E1/T1 and fractional E1/T1 (M8E1, M8T1 modules)
Note Ethernet Group Protection is not supported in CL.2/A modules.
Standards
Ethernet group protection is RAD proprietary technology.
Any pair of logical MACs can be configured as an Ethernet protection group, even
if the entities bound to them have different capacity, different encapsulation
methods, and/or different parameters. Only the wait-to-restore delay must be
the same.
To use Ethernet group protection, both the primary (working) logical MAC and the
secondary (protection) logical MAC must be assigned bandwidth (mapped) on the
particular links. In other words, the lower-hierarchy entities on these desired links
must be bound to this logical MAC. Provisioning appropriate trails through the
network ensures that in case of a fault anywhere along the primary group path,
its traffic will be automatically switched to the standby group and will follow a
different path through the SDH/SONET/T3/E1/T1 network, thereby ensuring that
the payload can still be transported end-to-end.
Depending on the desired protection level, the protection partners can be
mapped to different links on the same modules, or to links on the different
modules.
The Ethernet group protection mode is always 1+1 and operates as follows:
• During normal operation, the payload is directed to the primary logical MAC,
and transmitted only over the bandwidth assigned to this group.
Note Only the primary (working) logical MAC can be included in a flow. The protection
logical MAC will not appear in the list of available bridge ports.
• If an alarm condition is detected on the entities bound to the working logical

MAC, the payload is directed to the protection logical MAC, and transmitted
over its bandwidth. The alarm criteria taken into consideration for protection
switching include physical port failures and VCG failures. When using LCAS,
this also includes a decrease in available bandwidth below the specified
minimum.
The recovery mode after a redundancy switching is always revertive – which
means that the traffic will be automatically redirected back to the original group
when it returns to normal operation.
Megaplex-4 Ethernet Group Protection 7-13

To prevent switching under marginal conditions, the user can specify a wait-to-
restore time, which is the minimum interval before flipping back to the original
port. However, if a more severe alarm appears, immediate flipping will take place,
even if the wait-to-restore time has not yet expired.
Figure 7-1, Figure 7-2, Figure 7-3 and Figure 7-4 illustrate how Ethernet groups
are bound to the physical layer for Ethernet over SDH/SONET, Ethernet over T3
and Ethernet over E1/T1, respectively.
Flow
Egress/Ingress Port

ETH Group 1 32
OR
Bind 1:1
GFP 1..32 HDLC 1..32
OR
Bind 1:1
VCG
Bind 1:1
1..32
Bind 1:n
VCAT No
VC4-4C/
VC4/STS-3C VC3/STS-1 VC12/VT1.5
STS-12C
Figure 7-1. Ethernet Group Protection over SDH/SONET

Flow
Egress/Ingress Port

ETH Group 1 16
Bind 1:1 Bind 1:1
GFP 1 GFP 16
OR
Bind 1:1
VCG 1..16
Bind 1:1
Bind 1:n
T1 T3
Figure 7-2. Ethernet Group Protection over T3
Flow
Egress/Ingress Port

ETH Group 1 320
Bind 1:1
HDLC
slot#/1..32
Bind 1:n
TS 1..31
Figure 7-3. Ethernet Group Protection over E1/T1 (M8E1/M8T1 Modules)

Flow
Egress/Ingress Port

ETH Group 1 16
Bind 1:1 Bind 1:1
GFP 1 GFP 16
Bind 1:1 Bind 1:1
VCG 1 VCG 16
OR
Bind 1:n Bind 1:n
E1/T1 E1-i/T1-i
Figure 7-4. Ethernet Group Protection over E1/T1 (VS-16E1T1-EoP Modules)
Configuring Ethernet Protection Group
Adding and Removing an Ethernet Protection Group
 To add and define an Ethernet protection group:

2. Enter ethernet-group <group number>.
The Ethernet protection group is defined and enabled and the
config>protection>ethernet-group( <group number>)# prompt appears.
 To remove an Ethernet protection group:

• At the config>protection prompt, enter no ethernet-group <group number>.
The Ethernet protection group is removed.

Binding Ports to an Ethernet Protection Group
 To configure the Ethernet group protection:

• At the config>protection>ethernet-group(group number)# prompt, enter all
necessary commands according to the tasks listed below:
Activating the Ethernet protection no shutdown Using shutdown switches the

group Ethernet protection group to standby
mode
Adding a working/protection port bind {working | protection} Using no bind logical-mac

to the Ethernet protection group logical-mac <slot>/<port > <slot>/<port> removes a port from
Ethernet protection group
Port number is as follows:
• 1..32 for SDH/SONET
• 1..16 for T3 modules
• 1.. 32 for M8E1/M8T1 modules
• 1..16 for VS-16E1T1-EoP modules.
If TDM group protection is configured
for a T3 port, the Ethernet group
protection is also automatically
created on all the open Logical MAC
ports belonging to this T3 module.
The Logical MAC members belonging
to such a group have the same
numbers. The numbers of these
Ethernet protection groups start from
200.
Specifying a wait-to-restore wait-to-restore <time in 1..300..720

timeout in seconds seconds> If this Ethernet protection group is
automatically created upon
configuring TDM group protection in a
T3 module, its wait-to-restore value
is the same as for the TDM group
protection configured on the T3
module.
Example
 To add and configure an Ethernet protection group 2:
• M8E1 modules installed in slot 5
• Ethernet protection group number – 2
• Configure SDH ports cl-a/2 and cl-b/2
• Configure vcg cl-a/2 and bind vc-vt cl-a/2/1/1/1/1 to it
• Configure gfp cl-a/2 and bind vcg cl-a/2 to it (GFP encapsulation of this VCG)

• Configuring logical-mac cl-a/2 and bind gfp cl-a/2 to it

• Same on cl-b/2
• Configure flows (13) and (14) between logical-mac cl-a/2 and Ethernet port
5/2
• Set ethernet group 2 with logical-mac cl-b/2 as protection port for logical-
mac cl-a/2. Now flows (13 and (14) are protected
• Wait-to-restore time = 2 sec
mp4100# config slot cl-a card-type cl cl2-622gbe
mp4100# config slot cl-b card-type cl cl2-622gbe
mp4100# config slot 5 card e1-t1 m8e1
mp4100# config port eth 5/2 no shutdown
mp4100#
mp4100# exit all
mp4100# configure
mp4100>config# port
mp4100>config>port# sdh-sonet cl-a/2
mp4100>config>port>sdh-sonet(cl-a/2)# no shutdown
mp4100>config>port>sdh-sonet(cl-a/2)# speed 622mbps
mp4100>config>port>sdh-sonet(cl-a/2)# exit
mp4100>config>port#
mp4100>config>port# sdh-sonet cl-b/2
mp4100>config>port>sdh-sonet(cl-b/2)# no shutdown
mp4100>config>port>sdh-sonet(cl-b/2)# speed 622mbps
mp4100>config>port>sdh-sonet(cl-b/2)# exit
mp4100>config>port#
mp4100>config>port# vcg cl-a/2
mp4100>config>port>vcg(cl-a/2)$ bind vc-vt cl-a/2/1/1/1/1
mp4100>config>port>vcg(cl-a/2)$ no shutdown
mp4100>config>port>vcg(cl-a/2)$ exit
mp4100>config>port#
mp4100>config>port# gfp cl-a/2
mp4100>config>port>gfp(cl-a/2)$ bind vcg cl-a/2
mp4100>config>port>gfp(cl-a/2)$ no shutdown
mp4100>config>port>gfp(cl-a/2)$ exit
mp4100>config>port#
mp4100>config>port# logical-mac cl-a/2
mp4100>config>port>log-mac(cl-a/2)$ bind gfp cl-a/2
mp4100>config>port>log-mac(cl-a/2)$ no shutdown
mp4100>config>port>log-mac(cl-a/2)$
mp4100>config>port>log-mac(cl-a/2)$ exit all
mp4100# configure
mp4100>config# port
mp4100>config>port# vcg cl-b/2
mp4100>config>port>vcg(cl-b/2)$ bind vc-vt cl-b/2/1/1/1/1
mp4100>config>port>vcg(cl-b/2)$ no shutdown
mp4100>config>port>vcg(cl-b/2)$ exit
mp4100>config>port# gfp cl-b/2
mp4100>config>port>gfp(cl-b/2)$ bind vcg cl-b/2
mp4100>config>port>gfp(cl-b/2)$ no shutdown
mp4100>config>port>gfp(cl-b/2)$ exit
mp4100>config>port# logical-mac cl-b/2
mp4100>config>port>log-mac(cl-b/2)$ bind gfp cl-b/2
mp4100>config>port>log-mac(cl-b/2)$ no shutdown

mp4100>config>port>log-mac(cl-b/2)$
mp4100>config>port>log-mac(cl-b/2)$
mp4100>config>port>log-mac(cl-b/2)$ exit all
mp4100# configure flows classifier-profile vlan600 match-all match vlan 600
mp4100#
mp4100# config
mp4100>config# flows
mp4100>config>flows# flow 13
mp4100>config>flows>flow(13)$ ingress-port ethernet 5/2
mp4100>config>flows>flow(13)$ egress-port logical-mac cl-a/2
mp4100>config>flows>flow(13)$ classifier vlan600
mp4100>config>flows>flow(13)$
mp4100>config>flows>flow(13)$ exit
mp4100>config>flows>flow(14)$ ingress-port logical-mac cl-a/2
mp4100>config>flows>flow(14)$ egress-port ethernet 5/2
mp4100>config>flows>flow(14)$ classifier vlan600
mp4100>config>flows>flow(14)$ exit all
mp4100#
mp4100# ################
mp4100# # eth-group 2 #
mp4100# ################
mp4100#
mp4100# config prot eth 2
mp4100>config>protection>eth-group(2)# bind working logical-mac cl-a/2
mp4100>config>protection>eth-group(2)# bind protection logical-mac cl-b/2
mp4100>config>protection>eth-group(2)# wait-to-restore 2
mp4100>config>protection>eth-group(2)# commit
 To delete Ethernet protection group 2:

mp4100#configure protection no ethernet-group 2
Viewing the Status of an Ethernet Protection Group

This section illustrates the status display of an Ethernet protection group.
 To view the Ethernet protection group status:

• At the config>protection>ethernet-group (<group number>)# prompt, enter
show status.
The Ethernet protection group status appears. In this example, the
Ethernet protection group number is 1.

mp4100>config>protection# ethernet-group 1
mp4100>config>protection>eth-group(1)# show status
Ports
---------------------------------------------------------------
Port Admin Oper Active
Working Logical MAC cl-a/1 Up Up --
Protection Logical MAC cl-a/2 Up Down Yes
detected.
608 Error ILLEGAL PROTECTION GROUP Ethernet group protection over SDH/SONET is not
DEFINITION supported in CL.2/A modules.
See also Error 608 in PW Protection and Path Protection
for SDH/SONET Payload for additional meanings.
613 Error WITH CL-DS0 PROTECTION When M8E1/M8T1 modules are installed in a system with
MUST BE ON SAME SLOT CL.2/DS0 modules, Ethernet protection members must be
defined on the same I/O slot.
614 Error ILLEGAL LOCAL FLOW If the Ethernet group members reside on different
BETWEEN ETH PORT AND M8E1T1 modules, a flow between such Logical Mac and an
L.MAC Ethernet port residing on one of these slots is illegal. For
Logical Macs defined on the same M8E1T1 module, this
configuration is allowed.
615 Error ETHERNET GROUP MEMBERS Working and protection logical MACs cannot be bound to
SHOULD BE THE SAME entities of different types: they must be both bound
either to gfp or hdlc ports.
616 Error NUM OF ETHERNET GROUPS The number of Ethernet groups defined per M8E1T1
PER SLOT EXCEEDS MAX module must not exceed 8.
617 Error NUM OF ETHERNET GROUPS The number of Ethernet groups defined on M8E1T1
PER SYSTEM EXCEEDS MAX module must not exceed 40 per system.
7.4 Ethernet Ring Protection (ERP)

A G.8032 Layer-2 Ethernet ring is used by Megaplex-4 for Ethernet traffic
protection. This technology builds a logical ring, defined as a set of IEEE 802.1-
compliant bridges, and protects against link and node failures. Megaplex-4
supports a total of 5 rings or sub-rings per chassis.
Applicable Modules
This feature is available for the following modules and ports:
7-20 Ethernet Ring Protection (ERP) Megaplex-4

• CL.2 and M-ETH modules – between GbE ports

• VS-16E1T1-EoP modules – between Logical MAC’s representing EoP
The ERP functionality is supported with the following conditions:
• When a CL.2/A module with advanced carrier capabilities is installed in the
chassis
• CL modules: Between ports on the same module as well as between CL-A and
CL-B ports
• M-ETH module: Between ports located on the same module
• Sub-50 ms switching is guaranteed for up to 16 nodes per ring.
Standards
ITU-T G.8032/Y.1344, Y.1731
Benefits
G.8032 revertive rings provide sub-50 ms protection for Ethernet traffic and
prevent loops at the Ethernet layer.
Factory Defaults
No Ethernet protection rings are configured in the system by default. Other
parameter defaults are listed in the table below.
bridge 0
east-port 0
west-port 0
force-sf no force-sf
r-aps vlan 0
vlan-priority 7
mel 255
rpl/no rpl no rpl
timers guard 500 500
holdoff 0
port-type east node-port
port-type west node-port
interconnection-node no interconnection-node
backward-compatibility no backward-compatibility
Megaplex-4 Ethernet Ring Protection (ERP) 7-21

Ethernet Ring Protection technology provides a scalable solution for low-cost
traffic protection and rapid service restoration, with SDH/SONET-type resilience.
It is built on traditional Ethernet MAC (IEEE 802.3) and bridging (IEEE 802.1)
functions. It is independent of any physical-layer technologies and can be utilized
in any carrier’s network.
In ERP every ring node uses heartbeat messaging to determine availability of its
neighbor. When a link failure occurs, it is detected via LOS or heartbeat
messaging. Upon failure, node forwarding information is recalculated to ensure
that data traffic reaches its destination, using alternative path.
Ring ports can reside on the GbE Ethernet ports belonging to the same CL or I/O
card, providing port redundancy. In addition, they can reside on the ports
belonging to different CL cards, providing port redundancy. In total, Megaplex-4
supports up to 5 rings or sub-rings.
Note Ring port cannot be bound to a LAG.
Ring Topology
Megaplex-4 supports different ring topologies, including single and
interconnected (ladder) ring topologies.
Figure 7-5. Single Ethernet Ring
Major Ring
Sub-Ring
Figure 7-6. Interconnected Ethernet Rings
R-APS Messaging
Ethernet ring protection is achieved by means of a dedicated protocol,
Automated Protection Switching (APS). Every ring link is bound by two adjacent
nodes. At any time, traffic flows on all, but one of the ring links. This link is called
the ring protection link (RPL). Under normal conditions this link is blocked. RPL is

controlled by a single node called an RPL owner, which prevents traffic from using
the RPL. When a failure is detected, the RPL owner unblocks the RPL port,
allowing the RPL to be used for traffic.
R-APS messages require a designated transmission channel (R-APS channel),
which is separated from the service traffic channel. An R-APS channel is
configured using a separate dedicated VLAN to enable the R-APS messages to be
handled differently from the service traffic. The R-APS channel and service traffic
blocking is performed via VID filtering by the bridge.
Mechanism of Operation
Every failure along the ring triggers an R-APS (SF) (R-APS Signal Fail) message
along both directions from the nodes adjacent to the failed link. Before sending
the R-APS, these nodes block the ports facing the failed link. On receiving these
messages, the RPL owner unblocks the RPL port. An SF message is triggered even
if only one node adjacent to the failed link recognizes the failure. Moreover, to
overcome scenarios in which link failures are not recognized via LOS (Loss of
signal), ERPS can also use the standard Ethernet OAM 802.1ag Continuity Check
Messages (CCMs) to expose the failure to the two adjacent nodes.
During a recovery phase, when a failed link is restored and a node continually
detects a Clear SF, it sends an R-APS No Request (NR) message and keeps the
failed port blocked. When receiving the R-APS (NR), the RPL owner starts its
Wait-To-Restore (WTR) timer. When that timer expires, it blocks the RPL port and
sends RAPS (NR, RB) (R-APS no request, root blocked) messages in both
directions of the ring. Nodes receiving the R-APS (NR, RB) message flush their
learning table, unblock their blocked ports, and return to idle state.
Figure 7-7 illustrates a stable-state Ethernet ring with blocked RPL to prevent a
loop. Each node is monitored, using Ethernet CCM OAM messages, and the ring
protection is triggered by loss of continuity or server layer failure, as defined in
Y.1731.
Traffic is Blocked
CCM CCM
RPL Owner
CCM
CCM
CCM CCM
Figure 7-7. Fault-Free ERP
Administrative Commands
If there is a need to intervene into ERP operation for maintenance or any other
reason, the operator can issue a forced or manual switch command.
• Forced Switch (FS) – This command forces a block on the ring port where the
command is issued. It can be issued even if an SF condition exists on the ring.
Multiple force switch commands can be supported per ring instance but only
one per node.

• Manual Switch (MS) – In the absence of a failure or FS, this command forces
a block on the ring port where the command is issued. The manual switch
command can be applied to a single ring node only. When the command is
active, all ring nodes shift to the manual switch mode.
• Clear switch command clears all existing force and manual switch command
on the ERP.
Note The manual and forced switch commands are temporary commands and do not
permanently change the location of the RPL.
Multiple Rings
Multiple rings with a common link are usually referred to as ladder network (see
Figure 7-8). In such networks a common VLAN is shared on more than one
physical ring. For example, a user connected to node E is communicating with a
user connected to node A over the same VLAN.
Ring topology includes a physical link between nodes G and C. It belongs to the
major ring and is used by the sub-ring.
H G F
Virtual Channel
A Major Ring Sub-Ring E
B C D
Figure 7-8. Physical Ladder Topology
H G G F
A Major Ring Sub-Ring E
B C C D
Figure 7-9. Major Ring and Sub-Ring
The following terms are commonly used for describing ladder ring topology:
• Interconnection nodes – Ring nodes that are common to both interconnected
rings (nodes C and G in Figure 7-8).

• Major ring – An Ethernet ring that controls a full physical ring and is
connected to the interconnection nodes on two ports (ring A-H-G-C-B in
Figure 7-8)
• Sub-ring –An Ethernet ring that is connected to a major ring at the
interconnection nodes. By itself, the sub-ring does not constitute a closed
physical ring. A sub-ring is connected to the interconnection nodes on only
one port (ring C-D-E-F-G in Figure 7-8). Link C–G is not a part of the sub-ring
and it is controlled by the major ring. Megaplex-4 supports up to four sub-
rings per major ring.
• R-APS virtual channel – The R-APS virtual channel is the R-APS channel
connection between two interconnection nodes of a major ring over a
network.
In a stable state the rings in Figure 7-8 have two RPL owners that prevent the
traffic from looping in the network (nodes E, A). When a non-shared link fails in
the network, the RPL owner that controls the ERPS instance containing that link
unblocks the RPL port while the distant RPL port, which is not a part of this
instance, remains blocked. For example, if link G-F fails, only node E unblocks its
RPL port, while node A does not change the state of its RPL port.
If a shared link fails (link G-C), the RPL owner of the main ring (node A) unblocks
its port; however, the RPL port of the sub-ring (node E) remains blocked since
that link is declared as virtual channel for this ring.
Timers
The following timers are used to facilitate ERP operation:
• Wait-to-Restore (WTR) – Period of time used by RPL owner to verify that the
ring has stabilized before blocking the RPL after signal recovery.
• Guard – Period of time during which all received A-RPS messages are ignored
by the ERP mechanism. This prevents the ring nodes from receiving outdated
A-RPS messages circulating the network.
• Hold-off – Period of time during which the underlying Ethernet layer attempts
to filter out intermittent link faults before reporting them to the ERP
mechanism.
ERP Configuration
Configuring ERP
 To configure ERP:
1. In the configure>protection# prompt, enter erp followed by ring number
(1–5).
An ERP instance with is created and the config>protection>erp(1)#
prompt is displayed.
2. Configure the ERP as illustrated and explained below.
Note Using no before erp (ERP_number) deletes an ERP instance.

Making the ring backward-compatibility

compatible with previous no backward-compatibility
ERP implementations
Assigning the node to a bridge <1–11> 1 is always used for CL-A bridge,
bridge instance 2..11 –for bridges on M-ETH modules
Forcing a signal failure to force-sf {east | west} no force-sf cancels the command
initiate the Ethernet Ring
protection mechanism
Defining ERP node as an interconnection-node

interconnection node, no interconnection-node
sharing more than one
ring
Defining a bridge port as east-port <bridge_port_number> 1..84 for bridge 1

an East port of ERP node 1..9 for bridges 2..11
Sub-rings have East ports only
Defining a bridge port as west-port <bridge_port_number> 1..84 for bridge 1

a West port of ERP node 1..9 for bridges 2..11
Sub-rings do not have West ports
Defining node port type port-type owner {east | west} rpl – RPL owner
in relation to RPL owner port-type neighbor {east | west} neighbor – port directly connected to
port-type next-neighbor {east | west} RPL owner
port-type node-port next-neighbor – port connected to

RPL owner via neighbor
node-port – regular ring port, which
is not connected to RPL owner
Configuring dedicated r-aps [vlan <1–4094>] [mel <0–7>] R-APS settings must be the same for
VLAN for R-APS messages all ring members
MEL – Dedicated Maintenance Entity
Group Level for R-APS messages
Configuring the revertive revertive This mode is relevant only to the RPL
mode owner node.
In the revertive mode, after condition
causing the switch is cleared, traffic
is blocked at the RPL owner and
restored to the idle state (after WTR
timer has expired).
After the node has entered the state
in revertive mode, use the Clear
command to exit the state.
no revertive enables non-revertive
mode (system does not switch to idle
state)

Enabling propagation of sf-trigger {east | west} mep <md-id> Before enabling SF propagation,
Signal Failure (SF) <ma-id> <mep-id> verify that relevant CFM parameters
condition from the no sf-trigger {east | west} have been configured.
Ethernet OAM service MEPs used for SF propagation cannot
layer reside on R-APS VLAN; they must be
bound to data VLANs only.
Adding a short description <string> Up to 80 characters

description of the ring Using no description removes the
description.
Adding a short port-description {east | west} Up to 80 characters

description of the East or <string> Using no description removes the
Weat port description.
Connecting previously sub-ring <ring_number> This option is available for major rings
defined sub-ring to a no sub-ring only. The sub-ring number must be
major ring lower than the number of the major
ring it is assigned to.
Defining wait-to restore wait-to-restore <60–720> Wait-to-restore timer defines period

period for RPL owner of time used by RPL owner to verify
that the ring has stabilized before
blocking the RPL after signal
recovery. The WTR timer is configured
in 60-sec. steps.
Blocking the East or West manual-switch {east-port | west-port } The manual switch command can be
port of a ring node applied to a single ring node only.
When the command is active, all ring
nodes shift to the manual switch
mode.
Blocking the East or West force-switch {east-port | west-port } Multiple force switch commands can
port of a ring node be supported per ring instance, but
only one is supported per node.
Clearing the existing clear

switch commands
Administratively enabling no shutdown To avoid traffic loops, always enable

the ERP interface Ethernet ports only after enabling
Ethernet rings.
Using shutdown disables the ERP.

Defining guard and hold- timers [guard <10–2000>] [holdoff Guard timer is used by the ERP
off periods in msec <0–10000] mechanism to prevent ring nodes
from receive outdated R-APS
messages. While the guard timer is
active, all received R-APS messages
are ignored by the node. The guard
timer is configured in 10-ms steps.
Its recommended value for all ring
nodes is 2 sec.
Hold-off timer is used by Ethernet
layer to filter out intermittent faults.
Faults are reported to the ERP
mechanism only after the hold-off
timer expires. The guard timer is
configured in 100-ms steps.
Displaying ERP status show status
Displaying ERP statistics show statistics
Clearing ERP statistics clear statistics
Displaying ERP Status

You can display current status of configured ERP entity.
 To display ERP status:

• In the config>protection>erp(erp_number)$ prompt, enter show status.
The ERP status is displayed.
mp4100>config>protection>erp(5)# show status
Bridge Number : 1 East Port : 1 West Port : 2
RPL Link : West
Ring State : Protection
East Port Status : Block R-APS and Data Local SF Source : Server Layer
West Port Status : Forward Local SF Source : OK
The ERP status provides information on:
 Bridge number
 Bridge ports assigned to be East and West ring ports
 RPL link: East or West ring ports
 Ring state:
 Init – The node is not yet participating in the ring
 Idle – The node is performing normally (there is no link failure on the
ring). In this state, traffic is unblocked on both ring ports, except for
the RPL owner node, which blocks the RPL port (the other RPL owner
port is unblocked).

 Protection – A failure occurred on the ring. A not-owner node have

traffic blocked on the ring port that connects to the failed link. The
RPL owner, if it is not at one end of the failed link, unblocks the RPL
port so both ports are active.
 East/West Port Status:
 Forward – Port is forwarding data
 Blocked – Port is blocked
 East/West Port Local SF Source – Local Signal Failure source:
 Server Layer
 OAM CFM
 Admin
Displaying ERP Statistics

When the G.8032 Ethernet Ring Protection (ERP) is enabled, Megaplex-4 allows
collecting statistics on R-APS messages sent and received by the East and West
ports.
 To display ERP statistics:

• In the config>protection>erp(erp_number)$ prompt, enter show statistics.
The ERP statistic counters are displayed.
mp4100>config>protection>erp(1)$ show statistics
East Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 1 51
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
West Port
----------------------------------------------
R-APS Message Rx Frames Tx Frames
SF 1 51
NR 0 0
NR,RB 0 0
Total Valid 0 0
Total Errors 0 0
Table 7-7. ERP Statistic Counters
Counter Description
R-APS SF Message Tx/Rx Total number of R-APS Signal Fail (SF) messages received or transmitted
by East/West port.
Received R-APS Signal Fail message indicates a failed port in the ring.
Transmitted R-APS Signal Fail message indicates a failed port in the
node.

Counter Description
R-APS NR Message Tx/Rx Total number of R-APS No Request (NR) messages received or
transmitted by East/West port.
Received R-APS No Request message indicates absence of failed ports in
the ring.
Transmitted R-APS No Request message indicates that the node fixed its
failed port.
R-APS NR, RB Tx/Rx Total number of R-APS No Request (NR), RPL Blocked (RB) messages
received or transmitted by East/West port.
Received R-APS No Request, RPL Blocked message indicates that RPL
port is blocked and all other not-failed blocked ports are unblocked in
the ring.
Transmitted from the RPL No Request, RPL Blocked message indicates
that RPL port is blocked.
Total Valid Rx/Tx Total number of valid R-APS messages received or transmitted by
East/West port
Total Errors Rx/Tx Total number of errored R-APS messages received or transmitted by
East/West port
Example
The figure and the script below illustrate configuration a G.8032v2 ring over the
CL.2 and M-ETH module ports.
GbE
Port 1 Flow 2
East
BP 1 Bridge
Ethernet Flow 3
CL-A BP 3
Ring
Flow 1 BP 2
VLAN Port 1
GbE West
Port 2 500
(RPL Owner)
M-ETH
Module
Figure 7-10. ERP Configuration
 To configure the ERP:

1. Assign previously configured queue groups to module ports.
2. Add three bridge ports.
3. Define bridge port VLAN membership for bridge ports that are not ring
members:

 BP 3 – member of VLAN 500

4. Configure the ring:
 BP 1 – East port
 BP 2 – West port, RPL owner
 R-APS VLAN – 200
 Data VLAN – 500
5. Configure two management and data flows (red flows in the figure):
 Classifier profile for VLAN 500
 Configure flows 1, 2 between the CL.2 ports and BPs
6. Configure one data flow (blue flow in the figure):
 Classifier profile for VLAN 500
 Configure the data flow 3.
7. Enable the CL and M-ETH module ports.
mp4100# exit all
mp4100# config slot 3 card-type ethernet m8eth
mp4100#
#************Configuring_ Shaper_Profiles and Queue_Group_Profiles *********
mp4100# configure qos
mp4100>config>qos# shaper-profile b-s
mp4100>config>qos>shaper-profile(b-s)$ bandwidth cir 50000
mp4100>config>qos>shaper-profile(b-s)$ exit
mp4100>config>qos# queue-group-profile b-s
mp4100>config>qos>queue-group-profile(b-s)$ queue-block 0/1
mp4100>config>qos>queue-group-profile(b-s)>queue-block(0/1)$ profile
DefaultQueue1
mp4100>config>qos>queue-group-profile(b-s)>queue-block(0/1)$ shaper profile
b-s
mp4100>config>qos>queue-group-profile(b-s)>queue-block(0/1)$ exit all
#***********Enabling_Ports and Assigning Queue Group Profiles***********

mp4100#
mp4100# config port ethernet 3/1
mp4100>config>port>eth(3/1)# no shutdown
mp4100>config>port>eth(3/1)# queue-group profile b-s
mp4100>config>port>eth(3/1)# exit
mp4100>config>port#
mp4100>config>port# ethernet cl-a/1
mp4100>config>port>eth(cl-a/1)# no shutdown
mp4100>config>port>eth(cl-a/1)# queue-group profile b-s
mp4100>config>port>eth(cl-a/1)# exit
mp4100>config>port#
mp4100>config>port# ethernet cl-a/2
mp4100>config>port>eth(cl-a/2)# no shutdown
mp4100>config>port>eth(cl-a/2)# queue-group profile b-s
mp4100>config>port>eth(cl-a/2)# exit all
#*********************************End****************************************

#***************************Configuring_Bridge Ports*************************
mp4100#
mp4100# config bridge 1
mp4100>config>bridge(1)$ port 1
mp4100>config>bridge(1)>port(1)$ no shutdown
mp4100>config>bridge(1)>port(1)$ exit
mp4100>config>bridge(1)# port 2
mp4100>config>bridge(1)# port 3
mp4100>config>bridge(1)#
mp4100>config>bridge(1)# vlan-aware
mp4100>config>bridge(1)# exit all
mp4100#
#*********************************End****************************************
#*********************Configuring_Classifier_Profiles*****************
mp4100# config flows
mp4100>config>flows# classifier vlan500 match-any
mp4100>config>flows>classifier-profile(vlan500)$ match vlan 500
mp4100>config>flows>classifier-profile(vlan500)$ exit all
#*********************************End****************************************
#******************Configuring_Management_and_Data_Flows 1,2*****************
mp4100# config flows
mp4100>config>flows>flow(1)$ class vlan500
mp4100>config>flows>flow(1)$ ingress ethernet cl-a/1
mp4100>config>flows>flow(1)$ egress bridge-port 1 1
mp4100>config>flows>flow(1)$ reverse-direction queue 0 block 0/1
mp4100>config>flows#
mp4100>config>flows>flow(2)$ ingress ethernet cl-a/2
#*********************************End****************************************
#*********************Configuring_Data_Flow_3*****************
mp4100>config>flows>flow(3)$ ingress ethernet 3/1
#*********************************End****************************************

#************************ Configuring_the_Ring*******************************
mp4100# configure protection erp 1
mp4100>config>protection>erp(1)# bridge 1
mp4100>config>protection>erp(1)# r-aps vlan 200
mp4100>config>protection>erp(1)# r-aps mel 5
mp4100>config>protection>erp(1)# east-port 1
mp4100>config>protection>erp(1)# west-port 2
mp4100>config>protection>erp(1)# port-type west rpl
mp4100>config>protection>erp(1)# no shutdown
mp4100>config>protection>erp(1)# exit all
mp4100# commit
Result : OK
#*********************************End****************************************
7.5 HSR Protection

The High-availability Seamless Redundancy (HSR) ring offers zero recovery time,
which is crucial for applications that demand high availability and short reaction
times, such as protection applications for electrical station automation and
controllers for synchronized drives which require constant connection.
Note Zero loss switch-over is not supported when an active CL.2 module is removed
from the chassis.
The HSR functionality is supported with the CL.2/GBEA and CL.2/155/622/A

assemblies on the following ports:
• GbE ports of CL.2 modules
• GbE ports of M-ETH modules
• FE port of VS modules.
HSR protection employs the term LRE (Link Redundancy Entity). An LRE is defined
with two bridge ports bound to it via flows and corresponding bridge ports.
Megaplex-4 supports up to 5 LREs per chassis. Two ports bound to the LRE must
belong to the same type of module.
Benefits
HSR protection provides the following benefits:
• Increased availability. If a link fails or is replaced, the traffic is not disrupted
and communication is maintained error-free (even though the available
capacity is reduced)
• Minimized service downtime in the case of failure.
Standards
IEC 62439-3 Industrial communication networks – High availability automation
networks –Part 3: Parallel Redundancy Protocol (PRP) and High-availability
Seamless Redundancy (HSR).
Megaplex-4 HSR Protection 7-33

Note Only Store-And-Forward operation is supported by Megaplex-4. Cut-through

operation, as optionally required by the standard, cannot be supported due to
Megaplex-4 HW structure.
The HSR implements ring topology. Each frame is repeatedly transmitted on
different independent paths simultaneously. The receiver uses the first incoming
frame and eliminates the later arriving duplicates. This provides two apparently
disjoint paths available for each communication session.
Node Functionalities
Out of several node functionalities defined by the standard, two are implemented
in RAD’s HSR: DANH and RedBox:
• DANH is used for PW traffic inside the Megaplex device (PW services).
• RedBox is applicable when Megaplex-4 is used as a bridge between a local
LAN substation and a WAN.
DANH (Double Attached Node Implementing HSR) is a node directly inserted into
the ring as a leaf. It is a device with an integrated three-port HSR switch (two
external and one internal port). Of one frame to be transmitted, two copies are
made and transmitted simultaneously in the ring in both directions. Unicast
frames are removed from the ring by the receiver, multicast and broadcast
frames from the transmitter. The receiver uses the first received frame and
eliminates the duplicate arriving later.
For connecting devices without HSR capabity, a Redundancy Box (RedBox) is
used. This provides the HSR functions to all the connected nodes. HSR
Redundancy Boxes (RedBox) use two Ethernet ports operating in parallel to
connect to a ring.
The transmitting HSR node or HSR RedBox sends twin frames, one in each
direction, on the ring. For identification, the HSR node injects the twin frames
with an HSR tag. The HSR tag consists of a port identifier, the length of the
payload and a sequence number. In a normal operating ring, the destination HSR
node or RedBox receives both frames within a certain time skew. An HSR node
forwards the first frame to arrive to the upper layers and discards the second
frame when it arrives.
The figure below shows a diagram of HSR implementation.
RedBox
SAN#1 A
HSR
B
Bridge
SAN#4
The nodes support the IEEE 802.1D bridge functionality and forward frames from
one port to the other, except if they already sent the same frame in that same
direction (see Duplicate Discard below).
7-34 HSR Protection Megaplex-4

Duplicate Discard
The duplicate discard algorithm is used at the frame reception. Each node relays
the frames it receives from port A to port B, except for a frame (singlecast) that
it already forwarded or that is addressed to itself.
This feature can be disabled for testing purposes (network monitoring) or
redundant nodes setup. This is configured by a parameter per LRE entity
indicating if duplicate discard is activated at port A and port B. When this
parameter is activated, the duplicate frames are discarded. Otherwise, the
duplicate frames received from the A/B port are forwarded to the B/A port.
Proxy traffic is discarded in both modes.
When an LRE port is set to duplicate-discard, 2 clusters are allocated for ports A
and B. Clusters are also used for interlink ports. Therefore one duplicate-
discarded LRE port with one interlink use 3 clusters. The total number of available
clusters is 9. Thus only 3 LREs (with one interlink each) can be configured in
Megaplex-4 with duplicate-discard functionality.
Supervision Packet Analysis

You can activate supervision packets analysis for Megaplex to analyze the
received supervision frames. When this feature is switched off, Megaplex still
receives supervision frames without analyzing them. An HSR supervision frame is
sent by the node every 2 sec. The log is displayed in the node table and proxy
table. After 60 sec the node entry is cleared in both tables.
Configuring the HSR

LRE configuration includes the following steps:
1. Assigning a number to a LRE.
2. Creating bridge ports and defining them as egress tagged VLAN members
(part of “VLAN table”)
3. Configuring flows between bridge ports and Ethernet ports.
Note 1. No flows can be established between the LRE partners and other Ethernet
ports in Megaplex-4.
2. The classification of the packets to be forwarded via LRE is based on VLAN
membership.
4. Assigning queue group profiles to Ethernet ports

5. Binding bridge ports to the LRE
6. Assigning a name to the LRE.
For implementation of this procedure, see the figure and the configuration
example below.

Bridge
VLAN 100
eth#1
BP 1 2 Flow 1 Q-Block cl-a/1
nd
LRE Bi
eth#3
eth 1/1
Q-Block Flow 3 BP 1 1
Bi
nd
eth#2
BP 1 3 Flow 2 Q-Block cl-a/1
Figure 7-11. LRE Configuration
 To add a LRE:
2. Type lre and enter a LRE number (1..5).
The config>port>lre(number)# prompt is displayed.
 To configure the LRE:

• At the config>port>lre(number)# prompt, enter all necessary commands
Adding a bridge port to bind bridge-port <slot/port> Only CL bridge ports can be bound to the LRE
the LRE Ports A and B that are LRE partners must
belong to module of the same type (either
CL, or M-ETH, or VS)
A port configured as partner in HSR entity
cannot be used for non-HSR traffic.
Using no before bind removes a link from LRE
Assigning a name to the name <Alphanumeric string> Maximum name length is 64 characters
LRE
Using duplicate algorithm duplicate-discard The total number of ports with duplicate
at reception discard functionality is limited to 9 (this
means that out of 5 LREs available in
Megaplex-4, only 3 can be configured with
duplicate-discard functionality).
Using no before duplicate-discard cancels the
use of duplicate algorithm
Activating supervision rx-supervision-packets no rx-supervision-packets deactivates

packet analysis supervision packet analysis
Disabling the LRE port shutdown Using no shutdown enables the LRE port
Displaying the LRE status show status

Displaying the node table show node-table
Displaying the proxy table show proxy-table
Displaying LRE statistics show statistics
Clearing the node table clear-node-table
Clearing the proxy table clear-proxy-table
Clearing LRE statistics clear-statistics
Example
• LRE port 1
• LRE 1 partners:
 Port A: Bridge port 1 2
 Port B: Bridge port 1 3
 Port C (interlink): Bridge port 1 1
Note Port C is not bound to the LRE port.
• For more configuration details, see the table below.
Table 7-8. Flows and Ports Configured for HSR
Flow 1 2 3
Egress port Bridge port 1 1 Bridge port 1 2 Bridge port 1 3
Ingress port ethernet 1/1 ethernet cl-a/1 ethernet cl-a/2
Queue group Eth_port Giga Giga

profile
Shaper profile 100m 950m 950m
Partner in LRE 1 Port C (interlink) Port A Port B
mp4100# ############ up chassis ################

mp4100#
mp4100# exit all
mp4100# configure slot 1 card-type dsl m8sl
mp4100#
mp4100# ######### MNG #################
mp4100# config router 1 interface 1 address 172.17.174.2/24
mp4100# config router 1 static 0.0.0.0/0 address 172.17.174.1
mp4100# exit all
mp4100#
mp4100# ######### Queue groups #################
mp4100>config>qos# shaper-profile 950m
mp4100>config>qos>shaper-profile(950m)$ bandwidth cir 950000

mp4100>config>qos>shaper-profile(950m)$ exit
mp4100>config>qos# shaper-profile 100m
mp4100>config>qos>shaper-profile(100m)$ bandwidth cir 100000
mp4100>config>qos>shaper-profile(100m)$ exit all
mp4100#
mp4100>config>qos# queue-group-profile Giga
mp4100>config>qos>queue-group-profile(Giga)$ queue-block 0/1
mp4100>config>qos>queue-group-profile(Giga)>queue-block(0/1)$
shaper profile 950m
exit all
mp4100#
mp4100>config>qos# queue-group-profile Eth_Port
mp4100>config>qos>queue-group-profile(Eth_Port)$ queue-block
0/1
mp4100>config>qos>queue-group-profile(Eth_Port)>queue-
block(0/1)$ bind queue 0 queue-block 1/1
block(0/1)$ shaper profile 100m
block(0/1)$ exit all
mp4100#
mp4100# ######### Eth ports #################
mp4100# configure port eth cl-a/1 no shutdown
mp4100# configure port eth cl-a/1 queue-group profile Giga
mp4100# configure port eth cl-a/2 no shutdown
mp4100# configure port eth cl-a/2 queue-group profile Giga
mp4100# configure port eth 1/1 no shutdown
mp4100# configure port eth 1/1 queue-group profile Eth_Port
mp4100#
mp4100# ######### Brigde #################
mp4100# configure bridge 1 port 1 no shutdown
mp4100# configure bridge 1 vlan-aware
mp4100# configure bridge 1
mp4100>config>bridge(1)# vlan 100
mp4100>config>bridge(1)>vlan(100)$ tagged-egress 1..3
mp4100>config>bridge(1)>vlan(100)$ exit all

mp4100#
mp4100# ######### HSR port (LRE) #################
mp4100# configure port lre 1 bind bridge-port 1 2
mp4100# configure port lre 1 bind bridge-port 1 3
mp4100# configure port lre 1 no shutdown
mp4100#
mp4100# ######### Flows #################
mp4100# configure flows classifier-profile "100" match-all
match vlan 100
mp4100# configure flows
mp4100>config>flows>flow(1)$ ingress-port ethernet 1/1

mp4100>config>flows>flow(1)$ egress-port bridge-port 1 1

mp4100>config>flows>flow(1)$ classifier 100
mp4100>config>flows>flow(1)$ reverse-direction queue 0 block
0/1
mp4100>config>flows>flow(2)$ ingress-port eth cl-a/1
0/1
mp4100>config>flows>flow(3)$ ingress-port eth cl-a/2
0/1
mp4100>config>flows# com
 To delete an LRE:
mp4100#configure port no lre 1
detected.
790 Error LRE PORTS MUST BE IN SAME LRE ports must have the same VLAN membership
VLAN
791 Error SAME BP CAN'T BE USED IN A bridge port cannot be a partner in more than one LRE
DIFFERENT LRE's
792 Error TWO BP MUST BIND TO LRE An LRE must include exactly two LRE ports
PORT
793 Error ILLEGAL FLOW FOR ETH PORT Once an Ethernet port participates in a flow to an LRE
BOUND TO LRE bridge port, no other flows can be configured at this port
794 Error PORTS BOUND TO LRE MUST Ports A and B that are LRE partners must belong to
BE SAME MODULE TYPES module of the same type (either CL, or M-ETH, or VS)
795 Warning VLAN WITH 2 LRE BP MUST It is recommended that a VLAN including two LRE bridge
INCLUDE INTERLINK BP ports as members will also include the bridge ports with
tributary traffic (defined as interlinks)

796 Error HSR CLUSTER LIMITATION Try to do one of the following:

PROBLEM • Reduce the number of LREs
• Reduce the number of interlinks
• Do not use the duplicate discard algorithm.
Viewing the LRE Status

This section illustrates the status display of an LRE group.
 To view the LRE group status:

• At the config>port>lre (<number>)# prompt, enter show status.
The LRE group status appears.
mp4100>config>port>lre(1)# show status
Group
---------------------------------------------------------------
Name :
MAC Address : 00-20-D2-51-E4-D6
Links
---------------------------------------------------------------
Port Admin Oper
---------------------------------------------------------------
Up Up
Up Up
Displaying a Node Table

The LRE node table contains information about all remote LREs that advertised
themselves through supervision frames. The frames displayed in the table are of
two kinds:
• HSR supervision frames sent by DANH (Multicasts, both direction) declaring
their own MAC
• RedBox supervision frames declaring the MACs in their interlink.
 To display the node table:

• At the config>port>lre (<lre number>)# prompt, enter show node-table.
The node table is displayed.

mp4100>config>port>lre(1)# show node-table

Nodes
------------------------------------------------------------------------
Last Time Last Time
Id Node Type MAC Seen on Port A Seen on Port B
(ticks) (ticks)
------------------------------------------------------------------------
-----
1 Redboxp 00-00-03-00-51-01 33005 33005
2 Danp 00-20-D2-51-7B-1D 33005 33005
3 Redboxp 00-00-03-00-51-02 33005 32805
Displaying a Proxy Table

The proxy table contains source MAC’s of the frames forwarded from the Interlink
to the HSR ports. The learning is based on the HSR supervision messages with
MAC declaration. The total number of Source MAC addresses handled by HSR
engine is limited to 256; correspondingly, the maximum number of entries in the
proxy tables is 256. This number is shared between all the LREs (up to 5)
configured in the Megaplex.
 To display the proxy table:

• At the config>port>lre (<lre number>)# prompt, enter show proxy-table.
The proxy table is displayed.
mp4100>config>port>lre(1)# show proxy-table
Proxy Nodes
------------------------------------------------------------------------
Id MAC Address
------------------------------------------------------------------------
1 00-00-03-00-50-01
2 00-00-03-00-50-02
Displaying LRE Statistics

When the HSR protection is enabled, Megaplex-4 allows collecting the LRE
statistics.
 To display HSR statistics:

• In the config>protection>lre(lre_number)$ prompt, enter show statistics.
The LRE statistic counters are displayed.
mp4100>config>port>lre(1)# show statistics
Statistics Port A Port B Port C
---------------------------------------------------
Tx Frames : 281 281 113
Rx Frames : 283 283 0
Error Count : 0 0 --
Duplicate Frames : 0 0 0
Own Rx Frames : 0 0 --

Table 7-10. LRE Statistic Counters
Counter Description
TX frames Number of frames sent over port A/B/C that are HSR tagged. Only
frames that are HSR tagged are counted. A frame aborted during the
transmission is not counted.
RX frames Number of frames received over port A/B/C that are HSR tagged. Only
frames that are HSR tagged are counted. A frame aborted during the
reception is not counted.
Error Count Number of frames with errors (not matching HSR ETH type) received on
this LRE port
Duplicate Frames Number of entries in the duplicate detection mechanism on port A/B/C
for which one single duplicate was received.
Own RX frames Number of HSR tagged frames received on Port A/B that originated from
this device. Frames originate from this device if the source MAC matches
the MAC of the LRE, or if the source MAC appears in the node table
7.6 I/O Group Protection

The I/O group protection is hardware type redundancy established between two
identical modules installed in the same Megaplex chassis and connected by a
Y-cable (CBL-G703-8/RJ45/Y) that can be ordered from RAD. This type of
protection is supported by M8E1/M8T1 and M16T1 modules and provides
protection mainly for technical failures in the module hardware.
Note M16T1 modules require a special ordering option to support the I/O group
protection (see M16E1, M16T1 Data Sheet).
The I/O group protection must be defined between identical module types (M8E1
with M8E1, M16T1 with M16T1 etc). The maximum total number of I/O groups
that can be configured in the system is 5 for Megaplex-4100 and 2 for
Megaplex-4104.
Benefits
The I/O group protection provides two main advantages:
• Automatically restores service within a short time without user intervention
• In case of technical failure, allows service to continue while technical staff
finds the source of the failure and corrects it.
Moreover, when protection is used, tasks such as planned maintenance, updating
software versions, or installing modules with enhanced capabilities, can also be
performed without disrupting service, provided a few precautions are taken (see
below).
7-42 I/O Group Protection Megaplex-4

Standards
I/O Group Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with I/O group protection disabled.
For I/O group protection, two modules with the same type of physical and
electrical interfaces are connected to the same communication link by a single
Y-cable. A typical configuration is shown in Figure 7-12.
During normal operation, the transmit output of the protection module is
electrically disconnected from the link. If the working module fails, it is
disconnected from the link and from the internal buses, and the protection
module takes over.
The criteria for switchover between the modules are as follows:
• Working module failure (provided it is no more identified in the database)
• Working module extraction.
Y-Cable
POP B
POP A
SDH/
OC-3/12
1-8
1-8
1-8
1-8
T1 SONET T1
9-16
9-16
9-16
9-16
ADM ADM
PBX M16 M16 CL.2 CL.2 M16 M16 PBX

Patch Panel MP-4100 MP-4100 Patch Panel
Path Protection
Figure 7-12. I/O Group Protection using Y-Cable
Protection Mode
The protection mode for TDM I/O group redundancy is always non-revertive. The
module will not automatically flip back after the failed port returns to normal
operation, but only when the currently used I/O module is removed. The
switchover back to the working module will occur only if one of the criteria listed
below is satisfied:
• Protection module failure
• Protection module extraction.
Configuring I/O Group Protection

The I/O Group Protection is configured as follows.
Megaplex-4 I/O Group Protection 7-43

 To add an I/O protection group:

1. Navigate to configure protection.
2. Type io-group and enter a group number.
The config>protection>io-group(group number)# prompt is displayed.
 To configure the I/O protection group:

• At the config>protection>io-group(group number)# prompt, enter all
Assigning a name to the name <up to 80 characters>

I/O protection group
Administratively enabling no shutdown Using shutdown disables the group

the I/O protection group
Adding working and bind {working | protection} Using no bind protection removes the
protection modules <slot> protection port from the group. There is
slots to the I/O protection no need to remove the working port from
group the group.
Forced switching of traffic force-switch-to-working

from the protection slot to
the working slot
Forced switching of traffic force-switch-to-protection

from the working slot to
the protection slot
Manual switching of traffic manual-switch-to-working

from the protection slot
back to the working slot,
unless a failure condition
exists on the working slot
or an equal/higher priority
switch command is in
effect
Forced switching of traffic manual-switch-to-protection

from the working slot to
the protection slot, unless
a failure condition exists
on the protection slot or
an equal/higher priority
effect
Clearing the force switch clear Once the force-switch command is

command cleared, the module returns back to
normal operation.
7-44 I/O Group Protection Megaplex-4

Example
 To add and configure an I/O protection group:
• Protection group number – 2
• Working slot – M16T1 module installed in slot 6
• Protection slot – M16T1 module installed in slot 5
mp4100>config# protection
mp4100>config>protection# io-group 2
mp4100>config>protection>io-group(2)$ bind working 6
mp4100>config>protection>io-group(2)$ bind protection 5
mp4100>config>protection>io-group(2)$ no shutdown
mp4100>config>protection>io-group(2)$
mp4100>config>protection>io-group(2)$ commit
 To delete protection group 2:

mp4100#configure protection no io-group 2
detected.
604 Error PROTECTION PORT IS IN Ports in two modules participating in I/O group protection
SHUTDOWN STATE must have identical configuration. For example, if in the
1st module ports 1,3,5 are set to “no shutdown” and the
other ports are in shutdown state, the same should be in
the 2nd module.
605 Error DIFFERENT CARDS TYPE I/O group protection must be defined between identical
module types (M8E1 with M8E1, M16T1 with M16T1 etc)
606 Error WORKING & PROTECTION ARE Working and protection modules in I/O group protection
ON THE SAME SLOT must be defined on different slots
7.7 LAG Protection

Two Gigabit Ethernet ports on the Megaplex-4 CL modules ports can be operated
as a single logical interface, using link aggregation in accordance with IEEE
802.3-2005. LAG uses 1:1 distribution mechanism. Megaplex-4 supports up to 2
LAGs per chassis.
Using link aggregation inherently provides redundancy; if one of the GbE ports
fails, the other can continue transferring traffic. Link failure is detected by
sensing the loss of valid signals, or receiving a failure report via Link Aggregation
Control Protocol (LACP) if applicable, in which case all traffic is sent through the
other link.
Megaplex-4 <LAG Protection 7-45

The load sharing is automatically readjusted if a failure or recovery from failure

occurs in any of the links that participate in a LAG.
The CL modules support port aggregation on the same or different modules.
For a LAG aggregating two GbE of the same CL module, up to two LAGs can be
configured each time in the system. When LAG members belong to different CL
modules, only one LAG can be defined per system.
Benefits
Static LAGs provide the following benefits:
• Increased availability
If a link within a LAG fails or is replaced, the traffic is not disrupted and
communication is maintained (even though the available capacity is reduced).
• Load sharing
Traffic is distributed across multiple links, minimizing the probability that a
single link could be overwhelmed.
• Use of existing hardware
Software replaces the need to upgrade the hardware to higher bandwidth
capacity.
Link aggregation always provides revertive recovery, because that as soon as the
down port returns to normal, the full bandwidth is again available.
Configuring the LAG

This section explains how to define a link aggregation group (LAG) and enable link
aggregation control protocol (LACP). Megaplex-4 supports up to 2 LAGs.
LAG is defined with two Ethernet ports bound to the group. LAG serves as a
logical port with all relevant port attributes (queue block profile, L2CP profile,
etc). Services flow to and from the LAG, use the LAG as their ingress/egress port.
To ensure correct distribution of LACP traffic, you must configure a flow with an
L2CP profile with peer action for the LACP address (01-80-c2-00-00-02). The
flow must have the following attributes:
• Ingress port – LAG
• Egress port – according to application requirements.
If you use the flow only to peer the LACP frames and do not need to forward the
traffic, discard it, using the drop command on the flow.
LAG configuration includes the following steps:
1. Assigning a number to a LAG.
2. Binding ports to the LAG
3. Assigning a name to the LAG
4. Storing the LAG.
7-46 <LAG Protection Megaplex-4

 To add a LAG:
2. Type lag and enter a LAG number (1 or 2).
The config>port>lag(number)# prompt is displayed.
Note LAGs must be added in consecutive order. This means LAG 2 must be added after
LAG 1.
 To configure the LAG:

• At the config>port>lag(number)# prompt, enter all necessary commands
Adding a GBE port to the bind ethernet <slot/port> Using no before bind removes a link from LAG
LAG
Assigning a name to the name <Alphanumeric string> Maximum name length is 64 characters
LAG
Selecting the type of admin-key giga-ethernet The only possible option for the current
ports protected by LAG version is giga-ethernet: GbE ports
Enabling LACP and setting lacp [tx-activity {active | tx-activity:

LACP parameters: passive}] [tx-speed {slow | active – LAG interface periodically transmits
operation mode (active fast}] [sys-priority <0..65535>] LACP frames (LACPDUs) to all links with LACP
or passive), time to wait enabled
before sending LACP
passive – LAG interface does not initiate the
frames (long or short)
LACP exchange, but replies to received
and system priority
LACPDUs.
tx-speed:
slow – 90 seconds
fast_– 3 seconds
no lacp disables LACP protocol.
Assigning a queue group queue-group profile <profile no queue-group removes queue group
profile name> association
Assigning method of distribution-method dest-mac The only possible option is dest-mac: packets
distributing traffic within <slot/port> are distributed according to their destination
LAG MAC addresses
Disabling the LAG shutdown Using no shutdown enables the LAG
Displaying bind status show bind
Displaying LAG status show status
Displaying the LAG show lacp-statistics ethernet

members statistics <slot/port>

Displaying LAG members show lacp-status ethernet

status <slot/port>
For example:
 To create a LAG with packets distributed according to their destination MAC

addresses:
• LAG number – 1
• LAG members – GbE Port 1 and GbE port 2of a CL.2 module installed in slot
CL-A.
configure slot cl-a card-type cl cl2-622gbe
configure slot cl-b card-type cl cl2-622gbe
config port lag 1 bind ethernet cl-a/1
config port lag 1 bind ethernet cl-a/2
config port lag 1 admin-key giga-ethernet
config port lag 1 distribution-method dest-mac
config port lag 1 no shutdown
 To create a flow between this LAG and a fast Ethernet port of an ASMi-54C/N
module installed in I/O slot 1:
config flows classifier-profile 1000 match-all match vlan 1000
config flows flow 5 classifier 1000

config flows flow 5 ingress-port ethernet 1/1
config flows flow 5 egress-port lag 1
config flows flow 5 no shutdown
config flows flow 6 classifier 1000

config flows flow 6 ingress-port lag 1
config flows flow 6 egress-port ethernet 1/1
config flows flow 6 no shutdown
commit
 To delete a LAG:
mp4100#configure port no lag 1
Displaying LAG Status

 To display the status of a specific LAG:
mp4100>config>port>lag(1)$ show status
Name : lag 01
Displaying LACP Status

You can display the current status of LACP for each LAG member.

 To display LACP status:

• At the config>port>lag(1–44) #prompt, enter show lacp-status ethernet
<slot/port>.
The LACP statistic counters are displayed.
mp4100>config>port>lag(1)# show lacp-status ethernet cl-a/1
Ports
-----------------------------------------------------------------------------
Actor Partner
Port Number : 3004 0
Port Priority : 32768 0
System ID : 0020D2517B1D 0020D25171BE
System Priority : 32768 32768
Operational Key : 2 31
Activity : Active Active
Timeout : Short Short
Synchronized : Yes Yes
Collecting : Yes Yes
Distributing : Yes Yes
The LACP status screen provides information on the current state of the local
(actor) and remote (partner) interfaces in an LACP exchange.
Table 7-12. LACP States
Counter Description
Actor Local device participating in LACP negotiation
Partner Remote device participating in LACP negotiation
Activity Actor or partner's port activity. Passive indicates the port's preference
for not transmitting LAC PDUs unless its partner's control value is Active.
Active indicates the port's preference to participate in the protocol
regardless of the partner's control value.
Timeout LACP timeout preference. Periodic transmissions of LACP PDUs occur at

either a slow or fast transmission rate, depending upon the expressed
LACP timeout preference (Long Timeout or Short Timeout)
Synchronized If the value is Yes, the link is considered synchronized. It has been
allocated to the correct link aggregation group, the group has been
associated with a compatible aggregator, and the identity of the link
aggregation group is consistent with the system ID and operational key
information transmitted. If the value is No, the link is not synchronized.
It is currently not in the right aggregation.
Collecting Yes indicates collection of incoming frames on the link is currently

enabled and is not expected to be disabled. Otherwise, the value is No.
Distributing No indicates distribution of outgoing frames on the link is currently

disabled and is not expected to be enabled. Otherwise, the value is Yes.
Displaying LAG Statistics

 To display LAG statistics:

mp4100>config>port>lag(1)# show statistics

Running
---------------------------------------------------------------
Counter Rx Tx
Total Frames 21241092 7431095
Total Octets 4948371714 0
Unicast 12010124 0
Multicast 0 0
Broadcast 9230656 7431095
Paused Frames 0 0
FCS Errors 0 --
Table 7-13. LAG Statistics Parameters
Unicast Total number of unicast frames received/transmitted
Multicast Total number of multicast frames received/transmitted
Broadcast Total number of broadcast frames received/transmitted
Paused Frames Total number of pause frames (used for flow control) received/transmitted through
the corresponding Ethernet port
FCS Errors The number of frames received on this interface that are an integral number of octets
in length but do not pass the FCS check
Displaying LACP Statistics

You can display current LACP statistics for each LAG member.
 To display LACP statistics:

• At the config>port>lag(1–44) #prompt, enter show lacp-statistics ethernet
<slot/port>.
The LACP statistic counters are displayed.
mp4100>config>port>lag(1)# show lacp-statistics ethernet cl-a/1
LACP
-----------------------------------------------------------------------------
Rx LACP Frames : 43
Rx Marker Frames : 0
Rx Unknown Frames : 0
Rx Illegal Frames : 0
Tx LACP Frames : 46
Tx Marker response Frames : 0
Table 7-14. LACP Statistic Counters
Counter Description
Rx LACP Frames Number of valid LACP PDUs received

Counter Description
Rx Marker Frames Number of valid Marker PDUs received

Rx Unknown Frames Number of unrecognized packet errors
Rx Illegal Frames Number of invalid packets received
Tx LACP Frames Number of valid LACP PDUs transmitted
Tx Marker Response Frames Number of valid Marker Response PDUs received
error is detected.
553 Error ILLEGAL NUMBER OF LAGs Only a single LAG can be configured between two CL cards
BETWEEN CL CARDS
554 Error ILLEGAL NUMBER OF LAG At least two members must be defined in a LAG
MEMBERS
555 Error LAG MEMBER IS SHUTDOWN A LAG member should be in no shutdown state
7.8 Path Protection for SDH/SONET Payload
Factory Defaults
In Revertive mode, the wait-to-restore time is 300 sec.
Path (trail) protection is available for user-specified payload units (VC-12 for SDH
links, or VT1.5 for SONET links) mapped to VCG. Up to 252 VC path protection
groups can be defined by the user.
When path protection is enabled, the protected payload unit is assigned
bandwidth on both network links:
• The same payload is transmitted on both links.
• The receive interfaces of the two links continuously evaluate the received
signals. As long as the working path operates satisfactorily, its signal is
selected for processing. When the working path signal fails, or is degraded,
the receive side rapidly selects the other signal for processing.
Provisioning appropriate alternative paths through the network ensures that in
case of a fault anywhere along the active path, the traffic is automatically
switched to the standby path.
Megaplex-4 Path Protection for SDH/SONET Payload 7-51


• Non-revertive mode – the CL module will not automatically flip back after the
failed port returns to normal operation, but only when the currently used
port fails (that is, when its alarm weight exceeds that of the standby port).
• Revertive mode – the CL module will flip back to the original port when it
returns to normal operation (that is, its alarm weight is equal to, or lower
than, that of the currently active port).
Configuring VC Path Protection
Adding and Removing a VC Path Protection Group
 To add and define a VC path protection group:

2. Enter vc-path <path name>. The path name may consist of up to 80
alphanumeric characters.
The VC path protection group is defined and enabled and the
config>protection>vc-path(<path name>)# prompt appears.
 To remove a VC path protection group:

• At the config>protection# prompt, enter no vc-path <path name>.
The VC path protection group is removed.
Binding Ports to a VC path Protection Group
 To configure the SDH/SONET path protection:

• At the config>protection>vc-path(group name)# prompt, enter all necessary
Assigning a name to the VC name <up to 80 characters>

path protection group
Activating the VC path no shutdown Using shutdown switches the VC path

protection group protection group to standby mode
Adding a working/protection bind {working | protection} The number and type of working and
port to the VC path protection vc-vt <slot>/<port>/<au4>/ protection ports must be identical.
group <tug_3>/<tug_2>/<tributary> Using no before bind removes a port
from VC path protection group.
Enabling the reverting of the revertive In case reverting is selected, the

working and protection ports wait-to-restore time must be defined.
Using no revertive disables the
reverting.
7-52 Path Protection for SDH/SONET Payload Megaplex-4

Defining the wait-to-restore wait-to-restore <1–720> The unit of time is seconds.

period for the revertive Note. The last configured
recovery mode (the time to wait-to-restore value is copied to all VC
elapse after the link recovery path protection groups throughout the
before traffic switches back) system, so that the wait-to-restore
value is always the same for all vc-vt
ports.

from the protection port to
the working port

from the working port to the
protection port

normal operation.
Viewing the Status of a VC Path Protection Group

This section illustrates the status display of a VC path protection group.
 To view the VC path protection group status:

• At the config>protection>vc-path(<group name>)# prompt, enter show
status.
The VC path protection group status appears.
 In this example, the VC path protection group name is test.
mp4100>config>protection>vc-path(test)# show status
Group
-----------------------------------------------------------------------------
Mode : 1+1
Cards
-----------------------------------------------------------------------------
Working VC Admin Oper Active
-----------------------------------------------------------------------------
Protection Sdh-Sonet cl-a/1/1/1/1/1 Up Up --
Working Sdh-Sonet cl-a/2/1/1/1/1 Up Up Yes
Example
 To add and configure an VC path protection group:
• VC-path protection group name – test
• Working port: slot=cl-a, sdh port=2, aug=1, tug3=1, vc12=1, tributary=1
Megaplex-4 Path Protection for SDH/SONET Payload 7-53

• Protection port: slot=cl-a, sdh port=1, aug=1, tug3=1, vc12=1, tributary=1

• Reverting is enabled
mp4100>config>protection> vc-path(test)#revertive
• Wait-to-restore time is 25 sec.
mp4100#configure protection vc-path(test)#bind working sdh-sonet cl-a/2/1/1/1/1
mp4100>config>protection> vc-path(test)#bind protection sdh-sonet cl-a/1/1/1/1/1
mp4100>config>protection> vc-path(test)#revertive
mp4100>config>protection> vc-path(test)#wait-to-restore 25
 To delete VC path protection group named test:

mp4100#configure protection no vc-path test
detected.
Table 7-16. VC Path Protection Configuration Error Messages
607 Error MISSING MEMBER IN VC-path group must contain two members. Bind another
PROTECTION GROUP port to the group
608 Error ILLEGAL PROTECTION GROUP Path Protection cannot be configured on bypassed VC/VTs.
DEFINITION See also Error 608 in Ethernet Group Protection and PW
Protection for additional meanings.
7.9 PW Protection
PW protection mechanism protects pseudowire traffic in case of network path
failure. The user defines different network paths for the working and protection
pseudowires. This type of protection is supported by all the PW-equipped
modules except for MPW-1, and is configured between two different PWs on the
same module.
Benefits
The PW protection provides the following main advantages:
• Provides zero packet loss protection
7-54 PW Protection Megaplex-4

below).
Standards
PW Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with PW protection disabled.
For PW protection, two PW ports on the same module are connected to the same
DS1 port. A typical configuration is shown in the figure below.
The working and protection PWs must be configured with the same psn
parameter: either udp-over-ip or ethernet.
During normal operation, both PW ports process as usual the transmit and receive
signals, but the receive output of the protection port is disconnected.
During normal operation, the operational state of the protection PW is
continuously monitored to ensure that it is operating properly. In the case of
faulty condition on the working PW, the traffic is routed on the protection PW,
via another route not suffering from the same faulty conditions.
The protection mode is non-revertive.
PW #1 GbE
SVI #1
Working CL-A/1
I/O
DS1
Serial Port
PW #2 GbE
SVI #2
Protection CL-B/1
Figure 7-13. PW Protection
Working and Protection Port Parameters

For two ports configured to PW protection, the following parameters must be the
same for both ports:
• psn type (udp-over-ip or Ethernet)
• tdm-oos
• tdm-payload.
Configuring PW Protection
The PW protection is configured as follows.
Megaplex-4 PW Protection 7-55

 To add an PW protection group:

2. Type pw and enter a group number.
The config>protection>pw(group number)# prompt is displayed.
 To configure the PW protection group:

• At the config>protection>pw(group number)# prompt, enter all necessary
Assigning a name to the name <up to 80 characters>

PW protection group

TDM group
Adding working and bind {working | protection} Using no bind protection removes the
protection modules <slot> protection port from the group. There is
slots to the PW protection no need to remove the working port from
group the group.
Defining operation mode oper-mode 1-plus-1 Permanently set to 1-plus-1

of the PW protection
Example
 To add and configure a PW protection group:
• VS-12 module
• Working PW number – 1
• Protection PW number – 2
mp4100>config# protection
mp4100>config>protection# pw 4
mp4100>config>protection>pw(4)$ bind working 1
mp4100>config>protection>pw(4)$ bind protection 2
mp4100>config>protection>pw(4)$ no shutdown
 To delete PW protection group 4:

mp4100#configure protection no pw 4
detected.
7-56 PW Protection Megaplex-4

608 Error ILLEGAL PROTECTION GROUP Verify one of the following:

DEFINITION • Neither working nor protection PWs belong to the
MPW-1 module (MPW-1 does not support PW
protection).
• Working and protection PWs belong to the same
module.
See also Error 608 in Ethernet Group Protection and Path
Protection for SDH/SONET Payload for additional
meanings.
Viewing the PW Protection Status

This section illustrates the status display of a PW protection group.
 To view the PW protection group status:

• At the config>protection>pw (<group number>)# prompt, enter show status.
The PW protection group status appears. In this example, the PW
protection group number is pw1.
Group
------------------------------------------------------------------
Mode : 1+1
Last Switchover Time : last-switchover-time1
Last Switchover Reason : None
Last Command : None
------------------------------------------------------------------
------------------------------------------------------------------
Working VC Admin Oper Active
-------------------------------------------------------------------
protection pw1 Up Up Yes
working pw1 Up Up Yes
-------------------------------------------------------------------
7.10 TDM Group Protection

One of the simplest methods to protect against link and hardware failure is to
use the TDM group protection. This type of protection is used for e1, e1-I, t1,
t1-i, ds1, t3, mux-eth-tdm and cmd-channel ports.
For E1/T1/DS1/DS1-opt ports, the protection partner ports can be located on
either the same module, or another module, and can be of any of the following
depending on the interface type:
• For external/internal E1 ports: external E1 ports, internal E1 ports of OP
modules, internal E1 ports of CL modules, or internal E1 ports of M8SL and
Megaplex-4 TDM Group Protection 7-57

ASMi-54C/N modules, DS1-opt ports of VS-6/C37 modules or DS1 ports of

MPW-1 and VS modules.
• For external/internal T1 ports: external T1 ports, internal T1 ports of OP
modules, internal T1 ports of T3 modules, internal T1 ports of CL modules,
DS1-opt ports of VS-6/C37 modules or DS1 ports of MPW-1 and VS modules
For optical links (mux-eth-tdm ports) of OP modules, the protection partner port
is located on the same module and must be the following:
• mux-eth-tdm 2 is always a protection partner for mux-eth-tdm 1 (OP-34C,
OP A section of OP-108C)
• mux-eth-tdm 4 is always a protection partner for mux-eth-tdm 3 (OP B
section of OP-108C)
For CMD channels (cmd-channel ports) of TP modules, the protection partner port
is located on the same module and must be the following:
• cmd-channel 2 is always a protection partner for cmd-channel 1
• cmd-channel 4 is always a protection partner for cmd-channel 3.
The maximum total number of TDM groups that can be configured for Megaplex-4
is 144.
Benefits
The TDM group protection provides two main advantages:
below).
Standards
TDM Group Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with TDM protection disabled. Other parameter defaults
oper-mode dual-cable-tx
revertive/no revertive no revertive for cmd-channel ports

revertive for other ports
wait-to-restore 300 sec
7-58 TDM Group Protection Megaplex-4

The TDM group (dual-cable) configuration provides protection against both
transmission path failure and technical failure in the module hardware.
For this type of protection, two ports of the same type are connected to the
remote unit via two parallel links. Defining these two links as a TDM protection
group ensures that traffic carrying capacity is available even if one of the links
fails. These ports can be as follows:
• e1/e1-i/ds1/ds1-opt ports
• t1/t1-i/ds1/ds1-opt ports
• mux-eth-tdm ports of Optimux modules
• cmd channels of TP modules
• t3 ports of T3 modules.
Figure 7-14 shows a typical system configuration using dual-cable protection. The
user can select the module ports operating as a TDM group. Both ports process as
usual the transmit and receive signals, but the receive output of the protection
port is disconnected.
During normal operation, the operational state of the protection port is
continuously monitored to ensure that it is operating properly. If the working link
fails, the corresponding port is disconnected, and the protection port takes over.
The maximum switching time between main and backup ports is 50 msec.
Therefore protection switching will ensure essentially uninterrupted service for all
the types of applications; in particular, it will not cause the disconnection of voice
calls.
I/O Module with I/O Module with

E1 or T1 Ports E1 or T1 Ports
Working (Active) Link
Protection (Standby) Link

Megaplex-4100 Megaplex-4100
Figure 7-14. E1/T1 Link Protection Using Dual Cables (TDM Group)
Working and Protection Port Parameters

For two ports configured to TDM group protection, the following parameters
must be the same for both ports.
For E1/T1/E1-i/T1-i ports: Admin Status
• line-type
• line-code
• inband-management > timeslot
• inband-management > protocol
• inband-management > routing-protocol
For DS1 and DS1-opt ports:

• Admin Status
• line-type
• signaling
For cmd channels of TP modules:
• rate & trigger-mode
For T3 ports:
• Admin Status
• line-type.
Protection Mode
• Non-revertive mode – the module will not automatically flip back from
protection to working port after the working port returns to normal
operation, but only when the currently used port fails.
• Revertive mode – the module will flip back from protection to working port
when it returns to normal operation.
To prevent switching under marginal conditions, the user can specify a
restoration time (wait-to-restore). This is the minimum interval before flipping
back to the original port. During the restoration time, alarms with the same
weight, or with lower weights, are ignored. As a result, the module starts
evaluating the criteria for protection switching (flipping) only after the
restoration time expires, thereby ensuring that another flip cannot occur before
the specified time expires.
However, if an alarm with a weight exceeding that of the alarm which caused
flipping appears, immediate flipping will occur, even if the restoration time has
not yet expired.
Traffic Duplication
Traffic Duplication is a new technology developed by RAD for enhanced reliability
and performance, used to minimize delay on critical utility applications (such as
teleprotection). This technology is implemented in MPW-1 I/O module.
Mission-critical traffic can be transported over a new Carrier Ethernet network
running in parallel with the existing SDH/SONET network, while preparing for
future full service migration.
This type of protection employs three members and is implemented by defining
two TDM groups with a common member (see Example 5). One tdm group is
configured between two e1-i/t1-i ports on the CL.2 module and the second
tdm-group is configured between one of the e1-i/t1-i partners in the previous
group and a ds1 port of MPW-1 module.
Megaplex-4 duplicates the TDM service to two parallel flows:
• Towards the TDM uplink (PDH or SDH/SONET) based on its internal TDM
cross-connect. When transported over SDH/SONET it is also protected using
path protection.

• Towards the Ethernet uplink (single or Ring) using PWE encapsulation. The
figure below shows a G.8032 ring used to protect the Ethernet service.
Figure 7-15. Adding Traffic Duplication to an Existing SONET/SDH Network

through an Existing PSN
Configuring TDM Group Protection

The TDM Group Protection is configured as follows.
 To add a TDM protection group:

2. Type tdm-group and enter a group number.
The config>protection>tdm-group(group number)# prompt is displayed.
 To configure the TDM protection group:

• At the config>protection>tdm-group(group number)# prompt, enter all

TDM group
Defining operation mode oper-mode {y-cable | dual-cable- Y-cable protection (available in

of the TDM group tx} M8E1/M8T1 modules only) is supported
for backward compatibility. Instead of this
mode, use I/O group protection described
in the I/O Group Protection section below.

Adding working and bind {working | protection} e1 Using no bind protection (e1/e1-i/ds1)
protection <slot>/<port>/[<tributary>] removes the protection port from the
e1/e1-i/ds1 bind {working | protection} e1-i group. There is no need to remove the
ports to the TDM group <slot>/<port> working port from the group.
bind {working | protection} ds1 [<tributary>] relates to Megaplex Optimux
<slot>/<port> cards (OP-34C, OP-108C) as protection
ports (for internal E1 port numbering in
Optimux modules, see relevant section of
Appendix B).
An e1 port of VS-16E1T1-EoP module
bound to a VCG cannot be configured as a
partner in tdm-group.
An e1 port of VS-16E1T1-PW or VS-6/E1T1
module cross connected directly to PW
cannot be configured as a partner in tdm-
group.
Adding working and bind {working | protection} t1 Using no bind protection (t1/t1-i/ds1)
protection t1/t1-i/ds1 <slot>/<port>/[<tributary>] removes the protection port from the
ports to the TDM group bind {working | protection} t1-i group. There is no need to remove the
<slot>/<port> working port from the group.
bind {working | protection} ds1 [<tributary>] relates to internal T1 ports of
<slot>/<port> T3 modules.
If TDM group protection is configured for a
T3 port, the same type of protection is
also automatically configured on all the
open internal T1 ports belonging to this T3
module. The T1 members belonging to
such a group have the same numbers. The
group numbers start from 200.
You can also configure TDM group
protection on individual selected T1 ports
if their T3 ports are not configured to
protection.
A t1 port of VS-16E1T1-EoP module
bound to a VCG cannot be configured as a
partner in tdm-group.
A t1 port of VS-16E1T1-PW or VS-6/E1T1
module cross connected directly to PW
cannot be configured as a partner in tdm-
group.

Adding working and bind {working | protection} t3 Using no bind protection t3 removes the
protection t3 ports to <slot>/<port> protection port from the group. There is
the TDM group no need to remove the working port from
the group.
Once TDM group protection is configured
for the T3 port, the same type of
protection is also automatically configured
on all the open internal T1 ports belonging
to this T3 module.
Adding working and bind {working | protection} Using no bind protection mux-eth-tdm
protection mux-eth-tdm <slot>/<port> removes the protection port from the
mux-eth-tdm group. There is no need to remove the
ports to the TDM group working port from the group.
Adding working and bind {working | protection} 1,3 – working channels

protection cmd-channel cmd-channel <slot>/<port> 2, 4 – protection channels
ports to the TDM group
Using no bind protection cmd-channel
removes the protection port from the
group. There is no need to remove the
working port from the group.
Enabling the reverting of revertive Using no revertive disables the reverting

the working and protection The reverting value (revertive/no revertive)
ports configured for a T3 port TDM protection
group is automatically copied to the TDM
protection groups of all T1 ports belonging
to this T3.
Defining the wait-to- wait-to-restore <0–720> The unit of time is seconds. For
restore period (after the mux-eth-tdm ports, the wait-to-restore
switching criteria are time is always 0.
cleared, the time to elapse The wait-to-restore value configured for a
before traffic T3 port TDM protection group is
switches back) automatically copied to the TDM
protection groups of all T1 ports belonging
to this T3.

from the protection port
to the working port

from the working port to
the protection port

Manual switching of traffic manual-switch-to-working

from the protection port
back to the working port,
unless a failure condition
exists on the working port
or an equal/higher priority
effect
Forced switching of traffic manual-switch-to-protection

from the working port to
the protection port, unless
a failure condition exists
on the protection port or
an equal/higher priority
effect

normal operation.
Example 1
 To add and configure an E1/T1 protection group:
• Working link – Port 1 of the module installed in slot 6
• Protection link – Port 2 of the module installed in slot 5
• Operation mode – dual cable protection
mp4100#configure protection tdm-group 2 bind working e1 6/1
mp4100#configure protection tdm-group 2
mp4100>config>protection>tdm-group (2)#bind protection e1 5/2
mp4100>config>protection>tdm-group (2)#wait-to-restore 200

mp4100#configure protection no tdm-group 2
Example 2
 To add and configure an optical link protection group:

• Operation mode – dual cable protection (this is the only option so the 3rd
string is optional)
mp4100#configure port mux-eth-tdm 1/2
mp4100#configure protection tdm-group 1 bind working mux-eth-tdm 1/1
mp4100#configure protection tdm-group 1 bind protection mux-eth-tdm
1/2
mp4100#configure protection tdm-group 1 oper-mode dual-cable-tx
 To display the protection status:

mp4100>config>protection>tdm-group(1)# show status
Group
---------------------------------------------------------------
Mode :
Cards
---------------------------------------------------------------
Working Mux Eth TDM 1/1 Up Up Yes
Protection Mux Eth TDM 1/2 Up Down --

Example 3
 To add and configure an internal E1 protection group on OP-108C
• Working link – Port 1 of Section OP A of the module installed in slot 1
• Protection link – Port 4 of Section OP B of the module installed in slot 2
string is optional)
mp4100#configure protection tdm-group 3 bind working e1 1/1/1
mp4100#configure protection tdm-group 3 bind protection e1 2/3/4
mp4100#configure protection tdm-group 3 oper-mode dual-cable-tx


Group
---------------------------------------------------------------
Mode :
Cards
---------------------------------------------------------------
Working E1 1/1/1 Up Up Yes
Protection E1 2/3/4 Up Down --
Example 4
 To add and configure an CMD Channel protection group on TP module:
• Working link – CMD channel 1 of the module installed in slot 4
• Protection link – CMD channel 2 of the module installed in slot 4
string is optional)
• Not revertive
config protection tdm-group 1 bind working cmd-channel 4/1
config protection tdm-group 1 bind protection cmd-channel 4/2
config protection tdm-group 1 oper-mode dual-cable-tx
config protection tdm-group 1 no-revertive

Group
---------------------------------------------------------------
Mode : Dual Cable Tx
Cards
---------------------------------------------------------------
Working Cmd Channel 4/1 Up Up Yes
Protection Cmd Channel 4/2 Up Up --
Example 5.
 To configure traffic duplication:
 Working link – Port E1-i 1 of CL-A module
 Protection link – Port E1-i 1 of CL-B module
 Operation mode – dual cable protection (this is the only option so the 3rd
string is optional)

 Working link – Port E1-i 1 of CL-A module

 Protection link – Port DS1 1 of MPW-1 module installed in slot 3
 Operation mode – dual cable protection (this is the only option so the 3rd
string is optional)
configure protection
##### CL E1-i_Protection #####

tdm-group 1
bind working e1-i cl-a/1
bind protection e1-i cl-b/1
no revertive
exit
##### CL E1-i - MPW IntDs1_Protection #####

tdm-group 2
bind working e1-i cl-a/1
bind protection ds1 3/1
revertive
wait-to-restore 60

Group
---------------------------------------------------------------
Mode :
Cards
---------------------------------------------------------------
Working E1-I CL.A/1 Up Down --
Protection E1-I CL.B/1 Up Down --

Group
---------------------------------------------------------------
Mode :
Cards
---------------------------------------------------------------
Working E1-I CL.A/1 Up Down --
Protection E1-I DS1 3/1 Up Up Yes
The tdm group employing two CL e1(t1)-i ports must be configured to
non-revertive mode. The second tdm group (employing CL e1(t1)-i and MPW-1
ds1 ports) can be either revertive or non-revertive.

Example 6
 To add and configure a T3 protection group:
• Working link – T3 Port (1) of the module installed in slot 9
• Protection link – T3 Port (1) of the module installed in slot 8
• All other parameters are at their defaults.
mp4100#configure protection tdm-group 1 bind working t3 9/1
mp4100#configure protection tdm-group 1 bind protection t3 8/1
 To display the results:

mp4100>config>protection# info detail
echo "TDM Group Protection"
# TDM Group Protection
tdm-group 1
bind working t3 9/1
bind protection t3 8/1
exit
tdm-group 200
bind working t1 9/1/3
bind protection t1 8/1/3
exit
tdm-group 201
exit
tdm-group 202
exit
The display includes the created T3 TDM protection group 1 and T1 TDM
protections groups 200, 201 and 202 automatically created for all open T1 ports.
 To display the status of each T1 protection group:

mp4100>config>protection# tdm-group 200
Group
----------------------------------------------------------------------
Mode : Dual Cable Tx
Last Command :
Cards
----------------------------------------------------------------------
Working T1 9/1/3 Up Up Yes
Protection T1 8/1/3 Up Down --


detected.
Table 7-18. TDM Group Protection Configuration Error Messages
140 Error ILLEGAL TDM PROTECTION The protection assignment of one port does not point to
ASSIGNMENT another port
142 Error PORT CAN PARTICIPATE ONLY An E1/T1 port cannot be member of several TDM
IN ONE TDM GROUP protection groups.
420 Error MLPPP PORT CAN'T BE BOUND E1 port bound to MLPPP port cannot be a member of
TO TDM GROUP protection group
476 Error PROTECTED PORTS HAVE When TDM protection is configured between two DS1
ASSYMETRIC PARAMETERS ports, all their physical layer parameters must be identical
601 Error WORKING & PROTECTION ARE The same port cannot be defined as both working and
ON THE SAME PORT protection port
602 Error UNFRAMED TYPE CAN'T BE A Unframed E1/T1 ports of OP-108C/34C, M16E1/M16T1,
MEMBER OF TDM GROUP ASMi-54C/N modules cannot be selected as members of
TDM group
603 Error PORT PARAMETERS OF For two ports configured to TDM group protection, the
MEMBERS ARE ASSYMETRIC following parameters must be the same for both ports.
For E1/T1/E1-i/T1-i ports:
• Admin Status
• line-type
• line-code
• inband-management > timeslot
• inband-management > protocol
• inband-management > routing-protocol
For cmd channels of TP modules:
• rate & trigger-mode
For T3 ports:
• Admin Status
• line-type.
604 Error PROTECTION PORT IS IN One of the ports in tdm protection group is in shutdown
SHUTDOWN STATE state

610 Error ILLEGAL TRAFFIC DUP Incorrect traffic duplication configuration. The protection
MEMBERS DEFINITION members must be configured by using the two following
tdm-group entries:
TDM GROUP 1
Working Port: CL e1(t1)-i X
Protection Port: CL e1(t1)-i Y
TDM GROUP 2
Working Port: e1(t1)-i X (CL.2 module), same as in group 1
Protection Port: ds1 (MPW-1 module)
611 Error TRAFFIC DUP ENTRY MUST BE In traffic duplication configuration, the tdm group
NON REVERTIVE employing two CL e1(t1)-i ports, must be configured to
non-revertive mode.
612 Error IN T3 PROTECTION, MEMBERS The following asymmetrical ports were manually defined
MUST BE SYMMETRIC by the user on the T3 module:
• either T1 ports as TDM group protection members
• or Logical MAC ports as Ethernet group protection
members.
These members must be symmetric for working and
protection T3 module slots.
683 Error ILLEGAL CMD CHANNEL Cmd-channel protection members must satisfy the
PROTECTION ASSIGNMENT following conditions:
• Working and protection ports must belong to the same
slot
• Working ports must be Cmd-Channels 1 or 3
• Protected ports must be either Cmd-Channel 2 (for
working port 1) or 4 (for working port 3); no other
option is allowed.
777 Error PORT DISABLED ON PRIMARY A T1 or Logical MAC port was defined as a member of T3
TDM-GROUP MEMBER TDM protection group in the protection module slot, while
is not opened in the working module slot.
7.11 TDM Ring Protection

The TDM ring protection (E1/T1 ring redundancy) is a RAD proprietary topology
suitable for Megaplex-4 equipment. It provides higher availability for critical
applications at the E1 and T1 level, with fast protection switching time.
The maximum total number of TDM rings that can be configured for Megaplex-4 is
16.
7-70 TDM Ring Protection Megaplex-4

Benefits
E1/T1 ring protection can use the same cabling infrastructure as regular
point-to-point links, and provides several significant advantages:
• There is no single point of failure
• Rapid switching time in case of failure
• Does not require additional hardware. Any daisy chain topology can be
converted to an E1/T1 ring topology by connecting two additional pairs
between the E1, T1 port at the end of the chain to the E1/T1 port beginning
the chain (on the first Megaplex-4)
• Flexible solution (any Megaplex-4 unit in the ring can connect to additional
rings)
• Simple to configure: requires the same timeslot assignment as a chain
topology, except that at each node it is necessary to bypass timeslots that
are not used for local payload between the working and protection E1/T1
ports.
Standards
TDM Ring Protection is RAD proprietary technology.
Factory Defaults
Megaplex-4 is supplied with TDM ring protection disabled. The default
wait-to-restore time is 300 sec.
Figure 7-16 illustrates TDM Ring Protection topology. The links comprising the
ring can include E1 and T1 physical links. The different types of links can be
intermixed along the same ring, without requiring any media converters or
modems.
Figure 7-16. TDM (E1/T1) Ring Topology
Megaplex-4 TDM Ring Protection 7-71

TDM (E1/T1) ring protection is based on the use of two transmission paths, each
requiring a single twisted pair: one pair, called the working, is used instead of the
legacy transmit pair, and the other, called the protection, is used instead of the
legacy receive pair. Therefore, E1/T1 ring protection can use the same cabling
infrastructure as regular point-to-point links.
The E1/T1 ring protection topology can be efficiently implemented by any pair of
physical or internal (logical) E1 or T1 ports, as available on M8E1, M8T1, M8SL,
etc. Any pair of ports, even ports located on different modules, can be configured
as a protection group.
Any port participating in the TDM ring can automatically choose an appropriate
timing reference or data flow direction in accordance with internal messages
and/or alarms in the system.
Note When using inband management carried over a dedicated timeslot, you need to
add a Proprietary RIP or RIP2 routing protocol (inband-management <timeslot>
protocol {ppp | fr} routing-protocol {prop-rip | rip2}. It is highly recommended to
use RIP2 protocol rather than Proprietary RIP.
Figure 7-17 shows a typical application that uses the ring protection topology.
In each Megaplex-4 unit on the ring, two E1 or T1 ports (identified as port 1 and
port 2 in Figure 7-17) are defined as a protection group pair. One port of each
unit (in this example, port 2) is configured as working port: under normal
conditions, each Megaplex-4 transmits data to the next node through the working
port, and receives through the protection port. Timeslots not connected to local
channels are bypassed.
Working Ring
Protection 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
Working Working Working Working Working
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 7-17. E1/T1 Ring Protection – Signal Flow during Normal Operation
The payload is handled as follows:

• Working ring: at each unit, timeslots used at the local unit are dropped from
the receive side of the protection port, and added to the transmit side of the
working port. Timeslots used by the other Megaplex-4 units are bypassed
directly between these two ports.
• Protection ring: all the timeslots received by port 2 are bypassed to the
transmit side of port 1.

If one of the segments in the ring fails (see Figure 7-18), the CL modules of the
two Megaplex-4 units adjacent to the failure point detect the loss of signal and
change the signal routing within the corresponding units. Therefore, each unit
now receives and transmits only through the synchronized port. Timeslots
previously bypassed between the ports are now transferred between the receive
and transmit sides of the active port by a connection similar to the remote
loopback, thereby preserving transmission path continuity.
Working Ring
Protection 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
Working Working Working Working Working
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 HS-6N
A B C D
User's Equipment User's Equipment User's Equipment User's Equipment User's Equipment
Figure 7-18. E1/T1 Ring Protection – Signal Flow after Segment Failure
Note that all the other Megaplex-4 units do not change their operating
configuration: only the units that are connected to the failed segment take action
in response to the failure.
Notes
• To prevent unnecessary switching to the protection path, do not activate
remote loopbacks, or loopbacks on timeslots, on ports connected to the ring.
• When it is necessary to perform local bypassing (on the same module) from
another port to one of the ports participating in ring protection, you can do
that only for the working port; for the protection port, you get an error
message.
To save duplication of configuration parameters, all the E1/T1 port parameters

are selectable only for the working port. The parameters of the other
(protection) port are automatically copied from the working port after the
configuration of the working port has been completed and the database has
been updated. However, you can select different interface-type for the working
and protection ports, where this parameter is applicable.
The recovery mode after redundancy switching is always revertive – which means
that the traffic will be automatically redirected back to the original group when it
returns to normal operation.
Configuring TDM Ring Protection

 To add a TDM protection ring:
1. Navigate to configure>protection#.
2. Type tdm-ring and enter a ring number.
Megaplex-4 TDM Ring Protection 7-73

The config>protection>tdm-ring(ring number)# prompt is displayed.
 To configure the TDM ring protection:

• At the config>protection>tdm-ring(ring number)# prompt, enter all necessary
Administratively enabling no shutdown Using shutdown disables the ring

TDM ring
Adding working and bind {working | protection} e1 Using no bind protection (e1/e1-i)
protection e1/e1-i <slot>/<port>/[<tributary>] removes the protection port from the
ports to the TDM group bind {working | protection} e1-i group. There is no need to remove the
[<tributary>] relates to Megaplex
Optimux cards (OP-34C, OP-108C) as
protection ports (for internal E1 port
numbering in Optimux modules, see
relevant section of Appendix B).
Adding working and bind {working | protection} t1 Using no bind protection (t1/t1-i/ds-1)
protection t1/t1-i <slot>/<port>/ removes the protection port from the
ports to the TDM group bind {working | protection} t1-i group. There is no need to remove the
Defining the wait-to-restore wait-to-restore <time in seconds> 1..300..720

period (the time to elapse
after the link recovery
before traffic switches back)
Example
 To add and configure a TDM Ring protection group:
mp4100#configure protection tdm-ring 2 bind working e1 6/1
mp4100>config>protection> tdm-ring(2)#bind protection e1 5/2
mp4100>config>protection> tdm-ring(2)#wait-to-restore 200

mp4100#configure protection no tdm-ring 2
This document defines CLI commands for DS0 – SNC protection done by VS
modules.

Chapter 8
Networking
This chapter lists the commands used to configure network-related features:
management bridge and router, flows, pseudowire environment, cross-
connections and quality of service.
8.1 Bridge
The Megaplex-4 bridge is a VLAN-aware Layer-2 forwarding entity. Eleven bridge
instances can be created in the device: one bridge for the dual CL.2 modules and
one bridge for each M-ETH module.
Standards
IEEE 802.1D, 802.1Q
Benefits
The bridge is used to deliver EPLAN and EVPLAN (any-to-any) services.
Factory Defaults
By default, no bridge instances exist in the Megaplex-4 system.
A bridge is a forwarding entity used by Megaplex-4 for delivering E-LAN services
and G.8032 ring protection. 11 bridge instances can be defined in Megaplex-4:
one bridge for the CL subsystem (always bridge 1) and one bridge per M-ETH
module. In total, Megaplex-4 provides up to 170 bridge ports, subdivided as
follows:
• 80 ports on the CL.2 bridge
• 9 ports per M-ETH module bridge (8 external + 1 internal) – maximum 90
ports per chassis.
The bridge operates in VLAN-aware mode (IVL) with ingress filtering. It accepts
tagged frames only. To be admitted to the bridge, a frame’s VID must be
configured as a part of the bridge port VLAN member set. Untagged frames must
receive a relevant VID at port ingress (tag push) or they will be dropped.
The Megaplex-4 bridge supports up to 64 broadcast domains (bridge/VLAN) and a
MAC table with up to 16K entries. The MAC table flush is supported per bridge
Megaplex-4 Bridge 8-1

Chapter 8 Networking Installation and Operation Manual
instance. MAC address aging time is configured per chassis in the range of 60 to
3000 seconds (Default=300 seconds).
Megaplex-4 supports RSTP which can be used to prevent loops in Layer 2
networks and provides rapid convergence of the spanning tree.
Bridge Model
A bridge is defined by a bridge number, bridge ports and a VLAN membership
table that specifies which bridge ports are members in a certain broadcast
domain (VLAN).
Traffic in and out of a bridge port is configured using flows. This allows editing
action at ingress and egress bridge ports.
Bridge port to physical port mapping is always 1:1.
Deleting Bridge Elements

Deletion of bridge elements is performed in the following manner:
• All flows on the VLAN must be deleted before a VLAN member can be deleted
from a bridge port.
• All VLAN members of a bridge port must be deleted before the bridge port
can be deleted.
• All bridge ports must be deleted before the bridge can be deleted.
Using the Bridge for Management

Megaplex-4 management tasks are organized as shown in Figure 8-1. The
diagram shows the VLAN-aware management bridge, the management router 1
and their interconnections with management flows.
Note There are two routers in the Megaplex-4 architecture: Router 1 is used for inband
management, while Router 2 is used for pseudowire routing. Router 2 is
explained in the Router (Pseudowire) section.
Router 1 basic functionality is in connecting to control management stations

(such as PC) and accessing the Common Logic. By default, Megaplex-4 is managed
by Router 1, via Layer-3. If you want to manage the device via a management
VLAN (Layer-2 management), the bridge must be configured.
8-2 Bridge Megaplex-4

Installation and Operation Manual Chapter 8 Networking
mng-eth mng-eth
cl-a cl-b
RI#2
DTS
PPP
Router
BP#3 BP#2
DCC
RI#3
1 PPP
RI#1
Bridge#1 Aware Host
BP#1
SVI#1
Figure 8-1. Management Connectivity Diagram
The default management entities are created automatically by the system and are
in “no shutdown” state by default. These entities include Router 1 interface and
SVI port 1 connecting the router interface to the bridge. This SVI is not connected
to the bridge but represents Ethernet Control ports of both CL.2 modules.
The following table summarizes the default configuration file entities and their
automatically assigned ID numbers, which you can change later, if needed.
Table 8-1. Default Configuration File Entities
Entity Number
Router 1 interface 1
SVI port connecting the router interface to the 1

bridge
Management traffic flowing through Ethernet connections is normally assigned a

dedicated VLAN. Within the Megaplex-4, inband management traffic can reach the
management subsystem on the CL modules through Ethernet ports, PCS, GFP,
MLPPP port or virtually concatenated groups carrying Ethernet traffic.
Admission to Bridge
In order for a frame to be admitted to the bridge, its classification must match
the flow classification configured for the bridge port.
In VLAN-aware mode, an Egress tagged port must be defined. Additionally, flows
with untagged classification must have a push editing action.
In VLAN-unaware mode (M-ETH bridges only), any packet may be admitted
according to the configured flow classifications.
Packet Editing on Reverse Flows

In the case of a bidirectional flow, the editing action can be specified for the flow
to the bridge port, but not for the reverse direction (while only reverse flows can
be configured between bridge ports and other ports of Megaplex-4). Megaplex-4
performs editing on the reverse direction according to the flow classification and

specified editing actions. The following table shows the editing action on the
reverse flow, as well as the VLAN learned from the flow.
Table 8-2. Packet Editing on Reverse Flows
Classification Editing of Flow with Editing of VLAN Value

Bridge Port as Egress Reverse
Port Directional Flow
VLAN X + any None None X
VLAN X..Y None Not allowed Not allowed
Untagged None None Not supported; use

push action
VLAN X None None X

Inner VLAN Y
Any classification Push X Pop X

(including untagged) p-bit fixed/copy/profile
Any classification Push X push inner Y Pop twice X

(including untagged and p-bit and inner p-bit
all) fixed/copy/profile
VLAN X Pop Push X Y

Inner vlan Y
VLAN X Pop Not allowed Not allowed

Inner vlan Y..Z
VLAN X Pop Not allowed Not allowed
VLAN X + any Swap VLAN Y Swap VLAN X Y

p-bit fixed/copy/profile
VLAN X Swap VLAN Z Swap VLAN X Z

Inner VLAN Y p-bit fixed/copy/profile
VLAN Y..Z Swap VLAN Y Not allowed Not allowed

VLAN X Push VLAN Y, swap VLAN Z Pop, swap X Y

VLAN Y..Z Push VLAN X, swap VLAN Z Not allowed Not allowed
VLAN X Pop, swap VLAN Z Push X Z

Inner VLAN Y p-bit fixed/copy/profile Inner swap to Y
VLAN X Pop, swap 200 Not allowed Not allowed

Inner VLAN Y..Z p-bit fixed/copy/profile
VLAN X Swap VLAN Z, Swap X, inner swap Y Z

Inner VLAN Y inner swap VLAN K

Classification Editing of Flow with Editing of VLAN Value

Bridge Port as Egress Reverse
Port Directional Flow
VLAN X Swap VLAN Z, Not allowed Not allowed

Inner VLAN Y..Z inner swap VLAN K
Spanning Tree Protocol

Spanning Tree Protocols (STPs) are Layer-2 loop avoidance techniques used in
Ethernet networks. Loops are created in bridge-based networks with more than
one path between two endpoints, when the bridges repeatedly rebroadcast the
broadcast/multicast messages, flooding the network. So, STPs are used to
identify the best path to the destination, and block all other paths. The blocked
links are not always discarded. They are connected and kept inactive, creating
automatic backup links.
Figure 8-2 illustrates STP operation. Bridge 3 is connected directly to Bridge 1 and
Bridge 2. Another physical link connects directly Bridge 1 to Bridge 2. Under
normal conditions, there will be looping of data, causing broadcast congestion on
the network. When an STP is applied, Link A is blocked from transmitting any
data, but it remains on standby and listens to the network. If Link B or Link C
fails, Link A is activated, providing link and switch redundancy in the network.
Link A Link A
Bridge 1 Bridge 2 Bridge 1 Bridge 2
Link B Link C Link B Link C
Bridge 3 Bridge 3
Physical Topology Logical Topology
Figure 8-2. STP Operation
STP Bridge Types

The root bridge is the central reference bridge in the STP. It serves as a reference
for other bridges to determine their best cost path. Bridge 3 in Figure 8-2 serves
as a root in the application.
The root bridge is elected by selecting the bridge with the lowest bridge ID. It can
be done manually, or the bridges in the network elect a root bridge themselves
automatically. If the root bridge fails, the other bridges select a new root device.
The other bridges in the network are referred to as designated bridges.
Link Cost
Every link in the network receives a certain cost. Usually, higher-bandwidth links
that are adjacent to the root bridge are assigned a lower cost. Lower-bandwidth
links that are multiple hops away from the root bridge are assigned a higher cost.
Once link costs are estimated, STP determines the lowest cost connections from

each designated bridge to the root bridge to determine the lowest-cost path. It
also blocks all the other higher cost links to prevent loops in the network.
Bridge Protocol Data Units

The bridges use Bridge Protocol Data Units (BPDUs) to exchange information
about network topology, bridge IDs, link costs etc. BPDUs help establish the best
route (least cost path) to the root bridge.
When there is a change in the network, relevant BPDUs are sent to all the
bridges/bridge ports by the root bridge. The designated bridges adjust their
tables to determine the new routes to the terminals.
Rapid Spanning Tree Protocol

Rapid Spanning Tree Protocol (RSTP) provides significantly faster spanning tree
convergence after a topology change, supporting a loop-free Layer-2 forwarding
over a mesh/ring physical topology. In RSTP, link status of each port are
monitored pro-actively (instead of waiting for the BPDU messages) to detect
changes in network topology.
Configuring the Bridge
Configuring for Traffic

To configure the bridge for traffic, perform the following steps:
1. Configure a bridge instance (1–11).
2. Configure the bridge ports.
3. Configure VLANs (CL bridge ports only). For E-Tree service in a VLAN,
configure VLAN mode to E-Tree and configure root.
4. Configure flows between non-bridge ports and bridge ports (bridge ports are
defined as egress tagged VLAN members).
Configuring for Management

In order to manage the device via the bridge, you need to configure the
following:
1. Configure the router (1) interface for management, bound to SVI.
2. Configure the flow between the SVI and bridge port (only one SVI<->bridge
port flow can be created per bridge port).
3. Configure the flow between a non-bridge port and bridge port.
Configuring the Bridge

 To configure a bridge:
1. At the configure prompt, enter bridge followed by bridge number (1–11).
A bridge instance with the specified number is created and the
config>bridge(1)# prompt is displayed.
2. Configure the bridge as illustrated and explained below.

Note Using no before bridge (bridge_number) deletes a bridge instance.
3. Configure the new bridge port and bind it to the bridge as illustrated and
explained in the table below.
Defining aging time for MAC aging-time <60–3000> Default: 300

table entries (seconds)
Clearing addresses in MAC table clear-mac-table
Configuring bridge ports (see port <port-number> The range is:

below) 1–80 for CL bridge
1-9 for M-ETH bridges
To delete a bridge port, enter
no port <port-number>
Enabling Layer 2 bridging vlan-aware no vlan- aware disables Layer 2

according to the VLAN tag bridging according to the VLAN tag
Enabling or disabling filtering filtering In Megaplex-4, filtering is always

enabled
Defining VLANs (see below) vlan <vlan-id> Range is 1–4094

To delete a VLAN, enter
no vlan <vlan-id>
In order to make sure that all devices
are reached in case of traffic load, it
is recommended that the VLAN
intended for management (in Bridge
1) is mapped to queue 0 (highest
priority). This mapping is done while
configuring the egress-port of a flow
as bridge-port of Bridge 1 (see
Configuring Flows).
Configuring spanning tree (see spanning-tree Only CL.2/A modules support this
below) feature
If the bridge port is set as a member
in RSTP, it cannot be a member of
LAG, Ethernet group or ERP at the
same time.
Displaying MAC address table for show mac-address-table all Up to the first 100 entries are
all ports/VLANs or selected [vlan <vlan-id range v1..v2> | displayed on the screen.
VLANs/VLAN range/port/port port <port-number range
ranges p1..p2> ]

The following commands are available in the spanning-tree level, at the

config>bridge(1)> spanning-tree# prompt.
Defining the time duration in forward-time <4-30> You cannot assign forward-time a
listening and learning states that value less than max-age/2+1.
precede the forwarding state, in
seconds
Defining the time interval in hello-time <1-10>

seconds between BPDU
transmissions (seconds)
Defining the maximum age of max-age <6-40> You cannot assign max-age a
the configuration BPDU can be value that is less than 2*(hello-
maintained on a device time+1) or more than 2*(forward-
(seconds). time–1).
Defining the operation mode for mode {mstp | rstp} mstp is not supported.
spanning-tree
Assigning the bridge priority priority <0, 4096, 8192, 12288,

value 16384, 20480, 24576, 28672,
32768, 36864, 40960, 45056,
49152, 53248, 57344, 61440>
Configuring the maximum tx-hold-count <number> The value is 1-10.

number of BPDUs transmitted
Displaying the spanning-tree show status

status
The following commands are available in the port level, at the

config>bridge(1)>port(<port-number>)# prompt.
Assigning a name to the bridge name <port-name> To delete the bridge port name, enter
port no name
Administratively enabling the no shutdown To administratively disable the bridge

bridge port port, enter shutdown
Binding the bridge port to an bind ethernet <slot/port> M-ETH external bridge ports only
M-ETH Ethernet port To remove the binding, enter no bind
Assigning a default VLAN ID to pvid <vlan-id> Not relevant for Bridge 1 ports
an access port (for untagged or
priority-tagged frames) to
designate the virtual LAN
segment to which this port is
connected
Configuring spanning tree for spanning-tree

port (see below)

The following commands are available in the vlan level, at the

config>bridge(1)>vlan(<vlan-id>)# prompt.
Defining maximum MAC table maximum-mac-addresses Range: 0..16384

size supported by the VLAN <max-mac> 0 – all MAC addresses, without
restriction
Configuring VLAN to work in mode {e-tree | e-lan} CL bridge ports only

E-Tree or E-LAN mode If you change to E-Tree, you need
to define a bridge port as root.
Assigning a name to the VLAN name <vlan-name> To delete the VLAN name, enter
no name
Defining bridge ports as egress tagged-egress Bridge ports in a list can be

tagged VLAN members (part of <bridge_port_number> separated by a comma or given as
“VLAN table”) a range, for example: 1..3, 5.
Using no before the command
deletes VLAN membership for the
bridge port.
Configuring bridge port as root root <bridge-port> This command is available only if
port in E-Tree mode the VLAN mode is E-Tree
When all E-Tree bridge ports are
defined as root, the bridge
actually functions as E-LAN.
The following commands are available in spanning tree level of port, at the
config>bridge(1)>port(<port-number>) >spanning-tree# prompt.
Enabling the port as an edge admin-edge To cancel the edge port, enter no
port admin-edge.
Enabling the port as the edge auto-edge Using no before the command
port automatically cancels the setting.
Setting the path cost for the cost <number> If a loop occurs, the path cost is used
port to select an interface to place into
the forwarding state.
A lower path cost represents higher
speed links.
Forcing the port to transmit RST mcheck

BPDUs
Assigning the priority value on priority <0, 16, 32, 48, 64, 80,
the port 96, 112, 128, 144, 160, 176,
192, 208, 224, 240>
Administratively enabling the no shutdown shutdown disables the spanning-tree

spanning-tree on the port on the port.

Displaying the spanning-tree show status

status on the port
Example 1. Layer-2 Management Access

Figure 8-3 shows Layer-2 management connectivity via the CL bridge. The
connection consists of the following sections:
• RI #1 bound to SVI #1
• Flow 1 connecting SVI #1 to BP (bridge port) 1 (this flow must be defined in
two directions and consists of two sub-flows: bp-svi and svi-bp)
• BP 1 and BP 7 interbridge connectivity (based on VLAN membership that must
be configured with same VLAN values as VLAN configured in the flows)
• Flow 10 between BP 7 and the management Ethernet port of CL-A module.
(this flow must be defined in two directions and consists of two sub-flows:
eth-mng-bp and bp-eth-mng)
mng-eth mng-eth
L. MAC
cl-a cl-b
GbE cl-a 1
10
BP 1 7 BP 1 6 BP 1 5
Bind
RI#2
DTS
BP 1 8
PPP
Flow Router
GbE cl-b 1
DCC
RI#3
RI#1 PPP
MNG flow pop/push, bi-

BP 1 9
BP 1 1
directional flow in all Bridge#1 Aware
W
CL.2 assemblies 1 SVI#1

ERP#2
GbE cl-a 2
BP 1 4
BP 1 2 BP 1 5 BP 1 3
This connection is configured as follows.

### Define the SVI####
configure port svi 1
no shutdown
exit all
### Define the CL Bridge####

configure bridge 1
vlan-aware
port 1
no shutdown
exit all
configure bridge 1
port 7
no shutdown
exit all
vlan 100
tagged-egress 1
tagged-egress 7

exit all
### Define the physical management port 1 of CL-A module####

configure port
mng-ethernet cl-a/1
no shutdown
exit
### Define the Router Interface####

configure
router 1 interface 1 address 172.18.171.121/24
router 1 interface 1 bind svi 1
router 1 static-route 0.0.0.0/0 address 172.18.171.1
exit all
### Define the Flows. The Bridge is working on VLAN 100. The
MNG ‘host’ is untagged####
# Flow # 1: SVI <-> BP 1 1
configure flows
flow svi-bp
ingress-port svi 1
egress-port bridge-port 1 1
classifier mng-untagged
vlan-tag push vlan 100 p-bit fixed 7
no shutdown
exit
flow bp-svi
ingress-port bridge-port 1 1
egress-port svi 1
classifier mng-100
vlan-tag pop vlan
no shutdown
exit
# Flow # 10: MNG ETH <-> BP
flow eth-mng-bp
ingress-port mng-ethernet cl-a/1
classifier mng-untagged
no shutdown
exit
flow bp-eth-mng
ingress-port bridge-port 1 7
egress-port mng-ethernet cl-a/1
classifier mng-100
vlan-tag pop vlan
no shutdown
exit

Example 2. Layer-2 VLAN-aware Bridging between CL and

M-ETH Ports
Figure 8-4 shows three ports sharing the same VLAN (200): GbE port CL-B/2 and
M-ETH ports 1/3 and 2/8. Since these ports are located on different modules, the
bridging between them must be done via the CL bridge.
The connection consists of the following sections:
• Flow 20 between GbE port 2 of CL-A to BP 1 4
• BP 1 4 and BP 1 5 intrabridge connectivity (via VLAN 200 table)
• Flow 21 between BP 1 5 and the GbE port 3 of M-ETH #1 module
• Flow 22 between BP 1 3 and the GbE port 8 of M-ETH #2 module.
All the flows are bidirectional, i.e. you only need to define one flow from a port
to a bridge port, and specify the reverse-direction command.
mng-eth mng-eth
L. MAC
cl-a cl-b
GbE cl-a 1
BP 1 7 BP 1 6 BP 1 5
Bind
RI#2
DTS
BP 1 8
PPP
W
Flow Router
ERP#2
GbE cl-b 1
DCC
RI#3
RI#1 PPP
E

BP 1 9
BP 1 1
SVI#1
CL.2 assemblies
GbE cl-a 2
BP 1 4
20
BP 1 2 BP 1 5 BP 1 3
Eth 1 1
Bridge #4
BP 4 1
BP 4 3
ERP#3
BP 4 2
Eth 1 2
E
Eth 1 3
21
M-ETH in slot #1
Bridge #7
eth 2 1
BP 7 5
BP 7 1
Eth 2 2
BP 7 8
Eth 2 8
22
M-ETH in slot #2
Figure 8-4. Layer-2 VLAN-aware Bridging between CL and M-ETH Ports
####QoS Configuration######
exit all
configure qos

shaper-profile b-s
bandwidth cir 50000
exit
policer-profile 10m
bandwidth cir 10000 eir 0
exit
queue-group-profile b-s
queue-block 0/1
profile DefaultQueue1
shaper profile b-s
exit all
#### Configuration Physical Ports ######
configure port
ethernet cl-a/2
no shutdown
exit all
configure port
ethernet 1/3
no shutdown
exit all
configure port
ethernet 2/8
no shutdown
exit all
#### Configuring CL Bridge 1 (Ports 1 3, 1 4 and 1 5)######

config bridge 1
vlan-aware
port 3
no shutdown
exit
port 4
no shutdown
exit
port 5
no shutdown
exit
vlan 200
tagged-egress 3
tagged-egress 4
tagged-egress 5
exit all
######Configuring the Flow Connection – Consists of 3 flows:

#flow 20 between Ethernet port CL-A/2 and BP 1 4
#flow 21 between Ethernet port 1/3 (M-ETH in slot 1) and BP 1 5
#flow 22 between Ethernet port 2/8 (M-ETH in slot 2) and BP 1 3
######
exit all
config flows
classifier vlan200 match-any
match vlan 200
exit

flow 20
class vlan200
ingress Ethernet cl-a/2
egress bridge-port 1 4
reverse-direction queue 0 block 0/1
policer-profile 10m
no shutdown
exit
flow 21
class vlan200
ingress Ethernet 1/3
policer profile 10m
no shutdown
exit
flow 22
class vlan200
ingress Ethernet 2/8
policer-profile 10m
no shutdown
exit
Example 3. Cascading Bridges on Different M-ETH Modules via

CL Bridge
Figure 8-5 shows cascading bridges on different M-ETH modules via the CL
bridge. This configuration can be used for extending the number of available
bridge ports.

mng-eth mng-eth
L. MAC
cl-a cl-b
GbE cl-a 1
BP 1 7 BP 1 6 BP 1 5
Bind
RI#2
DTS
BP 1 8
PPP
W
Flow Router
ERP#2
GbE cl-b 1
DCC
RI#3
RI#1 PPP
E
BP 1 9
BP 1 1
SVI#1
CL.2 assemblies
GbE cl-a 2
BP 1 4
BP 1 2 BP 1 5 BP 1 3
Eth 1 1
Bridge #4
BP 4 1
BP 4 3
30
BP 4 2
Eth 1 2
Eth 1 3
M-ETH in slot #1
Bridge #7
eth 2 1
BP 7 5
BP 7 1
Eth 2 2
31
BP 7 8
Eth 2 8
M-ETH in slot #2
Figure 8-5. Cascading Bridges on Different M-ETH Modules via CL Bridge
The connection consists of the following sections:

• BP 4 1 bound to Eth 1/1, BP 4 2 bound to Eth 1/2
• BP 4 1, BP 4 2 and BP 4 3 interbridge connectivity (via VLAN 200 table)
• Flow 30 between BP 1 2 (CL bridge) and BP 4 3 (M-ETH module in Slot 1)
• BP 1 2 and BP 1 3 interbridge connectivity (via VLAN 200 table)
• Flow 31 between BP 1 3 (CL bridge) and BP 7 1 (M-ETH module in Slot 2)
• BP 7 1, BP 7 5 and BP 7 8 interbridge connectivity (via VLAN 200 table)
• BP 7 5 bound to Eth 2/1, BP 7 8 bound to Eth 2/2
All the flows are bidirectional, i.e. you only need to define one flow from a port
to a bridge port, and specify the reverse-direction command.
####QoS Configuration######
exit all
configure qos
shaper-profile b-s
bandwidth cir 50000
exit
policer-profile 10m
bandwidth cir 10000 eir 0

exit
queue-block 0/1
profile DefaultQueue1
shaper profile b-s
exit all
####Physical Port Configuration (2 Ethernet ports per each

M-ETH module)######
configure port
ethernet 2/2
no shutdown
queue-group profile b-s
exit all
configure port
ethernet 2/1
no shutdown
exit all
configure port
ethernet 1/2
no shutdown
exit all
configure port
ethernet 1/1
no shutdown
exit all
####Bridge 1 Configuration######
config bridge 1
vlan-aware
port 1 2
no shutdown
exit
port 1 3
no shutdown
exit
#Configuring Bridge 1 VLAN table#

vlan 200
tagged-egress 2
tagged-egress 3
exit all
config bridge 7
vlan-aware

port 1
no shutdown
exit
port 8
no shutdown
bind Ethernet 2/2
exit
port 5
no shutdown
bind Ethernet 2/1
exit

vlan 200
tagged-egress 1
tagged-egress 8
tagged-egress 5
exit all
config bridge 4
vlan-aware
port 1
no shutdown
exit
bind Ethernet 1/1
port 2
no shutdown
exit
bind Ethernet 1/2
port 3
no shutdown
exit

vlan 200
tagged-egress 1
tagged-egress 2
tagged-egress 3
exit all
######Flow Configuration######
exit all
config flows
classifier vlan200 match-any
match vlan 200
exit

flow 30
class vlan200
ingress bridge-port 1 2
policer-profile 10m
no shutdown
exit
flow 31
class vlan200
ingress bridge-port 1 3
policer-profile 10m
no shutdown
exit
Example 4. RSTP Basic Application

The following example illustrates the use of the RSTP:
Megaplex-4_A
M-ETH
CL.2 A ETH 2/1
ETH cl-a/2
NMS ETX-1_C
ETH1
CL.2 A
ETH5
ETH cl-a/1
ETH2
CL.2 A
ETH cl-a/1
VS-6/E&M
ETH 2/1
CL.2 A
ETH cl-a/2
Megaplex-4_B
Note To use RSTP, the MAC address of BPDU packet must be set as 01-80-C2-00-00-
00 peer.
The connection consists of the following sections.

Device Megaplex-4_A:
• Assign previously configured queue group profile to the I/O card port, l2cp
profile to CL.2 card port and enable the ports.
• Enable bridge ports
• Define the bridge port VLAN membership and root port
• Define the flows
• Configure spanning-tree on bridge port level
• Configure spanning-tree on bridge level

#******************** QoS Configuring

config qos queue-group-profile rstp
exit all
#************** Configure L2CP profile

configure port
l2cp-profile RSTP mac 01-80-C2-00-00-00 peer
#*********** Configure Ethernet port and associate L2CP

profile, queue-group profile
ethernet cl-a/1
no shutdown
l2cp profile RSTP
exit
ethernet cl-a/2
no shutdown
l2cp profile RSTP
exit
ethernet 2/1
no shutdown
queue-group profile rstp
exit
exit all
#*********** Bridge configuration

configure bridge 1
port 1 no shutdown
port 2 no shutdown
port 3 no shutdown
#*********** Configure Bridge VLAN table and configure VLAN to

work in E-Tree mode
vlan 100
tagged-egress 1..3
maximum-mac-addresses 0
mode e-tree
root 1
root 3
exit
exit all

#************** Flow configuration

configure flows
classifier-profile "v100" match-all match vlan 100
flow cl-a/1_b1
classifier "v100"
ingress-port ethernet cl-a/1
no shutdown
exit
flow cl-a/2_b2
classifier "v100"
no shutdown
exit
flow 2/1_b3
classifier "v100"
ingress-port ethernet 2/1
no shutdown
exit
exit all
#******************** Configuring_spanning tree on port

configure bridge 1 port 1 spanning-tree no shutdown
#******************** Configuring_spanning tree for bridge

configure bridge 1 spanning-tree priority 4096
Device Megaplex-4_B:
• Assign previously configured queue group profile to the I/O card port, l2cp
profile to CL.2 card port and enable the ports.
• Define the bridge port VLAN membership and root port
• Define the flows
• Configure spanning-tree on bridge port level
#******************** QoS Configuring
config qos queue-group-profile rstp
exit all
#************** Configure L2CP profile

configure port
l2cp-profile RSTP mac 01-80-C2-00-00-00 peer
#*********** Configure Ethernet port and associate L2CP

profile, queue-group profile
ethernet cl-a/1
no shutdown
l2cp profile RSTP
exit
ethernet cl-a/2
no shutdown
l2cp profile RSTP
exit
ethernet 2/1
no shutdown
queue-group profile rstp
exit
exit all

configure bridge 1
port 1 no shutdown
port 2 no shutdown
port 3 no shutdown
#*********** Configure Bridge VLAN table and configure VLAN to

work in E-Tree mode
vlan 100
tagged-egress 1..3
maximum-mac-addresses 0
mode e-tree
root 1
root 3
exit
exit all

#************** Flow configuration

configure flows
classifier-profile "v100" match-all match vlan 100
flow cl-a/1_b1
classifier "v100"
no shutdown
exit
flow cl-a/2_b2
classifier "v100"
no shutdown
exit
flow 2/1_b3
classifier "v100"
no shutdown
exit
exit all
#******************** Configuring_spanning tree on port


configure bridge 1 spanning-tree priority 20480
Device ETX-1_C:
• Define the bridge port VLAN membership


configure bridge 1
port 1 spanning-tree no shutdown
#*********** Configure Bridge VLAN table

vlan 100
tagged-egress 1..5
exit

spanning-tree
priority 8192
exit
exit all
Displaying MAC Address Table

You can display a Megaplex-4 MAC table, which provides information on dynamic
MAC addresses, bridge ports and VLANs associated with them. The regular show
mac-address-table command displays only 100 entries. To display the complete
MAC address table (up to 16384 addresses), you can use file>copy mac-table
command described below.
 To display MAC address table for all ports and VLANs (up to 100 entries):
• At the config>bridge(bridge_number)# prompt, enter show mac-address-table
all.
The MAC address table is displayed.
mp4100# configure bridge 1
mp4100>config>bridge(1)# show mac-address-table all
Total MAC Addresses : 20
Vlan MAC Address Port Status

---------------------------------------------------------------
3 00-00-00-00-00-CA 80 Dynamic
3 00-00-00-00-01-01 1 Dynamic
3 00-00-00-00-02-01 3 Dynamic
3 00-00-00-00-03-01 5 Dynamic
3 00-00-00-00-10-01 6 Dynamic
4 00-00-00-00-00-CA 80 Dynamic
4 00-00-00-00-01-01 1 Dynamic
4 00-00-00-00-02-01 3 Dynamic
4 00-00-00-00-03-01 5 Dynamic
4 00-00-00-00-10-01 6 Dynamic
5 00-00-00-00-00-CA 80 Dynamic
5 00-00-00-00-01-01 1 Dynamic
5 00-00-00-00-02-01 3 Dynamic
5 00-00-00-00-03-01 5 Dynamic
5 00-00-00-00-10-01 6 Dynamic
6 00-00-00-00-00-CA 80 Dynamic
6 00-00-00-00-01-01 1 Dynamic

6 00-00-00-00-02-01 3 Dynamic
6 00-00-00-00-03-01 5 Dynamic
6 00-00-00-00-10-01 6 Dynamic
 To display MAC address table for a specific VLAN/VLAN range/port/port range:

• At the config>bridge(bridge_number)# prompt, enter show mac-address-table
all [vlan <vlan-id range v1..v2> | port <port-number range p1..p2> ]
The MAC address table for the selected VLAN/VLAN range/port/port range
is displayed. For example, the table below is for vlan 10, ports 11-15:
mp4100>config>bridge(1)# show mac-address-table all vlan 10
ports 11..15
Total MAC Addresses : 5
Vlan MAC Address Port Status

---------------------------------------------------------------
10 00-00-00-00-02-03 11 Dynamic
10 00-00-00-00-03-02 13 Dynamic
10 00-00-00-00-10-03 15 Dynamic
 To display all the MAC address table entries (up to 16384 addresses):
1. Open a TFTP Server for file transfer to a folder selected on a PC.
2. At the file# prompt, enter copy mac-table tftp://<PC IP address>/<filename>
mp4100>file# copy mac-table tftp://172.17.151.59/MAC_TAB.txt
Are you sure? [yes/no] _ y
mp4100>file#
*****
File copy command was completed.*****
*****mac-table copied to tftp://172.17.151.59/MAC_TAB.txt successfully*****
*****1210 bytes copied in 1 secs (1210 bytes/sec)*****

3. Open the created text file with an appropriate text viewer (that allows
viewing table format).
Now all the MAC addresses can be displayed in one file.
Bridge VLAN MAC Address Port Status
------ ----- ----------------- ----- -------
1 500 00-00-00-00-00-bf 20 Learned
1 500 00-00-00-00-aa-07 80 Learned
1 500 00-00-00-00-00-bb 20 Learned
1 500 00-00-00-00-00-c3 20 Learned
1 500 00-00-00-00-aa-03 80 Learned
1 500 00-00-00-00-00-bd 20 Learned
1 500 00-00-00-00-aa-05 80 Learned
1 500 00-00-00-00-aa-09 80 Learned
1 500 00-00-00-00-00-c1 20 Learned
1 500 00-00-00-00-aa-01 80 Learned
1 500 00-00-00-00-aa-06 80 Learned
1 500 00-00-00-00-00-c2 20 Learned

1 500 00-00-00-00-aa-02 80 Learned

1 500 00-00-00-00-00-bc 20 Learned
1 500 00-00-00-00-00-c4 20 Learned
1 500 00-00-00-00-aa-04 80 Learned
1 500 00-00-00-00-aa-08 80 Learned
1 500 00-00-00-00-00-c0 20 Learned
1 500 00-00-00-00-aa-00 80 Learned
detected.
540 Error BRIDGE PORT IS SHUTDOWN Bridge port must be bound to SVI
541 Error MORE THAN ONE SVI BOUND Bridge port should be bound to a single SVI
TO BRIDGE PORT
542 Error SVI PORT IS NOT CONNECTED SVI is enabled (“no shutdown”) but not bound
543 Error SAME SVI BOUND TO SVI must be bound to bridge port 1:1
DIFFERENT BRIDGE PORTS
544 Error BRIDGE PORT NOT BOUND TO A bridge port is defined but not bound to any other port.
PORT
548 Error ILLEGAL BRIDGE PORT BINDING You cannot bind more than one physical port to a bridge
port.
600 Error 2 SVI FROM SAME CARD CAN’T Two SVI ports connected to two PWs defined on the same
USE SAME VLAN module cannot use the same VLAN.
700 Error NUM OF BRIDGE PORTS The maximum number of bridge ports is as follows:
EXCEEDED MAX • 80 for bridge number 1 (CL modules)
• 9 bridge pors for each M-ETH bridge
701 Error VLAN MEMBER AND FL CONF The VLAN table does not match the bridge/flow
MISMATCH configuration
702 Error PORT ALREADY IN USE Two flows with the same VLAN classification use the same
port.
703 Error REVERSE DIRECTION IS This flow must be configured in the reverse direction.
MISSING
705 Error DEFAULT QUEUE IS NOT This flow must have a valid non-default queue group
PERMITTTED profile.
706 Error NUM OF FLOWS OVER M-ETH M-ETH bridge cannot be connected to more than one
BRIDGE EXCEEDS ONE flow.
707 Error INVALID VLAN IDENTIFIER Flows connected to a bridge must have a VLAN
classification

708 Error WRONG FLOW ON PROTECTED A port protected by Ethernet group protection cannot
PORT serve as a flow ingress/egress port
709 Error BRIDGE PORT MUST BE EGRESS When configuring a flow between a physical port and a
bridge port, the ingress and egress ports must be set as
follows:
• physical port= ingress port
• bridge port = egress port.
8.2 Cross-Connections
The matrix in the figure below describes all possible cross-connections you can
perform in the Megaplex-4.
Figure 8-6. Cross-Connections in Megaplex-4
8-26 Cross-Connections Megaplex-4

The matrix cells are color-coded to indicate which option (command) to choose
for the various modules/ports/timeslots/entities at both ends, as follows:
Color Command Meaning
ds0, tdm, split-ts cross-connect on the DS0 or DS1 level and/or split timeslot cross-connect
ds0 cross-connect on the DS0 level (no split timeslot cross-connect)
ds0, tdm cross-connect on the DS0 level and/or split timeslot cross-connect
– LRS-102 Optimux modules only, fixed local cross-connect
bind cross-connect for Ethernet-over-TDM traffic
sdh-sonet SDH/SONET cross-connect
pw-tdm Pseudowire cross-connect
A number inside the cell refers to a special note regarding this type of
cross-connect.
Examples of using the table:
• To cross-connect an e1-i port of an M8SL module to an e1-i port on the CL.2
module you have to use ds0 cross-connect.
• To cross-connect a t1-i port to vt1.5 virtual tributary or e1-i to sdh, you have
to use sdh-sonet cross-connect
• To cross-connect the entire e1 port traffic of an M16E1 module transparently
to vc-12, you have to use sdh-sonet mapping
• To cross-connect the entire e1 port traffic of an M16E1 module transparently
to vc-12, you have to use sdh-sonet mapping
• To map the entire e1 port to an e1-i port, you can use either ds1 or ds0
cross-connect
• To cross-connect an hdlc port to e1, you have to use the bind command
• To cross-connect unframed stream, you have to use the ds1 command.
Split timeslot cross-connect is possible for the same ports where ds0
cross-connect is used, when working with the following modules: HSU-6/HSU-12,
HS-S, HS-RN, VC-4A, VC-8A, LS-6N/LS-12, VS serial ports operating in V.110
mode. HS-6N/12N, HS-703, HSF-2, VC-4/OMNI, voice ports of VS modules and
cmd channels of TP and VS-6/BIN modules do not support split timeslot
cross-connect.
Factory Defaults
No cross-connections exist in Megaplex-4 by default.
Megaplex-4 Cross-Connections 8-27

Benefits
Cross-connections allow flexible mapping of individual DS0 channels, full DS1
streams, pseudowire or VC/VT entities.
Timeslot Types
When configuring the cross-connect, it is necessary to instruct each port how to
handle the traffic flow and signaling information. This is performed by defining
the timeslot type.
The selections are as follows:
• data: the timeslot is handled as a data channel. This means that any signaling
information associated with the channel is ignored.
• voice: the timeslot is handled as a voice channel. This means two things:
 It is necessary to select a link framing mode that supports channel
associated signaling, e.g., G.704 multiframe (G.732S) for E1, SF (D4) or
ESF for T1.
 The signaling information of the channel is routed (automatically) in
parallel with the channel payload.
Full Timeslot versus Split Timeslot Assignment (Split Timeslot

Cross-Connect)
For user ports that do not require a full timeslot (eight bits, equivalent to a
bandwidth of 64 kbps), Megaplex-4 also permits split timeslot assignment, that
is, assignment of individual bits in a selected timeslot. This functionality is used
for ports operating at channel rates lower than 38.4 kbps.
Split timeslot assignment increases the bandwidth utilization efficiency for TDM
modules or channels, because it enables the allocation of link bandwidth in
smaller (sub-DS0) units: the split timeslot assignment unit is 16 kbps (a pair of
consecutive bits in a timeslot).
Split timeslot assignment is supported by voice modules (ADPCM encoding), low-
speed data modules, and ISDN modules.
The split timeslot assignment is performed in coordination with the modules
having sub-DS0 ports. It is not possible to mix bits from different modules in the
same DS0 timeslot.
The location of data bits in a timeslot depends on the port data rate and is
shown in the diagram below:
• For 2.4, 4.8 or 9.6 kbps data rates, the data can occupy bits 1-2, 3-4, 5-6 or
7-8.
• For 19.2 kbps data rate, the data can occupy bits 1-4 or 5-8.
MSB and LSB denote most signinficant bit and least signinficant bit, respectively.

Table 8-4. Data Allocation in a Timeslot
Rate Data Location in Timeslot
2.4, 4.8, 9.6 MSB LSB
1 2 3 4 5 6 7 8
19.2 MSB LSB
1 2 3 4 5 6 7 8
Bidirectional Transfer Mode

The bidirectional transfer mode is used to transfer data/voice simultaneously in
both receive and transmit directions.
Unidirectional Broadcast Function

The unidirectional broadcast mode enables a user at a central location to send
data or voice to multiple users connected to remote ports via the
Megaplex-4 links (simplex communication). In this mode, any message is
simultaneously received by all the remote unidirectional users, but none of them
can send back data to the originator.
This capability is achieved by separating the handling of the receive and transmit
paths for timeslots assigned to unidirectional channels.
You can specify the operating mode of each unidirectional channel or E1/T1
timeslot either as unidirectional transmit, or unidirectional receive:
• Unidirectional transmit: the channel/timeslot transmits, but cannot receive
(its receive path is disconnected). The information transmitted by the channel
can be routed to any number of E1/T1/E1-i/T1-i ports for distribution to
multiple remote Megaplex-4 units.
• Unidirectional receive: the channel/timeslot receives, but cannot transmit (its
transmit path is disconnected). The user can select the source port
(E1/T1/E1-i/T1-i or compatible I/O port) from which the channel receives, and
the specific timeslot. The same source port or a range of timeslots can be
connected to several channels operating in the unidirectional receive mode.
The unidirectional broadcast function is available only for ds0 cross-connect.
The unidirectional broadcast capabilities depend on the module type:
• Modules with internal or external E1 and T1 ports (see Table 8-5): the
payload received by a unidirectional broadcast timeslot is distributed in
parallel to multiple destination timeslots of other E1 or T1 links, or to
modules with unidirectional receive capabilities.

• Voice and data I/O modules (see Table 8-6): not all the modules support
unidirectional capabilities, but only modules which require a single timeslot
per channel, and that do not require handshaking for setting up a link.
Therefore, unidirectional broadcast is supported by VC-4/4A/8/8A/16 voice
modules with E&M and FXS interfaces, HS-6N/12N, HS-RN, or VS data
modules, as well as LS-6N/LS-12 (internal ports). In addition, VS-6/E&M and
FXS/E&M modules support unidirectional receive capabilities. ISDN interface
modules cannot support this capability.
Table 8-5. Unidirectional Broadcast for E1/T1 Ports
I/O Modules Ports unidirection-tx unidirection-rx
CL.2 Internal E1/T1 √ √
M8E1/M8T1 External E1/T1 √ √

M16E1/M16T1
ASMi-54C/N Internal E1 √ √
M8SL
SH-16
ASMi-54C/N External E1/T1 √ √
OP-34C, OP-108C Internal E1 √ √
T3 Internal T1 √ √
Table 8-6. Unidirectional Broadcast in Voice and Data I/O Modules
I/O Modules Ports unidirection-tx unidirection-rx
VC-4/4A/8/8A/16 FXS & E&M √ √
VC-4/4A/8/8A/16 FXO - -
HS-U-6, HS-U-12, HS-S serial - -
HS-RN serial √ √
LS-6N/LS-12 serial - -
LS-6N/LS-12 serial-bundle √ √
HS-6N/HS-12N serial √ √
VS-12, VS-6/BIN serial √ √
VS-6/E&M, FXS/E&M E&M - √
Bidirectional Broadcast Applications

The bidirectional broadcast mode enables a user at a central location to
communicate with several users connected to remote Megaplex-4 units, using polled
communications.
This mode is supported by the following modules:
• VC-4/OMNI modules configured to omni-bus or p2mp-src operation modes
(see Configuring Voice ports in Chapter 6).

• VS modules, whose serial ports are operating in 3-bit-transitional mode at

the rate of 64 kbps (see Encapsulation Modes in in VS Modules chapter of
Megaplex-4 I/O Modules).
• VS-6/E&M and FXS/E&M VS voice modules.
Broadcast is achieved as follows:
• At the central (source) location, a specific timeslot is assigned to each
remote site (Rx). The same data received from the source channel is
broadcast (Tx) in parallel to all the timeslots.
• At each remote (destination) site, the corresponding timeslot is connected to
the corresponding VC/VS module channel (with regular bi-directional
connection)
When the equipment connected to a remote channel identifies a polling
addressed to itself, the remote device answer is forwarded to the source
location (such as Regional Center node in Figure 8-7). The Megaplex device
located in the National Center takes in the channel with active data back to
the SCADA master port, located at the Regional Center.
VC-4/OMNI Modules
The logic to select the active channel can be based on voice signaling
(bidirection-rx) or voice-grade data activity (bi-direction). The choice depends on
the connected equipment: if central/remote device supports signaling, use
bidirection-rx mode, otherwise use bi-direction mode. Bidirectional broadcast
requires signaling (legacy or abcd) configured for internal voice ports.
The bidirectional broadcast capacity of the VC-4/OMNI module is 30 timeslots. Only
one internal voice port per external port of VC-4/OMNI module can be connected
using “bidirection-rx” DS0 cross connect option. Other ports are usually configured
as bi-direction DS0 cross-connect. A typical application is shown in Figure 8-7.
Regional Centers
VC-4/OMNI
E1
Megaplex-4
E1 1/1 TS 1 Voice
E1
SCADA
Megaplex voice port: RTU
National Center bi-direction
Voice port 3/2/2: Voice port 3/2/1: Up to 30
bi-direction bidirection-rx Nodes
VS-4/OMNI
VC-4/OMNI
E1 6/1 TS 1
E1 5/1 TS 1 Voice
Network E1
E1
SCADA Megaplex-4
Megaplex-4 Megaplex RTU
voice port:
bi-direction
SCADA
E1-i CL-A/1 TS 1 Voice

E1
SDH
VC-4/OMNI VC-4/OMNI
bi-direction
Megaplex-4
SCADA
Figure 8-7. Bidirectional Voice Grade Data Broadcast 1:n

VS Modules
The logic to select the active channel can be based on end-to-end control with
RTS signaling (end-to-end-control is selected) or data activity (no end-to-end-
control). The choice depends on the connected equipment: if central/remote
device supports RTS signaling, use ene-to-end control signaling.
A basic bidirectional broadcast application is shown in Figure 8-8.
VS-12
E1 1/1 TS 1 64 kbps
E1
Megaplex VS serial port: RTU

bi-direction
Up to 30
Control Center nodes
VS-12
VS-12
64 kbps E1 5/1 TS 1 64 kbps
E1
SCADA Megaplex-4 Megaplex
VS serial port: RTU
VS serial port 3/1:
bi-direction
bidirection-rx
VS-12
E1-i CL-A/1 TS 1
64 kbps
SDH
Megaplex VS serial port:
RTU
bi-direction
Figure 8-8. Bidirectional Broadcast: Serial Port is Sending Data to Different E1

Ports of Remote RTUs
Additional applications are possible using a virtual entity defined on VS modules,

which is called TDM bridge.
In Figure 8-9 a VS-12 module installed in a Regional Center uses the TDM bridge
to send and receive data to/from 3 remote RTUs, while a VS-12 module installed
in a National center performs data monitoring of the RTU replies/statuses.

VS-12
E1 1/1 TS 1 64 kbps
E1
National Center (Monitoring) Regional Center Megaplex VS Serial Port: RTU
bi-direction
TDM Up to 30
tdm-bridge3/1 Bridge Nodes
VS-12 E1 6/1 TS 1 unidirection-rx
VS-12
64 kbps Serial Port
SCADA Megaplex-4 VS-12 Bind E1 5/1 TS 1
VS Serial Port: 64 kbps
Unidirection-rx 64 kbps
E1
tdm-bridge3/1
Megaplex-4 bidirection-rx
Megaplex VS Serial Port: RTU
bi-direction
VS Serial Port 3/2
SCADA
VS-12
E1-i CL-A/1 TS 1 64 kbps

SDH
Megaplex VS Serial Port: RTU

bi-direction
Figure 8-9. Bidirectional Broadcast to/from Remote RTUs with Monitoring over E1
FXS/E&M and VS-6/E&M Modules

The logic to select the active channel can be based on voice signaling
(bidirection-rx) or voice-grade data activity (bi-direction). The choice depends on
the connected equipment: if the central/remote device supports signaling, use
bidirection-rx mode, otherwise use bi-direction mode.
The bidirectional broadcast capacity of the E&M module is 30 timeslots. Only one
internal voice port per external port of E&M module can be connected using
“bidirection-rx” DS0 cross connect option. Other ports are usually configured as
bi-direction DS0 cross-connect. A typical application is shown in Figure 8-10. The
application of VS-6/E&M modules is similar with FXS/E&M modules.
E1 1/1 TS 1 Voice
E1
Regional Centers Megaplex voice port: RTU

National Center bi-direction
Voice port 9/4: Voice port 9/9: Up to 30
bi-direction bidirection-rx Nodes
FXS/E&M
FXS/E&M
E1 6/1 TS 1
E1 5/1 TS 1 Voice
Network E1
E1
SCADA Megaplex-4
Megaplex-4 Megaplex RTU
voice port:
bi-direction
SCADA
E1-i CL-A/1 TS 1 Voice

SDH

bi-direction
Figure 8-10. Bidirectional Voice Grade Data Broadcast 1:n

DS0 Cross-Connect
Configuring a DS0 Cross-Connection
 To configure a DS0 cross-connection:

1. At the config# prompt, enter cross-connect or cr.
The config>xc# prompt appears.
2. Configure the cross-connection as illustrated and explained below for the
various interfaces.
Cross-connecting timeslot x (or ds0 {e1 | t1 | e1-i | t1-i | ds1} no ds0 {e1 | t1 | e1-i | t1-i | ds1}
range of sequential timeslots <slot>/<port>/[<tributary>] ts <slot>/<port>/[<tributary>] ts {<x> |
x1..x2) of the e1/t1/e1-i/t1- {<x> | <[x1..x2]>} e1 <[x1..x2]>} e1 <slot>/<port>/
i/ds1/ds1-opt port to timeslot <slot>/<port>/[<tributary>] [<tributary>] {ts <y> | start-ts <y1>}
y (or range of sequential {ts <y> | start-ts <y1>} {data | removes cross-connection
timeslots starting from y1) on voice} [bi-direction | unidirection- If one of the timeslots is defined as
the e1 port and setting rx | unidirection-tx] voice and the CL module has no
its/their type and direction SDH/SONET ports, this cross-connect
is impossible for internal T1 ports 17
to 28 of the T3 module (due to
insufficient signaling bandwidth).
See Examples 3,4
range of sequential timeslots <slot>/<port>/[<tributary>] ts <slot>/<port>/[<tributary>] ts {<x> |
x1..x2) of the e1/t1/e1-i/t1- {<x> | <[x1..x2]>} t1 <]x1..x2]>} t1 <slot>/<port>/
i/ds1/ds1-opt port to timeslot <slot>/<port>/[<tributary>] [<tributary>] {ts <y> | start-ts <y1>}
y (or range of sequential {ts <y> | start-ts <y1>} {data | removes cross-connection
timeslots starting from y1) on voice} [bi-direction | unidirection- If one of the timeslots is defined as
the t1 port and setting its/their rx | unidirection-tx] voice and the CL module has no
type and direction SDH/SONET ports, this cross-connect
is impossible for internal T1 ports 17
to 28 of the T3 module (due to
insufficient signaling bandwidth).
See Examples 3,4

Cross-connecting timeslot x of ds0 {e1 | t1 | e1-i | t1-i | ds1} no ds0 {e1 | t1 | e1-i | t1-i | ds1}
the e1/t1/e1-i/t1-i/ds1 port to <slot>/<port> ts <x> voice <slot>/<port> ts <x> voice
a voice port and setting its <slot>/<port>/[<tributary>} <slot>/<port>/[<tributary>] removes
direction [bi-direction | unidirection-rx | cross-connection
unidirection-tx | bidirection-rx } [<tributary>] is relevant only for
VC-4/OMNI modules.
bidirection-rx mode is available only
for the following modules:
• VC-4/OMNI modules operating in
omni-bus or p2mp-src module
• E&M interfaces of VS-6/E&M and
FXS/E&M modules.
This selection is available only for a
single internal port (tributary) per
each external port.
If the CL model does not have
SDH/SONET ports, this
cross-connect is impossible for
internal T1 ports 17 to 28 of the T3
module (due to insufficient signaling
bandwidth).
see Examples 1, 5, 7
the e1/t1/e1-i/t1-i/ds1/ds1-opt <slot>/<port>/[<tributary>] ts <x> <slot>/<port>/[<tributary>] ts <x>
port to cmd-channel and cmd-channel <slot>/<port> cmd-channel <slot>/<port> removes
setting its direction [bi-direction | unidirection-rx | cross-connection
unidirection-tx] This command is available in TP and
VS-6/BIN modules. See Example in
Megaplex-4 I/O Modules Installation
and Operation Manual,
Teleprotection Module section.
range of sequential timeslots <slot>/<port> ts <x> serial <slot>/<port> ts <x> serial
x1..x2) of the e1/t1/e1-i/t1- <slot>/<port> [bi-direction | <slot>/<port> removes
i/ds1/ds1-opt port to a serial unidirection-rx | unidirection-tx | cross-connection
port and setting its direction bidirection-rx } bidirection-rx mode is available only
in VS modules operating in 3-bit
transitional mode at the rate of
64 kbps.
see Examples 1, 2, 6, 8
Cross-connecting timeslot x of ds0 {e1 | t1 | e1-i | t1-i | ds1} bi-direction –not used in this version
the e1/t1/e1-i/t1-i/ds1 port to <slot>/<port> ts <x> tdm-bridge unidirection-rx – can be used in
a tdm bridge of VS module and <slot>/<port> [bi-direction | monitoring applications
setting its direction in unidirection-rx | bidirection-rx }
bidirection-rx - use for connections
bidirectional broadcast
to RTUs
applications
see Example 9

Cross-connecting the range of ds0 {e1 | t1 | e1-i | t1-i} no ds0 {e1 | t1 | e1-i | t1-i}
sequential timeslots x1..x2) of <slot>/<port>/[<tributary>] ts <slot>/<port>/[<tributary>] ts
the e1/t1/e1-i/t1-i port to an <x1..x2> hdlc <slot>/<port> <x1..x2> hdlc <slot>/<port> removes
hdlc port (M8E1, M8T1 cross-connection
modules) x2 must be an even number
(Ethernet can be mapped only to an
even number of TS).
range of sequential timeslots <slot>/<port>/[<tributary>] ts <slot>/<port>/
x1..x2) of the e1/t1/e1-i/t1- {<x> | <[x1..x2]>} e1-i [<tributary>] ts {<x> | <[x1..x2]>}
i/ds1/ds1-opt port to timeslot <slot>/<port>/[<tributary>] {ts e1-i <slot>/<port>/ [<tributary>] {ts
y (or range of sequential <y> | start-ts <y1>} {data | voice} <y> | start-ts <y1>} removes cross-
timeslots starting from y1) on [bi-direction | unidirection-rx | connection
the e1-i port and setting unidirection-tx] See Examples 3,4
its/their type and direction
x1..x2) of the e1/t1/e1-i/t1- {<x> | <[x1..x2]>} t1-i [<tributary>] ts {<x> | <[x1..x2]>}
i/ds1/ds1-opt port to timeslot <slot>/<port>/[<tributary>] {ts t1-i <slot>/<port>/ [<tributary>] {ts
y (or range of sequential <y> | start-ts <y1>} {data | voice} <y> | start-ts <y1>} removes cross-
timeslots starting from y1) on [bi-direction | unidirection-rx | connection
the t1-i port and setting unidirection-tx] See Examples 3,4
x1..x2) of the e1/t1/e1-i/t1- {<x> | <[x1..x2]>} ds1 [<tributary>] ts {<x> | <[x1..x2]>}
i/ds1/ds1-opt port to timeslot <slot>/<port>/[<tributary>] {ts ds1 <slot>/<port>/ [<tributary>]
y (or range of sequential <y> | start-ts <y1>} {data | voice} {ts <y> | start-ts <y1>} removes
timeslots starting from y1) on [bi-direction | unidirection-rx | cross-connection
the ds1 port and setting unidirection-tx]
Cross-connecting timeslot x of ds0 {e1 | t1 | e1-i | t1-i | ds1} Using no before ds0 {e1 | t1 | e1-i |
the e1/t1/e1-i/t1-i/ds1 port to <slot>/<port>/[<tributary>] ts <x> t1-i | ds1} <slot>/<port>/
bri port (HS-S, HS-U-6, bri <slot>/<port>/[<tributary>] [<tributary>] ts <x> bri
HS-U-12 modules) <slot>/<port> /[<tributary> removes
cross-connection
the e1/t1/e1-i/t1-i/ds1 port to <slot>/<port>/[<tributary>] ts <x> <slot>/<port>/
serial-bundle port (LS-6N, serial-bundle <slot>/<port> [bi- [<tributary>] ts <x> serial-bundle
LS-12 modules) direction | unidirection-rx | <slot>/<port> removes
unidirection-tx ] cross-connection

Note: The optional <tributary> index relates to different cards and denotes different entities, depending on
the ports if follows:
• When following {e1 | t1 | e1-i | t1-i | ds1} options, the index relates to only of the following:
 Megaplex Optimux cards (OP-34C, OP-108C) and denotes their internal E1 ports. Therefore, the
cross-connect side involving these tributary ports is relevant only for e1 port options, not for t1,
e1-i, t1-i, or ds1.
 Megaplex T3 modules and denotes their internal T1 ports. Therefore, the cross-connect side involving
these tributary ports is relevant only for t1 port options, not for e1, e1-i, t1-i, or ds1.
• When following bri port, the index relates to B1 and B2 channels.
Example 1. Bidirectional DS0 Cross-Connect: CL <-> I/O

Modules, Single Timeslot
• CL-A, port E1-i port 1/1, timeslot 1 to voice port 8/1
• CL-A, port E1-i port 1/1, timeslot 2 to serial port 9/1
config
cr
ds0 e1-i cl-a/1 ts 1 voice 8/1 bi-direction
ds0 e1-i cl-a/1 ts 2 serial 9/1 bi-direction
Example 2. Consecutive Timeslot Assignment: E1/T1/E1-i/T1-i

Port <-> Serial Module Port
In this example the entire traffic from the E1 port 1/1 (M8E1 module) is
transferred to HS-12N port 10/1 and vice versa. The ds0 cross-connect must be
used here since the M8E1 port is configured as framed.
config
cr
ds0 e1 1/1 ts [1..31] serial 10/1 bi-direction
Example 3. Consecutive Timeslot Assignment: Two

E1/T1/E1-i/T1-i I/0 Module Ports
In this example the entire traffic from the E1 port 1/2 (M8E1 module) is
transferred to E1-i port 9/1 (M8SL module) and vice versa. The ds0 cross-connect
must be used here since both ports are configured as framed. Note that in this
case the command must be repeated in both directions, and the word “bi-
direction” is optional.
config
cr
ds0 e1 1/2 ts [1..31] e1-i 9/1 start-ts 1 data bi-direction
ds0 e1-i 9/1 ts [1..31] e1 1/2 start-ts 1 data bi-direction
Example 4. Unidirectional Broadcast: M8E1 Port is Sending

Data to three M8E1 ports using UniRx
• Source port (sending data):
 M8E1, port 1/1, timeslot 1

• Destination ports (receiving data):

 M8E1, port 3/1, timeslot 1.
config
cr
ds0 e1 1/2 ts 1 e1 1/1 ts 1 data unidirection-rx
Example 5. Unidirectional Broadcast: Voice Port is Sending

Data to M8E1 Port using UniTx
• Sending from:
 VC-16, port 8/1,
• Sending to:
config
cr
ds0 e1 1/1 ts 1 voice 8/1 unidirection-tx
Example 6. Unidirectional Broadcast: Serial Port is Sending

Data to M8E1 Port using UniTx
• Sending from:
 HS-6N, port 9/1,
• Sending to:
config
cr
ds0 e1 1/2 ts 1 serial 9/1 unidirection-tx
Examples 7a and 7b. Bidirectional Voice-Grade Data Broadcast

1:n
For the application of the VC-4/OMNI module, see Figure 8-7.
• Sending from:
 VC/OMNI, port 3/2/1
 Operation mode: omni-bus
• Sending to/receiving from:
 M8E1 installed in slot 1: port 1, timeslot 1 (connected to RTU)
 M8E1 installed in slot 6: port 1, timeslot 1 (connected to National Center)

 CL-A, port E1-i 1, timeslot 1 (connected to RTU)

configure slot 3 card-type voice vc4-omni
configure slot 1 card-type e1-t1 m8e1
configure port e1 1/1 no shutdown

configure port e1-i cl-a/1 no shutdown
configure port voice 3/2 no shutdown

configure port voice 3/2 operation-mode omni-bus
configure port voice 3/2/1 no shutdown

configure cross-connect ds0 e1 1/1 ts 1 voice 3/2/1 bidirection-rx
configure cross-connect ds0 e1 5/1 ts 1 voice 3/2/1 bidirection-rx
configure cross-connect ds0 e1-i cl-a/1 ts 1 voice 3/2/1 bidirection-rx
configure port voice 3/2/2 no shutdown

configure cross-connect ds0 e1 6/1 ts 1 voice 3/2/2 bi-direction
---------------------------------------------------------------------------
mp4100>config>port>voice(3/2)# info detail

name "IO-3 voice 02"
no shutdown
coding a-law
tx-gain "0.0"
rx-sensitivity "0.0"
operation-mode omni-bus
mp4100>config>port>voice(3/2/1)# info detail

name "IO-3 voice 02/01"
no shutdown
mp4100>config>port>voice(3/2/2)# info detail

name "IO-3 voice 02/02"
no shutdown
mp4100>config>xc# info detail

ds0 e1 1/1 ts 1 voice 3/2/1 bidirection-rx
ds0 e1 5/1 ts 1 voice 3/2/1 bidirection-rx
ds0 e1-i cl-a/1 ts 1 voice 3/2/1 bidirection-rx
ds0 e1 6/1 ts 1 voice 3/2/2 bi-direction
For the application of FXS/E&M module, see Figure 8-10.
• Sending from:

 FXS/E&M, port 9/9

configure slot 9 card-type versatile vs-fxs-em

config port voice 9/9 signaling cas

config port voice 9/9 wire 4
configure cross-connect ds0 e1 1/1 ts 1 voice 9/9 bidirection-rx
configure cross-connect ds0 e1 5/1 ts 1 voice 9/9 bidirection-rx
configure cross-connect ds0 e1-i cl-a/1 ts 1 voice 9/9 bidirection-rx
config port voice 9/4 signaling cas

configure cross-connect ds0 e1 6/1 ts 1 voice 9/4 bi-direction
Example 8. Bidirectional Broadcast: Serial Port is Sending Data

to Remote RTUs over Various E1 Ports
For illustration, see Figure 8-8.
• Sending from:
 VS-12, serial port 3/1
 Encapsulation mode: 3-bit-transitional
config cr ds0 e1 1/1 ts 1 serial 3/1 bidirection-rx
config cr ds0 e1 5/1 ts 1 serial 3/1 bidirection-rx
config cr ds0 e1-i cl-a/1 ts 1 serial 3/1 bidirection-rx
Example 9. Bidirectional Broadcast with Monitoring over E1

For illustration, see Figure 8-9.

• Sending from:
 VS-12, serial port 3/2
 Encapsulation mode: 3bit-transitional
• Monitoring:
configure slot 3 card-type versatile vs-12

configure port serial 3/2 no shutdown

configure port serial 3/2 encapsulation-mode 3-bit-transition
configure port tdm-bridge 3/1 no shutdown

configure port tdm-bridge 3/1 bind serial 3/2
#======================================#
# Active OC : BI-BRD-RX to 3 RTUs #
#======================================#
configure cross-connect ds0 e1 1/1 ts 1 tdm-bridge 3/1 bidirection-rx

configure cross-connect ds0 e1 5/1 ts 1 tdm-bridge 3/1 bidirection-rx
configure cross-connect ds0 e1-i cl-a/1 ts 1 tdm-bridge 3/1 bidirection-rx
#==============================================#
# Monitoring NOC : UNI-RX from tdm-bridge 3/1 #
#==============================================#
configure cross-connect ds0 e1 6/1 ts 1 tdm-bridge 3/1 unidirection-rx
TDM Cross-Connect
Configuring a TDM Cross-Connection
 To configure a TDM cross-connection:

2. Configure the cross connection as illustrated and explained below for the
various interfaces.

Cross-connecting the tdm {e1 | t1 | e1-i | t1-i } <slot>/<port> no tdm {e1 | t1 | e1-i | t1-i }
full payload from this {e1 | t1 | e1-i | t1-i } <slot>/<port> <slot>/<port> command disables
e1/t1/e1-i/t1-i/serial the cross-connection
port with another port Unframed T1 port of M16T1 module
of the same type and cannot be cross-connected with
configuration T1-i port of CL module
If the CL module has no SDH/SONET
ports, this cross-connect is
impossible for unframed E1/T1 port
of VS-16E1T1-PW and VS-6/E1T1
module.
Cross-connecting the tdm e1 <slot>/<port>/<tributary> Megaplex Optimux cards (OP-34C,

full e1 payload from e1 <slot>/<port>/<tributary> OP-108C) only
this tributary port with no tdm e1 <slot>/<port>/
another port of the <tributary> command disables the
same type and cross-connection
configuration
Cross-connecting the tdm t1 <slot>/<port>/<tributary> T3 modules only

full t1 payload from this t1 <slot>/<port>/<tributary> no tdm t1 <slot>/<port>/
tributary port with <tributary> command disables the
another port of the cross-connection
same type and
configuration
Example 1
• Cross-connecting the full E1 payload
• M16E1 module installed in slot 3
• E1 port 3 with E1 port 2
mp4100>config>xc# tdm e1 3/2 e1 3/3
Example 2
• Port 2, line type G.732S
mp4100>config>port>e1(1/2)# line-type g732s
• Cross-connecting E1 port 2 with internal E1 port 1 on CL-A module
mp4100>config>xc# tdm e1 1/2 e1-i cl-a/1
• Cross-connecting (mapping) internal E1 port 1 to the SDH:
 VC-12 = 2
 TUG-3 = 1
 TUG-2 = 1
 AUG 1 = 1
 SDH port 1 on the CL-A module.

mp4100>config# cr sdh-sonet vc12-vt2 cl-a/1/1/1/1/2 e1-i cl-a/1
Split Timeslot Cross-Connect
Configuring a Cross-Connection
 To configure a split timeslot cross-connection:

various interfaces.
Cross-connecting the split-ts {e1 | t1 | e1-i | t1-i | ds1} Used for VC-4A/VC-8A modules working
timeslot bits of the <slot>/<port>/[<tributary>] ts <ts in ADPCM mode
e1/t1/e1-i/t1-i/ds1 port x> bits <bit y> voice voice no ds0 {e1 | t1 | e1-i | t1-i | ds1}
with this voice port <slot/port[/tributary]>} <slot>/<port>/[<tributary>] ts <ts x>
(defining the selected data bits <bit y> voice <slot>/<port>
rate on the voice port) removes cross-connection
The entire number of cross-connected
timeslot bits should match the selected
data rate
Cross-connecting the split-ts {e1 | t1 | e1-i | t1-i | ds1} no ds0 {e1 | t1 | e1-i | t1-i | ds1}
timeslot bits of the <slot>/<port>[<tributary>] ts <ts x> <slot>/<port>/[<tributary>] ts <ts x>
e1/t1/e1-i/t1-i/ds1 port bits <bit y> serial bits <bit y> serial <slot>/<port>
with this serial port <slot/port[/tributary]>} removes cross-connection
(defining the selected data The entire number of cross-connected
rate on the serial port) timeslot bits should match the selected
data rate
e1/t1/e1-i/t1-i/ds1 port bits <bit y> serial-bundle bits <bit y> serial-bundle <slot>/<port>
with this serial-bundle port <slot>/<port>} removes cross-connection
(defining the selected data The entire number of cross-connected
rate on the serial-bundle timeslot bits should match the selected
port) data rate
e1/t1/e1-i/t1-i/ds1 port rate-bits <bit y> bri <slot>/<port> rate-bits <bit y> bri <slot>/<port>
with this bri port (defining [<tributary>] [<tributary>] removes cross-connection
the selected data rate on The entire number of cross-connected
the bri port) timeslot bits should match the selected
data rate

Note: The optional <tributary> index relates to different cards and denotes different entities, depending on
the ports if follows:
• When following {e1 | t1 | e1-i | t1-i | ds1} options, the index relates to Megaplex Optimux cards (OP-34C,
OP-108C) only and denotes their internal E1 ports. Therefore, the cross-connect side involving these
tributary ports is relevant only for e1 port options, not for t1, e1-i, t1-i, or ds1.
• When following bri port, the index relates to B1 and B2 channels.
Example
The following section illustrates how to configure the HS-RN module installed in
slot 8 and cross-connect its serial ports with timeslot bits of the M8E1 module
installed in slot 1:
• Data rate 9.6 kbps on ports 1 and 2.
• Data rate 19.2 kbps on ports 3 and 4.
• Administratively enable the ports.
• Cross-connect serial port 1 with bits 1 and 2 of timeslot 1 of E1 port 2 of
M8E1 module installed in slot 1 (total data rate 9.6 kbps on serial port 1)
• Cross-connect serial port 2 with bits 1 and 2 of timeslot 1 of E1 port 3 of
the same M8E1 module (total data rate 9.6 kbps on serial port 2)
• Cross-connect serial port 3 with bits 1,2,3,4 of timeslot 1 of E1 port 4 of the
same M8E1 module (total data rate 19.2 kbps on serial port 3)
• Cross-connect serial port 4 with bits 1,2,3,4 of timeslot 1 of E1 port 5 of the
same M8E1 module (total data rate 19.2 kbps on serial port 4)
The total data rate transferred on the HS-RN module is 57.6 kbps.
mp4100>config# #------------hsr-n----------------
mp4100>config# port serial 8/1 no shutdown
mp4100>config# port serial 8/1
mp4100>config>port>serial(8/1)# rate 9.6
mp4100>config>port>serial(8/1)# exit
mp4100>config#
mp4100>config#
mp4100>config#

mp4100>config#
mp4100>config# cr
mp4100>config>xc# split-ts e1 1/2 ts 1 bits 1 serial 8/1
mp4100>config>xc#
mp4100>config>xc#
mp4100>config>xc#
See more examples in the LS-6N/12 and HSU-6/12 sections of the Megaplex-4 I/O
Modules Installation and Operation Manual.
SDH/SONET Cross-Connect
Configuring an SDH/SONET Cross-Connection
 To configure an SDH/SONET cross-connection:

1. At the config# prompt, enter cross-connect.
various interfaces.
Cross-connecting the E1 port sdh-sonet vc12-vt2 <slot>/<port>/<au4>/ [/tributary] refers to Megaplex Optimux
of an I/O module with a <tug3>/ <tug2>/<vc12-vt2> cards (OP-34C, OP-108C) only
vc12-vt2 from an SDH port e1<slot>/<port> [/tributary] Adding no before the full command
(“transparent clocking”) disables the cross-connection
This command is available only for
unframed E1 links in ASMi-54C/N,
OP-34C, OP-108C, VS-16E1T1-EoP,
VS-16E1T1-PW, VS-6/E1T1 and M16E1
modules
Cross-connecting the vc12-vt2 sdh-sonet vc12-vt2 Adding no before the full command
from an SDH port with an e1-i <slot>/<port>/<au4>/<tug3>/ disables the cross-connection
port of an I/O module <tug2>/<vc12-vt2> e1-i <slot>/<port> For VS-16E1T1-EoP module, this
command is available only when the line-
type of e1-i port is set as g.732n-crc.

Cross-connecting the vc12-vt2 sdh-sonet vc12-vt2 Adding no before the full command
from an SDH port with a ds1 <slot>/<port>/<au4>/<tug3>/ disables the cross-connection
port of an I/O module <tug2>/<vc12-vt2> ds1 <slot>/<port> This command is available only for
unframed DS1 port in VS-16E1T1-PW and
VS-6/E1T1 modules.
Cross-connecting two vc12-vt2 sdh-sonet vc12-vt2 <slot>/<port>/<au4>/ Adding no before the full command
containers <tug3>/ <tug2>/<vc12-vt2> vc12-vt2 disables the cross-connection
<slot>/<port>/<au4>/ <tug3>/<tug2>/ Number of vc-vt containers per CL
<vc12-vt2> module is limited to 252.
Cross-connecting the T1 port sdh-sonet vc11-vt1.5 Adding no before the full command
of an I/O module with a <slot>/<port>/<au4>/<tug3>/ disables the cross-connection
vc11-vt1.5 from a SONET port <tug2>/<vc11-vt5> t1 <slot>/<port> This command is available only for
(“transparent clocking”) unframed T1 links in M16T1 VS-16E1T1-
EoP, VS-16E1T1-PW and VS-6/E1T1
modules
Cross-connecting the sdh-sonet vc11-vt1.5 Adding no before the full command

vc11-vt1.5 from a SONET port <slot>/<port>/<au4>/<tug3>/ disables the cross-connection
with a ds1 port of an I/O <tug2>/<vc11-vt1.5> ds1 <slot>/<port> This command is available only for
module unframed DS1 port in VS-16E1T1-PW and
VS-6/E1T1 modules.
Cross-connecting two sdh-sonet vc11-vt1.5 Adding no before the full command

vc11-vt1.5 containers <slot>/<port>/<au4>/<tug3>/ disables the cross-connection
<tug2>/<vc12-vt2> vc11-vt1.5 Number of vc-vt containers per CL
<slot>/<port>/<au4>/ module is limited to 252
<tug3>/<tug2>/<vc11-vt1.5>
Cross-connecting two vc3-sts1 sdh-sonet vc3-sts1 Adding no before the full command
<slot>/<port>/<au4>/<tug3> vc3-sts1 disables the cross-connection
<slot>/<port>/<au4>/<tug3>
Cross-connecting two sdh-sonet vc4-sts3c <slot>/<port>/<au4> Adding no before the full command
vc4-sts3c vc4-sts3c <slot>/<port>/<au4> disables the cross-connection
Example 1. Direct Transparent Mapping of E1 Links over SDH

M16E1 modules allow direct mapping of E1 links over SDH/SONET in a transparent
mode (this feature is also called “transparent clocking”).
M16E1 module:
• I/O slot 1
• E1 port 2
Mapping E1 port 2 to the following VC-12 container:
• VC-12 = 1
• TUG-3 = 7

• TUG-2 = 1
• AUG 1 = 1
• SDH port 1 on the CL-A module.
cr sdh-sonet vc12-vt2 cl-a/1/1/1/7/1 e1 1/2
Example 2. Mapping Framed E1 Link Payload to VC-12

Container
Framed E1 links do not allow direct mapping to SDH. In this case the mapping is
done in two stages: first the E1 port is mapped to an internal E1 port on the CL.2
module and then the internal E1 port is mapped to the SDH.
• Port 2, line type G.732S
mp4100>config>port>e1(1/2)# line-type g732s
• Cross-connecting E1 port 2 with internal E1 port 46 on CL-A module
mp4100>config>xc# tdm e1 1/2 e1-i cl-a/46
• Cross-connecting (mapping) internal E1 port 1 to the SDH:
 VC-12 = 2
 TUG-3 = 1
 TUG-2 = 1
 AUG 1 = 1
 SDH port 1 on the CL-A module.
mp4100>config# cr sdh-sonet vc12-vt2 cl-a/1/1/1/1/2 e1-i cl-a/46
PW-TDM Cross-Connect
Configuring a PW-TDM Cross-Connection
 To configure a pw-tdm cross connection:

various interfaces.

Establishing cross- pw-tdm pw <pw number> {ds1 e1 and t1 ports are relevant to
connection <slot>/<port> | e1 <slot>/<port> | t1 VS-6/E1T1 and VS-16E1T1/PW modules
between this <slot>/<port> | e1-i <slot>/<port>} only.
pseudowire and time-slots <ts list> e1-i ports are relevant to the
ds1, e1-i, e1, or SH-16/E1/PW module only.
t1 port
The ds1 port should be populated by
using additional ds0 cross-connect
command between ds1 and other ports
in Megaplex-4 (see example below)
Timeslots in a list can be separated by a
comma or given as a range, for example:
1..3, 5.
Using no before the command removes
the cross-connection
Cross-connect cannot be configured to
PWs defined as protection ports.
A single PW can be connected to a single
DS1 or to a single serial port.
Establishing cross- pw-tdm pw <pw number> serial Using no before the command removes
connection <slot>/<port> the cross-connection
between this Cross-connect cannot be configured to
pseudowire and PWs defined as protection ports.
serial port
A single PW can be connected to a single
serial port. The timeslots on the DS1
port are connected automatically in
accordance with the rate defined on the
serial port.
Example 1
This section provides an example on creating a TDM pseudowire cross-connection
between PW 1 and serial HS-12N port.
PW-TDM cross-connect between:
• Pseudowire (PW) 1.
• MPW-1 module installed in slot 2, DS1 port 1, TS 1.
DS0 cross-connect between:
• HS-12N module installed in slot 10, port 1.
configure cross-connect pw-tdm pw 1 ds1 2/1 time-slots 1
configure cross-connect ds0 ds1 2/1 ts 1 serial 10/1
Example 2
This section provides an example on creating a TDM pseudowire cross-connection
between PW 1 and a serial port located on the same VS module.


• Pseudowire (PW) 1.
• VS module installed in slot 1, DS1 port 1, TS 1.
• VS serial module installed in slot 1, port 1.
• VS module installed in slot 1, DS1 port 1, TS 1.
configure cross-connect pw-tdm pw 1 serial 1/1 time-slots 1
detected.
Table 8-7. Cross-Connect Configuration Error Messages
190 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 configured to shutdown).
 One or more module channels are connected to a port
that cannot provide the required connection (for
example, the port is connected to another I/O port).
 For a tdm cross-connection: the port definitions are
not symmetrical
191 Error ILLEGAL TIMESLOT The required number of timeslots must be exactly the
ASSIGNMENT same as the number of timeslots assigned on the relevant
module port
192 Error ILLEGAL CROSS CONNECT The number of timeslots routed between two module
ports must be the same for both modules
193 Error TS-16 IS RESERVED FOR CAS To bypass signaling information between E1 ports on
SIGNALING different modules, timeslot 16 of one module must be
bound to timeslot 16 on the other module. Both ports
must use G732S framing, with or without CRC-4 (G732S,
G723S-CRC4).
194 Error ILLEGAL POSITION OF TS BIT 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
195 Error TS ASSIGNMENT/TS REQUEST The timeslot bit assignment does not match the
MISMATCH requirements for such timeslots

196 Error INCORRECT TS TYPE The definition of the timeslot must correspond to the type
of information generated by the module using the
timeslot:
 Timeslot cross-connected to serial port: the type must
be data (this also applies to timeslots cross-connected
to HSF modules).
 Timeslot cross-connected to voice I/O module: the type
must be voice.
In addition, the types of timeslots cross-connected
between links must be identical.
197 Warning TS DATA TYPE DOESN’T MATCH For T1 links, do not use the B7ZS line code when one or
B7ZS LINE CODE more timeslots are defined as data timeslots
198 Error ILLEGAL BROADCAST The ds0 cross-connect for the specified channel is not
DEFINITION correct.
199 Error NOT COMPLETE BROADCAST The timeslot assignment for the specified port is not
DEFINITION complete.
202 Error UNFRAMED TYPE CROSS-CONNECT TDM cross-connect is not supported between the
MISMATCH following modules:
• OP-108C/34C (E1 ports), M16E1/M16T1 (E1/T1
ports), ASMi-54C/N modules (E1, E1-i ports) on one
side
• M8E1/M8T1 modules (E1/T1 ports), M8SL (E1-i
ports), or MPW-1 (DS1 ports) on the other side
203 Error SPLIT TS BITS X-CONNECTED When configuring split timeslot assignment, shared bits of
TO DIFF SLOTS the same E1/T1 timeslot must be cross-connected with
serial/voice ports belonging to the same slot.
204 Error PORT IS UP BUT NOT X- A port is set to “no shutdown”, but no E1/T1 timeslot is
CONNECTED cross-connected with the port.
205 Error ILLEGAL TS DIRECTION If a timeslot is assigned to a tdm-bridge port, its direction
must be defined as either bidirection-rx or unidirection-rx
(any other option is illegal).
206 Error ASYMMETRIC BI-DIR TS CROSS When using bi-direction cross-connect between two
CONNECT e1/e1-i/t1/t1-i/ds1/ds1-opt ports, the command must be
repeated in both directions. For example:
config cr
ds0 e1 1/2 ts [1..31] e1-i 9/1 start-ts 1 data bi-direction
ds0 e1-i 9/1 ts [1..31] e1 1/2 start-ts 1 data bi-direction

207 Error XC OF VOICE TS WITH SIG IS When CL is CL2-DS0 or CL2-GBEA, some I/O module ports
NOT SUPPORTED cannot be cross-connected to voice ports using cas or
rbmf (robbed bit multiframe) signaling:
• SH-16/E1/PW: DS1 ports 1-16
• VS-6/E1T1: DS1 9-16
• VS-16E1T1/PW: E1/T1 9-16 and DS1 9-16.
Note: For the voice port using “no signaling” or rbf
(robbed bit frame) signaling, this cross-connect is
possible.
319 Error ILLEGAL TDM CROSS CONNECT Unframed T1 port of M16T1 or T3 module cannot be
cross-connected with T1-i port of CL module
750 Error NUM OF BI-DIRECTION-RX TS The total number of timeslots on the VS module serial
EXCEEDS 30 port or tdm-bridge port configured to bidirectional-rx
cross-connect (bidirectional broadcast) cannot exceed 30.
751 Error PORT IS UP BUT NOT BOUND The tdm-bridge port is up but not bound to a serial port.
TO SERIAL
752 Error BOUND SERIAL PORT IS IN The tdm-bridge port is bound to the serial port which is in
SHUTDOWN STATE shutdown state.
753 Error PORT IS BOUND TO MULTIPLE The tdm-bridge port is bound to more than one serial
SERIAL PORTS ports.
754 Error ILLEGAL SERIAL SLOT/PORT The tdm-bridge port is bound to a serial port in another
BOUND slot (the slot of the serial port and tdm-bridge port bound
to it must be the same).
755 Error ILLEGAL ENCAPSULATION The serial port to which the tdm-bridge port is bound
MODE FOR BOUND PORT must be configured to 3-bit-transitional encapsulation
mode.
756 Error PORT IS BOUND TO MULTIPLE The serial port is bound to more than one tdm-bridge
TDM-BRIDGE PORTS ports.
8.3 Ethernet OAM (CFM)

Ethernet Connectivity Fault Management (CFM) is a service-level OAM protocol
that provides tools for monitoring and troubleshooting end-to-end Ethernet
services. This includes proactive connectivity monitoring, fault verification, and
fault isolation. CFM uses standard Ethernet frames and can be run on any
physical media that is capable of transporting Ethernet service frames. Megaplex-
4 also supports performance monitoring per Y.1731.
Megaplex-4 can act as a Maintenance Entity Group Intermediate Point (MIP) or
Maintenance Entity Group End Point (MEP). If Megaplex-4 is acting as a MIP, it
forwards OAM CFM messages transparently, responding only to OAM link trace
(LTM) and unicast OAM loopback (LBM). MIPs are configured manually.
Megaplex-4 Ethernet OAM (CFM) 8-51

Standards
IEEE 802.1ag-D8, ITU-T Y.1731
Benefits
Ethernet service providers can monitor their services proactively and guarantee
that customers receive the contracted SLA. Fault monitoring and end-to-end
performance measurement provide tools for monitoring frame delay, frame delay
variation, and frame loss and availability.
Factory Defaults
By default, there are no MDs, MAs, or MEPs.
The default OAM CFM multicast address is 01-80-C2-00-00-30.
When a maintenance domain is created, it has the following default
configuration.
Parameter Default Remarks
proprietary-cc no proprietary-cc Standard OAM protocol
md-level 3
name string "MD<mdid>" For example the default name for

maintenance domain 1 is “MD1”.
When a maintenance association is created, it has the following default

configuration.
ccm-interval 1s Continuity check interval is 1 second
classification vlan 0
name string "MA<maid>" For example the default name for

maintenance association 1 is “MA1”.
When a maintenance endpoint is created, it has the following default

configuration.
ais no ais
bind no bind
client-md-level 4
8-52 Ethernet OAM (CFM) Megaplex-4

dest-addr-type ccm multicast pm unicast • Destination address type for CCM

messages – multicast
• Destination address type for performance
measurement messages – unicast
direction down
ccm-initiate ccm-initiate Initiate continuity check messages
ccm-priority 0
queue fixed 0 block 0/0
shutdown shutdown Administratively disabled
When a service is created, it has the following default configuration.
delay-threshold 10
delay-var-threshold 10
classification priority-bit 0
dmm-interval 1s
lmm-interval 1s
shutdown shutdown Administratively disabled
When a destination NE is created, it has the following default configuration.
delay two-way data-tlv-length 0
delay-measurement-bin no delay-measurement-bin
delay-var-measurement-bin no delay-var-measurement-bin
loss single-ended user-data
remote mac-address
00-00-00-00-00-00
OAM (Operation, Administration, and Maintenance) describes the monitoring of
network operation by network operators. OAM is a set of functions used by the
user that enables detection of network faults and measurement of network
performance, as well as distribution of fault-related information. OAM may trigger
control plane or management plane mechanisms, by activating rerouting or by
raising alarms, for example, but such functions are not part of the OAM itself.
OAM functionality ensures that network operators comply with QoS guarantees,
detect anomalies before they escalate, and isolate and bypass network defects.
As a result, the operators can offer binding service-level agreements.

Megaplex-4 provides the OAM (CFM) functions listed below in packet-switched

networks:
• End-to-end Connectivity Fault Management (CFM) per IEEE 802.1ag:
 Continuity check (CC)
 Non-intrusive loopback, used to detect loss of bidirectional continuity
 Link Trace for fault localization
• End-to-end service and performance monitoring per ITU-T Y.1731:
 Loss measurement
 Delay measurement.
OAM Elements
The Ethernet OAM mechanism monitors connectivity in Maintenance Association
(MA) groups, identified by a Maintenance Association Identifier (MAID). Each
maintenance association consists of two or more maintenance end points (MEP).
Every MA belongs to a maintenance domain (MD), and inherits its level from the
MD to which it belongs. The MD levels are used to specify the scope of the MA
(provider, operator, customer, etc).
• Maintenance Domain (MD) – The network or the part of the network for
which faults in connectivity can be managed. Each maintenance domain has
an MD level attribute which designates the scope of its monitoring.
• Maintenance Association (MA) – A set of MEPs, each configured with the
same MAID and MD level, established to verify the integrity of a single service
instance.
• Maintenance End Point (MEP) – An actively managed CFM entity. A MEP is
both an endpoint of a single MA, and an endpoint of a separate Maintenance
Entity for each of the other MEPs in the same MA. A MEP generates and
receives CFM PDUs and tracks responses.
• Maintenance Intermediate Point (MIP) – MIPs are defined under the MD level
and are transparent to connectivity messages
OAM Functions
RAD’s carrier Ethernet aggregation and demarcation devices feature a
comprehensive hardware-based Ethernet OAM and performance monitoring for
SLA assurance:
• End-to-end Connectivity Fault Management (CFM) per IEEE 802.1ag:
 Continuity check (CC)
 Non-intrusive loopback
 Link trace for fault localization
• End-to-end service and performance monitoring per ITU-T Y.1731
 Loss measurement (single-ended)
 Delay measurement (two-way).

The device supports:

• Up to 128 maintenance domains (MDs)
• Up to 128 maintenance associations (MAs)
• Up to 128 maintenance endpoints (MEPs). Up to eight MEPs can be
configured for an MA (on EVC.cos configuration).
• Up to 512 remote MEPs. Up to 80 remote MEPs can be configured for a MEP.
• Up to 256 services. Up to eight services can be configured for a MEP.
• Up to 256 destination NEs.
Note The above limits are subject to the limit of 300 received PPS (packets per
second). This includes AIS, Linktrace, and other management packets. It does not
include continuity check (CC), loopback (LB), delay measurement messages
(DMM), or loss measurement messages (LMM). The LB rate is 200 PPS.
MEPs and Services

Megaplex-4 Ethernet main cards support Ethernet OAM functionality and host
MEPs. A MEP can be either Down or Up, depending on its position and port
association, as explained below.
A MEP is transparent to OAM frames whose MD level is higher than the MEP level,
and drops OAM packets whose MD level lower than the MEP level. It fully supports
connectivity check (CC), loopback, link trace and PM counters.
Down MEP
Down MEPs reside at egress ports and are bound to physical ports. These MEPs
receive and send CFM PDU from and to the network. Down MEPs are supported
for either point-to-point or multipoint services. Different MEP locations are
illustrated below.
Figure 8-11 illustrates a point-to-point service between the CL and I/O GbE ports
with the MEP bound to M-ETH port 4. Tx flow in the service points to a queue
block.
Rx Flow
Tx Flow
CL.2 M-ETH
Port 1 DOWN Port 4
MEP
Figure 8-11. Point-to-Point Service with Down MEP Bound to M-ETH Port 4
Figure 8-12 illustrates a point-to-point service between the CL and I/O GbE ports
with the MEP bound to CL.2 port 1. Tx flow in the service points to a queue block.

Rx Flow
Tx Flow
CL.2 M-ETH
Port 1 DOWN Port 4
MEP
Figure 8-12. Point-to-Point Service with Down MEP Bound to CL.2 Port 1
The Down MEP is defined over the physical port, inheriting its MAC address. The
Down MEP location is characterized by:
• Rx flow, whose classification profile can be one of the following:
 Untagged
 Single VLAN
 Single VLAN+P-bit
 Single outer + single inner VLAN
 Single outer VLAN + P-bit + single inner VLAN
 Match all. If configured over an IO port, the flow from the corresponding
SAP must be used. It also needs a classification profile to specify the
packet tag structure (as it cannot be taken from the flow classification
profile).
• Tx flow to a destination queue to forward OAM frames.
Up MEP
Up MEPs are bound to physical ports. These MEPs receive and send CFM PDU from
and to the forwarding block. The Up MEPs inherit their MAC addresses from the
corresponding physical ports (egress ports of Tx flows). Different MEP locations
are illustrated below.
Figure 8-13 illustrates a point-to-point service between I/O card and CL ports
with the Up MEP bound to the I/O port. The Tx flow in this service points to the
CL port.
Rx Flow
Tx Flow
CL.2 UP M-ETH
Port 1 MEP Port 4
Figure 8-13. Point-to-Point Service with Up MEP Bound to M-ETH Port 4
Figure 8-14 illustrates a point-to-point service between the CL.2 card and I/O
ports with the Up MEP bound to the CL port. Tx flow in this service points to the
I/O port.

Rx Flow
Tx Flow
CL.2 M-ETH
Port 1 UP Port 4
MEP
Figure 8-14. Multipoint Service with Up MEP Bound to CL.2 Port 1
Messaging System
The Ethernet service OAM mechanism uses cyclic messages for availability
verification, fault detection and performance data collection. The main message
types are detailed below.
Note OAM cyclic messages (CCMs, LBMs and LTMs) packet priority (P-bit value) is
user-configurable at MEP level.
CC Messages
Continuity Check Messages (CCMs) are sent from the service source to the
destination node at regular periodic intervals. They are used to detect loss of
continuity or incorrect network connections. A CCM is multicast to each MEP in a
MA at each administrative level. CCM status information is available at the MEP
and RMEP levels.
AIS
When a MEP detects a connectivity failure at a physical port, it propagates an
Alarm Indication Signal (AIS) in the direction away from the detected failure to
the next higher level. The AIS is sent over the MEP Rx flow with the level as
configured by the client MD level (default is the MEP level + 1) for the following
trigger events:
• LOC
• LCK
• Rx AIS.
The signal is carried in dedicated AIS frames. The transmit interval is configured
per MEP and can be set to one frame per second (default) or one frame per
minute. The AIS message priority is set per MEP via P-bit (0–7) configuration.
AIS, LCK, LOC
Rx Flow
MEP
Tx Flow
Port A AIS Port B

(with client MD level)
Figure 8-15. AIS Transmission

RDI
When a downstream MEP detects a defect condition, such as a receive signal
failure or AIS, it sends a Remote Defect Indication (RDI) upstream in the opposite
direction of its peer MEP or MEPs. This informs the upstream MEPs that there has
been a downstream failure. The Tx RDI is also initiated when a LOC is detected on
at least one of the associated RMEPs.
CCM Interval
CCM interval is user-configurable at the MA level to 3.33 ms, 10 ms, 100 ms, 1s,
1m, 10m.
Loopback Messages
MEPs send loopback messages (LBMs) to verify connectivity with another MEP for
a specific MA. Loopback is a ping-like request/reply function. A MEP sends a
loopback request message to another MEP, which generates a subsequent LBR
(loopback response). LBMs/LBRs are used to verify bidirectional connectivity.
The LBMs are always marked green. LBM priority uses the CCM priority that is
configurable as a P-bit value at the MEP level. LBM CoS is set according to a P-bit-
to-CoS profile, with up to four such profiles per chassis.
LBMs are generated on demand and sent up to 500 times.
Link Trace Messages

MEPs multicast LTMs on a particular MA to identify adjacency relationships with
remote MEPs at the same administrative level.
LTMs can also be used for fault isolation. The message body of an LTM includes a
destination MAC address of a target MEP that terminates the link trace. When a
MIP or MEP receives an LTM, it generates a unicast LTR to the initiating MEP. It
also forwards the LTM to the target MEP destination MAC address. An LTM
effectively traces the path to the target MEP.
LTM Priority
The LTMs are always marked green. LTM priority uses the CCM priority that is
configurable as a P-bit value at the MEP level”.
LTM Response and Relay Behavior

This section describes how MEPs relay and respond to LTMs, according to the
Y.1731 requirements.
In Figure 8-16, the MEP responds with LTR if the target MAC address of the
received LTM is the same as the MEP MAC address (inherited from the port to
which the MEP is bound). LTM is not relayed.

LTM
MEP
LTR
Main Card Main Card
Port A Port B
Figure 8-16. MEP with LTM Sent from the Card Port in Point-to-Point Service
Megaplex-4 Ethernet service OAM PM functionality complies with the Y.1731
requirements. Megaplex-4 provides per-service loss and delay measurement and
event reporting.
The following performance parameters are measured by appropriate OAM
messages:
• Frame Loss Ratio (FLR) – FLR is defined as a ratio, expressed as a percentage,
of the number of service frames not delivered divided by the total number of
service frames during a time interval, where the number of service frames not
delivered is the difference between the number of service frames sent to an
ingress UNI and the number of service frames received at an egress UNI.
Megaplex-4 supports single-ended loss measurement (LM) with on-demand
LMM transmission and automatic LM response. OAM MEPs measure frame
loss only if statistic counters have been enabled on the incoming and
outgoing flows. LM is not supported over tunnels.
• Frame Delay (FD) – FD is specified as round trip delay for a frame, where FD
is defined as the time elapsed since the start of transmission of the first bit
of the frame by a source node until the reception of the last bit of the loop
backed frame by the same source node, when the loopback is performed at
the frame’s destination node.
Megaplex-4 supports dual-ended delay measurement (DM) with on-demand
DMM transmission and automatic DM response. Measurement is performed
for delay of up to 1 second with full DM over tunnels.
Configuring OAM
 To configure the service OAM:
1. Configure general OAM parameters
2. Add and configure maintenance domain(s) (MD).
3. Configure maintenance associations for the added MDs.
4. If Megaplex-4 is acting as a MIP, then configure (manually) the necessary MIPs
and configure the necessary flows from and to the unit(s).
5. If Megaplex-4 is acting as a MEP:
a. Configure MA endpoints, referred as MEPs.
b. Configure MEP services.
c. Configure Destination NEs.
d. Configure the necessary flows from and to the unit(s).

Configuring OAM CFM General Parameters

If necessary you can define general OAM CFM parameters. You can also display
OAM CFM information.
Configuring Multicast MAC Address
 To configure the OAM CFM multicast MAC address:

• Navigate to the CFM (Connectivity Fault Management) context
(config>oam>cfm) and enter: multicast-addr <mac-address>
Setting MIP Configuration Mode

Although MIPs are configured only manually you must set the MIP configuration
mode.
 To set the MIP configuration mode:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
2. Enter: mip-assign manual.
3. Now the manual MIP configuration commands are available.
Configuring Measurement Bin Profiles

You can define measurement bin profiles to define sets of threshold ranges for
displaying delay measurements in destination NEs.
 To define measurement bin profiles:

1. Navigate to configure oam cfm.
The config>oam>cfm prompt is displayed.
2. Enter the measurement bin profile level by typing the following:
measurement-bin-profile <name>
The prompt config>oam>cfm>measurement-bin-prof(<name>)# is
displayed.
3. Specify the thresholds (single value, or values separated by commas).
thresholds <thresholds-list>
Each value is used as the upper range of a set of thresholds, up to
5,000,000. For instance, entering thresholds 500,1000,15000 results in
this set of threshold ranges:
 0–500
 501–1,000
 1,001–15,000
 15,001–5,000,000.
4. Specifying the Ethertype expected in Ethernet packet).
Ethertype <0x0000-0xFFFF>

Configuring and Displaying Delay Measurement Bins (Example)
 To configure and display delay measurement bins:

• Bin1 used for round trip delay measurements, with threshold ranges:
 0–15,000
 15,001– 49,000
 49,001–55,000
 55,001–250,000
 250,001–5,000,000.
• Bin2 used for round trip delay variation measurements, with threshold
ranges:
 0–15,000
 15,001– 55,000
 55,001–105,000
 105,001–205,000
 205,001–5,000,000.
mp4100>config>oam>cfm# measurement-bin-profile bin1
mp4100>config>oam>cfm>measurement-bin-prof(bin1)# thresholds 15000,49000,55000,250000
mp4100>config>oam>cfm>measurement-bin-prof(bin1)# exit
mp4100>config>oam>cfm# measurement-bin-profile bin2
mp4100>config>oam>cfm>measurement-bin-prof(bin2)# thresholds 15000,55000,105000,205000
mp4100>config>oam>cfm>measurement-bin-prof(bin2)# exit
mp4100>config>oam>cfm# ma 1 ma 1 mep 1 serv 1 dest-ne 3
mp4100>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# delay-measurement-bin
profile bin1
mp4100>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# delay-var-measurement-bin
profile bin2
mp4100>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
delay-measurement-bins rt-delay all
Type : rt Delay
Current
-----------------------------------------------------------------------------
Bin range Rx DMR
(us)
-----------------------------------------------------------------------------
1 0..15000 0
2 15001..49000 0
3 49001..55000 0
4 55001..250000 0
5 250001..5000000 0

Type : rt Delay
Interval Bin range Rx DMR

(us)
-----------------------------------------------------------------------------
1 1 0..15000 36
1 2 15001..49000 0
1 3 49001..55000 0
1 4 55001..250000 0
1 5 250001..5000000 0
2 1 0..15000 753
2 2 15001..49000 0
2 3 49001..55000 0
2 4 55001..250000 0
2 5 250001..5000000 0
3 1 0..15000 713
3 2 15001..49000 0
3 3 49001..55000 0
3 4 55001..250000 0
3 5 250001..5000000 0
mp4100>config>oam>cfm>md(1)>ma(1)>mep(1)>service(1)>dest-ne(3)# show
delay-measurement-bins rt-delay-var all
Type : rt Delay Var
Current
-----------------------------------------------------------------------------
Bin range Rx DMR
(us)
-----------------------------------------------------------------------------
1 0..15000 0
2 15001..55000 0
3 55001..105000 0
4 105001..205000 0
5 205001..5000000 0

Type : rt Delay Var
Interval Bin range Rx DMR

(us)
-----------------------------------------------------------------------------
1 1 0..15000 36
1 2 15001..55000 0
1 3 55001..105000 0
1 4 105001..205000 0
1 5 205001..5000000 0
2 1 0..15000 753
2 2 15001..55000 0
2 3 55001..105000 0
2 4 105001..205000 0
2 5 205001..5000000 0
3 1 0..15000 713
3 2 15001..55000 0
3 3 55001..105000 0
3 4 105001..205000 0
3 5 205001..5000000 0
Displaying OAM CFM Information

You can display OAM CFM information by typing show summary, as shown in the
following.
mp4100# configure oam cfm
mp4100# config>oam>cfm# show summary
md slot/ classifi admin mep ok/total
md/ma/mepid md/ma name lvl port cation status def r.meps
001/001/001 MD1/MA1 3 eth1 100 enable off 1/1

002/002/8191 1234567890123456789012 3 eth1 0 disable
34567890/1234567801234
002/005/123 1234567890123456789012 3 eth1 100/ enable off 0/2
34567890/155 200
002/006/101 1234567890123456789012 3 eth3 untagged enable off 0/3
003/001/001 /iccname 4 eth1 100.1 enable off 0/1
004/001/001 20-64-32-AB-CD-64 120/ 0 eth1 4000 enable off 0/1
MA1
004/002/001 20-64-32-AB-CD-64 120/ 0 eth1 3000/ enable off 0/3
12345678901234567890123
You can display information on MIPs by typing show mips (see an example
below).
Configuring Maintenance Domains

MDs are domains for which the connectivity faults are managed. Each MD is
assigned a name that must be unique among all those used or available to an
operator. The MD name facilitates easy identification of administrative
responsibility for the maintenance domain.
 To add a maintenance domain:
• At the config>oam>cfm# prompt, enter maintenance-domain <mdid>
where <mdid> is 1–128.

The maintenance domain is created and the

config>oam>cfm>md(<mdid>)$ prompt is displayed.
 To delete a maintenance domain:

• At the config>oam>cfm# prompt, enter no maintenance-domain <mdid>.
The maintenance domain is deleted.
 To configure a maintenance domain:
1. Navigate to configure oam cfm maintenance-domain <mdid> to select the
maintenance domain to configure.
The config>oam>cfm>md(<mdid>)# prompt is displayed
Configuring maintenance maintenance -association <maid> Refer to Configuring Maintenance

association for the MD no maintenance –association <maid> Associations.
no maintenance –association <maid>
deletes the MA
Specifying the maintenance md-level <md-level> The allowed range for md-level is 0–7
domain level Note: If pre-standard OAM protocol is
being used, the only value allowed for
the maintenance domain level is 3.
Specifying the name format name string <md-name-string> • Maximum length of md-name-string is
and name of the name dns <md-name-string> 43 characters
maintenance domain • Maximum combined length of
name mac-and-uint <md-name-mac>
<md-name-uint> md-name-string and ma-name-string
(maintenance association name) is
no name
48 characters
• Format mac-and-uint – Specify
md-name-mac as xx-xx-xx-xx-xx-xx,
and md-name-uint as an unsigned
integer decimal number (0–65535)
• If prestandard OAM protocol is being
used, the maintenance domain must
have no name (use command no
name).
Specifying the OAM no proprietary-cc • Use no proprietary-cc for standard

protocol type proprietary-cc OAM protocol
• Use proprietary-cc for prestandard
OAM protocol.
Note: The MD must have no name (via
no name) and the level must be 3 before
you can set the protocol to prestandard.
Displaying information on show maintenance-association <maid>

configured MAs

Configuring Maintenance Associations

A maintenance domain contains maintenance associations, for each of which you
can configure the continuity check interval and maintenance endpoints (MEPs).
 To add a maintenance association (MA):
• At the config>oam>cfm>md(<mdid>)# prompt enter:
maintenance-association <maid>
where <maid> is 1–128.
The maintenance association is created and the
config>oam>cfm>md(<mdid>)>ma(<maid>)$ prompt is displayed.
 To delete a maintenance association:

• At the config>oam>cfm>md(<mdid>)# prompt enter: no maintenance-
association <maid>.
The maintenance association is deleted.
 To configure a maintenance association:

1. Navigate to configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> to select the maintenance association to
configure.
The config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt is displayed
Specifying the interval ccm-interval {3.33ms | 10ms |

between continuity check 100ms | 1s | 10s | 1min | 10min}
messages
Associating the MA with a classification vlan <vlan-id> Verify that the VLAN is the same as the VLAN
VLAN associated with the MEP
Note: If a classifier profile is associated with
the MEP, the VLAN should be set to 0.
Configuring MEP for the MA mep <mepid> Refer to Configuring Maintenance Endpoints
Configuring Maintenance Endpoints

Maintenance endpoints reside at the edge of a maintenance domain. They initiate
and respond to CCMs, link trace requests, and loopbacks, in order to detect,
localize, and diagnose connectivity problems. Megaplex-4 supports up to 128
MEPs.
 To add a maintenance endpoint (MEP):
• At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
mep <mepid>
where <mepid> is 1–8191.
The MEP is created and the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)$ is displayed.

 To delete a maintenance endpoint:

• At the config>oam>cfm>md(<mdid>)>ma(<maid>)# prompt, enter:
no mep <mepid>
The maintenance endpoint is deleted.
Note You can remove a maintenance endpoint regardless of whether it contains

services.
 To configure a maintenance endpoint:

maintenance-association <maid> mep <mepid>to select the maintenance
endpoint to configure.
The prompt config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)#
is displayed.
Enabling sending AIS and defining ais [ interval { 1s | 1min }] To disable AIS sending, enter no ais
the interval [priority <priority>]
Binding the MEP to an Ethernet bind ethernet <slot/port> To remove the MEP from an Ethernet port,
port, Logical Mac or PCS [/tributary]> Logical Mac or PCS, enter no bind
bind logical-mac <slot/port>
bind pcs <slot/port>
Enabling initiation of continuity ccm-initiate To disable initiating continuity check

check messages (CCM) messages, enter no ccm-initiate
Specifying the priority of CCMs, ccm-priority <priority> The allowed range for <priority> is 0–7
LBMs and LTMs transmitted by the
MEP
Associating the MEP with a classification vlan <vlan-id> You can associate more than one MEP to
classifier profile or VLAN classification profile <profile-name> the same VLAN if the MEPs belong to MDs
with different levels
Verify that the VLAN is the same as the
VLAN associated with the MA
Defining client MD level client-md-level <md_level> Client MD level is a level for sending
upstream AIS
Defining the MEP direction direction {up | down}
Specifying continuity verification continuity-verification <cc-based | This parameter is visible only in

method lb-based> prestandard mode and can be configured
only if ccm-initiate is enabled as explained
above. Use lb-based only for RAD
proprietary OAM functionality.

Defining the MAC address type dest-addr-type [ccm {unicast | If more than one remote MEP ID has been
sent in OAM continuity check multicast}] [pm {unicast | defined for the MEP and you change the
messages (CCM) and performance multicast}] CCM destination address type from
measurement messages (PM) multicast to unicast, all remote MEP IDs
are deleted except for the lowest remote
MEP ID.
If the MAC address type for PM messages
is unicast, then the MAC address for the
transmission of PM messages is
determined by the configuration of the
destination NE. If a remote MAC address is
configured for the destination NE, that
MAC is used. Otherwise if a remote MEP ID
is configured for the destination NE, the
remote MAC address is learned from CCM
messages. Refer to Configuring
Destination NEs for details.
Defining a unicast MAC address if dest-mac-addr <mac-addr> MAC address is in format xx-xx-xx-xx-xx-xx
you defined unicast MAC address
type for CCM messages with the
dest-addr-type command
Defining direction direction { up | down }
Defining forwarding method forwarding-method Currently only e-line is supported.

{ e-line | e-lan }
Defining the queue for the MEP queue fixed <queue-id> To delete queue assignment, enter no
[block <level-id>/<queue-id>] queue queue-mapping
queue queue-mapping
<queue_mapping_profile_name>
[block <level_id>/<queue_id>]
Performing OAM link trace linktrace See Performing OAM Link Trace
Activating OAM loopback lbm See Performing OAM Loopback
Defining remote MEP with which remote-mep <remote_mep_id> Allowed range for remote MEP is 1–8191
the MEP communicates no remote-mep <remote_mep_id> The MEP ID and the remote MEP ID must
be different. You can define up to 511
remote MEPs for the local MEP if standard
OAM protocol is being used for the MD
and the destination address type is
multicast; otherwise you can define only
one remote MEP.
To delete remote MEP, enter no
remote-mep <remote_mep_id>
Configuring service for the MEP service <service_id> Refer to Configuring Maintenance
Endpoint Services
Displaying MEP status show status

Displaying remote MEP status show remote-mep

<remote-mep-id> status
Administratively enabling MEP no shutdown To deactivate the MEP, enter shutdown
Configuring Maintenance Intermediate Points

If you wish to configure MIPs, you must first configure MIP assignment to manual
mode (see Setting MIP Configuration Mode). The MIP must be bound to an
Ethernet port, logical MAC port, or LAG.
 To add a MIP:
• At the config>oam>cfm>md(<mdid># prompt, enter:
mip <mipid>.
The MIP is created and the prompt
config>oam>cfm>md(<mdid>)>mip(<mipid>)$ is displayed.
 To delete a MIP:
• At the config>oam>cfm>md(<mdid>)# prompt enter: no mip <mipid>
The maintenance intermediary point is deleted.
 To configure a MIP:
1. Navigate to configure oam cfm maintenance-domain <mdid> mip <mipid> to
select the MIP to configure.
The config>oam>cfm>md(<mdid>)>mip(<mipid>)# prompt is displayed
Binding the MIP to an bind ethernet <port> To unbind the MIP, enter no bind
Ethernet port, logical MAC bind lag <lag-name>
port, or LAG
bind logical-mac <port-number>
Assigning unidirectional Rx flow uni-direction rx <rx-name> [tx <rx-name> – Rx flow name

and Tx flows to the MIP <tx-name>] <rt-name> – Tx flow name
To delete flow assignment, enter no flow
uni-direction
Administratively enabling no shutdown To deactivate the MIP, enter shutdown

MIP
Displaying MIP status show status
Examples
Configuring MD, MA, and MEP

This example illustrates configuring the following:
• MD ID 1

• MA ID 1
• MEP ID 1:
 Remote MEP ID 2
 Classification VLAN 100.
 To configure MD, MA, and MEP:

#**************************Configure MD
exit all
configure oam cfm
maintenance-domain 1
#**************************Configure MA
maintenance-association 1
#**************************Configure MEP
mep 1
bind ethernet cl-a 1
remote-mep 2
no shutdown
exit all
 To display the configured MD, MA, and MEP:

mp4100# configure oam cfm maintenance-domain 1
mp4100>config>oam>cfm>md(1)# info detail
no proprietary-cc
md-level 3
name string "MD1"
maintenance-association 1
name string "MA1"
ccm-interval 1s
mep 1
bind ethernet cl-a 1
remote-mep 2
dest-addr-type ccm multicast pm unicast
ccm-initiate
ccm-priority 0
forwarding-method e-line
direction down
client-md-level 4
no ais
no shutdown
exit
exit

Displaying MEP Status and Remote MEP Status

The following illustrates displaying MEP status and remote MEP status.
 To display MEP status:

• At the config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)# prompt,
enter: show status.
The MEP status information is displayed.
mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)# show status
Port : Ethernet cl-a/1
Direction : Down
VLAN : 10 Priority : 0
MD Name : MD1
MA Name : MA1
MEP Defect Status

Rx LCK Off
Rx AIS Off
Cross Connected CCM (Mismatch; Unexpected MD Level) Off
Invalid CCM (Unexpected MEP; Unexpected CCM Period) Off
Remote MEP Remote MEP Address Operational Status

---------------------------------------------------------------1
00-20-D2-50-0F-D9 OK
 To display Remote MEP status:

enter: show remote-mep <remote-mep ID> status.
The MEP status information is displayed.
mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)# show remote-mep 1 status
Remote MEP Address : 00-20-D2-50-0F-D9
Operational Status : OK
Configuring MIP
This example illustrates manual MIP configuration:
• MIP is bound to the GbE port 1 of CL-A
• Unidirectional Rx flow assigned to the MIP is "v10in"
• Unidirectional Tx flow assigned to the MIP is "v10out"
mp4100# configure oam cfm ma 1
mp4100>config>oam>cfm>md(1)# mip 1
mp4100>config>oam>cfm>md(1)>mip(1)# bind eth cl-a/1
mp4100>config>oam>cfm>md(1)>mip(1)# info detail
bind ethernet cl-a/1
flow uni-direction rx "v10in" tx "v10out"
no shutdown
mp4100>config>oam>cfm>md(1)>mip(1)# exit
mp4100>config>oam>cfm>md(1)# exit
mp4100>config>oam>cfm# info detail

multicast-addr 01-80-C2-00-00-30
ethertype 0x8902
mip-assign manual
maintenance-domain 1
no proprietary-cc
md-level 3
name string "MD1"
echo "MIP Configuration"
# MIP Configuration
mip 1
bind ethernet cl-a/1
flow uni-direction rx "v10in" tx "v10out"
no shutdown
 To display the MIPs:

mp4100>config>oam>cfm# show mips
MIP
-----------------------------------------------------------------------------
MD/MIP MD Name Level Port Admin Status
1/1 MD1 3 Ethernet Up
cl-a/1
Configuring Maintenance Endpoint Services

You can configure up to 8 services on a MEP. The service configures performance
monitoring (Y.1731) functionality for loss and delay measurements.
 To add a MEP service:

enter: service <serviceid>
where <serviceid> is 1–8.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)$
is displayed.
 To configure a MEP service:

maintenance-association <maid> mep <mepid> service <serviceid> to select
the service to configure (<serviceid> is1–8).
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#
is displayed.
Associating this service with a classification priority-bit <p-bit> The allowed range is 0–7
priority for LMMs and DMMs

Specifying delay threshold in delay-threshold <delay-thresh> The allowed range for delay
microseconds threshold is: 1–5,000,000. If the
threshold is exceeded, the
service is declared as degraded.
Specifying delay variation delay-var-threshold <delay-var-thresh> The allowed range for delay
threshold in microseconds variation threshold is:
1–5,000,000. If the threshold is
exceeded, the service is
declared as degraded.
Specifying the interval for dmm-interval {100ms | 1s | 10s}

delay measurement messages,
to be used by all remote NEs
defined for service
Specifying the interval for loss lmm-interval {100ms | 1s | 10s}

measurement messages, to be
used by all remote NEs defined
for service
Configuring destination NE for dest-ne <dest-ne-index> See Configuring Destination NEs

service below. The value range is
1–255. One NE per service is
allowed.
To delete a destination NE,
enter no dest-ne.
Activating the MEP service no shutdown You can activate a service only if
the corresponding MEP is active
and you have defined at least
one destination NE
Configuring Destination NEs

For performance measurement, the exact address of the destination NE must be
known. You can configure the remote MAC address of the NE, or Megaplex-4 can
learn it from the CCM messages.
If the remote MAC address is not configured and needs to be learned,
performance measurement messages are sent with all 0s in the MAC address until
the address is learned.
 To add a destination NE:

• At the prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service
(<serviceid>)#, enter: dest-ne <dest-ne-index>
where <dest-ne-index> is 1–255.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)$ is displayed.

 To configure a destination NE:

maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index> to select the destination NE to configure.
The prompt
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)
>dest-ne(<dest-ne-index>)# is displayed.
Enabling two-way delay delay two-way

measurement method [data-tlv-length <length-val>]
Defining the delay delay-measurement-bin The delay measurement bin profiles are
measurement bin profile to profile <name> defined in the conf>oam>cfm level
use as delay bin policy
Assigning the delay delay-var-measurement-bin The delay measurement bin profiles are
variation measurement bin profile <name> defined in the conf>oam>cfm level
profile
Defining single-ended loss loss single-ended [{ synthetic | • user-data – This method measures
measurement method user-data | lmm-synthetic }] user data and CCM messages.
• synthetic – This method measures
DM frames. It is recommended when
working with devices that do not
count user data frames
• lmm-synthetic – This method
measures synthetic frames as well.
Defining the MAC address remote mac-address <mac> If the MAC address is
of the destination NE 00-00-00-00-00-00, the statistic
counters for the destination NE do not
increment
Defining the remote MEP ID remote mep-id <remote-mep-id>

of the destination NE
Displaying the delay show delay-measurement-bins Relevant only if profiles were assigned
measurement bins for show delay-measurement-bins via delay-measurement-bin,
delay measurements via {rt-delay | rt-delay-var} current delay-var-measurement-bin
DMRs
- show delay-measurement-bins
{rt-delay | rt-delay-var} interval
<interval-num>
- show delay-measurement-bins
{rt-delay | rt-delay-var} all
Displaying statistics data show statistics

Configuring OAM CFM Service Event Reporting

In addition to the regular OAM statistics collection, Megaplex-4 supports proactive
SLA measurements per OAM service, as per RMON-based RFC 2819. The device
sends reports when one of the counters rises above or drops below the set
thresholds within the specified sampling period of time. These reports can be
sent as SNMP traps to the defined network management stations, or written to
the event log.
The following counters can be monitored:
• Far End Frame Loss Ratio – Total number of OAM frames lost from the local
MEP to the remote MEP, divided by the total number of OAM frames
transmitted since the service was activated
• Near End Frame Loss Ratio – Total number of OAM frames lost from the
remote MEP to the local MEP, divided by the total number of OAM frames
transmitted since the service was activated
• Frames Above Delay – Number of frames that exceeded the delay threshold
• Frames Above Delay Variation – Number of frames exceeding the delay
threshold
• Far End Unavailability Ratio – Total number of far end unavailable seconds
divided by the time elapsed since the service was activated
• Near End Unavailability Ratio – Total number of near end unavailable seconds
divided by the time elapsed since the service was activated.
 To configure the event reporting for a service:

1. Navigate to configure fault cfm.
2. Specify the service and counter for which you wish to configure event
reporting:
service md <mdid> ma <maid> mep <mepid> service <serviceid>
{above-delay | above-delay-var | far-end-loss-ratio | near-end-loss-ratio |
far-end-unavailability-ratio | near-end-unavailability-ratio}
The prompt
config>fault>cfm>service(<mdid>/<maid>/<mepid>/<serviceid>)# is
displayed.
3. Specify the type of event reporting for the counter (refer to Table 8-8):
 For counters above-delay and above-delay-var:
frames-report [event {none | log | trap | logandtrap}] [rising-threshold
<rising-threshold>] [falling-threshold <falling-threshold>]
[sampling-interval <value>]
 For counters near-end-loss-ratio or far-end-loss-ratio:
{1e-3 | 1e-4 | 1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 | 1e-10}] [falling-threshold
{1e-3 | 1e-4 | 1e-5 | 1e-6 | 1e-7 | 1e-8 | 1e-9 | 1e-10}]
 For counters near-end-unavailability-ratio or far-end-unavailability-ratio:
<rising-threshold>] [falling-threshold <falling-threshold>]

4. Type no shutdown to activate the event reporting for the counter.
Table 8-8. Service Event Reporting Parameters
Parameter Description Possible Values
event Specifies the type of event reporting none – The event is not reported
log – The event is reported via the event
log
trap –An SNMP trap is sent to report the
event
logandtrap –The event is reported via the
event log and an SNMP trap
rising-threshold A value above rising-threshold within • For counters above-delay or

falling-threshold the sampling interval for the particular above-delay-var:
event is considered a rising event 1–60
occurrence • For counters near-end-loss-ratio or
A value below falling-threshold within far-end-loss-ratio:
the sampling interval for the particular 1e-3
event is considered a falling event 1e-4
occurrence 1e-5
1e-6
1e-7
1e-8
1e-9
1e-10
• For counters
near-end-unavailability-ratio or
far-end-unavailability-ratio:
1–100
Note: Rising threshold must be greater
than falling-threshold.
sampling-interval Specifies the interval in seconds over Notes:

which the data is sampled and • Relevant only for counters above-delay
compared to the rising and falling or above-delay-var
thresholds
• Sampling interval value must be at
least double rising threshold.
For example:
 To configure OAM CFM event reporting:

• Configure counters for the following service, as shown in the table below:
 Maintenance domain 5
 Maintenance association 8
 MEP 3
 Service 4.

The delay and delay variation (jitter) threshold for this service are set to 10 and
5 milliseconds respectively. The reporting counters for this service are set as
shown in the table below.
Counter Event Type Rising Threshold Falling Threshold Sampling Interval
Frames Above Delay Log and trap 4 2 8
Frames Above Delay Variation Log 10 5 30
Far End Frame Loss Ratio Trap 1e-4 1e-8
Near End Frame Loss Ratio Log and trap 1e-9 1e-10
Far End Unavailability Ratio Trap 40 20
Near End Unavailability Ratio Log 50 25
In this example, an SNMP trap and an event are generated as notification of the
rising threshold if during an 8-second sample interval, four DMM packets or more
exceed the 10-milliseconds delay threshold of this service. The alarm is cleared
(falling threshold) if Megaplex-4 detects an 8-second sample interval in which
two or fewer packets cross the thresholds.
A rising or falling threshold event is generated if a specific ratio is exceeded. For
example, an SNMP trap is sent if the far end Frame Loss Ratio (from Megaplex-4
to the network) exceed 10^-4, i.e. more than one frame out of 10,000 LMMs sent
for this service are lost.
 To define the service delay thresholds:

mp4100# configure oam cfm ma 5 ma 8 mep 3 service 4
mp4100>config>oam>cfm>md(5)>ma(8)>mep(3)>service(4)delay-threshold 10
mp4100>config>oam>cfm>md(5)>ma(8)>mep(3)>service(4) delay-var-threshold 5
 To define the service event reporting counters:

mp4100# configure fault cfm
mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 above-delay
mp4100>config>fault>cfm>service(5/8/3/4/above-delay)$ frames-report event logandtrap
rising-threshold 4 falling-threshold 2 sampling-interval 8
mp4100>config>fault>cfm>service(5/8/3/4/above-delay)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/above-delay)$ exit
mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 above-delay-var

mp4100>config>fault>cfm>service(5/8/3/4/above-delay-var)$ frames-report event log rising-
threshold 10 falling-threshold 5 sampling-interval 30
mp4100>config>fault>cfm>service(5/8/3/4/above-delay-var)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/above-delay-var)$ exit
mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 far-end-loss-ratio

mp4100>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ frames-report event trap
rising-threshold 1e-4 falling-threshold 1e-8
mp4100>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/far-end-loss-ratio)$ exit

mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 near-end-loss-ratio

mp4100>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ frames-report event
logandtrap rising-threshold 1e-9 falling-threshold 1e-10
mp4100>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/near-end-loss-rati)$ exit
mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 far-end-unavailability-ratio

mp4100>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ frames-report event trap
rising-threshold 40 falling-threshold 20
mp4100>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/far-end-unavailabi)$ exit
mp4100>config>fault>cfm# service md 5 ma 8 mep 3 service 4 near-end-unavailability-ratio

mp4100>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ frames-report event log
rising-threshold 50 falling-threshold 25
mp4100>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ no shutdown
mp4100>config>fault>cfm>service(5/8/3/4/near-end-unavailab)$ exit
 To display the defined service event reporting counters:

mp4100>config>fault>cfm# info detail
service md 5 ma 8 mep 3 service 4 above-delay
frames-report event logandtrap rising-threshold 4 falling-threshold 2
sampling-interval 8
no shutdown
exit
service md 5 ma 8 mep 3 service 4 above-delay-var
frames-report event log rising-threshold 10 falling-threshold 5 sampling-
interval 30
no shutdown
exit
service md 5 ma 8 mep 3 service 4 far-end-loss-ratio
frames-report event trap rising-threshold 1e-4 falling-threshold 1e-8
no shutdown
exit
service md 5 ma 8 mep 3 service 4 near-end-loss-ratio
frames-report event logandtrap rising-threshold 1e-9 falling-threshold 1e-10
no shutdown
exit
service md 5 ma 8 mep 3 service 4 far-end-unavailability-ratio
frames-report event trap rising-threshold 40 falling-threshold 20
no shutdown
exit
service md 5 ma 8 mep 3 service 4 near-end-unavailability-ratio
frames-report event log rising-threshold 50 falling-threshold 25
no shutdown
exit
Displaying OAM CFM Statistics

You can display end-to-end performance monitoring data for the OAM services
and destination NEs. The statistics for a service are calculated from the statistics
for its destination NEs.
Megaplex-4 measures performance in fixed 15-minute intervals. It also stores
performance data for the last 12 hours (48 intervals).

You can view the following types of statistics for services and destination NEs:
• Running –OAM statistics collected since the corresponding service was
activated
• 12 hours – OAM statistics for the last 12 hours, or the amount of time since
the service was activated, if less than 12 hours.
• Interval – OAM statistics for the current interval or a selected interval. You
can select an interval only if it has already ended since the corresponding
service was activated.
When a service is first activated, you can view statistics for only the current
interval. The statistics data is shown for the time elapsed since the beginning
of the interval. When the current interval ends, it becomes interval 1 and you
can select it for viewing interval statistics. After each interval ends, you can
select it for viewing interval statistics.
 To display the OAM CFM statistics for a service or destination NE:

1. Navigate to the level corresponding to the OAM service or destination NE for
which you wish to view the statistics (configure oam cfm
maintenance-domain <mdid> maintenance-association <maid> mep <mepid>
service <serviceid> or configure oam cfm maintenance-domain <mdid>
maintenance-association <maid> mep <mepid> service <serviceid> dest-ne
<dest-ne-index>).
The prompt for service or destination NE is displayed:
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)#
config>oam>cfm>md(<mdid>)>ma(<maid>)>mep(<mepid>)>service(<serviceid>)>
dest-ne(<dest-ne-index>)#
Note The service for which you wish to view the statistics must be active. If the service
is not active, the commands to view statistics are not recognized.
Viewing running statistics show statistics running The statistics are displayed; refer to
Table 8-9 and Table 8-10
Viewing statistics for the show statistics current The statistics for the current interval are
current interval displayed; refer to Table 8-9 and
Table 8-10
Viewing the statistics for a show statistics interval • Allowed values for interval-num: 1–
selected interval <interval-num> 48
• The statistics for the selected interval
are displayed; refer to Table 8-9 and
Table 8-10.
• If you specified an interval that has
not yet ended since the service was
activated, a message is displayed that
the interval doesn’t exist.

Viewing statistics for show statistics 12-hours The statistics for the past 12 hours are
12 hours displayed; refer to Table 8-9 and
Table 8-10
Viewing running statistics, show statistics all The statistics are displayed; refer to
statistics for the current Table 8-9 and Table 8-10
interval, statistics for all
intervals, and 12-hour
statistics
Viewing statistics for all show statistics all-intervals The statistics for all intervals are
intervals displayed; refer to Table 8-9 and
Table 8-10
Clearing the statistics for clear-statistics All statistics data for the service or
the service or destination destination NE are cleared, including the
NE stored interval data, except for the
elapsed time since the start of the
current interval
Table 8-9. OAM Statistic Counters
Far End Tx Frames Total number of frames transmitted from local destination NE to
remote destination NE since the service was activated (the type of
frames counted is either user data or synthetic, according to the
method configured by the loss single-ended command)
Far End Rx Frames Total number of frames received by remote destination NE since the
service was activated (the type of frames counted is either user data
or synthetic, according to the method configured by the loss
single-ended command)
Far End Lost Frames Total number of frames lost from local destination NE to remote
destination NE since the service was activated (Far End Tx Frames -
Far End Rx Frames) (the type of frames counted is either user data or
synthetic, according to the method configured by the loss
Far End Frame Loss Ratio (%) Far End Lost Frames divided by Far End Tx Frames

Far End Unavailable Seconds (Sec) Number of seconds the remote destination NE is considered
unavailable. The definition of unavailability differs according to user
data or synthetic measurement mode, as configured by the loss
single-ended command:
• User data – The destination NE is considered unavailable after
10 consecutive seconds with SES (Severely Errored Second)
events; the 10 seconds are part of the unavailable time. An SES is
considered to have occurred if more than one frame out of 1000
is lost. The destination NE is considered available again after
10 consecutive non-SES events; the 10 seconds are part of the
available time.
• Synthetic mode – The destination NE is considered unavailable
after 3.5 consecutive seconds with no reception of synthetic
frames; the 3.5 seconds are part of the unavailable time. The
destination NE is considered available again when a synthetic
frame is received.
Near End Tx Frames Total number of frames transmitted from remote destination NE to
local destination NE since the service was activated (the type of
frames counted is either user data or synthetic, according to the
method configured by the loss single-ended command)
Near End Rx Frames Total number of frames received by local destination NE since the
service was activated (the type of frames counted is either user data
Near End Lost Frames Total number of frames lost from remote destination NE to local
destination NE since the service was activated (Near End Tx Frames -
Near End Rx Frames) (the type of frames counted is either user data
Near End Frame Loss Ratio (%) Near End Lost Frames divided by Near End Tx Frames
Near End Unavailable Seconds (Sec) Number of seconds the local destination NE is considered unavailable.
Refer to the description of Far End Unavailable Seconds for the
definition of unavailability.
Current Delay (uSec) Current delay received in the last Delay Measurement Reply (DMR)
Current Delay Variation (uSec) Difference between the current delay value and the previous current
delay value
Average Two Way Delay (uSec) Average of all frame delay values received in DM frames
Average Two Way Delay Var (uSec) Average difference between the frame delay values received in DM
frames
Frames Above Delay Threshold Number of DM frames whose delay value exceeded the delay
threshold configured for the service
Frames Above Delay Variation Number of DM frames whose delay variation exceeded the delay
Threshold variation threshold configured for the service
Elapsed Time (sec) Time (in seconds) elapsed since the service was activated

Table 8-10. OAM Delay and Loss Measurement Counters
Transmitted LMMs Number of transmitted loss measurement messages

Transmitted DMMs Number of transmitted delay measurement messages
Received LMRs Number of received loss measurement replies
Received DMRs Number of received delay measurement replies
The requested statistics is dispayed, for example as follows.

mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)>service(1)>dest-
ne(1)# show statistics running
Running Counters
---------------------------------------------------------------
Far End TX Frames : 1483
Far End RX Frames : 1483
Far End Lost Frames : 0
Far End Unavailable Seconds (Sec) : 0
Near End TX Frames : 1483

Near End RX Frames : 1483
Near End Lost Frames : 0
Near End Unavailable Seconds (Sec) : 0
Current Delay (mSec) : 0.066 mSec

Current Delay Variation (mSec) : 0.000 mSec
Frames Above Delay Threshold : 1431
Frames Above Delay Variation Threshold : 1
Elapsed Time (sec) : 1469
Loss and Delay Measurements Messages

---------------------------------------------------------------
:
Transmitted
LMMs : 1435
DMMs : 1435
:
Received
LMRs : 1435
DMRs : 1435
Clearing OAM Statistics

• At the corresponding prompt (Destination NE or Service)#, enter
clear-statistics.
mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)>service(1)>dest-
ne(1)# clear-statistics
The statistics for the specified level are cleared.

Performing OAM Loopback

This diagnostic utility verifies OAM connectivity on Ethernet connections. You can
execute the loopback according to the destination MAC address or the remote
MEP number.
Note The option for remote MEP ID is available only if Megaplex-4 can resolve at least
one remote MEP MAC address.
 To run an OAM loopback:

enter all necessary commands according to the tasks listed below.
Specifying remote MEP by lbm address <mac-address> [repeat • MAC address is in the
MAC address <repeat-num>] [data-tlv-length format <xx-xx-xx-xx-xx-xx>
<length-val>] • Allowed range of
Specifying remote MEP by lbm remote-mep <mep-id> [repeat repeat-num is 1–500
MEP ID <repeat-num>] [data-tlv-length • Allowed range of
<length-val>] data-tlv-length is 0–1900
Sending LBM messages to lbm multicast [repeat <repeat-num>]

default multicast MAC
address
Checking OAM loopback show lbm-results

results
For example:
mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)# show lbm-results
Remote MEP ID : 1
Destination Address : 00-20-D2-50-0F-D9
Messages Sent : 1
Replies In Order : 1
Replies Out Of Order : 0
Messages Lost/Timed Out : 0
Messages Lost/Timed Out % : 0
Performing OAM Link Trace

This diagnostic utility traces the OAM route to the destination, specified either by
the MAC address or the maintenance end point (MEP).
Note The option to specify the destination MEP ID is available only if Megaplex-4 can
resolve at least one remote MEP MAC address.
 To run an OAM link trace:

enter all necessary commands according to the tasks listed below.

Specifying remote MEP by MAC linktrace address <mac-address> • MAC address is in the
address [ttl <1–64>] format
<xx-xx-xx-xx-xx-xx>
Specifying remote MEP by ID linktrace remote-mep <mep-id>
[ttl <1–64>] • Allowed range for ttl-value
is 1–64. This parameter
specifies number of hops.
Each unit in the link trace
decrements the TTL until it
reaches 0, which terminates
the link trace.
Checking the OAM link trace show linktrace-results

results
For example:
mp4100>config>oam>cfm>md(1)>ma(1)>mep(100)# show linktrace-
results
Ingress
---------------------------------------------------------------
Hop : 1 MAC Address : 00-20-D2-50-0F-D9

Relay Action : Hit Ingress Action : Ingress OK
Port Sub Type : Interface Alias
Port ID : ETH 1
Egress
--------------------------------------------------------------
8.4 Ethernet OAM (EFM)

This section covers the monitoring of the Ethernet links using OAM EFM (OAM
Ethernet at the First Mile).
Megaplex-4 can act as the active or passive side in an IEEE 802.3-2005
application.
When link OAM (EFM) is enabled for a port, you can view its status by displaying
the port status (show status). You can also display the OAM (EFM) parameters
and OAM (EFM) statistics. You can configure OAM EFM for the following ports:
• GbE ports of CL.2 and M-ETH modules
• PCS ports on ASMi-54C/ETH modules (without E1 links).
Standards
IEEE 802.3-2005
Megaplex-4 Ethernet OAM (EFM) 8-83

Benefits
Ethernet OAM (EFM) provides remote management and fault indication for the
Ethernet links. Remote link failure can be detected via OAM (EFM).
The OAM (EFM) discovery process allows a local data terminating entity (DTE) to
detect Ethernet OAM capabilities on a remote DTE. Once Ethernet OAM support is
detected, both ends of the link exchange state and configuration information,
such as mode, PDU size, loopback support, etc. If both DTEs are satisfied with the
settings, OAM is enabled on the link. However, the loss of a link or a failure to
receive OAMPDUs for five seconds may cause the discovery process to restart.
DTEs may either be in active or passive mode. DTEs in active mode initiate the
ETH-OAM (EFM) communications and can issue queries and commands to a
remote device. DTEs in passive mode generally wait for the peer device to initiate
OAM communications and respond to commands and queries, but do not initiate
them.
A flag in the OAMPDU allows an OAM entity to convey the failure condition Link
Fault to its peer. Link Fault refers to the loss of signal detected by the receiver; A
Link Fault report is sent once per second with the Information OAMPDU.
Factory Defaults
By default, OAM EFM is not enabled for Ethernet/PCS ports.
Configuring OAM EFM

There are two available OAM EFM descriptors. Each can be configured to indicate
active or passive OAM EFM.
 To configure OAM EFM descriptor:

1. Navigate to configure oam efm.
The config>oam>efm# prompt is displayed.
2. Enter:
descriptor <number> {active | passive}
 To configure link OAM (EFM) for Ethernet/PCS port:

1. Navigate to configure port ethernet <slot>/<port> (configure port
pcs <slot>/<port>).
The prompt config>port>eth(<port-num>)#
(config>port>pcs(<port-num>)#) is displayed.
8-84 Ethernet OAM (EFM) Megaplex-4

Enabling link OAM (EFM) efm descriptor <1–2> The EFM descriptor must exist
before you can assign it to a port
In order for link OAM (EFM) to
function properly, the relevant
Ethernet port must be associated
with an L2CP profile that specifies
peer action for MAC 01-80-C2-00-
00-02.
Disabling link OAM (EFM) no efm
Displaying link OAM (EFM) show oam-efm Relevant only if link OAM (EFM) is
parameters enabled.
Displaying link OAM (EFM) statistics show oam-efm-statistics Relevant only if link OAM (EFM) is
enabled.
Commands in level efm
Enabling loopback loopback Type no loopback to disable

loopback
Example
 To enable active link OAM (EFM) for Ethernet port CL-A/1:
#************** Configure L2CP profile for OAM EFM

configure port l2cp-profile mac2peer
mac 01-80-C2-00-00-02 peer
commit
#************** Configure OAM EFM descriptor

exit all
configure oam efm-descriptor 1 active
exit
efm-descriptor 2 passive
commit
#************** Configure Ethernet port CL-A/1:

#************** Associate L2CP profile and OAM EFM descriptor
configure port ethernet cl-a/1
l2cp profile mac2peer
efm descriptor 1
exit
no shutdown
commit
#************** Configure Ethernet port CL-A/1:

#************** Associate L2CP profile and OAM EFM descriptor
l2cp profile mac2peer
Megaplex-4 Ethernet OAM (EFM) 8-85

efm descriptor 1
no shutdown
exit all
#************** Activate an EFM loopback

mp4100>config>port>eth(cl-a/1)>efm#
loopback
#****To display the link OAM (EFM) status for Eth port CL-A/1:

show oam-efm
mp4100>config>port>eth(cl-a/1)# show oam-efm

Administrative Status : Enabled
Operational Status : Operational
Loopback Status : Remote
OAM EFM Information

--------------------------------------------------------------
Local Remote
MAC Address : 00-20-D2-50-30-2D 00-20-D2-F6-8E-A3
Mode : Active Passive
Unidirectional : Supported Not Supported
Vars Retrieval : Supported Supported
Link Events : Supported Supported
Loopback : Not Supported Supported
PDU Size : 1518 1518
Vendor OUI : 0x0020D2 0x0020D2
8.5 Flows
Flows are the main traffic-carrying elements in Megaplex-4 architecture. They are
unidirectional entities that interconnect two physical or logical ports. You can use
classifier profiles to specify the criteria for flows. The classification is per port
and is applied to the ingress port of the flow.
Flows defined in Megaplex-4 can be unidirectional (between physical/logical
ports) or bidirectional (between physical/logic ports and brigde ports of CL
modules).
Note Bridge ports in M-ETH modules are bound directly (without using flows).
Megaplex-4 supports up to 512 unidirectional Ethernet data flows, which can be

used to provide E-line or E-LAN service delivery over Metro Ethernet networks.
Each Ethernet flow connects two ports. Ethernet flows are unidirectional, or
bidirectional in the case of bridge flows. For unidirectional flows, you have to
define two flows between two ports, one for each direction. For bidirectional
flows, you only need to define one flow from a port to a bridge port, and specify
the reverse-direction command.
8-86 Flows Megaplex-4

This section explains how to define the flows according to specific criteria such as
VLAN. You can use classifier profiles to specify the criteria for flows. The
classification is per port and is applied to the ingress port of the flow.
Standards
MEF 6 (E-Line – EPL and EVPL), MEF 10, MEF 9, MEF 14: EPL and EVPL, MEF 20,
IEEE 802.3, 802.3u, 802.1q, 802.1p, 802.3ad, 802.3-2005
Benefits
The user traffic can be classified into different Ethernet flows (EVC.CoS) to
provide services in a flexible manner, using better traffic management and QoS.
Factory Defaults
By default, no flows exist.
Ethernet Entities
Ethernet services are provided by means of the Megaplex-4 I/O modules with
traffic Ethernet ports, which can serve as customer’s edge network interfaces,
and by means of the CL.2 and M-ETH modules, which provide GbE ports that can
serve as service provider’s edge interfaces.
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:
• GbE ports located on the Megaplex-4 CL.2 modules (ethernet or lag in the CLI
language) and on the M-ETH modules (ethernet in the CLI language).
• Ethernet ports on other I/O modules (M8E1, M8T1, M8SL, OP-34C, OP-108C,
ASMi-54C, MPW-1, VS) (ethernet in the CLI language)
• Logical MAC ports (logical-mac). A Logical MAC port is bound to a gfp, hdlc or
mlppp port, which, in its turn, should be bound to the physical layer. The
meaning of the gfp, hdlc or mlppp ports and their further mapping depends
on the Ethernet traffic media:
 GFP ports represent VCGs (Virtual Concatenation Groups) with GFP
encapsulation and exist in two flavors:
 GFP ports defined on CL.2 modules and used for efficient transport of
Ethernet traffic over the SDH/SONET networks. GFP ports can be
mapped either directly to the physical layer or to VCG. In the latter case
to the physical layer.
 GFP ports located on T3 modules and used for efficient transport of
Ethernet traffic over the T1/T3 networks. GFP ports are mapped either
directly to the physical layer or to VCG. In the latter case, the binding is
done in two stages and the VCG is further bound to the physical layer.
Megaplex-4 Flows 8-87

 HDLC ports exist in two flavors:

 HDLC ports defined on CL.2 modules represent VCGs (Virtual
Concatenation Groups) with LAPS encapsulation. They can be mapped
either directly to the physical layer or to another VCG. In the latter case
to the physical layer
 HDLC ports defined on M8E1, M8T1 and M8SL modules represent HDLC
bundles which can be bound to the physical layer representing E1/T1
ports or specific timeslots
 MLPPP ports exist only on M8E1 and M8SL modules and are mapped to
the PPP port. The binding is done in two stages and this PPP port should
be further bound to the physical layer.
The maximum number of HDLC ports that may be defined on an I/O module
(M8E1, M8T1, or M8SL) is 32.
• PCS (Physical Coding Sublayer) ports available on the ASMi-54C/N, ASMI-54C
and SH-16 modules, which determine the Ethernet (packet) physical layer
transmission capabilities over SHDSL lines.
• SVI ports –intermediate Ethernet entities between the Bridge/Router and
another Ethernet port (bound one-to-one). An SVI port also serves as an
ingress or egress port for terminating management flows. The management
flows are configured between the physical port which is the management
source and the corresponding SVI port bound to the bridge port of the
Unaware Management Bridge (see Figure 8-1). For more information on the
bridge connections and configuration see the Management Bridge section.
The incoming Ethernet traffic is forwarded to a bridge port based on the flow
configured between the above entity and a bridge port. Then it is switched
between bridge ports inside the bridge based on MAC and VLAN (IVL) switching.
The last stage is forwarding traffic from the other bridge port to the other entitiy
via a flow.
Aware and Unaware Traffic

In general, a given bridge port can serve as the termination point of several flows
(the maximum number of traffic flows that can be defined on a Megaplex-4 is
512). Therefore, each flow must discriminate among the Ethernet frames (be
aware of the frame VLANs) reaching an associated bridge port in order to
determine how to handle customers’ edge traffic. In general, this action is based
on the user’s VLAN identifier (VLAN ID) received in each frame. For untagged or
priority-tagged traffic, a special VLAN ID is automatically assigned by the
Megaplex-4 for handling the Ethernet traffic.
The range of specific VLAN IDs that can be used for Ethernet traffic with IEEE
802.1Q tags is 1 to 4094 (for the management flow on non-A CL.2 options, only
the range of 1 to 3999 is allowed).
Note
When working with CL.2 (non-A) options, ingress VLAN ID within the 3800-4095
VLAN ID range may not be filtered.
The internal Ethernet switch of the module can also handle other types of
frames, such as untagged frames, and priority-tagged frames (frames with IEEE

802.Q tags with 0 as the VLAN ID). M8E1/M8T1 modules also enable the user to
configure flows to handle traffic with or without IEEE 802.Q tags: this traffic is
forwarded only between the bridge ports mapped to a given flow. This
forwarding mode is usually referred to as VLAN-unaware. In order to transmit
unclassified frames, its classification should be set to ‘match-all’.
The following list summarizes the configuration restrictions applying to the types
of flows to which any given bridge port can be mapped:
• A bridge port can terminate only one flow classified as unaware (i.e., which
does not discriminate Ethernet traffic in accordance with VLANs).
• When a bridge port is mapped to more than one flow, the bridge port can
terminate several flows with specific VLAN IDs, but only one flow classified as
unaware.
• A bridge port can terminate flows with different VLAN IDs (aware flow mode).
VLAN tagging, stacking and striping options enable transporting users’ traffic
transparently, thereby keeping all the user’s VLAN settings intact.
Defining Classifier Profiles

You can define up to 128 classifier profiles to apply to flows to ensure the
desired flow classification.
Note When a classification profile is assigned to a flow, each match in the profile is
allocated one of the 1000 available internal classification match entries,
according to the flow ingress port.
For example, if a classification profile is defined with matches to two different
VLANS, then if the profile is assigned to two flows that use different ingress
ports, the result is that four internal classification match entries are allocated. If
the profile is assigned to two flows that use the same ingress port, the result is
that two internal classification match entries are used.
 To define a classifier profile:

1. Navigate to the flows context (config>flows).
2. Define a classifier profile and assign a name to it:
classifier-profile <profile-name> match-any
The system switches to the context of the classifier profile
(config>flows>classifier-profile(<profile-name>)).
3. Specify the criteria for the classifier profile:
[no] match [ vlan <vlan-range> ] [ inner-vlan <inner-vlan-range> ]
[ p-bit <p-bit-range> ] [ inner-p-bit <inner-p-bit-range> ]
[ ip-precedence <ip-precedence-range> ] [ ip-dscp <ip-dscp-range> ]
[ether-type <ether-type>] [untagged] [non-ip] [all]
4. When you have completed specifying the criteria, enter exit to exit the
classifier profile context.

Examples:
 To create classifier profile with criteria VLAN 100 to VLAN 150:

exit all
configure flows classifier-profile v100_150 match-any
match vlan 100..150
exit all
 To create classifier profile with criteria VLAN 20 and inner VLAN 30:
exit all
configure flows classifier-profile v20_inner_30 match-any
match vlan 20 inner-vlan 30
exit all
 To create classifier profile that matches all criteria:

exit all
configure flows classifier-profile all match-any
match all
exit all
Tagging and Marking

150B
Megaplex-4 supports several options for marking and tagging.

You can perform the following marking actions:
• Overwrite inner or outer VLAN with a new value
• Overwrite inner or outer VLAN p-bit with a new value.
You can perform the following tagging actions:
• Add (push) outer VLAN, with p-bit value that can be copied from the original
value or set to a new value. When you add a new VLAN, the original outer
VLAN becomes the inner VLAN.
• Remove (pop) outer VLAN and p-bit. When you remove a VLAN, the inner
VLAN becomes the outer VLAN.
• Add (push) inner VLAN, with p-bit value that can be copied from the original
value or set to a new value
• Remove (pop) inner VLAN and p-bit.
Only certain combinations of actions on the outer and inner VLAN are allowed.
Refer to Table 8-2 for details on the permitted combinations of actions.
Configuring Flows
45B
 To create and configure a flow:

1. Navigate to the flows context (config>flows).
2. Define a flow and assign a name to it:
flow <flow-name>
The system switches to the respective flow context
(config>flows>flow(<flow-name>))

3. Specify the flow as explained in the table below.
Administratively enabling the no shutdown You can activate a flow only if it is

flow (the flow is created as associated with at least a classifier
inactive by default) profile, ingress port, and egress port.
Using no shutdown disables the flow
Mapping the previously classifier-profile <classifier-profile no classifier removes the mapping

configured classifier profile to name>
the flow
Specifying the egress port egress-port {ethernet | logical-mac All VLANs defined on the same egress
(ethernet, lag, logical-mac, pcs, | pcs} <slot/port> [<tributary>] bridge port must use the same queue-
svi), the egress queue block [queue-map-profile <queue-map- map-profile and block values.
and the queue (or queue map profile-name> block no egress-port removes the flow
profile) within the block <level_id/queue_id>] association with the egress port
egress-port {ethernet | logical-mac [<tributary>] denotes an internal
| pcs} <slot/port> [<tributary>] Ethernet egress port for Optimux
[queue <queue-id> block modules
<level_id/queue_id>]
When working with non-A CL
egress-port lag <port-number> assemblies, a flow between two PCS
[queue-map-profile <queue-map- ports of the same modules cannot be
profile-name> block set. In this case set flows between
<level_id/queue_id>] PCS ports of different modules.
egress-port lag <port-number> Megaplex-4 equipped with CL.2
[queue <queue-id> block modules has the following restriction:
<level_id/queue_id>] if at least one unaware flow is
egress-port bridge-port configured between a PCS port and an
<slot><port> (Note: if ingress-port Ethernet port on the same ASMi-54C
is a port of I/O module, see or ASMi-54C/N module, you can
reverse-direction command below) configure only one more flow on this
egress-port {svi } <port number> module, and it must be of the same
type (PCS – Ethernet, unaware).
egress-port mng-ethernet
Megaplex-4 equipped with CL.2/A
<slot/port>
modules does not have this
restriction.
Local switching (flows between
Ethernet ports on the same module) is
possible in the following cases:
• Within the I/O modules with FE
ports in systems equipped with
CL.2/A modules
• Within the M-ETH module in
systems equipped with any CL.2
modules

Specifying the opposite flow, reverse-direction [queue-map- reverse-direction is used when

the egress queue block and the profile <queue-map-profile-name> egress-port is bridge-port and
queue (or queue map profile) block <level_id/queue_id>] ingress-port is a port of I/O module.
within the block reverse-direction [queue <queue-
id> block <level_id/queue_id>]
Specifying the ingress port ingress-port ethernet no ingress-port removes the flow
(ethernet, lag, logical-mac, pcs, <slot><port>[<tributary>] association with the ingress port
svi) ingress-port {logical-mac | pcs | [<tributary>] denotes an internal
bridge-port} <slot><port> Ethernet ingress port for Optimux
ingress-port {svi | lag } <port modules
number> When working with non-A CL
ingress-port mng-ethernet assemblies, a flow between two PCS
<slot/port> ports of the same modules cannot be
set. In this case set flows between
PCS ports of different modules.
Megaplex-4 equipped with CL.2
modules has the following restriction:
if at least one unaware flow is
configured between a PCS port and an
Ethernet port on the same ASMi-54C
or ASMi-54C/N module, you can
configure only one more flow on this
module, and it must be of the same
type (PCS – Ethernet, unaware).
Megaplex-4 equipped with CL.2/A
modules does not have this
restriction.
Local switching (flows between
Ethernet ports on the same module) is
possible in the following cases:
• Within the I/O modules with FE
ports in systems equipped with
CL.2/A modules
• Within the M-ETH module in
systems equipped with any CL.2
modules
Associating the flow with a policer-profile <policer-profile- no policer removes the flow
policer profile name> association with the policer
Discarding traffic transmitted drop

via the flow
Defining marking actions for mark all Refer to the following table for the
the flow such as overwriting marking actions
the VLAN ID or inner VLAN ID
or setting the priority

Adding VLAN ID with p-bit set vlan-tag push vlan <sp-vlan> p-bit In Megaplex devices with CL modules
to specific value, and fixed <fixed-p-bit> [inner-vlan without Carrier Ready capabilities:
optionally adding inner VLAN <inner-sp-vlan> When a flow is established between a
ID with p-bit set to specific p-bit fixed <inner-fixed-p-bit>] PCS port of ASM-54C/ETH module and
value any other port, the VLAN/classifiers
configured at the egress and ingress
ports must be identical.
Adding VLAN ID with p-bit set vlan-tag push vlan <sp-vlan> p-bit
to specific value, and fixed <fixed-p-bit> [inner-vlan
optionally adding inner VLAN <inner-sp-vlan>
ID with p-bit set via marking p-bit profile <inner-marking-profil
profile e-name>]
Adding VLAN ID with p-bit set vlan-tag push vlan <sp-vlan> p-bit
to specific value, and fixed <fixed-p-bit> [inner-vlan
optionally adding inner VLAN <inner-sp-vlan> p-bit copy]
ID with p-bit set by copying
from the incoming frame
Adding VLAN ID with p-bit set vlan-tag push vlan <sp-vlan>

via marking profile, and p-bit profile <marking-profile-nam
optionally adding inner VLAN e> [inner-vlan <inner-sp-vlan>
ID with p-bit set to specific p-bit fixed <inner-fixed-p-bit>]
value

ID with p-bit set via marking p-bit profile <inner-marking-profil
profile e-name>]

ID with p-bit set by copying p-bit copy]
from the incoming frame

by copying from the incoming p-bit copy
frame, and optionally adding [inner-vlan <inner-sp-vlan>
inner VLAN ID with p-bit set to p-bit fixed <inner-fixed-p-bit>]
specific value:

inner VLAN ID with p-bit set via p-bit profile <inner-marking-profil
marking profile e-name>]


inner VLAN ID with p-bit set by p-bit copy]
copying from the incoming
frame
Removing VLAN ID, and vlan-tag pop vlan [inner-vlan]

optionally removing inner VLAN
ID
Removing pushing of inner no vlan-tag [push inner-vlan]

VLAN
Administratively enabling the no shutdown • You can activate a flow only if it is

flow associated with at least a classifier
profile, ingress port, and egress
port
• Flows are created as inactive by
default
• Type shutdown to disable the flow
The following marking actions can be performed in the mark level, at the
config>flows>flow(<flow-name>)>mark# prompt.

Overwriting p-bit according to marking-profile If a marking profile is used, it must be
marking profile <marking-profile-name> compatible with the classification criteria of the
flow, e.g. if the flow classification is according to
DSCP then the marking classification should not
be according to p bit
If a color-aware marking profile is applied for the
outer VLAN of a flow, then if marking is applied
to the inner VLAN, either the same color-aware
marking profile must be used for the inner VLAN,
or a non-color-aware marking profile must be
used for the inner VLAN.
Typing no marking-profile or
no inner-marking-profile removes the overwriting
of marking profile or inner marking profile
respectively
Overwriting inner p-bit inner-marking-profile See comments for marking-profile

according to marking profile <inner-marking-profile-name>
Overwriting p-bit with a new p-bit <p-bit-value> Typing no p-bit removes the overwriting of p-bit
value
Overwriting inner p-bit with a inner-p-bit <inner-p-bit-value > Typing no inner-p-bit removes the overwriting of
new value inner p-bit
Overwriting VLAN ID with a vlan <vlan-value> Typing no vlan removes the overwriting of VLAN
new value ID

Overwriting inner VLAN ID with inner-vlan <inner-vlan-value> Typing no inner-vlan removes the overwriting of
a new value inner VLAN ID
Exiting the marking context exit

and returning to the flow
context
Example
This section provides an example of creating two management flows between
PCS ports of an ASMi-54C module installed in slot 3. The procedure is as follows:
1. Create two flow classifiers: “mng_flow_bridge_side” and
“mng_flow_port_side”.
2. Create an ingress flow 1 between PCS port 1 of the ASMi-54C module and SVI
port 2 using the following parameters:
 Flow 1
 Classifier named “mng_flow_bridge_side”
 Tagging of the management traffic with VLAN 100, priority bit 7
 Set SVI 2 as ingress port.
 Set PCS 3/1 as egress port.
3. Create an egress flow 2 between PCS port 1 of an ASMi-54C module and SVI
port 2 using the following parameters:
 Flow 2.
 Classifier named “mng_flow_port_side”
 Removing VLAN before entering management bridge
 Set SVI 2 as egress port.
 Set PCS 3/1 as ingress port.
#Step 1
mp4100>config>flows# classifier-profile mng_flow_port_side match-
any match vlan 100
mp4100>config>flows# classifier-profile mng_flow_bridge_side
match-any match all
#Step 2
mp4100>config>flows# flow 1 classifier mng_flow_bridge_side
mp4100>config>flows# flow 1 vlan-tag push vlan 100 p-bit fixed 7
mp4100>config>flows# flow 1 ingress-port svi 2
mp4100>config>flows# flow 1 egress-port pcs 3/1
#Step 3
mp4100>config>flows# flow 2 classifier mng_flow_port_side
mp4100>config>flows# flow 2 vlan-tag pop vlan
mp4100>config>flows# flow 2 ingress-port pcs 3/1
mp4100>config>flows# flow 2 egress-port svi 2

For more examples see Configuring the Bridge section below: bridge configuration
examples include flow configuration as well.
Viewing the Flow Summary

You can view a summary of the flows you just configured.
 To view the flows summary:

• At the config>flows# prompt, enter info detail.
The summary of all configured flows appears.
mp4100>config>flows# info detail
echo "Classifier Profile Configuration"
# Classifier Profile Configuration
classifier-profile "mng" match-any
match vlan 100
exit
# Classifier Profile Configuration
classifier-profile "all" match-any
match all
exit
echo "Flow Configuration"
# Flow Configuration
flow "241"
classifier "mng"
vlan-tag pop vlan
egress-port svi 2
no shutdown
exit
# Flow Configuration
flow "242"
classifier "all"
ingress-port svi 2
egress-port ethernet 1/1
no shutdown
Testing the Flows

The Megaplex flows can be tested by independently activating a loop per each
specific flow as shown in the diagram below. The test can be performed on the
flows with GbE ingress ports only.

Megaplex-4
CL
Traffic
Counter
3rd Party Product Network GbE ETH Engine
Traffic
Generator
Figure 8-17. Loopback per Flow
 To perform a test on a flow:

1. Navigate to the config>flows>flow(<flow-name>) prompt.
Setting test duration and test [duration <duration in seconds Using no test disables the test
activating the test on this flow 0..86400> ]
 To display test results:

1. Navigate to the config>flows>flow(<flow-name>) prompt.
2. Type show test.
The display shows the following:
• The test status: On or Off
• Test duration in sec or Forever
• No TTL – “no time to leave”, always displayed in the current version.
Example
mp4100>config>flows>flow(4)# test duration 10
mp4100>config>flows>flow(4)# show test
Test : On Duration (Sec) : 10 No TTL
Displaying Flow Statistics

You can display the number of forwarded and discarded packets and bytes for a
flow.
 To display the statistics for a flow:

• At the relevant flow context (config>flows>flow(<flow-id>)), enter:
show statistics running.
Flow statistics are displayed.

 To clear the statistics for a flow:

• At the relevant flow context (config>flows>flow(<flow-id>)), enter:
clear-statistics.
The statistics for the flow are cleared.
For example:
 To display flow statistics:

mp4100# configure flows flow f10_out
mp4100>config>flows>flow(f10_out)# show statistics running
Rate Sampling Window
-----------------------------------------------------------------------------
Window Size [Min.] : 15
Window Remain Time [Min.] : 12
Rx Statistics
-----------------------------------------------------------------------------
Total
Packets : 0
Bytes : 0
Drop Statistics
-----------------------------------------------------------------------------
Packets Bytes
Total : 0 0
Green : 0 0
Yellow : 0 0
Red : 0 0
Total(Rate) : 0 0
Green(Rate) : 0 0
Yellow(Rate) : 0 0
Red(Rate) : 0 0
Tx Statistics
-----------------------------------------------------------------------------
Total Green Yellow
Packets : 0 0 0
Rate [pps] : 0 0 0
Bytes : 0 0 0
Rate [bps] : 0 0 0
Peak Measurement
-----------------------------------------------------------------------------
Min. Max.
Tx Bit Rate [bps] : 0 0
Drop Bit Rate [bps] : 0 0
detected.

559 Error INGRESS AND EGRESS PORTS Ingress and egress ports of a flow cannot both be bridge
ARE MEMBERS OF THE SAME ports of the same bridge.
BRIDGE
560 Error UP TO 240 FLOWS FOR DATA The maximum number of unidirectional flows for data for
CL.2 (non-A option) is 240. This does not include
management flows (which contain an SVI Port bound to
BP).
561 Error UP TO 192 FLOWS FOR The maximum number of management flows for CL.2
MANAGENENT (non-A option) is 192.
562 Error FLOW MUST CONSIST OF TWO Flow must connect 2 ports.
PORTS
563 Error SAME INGRESS AND EGRESS Ingress and egress ports must be different.
PORTS
564 Error FLOW MUST HAVE A A classifier profile must be bound to the flow.
CLASSIFIER
565 Error FLOW BETWEEN TWO SVI NOT A flow cannot connect between 2 SVI ports.
ALLOWED
566 Error CL L. MAC CAN’T BE MEMBER A Logical MAC with a VCG bound to it cannot be a member
IN MNG FLOW in a management flow
567 Error ILLEGAL FLOW BETWEEN ETH A flow between external or internal Ethernet ports on the
PORTS same I/O slot is not allowed.
568 Error CLASSIFIER PROFILE MUST BE If an ingress port is SVI bound to BP (management flow),
MATCH ALL the classifier must be “match all”.
569 Error MNG VLAN MUST BE LESS When working with CL.2 module option, management flow
THAN 4000 VLAN ID must be less than 4000 (not relevant for CL.2/A
option).
570 Error ILLEGAL CLASSIFIER FOR PORT The selected classification is not supported by this port.
Correction required according to the following:
• Command match vlan inner-vlan is valid only for flows
between GbE and/or LAG ports defined on CL modules
• Commands match vlan inner-vlan or match vlan are
obligatory for flows between GbE and/or LAG ports
defined on CL modules, no other classifier can be used
on these ports
• I/O port classifier can be only match vlan or match
all.

571 Error VLAN TAG ACTION PUSH NOT VLAN tag push action is not allowed in the following
ALLOWED cases:
• At egress port of flows between GbE and/or LAG ports
defined on CL modules
• On ports of I/O modules participating in non-
management (data) flows.
572 Error VLAN TAG ACTION POP NOT VLAN tag pop action is not allowed in the following cases:
ALLOWED • At egress ports of flows using classifier match all
• At egress port residing on an ASMi-54C/ETH module
when its ingress port classifier is different from match
vlan inner-vlan or match vlan
• When both ends of the flow reside on the same I/O
slot
• When both ends of the flow reside on GbE or LAG
ports defined on CL modules
573 Error VLAN ACTION MUST BE POP Pop action is obligatory in the following cases:
• Egress port is SVI bound to a bridge port
(management flow)
• Ingress port has inner VLAN as classifier (used only in
Logical macs defined on CL), and egress port is GBE or
LAG
• Ingress port has inner VLAN as classifier (match vlan
inner-vlan or match inner-vlan), and egress port is
defined on ASMi-54C/ETH module
If one of these cases is yours, define VLAN pop action.
574 Error VLAN ACTION MUST BE PUSH Push action is obligatory in the following cases:
• Ingress port is SVI bound to a bridge port
(management flow).
• I/O or CL Logical-mac classifier is ‘match all’ (push
VLAN must be added at the egress GBE/LAG port).
If one of these cases is yours, define VLAN push action.
575 Error CLASSIFIER/PUSHED Pay attention to one of the following:

VLAN/P-BIT MUST BE THE • All the flows where egress port is SVI bound to bridge
SAME port (management flow) must have the same VLAN
number in classifier
• All the flows where ingress port is SVI bound to bridge
port (management flow) must have the same push
vlan number and p-bit value.
• The VLAN number in classifier must be identical to the
push vlan number.
If the mentioned numbers/values are not the same,
correct according to the above.

576 Error MANAGEMENT FLOW MUST BE When a management flow is configured and SVI bound to
BI-DIRECTIONAL a bridge port is its egress port, another flow (with SVI
bound to the bridge port as ingress port) must be
configured and vice versa. In addition, this SVI cannot
participate in another flow.
577 Error VLAN CAN'T BE REPEATED BTW Pay attention to the following:
CL ETH/LAG PORTS • For non-management (data) flows the classifier profile
VLAN of each GbE/LAG port defined on CL module
must be unique. (Note: This is not relevant in case
when both flow ends reside on GbE/LAG ports defined
on CL module).
• For the flows with classifier based on outer&inner
VLAN, the inner VLAN can’t be repeated on GbE/LAG
ports defined on CL module
• Push SP-VLAN cannot be repeated on GbE/LAG ports
defined on the same CL module
If your case is different, correct according to the above.
578 Error FLOWS BETWEEN PORTS CAN’T If ingress port of several flows is the same I/O port, the
BE SPLIT egress ports of these flows cannot be different.
579 Error VLAN ID IS UNIQUE PER SLOT VLAN ID (number) must be unique per slot (except for the
management flows)
580 Error ONLY SINGLE FLOW IS If the classifier is 'match all', only a single flow is allowed
ALLOWED FOR MATCH ALL for the port.
581 Error CLASSIFIERS CONFLICT ON For any flow terminated on an ASMi-54C/ETH, the
SLOT classifier should be either ‘match all’ or ‘match vlan’ per
entire module
582 Error CLASSIFIERS CONFLICT ON All flows terminating on a specific port must use the same
PORT classifier criteria.
583 Error VLAN ID CAN’T BE REPEATED An ASMi-54C/ETH port classifier VLAN ID (number) is
PER SYSTEM unique per system (both at ingress and egress ports) and
cannot be repeated in other ASMi-54C/ETH ports.
584 Error NUMBER OF OUTER VLAN’S ON When the classifier on a GBE or LAG port is match vlan
PORT OUT OF RANGE inner-vlan, only up to 4 different VLANs (outer VLANs) can
be configured per port. In addition, the inner VLAN IDs
should be different from (outer) VLAN IDs.
585 Error FLOW CONNECTED TO PORT IN Flow can be connected to ports only in ‘no shutdown’
SHUTDOWN STATE state.
586 Error ILLEGAL FLOW WHEN PORT A local flow (a flow within the same module) cannot be
MEMBER IN MNG FLOW started/terminated on an SVI port bound to the
management router.
587 Warning SUM OF POLICERS RATE The total sum of bandwidths defined in policer profiles for
EXCEED SUPPORTED BW all 8 ports of the M-ETH module must not exceed 1 GbE.

588 Error INCORRECT POLICER The values of cbs/cir/ebr/eir parameters defined for
PARAMETERS bandwidth do not satisfy one of the conditions listed in
the configuration table under Configuring Policer Profiles.
589 Error ILLEGAL FLOW BETWEEN The following flows are iilegal:
GBE/LAG PORTS • Between two GbE ports (on CL module)
• Between two LAGs
• Between a LAG and a GbE port (on CL module)
590 Error VLAN 4000 IS ILLEGAL FOR Data flow VLAN ID cannot take the value of 4000
DATA PORTS
591 Error UP TO 512 FLOWS FOR DATA For CL.2/A the maximum number of unidirectional flows is
512.
592 Error FLOW EDITING NOT The editing is not according to allowed VLAN editing
SUPPORTED options as described in Table 8-2
593 Error ONE LEVEL 0 BLOCK ALLOWED The maximum number of level-0 queue blocks on a VCG
port is 1
594 Error UP TO 8 LEVEL 0 BLOCKS The maximum number of level-0 queue blocks on the GbE
ALLOWED port of CL module is 8
597 Error ERP VLAN AND CLASSIFIER The same VLAN cannot be defined for data and R-APS
CONFLICT messages.
598 Error FLOW CONNECTED TO AN The ingress or egress port of the flow do not exist
UNDEFINED PORT anymore (for example, the corresponding svi port was
deleted).
599 Error CLASSIFIER IS UNIQUE PER You cannot use the same classifier for two different flows
INGRESS SLOT/PORT on the same port.
8.6 Peer
Remote devices that serve as destinations for pseudowire traffic are referred to
as peers.
Factory Defaults
No peers exist by default.
Benefits
Peers serve as destinations for pseudowire connections for transporting a TDM
payload over packet-switched networks.
8-102 Peer Megaplex-4

Peers are remote devices operating opposite router interfaces. These devices
serve as destinations for pseudowire connections for transporting a TDM payload
over packet-switched networks. You can define up to 100 peers, each assigned a
unique index number. The index number is then used to specify the pseudowire
destination, instead of directly providing the necessary destination information.
To configure a UDP/IP peer, it is necessary to provide its IP address, and as an
option – the next hop IP address (if the peer IP address is not within a router
interface subnet).
For MEF-8 peers, you must specify the either an IP address or a MAC address of
the destination device.
When the MEF-8 peer is a MAC address, the central Megaplex device is configured
with a static MAC. In this case when the remote device fails needs to be replaced
with a different device (with different MAC), the peer must be reconfigured with
the new MAC to start working.
When the MEF-8 peer is an IP address, the MPW-1/VS module learns the remote
MAC by ARPs, and the remote device failure does not require reconfiguring the
peer.
Adding and Configuring Remote Peers

Peers are remote devices operating opposite router interfaces. These devices
serve as destinations for pseudowire connections for transporting a TDM payload
over packet-switched networks. You can define up to 100 peers.
 To add a remote peer:

• At the config>peer # prompt, type the peer number in the range of 1 to 100.
 To configure a remote peer:

• At the config>peer (peer number) # prompt, enter all necessary commands
Defining IP address of a remote ip <valid IP address>

peer in IP/UDP, MPLS or MEF-8
Ethernet networks
Assigning a name to a remote name <alphanumeric string >

peer
Megaplex-4 Peer 8-103

Specifying the IP address of the next-hop-ip <valid IP address> You need to specify a next hop
next port to which packets IP address only when the peer
directed to the selected peer will IP address is not within the IP
be sent subnet of the router interface
that will be used to send
packets to this peer.
The default value, 0.0.0.0,
means that no next hop IP
address is defined
Defining MAC address of a mac<valid MAC address>

remote peer in MEF-8 Ethernet
networks
 To remove a remote peer:

• At the config>peer (peer number) # prompt, type no peer (peer number).
Note Setting remote peers as destinations is done under configure pwe context.
 To display the remote peer table:

• At the config# prompt, type info and scroll to the corresponding section.
mp4100>config# info
peer 1 ip 6.6.6.7 next-hop-ip 0.0.0.0
peer 2 ip 172.17.153.191 name "peer_2" next-hop-ip 172.18.170.1
peer 3 ip 172.17.154.192 name "peer_3" next-hop-ip 172.18.170.1
Examples
 To configure remote peer 1 for UDP/IP PSN:
• IP address: 9.9.9.9
• Next hop IP address: 0.0.0.0
• Name: peer1.
mp4100>configure peer 1 ip 9.9.9.9 name peer1 next-hop-ip 0.0.0.0
 To configure remote MAC peer 1 for MEF-8 PSN:

• MAC address: 00-20-d6-54-bf-05
• Name: peer2.
mp4100>configure peer 1 mac 00-20-d6-54-bf-05 name peer2
 To configure remote IP peer 1 for MEF-8 PSN:

• IP address: 9.9.9.9
• Name: peer2.
mp4100>configure peer 1 ip 9.9.9.9 name peer2
 To delete remote peer 1:
8-104 Peer Megaplex-4

mp4100>config# no peer 1
See Table 8-18.
8.7 Pseudowires
Pseudowires are an emulation of Layer-2 point-to-point connection-oriented
services over packet-switching networks (PSN). In Megaplex-4, they are available
for MPW-1, VS, SH-16/E1/PW and TP modules.
Packet formats can be selected on a per-pseudowire basis for optimal
transmission over UDP/IP, MPLS- or Ethernet-based networks. Each pseudowire
can be independently routed to any destination.
The following user-configurable protocols are supported, independently for each
pseudowire:
• TDMoIP (TDM over IP) in accordance with RFC5087, and TDMoMPLS in
accordance with RFC5087 and ITU-T Rec. Y.1413 (the term TDMoPSN is used
when information is applicable to both protocols)
• HDLCoPSN (HDLC over PSN) in accordance with RFC5087 and RFC4618
(except Clause 5.3 – PPP)
• CESoPSN (structure-aware TDM circuit emulation over PSN) in accordance
with RFC5086.
• SAToPSN (structure-agnostic TDM over PSN) in accordance with RFC4553.
The maximum number of PW (connection) configurations that may be stored in
the Megaplex-4 is 640, where each pseudowire is assigned a unique index
number in the range of 1 to 640. The actual maximum number, however,
depends on the number and type of modules installed in the chassis.
Standards
The MPW-1 PW ports provide pseudowire emulation services over
packet-switched networks using the following user-configurable protocols:
• TDMoIP (TDM over IP) in accordance with RFC5087, and TDMoMPLS in
accordance with RFC5087 and ITU-T Rec. Y.1413
• HDLCoPSN (HDLC over PSN) in accordance with RFC5087 and RFC4618
(except Clause 5.3 – PPP)
• CESoPSN (structure-aware TDM circuit emulation over PSN) in accordance
with RFC5086
• SAToPSN (structure-agnostic TDM over PSN) in accordance with RFC4553.
For protocols supported by different Megaplex-4 modules, see Table 8-13.
Megaplex-4 Pseudowires 8-105

In addition, MPW-1, SH-16 and some of the VS modules meet the requirements
for edge-to-edge simulation of TDM circuits over PSN in accordance with
RFC4197, including high-performance adaptive timing recovery capabilities.
Benefits
Pseudowire circuit emulation technology enables packet-based infrastructure to
provide TDM services with the service quality of an SDH/SONET network.
The pseudowire services convert TDM payload to packets and transfer these
packets through Layer-2 or Layer-3 (router) services.
The pseudowire subsystem is located on the MPW-1, VS and TP modules.
The MPW-1 module has 8 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).
SH-16/E1/PW, VS-16E1T1/PW and VS-6/E1T1 modules have 16 independently-
configurable internal DS1 ports.
Other VS modules have 12 independently-configurable internal DS1 ports.
The TP modules have 4 independently-configurable internal DS1 ports.
Any PW-equipped module can serve as PW server for other modules, not
equipped with PW.
The traffic to the internal DS1 ports is directed by means of a pseudowire
cross-connect matrix (a timeslot cross-connect matrix similar to the TDM
cross-connect matrix), which routes traffic from the internal DS1 ports to the
pseudowire packet processors.
Multiple MPW-1, VS, SH-16 and TP modules can be installed in the Megaplex-4
chassis, in accordance with the required pseudowire transport capacity.
Note For additional information on the Megaplex-4 pseudowire system, see also the
following sections:
• Router (Pseudowire)
• Internal DS1 Ports (in Chapter 6)
• PW-TDM Cross-Connect (in this Chapter)
• Fault Propagation (in Chapter 7)
• MPW-1 Modules, SH-16 Modules, VS Modules and Teleprotection Modules in
Megaplex-4 I/O Modules Installation and Operation Manual).
Pseudowire Packet Processing Subsystem

The packet processors in the MPW-1/VS/TP packet processing subsystem perform
the functions necessary for converting TDM traffic directed to the MPW-1 internal
DS1 ports into packetized traffic for transmission over pseudowires.
8-106 Pseudowires Megaplex-4

The maximum number of pseudowires that can be processed for each DS1 port,
provided the port uses the DS0 cross-connect mode, is 16 (only one pseudowire
is supported when the port uses the TDM cross-connect mode).
A pseudowire can process traffic from only one internal DS1 port.
The basic format of a TDM-PW packet is illustrated below:
Ethernet Header
PSN and Multiplexing Layer Headers
Control Word
Packetized TDM Data (Payload)
Ethernet Header
The Ethernet header contains the DA, SA and Ethernet type information. It may
also contain an optional VLAN tag.
UDP over IP
For UDP/IP-type PSN, the Ethernet header is as follows:
• SA MAC – MAC address of the router interface used for packet forwarding
• DA MAC – MAC address of the resolved next hop, default gateway or host
• VLAN –VLAN assigned to the router interface used for packet forwarding
• P-bit – CoS of PW is set to 1. P-bit is a RIF attribute (CoS > P-bit).
MEF-8
For the MEF-type PSN, the Ethernet header is as follows:
• SA MAC – MAC address of the MPW-1 card
• DA MAC – MAC address of the peer
• VLAN – Flow (E-Line/E-LAN) VLAN
• P-bit – CoS of PW is set to 1. P-bit is a flow attribute (marking profile, CoS >
P-bit)
• Packet color – green.
PSN and Multiplexing Layer Headers

Each pseudowire has a header whose structure depends on the selected PSN
type, and includes labels that specify the uniquely specify the pseudowire source
and destination.
Notes • Different source and destination labels can be used. In this case, it is
necessary to ensure that the source (inbound) label selected at one
pseudowire endpoint is configured as the destination (outbound) label at the
other pseudowire endpoint, and vice versa.
• The inbound Input PW label must be unique.

Megaplex-4 supports the following PSN types:

• UDP over IP
• MPLS
• Ethernet (MEF-8).
UDP over IP
For UDP/IP-type PSN, the TDM-PW packet structure is as follows:
6 6 2 2 2 20 8 4
Type VLAN Type UDP
DA SA IP Header CW TDM Payload
8100 Tag 800 Header
Where:
• DA – MAC address of the next hop (taken from the forwarding table)
• SA – MAC address of the applicable router interface
• VLAN type 0x8100 + VLAN tag, optional
• Type – 0x800 (IP packet)
• IPv4 Header – the protocol field of the IP header is set to 17 (UDP)
• UDP Header – the PW label/s, manually configured (see below)
For UDP/IP-type PSN IP, the TOS byte in the IP header can be configured per PW.
The UDP header is used to multiplex between the different PWs. UDP port values
are as follows:
• For TDMoIP (CE) bundles using packet payload Version V1:
 During normal operation, the source UDP port is given by:
UDP Source Port = 1 + Destination PW Number.
This means that during normal operation, the UDP ports numbers are in
the range of 0 to 8191 decimal.
 While the pseudowire is in the local fail state, the source UDP port
changes to:
UDP Source Port = 8000 + Destination PW Number.
This means that in the local fail state, the UDP ports numbers are higher
than 8000 hexa (32768 decimal).
• For TDMoIP (CE) bundles using packet payload Version V2:
UDP Source Port = 2000 + Destination PW Number
This means that all the UDP ports numbers are higher than 2000 hexa (8192
decimal).
• For CESoPSN and SAToPSN bundles using packet payload Version V2:
UDP Source Port = C000 + Destination PW Number.
This means that all the UDP ports numbers are higher than C000 hexa (49152
decimal).
MEF-8
For MEF-8-type PSN, the TDM-PW packet structure is as follows:

6 6 2 2 2 4 4
Type VLAN Type
DA SA ECID CW TDM Payload
8100 Tag 88D8
Where:
• DA – MAC address of the peer device
• SA – MAC address of the associated SVI (per E5-cTDM-4 card)
• VLAN type 0x8100 + VLAN tag, optional
• Type – 0x88D8 (CESoETH packet)
• ECID – Emulated Circuit Identifier, a manually configured unique label which
identifies the PW.
Control Word
The control word structure is illustrated below.
0 1 2 3 4 5 6 7 8 9 10 15 16 31
0 0 0 0 L R M/RSV FRG LEN (6) Sequence Number (16)
Bits 0-3 – Set to zero.

L – local attachment circuit abnormal condition. If set, indicates that the source
has detected or has been notified of a TDM fault condition that is affecting the
data to be transmitted. If the TDM fault is cleared, the L bit is also cleared.
R – remote loss of frame. If set, indicates that packet loss or buffer underflow
condition is detected at the PSN.
M/RSV – a 2-bit modifier field in TDMoIP and CESoPSN. If L=0, it allows detection
of signaling packets, carrying RDI across the PSN. If L=1, only value ‘00’ for M bits
is currently defined. In SAToP it is reserved and must be set to 0.
L & M can be treated as a 3-bit code point that is described in the table below.
Table 8-12. L & M Code Point Interpretations
L M Code Point Interpretation
0 00 Normal situation, no failure
0 01 Reserved
0 10 RDI condition of the attachment circuit (TDM link). The payload is

received, and upon configuration RDI can be generated on the
outgoing TDM trunk.
0 11 Reserved for CESoPSN signaling packets.
1 00 TDM data is invalid. The payload is replaced by an “Idle” bit

pattern towards the TDM trunk. Additionally, it can be pro
configured to generate an AIS pattern or “Channel Idle” signal
towards the local CE on the TDM trunk.
1 01 Reserved
1 10 Reserved

L M Code Point Interpretation
1 11 Reserved
FRG – fragmentation field. This field is used for fragmenting multiframe

structures into multiple packets in case of structured CESoPSN with CAS bundles.
Must be set to zero.
LEN – the length of the TDM-PW packet (header + payload) if it is less than 64
bytes. Otherwise, it is set to zero.
Sequence Number – provides the common PW sequencing function as well as
detection of lost packets. Its generation rules:
• Its space is a 16-bit unsigned circular number
• Its initial value is random (unpredictable)
• It is incremented with each TDM-PW data packet sent in the specific PW.
TDM Payload
The table below lists the TDM payload encapsulation methods supported by
different I/O modules. It also indicates whether these modules support adaptive
timing. Each payload encapsulation method can be independently selected for
each pseudowire.
Table 8-13. Features Supported by PW-Equipped I/O Modules
I/O Module Payload Encapsulation Methods Adaptive

Timing
MPW-1 ces-psn-data, e1satop, t1satop, tdmoip-v1, tdmoip- Yes

v2, hdlc
TP, VS-12, VS-6/C37, ces-psn-data No

VS-6/BIN, VS Voice
SH-16/E1/PW ces-psn-data, e1satop Yes
VS-16E1T1/PW ces-psn-data, e1satop, t1satop Yes

VS-6/8E1T1/PW
TDMoPSN
The main functions performed by the packet processor when using the TDMoPSN
mode are as follows:
• In the transmit-to-network direction:
 Processes the data stream received through the internal DS1 port to
generate pseudowires, as specified by the user. When using a framed
mode, the user can specify the timeslots to be transported end-to-end.
To prepare a pseudowire, the packet processor extracts segments from
the continuous data stream for insertion into the pseudowire payload
section.
The size of the pseudowire payload section is specified by the user
(n × 48 bytes, where n is 1 to 30):

 When operating in a framed mode, the slices are formed by

collecting the appropriate timeslots from consecutive frames until
the TDM payload section of the packet is filled. Timeslot 0 is never
included; timeslot 16 is processed in accordance with the signaling
mode.
 When operating in the unframed mode, the slices are formed by
collecting consecutive bytes from the received DS1 stream until the
TDM payload section of the packet is filled.
 Adds the overhead necessary to transmit each slice over the packet
switched network, and builds TDMoIP, respectively TDMoMPLS, packets
for transmission to the desired destination. The resulting packets are
encapsulated as TDMoPSN over Ethernet, and then sent to the Ethernet
switching subsystem of the module.
 When signaling transport is enabled and the pseudowire timeslots are
defined as voice timeslots, the signaling information associated with the
timeslots transported by the pseudowire is also inserted in the packet.
• In the receive-from-network direction:
 The TDMoPSN packets retrieved from the received Ethernet frames are
stored in a packet buffer. Each pseudowire has its own buffer.
The function of this buffer is to enable the packet processor to read the
received packets at the rate of the original data stream of each
pseudowire, and thus eliminate jitter in their arrival times. Therefore, this
buffer is called jitter buffer.
 The packet processor recovers the payload carried by the packets and
restores the original data stream of the pseudowire, in accordance with
the selected framing mode.
When the pseudowire carries only selected timeslots, the payload is
reinserted in the appropriate timeslots. Therefore, when several
pseudowires carry payloads destined to the same internal DS1 port, all
the useful payload is reinserted in the original timeslots, and only the
remaining empty timeslots in the internal port frame are filled with a
user-selectable idle code.
In a similar way, the signaling information related to the voice timeslots
transported by each pseudowire is reinserted in the positions
corresponding to the pseudowire timeslots.
Since the TDMoPSN packet structure for framed ports does not depend
on the port frame structure, a pseudowire carrying traffic from an E1 port
can be directed to a T1 port at the far end, as long as the total number
of timeslots does not exceed 24, and the payload type is data (signaling
cannot be transferred between E1 and T1 ports).
HDLCoPSN
HDLCoPSN packet processing is similar to the processing of TDMoPSN packets
described above, except that the HDLCoPSN protocol is intended to provide
port-to-port transport of HDLC-encapsulated traffic, in accordance with RFC4618,
for example, Frame Relay or CCS protocols.

For framed ports, the HDLC traffic is carried in specific timeslots (these timeslots
are specified during the configuration of a HDLCoPSN pseudowire and are always
considered data timeslots).
Note For HDLCoPSN, it is not necessary to configure the same number of timeslots at
the pseudowire end points. The pseudowire bandwidth will be determined by the
endpoint with the smaller number of assigned timeslots.
The HDLCoPSN protocol can also handle whole (unframed) E1 streams.

When assembling packets for a HDLC pseudowire, HDLC idle flags are removed,
and only the contents of HDLC packets with useful payload are inserted in
packets. This results in better bandwidth utilization efficiency. At the receive end,
HDLC packet structure is restored and inserted in the restored port data stream.
Therefore, HDLC pseudowires can connect only ports with the same framing
mode.
SAToPSN
SAToPSN is different from the TDMoPSN and HDLCoPSN protocols, in that it is
used to transfer transparently a bit stream at the nominal port rate
(2.048 Mbps). Therefore, SAToPSN can be used only when the port uses the
unframed mode, and thus only one pseudowire can be configured per port.
SAToPSN packet payload consists of a user-specified number of raw TDM bytes
(MPW-1: 4 to 1440 bytes, SH-16/E1/PW, VS-16E1T1-PW and VS-6/E1T1: 32 to
1440 bytes), and is treated as data payload.
Note The SAToPSN packet overhead is large, and therefore, for efficient bandwidth
utilization, the number of raw TDM bytes per packet should be as large as
possible.
The receiving end restores the original bit stream, and therefore a SAToPSN
pseudowire can only be directed to another unframed E1 port, or to an
n×64 kbps protocol (where n must be 32, that is, to a high-speed serial port
operating at a rate of 2048 kbps).
CESoPSN
CESoPSN transports raw TDM data, that is, packets are formed by inserting a
user-specified number of complete TDM frames in the packet payload area.
CESoPSN pseudowires can only be configured on framed ports.
The TDM frames are considered as serial data, even if they carry voice and CAS.
Since a CESoPSN pseudowire transports raw TDM frames, a CESoPSN pseudowire
can only be directed to another E1 framed port.
PSN Configuration Parameters

Each pseudowire is handled in accordance with the user-configured PSN
parameters, considering the user-selected pseudowire parameters, and the
framing and signaling mode of the associated internal DS1 port.
Megaplex-4 enables the user to select the PSN type (UDP/IP, MPLS or Ethernet),
and configure the PSN transport parameters.

The PSN parameters, which are reflected in the pseudowire header structure,
enable specifying the requested priority or quality of service for pseudowire
traffic generated by the MPW-1/VS/TP module. The applicable parameters depend
on PSN type:
• When the PSN is based on Layer 2 forwarding, the user can specify the VLAN
priority (per IEEE 802.1p) for the Ethernet frames carrying pseudowire
packets. The priority is always selectable for traffic forwarded through the
Megaplex-4 GbE ports, because for these ports VLAN tagging is always
enabled; when using other bridge ports as pseudowire exit ports, it is
necessary to enable VLAN tagging in order to request a specific priority.
• When the PSN uses IP routing, the user can specify the Type of Service (ToS)
per RFC791; if the PSN supports RFC2474, ToS is interpreted as a DiffServ
codepoint per RFC2474.
• When the PSN uses MPLS, the user can specify the EXP bits. In addition, the
user can also add ingress and egress tunnel labels, which enable network
operators to plan preferential forwarding of pseudowire traffic using the
specified tunnel labels.
Another parameter that may be used, for compatibility with older TDMoIP
implementations, is the packet payload version, V1 or V2.
Pseudowire QoS/CoS
To enable optimal handling of pseudowire traffic within the PSN, the following
parameters can be configured:
• For Ethernet transport networks: outgoing pseudowire packets are assigned
to a dedicated VLAN ID according to 802.1Q and marked for priority using
802.1p bits.
• For IP transport networks: outgoing pseudowire packets are marked for
priority using DSCP or ToS bits. This allows TDMoIP packets to be given the
highest priority in IP networks.
• For MPLS transport networks: outgoing pseudowire packets are assigned to a
specific MPLS tunnel, and marked for priority using the EXP bits.
The proper balance between the PSN throughput and delay is achieved via
configurable packet size. A jitter buffer with selectable size compensates for
packet delay variation (jitter) of up to 200 msec in the network.
ToS
The ToS specifies the Layer 3 priority assigned to the traffic generated by this
pseudowire.
For IP networks, this priority is indicated by the IP type-of-service parameter for
this pseudowire. The specified value is inserted in the IP TOS field of the
pseudowire IP packets.
When supported by an IP network, the type-of-service parameter is interpreted,
in accordance with RFC791 or RFC2474, as a set of qualitative parameters for the
precedence, delay, throughput and delivery reliability to be provided to the IP
traffic generated by this pseudowire.

These qualitative parameters may be used by each network that transfers the
pseudowire IP traffic to select specific values for the actual service parameters of
the network, to achieve the desired quality of service.
You can also specify a Layer 2 priority by means of the vlan priority command.
Jitter Buffer
The packets of each pseudowire are transmitted by PW-equipped modules at
essentially fixed intervals towards the PSN. The packets are transported by the
PSN and arrive to the far end after some delay. Ideally, the PSN transport delay
should be constant: in this case, the packets arrive at regular intervals (these
intervals are equal to the intervals at which they had been transmitted).
However, in reality packets arrive at irregular intervals, because of variations in
the network transmission delay. The term Packet Delay Variation (PDV) is used to
designate the maximum expected deviation from the nominal arrival time of the
packets at the far end device.
Note
The deviations from the nominal transmission delay experienced by packets are
referred to as jitter, and the PDV is equal to the expected peak value of the jitter.
Note however that nothing prevents the actual delay from exceeding the selected
PDV value.
To compensate for deviations from the expected packet arrival time, the module
uses jitter buffers that temporarily store the packets arriving from the PSN (that
is, from the far end equipment) before being transmitted to the local TDM
equipment, to ensure that the TDM traffic is sent to the TDM side at a constant
rate.
For each pseudowire, the jitter buffer must be configured to compensate for the
jitter level expected to be introduced by the PSN, that is, the jitter buffer size
determines the Packet Delay Variation Tolerance (PDVT).
Two conflicting requirements apply:
• Since packets arriving from the PSN are first stored in the jitter buffer before
being transmitted to the TDM side, TDM traffic suffers an additional delay.
The added delay time is equal to the jitter buffer size configured by the user.
• The jitter buffer is filled by the incoming packets and emptied out to fill the
TDM stream. If the PSN jitter exceeds the configured jitter buffer size,
underflow/overflow conditions occur, resulting in errors at the TDM side:
 A jitter buffer overrun occurs when it receives a burst of packets that
exceeds the configured jitter buffer size + packetization delay. When an
overrun is detected, the module clears the jitter buffer, causing an
underrun.
 A jitter buffer underrun occurs when no packets are received for more
than the configured jitter buffer size, or immediately after an overrun.
When the first packet is received, or immediately after an underrun, the buffer is
automatically filled with a conditioning pattern up to the PDVT level in order to
compensate for the underrun. Then, the module starts processing the packets
and empty out the jitter buffer toward the TDM side.
To minimize the possibility of buffer overflow/underflow events, two conditions
must be fulfilled:

• The buffer must have sufficient capacity. For this purpose, the buffer size can
be selected by the user in accordance with the expected jitter characteristics,
separately for each pseudowire.
• The read-out rate must be equal to the average rate at which frames are
received from the network. For this purpose, the read-out rate must be
continuously adapted to the packet rate, a function performed by the
adaptive clock recovery mechanism of each packet processor.
Adaptive Timing
MPW-1 modules have independent adaptive clock recovery mechanisms for each
pseudowire, which recover the original timing (clock rate) of the far-end source
of each pseudowire. The clock recovery mechanisms can provide recovered clock
signals to serve as timing references for the Megaplex-4 nodal timing subsystem.
The receive path of each pseudowire must use a clock recovery mechanism to
recover a clock signal at the original payload transmit rate used at the far end.
This mechanism is referred to as adaptive clock recovery mechanism.
Each pseudowire has its own adaptive timing recovery mechanism, in accordance
with the options listed in RFC4197. The recovered pseudowire clocks can be used
as timing reference signals for the nodal Megaplex-4 timing subsystem, and
therefore MPW-1 allows flexible timing distribution.
The adaptive clock recovery mechanism estimates the average rate of the
payload data received in the frames arriving from the packet-switched network.
Assuming that the packet-switched network does not lose data, the average rate
at which payload arrives will be equal to the rate at which payload is transmitted
by the source.
Note
Generally, lost packets, as well as packets that did not arrive in the correct order,
are replaced by special dummy packets. However, for CESoPSN and SAToPSN,
packets can be reordered.
The method used to recover the payload clock of a pseudowire is based on

monitoring the fill level of the selected pseudowire jitter buffer: the clock
recovery mechanism monitors the buffer fill level, and generates a read-out clock
signal with adjustable frequency. The frequency of this clock signal is adjusted so
as to read frames out of the buffer at a rate that keeps the jitter buffer as near
as possible to the half-full mark. This condition can be maintained only when the
rate at which frames are loaded into the buffer is equal to the rate at which
frames are removed. Therefore, the adaptive clock recovery mechanism actually
recovers the original payload transmit clock.
The performance of the clock recovery mechanism can be optimized for the
operating environment, by specifying the following parameters:
• The accuracy of the original timing source, in accordance with the standard
SDH/SONET terminology (Stratum 1, 2, 3, 3E, or 4/unknown)
• The type of PSN that transports the traffic: router-based network (for
example, UDP/IP) versus switch-based network (for example, MPLS/Ethernet).
• Handling of transient conditions: even after the adaptive clock recovery
mechanism reaches a stable state, there may still be temporary changes in
the network delay, which may occur on a timescale that does not allow for

the mechanism to fully readjust. To provide the best possible user experience,
the user can specify how to handle such transient conditions (a capability
referred to as delay sensitivity):
 By disabling delay sensitivity, performance is optimized for accurate clock
recovery. This selection is optimal for data transmission applications.
 By enabling delay sensitivity, performance is optimized for constant delay.
This selection is optimal for voice transmission applications.
You can select a total of 10 pseudowire recovered clocks per Megaplex-4.
For HDLCoPSN pseudowires, it is not necessary to restore the original data rate,
because only useful HDLC payload (extracted from some of the HDLC frames
reaching each endpoint) is transferred through the pseudowire, as explained in
the HDLCoPSN section. Therefore, the payload, which requires only a fraction of
the available bandwidth, can be reinserted in timeslots at the receiving endpoint
rate, without requiring any clock adaptation mechanism.
VS-16E1T1-PW, VS-6/E1T1, SH-16/E1/PW and MPW-1 modules have the full
support of adaptive timing.
Adaptive timing is not supported by other PW-equipped modules.
OAM Protocol
The RAD proprietary implementation of the OAM connectivity protocol enables
detecting loss of communication with the pseudowire destination and taking
steps that prevent the resulting flooding. The protocol also enables checking that
the destination uses a compatible configuration.
The OAM protocol is supported only by packet payload version V2 and not
supported for MEF-8 encapsulation.
The OAM protocol is used to check for a valid pseudowire connection: this
includes checks for compatible configuration parameters at the packet processors
at the two endpoints of a pseudowire, and detection of inactive pseudowire
status.
The information regarding the pseudowire state is collected by the continuous,
periodic handshake between the two endpoints of a pseudowire, which
generates little traffic, but ensures that each endpoint recognizes the
connection, and that it is enabled. In case no response is received to OAM
packets within a predefined interval (a few tens of seconds), the pseudowire is
declared inactive.
When the use of the OAM protocol is enabled, little traffic flows until the
connection between the two pseudowire endpoints is established: only after the
connection is confirmed by the OAM exchange is transmission at the normal (full)
rate started, and the pseudowire starts carrying traffic. In case the connection is
lost, the transmitted traffic is again significantly decreased (several packets per
second per connection).
The OAM connectivity check also prevents network flooding in case the
connection is lost.
OAM packets sent by MPW-1 modules are identified in accordance with the
source port: the OAM packets run over a UDP port number (see the Determining

UDP Port Numbers Used by Pseudowires section) that is assigned only to OAM
traffic, but use the VLAN ID and ToS of the originating connection.
Factory Defaults
By default, no pseudowires are configured: you must define your own in
accordance with your application requirements. Other parameter defaults are
psn udp-over-ip
type MPW-1 module: tdmoip-v2

VS modules: ces-psn-data
exp-bits 0
tos 0
tunnel-index 0 (for ingress and egress)
Jitter-buffer [sec} 2500
tdm-payload 4
sensitivity disabled
oam disabled
vlan priority 0
label For udp-over-ip and ethernet: same as the

PW index number
For mpls: PW index number + 15
udp-mux-method src-port
oos parameters:
far-end-type e1
signaling force-idle
data 00
voice 00
Configuring Pseudowires
New pseudowire bundles are added by defining their number (1–640), type
(connection mode) and a PSN type.
 To define and configure a pseudowire:

1. If you intend to use UDP/IP PSN type, verify that the router interface with
valid IP address has been configured (see Router (Pseudowire) ).
2. At the config>pwe# prompt, enter the syntax illustrated in the table below.

The config>pwe>pw(<pw-number>)# prompt appears.
Note An internal DS1 port becomes active only if at least one enabled pseudowire with
a valid cross-connection is assigned to the port.
Assigning the pw <pw-number> [type {ces- PW number: 1..640

pseudowire number, psn-data | e1satop | PW type (must be configured for the first time):
selecting the t1satop | hdlc | tdmoip-v1 |
• hdlc: carrying HDLC traffic using the HDLCoPSN
encapsulation protocol tdmoip-v2]
protocol (supported only by MPW-1)
for the selected [psn { ethernet | mpls | udp-
pseudowire and over-ip}] • tdmoip-v1: TDMoPSN circuit emulation for
specifying the PSN carrying data and voice timeslots, old packet
type (selecting the payload format, can only be used for TDMoIP CE
type of PSN header) pseudowires (for example, when working with
MP-2100 ML-IP module and old IPmux devices).
This version requires two UDP sockets per
pseudowire (supported only by MPW-1)
• tdmoip-v2: TDMoPSN circuit emulation for
carrying data and voice timeslots, current packet
payload format. This version requires a single
UDP socket per pseudowire (supported only by
MPW-1)
• e1satop: SAToPSN protocol, for carrying
unframed E1 data streams
• t1satop: SAToPSN protocol, for carrying
unframed T1 data streams
• ces-psn-data: CESoPSN protocol, for carrying
framed data streams
To check PW types supported by different PW
modules, see Table 8-13.
psn (must be configured for the first time):
• udp-over-ip – UDP over IP network
encapsulation
• mpls –MPLS over Ethernet network
encapsulation with standard packet structure
(supported only by MPW-1). In this case, only
TDMoIP Version V2 is used.
• ethernet – MEF-8 Ethernet network
encapsulation
Using no before pw <number> deletes the
pseudowire
3. At the config>pwe>pw(<pw-number>)# prompt, enter the parameters

specified in the table below.
Assigning a name to the name <up to 32

pseudowire characters>

Specifying the PW label used label [in <number>] Out PW label:

in the inbound and [out < number>] • For udp-over-ip: Specifies the UDP source port
outbound directions number used by the pseudowire
• For mpls: Specifies the outer (tunnel) MPLS label
used by the pseudowire.
• For ethernet: Specifies the Emulated Circuit ID
(ECID) for Tx PW packets
In PW label:
• For udp-over-ip: Specifies the UDP source port
number used by the pseudowire for the Tx PW
packets (destination port for Rx PW packets)
• For mpls: Specifies the inbound MPLS label used
by the pseudowire
• For ethernet: Specifies the expected Emulated
Circuit ID (ECID) Rx PW packets
Each PW must have a unique in (source) label.
Do not reuse the same out (destination) value on
bundles terminating at the same peer, and/or using
the same VLAN ID (when VLAN tagging is enabled).
For udp-over-ip and ethernet, the allowed range is 1
to 8191.
For mpls, the allowed range is 16 to 1048575.

Specifying the type of far-end-type {e1 | t1- e1 – E1 stream with G.704 framing. The PCM signals
framing used by the esf | t1-sf | unframed | are processed assuming that they are encoded in
equipment at the fxs-e1 | fxs-t1} accordance with the A-law. You can use this
destination endpoint. The selection when the port line-type is a framed
selected value also version.
determines the encoding t1-esf – T1 stream with ESF framing. The PCM signals
law used on PCM voice are processed assuming that they are encoded in
channels accordance with the µ-law. You can use this
selection when the port line-type is a framed
version.
t1-sf – T1 stream with SF (D4) framing. The PCM
signals are processed assuming that they are
encoded in accordance with the µ-law. You can use
this selection when the port line-type is a framed
version.
fxs-e1 – E1 stream with G.704 framing, used when
Megaplex-4 is working opposite IPmux-1E. The PCM
encoded in accordance with the A-law. You can use
version. In addition, the option supports cadence
(for more details, refer to RAD Technical Support
Dept).
fxs-t1 – T1 stream with ESF framing, used when
Megaplex-4 is working opposite IPmux-1E. The PCM
encoded in accordance with the µ-law. You can use
version. In addition, the option supports cadence
(for more details, refer to RAD Technical Support
Dept).
unframed – unframed data stream, transparently
transferred. You can use this selection when the
port line-type is unframed.
This is the only selection for SAToPSN pseudowires.
For CESoPSN pseudowires it is not allowed.
For the PWs on the same module, make sure to
select the same value at both end points.
The selected value must also match the line-type
configured for the physical port of the pseudowire
local endpoint
This parameter is not relevant for HDLCoPSN
pseudowires

Optimizing the clock sensitivity Use no sensitivity to optimize the clock mechanism
recovery mechanism of the for accurate clock recovery. This selection is optimal
selected pseudowire for for data transmission applications.
constant delay. This This parameter is relevant only for MPW-1 modules
selection is optimal for voice and not relevant for HDLCoPSN pseudowires.
transmission applications
Transmitting an tdm-oos [voice <00 to tdm-oos voice and data are hexadecimal numbers in
out-of-service signal (OOS) FF (hexa)>] [data <00 the range of 00 to FF (two digits).
on PW failure and selecting to FF (hexa)>] The selected code for data is also sent during
the code transmitted by the [signaling {force-idle | out-of-service periods instead of the external data
port during out-of-service force-busy} ] stream when the unframed mode is used
periods on the timeslots
The voice OOS parameter is not relevant for the
defined as data and voice
following cases:
timeslots.
• HDLCoPSN pseudowires in MPW-1 module
• when the MPW-1 DS1 port uses the unframed
mode.
signaling (MPW-1 only) – Determines the state of
the signaling bits sent to the internal DS1 port
connected to the selected pseudowire during
out-of-service periods (relevant only when the
attached internal DS1 port is configured with
signaling enabled):
• force-idle – The signaling bits are forced to the
idle state (05 hexa) during out-of-service periods.
• force-busy – The signaling bits are forced to the
busy state (0F hexa) during out-of-service
periods.
Defining the jitter buffer jitter-buffer <value in Use the shortest feasible buffer, to minimize
size in msec µsec> connection latency
For MPW-1 module the allowed range depends on
the framing mode:
• framed: 2500 to 200000 µsec, in 1-µsec steps.
• unframed: 500 to 200000 µsec, in 1-µsec steps.
For SH-16/E1/PW, VS-16E1T1/PW and VS-6/E1T1
modules: 250 µsec to 256000 µsec, in 1-µsec steps
(the value entered by the user is rounded upward to
the closest n*125 µsec value).
For other VS and TP modules: 250 µsec to
8000 µsec, in 1-µsec steps (the value entered by the
user is rounded upward to the closest n*125 µsec
value).
pseudowires

Enabling/disabling the OAM oam The selection must be compatible with the
connectivity protocol for this equipment at the far end of the connection.
PW For pseudowires defined on redundant internal DS1
ports, make sure to select the same OAM mode.
Using no oam disables the OAM protocol.
This feature is supported in MPW-1 only and is not
available for MEF-8 Ethernet encapsulation.
OAM packets sent by MPW-1 modules are identified
in accordance with the source port: the OAM packets
run over a UDP port number (see the Determining
UDP Port Numbers Used by Pseudowires section)
that is assigned only to OAM traffic, but use the
VLAN ID and ToS of the originating connection.
Defining a remote peer peer <1–640> 1 to 640

terminating this PW Using no peer removes the remote peer
Specifying the number of tdm-payload <1–360> A larger value decreases the bandwidth utilization
TDM payload bytes to be efficiency, but also increases the connection intrinsic
inserted in each packet latency.
For MPW-1 selection consideration, refer to the
Selection Guidelines for TDM Payload Bytes per
Frame section in Megaplex-4 I/O Modules Installation
The number is specified as a multiple of 48 bytes, for
example, 1 means 48 bytes, and 30 means 1440
bytes.
The available selections for TDMoIP are 1 to 30 (48
to 1440 bytes, respectively).
The values for CESoPSN are:
• For MPW-1 module: 4 to 360.
• For VS-16E1T1-PW and VS-6/E1T1 and SH-
16/E1/PW modules: 1 to 61.
• For other VS and TP modules: 1 to 64.
In the case of voice with signaling transferred by the
MPW-1 module with CESoPSN protocol, the following
restrictions apply depending on the far-end-type.
far-end-type=e1: tdm-payload value must be 16.
far-end-type=t1-esf, t1-sf: tdm-payload value must
be 24.
The values for SAToPSN are:
• For MPW-1 module: 4 to 1140
• For VS-16E1T1-PW and VS-6/E1T1 and SH-
16/E1/PW modules: 32 to 1440.
pseudowires.

Specifying the value for the tos <tos number> This parameter is relevant only when psn is
TOS byte used on outbound udp-over-ip.
traffic Range: from 0 to 255.
In accordance with RFC 2474, it is recommended to
use only values which are multiples of 4.
Eabling and configuring vlan [priority <0..7>] VLAN priority: The allowed range in accordance with
VLAN tagging and priority on IEEE 802.1p is 7 (highest priority) to 0 (lowest
every transmitted packet priority).
Note: If the traffic on the specific PW must be
assigned priority, the priority parameter must be
configured in this context (not as part of flow
configuration) and then mapped via queue-map-
profile configuration (see Queue Mapping Profiles).
Specifying the value of the exp-bits <exp-bit The allowed range is 7 (highest priority) to 0 (lowest
outbound EXP bits that number> priority).
indicate the requested Applies only to MPLS PSN.
quality of service in the
MPLS header of the
pseudowire
Enabling and specifying the tunnel-index [ingress Relevant for MPLS PSN only
ingress and egress MLPS <ingress-label>] If an ingress label is configured, the egress label
tunnel indices [egress <egress- must be configured as well, and vice versa.
label>]
The supported range is 16 to 1048575.
Adding no before the command removes the labels
Assigning egress port for L2 egress-port svi This parameter is relevant only when psn is ethernet
forwarding <svi_number>
Specifying the UDP port udp-mux-method This parameter is relevant only when psn is
multiplexing method {dst-port | src-port } udp-over-ip.
dst-port:
UDP destination port = 0xC000 + <out-PW-label>
UDP source port is 0xC000 + <in-PW-label>
This selection is not supported for MPW-1.
src-port:
UDP destination port = 0xC000 + <out-PW-label>
UDP source port is 0x85E
Examples
 To configure a TDMoIP PW with UDP/IP network encapsulation:
• PW number 1
• PW type – TDMoIP (v2)
• PSN type – UDP/IP
• Out (destination) label – 3

• In (source) label – 2
• Far end type – E1
• Jitter buffer – 10 000
• OAM – enabled
• Peer – 1
• TDM payload size – 10 (480 bytes).
mp4100>config>pwe# pw 1 type tdmoip-v2 psn udp-over-ip
mp4100>config>pwe>pw(1) label out 3 in 2
mp4100>config>pwe>pw(1) far-end-type e1
mp4100>config>pwe>pw(1) jitter-buffer 10000
mp4100>config>pwe>pw(1) oam
mp4100>config>pwe>pw(1) peer 1
mp4100>config>pwe>pw(1) tdm-payload 10
 To configure a SAToP PW with UDP/IP network encapsulation:

• PW number 1
• PW type – SAToP
• PSN type – UDP/IP
• Jitter buffer – 10 000
• Peer – 1 (further configuration – under configure>peer)
• TDM payload size – 30.
mp4100>config>pwe# pw 1 type e1satop psn udp-over-ip
mp4100>config>pwe>pw(1) far-end-type unframed
 To configure a MEF-8 pseudowire:

• PW number 1
• PW type –SAToP
• PSN type – Ethernet
• Jitter buffer – 300
• OAM –disabled
• Peer – 1
• Egress port – SVI 1
• TDM payload size – 30

mp4100>config>pwe# pw 1 type t1satop psn ethernet

mp4100>config>pwe>pw(1) no oam
mp4100>config>pwe>pw(1) egress-port svi 1
Displaying PW Statistics
PW ports of MPW-1, VS and TP modules feature the collection of statistical
diagnostics, thereby allowing the carrier to monitor the transmission performance
of the links.
The pseudowire transmission statistics enable analyzing pseudowire traffic
volume, evaluate the end-to-end transmission quality (as indicated by sequence
errors), and jitter buffer performance. By resetting the status data at the desired
instant, it is possible to ensure that only current, valid data is taken into
consideration.
 To display the PW statistics:

• At the prompt config>slot>pwe>pw(<PW number>)#, enter show statistics
Displaying show statistics {total | all | all- • current - Displays the current statistics
statistics intervals | current} • all-intervals – Displays statistics for all valid
intervals (without current statistics)
• all –all statistics: first current statistics, then
statistics for all valid intervals, and finally total
statistics
• total – Displays total statistics of last 96 intervals
Displaying show statistics interval <interval-

statistics for a num 1..96>
specific interval
PW statistics are displayed. The counters are described in the tables

below.
For example:
Current Statistics:
mp4100>config>pwe>pw(1)# show statistics current
Valid Intervals : 0
*Missing Packets : 0
*Mis-order Dropped Packets : 0
*Reordered Packets : 0
Jitter Buffer Underflows Seconds : 0
Jitter Buffer Overflows Seconds : 0
Min Jitter Buffer Level (uSec) : 0
Max Jitter Buffer Level (uSec) : 441

Max Jitter Buffer Deviation (uSec) : 441
Note
All the examples are given for VS/TP modules. In the MPW-1 modules, the
counters marked by an asterisk are not displayed.

mp4100>config>pwe>pw(1)# show statistics interval 2
Interval Number : 2
Sequence Errors Seconds : 0

Missing Packets : 0
Mis-order Dropped Packets : 0
Reordered Packets : 0
All statistics:
mp4100>config>pwe>pw(1)# show statistics all
Valid Intervals : 0
Missing Packets : 0
Interval Number : 1
Missing Packets : 0
Interval Number : 2
Missing Packets : 0
Interval Number : 3

Missing Packets : 0
All Intervals Statistics:
mp4100>config>pwe>pw(1)# show statistics all-intervals
Interval Number : 1
Missing Packets : 0
Interval Number : 2
Missing Packets : 0

Interval Number : 3
Missing Packets : 0
Interval Number : 4
Missing Packets : 0

Interval Number : 5
Missing Packets : 0
more..
Total Statistics:
mp4100>config>pwe>pw(1)# show statistics total
Total
---------------------------------------------------------------
Rx Frames : 1391711
Tx Frames : 4798604
Sequence Errors Seconds : 0
Table 8-14. PWE Statistics Parameters – Current 15-Minute Interval
Time Elapsed (Sec) The elapsed time (in seconds) since the beginning of the current interval, in seconds.
The range is 1 to 900 seconds
Sequence Errors Displays the number of seconds during which sequence errors have been detected.
Seconds In accordance with the applicable standards, the transmitted packets carry a sequence
number that is automatically assigned, such that consecutive packets are
automatically consecutive sequence numbers. At the receive side, these numbers are
checked by the receive mechanism, which expects each new incoming packet to carry
the next number in the sequence, relative to the previous one (i.e., packet 5 must be
received after packet 4). Any deviation from the this rule indicates a problem with
packet flow integrity (and hence with the pseudowire payload (data or voice)
integrity), and in this case the sequence errors count is incremented by 1.
There are two main reasons for a sequence error event:
• One or more packets have been lost somewhere in the network.
• Packets have been reordered within the network. Packet reordering may occur due
to queuing mechanisms, rerouting by the network, or when the router updates
include very large routing tables
In VS, SH and TP modules, this number is the total number of seconds when the
Missing Packets, Mis-order Dropped Packets and Reordered Packets events occurred.
Missing Packets Number of missing packets as detected via Control Word sequence number gaps. This
(VS Modules only) count does not include misordered dropped packets.

Mis-order Dropped Number of packets detected via Control Word sequence number to be out of
Packets (VS sequence, and could not be re-ordered, or could not fit in the jitter buffer. This count
Modules only) includes duplicated packets.
Reordered Packets Number of packets detected via Control Word sequence number to be out of
(VS Modules only) sequence, but successfully reordered.
Jitter Buffer Displays the number of seconds during which at least one jitter buffer underflow
Underflows event has been detected (not relevant for HDLC pseudowires).
Seconds PW-containing modules are equipped with a Packet Delay Variation Tolerance buffer,
also called a “jitter buffer”, which is used to automatically compensate for packet
network delay variation (jitter). Each pseudowire has its own jitter buffer. Although
packets leave the transmitting PW-module at a constant rate, they will usually reach
the far end at a rate which is not constant, because in practice the network
transmission delay varies (due to factors such as congestion, rerouting, queuing
mechanisms, transport over wireless or half-duplex media, etc.).
TDM equipment at both ends of a pseudowire require a constant flow of data, and
cannot tolerate delay variation. Therefore, the receive side jitter buffer is required to
provide the TDM equipment with a synchronous and constant flow.
For this purpose, when a pseudowire is set up (and at any time after communication
is restored), the jitter buffer is loaded with packets up to its middle point: only after
this point it starts outputting TDM data towards the connected TDM equipment. The
stored packets assure that the TDM equipment will continue receiving data even if the
network delay momentarily increases. Obviously, if packets are delayed too long, the
buffer is gradually emptied out until it underflows (this situation is called buffer
starvation, and it affects the end-to-end voice/data integrity).
Each underflow event increases the jitter buffer underflow counter by 1.
Jitter Buffer Displays the number of seconds during which at least one jitter buffer overflow event
Overflows Seconds has been detected (not relevant for HDLC pseudowires).
As explained above, during steady state, the jitter buffer is filled up to its middle
point, which means that it has space to hold additional packets. An overflow will occur
when the network delay suddently decreases, for example, when a large burst of
packets reaches the PW module. If the burst includes more packets than the jitter
buffer can store at that instant, the buffer will be filled up to its top. In this case, an
unknown number of excess packets are dropped. To correct the situation, Megaplex-4
initiates a forced underflow by flushing (emptying) the buffer. Therefore, an overflow
always results in an immediate underflow. After the buffer is flushed, the process of
filling up the buffer is started again
Min Jitter Buffer Actual minimum size of the jitter buffer recorded for this pseudowire in the selected
Level (usec) interval, in µsec (not relevant for HDLC pseudowires).
Max Jitter Buffer Actual maximum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer The maximum jitter buffer deviation (variation of delay, in µsec) reported during the
Deviation (usec) selected interval (not relevant for HDLC pseudowires). This is the maximum jitter level
that had to be compensated for in the selected interval

Table 8-15. PWE Statistics Parameters – All Intervals Statistics
displayed, not including the current (not finished) interval (up to 96)
Sequence Errors Displays the number of seconds during which sequence errors have been detected.
Seconds In accordance with the applicable standards, the transmitted packets carry a sequence
number that is automatically assigned, such that consecutive packets are
automatically consecutive sequence numbers. At the receive side, these numbers are
checked by the receive mechanism, which expects each new incoming packet to carry
the next number in the sequence, relative to the previous one (i.e., packet 5 must be
received after packet 4). Any deviation from the this rule indicates a problem with
packet flow integrity (and hence with the pseudowire payload (data or voice)
integrity), and in this case the sequence errors count is incremented by 1.
There are two main reasons for a sequence error event:
• One or more packets have been lost somewhere in the network.
• Packets have been reordered within the network. Packet reordering may occur due
to queuing mechanisms, rerouting by the network, or when the router updates
include very large routing tables
Missing Packets Number of missing packets as detected via Control Word sequence number gaps. This
(VS Modules only) count does not include misordered dropped packets.
Mis-order Dropped Number of packets detected via Control Word sequence number to be out of
Packets (VS/SH/TP sequence, and could not be re-ordered, or could not fit in the jitter buffer. This count
Modules only) includes duplicated packets.
Reordered Packets Number of packets detected via Control Word sequence number to be out of
(VS/SH/TP Modules sequence, but successfully reordered.
only)
Min Jitter Buffer Actual minimum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer Actual maximum size of the jitter buffer recorded for this pseudowire in the selected
Max Jitter Buffer The maximum jitter buffer deviation (variation of delay, in µsec) reported during the
Deviation (usec) selected interval (not relevant for HDLC pseudowires). This is the maximum jitter level
that had to be compensated for in the selected interval
Table 8-16. PWE Statistics Parameters – Total Statistics
Tx Frames Total number of frames transmitted toward the PSN
Rx Frames Total number of frames received from the PSN
Sequence Errors Seconds Total number of seconds during which sequence errors have been detected.
In VS modules, this number is the total number of seconds when the Missing
Packets, Mis-order Dropped Packets and Reordered Packets events
occurred.
Jitter Buffer Underflows Total number of jitter buffer underflow events (not relevant for HDLC
Seconds pseudowires).

Jitter Buffer Overflows Total number of jitter buffer overflow events (not relevant for HDLC
Seconds pseudowires).
Clearing Statistics
 To clear the PW statistics:
• At the prompt config>pwe>pw<PW number>)#, enter clear-statistics.
The statistics for the specified PW are cleared.
Viewing the Pseudowire Status and Summary

 To display a single PW status:
1. At the config#pwe prompt, enter the desired pseudowire (pw <number>).
The config>pwe>pw(<number>)$ prompt appears.
2. Enter show status.
The status screen appears. For information on the connectivity status
values, refer to the table below.
mp4100>config# pwe
mp4100>config>pwe# pw 2
mp4100>config>pwe>pw(2)# show status
PW : pw-2
Name : pw-1
PW Type : CES PSN Data
PSN Type : UDP Over IP
Connectivity Status : Up
Out Label : 2
In Label : 2
Peer IP Address : 20.20.11.1
Next Hop MAC Address : 00-00-00-00-00-00
The table below explains the connectivity status values of the selected
pseudowire.
Table 8-17. Pseudowire Connectivity Status Values
Displayed
Disable The pseudowire is disabled
Up The pseudowire carries traffic, and both the remote and the local
pseudowire endpoints receive Ethernet frames. However, there
may be problems such as sequence errors, underflows, overflows,
etc., which may be displayed using the Statistics function.

Displayed
Unavailable The pseudowire reports loss of connectivity (it did not receive
neither OAM, nor data packets for 10 seconds or more (OAM link
then reports loss of synchronization). This is often caused by
network problems, or configuration errors.
Down The pseudowire is waiting for timeslot assignment
Local Fail A failure has been detected at the local pseudowire endpoint.
Remote Fail A failure is reported by the remote pseudowire endpoint.
 To display PW configuration summary:

• At the config>pwe# prompt, enter the show pw-summary command.
For example:
mp4100>config>pwe# show summary
PW : 1 PW Type : CES PSN Data

PSN Type : UDP Over IP Status : Up
Out Label : 1 In Label : 1
Peer : 1 Next Hop MAC Address: 00-00-00-00-00-00
Peer IP Address : 10.10.10.200
Jitter Buffer : 2500 Payload Size : 5
detected.
Table 8-18. Pseudowire Configuration Error Messages
460 Error SAME IP FOR ROUTER INTERF 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 address (0.0.0.0) have not yet been changed.
461 Error NOT SAME SUBNET FOR At least one of the IP addresses assigned to router
ROUTER INTERF & D.GATEWAY interfaces must be in the IP subnet of the Megaplex-4
router default gateway.

463 Error IN PW LABEL IS NOT UNIQUE This message, which is generated only after the specified
pseudowire is switched to the no shutdown state,
indicates that two or more pseudowires have the same
source UDP port number (the check is made irrespective
of the pseudowire PSN type, UDP/IP or Ethernet). This is
not allowed.
464 Error IP & NEXT HOP ARE THE SAME This message is generated after the specified static route
FOR STATIC ROUTE is updated, and indicates that the next hop IP address and
the destination IP address of the route are the same.
This is not allowed – the addresses must be different. If
the next hop IP address is not needed, leave the default
value, 0.0.0.0.
default IP addresses (0.0.0.0) have not yet been changed.
465 Error STATIC ROUTE IP IS NOT 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
466 Error ROUTER INTERF CAN'T BE ON The IP addresses assigned to the router interfaces must
THE SAME SUBNET be in different IP subnets.
467 Error MORE THAN 16 PWS FOR DS1 You are trying to connect too many pseudowires to the
PORT same ds1 port (the maximum is 16 pseudowires per port).
468 Error ILLEGAL FAR END TYPE The pseudowire far-end-type-mp parameter must match
FRAMING the framing mode of the ds1 port supporting the
pseudowire:
• Framed mode: select e1, t1-esf, or t1-sf
• Unframed mode: select unframed.
469 Error DS1 PORT OF PW IS DOWN The ds1 port assigned to a pseudowire is set to
shutdown. Change its setting to no shutdown.
470 Error TOO MANY ROUTER You are trying to configure more than 6 router interfaces
INTERFACES on a MPW-1 module (MPW-1 supports a maximum of 6
router interfaces). Check and remove unused interfaces.
471 Error NUMBER OF BYTES IN FRAME In CESoPSN the number of TDM payload bytes is equal to
EXCEEDS 1440 {tdm-payload value <4–360> * (number of timeslots
cross-connected between the PW and DS1 port).
This number must not exceed 1440 bytes.

472 Warning CHANGE MAY CAUSE DATA As a result of the last configuration actions, during the
INTERFERENCE database update you are initiating, the internal MPW-1
pseudowire processing assignments will be recalculated.
You are warned that this may this cause a short traffic
disruption (errors) for the other pseudowires served by
the same MPW-1 module. If this is not acceptable,
postpone the update and perform it while traffic load is
light
473 Error WRONG TIMESLOT When the redundancy partner of a DS1 port of the MPW-1
ASSIGNMENT is a T1 port, it is not allowed to assign more than 24
timeslots on the DS1 port.
474 Error WRONG SATOP PARAMETERS When using the SAToP protocol, make sure that DS1 port
is cross-connected via ds1 command and not ds0.
far-end-type-mp should be set to unframed.
475 Error PWS FROM DIFF SLOTS Pseudowires configured on different MPW-1 modules
DEMANDS DIFF PEERS must be configured with different peers, even if the
destination address is the same.
Using different peer numbers will result in the creation of
different internal flows, each directed to the relevant
router interface
476 Error PROTECTED PORTS HAVE When TDM protection is configured between two DS1
ASSYMETRIC PARAMETERS ports, all their physical layer parameters must be identical
477 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.
478 Error PEER NEEDS ROUTER It is not possible to configure peers before at least one
INTERFACE router interface has been configured.
479 Error V1/V2 PW LABEL DUPLICATED After assigning a label to a pseudowire using payload
format V1, do not assign the next label in sequence to a
pseudowire using payload format V2 (skip that label).
480 Error PEER NOT ATTACHED TO PW You have created a PEER without attaching it to any
pseudowire.
481 Error SLOT/PORT OF RI IS NOT You must configure a flow between the router interface
CONNECTED and the Ethernet entity
482 Error ASSYMETRIC FAR END TYPE When TDM protection is configured between two DS1
FOR PROTECTED PORTS ports, all their far-end-type parameters must be identical
483 Error PW FAR END TYPE PER SLOT When signaling is enabled on the DS1 port attached to a
MUST BE FRAMED pseudowire, the far-end-type-mp for all the pseudowires
terminated on the corresponding module must be set to
framed mode (either E1 or T1).
484 Error PEER PARAMETERS ARE Different peers must not have the same destination IP
DUPLICATED address and the same Next Hop IP address (at least one
of these parameters must be different). Therefore, if it
necessary for several pseudowires to reach the same IP
address, create separate router interfaces.

486 Warning TS NOT ASSIGNED TO ANY PW The specified MPW-1 DS1 port is connected to local
module ports, but no pseudowire has been assigned
timeslots on the same port.
You must specify timeslots to be connected to the DS1
port
487 Error PW CREATED BUT NOT A PW was created but not cross-connected to DS1 port.
ASSIGNED
488 Error PW CAN’T SERVE AS A pseudowire cannot serve as recovered clock source in
RECOVERED CLK one of this cases:
• It is using the HDLCoPSN protocol
• It is connected to VS module port.
489 Warning TS 16 IS RESERVED FOR CAS It is not allowed to assign timeslot 16 to a pseudowire
SIGNALING configured with signaling enabled and far-end-type=e1
490 Error FAULT PROPAGATION OF PW To use fault propagation for pseudowires, you must
MUST USE OAM enable the use of OAM
491 Error SAME IP CONFIGURED IN More than one router interfaces are configured with the
ANOTHER INTERFACE same IP address
493 Error STATIC ROUTE ADDRESS DOES Next hop address of static route is invalid
NOT MATCH
494 Warning WRONG PAYLOAD SIZE FOR In the case of voice with signaling transferred with
SIGNALING CESoPSN protocol, the following restrictions apply
depending on the far-end-type.
far-end-type=e1: tdm-payload value must be 16.
far-end-type=t1-esf, t1-sf: tdm-payload value must be
24.
495 Warning OAM IS NOT SUPPORTED OAM is not supported for MEF-8 encapsulation.
496 Error TDM-PAYLOAD SIZE NOT Tdm-payload value of less than 4 frames cannot be
SUPPORTED configured in MPW-1 modules operating with CESoPSN
encapsulation.
757 Error PORT CAN BE BOUND TO A DS1/Serial port can be cross-connected with only one
SINGLE PW ONLY PW port.
758 Error NUMBER OF BYTES IN FRAME When working with VS modules (CESoPSN encapsulation),
EXCEEDS 256 the number of bytes must not exceed 256.
The number of bytes is equal to number of frames (tdm-
payload size) multiplied by the number of timeslots cross-
connected with this PW. For example, when woking with
tdm-payload size 64, the maximum number of connected
ds1/serial timeslots is 4.
759 Error PW TYPE NOT SUPPORTED Only CESoPSN PW type is supported in supported in VS
modules.
760 Error SERIAL PORT OF PW IS DOWN The serial port cross-connected with this PW, is in
“shutdown” state.

761 Error TDM-PAYLOAD SIZE EXCEEDS For PW assigned to VS modules, tdm-payload size cannot
64 exceed 64 (Frames in packet).
765 Error ILLEGAL TUNNEL INDEX LABEL If an ingress label is configured for psn=mlps, the egress
label must be configured as well, and vice versa.
8.8 Router (Management)

Each router interface is assigned an IP address and can be bound to one of the
Megaplex-4 ports. The router supports up to 128 interfaces for binding TDM (E1,
T1, E1-i, T1-i) ports and up to 4 interfaces for binding SDH/SONET ports.
Management Router is configured at the router(1) level.
Note There are two routers in the Megaplex-4 architerchure: Router 1 is used for
inband management, while Router 2 is used for pseudowire routing. Router 2 is
explained in the Router (Pseudowire) section.
Megaplex-4 supports Proxy ARP functionality defined in RFC 1027.
Note Only IP addresses that are not included in the Interface #1 subnet can be
represented by Proxy-ARP. These IP addresses must be learned from the
management ports operating with RIP routing protocol.
Benefits
Router is used for segmenting a LAN, increasing network performance and
making packet forwarding more efficient.
Factory Defaults
The router interface RI#1 (see in Figure 8-1) is created automatically and included
into the default configuration file.
Configuring Inband Management

To define inband management through E1/T1 and SDH/SONET ports with its
parameters (dcc encapsulation, mode and routing-protocol for sdh-sonet ports),
protocol and routing-protocol for e1, t1, e1-i, t1-i ports), refer to the relevant
section in Chapter 6: E1 ports for e1 and e1-i ports, T1 ports for t1 and t1-i
ports, SDH/SONET ports for sdh-sonet ports.
Since inband management is transported over low speed channels and routing is
done by Host SW, the recommended quantity of nodes managed inband (DCC or
DTS) is 5. Larger chains must be fragmented by connecting node#6 via high
speed out-of-band link, for example VCG or Serial Bundle over full E1/T1.
8-136 Router (Management) Megaplex-4

In applications based on Megaplex-4 ver 3.0 and up, only RIP-2 protocol must be
used due to its capability to advertize subnets and single IP addresses, compared
to Proprietary RIP that supports advertizing only single IP addresses. Use
Proprietary RIP only on links attached to older Access+ products such as
Megaplex-2100/2104, DXC, FCD etc.
Loopback Router Interface

A loopback router interface is a virtual interface, whose IP address can be used as
IP address of the Megaplex device. Its IP address is not in either of the Router
subnets and published to the Router via RIP.
The loopback interface is not part of Factory default and is not bound to any
physical or virtual port. Once configured, it is always up, and its IP address is used
as device address, as an alternative of the IP address of RI#1.
Any Router 1 interface can be declared a loopback type, excluding #1.
Configuring the Management Router

Router configuration includes the following steps:
1. Adding a router instance
2. Add and configure router interfaces (1–132, 1)
Megaplex-4 ports.
 To configure a router instance:
1. Navigate to config>router(1)#.
Note Configuring Router 2 is explained in the Router (Pseudowire) section.
2. Configure the router as illustrated and explained below.
Assigning a name to the router name <value> Using no name deletes the router name
Administratively enabling the no shutdown Using shutdown administratively

router interface disables the router interface
Configuring router interfaces, interface <1–132> Using no interface <port_number>

see below deletes the router interface
Interface #1 is already defined as part of
the Default configuration. However it
can be configured at the interface level
(see below)
Configuring the static route and static-route <IP-address/ The next hop must be a subnet of one of
the next gateway (next hop) IP-mask-of-static-route> the router interfaces
using the next hop’s IP address address A particular case of a static route is
<IP-address-of-next-hop> default gateway, which is defined in
priority <1..255> Megaplex-4 by configuring a static route
0.0.0.0/0.
Megaplex-4 Router (Management) 8-137

Displaying the routing table show routing-table
Note The following IP addresses cannot be used for router interfaces:

• 255.255.255.255 – limited broadcast
• 127.x.x.x – loopback network
• 0.0.0.0 – this host
• 224.x.x.x – classes D and E
• x.y.z.255 – directed broadcast for net
• 0.0.0.x or zero mask.
The following marking actions can be performed at the interface level, at the
config>router(1)>interface(interface_number)# prompt.
Assigning a short name to name <string> Using no name removes the name
the router interface
Administratively enabling no shutdown Using shutdown administratively

the router interface disables the router interface
Defining the router loopback The loopback interface cannot be

interface to be of the bound to any physical or logical port.
loopback type Only one loopback interface can be
defined for the Megaplex device.
Assigning IP address and address <IP-address/IP-mask> For creating subnets, RAD

subnet mask to the router recommends using an IP subnet
interface calculator, for example
http://www.wildpackets.com/. Use the
following guidelines:
• When designing a ring, assign to
each interface a small subnet which
contains a minimum of IP
addresses (2 -3).
• Subnets inside the ring should not
overlap, that is the ring no two
addresses inside the ring should be
identical.
• IP-mask for loopback interface
must be /32.
Binding the router bind { sdh-sonet | e1 | t1 | e1-i | t1-i } To remove the binding, you must
interface to an sdh-sonet, <slot/port> delete the router interface (use no
e1, t1, e1-i, or t1-i port interface command)

Binding the router bind {e1 | t1} Megaplex Optimux cards (OP-34C,
interface to an E1/T1 <slot/port/tributary> OP-108C) only
Optimux module port To remove the binding, you must
delete the router interface (use no
interface command)
Binding the router bind svi <port-number> Router interface #1 is bound to SVI
interface #1 to an SVI port #1 by default. It is not
port recommended to change this binding.
Using no before bind removes the
binding
Enabling RIP-2 protocol rip v2 This option is possible only after RI#1
(interface #1 only) is bound to SVI.
Using no rip disables the protocol
Displaying a routing table show routing-table
Displaying the Routing Table

The routing table displays the following entries:
• Interfaces configured by the user provided they are synchronized (#27, #28,
#29 in our example). These interfaces are marked with Protocol “Local”.
• Static routes configured by the user, including the default gateway, or static
route 0.0.0.0/0 (in our example #1). These interfaces are marked with
Protocol “Static”.
• Interfaces learned from different protocols (in the example, the rest of the
interfaces have been learned from the RIP protocol).
For each interface the routing table includes the following:
• IP Address/Mask
• IP Address of the next hop
• Routing protocol
• Distance between this interface and the router IP addresses in hops
(Metric-1). In the case of a static route Metric-1 denotes priority.
 To display a routing table:

• At the config>router(1)# prompt, enter show routing-table.
The routing table is displayed.
Num IP Address/Mask Next Hop Protocol Metric-1

---------------------------------------------------------------
1. 0.0.0.0/0 172.17.173.1 Static 1
2. 172.17.173.0/24 172.18.197.49 RIP 5

3. 172.17.173.2/32 172.18.197.49 RIP 5

4. 172.18.197.4/30 172.18.197.49 RIP 4

5. 172.18.197.5/32 172.18.197.49 RIP 5
6. 172.18.197.6/32 172.18.197.49 RIP 4
7. 172.18.197.8/30 172.18.197.49 RIP 5
8. 172.18.197.9/32 172.18.197.49 RIP 5
9. 172.18.197.10/32 172.18.197.49 RIP 6
10. 172.18.197.12/30 172.18.197.49 RIP 3
11. 172.18.197.13/32 172.18.197.49 RIP 4
12. 172.18.197.14/32 172.18.197.49 RIP 3
13. 172.18.197.16/30 172.18.197.58 RIP 5
14. 172.18.197.17/32 172.18.197.58 RIP 5
15. 172.18.197.18/32 172.18.197.49 RIP 6
16. 172.18.197.24/30 172.18.197.49 RIP 4
17. 172.18.197.25/32 172.18.197.49 RIP 4
18. 172.18.197.28/30 172.18.197.58 RIP 5
19. 172.18.197.29/32 172.18.197.58 RIP 5
20. 172.18.197.32/30 172.18.197.49 RIP 6
21. 172.18.197.33/32 172.18.197.49 RIP 6
22. 172.18.197.36/30 172.18.197.49 RIP 3
23. 172.18.197.37/32 172.18.197.49 RIP 3
24. 172.18.197.40/30 172.18.197.49 RIP 2
25. 172.18.197.41/32 172.18.197.49 RIP 3
26. 172.18.197.42/32 172.18.197.49 RIP 2
27. 172.18.197.50/30 0.0.0.0 Local 0
28. 172.18.197.53/30 0.0.0.0 Local 0
29. 172.18.197.57/30 0.0.0.0 Local 0
30. 172.18.197.58/32 172.18.197.58 RIP 2
error is detected.
405 Error MORE THAN ONE TRAP Only one loopback trap source address can be defined in
SOURCE ADDRESS Megaplex-4
406 Error TRAP SOURCE ADDRESS DOES The configured trap source address matches neither of IP
NOT MATCH addresses existing in the Megaplex device
445 Error MORE THAN ONE LOOPBACK Only one loopback interface can be defined in Megaplex-4
INTERFACE
446 Error LOOPBACK INTERFACE MUST The loopback interface mask must be /32
BE HOST
447 Error MORE THAN ONE SVI PORT Only one SVI port can be bound to the router 1 interface
BOUND

448 Error RI NOT BOUND TO PORT OR This router interface is either not bound to any port or
PORT SHUTDOWN bound to a port which is in shutdown state
449 Error ILLEGAL IP ADDRESS The IP address is illegal (for example, it is a subnet ID or
subnet broadcast ID)
Example
Figure 8-1 shows an application with four Megaplex-4 nodes (MP1, MP2, MP3,
MP4) connected by an SDH ring. The central node (MP1) is connected via its
control port to the Management router which manages the entire network. The
nodes are connected via small subnets, and four different colors designate IP
addresses from the same subnet (for example, the yellow line from MP1 CL.A link
1 to MP2 CL.B link 1 connects two addresses from the same subnet:
172.17.197.5/30 and 172.17.197.6/30).
In each Megaplex the configuration procedure is as follows:
1. Configure 2 SDH ports with DCC management
2. Configure 2 router interfaces with subnets and bind them to SDH ports
Note Router interface 1 and SVI port 1 are present in the Megaplex-4 configuration as
part of the factory default file and need not be created. By default, SVI port 1 is
bound to Router interface 1.
In addition, for the central Megaplex-4 MP1 (IP address 172.17.173.1) you must
configure the default gateway (static-route 0.0.0.0/0) and the next hop (static
route).
1 2 1 2
CL.A
CL.B
MP 2
1 2 1 2 1 2 1 2
CL.A
CL.B
CL.A
CL.B
MP 3
PC
172.17.174.54 MP 1 1 2 1 2
172.17.173.1
CL.A
CL.B
MP 4
172.17.174.1
Figure 8-18. Four Megaplex-4 Nodes in an SDH Ring

Router (not part of the MP configuration)

Next hop 172.17.197.0 172.17.173.2
172.17.179.1/24
MP 1 Static Route*
CL A 172.17.173.2/24
0.0.0.0/0
SVI Control 172.17.173.2/24 172.17.173.1
CL A L1 172.17.197.5/30
CL B L1 172.17.197.9/30
MP 2
SVI 172.17.197.25/30
CL A L1 172.17.197.13/30
CL B L1 172.17.197.6/30
MP 3
SVI 172.17.197.29/30
CL A L1 172.17.197.17/30
CL B L1 172.17.197.14/30
MP 4
SVI 172.17.197.33/30
CL A L1 172.17.197.10/30
CL B L1 172.17.197.18/30
* A static-route is needed on the router to subnet 172.17.197.X

#MP 1

exit all
configure router 1 static-route 0.0.0.0/0 address 172.17.173.1
configure port sdh-sonet cl-a/1 no shutdown

configure port sdh-sonet cl-a/1 dcc encapsulation hdlc mode d1-to-d3 routing-
protocol rip2
configure router 1 interface 1 bind sdh-sonet cl-a/1
configure router 1 interface 1 no shutdown
configure port sdh-sonet cl-b/1 no shutdown

configure port sdh-sonet cl-b/1 dcc encapsulation hdlc mode d1-to-d3 routing-
protocol rip2
configure router 1 interface 2 bind sdh-sonet cl-b/1
commit
save
#MP 2
exit all

protocol rip2

protocol rip2
commit
save

#MP 3
exit all

protocol rip2

protocol rip2
commit
save
#MP 4
exit all

protocol rip2

protocol rip2
commit
save
8.9 Router (Pseudowire)

The Megaplex-4 Router 2 function is used to route pseudowire packets generated
by the MPW-1 and VS modules installed in the chassis to their destination
(peers).
8-144 Router (Pseudowire) Megaplex-4

The terms and parameters needed by the Megaplex-4 router function to support
pseudowire routing are explained below:
• Router interfaces: the Megaplex-4 Router 2 function supports up to 100
router interfaces, each assigned a unique index number. Each router interface
has its own IP address; you must also specify an IP subnet mask, and the
module and port on which interface is located.
For each router interface, you can also enable the use of VLAN tagging and
specify a VLAN ID, to enable differentiating the traffic carried by this router.
Note that when the router interface is connected (via SVI) to a GbE port or a
VCG, VLAN tagging is always enabled.
Each MPW-1, VS or TP module supports up to 6, 12 or 4 different router
interfaces, respectively; additional interfaces can be configured on any bridge
port in the Megaplex-4. The IP address of the appropriate interface is
automatically inserted as the pseudowire source IP address.
• Pseudowire peers: the pseudowire destination is referred to as the
pseudowire peer. Megaplex-4 supports up to 100 peers, each assigned a
unique index number. The index number is then used to specify the
pseudowire destination, instead of directly providing the necessary
destination information. To configure a peer, it is necessary to provide its IP
address, and as an option – the next hop IP address. The peers (the
pseudowire destinations) and the associated routing information are defined
under configure peer context.
• Static routes: to control the paths used to reach the pseudowire
destinations, the Megaplex-4 router function supports the definition of up to
100 static routes, in addition to a default gateway.
Within the Megaplex-4, pseudowires are forwarded to the appropriate exit port
(always a router interface) by internal E-line Ethernet flows (an E-line flow is a
type of Ethernet logical connection that interconnects two bridge ports).
Each router interface serves as a bridge port for the pseudowires using it (in
addition, each Megaplex-4 Ethernet port also serves as a bridge port).
To help you design the routing information, Figure 8-19 summarizes the process
used to select the router interface for each pseudowire peer. The priority of the
various router interfaces, as determined by the routing process, is as follows:
1. If the peer IP address is in the subnet of a router interface, that interface will
always be used.
2. If the peer IP address is not within a router interface subnet, then the router
checks if the specified peer next hop address is within the subnet of a router
interface. If such a router interface is found, it is selected to serve as the
pseudowire exit port.
3. If neither of the previous conditions is fulfilled, the router checks if the
specified peer next hop address is specified in a static route that is within the
subnet of a router interface.
4. The last priority is to use the router interface that is within the default
gateway subnet.
Megaplex-4 Router (Pseudowire) 8-145

DB Update
Peer IP address
No in the subnet Yes
of one of the
router interfaces
Peer Next Hop

No in the subnet Yes
of one of the
router interfaces
Look in static routes

No table, for peer Next Hop in Yes
the subnet of one
of the router interfaces
Find a router interface in

the default gateway
subnet
Select as the router interface in use
Figure 8-19. Selecting the Active Router Interface for an Ethernet Flow Serving a Pseudowire
The PW Router is configured at the router(2) level.
Adding and Configuring Router Interfaces

Megaplex-4 ports.
Adding a Router Interface
 To add a router interface:

1. Navigate to configure router 2.
The config>router(2)# prompt is displayed.
2. Type the interface command and enter an interface number in the 1–100
range.
An interface is added and the config>router(2)>interface(number)#

For example:
 To add router interface 5:

mp4100# config router 2
mp4100>config>router 2 interface 5 bind svi 4
 To delete router interface 5:

mp4100>config router 1 no interface 5
Configuring the Router Interface

After adding a router interface, you have to configure it. Once configuration is
completed, you can display the routing table (see below).
 To configure a router interface:

• At the config>router(2)>interface(number)# prompt, enter all necessary
Assigning a short name to name <string> Using no name removes the name
the router interface
Administratively enabling no shutdown Using shutdown administratively

the router interface disables the router interface
Assigning IP address and address <valid IP address with mask For creating subnets, RAD
subnet mask to the router in the address/mask format> recommends using an IP subnet
interface calculator, for example
http://www.wildpackets.com/. Use the
following guidelines:
• Router interfaces must be on
different subnets
• When designing a ring, assign to
each interface a small subnet which
contains a minimum of IP
addresses (2 -3)
• Subnets inside the ring should not
overlap, that is no two addresses
inside the ring should be identical.
Binding the PW router bind svi <port> This SVI port will be further bound to
interface to an SVI port an ethernet or logical mac port.
Using no before svi removes the
binding.
Note The following IP addresses cannot be used for router interfaces:

• 255.255.255.255 – limited broadcast

• 127.x.x.x – loopback network
• 0.0.0.0 – this host
• 224.x.x.x – classes D and E
• x.y.z.255 – directed broadcast for net
• 1.1.1. x or zero mask.
For example:
 To configure a router interface 5:

• IP address 172.17.171.217, subnet mask 24
• Bound to SVI port 2
mp4100>config>router 2 interface 5 bind svi 2
 To delete router interface 5:

mp4100>config router 2 no interface 5
Displaying the Routing Table

The routing table displays the following entries:
• Interfaces configured by the user on condition that they are synchronized (in
our example #2, #3, #4). These interfaces are marked with Protocol “Local”.
• Static routes configured by the user, including the default gateway, or static
route 0.0.0.0/0 (in our example #1). These interfaces are marked with
Protocol “Static”.
For each interface the routing table includes the following:
• IP Address/Mask
• IP Address of the next hop
• Routing protocol
• Distance between this interface and the router IP addresses in hops
(Metric-1). In the case of a static route Metric-1 denotes priority.

 To display a routing table:

mp4100>config>router(2)# show routing-table
Num IP Address/Mask Next Hop Protocol Metric-1

-----------------------------------------------------------
1. 0.0.0.0/0 172.18.170.1 Static 1
2. 172.18.170.75/24 0.0.0.0 Local 0
3. 172.17.151.55/24 0.0.0.0 Local 0
Configuring Static Routes and Default Gateway

To control the paths used to reach the pseudowire destinations, the PW router
supports the definition of up to 100 static routes, in addition to a default
gateway.
You can add fixed (static) routes to the Megaplex-4 routing table. A particular
case of a static route is default gateway, which is defined in Megaplex-4 by
configuring a static route 0.0.0.0/0.
 To configure a static route:

• At the config>router(2) # prompt, enter the static-route command as follows:
• static-route <IP address/mask> address <IP address of a next hop host>
priority <priority 1 to 255>
For example:
 To configure a static route:

• IP address – 10.10.10.10
• Mask – 24
• Next hop address –172.17.144.1
• Priority – 5.
mp4100>configure router 2 static-route 10.10.10.10/24 address 172.17.144.1
priority 5
 To delete a static route:

mp4100>configure router 2 no static-route 10.10.10.10/24 address 172.17.144.1
 To configure a default gateway at the host with IP address 172.17.173.1:

• Navigate to configure router 2.
The config>router(2)# prompt is displayed.

mp4100>configure router 2 static-route 0.0.0.0/0 address 172.17.173.1
 To remove a default gateway:

mp4100>config router 2 no static-route 0.0.0.0/0 address 172.17.173.1
Example 1. Establishing PW Connectivity between HS-12N Module and

MPW-1 Fast Ethernet Port
1. Configuring an HS-12N module in slot 10:
configure slot 10 card-type high-speed hs12n
2. Configuring a MPW-1 module in slot 2:
configure slot 2 card-type pw mpw1
configure port ds1 2/1 no shutdown
configure port ds1 2/1 signaling
3. Configuring PW 1:
configure pwe pw 1 type tdmoip-v2 psn udp-over-ip
oam
peer 1
exit all
4. Configuring the PW destination:
configure peer 1 ip 10.10.10.3
5. Creating a TDM pseudowire cross-connection between PW 1 and serial
HS-12N port:
• Pseudowire (pw) 1.
configure cross-connect ds0 ds1 2/1 ts 1 serial 10/1
configure cross-connect pw-tdm pw 1 ds1 2/1 time-slots 1
6. Configuring the default gateway and interface 1 on PW router:
configure router 2
interface 1 address 10.10.10.2/24
7. Configuring SVI port and binding it to router interface 1:
configure port svi 1 no shutdown
interface 1 bind svi 1
exit all
8. Creating two symmetric flows between Ethernet port 2/1 on MPW-1 module
and SVI 1 port, classifier match-all named C1:

configure flows
classifier-profile c1 match-all
match all
exit
flow 1
no shutdown
classifier c1
ingress-port eth 2/1
egress-port svi 1
exit
flow 2
no shutdown
classifier c1
ingress-port svi 1
egress-port eth 2/1
exit all
Now the traffic from HS-12N serial port is forwarded to Ethernet port, which
Example 2. Establishing PW Connectivity between HS-12N Module and

VCG
1. Configuring an HS-12N module in slot 10:
configure slot 10 card-type high-speed hs12n
2. Configuring a MPW-1 module in slot 4
configure slot 4 card-type pw mpw1
configure port ds1 4/1 no shutdown
3. Adding and configuring the remote peer:
config peer 1 ip 9.9.9.9 name peer1 next-hop-ip 0.0.0.0
4. Configuring PW 1 and setting its destination peer:
configure pwe
pw 1 type tdmoip-v2 psn udp-over-ip
peer 1
exit all
5. Creating a TDM pseudowire cross-connection between PW 1 and serial
HS-12N port:
• Pseudowire (pw) 1.

configure cr ds0 ds1 2/1 ts 1 serial 10/1

configure cr pw-tdm pw 1 ds1 4/1 time-slots 1
6. Configuring the default gateway and interface 1 on PW router:
configure router 2
interface 1 address 2.2.2.2/24
exit all
7. Configuring SVI port and binding it to router interface 1:
configure port svi 1 no shutdown
interface 1 bind svi 1
exit all
8. Defining VCG 1 and mapping it to SDH:
configure port vcg cl-a/1 no shutdown
configure port vcg cl-a/1 bind vc-vt cl-a/1/1/1/1/1
9. Defining gfp encapsulation for VCG 1:
configure port gfp cl-a/1
no shutdown
bind vcg cl-a/1
exit all
10. Defining logical-mac (logical Ethernet port for creating the flow):
configure port logical-mac cl-a/1
no shutdown
bind gfp cl-a/1
exit all
11. Creating two symmetric flows (Flow 1 and Flow 2) between Logical-mac 1 on
CL-A module and SVI 1 port, classifier profile named vlan-10:
configure flows
classifier-profile vlan-10 match-all
match vlan 10
exit all
configure flows
flow 1
no shutdown
classifier vlan-10
egress-port svi 1
ingress-port logical-mac cl-a/1
exit
flow 2
no shutdown
classifier vlan-1
egress-port logical-mac cl-a/1
ingress-port svi 1
exit all
Now the traffic from HS-12N serial port is forwarded to a VCG, which serves as a
pseudowire exit port toward the PSN.

8.10 Quality of Service (QoS)

Megaplex-4 devices employ various traffic engineering techniques to optimize
service delivery and ensure end-to-end QoS. They enable multi-criteria traffic
classification as well as metering, policing and shaping to rate-limit user traffic
according to CIR and EIR profiles.
A 3-level hierarchical scheduling mechanism combines strict priority and weighted
fair queue scheduling to handle different types of traffic.
Weighted random early detection (WRED) policy is used for intelligent queue
management and congestion avoidance.
Factory Defaults
Refer to the following sections for the specific default for each type of QoS.
Bandwidth Profiles
Megaplex-4 supports the following bandwidth profiles:
• Shaper profile – Applied to queue group blocks
• Policer profile – Applied to flows to limit flow traffic, or to Ethernet ports to
limit broadcast/multicast traffic
Note You can control the egress bandwidth utilization by defining the committed
information rate and committed burst size in shaper and policer profiles. You can
also define the excessive information rate and the excessive burst size in policer
profiles.
CIR: Defines the Committed Information Rate (CIR) for the current profile. The CIR
specifies a bandwidth with committed service guarantee (“green bucket” rate).
CBS: Defines the Committed Burst Size (CBS) for the current profile. The CBS
specifies the maximum guaranteed burst size (“green bucket” size).
EIR: Defines the Excess Information Rate (EIR). The EIR specifies an extra
bandwidth with no service guarantee (“yellow bucket” rate).
EBS: Defines the Excess Burst Size (EBS). The EBS specifies the extra burst with
no service guarantee (“yellow bucket” size).
Compensation: You can specify the amount of bytes that the shaper or policer
can compensate for the layer 1 overhead (preamble and IFG) and the overhead
for the added VLAN header in case of stacking.
Factory Defaults
Megaplex-4 provides default bandwidth profiles, as specified in the following
table. The default policer profile Policer1 is the same for all kinds of ports, while
the default shaper profile depends on the type of port:
• GbeShaper for GbE ports of CL modules
• MeShaper for GbE ports of M-ETH modules
Megaplex-4 Quality of Service (QoS) 8-153

• FeShaper for Fast Ethenet ports of I/O modules

• LMShaper for Logical Mac ports
• PcsShaper for PCS ports of ASMi-54C modules.
Table 8-20. Default Bandwidth Profiles
Profile Type Shaper Policer
Profile Name GbeShaper FeShaper MeShaper LMShaper PcsShaper Policer1
cir 500000 10000 100000 150000 11392 1000000
cbs 65535 65535 65535 65535 65535 1048575
eir – – – – – 0
ebs – – – – – 0
compensation 0 0 0 0 0 0
traffic-type – – – – – all
Configuring Shaper Profiles

You can define up to 30 shaper profiles.
 To define a shaper profile:

1. At the configure>qos# prompt, enter shaper-profile followed by profile name.
The config>qos> shaper-profile(profile_name)$ prompt is displayed.
Specifying the CIR (Kbps) and CBS bandwidth [cir <cir-kbit-sec>] [cbs <cbs-bytes>] Typing no bandwidth removes the
(bytes) bandwidth limits bandwidth limits.
CIR allowed values: 0–1000000.
CBS allowed values:
• M-ETH: 4096–258048
(4-252 Kbytes)
• Other modules: 0, or 64–1048575.
Specifying the compensation (bytes) compensation <0–63>
Example
 To create and configure a shaper profile named Shap2:

• CIR = 99,840 kbps
• CBS = 32,000 bytes
• Compensation = 48.
8-154 Quality of Service (QoS) Megaplex-4

mp4100# configure qos shaper-profile Shap2

mp4100>config>qos>shaper-profile(Shap2)$ bandwidth cir 99840 cbs 32000
mp4100>config>qos>shaper-profile(Shap2)$ compensation 48
mp4100>config>qos>shaper-profile(Shap2)$
Configuring Policer Profiles

When the flows are established, a metering and policing function can be applied
to each flow on indirectly-attached ports to regulate traffic according to the
contracted CIR, EIR, CBS and EBS bandwidth profiles.
There is a restriction on the number of flows in the system employing “high-
speed policers”, that is, policers that have total CIR + EIR greater than 100 Mbps.
High-speed policer(s) cannot be used in more than 16 flows. Regular policers can
be used without restriction.
 To define a policer profile:

1. At the configure>qos# prompt, enter policer-profile followed by profile name.
The config>qos>policer-profile(profile_name)$ prompt is displayed.
Specifying the CIR (Kbps), bandwidth [cir <cir-kbit-sec>] Typing no bandwidth removes the bandwidth
CBS (bytes), EIR (Kbps), and [cbs <cbs-bytes>] [eir <eir-kbit-sec>] limits.
EBS (bytes) bandwidth limits [ebs <ebs-bytes>] CIR & EIR allowed values: 0–1000000.
EBS allowed values: 0, or 64–1048575.
CBS allowed values:
• M-ETH: 4096–258048 (4-252 Kbytes)
• Other modules: 0, or 64–1048575.
CIR can be set to zero only if CBS is set to zero.
EIR can be set to zero only if EBS is set to zero.
CIR + EIR must not exceed the maximum available
bandwidth.
CBS should be greater than the maximum frame
size.
For policer profiles that will be attached to
Ethernet ports to limit broadcast/multicast
traffic, only the CIR and CBS parameters are
relevant (EIR and EBS should be set to 0).
The CIR and EIR granularity depend on the
configured values, as described in Table 8-21.
The CBS must be greater than or equal to the CIR
divided by policer granularity.
Specifying the compensation compensation <0–63>

(bytes)
Specifying the traffic type traffic-type {all | broadcast | multicast | Note: Traffic types other than all are relevant
unknown-unicast } only for policer profiles attached to ports.

Table 8-21. Granularity Rounding Down of CIR/EIR
Policer Type CBS/EBS <= 64,000 Bytes < 128,000 Bytes < 256,000 Bytes < 512,000 Bytes <
64,000 Bytes CBS/EBS <= CBS/EBS <= CBS/EBS <= CBS/EBS <=
128,000 Bytes 256,000 Bytes 512,000 Bytes 1,048,575 Bytes
Port policer, or 64 Kbps 128 Kbps 256 Kbps 512 Kbps 1 Mbps
flow policer with
CIR and EIR <
100,000 Kbps
Flow policer with 500 Kbps 1 Mbps 2 Mbps 4 Mbps 8 Mbps

CIR or EIR >=
100,000 Kbps
Note: The info command displays the CIR/EIR value:

• Rounded down to 64 Kbps granularity for low-speed policers
• Rounded down to 500 Kbps granularity for high-speed policers.
Example 1
 To create and configure a policer profile named Policer4:

• CIR = 50,000 Kbps
• EIR = 30,000 Kbps
• EBS = 20,000 bytes
• Compensation = 56.
Note CIR and EIR are rounded down to 64K granularity, as this is a low-speed policer
with burst size < 64,000 bytes.
mp4100# configure qos policer-profile Policer4

mp4100>config>qos>policer-profile(Policer4)$ bandwidth cir 50000 cbs 28000 eir 30000 ebs 20000
mp4100>config>qos>policer-profile(Policer4)$ compensation 56
mp4100>config>qos>policer-profile(Policer4)$ info detail
bandwidth cir 49984 cbs 28000 eir 29952 ebs 20000
traffic-type all
compensation 56
mp4100>config>qos>policer-profile(Policer4)$
 To create and configure a policer profile named PolicerPort:

• CIR = 960 Kbps
• EIR = 0
• EBS = 0
• Traffic type = broadcast and multicast.

mp4100# configure qos policer-profile PolicerPort

mp4100>config>qos>policer-profile(PolicerPort)$ bandwidth cir 960 cbs 1000 eir 0 ebs 0
mp4100>config>qos>policer-profile(PolicerPort)$ traffic-type broadcast-and-multicast
mp4100>config>qos>policer-profile(PolicerPort)$ info detail
bandwidth cir 960 cbs 1000 eir 0 ebs 0
traffic-type broadcast-and-multicast
compensation 0
mp4100>config>qos>policer-profile(PolicerPort)$ exit all
mp4100# configure port ethernet 5
mp4100>config>port>eth(5)# policer profile PolicerPort
mp4100>config>port>eth(5)#
Example 2
The procedure is as follows:
1. Create and configure a policer profile named policer4, setting a rate limitation
of 12 Mbps
2. Assign the created policer profile to:
 ASMi-54C/ETH module installed in slot 2
 Ethernet port 1
#Creating the policer profile (Step 1)
mp4100>config>qos# policer-profile policer4 bandwidth cir 12000
#Displaying the policer profile

mp4100>config>qos# info detail
policer-profile "policer4"
bandwidth cir 12000
#Assigning the policer profile (Step 2)

mp4100>config>port# eth 2/1
mp4100>config>port>eth(2/1)# policer profile policer4
#Displaying the result

name "ASMI-54C ETH -7"
no shutdown
auto-negotiation
max-capability 100-full-duplex
no flow-control
policer profile "policer4"
Example 3
One of the use of policer profiles in Megaplex-4 is for Optimux modules to
control the rate of the ingress frames from the remote device. This is done by
defining the committed information rate (CIR) in policer profiles. The CIR specifies
the highest bandwidth (rate) of the ingress frames from the remote device.
Possible values are 0 to 100 000 kbps (100 Mbps). Frames that are over the
ingress rate limit are dropped. The procedure is as follows:
1. Create and configure a policer profile named 108c, setting a rate limitation of
10 Mbps (frames that are over this ingress rate limit are dropped)

2. Assign the created policer profile to:

 OP-108C module installed in slot 3
 Remote Optimux-108 connected to Section OP A
#Creating the policer profile (Step 1)
mp4100>config>qos# policer-profile 108c bandwidth cir 10000
#Displaying the policer profile

mp4100>config>qos# info detail
policer-profile "108c"
bandwidth cir 10000
#Assigning the policer profile (Step 2)

mp4100>config>port# mux-eth-tdm 3/1 remote
mp4100>config>port> mux-eth-tdm (3/1)remote#
configure port ethernet 1 policer profile 108c
Queue Mapping Profiles

Queue mapping profiles are used to convert the following user priorities into
internal priority queues. Megaplex-4 supports up to 12 queue mapping profiles.
• p-bit, when the ingress traffic is prioritized according to the 802.1p
requirements
• ip-dscp, when the ingress traffic is prioritized according to DSCP
• ip-precedence, when the ingress traffic is prioritized according to
IP precedence
For each profile, you have to define the queue mapping to map the user priority
values to the internal queue values. The internal queues are combined into a
queue profile, which can be assigned to a queue block.
Factory Defaults
Default Queue Mapping Profile

Megaplex-4 provides a default queue mapping profile named CosProfile1, which
can be used when the ingress traffic is prioritized according to the 802.1p
requirements. It is defined with classification p-bit, and the following mappings:
• Map p-bit 0 to queue 7
• Map p-bit 7 to queue 0.

Default Configuration for IP Precedence Classification

When a new queue mapping profile is created with classification IP precedence, it
contains the following mappings:
• Map p-bit 7 to queue 0.
Default Configuration for DSCP Classification

When a new queue mapping profile is created with classification DSCP, it contains
the following mappings:
• Map p-bit 7 through 63 to queue 0.
Adding Queue Mapping Profiles

When you create a queue mapping profile, you specify the name and the
classification method (p-bit, IP precedence, or DSCP).
 To add a queue mapping profile:

1. Navigate to configure qos.
The config>qos# prompt is displayed.
2. Type:
queue-map-profile <queue-map-profile-name> classification {p-bit |
ip-precedence | ip-dscp }
A queue mapping profile with the specified name and classification
method is created and the following prompt is displayed:
config>qos>queue-map-profile (<queue-map-profile-name>)$. The
mappings for the new profile are configured by default as described in
Priority Queue Mapping.
3. Configure the queue profile mappings as described in Configuring Queue
Mappings.

Configuring Queue Mappings

1. Navigate to config qos queue-map-profile <queue-map-profile-name> to
select the queue mapping profile to configure.
The following prompt is displayed:
config>qos>queue-map-profile(<queue-map-profile-name>)#
2. Map the user priorities to queue IDs as necessary:
 Classification p-bit or IP precedence:
map <0-7> to-queue <0-7>
 Classification DSCP:
 Classification CoS:
Examples
 To create and configure a queue mapping profile named QMapPbit with

classification p-bit:
• Map priority 0 to queue 3
• Map priority 4 and 6 to queue 2.
exit all
configure qos queue-map-profile QMapPbit classification p-bit
map 0 to 3
map 4 to 2
map 6 to 2
exit all
 To display the configuration information for queue mapping profile QMapPbit:

mp4100# configure qos queue-map-profile QMapPbit
mp4100>config>qos>queue-map-profile(QMapPbit)# info detail
map 0 to-queue 3
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4..6 to-queue 2
map 7 to-queue 0
 To create and configure a queue mapping profile named QMapIPprec with

classification IP precedence:
• Map priority 2 and 3 to queue 3.
exit all
configure qos queue-map-profile QMapIPprec classif ip-precedence
map 2 to 3
map 3 to 3
exit all

 To display the configuration information for queue mapping profile QMapIPprec:

mp4100# configure qos queue-map-profile QMapIPprec
mp4100>config>qos>queue-map-profile(QMapIPprec)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2..4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0
 To create and configure a queue mapping profile named QMapDSCP with

classification DSCP:
• Map priority 63 to queue 5.
exit all
configure qos queue-map-profile QMapDSCP classif ip-dscp
map 7 to 6
map 55 to 4
map 63 to 5
exit all
 To display the configuration information for queue mapping profile QMapDSCP:

mp4100# configure qos queue-map-profile QMapDSCP
mp4100>config>qos>queue-map-profile(QMapDSCP)# info detail
map 0 to-queue 7
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 6
map 8..54 to-queue 0
map 55 to-queue 4
map 56..62 to-queue 0
map 63 to-queue 5
Marking Profiles
Marking profiles map the P-bit, IP precedence, DSCP, or CoS classifications to the
egress priority tags. The marking can also be done per color (green and/or
yellow), to support color re-marking, optionally specifying the Drop Eligible
Indicator (DEI) bit in the frame header. Megaplex-4 supports up to 12 marking
profiles.
Factory Defaults
Megaplex-4 provides a default non color-aware marking profile named
MarkingProfile1, which can be used when the ingress traffic is prioritized

according to the 802.1p requirements. It is defined with classification p-bit and

method p-bit, and the following markings:
• P-bit 0 => priority 0
• P-bit 1 =>priority 1
• P-bit 7 =>priority 7.
When a non color-aware marking profile is created, it has the same configuration
as MarkingProfile1.
Configuring Marking Profiles
 To define a marking profile and assign a priority mark to it:

1. Navigate to the qos context (config>qos).
2. Define the marking profile and assign a classification and a method to it:
3. marking-profile <marking-profile-name>
[classification {p-bit | ip-precedence | ip-dscp} [method p-bit] [color-aware
{none | green-yellow}
To define a color-aware profile, specify color-aware green-yellow.
Queue Block Profiles

In order to facilitate congestion management, you can sort traffic by applying
queue block profiles to queue block entities. A queue block profile contains
entries for queues 0–7, with the following parameters:
• Scheduling method:
 Strict – High-priority queues that are always serviced first. If a
lower-priority queue is being serviced and a packet enters a higher queue,
that queue is serviced immediately.
 WFQ (weighted fair queuing) – If one port does not transmit, its unused
bandwidth is shared by the ‘transmitting’ queues according to the
assigned weight.
In configurations with Strict and WFQ queues, the WFQ frames are
transmitted only after the transmission of frames associated with the Strict
queues is completed.
Note If one of the internal queues is configured to WFQ, queues with a higher queue
ID cannot be configured to Strict.
• Depth (queue size), in bytes.

Factory Defaults
Megaplex-4 provides a default queue block profile (for level 0) named
DefaultQueue1, which defines queues 0–7 as follows:
• Congestion avoidance: WRED profile corresponding to queue
• Scheduling method: WFQ, with weight set to 100
• Depth: 49152 bytes.
Default queue block profiles for level 1 are defined as "Scheduling1" to
"Scheduling8", with no congestion avoidance and Scheduling method WFQ, with
weight set to 100.
Adding Queue Block Profiles

You can define up to 16 queue block profiles.The Megaplex-4 device may create
up to 16 additional queue block profiles for internal usage.
 To add a queue block profile:

2. Type:
queue-block-profile <queue-block-profile-name>
A queue block profile with the specified name is created and the
config>qos>queue-block-profile(<queue-block-profile-name>)$ prompt is
displayed. The queues for the new profile are configured by default as
described in Factory Defaults.
3. Configure the queue block profile as described in Configuring Queue Block
Profile .
Configuring Queue Block Profile

17B
 To configure a queue block profile:

1. Navigate to config qos queue-block-profile <queue-block-profile-name> to
select the queue block profile to configure.
The config>qos>queue-block-profile(<queue-block-profile-name>)#
2. Perform the following for each queue that you wish to configure:
a. To configure a queue, enter:
queue <queue-ID>
config>qos>queue-block-profile(<queue-block-profile-name>)>queue(<queue-ID>)#.
b. Enter all necessary commands according to the tasks listed below.
c. Type exit to return to the queue block profile context.
Setting scheduling scheduling { strict | wfq The weight range is 3–110

method <weight>}

Specifying queue depth <value> Allowed range: 0–1048576

depth (in bytes) Notes:
• The queue depth that you configure might be
changed by Megaplex-4 due to granularity (see
Table 8-22). After you configure the queue depth,
it is recommended to use info detail to see the
actual value
• A queue block has 1 MB available, therefore the
sum of the depths of its eight queues must be no
greater than 1,048,576
.
Assigning a WRED congestion-avoidance wred You can assign a default profile (DefaultWREDProfile)
profile to the internal profile <wred-profile-name> to the internal queue or modify it, if needed.
queue no congestion-avoidance wred removes a WRED
profile association.
Table 8-22. Queue Depth Granularity
Entered Via CLI Granularity
0–1024 64
1025–16383 1024
16384–262143 16384
262144–1048576 262144
Example
 To create and configure a queue block profile named QBlockProf1:

• Queue 0 set to strict scheduling and depth 524,288
• Queue 1 set to strict scheduling and depth 212,992
• Queue 7 set to WFQ scheduling with weight 75.
mp4100# configure qos queue-block-profile QBlockProf1
mp4100>config>qos>queue-block-profile(QBlockProf1)$ queue 0
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ scheduling strict
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ depth 524288
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(0)$ exit
mp4100>config>qos>queue-block-profile(QBlockProf1)# queue 1
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(1)# scheduling strict
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(1)# depth 212992
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(1)# exit
mp4100>config>qos>queue-block-profile(QBlockProf1)# queue 7
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(7)# scheduling wfq 75
mp4100>config>qos>queue-block-profile(QBlockProf1)>queue(7)#

Queue Group Profiles

In order to facilitate congestion management, you can sort traffic by applying one
queue group profile per port. You can define up to 8 queue group profiles per
Megaplex-4 unit. Each queue group can contain up to 8 queue blocks in level 0
and one queue block in level 1.
Factory Defaults
Megaplex-4 provides default five queue group profiles. The profiles depend on
the type of port and are as follows:
• "GbeDefaultQueueGroup" for GbE ports of CL modules:
# queue-group-profile "GbeDefaultQueueGroup"
queue-block 1/1
name "Level1QueueBlock"
profile "Scheduling1"
exit
queue-block 0/1
name "Put your string here"
profile "DefaultQueue1"
shaper profile "GbeShaper"
exit
• "MeDefaultQueueGroup" for GbE ports of M-ETH modules
# queue-group-profile "MeDefaultQueueGroup"
queue-block 1/1
exit
queue-block 0/1
shaper profile "MeShaper"
exit
• "FeDefaultQueueGroup" for Fast Ethenet ports of I/O modules
# queue-group-profile "FeDefaultQueueGroup"
queue-block 1/1
exit
queue-block 0/1
shaper profile "FeShaper"
exit
• “LMDefaultQueueGroup” for Logical Mac ports

# queue-group-profile "LMDefaultQueueGroup"
queue-block 1/1
exit
queue-block 0/1
shaper profile "LMShaper"
exit
• "PcsDefaultQueueGroup" for PCS ports of ASMi-54C modules.
# queue-group-profile "PcsDefaultQueueGroup"
queue-block 1/1
exit
queue-block 0/1
shaper profile "PcsShaper"
exit
For the default profiles mentioned in the above screens see the following
sections:
• Shaper profiles – Table 8-20 in Bandwidth Profiles
• DefaultQueue1, Scheduling{1-5} – Queue Block Profiles
Adding Queue Group Profiles
 To add a queue group profile:

2. Type:
queue-group-profile <queue-group-profile-name>.
A queue group profile with the specified name is created and the
following prompt is displayed:
config>qos>queue-group-profile(<queue-group-profile-name>)$
3. Configure the queue group profile as described in Configuring Queue Group .
Configuring Queue Group Parameters

175B
 To configure a queue group profile:

1. Navigate to config qos queue-group-profile <queue-group-profile-name> to
select the queue group profile to configure.
The config>qos>queue-group-profile(<queue-group-profile-name>)#

2. Select a queue block in level 0 or 1 to configure:

queue-block 0/<1–8>
queue-block 1/1
Note Level 1 Queue Block profile must be unique per Queue Group

config>qos>queue-group-profile(<q-grp-profile-name>)>queue-block(<level/ID>)#
4. If you wish to configure another queue block, type exit to return to the queue
group profile context, and start again at Step 2.
Assigning a name to the queue block name <block-name>
Note
Normally there is no need for you to enter the bind command. When you add a
queue block in level 0 to the profile, bind is done automatically.
You cannot use the bind command if the queue group contains a single
queue block in level 0.
Example
Note This example uses the shaper profile and queue block profile created in the
examples in the preceding sections.
 To create and configure a queue group profile named QGroupProf1:

• Queue block 0/1:
 Queue block profile: QBlockProf1
 Shaper profile: Shap2.
Note Queue blocks 1/1 and 0/2 are automatically created.

mp4100# configure qos queue-group-profile QGroupProf1

mp4100>config>qos>queue-group-profile(QGroupProf1)$ queue-block 0/1
mp4100>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ profile
QBlockProf1
mp4100>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ shaper
profile Shap2
mp4100>config>qos>queue-group-profile(QGroupProf1)>queue-block(0/1)$ exit
mp4100>config>qos>queue-group-profile(QGroupProf1)$ info detail
queue-block 1/1
exit
queue-block 0/1
profile "QBlockProf1"
shaper profile "Shap2"
exit
queue-block 0/2
shaper profile "Shaper1"
exit
WRED Profiles
87B
The WRED mechanism defines the probability of dropping yellow packets

depending on the current queue usage. This avoids traffic congestion and
ensures the forwarding of green packets. You can configure the following:
• Minimum threshold – Defines the queue usage at which the WRED
mechanism starts to drop yellow packets
• Maximum threshold – Defines the queue usage above which the WRED
mechanism drops all yellow packets
• Probability –Determines the percentage of packets to be dropped when the
queue usage reaches the maximum threshold
There are eight WRED profiles available, named WREDProfile0 through
WREDProfile7. They are bound to the queues automatically: WREDProfile0 is
bound to queue 0, WREDProfile1 is bound to queue 1, etc. You cannot delete the
WRED profiles, and you cannot add more WRED profiles. The binding of the
profiles to the queues is set and cannot be changed, but you can change the
profile parameters. You can view the assignment of WRED profiles to queues via
the info command in the queue block profile level.
Note The WRED mechanism is activated only when you use a policer profile with EIR set
to a nonzero value.
Factory Defaults
17B
There are eight WRED profiles available, named WREDProfile0 through

WREDProfile7, bound to the corresponding queues.

Configuring WRED Profiles
 To configure WRED profiles:

1. Navigate to configure qos and type wred-profile WREDProfile<n> where n is 0
through 7.
The config>qos>wred-profile(WREDProfile<n>)# prompt is displayed.
2. Enter:
color yellow min <min-threshold> max <max-threshold> [probability
<max-probability>]
 min-threshold –Queue usage minimum threshold in percentage, 0–100
 max-threshold –Queue usage maximum threshold in percentage, 0–100
 max-probability – Percentage of packets to be dropped when the queue
usage reaches the maximimum limit.
Note You can configure the parameters for the color yellow only.
Example
 To configure WRED profile 4:

• Minimum threshold 64
• Maximum threshold 100
• Probability 50.
mp4100# configure qos wred-profile WREDProfile4
mp4100>config>qos>wred-profile(WREDProfile4)# color yellow min 64 max 100
probability 50
mp4100>config>qos>wred-profile(WREDProfile4)# info detail
color yellow min 64 max 100 probability 50
mp4100>config>qos>wred-profile(WREDProfile4)#


Chapter 9
Timing and
Synchronization
9.1 Clock Selection

Megaplex-4 flexible timing options enable reliable distribution of timing together
with flexible selections of timing sources, including support for an external station
clock interface that enables daisy-chaining the clock signals to other equipment.
Megaplex-4 also provides traceable timing quality and supports automatic
selection of best-quality timing reference.
Standards
The CSM module complies with the ITU-T G.781 standard.
Megaplex-4 supports one clock domain with up to 10 clock sources. The timing
subsystem automatically selects the best timing source to use for
synchronization.
The user can define the following clock sources:
• Recovered from the STM-1/STM-4/OC-3/OC-12 interface, including automatic
selection based on SSM (Synchronization Status Messaging)
• Recovered from the GbE interface (CL modules only), including automatic
selection based on ESMC (Ethernet Synchronization Messaging Channel)
• Internal crystal free-running oscillator-based clock
• Clock derived from the receive clock of a specified module user port
• Adaptive clock recovered from a pseudowire circuit (ACR)
• External station clock.
Multiple clock sources can be set and assigned a corresponding clock source
quality and priority.
If SDH/SONET, GbE or station clock sources are configured as SSM-based, their
quality can be determined by monitoring the synchronization status messages.
Clock Synchronization
20B
The synchronization network type identifies the type of synchronization network

connections and the synchronization level. Each synchronization network
Megaplex-4 Clock Selection 9-1

Chapter 9 Timing and Synchronization Installation and Operation Manual
connection is provided by one or more synchronization link connections, each link

connection supported by an SDH multiplex section trail.
The synchronization network types are:
1. Option I (Europe, Table 9-1)
2. Option II (USA, Table 9-2).
You can define the timing quality level of the source, or work without quality
level. The supported quality levels are according to the synchronization network
type, as shown in the following tables. The quality levels are shown in order of
highest quality level to lowest quality level.
Table 9-1. Option I Quality Levels
Quality Description Rank

Level
PRC Timing source is Primary Reference Clock as defined in Recommendation Highest

G.811
SSU-A Timing source is Type I or V Synchronization Supply Unit (SSU) clock as

defined in Recommendation G.812
SSU-B Timing source is Type VI Synchronization Supply Unit (SSU)clock as defined

in Recommendation G.812
SEC Timing source is Synchronous Equipment Clock as defined in

Recommendation G.813 or G.8262, Option I
DNU Do Not Use – This signal should not be used for synchronization Lowest
Table 9-2. Option II Quality Levels

Level
PRS Timing source is Primary Reference Source clock as defined in Highest

Recommendation G.811
STU Synchronization Traceability Unknown – Timing signal does not carry a

quality level indication of the source
ST2 Timing source is Stratum 2 clock as defined in Recommendation G.812,

Type II
TNC Timing source is Transit Node Clock as defined in Recommendation G.812,

Type V
ST3E Timing source is Stratum 3E clock as defined in Recommendation G.812,

Type III
ST3 Timing source is Stratum 3 clock as defined in Recommendation G.812,

Type IV
SMC Timing source is SONET/Ethernet self-timed clock as defined in

Recommendation G.813 or G.8262, Option II
ST4 Timing source is Stratum 4 free-running clock (applicable only to 1.5

Mbit/s signals)
9-2 Clock Selection Megaplex-4

Installation and Operation Manual Chapter 9 Timing and Synchronization

Level
PROV Provisionable by the network operator
DUS Don't Use for Sync – This signal should not be used for synchronization Lowest
System Timing Modes

The Megaplex-4 timing subsystem can use the following types of reference
sources:
• Internal Megaplex-4 oscillator
• Clock signal derived from the E1/T1 receive clock (Rx timing mode),
SDH/SONET port, GbE port located on CL module, or pseudowire
• Station clock, a special case of Rx timing, which uses an external clock signal
supplied to the CL module CLOCK connector.
Note Although GbE ports of M-ETH modules cannot serve as a reference source (Rx
clock), they can distribute the clock transparently throughout the system. This
feature requires a special ordering option (refer to M-ETH data sheet).
Table 9-3 lists the reference clock sources that can be configured, together with
the types of Megaplex-4 modules that can provide a timing reference signal.
For each module, the table also lists the type of ports and, when applicable, the
operating mode that must be selected for a port to provide a timing reference
signal.
Table 9-3. Clock Reference Sources
Source Type Module Type Selectable Ports Specific Operating Mode
Internal Not applicable Not applicable Not applicable
Station (external) CL.2 Station clock Not applicable

Source Type Module Type Selectable Ports Specific Operating Mode
M8E1, M16E1, External E1 or T1 ports Not applicable

M8T1, M16T1
VS-16E1T1-EoP
VS-6/E1T1 External E1 or T1 ports Not applicable

VS-16E1T1-PW Pseudowire recovered
clock
RX Clock from
MPW-1 Pseudowire recovered Not for HDLC pseudowires
Local User Port
clock
SH-16 Internal E1 ports SH-16/E1, STU-R module

only
Pseudowire recovered SH-16/E1/PW

clock
OP-108C/OP-34C Internal E1 ports Not applicable

ASMi-54C/N STU-R module only
T3 External T3 ports Not applicable

Internal T1 ports CL modules without
SDH/SONET ports
Line (STM-1/OC-3/STM-4/OC- CL.2 Link port Not applicable

12) Signal from SDH/SONET
Subsystem
Sync-E clock from GbE ports CL.2 (HW Ver 1.0 and GbE port Not applicable
on CL modules higher)
A timing source is defined by specifying the slot and the port to be used. The
source slot can be any I/O slot with a module having ports capable of recovering
a clock signal, or a CL slot.
Internal Timing Mode

In most Megaplex-4 applications, an external clock source is used. The internal
oscillator is used as a last recourse timing source: it is automatically selected
when no source is capable of providing a good timing reference.
Rx Timing Mode
In the Rx timing mode, the reference signal is derived from the receive (RX) clock
of a specified user port, or a clock recovered from a user-specified pseudowire:
• Megaplex-4 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 9-3.
• For Megaplex-4 equipped with MPW-1, SH-16/E1/PW, VS-6/E1T1 or
VS-16/E1T1/PW modules, it is also possible to configure certain pseudowires
to provide recovered clock signals to serve as timing references. Any type of
pseudowires, except HDLC, can provide recovered clock signals.

The algorithm that selects the Megaplex-4 timing reference source is based on
the user-defined priorities, and works to automatically select the operational port
as the nodal timing reference: first according to the highest quality, and then
according to the highest priority. If the quality level is not selected, Megaplex-4
selects the operational port with the highest available priority from the source
list.
If no operational port can be found in the source list, the Megaplex-4 switches to
the holdover mode. In this mode, the timing subsystem selects the frequency
used 26 msec before the fault condition that caused the switching to the next
clock source mode (this is assumed to be a safe selection, at which the
subsystem operated normally at the correct frequency). This frequency is
maintained until one of the user-specified sources can again be selected as a
reference. If time limit expires without any of the user-specified clock sources
returning to normal, Megaplex-4 switches to the internal oscillator.
Station Timing
When the station timing mode is used as one of the 10 clock sources, the
Megaplex-4 system (nodal) timing is synchronized to an external clock signal
delivered to the dedicated station clock interface located on each CL module. This
signal is usually provided by a highly-accurate clock source, configured with the
highest priority, which is often available in communication facilities (for example,
a signal provided by a GPS-based timing source, an independent primary clock
source, clock signals provided by an SDH/SONET ADM, or other suitable clock
source). The clock signal frequency is user-selectable: 2.048 MHz, 2048 Mbps, or
1.544 Mbps.
The station clock quality can be set by the user.
Each CL module can be connected to a separate station clock source, so that
both station ports can serve as a clock source.
The station clock has software-selectable interfaces:
• ITU-T Rec. G.703 interface. The clock interface (balanced/unbalanced) and
sensitivity (long or short range) are also user-selectable
• RS-422 interface for squarewave signals, which is the recommended interface
when timing quality is critical. Note that this interface is suitable for short
cable runs, interconnecting equipment units located in close proximity.
The station clock interface also provides an output clock signal, for chaining
applications. The source of the output clock is selectable:
• The external clock signal applied to the station clock interface.
• The external clock signal, after regeneration and filtering by a jitter
attenuator
When using the internal clock as the system timing reference, the transmitted SSM
message is SEC (SDH) or SMC (SONET).
Clock Domain
Clock Mode
The domain clock mode can be one of the following:

• Auto mode – domain timing is determined by the clock selection algorithm

(default)
• Free-run mode – the domain clock is based on the main card local oscillator
Notes • Quality in free-run mode is SEC/SMC.

• By default, Megaplex-4 uses free-run mode, until a valid clock source is
selected.
mp4100>config>system>clock>domain(1)# show status

System Clock Source : 2 State : Locked Quality : PRC
Force Switch : Inactive
Manual Switch : Inactive
Clock Domain States

Clock domain states indicate operation modes of the system clock (T0 timing
generator).
System clock:
• Locked – Locked to selected clock source
• Free-run – Locked to internal oscillator
• Holdover – Input lock is lost, the clock mechanism uses data stored during
normal operation for timing output.
Note By default, the Megaplex-4 system clock is in free-run state, until a valid clock
source is selected.
External Switch Commands

You can issue manual or forced switch commands to choose a specific clock
source. The manual command overrides the clock priority setting and allows
selection of a clock with a priority lower than an automatically selected clock
source. Both clock sources must have the same quality level.
The forced switch command allows selection of any clock source, regardless of its
priority or quality level. It overrides the previously issued manual switch
command.
The manual and forced switch commands are cleared using the clear command.
Factory Defaults
The table below lists the parameter defaults for the Clock Domain, Clock Source
and Station Clock configuration.
domain
sync-network-type 1

quality sdh-sonet: ssm-based

other ports, Type 1: dnu
other ports, Type 2: dus
mode auto
clock-source
priority 10
wait-to-restore 300 (s)
hold-off 300 (ms)
station
tx-clock-source system
interface-type e1, balanced
line-code hdb3
recovered
network-type type-b
Configuring the Clock Domain

 To configure the clock domain:
1. Navigate to configure system clock domain 1.
The config>system>clock>domain(1)# prompt is displayed.
Setting sync-network-type {1 | 2} Type 1 – Europe

synchronization Type 2 – USA
network type
When you change the synchronization network
type, you must redefine the clock sources.
Setting quality of quality Typing no quality removes the quality parameter. If

clock no quality is defined for the domain you cannot
configure quality level for the sources.
The quality value is PRC for Type 1 and PRS for
Type 2
Setting clock mode mode {auto | free-run} auto –Clock selection mechanism functions
normally, e.g. the best available clock source is
selected for synchronization
free-run – Internal oscillator is used for
synchronization

Forcing selection of a force <source-id> The range of source-id is 1 to 10.

particular clock
source when the
sources have
different quality
levels
Manually selecting a manual <source-id> The selection is performed in the following

particular clock conditions:
source • No quality is defined for the clock domain
• The sources have the same qualities
• The sources have different priorities.
Canceling previously clear

issued force or
manual command
Adding clock source source <src-id> rx-port {e1| t1 Refer to Configuring the Clock Sources
| e1-i | ds1-opt | sdh-sonet |
ethernet } <slot><port>
source <src-id> station
<slot>/1
source <src-id> recovered
<recovered-id >
Configuring clock source <src-id> Typing no source <src-id> deletes the source
source Refer to Configuring the Clock Sources
Displaying the Clock Domain Status

7B
 To view the clock domain status:

• At the system>clock>domain(1)#, enter show status.
The clock source status is displayed.
The possible clock states are explained in the following table.
Displayed
Free Run Indicates that the nodal timing system is locked to the internal oscillator
Note: When using the internal clock as the system timing reference, the transmitted
SSM message is SEC (SDH) or SMC (SONET).

Displayed
Holdover Indicates whether the nodal timing system is in the holdover state (yes) or not (no).
The nodal timing system enters the holdover state when all the configured sources
fail. In the holdover mode, the clock maintains the incoming reference frequency at
the last value acquired before the failure. This situation persists until at least one of
the configured sources returns to normal operation, and thus is selected again as
reference.
Note 1: This field is not relevant for “DS0 only” CL option. In this case after clock
source failure, the next available clock source is selected. If no valid clock source is
available, the Megaplex internal clock is used as a clock source.
Note 2: The transmitted quality level is SEC (SDH) or SMC (SONET).
Locked Indicates that the nodal timeing is locked on one of the clock references.
Example 1: Megaplex-4 domain is locked to Source 2, with PRC quality.

System Clock Source : 2 State : Locked Quality : PRC
Example 2: The nodal timing system entered the holdover state after all the
configured sources failed.
System Clock Source : 0 State : Holdover Quality : SEC
Example 3: Clock Domain Mode is configured to “free-run” and no clock selection

is performed.
System Clock Source : 0 State : Freerun Quality : SEC
Configuring the Clock Sources

You can define up to 10 clock sources for the domain. The sources can be:
• GbE port on CL module
• SDH/SONET port
• Station clock
• E1/T1 ports on I/O modules
• Recovered clock from a PW.
 To add a clock source:

1. Verify that the clock source to be used as an input is valid.

Note You can choose an invalid clock source. However, this input will be rejected by
the domain during the clock selection process.
2. Verify that the card whose port will be used as a source clock is provisioned.
3. Verify that the port to be used as a source clock is enabled (no shutdown).
5. Type one of the following, according to the required clock source:
source <src-id> rx-port ethernet <slot>/<port>
source <src-id> rx-port e1 <slot>/<port>
source <src-id> rx-port t1 <slot>/<port>
source <src-id> rx-port sdh-sonet <slot>/<port>
source <src-id> rx-port <slot>/<port>
source <src-id> rx-port ds1-opt <slot>/<port>
source <src-id> rx-port e1-i <slot>/<port>
source <src-id> station <slot>/1
source <src-id> recovered <recovered-id>
no source
Note 1 Recovered ID range is 1 to 99.
Note 2 For Ethernet clock source, to ensure correct distribution of ESMC traffic, you must
configure a flow with an L2CP profile with peer action on the 01-80-c2-00-00-02
address. The flow must have the following attributes:
• Untagged classification
• Ingress port – Ethernet port/LAG, serving as the ESMC source (Sync-E port)
• Egress port – according to application requirements.
If you use the flow only to peer the SSM frames and do not need to forward the
untagged traffic, discard it, using the drop command on the flow.
The clock source is created and the

config>system>clock>domain(1)>source(<1–10>)# prompt is displayed.
6. Enter all necessary commands according to the tasks listed below the
following procedure.
 To configure a clock source for which the port has been defined:
2. Type source <1–10> to select the source to configure.
The config>system>clock>domain(1)>source(<1–10>)# prompt is
displayed.

Setting priority priority <1–10> Priority 1 is the highest.
Setting quality level For Type 1: quality-level If no quality is defined for the domain, this
{prc | ssu-a | ssu-b | sec | command is not available
dnu | ssm-based} The quality level ssm-based indicates that the
For Type 2: quality-level { quality level is based on SSM messages and is
prs | stu | st2 | tnc | st3e | not available on DS0 only CL.2 modules
st3 | smc | st4 | dus | Using no quality cancels the quality hierarchy
ssm-based | prov } and the clock becomes priority-based only
Defining the time that a wait-to-restore <0–720> The time is defined in seconds.
previously failed
synchronization source must
be fault-free in order to be
considered available
Defining the time that hold-off <300–1800> The time is defined in milliseconds.
signal failure must be active
before it is transmitted
Canceling the clear-wait-to-restore This option is useful if a timing source fault is

wait-to-restore timer of a cleared and you want to souce to be
clock source immediately available.
Displaying the Clock Source Status

9B
 To view the clock source status:

• At the system>clock> domain(1)>source(<1–10>)#, enter show status.
The clock source status is displayed.
mp4100>config>system>clock>domain(1)>source(1)# show status
Status : Physical Fail
Tx Quality : DNU
Rx Quality : PRC
ESMC State : Unlocked
WTR State : Running
The clock status provides information about:
 Clock source status:
 OK – The clock source is valid and can be considered as clock input
candidate for the system clock
 Physical Fail – Clock failure has been detected at the physical level
 Monitoring Fail – Clock failure has been detected by the clock
monitoring entity of the domain. One reason for declaring a
monitoring failure state is that the maximum frequency deviation of
the clock source has been exceeded.
 ESMC Fail – Ethernet port with ESMC-based clock has not received a
SSM-packet stream for 5 seconds. Make sure the Ethernet port has

been configured to supply ESMC and a dedicated flow has been

directed to the port.
 Tx quality – Transmit clock quality
 Rx quality – Receive clock quality
 ESMC State – State of the Ethernet Synchronization Messaging Channel
(ESMC)
 WTR State – Wait-to-restore counter status
 Running – WTR Timer is running (when the clock source returns after
signal failure (SF), WTR timer is used to verify that the clock source
stable state is not intermittent)
 Inactive – WTR Timer is inactive (clock source status is OK).
Displaying Clock Source Statistics

You can display the Ethernet Synchronization Messaging Channel (ESMC) statistics
for the clock sources. ESMC is used as a transport layer for SSMs in Sync-E. The
ESMC statistic counters are available for CL GbE ports only.
 To display the ESMC statistics for a clock source:

1. Navigate to configure system clock domain 1 source <src-id>.
config>system>clock>domain(1)>source(<src-id>)#.
2. Enter show statistics.
The ESMC statistics are displayed.
mp4100>config>system>clock>domain(1)>source(1)#
mp4100>config>system>clock>domain(1)>source(1)# show statistics
ESMC Failure Counter : 1
Rx Tx
ESMC Events : 0 1
ESMC Information : 0 29
 ESMC Events – Number of changed quality level messages sent and
received
 ESMC Information – Number of quality level information messages sent
and received.
Configuring the Station Clock

The station clock is an E1/2MHz or T1/1.5MHz port that can be used for
synchronization. You can set the station clock timing to be based on the system
clock or recovered from the received signal of the station clock (with or without
jitter attenuator).
 To configure the station clock:

1. Navigate to configure system clock station <slot>/1 (<slot> is cl-a or cl-b).
The config>system>clock>station(<slot>/1)# prompt is displayed.

Selecting the source of the tx-clock-source {system | station- system – The output (transmit) clock is
clock output signal provided rclk-plus-ja} derived from the Megaplex-4 nodal
in the station clock timing
connector, for connection to station rclk after ja – The external clock
other equipment signal applied to the station clock
receive input is regenerated and filtered
by a jitter attenuator, before being
returned through the transmit output
Selecting the rate and type interface-type {e1 | 2mhz | t1} e1 – 2.048 Mbps signal per ITU-T Rec.
of signal accepted and G.703 Para. 9
transmitted via the station 2mhz – 2.048 MHz signal per ITU-T Rec.
clock port G.703 Para. 13
t1 –1.544 Mbps signal per ITU-T Rec.
G.703 Para. 5.
Selecting the impedance of impedance {balanced | unbalanced} For e1 and 2mhz options only. If you
signal accepted and specify e1 or 2mhz and do not specify
transmitted via the station balanced or unbalanced, by default the
clock port interface is set as balanced
Setting line code line-code {b8zs | ami | hdb3} hdb3 –High Density Bipolar coding of
order 3, used for e1 and 2mhz options
ami –Alternate Mark Inversion coding,
used for t1 and 1.5mhz options
b8zs – Binary-8 zero suppression
coding, used for t1 and 1.5mhz options
Specifying E1 framing mode line-type { g732n | g732n-crc | This command is not available when
unframed} CL.2 type is DS0 (ignore an AIS alarm
that appears in the remote equipment).
Specifying T1 framing mode line-type { sf | esf| unframed} This command is not available when
CL.2 type is DS0 (ignore an AIS alarm
that appears in the remote equipment).
Setting receiver sensitivity rx-sensitivity {short-haul | short-haul – maximum allowable

to adjust the signal long-haul} attenuation of 10 dB, relative to the
capability to reach nominal transmit level
destinations close by or long-haul – maximum allowable
farther away attenuation of 34 dB, relative to the
nominal transmit level
Enabling SSM transmission tx-ssm Using no tx-ssm disables SSM

transmission
This command is not available when
CL.2 type is DS0
Specifying bits in TS0 for ssm-channel { sa4 | sa5 | sa6 | sa7 This command is not available when
transfering clock quality via | sa8 } CL.2 type is DS0
SSM (E1 only)

Administratively enabling no shutdown Using shutdown disables the station

station clock clock
Displaying the Station Clock Status

 To view the station clock status:
• At the system>clock>recovered (<slot><1>)# prompt, enter show status.
The station clock status is displayed.
mp4100>config>system>clock>station(cl-a/1)# show status
Name : CL-A station 01
Administrative Status : Down
Operational Status : Down
Configuring the Recovered Clock

Pseudowires of all types, except HDLCoPSN, can be selected as timing sources for
the Megaplex-4 nodal timing subsystem. This timing mode is called adaptive clock
recovery and is supported by MPW-1, SH-16/E1/PW, VS-16E1T1-PW and
VS-6/E1T1 modules.
 To configure the recovered clock:

1. Navigate to configure system clock recovered <ID 1..99>.
The config>system>clock>recovered (<ID>)# prompt is displayed.
Associating the PW number pw <PW number> The possible PW number range is 1 to 640.
to recovered clock
type-a – Switch-based network, for example,

Specifies the type of packet
an MPLS/ETH network
switched network used to network-type {type-a | type-b}
type-b – Router-based network, for example,
transport the pseudowire
an UDP/IP network
Administratively enabling no shutdown Using shutdown disables the recovered clock

recovered clock
Displaying the Recovered Clock Status

You can display the recovered clock status and the current status of the
pseudowire adaptive clock recovery mechanism.
 To view the recovered clock status and pseudowire adaptive clock recovery
mechanism state:
• At the system>clock>recovered (<PW number)# prompt, enter show status.

The recovered clock status is displayed.

mp4100>config>system>clock>recovered(1)# show status
Clock State : Frequency Acquisition
The possible clock states are explained in the following table.
Displayed
Holdover Indicates whether the nodal timing subsystem is in the holdover state (yes) or not
(no).
The nodal timing system enters the holdover state when all the configured sources
fail or during clock switching. In the holdover mode, the clock maintains the
incoming reference frequency at the last value acquired before the failure. This
situation persists until at least one of the configured sources returns to normal
operation, and thus is selected again as reference.
Note 1: This field is not relevant for “DS0 only” CL option.
Note 2: The transmitted quality level is SEC (SDH) or SMC (SONET).
Frequency Indicates that the clock recovery mechanism is learning the frequency of the
Acquisition selected reference.
Rapid Phase Lock Indicates that the clock recovery mechanism is in the training process
Fine Phase Lock Indicates that the clock recovery mechanism successfully completed the training
process, and is now locked. At this stage, the clock recovery mechanism provides a
stable clock of good quality.
Not Applicable The adaptive clock recovery status is not relevant.
You can also display the number of the PW the recovered clock is locked to, and
the network type by means of the following command.
 To display the network type and the PW number:

mp4100>config>system>clock>recovered(1)# info detail
pw 1
network-type type-b
no shutdown
Specifying the system time time <hh:mm[:ss]> Seconds are optional.

It is recommended to set the
time about one minute beyond
the desired time, and then
save at the correct instant.
detected.

Table 9-4. Clock Sanity Messages
110 Error ILLEGAL CLOCK SOURCE The selected clock source is invalid for one of the
following reasons:
• The configured module port cannot supply a
reference clock
• The T1 ports of T3 modules can serve as a clock
source only when working with CL modules that do
not have SDH/SONET ports.
112 Error CLOCK SOURCE IS IN When configuring the clock source to be locked to the
SHUTDOWN STATE receive clock of a module/channel, the source
module/channel must be connected
114 Error CLOCK SOURCE CAN'T BE Unframed (transparent) E1/T1 ports from M16E1/16T1,
UNFRAMED ASMi-54C/N, or OP modules cannot serve as clock source
(only M8E1/M8T1 ports can)
115 Error RECOVERED CLOCK - PW DOES You are trying to configure a recovered clock source but
NOT EXIST the PW associated to it does not exist.
116 Error DOMAIN NET TYPE DOES NOT Domain network type 1 and 2 must match sdh and sonet
MATCH SDH/SONET frame-type, respectively.
9.2 Date and Time

You can set the date and time for the Megaplex-4 internal real-time clock.
Note The internal real-time clock is used to time-stamp various messages, alarms, etc.
The previously attached time stamps are not changed when the time-of-day is
changed as a result of updates.
Setting the Date and Time

You can set the date and time for the Megaplex-4 internal real-time clock.
 To specify the system date and time:

1. At the config>system# prompt, enter date-and-time.
The config>system>date-time# prompt appears.
2. Specify the date and time and associated parameters as illustrated and
explained below.
Specifying the system date date <selected format> Default: yyyy-mm-dd
9-16 Date and Time Megaplex-4

Selecting the date format date-format {yyyy-mm-dd | dd-mm- yyyy-mm-dd – ISO format
yyyy | mm-dd-yyyy | yyyy-dd-mm} dd-mm-yyyy – European
format
mm-dd-yyyy – US format
yyyy-dd-mm – Japanese format
dd stands for day, mm for
month and yyyy for year
Example
 To define dd-mm-yyyy as a date format:
mp4100>config>system>date-and-time# date-format dd-mm-yyyy
 To define January 2, 2011 as the Megaplex-4 date:

mp4100>config>system>date-and-time# date 02-01-2011
 To define 18:23 as the Megaplex-4 time:

mp4100>config>system>date-and-time# time 18:23
Displaying the Date and Time

 To view the date and time settings:
• At the config>system# prompt, enter show date-and-time.
The date, time and the time zone are displayed.
mp4100>config>system# show date-and-time
2011-03-04 19:52:23
Working with SNTP

This section explains how to receive the clock signal from NTP servers in the
network. Megaplex-4 can synchronize with up to ten servers, sending NTP
requests to the servers at user-defined intervals.
You can set one of the active SNTP servers as the preferred server, so that
Megaplex-4 sends NTP requests to the preferred server. If there is no preferred
server or if the preferred server does not answer, then Megaplex-4 sends NTP
requests to any enabled servers.
Factory Defaults
The default configuration of the SNTP parameters is:
• No SNTP servers defined
• Polling interval set to 15 minutes.
When an SNTP server is defined, its default configuration is:
• IP address set to 0.0.0.0
Megaplex-4 Date and Time 9-17

• Not preferred
• Administratively disabled (shutdown).
Configuring SNTP Parameters

 To configure SNTP parameters:
1. Navigate to configure system date-and-time sntp.
The config>system>date-time>sntp# prompt is displayed.
Enabling Megaplex-4 to listen to broadcast Type no broadcast to disable

NTP broadcast messages to broadcast mode
obtain accurate timestamps
Setting polling interval (in poll-interval interval <minutes> Allowed range is 1–1440
minutes) for SNTP requests
Defining and configuring SNTP server <server-id>

servers (see Defining SNTP
Servers and Configuring SNTP
Server Parameters)
Displaying SNTP status show status
Defining SNTP Servers

 To define an SNTP server:
1. Navigate to config system date-and-time sntp.
2. Type server <server-id> to define an SNTP server with ID <server-id>.
config>system>date-time>sntp>server(<server-id>)$. The SNTP server
parameters are configured by default as described in Factory Default.
3. Configure the SNTP server parameters as needed, as described in Configuring
SNTP Server Parameters.
Configuring SNTP Server Parameters

 To configure SNTP server parameters:
1. Navigate to config system date-and-time sntp.
2. Type server <server-id> to select the SNTP server to configure.
config>system>date-time>sntp>server(<server-id>)#

Setting the IP address of the address <IP-address>

server
Set SNTP server as preferred prefer Type no prefer to remove

server. preference
Note: Only one server can be
preferred.
Setting UDP port for NTP udp port <udp-port> Allowed range is 1–65535
requests, to a specific UDP port udp default
or to default UDP port (123)
Administratively enabling server no shutdown Using shutdown disables the

server
Sending query to server and query-server

displaying result
Example
 To define SNTP server:

• Server ID = 1
• IP address = 172.17.155.126
• Administratively enabled.
mp4100# configure system date-and-time sntp
mp4100>config>system>date-time>sntp# server 1
mp4100>config>system>date-time>sntp>server(1)# address 172.17.155.226
mp4100>config>system>date-time>sntp>server(1)# no shutdown
mp4100>config>system>date-time>sntp>server(1)# commit
Result : OK
 To display server information:

mp4100>config>system>date-time>sntp>server(1)$ query-server
Query Server Reply

--------------------------------------------------------------
Server : 172.17.155.226 UDP : 123
Date : 11-04-2013 Time(UTC) : 07:13:54
Stratum : 4
mp4100>config>system>date-time>sntp>server(1)# exit
mp4100>config>system>date-time>sntp# show status
System Uptime : 000 Days 02:24:59

System Time (Local) : 2013-04-11 07:18:07
Current Source : 172.17.155.226
NTP Server UDP Port Tstamp DateTime Stratum Received

---------------------------------------------------------------------------
172.17.155.226 Enable 123 11-04-2013 07:14:00 4 000Days00:04:07
Megaplex-4 Date and Time 9-19


Chapter 10
Administration
This chapter covers administrative tasks such as entering contact info, file
management, etc. In addition, this section instructs you on resetting the unit.
10.1 Administrative Information

The Megaplex-4 management software allows you to assign a name to the unit,
add its description, specify its location to distinguish it from the other devices
installed in your system, and assign a contact person.
 To configure device information:

1. Navigate to configure system.
The config>system# prompt is displayed.
Assigning device name name <device-name> The length of the device name is unlimited, but if
you enter a name containing more than
20 characters, the prompt displays only the first
20 characters followed by 0.
For example, this command that defines a
25-character device name:
mp4100# config sys name
Megaplex_NYC_Building_1 results in this prompt
that shows the first 20 characters, followed by 0:
Megaplex_NYC_Build0#
no name removes user-assigned device name
Specifying location location no location removes user-assigned location

<device-location>
Specifying contact person contact <contact-person> no contact removes user-assigned contact

information
Displaying device show device-information

information, MAC
address, and amount of
time the device has been
running
Note
For configuring the system clock and date&time, refer to Chapter 9.
Megaplex-4 Administrative Information 10-1

Chapter 10 Administration Installation and Operation Manual
 To display device information:

• At the config>system# prompt, enter show device-information.
For example:
mp4100# configure system
mp4100>config>system# name mp4100
mp4100>config>system# location floor-8
mp4100>config>system# contact Engineer-1
mp4100>config>system# show device-information

Description : MP-4100, HW: 0, SW: 4.0
Name : mp4100
Location : floor-8
Contact : Engineer-1
MAC Address : 00-20-D2-51-62-5A
System Up Time : 000 Days 00:22:06
10.2 MAC Address Allocation

Each Megaplex-4 CL module has 18 unique MAC addresses to be assigned to its
ports. Each of the following ports is assigned a different MAC address:
• Two CL GbE ports (the 1st MAC address is assigned to GBE port 1, the 2nd
MAC address – to GBE port 2)
• 16 Logical MAC ports bound to first 16 VCG ports (in the order of their
creation): MAC addresses 3-18 are assigned to VCGs 1-16.
Logical MACs bound to VCGs 17-32 inherit their MAC address from the CL on
which they are defined.
The MAC clients in the device (e.g. router interfaces, MEPs, etc., inherit their MAC
addresses from the relevant port).
You can view the MAC address assigned to an Ethernet or Logical MAC port via
show status command (see corresponding section in Chapter 6). For information
on which MAC address is used by a particular feature, refer to the relevant
section in this manual.
You can display the number of MAC addresses and the first MAC address defined
on a specific chassis slot as follows.
 To display MAC addresses defined on the slot:

• At the config>chassis# prompt, enter show manufacture-info slot
<slot_number> to display information on items installed in a specific slot.
For example:
10-2 MAC Address Allocation Megaplex-4

Installation and Operation Manual Chapter 10 Administration
M-ETH module:
mp4100>config>chassis# show manufacture-info slot 7

First MAC Address : 00-01-C1-00-00-07
Number of MACs : 1
CL module:
mp4100>config>chassis# show manufacture-info slot cl-a

First MAC Address : 00-20-D2-F3-BC-D3
Number of MACs : 18
10.3 Managing the SONET/SDH Link Rate Selection

License
By default, the CL.2 modules are supplied with STM-1/OC-3 ports. To enable the
STM-4/OC-12 functionality, a software license key is required:
MP-4100-LIC/622SK for Megaplex-4100 and MP-4104-LIC/622SK for
Megaplex-4104. You can order it together with the product or later, when the
upgrade is needed. The license is based on the module MAC address and must be
ordered separately for each CL.2 module.
Once the license is downloaded, the SDH/SONET ports are software-configurable
to STM-4/OC-12 or STM-1/OC-3.
Checking the License Availability

If you do not know whether your device features the STM-4/OC-12 functionality,
type:
 To display the license availability:

1. Navigate to show configure system license.
If the STM-4/OC-12 functionality is enabled, the following screen is
displayed:
mp4100#
mp4100# show configure system license
Feature Status Slot File Name
---------------------------------------------------------------
STM-4/OC-12 Enable CL-A license-1
STM-4/OC-12 Enable CL-B license-3
mp4100#
If the STM-4/OC-12 functionality is disabled, the following screen is
displayed:
Megaplex-4 Managing the SONET/SDH Link Rate Selection License 10-3

mp4100#
mp4100# show configure system license
Feature Status Slot File Name
---------------------------------------------------------------
STM-4/OC-12 Disable CL-A N/A
STM-4/OC-12 Disable CL-B N/A
mp4100#
Ordering the license is described in the following section.
Ordering the License

In order to activate the STM-4/OC-12 functionality, the license file must be
downloaded and activated. Once purchased, the license is permanent and does
not expire.
The licenses are based on the CL.2 module MAC address and distributed as
software files named *.txt, for example LIC_0020D2500C48.txt. The files can be
obtained from the local RAD Partner from whom the device was purchased. Each
license is ordered per CL module.
 To display the MAC Address of CL-A/CL-B:

• Use configure>chassis>show manufacture-info command as illustrated in the
following example.
mp4100# configure
mp4100>config# chassis
mp4100>config>chassis#
mp4100>config>chassis# show manufacture-info slot cl-a
First MAC Address : 00-20-D2-50-0E-93
Number of MACs : 1
mp4100>config>chassis# show manufacture-info slot cl-b
First MAC Address : 00-20-D2-50-05-B0
Number of MACs : 1
You can also use the following syntax:
mp4100# show configure chassis manufacture-info slot cl-a
First MAC Address : 00-20-D2-50-0C-48
Number of MACs : 1
mp4100#
mp4100# show configure chassis manufacture-info slot cl-b
First MAC Address : 00-20-D2-50-05-B0
Number of MACs : 1
The “Number of MACs” field value in the case of Megaplex-4 is always “1”.
The software upgrade utility includes four partitions called license-1, license -2,
license -3, license -4 for downloading and storing the licenses.
You can download the license file to Megaplex-4 via CLI in either of two ways:
• TFTP when downloading over a network
• XMODEM when downloading over a dumb terminal connected to the
Megaplex-4 control port.
10-4 Managing the SONET/SDH Link Rate Selection License Megaplex-4

Downloading the License File Using TFTP

 To download the license file using TFTP:
1. Assign the IP address to the Megaplex-4 device as described in Configuring
the Router Interface section (Chapter 8).
2. Download the valid license obtained from RAD using file>copy command as
follows.
3. For example:
 Host IP (PC) address is 172.17.170.38.
 License file for CL-A is LIC_0020D2500C48.txt
 License file for CL-B is LIC_0020D25005B0.txt.
mp4100# file copy tftp://172.17.170.38/LIC_0020D2500C48.txt license-1
mp4100#
File copy command was completed.
tftp://172.17.170.38/LIC_0020D2500C48.txt copied to license-1 successfully
139 bytes copied in 2 secs (69 bytes/sec)
mp4100#
mp4100# file copy tftp://172.17.170.38/LIC_0020D25005B0.txt license-2
mp4100#
tftp://172.17.170.38/LIC_0020D25005B0.txt copied to license-2 successfully
4. Type “commit”.
Now the license file is downloaded to the device.
Downloading the License File Using XModem
 To download the License File using XMODEM:

1. Type the following command (in our example we are downloading the license
to license-4 partition):
mp4100>file# copy xmodem: license-4

mp4100>file#
*****The terminal will become disable !!!
Please send the file
*****
2. Using the terminal application, select the license file and click the send
button.
Megaplex-4 Managing the SONET/SDH Link Rate Selection License 10-5

*****
*****xmodem: copied to license-4 successfully*****

Now the license file is downloaded to the device.
Installing the License for Redundant CL Modules

If two redundant modules (CL-A and CL-B) are installed in the chassis, the license
must be installed in both CL modules.
To ensure this, proceed as follows:
1. Install both CL modules in the chassis.
2. Download the license file to CL-A (for example, to “license-1”).
3. Reset the CL-A module.
Now the CL-B module becomes active (working) and you can download
the license to it.
4. Download the license file to CL-B (for example, to “license-1”).
5. Reset the CL-B module.
Now the modules can operate at STM-4/OC-12 rates as a redundant pair.
10.4 Inventory
The Megaplex-4 inventory table displays the unit’s components, hardware,
software and firmware revisions. You can display an inventory table that shows
all installed components, and you can display more detailed information for each
component.
Standards and MIBs

The inventory feature is implemented according to RFC 4133 – Entity MIB
(RFC 2737 was made obsolete by RFC 4133 version 3).
Benefits
You can monitor the installed components and hardware/software revisions.
Displaying Inventory Information

The Megaplex-4 inventory table displays the unit’s components, hardware,
software and firmware revisions.
 To display the inventory table:

• In the config>chassis# prompt, enter show summary-inventory.
10-6 Inventory Megaplex-4

The inventory table is displayed (refer to Example to see a typical

inventory table output).
Displaying Inventory Component Information

You can display more information for each installed inventory component. To do
this, enter the inventory level with the corresponding inventory component index.
The component index is determined by the position of the corresponding row in
the output of show inventory-summary, which changes according to what is
installed in the unit.
 To display the inventory component information:

1. Navigate to configure chassis inventory <index>.
2. Enter show status.
Information for the corresponding inventory component is displayed
(refer to Table 10-1 for information on the parameters).
Table 10-1. Inventory Parameters

Description Description of component type
Contained In Index of the component that contains the component for which
information is being displayed.
Physical Class Class of component. Possible values: Stack,Chassis, Container, Module, Port
Relative Position Contains the relative position of this component in relation to other
component with the same “Contained In” value
Name Name of component
HW Rev Hardware revision
SW Rev Software revision
FW Rev Firmware revision
Serial No. Serial number (read-write field, can be edited by the user; it is recommended
to type here the number on the sticker that is attached to the component
when it leaves RAD)
MFG Name Manufacturer name (blank if unknown for component)
Model Name The component information: type, slot, port etc
Alias Alias name for component (read-write field, can be edited by the user)
Asset ID Identification information for component (read-write field, can be edited by

the user; it is recommended to type here the HW configuration letter CSL)
FRU Indicates whether this component is a field replaceable unit that can be
replaced on site (True/False)
Setting Administrative Inventory Information

13B
If necessary, you can configure the alias, asset ID, and serial number for
inventory components of I/O modules. To configure the information, you need to
enter the inventory level with the corresponding inventory component index as
Megaplex-4 Inventory 10-7

determined by the position of the corresponding row in the output of

show summary-inventory.
 To set inventory component information:

1. Navigate to configure chassis inventory <index>.
The config>chassis>inventory(<index>)# prompt is displayed.
Assigning user-defined alias to alias <string> no alias removes the alias.

component Configuring the alias is
meaningful only for the chassis
component. It can be used by a
network manager as a
non-volatile identifier for the
device.
Assigning user-specific asset identifier asset-id <id> no asset-id removes the asset
to the component (usually for ID
removable physical components)
Assigning vendor-specific serial serial-number <string> no serial-number removes the

number to the component serial number
Example
23B
 To display the following inventory information:

• Inventory table
• Inventory information for T1 port 1 of M8T1 module installed in I/O slot 1.
mp4104# configure chassis
mp4104>config>chassis# show summary-inventory
Index Physical Class Name HW Ver SW Ver FW
Ver
-----------------------------------------------------------------------------
1 Stack stack
2 Chassis chassis
101 Power Supply PS-A
103 Module CL A 0.0 4.10.07
105 Module IO Card-1
201 Container PS-A
202 Container PS-B
203 Container slot a
204 Container slot b
205 Container slot 1
3001 Port RS-232 Control Port CL-A
3002 Port MNG Ethernet CL-A/1
3003 Port Station Clock CL-A
5001 Port T1 IO-1/1
10-8 Inventory Megaplex-4

5002 Port T1 IO-1/2

5003 Port T1 IO-1/3
5004 Port T1 IO-1/4
5005 Port T1 IO-1/5
5006 Port T1 IO-1/6
5007 Port T1 IO-1/7
5008 Port T1 IO-1/8
5009 Port Ethernet IO-1/1
103004Container slot a port 1
mp4104>config>chassis# inventory 5001
mp4104>config>chassis>inventory(5001)# show status
Description : MP-4100.T1 IO-1/1
Contained In : 105
Physical Class : Port
Relative Position : 1
Name : T1 IO-1/1
HW Ver :
SW Ver :
FW Ver :
Serial Number :
MFG Name : RAD
Module Name : T1 IO-1/1
Alias : IO-1 t1 01
Asset ID :
FRU : False
mp4104>config>chassis>inventory(5001)#
10.5 File Operations

You can perform the following operations:
• Copy files within the Megaplex-4 unit
• Display files within the Megaplex-4 unit
• Delete files.
File Names in the Unit

Megaplex-4 uses the following reserved file names:
• factory-default – Contains the factory default settings
• running-config – Contains the current user configuration that is different
from the default configuration.
Megaplex-4 File Operations 10-9

• startup-config – Contains saved user configuration. You must save the file
startup-config; it is not automatically created. Refer to Saving the
Configuration for details on how to save the user configuration.
• user-default-config – Contains default user configuration. Refer to Saving the
Configuration for details on how to save the default user configuration.
• candidate – Stores any configuration before it is copied to running-config via
commit command.
• sw-pack-1, sw-pack-2, sw-pack-3, sw-pack-4 – Contains up to four software
images
• log –Contains alarm and event log (5000 alarms/events)
• mac-table – Contains the MAC address table (see Displaying MAC Address
Table in Chapter 8 for description)
You can copy files via the copy command, or via the commands shown in
Table 10-2.
Table 10-2. Commands That Copy Files
Command Level Copies… Manual Section
factory-default admin factory-default to candidate Resetting to Factory

(then use commit to copy factory-default Defaults
to running-config and then save to copy
it to startup-config)
user-default-config admin user-default-config to candidate Resetting to User

(then use commit to copy Defaults
user-default-config to running-config and
then save to copy it to startup-config)
save global running-config to startup-config Saving the Configuration
Copying Files within Megaplex-4

You can copy files within the Megaplex-4 unit with the copy command.
Figure 10-1 shows the commands that can copy configuration files in a visual
diagram.
10-10 File Operations Megaplex-4

Admin user-default
Sanity
check
Copy
Commit Copy
Configuration
User-Default -
Session Running-config Startup-Config Factory-Default
Config
(Candidate DB)
TFTP
TFTP
Save
Copy
Admin factory-default
Figure 10-1. Commands that Copy Configuration Files
 To copy files within the device:

• At the file# prompt, enter:
copy <source-file> <dest-file>.
Example 1:
• Source file name – running-config
• Destination file name – startup-config.
mp4100# file
mp4100>file# copy running-config startup-config
Example 2:
• Source file name – log
• Destination file name – LOG_oos1 on tftp://172.17.151.59.
mp4100>file# copy log tftp://172.17.151.59/LOG_oos1
mp4100>file#
*****
*****log copied to tftp://172.17.151.59/LOG_oos1

successfully*****
Note
Due to a large file volume, copying starts after 30 sec of processing .
 To display the last copy command result:

• At the file# prompt, enter: show copy.

mp4100# show file copy

Network to Device, Transferring Data
Src: tftp://172.17.174.56/mp4cl2_03_00b06.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Transferred : 665600 Bytes in: 16 seconds (41600 Bytes/Second)
 To view the copy command history:

• At the file# prompt, enter: show copy summary.
For example:
mp4100>file# show copy summary
Direction Source Destination End Time Status
1 Local running-config user-default-conf 13-3-2011 Ended OK
14:6:51
2 Local running-config startup-config 13-3-2011 Ended OK
14:7:35
3 Dev to Net startup-config DB 13-3-2011 Ended OK
14:7:40
Displaying Files within Megaplex-4

The dir command is used to display the files within the device.
 To display the files:

• At the file# prompt, enter dir.
A list of the file names and types is displayed.
For example:
HyQ_C>file# dir
Codes: C-Configuration S-Software L-License LO-Log O-Other
Name Type Size(Bytes) Creation Date Status
sw-pack-1 S 13439930
20-5-2014 valid
11:45:49
sw-pack-2 S 14052947 5-6-2014 valid
14:30:30
sw-pack-3 S 14025662 2-4-2014 valid
14:3:34
sw-pack-4 S 14056358 16-6-2014 File In Use
11:47:29
startup-config C 37268 21-5-2014 valid
11:37:1
user-default-config C 11983 2-3-2014 valid
10:18:24
factory-default-config C 680 1-1-1970 Read Only
0:0:9
running-config C -- 18-6-2014 Read Only
15:44:25
log LO -- 18-6-2014 Read Only
15:44:25
Total Bytes : 101367808 Free Bytes : 31295488

Deleting Files
You can delete files. Before deleting the file, make sure the file is not in use. For
additional information on configuration files and the consequences of deleting,
refer to Configuration Files and Loading Sequence in Chapter 3.
 To delete a file:
1. At the file# prompt, enter: delete <file-name>.
You are prompted to confirm the deletion.
For example:
mp4100# file
mp4100>file# delete sw-pack-1
File will be erased. Are you sure?? [yes/no] _yes
2. Confirm the deletion.
The unit reverts to the factory default.
Saving the Configuration

You must save your configuration if you wish to have it available, as it is not
saved automatically. You can save your configuration as outlined below.
Additional information on config files is available under Configuration Files in
Chapter 3.
 To save your current configuration in the startup-config file:

• At any level, enter save.
• At the file# prompt enter:
copy running-config startup-config.
Resetting Megaplex-4
Megaplex-4 supports the following types of reset:
• Reset to factory defaults
• Reset to user defaults
• Overall reset (restart, reboot) of the device.
Resetting to Factory Defaults
 To reset Megaplex-4 to factory defaults:

1. At the device prompt, enter admin.
The admin> prompt appears.
2. Enter factory-default.
A confirmation message is displayed:
Current configuration will be erased with factory default configuration.
Are you sure?? [yes/no]

3. Enter yes to confirm resetting to factory defaults.

The factory-default file is copied to the candidate file.
4. Enter commit to complete the operation.
The factory-default file via Candidate DB is copied to the running-config
file. Now at the device startup, the factory defaults are loaded.
Resetting to User Defaults
 To reset Megaplex-4 to user defaults:

1. At the device prompt, enter admin.
The admin> prompt appears.
2. Enter user-default.
Current configuration will be erased with user default configuration. Are
you sure?? [yes/no]
3. Enter yes to confirm resetting to user defaults.
The user-default-config file is copied to the candidate file.
4. Enter commit to complete the operation.
The user-default config file via Candidate DB is copied to the
running-config file. Now at the device startup, the user defaults are
loaded.
Rebooting the Megaplex-4 Chassis
 To reboot the chassis:

1. At the admin# prompt, enter the reboot command.
Chassis will reboot. Are you sure?? [yes/no]
2. Enter yes to confirm the reset.
The chassis restarts.
Note If at this moment the CL modules are in synchronization state, the reboot
request is denied and the following message is displayed: "Unprotected data,
main cards in sync process, please wait... " In this case try rebooting the chassis
later.
Rebooting the Module

Use the following procedure to reboot a module installed in a specified slot.
Note Resetting a module will temporarily disrupt services supported by that module.
 To reboot a module:
1. Navigate to configure slot <slot>.

The config>slot<slot># prompt is displayed.

2. Enter reset.
Card will reset. Are you sure?? [yes/no]
3. Enter yes to confirm the reset.
The module restarts.
Note When trying to reboot CL modules in synchronization state, the reboot request is
denied and the following message is displayed: "Unprotected data, main cards in
sync process, please wait... " In this case try rebooting the CL module later.
Downloading/Uploading Files
You can download or upload files to the Megaplex-4 unit via SFTP. The following
types of files can be uploaded or downloaded:
• startup-config
• user-default-config
• factory-default-config (upload only)
• log (upload only)
• sw-pack-1, -2, -3, -4
The maximum allowed values for SFTP parameters are:
• Username – 1 – 60 characters
• Password –1– 60 characters
• File name – 1–100 characters
• Port – 1–65535.
Caution Always wait until all main cards installed in the chassis are up and running before
executing any file operation commands.
The SFTP protocol is used to provide secure file transfers via the device’s
Ethernet interface. SFTP is a version of FTP that encrypts commands and data
transfers, keeping your data secure and your session private. For SFTP file
transfers, an SFTP server application must be installed on the local or remote
computer. SFTP file transfers use Port 22. You must check that the firewall you
are using on the server computer allows communication through this port.
A variety of third-party applications offer SFTP server software. For more
information, refer to the documentation of these applications.
Application file is
transferred to MP
Ethernet
PC with an Active
SFTP Server and MP-4100/4104
Application File
Figure 10-2. Downloading a Software Application File via SFTP

Example – Download via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – mp4100.bin
• Destination file name – sw-pack-1.
mp4100# file
mp4100>file# copy sftp://admin:1234@192.20.20.20/mp4100.bin sw-pack-1
Note
Destination file name can be only sw-pack-1, sw-pack-2, sw-pack-3 or sw-pack-4.
Example – Upload via SFTP

• SFTP server address – 192.20.20.20
• SFTP user name – admin
• SFTP password – 1234
• Source file name – startup-config
• Destination file name –db1conf.cfg
mp4100# file
mp4100>file# copy startup-config
sftp://admin:1234@192.20.20.20/db1conf.cfg
Note
The source file name can be one of the following: startup-config or user-default-
config.

Chapter 11
Monitoring and
Diagnostics
The Megaplex-4 monitoring and diagnostic functions can be used to identify
problems in the network incorporating Megaplex-4 units, test the proper
operation of each Megaplex-4 unit, and rapidly locate the cause of the fault –
within the Megaplex-4 itself, in its connections to the network or to user
equipment, or in another network component.
In addition to the general Megaplex-4 functions described in this chapter, you can
find information on the module-specific diagnostic functions in the Megaplex-4
I/O Modules Installation and Operation Manual.
The available functions include:
• Detection of configuration (sanity) errors
• Alarm and event collection, and reporting of relevant alarms
• Configuration error (sanity) messages
• Collection of performance monitoring data
• Ping test
• Diagnostic tests for checking transmission paths.
11.1 Detecting Problems

Problems can be detected on the hardware level, for example by running the
self-test and monitoring the LED behavior.
On the software level, you can follow statistical counters and events and errors
returned by the system.
Indicators
Megaplex-4 modules and the Megaplex-4 chassis itself have various status
indicators that can be used to identify problems.
Refer to Chapter 2 of this manual for details regarding the functions and
indications of each system indicator and to Chapter 3 of this manual for normal
indications after power-up. Also refer to Megaplex-4 I/O Modules Installation and
Operation Manual for details regarding the functions and indications of each
module indicator.
Megaplex-4 Detecting Problems 11-1

Chapter 11 Monitoring and Diagnostics Installation and Operation Manual
Alarms and Traps

Megaplex-4 generates various alarms that can be displayed at a supervision
terminal, and sends alarm traps to management stations so that operators can
identify problems.
Megaplex-4 maintains a cyclic event log file that stores up to 5000 time-stamped
events. This list can be sent to an external file and seen by means of any text
editor. For this procedure, see Copying Files within Megaplex-4 in Chapter 10.
In addition, up to 200 latest alarms/events are displayed on the Megaplex-4
screen in the form of a monitor log. This log is user-manageable: it can be
renewed, cleared or sorted, as described below.
Statistic Counters
Megaplex-4 collects statistics per physical and logical ports (see the list below)
for 15-minute intervals. This enables the network operator to monitor the
transmission performance, and thus the quality of service provided to users, as
well as identify transmission problems. Performance parameters for all the active
entities are continuously collected during equipment operation.
Statistics for the last 24 hours are stored in the device and can be retrieved at
the network management station.
Statistic counters provide information on possible abnormal behavior and failures.
You can display statistics of the following:
• RADIUS server
• Ethernet, SDH/SONET, E1/T1, SHDSL, VCG, PCS, GFP, HDLC and PW ports.
For further information, refer to the relevant sections in Chapter 4 and the
relevant sections in the troubleshooting chart.
Configuration Error Messages

Megaplex-4 includes an extensive subsystem that checks the validity of the user’s
configuration activities and reports any conflicts and errors. These error
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-4; for example, an installed module is not
programmed in the chassis.
Error Errors that prevent proper operation of the

Megaplex-4 in its intended application; for example, an
invalid timeslot assignment).
For further information, refer to the relevant sections in the configuration

chapters.
11-2 Detecting Problems Megaplex-4

Installation and Operation Manual Chapter 11 Monitoring and Diagnostics
11.2 Handling Events

Reported events can be events, traps and alarms. The difference between them
is as follows:
• Alarm. A message that reports a failure. An alarm is a persistent indication of
a fault of an entity, which may be the device itself or any of its components.
• Event. Any change of status in a managed object in the network. SNMP
equipment can generate traps for many different kinds of events, not all of
which are important for telemetry. The ability to filter unimportant events is
essential for high-quality SNMP alarm management. An event is something
that may be of interest, such as a fault, a change in status, crossing a
threshold, or an external input to the system.
• Trap. An SNMP message issued by an agent that reports an event. The term
trap is used as abbreviation to SNMPv1 or SNMPv3 notification. The SNMP
version is usually omitted, unless it is important to specify it. Traps may be
generated and sent as a result of event or alarm.
Megaplex-4 includes a configurable mechanism of detecting and reporting alarms.
Once an alarm is triggered, Megaplex-4 sends an alarm trap to the relevant
network manager, depending on whether the relevant trap has been masked or
activated. In the current Megaplex-4 version, all traps are activated.
Alarms and events have the following properties:
• Source –An entity for which alarms and events can be generated. The source
consists of a source ID, source type (e.g., system, fan, Ethernet), and source
name.
• ID – Unique numeric identification of the alarm/event
• Name – Unique alphanumeric identification of the alarm/event, of up to
32 characters
• Description –Alphanumeric description that provides details about the
alarm/event
• Severity (alarms only) – Critical, Major, or Minor.
Masking
Alarms and events can be masked per source type, source ID, or minimum
severity. When masking by source type (such as Ethernet) or source ID (such as
Ethernet port 1 on card in slot 1), choose a specific alarm or event, or apply the
change to all the alarms and events of the selected source type or ID.
When masking an alarm/event, you can:
• Prevent the alarm/event from being written to the history log, sent to Syslog
servers, and displayed in the default view of the active alarms table
• Prevent any corresponding traps from being sent to management stations,
regardless of masking in the SNMP manager configuration
• Deactivate alarm reporting via LED and alarm relay.
Megaplex-4 Handling Events 11-3

When an alarm/event is not masked, any corresponding traps are sent only to
management station for which the traps are not masked in the SNMP manager
configuration. In addition, you can:
• Change alarm severity
• Mask a specific reporting method
• Mask alarms per their severity.
You can also acknowledge alarm logs. The last acknowledgement time is recorded
by Megaplex-4. When displaying the log, only entries entered after the last
acknowledgment time are displayed. This action does not delete any data from
the log, and you can also display acknowledged data by using a designated
keyword.
Alarm Buffer
Megaplex-4 continuously monitors critical signals and signal processing functions.
In addition, it can also monitor an external alarm line, connected to the ALARM
connector.
If a problem is detected, Megaplex-4 generates time-stamped alarm messages.
The time stamp is provided by an internal real-time clock.
The alarm messages generated by the Megaplex-4 are explained below.
Internally, the Megaplex-4 stores alarms in an alarm buffer. This alarm buffer can
store up to 200 alarm messages, together with their time stamps. The alarm
history buffer is organized as a FIFO queue; after 200 alarms are written into the
buffer, new alarms overwrite the oldest alarms.
Alarm messages can also be sent automatically as traps to the user-specified
network management stations.
The alarms can be read on-line by the network administrator using the network
management station, a Telnet host or a supervision terminal. The network
administrator can then use the various diagnostic tests to determine the causes of
the alarm messages and to return the system to normal operation.
When Megaplex-4 is powered down, the alarm messages are erased; old alarms
will not reappear after the Megaplex-4 is powered up again. When using the
terminal or a Telnet host, the user also can clear (delete) the alarms stored in
this buffer, after reading them.
Alarm Relays
In addition to the alarm reporting facility, Megaplex-4 has two alarm relays with
floating change-over contacts: one relay for indicating the presence of major
alarms and the other for minor alarms. Each relay changes state whenever the
first alarm is detected, and returns to its normal state when all the alarms of the
corresponding severity disappear.
The relay contacts can be used to report internal system alarms to outside
indicators (e.g., lights, buzzers, bells), located on a bay alarm or remote
monitoring panel.
11-4 Handling Events Megaplex-4

See also ACM Module, TP Module and VS Modules sections in the Megaplex-4 I/O
Modules Installation and Operation Manual for description of alarm relays
available on these modules.
Configuring Alarm Reporting

This section describes how to configure alarm/event properties, how to mask
them and rebuild active alarms. Some of the commands are available only with
ACM or VS-6/BIN modules installed in the system.
Factory Defaults
Configuration defaults are listed in the table below. This table is relevant only
when the ACM module is installed in the chassis.
active Alarm-input: active state of the port input line high
energized Alarm-output: state of port relay when alarm is present yes
 To configure alarm/event properties:

1. Navigate to configure reporting.
The config>reporting# prompt is displayed.
Setting the active state of alarm-input <slot>/<port> [active {high high – Active alarm input is indicated by
the port input line and alarm | low | off}] [description < alarm-input-high voltage
description (ACM module description-string>] low – Active alarm input is indicated by
only) low voltage
off – Alarm input is disabled
Description-string – a free-text alarm
name
Setting the alarm alarm-input <slot>/<port>/<tributary> Description-string – a free-text alarm

description (VS-6/BIN [description <alarm-input-description- name
module only) string>] Active state selection although present in
CLI is not relevant for this module.
Defining the state of the alarm-output <slot>/<port> Energizing:

output relay when an alarm energized {yes | no} • energized yes – The corresponding
is present (ACM module relay is normally unenergized and
only) switches to the energized state when
the alarm is active.
• energized no – The corresponding
relay is normally energized and
switches to the unenergized state
when the alarm is active.
The relay contacts are normally open.

Binding an alarm of specific bind-alarm-to-relay <source-type> For the list of source types and
source type to an alarm <alarm-name> alarm-output corresponding alarm names, refer to
output port <slot/port/tributary> Alarm list in this chapter.
Using no before the command cancels
the alarm binding
Applicable for ACM, VS-6/BIN and TP
modules installed in the system. In the TP
module, relevant for ports 5..8 only.
<tributary> relates only to VS-6/BIN
modules.
A cmd-out port cannot be simultaneously
bound as Alarm Relay (the current
command) and bound as secondary cmd-
out port to a primary cmd-out port (see
Chapter 6).
Binding an alarm of specific bind-alarm-source-to-relay <source- For the list of source types and
source type on a specific type> <alarm-name> <slot/port> corresponding alarm names, refer to
user port to an alarm output alarm-output <slot/port/tributary> Alarm list in this chapter.
port Using no before the command cancels
the alarm binding.
Applicable for ACM, VS-6/BIN and TP
modules installed in the system. In the TP
module, relevant for ports 5..8 only.
<tributary> relates only to VS-6/BIN
modules.

Masking alarm/event from a alarm-source-attribute <source-type> Use the no form to unmask

specific source, defining [<source-id>] alarm <alarm-name> alarms/events.
alarm severity and masking [severity {critical | major | minor}] [log] When you apply masking command, the
reporting methods [snmp-trap] [led-relay] alarm severity changes. If later you apply
Note: Severity and LED- alarm-source-attribute<source-type> the unmasking command (no
Relay apply only to alarms. [<source-id>] event <event-name> alarm-source-attribute…) the severity
[log] [snmp-trap] remains at its changed value. If you want
the initial severity back, repeat the
command with the desired severity.
The following apply:
• If a trap is masked according to
alarm/event attribute, it is not sent to
any management station, regardless
of whether it is masked in the SNMP
manager configuration
• If a trap is unmasked according to
alarm/event attribute, it is sent only
to management station for which it is
not masked in the SNMP manager
configuration.
• LED-Relay mask is not activated on
ALM LED until clear-log command is
performed for active alarm history log.
Masking alarm per severity mask-minimum-severity [log {critical | Masking a minimum severity means that
major | minor}] [snmp-trap {critical | lower severities are also masked
major | minor}] [led-relay {critical |
major | minor}]
no mask-minimum-severity [log]
[snmp-trap [led-relay]
Acknowledging the logs acknowledge {log | all-logs}
Displaying alarm logs show {active-alarms | active-alarms- See Working with the Alarm and Event
details | alarm-information | alarm-log | Logs
alarm-list | event-information |
event-list | log ]
Displaying the state of input show alarm-input {slot <slot>| all} Current status:
alarms and configured • Active – an active external alarm is
voltage for each port of the present on the port
slot/chassis
• Inactive – external alarm is not active
or port in shutdown state
Voltage: as defined by alarm-input
<slot>/<port> [active {high | low | off}]
command
Description: port name

Displaying the state of show alarm-outputs {slot <slot>| all} • Active – active alarms from the list
output alarms for each port configured by the user are present on
of the slot/chassis the port
• Inactive –no active alarms from the list
configured by the user are present on
the port
Note If alarm/event is masked using one of the masking commands

(alarm-source-attribute, alarm-source-type-attribute, mask-minimum-severity),
there is no need to repeat the procedure using the other commands.
Examples
 To mask alarm for a specific source type:

• Source type – All E1s
• Alarm – excessive-bpv
• Reporting methods – log
mp4100>config# reporting
mp4100>config>reporting# alarm-source-type-attribute e1
excessive-bpv log
 To mask event for a specific source:

• Source type –E1 1 in port 1 on card in slot 1
• Event – css-path-tca
• Reporting methods – SNMP trap
mp4100>config>reporting# alarm-source-attribute e1 1/1 event
css-path-tca snmp-trap
 To mask alarms per severity:

• Severity –major and lower
• Reporting method – LED and alarm relay
mp4100>config>reporting# mask-minimum-severity led-relay major
Working with the Alarm and Event Logs

This section explains how to display and clear different type of alarm and event
logs. The maximum number of items in manageable logs is 200. To export up to
5000 alarms/events to a text log file, see Chapter 10.
Instructions on viewing alarms and events can be found below. Lists of possible
alarms and events can be found under Alarm List and Event List sections,
respectively.

 To display the alarm/event log:

1. Navigate to configure>reporting# context.
2. Type show followed by the display option parameter listed in the following
table.
Display Option Meaning Example no
active-alarms Shows the active alarms table. Counters of active alarms in 1

the output, in order of severity, appear at top of the
screen
active-alarms-details Same as above but with time stamp added to active alarms 2
alarm-information Detailed information about alarm type. For example, if you 3

need to know what is LOF alarm on SDH/SONET in
Examples 1 or 2, see Example 3.
alarm-log Log of active and cleared alarms (without events). The 4

default view of the alarm log (i.e., history of alarms) shows
one line per raised alarm and one for cleared alarm
alarm-list List of all Megaplex-4 alarms for a specific source IDs and 5
[<source ID> [severity severity value or of all the alarms available in the system
{critical|major|minor}]]
event-information Detailed information about event type (similar to alarm-

information)
event-list List of all Megaplex-4 events for a specific source IDs or of

all the events available in the system
log Log of active alarms, cleared alarms and events
To scroll up and down in the list, use the arrow keys.
 To clear a log:
• At the config>reporting# context, enter clear-alarm-log {log | activity-log | all-
logs}.
The corresponding log is cleared.
Example 1: Displaying Active Alarms

This command shows the table of active alarms. On top of the screen appear counters of active alarms in the
output, by severity: critical, major and minor.
mp4100>config>reporting# show active-alarms

Total : Critical : 0 Major : 3 Minor : 0
1 SDH-SONET cl-a/2 LOF Maj unmasked

2 Ethernet MNG cl-b/1 LOS Maj unmasked
3 SDH-SONET cl-b/2 LOS Maj unmasked
Example 2. Displaying Active Alarms Details

This command shows the table of active alarms with their time stamp. On top of the screen appear counters
of active alarms in the output, by severity: critical, major and minor.

mp4100>config>reporting# show active-alarms-details

Total : Critical : 0 Major : 3 Minor : 0
1 Loss of frame (LOF)
15-05-2015 SDH-SONET LOF Major Unmasked

02:10:52 cl-a/2
2 Loss of signal (LOS)
15-05-2015 Ethernet LOS Major Unmasked

03:38:53 MNG cl-b/1
3 Loss of signal (LOS)
15-05-2015 SDH-SONET LOS Major Unmasked

03:38:48 cl-b/2
Example 3. Displaying Information of LOF alarm on

SDH/SONET port
This command displays detailed information about a specific alarm. The output
shows configuration of the source type, followed by a table of sources whose
configuration divert from the source type’s configuration.
For example, use this command if you need to know what is LOF alarm on
SDH/SONET in Examples 1 or 2. In this example the table of sources is empty
since all the sources are configured the same as their type.
mp4100>config>reporting# show alarm-information sdh-sonet lof

Source : SDH-SONET
Name : LOF
Description : Loss of frame (LOF)
Alarm ID : 100003
Severity : Major
LED : Yes
LED Relay : Yes
Logged : Yes
SNMP Trap : Yes
SNMP trap OID : 1.3.6.1.4.1.164.3.1.6.2.0.22
Source Source ID Severity LED Logged SNMP Trap

-----------------------------------------------------------------------------
Example 4. Alarm Log

This command displays the log of active and cleared alarms (without events). The
default view of the alarm log (i.e. history alarms) shows one line per raised alarm
and one for cleared alarm. The alarm severity is shown on the left. Its possible
values are critical, major, minor, or cleared. The field on the left shows the reason
of alarm removal: resolved, user-initiated, alarm suppression, not applicable.
mp4100>config>reporting# show alarm-log

Last Acknowledge On : 64-149-1203 00:206:27.
1 Alarm indication signal (AIS)
17-05-2015 SDH-SONET AIS-LINE

Major
20:19:36 cl-a/2

Cleared
20:19:38 cl-a/2 Resolved

Major
20:19:40 cl-a/2

Cleared
20:19:46 cl-a/2 Resolved
Example 5. Alarm List

This command displays the list of all Megaplex-4100 alarms for a specific source
IDs and severity value. The table also shows whether the alarm appears in the log
and whether these parameters are set to default or modified by the user. This
specific example displays the beginning of the list of all the alarms available in the
system.
mp4100>config>reporting# show alarm-list
Source
Name ID Severity Logged
System
hardware_failure_fe 20012 Yes (Default)
-----------------------------------------------------------------------------
System
configuration_mismatch_fe 20013 Yes (Default)
-----------------------------------------------------------------------------
System
INTERFACE_MISMATCH_FE 20014 Major Yes (Default)
-----------------------------------------------------------------------------
System
NO_INTERFACE_FE 20015 Yes (Default)
-----------------------------------------------------------------------------
Power Supply
POWER_DELIVERY_FAILURE 20201 Major Yes (Default)
-----------------------------------------------------------------------------

Alarm Input
Alarm_Relay_Input 20401 Major Yes (Default)
-----------------------------------------------------------------------------
Card
HARDWARE_FAILURE 40001 Major Yes (Default)
-----------------------------------------------------------------------------
Card
CARD_MISMATCH 40002 Major Yes (Default)
-----------------------------------------------------------------------------
To scroll up and down in the list, use the arrow keys.
Alarm, Event and Trap Lists

You can view the full lists of alarms and events supported by Megaplex-4, along
with the traps corresponding to each alarm or event.
 To view the alarms table:

• Double-click the paperclip image on the following line.
 To view the events table:

 To view the traps table:


Table 11-1 lists the messages displayed by Megaplex-4 when a configuration
error is detected.
730 Error LOG MUST BE MASKED If an alarm is masked for log reporting
TOGETHER WITH SNMP-TRAP (alarm-source-attribute command), it must be masked for
trap reporting as well.
11.3 Troubleshooting
Preliminary Checks
If a problem occurs, perform the following preliminary checks:
11-12 Troubleshooting Megaplex-4

• If the problem is detected when Megaplex-4 is put into operation (for the
first time), perform the following checks:
 Check for proper chassis and module installation, and correct cable
connections, in accordance with the system installation plan.
 Check that system and module configuration parameters are in
accordance with the specific application requirements, as provided by the
system administrator.
 If the Megaplex-4 nodal clock is to be locked to the clock recovered from
one of the ports of a module installed in the chassis, make sure a suitable
additional clock source is configured and provides a good clock signal.
• When two CL modules are installed, check the ON LINE indicators: the ON
LINE indicator of the active module must light steadily, and that of the
standby must flash. If not, check the configuration.
• Check the displayed alarm messages and refer to Alarm, Event and Trap Lists
section for their meaning and corrective actions.
Troubleshooting Procedure
If the problem cannot be corrected by performing the actions listed above, refer
to Table 11-2. Identify the best-fitting trouble symptoms and perform the actions
listed under “Corrective Measures” in the order given, until the problem is
corrected.
Table 11-2. Troubleshooting Chart
No. Trouble Probable Cause Corrective Measures

Symptoms
1 Megaplex-4 does 1. No power Check that power is available at the power outlets or power
not turn on distribution panel serving the Megaplex-4.
Check that both ends of all the Megaplex-4 power cables are
properly connected.
2. Defective PS Replace the suspected PS module

module
3. Defective Replace Megaplex-4
Megaplex-4
2 The local 1. Connection made Check that the connection is made to the CONTROL DCE
Megaplex-4 to the inactive CL connector of the CL module whose ON LINE indicator lights
cannot be module steadily
configured
2. Configuration Restore the default parameters as explained in Chapter 10
through its
problem and then perform the preliminary supervision terminal
CONTROL DCE
configuration instructions in accordance with chapter 4
port
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-4, check the equipment providing the data
link for proper operation
Megaplex-4 Troubleshooting 11-13


Symptoms
4. Software not yet Download the appropriate Megaplex-4 software to the CL

loaded into CL modules in accordance with Chapter 12
module, or
corrupted
5. Defective CL Replace the corresponding CL module
module
3 The local 1. Configuration Check the CONTROL ETH port configuration.
Megaplex-4 problems Check that the ON LINE indicator of the CL module lights
cannot be steadily
managed
through its 2. Problem in the Check that the LINK indicator of the CONTROL ETH port is lit.
CONTROL ETH connection If not, check for proper connection of the cable between the
port between the LAN and the CONTROL ETH port. Also check that at least one
CONTROL ETH port node is active on the LAN, and that the hub or Ethernet
and the LAN switch to which the Megaplex-4 CONTROL ETH port is
connected is powered
3. External problem Check the external equipment (for example, the default
gateway and other routers/switches) that process the traffic
coming from the local Megaplex-4 CONTROL ETH port
4. Defective CL Replace the corresponding CL module

module
5. Defective Replace Megaplex-4
Megaplex-4
4 The LOS indicator 1. Cable connection Check for proper connections of the cables to the
of an SDH/SONET problems SDH/SONET connector of each CL.2 port.
port is on Repeat the check at the user’s equipment connected to the
port.
2. External problem Activate the remote loopback at the local SDH/SONET module
port.
• If the user equipment connected to the SDH/SONET
connector does not receive its own signal, check its
operation, and replace if necessary
• If the problem is not in the equipment connected to
the SDH/SONET port, replace the CL.2 module
5 The status 1. Cable connection Check for proper connections of the cables to the module
indicator of a problems connector.
local I/O module Repeat the check at the user equipment connected to the
port lights in red port.
2. External problem Activate the local physical loopback on the corresponding
port. If the indicator of the corresponding local port lights in
green while the loop is connected, the problem is external.
Check cable connections, and the transmission equipment
providing the link to the remote unit.
3. Defective I/O Replace the I/O module

module
11-14 Troubleshooting Megaplex-4


Symptoms
6 The LOS indicator 1. Cable connection Check for proper connections of the cables to the connector.
of the CLOCK problems Repeat the check at the equipment providing the station
port lights in red clock signal to the Megaplex-4.
2. Defective CL Replace the CL module
module
11.4 Performing Diagnostics Tests

This section describes general diagnostic tests and RFC-2544 testing. For
information on testing ports, refer to Chapter 6. For information on testing
flows, refer to Chapter 8.
When a problem occurs, Megaplex-4 offers a set of diagnostic functions that
efficiently locate the problem (in the Megaplex-4 chassis, in one of Megaplex-4
modules, in a connecting cable, or in external equipment) and rapidly restore full
service.
The diagnostic functions include a ping utility on the system level and loopbacks
at the various ports, which identify whether a malfunction is caused by the
Megaplex-4 or by an external system component (for example, an equipment
unit, cable, or transmission path connected to the Megaplex-4).
Ethernet BERT (RFC-2544 Testing)

You can perform BER testing based on RFC-2544, on the flows terminated on PCS
ports of the ASMi-54C and ASMi-54C/N modules. The far-end device can be any
SHDSL modem featuring RLB loopback on its SHDSL ports, such as ASMi-54,
ASMi-54L, ASMi-52, ASMi-52L, etc.
Note Some of the ASMi-54 models support RLB loopback on PCS ports in addition to
RLB loopback on SHDSL ports. If this (PCS) loopback is activated from the CPE,
the IP management remains available during diagnostics.
Standards
RFC-2544, Benchmarking Methodology for Carrier Ethernet Networks
Benefits
The test can be performed with different frame sizes and data patterns including
PRBS to verify data integrity. It can be performed before service is commissioned
to ensure service parameters or during service for fault verification and isolation.
The Ethernet BERT test measures the packet loss, detecting the point at which
frame loss does not occur.
Megaplex-4 Performing Diagnostics Tests 11-15

The packet loss test is performed as follows:

• Transmit x frames at a rate of 100% throughput
• Calculate frame loss with the formula: [(tx - rx)/tx] *100
• If at least two attempts the test is 100% success (all the frames go through),
the test is reported as successful. If frame loss is detected on either the BERT
or analyzer, the next try is undertaken with the speed decreased by 10%.
This procedure is repeated until two successive attempts are successful.
Factory Defaults
By default, no profiles or tests are defined.
When you create a test profile, it is configured by default as shown below.
mp4100# config test rfc2544
mp4100>config>test>rfc2544# profile-name Testprf
mp4100>config>test>rfc2544>profile-name(Testprf)$ inf d
frame-size 64
pattern all-ones
mp4100>config>test>rfc2544>profile-name(Testprf)$
When you create a test, it is configured by default as shown below.
mp4100# config test rfc2544
mp4100>config>test>rfc2544# test 1
mp4100>config>test>rfc2544>test(1)$ info detail
max-rate 0 convention data-rate compensation 0
type frame-loss
max-test-duration 2
no associated-flow
mp4100>config>test>rfc2544>test(1)$
Performing the Test
 To perform the Ethernet BER test:

1. This step depends on the far-end device:
 For ASMi-54 (ver 2.x): From the remote CPE, activate the RLB loopback
towards Megaplex-4100/4104.
 For ASMi-54L (ver 2.x): From the module, activate the PCS RLB loopback
towards Megaplex-4100/4104 using the EOC proprietary protocol.
2. Initiate the BERT functionality by configuring the following:
 RFC-2544 profile – Template to create test runs. You can configure up to
eight test profiles.
 RFC-2544 test – Associated with RFC-2544 profile. Up to eight tests can
use the same test profile.
Note One Ethernet BER test can be run at a time.
3. Check the report menu for results.
Note The BER test is replacing the customer traffic.
11-16 Performing Diagnostics Tests Megaplex-4

In order to perform RFC-2544 tests, you must configure:
 To configure RFC-2544 test profiles:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
profile-name <name>
A test profile with the specified name is created if it does not already
exist, and the config>test>RFC2544> profile-nam(<name>)# prompt is
displayed.
Configuring frame sizes frame-size [64] [128] [256] [512] [1024] [1280] You can specify one standard
for the test [1518] [1700] [1900] [2000] frame size per profile.
Configuring pattern of pattern { all-ones | all-zeros-without-crc |

test frame payload all-zeros-with-crc | alternate | prbs-with-crc |
prbs-without-crc }
 To configure RFC-2544 tests:

1. Navigate to configure test rfc2544.
The config>test>rfc2544# prompt is displayed.
2. Type:
test <id>
The config>test>rfc2544> test(<id>)# prompt is displayed.
Activating the test activate Type no activate to stop the test
Associating test with flow associated-flow <name> The flow has the port to be tested as
the egress port.
Configuring maximum max-rate <kbps> max-rate – The maximum rate in kbps.

rate for test This value should be 1-2 of the
bandwidth value.
Configuring the maximum max-test-duration <minutes> Allowed values: 2–60

test duration The test is stopped when the
configured maximum duration has
elapsed, whether or not all the
configured test types have completed.
Associating a test profile test-profile <name>

with the test

Defining the type of type [frame-loss] In the current version, type is always
benchmark test to frame-loss.
perform on this run
Clearing test report clear-reports
Displaying test report show report all

show report iteration
<iteration-number>
Displaying test status show status
Displaying test summary show summary

error is detected.
656 Error PROFILE TEST MUST BE BOUND You must associate a test profile to the test using test-
profile command.
658 Error MAX RATE MUST BE You must specify the maximum rate using max-rate
CONFIGURED command.
659 Error ASSOCIATED FLOW ISN'T You must associate a flow to the test using
DEFINED associated-flow command.
660 Error FLOW ISN'T ACTIVE You must set the associated flow to “no shutdown”.
664 Error NO PARAMETER CHANGE, TEST You cannot modify test parameters while the test is still
IS IN PROGRESS running.
665 Error CLEAR REPORT BEFORE Test parameters can be modified only after the test report
PARAMETER SETTING is cleared.
666 Error ILLEGAL FRAME SIZE AND RATE The ratio max-rate/frame-size must must not be less than
COMBINATION 8 (relevant for CL.2/A only).
Example
 To run the Ethernet BER test:
• Frame size – 64
• Test type – frame loss
• Associated to flow “520-slot3-pcs1-gbe2-in”
• Maximum test duration – 2 min
• Maximum rate – 10 Mbps
mp4100>config>test>rfc2544>profile-name (1-64)#
frame-size 64
pattern all-ones

----------------------------------------------
mp4100>config>test>rfc2544>test(1)#
test-profile "1-64"
max-rate 10000000 convention data-rate compensation 0
type frame-loss
max-test-duration 2
associated-flow "520-slot3-pcs1-gbe2-in"
mp4100>config>test>rfc2544>test(1)# commit
mp4100>save
-----------------------------------------------
mp4100>config>test>rfc2544>test(1)# activate
--------------------------------------------------------
mp4100>config>test>rfc2544>test(1)# show status

Activity Status : In Progress
Elapsed Time <dd:hh:mm:ss> : <00:00:00:10>
Current Test Type : Frame Loss Current Frame Size : 64

----------------------------------------------------------------------
mp4100>config>test>rfc2544>test(1)# show report all
Test ID : 1
Iteration Number : 1
Date & Time : 31-12-2012 09:49:49
Profile Name : 1-64
Number of Trials : 1
Duration <dd:hh:mm:ss> : <00:00:04:04>
Test Parameters
-----------------------------------------------------------------------------
Max Rate (bps): 10000000 Pattern: All Ones
Flow Parameters
-----------------------------------------------------------------------------
Flow Name : 520-slot3-pcs1-gbe2-in
Loss Report
-----------------------------------------------------------------------------
Status : Success Duration : <00:00:04:04>
Frame Size : 64
Theoretical Max (FPS) : 22258
Throughput of Max Success

(%) (%)
-----------------------------------------------------------------------------
100 100
90 100

Performing a Ping Test

You can perform a ping test to check the Megaplex-4 IP connectivity.
 To perform a ping test:

1. At any level, start pinging the desired host specifying its IP address and,
optionally, the number of packets to be sent, and payload size:
ping <1.1.1.1–255.255.255.255> [number-of-packets <1–10000>] [payload-
size <32–1450 bytes>]
2. To stop the ping test, enter Ctrl-C.
Example:
mp4100# ping 172.17.170.81 number-of-packets 2 payload-size 64
Pinging 172.17.170.81 with 64 bytes of data:
Reply from 172.17.170.81 bytes=64 ttl=64 time=10ms seq=1

Reply from 172.17.170.81 bytes=64 ttl=64 time=0ms seq=2
mp4100#
--- Ping Statistics ---

Packets: Sent = 2, Received = 2, Lost = 0 (0% loss)
Running Diagnostic Loopbacks

There are two subsystems/engines in Megaplex-4 – TDM and Ethernet, each
featuring its own tests and loopbacks. These tests are shown in the diagrams
below (Table 11-4 and Table 11-5).
Table 11-4 identifies the general types of test and loopback functions supported
by Megaplex-4 TDM engine, and the paths of the signals when each test or
loopback is activated. The available diagnostic loopbacks depend on the installed
modules, and some of them support additional types of loopbacks. For specific
instructions, refer to the corresponding section in Chapter 6: for example, Testing
E1 Ports under E1 Ports, etc.
Table 11-5 schematically shows the tests available in the Megaplex Ethernet
engine.

Table 11-4. Megaplex-4 Test and Loopback Functions - TDM Engine
Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
Diagnostic
DS1 . SDH/
Function I/O Port Cross-Connect .. E1/T1 VC/VT
SONET
Mapper Matrix
Matrix . Framer
..
.
.
Local loopback on
I/O voice, serial,
serial-bundle, mux- DS1
I/O Port Cross-Connect
eth-tdm, shdsl Interface
Matrix
ports
Remote loopback
on I/O voice, serial,
DS1
serial-bundle, mux- Port Cross-Connect
Interface
eth-tdm, shdsl Matrix
ports
Local loopback on
E1 or T1 port
DS1
(M8E1/M8T1, Port Cross-Connect
Interface
M16E1/M16T1, Matrix
ASMi-54C/N, T3, all
"1 "
OP modules)
Remote loopback
on E1 or T1 port
DS1
(M8E1/M8T1, Port Cross-Connect
Interface
M16E1/M16T1, Matrix
ASMi-54C/N, T3, all
OP modules)

Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
Diagnostic
DS1 . SDH/
SONET
Mapper Matrix
Matrix . Framer
.
..
.
Local loopback on
I/O Interface
E1/E1-i/T1/T1-i
timeslots 1
DS1
(M8E1/M8T1, 2
.. Cross-Connect
M16E1/M16T1, .. Matrix
.
ASMi-54C/N, T3,
Megaplex OP
modules)
Remote loopback
I/O Interface
on E1/E1-i/T1/T1-i
timeslots 1
2 DS1
(M8E1/M8T1, .. Cross-Connect
M16E1/M16T1, .. Matrix
.
ASMi-54C/N, T3,
Megaplex OP
modules)
Remote loopback SDH/SONET

Framer
on SDH/SONET link
Local loopbacks on VC/VT

Matrix
AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5 ports
Remote loopbacks VC/VT

Matrix
on AUG/OC-3,
TUG-3/STS-1,
VC-12/VT-1.5 ports

Megaplex-4100
SDH/SONET Interface
E1-i/T1-i
CL Framers
1
2
Diagnostic
DS1 . SDH/
SONET
Mapper Matrix
Matrix . Framer
.
..
.
E1-i/T1-i Framers
Local loopback on
E1-i/T1-i port 1
2
..
.
..
.
E1-i/T1-i Framers
Remote loopback
on E1-i/T1-i port 1
2
..
..
..
Local loopback on E1-I/T1-I

Framers
timeslots of
E1-i/T1-i port
Remote loopback E1-I/T1-I

Framers
on timeslots of
E1-i/T1-i port

Table 11-5. Megaplex-4 Test and Loopback Functions - Ethernet Engine
Megaplex-4100
CL
CPU
Diagnostic
Traffic
Function Counter
CPE I/O Port ETH Engine L2
Switch
Traffic
Generator
Remote
loopback on PCS CPE
ports (initiated
PCS I/O Port
in Megaplex)
Ethernet BERT
CPE Traffic
Counter
PCS I/O Port
Traffic
Generator
Loop per flow See Testing the Flows in Chapter 8
The Megaplex loopbacks are activated from the following context and are
described in the corresponding sections in Chapters 6, 8 and 11.
Loopbacks Activated from
Local and remote loopbacks on I/O voice, serial, configure>port>voice

serial-bundle, mux-eth-tdm, shdsl, pcs ports configure>port>serial
configure>port>serial-bundle
configure>port>mux-eth-tdm
configure>port>shdsl
configure>port>pcs (remote only)
Local and remote loopbacks on configure>port>e1

E1 or T1 port configure>port>t1
Local and remote loopbacks on configure>port>t3

T3 ports
Local and remote loopbacks on E1/E1-i/T1/T1-i configure>port>e1

timeslots configure>port>t1
configure>port>e1-i
configure>port>t1-i

Loopbacks Activated from
Remote loopback on SDH/SONET link configure>port>sdh-sonet
Local and remote loopbacks on AUG ports configure>port>sdh-sonet>aug
Local and remote loopbacks on OC-3 ports configure>port>sdh-sonet>oc3
Local and remote loopbacks on TUG-3 ports configure>port>sdh-sonet>aug>tug3
Local and remote loopbacks on STS-1 ports configure>port>sdh-sonet>oc3>sts1
Local and remote loopbacks on VC-12 ports configure>port>sdh-sonet>aug>tug3>vc12
Local and remote loopbacks on VT-1.5 ports configure>port>sdh-sonet>oc3>sts1>vt1-5
Local and remote loopbacks on E1-i/T1-i port configure>port>e1-i

configure>port>t1-i
Local and remote loopbacks on timeslots of configure>port>e1-i

E1-i/T1-i port configure>port>t1-i
Ethernet BERT configure>test>rfc2544
Loop per flow configure>flows>flow
11.5 Performance Management

Megaplex-4 maintains performance management (PM) statistics for selected
entities in the device. The PM statistics are collected into a file periodically, for
retrieval by RADview, for display in the RADview PM portal (refer to the RADview
System User’s Manual for further details on the PM portal). The PM collection
process can be globally enabled or disabled for the entire device. In addition, the
statistics collection can be enabled for all entities of a specific type, or for
specific entities.
Benefits
The PM data is useful for analyzing Megaplex-4 service quality. The flexible
statistics collection allows only the necessary data to be collected.
PM statistics collection is configured for the device, entity type, and specific
entities. PM statistics are collected for the Ethernet ports.
Megaplex-4 Performance Management 11-25

Notes • PM statistics collection is performed only if it is enabled for the entire device,
regardless of whether it is enabled for any entity
• PM statistics are not collected for entities that are administratively disabled.
When PM statistics collection is enabled for all entities of the same type, then
when a new entity of that type is added the device automatically starts collecting
PM statistics for it.
Note If you are using the RADview PM Portal, it is recommended to enable PM statistics
collection for all relevant entities. See Examples for a script that you can use for
this purpose.
PM statistics collection is performed at user-configurable intervals of one second

to 15 minutes. A different interval can be configured for each entity type, and for
specific entities.
If different intervals are scheduled for collection at the same time, Megaplex-4
collects the PM statistics starting with the interval that has the highest frequency,
and ending with the interval that has the lowest frequency. If Megaplex-4 has not
finished collecting the statistics for an interval when the scheduled time for
another interval arrives, the following action is taken according to whether the
new interval is the next interval, or an interval with higher frequency:
• If it is the next interval, then the next interval is canceled, and a PM record
indicating the cancellation is inserted in the PM data
• If it is an interval with higher frequency, then Megaplex-4 collects the higher
frequency interval statistics and then resumes collecting the lower frequency
interval statistics. The PM data is retrieved from Megaplex-4 by RADview via
TFTP or SFTP. After PM data is retrieved, Megaplex-4 deletes the file and
opens a new one for further data.
Factory Defaults
Command Level under config Default Remarks
pm reporting pm PM statistics collection in the

device is globally enabled by
default
pm-collection eth reporting Disabled PM statistics collection for

Ethernet ports is not explicitly
configured by default,
therefore it is disabled
pm-collection Specific entity level Disabled PM statistics collection for

specific entities is not explicitly
configured by default;
therefore it is disabled until
statistics collection is enabled
for the entity type or entity
11-26 Performance Management Megaplex-4

Configuring Performance Management

PM statistics collection is configured for the entire device via the pm command,
and for entity types via the pm-collection command, in the reporting level. For
specific entities, PM statistics collection is configured via pm-collection, in the
specific entity level.
The interval parameter for the pm-collection command can range from 60 (1 min,
recommended) to 900 seconds (15 minutes), however the value must divide
evenly into 3600. Different intervals can be specified for an entity type and for
specific entities of that type. For example, if the PM statistics collection interval
for all Ethernet ports is configured to 15 minutes, and the PM statistics collection
interval for port 3/1 is configured to 1 minute, the data displayed in the RADview
PM portal shows Ethernet port data for every 15 minutes, and port 3/1 data for
every minute.
The following shows the PM statistics collection configuration tasks, and their
corresponding commands, as well as the level of each command.
Task Level under config Command Comments
Globally enabling PM reporting pm Type no pm to disable all

statistics collection for PM statistics collection in
device Megaplex-4
Enabling PM statistics reporting pm-collection eth Type no pm-collection eth

collection for Ethernet interval <seconds> to disable PM statistics
ports collection for Ethernet
ports
Enabling PM statistics port > pm-collection interval Type no pm-collection to

collection for a specific ethernet(<slot>/<port-num>) <seconds> disable PM statistics
Ethernet port (other collection for the Ethernet
than the management port
port)
Note
PM statistics are collected for entities for which PM statistics collection is
specifically enabled (at the entity(port) level) via pm-collection, even if PM
statistics collection for the entity type (under reporting context) is disabled.
Examples
 To enable PM for all relevant entities in Megaplex-4:
• PM statistics collection enabled for device
• PM statistics collection enabled for all relevant entities, every five minutes.
exit all
configure reporting
#**** Enable PM in device****#
pm
#**** Enable PM for Eth ports, collection interval=5 min****#
pm-collection eth interval 300
exit all
save
Megaplex-4 Performance Management 11-27

 To configure the following PM:

• PM statistics collection enabled for device
• PM statistics collection enabled for Ethernet ports, every two minutes
• PM statistics collection for Ethernet port cl-a/1 configured to every minute
exit all
configure reporting
#**** Enable PM in device
pm
#**** Enable PM for Eth ports, collection interval=2 min
exit all
#**** Configure PM statistics collection interval for Eth port cl-a/1, to

1 min
pm-collection interval 60
exit all
save
 To display PM configuration from above example:

mp4100# configure reporting
mp4100>config>reporting# info detail
pm
mp4100>config>reporting# exit all
mp4100# configure port ethernet cl-a/1

mp4100>config>port>eth(cl-a/1)# info detail
pm-collection interval 60
error is detected.
11.6 Technical Support

Technical support for this product can be obtained from the local partner from
whom it was purchased.
RADcare Global Professional Services offers a wide variety of service, support and
training options, including expert consulting and troubleshooting assistance,
online tools, regular training programs, and various equipment coverage options.
For further information, please contact the RAD partner nearest you or one of
RAD's offices worldwide.
RAD Data Communications would like your help in improving its product
documentation. Please send us an e-mail with your comments.
11-28 Technical Support Megaplex-4

Thank you for your assistance!
Megaplex-4 Technical Support 11-29

11-30 Technical Support Megaplex-4

Chapter 12
Software Upgrade
This chapter explains how to upgrade Megaplex-4.
Software upgrades may be required to fix product limitations, to enable new
features, or to make the unit compatible with other devices that are already
running the new software version. New software releases are distributed as *.bin
files, to be downloaded to Megaplex-4.
Megaplex-4 can store four software versions, each in one of the four partitions
of its flash memory, which also contains a boot program. The software is stored
in compressed format.
Note If your system has two CL modules, you must upgrade both modules to the same
software version to ensure seamless redundancy after the upgrade.
12.1 Compatibility Requirements

CL modules can be ordered in two different hardware assemblies: CL.2 and
CL.2/A. Both modules can be upgraded to Ver 4.0. However, when running
Ver 4.0, CL.2/A modules feature supports additional capabilities as compared to
CL.2, such as: Ethernet OAM&P, Ethernet Ring Protection Switching, E-LAN and
more (see Table 1-1 in Chapter 1).
Following are the CL software releases that can be upgraded to version 4.7, as
well as the hardware revisions that can accept the software version 4.7.
• Software –Ver. 3.x and above
• CL.2 Hardware – 0.1 and above
• CL.2/A Hardware – 1.0 and above.
12.2 Impact
Megaplex-4 is upgraded once the unit has been reset.
12.3 Software Upgrade Options

Application software can be downloaded to Megaplex-4 via CLI (using TFTP) or via
the boot menu (using TFTP or XMODEM). The upgrade consists of two stages.
Megaplex-4 Software Upgrade Options 12-1

Chapter 12 Software Upgrade Installation and Operation Manual
First the application software is downloaded from a PC to Megaplex-4 flash disk.

This can be done in the following ways:
• via CLI (using TFTP) using “file>copy” command
• via the boot commands (“download”, using TFTP or XMODEM).
Then the software pack is downloaded from the flash disk to the CL and I/O
modules. This can be done in the following ways:
• via the CLI “admin>software>install” command (both for CL and I/O modules)
• via the boot “set-active”command (CL modules only).
12.4 Prerequisites
This section details the software file names and outlines system requirements
needed for the upgrade procedure.
Software Files
New version releases are distributed as software files named *.bin, for example
sw-pack.bin. The files can be obtained from the local RAD business partner from
whom the device was purchased.
The software upgrade utility includes four partitions called sw-pack-1, sw-pack-2,
sw-pack-3, sw-pack-4 for downloading and storing the software versions. To
activate the specified software version, one of these partitions is set to active.
Each software pack consists of a set of image files for each (CL or I/O) module
with appropriate headers. The software pack can be ordered either for the entire
chassis, or for specific modules only.
System Requirements
Before starting the upgrade, verify that you have the following:
• For upgrade via TFTP:
 Megaplex-4 unit with a router interface bound to the management
interface used, and a static route defined to a PC with the TFTP server
application (such as 3Cdaemon or PumpKIN), and a valid IP address.
 Software file stored on the PC.
Note Megaplex-4 communicates with TFTP servers via Ethernet ports only.
• For upgrade via XMODEM:

 Operational Megaplex-4 unit
 Connection to a PC with HyperTerminal installed
 Software file stored on the PC.
12-2 Prerequisites Megaplex-4

Installation and Operation Manual Chapter 12 Software Upgrade
12.5 Upgrading Software using the CLI (TFTP)

The recommended method for downloading software to the flash disk is to use
the file copy command of the CLI environment. This can be done remotely and
does not require booting. Only CL modules need to be reset after this procedure.
The upgrade consists of two stages:
• The application software is downloaded from a PC to the Megaplex-4 flash
disk. This is done via TFTP, using the file>copy command
• The software pack is downloaded from the flash disk to the CL. This is done,
using the admin>software>install command.
Network administrators use the TFTP protocol to distribute new software
releases to all the managed Megaplex-4 units in the network from a central
location. The central application is a PC on the network with a TFTP server
application such as the PumpKIN server installed on it.
Application file is
transferred to
Megaplex-4100
Ethernet
Megaplex-4100
PC with an Active
TFTP Server and
Application File
Figure 12-1. Downloading a Software Application File to Megaplex-4 via TFTP
Use the following procedure to download the software release to Megaplex-4

using the copy command.
1. Verify that the required image file is stored on the PC together with the TFTP
server application.
2. Verify that Megaplex-4 has a router interface assigned to it, as explained in
Adding and Configuring Router Interfaces in Chapter 8.
3. Verify that a static route is configured to the PC, as explained in Configuring
Static Routes and Default Gateway in Chapter 8.
4. Ping the PC to verify the connection.
5. Activate the TFTP server application, as explained in Activating the TFTP
Server.
6. Download the image file to the unit, as explained in Downloading the New
Software Release File to Megaplex-4 Flash Disk.
Note Configuration values shown in this chapter are examples only.
Megaplex-4 Upgrading Software using the CLI (TFTP) 12-3

Verifying the IP Settings

Megaplex-4 must have a router interface with IP parameters configured according
to your network requirements. In addition, a static route must be established to
the TFTP server to establish a communication session with the TFTP server.
For example:
configure router 1 static 0.0.0.0/0 address 11.11.11.1
 To verify the IP parameters:

• At the router(1)# prompt, enter info detail.
The router interface configuration information is displayed.
mp4100>config>router(1)# info detail
interface 1
address 11.11.11.29/30
bind svi 1
no vlan
no shutdown
exit
arp-timeout 1200
Pinging the PC
Check the integrity of the communication link between Megaplex-4 and the PC by
pinging the Megaplex-4 from the PC.
Activating the TFTP Server

Once the TFTP server is activated on the PC, it waits for any TFTP file transfer
request originating from the product, and carries out the received request
automatically.
 To run the TFTP server:

• Activate a TFTP server application, such as 3Cdaemon (available from
www.3com.com) or PumpKIN (available from http://kin.klever.net/pumpkin/).
Downloading the New Software Release File to Megaplex-4 Flash Disk

Use this procedure to download the new software release to the Megaplex-4
flash disk.
 To download an application file to the Megaplex-4 flash disk via CLI:

• At the file# prompt, enter the copy command, as follows:
copy tftp://<tftp-ip-address>/<image-file-name> sw-pack-<index 1..4>
where tftp-ip-address is the IP address of the PC in which the TFTP server is
installed.
12-4 Upgrading Software using the CLI (TFTP) Megaplex-4

• For example, to download the sw-pack.bin file to sw-pack-4 partition from

the PC at 10.10.10.10:
mp4100>file# copy tftp://10.10.10.10/sw-pack.bin sw-pack-4
You are prompted to confirm the request:
The application file begins downloading.
 To check the flash memory contents:

• At the file# prompt, enter the dir command, for example:
mp4100>file# dir
Codes C - Configuration S - Software LO – Log
sw-pack-1 S 6306207 21-12-2010 valid
13:44:58
sw-pack-2 S 6305847 21-2-2011 valid
7:48:0
sw-pack-3 S 6278526 21-2-2011 valid
9:57:47
sw-pack-4 S 6289552 6-1-2011 valid
10:23:13
14:7:35
14:6:51
factory-default-conf C 796 1-1-1970 Read Only
0:0:9
running-config C 0 1-1-1970 Read Only
0:0:9
 To monitor the copy progress:

• At the file# prompt, enter the show copy command, for example:
Src: tftp://172.17.174.56/mp4cl2_03_00b06.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Finally, the application file is downloaded and saved in partition 4 of the
flash disk.
tftp://172.17.174.56/mp4cl2_03_00b06.bin copied to sw-pack-4
successfully
Once the file is downloaded, the following message is displayed:
mp4100>file# sw-pack.bin copied to sw-pack-4 successfully
 To display the partition contents:

• At the file# prompt, enter the show sw-pack command, for example:

mp4100>file# show sw-pack

Name Version Creation Time Status Actual
---------------------------------------------------------------
sw-pack-1 3.00B6 21-12-2010 13:44:58 Ready Yes
sw-pack-2 3.00B5 21-2-2011 7:48:0 Ready --
sw-pack-3 3.00B4 21-2-2011 9:57:47 Ready --
sw-pack-4 3.00B6 14-3-2011 9:32:56 Ready --
sw-pack-1 Size (Bytes) : 6306207
Type Name Version H/W Ver

Size
(Bytes)
---------------------------------------------------------------
main main.bin 3.00B6 0.1 6305967

Size
(Bytes)
---------------------------------------------------------------
main main.bin 3.00B5 0.1 6305607

Size
(Bytes)
---------------------------------------------------------------
main main.bin 3.00B4 0.1 6278286

Size
(Bytes)
---------------------------------------------------------------
main main.bin 3.00B6 0.1 6306207
asmi54cn asmi54cn.bin 3.4567 1.2 1625132
asmi54c asmi54c.bin 4.5678 2.3 1898111
m8e1 m8e1.bin 7.6543 9.8 844767
op34c op34c.bin 7.5642 8.9 683210
op108c op108c.bin 2.9637 8.5 1053603
In the above example, partitions 1, 2 and 3 contain software release for
CL.2 modules. Partition 4 contains software release for CL.2 and five
types of I/O modules. The active partition is 1.
Installing the New Software Release File from the Flash Disk
Once a file is saved on the Megaplex-4 flash disk, it must be copied to the CL.2 or
I/O modules to replace the current software. The sw-pack file includes the new
software version for all the CL.2 and I/O modules, according to your purchase
order.
You can choose to download the new SW release file to all the CL.2 and I/O
modules installed in the chassis simultaneously. In this case, if the chassis
includes several modules of the same kind, the new software release will be
installed in all of them. If you do not want this to happen, you can issue a
command to install the software in one specific slot.
12-6 Upgrading Software using the CLI (TFTP) Megaplex-4

 To download the new software release file from the flash disk to all the CL.2 and
I/O modules installed in the chassis:
• At the admin>software # prompt, enter the install command. For example:
mp4100# admin
mp4100>admin# software
mp4100>admin>software# install sw-pack-3
The previous software pack is deleted from the active partition:
deleting file /tffs0/Sw-Pack/Active/main.bin
deleting file /tffs0/Sw-Pack/Active/mainHdr.bin
deleting file /tffs0/Sw-Pack/Active/op-108c.bin
deleting file /tffs0/Sw-Pack/Active/op-108cHdr.bin
deleting file /tffs0/Sw-Pack/Active/m8e1.bin
deleting file /tffs0/Sw-Pack/Active/m8e1Hdr.bin
Wait until install command completed.....
successfull install to cl-a

successfull install to cl-b
installation completed
The software pack stored in sw-pack-3 partition is transferred to the
active partition and sent to all the relevant modules that are found in the
chassis. The I/O modules perform reboot automatically and are now ready
for operation with new software version.
7. To activate the new software release for the CL modules, you must perform
reboot. Disconnect the power, wait a few seconds and then reconnect the
power.
Megaplex-4 is upgraded and starts with the new software version.
mp4100# admin software install sw-pack-1
deleting file /tffs0:2/Sw-Pack/Active/main.bin
deleting file /tffs0:2/Sw-Pack/Active/mainHdr.bin
 To download the new software release file from the flash disk to a specified CL.2
or I/O module:
• At the admin>software # prompt, enter the install command and add the
specified slot number. For example:
mp4100# admin software install sw-pack-1 slot 10
successful install to op-108c
The OP-108C module installed in slot 10 is upgraded and starts with the
new software version.

12.6 Upgrading Software using the CLI (SFTP)

The recommended method for downloading software to the flash disk is to use
the file copy command of the CLI environment. This can be done remotely and
does not require booting. Only CL modules need to be reset after this procedure.
The upgrade consists of two stages:
• The application software is downloaded from a PC to the Megaplex-4 flash
disk. This is done via SFTP, using the file>copy command
• The software pack is downloaded from the flash disk to the CL. This is done,
using the admin>software>install command.
Network administrators use the SFTP protocol to securely distribute new
software releases to all the managed Megaplex-4 units in the network from a
central location. A central SFTP server application is installed on a PC on the
network.
Application file is
transferred to
Megaplex
Ethernet
PC with an Active
SFTP Server and Megaplex-4100/4104
Application File
Figure 12-2. Downloading a Software Application File to Megaplex-4 via SFTP
Use the following procedure to download the software release to

Megaplex-4 using the copy command.
1. Verify that the required image file is stored on the PC together with the SFTP
server application.
2. Verify that Megaplex-4 has a valid network connection to the PC
3. Ping the PC to verify the connection.
4. Activate the SFTP server application, as explained in Activating the SFTP
Server.
5. Download the image file to the unit, as explained in Downloading the New
Software Release File to Megaplex-4 Flash Disk.
Note Configuration values shown in this chapter are examples only.
Pinging the PC
Check the integrity of the communication link between Megaplex-4 and the PC by
pinging the Megaplex-4 from the PC.
Activating the SFTP Server

Once the SFTP server is activated on the PC, it waits for any SFTP file transfer
request originating from the product, and executes the received request
automatically.
12-8 Upgrading Software using the CLI (SFTP) Megaplex-4

 To run the SFTP server:

• Activate a third-party SFTP server application.
Downloading the New Software Release File to Megaplex-4 Flash Disk

Use this procedure to download the new software release to the Megaplex-4
flash disk.
 To download an application file to the Megaplex-4 flash disk via CLI:

• At the file# prompt, enter the copy command, as follows:
copy sftp://<SFTP_user_name>:<SFTP_password>@<sftp_ip_address>/
<image_file_name> sw-pack-<index 1..4>
where sftp-ip-address is the IP address of the PC in which the SFTP server is
installed.
• For example, to download the sw-pack.bin file to sw-pack-4 partition from
the PC at 10.10.10.10 with user name admin and password 1234:
mp4100>file# sftp://<admin>:<1234>@10.10.10.10/sw-pack.bin sw-
pack-4
You are prompted to confirm the request:
The application file begins downloading.
Note Issuing the dir command (file# prompt) while installing a new software release
causes the CLI to stop responding during the installation process. The CLI
connection is restored after the SW installation is complete.
 To check the flash memory contents:

• At the file# prompt, enter the dir command, for example:
Megaplex-4 Upgrading Software using the CLI (SFTP) 12-9

mp4100>file# dir
Codes C - Configuration S - Software LO – Log
sw-pack-1 S 6306207 21-12-2010 valid
13:44:58
sw-pack-2 S 6305847 21-2-2011 valid
7:48:0
sw-pack-3 S 6278526 21-2-2011 valid
9:57:47
sw-pack-4 S 6289552 6-1-2011 valid
10:23:13
14:7:35
14:6:51
factory-default-conf C 796 1-1-1970 Read Only
0:0:9
running-config C 0 1-1-1970 Read Only
0:0:9
 To monitor the copy progress:

• At the file# prompt, enter the show copy command, for example:
Src: sftp://mp4100:1234@172.17.150.95/mp4cl2_03_07_72.bin
Dst: sw-pack-4
Started: 14.3.2011 8:50:52
Finally, the application file is downloaded and saved in partition 4 of the
flash disk.
sftp://mp4100:1234@172.17.150.95/mp4cl2_03_07_72.bin copied to
sw-pack-4 successfully
 To display the partition contents:

12-10 Upgrading Software using the CLI (SFTP) Megaplex-4


Name Version Creation Time Actual
---------------------------------------------------------------
--------------
sw-pack-1 1.0.0(1.39) 2012-08-06 00:00:00 ready

Size
(Bytes)
---------------------------------------------------------------
main main.bin 3.00B6 0.1 6306207
asmi54c asmi54c.bin 4.5678 2.3 1898111
m8e1 m8e1.bin 7.6543 9.8 844767
op34c op34c.bin 7.5642 8.9 683210
op108c op108c.bin 2.9637 8.5 1053603
Installing the New Software Release File from the Flash Disk
Once a file is saved on the Megaplex-4100 flash disk, it must be copied to the
CL.2 or I/O modules to replace the current software. The sw-pack file includes the
new software version for all the CL.2 and I/O modules, according to your
purchase order.
You can choose to download the new SW release file to all the CL.2 and I/O
modules installed in the chassis simultaneously. In this case, if the chassis
includes several modules of the same kind, the new software release will be
installed in all of them. If you do not want this to happen, you can issue a
command to install the software in one specific slot.
 To download the new software release file from the flash disk to all the CL.2 and
I/O modules installed in the chassis:
1. At the admin>software # prompt, enter the install command. For example:
mp4100# admin
mp4100>admin# software
mp4100>admin>software# install sw-pack-3
The previous software pack is deleted from the active partition:
deleting file /tffs0/Sw-Pack/Active/m8e1.bin
deleting file /tffs0/Sw-Pack/Active/m8e1Hdr.bin
successfull install to cl-a

successfull install to cl-b
The software pack stored in sw-pack-3 partition is transferred to the
active partition and sent to all the relevant modules that are found in the
Megaplex-4 Upgrading Software using the CLI (SFTP) 12-11

chassis. The I/O modules perform reboot automatically and are now ready
for operation with new software version.
2. To activate the new software release for the CL modules, you must perform
reboot. Disconnect the power, wait a few seconds and then reconnect the
power.
Megaplex-4 is upgraded and starts with the new software version.
mp4100# admin software install sw-pack-1
deleting file /tffs0:2/Sw-Pack/Active/main.bin
deleting file /tffs0:2/Sw-Pack/Active/mainHdr.bin
 To download the new software release file from the flash disk to a specified CL.2
or I/O module:
• At the admin>software # prompt, enter the install command and add the
specified slot number. For example:
mp4100# admin software install sw-pack-1 slot 10
successful install to op-108c
The OP-108C module installed in slot 10 is upgraded and starts with the
new software version.
12.7 Upgrading Megaplex-4 Software via the Boot

Menu
Software downloading may also be performed using the Boot menu. The Boot
menu can be reached while Megaplex-4 performs initialization, for example, after
power-up.
You may need to start the loading from the Boot menu when it is not possible to
activate TFTP using the CLI because, for example, the Megaplex-4 software has
not yet been downloaded or is corrupted.
Caution The Boot menu procedures are recommended for use only by authorized
personnel, because this menu provides many additional options that are intended
for use only by technical support personnel.
You can upgrade via the Boot menu using either the TFTP or the XMODEM
protocol. Two software downloading options are available from the Boot
Manager:
• Downloading using the XMODEM protocol. This is usually performed by
downloading from a PC directly connected to the CONTROL port of the unit.
12-12 Upgrading Megaplex-4 Software via the Boot Menu Megaplex-4

• Downloading using the TFTP. This is usually performed by downloading from a

remote location that provides an IP communication path to an Ethernet port
of Megaplex-4.
Note All the screens shown in this section are for illustration purposes only. Your
Megaplex-4 may display different software versions and port profiles.
The preparations needed for using the TFTP/FTP protocol via the Boot menu are
similar to the preparations needed to download software using the TFTP protocol
via the CLI. The main difference is that you need to define the IP communication
parameters associated with the corresponding Ethernet port (IP addresses and
the associated subnet mask and a default gateway IP address).
Starting Boot Manager

Prior to initiating the VXWORKS Boot Manager functionality, connect the ASCII
terminal or PC with terminal emulation to the CONTROL DCE (serial) port of
Megaplex-4.
 To start VXWORKS Boot Manager:

1. Verify that the *.bin file is stored on the PC with the terminal application.
2. Configure the communication parameters of the selected PC serial port for
asynchronous communication for 115.2 kbps, no parity, one start bit, eight
data bits and one stop bit. Turn all types of flow control off.
3. Turn off Megaplex-4.
4. Activate the terminal application.
5. Turn on Megaplex-4.
Information about the System Boot, Boot version, and information about
CPU, OS-version, BSP version and Boot Manager version is displayed.
The following message appears:
Use '?'/help to view available commands.
Press any key to stop auto-boot....
6. Press any key to stop the auto-boot and get a boot prompt.
The boot prompt is displayed:
[boot]:
7. Press <?> to display the Help list.
The Help list is displayed.
Megaplex-4 Upgrading Megaplex-4 Software via the Boot Menu 12-13

• Commands:
?/help - print this list
p - print boot parameters
c [param] - change boot parameter(s)
v - print boot logo with
versions information
run - load active sw pack and
execute
delete <FileName> - delete a file
dir - show list of files
show <index> - show sw pack info
download <index> [,<FileName|x>] - download a sw pack to
specific index (x - by Xmodem)
set-active <index> - Set a sw pack index to be
the active application
control-x/reset - reboot/reset
Figure 12-3. VXWORKS Boot Manager Help List
8. Press <P> to display all boot parameters.

The boot parameters list appears. A typical boot parameters list is shown
in Figure 12-4. The parameters are described in Table 12-1.
[boot]: p
file name (fn) : vxworks

device IP (ip) : 10.10.10.88
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.10
gateway IP (g) : 10.10.10.10
user (u) : vxworks
ftp password (pw) : *******
device name (dn) : MP4100
quick autoboot (q) : yes
protocol (p) : ftp
baud rate (b) : 9600
Figure 12-4. Typical Boot Parameters Screen
Table 12-1. Boot Parameters
Parameter Command Description
file name fn The binary software pack file (*.bin) name
device ip ip The IP address of Megaplex-4
device mask dm The IP subnet mask of Megaplex-4
server IP sip The TFTP server IP address
gateway ip g The TFTP server default gateway IP-address if the

server is located on a different LAN.
Note: Be sure to select an IP address within the subnet
of the assigned Megaplex-4 IP address.
Note: If no default gateway is needed, for example,
because the TFTP server is attached to the same LAN
as Megaplex-4 being upgraded, enter 0.0.0.0.

Parameter Command Description
user u The user name, as registered at the FTP server.

Note: Displayed only when using FTP Protocol.
ftp password vx The user password, as registered at the FTP server.

Note: Displayed only when using FTP Protocol.
device name dn MP4100
quick autoboot q Enabling or disabling the quick autoboot feature
protocol p The file transfer protocol in use: TFTP or FTP
baud rate b Transmission bit rate (in kbps): 9600, 19200, 115200
Note The CLI commands are case insensitive.
9. Press <C> to change the boot parameters and type valid values in each field.
 Type 'c' to modify all parameters
 Type 'c [parameter]' to modify the specific parameter (for example, to
change the filename to sw-pack.bin, type: c fn vxworks sw-pack.bin).
'.' = clear field; '-' = go to previous field; ^D = quit
file name (fn) : vxworks sw-pack.bin

device IP (ip) : 10.10.10.88
device mask (dm) : 255.255.255.0
server IP (sip) : 10.10.10.10
gateway IP (g) : 10.10.10.10
user (u) : vxworks
ftp password (pw) (blank = use rsh): *******
device name (dn) : MP4100
quick autoboot [y/n] : y
protocol [tftp/ftp] : ftp
baud rate [9600/19200/115200]: 9600
10. To complete the upgrade and log on again, follow the onscreen instructions.
Using the TFTP/FTP Protocol

Use the following procedure to download software release to Megaplex-4 via
TFTP.
 To download software file(s) from the Boot menu to Megaplex-4 via TFTP/FTP:
1. Verify that the *.bin file is stored on the PC with the TFTP server application.
2. Activate the TFTP server application/FTP server.
Note When working with FTP server, the user name and password in Boot parameters
must be the same as defined in FTP server.
3. Turn on Megaplex-4 and enter the Boot menu. Set TFTP or FTP protocol.

4. From the Boot menu, type download <index 1..4> [<FileName>] command to
start downloading the software pack file from the PC to the corresponding
partition of the Megaplex-4 flash disk.
Note [<FileName>] is used if you did not specify the filename in the Boot menu
earlier.
For example: Download the file to sw-pack-2

[boot]: download 2
The file is being copied to sw-pack-2 partition:
File transferring - 7580KB
226 Transfer finished successfully.
Please wait, old file is being erased and written with new one.
File writing to flash: - 7580KB
File downloaded successfully to :2
[boot]:
5. Using dir command, check which partition is currently active. In our example it
is sw-pack-1.
[boot]: dir
SIZE FILE-NAME
796 factory-default-config
6296759 sw-pack-1
6305902 sw-pack-2
6278526 sw-pack-3
6289552 sw-pack-4
Active SW-pack is: 2
6. Use set-active command to activate the partition to which the file has been
downloaded (in our example: sw-pack-2).
[boot]: set-active 2
set-active may take few minutes...
SW set active 2 completed successfully.
The new software release is now stored in partition 2 and will be
activated after reset.
7. Perform one of the following:
 Type “@” or “run”.
The following message is displayed and the new software release is
activated:
[boot]: run
External file header passed validation!
Loading/un-compressing main.bin...
Starting the APPLICATION off address 0x10000...
 Press <Ctrl + X> to perform a cold (hard) reboot with turning power off
and then on.
 Type “reset” to perform a warm (soft) reboot without turning off power.

The following message is displayed:

Are you sure (y/n)?
Press <Y>.
When the downloading process is successfully completed, you will see a
sequence of messages similar to the following:
Instantiating /ram as rawFs, device = 0x20001

Formatting /ram for DOSFS
Instantiating /ram as rawFs, device = 0x20001
Formatting...Retrieved old volume params with %38 confidence:
Volume Parameters: FAT type: FAT32, sectors per cluster 0
0 FAT copies, 0 clusters, 0 sectors per FAT
Sectors reserved 0, hidden 0, FAT sectors 0
Root dir entries 0, sysId (null) , serial number 7d0000
Label:" " ...
Disk with 64 sectors of 512 bytes will be formatted with:
Volume Parameters: FAT type: FAT12, sectors per cluster 1
2 FAT copies, 54 clusters, 1 sectors per FAT
Sectors reserved 1, hidden 0, FAT sectors 2
Root dir entries 112, sysId VXDOS12 , serial number 7d0000
Adding 71349 symbols for standalone.


8. Press <Enter> to start working with the new SW release downloaded.
Note The new parameters take effect only after the reset is completed.
Using the XMODEM Protocol

XMODEM is used to download and upgrade from a PC connected to the CONTROL
DCE port of the Megaplex-4 unit.
Application file is
transferred to
Megaplex-4100
RS-232
Megaplex-4100
PC with a Terminal
Emulation and
Application File
Figure 12-5. Downloading a Software Application File to Megaplex-4 via XMODEM

 To download software release via XMODEM:

1. From the Boot menu, type download <index 1..4> [<FileName>] x command
and press <Enter> to start downloading the software pack file from the PC to
the corresponding partition of the Megaplex-4 flash disk.
Note [<FileName>] is used if you did not specify the filename in the Boot menu
earlier.
For example: Download the file to sw-pack-2.

[boot]: download 2, x
The following message appears:
The terminal will become disabled !!!
Please send the file in XMODEM
2. In HyperTerminal’s Menu bar, click on the icon or choose the Transfer

menu of HyperTerminal, and then select Send File.
The Send File window appears.
3. In the Protocol field, select Xmodem.
4. In the Filename field, enter the prescribed Megaplex-4 software file name and
its path, or click <Browse> to navigate to it.
The Send button becomes available.
5. When ready, click <Send>.
The Xmodem File Transfer window appears and the download starts. A
progress bar and counters let you monitor the progress as illustrated
below.
Figure 12-6. XMODEM File Send Status Window
6. Perform <dir> to verify status of the new image.

7. Use set-active command to activate the partition to which the file has been
downloaded (in our example: sw-pack-2).
[boot]: set-active 2
set-active may take few minutes...
SW set active 2 completed successfully.
The new software release is now stored in partition 2 and will be
activated after reset.
8. When the downloading process is successfully completed, press <@> to exit
the Boot Manager.
9. When the Megaplex-4 initialization ends, the unit loads the new software.
Note The command times out and the send file request is considered failed if you do
not initiate sending the file within approximately 3 minutes.
12.8 Verifying the Upgrade Results

To verify that the upgrade was successful, log on to Megaplex-4 via
HyperTerminal to view the Inventory summary.
 To verify the upgrade result:

• Type: show cards-summary in the config context and verify the active
software version in the SW Ver column.
mp4100>config# show cards-summary
Slot Family Type HW Ver SW Ver
---------------------------------------------------------------
--------------
PS-A Power Supply ps Undefined Undefined
PS-B Not Installed-- Undefined Undefined
CL-A CL CL2 622GbE 0.0/ 0.0 3.00B06/ 0
CL-B CL CL2 622GbE 0.0/ 0.0 3.00B06/ 0
1 Optimux OP-34C 1 1.50B1
2 DSL ASMI54C 2 2.73
3 Optimux OP-108C 4 2.51
4 DSL m8sl 1 1.121
5 E1-T1 M8 E1 1 1.121
6 E1-T1 M8 E1 1 1.121
7 Voice VC8 FXS 10 13.00
8 High Speed HS12N 2 6.00
9 DSL ASMI54C E1+Eth 1 3.00B0
10 E1-T1 M16 E1 1 1.50B1
Note
If downloading failed, repeat the entire procedure.
Megaplex-4 Verifying the Upgrade Results 12-19

12.9 Restoring the Previous Software Version

The procedure of restoring the previous software version (downgrading) depends
on its status inside the flash memory.
 To display the flash memory/partition contents:

Name Version Creation Time Status Actual
---------------------------------------------------------------
sw-pack-1 4.00B6 21-12-2010 13:44:58 Ready Yes
sw-pack-2 4.00B5 21-2-2011 7:48:0 Ready --
sw-pack-3 4.00B4 21-2-2011 9:57:47 Ready --
sw-pack-4 4.00B6 14-3-2011 9:32:56 Ready --

Size
(Bytes)
---------------------------------------------------------------
main main.bin 4.00B6 0.1 6305967

Size
(Bytes)
---------------------------------------------------------------
main main.bin 4.00B5 0.1 6305607

Size
(Bytes)
---------------------------------------------------------------
main main.bin 4.00B4 0.1 6278286

Size
(Bytes)
---------------------------------------------------------------
main main.bin 4.00B6 0.1 6306207
asmi54c asmi54c.bin 4.5678 2.3 1898111
m8e1 m8e1.bin 7.6543 9.8 844767
op34c op34c.bin 7.5642 8.9 683210
op108c op108c.bin 2.9637 8.5 1053603
• If the desired version is stored in one of the four sw-pack partitions, make
this partition active, as described in Installing the New Software Release File
from the Flash Disk.
• If the desired version does not appear in the list, you can restore the
previous software version by following any of the procedures described in
this section, as if it were a new version.
12-20 Restoring the Previous Software Version Megaplex-4

Appendix A
Connection Data
A.1 CONTROL DCE Connectors
Megaplex-4100 Connector
The Megaplex-4100 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. Megaplex-4100 CONTROL DCE Connector Wiring
Pin Function Direction

1 Data Carrier Detect (DCD) From Megaplex-4
2 Receive Data (RD) From Megaplex-4
3 Transmit Data (TD) To Megaplex-4
4 Data Terminal Ready (DTR) To Megaplex-4
5 Signal Ground (SIG) Common reference and DC power supply ground
6 Data Set Ready (DSR) From Megaplex-4
7 Request to Send (RTS) To Megaplex-4
8 Clear to Send (CTS) From Megaplex-4
9 Ring Indicator (RI) To Megaplex-4
Megaplex-4104 Connector
The Megaplex-4104 CONTROL DCE port has a mini USB 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-2. Megaplex-4104 CONTROL DCE Connector Wiring
Pin Designation Function Direction
1 – CAP to GND –
2 TX Transmit Output
3 RX Receive Input
Megaplex-4 CONTROL DCE Connectors A-1

Appendix A Connection Data Installation and Operation Manual
Pin Designation Function Direction
4 DSR RS-232 Enable Input
5 GND Ground –
Control Cables
Straight Control Cable for Megaplex-4100

For Megaplex-4100, RAD supplies a special control cable CBL-DB9F-DB9M-STR, for
connection of the DB-9 CONTROL DCE connector to the supervision terminal. This
cable is wired in accordance with Figure A-4.
9-Pin 9-Pin
Connector TD 3 3 Connector
RD 2 2
RTS 7 7
CTS 8 8
To
CONTROL DCE DSR 6 6 To Terminal
Connector DCD 1 1
RI 9 9
DTR 4 4
GND 5 5
CL Side Modem Side
Figure A-1. 9-Pin Straight Cable Wiring - Connection to CONTROL DCE Connector
Straight Control Cable for Megaplex-4104

For Megaplex-4104, RAD supplies a special control cable, CBL-MUSB-DB9F, for
connection of the mini-USB connector to the supervision terminal. This cable is
wired in accordance with Figure A-4.
A-2 CONTROL DCE Connectors Megaplex-4

Installation and Operation Manual Appendix A Connection Data
Mini-USB 9-Pin
Connector Connector
To RD 2 2 RD
CONTROL DCE To Terminal
TD 3 3 TD
Connector
GND 5 4 DSR
5 GND
CL Side Terminal Side
Figure A-2. 9-Pin Straight Cable Wiring - Connection to CONTROL DCE Connector
Additional Control Cables

The connections of the Megaplex-4100 and Megaplex-4104 CONTROL DCE ports
to a supervision terminal with 9-pin connector are made by means of the above
CBL-DB9F-DB9M-STR and CBL-MUSB-DB9F cables, respectively.
If additional connection options are needed, you can manufacture your own
cables according to the drawings below:
• Connection to a supervision terminal with 25-pin connector: by means of a
cable wired in accordance with Figure A-3.
• Connection to a modem with 25-pin connector (for communication with
remote supervision terminal): by means of a cable wired in accordance with
Figure A-3.
• Connection to a modem with 9-pin connector (for communication with
remote supervision terminal): by means of a crossed cable wired in
accordance with Figure A-4.
For Megaplex-4104, use these cables in conjunction with CBL-MUSB-DB9F.
Megaplex-4 CONTROL DCE Connectors A-3

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-3. 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-4. 9-Pin Crossed Cable Wiring - Connection to CONTROL DCE Connector
A-4 CONTROL ETH Connector Megaplex-4

A.2 CONTROL ETH Connector
Connector Data
Each Megaplex-4 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-3. In the MDIX
state, the receive and transmit pairs are interchanged.
Table A-3. 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 Connectors

The connection to the ALARM connector of Megaplex-4100 is made by means of
a cable provided by the customer, in accordance with the specific requirements of
each site. The alarm cable for Megaplex-4104 (CBL-MP-4104/AR/OPEN/2M) is
supplied by RAD.
Connector Data
The ALARM connector 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.
ALARM connectors are different for different chassis (CL modules):
Megaplex-4 ALARM Connectors A-5

• Megaplex-4100 has a 9-pin D-type female connector

• Megaplex-4104 has a 9-pin flat connector.
Connector pin functions are listed in Table A-4 for Megaplex-4100 and in
Table A-5 for Megaplex-4104.
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.
Table A-4. Megaplex-4100 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
Table A-5. Megaplex-4104 ALARM Connector, Pin Functions
Pin Function
1 Major alarm relay – normally-closed (NC) contact
2 Major alarm relay – center contact
3 Major alarm relay – normally-open (NO) contact
4 Minor alarm relay – normally- closed (NC) contact
5 Minor alarm relay – center contact
6 Minor alarm relay – normally-open (NO) contact
7 +5V auxiliary output (through 330 Ω series resistor)
9 Ground
A-6 ALARM Connectors Megaplex-4

CBL-MP-4104/AR/OPEN/2M
The CBL-MP-4104/AR/OPEN/2M alarm relay cable serves for connecting the 9-pin
Molex connector to the user alarm equipment. It includes one female Molex 9-pin
connector and one open-ended connector. The cable is 2m (6.5 ft) long. The
figure below shows the cable, the connector pinout and the diagram of dry
contacts.
J1, 9 PIN
(1 x 9)
Brown
9 Major Relay - Normally closed (NC)
Black
8 Major Relay - Central Contact
Gray
7 Major Relay - Normally open (NO)
Purple
6 Minor Relay - Normally closed (NC)
Blue
5 Minor Relay - Central Contact
Green
4 Minor Relay - Normally open (NO)
Yellow
3 +5V auxiliary output
Orange
Red
1
Molex
Connector Pin
Figure A-5. CBL-MP-4104/AR/OPEN/2M Cable
A.4 CL CLOCK Connector
Connector Data
The CLOCK interface located on CL modules has one RJ-45 eight-pin connector.
Table A-6 lists the connector pin functions.
Table A-6. 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
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.
Megaplex-4 CL CLOCK Connector A-7

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-6.
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-6. 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.
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-7.
Table A-7. 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
A-8 Power Connectors Megaplex-4

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-8, together with a view of the connector
itself. The nominal supply voltage appears in the table under the connector.
Table A-8. 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.
Megaplex-4 Power Connectors A-9

A-10 Power Connectors Megaplex-4

Appendix B
I/O Modules
B.1 Megaplex-4 I/O Modules

This appendix summarizes the I/O modules operating in the Megaplex-4 chassis
with CLI management. The main features, applications and installation procedures
for these modules are described in a separate manual (Megaplex-4 I/O Modules
Installation and Operation Manual). This manual also describes the installation
and operation procedures for the MPF device providing power feed to remote
modems and repeaters in conjunction with ASMi-54C modules.
For the same modules operating in the Megaplex-4100 chassis with menu
interface, or for modules operating in the Megaplex-2100/2104 chassis (modules
shared by Megaplex-4 and Megaplex-2100/2104), refer to the corresponding
module Installation and Operation Manual.
The I/O modules in the Megaplex-4 I/O Modules Installation and Operation Manual
are organized into the following groups:
Table B-1. Megaplex-4 I/O Modules
Chapter Name Description
Chapter 1. Alarm Relay ACM Alarm and diagnostics module with four outbound relays
Modules
TP (Teleprotection) 4-input, 8-output port teleprotection module with

selectable trip voltage
Chapter 2. E1, T1 and T3 M16E1, M16T1 16-port E1 or T1 modules

Modules
M8E1, M8T1 8-port E1 or T1 modules with 3 Ethernet ports
T3 T3 multiplexer module
Chapter 3. Ethernet and M-ETH 8-port GbE interface module

Pseudowire Modules
MPW-1 TDM pseudowire access gateway with 3 Ethernet ports
Chapter 4. High-Speed, HS-6N, HS-12N 6- or 12-port n x 64 kbps high speed module

Low-Speed and ISDN
HS-703 4-channel Codirectional data module
Modules
HSF-2 2-port fiber optic teleprotection interface module
HS-RN 4-port sub-DSO low speed module
HS-S 4-channel ISDN “S”-interface module
HSU-6, HSU-12 6- or 12-port IDSL modules
Megaplex-4 Megaplex-4 I/O Modules B-1

Appendix B I/O Modules Installation and Operation Manual
Chapter Name Description
LS-6N, LS-12 6- or 12-port low speed modules
Chapter 5. Optimux OP-108C Dual 4 x E1 and Ethernet fiber multiplexer module

Modules
OP-34C 16 x E1(E3) and Ethernet fiber multiplexer modules
Chapter 6. Ringers and Ringer-2100R DC power supply module for DC feed and up to 32 voice
Power Supplies channel ring voltages
MPF Standalone Power Supply for ASMi-54C Modules
Chapter 7. SHDSL ASMi-54C 8-port SHDSL.bis module with 2 Ethernet ports

Modules
ASMi-54C/N 8-port SHDSL/SHDSL.bis module with 2 Ethernet ports and
8 E1 ports
M8SL 8-port SHDSL E1 module with 3 Ethernet ports
SH-16 16-port SHDSL.bis EFM module with E1 and PW support
Chapter 8. Versatile VS Modules

Modules
VS-12 12-port serial module with 2 Ethernet ports
VS-6/BIN 6-port serial module with 8 binary in/out command ports

and 1 Ethernet port
VS-6/C37 6-port serial module with 2 fiber optic C37.94 ports and 1
Ethernet port
VS-16E1T1-EoP 16-port E1/T1 module with EOP support
VS-16E1T1-PW 16-port E1/T1 module with pseudowire support
VS-6/E1T1 6 serial data ports, 8 E1/T1 ports and 1 Ethernet port
VS Voice Modules
VS-6/E&M 6-port serial module with 4 E&M voice ports and 1

Ethernet port
FXS/E&M Voice module with 4 E&M ports and 8 FXS ports
VS-6/FXO 6-port serial module with 8 FXO voice ports and 1

Ethernet port
VS-6/FXS 6-port serial module with 8 FXS voice ports and 1 Ethernet
port
Chapter 9. Voice Modules VC-4/4A/8/8A/16 4/8/16-port FXS/FXO/E&M PCM and ADPCM analog voice
modules
VC-4/OMNI 4-port PCM omnibus voice module
VC-6/LB 6-port PCM voice module for local battery telephones
Chapter 10. Other D-NFV Distributed network functions virtualization module

Modules
B-2 Megaplex-4 I/O Modules Megaplex-4

Appendix C
Test Plan
C.1 Testing Basic Megaplex-4 Features
Introduction
This appendix describes basic verification tests for Megaplex-4 ver 4.5. The aim is
to perform a series of short tests that check the following:
• Basic functionality:
 Backward Compatibility
 Quick Stress
• Protection
 APS
 LAG
 ERP G.8032
 Ethernet Group
 VC Path
 TDM Group
 I/O Group
• Services
 Ethernet forwarding and traffic management
 Ethernet BERT
 TDM (E1) service
 High-speed serial service
 Low-speed serial service
 Voice service
 802.1ag OAM CFM + Y.1731 PM
 PW-over-ERP service
• Management and system
 ACL
 RADview
 SNMPv3
Megaplex-4 Testing Basic Megaplex-4 Features C-1

Appendix C Test Plan Installation and Operation Manual
 Clock Source.
Note All tests should pass if the following procedures are performed precisely.
Testing Time Estimation

The following table lists estimated test time by feature and setup.
Table C-1. Testing Time Estimation
Device Setup A Setup B Setup C Setup D Setup E Setup F Setup G Setup H
Backward
4h 6h 8h 4h 8h 4h
Compatibility
Quick Stress 4h 4h 4h 4h
APS 2h
LAG 2h
ERP G.8032 2h
Ethernet group
2h
protection
VC path protection 2h
TDM group
2h 2h
protection
I/O group protection 2h
Ethernet forwarding
and traffic 8h
management
Ethernet Bert 2h
TDM 2h 2h
High speed serial 2h 2h
Low speed serial 2h
Voice 2h
802.1ag & Y.1731 4h
Teleprotection 3h
ACL 2h, any setup
SNMPv3 2h
PW 2h
Clock Selection 2h 2h
RADview EMS 2h total, all setups
Ethernet over 4h
SDH/SONET
C-2 Testing Basic Megaplex-4 Features Megaplex-4

Installation and Operation Manual Appendix C Test Plan
Required Equipment
Table C-2 lists devices required for conducting the tests.
Table C-2. Required Equipment
Device Setup A Setup B Setup C Setup D Setup E Setup F Setup H Total
Megaplex-4100 1 3 5 1 6 2 1 19
CL.2 modules 2 6 11 4 23
CL.2/A modules 10 2 2 13
I/O modules
ASMi-54C E1+ETH 1 4 5
ASMi-54C E1 1 10 11
ASMi-54C 1 2 3
M16T1 3 12 15
M8T1 3 2 5
M8E1 5 5
MPW-1 5 5
M-ETH 3 3
OP-108C 2 2
VC-6/E&M 1 1
VC-6/FXS 3 3
VC-8/FXS 2 2
VC-4/FXO 1 1
HS-12N 2 2
HS-6N 2 2 4
HS-RN 4 2 1 7
HSF-2 5 5
Megaplex-2100 1 1
I/O modules
HSF-1 1 1
HS-2 1 1
ML-2T1 2 2
VC-6/E&M 1 1
VC-6/FXO 1 1
HS-RN 1 1
Other equipment
ASMi-52 Mux 4 4
ASMi-52 4 4
ASMi-54L 4 12 16
ASMi-54 6 6

Device Setup A Setup B Setup C Setup D Setup E Setup F Setup H Total
ASMi-52L 14 36 50
OP-108 2 2
OP-108L 2 2
FCD-E1L 3 3
DXC-4 1 1
SecFlow-4 1 1
ETX-205A 1 1
ETX-204A 1 1
ETX-202 1 1
FlexDSL Repeater 12 12
HBT 12 6 2 12 30
LBT 4 4
Ixia Ports 6 5 8 2 21
PC 1 1 1 1 1 1 6
Telephone set 7 2 9
Cisco switch 1 1
Egate generator 1 1
FireBerd tester 4 4
Ethernet switch 1 1
VSC 1 1
RADview 1 station for all setups
management
station
Test Setups
The Test plan includes 8 setups (A to H) for testing various Megaplex-4 features
and services. Each setup description also includes the list of features/services
designed to be tested on it. Only those features/services that have detailed
descriptions in this document are listed in these lists.
ACL functionality (see Testing ACL Functionality) can be tested on any setup and
is not included in these lists.
RADview test should be performed on each setup.
Note In its turn, the description of each feature/service includes the list of setups
designed for its testing. However, some services of the same type are present in
other setups not appearing in this list. These services take part in backward
compatibility and quick stress tests which are performed on all the setups. For
example, while high speed serial services are tested on Setups A and F, some of

them are also configured in Setup B where they are tested during the overall
backward compatibility and quick stress tests.
Setup A. SHDSL Hub. Extended Serial, Ethernet and TDM

services over SHDSL with Power Feeding
This setup is intended for testing the following:
• Backward compatibility (see Testing Backward Compatibility)
• Quick stress (see Testing Quick Stress)
• RADview (see Testing RADview)
• TDM (E1) services (see Testing TDM (E1) Services)
• High speed service (see Testing High Speed Serial Services).
Tests #1 #2, #3, #4, #8, #9, #10, #11, #12 are shown in colors in the figure below
and their testing is described in the respective sections:
• #1 #3, #4, #9, #11, #12; Testing High Speed Serial Services
• #2, #3, #8, #10, #12: Testing TDM (E1) Services
Note that Tests 3 and 12 consist of two parts: high speed service and TDM (E1)
service. These parts are shown in the figure as Test 3 V.35, Test 12 V.35, Test 3
E1 and Test 12 E1, respectively.
Other services (not colored in the picture) may also be used in backward
compatibility and quick stress tests.
Figure C-1 illustrates the test layout.
Below is the script used for Setup A configuration.

Test 12 V.35
Telefonica Setup
RPT - 8
Test 12 E1
Test 10
RPT - 6
HBT-9
ASMi-52 HBT-12 HBT-3
RPT - 5 V.35
MUX 1 V.35 V.35
E1 V.35
Test 12 V.35
Test 12 E1 + Test 12 V.35
Test 9
Test 12 E1
HBT-4
Test 10
HBT-1
V.35 V.35
Test 9
Test 12 V.35
Test 4
Test 3 V.35
HBT-11
Test 1
ASMi-52 ASMi-52 V.35
Mux 2 MUX 3 Test 11 V.35
Test 11
1 2 3 4
E1 V.35 V.35 E1
RPT - 7 5 6 7 8 1 2 3 4
SHDSL 5 6
Test 11 E1
7 8
Test 12
9 10 11 12
HBT E1-i
1 2 3 4
5 6 7 8
Slot 10 HS-12/N
HBT Test 10
V.35
1 2 3 4
Slot 9
ASMi-52 #2
5 6
1 2 3 4 7 8
FCD-E1L-1 5 6 7 8 E1
9E110 11 12
Test 11 E1
E1
ASMi-52 Slot 7
Mux 4
E1 V.35
Test 12 E1 Slot 10
ASMi-52 #3
ASMi-52 #4
ASMi-52 #1
E1
V.35
V.35
172.17.151.121 CL-B
V.35
E1
E1
GBE
CL-A 1 2
Test 3 V.35 + Test 3 E1
RPT - 9 Ixia
Slot 2 Test 14
Test 2
Test 1 SHDSL
Test 2
RPT - 10 RPT-2
4 3 2 1
8 7 6 5 4 3 2 1 SHDSL
Test 4 Test 4
RPT - 12 8 7 6 5
Test 5 11,392 Managed RPT-4

Test 3 V.35 1 2 ETH
4 3 2 1
Test 3 E1 RPT - 11 E1-i
8 7 6 5
Test 2 Test 2 4 3 2 1
8 7 6 5 E1-i
RPT - 3
Test 7 + Test 13
4 3 2 1
Test 14 + Test 8
8 7 6 5 E1 4 3 2 1
8 7 6 5 E1
Slot 4
Test 6
Non-Managed
E1
HBT 530 FCD-E1L-2 Test 3 E1 Test 7
ASMi-54L-3
44 3 2 1
Test 8
Test 13
FCD-E1L-3
Data Flow RPT - 1
E1
ASMi-54L-4
Test 6
V.35 : Test 1, Test 4, Test 9 4 3 2 11

V.35 + E1 Framed :Test 3, Test 11 HBT-7 530
ETH : Test 5, Test 13, Test 14 ASMi-54L-1
E1 unframed : Test 6, Test 8 4 3 2 1
Test 14
Test 13
E1 unframed : Test 10 à Test 12 à Test 2 HBT-8 E1

ASMi-54L-2
4 3 2 1
Ixia Ixia HBT-6 Ixia
Clock Setting
FCD-E1L-1 Internal
MP Receives from E1 7/5
Test 1 V.35 only; 31TS transparent; data-rate 2048 kbps. HBT à HS-12N 10/1 à ASMi-54C/N E1-i 4/1 à SHDSL slot 4 line 1,2 à Repeater 9 à ASMi-52 1 Loop.
Test 2 E1 unframed; data-rate 2048 kbps. Test 12 à ASMi-54C/N E1 4/3 à ASMi-54C/N E1-i 4/3 à SHDSL slot 4 line 3,4 à Repeater 10 à ASMi-52 2 Loop.
V.35 17-31 transparent data rate 2048 kbps. HBT HS-12N 10/3 à ASMi-54C/N E1-i 4/5 à SHDSL slot 4 line 5,6 à Repeater 11 à ASMi-52 3 Loop.
Test 3
E1 framed G.732S 1-15; data rate 2048 kbps. HBT (530) à FCD-E1 à ASMi-54C/N E1 4/5 à ASMI54C/N E1-i 4/5 à SHDSL slot 4 line 5,6 à Repeater 11 à ASMi-52 3 Loop.
Test 4 V35 30TS loop to E1. HBT à HS-12n 9/3 à ASMI54C/N E1-I 4/7 à SHDSL slot 4 line 7,8 à Repeater 12 à ASMI52 4 Loop.
Test 5 ETH only; classifier match all; data-rate 11392 kbps; single IP (EoC). Ixia A à ASMi-54L 1 ETH Port 2 à Repeater 1 à SHDSL slot 2 line 1,2 à PCS 2/1 à ASMi-54C/N ETH 2/1 à Ixia.
Test 6 E1 unframed; data-rate 2176 kbps. HBT à ASMi-54C/N E1 2/3 à ASMi-54C/N E1-i 2/3 à SHDSL slot 2 line 3,4 à Repeater 2 à ASMi-54L 2 à Loop.
Test 7 E1 framed g732s transparent 1-10 21-30. HBT (530) à FCD-E1 3 à ASMI54C/N E1 2/5 à ASMI54C/N E1-I 2/5 à SHDSL slot 2 line 5,6 à Repeater 3 à ASMI54L 3 Loop.
Test 8 E1 unframed. HBT-8 à ASMI54C/N E1 2/7 à ASMI54C/N E1-I 2/7 à SHDSL slot 2 line 7,8 à Repeater 4 à ASMI54L 4 Loop.
Test 9 V35 only 31TS data-rate 2048. HBT à HS-12n 9/1 à ASMI54C/N E1-i 7/2 à SHDSL slot 7 line 1,2 à Repeater 5 à ASMI52 MUX 1 Loop.
Test 10 E1 unframed data-rate 2176. HBT à ASMI54C/N E1 7/3 à ASMI54C/N E1-I 7/3 à SHDSL slot 7 line 3,4 à Repeater 6 à ASMI52 MUX 2 à Test 12.
E1 framed g732s transparent 1-10 21-30. HBT (530) à FCD-E1 1 à ASMI54C/N E1 7/5 à ASMI54C/N E1-I 7/5 à SHDSL slot 7 line 5,6 à Repeater 7 à ASMI52 MUX 3 Loop.
Test 11
V35 31TS (Clock from E1 port) data-rate 3456. HBT à HS-12n 9/10 à ASMI54C/N E1-i 7/6 à SHDSL slot 7 line 5,6 à Repeater 7 à ASMI52 MUX 3 Loop.
E1 unframed. Test 10 à ASMI54C/N E1 7/7 à ASMI54C/N E1-I 7/7 à SHDSL slot 7 line 7,8 à Repeater 8 à ASMI52 MUX 4 à Test 2.
Test 12
V35 31TS data-rate 4096. HBT à HS-12n 9/12 à ASMI54C/N E1-i 7/8 à SHDSL slot 7 line 7,8 à Repeater 8 à ASMI52 MUX 4 Loop.
Test 13 ETH classifier match all data-rate 11392 single IP (EoC). Ixia à ASMI54C/N ETH Port 2/2 à PCS 2/5 à SHDSL slot 2 line 5,6 à Repeater 3 à ASMI54L 3 ETH 4 à Ixia.
Test 14 Match Vlan20 data-rate 11392 single IP (EoC). Ixia Port B à CL-a/1 GBE à PCS 2/7 à SHDSL slot 2 line 7,8 à Repeater 4 à ASMI54L 4 ETH Port 1 à Test 7.
Figure C-1. Testing TDM (E1) over SHDSL and High Speed Serial Services

Setup B. Multiservice over Linear SONET Topology

This setup includes 3 Megaplex-4 sites (A, B, C) and one Megaplex-2100 site (D)
and is intended for testing the following:
• Ethernet group protection (Test 1) (see Testing Ethernet Group Protection )
• FXS Voice service ( Test 4) (see Testing Voice Services)
• Low speed service (Tests 2,3,5) (see Testing Low Speed Serial Services)
• RADview (see Testing RADview).
Tests 1 to 5 are shown in colors in the figure below and also shown in detail in
the respective sections. Other services (not colored in the picture) may be also
used in backward compatibility and quick stress tests.
Below are the scripts used for Setup B configuration of Megaplex devices.

Figure C-2. Testing Ethernet Group Protection, Low Speed Serial Services and FXS
Voice Services
Setup C. Four G.8032 Rings and SDH/SONET Ring

This setup is used to test the following:
• Backward Compatibility (see Testing Backward Compatibility )
• ERP G.8032 (see Testing ERP (G.8032))
• TDM Group Protection – Traffic Duplication (see Testing TDM Group
Protection)
• SNMPv3 (see Testing SNMPv3 Functionality)

• Pseudowire service over ERP (see Testing Pseudowire Services over ERP)
• Clock Selection (see Testing Clock Selection)
G.8032 GBE Ring
MP E
-41 100
00 -4
D MP
SE1 SE4
M8-E1 M8-E1
CL-A
CL-A
SP6
SP5
A1 A1
MPW A1 G.8032 Ring A1 MPW
SP7 over
TP FXS SP4
CL-B
CL-B
B1 B1
B1 SDH VCG B1
SE1 SE4
SP7
M-ETH TP
S-Clock A
S-Clock B
Clock Selection Test:

Sources 1-8
CL-A1 SDH CL-B1 SDH
CL-A1 GBE CL-B1 GBE FXS SP3 SP4
G.8032 MPW PW over ERP
SP1
Ring SE1
M-ETH CL-A CL-B HS-6N HBT-1
Over HS-RN SP2
SE4
M-8E1 SE2 SP5 SP6
M-ETH CL-A2 GbE CL-B2 GbE
CL-A2 SDH CL-B2 SDH
MP-4100 A
ERP Tests
SE1 SE3
M-ETH Traffic Duplication Test SE1
CL-A1
M8-E1 M8-E1
CL-A1
GbE
GbE
CL-A1
CL-A1
SDH
SDH
PW over ERP
Duplication
Duplication
SP1
HBT-1 HS-6N 2 HS-RN SP2
1
1
CL-A2
2
SDH
CL-A2
SDH
MPW-1 MPW-1
CL-A2
CL-A2
GbE
GbE
SP3 FXS
S-Clock A S-Clock A
S-Clock B S-Clock B
MP-4100 C MP-4100 B
SDH Ring
SecFlow-4 G.8032 GBE Ring ETX-205A
Legend:
Clock Selection Test
PW over ERP SE1
Traffic Duplication Test
SE# - ETH Service
SE1 SE3
ERP Tests SP# - PW Service
SE2
Figure C-3. Testing Traffic Duplication, ERP G.8032, SNMPv3 and Clock Selection

Setup D. Ethernet Aggregation for E-LAN, E-TREE and E-Line

services with LAG
• Backward Compatibility (see Testing Backward Compatibility)
• Ethernet Forwarding and Traffic Management (E-TREE, E-LAN, E-Line modes)
(see Testing Ethernet Forwarding and Traffic Management)
• Ethernet BERT (see Testing Ethernet BERT Functionality)
• LAG protection (see Testing the LAG)
• 802.1ag implementation (see Testing OAM CFM and Y.1731 PM
Functionalities)
• Y.1731 implementation (see Testing OAM CFM and Y.1731 PM Functionalities)
• Cisco switch interoperability
Below is the script used for Setup D configuration.

Cisco Switch
MNG
LAG
1
802.1ag + Y.1731 Test
Ixia 6
ETX-204A Ixia
2
1 2 1 2 1 2 1 2 1 2 1 2 1 2
GBE 2 GBE 1 GBE 1 GBE 2
ETH ETH ETH ETH ETH
MP-
MNG MNG
I/ O 1 I/ O 2 I/O 3 I/O 4 I/O 5 I/ O 6 I/O 10

ASMi- ASMi- OP- OP- ASMi- ASMi- ASMi-
54C 54CN 108C 108C 54CN 54CN 54CN
0B
CLX A CLX B
S S S S S
H H H H H
E E E E
D D D D D
1 1 LINK LINK LINK LINK 1 1
S S S 2 2
S S
1 1
L L L L L
1/1 1/2 1/3 1/4 10/1 10/2 10/3 10/4

2W
2/1 2/3 2/5 2/7

Ethernet
BERT 2W 2W 2W 2W
Test 4W 4W 4W 4W 3/1/1 4/1/1
3/3/1 4/3/1
OP-108L/BM/U/ETH/FC/13L #1
ASMI-54L #12 - 4ETH/4W/E1
ASMI-54L #11- 4ETH/4W/E1
OP-108L/BM/U/ETH/FC/13L #4
OP-108L/U/ETH/FC/13L #2
OP-108/U/ETH/FC/13L #3
ASMI-54L #10 - 4ETH/4W
ASMI-54L #9 – 4ETH/4W
ASMI-54L #1 – 4ETH/2W
ASMI-52L #4
ASMI-52L #3
ASMI-52L #2
ASMI-52L #1
Ethernet Forwarding and Traffic
Management
Legend:
802.1ag + Y.1731 Test
LAG
5 4 3
Ethernet BERT Test
Ethernet Forwarding and Traffic Management Ixia
Figure C-4. Testing E-TREE, E-LAN and E-Line Ethernet Forwarding, 802.1ag and
Y.1731 Implementation, LAG Protection, Ethernet BERT, Cisco Switch
Interoperability

Setup E. Multiservice over SONET Ring

This setup includes 5 Megaplex-4 sites (A, B, C, D, E) and is intended for testing
the following:
• VC path protection (see Testing VC Path Protection)
• TDM group protection (see Testing TDM Group Protection)
• Clock selection (see Testing Clock Selection).
Schematic diagrams for testing the three last features are shown in colors in the
figure below and also described in the respective sections. Other services (not
colored in the picture) may also be used in backward compatibility and quick
stress tests.
Below are the scripts used for Setup E configuration.

9-16
1-8
Clock Source
M16
CL-A
T1 M8
CL-1
T1
Clock Selection
Egate Gen.
MP-4100 A
TDM Group
VC4 FXO
S-Clock A
VC8 FXS
M16-T1
M16-T1
M16-T1
M16-T1
M16-T1
M16-T1
M8-T1
FB B ST
Protection CLK 1 FB E
VC Path ST
Protection 1 2 3 4 5 7 8 9 10 CLK 2
HBT 1 1
M1
8 6- 6-T
M1 T1 M1
6-T A2 B2
1
MP-4100 B MP-4100 E
A1 B1
B2 A2
B1 A1
S- kA
S-CClock loc B
loc A
kB
A2 A1 B1 B2 S-CClock
S-
OC-12
Ring
MP-4100 C MP-4100 D
B1 A1
B2 A2
A1 B1
oc k B
kA
Cl loc
1
-T
S -C
B2
16
A2
S
M
-
1
VC
8
FB C
FX
S- -Clo T1
oc k A
S
8-
M
B
Cl c
M
16
k
Legend:
-T
1
S
VC Path Protection
TDM Group Protection
Clock Selection FB D
Figure C-5. Testing TDM Group Protection, VC Path Protection and Clock Selection
Setup F. End-to-End Serial, Ethernet and TDM Services over

SHDSL and Extended STM-1/OC-3 link
• APS protection (see Testing APS)
• TDM (E1) services (see Testing TDM (E1) Services)
• High speed services (see Testing High Speed Serial Services)


Services #1 to #11 are shown in colors in the figure below and their testing is
also described in the respective sections. Other services (not colored in the
picture) may also be used in backward compatibility and quick stress tests.
Below are the scripts used for Setup F configuration.
Service 1 HBT-1 128 V35-HS ASMi-52L 1-1 384 TS0 looped G732N 384 TS0 looped G732N ASMi-52L 3-1 E1
Service 4 V35-HS ASMi-52L 1-4 Lines 1-2 E1-i1 TS 1-2 E1-i1(1:1:1) TS 1-2 TS 1-2 E1-i6(1:1:1) E1-i1 TS 1-2 Lines 1-2 E1
HBT-4 640 640 TS0 looped G732N 640 TS0 looped G732N ASMi-52L 3-4
Lines 3-4
Lines 5-6 1IO-1E1-i3 TS 1-4
E1-i5 TS 1-6 E1-i1(1:1:1) TS 7-12 TS 7-12 E1-i6(1:1:1)
E1-i3 TS 5-8
E1-i5 TS 1-6IO-3
3 Lines 3-4
Lines 5-6
Lines 7-8 E1-i7 TS 1-10 E1-i1(1:1:1) TS 13-22 TS 13-22 E1-i6(1:1:1) E1-i7 1-10 Lines 7-8
Service 6 HBT-6 1536 V35-HS ASMi-52L 2-2 1536 TS0 looped G732N
1536 TS0 looped G732N ASMi-52L 4-2 E1
Lines 1-2 E1-i1 TS 1-16 E1-i2(1:1:2) TS 1-16
Service 7 HBT-7 1920 V35-HS ASMi-52L 2-3 1920 TS0 looped G732N Lines 3-4 E1-i3 TS 1-24 E1-i3(1:1:3) TS 1-24
TS 1-16 E1-i7(1:1:2) E1-i1 TS 1-16 Lines 1-2 1920 TS0 looped G732N ASMi-52L 4-3 E1
Lines 5-6 2IO-2 E1-i5 1-30 E1-i4(2:1:1) TS 1-30
TS 1-24 E1-i8(1:1:3) E1-i3 TS 1-24
IO-44 Lines 3-4
E1-i7 Unfram. E1-i5(2:1:2) Unframed
TS 1-30 E1-i9(2:1:1) E1-i5 TS 1-30 Lines 5-6 ASMi-52L 4-4 E1
Service 8 HBT-8 Unframed E1 ASMi-52L 2-4 TS0 Transparent G732N Lines 7-8 Unframed E1-i10(1:1:2) E1-i7 Unfra. Lines 7-8
TS0 Transparent G732N
Service 9 HBT-9 Unframed E1 ASMi-52L 5-1 TS0 Transparent G732N CL-A/1 CL-A/2 TS0 Transparent G732N ASMi-52L 6-1 E1
Lines 1-2 E1-i1 E1-i11(1:2:3) Unframed
ASMi-52L 6-2 E1
E1 ASMi-52L 5-2 Lines 3-4 E1-i3 E1-i12(1:3:1) Unframed Unframed E1-i15(1:2:3) E1-i1 Lines 1-2
Lines 5-6 5IO-5 E1-i5 E1-i13(1:3:2) Unframed Unframed E1-i16(1:3:1) E1-i3
IO-66 Lines 3-4
E1 ASMi-52L 5-3 Lines 7-8 E1-i7 E1-i14(1:3:3) Unframed Unframed E1-i17(1:3:2) E1-i5 Lines 5-6 ASMi-52L 6-3 E1
Unframed E1-i18(1:3:3) E1-i7 Lines 7-8
E1 ASMi-52L 5-4 ASMi-52L 6-4 E1
E1 ASMi-52L 7-1 512 TS0 Transparent

Lines 1-2 E1-i1 TS 1-6 E1-i19(1:4:1) TS 1-6 TS 1-15,17-21 E1-i23(1:4:1) E1-i1 1-15,17-21 Lines 1-2 1408 TS0 Transparent ASMi-52L 8-1 E1
Lines 3-4 E1-i3 TS 1-10 E1-i20(1:4:2) TS 1-10 TS 1-15,17-25 E1-i24(1:4;2) E1-i3 1-15,17-25 Lines 3-4
E1 ASMi-52L 7-2 768 TS0 Transparent Lines 5-6 7IO-7
E1-i5 TS 1-12 E1-i21(1:4:3) TS 1-12 TS 1-15,17-27 E1-i25(1:4:3) IO-88
E1-i5 1-15,17-27 Lines 5-6 ASMi-52L 8-2
1664 TS0 Transparent E1
E1 MF Lines 7-8 E1-i7 1-15,17 E1-i22(1:5:1) TS 1-15,17 TS 1-15,17-29 E1-i26(1:5:1) E1-i7 1-15,17-29 Lines 7-8
E1 ASMi-52L 7-3 896 TS0 Transparent 1792 TS0 Transparent ASMi-52L 8-3 E1
E1 ASMi-52L 7-4 1152 TS0 Transparent 1920 TS0 Transparent ASMi-52L 8-4 E1
Lines 1-2 E1i-1 TS 1-12 IO-9 E1-1 TS 1-12 Lines 1-2

Lines 3-4 E1i-3 TS 1-12 IO-9 E1-3 APS
Lines 5-6 9IO-9 TS 1-12
TS 1-12 IO-10 E1-5 E1i-5 TS 1-12 10 Lines
IO-10 3-4
Lines 5-6
E1 ASMi-52L 9-1 + IO-10 E1-7 E1i-7 E1
Lines 7-8 TS 1-12 Lines 7-8 ASMi-52L 10-1
TDM
E1 ASMi-52L 9-2 Group ASMi-52L 10-2 E1
Protection
Service 11
TS 1-10 Data. TS 12-13 Voice
CL IO-3 VC-8 FXS CL-B/1 CL-B/2
IO-1 ML-2 E1 IO-4 VC-8 FXS
IO-2 ML-2 E1 IO-5 HS-12N/V.35 Service 11

HBT-11.2 Megaplex-4100
HBT-11.1
Megaplex-2104
HBT-10
Service 10
Service 11
Figure C-6. End-to-End Serial, Ethernet and TDM Services over SHDSL and
Extended STM-1/OC-3 Link
Setup G. Teleprotection Service

See Testing Teleprotection Functionality.
Setup H. Ethernet over SDH/SONET Service

See Testing Ethernet over SDH/SONET Service.
Testing Backward Compatibility

The objective of the test is to verify the backward compatibility of the setup
configuration.
Test Setup and Duration

Test durations for different setups are as follows:

• Setups A, D, F – 4 hours
• Setup B – 6 hours
• Setups C, E – 8 hours
Test Procedures
Table C-3 details the procedure of the backward compatibility test for startup.
Table C-3. Backward Compatibility Test Procedure
# Action Expected Result Result
1 Power up the setup. All the services are up and error-free.

Monitor the test equipment (HBT, The management is functional.
Ixia, Fireberd etc). No active alarms are displayed.
Check Ping and Telnet connectivity.
Open RADview for all the DUTs in
the setup.
Table C-4 details the backward compatibility test for upgrade procedures.
Note The procedures below describe the upgrade for a GA version. When upgrading a
Beta or an Alpha version, it should be done on a 'clean' setup as follows:
• Delete startup-config and user-config files.
• Perform admin reboot command.
• Perform upgrade.
• Download the previous database.
Table C-4. Backward Compatibility Test for Upgrade Procedure
1 Transfer the new SW version to all Files are transferred successfully.

the DUTs in the setup using TFTP.
2 Install the new SW version. The new SW is installed successfully to both

CL-A and CL-B in all the DUTs.
Management and data services are not
interrupted during the installation.
3 One by one, reset the active CL While rebooting the active CL, the standby CL
modules in all the DUTs to load the becomes active.
new SW version. Minimum disruption of data services and
management.
When the active CL is up again, it is updated
with the new SW version.

4 One by one, reset the standby CL While rebooting the standby CL, the active CL is
modules in all the DUTs to load the already operative with the new SW version.
new SW version. Minimum disruption of data services and
management.
When the standby CL is up again, it is updated
with the new SW version.
5 If not already done, upgrade Read is performed successfully.

RADview to support the new Agent
version.
Perform read from RADview.
6 Using CLI, delete the startup and SNMP connectivity is regained.

user configurations.
Using CLI, perform admin reboot
command.
Configure the IP address to regain
SNMP connectivity.
7 Perform update from RADview Update is performed successfully.

without doing any change. No disruption in management and data
services.
No alarms are observed in the system.
Testing Quick Stress

The objective of the test is to verify the robustness of the setup configuration.

Test durations for each of the relevant setups (A, B, E, F) is 4 hours.
Test Procedure
Table C-5 details the procedure of the Quick Stress test.
Table C-5. Quick Stress Test Procedure
1 Power the device down/up 3 times. Services continue to function.
2 Reboot the device 3 times. Services continue to function.
3 Remove and reinsert one of the Services continue to function.

two PS modules.
4 Remove and reinsert the active CL Services continue to function.

module.
5 Remove and reinsert the standby CL Services continue to function.

module.

6 Remove and reinsert some of the Services continue to function.

I/O modules.
7 Disconnect and reconnect some of Services continue to function.

the physical links.
8 Send the attached Ixia script while The device is up with no exceptions or
the device is initializing at 50 Mbps. interruptions.
Testing APS
The objective of the test is to verify the correct functionality of traffic switchover
between two SDH/SONET ports working in APS mode.
Test Duration and Setup

Setup F, 2 hours.
Test Procedure
Table C-6 details the APS test procedure.
Table C-6. APS Test Procedure
1 Perform “show status” command Services are working error-free.

for APS protection. The active links are working links on CL-A/1 and
CL-A/2.
2 Perform the following hit triggers: APS switchover is working properly.

• CL-A/1 link disconnect/reconnect No errors in data transmission are reported
• CL-A/2 link disconnect/reconnect (after switchover)
• CL-B/1 link disconnect/reconnect LOS alarm is reported on the failed link.
• CL-B/2 link disconnect/reconnect Status indication: SF is reported on the failed

link. When the failed link is restored, the status
• CL-A reset
changes to SD and UP.
• CL-B reset
• CL-A remove/insert
• CL-B remove/insert.

3 Using CLI, perform “force-switch- Commands are performed and functional.

to-protection” command.
Perform “force-switch-to-working”
command.
Perform “manual-switch-to-
protection” command.
Perform manual-switch-to-working”
command.
Perform “clear” command on both
protected links.
4 Test RADview operation: Read and Update are functional.

• Perform Read APS is up and functional
• Change parameters in APS Traffic is error-free.
configuration
• Perform Update.
5 Revert to the initial configuration. APS is up and functional, TDM traffic is running
error-free.
Testing the LAG

between two Ethernet ports combined in LAG.

Setup D, 2 hours
Test Procedure
Table C-7 details the LAG test procedure.
Table C-7. LAG Test Procedure
1 Display the LAG status. LAG is up and LACP is synchronized.

Ethernet traffic is running error-free, no packet
loss is detected.
2 Perform the following hit triggers: LAG switchover is working properly.

• CL-A/1 link disconnect/reconnect No errors in data transmission is reported
• CL-B/1 link disconnect/reconnect (after switchover).
• CL-A reset Switchover time is sub-50 msec.
• CL-B reset A LOS alarm indication is reported on the failed

link.
• CL-A remove/insert
• CL-B remove/insert.


• Perform Read LAG protection is up and LACP is synchronized.
• Change parameters in LAG Traffic is running error-free.
configuration.
• Perform Update.
Testing ERP (G.8032)

The objective of the test is to verify the correct functionality of ERP (G.8032)
rings.

Setup C, 1 hour
Test Procedure
Table C-8 details the ERP test procedure.
Table C-8. ERP Test Procedure
1 Perform the following: ERP rings are in idle state.

• Verify that the all the ERP rings Traffic (PW and ETH) is running properly in all
are in idle state ports.
• Send traffic on all the Ethernet Status indications are correct.
and PW services Transition time is sub-50 ms.
• Perform “show status”
command.
2 Disconnect and reconnect the East “Ring State” status changes to “Protected”.
and West port on all the ERP nodes Ethernet and pseudowire traffic is running
one by one to initialize traffic through all relevant ports error-free and
switchover. lossless.
CLK Domain in all the DUTs is locked.
3 On Megaplex A, reset the CL link “Ring State” status changes to “Protected”.

which is part of the idle link. Ethernet and pseudowire traffic is running
through all relevant ports error-free and
lossless.
4 Reset one of the nodes on the idle “Ring State” status changes to “Protected”.
path of Megaplex A. Ethernet and pseudowire traffic is running
through all relevant ports error-free and
lossless.


• Perform Read ERP is up.
• Change parameters in ERP Ethernet and pseudowire traffic is running
configuration through all relevant ports error-free and
• Perform Update. lossless.
Testing Ethernet Group Protection

The objective of the test is to verify the correct functionality of the Ethernet
group protection.

Setup B, 2 hours
Test Procedure
Table C-9 details the Ethernet group protection test procedure (Test #1 in
Setup B). The detailed diagram of the service is shown in the figure below:
MP-A 1/1/2, 1/1/3, 1/1/4

1/2/1, 1/2/3, 1/2/4
MP-B 1/1/2, 1/1/3, 1/1/4
1/2/1, 1/2/3, 1/2/4
M8T1 1/3/1, 1/3/2 1/3/1, 1/3/2
Link A/1 Link A/1 M8T1
ETH Flow VCG#1 9xVT VCG#1 9xVT Flow ETH
Ixia 3/1 Eth Group#1 Eth Group#2 7/2
VCG#1 9xVT VCG#1 9xVT
1/1/2, 1/1/3, 1/1/4 Link B/1 Link B/1 1/1/2, 1/1/3, 1/1/4
1/2/1, 1/2/3, 1/2/4 1/2/1, 1/2/3, 1/2/4
1/3/1, 1/3/2 1/3/1, 1/3/2
MP-B 1/1/2, 1/1/3, 1/1/4

1/2/1, 1/2/3, 1/2/4
MP-C 1/1/2, 1/1/3, 1/1/4
1/2/1, 1/2/3, 1/2/4
M8T1 1/3/1, 1/3/2 1/3/1, 1/3/2
M8T1
Link A /2 Link A /1
ETH Flow VCG#2 9xVT VCG#1 9xVT Flow ETH
Ixia 7/1 Eth Group#1 Eth Group#2 5 /1 Ixia
VCG#2 9xVT VCG#1 9xVT
1/1/2, 1/1/3, 1/1/4 Link B /2 Link B /1 1/1/2, 1/1/3, 1/1/4
1/2/1, 1/2/3, 1/2/4 1/2/1, 1/2/3, 1/2/4
1/3/1, 1/3/2 1/3/1, 1/3/2
Figure C-7. Ethernet Group Protection Test
Table C-9. Ethernet Group Protection Test Procedure

1 Verify that the following Ethernet group The service is up, with no errors or
protection is configured correctly: losses.
Site A
# Eth Group Protection
ethernet-group 1
bind logical-mac working cl-a/1
bind logical-mac protection cl-
b/1
wait-to-restore 10
no shutdown
exit
2 Disconnect the CL-A/1 link on Site B. The service is restored on the

Perform “show status” command for the protection link, with no errors or
Ethernet group protection. losses.
The status indication is switched to the
protection link.
Rx Trail Failure alarm indication is
observed on the GFP ports.
3 Reconnect the CL-A/1 link on Site B. The service reverts to the CL-A/1 link.
No errors are observed.
The status display reports switching
back to the CL-A/1 link.
4 Reset the CL-A module on Site B. The service is restored on the

protection link, with no errors or
losses.
The status indication is switched to the
protection link.
Rx Trail Failure alarm indication is
observed on the GFP ports.
5 Verify that CL-A module is back to action. The service reverts to the CL-A/1 link.
The status display reports switching
back to the CL-A/1 link.
6 On Site B, bind 3 more VT-1.5 to VCG 2 and Rx Trail Failure alarm indication is
perform “commit” observed on the GFP ports on both
Site A and Site B.
The service is switched to the
protection link with maximum loss of
50 msec.
Stable functionality is observed for
5 minutes
7 Add the same 3 x VT-1.5 on Site A and Rx Trail Failure alarm indication
perform “commit”. disappears.
Once wait-to-restore time elapses, the
service returns to the working link with
maximum loss of 50 msec.

Testing VC Path Protection

The objective of the test is to verify the correct functionality of the VC path
protection.

Setup E, 2 hours
Test Procedure
Table C-10 details the VC path protection test procedure. The protection is
configured as follows:
Site B
# VC Path Protection
vc-path 1
name "Group 1"
bind vc-vt protection cl-a/1/1/1/7/4
bind vc-vt working cl-b/1/1/1/7/4
no revertive
wait-to-restore 4
no shutdown
exit
Table C-10. VC Path Protection Test Procedure
1 Verify that VC path protection is The service is up and error-free.

configured according to the above.
2 On Site B, disconnect the CL-B/1 The service is restored on the protection link.
link. No errors are observed.
Perform “show status” command The status display indicates switching to the
for VC Path protection. protection link.
AIS alarms on the VC/VTs participating in VC
path protection groups are observed on sites C,
D and E.
3 On Site B, reconnect the CL-B/1 link Nothing happens.

The service continues to work on the
protection link.
4 Verify that CL-B/1 is up and The service switches back to the working link
synchronized. on CL-B/1.
Disconnect the SONET segment No errors are observed.
between C-D or D-E. AIS alarm is observed on the VC/VT protection
path.

5 On Site B, reset the CL-B module. The service is restored on the protection link.
Perform “show status” command No errors are observed.
for VC Path protection. The status display indicates switching to the
protection link.
AIS alarms on the VC/VTs participating in VC
path protection groups are observed on sites C,
D and E.
6 On Site B, verify that the CL-B Nothing happens.

module is up. The service continues to work on the
protection link.
7 Perform “force-switch-to- All commands are performed and functional.

command.
Perform “clear” command.
Perform “show status” command
for VC path protection.
Testing TDM Group Protection

The objective of the test is to verify the correct functionality of the TDM group
protection.

Setup C: 2 hours, Setup E: 2 hours.
Test Procedure
Two tables below detail two cases of TDM group protection test procedures:
• Table C-11 – regular TDM group protection test (Setup E, black line)
• Table C-12 – traffic duplication test (Setup C, DUT B and DUT C).

Table C-11. TDM Group Protection Test Procedure – Setup E
1 Verify that TDM group protection is The service is up and error-free.

configured as follows:
Setup E. Site B
echo "TDM Group Protection"
tdm-group 1
bind working t1-i cl-b/1
bind protection t1-i cl-a/1
wait-to-restore 10
revertive
exit
2 On Site B, disconnect the CL-B/1 link. The service is restored on the protection
Perform “show status” command for link. No errors are observed.
TDM group protection. The status display indicates switching to
the protection link.
AIS alarms on the VC/VTs participating in
VC path protection groups are observed
on sites C, D and E.
3 On Site B, reconnect the CL-B/1 link. The service switches back to the working
link on CL-B/1.
AIS alarms are cleared.
4 On Site B, reset the CL-B module. The service is restored on the protection
Perform “show status” command for link. No errors are observed.
TDM group protection. The status display indicates switching to
the protection link.
AIS alarms on the VC/VTs participating in
VC path protection groups are observed
on sites C, D and E.
5 On Site B, verify that CL-B is back into The service switches back to the working
action. link on CL-B/1.
AIS alarms are cleared.
6 Using CLI, perform “force-switch-to- Commands are performed and functional.

command.
Perform “manual-switch-to-protection”
command.
Perform manual-switch-to-working”
command.
Perform “clear” command on both
protected links.

Table C-12. TDM Group Protection (Traffic Duplication) Test Procedure – Setup C
1 On DUT C, disconnect SDH CL-A/1 Data is transferred via SDH CL-A/2

(working SDH link). (protection SDH link).
2 Disconnect SDH CL-A/2 (protection Data is transferred via DS1 link (protection
SDH link). PW link)/G.8032 ring.
3 Disconnect Ethernet CL-A/1 (working Data is transferred via DS1 (protection PW

GbE link participating in ERP). link)/G.8032 ring and protection Ethernet
link (ERP).
4 Reconnect Ethernet CL-A/1 (working Data is transferred via DS1 (protection PW

GbE link participating in ERP). link)/G.8032 ring and working Ethernet link
(ERP).
5 Reconnect SDH CL-A/2 (protection SDH Data is transferred via SDH CL-A/2
link). (protection SDH link).
6 Reconnect CL-A/1 (working SDH link). Data is transferred via SDH CL-A/2
(protection SDH link) since revertive mode is
not supported.
7 Disconnect CL-A/2 (protection SDH Data is transferred via CL-A/1 (working SDH
link). link).
Testing I/O Group Protection

between two I/O modules, working in I/O group protection mode.

Setup E, 2 hours
Test Procedure
Table C-13 details the I/O group protection test procedure. All the action in the
table are performed using CLI.
The protection is configured as follows:
configure slot 2 card-type e1-t1 m16t1
configure slot 1 card-type e1-t1 m16t1
exit all
config protection
io-group 1
bind working 2
bind protection 1
no shutdown
Table C-13. I/O Group Protection Test Procedure

1 Perform “force-switch-to- Data transfer and status are ok.

2 Perform ‘force-switch-to-working’ Data transfer and status are ok.

command to force-switch the
traffic to the working I/O module.
3 Perform ‘force-switch-to-protection Data transfer and status are ok.

command to force-switch the
traffic to the protection I/O module.
4 Reset the protection I/O module. The traffic reverts to the working I/O module.
Data transfer and status are ok.
5 Perform ‘force-switch-to-working’ Data transfer and status are ok.

command to force-switch the The working module is active.
traffic to the working I/O module.
6 Reset the working I/O module. No data is transferred till the working module is
up again (switch-to-protection action is not
available since the last ‘force-switch-to-
working’ command locked the switchover).
7 Perform ‘clear’ command to delete

the last command (unlock the Data transfer and status are ok.
switch-over).
8 Perform ‘force-switch-to- Data and Status OK

protection‘ command to force- Now the protection module is active.
switch the traffic to the protection
I/O module.
9 Reset the protection I/O module. No data is transferred till the working module is
up again (switch-to-protection action is not
available since the last ‘force-switch-to-
protection’ command locked the switchover).
10 Perform ‘clear’ command to delete

the last command (unlock the Data transfer and status are ok.
switch-over).
11 Remove and reinsert the protection Data and status are switched to the working
module. module.
12 Remove and reinsert the working Data and status are switched to the protection
module. module.
Testing Clock Selection

The objective of the test is to verify the correct functionality of the clock
selection system.

Setups C and E, 2 hours each

Test Procedure
Setup C
Table C-14 details the clock selection test procedure on Setup C. The clock
selection module includes eight SSM-based clock sources configured on Site A
with Sync-E functionality:
source 1 rx-port sdh-sonet cl-a/1
priority 1
quality-level ssm-based
wait-to-restore 10
exit
source 2 rx-port sdh-sonet cl-a/2
priority 1
wait-to-restore 10
exit
source 3 rx-port sdh-sonet cl-b/1
priority 1
wait-to-restore 10
exit
source 4 rx-port sdh-sonet cl-b/2
priority 1
wait-to-restore 10
exit
source 5 rx-port ethernet cl-a/1
priority 1
wait-to-restore 10
exit
source 6 rx-port ethernet cl-a/2
priority 1
wait-to-restore 10
exit
source 7 rx-port ethernet cl-b/1
priority 1
wait-to-restore 10
exit
source 8 rx-port ethernet cl-b/2
priority 1
wait-to-restore 10
exit
All clock sources of Site B and Site E have the same priority. Site A selects the
source clock (1..8) according to the highest quality among all clock sources
received on Site B and Site E.

Table C-14. Clock Selection Test Procedure, Setup C
Verify the following: The domain of site A is locked on clock source

• Site B distributes the clock with #1.
quality-level ST2. All sites are locked on PRC-quality clock sources
• Site E receives the clock from of site-E.
the Station clock and distributes Services on all sites function error-free and
the clock with quality level PRC. lossless.
Disconnect source#1 on Site A. The domain of Site A domain is locked on

source#2.
Services on all sites function error-free and
lossless.

source#3.
lossless.

source#4.
lossless.

source#5.
lossless.

source#6.
lossless.

source#7.
lossless.

source#8.
lossless.
Disconnect source#8 on Site A. The domain of Site A domain changes to

Holdover state.
Services on Site A function error-free and
lossless.

Connect all links/sources to Site A. The domain of Site A is locked on source#1

once wait-to-restore time elapses.
lossless.
Shutdown Site E. Site A domain is locked on source#5 (ST2

quality).
All sites are locked on ST2-quality clock
sources.
Power on Site E. The domain of Site A is locked on source#1

lossless.
Using RadView, perform Read. Read process passes OK.

Site B: Using RadView, change the Update process passes OK.
quality level to PRC. The domain of site A is locked on clock source
Site E: Using RadView, change the #5.
quality level to ST2. All sites are locked on PRC-quality clock sources
Perform Update. of Site B.
lossless.
Disconnect source#5 on Site A. The domain of Site A is locked on source#6.

lossless.

lossless.

lossless.

lossless.
Connect all links/sources to Site A. The domain of Site A is locked on source#5

lossless.
Shutdown Site B. The domain of Site A is locked on source#1

(ST2 quality).
All sites are locked on ST2-quality clock
sources.
lossless.

Power on Site B. The domain of Site A is locked on source#5

lossless.
Site A: Reset the CL-B module via The domain of Site A is locked on source#6.
RADview. Services on Site A function error-free and
lossless.
Verify that the CL-B module is up. The domain of Site A is locked on source#5
Using RADview, perform manual The domain of Site A is locked on source#6

switching to source #6. Services on site A function error-free and
lossless.
Using RADview, reset the active CL The domain of Site A is locked on source#5.
on Site A. Services on Site A function error-free and
lossless.
The CL-A module is up. The domain of Site A is still locked on source#5
(no change).
Site A: Reboot the Megaplex device The domain of site A is locked on source#5.
(both CL-A and CL-B cards)and wait Services on Site A function error-free and
till it is up. lossless.
Site A: Perform ‘show status’ on Status=OK.

the locked source#5. TX quality=DNU.
RX quality=PRC.
Setup E
Table C-15 details the clock selection test procedure on Setup E. The test is
shown in detail in the figure below. The clock is provided by the piggy on the
MP-4100 ver 2.x.

MP-4100 ver 2.x Megaplex-4 ver 4.x

CLX.1 M8T1 Domain-1
Piggy Station
T1 1 Source#1
cl-a/1
Station
T1 2 Source#2
oscillator cl-b/1
T1 3 M16T1 Source#3
T1 4 M8T1 Source#4
Figure C-8. Clock Selection Test – Setup E
The test includes 3 parts:
Test Purpose
Trigger-initiated clock switching • Verify error-free transition between multiple clock sources
• Verify the restore time according to the configured WTR
• Verify error-free transition from hold-over state to different
clock sources
Forcing clock source selection Force selection of a particular clock source when the sources have
different quality levels
Deleting active clock source Check switching to other clock sources according to their priority
and quality

The clocks are configured as follows:

source 1 station cl-a/1
priority 1
quality-level prs
wait-to-restore 0
exit
source 2 station cl-b/1
priority 2
quality-level prs
wait-to-restore 0
exit
source 3 rx-port t1 9/1
priority 3
quality-level sec
wait-to-restore 0
exit
source 4 rx-port t1 8/1
priority 4
quality-level sec
wait-to-restore 0
exit
Table C-15. Clock Selection Test Procedure, Setup E
Trigger-initiated clock switching
1 Verify that clock mode is set to All the services are up and working error-free.
“auto” and Clock Source #1 with
the highest priority is the active
one.
2 Using RADview, set a non-default Megaplex switches to CLK SRC #2.

WTR value. No errors are observed.
Set T1 port 1 of the M8T1 module
installed in MP-4100 ver 2.x to
“Down”.
Perform Update.
3 Set T1 port 1 to “Up”. After the configured WTR timer expires,

Perform Update. Megaplex switches to CLK SRC #1.
4 Set T1 ports 1 and 2 to “Down”. Megaplex switches to CLK SRC #3.

Perform Update. No errors are observed.

6 Set T1 ports 2 and 3 to “Down”. Megaplex switches to CLK SRC #4.

Perform Update. No errors are observed.


8 Set T1 port 4 to “Down”. Megaplex switches to hold-over state.

Perform Update.
9 Using CLI or RADview, switch from Megaplex switches from hold-over state to the
hold-over state to all the clock connected source (T1 ports in the “Up” state).
sources from 1 to 4, one by one: No errors are observed.
Hold-over to 1
Hold-over to 2
Hold-over to 3
Hold-over to 4.
Forcing clock selection
1 Verify that clock mode is set to

one.
2 Using CLI or RADview, force clock No errors are observed.

selection to SRC #2. The clock domain is locked on SRC #2.


5 Using RADview, change the priority SRC #2 has now the highest priority.
of SRC #1 to 2 and of SRC #2 to 1. No errors are observed.
Deleting active clock source
1 Verify that clock mode is set to

one.
2 Using RADview, delete the active Megaplex switches to CLK SRC #2.
source, SRC #1. No errors are observed.
3 Using RADview, change priority of No errors are observed.

SRC #4 to 3 (equal to SRC #3
priority) and quality of SRC #4 to
PRS (better than SRC #3 quality,
SEC)
4 Using RADview, delete the active Megaplex switches to CLK SRC #4 (which has
source, SRC #2. the same priority as SRC #3 and better quality)

Testing OAM CFM and Y.1731 PM Functionalities

The objective of the test is to verify the correct functionality of the Up and Down
MEPs for OAM CFM (802.1ag) and Y.1731 PM functionalities.
Test Duration
Setup D, 4 hours
Test Procedure
The table below details the test procedure.
Table C-16. OAM CFM (802.1ag ) and Y.1731 PM Test Procedure
1 Verify that all MEPs in the All Up and Down MEPs in the application are up.
application are up.
2 Send traffic from Ixia generator #6 There is correlation between frame counts for
on all the VLANs and on P-bits of all the far- and near-end counters on the
the MEPs. The traffic must be sent Megaplex and ETX devices.
on each of the VLANs 1-8 with
P-bits 0-7 for each VLAN.
Check the PM services (delay
measurements, delay variation
measurements, availablity etc.)
3 Run the OAM link trace test The link trace test passes successfully.
between the MEPs.
4 Run the OAM loopback between the The loopback test passes successfully.
MEPs
5 Perform Read from RADview. The device database is empty.

Using CLI, delete the Management connectivity is established.
“startup-config” file.
Using CLI, perform “admin reboot”
command.
Using CLI, configure IP management
via router interface #1.
6 Perform Update from RADview. All MEPs are up.
7 Run the OAM link trace test The link trace test passes successfully.
between the MEPs.
8 Run the OAM loopback between the The loopback test passes successfully.
MEPs
9 Run RADview Job Statistics Statistics are collected.

collection application. Information displayed in the PM portal is
identical to the information displayed in CLI and
RADview

Testing Ethernet Forwarding and Traffic Management

The objective of the test is to verify the correct functionality of E-TREE, E-LAN
and E-Line Ethernet forwarding and Traffic management (shaping, policing and
scheduling).
The following schemes describe the expected behavior with the pre-defined
configuration (for the full setup, see Setup D in Figure C-4).
1/1 1/2 1/3 1/4 2/1 2/3 2/5 2/7 3/1/1 3/3/1 4/1/1 4/3/1 10/1 10/2 10/3 10/4
Policer values 5M 4M 3.5M 3M 2M 1.5M 1M 500K 8M 50M 5M 2M 1M 500K

20M 1.5M
Policer Bi-directional
Test Shaper values
Bi-directional 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M 100M
VLAN 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315
Shaper values
5M 4M 3M 2M 1M 1.5M 1M 500K 8M 20M 50M 5M 2M 1.5M 1M 500K
Shaper Bi-directional
Test Policer values
Bi-directional 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M 60M
queue-map-profile P_bit classification p-bit

map 0 to-queue 7
map 1 to-queue 6
map 2 to-queue 5
map 3 to-queue 4
map 4 to-queue 3
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0
Strict Priority LAG
Policer Test: Shaper 100M

Shaper Test: Shaper 10M
Figure C-9. E-Line Data Forwarding and Defined QoS

1/1 1/2 1/3 1/4 2/1 2/3 2/5 2/7 3/1/1 3/3/1 4/1/1 4/3/1 10/1 10/2 10/3 10/4
Policer values 5M 4M 3.5M 3M 2M 1.5M 1M 500K 8M 20M 50M 5M 2M 1.5M 1M 500K

Policer
Test 100M 100M 100M 100M 100M 100M 100M
Shaper values 100M
100M 100M 100M 100M 100M 100M 100M 100M
Shaper values 5M 4M 3M 2M 1M 1.5M 1M 500K 8M 20M 50M 5M 2M 1.5M 1M 500K

Shaper
Test 60M 60M 60M 60M
60M 60M 60M 60M
Policer values 60M 60M 60M 60M
60M 60M 60M 60M
9 10 11
8 12
7 13
6 14
Strict Priority
5 15
map 0 to-queue 7 4 Bridge 16
map 1 to-queue 6
map 2 to-queue 5 3
17
map 3 to-queue 4 VLAN 200
map 4 to-queue 3 2
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0
Policer Test: Policer 50M Shaper 100M

Shaper Test: Policer 100M Shaper 10M
LAG
Figure C-10. E-LAN Data Forwarding and Defined QoS
1/1 1/2 1/3 1/4 2/1 2/3 2/5 2/7 3/1/1 3/3/1 4/1/1 4/3/1 10/1 10/2 10/3 10/4
Policer values 5M 4M 3.5M 3M 2M 1.5M 1M 500K 8M 20M 50M 5M 2M 1.5M 1M 500K

Policer
Test 100M 100M 100M 100M 100M 100M 100M
Shaper values 100M
100M 100M 100M 100M 100M 100M 100M 100M
Shaper values 5M 4M 3M 2M 1M 1.5M 1M 500K 8M 20M 50M 5M 2M 1.5M 1M 500K

Shaper
Test 60M 60M 60M 60M
60M 60M 60M 60M
Policer values 60M 60M 60M 60M
60M 60M 60M 60M
9 10 11
8 12
7 13
6 14
Strict Priority
5 15
map 0 to-queue 7 4 Bridge 16
map 1 to-queue 6
map 2 to-queue 5 3
17
map 3 to-queue 4 VLAN 100
map 4 to-queue 3 2
map 5 to-queue 2
map 6 to-queue 1
map 7 to-queue 0 ROOT
1
Policer Test: Policer 50M Shaper 100M

Shaper Test: Policer 100M Shaper 10M
LAG
Figure C-11. E-TREE Data Forwarding and Defined QoS


Setup D, 8 hours
Configuring Ixia Ports

This section explains how to configure Ixia ports used for traffic generation and
analysis. You can also use other equipment for this purpose, such as Spirent
TestCenter or other Ethernet traffic generators. The Ixia configuration files for
Ethernet forwarding, Policing and shaping, and Scheduling tests are given below
under respective headers.
Ethernet Forwarding
Ethernet Forwarding is tested using Unicast, Multicast, Broadcast and Unknown
Unicast packets. Table C-17 lists the configuration files used for IXIA ports and
the Ixia port on which they are loaded.
Table C-17. Ixia Configuration Files for Testing Ethernet Forwarding
Configuration File Loaded on Ixia Port Source MAC Address
1 SA 00-00-00-00-00-01
3 SA 00-00-00-00-00-03
4 SA 00-00-00-00-00-04
5 SA 00-00-00-00-00-05
For each mode (E-Line, E-Tree, E-LAN) and each type of packets, one of 7
streams is used. Each stream consists of a combination of R, L1, L2 and L3 IXIA
configuration files (see above) as shown in Table C-18.
Table C-18. Ixia Configuration for Testing Ethernet Forwarding
Unicast Multicast Broadcast Unknown Unicast
E-TREE (100) 1st stream: R, L1, L2, 2nd stream: R, L1, L2, 2nd stream: R, L1, L2, 2nd stream: R, L1,
L3 L3 L3 L2, L3
E-LAN (200) 3rd stream: R, L1, L2, 4th stream: R, L1, L2, 4th stream: R, L1, L2, 4th stream: R, L1,
L3 L3 L3 L2, L3
E-LINE (300) 5th stream: R, L1 6th stream: R, L1 7th stream: R, L1 ------
Policing and Shaping

Policing and Shaping are tested on Unicast packets only. Table C-19 lists the
configuration files used for IXIA ports and the Ixia port on which they are loaded.

Table C-19. Ixia Configuration Files for Testing Policing and Shaping
1 SA 00-00-00-00-00-01
3 SA 00-00-00-00-00-03
4 SA 00-00-00-00-00-04
5 SA 00-00-00-00-00-05
For each mode (E-Line, E-Tree, E-LAN) and each of 4 Ixia configuration files,
select streams indicated in Table C-20.
Table C-20. Ixia Ports Configuration for Testing of Policing and Shaping
E-TREE (100) E-LAN (200) E-LINE (300)
Port_sa1_policer_shaper.str Stream 5 Stream 6 Streams 1-4
Port_lag_policer shaper.str Stream 2 Stream 3 Stream 1
Scheduling
Scheduling is tested on Unicast packets only. Table C-21 lists the configuration
files used for IXIA ports and the Ixia port on which they are loaded.
Note For E-line, the Scheduling test is performed only on one flow: VLAN 300 – LAG1 –
ASMi-54L PCS 1/1 (see Figure C-9).
Table C-21. Ixia Configuration Files for Testing Scheduling
1 SA 00-00-00-00-00-01
3 SA 00-00-00-00-00-03
1 SA 00-00-00-00-00-01
1 SA 00-00-00-00-00-01

3 SA 00-00-00-00-00-03
4 SA 00-00-00-00-00-04
5 SA 00-00-00-00-00-05
For each mode (E-Line, E-Tree, E-LAN) and each of Ixia configuration files select
streams as indicated in Table C-22.
Table C-22. Ixia Ports Configuration for Testing of Scheduling
E-TREE (100) E-LAN (200) E-LINE (300)
Port_sa1_policer_shaper.str Stream 5 Stream 5 -
Scheduling_300_1 - - Streams 1-8
Scheduling_300_2 - - Streams 1-8
E_Tree_Scheduling_100_1.str All streams - -
E_LAN_Scheduling_200_1.str - All streams -
Test Procedure
Table C-10 details the test procedure.

Table C-23. Ethernet Forwarding and Traffic Management Testing Procedure
1 Generate traffic according to E-Line, E-Tree and E-LAN services are up.
Table C-17 and Table C-18 to test No loss is detected.
E-LINE, E-LAN and E-TREE services
The bridge in E-Tree and E-LAN services is
with Unicast, Broadcast, Multicast
functioning properly:
and Unknown Unicast packets.
E-Tree:
Rx R = Tx L1 + Tx L2 + Tx L3;
Rx L1=Tx R,
Rx L2=Tx R,
Rx L3=Tx R,
E-LAN:
Rx R = Tx L1 + Tx L2 + Tx L3;
Rx L1=Tx R + Tx L2 + Tx L3;
Rx L2=Tx R + Tx L1 + Tx L3;
Rx L3=Tx R + Tx L1 + TxL2.
Current statistics are functional in both CLI and
RADview.
E-Line Configuration
Recreating a flow and changing

ingress/egress port
1 On any flow of E-line configuration The service is up with the new ingress/egress
(101A to 132A), change its ingress port.
or egress port. No loss is observed.
2 Delete any flow of E-line The service is down.

configuration (101A to 132A).
3 Using RADview, recreate the flow The service is up, with no losses.
deleted in the previous step.
4 Using CLI, perform admin reboot The service is up, with no losses.
command.
Policing
1 Paste the following script into CLI, No sanity errors are displayed.
followed by “commit” and “save”.
2 Generate traffic with the rate above Ixia Rx rate is equal to the rate of the
the configured policer values in configured policer.
both directions according to The configuration is shown in Figure C-9.
Table C-19 and Table C-20, E-LINE
definitions.

3 Using RADview, configure some of Ixia Rx rate is equal to the rate of the
the policer values to 80% of the configured policer.
previous values.
Perform Update.
Generate traffic with the rate above
the newly configured policer values
in both directions
4 Using CLI, perform admin reboot Ixia Rx rate is equal to the rate of the
command. configured policer.
Shaping
1 Paste the following script into CLI, No sanity errors are displayed.
2 Generate traffic with the rate above Ixia Rx rate is equal to the rate of the
the configured shaper values in configured shaper, as defined in Figure C-9.
both directions according to
Table C-19 and Table C-20, E-Line
definitions.
3 Using RADview, configure some of Ixia Rx rate is equal to the rate of the
the shaper values to 80% of the configured shaper.
previous values.
Perform Update.
the newly configured shaper values
in both directions
4 Using CLI, perform admin reboot Ixia Rx rate is equal to the rate of the
command. configured shaper.
Scheduling
1 Generate streams with the All Data is forwarded lossless.

priorities bit (0..7) according to
Table C-21 and Table C-22.
2 Gradually increase the stream bit The high priority bit is forwarded lossless with
rate until you notice data loss. egress rate equal to the configured shaper CIR.
Continue to increase the bit rate
until only the first priority bit is
forwarded and only the first
internal queue performs
forwarding.
3 Stop transmitting the high priority The next high priority bit passes lossless.
bit and continue to transmit lower
priority bit.

4 Using RADview, change the queue The new high priority bit passes lossless.
map profile that is used by the
flow.
Perform Update.
5 Using CLI, perform admin reboot The new high priority bit passes lossless.
command.
E-Tree
Send Broadcast, Multicast, Root-to-leaf:

Unknown Unicast and Unicast • Broadcast, Multicast, Unknown Unicast
traffic according to Table C-17 and packets are distributed to all the leafs.
Table C-18.
• Unicast is sent only to the target leaf.
Leaf to root:
• Broadcast, Multicast, Unknown Unicast and
Unicast are distributed only to the roots and
not to other leafs.
Using RADview, create another Root-to-leaf:

E-Tree domain. • Broadcast, Multicast, Unknown Unicast
Send Broadcast, Multicast, packets are distributed to all the leafs.
Unknown Unicast and Unicast • Unicast is sent only to the target leaf.
traffic according to Table C-17 and
Leaf to root:
Table C-18 and change the VLAN to
match the new domain. Broadcast, Multicast, Unknown Unicast and
Unicast are distributed only to the roots and
not to other leafs.
Policing
Paste the following script into CLI, No sanity errors are displayed.
Generate traffic with the rate above Ixia Rx rate is equal to the rate of the
the configured policer values in configured policer, as defined is shown in
both directions according to Figure C-11.
Table C-19 and Table C-20, E-TREE
definitions.
Using RADview, configure some of Ixia Rx rate is equal to the rate of the
previous values.
Perform Update.
in both directions

Using CLI, perform admin reboot Ixia Rx rate is equal to the rate of the
Shaping
definitions.
previous values.
Perform Update.
in both directions
Scheduling
Generate streams with the All

Scheduler definitions.
Stop transmitting high priority bits The next high priority bit passes lossless.
and continue to transmit lower
priority bits.
Using RADview, change the queue The new high priority bit passes lossless.
flow.
Perform Update.
Using CLI, perform admin reboot The new high priority bit passes lossless.
command.
E-LAN
Remove a Bridge Port and associate Data stops on this path

a flow from an existing VLAN.
Add the same Bridge Port and Data is restored. No loss is observed.
associated flow from RADview

Policing
the configured policer values in configured policer, as defined in Figure C-10.
Table C-19 and Table C-20, E-LAN
definitions.
previous values.
Perform Update.
in both directions
Shaping
definitions.
previous values.
Perform Update.
in both directions

Scheduling
Generate streams with the All

(200) Scheduler definitions.
Stop transmitting high priority bits The next high priority bit passes lossless.
and continue to transmit lower
priority bits.
Using RADview, change the queue The new high priority bit passes lossless.
flow.
Perform Update.
Using CLI, perform admin reboot The new high priority bit passes lossless.
command.
Testing Ethernet BERT Functionality

20B
The objective of the test is to verify the correct functionality of the Ethernet
BERT.

64B
Setup D, 2 hours
Test Procedure
65B
Table C-10 details the Ethernet BERT test procedure.

Table C-24. Ethernet BERT Testing Procedure
1 Send user packets from Ethernet Management to the CPE is not affected.
generator ports to the CL Bridge User traffic on other services is not affected.
ports participating in other services.
User traffic on the BERT path stops (since
Activate a loop on a selected PCS Ethernet Bert is intrusive).
port of one of ASMi-54L devices.
BERT status is Success.
One by one, activate four Ethernet
The report gives indication on the rate in which
BERT tests using parameter
the test was 100% success.
combinations from the table below.
For example, a script for the first Note: Verify that the throughput results make sense.
test may be as follows:
exit all
config test rfc2544
profile-name 1
frame-size 64
exit
test 1
test-profile 1
max-rate 3000000
type frame-loss
associated-flow 101a
Table C-25. Testing Ethernet BERT Parameters
Operation Platform Flow Management SHDSL rate Bert Frame Size Bert Rate
Mode
E-line CLI 101A Managed Min. Value Min. Value Equal to SHDSL
Rate
E-Tree CLI 2 Managed Max value Max Value Higher than

SHDSL Rate
E-LAN RADview 22A Non-Managed Min. Value Min. Value Higher than
SHDSL Rate
E-Tree RADview 2 Non-Managed Max value Max Value Equal to SHDSL

Rate
Testing TDM (E1) Services

The objective of the test is to verify the correct functioning of TDM (E1) services.

Setups A and F; 2 hours each
Test Procedure
Two tables below detail the TDM (E1) services test procedure.

Table C-26. TDM (E1) Services Test Procedure – Setup A
1 Perform Read from RADview. A Sync Loss indication is observed in the

Using CLI, delete one of the coresponding generator/HBT device (for
services/tests 2, 3, 8, 10 or 12 and example, if test 8 is deleted, the indication is
send the “commit” command. observed in HBT-8).
2 Perform Update from RADview. Data passes error-free.

No active alarms are displayed.
3 Perform the loopbacks shown in the All the loopbacks are functional.
figure below (using either RADview
or CLI).
Megaplex-4
ASMi-54C/N Repeater
Local-on-Remote Remote-on-Remote
RLB LLB LLB RLB RLB Remote-on-Remote e1
SHDSL v35
e1 e1-i
Local-on-Remote Remote-on-Remote
Figure C-12. Loopbacks for Testing TDM (E1) Services
Table C-27. TDM (E1) Services Test Procedure – Setup F

(numbered 1-11) services and send example, if service 8 is deleted, the indication is
the “commit” command. observed in HBT-8).

3 Reset the CL-A module. TDM Group protection is activated. CL-B

becomes the active module.
No data loss is observed.
4 Perform the loopbacks shown in the All the loopbacks are functional.
figure above from the CL-B module
(using either RADview or CLI).
Testing High Speed Serial Services

The objective of the test is to verify the correct functioning of high speed serial
services.

Setups A and F; 2 hours each

Test Procedure
Two tables below detail the high speed serial services test procedure.
Table C-28. High Speed Serial Services Test Procedure – Setup A

services/tests 1, 3, 4, 9, 11 or 12 example, if test 3 is deleted, the indication is
and send the “commit” command. observed in HBT-3).

3 Activate the local loopback on the The error test signal is returned to the local
selected V.35 port for the duration HBT.
of 5 min. Data continues to be transferred.
Disconnect the HBT on the remote The test expires after 5 min and bidirectional
unit. data transfer is restored.
Fronm the corresponding HBT,
inject an error to the local (central)
unit.
4 Activate the remote loopback on The error test signal is returned to the remote
the selected V.35 port for the HBT.
duration of 5 min. Data continues to be transferred.
Disconnect the HBT on the The test expires after 5 min and bidirectional
local/central unit. data transfer is restored.
From the corresponding HBT, inject
an error to the remote (standalone)
unit.
Table C-29. High Speed Serial Services Test Procedure – Setup F

services/tests (1,2,…,7) and send example, if Service 5 is deleted, the indication
the “commit” command. is observed in HBT-5).

3 Remove the CL-A module. TDM Group protection is activated. CL-B

becomes the active module.
No data loss is observed.

4 Activate the local loopback on the The error test signal is returned to the local
selected V.35 port for the duration HBT.
of 5 min. Data continues to be transferred.
Disconnect the HBT on the remote The test expires after 5 min and bidirectional
unit. data transfer is restored.
an error to the local (central) unit.
the selected V.35 port for the HBT.
Disconnect the HBT on the The test expires after 5 min and bidirectional
local/central unit. data transfer is restored.
an error to the remote (standalone)
unit.
Testing Low Speed Serial Services

The objective of the test is to verify the correct functioning of low speed serial
services.

Setup B, 2 hours (see Tests 2,3,5).
Test Procedure
The table below details the low speed serial services test procedure.
Table C-30. Low Speed Serial Services Test Procedure

Using CLI, delete one of the coresponding generator/LBT device (for
services/tests 2,3,5 and send the example, if Test 3 is deleted, the indication is
“commit” command. The tests are observed in LBT-3).
shown in detail in Figure C-13.

The following test is performed on Low speed service that starts with LBT-5 in
MP-4100 A and ends with a loop on HS-RN CH 10/1 in MP-2100 D.

3 Replace the loop on MP-2100 D The error test signal is returned to the local
HS-RN CH 10/1 with an LBT only for LBT.
the purpose of this test. Data continues to be transferred.
Activate the local loopback on HS- The test expires after 5 min and bidirectional
RN CH 1/1 for the duration of data transfer is restored.
5 min.
Disconnect the LBT on MP-2100 D
HS-RN CH 10/1.
From the LBT, inject an error to the
local (central) unit.
the selected HS-RN port for the LBT (MP-2100 D HS-RN CH 10/1 LBT).
Disconnect the LBT from The test expires after 5 min. and bidirectional
MP-4100 A HS-RN CH 1/1. data transfer is restored.
From the LBT, inject an error on
MP-2100 D HS-RN CH 10/1.
MP-A 1/1/2, 1/1/3, 1/1/4

MP-B MP-C 3/1/1
MP-D
1/1/2, 1/1/3, 1/1/4
HS-RN M8T1 -
T1-I CLA/84 Link A /1 Link A /1 Link A /2 Link A /1 T1-I CL-B/1 M8T1 M2T1
LBT #2 4/3 3/1 3/2 TDM Group #1 Bypass TDM Group #1 5/1 3/1 3/2
4.8k, 1/1/2, 1/1/3, 1/1/4
async.
T1- I CL-B/1 Link B /1 Link B /1 Link B/2 Link B /1 T1-I CL-A/42
Test #2 1/1/2, 1/1/3, 1/1/4 3/1/1
MP-B 1/7/1 MP-C 1/7/1 4x64k

T1-I CL-A/22 T1-I CL-A/52 HSF-2
HS-RN Link A /2 Link A/1
Rx Tx
LBT-3 CH- 4 /1 TDM Group #2 TDM Group #2 CH 3/2
Tx Rx
1x64k
, sync. T1-I CL-B/22 Link B /2 Link B/1 Fiber
T1-I CL-B/11
Test #3 1/7/1 1/7/1
MP-A TS#10 MP-B MP-C TS#10

TS#10
MP-D
3/1/1 3/1/1 3/1/1 3/1/1
HS-RN T1-I CL- A/84 Link A /1 Link A/1 Link A/2 Link A/1 T1-I CLA- / 42 M16T1 M2T1 HS-RN
LBT -5 CH - 1/1 TDM Group #1 Bypass 9/3 1/1 CH 10/1

9.6k, TDM Group #1
9.6k,
TS#10
async. Link B /1 Link B/2 Link B/1 async.
T1-I CL- B/1 Link B /1 T1-I CL-B/ 1
3/1/1 3/1/1 3/1/1 3/1/1
Test #5
Figure C-13. Low Speed Services 2,3,5
Testing Voice Services

The objective of the test is to verify the correct functionality of FXS voice
services.

Setup B, 3 hours.

Test Procedure
The table below detail the voice service test procedure. The test is performed on
the VC-6A/FXS module.
MP-A 1/1/1 ESF

MP-B MP-C 1/3/3
1/1/1 1/3/3
VC6 -FXS T1-I CL-A/14 T1-I CL-A/24 VC6 -FXS
Link A /1 Link A/1 Link A/2 Link A /1
5/3 Bypass TDM Group #4 6/3

TDM Group #3
1/1/1 1/3/3
T1-I CL-B/14 Link B/1 Link B/1 Link B /2 Link B/1 T1-I CL-B/24
1/3/3
FXS-FXS Service 1/1/1
Figure C-14. FXS Voice Service (Test 4 in Setup B)
Table C-31. Voice Services Test Procedure – Setup B
1 Perform Read from RADview. Voice and signaling are not transferred.
Using CLI, delete Test 4 service and
send the “commit” command.
2 Perform Update from RADview. Voice and signaling are transferred in bi-
directional mode, error-free.
3 Site A: Activate the local loopback The local voice channel (Site A) receives its own
on the VC-6A/FXS voice channel as signal, e.g., a strong side tone is heard in the
shown in the Figure below (using earpiece if the channel is connected to a
either RADview or CLI). telephone set.
3 Disable the local loopback. Voice and signaling are transferred in

bidirectional mode.
Site A: Activate the remote The remote voice channel (Site C) receives its
loopback on the VC-6A/FXS voice own signal, e.g., a strong side tone is heard in
channel as shown in the Figure the earpiece if the channel is connected to a
below (using either RADview or CLI). telephone set.

3 Disable the remote loopback. Voice and signaling are transferred in

bidirectional mode.
4 Site A: Perform ‘local tone-inject’ The analog signal 1 kHz) is supplied to Local
loopback on the VC-6A/FXS voice Site A.
channel as shown in the Figure
below (using either RADview or CLI).
5 Disable the ‘local tone-inject’ Voice and signaling are transferred in

loopback. bidirectional mode.
6 Site A: Perform ‘remote tone-inject’ The analog signal (1 kHz) is supplied to remote
loopback on the VC-6A/FXS voice Site C.
channel as shown in the Figure
below (using either RADview or CLI).

7 Disable the ‘remote tone-inject’ Voice and signaling are transferred in

loopback. bidirectional mode.
Testing Pseudowire Services over ERP

The objective of the test is to verify the correct functionality of pseudowire
services over ERP.

Setup C, 4 hours.
Test Procedure
In this test PWs are configured to all possible PW types (TDMoIP, CES, SATOP) and
with different flow classifications: unclassified, tagged with VLAN and tagged with
double VLAN (vlan + inner-vlan).
The PW Traffic is getting priority over Ethernet Traffic. Order of priority: Voice,
Serial, E1, Ethernet. The table below details the test procedure.
Table C-32. PW over ERP Test Procedure
Configuration
1 Verify that PW over ERP connectivity PW traffic is transferred error-free.

is established successfully. The clock is properly locked (according to one
of the settings in Table C-14).
Ethernet traffic is transferred lossless.

2 Set a low (50M) shaper value on Order of traffic priority is as follows: voice,
the ERP working link to create serial, E1, Ethernet.
congestion.
3 Using RADview, set the shaper PW traffic is transferred error-free.

value to the maximum possible Ethernet traffic is transferred lossless.
(1 GbE) to remove congestion.
4 Perform Read from RADview. PW traffic is transferred error-free.

Using CLI, delete PW service SP1
followed by “commit”.
Perform Update from RADview to
recreate the deleted PW.
Diagnostics
1 MP-4100 C: Using either RADview or There is no disturbance to services provided by

CLI, activate the local loopback on means of the other timeslots (pseudowires) of
the selected internal DS1 port the same port
timeslots of the MPW-1 module as The error test signal is returned to the local
shown in the Figure below (the HBT.
local loopback is toward the local
HS-RN serial port).
2 Disable the local loopback. The service continues working in bidirectional

mode.
3 MP-4100 C: Using either RADview or There is no disturbance to services provided by

CLI, activate the remote loopback means of the other timeslots (pseudowires) of
on the selected internal DS1 port the same port
timeslots of the MPW-1 module as The error test signal is returned to the remote
shown in the Figure below (the HBT.
remote loopback is toward the PSN
and the remote HS-RN serial port).

4 Disable the remote loopback. The service continues working in bidirectional

mode.
Testing ACL Functionality

The objective of the test is to verify the correct functionality of the ACL.

Any setup, 2 hours
Test Procedure
The table below details the ACL test procedure.
Table C-33. ACL Testing Procedure
1 Verify the Telnet, SSH and SNMP Telnet, SSH, SNMP connectivity is ok.
connectivity.
2 Add the following script: Telnet, SSH and SNMP connectivity is lost.
3 In the script, replace IP address Telnet, SSH, SNMP connectivity is ok.

1.1.1.1 with the IP address of the
PC from which you manage the
Megaplex device.
Open Telnet, SSH and SNMP
sessions.
4 Reset the working CL module. Telnet, SSH and SNMP resume functioning
when the standby CL becomes active.

5 Perform Read from RADview. Telnet and SSH connectivities are lost, SNMP
In the Telnet and SSH sequences, connectivity is ok.
change the IP addresses with IP
addresses of any other station(s).
Perform Update from RADview.
Testing RADview
The objective of the test is to verify the correct functionality of RADview Jobs
application.

All the setups, 2 hours total.
Test Procedure
The table below details the RADview Jobs application testing procedure.
Table C-34. RADview Jobs Testing Procedure
1 Open RADview. The setup is up.

Data and management services are working
properly.
2 Verify that the following jobs are All RADview Jobs lists are working properly.
working properly:
• Download configuration
• Download software
• Execute script
• Collect statistics.
3 Using RADview Jobs application, The installation process is properly completed.

perform the installation on all the
Megaplex devices in the setup.
Testing SNMPv3 Functionality

The objective of the test is to verify the correct functionality of SNMPv3.

Setup C, 2 hours
Test Procedure
Table C-10 details the SNMPv3 test procedure.

Table C-35. SNMPv3 Testing Procedure
1 Verify the Telnet, SSH and SNMP Telnet, SSH, SNMP connectivity is ok.
connectivity.
2 Add the following SNMPv3 configuration to The corresponding nodes in RADview

one of the units in setup C. EMS Map are up.
SNMP poll is performed successfully.
SNMPv3_authpriv.tx
t
The script adds the following:

user authmd5 md5-auth none
user authsha sha-auth none
user pauthmd5 md5-auth des
user pauthsha sha-auth des
3 Open RADview zoom for each of the Zoom opens properly.
nodes. The dialogs present the relevant
Open as much as possible dialogs for information.
about 10 minutes. Read and Update procedures are
Perform Read and Update in each of the performed successfully.
dialogs.
Testing Teleprotection Functionality

The objective of the test is to verify the correct functionality of Teleprotection
features.

Setups G1 and G2, 2 hours. The setup diagrams are shown in the figures below.
Figure C-15. Teleprotection Test, Point-to-Point

Figure C-16. Teleprotection Test, Point-to-Multipoint
Test Procedure
Table C-10 details the Teleprotection test procedure.
Table C-36. Teleprotection Testing Procedure
Delay Measurement, Point-to-Point
1 Setup the test as in Figure C-15. The corresponding nodes in RADview

EMS Map are up.
SNMP poll is performed successfully.
2 Generate 300 commands from the tester, All the 300 commands are transmitted
each with the following signal via TP-OUT interface.
characteristics: The delay does not exceed 4msec.
3 Perform Read from RADview. Update passes successfully.

Using CLI, delete the statup-config and
user-config configurations.
Using CLI, perform admin reboot
command.
Configure the IP address to regain SNMP
connectivity.
Perform Update from RADview.
Repeat Step 2. All the 300 commands are transmitted

via TP-OUT interface.
The delay does not exceed 4msec.
Delay Measurement, Point-to-MultiPoint

Setup the test as in Figure C-16. All the 300 commands are transmitted
Generate 300 commands from the tester via TP-OUT interface.
for each path, each with the following The delay does not exceed 4msec.
signal characteristics.
Protection
Setup the test as in Figure C-15. No command is lost.

On both Megaplex devices configure All commands have latency ≤ 10msec.
revertive TDM Group protection on CL-A/1
(working) and CL-B/1 (protection).
Generate 3000 commands from the
tester, each with the following signal
characteristics.
Signal generation duration is ~50 seconds

During these 50 seconds disconnect and
reconnect MP-4100 #1 CL-A/1 link several
times.
False Commands
Power MP-4100 #1 down and up. No false command is observed on TP-

OUT ports.
On MP-4100 #1, reset CL-A. No false command is observed on TP-

OUT ports.
On MP-4100 #1, pull out and re-insert the No false command is observed on TP-
TP module. OUT ports.
On MP-4100 #1, power down and up one No false command is observed on TP-
of the power supply units. OUT ports.
Testing Ethernet over SDH/SONET Service

The objective of the test is to verify the correct functionality of Ethernet over
SDH/SONET. The test consists of two parts:
• Aggregation of 2 x STM-1 with VC-4 LCAS (Setup H1)
• 1-32 VCG Test (Setup H2).


Setups H1 and H2, 2 hours each
Test Procedure
Aggregation of 2 x STM-1 with VC-4 LCAS

In this test each VCG (A/1 and A2) has rate of VC-4 (full STM-1) so that the total
rate is 2 x STM-1.
SDH A/1
Flow
LCAS
IXIA GbE A/1 VCG A/1
& VCG A/2
SDH A/2
Fibers
SDH B/1
LCAS
Flow
IXIA GbE B/1 VCG B/1
& VCG B/2
SDH B/2
Figure C-17. Setup H1: Aggregation of 2 x STM-1 with VC-4 LCAS
Table C-37. Aggregation of 2 x STM-1 with VC-4 LCAS
Prepare the setup shown in the

figure above and paste the
attached configuration file.
Data traffic test
On IXIA ports, define the following

patterns at the data rate of
290 Mbps:
• Packet size 64 kbps, unaware 15 min error-free run

• Packet size 1518 kbps, vlan 200 Overnight error-free run
Disconnections and reboot tests
Perform a few different

disconnections, of the 1st
link, the 2nd and both The system recovers after each disconnection.
Perform many and fast

disconnections The system recovers at the end of the test.
Perform HW reset of CL-A The system recovers after reset.
Perform HW reset of CL-B The system recovers after reset.
Perform SW reset of CL-A

(“configure slot cl-a reset”) The system recovers after reset.
Perform SW reset of CL-B

(“configure slot cl-b reset”) The system recovers after reset.
Using CLI, perform admin reboot The system recovers after reboot.
command.
Change the IXIA port rate to The data traffic runs at the rate of 290 Mbps.
1000 Mbps.
Perform a combination of
disconnections and HW/SW The system recovers after each
resets. disconnection/reset.
RADview tests
On IXIA ports, define the data rate

of 290 Mbps and random packet
size of 64 to 1518 kbps. Data passes losslessly.
Perform Read. Read is performed successfully
Configure the setup using RADview The setup is configured successfully

Update is performed successfully, data traffic is
Perform Update error-free
Jumbo frame test
Configure egress-mtu=9600 on the Data passes losslessly.

ethernet and logical-mac ports.
On IXIA ports, define the pattern
with packet size of 9596 kbps and
vlan.
Make a few disconnections Verify that the system recovers after each
disconnection
Run data traffic for 5 minutes Verify that the traffic is error-free

1-32 VCG Test
SDH A/1
Flow
LCAS
IXIA GbE A/1 VCG A/1 Fiber
& VCG A/2
SDH A/2
Figure C-18. Setup H2: 1-32 VCG Test
Table C-38. 1-32 VCG Test Procedure
1 Configure a flow with one VC-12 The data traffic is running at 2 Mbps.
between GbE port A/1 and SDH port
A/1 via VCG A/1 according to the
attached script
2 Add another VC-12 to the existing The 2 Mbps data traffic keeps running.
VCG as follows:
conf port vcg cl-a/1 bind
vc-vt cl-a/1/1/1/1/2
commit
3 Increase the generator rate to The data traffic is running at 4 Mbps.
4 Mbps
4 Add three more VC-12 to the The 4 Mbps data traffic keeps running.
existing VCG as follows:
vc-vt cl-a/1/1/1/1/3
vc-vt cl-a/1/1/2/1/1
vc-vt cl-a/1/1/2/1/2
commit
5 Increase the generator rate to The data traffic is running at 10 Mbps.

10 Mbps.

6 Remove the 4 previously added The data traffic rate decreases to 2 Mbps.
VC-12 ports:
conf port vcg cl-a/1 no
bind vc-vt cl-a/1/1/1/1/2
commit
7 Change the binding from vc-vt to The data traffic rate increases to 49 Mbps
vc3 as follows: (1 x VC3).
vc3-sts1 cl-a/1/1/1
commit
8 Change the binding from vc3 to vc4 The data traffic rate increases to 150.3 Mbps
as follows: (1 x VC4).
bind vc3-sts1 cl-a/1/1/1
vc4-sts3c cl-a/1/1
commit
9 Add another vc4 to vcg: The data traffic rate increases to 300.6 Mbps
conf port vcg cl-a/1 bind (2 x VC4).
vc4-sts3c cl-a/1/2
commit
10 Add two more vc4 ports to vcg: The data traffic rate increases to 601.2 Mbps
conf port vcg cl-a/1 bind (4 x VC4)
vc4-sts3c cl-a/1/3
vc4-sts3c cl-a/1/4
commit
Note: define the shaper profile as
in the attached script.

11 Remove 3 of the 4 previously added The data traffic rate decreases to 150.3 Mbps
VC-12 ports: (1 x VC4)
bind vc4-sts3c cl-a/1/1
commit
12 Change the binding from vc4 to vc3 The data traffic rate decreases to 49 Mbps
as follows: (1 x VC3)
vc3-sts1 cl-a/1/4/3
commit
13 Change the binding from vc3to Data traffic decreases to 2 Mbps

vc-vt as follows:
bind vc3-sts1 cl-a/1/4/3
conf port vcg cl-a/1
commit
14 Start from the beginning (Step 1) No data traffic is observed

and paste the following script:
conf flows no flow a1
conf flows no flow a2
conf flows no classifier-
profile v100
conf port ethernet cl-a/1
shutdown
conf port logical-mac cl-
a/1 no bind gfp cl-a/1
conf port logical-mac cl-
a/1 shutdown
conf port no logical-mac
cl-a/1
conf port gfp cl-a/1 no
bind vcg cl-a/1
conf port gfp cl-a/1
shutdown
conf port no gfp cl-a/1
conf port vcg cl-a/1
shutdown
conf port no vcg cl-a/1
commit

15 Reconfigure 2 Mbps rate, using the The data traffic is running at 2 Mbps
attached script
16 Perform “admin factory-default” The data traffic is running at 2 Mbps

command and commit
17 Reconfigure 2 Mbps rate via a Data traffic is running at 2 Mbps

different vc12, using the attached
script
18 Save the configuration and reboot Once the CL module is on, the data traffic is
the device. running at 2 Mbps.
19 Perform “admin factory-default”

command and commit
20 Configure 32 vcg ports, each with a The data traffic is running at 2 Mbps for each
single vc12 bound to it. of the 32 vcg port.
Configure flows for each vcg port
with different vlans.
21 Step by step, perform changes The data traffic is according to changes.

according to the attached script
(504)
After any step, send data traffic
from IXIA ports (script 505) in
accordance with the configured
data rate.
22 Save the configuration.
23 While data traffic is running, Once CL-A is up, the data traffic recovers.
perform “configure slot cl-a reset”
command.
24 While CL-B is active, perform The data traffic recovers after switching
“configure slot cl-b reset” between CL-A and CL-B
command.
25 While CL-A is active, “configure slot No effect on CL-A

cl-b reset” command
26 Perform admin reboot command. Once CL-A is up, the data traffic recovers.
27 Perform a HW reset. Once CL-A is up, the data traffic recovers.

28 Run the traffic overnight. The data traffic is error-free.
29 Using RADview, perform Read and The date traffic continues error-free.
Update
30 Using RADview, delete the CL After update, data traffic is error-free.

database and perform Update
C.2 Testing New Features for Version 4.6

The attached document describes basic verification tests for Megaplex-4 ver 4.6
new features. The aim is to perform a series of short tests that check the
following:
• ERP main ring + subring functionality
• HSR (HaSaR) protection
• T3 module with Ethernet over n x T1s in a channelized or full T3 link
• New SH-16 module
• New D-NFV module
• New VS voice modules
• Advanced Ethernet services and Traffic Management
• Embedded PW engine for VS modules
• TP module with software-selectable trip voltage.
C.3 Testing New Features for Version 4.7

The attached document describes basic verification tests for Megaplex-4 ver 4.7
new features. The aim is to perform a series of short tests that check the
following:
• New SH-16/E1/PW module
• New VS E1/T1 modules
• Ethernet port statistics presentation in PM portal
• Teleportection module support in RADview
• 802.1x Authenticator & Supplicant
• RSTP
• D-NFV module configuration.
C-66 Testing New Features for Version 4.7 Megaplex-4

Publication No. 464-201-09/15
Order this publication by Catalog No. 803988
International Headquarters
24 Raoul Wallenberg Street
Tel Aviv 69719, Israel
Tel. 972-3-6458181
Fax 972-3-6498250, 6474436
E-mail market@rad.com
North America Headquarters

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

Megaplex-4100

Uploaded by

Copyright:

Available Formats

Megaplex-4100

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Megaplex-4100

Uploaded by

Copyright:

Available Formats

OPERATION MANUAL

International Headquarters North America Headquarters

24 Raoul Wallenberg Street 900 Corporate Drive

© 1988–2015 RAD Data Communications Ltd. Publication No. 464-201-09/15

General Safety Instructions

Protective ground: the marked lug or terminal should be connected to the

Handling Energized Products

General Safety Practices

Connecting Data and Telecommunications Cables

Ports Safety Status

Electromagnetic Compatibility (EMC)

FCC-15 User Information

Canadian Emission Requirements

Warning per EN 55022 (CISPR-22)

Avertissement Cet appareil est un appareil de Classe A. Dans un environnement résidentiel,

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

Mise au rebut du produit

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

Instructions générales de sécurité

Danger de choc électrique ! Evitez tout contact avec la surface marquée

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

Manipuler des produits sous tension

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

Connexion au courant du secteur

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

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

declares that the product:

Product Name: Megaplex-4100

Product Options: All

conforms to the following standard(s) or other normative

EMC EN 55022:2010 Information technology equipment; Radio disturbance

EN 55024:2010 Information technology equipment; Immunity characteristics;

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

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

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

European Contact: RAD Data Communications GmbH

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

declares that the product:

Product Name: Megaplex-4104

Product Options: All

conforms to the following standard(s) or other normative

EMC EN 55022:2010 Information technology equipment; Radio disturbance

EN 55024:2010 Information technology equipment; Immunity characteristics;

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

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

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

European Contact: RAD Data Communications GmbH

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

declares that the product:

Product Name: MPF

Product Option: MPF/48/120VDC

conforms to the following standard(s) or other normative

EMC EN 55022:2010 Information technology equipment; Radio disturbance

EN 55024:2010 Information technology equipment; Immunity characteristics;

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

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

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

European Contact: RAD Data Communications GmbH

1. Installing the Unit